www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: ROCKSDB license and Apache projects
Date Wed, 12 Jul 2017 10:17:46 GMT

In addition, I want to point out that the industry name for this license is
"Facebook BSD+Patents license" and it applies to much more than RocksDB.


On Wed, Jul 12, 2017 at 6:09 AM John D. Ament <johndament@apache.org> wrote:

> Chris,
> Did you see my note about rocksdbjni?  This is what's actually used in
> Kafka, and possibly other projects (I just checked Samza and Flink, both
> are using it).  That seems to be licensed differently.  I would recommend
> getting that squared away to avoid any incorrect statements going out to
> PMCs.
> Note that RocksDB doesn't ship any JARs, its a C++ library.  rocksdbjni
> does ship JARs, but it appears that this is an Apache Licensed product (no
> mention at all of the patent waiver).
> John
> On Tue, Jul 11, 2017 at 11:51 PM Chris Mattmann <mattmann@apache.org>
> wrote:
>> Please note that I will send the below to pmcs@ tomorrow likely by
>> mid-day Eastern Standard Time.
>> -----
>> Hi,
>> As some of you may know, recently the ROCKSDB has been
>> moved to Category X (https://www.apache.org/legal/resolved#category-x).
>> Please see LEGAL-303 [1] for a discussion of this.
>> This has impacted some projects, to date based on LEGAL-303
>> and the detective work of Todd Lipcon:
>> Samza, Flink, Marmotta, Kafka and Bahir
>> (perhaps more)
>> Please take notice of the following policy:
>> o No new project, sub-project or codebase, which has not
>>   used ROCKSDB licensed jars (or similar), are allowed to use
>>   them. In other words, if you haven't been using them, you
>>   aren't allowed to start. It is Cat-X.
>> o If you have been using it, and have done so in a *release*,
>>   you have a temporary exclusion from the Cat-X classification thru
>>   August 31, 2017. At that point in time, ANY and ALL usage
>>   of these ROCKSDB licensed artifacts are DISALLOWED. You must
>>   either find a suitably licensed replacement, or do without.
>>   There will be NO exceptions.
>> o Any situation not covered by the above is an implicit
>>   DISALLOWAL of usage.
>> Also please note that in the 2nd situation (where a temporary
>> exclusion has been granted), you MUST ensure that NOTICE explicitly
>> notifies the end-user that a ROCKSDB licensed artifact exists. They
>> may not be aware of it up to now, and that MUST be addressed.
>> If there are any questions, please ask on the legal-discuss@a.o
>> list.
>> Thanks.
>> Cheers,
>> Chris Mattmann
>> VP Legal Affairs
>> [1] https://issues.apache.org/jira/browse/LEGAL-303
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org

View raw message