www/licenses license-list.html

[Bryan Robert]

CVSROOT:        /web/www
Module name:    www
Changes by:     Bryan Robert <bpr>      19/01/07 23:24:46

Modified files:
        licenses       : license-list.html 

Log message:
        Updated ISC license entry (RT #1348091)

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

Patches:
Index: license-list.html
===================================================================
RCS file: /web/www/www/licenses/license-list.html,v
retrieving revision 1.499
retrieving revision 1.500
diff -u -b -r1.499 -r1.500
--- license-list.html   29 Dec 2018 12:49:06 -0000      1.499
+++ license-list.html   8 Jan 2019 04:24:45 -0000       1.500
@@ -650,31 +650,11 @@
     ISC License</a>
     <span class="anchor-reference-id">(<a href="#ISC">#ISC</a>)</span></dt>
 <dd>
-<p>This is a lax, permissive free software license, and compatible
-with the GNU GPL.</p> 
+<p>This license is sometimes also known as the OpenBSD License. It is a free 
software license, and compatible with the GNU GPL.</p>
 
-<p>This license is sometimes also known as the OpenBSD License,
-although there is one minor difference between the two licenses. The
-OpenBSD license was updated to remove the ambiguous term:
-&quot;and/or&quot;. The ISC license provides recipients with
-&quot;Permission to use, copy, modify, and/or distribute this
-software&hellip;&quot;, whereas the OpenBSD license provides
-recipients with &quot;Permission to use, copy, modify, and
-distribute&hellip;&quot;. </p>
-
-<p>At the time the ISC license was released, the use of
-&quot;and/or&quot; construct was a concern because it is similar
-language used in the license of Pine that the University of Washington
-later claimed prohibited people from distributing modified versions of
-the software. However, ISC has told us they do not share the
-University of Washington's interpretation, and we have every reason to
-believe them.  Thus, there's no reason to avoid software released
-under this license.  However, to help make sure this language cannot
-cause any trouble in the future, we encourage developers to choose a
-different license for their own works.  The <a href="#Expat">Expat
-License</a> and <a href="#FreeBSD">FreeBSD License</a> are similarly
-permissive and brief.</p></dd>
+<p>This license had an unfortunate wording choice: it provided recipients with 
&quot;Permission to use, copy, modify, and distribute this 
software&hellip;&quot;. This was the same language from the license of Pine 
that the University of Washington later claimed prohibited people from 
distributing modified versions of the software.</p>
 
+<p>ISC has told us they do not share the University of Washington's 
interpretation, and we have every reason to believe them. ISC also updated the 
license to read &quot;Permission to use, copy, modify, *and/or* distribute this 
software&hellip;&quot;. While the inclusion of &quot;and/or&quot; doesn't 
completely solve the issue, there's no reason to avoid software released under 
this license. However, to help make sure this language cannot cause any trouble 
in the future, we encourage developers to choose a different license for their 
own works. The <a href="#FreeBSD">FreeBSD License</a> is similarly permissive 
and brief. However, if you want a lax, weak license, we recommend using the 
Apache-2.0 license.</p></dd>
 
 <dt><a id="MPL-2.0"
        href="http://directory.fsf.org/wiki/License:MPLv2.0";>Mozilla Public
@@ -2787,7 +2767,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2018/12/29 12:49:06 $
+$Date: 2019/01/08 04:24:45 $
 <!-- timestamp end -->
 </p>
 </div>