[SpamAssassin Wiki] Updated: ClaVettingProcess

[co...@spamassassin.apache.org]

   Date: 2004-09-26T18:34:18
   Editor: DanielQuinlan <qu...@pathname.com>
   Wiki: SpamAssassin Wiki
   Page: ClaVettingProcess
   URL: http://wiki.apache.org/spamassassin/ClaVettingProcess

   minor editing

Change Log:

------------------------------------------------------------------------------
@@ -9,10 +9,12 @@
   * the CVS logs of the code: http://cvs.sourceforge.net/viewcvs.py/spamassassin/spamassassin/
   * comments in the code itself
   * data in the bug tracking system: http://bugzilla.spamassassin.org/
-  * mailing list traffic from the Spamassassin-talk and Spamassassin-devel lists: http://news.gmane.org/gmane.mail.spam.spamassassin.general, http://marc.theaimsgroup.com/?l=spamassassin-talk, http://news.gmane.org/gmane.mail.spam.spamassassin.devel, http://marc.theaimsgroup.com/?l=spamassassin-devel 
+  * mailing list traffic from the spamassassin-talk and spamassassin-devel at sourceforge.net:
+    * talk archives: [http://news.gmane.org/gmane.mail.spam.spamassassin.general gmane], [http://marc.theaimsgroup.com/?l=spamassassin-talk theaimsgroup]
+    * devel archives: [http://news.gmane.org/gmane.mail.spam.spamassassin.devel gmane], [http://marc.theaimsgroup.com/?l=spamassassin-devel theaimsgroup]
   * http://spamassassin.org/credits.html - the "credits" web page for the project
 
-Note for NAI readers: this differs from the NAI process, in that we assembled a list of *all* contributors from the entire project lifetime.  In other words -- it was not performed based on what was in the lines of code we wanted, since we needed to "cleanse" the entire codebase.
+Note for NAI readers: this differs from the NAI internal process, in that we assembled a list of *all* contributors from the entire project lifetime.  In other words -- it was not performed based on what was in the lines of code we wanted, since we needed to "cleanse" the entire codebase.
 
 Initial list was: http://taint.org/wk/SAContribList?action=recall&date=1065743884
 
@@ -50,7 +52,7 @@
 
 Next comes the name and email address, followed by a "where is the CLA" field used to track CLAs in transit, and finally, a textual description of what the change was, where it went, when, and whether it is still required.
 
-The list is complete; all contributors fall into these piles:
+The list is complete; all contributors fell into these piles:
 
   * Code removed -- their contribution either became obsolete and was removed, was rewritten, or was removed due to difficulties getting a CLA
   * Third party with CLA, and CLA confirmed -- they sent in a CLA, and Apache have confirmed its receipt