Re: [Gendispatch] Meetings summary

Jay Daley <jay@ietf.org> Wed, 14 October 2020 18:24 UTC

Return-Path: <jay@ietf.org>
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 ADB263A0FB9 for <gendispatch@ietfa.amsl.com>; Wed, 14 Oct 2020 11:24:51 -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, HTML_MESSAGE=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 h8KTBZ-Xx9ig; Wed, 14 Oct 2020 11:24:49 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 499DA3A0C4F; Wed, 14 Oct 2020 11:24:49 -0700 (PDT)
From: Jay Daley <jay@ietf.org>
Message-Id: <F25B1186-0DA8-4FD5-9FDB-5DA151EAECF0@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C7259E0C-1222-4A75-BFF0-F2D625F86268"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Thu, 15 Oct 2020 07:24:47 +1300
In-Reply-To: <0EE69F2A-6F1B-4F29-94B8-2978BB3E63AD@episteme.net>
Cc: gendispatch@ietf.org
To: Pete Resnick <resnick@episteme.net>
References: <B1075198-D4F5-498B-B16B-3081A9B07DDD@episteme.net> <0a2b6e3e-648f-ceec-90dd-9fd2487ab6db@cdt.org> <dc4c6c32-7fd0-8271-6801-b6f56eb26854@lounge.org> <C583F158-E31B-4D14-87F1-F4B9FFA0DA5C@ietf.org> <0EE69F2A-6F1B-4F29-94B8-2978BB3E63AD@episteme.net>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/JxNpUNUaNOnM75pF9yrYTGht4_E>
Subject: Re: [Gendispatch] Meetings summary
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: Wed, 14 Oct 2020 18:24:52 -0000

Hi Pete

Thank you for explaining that and please accept my apologies for not leaving this to you and Francesca to address.

Jay

> On 15/10/2020, at 5:42 AM, Pete Resnick <resnick@episteme.net> wrote:
> 
> Replying to Jay's message, but really this is to everyone and applies across WGs:
> 
> On 13 Oct 2020, at 19:06, Jay Daley wrote:
> 
>> Dan
>> 
>> Noting that I have absolutely no authority in this matter, either directly or indirectly, but that the emerging consensus is that I should be free to contribute to areas where I have no authority, I want to state that I think your message below has crossed a line of tolerable behaviour, even with a generous interpretation of "robust discourse".
> 
> Jay, there's nothing in your reply that I can really disagree with. However, when this kind of disruptive behavior happens on the list, the best plan of action is to drop a note to the chairs and let them address it. According to RFC 3934, the normal course of action is for the chairs to first talk to the person privately. Often, people do take it to heart and the behavior stops. (I always hope that doing so not only stops the behavior, but generates a public, "Sorry about that; didn't mean to be disruptive." Sometimes it happens, sometimes it doesn't.) Only if the behavior then continues do we get to the public warning or eventual suspension. While I appreciate that others publicly calling out bad behavior does show that others disagree with it too, it can lead to arguments on the list that are equally disruptive to getting work done.
> 
> Please give your chairs a chance to deal with disruptions on the list (in this WG or any other). I understand that it sometimes takes a bit of time for the chairs to get together to address these things (Francesca and I are in different time zones, so it took more than half a day for us to get our message together and sent out), but dealing with these things is (part of) why your chairs are here. Of course, if your chairs don't respond appropriately, there are other avenues (bringing it to the AD, bringing it to the Ombudsteam if the behavior is a bit more interpersonal) and you should feel free to use them. Doing so also gives the chairs a learning opportunity so they can address these things better in the future. But direct (and public) confrontations by other participants rarely lead to better behavior and work moving forward.
> 
> Again, I understand the good intentions of sending this sort of note, but in the long run I think having chairs deal with these sorts of incidents leads to better outcomes.
> 
> Thanks.
> 
> pr
> -- 
> Pete Resnick https://www.episteme.net/
> All connections to the world are tenuous at best
> 
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch
> 

-- 
Jay Daley
IETF Executive Director
jay@ietf.org