/[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.23 by rms, Tue Feb 17 12:12:30 2004 UTC revision 1.136 by josh, Thu Jun 26 20:59:38 2014 UTC
# Line 1  Line 1 
1  <!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">  <!--#include virtual="/server/header.html" -->
2  <HTML>  <!-- Parent-Version: 1.77 -->
3  <HEAD>  <title>What is free software?
4  <TITLE>The Free Software Definition - GNU Project - Free Software Foundation (FSF)</TITLE>  - GNU Project - Free Software Foundation</title>
5  <LINK REV="made" HREF="mailto:webmasters@www.gnu.org">  
6  </HEAD>  <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  <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" VLINK="#9900DD">  <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  <H3>The Free Software Definition</H3>  
9    <!--#include virtual="/philosophy/po/free-sw.translist" -->
10  <A HREF="/graphics/philosophicalgnu.html"><IMG SRC="/graphics/philosophical-gnu-sm.jpg"  <!--#include virtual="/server/banner.html" -->
11     ALT=" [image of a Philosophical Gnu] "  
12     WIDTH="160" HEIGHT="200"></A>  <h2>What is free software?</h2>
13    <!--#include virtual="/licenses/fsf-licensing.html" -->
14  [  
15  <!-- Please keep this list alphabetical -->  <h3>The Free Software Definition</h3>
16  <!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->  
17  <A HREF="/philosophy/free-sw.hr.html">Croatian</A>  <blockquote>
18  | <A HREF="/philosophy/free-sw.cs.html">Czech</A>  <p>
19  | <A HREF="/philosophy/free-sw.da.html">Danish</A>  The free software definition presents the criteria for whether a
20  | <A HREF="/philosophy/free-sw.nl.html">Dutch</A>  particular software program qualifies as free software.  From time to
21  | <A HREF="/philosophy/free-sw.html">English</A>  time we revise this definition, to clarify it or to resolve questions
22  | <A HREF="/philosophy/free-sw.fr.html">French</A>  about subtle issues.  See the <a href="#History">History section</a>
23  | <A HREF="/philosophy/free-sw.gl.html">Galician</A>  below for a list of changes that affect the definition of free
24  | <A HREF="/philosophy/free-sw.de.html">German</A>  software.
25  | <A HREF="/philosophy/free-sw.hu.html">Hungarian</A>  </p>
26  | <A HREF="/philosophy/free-sw.id.html">Indonesian</A>  </blockquote>
27  | <A HREF="/philosophy/free-sw.it.html">Italian</A>  
28  | <A HREF="/philosophy/free-sw.ja.html">Japanese</A>  <p>
29  | <A HREF="/philosophy/free-sw.ko.html">Korean</A>  &ldquo;Free software&rdquo; means software that respects users'
30  | <A HREF="/philosophy/free-sw.no.html">Norwegian</A>  freedom and community.  Roughly, it means that <b>the users have the
31  | <A HREF="/philosophy/free-sw.pl.html">Polish</A>  freedom to run, copy, distribute, study, change and improve the
32  | <A HREF="/philosophy/free-sw.pt.html">Portuguese</A>  software</b>.  Thus, &ldquo;free software&rdquo; is a matter of
33  | <A HREF="/philosophy/free-sw.ro.html">Romanian</A>  liberty, not price.  To understand the concept, you should think of
34  | <A HREF="/philosophy/free-sw.ru.html">Russian</A>  &ldquo;free&rdquo; as in &ldquo;free speech,&rdquo; not as in
35  | <A HREF="/philosophy/free-sw.sl.html">Slovenian</A>  &ldquo;free beer&rdquo;.
36  | <A HREF="/philosophy/free-sw.es.html">Spanish</A>  </p>
37  | <A HREF="/philosophy/free-sw.sv.html">Swedish</A>    
38  | <A HREF="/philosophy/free-sw.tr.html">Turkish</A>  <p>
39  <!-- Please keep this list alphabetical -->  We campaign for these freedoms because everyone deserves them.  With
40  <!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->  these freedoms, the users (both individually and collectively) control
41  ]  the program and what it does for them.  When users don't control the
42  <P>  program, we call it a &ldquo;nonfree&rdquo; or
43    &ldquo;proprietary&rdquo; program.  The nonfree program controls the
44  We maintain this free software definition to show clearly what must be  users, and the developer controls the program; this makes the
45  true about a particular software program for it to be considered  program <a href="/philosophy/free-software-even-more-important.html">
46  free software.  an instrument of unjust power</a>.
47    </p>
48  <P>  
49    <p>
50  ``Free software'' is a matter of liberty, not price.  To understand the  A program is free software if the program's users have the
51  concept, you should think of ``free'' as in ``free speech,'' not as in  four essential freedoms:
52  ``free beer.''  </p>
53  <P>  
54  Free software is a matter of the users' freedom to run, copy,  <ul>
55  distribute, study, change and improve the software.  More precisely,    <li>The freedom to run the program as you wish,
56  it refers to four kinds of freedom, for the users of the software:        for any purpose (freedom 0).</li>
57  <P>    <li>The freedom to study how the program works, and change it so it
58          does your computing as you wish (freedom 1). Access to the source
59  <UL>        code is a precondition for this.
60    <LI>The freedom to run the program, for any purpose (freedom 0).    </li>
61    <LI>The freedom to study how the program works, and adapt it to your needs    <li>The freedom to redistribute copies so you can help your neighbor
       (freedom 1).   Access to the source code is a precondition for this.  
   <LI>The freedom to redistribute copies so you can help your neighbor  
62        (freedom 2).        (freedom 2).
63    <LI>The freedom to improve the program, and release your improvements    </li>
64       to the public, so that the whole community benefits    <li>The freedom to distribute copies of your modified versions
65        (freedom 3).   Access to the source code is a precondition for this.        to others (freedom 3).  By doing this you can give the whole
66  </UL>        community a chance to benefit from your changes.
67          Access to the source code is a precondition for this.
68  <P>    </li>
69  A program is free software if users have all of these freedoms.  </ul>
70  Thus, you should be free to redistribute copies, either with or  
71  without modifications, either gratis or charging a fee for  <p>
72  distribution, to <A HREF="#exportcontrol">anyone anywhere</A>.  Being  A program is free software if it gives users adequately all of these
73  free to do these things means (among other things) that you do not  freedoms.  Otherwise, it is nonfree.  While we can distinguish various
74  have to ask or pay for permission.  nonfree distribution schemes in terms of how far they fall short of
75    being free, we consider them all equally unethical.</p>
76    
77    <p>The rest of this page clarifies certain points about what makes
78    specific freedoms adequate or not.</p>
79    
80    <p>Freedom to distribute (freedoms 2 and 3) means you are free to
81    redistribute copies, either with or without modifications, either
82    gratis or charging a fee for distribution, to
83    <a href="#exportcontrol">anyone anywhere</a>.  Being free to do these
84    things means (among other things) that you do not have to ask or pay
85    for permission to do so.
86    </p>
87    
88  <P>  <p>
89  You should also have the freedom to make modifications and use them  You should also have the freedom to make modifications and use them
90  privately in your own work or play, without even mentioning that they  privately in your own work or play, without even mentioning that they
91  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
92  notify anyone in particular, or in any particular way.  notify anyone in particular, or in any particular way.
93    </p>
94    
95  <P>  <p>
96  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
97  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
98  of overall job, and without being required to communicate subsequently  overall job and purpose, without being required to communicate about it
99  with the developer or any other specific entity.  with the developer or any other specific entity.  In this freedom, it is
100    the <em>user's</em> purpose that matters, not the <em>developer's</em>
101    purpose; you as a user are free to run the program for your purposes,
102    and if you distribute it to someone else, she is then free to run it
103    for her purposes, but you are not entitled to impose your purposes on her.
104    </p>
105    
106    <p>
107    The freedom to run the program as you wish means that you are not
108    forbidden or stopped from doing so.  It has nothing to do with what
109    functionality the program has, or whether it is useful for what you
110    want to do.</p>
111    
112  <P>  <p>
113  The freedom to redistribute copies must include binary or executable  The freedom to redistribute copies must include binary or executable
114  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
115  unmodified versions.  (Distributing programs in runnable form is  unmodified versions.  (Distributing programs in runnable form is necessary
116  necessary for conveniently installable free operating systems.)  It is  for conveniently installable free operating systems.)  It is OK if there
117  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
118  certain program (since some languages don't support that feature), but  (since some languages don't support that feature), but you must have the
119  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
120  or develop a way to make them.  make them.
121    </p>
122  <P>  
123  In order for the freedoms to make changes, and to publish improved  <p>
124  versions, to be meaningful, you must have access to the source code of  In order for freedoms 1 and 3 (the freedom to make changes and the
125  the program.  Therefore, accessibility of source code is a necessary  freedom to publish the changed versions) to be meaningful, you must have
126  condition for free software.  access to the source code of the program.  Therefore, accessibility of
127    source code is a necessary condition for free software.  Obfuscated
128  <P>  &ldquo;source code&rdquo; is not real source code and does not count
129  In order for these freedoms to be real, they must be irrevocable as  as source code.
130  long as you do nothing wrong; if the developer of the software has the  </p>
131  power to revoke the license, without your doing anything to give  
132    <p>
133    Freedom 1 includes the freedom to use your changed version in place of
134    the original.  If the program is delivered in a product designed to
135    run someone else's modified versions but refuse to run yours &mdash; a
136    practice known as &ldquo;tivoization&rdquo; or &ldquo;lockdown&rdquo;,
137    or (in its practitioners' perverse terminology) as &ldquo;secure
138    boot&rdquo; &mdash; freedom 1 becomes a theoretical fiction rather
139    than a practical freedom.  This is not sufficient.  In other words,
140    these binaries are not free software even if the source code they are
141    compiled from is free.
142    </p>
143    
144    <p>
145    One important way to modify a program is by merging in available free
146    subroutines and modules.  If the program's license says that you
147    cannot merge in a suitably licensed existing module &mdash; for instance, if it
148    requires you to be the copyright holder of any code you add &mdash; then the
149    license is too restrictive to qualify as free.
150    </p>
151    
152    <p>
153    Freedom 3 includes the freedom to release your modified versions
154    as free software.  A free license may also permit other ways of
155    releasing them; in other words, it does not have to be
156    a <a href="/copyleft/copyleft.html">copyleft</a> license.  However, a
157    license that requires modified versions to be nonfree does not qualify
158    as a free license.
159    </p>
160    
161    <p>
162    In order for these freedoms to be real, they must be permanent and
163    irrevocable as long as you do nothing wrong; if the developer of the
164    software has the power to revoke the license, or retroactively add
165    restrictions to its terms, without your doing anything wrong to give
166  cause, the software is not free.  cause, the software is not free.
167    </p>
168    
169  <P>  <p>
170  However, certain kinds of rules about the manner of distributing free  However, certain kinds of rules about the manner of distributing free
171  software are acceptable, when they don't conflict with the central  software are acceptable, when they don't conflict with the central
172  freedoms.  For example, copyleft (very simply stated) is the rule that  freedoms.  For example, copyleft (very simply stated) is the rule that
173  when redistributing the program, you cannot add restrictions to deny  when redistributing the program, you cannot add restrictions to deny
174  other people the central freedoms.  This rule does not conflict with  other people the central freedoms.  This rule does not conflict with
175  the central freedoms; rather it protects them.  the central freedoms; rather it protects them.
176    </p>
177    
178  <P>  <p>
179  Thus, you may have paid money to get copies of free software, or you  In the GNU project, we use <a href="/copyleft/copyleft.html">
180  may have obtained copies at no charge.  But regardless of how you got  copyleft </a> to protect the four freedoms legally for everyone.  We
181  your copies, you always have the freedom to copy and change the  believe there are important reasons why
182  software, even to <A HREF="/philosophy/selling.html">sell copies</A>.  <a href="/philosophy/pragmatic.html">it is better to use
183  <P>  copyleft</a>.  However,
184    <a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">
185  ``Free software'' does not mean ``non-commercial''.  A free program  noncopylefted free software</a> is ethical
186  must be available for commercial use, commercial development, and  too.  See <a href="/philosophy/categories.html">Categories of Free
187  commercial distribution.  Commercial development of free software is  Software</a> for a description of how &ldquo;free software,&rdquo;
188  no longer unusual; such free commercial software is very important.  &ldquo;copylefted software&rdquo; and other categories of software
189    relate to each other.
190  <P>  </p>
191  Rules about how to package a modified version are acceptable, if they  
192  don't effectively block your freedom to release modified versions.  <p>
193  Rules that ``if you make the program available in this way, you must  &ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  A free
194  make it available in that way also'' can be acceptable too, on the  program must be available for commercial use, commercial development,
195  same condition.  (Note that such a rule still leaves you the choice of  and commercial distribution.  Commercial development of free software
196  whether to publish the program or not.)  It is also acceptable for the  is no longer unusual; such free commercial software is very important.
197  license to require that, if you have distributed a modified version  You may have paid money to get copies of free software, or you may have
198  and a previous developer asks for a copy of it, you must send one.  obtained copies at no charge.  But regardless of how you got your copies,
199    you always have the freedom to copy and change the software, even to
200  <P>  <a href="/philosophy/selling.html">sell copies</a>.
201  In the GNU project, we use <A HREF="/copyleft/copyleft.html">  </p>
202  ``copyleft''</A> to protect these freedoms legally for everyone.  But  
203  <A HREF="/philosophy/categories.html#Non-CopyleftedFreeSoftware">  <p>
204  non-copylefted free software</A> also exists.  We believe there are  Whether a change constitutes an improvement is a subjective matter.
205  important reasons why <A HREF="/philosophy/pragmatic.html"> it is  If your right to modify a program is limited, in substance, to changes that
206  better to use copyleft</A>, but if your program is non-copylefted free  someone else considers an improvement, that program is not free.
207  software, we can still use it.  </p>
208    
209  <P>  <p>
210  See <A HREF="/philosophy/categories.html">Categories of Free Software  However, rules about how to package a modified version are acceptable,
211         (18k characters)</A>  if they don't substantively limit your freedom to release modified
212  for a description of how ``free software,'' ``copylefted software'' and  versions, or your freedom to make and use modified versions privately.
213  other categories of software relate to each other.  Thus, it is acceptable for the license to require that you change the
214    name of the modified version, remove a logo, or identify your
215  <P>  modifications as yours.  As long as these requirements are not so
216  Sometimes government <A NAME="exportcontrol">export control  burdensome that they effectively hamper you from releasing your
217  regulations</A> and trade sanctions can constrain your freedom to  changes, they are acceptable; you're already making other changes to
218  distribute copies of programs internationally.  Software developers do  the program, so you won't have trouble making a few more.
219  not have the power to eliminate or override these restrictions, but  </p>
220  what they can and must do is refuse to impose them as conditions of  
221  use of the program.  In this way, the restrictions will not affect  <p>
222  activities and people outside the jurisdictions of these governments.  Rules that &ldquo;if you make your version available in this way, you
223    must make it available in that way also&rdquo; can be acceptable too,
224  <P>  on the same condition.  An example of such an acceptable rule is one
225  Most free software licenses are based on copyright, and there are  saying that if you have distributed a
226  limits on what kinds of requirements can be imposed through copyright.  modified version and a previous developer asks for a copy of it, you
227  If a copyright-based license respects freedom in the ways described  must send one.  (Note that such a rule still leaves you the choice of
228  above, it is unlikely to have some other sort of problem that we never  whether to distribute your version at all.)  Rules that require release
229  anticipated (though this does happen occasionally).  However, some  of source code to the users for versions that you put into public use
230  free software licenses are based on contracts, and contracts can  are also acceptable.
231  impose a much larger range of possible restrictions.  That means there  </p>
232  are many possible ways such a license could be unacceptably  
233  restrictive and non-free.  <p>
234  <P>  A special issue arises when a license requires changing the name by
235  We can't possibly list all the possible contract restrictions that  which the program will be invoked from other programs.  That
236  would be unacceptable.  If a contract-based license restricts the user  effectively hampers you from releasing your changed version so that it
237  in an unusual way that copyright-based licenses cannot, and which  can replace the original when invoked by those other programs.  This
238  isn't mentioned here as legitimate, we will have to think about it,  sort of requirement is acceptable only if there's a suitable aliasing
239  and we will probably decide it is non-free.  facility that allows you to specify the original program's name as an
240  <P>  alias for the modified version.</p>
241  When talking about free software, it is best to avoid using terms like  
242  ``give away'' or ``for free'', because those terms imply that the  <p>
243  issue is about price, not freedom.  Some common terms such as  Sometimes government <a id="exportcontrol">export control regulations</a>
244  ``piracy'' embody opinions we hope you won't endorse.  See <A  and trade sanctions can constrain your freedom to distribute copies of
245  HREF="/philosophy/words-to-avoid.html">Confusing Words and Phrases  programs internationally.  Software developers do not have the power to
246  that are Worth Avoiding</A> for a discussion of these terms.  eliminate or override these restrictions, but what they can and must do
247  We also have a list of <A HREF="/philosophy/fs-translations.html">translations  is refuse to impose them as conditions of use of the program.  In this
248  of "free software"</A> into various languages.  way, the restrictions will not affect activities and people outside the
249    jurisdictions of these governments.  Thus, free software licenses
250  <P>  must not require obedience to any nontrivial export regulations as a
251    condition of exercising any of the essential freedoms.
252    </p>
253    
254    <p>
255    Merely mentioning the existence of export regulations, without making
256    them a condition of the license itself, is acceptable since it does
257    not restrict users.  If an export regulation is actually trivial for
258    free software, then requiring it as a condition is not an actual
259    problem; however, it is a potential problem, since a later change in
260    export law could make the requirement nontrivial and thus render the
261    software nonfree.
262    </p>
263    
264    <p>
265    A free license may not require compliance with the license of a
266    nonfree program.  Thus, for instance, if a license requires you to
267    comply with the licenses of &ldquo;all the programs you use&rdquo;, in
268    the case of a user that runs nonfree programs this would require
269    compliance with the licenses of those nonfree programs; that makes the
270    license nonfree.
271    </p>
272    
273    <p>
274    It is acceptable for a free license to specify which jurisdiction's
275    law applies, or where litigation must be done, or both.
276    </p>
277    
278    <p>
279    Most free software licenses are based on copyright, and there are limits
280    on what kinds of requirements can be imposed through copyright.  If a
281    copyright-based license respects freedom in the ways described above, it
282    is unlikely to have some other sort of problem that we never anticipated
283    (though this does happen occasionally).  However, some free software
284    licenses are based on contracts, and contracts can impose a much larger
285    range of possible restrictions.  That means there are many possible ways
286    such a license could be unacceptably restrictive and nonfree.
287    </p>
288    
289    <p>
290    We can't possibly list all the ways that might happen.  If a
291    contract-based license restricts the user in an unusual way that
292    copyright-based licenses cannot, and which isn't mentioned here as
293    legitimate, we will have to think about it, and we will probably conclude
294    it is nonfree.
295    </p>
296    
297    <p>
298    When talking about free software, it is best to avoid using terms
299    like &ldquo;give away&rdquo; or &ldquo;for free,&rdquo; because those terms imply that
300    the issue is about price, not freedom.  Some common terms such
301    as &ldquo;piracy&rdquo; embody opinions we hope you won't endorse.  See
302    <a href="/philosophy/words-to-avoid.html">Confusing Words and Phrases that
303    are Worth Avoiding</a> for a discussion of these terms.  We also have
304    a list of proper <a href="/philosophy/fs-translations.html">translations of
305    &ldquo;free software&rdquo;</a> into various languages.
306    </p>
307    
308    <p>
309  Finally, note that criteria such as those stated in this free software  Finally, note that criteria such as those stated in this free software
310  definition require careful thought for their interpretation.  To  definition require careful thought for their interpretation.  To decide
311  decide whether a specific software license qualifies as a free  whether a specific software license qualifies as a free software license,
312  software license, we judge it based on these criteria to determine  we judge it based on these criteria to determine whether it fits their
313  whether it fits their spirit as well as the precise words.  If a  spirit as well as the precise words.  If a license includes unconscionable
314  license includes unconscionable restrictions, we reject it, even if we  restrictions, we reject it, even if we did not anticipate the issue
315  did not anticipate the issue in these criteria.  Sometimes a license  in these criteria.  Sometimes a license requirement raises an issue
316  requirement raises an issue that calls for extensive thought,  that calls for extensive thought, including discussions with a lawyer,
317  including discussions with a lawyer, before we can decide if the  before we can decide if the requirement is acceptable.  When we reach
318  requirement is acceptable.  When we reach a conclusion about a new  a conclusion about a new issue, we often update these criteria to make
319  issue, we often update these criteria to make it easier to see why  it easier to see why certain licenses do or don't qualify.
320  certain licenses do or don't qualify.  </p>
321    
322  <P>  <p>
323    If you are interested in whether a specific license qualifies as a free
324  If you are interested in whether a specific license qualifies as a  software license, see our <a href="/licenses/license-list.html">list
325  free software license, see our <A  of licenses</a>.  If the license you are concerned with is not
326  HREF="/licenses/license-list.html">list of licenses</A>.  If the  listed there, you can ask us about it by sending us email at
327  license you are concerned with is not listed there, you can ask us  <a href="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</a>.
328  about it by sending us email at <A  </p>
329  HREF="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</A>.  
330    <p>
331  <HR>  If you are contemplating writing a new license, please contact the
332    Free Software Foundation first by writing to that address. The
333  <H4><A HREF="/philosophy/philosophy.html">Other Texts to Read</A></H4>  proliferation of different free software licenses means increased work
334    for users in understanding the licenses; we may be able to help you
335  <P>  find an existing free software license that meets your needs.
336  Another group has started using the term "open source" to mean  </p>
337  something close (but not identical) to "free software".  We prefer the  
338  term "free software" because, once you have heard it refers to freedom  <p>
339  rather than price, <A HREF="free-software-for-freedom.html">it calls  If that isn't possible, if you really need a new license, with our
340  to mind freedom</A>.  help you can ensure that the license really is a free software license
341    and avoid various practical problems.
342  <HR>  </p>
343  [  
344  <!-- Please keep this list alphabetical -->  <h3 id="beyond-software">Beyond Software</h3>
345  <!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->  
346  <A HREF="/philosophy/free-sw.hr.html">Croatian</A>  <p>
347  | <A HREF="/philosophy/free-sw.cs.html">Czech</A>  <a href="/philosophy/free-doc.html">Software manuals must be free</a>,
348  | <A HREF="/philosophy/free-sw.da.html">Danish</A>  for the same reasons that software must be free, and because the
349  | <A HREF="/philosophy/free-sw.nl.html">Dutch</A>  manuals are in effect part of the software.
350  | <A HREF="/philosophy/free-sw.html">English</A>  </p>
351  | <A HREF="/philosophy/free-sw.fr.html">French</A>  
352  | <A HREF="/philosophy/free-sw.gl.html">Galician</A>  <p>
353  | <A HREF="/philosophy/free-sw.de.html">German</A>  The same arguments also make sense for other kinds of works of
354  | <A HREF="/philosophy/free-sw.hu.html">Hungarian</A>  practical use &mdash; that is to say, works that embody useful knowledge,
355  | <A HREF="/philosophy/free-sw.id.html">Indonesian</A>  such as educational works and reference
356  | <A HREF="/philosophy/free-sw.it.html">Italian</A>  works.  <a href="http://wikipedia.org">Wikipedia</a> is the best-known
357  | <A HREF="/philosophy/free-sw.ja.html">Japanese</A>  example.
358  | <A HREF="/philosophy/free-sw.ko.html">Korean</A>  </p>
359  | <A HREF="/philosophy/free-sw.no.html">Norwegian</A>  
360  | <A HREF="/philosophy/free-sw.pl.html">Polish</A>  <p>
361  | <A HREF="/philosophy/free-sw.pt.html">Portuguese</A>  Any kind of work <em>can</em> be free, and the definition of free software
362  | <A HREF="/philosophy/free-sw.ro.html">Romanian</A>  has been extended to a definition of <a href="http://freedomdefined.org/">
363  | <A HREF="/philosophy/free-sw.ru.html">Russian</A>  free cultural works</a> applicable to any kind of works.
364  | <A HREF="/philosophy/free-sw.sl.html">Slovenian</A>        </p>
365  | <A HREF="/philosophy/free-sw.es.html">Spanish</A>  
366  | <A HREF="/philosophy/free-sw.tr.html">Turkish</A>  <h3 id="open-source">Open Source?</h3>
367  <!-- Please keep this list alphabetical -->  
368  <!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->  <p>
369  ]  Another group has started using the term &ldquo;open source&rdquo; to mean
370  <P>  something close (but not identical) to &ldquo;free software&rdquo;.  We
371  Return to <A HREF="/home.html">GNU's home page</A>.  prefer the term &ldquo;free software&rdquo; because, once you have heard that
372  <P>  it refers to freedom rather than price, it calls to mind freedom.  The
373    word &ldquo;open&rdquo; <a href="/philosophy/open-source-misses-the-point.html">
374  Please send FSF &amp; GNU inquiries &amp; questions to  never refers to freedom</a>.
375    </p>
376  <A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.  
377  There are also <A HREF="/home.html#ContactInfo">other ways to  <h3 id="History">History</h3>
378  contact</A> the FSF.  
379  <P>  <p>From time to time we revise this Free Software Definition.  Here is
380    the list of substantive changes, along with links to show exactly what
381  Please send comments on these web pages to  was changed.</p>
382    
383  <A HREF="mailto:webmasters@gnu.org"><EM>webmasters@gnu.org</EM></A>,  <ul>
384  send other questions to  
385  <A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.  <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
386  <P>  1.135</a>: Say each time that freedom 0 is the freedom to run the program
387  Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, Free  as you wish.</li>
388  Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  
389  02111,  USA  <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
390  <P>  1.134</a>: Freedom 0 is not a matter of the program's functionality.</li>
391  Verbatim copying and distribution of this entire article is  
392  permitted in any medium, provided this notice is preserved.  <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
393  <P>  1.131</a>: A free license may not require compliance with a nonfree license
394  Updated:  of another program.</li>
395    
396    <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
397    1.129</a>: State explicitly that choice of law and choice of forum
398    specifications are allowed.  (This was always our policy.)</li>
399    
400    <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
401    1.122</a>: An export control requirement is a real problem if the
402    requirement is nontrivial; otherwise it is only a potential problem.</li>
403    
404    <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
405    1.118</a>: Clarification: the issue is limits on your right to modify,
406    not on what modifications you have made.  And modifications are not limited
407    to &ldquo;improvements&rdquo;</li>
408    
409    <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
410    1.111</a>: Clarify 1.77 by saying that only
411    retroactive <em>restrictions</em> are unacceptable.  The copyright
412    holders can always grant additional <em>permission</em> for use of the
413    work by releasing the work in another way in parallel.</li>
414    
415    <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
416    1.105</a>: Reflect, in the brief statement of freedom 1, the point
417    (already stated in version 1.80) that it includes really using your modified
418    version for your computing.</li>
419    
420    <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
421    1.92</a>: Clarify that obfuscated code does not qualify as source code.</li>
422    
423    <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
424    1.90</a>: Clarify that freedom 3 means the right to distribute copies
425    of your own modified or improved version, not a right to participate
426    in someone else's development project.</li>
427    
428    <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
429    1.89</a>: Freedom 3 includes the right to release modified versions as
430    free software.</li>
431    
432    <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
433    1.80</a>: Freedom 1 must be practical, not just theoretical;
434    i.e., no tivoization.</li>
435    
436    <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
437    1.77</a>: Clarify that all retroactive changes to the license are
438    unacceptable, even if it's not described as a complete
439    replacement.</li>
440    
441    <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
442    1.74</a>: Four clarifications of points not explicit enough, or stated
443    in some places but not reflected everywhere:
444    <ul>
445    <li>"Improvements" does not mean the license can
446    substantively limit what kinds of modified versions you can release.
447    Freedom 3 includes distributing modified versions, not just changes.</li>
448    <li>The right to merge in existing modules
449    refers to those that are suitably licensed.</li>
450    <li>Explicitly state the conclusion of the point about export controls.</li>
451    <li>Imposing a license change constitutes revoking the old license.</li>
452    </ul>
453    </li>
454    
455    <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
456    1.57</a>: Add &quot;Beyond Software&quot; section.</li>
457    
458    <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
459    1.46</a>: Clarify whose purpose is significant in the freedom to run
460    the program for any purpose.</li>
461    
462    <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
463    1.41</a>: Clarify wording about contract-based licenses.</li>
464    
465    <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
466    1.40</a>: Explain that a free license must allow to you use other
467    available free software to create your modifications.</li>
468    
469    <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
470    1.39</a>: Note that it is acceptable for a license to require you to
471    provide source for versions of the software you put into public
472    use.</li>
473    
474    <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
475    1.31</a>: Note that it is acceptable for a license to require you to
476    identify yourself as the author of modifications.  Other minor
477    clarifications throughout the text.</li>
478    
479    <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
480    1.23</a>: Address potential problems related to contract-based
481    licenses.</li>
482    
483    <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
484    1.16</a>: Explain why distribution of binaries is important.</li>
485    
486    <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
487    1.11</a>: Note that a free license may require you to send a copy of
488    versions you distribute to the author.</li>
489    
490    </ul>
491    
492    <p>There are gaps in the version numbers shown above because there are
493    other changes in this page that do not affect the definition or its
494    interpretations.  For instance, the list does not include changes in
495    asides, formatting, spelling, punctuation, or other parts of the page.
496    You can review the complete list of changes to the page through
497    the <a href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log">cvsweb
498    interface</a>.</p>
499    
500    
501    </div><!-- for id="content", starts in the include above -->
502    <!--#include virtual="/server/footer.html" -->
503    <div id="footer">
504    <div class="unprintable">
505    
506    <p>Please send general FSF &amp; GNU inquiries to
507    <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
508    There are also <a href="/contact/">other ways to contact</a>
509    the FSF.  Broken links and other corrections or suggestions can be sent
510    to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
511    
512    <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
513            replace it with the translation of these two:
514    
515            We work hard and do our best to provide accurate, good quality
516            translations.  However, we are not exempt from imperfection.
517            Please send your comments and general suggestions in this regard
518            to <a href="mailto:web-translators@gnu.org">
519            &lt;web-translators@gnu.org&gt;</a>.</p>
520    
521            <p>For information on coordinating and submitting translations of
522            our web pages, see <a
523            href="/server/standards/README.translations.html">Translations
524            README</a>. -->
525    Please see the <a
526    href="/server/standards/README.translations.html">Translations
527    README</a> for information on coordinating and submitting translations
528    of this article.</p>
529    </div>
530    
531    <!-- Regarding copyright, in general, standalone pages (as opposed to
532         files generated as part of manuals) on the GNU web server should
533         be under CC BY-ND 3.0 US.  Please do NOT change or remove this
534         without talking with the webmasters or licensing team first.
535         Please make sure the copyright date is consistent with the
536         document.  For web pages, it is ok to list just the latest year the
537         document was modified, or published.
538        
539         If you wish to list earlier years, that is ok too.
540         Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
541         years, as long as each year in the range is in fact a copyrightable
542         year, i.e., a year in which the document was published (including
543         being publicly visible on the web or in a revision control system).
544        
545         There is more detail about copyright years in the GNU Maintainers
546         Information document, www.gnu.org/prep/maintain. -->
547    
548    <p>Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012, 2013
549    Free Software Foundation, Inc.</p>
550    
551    <p>This page is licensed under a <a rel="license"
552    href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
553    Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
554    
555    <!--#include virtual="/server/bottom-notes.html" -->
556    
557    <p class="unprintable">Updated:
558  <!-- timestamp start -->  <!-- timestamp start -->
559  $Date$ $Author$  $Date$
560  <!-- timestamp end -->  <!-- timestamp end -->
561  <HR>  </p>
562  </BODY>  </div>
563  </HTML>  </div>
564    </body>
565    </html>
Legend:
Removed from v.1.23  
changed lines
  Added in v.1.136
savannah-hackers-public@gnu.org
 ViewVC Help
Powered by ViewVC 1.1.26