/[www]/www/philosophy/free-sw.html

Diff of /www/philosophy/free-sw.html

Parent Directory | Revision Log | View Patch Patch

-revision 1.148 by rms,
Sat Aug 20 14:28:57 2016 UTC
+revision 1.149 by th_g,
Wed Nov 16 21:34:47 2016 UTC
 Line 10
  <!--#include virtual="/server/banner.html" -->
  <h2>What is free software?</h2>
- <!--#include virtual="/licenses/fsf-licensing.html" -->
  <h3>The Free Software Definition</h3>
+ <!--#include virtual="/licenses/fsf-licensing.html" -->
  <blockquote>
  <p>
  The free software definition presents the criteria for whether a
 Line 49 
 program <a href="/philosophy/free-softwa
  an instrument of unjust power</a>.
  </p>
+ <h4> The four essential freedoms</h4>
  <p>
  A program is free software if the program's users have the
  four essential freedoms:
-Line 85 
 implies users will need B, so we need to
+Line 87 
 implies users will need B, so we need to
  are free.  However, if we plan to modify A so that it doesn't use B,
  only A needs to be free; B is not pertinent to that plan.</p>
+ <p>
+ &ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  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.
+ You may have paid money to get copies of free software, or you may have
+ obtained copies at no charge.  But regardless of how you got your copies,
+ you always have the freedom to copy and change the software, even to
+ <a href="/philosophy/selling.html">sell copies</a>.
+ </p>
  <p>The rest of this page clarifies certain points about what makes
  specific freedoms adequate or not.</p>
- <p>Freedom to distribute (freedoms 2 and 3) means you are free to
+ <h4>The freedom to run the program as you wish</h4>
- redistribute copies, either with or without 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.
- </p>
- <p>
- You should also have the freedom to make modifications and use them
- privately in your own work or play, without even mentioning that they
- exist.  If you do publish your changes, you should not be required to
- notify anyone in particular, or in any particular way.
- </p>
  <p>
  The freedom to run the program means the freedom for any kind of person
 Line 120 
 forbidden or stopped from doing so.  It
  functionality the program has, or whether it is useful for what you
  want to do.</p>
- <p>
+ <h4>The freedom to study the source code and make changes</h4>
- 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
- 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
- make them.
- </p>
  <p>
  In order for freedoms 1 and 3 (the freedom to make changes and the
-Line 160 
 license is too restrictive to qualify as
+Line 151 
 license is too restrictive to qualify as
  </p>
  <p>
+ Whether a change constitutes an improvement is a subjective matter.
+ If your right to modify a program is limited, in substance, to changes that
+ someone else considers an improvement, that program is not free.
+ </p>
+ <h4>The freedom to redistribute if you wish: basic requirements</h4>
+ <p>Freedom to distribute (freedoms 2 and 3) means you are free to
+ redistribute copies, either with or without 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.
+ </p>
+ <p>
+ You should also have the freedom to make modifications and use them
+ privately in your own work or play, without even mentioning that they
+ exist.  If you do publish your changes, you should not be required to
+ notify anyone in particular, or in any particular way.
+ </p>
+ <p>
  Freedom 3 includes the freedom to release your modified versions
  as free software.  A free license may also permit other ways of
  releasing them; in other words, it does not have to be
-Line 169 
 as a free license.
+Line 183 
 as a free license.
  </p>
  <p>
- In order for these freedoms to be real, they must be permanent and
+ The freedom to redistribute copies must include binary or executable
- irrevocable as long as you do nothing wrong; if the developer of the
+ forms of the program, as well as source code, for both modified and
- software has the power to revoke the license, or retroactively add
+ unmodified versions.  (Distributing programs in runnable form is necessary
- restrictions to its terms, without your doing anything wrong to give
+ for conveniently installable free operating systems.)  It is OK if there
- cause, the software is not free.
+ 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
+ make them.
  </p>
+ <h4>Copyleft</h4>
  <p>
- However, certain kinds of rules about the manner of distributing free
+ Certain kinds of rules about the manner of distributing free
  software are acceptable, when they don't conflict with the central
  freedoms.  For example, <a href="/copyleft/copyleft.html">copyleft</a>
  (very simply stated) is the rule that when redistributing the program,
-Line 199 
 Software</a> for a description of how &l
+Line 218 
 Software</a> for a description of how &l
  relate to each other.
  </p>
- <p>
+ <h4>Rules about packaging and distribution details</h4>
- &ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  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.
- You may have paid money to get copies of free software, or you may have
- obtained copies at no charge.  But regardless of how you got your copies,
- you always have the freedom to copy and change the software, even to
- <a href="/philosophy/selling.html">sell copies</a>.
- </p>
- <p>
- Whether a change constitutes an improvement is a subjective matter.
- If your right to modify a program is limited, in substance, to changes that
- someone else considers an improvement, that program is not free.
- </p>
  <p>
- However, rules about how to package a modified version are acceptable,
+ 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
-Line 249 
 sort of requirement is acceptable only i
+Line 253 
 sort of requirement is acceptable only i
  facility that allows you to specify the original program's name as an
  alias for the modified version.</p>
+ <h4>Export regulations</h4>
  <p>
  Sometimes government <a id="exportcontrol">export control regulations</a>
  and trade sanctions can constrain your freedom to distribute copies of
-Line 271 
 export law could make the requirement no
+Line 277 
 export law could make the requirement no
  software nonfree.
  </p>
+ <h4>Legal considerations</h4>
+ <p>
+ In order for these freedoms to be real, they must be permanent and
+ irrevocable as long as you do nothing wrong; if the developer of the
+ software has the power to revoke the license, or retroactively add
+ restrictions to its terms, without your doing anything wrong to give
+ cause, the software is not free.
+ </p>
  <p>
  A free license may not require compliance with the license of a
  nonfree program.  Thus, for instance, if a license requires you to
-Line 285 
 It is acceptable for a free license to s
+Line 301 
 It is acceptable for a free license to s
  law applies, or where litigation must be done, or both.
  </p>
+ <h4>Contract-based licenses</h4>
  <p>
  Most free software licenses are based on copyright, and there are limits
  on what kinds of requirements can be imposed through copyright.  If a
-Line 304 
 legitimate, we will have to think about
+Line 322 
 legitimate, we will have to think about
  it is nonfree.
  </p>
+ <h4>Use the right words when talking about free software</h4>
  <p>
  When talking about free software, it is best to avoid using terms
  like &ldquo;give away&rdquo; or &ldquo;for free,&rdquo; because those terms imply that
-Line 315 
 a list of proper <a href="/philosophy/fs
+Line 335 
 a list of proper <a href="/philosophy/fs
  &ldquo;free software&rdquo;</a> into various languages.
  </p>
+ <h4>How we interpret these criteria</h4>
  <p>
  Finally, note that criteria such as those stated in this free software
  definition require careful thought for their interpretation.  To decide
-Line 329 
 a conclusion about a new issue, we often
+Line 351 
 a conclusion about a new issue, we often
  it easier to see why certain licenses do or don't qualify.
  </p>
+ <h4>Get help with free licenses</h4>
  <p>
  If you are interested in whether a specific license qualifies as a free
  software license, see our <a href="/licenses/license-list.html">list

 Legend:



Removed from v.1.148
 


changed lines


 
Added in v.1.149
 Legend:



Removed from v.1.148
 


changed lines


 
Added in v.1.149
-Removed from v.1.148
+Added in v.1.149

savannah-hackers-public@gnu.org	ViewVC Help
Powered by ViewVC 1.1.26