Living With The GitHub Issue Tracker
Over the last couple of years I’ve seen what it’s like to run a super-large open source project (and a few small ones) with the GitHub issue tracker.
First off, I think if you want high levels of engagement it’s the right thing to do. You will get more bug reports and submissions because everyone is already on GitHub — there is a barrier to entry to signing up for yet-another-bugtracker account and going back to check it, and GitHub notifications work very well.
Of course, it also makes interacting too easy. You’ll get a lot of traffic if your project is popular, and some times the reports don’t contain all the info they should. Writing a good bug report is an acquired skill. Plus, there’s often the desire of some to use the issue tracker of a support forum, which it’s not good at being a forum.