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 C4C8FCD98E4 for ; Tue, 16 Jun 2026 17:44:53 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1wZXpy-0002ni-Hk; Tue, 16 Jun 2026 13:44:34 -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 1wZXpx-0002mx-7m for qemu-devel@nongnu.org; Tue, 16 Jun 2026 13:44:33 -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 1wZXpv-0007ze-3X for qemu-devel@nongnu.org; Tue, 16 Jun 2026 13:44:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1781631870; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=ukacI6sGNmTj6VNIbx+kadlWWmfzzm+xNHrpd+2EMHo=; b=PUXpLNwiK31Lv8PuPKgAw9PpP6eeaxsx8OAWN9CNwPDKCsO0JvYW9dVkfi84B1Xe8QnPvM f5t4xoy70G1R7amvVoBcUjSopFFxDC6ZpEuNrlV26oDti9eXTfYPpIFu0OBnYGgPHh3at+ kzXswonXAW7cxJJsCqHFZ+7tA00sMhA= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-538-H5776DK9OyCZ-7mdXSyZag-1; Tue, 16 Jun 2026 13:44:27 -0400 X-MC-Unique: H5776DK9OyCZ-7mdXSyZag-1 X-Mimecast-MFC-AGG-ID: H5776DK9OyCZ-7mdXSyZag_1781631865 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (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-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id C2FE51955DBB; Tue, 16 Jun 2026 17:44:24 +0000 (UTC) Received: from redhat.com (unknown [10.44.49.111]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id C27AA19560A2; Tue, 16 Jun 2026 17:44:19 +0000 (UTC) Date: Tue, 16 Jun 2026 18:44:16 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Christian Borntraeger Cc: Paolo Bonzini , qemu-devel@nongnu.org, "Michael S. Tsirkin" , Alex =?utf-8?Q?Benn=C3=A9e?= , Alistair Francis , BALATON Zoltan , Fabiano Rosas , Kevin Wolf , Peter Maydell , Warner Losh , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , Paolo Bonzini Subject: Re: [PATCH v2] docs/devel: relax policy on AI-generated contributions Message-ID: References: <20260529094619.1034458-1-pbonzini@redhat.com> <9ad69343-38b5-449c-8d7b-5cbde9d3b72f@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <9ad69343-38b5-449c-8d7b-5cbde9d3b72f@linux.ibm.com> User-Agent: Mutt/2.3.2 (2026-04-26) X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: 8 X-Spam_score: 0.8 X-Spam_bar: / X-Spam_report: (0.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.445, 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_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no 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: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Tue, Jun 16, 2026 at 07:06:23PM +0200, Christian Borntraeger wrote: > Am 29.05.26 um 11:46 schrieb Paolo Bonzini: > > -Exceptions do 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, including any parts > > -that were generated or assisted by AI tools or other tools. > > +.. code-block:: none > > + > > + AI-used-for: tests, docs > > + AI-used-for: code > > + AI-used-for: code (refactoring) > > + AI-used-for: code (prototype) > > + AI-used-for: research > > + > > +``AI-used-for`` should not be included for "background" usage such as > > +autocomplete or obtaining a pre-review of the patch. > > So what about using AI for security scanning? So how do we want to treat > a patch from a human that is based on an AI report. > And if ok, would we then add something like > > Reported-by: Claude, chatgpt whatever? I see no need to provide advertizing for these tools. Our security disclosure rules require that the submitter acknowledge they have reviewed any LLM output themselves before reporting. So from that POV it is the human who gave us the report and whom deserves the credit, not any tool or vendor. FWIW, although pretty much every security report recently smells strongly of LLM (highly structured markdown with headings that look the same from all reporters), almost none of them credit the specific tool used anyway. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|