I'd be +1 and thanks for explaining.
Just using a descriptive name and keeping the concept open for various
design systems to be leveraged is a good approach and doesn't require
us to change anything later. Doing this now before a first release is
a big win as well. Also didn't realize these desi
Makes complete sense to me +1
On Thu, May 17, 2018 at 10:00 AM, Matt Burgess wrote:
> Makes sense to me, I'm a +1 as well.
>
> On Wed, May 16, 2018 at 4:52 PM, Scott Aslan
> wrote:
> > Good timing as we're close to ready for a first nifi-fds release.
> >
> > I would definitely favor us keeping
Makes sense to me, I'm a +1 as well.
On Wed, May 16, 2018 at 4:52 PM, Scott Aslan wrote:
> Good timing as we're close to ready for a first nifi-fds release.
>
> I would definitely favor us keeping the 'nifi-fds' naming as that means I
> dont have to change a bunch of code so Apache NiFi Flow Desi
