Re: discussion style and respect

Dave Crocker <dhc@dcrocker.net> Sat, 13 June 2015 13:40 UTC

Return-Path: <dhc@dcrocker.net>
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 5CA9C1A88A6 for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2015 06:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable
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 E2FHvAuRffSo for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2015 06:40:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 585F21A889F for <ietf@ietf.org>; Sat, 13 Jun 2015 06:39:53 -0700 (PDT)
Received: from [192.168.1.73] ([46.7.136.175]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t5DDdmi1013542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 13 Jun 2015 06:39:52 -0700
Message-ID: <557C32A4.2030708@dcrocker.net>
Date: Sat, 13 Jun 2015 14:39:48 +0100
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: discussion style and respect
References: <3BF40BF3-B7EB-4571-BD7B-D394D4F0CB6C@ietf.org> <20150610204037.6837A1ACD25@ietfa.amsl.com> <F56A33D90543E4A17CDC2875@JcK-HP8200.jck.com> <557AB950.3010005@dcrocker.net> <61C795A96BCCD200B6103001@JcK-HP8200.jck.com>
In-Reply-To: <61C795A96BCCD200B6103001@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 13 Jun 2015 06:39:53 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0SYaBpqp55UuDyCPjLwV9HrMGgs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sat, 13 Jun 2015 13:40:14 -0000

> We have rules.  They are mostly vague and subjective, but

They are not markedly more vague or subjective than is typical for this
topic.  The problem is with enforcement, not with the rules.


> We almost never try to enforce
> them when they appear to be violated, at least beyond private or
> low-key requests/ advice that someone shape up.

It's worse than even that.  We never enforce them, unless the offender
is a recidivist we do not like.

For recidivists we do like, we give them the mild warning and never go
further, pretending each offense does not sufficiently cross the line or
is new and they only warrants another quiet, useless warning.

To add to this egregious model, we consider it justified to engage in
offensive behavior if the community does not like the target.  After
all, they were asking for it...


>     We also have a recall
> mechanism for removing people from leadership position who have
> gotten out of hand, a mechanism that has never been used to the
> point of actually removing someone from office. 

Somewhat ironically, Nomcom regularly returns to office people who
regularly engage in offensive behavior.


> FWIW, I also believe that we are far more often victim to
> consensus by attrition than to direct interference with the
> system or overt bad behavior.   

Possibly a worthy topic, but it's quite separate from the continuing
tolerance and even encouragement of grossly unprofessional conduct.



Again:


   We have rules concerning acceptable behavior.  We do not enforce
them.  Perhaps they need strengthening, but we aren't even using the
ones we have.

   A generic, public call for better behavior is always useless.  It
might make the speaker feel that they've done something useful, but they
never have.  Never.

   A quiet, private chastisement to an individual is always useless with
a recidivist.  We have quite a few of those.

   At a minimum, a first step in taking corrective action needs to be to
require the offender to initiate a public apology.  The community needs
to see that unacceptable behavior is not acceptable.  (The issue is not
that the community see that this is the result of disciplinary action;
it needs to see acknowledgement that the behavior was not acceptable.)

   For recidivists and anyone engaging in particularly extreme behavior,
we need to start taking more severe actions.[*] There needs to be an
plan of escalating consequences.  It needs to be applied.

   Nomcom needs to pay attention to candidates' persistent, offensive
behaviors.


d/

[*]  This includes for offenses we class as harassment, taken to the
Ombud.  To date, this has been an entirely ineffective channel.


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net