Re: issue tracking -- let's fix this!

On Sep 30, 2010 at 03:14 PM -0400, will kahn-greene wrote:

I've never really developed anything (haha) so take my suggestions with a 
grain of salt.  Of the couple issue tracking systems I've encountered, trac 
and google code's system both seemed easily understandable to the outsider. 
It's very easy to get a sense of what the latest progress is.

I understand you don't want to use trac though.

> What options are there out there?

ikiwiki could be interesting.  It's based off of a revision control system, 
so that's a big plus.  It can be hosted in git, so it could live right along 
side the source code.  Or in a separate repository.  Which would also make 
it distributed.  It has bug tracking, todos, etc. built in.  It also appears 
to allow for anonymous bug submissions.  Looks like a cool project to me.

Google code has a nice clean interface too.  I don't know how easy/hard it 
would be to glue it onto a project hosted elsewhere though.

> Should we go for a git-based distributed issue tracking system?

See above.

> Should we roll our own system using the PyBlosxom core?

A possibility, but I might say the time and effort spent implementing an 
issue tracking system could be better spent elsewhere.

On a separate note, I'd like to contribute more to pyblosxom development 
(when I get a bit of time).  I've hacked up a number of plugins already just 
in the last couple weeks of usage, but I'd like to help in a more meaningful 
way as well.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev