On Tue, 9 Sep 2003, Tom Collins wrote:
> I have forked ownership since I felt that Inter7 was doing a poor job
> of maintaining vpopmail and qmailadmin. I readily acknowledge that Ken
> created vpopmail and qmailadmin. They're GPL projects, so I'm free to
> fork them if I like. Since moving the projects to SourceForge, we've
> kept up with submitted patches and bug reports. I feel that making the
> move was beneficial to the projects themselves and the people that use
I fully agree, and my rose-colored glasses are not on. People are
complaining about the rapid release process right now, but I think that's
to be expected. It seems there's a big cleanup in progress, and that will
stir up bugs. Always has, always will. I for one gladly accept this
because I have faith that the final product will be greatly improved.
> I'm certainly not doing this to be malicious or to hurt Ken and Inter7.
As a user, not a developer, I don't see anything malicious.
> Ken Jones hasn't contributed to vpopmail and qmailadmin development
> since March. We've had 12 qmailadmin releases and 7 vpopmail releases
> since then. Managing the projects on SourceForge keeps everything out
> in the open, and allows anyone to contribute.
And this is very important. I have no beef with Inter7, but if you look
at the mailing lists, you'll see patch after patch disappear into the
ether, never to be incorporated into the source. As a user, I want to see
forward motion, even if there are periods of instability. Having been a
user of free software for more than 7 years, I must say this is not at all
shocking. I really look forward to seeing CVS set up (and can offer a cvs
server for both public and developer use) and seeing more people use SF
resources to submit and track bug reports.
Without dissing Ken and Inter7, I have to say that I find Tom to be very
responsive, and it's obvious he's putting a huge amount of personal time
into moving the project forward.
I see no reason for people to pick this very time to crawl out of the
woodwork and bitch about the "instability" of current vpopmail code,
implying that past releases were really that much more "stable".
vpopmail has always been very close to "coming together", and now we've
got some great progress in cleaning things up.
Thanks to all involved,
> 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/