git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] SubmittingPatches: forbid use of genAI to generate changes

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2025, 16:20 UTC
Message-ID
<xmqqms9nkhms.fsf@gitster.g>
In-Reply-To
<CAP8UFD0bd1PD03VPaenAd+76Q6CeCOmDOJsso1nMKk4tZ4vbMg@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 16 quoted lines
>> +
>> +[[ai]]
>> +=== Use of AI content generators
>> +
>> +This project requires that contributors certify that their
>> +contributions are made under Developer's Certificate of Origin 1.1,
>> +which in turn means that contributors must understand the full
>> +provenance of what they are contributing.  With AI content generators,
>> +the copyright or license status of their output is ill-defined, without
>> +any generally accepted legal foundation.
>
> Here we would forbid licensing any "AI content generator" output, not
> just AI code generator output. So what we would forbid might be more
> general than what QEMU folks forbid. For example they might still
> accept a new logo, or even commit messages, made using an AI while we
> wouldn't.

I didn't think about the distinction you are trying to draw when I wrote the patch, but after thinking about it, I think it is a good thing to prevent us from adopting a new logo graphics somebody may have ownership rights without us knowing. I would consider the commit log message as an integral part of any "contribution", and read the word "contribution" used in the [[dco]] section as such, if the rule covers the commit log message, that is very much appreciated.

Show 6 quoted lines
>> +Hence, the project asks that contributors refrain from using AI content
>> +generators on changes that are submitted to the project.
>
> Here it looks like using an AI capable of generating content to just
> check code that would be submitted could also be forbidden. I don't
> think this is what we want, so I think we might want to reword this.

Good point. Asking agents to proofread and suggest improvements is like asking your friends to do so. Care to suggest replacement to these two sentences (above and below)?

>> +Contributions in which use of AI is either known or suspected may not
>> +be accepted.
>
> Here also "use of AI" might forbid checking what we submit using any AI tool.
Thanks.
Previous: Junio C HamanoNext: Christian Couder
Message 7 of 34 in “SubmittingPatches: forbid use of genAI to generate changes”
  1. SubmittingPatches: forbid use of genAI to generate changesJunio C Hamano, Jun 30, 2025
  2. brian m. carlsonJun 30, 2025
  3. Collin FunkJun 30, 2025
  4. Christian CouderJul 1, 2025
  5. Christian CouderJul 1, 2025
  6. Junio C HamanoJul 1, 2025
  7. Junio C HamanoJul 1, 2025
  8. Christian CouderJul 8, 2025
  9. SubmittingPatches: add section about AIChristian Couder, Oct 1, 2025
  10. Chuck WolberOct 1, 2025
  11. brian m. carlsonOct 1, 2025
  12. Ben KnobleOct 2, 2025
  13. Christian CouderOct 3, 2025
  14. Junio C HamanoOct 1, 2025
  15. Christian CouderOct 3, 2025
  16. Junio C HamanoOct 3, 2025
  17. rsbecker@nexbridge.comOct 3, 2025
  18. Christian CouderOct 8, 2025
  19. brian m. carlsonOct 1, 2025
  20. Christian CouderOct 3, 2025
  21. Elijah NewrenOct 3, 2025
  22. brian m. carlsonOct 3, 2025
  23. Junio C HamanoOct 6, 2025
  24. Elijah NewrenOct 8, 2025
  25. Junio C HamanoOct 12, 2025
  26. Christian CouderOct 8, 2025
  27. Junio C HamanoOct 13, 2025
  28. Junio C HamanoOct 23, 2025
  29. Elijah NewrenOct 8, 2025
  30. Christian CouderOct 8, 2025
  31. Michal SuchánekOct 8, 2025
  32. Christian CouderOct 8, 2025
  33. Collin FunkOct 9, 2025
  34. Christian CouderOct 8, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.