<!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">
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<br>
<br>
<br>
On 4/21/11 8:49 AM, Towfiq I. wrote:
<blockquote
cite="mid:BANLkTim0tu_CRXQxFHrz6LwWSskp68j-nA@mail.gmail.com"
type="cite"><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">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 class="h5"><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>
<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>