1.1 --- a/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 11:48:58 2008 +0200
     1.2 +++ b/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 12:23:10 2008 +0200
     1.3 @@ -4,24 +4,24 @@
     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. %FIXME: check date
     1.8 -Although various licenses make software free, none of them represents the thinking of \freesw\ like the the \GNU\ \gpl\ (short: \GPL), which was written by Stallman in 1983.
     1.9 -One could say, the \GPL\ ``powered'' the \name{Free Software movement}.
    1.10 +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.11 +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.12 +One could say, the \GPL\ catalized the \name{Free Software movement}.
    1.13  
    1.14 -But after all, the \GPL\ was not the first \freesw\ license used.
    1.15 -The \name{BSD License} for example is much older; with first occurences around 19xx. %FIXME: insert date
    1.16 -However, nobody talked about ``Free Software'' back then.
    1.17 +After all, the \GPL\ was not the first \freesw\ license used.
    1.18 +The \name{MIT License} (or \name{X Consortium License}) for example is older; published in 1988.
    1.19 +Licenses providing the same rights have been used since long time ago.
    1.20 +But none of them was so often (re)used by other projects---thus gattering less awareness.
    1.21 +Further more was the \GPL\ created to be a \emph{general} license for all kinds of programs, unlike most other licenses written for one particular program.
    1.22  
    1.23  \freesw\ gives freedoms to its users.
    1.24  In contrast to proprietary software restricting the users freedom.
    1.25 -The freedoms (or rights) the user has are stated in %FIXME where?
    1.26 -. Namely these are:
    1.27 +The freedoms (or rights) the user has are stated in the \name{Free Software Definition} of the \NAME{FSF}. Namely these are:
    1.28  \begin{enumerate}
    1.29 -	\item The freedom to use
    1.30 -	\item The freedom to copy and share
    1.31 -	\item The freedom to study the source code
    1.32 -	\item The freedom to modify
    1.33 -	\item The freedom to redistribute (granting the same freedom)
    1.34 +	\item The freedom to run the program, for any purpose (freedom 0).
    1.35 +	\item The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
    1.36 +	\item The freedom to redistribute copies so you can help your neighbor (freedom 2).
    1.37 +	\item The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.
    1.38  \end{enumerate}
    1.39  
    1.40  
    1.41 @@ -67,8 +67,7 @@
    1.42  Be it on the mailing list, the discussion board, or by telling the developers about a new feature wanted.
    1.43  
    1.44  There will hardly be a community if no communication channels are available.
    1.45 -If the development team does not provide them, there is a chance that enthusiastic %FIXME: better word
    1.46 -users set them up on their own.
    1.47 +If the development team does not provide them, there is a chance that encouraged users set them up on their own.
    1.48  But this is rare and the program needs to be very popular. %TODO: maybe include an example here (w3m?)
    1.49  
    1.50  Projects without a good community tend to die sooner or later.