First GPL lawsuit in US settles out of court
For real this time
Agentless Backup is Not a Myth
After a false alarm last month, the first lawsuit to test the GPL in the US has actually settled.
The Software Freedom Law Center (SFLC) announced yesterday that it has reached an agreement with Monsoon Multimedia to end the SFLC's copyright infringement suit against the company.
The lawsuit accused Monsoon of violating GPL version 2 by distributing GPL-licensed software without making the source code available. The plaintiffs, makers of the Unix utility collection BusyBox, alleged that Monsoon included BusyBox in the firmware for its media products and made the executable version of the firmware available for download on its website without ever offering up the firmware's source.
The plaintiffs argued that this violation of the GPL revoked the contingent license contained therein. With the license to use the software gone, according to the plaintiffs, the distribution of BusyBox infringed on their copyright in the program, and they requested money damages and an injunction preventing any further copying.
Shortly after the SFLC filed the suit, Monsoon released a statement that it had entered into negotiations with the SFLC in order to end the suit by coming into compliance with the GPL's requirements.
Many members of the press (but not El Reg, of course) jumped on this announcement as a declaration that the case had already settled.
Not so, said the SFLC. The organization wanted more than mere compliance. It believed that allowing firms to wriggle out of infringement lawsuits by simply doing what they should have done in the first place would remove any incentive to comply with the GPL, thus robbing it of its teeth.
With the actual settlement announced yesterday, the SFLC got what it was holding out for: money. The agreement includes an "undisclosed amount of financial consideration" for the plaintiffs, and also requires Monsoon to publish the source code, appoint an Open Source Compliance Officer and notify previous recipients of the software about their rights under the GPL.
Cyberlaw aficionados, on the other hand, didn't get what they had hoped for: a legal showdown that would have tested the very foundations of the GPL. Since the case settled, nothing legally binding came out of it, leaving the exact status of the GPL in murky legal waters - especially after a decision handed down in August by a federal judge in California.
That ruling held that plaintiffs could not pursue an injunction under copyright law for a violation of a different flavor of open source license, the Artistic License. Instead, the court treated the attribution requirement contained in the license as a condition on a contract, which foreclosed on the possibility of an injunction, or any other remedy under copyright law.
This removed a major tool for open source rights holders to enforce the Artistic License, and sent ripples of alarm through the open source community. Legal types saw the SFLC's suit as a chance to test the GPL to find out if courts interpreting the GPL would agree with the California judge's reasoning.
Now, however, it looks as though they'll have to wait until the second GPL lawsuit is filed in the US.
Whenever that may be. ®
COMMENTS
Contract conditions.
"Instead, the court treated the attribution requirement contained in the license as a condition on a contract, which foreclosed on the possibility of an injunction, or any other remedy under copyright law."
Then sue for breach of contract. Or simply write the injunction and suitable compensation as a clause in the GPL. You can then sue to get them to comply with it as they are contractually bound.
@ Wrong conclusion, mates!
Not really. Lawyers like precedents as proof of that particular contract/licence etc. being supported by the judiciary. Reaching a settlement just means that the defending party has decided it would be cheaper and easier to settle than to have to drag the whole thing through the courts, wasting time that they could be selling licensed items and making the profits thereon.
Re: Wrong Conclusion
I agree with what you're saying, but I think it mainly comes down to cost and risk.
Many (the majority?) of software houses which use/violate GPL software tend to be small outfits without many resources. Hence why they need to use/rip-off open source software. So, even if they did think they /could/ contest the GPL it's probably cheaper to settle and get on with business.
Plus, the risk of losing such a case would be even more punitive than settling that it's not a risk worth taking.

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Steps to Take Before Choosing a Business Continuity Partner
Enabling efficient data center monitoring
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider