News for hackers. Stuff that matters.
Re:Linux beats legal threat from one of its own developers by julienfr112 on Sunday March 11, 2018 @04:45PM (#16564669)
In fact, he acted like a bounty hunter : chasing wrongdoers ( companies that do not comply with the GPLv2) for his own personal gain. If you are serious about the GPL license, you should also be serious about punishing companies that violate it. And if the Free Software Foundation has not enough guns, why not let bounty hunters do the job ?
Re:Linux beats legal threat from one of its own developers by LukeShu on Monday March 12, 2018 @12:16AM (#16566176)
Several things:

The FSF, and the SF Conservancy (which does the bulk of GPL enforcement) espouse Community-Oriented GPL Enforcement[1]. The goal of Community-Oriented Enforcement is compliance, not punishment.

[1]: https://www.fsf.org/licensing/enforcement-principles

McHardy wasn't seeking compliance. He was saying "Your license to my portions of the kernel was automatically revoked when you did X. Pay me damages." This could arguably work as a deterrent, but it does nothing to fix the current violation.

Additionally, a problem with the GPLv2 is that it is automatically revoked upon violation, and has no reinstatement clauses. If a company violates the GPLv2, and then the SF Conservancy enforces the GPL against them, after it's all worked out, the SF Conservancy can reinstate the license to the portion of the code that the SF Conservancy owns or represents the owners of, but there's still quite a bit of code for which the infringer technically hasn't had its license reinstated for. Even after working everything out with the SF Conservancy, McHardy could say "Ok, but they didn't reinstate your license to the portion of the code that I own. You're infringing on my copyright, pay me damages."

Re:Linux beats legal threat from one of its own developers by forapurpose on Monday March 12, 2018 @02:48AM (#16566572)
Thanks; that's very informative.

> The goal of Community-Oriented Enforcement is compliance, not punishment.

Is there some record of the debate, if any, that led to this policy? Clearly, financial costs are a deterrent that leads to compliance. Many laws, regulations, and contracts achieve compliance in this manner. That doesn't make the FSF's position wrong, but I wonder how they reached it.

The FSF agrees, to an extent: https://www.fsf.org/licensing/enforcement-principles

Community-oriented enforcement must never prioritize financial gain. Financial penalties are a legitimate tool to achieve compliance when used judiciously. Logically, if the only penalty for violation is simply compliance with the original rules, bad actors will just wait for an enforcement action before even reading the GPL. That social model for copyleft and its enforcement is untenable and unsustainable. An enforcement system without a financial penalty favors bad actors over good ones, since the latter bear the minimal (but non-trivial) staffing cost of compliant distribution while the former avoid it ...

Re:Linux beats legal threat from one of its own developers by afarrell on Monday March 12, 2018 @04:53AM (#16566871)
> deterrent that leads to compliance

Note about general principles: a deterrent needs more than pain to ensure compliance.

* There also needs to be a clear path to compliance. If the subject of a rule isn’t capable of complying, they won’t comply.

* Knowledge about the possibility of violation & penalty needs to be available to the subject.

* There needs to be consistency in what will ensure compliance. Otherwise, the subject is better off taking out insurance, raising their prices, and accepting fines as a cost of business. Or getting out of the situation entirely.

————————-

There is a story from somewhere (possibly the warring states period of pre-Han China?) of a general who was late returning from an engagement.

General: “what is the punishment for lateness?”

Aide: “death.”

General: “and and what is the penalty for mutiny?”

Aide: “also death.”

General: “Well, I suppose mutiny gives us a chance of survival. Summon the captains.”

Re:Linux beats legal threat from one of its own developers by ubernostrum on Tuesday March 20, 2018 @01:15PM (#16630519)
The possibly-apocryphal story of the first Han ruler, Emperor Gaozu (pre-regnal name Liu Bang), is that he was overseeing the transport of convicts when some escaped. Since the penalty for allowing an escape was death, he released all of the convicts, went into the mountains and became the leader of an outlaw group which came out on top after the fall of the Qin dynasty.

https://en.wikipedia.org/wiki/Emperor_Gaozu_of_Han

Re:Linux beats legal threat from one of its own developers by forapurpose on Monday March 12, 2018 @06:05PM (#16572121)
Excellent points, and great story. Thanks.
Re:Linux beats legal threat from one of its own developers by cup-of-tea on Monday March 12, 2018 @04:58AM (#16566882)
So, in fact, there's no real way to "fix" the violation for a project like Linux. It could be done with FSF projects because they own the copyright too. But for Linux it would seem the only way to enforce compliance is to make people aware that their licence will be lost forever, and the only way to make them care about that is the threat of legal action from any one of thousands of developers.

Otherwise how else will compliance for Linux be enforced?

Re:Linux beats legal threat from one of its own developers by detaro on Sunday March 11, 2018 @04:52PM (#16564712)
Because the Linux Kernel community doesn't do enforcement like that not because they don't have enough guns, but because they believe it to be harmful to the overall ecosystem. If you plan to slowly herd them to where you want them, a bounty hunter taking loud potshots scaring everyone doesn't help.

The theory is that a violating Linux-based device where you can try to get the manufacturer to fix this in the future is better than a device with a closed system and no chance of getting it opened because the manufacturer was scared of legal consequences of using Linux.

Re:Linux beats legal threat from one of its own developers by belorn on Monday March 12, 2018 @04:00AM (#16566744)
Its hard to say with any amount of certainty what the 15000 developers from practically every country in the world believes in regard to copyright.

FSF and the SF Conservancy is attempting to try to bring a consensus to that issue, but that too is a contentious discussion. Some vocal developers has some views, the Linus Torvald has his, the Linux Foundation has theirs, and not counting everyone else which has a stake in the issue. In general it seems that the overall ecosystem seek compliance but I suspect even the effort to try establishing that as a consensus and have it written down as an official policy of the project would be an uphill battle.

An interesting aspect that this judge brought on is the statement that the 15000 developers should not be considered co-authors of the linux kernel as a whole but rather defined in the German law as "editing authors" with limited rights compared to co-authors. It might mean that Linus, if any, is the only one that can make enforcement for the project as a whole.

Re:Linux beats legal threat from one of its own developers by na85 on Sunday March 11, 2018 @11:52PM (#16566102)
If they don't care about companies leeching off of free work, why not license it under BSD?

The whole point of the GPL is that it's an enforceable license.

Re:Linux beats legal threat from one of its own developers by deathanatos on Monday March 12, 2018 @12:06AM (#16566144)
They do care about companies leeching off of free work, is the point; they just don't want the outcome to be financial gain, rather, they want the companies to stop "leeching", and rather contribute their contributions back to the community, so that others can benefit from the work just as they benefited from the work those before them did.

(This "contribute back" aspect is, IMO, the core difference between MIT/BSD and the GPL.)

Re:Linux beats legal threat from one of its own developers by belltaco on Monday March 12, 2018 @12:17AM (#16566178)
But the companies that are forced to pay out large amounts are going to be more careful next time and release their contributions as source code. Same with other companies that see this going on. That's a win for Linux and GPL code.
Re:Linux beats legal threat from one of its own developers by shakna on Monday March 12, 2018 @01:02AM (#16566312)
In my experience, they'll either be much more careful about hiding their reliance, or just strip Linux out of everything. Not contribute back.
Re:Linux beats legal threat from one of its own developers by pbhjpbhj on Monday March 12, 2018 @06:26AM (#16567166)
And you think by not punishing such companies then they'll come in to compliance?

It strikes me such companies never intended to comply with their legal obligations - make that position financially untenable and use the money to support development/developers who are compliant.

Re:Linux beats legal threat from one of its own developers by shakna on Monday March 12, 2018 @07:09AM (#16567335)
That's not my position either.

Most companies will see a lawsuit as an attack, and blacklist interacting with you in the future if they can. It reflects badly on the FOSS community, and makes future interactions even more difficult. There are a lot of businesses that will fight relying on any FOSS product, but leap at precisely the same thing with a paid license.

However, more polite requests usually get canned without reading.

This is a tough problem, with hypersensitive businesses thrown in the mix. Wielding the GPL like a hammer won't help, but ignoring it won't either.

Re:Linux beats legal threat from one of its own developers by crdoconnor on Monday March 12, 2018 @08:29AM (#16567710)
>Most companies will see a lawsuit as an attack, and blacklist interacting with you in the future if they can. It reflects badly on the FOSS community, and makes future interactions even more difficult. There are a lot of businesses that will fight relying on any FOSS product

The companies that will strip out FOSS from all of their products will have to cripple their product, increase their lead times and increase their costs - possibly all three.

If FOSS is competing with their closed source product, that makes FOSS more competitive. If companies that respect FOSS compete with their product, that makes them more competitive. These are good things.

I don't think it pays to accommodate companies with laywers that behave irrationally in response to enforcement of the GPL and it certainly doesn't pay to respond to bully tactics by relenting.

Re:Linux beats legal threat from one of its own developers by vbezhenar on Monday March 12, 2018 @10:15AM (#16568234)
When Microsoft sues companies for using pirate Windows, they extort extra fines and payments and put people in jail. It doesn't seem to hurt them. FSF position is weak. If you're not fighting with claws and teethes, strong ones won't respect you, they'll continue to abuse you just to "comply" if they got caught and sued.
Re:Linux beats legal threat from one of its own developers by older on Monday March 12, 2018 @04:40AM (#16566838)
Could you give an example? Any company that stripped Linux out of their product?
Re:Linux beats legal threat from one of its own developers by shakna on Monday March 12, 2018 @06:28AM (#16567181)
Not without breaching an NDA.

But how about a public case?

Verizon got caught breaching the GPL with Busybox.[!] At the end of the day, they agreed to become compliant... And Busybox is no longer a product they use or distribute. [0][1]

[!] https://www.softwarefreedom.org/news/2008/mar/17/busybox-ver...

[0] https://www.verizon.com/support/residential/internet/equipme...

[1] https://github.com/verizon

Re:Linux beats legal threat from one of its own developers by phaemon on Monday March 12, 2018 @08:18AM (#16567655)
Your link [1] has a link to a page with the Actiontec firmware downloads that includes Busybox. They clearly are still distributing it and are following the complience agreement. This appears to be an example that is the direct opposite of what you were trying to show.
Re:Linux beats legal threat from one of its own developers by older on Tuesday March 13, 2018 @11:16AM (#16576781)
Busybox != Linux.
Re:Linux beats legal threat from one of its own developers by teddyh on Monday March 12, 2018 @11:24AM (#16568737)
Both Google and Apple are working hard on it.
Re:Linux beats legal threat from one of its own developers by Hydraulix989 on Sunday March 11, 2018 @11:45PM (#16566074)
Tell that to Richard Stallman.
Re:Linux beats legal threat from one of its own developers by icebraining on Monday March 12, 2018 @03:40AM (#16566692)
As others have pointed out, the FSF (founded and headed by Stallman) has the same position.
Re:Linux beats legal threat from one of its own developers by sametmax on Sunday March 11, 2018 @11:44PM (#16566072)
But if the licence is not enforced, then what's the point of writing it or using it ? Put it under WTFL. Shorter, less paper work.
Re:Linux beats legal threat from one of its own developers by dizzystar on Monday March 12, 2018 @02:17AM (#16566487)
If it was under WTFL, the company would be able to release everything closed-source, which is exactly what the open source community is trying to discourage.

It also makes no sense to sue the companies violating the licenses. They would be more inclined to move to a closed-source option with a known fee, since the very product you are using has an ambiguous cost attached to it.

For example, I have deep disdain for people who build up WordPress or Drupal sites for clients and flat out refuse to let the customer have their code, but that still doesn't mean they should get sued to oblivion, no matter how much I disagree with this practice.

If you are for open source, you want to actively encourage the use of these platforms (regardless if you think they are trash) instead of having these people move over to some equally bad system. This is worse for the OSS community. It's also worse for the customer, since hidden fees for MS or Oracle will be tacked onto the product price. If word got out, even those who follow GPLv2 to a T would have reason to be nervous, so they'd just migrate off the platform as well.

Re:Linux beats legal threat from one of its own developers by sametmax on Monday March 12, 2018 @02:26AM (#16566516)
> If it was under WTFL, the company would be able to release everything closed-source, which is exactly what the open source community is trying to discourage.

Apparently they already can. If there is no enforcement, what prevents anybody from doing it ? Good will.

> but that still doesn't mean they should get sued to oblivion, no matter how much I disagree with this practice.

Remove "should" and "to oblivion", and the result seems reasonable. After all, we can't give tickets like for speeding for those infraction. The only problem with sueing here is the cost of it.

But it's perfectly alright from a moral point of view. People worked hard, sometimes for free, for free software to exist, out of idealism. The only thing they demand is to accept the licence.

Re:Linux beats legal threat from one of its own developers by wiz21c on Monday March 12, 2018 @03:35AM (#16566675)
Yup, all of that is strange. Because if enforcement is rare, then a simple risk analysis allows everyone to leech without contributing back. Even more so if the only punishment you may have is "comply" (publishing code that is tied to your own personal hardware is not that much a problem, I think).

Now that everybody knows the true political aim of the GPLv3 and that we know the pragmatism of BSD and others, I wonder under what license would the kernel have been published today...

Re:Linux beats legal threat from one of its own developers by tpxl on Monday March 12, 2018 @05:58AM (#16567059)
>publishing code that is tied to your own personal hardware is not that much a problem, I think

Code tied to your own hardware can lead to reverse engineering and creating other software to be used with said hardware. This is a good thing (for the user) though.

Re:Linux beats legal threat from one of its own developers by icebraining on Monday March 12, 2018 @03:43AM (#16566702)
The only thing they demand is to accept the licence.

Well, the problem here is that they're actually demanding a few million euros.

Re:Linux beats legal threat from one of its own developers by boomlinde on Monday March 12, 2018 @05:40AM (#16566993)
> It also makes no sense to sue the companies violating the licenses. They would be more inclined to move to a closed-source option with a known fee, since the very product you are using has an ambiguous cost attached to it.

It makes perfect sense to sue a company that fails to comply with the license. What doesn't make sense is for anyone with a two line contribution to the kernel to sue anyone for not complying with the license. I like the way free software enforcement organizations approach this currently. Represent the community as a whole, ask nicely first, sue if that doesn't lead to compliance.

> For example, I have deep disdain for people who build up WordPress or Drupal sites for clients and flat out refuse to let the customer have their code, but that still doesn't mean they should get sued to oblivion, no matter how much I disagree with this practice.

It means that they should comply with the license or possibly face legal consequences. If that means that they'll get sued to oblivion, that's their responsibility. If the customer can't see the code, however, there's a chance that the customer doesn't have a copy of the software (e.g. if it's running on a server that the contractor is maintaining) in which case GPLv2 doesn't give the customer the right to see the code making the example completely irrelevant.

> If you are for open source, you want to actively encourage the use of these platforms (regardless if you think they are trash) instead of having these people move over to some equally bad system. This is worse for the OSS community.

Why would I want to encourage anyone to build a platform using my GPLv2 software if they don't honor the license? Their use of my software gives no value to me if their changes aren't public. If a system is built on a Linux kernel that we never get to see the source of, its value compared to "some equally bad system" is exactly that, equal. It's proprietary software, and the only difference from some other proprietary system is that it's also illegal.

So as the proprietor of a piece of GPL software that gets used illegally, you're given the choice of a) having the non-compliant user continue violating your rights, the free software community having absolutely nothing to gain from it, or b) having the non-compliant user forced by a court to comply with the license, release the contribution and pay damages to you. The choice seems simple.

> It's also worse for the customer, since hidden fees for MS or Oracle will be tacked onto the product price.

In which case the company will have a hard time competing with the many others that are able to honor free software licenses and both benefit from and contribute to the free software community. How bad is that?

> If word got out, even those who follow GPLv2 to a T would have reason to be nervous, so they'd just migrate off the platform as well.

It's a very simple license to honor. If you don't want to honor it it means that you are either too lazy to care about licenses or that you've made changes of a proprietary nature that you don't want to share. Either way, malevolent.

Re:Linux beats legal threat from one of its own developers by dizzystar on Monday March 12, 2018 @06:14AM (#16567131)
I agree in some sense. My issue is pulling the trigger to fast and too hard, and there doesn't seem to be a good answer to that.

Even though I do my best to follow licenses, I may be making a mistake somewhere. If I heard a case where was sued for $1M to a GPLv2 software, I'd strongly consider moving over to a propriety product and pay $10 a month to mitigate my risk.

Remember that every uninstall is one less user, which is one less incentive to maintain the product, and once that gets close to zero, it's game over.

Re:Linux beats legal threat from one of its own developers by pbhjpbhj on Monday March 12, 2018 @06:34AM (#16567200)
If you heard of a case where someone without a driving license was punished, would you - having done your due diligence to get a license and conky with its requirements - get worried you also would be punished and so choose to always take taxis?

Are these non-compliant companies using cracked versions of other closed-source software? I'll bet they pay for their MS licenses, because they know MS will sue them if they don't.

Re:Linux beats legal threat from one of its own developers by dizzystar on Monday March 12, 2018 @07:41AM (#16567483)
Of course there are companies using cracked versions of software.

We also know kids use all sorts of cracked software as well. The reason they don't get sued is because the companies know that it is bad blood to sue. They know that, in the future, these kids will be running offices and they will buy that software they loved.

Granted, the goodwill ends up with money coming in, but it's the same theory with open source. Most large projects are backed by companies that earn millions. The idea of a single dude doing free work is often times a myth.

Re:Linux beats legal threat from one of its own developers by boomlinde on Monday March 12, 2018 @09:34AM (#16568018)
> Even though I do my best to follow licenses, I may be making a mistake somewhere.

There are plenty of resources available on how to comply and how to setup a process to minimize this risk. Simply dump all the versions and licenses of third party software you use to a file and accompany your distribution with a written offer to share the source code or links to their official repositories if they are unmodified.

> If I heard a case where was sued for $1M to a GPLv2 software, I'd strongly consider moving over to a propriety product and pay $10 a month to mitigate my risk.

You're considering this from the perspective of an end user? Let me clarify that the limitations of GPLv2 kick into effect once you distribute software. As far as respecting copyright goes, you can use GPL software and modify it freely without any legal forethought. It's when you distribute such software that you'd get in trouble by not also sharing the source code.

In fact, this is better for the consumer, who will be able to use the bundled GPLv2 licensed software without buying the product.

> Remember that every uninstall is one less user, which is one less incentive to maintain the product, and once that gets close to zero, it's game over.

This implies that the amount of users is the only incentive when it really is not, For one, some users are more important than other users. Companies like Intel, Google, IBM, SUSE, Red Hat and AMD are important users in that they also make significant contributions to the kernel for their own benefit. There is a huge incentive for these to contribute back even if they don't need to distribute their changes because getting it into the mainline kernel simplifies maintenance. Whether some Shenzhen set top box that violates the GPL uses Linux doesn't make a difference. If anything, their continued illicit use detracts from the credibility of the license and discourages contributors that give a hoot about people respecting their individual property and the overall philosophy of free software. Then, particularly for smaller projects than the kernel, there are the individual contributors who are usually users of the software they contribute to.

I think you've maybe made the connection "users == customers" where there is none. In those terms, companies that ignore free software licenses are simply pirates.

Re:Linux beats legal threat from one of its own developers by greglindahl on Monday March 12, 2018 @01:40AM (#16566387)
The license is enforced, just more gently than some might want.
Re:Linux beats legal threat from one of its own developers by sametmax on Monday March 12, 2018 @02:26AM (#16566520)
Define "gently", because that doesn't seems like a term that goes well with enforcement, which contains the root "force".
Re:Linux beats legal threat from one of its own developers by greglindahl on Monday March 12, 2018 @02:35AM (#16566539)
The definition has already been given in the other comments in this discussion about how the community prefers enforcement to be done.
Re:Linux beats legal threat from one of its own developers by sametmax on Monday March 12, 2018 @02:48AM (#16566574)
No it hasn't.

That's not enforcement.

The community choose not to enforce. "gently" has nothing to do with it.

I get that this is a preference, and they make the software and choose the licence so this is their choice.

But that's not enforcement.

It basically means you can do whatever you want with it.

And hence people do.

The system works because a few are giving away a lot while most benefit from it with taking without giving back anything.

This is why everything is behind an API paywall now. This is why XMPP is getting shut down. This is why IMAP is being replaced by proprietary front ends. Why we have DRM in HTML5. Why TiVo did what it did.

Because, well, we let them.

Re:Linux beats legal threat from one of its own developers by icebraining on Monday March 12, 2018 @03:47AM (#16566718)
This is why everything is behind an API paywall now. This is why XMPP is getting shut down. This is why IMAP is being replaced by proprietary front ends. Why we have DRM in HTML5. Why TiVo did what it did.

In what way would a vigorous enforcement of the GPL prevent any of that?

The only even remotely related to the GPL is TiVo, and even then it wasn't lack of enforcement, the version of the license simply didn't prevent it, hence GPLv3.

Re:Linux beats legal threat from one of its own developers by julienfr112 on Monday March 12, 2018 @04:31AM (#16566810)
oxymoron, right ? like a benevolent punishment, a liberating constrain ...

Come on, we are in the same boat here, we agree Linux (and Wikipedia and ...) are amazing things. And we all admire and cheer the contributors and so on. Don't be mad when we point a small incoherence. It's like opening an issue, close it if you have a large support of the community, but please, spend 5 minutes thinking about it from a new point a view.

Re:Linux beats legal threat from one of its own developers by megous on Sunday March 11, 2018 @11:32PM (#16566042)
Because the goal is achieving compliance (something that would benefit everyone), not punishment (something that just benefits the author).
Re:Linux beats legal threat from one of its own developers by geezerjay on Monday March 12, 2018 @05:28AM (#16566957)
It's also rather obvious that pursuing a policy based on punishment would hinder the adoption of any software licensed under any free software license, and also have a negative impact on the community's public image.
Re:Linux beats legal threat from one of its own developers by pbhjpbhj on Monday March 12, 2018 @06:39AM (#16567212)
I don't see how that's clear at all - it's only harming those who knowingly choose not to comply. Suing such people says we care about making software (F)OSS, we care enough to ensure people who make a profit from open source give back to the community.
Re:Linux beats legal threat from one of its own developers by exikyut on Monday March 12, 2018 @12:18AM (#16566182)
Because there's no legal and/or social infrastructure in place that demands the bounty hunter shares their winnings.

The way things are right now, the bounty hunter could argue that the very idea of the statement above is absurd - and that demonstrates how broken things are.

I can't help but agree more and more as time goes by that maybe Linux is getting too big for its own good. I do wonder how it'll topple.

Re:Linux beats legal threat from one of its own developers by pbhjpbhj on Monday March 12, 2018 @06:46AM (#16567241)
There's legal precedent. If one dev proves their copyright was infringed by failure to comply with the contractual obligations set through the OSS license, then the court more than likely will find for every other dev too. The "bounty hunter" will get paid the damages against them, not the damages against the community, there's no reason to disperse them.

If someone does a hit-and-run and hits several people with their car, one of those people suing and getting damages from the malfeasant isn't a bad thing, nor is it something we should frown on IMO.

Re:Linux beats legal threat from one of its own developers by exikyut on Tuesday March 13, 2018 @12:21AM (#16573859)
This is very correct, and I can't argue with it.

However, the basis of this post was that one person's actions were exploitative from the perspective of the community.

I'm just saying it's sad that there wasn't sufficient precedent of some kind to dissuade what happened from occurring.

Re:Linux beats legal threat from one of its own developers by emiliobumachar on Monday March 12, 2018 @09:30AM (#16567992)
Quoting from another top-level comment:

"If anyone needed another reason to avoid GPL software here you go. I thought the whole idea of open source was to avoid litigious assholes."

The FSF would be disinterested in the spread of this sort of thinking. That's a good reason against letting bounty hunters loose.