<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><font class="Apple-style-span" face="Verdana, Arial, Helvetica, sans-serif">Hi</font><div><font class="Apple-style-span" face="Verdana, Arial, Helvetica, sans-serif"><br></font></div><div><font class="Apple-style-span" face="Verdana, Arial, Helvetica, sans-serif">In the theme review guide by Chip, it says stylesheets must be enqueued, so does that mean that if the main stylesheet is empty except for 3 @import declarations, the theme isn't valid?<br></font><div id="1" style="font-family: Verdana, arial, Helvetica, sans-serif; "><br>---- On Wed, 19 Oct 2011 10:00:02 -0200 <b> <<a href='mailto:theme-reviewers-request@lists.wordpress.org' target='_blank'>theme-reviewers-request@lists.wordpress.org</a>></b> wrote ---- <br></div><br><blockquote style="font-family: Verdana, arial, Helvetica, sans-serif; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(0, 0, 255); padding-left: 6px; ">Send theme-reviewers mailing list submissions to <br> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a> <br> <br>To subscribe or unsubscribe via the World Wide Web, visit <br> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a> <br>or, via email, send a message with subject or body 'help' to <br> <a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a> <br> <br>You can reach the person managing the list at <br> <a href="mailto:theme-reviewers-owner@lists.wordpress.org" target="_blank">theme-reviewers-owner@lists.wordpress.org</a> <br> <br>When replying, please edit your Subject line so it is more specific <br>than "Re: Contents of theme-reviewers digest..." <br> <br> <br>Today's Topics: <br> <br> 1. Re: [WordPress Themes] Custom Community, new version 1.8.7 (Otto) <br> 2. Re: [WordPress Themes] Custom Community, new version 1.8.7 (Otto) <br> 3. Re: [WordPress Themes] Custom Community, new version 1.8.7 <br> (Chip Bennett) <br> <br> <br>---------------------------------------------------------------------- <br> <br>Message: 1 <br>Date: Tue, 18 Oct 2011 14:53:41 -0500 <br>From: Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> <br>Subject: Re: [theme-reviewers] [WordPress Themes] Custom Community, <br> new version 1.8.7 <br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a> <br>Message-ID: <br> <CAD-FghxE8dhO5WfuLd+q<a href="mailto:KmKFnx3FnELjL-9jmH6XpC3RQRHUOA@mail.gmail.com" target="_blank">KmKFnx3FnELjL-9jmH6XpC3RQRHUOA@mail.gmail.com</a>> <br>Content-Type: text/plain; charset=ISO-8859-1 <br> <br>On Tue, Oct 18, 2011 at 2:51 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote: <br>> We "mark as old" Themes that are not-approved. They stay in the Extend queue <br>> until we do so. <br> <br>Oh. <br> <br>The upload process automatically marks any previous pending versions <br>of a theme as "old" when a new version gets uploaded, so assuming the <br>theme author is going to fix the problems with the theme, the old <br>version will disappear when they upload a new one. <br> <br>So unless you're picky about an orderly pending list, it's not <br>actually necessary to take that step. <br> <br>-Otto <br> <br> <br>------------------------------ <br> <br>Message: 2 <br>Date: Tue, 18 Oct 2011 14:56:12 -0500 <br>From: Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> <br>Subject: Re: [theme-reviewers] [WordPress Themes] Custom Community, <br> new version 1.8.7 <br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a> <br>Message-ID: <br> <CAD-Fghye8qQPDCiWK7sT<a href="mailto:v8no5d_LFY4O2qy2XhB7jLdR-VanDA@mail.gmail.com" target="_blank">v8no5d_LFY4O2qy2XhB7jLdR-VanDA@mail.gmail.com</a>> <br>Content-Type: text/plain; charset=ISO-8859-1 <br> <br>On Tue, Oct 18, 2011 at 2:40 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote: <br>> If we went a route similar to this, I would propose that instead of using <br>> PRIORITY, we update the Trac workflow to add an additional STATE, of <br>> "review-complete" (or whatever is appropriate). <br>> And if we go this route, I would suggest looking into adding a TRAINEE user <br>> level, for which the only elevated permission is to change the ticket state <br>> to "review-complete". <br>> From purely a workflow standpoint, using the "needs-sync" priority is really <br>> no improvement over using keywords (either way, the admin still has to <br>> change the priority, just as the admin currently has to remove the sync <br>> keyword). <br> <br>Agreed on the workflow, however that's a bit beyond what I have the <br>capability to easily alter at present. I've emailed the sysadmins <br>about a similar change, when they get back to me I'm going to try to <br>get a copy of the existing ini file and set up a test trac. Then I can <br>see about making some changes to the workflow. <br> <br>-Otto <br> <br> <br>------------------------------ <br> <br>Message: 3 <br>Date: Tue, 18 Oct 2011 15:00:37 -0500 <br>From: Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> <br>Subject: Re: [theme-reviewers] [WordPress Themes] Custom Community, <br> new version 1.8.7 <br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a> <br>Message-ID: <br> <CAPdLKqewFqFJo+mKoh-5<a href="mailto:f1FRnuV+e6CU06c+XZ3QMdVSyRVTvg@mail.gmail.com" target="_blank">f1FRnuV+e6CU06c+XZ3QMdVSyRVTvg@mail.gmail.com</a>> <br>Content-Type: text/plain; charset="iso-8859-1" <br> <br>The assumption that Theme developers re-submit their Themes with fixes is... <br>not terribly valid, unfortunately. <br> <br>Also, having the Extend queue as clean as possible helps to find the Themes <br>that need to be synchronized as *live*. <br> <br>And: you know me. I'm way past "picky"; I'm a pedant. <br> <br>Chip <br> <br>On Tue, Oct 18, 2011 at 2:53 PM, Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote: <br> <br>> On Tue, Oct 18, 2011 at 2:51 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> <br>> wrote: <br>> > We "mark as old" Themes that are not-approved. They stay in the Extend <br>> queue <br>> > until we do so. <br>> <br>> Oh. <br>> <br>> The upload process automatically marks any previous pending versions <br>> of a theme as "old" when a new version gets uploaded, so assuming the <br>> theme author is going to fix the problems with the theme, the old <br>> version will disappear when they upload a new one. <br>> <br>> So unless you're picky about an orderly pending list, it's not <br>> actually necessary to take that step. <br>> <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>> <br>-------------- next part -------------- <br>An HTML attachment was scrubbed... <br>URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111018/c36c1f97/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111018/c36c1f97/attachment-0001.htm</a>> <br> <br>------------------------------ <br> <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> <br>End of theme-reviewers Digest, Vol 17, Issue 60 <br>*********************************************** <br></blockquote><br></div></body></html>