Re: [Eligibility-discuss] [Gendispatch] New Version Notification for draft-knodel-nomcom-gender-representation-00.txt

Michael StJohns <msj@nthpermutation.com> Thu, 23 November 2023 17:58 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 63E75C14CE31 for <eligibility-discuss@ietfa.amsl.com>; Thu, 23 Nov 2023 09:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yg69uNcG74Q for <eligibility-discuss@ietfa.amsl.com>; Thu, 23 Nov 2023 09:58:27 -0800 (PST)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADC2C14CE30 for <eligibility-discuss@ietf.org>; Thu, 23 Nov 2023 09:58:27 -0800 (PST)
Received: by mail-qv1-xf34.google.com with SMTP id 6a1803df08f44-67a00f24ceeso5824296d6.3 for <eligibility-discuss@ietf.org>; Thu, 23 Nov 2023 09:58:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1700762306; x=1701367106; darn=ietf.org; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=zFrt3k/Svnb79xoGPELoDv65zFdzgVQgW9s2PiLIHsY=; b=TYeCQNui/g1xj85FC1gsQl3V48tiWnRpm4FPkqzKVkHqU/633qF+MX+g/LWERs9KYg tNd7vdH8l/nM2xJJl2tlFKM2XtvbKq7RFRUttk9D9yIlkEKqTB8Txtun25XRbcnRVi/o gSXZKeG0A1/hCRK7/EcTeG3mhd7HWHnk6OJuv5nMIuUxfP1Z/EfzlnEzpq4aMGv/sYlM cY1Bc2kRroiHoDMYaVxHWZ3tCNwpmV6jSpyrf818UZZugSQ9laFJzMYLrhOFSOfBbeHI F78/+1imcKrhx21mTOixqRnfPMaZk4+M8xoivFuQA9kptZJiaL2RtOtAw6DRFs/9hxap 3ygQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700762306; x=1701367106; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=zFrt3k/Svnb79xoGPELoDv65zFdzgVQgW9s2PiLIHsY=; b=F1pl1X53/0T624obF18A80Q1y9Q0ESn6kRWj4PLarvTMEUtg9QYOAd/3dLGdwkwGLM xfUtP8MWgbFJ6GHbsgZNL+c+kf6CmA2QB1/vcF9mDyMsdud0Dy+1hDA5WA4GOvzznjTj o0TfJ+boVZ7jrh5mjlNhoH6lSQiN4oznQZ50TNTE/vYscTc39wGbMyyNY3GxlzUxli+s j3COJ05NRAvYOd0oPqwkSCwQX25Ts7OpPVWLRP/xxh8K1eWW5jMzGZv7gBkDgwxK5199 j0fD9t+cK/T5qrskngLbqkNjXtf3oDGEehK1V8TJYZgV2OMy71ufsOG33uSAAyg98ziu BO3Q==
X-Gm-Message-State: AOJu0YzTImrLk97nAohEA3DkeWwG3oS2rZdeVC8ERoLPIUx59lHzjMQI o8/szkrV9gQgY8Do4Jn9foQWdWXi0H3hL4PHHRc=
X-Google-Smtp-Source: AGHT+IEVCs8LULtLDxR6dQRazlgfCiWvyEZPSiUbIyRQXUS41/MSQPtbQXXuvUwziBFDzAgJ28oqUg==
X-Received: by 2002:a0c:ea82:0:b0:670:85e1:3902 with SMTP id d2-20020a0cea82000000b0067085e13902mr183129qvp.57.1700762306290; Thu, 23 Nov 2023 09:58:26 -0800 (PST)
Received: from [192.168.1.23] (pool-108-31-156-76.washdc.fios.verizon.net. [108.31.156.76]) by smtp.gmail.com with ESMTPSA id rv19-20020a05620a689300b0077d5c39dfcesm613427qkn.58.2023.11.23.09.58.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 23 Nov 2023 09:58:25 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------98O9fOgf1OkCgPUJowqlBmj0"
Message-ID: <25ea1487-d5f6-46e2-9c2e-487291fd55b3@nthpermutation.com>
Date: Thu, 23 Nov 2023 12:58:23 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Eric Rescorla <ekr@rtfm.com>
Cc: eligibility-discuss@ietf.org
References: <f871d358-8d9d-4714-99a8-6a51198a61c9@cdt.org> <5282ED25-E538-493A-A7B5-DA34CD0460ED@yahoo.com> <CALaySJ+4206AH0BoTvsLkn4LYw-TcdBFJSc0vCK6BR58QH=zfA@mail.gmail.com> <39411eb3-7947-49bf-9406-089f43ada331@nthpermutation.com> <CABcZeBN=_Lg2Hd=4QdB6c-_RN8f8b2f3So_AWAuwZGafs_Mocg@mail.gmail.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <CABcZeBN=_Lg2Hd=4QdB6c-_RN8f8b2f3So_AWAuwZGafs_Mocg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/6drhIXgQ41ymxMG0cJZrW24NzWE>
Subject: Re: [Eligibility-discuss] [Gendispatch] New Version Notification for draft-knodel-nomcom-gender-representation-00.txt
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <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: Thu, 23 Nov 2023 17:58:28 -0000

On 11/23/2023 12:18 PM, Eric Rescorla wrote:
>
>
> On Wed, Nov 22, 2023 at 10:45 PM Michael StJohns 
> <msj@nthpermutation.com> wrote:
>
>
>     We pick randomly, and with the exception of the 2 person per org
>     limit,
>     any volunteer has an equal weight in being selected.  If you believe
>     some group is underrepresented in the pool, the solutions is to
>     recruit
>     members of that group to volunteer.
>
>
> There are two distinct issues:
>
> 1. Whether women are sufficiently represented in the nomcom selection 
> pool.
> 2. Whether women are sufficiently represented in a given nomcom.
>
> As Christian (and I earlier) noted, because the nomcom itself is quite 
> small,
> it is possible for women to be very underrepresented in a given nomcom
> with respect to the underlying pool. You may believe that's not an issue,
> but to the extent to which it is an issue, I don't think "try to get 
> more women
> into the pool" is a plausible response to that issue.
>
> -Ekr
>
Hi Ekr -

To the extent not having a POV from a specific community is a problem, 
the chair of the Nomcom has a tool to resolve that - the appointment of 
a non-voting liaison or advisor.  Yes, this person will not get a vote, 
but as they participate in the discussions - including those for 
candidates - they can bring their concerns to the attention of the 
voting members.  As can the ex officio members  of the nomcom who are 
also members of that community.

Reserving a spot on the Nomcom for a member of a given community seems 
fraught.  What's next?  Reserving a slot for the south American 
participants?  The Antarctica participants?  North American?   Left 
handed?  Wine drinkers? Beer Drinkers? Etc.  I would put that general 
tool of mandatory selection from a community in the category of non-useful.

    Digression on left handed people: "Brain scans indicate that
    left-handed people think differently from right-handed people. They
    tend to activate the right half of their brain more for certain
    tasks and functions."

On the question of the size of the Nomcom - we've been at 10 since the 
start.  We've mostly doubled the work load.  It may be time to increase 
the size to say 15 or 16.   This would allow for more opportunities to 
serve, for the math to select more people of any given community or 
grouping, and would reduce the impact of the organizations that can 
populate larger portions of the volunteer pool and are almost guaranteed 
to serve.

It's possible for any community to be underrepresented (or for that 
matter overrepresented) in any Nomcom - that's just how random selection 
works.    If you want to avoid that, probabilisticly,  you add members 
of that community to the source pool.  You might still end up with no 
members from the group, but over time it will balance out.

  Other organizations use a different method for selecting their 
leadership, and some have designated people per community (e.g. the IETF 
sends nomcom members to ISOC for example).

So a big no on this document and this approach from me based on the 
existing tools and the fact that the naive algorithm proposed would have 
some interesting side effects.

If we did reserve a slot and we got to the end with 10 non-community 
members, I'd go back and randomly select from the entirety of the 
community member volunteers.  If the selected one was also a member of 
one of the max-2 orgs I'd randomly replace one of the two members with 
that person.  If not, I'd pick 1-10 and replace that member even if it 
reduced one of the max-2 orgs. This is not a simple algorithm, but is 
less unfair (probability wise) than the one proposed.

Later, Mike