Advanced

Microsoft to issue "Community Promise" for C# and CLI

Posted by Yuioup on · 5 comments
Miguel de Icaza's web log; By Miguel de Icaza
Mail this story
Print this story

First the big news: Microsoft will be applying the Community Promise patent licensing to both C# and the CLI. The announcement was done by Peter Galli at Microsoft over at Port25. A few months ago we approached Bob Muglia and Brian Goldfarb (@bgoldy) at Microsoft with a request to clarify the licensing situation for the ECMA standards covering C# and the CLI (also ISO standards, for the ISO loving among you). Previously Microsoft had detailed the patent license plans and today they have delivered on those plans. Astute readers will point out that Mono contains much more than the ECMA standards, and they will be correct. In the next few months we will be working towards splitting the jumbo Mono source code that includes ECMA + A lot more into two separate source code distributions. One will be ECMA, the other will contain our implementation of ASP.NET, ADO.NET, Winforms and others.

Full Story

  Nav
» Read more about: Groups: Microsoft

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (5)

This part still raises my hairs:

Quoting:Q: What if I don’t implement the entire specification? Will I still get the protections under the CP?

A: The CP applies only if the implementation conforms fully to required portions of the specification. Partial implementations are not covered.


I'm no lawyer so I refrain from commenting until a lawyer reviews that, but I wonder how that would work with GPLv3 section 11.
I don't see how it can conform to GPLV3, as the failure to cover partial implementations imposes a significant restriction on the rights of recipients to modify the code.
Yes, but GPLv3 section 11 also mentions several things that apply only to the patent holder or controller. A 3rd party use creating GPLv3 code does not control the patent in this case.

I assume that someone with FSF is looking at it as we're speaking and that comments and analysis will shortly follow. I'll wait for readable version of all that legalese before I make up my mind.
Why are we looking for GPL compatibility on a license that isnt even on the OSI's license list?

p.s. GPL compatibility does not an open source license make, or rather lack of said compatibility does not mean that a license isnt an open source license. In this case however, it's a completely moot point.

http://www.opensource.org/licenses/alphabetical
Quoting:Why are we looking for GPL compatibility on a license that isnt even on the OSI's license list?


Because the MS-CP isn't a source code license so it will never show up on the OSI list. IMB's patent promise isn't on OSI either. Neither is the OIN promise.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post