I don't quite understand the question. But if you have questions about
hortonworks commercial offerings, this is not the right mailing list for
questions.
On Jun 21, 2016 7:26 PM, "Pat Trainor" <pat.trai...@gmail.com> wrote:

> Tony,
>
> So this is what Hortonworks has done? Made their own version of nifi,
> right?
> On Jun 20, 2016 3:35 PM, "Tony Kurc" <trk...@gmail.com> wrote:
>
>> I think that your "no" is a no to the subject line and not the question
>> in the body. The source code for Apache NiFi has been available since the
>> start of incubation with Apache. Others may have forks of the code (the
>> Apache license v2 allows this), but the canonical repository for Apache
>> NiFi is hosted on Apache's git service (
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git)
>> On Jun 20, 2016 12:04 PM, "Joe Witt" <joe.w...@gmail.com> wrote:
>>
>>> Pat,
>>>
>>> I'll respond wearing my Apache member and Apache NiFi PMC hats.
>>>
>>>    No.
>>>
>>> NiFi is of the Apache Software Foundation and thus cannot be bought.
>>> That said to the spirit of your question it is fair to ask whether
>>> this community is diverse in its representation of members and who
>>> they are employed by.  In the committer and PMC of NiFi today we have
>>> Hortonworks, Cloudera, Twitter, and a number of other companies
>>> represented.  I think we do quite well in this regard though we must
>>> continue to work on ensuring this stays true.
>>>
>>> If you start seeing our UI turning all green then maybe it is time to
>>> start worrying :-)
>>>
>>> If there are any specific things you're seeing happening that you find
>>> concerning please do let us know.
>>>
>>> Thanks
>>> Joe
>>>
>>> On Mon, Jun 20, 2016 at 11:53 AM, Pat Trainor <pat.trai...@gmail.com>
>>> wrote:
>>> > When Hortonworks bought Nifi, did an open source fork get created that
>>> will
>>> > remain?
>>> >
>>> > Thanks!
>>> >
>>> > pat
>>> > ( ͡° ͜ʖ ͡°)
>>> >
>>> > "A wise man can learn more from a foolish question than a fool can
>>> learn
>>> > from a wise answer". ~ Bruce Lee.
>>>
>>

Reply via email to