Re: Effective discourse in the IETF

Richard Barnes <rlb@ipv.sx> Wed, 03 July 2019 15:37 UTC

Return-Path: <rlb@ipv.sx>
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 E7CF21205D7 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 08:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 2CZI14Cqjl8o for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 08:37:53 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 73F571205D5 for <ietf@ietf.org>; Wed, 3 Jul 2019 08:37:43 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id v186so2446036oie.5 for <ietf@ietf.org>; Wed, 03 Jul 2019 08:37:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PuRm6gBqB8kTLtR2/zW628wdD8muO/B2sGITVbzjcMI=; b=feHrALZLrw7POX5I8QPgIFi9e0gg3HHJzIaCMWR9RTgGkgzv70gc3FKq0Ej4fllmBl tVKtmyKBOVizgQ55Mi2j8t8NLA31JJMO2QUYoBTtx1oYRUHaHzxYgzVrNGMgvfP26swm GfCZgPRviO6sjtqvrcH0QkIgDj/4Cn5bCHkKDoxie1vQgju9E1b2zG7VfsM2fQvBVmnm 7UsV4oI97BnmlzxN3fUk2ACRyWAy1XZ7xPsFrGvwk91kvoulhh4Su3NYW6/d2FMTihU0 /FROBayFlxDcpzTAVK/+pRm/ar193ZDotw3kaGBuGZgxPatgHk/oe4zIgsGJ86pDRLwt xCeA==
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=PuRm6gBqB8kTLtR2/zW628wdD8muO/B2sGITVbzjcMI=; b=INlq5uVOY53NnN7z9UFamjVCRuwXsft4fDN1FXWCE22Jj8cDa4ZFzOwZpznY7707i6 FS+izwmW+yXucW22qmUSxy1l7VdolkwpFfsleLXreVGZrICuHLSs1i4eYazedTxYAkph obAXD3DYBBJ0N13Oa+ItqRexPzgt8nWYYBgmNrf+Fy0L7tGmB1aUKKV5MAWtx89LU5em 4vy6RP6Z5i3Gsrs/ArLuQyp/xuMkGG59QTMDH+MA7A0Bb4fPR1KeYhhVRozTXcZtzMH0 8WkeE/hqFgooSydOWdcWzg3dG0vvD4XrzdFmyJeZJWHUpT6vjrV0ewkN5r7S+GjcI/Vf WNbA==
X-Gm-Message-State: APjAAAXkNByPF6w2dbYXDpgdZd845gRK1R0pcuHH9wd3jJDbymR1pYtD ieiAr95ymxSSHNd3xUT02gLoh2UmcZXlodf7AVoEDA==
X-Google-Smtp-Source: APXvYqy4i5Ax7IsIKBWITYy5ok3W8ZUOtHjuIrYFdCUPcTmnUMJJOJZ88ndpmHiTnVKyq8qAtqgDnJ1aAOfYvWeBvN8=
X-Received: by 2002:aca:f1c4:: with SMTP id p187mr7042284oih.149.1562168262447; Wed, 03 Jul 2019 08:37:42 -0700 (PDT)
MIME-Version: 1.0
References: <20190628232206.GC10013@kduck.mit.edu> <e7bf71c3-7842-8699-1f56-36ffa823da99@comcast.net> <20190701223914.GK13810@kduck.mit.edu> <bad99f11-0d66-4aba-72ef-b4b648470753@comcast.net> <34A581FE-BCFA-4FDD-A626-372E036BD79A@cooperw.in> <20190703125524.GB98598@verdi> <c24b3857-fa3e-46a9-f55b-dd160250f290@acm.org> <2807ff5a-7fd3-65cc-5574-ae05df6c622c@acm.org> <20190703141309.GX49950@hanna.meerval.net> <F86FDC5A-AF66-492E-A1FC-678486C26065@fugue.com> <20190703151443.GA49950@hanna.meerval.net>
In-Reply-To: <20190703151443.GA49950@hanna.meerval.net>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 03 Jul 2019 11:37:27 -0400
Message-ID: <CAL02cgQ2RFZ-_MJYtPhS8Vq0kOKDEmBxR8wKCc2+BJ7uTwTtLw@mail.gmail.com>
Subject: Re: Effective discourse in the IETF
To: Job Snijders <job@ntt.net>
Cc: Ted Lemon <mellon@fugue.com>, John Leslie <john@jlc.net>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005ceda7058cc8a4e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mu-EcjTmxUdAMWXCJHofUDwKjpk>
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: Wed, 03 Jul 2019 15:37:59 -0000

Just to +1 a couple of points Job makes below.

On Wed, Jul 3, 2019 at 11:15 AM Job Snijders <job@ntt.net> wrote:

> > That is, we tend not to engage in self-censorship.
>
> I respectfully disagree, I believe there have been milions of instances
> where IETFers have deleted and not-yet-send emails because they realized
> that for one reason or another the message would not positively
> contribute.
>

These observations are not contradictory.  There is a privileged group
(largely the top posters to ietf@) who feel free to say whatever is on
their mind.  There is also a broader set of folks who do not.  I can see
how Ted arrived at his conclusion, given the bias in the data.

I would also challenge the phrase “self-censorship”.  Adapting ones
communications for an audience is not censorship, it’s effective
communications.  It can require that we think a bit before we speak, but
that cost is offset by the benefit of a better functioning community.

> The IETF can’t function that way.   We have to practice.  This is not
> > a social club.  This doesn’t mean that we should be unkind to each
> > other: we should definitely do our best to be kind.  But being kind
> > isn’t always being nice, and being nice can’t be the standard of
> > discourse that the IETF follows if we wish to continue to do good
> > work.
>
> I absolutely do not think that "being nice" and "good work" are mutually
> exclusive, quite the opposite. Some of the best work done was the result
> of people being nice to each other. I define being nice as demonstrating
> patience and acting with empathy towards each other.
>

1000% this.  I've seen this work out across a bunch of different technical
communities, where there were strong disagreements, but also strong norms
for respect.

It may be surprising to folks that open discussion and strong enforcement
of community norms go together, but they're necessary partners.  One
person's speech can discourage another's, so if we really want to have an
open community, we need to keep each other honest not just technically, but
in terms of respect as well.

--Richard