Chaos Mesh RFCs is a request-for-comments process repository that manages substantial design decisions and feature proposals for Chaos Mesh and its ecosystem.
The repository addresses the need to formalize how major changes enter the project. Rather than treating all contributions identically, it establishes a structured design process for substantial changes that require community consensus. Contributors submit proposals by copying a template, writing a design document, and opening a pull request. Discussion and revision follow, with merging or closure occurring once at least two project maintainers reach consensus on the direction.
Teams adopting this RFC process should understand it is designed for substantial changes only—routine bug fixes and documentation improvements continue through normal pull request workflows. This approach suits projects with multiple stakeholders who need confidence in architectural direction and want to avoid rework from misaligned designs. The process requires maintainers to actively review and reach explicit consensus, making it most effective for projects with engaged leadership and a community invested in long-term direction.
The project maintains markdown linting standards via markdownlint rules to ensure consistent documentation quality. RFC submissions follow a defined timeline from initial pull request through discussion and revision to final consensus-based resolution. The repository enforces structural consistency through a template-based submission process and requires Node.js for running linting checks.