From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"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 v3 0/3] docs: define policy forbidding use of "AI" / LLM code generators
Date: Tue, 3 Jun 2025 17:25:33 +0200 [thread overview]
Message-ID: <aD8T7RSDofG0TNCK@redhat.com> (raw)
In-Reply-To: <20250603142524.4043193-1-armbru@redhat.com>
Am 03.06.2025 um 16:25 hat Markus Armbruster geschrieben:
> More than a year ago, Daniel posted patches to put an AI policy in
> writing. Reception was mostly positive. A v2 to address feedback
> followed with some delay. But no pull request.
>
> I asked Daniel why, and he told me he was concerned it might go too
> far in its interpretation of the DCO requirements. After a bit of
> discussion, I think Daniel's text is basically fine. The policy it
> describes is simple and strict. Relaxing policy is easier than
> tightening it. I softened the phrasing slightly, addressed open
> review comments, and fixed a few minor things I found myself.
>
> [...]
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
prev parent reply other threads:[~2025-06-03 15:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:25 [PATCH v3 0/3] docs: define policy forbidding use of "AI" / LLM code generators Markus Armbruster
2025-06-03 14:25 ` [PATCH v3 1/3] docs: introduce dedicated page about code provenance / sign-off Markus Armbruster
2025-06-03 16:53 ` Alex Bennée
2025-06-04 6:44 ` Markus Armbruster
2025-06-04 7:18 ` Daniel P. Berrangé
2025-06-04 7:46 ` Philippe Mathieu-Daudé
2025-06-04 8:52 ` Markus Armbruster
2025-06-05 9:04 ` Markus Armbruster
2025-06-04 7:58 ` Gerd Hoffmann
2025-06-05 14:52 ` Markus Armbruster
2025-06-05 15:07 ` Alex Bennée
2025-06-03 14:25 ` [PATCH v3 2/3] docs: define policy limiting the inclusion of generated files Markus Armbruster
2025-06-03 14:25 ` [PATCH v3 3/3] docs: define policy forbidding use of AI code generators Markus Armbruster
2025-06-03 15:37 ` Kevin Wolf
2025-06-04 6:18 ` Markus Armbruster
2025-06-03 18:25 ` Stefan Hajnoczi
2025-06-04 6:17 ` Markus Armbruster
2025-06-04 7:15 ` Daniel P. Berrangé
2025-06-04 7:54 ` Philippe Mathieu-Daudé
2025-06-04 8:40 ` Daniel P. Berrangé
2025-06-04 9:19 ` Philippe Mathieu-Daudé
2025-06-04 9:04 ` Markus Armbruster
2025-06-04 8:58 ` Markus Armbruster
2025-06-04 9:22 ` Daniel P. Berrangé
2025-06-04 9:40 ` Markus Armbruster
2025-06-04 12:35 ` Yan Vugenfirer
2025-06-04 9:10 ` Daniel P. Berrangé
2025-06-04 11:01 ` Stefan Hajnoczi
2025-06-03 15:25 ` Kevin Wolf [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=aD8T7RSDofG0TNCK@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@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).