Theo Browne responds to Codeberg's member-approved plan to prohibit projects that mostly consist of generative AI-written codeCode generation uses AI or another automated system to create source code from instructions, examples, schemas, or higher-level specifications.. He argues that the policy treats AI use as a proxy for poor quality or malicious intent, even though the practical risks depend more on oversight, maintenance and contributor behavior.
Theo Browne agrees that Codeberg has legitimate reasons to control infrastructure costs, resource-heavy projects and low-effort AI-generated contributions. His central criticism is that usage limits and project-level moderationGovernance defines decision-making authority, rules and accountability within a system or organization. would address those problems more directly than a broad terms-of-use restriction.
Theo Browne also accepts that AI-generated contributions can raise maintainer workload and weaken trust, but says the answer is to improve review toolsCode review examines proposed source changes to assess their correctness, clarity and suitability before or around integration. and contributor practices. He frames the dispute as a test of whether open sourceOpen-source software provides source code under a license that permits use, modification and redistribution. communities can adopt modern coding tools while preserving collaboration and accountability.
Watch on YouTube




