> Greetings,

> Ever since I started using a DSCM I've been annoyed with how bad
> traditional bug/issue/task/ticket/whatever tracking fits into the
> picture, the biggest one being how there's only one path, not much
> unlike SVN.

> I really want to add a tracker to Gitorious.org, not only because I'm
> starting to need one myself (and thus I'm guessing it'll be useful for
> others), but also because I think we have the opportunity to build
> something that fits better into the world of DSCMs like git. So in the
> spirit of keeping things open, here's a braindump of my current ideas.

> The most basic requirement I have is that I should be able to track
> tickets across clones and projects. It's a sweet way to collaborate
> because a bug in "clone-a" could be marked as fixed in "clone-b" (by
> another user), so instead of messing around with patch files I could
> just pull in his changes and have the bug fixed. This is pretty much
> exactly the way we all use git today, it's just not tied in properly
> with bug reports.

> It should also tie into the growing ecosystem of gitorious itself,
> lets say I have a failing testcase and someone files a ticket on it,
> but after looking at it it turns out it's a bug in rspec, the testing
> framework, and I could just "move" that ticket to the rspec project.
> But still have it tracked in my project, so that whenever it's fixed
> in rspec, the bug would be marked as "fixed upstream" or something.

> It would also be really neat if the tracker itself was distributed, so
> I at least could bring it along on the train/bus/airplane and resync
> when I'm back online. It may turn out to be a pipe dream, but I'm
> looking at a couple of document databases with replication features
> that I think would be a good possible solution.
> To be honest, it kinda makes the most sense to store the bugs directly
> in the repository, with a nice web UI on top for those into that,
> since it would make it easier to track them across clones and
> branches, but that might be a tad intruding for some projects?

> While it potentially increases the complexity of gitorious a bit, I
> really do think it'll be a nice feature for the projects that wishes
> to use it (eg opt-in). Mostly because it's a good aid in helping to
> build a community around the given project; new people can easily pick
> out something to work on their clone, and regular contributors gets
> all the usual benefits of a bug tracker.

> But what do you guys/girls think? I'm thinking that at least the first
> one of the above is a killer, and something I'd love to have on my
> internal/company projects...

> Cheers,
> JS