a question for tom, if ken does participate as a developer, and contributes in a manner representative of a lead developer, at a later time would you consider adding him as an administrator?
Definitely. Up until now, I haven't seen a need for Ken to have admin access. I'll admit that I was hesitant to add Ken as an admin on the off chance that he would then demote me from admin status, thus preventing me from releasing files or modifying the trackers.
I have been learning about CVS today, and will have a CVS repository of the current versions of vpopmail and qmailadmin available within the next 24 hours. I want to make sure I have a full understanding of how CVS works so I can make sure I set it up properly (and know how to correctly commit future changes).
I'd like to discuss a system for managing updates and deciding on how to test a release for stability before releasing it. 5.2.1 is an old release, and we've incorporated many bug fixes and new features into the 5.3 line. Michael Bowe back-ported many bug fixes to a 5.2.2 release available on SourceForge, but we don't have the resources to test it and declare it stable.
My goal has been to get to a 5.4 release from the current 5.3 series. I personally use 5.3.20 on my production server, and perhaps it would be a good idea to include information on the site as to the most recent "stable" development release for those who like to live on the cutting edge (and will keep up with the mailing list for announcements of bug fixes).
I would like to find a way for Inter7 to embrace the projects on SourceForge, and even consider moving some of their other projects there (like vqadmin). I'm more than happy to just contribute code if others can do file releases and (more importantly) additional testing and quality control.
-- Tom Collins [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/