[etanol]

Too bad there are no comments on the blog:

    SQLAlchemy's issue repository will remain hosted on Trac;
    while a Git repository can be mirrored in any number of
    places, an issue repository cannot (for now! Can someone
    please create a distributed issue tracker? Should be
    pretty doable, though getting Github/Bitbucket to use it,
    not so much...), so SQLAlchemy's long history of issue
    discussion remains maintained directly by the project.

http://fossil-scm.org !!!

[qznc]

There are tools like Bugs Everywhere [0], which mix well with distributed VCS. However, the question is if distributed bug tracking makes sense.

[0] http://bugseverywhere.org/

[travisb]

There are many different projects which implement distributed bug tracking[0], some better than others. The question of how much distributed bug tracking makes sense depends strongly on the structure of the project. If the project is developer heavy (such as developers responding to user help requests) it can work well, but if the project has several strata of developers and support people and users then it might not make as much sense.

[0] http://travisbrown.ca/blog.html#TooMuchAboutDistributedBugTr...

[zzzeek]

uh yikes! http://fossil-scm.org/index.html/dir?ci=601c15421a4a5ca5&...

although good point, I see they're doing distributed. will take a look at how they approach that.

[etanol]

I think you can customize most parts of the Web UI:

http://www.fossil-scm.org/fossil/wiki?name=Cookbook#css

[voltagex_]

Trac is pretty bad. Can you remove yourself off a subscribed issue yet?