LOL... #dammit<br><br><div class="gmail_quote">On Wed, Oct 13, 2010 at 11:46 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Wed, Oct 13, 2010 at 10:38 AM, Simon Prosser <<a href="mailto:pross@pross.org.uk">pross@pross.org.uk</a>> wrote:<br>
> The new uploader *should* take up the slack and stop a lot of the crap<br>
> getting through, well that's what im hoping for.<br>
<br>
Interesting conundrum here. If the uploader actually did prevent bad<br>
code getting through (assume it's magically perfect and checks for all<br>
required stuff as well as preventing all bad stuff getting through),<br>
then that actually increases the workload on the reviewers. Why?<br>
Because now there's no longer any obvious things for a reviewer to<br>
check for to bounce themes back quickly. Theme authors getting<br>
rejected by the theme uploader are more likely to fix their themes and<br>
try again. So every theme making it through would have to be fully<br>
checked, as all requirements would be met. ;-)<br>
<font color="#888888"><br>
-Otto<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>
</font></blockquote></div><br>