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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.37 by novalis, Thu May 5 19:37:14 2005 UTC revision 1.124 by ineiev, Tue Oct 15 04:42:00 2013 UTC
# Line 1  Line 1 
1  <?xml version="1.0" encoding="utf-8" ?>  <!--#include virtual="/server/header.html" -->
2  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"  <!-- Parent-Version: 1.75 -->
3      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">  <title>What is free software?
4  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">  - GNU Project - Free Software Foundation</title>
   
 <head>  
 <title>The Free Software Definition - GNU Project - Free Software Foundation (FSF)</title>  
 <meta http-equiv="content-type" content='text/html; charset=utf-8' />  
 <link rel="stylesheet" type="text/css" href="/gnu.css" />  
 <link rev="made" href="mailto:webmasters@gnu.org" />  
 </head>  
   
 <!-- This document is in XML, and xhtml 1.0 -->  
 <!-- Please make sure to properly nest your tags -->  
 <!-- and ensure that your final document validates -->  
 <!-- consistent with W3C xhtml 1.0 and CSS standards -->  
 <!-- See validator.w3.org -->  
5    
6  <body>  <meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, Linux, Emacs, GCC, Unix, Free Software, Operating System, GNU Kernel, HURD, GNU HURD, Hurd" />
7    <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." />
8    
9  <p><a href="#translations">Translations</a> of this page</p>  <!--#include virtual="/philosophy/po/free-sw.translist" -->
10    <!--#include virtual="/server/banner.html" -->
11    
12    <h2>What is free software?</h2>
13    
14  <h3>The Free Software Definition</h3>  <h3>The Free Software Definition</h3>
15    
16    <blockquote>
17    <p>
18    The free software definition presents the criteria for whether a
19    particular software program qualifies as free software.  From time to
20    time we revise this definition, to clarify it or to resolve questions
21    about subtle issues.  See the <a href="#History">History section</a>
22    below for a list of changes that affect the definition of free
23    software.
24    </p>
25    </blockquote>
26    
27  <p>  <p>
28  <a href="/graphics/philosophicalgnu.html"><img src="/graphics/philosophical-gnu-sm.jpg" alt=" [image of a Philosophical Gnu] " width="160" height="200" /></a>  &ldquo;Free software&rdquo; means software that respects users'
29    freedom and community.  Roughly, <b>the users have the freedom to run,
30    copy, distribute, study, change and improve the software</b>.  With these
31    freedoms, the users (both individually and collectively) control the
32    program and what it does for them.
33  </p>  </p>
34    
35  <p>  <p>
36  We maintain this free software definition to show clearly what must be  When users don't control the program, the program controls the users.
37  true about a particular software program for it to be considered  The developer controls the program, and through it controls the users.
38  free software.</p>  This nonfree or &ldquo;proprietary&rdquo; program is therefore an
39    instrument of unjust power.
40    </p>
41    
42  <p>  <p>
43  ``Free software'' is a matter of liberty, not price.  To understand the  Thus, &ldquo;free software&rdquo; is a matter of liberty, not price.
44  concept, you should think of ``free'' as in ``free speech,'' not as in  To understand the concept, you should think of &ldquo;free&rdquo; as
45  ``free beer.''</p>  in &ldquo;free speech,&rdquo; not as in &ldquo;free beer&rdquo;.
46    </p>
47    
48  <p>  <p>
49  Free software is a matter of the users' freedom to run, copy,  A program is free software if the program's users have the
50  distribute, study, change and improve the software.  More precisely,  four essential freedoms:
51  it refers to four kinds of freedom, for the users of the software:</p>  </p>
52    
53  <ul>  <ul>
54    <li>The freedom to run the program, for any purpose (freedom 0).</li>    <li>The freedom to run the program, for any purpose (freedom 0).</li>
55    <li>The freedom to study how the program works, and adapt it to your needs    <li>The freedom to study how the program works, and change it so it
56        (freedom 1).   Access to the source code is a precondition for this.</li>        does your computing as you wish (freedom 1). Access to the source
57          code is a precondition for this.
58      </li>
59    <li>The freedom to redistribute copies so you can help your neighbor    <li>The freedom to redistribute copies so you can help your neighbor
60        (freedom 2).</li>        (freedom 2).
61    <li>The freedom to improve the program, and release your improvements    </li>
62       to the public, so that the whole community benefits    <li>The freedom to distribute copies of your modified versions
63        (freedom 3).   Access to the source code is a precondition for this.</li>        to others (freedom 3).  By doing this you can give the whole
64          community a chance to benefit from your changes.
65          Access to the source code is a precondition for this.
66      </li>
67  </ul>  </ul>
68    
69  <p>  <p>
70  A program is free software if users have all of these freedoms.  A program is free software if users have all of these freedoms.  Thus,
71  Thus, you should be free to redistribute copies, either with or  you should be free to redistribute copies, either with or without
72  without modifications, either gratis or charging a fee for  modifications, either gratis or charging a fee for distribution, to
73  distribution, to <a href="#exportcontrol">anyone anywhere</a>.  Being  <a href="#exportcontrol">anyone anywhere</a>.  Being free to do these
74  free to do these things means (among other things) that you do not  things means (among other things) that you do not have to ask or pay
75  have to ask or pay for permission.</p>  for permission to do so.
76    </p>
77    
78  <p>  <p>
79  You should also have the freedom to make modifications and use them  You should also have the freedom to make modifications and use them
80  privately in your own work or play, without even mentioning that they  privately in your own work or play, without even mentioning that they
81  exist.  If you do publish your changes, you should not be required to  exist.  If you do publish your changes, you should not be required to
82  notify anyone in particular, or in any particular way.</p>  notify anyone in particular, or in any particular way.
83    </p>
84    
85  <p>  <p>
86  The freedom to use a program means the freedom for any kind of person  The freedom to run the program means the freedom for any kind of person
87  or organization to use it on any kind of computer system, for any kind  or organization to use it on any kind of computer system, for any kind of
88  of overall job, and without being required to communicate subsequently  overall job and purpose, without being required to communicate about it
89  with the developer or any other specific entity.</p>  with the developer or any other specific entity.  In this freedom, it is
90    the <em>user's</em> purpose that matters, not the <em>developer's</em>
91    purpose; you as a user are free to run the program for your purposes,
92    and if you distribute it to someone else, she is then free to run it
93    for her purposes, but you are not entitled to impose your purposes on her.
94    </p>
95    
96  <p>  <p>
97  The freedom to redistribute copies must include binary or executable  The freedom to redistribute copies must include binary or executable
98  forms of the program, as well as source code, for both modified and  forms of the program, as well as source code, for both modified and
99  unmodified versions.  (Distributing programs in runnable form is  unmodified versions.  (Distributing programs in runnable form is necessary
100  necessary for conveniently installable free operating systems.)  It is  for conveniently installable free operating systems.)  It is OK if there
101  ok if there is no way to produce a binary or executable form for a  is no way to produce a binary or executable form for a certain program
102  certain program (since some languages don't support that feature), but  (since some languages don't support that feature), but you must have the
103  you must have the freedom to redistribute such forms should you find  freedom to redistribute such forms should you find or develop a way to
104  or develop a way to make them.</p>  make them.
105  <p>  </p>
106  In order for the freedoms to make changes, and to publish improved  
107  versions, to be meaningful, you must have access to the source code of  <p>
108  the program.  Therefore, accessibility of source code is a necessary  In order for freedoms 1 and 3 (the freedom to make changes and the
109  condition for free software.</p>  freedom to publish the changed versions) to be meaningful, you must have
110  <p>  access to the source code of the program.  Therefore, accessibility of
111  In order for these freedoms to be real, they must be irrevocable as  source code is a necessary condition for free software.  Obfuscated
112  long as you do nothing wrong; if the developer of the software has the  &ldquo;source code&rdquo; is not real source code and does not count
113  power to revoke the license, without your doing anything to give  as source code.
114  cause, the software is not free.</p>  </p>
115    
116    <p>
117    Freedom 1 includes the freedom to use your changed version in place of
118    the original.  If the program is delivered in a product designed to
119    run someone else's modified versions but refuse to run yours &mdash; a
120    practice known as &ldquo;tivoization&rdquo; or &ldquo;lockdown&rdquo;,
121    or (in its practitioners' perverse terminology) as &ldquo;secure
122    boot&rdquo; &mdash; freedom 1 becomes a theoretical fiction rather
123    than a practical freedom.  This is not sufficient.  In other words,
124    these binaries are not free software even if the source code they are
125    compiled from is free.
126    </p>
127    
128    <p>
129    One important way to modify a program is by merging in available free
130    subroutines and modules.  If the program's license says that you
131    cannot merge in a suitably licensed existing module &mdash; for instance, if it
132    requires you to be the copyright holder of any code you add &mdash; then the
133    license is too restrictive to qualify as free.
134    </p>
135    
136    <p>
137    Freedom 3 includes the freedom to release your modified versions
138    as free software.  A free license may also permit other ways of
139    releasing them; in other words, it does not have to be
140    a <a href="/copyleft/copyleft.html">copyleft</a> license.  However, a
141    license that requires modified versions to be nonfree does not qualify
142    as a free license.
143    </p>
144    
145    <p>
146    In order for these freedoms to be real, they must be permanent and
147    irrevocable as long as you do nothing wrong; if the developer of the
148    software has the power to revoke the license, or retroactively add
149    restrictions to its terms, without your doing anything wrong to give
150    cause, the software is not free.
151    </p>
152    
153  <p>  <p>
154  However, certain kinds of rules about the manner of distributing free  However, certain kinds of rules about the manner of distributing free
155  software are acceptable, when they don't conflict with the central  software are acceptable, when they don't conflict with the central
156  freedoms.  For example, copyleft (very simply stated) is the rule that  freedoms.  For example, copyleft (very simply stated) is the rule that
157  when redistributing the program, you cannot add restrictions to deny  when redistributing the program, you cannot add restrictions to deny
158  other people the central freedoms.  This rule does not conflict with  other people the central freedoms.  This rule does not conflict with
159  the central freedoms; rather it protects them.</p>  the central freedoms; rather it protects them.
160    </p>
161    
162  <p>  <p>
163  You may have paid money to get copies of free software, or you  &ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  A free
164  may have obtained copies at no charge.  But regardless of how you got  program must be available for commercial use, commercial development,
165  your copies, you always have the freedom to copy and change the  and commercial distribution.  Commercial development of free software
166  software, even to <a href="/philosophy/selling.html">sell copies</a>.</p>  is no longer unusual; such free commercial software is very important.
167  <p>  You may have paid money to get copies of free software, or you may have
168  ``Free software'' does not mean ``non-commercial''.  A free program  obtained copies at no charge.  But regardless of how you got your copies,
169  must be available for commercial use, commercial development, and  you always have the freedom to copy and change the software, even to
170  commercial distribution.  Commercial development of free software is  <a href="/philosophy/selling.html">sell copies</a>.
171  no longer unusual; such free commercial software is very important.</p>  </p>
172  <p>  
 Rules about how to package a modified version are acceptable, if they  
 don't substantively block your freedom to release modified versions.  
 Rules that ``if you make the program 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 the program or not.)  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.</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">non-copylefted  
 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 non-copylefted free  
 software, we can still use it.</p>  
 <p>  
 See <a href="/philosophy/categories.html">Categories of Free Software</a>  
 for a description of how ``free software,'' ``copylefted software'' 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 eliminate or override these restrictions, but  
 what they can and must do 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.</p>  
 <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 copyright-based license respects freedom in the ways described  
 above, it is unlikely to have some other sort of problem that we never  
 anticipated (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.</p>  
 <p>  
 We can't possibly list all the possible contract restrictions that  
 would be unacceptable.  If a 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 decide it is non-free.</p>  
 <p>  
 When talking about free software, it is best to avoid using terms like  
 ``give away'' or ``for free'', because those terms imply that the  
 issue is about price, not freedom.  Some common terms such as  
 ``piracy'' 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 "free software"</a> into various languages.</p>  
173  <p>  <p>
174  Finally, note that criteria such as those stated in this free software  Whether a change constitutes an improvement is a subjective matter.
175  definition require careful thought for their interpretation.  To  If your right to modify a program is limited, in substance, to changes that
176  decide whether a specific software license qualifies as a free  someone else considers an improvement, that program is not free.
 software license, we judge it based on these criteria to determine  
 whether it fits their spirit as well as the precise words.  If a  
 license includes unconscionable restrictions, we reject it, even if we  
 did not anticipate the issue in these criteria.  Sometimes a license  
 requirement raises an issue that calls for extensive thought,  
 including discussions with a lawyer, before we can decide if the  
 requirement is acceptable.  When we reach a conclusion about a new  
 issue, we often update these criteria to make it easier to see why  
 certain licenses do or don't qualify.</p>  
 <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 of licenses</a>.  If the  
 license you are concerned with is not listed there, you can ask us  
 about it by sending us email at <a  
 href="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</a>.</p> <p>  
 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.  
177  </p>  </p>
178    
179  <p>  <p>
180  If that isn't possible, if you really need a new license, with our  However, rules about how to package a modified version are acceptable,
181  help you can ensure that the license really is a Free Software license  if they don't substantively limit your freedom to release modified
182  and avoid various practical problems.  versions, or your freedom to make and use modified versions privately.
183    Thus, it is acceptable for the license to require that you change the
184    name of the modified version, remove a logo, or identify your
185    modifications as yours.  As long as these requirements are not so
186    burdensome that they effectively hamper you from releasing your
187    changes, they are acceptable; you're already making other changes to
188    the program, so you won't have trouble making a few more.
189  </p>  </p>
 <hr />  
190    
191  <p>  <p>
192  Another group has started using the term "open source" to mean  Rules that &ldquo;if you make your version available in this way, you
193  something close (but not identical) to "free software".  We prefer the  must make it available in that way also&rdquo; can be acceptable too,
194  term "free software" because, once you have heard it refers to freedom  on the same condition.  An example of such an acceptable rule is one
195  rather than price, <a href="free-software-for-freedom.html">it calls  saying that if you have distributed a
196  to mind freedom</a>.  The word "open" never does that.</p>  modified version and a previous developer asks for a copy of it, you
197    must send one.  (Note that such a rule still leaves you the choice of
198  <hr />  whether to distribute your version at all.)  Rules that require release
199  <h4><a href="/philosophy/philosophy.html">Other Texts to Read</a></h4>  of source code to the users for versions that you put into public use
200    are also acceptable.
   
 <!-- All pages on the GNU web server should have the section about    -->  
 <!-- verbatim copying.  Please do NOT remove this without talking     -->  
 <!-- with the webmasters first. -->  
 <!-- Please make sure the copyright date is consistent with the document -->  
 <!-- and that it is like this "2001, 2002" not this "2001-2002." -->  
   
 <div class="translations">  
 <p><a id="translations"></a>  
 <b>Translations of this page</b>:<br />  
   
 <!-- Please keep this list alphabetical, and in the original -->  
 <!-- language if possible, otherwise default to English -->  
 <!-- If you do not have it English, please comment what the -->  
 <!-- English is.  If you add a new language here, please -->  
 <!-- advise web-translators@gnu.org and add it to -->  
 <!--    - in /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->  
 <!--    - in /home/www/html/server/standards/README.translations.html -->  
 <!--      one of the lists under the section "Translations Underway" -->  
 <!--    - if there is a translation team, you also have to add an alias -->  
 <!--      to mail.gnu.org:/com/mailer/aliases -->  
 <!-- Please also check you have the 2 letter language code right versus -->  
 <!--     http://www.w3.org/WAI/ER/IG/ert/iso639.htm -->  
 [  
   <a href="/philosophy/free-sw.ca.html">Catal&#x00e0;</a>       <!-- Catalan -->  
   
 <!-- Chinese (Simplified) -->  
 | <a href="/philosophy/free-sw.cn.html">&#x7b80;&#x4f53;&#x4e2d;&#x6587;</a>  
   
 <!-- Chinese (Traditional) -->  
 | <a href="/philosophy/free-sw.zh.html">&#x7e41;&#x9ad4;&#x4e2d;&#x6587;</a>  
   
 | <a href="/philosophy/free-sw.cs.html">&#x010c;esky</a>        <!-- Czech -->  
 | <a href="/philosophy/free-sw.da.html">Dansk</a>       <!-- Danish -->  
 | <a href="/philosophy/free-sw.de.html">Deutsch</a>     <!-- German -->  
 | <a href="/philosophy/free-sw.html">English</a>  
 | <a href="/philosophy/free-sw.es.html">Espa&#x00f1;ol</a>      <!-- Spanish -->  
   
 <!-- Persian/Farsi -->  
 | <a href="/philosophy/free-sw.fa.html">&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc;</a>  
   
 | <a href="/philosophy/free-sw.fr.html">Fran&#x00e7;ais</a>     <!-- French -->  
 | <a href="/philosophy/free-sw.gl.html">Galego</a>      <!-- Galician -->  
 | <a href="/philosophy/free-sw.he.html">&#x05e2;&#x05d1;&#x05e8;&#x05d9;&#x05ea;</a>    <!-- Hebrew -->  
 | <a href="/philosophy/free-sw.hr.html">Hrvatski</a>    <!-- Croatian -->  
 | <a href="/philosophy/free-sw.id.html">Bahasa Indonesia</a>    <!-- Indonesian -->  
 | <a href="/philosophy/free-sw.it.html">Italiano</a>    <!-- Italian -->  
 | <a href="/philosophy/free-sw.ja.html">&#x65e5;&#x672c;&#x8a9e;</a>    <!-- Japanese -->  
 | <a href="/philosophy/free-sw.ko.html">&#xd55c;&#xad6d;&#xc5b4;</a>    <!-- Korean -->  
 | <a href="/philosophy/free-sw.hu.html">Magyar</a>      <!-- Hungarian -->  
 | <a href="/philosophy/free-sw.nl.html">Nederlands</a>  <!-- Dutch -->  
 | <a href="/philosophy/free-sw.no.html">Norsk</a>       <!-- Norwegian -->  
 | <a href="/philosophy/free-sw.pl.html">Polski</a>      <!-- Polish -->  
 | <a href="/philosophy/free-sw.pt.html">Portugu&#x0ea;s</a>     <!-- Portuguese -->  
 | <a href="/philosophy/free-sw.ro.html">Rom&#x00e2;n&#x0103;</a>        <!-- Romanian -->  
 | <a href="/philosophy/free-sw.ru.html">&#1056;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;</a> <!-- Russian -->  
 | <a href="/philosophy/free-sw.sl.html">Slovinsko</a>   <!--- Slovenian -->  
 | <a href="/philosophy/free-sw.sr.html">&#x0421;&#x0440;&#x043f;&#x0441;&#x043a;&#x0438;</a> <!-- Serbian -->  
 | <a href="/philosophy/free-sw.tr.html">T&#x00fc;rk&#x00e7;e</a>        <!-- Turkish -->  
 ]  
201  </p>  </p>
 </div>  
202    
 <div class="copyright">  
203  <p>  <p>
204  Return to the <a href="/home.html">GNU Project home page</a>.  A special issue arises when a license requires changing the name by
205    which the program will be invoked from other programs.  That
206    effectively hampers you from releasing your changed version so that it
207    can replace the original when invoked by those other programs.  This
208    sort of requirement is acceptable only if there's a suitable aliasing
209    facility that allows you to specify the original program's name as an
210    alias for the modified version.</p>
211    
212    <p>
213    In the GNU project, we use
214    <a href="/copyleft/copyleft.html">copyleft</a>
215    to protect these freedoms legally for everyone.  But
216    <a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">noncopylefted
217    free software</a> also exists.  We believe there are important reasons why
218    <a href="/philosophy/pragmatic.html">it is better to use copyleft</a>,
219    but if your program is noncopylefted free software, it is still basically
220    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.)
221  </p>  </p>
222    
223  <p>  <p>
224  Please send FSF &amp; GNU inquiries to  Sometimes government <a id="exportcontrol">export control regulations</a>
225  <a href="mailto:gnu@gnu.org"><em>gnu@gnu.org</em></a>.  and trade sanctions can constrain your freedom to distribute copies of
226  There are also <a href="/home.html#ContactInfo">other ways to contact</a>  programs internationally.  Software developers do not have the power to
227  the FSF.  eliminate or override these restrictions, but what they can and must do
228  <br />  is refuse to impose them as conditions of use of the program.  In this
229  Please send broken links and other corrections (or suggestions) to  way, the restrictions will not affect activities and people outside the
230  <a href="mailto:webmasters@gnu.org"><em>webmasters@gnu.org</em></a>.  jurisdictions of these governments.  Thus, free software licenses
231    must not require obedience to any nontrivial export regulations as a
232    condition of exercising any of the essential freedoms.
233  </p>  </p>
234    
235  <p>  <p>
236  Please see the  Merely mentioning the existence of export regulations, without making
237  <a href="/server/standards/README.translations.html">Translations  them a condition of the license itself, is acceptable since it does
238  README</a> for information on coordinating and submitting  not restrict users.  If an export regulation is actually trivial for
239  translations of this article.  free software, then requiring it as a condition is not an actual
240    problem; however, it is a potential problem, since a later change in
241    export law could make the requirement nontrivial and thus render the
242    software nonfree.
243  </p>  </p>
244    
245  <p>  <p>
246  Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free  Most free software licenses are based on copyright, and there are limits
247  Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  on what kinds of requirements can be imposed through copyright.  If a
248  02110,  USA  copyright-based license respects freedom in the ways described above, it
249  <br />  is unlikely to have some other sort of problem that we never anticipated
250  Verbatim copying and distribution of this entire article is  (though this does happen occasionally).  However, some free software
251  permitted in any medium without royalty provided this notice is  licenses are based on contracts, and contracts can impose a much larger
252  preserved.  range of possible restrictions.  That means there are many possible ways
253    such a license could be unacceptably restrictive and nonfree.
254  </p>  </p>
255    
256  <p>  <p>
257  Updated:  We can't possibly list all the ways that might happen.  If a
258    contract-based license restricts the user in an unusual way that
259    copyright-based licenses cannot, and which isn't mentioned here as
260    legitimate, we will have to think about it, and we will probably conclude
261    it is nonfree.
262    </p>
263    
264    <p>
265    When talking about free software, it is best to avoid using terms
266    like &ldquo;give away&rdquo; or &ldquo;for free,&rdquo; because those terms imply that
267    the issue is about price, not freedom.  Some common terms such
268    as &ldquo;piracy&rdquo; embody opinions we hope you won't endorse.  See
269    <a href="/philosophy/words-to-avoid.html">Confusing Words and Phrases that
270    are Worth Avoiding</a> for a discussion of these terms.  We also have
271    a list of proper <a href="/philosophy/fs-translations.html">translations of
272    &ldquo;free software&rdquo;</a> into various languages.
273    </p>
274    
275    <p>
276    Finally, note that criteria such as those stated in this free software
277    definition require careful thought for their interpretation.  To decide
278    whether a specific software license qualifies as a free software license,
279    we judge it based on these criteria to determine whether it fits their
280    spirit as well as the precise words.  If a license includes unconscionable
281    restrictions, we reject it, even if we did not anticipate the issue
282    in these criteria.  Sometimes a license requirement raises an issue
283    that calls for extensive thought, including discussions with a lawyer,
284    before we can decide if the requirement is acceptable.  When we reach
285    a conclusion about a new issue, we often update these criteria to make
286    it easier to see why certain licenses do or don't qualify.
287    </p>
288    
289    <p>
290    If you are interested in whether a specific license qualifies as a free
291    software license, see our <a href="/licenses/license-list.html">list
292    of licenses</a>.  If the license you are concerned with is not
293    listed there, you can ask us about it by sending us email at
294    <a href="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</a>.
295    </p>
296    
297    <p>
298    If you are contemplating writing a new license, please contact the
299    Free Software Foundation first by writing to that address. The
300    proliferation of different free software licenses means increased work
301    for users in understanding the licenses; we may be able to help you
302    find an existing free software license that meets your needs.
303    </p>
304    
305    <p>
306    If that isn't possible, if you really need a new license, with our
307    help you can ensure that the license really is a free software license
308    and avoid various practical problems.
309    </p>
310    
311    <h3 id="beyond-software">Beyond Software</h3>
312    
313    <p>
314    <a href="/philosophy/free-doc.html">Software manuals must be free</a>,
315    for the same reasons that software must be free, and because the
316    manuals are in effect part of the software.
317    </p>
318    
319    <p>
320    The same arguments also make sense for other kinds of works of
321    practical use &mdash; that is to say, works that embody useful knowledge,
322    such as educational works and reference
323    works.  <a href="http://wikipedia.org">Wikipedia</a> is the best-known
324    example.
325    </p>
326    
327    <p>
328    Any kind of work <em>can</em> be free, and the definition of free software
329    has been extended to a definition of <a href="http://freedomdefined.org/">
330    free cultural works</a> applicable to any kind of works.
331    </p>
332    
333    <h3 id="open-source">Open Source?</h3>
334    
335    <p>
336    Another group has started using the term &ldquo;open source&rdquo; to mean
337    something close (but not identical) to &ldquo;free software&rdquo;.  We
338    prefer the term &ldquo;free software&rdquo; because, once you have heard that
339    it refers to freedom rather than price, it calls to mind freedom.  The
340    word &ldquo;open&rdquo; <a href="/philosophy/open-source-misses-the-point.html">
341    never refers to freedom</a>.
342    </p>
343    
344    <h3 id="History">History</h3>
345    
346    <p>From time to time we revise this Free Software Definition.  Here is
347    the list of substantive changes, along with links to show exactly what
348    was changed.</p>
349    
350    <ul>
351    
352    <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
353    1.122</a>: An export control requirement is a real problem if the
354    requirement is nontrivial; otherwise it is only a potential problem.</li>
355    
356    <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
357    1.111</a>: Clarify 1.77 by saying that only
358    retroactive <em>restrictions</em> are unacceptable.  The copyright
359    holders can always grant additional <em>permission</em> for use of the
360    work by releasing the work in another way in parallel.</li>
361    
362    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.104&amp;r2=1.105">Version
363    1.105</a>: Reflect, in the brief statement of freedom 1, the point
364    (already stated in version 1.80) that it includes really using your modified
365    version for your computing.</li>
366    
367    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.91&amp;r2=1.92">Version
368    1.92</a>: Clarify that obfuscated code does not qualify as source code.</li>
369    
370    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.89&amp;r2=1.90">Version
371    1.90</a>: Clarify that freedom 3 means the right to distribute copies
372    of your own modified or improved version, not a right to participate
373    in someone else's development project.</li>
374    
375    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.88&amp;r2=1.89">Version
376    1.89</a>: Freedom 3 includes the right to release modified versions as
377    free software.</li>
378    
379    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.79&amp;r2=1.80">Version
380    1.80</a>: Freedom 1 must be practical, not just theoretical;
381    i.e., no tivoization.</li>
382    
383    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.76&amp;r2=1.77">Version
384    1.77</a>: Clarify that all retroactive changes to the license are
385    unacceptable, even if it's not described as a complete
386    replacement.</li>
387    
388    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.73&amp;r2=1.74">Version
389    1.74</a>: Four clarifications of points not explicit enough, or stated
390    in some places but not reflected everywhere:
391    <ul>
392    <li>"Improvements" does not mean the license can
393    substantively limit what kinds of modified versions you can release.
394    Freedom 3 includes distributing modified versions, not just changes.</li>
395    <li>The right to merge in existing modules
396    refers to those that are suitably licensed.</li>
397    <li>Explicitly state the conclusion of the point about export controls.</li>
398    <li>Imposing a license change constitutes revoking the old license.</li>
399    </ul>
400    </li>
401    
402    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.56&amp;r2=1.57">Version
403    1.57</a>: Add &quot;Beyond Software&quot; section.</li>
404    
405    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.45&amp;r2=1.46">Version
406    1.46</a>: Clarify whose purpose is significant in the freedom to run
407    the program for any purpose.</li>
408    
409    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.40&amp;r2=1.41">Version
410    1.41</a>: Clarify wording about contract-based licenses.</li>
411    
412    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.39&amp;r2=1.40">Version
413    1.40</a>: Explain that a free license must allow to you use other
414    available free software to create your modifications.</li>
415    
416    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.38&amp;r2=1.39">Version
417    1.39</a>: Note that it is acceptable for a license to require you to
418    provide source for versions of the software you put into public
419    use.</li>
420    
421    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.30&amp;r2=1.31">Version
422    1.31</a>: Note that it is acceptable for a license to require you to
423    identify yourself as the author of modifications.  Other minor
424    clarifications throughout the text.</li>
425    
426    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.22&amp;r2=1.23">Version
427    1.23</a>: Address potential problems related to contract-based
428    licenses.</li>
429    
430    <li><a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.15&amp;r2=1.16">Version
431    1.16</a>: Explain why distribution of binaries is important.</li>
432    
433    <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
434    1.11</a>: Note that a free license may require you to send a copy of
435    versions you distribute to the author.</li>
436    
437    </ul>
438    
439    <p>There are gaps in the version numbers shown above because there are
440    other changes in this page that do not affect the definition as such.
441    These changes are in other parts of the page.  You can review the
442    complete list of changes to the page through
443    the <a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log">cvsweb
444    interface</a>.</p>
445    
446    
447    </div><!-- for id="content", starts in the include above -->
448    <!--#include virtual="/server/footer.html" -->
449    <div id="footer">
450    
451    <p>Please send general FSF &amp; GNU inquiries to
452    <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
453    There are also <a href="/contact/">other ways to contact</a>
454    the FSF.  Broken links and other corrections or suggestions can be sent
455    to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
456    
457    <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
458            replace it with the translation of these two:
459    
460            We work hard and do our best to provide accurate, good quality
461            translations.  However, we are not exempt from imperfection.
462            Please send your comments and general suggestions in this regard
463            to <a href="mailto:web-translators@gnu.org">
464            &lt;web-translators@gnu.org&gt;</a>.</p>
465    
466            <p>For information on coordinating and submitting translations of
467            our web pages, see <a
468            href="/server/standards/README.translations.html">Translations
469            README</a>. -->
470    Please see the <a
471    href="/server/standards/README.translations.html">Translations
472    README</a> for information on coordinating and submitting translations
473    of this article.</p>
474    
475    <!-- Regarding copyright, in general, standalone pages (as opposed to
476         files generated as part of manuals) on the GNU web server should
477         be under CC BY-ND 3.0 US.  Please do NOT change or remove this
478         without talking with the webmasters or licensing team first.
479         Please make sure the copyright date is consistent with the
480         document.  For web pages, it is ok to list just the latest year the
481         document was modified, or published.
482        
483         If you wish to list earlier years, that is ok too.
484         Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
485         years, as long as each year in the range is in fact a copyrightable
486         year, i.e., a year in which the document was published (including
487         being publicly visible on the web or in a revision control system).
488        
489         There is more detail about copyright years in the GNU Maintainers
490         Information document, www.gnu.org/prep/maintain. -->
491    
492    <p>Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012, 2013
493    Free Software Foundation, Inc.</p>
494    
495    <p>This page is licensed under a <a rel="license"
496    href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
497    Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
498    
499    <!--#include virtual="/server/bottom-notes.html" -->
500    
501    <p>Updated:
502  <!-- timestamp start -->  <!-- timestamp start -->
503  $Date$ $Author$  $Date$
504  <!-- timestamp end -->  <!-- timestamp end -->
505  </p>  </p>
506  </div>  </div>
507    </div>
508  </body>  </body>
509  </html>  </html>

Legend:
Removed from v.1.37  
changed lines
  Added in v.1.124

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