docs/code-provenance: AI exceptions are in addition to DCO

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.

[This is not my preferred phrasing.  I would prefer something lighter
like "the "Signed-off-by" label in the contribution gives the author
responsibility".  But for the sake of not reinventing the wheel I am
keeping the exact words from the OpenInfra policy.]

Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Paolo Bonzini 2025-09-22 13:14:01 +02:00
parent 9ceb9b42c8
commit cd64320e1e

View file

@ -341,3 +341,9 @@ or more general revisions. This can be done by contacting the qemu-devel
mailing list with details of a proposed tool, model, usage scenario, etc.
that is beneficial to QEMU, while still mitigating issues around compliance
with the DCO. After discussion, any exception will be listed below.
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 submission 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.