On Nov 28, 2007 12:47 AM, Andreas Schneider <[EMAIL PROTECTED]> wrote: > Mick Johnson wrote: > > Sensory Networks continues to maintain these mailing lists, the website, and > > the mirror system (currently attempting to reconnect 2 of the disconnected > > mirrors). I have 10 - 20 currently outstanding patches, depending on whether > > you count by email or section of code, and we are attempting to schedule a > > future release candidate. > > Could you please apply the patches and update CVS so that not everyone is > doing the same patch again and again. It would be even better to switch to git > instead of CVS.
I concur. Ideally, development of dspam would occur in the open. This means that patches and updates to dspam that are intended to go into the next release show up in CVS (or similar) as soon as possible. > > We'll be putting out the next patch release early next year, and would like > > anyone interested in being a tester to please drop us a line! You can always > > Sorry, I don't understand why this is required. Create a source package > release it to the public. People will try and test it and report back to the > dev mailing list. There are a lot of people doing patches atm. Again, I concur. At the very least, there are enough patches floating around to warrant a 3.8.1 release. I'm afraid that if development doesn't happen out in the open, it will be more difficult to attract outside developers and testers. If that is not a priority and development remains behind closed doors, then I would suspect that would motivate people to fork the project. Just look at all the discussion that has take place about forking dspam recently because of the lack of response from Sensory Networks. I am excited to see some response from Sensory Networks. I hope that development can continue as dspam is an excellent spam filter. Regards Dave
