Re: On harassment at IETF

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 02 April 2019 01:47 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9A412016C for <ietf@ietfa.amsl.com>; Mon, 1 Apr 2019 18:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=no 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 dm9DFO2tcVLq for <ietf@ietfa.amsl.com>; Mon, 1 Apr 2019 18:47:54 -0700 (PDT)
Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D010120021 for <ietf@ietf.org>; Mon, 1 Apr 2019 18:47:54 -0700 (PDT)
Received: by mail-ot1-f52.google.com with SMTP id f10so2956381otb.6 for <ietf@ietf.org>; Mon, 01 Apr 2019 18:47:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3JK4IgbUbpuJRwinL93CEnb/KgzANq0edecW3kul8tM=; b=rD5nhLPWZXVJEiQSN9btwsDsWXaOFTn2YqpdF0Hu9mt0l/8LzEfx1N87bCXWZOMGzz CoOdPNNEpn7rvN5qwFHALITGCMoiaNwqIjqS8ave1jBmm45BQxHtgzhjkFvOVLawotyA rPcYiY6zq6G+8V0MrtlsqLUzf/iBWw+OXwC/FhTv+OgrMtmOt4C/cXK9BmoRra/DxZH5 FPSy6esLRdiF5LKkf4RQmQnEjzRV41c4iKTjImV4fyYKHmMieCqSED/snf+wGxVoWTZo utOSltyByBKhtKK79nDTbwQgCep4UEKs7Q52V+oj7zInYw5UhtW/cwyJJxZSRO6Jmbty ydZg==
X-Gm-Message-State: APjAAAUUulZZdKIwXe4ARr2hLnpFGAU8pPdg74m1uIs3uG32TdbBxc5q i1OYYap2mVYTgZ2AzMGnF2r8m7In5Ht25fefLHk=
X-Google-Smtp-Source: APXvYqxRpTIc7AHurQXZbQCmeXCbb35mlfOi5ntD/VkYE0EY1JFISDgl/L3hyERvIzKXTsg8XDH8Y/hYPocsSYGwkCM=
X-Received: by 2002:a9d:6397:: with SMTP id w23mr27285384otk.332.1554169673229; Mon, 01 Apr 2019 18:47:53 -0700 (PDT)
MIME-Version: 1.0
References: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org> <CAJU8_nX0qTDs2tcwFC_4R-9X48NxUdiHEfDEbCrtFxEnNN9m-w@mail.gmail.com> <20190330145727.GD15757@mit.edu>
In-Reply-To: <20190330145727.GD15757@mit.edu>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 2 Apr 2019 02:47:42 +0100
Message-ID: <CAMm+LwhJQbu70NNLYYSNRbqRvREOzkkDAvVz9-hfu772uOziQA@mail.gmail.com>
Subject: Re: On harassment at IETF
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Kyle Rose <krose@krose.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004b2bb40585825370"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vuaixJRYJM5SAH4viRI07PbgVHQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Apr 2019 01:47:56 -0000

The Arisia situation was complicated by several factors. There was more
than one case at issue and in one of the cases, the accused individual
engineered a re-organization of the complaints procedure that had the
intended effect of causing the complaint against himself to be lost in the
shuffle.

As we all know from observing a certain very high profile abuser,
pre-emtive accusations of abuse are often part of the toolkit used by
abusers to cover their tracks and delegitimize the accusations made against
them.

So rules of the form 'always believe the accuser' don't work either because
the minute you make a rule of that type, it will be used for abuse.


On Sat, Mar 30, 2019 at 2:58 PM Theodore Ts'o <tytso@mit.edu> wrote:

> On Sat, Mar 30, 2019 at 12:45:23PM +0100, Kyle Rose wrote:
> >
> > Many of us observe a clear distinction between taking official action via
> > established channels against those who have violated IETF policies on
> > harrassment, and advocating mob justice. I am in favor of the former. I
> am
> > against the latter.
>
> I think it's important to remember that if there are calls for mob
> justice, that might be a sign that the offical, establish channels
> have failed in some way.  If people chose not to come forward, but are
> only willing to engage in unoffical conversations with people who
> might official roles, but who are unwilling to file a formal complaint
> because they feel unsafe in doing so --- that there might be
> consequences for the target of harassment making a formal report, or
> because they don't believe it will be taken seriously or will be
> addressed, and then they keep their mouths shut.
>
> And then several years later, when several people come forward within
> a short space of time with credible stories, and the mob shows up
> demanding resignations or they will leave the organization, and urge
> sponsors to stop funding things, etc. --- and the people with official
> hats on wring their hands and say, but.... they refused to file a
> formal complaint, so our hands were tied, and it's the target's fault,
> not ours....  does it really matter whether or not the mob justice was
> justified or right or something we should approve of?
>
> This is essentially what happened at Arisia last year.  The public
> complaint, followed up with other women declaring that they had
> similar things happen to them, with little to know followup from the
> incident response teams, and volunteers declaring they would cease work
> and withdraw their membership until there was was substantial change
> from the top, guests of honor withdrawing or declining to participate
> in future years --- was that mob justice?  And does it matter?
>
> Whether or not it was "mob justice", and whether or not the targets
> "should" have followed the official channels (some did, with no
> satisfaction), the end result was the president and most of the board
> was forced to resign as a result of the wide outcry from their
> community, and the conference went through a near-death experience.
>
> This is why all organizations need to have a very robust process;
> because if it fails, the alternative will be mob justice, whether we
> like it or not.  And when the mob shows up, and alternative is give
> them satisfaction or let the organization die, they're not going ask
> for your approval first.
>
>                                         - Ted
>
>