Code review vs. bug tracking?

[kanzure]

Could the README possibly provide a comparison to tools like https://bugseverywhere.org/ ?

Bugs Everywhere is a “distributed bugtracker”, designed to complement distributed revision control systems. By using distributed revision control as a backend for bug state, we gain several convenient features: ....

[timoc]

+1 ish - I would link this to distributed issue management.
If you imagine this is being used by a distributed team in an Agile or TDD type scenario. Further, that any commit (and hence a review) would correspond to a feature in the current sprint or backlog. That way the reviewer has some context for use-case that generated the code that is under review. That way the open/closed issues are managed in branches too.

I would assume the issues/user stories are in a parse-able text file - I use a linked set of org-mode-markup files as they can act like a wiki, but markdown or json might be easier.

Further these files could be auto synced/generated from issue trackers such as redmine/github etc. but that would be built upon a standalone implementation.

[mcepl]

Just to mention … BugsEverywhere was Python 2 … unfinished port to Python 3 is in the python3 branch of https://git.cepl.eu/cgit/git/bugseverywhere/. If anybody could finish port to py3k (at least resolve current failing tests), it would be awesome.

However, the point of the port is mostly to get BE databases out of it, because currently the most maintained and similar tool is https://github.com/git-bug/git-bug.