From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alistair Francis" <alistair.francis@wdc.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Fabiano Rosas" <farosas@suse.de>,
"Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Warner Losh" <imp@bsdimp.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 1/4] docs/devel: relax policy on AI-generated contributions
Date: Thu, 19 Nov 2026 12:11:54 +0000 [thread overview]
Message-ID: <av7nikqiy3m-sLPS@redhat.com> (raw)
In-Reply-To: <av3D7Z8UYQBOI2Cp@redhat.com>
On Wed, Nov 18, 2026 at 09:30:04AM -0600, Eric Blake wrote:
> On Wed, Nov 18, 2026 at 11:41:47AM +0100, Paolo Bonzini wrote:
> > Until now QEMU's code provenance policy declined any contribution
> > believed to include or derive from AI-generated content. A blanket ban
> > was easy to maintain while LLM output was rarely usable on its own, but
> > as the tools improved an absolute prohibition has become harder to
> > justify and enforce.
> >
>
> > +LLM-assisted and LLM-created contributions
> > +''''''''''''''''''''''''''''''''''''''''''
> > +
> > +Use of generative AI can be classified in the following four buckets:
>
> This calls out four buckets...
This is a classic trap with itemized lists. Just remove the word 'four',
since there's no need to tell people upfront how many list items to expect.
>
> > +
> > +- "background" assistance, such as completion and code review. This does
> > + not need disclosure.
> > +
> > +- small LLM-assisted bugfixes (as a rule of thumb, below 10 lines of code)
> > + are allowed with disclosure.
> > +
> > +- use of LLMs to help generating parts of a larger patch---test cases,
> > + adaptations of existing code, boilerplate code for a new API, a tool to
> > + help performing mechanical changes, etc. These are generally allowed;
> > + disclosure is required for non-trivial, functional code changes.
> > +
> > +Large, heavily LLM-assisted contributions where LLMs write large parts
> > +of functional code are currently not allowed.
>
> ...but only three bullet points, until the later patches add in a
> fourth bucket. If the entire series goes in, I don't know if it is
> worth the churn of respinning (a slight docs inconsistency when
> bisecting is different than non-working code); but if the consensus is
> to delay the patch for the fourth bucket to a later date, then this
> may need another round of word-smithing.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc.
> Virtualization: qemu.org | libguestfs.org
>
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 :|
next prev parent reply other threads:[~2026-11-19 12:12 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 10:41 [PATCH v5 0/4] docs/devel, AGENTS.md: a completely new policy on AI-generated contributions Paolo Bonzini
2026-11-18 10:41 ` [PATCH 1/4] docs/devel: relax " Paolo Bonzini
2026-11-18 15:30 ` Eric Blake
2026-11-19 12:11 ` Daniel P. Berrangé [this message]
2026-11-18 10:41 ` [PATCH 2/4] AGENTS.md: let agents know what the participation rules are Paolo Bonzini
2026-11-18 10:41 ` [PATCH 3/4] AGENTS.md: make the human part of the design process Paolo Bonzini
2026-11-18 10:41 ` [PATCH 4/4] docs/devel: allow larger contributions with pre-arrangement Paolo Bonzini
2026-11-19 15:31 ` BALATON Zoltan
2026-11-18 13:49 ` [PATCH v5 0/4] docs/devel, AGENTS.md: a completely new policy on AI-generated contributions Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2026-09-30 8:54 [PATCH v4 " Paolo Bonzini
2026-09-30 8:54 ` [PATCH 1/4] docs/devel: relax " Paolo Bonzini
2026-09-30 12:54 ` Philippe Mathieu-Daudé
2026-09-30 12:57 ` Philippe Mathieu-Daudé
2026-09-30 13:09 ` Daniel P. Berrangé
2026-09-30 19:01 ` Paolo Bonzini
2026-09-30 16:14 ` Kevin Wolf
2026-10-01 12:21 ` Peter Maydell
2026-10-02 9:41 ` Paolo Bonzini
2026-10-05 21:09 ` BALATON Zoltan
2026-10-06 8:41 ` Kevin Wolf
2026-10-06 9:44 ` Alex Bennée
2026-10-06 9:56 ` Daniel P. Berrangé
2026-10-06 11:49 ` Kevin Wolf
2026-10-06 13:13 ` Alex Bennée
2026-10-02 14:53 ` Daniel P. Berrangé
2026-10-07 6:00 ` Paolo Bonzini
2026-11-13 10:14 ` Markus Armbruster
2026-11-13 13:09 ` Michael S. Tsirkin
2026-11-18 12:22 ` Paolo Bonzini
2026-11-18 12:54 ` Markus Armbruster
2026-10-27 18:01 ` Alex Bennée
2026-10-27 18:03 ` Paolo Bonzini
2026-10-29 9:34 ` Alex Bennée
2026-11-13 9:44 ` Markus Armbruster
2026-11-17 22:22 ` Paolo Bonzini
2026-11-17 20:40 ` Eric Blake
2026-11-17 21:13 ` Kevin Wolf
2026-11-17 21:31 ` Peter Maydell
2026-11-17 22:20 ` Paolo Bonzini
2026-11-17 21:42 ` BALATON Zoltan
2026-11-17 22:09 ` Philippe Mathieu-Daudé
2026-11-19 14:04 ` BALATON Zoltan
2026-09-21 7:52 [RFC PATCH v3 0/4] docs/devel, AGENTS.md: a completely new " Paolo Bonzini
2026-09-21 7:52 ` [PATCH 1/4] docs/devel: relax " Paolo Bonzini
2026-09-21 9:22 ` Alex Bennée
2026-09-21 14:11 ` Daniel P. Berrangé
2026-09-23 15:52 ` Kevin Wolf
2026-09-21 10:46 ` BALATON Zoltan
2026-09-21 10:57 ` Daniel P. Berrangé
2026-09-21 13:20 ` Daniel P. Berrangé
2026-09-23 16:16 ` Kevin Wolf
2026-09-24 2:23 ` Michael S. Tsirkin
2026-09-24 9:41 ` Kevin Wolf
2026-09-24 16:16 ` Michael S. Tsirkin
2026-09-24 9:29 ` Alex Bennée
2026-09-24 10:46 ` Kevin Wolf
2026-09-24 11:30 ` Daniel P. Berrangé
2026-09-24 21:16 ` Warner Losh
2026-09-25 10:05 ` Kevin Wolf
2026-09-25 11:22 ` Daniel P. Berrangé
2026-09-25 12:20 ` BALATON Zoltan
2026-09-27 9:24 ` Michael S. Tsirkin
2026-09-27 10:03 ` BALATON Zoltan
2026-09-27 16:28 ` Michael S. Tsirkin
2026-09-27 18:05 ` BALATON Zoltan
2026-09-30 16:58 ` Paolo Bonzini
2026-09-24 16:06 ` Michael S. Tsirkin
2026-09-24 18:06 ` Kevin Wolf
2026-09-27 9:20 ` Michael S. Tsirkin
2026-09-28 7:58 ` Kevin Wolf
2026-09-28 8:23 ` Michael S. Tsirkin
2026-09-29 14:23 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=av7nikqiy3m-sLPS@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=balaton@eik.bme.hu \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=imp@bsdimp.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.