Tim Perdue on GForge & Building SourceForge
Steve Mallett writes "I've just posted an interview I did with Tim Perdue, former co-'head honcho' responsible for developing SourceForge. You'll either love it or hate the interview, but it's on his new project GForge, a fork of the previously open source code running SF, while he shares some insight in what seems like a miracle that SourceForge was built at all." Obviously Slashdot's parent runs
SourceForge, so insert whatever mental disclaimer and conspiracy theory you
want here.
Before it got /.-ed, Tim had posted something to the effect that "Ripped out lots of hacks and ugly code, as GForge doesn't need to scale to 500,000 users".
GForge is meant more for people to use internally and has some very cool (planned) features that I'm looking forward to (and looking forward to helping out with, if I can), such as:
Ryan T. Sammartino
"Ancora imparo"
The web page implies that gforge requires php4, which, last I checked, contained and required the GPL-incompatible zend "engine." Does anyone know how much work would be involved in porting gforge to (GPL compatible) php3?
from the website:
>Since VA has not released the source in over one year, despite their promises to the contrary, a fork was necessary to ensure a viable open source version of the codebase.
>
so i went over to the site in question (sourceforge.net) and was unable to determine anything about the software which is used to run SF.
So... does Tim have a legit beef? I do not know the history of SF.net enough to know. Is the sf.net code open? Is it VA or OSDN owned? Is it proprietary?
just curious.
It just seemed out of the norm since they've been pretty good about slashcode and all....
guns kill people like spoons make Rosie O'Donnell fat.
On a related note, Sharp Electronics launched ZAURUS.COM today, which includes a Sourceforge 2.5 based custom implementation designed by Tony Guntharp, Tim Purdue's colleague in the original SourceForge project.