Re: [Eligibility-discuss] enfranchising mostly-remote participants

Russ Housley <housley@vigilsec.com> Fri, 25 October 2019 18:24 UTC

Return-Path: <housley@vigilsec.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 5DACD12091D for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 11:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 w9YEPWlnscI9 for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 11:24:38 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 755CA120A23 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 11:24:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E4593300B1A for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 14:24:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hkpWl7UseVAP for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 14:24:33 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 63234300250; Fri, 25 Oct 2019 14:24:33 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <BA6857F9-5416-48E2-B27C-E906663AB1CE@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_32755F4E-1AAE-4B39-B1E4-70CE08F90CD8"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 25 Oct 2019 14:24:33 -0400
In-Reply-To: <19743.1572014559@localhost>
Cc: eligibility-discuss@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <19743.1572014559@localhost>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/rVYC--BpXveK9sE6VLAk7ywJ9HE>
Subject: Re: [Eligibility-discuss] enfranchising mostly-remote participants
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: Fri, 25 Oct 2019 18:24:40 -0000

The goal should be to seat people that understand the IETF culture and will actively participate in the NomCom if chosen.

Rule (a) tries to approximate these by regularly showing up at the meetings.

I think that an alternate rule would show investment in the process.  Maybe listed as author of an RFC that was published in the last 5 meeting window.

Russ


> On Oct 25, 2019, at 10:42 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> The current rule for nomcom eligbility is physical attendance at 3 of the
> past 5 meetings.  Let's call this the (a) rule.
> 
> (a) Anyone who satisfies the 3/5 rule is eligible.
> 
>   I propose that we evaluate this in April/May/June of each year, as that is
>   when nomcom cares, and that we apply the status until the following April.
> 
>   {This simplifies things a great deal at the possible cost of not
>   enfranchising someone in November of that year for a potential recall}
> 
> I propose to add (b) rule:
> 
> (b) In April of each year determine:
>    b.1 anyone who had satisfied the (a) rule in the previous year, but does not
>     -OR-
>    b.2 anyone who satisfied the (b) rule in the previous year
>  AND
>    b.3 has attended at least one meeting of the past three.
> 
> IS eligible for the rest of the year.
> 
> ---
> 
> NOW, I didn't write Physically Attended in B.3.
> 
> There are numerous variations and formula that we could go for here, and I
> have quite a number of possible suggestions, but before we tweak that, is any
> support for the overall concept?
> 
> {We *MAY* want to include a one-time bootstrap where we say that anyone who
> was nomcom eligible back to... 1992 if you like... is deemed to satisfy (b)
> for the previous year}
> 
> The GOAL is that once people become nomcom-eligible, we assume that if they
> continue to be involved, that they continue to have a good idea what is going
> on.
> 
> I think that having to satisfy the (a) rule at least once is still a pretty
> big step, and my proposal does not mean I do not also want some (c) rule.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 
> 
>