3 ms·
An enormous difference (which was one of the reasons that I moved to Google Code and GitHub) was that on SourceForge one had to request a project and the SF sta
by danieldk 9y ago
An enormous difference (which was one of the reasons that I moved to Google Code and GitHub) was that on SourceForge one had to request a project and the SF staff had to approve the project. They would reject projects for all kinds of silly reasons.
On GitHub, you could just create a project and get going.
- octalmage 9y agoI switched to Google Code for the same reason. The fact that I had to ask someone before I could create a new repo was insane. It took days to get a new project up and running on SF. Google Code was a little bit nicer but they just let it fall behind the times.
- mcphage 9y agoAbsolutely. SourceForge tried to act as gatekeepers of what was worth hosting. GitHub got out of your way. Much better approach.
- ZephyrP 9y agoI put my project (a small, windows-only WEP cracker for a very specific wireless device) on SourceForge "for free" -- it was a huge hassle to be sure, having to upload new versions with FTP and so on. It was free and 'gatekeeperless' however.
- mcphage 9y agoI've learned (from this topic coming up other times) that there were times you didn't need approval for new projects on SF, but there definitely were times where you did. I don't know when, perhaps when they dropped the restrictions I had already moved on to github?