www/licenses why-affero-gpl.html

[Richard M. Stallman]

CVSROOT:        /web/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       15/05/10 22:01:59

Modified files:
        licenses       : why-affero-gpl.html 

Log message:
        Correction: the AGPL source download requirement applies only to
        modified versions.
        
        Clarify the point that we couldn't fix the SaaSS problem with a
        software license.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/why-affero-gpl.html?cvsroot=www&r1=1.21&r2=1.22

Patches:
Index: why-affero-gpl.html
===================================================================
RCS file: /web/www/www/licenses/why-affero-gpl.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- why-affero-gpl.html 12 Apr 2014 12:39:52 -0000      1.21
+++ why-affero-gpl.html 10 May 2015 22:01:59 -0000      1.22
@@ -8,11 +8,9 @@
 
 <p>The GNU Affero General Public License is a modified version of the
 ordinary GNU GPL version 3.  It has one added requirement: if you run
-the program on a server and let other users communicate with it there,
-your server must also allow them to download the source code
-corresponding to the program that it's running.  If what's running
-there is your modified version of the program, the server's users must
-get the source code as you modified it.</p>
+a modified program on a server and let other users communicate with it
+there, your server must also allow them to download the source code
+corresponding to the modified version running there.</p>
 
 <p>The purpose of the GNU Affero GPL is to prevent a problem that
 affects developers of free programs that are often used on
@@ -62,9 +60,10 @@
 <p>We don't see any sensible way to address the SaaSS problem with
 license conditions on particular programs.  Even to write a legal
 condition to distinguish between SaaSS use and non-SaaSS use would be
-a challenge, and if we had that, it is not clear what we would want to
-require in the SaaSS case.  Thus, our solution to the problem of SaaSS
-is simple: refuse to use it.</p>
+a challenge, and if we had that, we don't see anything that the
+program's license might require in the SaaSS case that would correct
+the inherent wrong of SaaSS.  Thus, our solution to the problem of
+SaaSS is simple: refuse to use services that are SaaSS.</p>
 
 <p>If a program is meant specifically and only for SaaSS, you
 shouldn't write it.  But many programs are useful for a variety of
@@ -130,7 +129,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/04/12 12:39:52 $
+$Date: 2015/05/10 22:01:59 $
 <!-- timestamp end -->
 </p>
 </div>