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 摘要。