Proposal: Create a yearly moderation team chair role
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Domínio
- documentation
Direção de pesquisa
Comece revisando Moderation-Policy.md e as issues vinculadas sobre a política de moderação, especialmente as propostas de SLA e permissões. O trabalho primeiro exige consenso sobre a necessidade do papel de chair e um acordo sobre os detalhes de sua eleição e das vacâncias; se aceito, estará concluído quando o primeiro chair for eleito e o papel for adicionado a Moderation-Policy.md por meio de uma PR.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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).
Shared responsibility has meant no one is responsible
The moderation team operates as equal peers. No one is designated to keep things moving. The results are visible:
- A self-nomination sat for 7 months.
- Monthly TSC reports are not being produced.
- Annual recertification has lapsed. (A subject for another proposal, perhaps)
- Proposed SLAs (see https://github.com/nodejs/admin/issues/1093) need someone watching whether they are being met.
Propose a chair whose job is to expedite
The chair coordinates the team's operational commitments. They do not lead investigations, override decisions, or speak for the team on any case.
The chair expedites:
- Monitors whether SLAs are being met and follows up when they are not
- Ensures the monthly TSC report is produced (this may require separate tooling investment)
- Initiates the annual recertification process in coordination with the TSC
- Drives the onboarding checklist when a new member is approved, unless designated to another member
- Serves as default point of contact for the TSC, CPC, and OpenJS Foundation on moderation logistics
The chair does not:
- Have a casting vote or veto on enforcement decisions
- Direct the outcome of any investigation
- Hold additional permissions beyond what any other moderator holds (per https://github.com/nodejs/admin/issues/1092)
Prior art
The Python PSF Code of Conduct Working Group designates chairs whose responsibilities include leading recertification, facilitating meetings, and ensuring the group delivers on its obligations to the PSF Board. Chairs are operational facilitators, not decision-makers.
The CNCF CoC Committee relies on Linux Foundation staff for operational coordination. We do not have equivalent staff support, which makes a volunteer chair role more necessary.
Election and term
The chair is elected yearly, tied to the annual recertification cycle:
- Recertification completes first. The team knows who opted in and was recertified.
- Any recertified member may self-nominate or nominate another (with consent). Nominations collected within 7 days.
- Consensus-seeking votes. Concerns escalated to the TSC.
- One-year term, starting at recertification, ending at the next.
If the chair does not recertify, the role is vacated automatically.
Vacancy
In the event of a vacancy, the team operates as peers, as we currently do, and report this gap to the TSC.
Open questions
- Is this role necessary, or can the team coordinate effectively without it? History would suggest the role is needed.
Action items
- Consensus on whether to create the role
- If accepted: elect the first chair
- Add the chair role to the Moderation Policy via PR
Assisted by: Claude Opus
- Linguagem predominante
- JavaScript
- Estrelas
- 202
- Forks
- 183
- Merge médio
- 13d 12h
- PRs com merge (30d)
- 2
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de nodejs/admin
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 90/100
-
tsc-agenda
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 30/100
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 30/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 35/100
Todas as issues de nodejs/admin
Issues semelhantes
-
Add: Digi 4K LogoAbertacheck:passed logos:add
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
component/administration domain/framework needs-triage Platform(Default) priority/low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 90/100
semantic-release/gitlab#1032 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
Mantenedores costumam responder em até 1 dia
-
[aw] Upgrade availableAbertaagentic-workflows
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 85/100
githubnext/gh-aw-workshop#3933 ·
Mantenedores costumam responder em até 1 dia