I like the theme-slug white-list, versus the author white-list, in conjunction with a tag/keyword.<br>Also, the reviewer(s) will need to be able to easily see the theme would require special attention after the first approved version goes live.<br>
<br>I take it this would be a completely manual process into the repo, or would we be going with a proper submission after the theme passes the niche/non-niche criteria and the white-list(s) have been updated?<br><br><br clear="all">
Cais.<br>
<br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 3:03 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 2:00 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> So, same thing, except for white-listed *usernames*, rather than<br>
> *theme-slugs*?<br>
> My issue with that idea is that, then, even that user's *non-niche* Themes<br>
> would bypass the checks (and most likely, the Reviewer will have no idea of<br>
> this occurrence - unless the Trac ticket includes some relevant<br>
> notification). Thus, if we're going to go to the trouble of white-listing, I<br>
> think theme-slug makes more sense than username.<br>
> And speaking of Trac handling: I like the idea of appending a relevant<br>
> *ticket keyword* for such Themes, so that we can process them separately.<br>
<br>
</div>Theme slug would work too.<br>
<br>
Tags or keywords could be added too.<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>