...
Wiki Markup Log into \[http://bugzilla.spamassassin.org Bugzilla\] and look for bugs that you can fix. Fix it, and attach a patch (from latest SVN) to the bug report. See also [UsingBugzilla]. \\
Documentation
- The best source of documentation for SpamAssassin is this wiki; unfortunately, most users look for documentation elsewhere - man pages, READMEs, etc. We need people to submit patches to improve the documentation, to improve its accuracy, completeness, and clarity. If you also know perl, you can also read our code to ensure the documentation agrees with what the code does, or to write man pages for perl modules that don't currently have one (see man perlpod). (We've often had problems with READMEs that document the old behaviour of the code.) Really, anyone can help us with this; if you don't understand perl, simply reading the docs to suggest any improvements is helpful. (DuncanFindlay)
New Rules
Wiki Markup We are looking for an individual (or many individuals) to help us write new rules, and help us add rules written by others (i.e. rules from [CustomRulesets], with permission of course) into our code base. A good knowledge of [SpamAssassin] and experience writing rules would be useful. Let us know if you're interested by sending mail to the \[http://spamassassin.org/lists.html Spamassassin-dev mailing list\]. Generally the developers are focused more on code issues rather than rules, so the more help we get in the rules department means we have more time to devote to writing code. \\
...