From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Alexander Graf" <agraf@csgraf.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v5 3/3] docs: define policy forbidding use of AI code generators
Date: Thu, 26 Jun 2025 08:56:29 +0100 [thread overview]
Message-ID: <aFz9LT0r6aPVK3hn@redhat.com> (raw)
In-Reply-To: <20250626023413-mutt-send-email-mst@kernel.org>
On Thu, Jun 26, 2025 at 02:34:57AM -0400, Michael S. Tsirkin wrote:
> On Mon, Jun 16, 2025 at 11:22:41AM +0200, Markus Armbruster wrote:
> > +The QEMU project thus requires that contributors refrain from using AI content
> > +generators on patches intended to be submitted to the project, and will
> > +decline any contribution if use of AI is either known or suspected.
>
> What is this suspected thing by the way? Suspected by whom? You do not
> think this is draconian?
Suspected as in, as a reviewer you see obvious signs of LLM slop and
or hallucinations in the contributions, while the contributor has not
declared such.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-06-26 7:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 9:22 [PATCH v5 0/3] docs: define policy forbidding use of "AI" / LLM code generators Markus Armbruster
2025-06-16 9:22 ` [PATCH v5 1/3] docs: introduce dedicated page about code provenance / sign-off Markus Armbruster
2025-06-16 9:22 ` [PATCH v5 2/3] docs: define policy limiting the inclusion of generated files Markus Armbruster
2025-06-16 9:22 ` [PATCH v5 3/3] docs: define policy forbidding use of AI code generators Markus Armbruster
2025-06-25 19:16 ` Michael S. Tsirkin
2025-06-25 19:46 ` Daniel P. Berrangé
2025-06-25 20:01 ` Michael S. Tsirkin
2025-06-26 10:41 ` Markus Armbruster
2025-06-25 20:38 ` Kevin Wolf
2025-06-25 20:45 ` Michael S. Tsirkin
2025-06-25 20:47 ` Stefan Hajnoczi
2025-06-25 20:49 ` Michael S. Tsirkin
2025-06-26 8:18 ` Daniel P. Berrangé
2025-06-26 8:38 ` Michael S. Tsirkin
2025-06-26 6:34 ` Michael S. Tsirkin
2025-06-26 7:56 ` Daniel P. Berrangé [this message]
2025-06-23 19:30 ` [PATCH v5 0/3] docs: define policy forbidding use of "AI" / LLM " Stefan Hajnoczi
2025-06-23 22:25 ` Alex Bennée
2025-06-24 5:02 ` Markus Armbruster
2025-06-24 10:41 ` Stefan Hajnoczi
2025-06-24 17:33 ` Stefan Hajnoczi
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=aFz9LT0r6aPVK3hn@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).