On Thu, Dec 17, 2015 at 02:01:20PM -0400, Joey Hess wrote: > That's fine, but 98%[1] of all other projects whose bug tracking > systems I interact with have bugs tracked on github. > > So the question may be, what needs to change to get distributed bug > tracking to extend beyond quick and easy systems built for > essentially personal, or at best project-wide use?
My guess is those 98% projects also store their canonical repository on GitHub and don't care enough about distributing their issue tracker (or getting some other issue-tracking feature) to pick something besides GitHub's built-in system. In that case, the change needs to be one of: * Convince GitHub to use a distributed issue tracker (seems unlikely). * Create a better-than-GitHub forge that uses a distributed issue tracker (even less likely). * Create a GitHub-issue sync tool for your favorite distributed tracker. This is technically straightforward, but without buy-in to your distributed tracker from other project users, GitHub is still a required centralized sync point. So the answer seems to be “get your tool to sync with GitHub, advertise your use of your distributed tool to your project-mates, and see if any of them join you in using it”. And this same argument holds for any centralized system, not just GitHub. Cheers, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dist-bugs mailing list [email protected] http://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
