Growing Your Code of Conduct as Your Project Scales
How to evolve your code of conduct as your project grows from a few contributors to a large community. Covers milestones, expansion strategies, and community involvement.
Detailed Explanation
Growing Your Code of Conduct
A code of conduct is a living document that should evolve with your community. What works for 5 contributors is insufficient for 500, and what works for 500 may be too bureaucratic for 5.
Growth Milestones
Stage 1: Solo / Small Team (1-10 contributors)
- Minimal code of conduct is sufficient
- Single maintainer handles reports
- Focus: setting the tone early
Stage 2: Growing Community (10-50 contributors)
- Adopt a standard template (Contributor Covenant recommended)
- Add a second person to handle reports
- Create reporting email alias
- Focus: formalizing expectations
Stage 3: Established Project (50-200 contributors)
- Form a 3-5 person enforcement committee
- Add detailed enforcement guidelines
- Document incident response procedures
- Create transparency reports
- Focus: professional enforcement
Stage 4: Large Community (200+ contributors)
- Expand committee to 5-7 members with fixed terms
- Add appeal process
- Consider paid community management
- Conduct annual CoC reviews
- Focus: scaling and sustainability
Revision Process
When updating your code of conduct:
- Announce the revision — Give the community notice (30+ days)
- Gather feedback — Open a discussion period for comments
- Draft changes — Incorporate feedback into proposed changes
- Community vote — For major changes, consider a community vote
- Publish with changelog — Document what changed and why
- Grace period — Allow 30 days for community members to review
What to Add at Each Stage
| Stage | Add | Remove |
|---|---|---|
| 1 → 2 | Standard template, reporting email | Informal "be nice" statement |
| 2 → 3 | Committee, enforcement tiers, incident response | Single-person enforcement |
| 3 → 4 | Appeal process, transparency reports, paid staff | Ad-hoc processes |
Community Involvement
Your code of conduct is more effective when the community feels ownership:
- RFC process — Major changes go through a Request for Comments period
- Annual survey — Ask the community if the CoC meets their needs
- Public incidents — Share lessons learned (anonymized) to build understanding
- New contributor input — Ask newcomers what made them feel welcome (or not)
Use Case
Maintainers of growing open source projects who need to plan how their code of conduct and enforcement infrastructure should evolve as the community expands from a handful of contributors to hundreds.