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

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 21 March 2011 18:01 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 7F7B928C19B for <apps-review@core3.amsl.com>; Mon, 21 Mar 2011 11:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 uY-a-Cmkb6TI for <apps-review@core3.amsl.com>; Mon, 21 Mar 2011 11:01:48 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 6B3AF28C194 for <apps-review@ietf.org>; Mon, 21 Mar 2011 11:01:48 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TYeS5wADL78v@rufus.isode.com>; Mon, 21 Mar 2011 18:03:20 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D8792AE.9070208@isode.com>
Date: Mon, 21 Mar 2011 18:02:22 +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: John C Klensin <klensin@jck.com>, SM <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com> <4D861898.2040101@isode.com> <6.2.5.6.2.20110320113434.0c1626b8@elandnews.com> <7AE95D9A5FCB3646106E712E@[192.168.1.128]>
In-Reply-To: <7AE95D9A5FCB3646106E712E@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; 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: Mon, 21 Mar 2011 18:01:49 -0000

John C Klensin wrote:

>--On Sunday, March 20, 2011 13:08 -0700 SM
><sm+ietf@elandsys.com> wrote:
>
>  
>
>>One suggested change that has not be discussed is the Team
>>Lead.  The Team Lead should have a good relationship with the
>>Apps Area ADs as he or she works under their direction.
>>Keeping a Team Lead for too long does not ensure continuity.
>>    
>>
SM, I would like to know why you think that.
I don't think there is a need for changing the Team Lead every year.

>>I would like the team to discuss with the Apps Area ADs when
>>they meet in person about:
>>
>>  (i)   Should the Team Lead be selected for a year only
>>
No, unless this is what the Team Lead candidate wants.

>>  (ii)  Should the Team Lead have IESG experience to provide
>>better guidance to reviewers
>>
I don't think so.

>One comment on that question: one of the things the IETF does
>much less well than it should is to arrange things that
>familiarize new people with how the system works and generally
>to do leadership development.  While one might gain something in
>efficiency by having a team lead who was a former AD, it would
>be _far_ better, IMO, to use the position as an opportunity for
>increased understanding of the community, actors, and dynamics
>(as I am sure it has been for you).   As long as things are
>fairly open, there will always be present and ex-ADs ready to
>step in and provide that sort of guidance, perhaps even when the
>team lead doesn't want it :-).  But let's not throw away the
>opportunity to read more people in on the system in order to
>gain small marginal efficiencies by reusing the same folks over
>and over again.
>
+100.

>
>  
>