|
You gave an impressively long comment, but here are my two cents: There’s no precedent to set here. There’s already a license for BSD+PATENT, and it’s called Apache license. Is Apache setting a bad precedent as well? Additionally, it’s not like companies licensing open source work under customized license is uncommon — tons of software do that, and Facebook is by no means the first. For example, OpenJDK customized GPL by adding a classpath exemption. Why then, do you need to give Facebook special treatment, and make this look like a dangerous slippery slope? Oh yeah, because Facebook is a evil megacorp that’s “hostile to the open web”. How is this, as part of a discussion about the license, “completely and utterly pointless”? This whole argument could be summarized into we want GPL, react’s license is not GPL (“In WP we take no exceptions to GPL compliance”). That’s it. Instead, you have to point to supposedly evil motives behind putting the PATENT file there, and yes, I’ll say it, using not-so-true arguments to spread FUD and perform a character assassination. It’s ridiculous. |
I don't understand how anyone complaining about the FB patent grant could honestly bet the farm on any implicit grants in BSD/MIT style licenses. The only logical conclusion if you're that scared of patents is to avoid anything without an explicit patent grant, i.e. sticking to Apache, GPL and friends.