www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joan Touzet <woh...@apache.org>
Subject Re: Facebook BSD+patents license and Apache products
Date Tue, 18 Jul 2017 00:08:49 GMT
Yes, one of our PMC knows the author very well (and announced it at his
JS conference). Issues we're aware of:

  * It is at present a one-person project
  * The scuttlebutt is that it is buggy and incomplete

But if React refuses to re-license, that's where we're likely to go.

Another option is Inferno:



----- Original Message -----
From: "Greg Stein" <gstein@gmail.com>
To: legal-discuss@apache.org, private@couchdb.apache.org
Sent: Monday, 17 July, 2017 7:29:26 PM
Subject: Re: Facebook BSD+patents license and Apache products

Looks like Preact is close to React and even has an extra/optional
compatibility layer to be a drop-in replacement. And it is MIT-licensed.


On Sat, Jul 15, 2017 at 4:20 PM, Joan Touzet <joant@lrtw.org> wrote:

> Hi Chris,
> We have been discussing this in the Apache CouchDB PMC, and wanted to
> ensure that other projects note that the extremely popular React.JS
> library[1] falls under the same "Facebook BSD+Patents" license. You may
> want to inform other PMCs (especially those building web interfaces) of
> this conflict, and extend your search through the ASF repositories for
> evidence of use of this library. (Searching for 'import React' in *.js
> might be sufficient.)
> For what it's worth, CouchDB has not fully resolved our direction here,
> but we are likely to complete our 2.1 release prior to 31 Aug 2017
> (containing React.JS, as our 2.0 release did) and then expurgate React
> prior to a subsequent 2.2/3.0 release.
> Thanks for the heads up.
> -Joan Touzet
> on behalf of the CouchDB PMC
> [1]: https://facebook.github.io/react/
> ----- Original Message -----
> From: "Chris Mattmann" <mattmann@apache.org>
> To: legal-discuss@apache.org
> Sent: Saturday, 15 July, 2017 12:56:30 PM
> Subject: Facebook BSD+patents license and Apache products
> 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
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org

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

View raw message