"Michael S. Tsirkin" <[email protected]> writes: > As a first step towards moving with the times, let's add > exceptions. Let's also do what linux does and ask for tags > on ai generated code. > > This is not going far enough imho but will hopefully be > noncontroversial. > > Signed-off-by: Michael S. Tsirkin <[email protected]> > --- > docs/devel/code-provenance.rst | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/docs/devel/code-provenance.rst b/docs/devel/code-provenance.rst > index 4e6a9afe0d..c3ed7f5e69 100644 > --- a/docs/devel/code-provenance.rst > +++ b/docs/devel/code-provenance.rst > @@ -347,3 +347,22 @@ 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. > + > +1. When AI generated part of the contribution is not creative in nature > + (so not even copyrighteable). > + > +2. When the creative part of the contribution is clearly QEMU-specific > + (so derived from the prompt). > +
Before we start adding exceptions I think we need to be more explicitly clear about the responsibility of the person who adds the s-o-b to the patches. Once we open the door to AI assisted contributions we need to be ready for a potential avalanche of slop. > + > +Attribution > +^^^^^^^^^^ > + > +AI agents must not add Signed-off-by tags. Instead, > +contributions should include an Assisted-by tag, like this: > + > + Assisted-by: AGENT_NAME:MODEL_VERSION > + > +For example: > + > + Assisted-by: Claude:claude-opus-4-6 -- Alex Bennée Virtualisation Tech Lead @ Linaro
