Re: Updating BCP 10 -- NomCom ELEGIBILITY

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 11 February 2015 21:23 UTC

Return-Path: <mcr@sandelman.ca>
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 929C81A6EDB for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 13:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7ZcjvmJNpksq for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 13:23:14 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5AA21A1F70 for <ietf@ietf.org>; Wed, 11 Feb 2015 13:23:13 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 27596203CD; Wed, 11 Feb 2015 16:30:40 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C74FE63A21; Wed, 11 Feb 2015 16:23:12 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B2114637F4; Wed, 11 Feb 2015 16:23:12 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
In-Reply-To: <20150211205825.A17AC1A8A92@ietfa.amsl.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <04AED0595DF62A6F1013479D@JcK-HP8200.jck.com> <54DB5CBE.3070502@dcrocker.net> <54DB66A0.1050006@pi.nu> <BE226640-1857-4232-9D4F-78445D82776A@nominum.com> <54DB78A1.5020407@pi.nu> <20150211205825.A17AC1A8A92@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 11 Feb 2015 16:23:12 -0500
Message-ID: <3400.1423689792@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/M_2zAGn645-vbMjSL9R-H9-T27Q>
Cc: ietf <ietf@ietf.org>
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: Wed, 11 Feb 2015 21:23:27 -0000

On this topic, I asked the secretariat:

> Putting aside the problems of different emails used to register,  is it a
> simple query against the registration database (which I think is not in
> anyway connected to the datatracker), to determine how many people are
> nomcom eligible at a given time?  (I don't care who they are)

> Can this run from a historical point of view?

> Regardless, if we can run this, could we run it three times a year (after
> each meeting), and capture that data?



Michael StJohns <mstjohns@comcast.net> wrote:
    > At 10:43 AM 2/11/2015, Loa Andersson wrote:
    >>> The operation of each nomcom are pretty opaque to those who are not on it.   For those who have interacted with a nomcom as candidates, such an impression might exist.   It's possible that nomcom liaisons or chairs could speak to this.   However, since nomcom proceedings are supposed to be confidential, I don't know how much they could really say.   Because these properties of the nomcom are intentional and useful, it does make sense to be particularly careful about how nomcom eligibility is determined and not just trust to peoples' good natures.
    >>
    >> Sorry I was not talking about the operations of the NomCom, but how
    >> many drones we have in the pool. Looking at a few of the last pools
    >> (the +100) I dare say that the figure is low, if we regardless of that
    >> have problems in the NomCom operations no rule whatsoever will help.


    > It would be interesting to take a look at the "large company" pool volunteers over say the past 20 years and figure out a way of giving them an activity factor (e.g. attendee vs contributor) - but finding an objective scale that we could all agree with to assign such activity factor would be difficult.

    > I say large company because about 55-60% (rough number - just from scanning) or so of the voting members of the Nomcoms over the last 20 years appear have come from companies with large numbers of attendees at the IETF - said companies tending to be what I think of as "big".

    > The other number to look at might be the number of attendees (percentage wise) per company per meeting vs number of volunteers (percentage wise) per company per nomcom.  All things being equal I would expect those percentages to be close to identical.  I would expect where the nomcom volunteer percentage exceeds the attendee percentage to maybe be indicative of a desire by the company to place members on the Nomcom.

    > Later, Mike




--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-