Group: Software/Upstream projects/LLMPolicies

Introduction

More and more Free Software and Open Source projects are adopting policies related to the use of LLM to generate code.

In many cases there is nothing new and the new policies are only a way to clarify the existing policies which already set requirements that don't magically go away with the use of LLMs.

Policies

Project	Policy	Analysis
Coreboot	Documentation/contributing/index.md in the Coreboot source code.	Requires the contributions to be compatible with Coreboot license (GPLv2). Seems to imply that using generative LLM won't magically make the licensing requirement go away.
Dillo	Blog post	Forbids the inclusion of code generated by/with LLMs.
GNU	Public and private discussions on various mailing lists.	No new content generated by LLM is allowed for now (until we get more legal clarity on the situation). No exceptions to this rule (even for content that is small, looks non-copyrightable, etc)
Linux	coding-assistants.rst in Documentation/process/ in the Linux source code. security-bugs.rst in Documentation/process/ in the Linux source code. Requires to sign the DCO (Developer Certificate of Origin)	Requires the contributions to be compatible with Linux license (GPLv2). Seems to imply that using generative LLM won't magically make the licensing requirement or other policies go away.
SeaBIOS	Contributing.md	Requires to sign the DCO (Developer Certificate of Origin) Since it requires to sign the DCO and that it says nothing about LLM, we can safely assume that licensing requirements are to be compatible with SeaBIOS's license (LGPLv3+).
Vim	CONTRIBUTING.md	According to the Forking Vim to avoid LLM-generated code lwn.net article, there is no limitations to the use of LLM for generating code.
Vim classic	blog post	Forbids the inclusion of code generated by/with LLMs.