incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: Advice on binary NOTICE
Date Sat, 19 Mar 2016 15:26:11 GMT
On Fri, Mar 18, 2016 at 7:57 AM, Stephen Mallette <> wrote:
> The Jackson JSON processing lib which is Apache 2.0 licensed carries this
> NOTICE file:

---->8 snip 8<----

> Does anyone have any advice on what portion of this is relevant for
> inclusion in a binary NOTICE file? Should it all be included perhaps?

Ultimately, this is up to the judgment of the supplier of the
convenience binary, and IANAL.  That said...

It seems to me that a good, simple rule can be applied to any
ALv2-licensed dependency which originates from outside the ASF and
provides a NOTICE file -- regardless of length: Propagate the entire
content of the dependency NOTICE file into the top-level NOTICE file.

I think this more conservative approach is justified because it is
hard to know whether the dependency's copyright holders would agree
with downstream analysis as to which parts of the NOTICE may be
omitted and which may not.

> Perhaps more generally, given
> where it says,
> "If the dependency supplies a NOTICE file, its contents must be analyzed
> and the relevant portions bubbled up into the top-level NOTICE file."
> is there any more detailed information on how "relevant portions" get
> determined?

Well, the definitive resources for determining licensing obligations
are the literal license texts. That's more detail than you're asking
for, of course.

For binaries, we don't provide significant guidance at this time. It's
challenging to get our official source releases compliant with our own
policies consistently, let alone convenience binaries. There's a lot
of work to be done.

Marvin Humphrey

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message