chaos-mesh/rfcs

RFCs for changes to Chaos Mesh and its ecosystem

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

chaos-mesh/rfcs has 10+ stars and 20+ forks on GitHub and was last pushed on May 14, 2024. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Type:Documentation / SpecificationCategory(s):Documentation ToolsDeveloper Tools
Added to GitGenius on October 15th, 2026
Created on October 22nd, 2020
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 22
Total Stargazers: 14 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

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.