Project: Chaos Mesh (Observability and Analysis / Chaos Engineering)
File: GOVERNANCE.md

Chaos Mesh is a meritocratic, consensus-based community project. Anyone with an interest in the project can join the community, contribute to the project design and participate in the decision making process. This document describes how that participation takes place and how to set about earning merit within the project community. Contributors are community members who contribute in concrete ways to the project. Anyone can contribute to the project and become a contributor, regardless of their skillset. There is no expectation of commitment to the project, no specific skill requirements, and no selection process. There are many ways to contribute to the project, which may be one or more of the following (but not limited to): Reporting or fixing bugs. Identifying requirements, strengths, and weaknesses. Improving the Chaos Mesh website. Writing documentation. Joining discussions on , our community Slack channel , or at . Evangelizing about the project (e.g. a link on a website or word-of-mouth awareness raising). For first-time contributors, its recommended to start by going through , and joining our community Slack channel. As one continues to contribute to the project and engage with the community, he/she may at some point become eligible for a Chaos Mesh Member. Chaos Mesh are continuously active contributors in the community. There are multiple ways to stay "active" and engaged with us - contributing to codes, raising issues, writing tutorials and case studies, and even answering questions. To become a Chaos Mesh member, you are expected to: Have made multiple contributions, which may be one or more of the following (but not limited to): Authored PRs on GitHub. Filed, or commented on issues on GitHub. Join community discussions (e.g. community meetings, Slack). Sponsored by at least 1 Chaos Mesh . Contributors that meet the above requirements will then be invited to the GitHub organization "Chaos Mesh" by a sponsor, and there would be an announcement published in the slack channel . Members are expected to respond to issues and PRs assigned to them, and be the owners of the code or docs they have contributed. Members that have not contributed to the project or community in any way in over 6 months will lose their membership. As one gains experience and familiarity with the project and as their commitment to the community increases, they may find themselves being nominated for committership at some stage. Committers are active community members who have shown that they are committed to the continuous development of the project through ongoing engagement with the

Committership allows contributors to more easily carry on with their project-related activities by giving them direct access to the projects resources. Typically, a potential committer needs to show that they have a sufficient understanding of the project, its objectives, and its strategy. To become a committer, you are expected to: Be a Chaos Mesh member. Express interest to the existing maintainers that you are interested in becoming a committer. Have contributed 6 or more substantial PRs. Have an above-average understanding of the project codebase, its goals, and directions. Members that meet the above requirements will be nominated by an existing maintainer to become a committer. It is recommended to describe the reasons for the nomination and the contribution of the nominee in the PR. The existing maintainers will confer and decide whether to grant committer status or not. Committers are expected to review issues and PRs. Their LGTM counts towards the required LGTM count to merge a PR. While committership indicates a valued member of the community who has demonstrated a healthy respect for the projects aims and objectives, their work continues to be reviewed by the community before acceptance in an official release. A committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become a maintainer. This role is described below. Maintainers are first and foremost committers that have shown they are committed to the long term success of a project. They are the planners and designers of the Chaos Mesh project. Maintainership is about building trust with the current maintainers of the project and being a person that they can depend on to make decisions in the best interest of the project in a consistent manner. Committers wanting to become maintainers are expected to: Enable adoptions or ecosystems. Collaborate well. Demonstrate a deep and comprehensive understanding of Chaos Mesh's architecture, technical goals, and directions. Actively engage with major Chaos Mesh feature proposals and implementations. A new maintainer must be nominated by an existing maintainer. The nominating maintainer will create a PR to update the . It is recommended to describe the reasons for the nomination and the contribution of the nominee in the PR. Upon consensus of incumbent maintainers, the PR will be approved and the new maintainer becomes active. If a maintainer is no longer interested or cannot perform the maintainer duties listed above, they should volunteer to be moved to . In extreme cases this can also occur by a vote of the maintainers per the voting process, as mentioned

PRs may be merged only after receiving at least two approvals (LGTMs) from committers or maintainers. However, maintainers can sidestep this rule under justifiable circumstances. For example: If a CI tool is broken, may override the tool to still submit the change. Minor typos or fixes for broken tests. The change was approved through other means than the standard process. Ideally, all project decisions are resolved by consensus via a PR or GitHub issue. Any of the day-to-day project maintenance can be done by a . Community or project level decisions such as RFC submission, creating a new project, maintainer promotion, and major updates on GOVERNANCE must be brought to broader awareness of the community via community meetings, GitHub discussions, and slack channels. A supermajority (2/3) approval from Maintainers is required for such approvals. In general, we prefer that technical issues and maintainer membership are amicably worked out between the persons involved. If a dispute cannot be decided independently, the maintainers can be called in to resolve the issue by voting. For voting, a specific statement of what is being voted on should be added to the relevant github issue or PR, and a link to that issue or PR added to the maintainers meeting agenda document. Maintainers should indicate their yes/no vote on that issue or PR, and after a suitable period of time, the votes will be tallied and the outcome noted. Decision making must comply with the . We use a Request for Comments (RFC) process for any substantial changes to Chaos Mesh. This process involves an upfront design that will provide increased visibility to the community. If you're considering a PR that will bring in a new feature that may affect how Chaos Mesh is implemented, or may be a breaking change, then you should start with a RFC. The process is documented in the and has for you to get started. The following table describes how the nomination is approved. | Nomination | Description | Approval | Binding Roles | Minimum Length (days) | | :-- | :- | : | :-- | :-- | | New Member | When a new member is proposed, should be only nominated by a committer. | | Active committers or maintainers | 3 | | New Committer | When a new committer is proposed, should be only nominated by a maintainer. | | Active maintainers | 7 | | New Maintainer | When a new maintainer is proposed, should be only nominated by a maintainer. | Supermajority (2/3) Approval | Active maintainers | 7 |