community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William A Rowe Jr <wr...@rowe-clan.net>
Subject Re: What is the legal basis for enforcing release policies at ASF?
Date Sat, 08 Aug 2015 04:37:57 GMT
On Aug 7, 2015 3:20 PM, "Benson Margulies" <bimargulies@gmail.com> wrote:
>
> On Fri, Aug 7, 2015 at 12:08 PM, Gregory Chase <gchase@pivotal.io> wrote:
> > Does "...based on Apache Hadoop" require a clear dependency notation as
to
> > which versions of Apache component releases are part of the commercial
> > distribution?
>
> No, it cannot. Trademark law is not a matter of such distinctions, and
> our very own Apache License imposes no such complexity.

Correct, and I don't expect we would ever enforce such a covenant on the
use of an ASF mark.

However, in the context of offering ASF software in the commercial or
noncommercial spaces, providing that information in some manner is just
good form and helpful to all end users.

Please never claim it is based on an unreleased version number.  Many
projects refer to foo 1.5.2-dev until 1.5.2 is released.  But if it is
based on 1.5.2-dev, this probably corresponds to 1.5.1+ patches, not the
actual 1.5.2 that will ship in the future.

Note that in the case of these projects here, it is important to note that
the code base is incubating (phrased as Apache Incubator Project Foo or
Apache Foo, incubating).  This isn't a concern for bundling TLP project
sources.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message