amirho/react.dev
1
0
Fork 0
mirror of https://github.com/reactjs/react.dev.git synced 2026-02-23 20:23:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Blog post about new RFC process

Browse Source
This commit is contained in:
Andrew Clark
2017-12-06 17:31:50 -08:00
parent 24acf2f8f2
commit a9df1c5e67
1 changed files with 39 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
content/blog/2017-12-07-introducing-the-react-rfc-process.md Normal file
View File

@@ -0,0 +1,39 @@
---
title: "Introducing the React RFC Process"
author: [acdlite]
---
We're adopting an RFC ("request for comments") process for contributing ideas to React.
Inspired by [Yarn](https://github.com/yarnpkg/rfcs), [Ember](https://github.com/emberjs/rfcs), and [Rust](https://github.com/rust-lang/rfcs), the goal is to allow React core team members and community members to collaborate on the design of new features. It's also intended to provide a clear path for ideas to enter the project:
- Create an RFC document detailing your proposal.
- Submit a PR to the [RFC repository](https://github.com/reactjs/rfcs).
- Incorporate feedback into the proposal.
- After discussion, the RFC may be accepted for implementation by the core team.
A more thorough description is available in the repository's [README](https://github.com/reactjs/rfcs/blob/master/README.md). The exact details may change in the future as we continue to refine our process.
## Who Can Submit RFCs?
Anyone! No knowledge of React's internals is required, nor are you expected to implement the proposal yourself.
As with our other repositories, we do ask that you complete a [Contributor License Agreement](https://github.com/reactjs/rfcs#contributor-license-agreement-cla) before we can accept your PR.
## What Types of Changes Should Be Submitted As RFCs?
Generally, any idea that would benefit from additional review or design before being implemented is a good candidate for an RFC. As a rule of thumb, this means any proposal that adds, changes, or removes a React API.
Not every change must go through the RFC process. Bug fixes or performance improvements that don't touch the API can be submitted directly to the main library.
We now have several different repositories for contributing improvements to React:
- **Issues, bugfixes, and code changes to the main library**: [facebook/react](https://github.com/facebook/react)
- **Website and documentation**: [reactjs/reactjs.org](https://github.com/reactjs/reactjs.org)
- **Ideas for changes that need additional review before being implemented**: [reactjs/rfcs](https://github.com/reactjs/rfcs)
## RFC for A New Context API
Coinciding with the launch of our RFC process, we've submitted a [proposal for a new version of context](https://github.com/reactjs/rfcs/pull/2). The proposal has already received many valuable comments from the community that we will incorporate into the design of the new API.
The context PR is a good example of how a typical RFC should be structured. We're excited to start receiving your proposals!