Just some comments :
* WHERE : why not sourceforge.net ? they provide a lot of tools.
* HOW : I know that on sourceforge we are able to manage sevral branch
mainly -stable and -devel. So I suggest to release 6.2.6 as stable branch
and doing some devel stuff based on it.
As far as code control goes, Subversion was generally favored
over CVS, so
if possible we will try to host the code with Subversion.
I believe that a bug-tracking system is quite important, and in fact tend
to prefer that, once we have one, all patches be submitted through it.
The code plan, as I see it, will be to first put 6.2.5 into code control,
add whatever "round 1" patches are deemed necessary (bug fixes only, no
major feature addition or removal), then do a release (What number
designation? 6.2.6? 126.96.36.199?) with announcements of the new management
going to all the usual places. (I'd love it if someone could
come up with
a list of the usual places and their contact info.) Then we work
2, probably the UID stuff.
At this point I'd suggest that we try Berlios first, and if they don't
accept the project or just ignore us, we fall back to Alioth. Further
comments, suggestions, and arguments for or against a particular site are
quite welcome, preferably soon.
I'd suggest that the new project have its own development mailing list.
Whether user assistance stays on fetchmail-friends or goes to
is something we can discuss later among the community of developers and