Re: [PATCH 2/3] docs/code-provenance: make the exception process more prominent

[Stefan Hajnoczi <stefanha@gmail.com>]

On Tue, Sep 23, 2025 at 3:20 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 9/23/25 19:58, Stefan Hajnoczi wrote:
> >> +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 the legal risks to the
> >> +project.  After discussion, any exception will be listed below.
> >
> > "Legal risks to the project" is all-encompassing and vague. People may
> > not know how to start addressing the topic and might therefore not
> > attempt to request an exception.
> >
> > I suggest replacing "legal risks to the project" with something more
> > concrete like "issues around license and copyright status required to
> > satisfy the Developer Certificate of Origin (DCO) requirements".
>
> It's already a long sentence.  Would "while still mitigating issues around
> compliance with the DCO" be enough?

Yes.

Thanks,
Stefan