Addressing Moderator Burnout: Tooling, Guidance, and Resource Support #572

New issue

Open

opened 2026-07-06 16:52:12 +00:00 by jflory7 · 0 comments

jflory7 commented

2026-07-06 16:52:12 +00:00

Owner

Summary

Initiate a Council-led strategy to formally resource, support, and empower Fedora's community moderators across collaboration platforms.

Background

Community moderators perform critical, high-stress volunteer labor. They have to interpret the Code of Conduct, manage disputes, and maintain the psychological safety required for open technical debate. Currently, this labor is often siloed and under-supported. Moderators lack formalized, project-wide escalation pathways, tailored tooling, and dedicated resource commitments (e.g., money, people, time). As the project scales, treating moderation as an ad-hoc volunteer effort rather than a core infrastructure requirement risks severe burnout and threatens the health of our community spaces.

Details

Because this ticket does not start with a predetermined solution, we need collaborative shaping. The required steps are:

Discovery: The Council hosts a structured discussion with active community moderators to identify their most critical resource gaps and friction points (e.g., tooling limitations, CoC interpretation guidance, escalation needs).
Drafting: The Council drafts a formal proposal, which includes how other Fedora teams/SIGs can actively support community moderation, establishing clear escalation pathways and resource allocations.
Execution & Accountability: The Council takes formal ownership of driving and executing the finalized proposal, ensuring the identified solutions and resources are actually delivered to the moderation teams.

Summary

Fedora community moderators receive the structured support, resources, and leadership backing required to maintain safe, open collaboration spaces without suffering from burnout.

### Summary Initiate a Council-led strategy to formally resource, support, and empower Fedora's community moderators across collaboration platforms. ### Background Community moderators perform critical, high-stress volunteer labor. They have to interpret the Code of Conduct, manage disputes, and maintain the psychological safety required for open technical debate. Currently, this labor is often siloed and under-supported. Moderators lack formalized, project-wide escalation pathways, tailored tooling, and dedicated resource commitments (e.g., money, people, time). As the project scales, treating moderation as an ad-hoc volunteer effort rather than a core infrastructure requirement risks severe burnout and threatens the health of our community spaces. ### Details Because this ticket does not start with a predetermined solution, we need collaborative shaping. The required steps are: 1. **Discovery**: The Council hosts a structured discussion with active community moderators to identify their most critical resource gaps and friction points (e.g., tooling limitations, CoC interpretation guidance, escalation needs). 2. **Drafting**: The Council drafts a formal proposal, which includes how other Fedora teams/SIGs can actively support community moderation, establishing clear escalation pathways and resource allocations. 3. **Execution & Accountability**: The Council takes formal ownership of driving and executing the finalized proposal, ensuring the identified solutions and resources are actually delivered to the moderation teams. ### Summary Fedora community moderators receive the structured support, resources, and leadership backing required to maintain safe, open collaboration spaces without suffering from burnout.

👀 1