www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bay...@apache.org
Subject svn commit: r668031 - in /infrastructure/site/trunk: docs/legal/resolved.html xdocs/legal/resolved.xml
Date Mon, 16 Jun 2008 01:09:11 GMT
Author: bayard
Date: Sun Jun 15 18:09:11 2008
New Revision: 668031

URL: http://svn.apache.org/viewvc?rev=668031&view=rev
Log:
Adding Sam's Category B text, allowing binary only dependencies on CDDL, CPL, EPL, MPL, IPL
and SPL

Modified:
    infrastructure/site/trunk/docs/legal/resolved.html
    infrastructure/site/trunk/xdocs/legal/resolved.xml

Modified: infrastructure/site/trunk/docs/legal/resolved.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/legal/resolved.html?rev=668031&r1=668030&r2=668031&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/legal/resolved.html (original)
+++ infrastructure/site/trunk/docs/legal/resolved.html Sun Jun 15 18:09:11 2008
@@ -165,6 +165,38 @@
      <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-Share
Alike</a> 
      license may be included in Apache products, subject to the licenses attribution clauses
which may require 
      LICENSE/NOTICE/README changes. For any other type of CC-SA licensed work, please contact
the Legal PMC. </p>
+<p><b>* How should so-called "Weak Copyleft" Licenses be handled?</b></p>
+<p>Each license in this category requires some degree of reciprocity;
+     this may means that additional action is warranted in order to
+     minimize the chance that a user of an Apache product will create a
+     derivative work of a reciprocally-licensed portion of an Apache
+     product without being aware of the applicable requirements. </p>
+<p>Software under the following licenses may be included in binary form
+     within an Apache product if the inclusion is appropriately labeled: </p>
+<ul>
+      <li><a href="http://www.sun.com/cddl/">CDDL 1.0</a></li>
+      <li><a href="http://www.opensource.org/licenses/cpl1.0.php">CPL 1.0</a></li>
+      <li><a href="http://www.eclipse.org/legal/epl-v10.html">EPL 1.0</a></li>
+      <li><a href="http://www.opensource.org/licenses/ibmpl.php">IPL 1.0</a></li>
+      <li><a href="http://www.mozilla.org/MPL/MPL-1.0.html">MPL 1.0</a>
and 
+          <a href="http://www.mozilla.org/MPL/MPL-1.1.html">MPL 1.1</a></li>
+      <li><a href="http://java.sun.com/spl.html">SPL 1.0</a></li>
+  </ul>
+<p>By including only the object/binary form, there is less exposed
+     surface area of the third-party work from which a work might be
+     derived; this addresses the second guiding principle of this policy.
+     By attaching a prominent label to the distribution and requiring an
+     explicit action by the user to get the reciprocally-licensed source,
+     users are less likely to be unaware of restrictions significantly
+     different from those of the Apache License. Please include the 
+     URL to the product's homepage in the prominent label. </p>
+<p>For small amounts of source that is directly consumed by the ASF
+     product at runtime in source form, and for which that source is
+     unmodified and unlikely to be changed anyway (say, by virtue of being specified by a
+     standard), inclusion of appropriately labeled source is also
+     permitted. An example of this is the web-facesconfig_1_0.dtd, whose
+     inclusion is mandated by the JSR 127: JavaServer Faces specification. </p>
+<p>This is colloquially known as the <i>Category B</i> list. </p>
 </div>
 </div>
          </div>

Modified: infrastructure/site/trunk/xdocs/legal/resolved.xml
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/xdocs/legal/resolved.xml?rev=668031&r1=668030&r2=668031&view=diff
==============================================================================
--- infrastructure/site/trunk/xdocs/legal/resolved.xml (original)
+++ infrastructure/site/trunk/xdocs/legal/resolved.xml Sun Jun 15 18:09:11 2008
@@ -123,6 +123,46 @@
      license may be included in Apache products, subject to the licenses attribution clauses
which may require 
      LICENSE/NOTICE/README changes. For any other type of CC-SA licensed work, please contact
the Legal PMC. </p>
 
+
+  <p><b>* How should so-called "Weak Copyleft" Licenses be handled?</b></p>
+
+  <p>Each license in this category requires some degree of reciprocity;
+     this may means that additional action is warranted in order to
+     minimize the chance that a user of an Apache product will create a
+     derivative work of a reciprocally-licensed portion of an Apache
+     product without being aware of the applicable requirements. </p>
+ 
+  <p>Software under the following licenses may be included in binary form
+     within an Apache product if the inclusion is appropriately labeled: </p>
+ 
+  <ul>
+      <li><a href="http://www.sun.com/cddl/">CDDL 1.0</a></li>
+      <li><a href="http://www.opensource.org/licenses/cpl1.0.php">CPL 1.0</a></li>
+      <li><a href="http://www.eclipse.org/legal/epl-v10.html">EPL 1.0</a></li>
+      <li><a href="http://www.opensource.org/licenses/ibmpl.php">IPL 1.0</a></li>
+      <li><a href="http://www.mozilla.org/MPL/MPL-1.0.html">MPL 1.0</a>
and 
+          <a href="http://www.mozilla.org/MPL/MPL-1.1.html">MPL 1.1</a></li>
+      <li><a href="http://java.sun.com/spl.html">SPL 1.0</a></li>
+  </ul>
+ 
+  <p>By including only the object/binary form, there is less exposed
+     surface area of the third-party work from which a work might be
+     derived; this addresses the second guiding principle of this policy.
+     By attaching a prominent label to the distribution and requiring an
+     explicit action by the user to get the reciprocally-licensed source,
+     users are less likely to be unaware of restrictions significantly
+     different from those of the Apache License. Please include the 
+     URL to the product's homepage in the prominent label. </p>
+ 
+  <p>For small amounts of source that is directly consumed by the ASF
+     product at runtime in source form, and for which that source is
+     unmodified and unlikely to be changed anyway (say, by virtue of being specified by a
+     standard), inclusion of appropriately labeled source is also
+     permitted. An example of this is the web-facesconfig_1_0.dtd, whose
+     inclusion is mandated by the JSR 127: JavaServer Faces specification. </p>
+
+  <p>This is colloquially known as the <i>Category B</i> list. </p>
+
 </section>
 
 </section>



---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message