CVSROOT: /webcvs/www
Module name: www
Changes by: Richard M. Stallman <rms> 10/09/24 14:12:11
Modified files:
philosophy : free-sw.html
Log message:
Clarify meaning of packaging requirements.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/free-sw.html?cvsroot=www&r1=1.97&r2=1.98
Patches:
Index: free-sw.html
===================================================================
RCS file: /webcvs/www/www/philosophy/free-sw.html,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -b -r1.97 -r1.98
--- free-sw.html 1 Jul 2010 07:48:40 -0000 1.97
+++ free-sw.html 24 Sep 2010 14:12:05 -0000 1.98
@@ -157,18 +157,27 @@
</p>
<p>
-However, rules about how to package a modified version are acceptable, if they
-don't substantively limit your freedom to release modified versions, or
-your freedom to make and use modified versions privately. Rules that “if
-you make your version available in this way, you must make it available in
-that way also” can be acceptable too, on the same condition. (Note that
-such a rule still leaves you the choice of whether to publish your version
-at all.) Rules that require release of source code to the users for
-versions that you put into public use are also acceptable. It is also
-acceptable for the license to require that you identify
-your modifications as yours, or that, if you have distributed a modified
-version and a previous developer asks for a copy of it, you must send
-one.
+However, rules about how to package a modified version are acceptable,
+if they don't substantively limit your freedom to release modified
+versions, or your freedom to make and use modified versions privately.
+Thus, it is acceptable for the license to require that you change the
+name of the modified version, remove a logo, or identify your
+modifications as yours. As long as these requirements are not so
+burdensome that they effectively hamper you from releasing your
+changes, they are acceptable; you're already making other changes to
+the program, so you won't have trouble making a few more.
+</p>
+
+<p>
+Rules that “if you make your version available in this way, you
+must make it available in that way also” can be acceptable too,
+on the same condition. An example of such an acceptable rule is one
+saying that if you have distributed a
+modified version and a previous developer asks for a copy of it, you
+must send one. (Note that such a rule still leaves you the choice of
+whether to distribute your version at all.) Rules that require release
+of source code to the users for versions that you put into public use
+are also acceptable.
</p>
<p>
@@ -416,7 +425,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2010/07/01 07:48:40 $
+$Date: 2010/09/24 14:12:05 $
<!-- timestamp end -->
</p>
</div>
