The todo list
Dan Sugalski
I got reminded the other day that we have a full, working RT
installation (as everyone's probably noticed with the tickets that
fly past on occasion) and, well, we ought to use it. What I'm going
to start doing is putting in tickets for the tasks that need doing,
that way they don't get forgotten, and so we've a place to track
discussion and whatnot on them as need be. Also this way anyone who
wants to claim a task can grab a ticket, which'll be good. More user
tracking.
What I'd like is for a volunteer or two to manage the todo queue.
Nothing fancy, just be there to assign todo list items to the folks
that volunteer, make sure they're closed out when done, and reassign
them if whoever's handling a task needs to bail for whatever reason.
Since anyone with a perl.org account can participate in RT activity
(as far as I know) all you'll need to do this (be a ticket manager or
take a todo list) is sign up at http://bugs6.perl.org and follow the
"create or modify your perl.org account" link.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
Harry Jackson
> Folks,
>
> I got reminded the other day that we have a full, working RT
> installation (as everyone's probably noticed with the tickets that fly
> past on occasion) and, well, we ought to use it. What I'm going to start
> doing is putting in tickets for the tasks that need doing, that way they
> don't get forgotten, and so we've a place to track discussion and
> whatnot on them as need be. Also this way anyone who wants to claim a
> task can grab a ticket, which'll be good. More user tracking.
>
> What I'd like is for a volunteer or two to manage the todo queue.
> Nothing fancy, just be there to assign todo list items to the folks that
> volunteer, make sure they're closed out when done, and reassign them if
> whoever's handling a task needs to bail for whatever reason.
>
> Since anyone with a perl.org account can participate in RT activity (as
> far as I know) all you'll need to do this (be a ticket manager or take a
> todo list) is sign up at http://bugs6.perl.org and follow the "create or
> modify your perl.org account" link.
Having managed to fish a few lurkers out of the woodwork I can confirm
13 lurkers on this list and most would like to get involved in some way.
I am sure there are more but they are playing possum at the moment ;-).
We already have the string documentation being overhalued (Go Robert).
If there are any more of you guys lurking speak up and for those that
want to help the Request Tracking (RT) System would be a great place to
start. If a couple of you want to take it on get yourself a perl.org
account at the following place.
http://dev.x.perl.org/auth/account
Then when you have registered go here
Have a look at the RT system to see if there is anything on it at the
moment that you would like to take on.
An important task at the moment is to start chasing these tasks up to
see what state they are in or if they have been closed etc. Most of the
tasks are over 6 months old so I imagine a lot of the bugs are no longer
relevant.
If Dan is going to be adding tasks to the RT system in the future then
it will also be a good place to get involved with stuff as it comes up.
Harry
David Pippenger
>
> What I'd like is for a volunteer or two to manage the todo queue.
> Nothing fancy, just be there to assign todo list items to the folks
> that volunteer, make sure they're closed out when done, and reassign
> them if whoever's handling a task needs to bail for whatever reason.
>
I may not have 20+ years of C/C++ experience but I do wrangle RT tickets
professionally. I'd like to volunteer for this role. Speaking from
personal experience, RT is an amazing tool for decomposing projects into
tiny bits that can be spread around. I predict that this would allow many
shy lurkers to get some skin in the game.
-- Dave
Dan Sugalski
>
>What I'd like is for a volunteer or two to manage the todo queue.
>Nothing fancy, just be there to assign todo list items to the folks
>that volunteer, make sure they're closed out when done, and reassign
>them if whoever's handling a task needs to bail for whatever reason.
Okay, I've two volunteers, Dave Pippenger and Stephane Peiry. (Make
sure you get me your perl.org logins if you've not done so yet (I've
not checked (Wheee, parenthesis!))) When Robert's back from vacation
we'll get you installed with access to the RT queues for parrot and
see what we can do.
In the mean time, if anyone else has todo list items, send them
(*ONE* per e-mail!) to bugs-parrot at bugs6.perl.org to get 'em in
the queue and we'll start sorting them out from there. If we're lucky
and have sufficient web luck we might even get 'em into a
web-accessible TODO list (so make sure the subjects are descriptive
too!)
Robert Spier
> (*ONE* per e-mail!) to bugs-parrot at bugs6.perl.org to get 'em in
> the queue and we'll start sorting them out from there. If we're lucky
> and have sufficient web luck we might even get 'em into a
> web-accessible TODO list (so make sure the subjects are descriptive
> too!)
I need to repair the web-accessible TODO list. Someone nag me
periodically.
-R