Distributed issue tracking seems like a belting idea to me, but it has never really taken off in a big way. Is there a good reason for that?I am aware of:bugz everywheretoo complex to set uptoo many requirementsreasonably successful, used by some large projectsfossiltries to integrate too many things, and ends up being a slightly worse version of all of them - except maybe for the distributed issue tracking part, which is decent (probably best I have seen)several other smaller projectsnone of which have gained any tractionI am thinking about making my own, but before I begin, I would like to know why none of the others have taken off in a big way.Anticipated issues: (I think they can all be overcome)merging distributed issues as they are updated is complex, as is merging any code filesconversation continuity can be destroyed, as comments can come in at any time, perhaps not in the correct flowexpectation of central server with issues up-to-date
Distributed Issue Tracking
version control;issue tracking;distributed computing