Slashdot Mirror


SFLC Says Microsoft Violated the GPL

After Microsoft donated driver code to the Linux kernel under the GPLv2, stories surfaced that they had done so under duress of already being in violation of the GPL. Microsoft quickly denied that any GPL violation was a driver for their decision to donate the code; the company's senior director of platform strategy, Sam Ramji, said at the time: "Microsoft's decision was not based on any perceived obligations tied to the GPLv2 license." Now the Software Freedom Law Center confirms that Microsoft was indeed in violation of the GPLv2 when it distributed its Hyper-V Linux Integration Components without providing source code. Community members led by Greg Kroah-Hartman contacted the company and coached them through the process of getting compliant. Microsoft now says that they had already been on the path for several months toward releasing the software under GPLv2 before Kroah-Hartman got in touch.

2 of 237 comments (clear)

  1. I've Still Yet to See the Code from Them by eldavojohn · · Score: 5, Interesting
    So I downloaded the Hyper-V Linux Integration Components from Microsoft and unpacked the exe. I was prompted with this agreement:

    MICROSOFT SOFTWARE LICENSE TERMS

    MICROSOFT WINDOWS SERVER 2008

    HYPER-V LINUX INTEGRATION COMPONENTS

    PLEASE NOTE: Microsoft Corporation (or based on where you live, one of its affiliates) licenses this supplement to you. You may use it with each validly licensed copy of Microsoft operating system products software (for which this supplement is applicable) (the âoesoftwareâ). You may not use the supplement if you do not have a license for the software. The license terms for the software apply to your use of this supplement. Microsoft provides support services for the supplement as described at www.support.microsoft.com/common/international.aspx.

    After it unpacks, I get an RTF named "Linux ICs for Hyper-V" and LinuxIC.iso ... no source code. Anybody know where said source code is? Because when I do a search on their site, I'm not finding it.

    Sure, it may have contributed the source code to some repository somewhere but I think the GPLv2 says you need to provide it if you are distributing. Which is what they're doing. Pretty obvious violation right there. Also, when you distribute it, you should have a copy of the GPLv2 license with it. I can't find a trace of it when I get the iso from them ...

    --
    My work here is dung.
  2. Surprising, actually. by fuzzyfuzzyfungus · · Score: 4, Interesting

    I'm actually pretty surprised by this news. It is well known that MS hates the GPL; but they are a big company, with a nontrivial legal team, and they know that the GPL has, thus far, held up in court.

    Surely legal would have thrown a screaming fit if they tried to release anything that constituted a clear licence violation. In practice, copyright holders of GPL licenced stuff have been mild and cooperative about this sort of thing, generally aiming at compliance and occasionally fairly small damages; but they are under no legal obligation to do so, and MS has very deep pockets, which would bring the lawyers swarming if they were in clear violation.

    Are they trying to provoke a test case, or did they just fuck up?