[Eligibility-discuss] The recall procedure and shaming
John C Klensin <john-ietf@jck.com> Tue, 29 October 2019 18:10 UTC
Return-Path: <john-ietf@jck.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 E451712088A for <eligibility-discuss@ietfa.amsl.com>; Tue, 29 Oct 2019 11:10:46 -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, 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 kA8c58ElZAus for <eligibility-discuss@ietfa.amsl.com>; Tue, 29 Oct 2019 11:10:41 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7C6B120A08 for <eligibility-discuss@ietf.org>; Tue, 29 Oct 2019 11:10:15 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iPVwc-000NaG-1Z; Tue, 29 Oct 2019 14:10:14 -0400
Date: Tue, 29 Oct 2019 14:10:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <resnick@episteme.net>, eligibility-discuss@ietf.org
Message-ID: <69DFC9FF020C06F8353314B2@PSB>
In-Reply-To: <99234A93-2224-47F1-AA65-C71DC5DA3CD3@episteme.net>
References: <99234A93-2224-47F1-AA65-C71DC5DA3CD3@episteme.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/WAALMmo2wFWQP3lDYNUe9NBHSYg>
Subject: [Eligibility-discuss] The recall procedure and shaming
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: Tue, 29 Oct 2019 18:10:47 -0000
--On Tuesday, October 29, 2019 10:20 -0500 Pete Resnick <resnick@episteme.net> wrote: >... > One concern about making the recall process easier to use is > that the invocation of the recall procedure could be used to > shame leaders who are failing to get their work done (as > against those engaged in active bad behavior). >... This sort of got lost in the conversation, but I want to suggest a radical idea and note something else that did not come up clearly enough to be reflected in the minutes. In reverse order and noting that these are general thoughts about the whole process and its utility, not just about the initiation (petitioning) process. >From what I remember of the POISED discussions, when the recall model was designed, we were thinking a lot more about malfeasance (engaging in active bad behavior in your words) than about non-performance (failing to get work done or just disappearing from the role). Maybe there is a third category, which is behavior toward, and positions on, the work of the IETF that is seriously out of line with apparent community consensus [1]. In any event, I think it would be very helpful if we tried to separate the three in our thinking. For serious non-performance or disappearance, the recall mechanism may just be wrong. In ideal situations, and I would classify the one case that almost went to a recall committee that way although it took too long, the optimal answer is probably to more or less privately reach out to the person involved and convince them to voluntarily resign and step down. If nothing else, that should take less time and be less damaging to both the offending party and the community. If they obstinately refuse to do so, the situation looks more and more like malfeasance. For cases of malfeasance, a careful, multi-step, process may be exactly what we need (even though I worry about its taking too long). It is, in any event different because non-performance or disappearance can, in at least most cases, be objectively measured and evaluated (even if one can imagine debates about whether someone who is doing half the job should be forced out) while malfeasance is almost always going to be a matter of judgment and degree. Second, what I heard on the call (others may have heard things differently), I'm a little concerned about what seemed to be a logic path between "this could be used to shame" and "therefore we don't want to touch it". It is oddly possible that the recall procedure has actually worked rather well, but in a way that has been largely invisible to the community. People who were behaving badly have occasionally been told "stop that or resign or you will have to live through an unpleasant and possibly career-damaging recall procedure" and that has brought about changes in behavior. I'm even aware of one case in which someone was shown a petition with most or all of the required signatures and given that same message. Now those cases are threats of shaming and offers of shaming and having the dirty laundry washing in public would certainly be shaming. But they are also part of holding someone accountable and keeping the IETF working. If we never want to anyone to feel shames, then we should eliminate the ability of the Nomcom to not return people who were publicly willing to serve another term in their positions. And maybe we should figure out how to not disclose the names of people who have indicated their willingness to serve in particular positions because no being selected might cause shame. Let's be a little careful about what we wish for... or wish to avoid. best, john [1] It is really a separate issue, at least IMO, but proposals to let I* bodies remove their own membership are part of that issue because, if we start removing people for that sort of reason, we'd better be really sure that it is community consensus they are out of line with, or "self-selection" by the bodies is the least of our worries, especially because dissenting voices and reminding the community about other perspectives can be very valuable.
- [Eligibility-discuss] Draft meeting minutes Pete Resnick
- [Eligibility-discuss] The recall procedure and sh… John C Klensin
- [Eligibility-discuss] Questions about I* bodies r… John C Klensin
- Re: [Eligibility-discuss] Questions about I* bodi… Melinda Shore
- Re: [Eligibility-discuss] Questions about I* bodi… Samuel Weiler
- Re: [Eligibility-discuss] Questions about I* bodi… Warren Kumari
- Re: [Eligibility-discuss] Draft meeting minutes Brian E Carpenter
- Re: [Eligibility-discuss] Questions about I* bodi… Michael StJohns
- Re: [Eligibility-discuss] Draft meeting minutes Michael StJohns
- Re: [Eligibility-discuss] Draft meeting minutes Brian E Carpenter
- Re: [Eligibility-discuss] Draft meeting minutes Pete Resnick
- Re: [Eligibility-discuss] Questions about I* bodi… S Moonesamy
- [Eligibility-discuss] on re-using nomcom chairs (… Andrew Sullivan
- Re: [Eligibility-discuss] Questions about I* bodi… John C Klensin
- Re: [Eligibility-discuss] Questions about I* bodi… S Moonesamy
- Re: [Eligibility-discuss] on re-using nomcom chai… Michael StJohns
- Re: [Eligibility-discuss] Questions about I* bodi… John C Klensin
- Re: [Eligibility-discuss] Questions about I* bodi… Warren Kumari