X-Git-Url: https://projects.mako.cc/source/fspm_howto/blobdiff_plain/869d3b22b455151bd328cf142e3cbfd6df810246..8ecfa07384512fddf82fea3f8f15e40226489931:/FreeSoftwareProjectManagementHOWTO.sgml

diff --git a/FreeSoftwareProjectManagementHOWTO.sgml b/FreeSoftwareProjectManagementHOWTO.sgml
index d85158d..6d4bd70 100644
--- a/FreeSoftwareProjectManagementHOWTO.sgml
+++ b/FreeSoftwareProjectManagementHOWTO.sgml
@@ -17,6 +17,13 @@
     </address>
    </affiliation>
   </author>
+  <revhistory>
+   <revision>
+    <revnumber>v0.2.1</revnumber>
+    <date>10 April 2001</date>
+    <authorinitials>bch</authorinitials>
+   </revision>
+  </revhistory>
   
   <revhistory>
    <revision>
@@ -250,6 +257,13 @@
     In this version I have the pleasure of acknowledging:
    </para>
 
+   <para>
+    Josh Crawford, Andy King, and Jaime Davila who all read through
+    this beast and gave me feedback that has helped me make changes
+    and improvements to this document. I can't thank you guys enough
+    for your help.
+   </para>
+
    <para>
     <emphasis>Karl Fogel</emphasis>, the author of <emphasis>Open
     Source Development with CVS</emphasis> published by the Coriolis
@@ -393,11 +407,10 @@
     <title>Identify and articulate your idea</title>
     <para>
      Eric S. Raymond writes about how free software projects start in
-     his essay, <quote>The Cathedral and the Bazaar,</quote> which
-     comes as required reading for any free software developer. It is
-     available <ulink
-     url="http://www.tuxedo.org/~esr/writings/cathedral-bazaar/">online
-     </ulink>.
+     his essay, <ulink
+     url="http://www.tuxedo.org/~esr/writings/cathedral-bazaar/"><quote>The
+     Cathedral and the Bazaar,</quote></ulink> which comes as required
+     reading for any free software developer. It is available online .
     </para>
 
     <para>
@@ -754,8 +767,9 @@
     <para>
      The text of the <acronym>GPL</acronym> offers <ulink
      url="http://www.gnu.org/copyleft/gpl.html#SEC4">a good
-     description</ulink> of mechanics of applying a license to a piece
-     of software. My quick checklist for applying a license includes:
+     description of the mechanics of applying a license</ulink> to a
+     piece of software. My quick checklist for applying a license
+     includes:
     </para>
 
     <para>
@@ -1946,18 +1960,19 @@ pages for more information and options.
      freeze in effect.
     </para>
    </sect3>
+  </sect2>
 
-   <sect3>
-    <title>Forking</title>
+   <sect2>
+    <title>Forks</title>
     <para>
-     Forks are like the most extreme version of a branch. A fork is
-     when a group of developers takes code from a free software
-     project and actually starts a brand new free software
-     project with it. The most famous example of a fork was between Emacs and
-     XEmacs. Both emacsen are based on an identical code-base
-     but for technical, political, and philosophical reasons,
-     development was split into two projects which now compete with
-     each other.
+     I wasn't sure about how I would deal with forking in this
+     document (or if I would deal with forking at all). A fork is when
+     a group of developers takes code from a free software project and
+     actually starts a brand new free software project with it. The
+     most famous example of a fork was between Emacs and XEmacs. Both
+     emacsen are based on an identical code-base but for technical,
+     political, and philosophical reasons, development was split into
+     two projects which now compete with each other.
     </para>
 
     <para>
@@ -1977,7 +1992,6 @@ pages for more information and options.
      absolutely unresolvable, I recommend Fogel's book as a good place
      to start.
     </para>
-   </sect3>
   </sect2>
  </sect1>