So, same thing, except for white-listed *usernames*, rather than *theme-slugs*?<div><br></div><div>My issue with that idea is that, then, even that user's *non-niche* Themes would bypass the checks (and most likely, the Reviewer will have no idea of this occurrence - unless the Trac ticket includes some relevant notification). Thus, if we're going to go to the trouble of white-listing, I think theme-slug makes more sense than username.</div>
<div><br></div><div>And speaking of Trac handling: I like the idea of appending a relevant *ticket keyword* for such Themes, so that we can process them separately.</div><div><br></div><div>Chip<br><br><div class="gmail_quote">
On Fri, Oct 28, 2011 at 1:55 PM, 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;">
<div class="im">On Fri, Oct 28, 2011 at 1:50 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> I am worried about the potential for abuse, if this is solely tag-based.<br>
> What about adding a theme-slug bypass filter to the uploader script, whereby<br>
> "niche" Themes bypass non-critical checks, based on a registered theme-slug?<br>
<br>
</div>I would prefer something where we whitelist actual user accounts.<br>
<br>
Somebody wanting special case access submits their theme to the list<br>
(not to the uploader, BTW), and if whatever process decides that they<br>
deserve it, we flag their username to bypass the more stringent<br>
checks.<br>
<div><div></div><div class="h5"><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>
</div></div></blockquote></div><br></div>