On 2025-06-30 at 20:32:22, Junio C Hamano wrote: > Following the example set by QEMU folks, let's explicitly forbid use > of genAI tools until the copyright and license situations become > more clear. Here is what QEMU folks say in their commit to adopt > such a rule: > > The DCO requires contributors to assert they have the right to > contribute under the designated project license. Given the lack > of consensus on the licensing of AI code generator output, it is > not considered credible to assert compliance with the DCO clause > (b) or (c) where a patch includes such generated code. > > and it applies equally well to ours. > > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- > Documentation/SubmittingPatches | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git c/Documentation/SubmittingPatches w/Documentation/SubmittingPatches > index 958e3cc3d5..63fd10ce39 100644 > --- c/Documentation/SubmittingPatches > +++ w/Documentation/SubmittingPatches > @@ -439,6 +439,23 @@ highlighted above. > Only capitalize the very first letter of the trailer, i.e. favor > "Signed-off-by" over "Signed-Off-By" and "Acked-by:" over "Acked-By". > > + > +[[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. > + > +Hence, the project asks that contributors refrain from using AI content > +generators on changes that are submitted to the project. > +Contributions in which use of AI is either known or suspected may not > +be accepted. This matches the advice we gave contributors to GSOC and similar projects, so it's good that we're being consistent here. I think this seems prudent given the fact that there are 181 signatories to the Berne Convention and even if the courts rule that the use of generative AI is acceptable in one country (say, the United States), it isn't clear that that will mean anything in other countries (such as Canada). Considering that there's ongoing litigation and quite a bit of legal uncertainty, as well as substantial pushback on generative AI from the open source community, this approach seems like it's in the best interests of the project at the moment[0]. We can always reconsider in the future if need be. I'll note that this was my interpretation of the DCO from the start (and I have governed my behaviour and contributions accordingly) but it can be helpful to explicitly document our shared understanding. One style note: I noticed that there's two blank lines before and after this block. Some sections have one blank line between them and some have two, so I don't think this is a problem, but I thought I might as well point it out. [0] I know some large companies feel differently, but considering our status as a member project of Conservancy (which is a non-profit), our comparatively limited assets, and the potential negative legal effects on downstream distributors (many of which are independent people or non-profits), I would say we find ourselves in a different position from those companies and would need to make a different decision. -- brian m. carlson (they/them) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
