<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think your boilerpate is awesome. I have one I use as well, but I
may borrow from yours :)<br>
<br>
My example was merely an example :) I am not sure to what extent to
standardize, but I think it is important to offer some consistency
across all reviews. Everyone will approach a little differently of
course, but having some standard areas at minimum would be helpful,
especially in cases where the theme is not approved and will be
re-reviewed. <br>
<br>
Dre<br>
<br>
On 4/21/11 9:14 AM, Chip Bennett wrote:
<blockquote
cite="mid:BANLkTi=Rv0BqssL2B1fJ7FYbrS8u_QqEOQ@mail.gmail.com"
type="cite">I do use my own standard boilerplate, but I wouldn't
want to impose it on anyone. Every reviewer is going to be most
comfortable communicating information in his or her own manner.
<div><br>
What I think is critical is communication of these two key
points:</div>
<div><br>
</div>
<div>1) Why the Theme failed the review (i.e. the *required*
issues)</div>
<div>2) How to communicate with the reviewer</div>
<div><br>
</div>
<div>For the first point, I simply list comments under the
following headings:</div>
<div><br>
</div>
<blockquote class="webkit-indent-blockquote" style="margin: 0pt
0pt 0pt 40px; border: medium none; padding: 0px;">
<div>'''Theme-Check Required''' (Note: we shouldn't have any
more of these)</div>
<div><br>
</div>
<div>'''Required'''</div>
<div><br>
</div>
<div>'''Required, but can be fixed in next revision''' (Note:
only if nothing is listed under the '''Required''' heading)</div>
<div><br>
</div>
<div>'''Strongly Recommended, not Required'''</div>
</blockquote>
<div><br>
</div>
<div>Then, under the heading, '''Review Summary''', I add certain
boilerplate text, that I recommend as generally useful for any
reviewer, i.e.:</div>
<div><br>
</div>
<div>For a complete review:</div>
<div><br>
</div>
<blockquote class="webkit-indent-blockquote" style="margin: 0pt
0pt 0pt 40px; border: medium none; padding: 0px;">
<div>
<div>'''Review Summary'''</div>
<div><br>
</div>
<div>'''This is a complete review.''' Theme cannot be accepted
until items listed under '''Required''' are addressed. Once
these issues have been resolved, please re-submit your Theme
using the uploader tool on <a moz-do-not-send="true"
href="http://wordpress.org/extend/themes">wordpress.org/extend/themes</a>,
and a new Trac ticket will be generated. </div>
<div><br>
</div>
<div>Note:</div>
<div> * Re-submitted Themes are given review priority over new
Themes.</div>
<div> * Prior to re-submitting, please ensure Theme meets all
requirements in the [<a moz-do-not-send="true"
href="http://codex.wordpress.org/Theme_Review">http://codex.wordpress.org/Theme_Review</a>
Theme Review Guidelines] and the [<a moz-do-not-send="true"
href="http://codex.wordpress.org/Theme_Unit_Test">http://codex.wordpress.org/Theme_Unit_Test</a>
Theme Unit Tests].</div>
</div>
</blockquote>
<div><br>
</div>
<div>For a cursory review:</div>
<div><br>
</div>
<blockquote class="webkit-indent-blockquote" style="margin: 0pt
0pt 0pt 40px; border: medium none; padding: 0px;">
<div>
<div>'''Review Summary'''</div>
<div><br>
</div>
<div>'''This is a cursory review only.''' This Theme failed a
sufficient number of criteria to warrant discontinuing
further review. '''Prior to re-submitting, please ensure
Theme meets all requirements in the [<a
moz-do-not-send="true"
href="http://codex.wordpress.org/Theme_Review">http://codex.wordpress.org/Theme_Review</a>
Theme Review Guidelines] and the [<a moz-do-not-send="true"
href="http://codex.wordpress.org/Theme_Unit_Test">http://codex.wordpress.org/Theme_Unit_Test</a>
Theme Unit Tests].''' Once these issues have been resolved,
please re-submit your Theme using the uploader tool on <a
moz-do-not-send="true"
href="http://wordpress.org/extend/themes">wordpress.org/extend/themes</a>,
and a new Trac ticket will be generated. </div>
<div><br>
</div>
<div>Note:</div>
<div> * Re-submitted Themes are given review priority over new
Themes.</div>
<div> * Test your Theme using the [<a moz-do-not-send="true"
href="http://pross.org.uk/theme-check/">http://pross.org.uk/theme-check/</a>
Theme Check tool], and ensure that no errors are found,
prior to re-submission.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Finally, under the heading '''Responding To This Review''', I
add additional boilerplate text:</div>
<div><br>
</div>
<blockquote class="webkit-indent-blockquote" style="margin: 0pt
0pt 0pt 40px; border: medium none; padding: 0px;">
<div>
<div>Theme developer questions, comments, and feedback are
welcome and encouraged. Please use one of the following
methods:</div>
<div><br>
</div>
<div> 1) Leave a comment on this ticket</div>
<div> 2) Email the theme-reviewers email list</div>
<div> 3) Use the #wordpress-themes channel on <a
moz-do-not-send="true" href="http://irc.freenode.net">irc.freenode.net</a></div>
</div>
</blockquote>
<div><br>
</div>
<div>I'm certainly open to any additional standardization that you
think would be useful?</div>
<div><br>
</div>
<div>Chip<br>
<br>
<div class="gmail_quote">On Thu, Apr 21, 2011 at 10:58 AM, Dre
Armeda <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:feeds@armeda.com">feeds@armeda.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Chip, I think another
area we may want to look at is how the reviews are
published to the theme submitter. What about standardizing
the information published in the review, and using a
single template that contains all of the relevant review
points?<br>
<br>
As an example:<br>
<ul>
<li>Intro statement (exp. Thanks for contributing. The
theme is awesome but there are areas you need to clean
up)</li>
<li>Theme Check Info</li>
<ul>
<li>Required Items</li>
<li>Recommended Items</li>
<li>Info Items</li>
</ul>
<li>Debogger Items</li>
<li>Deprecated Calls Info</li>
<li>Test Data Info</li>
<li>Test Environment Info</li>
<li>Quick Observations</li>
<li>Recommendations</li>
<li>Closing Statement</li>
</ul>
<br>
Let me know if I missed anything. The objective is to
manage expectations. Standardizing gives a uniform feel
upon delivery of the review information to the submitter,
and also gives reviewers a common approach which may
improve the process and learning curve.<br>
<br>
Just an idea. Continual process improvement will enable us
as reviewers to become more proficient :)<br>
<br>
Cheers,<br>
Dre Armeda
<div>
<div class="h5"><br>
<br>
<br>
On 4/21/11 8:49 AM, Towfiq I. wrote: </div>
</div>
<blockquote type="cite">
<div>
<div class="h5"><br>
<br>
<div class="gmail_quote">On Thu, Apr 21, 2011 at
7:41 PM, Chip Bennett <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:chip@chipbennett.net"
target="_blank">chip@chipbennett.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt
0pt 0pt 0.8ex; border-left: 1px solid rgb(204,
204, 204); padding-left: 1ex;"> A good question.
<div><br>
</div>
<div>When we only had 3-6 active reviewers, we
would, purely out of necessity, perform
cursory reviews. Unfortunately, that practice
primarily led to the Theme developers
addressing only the issues noted in the
cursory review, and not ensuring that all of
the Guidelines were met. Thus, we would end up
seeing the same Theme, several times - and
each time, reviewing the Theme would incur the
overhead of a new review.</div>
<div><br>
</div>
<div>So, now that we have many reviewers, I
would strongly recommend that every review be
as thorough and complete as possible. Our goal
would be to review a Theme only once (if
perfect the first time) or twice (the second
time, addressing all issues in the first
review) before approval.</div>
<div><br>
</div>
<div>Also, doing so will help all of the new
reviewers through the learning process of
performing Theme reviews.</div>
<div><br>
</div>
<div><font color="#888888">Chip</font>
<div>
<div><br>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
Totally Agree with Chip...<br clear="all">
<br>
-- <br>
<span style="color: rgb(153, 153, 153);">Towfiq I.</span><br>
<br>
</div>
</div>
<pre><fieldset></fieldset>
_______________________________________________
theme-reviewers mailing list
<div class="im"><a moz-do-not-send="true" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a moz-do-not-send="true" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</div></pre>
</blockquote>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
</body>
</html>