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