Re: [apps-review] Early Cursory Reviews

[SM <[e-mail]>]

Hi Pete,
At 08:11 20-03-2011, Pete Resnick wrote:
>Even if you were assigned one per month, what would be the amount of 
>time you would want from "pickup out of the queue" until "completion 
>of review"? What I worry about is the same thing SM is trying to 
>address with the initial proposed changes: I don't want to wait for 
>a month to find out that someone is *not* going to be able to 
>complete a review and then we have to restart the month timer in the 
>queue, especially for what I'm hoping is an early cursory review. Is 
>one week enough time to complete a review of this sort, even if you 
>are only asked to do one per month?

The general agreement was one week for reviews going for IESG 
evaluation and two weeks for other reviews.  Here's when some reviews 
were assigned and when they were submitted:

draft-cheshire-dnsext-dns-sd            2010-12-02   2010-12-03
draft-ietf-sipcore-event-rate-control   2010-12-02   2010-12-15
draft-bryan-metalinkhttp                2011-01-22   2011-02-28
draft-ietf-hokey-ldn-discovery-06       2011-02-01   2011-02-04
draft-holsten-about-uri-scheme-06       2011-02-01   2011-02-07
draft-ietf-netconf-4741bis-07           2011-02-01   2011-02-07

Some reviewers take a week or less.  As some documents are be quite 
lengthy, the review takes more time.  There are also other factors to 
take into account, such as how familiar the reviewer is with the 
subject matter, to determine how long a review may take.

Although I mentioned it several times, team members do not generally 
ask to be put on leave.  I didn't do that last November and it caused 
some delays in posting the assignments.  It is easier for me to plan 
the work if I know about the availability of reviewers.

I suggest that we do a few cursory reviews so that the team gets a 
better idea of how it works and how much work it entails.

Best regards,
-sm