Re: [88attendees] Anti-harassment policy and ombudsperson

Jon Hudson <jon.hudson@gmail.com> Mon, 04 November 2013 18:54 UTC

Return-Path: <jon.hudson@gmail.com>
X-Original-To: 88attendees@ietfa.amsl.com
Delivered-To: 88attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5C421E81BA for <88attendees@ietfa.amsl.com>; Mon, 4 Nov 2013 10:54:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeucM7YG+sON for <88attendees@ietfa.amsl.com>; Mon, 4 Nov 2013 10:54:39 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 39D4721E8173 for <88attendees@ietf.org>; Mon, 4 Nov 2013 10:54:33 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id e14so12824531iej.22 for <88attendees@ietf.org>; Mon, 04 Nov 2013 10:54:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3hxpALxKsMsyQGqbhaEXmsA/aBKocYfUZHuON9fB1Dc=; b=vbS+nrggsARTGg9dd4DGnDC/b0ZOGPHSBHxg6RkcAomZOnUE/VqpvtepYrxh3KA/yn bkxe+aS6caIhSBuwR+V8soa8T+zKwPnpFccKDZYI0vEfGUlcrfW4FC6DPnknpxxkAIp/ SQuiLrzZSOg7xoDZw4RCdzgEogx3N/jsY/8vyMd2rWk6g/117RrNW1zgCA1boBZ0C/nD gjSbU3PDooGmouiE4cgC5K9820WEVFbZWZHfXSCkhRg3v4M8BMBvRqMXtXUPqvCrNzYU ecohICNk6e0R9NzkjuMLqoGBam75RktiMtXlpL5s1RfPywPxTgN9ilVS2Qc6SeyHpONl oyvQ==
MIME-Version: 1.0
X-Received: by 10.50.114.168 with SMTP id jh8mr12743160igb.6.1383591272872; Mon, 04 Nov 2013 10:54:32 -0800 (PST)
Received: by 10.50.135.102 with HTTP; Mon, 4 Nov 2013 10:54:32 -0800 (PST)
In-Reply-To: <6C6450A1-BF6E-4EB9-BB36-EBA8E3F07F0C@fugue.com>
References: <211BE376-9766-4024-9443-304336C6C14D@ietf.org> <5276E036.4030808@sunet.se> <5277B272.5090007@ericsson.com> <CAHBU6iu5vyxio1G0Z8WpSxbWK2Y_XGumX_4M-ALZChNLW4YT6A@mail.gmail.com> <6C6450A1-BF6E-4EB9-BB36-EBA8E3F07F0C@fugue.com>
Date: Mon, 4 Nov 2013 10:54:32 -0800
Message-ID: <CANbjNQEbuWAi-Epz+Yu64kHPfYuB9SssyQQeK3ZcJyuu04oZ1g@mail.gmail.com>
From: Jon Hudson <jon.hudson@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=089e01229f86558c4504ea5e726e
Cc: Balazs Lengyel <balazs.lengyel@ericsson.com>, Tim Bray <tbray@textuality.com>, IETF 88 Attendees <88attendees@ietf.org>
Subject: Re: [88attendees] Anti-harassment policy and ombudsperson
X-BeenThere: 88attendees@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list of IETF 88 attendees that have opted in to the list." <88attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/88attendees>, <mailto:88attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/88attendees>
List-Post: <mailto:88attendees@ietf.org>
List-Help: <mailto:88attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/88attendees>, <mailto:88attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 18:54:40 -0000

For those not familiar with the Pycon event here is one take on it

http://arstechnica.com/tech-policy/2013/03/how-dongle-jokes-got-two-people-fired-and-led-to-ddos-attacks/

This really is a great example of things getting way out of hand way too
fast.


On Mon, Nov 4, 2013 at 10:45 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Nov 4, 2013, at 9:10 AM, Tim Bray <tbray@textuality.com> wrote:
> > It seems fairly obvious that this is in response to concerns in the the
> tech-conferencing community as a whole, not the IETF specifically.
>  There’ve been issues at gatherings of other communities that have spiraled
> into the danger zone very quickly and seriously damaged careers and lives.
> Trying to get in front of this proactively seems smart to me.
>
> Exactly.   Google pycon harassment for an example.   It is a very safe
> assumption that in any organization the size of the IETF, some incidents
> have occurred, and some will occur in the future.   I would like to think
> the IETF is special, and that such things never happen, but I do not think
> it is responsible to make such an assumption, no matter how tempting it is.
>
> If you look at the pycon incident, it's clear that both the "accused" and
> the "accuser" suffered way out of proportion to what was called for by the
> actual incident.   The whole fiasco would have come out hugely better for
> all involved if a clear policy had been in effect at that conference.
>
> I would not like to see something like that happen at IETF.
>
> _______________________________________________
> 88attendees mailing list
> 88attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/88attendees
>



-- 
"Do not lie. And do not do what you hate."