[theme-reviewers] Closing Tickets and "Bumping" review ticket comments

[yulian yordanov]

I remember the time when we did reviews with helping to the developers and
the WP community in mind. There were no awards neither contests. But
whatever...

Fingli


2014-04-08 8:11 GMT+03:00 Srikanth Koneru <tskk79 at gmail.com>:

> yep, one ticket at a time, post review and then next
>
>
> On Tue, Apr 8, 2014 at 10:05 AM, rabin shrestha <sun_ravi90 at yahoo.com>wrote:
>
>> Yeah as Srikanth said, this month it seems it's going to be tough. But I
>> have seen that some theme reveiwers grabbing all the tickets to them selves
>> as soon as the ticket comes in theme updates. Is this allowed? Shouldn't
>> one make a review on one theme then jump into another. I think whether it's
>> theme update or new theme, one should make complete review and then only
>> jump into another ticket instead of grabbing all at once. What do you have
>> to say about this?
>>
>>
>>   On Tuesday, April 8, 2014 7:40 AM, Srikanth Koneru <tskk79 at gmail.com>
>> wrote:
>>  yep, good problem but how do we get new themes submitted and how does
>> lack of tickets effect the incentive program, its going to be hard to get
>> 1/10 or 1/4th this month for many of us. I am watching my queue all day and
>> cutting back on sleep and still find it hard to catch a ticket :(
>>
>>
>> On Tue, Apr 8, 2014 at 3:31 AM, Chip Bennett <chip at chipbennett.net>wrote:
>>
>> All,
>>
>> A couple requests:
>>
>> *Please do not "bump" comments in open tickets*. I follow-up on on
>> open/assigned tickets based on age of the ticket, as determined by latest
>> activity. Generally, I follow up on tickets that have had no activity for
>> over one week, and then close tickets that have not had activity for
>> another week. So, if you "bump" the comments in the tickets, by asking for
>> updates, it "resets" the clock on admin follow-up activity, meaning that
>> abandoned tickets will stay open for longer.
>>
>> Also, except for extreme circumstances, *please do not close tickets as
>> "not approved"*. Per our current workflow, we leave the ticket open to
>> allow for developer response. We want the ticket to stay open if the
>> developer is responsive, so that all updates take place in the same ticket.
>> If the developer fails to respond, I'll catch it in the ticket follow-up,
>> and will take care of closing them.
>>
>> Thanks for all of your contributions. We're currently running out of
>> tickets to be assigned, which is a very good problem!
>>
>> Chip
>>
>> _______________________________________________
>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>
>


-- 
Yulian Yordanov
post-scriptum.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140408/dc4e1b35/attachment.html>