Description
Hi folks. (TL;DR is at the bottom.)
We have moved Redux, React Router and other community projects over to reactjs Github org.
We did this because in the future, we want to ensure Redux and related projects don’t end up like Express. We would like a separate legal entity (such as a foundation) to own that code. This is a work in progress and I can’t give you exact details but ensuring those libraries are well cared for and don’t end up as some company’s property (including Facebook itself) is the goal.
You might have noticed that reactjs has never been the home of React itself. React lives under the facebook org because it is Facebook’s project.
On the other hand, reactjs was meant for community projects such as react-rails. I think we can all agree that React Router, Redux, and a few other Rackt libraries deserve to be there, as they are most widely used together with React. In January 2016, every second npm install react also included react-router, and every third npm install react also included Redux.
We want reactjs to be the home for projects that are widely depended upon in the React ecosystem, whether or not they depend on React itself. This is why Redux, while technically independent on React, ends up there. The examples and the documentation have always been oriented at React users, so it shouldn’t come as a big surprise that we want to be closer to the React community.
In no way will this impact the technical direction of Redux core. We are not going to suddenly force you to sign up for Facebook or introduce a React dependency to the core. It is sufficient to read the source code for the core to understand that this wouldn’t make any sense. For example, we are enthusiastic about Redux being adopted by the Angular community as well as by Angular-specific takes on Redux.
This move was made because @ryanflorence, @mjackson, me, and other contributors wanted to ensure that Rackt family of projects doesn’t end up as IP of some single company. We are talking to Facebook, and they might help us through the legal hurdles of ensuring this.
Finally, all collaborators on the Rackt team should have received their invitations to the reactjs org. If we messed up the permissions and something doesn’t work that used to work, please ping me in DM on Twitter or via email, and we’ll make this right.