moving to SourceForge

[Stephen Weeks]

> FWIW: we considered Sourceforge here and after trying to setup a reasonable
> environment for about 3 weeks gave up.  Erice Beuscher who is a fairly 
> competent Unix hacker told me that there were too many undocumented features
> that made it impossible to use.  I think it was especially hard to use for
> remote development.  We stuck with CVS.  Of course, VA Linux has a number of
> different schemes and installation choices so the one we were looking at may
> have been quite different than what you're thinking of, but the end analysis
> was pretty negative.  I'll try to dig up more details if you're interested.

Please do.

One thing that you said that doesn't make sense to me is that CVS is
one of the main things that SourceForge (and the GNU spinoff,
Savannah) provides.  I think that our interaction with their CVS would
be the same as with the one on Sourcelight.