new issue tracker

will kahn-greene <[email protected]> Thu, 06 Jan 2011 08:27:55 -0500
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
I'm really sorry this took so long, but it's just been pretty crazy in
Will land.

I went back to the conversation we had about issue tracking in October
and collected the following requirements:

* web-based interface
* maximize ease of use
* use something pre-existing rather than writing our own
* use something that is widely used rather than something that isn't
widely used
* minimizes spam
* roadmap showing all the bugs in a given milestone so we know where
things are at
* activity so we know what's happening (or not happening)

I had these additional requirements, but was ok with dropping them
depending on how compelling a given solution was:

* use something we host and have full control over (I'm loathe to have a
SF-like experience again)
* use something written in php or python (those are languages I can deal
with easily and can extend)
* no Trac
* email interface


I've been doing some bug reporting for OpenHatch which uses Roundup.
After talking with Asheesh, I decided that Roundup meets a lot of these
requirements.  I know there were a few people who dislike Roundup.  I
suspect some of that is either theme related or interface related.  More
on that in a smidge.

Anyhow, I spent the last week or so working my way through Roundup,
installing it on my server, and with lots of help from Asheesh and the
OpenHatch crew, got milestones working.

The result is at:

   http://pyblosxom.bluesock.org/bugs/

There are probably still some issues and the theme could be better
(which can also be said of the entire PyBlosxom site).

Things I need help with:

1. I need someone to go through the bugtracker on SF and move bugs over
to the new bug tracker.

2. If there are problems with the new bug tracker, I need people to
write up bugs for them.  I created an "infrastructure" keyword for any
issues regarding the PyBlosxom web-site, bug tracker, git repository, ...

3. If you've written an email to the devel list about a problem you're
having that you know hasn't been fixed yet, write it up as an issue.
Feel free to just copy and paste your email into the issue description.

4. If you're into theming, I'd love to get a better theme for the whole
PyBlosxom site including Roundup.  Let me know if that's something
you're interested in.


In the meantime, I'm going to write up issues for the things I think
still need to be fixed for 1.5.

After all that work, I think we'll be in a much better place.  Amongst
other things, it'll be a lot clearer to all of us where we're at.

One thing you'll notice is that there's no link to the issue tracker on
the PyBlosxom web-site.  I'll rectify that today or tomorrow.  I wanted
to make sure the issue tracker was working for all of us before I made
the whole thing public.

I really appreciate that discussion on issue trackers a while back.
Thank you all for your input--it helped get us to where we're at now.

/will

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl