From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel@nongnu.org, "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>,
"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 v3 3/3] docs: define policy forbidding use of AI code generators
Date: Wed, 4 Jun 2025 08:15:47 +0100 [thread overview]
Message-ID: <aD_yhelX-w4Vdm8Z@redhat.com> (raw)
In-Reply-To: <87a56o1154.fsf@pond.sub.org>
On Wed, Jun 04, 2025 at 08:17:27AM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi <stefanha@gmail.com> writes:
>
> > On Tue, Jun 3, 2025 at 10:25 AM Markus Armbruster <armbru@redhat.com> wrote:
> >>
> >> From: Daniel P. Berrangé <berrange@redhat.com>
>> +
> >> +The increasing prevalence of AI code generators, most notably but not limited
> >
> > More detail is needed on what an "AI code generator" is. Coding
> > assistant tools range from autocompletion to linters to automatic code
> > generators. In addition there are other AI-related tools like ChatGPT
> > or Gemini as a chatbot that can people use like Stackoverflow or an
> > API documentation summarizer.
> >
> > I think the intent is to say: do not put code that comes from _any_ AI
> > tool into QEMU.
> >
> > It would be okay to use AI to research APIs, algorithms, brainstorm
> > ideas, debug the code, analyze the code, etc but the actual code
> > changes must not be generated by AI.
The scope of the policy is around contributions we receive as
patches with SoB. Researching / brainstorming / analysis etc
are not contribution activities, so not covered by the policy
IMHO.
>
> The existing text is about "AI code generators". However, the "most
> notably LLMs" that follows it could lead readers to believe it's about
> more than just code generation, because LLMs are in fact used for more.
> I figure this is your concern.
>
> We could instead start wide, then narrow the focus to code generation.
> Here's my try:
>
> The increasing prevalence of AI-assisted software development results
> in a number of difficult legal questions and risks for software
> projects, including QEMU. Of particular concern is code generated by
> `Large Language Models
> <https://en.wikipedia.org/wiki/Large_language_model>`__ (LLMs).
Documentation we maintain has the same concerns as code.
So I'd suggest to substitute 'code' with 'code / content'.
> If we want to mention uses of AI we consider okay, I'd do so further
> down, to not distract from the main point here. Perhaps:
>
> The QEMU project thus requires that contributors refrain from using AI code
> generators on patches intended to be submitted to the project, and will
> decline any contribution if use of AI is either known or suspected.
>
> This policy does not apply to other uses of AI, such as researching APIs or
> algorithms, static analysis, or debugging.
>
> Examples of tools impacted by this policy includes both GitHub's CoPilot,
> OpenAI's ChatGPT, and Meta's Code Llama, amongst many others which are less
> well known.
>
> The paragraph in the middle is new, the other two are unchanged.
>
> Thoughts?
IMHO its redundant, as the policy is expressly around contribution of
code/content, and those activities as not contribution related, so
outside the scope already.
>
> >> +to, `Large Language Models <https://en.wikipedia.org/wiki/Large_language_model>`__
> >> +(LLMs) results in a number of difficult legal questions and risks for software
> >> +projects, including QEMU.
>
> Thanks!
>
> [...]
>
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-04 7:16 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é [this message]
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 ` [PATCH v3 0/3] docs: define policy forbidding use of "AI" / LLM " Kevin Wolf
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=aD_yhelX-w4Vdm8Z@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@gmail.com \
--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).