Repository navigation
RFC: Update the AI policy - #942
Merged
Merged
Conversation
This follows the discussion had during the meeting on 2026-09-22 rust-embedded#940
Dirbaio
approved these changes
Sep 23, 2026
Contributor
Author
Member
|
Apologies, I thought a smallish wording update wouldn't need such reviews, but now I see the discussion item has some debate there. Feedback can be added here and I can follow up with a PR. I'll ping the discussion thread to ensure those get a chance to sign off on this wording. |
adamgreig
reviewed
Sep 23, 2026
| When using AI tools for contributing, human oversight remains critical. | ||
|
|
||
| - **You are responsible for your contributions.** It is your responsibility to review, test, and understand everything you submit. Submitting unverified or low-quality machine-generated content creates an unfair review burden on the community and is not an acceptable contribution. Contributors should review and understand their own submissions before asking the community to review their code. | ||
| - **AI tools must not replace humain-to-human contributons.** AI generated prose must not be used in code comments, commit messages, github issues or pull requests descriptions and comments. AI generated prose tend to require time and energy to sort trough, do not expect fellow contributors to do it for you. You must understand what you submit, explaining it in your own words proves that you do, while AI prose raises doubts. |
Member
There was a problem hiding this comment.
Suggested change
| - **AI tools must not replace humain-to-human contributons.** AI generated prose must not be used in code comments, commit messages, github issues or pull requests descriptions and comments. AI generated prose tend to require time and energy to sort trough, do not expect fellow contributors to do it for you. You must understand what you submit, explaining it in your own words proves that you do, while AI prose raises doubts. | |
| - **AI tools must not replace humain-to-human contributons.** AI generated prose must not be used in code comments, commit messages, GitHub issues or pull requests descriptions and comments. AI generated prose tend to require time and energy to sort through, do not expect fellow contributors to do it for you. You must understand what you submit, so explaining it in your own words proves that you do, while AI prose raises doubts. |
Contributor
Author
There was a problem hiding this comment.
An unfortunate typo 😅
Contributor
Author
There was a problem hiding this comment.
I pushed the fixes to the ai-update branch in my fork but I'm not sure how to proceed with the already-merged PR
Member
There was a problem hiding this comment.
I opened #943 but I'm equally happy with a new PR with these changes too.
Member
|
Would you mind re-opening this PR? (edit: possibly you'll have to create a new one from the same branch since this got merged). |
Merged
Contributor
Author
|
Re-Opened in: #944 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This follows the discussion had during the meeting on 2026-09-22: #940
I tried to be succinct, while still explaining why the policy is that way.