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