Re: How to get diversity of nominees was Re: Diversity of candidates was Re: NomCom 2020 Announcement of Selections

tom petch <daedulus@btconnect.com> Wed, 27 January 2021 09:48 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 829C03A0C58 for <ietf@ietfa.amsl.com>; Wed, 27 Jan 2021 01:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 W1VXgHlijpbH for <ietf@ietfa.amsl.com>; Wed, 27 Jan 2021 01:48:05 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2127.outbound.protection.outlook.com [40.107.20.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B2C63A0C44 for <ietf@ietf.org>; Wed, 27 Jan 2021 01:48:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C3kSRACyKBu7ZrdhKfucC0lCs59Wxv0pkZ3M7YOjWatcJIzTbz2/cXxKnJkPh4Mfzldi2YnapfbrYNikqSVgceFNpnI5Wh0ccB4lnrZNnf2NHKWuIoldAqUlasss2Axe5RxhulQ+QFMd30/Jg4rKfNCOo0CtfdJWQQCV0Va5jwneBTy7Ue5geqhMZN2n0ebBQs3SH3aqFvFZyl3+iGRXYN3jTcanapcRv034KHNzXeeP0PWfuICSPcj4lEEJDiN8uufj6YbHzViJOaBibFRUvaU5bxdU7yZK/vN2uD7qPBn/l8xaAAWkflgT68r0n9ry+e3ToNdzdxdxxS9FZbkqeA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aDM9dAyekOrqiglEMYk0sNNnP4hmy0rWwGqdJKivgrU=; b=YkCGIVudDWEjZ/IJbQYdL/sndxlPWyUvFtInEVmnaINbIW9PLkxq/U6u3qCjZ1yCzSG5xfpC9/S38Kspf/nZuwm0ykTu0IP4a5Usxw9helkX0XW2RZwjuYaThS1mAqYxVVWoJFBL5n05QVAlxYW6uKNmPkn73OWA+8YCsXwv8Xr6C7jPQNReO7fyG8MI8M4pNVOmqvOqyPBRnO946gI2xnuI6zy04ZxMG3c5On6t4MWSYj/CEb8N5PVrrD6THUFLK0XkRk0v7cRyiDRx48wZxLuszVRrDUI+VEy1LWDJ3cooUHaCsBRvxbfYEpFKRSONgoYpaNrvA0JT8wOr+jwL/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aDM9dAyekOrqiglEMYk0sNNnP4hmy0rWwGqdJKivgrU=; b=itMuJ2b5x6O/rVWlD4GGaW1SLnkZn6wLkhy4GGt2DCO/Np9+LYMG2fx5KdoC25oaTz7HyyV8zSTAU4wY1+nyWwqUCGzFc2okPEvmcjbWA6Pn4qQYS2swcKITU/zeq68GC6x3+VcV1u2/hQvr6JNewLbGD/Vi4O99+nQVVMVrysw=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from (2603:10a6:800:18b::8) by VI1PR07MB4814.eurprd07.prod.outlook.com (2603:10a6:803:a1::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.6; Wed, 27 Jan 2021 09:48:02 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::181c:709a:6f7a:b811]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::181c:709a:6f7a:b811%4]) with mapi id 15.20.3805.017; Wed, 27 Jan 2021 09:48:02 +0000
Subject: Re: How to get diversity of nominees was Re: Diversity of candidates was Re: NomCom 2020 Announcement of Selections
To: Fred Baker <fredbaker.ietf@gmail.com>, "STARK, BARBARA H" <bs7652@att.com>
References: <DM6PR02MB69249C1C01C2D89BE57184D1C3BC9@DM6PR02MB6924.namprd02.prod.outlook.com> <CAC37826-1189-4A53-9B6E-8B4911E925F5@gmail.com>
Cc: ietf@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <601136CF.6010600@btconnect.com>
Date: Wed, 27 Jan 2021 09:47:59 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <CAC37826-1189-4A53-9B6E-8B4911E925F5@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P265CA0191.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::35) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO2P265CA0191.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3805.16 via Frontend Transport; Wed, 27 Jan 2021 09:48:01 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5480be52-e29d-43d7-e318-08d8c2a8a32d
X-MS-TrafficTypeDiagnostic: VI1PR07MB4814:
X-Microsoft-Antispam-PRVS: <VI1PR07MB48145DCA605231AF944B604EC6BB0@VI1PR07MB4814.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:3826;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: Hrh1/O5Coc+7J6laFkkAAuxeOO5a2LG5/tjI1vz6dpRg44tHjmyvEIpuemgwPbVg+PoNOZBaROGzDyle38E+kq2n20DmQEmkXI0QouMSPlrWn55+kc8h142UhQ5MkRrOvZiV6yHlu/3I3l+k64AR8/sHdjt4rqCokoa5TT/+roqkm+9SzCExEzte0ICXET24TgxLyXM9XV6aTgHC0P0bCldjOs4PC43UtA7/BqsOkcoDX/I2sWII4x/mDCJxDd2kvZojuXzYdX3q+JdPyJbEb8f4EplhUu5tYw7T3OUmwvDtsdJy3AAPVLlCR92YTpfXXZ3xdBKDBSH1yp/DaSaWoxD7C0pN4lB9PJJiZP+2czlROObsfuep1Ciyeb8tkkYoo1WOinWNwPbAGXg+Gqi2oVEc03qzFHMr/Gw/7zYr5K/23zib2xAkUys7vW8/mcHuUN9anusnjl8jBzwn1P2LgKE/zWmNEMPY20aKqQUoHo5OBrQ2Pk9nQLB+VfPTzcO29jPzOJNcfq2PR/9O/vUTEQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(376002)(39860400002)(346002)(396003)(366004)(87266011)(36756003)(52116002)(26005)(956004)(2616005)(110136005)(53546011)(83380400001)(86362001)(16526019)(66476007)(66946007)(186003)(478600001)(4326008)(5660300002)(8676002)(8936002)(2906002)(316002)(33656002)(16576012)(66556008)(6486002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: Qta5mMfsPoUZWPkX88QIQTHnKI7qAWVUh3EvXKoR6htaZqpKG4UtnPDJfJbBdxugQAfbq444O91STpUUxhT/+OtO4hXVAqInAMwznKB9NnyeAV8XnQXRDvHTc1siqI12ze1hPGq7sSCmUcpsOlIJTJvGZSIb8FFL/YiGmCk2D4lnyd6vcaKrkVqxg3uEy/79DQVCVXNM4aAnchIuwUqO3nSAbCzzzLpYQxUoQQOAls6znl/sZ54AuYMcU4FF8O7a/SEmdD4AnAmTCcrck9CqvIIMCNb8MUu2ty5heUOJDnyHLlyj9GxUDPTF137dUKAjNNUBNrxAyqjOJPUINdkaXyAJkczhen2JjcUTfQJHqqhDO3ujJQOCJl4m4vB6wz2G+L6JCGv8U6jPpRsd54wCgTKQ+6lJxJFsUUNE9J4S3W/vJOnxZteqxTIv1wKD8bkeMgsnsbbQH+6xN2O7D/A5Sa5Gt9jRWrRLh3Uao8S5B1m/KQ0NYFo/YncmNbUSnVNEskVvpcNPhU/wmrrxptayCDeVdw3UtMufqvp/nQLO0kmYdAsU/WK2qbnAoUDfHrMlISbCwMOhbV03DRXtiM4iRYIZB8CHcFtxpHJtbb2SYMZFokPXDkEFuiH8r1bqH0gBpJUFNA+JIgpN1PzlSslSh9gw0XOFyYji0SHmJpMa6nrvZDlKfiH3Ic15m9iN773MSLB8c0CtyWoxwnrtiWuoMGzjsEIIyfVXRzQGkxlfndcM2IBA/URo6wiGCmHbmunha3s0WsOsBbC59ab9FuDkjmESohaeHRne2KldjqjLAuxgwzx8IU+2s0mT6KsCULM8JlR1q6sZjk5G/PeVVllrFxtpAdNHIbOAo18h4/7PoW3n2CORl01ofbzr46qM0ms/RCDPp0ywQidEkVlds16Ov2zFEsp0EDMeBLyk/1U6ts5NgUQW+mxL5Z/EVihDzxf3WT4s8/60ONoHCEUJ/ZCMNu4RaibH+Mont+5q47Pf21od6eTJy/OHuijiSvznbH1Xu87vQzJvLw+yCdWvM/gTn44CldvDd+hbT6gJG8oaZtUT7st29tg1xgz1Omk6kEaD
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5480be52-e29d-43d7-e318-08d8c2a8a32d
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jan 2021 09:48:02.4327 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: JYeRxz7cBVt6/FQS0uKaZuRbSNr6wzopSfV1+/HW5TC8gysFJh++D+Jqdb25ntwOlDvOWejowfumZy0NxwJiQw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4814
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dQmr-aD5XegGiJxwTHvbuyTXVpk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 27 Jan 2021 09:48:08 -0000

On 26/01/2021 19:11, Fred Baker wrote:
> Guilty as charged regarding having been in a working group chair capacity for a while. For the record, my co-chair was at one point my AD. One thing to think about in chairs - it is common to couple an experienced chair and “fresh meat” for training purposes

I am conflicted on this.  In general, I believe that all posts should be 
limited, to five years or less.  On the other hand, if I want to 
reference an exemplar of what a WG chair should be seen to do, then your 
chairmanship is high on the list and losing it would diminish the IETF.

On the other hand, I may see a WG chair in place for a long time and 
doing the job in a way that I believe damages the IETF and cannot 
understand why the ADs do not act.  Were we meeting in person, I would 
say more but that is not for e-mail.

One step forward would be to stop WG Chairs authoring I-D.  If they 
cannot get someone else to hold the pen, then there is insufficient 
support, perhaps insufficient leadership, in the IETF for the work to 
proceed IMHO.

 From my own experience of running things, sometimes the way forward is 
to create a hole, a space, not having a clear idea of what will fill 
that hole, and see what comes to fill it.

Tom Petch

> A suggestion: it might be worthwhile to keep some form of nomination roll - if someone would like to become a chair, they sign up, and their colleagues can (in one way or another) say good things about them. Then when an AD is looking for a possibility, s/he can review the roll. I suspect that the biggest reason ADs choose folks they know is that they don’t necessarily have ways to expand their circle of friends. The most common timing for people to become chairs is probably at working group formation, although it’s not limited to that, and the chair is one of the proponents of the project. Another source of leaders is folks that post drafts. If a person posts periodically and becomes known as an intelligent person that is easy to work with, they become part of a pool to tap.
>
> The comment about “big companies” holds water. I once worked for a smaller company, and was told that its employees read and commented on drafts, but didn’t venture further; the company tried to NOT employ leadership. I filed drafts anyway, and lo and behold the NM AD (Dave Crocker at the time) wanted to open a working group and needed a chair. But yes, larger companies sometimes see leadership positions as in their interest, and are willing to see employees take that step (may even include the possibility in job descriptions or internal training, or institute a corporate policy of promoting its people or hiring leadership). So anyone *can*, but larger companies have more resources to expend in that direction. I have mentioned this before, but I’ll mention it again: if you’re *expected* to show up at random meetings and workshops, funding can be an issue. The LLC can encourage non-big-company folks by having a funding mechanism for their travel expenses.
>
> Sent from my iPad
>
>> On Jan 26, 2021, at 10:28 AM, STARK, BARBARA H <bs7652@att.com> wrote:
>>
>> Since this conversation is happening, and I had a first row seat to all things NomCom this past year ...
>>
>> I don't think the pool of nominee diversity reflected the diversity of the set of people who regularly attend meetings. In my NomCom Chair report at IETF 109, I specifically highlighted the big difference in "time zone" / geographic diversity that was made obvious to me by the time zone info Calendly gave me when nominees scheduled their interviews vs. available statistics regarding current-address-continent of meeting attendees.
>>
>> IIRC, all the nominees were WG Chairs. This is generally considered an intermediary step towards the NomCom-appointed leadership positions. I strongly suspect (but don't feel incented to get real statistics) that the nominee pool diversity reasonably resembled WG Chair diversity, but that WG Chair diversity does not reflect attendee diversity. It may be useful to focus on how to increase WG Chair diversity. I actually think there are some rather simple-to-implement ideas that could move this in the "right" direction (where "right" => leadership diversity = regular attendee diversity).
>>
>> Most organizations that have improved their diversity at various management layers have done so by instituting a policy that requires the "hiring boss" to interview a diverse candidate pool. In many cases, the organizations also had to implement policies that made it easy for people interested in a position to self-nominate (apply) for it, rather than allowing the "hiring boss" to choose the candidate(s) from among the people they like, hang out with, and are comfortable with (or recommendations from such people). I've noticed that WG Chair positions are rarely broadly advertised and that each AD seems to have their own method of figuring out who to interview for a Chair position. It might make it easier for ADs to interview a more representative (of regular attendees) set of people if available WG Chair positions were posted and people were allowed to ask to be interviewed (or nominated by a "friend") for the position.
>>
>> Another part of this, though, is the scarcity of open WG Chair positions. People mentioned that they don't want people hanging out in AD and IAB positions for many terms. But what about long-standing WGs where all the Chairs have been there for 10 or more years? Might it be useful to encourage a little more rotation of WG Chair positions?
>>
>> Just some thoughts...
>> Barbara
>>
>
> .
>