From 3beb7ec6ea450d498296e910a93d3d455ffc91ee Mon Sep 17 00:00:00 2001 From: james7132 Date: Mon, 11 Aug 2025 19:57:04 -0700 Subject: [PATCH 01/13] Add the Bevy Org's AI policy. --- content/learn/contribute/policies/_index.md | 7 ++ content/learn/contribute/policies/ai.md | 79 ++++++++++++++++++++ content/learn/contribute/reference/_index.md | 2 +- content/learn/contribute/reference/triage.md | 6 ++ 4 files changed, 93 insertions(+), 1 deletion(-) create mode 100644 content/learn/contribute/policies/_index.md create mode 100644 content/learn/contribute/policies/ai.md diff --git a/content/learn/contribute/policies/_index.md b/content/learn/contribute/policies/_index.md new file mode 100644 index 0000000000..1289b96e7e --- /dev/null +++ b/content/learn/contribute/policies/_index.md @@ -0,0 +1,7 @@ ++++ +title = "Policies" +template = "docs.html" +redirect_to = "/learn/contribute/policies/ai" +[extra] +weight = 4 ++++ diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md new file mode 100644 index 0000000000..0f7c0cde36 --- /dev/null +++ b/content/learn/contribute/policies/ai.md @@ -0,0 +1,79 @@ ++++ +title = "AI Policy" +insert_anchor_links = "right" +[extra] +weight = 2 ++++ + +In recent times, there have been a growing number of contributions that are fully or +partially produced by generative AI (e.g. LLMs and friends) which exhibit +characteristics that result in undue extra work for other contributors and maintainers. +While we've seen PRs and issues with these characteristics produced entirely by +humans, generative AI tools have significantly lowered the level of effort required to produce +"plausibly-worthwhile" contributions that are otherwise entirely unmergable or +incorrectly report bugs, and so have become a major source of burdensome PRs and +issues. + +Whether AI generated code are copyrightable works is also a hot-button legal topic that is +still being openly debated and litigated. How this impacts the legal aspects of maintaining +a FOSS project is currently a unresolved question. + +This policy is established as a response targeted at the problem of an +increasing frequency of burdensome PRs/issues and to address the potential legal issues +currently surrounding the intersection of AI generated code and the FOSS contribution model. + +## AI Generated Communications +The unsolicited use of automated systems to communicate issues, bugs, or security vulnerabilites +about Bevy Organization projects under the guise of a human is considered unacceptable +and a Code of Conduct violation. Any individual contributor, operator of automated systems, +or company they may represent may be barred from future contributions and banned from regular +communication channels if these communications were found to be submitted in bad faith. + +This policy applies to all regular channels of communication used by members of the +Bevy Organization, including but not limited to GitHub Issues, GitHub Pull Requests, Discord, +other social media platforms, etc. + +We recognize that English may not be the primarily language for all contributors and that +machine translation is an indispensable tool for proper collaboration, and thus not subject to +the above policy, though it is recommended by the community to use non-LLM machine translation +options, as they tend to be less verbose while still getting the point across. + +## Copyrightable AI Generated Contributions +At the current time of writing (August 11th, 2025), the US Copyright Office has +[stated publicly][us-copyright-office-response] that "human authorship is a +pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] +from the same institution shows a much more contested legal space, both within the US and +internationally. In the case that AI generated works are not copyrightable, those same works +cannot be licensed to others, and thus AI-generated code and assets would not legally be +licensed under MIT or Apache. + +Erring on the side of caution in light of a openly debated legal topic, +all[^1] forms of AI-generated contributions cannot be merged into repos maintained +by the Bevy Organization. This includes both code and non-code game assets (e.g. textures, +audio, etc). + +Any triage team member suspecting a pull request to be made primarily through the use of +LLMs or other generative tools should mark the PR as `S-Nominated-to-Close`, upon which a +maintainer can then review the PR for closure. To help identify these cases, +pull requests subject to this policy have characteristics such as (but not limited to): + + * Needlessly or overly verbose descriptions or responses. + * Not internally coherent or even self-contradictory. + * Demonstrates misunderstanding of important aspects of what the code is doing + or the purpose of the change. + +Any contributor, operator of automated systems, or company they may represent found to +have repeatedly submitted contributions with majority AI-generated code or assets may be +subject to: + + * Blanket rejection of all future contributions to Bevy Organization projects. + * Retroactive removal of any potentially suspect AI-generated code and asset contributions. + * Further Code of Conduct actions if these contributions were found to be submitted in bad faith. + +This policy may be revisited when the legal debate has settled. + +[us-copyright-office-response]: https://www.copyright.gov/rulings-filings/review-board/docs/a-recent-entrance-to-paradise.pdf +[us-copyright-office-report]: https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf + +[^1]: Trivial LLM generated content such as variable renames or autocompleted function calls, often branded "predictions" or "suggestions", that is indistinguishable from traditional methods such as a regex search/replace or an LSP autocompletion is by definition not detectable and can be treated like other regular IDE tools such as Intellisense. +This is does not include cases where the prediction generates things like entire function blocks. \ No newline at end of file diff --git a/content/learn/contribute/reference/_index.md b/content/learn/contribute/reference/_index.md index 0af4eece25..1b06421785 100644 --- a/content/learn/contribute/reference/_index.md +++ b/content/learn/contribute/reference/_index.md @@ -3,5 +3,5 @@ title = "Reference" template = "docs.html" redirect_to = "/learn/contribute/reference/triage" [extra] -weight = 4 +weight = 5 +++ diff --git a/content/learn/contribute/reference/triage.md b/content/learn/contribute/reference/triage.md index 10698d8f6b..a77c58e8a3 100644 --- a/content/learn/contribute/reference/triage.md +++ b/content/learn/contribute/reference/triage.md @@ -91,6 +91,10 @@ Some reasons to apply `D-Trivial` include: 2. Moving a file from one location to another. 3. Small changes to documentation or error messages. +Some reasons to apply `S-Nominated-to-Close` include: + + 1. The PR shows inconsistencies and verbosity to suggest that the code was [AI generated][ai-policy]. + Remember that difficulty labels are for expertise required to either solve an issue or review a pull request. By labeling an issue as `D-Trivial`, you are marking it as a good first issue for new contributors to the Bevy project. ## Closing PRs and Issues @@ -118,6 +122,7 @@ There are several paths for PRs to be closed: 6. In the case of PRs where some members of the community, other than the author, are in favor, and some are opposed, any two relevant SMEs or Maintainers may act in concert to close the PR. 7. For a PR that has been sitting for a while and became bitrotten, check with the original author if they intend to continue working on it. If not, or without a response, the PR can be labeled with `S-Adopt-Me`, and closed. Tracking adoption progress will happen in a linked issue. 8. Inactive `X-Controversial` can be closed if relevant SMEs or Maintainers have decided there's no more interest for it. If it's still interesting and controversial, a decision must be made. +9. Majority AI-Generated PRs cannot be merged as per the Bevy org's [AI policy][ai-policy]. Please mark these PRs as `S-Nominated-to-Close` for maintainers to make a final decision. When closing a PR, check if it has an issue linked. If it does not, you should strongly consider creating an issue and linking the now-closed PR to help make sure the previous work can be discovered and credited. @@ -167,3 +172,4 @@ Members of the Triage Team within the Bevy organization have permissions to labe If that applies to you, then feel free to ask a Maintainer on [Discord] or email . Everyone is welcome to do this. We generally accept membership requests, so don't hesitate if you are interested! [Discord]: https://discord.gg/bevy +[ai-policy]: /learn/contribute/policies/ai \ No newline at end of file From d57703bb1ec1cbceeae9bda157815c1f5e87a5c2 Mon Sep 17 00:00:00 2001 From: james7132 Date: Mon, 11 Aug 2025 20:07:38 -0700 Subject: [PATCH 02/13] Change weight --- content/learn/contribute/policies/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index 0f7c0cde36..0929117a2e 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -2,7 +2,7 @@ title = "AI Policy" insert_anchor_links = "right" [extra] -weight = 2 +weight = 1 +++ In recent times, there have been a growing number of contributions that are fully or From be755418717cae5c7eecb58c4fc0dd4b3806853c Mon Sep 17 00:00:00 2001 From: james7132 Date: Mon, 11 Aug 2025 20:09:05 -0700 Subject: [PATCH 03/13] Add a copy of the Code of Conduct to the Polciies section --- .../contribute/policies/code_of_conduct.md | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 content/learn/contribute/policies/code_of_conduct.md diff --git a/content/learn/contribute/policies/code_of_conduct.md b/content/learn/contribute/policies/code_of_conduct.md new file mode 100644 index 0000000000..1b3c7af266 --- /dev/null +++ b/content/learn/contribute/policies/code_of_conduct.md @@ -0,0 +1,44 @@ ++++ +title = "Code of Conduct" +insert_anchor_links = "right" +[extra] +weight = 1 ++++ + +_This Code of Conduct is based on the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct), which is adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) and the [Contributor Covenant](https://www.contributor-covenant.org)._ + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. + +## Our Standards + +In this community we strive to go the extra step to look out for each other. Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely. + +And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better — remember that it’s your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust. + +* Please avoid using overtly sexual aliases or other nicknames that might detract from a friendly, safe and welcoming environment for all. +* Please be kind and courteous. There’s no need to be mean or rude. +* Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer. +* Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works. +* We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term “harassment” as including the definition in the [Citizen Code of Conduct](https://github.com/stumpsyn/policies/blob/master/citizen_code_of_conduct.md); if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don’t tolerate behavior that excludes people in socially marginalized groups. +* Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact the maintainers immediately. Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you and we’ve got your back. +* Do not make casual mention of slavery or indentured servitude and/or false comparisons of one's occupation or situation to slavery. Please consider using or asking about alternate terminology when referring to such metaphors in technology. +* Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome. + +## Moderation + +These are the policies for upholding [our community’s standards of conduct](#our-standards). If you feel that a thread needs moderation, please contact the maintainers. + +1. Remarks that violate the community standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner). +2. Remarks that maintainers find inappropriate, whether listed in the code of conduct or not, are also not allowed. +3. Maintainers will first respond to such remarks with a warning. +4. If the warning is unheeded, the user will be “kicked,” i.e., kicked out of the communication channel to cool off. +5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded. +6. Maintainers may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology. +7. If a maintainer bans someone and you think it was unjustified, please take it up with that maintainer, or with a different maintainer, in private. Complaints about bans in-channel are not allowed. +8. Maintainers are held to a higher standard than other community members. If a maintainer creates an inappropriate situation, they should expect less leeway than others. + +The enforcement policies in the code of conduct apply to all official venues, including Discord channels, GitHub repositories, the Twitter community and all other forums. From 6dd1db3b1f725977160f802bc3bc8f3503e8d940 Mon Sep 17 00:00:00 2001 From: James Liu Date: Tue, 12 Aug 2025 16:39:31 +0000 Subject: [PATCH 04/13] a -> an MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: François Mockers --- content/learn/contribute/policies/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index 0929117a2e..9b09a29013 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -16,7 +16,7 @@ issues. Whether AI generated code are copyrightable works is also a hot-button legal topic that is still being openly debated and litigated. How this impacts the legal aspects of maintaining -a FOSS project is currently a unresolved question. +a FOSS project is currently an unresolved question. This policy is established as a response targeted at the problem of an increasing frequency of burdensome PRs/issues and to address the potential legal issues From 075c91469e7ee6dd86eeb21a90fc49929fc1801a Mon Sep 17 00:00:00 2001 From: Alice Cecile Date: Tue, 12 Aug 2025 13:07:27 -0400 Subject: [PATCH 05/13] Spelling MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: François Mockers --- content/learn/contribute/policies/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index 9b09a29013..a52d392fdc 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -23,7 +23,7 @@ increasing frequency of burdensome PRs/issues and to address the potential legal currently surrounding the intersection of AI generated code and the FOSS contribution model. ## AI Generated Communications -The unsolicited use of automated systems to communicate issues, bugs, or security vulnerabilites +The unsolicited use of automated systems to communicate issues, bugs, or security vulnerabilities about Bevy Organization projects under the guise of a human is considered unacceptable and a Code of Conduct violation. Any individual contributor, operator of automated systems, or company they may represent may be barred from future contributions and banned from regular From d896d372344300113cc639876c52c272d54a6527 Mon Sep 17 00:00:00 2001 From: Alice Cecile Date: Tue, 12 Aug 2025 15:14:50 -0400 Subject: [PATCH 06/13] Whitespace MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: François Mockers --- content/learn/contribute/policies/ai.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index a52d392fdc..c1e0711f0a 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -23,6 +23,7 @@ increasing frequency of burdensome PRs/issues and to address the potential legal currently surrounding the intersection of AI generated code and the FOSS contribution model. ## AI Generated Communications + The unsolicited use of automated systems to communicate issues, bugs, or security vulnerabilities about Bevy Organization projects under the guise of a human is considered unacceptable and a Code of Conduct violation. Any individual contributor, operator of automated systems, @@ -39,6 +40,7 @@ the above policy, though it is recommended by the community to use non-LLM machi options, as they tend to be less verbose while still getting the point across. ## Copyrightable AI Generated Contributions + At the current time of writing (August 11th, 2025), the US Copyright Office has [stated publicly][us-copyright-office-response] that "human authorship is a pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] From 7af64b4b61bbef7dfbab956177b8c88310d78b10 Mon Sep 17 00:00:00 2001 From: James Liu Date: Tue, 12 Aug 2025 12:39:44 -0700 Subject: [PATCH 07/13] Expand `S-Nominated-to-Close` guidance. Co-authored-by: Alice Cecile --- content/learn/contribute/reference/triage.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/learn/contribute/reference/triage.md b/content/learn/contribute/reference/triage.md index a77c58e8a3..b832d0cb04 100644 --- a/content/learn/contribute/reference/triage.md +++ b/content/learn/contribute/reference/triage.md @@ -94,6 +94,8 @@ Some reasons to apply `D-Trivial` include: Some reasons to apply `S-Nominated-to-Close` include: 1. The PR shows inconsistencies and verbosity to suggest that the code was [AI generated][ai-policy]. + 2. The PR has serious flaws and has not attracted any support from reviewers. + 3. The PR is no longer needed. Remember that difficulty labels are for expertise required to either solve an issue or review a pull request. By labeling an issue as `D-Trivial`, you are marking it as a good first issue for new contributors to the Bevy project. From e2a29c8469c11e04e55f57c90d0b27bcce82ce6e Mon Sep 17 00:00:00 2001 From: Alice Cecile Date: Wed, 13 Aug 2025 12:35:33 -0400 Subject: [PATCH 08/13] Typo Co-authored-by: Niklas Eicker --- content/learn/contribute/policies/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index c1e0711f0a..35248e18b7 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -78,4 +78,4 @@ This policy may be revisited when the legal debate has settled. [us-copyright-office-report]: https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf [^1]: Trivial LLM generated content such as variable renames or autocompleted function calls, often branded "predictions" or "suggestions", that is indistinguishable from traditional methods such as a regex search/replace or an LSP autocompletion is by definition not detectable and can be treated like other regular IDE tools such as Intellisense. -This is does not include cases where the prediction generates things like entire function blocks. \ No newline at end of file +This does not include cases where the prediction generates things like entire function blocks. \ No newline at end of file From 78035f00e2caa729678e16b280f5ca23d1db948a Mon Sep 17 00:00:00 2001 From: James Liu Date: Fri, 15 Aug 2025 03:26:42 +0000 Subject: [PATCH 09/13] Apply suggestions from code review Co-authored-by: Alice Cecile --- content/learn/contribute/policies/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index 35248e18b7..2203475fc4 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -36,7 +36,7 @@ other social media platforms, etc. We recognize that English may not be the primarily language for all contributors and that machine translation is an indispensable tool for proper collaboration, and thus not subject to -the above policy, though it is recommended by the community to use non-LLM machine translation +the above policy. The community recommends that you instruct the LLM to produce a concise output or use non-LLM machine translation options, as they tend to be less verbose while still getting the point across. ## Copyrightable AI Generated Contributions From e3668cad5d04161db1c3243736a51c108992404c Mon Sep 17 00:00:00 2001 From: james7132 Date: Thu, 14 Aug 2025 20:36:04 -0700 Subject: [PATCH 10/13] Reword legal argument --- content/learn/contribute/policies/ai.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index 2203475fc4..c04c5d85d4 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -45,9 +45,10 @@ At the current time of writing (August 11th, 2025), the US Copyright Office has [stated publicly][us-copyright-office-response] that "human authorship is a pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] from the same institution shows a much more contested legal space, both within the US and -internationally. In the case that AI generated works are not copyrightable, those same works -cannot be licensed to others, and thus AI-generated code and assets would not legally be -licensed under MIT or Apache. +internationally. In the case that AI generated works are copyrightable, those works +would be considered derivatives of the input dataset, and thus use AI-generated code and assets +may constitute copyright infringement or may be subject to licensing terms incompatible +with the FOSS licenses used by the Bevy Organization. Erring on the side of caution in light of a openly debated legal topic, all[^1] forms of AI-generated contributions cannot be merged into repos maintained From 7c7634e9a1b853062f5582be654997d78cc6e087 Mon Sep 17 00:00:00 2001 From: james7132 Date: Thu, 14 Aug 2025 20:40:57 -0700 Subject: [PATCH 11/13] Reword some additonal parts for clarity --- content/learn/contribute/policies/ai.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index c04c5d85d4..b920002333 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -6,7 +6,7 @@ weight = 1 +++ In recent times, there have been a growing number of contributions that are fully or -partially produced by generative AI (e.g. LLMs and friends) which exhibit +partially produced by generative AI (e.g. large language models and friends) which exhibit characteristics that result in undue extra work for other contributors and maintainers. While we've seen PRs and issues with these characteristics produced entirely by humans, generative AI tools have significantly lowered the level of effort required to produce @@ -14,7 +14,7 @@ humans, generative AI tools have significantly lowered the level of effort requi incorrectly report bugs, and so have become a major source of burdensome PRs and issues. -Whether AI generated code are copyrightable works is also a hot-button legal topic that is +Whether AI generated code are subject to copyright protection is also a hot-button legal topic that is still being openly debated and litigated. How this impacts the legal aspects of maintaining a FOSS project is currently an unresolved question. @@ -36,28 +36,29 @@ other social media platforms, etc. We recognize that English may not be the primarily language for all contributors and that machine translation is an indispensable tool for proper collaboration, and thus not subject to -the above policy. The community recommends that you instruct the LLM to produce a concise output or use non-LLM machine translation -options, as they tend to be less verbose while still getting the point across. +the above policy. The community recommends that you instruct the LLM to produce a concise output +or use non-LLM machine translation options, as they tend to be less verbose while still getting +the point across. -## Copyrightable AI Generated Contributions +## AI Generated Contributions and Copyright At the current time of writing (August 11th, 2025), the US Copyright Office has [stated publicly][us-copyright-office-response] that "human authorship is a pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] from the same institution shows a much more contested legal space, both within the US and -internationally. In the case that AI generated works are copyrightable, those works +internationally. In the case that AI generated works are protected under copyright, those works would be considered derivatives of the input dataset, and thus use AI-generated code and assets may constitute copyright infringement or may be subject to licensing terms incompatible with the FOSS licenses used by the Bevy Organization. Erring on the side of caution in light of a openly debated legal topic, -all[^1] forms of AI-generated contributions cannot be merged into repos maintained +all[^1] forms of AI-generated contributions cannot be merged into repositories maintained by the Bevy Organization. This includes both code and non-code game assets (e.g. textures, audio, etc). Any triage team member suspecting a pull request to be made primarily through the use of -LLMs or other generative tools should mark the PR as `S-Nominated-to-Close`, upon which a -maintainer can then review the PR for closure. To help identify these cases, +large language models or other generative tools should mark the PR as `S-Nominated-to-Close`, +upon which a maintainer can then review the PR for closure. To help identify these cases, pull requests subject to this policy have characteristics such as (but not limited to): * Needlessly or overly verbose descriptions or responses. From 6e392362347d98499af797b472b47404cc699705 Mon Sep 17 00:00:00 2001 From: james7132 Date: Thu, 14 Aug 2025 20:54:58 -0700 Subject: [PATCH 12/13] Formatting --- content/learn/contribute/policies/ai.md | 64 ++++++++++++------------- 1 file changed, 32 insertions(+), 32 deletions(-) diff --git a/content/learn/contribute/policies/ai.md b/content/learn/contribute/policies/ai.md index b920002333..e28fe433aa 100644 --- a/content/learn/contribute/policies/ai.md +++ b/content/learn/contribute/policies/ai.md @@ -5,20 +5,20 @@ insert_anchor_links = "right" weight = 1 +++ -In recent times, there have been a growing number of contributions that are fully or -partially produced by generative AI (e.g. large language models and friends) which exhibit -characteristics that result in undue extra work for other contributors and maintainers. -While we've seen PRs and issues with these characteristics produced entirely by -humans, generative AI tools have significantly lowered the level of effort required to produce +In recent times, there have been a growing number of contributions that are fully or +partially produced by generative AI (e.g. large language models and friends) which exhibit +characteristics that result in undue extra work for other contributors and maintainers. +While we've seen PRs and issues with these characteristics produced entirely by +humans, generative AI tools have significantly lowered the level of effort required to produce "plausibly-worthwhile" contributions that are otherwise entirely unmergable or incorrectly report bugs, and so have become a major source of burdensome PRs and issues. -Whether AI generated code are subject to copyright protection is also a hot-button legal topic that is +Whether AI generated code are subject to copyright protection is also a hot-button legal topic that is still being openly debated and litigated. How this impacts the legal aspects of maintaining a FOSS project is currently an unresolved question. -This policy is established as a response targeted at the problem of an +This policy is established as a response targeted at the problem of an increasing frequency of burdensome PRs/issues and to address the potential legal issues currently surrounding the intersection of AI generated code and the FOSS contribution model. @@ -30,54 +30,54 @@ and a Code of Conduct violation. Any individual contributor, operator of automat or company they may represent may be barred from future contributions and banned from regular communication channels if these communications were found to be submitted in bad faith. -This policy applies to all regular channels of communication used by members of the -Bevy Organization, including but not limited to GitHub Issues, GitHub Pull Requests, Discord, +This policy applies to all regular channels of communication used by members of the +Bevy Organization, including but not limited to GitHub Issues, GitHub Pull Requests, Discord, other social media platforms, etc. -We recognize that English may not be the primarily language for all contributors and that +We recognize that English may not be the primarily language for all contributors and that machine translation is an indispensable tool for proper collaboration, and thus not subject to -the above policy. The community recommends that you instruct the LLM to produce a concise output -or use non-LLM machine translation options, as they tend to be less verbose while still getting +the above policy. The community recommends that you instruct the LLM to produce a concise output +or use non-LLM machine translation options, as they tend to be less verbose while still getting the point across. ## AI Generated Contributions and Copyright At the current time of writing (August 11th, 2025), the US Copyright Office has [stated publicly][us-copyright-office-response] that "human authorship is a -pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] -from the same institution shows a much more contested legal space, both within the US and -internationally. In the case that AI generated works are protected under copyright, those works -would be considered derivatives of the input dataset, and thus use AI-generated code and assets +pre-requisite to copyright protection". A [more recent report][us-copyright-office-report] +from the same institution shows a much more contested legal space, both within the US and +internationally. In the case that AI generated works are protected under copyright, those works +would be considered derivatives of the input dataset, and thus use AI-generated code and assets may constitute copyright infringement or may be subject to licensing terms incompatible with the FOSS licenses used by the Bevy Organization. -Erring on the side of caution in light of a openly debated legal topic, -all[^1] forms of AI-generated contributions cannot be merged into repositories maintained +Erring on the side of caution in light of a openly debated legal topic, +all[^1] forms of AI-generated contributions cannot be merged into repositories maintained by the Bevy Organization. This includes both code and non-code game assets (e.g. textures, audio, etc). -Any triage team member suspecting a pull request to be made primarily through the use of -large language models or other generative tools should mark the PR as `S-Nominated-to-Close`, -upon which a maintainer can then review the PR for closure. To help identify these cases, -pull requests subject to this policy have characteristics such as (but not limited to): +Any triage team member suspecting a pull request to be made primarily through the use of +large language models or other generative tools should mark the PR as `S-Nominated-to-Close` , +upon which a maintainer can then review the PR for closure. To help identify these cases, +pull requests subject to this policy have characteristics such as (but not limited to): - * Needlessly or overly verbose descriptions or responses. - * Not internally coherent or even self-contradictory. - * Demonstrates misunderstanding of important aspects of what the code is doing - or the purpose of the change. +- Needlessly or overly verbose descriptions or responses. +- Not internally coherent or even self-contradictory. +- Demonstrates misunderstanding of important aspects of what the code is doing + or the purpose of the change. Any contributor, operator of automated systems, or company they may represent found to -have repeatedly submitted contributions with majority AI-generated code or assets may be +have repeatedly submitted contributions with majority AI-generated code or assets may be subject to: - * Blanket rejection of all future contributions to Bevy Organization projects. - * Retroactive removal of any potentially suspect AI-generated code and asset contributions. - * Further Code of Conduct actions if these contributions were found to be submitted in bad faith. +- Blanket rejection of all future contributions to Bevy Organization projects. +- Retroactive removal of any potentially suspect AI-generated code and asset contributions. +- Further Code of Conduct actions if these contributions were found to be submitted in bad faith. This policy may be revisited when the legal debate has settled. [us-copyright-office-response]: https://www.copyright.gov/rulings-filings/review-board/docs/a-recent-entrance-to-paradise.pdf [us-copyright-office-report]: https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf -[^1]: Trivial LLM generated content such as variable renames or autocompleted function calls, often branded "predictions" or "suggestions", that is indistinguishable from traditional methods such as a regex search/replace or an LSP autocompletion is by definition not detectable and can be treated like other regular IDE tools such as Intellisense. -This does not include cases where the prediction generates things like entire function blocks. \ No newline at end of file +[^1]: Trivial LLM generated content such as variable renames or autocompleted function calls, often branded "predictions" or "suggestions", that is indistinguishable from traditional methods such as a regex search/replace or an LSP autocompletion is by definition not detectable and can be treated like other regular IDE tools such as Intellisense. +This does not include cases where the prediction generates things like entire function blocks. From 9d093fb8dda461604c80ef5002f9bf6717af7e6e Mon Sep 17 00:00:00 2001 From: james7132 Date: Thu, 14 Aug 2025 21:14:32 -0700 Subject: [PATCH 13/13] More formatting --- content/learn/contribute/reference/triage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learn/contribute/reference/triage.md b/content/learn/contribute/reference/triage.md index b832d0cb04..dd62bcea60 100644 --- a/content/learn/contribute/reference/triage.md +++ b/content/learn/contribute/reference/triage.md @@ -174,4 +174,4 @@ Members of the Triage Team within the Bevy organization have permissions to labe If that applies to you, then feel free to ask a Maintainer on [Discord] or email . Everyone is welcome to do this. We generally accept membership requests, so don't hesitate if you are interested! [Discord]: https://discord.gg/bevy -[ai-policy]: /learn/contribute/policies/ai \ No newline at end of file +[ai-policy]: /learn/contribute/policies/ai