| |||||||||||||
|
| |||||||||||||
SourceForge goes to DB2SourceForge goes to DB2Posted Aug 15, 2002 6:08 UTC (Thu) by mauriceh (guest, #3267)Parent article: SourceForge goes to DB2
This was inevitable There is a word for people like this:
(Log in to post comments)
SourceForge goes to DB2 Posted Aug 15, 2002 19:17 UTC (Thu) by jasone (guest, #2423) [Link] Referring to VA as whorish is in my opinion quite unfair. "Misguided" or "shortsighted" might be reasonable descriptive terms, but ultimately, SourceForge has been a continuing gift to the open source community that we shouldn't scoff at. Unfortunately, VA hasn't been able to come up with a sustainable business model to support the gift, but that doesn't make it less of a gift.That said, I have never been comfortable with trusting SourceForge with my work, precisely because I fear its unsustainable business underpinnings will cause it to go away. Last I checked, there still wasn't a good way to migrate projects (cvs repository, mail logs, bug databases, etc.) back out of SourceForge, which would cause me much anxiety, given the uncertain future of SourceForge.
SourceForge goes to DB2 Posted Aug 18, 2002 3:44 UTC (Sun) by puetzk (guest, #3318) [Link] I don't know about bug databases and mailing archives, but getting your CVS out of sourceforge (or just backing it up) is quite easy... I've never had occasion to look for the others, but as the CVS HOWTO on sourceforge explains, http://cvs.sourceforge.net/cvstarballs/ contains tarballs of the cvsroot for each project, generated nightly. So that part is not a big deal, other than finding another place to host it that's half as good :-) (end-users note - these are not cvs snapshot tarballs, they are copies of the full repository including all revision history, suitable for setting up a new cvs server with all the old info, not for direct use). -- and no, I have no connection to sourceforge, not even a project hosted on it :-)
|
|
||||||||||||