Page History

...

• RuleDevelopment: some notes on rule development.
• UsingBugzilla: What to watch out for when using SpamAssassin's bug tracker.
• DevBookmarks: some good bookmarks for SA developers and contributors.
• CodingStyle: To be written.
• NextRelease: Might contain a schedule for the next release.
• DownloadFromSvn: How to download the latest version of SpamAssassin from Subversion.
• VotingProcedure: We follow the ASF way of doing things like this.
• DevelopmentMode: The difference between C-T-R and R-T-C, etc.
• ProjectRoles: Users, Contributors, Committers, PMC members

Historical information 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 the resolution of the process
  

• ContinuousTesting: our continuous testing system
  

Stuff about scoring

• TenFoldCrossValidation: How to test the accuracy of the scoring system
• NightlyMassCheck: How to run nightly mass-check runs to help with rule scoring
• RescoreMassCheck: How to generate a new score-set (the big mass-check run)
  

...

• MailManglingInTheField: Information about known ways a mail message can be changed in transit.

• Wiki Markup
  \[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.

• Wiki Markup
  \[http://spamassassin.apache.org/gtube/ GTUBE\]: the Generic Test For Unsolicited Bulk Email.

• Package Building: RPM's, etc.
  

Historical information 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 the resolution of the process
  

...

CategoryDevelopment