Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,10 @@ The process for [submitting original content](https://docs.rockylinux.org/guides

## Notes

### AI-Assisted Contributions

For information about the Rocky Linux Documentation policy on AI-Assisted Contributions please review [Ai-Assisted Contributions Policy](https://docs.rockylinux.org/guides/contribute/createnew/)

### Links

Links can be internal (other docs within our domain), external (publicly hosted URLs), or lab-based (used as examples within your document).
Expand Down
1 change: 1 addition & 0 deletions docs/guides/contribute/.pages
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
nav:
- ... | README*.md
- ... | beginners*.md
- ... | ai-contribution-policy*.md
- ... | createnew*.md
- ... | rockydocs_formatting*.md
- Local Documentation: localdocs
Expand Down
53 changes: 53 additions & 0 deletions docs/guides/contribute/ai-contribution-policy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
!!! note
This Rocky Linux Documentation project’s AI-Assisted Contributions Policy is based on and extends the [AI-Assisted Contributions Policy](https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/) developed by the Fedora Project.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There needs to be a blank line between the admonition type and the content line. FYI. This is easily fixable with an edit later though.



You *MAY* use AI assistance for contributing to the Rocky Linux Documentation Project, as long as you follow the principles described below.

*Accountability*

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than using bold face, I think the best policy would be to use a Level 2 heading for each. For instance:

## Accountability
## Transparency
## Examples 

Which renders bold face anyway:

Accountability

Transparency

Examples

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then just continue down the page with the other bold face items as Level 2 headings as well.

You *MUST* take the responsibility for your contribution.
Contributing to Rocky Linux means vouching for the quality, license compliance, and utility of your submission.
All contributions, whether from a human author or assisted by large language models (LLMs) or other generative AI tools, must meet the project’s standards for inclusion.
The contributor is always the author and is fully accountable for the entirety of these contributions.

*Transparency*

You *MUST* disclose the use of AI tools when the significant part of the contribution is taken from a tool without changes.
You *SHOULD* disclose the other uses of AI tools, where it might be useful.
Routine use of assistive tools for correcting grammar and spelling, or for clarifying language, does not require disclosure.
Information about the use of AI tools will help us evaluate their impact, build new best practices and adjust existing processes.
Disclosures are made where authorship is normally indicated.
For contributions tracked in git, the recommended method is an `Assisted-by:` commit message trailer.
For contributed content, disclosure must be included in the document preamble or other document metadata section.

Examples:
```
---
title:
author: Steven Spencer
contributors: Ganna Zhyrnova, Colussi Franco, tianci li, Wale Soyinka
ai-contributors: Claude (claude-sonnet-4-20250514), Gemini (gemini-2.5-pro)
---
```

*Contribution & Community Evaluation*

AI tools may be used to assist human reviewers by providing analysis and suggestions.
You *MUST NOT* use AI as the sole or final arbiter in making a substantive or subjective judgment on a contribution, nor may it be used to evaluate a person’s standing within the community (e.g., for funding, leadership roles, or Code of Conduct matters).
This does not prohibit the use of automated tooling for objective technical validation, such as CI/CD pipelines, automated testing, or spam filtering.
The final accountability for accepting a contribution, even if implemented by an automated system, always rests with the human contributor who authorizes the action.

*Large scale initiatives*

The policy does not cover the large scale initiatives which may significantly change the ways the project operates or lead to exponential growth in contributions in some parts of the project. Such initiatives need to be discussed separately with the Fedora Council.

**Respect for Existing Contributions**

You *MUST NOT* submit AI-generated contributions that are primarily derived from, or substantially a rework of, other contributors’ work.
AI-assisted edits *SHOULD* preserve the original author’s intent, voice, and structure.


Concerns about possible policy violations should be reported as an [issue via this link](https://github.com/rocky-linux/documentation/issues)

The key words “MAY”, “MUST”, “MUST NOT”, and “SHOULD” in this document are to be interpreted as described in link:https://datatracker.ietf.org/doc/html/rfc2119[RFC 2119].