Consider re-licensing to AL v2.0, as RocksDB has just done
Problem
Hi there, The Apache Software Foundation Legal Affairs Committee [has announced][1] that the so-called 'Facebook BSD+Patents License' is no longer allowed to be used as a direct dependency in Apache projects. This has lead to a lot of upset and frustration in the Apache community, especially from projects requiring similarly-licensed code as direct dependencies - the chief of these being RocksDB. However, we (the Apache Software Foundation) have just received word that [RocksDB will be re-licensing their code under the dual Apache License v2.0 and GPL 2 licenses][2]. As a user of React.JS in an ASF top-level project (Apache CouchDB), please consider re-licensing React.JS under similar terms. Otherwise, many ASF projects such as our own will have to stop relying on and building with React. A previous bug (#9760) suggested I mention @lacker in this issue when asking licensing questions, so I'm doing so. Thank you kindly for your consideration. [1]: https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663 [2]: https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088730&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088730
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Re-license React.JS to Apache License v2.0 and GPL 2.0
The Apache Software Foundation's Legal Affairs Committee has prohibited the use of the 'Facebook BSD+Patents License' for direct dependencies in Apache projects. This change affects projects like Apache CouchDB that rely on React.JS, which is currently under this license. To maintain compatibility and support for these projects, React.JS needs to be re-licensed under terms similar to RocksDB, specifically the dual Apache License v2.0 and GPL 2.0.
Awaiting Verification
Be the first to verify this fix
- 1
Review Current License
Examine the current licensing terms of React.JS to understand the implications of changing the license. This will involve reviewing the existing documentation and legal agreements.
- 2
Draft New License Terms
Prepare a draft of the new licensing terms that will replace the current license. This should include the dual licensing under Apache License v2.0 and GPL 2.0. Consult with legal experts if necessary to ensure compliance.
- 3
Community Consultation
Engage with the React.JS community to discuss the proposed licensing changes. Gather feedback and address any concerns raised by contributors and users.
- 4
Finalize and Implement License Change
Once the community feedback is incorporated, finalize the new license terms and update the project repository. Ensure that all documentation reflects the new licensing.
- 5
Notify Users and Contributors
Communicate the changes to all users and contributors of React.JS. Provide clear instructions on how the new licensing will affect their use of the library.
Validation
Confirm the fix by checking the React.JS repository for the updated license file and ensuring that community projects like Apache CouchDB can successfully integrate and build with the new licensing terms.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep