FSF Migrating From Savannah to Gforge
bluestrain writes "It's been almost 4 months since Savannah was hacked. The site is still not completely functional, no new projects have been accepted since December 2003. Now it seems that the FSF is abandoning Savannah in favor of Gforge. RMS himself has
confirmed the plans. A few developers are questioning the change. Hopefully the dust will settle and savannah can start accepting projects again."
I don't have time to discuss this further. I am in the hospital and falling behind on my other work.
He's in hospital? Nothing serious, I hope.
SpamNet - a spam blocker that really works
GForge doesn't actually host projects (besides its own). It is simply a software package used to maintain and coordinate development efforts. If/when the FSF switches to GForge, it will be up to them to provide the resources necessary to handle the large amounts of traffic and projects. That responsibility does not fall on GForge.
-- Fighting mediocrity one bad post at a time.
Sourceforge, also code named Alexandria. Original concept of a public development and collaboration for Open Source Projects. Last code base available was about 2000 before VA took the project Closed source for commercial purposes.
Savannah: Fork of Alexandria code for GNU projects. I evaluated it but it was too kludgy to understand.
GForge: Fork of Alexandria code by former Sourceforge developer. Rips out foundries and is for optimized PHP and Postgresql and Apache. Patches for Oracle in beta, refuses mysql patches.
Novell Forge: Fork of XoopsForge that uses LDAP and Novell directory server. Needs Xoops 2.0 to run.
XoopsForge: Fork of Alexandria that runs as a module in Xoops. Not much Dev activity, most dev in Novell Forge.
MyXoopsForge: Fork of XoopsForge that has some active development. Used for forge.xoops.org
The only thing that may compete in the same space that is somewhat similar is PHPGroupWare.
-Electrawn