[Mono-list] relicensing from NPL to MIT/X11

César Octavio López Natarén cesar.nataren at gmail.com
Fri Jun 9 02:11:32 EDT 2006


Hello Bryan.

>> To sum up - did mono ask all authors of the "TokenStream.java" class
>> to change the license from NPL 1.1 to MIT/X11 license or is it valid
>> to "just" change from NPL to MIT/X11?
> 
> You need to obtain permission to get it under different terms, you can
> not remove the terms of the original license.
> 
>> 1)
>> http://svn.myrealbox.com/source/trunk/mcs/class/Microsoft.JScript/Microsoft.JScript/TokenStream.cs
>> 2)
>> http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/js/rhino/src/org/mozilla/javascript/TokenStream.java&rev=&root=/cvsroot
>>  
>> Thanks for any response which helps bringing some light into this
>> issue :-)
> 
> I had the impression that we had listed the explicit license for code
> that we have ported, but it seems that Cesar did not track this.

What we did was not changing the license but offering at MPL and MITX11, 
that's stated in file mcs/LICENSE:

"The Microsoft.JScript assembly is covered by the
MIT X11 and the Mozilla MPL license as it contains
ported pieces of code from Rhino, the Mozilla JavaScript
implementations"

And we also include mcs/LICENSE.MPL.

So the original authors are kept, and the .cs files are listed as 'port 
of the Rhino file'.

> I have CCed him on this email, maybe he can clarify, and if did port the
> code he should include the original license that he got it under, and
> document those license changes in the toplevel assembly directory.

Hello Miguel. I just added the original NPL license header to the files 
that are ported code from Rhino, to avoid more confusion.

Regards
césar


More information about the Mono-list mailing list