Skip to content

Commit 7b0c379

Browse files
chriscoolgitster
authored andcommitted
SubmittingPatches: add section about AI
As more and more developer tools use AI, we are facing two main risks related to AI generated content: - its situation regarding copyright and license is not clear, and: - more and more bad quality content could be submitted for review to the mailing list. To mitigate both risks, let's add an "Use of Artificial Intelligence" section to "Documentation/SubmittingPatches" with the goal of discouraging its blind use to generate content that is submitted to the project, while still allowing us to benefit from its help in some innovative, useful and less risky ways. Helped-by: Rick Sanders <rick@sfconservancy.org> Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 821f583 commit 7b0c379

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

Documentation/SubmittingPatches

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -446,6 +446,34 @@ highlighted above.
446446
Only capitalize the very first letter of the trailer, i.e. favor
447447
"Signed-off-by" over "Signed-Off-By" and "Acked-by:" over "Acked-By".
448448

449+
[[ai]]
450+
=== Use of Artificial Intelligence (AI)
451+
452+
The Developer's Certificate of Origin requires contributors to certify
453+
that they know the origin of their contributions to the project and
454+
that they have the right to submit it under the project's license.
455+
It's not yet clear that this can be legally satisfied when submitting
456+
significant amount of content that has been generated by AI tools.
457+
458+
Another issue with AI generated content is that AIs still often
459+
hallucinate or just produce bad code, commit messages, documentation
460+
or output, even when you point out their mistakes.
461+
462+
To avoid these issues, we will reject anything that looks AI
463+
generated, that sounds overly formal or bloated, that looks like AI
464+
slop, that looks good on the surface but makes no sense, or that
465+
senders don’t understand or cannot explain.
466+
467+
We strongly recommend using AI tools carefully and responsibly.
468+
469+
Contributors would often benefit more from AI by using it to guide and
470+
help them step by step towards producing a solution by themselves
471+
rather than by asking for a full solution that they would then mostly
472+
copy-paste. They can also use AI to help with debugging, or with
473+
checking for obvious mistakes, things that can be improved, things
474+
that don’t match our style, guidelines or our feedback, before sending
475+
it to us.
476+
449477
[[git-tools]]
450478
=== Generate your patch using Git tools out of your commits.
451479

0 commit comments

Comments
 (0)