All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"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>
Subject: Re: [PATCH v5 0/4] docs/devel, AGENTS.md: a completely new policy on AI-generated contributions
Date: Wed, 18 Nov 2026 08:49:20 -0500	[thread overview]
Message-ID: <20261118084905-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20261118104150.599535-1-pbonzini@redhat.com>

On Wed, Nov 18, 2026 at 11:41:46AM +0100, Paolo Bonzini wrote:
> In preparation for the next community call, here is another version of
> the new AI policy.  Discussion after v4 centered on two points, namely
> large contributions and cross-subsystem changes.  In order to facilitate
> reaching a consensus, I am splitting the part about larger contributions
> to a separate commit that can or cannot be included.
> 
> I will leave out from the cover letter the blurb on why reviewing the
> policy and the benefits/risks that it entails.  As before, the change
> seeks to ensure clarity on the part of contributors, and to have AI usage
> that helps us produce better code rather than flood us with dubious work.
> 
> Trying to split out large contributions made me realize how hard it is
> for such a policy to be balanced.  In my opinion, the version that
> does *not* allow large contributions makes the job harder for
> maintainers, because it does not provide a sanctioned way to grow
> a steady stream of small but useful contributions into something more
> structured.  I've tried to put my thoughts in the commit message of
> patch 4, which also covers cross-subsystem changes.
> 
> As before, the patches introduce agent instructions that help the
> contributor drive the design and understand the code produced by the LLM;
> the instructions are also split into "no large changes allowed" and
> "large changes allowed" parts.
> 
> I chose to move the Reviewed-by tags to the *last* patch, including the
> large contributions part, since that is effectively the version that was
> reviewed.
> 
> Paolo


Reviewed-by: Michael S. Tsirkin <mst@redhat.com>

> v4->v5:
> - "AGENTS.md: add final instructions" already merged
> - fix rST syntax
> - section "No automated posting" in AGENTS.md revised and expanded;
>   same for the "official project agents" exception in the policy
> - "``AI-used-for`` must not be included unless some part of the patch
>   *content* was authored by the AI" added explicitly
> - disclosure required for all non-trivial, functional code changes,
>   even if only a small part of a larger patch
> - "docs/devel: allow larger contributions with pre-arrangement" split
> - minor wording changes, mostly to allow separating patch 4
> 
> Paolo Bonzini (4):
>   docs/devel: relax policy on AI-generated contributions
>   AGENTS.md: let agents know what the participation rules are
>   AGENTS.md: make the human part of the design process
>   docs/devel: allow larger contributions with pre-arrangement
> 
>  docs/devel/code-provenance.rst |  71 +----------
>  docs/devel/index-process.rst   |   1 +
>  docs/devel/llm-usage.rst       | 208 +++++++++++++++++++++++++++++++++
>  AGENTS.md                      | 138 +++++++++++++++++++---
>  scripts/checkpatch.pl          |   5 +-
>  5 files changed, 343 insertions(+), 80 deletions(-)
>  create mode 100644 docs/devel/llm-usage.rst
> 
> -- 
> 2.56.0



      parent reply	other threads:[~2026-11-18 13:49 UTC|newest]

Thread overview: 9+ 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é
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 ` Michael S. Tsirkin [this message]

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=20261118084905-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=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.