https://github.com/chaos-mesh/rfcs

RFCs for changes to Chaos Mesh and its ecosystem
https://github.com/chaos-mesh/rfcs

Last synced: 6 days ago
JSON representation

RFCs for changes to Chaos Mesh and its ecosystem

• Host: GitHub
• URL: https://github.com/chaos-mesh/rfcs
• Owner: chaos-mesh
• License: apache-2.0
• Created: 2020-10-22T01:54:31.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2023-01-02T03:02:02.000Z (almost 2 years ago)
• Last Synced: 2023-03-03T20:09:56.306Z (over 1 year ago)
• Homepage:
• Size: 156 KB
• Stars: 16
• Watchers: 11
• Forks: 22
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Chaos Mesh RFCs

Many changes, including bug fixes and documentation improvements can be

implemented and reviewed via the normal GitHub pull request workflow.

Some changes though are "substantial", and we ask that these be put through a

bit of a design process and produce a consensus among the Chaos Mesh community.

The "RFC" (request for comments) process is intended to provide a consistent

and controlled path for new features to enter the project, so that all

stakeholders can be confident about the direction the project is evolving in.

## How to submit an RFC

1. Copy `template.md` into `text/YYYY-MM-DD-my-feature.md`.

2. Write the document and fill in the blanks.

3. Submit a pull request.

## Timeline of an RFC

1. An RFC is submitted as a PR.

2. Discussion takes place, and the text is revised in response.

3. The PR is merged or closed when at least two project maintainers reach

   consensus.

## Style of an RFC

We follow lint rules listed in

[markdownlint](https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md).

Run lints (you must have [Node.js](https://nodejs.org) installed):

```bash

# Install linters: npm install

npm run lint

```

## License

This content is licensed under Apache License, Version 2.0,

([LICENSE](LICENSE) or http://www.apache.org/licenses/LICENSE-2.0)

## Contributions

Unless you explicitly state otherwise, any contribution intentionally submitted

for inclusion in the work by you, as defined in the Apache-2.0 license, shall

be dual licensed as above, without any additional terms or conditions.