[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Richard M. Stallman
Sat, 12 Dec 2009 14:54:28 +0000
Module name: www
Changes by: Richard M. Stallman <rms> 09/12/12 14:54:28
philosophy : free-sw.html
Minor cleanups in text.
RCS file: /webcvs/www/www/philosophy/free-sw.html,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -b -r1.87 -r1.88
--- free-sw.html 11 Dec 2009 15:54:22 -0000 1.87
+++ free-sw.html 12 Dec 2009 14:54:22 -0000 1.88
@@ -53,7 +53,7 @@
modifications, either gratis or charging a fee for distribution, to
<a href="#exportcontrol">anyone anywhere</a>. Being free to do these
things means (among other things) that you do not have to ask or pay
+for permission to do so.
@@ -69,7 +69,7 @@
overall job and purpose, without being required to communicate about it
with the developer or any other specific entity. In this freedom, it is
the <em>user's</em> purpose that matters, not the <em>developer's</em>
-purpose; you as a user are free to run a program for your purposes,
+purpose; you as a user are free to run the program for your purposes,
and if you distribute it to someone else, she is then free to run it
for her purposes, but you are not entitled to impose your purposes on her.
@@ -78,7 +78,7 @@
The freedom to redistribute copies must include binary or executable
forms of the program, as well as source code, for both modified and
unmodified versions. (Distributing programs in runnable form is necessary
-for conveniently installable free operating systems.) It is ok if there
+for conveniently installable free operating systems.) It is OK if there
is no way to produce a binary or executable form for a certain program
(since some languages don't support that feature), but you must have the
freedom to redistribute such forms should you find or develop a way to
@@ -86,10 +86,10 @@
-In order for the freedoms to make changes, and to publish improved
-versions, to be meaningful, you must have access to the source code of
-the program. Therefore, accessibility of source code is a necessary
-condition for free software.
+In order for freedoms 1 and 3 (the freedom to make changes and the
+freedom to publish improved versions) to be meaningful, you must have
+access to the source code of the program. Therefore, accessibility of
+source code is a necessary condition for free software.
@@ -106,8 +106,8 @@
One important way to modify a program is by merging in available free
subroutines and modules. If the program's license says that you
-cannot merge in a suitably-licensed existing module, such as if it
-requires you to be the copyright holder of any code you add, then the
+cannot merge in a suitably licensed existing module — for instance, if it
+requires you to be the copyright holder of any code you add — then the
license is too restrictive to qualify as free.
@@ -129,7 +129,7 @@
-<q>Free software</q> does not mean <q>non-commercial.</q> A free
+<q>Free software</q> does not mean <q>noncommercial.</q> A free
program must be available for commercial use, commercial development,
and commercial distribution. Commercial development of free software
is no longer unusual; such free commercial software is very important.
@@ -154,9 +154,10 @@
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, if you have distributed a
-modified version and a previous developer asks for a copy of it, you
-must send one, or that you identify yourself on your modifications.
+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
@@ -196,7 +197,7 @@
(though this does happen occasionally). However, some free software
licenses are based on contracts, and contracts can impose a much larger
range of possible restrictions. That means there are many possible ways
-such a license could be unacceptably restrictive and non-free.
+such a license could be unacceptably restrictive and nonfree.
@@ -204,7 +205,7 @@
contract-based license restricts the user in an unusual way that
copyright-based licenses cannot, and which isn't mentioned here as
legitimate, we will have to think about it, and we will probably conclude
-it is non-free.
+it is nonfree.
@@ -214,7 +215,7 @@
as <q>piracy</q> embody opinions we hope you won't endorse. See
<a href="/philosophy/words-to-avoid.html">Confusing Words and Phrases that
are Worth Avoiding</a> for a discussion of these terms. We also have
-a list of <a href="/philosophy/fs-translations.html">translations of
+a list of proper <a href="/philosophy/fs-translations.html">translations of
<q>free software</q></a> into various languages.
@@ -241,16 +242,16 @@
-If you are contemplating writing a new license, please contact the FSF
-by writing to that address. The proliferation of different free software
-licenses means increased work for users in understanding the licenses;
-we may be able to help you find an existing Free Software license that
-meets your needs.
+If you are contemplating writing a new license, please contact the
+Free Software Foundation first by writing to that address. The
+proliferation of different free software licenses means increased work
+for users in understanding the licenses; we may be able to help you
+find an existing free software license that meets your needs.
If that isn't possible, if you really need a new license, with our
-help you can ensure that the license really is a Free Software license
+help you can ensure that the license really is a free software license
and avoid various practical problems.
@@ -398,7 +399,7 @@
<!-- timestamp start -->
-$Date: 2009/12/11 15:54:22 $
+$Date: 2009/12/12 14:54:22 $
<!-- timestamp end -->