I agree. I wrote a clone of Bugs Everywhere in 2010 [0]. Since then I have come to the conclusion that an issue tracker is meant to be central. Per-repo issue t

I agree. I wrote a clone of Bugs Everywhere in 2010 [0]. Since then I have come to the conclusion that an issue tracker is meant to be central. Per-repo issue tracking is ok for personal projects, but then a TODO.txt probably works just as well. There is one other place for bugs: The testsuite. Then your test runner needs to have some concept of "expected to fail" though. [0] http://beza1e1.tuxen.de/articles/later_bug_tracker.html http://beza1e1.tuxen.de/articles/later_bug_tracker.html