diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2025-09-22 12:51:37 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-09-24 09:26:23 +0200 |
| commit | 9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8 (patch) | |
| tree | 7ee4869b9e075f40c6b8b51140b89f316c594f23 | |
| parent | 1f64df25477eff72779b000588cb821c654f26b7 (diff) | |
| download | focaccia-qemu-9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8.tar.gz focaccia-qemu-9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8.zip | |
docs/code-provenance: make the exception process more prominent
QEMU's AI generated content policy does not flesh out the exception process yet. Do it, while at the same time keeping things informal: ask contributors to explain what they would like to use AI for, and let them reach a consensus with the project on why it is credible to claim DCO compliance in that specific scenario. In other words, exceptions do not "solve the AI copyright problem". They take a position that a reasonable contributor could have, and assert that we're comfortable with the argument. Suggested-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| -rw-r--r-- | docs/devel/code-provenance.rst | 15 |
1 files changed, 10 insertions, 5 deletions
diff --git a/docs/devel/code-provenance.rst b/docs/devel/code-provenance.rst index dc3524ac17..6968d54be8 100644 --- a/docs/devel/code-provenance.rst +++ b/docs/devel/code-provenance.rst @@ -331,8 +331,13 @@ ChatGPT, Anthropic's Claude, and Meta's Code Llama, and code/content generation agents which are built on top of such tools. This policy may evolve as AI tools mature and the legal situation is -clarifed. In the meanwhile, requests for exceptions to this policy will be -evaluated by the QEMU project on a case by case basis. To be granted an -exception, a contributor will need to demonstrate clarity of the license and -copyright status for the tool's output in relation to its training model and -code, to the satisfaction of the project maintainers. +clarified. + +Exceptions +^^^^^^^^^^ + +The QEMU project welcomes discussion on any exceptions to this policy, +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. |