Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107
Michael Richardson <mcr+ietf@sandelman.ca> Sun, 29 March 2020 22:26 UTC
Return-Path: <mcr+ietf@sandelman.ca>
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 EA6AD3A0E6A for <eligibility-discuss@ietfa.amsl.com>; Sun, 29 Mar 2020 15:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.012
X-Spam-Level:
X-Spam-Status: No, score=0.012 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1U66tJ3_Iagd for <eligibility-discuss@ietfa.amsl.com>; Sun, 29 Mar 2020 15:26:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3D53A0E86 for <eligibility-discuss@ietf.org>; Sun, 29 Mar 2020 15:26:01 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 3660B3897E for <eligibility-discuss@ietf.org>; Sun, 29 Mar 2020 18:24:30 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2C1B9FC9 for <eligibility-discuss@ietf.org>; Sun, 29 Mar 2020 18:25:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: eligibility-discuss@ietf.org
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="==-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 29 Mar 2020 18:25:58 -0400
Message-ID: <28433.1585520758@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/RxHg6sIV1iWJax_TEwjFQqOEwik>
Subject: Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Sun, 29 Mar 2020 22:26:09 -0000
--- Begin Message ---My two cents... There are many steps to the process related to nomcom participant selection. The chair along with the secretariat along with the tools team leverage all the registration and attendance data present. My experience is that there are multiple places data about past attendance is pulled. This leads to discrepancies in validation of eligibility that requires investigation on a case-by-case basis. In the end the nomcom team gets a list together and sends it to the community for review. During that process, some in the community do take the time to review the list and provide their opinions on the list (kudos to the community!). There are times that the list is missing people, there are times the list has people that are not eligible for various reasons. Once the list is finalized, the randomizer is run and the people on the list are contacted to determine if they are willing to do the job. Keeping in mind that we need to check for disqualifying factors like affiliations (no more than 2 of the same) and/or if the individual has decided to run for leadership. Once the random list is validated, it is sent to the community for yet another review. So the list has to go through another challenge period before the list of volunteers is finalized. My point is... There is a lot of community feedback and transparency to the volunteer selection process. There are multiple chances for challenge and comment. So while I understand the desire to "reward" people that have attended 3 out of the last 5 face-to-face IETFs meeting (because they would be more steeped in the culture I reckon), I find the 3 out of 5 face-to-face meeting issue to be less important (anachronism really) than the "I'm willing to do the job" criteria. As more work is done remotely on email lists, we have seen that people can be effective with remote attendance. I value the face-to-face meetings, but I sense a change (virus notwithstanding) demonstrating the efficacy of hybrid f2f/virtual meetings. That leads me to the conclusion that getting virtual attendance counted for nomcom participation a must. Currently the requirements on a nomcom member are high. It is STRONGLY recommended, that if you are on a nomcom that you attend the Summer meeting and the Fall meeting IN-PERSON and dedicate a serious bulk of your time at the Fall meeting for interviews and discussion. There are eMeetings between Summer and Fall, and if the nomcom doesn't finish, there are eMeetings after the Fall meeting. Each nomcom has its own set of issues. We have had remote participants that do practically nothing, we have had remote participants that perform extremely well. Same can be said for face-to-face participants. It is harder on the face-to-face participants in some ways to include remote participants in the deliberations at a face-to-face meeting, but WE are the INTERNET community and should be able to figure it out. My suggestions: 1) Drop the 3/5 face-to-face requirement for the upcoming nomcom (since we don't really have a process for virtual participation yet) 2) For this upcoming nomcom - take the list of anyone that checked the "nomcom willing" box from any of the past 5 meetings (103 - 107) - and follow the usual process described above. 3) When the call is made for nomcom volunteers, send the criteria/expectations for participation, and the list from step 2 4) Ask the community for feedback on the list as per usual 5) For IETF 108 (and beyond) registration. Keep asking the question if the individual is willing and able to do the nomcom job and start tracking virtual attendance if you really still want to have some kind of 3 out 5 meeting requirement (virtual, hybrid, face-to-face whatever) 6) Rinse, Repeat -scott. -----Original Message----- From: ietf <ietf-bounces@ietf.org> On Behalf Of Lars Eggert Sent: Friday, March 27, 2020 7:53 AM To: Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> Cc: Michael Richardson <mcr+ietf@sandelman.ca>; Barry Leiba <barryleiba@computer.org>; IETF discussion list <ietf@ietf.org> Subject: Re: NomCom eligibility & IETF 107 Hi, On 2020-3-26, at 19:54, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote: > I want to get the largest pool of candidates. so that's a worthwhile goal. But: My guess is that any fine-tuning here would not make a huge difference to the size of the pool of people eligible to be considered as voting members. The pool that we actually want to maximize is the sub-pool of eligible people *who volunteer to be considered*. If we can convince more eligible people to actually volunteer it would have a much more sizable impact (again, a guess.) Anyone got data on #eligible vs. #volunteered? Lars--- End Message ---
-- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- Re: [Eligibility-discuss] NomCom eligibility & IE… Michael Richardson
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- Re: [Eligibility-discuss] NomCom eligibility & IE… Salz, Rich
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- [Eligibility-discuss] ways to advance the discuss… Michael Richardson
- Re: [Eligibility-discuss] NomCom eligibility & IE… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- Re: [Eligibility-discuss] NomCom eligibility & IE… Michael Richardson
- Re: [Eligibility-discuss] NomCom eligibility & IE… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- Re: [Eligibility-discuss] NomCom eligibility & IE… Loa Andersson
- Re: [Eligibility-discuss] NomCom eligibility & IE… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- Re: [Eligibility-discuss] NomCom eligibility & IE… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Salz, Rich
- Re: [Eligibility-discuss] NomCom eligibility & IE… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Ted Lemon
- Re: [Eligibility-discuss] NomCom eligibility & IE… Salz, Rich
- Re: [Eligibility-discuss] NomCom eligibility & IE… Brian E Carpenter
- Re: [Eligibility-discuss] ways to advance the dis… Brian E Carpenter
- Re: [Eligibility-discuss] ways to advance the dis… Victor Kuarsingh
- Re: [Eligibility-discuss] NomCom eligibility & IE… Michael Richardson
- Re: [Eligibility-discuss] ways to advance the dis… Michael Richardson
- Re: [Eligibility-discuss] ways to advance the dis… Stephen Farrell