RFCs for changes to TiKV and its ecosystem
Clone or download
breeswish Merge pull request #16 from tikv/wrap80
80 characters per line is preferred
Latest commit 14ea9d6 Dec 5, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
text Format unified-key-format Nov 29, 2018
.travis.yml Ignore urls Nov 26, 2018
LICENSE Initial commit Aug 17, 2018
README.md Address comment Nov 28, 2018
template.md 80 characters per line is preferred Nov 22, 2018

README.md

TiKV 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 TiKV 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 should wrap line at 80 characters.

License

This content is licensed under Apachie License, Version 2.0, (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.