council/docs
council/docs
11
0
Fork 3
Code Issues 7 Pull requests 1 Projects Activity Actions
docs/council/modules/ROOT/pages/policy/ai-contribution-policy.adoc
Justin Wheeler 6fdcc1bead
 📝 docs(council): Add versioning and date of approval to AI Policy 
This commit edits the frontmatter of the Fedora AI-Assisted
Contributions Policy to clearly note the document version (v1.0, the
original and first version) and the date of the publication, which was
when the git commit was merged into this repository on Friday, October
24th, 2025.

No changes to policy content; this just makes it easier for ourselves
and the rest of the world to understand the versioning and cadence of
our own policy documents. It also subtly encourages us to maintain a
changelog, so we can always clearly explain what changes we made and
why. Transparency++

Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-01-15 22:04:36 -05:00

3.1 KiB
Raw Permalink Blame History

AI-Assisted Contributions Policy

Jason Brooks; Fedora Council; Fedora community v1.0, 2025-10-24 :description: Fedora Project’s official policy for AI-assisted contributions. Learn the key rules on accountability, transparency, and the proper use of generative AI tools.

  1. You MAY use AI assistance for contributing to Fedora, as long as you follow the principles described below.

  2. Accountability: You MUST take the responsibility for your contribution. Contributing to Fedora 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.

  3. 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 other contributions, disclosure may include document preambles, design file metadata, translation notes, or wiki page categories.

    • Examples:

      • Assisted-by: generic LLM chatbot

      • Assisted-by: ChatGPTv5

  4. 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.

  5. 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.

Concerns about possible policy violations should be reported via {team_issue_tracker_name} private tickets to Fedora Council.

The key words “MAY”, “MUST”, “MUST NOT”, and “SHOULD” in this document are to be interpreted as described in RFC 2119.