[theme-reviewers] Thanks to All
chip at chipbennett.net
Fri Mar 9 14:04:35 UTC 2012
For me, the key, determining factor is this: does the Theme developer
appear to be willing and intent to conform to the Guidelines? If so, so
whatever you can to help the developer pass the review, including leaving
previous tickets open, and claiming new tickets, to help expedite the
After a few reviews, you'll find that it's pretty easy to tell these types
of developers from others. We want to work with and to help and to
encourage the developers who are genuinely trying to submit a good Theme,
or who want to give back to the WordPress community by contributing a
Theme, or even who are merely trying to learn the Theme development process.
To that end, use your best judgement. :)
On Fri, Mar 9, 2012 at 4:42 AM, Qamar Ashraf <life.object at gmail.com> wrote:
> Thanks Emil,
> Please guide me in the following points as well.
> - Let a theme is approved. I will definitely move into DIFF REVIEW
> only, if it has not major changes.
> - I usually see some other parts of code like header, footer, menus
> etc. So let find some Required or Recommended items are in need to address.
> - Should i ask the reporter to fix it ?
> - Or, Approve the theme and leave recommendations for the next
> theme revision.
> On Fri, Mar 9, 2012 at 3:34 PM, Emil Uzelac <emil at themeid.com> wrote:
>> If Theme was previously approved and if there are no major coding changes
>> in functionalities or features, we only review the Diff. Grace period is up
>> to reviewer, I like to give couple of days to ticket owner giving them a
>> chance to fix the issues, re-submit Theme and of course note the
>> last reviewed ticket in trac once the changes are ready.
>> Theme in question did add support for header and background, however did
>> not fulfill the requirements. (*Theme is recommended to incorporate the
>> following WordPress core features, but is not required to do so. However,
>> if incorporated, features must support the core WordPress implementation:
>> *) this was left out from previous reviews, but what can we do now.
>> I've seen cases (not many, but they exist) when author does a complete
>> Theme overhaul each time new ticket was submitted, this is most definitely
>> time to start from scratch, even in that case it would be nice to keep
>> ticket open for couple of days, since it was already approved and in
>> repository anyways. Same goes for all other major changes and that's why we
>> have the Diff to see what was done since last review.
>> I personally have zero tolerance for spam, sponsored links etc, but when
>> author really tries hard and its here to truly contribute, we need to help
>> them as much as we can.
>> On Fri, Mar 9, 2012 at 4:05 AM, Qamar Ashraf <life.object at gmail.com>wrote:
>>> I have just studied comments in my reviewed theme i.e
>>> - http://themes.trac.wordpress.org/ticket/6834
>>> I am writing here, because i am happy to be the part of co-operative
>>> and straight forward theme reviewers team. I also invite others to be the
>>> part of WPTRT, as i have learned a lot and still learning.
>>> Once again thanks to, Emiluzelac and Chip Bennett.
>>> One little question as well :)
>>> - In which conditions, we can give a grace period to the theme
>>> reporter and how much ?
>>> Qamar Ashraf
>>> Project Manager
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
> Qamar Ashraf
> Project Manager
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers