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.

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

Add Moderation Policy #6

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

IamLizu
Copy link
Member

@IamLizu IamLizu commented Nov 3, 2024

As discussed in GitHub issue #270, this pull request presents a draft of the Moderation Policy for the expressjs, jshttp, and pillarjs GitHub organizations. This draft is largely based on the Node.js Moderation Policy, as most of its provisions are deemed suitable for the our organizations.

While the entire document is open for review, I request particular attention to the following items,

  1. The scope of this moderation policy mentions only the GitHub organizations unlike Nodejs, as they have Slack and other communities in scope.
  2. Following Nodejs, I have kept the process of requesting moderation via email, and suggested an example email address as report@expressjs.com.
    • If we decide to not have this approach, we can simply remove the relevant parts of this process.
    • Otherwise, a mailbox creation is suggested.
  3. expressjs/moderation repository should be the home for discussing things related to moderation and a place for moderation requests.
    • If we have the repository, all collaborators should be added.
    • Otherwise, suggesting to create the repository.
    • A label moderation-review to escalate issues
  4. I have added a Requirements section in addition to the existing process of being a Moderator as mentioned in Nodejs model,
    • Must be a Collaborator in the expressjs GitHub organization.
    • Active participation in the expressjs/moderation repository.
    • Show a commitment to the expressjs Code of Conduct.

Notes

ModerationPolicy.md Outdated Show resolved Hide resolved
Co-authored-by: Aravind Nair <22199259+aravindvnair99@users.noreply.github.com>
ModerationPolicy.md Outdated Show resolved Hide resolved
ModerationPolicy.md Outdated Show resolved Hide resolved
@IamLizu
Copy link
Member Author

IamLizu commented Nov 3, 2024

Okay, I will wait for further suggestions from others as well and then do a batch-update.

ModerationPolicy.md Outdated Show resolved Hide resolved
ModerationPolicy.md Outdated Show resolved Hide resolved
ModerationPolicy.md Outdated Show resolved Hide resolved
ModerationPolicy.md Outdated Show resolved Hide resolved
@IamLizu IamLizu requested a review from ljharb November 4, 2024 08:48
Anyone may request Moderation of a Post. Requesting Moderation of a Post can be
accomplished in one of four ways:

- Via the [report@expressjs.com][] email address,
Copy link
Member

Choose a reason for hiding this comment

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

IMO We will need to wait until we have that email alias ready before landing this PR.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure.

That brings the question, will everyone at Moderation team have access to that mailbox?

What is the plan regarding that?

Copy link
Member

Choose a reason for hiding this comment

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

We need to work with the CPC on this. We have some emails setup, but I think we need to do some administrative work before we can use them.

@ctcpip ctcpip marked this pull request as draft November 4, 2024 22:36
Copy link
Member

@ctcpip ctcpip left a comment

Choose a reason for hiding this comment

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

converting to draft, and would like to discuss this with the TC before moving forward

Copy link

@CBID2 CBID2 left a comment

Choose a reason for hiding this comment

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

Just gave one suggestion

Comment on lines 70 to 71
Note that Collaborators may Moderate non-Collaborator Posts at any time without
submitting an initial request (see: [Non-Collaborator Posts][]).
Copy link

Choose a reason for hiding this comment

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

Suggested change
Note that Collaborators may Moderate non-Collaborator Posts at any time without
submitting an initial request (see: [Non-Collaborator Posts][]).
> [!NOTE]
> Collaborators may Moderate non-Collaborator Posts at any time without
submitting an initial request (see: [Non-Collaborator Posts][]).

Copy link
Member Author

@IamLizu IamLizu Nov 5, 2024

Choose a reason for hiding this comment

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

Hi @CBID2 👋

Thanks for the suggestion. The formatting change does look good. However, this would require changing the link markup from [][] to []().

If you could make this change, I could commit the suggestion.

Copy link
Member

@wesleytodd wesleytodd left a comment

Choose a reason for hiding this comment

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

Not dropping the approve yet, but I think this is GREAT. I want to spend a bit more time reading it and also comparing to some others in the ecosystem. I will also see if we can get some folks experienced in moderation to help review.


This policy applies to all repositories under these GitHub organizations: expressjs, jshttp, and pillarjs, as well as all Working Groups.

Any posts, comments, issues, or pull requests that violate the [Code of Conduct][] are subject to Moderation as defined in this policy.
Copy link
Member

Choose a reason for hiding this comment

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

This policy also needs to apply to any project run comms: slack, discord, socials (the ones on behalf of the project, not personal), etc. Not just githbu.

Copy link

Choose a reason for hiding this comment

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

Typically, if one's personal presence anywhere also mentions that you're involved in the project, that makes it an applicable space. iow, if your twitter bio says "express.js contributor", then the policy applies to your tweets.

Copy link
Member

Choose a reason for hiding this comment

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

TIL. Thanks for that. We should then be very explicit in the wording here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Alright, revising that.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

Anyone may request Moderation of a Post. Requesting Moderation of a Post can be
accomplished in one of four ways:

- Via the [report@expressjs.com][] email address,
Copy link
Member

Choose a reason for hiding this comment

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

We need to work with the CPC on this. We have some emails setup, but I think we need to do some administrative work before we can use them.

Note that Collaborators may Moderate non-Collaborator Posts at any time without
submitting an initial request (see: [Non-Collaborator Posts][]).

Use of the [report@expressjs.com][] email address -- or private email to individual
Copy link
Member

Choose a reason for hiding this comment

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

just a note to fix all the emails as per the comment above when we can.

Use of the [report@expressjs.com][] email address -- or private email to individual
Moderation Team members -- is appropriate when the individual requesting the
Moderation does not feel comfortable directly or publicly making the request.
All emails sent to the [report@expressjs.com][] address are currently forwarded
Copy link
Member

Choose a reason for hiding this comment

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

email update

All emails sent to the [report@expressjs.com][] address are currently forwarded
to all members of the Moderation Team.

When a request is sent by email to the [report@expressjs.com][] (or directly to a
Copy link
Member

Choose a reason for hiding this comment

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

email update

ModerationPolicy.md Outdated Show resolved Hide resolved
for exclusion from any OpenJS Foundation sponsored event or activity.
- Minor edits to the formatting of a Post or to correct typographical errors
are not "Moderation". Such edits and their intent must
still be documented with a short note indicating who made the edit and why.
Copy link

Choose a reason for hiding this comment

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

github's "edits" feature already documents who made the edit and what change was made; only the "why" wouldn't be included.

Copy link
Member

Choose a reason for hiding this comment

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

Should we record the why in a private space?

Copy link

Choose a reason for hiding this comment

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

i assume that would be the moderation repo. but also i think this will either create a lot of useless noise, or will prevent a lot of helpful corrections, because the "why" will likely be pretty apparent.

Copy link
Member Author

@IamLizu IamLizu Nov 17, 2024

Choose a reason for hiding this comment

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

Rephrasing it to include only why.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

ModerationPolicy.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proposal: Allow moderation rights to Triage team
8 participants