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 /scripts/lib/kdoc/kdoc_files.py | |
| parent | 1f64df25477eff72779b000588cb821c654f26b7 (diff) | |
| download | qemu-9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8.zip qemu-9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8.tar.gz qemu-9ceb9b42c8f0f7ea6a4975e67405cfebee249ba8.tar.bz2 | |
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>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions