incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Bloated NOTICE files are evil
Date Sun, 12 Oct 2014 12:16:36 GMT
On 11 October 2014 19:30, Roman Shaposhnik <rvs@apache.org> wrote:
> On Sat, Oct 11, 2014 at 11:08 AM, Sean Owen <srowen@gmail.com> wrote:
>> On Sat, Oct 11, 2014 at 7:02 PM, Ted Dunning <ted.dunning@gmail.com> wrote:
>>> Netty's artifacts ("its distribution") do not include a notice.  Thus,
>>
>> They most certainly do. Please download the distribution of Netty 4.0.20:
>>
>> https://github.com/netty/netty/releases/tag/netty-4.0.20.Final
>
> This is source code distribution. Assuming that distribution == source
> code distribution is a very ASF-centered view point. Nothing wrong
> with this, but form my interpretation of legal view on this, unless your
> license clearly spells out what "distribution" you can't assume whether
> that is source, binary or both.
>
> Now, ALv2, of course, clearly defines that it is both. And there's the
> rub: it does not, as far as I can tell, infer cross-contamination of these
> types of distributions. IOW the following is true, as far as I can tell:
>    1. if source distribution of ALv2 software has NOTICEs then and only
>        then a derviate work distributed in *SOURCE* form must continue
>        shipping them.

I don't think that's correct.

A source distribution with NOTICE may be included in an ASF binary
distribution - e.g. example code is often included in biary dists.
In this case the relevant parts of the source NOTICE would need to be
considered for inclusion in the ASF NOTICE for the binary.

In other words a source distribution affects all works that include
it, not just source distributiions.

The NOTICE file in an ASF source release must contain all *required*
attributions for all included bits, and must not contain attributions
for bits that are not included. Only INCLUDED bits affect the NOTICE
(and LICENSE) files.

The process for determining what goes in the ASF NOTICE file starts
with the contents of the associated release artifact.
For each item in the release artifact, you need to determine what
attributions (if any) need to be added to the NOTICE file.

>    2. if binary distribution of ALv2 software has NOTICEs then and only
>        then a derviate work distributed in *BINARY* form must continue
>        shipping them.

Ditto; binary dists (e.g. images) may be included in ASF source.

>    3. presence or absence of NOTICEs in binary distribution doesn't
>        affect source distribution.

Not true.

>    4. presence or absence of NOTICEs in source distribution doesn't
>        affect binary distribution.

Not true.

==

The principle is that the NOTICE and LICENSE files in an ASF release
tarball (whether that is binary or source) must only relate to the
bits which are actually included in the artifact.

> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message