> > > Surely AOL could provide this as a way of thanking the efforts of > > > the community developers? > > > > The downside of this is that no one from outside of AOL could ever get > > access to make changes to the site, because of the way security is set > > up. > > > > Right now, anyone inside or outside of AOL can make changes to the > > aolserver.com site if they're a project member of the AOLserver > > SourceForge project because aolserver.com is also hosted at > > SourceForge. > > How about a middle of the road solution on the website?
I thought that SF was a good middle-of-the-road solution. While you might separate the website (as many larger SF-hosted projects do), I would not encourage separating the CVS or download areas. > I can offer a home for the website with good connectivity at > this time I can give up the bandwidth for the cvs and > download areas. Also, I don't have any extra boxes lying What is your backup plan? What is your redundancy plan? These are some of the critical background features that SF offers. Sure, it has some downtime as well, but they offer a lot in terms of the general system for dev management. I would not be so quick to dismiss it. Moving the standard website hosting off it isn't a bad idea though. Jeff -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
