Re: new issue tracker

I haven't heard anything from anyone except for Tim.  I (manually)
copied the bugs over from SF and closed two of them.  Other than that,
no one has added any new bugs or continued this thread.

Is this not the system you were hoping for?  Have the fires of PyBlosxom
development cooled so much due to my ridiculous amount of bottlenecking
and business?


On 01/06/2011 08:27 AM, will kahn-greene wrote:
> 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

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl