From a9df1c5e67abc5a952cbbdd5571cf5ada2130891 Mon Sep 17 00:00:00 2001 From: Andrew Clark Date: Wed, 6 Dec 2017 17:31:50 -0800 Subject: [PATCH 1/4] Blog post about new RFC process --- ...12-07-introducing-the-react-rfc-process.md | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 content/blog/2017-12-07-introducing-the-react-rfc-process.md diff --git a/content/blog/2017-12-07-introducing-the-react-rfc-process.md b/content/blog/2017-12-07-introducing-the-react-rfc-process.md new file mode 100644 index 00000000..cc226ec6 --- /dev/null +++ b/content/blog/2017-12-07-introducing-the-react-rfc-process.md @@ -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! From 4949bb02190f7a47634b2cb61d63e559d08a1906 Mon Sep 17 00:00:00 2001 From: Andrew Clark Date: Wed, 6 Dec 2017 18:19:28 -0800 Subject: [PATCH 2/4] Clarify what it means when an RFC is accepted --- content/blog/2017-12-07-introducing-the-react-rfc-process.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/blog/2017-12-07-introducing-the-react-rfc-process.md b/content/blog/2017-12-07-introducing-the-react-rfc-process.md index cc226ec6..3b0b54bd 100644 --- a/content/blog/2017-12-07-introducing-the-react-rfc-process.md +++ b/content/blog/2017-12-07-introducing-the-react-rfc-process.md @@ -10,9 +10,10 @@ Inspired by [Yarn](https://github.com/yarnpkg/rfcs), [Ember](https://github.com/ - 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. +- After discussion, the RFC may or may not be accepted by the core team. +- If the RFC is accepted, the PR is merged. -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. +RFCs are accepted when they are approved for implementation in React. A more thorough description of the process is available in the repository's [README](https://github.com/reactjs/rfcs/blob/master/README.md). The exact details may be refined in the future. ## Who Can Submit RFCs? From 867e8f1dc62a781ad8864852213c84d616d3d88e Mon Sep 17 00:00:00 2001 From: Andrew Clark Date: Thu, 7 Dec 2017 07:54:34 -0800 Subject: [PATCH 3/4] Reword sentence about contributing to different repos --- content/blog/2017-12-07-introducing-the-react-rfc-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2017-12-07-introducing-the-react-rfc-process.md b/content/blog/2017-12-07-introducing-the-react-rfc-process.md index 3b0b54bd..c3e9b1a0 100644 --- a/content/blog/2017-12-07-introducing-the-react-rfc-process.md +++ b/content/blog/2017-12-07-introducing-the-react-rfc-process.md @@ -27,7 +27,7 @@ Generally, any idea that would benefit from additional review or design before b 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: +We now have several repositories where you can submit contributions 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) From f8e7fc6b0c62d17df29933b9df85c9561bfb9f1d Mon Sep 17 00:00:00 2001 From: Andrew Clark Date: Thu, 7 Dec 2017 07:57:24 -0800 Subject: [PATCH 4/4] Passive -> active voice --- content/blog/2017-12-07-introducing-the-react-rfc-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2017-12-07-introducing-the-react-rfc-process.md b/content/blog/2017-12-07-introducing-the-react-rfc-process.md index c3e9b1a0..595b7f37 100644 --- a/content/blog/2017-12-07-introducing-the-react-rfc-process.md +++ b/content/blog/2017-12-07-introducing-the-react-rfc-process.md @@ -10,7 +10,7 @@ Inspired by [Yarn](https://github.com/yarnpkg/rfcs), [Ember](https://github.com/ - 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 or may not be accepted by the core team. +- After discussion, the core team may or may not accept the RFC. - If the RFC is accepted, the PR is merged. RFCs are accepted when they are approved for implementation in React. A more thorough description of the process is available in the repository's [README](https://github.com/reactjs/rfcs/blob/master/README.md). The exact details may be refined in the future.