QEMU: Define policy forbidding use of AI code generators

Summary

@@ -282,4 +282,57 @@ boilerplate code template which is then filled in to produce the final patch.282282The output of such a tool would still be considered the "preferred format",283283since it is intended to be a foundation for further human authored changes.284284Such tools are acceptable to use, provided there is clearly defined copyright285-and licensing for their output.285+and licensing for their output. Note in particular the caveats applying to AI286+content generators below.287+288+Use of AI content generators289+~~~~~~~~~~~~~~~~~~~~~~~~~~~~290+291+TL;DR:292+293+ **Current QEMU project policy is to DECLINE any contributions which are294+ believed to include or derive from AI generated content. This includes295+ ChatGPT, Claude, Copilot, Llama and similar tools.**296+297+The increasing prevalence of AI-assisted software development results in a298+number of difficult legal questions and risks for software projects, including299+QEMU. Of particular concern is content generated by `Large Language Models300+<https://en.wikipedia.org/wiki/Large_language_model>`__ (LLMs).301+302+The QEMU community requires that contributors certify their patch submissions303+are made in accordance with the rules of the `Developer's Certificate of304+Origin (DCO) <dco>`.305+306+To satisfy the DCO, the patch contributor has to fully understand the307+copyright and license status of content they are contributing to QEMU. With AI308+content generators, the copyright and license status of the output is309+ill-defined with no generally accepted, settled legal foundation.310+311+Where the training material is known, it is common for it to include large312+volumes of material under restrictive licensing/copyright terms. Even where313+the training material is all known to be under open source licenses, it is314+likely to be under a variety of terms, not all of which will be compatible315+with QEMU's licensing requirements.316+317+How contributors could comply with DCO terms (b) or (c) for...