-
Notifications
You must be signed in to change notification settings - Fork 112
RFC: Add AI tool use policy in code of conduct #876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I love this |
This is a reasonable approach. I like it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is all common sense for anyone familiar with OSS communities and the discourse around AI. I think it's a good to spell it out for those who are new to OSS. I am in favor of adding this.
I am curious, has anyone in the WG had a negative experience with a reviewer or submitter using AI? In other words is this policy to make the WG position clear before problems exist, or is this already a problem?
Yes |
Thank you for writing this up, it's great! |
First-rate. Thanks much. |
Our golden rule is that a contribution should be worth more to the project than the time it takes to review it. If a maintainer judges that a contribution is extractive (i.e., it is generated with tool-assistance or simply requires significant revision), they | ||
should copy-paste the following response, add the `extractive` label if applicable, and refrain from further engagement: | ||
|
||
> This PR appears to be extractive, and requires additional justification for why it is valuable enough to the project for us to review it. Please see our developer policy on AI-generated contributions: https://github.com/rust-embedded/wg/blob/master/CODE_OF_CONDUCT.md#AI-Tool-Use-Policy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this specific to the use of AI ? LLMs facilitates this but It feels like this section could be a ##
too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can make it ##
, sure! If you open a suggestion I will add it to the PR
I can't say for sure but I have strong suspicions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for writing this up, looks good to me and captures our discussion last week well. What do you think of these slight wording tweaks?
Co-authored-by: Adam Greig <[email protected]>
709fd60
Co-authored-by: Adam Greig <[email protected]>
Co-authored-by: Adam Greig <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was very well written and thoughtful, thank you!
Which team has sign-off for this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
As discussed on the previous WG meeting, I think we should include a few sentences regarding the use of AI tools in our code of conduct.
I adapted the proposed text for the LLVM project to our needs. Let me know what you think!