[Pydotorg-redesign] Re: Kevin Altis blog move

[Richard Jones]

[Note: I'm not on the -redesign mailing list... please CC me]

On Mon, 14 Apr 2003 09:55 am, Kevin Altis wrote:
> BTW, there is a thread on the pydotorg-redesign mailing list that is
> relevant to you because roundup might solve the tracker problem the
> python.org maintainers currently have with webmaster at python.org...
>
>   http://mail.python.org/pipermail/pydotorg-redesign/2003-April/000006.html
>
>   http://mail.python.org/pipermail/pydotorg-redesign/2003-April/thread.html
>
> If you are able to volunteer to get it going on python.org and help with
> any use issues that would be helpful. We're trying to "clean house" before
> "redecorating" python.org. :)

I could set something up using Roundup, sure. Just gimme a spec :)

It'll be easier to set up than the pythonlabs tracker, which is still needing 
more attention than I have to give, because it requires significantly less 
customisation work, and doesn't require a database migration from sourceforge 
:) I also need to do something very similar for work, so there's a much 
higher chance I'll get it done ;)

In terms of spec, I suppose the simplest thing to do would be to have:

1. a form on the website that submits a new issue to the tracker (capture
   details of query and email address for responses) ... the webmaster alias
   could also be pointed at this system too, I suppose
2. on submission, the tracker:
   - picks a random webmaster user (weighted by # of assigned issues) to
     assign the issue to (that user automatically gets emailed a copy of
     the query), and
   - sends a form-letter to the user acknowledging the issue (/dev/null reply
     address)
3. a cron job checks for issues unanswered for 2 (or so) days and reassigns
   if necessary (new assignee gets the same query message sent to them)
4a. assigned user replies to the query message (which goes back to the
    tracker) - the tracker closes the issue and forwards the reply to the user
4b. assigned user manually closes or reassigns issue via web interface
(5) optionally, the user responds to the message, and the issue is reopened.
    loop to 4.


    Richard