Skip to content

RFC: Add AI tool use policy in code of conduct - #876

Merged
adamgreig merged 4 commits into
rust-embedded:masterfrom
romancardenas:master
Oct 22, 2025
Merged

adamgreig merged 4 commits into
rust-embedded:masterfrom
romancardenas:master

Conversation

@romancardenas

Copy link
Copy Markdown
Contributor

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!

@romancardenas
romancardenas requested a review from a team as a code owner October 13, 2025 11:21
@jonathanpallant

Copy link
Copy Markdown
Contributor

I love this

MabezDev
MabezDev previously approved these changes Oct 13, 2025
@sirhcel

sirhcel commented Oct 13, 2025

Copy link
Copy Markdown
Member

This is a reasonable approach. I like it.

newAM
newAM previously approved these changes Oct 13, 2025

@newAM newAM left a comment

Copy link
Copy Markdown
Member

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?

robamu
robamu previously approved these changes Oct 13, 2025
@jonathanpallant

Copy link
Copy Markdown
Contributor

has anyone in the WG had a negative experience with a reviewer or submitter using AI

Yes

rmsyn
rmsyn previously approved these changes Oct 13, 2025
@rmsyn

rmsyn commented Oct 13, 2025

Copy link
Copy Markdown
Contributor

Thank you for writing this up, it's great!

@BartMassey

Copy link
Copy Markdown
Member

First-rate. Thanks much.

Comment thread CODE_OF_CONDUCT.md
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

Copy link
Copy Markdown
Member

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.

Copy link
Copy Markdown
Contributor Author

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

@ithinuel

Copy link
Copy Markdown
Member

I am curious, has anyone in the WG had a negative experience with a reviewer or submitter using AI?

I can't say for sure but I have strong suspicions.

@adamgreig adamgreig left a comment

Copy link
Copy Markdown
Member

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?

Comment thread CODE_OF_CONDUCT.md Resolved
Comment thread CODE_OF_CONDUCT.md Resolved
Comment thread CODE_OF_CONDUCT.md Resolved
Co-authored-by: Adam Greig <adam@adamgreig.com>
@romancardenas
romancardenas dismissed stale reviews from rmsyn, robamu, newAM, and MabezDev via 709fd60 October 15, 2025 12:12
romancardenas and others added 2 commits October 15, 2025 14:12
Co-authored-by: Adam Greig <adam@adamgreig.com>
Co-authored-by: Adam Greig <adam@adamgreig.com>

@jamesmunns jamesmunns left a comment

Copy link
Copy Markdown
Member

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!

@jonathanpallant

Copy link
Copy Markdown
Contributor

Which team has sign-off for this PR?

@berkus berkus left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

@jamesmunns
jamesmunns requested a review from a team October 21, 2025 18:15

@BartMassey BartMassey left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks much for this

@jamesmunns

Copy link
Copy Markdown
Member

(I've added @rust-embedded/all, feel free to add a more "load bearing" review of approval if you'd like, we're aiming for 11/33 members of rust-embedded/all, as it's been more than a week as per https://github.com/rust-embedded/wg/blob/master/rfcs/0206-voting-majority.md)

@sirhcel
sirhcel self-requested a review October 21, 2025 18:50

@Emilgardis Emilgardis left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jamesmunns

Copy link
Copy Markdown
Member

@adamgreig or @therealprof we have at least 11 votes, including the ones that are "sounds great" but are not green checks. I believe we can merge this and count it as approved. (pinging you two to press the button wearing your official core team hats :) )

@adamgreig
adamgreig merged commit e9d78bc into rust-embedded:master Oct 22, 2025
@sgued sgued mentioned this pull request Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.