(Today weâ€™re interviewing Shane Curcuru about the recent issues reported with Facebookâ€™s React.js softwareâ€™s BSD + PATENTS file license, and what the Apache Software Foundation (ASF) has to do with it all. Shane serves in a leadership position at the ASF, but he wants you to know heâ€™s speaking only as an individual here; this does not represent an official position of the ASF.)
UPDATE: Facebook has relicensed React.js as well as some other software under the MIT license, without the FB+PATENTS file. Thatâ€™s good news, in general!
Hello and welcome to our interview about the recent licensing kerfuffle around Facebookâ€™s React.js software, and the custom license including a custom PATENTS file that Facebook uses for the software.
Continue reading FAQ for Facebook React.js BSD + PATENTS License issue with the Apache Software Foundation
There are really three aspects to your projectâ€™s decision (to use React.js or not based on the BSD+Patents license), and itâ€™s important to consider each of them. You really need to consider which aspects are important to your projectâ€™s success â€” and which ones donâ€™t really matter to you.
(See the updatedÂ FAQ about the PATENTS issueÂ on Medium!)
- Legal â€” both details of the license and PATENTS file that Facebook offers React.js under, and some realistic situations where the patent clauses might actually come into play (which is certainly rare in court, but itâ€™s the chilling effect of uncertainty thatâ€™s the issue)
- Technology â€” are other libraries sufficiently functional to provide the features your project needs? Does a project have the capacity to make a change, if they decided to?
- Community â€” how does the rest of the open source community-of-communities see the issue, and care about your choices? This includes both future buyers of a startup, as well as future partners, as well as future talent (employees) or contributors (open source developers).
Continue reading Three React-ions to the Facebook PATENTS License