Re: Updating BCP 10 -- NomCom ELEGIBILITY

John C Klensin <john-ietf@jck.com> Sun, 11 January 2015 01:08 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46011A1A98 for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 17:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.101
X-Spam-Level: *
X-Spam-Status: No, score=1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cX1xdlneohWg for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 17:08:54 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E20A1A01F0 for <ietf@ietf.org>; Sat, 10 Jan 2015 17:08:53 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=P5) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YA71N-000DA2-Hd; Sat, 10 Jan 2015 20:08:49 -0500
Date: Sat, 10 Jan 2015 20:08:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, ietf <ietf@ietf.org>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
Message-ID: <23443CE3987807F72F2B3D3D@P5>
In-Reply-To: <20150110223107.C0B7B1A03C7@ietfa.amsl.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <54B02B51.1070308@cs.tcd.ie> <5237.1420905553@sandelman.ca> <20150110183324.5CED31A6F11@ietfa.amsl.com> <54B17DDB.3080005@gmail.com> <20150110223107.C0B7B1A03C7@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uq_Ra_yzFNZxEJPI_D54iF786Yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2015 01:08:56 -0000


--On Saturday, 10 January, 2015 17:31 -0500 Michael StJohns
<mstjohns@comcast.net>; wrote:

>...
> Everyone who volunteers for Nomcom must have at least 3
> certified and approved instances of being a note taker or
> jabber scribe for a full set of sessions for a specific
> working group in the past 5 meetings in addition to attending
> 3 of 5 meetings.  "Approved" means that the notes are
> complete, correct and readable as viewed by the majority of
> the WG chairs and editors.  "Certified" means that the WG
> chair(s) heard you volunteer and noted that in the minutes.
> Notes may be taken in any language, but must be translated to
> English within a month of the end of the IETF meeting.
> Multiple note takers may be certified at any given meeting and
> all notes gleaned from any of them will be added to the
> meeting record.

> The above has the advantage that it is a relatively small bar,
> it provides a benefit to the IETF, and its annoying enough to
> discourage the run of the mill gamers from participating.

Interesting.  Looking at the volunteer list for the last few
years, I've wondered whether we are developing a collection of
people (or the companies who support their IETF participation)
who would rather be on the Nomcom than do substantive technical
work.  Certainly not all volunteers for the Nomcom are like
that, but I wonder.  It seems to me that the approach above
would help drive some portion of the community toward Nomcom
roles and that conditions needed to get them and away from being
document editors, WG secretaries or chairs, etc.  

I agree with your concern about oligarchies, but I think the
Nomcom model depends on Nomcom members being more or less a
random sample of participants, ideally active participants, in
the IETF.  Changing things to the point that we end up
effectively splitting IETF participation into  a
Nomination-Selection class of people and a Technical Work and
Leadership Role class of people would not be, IMO, beneficial.

    john