-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #26 from chris-box/rename-unprofessional
Rename unprofessional-commentary to uncivil-commentary
- Loading branch information
Showing
8 changed files
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ While [RFC 9245] creates the role of Moderators for the [email protected] mailing li | |
|
||
* [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. | ||
* A definition of [Uncivil Commentary](unprofessional-commentary.md) the Moderators follows. | ||
* A definition of [Uncivil Commentary](uncivil-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. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,7 +13,7 @@ Current team members are: | |
|
||
The Moderators strive to monitor all postings on [email protected] 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. | ||
|
||
When IETF discussion list subscribers believe that a posting may be considered inappropriate according to [RFC 9245] or the [Uncivil Commentary](unprofessional-commentary.md), they are encouraged to report it to [email protected]. Moderators team members are also subscribers to the IETF discussion list and they follow the same process to report posts that they consider inappropriate.The Moderators team will discuss all reports received and make a determination about whether they believe the posting was inappropriate. At least two team members must agree that a posting was inappropriate before the Moderators team takes any action in response. | ||
When IETF discussion list subscribers believe that a posting may be considered inappropriate according to [RFC 9245] or the [Uncivil Commentary](uncivil-commentary.md), they are encouraged to report it to [email protected]. Moderators team members are also subscribers to the IETF discussion list and they follow the same process to report posts that they consider inappropriate.The Moderators team will discuss all reports received and make a determination about whether they believe the posting was inappropriate. At least two team members must agree that a posting was inappropriate before the Moderators team takes any action in response. | ||
|
||
When the Moderators team determines that a posting is inappropriate, one team member suggests a response to the rest of the team, including specific text for email(s) to the original poster and/or the list, as appropriate. The Moderators team uses a standard set of [email templates](email-templates). Proposed emails to either individuals or to the list must be vetted and approved by at least one other Moderators team member before being sent. | ||
|
||
|
File renamed without changes.