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

Ted Lemon <mellon@fugue.com> Sat, 25 November 2023 21:34 UTC

Return-Path: <mellon@fugue.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 147CFC1519A5 for <eligibility-discuss@ietfa.amsl.com>; Sat, 25 Nov 2023 13:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 GtIJLD_L0jgO for <eligibility-discuss@ietfa.amsl.com>; Sat, 25 Nov 2023 13:34:20 -0800 (PST)
Received: from mail-oo1-xc35.google.com (mail-oo1-xc35.google.com [IPv6:2607:f8b0:4864:20::c35]) (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 58ECAC14CE30 for <eligibility-discuss@ietf.org>; Sat, 25 Nov 2023 13:34:19 -0800 (PST)
Received: by mail-oo1-xc35.google.com with SMTP id 006d021491bc7-58a42c3cbb8so1712298eaf.3 for <eligibility-discuss@ietf.org>; Sat, 25 Nov 2023 13:34:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1700948059; x=1701552859; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=M9Bv6SFrkYFW1ALL6Uhc3Zq53eOQf1QB8tuAG1QJ5Fw=; b=roLLuwUIOczyRjaDYFO9DFFZwjYmOmt4kq+Q9ZgsyWPLnXH4jGWaGR8RW/NYq57xuX Qxh/4ngB4fC4kEAKm94sbn/yaynQwSxndpjXyEzn5erxnGvc9sgrz23nGJqWaA1Nc3wY clP4mS4LAu4d7OwrqcoPi7E6vjn7m4fbtIWS1O66lcg+OoT2LjsZRK7yyrDFnEOlndK6 zH0J8TAq4wcgSKDbU/v2e3Rkv6SmQ8tQrYneZoyrmRlwC3dlMcFa7YZTq/ovJJUhPR5B wQzMoQ+rZcZB7kMtpa3DAqa6ul0JPr6sAp9s+KOZWja5MKFiegz3wwWU0QZhdZnKs5ZI NuGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700948059; x=1701552859; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=M9Bv6SFrkYFW1ALL6Uhc3Zq53eOQf1QB8tuAG1QJ5Fw=; b=nLwOF0bKpiJ6W0UGeD8x461ZTP9W51U5vaQbx6mp6LUX7/KX+S0zQkH7PIZK2dX6JA 840EfLOfQBB8ijIszxwoOUbDDNhH1dw7SIxEmdmZ3cRdaWMRbMUPPQDCvr2L3qdnF/UK KmGeDCMm9XkFgpH6AWPoTRLxz8u5qho12AZqTRd3HMVz1jkXLsf1JYxfKR/3QqHeD9yG S19qobjbj/Qb75rIh5p8Yn+ZY6WjImpUgtcO2MwzIC99NxklwY951uWs2kPG23FP+FVW 9x8xvuzP5kCqpBYJ0RWq1+RDlWhJjSux1EDAXBhrWSAHtQ4FfOul+Ptns0Hi2mscuMjt GqxA==
X-Gm-Message-State: AOJu0YyWFGeb3teC28sW0XG8b8FD1cDYqpVLYh/CAuJvc8ebtfI+nuhy qL3lP7wYTOxX/rJbOLHJzJKON8r2hnESVT1tMVwBbkVZpS3jcTZ4
X-Google-Smtp-Source: AGHT+IEXET3fGET4t39VkNiSe2gC+Mw3q19+KTYBPA2JTNw0yLa9WMoKAL84d2cw99pVWVnV+fK9jpwjFRPoY5MW+PY=
X-Received: by 2002:a05:6358:7e4a:b0:16e:2898:5e02 with SMTP id p10-20020a0563587e4a00b0016e28985e02mr5192619rwm.32.1700948058775; Sat, 25 Nov 2023 13:34:18 -0800 (PST)
MIME-Version: 1.0
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> <25ea1487-d5f6-46e2-9c2e-487291fd55b3@nthpermutation.com> <761E201D-5D19-4F1D-94C4-40E9A011BDE2@akamai.com> <b78b56cc-b37d-4385-b746-be782621dfa1@nthpermutation.com> <00B57B77-CADF-4183-B0A1-84AF1AB5981A@akamai.com> <a37ad0bc-a69c-45c4-b471-088f107ee467@nthpermutation.com> <CAPt1N1ki6ACX70B0MoKDxsF-ncET235E5eUww8Op6rtfrECztQ@mail.gmail.com> <21bf3cfe-afad-48d2-ae9b-82ae4c237941@nthpermutation.com>
In-Reply-To: <21bf3cfe-afad-48d2-ae9b-82ae4c237941@nthpermutation.com>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 25 Nov 2023 16:33:42 -0500
Message-ID: <CAPt1N1kOOXhjDkbW_YwMfTrWsdKScgOT8CSWdMKwmtZmHeZS_w@mail.gmail.com>
To: Michael StJohns <msj@nthpermutation.com>
Cc: "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d331f0060b00d490"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/yxZfpCeJeOmfidScjwro_-FOolw>
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: Sat, 25 Nov 2023 21:34:24 -0000

Why would any demographic standard other than "the whole population" make
sense? I don't think anyone is proposing that we actually succeed, in the
IETF, in achieving parity, but clearly we are so utterly removed from
parity that some extra effort is reasonably called for to at least make
space for there to be a consistent voice for the part of the population
that is currently so far from parity. We make genuine (although I would say
incomplete, since we never go to Africa) efforts for regional parity, so
why not do the same for gender parity?

As for the community thing, my point was just that I really don't want to
speak of IETF participants and potential participants whose gender is not
male as being in a separate community. I think that is the opposite of what
we are trying to achieve. I'm sorry if I implied that this was your goal—I
was just objecting to that particular turn of phrase, which I think leads
in an unfortunate direction. An added challenge is that for people whose
gender is not cis, we definitely don't have a large enough pool to choose
from, which is .. not great .. but as others have observed, this proposal
probably isn't going to work there without getting the IETF population to
parity with the general population, which is still a distant thing on the
horizon that I hope at least some of us consider a goal.

On Sat, Nov 25, 2023 at 2:33 PM Michael StJohns <msj@nthpermutation.com>
wrote:

> Hi Ted - thanks for the thoughtful note.  Comments.
>
> On 11/25/2023 1:11 PM, Ted Lemon wrote:
>
> I feel like the problem that you aren't representing here that I think is
> quite important, Mike, is that most of us live in societies that clearly
> bias in favor of men being in positions that allow them to travel to the
> IETF. And I think we've seen that the IETF is also a fairly unwelcoming
> environment for people who are not willing to handle disrespect by
> responding in kind. (In cast it's not clear, I DO NOT mean you here—I'm
> just saying this about the social structure we dwell in generally).
>
> Agreed. And there are non-societal structural issues we've started to
> address - e.g. provision of child care that should start to help.
>
> (Let me address "non-male community" - Mallory's document uses the term
> gender and that's got a number of 2020era edges and hooks that don't
> exactly match to a simple binary choice between male and female.  "non-male
> community/class/?" was the best I could get to trying to identify the class
> of have-nots in this discussion. Community may have been a bad choice.
> Offense if any was given was not intended.).
>
>
> And women are generally, in our societies, socialized to accept disrespect
> without responding in kind. They are generally seen in a poorer light than
> men if they do respond in kind. They generally experience negative
> consequences most men are not familiar with if they respond in kind.
> Indeed, they also often experience these consequences merely by
> disagreeing, even when they do so politely and constructively.
>
> I believe you're correct that the literature says that.  The question is
> how do we - the IETF - mitigate this characteristic of conditioning?
>
>
>
> As a result of this, it is pretty much inevitable, particularly to the
> extent that we measure IETF participation on the basis of who shows up and
> who talks the most on mailing lists, that women are going to be
> underrepresented in the IETF, and consequently on nomcom.
>
> Underrepresented based on whole population?  Based on equivalent
> populations in the tech world? Based on membership on the mailing lists?
> Based on WG chairs?
>
> Based on whole population, pretty much every tech community  has women
> substantially under-represented.  And mostly not something the IETF can
> directly address.
>
> On a SWAG basis I'd guess women  already in the tech world are only
> moderately under-represented in the IETF.  I don't know the answer for
> mailing lists, and I once did the math for WG chairs and our leadership was
> actually overrepresented based on the proportion of women WG chairs at that
> time.
>
> I started through the volunteer list for the current Nomcom and gave up
> trying to gender the entries by name.  Some are people I know, some I
> guessed based on the organizational/national  association, but after
> Linkedin dinged me for looking up a number of the non-european derived
> names in quick order, I gave up.
>
> What I would like to know is whether the proportion of women volunteers vs
> eligible women is similar to the overall proportion vs eligible.  There
> were 254 volunteers this year - I seem to remember that worked out to be
> about 10% of the eligible pool.
>
>
> For what it's worth, I don't really like the notion of a "non-male
> community." I feel like this draws a line that doesn't exist. Women are
> members of our community: they are just treated differently, and because of
> that fewer of them participate in ways that make them eligible for nomcom.
>
> Attend 3/5 meetings either in person or virtually is all that is needed to
> become eligible.  Do we want people on the Nomcom without that minimum
> requirement?  Mallory's document does not suggest that and I wouldn't
> support it.
>
>
> So the question is not how we address the needs of the "non-male
> community," but how we do a better job of including those members of our
> community who are not currently being fairly and effectively included.
>
> I don't actually know how to do that. I'm not convinced that Mallory's
> proposal is the best approach. However, I don't have a better suggestion,
> and none of the suggestions you've offered feel to me like they are better
> suggestions.
>
> I keep asking the question and no one says more than "it couldn't hurt" -
> does Mallory's proposal fix a problem other than the math occasionally
> omitting a woman from the Nomcom?   Does having a guaranteed member of the
> Nomcom lead to more women being selected to IETF leadership?
>
>
> In an ideal world, I would much rather make the changes that we need to
> make so that we have appropriate proportional representation of women and
> men in our community, which I think is roughly 51-49 based on my limited
> demographic knowledge.
>
> And you would be wrong.  To the extent that googling gives you anything,
> take a look at  https://www.luisazhou.com/blog/women-in-tech-statistics/
> It's roughly 3:1 men to women - so about 25%.
>
> The rest of the document matches my limited understanding of the overall
> tech women problem.
>
> I think the fact that we could implement Mallory's proposal now is
> actually evidence that we've made some progress in that direction. But this
> feels very much like a chicken-and-egg problem. I don't know how to get men
> in our community to be more respectful and welcoming of women. Even if we
> were (and I think the majority of us are!), I don't know what we can do
> about the problem of representation that isn't directly our fault, but is
> simply the emergent property of our societies' biases, over which we have
> very limited agency.
>
> So having said that, it feels to me like what Mallory has proposed is
> something that's actually within our power, and does address a real
> problem. And so maybe until we can identify an approach that we can agree
> is better, this proposal is a reasonable place to start.
>
> And I'm still disagreeing with "address(es) a real problem".    This is an
> artifact of how we do things nothing more.  The problem is actually
> disproportional representation in the leadership if any.
>
>
> Let me suggest a more radical approach that is evidence based and not
> triggered by the math and the volunteer pool or a weak statement of a
> problem:
>
> 1) Resolved: The Nomcom voting membership should reflect the tech industry
> population, not just the IETF's current population.
>
> 2) The selection algorithm for the Nomcom shall select 2 women for the
> first two slots of the Nomcom.   The number of women shall be capped at 3.
> In other words, each Nomcom  will have either 20% or 30% of the voting
> members as women.  Selection for the first two slots shall only be done
> from volunteers who self-identify for inclusion.
>
> 3) The remaining selections for the Nomcom shall be from the entire pool
> of volunteers discarding any that would violate a cap restriction.
>
> 4) If the volunteer pool for women falls below 10% of the pool or below 10
> women, the guarantee drops to 1.  If the pool contains  <= 10 women then in
> addition, the cap drops to 2.
>
> 5) The numbers in section 2 shall be readdressed by the IETF community
> every 8 years and shall be adjusted based on the population of women in
> technology irrespective of the IETF'c current participation to give
> guaranteed proportional representation.
>
> 6) Volunteers must self-identify to qualify for selection under 2.  This
> self-identification is not subject to challenge.
>
>
> I don't actually know if that will effect the output of the Nomcom, but
> hope springs eternal.
>
> Mike
>
>
> On Sat, Nov 25, 2023 at 12:42 PM Michael StJohns <msj@nthpermutation.com>
> wrote:
>
>> I'm going to reset this slightly and offer a heretical comment.
>>
>> The lack of a particular community participating on a given nomcom is NOT
>> a problem, well-known or otherwise.  It's one fact from a fair random
>> selection.
>>
>> Instead, "The Nomcom candidate selections under-represent a given
>> community over many Nomcoms."  would be a problem if the statistics showed
>> that.  Is that the actual problem we should be addressing?
>>
>> Is the following a more accurate statement of the perceived problem?
>>
>> If Mallory's document said "We have this problem of under-representation
>> in the IETF leadership.  Under-representation in the proposed candidates is
>> measurably increased in the years where the voting members of the Nomcom do
>> not include a member from that community and here's the statistics to show
>> that case.  If we imposed a requirement to require at least one of those
>> community members on each Nomcom statistics show this would help to resolve
>> the under-representation of that community within the output selections."
>> I would probably be more accepting of Mallory's proposed solution in that
>> case.
>>
>> Unfortunately the current document doesn't say that, and I can't actually
>> figure out what the problem being addressed actually is.  It can't be that
>> losing a lottery is the actual problem.
>>
>> I might still argue against the simplistic approach proposed to solving
>> the under-representation problem.  I would suggest that instead the
>> liaison/advisor approach coupled with greater oversight by the confirming
>> bodies and a willingness by them to require the Nomcom to reconsider
>> selections as a means of achieving appropriate levels of representation
>> might address an under-representation problem.
>>
>> We address the input conditions to affect the output conditions.  If
>> adjusting the input condition results in no difference to the output
>> conditions, why are we twiddling?  If adjusting the input conditions does
>> affect the output - show me the math.
>>
>> A few other questions before I end - related to the proposal on the table
>> and that will need to be addressed without hand waving:
>>
>> 1) Does the mandatory requirement apply if the volunteer pool
>> participation for a community falls below 10%?  5%?  3%?  Or goes above
>> 20%? 30%?
>>
>> 2) What is the criteria for selecting other communities for similar
>> treatment?
>>
>> 3) Are claims of community membership subject to challenge (similar to
>> claims of organizational association)?
>>
>> 4) What happens if the sole selected community member needs to be
>> replaced?  Consider both the before the Nomcom convenes and after?
>>
>> 5) Is there a sunset clause?  If so, how is it triggered?  If not, why
>> not?
>>
>> Lastly - the more general algorithm that would probably work without
>> collapse is to select the special community members at the beginning of the
>> process applying all of the rest of the rules for the remaining batch of
>> selections.
>>
>> And to capture the possibilities:
>>
>> Possible changes to the Nomcom process (zero or more of these):
>>
>> 1) Impose a requirement to select at least one member from the non-male
>> community to serve on the Nomcom.
>>
>> 1a) .... at least 2 members...  [[generally to address a past issue which
>> has resulted in knock on present issues, you over represent the affected
>> community for a period of time]]
>>
>> 2) Increase the number of voting members from 10 to 15 or 16.  At 16,
>> with 10% of the pool, a community has a 4 in 5 chance of at least 1 member,
>> a 1 in 2 chance of at least 2.
>>
>> 3) Provide a non-male liaison/advisor either for every Nomcom or for any
>> Nomcom without a non-male voting member.
>>
>> 4) Have a mandatory 1/2 briefing for the Nomcom on diversity issues prior
>> to their first deliberation?
>>
>> Later, Mike
>>
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>
>