Re: Updating BCP 10 -- NomCom

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 12 February 2015 00:46 UTC

Return-Path: <superuser@gmail.com>
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 8176D1A1AEC for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 16:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 57ZryEO7j0Kx for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 16:46:47 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (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 6EB511A1A65 for <ietf@ietf.org>; Wed, 11 Feb 2015 16:46:47 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so559649wid.5 for <ietf@ietf.org>; Wed, 11 Feb 2015 16:46:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gdOFtKBHdYpAkkxs5pX6KCVYZskjHZVq7jykPXOUTYE=; b=A+xpSsbyjslexJZ+Nij/spRqcauWxTwl8o4LmZDM5Bx+qep8G+RZ1ouSKqCJnbyukR 4BX9a5ATgAFqDqJ1CIpyy+gFhrNaGui0a9NVT3PU3/XltS1YSGwHbS65Bi/5Nc+S5fPt UvS8ltWd24XMa82V1vW2tThcuWFbo59fliXci3Dp3UqsyK4avyGnQp+mTd1X+C7HMXB5 Lj7+BBlxrg5Ne/vrl5cj5VuxPR1ABC0F5mx7a11lWsVU5Rp5gU71FOBbLKdELFlTmlR2 xz8bFVnaRvqDNf1Q7Yjh3X37L8VEnmVy4c/9Svae9KAh6IB8ZwBHvkHXzfEX/qFeQfqf /FWw==
MIME-Version: 1.0
X-Received: by 10.194.185.197 with SMTP id fe5mr2126592wjc.135.1423702006168; Wed, 11 Feb 2015 16:46:46 -0800 (PST)
Received: by 10.27.179.146 with HTTP; Wed, 11 Feb 2015 16:46:46 -0800 (PST)
In-Reply-To: <54dbbf33.066b8c0a.72fd.ffff84d7SMTPIN_ADDED_MISSING@mx.google.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <CAP8yD=uky=fbJNA5KjCSk3q+u036++c+pnR_3inmvnOECxRRKA@mail.gmail.com> <CAL0qLwYsSXBYjrQ54M9VFHdp1htrjbLX-ZQjzZ78WeLzPjzZXQ@mail.gmail.com> <CAP8yD=v1djPpXhQ-+=esxRKVpuzUcs57S5e4auChdjdMfHP7vw@mail.gmail.com> <54dbbf33.066b8c0a.72fd.ffff84d7SMTPIN_ADDED_MISSING@mx.google.com>
Date: Wed, 11 Feb 2015 16:46:46 -0800
Message-ID: <CAL0qLwaJN1iAUKgCWAR4cw0ttNk6pP33=odYYM3oniJ3M8T=Bg@mail.gmail.com>
Subject: Re: Updating BCP 10 -- NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: multipart/alternative; boundary=047d7bdc8f9e5800ac050ed974ce
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aUocGOdJNrReJzATpU3335X5b3s>
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: Thu, 12 Feb 2015 00:46:50 -0000

On Wed, Feb 11, 2015 at 12:45 PM, Michael StJohns <mstjohns@comcast.net>
wrote:

>  A couple of things.
>
> The nomcom is not either individually nor collectively the "hiring
> manager" for the IETF.  It neither makes the final decision (that's the
> CB's call), nor does it direct the work of the "hired" entity.
>
> The Nomcom is and always has been a "search committee" and as such it
> gathers and winnows candidates before proposing them for confirmation.
> Indeed, there is no bar to the Nomcom proposing multiple candidates for a
> position and allowing the CB to choose its preference - that hasn't
> actually been done, but its not barred.
>

I think that's a fair point.  I've adjusted her suggested text accordingly.


> The interview should be used to fill in details not clear from the
> questionnaire, so matters of fairness should be addressed when crafting the
> questions, not later when you get around to talking with the candidate.
> Generally, the interview should be used to evaluate the BS factor of the
> answers from the questionnaire and not delve into new fields or hobby
> horses of the interviewers.
>

The questionnaire is actually not codified in BCP 10 anywhere.  Does anyone
think it needs to be?


> The digression to "thinking slow" is interesting, but somewhat trendy.
> Next year there will be another interview and decision method that will be
> trendy and its unclear why this "thinking slow" would be a better choice
> than next year's flavor and why it should be immortalized in the next
> version of 3777.  I would instead focus on the virtues of clarity,
> completeness and fairness and leave the rest of it to the best abilities of
> the chosen Nomcom.  In any event, attempting to "program" the Nomcom
> members to a specific behavior pattern will be unsuccessful.
>

I tend to agree with this, though since we do have an appendix that talks
about "oral tradition", there's probably little harm in including this
stuff in a similar appendix.  We could even label it clearly as something
that worked well for NomCom 2013.


> Allison - your desire to have 3+ interviewers per interviewee is going to
> contribute to slowing down the process even more.  At this point I see us
> starting to try and begin the process a full two years before confirmation.
> (Yup - hyperbole, but seriously, we're spending WAY too much calendar time
> from first indication of candidacy to selection).
>

I also disagree with this.  I served on NomComs 2013 and 2014, we did it
this way, and it worked rather well.

-MSK