Group: Software/Upstream projects/LLMPolicies

From LibrePlanet
Jump to: navigation, search
(Introduction: I assume that not many projects will remove actual requirements of proper licensing etc.)
(Policies: Add VIM policy)
 
Line 17: Line 17:
 
* Requires the contributions to be compatible with Coreboot license (GPLv2).
 
* 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.
 
* Seems to imply that using generative LLM won't magically make the licensing requirement go away.
 +
|-
 +
| Vim
 +
| [https://raw.githubusercontent.com/vim/vim/master/CONTRIBUTING.md CONTRIBUTING.md]
 +
| According to the [https://lwn.net/Articles/1067007/ Forking Vim to avoid LLM-generated code lwn.net article], there is no limitations to the use of LLM for generating code.
 
|}
 
|}

Latest revision as of 17:00, 25 April 2026

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.
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.