Re: [Eligibility-discuss] on re-using nomcom chairs (was Re: Draft meeting minutes)

Michael StJohns <msj@nthpermutation.com> Wed, 30 October 2019 16:13 UTC

Return-Path: <msj@nthpermutation.com>
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 B47A21208AD for <eligibility-discuss@ietfa.amsl.com>; Wed, 30 Oct 2019 09:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.com
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 99_ogmSdpe3e for <eligibility-discuss@ietfa.amsl.com>; Wed, 30 Oct 2019 09:13:39 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37F7C120A59 for <eligibility-discuss@ietf.org>; Wed, 30 Oct 2019 09:13:39 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id u184so3316737qkd.4 for <eligibility-discuss@ietf.org>; Wed, 30 Oct 2019 09:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=0062z7dUt73Rdq01EmMtyWVtJWA/vJTaTkxBhD2Nkgs=; b=FPrQWSAn5q/I/EqPs701nZ46qvMK3bQM2UmZ0VzkldQtZoLFIu9hLJ1/DER053omyJ Zv1Z2WL1YyHisJUPlZXFrYrp+/pBEbKX8kAy2jEQP+GnRfmuBLOdi5389lueDDJO6l53 sJ3XHYEdXOhmazq/v5IKLIRTAN8jTtwFdBwPK+URnUKUVkREX/xCC4tiz0fX7BSqfsAp osmcdMj8qWfOQEcY1+q4qnphe14XEuRSO66gSSVe+eRWS0BQyODcINFfaKljxnALds3M opwNsEBLOKRBBbOA73U69C5k7/+8wK3nnvpgzDwVPGTjF7cppUOhy/F5rj8zanEgZudA OptQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=0062z7dUt73Rdq01EmMtyWVtJWA/vJTaTkxBhD2Nkgs=; b=naFYN2BJeBPpHyxJQF4xp0+r5iNsIQrnbe8fV+/NWlJvgeL4qmZdVnttX6S31etqbZ m2LGW7CjYQn4Df1yl/WBYscAo9RRJV53qofue9Y74tR6pEbuDMiZ8nPQdMoAK1nkn1OZ 00TgPzLn19y9PRy8hG85ViTX0j4gz2GsrgI8bB3z+/CErVb1tVJ7NENDgG7XfesBaukK iMn6qbYvdbnXGC980KUEOIHUej9vF02n98i2RdLQoCbZ8AoyTbRSNnA00mO8TBxh4kfX /0YGpq0ZFH3pIxhGOSDUCDn4A+F9qd0cwMPUbQH65Xyg0XiUgmbgiseJiPPK6Y3/t++y PaYg==
X-Gm-Message-State: APjAAAXaZ4f6q9dMGenHJjcD8+ZmmMkeMMMIQ9ClUNjeu0H4YQHCp2us 1d5V1KQJjcDldxjTWXRZYvja9WFTdKo=
X-Google-Smtp-Source: APXvYqwQEKOjHWLLl2ALcrtd1wyFJ47oPjV1jCC+vMMNBBNkUUNTPGhp7jcnXkTU04BSbJXHWdwtTg==
X-Received: by 2002:a05:620a:1498:: with SMTP id w24mr745769qkj.170.1572452017830; Wed, 30 Oct 2019 09:13:37 -0700 (PDT)
Received: from ?IPv6:2601:152:4400:437c:50c5:49d:49d9:fd2c? ([2601:152:4400:437c:50c5:49d:49d9:fd2c]) by smtp.gmail.com with ESMTPSA id a28sm237242qkn.126.2019.10.30.09.13.37 for <eligibility-discuss@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Oct 2019 09:13:37 -0700 (PDT)
To: eligibility-discuss@ietf.org
References: <99234A93-2224-47F1-AA65-C71DC5DA3CD3@episteme.net> <f20ef671-1e13-5dc7-4e7e-06eb40d77796@gmail.com> <ad44164b-db3a-88c2-6222-c9954e8bd4b9@nthpermutation.com> <20191030114452.ngy5jlp75gptqrjp@mx4.yitter.info>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <b59e16d3-4abf-8225-ffa3-14aa1030ae47@nthpermutation.com>
Date: Wed, 30 Oct 2019 12:13:36 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191030114452.ngy5jlp75gptqrjp@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/hNs5Akntf7m78f_n5ygJzDkAKbk>
Subject: Re: [Eligibility-discuss] on re-using nomcom chairs (was Re: Draft meeting minutes)
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: Wed, 30 Oct 2019 16:13:43 -0000

Hi Andrew - comments below.

On 10/30/2019 7:44 AM, Andrew Sullivan wrote:
> Hi,
>
> Speaking with my ISOC President hat on:
>
> On Tue, Oct 29, 2019 at 04:16:29PM -0400, Michael StJohns wrote:
>   
>> How about the last three Nomcom chairs that didn't serve on a Nomcom
>> committee or with the petition target on one of the I* bodies or as a
>> co-worker?   2/3 vote to void the petition?
> I would like to remind people that I already have quite a difficult
> job finding a well-qualified, non-disqualified, willing and able
> nomcom chair.  And I start with the advantage of knowing some part of
> the community (knowledge that inevitably will grow stale over time, of
> course); not everyone who will ever be appointed to my job will start
> with such an advantage.  If people take a decision that starts to add
> more possible time commitments to nomcom chairs, finding good chairs
> will get harder.  If serving as nomcom chair signs you up to a
> possible responsibility for an undefined number of years (as the above
> formula would, because of the interactions with who you didn't appoint
> and work with and and so on), you might be reluctant to take on such a
> job.  It's already a two year commitment.

All good points, but missing a few others:

1) The workload for a recall committee is ... maybe one week.

2) The chance of a former chair being called back is ... minimal.  If 
it's not minimal, the Nomcom process is sorely broken.

3) Any given chair can refuse the call when it comes.

4) Unlike the selection of the Nomcom chair, the selection of the recall 
chair, in the worst circumstances, could be perceived as being selected 
to achieve a specific result in the recall. Avoiding that perception by 
making the selection of the recall chair in a manner (e.g. mechanically, 
through a previously agreed approach) that eliminates that possibility 
seems to me to be a good result.

5) And as you noted in a previous message, it's a pain and 
time-consuming to find and recruit the right person.  It also puts the 
ISOC President squarely in the critical path of the current recall 
process.  ISTM that eliminating the time (clock time which causes a 
delay in resolution and the ISOC President's time which impacts their 
other duties) to run that process is a *good thing* (TM).

6) TANSTAAFL - we're either going to pay a little over time (by keeping 
the Nomcom chair's in pocket for a possible recall) or pay a lot all at 
once, perhaps when we can least afford the time or effort.  Personally, 
I'd really do the former.

7) At least a few times over the past 10-15 years  various groups of 
past chairs have gotten together to discuss the Nomcom process.  I 
remain invested in it even after 20 years or so.  If you reach out to 
the group and find more than a few who said "no way in hell" I'd be 
surprised.

Mike


ps -

As you note, the ISOC president isn't guaranteed to have your level of 
knowledge.  Perhaps it's time for the IETF to reconsider who selects the 
Nomcom chair (and how that process might work if it's not the ISOC 
president).  The current scheme has been in place for quite a long while 
- it's probably worth a look.   I mention this as an aside to this 
thread mainly because of your comments above, rather than something to 
add to the current discussion.   Poised/poisson topic I think if we head 
that way. /msj/


>
> Best regards,
>
> A
>