Re: [apps-review] Suggested changes for Applications Area Review Team

SM <sm+ietf@elandsys.com> Sat, 19 March 2011 22:42 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 090BE3A6A29 for <apps-review@core3.amsl.com>; Sat, 19 Mar 2011 15:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level:
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZ1dWJ0MpfdW for <apps-review@core3.amsl.com>; Sat, 19 Mar 2011 15:42:07 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id 938643A6A4B for <apps-review@ietf.org>; Sat, 19 Mar 2011 15:42:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.236.222]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p2JMhITI007188; Sat, 19 Mar 2011 15:43:30 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1300574612; bh=dbUWhNzKWnLJjSRnrpzObDNxqJA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=nht92GcPhjksbKGaKaBdIJqxN85QQjELc8LTFYPFbt9gM7NR7x8Te8MvMKr/AZC5u lDzgFhNNUYZltNpPhzvfNYd08xUygZdRxxwauc3UeKPI7WasI0hvBitXjKWISfCGRK tN38ED5HLoS2wuhWlf+3xPN9KOVuNC3+ergQxTIs=
Message-Id: <6.2.5.6.2.20110319140646.0c88b480@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 19 Mar 2011 15:38:54 -0700
To: Dave CROCKER <dcrocker@bbiw.net>
From: SM <sm+ietf@elandsys.com>
In-Reply-To: <4D85035A.6030308@bbiw.net>
References: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com> <4D84D06B.2070600@dcrocker.net> <6.2.5.6.2.20110319095600.0bc0c0d8@elandnews.com> <4D85035A.6030308@bbiw.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Pete Resnick <presnick@qualcomm.com>, apps-review@ietf.org
Subject: Re: [apps-review] Suggested changes for Applications Area Review Team
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Apps Area Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 22:42:11 -0000

Hi Dave,
At 12:26 19-03-2011, Dave CROCKER wrote:
>Before there was computer communications, the word protocol referred 
>to rules of conduct among people.  It is still used that way in some 
>circles.  I used the term in an attempt to invoke a well understood 
>design concept among independent participants -- human as well as 
>computer:  Failing to obtain explicit confirmation does not work, 
>for critical functions.

I tried to get the message through without any undue risk to my 
personal safety. :-)

>If there really is a time-critical aspect to the review, then it is 
>better to err on the side of sending a new query to a new reviewer 
>than to wait longer for the original reviewer to confirm. The 
>downside of contacting a new reviewer unnecessarily is two 
>reviews.  The downside of waiting too long to contact the new 
>reviewer could well be no reivews.

The explicit ACK would then mean five days for me to find a 
reviewer.  If a review has a two week deadline, it turns into one 
week to get the review out so that the Apps Area ADs can read it 
before an IESG evaluation.

The real issue here is that the review is being assigned too late in 
the process.  The time-critical aspect can be avoided by identifying 
the document to be reviewed earlier, i.e. when it is in Last Call.

>However that's different from setting expectations among all 
>participants -- that's us, in this case -- to know we have an 
>obligation to respond quickly.

I did not intend it to be viewed as an obligation.  It was meant as a 
target that I could tweak.

>If there are deeper problems with this group -- and I wasn't aware 
>there was -- then they need to be addressed directly and not through 
>bits of indirect cleverness in specified conventions.  We ain't very 
>good at subtlety around here...

There are problems in getting reviews done.  When I first took over, 
it looked like an impossible task.  Some people left the team and 
there was a shortage of XML reviewers.  Reviews requested by WG 
Chairs took months to be delivered due to reassignments.

>certainly agree it is excellent for you to do that.  (By the same 
>token, it is an extra burden for you and while it's great that you 
>are willing to carry that burden, I would not want to write it into 
>the formal job description, since the next person doing this job 
>might not be willing or able to incur that extra effort.)

I would not describe it as a burden as I signed up for it.  I would 
like to hand over a group that works to the next person doing the job.

BTW, you message to apps-review was automatically discarded.  I don't know why.

Best regards,
-sm