-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Theo Van Dinter wrote:
> On Thu, Jun 02, 2005 at 09:30:52AM -0700, Justin Mason wrote: > >> can anyone think of good SpamAssassin projects for this? I'm a >> bit stumped ;) > > > There's a bunch of stuff we want to get done, I just don't know if > any of it really works well as a contained project. A quick random > brainstorm: > > - Setup the backend of the updates system, get it working, start > publishing updates for 3.0 and 3.1. - Get short-circuiting working > - Part of me wants to split off the rules into a subproject, > possibly doing releases via the updates system, but at least being > able to move faster, do faster release cycles, etc. More to the > goal of "SpamAssassin" as engine as well. > > An actual possibility is: > > - Build a real/full test suite. "make test" is a high level check > for most things, but we've been talking about having a "several > thousand" large test system to get down and check the nity-grity > bits in the code. Regressions for all fixed bug tickets, etc. > Well, I responded to Theo's first msg on this, but it's lost in the ether somewhere, so here goes again, sorry if it ends up being a dupe. The most obvious list is: http://wiki.apache.org/spamassassin/WeLoveVolunteers Discussions on other lists are pointing out that to be eligible it had to be a coding project, so updates backend and rules subproject may not qualify. I like the beefing up of our tests, but again it might be marginal. There are a number of enhancement bugs in Bugzilla, so there is a good source. Off the top of my head, how about persistent DB connections or pluginizing the Bayes subsystem. Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCn0U0G4km+uS4gOIRAtrJAJkBoT7gG2O1Fv4DnQ948dBS71ke3QCeP+tq 4JS65Tr4gTsOYAcETWyS2wo= =wx0x -----END PGP SIGNATURE-----
