From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Warner Losh" <imp@bsdimp.com>, "Paolo Bonzini" <bonzini@gnu.org>
Subject: Re: [PATCH] docs/devel: relax policy on AI-generated contributions
Date: Thu, 28 May 2026 03:59:38 -0400 [thread overview]
Message-ID: <20260528035815-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CABgObfZwaiu4A2b2EFuFRA4dbWfHrDYEfiq5_-mf+zQpsYfTLQ@mail.gmail.com>
On Thu, May 28, 2026 at 09:53:12AM +0200, Paolo Bonzini wrote:
> On Thu, May 28, 2026 at 9:48 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> > > -How contributors could comply with DCO terms (b) or (c) for the output of AI
> > > -content generators commonly available today is unclear. The QEMU project is
> > > -not willing or able to accept the legal risks of non-compliance.
> > > +If you wish to send large amounts of AI-generated changes, or any other
> > > +contribution not in the above categories, please get in touch with the
> > > +maintainer beforehand.
> >
> > To be clear, the implication is that
> > These can be accepted at the discretion of the maintainer
>
> Yes.
>
> > Maybe make it explicit.
>
> Ok.
>
> > > + AI-used-for: tests, docs
> > > + AI-used-for: code
> > > + AI-used-for: code (refactoring)
> > > + AI-used-for: code (prototype)
> > > + AI-used-for: research
BTW: commit log ?
> > Why include research here when we also explicitly say:
> >
> > > +These boundaries do not apply to other uses of AI, such as researching
> > > +APIs or algorithms, static analysis, or debugging, provided the model's
> > > +output is not included in contributions.
>
> I suppose it can still be useful for traceability. I copied it from
> Kevin's proposal but I can remove it.
>
> "Research" may also include using a script written by the LLM, which
> is encouraged in the first section.
>
> Paolo
but again, if the script is not merged, then the boundaries do not
apply?
--
MST
next prev parent reply other threads:[~2026-05-28 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 7:34 [PATCH] docs/devel: relax policy on AI-generated contributions Paolo Bonzini
2026-05-28 7:40 ` Philippe Mathieu-Daudé
2026-05-28 7:43 ` Paolo Bonzini
2026-05-28 7:50 ` Michael S. Tsirkin
2026-05-28 7:48 ` Michael S. Tsirkin
2026-05-28 7:53 ` Paolo Bonzini
2026-05-28 7:59 ` Michael S. Tsirkin [this message]
2026-05-28 8:04 ` Paolo Bonzini
2026-05-28 8:18 ` Michael S. Tsirkin
2026-05-28 8:26 ` Philippe Mathieu-Daudé
2026-05-28 9:04 ` Alex Bennée
2026-05-28 12:12 ` BALATON Zoltan
2026-05-28 13:45 ` Michael S. Tsirkin
2026-05-28 13:18 ` Fabiano Rosas
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=20260528035815-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=berrange@redhat.com \
--cc=bonzini@gnu.org \
--cc=imp@bsdimp.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@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.