Skip to content

The state of the React Native Community in 2018

updated

The React Native blog has published a review of how the React Native Community changed the way the project is developed and discussed during 2018. The post notes the excitement about the architecture rewrite known as Fabric, which together with JSI and TurboModules is meant to address fundamental limitations in React Native, and calls empowering the community the biggest shift of the year.

Releases in the open

In January the community created the react-native-releases repository. It lets anyone follow upcoming releases collaboratively and propose cherry-picks for a given version, as happened for 0.57.8 and the releases before it. According to the post, this repository was a driving force behind dropping the monthly release cycle in favor of the "long term support" approach now used for 0.57.x.

An RFC process for React Native

In July the discussions-and-proposals repository followed. Previously, broader conversations lived in issues labelled For Discussion in the main repository; the new repo moves toward an RFC process similar to the one used by React. The post notes that the Facebook team now uses this community RFC process to discuss possible improvements to React Native and to coordinate work on the Lean Core project, among other topics.

Easier ways to keep up

Acknowledging that communication about these efforts had not been as effective as intended, the community launched a new account, @ReactNativeComm, to share news on releases and active discussions. For those not on that social network, the post suggests watching the relevant GitHub repositories, noting that GitHub now allows notifications for releases only.

Guidelines for the community organization

Over the past several months, core contributors have used the React Native Community GitHub organization to take more ownership of React Native's development and to collaborate more closely with Facebook. What has been missing is a formal structure. The plan is for the organization to enforce a shared set of standards for the packages and repositories it hosts, and to give maintainers a single place to help one another and contribute code that follows community-agreed standards. These guidelines are expected to be in place in early 2019, and feedback is being collected in a dedicated discussion.

Looking ahead

The post frames these steps as groundwork for a more collaborative path toward a 1.0 release, and invites developers to take part in the repositories above.

Source: reactnative.dev