From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
"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 2/4] AGENTS.md: Let agents know what the participation rules are
Date: Wed, 2 Sep 2026 14:47:57 +0100 [thread overview]
Message-ID: <apgpDaBqCaVPqmLH@redhat.com> (raw)
In-Reply-To: <87a4pzrcqw.fsf@draig.linaro.org>
On Wed, Sep 02, 2026 at 02:42:15PM +0100, Alex Bennée wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > Humans seem to be extremely unreliable in following rules around this,
> > even after being told directly and repeatedly. Telling agents what to
> > do seems to yield better results.
> >
> > This document is based on GStreamer's AGENTS.md file, as of its commit
> > d08375499c279a56c0e77c928fbeae0d80cdf937. However, GStreamer's agent
> > instructions are "effective" enough to require an explicit carve-out
> > for maintainers. I actually believe that such a carve-out is a sign of
> > going too far, especially given the good quality of some suspected-AI
> > contributions we've received.
> >
> <snip>
> > diff --git a/AGENTS.md b/AGENTS.md
> > new file mode 100644
> > index 00000000000..8fb96ebfc38
> > --- /dev/null
> > +++ b/AGENTS.md
> > @@ -0,0 +1,100 @@
> > +# Agent Guidelines for the QEMU Project
> > +
> > +QEMU is a cross-platform emulator and virtualizer. Due to the complexity
> > +of the domain and codebase, and the interactions therein, the QEMU
> > +project relies extensively on the effort of **human reviewers**, which
> > +is **a scarce resource**.
> > +
> > +There are strictly-enforced rules for you, the agent, to participate in the
> > +project.
> > +
> > +## Interactions with maintainers must be human-human
> > +
> > +The QEMU project has strict rules on what AI-generated material can
> > +reach the maintainers.
> > +
> > +### No automated posting
> > +
> > +- Agents **must not** use any API, CLI, or web UI automation to:
> > + - Interact with the QEMU mailing lists
> > + - Create, edit, or close **issues ("work items")**
>
> The others I'm fine with but I currently use an agent to do triage on
> un-tagged issues. It only updates labels and occasionally posts a
> comment when more information or a human input is required.
While this is technically something you're doing via your personal
gitlab account, I none the less view the agent triage bot as something
run as an "official" project service.
IMHO the AGENTS.md policy primarily applies to actions done in an
individual capacity (whether contributor or maintainer).
If the project wants to deploy project level services that utilize
AI in some manner and that conflicts with AGENTS.md that's acceptable,
provided we discuss & agree that the project service in question is
desirable.
Perhaps this is me saying that the issue triage bot should be made
more official as a service, committed to git, etc
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-09-02 13:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 16:14 [RFC PATCH v2 0/4] docs/devel, AGENTS.md: a completely new policy on AI-generated contributions Paolo Bonzini
2026-09-01 16:14 ` [PATCH 1/4] docs/devel: introduce a " Paolo Bonzini
2026-09-02 1:38 ` Alistair Francis
2026-09-02 7:09 ` Paolo Bonzini
2026-09-02 9:41 ` Michael S. Tsirkin
2026-09-02 10:08 ` Daniel P. Berrangé
2026-09-02 12:01 ` Peter Maydell
2026-09-03 1:39 ` Alistair Francis
2026-09-03 7:09 ` Paolo Bonzini
2026-09-02 16:09 ` Daniel P. Berrangé
2026-09-03 10:05 ` Paolo Bonzini
2026-09-01 16:14 ` [PATCH 2/4] AGENTS.md: Let agents know what the participation rules are Paolo Bonzini
2026-09-02 1:44 ` Alistair Francis
2026-09-02 16:26 ` Daniel P. Berrangé
2026-09-02 17:45 ` Paolo Bonzini
2026-09-02 13:42 ` Alex Bennée
2026-09-02 13:47 ` Daniel P. Berrangé [this message]
2026-09-02 13:56 ` Michael S. Tsirkin
2026-09-02 14:08 ` Daniel P. Berrangé
2026-09-02 15:15 ` Michael S. Tsirkin
2026-09-02 13:48 ` Michael S. Tsirkin
2026-09-01 16:14 ` [PATCH 3/4] AGENTS.md: make the human part of the design process Paolo Bonzini
2026-09-02 1:44 ` Alistair Francis
2026-09-01 16:14 ` [PATCH 4/4] agents: add CLAUDE.md and GEMINI.md Paolo Bonzini
2026-09-02 1:47 ` Alistair Francis
2026-09-02 4:45 ` Philippe Mathieu-Daudé
2026-09-02 9:46 ` Michael S. Tsirkin
2026-09-02 9:56 ` Paolo Bonzini
2026-09-02 10:06 ` Michael S. Tsirkin
2026-09-02 10:12 ` Daniel P. Berrangé
2026-09-02 13:04 ` Michael S. Tsirkin
2026-09-02 14:30 ` Paolo Bonzini
2026-09-02 15:54 ` [RFC PATCH v2 0/4] docs/devel, AGENTS.md: a completely new policy on AI-generated contributions Peter Maydell
2026-09-02 17:50 ` Alex Bennée
2026-09-03 11:29 ` BALATON Zoltan
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=apgpDaBqCaVPqmLH@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=balaton@eik.bme.hu \
--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.