[theme-reviewers] Getting The Review Queue Back On Track

[Kirk Wight]

Great ideas and bold action Chip; we all appreciate your awesome work and
dedication!

"So, effective immediately, *the Theme Review Team will no longer emphasize
complete and thorough reviews, and will instead close tickets upon
observation of any non-trivial issues*."

This alone should speed things up. You're right, the onus should be on the
submitter to have followed at least the REQUIRED guidelines before
submitting; as soon as a reviewer catches something non-trivial, it should
go right back to the submitter, and the reviewer can move along to the next
ticket. Reviewers, Chip has a comprehensive procedure for doing a review
here (
http://www.chipbennett.net/2011/04/20/a-guide-to-reviewing-themes-for-the-wordpress-theme-repository/),
and his suggestion of starting with policy checks can catch a lot of
non-compliant themes quickly.


On 15 December 2011 06:49, Phenomenoodle | Taryn Wallis <
taryn at phenomenoodle.com> wrote:

> Thanks, Chip. These changes will make a big difference.
> ___________________________________________________________________
>
> *Taryn Wallis*
> Phenomenoodle
>
>
>
> On Thu, Dec 15, 2011 at 9:29 AM, Mario Peshev <mario at peshev.net> wrote:
>
>> So, basically the full review is done only when no critical issues at all
>> are noticed?
>>
>> If so, this would increase the number of reviewed themes as the full
>> review takes a significantly larger amount of time which is not good at the
>> moment with the long queue last 2 months.
>>
>> powered by Android
>>
>> On Dec 15, 2011 11:18 AM, "Merci Javier" <mercijavier at gmail.com> wrote:
>>
>>
>> Thank you very much Chip.
>>
>> Good to hear from you. I'm all for finding ways to improve anything :-)
>>
>> *RE: The Theme Review Team will no longer emphasize complete and
>> thorough reviews, and will instead close tickets upon observation of any
>> non-trivial issues
>> *
>>
>> Just helped review a theme per request<http://themes.trac.wordpress.org/ticket/5429#comment:4>with WP 3.3 installed and some styles from theme bled into wp-admin. This
>> is going to be a blocker for some themes which were submitted before WP 3.3
>> rolled out.
>> http://core.trac.wordpress.org/ticket/19510
>>
>> http://wpdevel.wordpress.com/2011/12/12/use-wp_enqueue_scripts-not-wp_print_styles-to-enqueue-scripts-and-styles-for-the-frontend/
>>
>> Welcome to the new full-reviewers! The more the merrier :-)
>>
>> Cheers.
>>
>> Mercime
>>
>>
>> On Wed, Dec 14, 2011 at 5:52 PM, Chip Bennett <chip at chipbennett.net>
>> wrote:
>>
>>> >
>>> > All,
>>> >
>>> > Please read; comments welcome!
>>> > http://make.wordpress.org/themes/2011/12/15/getting-th...
>>>
>>> > _______________________________________________
>>> > theme-reviewers mailing list
>>> > theme-reviewers at l...
>>>
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111215/21677553/attachment.htm>