5 ms·
There was some article on the intertubes about how Github panders to devs, while Sourceforge panders to distributers.
by wisty 15y ago
There was some article on the intertubes about how Github panders to devs, while Sourceforge panders to distributers.
- rat 15y agoI found the launchpad bzr code browser not to bad. Launchpad is also more project based then code based. The thing is that sourceforge and launchpad try to give you an overview of the project first while github show the code and a readme and maybe some wiki pages.
- ashley_woodard 15y agoYou might be thinking of Zed Shaw's article "Launchpad vs. Github/SysAdmin vs. Coder": http://sheddingbikes.com/posts/1299555462.html http://sheddingbikes.com/posts/1299555462.html
- wisty 15y agoYep, that's it.
- jarin 15y agoThe one thing I would disagree with is that Github's issue tracking still needs some serious love (although it has improved significantly since launch). Mainly I would say that it works great for projects with relatively few contributors (like most Ruby gems), but seems to fall apart on very large projects (like Rails, who uses Lighthouse for issue tracking). Everything else about Github is amazing, though.
- amerine 15y agoRails no longer uses lighthouse. They've been using GH issue for months.
- jarin 15y agoAh oops, it's been a little while since I jumped in there. Guess that's a good sign I need to find something to fix :)
- TrevorBurnham 15y agoI think Github's issue tracker is the best around, now that search actually works. Very lightweight, and the integration with commits and pull requests is really nice. dhh doesn't sound like he was ever a fan of Lighthouse: https://twitter.com/#!/dhh/status/63366853636009985 https://twitter.com/#!/dhh/status/63366853636009985
- nosequel 15y agoI would use it if it allowed groups to keep all of their issues in one place. Our organization has 20+ repos, so having 20+ bug trackers is pretty dumb. If they make a toplevel issue tracker, I think we'd switch to it.