Re: [Pyblosxom-devel] issue tracking -- let's fix this!

[Dieter P. <di...@pl...>]

On Tue, 5 Oct 2010 12:24:14 +0000
seanh <sn...@gm...> wrote:

> Does gitorious plan to implement a bug tracker like github has?
> 
> What bug trackers do other projects on gitorious use?
> 
> I notice that for the gitorious source code (which is hosted on
> gitorious) they use Lighthouse, which I don't think is free software.
> 
> I looked at some of the featured projects on the gitorious front page
> to see what they use. StatusNet hosts its own bug tracker at its
> website:
> 
> http://status.net/open-source/issues
> 
> I guess that is a drupal module?
> 
> XBMC hosts its own trac.
> 
> OpenSuSe uses Bugzilla. Qt uses some enterprise thing.
> 
> None of these feel very pyblosxom. I'd say Lighthouse, because it
> claims to be very simple, seems most appropriate but it isn't free
> software.
> 
> I suggested using Launchpad back when we were thinking about moving
> from Sourceforge. I've seen projects before that use Launchpad for
> some things (e.g. issue tracking) and another site for other things
> (e.g. code hosting). I think we could go with that still. We'd use
> gitorious for the code hosting, bluesock for the website, we already
> seem to have mailing lists, but Launchpad could provide us with
> (whichever we want from): bug tracking, translations, Ubuntu package
> building and hosting (we could have a PyBlosxom PPA), blueprint and
> specification tracking, and the community support thingy "Launchpad
> Answers". The disadvantage is that Launchpad is quite a confusing and
> difficult-to-navigate site, and that we'd be spreading things across
> even more services (bluesock, gitorious, sourceforge, launchpad),
> although we could use the front page of the bluesock pyblosxom
> website as the central place to link to them all. It might have the
> potential for things to get quite confusing.

Launchpad is IMHO hard-to-work-with bloatware.
We can also use bugseverywhere.
It's a distributed bugtracker that stores issues in
your git repo, next to the code.
http://bugseverywhere.org/be/show/HomePage
I thisk distributed bugtracking in general makes a lot of sense (read
the bugseverywhere page and/or http://lwn.net/Articles/281849/)

I've never tried bugseverywhere myself though, they say they have a
webinterface for people who don't like the commandline, but not sure
how well that works.

Dieter