Some important changes in Strapi require some thoughts to be put into the design phase before starting working on a PR.
The RFC (Request For Comments) process will help us create consensus among the core team and include as much feedback as possible from the community, for these upcoming changes.
xxxx-template.md
(leave the xxxx at the beginning) file to the rfcs folder.Once an RFC becomes active, then authors may implement it and submit the feature as a pull request to the Strapi repository.
A RFC being 'active' does not necessarily mean the feature will ultimately be merged; it does mean that the core team has agreed to it in principle and are open to merging it.
Furthermore, the fact that a given RFC has been accepted and is 'active' implies nothing about what priority is assigned to its implementation, nor whether anybody is currently working on it.
Each week the team will attempt to review some portion of then open RFC pull requests.
Strapi's RFC process owes its inspiration to the React RFC process, Yarn RFC process, Rust RFC process, and Ember RFC process