issue tracking -- let's fix this!

We've switched from svn to git.  That solved a bunch of problems.  Yay!

We've moved the website from Sourceforge to Bluesock (my server) and
that's solved some problems and has the potential to solve more
problems.  Yay!

The next two problems to solve are these:

1. issue tracking

2. plugin/flavour registry

I really want to solve number 1 next.  An issue is a bug, feature,
plugin idea, documentation suggestion, ...  I want to use an issue
tracking system that is:

1. maximizes ease of use

2. minimizes spam

3. maximizes ability of anonymous people to use -- people shouldn't have
to create an account to log a bug (maybe this is solved by people
sending me email--I don't know)

4. maximizes the ability to figure out where PyBlosxom is at in terms of
issues, items that should be done, things that people can jump in and
work on, ...

5. minimizes administration, maintenance and installation difficulties

6. must be Free Software


To reduce the scope of this conversation, I offer the following
anti-suggestions:

1. no bugzilla -- it's great, I love it, doesn't meet my requirements
for PyBlosxom

2. no Trac -- other people like it, I don't


What options are there out there?

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

Should we roll our own system using the PyBlosxom core?

Are there other requirements I'm not thinking about?

I'd love to talk about this for the next couple of weeks and come to
some kind of solution both for the software to use as well as any
workflow suggestions that address the requirements.  Then we'll
implement something in late October and solve this problem because it's
seriously hampering our mojo and that sux0rz.

/will

------------------------------------------------------------------------------
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