[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/po/thegnuproject.hr.po gnu/po/thegnupro...
|
From: |
GNUN |
|
Subject: |
www gnu/po/thegnuproject.hr.po gnu/po/thegnupro... |
|
Date: |
Sun, 07 Apr 2013 11:00:58 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 13/04/07 11:00:58
Modified files:
gnu/po : thegnuproject.hr.po thegnuproject.translist
server/po : body-include-2.hr.po
Added files:
. : planetfeeds.hr.html
gnu : thegnuproject.hr.html
gnu/po : thegnuproject.hr-en.html
philosophy : philosophy-menu.hr.html
server : body-include-1.hr.html body-include-2.hr.html
bottom-notes.hr.html footer-text.hr.html
head-include-2.hr.html outdated.hr.html
skip-translations.hr.html top-addendum.hr.html
server/gnun : generic.hr.html
server/gnun/compendia: compendium.hr.po
software : recent-releases-include.hr.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/planetfeeds.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.hr.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.translist?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.hr-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/philosophy-menu.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/body-include-1.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/body-include-2.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/bottom-notes.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/footer-text.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/head-include-2.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/outdated.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/skip-translations.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/top-addendum.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/gnun/generic.hr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/gnun/compendia/compendium.hr.po?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/body-include-2.hr.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/software/recent-releases-include.hr.html?cvsroot=www&rev=1.1
Patches:
Index: gnu/po/thegnuproject.hr.po
===================================================================
RCS file: /web/www/www/gnu/po/thegnuproject.hr.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnu/po/thegnuproject.hr.po 7 Apr 2013 10:47:07 -0000 1.1
+++ gnu/po/thegnuproject.hr.po 7 Apr 2013 11:00:55 -0000 1.2
@@ -11,6 +11,7 @@
"PO-Revision-Date: 2013-04-07 10:09+0100\n"
"Last-Translator: Marin Rameša <address@hidden>\n"
"Language-Team: hrvatski <>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Index: gnu/po/thegnuproject.translist
===================================================================
RCS file: /web/www/www/gnu/po/thegnuproject.translist,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- gnu/po/thegnuproject.translist 25 Mar 2013 07:05:09 -0000 1.9
+++ gnu/po/thegnuproject.translist 7 Apr 2013 11:00:55 -0000 1.10
@@ -11,6 +11,7 @@
<span dir="ltr"><a lang="es" hreflang="es"
href="/gnu/thegnuproject.es.html">español</a> [es]</span>
<span dir="ltr"><a lang="fi" hreflang="fi"
href="/gnu/thegnuproject.fi.html">suomi</a> [fi]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/gnu/thegnuproject.fr.html">français</a> [fr]</span>
+<span dir="ltr"><a lang="hr" hreflang="hr"
href="/gnu/thegnuproject.hr.html">hrvatski</a> [hr]</span>
<span dir="ltr"><a lang="id" hreflang="id"
href="/gnu/thegnuproject.id.html">Bahasa
Indonesia</a> [id]</span>
<span dir="ltr"><a lang="it" hreflang="it"
href="/gnu/thegnuproject.it.html">italiano</a> [it]</span>
<span dir="ltr"><a lang="ja" hreflang="ja"
href="/gnu/thegnuproject.ja.html">æ¥æ¬èª</a> [ja]</span>
Index: server/po/body-include-2.hr.po
===================================================================
RCS file: /web/www/www/server/po/body-include-2.hr.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- server/po/body-include-2.hr.po 7 Apr 2013 10:43:24 -0000 1.1
+++ server/po/body-include-2.hr.po 7 Apr 2013 11:00:58 -0000 1.2
@@ -11,6 +11,7 @@
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -22,8 +23,8 @@
#. type: Content of: <div><div><div><p>
msgid ""
-"<a href=\"https://www.fsf.org/associate/support_freedom?referrer=4052";
-"\">Join the FSF!</a>"
+"<a href=\"https://www.fsf.org/associate/support_freedom?";
+"referrer=4052\">Join the FSF!</a>"
msgstr ""
#. type: Content of: <div><div><div><h4>
Index: planetfeeds.hr.html
===================================================================
RCS file: planetfeeds.hr.html
diff -N planetfeeds.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ planetfeeds.hr.html 7 Apr 2013 11:00:54 -0000 1.1
@@ -0,0 +1,4 @@
+<!-- Autogenerated File by planetrss.pl
http://web.cvs.savannah.gnu.org/viewvc/www/server/source/planetrss/?root=www -->
+<p><a
href='http://heronsperch.blogspot.com/2013/04/version-0231-of-gnustep-gui-library.html'>Version
0.23.1 of the GNUstep GUI library (`gnustep-gui') is available</a>: The
GNUstep GUI library is a library of graphical user interface classes written
completely in the Objective-C language... <a
href='http://heronsperch.blogspot.com/2013/04/version-0231-of-gnustep-gui-library.html'>more</a></p>
+<p><a
href='http://lcinexile.blogspot.com/2013/04/guile-100-4-tar-files.html'>Guile
100 #4: tar files</a>: Challenge #4 in the Guile 100 Programs Project is quite
simple. Write a script that will create a tar file from a list of files. It is
the fourth and final challenge i... <a
href='http://lcinexile.blogspot.com/2013/04/guile-100-4-tar-files.html'>more</a></p>
+<p><a
href='http://www.fsf.org/news/2012-free-software-award-winners-announced-2'>2012
Free Software Award winners announced</a>: Free Software Foundation president
Richard M. Stallman announced the winners of the FSF's ... <a
href='http://www.fsf.org/news/2012-free-software-award-winners-announced-2'>more</a></p>
Index: gnu/thegnuproject.hr.html
===================================================================
RCS file: gnu/thegnuproject.hr.html
diff -N gnu/thegnuproject.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/thegnuproject.hr.html 7 Apr 2013 11:00:55 -0000 1.1
@@ -0,0 +1,1042 @@
+
+
+<!--#include virtual="/server/header.hr.html" -->
+<!-- Parent-Version: 1.75 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+ <!--#set var="ENGLISH_PAGE" value="/gnu/thegnuproject.en.html" -->
+
+<title>O GNU projektu - GNU projekt - Zaklada za slobodan softver</title>
+<meta http-equiv="Keywords" content="GNU, GNU projekt, FSF, slobodan softver,
Zaklada za slobodan softver,
+povijest" />
+
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+<!--#include virtual="/server/banner.hr.html" -->
+<h2>GNU projekt</h2>
+
+<p>
+<a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a></p>
+
+<blockquote>
+<p>
+Originalno objavljeno u knjizi <em>Otvoreni Izvori</em>. Richard Stallman <a
+href="http://www.gnu.org/philosophy/open-source-misses-the-point.html";>nije
+nikada bio pobornik “otvorenog izvornog koda”</a>
+(“<i>open source</i>”), ali je pridonijeo ovaj Älanak tako da
+ideje pokreta slobodnog softvera ne budu u potpunosti odsutne iz te knjige.
+</p>
+</blockquote>
+
+<h3>Prva zajednica oko softvera za razmjenu</h3>
+<p>
+Kada sam 1971. zapoÄeo raditi u <acronym title="Massachusetts Institute of
+Technology">MIT</acronym> Laboratoriju za Umjetnu Inteligenciju, postao sam
+dio zajednice okupljene oko softvera za razmjenu koja je postojala mnogo
+godina. Razmjena softvera nije bila ograniÄena na naÅ¡u partikularnu
+zajednicu; stara je kao i raÄunala, isto kao Å¡to je razmjena recepata stara
+isto kao i kuhanje. Ali mi smo razmjenjivali viÅ¡e nego veÄina.</p>
+<p>
+UI Laboratorij je koristio operativni sustav za znaÄajkom dijeljenja vremena
+(<i>timesharing</i>) zvan <acronym title="Incompatible Timesharing
+System">ITS</acronym> (Incompatible Timesharing System) kojeg je
+laboratorijsko osoblje hakera (1) dizajniralo i zapisalo u asembler jeziku
+za Digital <acronym title="Programmed Data Processor">PDP</acronym>-10,
+jednog od velikih raÄunala tog razdoblja. Kao Älan te zajednice, haker
+sustava u osoblju UI Laboratorija, moj posao je bio da poboljšam taj
sustav.</p>
+<p>
+Nismo zvali naÅ¡ softver “slobodan softver”, jer taj termin joÅ¡
+nije postojao, ali to je ono Å¡to je taj softver bio. Kada god su ljudi iz
+drugih sveuÄiliÅ¡ta ili kompanija htjeli prebaciti i koristiti program na
+njihovim sustavima, mi smo im to rado dopustili. Ako biste vidjeli nekoga da
+koristi nepoznati i zanimljivi program, vi ste uvijek mogli pitati da vidite
+izvorni kod, tako da biste ga mogli Äitati, izmijeniti, ili preuzeti
+dijelove za prepravak da biste napravili novi program.</p>
+<p>
+(1) KoriÅ¡tenje termina “haker” da oznaÄava “prekrÅ¡itelja
+sigurnosnog sustava” je pometnja od strane masovnih medija. Mi,
+hakeri, odbijamo priznati to znaÄenje, i nastavljamo koristiti rijeÄ kao da
+oznaÄava nekoga tko voli programirati, nekoga tko uživa u razigranoj
+bistrini, ili u kombinaciji tih dvoje. Vidjeti moj Älanak, <a
+href="http://stallman.org/articles/on-hacking.html";>O hakiranju</a>.</p>
+
+<h3>Kolaps zajednice</h3>
+<p>
+Situacija se promijenila drastiÄno u ranim 1980-ima kada je Digital ukinuo
+PDP-10 seriju. Njegova arhitektura, elegantna i moÄna u 60-ima, nije se
+mogla prirodno produžiti na veÄe adresne prostore koji su postajali
+izvodivima u 80-ima. To je znaÄilo da su skoro svi programi koji su
+sastavljali ITS bili zastarjeli.</p>
+<p>
+Hakerska zajednica UI Laboratorija je, nedugo prije toga, kolapsirala. U
+1981., derivirana (<i>spin-off</i>) kompanija Symbolics je unajmila skoro
+sve hakere iz UI Laboratorija, i raseljena zajednica nije bila u moguÄnosti
+da se održava. (Knjiga Hakeri, Äiji autor je Steve Levy, opisuje te dogaÄaje
+i daje jasnu sliku te zajednice u njezinim najboljim vremenima.) Kada je UI
+Laboratorij kupio novi PDP-10 u 1982., njegovi administratori su odluÄili
+koristiti neslobodni sustav dijeljenja vremena od tvrtke Digital umjesto
+ITS-a.</p>
+<p>
+Moderna raÄunala toga razdoblja, kao Å¡to su VAX ili 68020, su imala vlastite
+operativne sustave, ali niti jedan od njih nije bio slobodan softver: morali
+ste potpisati sporazum o tajnosti (<i>nondisclosure</i>) Äak i da biste
+dobili izvršnu kopiju.</p>
+<p>
+To je znaÄilo da je prvi korak u koriÅ¡tenju raÄunala bio obeÄanje da
neÄete
+pomagati svome susjedu. Zajednica koja suraÄuje je bila zabranjena. Pravilo
+koje su napravili vlasnici posjedniÄkog (<i>proprietary</i>) softvera je
+bilo, “Ako razmjenjujete sa svojim susjedom, vi ste pirat. Ako želite
+neke promjene, molite nas da ih napravimo.”</p>
+<p>
+Ideja da je druÅ¡tveni sustav posjedniÄkog softvera—sustav koji kaže da
+vam nije dopuÅ¡tena razmjena ili izmjena softvera—antisocijalan, da je
+ne-etiÄan, da je jednostavno kriv, može biti iznenaÄenje nekim
+Äitateljima. Ali Å¡to drugo možemo reÄi o sustavu utemeljenom na podijeli
+javnosti i na ostavljanju korisnika bespomoÄnima? Äitatelji koji nalaze
+ideju iznenaÄujuÄom možda su uzeli druÅ¡tveni sustav posjedniÄkog softvera
+kao dan, ili su ga procijenili u terminima predloženima od strane tvrtki
+koje se bave posjedniÄkim softverom. IzdavaÄi softvera su radili dugo i
+naporno da bi uvjerili ljude da postoji samo jedan naÄin da se gleda na taj
+problem.</p>
+<p>
+Kada izdavaÄi softvera govore o “provoÄenju” svojih
+“prava” ili o “zaustavljanju <a
+href="/philosophy/words-to-avoid.html#Piracy">piratstva</a>”, ono Å¡to
+uistinu govore je sekundarno. Stvarna poruka tih izjava je u ne-utvrÄenim
+pretpostavkama koje oni uzimaju zdravo za gotovo, koje je javnost pozvana da
+ih prihvati bez ispitivanja. Hajdemo ih stoga ispitati. </p>
+<p>
+Jedna pretpostavka je da softverske kompanije imaju neupitno prirodno pravo
+da posjeduju softver i stoga da imaju moÄ nad svim svojim korisnicima. (Kada
+bi to bilo prirodno pravo, tada bez obzira na koliÄinu Å¡tete nanesenu
+javnosti, ne bismo mogli prigovoriti.) Interesantno, AmeriÄki Ustav i pravna
+tradicija odbijaju takvo gledište; autorsko pravo kopiranja
+(<i>copyright</i>) nije prirodno pravo, nego umjetan, od vlade nametnuti
+monopol koji ograniÄuje korisniÄka prirodna prava na kopiranje.</p>
+<p>
+Druga ne-utvrÄena pretpostavka: jedina važna stvar oko softvera je koje vam
+poslove dopuÅ¡ta da napravite—da mi, raÄunalni korisnici ne bi trebali
+mariti za vrstu društva koje nam je dopušteno imati.</p>
+<p>
+TreÄa pretpostavka je da mi ne bismo imali upotrebljivi softver (ili nikada
+ne bismo imali program koji Äe napraviti taj ili onaj partikularni posao)
+kada ne bismo ponudili kompaniji moÄ nad korisnicima programa. Ova
+pretpostavka se možda Äinila vjerodostojna, prije nego je pokret slobodnog
+softvera pokazao da možemo napraviti mnogo korisnog softvera bez da ga
+ograniÄimo.</p>
+<p>
+Ako odbijemo prihvatiti te pretpostavke, i prosudimo te probleme temeljem
+obiÄne zdravo razumske moralnosti dok stavljamo korisnike na prvo mjesto,
+dolazimo do vrlo razliÄitih zakljuÄaka. RaÄunalni korisnici bi trebali biti
+slobodni da izmjenjuju programe kako bi isti odgovarali njihovim potrebama,
+i biti slobodni da razmjenjuju softver, jer pomaganje drugim ljudima je
+temelj društva.</p>
+<p>
+Ovdje nema mjesta za opsežnu izjavu o logici iza ovoga zakljuÄka, pa stoga
+upuÄujem Äitatelja na mrežnu stranicu, <a href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a>.</p>
+
+<h3>Izraziti moralni izbor</h3>
+<p>
+Kada je moja zajednica nestala, nastavak u istome tonu je postao
+nemoguÄim. Umjesto toga, suoÄio sam se sa izrazitim moralnim izborom.</p>
+<p>
+Lagani izbor je bio pridruživanje svijetu posjedniÄkog softvera, potpisujuÄi
+sporazume o tajnosti i obeÄavajuÄi da neÄu pomoÄi kolegi
+hakeru. Najvjerojatnije bi isto razvijao softver objavljen pod sporazumima o
+tajnosti, dakle dodajuÄi pritisak na druge ljude da isto izdaju svoje
+kolege.</p>
+<p>
+Na taj naÄin mogao sam steÄi novac, i možda se zabaviti pisanjem koda. Ali
+sam znao da na kraju moje karijere, gledao bi natrag na godine izgraÄivanja
+zidova da razdvojim ljude, osjeÄajuÄi da sam proveo svoj život radeÄi
svijet
+gorim mjestom.</p>
+<p>
+VeÄ sam doživio kako je to biti na drugoj strani sporazuma o tajnosti, kada
+je netko odbio dati meni i MIT UI Laboratoriju izvorni kod kontrolnog
+programa naÅ¡ega pisaÄa. (Nedostatak odreÄenih znaÄajki u tom programu je
+napravio koriÅ¡tenje pisaÄa krajnje frustrirajuÄim.) Pa stoga nisam mogao
+reÄi sebi da su sporazumi o tajnosti bili bezazleni. Bio sam vrlo ljut kada
+je on odbio dijeliti sa nama; nisam mogao zauzvrat napraviti istu stvar svim
+drugima.</p>
+<p>
+Drugi izbor, iskren ali neprijatan, je bio odlazak iz raÄunalne struke. Na
+taj naÄin moje vjeÅ¡tine ne bi bile krivo upotrijebljene, ali bi bile uzalud
+potroÅ¡ene. Ne bi bio kriv za razdjeljivanje i ograniÄavanje raÄunalnih
+korisnika, ali bi se to svejedno dogodilo.</p>
+<p>
+Dakle sam tražio naÄin na koji bi programer mogao napraviti neÅ¡to za
+dobrobit. Pitao sam sebe, da li postoji program ili programi koje bi mogao
+napisati, u cilju ponovnog raÄenja zajednice moguÄom?</p>
+<p>
+Odgovor je bio jasan: prva potrebna stvar je bila operativni sustav. To je
+presudan softver u poÄecima koriÅ¡tenja raÄunala. Sa operativnim sustavom,
+možete raditi mnoge stvari; bez njega, ne možete niti pokrenuti raÄunalo. Sa
+slobodnim operativnim sustavom, mogli bismo opet imati zajednicu hakera koji
+suraÄuju—i pozvati svih da se pridruže. I svatko bi mogao koristiti
+raÄunalo bez da zapoÄne urotom liÅ¡iti njegove ili njezine prijatelje.</p>
+<p>
+Kao developer operativnih sustava, imao sam prave vještine za taj
+posao. Iako nisam mogao uzeti uspjeh zdravo za gotovo, shvatio sam da sam
+odabran da napravim posao. Odabrao sam da napravim sustav kompatibilan sa
+Unix operativnim sustavom, tako da bi bio prenosiv, i da bi se Unix
+korisnici mogli lako prebaciti na njega. Ime GNU je bilo odabrano, slijedeÄi
+hakersku tradiciju, kao rekurzivni akronim za “GNU Nije Unix.”</p>
+<p>
+Operativni sustav ne znaÄi samo imati jezgru (<i>kernel</i>), jedva dovoljnu
+da pokrene druge programe. U 1970-ima, svaki operativni sustav dostojan
+imena je ukljuÄivao komandne procesore, asemblere, kompajlere, interpretere,
+softver za praÄenje izvrÅ¡enja programa (<i>debugger</i>), ureÄivaÄe teksta,
+softver za slanje elektroniÄkih poruka (<i>mailer</i>), i joÅ¡ mnogo
+toga. ITS ih je imao, Multics ih je imao, VMS ih je imao, i Unix ih je
+imao. GNU operativni sustav Äe ih isto ukljuÄiti.</p>
+<p>
+Kasnije sam Äuo ove rijeÄi, pripisane Hillelu (1):</p>
+
+<blockquote><p>
+ Ako nisam za sebe, tko Äe biti za mene?<br />
+ Ako sam samo za sebe, Å¡to sam ja?<br />
+ Ako ne sada, kada?
+</p></blockquote>
+<p>
+Odluka da se zapoÄne GNU Projekt je bila utemeljena u sliÄnom duhu.</p>
+<p>
+(1) Kao ateist, ne slijedim religijske voÄe, ali ponekad se divim nekim
+njihovim rijeÄima.</p>
+
+<h3>Slobodno kao u slobodi</h3>
+<p>
+Termin “slobodan softver” je ponekad pogreÅ¡no
+shvaÄeni—nema veze sa cijenom. On govori o slobodi. Ovo je, prema
+tome, definicija slobodnoga softvera.</p>
+
+<p>Program je slobodan softver, za vas, partikularnoga korisnika, ako:</p>
+
+<ul>
+ <li>Imate slobodu da pokrenete program kako želite, za bilo koji cilj.</li>
+
+ <li>Imate slobodu da promijenite program da odgovara vašim potrebama. (Da
ova
+sloboda bude efektivna u praksi, morate imati pristup izvornome kodu, pošto
+je izmjenjivanje programa bez izvornoga koda iznimno teško.)</li>
+
+ <li>Imate slobodu ponovne distribucije kopija, bilo besplatno ili za
cijenu.</li>
+
+ <li>Imate slobodu distribucije izmijenjenih verzija programa, tako da
zajednica
+može imati korist od vaših poboljšanja.</li>
+</ul>
+<p>
+PoÅ¡to se “slobodan” odnosi na slobodu, ne na cijenu, nema
+kontradikcije izmeÄu prodavanja kopija i slobodnog softvera. U stvarnosti,
+sloboda prodavanja kopija je presudna: kolekcije slobodnog softvera koje se
+prodaju na CD-ROM-ovima su važne za zajednicu, i njihovo prodavanje je važan
+naÄin da se sakupe sredstva za razvijanje slobodnog softvera. Prema tome,
+program kojeg ljudi nisu slobodni ukljuÄiti u te kolekcije nije slobodan
+softver.</p>
+<p>
+Zbog dvosmislenosti “slobodnog”, ljudi su odavna tražili
+alternative, ali nitko nije našao bolji termin. Engleski jezik ima više
+rijeÄi i nijansi nego bilo koji drugi, ali nedostaje mu jednostavna,
+nedvosmislena, rijeÄ koja znaÄi “slobodan”, kao u
+slobodi—“nesputani” je rijeÄ koja dolazi najbliže pravom
+znaÄenju. Takve alternative kao “osloboÄen”,
+“sloboda” i “otvoren” imaju ili krivo znaÄenje ili
+neki drugi hendikep.</p>
+
+<h3>GNU softver i GNU sustav</h3>
+<p>
+Razvijanje cijeloga sustava je vrlo veliki projekt. Da bi se stavio u doseg,
+odluÄio sam prilagoditi i koristiti postojeÄe dijelove slobodnog softvera
+kada god je to bilo moguÄe. Na primjer, odluÄio sam na samome poÄetku
+koristiti TeX kao glavni oblikovatelj teksta; nekoliko godina kasnije,
+odluÄio sam iskoristiti X Window System, radije nego pisati novi grafiÄki
+sustav za GNU.</p>
+<p>
+Zbog tih odluka, i drugih sliÄnih njima, GNU sustav nije isto Å¡to i
+kolekcija svog GNU softvera. GNU sustav ukljuÄuje programe koji nisu GNU
+softver, programe koje su razvili drugi ljudi i projekte za njihove vlastite
+ciljeve, ali koje možemo koristiti jer su slobodan softver.</p>
+
+<h3>PoÄetak projekta</h3>
+<p>
+U sijeÄnju 1984. dao sam otkaz na MIT poslu i poÄeo pisati GNU
+softver. Odlazak iz MIT-a je bio nužan tako da se MIT ne bi mogao umiješati
+u distribuciju GNU-a kao slobodnog softvera. Da sam ostao u osoblju, MIT je
+mogao tvrditi da posjeduje djelo, i mogao je nametnuti svoja distribucijska
+pravila, ili Äak pretvoriti djelo u posjedniÄki softverski paket. Nisam imao
+namjeru raditi veliki opseg posla samo da vidim kako postaje beskoristan za
+njegov namijenjeni cilj: stvaranje nove zajednice oko softvera za razmjenu.</p>
+<p>
+MeÄutim, profesor Winston, tada glavni u MIT UI Laboratoriju, ljubazno me
+pozvao da nastavim koristiti postrojenja laboratorija.</p>
+
+<h3>Prvi koraci</h3>
+<p>
+Nedugo nakon poÄetka GNU Projekta, Äuo sam za Kompajlerski Sustav Slobodnog
+SvuÄiliÅ¡ta, znani kao VUCK. (Nizozemska rijeÄ za “slobodan” se
+piše sa <em>v</em>.) To je bio kompajler dizajnirani da barata sa
+viÅ¡estrukim jezicima, ukljuÄujuÄi C i Pascal, i da podržava viÅ¡estruke
+ciljne strojeve. Pisao sam njegovu autoru sa pitanjem da li ga GNU može
+koristiti.</p>
+<p>
+Odgovorio je podrugljivo, izjavljujuÄi da je sveuÄiliÅ¡te slobodno ali
+kompajler nije. Prema tome sam odluÄio da Äe moj prvi program za GNU Projekt
+biti viÅ¡ejeziÄan, viÅ¡eplatformski kompajler.</p>
+<p>
+NadajuÄi da Äu izbjeÄi potrebu da sam napiÅ¡em cijeli kompajler, nabavio sam
+izvorni kod za Pastel kompajler, koji je bio višeplatformski kompajler
+razvijen u Lawrence Livermore Laboratoriju. Podržavao je, i bio je napisan u
+poboljšanoj verziji Pascal jezika, dizajniran da bude jezik za sistemsko
+programiranje. Dodao sam C suÄelje, i zapoÄeo prenoÅ¡enje na Motorola 68000
+raÄunalo. Ali morao sam odustati od toga kada sam otkrio da kompajler
+potrebuje mnogo megabajta stog (<i>stack</i>) prostora, dok je dostupni
+68000 Unix sustav samo dozvoljavao 64k.</p>
+<p>
+Tada sam shvatio da je Pastel kompajler funkcionirao tako Å¡to je
+raÅ¡Älanjivao (<i>parse</i>) cijelu ulaznu datoteku u stablo sintakse,
+pretvarajuÄi cijelo sintaksno stablo u lanac “instrukcija”, i
+tada je generirao cijelu izlaznu datoteku, bez da je oslobodio bilo kakav
+prostor. U toj toÄki, zakljuÄio sam da Äu morati iznova napisati novi
+kompajler. Taj novi kompajler je sada znani kao <acronym title="GNU Compiler
+Collection">GCC</acronym>; ništa od Pastel kompajlera nije upotrebljeno u
+njemu, ali sam uspio prilagoditi i iskoristiti C suÄelje koje sam
+napisao. Ali to je bilo nekoliko godina kasnije; prvo sam radio na GNU
+Emacs-u.</p>
+
+<h3>GNU Emacs</h3>
+<p>
+ZapoÄeo sam rad na GNU Emacs-u rujnu 1984., i u ranoj 1985. postajao je
+upotrebljiv. To mi je omoguÄilo da poÄinjem koristiti Unix sustave za
+ureÄivanje; bez interesa da nauÄim koristiti vi ili ed, do tada sam radio
+ureÄivanje na drugim vrstama strojeva.</p>
+<p>
+U toj toÄki, ljudi su poÄeli željeti koristiti GNU Emacs, Å¡to je uzdignulo
+pitanje oko naÄina njegove distribucije. Naravno, stavio sam ga na anonimni
+ftp poslužitelj na MIT raÄunalu koje sam koristio. (To raÄunalo,
+prep.ai.mit.edu, je dakle postalo glavno mjesto za GNU ftp distribuciju;
+kada je bilo ukinuto nekoliko godina kasnije, premjestili smo ime na naš
+novi ftp poslužitelj.) Ali u to vrijeme, mnogi ljudi koji su bili
+zainteresirani nisu bili na Internetu i nisu mogli preuzeti kopiju
+ftp-om. Dakle pitanje je bilo, Å¡to Äu njima reÄi?</p>
+<p>
+Mogao sam reÄi: “NaÄite prijatelja koji je na mreži i koji Äe
+napraviti kopiju za vas.” Ili sam mogao napraviti isto Å¡to i sa
+originalnim PDP-10 Emacs-om: reÄi im: “PoÅ¡aljite mi traku i <acronym
+title="Self-addressed Stamped Envelope">SASE</acronym>, i poslati Äu vam je
+natrag sa Emacs-om." Ali nisam imao posao, i tražio sam naÄine da steknem
+novac od slobodnog softvera. Tada sam proglasio da Äu poslati traku svakome
+tko je htio, za proviziju od $150. Na taj naÄin, zapoÄeo sam posao
+distribucije slobodnog softvera, prethodnik kompanija koje danas
+distribuiraju cijele Linux-temeljene GNU sustave.</p>
+
+<h3>Da li je program slobodan za svakog korisnika?</h3>
+<p>
+Ako je program slobodan softver kada napusti ruke njegova autora, to nužno
+ne znaÄi da Äe biti slobodan softver za svakoga tko ima kopiju. Na primjer,
+<a href="/philosophy/categories.html#PublicDomainSoftware">softver u javnoj
+domeni</a> (softver koji nije pod autorskim pravom kopiranja) je slobodan
+softver; ali svatko može napraviti posjedniÄku izmijenjenu verziju. SliÄno,
+mnogi slobodni programi su pod autorskim pravom kopiranja ali su
+distribuirani pod jednostavnim popustljivim licencama koje dopuštaju
+posjedniÄke izmijenjene verzije.</p>
+<p>
+ParadigmatiÄan primjer toga problema je X Window System. Razvijen na MIT-u,
+i objavljen kao slobodni softver sa popustljivom licencom, bio je uskoro
+prilagoÄen od strane raznih raÄunalnih kompanija. Oni su dodali X svojim
+posjedniÄkim Unix sustavima, samo u binarnom obliku, i pokrivenom istim
+sporazumom o tajnosti. Te X kopije više nisu bile slobodni softver, isto kao
+Å¡to i Unix nije bio.</p>
+<p>
+Developeri X Windows System-a nisu to smatrali problemom—oni su
+oÄekivali i naumili da se to dogodi. Njihov cilj nije bila sloboda, nego
+samo “uspjeh”, definiran kao “imati puno korisnika.”
+Oni nisu marili da li ti korisnici imaju slobodu, samo da bi trebali biti
+brojni.</p>
+<p>
+To je vodilo u paradoksalnu situaciju gdje su dva razliÄita naÄina brojanja
+koliÄine slobode dale razliÄite odgovore na pitanje: “Da li je ovaj
+program slobodan?” Ako ste prosuÄivali na temelju slobode dane
+distribucijskim pravilima MIT objave, rekli biste da je X bio slobodan
+softver. Ali ako ste mjerili slobodu prosjeÄnog X korisnika, morali biste
+reÄi da je X posjedniÄki softver. VeÄina X korisnika su pokretali
+posjedniÄke verzije koje su dolazile sa Unix sustavima, ne slobodne
verzije.</p>
+
+<h3>Copyleft i GNU GPL</h3>
+<p>
+Cilj GNU-a je bio dati korisnicima slobodu, ne samo biti popularan. Tako smo
+trebali koristiti distribucijska pravila koja bi sprijeÄila da GNU softver
+bude pretvoren u posjedniÄki softver. Metoda koju koristimo se zove
+“copyleft”.(1)</p>
+<p>
+Copyleft koristi zakon o autorskim pravima kopiranja, ali ga preokreÄe na
+drugu stranu da služi suprotno od uobiÄajene svrhe: umjesto sredstvo
+ograniÄenja programa, postaje sredstvo održavanja programa slobodnim.</p>
+<p>
+Središnja ideja copylefta je da dajemo svima dopuštenje da pokrenu program,
+kopiraju program, izmjene program, i distribuiraju izmijenjene
+verzije—ali ne dopuÅ¡tenje da dodaju svoja dodatna ograniÄenja. Dakle,
+presudne slobode koje definiraju “slobodni softver” su
+garantirane svima koji imaju kopiju; postaju neotuÄiva prava.</p>
+<p>
+Za efektivni copyleft, izmijenjene verzije moraju isto biti slobodne. To
+osigurava da djelo temeljeno na našemu postane dostupno našoj zajednici ako
+je objavljeno. Kada programeri koji imaju poslove kao programeri volontiraju
+da poboljÅ¡aju GNU softver, copyleft je taj koji sprjeÄava njihove poslodavce
+da kažu: “Vi ne možete razmjenjivati te izmjene, jer Äemo ih
+iskoristiti da napravimo naÅ¡u posjedniÄku verziju programa.”</p>
+<p>
+Zahtjev da izmjene moraju biti slobodne je suštinski ako želimo osigurati
+slobodu za svakog korisnika programa. Kompanije koje su privatizirale X
+Window System obiÄno su napravile neke izmjene da bi softver prenosili na
+njihove sustave i hardver. Te izmjene su bile male u usporedbi sa velikim
+opsegom X-a, ali nisu bile trivijalne. Kada bi izrada izmjena bila isprika
+da se ospori korisnicima sloboda, bilo bi lagano za svakoga da iskoristi
+ispriku.</p>
+<p>
+Srodan problem tiÄe se kombinacije slobodnog programa sa neslobodnim
+kodom. Takva kombinacija bi neizbježno bila neslobodna; koje god slobode
+nedostaju za neslobodni dio bi isto nedostajale i za cjelinu. Dozvoljavanje
+takvih kombinacija bi otvorilo ponor toliko velik da se u njemu može
+potopiti brod. Dakle, presudni zahtjev za copyleft je da zaÄepi taj ponor:
+sve dodano ili kombinirano sa programom pod copyleftom mora biti takvo da
+veÄa kombinirana verzija bude isto slobodna i pod copyleftom.</p>
+<p>
+SpecifiÄna implementacija copylefta kojeg koristimo za veÄinu GNU softvera
+je GNU opÄa javna licenca (<i>GNU General Public License</i>), ili GNU GPL
+ukratko. Imamo druge vrste copylefta koje se koriste u specifiÄnim
+uvjetima. GNU priruÄnici su isto pod copyleftom, ali koriste mnogo
+jednostavniju vrstu copylefta, jer kompleksnost GNU GPL-a nije nužna za
+priruÄnike.(2)</p>
+<p>
+(1) U 1984. ili 1985., Don Hopkins (vrlo maÅ¡tovit Äovjek) mi je poslao
+pismo. Na koverti je napisao nekoliko zabavnih dosjetki, ukljuÄujuÄi ovu:
+“Copyleft - sva prava preokrenuta.” Ja sam koristio rijeÄ
+“copyleft” da bi dao ime distribucijskom konceptu kojeg sam
+razvijao u to vrijeme.</p>
+
+<p>
+(2) Sada koristimo <a href="/licenses/fdl.html">GNU licencu slobodne
+dokumentacije (<i>GNU Free Documentation License</i>)</a> za dokumentaciju.</p>
+
+<h3>Zaklada za slobodan softver</h3>
+
+<p>Interes za koriÅ¡tenje Emacs-a je rastao, drugi ljudi su postali ukljuÄeni
u
+GNU projekt, i odluÄili smo da je vrijeme da joÅ¡ jednom potražimo
+financiranje. Tako smo u 1985. stvorili <a
+href="http://www.fsf.org/";>Zakladu za slobodan softver (Free Software
+Fundation)</a> (FSF), dobrotvornu ustanovu osloboÄenu od poreza za
+razvijanje slobodnog softvera. <acronym title="Free Software
+Foundation">FSF</acronym> je isto preuzeo posao distribucije Emacs-a na
+trakama; kasnije se to proširilo dodavanjem drugog slobodnog softvera (GNU i
+ne-GNU) na traku, i isto tako, prodajom slobodnih priruÄnika.</p>
+
+<p>VeÄina FSF prihoda je dolazila od prodaje kopija slobodnog softvera i
drugih
+srodnih usluga (CD-ROM-ovi izvornoga koda, CD-ROM-ovi sa binarnim
+datotekama, lijepo ispisani priruÄnici, sve sa slobodom za ponovnu
+distribuciju i izmjenu), i luksuzne distribucije (distribucije za koje smo
+izgradili cijelu kolekciju softvera za platformu koju je klijent
+odabrao). Danas FSF još uvijek <a href="http://shop.fsf.org/";>prodaje
+priruÄnike i drugu opremu</a>, ali dobiva glavni dio financiranja od
+Älanarina. Vi se možete pridružiti FSF na <a
+href="http://fsf.org/join";>fsf.org</a>.</p>
+
+<p>Zaposlenici Zaklade za slobodan softver su napisali i održavaju velik broj
+GNU softverskih paketa. Dva znaÄajna su C biblioteka i ljuska. GNU C
+biblioteka je ono Å¡to svaki program koji je pokrenut na GNU/Linux sustavu
+upotrebljava da bi komunicirao sa Linux-om. Razvijena je od strane Älana
+osoblja Zaklade za slobodan softver, Roland McGrath. Ljuska koja se koristi
+na veÄini GNU/Linux sustava je <acronym title="Bourne Again
+Shell">BASH</acronym>, Bourne Again Shell (1), koja je razvijena od strane
+FSF zaposlenika, Brian Fox.</p>
+
+<p>Financirali smo razvitak tih programa jer GNU Projekt nije bio samo alati
+ili razvojno okruženje. Naš cilj je bio potpuni operativni sustav, i ti
+programi su bili potrebni za taj cilj.</p>
+
+<p>(1) “Bourne Again Shell” je igra sa imenom “Bourne
+Shell”, koja je bila uobiÄajena ljuska na Unix sustavu.</p>
+
+<h3>Podrška slobodnog softvera</h3>
+
+<p>Filozofija slobodnog softvera odbija specifiÄnu rasprostranjenu poslovnu
+praksu, ali nije protiv tvrtki. Kada tvrtke poÅ¡tuju korisniÄke slobode,
+želimo im uspjeh.</p>
+
+<p>Prodaja Emacs kopija demonstrira jednu vrstu posla vezanog uz slobodni
+softver. Kada je FSF preuzeo taj posao, trebao sam drugi naÄin
+preživljavanja. Našao sam ga u prodaji usluga koje se odnose na slobodni
+softver koji sam razvio. To je ukljuÄivalo poduÄavanje, kako programirati
+GNU Emacs i kako prilagoditi GCC, i razvoj softvera, uglavnom prenošenje
+GCC-a na nove platforme.</p>
+
+<p>Danas svaki od ovih vrsta poslova vezanih uz slobodni softver je u praksi u
+brojnim korporacijama. Neki distribuiraju kolekcije slobodnog softvera na
+CD-ROM-u; drugi prodaju podrÅ¡ku na razinama od odgovaranja na korisniÄka
+pitanja, do popravljanja greÅ¡aka, do dodavanja znatnih novih znaÄajki. Äak i
+poÄinjemo viÄati kompanije slobodnog softvera temeljene na poduzimanju novih
+projekata slobodnog softvera.</p>
+
+<p>Premda, pripazite—brojne kompanije koje vežu sebe na termin
+“otvoreni izvorni kod” u aktualnosti temelje svoj posao na
+neslobodnom softveru koji radi sa slobodnim softverom. To nisu kompanije
+slobodnog softvera, one su kompanije posjedniÄkog softvera Äiji proizvodi
+primamljuju korisnike dalje od slobode. Oni zovu te programe “paketi
+sa dodanom vrijednoÅ¡Äu”, koji pokazuju vrijednosti koje bi oni htjeli
+da prihvatimo: pogodnost iznad slobode. Ako više vrednujemo slobodu, trebali
+bi ih zvati paketi “oduzimanja slobode”.</p>
+
+<h3>TehniÄki ciljevi</h3>
+
+<p>Glavni cilj GNU-a je bio da bude slobodan softver. Äak i kada GNU ne bi
imao
+tehniÄku prednost nad Unix-om, imao bi druÅ¡tvenu prednost, dopuÅ¡tajuÄi
+korisnicima da suraÄuju, i etiÄku prednost, poÅ¡tivanje slobode
korisnika.</p>
+
+<p>Ali bilo je prirodno primijeniti znane standarde dobre prakse na
+djelo—na primjer, dinamiÄko alociranje struktura podataka da bi se
+izbjegla proizvoljno fiksirana ograniÄenja veliÄine, i rukovanje sa svim
+moguÄim 8-bitnim kodovima gdje god je to imalo smisla.</p>
+
+<p>U dopuni, odbili smo fokus Unix-a na malu veliÄinu memorije, odlukom da ne
+podržavamo 16-bitne strojeve (bilo je jasno da Äe 32-bitni strojevi biti
+mjerilo dok doÄe vrijeme zavrÅ¡avanja GNU sustava), i da ne napravimo napor
+da smanjimo upotrebu memorije sve dok ne prijeÄe megabajt. U programima za
+koje rukovanje velikim datotekama nije bilo presudno, ohrabrivali smo
+programere da uÄitaju cijelu ulaznu datoteku u jezgru, i tada da pretraže
+njen sadržaj bez brige oko I/O (<i>Input/Output</i>).</p>
+
+<p>Te odluke su omoguÄile mnogim GNU programima da nadiÄu svoje Unix verzije
u
+pouzdanosti i brzini.</p>
+
+<h3>Donirana raÄunala</h3>
+
+<p>Kako je ugled GNU Projekta rastao, ljudi su projektu poÄeli nuditi donacije
+strojeva koji su pokretali Unix. Oni su bili vrlo korisni, jer je najlakši
+naÄin razvijanja GNU komponenata bio da se to radi na Unix sustavu, i
+zamjenjivanje komponenata tog sustava jednu po jednu. Ali to je postavilo
+etiÄno pitanje: da li je bilo ispravno za nas da uopÄe imamo kopiju
Unix-a.</p>
+
+<p>Unix je bio (i jest) posjedniÄki softver, i filozofija GNU Projekta je
+govorila da ne bismo trebali koristiti posjedniÄki softver. Ali,
+primjenjivajuÄi istu logiku koja vodi do zakljuÄka da je nasilje u
+samoobrani opravdano, zakljuÄio sam da je legitimno koristiti posjedniÄki
+paket kada je to bilo presudno za razvitak slobodne zamijene koja Äe pomoÄi
+drugima da prestanu koristiti posjedniÄki paket.</p>
+
+<p>Ali, iako je to bilo opravdano zlo, bilo je još uvijek zlo. Danas više
+nemamo kopija Unix-a, jer smo ih zamijenili sa slobodnim operativnim
+sustavima. Ako nismo mogli zamijeniti operativni sustav stroja sa slobodnim,
+umjesto toga zamijenili smo stroj.</p>
+
+<h3>GNU lista zadataka</h3>
+
+<p>Nastavkom GNU Projekta, poveÄavajuÄi broj sistemskih komponenti je naÄen
ili
+razvijen, eventualno je postalo korisno napraviti listu preostalih
+praznina. Koristili smo tu listu da vrbujemo developere da napišu dijelove
+koji su nedostajali. Ta lista je postala znana kao GNU lista zadataka. U
+dodatku Unix komponenata koje nedostaju, popisali smo razni drugi korisni
+softver i dokumentacijske pakete za koje smo mislili da bi istinski potpuni
+sustav trebao imati.</p>
+
+<p>Danas (1), jedva da postoji Unix komponenta koja je ostala u GNU listi
+zadataka—ti poslovi su napravljeni, osim nekoliko nebitnih. Ali lista
+je puna projekata koje neki nazivaju “aplikacijama”. Svaki
+program koji privlaÄi viÅ¡e nego usku klasu korisnika bi bio korisna stvar za
+dodati u operativni sustav.</p>
+
+<p>Äak su i igre ukljuÄene u listu zadataka—i bile su od poÄetka.
Unix je
+ukljuÄivao igre, pa bi tako i GNU prirodno trebao. Ali kompatibilnost nije
+problem za igre, tako da nismo slijedili listu igara koje je Unix
+imao. Umjesto toga, popisali smo spektar razliÄitih vrsta igara koje bi se
+mogle svidjeti korisnicima.</p>
+
+<p>(1) Ovo je napisano u 1998. U 2009. viÅ¡e ne održavamo dugaÄku listu
+zadataka. Zajednica razvija slobodni softver toliko brzo da ne možemo
+pratiti sve. Umjesto toga, imamo listu projekata visokog prioriteta, mnogo
+kraÄu listu projekata za koje stvarno želimo ohrabriti ljude da ih
napišu.</p>
+
+<h3>GPL GNU biblioteke</h3>
+
+<p>GNU C biblioteka koristi posebnu vrstu copylefta nazvanu GNU opÄa javna
+licenca za biblioteke (<i>GNU Library General Public License</i>) (1), koja
+daje dopuÅ¡tenje da se veže posjedniÄki softver sa bibliotekom. ZaÅ¡to je ova
+iznimka napravljena?</p>
+
+<p>Nije stvar principa; ne postoji princip koji kaže da proizvodi
posjedniÄkog
+softvera imaju pravo ukljuÄiti naÅ¡ kod. (ZaÅ¡to doprinijeti projektu koji se
+temelji na odbijanju razmijene sa nama?) Korištenje LGPL-a za C biblioteku,
+ili za bilo koju biblioteku, je stvar strategije.</p>
+
+<p>C biblioteka radi generiÄki posao; svaki posjedniÄki sustav ili kompajler
+dolazi sa C bibliotekom. Dakle, pravljenjem naše C biblioteke dostupne samo
+slobodnom softveru ne bi dali slobodnom softveru nikakvu prednost—samo
+bi obeshrabrilo korištenje naše biblioteke.</p>
+
+<p>Jedan sustav je iznimka za to: na GNU sustavu (i to ukljuÄuje i GNU/Linux),
+GNU C biblioteka je jedina C biblioteka. Prema tome, distribucijska pravila
+GNU C biblioteke odreÄuju da li je moguÄe kompilirati posjedniÄki program za
+GNU sustav. Ne postoji etiÄki razlog da se dopuste posjedniÄke aplikacije na
+GNU sustavu, ali strategijski se Äini da bi odbijanje njih viÅ¡e doprinijelo
+obeshrabrivanju korištenja GNU sustava nego ohrabrivanju razvitka slobodnih
+aplikacija. Zbog toga je korištenje GPL za Biblioteke dobra strategija za C
+biblioteku.</p>
+
+<p>Za druge biblioteke, strategijska odluka se treba razmotriti od sluÄaja do
+sluÄaja. Kada biblioteka radi poseban posao koji može pomoÄi u pisanju
+odreÄenih vrsta programa, tada objava pod GPL-om, ograniÄavanje samo na
+slobodne programe, je naÄin pomaganja drugim developerima slobodnog
+softvera, dajuÄi im prednost u odnosu na posjedniÄki softver.</p>
+
+<p>Razmotrite GNU Readline, biblioteka koja je razvijena da bi se obezbijedilo
+ureÄivanje komandne linije za BASH. Readline je objavljena pod obiÄnim GNU
+GPL-om, ne GPL-om za Biblioteke. To vjerojatno smanjuje koliÄinu koriÅ¡tenja
+Readline-a, ali to nije gubitak za nas. U meÄuvremenu, barem jedna korisna
+aplikacija je postala slobodan softver specifiÄno da bi mogla koristiti
+Readline, i to je stvarna dobit za zajednicu.</p>
+
+<p>Developeri posjedniÄkog softvera imaju prednosti koje novac daje;
developeri
+slobodnog softvera moraju raditi prednosti meÄu sobom. Nadam se da Äemo
+jedan dan imati veliku kolekciju biblioteka pokrivenih GPL-om koji nemaju
+paralelu dostupnu posjedniÄkom softveru, dajuÄi korisne module da služe za
+izgradnju novog slobodnog softvera, i dodavajuÄi veliku prednost za daljnji
+razvitak slobodnog softvera.</p>
+
+<p>(1) Ova licenca je sada zvana GNU niža opÄa javna licenca (<i>GNU Lesser
+General Public License</i>), da bi se izbjegla ideja da bi je sve biblioteke
+trebale koristiti. Pogledajte <a
+href="http://www.gnu.org/philosophy/why-not-lgpl.html";>Zašto ne biste
+trebali koristiti niži GPL za vaÅ¡u sljedeÄu biblioteku</a> za viÅ¡e
+informacija.</p>
+
+<h3>ÄeÅ¡anje svraba?</h3>
+<p>
+Eric Raymond kaže: “Svako dobro djelo softvera zapoÄinje ÄeÅ¡anjem
+developerovog osobnog svraba.” Možda se to i dogodi ponekad, ali mnogi
+glavni dijelovi GNU softvera su razvijeni sa ciljem da se napravi potpuni
+operativni sustav. Oni dolaze iz vizije i plana, ne iz impulsa.</p>
+<p>
+Na primjer, razvili smo GNU C biblioteku jer sustav nalik Unix-u treba C
+biblioteku, BASH zato jer sustav nalik Unix-u treba ljusku, i GNU tar zato
+jer sustav nalik Unix-u treba tar program. Isto je istina i za moje
+programe—GNU C kompajler, GNU Emacs, GDB i GNU Make.</p>
+<p>
+Neki GNU programi su razvijeni da bi se nosili sa specifiÄnim prijetnjama
+našoj slobodi. Dakle, razvili smo gzip da bi zamijenili Compress program,
+koji je bio izgubljen iz zajednice zbog <acronym
+title="Lempel-Ziv-Welch">LZW</acronym> patenata. NaÅ¡li smo ljude koji Äe
+razvijati LessTif, i viÅ¡e nedavno zapoÄeli smo <acronym title="GNU Network
+Object Model Environment">GNOME</acronym> i Harmony, da bi adresirali
+probleme izazvane odreÄenim posjedniÄkim bibliotekama (vidite
+ispod). Razvijamo GNU Privacy Guard da nadomjestimo popularni neslobodni
+enkripcijski softver, jer korisnici ne bi trebali birati izmeÄu privatnosti
+i slobode.</p>
+<p>
+Naravno, ljudi koji pišu te programe su postali zainteresirani za rad, i
+mnoge znaÄajke su dodane od strane raznih ljudi zbog vlastitih potreba i
+interesa. Ali to nije razlog zašto ti programi postoje.</p>
+
+<h3>NeoÄekivani razvoji</h3>
+<p>
+Na poÄetku GNU Projekta, zamislio sam da Äemo razviti cijeli GNU sustav, i
+onda ga objaviti kao cjelinu. Nije se tako dogodilo.</p>
+<p>
+Pošto je svaka komponenta GNU sustava implementirana na Unix sustavu, svaka
+komponenta se mogla pokrenuti da Unix sustavu dugo prije nego je potpuni GNU
+sustav postojao. Neki od tih programa su postali popularni, i korisnici su
+ih poÄeli proÅ¡irivati i prenositi na druge platforme—na razne
+nekompatibilne verzije Unix-a, i katkad na druge sustave.</p>
+<p>
+Taj proces je napravio te programe mnogo moÄnijima, i privukao financiranje
+i suradnike na GNU Projekt. Ali je vjerojatno i usporio završenje
+minimalnoga radnog sustava za nekoliko godina, pošto je vrijeme GNU
+developera stavljeno u održavanje tih prenesenih programa i u dodavanje
+znaÄajki postojeÄim komponentama, radije nego u poÄetak pisanja, jednu za
+drugom, komponenata koje nedostaju.</p>
+
+<h3>GNU Hurd</h3>
+<p>
+1990., GNU sustav je bio skoro dovršeni; jedina velika komponenta koja je
+nedostajala je bila jezgra. OdluÄili smo implementirati jezgru kao kolekciju
+poslužiteljskih procesa koji se izvršavaju iznad Mach-a. Mach je
+mikro-jezgra razvijena na Carnegie Mellon SveuÄiliÅ¡tu i tada na Utah
+SveuÄiliÅ¡tu; GNU Hurd je kolekcija poslužitelja (odnosno, krdo GNU-a) koji
+se izvrÅ¡avaju iznad Mach-a, i rade razne poslove Unix jezgre. PoÄetak
+razvitka je bio u zakaÅ¡njenju dok smo Äekali da Mach bude objavljen kao
+slobodan softver, kao Å¡to je bilo obeÄano.</p>
+<p>
+Jedan razlog odabira tog dizajna je bilo izbjegavanje onoga Å¡to se Äinilo
+najtežim dijelom posla: otklanjanje grešaka u programu jezgre bez softvera
+koji na razini izvornog koda prati izvršenje programa (<i>source-level
+debugger</i>). Taj dio posla je veÄ napravljen, u Mach-u, i oÄekivali smo da
+Äe otklanjanje greÅ¡aka u Hurd poslužiteljima biti na razini korisniÄkih
+programa, sa GDB-om. Ali proÅ¡lo je dosta vremena dok je to postalo moguÄe, i
+viÅ¡enitni (<i>multithreaded</i>) poslužitelji koji Å¡alju poruke meÄu sobom
+su se ispostavili vrlo teÅ¡kima u procesu otklanjanja greÅ¡aka. RadeÄi Hurd
+posao razvuÄenim kroz mnogo godina.</p>
+
+<h3>Alix</h3>
+<p>
+GNU jezgra se na poÄetku nije trebala zvati Hurd. Njegovo originalno ime je
+bilo Alix—dano prema ženi koja je bila u to vrijeme moja
+simpatija. Ona, Unix administrator, je ukazala na to kako bi njeno ime dobro
+pristajalo u uobiÄajeni uzorak davanja imena verzija Unix sustava; u Å¡ali,
+rekla je svojim prijateljima: “Netko bi trebao nazvati jezgru po
+meni.” Nisam rekao niÅ¡ta, nego sam je odluÄio iznenaditi s jezgrom po
+imenu Alix.</p>
+<p>
+Nije ostalo na tome. Michael (sada Thomas) Bushnell, glavni developer
+jezgre, više je volio ime Hurd, i ponovno je definirao Alix da se odnosi na
+odreÄeni dio jezgre—dio koji bi hvatao sistemske pozive i rukovao s
+njima slanjem poruka Hurd poslužiteljima.</p>
+<p>
+Kasnije, Alix i ja smo prekinuli, i ona je promijenila svoje ime; neovisno,
+dizajn Hurd-a je promijenjen tako da bi C biblioteka slala poruke direktno
+poslužiteljima, i zbog toga je Alix komponenta nestala iz dizajna.</p>
+<p>
+Ali prije nego su se te stvari dogodile, njezin prijatelj je našao ime Alix
+u izvornom kodu Hurd-a, i spomenuo je to njoj. Tako da je imala Å¡ansu naÄi
+jezgru po njenom imenu.</p>
+
+<h3>Linux i GNU/Linux</h3>
+<p>
+GNU Hurd nije prikladan za produkcijsko koriÅ¡tenje, i ne znamo da li Äe
+ikada biti. Dizajn temeljen na moguÄnostima ima problema koji rezultiraju
+direktno iz fleksibilnosti dizajna, i nije jasno da li rješenja postoje.</p>
+
+<p>
+SreÄom, druga jezgra je dostupna. U 1991., Linus Torvalds je razvio jezgru
+kompatibilnu sa Unix-om i nazvao je Linux. U 1992., napravio je Linux
+slobodnim softverom; kombinirajuÄi Linux sa joÅ¡ nedovrÅ¡enim GNU sustavom
+rezultiralo je potpunim slobodnim operativnim sustavom. (Naravno,
+kombiniranje je bio znatan posao sam po sebi.) Zbog Linux-a mi danas možemo
+pokrenuti verziju GNU sustava.</p>
+<p>
+Zovemo tu verziju sustava GNU/Linux, da bi izrazili njegov sastav kao
+kombinaciju GNU sustava sa Linux-om kao jezgrom.</p>
+
+<h3>Izazovi u naÅ¡oj buduÄnosti</h3>
+<p>
+Dokazali smo našu sposobnost da razvijemo široki spektar slobodnog
+softvera. To ne znaÄi da smo nepobjedivi i nezaustavljivi. Nekoliko izazova
+rade buduÄnost slobodnog softvera nesigurnom; suoÄavanje sa njima Äe
+zahtijevati postojan napor i izdržljivost, trajuÄi ponekad i po nekoliko
+godina. Zahtijevati Äe vrstu determinacije koje ljudi pokazuju kada cijene
+svoju slobodu i neÄe dopustiti nikome da je oduzme.</p>
+<p>
+SljedeÄa Äetiri odjeljka raspravljaju o tim izazovima.</p>
+
+<h3>Tajni hardver</h3>
+<p>
+ProizvoÄaÄi hardvera u poveÄavajuÄem trendu drže specifikacije hardvera
+tajnim. Zbog toga je teÅ¡ko pisati slobodne upravljaÄke programe tako da bi
+Linux i XFree86 podržavali novi hardver. Imamo potpune slobodne sustave
+danas, ali ih sutra neÄemo imati ako ne možemo podržavati sutraÅ¡nja
+raÄunala.</p>
+<p>
+Postoje dva naÄina suoÄavanja sa tim problemom. Programeri mogu raditi
+obrnuti inženjering da bi dokuÄili kako podržavati hardver. Mi ostali
možemo
+izabrati hardver koji je podržani od strane slobodnog softvera; kako se naši
+brojevi budu poveÄavali, tajnost specifikacija Äe postati samo-poražavajuÄa
+politika.</p>
+<p>
+Obrnuto inženjerstvo je veliki posao; da li Äemo imati programere sa
+dovoljnom determinacijom da to poduzmu? Da—ako smo izgradili jak
+osjeÄaj da je slobodan softver stvar principa, i da se neslobodni
+upravljaÄki programi ne mogu tolerirati. I da li Äe veliki broj nas
+potroÅ¡iti viÅ¡ak novca, ili Äak malo viÅ¡ka vremena, da možemo koristiti
+slobodne upravljaÄke programe? Da, ako je determinacija za posjedovanjem
+slobode Å¡iroko rasprostranjena.</p>
+<p>
+(bilješka iz 2008: ovaj problem se isto tako i proširuje na BIOS. Postoji
+slobodni BIOS, coreboot; problem je nabavka specifikacija za strojeve tako
+da ih coreboot može podržavati.)</p>
+
+<h3>Neslobodne biblioteke</h3>
+<p>
+Neslobodna biblioteka koja se vrti na slobodnim operativnim sustavima
+djeluje kao zamka za developere slobodnog softvera. Primamljive znaÄajke
+biblioteke su mamac; ako koristite biblioteku, padate u zamku, zato jer vaš
+program ne može korisno biti dio slobodnog operativnoga sustava. (Strogo
+govoreÄi, možemo ukljuÄiti vaÅ¡ program, ali neÄe se <em>pokrenuti</em> bez
+biblioteke.) JoÅ¡ gore, ako program koji koristi posjedniÄku biblioteku
+postane popularan, može namamiti druge nesumnjajuÄe programere u zamku.</p>
+<p>
+Prvi sluÄaj ovog problema su bili Motif alati, natrag u 80-ima. Iako tada
+nisu postojali slobodni operativni sustavi, bilo je jasno koji problem Äe im
+Motif uzrokovati kasnije. GNU Projekt je odgovorio na dva naÄina: pitajuÄi
+individualne projekte slobodnog softvera da podržavaju slobodne X alatne
+blokove (<i>widgets</i>) kao i Motif, i raspitivajuÄi se za nekoga tko bi
+napisao slobodnu zamjenu za Motif. Posao je trajao mnogo godina; LessTif,
+razvijen od strane Hungry Programmers, postao je dovoljno moÄan da podržava
+veÄinu Motif aplikacija tek u 1997.</p>
+<p>
+IzmeÄu 1996. i 1998., druga neslobodna <acronym title="Graphical User
+Interface">GUI</acronym> alatna biblioteka, zvana Qt, je bila korištena u
+znatnoj kolekciji slobodnog softvera, <acronym title="K Desktop
+Environment">KDE</acronym> desktop.</p>
+<p>
+Slobodni GNU/Linux sustavi nisu bili u moguÄnosti koristiti KDE, zato jer
+nismo mogli koristiti biblioteku. MeÄutim, neki komercijalni distributeri
+GNU/Linux sustava koji nisu bili strogi da se drže slobodnog softvera,
+dodali su KDE svojim sustavima—producirajuÄi sustav sa viÅ¡e
+sposobnosti, ali manje slobode. KDE grupa je aktivno ohrabrivala sve više
+programera da koriste Qt, i milijuni novih “Linux korisnika”
+nisu nikada bili izloženi ideji da ima nešto krivo u tome. Situacija se
+Äinila mrgodnom.</p>
+<p>
+Zajednica slobodnog softvera je odgovorila na problem u dva naÄina: GNOME i
+Harmony.</p>
+<p>
+GNOME, GNU Network Object Model Environment, je desktop projekt
+GNU-a. Miguel de Icaza ga je zapoÄeo u 1997., i bio je razvijan sa podrÅ¡kom
+Red Hat Software-a, GNOME je krenuo obezbjediti sliÄna desktop postrojenja,
+ali ekskluzivno koriÅ¡tenjem slobodnog softvera. Ima i tehniÄke prednosti,
+kao što su podrška za razne jezike, ne samo C++. Ali njegov glavni cilj je
+bila sloboda: da se ne zahtijeva korištenje neslobodnog softvera.</p>
+<p>
+Harmony je kompatibilna zamjenska biblioteka, dizajnirana da omoguÄi
+pokretanje KDE softvera bez korištenja Qt-a.</p>
+<p>
+Studeni 1998, developeri Qt-a su proglasili promjenu licence koja Äe, kada
+se provede, napraviti Qt slobodnim softverom. Ne postoji naÄin da se bude
+siguran, ali mislim da je to dijelom zbog Ävrstog odgovora zajednice na
+problem koji je Qt stvarao dok je bio neslobodan. (Nova licenca je nepogodna
+i nepravedna, pa ostaje poželjno izbjegavati korištenje Qt-a.)</p>
+<p>
+[Naknadna bilješka: u rujnu 2000, Qt je ponovno objavljen pod GNU GPL-om,
+što je suštinski riješilo taj problem.]</p>
+<p>
+Kako Äemo odgovoriti na slijedeÄu primamljivu neslobodnu biblioteku? Da li
+Äe cijela zajednica shvatiti potrebu da se ne upadne u zamku? Ili Äe mnogi
+od nas odustati od slobode zbog pogodnosti, i napraviti veliki problem? Naša
+buduÄnost ovisi o naÅ¡oj filozofiji.</p>
+
+<h3>Softverski patenti</h3>
+<p>
+Najgora prijetnja sa kojom se suoÄavamo dolazi od softverskih patenata, koji
+mogu staviti algoritme i znaÄajke izvan dosega slobodnog softvera do
+dvadeset godina. Patenti LZW algoritma za kompresiju su bili primijenjeni u
+1983., i još uvijek ne možemo objaviti slobodni softver da producira prave
+komprimirane <acronym title="Graphics Interchange
+Format">GIF</acronym>-ove. [Od 2009. oni su istekli.] U 1998., slobodan
+program za produkciju <acronym title="MPEG-1 Audio Layer 3">MP3</acronym>
+kompriminiranog zvuka je izbaÄen iz distribucije zbog prijetnje patentnom
+tužbom.</p>
+<p>
+Postoje naÄini da se nosimo sa patentima: možemo tražiti dokaze da je patent
+nevažeÄi, i možemo tražiti alternativne naÄine da napravimo posao. Ali
svaka
+od tih metoda radi samo ponekad; kada obje pobace, patent može prisiliti sav
+slobodni softver da nema neke znaÄajke koje korisnici žele. Å to Äemo
+napraviti kada se to dogodi?</p>
+<p>
+Oni meÄu nama koji vrednuju slobodni softver zbog slobode Äe ostati svejedno
+upotrebljavati slobodni softver. Uspjeti Äemo napraviti posao bez
+patentiranih znaÄajki. Ali oni koji vrednuju slobodni softver jer oÄekuju da
+bude tehniÄki superioran Äe vjerojatno nazvati to neuspjehom kada patent
+ograniÄava softver. Dakle, dok je korisno govoriti o praktiÄnoj efektivnosti
+“bazar” modela razvoja, i o pouzdanosti i moÄi nekog slobodnog
+softvera, ne smijemo se zaustaviti na tome. Moramo govoriti o slobodi i
+principu.</p>
+
+<h3>Slobodna dokumentacija</h3>
+<p>
+NajveÄi nedostatak naÅ¡ih slobodnih operativnih sustava nije u
+softveru—nego u nedostatku dobrih slobodnih priruÄnika koje možemo
+ukljuÄiti u naÅ¡e sustave. Dokumentacija je suÅ¡tinski dio svakog softverskog
+paketa; kada važan paket slobodnog softvera ne doÄe sa dobrim slobodnim
+priruÄnikom, to je velik propust. Danas imamo mnoge takve praznine.</p>
+<p>
+Slobodna dokumentacija, kao i slobodni softver, je stvar slobode, a ne
+cijene. Kriterij za slobodni priruÄnik je uglavnom isti kao i za slobodni
+softver: stvar je u davanju svim korisnicima odreÄene slobode. Ponovna
+distribucija (ukljuÄujuÄi i komercijalnu prodaju) mora biti dopuÅ¡tena, na
+mreži i na papiru, tako da priruÄnik može popratiti svaku kopiju
programa.</p>
+<p>
+Dozvola za izmjenu je isto presudna. Kao opÄenito pravilo, ne vjerujem da je
+bitno za ljude da imaju dozvolu da izmjenjuju Älanke i knjige svake
+vrste. Na primjer, ne mislim da smo vi ili ja dužni dati dozvolu da se
+izmjenjuju Älanci poput ovoga, koji opisuju naÅ¡a djela i naÅ¡a glediÅ¡ta.</p>
+<p>
+Ali postoji partikularni razlog zašto je sloboda izmijene presudna za
+dokumentaciju slobodnog softvera. Kada ljudi prakticiraju svoje pravo da
+izmijene softver, i dodaju ili izmijene neke njegove znaÄajke, ako su
+savjesni oni Äe isto izmijeniti i priruÄnik—tako da mogu obezbjediti
+toÄnu i upotrebljivu dokumentaciju sa izmijenjenim programom. Neslobodni
+priruÄnik, koji ne dozvoljava programerima da budu savjesni i da dovrÅ¡e
+posao, ne dopunjuje potrebe naše zajednice.</p>
+<p>
+Neke odreÄene granice na to kako se izmijene rade ne predstavljaju
+problem. Na primjer, zahtjevi da se oÄuvaju originalna autorova biljeÅ¡ka o
+autorskim pravima kopiranja, distribucijska pravila, ili lista autora, su u
+redu. Isto tako nije problem da se zahtijeva da izmijenjene verzije
+ukljuÄuju biljeÅ¡ku da su bile izmijenjene, Äak i da imaju cijele odjeljke
+koji mogu biti izbrisani ili promijenjeni, sve dok ti odjeljci se drže
+ne-tehniÄkih tema. Te vrste restrikcija nisu problem jer ne zaustavljaju
+savjesnog programera da prilagodi priruÄnik tako da odgovara izmijenjenom
+programu. Drugim rijeÄima, ne zaustavljaju zajednicu oko slobodnog softvera
+da dobije cijelu korist od priruÄnika.</p>
+<p>
+MeÄutim, mora biti moguÄe izmijeniti cijeli <em>tehniÄki</em> sadržaj
+priruÄnika, i tada distribuirati rezultat na svim uobiÄajenim medijima, kroz
+sve uobiÄajene kanale; u suprotnom, restrikcije ometaju zajednicu, priruÄnik
+nije slobodan, i trebamo drugi priruÄnik.</p>
+<p>
+Da li Äe developeri slobodnog softvera imati svjesnost i determinaciju da
+produciraju cijeli spektar slobodnih priruÄnika? JoÅ¡ jednom, naÅ¡a buduÄnost
+ovisi o filozofiji.</p>
+
+<h3>Moramo govoriti o slobodi</h3>
+<p>
+Procjene danas su da postoji deset milijuna korisnika GNU/Linux sustava kao
+Å¡to su Debian GNU/Linux i Red Hat “Linux”. Slobodni softver je
+razvio takve praktiÄne prednosti da se korisnici sjate na njih iz Äisto
+praktiÄnih razloga.</p>
+<p>
+Dobre posljedice toga su oÄite: viÅ¡e interesa za razvoj slobodnog softvera,
+više klijenata za poslove slobodnog softvera, i više sposobnosti da se
+ohrabre kompanije da razvijaju komercijalni slobodni softver umjesto
+posjedniÄkih softverskih proizvoda.</p>
+<p>
+Ali interes za softver raste brže nego svjesnost filozofije na kojoj je
+utemeljen, i to vodi u nevolju. NaÅ¡a sposobnost da se suoÄimo sa izazovima i
+prijetnjama opisanima iznad ovisi o volji da ostanemo Ävrsto za slobodu. Da
+bi osigurali da naÅ¡a zajednica ima tu volju, moramo raÅ¡iriti tu ideju meÄu
+novim korisnicima kako oni dolaze u našu zajednicu.</p>
+<p>
+Ali nismo uspješni u tome: napori da se privuku novi korisnici u našu
+zajednicu daleko nadmaÅ¡uju napore da ih poduÄimo pravima i dužnostima naÅ¡e
+zajednice. Moramo napraviti oboje, i moramo držati ta dva napora u
+ravnoteži.</p>
+
+<h3>“Otvoreni izvorni kod”</h3>
+<p>
+PoduÄavanje novih korisnika o slobodi je postalo teže u 1998, kada je dio
+zajednice odluÄio prestati koristiti termin “slobodan softver” i
+reÄi “softver otvorenog izvornog koda” umjesto toga.</p>
+<p>
+Neki koji favoriziraju taj termin ciljali su da izbjegnu konfuziju
+“slobodnog” sa “besplatnog”—valjani
+cilj. Drugi, meÄutim, su ciljali da stave na stranu duh principa koji je
+motivirao pokret slobodnog softvera i GNU Projekt, i umjesto toga napraviti
+priziv izvršnim i poslovnim korisnicima, mnogi od kojih drže ideologiju koja
+stavlja profit iznad slobode, iznad zajednice, iznad principa. Tako,
+retorika “otvorenog izvornog koda” fokusira na potencijal da se
+napravi visoko kvalitetan, moÄan softver, ali izbjegava ideje slobode,
+zajednice i principa.</p>
+<p>
+“Linux” Äasopisi su jasan primjer toga—puni su oglasa za
+posjedniÄki softver koji radi sa GNU/Linux-om. Kada se pojavi slijedeÄi
+Motif ili Qt, da li Äe ti Äasopisi upozoriti programere da udalje od toga,
+ili Äe raditi reklame za to?</p>
+<p>
+PodrÅ¡ka poslovnog dijela može pridonijeti zajednici na mnoge naÄine; sve
+drugo jednako, korisno je. Ali dobivanje njihove podrÅ¡ke govoreÄi joÅ¡ manje
+o slobodi i principu može biti katastrofalno; radi ranije spomenutu
+neravnotežu izmeÄu dosega prema novim korisnicima i edukaciji o pravima i
+dužnostima još gorom.</p>
+<p>
+“Slobodan softver” i “otvoreni izvorni kod” opisuju
+istu kategoriju softvera, viÅ¡e-manje, ali govore razliÄite stvari o
+softveru, i o vrijednostima. GNU Projekt nastavlja koristiti termin
+“slobodan softver”, da se izrazi ideja da je sloboda, ne samo
+tehnologija, važna.</p>
+
+<h3>Pokušajte!</h3>
+<p>
+Aforizam Yode (“Ne postoji ‘pokuÅ¡aj’”) zvuÄi lijepo,
+ali ne radi za mene. Napravio sam veÄinu svoga rada dok sam bio tjeskoban
+oko toga da li Äu moÄi napraviti posao, ako da, nesiguran da li Äe to biti
+dovoljno da dosegnem cilj. Ali pokušao sam svejedno, jer nije bilo nikoga
+osim mene izmeÄu neprijatelja i mojeg grada. IznenaÄujuÄi sebe, ponekad sam
+uspio.</p>
+<p>
+Ponekad nisam uspio; neki od mojih gradova su pali. Tada sam našao drugi
+grad pod prijetnjom, i pripremio se za joÅ¡ jednu bitku. Vremenom, nauÄio sam
+tražiti prijetnje i staviti sebe izmeÄu njih i mojeg grada, prizivajuÄi
+druge hakere da doÄu i da se pridruže.</p>
+<p>
+U danaÅ¡nje vrijeme, Äesto nisam jedini. OlakÅ¡anje je i radost kada vidim puk
+hakera kako kopaju da bi zadržali vod, i shvatim, ovaj grad možda preživi -
+zasada. Ali opasnosti su sve veÄe svake godine, i sada je Microsoft
+specifiÄno naciljao naÅ¡u zajednicu. Ne možemo uzeti buduÄnost slobode
zdravo
+za gotovo. Ne uzimajte je zdravo za gotovo! Ako želite zadržati svoju
+slobodu, morati biti pripremljeni da je branite. </p>
+
+
+<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.hr.html" -->
+<div id="footer">
+
+<p>Molim vas Å¡aljite opÄenite FSF & GNU upite na <a
+href="mailto:address@hidden";><address@hidden></a>. Postoje isto i <a
+href="/contact/">drugi naÄini kontaktiranja</a> FSF-a. Prekinute poveznice i
+drugi ispravci ili prijedlozi mogu biti poslani na <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>. -->
+Radimo naporno i dajemo sve od sebe da bi pružili toÄne, visoko kvalitetne
+prijevode. MeÄutim, nismo osloboÄeni od nesavrÅ¡enosti. Molim vas Å¡aljite
+vaÅ¡e komentare i opÄenite prijedloge u tom smislu na <a
+href="mailto:address@hidden";><address@hidden></a>.</p>
+<p>Za informacije o koordiniranju i slanju prijevoda naših mrežnih stranica,
+pogledajte <a href="/server/standards/README.translations.html">README za
+prijevode</a>.</p>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) 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.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright © 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010 Richard
+Stallman<br />Copyright © 2013 Marin RameÅ¡a (translation)</p>
+
+<p>Ovo djelo je dano na korištenje pod licencom <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.hr";> Creative
+Commons Imenovanje-Bez prerada 3.0 SAD</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.hr.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+ </div>
+
+
+ <p><!-- timestamp start -->
+Zadnji put promijenjeno:
+
+$Date: 2013/04/07 11:00:55 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: gnu/po/thegnuproject.hr-en.html
===================================================================
RCS file: gnu/po/thegnuproject.hr-en.html
diff -N gnu/po/thegnuproject.hr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/po/thegnuproject.hr-en.html 7 Apr 2013 11:00:55 -0000 1.1
@@ -0,0 +1,1050 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.75 -->
+<title>About the GNU Project
+- GNU Project - Free Software Foundation</title>
+<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software,
Free Software Foundation, History" />
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The GNU Project</h2>
+
+<p>
+by <a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a></p>
+
+<blockquote>
+<p>
+Originally published in the book <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>
+
+<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 choice</h3>
+<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 these decisions, and others like them,
+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>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<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. 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>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) 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.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010
+Richard Stallman</p>
+
+<p>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>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2013/04/07 11:00:55 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: philosophy/philosophy-menu.hr.html
===================================================================
RCS file: philosophy/philosophy-menu.hr.html
diff -N philosophy/philosophy-menu.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/philosophy-menu.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,17 @@
+
+
+<!-- begin philosophy/philosophy-menu.html -->
+<!-- begin edu navigation bar -->
+<ul id="edu-navigation">
+ <li><a href="/philosophy/philosophy.html">Introduction</a></li>
+ <li><a href="http://audio-video.gnu.org/";>Audio and video</a></li>
+ <li><a href="/philosophy/essays-and-articles.html">Essays and
articles</a></li>
+ <li><a href="/philosophy/speeches-and-interview.html">Speeches and
+interviews</a></li>
+ <li><a href="/philosophy/third-party-ideas.html">Third party
ideas</a></li>
+ <li><a href="/server/sitemap.html#directory-philosophy">All philosophy
+articles</a></li>
+</ul>
+
+<!-- end edu navigation bar -->
+<!-- end philosophy/philosophy-menu.html -->
Index: server/body-include-1.hr.html
===================================================================
RCS file: server/body-include-1.hr.html
diff -N server/body-include-1.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/body-include-1.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,17 @@
+
+
+<!-- start of server/body-include-1.html -->
+<!--#set var="HTML_BODY" value="yes" -->
+<div id="toplinks"><a href="#content">Skip to content</a> | <span
class="netscape4"> <a
+href="#navigation">Skip to navigation</a> |</span> <a
+href="/accessibility/">Accessibility</a></div>
+
+<!--#if expr="$TRANSLATION_LIST" -->
+<!--#echo encoding="none" var="TRANSLATION_LIST" -->
+<!--#elif expr="$INITIAL_TRANSLATIONS_LIST = included" -->
+<!-- if initial translation list isn't included before banner.html,
+ then the file may use an old boilerplate that contains
+ div#translations in its body, and we mustn't duplicate it here. -->
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<!--#endif -->
+<!-- end of server/body-include-1.html -->
Index: server/body-include-2.hr.html
===================================================================
RCS file: server/body-include-2.hr.html
diff -N server/body-include-2.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/body-include-2.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,59 @@
+
+
+ <!-- start of server/body-include-2 -->
+<div id="header">
+ <div class="inner" style="position: relative;">
+
+ <h1 id="logo"><a href="/">The GNU Operating System</a></h1>
+
+
+
+ <div id="fssbox">
+ <p id="joinfsftab"><a
+href="https://www.fsf.org/associate/support_freedom?referrer=4052";>Join the FSF!</a></p>
+ <h4>Sign up for the <a href="http://www.fsf.org/fss";>Free Software
Supporter</a></h4>
+ <p>A monthly email newsletter about GNU and Free Software</p>
+ <form
action="https://crm.fsf.org/civicrm/profile/create&reset=1&gid=31";
method="post">
+<div><input name="postURL" type="hidden" value="" /> <input type="hidden"
+name="group[25]" value="1" /> <input name="cancelURL" type="hidden"
+value="https://crm.fsf.org/civicrm/profile?reset=1&gid=31"; /> <input
+name="_qf_default" type="hidden" value="Edit:cancel" />
+</div>
+
+ <p><label>Enter your email address (e.g.
address@hidden)</label></p><p><input type="text" id="frmEmail"
name="email-Primary" size="15"
+maxlength="80" /> <input type="submit" name="_qf_Edit_next"
+value="Ok" /></p>
+ </form>
+ </div>
+ </div>
+ </div>
+
+<div id="navigation">
+ <div class="inner">
+
+ <div id="searcher">
+ <form method="get" action="http://www.gnu.org/cgi-bin/estseek.cgi";>
+ <div><label class="netscape4" for="phrase">Search:</label> <input
name="phrase"
+id="phrase" type="text" size="18" accesskey="s" value="Why GNU/Linux?"
+onfocus="this.value=''" /> <input type="submit" value="Search" /></div>
+ <!-- unnamed label -->
+</form>
+ </div>
+
+ <!-- /searcher -->
+<ul>
+ <li id="tabAboutGNU"><a href="/gnu/gnu.html">About GNU</a></li>
+ <li id="tabPhilosophy"><a href=
"/philosophy/philosophy.html">Philosophy</a></li>
+ <li id="tabLicenses"><a href="/licenses/licenses.html">Licenses</a></li>
+ <li id="tabEducation"><a href="/education/education.html">Education</a></li>
+ <li id="tabSoftware"><a href="/software/software.html">Downloads</a></li>
+ <li id="tabDoc"><a href="/doc/doc.html">Documentation</a></li>
+ <li id="tabHelp"><a href="/help/help.html">Help GNU</a></li>
+ </ul>
+
+ </div>
+<!-- /inner -->
+</div>
+
+<!-- /navigation -->
+<!-- end of server/body-include-2 -->
Index: server/bottom-notes.hr.html
===================================================================
RCS file: server/bottom-notes.hr.html
diff -N server/bottom-notes.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/bottom-notes.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,6 @@
+
+<!-- start of server/bottom-notes.html -->
+<p><a href="http://www.fsf.org/about/dmca-notice";>Copyright Infringement
+Notification</a></p>
+
+<!-- end of server/bottom-notes.html -->
Index: server/footer-text.hr.html
===================================================================
RCS file: server/footer-text.hr.html
diff -N server/footer-text.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/footer-text.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,41 @@
+
+<!-- begin server/footer-text.html -->
+<div class="inner">
+
+<div class="yui-g" id="fsf-links">
+ <ul>
+ <li><a href="/">GNU home page</a></li>
+ <li><a
href="http://www.fsf.org/";>FSF home page</a></li>
+ <li><a href="/graphics/graphics.html">GNU Art</a></li>
+ <li><a href="/fun/fun.html">GNU Fun</a></li>
+ <li><a href="/people/people.html">GNU's Who?</a></li>
+ <li><a
href="http://directory.fsf.org";>Free Software Directory</a></li>
+ <li><a href="/server/sitemap.html">Site map</a></li>
+ </ul>
+</div>
+
+<div class="yui-g" id="mission-statement">
+
+<p><small>The <a href="http://www.fsf.org";>Free Software Foundation</a> is the
+principal organizational sponsor of the <a href="http://www.gnu.org/";>GNU
+Operating System</a>. <strong>Our mission is to preserve, protect and
+promote the freedom to use, study, copy, modify, and redistribute computer
+software, and to defend the rights of Free Software users.</strong> Support
+GNU and the FSF by <a href="http://shop.fsf.org/";>buying manuals and
+gear</a>, <a href="http://www.fsf.org/join";>joining the FSF as an associate
+member</a> or by making a donation, either <a
+href="http://donate.fsf.org/";>directly to the FSF</a> or <a
+href="http://flattr.com/thing/313733/gnuproject-on-Flattr";>via
+Flattr</a>.</small></p>
+
+<p id="backtotop"><a href="#header">back to top</a></p>
+
+
+
+
+</div>
+
+
+</div>
+
+<!-- end server/footer-text.html -->
Index: server/head-include-2.hr.html
===================================================================
RCS file: server/head-include-2.hr.html
diff -N server/head-include-2.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/head-include-2.hr.html 7 Apr 2013 11:00:56 -0000 1.1
@@ -0,0 +1,11 @@
+
+
+<!-- start of head-include-2.html -->
+<link rel="stylesheet" href="/combo.css" media="screen" />
+<link rel="stylesheet" href="/layout.css" media="screen" />
+
+<link rel="stylesheet" href="/mini.css" media="handheld" />
+
+<link rel="stylesheet" href="/print.css" media="print" />
+
+<!-- end of head-include-2.html -->
Index: server/outdated.hr.html
===================================================================
RCS file: server/outdated.hr.html
diff -N server/outdated.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/outdated.hr.html 7 Apr 2013 11:00:57 -0000 1.1
@@ -0,0 +1,35 @@
+<div id="outdated">
+
+<p>The English original page has been changed since this translation was last
+updated. The English page can be found at:<br />
+
+<!--#set var="ORIGINAL_LINK"
+ value="<a href=\"${ORIGINAL_FILE}.en\">
+
+http://www.gnu.org${ORIGINAL_FILE}.en</a>" -->
+<!--#echo encoding="none" var="ORIGINAL_LINK" -->
+<!--#if expr='"${DIFF_FILE}" != ""' -->
+<br />
+Difference between the latest translated version and the current English
+version can be found at:<br />
+
+<!--#set var="DIFF_LINK"
+ value="<a href=\"${DIFF_FILE}\">
+
+http://www.gnu.org${DIFF_FILE}</a>" -->
+<!--#echo encoding="none" var="DIFF_LINK" -->
+<!--#endif -->
+<!--#if expr='"${OUTDATED_SINCE}" != ""' -->
+<br />
+The date of change in the English page is:
+<br />
+
+<!--#echo encoding="none" var="OUTDATED_SINCE" -->
+<!--#endif -->
+</p>
+
+<p>Please see the <a
+href="/server/standards/README.translations.html">Translations README</a> to
+find out how you can help with updating this translation.
+</p>
+</div>
Index: server/skip-translations.hr.html
===================================================================
RCS file: server/skip-translations.hr.html
diff -N server/skip-translations.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/skip-translations.hr.html 7 Apr 2013 11:00:57 -0000 1.1
@@ -0,0 +1,5 @@
+
+<!-- start of /server/skip-translations -->
+<p><a href="#skiptrans">Skip translations list</a></p>
+
+<!-- end of /server/skip-translations -->
Index: server/top-addendum.hr.html
===================================================================
RCS file: server/top-addendum.hr.html
diff -N server/top-addendum.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/top-addendum.hr.html 7 Apr 2013 11:00:57 -0000 1.1
@@ -0,0 +1,21 @@
+
+
+<!--#if expr="${DISABLE_TOP_ADDENDUM} == yes" -->
+<!--#else -->
+<!--#set var='link_to_english_page' value='' -->
+<!--#if expr="${ENGLISH_PAGE}" -->
+<!--#set var='link_to_english_page'
+ value='<a href="${ENGLISH_PAGE}">' -->
+<!--#endif -->
+<p class="trans-disclaimer">
+<!--#echo encoding="none" var="link_to_english_page" -->
+This is a translation of an original page in English.
+<br />
+
+<!--#if expr="${ENGLISH_PAGE}" -->
+</a>
+
+<!--#endif -->
+</p>
+
+<!--#endif -->
Index: server/gnun/generic.hr.html
===================================================================
RCS file: server/gnun/generic.hr.html
diff -N server/gnun/generic.hr.html
Index: server/gnun/compendia/compendium.hr.po
===================================================================
RCS file: server/gnun/compendia/compendium.hr.po
diff -N server/gnun/compendia/compendium.hr.po
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/gnun/compendia/compendium.hr.po 7 Apr 2013 11:00:57 -0000
1.1
@@ -0,0 +1,277 @@
+# Croatian translation of http://www.gnu.org/gnu/thegnuproject.html
+# Copyright (C) 2010 Richard Stallman
+# Copyright (C) 2013 Marin Rameša (translation).
+# This file is distributed under the same license as the original article.
+# Marin Rameša <address@hidden>, 2013.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: thegnuproject.html\n"
+"POT-Creation-Date: 2012-10-05 13:02-0300\n"
+"PO-Revision-Date: 2013-04-07 10:09+0100\n"
+"Last-Translator: Marin Rameša <address@hidden>\n"
+"Language-Team: hrvatski <>\n"
+"Language: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+"X-Generator: Poedit 1.5.4\n"
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| 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 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."
+msgstr ""
+"Molim vas Å¡aljite opÄenite FSF & GNU upite na <a
href=\"mailto:address@hidden";
+"org\"><address@hidden></a>. Postoje isto i <a href=\"/contact/\">drugi
"
+"naÄini kontaktiranja</a> FSF-a. Prekinute poveznice i drugi ispravci ili "
+"prijedlozi mogu biti poslani na <a href=\"mailto:address@hidden";><"
+"address@hidden></a>. "
+
+#. type: Content of: <div><p>
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#
+#
+#
+#. 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."
+msgstr ""
+"Radimo naporno i dajemo sve od sebe da bi pružili toÄne, visoko kvalitetne "
+"prijevode. MeÄutim, nismo osloboÄeni od nesavrÅ¡enosti. Molim vas Å¡aljite "
+"vaÅ¡e komentare i opÄenite prijedloge u tom smislu na <a href=\"mailto:web-";
+"address@hidden"><address@hidden></a>.</p> <p>Za "
+"informacije o koordiniranju i slanju prijevoda naših mrežnih stranica, "
+"pogledajte <a href=\"/server/standards/README.translations.html\">README za "
+"prijevode</a>."
+
+#. timestamp start
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr "Zadnji put promijenjeno:"
+
+#. type: Content of: <div><p>
+msgid ""
+"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. Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";><address@hidden"
+"org></a>."
+msgstr ""
+"Molim vas Å¡aljite opÄenite FSF & GNU upite na <a
href=\"mailto:address@hidden";
+"org\"><address@hidden></a>. Postoje isto i <a href=\"/contact/\">drugi
"
+"naÄini kontaktiranja</a> FSF-a. Prekinute poveznice i drugi ispravci ili "
+"prijedlozi mogu biti poslani na <a href=\"mailto:address@hidden";><"
+"address@hidden></a>. "
+
+#. type: Content of: <div><p>
+msgid ""
+"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>."
+msgstr ""
+"Ovo djelo je dano na korištenje pod licencom <a rel=\"license\" href="
+"\"http://creativecommons.org/licenses/by-nd/3.0/us/deed.hr\";> Creative "
+"Commons Imenovanje-Bez prerada 3.0 SAD</a>."
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| 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 FSF & GNU inquiries to <a href=\"mailto:address@hidden";
+"\"><em>address@hidden</em></a>. There are also <a href=\"/contact/\">other "
+"ways to contact</a> the FSF."
+msgstr ""
+"Molim vas Å¡aljite opÄenite FSF & GNU upite na <a
href=\"mailto:address@hidden";
+"org\"><address@hidden></a>. Postoje isto i <a href=\"/contact/\">drugi
"
+"naÄini kontaktiranja</a> FSF-a. Prekinute poveznice i drugi ispravci ili "
+"prijedlozi mogu biti poslani na <a href=\"mailto:address@hidden";><"
+"address@hidden></a>. "
+
+#. type: Content of: <div><p>
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";><em>address@hidden</em></a>."
+msgstr ""
+
+#. type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110, USA"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Paul Eggert"
+msgstr ""
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| 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 "
+"to contact</a> the FSF."
+msgstr ""
+"Molim vas Å¡aljite opÄenite FSF & GNU upite na <a
href=\"mailto:address@hidden";
+"org\"><address@hidden></a>. Postoje isto i <a href=\"/contact/\">drugi
"
+"naÄini kontaktiranja</a> FSF-a. Prekinute poveznice i drugi ispravci ili "
+"prijedlozi mogu biti poslani na <a href=\"mailto:address@hidden";><"
+"address@hidden></a>. "
+
+#. type: Content of: <table><tr><td>
+msgid "</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-contents.html\">Education Contents</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-cases.html\">Case Studies</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-resources.html\">Educational Resources</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-projects.html\">Education Projects</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-faq.html\">FAQ</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-team.html\">The Education Team</a>"
+msgstr ""
+
+#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</"
+#| "strong></a>"
+msgid "by <a href=\"http://www.stallman.org/\";>Richard Stallman</a>"
+msgstr ""
+"<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+
+#. type: Attribute 'content' of: <meta>
+msgid ""
+"GNU, FSF, Free Software Foundation, Linux, Emacs, GCC, Unix, Free Software, "
+"Operating System, GNU Kernel, HURD, GNU HURD, Hurd"
+msgstr ""
+
+#. type: Attribute 'content' of: <meta>
+msgid ""
+"Since 1983, developing the free Unix style operating system GNU, so that "
+"computer users can have the freedom to share and improve the software they "
+"use."
+msgstr ""
+
+#. type: Attribute 'title' of: <link>
+msgid "What's New"
+msgstr ""
+
+#. type: Attribute 'title' of: <link>
+#, fuzzy
+#| msgid "The Free Software Foundation"
+msgid "New Free Software"
+msgstr "Zaklada za slobodan softver"
+
+#. type: Content of: <h2>
+msgid "Disclaimer"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"<a href=\"/fun/humor.html\">Other humor</a> in the GNU Humor Collection."
+msgstr ""
+
+#. type: Content of: <p>
+#, fuzzy
+#| msgid "The Free Software Foundation"
+msgid "The Free Software Foundation claims no copyright on this joke."
+msgstr "Zaklada za slobodan softver"
+
+#. type: Content of: <p>
+msgid ""
+"The joke on this page was obtained from the FSF's <a href=\"http://lists.gnu.";
+"org/\">email archives</a> of the GNU Project."
+msgstr ""
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid "The Free Software Foundation"
+msgid "Copyright © 2013 Free Software Foundation, Inc."
+msgstr "Zaklada za slobodan softver"
+
+#. type: Content of: <h4>
+msgid "Footnotes"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+msgstr ""
+"<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+
+#. type: Content of: <p>
+msgid ""
+"<a href=\"/graphics/graphics.html\">Other art</a> in the GNU Art Gallery."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The GNU logo can be used verbatim in contexts talking about GNU in a "
+"supportive and accurate way. For permission, ask address@hidden"
+msgstr ""
+
+#. type: Content of: <p>
+msgid "This picture is available in the following formats:"
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Licensing"
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid "Copyright notice above."
+msgstr ""
+
+#. type: Content of: <blockquote><p>
+#, fuzzy
+#| msgid "The Free Software Foundation"
+msgid "Media Contact: Free Software Foundation"
+msgstr "Zaklada za slobodan softver"
+
+#. type: Content of: <p>
+msgid "Krishna Kunchithapadam"
+msgstr ""
+
+#. type: Content of: <p>
+msgid "Terence O'Gorman"
+msgstr ""
Index: software/recent-releases-include.hr.html
===================================================================
RCS file: software/recent-releases-include.hr.html
diff -N software/recent-releases-include.hr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ software/recent-releases-include.hr.html 7 Apr 2013 11:00:58 -0000
1.1
@@ -0,0 +1,83 @@
+<ul>
+<li><strong>April 04, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-04/msg00003.html";>GNU RCS
5.8.2 available</a>, <i>Thien-Thi Nguyen</i>, <tt>16:49</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-04/msg00002.html";>Shishi
1.0.2 released</a>, <i>Simon Josefsson</i>, <tt>03:14</tt></li>
+</ul></li>
+<li><strong>April 01, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-04/msg00001.html";>Release
of version 4.13.4 of sharutils</a>, <i>Bruce Korb</i>, <tt>11:34</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-04/msg00000.html";>GNU
AutoGen Version 5.17.3/AutoOpts Version 38.0</a>, <i>Bruce Korb</i>,
<tt>10:04</tt></li>
+</ul></li>
+</ul>
+<ul>
+<li><strong>March 30, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00023.html";>GNU
Barcode 0.99 released</a>, <i>Giuseppe Scrivano</i>, <tt>03:05</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00022.html";>GNU
gcal 3.6.3</a>, <i>Giuseppe Scrivano</i>, <tt>03:05</tt></li>
+</ul></li>
+<li><strong>March 29, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00021.html";>Denemo
0.1.0 Release</a>, <i>Richard Shann</i>, <tt>11:34</tt></li>
+</ul></li>
+<li><strong>March 27, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00020.html";>Binutils
2.23.2 released</a>, <i>Tristan Gingold</i>, <tt>19:25</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00019.html";>GNU
Serveez 0.2.1 available</a>, <i>Thien-Thi Nguyen</i>, <tt>19:24</tt></li>
+</ul></li>
+<li><strong>March 26, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00018.html";>ANN:
GWorkspace 0.9.2</a>, <i>Riccardo Mottola</i>, <tt>09:53</tt></li>
+</ul></li>
+<li><strong>March 25, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00017.html";>diffutils-3.3
released [stable]</a>, <i>Jim Meyering</i>, <tt>11:00</tt></li>
+</ul></li>
+<li><strong>March 20, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00016.html";>GNU
LibreJS 4.9.3 released</a>, <i>Loic J. Duros</i>, <tt>13:24</tt></li>
+</ul></li>
+<li><strong>March 19, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00015.html";>GNU
xorriso 1.2.8 released</a>, <i>Thomas Schmitt</i>, <tt>12:16</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00014.html";>Announcing
of maverik release 6.5</a>, <i>Hartmut Rosch</i>, <tt>09:46</tt></li>
+</ul></li>
+<li><strong>March 18, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00013.html";>Libgcrypt
1.5.1 released</a>, <i>Werner Koch</i>, <tt>14:01</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00012.html";>Announce:
GNU MPFR 3.1.2 is released</a>, <i>Vincent Lefevre</i>, <tt>11:43</tt></li>
+</ul></li>
+<li><strong>March 17, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00011.html";>GNU
MCSim version 5.5.0 released on March 17, 2013</a>, <i>Frederic Bois</i>,
<tt>18:48</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00010.html";>GNU gv
3.7.4 released</a>, <i>Markus Steinborn</i>, <tt>18:48</tt></li>
+</ul></li>
+<li><strong>March 16, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00009.html";>cppi-1.18
released [stable]</a>, <i>Jim Meyering</i>, <tt>21:18</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00008.html";>vc-dwim-1.7
released [stable]</a>, <i>Jim Meyering</i>, <tt>21:18</tt></li>
+</ul></li>
+<li><strong>March 12, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00007.html";>texinfo-5.1
available</a>, <i>Karl Berry</i>, <tt>19:30</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00006.html";>Trueprint
5.4 Released</a>, <i>Jeffrin Jose</i>, <tt>10:43</tt></li>
+</ul></li>
+<li><strong>March 11, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00005.html";>Emacs
24.3 released</a>, <i>Glenn Morris</i>, <tt>13:09</tt></li>
+</ul></li>
+<li><strong>March 10, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00004.html";>GNU
Chess release 6.0.3</a>, <i>Antonio Ceballos</i>, <tt>22:18</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00003.html";>Version
1.5 of GNU moe released</a>, <i>Antonio Diaz Diaz</i>, <tt>16:15</tt></li>
+</ul></li>
+<li><strong>March 09, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00002.html";>GNU
Marst 2.7 release information</a>, <i>Andrew Makhorin</i>, <tt>17:02</tt></li>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00001.html";>wdiff
1.2.1 released</a>, <i>Martin von Gagern</i>, <tt>17:02</tt></li>
+</ul></li>
+<li><strong>March 05, 2013</strong>
+<ul>
+<li><a
href="http://lists.gnu.org/archive/html/info-gnu/2013-03/msg00000.html";>GNU
gettext 0.18.2.1 released</a>, <i>Daiki Ueno</i>, <tt>10:54</tt></li>
+</ul></li>
+</ul>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu/po/thegnuproject.hr.po gnu/po/thegnupro...,
GNUN <=