nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: "External" extensions
Date Sun, 01 Nov 2015 20:04:31 GMT
How about maintaining a registry like npm or
where individuals host their modules on github and users can discover them via registry? 

Sent from my iPad

> On Nov 1, 2015, at 10:35 AM, Joe Witt <> wrote:
> " but raises several questions, all pertaining to the relationship of
> this project with ASF, its ownership and control."
> ...that is what I'm struggling to respond to as well.
> It feels like the right path within the ASF is to establish child
> projects of Apache NiFi.  I think we knew we needed to do this anyway
> as we've mentioned before.  It just might be time now...
> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
> <> wrote:
>> Tony, plenty of opinion but so are the questions/concerns.
>> Managing it on GitHub is perfect, but raises several questions, all pertaining to
the relationship of this project with ASF, its ownership and control.
>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>> Cheers
>> Oleg
>> Sent from my iPhone
>>> On Nov 1, 2015, at 13:08, Adam Estrada <> wrote:
>>> This has been suggested before. It's a great idea!!! I suggest creating a repo
on github for NiFi-Processors or something like that. There are many more folks searching
through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>> A
>>> Sent from my iPhone
>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <> wrote:
>>>> Not very strong opinions on this?
>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <> wrote:
>>>>> Tony,
>>>>> I completely agree we should do this.  A quick github search reveals
>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>> for which they're not necessarily going to submit them as PRs.  We
>>>>> should link to these as much as possible but we should also help folks
>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>> community directly but they are good for users and developers to know
>>>>> about.
>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>> above sort of disclaimer and a healthy recognition such references
>>>>> will become stale...
>>>>> Thanks
>>>>> Joe
>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <>
>>>>>> All,
>>>>>> I wanted to start a conversation about projects that are good for
>>>>>> using or developing NiFi, but either can't or don't belong in the
>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>> (or
>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>> License),
>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>> NIFI-1074
>>>>>> [2].
>>>>>> I'd like to propose either capturing these on the website or on the
>>>>> or
>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>> archetype for this type of documentation in another apache project,
>>>>>> didn't find anything I personally liked. If you have seen something
>>>>>> like or don't, I'd be interested to hear.
>>>>>> [1]
>>>>>> [2]

View raw message