Skip to content
master
Switch branches/tags
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

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 follow lint rules listed in markdownlint.

Run lints (you must have Node.js installed):

# Install linters: npm install
npm run lint

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.

About

RFCs for changes to TiKV and its ecosystem

Resources

License

Releases

No releases published

Packages

No packages published