Also, just wanted to clarify that the docs at nifi.apache.org that show all of the processors are auto-generated from the NiFi code, so that is only for processors that are part of the NiFi codebase.
If you want to maintain your code separately then Joey's page or Aldrin's page would be the way to advertise it. On Wed, Dec 7, 2016 at 10:36 AM, Joey Frazee <[email protected]> wrote: > Brian, I went ahead and added it to https://github.com/jfrazee/ > awesome-nifi, which, while not an official Apache project page of any > sort, I maintain to keep track of community work like this. > > -joey > > > On Nov 28, 2016, at 11:37 AM, Brian Flannery <[email protected]> wrote: > > > > Hi all -- great job on NiFi. The number of Processors etc speaks for > itself > > and the docs are pretty detailed. > > > > I am the Community and Ecosystem lead for NATS.io -- you may already be > > aware of it; a very lightweight, simple alternative to messaging systems > > like RabbitMQ, JMS etc. > > > > There is a community developed NATS/NiFi library - > > https://github.com/mring33621/nats-messaging-for-nifi > > > > Can you list this on your documentation page where you list the various > > processors? https://nifi.apache.org/docs.html > > > > If I need to do anything like a PR just let me know, but figured I could > > just send you the GH link? > > > > All the best, > > > > B > > > > *Brian Flannery* | Community and Ecosystem, NATS > > [email protected] | 805.570.8410 > > > > [image: www.nats.io] <http://www.nats.io> > > > > *Cloud Native Infrastructure from Apcera: NATS.io *www.nats.io >
