Slashdot Mirror


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."

12 of 96 comments (clear)

  1. Time to begin a move to GPLv3? by gQuigs · · Score: 4, Informative

    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.

    1. Re:Time to begin a move to GPLv3? by Bruce+Perens · · Score: 4, Interesting

      To be fair to the Kernel Team, the major thing they objected to in GPL3 back then was the anti-TiVo-ization terms. These would prevent lock-down of the software such that the end user would be blocked from updating it. I am told that a number of products gained a "developer mode" just to comply with GPL3. This is something we should encourage, IMO. But perhaps the Kernel Team are still more oriented to having companies use Linux than keeping it as Free as I would like.

    2. Re:Time to begin a move to GPLv3? by Bruce+Perens · · Score: 3, Informative

      It's not really impossible, and even the Kernel team has studied the problem with a lawyer and acknowledged this. It's not easy either. Remember, Wikipedia did a some time ago. You have to publish the decision for opposition, and then anyone who opposes it who has code in the kernel has the right to ask for that code to be removed before the change.

    3. Re:Time to begin a move to GPLv3? by Bruce+Perens · · Score: 4, Interesting

      Here's the Wikipedia relicensing. Definitely not easy. I objected to GFDL applied to Wikipedia before this, and they knew that, but I didn't play an active role in this change and there must have been many other people who objected too.

  2. Re:can't we all just get along? by Bruce+Perens · · Score: 4, Informative

    Copyright is not the only possible legal regime. It's just the one we have now. A legal structure supporting openness could exist side-by-side with proprietary copyright.

  3. Re:can't we all just get along? by KiloByte · · Score: 4, Interesting

    Without copyright there is no such thing as the GPL. There is no such thing as copyleft,

    Without copyright, there would be no need for copyleft. Somewhat counterintuitively, it's GPL (v2) rather than BSD/MIT that emulates a world without copyright better: we'd have decompilers.

    Decompiling is merely an optimization problem: make a front-end that takes x86/etc code (these already exist), output C/etc code, optimizing for human readability; you lose comments and (without debug info) function and variable names. The only reason no one wrote a serious decompiler yet is that cases when using source recovered this way are so niche it's not worth the effort.

    For pretty much any interesting program, people would clean up and comment such source, thus there'd be no commercial benefit for keeping the code closed. And, releasing real source means you get better outside contributions, thus cooperating with your users is a win. Ie, we'd have an all-GPL world.

    I specified GPLv2, as there exist a way around decompilers: DRM. Of course, doing so on a general-purpose CPU would be mere pointless obfuscation (just run the thing in an emulator and dump memory when decrypted), thus such evil CPU would need to include sealed DRM chips. But, the corp would still have to give the user both the lock and the key: decapping is not that simple, but it can be done, immediately breaking all DRMed code runnable by the chip that got decapped. DRM is physically impossible, it serves merely as a stumbling block. At this point, it'd be so niche that no company would really bother, turning the tables to what we have now with decompilers.

    We'd end with a prisoner dilemma world where everyone cooperates, instead of current population of defectors.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  4. Re:can't we all just get along? by Bruce+Perens · · Score: 4, Insightful

    The thing about going to war is that you have to win.

    If your goal is having as many users as possible, you don't set out to use the GPL. Inherent in that choice you are rejecting some users in favor of gaining a better bargain for everyone else. The Kernel Team still has trouble dealing with this.

  5. Re:VMWare by Bruce+Perens · · Score: 3, Informative

    So does this mean, VMWare is in for a world of problems, finally?

    No. Last I heard (and many people are not aware of this) the VMWare case was under appeal in Germany. Meaning that VMWare could still lose. However, VMWare has been given cure periods far in excess of the ones mentioned here.

  6. Re:can't we all just get along? by KiloByte · · Score: 3, Informative

    The prisoner's dilemma doesn't result in everyone cooperating. If it did, then it wouldn't be a dilemma.

    If the reward for defecting is small enough, and the population punishes defectors enough, it's a smart play to cooperate. If the payoffs are (5,0), (3,3), (0,5), (1,1), you can get 5 once then nothing but 1s for the rest of your life -- while everyone else keeps getting 3s. On the other hand, if you're in a population of defectors, cooperation is suicidal. Note that in a world of cooperation, the average person fares drastically better.

    But alas, we live in a world where defectors buy themselves draconian copyright laws, and attempt to make cooperation illegal (like FCC rules or Article 13 of the EU Copyright Directive).

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  7. Original Article by Bruce+Perens · · Score: 4, Informative

    In case you didn't realize, the original article is the last link. Or you can just look at it here.

  8. Re:GPL violators by julian67 · · Score: 3, Insightful

    They may or may not have been worse than Hitler, but Hitler is not worse than Hitler.

    To be less flippant:

    Of Hitler, Mao, Stalin, and Muhammad it seems that Hitler is the only one who sought to murder millions of people as a matter of policy, on principle as it were. The others murdered millions of people, evidently many more millions in the cases of Stalin and Mao, incidentally. The moral import of this escapes me. To be in fear is to be in fear. To be murdered is to be murdered. The scale of the crimes defies my ability to assess or differentiate.

  9. Re:Bad cop by Bruce+Perens · · Score: 3, Insightful

    Creating a Laches (which is what you are talking about) isn't really the same as placing something in the public domain. Laches means you waited for economic demand for the infringing product to develop before you brought the lawsuit, presumably to enrich your income. It doesn't apply to the next new infringer to come along.

    Also, be careful not to confuse it with trademarks going into the public domain.