Skip to content

Commit b573f7c

Browse files
committed
Rename list and team
1 parent e0414df commit b573f7c

16 files changed

+53
-53
lines changed

last-call-templates/PR-message-to-list.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Hi all,
22

3-
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].
3+
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].
44

55
Thanks,
6-
[NAME] on behalf of the Moderators team for ietf@ietf.org
6+
[NAME] on behalf of the Team for last-call@ietf.org
77

88
[1] https://www.ietf.org/how/lists/discussion/
99
[2] [LINK to specific message 1]

last-call-templates/PR-moderation-message-to-list.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Hi all,
22

3-
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].
3+
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].
44

55
Thanks,
6-
[NAME] on behalf of the Moderators team for ietf@ietf.org
6+
[NAME] on behalf of the Team for last-call@ietf.org
77

88
[1] https://www.ietf.org/how/lists/discussion/
99
[2] [LINK to specific message 1]

last-call-templates/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Email Templates
22

3-
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.
3+
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.
44

55
## Level 0: Initial suggestion
66

last-call-templates/announcements-to-list.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Hi all,
22

3-
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].
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].
44

55
Thanks,
6-
[NAME] on behalf of the Moderators team for ietf@ietf.org
6+
[NAME] on behalf of the Team for last-call@ietf.org
77

88
[1] https://www.ietf.org/how/lists/discussion/
99
[2] [LINK to specific message 1]

last-call-templates/announcements.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
Hi [NAME],
22

3-
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].
3+
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].
44

5-
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.
5+
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.
66

7-
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.
7+
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.
88

99
Thanks,
10-
[NAME] on behalf of the Moderators team for ietf@ietf.org
10+
[NAME] on behalf of the Team for last-call@ietf.org
1111

1212
[1] https://www.ietf.org/how/lists/discussion/
1313
[2] [LINK to specific message]

last-call-templates/first-message-to-list.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Hi all,
22

3-
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].
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 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].
44

55
Thanks,
6-
[NAME] on behalf of the Moderators team for ietf@ietf.org
6+
[NAME] on behalf of the Team for last-call@ietf.org
77

88
[1] https://www.ietf.org/how/lists/discussion/
99
[2] [LINK to specific message 1]

last-call-templates/first-message.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
Hi [NAME],
22

3-
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].
3+
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].
44

5-
We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language:
5+
We are reaching out to you because of your recent message to last-call@ietf.org [3]. The message contained the following language:
66

77
[LANGUAGE]
88

9-
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.
9+
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.
1010

1111
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.
1212

13-
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.
13+
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.
1414

1515
Thanks,
16-
[NAME] on behalf of the Moderators team for ietf@ietf.org
16+
[NAME] on behalf of the Team for last-call@ietf.org
1717

1818
[1] https://www.ietf.org/how/lists/discussion/
1919
[2] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/first-moderation-message-to-list.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Hi all,
22

3-
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].
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] 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].
44

55
Thanks,
6-
[NAME] on behalf of the Moderators team for ietf@ietf.org
6+
[NAME] on behalf of the Team for last-call@ietf.org
77

88
[1] https://www.ietf.org/how/lists/discussion/
99
[2] [LINK to specific message]

last-call-templates/first-moderation-thread-message.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
Hi [NAME],
22

3-
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].
3+
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].
44

5-
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].
5+
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].
66

7-
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.
7+
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.
88

9-
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.
9+
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.
1010

1111
Thanks,
12-
[NAME] on behalf of the Moderators team for ietf@ietf.org
12+
[NAME] on behalf of the Team for last-call@ietf.org
1313

1414
[1] https://www.ietf.org/how/lists/discussion/
1515
[2] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/first-pattern-of-abuse-message.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
Hi [NAME],
22

3-
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].
3+
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].
44

5-
We are reaching out to you because of your recent message to ietf@ietf.org [3]. The message contained the following language:
5+
We are reaching out to you because of your recent message to last-call@ietf.org [3]. The message contained the following language:
66

77
[LANGUAGE]
88

9-
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.
9+
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.
1010

11-
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.
11+
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.
1212

13-
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.
13+
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.
1414

1515
Thanks,
16-
[NAME] on behalf of the Moderators team for ietf@ietf.org
16+
[NAME] on behalf of the Team for last-call@ietf.org
1717

1818
[1] https://www.ietf.org/how/lists/discussion/
1919
[2] https://www.rfc-editor.org/rfc/rfc9245.html

0 commit comments

Comments
 (0)