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