Re: [PATCH v2] SubmittingPatches: add section about AI

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 13, 2025, 18:14 UTC
Message-ID: <xmqqv7ki1xf1.fsf@gitster.g>
In-Reply-To: <CAP8UFD1Bc0bRdty9O0et9T=UL9FtN-g_K3DYUmHUR31waTQ+GQ@mail.gmail.com>

Christian Couder <christian.couder@gmail.com> writes:

Show 11 quoted lines

> On Mon, Oct 6, 2025 at 7:45 PM Junio C Hamano <gitster@pobox.com> wrote:
>
>> OK, so here is theirs for further discussion minimally adjusted for
>> our use.  I do not see much difference at least in spirit with what
>> started this thread, but phrasing is certainly firmer, and I have no
>> problem with it.
>
> I don't think it's a good idea to be too firm. It could prevent people
> willing to follow the rules from doing things that are actually
> acceptable while it won't prevent the risks from people not following
> the rules anyway.

Show 7 quoted lines

>> How contributors could comply with DCO terms (b) or (c) for the output of AI
>> content generators commonly available today is unclear.  The Git project is
>> not willing or able to accept the legal risks of non-compliance.
>
> I think this could be understood as if the Git project is responsible
> for contributors submitting content they should not submit. I don't
> think we should go into this.

When the project distributes work that it has no right to distribute, those who claim to be right holders would try to make the project be held responsible for it. It is a different story if the court agrees.

Show 14 quoted lines

> [...]
>
>> This policy does not apply to other uses of AI, such as researching APIs or
>> algorithms, static analysis, or debugging, provided their output is not to be
>> included in contributions.
>
> This is not realistic. If an AI does static analysis for example, it
> is likely to suggest a fix for the issues it finds. Hopefully the fix
> will be the right one, so it will end up being included in the
> contributions.
>
>> Examples of tools impacted by this policy includes GitHub's CoPilot, OpenAI's
>
> s/includes/include/

We are not in the business of typofixing QEMU policy. Send that patch in their direction ;-).

I do not have strong preference either way. Even if the wording is firm, it is really up to each contributor to honor the guideline and be honest with us. You may see autocorrection in your editor fix a typo for you, and more advanced tools may offer to rewrite what you wrote, whether it is prose or code. It is very plausible that, especially for simple fixes, the result may be what the contributor would have arrived on their own anyway, and in such a case, even the contributor would not even know how much came from "AI" or simple dictionary, or if that AI learned with things you should not have seen.

So, I do not think it makes too big a difference in practice whether we adopt the QEMU with minimum rewrite, or the version you posted. As the one you sent is in line with what we give applicants of our mentoring programs, and it was read over by our SFC lawyer, I'd prefer to keep the version I already have in my tree. Not moving on either, I think, is worse than adopting either in this case.

Thanks.