From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists1p.gnu.org (lists1p.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CE7C8C9830B for ; Wed, 23 Sep 2026 16:17:08 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1x9Pe1-0007Tn-Ju; Wed, 23 Sep 2026 12:16:29 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1x9Pe0-0007Td-6E for qemu-devel@nongnu.org; Wed, 23 Sep 2026 12:16:28 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1x9Pdy-0003hf-E0 for qemu-devel@nongnu.org; Wed, 23 Sep 2026 12:16:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1790180184; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6ICqM+S022EIe6oxaWs4EOYGV+pkThE1kGyKEKfbgpo=; b=N4lFQI0WpmtTtJp1QInazNoq6cIUy1V8cOlUDmbnSzDgsupO9lHqyqGasQSEMCC/A+0PnU p5vJhtnxgxrH+u7EJMdxyRlA67sELsaIkJf8uvhSMX0KZoc8uxyg0+dGflv5LSpn/LpikO gLS13Bn5nAH1T7PDeY5+02+yH4DM2Yg= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-94-wwm-CHEaNOqccL2hHtiSRw-1; Wed, 23 Sep 2026 12:16:20 -0400 X-MC-Unique: wwm-CHEaNOqccL2hHtiSRw-1 X-Mimecast-MFC-AGG-ID: wwm-CHEaNOqccL2hHtiSRw_1790180178 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 6BA271809CBB; Wed, 23 Sep 2026 16:16:18 +0000 (UTC) Received: from redhat.com (unknown [10.44.48.191]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id DD9CB19539A7; Wed, 23 Sep 2026 16:16:14 +0000 (UTC) Date: Wed, 23 Sep 2026 18:16:12 +0200 From: Kevin Wolf To: Daniel =?iso-8859-1?Q?P=2E_Berrang=E9?= Cc: Paolo Bonzini , qemu-devel@nongnu.org, "Michael S . Tsirkin" , Alex =?iso-8859-1?Q?Benn=E9e?= , Alistair Francis , BALATON Zoltan , Fabiano Rosas , Peter Maydell , Warner Losh , Philippe =?iso-8859-1?Q?Mathieu-Daud=E9?= Subject: Re: [PATCH 1/4] docs/devel: relax policy on AI-generated contributions Message-ID: References: <20260921075251.12831-1-pbonzini@redhat.com> <20260921075251.12831-2-pbonzini@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 Received-SPF: pass client-ip=170.10.133.124; envelope-from=kwolf@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Am 21.09.2026 um 15:20 hat Daniel P. Berrangé geschrieben: > On Mon, Sep 21, 2026 at 09:52:48AM +0200, Paolo Bonzini wrote: > > +.. note:: **Use of AI does not remove the need for authors to comply > > + with all other requirements for contribution.** In particular, > > + the ``Signed-off-by`` label in a patch submission is a statement > > + that the author takes responsibility for the entire contents of > > + the patch, certifying that their patch submission is made in > > + accordance with the rules of the :ref:`Developer's Certificate of > > + Origin (DCO) `. > > + > > + Since a submitter cannot audit LLM output against its training > > + data, the DCO is paired with :ref:`metadata in the commit message > > + ` about AI-generated parts. The DCO still certifies > > + that the contributor has the legal right to submit code in general. > > I'm not a fan of this second paragraph, as that feels like it is undermining > the DCO. That first sentence in particular is somewhat saying that the > contributor does not have to think about plagarism and thed project is ok > with that, and also implying that the DCO doesn't apply to the LLM output. > This is both not OK in its implication of the project accepting some > liability, and then also contradicted by the next sentence. > > IMHO this paragraph should just be removed. The first paragraph clearly > states the DCO applies to the submission as a whole, and leaves all liability > for infringement on the contributor. I don't think making this the individual contributor's problem is great. It's rather unfriendly towards contributors to expect them to certify something that we all know they can't honestly certify. Our current AI policy was built on the assertion that it's impossible to sign the DCO for AI output, and I think that's still right. A developer can't certify the origin of something when they don't really know where it comes from. If we decide that we don't care as much about the legal risks any more and that we're willing to accept them to some extent, that should be explicitly reflected in the policy. It seems to me that the cleanest way to do it is to exempt correctly advertised (with 'AI-used-for:') AI output from the DCO requirement and instead add to the 'AI-used-for:' definition some relaxed version of it, e.g. "I have reviewed the contribution for potential licensing issues and haven't found a reason to doubt that I have the rights to submit this AI generated content under the open source license indicated in the file". This is something that could realistically be certified by contributors in good faith and also isn't just "anything goes", but of course it still is weaker than the DCO. If we're not willing to take the legal risk from this, we should probably leave the current AI policy unchanged instead of telling contributors that they have to work in a legal grey area. Kevin