The Free Software Foundation’s Licensing Lab logged over 400 queries last year alone about projects with mysteriously altered licenses.
Distributors tweaking code. Forks sprouting new terms. Combinations that shouldn’t work but do—or don’t. It’s chaos in the open source trenches.
And the FSF just dropped a clarion call: relicensing isn’t compatibility. Full stop.
What Even Is Relicensing?
Relicensing — that’s when every single copyright holder on a project signs off to slap a new license on the whole shebang. Think upgrading from GPL-2 to GPL-3, or maybe to Apache if everyone’s cool with it. Rare as hen’s teeth, because coordination’s a nightmare.
But here’s the FSF’s mic-drop moment, straight from their updated guide with volunteer Yoni Rabkin:
The GNU General Public License (GNU GPL) is intended to work in such situations [of license changes or combinations] by requiring that the combined work be released under the GPL.
Compatibility? Totally different beast. It’s about whether License A plays nice with License B when you mash them together. GPL with MIT? Sure, under rules. But don’t pretend slapping MIT on a GPL project counts as ‘compatible.’
Look, distributors love this gray area. They grab your GPL gem, bundle it, and — poof — call their output ‘proprietary-compatible.’ Nope.
Why Can’t You Just Change the License Downstream?
Short answer: copyright.
You own your code’s terms until you say otherwise. A downstream repackager? They’re guests in your house, not landlords.
The FSF’s point lands hard here — and it’s why their Lab’s swamped. Projects get relicensed without upstream say-so, violations pile up, and suddenly you’re chasing lawyers across GitHub issues.
Take historical drama: MySQL’s Oracle-era relicensing wars. Community forks like MariaDB emerged because relicensing upstream broke trust. Parallel? Absolutely. Today’s AI model trainers hoover up GPL code, retrain, and spit out ‘compatible’ weights under friendlier terms. FSF’s watching that battlefield closely.
My unique take: this isn’t just semantics. It’s architecture. Open source thrives on trust in license invariants. Mess with relicensing rules, and you erode the copyleft fortress brick by brick — predicting a surge in ‘relicensed’ AI datasets by 2026, sparking FSF lawsuits that make today’s noise look quaint.
## Is Relicensing Dead in Modern Open Source?
Not dead. Evolving.
Dual-licensing outfits like Qt pulled it off — GPL or commercial, your pick. But for pure community projects? Forget it. Too many holders, too little consensus.
FSF pushes compatibility instead: build atop GPL, release under GPL. Keeps the freedom flowing.
But — em-dash alert — distributors dodge. They static-link, obfuscate, or ‘relicense’ via EULAs. FSF calls BS, and they’re right. It’s corporate spin dressed as engineering.
How GPL Actually Handles Combinations
Sprawling sentence incoming: Picture two crates, one GPL’d gem for crypto, another Apache’d UI lib; combine them in your app, and boom, the whole output must GPL out because GPL demands it — no sneaking proprietary shells around the copyleft virus, as RMS once quipped.
That’s compatibility in action. Not relicensing the crypto lib to Apache.
FSF’s Lab sees this mangled daily. Reports roll in: “My project’s forked with MIT!” Cue audits, cease-and-desists.
Skeptical eye: some ‘violations’ are honest mistakes. Others? Calculated license laundering. Call out the latter — it’s poisoning the well.
The Real-World Fallout
One paragraph punch: Developers waste weeks on license FUD.
Then dense dive: Fork proliferation skyrockets — good for choice, bad for cohesion. Enterprise adopters balk at GPL entanglements, opting for permissive alternatives. And AI? Training on relicensed mishmashes could invalidate models if upstream holders sue. We’ve seen it with GitHub Copilot scraps already.
FSF’s guide isn’t preachy; it’s a scalpel. Cuts through hype, reminds us: licenses are contracts, not suggestions.
Why Does This Matter for Open Source Architects?
Because your stack’s foundation wobbles.
Choose GPL? Lock in freedoms, but brace for compatibility gatekeeping. Go permissive? Easier merges, but watch your code get relicensed into oblivion.
Bold prediction: By embedding this in tools like GitHub’s license scanner — with FSF-approved checks — we’ll halve violation reports in two years. Or not, if Big Tech ignores it.
🧬 Related Insights
- Read more: One Developer Just Freed Agent Skills from Their Walled Gardens—and It Changes Everything
- Read more: The Silent Killer of On-Call Engineers: Why Your Monitoring Is Broken
Frequently Asked Questions
What is the difference between relicensing and license compatibility?
Relicensing changes the original code’s license with all holders’ OK. Compatibility governs how different licenses mix in derivatives — no upstream change needed.
Can a distributor relicensing my GPL project?
No. Only you and co-holders can. Downstream changes are violations, per FSF.
Why is the FSF updating this now?
Rising reports of unauthorized changes and combo projects, especially in bundled distros.
