<html><body bgcolor="#FFFFFF"><div>Thanks for that, Chip. I actually try to do this. I generally only post the required changes so the developer knows exactly what needs to be fixed. </div><div><br></div><div>That's not to say that I don't miss things, but I try. <br>
</div><div><br></div><div><br>On May 2, 2011, at 7:50 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Good evening, all!<div>
<br></div><div>Just a quick bit of feedback on reviews, primarily for the trainees, regarding Theme Check results.</div><div><br></div><div>For anything other than "Warning" or "Required" (which we shouldn't see, anyway, as the uploader should filter out Themes that return Warning/Required-level errors), the results are primarily for *your* information and reference. These results should help point you in the right direction regarding things to look for.</div>
<div><br></div><div>These results do NOT necessarily need to be output in the ticket.</div><div><br></div><div>The reason that I say that is because simply copy/pasting Theme Check results into the review comments can distract from the REQUIRED issues in the review, and can be misleading for the Theme developer. I've seen several instances where RECOMMENDED/INFO results were added to the ticket, but were not actually applicable to the Theme - and then the Theme developer got dinged in the subsequent ticket, for wrongly implementing changes based on those results. </div>
<div><br></div><div>For example: </div><div><ul><li>The get_template_part() include function only applies to *template-part* files (or code output in template-part files), and NOT (generally) to functions.php, or including library files (such as theme-options.php, etc.) within functions.php.</li>
<li>Hard-coded links are not inherently prohibited. This INFO output is only intended to help you review the Theme, by collecting all such links in one place, so that you can review them for appropriateness. If all such links are appropriate, then this INFO result should NOT be included in the review comments.</li>
</ul></div><div><br></div><div>The RECOMMENDED results, especially the ones regarding Theme features/functionality, may be useful to include. But if you include them, be sure to delineate them such that it is very clear that they are NOT required. I would suggest placing them *after* listing all of the required issues. (I generally leave them out altogether. The Theme developer sees them in the uploader output, and also when testing locally using Theme Check.)</div>
<div><br></div><div>In the end, remember that our ultimate goal is to communicate to the Theme developer the specific deficiencies in the Theme - the specific things that the Theme developer needs to address, in order for the Theme to pass the review.</div>
<div><br></div><div>Thanks, again, for all of your help and contributions with reviewing Themes!</div><div><br></div><div>Chip</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>theme-reviewers mailing list</span><br><span><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a></span><br>
<span><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></span><br></div></blockquote></body></html>