Codeberg’s members closed a 14-day vote on 22 July and adopted a binding Terms-of-Use restriction for hosted projects. The operative text bars users from sharing projects that mostly consist of code written by generative-AI tools. Its threshold concerns the composition of a project, rather than every instance of AI assistance during development. The narrower scope follows from the clause Codeberg chose to enact. [E1][E2]
Codeberg grounds the restriction in the costs and obligations of maintaining a shared software forge. Its official explanation cites infrastructure expense, uncertain copyright, added review work, harmful-code risk and projects that lack durable community maintenance. Enforcement is to proceed case by case. Codeberg also says the change will not trigger a mass purge. [E1]
Debian has opened a different process with no settled rule. Its General Resolution entered discussion on 24 July with four competing alternatives. They range from prohibiting direct LLM-assisted Debian contributions to allowing marked assistance under legal checks, disclosure and contributor accountability, with an intermediate option that discourages the practice and establishes conduct rules. No vote has concluded. [E3]
The NVIDIA-led letter addresses a separate governed object: downloadable model weights. It asks policymakers to avoid premature restrictions, arguing that open weights can widen access, strengthen competition, permit external inspection and reduce concentration in closed-model providers. The letter also acknowledges that releasing weights creates distinct risks. Jensen Huang introduced the argument by saying the world needs both frontier closed and frontier open models. [E4][E5]
Codeberg and Debian regulate artifacts entering volunteer-maintained trust chains. The coalition advocates the legal availability of models that others can inspect, modify and run. Neither position determines the other: access to weights does not compel a software project to admit generated code, and a contribution rule does not itself restrict weight distribution. Treating them as one policy dispute would erase the clauses that actually bind. [E2][E3][E4]
The null case is coherent: an institution can support open weights while refusing machine-written submissions. Those positions apply at different points in the production chain and reflect different allocations of legal, security and maintenance risk. Codeberg has enacted one hosted-project rule, while Debian is still considering four alternatives. The available record therefore supplies no unified FOSS doctrine on generative AI. [E1][E2][E3][E4]
A supply-chain tension nevertheless appears at the boundary between the two regimes. Wider access to open weights can increase downstream generation, while commons institutions may impose stricter tests before generated artifacts enter repositories, packages or maintenance queues. The practical dispute will concern disclosure, responsibility, review capacity and the point at which assistance becomes project composition. The contested interface is generation versus admission. [E1][E2][E3][E4]