Generally, we coordinate the overall flow on the SpamAssassin-Users and SpamAssassin-Dev [MailingLists]. Then, for specific new functionality or rules, a \[http://bugzilla.spamassassin.org/ Bugzilla bug\] should be created to track progress and provide a forum for discussion; any patches should be stored (as an attachment) on that Bugzilla bug. |
The code itself is maintained in a \[http://subversion.tigris.org/ Subversion\] repository which can be browsed via the following methods: |
a web UI on SVN history via this \[http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/?root=Apache-SVN ViewCVS view\] |
\[http://svn.apache.org/snapshots/spamassassin/ periodic snapshot tarballs\]. \\ |
\[http://spamassassin.apache.org/publiccorpus/ The SpamAsassin public corpus\]: an old collection of hand-filtered ham and spam for testing GA work, developing new filter techniques, and benchmarking filters. |
\[http://spamassassin.apache.org/gtube/ GTUBE\]: the Generic Test For Unsolicited Bulk Email. |