search

facebook / wangle

Wangle is a framework providing a set of common client/server abstractions for building services in a consistent, modular, and composable way.
Apache License 2.0
3.05k stars 539 forks source link

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

Closed enis closed 7 years ago

enis commented 7 years ago

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 (https://github.com/facebook/rocksdb/pull/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: https://github.com/facebook/rocksdb/pull/2589 https://github.com/facebook/react/issues/10191

Thank you kindly for your consideration.

yfeldblum commented 7 years ago

Thanks for opening the issue. In 5f686dee5753890f37326fcf38c396b7ba8981ee, 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 commented 7 years ago

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

lukewlms commented 7 years ago

@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?