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

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

Parent Directory | Revision Log | View Patch Patch

-revision 1.121 by rms,
Mon May 27 03:49:32 2013 UTC
+revision 1.148 by rms,
Sat Aug 20 14:28:57 2016 UTC
 Line 1
  <!--#include virtual="/server/header.html" -->
+ <!-- Parent-Version: 1.77 -->
- <title>What is free software? - GNU Project - Free Software Foundation (FSF)</title>
+ <title>What is free software?
+ - GNU Project - Free Software Foundation</title>
  <meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, Linux, Emacs, GCC, Unix, Free Software, Operating System, GNU Kernel, HURD, GNU HURD, Hurd" />
  <meta http-equiv="Description" content="Since 1983, developing the free Unix style operating system GNU, so that computer users can have the freedom to share and improve the software they use." />
- <link rel="alternate" title="What's New" href="http://www.gnu.org/rss/whatsnew.rss" type="application/rss+xml" />
- <link rel="alternate" title="New Free Software" href="http://www.gnu.org/rss/quagga.rss" type="application/rss+xml" />
  <!--#include virtual="/philosophy/po/free-sw.translist" -->
  <!--#include virtual="/server/banner.html" -->
  <h2>What is free software?</h2>
+ <!--#include virtual="/licenses/fsf-licensing.html" -->
  <h3>The Free Software Definition</h3>
 Line 27 
 software.
  <p>
  &ldquo;Free software&rdquo; means software that respects users'
- freedom and community.  Roughly, <b>the users have the freedom to run,
+ freedom and community.  Roughly, it means that <b>the users have the
- copy, distribute, study, change and improve the software</b>.  With these
+ freedom to run, copy, distribute, study, change and improve the
- freedoms, the users (both individually and collectively) control the
+ software</b>.  Thus, &ldquo;free software&rdquo; is a matter of
- program and what it does for them.
+ liberty, not price.  To understand the concept, you should think of
+ &ldquo;free&rdquo; as in &ldquo;free speech,&rdquo; not as in
+ &ldquo;free beer&rdquo;.  We sometimes call it &ldquo;libre
+ software,&rdquo; borrowing the French or Spanish word for
+ &ldquo;free&rdquo; as in freedom, to show we do not mean the software
+ is gratis.
  </p>
  <p>
- When users don't control the program, the program controls the users.
+ We campaign for these freedoms because everyone deserves them.  With
- The developer controls the program, and through it controls the users.
+ these freedoms, the users (both individually and collectively) control
- This nonfree or &ldquo;proprietary&rdquo; program is therefore an
+ the program and what it does for them.  When users don't control the
- instrument of unjust power.
+ program, we call it a &ldquo;nonfree&rdquo; or
- </p>
+ &ldquo;proprietary&rdquo; program.  The nonfree program controls the
+ users, and the developer controls the program; this makes the
- <p>
+ program <a href="/philosophy/free-software-even-more-important.html">
- Thus, &ldquo;free software&rdquo; is a matter of liberty, not price.
+ an instrument of unjust power</a>.
- To understand the concept, you should think of &ldquo;free&rdquo; as
- in &ldquo;free speech,&rdquo; not as in &ldquo;free beer&rdquo;.
  </p>
  <p>
-Line 52 
 four essential freedoms:
+Line 55 
 four essential freedoms:
  </p>
  <ul>
-   <li>The freedom to run the program, for any purpose (freedom 0).</li>
+   <li>The freedom to run the program as you wish,
+       for any purpose (freedom 0).</li>
    <li>The freedom to study how the program works, and change it so it
        does your computing as you wish (freedom 1). Access to the source
        code is a precondition for this.
-Line 68 
 four essential freedoms:
+Line 72 
 four essential freedoms:
  </ul>
  <p>
- A program is free software if users have all of these freedoms.  Thus,
+ A program is free software if it gives users adequately all of these
- you should be free to redistribute copies, either with or without
+ freedoms.  Otherwise, it is nonfree.  While we can distinguish various
- modifications, either gratis or charging a fee for distribution, to
+ nonfree distribution schemes in terms of how far they fall short of
+ being free, we consider them all equally unethical.</p>
+ <p>In any given scenario, these freedoms must apply to whatever code
+ we plan to make use of, or lead others to make use of.  For instance,
+ consider a program A which automatically launches a program B to
+ handle some cases.  If we plan to distribute A as it stands, that
+ implies users will need B, so we need to judge whether both A and B
+ 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>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
+ 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.
-Line 95 
 for her purposes, but you are not entitl
+Line 115 
 for her purposes, but you are not entitl
  </p>
  <p>
+ The freedom to run the program as you wish means that you are not
+ forbidden or stopped from doing so.  It has nothing to do with what
+ functionality the program has, or whether it is useful for what you
+ want to do.</p>
+ <p>
  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
-Line 120 
 the original.  If the program is deliver
+Line 146 
 the original.  If the program is deliver
  run someone else's modified versions but refuse to run yours &mdash; a
  practice known as &ldquo;tivoization&rdquo; or &ldquo;lockdown&rdquo;,
  or (in its practitioners' perverse terminology) as &ldquo;secure
- boot&rdquo; &mdash; freedom 1 becomes a theoretical fiction rather
+ boot&rdquo; &mdash; freedom 1 becomes an empty pretense rather than a
- than a practical freedom.  This is not sufficient.  In other words,
+ practical reality.  These binaries are not free
- these binaries are not free software even if the source code they are
+ software even if the source code they are compiled from is free.
- compiled from is free.
  </p>
  <p>
-Line 154 
 cause, the software is not free.
+Line 179 
 cause, the software is not free.
  <p>
  However, certain kinds of rules about the manner of distributing free
  software are acceptable, when they don't conflict with the central
- freedoms.  For example, copyleft (very simply stated) is the rule that
+ freedoms.  For example, <a href="/copyleft/copyleft.html">copyleft</a>
- when redistributing the program, you cannot add restrictions to deny
+ (very simply stated) is the rule that when redistributing the program,
- other people the central freedoms.  This rule does not conflict with
+ you cannot add restrictions to deny other people the central freedoms.
- the central freedoms; rather it protects them.
+ This rule does not conflict with the central freedoms; rather it
+ protects them.
+ </p>
+ <p>
+ In the GNU project, we use copyleft to protect the four freedoms
+ legally for everyone.  We believe there are important reasons why
+ <a href="/philosophy/pragmatic.html">it is better to use
+ copyleft</a>.  However,
+ <a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">
+ noncopylefted free software</a> is ethical
+ too.  See <a href="/philosophy/categories.html">Categories of Free
+ Software</a> for a description of how &ldquo;free software,&rdquo;
+ &ldquo;copylefted software&rdquo; and other categories of software
+ relate to each other.
  </p>
  <p>
-Line 211 
 facility that allows you to specify the
+Line 250 
 facility that allows you to specify the
  alias for the modified version.</p>
  <p>
- In the GNU project, we use
- <a href="/copyleft/copyleft.html">copyleft</a>
- to protect these freedoms legally for everyone.  But
- <a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">noncopylefted
- free software</a> also exists.  We believe there are important reasons why
- <a href="/philosophy/pragmatic.html">it is better to use copyleft</a>,
- but if your program is noncopylefted free software, it is still basically
- ethical. (See <a href="/philosophy/categories.html">Categories of Free Software</a> for a description of how &ldquo;free software,&rdquo; &ldquo;copylefted software&rdquo; and other categories of software relate to each other.)
- </p>
- <p>
  Sometimes government <a id="exportcontrol">export control regulations</a>
  and trade sanctions can constrain your freedom to distribute copies of
  programs internationally.  Software developers do not have the power to
-Line 229 
 eliminate or override these restrictions
+Line 257 
 eliminate or override these restrictions
  is refuse to impose them as conditions of use of the program.  In this
  way, the restrictions will not affect activities and people outside the
  jurisdictions of these governments.  Thus, free software licenses
- must not require obedience to any export regulations as a condition of
+ must not require obedience to any nontrivial export regulations as a
- any of the essential freedoms.
+ condition of exercising any of the essential freedoms.
+ </p>
+ <p>
+ Merely mentioning the existence of export regulations, without making
+ them a condition of the license itself, is acceptable since it does
+ not restrict users.  If an export regulation is actually trivial for
+ free software, then requiring it as a condition is not an actual
+ problem; however, it is a potential problem, since a later change in
+ export law could make the requirement nontrivial and thus render the
+ software nonfree.
+ </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
+ comply with the licenses of &ldquo;all the programs you use&rdquo;, in
+ the case of a user that runs nonfree programs this would require
+ compliance with the licenses of those nonfree programs; that makes the
+ license nonfree.
+ </p>
+ <p>
+ It is acceptable for a free license to specify which jurisdiction's
+ law applies, or where litigation must be done, or both.
  </p>
  <p>
-Line 324 
 free cultural works</a> applicable to an
+Line 376 
 free cultural works</a> applicable to an
  <h3 id="open-source">Open Source?</h3>
  <p>
- Another group has started using the term &ldquo;open source&rdquo; to mean
+ Another group uses the term &ldquo;open source&rdquo; to mean
  something close (but not identical) to &ldquo;free software&rdquo;.  We
  prefer the term &ldquo;free software&rdquo; because, once you have heard that
  it refers to freedom rather than price, it calls to mind freedom.  The
-Line 340 
 was changed.</p>
+Line 392 
 was changed.</p>
  <ul>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.140&amp;r2=1.141">Version
+.141</a>: Clarify which code needs to be free.</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.134&amp;r2=1.135">Version
+.135</a>: Say each time that freedom 0 is the freedom to run the program
+ as you wish.</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.133&amp;r2=1.134">Version
+.134</a>: Freedom 0 is not a matter of the program's functionality.</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.130&amp;r2=1.131">Version
+.131</a>: A free license may not require compliance with a nonfree license
+ of another program.</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.128&amp;r2=1.129">Version
+.129</a>: State explicitly that choice of law and choice of forum
+ specifications are allowed.  (This was always our policy.)</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.121&amp;r2=1.122">Version
+.122</a>: An export control requirement is a real problem if the
+ requirement is nontrivial; otherwise it is only a potential problem.</li>
+ <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.117&amp;r2=1.118">Version
+.118</a>: Clarification: the issue is limits on your right to modify,
+ not on what modifications you have made.  And modifications are not limited
+ to &ldquo;improvements&rdquo;</li>
  <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.110&amp;r2=1.111">Version
 .111</a>: Clarify 1.77 by saying that only
  retroactive <em>restrictions</em> are unacceptable.  The copyright
-Line 419 
 licenses.</li>
+Line 498 
 licenses.</li>
  <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.10&amp;r2=1.11">Version
 .11</a>: Note that a free license may require you to send a copy of
- versions you distribute to the author.</li>
+ versions you distribute to previous developers on request.</li>
  </ul>
  <p>There are gaps in the version numbers shown above because there are
- other changes in this page that do not affect the definition as such.
+ other changes in this page that do not affect the definition or its
- These changes are in other parts of the page.  You can review the
+ interpretations.  For instance, the list does not include changes in
- complete list of changes to the page through
+ asides, formatting, spelling, punctuation, or other parts of the page.
+ You can review the complete list of changes to the page through
  the <a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log">cvsweb
  interface</a>.</p>
- </div>
+ </div><!-- for id="content", starts in the include above -->
  <!--#include virtual="/server/footer.html" -->
  <div id="footer">
+ <div class="unprintable">
- <p>
+ <p>Please send general FSF &amp; GNU inquiries to
- Please send FSF &amp; GNU inquiries to
  <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
  There are also <a href="/contact/">other ways to contact</a>
- the FSF.
+ the FSF.  Broken links and other corrections or suggestions can be sent
- <br />
+ to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
- Please send broken links and other corrections or suggestions to
- <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.
+ <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
- </p>
+         replace it with the translation of these two:
+         We work hard and do our best to provide accurate, good quality
+         translations.  However, we are not exempt from imperfection.
+         Please send your comments and general suggestions in this regard
+         to <a href="mailto:web-translators@gnu.org">
+         &lt;web-translators@gnu.org&gt;</a>.</p>
+         <p>For information on coordinating and submitting translations of
+         our web pages, see <a
+         href="/server/standards/README.translations.html">Translations
+         README</a>. -->
+ Please see the <a
+ href="/server/standards/README.translations.html">Translations
+ README</a> for information on coordinating and submitting translations
+ of this article.</p>
+ </div>
- <p>
+ <!-- Regarding copyright, in general, standalone pages (as opposed to
- Please see the
+      files generated as part of manuals) on the GNU web server should
- <a href="/server/standards/README.translations.html">Translations
+      be under CC BY-ND 4.0.  Please do NOT change or remove this
- README</a> for information on coordinating and submitting
+      without talking with the webmasters or licensing team first.
- translations of this article.
+      Please make sure the copyright date is consistent with the
- </p>
+      document.  For web pages, it is ok to list just the latest year the
+      document was modified, or published.
+      If you wish to list earlier years, that is ok too.
+      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+      years, as long as each year in the range is in fact a copyrightable
+      year, i.e., a year in which the document was published (including
+      being publicly visible on the web or in a revision control system).
+      There is more detail about copyright years in the GNU Maintainers
+      Information document, www.gnu.org/prep/maintain. -->
+ <p>Copyright &copy; 1996, 2002, 2004-2007, 2009-2016
+ Free Software Foundation, Inc.</p>
- <p>
- Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012 Free Software
- Foundation, Inc.
- </p>
  <p>This page is licensed under a <a rel="license"
- href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+ href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
- Commons Attribution-NoDerivs 3.0 United States License</a>.
+ Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
- </p>
  <!--#include virtual="/server/bottom-notes.html" -->
- <p>Updated:
+ <p class="unprintable">Updated:
  <!-- timestamp start -->
  $Date$
  <!-- timestamp end -->
  </p>
  </div>
  </div>
  </body>
  </html>

 Legend:



Removed from v.1.121
 


changed lines


 
Added in v.1.148
 Legend:



Removed from v.1.121
 


changed lines


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

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