4 ms·
LOL, I don't think the github guys are worried about pissing off the lighthouse guys. Hell, you can do issue tracking in git itself with Scott Chacon's awesome
by bjclark 18y ago
LOL, I don't think the github guys are worried about pissing off the lighthouse guys. Hell, you can do issue tracking in git itself with Scott Chacon's awesome Ticgit (http://github.com/schacon/ticgit/tree/master http://github.com/schacon/ticgit/tree/master). I would think it would take them a day to slap a web interface on that.
Instead, I think they don't WANT to do ticket tracking. That's not what github is about. It's a social network built around code. I don't think it's a business oriented project management site.
- gunderson 18y agoGood points, but how cool would it be to simply scan a project's open tickets and then fork it, hack away on one and submit a pull request. That's a far more cooperative spirit than simply forking someone's project for your own purposes. Also, if someone is going to take the time to go through the code after forking, they might feel like fixing any bugs or handling a few new feature requests while they're at it, especially for small, informal projects.
- bjclark 18y agoSo the only thing stopping you from this is that they are on 2 different domains? Why does that stop you?
- gunderson 18y agoI try to minimize the number of sites I set up accounts on, and there is no logical reason why github shouldn't have simple tickets, other than deference to lighthouse.