Ideas for Google Summer of Code 2006

These are possibilities, and won't be considered until they're listed in the real page at http://wiki.apache.org/general/SummerOfCode2006 . Anyone who's planning to mentor for these will also need to sign up there foo. Please adopt the templates used in that page.

Subject ID: spamassassin-easy-mass-check

Title: Nightly Mass Check for Normal People

ASF Project: SpamAssassin - http://SpamAssassin.apache.org/

Keywords: perl, email, corpora, distributed, community

Description:

We need a way to make nightly mass check easily accessible to normal users. They need easy to use software to do mass checks and submit results. They must be properly trained on the sorting rules. Our project then needs some way of tracking the level of trust of these growing number of submitters. see SocNightlyMassCheck

Possible Mentors: Justin Mason (jm at jmason.org)

Status: -

Subject ID: spamassassin-persistent-db-conns

Title: Persistent database connections

ASF Project: SpamAssassin - http://SpamAssassin.apache.org/

Keywords: perl, databases, sql

Description:

'persistent DB connections (suggested by Michael last year); This exists, but is not an ASL friendly license. So a "clean room" implementation might be cool.'

Possible Mentors: -

Status: -

Subject ID: spamassassin-separate-expiry

Title: Helper process for Bayes expiry

ASF Project: SpamAssassin - http://SpamAssassin.apache.org/

Keywords: perl, bayes, spamd, processes

Description:

Theo said: 'I also suggested having things like Bayes expiry and such being passed back to the parent who can spawn a helper process to do the work. That way the children processes will be able to accept, process, return the result, notify parent for bayes work, go back to listening. Right now we do: accept, process, do bayes work, return result, go back to listening, which ends up causing timeouts and possibly eats up all processing children.'

Possible Mentors: -

Status: -