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