duplys / git-issues

A distributed issue tracking system based on Git repositories, written in Python
http://www.newartisans.com
BSD 3-Clause "New" or "Revised" License
256 stars 35 forks source link

eat your own dogfood #3

Closed teepark closed 14 years ago

teepark commented 14 years ago

github issues on a ticket tracker? really?

jwiegley commented 14 years ago

Very useful.

teepark commented 14 years ago

I think you're missing the point. The first project to use the git-issues ticket tracker should be git-issues. I'm not going to use any ticket tracker for which the author opts instead to use github issues, nor, I think, will most developers.

http://en.wikipedia.org/wiki/Eating_one's_own_dog_food

jwiegley commented 14 years ago

However, you are making assumptions. I never "turned on" the issue tracker here at GitHub, it was just on because I use it for some of my other projects. Also, sometimes it's easier for other people to submit issues via this interface than to require that they pull down git-issues and submit their issue as a patch.

jean commented 13 years ago

What I would love is for the github issue tracker to be able to use git-issues as a backend. What would need to happen for that to be possible?

jwiegley commented 13 years ago

Do you work for GitHub? That would make it happen. :)

John (from my iPhone)

On Oct 28, 2011, at 12:21 AM, jeanreply@reply.github.com wrote:

What I would love is for the github issue tracker to be able to use git-issues as a backend. What would need to happen for that to be possible?

Reply to this email directly or view it on GitHub: https://github.com/jwiegley/git-issues/issues/3#issuecomment-2552917

jean commented 13 years ago

I don't, but mojombo does (rather!): see https://github.com/github/gollum/issues/223