www/licenses license-list.html

[Craig Topham]

CVSROOT:        /web/www
Module name:    www
Changes by:     Craig Topham <craigt>   23/04/06 15:54:47

Modified files:
        licenses       : license-list.html 

Log message:
        Summary: Updated text regarding Creative Commons Zero CC)

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-list.html?cvsroot=www&r1=1.541&r2=1.542

Patches:
Index: license-list.html
===================================================================
RCS file: /web/www/www/licenses/license-list.html,v
retrieving revision 1.541
retrieving revision 1.542
diff -u -b -r1.541 -r1.542
--- license-list.html   4 Mar 2023 16:55:19 -0000       1.541
+++ license-list.html   6 Apr 2023 19:54:42 -0000       1.542
@@ -768,13 +768,11 @@
 domain material is compatible with the GNU GPL.</p>
 
 <p>If you want to release your work to the public domain, we encourage
-you to use formal tools to do so.  We ask people who make small
-contributions to GNU to sign a disclaimer form; that's one solution.
-If you're working on a project that doesn't have formal contribution
-policies like that, <a href="#CC0">CC0</a> is a good tool that anyone
-can use.  It formally dedicates your work to the public domain, and
-provides a fallback license for cases where that is not legally
-possible.</p></dd>
+you to use formal tools to do so.  Our solution is to ask people who
+make small contributions to GNU to sign a disclaimer form.  If you're
+working on a project that doesn't have formal contribution policies,
+contact the project to discuss how best to contribute within the
+project's licensing model.</p></dd>
 
 <dt><a id="Python" 
href="https://directory.fsf.org/wiki?title=License:Python2.0.1";>
     License of Python 2.0.1, 2.1.1, and newer versions</a>
@@ -892,11 +890,6 @@
 Both public domain works and the lax license provided by the
 Unlicense are compatible with the GNU GPL.</p>
 
-<p>If you want to release your work to the public domain, we recommend
-you use <a href="#CC0">CC0</a>.  CC0 also provides a public domain
-dedication with a fallback license, and is more thorough and
-mature than the Unlicense.</p></dd>
-
 <dt><a id="Vim" href="https://directory.fsf.org/wiki/License:Vim7.2";>
     License of Vim, Version 6.1 or later</a>
     <span class="anchor-reference-id">(<a href="#Vim">#Vim</a>)</span></dt>
@@ -1802,13 +1795,10 @@
 licenses are for.</p>
 
 <p>Some countries allow authors to put code in the public domain, but
-that requires explicit action.  If you wish to do that, the method we
-recommend is to use <a href="#CC0">CC0</a>, which also works in other
-countries by putting on a license that is more or less equivalent to
-public domain.  However, in most cases it
-is <a href="/licenses/license-recommendations.html"> better to
-copyleft your code</a> to assure that freedom reaches all users of the
-code.</p>
+that requires explicit action which can vary among jurisdictions. In
+most cases it is <a href="/licenses/license-recommendations.html">
+better to copyleft your code</a> to assure that freedom reaches all
+users of the code.</p>
 
 <p>Code written by employees of the US government is a special
 exception, since US copyright law explicitly puts that in the public
@@ -2809,8 +2799,8 @@
 use.</p>
 
 <p>3D-printer plans for objects meant for practical use should also be
-free.  We recommend the GNU GPL or one of the Creative Commons
-licenses that are free: CC-BY, CC-BY-SA, or CC0.</p>
+free. We recommend the GNU GPL or one of the Creative Commons licenses
+that are free such as CC-BY or CC-BY-SA.</p>
 
 <p>3D-printer plans for decorative objects are artistic works; any of the
 Creative Commons licenses is ok for them.</p>
@@ -2855,7 +2845,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2023/03/04 16:55:19 $
+$Date: 2023/04/06 19:54:42 $
 <!-- timestamp end -->
 </p>
 </div>