docs/diploma

diff thesis/tex/2-FreeSoftwareProjects.tex @ 50:f944ca6dd688

added CATB cite; added unbreakable spaces
author meillo@marmaro.de
date Tue, 14 Oct 2008 21:59:22 +0200
parents a60b2d32b597
children 34bc9138c3d9
line diff
     1.1 --- a/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 19:43:31 2008 +0200
     1.2 +++ b/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 21:59:22 2008 +0200
     1.3 @@ -4,7 +4,7 @@
     1.4  To understand \freesw\ projects, one needs to understand \freesw\ itself first.
     1.5  
     1.6  \section{About \freesw}
     1.7 -The term ``Free Software'' was coined by the \name{Free Software Foundation} (short: \NAME{FSF}), founded by Richard M.\ Stallman (known as ``RMS'') in 1985.
     1.8 +The term ``Free Software'' was coined by the \name{Free Software Foundation} (short: \NAME{FSF}), founded by Richard~M.\ Stallman (known as ``RMS'') in 1985.
     1.9  Although various licenses make software free, none of them represents the thinking of \freesw\ like the the \GNU\ \gpl\ (short: \GPL). Its first version was written by Stallman in 1989.
    1.10  One could say, the \GPL\ catalized the \name{Free Software movement}.
    1.11  
    1.12 @@ -45,7 +45,7 @@
    1.13  
    1.14  The other, now less common, method is a more closed group, developing in a ``sealed'' room, but releasing finished versions to the public.
    1.15  
    1.16 -Eric S.\ Raymond discusses about these methods, which he named \name{the bazaar} and \name{the cathedral}. %FIXME: add reference
    1.17 +Eric~S.\ Raymond discusses about these methods, which he named \name{the bazaar} and \name{the cathedral}. %FIXME: add reference
    1.18  
    1.19  The following text will focus on the ``bazaar'' model.
    1.20  
    1.21 @@ -96,7 +96,7 @@
    1.22  This makes it interesting for other developers to join.
    1.23  Developers are the core of a community.
    1.24  
    1.25 -Third, there is a rule of thumb that should be followed: ``Release early, release often!'' %FIXME: add reference
    1.26 +Third, there is a rule of thumb that should be followed: ``Release early, release often!'' \cite{catb}.
    1.27  Releases are (more) stable versions, primary for users.
    1.28  They should be created, frequently.
    1.29  People will more likely use programs of active projects.