The Microsoft Linux GPLv2 contribution saga unfolds
Microsoft responds to Linux contributor's claims about potential GPL violations in the Linux Integration Components
Follow @SavioRodriguesMicrosoft has responded to claims that its Linux Integration Components (LIC) were only contributed under the GPLv2 after being out of compliance with the GPL in the first place.
It's important to note that LIC was pre-existing code available from Microsoft. The version I downloaded only supported Novel Suse, but it seems Red Hat Enterprise Linux was supported also. Until a few days ago, this code was not completely under the GPLv2. How much was, and whether GPLv2 and non-GPLv2 code was combined in a manner that violates the GPLv2, is at the root of this story.
[ To read more about Microsoft's open source contributions this week, see "Microsoft releases code for Linux drivers" and "Microsoft makes second GPLv2 release is as many days." | An engineer claims that Microsoft had been in violation of GPLv2 before releasing the Linux driver code. ]
A well-known Linux contributor, Stephen Hemminger found the LIC prior to its contribution under the GPLv2. He writes:
But on closer examination there was a problem. The driver had both open-source components which were under GPL, and statically linked to several binary parts. The GPL does not permit mixing of closed and open source parts, so this was an obvious violation of the license. Rather than creating noise, my goal was to resolve the problem, so I turned to Greg Kroah-Hartman.
Steve's post resulted in Greg Kroah-Hartman (aka Greg K-H), the Linux kernel maintainer who accepted the Microsoft code, updating his post about the Microsoft GPLv2 contribution:
Steve gives a little more of the backstory of what caused me to start talking to Microsoft in the first place.
Microsoft's Sam Ramji posted today:
