You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This stuff will most likely not be terribly useful to those not interested in SpamAssassin development:

Introduction

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 [http://svn.apache.org/repos/asf/spamassassin/ HTTP] and WebDAV (replace the http scheme with webdav to browser the repository – [MoinMoin] doesn't like webdav-links). There are also [http://svn.apache.org/snapshots/spamassassin/ snapshots] of the current development tree available.

General stuff

Stuff relating to the Incubation process

  • IncubatorToDo: To-do list for moving out of the Apache Incubator
  • ClaVettingProcess: How we tracked down code owners in order to relicense, and current status.

Stuff about scoring

More Stuff

  • MailManglingInTheField: Information about known ways a mail message can be changed in transit.
  • [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.

  • Package Building: RPM's, etc.

I'm sure more stuff should be added here. Please help out (wink)

(TheoVanDinter)

  • No labels