Mailing-List: contact dev-help@flink.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of srowen@gmail.com designates
 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHfHakFZN3gTacE6PnfP5B4cEkLRdd7fBUypM8t0axiA=Qzh1Q@mail.gmail.com>
References: <53EE4260.9030702@hortonworks.com>
 <CAEccTyz=HkvVqOzVveB7neHHBghu4EuwUYT2T5RYBMQzYVWoag@mail.gmail.com>
 <CAHfHakFZN3gTacE6PnfP5B4cEkLRdd7fBUypM8t0axiA=Qzh1Q@mail.gmail.com>
From: Sean Owen <srowen@gmail.com>
Date: Fri, 15 Aug 2014 19:26:46 +0100
Message-ID: 
 <CAEccTyxtG1s4QFEkKdJJZ_GEKNFVMCpDEnnd8wFODPVsuxt60Q@mail.gmail.com>
Subject: Re: Question on providing CDH packages
To: dev@flink.incubator.apache.org
Content-Type: text/plain; charset=UTF-8

PS, sorry for being dense, but I don't see vendor packages at
http://flink.incubator.apache.org/downloads.html ?

Is it this page?
http://flink.incubator.apache.org/docs/0.6-SNAPSHOT/building.html

That's more benign, just helping people rebuild for certain distros if
desired. Can the example be generified to refer to a fictional "ACME
Distribution"? But a note here and there about gotchas building for
certain versions and combos seems reasonable.

I also find this bit in the build script, although vendor-specific, is
a small nice convenience for users:
https://github.com/apache/incubator-flink/blob/master/pom.xml#L195

On Fri, Aug 15, 2014 at 7:01 PM, Owen O'Malley <omalley@apache.org> wrote:
> As a mentor, I agree that vendor specific packages aren't appropriate for
> the Apache site. (Disclosure: I work at Hortonworks.) Working with the
> vendors to make packages available is great, but they shouldn't be hosted
> at Apache.
>
> .. Owen
>
>
> On Fri, Aug 15, 2014 at 10:32 AM, Sean Owen <srowen@gmail.com> wrote:
>
>> I hope not surprisingly, I agree. (Backstory: I am at Cloudera.) I
>> have for example lobbied Spark to remove CDH-specific releases and
>> build profiles. Not just for this reason, but because it is often
>> unnecessary to have vendor-specific builds, and also just increases
>> maintenance overhead for the project.
>>
>> Matei et al say they want to make it as easy as possible to consume
>> Spark, and so provide vendor-build-specific artifacts and such here
>> and there. To be fair, Spark tries to support a large range of Hadoop
>> and YARN versions, and getting the right combination of profiles and
>> versions right to recreate a vendor release was kind of hard until
>> about Hadoop 2.2 (stable YARN really).
>>
>> I haven't heard of any formal policy. I would ask whether there are
>> similar reasons to produce pre-packaged releases like so?
>>
>>
>> On Fri, Aug 15, 2014 at 6:24 PM, Alan Gates <gates@hortonworks.com> wrote:
>> > Let me begin by noting that I obviously have a conflict of interest
>> since my
>> > company is a direct competitor to Cloudera.  But as a mentor and Apache
>> > member I believe I need to bring this up.
>> >
>> > What is the Apache policy towards having a vendor specific package on a
>> > download site?  It is strange to me to come to Flink's website and see
>> > packages for Flink with CDH (or HDP or MapR or whatever).  We should
>> avoid
>> > providing vendor specific packages.  It gives the appearance of
>> preferring
>> > one vendor over another, which Apache does not want to do.
>> >
>> > I have no problem at all with Cloudera hosting a CDH specific package of
>> > Flink, nor with Flink project members working with Cloudera to create
>> such a
>> > package.  But I do not think they should be hosted at Apache.
>> >
>> > Alan.
>> > --
>> > Sent with Postbox <http://www.getpostbox.com>
>> >
>> > --
>> > CONFIDENTIALITY NOTICE
>> > NOTICE: This message is intended for the use of the individual or entity
>> to
>> > which it is addressed and may contain information that is confidential,
>> > privileged and exempt from disclosure under applicable law. If the
>> reader of
>> > this message is not the intended recipient, you are hereby notified that
>> any
>> > printing, copying, dissemination, distribution, disclosure or forwarding
>> of
>> > this communication is strictly prohibited. If you have received this
>> > communication in error, please contact the sender immediately and delete
>> it
>> > from your system. Thank You.
>>