I agree with doing our best to keep the process easily understood and easily implemented by all involved: Theme Authors and Theme Reviewers ... our goal is to provide more for the community and especially the end-users.<br>
Since @Otto feels confident enough to basically say he can sort out pretty much anything we come up with notwithstanding any truly outlandish ideas.<br><br>I agree the next step should be to get buy-in from WordPress.org et al.; the question is now: whom do we take this to directly?<br>
<br>... or, Otto? Do we just flesh out the idea and have you put it into code/action?<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 4:32 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I was trying to start from the most-simple, and work toward more complex as necessary.<div><br></div><div>At the simplest, the Theme developer documents the "niche" nature of the Theme in readme.txt, and explains its special usage. At the same end of the complexity spectrum, the Theme developer adds the special-consideration rationale in as an in-ticket comment, before the review commences.</div>
<div><br></div><div>At the more-complex end of the spectrum, but easier on the Reviewers, we would have a submission form to request a theme-slug to be white-listed, with an explanation of the "niche" nature of the Theme, and rationale for special consideration.</div>
<div><br></div><div>From the user perspective, I would also like to see a new Filter Tag class: perhaps "Special-Use Themes", with tags such as "landing-page", etc. (or, even just "special-use").</div>
<div><br></div><div>I'm with you: I'm all for getting more, great Themes into the repository, and for encouraging and facilitating innovative uses of WordPress Themes. The bigger problem - and the one that we can't solve - will be the same problem we have with Child Themes: the powers-that-be may kibbosh the entire idea, due to lack of Extend/wp-admin back-end exposure/handling of niche Themes. So, we should get their buy-in before we explore the idea too far.</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 2:37 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm good with something like that.<br>I think we also need to specify the Theme Author must explain why they need/want to have their specific theme by-pass the upload checks in their "User request"; maybe a form submission (a la plugins) rather than having it hit this mailing list?<br>
<br>I'm all for finding a way to open the repository to quality niche themes, but something tells me Pandora's box may be in the shadows ... are we missing anything?<br><br><br clear="all">Cais.<div><div></div><div>
<br>
<br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 3:29 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here's how I'm currently envisioning it:<div><ol><li>User requests theme-slug whitelist</li><li>Otto/Pross adds theme-slug to bypass white-list</li><li>User uploads Theme, using the Uploader</li><li>Ticket created</li>
<li>Ticket keyword "niche" (or "uploader-bypass" or whatever) appended</li><li>Ticket gets sorted into new Queue (just like BuddyPress Themes have their own queue)</li></ol></div><div>From there, the process is pretty much the same, except that the actual *review* will be far more manual.</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 2:23 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<div><div></div><div><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" target="_blank">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>On Fri, Oct 28, 2011 at 2:00 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">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><br>
-Otto<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></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>