From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Alistair Francis" <alistair.francis@wdc.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"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>,
"Paolo Bonzini" <bonzini@gnu.org>
Subject: Re: [PATCH v2] docs/devel: relax policy on AI-generated contributions
Date: Fri, 29 May 2026 09:10:34 -0400 [thread overview]
Message-ID: <20260529090830-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <224a940c-2f6e-4d5f-8c91-0107d19b82b2@redhat.com>
On Fri, May 29, 2026 at 03:06:54PM +0200, Paolo Bonzini wrote:
> On 5/29/26 13:52, Alex Bennée wrote:
> > > - **Current QEMU project policy is to DECLINE any contributions which are
> > > - believed to include or derive from AI generated content. This includes
> > > - ChatGPT, Claude, Copilot, Llama and similar tools.**
> > > + Please read the below policy before using AI to contribute code or
> > > + documentation to QEMU. This applies to ChatGPT, Claude, Copilot,
> > > + Llama, and similar tools.**
> >
> > Stray **, also extra space after QEMU.
>
> Will fix the stars (extra space is intentional, though it shows my age. I
> still find that it reads better on monospace fonts to have two spaces at the
> end of the sentence).
>
> > > +**Mechanical changes**
> > > + If you can use a deterministic tool, it is preferred that you use
> >
> > deterministic tool or script,?
>
> Sure.
>
> > In my v2 I added:
> >
> > AI tools **should not be used to write commit messages**. The act of
> > summarising and explaining the reasoning for the changes is an
> > important demonstration of the human authors understanding of the
> > commit.
>
> While I didn't include this, v2 links to the "how to write a commit message"
> paragraph elsewhere in the documentation. I don't want it to look like
> people can't even ask for copy-editing of commit messages.
> Paolo
And maybe "It is ok to ask an AI tool to correct grammar and spelling in
your text, as long as you are not asking it to write it".
next prev parent reply other threads:[~2026-05-29 13:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 9:46 [PATCH v2] docs/devel: relax policy on AI-generated contributions Paolo Bonzini
2026-05-29 11:52 ` Alex Bennée
2026-05-29 13:06 ` Paolo Bonzini
2026-05-29 13:10 ` Michael S. Tsirkin [this message]
2026-05-29 11:59 ` BALATON Zoltan
2026-05-29 15:34 ` Peter Maydell
2026-05-29 15:46 ` Michael S. Tsirkin
2026-05-29 15:55 ` Peter Maydell
2026-05-29 16:17 ` Paolo Bonzini
2026-05-29 17:47 ` Michael S. Tsirkin
2026-06-02 7:38 ` Michael S. Tsirkin
2026-06-02 8:09 ` Paolo Bonzini
2026-06-02 15:53 ` Stefan Hajnoczi
2026-06-03 11:35 ` Paolo Bonzini
2026-06-03 14:55 ` Stefan Hajnoczi
2026-06-03 14:59 ` Daniel P. Berrangé
2026-06-03 15:06 ` Michael S. Tsirkin
2026-06-03 15:35 ` Paolo Bonzini
2026-06-03 17:54 ` Daniel P. Berrangé
2026-06-04 10:37 ` Paolo Bonzini
2026-06-05 9:17 ` Daniel P. Berrangé
2026-06-05 9:25 ` Michael S. Tsirkin
2026-06-05 9:39 ` Daniel P. Berrangé
2026-06-05 9:48 ` Michael S. Tsirkin
2026-06-05 10:23 ` Daniel P. Berrangé
2026-06-05 10:28 ` Michael S. Tsirkin
2026-06-05 10:34 ` Daniel P. Berrangé
2026-06-05 11:26 ` Paolo Bonzini
2026-06-05 12:39 ` BALATON Zoltan
2026-06-05 13:00 ` Daniel P. Berrangé
2026-06-03 18:14 ` Alex Bennée
2026-06-03 18:20 ` Daniel P. Berrangé
2026-06-04 10:04 ` Alex Bennée
2026-06-04 6:08 ` Michael S. Tsirkin
2026-06-05 10:12 ` Kevin Wolf
2026-06-05 10:23 ` Michael S. Tsirkin
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=20260529090830-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=balaton@eik.bme.hu \
--cc=berrange@redhat.com \
--cc=bonzini@gnu.org \
--cc=farosas@suse.de \
--cc=imp@bsdimp.com \
--cc=kwolf@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.