Re: BCP 83 PR actions and new media

Samuel Weiler <weiler@csail.mit.edu> Thu, 10 November 2022 10:49 UTC

Return-Path: <weiler@csail.mit.edu>
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 8619AC14CF00; Thu, 10 Nov 2022 02:49:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.244
X-Spam-Level:
X-Spam-Status: No, score=-1.244 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJw59TZkEp1T; Thu, 10 Nov 2022 02:49:33 -0800 (PST)
Received: from cyrus.watson.org (cyrus.watson.org [147.160.157.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9EEC14CEFC; Thu, 10 Nov 2022 02:49:32 -0800 (PST)
Received: from dhcp-8c65.meeting.ietf.org (dhcp-8c65.meeting.ietf.org [31.133.140.101]) by cyrus.watson.org (Postfix) with ESMTPSA id B21668EE5B; Thu, 10 Nov 2022 10:49:31 +0000 (UTC)
Date: Thu, 10 Nov 2022 05:49:30 -0500
From: Samuel Weiler <weiler@csail.mit.edu>
To: iesg@ietf.org
cc: ietf@ietf.org
Subject: Re: BCP 83 PR actions and new media
In-Reply-To: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org>
Message-ID: <6a4f347a-673e-5a2f-8864-5a26ff88e940@csail.mit.edu>
References: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oxL0jbws1pY4yEGjvT9o7iou0CE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Thu, 10 Nov 2022 10:49:34 -0000

I may have been unclear, or Keith's question might have dragged the 
discussion in a different direction.

On Wed, 9 Nov 2022, Samuel Weiler wrote:

> Do PR actions also apply to other-than-email IETF communications such as 
> Github, Slack, Zulip, and whatever new collaboration technologies we adopt in 
> the future?

I'm asking if the penalty imposed by a PR action also applies to 
other-than-email IETF communications, e.g. may a WG chair block 
someone already subject to a PR action from posting in a Github 
repository?

> I propose that they should and that we should not need to revise BCP 83 every 
> time we add a new collaboration technology, and I'm hoping you agree with me.

While the language of 3683 was written before we were using many of 
these other tools, this seems like the obvious interpretation.

-- Sam