nodejs / nodejs/admin

Better process for communicating feedback to members by the TSC

Open
#876 3 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
202
Forks
183
Avg merge
2m
Merged PRs (30d)
1

Description

Hey,

The moderation team has a pretty simple process where when we want to provide feedback to an individual or take a moderation action typically the process is:

  • We post in chat.
  • We collect feedback from other team members for a bit (a few hours)
  • We take the action (e.g. sending the email).

In the TSC, we don't really have a clear process for "how long should I wait before speaking for the TSC about feedback for an individual?" so whenever we discuss people we often take a long time to respond sometimes creating a lot of frustration and cases where people are waiting for feedback for a long time needlessly.

cc @aduh95 in particular who is active in both groups and probably feels this :] (as a side note, thanks ❤️ )

Rather than suggest a solution (I have several) I figured it'd be a good idea to let @nodejs/tsc suggest (hopefully!) a short/clear process for escalating these sort of issues. Ideally in a way where we don't wait for more than 72h if we don't have to meet and 1w if we do.


I am posting this in public since in general I try to keep governance discussions as public as possible but obvious I won't name any concrete examples where feedback was provided or actions taken for privacy.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue's existing moderation-team process: post in chat, collect feedback, then act. Review the TSC discussion and define a short, clear escalation process with responses within 72 hours when no meeting is needed and one week when a meeting is required; done means the agreed process is documented and adopted.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.