<div dir="ltr">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.<div>
<br></div><div style>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.</div>
<div style><br></div><div style>Thanks,</div><div style><br></div><div style>Chip</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 11:21 AM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank">mario@peshev.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>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'.</div>
<div class="im">
<div><br></div>On Mon, Jan 7, 2013 at 6:17 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><br></div><div class="im"><div>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.</div>
</div></div></blockquote><div><br></div><div>+1 for that</div><div class="HOEnZb"><div class="h5"><div><br>Mario Peshev<br>WordPress Engineer, Open Source Consultant<br><a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
<div><a href="http://me.peshev.net/" target="_blank">http://me.peshev.net</a></div><div><br></div></div>
<br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888">
<div></div></font></span></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>