-
Notifications
You must be signed in to change notification settings - Fork 17
Expand file tree
/
Copy pathfirst-pattern-of-abuse-message.txt
More file actions
21 lines (13 loc) · 1.41 KB
/
first-pattern-of-abuse-message.txt
File metadata and controls
21 lines (13 loc) · 1.41 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Hi [NAME],
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 last-call@ietf.org [3]. The message contained the following language:
[LANGUAGE]
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 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 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/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