Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy (gitlab.redox-os.org)

Article summary

The Redox OS project has adopted a Certificate of Origin policy and a strict no-LLM policy, which has sparked a discussion about the use of Large Language Models in software development. The policy states that any content submitted that is clearly labelled as LLM-generated will be immediately closed, and any attempt to bypass this policy will result in a ban from the project. The discussion revolves around the enforceability and implications of this policy. The project's decision is seen as a way to maintain the integrity and quality of the codebase.

Main themes

• LLM usage in software development
• Code quality and integrity
• Enforceability of policies
• Copyright and ownership
• AI-generated code

What commenters say

• The no-LLM policy is unenforceable because it's impossible to distinguish between high-quality LLM-generated code and hand-typed code.
• The policy is necessary to prevent low-effort contributions and maintain the quality of the codebase.
• Using LLMs in software development is inevitable and will become the norm, making manual keyboard entry of code obsolete.
• The use of LLMs raises copyright and ownership concerns, as the generated code may not be considered the original work of the contributor.
• The policy is a reasonable measure to ensure that contributors are accountable for their work and to prevent plagiarism.
• The distinction between LLM-generated code and human-written code is becoming increasingly blurred, making it difficult to determine the origin of the code.
• The no-LLM policy may stifle innovation and progress in software development, as LLMs can be a powerful tool for generating high-quality code.
• The policy is not about preventing the use of LLMs altogether, but about ensuring that contributors are transparent about their use and take responsibility for the generated code.