From 65562d03b903df327c3f64b2d7de64aef48431be Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Wed, 12 Jun 2024 15:06:56 -0400 Subject: [PATCH 1/5] add a "last-call process" document --- README.md | 3 +++ last-call.md | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 last-call.md diff --git a/README.md b/README.md index 2f8ee9e..4fb8bb8 100644 --- a/README.md +++ b/README.md @@ -3,10 +3,13 @@ This is a repository of guidelines, procedures, and templates used by the IETF Moderators team (formerly called Sergeants-at-Arms(SAA)). The goal of the Moderators team is to foster an environment of digntity, decency, and respect on ietf@ietf.org where everyone feels welcome to contribute. +This repository also contains [guideliness for the last-call@ietf.org mailing list](last-call.md). + While [RFC 9245] creates the role of Moderators for the ietf@ietf.org mailing list, the guidance for inappropriate postings and the actions to be taken are not well-defined. This repository aims to address this lack of clarity. * [Standard Operating Procedures](sop.md) outlines how and when the Moderators engages with inappropriate postings, including escalation paths. * [Templates](email-templates) that engagement messages from the Moderators adhere to. +* [Last Call Templates](last-call-templates) that engagement messages from the Last Call team adhere to. * A definition of [Uncivil Commentary](unprofessional-commentary.md) the Moderators follows. This set of documents is considered a work-in-progress, and is expected to evolve to meet the needs of the IETF. diff --git a/last-call.md b/last-call.md new file mode 100644 index 0000000..54ce40a --- /dev/null +++ b/last-call.md @@ -0,0 +1,32 @@ +# Last Call Standard Operating Proceedure + +## Personnel + +The Last Call team can be reached by emailing [last-call-owner@ietf.org](mailto:last-call-owner@ietf.org). + +## General operations + +The Last Call team strive to monitor all postings on last-call@ietf.org on a daily basis. The IETF Chair also monitors the list but may not be in a position to read each message or monitor every day. + +The rules for engagement are similar to those of ietf@ietf.org; so everything from the code of conduct there also applies to this list, with stronger content restriction - the Last Call list is specifically for discussion of documents in last-call and other IESG activities. + +## Escalation ladder for handling issues other than "off topic" + +The Last Call team use the same process as the Moderators of the ietf@ietf.org mailing list as described in [their sop](sop.md). + +## Handling of conversations drifting off topic + +The vast majority of discussions on the last-call mailing list are related to drafts which are in IETF-wide last call and come from a specific area. When these get too complex; the Last Call team may ask the responsible area director to guide the conversation back to the source working group, or ask those involved to take a pause and give the authors a chance to respond. + +In general, participants are asked to address their feedback to the authors of documents or the escalation path (chairs, area directors, assigned reviewers, and the IETF chair). If a conversation becomes heated between participants who are not one of those parties, the Last Call team may intervene and ask people to wait for author feedback before continuing the conversation. + +### Posting Rights actions + +A specific area that commonly causes significant traffic to the last-call list are BCP 83 posting rights actions. + +If these get out of hand, the last-call team will remind contributors that the purpose of a Posting Rights last call is to inform the IESG, and to restrict their contributions to directly address the specific PR action, and to address their contributions to the IESG, not to other participants on the mailing list. + +## Finding an appropriate forum + +In many cases, the correct next location is the ietf@ietf.org list for conversations which have drifted out of last-call territory, however the Last Call team recommends that participants try to identify a more specific location. It is acceptable for participants in a conversation that has already kicked-off on the last-call list to cross-post a single message advising the list of the location where the conversation has moved. + From e0414df134f4b107221d325fb28293cf3bee9d0a Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Wed, 12 Jun 2024 15:28:44 -0400 Subject: [PATCH 2/5] copy email-templates to last-call templates --- last-call-templates/PR-message-to-list.txt | 12 +++++++ .../PR-moderation-message-to-list.txt | 14 ++++++++ last-call-templates/README.md | 36 +++++++++++++++++++ last-call-templates/announcements-to-list.txt | 10 ++++++ last-call-templates/announcements.txt | 14 ++++++++ last-call-templates/first-message-to-list.txt | 12 +++++++ last-call-templates/first-message.txt | 21 +++++++++++ .../first-moderation-message-to-list.txt | 12 +++++++ .../first-moderation-thread-message.txt | 18 ++++++++++ .../first-pattern-of-abuse-message.txt | 21 +++++++++++ last-call-templates/forum-to-list.txt | 13 +++++++ last-call-templates/out-of-scope.txt | 15 ++++++++ .../second-moderation-thread-message.txt | 16 +++++++++ .../second-pattern-of-abuse-message.txt | 19 ++++++++++ .../unsolicited-email-to-list.txt | 10 ++++++ last-call-templates/unsolicited-email.txt | 14 ++++++++ 16 files changed, 257 insertions(+) create mode 100644 last-call-templates/PR-message-to-list.txt create mode 100644 last-call-templates/PR-moderation-message-to-list.txt create mode 100644 last-call-templates/README.md create mode 100644 last-call-templates/announcements-to-list.txt create mode 100644 last-call-templates/announcements.txt create mode 100644 last-call-templates/first-message-to-list.txt create mode 100644 last-call-templates/first-message.txt create mode 100644 last-call-templates/first-moderation-message-to-list.txt create mode 100644 last-call-templates/first-moderation-thread-message.txt create mode 100644 last-call-templates/first-pattern-of-abuse-message.txt create mode 100644 last-call-templates/forum-to-list.txt create mode 100644 last-call-templates/out-of-scope.txt create mode 100644 last-call-templates/second-moderation-thread-message.txt create mode 100644 last-call-templates/second-pattern-of-abuse-message.txt create mode 100644 last-call-templates/unsolicited-email-to-list.txt create mode 100644 last-call-templates/unsolicited-email.txt diff --git a/last-call-templates/PR-message-to-list.txt b/last-call-templates/PR-message-to-list.txt new file mode 100644 index 0000000..05de1f2 --- /dev/null +++ b/last-call-templates/PR-message-to-list.txt @@ -0,0 +1,12 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the ietf@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message 1] +[3] [LINK to specific message 2] +[4] https://www.rfc-editor.org/rfc/rfc9245.html +[5] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/PR-moderation-message-to-list.txt b/last-call-templates/PR-moderation-message-to-list.txt new file mode 100644 index 0000000..14cd58c --- /dev/null +++ b/last-call-templates/PR-moderation-message-to-list.txt @@ -0,0 +1,14 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the ietf@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [5] and our SOP [6]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message 1] +[3] [LINK to specific message 2] +[4] [LINK to the IETF chair message to the list] +[5] https://www.rfc-editor.org/rfc/rfc9245.html +[6] https://github.com/ietf/Moderators/blob/main/sop.md + diff --git a/last-call-templates/README.md b/last-call-templates/README.md new file mode 100644 index 0000000..db184c2 --- /dev/null +++ b/last-call-templates/README.md @@ -0,0 +1,36 @@ +# Email Templates + +These are the templates used by the Moderators to communicate with individuals and the list about an incident, grouped by escalation level, then by category (where applicable) and intended recipient. + +## Level 0: Initial suggestion + +* Appropriate Forum + - [To List](./forum-to-list.txt) +* Unauthorized Announcements + - [To sender](./announcements.txt) + - [To list](./announcements-to-list.txt) +* Unsolicited Email + - [To sender](./unsolicited-email.txt) + - [To list](./unsolicited-email-to-list.txt) +* Uncivil Commentary and Disruptive Behavior + - [To sender](./first-message.txt) +* Out of Scope + - [To sender](./out-of-scope.txt) + +## Level 1: Cooling off period +### Uncivil Commentry +* [To sender](./first-pattern-of-abuse-message.txt) +* [To list](./first-message-to-list.txt) + +### Moderation +* [To sender](./first-moderation-thread-message.txt) +* [To list](./first-moderation-message-to-list.txt) + +## Level 2: Temporary posting rights restriction +### Uncivil Commentry +* [To sender](./second-pattern-of-abuse-message.txt) +* [To list](./PR-message-to-list.txt) + +### Moderation +* [To sender](./second-moderation-thread-message.txt) +* [To list](./PR-moderation-message-to-list.txt) diff --git a/last-call-templates/announcements-to-list.txt b/last-call-templates/announcements-to-list.txt new file mode 100644 index 0000000..76efb3c --- /dev/null +++ b/last-call-templates/announcements-to-list.txt @@ -0,0 +1,10 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message 1] +[3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/announcements.txt b/last-call-templates/announcements.txt new file mode 100644 index 0000000..24d072a --- /dev/null +++ b/last-call-templates/announcements.txt @@ -0,0 +1,14 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. + +We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. + +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying ietf@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message] +[3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-message-to-list.txt b/last-call-templates/first-message-to-list.txt new file mode 100644 index 0000000..78de3c5 --- /dev/null +++ b/last-call-templates/first-message-to-list.txt @@ -0,0 +1,12 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message 1] +[3] [LINK to specific message 2] +[4] https://www.rfc-editor.org/rfc/rfc9245.html +[5] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/first-message.txt b/last-call-templates/first-message.txt new file mode 100644 index 0000000..34ac2b1 --- /dev/null +++ b/last-call-templates/first-message.txt @@ -0,0 +1,21 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. + +We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: + +[LANGUAGE] + +which the Moderators team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on ietf@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. + +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. If we see such a pattern emerge, we will get back in touch with you to suggest that you voluntarily take a break from posting to the list. + +If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] https://www.rfc-editor.org/rfc/rfc9245.html +[3] [LINK to specific message] +[4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/first-moderation-message-to-list.txt b/last-call-templates/first-moderation-message-to-list.txt new file mode 100644 index 0000000..275929e --- /dev/null +++ b/last-call-templates/first-moderation-message-to-list.txt @@ -0,0 +1,12 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to ietf@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF discussion list charter [4] and our SOP [5]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message] +[3] [LINK to the IETF chair message to the list] +[4] https://www.rfc-editor.org/rfc/rfc9245.html +[5] https://github.com/ietf/Moderators/blob/main/sop.md diff --git a/last-call-templates/first-moderation-thread-message.txt b/last-call-templates/first-moderation-thread-message.txt new file mode 100644 index 0000000..a9f3a3f --- /dev/null +++ b/last-call-templates/first-moderation-thread-message.txt @@ -0,0 +1,18 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. + +We are reaching out to you because of your recent message to ietf@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. + +We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the discussion on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to ietf@ietf.org as per our SOP [5]. We will be notifying ietf@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to ietf@ietf.org for 14 days. + +If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] https://www.rfc-editor.org/rfc/rfc9245.html +[3] [LINK to specific message] +[4] [LINK to the IETF chair message to the list] +[5] https://github.com/ietf/Moderators/blob/main/sop.md diff --git a/last-call-templates/first-pattern-of-abuse-message.txt b/last-call-templates/first-pattern-of-abuse-message.txt new file mode 100644 index 0000000..033ecb5 --- /dev/null +++ b/last-call-templates/first-pattern-of-abuse-message.txt @@ -0,0 +1,21 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. + +We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: + +[LANGUAGE] + +which the Moderators team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on ietf@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. + +We are concerned that this message is part of an emerging pattern of abuse on your part, given our previous correspondence with you on [DATE]. As such, we request that you take a voluntary 5-day break from posting to ietf@ietf.org. We will be notifying ietf@ietf.org that we have been in touch with you. If we continue to see this pattern, we will consider temporarily restricting your posting rights to ietf@ietf.org. + +If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] https://www.rfc-editor.org/rfc/rfc9245.html +[3] [LINK to specific message] +[4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/forum-to-list.txt b/last-call-templates/forum-to-list.txt new file mode 100644 index 0000000..e67c752 --- /dev/null +++ b/last-call-templates/forum-to-list.txt @@ -0,0 +1,13 @@ +Hi all, + +We wanted to let the list know that the Moderators team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF discussion list charter [4], we suggest that the discussions should be moved to the more specific forum identified. + +[The Moderators team has been in touch with the [LIST] administers off-list.] (if required) + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to thread] +[3] [LINK to join LIST] +[4] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/out-of-scope.txt b/last-call-templates/out-of-scope.txt new file mode 100644 index 0000000..d5af916 --- /dev/null +++ b/last-call-templates/out-of-scope.txt @@ -0,0 +1,15 @@ + +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. + +We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message is not in scope of the IETF Discussion List Charter as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. + +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message] +[3] https://www.rfc-editor.org/rfc/rfc9245.html \ No newline at end of file diff --git a/last-call-templates/second-moderation-thread-message.txt b/last-call-templates/second-moderation-thread-message.txt new file mode 100644 index 0000000..7520368 --- /dev/null +++ b/last-call-templates/second-moderation-thread-message.txt @@ -0,0 +1,16 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. + +We are reaching out to you because of your recent message to ietf@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. + +Given our correspondence with you on [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify ietf@ietf.org of the restriction as per our SOP [5]. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] https://www.rfc-editor.org/rfc/rfc9245.html +[3] [LINK to specific message] +[4] [LINK to the IETF chair message to the list] +[5] https://github.com/ietf/Moderators/blob/main/sop.md diff --git a/last-call-templates/second-pattern-of-abuse-message.txt b/last-call-templates/second-pattern-of-abuse-message.txt new file mode 100644 index 0000000..9d34925 --- /dev/null +++ b/last-call-templates/second-pattern-of-abuse-message.txt @@ -0,0 +1,19 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. + +We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: + +[LANGUAGE] + +which the Moderators team considers uncivil commentary [4] for [REASON]. + +Given our correspondence with you on [DATE] and [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify ietf@ietf.org of the restriction. We remain happy to discuss suggestions for how to convey your messages in an appropriate way if you would like to discuss that during this time. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] https://www.rfc-editor.org/rfc/rfc9245.html +[3] [LINK to specific message] +[4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/unsolicited-email-to-list.txt b/last-call-templates/unsolicited-email-to-list.txt new file mode 100644 index 0000000..5cc63f5 --- /dev/null +++ b/last-call-templates/unsolicited-email-to-list.txt @@ -0,0 +1,10 @@ +Hi all, + +We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings of unsolicited bulk email. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message 1] +[3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/unsolicited-email.txt b/last-call-templates/unsolicited-email.txt new file mode 100644 index 0000000..765ba3d --- /dev/null +++ b/last-call-templates/unsolicited-email.txt @@ -0,0 +1,14 @@ +Hi [NAME], + +I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. + +We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message includes unsolicited bulk email as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. + +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying ietf@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. + +Thanks, +[NAME] on behalf of the Moderators team for ietf@ietf.org + +[1] https://www.ietf.org/how/lists/discussion/ +[2] [LINK to specific message] +[3] https://www.rfc-editor.org/rfc/rfc9245.html From b573f7cfd7dafd6eafe60b11f34557561114912d Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Wed, 12 Jun 2024 15:32:20 -0400 Subject: [PATCH 3/5] Rename list and team --- last-call-templates/PR-message-to-list.txt | 4 ++-- .../PR-moderation-message-to-list.txt | 4 ++-- last-call-templates/README.md | 2 +- last-call-templates/announcements-to-list.txt | 4 ++-- last-call-templates/announcements.txt | 8 ++++---- last-call-templates/first-message-to-list.txt | 4 ++-- last-call-templates/first-message.txt | 10 +++++----- .../first-moderation-message-to-list.txt | 4 ++-- .../first-moderation-thread-message.txt | 10 +++++----- .../first-pattern-of-abuse-message.txt | 12 ++++++------ last-call-templates/forum-to-list.txt | 6 +++--- last-call-templates/out-of-scope.txt | 8 ++++---- .../second-moderation-thread-message.txt | 8 ++++---- .../second-pattern-of-abuse-message.txt | 10 +++++----- last-call-templates/unsolicited-email-to-list.txt | 4 ++-- last-call-templates/unsolicited-email.txt | 8 ++++---- 16 files changed, 53 insertions(+), 53 deletions(-) diff --git a/last-call-templates/PR-message-to-list.txt b/last-call-templates/PR-message-to-list.txt index 05de1f2..0e8faff 100644 --- a/last-call-templates/PR-message-to-list.txt +++ b/last-call-templates/PR-message-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the ietf@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message 1] diff --git a/last-call-templates/PR-moderation-message-to-list.txt b/last-call-templates/PR-moderation-message-to-list.txt index 14cd58c..046d39e 100644 --- a/last-call-templates/PR-moderation-message-to-list.txt +++ b/last-call-templates/PR-moderation-message-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the ietf@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [5] and our SOP [6]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [5] and our SOP [6]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message 1] diff --git a/last-call-templates/README.md b/last-call-templates/README.md index db184c2..cb86fbb 100644 --- a/last-call-templates/README.md +++ b/last-call-templates/README.md @@ -1,6 +1,6 @@ # Email Templates -These are the templates used by the Moderators to communicate with individuals and the list about an incident, grouped by escalation level, then by category (where applicable) and intended recipient. +These are the templates used by the Last Call team to communicate with individuals and the list about an incident, grouped by escalation level, then by category (where applicable) and intended recipient. ## Level 0: Initial suggestion diff --git a/last-call-templates/announcements-to-list.txt b/last-call-templates/announcements-to-list.txt index 76efb3c..cb74d9b 100644 --- a/last-call-templates/announcements-to-list.txt +++ b/last-call-templates/announcements-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message 1] diff --git a/last-call-templates/announcements.txt b/last-call-templates/announcements.txt index 24d072a..76ee879 100644 --- a/last-call-templates/announcements.txt +++ b/last-call-templates/announcements.txt @@ -1,13 +1,13 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1]. -We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. +We are reaching out to you because of your recent message to last-call@ietf.org [2]. The message includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. Please try to avoid sending these messages on last-call@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. -We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying ietf@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying last-call@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to last-call@ietf.org. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message] diff --git a/last-call-templates/first-message-to-list.txt b/last-call-templates/first-message-to-list.txt index 78de3c5..48fe413 100644 --- a/last-call-templates/first-message-to-list.txt +++ b/last-call-templates/first-message-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message 1] diff --git a/last-call-templates/first-message.txt b/last-call-templates/first-message.txt index 34ac2b1..4a7126a 100644 --- a/last-call-templates/first-message.txt +++ b/last-call-templates/first-message.txt @@ -1,19 +1,19 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1] and [2]. -We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: +We are reaching out to you because of your recent message to last-call@ietf.org [3]. The message contained the following language: [LANGUAGE] -which the Moderators team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on ietf@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. +which the Last Call team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on last-call@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. If we see such a pattern emerge, we will get back in touch with you to suggest that you voluntarily take a break from posting to the list. -If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. +If you wish for us to make this message public, please let us know and we will re-send it with last-call@ietf.org on cc. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-moderation-message-to-list.txt b/last-call-templates/first-moderation-message-to-list.txt index 275929e..cb572be 100644 --- a/last-call-templates/first-moderation-message-to-list.txt +++ b/last-call-templates/first-moderation-message-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to ietf@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF discussion list charter [4] and our SOP [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to last-call@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF discussion list charter [4] and our SOP [5]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message] diff --git a/last-call-templates/first-moderation-thread-message.txt b/last-call-templates/first-moderation-thread-message.txt index a9f3a3f..8440451 100644 --- a/last-call-templates/first-moderation-thread-message.txt +++ b/last-call-templates/first-moderation-thread-message.txt @@ -1,15 +1,15 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1] and [2]. -We are reaching out to you because of your recent message to ietf@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. +We are reaching out to you because of your recent message to last-call@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. -We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the discussion on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to ietf@ietf.org as per our SOP [5]. We will be notifying ietf@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to ietf@ietf.org for 14 days. +We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the discussion on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org as per our SOP [5]. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to last-call@ietf.org for 14 days. -If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. +If you wish for us to make this message public, please let us know and we will re-send it with last-call@ietf.org on cc. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-pattern-of-abuse-message.txt b/last-call-templates/first-pattern-of-abuse-message.txt index 033ecb5..3c9df6e 100644 --- a/last-call-templates/first-pattern-of-abuse-message.txt +++ b/last-call-templates/first-pattern-of-abuse-message.txt @@ -1,19 +1,19 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1] and [2]. -We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: +We are reaching out to you because of your recent message to last-call@ietf.org [3]. The message contained the following language: [LANGUAGE] -which the Moderators team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on ietf@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. +which the Last Call team considers uncivil commentary [4] for [REASON]. Please try to avoid using this kind of language on last-call@ietf.org in the future. We are happy to discuss suggestions for how to convey the same message in an appropriate way if you would like to discuss that. -We are concerned that this message is part of an emerging pattern of abuse on your part, given our previous correspondence with you on [DATE]. As such, we request that you take a voluntary 5-day break from posting to ietf@ietf.org. We will be notifying ietf@ietf.org that we have been in touch with you. If we continue to see this pattern, we will consider temporarily restricting your posting rights to ietf@ietf.org. +We are concerned that this message is part of an emerging pattern of abuse on your part, given our previous correspondence with you on [DATE]. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will consider temporarily restricting your posting rights to last-call@ietf.org. -If you wish for us to make this message public, please let us know and we will re-send it with ietf@ietf.org on cc. +If you wish for us to make this message public, please let us know and we will re-send it with last-call@ietf.org on cc. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/forum-to-list.txt b/last-call-templates/forum-to-list.txt index e67c752..a005b14 100644 --- a/last-call-templates/forum-to-list.txt +++ b/last-call-templates/forum-to-list.txt @@ -1,11 +1,11 @@ Hi all, -We wanted to let the list know that the Moderators team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF discussion list charter [4], we suggest that the discussions should be moved to the more specific forum identified. +We wanted to let the list know that the Last Call team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF discussion list charter [4], we suggest that the discussions should be moved to the more specific forum identified. -[The Moderators team has been in touch with the [LIST] administers off-list.] (if required) +[The Last Call team has been in touch with the [LIST] administers off-list.] (if required) Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to thread] diff --git a/last-call-templates/out-of-scope.txt b/last-call-templates/out-of-scope.txt index d5af916..9347963 100644 --- a/last-call-templates/out-of-scope.txt +++ b/last-call-templates/out-of-scope.txt @@ -1,14 +1,14 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1]. -We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message is not in scope of the IETF Discussion List Charter as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. +We are reaching out to you because of your recent message to last-call@ietf.org [2]. The message is not in scope of the IETF Discussion List Charter as per [3]. Please try to avoid sending these messages on last-call@ietf.org in the future. -We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. If a pattern emerges, we will consider temporarily restricting your posting rights to last-call@ietf.org. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message] diff --git a/last-call-templates/second-moderation-thread-message.txt b/last-call-templates/second-moderation-thread-message.txt index 7520368..1d0ca61 100644 --- a/last-call-templates/second-moderation-thread-message.txt +++ b/last-call-templates/second-moderation-thread-message.txt @@ -1,13 +1,13 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1] and [2]. -We are reaching out to you because of your recent message to ietf@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. +We are reaching out to you because of your recent message to last-call@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. -Given our correspondence with you on [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify ietf@ietf.org of the restriction as per our SOP [5]. +Given our correspondence with you on [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify last-call@ietf.org of the restriction as per our SOP [5]. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/second-pattern-of-abuse-message.txt b/last-call-templates/second-pattern-of-abuse-message.txt index 9d34925..b1fd7ae 100644 --- a/last-call-templates/second-pattern-of-abuse-message.txt +++ b/last-call-templates/second-pattern-of-abuse-message.txt @@ -1,17 +1,17 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1] and [2]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1] and [2]. -We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language: +We are reaching out to you because of your recent message to last-call@ietf.org [3]. The message contained the following language: [LANGUAGE] -which the Moderators team considers uncivil commentary [4] for [REASON]. +which the Last Call team considers uncivil commentary [4] for [REASON]. -Given our correspondence with you on [DATE] and [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify ietf@ietf.org of the restriction. We remain happy to discuss suggestions for how to convey your messages in an appropriate way if you would like to discuss that during this time. +Given our correspondence with you on [DATE] and [DATE], we believe you are engaging in a pattern of abuse that warrants a temporary restriction of your posting rights. Your posting rights will be restricted for the next 14 days and we will notify last-call@ietf.org of the restriction. We remain happy to discuss suggestions for how to convey your messages in an appropriate way if you would like to discuss that during this time. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/unsolicited-email-to-list.txt b/last-call-templates/unsolicited-email-to-list.txt index 5cc63f5..d3c04e8 100644 --- a/last-call-templates/unsolicited-email-to-list.txt +++ b/last-call-templates/unsolicited-email-to-list.txt @@ -1,9 +1,9 @@ Hi all, -We wanted to let the list know that the Moderators team for ietf@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings of unsolicited bulk email. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings of unsolicited bulk email. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message 1] diff --git a/last-call-templates/unsolicited-email.txt b/last-call-templates/unsolicited-email.txt index 765ba3d..0150930 100644 --- a/last-call-templates/unsolicited-email.txt +++ b/last-call-templates/unsolicited-email.txt @@ -1,13 +1,13 @@ Hi [NAME], -I am writing to you on behalf of the Moderators team for ietf@ietf.org. This message has been vetted with others on the Moderators team, which is described in more detail at [1]. +I am writing to you on behalf of the Team for last-call@ietf.org. This message has been vetted with others on the Last Call team, which is described in more detail at [1]. -We are reaching out to you because of your recent message to ietf@ietf.org [2]. The message includes unsolicited bulk email as per [3]. Please try to avoid sending these messages on ietf@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. +We are reaching out to you because of your recent message to last-call@ietf.org [2]. The message includes unsolicited bulk email as per [3]. Please try to avoid sending these messages on last-call@ietf.org in the future. You can reach the IETF chair at chair@ietf.org to seek approval before sending. -We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying ietf@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to ietf@ietf.org. +We consider this an initial suggestion. We do not believe your message is part of a pattern of abuse that would warrant the restriction of your posting rights. We will be notifying last-call@ietf.org that we have been in touch with you. If a pattern emerges, we will consider temporarily restricting your posting rights to last-call@ietf.org. Thanks, -[NAME] on behalf of the Moderators team for ietf@ietf.org +[NAME] on behalf of the Team for last-call@ietf.org [1] https://www.ietf.org/how/lists/discussion/ [2] [LINK to specific message] From 9fcbc469611027adf25f3b112e8bc7c4a406372a Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Wed, 12 Jun 2024 15:34:07 -0400 Subject: [PATCH 4/5] update list location --- last-call-templates/PR-message-to-list.txt | 4 ++-- last-call-templates/PR-moderation-message-to-list.txt | 4 ++-- last-call-templates/announcements-to-list.txt | 4 ++-- last-call-templates/announcements.txt | 2 +- last-call-templates/first-message-to-list.txt | 4 ++-- last-call-templates/first-message.txt | 2 +- last-call-templates/first-moderation-message-to-list.txt | 4 ++-- last-call-templates/first-moderation-thread-message.txt | 4 ++-- last-call-templates/first-pattern-of-abuse-message.txt | 2 +- last-call-templates/forum-to-list.txt | 4 ++-- last-call-templates/out-of-scope.txt | 2 +- last-call-templates/second-moderation-thread-message.txt | 2 +- last-call-templates/second-pattern-of-abuse-message.txt | 2 +- last-call-templates/unsolicited-email-to-list.txt | 4 ++-- last-call-templates/unsolicited-email.txt | 2 +- 15 files changed, 23 insertions(+), 23 deletions(-) diff --git a/last-call-templates/PR-message-to-list.txt b/last-call-templates/PR-message-to-list.txt index 0e8faff..b0e668c 100644 --- a/last-call-templates/PR-message-to-list.txt +++ b/last-call-templates/PR-message-to-list.txt @@ -1,11 +1,11 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF list charter [4] and avoid postings that include uncivil commentary [5]. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message 1] [3] [LINK to specific message 2] [4] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/PR-moderation-message-to-list.txt b/last-call-templates/PR-moderation-message-to-list.txt index 046d39e..02b4fdf 100644 --- a/last-call-templates/PR-moderation-message-to-list.txt +++ b/last-call-templates/PR-moderation-message-to-list.txt @@ -1,11 +1,11 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF discussion list charter [5] and our SOP [6]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days. We encourage everyone to review the IETF list charter [5] and our SOP [6]. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message 1] [3] [LINK to specific message 2] [4] [LINK to the IETF chair message to the list] diff --git a/last-call-templates/announcements-to-list.txt b/last-call-templates/announcements-to-list.txt index cb74d9b..d705278 100644 --- a/last-call-templates/announcements-to-list.txt +++ b/last-call-templates/announcements-to-list.txt @@ -1,10 +1,10 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message 1] [3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/announcements.txt b/last-call-templates/announcements.txt index 76ee879..2a98fec 100644 --- a/last-call-templates/announcements.txt +++ b/last-call-templates/announcements.txt @@ -9,6 +9,6 @@ We consider this an initial suggestion. We do not believe your message is part o Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message] [3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-message-to-list.txt b/last-call-templates/first-message-to-list.txt index 48fe413..97b31af 100644 --- a/last-call-templates/first-message-to-list.txt +++ b/last-call-templates/first-message-to-list.txt @@ -1,11 +1,11 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF list charter [4] and avoid postings that include uncivil commentary [5]. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message 1] [3] [LINK to specific message 2] [4] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-message.txt b/last-call-templates/first-message.txt index 4a7126a..72e2b13 100644 --- a/last-call-templates/first-message.txt +++ b/last-call-templates/first-message.txt @@ -15,7 +15,7 @@ If you wish for us to make this message public, please let us know and we will r Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] https://www.rfc-editor.org/rfc/rfc9245.html [3] [LINK to specific message] [4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/first-moderation-message-to-list.txt b/last-call-templates/first-moderation-message-to-list.txt index cb572be..b96b719 100644 --- a/last-call-templates/first-moderation-message-to-list.txt +++ b/last-call-templates/first-moderation-message-to-list.txt @@ -1,11 +1,11 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to last-call@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF discussion list charter [4] and our SOP [5]. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to last-call@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF list charter [4] and our SOP [5]. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message] [3] [LINK to the IETF chair message to the list] [4] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/first-moderation-thread-message.txt b/last-call-templates/first-moderation-thread-message.txt index 8440451..74e1e24 100644 --- a/last-call-templates/first-moderation-thread-message.txt +++ b/last-call-templates/first-moderation-thread-message.txt @@ -4,14 +4,14 @@ I am writing to you on behalf of the Team for last-call@ietf.org. This message h We are reaching out to you because of your recent message to last-call@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. -We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the discussion on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org as per our SOP [5]. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to last-call@ietf.org for 14 days. +We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the last-call on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org as per our SOP [5]. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to last-call@ietf.org for 14 days. If you wish for us to make this message public, please let us know and we will re-send it with last-call@ietf.org on cc. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] https://www.rfc-editor.org/rfc/rfc9245.html [3] [LINK to specific message] [4] [LINK to the IETF chair message to the list] diff --git a/last-call-templates/first-pattern-of-abuse-message.txt b/last-call-templates/first-pattern-of-abuse-message.txt index 3c9df6e..dd9041d 100644 --- a/last-call-templates/first-pattern-of-abuse-message.txt +++ b/last-call-templates/first-pattern-of-abuse-message.txt @@ -15,7 +15,7 @@ If you wish for us to make this message public, please let us know and we will r Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] https://www.rfc-editor.org/rfc/rfc9245.html [3] [LINK to specific message] [4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/forum-to-list.txt b/last-call-templates/forum-to-list.txt index a005b14..6c9c0dc 100644 --- a/last-call-templates/forum-to-list.txt +++ b/last-call-templates/forum-to-list.txt @@ -1,13 +1,13 @@ Hi all, -We wanted to let the list know that the Last Call team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF discussion list charter [4], we suggest that the discussions should be moved to the more specific forum identified. +We wanted to let the list know that the Last Call team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF list charter [4], we suggest that the last-calls should be moved to the more specific forum identified. [The Last Call team has been in touch with the [LIST] administers off-list.] (if required) Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to thread] [3] [LINK to join LIST] [4] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/out-of-scope.txt b/last-call-templates/out-of-scope.txt index 9347963..482e8de 100644 --- a/last-call-templates/out-of-scope.txt +++ b/last-call-templates/out-of-scope.txt @@ -10,6 +10,6 @@ We consider this an initial suggestion. We do not believe your message is part o Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message] [3] https://www.rfc-editor.org/rfc/rfc9245.html \ No newline at end of file diff --git a/last-call-templates/second-moderation-thread-message.txt b/last-call-templates/second-moderation-thread-message.txt index 1d0ca61..7bbb596 100644 --- a/last-call-templates/second-moderation-thread-message.txt +++ b/last-call-templates/second-moderation-thread-message.txt @@ -9,7 +9,7 @@ Given our correspondence with you on [DATE], we believe you are engaging in a pa Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] https://www.rfc-editor.org/rfc/rfc9245.html [3] [LINK to specific message] [4] [LINK to the IETF chair message to the list] diff --git a/last-call-templates/second-pattern-of-abuse-message.txt b/last-call-templates/second-pattern-of-abuse-message.txt index b1fd7ae..4be0295 100644 --- a/last-call-templates/second-pattern-of-abuse-message.txt +++ b/last-call-templates/second-pattern-of-abuse-message.txt @@ -13,7 +13,7 @@ Given our correspondence with you on [DATE] and [DATE], we believe you are engag Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] https://www.rfc-editor.org/rfc/rfc9245.html [3] [LINK to specific message] [4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md diff --git a/last-call-templates/unsolicited-email-to-list.txt b/last-call-templates/unsolicited-email-to-list.txt index d3c04e8..5318cf3 100644 --- a/last-call-templates/unsolicited-email-to-list.txt +++ b/last-call-templates/unsolicited-email-to-list.txt @@ -1,10 +1,10 @@ Hi all, -We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings of unsolicited bulk email. +We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF list charter [3] and avoid postings of unsolicited bulk email. Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message 1] [3] https://www.rfc-editor.org/rfc/rfc9245.html diff --git a/last-call-templates/unsolicited-email.txt b/last-call-templates/unsolicited-email.txt index 0150930..618b5a0 100644 --- a/last-call-templates/unsolicited-email.txt +++ b/last-call-templates/unsolicited-email.txt @@ -9,6 +9,6 @@ We consider this an initial suggestion. We do not believe your message is part o Thanks, [NAME] on behalf of the Team for last-call@ietf.org -[1] https://www.ietf.org/how/lists/discussion/ +[1] https://www.ietf.org/how/lists/last-call/ [2] [LINK to specific message] [3] https://www.rfc-editor.org/rfc/rfc9245.html From 2d28e72bd1d47ea1d398f5bfab87949e4d04cb1c Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Thu, 13 Jun 2024 11:19:08 -0400 Subject: [PATCH 5/5] last-call: add current team members --- last-call.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/last-call.md b/last-call.md index 54ce40a..f7c8a98 100644 --- a/last-call.md +++ b/last-call.md @@ -4,6 +4,10 @@ The Last Call team can be reached by emailing [last-call-owner@ietf.org](mailto:last-call-owner@ietf.org). +Current team members are: +* Bron Gondwana <[brong@fastmailteam.com](mailto:brong@fastmailteam.com)> +* Jared Mauch <[jared@puck.nether.net](mailto:jared@puck.nether.net)> + ## General operations The Last Call team strive to monitor all postings on last-call@ietf.org on a daily basis. The IETF Chair also monitors the list but may not be in a position to read each message or monitor every day.