incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: [DISCUSS] Release of Apache Allura (incubating) v1.0.0
Date Wed, 25 Sep 2013 22:53:29 GMT
On Wed, Sep 25, 2013 at 9:02 AM, Cory Johns <> wrote:
> Marvin,
> We've been having some discussion and I'd just like to clarify something
> you said:
>> Any artifact that is being distributed through Apache channels is
>> supposed to adhere to our policies.
> Does this mean that as long as we are releasing the sub-packages on PyPI
> only, and not through Apache channels, that we can leave out the LICENSE
> and NOTICE files (with license headers remaining in the individual files
> and the top-level LICENSE and NOTICE file remaining in the ASF release, of
> course)?

Thanks for the thoughtful inquiry, Cory.

Downstream products are the work of the individuals who prepare them.  Apache
PMCs can't exert oversight over downstream products, we can't VOTE on them or
veto them or provide consistent quality control.

That said, I don't believe you have the option of omitting the NOTICE file
from the PyPI release, or at least the relevant portion of the NOTICE file --
the ALv2 requires propagation of any relevant notices therein to derivative
works.  See section 4d:

It's a little odd to have discussions on an ASF project dev list
about downstream products which deliberately diverge from ASF policy, but so
long as what's being contemplated is legally sound, it's a gray area.  To
avoid a "too many cooks" situation, I'm inclined to defer to Allura's Mentors,
who presumably have a more complete context about the motivations, costs and
benefits of various alternatives.


Marvin Humphrey

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

View raw message