Re: Updating BCP 10 -- NomCom ELEGIBILITY

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 12 February 2015 13:44 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A811A8823 for <ietf@ietfa.amsl.com>; Thu, 12 Feb 2015 05:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FhMkP7ml9SxO for <ietf@ietfa.amsl.com>; Thu, 12 Feb 2015 05:44:42 -0800 (PST)
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 ADCC81A1A96 for <ietf@ietf.org>; Thu, 12 Feb 2015 05:44:40 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2C133203CD; Thu, 12 Feb 2015 08:52:09 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 2149F63A21; Thu, 12 Feb 2015 08:44:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E1ED1637F4; Thu, 12 Feb 2015 08:44:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
In-Reply-To: <CAL0qLwZ5DuBKH+jwiyT5+EUGoeR-XmCBp3dTg2SkWCK_kH+ihw@mail.gmail.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <6025.1423672358@sandelman.ca> <CAL0qLwYtE618sA99hgXP-5wk+BYdcXLbiZqd_36OreYQ1LB7hQ@mail.gmail.com> <10262.1423710637@sandelman.ca> <CAL0qLwZ5DuBKH+jwiyT5+EUGoeR-XmCBp3dTg2SkWCK_kH+ihw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
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-sha1; protocol="application/pgp-signature"
Date: Thu, 12 Feb 2015 08:44:38 -0500
Message-ID: <10464.1423748678@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VqaXPTTG1F4DRZSNOQWwyA6VL4s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Feb 2015 13:44:52 -0000

Murray S. Kucherawy <superuser@gmail.com>; wrote:
    > other things that I would argue should qualify.  For instance:  Requiring
    > that I be the submitting author on a document that got WG time disregards
    > valuable documents that never needed in-person WG time.

I take your point; the reason I wrote it that way is because I am sure that
a document that gets 'air-time' must in some way be important.  But, if your
document goes straight to publication, I guess we could change things in
point (1) about AUTH48, and include authors in that list.

    > Even better, contributing to the IETF in meaningful ways is not always
    > tied to meetings.  Some working group chairs and editors do great work
    > for WGs that never even meet.  Nothing ever gets agenda time in those.

I was trying to capture this into the AUTH48 criteria. The reason I picked
AUTH48 is that the document can sit for months in misref after that point.

    > The speed with which something gets to AUTH48 isn't always reliable.  I'm
    > not sure making that a gating factor would work so well; I could lose my
    > eligibility just because some directorate review took way too long to
    > come in.

I see your point;  we value writing documents, reviewing them, and
progressing them.  Progressing them is the thing that brings a person most
into contact with the bureaucracy, and leads (in my opinion) to the most
knowledge of how things work (short of being on the nomcom...)

hmm. I guess perhaps being on the nomcom needs to be included as a
contribution...

    > To repeat: I recognize that we like the general idea here, and I agree.
    > I'm just having trouble coming up with ways to qualify that aren't
    > difficult to describe precisely and completely and don't needlessly
    > exclude people that probably should qualify.

One reason I wondered if the list should be contained in BCP10 is that I
wondered if we would find ways to evolve the list.  Of course, we can write a
document that updates BCP10.  I'm thinking that starting by including some
people is better than including none, and that if there is needless
exclusion, we should figure that out, and adjust things.

[having spent way too much time writing emails on this topic in the last 24
hours, including a few emails I decided not to send, I now wonder if I'll be
near the top of Thomas' posting summary.  Then it occured to me just now,
given how few people who came to the plenary actually read ietf@ietf, one
wonders if being on Thomas' list is a + or - :-)

--
Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
 -= IPv6 IoT consulting =-