Re: Updating BCP 10 -- NomCom

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 09 January 2015 19:17 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 027291A8F3B for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:17:37 -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 QLGOffPiug0U for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:17:34 -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 A62661A8ABA for <ietf@ietf.org>; Fri, 9 Jan 2015 11:17:34 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 58072203AA for <ietf@ietf.org>; Fri, 9 Jan 2015 14:23:04 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id AB1A1637FE; Fri, 9 Jan 2015 14:17:33 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 91F99637EA for <ietf@ietf.org>; Fri, 9 Jan 2015 14:17:33 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>
Subject: Re: Updating BCP 10 -- NomCom
In-Reply-To: <CAP8yD=uky=fbJNA5KjCSk3q+u036++c+pnR_3inmvnOECxRRKA@mail.gmail.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <CAP8yD=uky=fbJNA5KjCSk3q+u036++c+pnR_3inmvnOECxRRKA@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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 09 Jan 2015 14:17:33 -0500
Message-ID: <12811.1420831053@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Pfl6qE20glXFUEQTuK7pmxpqj0I>
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:17:37 -0000

Allison Mankin <allison.mankin@gmail.com> wrote:
    > 1. Improved transition for Chairs - my thought is to add a Future Chair
    > early so that she or he can observe.  Right now we've been tending
    > mainly to select as Chairs people who were recently Nomcom members.  My

Oh, yes, we almost forgot: we need a turn-over ceremony at the "Second meeting"
(probably should be the Admin plenary), when the new nomcom is now *CLEARLY*
responsible for any open positions.

This is also when the past nomcom-chair and committee members can completely
and irrevocably destroy any private keys and notes they might have kept,
and the secretariat can remove any email aliases that might be around and
might get autocompleted.

I don't know if this needs to go into 7437, but it needs to written down.

    > 2. During my tenure we had to invoke the thoughtful BCP 10 allowance to
    > operate with 9 members rather than 10, because one of our members
    > became permanently unavailable.  We had some risk of losing another
    > late in the game as well, and I think this is always a risk. Therefore
    > I'd like to see the addition of one warm spare, selected during the
    > random draw, who joins meetings, observes, conceivably helps with
    > interviewing, and is available quickly to participate if there is a

We discussed drawing the name, but I didn't know you anticipating them
joining too...  I'm thinking about this.

    > 3. A bit fuzzier, but I think important, would be to include some
...
    > I can propose some text for these.

good.  I think you massively improved this part, and I found it challenging
to live up to the example you set.

-- 
]               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    [