Re: [Gendispatch] draft charter text: terminology-related WG

Fernando Gont <fernando@gont.com.ar> Fri, 12 February 2021 21:29 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 190A53A0EEF; Fri, 12 Feb 2021 13:29:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ccD-8epCRuTX; Fri, 12 Feb 2021 13:29:12 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08CD53A0EEC; Fri, 12 Feb 2021 13:29:04 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:4181:442:5061:d73f] (unknown [IPv6:2800:810:464:2b9:4181:442:5061:d73f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 22BB4283DC2; Fri, 12 Feb 2021 21:29:00 +0000 (UTC)
To: John Levine <johnl@taugh.com>, gendispatch@ietf.org
Cc: vittorio.bertola@open-xchange.com, Keith Moore <moore@network-heretics.com>
References: <20210212205351.27E4B6DDB49D@ary.qy>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <3b4ea13c-0743-c882-7fc0-1fe7288f6d07@gont.com.ar>
Date: Fri, 12 Feb 2021 18:24:01 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210212205351.27E4B6DDB49D@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/xqUqQXMxVx-QoKM9sRHEmPScQU8>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 21:29:15 -0000

On 12/2/21 17:53, John Levine wrote:
> In article <968461968.13727.1613122672205@appsuite-gw1.open-xchange.com> you write:
>> However, what I really care about is that any effort to improve language inclusiveness is actually inclusive. Whenever this
>> discussion comes up, it focuses regularly just on a handful of terms that are deemed offensive to one specific ethnicity in one
>> specific country. While of course this is not the intention, this often feels exclusive to people from other countries and other
>> ethnicities; this became apparent during some past discussions on the main IETF list.
> 
> I share the concern that this is an exercise in which a bunch of
> mostly rich white people are trying to guess how people who are not
> rich and white might feel. 

I couldn't have phrased it better than that.

(Would also argue that then said group would probably also later claim 
that the IETF cares about inclusiveness).



> While I agree it is an important topic to
> address, it is my strong impression that most of the obvious things
> one might do, e.g., making lists of words to avoid, are not actually
> productive.

Well, paraphrasing Lewis Carrol, it all depends where one wants to go. :-)

Focusing the effort of inclusiveness on terminology seems to be the sort 
of thing that essentially doesn't affect the status quo at all -- so 
that probably tells you how much it'll do for inclusiveness.


Note: I don't mind it. However, pretending that one is really helping 
the situation by deprecating/banning a list of words, while 
well-intentioned, seems to me like really ignoring the problem.


As a hint, this work: draft-kuehlewind-shmoo-remote-fee does, IMO, more 
for many axis of inclusiveness than any specific recommnendation on 
language.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1