Re: Updating BCP 10 -- NomCom ELEGIBILITY

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 09 January 2015 19:26 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 DF0061A9250 for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 oA1EGWopCx7V for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:26:14 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF251A924E for <ietf@ietf.org>; Fri, 9 Jan 2015 11:26:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 07C8ABF09; Fri, 9 Jan 2015 19:26:13 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qll9ZrHzHXy; Fri, 9 Jan 2015 19:26:11 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.46.19.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DBDBCBF07; Fri, 9 Jan 2015 19:26:11 +0000 (GMT)
Message-ID: <54B02B51.1070308@cs.tcd.ie>
Date: Fri, 09 Jan 2015 19:26:09 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <ietf@ietf.org>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca>
In-Reply-To: <9772.1420830216@sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/H5WvWKM5-4PBNsG6_bJcZmXQ01E>
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: Fri, 09 Jan 2015 19:26:17 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 09/01/15 19:03, Michael Richardson wrote:
> So I would keep the 3/5 in-person meetings to *become* nomcom 
> eligible.
> 
> Once eligible, the rules for remaining eligible would be
> different.

I like that.

Given that remote participation is likely to continue changing
and hopefully improving in the coming years, if we do go down
this road I think it'd be good to figure some way to allow the
rules for continued eligibility to be changed without having
to update the BCP. That could be a task given to the IESG or
someone other I* group or the current nomcom could set the rule
for the next. I don't care which of those, but maybe the last
would be best, as nomcom members may know best what's needed,
(though some form of appeal against a nomcom getting themselves
all back next year would be needed:-)

Also, if we go there then I'd prefer that we apply that new
rule retrospectively as well so folks who were ever nomcom
eligible could "re-establish" that via participation any time.
(Unless that caused some tooling problem in checking
eligibility after someone volunteers.)

S.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUsCtRAAoJEC88hzaAX42iHgEH/j1SF85f4GfbOCvIAT8aJLjd
xVJijAaOuJt2rHwpjJxJSZPw9fGBwXE0haMKG7JGFRCC4eAr43LnNFzGiD7FuEga
yY7PJMfVGK1dMCUD+6E3yrfUPtiuT8I+67Ml9kJl9oW+Htb+HFzJKaq3pTfgG1N9
hNbPUKkvkWfOwIJeuw5U7IeSbYGxzLDsR1y6w3Isx7eKBzG4wJxB75VLEc1j5n/X
V9Qctk1OlOW/zBdkkapONJ5dUe5p6T5kb0pkL/pBIYEdaarMs8IgY+4hL4N9iI4V
YttSKNxQ9RtgBOuT0DlVyb2tJSG6FWQYtmRUfqUgwa7oTPRnvDSZShcZZF9EdHk=
=HqpJ
-----END PGP SIGNATURE-----