Re: NomCom procedures revision

Harald Alvestrand <harald@alvestrand.no> Fri, 28 August 2015 11:13 UTC

Return-Path: <harald@alvestrand.no>
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 893C41AD2D9 for <ietf@ietfa.amsl.com>; Fri, 28 Aug 2015 04:13:51 -0700 (PDT)
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, 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 L5GY6RqF1_xt for <ietf@ietfa.amsl.com>; Fri, 28 Aug 2015 04:13:49 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9A91AD0D3 for <ietf@ietf.org>; Fri, 28 Aug 2015 04:13:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id CE3577C3D95; Fri, 28 Aug 2015 13:13:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLI1o6JC6WRz; Fri, 28 Aug 2015 13:13:46 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:1d33:2b7c:f822:f35c] (unknown [IPv6:2001:470:de0a:27:1d33:2b7c:f822:f35c]) by mork.alvestrand.no (Postfix) with ESMTPSA id 7D9DB7C3D2C; Fri, 28 Aug 2015 13:13:46 +0200 (CEST)
Message-ID: <55E0426A.3000800@alvestrand.no>
Date: Fri, 28 Aug 2015 13:13:46 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: NomCom procedures revision
References: <CAL0qLwYJzFZT=OgWqiiTw-n6mvb3PPusRtArmPs_d4_qpLfmpg@mail.gmail.com> <CADnDZ8_KsNP=_nwp2wrckXtHF8ZSxrQTvf9UKbAMpt68BiiCFA@mail.gmail.com> <CAL0qLwbhhqG1qoHbBrymPQrU31qjswPAhdeJBqVdRj2L4AR80A@mail.gmail.com>
In-Reply-To: <CAL0qLwbhhqG1qoHbBrymPQrU31qjswPAhdeJBqVdRj2L4AR80A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/kumYbxHyz0wuce4jEtpctVbGt9Y>
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Aug 2015 11:13:51 -0000

Den 27. aug. 2015 19:54, skrev Murray S. Kucherawy:
> Have a look at Appendix F. I plan to fill out Section 10 once we know
> for sure which changes have consensus rather than a few points that
> might still be fluid.

Some notes (this is NOT a detailed review):

Having just gone through the exercise of establishing a voting mechanism
for my nomcom, I think the following needs to go:

5.5.  Voting Mechanism

   The Chair must establish a voting mechanism.  The mechanism by which
   this is accomplished is left to the discretion of the Chair, but must
   be accepted by at least 75% of the selecting volunteers before the
   work of the committee can begin.  Once established, this procedure
   cannot be altered until the current nominating committee is
   dissolved.

A) It turns out that voting mechanisms are *tricky* beasts. The idea
that a nomcom will make them 100% right on the first try is a Bad Idea.


I suggest changing this to "Once established, the minimum threshold for
changing the procedure is 75% of the selecting volunteers".

Note: The 75% acceptance criterion is new. 75% of the selecting
volunteers is 8 people. That means that 3 people can a) block the
acceptance of any procedure and b) (with my suggested change) prevent
any change to the procedure. We should make sure that's what we want.

B) A strict interpretation of "before the work can begin" would have the
members accept the voting mechanism before they start discussing the
voting mechanism. I don't think that is a good idea.)

I suggest "before the first vote on candidates is taken" (which is very
late, but at least it's an explicit point in time).

Also, is it an obvious consensus that the chair and the liaisons should
have no input into the decision to accept the voting mechanism?


5.6.  Voting Quorum

   At least a quorum of committee members must participate in a vote.

   Only selecting volunteers vote on a candidate selection.  For a
   candidate selection vote, a quorum is comprised of at least two
   thirds of the selecting volunteers.

   At all other times, a quorum is present if at least 75% of the
   nominating committee members are participating.

It is not at all clear what a "quorum" does. In our procedures work, we
found that separating out the idea of "meeting quorum" from "voting
quorum" made a lot of sense, espcially since we chose to do secret
ballots only - which means we can't do it in a meeting anyway, and there
was actually no requirement for the members of the quorum to be present
at the same time.

It also seemed unusual to have a meeting quorum without either the chair
or the prior year's chair; we put that into the procedures too.

Note that 4.15, 5.7 and 7.1 still uses "voting member" where it should
have "selecting member".

Apologies if this reiterates previous discussions; I must admit that I
seem to have skipped those debates when they happened.

Harald