-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Licensing change #304
Comments
@empyrical could you please clarify what are the benefits to have it under MIT instead of BSD+PATENTS license? Thanks! |
Or are there currently some incompatibility issues between licenses? |
It is not incompatible, but enough people took issue with some aspects of the PATENTS license that it hindered adoption of React/GraphQL/etc. and eventually motivated FB to change licenses: https://www.apache.org/legal/resolved.html#category-x Other popular posts on the matter: https://medium.com/@raulk/if-youre-a-startup-you-should-not-use-react-reflecting-on-the-bsd-patents-license-b049d4a67dd2 I personally was not all that bothered by the PATENTS license, but it might be an issue for other people using this project. |
A little while back, React Native was switched from its BSD+PATENTS license to the MIT license
https://twitter.com/reactjs/status/964689022747475968?lang=en
facebook/react-native@26684cf
Right now, a lot of the Qt/Qml-related code in this repo is still under the BSD+PATENTS license (presumably due to the original ReactUbuntu stuff being under that license) - are there any plans to relicense it to MIT?
For the files that were based off of Canonical's ReactUbuntu code, you'll need to reach out to them and see if they're open to relicensing to MIT. Seeing that their repo seems to not have had any updates in a while, they may be open to "passing the torch" to this project.
The text was updated successfully, but these errors were encountered: