> On Mon, Apr 30, 2012 at 9:39 PM, Roman Shaposhnik <rvs@...> wrote:
>> On Mon, Apr 30, 2012 at 9:13 PM, Eric Baldeschwieler
>> <eric14@...> wrote:
>>> So you are suggesting expanding the charter to include projects not hosted at Apache?
>> I don't think this is what Bruno suggested. Personally I can't find
>> any reference in Bigtop
>> charter that restricts it to Projects that belong to Apache Software
> As a mentor of the Bigtop project, I don't see it as acceptable for an
> Apache project to distribute binaries of non-Apache software. If the
> owners of the Hue project decide to donate it to Apache and it had
> been released by Apache, then it would be acceptable. I'm strictly -1
> on releasing any version of Bigtop with Hue or any other non-Apache
> software as part of the release.
> -- Owen
As part of mentoring Apache Bigtop (incubating) project, it would also
be greatly appreciated if you would explain why this -1.
Apache Bigtop (incubating) does not and will not include anything that
does not belong to the Apache Foundation.
So I am really confused as to why this strong reaction.
The convenience artefact may pull Hue in, but this is in no way
different from Apache Hadoop pulling in Google protocol buffer or Google
guava. So again, how is this different? Is Apache Hadoop going to
avandon Google Protocolbuffer?
Furthermore as I just stated above, Apache Bigtop (incubating) does not
and will not include any source of Hue.
I am also confused on your definition of release since from my
understanding, only source releases are voted on. And they won't contain
Hue or any code that does not belong to the Apache Foundation. We don't
check in any of our dependency, so I am confused about your statements.
All of this is really no different from Apache Hadoop which pulls some
non-Apache Foundation dependencies such as Google Protocolbuffer.