Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt

Sam Hartman <hartmans-ietf@mit.edu> Tue, 24 March 2015 01:44 UTC

Return-Path: <hartmans@mit.edu>
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 2825B1B2B35; Mon, 23 Mar 2015 18:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=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 nKl1PZLvsvyM; Mon, 23 Mar 2015 18:44:55 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7EA1B2B65; Mon, 23 Mar 2015 18:44:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 423C720662; Mon, 23 Mar 2015 21:42:49 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cbdhn6GZDnjZ; Mon, 23 Mar 2015 21:42:48 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-26-195.hsd1.ma.comcast.net [50.177.26.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 23 Mar 2015 21:42:48 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 4BE5A87201; Mon, 23 Mar 2015 21:44:24 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt
References: <5503914A.7060209@gmail.com> <5503BF22.5020902@gmail.com> <2AE2D092-C32A-46EB-88CA-71366965F4D7@cisco.com> <5505D873.1040203@gmail.com> <CAL0qLwbQf_2WUn8PrUXCMy_3w6tt+iJw0tyF=gUojA5fwRXJNg@mail.gmail.com> <550736E0.6080101@dcrocker.net> <20150316203250.GJ2179@mx1.yitter.info> <55073F22.6000606@dcrocker.net> <20150316204616.GK2179@mx1.yitter.info> <55074AC1.9080500@dcrocker.net> <20150316214620.GO2179@mx1.yitter.info> <550751AC.7090108@dcrocker.net> <55075EBA.4000905@gmail.com> <5509BB58.4060307@qti.qualcomm.com> <B714CBFE-5D3D-4293-91C2-534A3437EB24@piuha.net> <014401d0624e$5220d940$f6628bc0$@olddog.co.uk> <tsl619rd9t7.fsf@mit.edu> <CAKKJt-dW-sb1nvxoXDNJJmvVnieOVkcU0H6FG8JnMK6uFSnZmA@mail.gmail.com>
Date: Mon, 23 Mar 2015 21:44:24 -0400
In-Reply-To: <CAKKJt-dW-sb1nvxoXDNJJmvVnieOVkcU0H6FG8JnMK6uFSnZmA@mail.gmail.com> (Spencer Dawkins at IETF's message of "Mon, 23 Mar 2015 10:46:33 -0500")
Message-ID: <tslegof9nk7.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yBlO25zQb13W3QAU94MmnaMphBY>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Sam Hartman <hartmans-ietf@mit.edu>, IETF Discussion List <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
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: Tue, 24 Mar 2015 01:44:57 -0000

>>>>> "Spencer" == Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> writes:


>      John Klensin, Brian Carpenter, myself and perhaps Dave
 Crocker have all raised objections that the recall process
 is unlikely to work in cases of harassment.  We've each
 discussed problems with the committee itself both in terms
 of fairness and confidentiality of information provided by
 subject and reporter.

    Spencer>    Right. That's what I think I've seen.  If I'm reading
    Spencer> this part of the conversation accurately, at least some of
    Spencer> those people are objecting that the recall process is
    Spencer> unlikely to work in any case.  If I needed to be recalled,
    Spencer> I'm not sure it matters much why I need to be recalled
    Spencer> (harassment, or some other reason).  If the vast majority
    Spencer> of the community thinks the recall process would work
    Spencer> perfectly if we ever tried to use it running to completion,
    Spencer> all they have to do is say so.  But if that's not the case
    Spencer> ... I would encourage people to think about fixing the
    Spencer> recall process more broadly.  I understand that some of the
    Spencer> mechanics may very well be different for harassment, but I
    Spencer> would encourage people to make the process work in the
    Spencer> general case, and then start making changes to accommodate
    Spencer> the ways that harassment is different.  Maybe it's not
    Spencer> possible to have a process for harassment removals that
    Spencer> looks anything like recalls for other reasons, but I would
    Spencer> encourage the community to special-case as little as
    Spencer> possible here.  Speaking only for myself, of course.  

I'm very sympathetic to that, but I want us to have something that works
in practice now for harassment even if we make changes later and employ
abstraction once we figure out what the abstraction is.

For myself, I'm unconvinced that a recall for harassment reasons should
look at all like a recall for bad job fit.

Here are some reasons I find them different:

* The skill set necessary to fairly handle a harassment claim is very
  different than the skill set necessary to evaluate an I* member's
  performance.

* There are less confidentiality issues surrounding  a recall for bad
  job fit.



In addition, if I were going to reform the recall process, the kind of
reforms I'd generally propose would not help with harassment issues.
The main problem I have is that it's perhaps a bit too difficult too
collect signatures.  So, I'd look at proposals like the one John Klensin
authored a while ago to let sitting I* members sign recall petitions, or
possibly letting our leadership bodies remove one of their members
directly as an additional alternative to the recall process.

Honestly, it's a bit hard for me to evaluate because there's only been
one I* member I was convinced needed to leave their office.  In that
case we did eventually get a recall petition signed.  I've disagreed
with I* members in the past and a couple of times suggested to nomcom
that a change would be for the best, but even then I valued the smoothe
transition of using the normal nomcom process.

I hope we never need to remove someone from I* for harassment.
However,  part of the point of having this harassment policy is to help
people feel safe and secure participating in our standards process.

Knowing that adequate remedies exist is part of that.

I understand that from the respondent's standpoint being able to trust
that you'll be given a fair hearing is also part of the process.
However, were I to be a respondent I'd be more worried about the fair
hearing from the folks who could ban me from the meeting than whether I
got removed from an I* position.  We have to get fairness right for the
exclusions too.