Andrew Mercer
on this page

Open source is mainstream now, but its DNA is rebellion. That rebellion shows up in a few recurring forms.

1. Rebellion against ownership of knowledge

The original premise — that you have the right to read, understand, and fix the tools you depend on — was a direct rejection of the idea that software is a black box you rent. Copyleft weaponized copyright law against the very model it was designed to protect.

2. Rebellion against corporate monopoly

Linux was a hobbyist kernel that ended up running most of the world's servers, every Android phone, every supercomputer on the TOP500 list, and much of the cloud — beating companies that spent billions fighting it. The Halloween Documents, Ballmer's "cancer" quote, and SCO's lawsuit were all attempts to stop it. They failed.

3. The fork as dissent

The right to fork is open source's ultimate check on power. If stewards act against the community, the community can take the code and leave:

Original Fork Year Why
XFree86 X.Org 2004 License change and closed governance
MySQL MariaDB 2009 Oracle's acquisition of Sun
OpenOffice.org LibreOffice 2010 Oracle's stewardship
Hudson Jenkins 2011 Trademark dispute with Oracle
Node.js io.js 2014 Governance (merged back in 2015)
Gitea Forgejo 2022 Control moved to a for-profit company
Terraform OpenTofu 2023 BSL relicensing
Redis Valkey 2024 Source-available relicensing

The fork is why relicensing an open source project is risky: you can change the license of future versions, but the last open version is out there forever.

4. Rebellion against gatekeeping

Anyone with an internet connection can read the Linux kernel, submit a patch, and have it judged on its merits. Your résumé doesn't matter; your code does. (That ideal has real limits — open source communities have long struggled with diversity, toxicity, and unpaid labour — but the principle of permissionless participation is radical.)

5. Rebellion against secrecy

"Release early, release often" and public bug trackers mean failures happen in the open. Proprietary vendors hide vulnerabilities; open source projects publish CVEs, post-mortems, and mailing list arguments for anyone to read.