Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

meta: moderation policy updates #276

Merged
merged 7 commits into from
Aug 29, 2017
Merged

meta: moderation policy updates #276

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
98a6a49
meta: update moderation policy
jasnell Aug 21, 2017
2eb2eec
[Squash] Language Refinements
jasnell Aug 22, 2017
29cec5a
[Squash] Nits
jasnell Aug 22, 2017
e1dfb4d
[Squash] Clarify language around temporary bans
jasnell Aug 22, 2017
588f6aa
[Squash] Extend auto approval period to seven days
jasnell Aug 23, 2017
479eff3
[Squash] nit
jasnell Aug 28, 2017
a7b190f
[Squash] recertification for moderations
jasnell Aug 29, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions Moderation-Policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ nodejs/moderation repository issue is not considered a violation of the
in requests posted to public repositories.

Requests for Moderation that do not appear to have been submitted in good faith
with intent to address a legitimate [Code of Conduct][] violation may be
with intent to address a legitimate [Code of Conduct][] violation will be
ignored.

## Consideration of Intent
Expand Down Expand Up @@ -163,8 +163,8 @@ a Post from Moderation.
* Identify all changes made to the Post, and
* Identify the steps previously taken to resolve the issue.
* If the Moderation action included Banning an indication of whether the Ban
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comma after "Banning"?

is permanent or temporary is required, along with a note justifying the
action.
is permanent or temporary is required, along with an issue posted to the
moderation repository justifying the action.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a link to the moderation repository?

* Explanations of Moderation actions on Collaborator Posts must be provided in:
* A new post within the original thread, or
* A new issue within the private nodejs/moderation repository.
Expand Down Expand Up @@ -209,6 +209,11 @@ The Moderation Team may, at their discretion, choose to enable GitHub's
[Temporary Interaction Limits][] on any GitHub repository in the Node.js GitHub
Organization.

Any Collaborator may request that the Moderation Team enable the Temporary
Interaction Limits by posting an issue to the moderation repository. If the
Moderation Team choose not to do so, then a comment explaining why that
decision was made should be added to the moderation repository thread.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this ought to be "must be added." Otherwise, it leaves a gap where the Moderation Team decides not to, and then never posts a decision to the thread. This would not look good.


## Privacy of the nodejs/moderation Repository

The nodejs/moderation Repository is used to discuss the potentially sensitive
Expand Down