React Native would be a notable omission, unless it's included as part of React.
Relicensing React, Jest, Flow, and Immutable.js
21–30 of 528 posts
Re: Relicensing React, Jest, Flow, and Immutable.js
#22This is a very smart move by Facebook, and a win for the open source community as a whole. Why it took so long for the license change is a bit of a mystery, but removing the complications of software patents from their licenses will help further drive adoption and remove the precedent they were in danger of setting.
> Why it took so long for the license change is a bit of a mystery
Big organizations require more time and people to reach consensus at different hierarchical levels. Probably the legal department was the bottleneck.
Re: Relicensing React, Jest, Flow, and Immutable.js
#23Looks like React Native isn't included in the list for a license update.
What????
Re: Relicensing React, Jest, Flow, and Immutable.js
#24Death to asymmetrical patent clauses! Huge victory for OSS.
Was it asymmetrical? I thought it was a "we won't sue you for anything in this software, unless you sue us first". This change still allows them to sue you for any reason.
It’s asymmetrical in the sense that your license terminates even if you sue them for something that’s not in the software you’re using. I.e. they rip off your feature, and you’re using React, you’re f##d.
Re: Relicensing React, Jest, Flow, and Immutable.js
#25Kudos to Facebook and the React community for prompting this change, this was the right move.
Re: Relicensing React, Jest, Flow, and Immutable.js
#26Looks like React Native isn't included in the list for a license update.
That's what gets me. There's a very narrow list of packages that they've selected for the MIT treatment. Why isn't the blog post something along the lines of "We're re-licensing all of our open source libraries under the MIT License and removing their patent clauses"? It seems like they're still trying to play games, and are only buckling to the pressure for a tiny number of libraries.
Re: Relicensing React, Jest, Flow, and Immutable.js
#27What about GraphQL?
Waiting for update here https://github.com/facebook/graphql/issues/351
Re: Relicensing React, Jest, Flow, and Immutable.js
#28What about GraphQL?
"This shift naturally raises questions about the rest of Facebook's open source projects. Many of our popular projects will keep the BSD + Patents license for now."
Re: Relicensing React, Jest, Flow, and Immutable.js
#29Looks like React Native isn't included in the list for a license update.
That's what gets me. There's a very narrow list of packages that they've selected for the MIT treatment. Why isn't the blog post something along the lines of "We're re-licensing all of our open source libraries under the MIT License and removing their patent clauses"? It seems like they're still trying to play games, and are only buckling to the pressure for a tiny number of libraries.
My less cynical view (hope) maybe react-native isn't due for an update soon and they'll do it next time there's a version bump?
Re: Relicensing React, Jest, Flow, and Immutable.js
#30This is a very smart move by Facebook, and a win for the open source community as a whole. Why it took so long for the license change is a bit of a mystery, but removing the complications of software patents from their licenses will help further drive adoption and remove the precedent they were in danger of setting.
> Why it took so long for the license change is a bit of a mystery Big organizations require more time and people to reach consensus at different hierarchical levels. Probably the legal department was the bottleneck.
I suspect it also took time for the mounting discontent and for the number of voices to reach some kind of tipping point which then caused Facebook to begin the internal process of re-evaluating their licensing.
Either way, it's a good move.