• On MovieTome: The next Spider-Man villain?
October 16, 2007 4:05 AM PDT

OSI gives two Microsoft licenses its blessing

by Matt Asay

The Open Source Initiative (OSI) has formally approved two of Microsoft's licenses:

I never doubted that these would be approved, but am glad to see the studied manner in which the process was (mostly) carried out. To me, this shows Microsoft the correct way to engage in open source: through the front door, rather than through back-door patent FUD.

Michael Tiemann of OSI writes on the process:

The decision to approve was informed by the overwhelming (though not unanimous) consensus from the open-source community that these licenses satisfied the 10 criteria of the Open Source definition and should therefore be approved.

The formal evaluation of these licenses began in August and the discussion of these licenses was vigorous and thorough. The community raised questions that Microsoft (and others) answered; they raised issues that, when germane to the licenses in question, Microsoft addressed. Microsoft came to the OSI and submitted their licenses according to the published policies and procedures that dozens of other parties have followed over the years. Microsoft didn't ask for special treatment, and didn't receive any. In spite of recent negative interactions between Microsoft and the open source community, the spirit of the dialog was constructive and we hope that carries forward to a constructive outcome as well.

In short, Microsoft played by open source's rules on this one and so was treated as a full open-source participant. In other contexts, with different behavior, Microsoft will be treated much differently.

Let's be clear, however: this OSI certification is not a blanket certification of Microsoft or its licenses. Microsoft had two licenses approved. Its software is only open source to the extent that it licenses said software under these two licenses. The rest can be proprietary, shared source, or whatever euphemism for "closed and proprietary" that Microsoft cares to use. Only Microsoft software licensed under its Microsoft Public License or its Microsoft Reciprocal License deserves to be called "open source."


Disclosure: I am on the board of the OSI.

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay.
Recent posts from The Open Road
Cloud to suck money out of market, report says
When open source isn't (open enough)
SAP wants an open Java process (pot, meet kettle)
Google shifts software value to operations, away from IP
Mobile: Still waiting to see what sticks
Google privacy controls: Most people won't care
Amazon's move mocks EU's fear of Oracle
Skype to open-source far too little
advertisement

As alternative energy grows, NIMBY greens

With more renewable energy projects trying to come online, the country grapples with the balance between local land use and a national push for clean energy.

Google to remake programming with Go

A Unix co-creator is among those behind a language Google hopes will speed computers and programming. Today, Go becomes open-source software.

advertisement

About The Open Road

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Open Road topics

advertisement
advertisement

Inside CNET News

Scroll Left Scroll Right