Better process for communicating feedback to members by the TSC
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- developer-experience
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.
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.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·