Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Sat, 15 Jul 2017 16:58:00 +0000 (UTC)
From: "Chris A. Mattmann (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.13065712.1492732119000.255582.1500137880233@Atlassian.JIRA>
In-Reply-To: <JIRA.13065712.1492732119000@Atlassian.JIRA>
References: <JIRA.13065712.1492732119000@Atlassian.JIRA> <JIRA.13065712.1492732119653@jira-lw-us.apache.org>
Subject: [jira] [Commented] (LEGAL-303) RocksDB Integrations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 15 Jul 2017 16:58:08 -0000


    [ https://issues.apache.org/jira/browse/LEGAL-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088663#comment-16088663 ] 

Chris A. Mattmann commented on LEGAL-303:
-----------------------------------------

I sent a notice today to all Apache PMCs with the following contents:

{noformat}
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).
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
{noformat}


> RocksDB Integrations
> --------------------
>
>                 Key: LEGAL-303
>                 URL: https://issues.apache.org/jira/browse/LEGAL-303
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Jeff Jirsa
>            Assignee: Chris A. Mattmann
>
> Hi Legal,
> There's a hypothetical question on the Apache Cassandra mailing list about potentially expanding Cassandra's storage to be pluggable, specifically using RocksDB.
> RocksDB has a 3 clause BSD license (
> https://github.com/facebook/rocksdb/blob/master/LICENSE ), and a patent
> grant ( https://github.com/facebook/rocksdb/blob/master/PATENTS )
> I know the 3 clause BSD license is fine, but is the wording of the patent grant problematic? 
> cc [~dikanggu]


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org