Re: Updating BCP 10 -- NomCom ELEGIBILITY

Michael Richardson <mcr@sandelman.ca> Wed, 14 January 2015 17:43 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 9D1E61A9143 for <ietf@ietfa.amsl.com>; Wed, 14 Jan 2015 09:43:48 -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 20Xgwnrb_Ts8 for <ietf@ietfa.amsl.com>; Wed, 14 Jan 2015 09:43:43 -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 301941A1A86 for <ietf@ietf.org>; Wed, 14 Jan 2015 09:43:42 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A7B1520098; Wed, 14 Jan 2015 12:49:27 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C6891637FE; Wed, 14 Jan 2015 12:43:39 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id AF5E1637EC; Wed, 14 Jan 2015 12:43:39 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
In-Reply-To: <CAMm+LwgYqgQBHFR43oXM8nEraFj1uiH0WoKLBNhw+OSSPB3UaQ@mail.gmail.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> <201501102231.t0AMV21b009190@colo4.roaringpenguin.com> <22671.1421006639@sandelman.ca> <CAMm+LwgYqgQBHFR43oXM8nEraFj1uiH0WoKLBNhw+OSSPB3UaQ@mail.gmail.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
Date: Wed, 14 Jan 2015 12:43:39 -0500
Message-ID: <17472.1421257419@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4q9duKWMh5ovPLLz_RUUskDXiXw>
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, 14 Jan 2015 17:43:48 -0000

{I'm not at all in favour of making jabber scribe a way to contribute.
I don't think you can do it remotely, and if you are already in physical
attendance, then you already are eligible.  I am not trying to make being
eligible harder; but rather more equitable given that travel is often
difficult.
People are not, in general, lining up to volunteer for nomcom}

Phillip Hallam-Baker <phill@hallambaker.com>; wrote:
    > One issue with Michael's original proposal is that if the details of
    > implementation are not done right it can create problems for verifying
    > eligibility. And it is not just a matter of the chair of one nomcon handing
    > a spreadsheet on to the next because a lot of people who are eligible on
    > attendance grounds are ineligible on other grounds.

The current tool involves putting an email into a web form and looking at the
results.  I turned that into a perl script with Net::HTTP, and some screen
scraping.  
Then, it involves some back and forth with people who thought that they were
eligible, but were not trivially verifiable, and some additional emails that
they used to register.
The registration system is not, to my knowledge, connected to the datatracker.

While there is a button on the registration form, it does not interlock with
the datatracker; lots of people push that button who have never been to a
meeting, for instance.

So the things that I said: uploading a draft, shepherd'ing a document, being
a WG chair, etc. are things that the datatracker quite clearly already knows
about.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [