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

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 20 March 2011 15:08 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 36C8C28C0D8 for <apps-review@core3.amsl.com>; Sun, 20 Mar 2011 08:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level:
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, 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 gdH9hy8Dt7J8 for <apps-review@core3.amsl.com>; Sun, 20 Mar 2011 08:08:30 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 2730E28C0CF for <apps-review@ietf.org>; Sun, 20 Mar 2011 08:08:30 -0700 (PDT)
Received: from [192.168.20.2] ((unknown) [212.183.140.35]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TYYYxwADL6mj@rufus.isode.com>; Sun, 20 Mar 2011 15:10:00 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D861898.2040101@isode.com>
Date: Sun, 20 Mar 2011 15:09:12 +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: SM <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com>
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:08:31 -0000

SM wrote:

> Hello,

Hi SM,
A couple of comments:

> I have been acting as Applications Area Review Team Lead for nearly a 
> year.  My assessment is that the team is still not fully functional.  
> Alexey made some suggestions.  Please comment on the following 
> suggested changes:
>
> There are three kinds of requests:
>
>  (a) Early reviews requested by the Apps Area ADs
>
>  (b) Review of a document in Last Call
>
>  (c) Document on the IESG Agenda
>
> I would like to minimize requests for (c) as it would mean a short 
> deadline for assignments.

GenArt and SecDir ask reviewers to confirm that their issues were 
addressed and/or appropriately discussed before documents are put on 
IESG telechat. Maybe we should do the same.
 [...]

> The review template at 
> http://www.apps.ietf.org/content/apps-review-template suggests that 
> the review should provide a one-sentence summary, e.g.:
>
>  (i)   This draft is ready for publication as an Experimental RFC
>
>  (ii)  This draft is almost ready for publication as an Informational 
> RFC but
>        has a few issues that should be fixed before publication
>
>  (iii) This draft is not ready for publication as a Proposed Standard and
>        should be revised before publication
>
> followed by major issues, minor issues and nits.
>
> Major issues are the type of concerns that will result in the document 
> being blocked until they are resolved.
>
> Minor issues are concerns about clarity or technical accuracy that 
> should be discussed and resolved before publication, but which would 
> normally be resolved between the authors and the reviewers.
>
> Nits are editorial or layout items.  They would ideally be resolved 
> before publication to make the document more readable.  Usually a 
> reviewer will not be looking for this type of issue, but may find some 
> in the course of the review.
>
> If you have any other suggestions, please send them to the list.

I also want to remind everybody that Apps Review Team reviews are 
treated as IETF LC comments and have no more weight then them. 
Sponsoring ADs should take them into considerations, but they might 
disagree with certain conclusions made by reviewers (e.g. which issues 
are major, which are minor, which are blocking, etc.).