We have no explicit guidelines about inline documentation. <div><br></div><div>You can certainly recommend changes to inline documentation (especially if the documentation is wrong/inconsistent/misleading/etc.), but at current such issues wouldn't fall under REQUIRED.</div>
<div><br></div><div>Exceptions would be:</div><div>1) Inline documentation that contradicts the license</div><div>2) Obvious copy-pasta (e.g. references to TwentyTen, etc.)</div><div>3) Similar</div><div><br></div><div>Chip<br>
<br><div class="gmail_quote">On Fri, Oct 7, 2011 at 3:06 PM, Kirk Wight <span dir="ltr"><<a href="mailto:kwight@kwight.ca">kwight@kwight.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<div><br></div><div>How do we grade errors in commenting? Theme developers sometimes miss correcting code comments when their theme is based on another theme; for example, referencing a widget or function that no longer exists in their own version of the theme.</div>
<div><br></div><div>Do we just RECOMMEND that the errors are corrected (since inaccurate comments don't affect how the theme operates), or is it REQUIRED that all commenting be as accurate as possible?</div><div><br>
</div><font color="#888888">
<div>Kirk</div>
</font><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>