Protecting our FLOSS commons from LLMs
A non-profit Git hosting platform, Codeberg, has introduced terms of service banning projects that are “mostly” generated by LLMs, positioning itself as a home for human-written, FLOSS code and responding to worries about legal risk, security, hardware costs, and cultural erosion from AI-generated “slop.” Supporters see this as a democratically chosen, community-defining stance that protects resources and fosters higher-quality, human-centric projects. Critics argue the policy is vague, hard to enforce, exclusionary toward common AI-assisted workflows, and indicative of a volatile, activist governance style that makes the service less reliable as a long-term host.
Support for Codeberg’s anti‑LLM policy
- Many welcome a clearly anti‑LLM forge as a “safe space” for human‑centric FLOSS, distinct from GitHub’s “dumping ground” feel.
- Supporters see it as:
- Quality control against “vibe‑coded” low‑effort slop.
- Protection of the FLOSS commons from license laundering and unclear copyright status.
- A way to avoid ghost projects that heavily consume CI/storage with little real userbase.
- A cultural stand against big US tech and commercialization of community labor.
- Some like that it creates a strong signal: code hosted there is expected to be mostly human‑written and cared for.
Criticism and concerns about the policy
- Critics find “projects that mostly consist of AI‑generated code” too vague and subject to selective, subjective enforcement.
- Several worry about:
- Capricious “activist” governance and shifting rules over time.
- Being forced to prove they didn’t use LLMs if accused, enabling trolling or harassment.
- A purity‑test culture and hostile rhetoric (e.g., analogies to rape or Nazis) that feels undemocratic and toxic.
- Some maintainers who responsibly use LLMs for parts of their work have already moved projects off Codeberg, saying they don’t want to be under that “microscope.”
Governance and democracy debate
- Defenders argue the rule was democratically adopted by voting members; membership is open to any user who joins the association.
- Detractors counter that “members only” voting is effectively closed‑door and can marginalize minority views; Codeberg feels more like a club than a neutral platform.
Debate over LLMs in software development
- Pro‑LLM voices report major productivity gains in CI/CD, debugging, packaging, deployment, and issue resolution, leading to more FOSS participation.
- Anti‑LLM voices emphasize:
- Non‑consensual training on licensed code and erosion of reciprocity.
- Environmental and hardware‑market externalities, harming small operators and hobbyists.
- Floods of low‑quality contributions, pressure on non‑users, and perceived decline in craft and community.
Practical and ecosystem implications
- Enforcement is seen as largely honor‑based and technically hard to verify; some predict it will just push LLM use underground.
- Others note that multiple forges with distinct norms is healthy: people who dislike the policy can self‑host or stay on GitHub, while Codeberg becomes a niche hub for anti‑LLM projects.