Skip to content
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

Consider re-licensing to AL v2.0, as RocksDB has just done #105

Closed
enis opened this issue Jul 17, 2017 · 3 comments
Closed

Consider re-licensing to AL v2.0, as RocksDB has just done #105

enis opened this issue Jul 17, 2017 · 3 comments

Comments

@enis
Copy link

enis commented Jul 17, 2017

Hi,

The Apache Software Foundation Legal Affairs Committee has announced 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 (facebook/rocksdb#2589).

Apache HBase C++ client (HBASE-14850) depends on folly and wangle for implementing async socket IO and async RPC framework. We would kindly ask Wangle to change the license to be an ASF-compatible license, otherwise, as many ASF projects, we have no option but to stop using Wangle.

Please note that folly itself is using Apache License 2.0, and RocksDB have decided to switch their licenses to be the same, and React is deciding on the option:
facebook/rocksdb#2589
facebook/react#10191

Thank you kindly for your consideration.

@yfeldblum
Copy link
Contributor

Thanks for opening the issue. In 5f686de, which is in the history of master, the Wangle license is changed to Apache License 2.0. This license change will be included in the next weekly release tag.

@enis
Copy link
Author

enis commented Aug 30, 2017

Thanks @yfeldblum and others. This is really great that, and unblocks us in the HBase community.

@lukewlms
Copy link

lukewlms commented Aug 30, 2017

@yfeldblum This is great. Can you provide any guidance on why Wangle was able to go a different direction from most of the Facebook open source ecosystem on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants