Queue Weekly Status 2016-01-22

Review Queue state (listed add-ons only)

The tables below represent the state of the review queues at different points in time, divided into 3 “buckets” depending on how long they have been waiting. Ideally we want all nominations and updates to be under 5 days, so our goal is to have 100% of reviews on the third column.

Full Review Nominations

             10 days+     5-10 days       5 days-    Total
12/01        83 (70%)      22 (19%)      13 (11%)      118
01/01       143 (76%)      30 (16%)       14 (7%)      187
Now         124 (69%)      27 (15%)      28 (16%)      179

Full Review Updates

             10 days+     5-10 days       5 days-    Total
12/01        19 (31%)       9 (15%)      33 (54%)       61
01/01        61 (64%)      22 (23%)      12 (13%)       95
Now            1 (4%)        0 (0%)      23 (96%)       24

Preliminary Reviews

             10 days+     5-10 days       5 days-    Total
12/01        64 (47%)      37 (27%)      34 (25%)      135
01/01       148 (67%)      53 (24%)       20 (9%)      221
Now           9 (15%)      21 (35%)      30 (50%)       60

Reviewer Contributions

     Nominations    Updates    Prelim.  Admin flag   Info req  Total
Nov    513 (13%) 1085 (27%) 1984 (50%)     12 (0%)   364 (9%)   3958
Dec     660 (9%) 1308 (18%) 5240 (70%)     43 (1%)   187 (3%)   7438
Jan     464 (7%) 2126 (30%) 4255 (61%)     13 (0%)   149 (2%)   7007

Nominations: full review nominations.
Updates: full review updates.
Prelim.: preliminary reviews.
Admin flag: reviews escalated to admin review.
Info req: information requests to authors.


More

For more information on how the review process works, and how you can check your add-on review status, please read An Overview of the AMO Review Process.

It looks like my extension got stuck in the 15% that are preliminary reviews more than 10 days long.

Is there anything I can do to make the review process easier for you guys? I want to start releasing this to users that know the link.

The name of the extension is Toolkit for YNAB. I’m happy to do anything that would help.

It looks like the add-on was incorrectly rejected yesterday. I moved it back to the review queue.

Not using Kango would go a long way in shortening your waiting time, but that may be required for your add-on so I don’t want to push this point too hard.

Yeah, unfortunately our primary user base is Chrome, so if I was going to stop using Kango we’d cut support for Firefox altogether.

Do you guys have an approximate waiting time for us? I’m getting a lot of pressure from users asking if it’s doing something dodgy because it’s taking a while to be reviewed. I’m assuming Kango flags us as needing an admin to review?

It doesn’t flag you, but for all practical purposes it is, since most reviewers won’t fell comfortable reviewing it.

Fortunately, we’re working on an extensions API largely based on the Chrome one, so in a few months you’ll be able to have a cross-browser extension without needing such frameworks.

Unfortunately we support Safari as well, so until all 3 use the same API we’ll be on Kango.

Given how long it’s going to take to get a review should I switch to requesting a full review? I did preliminary to get it out the door quickly, but it feels like it might be better to just get it all out of the way at once. Will I lose my place in the queue if I request a full review now?

I would suggest to go with full, since ultimately there will be little difference in the waiting time, given that the determining factor is kango use.