From 823e93b640dea2205d6df2bc51586552a52898d7 Mon Sep 17 00:00:00 2001 From: Justin Wheeler Date: Oct 25 2025 02:56:44 +0000 Subject: 📝 docs(council): Add AI-Assisted Contributions Policy This commit is the initial commit of the AI-Assisted Contributions Policy, as voted on and approved by the Fedora Council on Wednesday, 22 October 2025. This text is an AsciiDoc representation of the policy text approved in the ticket. Very few minor changes were made at commit time: 1. Bullet levels: For the Transparency rule, I used bullets at further sub-levels / indentions to more clearly organize the information in AsciiDoc. This also more clearly ties the sub-levels to the Transparency rule. The original text simply used whitespace, which is not obvious how to do in AsciiDoc. 2. Wiki page categories: I added a new type of disclosure at my own discretion, about how content creators can declare the use of AI when using it for writing Fedora Wiki pages. Fedora contributors can use a new Fedora Wiki category to "declare" the use of generative AI on Wiki page content. I linked to the Fedora Wiki category page in the policy document. This was not in the original draft, but it does not change the interpretation or substance of the policy itself. Since it provides further context about how contributors should appropriately declare the use of generative AI, this felt like an appropriate change to slip in without triggering another round of voting. 3. Author credit: I credited @jasonbrooks, the Fedora Council, and the Fedora community as authors of this policy, in recognition of the work that Jason specifically did in crafting the policy, the input of the Fedora Council in shaping the final version of the policy, and of course, the valuable input from our diverse, global community of contributors who helped us shape this policy over several weeks, if not months (depending when you consider this work as having started). Closes Fedora-Council/tickets#542. ref: https://pagure.io/Fedora-Council/tickets/issue/542 ref: https://discussion.fedoraproject.org/t/fedora-council-meeting-2025-10-22-ai-policy-approved-docs-initiative-proposed/169630 Signed-off-by: Justin Wheeler --- diff --git a/council/modules/ROOT/nav.adoc b/council/modules/ROOT/nav.adoc index dcca7ee..e847e77 100644 --- a/council/modules/ROOT/nav.adoc +++ b/council/modules/ROOT/nav.adoc @@ -8,6 +8,7 @@ include::ROOT:partial$attributes.adoc[] ** xref:foa.adoc[Fedora Operations Architect] ** xref:dei:roles:council-advisor.adoc[Fedora DEI Advisor ^[🡵\]^] * Council Policies +** xref:policy/ai-contribution-policy.adoc[AI-Assisted Contributions Policy] ** xref:policy/community-publishing-platforms.adoc[Community Publishing Platforms] ** xref:policy/guiding-policy.adoc[Guiding Policy] ** xref:policy/policy-change-policy.adoc[Policy Change Policy] diff --git a/council/modules/ROOT/pages/policy/ai-contribution-policy.adoc b/council/modules/ROOT/pages/policy/ai-contribution-policy.adoc new file mode 100644 index 0000000..49152b1 --- /dev/null +++ b/council/modules/ROOT/pages/policy/ai-contribution-policy.adoc @@ -0,0 +1,36 @@ +include::ROOT:partial$attributes.adoc[] + += AI-Assisted Contributions Policy +Jason Brooks; Fedora Council; Fedora community +: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. +:page-authors: {author}, {author_2}, {author_3} + +. You *MAY* use AI assistance for contributing to Fedora, as long as you follow the principles described below. +. *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. +. *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 link:{url_wiki}/Category:AI_Assistance_Used[wiki page categories]. +** Examples: +*** `Assisted-by: generic LLM chatbot` +*** `Assisted-by: ChatGPTv5` +. *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. + +Concerns about possible policy violations should be reported via {team_issue_tracker_name} private tickets link:{team_issue_tracker}[to Fedora Council]. + +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].