5 ms·
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
by CydeWeys 9y ago
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.
- randall 9y agoMy 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?
- CydeWeys 9y agoYou don't need to update anything else besides the license when changing the license, though? There's no version bump required.
- cesarb 9y agoIsn't the license file part of the distributed .tar.gz, packaging metadata, and other release artifacts? It's bad form to change the contents of a release after it's distributed. So even a small change like that would require a (minor) version bump.
- sebastianmck 9y agoSee the fourth paragraph. > 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. We're evaluating those projects' licenses too, but each project is different and alternative licensing options will depend on a variety of factors.
- CydeWeys 9y agoSo the list of packages they're truly open sourcing is intentionally small, then. They're only truly open sourcing the ones that are very popular and that had a huge amount of outcry over the license. That makes it worse.
- Kilenaitor 9y ago> That makes it worse. In what way does re-licensing their most popular packages make it worse? It says they're evaluating. Doesn't say no and as demonstrated here it doesn't mean they wont change their mind later.
- s73ver_ 9y agoWhat more is there to evaluate, though? What is different between React, which did get the relicense, and React Native, which didn't?
- CydeWeys 9y agoYou didn't interpret my comment correctly. What is worse is that the narrowly selected range of projects to re-license is intentional rather than unintentional. They're only fixing the patent clauses on the bare minimum that they feel is necessary due to outrage. That means that they'd rather not but they're being forced into it. It'd be different if they were deciding to re-license everything; that might indicate an actual change of heart.
- wolco 9y agoWhat worries many is that they may change the license at a later
- irrational 9y agoIt creates continued uncertainty. If all the tools/libraries in the React ecosystem (such as React Native) don't all have the license, then we will probably stay the course with Vue. While Vue is amazing, React has a larger ecosystem. But if that entire ecosystem isn't available due to licenses then we might as well stick with Vue.
- 9y ago