Proposal: Define SLAs for moderation team responsiveness
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
首先查看 Moderation-Policy.md 和 action items 中引用的 ONBOARDING.md 检查清单,然后阅读链接的审核政策讨论。当 SLA 数字达成共识,并且通过 PR 更新了入门检查清单和 Moderation Policy 后,工作即告完成。
由索引模型根据 Issue 内容生成。
描述
Part of the moderation policy review framed by openjs-foundation/summit#511, for discussion at the Moderation Roundtable on October 1 (if not resolves to consensus prior).
There are no response time expectations for moderation
The Moderation Policy describes what the moderation team can do but never says how quickly. There are no timelines for acknowledging reports, responding to issues in nodejs/moderation, acting on @nodejs/moderation tags, or onboarding new members. This matters if our community is to be kept safe and we can more confidently model inclusivity and trust.
A recent self-nomination took 7 months to resolve. A collaborator who reports harassment has no idea when someone will look at it. A @nodejs/moderation tag in an issue can go unacknowledged indefinitely.
Proposed SLAs (Service Level Agreement)
Draft timelines for four common moderation surfaces. All times are calendar time.
1. Responding to reports (report@nodejs.org and private emails)
| Step | SLA |
|---|---|
| Acknowledge receipt to reporter | 24 hours |
| Begin incident response process | 48 hours |
2. Responding to issues in nodejs/moderation
| Step | SLA |
|---|---|
| Acknowledge the issue | 24 hours |
| Assign a moderator to resolve (if action is needed) | 48 hours |
The goal here is to help drive conversation in this repo where we typically have open-ended "is this spam?" discussions, that don't have clear steps to resolve.
3. Responding to @nodejs/moderation tags across the org
| Step | SLA |
|---|---|
| Acknowledge the tag | 24 hours |
Triage: resolve in-thread or open a tracking issue in nodejs/moderation |
48 hours |
[!NOTE]
This is the most nebulous reporting mechanism, but when it happens it's typically in response to an ongoing, active argument or potential CoC violation. Discussion should perhaps first confirm this is a valid reporting mechanism at all.
4. Onboarding new moderation team members
| Step | SLA |
|---|---|
| Acknowledge nomination | 7 days |
| TSC vote (on agenda or async) | 30 days from submission |
| Permissions granted after approval | 7 days |
| Total: nomination to active member | 45 days maximum |
If any step exceeds its SLA, the nominee or any moderation team member may escalate to the TSC chair.
Open questions
- Are these numbers realistic with current team capacity and time zone coverage?
- How do we ensure SLA conformance without placing undue burden on volunteers? (See forthcoming proposal on moderation team chair role.)
Action items
- Consensus on SLA numbers
- Edit onboarding checklist
- Add SLAs to the Moderation Policy via PR
Assisted by: Claude Opus
- 主要语言
- JavaScript
- 星标
- 202
- 派生
- 183
- 平均合并
- 13 天 12 小时
- 30 天内合并 PR
- 2
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nodejs/admin 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
tsc-agenda
难度 5/5 一周以上 新手友好度 30/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 30/100
-
难度 1/5 1 小时以内 新手友好度 35/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
antfu-collective/icones#398 ·
-
ECmail.com 未关闭
难度 1/5 1 小时以内 新手友好度 90/100
wesbos/burner-email-providers#554 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
radiantearth/stac-browser#1023 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
components-web-app/docs#92 ·