qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH 3/3] docs/code-provenance: AI exceptions are in addition to DCO
Date: Mon, 29 Sep 2025 11:19:20 +0200	[thread overview]
Message-ID: <2eec6166-f426-41f8-bb79-18ac7d5497cd@redhat.com> (raw)
In-Reply-To: <aNo7RaEOKJ5GFjNQ@redhat.com>

On 9/29/25 09:54, Kevin Wolf wrote:
> Am 22.09.2025 um 17:48 hat Paolo Bonzini geschrieben:
>> Using phrasing from https://openinfra.org/legal/ai-policy (with just
>> "commit" replaced by "submission", because we do not submit changes
>> as commits but rather emails), clarify that the contributor remains
>> responsible for its copyright or license status.
> 
> I feel here the commit message is clearer than...
>
>> +Exceptions do not remove the need for authors to comply with all other
>> +requirements for contribution.  In particular, the "Signed-off-by"
>> +label in a patch submissions is a statement that the author takes
>> +responsibility for the entire contents of the patch, including any parts
>> +that were generated or assisted by AI tools or other tools.
> 
> ...the actually committed text. We should probably mention "copyright or
> license status" explicitly here in some way instead of just a more
> generic "responsibility for the entire contents" without referring to
> copyright.

It's mentioned earlier, since the responsibility is not limited to 
exceptions: "To satisfy the DCO, the patch contributor has to fully 
understand the copyright and license status of content they are 
contributing to QEMU".  I find this sentence to be already a bit heavy, 
and would prefer not to make it longer.

Paolo

> Maybe something like "...responsibility for the entire contents of the
> patch and in particular its copyright or license status, ..."



  reply	other threads:[~2025-09-29  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 15:48 [PATCH 0/3] docs/code-provenance: clarify AI exception process Paolo Bonzini
2025-09-22 15:48 ` [PATCH 1/3] docs/code-provenance: clarify scope very early Paolo Bonzini
2025-09-22 15:55   ` Peter Maydell
2025-09-22 16:05   ` Alex Bennée
2025-09-23 17:58   ` Stefan Hajnoczi
2025-09-22 15:48 ` [PATCH 2/3] docs/code-provenance: make the exception process more prominent Paolo Bonzini
2025-09-23 17:58   ` Stefan Hajnoczi
2025-09-23 19:20     ` Paolo Bonzini
2025-09-23 20:00       ` Stefan Hajnoczi
2025-09-22 15:48 ` [PATCH 3/3] docs/code-provenance: AI exceptions are in addition to DCO Paolo Bonzini
2025-09-22 15:54   ` Peter Maydell
2025-09-23 17:59   ` Stefan Hajnoczi
2025-09-29  7:54   ` Kevin Wolf
2025-09-29  9:19     ` Paolo Bonzini [this message]
2025-09-29  9:35       ` Kevin Wolf
2025-09-29 15:10         ` Paolo Bonzini

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=2eec6166-f426-41f8-bb79-18ac7d5497cd@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).