Add Moderation Policy #6

IamLizu · 2024-11-03T07:04:33Z

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,

The scope of this moderation policy mentions only the GitHub organizations unlike Nodejs, as they have Slack and other communities in scope.
Following Nodejs, I have kept the process of requesting moderation via email, and suggested an example email address as [email protected].
- If we decide to not have this approach, we can simply remove the relevant parts of this process.
- Otherwise, a mailbox creation is suggested.
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
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

Fixes Proposal: Allow moderation rights to Triage team discussions#270

ModerationPolicy.md

Co-authored-by: Aravind Nair <[email protected]>

ModerationPolicy.md

IamLizu · 2024-11-03T09:43:44Z

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

ModerationPolicy.md

UlisesGascon · 2024-11-04T12:33:08Z

ModerationPolicy.md

+Anyone may request Moderation of a Post. Requesting Moderation of a Post can be
+accomplished in one of four ways:
+
+-   Via the [[email protected]][] email address,


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

Sure.

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

What is the plan regarding that?

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

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

CBID2

Just gave one suggestion

CBID2 · 2024-11-05T03:27:07Z

ModerationPolicy.md

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


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][]).

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.

wesleytodd

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.

wesleytodd · 2024-11-12T14:54:36Z

ModerationPolicy.md

+
+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.


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.

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.

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

Alright, revising that.

wesleytodd · 2024-11-12T14:55:39Z

ModerationPolicy.md

+Anyone may request Moderation of a Post. Requesting Moderation of a Post can be
+accomplished in one of four ways:
+
+-   Via the [[email protected]][] email address,


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.

wesleytodd · 2024-11-12T14:56:23Z

ModerationPolicy.md

+Note that Collaborators may Moderate non-Collaborator Posts at any time without
+submitting an initial request (see: [Non-Collaborator Posts][]).
+
+Use of the [[email protected]][] email address -- or private email to individual


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

wesleytodd · 2024-11-12T14:56:29Z

ModerationPolicy.md

+Use of the [[email protected]][] 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 [[email protected]][] address are currently forwarded


email update

wesleytodd · 2024-11-12T14:56:35Z

ModerationPolicy.md

+All emails sent to the [[email protected]][] address are currently forwarded
+to all members of the Moderation Team.
+
+When a request is sent by email to the [[email protected]][] (or directly to a


email update

ModerationPolicy.md

ljharb · 2024-11-12T16:51:11Z

ModerationPolicy.md

+    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.


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

Should we record the why in a private space?

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.

Rephrasing it to include only why.

ModerationPolicy.md

docs: add moderation policy draft

ef5596e

IamLizu requested review from ljharb, UlisesGascon, jonchurch, wesleytodd, LinusU, blakeembrey, sheplu, crandmck, ctcpip and a team November 3, 2024 07:04

aravindvnair99 suggested changes Nov 3, 2024

View reviewed changes

ModerationPolicy.md Outdated Show resolved Hide resolved

refactor: fix typo

c0e7833

Co-authored-by: Aravind Nair <[email protected]>

aravindvnair99 suggested changes Nov 3, 2024

View reviewed changes

ModerationPolicy.md Outdated Show resolved Hide resolved

ModerationPolicy.md Outdated Show resolved Hide resolved

IamLizu requested a review from aravindvnair99 November 3, 2024 09:45

ljharb reviewed Nov 3, 2024

View reviewed changes

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

docs: fix typo

dd8e7ae

IamLizu requested a review from ljharb November 4, 2024 08:48

IamLizu added 2 commits November 4, 2024 14:55

docs: fix typo

2b73663

docs: add table of contents header

a1ee0aa

UlisesGascon reviewed Nov 4, 2024

View reviewed changes

ctcpip marked this pull request as draft November 4, 2024 22:36

ctcpip requested changes Nov 4, 2024

View reviewed changes

CBID2 reviewed Nov 5, 2024

View reviewed changes

wesleytodd reviewed Nov 12, 2024

View reviewed changes

ljharb reviewed Nov 12, 2024

View reviewed changes

wesleytodd mentioned this pull request Nov 15, 2024

add Code of Conduct expressjs/.github#8

Open

IamLizu added 2 commits November 17, 2024 23:24

docs: reduce diff churn and purge current members

20da36d

docs: only include the _why_ for minor edits

a24187c

IamLizu requested review from wesleytodd, ljharb, ctcpip and UlisesGascon November 17, 2024 17:30

jonchurch added the tc agenda label Nov 20, 2024

jonchurch mentioned this pull request Nov 20, 2024

2024-11-20 Express Working Session expressjs/discussions#308

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Moderation Policy #6

Add Moderation Policy #6

IamLizu commented Nov 3, 2024 •

edited

Loading

IamLizu commented Nov 3, 2024 •

edited

Loading

UlisesGascon Nov 4, 2024

IamLizu Nov 4, 2024

wesleytodd Nov 12, 2024

ctcpip left a comment

CBID2 left a comment

CBID2 Nov 5, 2024

IamLizu Nov 5, 2024 •

edited

Loading

wesleytodd left a comment

wesleytodd Nov 12, 2024

ljharb Nov 12, 2024

wesleytodd Nov 12, 2024

IamLizu Nov 17, 2024

IamLizu Nov 18, 2024

wesleytodd Nov 12, 2024

wesleytodd Nov 12, 2024

wesleytodd Nov 12, 2024

wesleytodd Nov 12, 2024

ljharb Nov 12, 2024

wesleytodd Nov 12, 2024

ljharb Nov 12, 2024

IamLizu Nov 17, 2024 •

edited

Loading

IamLizu Nov 18, 2024

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


		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.

Add Moderation Policy #6

Are you sure you want to change the base?

Add Moderation Policy #6

Conversation

IamLizu commented Nov 3, 2024 • edited Loading

Notes

IamLizu commented Nov 3, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ctcpip left a comment

Choose a reason for hiding this comment

CBID2 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

IamLizu Nov 5, 2024 • edited Loading

Choose a reason for hiding this comment

wesleytodd left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

IamLizu Nov 17, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

IamLizu commented Nov 3, 2024 •

edited

Loading

IamLizu commented Nov 3, 2024 •

edited

Loading

IamLizu Nov 5, 2024 •

edited

Loading

IamLizu Nov 17, 2024 •

edited

Loading