[theme-reviewers] Priority #1 track list seems to be stopped (Emil Uzelac)

[Srikanth Koneru]

I skipped your ticket because it was complex for me and moved on to next
tickets. You will have to wait for a more experienced reviewer.
The neuro ticket is not a stumbling block and not the reason for your
ticket being not reviewed yet.
Also don't reply to digests :)


On Mon, Jul 15, 2013 at 1:31 PM, Nicolas GUILLAUME <nguillaume at gmail.com>wrote:

> @reviewers : what is the exact priority rule for already approved theme :
> it seems that some tickets are sometimes reviewed and approved before older
> ones. Is it related to the complexity of the ticket or, are there some
> other rules to be aware of?
> Thank you for your answers.
>
> @Emil Uzelac : correct me if I am wrong but from my understanding, tickets
> are addressed in a chronological order, from the oldest to the newest. To
> deblock the queue, this ticket should then be treated in first :
> http://themes.trac.wordpress.org/ticket/13131.* It has been reopened 3
> weeks ago by Chip Bennett but the developer did not answer Chip's question
> since then.*
>
> In my case, the ticket is this one :
> http://themes.trac.wordpress.org/ticket/13241. I made many improvements
> in the code and I can't wait to see it live!
>
> Cheers,
> Nicolas.
>
>
>
>
> 2013/7/15 <theme-reviewers-request at lists.wordpress.org>
>
>> Send theme-reviewers mailing list submissions to
>>         theme-reviewers at lists.wordpress.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> or, via email, send a message with subject or body 'help' to
>>         theme-reviewers-request at lists.wordpress.org
>>
>> You can reach the person managing the list at
>>         theme-reviewers-owner at lists.wordpress.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of theme-reviewers digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: Webmaster Tools IDs - plugin territory? (Emil Uzelac)
>>    2. Re: Webmaster Tools IDs - plugin territory?
>>       (Philip M. Hofer (Frumph))
>>    3. Priority #1 track list seems to be stopped (Nicolas GUILLAUME)
>>    4. Re: Priority #1 track list seems to be stopped (Emil Uzelac)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 14 Jul 2013 19:59:23 -0500
>> From: Emil Uzelac <emil at uzelac.me>
>> To: "Discussion list for WordPress theme reviewers."
>>         <theme-reviewers at lists.wordpress.org>
>> Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?
>> Message-ID:
>>         <
>> CAEytdhevbPu39fVfjMe6Rh4E1m0TDDP-tCFms8sckgKMrAvCqA at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> No worries, it's all good. So here it is, one example:
>> http://codex.wordpress.org/Settings_API excluding "Cowboy Coding"
>> there should not be any issues with that.
>>
>> Or even better:
>> https://codex.wordpress.org/Theme_Customization_API
>>
>>
>>
>> On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <prodevstudio at gmail.com
>> >wrote:
>>
>> > If there is no core api for this kind of option/configuration then how
>> > does a developer add those properly? (I am not picking on you Emil so
>> don't
>> > take it personally)
>> >
>> > IMO these options are equivalent to robot.txt which is taken care of in
>> > core.
>> >
>> > In my view these are site configuration and theme should stay out of
>> them.
>> > It has nothing to do with presentation.
>> >
>> > WPTRT could propose that if a theme is going to provide an interface to
>> > set these value they need to be stores such a way that it can transfer
>> > from theme to theme and even plugins. WPTRT needs provide those
>> guidelines
>> > in where and how these config stored/retrived. so that user/site is not
>> impacted
>> > adversely when switching themes.
>> >
>> > I know not everyone will agree to above but it is in the best interest
>> of
>> > the end user.
>> >
>> > Regards,
>> >
>> > Azizur
>> >
>> >
>> >
>> > On Monday, 15 July 2013, Emil Uzelac wrote:
>> >
>> >> Hi Jason,
>> >>
>> >> Assuming that we're referring to Theme Options, this should be fine.
>> >>
>> >> *As long as this is not hardcoded and properly added :)*
>> >>
>> >> Thanks,
>> >> Emil
>> >>
>> >>
>> >> On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <jgc at jasonclarke.org
>> >wrote:
>> >>
>> >>> Hi Admins,
>> >>>
>> >>> Long-time listener, first-time caller here- in reviewing my first
>> theme,
>> >>> I remembered a recent list discussion on how Analytics-specific
>> fields in
>> >>> themes are not allowed because they're considered plugin territory.
>> >>>
>> >>> On a related note, I'm assuming that other similar fields such as
>> >>> "Google Webmaster Tools ID" and "Alexa ID" are also plugin territory-
>> can
>> >>> the admins confirm this is the case?
>> >>>
>> >>> Thank you!
>> >>> Jason
>> >>>
>> >>> PS - As a side/related note, it would be super helpful if the list
>> >>> archives where somehow searchable - that might be one more avenue for
>> >>> newbies like myself to check before emailing the list (assuming
>> guidelines
>> >>> haven't changed).
>> >>>
>> >>> --
>> >>> Jason Clarke
>> >>> http://jasonclarke.org
>> >>>
>> >>> ************************
>> >>>
>> >>> _______________________________________________
>> >>> theme-reviewers mailing list
>> >>> theme-reviewers at lists.wordpress.org
>> >>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> >>>
>> >>>
>> >>
>> >
>> > --
>> > Sent from Gmail Mobile
>> >
>> > _______________________________________________
>> > theme-reviewers mailing list
>> > theme-reviewers at lists.wordpress.org
>> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> >
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/3ce1bd48/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 14 Jul 2013 22:52:17 -0700
>> From: "Philip M. Hofer \(Frumph\)" <philip at frumph.net>
>> To: "Discussion list for WordPress theme reviewers."
>>         <theme-reviewers at lists.wordpress.org>
>> Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?
>> Message-ID: <B338F0A4D6B7404597E3A9EDB487E426 at furious>
>> Content-Type: text/plain; charset="utf-8"
>>
>> There are two sides of the fence on this subject, those who feel that
>> themes should not include anything that a plugin can do; which is fine.
>> There?s really nothing wrong with that method of thinking.  The OTHER side,
>> which includes myself and Emil and a bunch of others do not really think
>> that it?s a necessity to police those particular things.   A theme doesn?t
>> have to be cross compatible in every way except the way that the theme unit
>> looks.  Any extra feature to a theme is just that, a bonus.   Whether
>> someone switches theme?s constantly makes no difference.
>>
>> A HUGE majority of themes that are being used are actually commercial
>> themes: http://wordpress.org/themes/commercial/
>>
>> Those when switching to one theme or another will have some things no
>> longer work ? and that is fine.  There are plenty of ways, avenues and
>> programming that you can take to include those features into the theme you
>> switch to.
>>
>> The BIGGEST idea about that the don?t-worry-about-it group?s main
>> objective is to make the theme review process easier and faster to get
>> through.   The biggest thing that people get hung up on returning day after
>> day to review themes is how time consuming they are to go through.   We
>> also believe that it?s not the theme review team?s responsibility to
>> control that aspect of allowing a theme to have a feature or not, that is
>> up to the core dev?s to make that determination.
>>
>> Use all of the plugins, theme unit test and requirements for the
>> backlinks and other things.   Do the cursory views of everything that?s
>> important and move em through the review process.
>>
>>
>>
>> From: Emil Uzelac
>> Sent: Sunday, July 14, 2013 5:59 PM
>> To: Discussion list for WordPress theme reviewers.
>> Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?
>>
>> No worries, it's all good. So here it is, one example:
>> http://codex.wordpress.org/Settings_API excluding "Cowboy Coding"
>> there should not be any issues with that.
>>
>> Or even better:
>> https://codex.wordpress.org/Theme_Customization_API
>>
>>
>>
>>
>>
>> On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <prodevstudio at gmail.com>
>> wrote:
>>
>>   If there is no core api for this kind of option/configuration then how
>> does a developer add those properly? (I am not picking on you Emil so don't
>> take it personally)
>>
>>   IMO these options are equivalent to robot.txt which is taken care of in
>> core.
>>
>>   In my view these are site configuration and theme should stay out of
>> them. It has nothing to do with presentation.
>>
>>   WPTRT could propose that if a theme is going to provide an interface to
>> set these value they need to be stores such a way that it can transfer from
>> theme to theme and even plugins. WPTRT needs provide those guidelines in
>> where and how these config stored/retrived. so that user/site is not
>> impacted adversely when switching themes.
>>
>>
>>   I know not everyone will agree to above but it is in the best interest
>> of the end user.
>>
>>   Regards,
>>
>>   Azizur
>>
>>
>>
>>   On Monday, 15 July 2013, Emil Uzelac wrote:
>>
>>     Hi Jason,
>>
>>     Assuming that we're referring to Theme Options, this should be fine.
>>
>>     As long as this is not hardcoded and properly added :)
>>
>>     Thanks,
>>     Emil
>>
>>
>>
>>     On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <jgc at jasonclarke.org>
>> wrote:
>>
>>       Hi Admins,
>>
>>       Long-time listener, first-time caller here- in reviewing my first
>> theme, I remembered a recent list discussion on how Analytics-specific
>> fields in themes are not allowed because they're considered plugin
>> territory.
>>
>>       On a related note, I'm assuming that other similar fields such as
>> "Google Webmaster Tools ID" and "Alexa ID" are also plugin territory- can
>> the admins confirm this is the case?
>>
>>       Thank you!
>>       Jason
>>
>>       PS - As a side/related note, it would be super helpful if the list
>> archives where somehow searchable - that might be one more avenue for
>> newbies like myself to check before emailing the list (assuming guidelines
>> haven't changed).
>>
>>
>>       --
>>       Jason Clarke
>>       http://jasonclarke.org
>>
>>       ************************
>>
>>
>>       _______________________________________________
>>       theme-reviewers mailing list
>>       theme-reviewers at lists.wordpress.org
>>       http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>>
>>
>>
>>   --
>>   Sent from Gmail Mobile
>>
>>   _______________________________________________
>>   theme-reviewers mailing list
>>   theme-reviewers at lists.wordpress.org
>>   http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/273c87f7/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Mon, 15 Jul 2013 08:43:57 +0200
>> From: Nicolas GUILLAUME <nguillaume at gmail.com>
>> To: theme-reviewers at lists.wordpress.org
>> Subject: [theme-reviewers] Priority #1 track list seems to be stopped
>> Message-ID: <51E39A2D.40107 at gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Hi,
>>
>> There are some tickets older than 7 days in the list (including the
>> ticket for my theme Customizr).
>>
>> I can see that the top of the list ticket is reopened since 3 weeks and
>> seems to lock all other tickets...
>>
>> Is there an issue there? Could somebody please take care of that?
>> Thanks and best regards,
>> Nicolas
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 15 Jul 2013 01:48:05 -0500
>> From: Emil Uzelac <emil at uzelac.me>
>> To: "Discussion list for WordPress theme reviewers."
>>         <theme-reviewers at lists.wordpress.org>
>> Subject: Re: [theme-reviewers] Priority #1 track list seems to be
>>         stopped
>> Message-ID:
>>         <CAEytdhfbdKQT-o0fumAA36i8=
>> o+qguTrC+n1ChzLiUB8_JdUng at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> What needs to be done?
>> On Jul 15, 2013 1:44 AM, "Nicolas GUILLAUME" <nguillaume at gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > There are some tickets older than 7 days in the list (including the
>> ticket
>> > for my theme Customizr).
>> >
>> > I can see that the top of the list ticket is reopened since 3 weeks and
>> > seems to lock all other tickets...
>> >
>> > Is there an issue there? Could somebody please take care of that?
>> > Thanks and best regards,
>> > Nicolas
>> > ______________________________**_________________
>> > theme-reviewers mailing list
>> > theme-reviewers at lists.**wordpress.org<
>> theme-reviewers at lists.wordpress.org>
>> > http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130715/cb88feaf/attachment.html
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>> ------------------------------
>>
>> End of theme-reviewers Digest, Vol 38, Issue 72
>> ***********************************************
>>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130715/ed9d0666/attachment-0001.html>