[theme-reviewers] Trac Report Updates

[Chip Bennett]

On Wed, Sep 1, 2010 at 1:35 PM, Otto <otto at ottodestruct.com> wrote:

> On Wed, Sep 1, 2010 at 1:25 PM, Chip Bennett <chip at chipbennett.net> wrote:
> > If I'm reading him correctly, I think Phil's point was that we're not
> seeing
> > Theme developers trying to assign-and-accept their own Theme tickets in
> > order to facilitate a faster review for an updated Theme, but rather to
> > bypass the review process entirely.
>
> Oh... Yeah, okay, that interpretation makes much more sense. :)
>
> > Just FYI: as of Sunday, the average age of New/Unassigned tickets was
> only
> > 3.76 days. We're getting *much* better at turning reviews around in a
> more
> > timely manner.
>
> What else could help? What tools are needed? What tools do you find
> yourself using a lot?
>
> -Otto


The one thing that will really start paying dividends is the prioritization
of  Themes by status, and division of labor. Just as Phil is focusing on
tickets for updates to already-reviewed-and-approved Themes, I'm focusing on
First-Timers. Phil can do a cursory diff-review, while I can focus on
in-depth, thorough reviews.

So, hopefully, this will help reduce the repetitive submission of Themes,
thereby reducing both the workload and the tact time.

As for other tools: you guys are covering that pretty well in IRC. Could you
perhaps add a list to http://themereviews.wordpress.com/ ? That way, we can
keep track of what we've asked of you, and what you've been able to
implement?

(Use of that P2 blog is a bit of an experiment. If there's a better way,
feel free to throw it out there!)

Chip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100901/cf1ebaa2/attachment.htm>