Lumi, a longtime free software activist, has published a personal manifesto arguing that the movement's fixation on copyleft licensing has become a distraction from the deeper question: who actually controls a project and what values do they hold? The argument is simple but structurally interesting — copyright is an inherently extractive system, and copyleft is a hack that uses that system against itself. Hacks have limits. The core claim is that a project can satisfy every letter of the AGPL-3.0 and still be functionally proprietary in spirit. The telltale signs: dual-licensing under a commercial license, mandatory contributor license agreements (CLAs) that transfer rights from contributors to a single corporate entity, and development governance that runs through corporate decision-making rather than community consensus. The license says 'free.' The power structure says 'ours.' Lumi proposes a checklist that goes well beyond license text. Does the project have an inclusive code of conduct? Does it ban generative AI from its contribution pipeline? Is development centralized in a corporation? Does it endorse proprietary platforms like Discord and GitHub for its core infrastructure? These are values questions, not legal questions, and the essay argues they matter more than whether the license is MIT or GPL. The essay also pushes toward cooperative models of software development — naming The Starlight Network and Polyphony as examples of communities that span multiple projects and share labor. This is the generative kernel: software cooperatives as an organizational form that distributes power by design, rather than relying on a license to constrain power after it has already been concentrated. The weakness here is structural vagueness. There are no metrics for evaluating community health, no framework for what 'inclusive' means in practice, and no acknowledgment that community governance has its own failure modes — burnout, capture by vocal minorities, scope creep into political litmus tests that drive away contributors. The checklist is a starting point, not an answer. What makes this worth reading is the honest reckoning with a movement's own tools. Copyleft was a brilliant legal jiu-jitsu move. But legal mechanisms don't build solidarity, and they don't prevent extraction by actors who are sophisticated enough to comply with the letter while violating the spirit. The essay is a call to shift attention from the contract to the people who sign it. The practical implication is straightforward: if you care about free software, contributing code is not enough. Contributing to governance, documentation, community management, and cultural norm-setting is where the real leverage lives. The license protects the code. The community protects the project.
