[theme-reviewers] Review-Continuation Tickets, and Reviewing Previous Tickets
chip at chipbennett.net
Mon Jan 7 17:45:12 UTC 2013
I would definitely like to see more emphasis directly on *required* issues,
and less on recommended/subjective issues. Especially for a complete and
thorough review, while it is always helpful to mention *recommended* items,
and other suggestions from the Reviewer, we need to ensure that we are very
clear and explicit on which *REQUIRED* issues have kept the Theme from
being approved, and must be addressed for approval.
We've not tried to dictate a certain format for the review comments (again:
doing so usually just yields more needless bureaucracy), but I would
recommend that all Reviewers, at a minimum, include a bulleted list,
clearly indicated as "Required Issues", of the items that fail a *required*
criterion in the Guidelines. That way, the Theme developer knows exactly
what issues to address in order to pass the review process.
On Mon, Jan 7, 2013 at 11:21 AM, Mario Peshev <mario at peshev.net> wrote:
> The QA issue is real and I don't vote 'for' it; still, the Trac has a
> number of reviews directly closed as 'non-approved' with say 2 required
> remarks and several subjective ones as: 'comments need more padding' or
> other similar factors that are more about 'up to the author' and not
> 'breaking the theme functionality'.
> On Mon, Jan 7, 2013 at 6:17 PM, Chip Bennett <chip at chipbennett.net> wrote:
>> And as others have expressed: I too want to avoid the WPTRT becoming
>> unnecessarily bureaucratic, which is why I favor a "Reviewer's discretion"
>> approach, both to early termination of a review of an obviously failing
>> Theme, and to continuing the review in a subsequent ticket for "almost
>> there" Themes.
> +1 for that
> Mario Peshev
> WordPress Engineer, Open Source Consultant
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers