Certainly, agreed!<div><br></div><div>But, it would be nice to do some forward thinking, too, so that, if/when the time is right, we can implement workflow changes to incorporate a security review.</div><div><br></div><div>
Maybe a topic for the next WPTRT IRC meeting?</div><div><br></div><div>In any case, I'll be focusing on the first issue (keeping the queue manageable) for the foreseeable future)...</div><div><br></div><div>Chip<br><br>
<div class="gmail_quote">On Wed, Oct 13, 2010 at 10:32 AM, Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Oct 13, 2010 at 11:27 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
These kinds of questions/issues demonstrate why the next step in Theme Reviews really needs to be to explore our original idea of having Security Ninjas, who focus on such issues, and who perform a post-quality-review Security review.<div>
<br></div><div>If we can keep the Review Queue manageable for a few weeks, would it be worthwhile to explore this idea further?</div></blockquote><div><br></div></div><div>I think the next two steps should be to keep the queue manageable for a few weeks, followed by an uploader overhaul, and see how that affects the queue.</div>
</div>
<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>