Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

After seeing so many "dump and run" code drops on sourceforge, and now on github

I think the big difference between the two sites is that it's much easier for these types of projects to gain momentum and continue being updated on GitHub.

On SourceForge, a project would linger with no activity, bugs and feature requests would pile up, and creating a new project for a fork was a pain. I've checked out project CVS/SVN trees from SourceForge to fix things and since the projects looked dead, I never contributed the patches anywhere. I certainly wasn't going to create a new SourceForge project just to host my one patch. The few times I've created bugs for the patches, they never got any attention.

With GitHub, it's much easier to fork a repo, fix a bug, and push the fix back up for everyone to see, even if it never gets turned into a pull request or accepted upstream, lingering in your own git repo never to be touched again. Since GitHub shows your fork on the original project's fork tree, it's easy for other users to find your fork with your bugfix and continue that momentum by forking your fork, fixing their own bug, and so on.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: