Re: "External" extensions

In nodejs/npm world, each module has package.json, which declaratively indicate which node version and other external modules it depends on. Similarly I am thinking Nar modules can declare which version of JVM and NiFi it depends on and also which other modules it depends on. NPM ( NiFi

Re: "External" extensions

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

Re: "External" extensions

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

Re: "External" extensions

Well the question still remains unanswered, what relationship those projects have to ASF distribution of NiFi? I seriously doubt that anyone on this list suggests that all have to be part of the release. And if they are not then they are just individual projects managed in/out of ASF, right?

Re: "External" extensions

ASF policy; a PMC should not be in the business of creating and maintaining code 'somewhere else' and/or under another license, for fear of confusion. Gray area -- some PMC members can be in that business, as long as the boundary is clear. There was a thing called 'apache extras' for this.

"External" extensions

All, I wanted to start a conversation about projects that are good for people using or developing NiFi, but either can't or don't belong in the source 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