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

Asheesh Laroia <[email protected]> Fri, 1 Oct 2010 20:37:09 -0400 (EDT)
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <alpine.DEB.2.00.1010012034480.6532@localhost>
On Thu, 30 Sep 2010, will kahn-greene wrote:

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

2 and 3 are tough together.

I would try Roundup...

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

You can do that with custom queries (if you pay attention to making a 
query) in most bug trackers except Launchpad's :P

> 5. minimizes administration, maintenance and installation difficulties
>
> 6. must be Free Software

*nod*

self-hosted Roundup is slightly less attractive for you, but on the other 
hand Roundup has a pretty high quality Debian package.

> What options are there out there?
>
> Should we go for a git-based distributed issue tracking system?

Eek, they all have really low usability as far as I know.

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

Heck no. :P

> Are there other requirements I'm not thinking about?

Email interaction? Roundup has that, for what it's worth.

-- Asheesh.

-- 
<_Anarchy_> acf: maybe April 1 next year slashdot needs to run "Rob Malda
             accepts new job as head of Debian project" 8)

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