Re: [Eligibility-discuss] Suggestions for nomcom chair selection?
Michael Richardson <mcr+ietf@sandelman.ca> Fri, 14 August 2020 23:10 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6E33A0745 for <eligibility-discuss@ietfa.amsl.com>; Fri, 14 Aug 2020 16:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 MxCRQI4RZf8I for <eligibility-discuss@ietfa.amsl.com>; Fri, 14 Aug 2020 16:10:31 -0700 (PDT)
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 8B6E73A0766 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 16:10:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 80205389BA for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 18:49:41 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3cucpRwy3fL9 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 18:49:40 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9875E389B8 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 18:49:40 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 207C6591 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 19:10:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: eligibility-discuss@ietf.org
In-Reply-To: <20200814192145.iiuoma7a3frf7mm7@crankycanuck.ca>
References: <20200814192145.iiuoma7a3frf7mm7@crankycanuck.ca>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
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-sha512"; protocol="application/pgp-signature"
Date: Fri, 14 Aug 2020 19:10:28 -0400
Message-ID: <9357.1597446628@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/bBSanvyQRfh7QpvQcTXvbZwZTRY>
Subject: Re: [Eligibility-discuss] Suggestions for nomcom chair selection?
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2020 23:10:34 -0000
Andrew Sullivan <ajs@anvilwalrusden.com> wrote: > I'm the President and CEO of the Internet Society (ISOC), and I'm > writing with that hat on; but this account is where my IETF mail > subscriptions generally are so it's more convenient to use this > address. > One of the things that I have been reflecting on in the discussions > about nomcom eligibility is that it would also affect the pool for > nomcom chair availability. As you probably know, I'm responsible to > appoint the nomcom from year to year as part of my job. When I am > replaced, that person will take over the responsibility. Appointing nomcom chair is I think, a rather difficult job. Expanding the pool would not really change who would be willing to chair in my opinion. Allison and I tried to change the process slightly so that nomcom chairs were appointed in mid-October the year before in order that they could be invited to sit through the November nomcom process as "nomcom-chair-elect". While many nomcom chairs have previously been nomcom selecting members, even if they have things change, and providing a smoother introduction/training is important. There was various amounts of push back, one of which was to point out that this makes the nomcom chair 2.5 years, rather than 2. This is a bit inaccurate as the nomcom-past-chair duties are essentially over by January, and I also think it would spread the information transfer from nomcom chair N to nomcom chair N+1 over twice as many months. How can we make the nomcom chair role more rewarding? > but I'm also aware that my familiarity with the IETF community is > decreasing over time. Yes, but started with a connection to the IETF community that was perhaps two orders of magnitude stronger than some ISOC presidents. > The trouble I have is that I don't really know where to start except > with the approaches I have, which are mostly informal and depend upon > the social-professional networks I have as well as those of others. > That seems like a poor foundation on which to build, so I thought I'd > ask to see whether people here have other suggestions for a starting > point. The set of previous nomcom chairs started to meet a few times about various things. I think Montreal (105) was the last time. I think that this group of people is a good place to start this discussion. Perhaps making this group slightly more formal in some way. If we started from scratch, I think that the appointment of the nomcom chair would have been assigned to the LLC. Should the LLC be more involved? As Andrew Malis said, people are always worried about process/regulatory capture. But, one has to acknowledge that you can't appoint strangers to do this job. While the group of WG chairs is a good place to include, it is also the place in which the overwhelming majority of AD candidates are going to be taken. I imagine you have already collected the list of all the previous nomcom voting volunteers already. I'd have them in a file with some notes and I'd keep coming back to them a dozen or so a quarter. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Eligibility-discuss] Suggestions for nomcom chai… Andrew Sullivan
- Re: [Eligibility-discuss] Suggestions for nomcom … Andrew G. Malis
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael Richardson
- Re: [Eligibility-discuss] Suggestions for nomcom … Brian E Carpenter
- Re: [Eligibility-discuss] Suggestions for nomcom … Adrian Farrel
- Re: [Eligibility-discuss] Suggestions for nomcom … Spencer Dawkins at IETF
- Re: [Eligibility-discuss] Suggestions for nomcom … 'Andrew Sullivan'
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael Richardson
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael StJohns
- Re: [Eligibility-discuss] Suggestions for nomcom … Brian E Carpenter
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael Richardson
- Re: [Eligibility-discuss] Suggestions for nomcom … Andrew Sullivan
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael StJohns
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael Richardson
- Re: [Eligibility-discuss] Suggestions for nomcom … STARK, BARBARA H
- Re: [Eligibility-discuss] Suggestions for nomcom … Michael Richardson
- Re: [Eligibility-discuss] Suggestions for nomcom … Mirja Kuehlewind
- Re: [Eligibility-discuss] Suggestions for nomcom … Victor Kuarsingh