This appears to remove that language and creates the much more desirable balanced situation you are talking about (IANAL).
But I don't see how the original license was somehow worse than the open source projects that use the MIT or BSD licenses without any patent license, thus potentially allowing the patent owner to use patents against you offensively or defensively. (As far as I know, it is still unresolved whether the MIT or BSD licenses include an implied grant of patent rights, but at the very least there would be serious legal uncertainty.)
For one example, see the license on this Google project: https://github.com/google/trace-viewer/blob/master/LICENSE. No mention of patent rights, and unless you could successfully argue that there was an implied license, Google could sue a user for patent infringement for using this software (not that Google has ever used patents offensively, to my knowledge). So it confused me to see a Google employee complaining in the other thread that they weren't allowed to use Facebook open source software due to the limited patent grant. I'd be really interested to know more about this policy.
https://www.fenwick.com/FenwickDocuments/potential_defenses....
http://ipmall.info/hosted_resources/sipla/sipla_2005/raviche...
It's not really unresolved. There are dreamers who believe it's not the case. For everyone else, it's clearly the case until proven otherwise. There is a ton of case law on implied licenses. To believe it would simply not apply to software when it applies to every other area in which there are patents, for some magical unknown reason is ... strange and weird legal thinking?
In some cases, Google uses a BSD-style license with a separate PATENTS file. For example, here are the PATENTS files for Go [1] and Dart [2]. Apache 2 is also common and it includes a patent grant.
[1] https://go.googlesource.com/go/+/master/PATENTS [2] https://code.google.com/p/dart/source/browse/branches/bleedi...
Where the original patent license was perhaps "worse", in an ethical if not legal way, than no license at all, was that its limitations were non-obvious, and there was a feeling, right or wrong, that Facebook were attempting to restrict developers' rights by stealth. Licenses without any patent grant are problematic and uncertain, but they are at least problematic and uncertain in an obvious way, if that makes sense.
The original patent license felt akin to the Microsoft's early attempts at "shared source" versions of their libraries and frameworks, where just reading the source code could theoretically curtail developers' ability to work on open source implementations.
I think it's natural that people will react more negatively and forcibly to these kind of apparent bad-faith actions than to simple omissions. Furthermore, taking an aggressive stand against these sort of license tripwires hopefully makes it much less likely that others will attempt to insert similar clauses in future.
> the original language, which was that the license would be terminated if you attempted to invalidate one of Facebook's patents
That clause is the exact reason many of us saw the old patent terms as being offensive rather than defensive. Why would it be valuable to Facebook to prevent people from arguing that their patents are invalid, if they weren't planning to sue for infringement of those patents? Facebook's calling the new terms "clearer" but the clause that they removed seemed pretty unambiguous in its intent.
It's like saying Facebook can use all Google's patent, from search engines, Androids, Google car, etc. All because Google use React in a single presentation page.
It's even more viral than GPL. At least with GPL, your code only becomes infected with GPL in derived works. But Facebook has all access to even your unrelated patents.
If I'm doing a startup, this clause is no issue. If I actually have patent assets, this seems like a non-starter still.
I can understand people getting upset about that. It seems hardly a small limitation.
I wouldn't agree to terms of use that mean I cannot point out that an unrelated idea was previously thought of.
Let the lawyers argue about the patents; I don't want to accidentally hobble the ones on my side or arm the ones on the other side, I don't want to accidentally harm other open-source contributors, I'd rather not be involved at all.
(In the BSD vs GPL debate I'm pro-GPL, but not GPLv3, because it involves the patents...)
But I'm confused by your statement that you want the license not to mention patents because you want to leave patent issues to the lawyers. The license isn't software code, it's legal code--it's what the lawyers are arguing about!
If the license doesn't mention patents (and doesn't imply a particular grant of patent rights, which like I said is an open issue), then you haven't chosen "nothing." You've chosen the default: the patent holder retains all rights.
It seems that any variation either hurts my defense or comes off as aggressive (which is what happened to facebook).
In a hypothetical situation where the patent language matters, it's total war. Multiple concurrent lawsuits in opposite directions, ITC injunction requests, etc. Maximum pain to make the opponent capitulate. None of these patents are really valid anyway, it's either math or implementation detail. There's no reason or logic here.
Better to make no statement, leave the default unsaid, and stick your head in the sand, it may keep you under the radar of involvement.
As an illustrative example of what can happen when some third-party profiteers file for patents on your software while re-selling it themselves, read up on the JMRI project's legal troubles:
http://jmri.sourceforge.net/k/summary.shtml http://lwn.net/Articles/181261/ http://lwn.net/Articles/294066/
That's why my preference is for licenses that explicitly deal with patents: ALv2, MPLv2, (L)GPLv3.
Was there any language in the license that bound Facebook to defensive use only and not offensive? Because otherwise this seems to be reading a lot of good intent into a place where none might be deserved.
Two important limitations--the original license terminated if you argued that a Facebook patent was invalid or tried to use patents defensively against them (this has been fixed in the new license, as far as I can tell), and Facebook can still sue you for patent infringement for something other than using React.
[1] https://github.com/facebook/react-native/blob/6938f4524676e2...
You would (probably) only do this defensively against an aggression by Facebook. People don't generally have an interest in alleging patents are invalid, unless they are being sued for infringement of those patents.
Also check out Ask Patents, which works on invalidating patent applications: http://www.joelonsoftware.com/items/2013/07/22.html.
https://www.apache.org/licenses/LICENSE-2.0.txt
IANAL but Section 3. definitely seems to cover exactly the same thing, with quite clear, and moreover long established language:
> 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
I was perplexed by the uproar on HN about the original patent language (in the thread announcing the release of React Native [1]). This kind of open-source patent license--which, in effect, allows Facebook to use its patents against users of React defensively but not offensively--is exactly what we need more of in the open source world. Why did people think that their defensive patent license was somehow worse than the industry standard (the MIT or BSD copyright license with no patent license, which made patent rights murky at best)?
But this new language eliminates the major limitation on the original language, which was that the license would be terminated if you attempted to invalidate one of Facebook's patents or defensively argued that it was invalid or unenforceable (or even, according to a strict though implausible reading of the language, if you publicly stated that the patent was invalid).
Glad to see Facebook paying attention, even if the original complaint was overblown.
[1] https://news.ycombinator.com/item?id=9271246