On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
> On Wed, Jan 6, 2010 at 06:57, Brian Curtin <brian.curtin@gmail.com> wrote:

> > On the topic of bugs that can be readily closed (literally), I've recently
> > come across a number of issues which appear to be sitting in a patch or
> > review stage, but their patches have been committed and the issue remains
> > open. What is the best course of action there? I'd just go ahead and close
> > the issue myself but I don't have tracker privileges.
> >
> >
> If a core developer is willing to step forward and vouch for you to get
> tracker privileges then I will give them to you. We are trying to give out
> tracker privs w/ less time than required to get commit privileges. So as
> long as you have helped out on a few issues in a positive and correct way
> that should be enough to get one of the regulars who perform triage to
> notice.
>
> -Brett

I've done a quick scan of issues Brian is nosy on to refresh my
memory, and I'd say he's definitely been making positive contributions.
I'm willing to volunteer to keep an eye on his triage work for a while
if you grant him tracker privs.

Brian, I assume you'll be cognizant of Antoine's advice about making
sure a bug really should be closed before closing it :)  Hanging out in
#python-dev on freenode while working on issues can be helpful, as well,
since you can quickly ask whoever is there for second opinions on
particular bugs.

--
R. David Murray                                      www.bitdance.com
Business Process Automation - Network/Server Management - Routers/Firewalls