Re: [Eligibility-discuss] Review of draft-carpenter-eligibility-expand-06

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 29 October 2020 16:43 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 B5F353A09BE for <eligibility-discuss@ietfa.amsl.com>; Thu, 29 Oct 2020 09:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 lLWp9kM-E9s8 for <eligibility-discuss@ietfa.amsl.com>; Thu, 29 Oct 2020 09:43:03 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D81493A09BC for <eligibility-discuss@ietf.org>; Thu, 29 Oct 2020 09:43:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9B0C8389CF; Thu, 29 Oct 2020 12:49:47 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WFMb4gZ_AD97; Thu, 29 Oct 2020 12:49:47 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2C4A5389C9; Thu, 29 Oct 2020 12:49:47 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C8CB559A; Thu, 29 Oct 2020 12:43:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Barry Leiba <barryleiba@computer.org>, eligibility-discuss@ietf.org
In-Reply-To: <f975ab5a-0f81-ac1f-9a60-36c54c606561@gmail.com>
References: <CALaySJ+pWd7CCq5j7GLUxF-VOwAm4tx3OthE_gU9pUaMous7=g@mail.gmail.com> <f975ab5a-0f81-ac1f-9a60-36c54c606561@gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Thu, 29 Oct 2020 12:43:00 -0400
Message-ID: <15656.1603989780@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/j6XpZDqE3TgYUFYbZfiraTCPXrI>
Subject: Re: [Eligibility-discuss] Review of draft-carpenter-eligibility-expand-06
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: Thu, 29 Oct 2020 16:43:05 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> *  Path 3: Has been a listed author of at least 2 IETF stream RFCs
    >> within the last 5 years.  An Internet-Draft that has been approved
    >> by the IESG and is in the RFC Editor queue counts.
    >>
    >> I find this troubling for a few reasons, though I’ll say up front that
    >> I don’t have a suitable alternative that meets the “algorithmis” goal.
    >>
    >> 1. While I understand the reason, as stated in the notes, for making
    >> this 5 years, it seems odd that someone whose name got on a draft 5
    >> years ago becomes NomCom-eligible, while someone who was the working
    >> group chair at the time but stepped down a year later does not.

    > Yes, one could play with this for ever. Maybe we will get enough
    > IETF Last Call inputs to confirm the 5 years or reduce it.

We increased it from 3-years to 5-years for RFC-publication because we felt
3-4 years was a typical cycle time from ID-00 to RFC.  So if someone works on
one document at a time that 3-years might catch them between publication
times.

To me, the question is whether or not we should increase WG chair criteria
from 3-years to 5-years if you want parity.

    >> 3. It’s often the case that people listed in a Contributors section
    >> have been more active participants (and had more to do with shaping
    >> the document) than some of those listed on the front page.

    > That's true, but Contributors sections are relatively rare. Our goal
    > here is surely to have a big enough pool, not to collect every possible
    > name.

I'd really like to encourage the contributors section to always use the
available structure so that we can, going forward, collect that information
mechanically.  Then, we could collect some data.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide