On 07.03.2012, at 14:53, Jonathan Nieder wrote: > Joern Huxhorn wrote: > >> To get accepted in this community, an issue tracker would need to be >> decentralized > > No, I don't think that's a requirement. > I didn't mean to imply that this would be a matter of principle. A decentralized tracker would just offer the same advantages that a decentralized VCS has to offer. One could work on issues while not connected to the internet, for example. So this would be a VeryGoodThing™. I don't think that it would be a good idea to "teach" git issue tracker functionality. I simply wanted to voice my opinion that something like the ideas Neal suggested down the thread, a cli issue tracker with git in the backend, are very worthwhile to evaluate. But it should have an additional layer so it's really easy to use. It has to be so it *is* actually used. It needs to reduce workload instead of increasing it. Cheers, Joern.-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html