-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We just moved to the reactjs Github org #1392
Comments
This is a solid move for the future of Redux and the React ecosystem. Thanks @gaearon for all your hard work, and I can confidently say we're all looking forward to the future! |
🎉 |
awesome!!! |
what about Reselect? |
We haven’t talked to the authors yet so I haven’t moved it. Will be up to them. |
great move! |
awesome! |
|
seems like a great idea... I don't quite understand though how moving github orgs consistituets any sort of legal safety though. each project is still bound by their chosen license. also the intent twinges a bit when the organization you moved too is managed and owned by Facebook. are there any concert plans for governance? |
Ummm... what did I miss? |
@rossipedia Express was owned by Strongloop then Strongloop was acquired by IBM. Everyone wondered about the future of Express, but the Node foundation said they'll bring the project in house. |
By itself, it doesn’t mean anything other than React team recognizing these projects as important and giving them spotlight. There are plans to turn this into an independent legal entity but I can’t say more details at this point.
The
AFAIK Express was owned by a single person, later bought by a company. I just learned it is going to be part of Node Foundation but we want to avoid the whole debacle 😄 . The move to the Github org is only a start, as I said above. |
great 👍 |
🎉 |
@gaearon not a concern but more a need of more information. Not a critique. But ... While I agree on the need to act and to move to some foundation, I don't understand how reactjs can help. Why not apply here https://github.com/nodejs/TSC/tree/master/Applications ? Node.js seems to have a lot of experience in term of foundation, and is backed up with Linux one (hope I said nothing wrong) ! |
The move to http://github.com/reactjs is motivated by the fact that:
We don’t know the legal details yet. We are talking about this, and these talks take time. We’ll let everyone know when/if we announce a foundation or something else. In the meantime, think of http://github.com/reactjs as of a rebranding of http://github.com/rackt with React team’s approval but with the original maintainers and project owners in full control. It’s really nothing more than that. And it’s definitely not going to make “more React oriented”, “owned by Facebook” or anything. These concerns are baseless. If there is ever any intention of this (which there is not), I’ll transfer Redux to my personal account. I am still its author 😉 . |
I agree with this move wholeheartedly. Merging the Rackt family of projects to the reactjs org is great for the future of the React (..and JS) ecosystem, provided the legal aspects follow through as expected. I appreciate what @gaearon, @mjackson, @ryanflorence, and others are hoping to achieve. If Facebook does indeed help with the legal aspects of making sure the Rackt projects do not become IP of any one company, but instead are controlled by something such as a foundation, that would be quite excellent. Best of luck! |
I think we want modules there to be useful to React users and not just library authors. Modules like |
Fair enough |
great news 🎉 🍻 ! |
dig it |
really love the idea. Hope we will see more contributions to the reactjs family. thanks @gaearon for all the hard work (y) |
I'm going to directly quote @tomocchino as we started this:
|
🎉 Glad to see that https://github.com/reactjs/react-router-redux also moved. 👪 Many links such as http://rackt.github.io/react-tabs/example/ wil be broken for a while. (example from https://github.com/reactjs/react-tabs ) |
This is a great initiative. Would like to see recompose and redux-actions under this org as well. Both of these libraries are awesome for writing functional style react/redux apps. |
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 includedreact-router
, and every thirdnpm 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.
TL;DR
The text was updated successfully, but these errors were encountered: