www/licenses licenses.html rms-why-gplv3.html

[Rob Myers]

CVSROOT:        /web/www
Module name:    www
Changes by:     Rob Myers <robmyers>    09/09/11 21:56:35

Modified files:
        licenses       : licenses.html rms-why-gplv3.html 

Log message:
        Normalise title, remove meta tag.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/licenses.html?cvsroot=www&r1=1.80&r2=1.81
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/rms-why-gplv3.html?cvsroot=www&r1=1.12&r2=1.13

Patches:
Index: licenses.html
===================================================================
RCS file: /web/www/www/licenses/licenses.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -b -r1.80 -r1.81
--- licenses.html       11 Sep 2009 20:02:56 -0000      1.80
+++ licenses.html       11 Sep 2009 21:56:28 -0000      1.81
@@ -1,6 +1,5 @@
 <!--#include virtual="/server/header.html" -->
-<title>Licenses</title>
-<meta name="keywords" description="GNU GPL, GNU LGPL, GNU FDL, General Public 
License, Lesser General Public License, Free Documentation License, List of 
Free Software Licenses">
+<title>Licenses - GNU Project - Free Software Foundation</title>
 <!--#include virtual="/server/banner.html" -->
 
 <h2>Licenses</h2>
@@ -435,7 +434,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2009/09/11 20:02:56 $
+$Date: 2009/09/11 21:56:28 $
 <!-- timestamp end -->
 </p>
 </div>

Index: rms-why-gplv3.html
===================================================================
RCS file: /web/www/www/licenses/rms-why-gplv3.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- rms-why-gplv3.html  20 Oct 2008 17:29:50 -0000      1.12
+++ rms-why-gplv3.html  11 Sep 2009 21:56:28 -0000      1.13
@@ -12,18 +12,36 @@
 <!-- language, where necessary. -->
 
 <p>by <strong>Richard Stallman</strong></p>
-
+<p align="right">
+Index of topics
+<ol>
+  <li><a href="#choice">Upgrading is a Choice</a></li>
+  <li><a href="#incompatibility">Incompatibility with GPL v2</a></li>
+  <li><a href="#tivoization">Tivoization</a></li>
+  <li><a href="#drm">DRM</a></li>
+  <li><a href="#patent-deals">Patent Deals</a></li>
+  <li><a href="#patent-protection">Patent Protection</a></li>
+  <li><a href="#further-advantages">Better Internationalization</a></li>
+  <li><a href="#further-advantages">Gentler Licence Termination</a></li>
+  <li><a href="#further-advantages">BitTorrent Support</a></li>
+  <li><a href="#further-advantages">Apache Compatibility</a></li>
+  <li><a href="#gpl4">GPL v4</a></li>
+  <li><a href="#future-proofing">Easy Future Upgrades</a></li>
+</ol>
+</p>
 <p><a href="/licenses/gpl.html">Version 3 of the GNU General Public
 License</a> has been released, enabling free software packages to
 upgrade from GPL version 2.  This article explains why upgrading the
 license is important.</p>
 
-<p>First of all, it is important to note that upgrading is a choice.  GPL
+<p id="choice">
+First of all, it is important to note that upgrading is a choice.  GPL
 version 2 will remain a valid license, and no disaster will happen if
 some programs remain under GPLv2 while others advance to GPLv3.  These
 two licenses are incompatible, but that isn't a serious problem.</p>
 
-<p>When we say that GPLv2 and GPLv3 are incompatible, it means there is
+<p id="incompatibility">
+<a >When we say that GPLv2 and GPLv3 are incompatible, it means there is
 no legal way to combine code under GPLv2 with code under GPLv3 in a
 single program.  This is because both GPLv2 and GPLv3 are copyleft
 licenses: each of them says, &ldquo;If you include code under this license
@@ -45,7 +63,8 @@
 <p>Keeping a program under GPLv2 won't create problems.  The reason to
 migrate is because of the existing problems which GPLv3 will address.</p>
 
-<p>One major danger that GPLv3 will block is tivoization.  Tivoization
+<p id="tivoization">
+One major danger that GPLv3 will block is tivoization.  Tivoization
 means computers (called &ldquo;appliances&rdquo;) contain GPL-covered software
 that you can't change, because the appliance shuts down if it detects
 modified software.  The usual motive for tivoization is that the
@@ -62,7 +81,8 @@
 does, not merely that you can beg or threaten someone else who decides
 for you.</p>
 
-<p>In the crucial area of Digital Restrictions Management&mdash;nasty features
+<p id="drm">
+In the crucial area of Digital Restrictions Management&mdash;nasty features
 designed to restrict your use of the data in your
 computer&mdash;competition is no help, because relevant competition is
 forbidden.  Under the Digital Millennium Copyright Act and similar
@@ -87,7 +107,8 @@
 only for products that are almost exclusively meant for businesses and
 organizations.</p>
 
-<p>Another threat that GPLv3 resists is that of patent deals like the
+<p id="patent-deals">
+Another threat that GPLv3 resists is that of patent deals like the
 Novell-Microsoft deal.  Microsoft wants to use its thousands of
 patents to make GNU/Linux users pay Microsoft for the privilege, and
 made this deal to try to get that.  The deal offers Novell's customers
@@ -104,7 +125,8 @@
 Microsoft's future attempts to make redistributors collect Microsoft
 royalties from the program's users.</p>
 
-<p>GPLv3 also provides for explicit patent protection of the users from
+<p id="patent-protection">
+GPLv3 also provides for explicit patent protection of the users from
 the program's contributors and redistributors.  With GPLv2, users rely
 on an implicit patent license to make sure that the company which
 provided them a copy won't sue them, or the people they redistribute
@@ -138,17 +160,20 @@
 patents to tell some users &ldquo;That doesn't include you.&rdquo;  It also 
stops
 them from colluding with other patent holders to do this.</p>
 
-<p>Further advantages of GPLv3 include better internationalization, gentler
+<p id="further-advantages">
+Further advantages of GPLv3 include better internationalization, gentler
 termination, support for BitTorrent, and compatibility with the Apache
 license.  All in all, plenty of
 reason to upgrade.</p>
 
-<p>Change is unlikely to cease once GPLv3 is released.  If new threats to
+<p id="gpl4">
+Change is unlikely to cease once GPLv3 is released.  If new threats to
 users' freedom develop, we will have to develop GPL version 4.  It is
 important to make sure that programs will have no trouble upgrading to
 GPLv4 when the time comes.</p>
 
-<p>One way to do this is to release a program under &ldquo;GPL version 3 or any
+<p id="future-proofing">
+One way to do this is to release a program under &ldquo;GPL version 3 or any
 later version&rdquo;.  Another way is for all the contributors to a program
 to state a proxy who can decide on upgrading to future GPL versions.
 The third way is for all the contributors to assign copyright to one
@@ -193,7 +218,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2008/10/20 17:29:50 $
+$Date: 2009/09/11 21:56:28 $
 <!-- timestamp end -->
 </p>
 </div>