Add Moderation Policy by IamLizu · Pull Request #6 · expressjs/admin

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

FixesProposal: Allow moderation rights to Triage team discussions#270

Co-authored-by: Aravind Nair <22199259+aravindvnair99@users.noreply.github.com>

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

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

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

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


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.

I have gotten access setup and will be meeting with Ben next week to sort out details of how we can manage these going forward. Will circle back when we have that sorted out.

Were we able to setup a list for the moderation team? I was wondering if we could move forward on this.

Right now it's not simply a matter of setting up distribution lists. The TC has not gotten consensus to proceed with this.

Yeah, I think this gets my 👍 generally but we for sure need to loop back now that we can all comment on the specifics and make sure we agree we can move forward.

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

+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

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

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


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

+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


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

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

+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


email update

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

+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


email update

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

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

bjohansebas · 2025-01-28T22:51:54Z

+- Accounts that are reasonably believed to be bots (other than bots authorized by the TC) are subject to immediate Blocking.
+- Issues, pull requests, discussions, and comments that are spam (job posting, service advertising, etc.) are subject to immediate moderation.
+- Collaborators may use the Hide feature in the GitHub interface for off-topic posts by non-Collaborators.
+- Moderation Team members and TC voting members can delete any issues or comments posted by accounts that have been deleted by GitHub. These accounts show up in the GitHub interface as user `ghost`. There is no need to screenshot or document these deletions.


Only TC
Suggested change
- Moderation Team members and TC voting members can delete any issues or comments posted by accounts that have been deleted by GitHub. These accounts show up in the GitHub interface as user `ghost`. There is no need to screenshot or document these deletions.
- Moderation Team members and TC members can delete any issues or comments posted by accounts that have been deleted by GitHub. These accounts show up in the GitHub interface as user `ghost`. There is no need to screenshot or document these deletions.

bjohansebas · 2025-01-28T22:55:13Z

+ - A new issue within the private expressjs/moderation repository.
+- Any Collaborator habitually violating the Code of Conduct or this Moderation policy may be Blocked temporarily or, in extreme cases, Removed and Blocked indefinitely.
+
+### Non-Collaborator Posts


This was added to Node.js, some time later, maybe you will want to add it too.
* Issues, pull requests, discussions, and comments that are believed to be LLM-generated (e.g a PR coming from a new contributor changing a single file without clear motivation) should be closed with a comment such as "It seems you are using a LLM, please stop, this is not bringing any value and is wasting our time. If you are not using one, please read and follow our contributing guidelines." Report the user to the moderation repository so they get blocked if they do it again.

Makes sense, thanks for the input. I will update it in next change.

ctcpip · 2025-04-28T20:59:33Z

Closing per expressjs/discussions#270 (comment)

docs: add moderation policy draft
ef5596e

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

aravindvnair99 suggested changes Nov 3, 2024
View reviewed changes

Comment threadModerationPolicy.md Outdated

refactor: fix typo
c0e7833
Co-authored-by: Aravind Nair <22199259+aravindvnair99@users.noreply.github.com>

aravindvnair99 suggested changes Nov 3, 2024
View reviewed changes

Comment threadModerationPolicy.md Outdated
Comment threadModerationPolicy.md Outdated

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

ljharb reviewed Nov 3, 2024
View reviewed changes

Comment threadModerationPolicy.md Outdated
Comment threadModerationPolicy.md Outdated
Comment threadModerationPolicy.md Outdated
Comment threadModerationPolicy.md Outdated

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
Merged

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 UlisesGascon, ctcpip, ljharb and wesleytodd 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

github-actionsBot mentioned this pull request Dec 3, 2024
2024-12-09 Express TC Meeting expressjs/discussions#312
Closed

This was referenced Dec 17, 2024
2024-12-23 Express TC Meeting expressjs/discussions#314
Closed
2024-12-23 Express TC Meeting expressjs/discussions#317
Closed

github-actionsBot mentioned this pull request Dec 31, 2024
2025-01-06 Express TC Meeting expressjs/discussions#319
Closed

github-actionsBot mentioned this pull request Jan 14, 2025
2025-01-20 Express TC Meeting expressjs/discussions#321
Closed

github-actionsBot mentioned this pull request Jan 28, 2025
2025-02-03 Express TC Meeting expressjs/discussions#328
Closed

bjohansebas reviewed Jan 28, 2025
View reviewed changes

github-actionsBot mentioned this pull request Feb 11, 2025
2025-02-17 Express TC Meeting expressjs/discussions#334
Closed

github-actionsBot mentioned this pull request Feb 25, 2025
2025-03-03 Express TC Meeting expressjs/discussions#343
Closed

github-actionsBot mentioned this pull request Mar 11, 2025
2025-03-17 Express TC Meeting expressjs/discussions#347
Closed

github-actionsBot mentioned this pull request Mar 25, 2025
2025-03-31 Express TC Meeting expressjs/discussions#351
Closed

github-actionsBot mentioned this pull request Apr 8, 2025
2025-04-14 Express TC Meeting expressjs/discussions#357
Closed

github-actionsBot mentioned this pull request Apr 22, 2025
2025-04-28 Express TC Meeting expressjs/discussions#361
Closed

ctcpip closed this Apr 28, 2025

		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.

	- Moderation Team members and TC voting members can delete any issues or comments posted by accounts that have been deleted by GitHub. These accounts show up in the GitHub interface as user `ghost`. There is no need to screenshot or document these deletions.
	- Moderation Team members and TC members can delete any issues or comments posted by accounts that have been deleted by GitHub. These accounts show up in the GitHub interface as user `ghost`. There is no need to screenshot or document these deletions.

Uh oh!

Uh oh!

Conversation

IamLizu commented Nov 3, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Notes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

IamLizu commented Nov 3, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ctcpip left a comment

Choose a reason for hiding this comment

Uh oh!

CBID2 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

IamLizuNov 5, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

wesleytodd left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

IamLizuNov 17, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

IamLizu commented Nov 3, 2024•
edited
Loading

IamLizu commented Nov 3, 2024•
edited
Loading

IamLizuNov 5, 2024•
edited
Loading

IamLizuNov 17, 2024•
edited
Loading