doc: contributing: document AI usage policy - #571
Conversation
yaakov-stein
left a comment
yaakov-stein
left a comment
There was a problem hiding this comment.
My main thought is that we may care less about AI usage and more about quality and an author willing to stand behind the work + deeply understand what they are sending. If that is the case, then it may make more sense to focus more on the rules that are in line with ensuring quality. But either way, this is more of a nit and the current change LGTM
|
|
||
| **Follow the style guide.** Formatting is enforced by ``.clang-format``, the rest is in :doc:`style`, and commits use ``component: subcomponent: short description``. Ignoring the style after it's been pointed out tells me the same thing an untested diff does: nobody looked. | ||
|
|
||
| **Say if you used AI.** A line in the PR is enough ("AI-drafted the tests and description, wrote the code by hand"). "None" is a fine answer. I may ask, so just be straight about it. Undisclosed AI is one of the things that gets a PR closed with a link to this page. |
There was a problem hiding this comment.
If the PR is tested well, summary is clear, concise, and high-value, and the code is well-written and not overly verbose - is it really important to disclose AI usage?
Also, if it is purely based on an AI disclosure, how do we prevent garbage AI PR's where the author lies about AI usage?
There was a problem hiding this comment.
If the PR is tested well, summary is clear, concise, and high-value, and the code is well-written and not overly verbose - is it really important to disclose AI usage?
I think it would be worth it anyway, as it could give us hints about the whether there's a human involved or not. This requirement can be dropped for trusted (for some definition of "trusted") contributors.
Also, if it is purely based on an AI disclosure, how do we prevent garbage AI PR's where the author lies about AI usage?
Some people will lie anyway, but it could make our life easier: em dashes in the commit message + "I didn't use AI at all" would be a solid ground to close the PR.
Move the content of CONTRIBUTING.md into the developer documentation so it lives on a single page, and reduce CONTRIBUTING.md to a link to it. Add a policy on AI-assisted contributions: AI is welcome, but authors must understand, build, and test what they submit, and disclose AI usage in the PR. Add a pull request template enforcing the same expectations, and restore the security disclosure instructions as a dedicated section.
176c930 to
184493d
Compare
2 participants
Move the content of CONTRIBUTING.md into the developer documentation so it lives on a single page, and reduce CONTRIBUTING.md to a link to it. Add a policy on AI-assisted contributions: AI is welcome, but authors must understand, build, and test what they submit, and disclose AI usage in the PR. Add a pull request template enforcing the same expectations, and restore the security disclosure instructions as a dedicated section.