Slashdot Mirror


Microsoft Excludes GPLv3 From Linspire Deal

rs232 writes to tell us that Microsoft is excluding any software licensed under the new GPLv3 from their recent patent protection deal with Linspire. "Microsoft has since been treating GPLv3 software as though it were radioactive. 'Microsoft isn't a party to the GPLv3 license and none of its actions are to be misinterpreted as accepting status as a contracting party of GPLv3 or assuming any legal obligations under such license,' the company said in a statement released shortly after GPLv3 was published on June 29. In addition to excluding GPLv3 software from the Linspire deal, Microsoft recently said that it wouldn't distribute any GPLv3 software under its SUSE Linux alliance with Novell, even as it maintains in public statements that the antilawsuit provisions in the license have no legal weight. "

10 of 342 comments (clear)

  1. The GPLv3 works by A+beautiful+mind · · Score: 3, Interesting

    Microsoft has since been treating GPLv3 software as though it were radioactive.
    Great news!
    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
    1. Re:The GPLv3 works by kripkenstein · · Score: 5, Interesting

      Great news!
      As you and others said, if Microsoft is so worried about the GPL3, then the GPL3 must be on the right track. However, that isn't the real story here, as I see it.

      The real story is how Microsoft changed its patent covenant, after the deal with Linspire was already finalized. Is Microsoft free under that deal to alter the patent covenant however they want - making it useless?

      Not that the deal was useful for anything previously either. It doesn't cover 'clone products' - which perhaps includes OpenOffice and Wine, and it doesn't cover 'video game applications designed to run on a computer', nor 'unified communications', nor a long list of other things. Does it cover anything at all?
  2. Re:So what? by RiffRafff · · Score: 4, Interesting

    True, but it would seem to me to undercut much of the Novell deal if a large percentage of the software in the distribution went to GPL3.

    --
    "I might have made a tactical error in not going to a physician for 20 years." -- Warren Zevon
  3. Does Linspire have any market share? by jkrise · · Score: 3, Interesting

    So many firms have merely pretended to be at war with Microsoft - only to cave in later and become partners - Novell and Linspire being recent cases. Have any significant no. of customers actually signed up with Linspire for patent protection? I don't think so.

    Microsoft's Covenant to Customers (Linspire's customers it would seem - not Microsoft's) hardly makes compelling business sense to consider Linspire for the business desktop. Few home users would consider themselves vulnerable to patent lawsuits by Microsoft, if they used Linux.

    So this announcement merely indicates that GPL3 has won, and Microsoft has been compelled to publicly qualify their pre-negotiated deals with business partners, and customers gain more from GPL3 than covenants from Microsoft.

    --
    If you keep throwing chairs, one day you'll break windows....
  4. Re:So what? by Ohreally_factor · · Score: 3, Interesting

    GPL 3 is going to be "radioactive" to a lot of companies. Hell, even the main Linux Kernel guys consider it malignant. Developers that want to see their code adopted and used by the mainstream, whether they are in it for profit or not, might want to avoid GPL 3, especially if their software has runs on specialized or proprietary hardware. GPL 3 creates what in essence is a walled garden. If you GPL 3 your code, you're putting it into that garden. It might be a very beautiful garden, but your code will never get out.*

    *Assuming others are contributing to it. If you're the sole copyright holder for your project, you can always do whatever the hell you want.

    --
    It's not offtopic, dumbass. It's orthogonal.
  5. Re:An other example of GPL3 suckyness by kebes · · Score: 5, Interesting

    With these loopholes both sides won.
    Strange, I don't remember feeling a satisfying sense of victory when Microsoft tried to undermine our software by claiming that it infringed their patents. I don't remember feeling that we had "won" when Novell signed a deal with Microsoft to protect themselves and leave the rest of the community out in the cold.

    The loopholes were just that: sneaky ways to evade the intentions of most of the most important contributors in the realm of FOSS. I have no problem with businesses making money using FOSS, and many of them do it in a way that is not only compatible with the intentions of the GPL, but actively promotes the cause of free software. However, those businesses who were exploiting loopholes in the GPL knew that they were not promoting our interests, and therefore should not be surprised when the community shifts to close those loopholes. Such a shift will only alienate businesses who were not helping "the cause" anyways.

    The GPLv3 is not perfect, and is not a perfect license. I don't think that every project should switch to GPLv3... for some the GPLv2 may be a better match. However GPLv3 was crafted to address a very real problem, and judging from Microsoft's reaction, it is doing a great job in that regard.
  6. Re:An other example of GPL3 suckyness by 71thumper · · Score: 4, Interesting

    More importantly, GPLv3 serves as a reminder that choosing Open Source with the idea that "you'll never get left behind" is not a true position -- that all any given Open Source project really represents is the right to have the source code AS IT EXISTS NOW. In the future more restrictive licensing could be released that could impact you.

    In short, GPLv3 really made "Open Source" more like "Closed Source" by clearly pointing out that what you may be allowed to do now you may not be allowed to do later (unless you fork and thus lose the community aspect that made it interesting in the first place).

    After all, who's to say GPLv4 won't say "you must release any changes back to the community whether you distribute or not" ?

    GPLv3 is the best possible thing that could have happened to Closed Source vendors because it just kicked the chair out from under most of the arguments in favor of Open Source.

  7. pleading in the alternative by oliphaunt · · Score: 4, Interesting

    I'm not a lawyer, yet.

    In a lawsuit, it is possible to argue multiple theories of liability, or multiple theories of innocence. As long as each theory is internally consistent, they don't all have to be consistent with each other. It's the legal version of throwing stuff at the wall to see what sticks... and when you're just getting started, you don't want to leave stuff out by mistake, becuase there might be a chance that if you don't bring it up at the beginning you won't be allowed to bring it up later.

    The classic example is: Your buddy says, "You bastard, you slept with my wife!" If this was a lawsuit, you might respond

    a. No I didn't!
    b. You said that I could!
    c. She wasn't your wife!
    d. I thought she was someone else!
    e. I was insane!

    This would be OK, becuase even though (d) seems to contradict (a), that doesn't automatically mean that (a) is invalid, even though BOTH statements can't be true at the same time. These are all alternative theories of how you might avoid blame/liability for the act, and in filing or responding to lawsuits, this practice is known as alternative pleading.

    In that context, Microsoft's GPLv3 statement doesn't need to be consistent- although it is unusual to see this kind of logical construct outside of a court document. The press release reads like they're anticipating a lawsuit, and they're trying to get their story straight ahead of time... In this situation, their story is plausible deniability. and it doesn't matter which alternative theory ends up working, as long as one of them does the job.

    So it's perfectly legit for MS to use alternate theories to justify their actions- it just reeks of bad faith when their public position is so openly contradictory. It does seem pretty odd that Microsoft is using legal tactics to write their press releases- almost like they've got something to hide.

    --




    Humpty Dumpty was pushed.
  8. Re:15 years ago: by Em+Ellel · · Score: 4, Interesting

    The GPL is going to be "radioactive" to a lot of companies. Hell, even the main BSD guys consider it malignant. Developers that want to see their code adopted and used by the mainstream, whether they are in it for profit or not, might want to avoid GPL, especially if their software has runs on specialized or proprietary hardware. GPL creates what in essence is a walled garden. If you GPL your code, you're putting it into that garden. It might be a very beautiful garden, but your code will never get out.*

    *Assuming others are contributing to it. If you're the sole copyright holder for your project, you can always do whatever the hell you want. Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. 15 years later BSD made it into mainstream products from large manufacturers (F5, OS/X and iPhone, etc) And the companies that try Linux (Tivo, Cisco) are treated as the enemy by GPLv3. Has GPL been like GPLv3 from the get go, would Tivo or Linksys ever consider using Linux or would those be BSD products?

    -Em

    --
    RelevantElephants: A Somatic WebComic...
  9. Re:So what? by Crayon+Kid · · Score: 5, Interesting

    Old versions of samba exist. It'll just fork.


    It's not as simple as saying, "fine, we'll just ditch anything GPLv3". Who's gonna maintain the fork? 'Cause you gotta maintain it, you can't just fork it and let it rot. Will Microsoft pick up the fork? Will any of the Linux distro's that made a deal with Microsoft? Will they fork and maintain all projects that go GPLv3?

    See, it's not just a matter of forking the code. The license still sticks. OK, it's not GPLv3, it's good old GPLv2, but I think they'll have a lot of trouble dealing with just GPLv2 too. Remember, v3 made patent protection explicit and took it globally. But the stuff was still there, albeit implicit and USA-centric.

    All in all, I absolutely love seeing Microsoft publicly stating it won't touch GPLv3 with a ten foot pole. This is it, folks, this is THE shit. FSF got the holy Grail. It tells the corporate assholes "take it or leave it", and they gotta choose. And neither option comes easy.

    I think it's a knee-jerk reaction of Microsoft's to simply dismiss everything GPLv3, but they're probably frantic to get out of the Novell deal with clean face. It turned worse that they could've ever dreamed.
    --
    i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer