[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/gnu-linux-faq.de.html gnu/thegnuproject...
|
From: |
GNUN |
|
Subject: |
www gnu/gnu-linux-faq.de.html gnu/thegnuproject... |
|
Date: |
Wed, 19 Sep 2012 00:30:21 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 12/09/19 00:30:21
Modified files:
gnu : gnu-linux-faq.de.html thegnuproject.ca.html
thegnuproject.cs.html thegnuproject.nl.html
gnu/po : gnu-linux-faq.de-en.html
help : help.de.html help.it.html help.pl.html
help.ru.html
help/po : help.de-en.html help.it-en.html help.it.po
help.pl-en.html help.ru-en.html help.ru.po
people : past-webmasters.de.html
people/po : past-webmasters.de-en.html
past-webmasters.de.po
philosophy : no-word-attachments.fr.html
philosophy/po : no-word-attachments.fr-en.html
server/standards: README.translations.de.html
server/standards/po: README.translations.de-en.html
Added files:
gnu/po : thegnuproject.ca-diff.html
thegnuproject.cs-diff.html
thegnuproject.nl-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/gnu-linux-faq.de.html?cvsroot=www&r1=1.29&r2=1.30
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.ca.html?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.cs.html?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.nl.html?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.de-en.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.ca-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.cs-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.nl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/help/help.de.html?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/help/help.it.html?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/help/help.pl.html?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/help/help.ru.html?cvsroot=www&r1=1.33&r2=1.34
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.de-en.html?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.it-en.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.it.po?cvsroot=www&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.pl-en.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.ru-en.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/help.ru.po?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/people/past-webmasters.de.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/people/po/past-webmasters.de-en.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/people/po/past-webmasters.de.po?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/no-word-attachments.fr.html?cvsroot=www&r1=1.47&r2=1.48
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/no-word-attachments.fr-en.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.translations.de.html?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.de-en.html?cvsroot=www&r1=1.13&r2=1.14
Patches:
Index: gnu/gnu-linux-faq.de.html
===================================================================
RCS file: /web/www/www/gnu/gnu-linux-faq.de.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- gnu/gnu-linux-faq.de.html 17 Sep 2012 16:27:35 -0000 1.29
+++ gnu/gnu-linux-faq.de.html 19 Sep 2012 00:27:57 -0000 1.30
@@ -134,7 +134,7 @@
<li><a href="#linuxgnu" id="TOClinuxgnu">Warum heiÃt es nicht einfach
<em>‚Linux ist der GNU-Betriebssystemkern‘</em> und eine
-vorhandene Version von GNU/Linux unter dem Namen <em>GNU</em>
+vorhandene Version von GNU/Linux wird unter dem Namen <em>GNU</em>
veröffentlicht?</a></li>
<li><a href="#condemn" id="TOCcondemn">Hat das GNU-Projekt den Einsatz von
Linux
@@ -442,7 +442,7 @@
Es ist sinnvoll, einen häufig verwendeten Namen abzukürzen, aber nicht, wenn
die Abkürzung irreführend ist.
<p>
-Fast jeder in den entwickelten Länder weià wirklich, dass das
+Fast jeder in den entwickelten Ländern weià wirklich, dass das
<em>Windows</em>-System von Microsoft erstellt wurde. Die Abkürzung von
<em>Microsoft Windows</em> mit <em>Windows</em> führt also niemanden
hinsichtlich Natur und Ursprungs in die Irre. <strong>GNU/Linux</strong>
@@ -681,10 +681,10 @@
href="#others">#others</a>)</span></dt>
<dd>
-Tausende Projekte haben Programme, die in weithin in heutigen
-GNU/Linux-Systemen enthalten sind,entwickelt. Alle verdienen Anerkennung für
-ihre Beiträge, aber sie sind nicht die Hauptentwickler des Systems als
-Ganzes, sodass sie nicht bitten als solche anerkannt zu werden.
+Tausende Projekte haben Programme entwickelt, die in heutigen
+GNU/Linux-Systemen enthalten sind. Alle verdienen Anerkennung für ihre
+Beiträge, aber sie sind nicht die Hauptentwickler des Systems als Ganzes,
+sodass sie nicht bitten als solche anerkannt zu werden.
<p>
GNU ist anders, weil es mehr als nur ein beigetragenes Programm ist, mehr
als nur eine Sammlung beigetragener Programme. GNU ist der Rahmen, worauf
@@ -697,8 +697,8 @@
<dd>
Im Jahr 2008 stellten wir fest, dass GNU-Pakete 15 % des offiziellen
Projektarchivs (<em>main</em>) der gNewSense GNU/Linux-Distribution
-ausmachten. Linux machte 1,5 % aus. Also würde dasselbe Argument noch
-stärker dafür gelten, es <ins>nicht</ins> <em>Linux</em> zu nennen.
+ausmachten. Linux machte 1,5 % aus. Folglich würde dasselbe Argument
+noch viel stärker auf die Benennung von <em>Linux</em> zutreffen.
<p>
GNU ist heutzutage ein kleiner Bruchteil des Systems, und Linux ist ein noch
@@ -734,11 +734,11 @@
href="#whyslash">#whyslash</a>)</span></dt>
<dd>
-Nach den Regeln der englischen Sprache wird in der Konstruktion <em>GNU
-Linux</em> das Wort <em>Linux</em> durch <em>GNU</em> modifiziert. Dies kann
-entweder <em>GNUs Version von Linux</em> oder <em>Linux, welches ein
-GNU-Paket ist</em> bedeuten. Keine dieser Bedeutungen passt zur vorhandenen
-Situation.
+Nach den Regeln der englischen Sprache wird in der Konstruktion
+<em>‚GNU Linux‘</em> das Wort <em>Linux</em> durch <em>GNU</em>
+modifiziert. Dies kann entweder <em>GNUs Version von Linux</em> oder
+<em>Linux, welches ein GNU-Paket ist</em> bedeuten. Keine dieser Bedeutungen
+passt zur vorhandenen Situation.
<p>
Linux ist kein GNU-Paket; das heiÃt, dass es nicht unter Leitung des
GNU-Projekts entwickelt oder speziell zum GNU-Projekt beigesteuert worden
@@ -749,11 +749,11 @@
Wir reden hier nicht von einer eigenständigen GNU-Version von Linux, dem
Betriebssystemkern. Die freien GNU/Linux-Distributionen haben eine <a
href="http://directory.fsf.org/project/linux";>separate Version von
-Linux</a>, seitdem die <em>Standard</em>-Version unfreie Firmware <em>groÃer
-binärer Objekte</em> (<span xml:lang="en" lang="en" title="Binary Large
+Linux</a>, seitdem die <em>Standard</em>-Version unfreie Firmware <em>groÃe
+binäre Objekte</em> (<span xml:lang="en" lang="en" title="Binary Large
Objects">BLOBs</span>) enthält. Wäre Linux Teil des GNU-Projekts, könnte es
-als <em>GNU Linux</em> betrachtet werden; aber wir würden es nicht so
-nennen wollen, weil es zu verwirrend wäre.</p>
+als <em>#8218;GNU Linux#8216;</em> betrachtet werden; aber wir würden
+es nicht so nennen wollen, weil es zu verwirrend wäre.</p>
<p>
Wir reden über eine Version von GNU, das Betriebssystem, bei der sich Linux
als Betriebssystemkern auszeichnet. Ein Schrägstrich liegt auf der Hand,
@@ -772,8 +772,8 @@
<dd>
Es ist richtig und angemessen, den Hauptbeitrag zuerst zu erwähnen. Der
-Beitrag von GNU zum System ist nicht nur gröÃer als Linux und war vor Linux,
-wir begannen tatsächlich mit der ganzen Aktivität.
+Beitrag von GNU zum System ist nicht nur gröÃer als Linux und war bevor
+Linux, wir begannen tatsächlich mit der gesamten Aktivität.
<p>
Aber wenn Sie bevorzugen, das System <em>Linux/GNU</em> zu nennen, ist das
viel besser als das, was viele üblicherweise tun, nämlich GNU vollständig
@@ -785,7 +785,7 @@
class="anchor-reference-id">(<a
href="#distronames">#distronames</a>)</span></dt>
<dd>
-<p>Es bedeutet, dass die Leute, die die <em>Foobar Linux</em>-Distribution
+<p>Es bedeutet, dass die Leute, die die <em>Fubar Linux</em>-Distribution
anbieten, den häufig gemachten Fehler wiederholen. Wir wissen es zu
schätzen, dass Distributionen wie Debian, Dragora, Musix, Trisquel und
Venenux GNU/Linux als Bestandteil ihres offiziellen Namens übernommen haben,
@@ -870,7 +870,7 @@
dieser Gruppe für eine Ãnderung ihrer Ausrichtung (und ihres Namens)
einzusetzen oder eine neue Gruppe zu gründen. Die Leute, die sich auf die
oberflächlicheren Ziele konzentrieren, haben ein Recht auf ihre Ansichten,
-aber lass sie dich nicht mitreiÃen!</p>
+aber lassen Sie sich nicht mitreiÃen!</p>
</dd>
<dt id="gnudist">Warum wird keine GNU-Distribution von Linux [sic] hergestellt
und diese dann
@@ -895,16 +895,16 @@
GNU/Linux-Distributionen wie gNewSense und Ututo.</p>
</dd>
-<dt id="linuxgnu">Warum heiÃt es nicht einfach <em>Linux ist der
GNU-Betriebssystemkern </em>
-und eine vorhandene Version von GNU/Linux unter dem Namen <em>GNU</em>
-veröffentlicht? <span class="anchor-reference-id">(<a
-href="#linuxgnu">#linuxgnu</a>)</span></dt>
+<dt id="linuxgnu">Warum heiÃt es nicht einfach <em>‚Linux ist der
+GNU-Betriebssystemkern‘</em> und eine vorhandene Version von GNU/Linux
+wird unter dem Namen <em>GNU</em> veröffentlicht? <span
+class="anchor-reference-id">(<a href="#linuxgnu">#linuxgnu</a>)</span></dt>
<dd>
Es könnte eine gute Idee gewesen sein, Linux als GNU-Betriebssystemkern
-anzunehmen. Hätten wir damals realisiert wie lange es dauern würde, den GNU
-Hurd zum Laufen zu bringen, dann hätten wir das tun können (leider ist das
-nachträgliche Einsicht).
+anzunehmen. Hätten wir damals realisiert wie lange es dauern würde, den
+GNU Hurd zum Laufen zu bringen, dann hätten wir das tun können (leider
+ist das nachträgliche Einsicht).
<p>
Wenn wir eine vorhandene Version von GNU/Linux nehmen und als <em>GNU</em>
bezeichnen würden, wäre das ein wenig wie eine Version des GNU-Systems
@@ -1020,13 +1020,13 @@
eine humorvolle Art der Danksagung an Unix und folgt einer Hackertradition
von rekursiven Akronymen, die in den 70ern begannen.</p>
<p>
-Das erste derartiger rekursiven Akronyme war TINT, <span xml:lang="en"
-lang="en"><em>TINT Is Not TECO</em></span> ‚TINT Ist Nicht
-TECO‘. Der Autor von TINT schrieb eine andere Implementierung von TECO
-(es gab bereits viele für verschiedene Systeme). Aber anstatt es mit einem
-langweiligen Namen wie <em>etwas-oder-anderes TECO</em> zu bezeichnen,
-dachte er an einen cleveren amüsanten Namen (genau das, was Hacken bedeutet:
-<a href="http://stallman.org/articles/on-hacking.html";>spielerische
+Das erste derartige rekursive Akronym war <abbr title="TINT Is Not TECO"
+xml:lang="en" lang="en">TINT</abbr> (‚TINT Ist Nicht TECO‘). Der
+Autor von TINT schrieb eine andere Implementierung von TECO (es gab bereits
+viele für verschiedene Systeme). Aber anstatt es mit einem langweiligen
+Namen wie <em>etwas-oder-anderes TECO</em> zu bezeichnen, dachte er an einen
+cleveren amüsanten Namen (genau das, was Hacken bedeutet: <a
+href="http://stallman.org/articles/on-hacking.html";>spielerische
Klugheit</a>).</p>
<p>
Anderen Hackern hatte dieser Name so sehr gefallen, dass wir den Ansatz
@@ -1116,14 +1116,15 @@
Beispiel. Aber es ist ein Fehler, sie <em>‚Linux‘</em>-Systeme
zu nennen.
<p>
-Android unterscheidet sich sehr vom GNU/Linux-System, weil es sehr wenig vom
-GNU-System enthält, nur Linux. Insgesamt ist es ein anderes System. Wenn Sie
-das Gesamtsystem <em>‚Linux‘</em> nennen, werden Sie es für
-notwendig erachten, Dinge zu sagen wie: „Android enthält Linux, aber
-es nicht Linux, weil es nicht die üblichen Linux [sic]-Bibliotheken und
--Dienstprogramme [d. h. das GNU-System] enthält.“ Android enthält
-ebensoviel von Linux wie GNU/Linux. Was es nicht enthält, ist das
-GNU-System. Stattdessen eine Menge Software von Google.</p>
+Android unterscheidet sich sehr vom GNU/Linux-System ‑ weil
+es sehr wenig vom GNU-System enthält, nur Linux. Insgesamt ist es ein
+anderes System. Wenn Sie das Gesamtsystem <em>‚Linux‘</em>
+nennen, werden Sie es für notwendig erachten, Dinge zu sagen wie:
+„Android enthält Linux, aber es nicht Linux, weil es nicht die
+üblichen Linux [sic]-Bibliotheken und -Dienstprogramme [d. h. das
+GNU-System] enthält.“ Android enthält ebensoviel von Linux wie
+GNU/Linux. Was es nicht enthält, ist das GNU-System. Stattdessen eine Menge
+Software von Google.</p>
</dd>
<dt id="helplinus">Warum wird das System nicht einfach
<em>‚Linux/GNU‘</em> genannt
@@ -1134,7 +1135,7 @@
<dd>
Linus Torvalds ist das <em>Aushängeschild</em> (das ist die Wortwahl anderer
Menschen, nicht unsere) für seine Ziele, nicht unserer. Sein Ziel ist es,
-das System populärer zu machen und glaubt, dass dessen Wert für die
+das System populärer zu machen und zu glauben, dass dessen Wert für die
Gesellschaft lediglich in den praktischen Vorteilen liegt, die es bietet:
seiner Leistung, Verlässlichkeit und einfacher Verfügbarkeit. Er hat nie
Freiheit als ein ethisches Prinzip zur Zusammenarbeit befürwortet, weshalb
@@ -1199,7 +1200,7 @@
nennt ist keine in einem Augenblick von der <em>Gesellschaft</em> vorgenomme
einzelne Entscheidung: jede Person, jede Organisation kann entscheiden,
welcher Name benutzt wird. Man kann anderen nicht vorschreiben
-<strong>GNU/Linux</strong>> zu sagen, aber man kann für sich selbst
+<strong>GNU/Linux</strong> zu sagen, aber man kann für sich selbst
beschlieÃen, das System <strong>GNU/Linux</strong> zu
nennen ‑ und dadurch helfen, andere zu informieren.
</dd>
@@ -1254,7 +1255,7 @@
<dd>
Das System <em>‚Linux‘</em> zu nennen, vermittelt tendenziell
-ein falsches Bild von der Geschichte und dem Grund für die Existenz des
+ein falsches Bild der Geschichte und dem Grund für die Existenz des
Systems. Leute, die über unsere Bitte womöglich lachen, haben sich dieses
falsche Bild angeeignet ‑ sie denken, unsere Arbeit von
Linus gemacht wurde, also lachen sie, wenn wir um Anerkennung bitten. Hätten
@@ -1333,7 +1334,7 @@
wie unfreie Software mit dem GNU/Linux-System bündeln oder sogar dafür
entwickeln, der bloÃe Akt hingegen, das System <em>‚Linux‘</em>
zu nennen, spricht den Nutzern an sich nicht ihre Freiheit ab. Welchen Namen
-man für das System verwenden kann, erscheint die Beschränkung der GPL
+man für das System verwenden kann, scheint eine Beschränkung der GPL
unpassend zu sein.
</dd>
@@ -1360,8 +1361,8 @@
berechtigt sind, einen so viel wie Sie mögen auszunutzen. Mit anderen
Worten, es wird davon ausgegangen, dass Macht vor Recht geht.
<p>
-Wir hoffen, dass Sie mit dieser Prämisse genauso wie wir nicht einverstanden
-sind.</p>
+Wir hoffen, dass Sie mit dieser Prämisse ‑ genauso wie
+wir ‑ nicht einverstanden sind.</p>
</dd>
<dt id="contradict">Wäre es nicht besser dem nicht zu widersprechen, was so
viele glauben? <span
@@ -1470,7 +1471,7 @@
<p><!-- timestamp start -->
Aktualisierung:
-$Date: 2012/09/17 16:27:35 $
+$Date: 2012/09/19 00:27:57 $
<!-- timestamp end -->
</p>
Index: gnu/thegnuproject.ca.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.ca.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- gnu/thegnuproject.ca.html 16 Sep 2012 05:22:19 -0000 1.22
+++ gnu/thegnuproject.ca.html 19 Sep 2012 00:27:58 -0000 1.23
@@ -10,6 +10,13 @@
Història" />
<!--#include virtual="/server/banner.ca.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/gnu/po/thegnuproject.ca.po";>
+ http://www.gnu.org/gnu/po/thegnuproject.ca.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/gnu/thegnuproject.html" -->
+ <!--#set var="DIFF_FILE" value="/gnu/po/thegnuproject.ca-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-07-20" -->
+ <!--#include virtual="/server/outdated.ca.html" -->
<!--#include virtual="/gnu/po/thegnuproject.translist" -->
<h2>El Projecte GNU</h2>
@@ -1046,7 +1053,7 @@
<!-- timestamp start -->
Updated:
-$Date: 2012/09/16 05:22:19 $
+$Date: 2012/09/19 00:27:58 $
<!-- timestamp end -->
</p>
Index: gnu/thegnuproject.cs.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.cs.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnu/thegnuproject.cs.html 16 Sep 2012 05:22:19 -0000 1.14
+++ gnu/thegnuproject.cs.html 19 Sep 2012 00:27:58 -0000 1.15
@@ -8,6 +8,13 @@
<meta http-equiv="Keywords" content="GNU, GNU projekt, FSF, Free Software,
Nadace pro svobodný software, historie" />
<!--#include virtual="/server/banner.cs.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/gnu/po/thegnuproject.cs.po";>
+ http://www.gnu.org/gnu/po/thegnuproject.cs.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/gnu/thegnuproject.html" -->
+ <!--#set var="DIFF_FILE" value="/gnu/po/thegnuproject.cs-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-07-20" -->
+ <!--#include virtual="/server/outdated.cs.html" -->
<!--#include virtual="/gnu/po/thegnuproject.translist" -->
<h2>Projekt GNU</h2>
@@ -987,7 +994,7 @@
<!-- timestamp start -->
Aktualizováno:
-$Date: 2012/09/16 05:22:19 $
+$Date: 2012/09/19 00:27:58 $
<!-- timestamp end -->
</p>
Index: gnu/thegnuproject.nl.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.nl.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- gnu/thegnuproject.nl.html 16 Sep 2012 05:22:19 -0000 1.13
+++ gnu/thegnuproject.nl.html 19 Sep 2012 00:27:58 -0000 1.14
@@ -8,6 +8,13 @@
<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software,
Free Software Foundation, Geschiedenis" />
<!--#include virtual="/server/banner.nl.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/gnu/po/thegnuproject.nl.po";>
+ http://www.gnu.org/gnu/po/thegnuproject.nl.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/gnu/thegnuproject.html" -->
+ <!--#set var="DIFF_FILE" value="/gnu/po/thegnuproject.nl-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-07-20" -->
+ <!--#include virtual="/server/outdated.nl.html" -->
<!--#include virtual="/gnu/po/thegnuproject.translist" -->
<h2>Het GNU Project</h2>
@@ -1060,7 +1067,7 @@
<!-- timestamp start -->
Bijgewerkt:
-$Date: 2012/09/16 05:22:19 $
+$Date: 2012/09/19 00:27:58 $
<!-- timestamp end -->
</p>
Index: gnu/po/gnu-linux-faq.de-en.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.de-en.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gnu/po/gnu-linux-faq.de-en.html 17 Sep 2012 16:27:48 -0000 1.16
+++ gnu/po/gnu-linux-faq.de-en.html 19 Sep 2012 00:28:09 -0000 1.17
@@ -1352,7 +1352,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/09/17 16:27:48 $
+$Date: 2012/09/19 00:28:09 $
<!-- timestamp end -->
</p>
</div>
Index: help/help.de.html
===================================================================
RCS file: /web/www/www/help/help.de.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- help/help.de.html 16 Sep 2012 09:18:39 -0000 1.22
+++ help/help.de.html 19 Sep 2012 00:28:25 -0000 1.23
@@ -1,27 +1,27 @@
<!--#include virtual="/server/header.de.html" -->
+<!-- Parent-Version: 1.69 -->
<!-- This file is automatically generated by GNUnited Nations! -->
-<title>Wie Sie dem GNU-Projekt helfen können - GNU-Projekt - Free Software
+<title>Wie man dem GNU-Betriebssystem helfen kann - GNU-Projekt - Free Software
Foundation</title>
<!--#include virtual="/server/banner.de.html" -->
<!--#include virtual="/help/po/help.translist" -->
-<h2>Wie Sie dem GNU-Projekt helfen können</h2>
+<h2>Wie man dem GNU-Betriebssystem helfen kann</h2>
<p>Die <span xml:lang="en" lang="en">GNU Volunteer Coordinators</span> <a
-href="mailto:address@hidden";><address@hidden></a> können Ihnen helfen,
wenn
-Sie zum GNU-Projekt beitragen möchten und können den Kontakt mit anderen
-Menschen herstellen, die ebenfalls interessiert oder an ähnlichen Projekten
-arbeiten.<!--When you have selected a task from our task lists, please let
-them know you're interested in working on it.--></p>
-
-<p>Informieren Sie bitte die <span xml:lang="en" lang="en">GNU Volunteer
-Coordinators</span><!-- <a
-href="mailto:address@hidden";><address@hidden></a>-->, wenn Sie eine
Aufgabe
-betreuen möchten, damit wir wissen, welche Aufgaben von Freiwilligen
-übernommen wurden.</p>
+href="mailto:address@hidden";><address@hidden></a>, GNUs ehrenamtliche
+Koordinatoren, unterstützen Sie, wenn Sie zum GNU-Projekt beitragen möchten
+und können ebenso den Kontakt zu anderen Menschen herstellen, die in oder an
+vergleichbaren Projekten arbeiten.<!--When you have selected a task from our
+task lists, please let them know you're interested in working on it.--></p>
+
+<p>Informieren Sie bitte unsere ehrenamtlichen Koordinatoren<!-- <a
+href="mailto:address@hidden";><address@hidden></a>-->, wenn Sie sich einer
+Aufgabe annehmen möchten, damit wir einen Ãberblick haben, welche Aufgaben
+von Ehrenamtlichen übernommen wurden.</p>
<p>Allgemeine Fragen zum GNU-Projekt können an <a
href="mailto:address@hidden";><address@hidden></a> gesendet werden, Fragen
@@ -36,110 +36,109 @@
</p>
<ul>
<li><a href="http://savannah.gnu.org";>Savannah</a>. Wir suchen vor allem
-Freiwillige als technische Systemverwalter, die bei der Unterstützung der
-zugrundeliegenden Infrastruktur helfen können. Freiwillige, die bei
-anhängigen Projekteinreichungen unterstützen können, sind ebenfalls sehr
-willkommen. Bitte beachten Sie die allgemeinen Informationen, <a
-href="http://savannah.gnu.org/maintenance/HowToBecomeASavannahHacker";>Wie
-man Savannah-Hacker wird</a>. Bitte kontaktieren Sie uns unter <a
+ehrenamtliche technische Systemverwalter für die zugrundeliegende
+Infrastruktur. Ehrenamtliche, die bei anhängigen Projekteinreichungenen
+helfen können, sind ebenfalls sehr willkommen. Siehe bitte <a
+href="http://savannah.gnu.org/maintenance/HowToBecomeASavannahHacker";
+title="How to become a Savannah Hacker">Wie man ein Savannah-Hacker wird</a>
+für weitere Informationen. Bitte kontaktieren Sie uns unter <a
href="http://lists.gnu.org/mailman/listinfo/savannah-hackers-public";>Savannah-Hackers-Public</a>.</li>
<li>Neue <a
href="http://libreplanet.org/wiki/Group_list";>GNU/Linux-Benutzergruppe</a>
-koordinieren.</li>
+aufbauen.</li>
- <li>Eine neue Freie-Software-Aktivisten-Benutzergruppe koordinieren, um die
-Nutzung von Freie Software in Ihrem Bundesland, Region oder Stadt zu
-fördern.</li>
-
- <li>Gehen Sie mit gutem Beispiel voran und steigen auf ein Betriebssystem
um,
-dass <em>vollständig</em> <a href="/software/software">Freie Software</a>
-ist. Der einfachste Weg ist die Installation und Nutzung von <a
+ <li>Eine neue Freie-Software-Aktivisten-Benutzergruppe aufbauen, um die
Nutzung
+von freier Software in Ihrem Bundesland, Region oder Stadt zu fördern.</li>
+
+ <li>Mit gutem Beispiel voran gehen und auf ein Betriebssystem umsteigen,
dass
+<em>völlig </em> <a href="/software/software">Freie Software</a> ist. Der
+einfachste Weg ist die Installation und Nutzung von <a
href="/distros/free-distros">Freie GNU/Linux-Distributionen</a>.</li>
<li>Freie Software schreiben:
<ul>
- <li><a href="http://www.fsf.org/campaigns/priority.html";>Projekten mit
hoher
+ <li><a href="http://www.fsf.org/campaigns/priority.html";>Projekte mit
hoher
Priorität</a>;</li>
<li><a href="/server/takeaction.html#python_configure">GNU für
Python-Pakete
konfigurieren</a>;</li>
- <li><a href="http://savannah.gnu.org/people/?type_id=1";>GNU-Projekte
auf
-Savannah</a>, allgemeine Aufgaben für GNU-Pakete. Vielleicht möchten Sie
-auch ein <a href="/server/takeaction.html#unmaint">unbetreutes GNU-Paket als
-ProjektbetreuerIn übernehmen</a>.</li>
+ <li><a href="http://savannah.gnu.org/people/?type_id=1";>GNU-Projekte,
die Hilfe
+suchen</a>. Allgemeine Aufgaben für GNU-Softwarepakete. Vielleicht möchten
+Sie auch ein <a href="/server/takeaction.html#unmaint">unbetreutes GNU-Paket
+als ProjektbetreuerIn übernehmen</a>.</li>
<li>Bitte beachten Sie die <a href="/prep/standards/" xml:lang="en"
lang="en">GNU Coding Standards</a> und <a href="/prep/maintain/"
xml:lang="en" lang="en">Information for Maintainers of GNU Software</a>,
-wenn Sie Software für GNU schreiben.</li>
+wenn Sie Software für GNU schreiben;</li>
<li>Unter <a href="/help/evaluation">GNU-Softwareevaluierung</a>
finden Sie
weitere Informationen, wenn Sie für GNU Software geschrieben haben und
-anbieten möchten.</li>
+bereitstellen möchten.</li>
<li>Manchmal wird Software angeboten, die bereits im Wesentlichen die
gleiche
-Aufgabe wie eines bereits vorhandenen GNU-Pakets erledigt. Obwohl wir
+Aufgabe wie die eines bereits vorhandenen GNU-Pakets erledigt. Obwohl wir
natürlich alle Angebote zu schätzen wissen, möchten wir ProgrammiererInnen
-natürlich gerne ermutigen, ihre Zeit mit dem Schreiben von Freie Software zu
-verbringen, um neue Aufgaben zu lösen, nicht bereits gelöste. Bevor Sie also
-mit einem neuen Programm starten, überprüfen Sie bitte das <a
-href="http://directory.fsf.org/";>Freie-Software-Verzeichnis</a> auf Freie
-Software, die diese Aufgabe bereits löst.</li>
+natürlich gerne ermutigen, ihre Zeit mit dem Schreiben von freier Software
+zu verbringen, um neue Aufgaben zu lösen, nicht bereits gelöste. Bevor Sie
+also mit einem neuen Programm starten, überprüfen Sie bitte das <a
+href="/directory/">Freie-Software-Verzeichnis</a> auf Freie Software, die
+diese Aufgabe bereits löst.</li>
<li>Wir bieten einige <a href="/software/devel">Ressourcen für die
-Entwicklung</a>, um GNU-Softwareentwicklern zu helfen.
+Entwicklung</a> an, um GNUs Softwareentwicklern zu helfen.
</li>
</ul></li>
<li id="documentation">Dokumentation für GNU-Software schreiben.</li>
- <li>Als Freiwillige/r <em>Freedom Verifier</em>, um eine bestimmte
Distribution
-auf ausschlieÃlich Freie Software zu überprüfen, damit sie den <a
+ <li>Als ehrenamtliche/r <span xml:lang="en" lang="en"><em>Freedom
+Verifier</em></span>, um eine bestimmte Distribution auf ausschlieÃlich
+Freie Software zu überprüfen, damit sie den <a
href="/distros/free-distros">Freie GNU/Linux-Distributionen</a> hinzugefügt
werden kann.</li>
- <li>Als Freiwillige/r GNU Webmaster (siehe <a
-href="/server/standards/webmaster-quiz">Fragen für freiwillige GNU
-Webmaster</a>).</li>
+ <li>Als ehrenamtliche/r GNU-Webmaster (siehe <a
+href="/server/standards/webmaster-quiz">Fragen für ehrenamtliche
+GNU-Webmaster</a>).</li>
<li id="helptranslations">Ãbersetzen Sie GNUs Webseiten in andere
Sprachen. Weitere Informationen zum
Thema finden Sie unter <a
href="/server/standards/README.translations">Leitfaden für die Ãbersetzung
von www.gnu.org-Webseiten</a>. Senden Sie eine Nachricht an <a
-href="mailto:address@hidden";><address@hidden></a>,
+href="mailto:address@hidden@gnu.org";><address@hidden></a>,
wenn Sie helfen möchten.</li>
- <li>Freunde und Bekannte über das GNU-Projekt und der Free Software
Foundation
-informieren:
+ <li>Andere über das GNU-Projekt und die <span xml:lang="en" lang="en">Free
+Software Foundation</span> informieren:
<ul>
- <li>die <a href="/philosophy/philosophy">Philosophie</a> und <a
+ <li>über die <a href="/philosophy/philosophy">Philosophie</a> und <a
href="/software/software">Software</a> von GNU;</li>
- <li>das das „Linux“-Betriebssystem tatsächlich <a
+ <li>dass das <em>‚Linux‘</em>-Betriebssystem tatsächlich
<a
href="/gnu/linux-and-gnu"><strong>GNU/Linux</strong></a> ist: also das
-GNU-Betriebssystem mit Linux, dem Betriebssystemkern [um Hardware
-anzusprechen, A. d. Ã.]. Unterscheiden Sie einfach konsistent und unfehlbar
-zwischen GNU/Linux (dem Gesamtsystem) und Linux (dem Betriebssystemkern),
-wenn Sie über das System schreiben oder sprechen (siehe auch <a
-href="/gnu/why-gnu-linux">GNU/Linux. Ist der Name Schall und Rauch?</a>);
-das hilft GNU sehr und beansprucht nur sehr wenig Zeit, bis eine alte
-Gewohnheit vergessen ist;</li>
-
- <li>einen <a href="/help/linking-gnu">Verweis zur GNU-Startseite</a>
von Ihren
-Webseiten hinzufügen und anderen empfehlen, ebenfalls einen Verweis
-anzubringen.</li>
+GNU-System zuzüglich Linux, dem Betriebssystemkern. Unterscheiden Sie
+einfach konsistent und unfehlbar zwischen GNU/Linux (dem Gesamtsystem) und
+Linux (dem Betriebssystemkern), wenn Sie über das System schreiben oder
+sprechen (siehe auch <a href="/gnu/why-gnu-linux">GNU/Linux. Ist der Name
+Schall und Rauch?</a>); das hilft GNU sehr und beansprucht nur sehr wenig
+Zeit, bis eine alte Gewohnheit vergessen ist;</li>
+
+ <li>sowohl durch das <a href="/help/linking-gnu">Hinzufügen eines
Verweises zur
+Startseite GNUs</a> auf Ihren Webseiten als auch durch anderen zu empfehlen,
+ebenfalls einen Verweis anzulegen.</li>
</ul></li>
- <li>Wenn Sie mit Menschen sprechen, die Freiheit und Gemeinschaft nicht
-einordnen können, können Sie ihnen die vielen praktischen Vorteile von Freie
-Software aufzeigen (siehe auch <a
-href="http://www.dwheeler.com/oss_fs_why.html"; xml:lang="en" lang="en">Why
-Open Source/Free Software? Look at the Numbers!</a> für weitere
-Hinweise). Aber erwähnen Sie auch die ethischen Fragen! Ãndern Sie nicht
-Ihre Ausdrucksweise als Open-Source-Sprachrohr, nur um anderen gerecht zu
-werden.</li>
+ <li>Wenn Sie mit Menschen sprechen, die den Wert von Freiheit und
Gemeinschaft
+nicht einordnen können, können Sie ihnen die vielen praktischen Vorteile von
+freier Software aufzeigen (siehe auch Wheeler, David A: <a
+href="http://www.dwheeler.com/oss_fs_why.html"; xml:lang="en"
+lang="en"><cite>Why Open Source Software/Free Software? Look at the
+Numbers!</cite></a> (2007) für weitere Hinweise). Aber erwähnen Sie auch die
+ethischen Fragen! Ãndern Sie Ihre Stimme nicht in ein
+Open-Source-Sprachrohr, nur um anderen gerecht zu werden.</li>
<li>Mithelfen, die Mittel der FSF zu erhöhen:
<ul>
@@ -171,13 +170,13 @@
<li>
<a href="/philosophy/selling">Freie Software verkaufen</a> und ein
Teil des
-Erlöses an die <a href="/fsf/fsf.html" xml:lang="en" lang="en">Free Software
+Erlöses an die <a href="/fsf/" xml:lang="en" lang="en">Free Software
Foundation</a> oder für die Entwicklung eines anderen
Freie-Software-Projekts spenden. So können Sie bereits im Voraus die Welt
der freien Software fördern.
<p>
- <strong>Der Vertrieb von Freie Software ist eine Möglichkeit, um die
Mittel
-für die Entwicklung zu erhöhen. Vergeuden Sie sie nicht!</strong>
+ <strong>Der Freie-Software-Vertrieb ist eine Möglichkeit, um die
Mittel für
+die Entwicklung zu erhöhen. Vergeuden Sie sie nicht!</strong>
</p></li>
</ul></li>
@@ -195,7 +194,7 @@
href="mailto:address@hidden";><address@hidden></a>.
</li>
- <li><a href="/help/help-hardware">Hardware</a>-Spenden an die FSF.</li>
+ <li><a href="/help/help-hardware">Hardware</a> an die FSF spenden.</li>
<li>Eine der <a href="/server/tasks">Aufgaben</a> übernehmen, die für
diesen <a
href="/server/server">Webserver</a> erledigt werden müssen.</li>
@@ -205,8 +204,8 @@
(bzw. das Unternehmen) im <a href="/prep/service.html"
hreflang="en">Dienstleistungsverzeichnis</a> eintragen.</li>
- <li>Stellt Ihr Unternehmen MitarbeiterInnen ein, um mit Freie Software zu
-arbeiten, können Sie unter <a
+ <li>Stellt Ihr Unternehmen MitarbeiterInnen ein, die mit freier Software
+arbeiten müssen, können Sie unter <a
href="http://www.fsf.org/resources/jobs/";>Freie Software-Jobs</a> eine
Anzeige aufgeben.</li>
@@ -218,23 +217,55 @@
</ul>
-
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
<div style="font-size: small;">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
</div>
</div>
+<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.de.html" -->
<div id="footer">
-<p>
-Bitte senden Sie Fragen zur FSF & GNU an <a
+
+<p>Bitte senden Sie Fragen zur FSF & GNU an <a
href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
-href="/contact/">Free Software Foundation kontaktieren</a>.
-<br />
-Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
-an <a href="mailto:address@hidden";><address@hidden></a>.
-</p>
+href="/contact/">Free Software Foundation kontaktieren</a>. Ungültige
+Verweise und andere Korrekturen oder Vorschläge können an <a
+href="mailto:address@hidden";><address@hidden></a> gesendet
+werden.</p>
+
+<p>
+
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu dieser Webseite haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für
Ãbersetzungen</a>.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
@@ -250,14 +281,14 @@
<div class="translators-credits">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
-<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011, 2012.</div>
<p>
<!-- timestamp start -->
Aktualisierung:
-$Date: 2012/09/16 09:18:39 $
+$Date: 2012/09/19 00:28:25 $
<!-- timestamp end -->
</p>
Index: help/help.it.html
===================================================================
RCS file: /web/www/www/help/help.it.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- help/help.it.html 16 Sep 2012 09:18:39 -0000 1.15
+++ help/help.it.html 19 Sep 2012 00:28:25 -0000 1.16
@@ -1,9 +1,10 @@
<!--#include virtual="/server/header.it.html" -->
+<!-- Parent-Version: 1.69 -->
<!-- This file is automatically generated by GNUnited Nations! -->
-<title>Come potete aiutare il Progetto GNU - Free Software Foundation
(FSF)</title>
+<title>Come potete aiutare il Progetto GNU - Free Software Foundation</title>
<!--#include virtual="/server/banner.it.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -213,24 +214,51 @@
</ul>
-
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
<div style="font-size: small;">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
</div>
</div>
+<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.it.html" -->
<div id="footer">
-<p>
-Per informazioni su FSF e GNU rivolgetevi, possibilmente in inglese, a <a
+
+<p>Per informazioni su FSF e GNU rivolgetevi, possibilmente in inglese, a <a
href="mailto:address@hidden";><address@hidden></a>. Ci sono anche <a
-href="/contact/">altri modi di contattare</a> la FSF.
-<br />
-Inviate segnalazioni di link non funzionanti e altri suggerimenti relativi
-alle pagine web a <a
-href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+href="/contact/">altri modi di contattare</a> la FSF. Inviate segnalazioni
+di link non funzionanti e altri suggerimenti relativi alle pagine web a <a
+href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p>
+
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Per informazioni su come tradurre questa pagina consultate la <a
+href="/server/standards/README.translations.html">Guida alle
+traduzioni</a>. Per segnalare errori di traduzione o collaborare alla
+traduzione italiana delle pagine di questo sito contattate il <a
+href="http://savannah.gnu.org/projects/www-it/";>gruppo dei traduttori
+italiani</a>.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
@@ -255,7 +283,7 @@
<!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2012/09/16 09:18:39 $
+$Date: 2012/09/19 00:28:25 $
<!-- timestamp end -->
</p>
Index: help/help.pl.html
===================================================================
RCS file: /web/www/www/help/help.pl.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- help/help.pl.html 16 Sep 2012 09:18:39 -0000 1.40
+++ help/help.pl.html 19 Sep 2012 00:28:25 -0000 1.41
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.pl.html" -->
+<!-- Parent-Version: 1.69 -->
<!-- This file is automatically generated by GNUnited Nations! -->
<title>Jak możecie pomóc Projektowi GNU - Projekt GNU - Fundacja Wolnego
@@ -219,24 +220,52 @@
</ul>
-
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
<div style="font-size: small;">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
</div>
</div>
+<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.pl.html" -->
<div id="footer">
-<p>
-Pytania dotyczÄ
ce GNU i FSF prosimy kierowaÄ na adres <a
+
+<p>Pytania dotyczÄ
ce GNU i FSF prosimy kierowaÄ na adres <a
href="mailto:address@hidden";><address@hidden></a>. IstniejÄ
także <a
-href="/contact/contact.html">inne sposoby skontaktowania siÄ</a> z FSF.
-<br />
-Informacje o niedziaÅajÄ
cych odnoÅnikach oraz inne poprawki (lub
-propozycje) prosimy wysyÅaÄ na adres <a
-href="mailto:address@hidden";><address@hidden></a>.
-</p>
+href="/contact/contact.html">inne sposoby skontaktowania siÄ</a>
+z FSF. <br /> Informacje o niedziaÅajÄ
cych odnoÅnikach oraz inne
+poprawki (lub propozycje) prosimy wysyÅaÄ na adres <a
+href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p>
+
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Aby zapoznaÄ siÄ z informacjami dotyczÄ
cymi tÅumaczenia
+i koordynowania tÅumaczeÅ artykuÅów, proszÄ odwiedziÄ stronÄ <a
+href="/server/standards/README.translations.html">tÅumaczeÅ</a>. <br />
+Komentarze odnoÅnie tÅumaczenia polskiego oraz zgÅoszenia dotyczÄ
ce
+chÄci wspóÅpracy w tÅumaczeniu prosimy kierowaÄ na adres <a
+href="mailto:address@hidden";>address@hidden</a></p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
@@ -260,7 +289,7 @@
<!-- timestamp start -->
Aktualizowane:
-$Date: 2012/09/16 09:18:39 $
+$Date: 2012/09/19 00:28:25 $
<!-- timestamp end -->
</p>
Index: help/help.ru.html
===================================================================
RCS file: /web/www/www/help/help.ru.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- help/help.ru.html 16 Sep 2012 09:18:40 -0000 1.33
+++ help/help.ru.html 19 Sep 2012 00:28:25 -0000 1.34
@@ -1,10 +1,11 @@
<!--#include virtual="/server/header.ru.html" -->
+<!-- Parent-Version: 1.69 -->
<!-- This file is automatically generated by GNUnited Nations! -->
<title>Ðак Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе помоÑÑ Ð¿ÑоекÑÑ GNU - ÐÑоекÑ
GNU - Фонд Ñвободного пÑогÑаммного
-обеÑпеÑÐµÐ½Ð¸Ñ (FSF)</title>
+обеÑпеÑениÑ</title>
<!--#include virtual="/server/banner.ru.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -14,13 +15,13 @@
href="mailto:address@hidden";><address@hidden></a> могÑÑ
поддеÑжаÑÑ Ð²Ð°Ñ, еÑли
Ð²Ñ Ð¶ÐµÐ»Ð°ÐµÑе помоÑÑ Ð¿ÑоекÑÑ GNU. ÐооÑдинаÑоÑÑ
помогÑÑ Ð²Ð°Ð¼ ÑвÑзаÑÑÑÑ Ñ Ð´ÑÑгими
лÑдÑми, ÑабоÑаÑÑими над ÑÑ
однÑми
пÑоекÑами. Ðогда Ð²Ñ Ð²ÑбеÑеÑе Ñебе задаÑÑ Ð¸Ð·
-наÑего ÑпиÑка, пожалÑйÑÑа, дайÑе знаÑÑ Ð¸Ð¼,
ÑÑо Ð²Ñ Ð·Ð°Ð¸Ð½ÑеÑеÑÐ¾Ð²Ð°Ð½Ñ Ð² ÑабоÑе
+наÑего ÑпиÑка, пожалÑйÑÑа, дайÑе им знаÑÑ,
ÑÑо Ð²Ñ Ð·Ð°Ð¸Ð½ÑеÑеÑÐ¾Ð²Ð°Ð½Ñ Ð² ÑабоÑе
над ней.</p>
<p>ÐожалÑйÑÑа, ÑообÑиÑе кооÑдинаÑоÑам
добÑоволÑÑев пÑоекÑа GNU <a
href="mailto:address@hidden";><address@hidden></a>, еÑли вÑ
беÑеÑеÑÑ Ð·Ð°
ÑеÑение лÑбой задаÑи из ÑÑого ÑпиÑка. ÐÑ Ñ
оÑим бÑÑÑ Ð² кÑÑÑе, над какими
-задаÑами ÑабоÑаÑÑ Ð½Ð°Ñи добÑоволÑнÑе
помоÑники.</p>
+задаÑами ÑабоÑаÑÑ Ð½Ð°Ñи добÑоволÑÑÑ.</p>
<p>С обÑими вопÑоÑами о пÑоекÑе GNU
обÑаÑайÑеÑÑ Ð¿Ð¾ адÑеÑÑ <a
href="mailto:address@hidden";><address@hidden></a>, а Ñ
вопÑоÑами и
@@ -30,17 +31,17 @@
<h3 id="helpgnu">Чем помоÑÑ Ð¿ÑоекÑÑ GNU</h3>
<p>
-ÐÑÐ¾Ñ ÑпиÑок ÑпоÑÑдоÑен Ñак, ÑÑо более
ÑÑоÑнÑе дела ÑаÑÐ¿Ð¾Ð»Ð¾Ð¶ÐµÐ½Ñ Ð±Ð»Ð¸Ð¶Ðµ к
-наÑалÑ. ÐожалÑйÑÑа, обÑаÑиÑе внимание, ÑÑо
многие пÑнкÑÑ ÑÑого пеÑеÑÐ½Ñ Ð¸Ð¼ÐµÑÑ
-ÑÑÑлки на более длиннÑе, ÑазвеÑнÑÑÑе
ÑпиÑки.
+ÐÑÐ¾Ñ ÑпиÑок ÑпоÑÑдоÑен пÑимеÑно Ñак, ÑÑо
более важнÑе дела ÑаÑÐ¿Ð¾Ð»Ð¾Ð¶ÐµÐ½Ñ Ð±Ð»Ð¸Ð¶Ðµ
+к наÑалÑ. ÐожалÑйÑÑа, обÑаÑиÑе внимание,
ÑÑо многие пÑнкÑÑ ÑÑого пеÑеÑнÑ
+имеÑÑ ÑÑÑлки на более длиннÑе, ÑазвеÑнÑÑÑе
ÑпиÑки.
</p>
<ul>
- <li>ÐомогиÑе ÑайÑÑ <a
href="http://savannah.gnu.org";>Savannah</a>. ÐÑ Ð¸Ñем
-ÑеÑ
ниÑеÑкиÑ
ÑпеÑиалиÑÑов Ð´Ð»Ñ Ð¿Ð¾Ð¼Ð¾Ñи по
поддеÑжке инÑÑаÑÑÑÑкÑÑÑÑ ÑайÑа. Также
-оÑÐµÐ½Ñ Ð¶ÐµÐ»Ð°ÑелÑна добÑоволÑÐ½Ð°Ñ Ð¿Ð¾Ð¼Ð¾ÑÑ Ð²
ÑегиÑÑÑаÑии пÑоекÑов. ÐожалÑйÑÑа,
-пÑоÑÑиÑе <a
+ <li>ÐомогиÑе Ñ ÑайÑом <a
href="http://savannah.gnu.org";>Savannah</a>. ÐÑ Ð¸Ñем
+ÑеÑ
ниÑеÑкиÑ
ÑпеÑиалиÑÑов Ð´Ð»Ñ Ð¿Ð¾Ð¼Ð¾Ñи по
поддеÑжке инÑÑаÑÑÑÑкÑÑÑÑ. Также оÑенÑ
+желаÑелÑна добÑоволÑÐ½Ð°Ñ Ð¿Ð¾Ð¼Ð¾ÑÑ Ð²
ÑегиÑÑÑаÑии пÑоекÑов. ÐожалÑйÑÑа, пÑоÑÑиÑе
+<a
href="http://savannah.gnu.org/maintenance/HowToBecomeASavannahHacker";>обÑие
-ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾ Ñом, как ÑÑаÑÑ Ð¿ÑогÑаммиÑÑом
пÑоекÑа Savannah</a>. ÐожалÑйÑÑа,
+ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾ Ñом, как ÑÑаÑÑ Ð¿ÑогÑаммиÑÑом
ÑайÑа Savannah</a>. ÐожалÑйÑÑа,
ÑвÑжиÑеÑÑ Ñ Ð½Ð°Ð¼Ð¸ в оÑкÑÑÑом ÑпиÑке
ÑаÑÑÑлки <a
href="http://lists.gnu.org/mailman/listinfo/savannah-hackers-public";>savannah-hackers-public</a>.</li>
@@ -71,10 +72,10 @@
могли Ð±Ñ Ñакже подÑмаÑÑ Ð¾ Ñом, ÑÑÐ¾Ð±Ñ Ð²Ð·ÑÑÑ
на ÑÐµÐ±Ñ Ð¾Ð´Ð¸Ð½ из пакеÑов GNU, <a
href="/server/takeaction.html#unmaint">оÑÑавÑиÑ
ÑÑ Ð±ÐµÐ·
поддеÑжки</a>.</li>
- <li>Ðогда пиÑеÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ GNU,
бÑдÑÑе лÑÐ±ÐµÐ·Ð½Ñ ÑледоваÑÑ Ð´Ð¾ÐºÑменÑам <a
-href="/prep/standards/">“СÑандаÑÑÑ
пÑогÑаммиÑÐ¾Ð²Ð°Ð½Ð¸Ñ GNU”</a> и
-<a href="/prep/maintain/">“Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ поддеÑжке
пÑогÑамм
-GNU”</a>.</li>
+ <li>Ðогда пиÑеÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ GNU,
ÑледÑйÑе, пожалÑйÑÑа, докÑменÑам “<a
+href="/prep/standards/">СÑандаÑÑÑ Ð¿ÑогÑаммиÑованиÑ
GNU</a>” и
+“<a href="/prep/maintain/">Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ поддеÑжке
пÑогÑамм
+GNU</a>”.</li>
<li>ЧÑÐ¾Ð±Ñ Ð¿ÑедложиÑÑ Ð½Ð°Ð¿Ð¸ÑаннÑÑ Ð²Ð°Ð¼Ð¸
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿ÑоекÑÑ GNU, ознакомÑÑеÑÑ,
пожалÑйÑÑа, Ñ ÑÑими ÑведениÑми по <a
href="/help/evaluation.html">оÑенке
@@ -84,7 +85,7 @@
как один из ÑÑÑеÑÑвÑÑÑиÑ
пакеÑов GNU. ХоÑÑ
мÑ, безÑÑловно, Ñеним вÑе
пÑедложениÑ, нам бÑ, еÑÑеÑÑвенно, Ñ
оÑелоÑÑ
пооÑÑÑÑÑ Ð¿ÑогÑаммиÑÑов ÑÑаÑиÑÑ
Ñвое вÑÐµÐ¼Ñ Ð½Ð° Ñоздание ÑвободнÑÑ
пÑогÑамм
Ð´Ð»Ñ ÑеÑÐµÐ½Ð¸Ñ Ð½Ð¾Ð²ÑÑ
задаÑ, а не Ñже
-ÑеÑеннÑÑ
. ÐоÑÑомÑ, пÑежде Ñем наÑаÑÑ Ð½Ð¾Ð²Ñй
пÑоекÑ, пожалÑйÑÑа, пÑовеÑÑÑе,
+ÑеÑеннÑÑ
. ÐоÑÑомÑ, пÑежде Ñем наÑаÑÑ Ð½Ð¾Ð²Ñй
пÑоекÑ, пÑовеÑÑÑе, пожалÑйÑÑа,
Ð½ÐµÑ Ð»Ð¸ в <a href="http://directory.fsf.org/";>ÐаÑалоге
ÑвободнÑÑ
пÑогÑамм</a>
пакеÑа, коÑоÑÑй Ñже Ð´ÐµÐ»Ð°ÐµÑ ÑÑÑ ÑабоÑÑ.</li>
@@ -98,17 +99,16 @@
<li>СÑанÑÑе “пÑовеÑÑÑÑим Ñвободє.
ÐозÑмиÑе диÑÑÑибÑÑив и
ÑдоÑÑовеÑÑÑеÑÑ, ÑÑо в нем ÑодеÑжиÑÑÑ
ÑолÑко Ñвободное пÑогÑаммное
обеÑпеÑение, ÑÑÐ¾Ð±Ñ ÐµÐ³Ð¾ можно бÑло добавиÑÑ
в <a
-href="/links/links.html#FreeGNULinuxDistributions">ÑпиÑок
ÑвободнÑÑ
-диÑÑÑибÑÑивов</a>.</li>
+href="/distros/free-distros.html">ÑпиÑок ÑвободнÑÑ
диÑÑÑибÑÑивов</a>.</li>
- <li>ÐомогиÑе Ñ Ð¿Ð¾Ð´Ð´ÐµÑжкой ÑайÑа GNU.ORG,
заполнив <a
+ <li>ÐомогиÑе Ñ Ð¿Ð¾Ð´Ð´ÐµÑжкой ÑайÑа GNU,
заполнив <a
href="http://www.gnu.org/server/standards/webmaster-quiz.html";>
ÑооÑвеÑÑÑвÑÑÑÑÑ Ð°Ð½ÐºÐµÑÑ</a>.</li>
<li id="helptranslations">ÐеÑеведиÑе ÑÑÑаниÑÑ ÑайÑа
GNU на дÑÑгие ÑзÑки. ÐополниÑелÑнÑе ÑведениÑ
-ÑмоÑÑиÑе в <a
-href="/server/standards/README.translations.html">“Ð
ÑководÑÑве по
-пеÑÐµÐ²Ð¾Ð´Ñ ÑайÑа www.gnu.org”</a>. ÐиÑиÑе по
адÑеÑÑ <a
+ÑмоÑÑиÑе в “<a
+href="/server/standards/README.translations.html">Ð ÑководÑÑве по
пеÑеводÑ
+ÑайÑа www.gnu.org</a>”. ÐиÑиÑе по адÑеÑÑ <a
href="mailto:address@hidden";><address@hidden></a>,
еÑли Ñ
оÑиÑе помоÑÑ.</li>
@@ -119,14 +119,14 @@
href="/philosophy/philosophy.html">ÑилоÑоÑии</a> и <a
href="/software/software.html">пÑогÑаммаÑ
</a> пÑоекÑа
GNU.</li>
- <li>обÑÑÑнÑÑ Ð´ÑÑзÑÑм, ÑÑо опеÑаÑионнÑÑ
ÑиÑÑÐµÐ¼Ñ “Linux” на Ñамом деле
-ÑледÑÐµÑ Ð½Ð°Ð·ÑваÑÑ <a
-href="/gnu/linux-and-gnu.html">“GNU/Linux”</a>, Ñ.е.
ÑиÑÑема GNU
-+ ÑдÑо Linux; пÑоÑÑо поÑледоваÑелÑно и
безоÑибоÑно подÑеÑÐºÐ¸Ð²Ð°Ñ ÑазлиÑиÑ
-Ð¼ÐµÐ¶Ð´Ñ GNU/Linux как ÑиÑÑемой в Ñелом и ÑдÑом
Linux, когда пиÑеÑе или
-говоÑиÑе об ÑÑой опеÑаÑионной ÑиÑÑеме, Ð²Ñ <a
-href="/gnu/why-gnu-linux.html">оÑÐµÐ½Ñ Ð½Ð°Ð¼ поможеÑе</a>. ÐÑо
бÑÐ´ÐµÑ Ð·Ð°Ð½Ð¸Ð¼Ð°ÑÑ
-ÑовÑем немного вÑемени, когда Ð²Ñ Ð¾ÑÑÑиÑеÑÑ
Ð¾Ñ ÑÑаÑой пÑивÑÑки.</li>
+ <li>обÑÑÑнÑÑ Ñвоим знакомÑм, ÑÑо
опеÑаÑÐ¸Ð¾Ð½Ð½Ð°Ñ ÑиÑÑема
+“Linux” — ÑÑо на Ñамом деле <a
+href="/gnu/linux-and-gnu.html">GNU/Linux</a>, Ñ.е. ÑиÑÑема GNU +
Linux,
+ÑдÑо; пÑоÑÑо поÑледоваÑелÑно и
безоÑибоÑно подÑеÑÐºÐ¸Ð²Ð°Ñ ÑазлиÑÐ¸Ñ Ð¼ÐµÐ¶Ð´Ñ
+GNU/Linux (ÑиÑÑемой в Ñелом) и Linux (ÑдÑом), когда
пиÑеÑе или говоÑиÑе об
+ÑÑой опеÑаÑионной ÑиÑÑеме, Ð²Ñ <a
href="/gnu/why-gnu-linux.html">оÑÐµÐ½Ñ Ð½Ð°Ð¼
+поможеÑе</a>. ÐÑо бÑÐ´ÐµÑ Ð·Ð°Ð½Ð¸Ð¼Ð°ÑÑ ÑовÑем
немного вÑемени, когда Ð²Ñ Ð¾ÑÑÑиÑеÑÑ
+Ð¾Ñ ÑÑаÑой пÑивÑÑки.</li>
<li><a href="/help/linking-gnu.html">добавив ÑÑÑÐ»ÐºÑ Ð½Ð°
ÑÐ°Ð¹Ñ GNU</a> к ваÑей
домаÑней ÑÑÑаниÑе и пÑедложив дÑÑгим
ÑделаÑÑ Ñо же Ñамое.</li>
@@ -134,9 +134,9 @@
<li>Ðогда Ð²Ñ Ð±ÐµÑедÑеÑе Ñ Ð»ÑдÑми, коÑоÑÑе
не ÑенÑÑ ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð¸ ÑообÑеÑÑво, вÑ
можеÑе ÑказаÑÑ Ð¸Ð¼ на многие пÑакÑиÑеÑкие
доÑÑоинÑÑва ÑвободнÑÑ
пÑогÑамм
-(Ñм. некоÑоÑÑе полезнÑе ÑвидеÑелÑÑÑва в
ÑÑаÑÑе <a
-href="http://www.dwheeler.com/oss_fs_why.html";>“Why Open Source / Free
-Software? Look at the Numbers!”</a>). Ðо непÑеменно
ÑпоминайÑе и об
+(Ñм. некоÑоÑÑе полезнÑе ÑвидеÑелÑÑÑва в
ÑÑаÑÑе “<a
+href="http://www.dwheeler.com/oss_fs_why.html";>Why Open Source / Free
+Software? Look at the Numbers!</a>”). Ðо непÑеменно
ÑпоминайÑе и об
ÑÑиÑеÑкиÑ
аÑпекÑаÑ
! Ðе вÑÑказÑвайÑеÑÑ Ð²
поддеÑÐ¶ÐºÑ Ð¾ÑкÑÑÑого иÑÑ
одного ÑекÑÑа
ÑолÑко Ñади Ñого, ÑÑÐ¾Ð±Ñ ÑгодиÑÑ ÐºÐ¾Ð¼Ñ-Ñо.</li>
@@ -152,7 +152,9 @@
<li>
вÑбÑав ФСÐРкак оÑганизаÑиÑ, коÑоÑой
бÑдÑÑ Ð¸Ð´Ñи оÑÑиÑÐ»ÐµÐ½Ð¸Ñ Ð¾Ñ Ð²Ð°Ñего лиÑа
-ÑеÑез ÑиÑÑÐµÐ¼Ñ <a href="http://www.affero.com/ca/fsf";>Affero</a>.
+ÑеÑез ÑиÑÑÐµÐ¼Ñ <a href="http://www.affero.com/ca/fsf";>Affero</a>,
ÑÑÑлаÑÑÑ Ð½Ð°
+ÑÐ²Ð¾Ñ ÑÑÑаниÑÑ Ð¤Ð¡ÐРв Affero в Ñвоей подпиÑи к
ÑлекÑÑоннÑм пиÑÑмам, пÑоекÑе
+по ÑазÑабоÑке пÑогÑамм и дÑÑгиÑ
пиÑÑменнÑÑ
маÑеÑиалаÑ
.
</li>
<li>
@@ -166,9 +168,9 @@
</li>
<li>
- <a href="/philosophy/selling.html">пÑÐ¾Ð´Ð°Ð²Ð°Ñ ÑвободнÑе
пÑогÑаммÑ</a> и
-жеÑÑвÑÑ ÑаÑÑÑ Ð´Ð¾Ñ
одов <a href="/fsf/fsf.html">ФондÑ
Ñвободного пÑогÑаммного
-обеÑпеÑениÑ</a> или дÑÑгим пÑоекÑам по
ÑазÑабоÑке ÑвободнÑÑ
+ <a href="/philosophy/selling.html">пÑÐ¾Ð´Ð°Ð²Ð°Ñ ÑвободнÑе
пÑогÑаммÑ</a> и вноÑÑ
+ÑаÑÑÑ Ð´Ð¾Ñ
одов в <a href="/fsf/fsf.html">Фонд
Ñвободного пÑогÑаммного
+обеÑпеÑениÑ</a> или дÑÑгие пÑоекÑÑ Ð¿Ð¾
ÑазÑабоÑке ÑвободнÑÑ
пÑогÑамм. ФинанÑиÑÑÑ ÑазÑабоÑки, вÑ
двигаеÑе впеÑед Ð¼Ð¸Ñ Ñвободного
пÑогÑаммного обеÑпеÑениÑ.
<p>
@@ -179,18 +181,17 @@
<li>
УбедиÑеÑÑ, ÑÑо оÑеÑки Ñ Ð½Ð°Ñей <a
href="/philosophy/philosophy.html">ÑÑÑаниÑÑ
-ÑилоÑоÑии</a> и дÑÑгие ÑÑÑаниÑÑ ÑайÑа GNU
ÑпоминаÑÑÑÑ Ð² каÑалогаÑ
Internet,
+ÑилоÑоÑии</a> и дÑÑгие ÑÑÑаниÑÑ ÑайÑа GNU
ÑпоминаÑÑÑÑ Ð² каÑалогаÑ
ÐнÑеÑнеÑа,
поÑÑалаÑ
и ÑазлиÑнÑÑ
поиÑковÑÑ
ÑиÑÑемаÑ
— ÑакиÑ
, как Yahoo!,
dmoz.org, Google, РамблеÑ, ЯндекÑ. ÐобавÑÑе на ÑÑи
ÑайÑÑ Ð¿Ð¾Ð´ÑобнÑе опиÑаниÑ
-ÑазнÑÑ
ÑÑÑÐ°Ð½Ð¸Ñ Ð½Ð°Ñего ÑайÑа. УбедиÑеÑÑ,
ÑÑо оÑеÑки Ñ Ð½Ð°Ñей
-<a href="/philosophy/philosophy.html">ÑÑÑаниÑÑ ÑилоÑоÑии</a>
и дÑÑгие
-ÑÑÑаниÑÑ Ð½Ð°Ñ
одÑÑÑÑ ÑÑеди пеÑвÑÑ
в
ÑооÑвеÑÑÑвÑÑÑиÑ
каÑегоÑиÑÑ
. ÐÑли Ð²Ñ Ñ
оÑиÑе
-помоÑÑ Ð½Ð°Ð¼ в ÑÑом, пожалÑйÑÑа, ÑвÑжиÑеÑÑ Ñ
кооÑдинаÑоÑами добÑоволÑÑев
-пÑоекÑа GNU <a href="mailto:address@hidden";><address@hidden></a>.
+ÑазнÑÑ
ÑÑÑÐ°Ð½Ð¸Ñ Ð½Ð°Ñего ÑайÑа. УбедиÑеÑÑ,
ÑÑо оÑеÑки Ñ Ð½Ð°Ñей <a
+href="/philosophy/philosophy.html">ÑÑÑаниÑÑ ÑилоÑоÑии</a> и
дÑÑгие ÑÑÑаниÑÑ
+наÑ
одÑÑÑÑ ÑÑеди пеÑвÑÑ
в ÑооÑвеÑÑÑвÑÑÑиÑ
каÑегоÑиÑÑ
. ÐÑли Ð²Ñ Ñ
оÑиÑе помоÑÑ
+нам в ÑÑом, пожалÑйÑÑа, ÑвÑжиÑеÑÑ Ñ
кооÑдинаÑоÑами добÑоволÑÑев пÑоекÑа GNU
+<a href="mailto:address@hidden";><address@hidden></a>.
</li>
- <li>ÐÑиноÑиÑе в Ð´Ð°Ñ Ð¤Ð¡ÐÐ <a
href="/help/help-hardware.html">аппаÑаÑное
-обеÑпеÑение</a>.</li>
+ <li>ÐÑиноÑиÑе в Ð´Ð°Ñ Ð¤Ð¡ÐÐ <a
href="/help/help-hardware.html">аппаÑаÑÑÑÑ</a>.</li>
<li>ÐозÑмиÑе на ÑÐµÐ±Ñ Ð²Ñполнение одной из <a
href="/server/tasks.html">ÑабоÑ</a>,
коÑоÑÑе нам необÑ
Ð¾Ð´Ð¸Ð¼Ñ Ð´Ð»Ñ ÑÑого <a
href="/server/server.html">ÑеÑвеÑа</a>.</li>
@@ -210,24 +211,52 @@
</ul>
-
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
<div style="font-size: small;">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
</div>
</div>
+<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.ru.html" -->
<div id="footer">
-<p>
-ÐожалÑйÑÑа, пÑиÑÑлайÑе запÑоÑÑ ÑÐ¾Ð½Ð´Ñ Ð¸ GNU
по адÑеÑÑ <a
+
+<p>ÐожалÑйÑÑа, пÑиÑÑлайÑе обÑие запÑоÑÑ
ÑÐ¾Ð½Ð´Ñ Ð¸ GNU по адÑеÑÑ <a
href="mailto:address@hidden";><address@hidden></a>. ÐÑÑÑ Ñакже <a
-href="/contact/">дÑÑгие ÑпоÑÐ¾Ð±Ñ ÑвÑзаÑÑÑÑ</a> Ñ
Ñондом.
-<br />
-ÐожалÑйÑÑа, пÑиÑÑлайÑе оÑÑеÑÑ Ð¾
неÑабоÑаÑÑиÑ
ÑÑÑлкаÑ
и дÑÑгие попÑавки или
-пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾ адÑеÑÑ <a
-href="mailto:address@hidden";><address@hidden></a>.
-</p>
+href="/contact/">дÑÑгие ÑпоÑÐ¾Ð±Ñ ÑвÑзаÑÑÑÑ</a> Ñ
Ñондом. ÐÑÑеÑÑ Ð¾
+неÑабоÑаÑÑиÑ
ÑÑÑлкаÑ
и дÑÑгие попÑавки
или пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¼Ð¾Ð¶Ð½Ð¾ пÑиÑÑлаÑÑ Ð¿Ð¾
+адÑеÑÑ <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p>
+
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+ÐÑ ÑÑаÑалиÑÑ ÑделаÑÑ ÑÑÐ¾Ñ Ð¿ÐµÑевод ÑоÑнÑм и
каÑеÑÑвеннÑм, но иÑклÑÑиÑÑ
+возможноÑÑÑ Ð¾Ñибки Ð¼Ñ Ð½Ðµ можем.
ÐÑиÑÑлайÑе, пожалÑйÑÑа, Ñвои замеÑÐ°Ð½Ð¸Ñ Ð¸
+пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾ пеÑÐµÐ²Ð¾Ð´Ñ Ð¿Ð¾ адÑеÑÑ <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p><p>Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ кооÑдинаÑии и
пÑедложениÑм пеÑеводов наÑиÑ
ÑÑаÑей Ñм. в
+<a href="/server/standards/README.translations.html">“Ð
ÑководÑÑве по
+пеÑеводам”</a>.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
@@ -250,7 +279,7 @@
<!-- timestamp start -->
Ðбновлено:
-$Date: 2012/09/16 09:18:40 $
+$Date: 2012/09/19 00:28:25 $
<!-- timestamp end -->
</p>
Index: help/po/help.de-en.html
===================================================================
RCS file: /web/www/www/help/po/help.de-en.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- help/po/help.de-en.html 16 Sep 2012 09:19:04 -0000 1.13
+++ help/po/help.de-en.html 19 Sep 2012 00:28:29 -0000 1.14
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.69 -->
-<title>How you can help the GNU Project - GNU Project - Free Software
Foundation (FSF)</title>
+<title>How you can help the GNU Project - GNU Project - Free Software
Foundation</title>
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -218,20 +219,43 @@
</ul>
-</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
-<!--#include virtual="/server/footer.html" -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
There are also <a href="/contact/">other ways to contact</a>
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
@@ -245,7 +269,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:19:04 $
+$Date: 2012/09/19 00:28:29 $
<!-- timestamp end -->
</p>
Index: help/po/help.it-en.html
===================================================================
RCS file: /web/www/www/help/po/help.it-en.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- help/po/help.it-en.html 16 Sep 2012 09:19:05 -0000 1.6
+++ help/po/help.it-en.html 19 Sep 2012 00:28:30 -0000 1.7
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.69 -->
-<title>How you can help the GNU Project - GNU Project - Free Software
Foundation (FSF)</title>
+<title>How you can help the GNU Project - GNU Project - Free Software
Foundation</title>
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -218,20 +219,43 @@
</ul>
-</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
-<!--#include virtual="/server/footer.html" -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
There are also <a href="/contact/">other ways to contact</a>
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
@@ -245,7 +269,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:19:05 $
+$Date: 2012/09/19 00:28:30 $
<!-- timestamp end -->
</p>
Index: help/po/help.it.po
===================================================================
RCS file: /web/www/www/help/po/help.it.po,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- help/po/help.it.po 18 Sep 2012 21:12:59 -0000 1.8
+++ help/po/help.it.po 19 Sep 2012 00:28:30 -0000 1.9
@@ -13,14 +13,8 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Outdated-Since: 2012-09-18 04:25-0300\n"
-# | How you can help the GNU Project - GNU Project - Free Software Foundation
-# | [-(FSF)-]
#. type: Content of: <title>
-#| msgid ""
-#| "How you can help the GNU Project - GNU Project - Free Software Foundation "
-#| "(FSF)"
msgid ""
"How you can help the GNU Project - GNU Project - Free Software Foundation"
msgstr "Come potete aiutare il Progetto GNU - Free Software Foundation"
@@ -442,14 +436,7 @@
msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
msgstr " "
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
-#| "org\"><address@hidden></a>. There are also <a href=\"/contact/"
-#| "\">other ways to contact</a> the FSF. Broken links and other corrections "
-#| "or suggestions can be sent to <a href=\"mailto:address@hidden";><"
-#| "address@hidden></a>."
msgid ""
"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
@@ -463,7 +450,6 @@
"link non funzionanti e altri suggerimenti relativi alle pagine web a <a href="
"\"mailto:address@hidden";><address@hidden></a>."
-# || No change detected. The change might only be in amounts of spaces.
#. TRANSLATORS: Ignore the original text in this paragraph,
#. replace it with the translation of these two:
#. We work hard and do our best to provide accurate, good quality
@@ -476,10 +462,6 @@
#. href="/server/standards/README.translations.html">Translations
#. README</a>.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Please see the <a href=\"/server/standards/README.translations.html"
-#| "\">Translations README</a> for information on coordinating and submitting "
-#| "translations of this article."
msgid ""
"Please see the <a href=\"/server/standards/README.translations.html"
"\">Translations README</a> for information on coordinating and submitting "
Index: help/po/help.pl-en.html
===================================================================
RCS file: /web/www/www/help/po/help.pl-en.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- help/po/help.pl-en.html 16 Sep 2012 09:19:05 -0000 1.5
+++ help/po/help.pl-en.html 19 Sep 2012 00:28:30 -0000 1.6
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.69 -->
-<title>How you can help the GNU Project - GNU Project - Free Software
Foundation (FSF)</title>
+<title>How you can help the GNU Project - GNU Project - Free Software
Foundation</title>
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -218,20 +219,43 @@
</ul>
-</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
-<!--#include virtual="/server/footer.html" -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
There are also <a href="/contact/">other ways to contact</a>
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
@@ -245,7 +269,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:19:05 $
+$Date: 2012/09/19 00:28:30 $
<!-- timestamp end -->
</p>
Index: help/po/help.ru-en.html
===================================================================
RCS file: /web/www/www/help/po/help.ru-en.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- help/po/help.ru-en.html 16 Sep 2012 09:19:05 -0000 1.9
+++ help/po/help.ru-en.html 19 Sep 2012 00:28:30 -0000 1.10
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.69 -->
-<title>How you can help the GNU Project - GNU Project - Free Software
Foundation (FSF)</title>
+<title>How you can help the GNU Project - GNU Project - Free Software
Foundation</title>
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/help/po/help.translist" -->
@@ -218,20 +219,43 @@
</ul>
-</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published. -->
-<!--#include virtual="/server/footer.html" -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
There are also <a href="/contact/">other ways to contact</a>
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
@@ -245,7 +269,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:19:05 $
+$Date: 2012/09/19 00:28:30 $
<!-- timestamp end -->
</p>
Index: help/po/help.ru.po
===================================================================
RCS file: /web/www/www/help/po/help.ru.po,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- help/po/help.ru.po 18 Sep 2012 17:02:10 -0000 1.23
+++ help/po/help.ru.po 19 Sep 2012 00:28:31 -0000 1.24
@@ -15,15 +15,9 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Outdated-Since: 2012-09-18 04:25-0300\n"
# type: Content of: <title>
#. type: Content of: <title>
-# | How you can help the GNU Project - GNU Project - Free Software Foundation
-# | [-(FSF)-]
-#| msgid ""
-#| "How you can help the GNU Project - GNU Project - Free Software Foundation "
-#| "(FSF)"
msgid ""
"How you can help the GNU Project - GNU Project - Free Software Foundation"
msgstr ""
@@ -103,13 +97,13 @@
"hackers-public</a> mailing list."
msgstr ""
"ÐомогиÑе Ñ ÑайÑом <a
href=\"http://savannah.gnu.org\";>Savannah</a>. ÐÑ Ð¸Ñем "
-"ÑеÑ
ниÑеÑкиÑ
ÑпеÑиалиÑÑов Ð´Ð»Ñ Ð¿Ð¾Ð¼Ð¾Ñи по
поддеÑжке инÑÑаÑÑÑÑкÑÑÑÑ. Также "
-"оÑÐµÐ½Ñ Ð¶ÐµÐ»Ð°ÑелÑна добÑоволÑÐ½Ð°Ñ Ð¿Ð¾Ð¼Ð¾ÑÑ Ð²
ÑегиÑÑÑаÑии пÑоекÑов. ÐожалÑйÑÑа, "
-"пÑоÑÑиÑе <a href=\"http://savannah.gnu.org/maintenance/";
-"HowToBecomeASavannahHacker\">обÑие ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾ Ñом, как
ÑÑаÑÑ Ð¿ÑогÑаммиÑÑом "
-"ÑайÑа Savannah</a>. ÐожалÑйÑÑа, ÑвÑжиÑеÑÑ Ñ Ð½Ð°Ð¼Ð¸
в оÑкÑÑÑом ÑпиÑке "
-"ÑаÑÑÑлки <a
href=\"http://lists.gnu.org/mailman/listinfo/savannah-hackers-";
-"public\">savannah-hackers-public</a>."
+"ÑеÑ
ниÑеÑкиÑ
ÑпеÑиалиÑÑов Ð´Ð»Ñ Ð¿Ð¾Ð¼Ð¾Ñи по
поддеÑжке инÑÑаÑÑÑÑкÑÑÑÑ. Также оÑÐµÐ½Ñ "
+"желаÑелÑна добÑоволÑÐ½Ð°Ñ Ð¿Ð¾Ð¼Ð¾ÑÑ Ð²
ÑегиÑÑÑаÑии пÑоекÑов. ÐожалÑйÑÑа, пÑоÑÑиÑе
"
+"<a href=\"http://savannah.gnu.org/maintenance/HowToBecomeASavannahHacker";
+"\">обÑие ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾ Ñом, как ÑÑаÑÑ
пÑогÑаммиÑÑом ÑайÑа Savannah</a>. "
+"ÐожалÑйÑÑа, ÑвÑжиÑеÑÑ Ñ Ð½Ð°Ð¼Ð¸ в оÑкÑÑÑом
ÑпиÑке ÑаÑÑÑлки <a href=\"http://";
+"lists.gnu.org/mailman/listinfo/savannah-hackers-public\">savannah-hackers-"
+"public</a>."
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
@@ -186,10 +180,9 @@
"\">GNU Coding Standards</a> and <a href=\"/prep/maintain/\">Information for "
"Maintainers of GNU Software</a> documents."
msgstr ""
-"Ðогда пиÑеÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ GNU, ÑледÑйÑе,
пожалÑйÑÑа, докÑменÑам “<a href="
-"\"/prep/standards/\">СÑандаÑÑÑ Ð¿ÑогÑаммиÑованиÑ
GNU</a>” и “<a "
-"href=\"/prep/maintain/\">Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ поддеÑжке
пÑогÑамм GNU</"
-"a>”."
+"Ðогда пиÑеÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ GNU, ÑледÑйÑе,
пожалÑйÑÑа, докÑменÑам “<a "
+"href=\"/prep/standards/\">СÑандаÑÑÑ Ð¿ÑогÑаммиÑованиÑ
GNU</a>” и “"
+"<a href=\"/prep/maintain/\">Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ поддеÑжке
пÑогÑамм GNU</a>”."
# type: Content of: <ul><li><ul><li>
#. type: Content of: <ul><li><ul><li>
@@ -262,8 +255,8 @@
"you want to help."
msgstr ""
"ÐеÑеведиÑе ÑÑÑаниÑÑ ÑайÑа GNU на дÑÑгие
ÑзÑки. ÐополниÑелÑнÑе ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ "
-"ÑмоÑÑиÑе в “<a
href=\"/server/standards/README.translations.html\">"
-"Ð ÑководÑÑве по пеÑÐµÐ²Ð¾Ð´Ñ ÑайÑа
www.gnu.org</a>”. ÐиÑиÑе по адÑеÑÑ <a "
+"ÑмоÑÑиÑе в “<a
href=\"/server/standards/README.translations.html"
+"\">Ð ÑководÑÑве по пеÑÐµÐ²Ð¾Ð´Ñ ÑайÑа
www.gnu.org</a>”. ÐиÑиÑе по адÑеÑÑ <a "
"href=\"mailto:address@hidden";><address@hidden></a>, "
"еÑли Ñ
оÑиÑе помоÑÑ."
@@ -295,9 +288,9 @@
"\">help us greatly</a>, while taking very little time once you have "
"unlearned the old habit."
msgstr ""
-"обÑÑÑнÑÑ Ñвоим знакомÑм, ÑÑо опеÑаÑионнаÑ
ÑиÑÑема “Linux” — "
-"ÑÑо на Ñамом деле <a
href=\"/gnu/linux-and-gnu.html\">GNU/Linux"
-"</a>, Ñ.е. ÑиÑÑема GNU + Linux, ÑдÑо; пÑоÑÑо
поÑледоваÑелÑно и безоÑибоÑно "
+"обÑÑÑнÑÑ Ñвоим знакомÑм, ÑÑо опеÑаÑионнаÑ
ÑиÑÑема “Linux” "
+"— ÑÑо на Ñамом деле <a
href=\"/gnu/linux-and-gnu.html\">GNU/Linux</"
+"a>, Ñ.е. ÑиÑÑема GNU + Linux, ÑдÑо; пÑоÑÑо
поÑледоваÑелÑно и безоÑибоÑно "
"подÑеÑÐºÐ¸Ð²Ð°Ñ ÑазлиÑÐ¸Ñ Ð¼ÐµÐ¶Ð´Ñ GNU/Linux
(ÑиÑÑемой в Ñелом) и Linux (ÑдÑом), "
"когда пиÑеÑе или говоÑиÑе об ÑÑой
опеÑаÑионной ÑиÑÑеме, Ð²Ñ <a href=\"/gnu/"
"why-gnu-linux.html\">оÑÐµÐ½Ñ Ð½Ð°Ð¼ поможеÑе</a>. ÐÑо
бÑÐ´ÐµÑ Ð·Ð°Ð½Ð¸Ð¼Ð°ÑÑ ÑовÑем "
@@ -324,8 +317,8 @@
msgstr ""
"Ðогда Ð²Ñ Ð±ÐµÑедÑеÑе Ñ Ð»ÑдÑми, коÑоÑÑе не
ÑенÑÑ ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð¸ ÑообÑеÑÑво, Ð²Ñ "
"можеÑе ÑказаÑÑ Ð¸Ð¼ на многие пÑакÑиÑеÑкие
доÑÑоинÑÑва ÑвободнÑÑ
пÑогÑамм (Ñм. "
-"некоÑоÑÑе полезнÑе ÑвидеÑелÑÑÑва в
ÑÑаÑÑе “<a href=\"http://www.dwheeler.com/";
-"oss_fs_why.html\">Why Open Source / Free Software? Look at the "
+"некоÑоÑÑе полезнÑе ÑвидеÑелÑÑÑва в
ÑÑаÑÑе “<a href=\"http://www.";
+"dwheeler.com/oss_fs_why.html\">Why Open Source / Free Software? Look at the "
"Numbers!</a>”). Ðо непÑеменно ÑпоминайÑе и об
ÑÑиÑеÑкиÑ
аÑпекÑаÑ
! Ðе "
"вÑÑказÑвайÑеÑÑ Ð² поддеÑÐ¶ÐºÑ Ð¾ÑкÑÑÑого иÑÑ
одного ÑекÑÑа ÑолÑко Ñади Ñого, "
"ÑÑÐ¾Ð±Ñ ÑгодиÑÑ ÐºÐ¾Ð¼Ñ-Ñо."
@@ -360,8 +353,8 @@
msgstr ""
"вÑбÑав ФСÐРкак оÑганизаÑиÑ, коÑоÑой
бÑдÑÑ Ð¸Ð´Ñи оÑÑиÑÐ»ÐµÐ½Ð¸Ñ Ð¾Ñ Ð²Ð°Ñего лиÑа "
"ÑеÑез ÑиÑÑÐµÐ¼Ñ <a
href=\"http://www.affero.com/ca/fsf\";>Affero</a>, ÑÑÑлаÑÑÑ "
-"на ÑÐ²Ð¾Ñ ÑÑÑаниÑÑ Ð¤Ð¡ÐРв Affero в Ñвоей
подпиÑи к ÑлекÑÑоннÑм пиÑÑмам, пÑоекÑе "
-"по ÑазÑабоÑке пÑогÑамм и дÑÑгиÑ
пиÑÑменнÑÑ
маÑеÑиалаÑ
."
+"на ÑÐ²Ð¾Ñ ÑÑÑаниÑÑ Ð¤Ð¡ÐРв Affero в Ñвоей
подпиÑи к ÑлекÑÑоннÑм пиÑÑмам, "
+"пÑоекÑе по ÑазÑабоÑке пÑогÑамм и дÑÑгиÑ
пиÑÑменнÑÑ
маÑеÑиалаÑ
."
# type: Content of: <ul><li><ul><li>
#. type: Content of: <ul><li><ul><li>
@@ -390,10 +383,10 @@
"development, you can advance the world of free software."
msgstr ""
"<a href=\"/philosophy/selling.html\">пÑÐ¾Ð´Ð°Ð²Ð°Ñ ÑвободнÑе
пÑогÑаммÑ</a> и "
-"вноÑÑ ÑаÑÑÑ Ð´Ð¾Ñ
одов в <a href=\"/fsf/fsf.html\">Фонд
Ñвободного "
-"пÑогÑаммного обеÑпеÑениÑ</a> или дÑÑгие
пÑоекÑÑ Ð¿Ð¾ ÑазÑабоÑке ÑвободнÑÑ
"
-"пÑогÑамм. ФинанÑиÑÑÑ ÑазÑабоÑки, вÑ
двигаеÑе впеÑед Ð¼Ð¸Ñ Ñвободного "
-"пÑогÑаммного обеÑпеÑениÑ."
+"вноÑÑ ÑаÑÑÑ Ð´Ð¾Ñ
одов в <a href=\"/fsf/fsf.html\">Фонд
Ñвободного пÑогÑаммного "
+"обеÑпеÑениÑ</a> или дÑÑгие пÑоекÑÑ Ð¿Ð¾
ÑазÑабоÑке ÑвободнÑÑ
пÑогÑамм. "
+"ФинанÑиÑÑÑ ÑазÑабоÑки, Ð²Ñ Ð´Ð²Ð¸Ð³Ð°ÐµÑе впеÑед
Ð¼Ð¸Ñ Ñвободного пÑогÑаммного "
+"обеÑпеÑениÑ."
# type: Content of: <ul><li><ul><li><p>
#. type: Content of: <ul><li><ul><li><p>
@@ -422,11 +415,11 @@
"каÑалогаÑ
ÐнÑеÑнеÑа, поÑÑалаÑ
и ÑазлиÑнÑÑ
поиÑковÑÑ
ÑиÑÑемаÑ
— "
"ÑакиÑ
, как Yahoo!, dmoz.org, Google, РамблеÑ, ЯндекÑ.
ÐобавÑÑе на ÑÑи ÑайÑÑ "
"подÑобнÑе опиÑÐ°Ð½Ð¸Ñ ÑазнÑÑ
ÑÑÑÐ°Ð½Ð¸Ñ Ð½Ð°Ñего
ÑайÑа. УбедиÑеÑÑ, ÑÑо оÑеÑки Ñ "
-"наÑей "
-"<a href=\"/philosophy/philosophy.html\">ÑÑÑаниÑÑ
ÑилоÑоÑии</a> и дÑÑгие "
-"ÑÑÑаниÑÑ Ð½Ð°Ñ
одÑÑÑÑ ÑÑеди пеÑвÑÑ
в
ÑооÑвеÑÑÑвÑÑÑиÑ
каÑегоÑиÑÑ
. ÐÑли Ð²Ñ Ñ
оÑиÑе
"
-"помоÑÑ Ð½Ð°Ð¼ в ÑÑом, пожалÑйÑÑа, ÑвÑжиÑеÑÑ Ñ
кооÑдинаÑоÑами добÑоволÑÑев "
-"пÑоекÑа GNU <a
href=\"mailto:address@hidden";><address@hidden></a>."
+"наÑей <a href=\"/philosophy/philosophy.html\">ÑÑÑаниÑÑ
ÑилоÑоÑии</a> и "
+"дÑÑгие ÑÑÑаниÑÑ Ð½Ð°Ñ
одÑÑÑÑ ÑÑеди пеÑвÑÑ
в
ÑооÑвеÑÑÑвÑÑÑиÑ
каÑегоÑиÑÑ
. ÐÑли Ð²Ñ "
+"Ñ
оÑиÑе помоÑÑ Ð½Ð°Ð¼ в ÑÑом, пожалÑйÑÑа,
ÑвÑжиÑеÑÑ Ñ ÐºÐ¾Ð¾ÑдинаÑоÑами "
+"добÑоволÑÑев пÑоекÑа GNU <a
href=\"mailto:address@hidden";><address@hidden></"
+"a>."
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
@@ -487,13 +480,6 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-# || No change detected. The change might only be in amounts of spaces.
-#| msgid ""
-#| "Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
-#| "org\"><address@hidden></a>. There are also <a href=\"/contact/"
-#| "\">other ways to contact</a> the FSF. Broken links and other corrections "
-#| "or suggestions can be sent to <a href=\"mailto:address@hidden";><"
-#| "address@hidden></a>."
msgid ""
"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
Index: people/past-webmasters.de.html
===================================================================
RCS file: /web/www/www/people/past-webmasters.de.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- people/past-webmasters.de.html 16 Sep 2012 09:22:13 -0000 1.6
+++ people/past-webmasters.de.html 19 Sep 2012 00:28:49 -0000 1.7
@@ -89,6 +89,13 @@
überzeugen, Freie Software zu benutzen und der GNU-Philosophie zu folgen; er
ist auch Mitglied im spanischen Ãbersetzungsteam.</dd>
+ <dt><strong><a href="http://freedomphilosophy.eu5.org";>Fabio
+J. Gonzalez</a></strong> <a href=
+"mailto:address@hidden";><address@hidden></a></dt>
+
+ <dd>Fabio ist ein brasilianischer GNU-Webmaster. AuÃerdem ist er
Programmierer
+und sorgt sich um die Freiheit von Rechnernutzern.</dd>
+
<dt><strong><a href="http://francoiacomella.org/";>Franco
Iacomella</a></strong>
<a href="mailto:address@hidden";><yaco at gnu.org></a></dt>
@@ -354,7 +361,7 @@
<!-- timestamp start -->
Aktualisierung:
-$Date: 2012/09/16 09:22:13 $
+$Date: 2012/09/19 00:28:49 $
<!-- timestamp end -->
</p>
Index: people/po/past-webmasters.de-en.html
===================================================================
RCS file: /web/www/www/people/po/past-webmasters.de-en.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- people/po/past-webmasters.de-en.html 16 Sep 2012 09:22:39 -0000
1.4
+++ people/po/past-webmasters.de-en.html 19 Sep 2012 00:29:00 -0000
1.5
@@ -103,6 +103,13 @@
GNU philosophy, he also works with the spanish
translation team.</dd>
+ <dt><strong><a href="http://freedomphilosophy.eu5.org";>Fabio
+ J. Gonzalez</a></strong> <a href=
+ "mailto:address@hidden";><address@hidden></a></dt>
+
+ <dd>Fabio is a brazilian GNU webmaster. He is also a programmer
+ and worry about the freedom of computer users.</dd>
+
<dt><strong><a href="http://francoiacomella.org/";>Franco
Iacomella</a></strong> <a href=
"mailto:address@hidden";><yaco at gnu.org></a></dt>
@@ -400,7 +407,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:22:39 $
+$Date: 2012/09/19 00:29:00 $
<!-- timestamp end -->
</p>
</div>
Index: people/po/past-webmasters.de.po
===================================================================
RCS file: /web/www/www/people/po/past-webmasters.de.po,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- people/po/past-webmasters.de.po 18 Sep 2012 18:55:08 -0000 1.7
+++ people/po/past-webmasters.de.po 19 Sep 2012 00:29:00 -0000 1.8
@@ -209,9 +209,6 @@
"ist auch Mitglied im spanischen Ãbersetzungsteam."
#. type: Content of: <dl><dt>
-#| msgid ""
-#| "<strong><a href=\"http://francoiacomella.org/\";>Franco Iacomella</a></"
-#| "strong> <a href= \"mailto:address@hidden";><yaco at gnu.org></a>"
msgid ""
"<strong><a href=\"http://freedomphilosophy.eu5.org\";>Fabio J. Gonzalez</a></"
"strong> <a href= \"mailto:address@hidden";><address@hidden>"
Index: philosophy/no-word-attachments.fr.html
===================================================================
RCS file: /web/www/www/philosophy/no-word-attachments.fr.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- philosophy/no-word-attachments.fr.html 16 Sep 2012 09:23:32 -0000
1.47
+++ philosophy/no-word-attachments.fr.html 19 Sep 2012 00:29:14 -0000
1.48
@@ -64,7 +64,7 @@
<p>
Beaucoup d'utilisateurs de GNU qui reçoivent des documents Word essaient de
-trouver des moyens de les lire. On peut de débrouiller pour trouver le texte
+trouver des moyens de les lire. On peut se débrouiller pour trouver le texte
en ASCII, plus ou moins masqué, en parcourant le fichier. Aujourd'hui, les
logiciels libres peuvent lire certains documents Word, mais pas tous (le
format est secret et n'a pas encore été totalement décodé). Et pire encore,
@@ -351,7 +351,7 @@
<!-- timestamp start -->
Dernière mise à jour :
-$Date: 2012/09/16 09:23:32 $
+$Date: 2012/09/19 00:29:14 $
<!-- timestamp end -->
</p>
Index: philosophy/po/no-word-attachments.fr-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/no-word-attachments.fr-en.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- philosophy/po/no-word-attachments.fr-en.html 16 Sep 2012 09:25:08
-0000 1.16
+++ philosophy/po/no-word-attachments.fr-en.html 19 Sep 2012 00:29:26
-0000 1.17
@@ -304,7 +304,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/16 09:25:08 $
+$Date: 2012/09/19 00:29:26 $
<!-- timestamp end -->
</p>
</div>
Index: server/standards/README.translations.de.html
===================================================================
RCS file: /web/www/www/server/standards/README.translations.de.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- server/standards/README.translations.de.html 17 Sep 2012 08:27:47
-0000 1.22
+++ server/standards/README.translations.de.html 19 Sep 2012 00:29:46
-0000 1.23
@@ -19,17 +19,18 @@
<h3 id="intro">Einführung</h3>
<p>Die vielen Artikel auf gnu.org zu übersetzen und aktuell zu halten ist eine
-komplexe Aufgabe, die sorgfältige Organisation erfordert. ÃbersetzerInnen
-sind in Teams gruppiert, eins für jede Sprache, und jedes hat normalerweise
-einen Koordinator. Jedoch gibt es einige Sprachen, für die noch kein Team
-eingerichtet wurde, und manchem ist ein Koordinator verloren gegangen.</p>
+komplexe Aufgabe, die eine sorgfältige Organisation
+erfordert. ÃbersetzerInnen sind in Teams gruppiert, eins für jede Sprache,
+und jedes hat normalerweise einen Koordinator. Jedoch gibt es einige
+Sprachen, für die noch kein Team gegründet wurde, und manchem ist ein
+Koordinator verloren gegangen.</p>
<p>Teamkoordinatoren verwenden Dienstprogramme, um Webseiten effizient für
teilweise Ãnderungen zu aktualisieren. Eines dieser Dienstprogramme ist ein
Programm namens <strong>GNUnited Nations</strong> (GNUN) , das es sehr
leicht macht, Ãbersetzungen zu pflegen und im Auge zu behalten, was
aktualisiert werden muss; es wurde ad hoc vom derzeitigen GNU-<span
-xml:lang="en" lang="en">Translations Manager</span> Yavor Doganov
+xml:lang="en" lang="en">Translations Manager</span>, Yavor Doganov,
entwickelt.</p>
<p>Der <span xml:lang="en" lang="en">Translations Manager</span> ist die für
@@ -97,9 +98,9 @@
sollte es kein Team oder TeamkoordinatorIn geben.</dd>
<dt>Als Teamkoordinator</dt>
- <dd>Ist noch kein Team in Ihrer Sprache vorhanden oder ein neuer
Teamkoordinator
-erforderlich, sind wir dankbar, wenn Sie diese Aufgabe übernehmen
-würden. Als Koordinator müssen Sie sowohl dem allgemeinen <a
+ <dd>Ist noch kein Team in Ihrer Sprache gegründet oder ein neue/r
+TeamkoordinatorIn erforderlich, sind wir dankbar, wenn Sie diese Aufgabe
+übernehmen würden. Als Koordinator müssen Sie sowohl dem allgemeinen <a
href="#general-guide">Leitfaden für Ãbersetzungen</a> als auch dem <a
href="#coordinator-guide">Leitfaden für Teamkoordinatoren</a> folgen.
</dd>
@@ -151,7 +152,7 @@
<ul>
<li><p><strong><em>Copyleft</em></strong>. Das ist ein Begriff, der in
einigen
-Sprachen schwer übersetzbar sein kann und ein Wortspiel mit dem Wort
+Sprachen schwer übersetzbar sein kann und ist ein Wortspiel mit dem Wort
<em>Copyright</em> basierend auf die beiden Bedeutungen von <em>right</em>:
ethisch und richtungsweisend. Weitere Informationen (und wie er in andere
Sprachen übersetzt wurde) finden Sie im Artikel <a
@@ -171,7 +172,7 @@
GNU-Projekts]â</em> diese Unterscheidung noch nicht vorgenommen. Beim
Ãbersetzen [oder Korrekturlesen] muss also sorgfältig die richtige
Behandlung des Wortes <em>frei</em> geachtet werden. Sie haben die
-Möglichkeit, das Wort auf Englisch zu lassen, gefolgt von einer Erklärung
+Möglichkeit, das Wort auf Englisch zu belassen, gefolgt von einer Erklärung
der Bedeutung: entweder Freiheit, Preis oder mehrdeutig beides.</p>
<p>Allerdings sollte auch in diesen alten Dokumenten das Wort <span
@@ -595,7 +596,7 @@
<p><!-- timestamp start -->
Aktualisierung:
-$Date: 2012/09/17 08:27:47 $
+$Date: 2012/09/19 00:29:46 $
<!-- timestamp end -->
</p>
Index: server/standards/po/README.translations.de-en.html
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.de-en.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- server/standards/po/README.translations.de-en.html 17 Sep 2012 08:28:04
-0000 1.13
+++ server/standards/po/README.translations.de-en.html 19 Sep 2012 00:29:58
-0000 1.14
@@ -580,7 +580,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/09/17 08:28:04 $
+$Date: 2012/09/19 00:29:58 $
<!-- timestamp end -->
</p>
</div>
Index: gnu/po/thegnuproject.ca-diff.html
===================================================================
RCS file: gnu/po/thegnuproject.ca-diff.html
diff -N gnu/po/thegnuproject.ca-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/po/thegnuproject.ca-diff.html 19 Sep 2012 00:28:09 -0000 1.1
@@ -0,0 +1,1060 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/gnu/thegnuproject.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+
+<title>About the GNU Project - GNU Project - Free Software Foundation
(FSF)</title>
+
+<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software,
Free Software Foundation, History" />
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+
+<h2>The GNU Project</h2>
+
+<!-- This document uses XHTML 1.0 Strict, but may be served as -->
+<!-- text/html. Please ensure that markup style considers -->
+<!-- appendex C of the XHTML 1.0 standard. See validator.w3.org. -->
+
+<!-- Please ensure links are consistent with Apache's MultiView. -->
+<!-- Change include statements to be consistent with the relevant -->
+<!-- language, where necessary. -->
+
+<p>
+by <a href="http://www.stallman.org/"><strong>Richard
Stallman</strong></a></p>
+<span class="inserted"><ins><em><blockquote></em></ins></span>
+<p>
+<span class="removed"><del><strong>the original version
was</strong></del></span>
+<span class="inserted"><ins><em>Originally</em></ins></span> published in the
book <span class="removed"><del><strong>“Open
Sources”</p></strong></del></span> <span
class="inserted"><ins><em><em>Open Sources</em>. Richard
+Stallman was <a href="/philosophy/open-source-misses-the-point.html">
+never a supporter of “open source”</a>, but contributed
+this article so that the ideas of the free software movement would not
+be entirely absent from that book.
+</p>
+</blockquote></em></ins></span>
+
+<h3>The first software-sharing community</h3>
+<p>
+When I started working at the
+<acronym title="Massachusetts Institute of
Technology">MIT</acronym>
+Artificial Intelligence Lab in 1971, I became part of a
+software-sharing community that had existed for many years. Sharing
+of software was not limited to our particular community; it is as old
+as computers, just as sharing of recipes is as old as cooking. But we
+did it more than most.</p>
+<p>
+The AI Lab used a timesharing operating system called
+<acronym title="Incompatible Timesharing System">ITS</acronym> (the
+Incompatible Timesharing System) that the lab's staff hackers (1) had
+designed and written in assembler language for the Digital
+<acronym title="Programmed Data Processor">PDP</acronym>-10, one of
+the large computers of the era. As a member of this community, an AI
+Lab staff system hacker, my job was to improve this system.</p>
+<p>
+We did not call our software “free software”, because that
+term did not yet exist; but that is what it was. Whenever people from
+another university or a company wanted to port and use a program, we
+gladly let them. If you saw someone using an unfamiliar and
+interesting program, you could always ask to see the source code, so
+that you could read it, change it, or cannibalize parts of it to make
+a new program.</p>
+<p>
+(1) The use of “hacker” to mean “security
+breaker” is a confusion on the part of the mass media. We
+hackers refuse to recognize that meaning, and continue using the word
+to mean someone who loves to program, someone who enjoys playful
+cleverness, or the combination of the two. See my
+article, <a href="http://stallman.org/articles/on-hacking.html">On
+Hacking</a>.</p>
+
+<h3>The collapse of the community</h3>
+<p>
+The situation changed drastically in the early 1980s when Digital
+discontinued the PDP-10 series. Its architecture, elegant and
+powerful in the 60s, could not extend naturally to the larger address
+spaces that were becoming feasible in the 80s. This meant that nearly
+all of the programs composing ITS were obsolete.</p>
+<p>
+The AI Lab hacker community had already collapsed, not long before.
+In 1981, the spin-off company Symbolics had hired away nearly all of
+the hackers from the AI Lab, and the depopulated community was unable
+to maintain itself. (The book Hackers, by Steve Levy, describes these
+events, as well as giving a clear picture of this community in its
+prime.) When the AI Lab bought a new PDP-10 in 1982, its
+administrators decided to use Digital's nonfree timesharing system
+instead of ITS.</p>
+<p>
+The modern computers of the era, such as the VAX or the 68020, had
+their own operating systems, but none of them were free software: you
+had to sign a nondisclosure agreement even to get an executable copy.</p>
+<p>
+This meant that the first step in using a computer was to promise not
+to help your neighbor. A cooperating community was forbidden. The
+rule made by the owners of proprietary software was, “If you
+share with your neighbor, you are a pirate. If you want any changes,
+beg us to make them.”</p>
+<p>
+The idea that the proprietary software social system—the system
+that says you are not allowed to share or change software—is
+antisocial, that it is unethical, that it is simply wrong, may come as
+a surprise to some readers. But what else could we say about a system
+based on dividing the public and keeping users helpless? Readers who
+find the idea surprising may have taken the proprietary software
+social system as a given, or judged it on the terms suggested by
+proprietary software businesses. Software publishers have worked long
+and hard to convince people that there is only one way to look at the
+issue.</p>
+<p>
+When software publishers talk about “enforcing” their
+“rights” or “stopping <a
href="/philosophy/words-to-avoid.html#Piracy">piracy</a>”, what
they
+actually <em>say</em> is secondary. The real message of these
statements is
+in the unstated assumptions they take for granted, which the public is
+asked to accept without examination. Let's therefore examine them.</p>
+<p>
+One assumption is that software companies have an unquestionable natural
+right to own software and thus have power over all its users. (If
+this were a natural right, then no matter how much harm it does to the
+public, we could not object.) Interestingly, the US Constitution and
+legal tradition reject this view; copyright is not a natural right,
+but an artificial government-imposed monopoly that limits the users'
+natural right to copy.</p>
+<p>
+Another unstated assumption is that the only important thing about
+software is what jobs it allows you to do—that we computer users
+should not care what kind of society we are allowed to have.</p>
+<p>
+A third assumption is that we would have no usable software (or would
+never have a program to do this or that particular job) if we did not
+offer a company power over the users of the program. This assumption
+may have seemed plausible, before the free software movement
+demonstrated that we can make plenty of useful software without
+putting chains on it.</p>
+<p>
+If we decline to accept these assumptions, and judge these issues
+based on ordinary commonsense morality while placing the users first,
+we arrive at very different conclusions. Computer users should be
+free to modify programs to fit their needs, and free to share
+software, because helping other people is the basis of society.</p>
+<p>
+There is no room here for an extensive statement of the reasoning
+behind this conclusion, so I refer the reader to the web page,
+<a href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a>.</p>
+
+<h3>A stark moral <span
class="removed"><del><strong>choice.</h3></strong></del></span> <span
class="inserted"><ins><em>choice</h3></em></ins></span>
+<p>
+With my community gone, to continue as before was impossible.
+Instead, I faced a stark moral choice.</p>
+<p>
+The easy choice was to join the proprietary software world, signing
+nondisclosure agreements and promising not to help my fellow hacker.
+Most likely I would also be developing software that was released
+under nondisclosure agreements, thus adding to the pressure on other
+people to betray their fellows too.</p>
+<p>
+I could have made money this way, and perhaps amused myself writing
+code. But I knew that at the end of my career, I would look back on
+years of building walls to divide people, and feel I had spent my life
+making the world a worse place.</p>
+<p>
+I had already experienced being on the receiving end of a
+nondisclosure agreement, when someone refused to give me and the MIT
+AI Lab the source code for the control program for our printer. (The
+lack of certain features in this program made use of the printer
+extremely frustrating.) So I could not tell myself that nondisclosure
+agreements were innocent. I was very angry when he refused to share
+with us; I could not turn around and do the same thing to everyone
+else.</p>
+<p>
+Another choice, straightforward but unpleasant, was to leave the
+computer field. That way my skills would not be misused, but they
+would still be wasted. I would not be culpable for dividing and
+restricting computer users, but it would happen nonetheless.</p>
+<p>
+So I looked for a way that a programmer could do something for the
+good. I asked myself, was there a program or programs that I could
+write, so as to make a community possible once again?</p>
+<p>
+The answer was clear: what was needed first was an operating system.
+That is the crucial software for starting to use a computer. With an
+operating system, you can do many things; without one, you cannot run
+the computer at all. With a free operating system, we could again
+have a community of cooperating hackers—and invite anyone to join.
+And anyone would be able to use a computer without starting out by
+conspiring to deprive his or her friends.</p>
+<p>
+As an operating system developer, I had the right skills for this job.
+So even though I could not take success for granted, I realized that I
+was elected to do the job. I chose to make the system compatible with
+Unix so that it would be portable, and so that Unix users could easily
+switch to it. The name GNU was chosen, following a hacker tradition, as
+a recursive acronym for “GNU's Not Unix.”</p>
+<p>
+An operating system does not mean just a kernel, barely enough to run
+other programs. In the 1970s, every operating system worthy of the
+name included command processors, assemblers, compilers, interpreters,
+debuggers, text editors, mailers, and much more. ITS had them,
+Multics had them, VMS had them, and Unix had them. The GNU operating
+system would include them too.</p>
+<p>
+Later I heard these words, attributed to Hillel (1):</p>
+
+<blockquote><p>
+ If I am not for myself, who will be for me?<br />
+ If I am only for myself, what am I?<br />
+ If not now, when?
+</p></blockquote>
+<p>
+The decision to start the GNU Project was based on a similar spirit.</p>
+<p>
+(1) As an Atheist, I don't follow any religious leaders, but I
+sometimes find I admire something one of them has said.</p>
+
+<h3>Free as in freedom</h3>
+<p>
+The term “free software” is sometimes misunderstood—it
+has nothing to do with price. It is about freedom. Here, therefore,
+is the definition of free software.</p>
+
+<p>A program is free software, for you, a particular user, if:</p>
+
+<ul>
+ <li>You have the freedom to run the program as you wish, for any
purpose.</li>
+
+ <li>You have the freedom to modify the program to suit your needs.
+ (To make this freedom effective in practice, you must have access
+ to the source code, since making changes in a program without
+ having the source code is exceedingly difficult.)</li>
+
+ <li>You have the freedom to redistribute copies, either gratis
+ or for a fee.</li>
+
+ <li>You have the freedom to distribute modified versions of the
program,
+ so that the community can benefit from your improvements.</li>
+</ul>
+<p>
+Since “free” refers to freedom, not to price, there is no
+contradiction between selling copies and free software. In fact, the
+freedom to sell copies is crucial: collections of free software sold
+on CD-ROMs are important for the community, and selling them is an
+important way to raise funds for free software development.
+Therefore, a program which people are not free to include on these
+collections is not free software.</p>
+<p>
+Because of the ambiguity of “free”, people have long
+looked for alternatives, but no one has found a better term.
+The English language has more words and nuances than any other, but it
+lacks a simple, unambiguous, word that means “free”, as in
+freedom—“unfettered” being the word that comes closest in
+meaning. Such alternatives as “liberated”,
+“freedom”, and “open” have either the wrong
+meaning or some other disadvantage.</p>
+
+<h3>GNU software and the GNU system</h3>
+<p>
+Developing a whole system is a very large project. To bring it into
+reach, I decided to adapt and use existing pieces of free software
+wherever that was possible. For example, I decided at the very
+beginning to use TeX as the principal text formatter; a few years
+later, I decided to use the X Window System rather than writing
+another window system for GNU.</p>
+<p>
+Because of <span class="removed"><del><strong>this
decision,</strong></del></span> <span class="inserted"><ins><em>these
decisions, and others like them,</em></ins></span>
+the GNU system is not the same as the collection of all
+GNU software. The GNU system includes programs that are not GNU
+software, programs that were developed by other people and projects
+for their own purposes, but which we can use because they are free
+software.</p>
+
+<h3>Commencing the project</h3>
+<p>
+In January 1984 I quit my job at MIT and began writing GNU software.
+Leaving MIT was necessary so that MIT would not be able to interfere
+with distributing GNU as free software. If I had remained on the
+staff, MIT could have claimed to own the work, and could have imposed
+their own distribution terms, or even turned the work into a
+proprietary software package. I had no intention of doing a large
+amount of work only to see it become useless for its intended purpose:
+creating a new software-sharing community.</p>
+<p>
+However, Professor Winston, then the head of the MIT AI Lab, kindly
+invited me to keep using the lab's facilities.</p>
+
+<h3>The first steps</h3>
+<p>
+Shortly before beginning the GNU Project, I heard about the Free
+University Compiler Kit, also known as VUCK. (The Dutch word for
+“free” is written with a <em>v</em>.) This was a
compiler
+designed to handle multiple languages, including C and Pascal, and to
+support multiple target machines. I wrote to its author asking if GNU
+could use it.</p>
+<p>
+He responded derisively, stating that the university was free but the
+compiler was not. I therefore decided that my first program for the
+GNU Project would be a multilanguage, multiplatform compiler.</p>
+<p>
+Hoping to avoid the need to write the whole compiler myself, I
+obtained the source code for the Pastel compiler, which was a
+multiplatform compiler developed at Lawrence Livermore Lab. It
+supported, and was written in, an extended version of Pascal, designed
+to be a system-programming language. I added a C front end, and began
+porting it to the Motorola 68000 computer. But I had to give that
+up when I discovered that the compiler needed many megabytes of stack
+space, and the available 68000 Unix system would only allow 64k.</p>
+<p>
+I then realized that the Pastel compiler functioned by parsing the
+entire input file into a syntax tree, converting the whole syntax tree
+into a chain of “instructions”, and then generating the
+whole output file, without ever freeing any storage. At this point, I
+concluded I would have to write a new compiler from scratch. That new
+compiler is now known as <acronym title="GNU Compiler
Collection">GCC</acronym>;
+none of the Pastel compiler is used in it, but I managed to adapt and
+use the C front end that I had written. But that was some years
+later; first, I worked on GNU Emacs.</p>
+
+<h3>GNU Emacs</h3>
+<p>
+I began work on GNU Emacs in September 1984, and in early 1985 it was
+beginning to be usable. This enabled me to begin using Unix systems
+to do editing; having no interest in learning to use vi or ed, I had
+done my editing on other kinds of machines until then.</p>
+<p>
+At this point, people began wanting to use GNU Emacs, which raised the
+question of how to distribute it. Of course, I put it on the
+anonymous ftp server on the MIT computer that I used. (This computer,
+prep.ai.mit.edu, thus became the principal GNU ftp distribution site;
+when it was decommissioned a few years later, we transferred the name
+to our new ftp server.) But at that time, many of the interested
+people were not on the Internet and could not get a copy by ftp. So
+the question was, what would I say to them?</p>
+<p>
+I could have said, “Find a friend who is on the net and who will make
+a copy for you.” Or I could have done what I did with the original
+PDP-10 Emacs: tell them, “Mail me a tape and a
+<acronym title="Self-addressed Stamped Envelope">SASE</acronym>,
and I
+will mail it back with Emacs on it.” But I had no job, and I was
+looking for ways to make money from free software. So I announced
+that I would mail a tape to whoever wanted one, for a fee of $150. In
+this way, I started a free software distribution business, the
+precursor of the companies that today distribute entire Linux-based
+GNU systems.</p>
+
+<h3>Is a program free for every user?</h3>
+<p>
+If a program is free software when it leaves the hands of its author,
+this does not necessarily mean it will be free software for everyone
+who has a copy of it. For example,
+<a href="/philosophy/categories.html#PublicDomainSoftware"> public domain
+software</a> (software that is not copyrighted) is free software; but
+anyone can make a proprietary modified version of it. Likewise, many
+free programs are copyrighted but distributed under simple permissive
+licenses which allow proprietary modified versions.</p>
+<p>
+The paradigmatic example of this problem is the X Window System.
+Developed at MIT, and released as free software with a permissive
+license, it was soon adopted by various computer companies. They
+added X to their proprietary Unix systems, in binary form only, and
+covered by the same nondisclosure agreement. These copies of X were
+no more free software than Unix was.</p>
+<p>
+The developers of the X Window System did not consider this a
+problem—they expected and intended this to happen. Their goal was
+not freedom, just “success”, defined as “having many
+users.” They did not care whether these users had freedom, only
+that they should be numerous.</p>
+<p>
+This led to a paradoxical situation where two different ways of
+counting the amount of freedom gave different answers to the question,
+“Is this program free?” If you judged based on the freedom
+provided by the distribution terms of the MIT release, you would say
+that X was free software. But if you measured the freedom of the
+average user of X, you would have to say it was proprietary software.
+Most X users were running the proprietary versions that came with Unix
+systems, not the free version.</p>
+
+<h3>Copyleft and the GNU GPL</h3>
+<p>
+The goal of GNU was to give users freedom, not just to be popular. So
+we needed to use distribution terms that would prevent GNU software
+from being turned into proprietary software. The method we use is
+called “copyleft”.(1)</p>
+<p>
+Copyleft uses copyright law, but flips it over to serve the opposite
+of its usual purpose: instead of a means for restricting a program, it
+becomes a means for keeping the program free.</p>
+<p>
+The central idea of copyleft is that we give everyone permission to
+run the program, copy the program, modify the program, and distribute
+modified versions—but not permission to add restrictions of their
+own. Thus, the crucial freedoms that define “free
+software” are guaranteed to everyone who has a copy; they become
+inalienable rights.</p>
+<p>
+For an effective copyleft, modified versions must also be free. This
+ensures that work based on ours becomes available to our community if
+it is published. When programmers who have jobs as programmers
+volunteer to improve GNU software, it is copyleft that prevents their
+employers from saying, “You can't share those changes, because
+we are going to use them to make our proprietary version of the
+program.”</p>
+<p>
+The requirement that changes must be free is essential if we want to
+ensure freedom for every user of the program. The companies that
+privatized the X Window System usually made some changes to port it to
+their systems and hardware. These changes were small compared with
+the great extent of X, but they were not trivial. If making changes
+were an excuse to deny the users freedom, it would be easy for anyone
+to take advantage of the excuse.</p>
+<p>
+A related issue concerns combining a free program with nonfree code.
+Such a combination would inevitably be nonfree; whichever freedoms
+are lacking for the nonfree part would be lacking for the whole as
+well. To permit such combinations would open a hole big enough to
+sink a ship. Therefore, a crucial requirement for copyleft is to plug
+this hole: anything added to or combined with a copylefted program
+must be such that the larger combined version is also free and
+copylefted.</p>
+<p>
+The specific implementation of copyleft that we use for most GNU
+software is the GNU General Public License, or GNU GPL for short. We
+have other kinds of copyleft that are used in specific circumstances.
+GNU manuals are copylefted also, but use a much simpler kind of
+copyleft, because the complexity of the GNU GPL is not necessary
+for manuals.(2)</p>
+<p>
+(1) In 1984 or 1985, Don Hopkins (a very imaginative fellow) mailed me
+a letter. On the envelope he had written several amusing sayings,
+including this one: “Copyleft—all rights reversed.” I
+used the word “copyleft” to name the distribution concept
+I was developing at the time.</p>
+
+<p>
+(2) We now use the <a href="/licenses/fdl.html">GNU Free
+Documentation License</a> for documentation.</p>
+
+<h3>The Free Software Foundation</h3>
+
+<p>As interest in using Emacs was growing, other people became
+involved in the GNU project, and we decided that it was time to seek
+funding once again. So in 1985 we created
+the <a href="http://www.fsf.org/">Free Software Foundation</a>
(FSF),
+a tax-exempt charity for free software development. The
+<acronym title="Free Software Foundation">FSF</acronym> also took
over
+the Emacs tape distribution business; later it extended this by adding
+other free software (both GNU and non-GNU) to the tape, and by selling
+free manuals as well.</p>
+
+<p>Most of the FSF's income used to come from sales of copies of free
+software and of other related services (CD-ROMs of source code,
+CD-ROMs with binaries, nicely printed manuals, all with the freedom to
+redistribute and modify), and Deluxe Distributions (distributions for
+which we built the whole collection of software for the customer's
+choice of platform). Today the FSF
+still <a href="http://shop.fsf.org/"> sells manuals and other
+gear</a>, but it gets the bulk of its funding from members' dues. You
+can join the FSF at <a
href="http://fsf.org/join">fsf.org</a>.</p>
+
+<p>Free Software Foundation employees have written and maintained a
+number of GNU software packages. Two notable ones are the C library
+and the shell. The GNU C library is what every program running on a
+GNU/Linux system uses to communicate with Linux. It was developed by
+a member of the Free Software Foundation staff, Roland McGrath. The
+shell used on most GNU/Linux systems is
+<acronym title="Bourne Again Shell">BASH</acronym>, the Bourne
Again
+Shell(1), which was developed by FSF employee Brian Fox.</p>
+
+<p>We funded development of these programs because the GNU Project was
+not just about tools or a development environment. Our goal was a
+complete operating system, and these programs were needed for that
+goal.</p>
+
+<p>(1) “Bourne Again Shell” is a play on the name
+“Bourne Shell”, which was the usual shell on Unix.</p>
+
+<h3>Free software support</h3>
+
+<p>The free software philosophy rejects a specific widespread business
+practice, but it is not against business. When businesses respect the
+users' freedom, we wish them success.</p>
+
+<p>Selling copies of Emacs demonstrates one kind of free software
+business. When the FSF took over that business, I needed another way
+to make a living. I found it in selling services relating to the free
+software I had developed. This included teaching, for subjects such
+as how to program GNU Emacs and how to customize GCC, and software
+development, mostly porting GCC to new platforms.</p>
+
+<p>Today each of these kinds of free software business is practiced by a
+number of corporations. Some distribute free software collections on
+CD-ROM; others sell support at levels ranging from answering user
+questions, to fixing bugs, to adding major new features. We are even
+beginning to see free software companies based on launching new free
+software products.</p>
+
+<p>Watch out, though—a number of companies that associate
themselves
+with the term “open source” actually base their business
+on nonfree software that works with free software. These are not
+free software companies, they are proprietary software companies whose
+products tempt users away from freedom. They call these programs
+“value-added packages”, which shows the values they
+would like us to adopt: convenience above freedom. If we value freedom
+more, we should call them “freedom-subtracted” packages.</p>
+
+<h3>Technical goals</h3>
+
+<p>The principal goal of GNU is to be free software. Even if GNU had no
+technical advantage over Unix, it would have a social advantage,
+allowing users to cooperate, and an ethical advantage, respecting the
+user's freedom.</p>
+
+<p>But it was natural to apply the known standards of good practice to
+the work—for example, dynamically allocating data structures to avoid
+arbitrary fixed size limits, and handling all the possible 8-bit codes
+wherever that made sense.</p>
+
+<p>In addition, we rejected the Unix focus on small memory size, by
+deciding not to support 16-bit machines (it was clear that 32-bit
+machines would be the norm by the time the GNU system was finished),
+and to make no effort to reduce memory usage unless it exceeded a
+megabyte. In programs for which handling very large files was not
+crucial, we encouraged programmers to read an entire input file into
+core, then scan its contents without having to worry about I/O.</p>
+
+<p>These decisions enabled many GNU programs to surpass their Unix
+counterparts in reliability and speed.</p>
+
+<h3>Donated computers</h3>
+
+<p>As the GNU Project's reputation grew, people began offering to donate
+machines running Unix to the project. These were very useful, because
+the easiest way to develop components of GNU was to do it on a Unix
+system, and replace the components of that system one by one. But
+they raised an ethical issue: whether it was right for us to have a
+copy of Unix at all.</p>
+
+<p>Unix was (and is) proprietary software, and the GNU Project's
+philosophy said that we should not use proprietary software. But,
+applying the same reasoning that leads to the conclusion that violence
+in self defense is justified, I concluded that it was legitimate to
+use a proprietary package when that was crucial for developing a free
+replacement that would help others stop using the proprietary
package.</p>
+
+<p>But, even if this was a justifiable evil, it was still an evil. Today
+we no longer have any copies of Unix, because we have replaced them
+with free operating systems. If we could not replace a machine's
+operating system with a free one, we replaced the machine instead.</p>
+
+<h3>The GNU Task List</h3>
+
+<p>As the GNU Project proceeded, and increasing numbers of system
+components were found or developed, eventually it became useful to
+make a list of the remaining gaps. We used it to recruit developers
+to write the missing pieces. This list became known as the GNU Task
+List. In addition to missing Unix components, we listed various
+other useful software and documentation projects that, we thought, a
+truly complete system ought to have.</p>
+
+<p>Today (1), hardly any Unix components are left in the GNU Task
+List—those jobs had been done, aside from a few inessential
+ones. But the list is full of projects that some might call
+“applications”. Any program that appeals to more than a
+narrow class of users would be a useful thing to add to an operating
+system.</p>
+
+<p>Even games are included in the task list—and have been since the
+beginning. Unix included games, so naturally GNU should too. But
+compatibility was not an issue for games, so we did not follow the
+list of games that Unix had. Instead, we listed a spectrum of
+different kinds of games that users might like.</p>
+
+<p>(1) That was written in 1998. In 2009 we no longer maintain a long
+task list. The community develops free software so fast that we can't
+even keep track of it all. Instead, we have a list of High Priority
+Projects, a much shorter list of projects we really want to encourage
+people to write.</p>
+
+<h3>The GNU Library GPL</h3>
+
+<p>The GNU C library uses a special kind of copyleft called the GNU
+Library General Public License(1), which gives permission to link
+proprietary software with the library. Why make this exception?</p>
+
+<p>It is not a matter of principle; there is no principle that says
+proprietary software products are entitled to include our code. (Why
+contribute to a project predicated on refusing to share with us?)
+Using the LGPL for the C library, or for any library, is a matter of
+strategy.</p>
+
+<p>The C library does a generic job; every proprietary system or compiler
+comes with a C library. Therefore, to make our C library available
+only to free software would not have given free software any
+advantage—it would only have discouraged use of our library.</p>
+
+<p>One system is an exception to this: on the GNU system (and this
+includes GNU/Linux), the GNU C library is the only C library. So the
+distribution terms of the GNU C library determine whether it is
+possible to compile a proprietary program for the GNU system. There
+is no ethical reason to allow proprietary applications on the GNU
+system, but strategically it seems that disallowing them would do more
+to discourage use of the GNU system than to encourage development of
+free applications. That is why using the Library GPL is a good
+strategy for the C library.</p>
+
+<p>For other libraries, the strategic decision needs to be
+considered on a case-by-case basis. When a library does a special job
+that can help write certain kinds of programs, then releasing it under
+the GPL, limiting it to free programs only, is a way of helping other
+free software developers, giving them an advantage against proprietary
+software.</p>
+
+<p>Consider GNU Readline, a library that was developed to provide
+command-line editing for BASH. Readline is released under the
+ordinary GNU GPL, not the Library GPL. This probably does reduce the
+amount Readline is used, but that is no loss for us. Meanwhile, at
+least one useful application has been made free software specifically
+so it could use Readline, and that is a real gain for the
+community.</p>
+
+<p>Proprietary software developers have the advantages money provides;
+free software developers need to make advantages for each other. I
+hope some day we will have a large collection of GPL-covered libraries
+that have no parallel available to proprietary software, providing
+useful modules to serve as building blocks in new free software, and
+adding up to a major advantage for further free software development.</p>
+
+<p>(1) This license is now called the GNU Lesser General Public License,
+to avoid giving the idea that all libraries ought to use it.
+See <a href="/philosophy/why-not-lgpl.html">Why you shouldn't use the
+Lesser GPL for your next library</a> for more information.</p>
+
+<h3>Scratching an itch?</h3>
+<p>
+Eric Raymond says that “Every good work of software starts by
+scratching a developer's personal itch.” Maybe that happens
+sometimes, but many essential pieces of GNU software were developed in
+order to have a complete free operating system. They come from a
+vision and a plan, not from impulse.</p>
+<p>
+For example, we developed the GNU C library because a Unix-like system
+needs a C library, BASH because a Unix-like
+system needs a shell, and GNU tar because a Unix-like system needs a
+tar program. The same is true for my own programs—the GNU C
+compiler, GNU Emacs, GDB and GNU Make.</p>
+<p>
+Some GNU programs were developed to cope with specific threats to our
+freedom. Thus, we developed gzip to replace the Compress program,
+which had been lost to the community because of
+the <acronym title="Lempel-Ziv-Welch">LZW</acronym> patents. We
found
+people to develop LessTif, and more recently started
+<acronym title="GNU Network Object Model
Environment">GNOME</acronym>
+and Harmony, to address the problems caused by certain proprietary
+libraries (see below). We are developing the GNU Privacy Guard to
+replace popular nonfree encryption software, because users should not
+have to choose between privacy and freedom.</p>
+<p>
+Of course, the people writing these programs became interested in the
+work, and many features were added to them by various people for the
+sake of their own needs and interests. But that is not why the
+programs exist.</p>
+
+<h3>Unexpected developments</h3>
+<p>
+At the beginning of the GNU Project, I imagined that we would develop
+the whole GNU system, then release it as a whole. That is not how it
+happened.</p>
+<p>
+Since each component of the GNU system was implemented on a Unix
+system, each component could run on Unix systems long before a
+complete GNU system existed. Some of these programs became popular,
+and users began extending them and porting them—to the various
+incompatible versions of Unix, and sometimes to other systems as
well.</p>
+<p>
+The process made these programs much more powerful, and attracted both
+funds and contributors to the GNU Project. But it probably also
+delayed completion of a minimal working system by several years, as
+GNU developers' time was put into maintaining these ports and adding
+features to the existing components, rather than moving on to write
+one missing component after another.</p>
+
+<h3>The GNU Hurd</h3>
+<p>
+By 1990, the GNU system was almost complete; the only major missing
+component was the kernel. We had decided to implement our kernel as a
+collection of server processes running on top of Mach. Mach is a
+microkernel developed at Carnegie Mellon University and then at the
+University of Utah; the GNU Hurd is a collection of servers (i.e., a
+herd of GNUs) that run on top of Mach, and do the
+various jobs of the Unix kernel. The start of development was delayed
+as we waited for Mach to be released as free software, as had been
+promised.</p>
+<p>
+One reason for choosing this design was to avoid what seemed to be the
+hardest part of the job: debugging a kernel program without a
+source-level debugger to do it with. This part of the job had been
+done already, in Mach, and we expected to debug the Hurd servers as
+user programs, with GDB. But it took a long time to make that possible,
+and the multithreaded servers that send messages to each other have
+turned out to be very hard to debug. Making the Hurd work solidly has
+stretched on for many years.</p>
+
+<h3>Alix</h3>
+<p>
+The GNU kernel was not originally supposed to be called the Hurd. Its
+original name was Alix—named after the woman who was my sweetheart at
+the time. She, a Unix system administrator, had pointed out how her
+name would fit a common naming pattern for Unix system versions; as a
+joke, she told her friends, “Someone should name a kernel after
+me.” I said nothing, but decided to surprise her with a kernel
+named Alix.</p>
+<p>
+It did not stay that way. Michael (now Thomas) Bushnell, the main
+developer of the kernel, preferred the name Hurd, and redefined Alix
+to refer to a certain part of the kernel—the part that would trap
+system calls and handle them by sending messages to Hurd servers.</p>
+<p>
+Later, Alix and I broke up, and she changed her name;
+independently, the Hurd design was changed so that the C library would
+send messages directly to servers, and this made the Alix component
+disappear from the design.</p>
+<p>
+But before these things happened, a friend of hers came across the
+name Alix in the Hurd source code, and mentioned it to her. So
+she did have the chance to find a kernel named after her.</p>
+
+<h3>Linux and GNU/Linux</h3>
+<p>
+The GNU Hurd is not suitable for production use, and we don't know
+if it ever will be. The capability-based design has problems that
+result directly from the flexibility of the design, and it is not
+clear whether solutions exist.</p>
+
+<p>
+Fortunately, another
+kernel is available. In 1991, Linus Torvalds developed a
+Unix-compatible kernel and called it Linux. In 1992, he made Linux
+free software; combining Linux with the not-quite-complete GNU system
+resulted in a complete free operating system. (Combining them was a
+substantial job in itself, of course.) It is due to Linux that we can
+actually run a version of the GNU system today.</p>
+<p>
+We call this system version GNU/Linux, to express its composition as a
+combination of the GNU system with Linux as the kernel.</p>
+
+<h3>Challenges in our future</h3>
+<p>
+We have proved our ability to develop a broad spectrum of free
+software. This does not mean we are invincible and unstoppable.
+Several challenges make the future of free software uncertain; meeting
+them will require steadfast effort and endurance, sometimes lasting
+for years. It will require the kind of determination that people
+display when they value their freedom and will not let anyone take it
+away.</p>
+<p>
+The following four sections discuss these challenges.</p>
+
+<h3>Secret hardware</h3>
+<p>
+Hardware manufacturers increasingly tend to keep hardware
+specifications secret. This makes it difficult to write free drivers
+so that Linux and XFree86 can support new hardware. We have complete
+free systems today, but we will not have them tomorrow if we cannot
+support tomorrow's computers.</p>
+<p>
+There are two ways to cope with this problem. Programmers can do
+reverse engineering to figure out how to support the hardware. The
+rest of us can choose the hardware that is supported by free software;
+as our numbers increase, secrecy of specifications will become a
+self-defeating policy.</p>
+<p>
+Reverse engineering is a big job; will we have programmers with
+sufficient determination to undertake it? Yes—if we have built up a
+strong feeling that free software is a matter of principle, and
+nonfree drivers are intolerable. And will large numbers of us spend
+extra money, or even a little extra time, so we can use free drivers?
+Yes, if the determination to have freedom is widespread.</p>
+<p>
+(2008 note: this issue extends to the BIOS as well.
+There is a free BIOS, coreboot; the problem is getting specs
+for machines so that coreboot can support them.)</p>
+
+<h3>Nonfree libraries</h3>
+<p>
+A nonfree library that runs on free operating systems acts as a trap
+for free software developers. The library's attractive features are
+the bait; if you use the library, you fall into the trap, because your
+program cannot usefully be part of a free operating system. (Strictly
+speaking, we could include your program, but it
+won't <em>run</em> with the library missing.) Even worse, if
+a program that uses the proprietary library becomes popular, it can
+lure other unsuspecting programmers into the trap.</p>
+<p>
+The first instance of this problem was the Motif toolkit, back in the
+80s. Although there were as yet no free operating systems, it was
+clear what problem Motif would cause for them later on. The GNU
+Project responded in two ways: by asking individual free software
+projects to support the free X Toolkit widgets as well as Motif, and
+by asking for someone to write a free replacement for Motif. The job
+took many years; LessTif, developed by the Hungry Programmers, became
+powerful enough to support most Motif applications only in 1997.</p>
+<p>
+Between 1996 and 1998, another nonfree
+<acronym title="Graphical User Interface">GUI</acronym> toolkit
+library, called Qt, was used in a substantial collection of free
+software, the desktop
+<acronym title="K Desktop Environment">KDE</acronym>.</p>
+<p>
+Free GNU/Linux systems were unable to use KDE, because we could not
+use the library. However, some commercial distributors of GNU/Linux
+systems who were not strict about sticking with free software added
+KDE to their systems—producing a system with more capabilities,
+but less freedom. The KDE group was actively encouraging more
+programmers to use Qt, and millions of new “Linux users”
+had never been exposed to the idea that there was a problem in this.
+The situation appeared grim.</p>
+<p>
+The free software community responded to the problem in two ways:
+GNOME and Harmony.</p>
+<p>
+GNOME, the GNU Network Object Model Environment, is GNU's desktop
+project. Started in 1997 by Miguel de Icaza, and developed with the
+support of Red Hat Software, GNOME set out to provide similar desktop
+facilities, but using free software exclusively. It has technical
+advantages as well, such as supporting a variety of languages, not
+just C++. But its main purpose was freedom: not to require the use of
+any nonfree software.</p>
+<p>
+Harmony is a compatible replacement library, designed to make it
+possible to run KDE software without using Qt.</p>
+<p>
+In November 1998, the developers of Qt announced a change of license
+which, when carried out, should make Qt free software. There is no
+way to be sure, but I think that this was partly due to the
+community's firm response to the problem that Qt posed when it was
+nonfree. (The new license is inconvenient and inequitable, so it
+remains desirable to avoid using Qt.)</p>
+<p>
+[Subsequent note: in September 2000, Qt was rereleased under the GNU GPL,
+which essentially solved this problem.]</p>
+<p>
+How will we respond to the next tempting nonfree library? Will the
+whole community understand the need to stay out of the trap? Or will
+many of us give up freedom for convenience, and produce a major
+problem? Our future depends on our philosophy.</p>
+
+<h3>Software patents</h3>
+<p>
+The worst threat we face comes from software patents, which can put
+algorithms and features off limits to free software for up to twenty
+years. The LZW compression algorithm patents were applied for in
+1983, and we still cannot release free software to produce proper
+compressed <acronym title="Graphics Interchange
Format">GIF</acronym>s.
+[As of 2009 they have expired.] In 1998, a free program to produce
+<acronym title="MPEG-1 Audio Layer 3">MP3</acronym> compressed
audio
+was removed from distribution under threat of a patent suit.</p>
+<p>
+There are ways to cope with patents: we can search for evidence that a
+patent is invalid, and we can look for alternative ways to do a job.
+But each of these methods works only sometimes; when both fail, a
+patent may force all free software to lack some feature that users
+want. What will we do when this happens?</p>
+<p>
+Those of us who value free software for freedom's sake will stay with
+free software anyway. We will manage to get work done without the
+patented features. But those who value free software because they
+expect it to be technically superior are likely to call it a failure
+when a patent holds it back. Thus, while it is useful to talk about
+the practical effectiveness of the “bazaar” model of
+development, and the reliability and power of some free software,
+we must not stop there. We must talk about freedom and principle.</p>
+
+<h3>Free documentation</h3>
+<p>
+The biggest deficiency in our free operating systems is not in the
+software—it is the lack of good free manuals that we can include in
+our systems. Documentation is an essential part of any software
+package; when an important free software package does not come with a
+good free manual, that is a major gap. We have many such gaps today.</p>
+<p>
+Free documentation, like free software, is a matter of freedom, not
+price. The criterion for a free manual is pretty much the same as for
+free software: it is a matter of giving all users certain freedoms.
+Redistribution (including commercial sale) must be permitted, online
+and on paper, so that the manual can accompany every copy of the
+program.</p>
+<p>
+Permission for modification is crucial too. As a general rule, I
+don't believe that it is essential for people to have permission to
+modify all sorts of articles and books. For example, I don't think
+you or I are obliged to give permission to modify articles like this
+one, which describe our actions and our views.</p>
+<p>
+But there is a particular reason why the freedom to modify is crucial
+for documentation for free software. When people exercise their right
+to modify the software, and add or change its features, if they are
+conscientious they will change the manual, too—so they can
+provide accurate and usable documentation with the modified program.
+A nonfree manual, which does not allow programmers to be conscientious
+and finish the job, does not fill our community's needs.</p>
+<p>
+Some kinds of limits on how modifications are done pose no problem.
+For example, requirements to preserve the original author's copyright
+notice, the distribution terms, or the list of authors, are OK. It is
+also no problem to require modified versions to include notice that
+they were modified, even to have entire sections that may not be
+deleted or changed, as long as these sections deal with nontechnical
+topics. These kinds of restrictions are not a problem because they
+don't stop the conscientious programmer from adapting the manual to
+fit the modified program. In other words, they don't block the free
+software community from making full use of the manual.</p>
+<p>
+However, it must be possible to modify all the <em>technical</em>
content of
+the manual, and then distribute the result in all the usual media,
+through all the usual channels; otherwise, the restrictions do
+obstruct the community, the manual is not free, and we need another
+manual.</p>
+<p>
+Will free software developers have the awareness and determination to
+produce a full spectrum of free manuals? Once again, our future
+depends on philosophy.</p>
+
+<h3>We must talk about freedom</h3>
+<p>
+Estimates today are that there are ten million users of GNU/Linux
+systems such as Debian GNU/Linux and Red Hat “Linux”.
+Free software has developed such practical advantages that users are
+flocking to it for purely practical reasons.</p>
+<p>
+The good consequences of this are evident: more interest in developing
+free software, more customers for free software businesses, and more
+ability to encourage companies to develop commercial free software
+instead of proprietary software products.</p>
+<p>
+But interest in the software is growing faster than awareness of the
+philosophy it is based on, and this leads to trouble. Our ability to
+meet the challenges and threats described above depends on the will to
+stand firm for freedom. To make sure our community has this will, we
+need to spread the idea to the new users as they come into the
+community.</p>
+<p>
+But we are failing to do so: the efforts to attract new users into our
+community are far outstripping the efforts to teach them the civics of
+our community. We need to do both, and we need to keep the two
+efforts in balance.</p>
+
+<h3>“Open Source”</h3>
+<p>
+Teaching new users about freedom became more difficult in 1998, when a
+part of the community decided to stop using the term “free
+software” and say “open source software”
+instead.</p>
+<p>
+Some who favored this term aimed to avoid the confusion of
+“free” with “gratis”—a valid goal. Others,
+however, aimed to set aside the spirit of principle that had motivated
+the free software movement and the GNU Project, and to appeal instead
+to executives and business users, many of whom hold an ideology that
+places profit above freedom, above community, above principle. Thus,
+the rhetoric of “open source” focuses on the potential to
+make high-quality, powerful software, but shuns the ideas of freedom,
+community, and principle.</p>
+<p>
+The “Linux” magazines are a clear example of this—they
+are filled with advertisements for proprietary software that works
+with GNU/Linux. When the next Motif or Qt appears, will these
+magazines warn programmers to stay away from it, or will they run ads
+for it?</p>
+<p>
+The support of business can contribute to the community in many ways;
+all else being equal, it is useful. But winning their support by
+speaking even less about freedom and principle can be disastrous; it
+makes the previous imbalance between outreach and civics education
+even worse.</p>
+<p>
+“Free software” and “open source” describe the
+same category of software, more or less, but say different things
+about the software, and about values. The GNU Project continues to
+use the term “free software”, to express the idea that
+freedom, not just technology, is important.</p>
+
+<h3>Try!</h3>
+<p>
+Yoda's aphorism (“There is no ‘try’”) sounds
+neat, but it doesn't work for me. I have done most of my work while
+anxious about whether I could do the job, and unsure that it would be
+enough to achieve the goal if I did. But I tried anyway, because
+there was no one but me between the enemy and my city. Surprising
+myself, I have sometimes succeeded.</p>
+<p>
+Sometimes I failed; some of my cities have fallen. Then I found
+another threatened city, and got ready for another battle. Over time,
+I've learned to look for threats and put myself between them and my
+city, calling on other hackers to come and join me.</p>
+<p>
+Nowadays, often I'm not the only one. It is a relief and a joy when I
+see a regiment of hackers digging in to hold the line, and I realize,
+this city may survive—for now. But the dangers are greater each
+year, and now Microsoft has explicitly targeted our community. We
+can't take the future of freedom for granted. Don't take it for
+granted! If you want to keep your freedom, you must be prepared to
+defend it.</p>
+
+
+<!-- If needed, change the copyright block at the bottom. In general, -->
+<!-- all pages on the GNU web server should have the section about -->
+<!-- verbatim copying. Please do NOT remove this without talking -->
+<!-- with the webmasters first. -->
+<!-- Please make sure the copyright date is consistent with the document
-->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>. There
are
+also <a href="/contact/">other ways to contact</a> the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden"><address@hidden></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010 Richard
Stallman
+<br />
+This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2012/09/19 00:28:09 $
+<!-- timestamp end -->
+</p>
+</div>
+
+
+</div>
+</body>
+</html>
+</pre></body></html>
Index: gnu/po/thegnuproject.cs-diff.html
===================================================================
RCS file: gnu/po/thegnuproject.cs-diff.html
diff -N gnu/po/thegnuproject.cs-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/po/thegnuproject.cs-diff.html 19 Sep 2012 00:28:09 -0000 1.1
@@ -0,0 +1,1060 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/gnu/thegnuproject.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+
+<title>About the GNU Project - GNU Project - Free Software Foundation
(FSF)</title>
+
+<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software,
Free Software Foundation, History" />
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+
+<h2>The GNU Project</h2>
+
+<!-- This document uses XHTML 1.0 Strict, but may be served as -->
+<!-- text/html. Please ensure that markup style considers -->
+<!-- appendex C of the XHTML 1.0 standard. See validator.w3.org. -->
+
+<!-- Please ensure links are consistent with Apache's MultiView. -->
+<!-- Change include statements to be consistent with the relevant -->
+<!-- language, where necessary. -->
+
+<p>
+by <a href="http://www.stallman.org/"><strong>Richard
Stallman</strong></a></p>
+<span class="inserted"><ins><em><blockquote></em></ins></span>
+<p>
+<span class="removed"><del><strong>the original version
was</strong></del></span>
+<span class="inserted"><ins><em>Originally</em></ins></span> published in the
book <span class="removed"><del><strong>“Open
Sources”</p></strong></del></span> <span
class="inserted"><ins><em><em>Open Sources</em>. Richard
+Stallman was <a href="/philosophy/open-source-misses-the-point.html">
+never a supporter of “open source”</a>, but contributed
+this article so that the ideas of the free software movement would not
+be entirely absent from that book.
+</p>
+</blockquote></em></ins></span>
+
+<h3>The first software-sharing community</h3>
+<p>
+When I started working at the
+<acronym title="Massachusetts Institute of
Technology">MIT</acronym>
+Artificial Intelligence Lab in 1971, I became part of a
+software-sharing community that had existed for many years. Sharing
+of software was not limited to our particular community; it is as old
+as computers, just as sharing of recipes is as old as cooking. But we
+did it more than most.</p>
+<p>
+The AI Lab used a timesharing operating system called
+<acronym title="Incompatible Timesharing System">ITS</acronym> (the
+Incompatible Timesharing System) that the lab's staff hackers (1) had
+designed and written in assembler language for the Digital
+<acronym title="Programmed Data Processor">PDP</acronym>-10, one of
+the large computers of the era. As a member of this community, an AI
+Lab staff system hacker, my job was to improve this system.</p>
+<p>
+We did not call our software “free software”, because that
+term did not yet exist; but that is what it was. Whenever people from
+another university or a company wanted to port and use a program, we
+gladly let them. If you saw someone using an unfamiliar and
+interesting program, you could always ask to see the source code, so
+that you could read it, change it, or cannibalize parts of it to make
+a new program.</p>
+<p>
+(1) The use of “hacker” to mean “security
+breaker” is a confusion on the part of the mass media. We
+hackers refuse to recognize that meaning, and continue using the word
+to mean someone who loves to program, someone who enjoys playful
+cleverness, or the combination of the two. See my
+article, <a href="http://stallman.org/articles/on-hacking.html">On
+Hacking</a>.</p>
+
+<h3>The collapse of the community</h3>
+<p>
+The situation changed drastically in the early 1980s when Digital
+discontinued the PDP-10 series. Its architecture, elegant and
+powerful in the 60s, could not extend naturally to the larger address
+spaces that were becoming feasible in the 80s. This meant that nearly
+all of the programs composing ITS were obsolete.</p>
+<p>
+The AI Lab hacker community had already collapsed, not long before.
+In 1981, the spin-off company Symbolics had hired away nearly all of
+the hackers from the AI Lab, and the depopulated community was unable
+to maintain itself. (The book Hackers, by Steve Levy, describes these
+events, as well as giving a clear picture of this community in its
+prime.) When the AI Lab bought a new PDP-10 in 1982, its
+administrators decided to use Digital's nonfree timesharing system
+instead of ITS.</p>
+<p>
+The modern computers of the era, such as the VAX or the 68020, had
+their own operating systems, but none of them were free software: you
+had to sign a nondisclosure agreement even to get an executable copy.</p>
+<p>
+This meant that the first step in using a computer was to promise not
+to help your neighbor. A cooperating community was forbidden. The
+rule made by the owners of proprietary software was, “If you
+share with your neighbor, you are a pirate. If you want any changes,
+beg us to make them.”</p>
+<p>
+The idea that the proprietary software social system—the system
+that says you are not allowed to share or change software—is
+antisocial, that it is unethical, that it is simply wrong, may come as
+a surprise to some readers. But what else could we say about a system
+based on dividing the public and keeping users helpless? Readers who
+find the idea surprising may have taken the proprietary software
+social system as a given, or judged it on the terms suggested by
+proprietary software businesses. Software publishers have worked long
+and hard to convince people that there is only one way to look at the
+issue.</p>
+<p>
+When software publishers talk about “enforcing” their
+“rights” or “stopping <a
href="/philosophy/words-to-avoid.html#Piracy">piracy</a>”, what
they
+actually <em>say</em> is secondary. The real message of these
statements is
+in the unstated assumptions they take for granted, which the public is
+asked to accept without examination. Let's therefore examine them.</p>
+<p>
+One assumption is that software companies have an unquestionable natural
+right to own software and thus have power over all its users. (If
+this were a natural right, then no matter how much harm it does to the
+public, we could not object.) Interestingly, the US Constitution and
+legal tradition reject this view; copyright is not a natural right,
+but an artificial government-imposed monopoly that limits the users'
+natural right to copy.</p>
+<p>
+Another unstated assumption is that the only important thing about
+software is what jobs it allows you to do—that we computer users
+should not care what kind of society we are allowed to have.</p>
+<p>
+A third assumption is that we would have no usable software (or would
+never have a program to do this or that particular job) if we did not
+offer a company power over the users of the program. This assumption
+may have seemed plausible, before the free software movement
+demonstrated that we can make plenty of useful software without
+putting chains on it.</p>
+<p>
+If we decline to accept these assumptions, and judge these issues
+based on ordinary commonsense morality while placing the users first,
+we arrive at very different conclusions. Computer users should be
+free to modify programs to fit their needs, and free to share
+software, because helping other people is the basis of society.</p>
+<p>
+There is no room here for an extensive statement of the reasoning
+behind this conclusion, so I refer the reader to the web page,
+<a href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a>.</p>
+
+<h3>A stark moral <span
class="removed"><del><strong>choice.</h3></strong></del></span> <span
class="inserted"><ins><em>choice</h3></em></ins></span>
+<p>
+With my community gone, to continue as before was impossible.
+Instead, I faced a stark moral choice.</p>
+<p>
+The easy choice was to join the proprietary software world, signing
+nondisclosure agreements and promising not to help my fellow hacker.
+Most likely I would also be developing software that was released
+under nondisclosure agreements, thus adding to the pressure on other
+people to betray their fellows too.</p>
+<p>
+I could have made money this way, and perhaps amused myself writing
+code. But I knew that at the end of my career, I would look back on
+years of building walls to divide people, and feel I had spent my life
+making the world a worse place.</p>
+<p>
+I had already experienced being on the receiving end of a
+nondisclosure agreement, when someone refused to give me and the MIT
+AI Lab the source code for the control program for our printer. (The
+lack of certain features in this program made use of the printer
+extremely frustrating.) So I could not tell myself that nondisclosure
+agreements were innocent. I was very angry when he refused to share
+with us; I could not turn around and do the same thing to everyone
+else.</p>
+<p>
+Another choice, straightforward but unpleasant, was to leave the
+computer field. That way my skills would not be misused, but they
+would still be wasted. I would not be culpable for dividing and
+restricting computer users, but it would happen nonetheless.</p>
+<p>
+So I looked for a way that a programmer could do something for the
+good. I asked myself, was there a program or programs that I could
+write, so as to make a community possible once again?</p>
+<p>
+The answer was clear: what was needed first was an operating system.
+That is the crucial software for starting to use a computer. With an
+operating system, you can do many things; without one, you cannot run
+the computer at all. With a free operating system, we could again
+have a community of cooperating hackers—and invite anyone to join.
+And anyone would be able to use a computer without starting out by
+conspiring to deprive his or her friends.</p>
+<p>
+As an operating system developer, I had the right skills for this job.
+So even though I could not take success for granted, I realized that I
+was elected to do the job. I chose to make the system compatible with
+Unix so that it would be portable, and so that Unix users could easily
+switch to it. The name GNU was chosen, following a hacker tradition, as
+a recursive acronym for “GNU's Not Unix.”</p>
+<p>
+An operating system does not mean just a kernel, barely enough to run
+other programs. In the 1970s, every operating system worthy of the
+name included command processors, assemblers, compilers, interpreters,
+debuggers, text editors, mailers, and much more. ITS had them,
+Multics had them, VMS had them, and Unix had them. The GNU operating
+system would include them too.</p>
+<p>
+Later I heard these words, attributed to Hillel (1):</p>
+
+<blockquote><p>
+ If I am not for myself, who will be for me?<br />
+ If I am only for myself, what am I?<br />
+ If not now, when?
+</p></blockquote>
+<p>
+The decision to start the GNU Project was based on a similar spirit.</p>
+<p>
+(1) As an Atheist, I don't follow any religious leaders, but I
+sometimes find I admire something one of them has said.</p>
+
+<h3>Free as in freedom</h3>
+<p>
+The term “free software” is sometimes misunderstood—it
+has nothing to do with price. It is about freedom. Here, therefore,
+is the definition of free software.</p>
+
+<p>A program is free software, for you, a particular user, if:</p>
+
+<ul>
+ <li>You have the freedom to run the program as you wish, for any
purpose.</li>
+
+ <li>You have the freedom to modify the program to suit your needs.
+ (To make this freedom effective in practice, you must have access
+ to the source code, since making changes in a program without
+ having the source code is exceedingly difficult.)</li>
+
+ <li>You have the freedom to redistribute copies, either gratis
+ or for a fee.</li>
+
+ <li>You have the freedom to distribute modified versions of the
program,
+ so that the community can benefit from your improvements.</li>
+</ul>
+<p>
+Since “free” refers to freedom, not to price, there is no
+contradiction between selling copies and free software. In fact, the
+freedom to sell copies is crucial: collections of free software sold
+on CD-ROMs are important for the community, and selling them is an
+important way to raise funds for free software development.
+Therefore, a program which people are not free to include on these
+collections is not free software.</p>
+<p>
+Because of the ambiguity of “free”, people have long
+looked for alternatives, but no one has found a better term.
+The English language has more words and nuances than any other, but it
+lacks a simple, unambiguous, word that means “free”, as in
+freedom—“unfettered” being the word that comes closest in
+meaning. Such alternatives as “liberated”,
+“freedom”, and “open” have either the wrong
+meaning or some other disadvantage.</p>
+
+<h3>GNU software and the GNU system</h3>
+<p>
+Developing a whole system is a very large project. To bring it into
+reach, I decided to adapt and use existing pieces of free software
+wherever that was possible. For example, I decided at the very
+beginning to use TeX as the principal text formatter; a few years
+later, I decided to use the X Window System rather than writing
+another window system for GNU.</p>
+<p>
+Because of <span class="removed"><del><strong>this
decision,</strong></del></span> <span class="inserted"><ins><em>these
decisions, and others like them,</em></ins></span>
+the GNU system is not the same as the collection of all
+GNU software. The GNU system includes programs that are not GNU
+software, programs that were developed by other people and projects
+for their own purposes, but which we can use because they are free
+software.</p>
+
+<h3>Commencing the project</h3>
+<p>
+In January 1984 I quit my job at MIT and began writing GNU software.
+Leaving MIT was necessary so that MIT would not be able to interfere
+with distributing GNU as free software. If I had remained on the
+staff, MIT could have claimed to own the work, and could have imposed
+their own distribution terms, or even turned the work into a
+proprietary software package. I had no intention of doing a large
+amount of work only to see it become useless for its intended purpose:
+creating a new software-sharing community.</p>
+<p>
+However, Professor Winston, then the head of the MIT AI Lab, kindly
+invited me to keep using the lab's facilities.</p>
+
+<h3>The first steps</h3>
+<p>
+Shortly before beginning the GNU Project, I heard about the Free
+University Compiler Kit, also known as VUCK. (The Dutch word for
+“free” is written with a <em>v</em>.) This was a
compiler
+designed to handle multiple languages, including C and Pascal, and to
+support multiple target machines. I wrote to its author asking if GNU
+could use it.</p>
+<p>
+He responded derisively, stating that the university was free but the
+compiler was not. I therefore decided that my first program for the
+GNU Project would be a multilanguage, multiplatform compiler.</p>
+<p>
+Hoping to avoid the need to write the whole compiler myself, I
+obtained the source code for the Pastel compiler, which was a
+multiplatform compiler developed at Lawrence Livermore Lab. It
+supported, and was written in, an extended version of Pascal, designed
+to be a system-programming language. I added a C front end, and began
+porting it to the Motorola 68000 computer. But I had to give that
+up when I discovered that the compiler needed many megabytes of stack
+space, and the available 68000 Unix system would only allow 64k.</p>
+<p>
+I then realized that the Pastel compiler functioned by parsing the
+entire input file into a syntax tree, converting the whole syntax tree
+into a chain of “instructions”, and then generating the
+whole output file, without ever freeing any storage. At this point, I
+concluded I would have to write a new compiler from scratch. That new
+compiler is now known as <acronym title="GNU Compiler
Collection">GCC</acronym>;
+none of the Pastel compiler is used in it, but I managed to adapt and
+use the C front end that I had written. But that was some years
+later; first, I worked on GNU Emacs.</p>
+
+<h3>GNU Emacs</h3>
+<p>
+I began work on GNU Emacs in September 1984, and in early 1985 it was
+beginning to be usable. This enabled me to begin using Unix systems
+to do editing; having no interest in learning to use vi or ed, I had
+done my editing on other kinds of machines until then.</p>
+<p>
+At this point, people began wanting to use GNU Emacs, which raised the
+question of how to distribute it. Of course, I put it on the
+anonymous ftp server on the MIT computer that I used. (This computer,
+prep.ai.mit.edu, thus became the principal GNU ftp distribution site;
+when it was decommissioned a few years later, we transferred the name
+to our new ftp server.) But at that time, many of the interested
+people were not on the Internet and could not get a copy by ftp. So
+the question was, what would I say to them?</p>
+<p>
+I could have said, “Find a friend who is on the net and who will make
+a copy for you.” Or I could have done what I did with the original
+PDP-10 Emacs: tell them, “Mail me a tape and a
+<acronym title="Self-addressed Stamped Envelope">SASE</acronym>,
and I
+will mail it back with Emacs on it.” But I had no job, and I was
+looking for ways to make money from free software. So I announced
+that I would mail a tape to whoever wanted one, for a fee of $150. In
+this way, I started a free software distribution business, the
+precursor of the companies that today distribute entire Linux-based
+GNU systems.</p>
+
+<h3>Is a program free for every user?</h3>
+<p>
+If a program is free software when it leaves the hands of its author,
+this does not necessarily mean it will be free software for everyone
+who has a copy of it. For example,
+<a href="/philosophy/categories.html#PublicDomainSoftware"> public domain
+software</a> (software that is not copyrighted) is free software; but
+anyone can make a proprietary modified version of it. Likewise, many
+free programs are copyrighted but distributed under simple permissive
+licenses which allow proprietary modified versions.</p>
+<p>
+The paradigmatic example of this problem is the X Window System.
+Developed at MIT, and released as free software with a permissive
+license, it was soon adopted by various computer companies. They
+added X to their proprietary Unix systems, in binary form only, and
+covered by the same nondisclosure agreement. These copies of X were
+no more free software than Unix was.</p>
+<p>
+The developers of the X Window System did not consider this a
+problem—they expected and intended this to happen. Their goal was
+not freedom, just “success”, defined as “having many
+users.” They did not care whether these users had freedom, only
+that they should be numerous.</p>
+<p>
+This led to a paradoxical situation where two different ways of
+counting the amount of freedom gave different answers to the question,
+“Is this program free?” If you judged based on the freedom
+provided by the distribution terms of the MIT release, you would say
+that X was free software. But if you measured the freedom of the
+average user of X, you would have to say it was proprietary software.
+Most X users were running the proprietary versions that came with Unix
+systems, not the free version.</p>
+
+<h3>Copyleft and the GNU GPL</h3>
+<p>
+The goal of GNU was to give users freedom, not just to be popular. So
+we needed to use distribution terms that would prevent GNU software
+from being turned into proprietary software. The method we use is
+called “copyleft”.(1)</p>
+<p>
+Copyleft uses copyright law, but flips it over to serve the opposite
+of its usual purpose: instead of a means for restricting a program, it
+becomes a means for keeping the program free.</p>
+<p>
+The central idea of copyleft is that we give everyone permission to
+run the program, copy the program, modify the program, and distribute
+modified versions—but not permission to add restrictions of their
+own. Thus, the crucial freedoms that define “free
+software” are guaranteed to everyone who has a copy; they become
+inalienable rights.</p>
+<p>
+For an effective copyleft, modified versions must also be free. This
+ensures that work based on ours becomes available to our community if
+it is published. When programmers who have jobs as programmers
+volunteer to improve GNU software, it is copyleft that prevents their
+employers from saying, “You can't share those changes, because
+we are going to use them to make our proprietary version of the
+program.”</p>
+<p>
+The requirement that changes must be free is essential if we want to
+ensure freedom for every user of the program. The companies that
+privatized the X Window System usually made some changes to port it to
+their systems and hardware. These changes were small compared with
+the great extent of X, but they were not trivial. If making changes
+were an excuse to deny the users freedom, it would be easy for anyone
+to take advantage of the excuse.</p>
+<p>
+A related issue concerns combining a free program with nonfree code.
+Such a combination would inevitably be nonfree; whichever freedoms
+are lacking for the nonfree part would be lacking for the whole as
+well. To permit such combinations would open a hole big enough to
+sink a ship. Therefore, a crucial requirement for copyleft is to plug
+this hole: anything added to or combined with a copylefted program
+must be such that the larger combined version is also free and
+copylefted.</p>
+<p>
+The specific implementation of copyleft that we use for most GNU
+software is the GNU General Public License, or GNU GPL for short. We
+have other kinds of copyleft that are used in specific circumstances.
+GNU manuals are copylefted also, but use a much simpler kind of
+copyleft, because the complexity of the GNU GPL is not necessary
+for manuals.(2)</p>
+<p>
+(1) In 1984 or 1985, Don Hopkins (a very imaginative fellow) mailed me
+a letter. On the envelope he had written several amusing sayings,
+including this one: “Copyleft—all rights reversed.” I
+used the word “copyleft” to name the distribution concept
+I was developing at the time.</p>
+
+<p>
+(2) We now use the <a href="/licenses/fdl.html">GNU Free
+Documentation License</a> for documentation.</p>
+
+<h3>The Free Software Foundation</h3>
+
+<p>As interest in using Emacs was growing, other people became
+involved in the GNU project, and we decided that it was time to seek
+funding once again. So in 1985 we created
+the <a href="http://www.fsf.org/">Free Software Foundation</a>
(FSF),
+a tax-exempt charity for free software development. The
+<acronym title="Free Software Foundation">FSF</acronym> also took
over
+the Emacs tape distribution business; later it extended this by adding
+other free software (both GNU and non-GNU) to the tape, and by selling
+free manuals as well.</p>
+
+<p>Most of the FSF's income used to come from sales of copies of free
+software and of other related services (CD-ROMs of source code,
+CD-ROMs with binaries, nicely printed manuals, all with the freedom to
+redistribute and modify), and Deluxe Distributions (distributions for
+which we built the whole collection of software for the customer's
+choice of platform). Today the FSF
+still <a href="http://shop.fsf.org/"> sells manuals and other
+gear</a>, but it gets the bulk of its funding from members' dues. You
+can join the FSF at <a
href="http://fsf.org/join">fsf.org</a>.</p>
+
+<p>Free Software Foundation employees have written and maintained a
+number of GNU software packages. Two notable ones are the C library
+and the shell. The GNU C library is what every program running on a
+GNU/Linux system uses to communicate with Linux. It was developed by
+a member of the Free Software Foundation staff, Roland McGrath. The
+shell used on most GNU/Linux systems is
+<acronym title="Bourne Again Shell">BASH</acronym>, the Bourne
Again
+Shell(1), which was developed by FSF employee Brian Fox.</p>
+
+<p>We funded development of these programs because the GNU Project was
+not just about tools or a development environment. Our goal was a
+complete operating system, and these programs were needed for that
+goal.</p>
+
+<p>(1) “Bourne Again Shell” is a play on the name
+“Bourne Shell”, which was the usual shell on Unix.</p>
+
+<h3>Free software support</h3>
+
+<p>The free software philosophy rejects a specific widespread business
+practice, but it is not against business. When businesses respect the
+users' freedom, we wish them success.</p>
+
+<p>Selling copies of Emacs demonstrates one kind of free software
+business. When the FSF took over that business, I needed another way
+to make a living. I found it in selling services relating to the free
+software I had developed. This included teaching, for subjects such
+as how to program GNU Emacs and how to customize GCC, and software
+development, mostly porting GCC to new platforms.</p>
+
+<p>Today each of these kinds of free software business is practiced by a
+number of corporations. Some distribute free software collections on
+CD-ROM; others sell support at levels ranging from answering user
+questions, to fixing bugs, to adding major new features. We are even
+beginning to see free software companies based on launching new free
+software products.</p>
+
+<p>Watch out, though—a number of companies that associate
themselves
+with the term “open source” actually base their business
+on nonfree software that works with free software. These are not
+free software companies, they are proprietary software companies whose
+products tempt users away from freedom. They call these programs
+“value-added packages”, which shows the values they
+would like us to adopt: convenience above freedom. If we value freedom
+more, we should call them “freedom-subtracted” packages.</p>
+
+<h3>Technical goals</h3>
+
+<p>The principal goal of GNU is to be free software. Even if GNU had no
+technical advantage over Unix, it would have a social advantage,
+allowing users to cooperate, and an ethical advantage, respecting the
+user's freedom.</p>
+
+<p>But it was natural to apply the known standards of good practice to
+the work—for example, dynamically allocating data structures to avoid
+arbitrary fixed size limits, and handling all the possible 8-bit codes
+wherever that made sense.</p>
+
+<p>In addition, we rejected the Unix focus on small memory size, by
+deciding not to support 16-bit machines (it was clear that 32-bit
+machines would be the norm by the time the GNU system was finished),
+and to make no effort to reduce memory usage unless it exceeded a
+megabyte. In programs for which handling very large files was not
+crucial, we encouraged programmers to read an entire input file into
+core, then scan its contents without having to worry about I/O.</p>
+
+<p>These decisions enabled many GNU programs to surpass their Unix
+counterparts in reliability and speed.</p>
+
+<h3>Donated computers</h3>
+
+<p>As the GNU Project's reputation grew, people began offering to donate
+machines running Unix to the project. These were very useful, because
+the easiest way to develop components of GNU was to do it on a Unix
+system, and replace the components of that system one by one. But
+they raised an ethical issue: whether it was right for us to have a
+copy of Unix at all.</p>
+
+<p>Unix was (and is) proprietary software, and the GNU Project's
+philosophy said that we should not use proprietary software. But,
+applying the same reasoning that leads to the conclusion that violence
+in self defense is justified, I concluded that it was legitimate to
+use a proprietary package when that was crucial for developing a free
+replacement that would help others stop using the proprietary
package.</p>
+
+<p>But, even if this was a justifiable evil, it was still an evil. Today
+we no longer have any copies of Unix, because we have replaced them
+with free operating systems. If we could not replace a machine's
+operating system with a free one, we replaced the machine instead.</p>
+
+<h3>The GNU Task List</h3>
+
+<p>As the GNU Project proceeded, and increasing numbers of system
+components were found or developed, eventually it became useful to
+make a list of the remaining gaps. We used it to recruit developers
+to write the missing pieces. This list became known as the GNU Task
+List. In addition to missing Unix components, we listed various
+other useful software and documentation projects that, we thought, a
+truly complete system ought to have.</p>
+
+<p>Today (1), hardly any Unix components are left in the GNU Task
+List—those jobs had been done, aside from a few inessential
+ones. But the list is full of projects that some might call
+“applications”. Any program that appeals to more than a
+narrow class of users would be a useful thing to add to an operating
+system.</p>
+
+<p>Even games are included in the task list—and have been since the
+beginning. Unix included games, so naturally GNU should too. But
+compatibility was not an issue for games, so we did not follow the
+list of games that Unix had. Instead, we listed a spectrum of
+different kinds of games that users might like.</p>
+
+<p>(1) That was written in 1998. In 2009 we no longer maintain a long
+task list. The community develops free software so fast that we can't
+even keep track of it all. Instead, we have a list of High Priority
+Projects, a much shorter list of projects we really want to encourage
+people to write.</p>
+
+<h3>The GNU Library GPL</h3>
+
+<p>The GNU C library uses a special kind of copyleft called the GNU
+Library General Public License(1), which gives permission to link
+proprietary software with the library. Why make this exception?</p>
+
+<p>It is not a matter of principle; there is no principle that says
+proprietary software products are entitled to include our code. (Why
+contribute to a project predicated on refusing to share with us?)
+Using the LGPL for the C library, or for any library, is a matter of
+strategy.</p>
+
+<p>The C library does a generic job; every proprietary system or compiler
+comes with a C library. Therefore, to make our C library available
+only to free software would not have given free software any
+advantage—it would only have discouraged use of our library.</p>
+
+<p>One system is an exception to this: on the GNU system (and this
+includes GNU/Linux), the GNU C library is the only C library. So the
+distribution terms of the GNU C library determine whether it is
+possible to compile a proprietary program for the GNU system. There
+is no ethical reason to allow proprietary applications on the GNU
+system, but strategically it seems that disallowing them would do more
+to discourage use of the GNU system than to encourage development of
+free applications. That is why using the Library GPL is a good
+strategy for the C library.</p>
+
+<p>For other libraries, the strategic decision needs to be
+considered on a case-by-case basis. When a library does a special job
+that can help write certain kinds of programs, then releasing it under
+the GPL, limiting it to free programs only, is a way of helping other
+free software developers, giving them an advantage against proprietary
+software.</p>
+
+<p>Consider GNU Readline, a library that was developed to provide
+command-line editing for BASH. Readline is released under the
+ordinary GNU GPL, not the Library GPL. This probably does reduce the
+amount Readline is used, but that is no loss for us. Meanwhile, at
+least one useful application has been made free software specifically
+so it could use Readline, and that is a real gain for the
+community.</p>
+
+<p>Proprietary software developers have the advantages money provides;
+free software developers need to make advantages for each other. I
+hope some day we will have a large collection of GPL-covered libraries
+that have no parallel available to proprietary software, providing
+useful modules to serve as building blocks in new free software, and
+adding up to a major advantage for further free software development.</p>
+
+<p>(1) This license is now called the GNU Lesser General Public License,
+to avoid giving the idea that all libraries ought to use it.
+See <a href="/philosophy/why-not-lgpl.html">Why you shouldn't use the
+Lesser GPL for your next library</a> for more information.</p>
+
+<h3>Scratching an itch?</h3>
+<p>
+Eric Raymond says that “Every good work of software starts by
+scratching a developer's personal itch.” Maybe that happens
+sometimes, but many essential pieces of GNU software were developed in
+order to have a complete free operating system. They come from a
+vision and a plan, not from impulse.</p>
+<p>
+For example, we developed the GNU C library because a Unix-like system
+needs a C library, BASH because a Unix-like
+system needs a shell, and GNU tar because a Unix-like system needs a
+tar program. The same is true for my own programs—the GNU C
+compiler, GNU Emacs, GDB and GNU Make.</p>
+<p>
+Some GNU programs were developed to cope with specific threats to our
+freedom. Thus, we developed gzip to replace the Compress program,
+which had been lost to the community because of
+the <acronym title="Lempel-Ziv-Welch">LZW</acronym> patents. We
found
+people to develop LessTif, and more recently started
+<acronym title="GNU Network Object Model
Environment">GNOME</acronym>
+and Harmony, to address the problems caused by certain proprietary
+libraries (see below). We are developing the GNU Privacy Guard to
+replace popular nonfree encryption software, because users should not
+have to choose between privacy and freedom.</p>
+<p>
+Of course, the people writing these programs became interested in the
+work, and many features were added to them by various people for the
+sake of their own needs and interests. But that is not why the
+programs exist.</p>
+
+<h3>Unexpected developments</h3>
+<p>
+At the beginning of the GNU Project, I imagined that we would develop
+the whole GNU system, then release it as a whole. That is not how it
+happened.</p>
+<p>
+Since each component of the GNU system was implemented on a Unix
+system, each component could run on Unix systems long before a
+complete GNU system existed. Some of these programs became popular,
+and users began extending them and porting them—to the various
+incompatible versions of Unix, and sometimes to other systems as
well.</p>
+<p>
+The process made these programs much more powerful, and attracted both
+funds and contributors to the GNU Project. But it probably also
+delayed completion of a minimal working system by several years, as
+GNU developers' time was put into maintaining these ports and adding
+features to the existing components, rather than moving on to write
+one missing component after another.</p>
+
+<h3>The GNU Hurd</h3>
+<p>
+By 1990, the GNU system was almost complete; the only major missing
+component was the kernel. We had decided to implement our kernel as a
+collection of server processes running on top of Mach. Mach is a
+microkernel developed at Carnegie Mellon University and then at the
+University of Utah; the GNU Hurd is a collection of servers (i.e., a
+herd of GNUs) that run on top of Mach, and do the
+various jobs of the Unix kernel. The start of development was delayed
+as we waited for Mach to be released as free software, as had been
+promised.</p>
+<p>
+One reason for choosing this design was to avoid what seemed to be the
+hardest part of the job: debugging a kernel program without a
+source-level debugger to do it with. This part of the job had been
+done already, in Mach, and we expected to debug the Hurd servers as
+user programs, with GDB. But it took a long time to make that possible,
+and the multithreaded servers that send messages to each other have
+turned out to be very hard to debug. Making the Hurd work solidly has
+stretched on for many years.</p>
+
+<h3>Alix</h3>
+<p>
+The GNU kernel was not originally supposed to be called the Hurd. Its
+original name was Alix—named after the woman who was my sweetheart at
+the time. She, a Unix system administrator, had pointed out how her
+name would fit a common naming pattern for Unix system versions; as a
+joke, she told her friends, “Someone should name a kernel after
+me.” I said nothing, but decided to surprise her with a kernel
+named Alix.</p>
+<p>
+It did not stay that way. Michael (now Thomas) Bushnell, the main
+developer of the kernel, preferred the name Hurd, and redefined Alix
+to refer to a certain part of the kernel—the part that would trap
+system calls and handle them by sending messages to Hurd servers.</p>
+<p>
+Later, Alix and I broke up, and she changed her name;
+independently, the Hurd design was changed so that the C library would
+send messages directly to servers, and this made the Alix component
+disappear from the design.</p>
+<p>
+But before these things happened, a friend of hers came across the
+name Alix in the Hurd source code, and mentioned it to her. So
+she did have the chance to find a kernel named after her.</p>
+
+<h3>Linux and GNU/Linux</h3>
+<p>
+The GNU Hurd is not suitable for production use, and we don't know
+if it ever will be. The capability-based design has problems that
+result directly from the flexibility of the design, and it is not
+clear whether solutions exist.</p>
+
+<p>
+Fortunately, another
+kernel is available. In 1991, Linus Torvalds developed a
+Unix-compatible kernel and called it Linux. In 1992, he made Linux
+free software; combining Linux with the not-quite-complete GNU system
+resulted in a complete free operating system. (Combining them was a
+substantial job in itself, of course.) It is due to Linux that we can
+actually run a version of the GNU system today.</p>
+<p>
+We call this system version GNU/Linux, to express its composition as a
+combination of the GNU system with Linux as the kernel.</p>
+
+<h3>Challenges in our future</h3>
+<p>
+We have proved our ability to develop a broad spectrum of free
+software. This does not mean we are invincible and unstoppable.
+Several challenges make the future of free software uncertain; meeting
+them will require steadfast effort and endurance, sometimes lasting
+for years. It will require the kind of determination that people
+display when they value their freedom and will not let anyone take it
+away.</p>
+<p>
+The following four sections discuss these challenges.</p>
+
+<h3>Secret hardware</h3>
+<p>
+Hardware manufacturers increasingly tend to keep hardware
+specifications secret. This makes it difficult to write free drivers
+so that Linux and XFree86 can support new hardware. We have complete
+free systems today, but we will not have them tomorrow if we cannot
+support tomorrow's computers.</p>
+<p>
+There are two ways to cope with this problem. Programmers can do
+reverse engineering to figure out how to support the hardware. The
+rest of us can choose the hardware that is supported by free software;
+as our numbers increase, secrecy of specifications will become a
+self-defeating policy.</p>
+<p>
+Reverse engineering is a big job; will we have programmers with
+sufficient determination to undertake it? Yes—if we have built up a
+strong feeling that free software is a matter of principle, and
+nonfree drivers are intolerable. And will large numbers of us spend
+extra money, or even a little extra time, so we can use free drivers?
+Yes, if the determination to have freedom is widespread.</p>
+<p>
+(2008 note: this issue extends to the BIOS as well.
+There is a free BIOS, coreboot; the problem is getting specs
+for machines so that coreboot can support them.)</p>
+
+<h3>Nonfree libraries</h3>
+<p>
+A nonfree library that runs on free operating systems acts as a trap
+for free software developers. The library's attractive features are
+the bait; if you use the library, you fall into the trap, because your
+program cannot usefully be part of a free operating system. (Strictly
+speaking, we could include your program, but it
+won't <em>run</em> with the library missing.) Even worse, if
+a program that uses the proprietary library becomes popular, it can
+lure other unsuspecting programmers into the trap.</p>
+<p>
+The first instance of this problem was the Motif toolkit, back in the
+80s. Although there were as yet no free operating systems, it was
+clear what problem Motif would cause for them later on. The GNU
+Project responded in two ways: by asking individual free software
+projects to support the free X Toolkit widgets as well as Motif, and
+by asking for someone to write a free replacement for Motif. The job
+took many years; LessTif, developed by the Hungry Programmers, became
+powerful enough to support most Motif applications only in 1997.</p>
+<p>
+Between 1996 and 1998, another nonfree
+<acronym title="Graphical User Interface">GUI</acronym> toolkit
+library, called Qt, was used in a substantial collection of free
+software, the desktop
+<acronym title="K Desktop Environment">KDE</acronym>.</p>
+<p>
+Free GNU/Linux systems were unable to use KDE, because we could not
+use the library. However, some commercial distributors of GNU/Linux
+systems who were not strict about sticking with free software added
+KDE to their systems—producing a system with more capabilities,
+but less freedom. The KDE group was actively encouraging more
+programmers to use Qt, and millions of new “Linux users”
+had never been exposed to the idea that there was a problem in this.
+The situation appeared grim.</p>
+<p>
+The free software community responded to the problem in two ways:
+GNOME and Harmony.</p>
+<p>
+GNOME, the GNU Network Object Model Environment, is GNU's desktop
+project. Started in 1997 by Miguel de Icaza, and developed with the
+support of Red Hat Software, GNOME set out to provide similar desktop
+facilities, but using free software exclusively. It has technical
+advantages as well, such as supporting a variety of languages, not
+just C++. But its main purpose was freedom: not to require the use of
+any nonfree software.</p>
+<p>
+Harmony is a compatible replacement library, designed to make it
+possible to run KDE software without using Qt.</p>
+<p>
+In November 1998, the developers of Qt announced a change of license
+which, when carried out, should make Qt free software. There is no
+way to be sure, but I think that this was partly due to the
+community's firm response to the problem that Qt posed when it was
+nonfree. (The new license is inconvenient and inequitable, so it
+remains desirable to avoid using Qt.)</p>
+<p>
+[Subsequent note: in September 2000, Qt was rereleased under the GNU GPL,
+which essentially solved this problem.]</p>
+<p>
+How will we respond to the next tempting nonfree library? Will the
+whole community understand the need to stay out of the trap? Or will
+many of us give up freedom for convenience, and produce a major
+problem? Our future depends on our philosophy.</p>
+
+<h3>Software patents</h3>
+<p>
+The worst threat we face comes from software patents, which can put
+algorithms and features off limits to free software for up to twenty
+years. The LZW compression algorithm patents were applied for in
+1983, and we still cannot release free software to produce proper
+compressed <acronym title="Graphics Interchange
Format">GIF</acronym>s.
+[As of 2009 they have expired.] In 1998, a free program to produce
+<acronym title="MPEG-1 Audio Layer 3">MP3</acronym> compressed
audio
+was removed from distribution under threat of a patent suit.</p>
+<p>
+There are ways to cope with patents: we can search for evidence that a
+patent is invalid, and we can look for alternative ways to do a job.
+But each of these methods works only sometimes; when both fail, a
+patent may force all free software to lack some feature that users
+want. What will we do when this happens?</p>
+<p>
+Those of us who value free software for freedom's sake will stay with
+free software anyway. We will manage to get work done without the
+patented features. But those who value free software because they
+expect it to be technically superior are likely to call it a failure
+when a patent holds it back. Thus, while it is useful to talk about
+the practical effectiveness of the “bazaar” model of
+development, and the reliability and power of some free software,
+we must not stop there. We must talk about freedom and principle.</p>
+
+<h3>Free documentation</h3>
+<p>
+The biggest deficiency in our free operating systems is not in the
+software—it is the lack of good free manuals that we can include in
+our systems. Documentation is an essential part of any software
+package; when an important free software package does not come with a
+good free manual, that is a major gap. We have many such gaps today.</p>
+<p>
+Free documentation, like free software, is a matter of freedom, not
+price. The criterion for a free manual is pretty much the same as for
+free software: it is a matter of giving all users certain freedoms.
+Redistribution (including commercial sale) must be permitted, online
+and on paper, so that the manual can accompany every copy of the
+program.</p>
+<p>
+Permission for modification is crucial too. As a general rule, I
+don't believe that it is essential for people to have permission to
+modify all sorts of articles and books. For example, I don't think
+you or I are obliged to give permission to modify articles like this
+one, which describe our actions and our views.</p>
+<p>
+But there is a particular reason why the freedom to modify is crucial
+for documentation for free software. When people exercise their right
+to modify the software, and add or change its features, if they are
+conscientious they will change the manual, too—so they can
+provide accurate and usable documentation with the modified program.
+A nonfree manual, which does not allow programmers to be conscientious
+and finish the job, does not fill our community's needs.</p>
+<p>
+Some kinds of limits on how modifications are done pose no problem.
+For example, requirements to preserve the original author's copyright
+notice, the distribution terms, or the list of authors, are OK. It is
+also no problem to require modified versions to include notice that
+they were modified, even to have entire sections that may not be
+deleted or changed, as long as these sections deal with nontechnical
+topics. These kinds of restrictions are not a problem because they
+don't stop the conscientious programmer from adapting the manual to
+fit the modified program. In other words, they don't block the free
+software community from making full use of the manual.</p>
+<p>
+However, it must be possible to modify all the <em>technical</em>
content of
+the manual, and then distribute the result in all the usual media,
+through all the usual channels; otherwise, the restrictions do
+obstruct the community, the manual is not free, and we need another
+manual.</p>
+<p>
+Will free software developers have the awareness and determination to
+produce a full spectrum of free manuals? Once again, our future
+depends on philosophy.</p>
+
+<h3>We must talk about freedom</h3>
+<p>
+Estimates today are that there are ten million users of GNU/Linux
+systems such as Debian GNU/Linux and Red Hat “Linux”.
+Free software has developed such practical advantages that users are
+flocking to it for purely practical reasons.</p>
+<p>
+The good consequences of this are evident: more interest in developing
+free software, more customers for free software businesses, and more
+ability to encourage companies to develop commercial free software
+instead of proprietary software products.</p>
+<p>
+But interest in the software is growing faster than awareness of the
+philosophy it is based on, and this leads to trouble. Our ability to
+meet the challenges and threats described above depends on the will to
+stand firm for freedom. To make sure our community has this will, we
+need to spread the idea to the new users as they come into the
+community.</p>
+<p>
+But we are failing to do so: the efforts to attract new users into our
+community are far outstripping the efforts to teach them the civics of
+our community. We need to do both, and we need to keep the two
+efforts in balance.</p>
+
+<h3>“Open Source”</h3>
+<p>
+Teaching new users about freedom became more difficult in 1998, when a
+part of the community decided to stop using the term “free
+software” and say “open source software”
+instead.</p>
+<p>
+Some who favored this term aimed to avoid the confusion of
+“free” with “gratis”—a valid goal. Others,
+however, aimed to set aside the spirit of principle that had motivated
+the free software movement and the GNU Project, and to appeal instead
+to executives and business users, many of whom hold an ideology that
+places profit above freedom, above community, above principle. Thus,
+the rhetoric of “open source” focuses on the potential to
+make high-quality, powerful software, but shuns the ideas of freedom,
+community, and principle.</p>
+<p>
+The “Linux” magazines are a clear example of this—they
+are filled with advertisements for proprietary software that works
+with GNU/Linux. When the next Motif or Qt appears, will these
+magazines warn programmers to stay away from it, or will they run ads
+for it?</p>
+<p>
+The support of business can contribute to the community in many ways;
+all else being equal, it is useful. But winning their support by
+speaking even less about freedom and principle can be disastrous; it
+makes the previous imbalance between outreach and civics education
+even worse.</p>
+<p>
+“Free software” and “open source” describe the
+same category of software, more or less, but say different things
+about the software, and about values. The GNU Project continues to
+use the term “free software”, to express the idea that
+freedom, not just technology, is important.</p>
+
+<h3>Try!</h3>
+<p>
+Yoda's aphorism (“There is no ‘try’”) sounds
+neat, but it doesn't work for me. I have done most of my work while
+anxious about whether I could do the job, and unsure that it would be
+enough to achieve the goal if I did. But I tried anyway, because
+there was no one but me between the enemy and my city. Surprising
+myself, I have sometimes succeeded.</p>
+<p>
+Sometimes I failed; some of my cities have fallen. Then I found
+another threatened city, and got ready for another battle. Over time,
+I've learned to look for threats and put myself between them and my
+city, calling on other hackers to come and join me.</p>
+<p>
+Nowadays, often I'm not the only one. It is a relief and a joy when I
+see a regiment of hackers digging in to hold the line, and I realize,
+this city may survive—for now. But the dangers are greater each
+year, and now Microsoft has explicitly targeted our community. We
+can't take the future of freedom for granted. Don't take it for
+granted! If you want to keep your freedom, you must be prepared to
+defend it.</p>
+
+
+<!-- If needed, change the copyright block at the bottom. In general, -->
+<!-- all pages on the GNU web server should have the section about -->
+<!-- verbatim copying. Please do NOT remove this without talking -->
+<!-- with the webmasters first. -->
+<!-- Please make sure the copyright date is consistent with the document
-->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>. There
are
+also <a href="/contact/">other ways to contact</a> the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden"><address@hidden></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010 Richard
Stallman
+<br />
+This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2012/09/19 00:28:09 $
+<!-- timestamp end -->
+</p>
+</div>
+
+
+</div>
+</body>
+</html>
+</pre></body></html>
Index: gnu/po/thegnuproject.nl-diff.html
===================================================================
RCS file: gnu/po/thegnuproject.nl-diff.html
diff -N gnu/po/thegnuproject.nl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/po/thegnuproject.nl-diff.html 19 Sep 2012 00:28:09 -0000 1.1
@@ -0,0 +1,1060 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/gnu/thegnuproject.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+
+<title>About the GNU Project - GNU Project - Free Software Foundation
(FSF)</title>
+
+<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software,
Free Software Foundation, History" />
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+
+<h2>The GNU Project</h2>
+
+<!-- This document uses XHTML 1.0 Strict, but may be served as -->
+<!-- text/html. Please ensure that markup style considers -->
+<!-- appendex C of the XHTML 1.0 standard. See validator.w3.org. -->
+
+<!-- Please ensure links are consistent with Apache's MultiView. -->
+<!-- Change include statements to be consistent with the relevant -->
+<!-- language, where necessary. -->
+
+<p>
+by <a href="http://www.stallman.org/"><strong>Richard
Stallman</strong></a></p>
+<span class="inserted"><ins><em><blockquote></em></ins></span>
+<p>
+<span class="removed"><del><strong>the original version
was</strong></del></span>
+<span class="inserted"><ins><em>Originally</em></ins></span> published in the
book <span class="removed"><del><strong>“Open
Sources”</p></strong></del></span> <span
class="inserted"><ins><em><em>Open Sources</em>. Richard
+Stallman was <a href="/philosophy/open-source-misses-the-point.html">
+never a supporter of “open source”</a>, but contributed
+this article so that the ideas of the free software movement would not
+be entirely absent from that book.
+</p>
+</blockquote></em></ins></span>
+
+<h3>The first software-sharing community</h3>
+<p>
+When I started working at the
+<acronym title="Massachusetts Institute of
Technology">MIT</acronym>
+Artificial Intelligence Lab in 1971, I became part of a
+software-sharing community that had existed for many years. Sharing
+of software was not limited to our particular community; it is as old
+as computers, just as sharing of recipes is as old as cooking. But we
+did it more than most.</p>
+<p>
+The AI Lab used a timesharing operating system called
+<acronym title="Incompatible Timesharing System">ITS</acronym> (the
+Incompatible Timesharing System) that the lab's staff hackers (1) had
+designed and written in assembler language for the Digital
+<acronym title="Programmed Data Processor">PDP</acronym>-10, one of
+the large computers of the era. As a member of this community, an AI
+Lab staff system hacker, my job was to improve this system.</p>
+<p>
+We did not call our software “free software”, because that
+term did not yet exist; but that is what it was. Whenever people from
+another university or a company wanted to port and use a program, we
+gladly let them. If you saw someone using an unfamiliar and
+interesting program, you could always ask to see the source code, so
+that you could read it, change it, or cannibalize parts of it to make
+a new program.</p>
+<p>
+(1) The use of “hacker” to mean “security
+breaker” is a confusion on the part of the mass media. We
+hackers refuse to recognize that meaning, and continue using the word
+to mean someone who loves to program, someone who enjoys playful
+cleverness, or the combination of the two. See my
+article, <a href="http://stallman.org/articles/on-hacking.html">On
+Hacking</a>.</p>
+
+<h3>The collapse of the community</h3>
+<p>
+The situation changed drastically in the early 1980s when Digital
+discontinued the PDP-10 series. Its architecture, elegant and
+powerful in the 60s, could not extend naturally to the larger address
+spaces that were becoming feasible in the 80s. This meant that nearly
+all of the programs composing ITS were obsolete.</p>
+<p>
+The AI Lab hacker community had already collapsed, not long before.
+In 1981, the spin-off company Symbolics had hired away nearly all of
+the hackers from the AI Lab, and the depopulated community was unable
+to maintain itself. (The book Hackers, by Steve Levy, describes these
+events, as well as giving a clear picture of this community in its
+prime.) When the AI Lab bought a new PDP-10 in 1982, its
+administrators decided to use Digital's nonfree timesharing system
+instead of ITS.</p>
+<p>
+The modern computers of the era, such as the VAX or the 68020, had
+their own operating systems, but none of them were free software: you
+had to sign a nondisclosure agreement even to get an executable copy.</p>
+<p>
+This meant that the first step in using a computer was to promise not
+to help your neighbor. A cooperating community was forbidden. The
+rule made by the owners of proprietary software was, “If you
+share with your neighbor, you are a pirate. If you want any changes,
+beg us to make them.”</p>
+<p>
+The idea that the proprietary software social system—the system
+that says you are not allowed to share or change software—is
+antisocial, that it is unethical, that it is simply wrong, may come as
+a surprise to some readers. But what else could we say about a system
+based on dividing the public and keeping users helpless? Readers who
+find the idea surprising may have taken the proprietary software
+social system as a given, or judged it on the terms suggested by
+proprietary software businesses. Software publishers have worked long
+and hard to convince people that there is only one way to look at the
+issue.</p>
+<p>
+When software publishers talk about “enforcing” their
+“rights” or “stopping <a
href="/philosophy/words-to-avoid.html#Piracy">piracy</a>”, what
they
+actually <em>say</em> is secondary. The real message of these
statements is
+in the unstated assumptions they take for granted, which the public is
+asked to accept without examination. Let's therefore examine them.</p>
+<p>
+One assumption is that software companies have an unquestionable natural
+right to own software and thus have power over all its users. (If
+this were a natural right, then no matter how much harm it does to the
+public, we could not object.) Interestingly, the US Constitution and
+legal tradition reject this view; copyright is not a natural right,
+but an artificial government-imposed monopoly that limits the users'
+natural right to copy.</p>
+<p>
+Another unstated assumption is that the only important thing about
+software is what jobs it allows you to do—that we computer users
+should not care what kind of society we are allowed to have.</p>
+<p>
+A third assumption is that we would have no usable software (or would
+never have a program to do this or that particular job) if we did not
+offer a company power over the users of the program. This assumption
+may have seemed plausible, before the free software movement
+demonstrated that we can make plenty of useful software without
+putting chains on it.</p>
+<p>
+If we decline to accept these assumptions, and judge these issues
+based on ordinary commonsense morality while placing the users first,
+we arrive at very different conclusions. Computer users should be
+free to modify programs to fit their needs, and free to share
+software, because helping other people is the basis of society.</p>
+<p>
+There is no room here for an extensive statement of the reasoning
+behind this conclusion, so I refer the reader to the web page,
+<a href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a>.</p>
+
+<h3>A stark moral <span
class="removed"><del><strong>choice.</h3></strong></del></span> <span
class="inserted"><ins><em>choice</h3></em></ins></span>
+<p>
+With my community gone, to continue as before was impossible.
+Instead, I faced a stark moral choice.</p>
+<p>
+The easy choice was to join the proprietary software world, signing
+nondisclosure agreements and promising not to help my fellow hacker.
+Most likely I would also be developing software that was released
+under nondisclosure agreements, thus adding to the pressure on other
+people to betray their fellows too.</p>
+<p>
+I could have made money this way, and perhaps amused myself writing
+code. But I knew that at the end of my career, I would look back on
+years of building walls to divide people, and feel I had spent my life
+making the world a worse place.</p>
+<p>
+I had already experienced being on the receiving end of a
+nondisclosure agreement, when someone refused to give me and the MIT
+AI Lab the source code for the control program for our printer. (The
+lack of certain features in this program made use of the printer
+extremely frustrating.) So I could not tell myself that nondisclosure
+agreements were innocent. I was very angry when he refused to share
+with us; I could not turn around and do the same thing to everyone
+else.</p>
+<p>
+Another choice, straightforward but unpleasant, was to leave the
+computer field. That way my skills would not be misused, but they
+would still be wasted. I would not be culpable for dividing and
+restricting computer users, but it would happen nonetheless.</p>
+<p>
+So I looked for a way that a programmer could do something for the
+good. I asked myself, was there a program or programs that I could
+write, so as to make a community possible once again?</p>
+<p>
+The answer was clear: what was needed first was an operating system.
+That is the crucial software for starting to use a computer. With an
+operating system, you can do many things; without one, you cannot run
+the computer at all. With a free operating system, we could again
+have a community of cooperating hackers—and invite anyone to join.
+And anyone would be able to use a computer without starting out by
+conspiring to deprive his or her friends.</p>
+<p>
+As an operating system developer, I had the right skills for this job.
+So even though I could not take success for granted, I realized that I
+was elected to do the job. I chose to make the system compatible with
+Unix so that it would be portable, and so that Unix users could easily
+switch to it. The name GNU was chosen, following a hacker tradition, as
+a recursive acronym for “GNU's Not Unix.”</p>
+<p>
+An operating system does not mean just a kernel, barely enough to run
+other programs. In the 1970s, every operating system worthy of the
+name included command processors, assemblers, compilers, interpreters,
+debuggers, text editors, mailers, and much more. ITS had them,
+Multics had them, VMS had them, and Unix had them. The GNU operating
+system would include them too.</p>
+<p>
+Later I heard these words, attributed to Hillel (1):</p>
+
+<blockquote><p>
+ If I am not for myself, who will be for me?<br />
+ If I am only for myself, what am I?<br />
+ If not now, when?
+</p></blockquote>
+<p>
+The decision to start the GNU Project was based on a similar spirit.</p>
+<p>
+(1) As an Atheist, I don't follow any religious leaders, but I
+sometimes find I admire something one of them has said.</p>
+
+<h3>Free as in freedom</h3>
+<p>
+The term “free software” is sometimes misunderstood—it
+has nothing to do with price. It is about freedom. Here, therefore,
+is the definition of free software.</p>
+
+<p>A program is free software, for you, a particular user, if:</p>
+
+<ul>
+ <li>You have the freedom to run the program as you wish, for any
purpose.</li>
+
+ <li>You have the freedom to modify the program to suit your needs.
+ (To make this freedom effective in practice, you must have access
+ to the source code, since making changes in a program without
+ having the source code is exceedingly difficult.)</li>
+
+ <li>You have the freedom to redistribute copies, either gratis
+ or for a fee.</li>
+
+ <li>You have the freedom to distribute modified versions of the
program,
+ so that the community can benefit from your improvements.</li>
+</ul>
+<p>
+Since “free” refers to freedom, not to price, there is no
+contradiction between selling copies and free software. In fact, the
+freedom to sell copies is crucial: collections of free software sold
+on CD-ROMs are important for the community, and selling them is an
+important way to raise funds for free software development.
+Therefore, a program which people are not free to include on these
+collections is not free software.</p>
+<p>
+Because of the ambiguity of “free”, people have long
+looked for alternatives, but no one has found a better term.
+The English language has more words and nuances than any other, but it
+lacks a simple, unambiguous, word that means “free”, as in
+freedom—“unfettered” being the word that comes closest in
+meaning. Such alternatives as “liberated”,
+“freedom”, and “open” have either the wrong
+meaning or some other disadvantage.</p>
+
+<h3>GNU software and the GNU system</h3>
+<p>
+Developing a whole system is a very large project. To bring it into
+reach, I decided to adapt and use existing pieces of free software
+wherever that was possible. For example, I decided at the very
+beginning to use TeX as the principal text formatter; a few years
+later, I decided to use the X Window System rather than writing
+another window system for GNU.</p>
+<p>
+Because of <span class="removed"><del><strong>this
decision,</strong></del></span> <span class="inserted"><ins><em>these
decisions, and others like them,</em></ins></span>
+the GNU system is not the same as the collection of all
+GNU software. The GNU system includes programs that are not GNU
+software, programs that were developed by other people and projects
+for their own purposes, but which we can use because they are free
+software.</p>
+
+<h3>Commencing the project</h3>
+<p>
+In January 1984 I quit my job at MIT and began writing GNU software.
+Leaving MIT was necessary so that MIT would not be able to interfere
+with distributing GNU as free software. If I had remained on the
+staff, MIT could have claimed to own the work, and could have imposed
+their own distribution terms, or even turned the work into a
+proprietary software package. I had no intention of doing a large
+amount of work only to see it become useless for its intended purpose:
+creating a new software-sharing community.</p>
+<p>
+However, Professor Winston, then the head of the MIT AI Lab, kindly
+invited me to keep using the lab's facilities.</p>
+
+<h3>The first steps</h3>
+<p>
+Shortly before beginning the GNU Project, I heard about the Free
+University Compiler Kit, also known as VUCK. (The Dutch word for
+“free” is written with a <em>v</em>.) This was a
compiler
+designed to handle multiple languages, including C and Pascal, and to
+support multiple target machines. I wrote to its author asking if GNU
+could use it.</p>
+<p>
+He responded derisively, stating that the university was free but the
+compiler was not. I therefore decided that my first program for the
+GNU Project would be a multilanguage, multiplatform compiler.</p>
+<p>
+Hoping to avoid the need to write the whole compiler myself, I
+obtained the source code for the Pastel compiler, which was a
+multiplatform compiler developed at Lawrence Livermore Lab. It
+supported, and was written in, an extended version of Pascal, designed
+to be a system-programming language. I added a C front end, and began
+porting it to the Motorola 68000 computer. But I had to give that
+up when I discovered that the compiler needed many megabytes of stack
+space, and the available 68000 Unix system would only allow 64k.</p>
+<p>
+I then realized that the Pastel compiler functioned by parsing the
+entire input file into a syntax tree, converting the whole syntax tree
+into a chain of “instructions”, and then generating the
+whole output file, without ever freeing any storage. At this point, I
+concluded I would have to write a new compiler from scratch. That new
+compiler is now known as <acronym title="GNU Compiler
Collection">GCC</acronym>;
+none of the Pastel compiler is used in it, but I managed to adapt and
+use the C front end that I had written. But that was some years
+later; first, I worked on GNU Emacs.</p>
+
+<h3>GNU Emacs</h3>
+<p>
+I began work on GNU Emacs in September 1984, and in early 1985 it was
+beginning to be usable. This enabled me to begin using Unix systems
+to do editing; having no interest in learning to use vi or ed, I had
+done my editing on other kinds of machines until then.</p>
+<p>
+At this point, people began wanting to use GNU Emacs, which raised the
+question of how to distribute it. Of course, I put it on the
+anonymous ftp server on the MIT computer that I used. (This computer,
+prep.ai.mit.edu, thus became the principal GNU ftp distribution site;
+when it was decommissioned a few years later, we transferred the name
+to our new ftp server.) But at that time, many of the interested
+people were not on the Internet and could not get a copy by ftp. So
+the question was, what would I say to them?</p>
+<p>
+I could have said, “Find a friend who is on the net and who will make
+a copy for you.” Or I could have done what I did with the original
+PDP-10 Emacs: tell them, “Mail me a tape and a
+<acronym title="Self-addressed Stamped Envelope">SASE</acronym>,
and I
+will mail it back with Emacs on it.” But I had no job, and I was
+looking for ways to make money from free software. So I announced
+that I would mail a tape to whoever wanted one, for a fee of $150. In
+this way, I started a free software distribution business, the
+precursor of the companies that today distribute entire Linux-based
+GNU systems.</p>
+
+<h3>Is a program free for every user?</h3>
+<p>
+If a program is free software when it leaves the hands of its author,
+this does not necessarily mean it will be free software for everyone
+who has a copy of it. For example,
+<a href="/philosophy/categories.html#PublicDomainSoftware"> public domain
+software</a> (software that is not copyrighted) is free software; but
+anyone can make a proprietary modified version of it. Likewise, many
+free programs are copyrighted but distributed under simple permissive
+licenses which allow proprietary modified versions.</p>
+<p>
+The paradigmatic example of this problem is the X Window System.
+Developed at MIT, and released as free software with a permissive
+license, it was soon adopted by various computer companies. They
+added X to their proprietary Unix systems, in binary form only, and
+covered by the same nondisclosure agreement. These copies of X were
+no more free software than Unix was.</p>
+<p>
+The developers of the X Window System did not consider this a
+problem—they expected and intended this to happen. Their goal was
+not freedom, just “success”, defined as “having many
+users.” They did not care whether these users had freedom, only
+that they should be numerous.</p>
+<p>
+This led to a paradoxical situation where two different ways of
+counting the amount of freedom gave different answers to the question,
+“Is this program free?” If you judged based on the freedom
+provided by the distribution terms of the MIT release, you would say
+that X was free software. But if you measured the freedom of the
+average user of X, you would have to say it was proprietary software.
+Most X users were running the proprietary versions that came with Unix
+systems, not the free version.</p>
+
+<h3>Copyleft and the GNU GPL</h3>
+<p>
+The goal of GNU was to give users freedom, not just to be popular. So
+we needed to use distribution terms that would prevent GNU software
+from being turned into proprietary software. The method we use is
+called “copyleft”.(1)</p>
+<p>
+Copyleft uses copyright law, but flips it over to serve the opposite
+of its usual purpose: instead of a means for restricting a program, it
+becomes a means for keeping the program free.</p>
+<p>
+The central idea of copyleft is that we give everyone permission to
+run the program, copy the program, modify the program, and distribute
+modified versions—but not permission to add restrictions of their
+own. Thus, the crucial freedoms that define “free
+software” are guaranteed to everyone who has a copy; they become
+inalienable rights.</p>
+<p>
+For an effective copyleft, modified versions must also be free. This
+ensures that work based on ours becomes available to our community if
+it is published. When programmers who have jobs as programmers
+volunteer to improve GNU software, it is copyleft that prevents their
+employers from saying, “You can't share those changes, because
+we are going to use them to make our proprietary version of the
+program.”</p>
+<p>
+The requirement that changes must be free is essential if we want to
+ensure freedom for every user of the program. The companies that
+privatized the X Window System usually made some changes to port it to
+their systems and hardware. These changes were small compared with
+the great extent of X, but they were not trivial. If making changes
+were an excuse to deny the users freedom, it would be easy for anyone
+to take advantage of the excuse.</p>
+<p>
+A related issue concerns combining a free program with nonfree code.
+Such a combination would inevitably be nonfree; whichever freedoms
+are lacking for the nonfree part would be lacking for the whole as
+well. To permit such combinations would open a hole big enough to
+sink a ship. Therefore, a crucial requirement for copyleft is to plug
+this hole: anything added to or combined with a copylefted program
+must be such that the larger combined version is also free and
+copylefted.</p>
+<p>
+The specific implementation of copyleft that we use for most GNU
+software is the GNU General Public License, or GNU GPL for short. We
+have other kinds of copyleft that are used in specific circumstances.
+GNU manuals are copylefted also, but use a much simpler kind of
+copyleft, because the complexity of the GNU GPL is not necessary
+for manuals.(2)</p>
+<p>
+(1) In 1984 or 1985, Don Hopkins (a very imaginative fellow) mailed me
+a letter. On the envelope he had written several amusing sayings,
+including this one: “Copyleft—all rights reversed.” I
+used the word “copyleft” to name the distribution concept
+I was developing at the time.</p>
+
+<p>
+(2) We now use the <a href="/licenses/fdl.html">GNU Free
+Documentation License</a> for documentation.</p>
+
+<h3>The Free Software Foundation</h3>
+
+<p>As interest in using Emacs was growing, other people became
+involved in the GNU project, and we decided that it was time to seek
+funding once again. So in 1985 we created
+the <a href="http://www.fsf.org/">Free Software Foundation</a>
(FSF),
+a tax-exempt charity for free software development. The
+<acronym title="Free Software Foundation">FSF</acronym> also took
over
+the Emacs tape distribution business; later it extended this by adding
+other free software (both GNU and non-GNU) to the tape, and by selling
+free manuals as well.</p>
+
+<p>Most of the FSF's income used to come from sales of copies of free
+software and of other related services (CD-ROMs of source code,
+CD-ROMs with binaries, nicely printed manuals, all with the freedom to
+redistribute and modify), and Deluxe Distributions (distributions for
+which we built the whole collection of software for the customer's
+choice of platform). Today the FSF
+still <a href="http://shop.fsf.org/"> sells manuals and other
+gear</a>, but it gets the bulk of its funding from members' dues. You
+can join the FSF at <a
href="http://fsf.org/join">fsf.org</a>.</p>
+
+<p>Free Software Foundation employees have written and maintained a
+number of GNU software packages. Two notable ones are the C library
+and the shell. The GNU C library is what every program running on a
+GNU/Linux system uses to communicate with Linux. It was developed by
+a member of the Free Software Foundation staff, Roland McGrath. The
+shell used on most GNU/Linux systems is
+<acronym title="Bourne Again Shell">BASH</acronym>, the Bourne
Again
+Shell(1), which was developed by FSF employee Brian Fox.</p>
+
+<p>We funded development of these programs because the GNU Project was
+not just about tools or a development environment. Our goal was a
+complete operating system, and these programs were needed for that
+goal.</p>
+
+<p>(1) “Bourne Again Shell” is a play on the name
+“Bourne Shell”, which was the usual shell on Unix.</p>
+
+<h3>Free software support</h3>
+
+<p>The free software philosophy rejects a specific widespread business
+practice, but it is not against business. When businesses respect the
+users' freedom, we wish them success.</p>
+
+<p>Selling copies of Emacs demonstrates one kind of free software
+business. When the FSF took over that business, I needed another way
+to make a living. I found it in selling services relating to the free
+software I had developed. This included teaching, for subjects such
+as how to program GNU Emacs and how to customize GCC, and software
+development, mostly porting GCC to new platforms.</p>
+
+<p>Today each of these kinds of free software business is practiced by a
+number of corporations. Some distribute free software collections on
+CD-ROM; others sell support at levels ranging from answering user
+questions, to fixing bugs, to adding major new features. We are even
+beginning to see free software companies based on launching new free
+software products.</p>
+
+<p>Watch out, though—a number of companies that associate
themselves
+with the term “open source” actually base their business
+on nonfree software that works with free software. These are not
+free software companies, they are proprietary software companies whose
+products tempt users away from freedom. They call these programs
+“value-added packages”, which shows the values they
+would like us to adopt: convenience above freedom. If we value freedom
+more, we should call them “freedom-subtracted” packages.</p>
+
+<h3>Technical goals</h3>
+
+<p>The principal goal of GNU is to be free software. Even if GNU had no
+technical advantage over Unix, it would have a social advantage,
+allowing users to cooperate, and an ethical advantage, respecting the
+user's freedom.</p>
+
+<p>But it was natural to apply the known standards of good practice to
+the work—for example, dynamically allocating data structures to avoid
+arbitrary fixed size limits, and handling all the possible 8-bit codes
+wherever that made sense.</p>
+
+<p>In addition, we rejected the Unix focus on small memory size, by
+deciding not to support 16-bit machines (it was clear that 32-bit
+machines would be the norm by the time the GNU system was finished),
+and to make no effort to reduce memory usage unless it exceeded a
+megabyte. In programs for which handling very large files was not
+crucial, we encouraged programmers to read an entire input file into
+core, then scan its contents without having to worry about I/O.</p>
+
+<p>These decisions enabled many GNU programs to surpass their Unix
+counterparts in reliability and speed.</p>
+
+<h3>Donated computers</h3>
+
+<p>As the GNU Project's reputation grew, people began offering to donate
+machines running Unix to the project. These were very useful, because
+the easiest way to develop components of GNU was to do it on a Unix
+system, and replace the components of that system one by one. But
+they raised an ethical issue: whether it was right for us to have a
+copy of Unix at all.</p>
+
+<p>Unix was (and is) proprietary software, and the GNU Project's
+philosophy said that we should not use proprietary software. But,
+applying the same reasoning that leads to the conclusion that violence
+in self defense is justified, I concluded that it was legitimate to
+use a proprietary package when that was crucial for developing a free
+replacement that would help others stop using the proprietary
package.</p>
+
+<p>But, even if this was a justifiable evil, it was still an evil. Today
+we no longer have any copies of Unix, because we have replaced them
+with free operating systems. If we could not replace a machine's
+operating system with a free one, we replaced the machine instead.</p>
+
+<h3>The GNU Task List</h3>
+
+<p>As the GNU Project proceeded, and increasing numbers of system
+components were found or developed, eventually it became useful to
+make a list of the remaining gaps. We used it to recruit developers
+to write the missing pieces. This list became known as the GNU Task
+List. In addition to missing Unix components, we listed various
+other useful software and documentation projects that, we thought, a
+truly complete system ought to have.</p>
+
+<p>Today (1), hardly any Unix components are left in the GNU Task
+List—those jobs had been done, aside from a few inessential
+ones. But the list is full of projects that some might call
+“applications”. Any program that appeals to more than a
+narrow class of users would be a useful thing to add to an operating
+system.</p>
+
+<p>Even games are included in the task list—and have been since the
+beginning. Unix included games, so naturally GNU should too. But
+compatibility was not an issue for games, so we did not follow the
+list of games that Unix had. Instead, we listed a spectrum of
+different kinds of games that users might like.</p>
+
+<p>(1) That was written in 1998. In 2009 we no longer maintain a long
+task list. The community develops free software so fast that we can't
+even keep track of it all. Instead, we have a list of High Priority
+Projects, a much shorter list of projects we really want to encourage
+people to write.</p>
+
+<h3>The GNU Library GPL</h3>
+
+<p>The GNU C library uses a special kind of copyleft called the GNU
+Library General Public License(1), which gives permission to link
+proprietary software with the library. Why make this exception?</p>
+
+<p>It is not a matter of principle; there is no principle that says
+proprietary software products are entitled to include our code. (Why
+contribute to a project predicated on refusing to share with us?)
+Using the LGPL for the C library, or for any library, is a matter of
+strategy.</p>
+
+<p>The C library does a generic job; every proprietary system or compiler
+comes with a C library. Therefore, to make our C library available
+only to free software would not have given free software any
+advantage—it would only have discouraged use of our library.</p>
+
+<p>One system is an exception to this: on the GNU system (and this
+includes GNU/Linux), the GNU C library is the only C library. So the
+distribution terms of the GNU C library determine whether it is
+possible to compile a proprietary program for the GNU system. There
+is no ethical reason to allow proprietary applications on the GNU
+system, but strategically it seems that disallowing them would do more
+to discourage use of the GNU system than to encourage development of
+free applications. That is why using the Library GPL is a good
+strategy for the C library.</p>
+
+<p>For other libraries, the strategic decision needs to be
+considered on a case-by-case basis. When a library does a special job
+that can help write certain kinds of programs, then releasing it under
+the GPL, limiting it to free programs only, is a way of helping other
+free software developers, giving them an advantage against proprietary
+software.</p>
+
+<p>Consider GNU Readline, a library that was developed to provide
+command-line editing for BASH. Readline is released under the
+ordinary GNU GPL, not the Library GPL. This probably does reduce the
+amount Readline is used, but that is no loss for us. Meanwhile, at
+least one useful application has been made free software specifically
+so it could use Readline, and that is a real gain for the
+community.</p>
+
+<p>Proprietary software developers have the advantages money provides;
+free software developers need to make advantages for each other. I
+hope some day we will have a large collection of GPL-covered libraries
+that have no parallel available to proprietary software, providing
+useful modules to serve as building blocks in new free software, and
+adding up to a major advantage for further free software development.</p>
+
+<p>(1) This license is now called the GNU Lesser General Public License,
+to avoid giving the idea that all libraries ought to use it.
+See <a href="/philosophy/why-not-lgpl.html">Why you shouldn't use the
+Lesser GPL for your next library</a> for more information.</p>
+
+<h3>Scratching an itch?</h3>
+<p>
+Eric Raymond says that “Every good work of software starts by
+scratching a developer's personal itch.” Maybe that happens
+sometimes, but many essential pieces of GNU software were developed in
+order to have a complete free operating system. They come from a
+vision and a plan, not from impulse.</p>
+<p>
+For example, we developed the GNU C library because a Unix-like system
+needs a C library, BASH because a Unix-like
+system needs a shell, and GNU tar because a Unix-like system needs a
+tar program. The same is true for my own programs—the GNU C
+compiler, GNU Emacs, GDB and GNU Make.</p>
+<p>
+Some GNU programs were developed to cope with specific threats to our
+freedom. Thus, we developed gzip to replace the Compress program,
+which had been lost to the community because of
+the <acronym title="Lempel-Ziv-Welch">LZW</acronym> patents. We
found
+people to develop LessTif, and more recently started
+<acronym title="GNU Network Object Model
Environment">GNOME</acronym>
+and Harmony, to address the problems caused by certain proprietary
+libraries (see below). We are developing the GNU Privacy Guard to
+replace popular nonfree encryption software, because users should not
+have to choose between privacy and freedom.</p>
+<p>
+Of course, the people writing these programs became interested in the
+work, and many features were added to them by various people for the
+sake of their own needs and interests. But that is not why the
+programs exist.</p>
+
+<h3>Unexpected developments</h3>
+<p>
+At the beginning of the GNU Project, I imagined that we would develop
+the whole GNU system, then release it as a whole. That is not how it
+happened.</p>
+<p>
+Since each component of the GNU system was implemented on a Unix
+system, each component could run on Unix systems long before a
+complete GNU system existed. Some of these programs became popular,
+and users began extending them and porting them—to the various
+incompatible versions of Unix, and sometimes to other systems as
well.</p>
+<p>
+The process made these programs much more powerful, and attracted both
+funds and contributors to the GNU Project. But it probably also
+delayed completion of a minimal working system by several years, as
+GNU developers' time was put into maintaining these ports and adding
+features to the existing components, rather than moving on to write
+one missing component after another.</p>
+
+<h3>The GNU Hurd</h3>
+<p>
+By 1990, the GNU system was almost complete; the only major missing
+component was the kernel. We had decided to implement our kernel as a
+collection of server processes running on top of Mach. Mach is a
+microkernel developed at Carnegie Mellon University and then at the
+University of Utah; the GNU Hurd is a collection of servers (i.e., a
+herd of GNUs) that run on top of Mach, and do the
+various jobs of the Unix kernel. The start of development was delayed
+as we waited for Mach to be released as free software, as had been
+promised.</p>
+<p>
+One reason for choosing this design was to avoid what seemed to be the
+hardest part of the job: debugging a kernel program without a
+source-level debugger to do it with. This part of the job had been
+done already, in Mach, and we expected to debug the Hurd servers as
+user programs, with GDB. But it took a long time to make that possible,
+and the multithreaded servers that send messages to each other have
+turned out to be very hard to debug. Making the Hurd work solidly has
+stretched on for many years.</p>
+
+<h3>Alix</h3>
+<p>
+The GNU kernel was not originally supposed to be called the Hurd. Its
+original name was Alix—named after the woman who was my sweetheart at
+the time. She, a Unix system administrator, had pointed out how her
+name would fit a common naming pattern for Unix system versions; as a
+joke, she told her friends, “Someone should name a kernel after
+me.” I said nothing, but decided to surprise her with a kernel
+named Alix.</p>
+<p>
+It did not stay that way. Michael (now Thomas) Bushnell, the main
+developer of the kernel, preferred the name Hurd, and redefined Alix
+to refer to a certain part of the kernel—the part that would trap
+system calls and handle them by sending messages to Hurd servers.</p>
+<p>
+Later, Alix and I broke up, and she changed her name;
+independently, the Hurd design was changed so that the C library would
+send messages directly to servers, and this made the Alix component
+disappear from the design.</p>
+<p>
+But before these things happened, a friend of hers came across the
+name Alix in the Hurd source code, and mentioned it to her. So
+she did have the chance to find a kernel named after her.</p>
+
+<h3>Linux and GNU/Linux</h3>
+<p>
+The GNU Hurd is not suitable for production use, and we don't know
+if it ever will be. The capability-based design has problems that
+result directly from the flexibility of the design, and it is not
+clear whether solutions exist.</p>
+
+<p>
+Fortunately, another
+kernel is available. In 1991, Linus Torvalds developed a
+Unix-compatible kernel and called it Linux. In 1992, he made Linux
+free software; combining Linux with the not-quite-complete GNU system
+resulted in a complete free operating system. (Combining them was a
+substantial job in itself, of course.) It is due to Linux that we can
+actually run a version of the GNU system today.</p>
+<p>
+We call this system version GNU/Linux, to express its composition as a
+combination of the GNU system with Linux as the kernel.</p>
+
+<h3>Challenges in our future</h3>
+<p>
+We have proved our ability to develop a broad spectrum of free
+software. This does not mean we are invincible and unstoppable.
+Several challenges make the future of free software uncertain; meeting
+them will require steadfast effort and endurance, sometimes lasting
+for years. It will require the kind of determination that people
+display when they value their freedom and will not let anyone take it
+away.</p>
+<p>
+The following four sections discuss these challenges.</p>
+
+<h3>Secret hardware</h3>
+<p>
+Hardware manufacturers increasingly tend to keep hardware
+specifications secret. This makes it difficult to write free drivers
+so that Linux and XFree86 can support new hardware. We have complete
+free systems today, but we will not have them tomorrow if we cannot
+support tomorrow's computers.</p>
+<p>
+There are two ways to cope with this problem. Programmers can do
+reverse engineering to figure out how to support the hardware. The
+rest of us can choose the hardware that is supported by free software;
+as our numbers increase, secrecy of specifications will become a
+self-defeating policy.</p>
+<p>
+Reverse engineering is a big job; will we have programmers with
+sufficient determination to undertake it? Yes—if we have built up a
+strong feeling that free software is a matter of principle, and
+nonfree drivers are intolerable. And will large numbers of us spend
+extra money, or even a little extra time, so we can use free drivers?
+Yes, if the determination to have freedom is widespread.</p>
+<p>
+(2008 note: this issue extends to the BIOS as well.
+There is a free BIOS, coreboot; the problem is getting specs
+for machines so that coreboot can support them.)</p>
+
+<h3>Nonfree libraries</h3>
+<p>
+A nonfree library that runs on free operating systems acts as a trap
+for free software developers. The library's attractive features are
+the bait; if you use the library, you fall into the trap, because your
+program cannot usefully be part of a free operating system. (Strictly
+speaking, we could include your program, but it
+won't <em>run</em> with the library missing.) Even worse, if
+a program that uses the proprietary library becomes popular, it can
+lure other unsuspecting programmers into the trap.</p>
+<p>
+The first instance of this problem was the Motif toolkit, back in the
+80s. Although there were as yet no free operating systems, it was
+clear what problem Motif would cause for them later on. The GNU
+Project responded in two ways: by asking individual free software
+projects to support the free X Toolkit widgets as well as Motif, and
+by asking for someone to write a free replacement for Motif. The job
+took many years; LessTif, developed by the Hungry Programmers, became
+powerful enough to support most Motif applications only in 1997.</p>
+<p>
+Between 1996 and 1998, another nonfree
+<acronym title="Graphical User Interface">GUI</acronym> toolkit
+library, called Qt, was used in a substantial collection of free
+software, the desktop
+<acronym title="K Desktop Environment">KDE</acronym>.</p>
+<p>
+Free GNU/Linux systems were unable to use KDE, because we could not
+use the library. However, some commercial distributors of GNU/Linux
+systems who were not strict about sticking with free software added
+KDE to their systems—producing a system with more capabilities,
+but less freedom. The KDE group was actively encouraging more
+programmers to use Qt, and millions of new “Linux users”
+had never been exposed to the idea that there was a problem in this.
+The situation appeared grim.</p>
+<p>
+The free software community responded to the problem in two ways:
+GNOME and Harmony.</p>
+<p>
+GNOME, the GNU Network Object Model Environment, is GNU's desktop
+project. Started in 1997 by Miguel de Icaza, and developed with the
+support of Red Hat Software, GNOME set out to provide similar desktop
+facilities, but using free software exclusively. It has technical
+advantages as well, such as supporting a variety of languages, not
+just C++. But its main purpose was freedom: not to require the use of
+any nonfree software.</p>
+<p>
+Harmony is a compatible replacement library, designed to make it
+possible to run KDE software without using Qt.</p>
+<p>
+In November 1998, the developers of Qt announced a change of license
+which, when carried out, should make Qt free software. There is no
+way to be sure, but I think that this was partly due to the
+community's firm response to the problem that Qt posed when it was
+nonfree. (The new license is inconvenient and inequitable, so it
+remains desirable to avoid using Qt.)</p>
+<p>
+[Subsequent note: in September 2000, Qt was rereleased under the GNU GPL,
+which essentially solved this problem.]</p>
+<p>
+How will we respond to the next tempting nonfree library? Will the
+whole community understand the need to stay out of the trap? Or will
+many of us give up freedom for convenience, and produce a major
+problem? Our future depends on our philosophy.</p>
+
+<h3>Software patents</h3>
+<p>
+The worst threat we face comes from software patents, which can put
+algorithms and features off limits to free software for up to twenty
+years. The LZW compression algorithm patents were applied for in
+1983, and we still cannot release free software to produce proper
+compressed <acronym title="Graphics Interchange
Format">GIF</acronym>s.
+[As of 2009 they have expired.] In 1998, a free program to produce
+<acronym title="MPEG-1 Audio Layer 3">MP3</acronym> compressed
audio
+was removed from distribution under threat of a patent suit.</p>
+<p>
+There are ways to cope with patents: we can search for evidence that a
+patent is invalid, and we can look for alternative ways to do a job.
+But each of these methods works only sometimes; when both fail, a
+patent may force all free software to lack some feature that users
+want. What will we do when this happens?</p>
+<p>
+Those of us who value free software for freedom's sake will stay with
+free software anyway. We will manage to get work done without the
+patented features. But those who value free software because they
+expect it to be technically superior are likely to call it a failure
+when a patent holds it back. Thus, while it is useful to talk about
+the practical effectiveness of the “bazaar” model of
+development, and the reliability and power of some free software,
+we must not stop there. We must talk about freedom and principle.</p>
+
+<h3>Free documentation</h3>
+<p>
+The biggest deficiency in our free operating systems is not in the
+software—it is the lack of good free manuals that we can include in
+our systems. Documentation is an essential part of any software
+package; when an important free software package does not come with a
+good free manual, that is a major gap. We have many such gaps today.</p>
+<p>
+Free documentation, like free software, is a matter of freedom, not
+price. The criterion for a free manual is pretty much the same as for
+free software: it is a matter of giving all users certain freedoms.
+Redistribution (including commercial sale) must be permitted, online
+and on paper, so that the manual can accompany every copy of the
+program.</p>
+<p>
+Permission for modification is crucial too. As a general rule, I
+don't believe that it is essential for people to have permission to
+modify all sorts of articles and books. For example, I don't think
+you or I are obliged to give permission to modify articles like this
+one, which describe our actions and our views.</p>
+<p>
+But there is a particular reason why the freedom to modify is crucial
+for documentation for free software. When people exercise their right
+to modify the software, and add or change its features, if they are
+conscientious they will change the manual, too—so they can
+provide accurate and usable documentation with the modified program.
+A nonfree manual, which does not allow programmers to be conscientious
+and finish the job, does not fill our community's needs.</p>
+<p>
+Some kinds of limits on how modifications are done pose no problem.
+For example, requirements to preserve the original author's copyright
+notice, the distribution terms, or the list of authors, are OK. It is
+also no problem to require modified versions to include notice that
+they were modified, even to have entire sections that may not be
+deleted or changed, as long as these sections deal with nontechnical
+topics. These kinds of restrictions are not a problem because they
+don't stop the conscientious programmer from adapting the manual to
+fit the modified program. In other words, they don't block the free
+software community from making full use of the manual.</p>
+<p>
+However, it must be possible to modify all the <em>technical</em>
content of
+the manual, and then distribute the result in all the usual media,
+through all the usual channels; otherwise, the restrictions do
+obstruct the community, the manual is not free, and we need another
+manual.</p>
+<p>
+Will free software developers have the awareness and determination to
+produce a full spectrum of free manuals? Once again, our future
+depends on philosophy.</p>
+
+<h3>We must talk about freedom</h3>
+<p>
+Estimates today are that there are ten million users of GNU/Linux
+systems such as Debian GNU/Linux and Red Hat “Linux”.
+Free software has developed such practical advantages that users are
+flocking to it for purely practical reasons.</p>
+<p>
+The good consequences of this are evident: more interest in developing
+free software, more customers for free software businesses, and more
+ability to encourage companies to develop commercial free software
+instead of proprietary software products.</p>
+<p>
+But interest in the software is growing faster than awareness of the
+philosophy it is based on, and this leads to trouble. Our ability to
+meet the challenges and threats described above depends on the will to
+stand firm for freedom. To make sure our community has this will, we
+need to spread the idea to the new users as they come into the
+community.</p>
+<p>
+But we are failing to do so: the efforts to attract new users into our
+community are far outstripping the efforts to teach them the civics of
+our community. We need to do both, and we need to keep the two
+efforts in balance.</p>
+
+<h3>“Open Source”</h3>
+<p>
+Teaching new users about freedom became more difficult in 1998, when a
+part of the community decided to stop using the term “free
+software” and say “open source software”
+instead.</p>
+<p>
+Some who favored this term aimed to avoid the confusion of
+“free” with “gratis”—a valid goal. Others,
+however, aimed to set aside the spirit of principle that had motivated
+the free software movement and the GNU Project, and to appeal instead
+to executives and business users, many of whom hold an ideology that
+places profit above freedom, above community, above principle. Thus,
+the rhetoric of “open source” focuses on the potential to
+make high-quality, powerful software, but shuns the ideas of freedom,
+community, and principle.</p>
+<p>
+The “Linux” magazines are a clear example of this—they
+are filled with advertisements for proprietary software that works
+with GNU/Linux. When the next Motif or Qt appears, will these
+magazines warn programmers to stay away from it, or will they run ads
+for it?</p>
+<p>
+The support of business can contribute to the community in many ways;
+all else being equal, it is useful. But winning their support by
+speaking even less about freedom and principle can be disastrous; it
+makes the previous imbalance between outreach and civics education
+even worse.</p>
+<p>
+“Free software” and “open source” describe the
+same category of software, more or less, but say different things
+about the software, and about values. The GNU Project continues to
+use the term “free software”, to express the idea that
+freedom, not just technology, is important.</p>
+
+<h3>Try!</h3>
+<p>
+Yoda's aphorism (“There is no ‘try’”) sounds
+neat, but it doesn't work for me. I have done most of my work while
+anxious about whether I could do the job, and unsure that it would be
+enough to achieve the goal if I did. But I tried anyway, because
+there was no one but me between the enemy and my city. Surprising
+myself, I have sometimes succeeded.</p>
+<p>
+Sometimes I failed; some of my cities have fallen. Then I found
+another threatened city, and got ready for another battle. Over time,
+I've learned to look for threats and put myself between them and my
+city, calling on other hackers to come and join me.</p>
+<p>
+Nowadays, often I'm not the only one. It is a relief and a joy when I
+see a regiment of hackers digging in to hold the line, and I realize,
+this city may survive—for now. But the dangers are greater each
+year, and now Microsoft has explicitly targeted our community. We
+can't take the future of freedom for granted. Don't take it for
+granted! If you want to keep your freedom, you must be prepared to
+defend it.</p>
+
+
+<!-- If needed, change the copyright block at the bottom. In general, -->
+<!-- all pages on the GNU web server should have the section about -->
+<!-- verbatim copying. Please do NOT remove this without talking -->
+<!-- with the webmasters first. -->
+<!-- Please make sure the copyright date is consistent with the document
-->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>. There
are
+also <a href="/contact/">other ways to contact</a> the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden"><address@hidden></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010 Richard
Stallman
+<br />
+This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2012/09/19 00:28:09 $
+<!-- timestamp end -->
+</p>
+</div>
+
+
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu/gnu-linux-faq.de.html gnu/thegnuproject...,
GNUN <=