Governance & Roles
Updated February, 2026
Maintaining the Codewars ecosystem is a collaborative effort. The following roles define accountability and execution for kata maintenance:
- Strategic Community Experience Manager/Lead (MC): Senior stakeholder at Andela overseeing broader community strategy. MC advises on community sentiment, ensures communication aligns with Codewars & Andela values, and supports SB in final decision-making.
- Developer in Residence / Community Product Manager (SB): Reports to MC. Leads the improvement initiative, is the Lead Moderator Liaison, and makes final decisions on Tier 3/4 changes after considering moderator feedback.
- Moderators and Power Users: Identify and report issues, tag them with the appropriate Triage Tier, propose fixes via forks, and participate in review discussions.
- Kata Authors and Menders: Draft clear descriptions, ensure new content meets quality standards, and actively assist with migrating or fixing problematic legacy kata.
- Engineering / Platform Team (Future): Responsible for implementing tooling needed for issue tracking and Code enhancements. Triages tasks requiring codebase changes (e.g., potential future versioning support) and estimates effort.
The Discord Protocol & Archiving
Official policy shifts, 7-14 day consensus periods, and structural updates are facilitated in the #fixing or power-users Discord channels.
- Archiving: When major decisions occur in Discord, leadership must archive the key points and link them in an internal wiki to ensure institutional knowledge persists beyond chat history.