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

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 20 March 2011 15:03 UTC

Return-Path: <alexey.melnikov@isode.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 01B0A3A6BC5 for <apps-review@core3.amsl.com>; Sun, 20 Mar 2011 08:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level:
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, 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 lTY68UoYnVZB for <apps-review@core3.amsl.com>; Sun, 20 Mar 2011 08:03:20 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id F304B3A6BBC for <apps-review@ietf.org>; Sun, 20 Mar 2011 08:03:19 -0700 (PDT)
Received: from [192.168.20.2] ((unknown) [212.183.140.35]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TYYXkQADL1CD@rufus.isode.com>; Sun, 20 Mar 2011 15:04:50 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D861764.9040208@isode.com>
Date: Sun, 20 Mar 2011 15:04:04 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: dcrocker@bbiw.net
References: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com> <4D84D06B.2070600@dcrocker.net>
In-Reply-To: <4D84D06B.2070600@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Sun, 20 Mar 2011 15:03:21 -0000

Dave CROCKER wrote:
 [...]

>> followed by major issues, minor issues and nits.
>
> I usually follow a review format that has:
>
>    1. Summary of my understanding of the purpose and content of the 
> document. This is a common reviewing technique and it establishes a 
> base of factual understanding, before launching into the my opinions 
> about the quality of the content. If I have any misunderstanding of 
> the basics, it's better to surface that at the outset.  I also find 
> that the discipline of formulating the factual summary helps to 
> organize my thoughts about the draft.
>
>    2. Summary of major issues
>
>    3. Inline detailed comments.  For extended documents, the detailed 
> feedback is typically extensive and not subject to summarization.  I 
> frankly do not know how to break it out into clean distinctions of 
> major/minor/nits without dramatically more work.  In addition, my view 
> of major vs. minor vs. nit is likely not to match the authors'...
>
> Adding an explicit "rating" at the beginning seems like an excellent 
> idea; I'll try to remember to add one.

I think this is a good format and it is quite similar to what GenArt and 
SecDir teams are using.