Re: [Terminology] Recent posts to the terminology mailing list
Nick Doty <npdoty@ischool.berkeley.edu> Fri, 05 November 2021 21:02 UTC
Return-Path: <npdoty@berkeley.edu>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA49C3A0E91 for <terminology@ietfa.amsl.com>; Fri, 5 Nov 2021 14:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=ischool-berkeley-edu.20210112.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 iIeFOl5EKBXS for <terminology@ietfa.amsl.com>; Fri, 5 Nov 2021 14:02:44 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 2CDC63A0E8D for <terminology@ietf.org>; Fri, 5 Nov 2021 14:02:44 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id g19so3928414pfb.8 for <terminology@ietf.org>; Fri, 05 Nov 2021 14:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ischool-berkeley-edu.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gTu29H4JqoX8Vr9hIP1xf8ZBi3GjrVlxxbRa700SwQc=; b=Yh+E/FOdYnwkUb4DtNU46AULVPTZoUOe6rRgk6ZPb4KxN6c6QXUogGV9R2qt+I+7Iv 6kgK0hTzqYlDYqcS2HT3x0INLm2e/Bm2nfdea4mhCSoLfWq6w7TzwTLSci+iijr94pJY KgmOHBWRFjqFtWnQRGVkzdEERaRWi9ym8aNIy4SmnCCvgU3D+qhLtiQBhXg+1TVd2l9l jp9m+iwnXKk1GHiAt2F1gkIi7CsGUdd69yq0zpVujWFwN/kTymUoEVvdrrmHpPtoSTbZ EfMgFE5ZOGJ/Jvlv0NQvypehWSC3pMVoUdJ4LnT++bwEpEkHzFv9djhsPNQxs9DLKXbS kVEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gTu29H4JqoX8Vr9hIP1xf8ZBi3GjrVlxxbRa700SwQc=; b=4Vz1zirqzn4so03sfld8UO+eDsioTR5xxrM8/eNrEc88qyvysaxNpFcjfjJyt7uu2L GN2dEWl2IioD100jlz2OtKRIUYQN7Ohtda9OIuFyJL22mf7vpYafRDqPxvt36dP856ad FSiVGctQMtY5SbyLClKpy3oOSEXm4JMddFcNjz7YSGzbJm169q3AWz+7qsYk++qxGM73 ZKrnZLq59YO22OTGtPKaKhKpCdNeTZJ/Dd1/Ca0+Tt5LcIvlHhuwLSa4jhV85l2Xrtik +ievrB0O4gvLb900FTSFh8c/AkRuE4vmrhTNrILEeFwb8MO+aUIUiYHlfU50OdbeLJ4i fANQ==
X-Gm-Message-State: AOAM532xWD6iDxKbcCIep1WbbZG0u2fNYd650+058CQVF7JKLW8QCTdy NUkb7Y2z8MHyJE/GROBcSpHBt4oh2cOFbKsufFWVIQ==
X-Google-Smtp-Source: ABdhPJxH9b+fjyixPJiJj/6yqI1AfZMjbJN+ybTFwlt5/AsY59Z9Gk6PiBA6GtoRwvuWERxM3XTZvCvET10eAoc4ywE=
X-Received: by 2002:a05:6a00:1511:b0:492:61fe:9fa6 with SMTP id q17-20020a056a00151100b0049261fe9fa6mr23033079pfu.57.1636146161766; Fri, 05 Nov 2021 14:02:41 -0700 (PDT)
MIME-Version: 1.0
References: <BY5PR11MB419686515616F100D00EA0AFB58D9@BY5PR11MB4196.namprd11.prod.outlook.com>
In-Reply-To: <BY5PR11MB419686515616F100D00EA0AFB58D9@BY5PR11MB4196.namprd11.prod.outlook.com>
From: Nick Doty <npdoty@ischool.berkeley.edu>
Date: Fri, 05 Nov 2021 17:02:30 -0400
Message-ID: <CAFfrZstPj8ZmQNrv5AG_u3soHsu0t=rKzc8OisFwpWtgz3GAhw@mail.gmail.com>
To: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>
Cc: "terminology@ietf.org" <terminology@ietf.org>, Lars Eggert <lars@eggert.org>, Sean Turner <sean@sn3rd.com>
Content-Type: multipart/alternative; boundary="000000000000c5fa2a05d010f67e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/QcEEvE1kUNCMUgmqczBJ1EY7LBE>
Subject: Re: [Terminology] Recent posts to the terminology mailing list
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2021 21:02:49 -0000
Hi Rob, On Thu, Nov 4, 2021 at 4:34 PM Rob Wilton (rwilton) <rwilton= 40cisco.com@dmarc.ietf.org> wrote: > Hi, > > I've recently joined Lars and Sean as a co-moderator for this list. > Thank you for helping with moderation of this list, which is needed. > I would like to send a blanket reminder to all subscribed to this mailing > list that the IETF goal is to make the Internet better. I believe that the > most effective way to achieve that is for all participants to communicate > in a constructive way that is respectful to other participants. Further, I > would like to add that I believe the vast majority of IETF participants > engage in such a way. > > In some cases, the recent postings to this mailing list have been neither > constructive nor respectful and I have contacted the individual(s) involved > to politely request that they moderate how they construct their messages. > > I see that there is no benefit in further discussing > draft-knodel-terminology on this list. As the ISE has made clear (as per > https://mailarchive.ietf.org/arch/msg/terminology/l4vjg55V6lgxB-Yn_IuPGnjoe9s/), > the decision as to whether to publish this draft is an ISE decision and > does not require or benefit from any form of IETF consensus or discussion. > > At the moment, I believe that the only terminology related work happening > in the IETF is the implementation of the IESG Statement on Inclusive > language, > https://www.ietf.org/about/groups/iesg/statements/on-inclusive-language/. > As far as I understand it, the current process is working well in a > reasonable and proportionate way. > > I would like to keep the terminology mailing list open to ensure that IETF > has a place for any necessary terminology related discussions, where IETF > participants are free to choose to subscribe or unsubscribe based on their > interest. > Can you update the listinfo page to clarify the current purpose of the mailing list and to identify the moderators of the list? Currently, that information is out of date or missing. The listinfo page indicates that this is the list of the TERM WG, which might indicate to subscribers that there are WG chairs who can follow BCP 94 in explicitly moderating the mailing list and stopping disruptive behavior. I don't have strong feelings either way, but I'm fine with keeping the list open for discussion of terminology questions, the IESG statement and how to make use of the NIST report. As I recall, it was used for that regarding NTP and interactions with IEEE, which seemed helpful. https://mailarchive.ietf.org/arch/msg/terminology/L517hr-i6qASoTDWbeuH23XSZvM/ On Fri, Nov 5, 2021 at 11:02 AM Rob Wilton (rwilton) <rwilton= 40cisco.com@dmarc.ietf.org> wrote: > My reasoning for wanting to keep the list open is not because I expect > much further discussion, but I would rather that any terminology related > discussion occurs on this list than end back on ietf@ietf.org, > particularly because it seems that this is an emotive topic and these > discussions unfortunately bring out uncivil behaviour from some people. I > see that having a separate list allows for such discussions to occur > (freedom of speech) without forcing the discussion onto the larger lists of > subscribers on ietf@ietf.org who are presumably less interested in these > discussions (freedom of listening to the free speech), given that > relatively few of the ietf@ietf.org subscribers are also subscribed to > the terminology list. > I hope we agree that uncivil, unconstructive, disrespectful behavior is unwelcome on IETF mailing lists whether the list has very many subscribers or is a smaller list focused on a particular topic. I do not subscribe to ietf@ietf.org as it's well-known that it regularly contains toxic discussion. I would like to continue to subscribe to and contribute to smaller mailing lists on work topics of interest, like this one. I do not believe the purpose of this list is to divert uncivil behavior from the ietf list. I'm not sure this is very directly related to freedom of speech, although that term can often be used in different senses. There are many outlets for publishing speech of all kinds, including insults towards individuals or groups one dislikes, on the Internet, among them blogs, newsletters and social media. But as you have noted, IETF mailing lists have more specific purposes and guidelines for conduct, as described in BCP 54, for example. > Having something like BCP45bis for all moderated lists would probably > generally be helpful for the IETF, but any of these process type documents > seem to take quite a lot of effort/energy to progress. But always happy if > someone from the community wants to try and pick this up and drive this, > presumably via Gendispatch. > My understanding was that BCP 54 applied to all IETF participation, including in-person and all IETF mailing lists. But if the scope of BCP 94 or BCP 25 are limited only to chartered WG mailing lists and BCP 45 is limited to the ietf@ietf.org list, then it does seem like there is an important gap that needs to be filled so that all our mailing lists can be regularly moderated without always needing direct IESG involvement. > In terms of my role, no I'm not an SAA, just a list owner with a role to > moderate the list alongside Lars and Sean. I was added by Lars because we > thought that he was the only list owner at the time and thought that it > would be helpful if the moderation was handled by someone else. I.e., > generally, I find that the IESG members go out of their way to try and be > impartial and be seen to be impartial. We subsequently found that Sean was > also a moderator. Hopefully, everyone will be constructive and respectful > to each other and no further moderation will be necessary. > If list moderators are documented publicly somewhere, I think that would help with this confusion. Thanks again, Nick
- [Terminology] Recent posts to the terminology mai… Rob Wilton (rwilton)
- Re: [Terminology] Recent posts to the terminology… lloydwood@users.sourceforge.net
- Re: [Terminology] Recent posts to the terminology… Rob Wilton (rwilton)
- Re: [Terminology] Recent posts to the terminology… Dan Harkins
- Re: [Terminology] Recent posts to the terminology… Nick Doty
- Re: [Terminology] Recent posts to the terminology… Lloyd W
- Re: [Terminology] Recent posts to the terminology… Dan Harkins
- Re: [Terminology] Recent posts to the terminology… Bron Gondwana
- Re: [Terminology] Recent posts to the terminology… S Moonesamy
- Re: [Terminology] Recent posts to the terminology… S Moonesamy
- [Terminology] Rejecting kings and such Eliot Lear
- Re: [Terminology] Recent posts to the terminology… Vittorio Bertola