CVSROOT: /web/www
Module name: www
Changes by: Brett Smith <brett> 12/01/03 16:01:19
Modified files:
licenses : license-list.html
Log message:
Publish MPL 2.0 description. RT#706686.
The link might be dead when I commit this, but I've been promised
it'll be up very soon.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-list.html?cvsroot=www&r1=1.302&r2=1.303
Patches:
Index: license-list.html
===================================================================
RCS file: /web/www/www/licenses/license-list.html,v
retrieving revision 1.302
retrieving revision 1.303
diff -u -b -r1.302 -r1.303
--- license-list.html 23 Dec 2011 23:04:05 -0000 1.302
+++ license-list.html 3 Jan 2012 16:00:44 -0000 1.303
@@ -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 “Larger Work” 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
+“Incompatible With Secondary Licenses.” 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>
@@ -2148,7 +2196,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2011/12/23 23:04:05 $
+$Date: 2012/01/03 16:00:44 $
<!-- timestamp end -->
</p>
</div>
