Re: RFC Series Editor Resignation

Kyle Rose <krose@krose.org> Wed, 03 July 2019 15:00 UTC

Return-Path: <krose@krose.org>
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 B852E1203AC for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 08:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 AaVUqAvsH3nk for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 08:00:57 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 08959120151 for <ietf@ietf.org>; Wed, 3 Jul 2019 08:00:57 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id y57so1485653qtk.4 for <ietf@ietf.org>; Wed, 03 Jul 2019 08:00:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vkJiQEGoqZbGzj8lt3/TJSfglwlNiHvqHgzHfwD/VJc=; b=bm9xVAugPZlEJR9RAIOPbqQFIE2NbtsVIqjOJubwIkmznvKKOpn2v3rE3CreHsahY2 T/xTAB3KugV9Tt+x0eFZJU4QLAVazHp8X8ZcfdcxF33X7jTrb2HE0jEIP1HsGe8zlieK mo9rLXQNy7u19N9br/DVbCnhlev5J4b1X/v+s=
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=vkJiQEGoqZbGzj8lt3/TJSfglwlNiHvqHgzHfwD/VJc=; b=uN5qEj7Br+32uGcsv7R8hna2WrwxWlRvFvQLZxEMJkmFlR/3BXuhwIGlAX0ypeQewM 2nQcb4DxAed/hCnYklXiqqR9EQ1dXyF5CgGp19O4WUs501GT4Aftzhvoq6tCRBeVWB3n wgNizSFytR6W/79Xrh0bDwZy4B3f1ug1bwPIh2775mtfYsZq3yaJ7FP9wOWwnyNXhUgt n2cJGPh/jSm2XtDNnadScyB7RTqy3sAdxmD0nQjgV/3GtxeseGWKTmHZ90Xh73qEQmiq mzVzPrglheZtNJQTVCih2Q81UOqjdTbHzZFWmOSM448ZShKi+ShX9inr9KXkPml7JYAf noRA==
X-Gm-Message-State: APjAAAVOgpnGBAM6gbWX1FqiVwa4Ag7V7ytAWoB+El+x8bHo8DgYOWZW ai7La20y6LzHJUOsAd+8TkixVo+6Obi/iZku3jKeSg==
X-Google-Smtp-Source: APXvYqxDn9zwQJ980ZWif4WEIknu6wPzvBaLj6SH7GKGGmeRExr0f+26hgd2F3X0f+0bH739pXZHiJYN4WXXZ4/u/VY=
X-Received: by 2002:a81:4911:: with SMTP id w17mr9504288ywa.156.1562166055696; Wed, 03 Jul 2019 08:00:55 -0700 (PDT)
MIME-Version: 1.0
References: <20190628214503.GC30882@kduck.mit.edu> <7e5167bf-8167-bf81-981f-662d6da6f1ab@comcast.net> <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> <B926E8F3-AC7C-4EF0-B433-82513723194A@sobco.com> <3EACBC3B-B559-45DF-B976-6F770096C9B5@cooperw.in> <20190703140240.GD2041@mit.edu>
In-Reply-To: <20190703140240.GD2041@mit.edu>
From: Kyle Rose <krose@krose.org>
Date: Wed, 03 Jul 2019 11:00:44 -0400
Message-ID: <CAJU8_nXtfFDrsEGs4mPcva8NSHAjouDjhJOB=vjAPEsW_jv4Bg@mail.gmail.com>
Subject: Re: RFC Series Editor Resignation
To: Theodore Ts'o <tytso@mit.edu>
Cc: Alissa Cooper <alissa@cooperw.in>, john@jlc.net, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d48f31058cc82052"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lTZqsBUcc1pS-Qp4vtxtuxFq2Hg>
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:01:00 -0000

On Wed, Jul 3, 2019 at 10:03 AM Theodore Ts'o <tytso@mit.edu> wrote:

> FWIW, my own interpretation of Ben and Alissa's intervention (and I
> speak as a former SAA) is that it sounded very much like what the
> "geek feminism" web sites frequently refer to as "tone policing"[1]
>
> [1] https://everydayfeminism.com/2015/12/tone-policing-and-privilege/


This is a thorny subject, and I don't want to derail the discussion too
much, but criticism of "tone policing" fails the symmetry test. Those who
engage in "tone policing" are equivalently engaging in "enforcing their
terms of engagement". If I don't want to have a conversation with angry
people, that's my choice. If you don't like it, find someone else to argue
with. That having been said, candor is absolutely necessary to getting good
technical outcomes.

I think the trick is figuring out how to be candid without being rude.
Offense is definitely a manifestation in the mind of the reader/listener,
so it's not entirely within the power of the writer/speaker to avoid
causing offense (nor, would I argue, should people walk around on eggshells
to avoid causing offense to the long tail), but certain modes of engagement
can certainly have a measurably negative effect on the standards process by
pushing out folks who would otherwise make valuable technical contributions
but who refuse to engage with those who employ invective as an everyday
tool. I don't think it's necessarily a race to the bottom (as a community
entirely comprising misanthropes will have a hard time propagating their
ideas outside of the group), but it's not clear the equilibrium reached
will be optimal.

Basically, my position is that contributors should make frank technical
judgments and use clear language without being jerks. There's definitely a
grey area, ripe for tussle, but as long as we don't stray too far to one
extreme, neither participation nor technical outcomes are likely to suffer
greatly.

Kyle