How Licenses Became Enforceable¶
Year: 2008–present
Lesson: A license you can't enforce is a suggestion
The question under all the others¶
For the first two decades of free software, nobody actually knew whether any of it worked.
The GPL was published in 1989. It got argued over, translated, revised, and shipped on hundreds of millions of devices. What it had never been was tested. Companies complied because the Free Software Foundation would write them a letter and the letter was embarrassing. That is not the same thing as a legal obligation.
And there was a specific reason to worry, one that has nothing to do with whether the license text is any good.
If an open source license is only a contract, then violating it is a breach of contract. Breach of contract gets you contract damages — the money you lost. So: what did you lose when a company shipped your GPL code without the source?
You gave it away for free. Your lost profits are zero. Your reasonable royalty is zero, because your price was zero.
A rule with a worthless remedy is a rule people ignore as soon as they do the math. Somebody always does the math.
That's the hole the whole edifice was standing over. Not "is the license valid" — the license was fine. The problem was that the remedy for breaking it might be worth nothing, and a company's lawyers only have to notice that once.
Closing the hole took about twenty years, and it started with a model railroad hobbyist.
Jacobsen v. Katzer: conditions, not covenants¶
Robert Jacobsen ran the Java Model Railroad Interface, an open source project for controlling model trains from a computer. He released it under the Artistic License — an early permissive license, best known from Perl, that requires attribution and notice of changes. Matthew Katzer's company sold commercial model railroad software, took Jacobsen's code, stripped the attribution, and shipped it.
Jacobsen sued for copyright infringement. The district court threw that out. Its reasoning: the Artistic License is "intentionally broad" and unlimited in scope, so Katzer had a license, and having a license means you cannot infringe. Jacobsen could sue for breach of contract if he liked.
Which, per the arithmetic above, was an invitation to go home.
The Federal Circuit reversed in August 2008.1 The terms of the Artistic License were conditions on the copyright grant, not covenants collateral to it — and that distinction carries the whole weight of open source enforcement:
- A covenant is a promise alongside the license. Break it and you still have the license. You owe damages for a broken promise.
- A condition is a term the license is granted subject to. Fail it and the grant doesn't reach what you did. You are using copyrighted work without permission — which is infringement.
Infringement unlocks a different toolbox: statutory damages, and, decisively, injunctions. A court can order a company to stop shipping. That is a threat with a number attached, and it is the only reason a compliance conversation ever moves quickly.
The court also put on the record why the money framing had been the wrong lens all along:
Copyright holders who engage in open source licensing have the right to control the modification and distribution of copyrighted material.
The consideration in open source isn't cash. It's attribution, source availability, downstream freedom — things with real economic value that simply don't show up on an invoice.
The case went back down and settled on February 16, 2010: $100,000 paid to Jacobsen in installments, and an injunction the parties agreed to and asked the court to enter.2
One honest caveat
The Federal Circuit heard this case because it also involved patent claims, which is how the CAFC gets jurisdiction. Its copyright holding is therefore not binding precedent in the regional circuits, where most software cases live. It has been followed and cited relentlessly anyway. Influential is not the same as binding, and a page like this shouldn't pretend otherwise.
FSF v. Cisco: the remedy that isn't money¶
In December 2008, the Free Software Foundation sued Cisco over Linksys firmware — GCC, binutils, and glibc, all programs the FSF holds copyright in. Cisco had been in intermittent compliance conversations for years.
They settled in May 2009, and the terms are the interesting part.3 Cisco made an undisclosed payment, which nobody remembers. What Cisco also agreed to:
- Appoint a Free Software Director for Linksys, responsible for license compliance
- Have that person report to the FSF periodically
- Notify previous recipients of Linksys products of their rights under the GPL
- Publish a licensing notice on the Linksys website
A named employee, a reporting line to the plaintiff, and a duty to go tell customers what they were owed. For a copyleft holder, that is worth more than a check, because the check is spent once and the compliance officer shows up to work on Monday.
This is the enforcement pattern that has held ever since: the goal is compliance, and money is leverage toward it rather than the point of it. It's also why "we'll just pay if we get caught" is a bad plan — nobody is offering to sell you an indulgence.
Artifex v. Hancom: it's a contract too¶
Nine years later, the pendulum came back — usefully.
Artifex publishes Ghostscript, the PDF interpreter, under a dual license: GPL if you comply with the GPL, or a paid commercial license if you'd rather not. Hancom shipped Ghostscript in its office suite, didn't provide source, and didn't buy the commercial license.
Artifex sued for both copyright infringement and breach of contract. Hancom argued there was no contract at all — it never signed anything, never even clicked anything.
In September 2017, the Northern District of California disagreed.4 The GPL can be a contract. And then the court went to damages, which is where it gets genuinely useful: Artifex could measure its loss by the commercial license fee Hancom would have paid had it taken the paid option.
Read that against the Jacobsen problem. Contract damages for free software were supposed to be zero. For a dual-licensed project, they are the published price list.
The case settled confidentially in December 2017.
So by 2018 there were two independent doors into a courtroom:
| Theory | What it gets you | Who can walk through it |
|---|---|---|
| Copyright (Jacobsen) | Injunctions, statutory damages | Copyright holders only |
| Contract (Artifex) | Damages measured as unpaid license fees | Parties to the contract |
Both doors matter, and they aren't redundant. The copyright door has the stronger remedies and a narrow guest list. The contract door has a weaker remedy and — this becomes the whole story later — a guest list that might not be limited to authors.
Entr'ouvert v. Orange: Europe attaches a number¶
In February 2024, the Paris Court of Appeal awarded Entr'ouvert roughly €860,000 against Orange for GPL v2 violations involving its Lasso software, including €500,000 in compensatory damages.5
The case took thirteen years.
Two things are notable. European courts have been consistently more willing than American ones to enforce free software licenses and to attach real consequences to the result — the Steck v. AVM case in Berlin, which won LGPL users the right to modify and reinstall firmware on their own routers, points the same way.6 And the venue question turns out to be strategic: a compliance program calibrated to American litigation risk is calibrated to the wrong jurisdiction.
SFC v. Vizio: who gets to sue¶
Which brings us to the case that went to trial in Orange County this month.
By 2021 the enforceability question was settled well enough that the Software Freedom Conservancy could ask a harder one: not is the GPL enforceable, but who is allowed to enforce it.
Every case above was brought by a copyright holder or a party to a license. SFC bought a Vizio TV and sued as a user — arguing it is a third-party beneficiary of the GPL, since the license exists precisely to give downstream recipients source code. If that holds, GPL enforcement stops depending on whether some author from 2003 can be located and persuaded to litigate. Every customer becomes a potential plaintiff.
The tentative ruling in December 2025 is where this page pays off. SFC won — on the narrow ground that when its administrator requested source and Vizio had made a written offer, the two formed a direct contract.
That's Artifex's door, not Jacobsen's. The broader third-party beneficiary theory was tentatively rejected on procedural grounds, and it's what SFC is still trying to prove at trial. Twelve years of doctrine, and the win still came through the narrower opening.
What the chain actually built¶
Reading these together, the arc is not "courts decided to like open source." It's narrower and more useful than that:
- Jacobsen (2008) — license terms are conditions, so violations are infringement, so injunctions are available.
- Cisco (2009) — the settlement worth having is structural, not financial.
- Artifex (2017) — the license is also a contract, and for dual-licensed code the damages have a published price.
- Entr'ouvert (2024) — in Europe, the number is large and the patience is long.
- Vizio (2021–) — the open question is standing, and it is still open.
Every step was won by someone willing to spend years in court over software they had given away. Jacobsen ran a model railroad project. Artifex is a small company. SFC is a charity that bought a television. None of them had to do it, and the enforceability that every open source project now relies on exists because they did.
What this means for you¶
If you're complying:
- "We'll settle if they notice" misreads the remedy. Injunctions stop shipments, and compliance settlements install oversight that outlasts the check.
- Dual-licensed dependencies carry a specific arithmetic: your exposure is the commercial license you didn't buy, and it's on their website.
- Your risk isn't only the author's willingness to sue. Depending on how Vizio resolves, it may include your own customers.
If you're enforcing:
- Register your copyrights. Statutory damages in the US depend on it, and statutory damages are what make the copyright door worth using.
- Keep your provenance clean. The SCO litigation demonstrated that a decade can go to arguing about who owns what.
- A dual-licensing model does more than fund the project — it puts a number on the breach.
If you're choosing a license:
Enforceability is not a property of license text. It's a property of license text plus a jurisdiction plus somebody with standing who is willing to spend years on it. Pick a license whose community has that last part, because the clause you're relying on is only worth what the last person to litigate it made it worth.