Understanding the New Red Hat-IBM-Google-Facebook GPL Enforcement Announcement (perens.com)
Bruce Perens co-founded the Open Source Initiative with Eric Raymond -- and he's also Slashdot reader #3872. Bruce Perens writes: Red Hat, IBM, Google, and Facebook announced that they would give infringers of their GPL software up to a 30-day hold-off period during which an accused infringer could cure a GPL violation after one was brought to their attention by the copyright holder, and a 60 day "statute of limitations" on an already-cured infringement when the copyright holder has never notified the infringer of the violation. In both cases, there would be no penalty: no damages, no fees, probably no lawsuit; for the infringer who promptly cures their infringement.
Perens sees the move as "obviously inspired" by the kernel team's earlier announcement, and believes it's directed against one man who made 50 copyright infringement claims involving the Linux kernel "with intent to collect income rather than simply obtain compliance with the GPL license."
Unfortunately, "as far as I can tell, it's Patrick McHardy's legal right to bring such claims regarding the copyrights which he owns, even if it doesn't fit Community Principles which nobody is actually compelled to follow."
Perens sees the move as "obviously inspired" by the kernel team's earlier announcement, and believes it's directed against one man who made 50 copyright infringement claims involving the Linux kernel "with intent to collect income rather than simply obtain compliance with the GPL license."
Unfortunately, "as far as I can tell, it's Patrick McHardy's legal right to bring such claims regarding the copyrights which he owns, even if it doesn't fit Community Principles which nobody is actually compelled to follow."
The soft stance taken with GPL violators is an attempt for a peace and love approach to copyleft. This is disappointing when copyleft should really be at war with the copyright tyrants that have repeatedly destroyed lives of so-called pirates with violent para-military raids and freezing of personal assets. The corporate world is playing hard ball, and the open source world wants to string daisy chains.
“Common sense is not so common.” — Voltaire
Are worse than Hitler.
From the article:
Q: Is it true that the principles the four companies announced today are taken from the GPL 3 license, but they are applying them to GPL 2?
A: Yes. If your software is under GPL 3, the same waiting periods that the four companies have promised are required. Thus, it is ironic that when originally presented with the opportunity to apply the GPL 3 to Linux, Linus Torvalds and the Kernel team were quite hostile about it, while the kernel team’s recent announcement attributes the principles they have adopted to the text in GPL 3. Perhaps they’ve learned something since those hostile moments.
I don't see the problem with this. Either way, the deliberately offending party gets held accountable. In fact it would be entirely appropriate for these companies to fund lawsuits like this a la the Gawker case because their interests overlap heavily.
The corporate world is playing hard ball, and the open source world wants to string daisy chains.
Community can be great but isn't enough to make sure our code is used the way we want. Making a choice about what license we are going to use isn't the end of our copyright decision-making. If we want our licenses to be effective, we need to plan for enforcement, for inheritance, and for who will "own" the copyright in our code even if we want our code to be free.
Real lawyers write in C++
So does this mean, VMWare is in for a world of problems, finally?
In case you didn't realize, the original article is the last link. Or you can just look at it here.
Bruce Perens.
If Google, Facebook, IBM, and Microsoft are all banding together to defend the GPL, maybe the GPL isn't in your interests as much as you had once thought.
Copyright isn't capitalism.. Copyright is protectionism. We had capitalism in this country before we started protecting book authors from book publishers. Our copyright system started off as a social program to protect weak individuals from powerful people.
“Common sense is not so common.” — Voltaire
As far as I can tell so far (not having read the actual cases) it's McHardy's legal right. However, the Kernel Team is bothered that it might turn users away from Linux and don't condone his asking people for money. Nor do any community norms I've seen in 20 years approve of his behavior.
Huh? Isn't this about basic copyright enforcement? Party A has copyright. Party A accuses party B of violating that copyright. Party A seeks damages. Party A and B settle in or out of court. That seems definitionally 'norm'al to me. What seems unusual to me is a large, significant group of people that seem to be implying that though they agree with Party A's legal theory, they don't wish Party A to excercise their legal rights in that way, and thus- generate some controversy sold by journalists.
I suspect what may be happening is that the mainstream group is afraid to take the obvious logical action of effectively un-merging the persons code and reimplementing it- because if they did that they'd have to admit to themselves how legally easy it would be for any billion dollar corporation to get away with doing to their subset of that codebase if it ever suited them tactically.
If someone uses GPL code without following the licence, they're committing copyright infringement. All the contributors should be allowed to sue for damages for their pieces of code
> Decompiling is merely an optimization problem [...] you lose comments and (without debug info) function and variable names.
There are folks working on this: https://github.com/eth-srl/Nic.... The idea: use machine learning to look at t lot of code to come up with plausible variable names (the first demonstrator was AFAIR for a Javascript deminifier from ETHZ).
Who knows... perhaps the thing could come up with some useful comments too... I'd bet it'd be better than the Doxygen comments churned out by many a Java sweatshop.
Backup your bs with proof OrangeTide https://it.slashdot.org/comments.pl?sid=11425437&cid=55663429/
APK
P.S.=> See you there (somehow, I don't think I will & you will continue to embarass yourself as you did starting garbage with me - I am going to let YOU finish YOURSELF boy)... apk
Backup your bs with proof OrangeTide https://it.slashdot.org/comments.pl?sid=11425437&cid=55663429/
APK
P.S.=> See you there (somehow I don't think I will & you will continue to embarass yourself as you did starting garbage with me - I am going to let YOU finish YOURSELF boy)... apk
Backup your bs w/ proof OrangeTide https://it.slashdot.org/comments.pl?sid=11425437&cid=55663429/ provide proof of me picking on you 'for years' as you said in the post parent to mine in that link I just posted - you can't.
(If I had issues w/ you I'd have bookmarked it & I never have before YOU came in calling me a "git" (fool) starting hassles!)
* See you there (somehow I don't think I will & you will continue to embarass yourself as you did starting garbage with me - I am going to let YOU finish YOURSELF boy)
Additionally - CLASSIC & PRICELESS: I also CAUGHT YOU posting UNIDENTIFIABLE AC vs. using your registered 'lusername' yet you point to YOUR POST that was done under your REGISTERED 'lusrname' claiming it too (YOU = FLATOUT-BUSTED -> https://slashdot.org/comments.pl?sid=11432439&cid=55667787/ )
SEE YOU DOWNMOD HID THIS 8x TIMES I POSTED IT TOO https://slashdot.org/comments.pl?sid=11430293&cid=55668641/ & https://slashdot.org/comments.pl?sid=11433711&cid=55669021/ + https://slashdot.org/comments.pl?sid=11432725&cid=55669055/ https://slashdot.org/comments.pl?sid=11432725&cid=55669519/ https://slashdot.org/comments.pl?sid=11430293&cid=55669493/ https://slashdot.org/comments.pl?sid=11432483&cid=55666417/ - weak trying to hide it!
APK
P.S.=> This is the 17th time you've done a "Run, Forrest: RUN!!!" vs. it OrangeTide - why's that? I caught you lying?? Cat got your tongue??? Yes, obviously - pitiful... apk