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

[Tim G. <tg...@pr...>]

On Oct 05, 2010 at 12:24 PM +0000, seanh wrote:
> 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.

I've been thinking about this, and though I don't have any more specific 
suggestions, I think this is a good point.  If it were me, I'd either 
consolidate the source code, web page, and bug tracking on an external 
service, or try to keep them all in house.  Though having the source on 
gitorious isn't the end of the world - anybody who wants a the current dev 
version should know enough to navigate multiple sites.

But, if you want the issue tracking to be visible and easily useable by 
first timers, then I think it might be a good idea if it is well integrated 
into bluesock.  I guess that doesn't necessarily mean it should be hosted at 
bluesock, but I think I would stay away from using just the issue tracking 
part of a larger integrated service.

Furthermore, a nice clean activity and roadmap interface really helps to 
answer Will's original point 4 about status visibility.  Trac and Redmine 
seem relatively intuitive in this way to me.  Since Will doesn't like Trac, 
I think Redmine looks good to me.

One thing I've been keeping in mind as I look at the different suggestions 
is whether or not the mentioned package hosts their own package's project 
page via their package's web interface.  I figure any modern issue tracker 
should have the ability to have an overview page and some kind of wiki like 
thing for each project (which should be sufficient for an issue trackers 
public web presence), and if it doesn't, it's missing some features that 
would be very useful.  Of course, one could use this argument to say 
Pyblosxom host it's own issues... but that should be for the future, not for 
now.