1. Contributing to the Wiki
You can edit any page by pressing the Edit text link at the bottom of the page. Because the Wiki has been repeatedly defaced by spammers, you must create an account and log in before you can edit any pages. You can do this via UserPreferences.
Capitalized words joined together form a WikiName, which hyperlinks to another page. The highlighted title searches for all pages that link to the current page. Pages which do not yet exist are linked in bold red: just follow the link to create that page. If you want to experiment before making changes, please use the WikiSandBox.
To learn more about what a Wiki is, read about WhyWikiWorks. Also, you can consult the WikiWikiWebFaq.
2. Contributing to the SpamBayes project
There's a whole bunch of things that you could do, starting with the non-technical:
-
Try to reproduce bugs that we're having trouble reproducing; see the bug list at http://sourceforge.net/tracker/?group_id=61702&atid=498103 (807217 is my personal hate figure).
-
Help with testing; we're only able to test within our own environments, and only the developers who are around at the time of a release are able to do even that. Some "real people" who could help test in their environments would be a big help.
-
Help improve the website; there's a Wiki page about that at http://www.entrian.com/sbwiki/WebSiteDevelopment
-
Help improve the documentation, especially for the non-Outlook applications (POP3 proxy, IMAP filter, Notes filter, sb_filter).
-
Help out newbies on the mailing list.
-
Make contributions to the Wiki - any hints and tips, scripts, recipes etc.
-
Take part in discussions on the developer's mailing list at spambayes-dev@python.org. You don't need to be a developer to participate, you just need to have a decent grasp of the project and have opinions about how it should be developed.
For those with programming skills, there's even more you could help with, even without in-depth knowledge of the code. The code's pretty accessible, and developers are always glad to answer questions about how it all works. Here's a small list off the top of my head:
-
Test patches, tidying them up, making them fit the coding standard (http://www.python.org/peps/pep-0008.html) if they don't already. See http://sourceforge.net/tracker/?group_id=61702&atid=498105
-
Fix bugs - turning a bug report into a patch makes it far more likely to be fixed!
-
Improve our unit tests, or help develop an acceptance test framework.
-
Once you've got a handle on how the code works, implement feature requests.
-
Backport bugfixes from the head onto the bugfix branch, although our branch strategy is a little up in the air at the moment, so that's one for the future.
-
Help with sailing our fleet of luxury yachts from the Caribbean to the Med for the Spring season... or am I dreaming again?
There are probably a dozen other things that I haven't thought of.
3. Contributing to the source code
If you have a bugfix or an enhancement to the SpamBayes source code, you should make a context diff against the current CVS trunk and submit it to the SourceForge patch manager via the SpamBayes project page.