From 239ac3970db28d2c13dbc49a536281a7c84ad07d Mon Sep 17 00:00:00 2001 From: Sidhartha Chatterjee Date: Wed, 19 Feb 2020 01:18:15 +0530 Subject: [PATCH] docs(blog): Add new RFC process in latest Gazette (#21561) * Add details for new RFC process * Update docs/blog/2020-02-18-gazette-2019-recap/index.md --- docs/blog/2020-02-18-gazette-2019-recap/index.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/blog/2020-02-18-gazette-2019-recap/index.md b/docs/blog/2020-02-18-gazette-2019-recap/index.md index 7f0e61d348d96..7014e0294d20f 100644 --- a/docs/blog/2020-02-18-gazette-2019-recap/index.md +++ b/docs/blog/2020-02-18-gazette-2019-recap/index.md @@ -156,6 +156,12 @@ We started off this year on a solid note with the release of [Gatsby Builds](/bl [Ward Peeters](https://twitter.com/wardpeet) built the new Gatsby Jobs API which enables Gatsby to better distribute CPU intensive work like image processing and HTML generation to workers on local machines and the Cloud. +### New RFC Process + +[Dustin Schau](https://twitter.com/SchauDustin) proposed a new RFC process late last year. The main difference is that we'll be creating a new, top-level `rfcs` folder within the [gatsbyjs/gatsby](https://github.com/gatsbyjs/gatsby) monorepo and deprecate the old [gatsbyjs/rfcs](https://github.com/gatsbyjs/rfcs) repo. + +The main goal is to improve visibility and encourage more community engagement. Read more about [the new RFC process](https://github.com/gatsbyjs/rfcs/blob/master/text/0011-move-rfcs-to-monorepo.md) in its RFC. 😉 + ## What's next? You might've noticed a trend in our work last year. Lots of it focussed on foundational improvements to Gatsby unlocking even bigger DX wins and new features that were just _not_ possible before.