Freigeben über

Releasing the Linux Integration Component Drivers...

  • Artikel

by Sam Ramji on July 23, 2009 08:38pm

Microsoft on Monday contributed the Linux Integration Component drivers to the Linux community for the reasons stated in our release. Microsoft chose the GPLv2 license for the mutual benefit of our customers, partners, the community, and Microsoft.

Microsoft's decision was not based on any perceived obligations tied to the GPLv2 license. For business reasons and for customers, we determined it was beneficial to release the drivers to the kernel community under the GPLv2 license through a process that involved working closely with Greg Kroah-Hartman, who helped us understand the community norms and licensing options surrounding the drivers. 

The primary reason we made this determination in this case is because GPLv2 is the preferred license required by the Linux community for their broad acceptance and engagement. For us to participate in the Linux Driver Project, GPLv2 was the best option that allowed us to enjoy the tremendous offer of community support. The community's response even within a few hours of posting the code was welcoming and we appreciate it greatly.

We arrived at the decision to release the drivers to the community under the GPLv2 through this process. Both Greg K-H and Jim Zemlin of the Linux Foundation have reiterated that this is the same process that other companies follow when deciding how to release new device drivers to the Linux community.

We are looking forward to the positive collaboration and acceptance that has marked the vast majority of our interactions with customers and community members regarding this important project.

Cheers,

Sam

Updated 7/25/2009 @ 11:54 AM Pacific: Dave Roberts of Vyatta posted a blog entry rebutting recent cloims that we were accused of a licensing violation with some detail on the technical issues.

Comments

  • Anonymous
    June 08, 2011
    Updated 7/25/2009 @ 11:54 AM Pacific: Dave Roberts of Vyatta posted a blog entry rebutting recent cloims that we were accused of a licensing violation with some detail on the technical issues.