Re: [ANNOUNCE] New Apache NiFi Committer Rob Fellows

[Rob Moran]

Thanks for all your work, Rob -- congrats!

On Wed, Sep 25, 2019 at 9:29 AM Andrew Lim 
wrote:

> Congrats Rob!
>
>
> > On Sep 24, 2019, at 7:56 PM, Tony Kurc  wrote:
> >
> > Apache NiFi community,
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that Rob
> > has accepted the PMC's invitation to become a committer on the Apache
> NiFi
> > project. We greatly appreciate all of Rob's hard work and generous
> > contributions to the project. We look forward to his continued
> involvement
> > in the project.
> >
> > What stood out with Rob are his regular code contributions and reviews on
> > many parts of the project to include NiFi, NiFi FDS, and NiFi Registry
> > since early this year. Additionally, he's been doing the
> > not-always-glamorous work of helping verify releases, which was a huge
> > assist in getting NiFi 1.9.1, NiFi Registry 0.4.0 and 0.5.0, and NiFi FDS
> > 0.2.0 out to the community.
> >
> > Welcome and congratulations!
> > Tony
>
>

Re: UI Features

[Rob Moran]

Thanks for sharing your thoughts, Raymond.

Some of the items you call out have tickets already or there may be
similar/related ones. I will plan to go through each and reply back with my
findings.

Thanks again!

On Fri, Jul 26, 2019 at 9:46 AM ski n  wrote:

> I was creating a flow and I noticed some things of the GUI that were
> missing. Don’t know if there already plans/tickets for these items, but I
> would like your opinion first.
>
> If you think it’s a good idea and there is no ticket yet than I will create
> one:
>
> 1) It’s already possible to align flows, but sometimes it takes a lot
> of time to make a flow look clean. I like if an automatically ordering
> option of a flow (which calculate the best view). Ordering a flow from left
> to right or ordering a flow from top to bottom.
>
> 2) Double-click on the canvas to zoom in.
>
> 3) Add possibility to use keyboard to move elements (for example
> processors)
>
> 4) Select multiple items with mouse (like MS Visio). Now you need the
> shift key to do this.
>
> 5) Moving step/flows into a process group. “Right-Click” on a flow step
> (Move step to process group / Move flow to process group / Create process
> group for this flow)
>
> 6) Possibility to add links in labels (for example link to a process
> group)
>
> 7) Search box (to find and navigate to a process group/flow/flow step)
>
> 8) Queues are highlighted yellow, while processors are highlight black
> (Better both yellow, black is hard to see)
>
> 9) Add Ctrl X / Cut
>
> 10)  Add Ctrl Z / Revert last change
>
> 11)  Sometimes the "apply" button navigates you directly back to the canvas
> (for example with configuration), sometimes not (process group). Like to
> have a 'save' button which means apply change and leave the popup, while
> apply applies the change.
>
> 12)  Export canvas to image (jpeg/png)
>
> 13)  Links to file resources --> open the resource in an online editor
>
> 14) Option to edit the processor as XML (sometimes this goes faster). Now
> you need to export/import the processor as a template.
>
>
>
> Best regards,
>
>
> Raymond
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)

[Rob Moran]

+1 Release this package as nifi-fds-0.2.0

Thanks for putting this together, Scott!

On Fri, Jul 26, 2019 at 2:10 PM Joe Witt  wrote:

> +1 (binding)
>
> Full clean build following readme and testapp check out.  L looks good.
> Sigs/Commit checks out.
>
> I would recommend ditching the sha1 entry.  256 and 512 are good.
>
> Thanks
>
> On Fri, Jul 26, 2019 at 1:33 PM Marc Parisi  wrote:
>
> > +1 (binding). I built and tested according to the release helper guide.
> > Demo app, hashes, readmes, and notices all look good.
> >
> > Thanks Scott!
> >
> > On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman 
> > wrote:
> >
> > > +1 (binding) Release this package as nifi-fds-0.2.0
> > >
> > > Ran through release helper. Checked out demo app and all looks good.
> > >
> > > Thanks for RMing Scott!
> > >
> > > Matt
> > >
> > > On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras
> >  > > >
> > > wrote:
> > >
> > > > * Verified the signature
> > > > * Verified the hashes
> > > > * Verified README
> > > > * Verified the demo app works as expected
> > > >
> > > > Unfortunately majority of npm scripts are broken on windows, however
> I
> > > > could make them run and test the app with some minor changes. JIRA
> > issue:
> > > > https://issues.apache.org/jira/browse/NIFI-6481
> > > >
> > > > + 1 (non-binding)
> > > >
> > > > András
> > > >
> > > > On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis
> > >  > > > >
> > > > wrote:
> > > >
> > > > > * Verified the git commit
> > > > > * Verified the signature
> > > > > * Verified the hashes
> > > > > * Verified the build
> > > > > * Verified README
> > > > > * Verified the demo app works as expected
> > > > >
> > > > > + 1 (non-binding)
> > > > >
> > > > > Cheers,
> > > > > Adam
> > > > >
> > > > > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows <
> > rob.fell...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > * Verified the signature
> > > > > > * Verified the hashes
> > > > > > * Verified the build
> > > > > > * Verified README
> > > > > > * Verified the demo app works as expected
> > > > > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked
> > > with
> > > > > > documented updates.
> > > > > >
> > > > > > + 1 (non-binding)
> > > > > >
> > > > > >
> > > > > > -- Rob Fellows
> > > > > >
> > > > > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan <
> scottyas...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > >
> > > > > > > I am pleased to be calling this vote for the source release of
> > > Apache
> > > > > > >
> > > > > > > NiFi Flow Design System 0.2.0.
> > > > > > >
> > > > > > >
> > > > > > > The source zip, including signatures, etc. can be found at:
> > > > > > >
> > > > > > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
> > > > > > >
> > > > > > >
> > > > > > > The Git tag is NIFI-FDS-0.2.0-RC2
> > > > > > >
> > > > > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17
> > > > > > >
> > > > > > >
> > > > > > > Checksums of nifi-fds-0.2.0-source-release.zip:
> > > > > > >
> > > > > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d
> > > > > > >
> > > > > > > SHA256:
> > > > > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f
> > > > > > >
> > > > > > > SHA512:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1
> > > > > > >
> > > > > > >
> > > > > > > Release artifacts are signed with the following key:
> > > > > > >
> > > > > > > https://people.apache.org/keys/committer/scottyaslan.asc
> > > > > > >
> > > > > > >
> > > > > > > KEYS file available here:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > > > >
> > > > > > >
> > > > > > > 36 issues were closed/resolved for this release:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020
> > > > > > >
> > > > > > >
> > > > > > > Release note highlights can be found here:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0
> > > > > > >
> > > > > > >
> > > > > > > The vote will be open for 72 hours.
> > > > > > >
> > > > > > >
> > > > > > > Please download the release candidate and evaluate the
> necessary
> > > > items
> > > > > > >
> > > > > > > including checking hashes, signatures, build from source, and
> > test.
> > > > > > >
> > > > > > >
> > > > > > > The please vote:
> > > > > > >
> > > > > > >
> > > > > > > [ ] +1 Release this package as nifi-fds-0.2.0
> > > > > > >
> > > > > > > [ ] +0 no opinion
> > > 

Re: [ANNOUNCE] New NiFi PMC member Jeremy Dyer

[Rob Moran]

Congratulations, Jeremy!

On Tue, Jul 31, 2018 at 1:17 PM Sivaprasanna 
wrote:

> Congratulations, Jeremy. Well deserved.
>
> On Tue, 31 Jul 2018 at 9:44 PM, Scott Aslan  wrote:
>
> > Congrats Jeremy!
> >
> > On Tue, Jul 31, 2018 at 11:02 AM Michael Moser 
> wrote:
> >
> > >  Congrats, welcome, and thank you for your work.
> > >
> > >
> > > On Tue, Jul 31, 2018 at 9:21 AM Otto Fowler 
> > > wrote:
> > >
> > > > Congratulations!
> > > >
> > > >
> > > > On July 31, 2018 at 08:36:48, Tony Kurc (tk...@apache.org) wrote:
> > > >
> > > > All,
> > > >
> > > > On behalf of the Apache NiFi PMC, I am pleased to announce that
> Jeremy
> > > Dyer
> > > > has accepted the PMC's invitation to join the Apache NiFi PMC.
> > > >
> > > > Jeremy has been a long-time contributor to the project - across many
> > > > different parts of the project to include NiFi and and MiNiFi,
> > > contributing
> > > > code, reviews, release verification, and help on the mailing lists.
> > He's
> > > > performed the challenging, detail oriented work of acting as a
> release
> > > > manager for both the Java and C++ versions of MiNiFi (0.5.0 of each).
> > > >
> > > > Congratulations Jeremy and well deserved!
> > > >
> > > > Tony
> > > >
> > >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Kevin Doran

[Rob Moran]

Congratulations, Kevin!

On Tue, Jul 31, 2018 at 1:16 PM Sivaprasanna 
wrote:

> Congratulations, Kevin.
>
> On Tue, 31 Jul 2018 at 9:43 PM, Scott Aslan  wrote:
>
> > Congrats Kevin!
> >
> > On Tue, Jul 31, 2018 at 11:01 AM Michael Moser 
> wrote:
> >
> > > Congrats, welcome, and thank you for your work.
> > >
> > >
> > > On Tue, Jul 31, 2018 at 9:21 AM Otto Fowler 
> > > wrote:
> > >
> > > > Congratulations!
> > > >
> > > >
> > > > On July 31, 2018 at 08:26:34, Tony Kurc (tk...@apache.org) wrote:
> > > >
> > > > NiFi Community,
> > > >
> > > > On behalf of the Apache NiFi PMC, I am pleased to announce that Kevin
> > > Doran
> > > > has accepted the PMC's invitation to join the Apache NiFi PMC.
> > > >
> > > > In addition to being a regular code contributor to the project for
> > quite
> > > > some time, Kevin has been hard to miss on the mailing lists,
> especially
> > > on
> > > > NiFi Registry threads. We all appreciate his hard work getting
> releases
> > > > "out the door", helping verify releases and recently doing release
> > > manager
> > > > duty for the NiFi Registry 0.2.0.
> > > >
> > > > Please join us in congratulating and welcoming Kevin to the Apache
> NiFi
> > > > PMC.
> > > >
> > > > Tony
> > > >
> > >
> >
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.1.0 RC3

[Rob Moran]

+1

* Stepped through the release guide to verify the sig, hashes, and commit ID
* Checked for readme, notice, and license in source and target
* Checked for the package version update changes
* Ran the demo app – seems to be a slight delay initially loading up but
all looks good

Thanks for all your effort on this, Scott!


On Tue, Jun 12, 2018 at 2:59 AM Pierre Villard 
wrote:

> +1, binding
>
> Went through the release helper guide and all looks good to me AFAICT.
> I merged the PR from Andy and set the fix version to 0.2.0.
> (could be a good idea to ask infra for a dedicated JIRA so we don't mix
> things regarding version numbers?)
>
> Congrats on this first release and thanks to everyone involved!
>
> Pierre
>
> 2018-06-12 1:02 GMT+02:00 Andy LoPresto :
>
> > Verified the GPG signature (SHA-512 digest, excellent) and checksums.
> > Ran through the build and deployed, testing the demo app.
> > Verified the LICENSE, NOTICE, and README in the source and deployable
> > application.
> > Checked the versioning in package.json and package-lock.json (not a
> > JS/node expert, but I think it’s right).
> >
> > (One tiny typo in the README, which I fixed in a PR).
> >
> > +1, binding
> >
> > Thanks for your continued work on this release, Scott.
> >
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Jun 11, 2018, at 1:50 PM, Scott Aslan  wrote:
> >
> > Hello,
> >
> >
> > I am pleased to be calling this vote for the source release of Apache
> >
> > NiFi Flow Design System 0.1.0.
> >
> >
> > The source zip, including signatures, etc. can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/
> >
> >
> > The Git tag is nifi-fds-0.1.0-RC3
> >
> > The Git commit ID is 4f62f3d4a4626f66011289c7f1346c082a932184
> >
> > *https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=
> > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184
> >  > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184>*
> >
> >
> > Checksums of nifi-fds-0.1.0-source-release.zip:
> >
> > SHA1:
> >
> > ce971d78cc0660299dcee2233bc22fa78e2940af
> >
> > SHA256:
> >
> > 7cb36f412b4147c0e071508f4f6d2ca76b2fe524382937d6552dbe7efe10a827
> >
> > SHA512:
> >
> > 11e9cf4a529862da528bd616124e57f567503c25820e4b70e72d3d53f16b
> > fed7c0c97f05f7c390267d2163cdae2c6151dc6d9a9bdf6c11be8a6dca4409b3bd15
> >
> >
> > Release artifacts are signed with the following key:
> >
> > https://people.apache.org/keys/committer/scottyaslan.asc
> >
> >
> > KEYS file available here:
> >
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> >
> > 7 issues were closed/resolved for this release:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12316020=12343357
> >
> >
> > Release note highlights can be found here:
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+
> > Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.0
> >
> >
> > The vote will be open for 72 hours.
> >
> >
> > Please download the release candidate and evaluate the necessary items
> >
> > including checking hashes, signatures, build from source, and test.
> >
> >
> > The please vote:
> >
> >
> > [ ] +1 Release this package as nifi-fds-0.1.0
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 Do not release this package because...
> >
> >
> >
>

[RESULT] [VOTE] Change the name Apache NiFi Fluid Design System to Apache NiFi Flow Design System

[Rob Moran]

Thanks to all who participated. The results are:

+1: 12 (10 binding, 2 non-binding​)
+0:  none
-1:  none

The vote to change the name Apache NiFi Fluid Design System to Apache NiFi
Flow Design System has passed.

I will file a JIRA to update the nifi-fds README.

Thanks,
Rob

[VOTE] Change the name Apache NiFi Fluid Design System to Apache NiFi Flow Design System

[Rob Moran]

Following positive response discussing the name change of nifi-fds [1], I'd
like to call a vote to officially change the name of the Apache NiFi Fluid
Design System to the Apache NiFi Flow Design System.

The name change reflects that nifi-fds is meant to establish a set of
reusable UI components for the NiFi ecosystem, and that these components
are not tied to a single design system or UI platform.

I am a +1.

The vote will be open for 72 hours and will be a majority rule vote.

[ ] +1 Change the name to Apache NiFi Flow Design System
[ ] +0 No opinion
[ ] -1 Do not change the name because...

[1]
http://mail-archives.apache.org/mod_mbox/nifi-dev/201805.mbox/%3CCAGmW7OxAaazAYDs8_v%3DkwYPKtJp3tMDEJdyGztSFgcmdv%3DAS4w%40mail.gmail.com%3E

Re: [DISCUSS] Change Apache NiFi Fluid Design System naming

[Rob Moran]

Great – looks like a good consensus from the positive response. I'll send a
vote soon to formalize a decision.

On Thu, May 17, 2018 at 12:06 PM Joe Witt <joe.w...@gmail.com> wrote:

> 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 design systems were at
> play so that is cool and would be good to have in the readme for sure.
> Would help people that want to contribute have some frame of reference
> to start from.
>
> Thanks
> Joe
>
> On Thu, May 17, 2018 at 10:41 AM, Jeremy Dyer <jdy...@gmail.com> wrote:
> > Makes complete sense to me +1
> >
> > On Thu, May 17, 2018 at 10:00 AM, Matt Burgess <mattyb...@apache.org>
> wrote:
> >
> >> Makes sense to me, I'm a +1 as well.
> >>
> >> On Wed, May 16, 2018 at 4:52 PM, Scott Aslan <scottyas...@gmail.com>
> >> 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 Design System
> >> does
> >> > that just fine. I will take care of updating the readme and other
> areas
> >> we
> >> > need to change but we can keep the repo as-is with this.
> >> >
> >> > The descriptive name is better, generic, and consistent with some of
> the
> >> > discuss thread feedback a while back anyway.
> >> >
> >> > I'll wait to kick off the release for the outcome of this discussion
> and
> >> > vote.
> >> >
> >> > I'm +1 on this.
> >> >
> >> > Thanks
> >> >
> >> > On Wed, May 16, 2018 at 2:46 PM, Rob Moran <rmo...@gmail.com> wrote:
> >> >
> >> >> I think it's important to highlight that for nifi-fds the 'f' part of
> >> the
> >> >> name was for 'fluid.' This is part of a FLUID product design system
> [1]
> >> to
> >> >> which I also contribute, that at the time was an internal concept,
> but
> >> is
> >> >> now being described in a public manner. However, nifi-fds is
> partially
> >> >> inspired by FLUID concepts as well as others. Specifically, Material
> >> Design
> >> >> [2] and Teradata's Covalent UI Platform [3].
> >> >>
> >> >> We should change the name to reflect that what we're aiming for is a
> >> set of
> >> >> reusable UI components that the NiFi ecosystem can leverage. The UI
> >> >> components are inspired by these design systems, and will possibly be
> >> >> influenced by others as it evolves.
> >> >>
> >> >> Since we've already established the FDS naming scheme, I propose a
> >> simple
> >> >> path would be to call it the Apache NiFi *Flow* Design System rather
> >> than a
> >> >> unique/standalone term. This way the nifi-fds repo will not require a
> >> >> change. We can just update the descriptions.
> >> >>
> >> >> I assume we should vote on this if others agree?
> >> >>
> >> >> [1] http://productdesign.hortonworks.com/
> >> >> [2] https://material.io/design/
> >> >> [3] https://teradata.github.io/covalent/#/
> >> >>
> >>
>

[DISCUSS] Change Apache NiFi Fluid Design System naming

[Rob Moran]

I think it's important to highlight that for nifi-fds the 'f' part of the
name was for 'fluid.' This is part of a FLUID product design system [1] to
which I also contribute, that at the time was an internal concept, but is
now being described in a public manner. However, nifi-fds is partially
inspired by FLUID concepts as well as others. Specifically, Material Design
[2] and Teradata's Covalent UI Platform [3].

We should change the name to reflect that what we're aiming for is a set of
reusable UI components that the NiFi ecosystem can leverage. The UI
components are inspired by these design systems, and will possibly be
influenced by others as it evolves.

Since we've already established the FDS naming scheme, I propose a simple
path would be to call it the Apache NiFi *Flow* Design System rather than a
unique/standalone term. This way the nifi-fds repo will not require a
change. We can just update the descriptions.

I assume we should vote on this if others agree?

[1] http://productdesign.hortonworks.com/
[2] https://material.io/design/
[3] https://teradata.github.io/covalent/#/

Re: [VOTE] Establish Fluid Design System, a sub-project of Apache NiFi

[Rob Moran]

+1

On Sat, Mar 10, 2018, 12:59 PM James Wing  wrote:

> +1
>
> On Fri, Mar 9, 2018 at 12:10 PM, Scott Aslan 
> wrote:
>
> > All,
> >
> > Following a solid discussion for the past couple of weeks [1] regarding
> the
> > establishment of Fluid Design System as a sub-project of Apache NiFi, I'd
> > like to
> > call a formal vote to record this important community decision and
> > establish consensus.
> >
> > The scope of this project is to define a theme-able set of high quality
> UI
> > components and utilities for use across the various Apache NiFi web
> > applications in order to provide a more consistent user experience.
> >
> > I am a +1 and looking forward to the future work in this area.
> >
> > The vote will be open for 72 hours and be a majority rule vote.
> >
> > [ ] +1 Establish Fluid Design System, a subproject of Apache NiFi
> > [ ]   0 Do not care
> > [ ]  -1 Do not establish Fluid Design System, a subproject of Apache NiFi
> >
> > Thanks,
> >
> > ScottyA
> >
> > [1] *http://mail-archives.apache.org/mod_mbox/nifi-dev/201802.mbox/%
> > 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com
> %3E
> >  > 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com
> %3E
> > >*
> >
>
-- 
Rob

Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)

[Rob Moran]

+1, non-binding

* All looks good/in place following the release helper
* Reviewed help docs related to new Registry integration
* Connected a registry client and did some quick testing of basic version
control related actions


On Wed, Jan 10, 2018 at 1:24 PM Andrew Lim 
wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (10.11.6)
> -Tested integration with NiFi Registry
> -Ran record reader/writer flows
> -Reviewed resolved “Core UI” component Jiras and spot checked inclusion in
> build
> -Reviewed documentation
>
> Drew
>
>
> > On Jan 9, 2018, at 5:19 AM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.5.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1116
> >
> > The Git tag is nifi-1.5.0-RC1
> > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> >
> > Checksums of nifi-1.5.0-source-release.zip:
> > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f
> > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c
> > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c942d13
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 195 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12341668
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.5.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test.  The please vote:
> >
> > [ ] +1 Release this package as nifi-1.5.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

-- 
Rob

Re: [ANNOUNCE] New NiFi PMC member Marc Parisi

[Rob Moran]

Congratulations, Marc!

On Fri, Dec 15, 2017 at 4:31 AM Pierre Villard 
wrote:

> Congrats Marc!!
>
> 2017-12-15 6:38 GMT+01:00 Jeff :
>
> > Congrats, Marc!  Treat yourself to some Kobe beef. :)
> >
> > On Thu, Dec 14, 2017 at 9:47 PM Mike Hogue  wrote:
> >
> > > Congrats, Marc! Well deserved!
> > > On Thu, Dec 14, 2017 at 20:41 Jeremy Dyer  wrote:
> > >
> > > > Congrats Marc! Lots of good work I have seen from you and appreciate
> > all
> > > > you have given the community!
> > > >
> > > > - Jeremy Dyer
> > > >
> > > > > On Dec 14, 2017, at 8:29 PM, Scott Aslan 
> > > wrote:
> > > > >
> > > > > Congrats!
> > > > >
> > > > >> On Thu, Dec 14, 2017 at 6:50 PM, Matt Burgess <
> mattyb...@apache.org
> > >
> > > > wrote:
> > > > >>
> > > > >> Congratulations Marc with a C :) Welcome aboard, looking forward
> to
> > > > >> more kick-arse contributions!
> > > > >>
> > > > >>> On Thu, Dec 14, 2017 at 6:47 PM, Tony Kurc 
> > wrote:
> > > > >>> NiFi community,
> > > > >>> On behalf of the Apache NiFi PMC, I am pleased to announce that
> > Marc
> > > > >> Parisi
> > > > >>> has accepted the PMC's invitation to join the Apache NiFi PMC.
> We
> > > > >> greatly
> > > > >>> appreciate all of Marc's hard work and generous contributions to
> > the
> > > > >>> project. We look forward to continued involvement in the project.
> > > > >>>
> > > > >>> Marc is a major contributor to MiNiFi CPP; in addition to his
> code
> > > and
> > > > >>> review contributions, he recently release managed the 0.3.0
> > release.
> > > > He's
> > > > >>> super friendly, active across the NiFi project, and can lift a
> > small
> > > > car.
> > > > >>>
> > > > >>> Congratulations and welcome, Marc!
> > > > >>>
> > > > >>> Tony
> > > > >>
> > > >
> > >
> >
>
-- 
Rob

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Rob Moran]

Awesome – congrats Scott!!

On Mon, Dec 4, 2017 at 4:28 AM Pierre Villard 
wrote:

> Congrats Scott, well deserved!
>
> 2017-12-03 13:58 GMT+01:00 Scott Aslan :
>
> > Thank you everyone!
> >
> > It is truly an honor and I am blessed to work with such an committed,
> > energetic, and professional group. I look forward to many more great
> > achievements for this community and our project!
> >
> > -Scotty Aslan
> >
> >
> > On Sat, Dec 2, 2017 at 9:51 PM, Yolanda Davis  >
> > wrote:
> >
> > > Congrats Scott!!
> > >
> > > Sent from my iPhone
> > >
> > > > On Dec 2, 2017, at 8:43 PM, Marc  wrote:
> > > >
> > > > Congrats Scott!
> > > >
> > > >> On Dec 2, 2017 8:14 PM, "Kevin Doran" 
> > wrote:
> > > >>
> > > >> Congrats, Scott! Keep crushing it!
> > > >>
> > > >> Get Outlook for iOS
> > > >> 
> > > >> From: Joe Witt 
> > > >> Sent: Saturday, December 2, 2017 7:27:35 PM
> > > >> To: dev@nifi.apache.org
> > > >> Subject: Re: [ANNOUNCE] New NiFi PMC member Scott Aslan
> > > >>
> > > >> congrats scott and thanks for all the awesome ui and community work
> > > youve
> > > >> done!
> > > >>
> > > >>> On Dec 2, 2017 2:48 PM, "Matt Burgess" 
> wrote:
> > > >>>
> > > >>> Congratulations Scotty! Glad to have you aboard!
> > > >>>
> > > >>>
> > >  On Dec 2, 2017, at 2:46 PM, Tony Kurc  wrote:
> > > 
> > >  NiFi community,
> > >  On behalf of the Apache NiFi PMC, I am pleased to announce that
> > Scott
> > > >>> Aslan
> > >  has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> > > >>> greatly
> > >  appreciate all of Scotts's hard work and generous contributions to
> > the
> > >  project. We look forward to continued involvement in the project.
> > > 
> > >  Scott has been delivering as a strong committer for quite a long
> > time,
> > > >> is
> > >  making huge progress on nifi-registry, and has had wide reach to
> the
> > >  community in many ways, to include our mailing lists.
> > > 
> > >  Congratulations and welcome, Scott!
> > > 
> > >  Tony
> > > >>>
> > > >>
> > >
> >
>
-- 
Rob

Re: [DRAFT][REPORT] Apache NiFi Board Report Oct 2017

[Rob Moran]

Joe, looks good with the couple changes Drew mentioned--thanks.

On Mon, Oct 9, 2017 at 10:30 AM Andrew Lim 
wrote:

> Noticed the following:
>
> -In Health Report section: "seeing a very strong pipeline to both both
> committer and PMC” (remove extra both)
> -"Apache NiFi 1.4.0 was released Oct 1 2017” (Change? Release Notes says
> Oct 2)
>
> Otherwise, looks great!
>
> -Drew
>
> > On Oct 9, 2017, at 10:23 AM, Marc  wrote:
> >
> > Joe
> >
> >  I think this looks great.
> >
> >  Thanks for putting this together,
> >
> >
> >
> > On Mon, Oct 9, 2017 at 10:12 AM, Joe Witt  wrote:
> >
> >> Team,
> >>
> >> Please see draft board report.  Am looking for feedback/edits quickly
> >> as this needs to be submitted by Wed.  I'll probably send it in
> >> tonight though as I might not have time over the next couple of days.
> >>
> >> Thanks
> >> Joe
> >>
> >> **==**==**==**==**
> >>
> >> ## Description:
> >> - Apache NiFi is an easy to use, powerful, and reliable system to
> >>   process and distribute data.
> >> - Apache NiFi MiNiFi is an edge data collection agent built to
> seamlessly
> >>   integrate with and leverage the command and control of NiFi. There are
> >>   both Java and C++ implementations.
> >> - Apache NiFi Registry is a centralized registry for key configuration
> >> items
> >>   including flow versions, assets, and extensions for Apache NiFi
> >>   and Apache MiNiFi.
> >> - Apache NiFi Nar Maven Plugin is a release artifact used for supporting
> >>   the NiFi classloader isolation model.
> >>
> >> ## Issues:
> >> - There are no issues requiring board attention at this time.
> >>
> >> ## Activity:
> >> - Released Apache NiFi 1.4.0 which is another very heavy feature,
> >> stability,
> >>   and bug fix release.  It includes improvements on the web UI coming
> >> from new
> >>   contributors which is a great sign.
> >> - The Apache NiFi downloads have been quite large and growing for some
> >> time.
> >>   The groundwork to solve this is the Apache NiFi Registry effort which
> is
> >>   coming along nicely and which the foundational elements of NiFi to
> >> integrate
> >>   with it are present.  We're probably looking at two more releases for
> >> that
> >>   to land and for which we can drop the NiFi build size down.
> >> - We continue to hover around the 100 outstanding pull requests number.
> >> What
> >>   is encouraging is we've seen an uptick in contributions both in code
> and
> >>   review feedback from new community members.
> >> - The Apache NiFi MiNiFi C++ agent has rapidly matured over the past
> >> couple of
> >>   months and is serving as a new source for contributions and
> >> contributors.
> >>
> >> ## Health report:
> >> - As stated in our past report, health of the community is strong and
> >>   indicators of strength continue trending in the right direction.
> Mailing
> >>   list and JIRA activity is strong. ASF Hipchat is serving as an on-ramp
> >> for
> >>   new users to our mailing list and JIRA systems. We continue to see new
> >>   users and contributors.
> >> - The PMC and committer ranks did not grow during the reporting period.
> >> This
> >>   is a reflection of the PMC not focusing enough on the topic though as
> >> we're
> >>   seeing a very strong pipeline to both both committer and PMC. Expect
> >> both
> >>   new committers and PMC members during our next reporting period.
> >>
> >> ## PMC changes:
> >>
> >> - Currently 22 PMC members.
> >> - Last PMC member added Fri May 26 2017.
> >>
> >> ## Committer base changes:
> >>
> >> - Currently 34 committers.
> >> - Last committer added Thu Jun 01 2017.
> >>
> >> ## Releases:
> >>
> >> - Apache NiFi 1.4.0 was released Oct 1 2017.
> >>
> >> ## Mailing list activity:
> >>
> >> - Activity on the mailing lists remains extremely high with a mixture
> >>   of new users, contributors, and deeper more experienced users and
> >>   contributors sparking discussion and questions and filing bugs or
> >>   new features.
> >>
> >> - us...@nifi.apache.org:
> >>- 553 subscribers (up 34 in the last 3 months):
> >>- 748 emails sent to list (862 in previous quarter)
> >>
> >> - dev@nifi.apache.org:
> >>- 383 subscribers (up 12 in the last 3 months):
> >>- 604 emails sent to list (947 in previous quarter)
> >>
> >> - iss...@nifi.apache.org:
> >>- 46 subscribers (up 4 in the last 3 months):
> >>- 5775 emails sent to list (7457 in previous quarter)
> >>
> >>
> >> ## JIRA activity:
> >>
> >> - 335 JIRA tickets created in the last 3 months
> >> - 263 JIRA tickets closed/resolved in the last 3 months
> >>
>
> --
Rob

Re: [DISCUSS] Component deprecation annotation

[Rob Moran]

I agree on treating these as we do restricted ones. I will work on some
recommendations for a unique icon that the chooser dialog can display as
well as how to best carry that over onto the canvas component.

It would also be nice to suggest the alternative in the UI, for example
when the user hovers the deprecated icon in the Add Processor dialog,
specifically call out the alternative(s) by name.

Rob

On Apr 30, 2017 10:05 PM, "Andre" <andre-li...@fucs.org> wrote:

All,

Thank you for the feedback.

I will extend the PR so that the required endpoints are in place but will
leave the effective UI design to our UX experts.

Hopefully I should be able to use the @Restricted as a basis for this work.
Otherwise I will shout for some guidance.

Cheers


On Mon, May 1, 2017 at 11:23 AM, Joe Witt <joe.w...@gmail.com> wrote:

> Agreed on both the icon being preferable as the vehicle to show this
> for processors on the graph instead of color and also in emphasizing
> this during processor selection.
>
> Thanks
>
> On Sun, Apr 30, 2017 at 7:21 PM, Matt Burgess <mattyb...@gmail.com> wrote:
> > Visual indication on existing processors is a good thing, but IMO we'll
> definitely need indication on the processor selection dialog, so the user
> will know that we suggest they choose an alternative.
> >
> > Regards,
> > Matt
> >
> >> On Apr 30, 2017, at 7:12 PM, Jeff <jtsw...@gmail.com> wrote:
> >>
> >> I think an icon on the processor would be best to denote an upcoming
> >> deprecation.  That leaves all colors available to the flow design,
since
> >> any color may have specific meaning to any current flow out there.
> >>
> >>> On Sat, Apr 29, 2017 at 3:58 PM Juan Sequeiros <helloj...@gmail.com>
> wrote:
> >>>
> >>> In same train of though maybe make it default to some color other than
> >>> white, instinct says red but that might be used to represent an
> important
> >>> processor. So suggest maybe default beige?
> >>>
> >>>
> >>> On Sat, Apr 29, 2017 at 8:20 AM Andy LoPresto <
> alopresto.apa...@gmail.com>
> >>> wrote:
> >>>
> >>>> I'd leave the graphics work/decisions to someone like Rob Moran, but
I
> >>> see
> >>>> it as similar to the restricted components -- an icon on the
> processors
> >>> on
> >>>> the canvas and the dialog to add components, with additional
> explanation
> >>>> (and maybe a target release for full deprecation) in the help notes.
> >>>>
> >>>> Andy LoPresto
> >>>> alopre...@apache.org
> >>>> alopresto.apa...@gmail.com
> >>>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >>>>
> >>>>> On Apr 29, 2017, at 05:16, Andre <andre-li...@fucs.org> wrote:
> >>>>>
> >>>>> dev,
> >>>>>
> >>>>> In light of the some recent deprecations (ListenLumberjack) and some
> >>>>> potential deprecation (PutJMS/GetJMS) I started some progress on how
> to
> >>>>> document the depreciation of NiFi components using annotations.
> >>>>>
> >>>>> In the absence of any better name I called the annotation
> >>>>> @DeprecationWarning (so not overlap with Java's @Deprecated)
> >>>>>
> >>>>> The suggested modifications are part of PR#1718 and I am keen to
hear
> >>>> your
> >>>>> thoughts.
> >>>>>
> >>>>> While the documentation can be displayed as part of the usage,
> however
> >>> I
> >>>>> would imagine the frequency a user browses to the usage pages will
> >>> reduce
> >>>>> as her/him becomes familiar with the components.
> >>>>>
> >>>>> In light of this it may be a good idea to use  the web UI to
> highlight
> >>> a
> >>>>> processor has been deprecated.
> >>>>>
> >>>>> Would anyone suggest a way of doing so without disrupting the user
> >>>>> experience?
> >>>>>
> >>>>> Cheers
> >>>>
> >>>
>

Re: [ANNOUNCE] New Apache NiFi PMC Member - Oleg Zhurakousky

[Rob Moran]

Thank you and congratulations Oleg!

Rob

On Tue, Apr 4, 2017 at 11:09 PM, Adam Lamar  wrote:

> Congrats Oleg, well deserved!
>

Re: [ANNOUNCE] New Apache NiFi Committer Bin Qiu

[Rob Moran]

Thank you and congratulations BIn!

Rob

On Tue, Apr 4, 2017 at 10:44 PM, Joe Skora  wrote:

> Congratulations and welcome!
>
> On Tue, Apr 4, 2017 at 10:07 PM, Andy LoPresto 
> wrote:
>
> > Great work Bin.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Apr 4, 2017, at 6:03 PM, Matt Burgess  wrote:
> >
> > Congratulations Bin!!
> >
> > On Tue, Apr 4, 2017 at 8:29 PM, Andre  wrote:
> >
> > congrats Bin!
> >
> > Looking forward for building a NiFi-CPP cluster in the future (Late
> > April fool... happy to keep it as MiNiFi-CPP :-) )
> >
> > Cheers
> >
> >
> >
> > On Wed, Apr 5, 2017 at 6:17 AM, Tony Kurc  wrote:
> >
> > Apache NiFi community,
> >
> >
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that Bin
> > Qiu has accepted the PMC's invitation to become a committer on the Apache
> > NiFi project. We greatly appreciate all of Bin’s hard work and generous
> > contributions and look forward to continued involvement in the project.
> >
> > Bin has been one of the driving forces behind MiNiFi - C++, contributing
> a
> > massive amount in terms of code and helping with release verification and
> > always being responsive to the community.
> >
> >
> > Congrats, Bin!
> >
> >
> > - Tony
> >
> >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Jeff Storck

[Rob Moran]

Thanks and congrats, Jeff!

Rob

On Tue, Feb 21, 2017 at 3:01 PM, Pierre Villard  wrote:

> Congrats !
>
> 2017-02-21 20:58 GMT+01:00 Joe Witt :
>
> > Congrats Jeff!
> >
> > On Tue, Feb 21, 2017 at 2:43 PM, Jeremy Dyer  wrote:
> > > Congratulations Jeff! Good to have you aboard!
> > >
> > > On Tue, Feb 21, 2017 at 2:41 PM, Aldrin Piri 
> wrote:
> > >
> > >> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Jeff
> > >> Storck has accepted the PMC's invitation to become a committer on the
> > >> Apache NiFi project. We greatly appreciate all of Jeff's hard work and
> > >> generous contributions and look forward to continued involvement in
> the
> > >> project.
> > >>
> > >> Jeff's contributions include significant efforts toward upgrade and
> > >> migration processes inclusive of flow layout when upgrading from 0.x
> to
> > 1.x
> > >> and the ZooKeeper migration toolkit.
> > >>
> > >> Congrats, Jeff!
> > >>
> >
>

Re: [DISCUSS] Idea for visual access control policy application

[Rob Moran]

If I'm understanding how this security zone concept would work, I think
making decisions about the placement of components on the canvas according
to authorization would introduce a lot of confusion around understanding
the data flow itself and how it is supposed to work.

To me a big part of access policy management that NiFi lacks is the ability
to think about it from an individual user/user group perspective. That
would help those user(s) tasked with managing policies easily think about
and control "what Matt can see and do" and "what the HR group can see and
do."

Perhaps a more engaging UI with drag and drop capabilities would be useful
to help manage it. There I could see the concept of security zones or
profiles (roles?) to help. I'm all for exploring those options, but I think
that experience should happen outside the canvas and not influence
decisions made when building a data flow.

Rob

On Thu, Jan 19, 2017 at 9:33 AM, Matt Gilman <matt.c.gil...@gmail.com>
wrote:

> Thanks for starting this DISCUSS. This is definitely an area that we need
> to continue improving.
>
> The concept of a security zone seems like it could be implemented using a
> Process Group. However, if I'm following along the difference being that
> the security zone does not visually hide encapsulated components. Koji's
> comment about allowing components to share a security zone but not be
> co-located is interesting as well. Continuing down this thought process,
> defining security zones using a selector-like mechanism would allow the
> security zones to automatically update (kind of like a smart playlist).
>
> Definitely some good ideas here. As we continue to introduce these sorts of
> efficiencies we'll need to ensure we have a rock solid UX to ensure there
> is no ambiguity regarding the component policies at any point in time.
>
> Matt
>
> On Wed, Jan 18, 2017 at 8:50 PM, Koji Kawamura <ijokaruma...@gmail.com>
> wrote:
>
> > Hi Andy,
> >
> > I like this idea, too! Enabling security policy for multiple components
> is
> > definitely useful.
> >
> > While I was thinking about the security zone concept, I was wondering if
> > components those share the same level of security policy stay close in 2
> > Dimensional position on a flow. Maybe those components would scatter
> around
> > in a flow, and it'd be hard to put them in a single rectangle area.
> >
> > One alternative approach to apply policy to components came up.
> > That is managing components by adding TAGs or Classes as such in CSS
> class.
> > Then like CSS, specify policies to a particular class. We will also able
> > to alter visual style on NiFi flow based on the style.
> >
> > Just an idea, but wanted to share.
> >
> > Thanks,
> > Koji
> >
> >
> > On Thu, Jan 19, 2017 at 9:49 AM, Andy LoPresto <alopre...@apache.org>
> > wrote:
> >
> >> Thanks for the feedback so far. I don’t want to cut off conversation
> >> here, I just wanted to see if this was worth exploring further and it
> seems
> >> it is. I would love to hear additional input from (among others) Andre
> Fucs
> >> de Miranda and Anders Braindahl who have both offered really valuable
> >> security insight in the past, Matt Gilman who is the Oracle of NiFi
> policy,
> >> and Rob Moran who would know how to make this actually look appealing
> and
> >> work the way users expect.
> >>
> >> I’ll open a ticket for this to facilitate further conversation and make
> >> it trackable.
> >>
> >> Andy LoPresto
> >> alopre...@apache.org
> >> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >>
> >> On Jan 18, 2017, at 3:50 PM, Jeremy Farbota <jfarb...@payoff.com>
> wrote:
> >>
> >> I like this idea. I like moving some of the security controls into the
> >> UI. Using this with Process Groups would be an adequate level of
> >> granularity for me. I think this would add a lot of value to the UI and
> >> adding security policy controls to UI enables super users to manage the
> >> security without needing root access on the server. This could simplify
> the
> >> process of recreating NiFi environments because you can see the security
> >> policies in the UI instead of needing to look at the configs.
> >>
> >> On Wed, Jan 18, 2017 at 12:38 PM, Andy LoPresto <alopre...@apache.org>
> >> wrote:
> >>
> >>> I just opened NIFI-3370 [1] for “apply access control polices
> >>> simulta

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

[Rob Moran]

Thank you and congratulations Jeremy!

Rob

On Tue, Dec 20, 2016 at 7:14 AM, Joe Skora  wrote:

> Congrats Jeremy, welcome!
>
> On Tue, Dec 20, 2016 at 8:47 AM, Pierre Villard <
> pierre.villard...@gmail.com
> > wrote:
>
> > Congrats Jeremy, great to have you!
> >
> > 2016-12-20 6:18 GMT+01:00 Andrew Psaltis :
> >
> > > Congrats Jeremy!!
> > >
> > > On Mon, Dec 19, 2016 at 9:45 PM, Joe Witt  wrote:
> > >
> > > > Well done Jeremy and thanks for all your contributions!
> > > >
> > > > On Mon, Dec 19, 2016 at 9:24 PM, Joe Percivall
> > > >  wrote:
> > > > > Congrats Jeremy! Very well deserved.
> > > > >
> > > > >
> > > > > - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
> > > > joeperciv...@yahoo.com
> > > > >
> > > > >
> > > > > On Monday, December 19, 2016, 9:13:22 PM EST, Bryan Bende <
> > > > bbe...@gmail.com> wrote:Congrats and welcome!
> > > > >
> > > > > On Mon, Dec 19, 2016 at 8:52 PM Matt Burgess  >
> > > > wrote:
> > > > >
> > > > > Congratulations Jeremy and welcome! Very well deserved.
> > > > >
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Matt
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Dec 19, 2016 at 8:23 PM, Aldrin Piri 
> > > wrote:
> > > > >
> > > > >> On behalf of the Apache NiFI PMC, I am very pleased to announce
> that
> > > > > Jeremy
> > > > >
> > > > >> Dyer has accepted the PMC's invitation to become a committer on
> the
> > > > Apache
> > > > >
> > > > >> NiFi project. We greatly appreciate all of Jeremy's hard work and
> > > > generous
> > > > >
> > > > >> contributions and look forward to continued involvement in the
> > > project.
> > > > >
> > > > >>
> > > > >
> > > > >> Jeremy’s contributions include creation a suite of the processors
> > that
> > > > > aided
> > > > >
> > > > >> in parsing HTML, build improvement and testing for MiNiFi, as well
> > as
> > > > many
> > > > >
> > > > >> articles and presentations on using NiFi in new and novel ways.
> > > > >
> > > > >>
> > > > >
> > > > >> Welcome Jeremy!
> > > > >
> > > > > --
> > > > > Sent from Gmail Mobile
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > Andrew
> > >
> > > Subscribe to my book: Streaming Data 
> > > 
> > > twiiter: @itmdata 
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Scott Aslan

[Rob Moran]

Congrats Scott - thanks for all the awesome work!

Rob

On Fri, Nov 4, 2016 at 11:43 AM, Pierre Villard  wrote:

> Congrats! Well deserved is an euphemism ;-)
>
> 2016-11-04 16:32 GMT+01:00 Oleg Zhurakousky 
> :
>
> > Congrats Scott! Well earned!
> >
> > Oleg
> > > On Nov 4, 2016, at 11:25 AM, Tony Kurc  wrote:
> > >
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Scott
> > > Aslan has accepted the PMC's invitation to become a committer on the
> > Apache
> > > NiFi project. We greatly appreciate all of Scott's hard work and
> generous
> > > contributions to the project. We look forward to his continued
> > involvement
> > > in the project.
> > >
> > > For those familiar with the UI improvements in 1.x, a lot of the
> > > implementation was contributed by Scott, so another set of very visible
> > > contributions! (Sorry for the pun, I couldn't help myself).
> > >
> > > Welcome and congratulations!
> > > Tony
> >
> >
>

Re: Double-click action

[Rob Moran]

I think the logic Matt B described would make a lot of sense to experienced
users, but it is changing behavior of the action and that *could* confuse
new users.

But as Lee brought up it is already being used differently, so it very well
could be appreciated as learned behavior.

It would be nice to expose common actions (like configure) on the faces of
components so they are only a single click away. However, it would be tough
to add more to them given current layouts.

Rob

On Mon, Oct 24, 2016 at 10:49 AM, Matt Gilman 
wrote:

> Certainly not the first time this has been brought up... in fact, there's
> already a JIRA for it [1]. Use of double click on the connection is a great
> counter point for consistency between the components.
>
> [1] https://issues.apache.org/jira/browse/NIFI-1580
>
> On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:
>
> > Don't forget about connection behavior.
> >
> > Double-click on a connection places a movable vertex on the connection.
> > Double-click on a vertex deletes it.
> >
> > Very intuitive once you realize it's there.
> >
> > Lee
> >
> >
> > > On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
> > STaTS/StorefrontRemote)  wrote:
> > >
> > > I like this, Matt.  It has often find myself double clicking to try to
> > configure, or view configuration.  It just seems natural.
> > >
> > >
> > > Chris McDermott
> > >
> > > Remote Business Analytics
> > > STaTS/StoreFront Remote
> > > HPE Storage
> > > Hewlett Packard Enterprise
> > > Mobile: +1 978-697-5315
> > >
> > >
> > >
> > > On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:
> > >
> > >+1 for avoiding confusion or changing existing behavior, but I
> think a
> > >good compromise is to leave the Configure option on both context
> menus
> > >(right-click, e.g.) and add the double-click behavior to the
> Processor
> > >to open the configuration dialog. In that case, the default
> > >(double-click) option for both Processors and Process Groups is no
> > >longer "nothing" and "Enter Group" respectively; rather it is
> > >conceptually something like "Drill-down". For PGs drill-down is
> Enter
> > >Group, for Processors you can't drill down any further than the
> config
> > >dialog, so that becomes the default action for double-click.
> > >
> > >Thoughts? Thanks,
> > >Matt
> > >
> > >On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
> > > wrote:
> > >> Yep, that's a good point and I agree we should avoid confusion with
> > >> different behaviors depending of the components.
> > >>
> > >> Thanks Matt!
> > >>
> > >> Pierre
> > >>
> > >> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
> > >>
> > >>> Pierre,
> > >>>
> > >>> Currently the double click action is used to enter a Process Group.
> > >>> There's been discussion in the past on this mailing about possibly
> > using it
> > >>> to configure. My only hesitation there would be the inconsistency
> > between
> > >>> action on the different components. Unless of course we also switch
> the
> > >>> action for entering a group. Then I start to worry about confusing
> the
> > user
> > >>> with changing up the existing behavior too much.
> > >>>
> > >>> Matt
> > >>>
> > >>> Sent from my iPhone
> > >>>
> >  On Oct 24, 2016, at 7:39 AM, Pierre Villard <
> > pierre.villard...@gmail.com>
> > >>> wrote:
> > 
> >  Hi,
> > 
> >  I was wondering if there is any reason why the double click action
> is
> > not
> >  used in the UI? I think this could be a nice shortcut to access
> >  "Configure/View configuration" view from elements on the canvas.
> > >>> Thoughts?
> > 
> >  Pierre
> > >>>
> > >
> > >
> >
>

Re: Jira privileges request

[Rob Moran]

Thanks Mark!

Rob

On Tue, Jul 19, 2016 at 3:13 PM, Mark Payne <marka...@hotmail.com> wrote:

> Rob,
>
> You should be good to go! Let me know if you have any problem.
>
> Thanks
> -Mark
>
>
> > On Jul 19, 2016, at 2:47 PM, Rob Moran <rmo...@gmail.com> wrote:
> >
> > I'd like to assign some issues to myself as well. Can I be added to the
> > contributors role?
> >
> > My username is rmoran
> >
> > Rob
> >
> > On Tue, Jul 12, 2016 at 5:22 PM, Andrew Psaltis <
> psaltis.and...@gmail.com>
> > wrote:
> >
> >> Thank you sir!
> >>
> >> On Tue, Jul 12, 2016 at 5:11 PM, Tony Kurc <trk...@gmail.com> wrote:
> >>
> >>> Andrew, I added you to Contributors.
> >>>
> >>> On Tue, Jul 12, 2016 at 5:06 PM, Andrew Psaltis <
> >> psaltis.and...@gmail.com>
> >>> wrote:
> >>>
> >>>> Bryan,
> >>>> While you are in the giving mood -- can you please add my id: apsaltis
> >>>>
> >>>> Thanks,
> >>>> Andrew
> >>>>
> >>>> On Tue, Jul 12, 2016 at 4:58 PM, Bryan Bende <bbe...@gmail.com>
> wrote:
> >>>>
> >>>>> Haimo,
> >>>>>
> >>>>> You are now added as well.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Bryan
> >>>>>
> >>>>> On Tue, Jul 12, 2016 at 4:40 PM, Haimo Liu <haimoli...@gmail.com>
> >>> wrote:
> >>>>>
> >>>>>> Hi Bryan,
> >>>>>>
> >>>>>> I would be more than glad to become a contributor too, can you help
> >>>> grant
> >>>>>> me the same JIRA privilege? Username: h_liu
> >>>>>>
> >>>>>> Thanks!
> >>>>>> Haimo
> >>>>>>
> >>>>>> On Tue, Jul 12, 2016 at 1:12 PM, Andrew Lim <
> >>>> andrewlim.apa...@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Thanks Bryan!  I think I’m all set now.
> >>>>>>>
> >>>>>>> -Drew
> >>>>>>>
> >>>>>>>> On Jul 12, 2016, at 1:09 PM, Bryan Bende <bbe...@gmail.com>
> >>> wrote:
> >>>>>>>>
> >>>>>>>> Drew,
> >>>>>>>>
> >>>>>>>> I added you the contributors role in JIRA. Let us know if you
> >>> still
> >>>>>> can't
> >>>>>>>> assign tickets.
> >>>>>>>>
> >>>>>>>> -Bryan
> >>>>>>>>
> >>>>>>>> On Tue, Jul 12, 2016 at 1:06 PM, Andrew Lim <
> >>>>>> andrewlim.apa...@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> There are some tickets that I would like to assist on and
> >> assign
> >>>> to
> >>>>>>>>> myself.  Could I be given the privileges in Jira to do so?
> >>>>>>>>>
> >>>>>>>>> My username is:   andrewmlim
> >>>>>>>>>
> >>>>>>>>> Thanks!
> >>>>>>>>>
> >>>>>>>>> -Drew
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Thanks,
> >>>> Andrew
> >>>>
> >>>> Subscribe to my book: Streaming Data <http://manning.com/psaltis>
> >>>> <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306>
> >>>> twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata
> >
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Andrew
> >>
> >> Subscribe to my book: Streaming Data <http://manning.com/psaltis>
> >> <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306>
> >> twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata>
> >>
>
>

Re: Jira privileges request

[Rob Moran]

I'd like to assign some issues to myself as well. Can I be added to the
contributors role?

My username is rmoran

Rob

On Tue, Jul 12, 2016 at 5:22 PM, Andrew Psaltis 
wrote:

> Thank you sir!
>
> On Tue, Jul 12, 2016 at 5:11 PM, Tony Kurc  wrote:
>
> > Andrew, I added you to Contributors.
> >
> > On Tue, Jul 12, 2016 at 5:06 PM, Andrew Psaltis <
> psaltis.and...@gmail.com>
> > wrote:
> >
> > > Bryan,
> > > While you are in the giving mood -- can you please add my id: apsaltis
> > >
> > > Thanks,
> > > Andrew
> > >
> > > On Tue, Jul 12, 2016 at 4:58 PM, Bryan Bende  wrote:
> > >
> > > > Haimo,
> > > >
> > > > You are now added as well.
> > > >
> > > > Thanks,
> > > >
> > > > Bryan
> > > >
> > > > On Tue, Jul 12, 2016 at 4:40 PM, Haimo Liu 
> > wrote:
> > > >
> > > > > Hi Bryan,
> > > > >
> > > > > I would be more than glad to become a contributor too, can you help
> > > grant
> > > > > me the same JIRA privilege? Username: h_liu
> > > > >
> > > > > Thanks!
> > > > > Haimo
> > > > >
> > > > > On Tue, Jul 12, 2016 at 1:12 PM, Andrew Lim <
> > > andrewlim.apa...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks Bryan!  I think I’m all set now.
> > > > > >
> > > > > > -Drew
> > > > > >
> > > > > > > On Jul 12, 2016, at 1:09 PM, Bryan Bende 
> > wrote:
> > > > > > >
> > > > > > > Drew,
> > > > > > >
> > > > > > > I added you the contributors role in JIRA. Let us know if you
> > still
> > > > > can't
> > > > > > > assign tickets.
> > > > > > >
> > > > > > > -Bryan
> > > > > > >
> > > > > > > On Tue, Jul 12, 2016 at 1:06 PM, Andrew Lim <
> > > > > andrewlim.apa...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> There are some tickets that I would like to assist on and
> assign
> > > to
> > > > > > >> myself.  Could I be given the privileges in Jira to do so?
> > > > > > >>
> > > > > > >> My username is:   andrewmlim
> > > > > > >>
> > > > > > >> Thanks!
> > > > > > >>
> > > > > > >> -Drew
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > Andrew
> > >
> > > Subscribe to my book: Streaming Data 
> > > 
> > > twiiter: @itmdata 
> > >
> >
>
>
>
> --
> Thanks,
> Andrew
>
> Subscribe to my book: Streaming Data 
> 
> twiiter: @itmdata 
>

Re: NiFi Web UI development in Dreamweaver

[Rob Moran]

Colin,

Just wanted to echo some of the comments from other responses so far and
say welcome. I've been putting together the mockups you see in NIFI-1323
. The initial goal is to
modernize a bit for a nice foundation as we plan more key functionality and
end-user experience improvements. Again, if you're interested we'd
appreciate your opinions on that effort.

Also - I'd be interested in your results using Dreamweaver. As a designer I
primarily use Adobe Illustrator, but I have access to Dreamweaver and if I
could leverage it to help on the implementation/development side that'd be
great.

Rob

On Wed, Apr 13, 2016 at 1:58 PM, Matt Gilman 
wrote:

> Colin,
>
> Thanks for checking out Apache NiFi. The UI is a packaged as a Java web
> application that is built as part of NiFi's build process. NiFi uses Maven
> to build and package the application. You should be able to edit the
> sources that comprise that WAR with any IDE that can import Maven projects.
> At that point, you should be able to edit all the JSP files, Javascript
> files, and CSS files.
>
> As Joe mentioned, there is currently an effort underway to fresh the look
> and feel as described in NIFI-1323. Let me know if you have any other
> questions.
>
> Matt
>
> On Wed, Apr 13, 2016 at 12:49 PM, Joe Witt  wrote:
>
> > Colin,
> >
> > I'll defer to others to comment on the specifics around dreamweaver or
> > other tools but I do want to reach out and suggest you could also
> > contribute to https://issues.apache.org/jira/browse/NIFI-1323 which is
> > part of the NiFi 1.0.0 efforts and is under active design/discussion
> > and implementation.  By no means should that deter from whatever else
> > you might want to do but if you're interested happy to hear your
> > opinions there.
> >
> > Thanks
> > Joe
> >
> > On Wed, Apr 13, 2016 at 11:46 AM, Colin Bowdery
> >  wrote:
> > > Hi All,
> > >
> > > Can anyone provide any pointers as to how I might be able to develop
> the
> > NiFi Web UI using a tool such as Dreamweaver? I have been modifying
> > nifi-web-ui-0.6.0-SNAPSHOT.war manually but would really like to use a
> more
> > professional approach. I also note there are no HTML files in this .war.
> > >
> > > Objective is to test out some alternative layouts, styling, test
> various
> > browser support and benchmark performance. I am happy to share the
> results
> > back to the dev team.
> > >
> > > Many thanks,
> > >
> > >
> > > Colin.
> > >
> >
>

Re: [VOTE] Establish Apache MiNiFi, a subproject of Apache NIFi

[Rob Moran]

+1

Rob

On Sat, Apr 9, 2016 at 3:48 AM, Jennifer Barnabee <
jennifer.barna...@gmail.com> wrote:

> +1
>
> On Sat, Apr 9, 2016 at 1:13 AM, Joe Witt  wrote:
>
> > Team,
> >
> > Following a solid discussion [1] in early January regarding
> > establishment of MiNiFi as a subproject of NiFi I'd like to call a
> > formal vote to record this important community decision and
> > established consensus.
> >
> > Through lazy consensus [2] the repositories were setup for source,
> > JIRA, and git-hub mirror [3].  There has since been solid progress and
> > discussion on a number of MINIFI JIRAs.  The core goals of MiNiFi have
> > been documented on Confluence/Wiki [4].  It was also reported in our
> > April 2016 board report that we have established MiNiFi based on these
> > things.  But, lets make sure we get this right.
> >
> > [1] https://s.apache.org/czuz
> > [2] https://s.apache.org/Ucxs
> > [3]
> >
> https://cwiki.apache.org/confluence/display/NIFI/Supporting+Infrastructure
> > [4] https://cwiki.apache.org/confluence/display/NIFI/MiNiFi
> >
> > I am a +1 and am very excited by the progress made thus far!
> >
> > The vote will be open for 72 hours and be a majority rule vote.
> >
> > [ ] +1 Establish Apache MiNiFi, a subproject of Apache NiFi
> > [ ]   0 Do not care
> > [ ]  -1 Do not establish Apache MiNiFi
> >
> > Thanks
> > Joe
> >
>

Re: Errors in your Documentation

[Rob Moran]

Regarding the "undo" feature, just wanted to mention there is a ticket [1].
On a related note, there was also talk of confirmation dialogs as perhaps
an alternate way of catching unintended actions [2].

[1] https://issues.apache.org/jira/browse/NIFI-833
[2] https://issues.apache.org/jira/browse/NIFI-1089

Rob

On Wed, Mar 23, 2016 at 1:13 PM, Andy LoPresto 
wrote:

> Paul,
>
> Please create Jira tickets with your feature requests. I have not
> previously encountered users making this request, so I want to ensure we
> capture all of your desires for a successful implementation of this feature
> in order to accurately estimate the resources necessary for it and
> prioritize it accordingly.
>
> Please consider how you would like NiFi to indicate the current mode,
> whether this “operational” mode would allow any changes to processor
> properties and addition of new processors or simply fixes the location of
> canvas elements, the mechanism to switch between modes conveniently, if
> this would affect the UI only or the REST API as well, etc.
>
> To the best of my knowledge, we have not had any requests for a feature
> like this, nor do many/most of our users envision the environment in this
> split mode mentality. Users who should not be able to modify the flow
> usually are assigned the ROLE_MONITOR role, and those who need to
> manipulate the flow itself have not mentioned the issues you brought up.
>
>
> Andy LoPresto
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Mar 23, 2016, at 4:28 AM, Paul Nahay  wrote:
>
> Thanks. I wouldn't be able to send you any screen shots, as the system
> with NiFi is not the same as this which I can send email on.
>
> Yes, I'm asking about a feature whereby a single user can switch back and
> forth between these two modes. When I first encountered NiFi, THIS was the
> most glaring omission, in my view. The use case occurs every day by many
> people: we inadvertently move something, and since you have no "undo" (the
> 2nd most glaring omission), the canvas is screwed up. THIS HAPPENS ALL THE
> TIME. It seems an obviously need thing to me. Basically one is interacting
> with the canvas in one of two situations: "operationally", in which case
> one DOES NOT WANT ANYTHING TO MOVE, not matter how one clicks around the
> canvas, and "editing-ally", in which we DO want to move things around.
>
> Computers routinely are programmed to help us, including help us NOT do
> things we do NOT want done, including inadvertent things. Why can't NiFi
> help us with this? Why can't we say "hey, NiFi, I'm going to use you
> operationally, I'm not modifying anything", and have NiFi NOT allow things
> to be moved around?
>
> I know your answer: "So don't move things around". But given that I have
> to use the mouse when I'm using it operationally, including clicking to
> drag the entire canvas around so I can see things, it is not hard to
> understand that if I click slight off of where I intend, I can
> inadvertently move things that I do not intend to move. Again, THIS HAPPENS
> ALL THE TIME, and not just by me.
>
> PLEASE, add an "EDIT MODE/OPERATION MODE" toggle, and although I know it
> would be very difficult to do, add some for of canvas "undo", at LEAST "one
> level", letting you restore something you just deleted!
>
> Paul
>
> -Original Message-
> From: Andy LoPresto
> Sent: Mar 22, 2016 8:03 PM
> To: Paul Nahay
> Cc: dev@nifi.apache.org
> Subject: Re: Errors in your Documentation
>
> Thanks Paul.
>
> Bugs and feature requests can be submitted here [1] which will ensure they
> are seen by the entire team/community. The most helpful reports include
> screenshots when applicable, current system description, and potential use
> cases or unit tests to verify issue resolution.
>
> Very quickly, you can accomplish a “non-edit mode” by assigning
> “ROLE_MONITOR” to a user in the authorized-users.xml configuration file,
> but currently a feature whereby a single user can switch back and forth
> between those two modes instantaneously does not exist. Can you describe
> the use case where you see this being valuable? Are you having trouble and
> accidentally modifying items on the canvas?
>
> [1]
> https://issues.apache.org/jira/browse/NIFI/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
>
> Andy LoPresto
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Mar 22, 2016, at 4:55 PM, Paul Nahay  wrote:
>
> Great.
>
> I can tell you a list of things I think need to be improved in NiFi. The
> most important is having two “modes” that one is always in, an “edit mode”,
> which is basically what you have 100% of the time now, and a “non-edit
> mode”, where the user cannot move things (inadvertently) around on the
> canvas.
>
> Oh, and you desperately need an “undo”.
>
> Paul
>
> *From:* Andy LoPresto 

Re: Auto-Organize Layout

[Rob Moran]

I agree with Matt's points. I was just replying with something similar
basically saying I think trying to set a standard would not be
well-received.

I believe what could be more useful are layout tools that would help users
place components to help achieve their preferred layouts. For example, the
ability to align (left, right, center) components
or horizontally/vertically distribute components evenly. Other features
such as snap-to and/or smart-guides could make it easier for users to
follow their organization's best practices when designing a flow.

Rob

On Tue, Jan 19, 2016 at 1:49 PM, Matthew Clarke <matt.clarke@gmail.com>
wrote:

> Ryan,
>
>   Setting a standard is a difficult thing to do.  The complexity
> that can exist in many flows would make enforcing a standard difficult. The
> first example you provide of success to points right while failures point
> up is not recommended. It would be better to have failures point down since
> it is common to put labels over processor(s). Any relationships pointing up
> would pass through these labels making both the relationship box and the
> label hard to read.  It is often coomon to see flows designed with a
> combination of left to right and top to bottom design.
>
> Matt
>
> On Tue, Jan 19, 2016 at 12:07 PM, Ryan H <rhendrickson.w...@gmail.com>
> wrote:
>
> > Hi Rob,
> > Yea we did, it was at the end of the meeting.
> >
> > I think it would be useful to have a couple default type views that
> > help standardize flow layout across the community.
> >
> > For example, when we organize processors left-to-right, failure
> > relationships always point up, and success always point right.
> > Alternatively, when we organize processors up-and-down, failure
> > relationships always point left, and successes always point down.
> >
> > Of course, in some of these scenarios there are processors that have
> > more than 1 success relationship, but that's when a good layout library
> > would come into play.
> >
> > What do you think?
> >
> > On Tue, Jan 19, 2016 at 11:10 AM, Rob Moran <rmo...@gmail.com> wrote:
> >
> > > Ryan - I think we spoke briefly (at a very high level) about this at a
> > > prior meetup. What alternate views did you have in mind, and in what
> ways
> > > do you think they'd be useful?
> > >
> > > Rob
> > >
> > > On Tue, Jan 19, 2016 at 10:56 AM, Ryan H <rhendrickson.w...@gmail.com>
> > > wrote:
> > >
> > > > It'd be pretty awesome if NiFi provided the ability to auto-organize
> a
> > > > layout.
> > > >
> > > > Maybe even just a auto-organized layout that doesn't change the
> > flow.xml,
> > > > just an alternate view.
> > > >
> > > > Looking at these demos here: http://js.cytoscape.org/#demos
> > > >
> > > > Ryan
> > > >
> > >
> >
>

Redesign User Interface (UI)

[Rob Moran]

Greetings ​​NiFi community,

NIFI-1323 [1] has been mentioned in (at least one) previous thread. In case
you are unaware, it involves beginning work on a series of UI improvements.

I'd like to point your attention to the wiki page [2] where you can read up
on factors that are driving this effort.

[1] https://issues.apache.org/jira/browse/NIFI-1323
[2] https://cwiki.apache.org/confluence/display/NIFI/Redesign+User+Interface

Thanks,
Rob

Re: Redesign User Interface (UI)

[Rob Moran]

Echoing Matt G's last comment regarding changes, with a little more
detail...

These are mainly style changes. The positioning changes are taking current
actions related to operating the flow into a docked panel. That appears
along with a separate one housing navigation controls. The other
positioning change is moving breadcrumbs to the bottom, styled similarly to
the panels in an effort to better connect those pieces to the user's
component interaction on the canvas.


Thanks,
Rob

On Wed, Jan 6, 2016 at 2:40 PM, Matt Gilman <matt.c.gil...@gmail.com> wrote:

> Tony,
>
> That is correct. The UI redesign is necessary for a 1.0 feature.
> Additionally, the UI changes are limited to styling and positioning of
> certain elements for controlling the dataflow.
>
> Matt
>
> On Wed, Jan 6, 2016 at 2:33 PM, Tony Kurc <trk...@gmail.com> wrote:
>
> > Matt,
> > I'm not sure I followed. I think you said we have two things:
> > A) ui redesign
> > B) multi-tenant dataflow
> >
> > We need A before B, and B will be in 1.0, so we need A in a release
> before
> > 1.0.
> >
> >
> > Tony
> >
> > On Wed, Jan 6, 2016 at 2:17 PM, Matt Gilman <matt.c.gil...@gmail.com>
> > wrote:
> >
> > > One of the items that's needed to go over the 1.0 cliff is support for
> > > multi-tenant dataflows. Scoping user authorization to portions of a
> > > dataflow will require a major bump due to API changes and the like.
> Part
> > of
> > > the motivation for this UI redesign is laying the foundation for that
> > > effort. Additionally, we'll get the added benefit of supporting a more
> > > responsive layout and modernized look and feel in the meantime.
> > >
> > > Matt
> > >
> > > On Wed, Jan 6, 2016 at 1:28 PM, Sean Busbey <bus...@cloudera.com>
> wrote:
> > >
> > > > +1 to "UI redesign warrants a major version increment"
> > > >
> > > > I know that we're "pre 1.0", but this sounds like it's time to figure
> > out
> > > > what we need to include to go over that cliff.
> > > >
> > > > On Wed, Jan 6, 2016 at 12:22 PM, Tony Kurc <trk...@gmail.com> wrote:
> > > >
> > > > > Looks great so far!
> > > > >
> > > > > I saw the target release of 0.6, which surprised me a bit. I would
> > have
> > > > > expected this significant of a change would warrant a major release
> > > > > increment.
> > > > >
> > > > > On Wed, Jan 6, 2016 at 1:08 PM, Rob Moran <rmo...@gmail.com>
> wrote:
> > > > >
> > > > > > Greetings ​​NiFi community,
> > > > > >
> > > > > > NIFI-1323 [1] has been mentioned in (at least one) previous
> thread.
> > > In
> > > > > case
> > > > > > you are unaware, it involves beginning work on a series of UI
> > > > > improvements.
> > > > > >
> > > > > > I'd like to point your attention to the wiki page [2] where you
> can
> > > > read
> > > > > up
> > > > > > on factors that are driving this effort.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/NIFI-1323
> > > > > > [2]
> > > > > >
> > > >
> > https://cwiki.apache.org/confluence/display/NIFI/Redesign+User+Interface
> > > > > >
> > > > > > Thanks,
> > > > > > Rob
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean
> > > >
> > >
> >
>