451 CAOS Theory *
A blog for the enterprise open source community

What Microsoft can and cannot do

Jay Lyman, August 29, 2007 @ 11:01 pm ET

Much of the hottest debate and discussion in the open source community lately has been about one the most proprietary of vendors, Microsoft. As Redmond alters its course and plots its co-existence and next wave of competition with open source, it is running into everything from pushback to open arms to, more recently, a challenge by the Free Software Foundation. The FSF repudiates Microsoft’s July 2007 statement declaring its unwillingness to include support for GPLv3-licensed code in its distribution of SUSE Linux, which is part of the Microsoft-Novell collaboration deal struck in November 2006. When released, Microsoft’s statement seemed somewhat odd and looked to some like recognition that there may be some issues for Microsoft in this new open source license.

While I disagree with the FSF that the term intellectual property is “a propaganda term designed to confuse patent law with copyright and other unrelated laws, and to muddy the different issues they raise,” I do agree that Microsoft must abide by the terms and conditions of the GPL, whether version 2 or 3, whichever is applicable, which may emerge as a key question. Microsoft found a loophole in GPLv2 that allowed the patent promise to Novell SUSE Linux users but not other Linux users. The selective patent promise, while contrary to the spirit of the GPL and nebulous for users, does comply with the letter of the open source license. However, GPLv3 is different, and Microsoft was exactly what the FSF had in mind when it described and defined distributor, propagator and conveyor of Linux in the new license.

Should Microsoft be discriminated against or otherwise treated differently as it attempts to foster its own open source efforts or seeks OSI approval on its proposed open source licenses? Absolutely not. I liken this to the discussion of open source software used in weapons and military applications. The bottom line is that while some may not like the result of what’s done with granted freedoms, those freedoms must in no way be limited or exclusionary to any groups or individuals. The whole basis, and here’s where I agree with the FSF again, of free and open source software is freedom. On the flip side, Microsoft can’t come out and declare that it won’t need to have anything to do with GPLv3 because it says so. What the license says is far more relevant. The company should not, dare I say cannot, seek any special status if it wants to be treated fairly, particularly in regards to software licenses, which are the basis for the bulk of Microsoft’s billions.

Permalink | Technorati Links | Bookmark on del.icio.us | digg it
Categories: Licensing, Software

Comments RSS feed | Trackback URI

3 Comments»

Collapse Comment by Savio Rodrigues, August 30, 2007 12:51 pm

Jay,

>Microsoft can’t come out and declare that it won’t need to have anything to do with GPLv3 because it says so.

Actually, Microsoft can do that. It’s now up to the FSF/SFLC/??? to take MS to court if these bodies believe Microsoft has violated terms of the GPLv3.

My bets are against this happening. First there is the issue of legal costs. Second the issue of setting legal precedent (but IANAL).

Savio

Collapse Comment by Jay Lyman, August 30, 2007 1:58 pm

Thanks for the comment, Savio. You’re right that MS can and HAS declared it won’t have anything to do with GPLv3, and I agree the issue, like Microsoft’s patent threats, will not get to court. My point is that this has repercussions for Microsoft. If it wants a fair shake on its open source software partnerships and initiatives, it cannot seek special treatment on GPLv3 or any other license. Well, it should not, but the title ‘What Microsoft can and should not do’ doesn’t sound as good ;).

 
 
Collapse Comment by tomb, August 30, 2007 8:49 pm

As a matter of fact, the issue of Microsoft and GPL3 will appear in court, but not through any action of the FSF. Should Microsoft decide to sue anyone over patent violations, as they have foolishly threatened, then the whole GPL3 argument becomes part of the defense and/or counterclaims. Call it the Mutually Assured Destruction option.
So, bottom line is that Microsoft stands a chance of being hurt by this only if they pull the trigger first, and that’s the only way it’ll happen.

 

Leave a Comment

Some HTML is allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> .

Your Comment (smaller size | larger size)