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