My only two points:
1) *IF* there is a fork, with two codebases, follow the others' suggestions and name the new fork differently so that we can have sane discussions about which program we are dealing with on any given matter.
2) *IF* there is a fork, and for either fork, manage releases and bug checking with the CVS "proving ground" to deal with dev. issues. I would be hard pressed right now to recommend a particular "stable" version of vpopmail due to the heavy (and very welcome) rapid development and code polishing efforts over the last two months.

I LOVE the product, the confusion scares me. D.

Tom Collins wrote:

On Tuesday, September 9, 2003, at 10:07 AM, Ken Jones wrote:

Just so everyone knows. Tom Collins is attempting
to fork the vpopmail project. He refuses to let me
share ownership of the vpopmail and qmailadmin
projects on source forge. When I asked him to
add me as an owner on the project he said he
refuses now and at any time in the future to
allow me to share ownership.

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 them.

I'm certainly not doing this to be malicious or to hurt Ken and Inter7.

I've told Ken that he's more than welcome to contribute to the project on SourceForge, or to maintain his own version of vpopmail and qmailadmin. I also stated that until I stopped actively maintaining vpopmail and qmailadmin, I saw no need to add him as a project administrator. Michael Bowe has been actively involved with vpopmail development, and I had no problem adding him as an admin.

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.

Ken hasn't stated why he wants to be an owner of the project. I'm not sure I understand what he loses out on by being a developer on the project and not an admin.

Tom Collins
QmailAdmin:  Vpopmail:
Info on the Sniffter hand-held Network Tester:

Reply via email to