Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Better process for communicating feedback to members by the TSC

未關閉
#876 3 則留言 8 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯

研究方向

從 issue 現有的審核團隊流程開始:在 chat 中發文、收集回饋,然後採取行動。審閱 TSC 的討論,並定義一個簡短、清楚的升級流程:不需要會議時在 72 小時內回覆,需要會議時在一週內回覆;完成表示已將約定的流程記錄成文件並採用。

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
JavaScript
星號
202
分支
183
平均合併
13 天 12 小時
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

nodejs/admin 的其他 Issue

查看 nodejs/admin 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。