Free Software Movement
1983–
The free software movement is the claim that software freedom is a prerequisite for other freedoms — and the forty-year project of building an alternative.
Origin
In 1983, Richard Stallman announced the GNU Project: an attempt to write a complete free Unix-compatible operating system from scratch, so that users would no longer be dependent on proprietary software. The GNU Manifesto (1985) made the political argument explicit. In 1985, he founded the Free Software Foundation.
By the early 1990s, GNU had most of the pieces. What it lacked was a kernel. In 1991, Linus Torvalds released Linux, and in 1992 relicensed it under the GPL. Combined with GNU tools, this became the operating system that now runs most of the world’s servers and infrastructure — and the Linux kernel sits under most of the world’s phones.
The Four Freedoms as Commons Governance
Stallman’s four freedoms (to run, study, modify, and distribute) are not just a user rights framework — they’re a commons governance structure. The GPL enforces them legally through copyleft: any distribution of modified code must carry the same freedoms. You cannot enclose it.
As a loose analogy, it echoes some of Ostrom’s design principles: clear boundaries (what’s covered), local rules (the license terms), collective decision-making (governance of the Foundation and projects), and graduated sanctions (license enforcement). The commons worked because the governance held.
Forks and Tensions
The movement has always been internally contested:
- Free software vs. open source: In 1998, Eric Raymond and others founded the Open Source Initiative, emphasizing practical benefits (better code, more contributors) over Stallman’s moral framing. “Open source” became the corporate-friendly term; “free software” stayed the political one. The code is often the same. The argument about why it matters is different.
- Copyleft vs. permissive licenses: The GPL requires that derivatives remain free. MIT and BSD licenses don’t — they permit proprietary forks. Much of the current cloud infrastructure runs on permissively-licensed free software that large companies use without reciprocating. Whether this is a betrayal or a feature depends on what you think the movement is for.
What It Built
The stack that makes local AI, meshnet, and self-hosted infrastructure possible is almost entirely free software:
- Linux (kernel)
- Python, Rust, Go (languages)
- Ollama, PyTorch, llama.cpp (AI inference)
- Git (version control)
- Apache, Nginx, Postgres, SQLite (infrastructure)
- Quartz, Astro (static sites)
None of this required permission. None of it can be revoked. That’s not an accident — it’s the result of forty years of deliberate commons-building.
Key Figures
- Richard Stallman — founding philosophy and legal architecture
- Yochai Benkler — economic theory of why it works
- Linus Torvalds — Linux kernel (pragmatist, not ideologue)
- Eric Raymond — open source framing, The Cathedral and the Bazaar
Connections
- commons — the governance model
- appropriate-technology — software freedom as appropriate technology
- conviviality — free tools as convivial tools
- repair-culture — right to study and modify as right to repair
- Vitalik Buterin — blockchain as an extension of this tradition
- cypherpunk — parallel tradition, different emphasis
The GPL didn’t just license software. It proved that a commons could hold against enclosure pressure for decades — and that the legal architecture of a commons matters as much as the social norms.