The rise of copyright trolls
The rise of copyright trolls
Posted May 2, 2017 22:36 UTC (Tue) by Cyberax (✭ supporter ✭, #52523)In reply to: The rise of copyright trolls by armijn
Parent article: The rise of copyright trolls
GPLv2 is a smallish two-page text. Putting it along with your software is enough, no need for CD.
My lawyers assured me that printing: "Warning! Code may contain peanuts^W GPL, see the full license and source code at: http://..." is enough to comply.
Posted May 2, 2017 22:43 UTC (Tue)
by armijn (subscriber, #3653)
[Link] (11 responses)
Posted May 3, 2017 6:20 UTC (Wed)
by paulj (subscriber, #341)
[Link] (10 responses)
I seem to get volumes of paper with most electronics that I buy, even trivial bits of electronics. Yet, a copy of the GPL and a URI is a problem?
Posted May 3, 2017 7:21 UTC (Wed)
by armijn (subscriber, #3653)
[Link] (9 responses)
Posted May 3, 2017 8:30 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
"7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License."
So either you get a waiver for the legal requirements or stop distributing a GPL-ed product. As of now there are no laws preventing putting a tiny printed GPLv2 text with a product.
I have very few sympathies to companies that violate GPL and I absolutely welcome any attempts to bring compliance, even by trollish methods. I'd gladly contribute to a fund that will extend this trolling to all other companies that ignore GPL.
This is quite selfish - we spend time making sure our products are license-clean (either no GPL or GPL with source code offer) and I absolutely detest that many of our competitors can just wave away all the compliance issues.
Posted May 3, 2017 12:35 UTC (Wed)
by paulj (subscriber, #341)
[Link] (7 responses)
Is it the fact that he sends Cease and Desist letters?
Is it that he offers to help them become compliant, in return for a fee for his time (which this article describes as 'modest')?
Is it that he has them sign an undertaking to remain in compliance from there on in, with penalties for further non-compliance?
Is it the size of those penalties for further non-compliance?
Is it the threat of injunctions?
What exactly is it that free software developers are not allowed to do, to enforce their copyright?
Posted May 3, 2017 12:51 UTC (Wed)
by armijn (subscriber, #3653)
[Link] (6 responses)
This is one of the reasons is why Shane and I wrote this new (free of charge) guide we just published to get the companies up to speed.
Posted May 3, 2017 21:08 UTC (Wed)
by paulj (subscriber, #341)
[Link] (5 responses)
- I can not recover my costs in the time I spent to show there was infringement, unless I also provide further time consulting with them on how to come into compliance?
What if I have another job and I am not at liberty, via conditions of employment and/or time, to go and do other licence compliance consulting? I simply am not allowed to try get infringers to honour the licence to my code?
I think precision is very important here.
Posted May 3, 2017 21:17 UTC (Wed)
by paulj (subscriber, #341)
[Link]
Which makes me think the answer isn't to find a way to stop people from enforcing the licence on their code, but to provide some kind of service to these companies to help them with compliance. Possibly the only "social contract" change needed then is to have those who initiate enforcement actions be required to refer to the subject to a reputable or neutral compliance advice service
From what you say, McHardy did refer people to GPL resources in his actions. He's hardly obligated to provide further legal advice to them. Indeed, my experience of lawyers is that they strongly advise you to _not_ try give any legal-ish advice to any parties you have a complaint with - so I doubt that someone pursuing a GPL infringement would ever want to do anything more than provide a link to a neutral website.
Posted May 3, 2017 21:44 UTC (Wed)
by armijn (subscriber, #3653)
[Link] (3 responses)
Approaching companies with a fairly innocent request, tricking them into signing a contract (at which point it is no longer about the license, but about the *contract*) and then coming up with the most bizarre interpretations of the license to show that companies are breaching the contract to milk them for a lot of money under the guise of compliance while not actually helping companies despite companies actively asking for help (and simply letting them figure it out themselves), and then hitting them again over and over again crying about non-compliance is simply immoral. It has nothing to do with compliance, or helping free software. It is ordinary trolling.
Enforcement and helping free software can actually go hand in hand: when I was helping out at gpl-violations.org we tried to make sure to start a dialogue with the companies to find out where their issues were and how to help them further. There it served as a wakeup call to companies. With McHardy it is scorched earth.
Posted May 22, 2017 7:43 UTC (Mon)
by ras (subscriber, #33059)
[Link] (2 responses)
Others have commented how this is a GPL v2 problem mostly fixed by GPL v3. IMO GPL v3 is a would be a truly worthy successor on GPL v2, if it weren't "Installation Information" brain fart that renders ended up rendering it incompatible with the way most software is distributed nowadays (app stores). (I give Moglen credit for the beauty and clarity of the writing in GPL v3, but as one of the great intellects behind it he must shoulder a fair portion of the blame for this mistake. I'm sure it's the main reason for it's poor uptake to date.)
But there is a fix patch for GPL v3. You can neuter that rule. I am no lawyer so so I pinched this para from a fsf lawyers blog post, where he praised it (or maybe didn't criticise it - which I took as praise):
> The copyright holders grant you an additional permission under Section 7 of the GNU Affero General Public License, version 3, exempting you from the requirement in Section 6 of the GNU General Public License, version 3, to accompany Corresponding Source with Installation Information for the Program or any work based on the Program. You are still required to comply with all other Section 6 requirements to provide Corresponding Source.
Add that little snippet, and you have an excellent successor for GPL V2. I wish more people would do it because GPL v3 is so much better than GPL v2 in so many ways.
Posted May 22, 2017 8:16 UTC (Mon)
by Cyberax (✭ supporter ✭, #52523)
[Link] (1 responses)
Posted May 23, 2017 14:40 UTC (Tue)
by bronson (subscriber, #4806)
[Link]
Posted May 3, 2017 3:35 UTC (Wed)
by bronson (subscriber, #4806)
[Link] (5 responses)
> There are some "more exotic" complaints too, Radcliffe said, including that the GPL text distributed is not translated into German or that the source offer should not come from the parent company; there are others that are even more odd.
You probably want to find some more careful lawyers.
Posted May 3, 2017 3:41 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link] (4 responses)
These are the sorts of the complaints that are usually tucked onto a larger litigation ("murder, arson and jaywalking" style). I very much doubt that he's suing solely for GPL not being translated into German.
Also keep in mind that German law is pretty harsh towards frivolous lawsuits.
Posted May 5, 2017 6:41 UTC (Fri)
by bronson (subscriber, #4806)
[Link] (3 responses)
The point is: this stuff is complex and open to interpretation. Your comments seem to show this, even though you claim otherwise.
If you can find a reputable lawyer to agree that printing "Contains GPL, see license at http://blah" on a slip of paper is clearly sufficient, then I'm interested. Until then, I don't think anyone's going to stake their company on advice found in a LWN comment.
Besides, I bet McHardy could find compliance issues in the paper type and font size...
Posted May 5, 2017 9:27 UTC (Fri)
by farnz (subscriber, #17727)
[Link] (2 responses)
At a former employer, we had a serious lawyer say exactly that. Of course, what had to be present at http://blah/ was more than just the licence text - we also had to provide full GPL sources for all the software we shipped, and detailed build instructions to enable you to rebuild and replace any GPL software on the devices we shipped with your own build.
Indeed, our lawyer actually suggested that we could go further - we already put a sticker on the device with MAC address and serial number - we could simply put "Software licence details at http://blah/ - you have rights" on that sticker, and as long as http://blah was correctly set up to cover the licence requirements, they'd defend us pro-bono. We also ran this past the FSFE, who verified our instructions on the web site, and then were willing to write a letter telling us that in their opinion, we were compliant given the sticker or the slip of paper. Further, there was no issue with the idea that to get support from us, you had to restore our original software, or with us shipping "surplus" source (e.g. we used gdb internally for debugging - we didn't install gdb on shipped devices, but we could still choose to offer you gdb source code).
This did lead to some challenges for us (we had to come up with a process to let you rebuild things that we shipped outside our infra, to let you reinstall binaries on the product in such a way that it was tamper-evident for our support team, and to reset back to a clean state), but we made it work.
Posted May 5, 2017 15:28 UTC (Fri)
by bronson (subscriber, #4806)
[Link] (1 responses)
If you ever felt like turning this into an article or a blog post, I'd be interested to read more.
Posted May 7, 2017 15:13 UTC (Sun)
by pboddie (guest, #50784)
[Link]
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
You're joking, right?
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
The rise of copyright trolls
