Skip to content

Commit

Permalink
Clarify moderation reporting requirements (#663)
Browse files Browse the repository at this point in the history
* Clarify moderation reporting requirements

Refs: #662

This adds specific scenarios as well as removes hiding comments from the reporting requirements.
It also adds a few examples and removes the (unclear IMO) exception to reporting regarding bad faith.

Happy to iterate on this and change this - mostly opening this to see what people think.

cc @nodejsmoderation @nodejs/tsc

* Update Moderation-Policy.md

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Rich Trott <rtrott@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Darshan Sen <raisinten@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Rich Trott <rtrott@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Rich Trott <rtrott@gmail.com>

* Update Moderation-Policy.md

Co-authored-by: Rich Trott <rtrott@gmail.com>

Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Darshan Sen <raisinten@gmail.com>
  • Loading branch information
4 people authored Jan 12, 2023
1 parent a8bbb53 commit 49600c5
Showing 1 changed file with 33 additions and 8 deletions.
41 changes: 33 additions & 8 deletions Moderation-Policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ a Post from Moderation.
* Posts authored by non-Collaborators are always subject to immediate Moderation
by any Collaborator if the content is intentionally disruptive or in violation
of the [Code of Conduct][].
* When Moderating non-Collaborator Posts, the moderating Collaborator must:
* When moderating non-Collaborator posts, the moderating Collaborator must:
* Explain the justification for Moderating the post, and
* Identify all changes made to the Post.
* If the Moderation action included Blocking, an indication of whether the Block
Expand All @@ -172,13 +172,9 @@ of the [Code of Conduct][].
* Moderation of Posts authored by non-Collaborators may result in those
non-Collaborators being Blocked temporarily or indefinitely from further
participation in the Node.js GitHub organization.
* One may immediately bypass the above procedures if it is clear that there is no intention to
collaborate in good faith. In such cases, it is permissible to immediately:
* remove posts
* lock issues/pull requests
* delete issues/pull requests
* block users
* report accounts to GitHub
* If it is clear that there is no intention to collaborate in good faith,
it is possible to hide comments of non-Collaborators. In that case there is
an exception to the reporting requirement described above.
* Accounts that are reasonably believed to be bots (other than bots authorized
by the TSC) are subject to immediate Blocking.
* Issues, pull requests, discussions, and comments that are spam (job posting,
Expand All @@ -190,6 +186,35 @@ of the [Code of Conduct][].
GitHub interface as user `ghost`. There is no need
to screenshot or document these deletions.

There are a few examples of moderating non-Collaborator posts:

Scenario 1:
* A non-Collaborator posts a comment that indicates that they are a bot.
* A collaborator sees the post and hides it.
* No further action is necessary.

Scenario 2:
* A non-Collaborator posts a comment that is against the Code of Conduct.
* A Collaborator sees the comment and asks the author to self-moderate.
* The author refuses to self-moderate.
* The Collaborator deletes the comment and posts an issue in the moderation
repository explaining their actions.

Scenario 3:
* A non-Collaborator opens a pull request with comments indicating they are a
bot.
* A Collaborator sees that pull requests, closes it, deletes the comments
and posts an issue in the moderation repository explaining their actions.
* A moderation team member sees the issue and decides to block the user from the
organization.

Scenario 4:
* A non-Collaborator posts a comment on an old commit that is against the
Code of Conduct.
* A Collaborator sees the comment, takes a screenshot, and deletes it.
* The Collaborator posts an issue in the moderation repository explaining
their actions.

### Temporary Interaction Limits

The Moderation Team may, at their discretion, choose to enable [GitHub's
Expand Down

0 comments on commit 49600c5

Please sign in to comment.