News for hackers. Stuff that matters.
Re:Relicensing React, Jest, Flow, and Immutable.js by adambrenecki on Friday September 22, 2017 @06:08PM (#15316318)
Wait, so they're replacing a license that has a dodgy patent grant that everyone distrusted, with a license that doesn't have a patent grant at all? Why not Apache?
Re:Relicensing React, Jest, Flow, and Immutable.js by JelteF on Saturday September 23, 2017 @05:25AM (#15318940)
To quote a comment in a similar thread, apparently there's such a thing as an implied patent license:

Implied patent licenses:

https://www.wilmerhale.com/pages/publicationsandnewsdetail.a....

https://copyleft.org/guide/comprehensive-gpl-guidech7.html

Basically, if you sell or license a product that requires a patent to work, courts have generally held that you grant an implied patent license for any patents that the product might require. If you explicitly reference patents within the license, however, then whatever terms you explicitly write into the license supersede this implied patent license. BSD+patents (and Apache 2) have explicit patent language; paradoxically, this makes them more restrictive than licenses like MIT, BSD, or GPL that don't mention patents at all.

Re:Relicensing React, Jest, Flow, and Immutable.js by JamesFM on Friday September 22, 2017 @06:23PM (#15316433)
Yeah, exactly, what does this actually accomplish besides putting the user in a worse situation where they are no longer given any sort of patent grant?
Re:Relicensing React, Jest, Flow, and Immutable.js by matthewmacleod on Friday September 22, 2017 @06:27PM (#15316468)
At least it might give the louder parts of the community that have been consistently complaining about this issue a good reason to stop shouting quite as much
Re:Relicensing React, Jest, Flow, and Immutable.js by Spivak on Friday September 22, 2017 @09:06PM (#15317400)
Because an unspecified parent grant is most likely an implied patent grant, and especially for FOSS there is a very strong case since your are explicitly permitted to study, modify, and use any part of the code.
Re:Relicensing React, Jest, Flow, and Immutable.js by chrisco255 on Friday September 22, 2017 @07:39PM (#15316930)
Probably because they have no patents that cover the concepts these libraries introduce. Perhaps wit some of the others they will go Apache v2. People have been so worked up by the FUD that Facebook can't even relicense under MIT one of the de facto open source licenses without being met with suspicion.
Re:Relicensing React, Jest, Flow, and Immutable.js by magicalist on Friday September 22, 2017 @09:37PM (#15317507)
> Probably because they have no patents that cover the concepts these libraries introduce.

Apache 2.0 certainly doesn't require you to have patents in order to use it ("applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s)")

Re:Relicensing React, Jest, Flow, and Immutable.js by ergo14 on Saturday September 23, 2017 @03:43AM (#15318689)
They have the patent: https://www.google.com/patents/US20170221242. Just MIT is a good option, I don't really understand why they don't want to "fix" the patent grant to be like Apache 2.0 or Google's. Why relicense everything when fixing 1 sentence would fix the problem completely.