trans-coord-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

trans-coord/gnun/licenses license-list.html


From: Yavor Doganov
Subject: trans-coord/gnun/licenses license-list.html
Date: Tue, 03 Jan 2012 19:10:17 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   12/01/03 19:10:17

Modified files:
        gnun/licenses  : license-list.html 

Log message:
        Automatic sync from the master www repository.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/licenses/license-list.html?cvsroot=trans-coord&r1=1.71&r2=1.72

Patches:
Index: license-list.html
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/licenses/license-list.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -b -r1.71 -r1.72
--- license-list.html   24 Dec 2011 19:10:14 -0000      1.71
+++ license-list.html   3 Jan 2012 19:10:17 -0000       1.72
@@ -515,6 +515,54 @@
 License</a> are similarly permissive and brief.</p></dd>
 
 
+<dt><a id="MPL-2.0"
+       href="http://www.mozilla.org/MPL/2.0/";>Mozilla Public
+       License (MPL) version 2.0</a>
+    <span class="anchor-reference-id">(<a 
href="#MPL-2.0">#MPL-2.0</a>)</span></dt>
+<dd>
+<p>This is a free software license.  Section 3.3 provides indirect
+compatibility between this license and the GNU GPL version 2.0, the
+GNU LGPL version 2.1, the GNU AGPL version 3.0, and all later versions
+of those licenses.  When you receive work under the MPL version 2.0,
+you may make a &ldquo;Larger Work&rdquo; that combines that work with
+work under one of those GNU licenses.  When you do, section 3.3 gives
+you permission to distribute the MPL-covered work under the terms of
+that same GNU license, with one condition: you must make sure that the
+files that were originally under the MPL are still available under the
+MPL's terms as well.  In other words, when you make a combination this
+way, the files that were originally under the MPL will be dual
+licensed under the MPL and the GNU license.  The end result is that
+the Larger Work, as a whole, will be covered under the GNU license.
+People who receive that combination from you will have the option to
+use any files that were originally covered by the MPL under that
+license's terms, or distribute the Larger Work in whole or in part
+under the terms of the GNU license with no further restrictions.</p>
+
+<p>It's important to understand that the condition to distribute files
+under the MPL's terms only applies to the party that first creates and
+distributes the Larger Work.  If it applied to their recipients as well, it
+would be a further restriction and incompatible with the GNU licenses.
+That said, when you make contributions to an existing project, we usually
+<a href="/licenses/license-recommendations.html#contributing">recommend that 
you keep your changes under the same license</a>,
+even when you're not required to do so.  If you receive a work under a GNU
+license where some files are also under the MPL, you should only remove the
+MPL from those files when there's a strong reason to justify it.</p>
+
+<p>Check the license notices on the MPL-covered software before you make
+a Larger Work this way.  Parties who release original work under the
+MPL version 2.0 may choose to opt out of this compatibility by
+including a sentence in the license notices that says that the work is
+&ldquo;Incompatible With Secondary Licenses.&rdquo; Any software that
+includes this notice is <strong>not</strong> compatible with the GPL
+or AGPL.</p>
+
+<p>Software under previous versions of the MPL can be upgraded to version
+2.0, but any software that isn't already available under one of the
+listed GNU licenses <strong>must</strong> be marked as Incompatible With 
Secondary
+Licenses.  This means that software that's only available under
+previous versions of the MPL is still incompatible with the GPL and AGPL.</p>
+</dd>
+
 <dt><a id="NCSA" href="http://www.opensource.org/licenses/UoI-NCSA.php";>
     NCSA/University of Illinois Open Source License</a>
     <span class="anchor-reference-id">(<a href="#NCSA">#NCSA</a>)</span></dt>
@@ -534,15 +582,7 @@
 <p>This is the disjunction of the <a href="#NPL">Netscape Public
 License</a> and the <a href="/licenses/gpl.html">GNU GPL</a>.  Because
 of that, it is a free software license, compatible with the GNU GPL, but
-not a strong copyleft.</p> <p>This disjunctive license is a good choice
-if you want to make your package GPL-compatible and MPL-compatible.
-However, you can also accomplish that by using the LGPL or the Guile
-license.</p>
-
-<p>Such a disjunctive license might be a good choice if you have been
-using the MPL, and want to change to a GPL-compatible license without
-subtracting any permission you have given for previous
-versions.</p></dd>
+not a strong copyleft.</p></dd>
 
 
 <dt><a id="newOpenLDAP"
@@ -922,7 +962,7 @@
     <span class="anchor-reference-id"> (<a href="#CPAL">#CPAL</a>)</span></dt>
 <dd>
 <p>This is a free software license.  It is based on the <a
-href="#MPL">Mozilla Public License</a>, and is incompatible with the GPL
+href="#MPL">Mozilla Public License</a> version 1, and is incompatible with the 
GPL
 for the same reasons: it has several requirements for modified versions
 that do not exist in the GPL.  It also requires you to publish the
 source of the program if you allow others to use it.</p></dd>
@@ -1109,7 +1149,7 @@
 
 
 <dt><a id="MPL" href="http://www.mozilla.org/MPL/MPL-1.1.html";>
-     Mozilla Public License (MPL)</a>
+     Mozilla Public License (MPL) version 1.1</a>
     <span class="anchor-reference-id">(<a href="#MPL">#MPL</a>)</span></dt>
 <dd>
 <p>This is a free software license which is not a strong copyleft;
@@ -1131,7 +1171,7 @@
     <span class="anchor-reference-id">(<a href="#NOSL">#NOSL</a>)</span></dt>
 <dd>
 <p>This is a free software license that is essentially the same as the
-Mozilla Public License, Version 1.1.  Like the MPL, the NOSL has some
+Mozilla Public License version 1.1.  Like the MPL, the NOSL has some
 complex restrictions that make it incompatible with the GNU GPL.  That
 is, a module covered by the GPL and a module covered by the NOSL cannot
 legally be linked together.  We urge you not to use the NOSL for this
@@ -1144,17 +1184,18 @@
 <dd>
 <p>This is a free software license, not a strong copyleft, and
 incompatible with the GNU GPL.  It consists of the Mozilla Public
-License with an added clause that permits Netscape to use your added
-code <em>even in their proprietary versions of the program</em>.  Of
-course, they do not give <em>you</em> permission to use <em>their</em>
-code in the analogous way.  We urge you not to use the NPL.</p></dd>
+License version 1.1 with an added clause that permits Netscape to use
+your added code <em>even in their proprietary versions of the
+program</em>.  Of course, they do not give <em>you</em> permission to
+use <em>their</em> code in the analogous way.  We urge you not to use
+the NPL.</p></dd>
 
 
 <dt><a id="Nokia" href="http://opensource.org/licenses/nokia.html";>
     Nokia Open Source License</a>
     <span class="anchor-reference-id">(<a href="#Nokia">#Nokia</a>)</span></dt>
 <dd>
-<p>This is similar to the Mozilla Public License: a free
+<p>This is similar to the Mozilla Public License version 1: a free
 software license incompatible with the GNU GPL.</p></dd>
 
 
@@ -1307,7 +1348,7 @@
     Sun Public License</a>
     <span class="anchor-reference-id">(<a href="#SPL">#SPL</a>)</span></dt>
 <dd>
-<p>This is essentially the same as the Mozilla Public License: a free
+<p>This is essentially the same as the Mozilla Public License version 1: a free
 software license incompatible with the GNU GPL.  Please do not confuse
 this with the <a href="#SunCommunitySourceLicense">Sun Community Source
 License</a>, which is not a free software license.</p></dd>
@@ -2148,7 +2189,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2011/12/24 19:10:14 $
+$Date: 2012/01/03 19:10:17 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]