A debate on the GNU Emacs mailing list about accepting LLM-generated code exposed a broader disagreement over what free software ethics should cover. Asked whether Emacs should accept technically sound code produced through slavery, maintainer Eli Zaretskii said yes, arguing that judging contributors’ ethics or circumstances would divide the community and that the project’s concern is software freedom. The writer says this answer was consistent rather than malicious, and recognizes the practical case against moral purity tests: maintainers cannot adjudicate every contributor’s life, and rejecting a patch does not itself liberate anyone.
The writer argues, however, that defining freedom only as users’ control over software leaves out the people and conditions behind it: exploited labor and training data, people affected by automated decisions, and those excluded by language, disability, or lack of access. They propose that projects openly set policies for LLM contributions and assess how code was produced, not a contributor’s personal beliefs. More broadly, free software should consider its human supply chains and social effects, and treat accessibility and solidarity as part of freedom. The writer does not advocate restricting software use through licenses, and acknowledges that forking is not a realistic remedy for dominant projects. Their central claim is that accepting code is not ethically neutral, so projects should make their choices explicit rather than default to “only the code matters.”
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.