In 1980, Xerox gave the MIT AI Lab a laser printer. The lab’s previous printer jammed
constantly, so the hackers read the source and changed the software to message everyone with
a queued job whenever the paper wedged. Annoyance, patch, solved. That was the normal
relationship to software back then. You fixed it.
The new printer jammed too. This time there was no source code. Dr. Stallman tracked down a
researcher at Carnegie Mellon who had a copy, and the man refused to share it because he had
signed a nondisclosure agreement. He had promised, in writing, not to help his neighbor.
Dr. Stallman later called that the moment he understood proprietary software for what it is:
a system for keeping users helpless. GNU was announced three years later. The whole movement
traces back to one office appliance and one broken promise.
Forty-five years later the printer is still the most user-hostile object in the building, for
exactly the reason nobody fixed in 1980. Ink cartridges carry cryptographic chips so the
machine can refuse cheaper ink. Firmware updates arrive quietly and brick the third-party
cartridges that worked yesterday. Printers decline to scan, an operation involving
zero ink, because a toner counter says so. Drivers get abandoned, and a perfectly good machine
becomes e-waste because the software rotted and you’re forbidden to cure it. Nobody ever fixed
the jam. They monetized it. Every subscription-ink scheme is that CMU nondisclosure agreement
with a billing department attached.
So be precise about the words. “Open” is a marketing term. It was coined in 1998 expressly
because “free” made corporate buyers flinch, and that flinch tells you plenty. A price tag
doesn’t scare these companies. A word that hands you rights does. When a term
frightens exactly the people who profit from your helplessness, keep saying it.
Free software dates to 1983. Dr. Stallman announced GNU that September, the Free Software
Foundation followed in 1985, and the GPL turned the four freedoms into something you could
enforce in court. By the time anyone said “open source,” the movement it renamed had fifteen
years of code behind it: Emacs, GCC, most of a working operating system.
And the talking mattered as much as the code. In 1991 a Finnish student who’d been steeped
in the GNU world wrote a kernel for fun, licensed it under Dr. Stallman’s GPL, and dropped it
into the fifteen years of GNU userland already waiting for it. That student was Linus
Torvalds, and that’s why Linux became an operating system instead of a hobby tarball. In 1997
Werner Koch heard Dr. Stallman speak in Germany, urging Europeans to build a free replacement
for PGP that US crypto export law couldn’t touch; Koch went home and wrote GPG, the tool
journalists and dissidents still stake their lives on. No preaching, no Linux, no GPG. The
preacher was load-bearing.
Open source arrived in 1998, and it arrived as a pitch. Part of the community had decided
that the word freedom was scaring the customers, and they were candid about the fix:
Some of the supporters of open source considered the term a “marketing campaign for free
software,” which would appeal to business executives by highlighting the software’s practical
benefits, while not raising issues of right and wrong that they might not like to hear.
Millions of people now use and write free software under a different name, and most of them
have never once heard the original argument for it. As Dr. Stallman puts it, most discussion
of open source “pays no attention to right and wrong, only to popularity and success.”
Free means freedom, not price. Free speech, not free beer. A program is free
software when its license respects four freedoms, and every one of them belongs to the person
using the program. They read like a bill of rights because that’s what they are. Enumerated,
unalienable, and infringed just as often:
freedom 0
Run it, for any purpose
Use it for anything, on anything, forever. No approved-purposes list. Remember this one; it comes up later.
freedom 1
Study it, change it
Read it, learn from it, rewrite it. Source access exists to serve this freedom, not the other way around.
freedom 2
Redistribute copies
Give a copy to whoever needs one. Helping your neighbor is the design goal, not a piracy edge case.
freedom 3
Share your changed versions
Ship your modifications, so your fixes reach everyone the program reaches.
The GPL was written to guarantee these “for all users of a program,” including someone three
distributors downstream from the author. Copyleft is just freedom with an enforcement
mechanism attached. Dr. Stallman calls the freedoms essential “not just for the individual users’
sake, but for society as a whole,” and here’s the thing: the other camp never actually
disagreed with any of that. They just stopped bringing it up.
The FSF and the OSI both spend their days talking about licenses, which makes them easy to
mix up. Follow the money instead. The OSI runs on corporate sponsorship, and its sponsors are
some of the largest companies on earth. The FSF runs on membership dues from individuals.
FSF est. 1983
Campaigns for the freedom of computer users. That’s the whole mission statement.
Wrote the GPL, “designed specifically to protect freedom for all users of a program,” and defends it.
No corporate members. Funded by individual dues and limited donations that buy no vote and no seat.
Says “freedom” in meetings, unprompted, since 1983.
OSI est. 1998
Approves licenses. (§05 covers the quality control.)
Maintains a definition that never grants you the right to run the program. (§04.)
Founded to make free software palatable to business, with the ethics filed off.
Microsoft and Google do not sponsor things out of sentiment. Money at that scale steers,
whatever the org chart says. The FSF is structurally incapable of being bought the same way:
there is no corporate membership to buy. A company can donate, within limits, and what the
donation purchases is nothing. One of these organizations exists to defend you from
corporations. The other one sends corporations a welcome basket.
And when a license is actually violated, only one of them shows up. The FSF runs a licensing
and compliance lab, answers license questions for free, and holds the copyrights that make
enforcement possible. When Cisco shipped GPL code in Linksys routers without offering source,
the FSF took them to federal court in 2008 and settled on its terms: source code published, a
free-software compliance officer appointed, money paid. GPL violators can expect a courtroom.
The OSI offers nothing comparable. It holds no copyrights, runs no compliance program, and has
never enforced a license in its life; it stamps them and walks away. If anything, the
institution leans the other way: its co-founder spent years arguing that open source
“doesn’t need the GPL anymore.” Certifying dozens of alternatives to copyleft while defending
none of them is not neutrality. It is a way of hobbling the one license built to fight back.
Here is the structural problem, straight from the essay: almost all the items in the Open
Source Definition are “formulated as conditions on the software’s source license rather than
on what users are free to do.” Ten criteria about how code may be distributed. Nothing about
what you may do with it once you have it.
Try it yourself. The document is short:
run0/0
document: The Open Source Definition · matches: none
freedom0/0
document: The Open Source Definition · matches: none
user0/0
document: The Open Source Definition · matches: none
The word “use” appears once, in a rule about fields of endeavor: a license may not forbid
running the program in, say, a genetics lab or a business. Useful, but that’s a restriction
on restrictions, not a right handed to you. Nowhere does the definition actually say you may
run the program. The FSF numbered that freedom zero because everything else depends on it.
The OSD skips it because the OSD is a document about licenses, written for the people who
ship them. Users weren’t the audience.
If the OSD really captured freedom, no license could clear OSI review and still fail the
FSF’s. Several have. Everything below is officially, certifiably open source. None of it is
free:
Exhibit A — the star witness
Sybase Open Watcom Public License 1.0
OSI
Approved. Welcome aboard!
FSF
Nonfree.
Modify it and merely use it yourself (at home, alone, blinds closed) and that counts as “Deploy,” which obligates you to publish your source code. Using your own software is a legal event now.
Per Dr. Stallman: “it does not allow making a modified version and using it privately.” The exact freedom the OSD forgot to require.
NONFREE
Exhibit B
Reciprocal Public License 1.5
OSI
Approved. Welcome aboard!
FSF
Nonfree.
Requires you to publish every modified version you use, for any purpose (private included), and restricts selling copies. Mandatory transparency, but only for you.
Reciprocity, in the sense a vending machine loves you back.
NONFREE
Exhibit C
NASA Open Source Agreement 1.3
OSI
Approved. Welcome aboard!
FSF
Nonfree.
Contributions must be your “original creation,” so incorporating existing free code from third parties is off the table. A collaboration license that is afraid of collaboration.
It’s not rocket science. Legally, however, it is.
NONFREE
Exhibit D
Artistic License 1.0
OSI
Approved. Welcome aboard!
FSF
Nonfree.
So vague the FSF could not determine what it actually permits, with clauses famously “too clever for their own good.” Perl dual-licensed its way out of the blast radius.
The license equivalent of vibes.
NONFREE
These four are the famous exhibits, not the full docket. The FSF’s license list records more
OSI-approved licenses it classifies as nonfree, and plenty of freedom-hostile fine print this
page never gets to. The names change; the finding doesn’t. None of these documents were
written to protect your freedom.
Restrictions also stack on top of licenses, where no definition is looking at all. Dr. Stallman
points at the Rust compiler: possibly nonfree in practice, not because of its license but
because of trademark terms that forbid selling copies or shipping modified versions under the
name. So even a fully free license doesn’t settle the question, because the checkbox never
looks past the license.
“Free software” is ambiguous (free as in what?), but one slogan fixes it, and once you’ve
heard “free speech, not free beer” you don’t get it wrong again. “Open source” has the worse
problem: its plain-English reading is simply incorrect. To most people it means “you can look
at the source code,” which describes source-available software, a much weaker thing.
No slogan can talk the public out of the obvious reading. Watch it fail in the wild:
“Linux is ‘open source’ software meaning, simply, that anyone can get copies of its
source code files.”
“OSS is software for which the source code is freely and publicly available, though the
specific licensing agreements vary as to what one is allowed to do with that code.”
And the word kept drifting. Open government, open education, open science, open anything.
By now it often means no more than “participatory,” and in Dr. Stallman’s words, “at worst, it
has become a vacuous buzzword.” A movement can survive being attacked. Becoming a buzzword
is harder.
Say the license is fine and the source really is up there, mirrored and tarballed. The device
in your hand still checks cryptographic signatures and refuses to boot anything you compile
from it. The industry name for this is tivoization. Dr. Stallman’s is blunter:
We call these devices “tyrants,” and the practice is called “tivoization” after the product
(Tivo) where we first saw it. Even if the executable is made from free source code, the users
cannot usefully run modified versions of it, so the executable is de-facto nonfree.
This isn’t an edge case. Android is the best-selling computing platform in history, its
kernel is GPLv2, and most Android phones ship exactly this way. Open source on the label,
tyrant in the box. And by the plain meaning of “open source,” nothing has even gone wrong.
GPLv3 exists specifically to forbid this. The FSF watched the trap close and rebuilt the
license. The open source world’s response, for the most part, was to stay on GPLv2 and keep
shipping. When the philosophy is whatever works, tyrants are what works.
I have sworn upon the altar of God, eternal hostility against every form of tyranny over the
mind of man.
The open source case is that openness makes software more powerful and more reliable. That
invites a question the framework has no way to process: powerful for whom?
What if the software is designed to put chains on its users? Then powerfulness means the
chains are more constricting, and reliability that they are harder to remove.
Spying, restrictions, back doors, imposed upgrades. Dr. Stallman lists them as standard
proprietary features that “some open source supporters want to implement in open source
programs.” Open-source DRM has been earnestly proposed: publish the source of the thing that
restricts you, let the community harden it, then ship it in a device you can’t change. Open
source, as a methodology, files no objection to any of this. There’s nothing in the framework
to object with.
Open-source spyware is still spyware. You just get to read exactly how you’re being watched.
Why did the split happen in the first place? Because ethics made the sales calls awkward.
“Raising ethical issues such as freedom… is asking people to think about things they might
prefer to ignore,” and executives don’t buy discomfort. So the leaders of open source stopped
raising the issues. Here is what that training produces when genuinely excellent proprietary software shows up:
the open source enthusiast
“I am surprised you were able to make the program work so well without using our
development model. How can I get a copy?”
This attitude “will reward schemes that take away our freedom, leading to its loss.”
the free software activist
“Your program is very attractive, but I value my freedom more. So I reject it. I will get
my work done some other way.”
“If we value our freedom, we can act to maintain and defend it.”
The rebrand delivered users by the millions, and it delivered them unarmed. Open source
“brings many people into our community, but does not teach them to defend it.” Sooner or
later each of those users gets a compelling offer to go proprietary again (better features,
a free tier, a discount) and nothing in the open source worldview supplies a reason to say
no. Where loving freedom looks like an eccentricity, the discount wins.
Nobody can give you freedom. Nobody can give you equality or justice or anything. If you’re a
man, you take it.
When in the course of computing events it becomes necessary for a community to dissolve the
vocabulary which has connected it with a sponsor page, a decent respect to the opinions of
mankind requires that it should declare the causes. Better still: prove them.
“Free” and “open” compete for the same slot in your head, and only one of them teaches you
anything while it sits there. “Any activity that promotes the word ‘open’ tends to extend the
curtain that hides the ideas of the free software movement.” Every sponsored conference and
every corporate open-source initiative pulls that curtain a little further across.
The companies funding all of it are not confused. Open is a methodology, a supply chain, a
hiring pipeline, a compliance checkbox. All of that is fundable. Freedom is a demand, and
nobody funds demands against themselves. Nobody managed to capture the movement’s values, so
they captured its vocabulary instead, and that turned out to be enough. Neutral terms won’t
undo it either; on FOSS and FLOSS, Dr. Stallman is curt: “if you want to stand up for freedom,
using a neutral term isn’t the way.”
Freedom is never voluntarily given by the oppressor; it must be demanded by the oppressed.
So separate. Not out of purity, out of arithmetic. The vocabulary is taken, the definition
has sponsors, and the organization holding it answers to them, not to you.
You could keep arguing about this forever. Or you could notice that it stopped being an
argument a while ago, because it’s a theorem.
Both organizations are US 501(c)(3) nonprofits, and both publish their finances. That makes
this the rare internet argument you can settle with primary sources. Every link in this
section goes to a document the organizations host themselves.
The OSI’s money is corporate sponsorship, sold in tiers with names like Titanium, Diamond, Platinum, and Gold, the way conference booths are sold.
Microsoft made it official in 2017,
joining Google, IBM, GitHub, Facebook, and Comcast on the sponsor page. There is a “Supporting
Member” program for individuals, but it’s a side door on a building designed for
corporations. The 2025 annual report puts numbers on it: in 2024 the OSI took in $520,000 of corporate sponsorships and $249,000
in grants, against $26,000 of membership dues. The side door is 2.4% of the building.
The FSF files the boring paperwork. Its most recent audited statement, FY2024 (year ended September 30, 2024) puts membership dues at $676,664 and direct contributions at
$381,322, against total revenue of $1,312,822. Do the division: individual dues and gifts are
roughly four-fifths of everything the FSF took in. The statement even itemizes $22,389 in
Bitcoin and Litecoin from donors. Year-end net assets: about $1.35 million. That is the
entire war chest of the organization defending the GPL, smaller than a rounding error in any
single sponsor’s marketing budget.
An organization is what its revenue makes it. §03 made that argument with adjectives; this is
the same argument in dollars, signed by an independent auditor. If you think this page is
spinning the numbers, good. Go check: every FSF financial statement and Form 990 is public, going back years.
Contributions (donor type unstated)$227,000 · 20.8%
Events & other$69,000 · 6.3%
Membership dues$26,000 · 2.4%
data table
Source
USD
Share
Corporate sponsorships
$520,000
47.7%
Grants (foundations)
$249,000
22.8%
Contributions (donor type unstated)
$227,000
20.8%
Events & other
$69,000
6.3%
Membership dues
$26,000
2.4%
Total revenue
$1,091,000
100%
Source: the OSI’s own 2025 annual report, 2024 column, rounded there to the nearest $1,000. Self-reported, not an independent audit.
Same question, both books, same year. Look at the blue slice: membership dues from
individual people. At the FSF it is the single biggest line, 51.5% of everything. At the
OSI it is 2.4%, and corporate sponsorships plus foundation grants make up 70%. The blue
money votes with its feet. The amber money votes at the board.
Ten years of books · 2015–2024
20152024
FSF · 2024audited statement
Total revenue
$1,312,822
Net assets
$1,351,023
Membership dues
$676,664 · 51.5%
OSI · 2024own annual report
Total revenue
$1,091,000
Net assets
not reported
Membership dues
$26,000 · 2.4%
A note on the dues rows: the FSF’s audits didn’t itemize dues before FY2021 (they sat
inside “contributions”), and the OSI has never put a dues line on a Form 990 in its life.
Its first disclosure, in its own 2025 annual report, was 2.4% for 2024. A membership share
nobody bothers to measure is a membership that doesn’t pay the bills.
One more thing the decade makes plain: the FSF was never endowed. There is no university-style
war chest quietly compounding; net assets have hovered around a single year of expenses for
ten years, and the 2018–19 bump was one-time gifts, Handshake’s $1 million among them, spent down doing the work. Every single year the books reset to the same question:
will enough individuals renew? It relies on its members more than you think. The OSI’s curve
bends up too, and you have seen whose money bends it.
The OSI sponsor wall · July 2026
21 corporate sponsors across 8 named
tiers, plus two foundations.
Titanium1›
Automattic
Diamond3›
MongoDB
Cisco
Amazon Web Services
Platinum3›
Bloomberg
Google Open Source
Microsoft
Gold5›
Capital One
GitHub
Red Hat
Sentry
Eclipse
Silver2›
OpenLogic by Perforce
Block
Bronze2›
Blindside Networks
pretix
Partner2›
DLA Piper
LPL
Community3›
Open Project
Sourcegraph
WordUnscrambler
If you want to know what sponsor money buys, look at what the OSI did to its own founding
document. In 2024 it shipped the Open Source AI Definition, which blesses AI systems as
“open source” even when the training data that built them stays secret. The Software Freedom
Conservancy’s verdict is in its title: the definition “erodes the meaning of open source.” The OSI’s defense was that a stricter definition would have excluded every existing system.
Read that again. The standard was loosened until the sponsors’ products could pass it. That
is not stewardship. That is a rubber stamp with a waiting room.
The free software press watched it happen in real time. Tux Machines tracked the openwashing wave through late 2024 and relayed the Conservancy’s criticism when the paymasters got named directly. The pattern that coverage keeps finding is the one
the donut above already showed you: an organization that certifies whatever the logo wall
needs certified.
Techrights, which has covered the OSI for more than a decade, is blunter. Its running series
documents what it calls the corruption of the OSI,
describing a front group for Microsoft and friends that its original enemies simply devoured,
funded so top-heavily that member money barely registers. Its obituary runs one line: cause of death, Microsoft bribes.
Those are fighting words from an advocacy site, and you should weigh them as such. Then look
back at the chart. Dues at 2.4%. The OSI’s harshest critics and the OSI’s own annual report
are describing the same organization.
You don’t have to adopt anybody’s rhetoric to see the shape. When a standards body lives on
sponsorships, its standards drift toward its sponsors, and the OSAID is that drift printed,
ratified, and press-released. The FSF has spent forty years refusing to bend the four
freedoms. The OSI bent its founding document the first time the money asked. One of those
definitions will mean the same thing in ten years. The other means whatever next year’s
Titanium tier needs it to mean.
In the absence of true control over various systems (that we control, use, own, or merely
connect to) we cannot control our lives; someone else controls us.
Whatever goodwill the OSI still carried into this decade, it has been spending fast. Start
with a precedent it broke in 2021: a license steward issuing an official statement about a person.
The OSI declared it “inappropriate” for Dr. Stallman to hold any leadership position in the
community, refused to attend events that include him, and cut collaboration with the FSF
until he was removed. An organization built to certify licenses appointed itself to certify
people, and it started with the man who founded the movement it renamed. The accusations it
leaned on have been examined line by line, with primary sources, at stallmansupport.org.
Whatever you conclude there, the institutional fact stands: the OSI severed its last working
tie to the free software movement on purpose, in writing.
Then came the definition work. §11 covered what the Open Source AI Definition permits;
what’s worth adding is that the complications never ended. The dissent from the Software
Freedom Conservancy and others has not died down, and the contrast with the other camp is
instructive: the FSF convened a working group in May 2024 and is still carefully working out criteria for free machine learning applications to this day, insisting that training data and scripts carry the four freedoms too. One
organization is taking years to get freedom right. The other shipped whatever its sponsors
could pass, on deadline, and called the dissent noise.
And the org chart tells its own story. When the executive director’s office emptied in
late 2025, filling it took roughly half a year of searching, an interim caretaker, and a
recruitment drive; FOSS Force’s headline for the eventual hire said the quiet part: “Duane O’Brien Takes OSI’s Hot Seat.” Healthy institutions do not struggle for months to give away their top job. Hot seats are
hot for a reason: whoever sits down inherits the sponsor list, the definition backlash, and
a community that increasingly wonders what the organization is for.
Add it up. It denounced the movement’s founder, bent its founding document for its
sponsors’ product lines, and can barely staff its own leadership. None of these are the
troubles of an organization that answers to users, because users were never the
constituency. The OSI represents corporations in computing. If you are a person in
computing, it does not represent you, and its last few years are the proof it keeps
publishing about itself.
None of this is an assault on open source folks. Most of them are the community:
maintaining the packages, reviewing the patches, answering issues at eleven at night for
strangers. What’s being called out is a continual pattern of bad practice at the top of the
institution, not the people doing the work under its name.
We in the free software movement don’t think of the open source camp as an enemy; the
enemy is proprietary (nonfree) software.
That’s verbatim. Open source developers are allies in the fight that actually matters, the
one against nonfree software. The disagreement isn’t a war between camps. It’s bookkeeping:
coming clean about which words, licenses, and institutions are helping the free software
movement, and which ones quietly drain it. Get that accounting wrong for long enough and
the whole thing derails, with everyone aboard still convinced the train is fine.
Dr. Stallman’s point is that open source people are not the enemy; nonfree software is.
We just need to stay honest about what helps the free software movement and what could derail it.
Take the open source program offices at universities. A lot of them do genuinely good work:
prying research code out of desk drawers, teaching students to contribute upstream, cleaning
up license messes so that public money actually produces public code. But notice what the
name is for. “Open Source Program Office” is a phrase built for a provost’s budget
spreadsheet. Bureaucracy, not philosophy. What the good ones practice day to day looks a
lot like free software; the label mostly came stapled to the funding paperwork.
The institution is a different story, and the difference is structural. No organization that
lets the world’s largest companies steer it has your best interest at heart. It can’t. Not
because its staff are bad people, but because incentives don’t care. The OSI runs on
corporate sponsorship, with Microsoft, Google, Amazon and Meta among the names on the checks.
The FSF takes no corporate members at all. Companies may donate within limits, and the
donation buys no vote, no seat, no leverage over the organization. Its money is membership
dues from individuals. People like you and me, forty dollars at a time. One of those funding
models can be fired by its base. The other one is its base.
Power concedes nothing without a demand. It never did and it never will.
Free software came first, in 1983, and it will still be here last, because it’s the
better-defined movement: four freedoms you can test any license against in an afternoon,
versus a brand whose own advocates spend half their time explaining what it doesn’t mean.
A definition with teeth ages well. One with sponsors gets renegotiated whenever the sponsors
need it to.
Everything above was rhetoric. This part is not. The entire forty-year argument fits in
three symbols, and here they are.
Definitions
Let U be the universal set of all software licenses. Define two
subsets of U:
F={ℓ∈U:ℓ satisfies the Free Software Definition}
— the four freedoms: run, study, modify, redistribute. Maintained by people who use the
word “freedom” in public.
O={ℓ∈U:ℓ satisfies the Open Source Definition}
— the OSD’s ten criteria. Maintained by the OSI and a sponsor page you’ve already met.
The claim to prove:
F⊆O∧O⊈F, which together imply F⊂O.
Lemma 1. F⊆O
Take any license ℓ∈F. By definition, ℓ grants users the freedom
to run, study, modify, and redistribute the software, which necessarily requires that
source code be available. This satisfies the OSD’s core criteria (free redistribution,
access to source, permission for derived works), so ℓ∈O.
Formally:
∀ℓ(ℓ∈F⟹ℓ∈O)
This is exactly subset inclusion, so F⊆O holds. It is why the
acronym FOSS treats the two as closely overlapping: every free license is automatically an
open source license, since exercising the freedoms to study and modify demands source
availability, which is itself an open source requirement. ∎
Lemma 2. O⊈F
To disprove the reverse inclusion it suffices to produce a single counterexample: a license ℓ0∈O such that ℓ0∈/F.
∃ℓ0(ℓ0∈O∧ℓ0∈/F)
Take ℓ0 = the Sybase Open Watcom Public License 1.0. It is
OSI-approved, and it is nonfree: it does not allow making a modified version and using it
privately. One witness suffices, and this witness is not hypothetical. It has a website,
a committee vote, and friends (§05 supplied three more). The existential statement is the
logical negation of O⊆F, so the reverse inclusion fails. ∎
Fig. 1 — O ∖ F is not the empty set. Unfortunately.
Combining the results
Statement
Symbolic form
Status
Every free license is open source
∀ℓ(ℓ∈F⟹ℓ∈O)
True
Every open source license is free
∀ℓ(ℓ∈O⟹ℓ∈F)
Falsecounterexample exists
Free is a proper subset of open source
F⊂O
True
Theorem
Since F⊆O is true and O⊆F is false,
by definition F is a proper subset of O:
F⊆O∧F=O
F⊂O ∎
Remark
The practical set difference O∖F is nonempty: licenses that
are technically open but philosophically nonfree. That crescent is the mathematical core of
the whole dispute: the two camps agree almost entirely on which licenses qualify, and
disagree completely on whether openness or freedom is the thing being
defended. Corporations noticed which of the two doesn’t inconvenience them.
One more empirical observation about that crescent: almost nobody builds there. The
licenses real projects actually ship under, copyleft or permissive, are the FSF-approved
ones: the GPLs, BSD, MIT, Apache. The O ∖ F residue is museum inventory, licenses with
committee votes and no users. Which tells you what “open source” is operationally for:
a label for presenting your project to corporations. It isn’t what protects you. To the
extent anything protects you, it’s copyleft, doing the same work it did before the label
existed.
The only “open source” you can trust is the part that was already free software. You never
needed the O. You needed the F.
✦ life, liberty, and the pursuit of computing freedom ✦
“It’s free software, and it gives you freedom!”
“Every time you say ‘free software’ rather than ‘open source,’ you help our cause.” That’s
it. One word, said on purpose.
And demand better from the organizations wearing the “open source” name: the
foundations, the program offices, the sponsored conferences. If they want your code and
your trust, they can mean free software when
they say it.
“Those who would give up essential Liberty, to purchase a little temporary Safety, deserve
neither Liberty nor Safety.”
Swap “Safety” for “a slightly nicer app” and the sentence still scans.
It costs nothing. It’s free. As in freedom, and, this once, also as in beer.