Proposal: Define SLAs for moderation team responsiveness
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
研究方向
先檢視 Moderation-Policy.md 以及 action items 中引用的 ONBOARDING.md 檢查清單，然後閱讀連結的審核政策討論。當 SLA 數字達成共識，且透過 PR 更新 onboarding 檢查清單和 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 ([email protected] 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
-
Design only Leadership Survey SLFS
難度 2/5 1-3 小時 新手友好度 70/100
bcgov/digital-journeys#2293 ·
-
Toolkit
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
API Bug
難度 2/5 1-3 小時 新手友好度 78/100
ProjectSidewalk/SidewalkWebpage#5556 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
jessepollak/home#1454 ·
維護者通常 1 天內回覆
-
Mend: dependency security vulnerability untriaged
難度 2/5 1-3 小時 新手友好度 64/100
opensearch-project/OpenSearch-Dashboards#12822 ·
維護者通常 1 天內回覆