RECENT ARTICLES

Open Source Weblog

Do Microsoft's licenses stand a chance of OSI approval?
July 27, 2007

So Microsoft is to submit its shared source licenses for approval by the OSI.

Do any of them stand a chance? Here's my (admittedly simplified) two-penneth.

Microsoft has five shared source licenses, two of which would have the potential to be approved by the OSI.

The Microsoft Permissive License (Ms-PL) is the least restrictive and could be thought of as the most like the BSD license in that it allows users to view, modify, and redistribute the source code for either commercial or non-commercial purposes.

The Microsoft Community License (Ms-CL) is more like the GNU General Public License, in that it allows users to view, modify, and redistribute the code and ensures that any larger work distributed as a single file also needs to be licensed under the same license.

The Microsoft Reference License (Ms-RL) is a reference-only license that allows users to view the source code but not modify or redistribute it and therefore stands no chance of being approved.

The other two licenses, the Ms-LPL and Ms-LCL, are limited versions that only allow code to be run on the Windows operating system, and would therefore fail to meet the criteria of the Open Source Definition.

When the licenses were introduced in late 2005, the Free Software Foundation Europe noted that the Ms-PL and Ms-CL appeared to satisfy the four freedoms that define Free Software.

That would give the licenses a good chance of meeting the 10 requirements that make up the Open Source Definition, but there are no guarantees. Even if the license were found to have met all 10 criteria, the OSI has been actively trying to reduce license proliferation and it could be that Microsoft’s licenses are seen as too similar to existing licenses to warrant separate approval.


Digg!


  Email this entry to a friend

Posted by Matthew Aslett on July 27, 2007 03:26 PM

Comments

I believe the MS-PL and the MS-CL licenses do not provide the patent protection that GPL2 and GPL3 do, which is why Microsoft is now pushing them now. Basically Microsoft has realised it hasn't got a hope in hell in beating Open Source, and that it can only control and parasitize Open Source through licensing of patented lock-in standards like OOXML. Microsoft's hopes of doing this to GPL were dashed by the patent protection clauses in GPL2 and GPL3. Microsoft has therefore decided to create an open source license that it can actually parasitize in the hope of luring unwary developers into it's sphere of control.
.
These shannegans are Microsoft's admission of failure to tax, manipulate and control GPL software.

Posted by: SPM on July 31, 2007 02:22 PM

Post a comment

Name:

Email Address:

URL:

Remember Me?    Yes     No 

Comments: