Repository navigation
Conversation
Documentation build overview
|
|
|
||
| .. _ai-tools-new-contributors: | ||
|
|
||
| Additional rules for new contributors |
There was a problem hiding this comment.
Shouldn't these rules apply to all contributors?
There was a problem hiding this comment.
I want to allow "regular" contributors use of AI because of the trust they built, even if they are neither triagers nor core devs. But I don't want that the first contributions of users is solely AI. But if you want a stronger policy where this applies to everyone, I'm fine as well, though I think it's sad that core devs can't use what the AI generated for them.
It's hard to convene that but informally:
- Newcomers: please don't use AI, you need to prove yourself.
- Others: we can trust your judgment more so you also generate your PRs with AI. But please, make it so that it's not annoying to read.
There was a problem hiding this comment.
I agree that llm-based contributions are annoying, and I agree that we need a way to trust the new contributos and for the new contributors to earn our trust.
But I disagree with this particular approach of creating yet another class of contributors: those who are allowed to use AI and those who are not.
I've been asking myself what I want to know from contributors when they use AI. I still don't have answers or solutions, but these are the things I've been thinking about:I want to know what is their contribution to the PR, did they simply point the agent to the issue and click accept? Did they ask the agent first to explain and clarify? Did they try to verify, replicate, weigh the options from the agents. Did they make any judgement calls, was there a time that they went against the agents recommendations, if so what was that? These are the things that would help me gain trust in the contributor, not the number of PRs they've made and not their status or core dev or not. (I've shared a long form reflection on my personal blog)
First draft of a stricter AI policy for newcomers. Like the other PR, I also used Opus 5.5 for the text and reading the existing parts of the devguide and to polish the tone in a more... diplomatic way I would have said.
I think it grasps my main intent at least: we want newcomers to learn something, not to farm contribution points.