Thank you, I beleve Mahout is safe:
``` andy@micheal:~/sandbox/mahout_cuda$ mvn dependency:list | grep org.rocksdb ``` yields no results; transitive dependenies are listed by default --andy ________________________________ From: John D. Ament <johndam...@apache.org> Sent: Saturday, July 15, 2017 5:45 PM To: legal-disc...@apache.org; dev@flink.apache.org; ap....@outlook.com; priv...@mahout.apache.org Subject: Re: Facebook BSD+patents license and Apache products The assertion that Flink is using RocksDB seems to be a bit over stated. https://github.com/apache/flink/search?utf8=%E2%9C%93&q=rocksdb&type= is how Flink uses RocksDB. It appears that its an optional dependency already, and not core to Flink. What this means is that you shouldn't use the Flink RocksDB backend, and Flink will need to remove that contrib module from the ASF based sources. I'll also point out that cross this between public and private lists is confusing, and not very ASF friendly. John On Sat, Jul 15, 2017 at 5:39 PM Andrew Palumbo <ap....@outlook.com> wrote: > + dev@flink (if they allow this through moderation.. I'm not subscribed > to their list anymore; If not I believe that there are enough Flink PMCs on > private@mahout to answer > > > We've stopped shipping the flink binaries as of Mahout 0.13.0: > > > https://mvnrepository.com/artifact/org.apache.mahout/mahout-flink_2.10 > > > Due to some versioning issues IIRC. Source is all still available for > build with or without ViennaCL. > > > Is there anything that needs tom be done from our end? > > > --andy > > > ------------------------------ > *From:* Pat Ferrel <p...@occamsmachete.com> > *Sent:* Saturday, July 15, 2017 2:22:32 PM > *To:* priv...@mahout.apache.org > *Cc:* legal-disc...@apache.org > > *Subject:* Re: Facebook BSD+patents license and Apache products > > Does this mean we have to remove Flink from release binaries By August? > > > > On Jul 15, 2017, at 9:56 AM, Chris Mattmann <mattm...@apache.org> wrote: > > Hi, > > As some of you may know, recently the Facebook BSD+patents license has been > moved to Category X (https://www.apache.org/legal/resolved#category-x). ASF Legal Previously Asked Questions<https://www.apache.org/legal/resolved#category-x> www.apache.org Purpose and Intended Audience¶ This page provides a history of the answers to questions asked on the legal-discuss@ mailing list, and the scope of those answers. > Please see LEGAL-303 [1] for a discussion of this. The license is also > referred > to as the ROCKSDB license, even though Facebook BSD+patents is its more > industry standard name. > > 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 Facebook BSD+patents 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 Facebook BSD+patents 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 Facebook BSD+patents 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 > > > >
