Re: [VOTE] Release Apache NiFi 2.0.0 (RC2)

[Scott Aslan]

+1 (binding)

I followed the release guide, verified successful build, and launched the
UI to create a few data flows to verify UI/UX in both light and dark mode
theming, as well as to check for any other UI defects. I verified that the
following issues have been addressed in this RC:

   -

   Sidenav font color does not align with the application's font color:
   NIFI-13917 
   -

   The mat-select icon is slightly misaligned: NIFI-13916
   
   -

   codemirror theming updates: NIFI-13925
   
   -

   draggable new canvas component icon color: NIFI-13920
   

Thanks again David.

-Scott

On Tue, Oct 29, 2024 at 11:25 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 2.0.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
>
> The source being voted on the and the convenience binaries are
> available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1294/
>
> Git Tag: nifi-2.0.0-RC2
> Git Commit ID: 2f13b609bdb77cb985aa35e8b66b4f04274d7c59
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/2f13b609bdb77cb985aa35e8b66b4f04274d7c59
>
> Checksums of nifi-2.0.0-source-release.zip
>
> SHA512:
> deff4c81842759ef14651874a1b3204f75d0287a578174505b409ab2869704ed77527a5e262dd030bb7a5d1531a8d55105b015444c5802f55caf80439fe11220
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file is available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> Issues resolved for this version: 358
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354889
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.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.
> Then please vote:
>
> [] +1 Release this package as nifi-2.0.0
> [] +0 no opinion
> [] -1 Do not release this package because...
>

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

[Scott Aslan]

+1 (binding)

I followed the release guide, verified successful build, and launched the
UI to create a few data flows to verify UI/UX in both light and dark mode
theming, as well as to check for any other UI defects. I encountered a few
minor issues, but none of these should block the release candidate:

   -

   Sidenav font color does not align with the application's font color:
   NIFI-13917  (PR
   submitted)
   -

   The root group UUID is missing from the flow analysis drawer on the
   canvas:
   NIFI-13918 
   -

   The mat-select icon is slightly misaligned:
   NIFI-13916  (PR
   submitted)

It is always a pleasure to collaborate with such a talented group of
contributors, especially on such a milestone release! Thanks for RM'ing,
David!


On Wed, Oct 23, 2024 at 10:56 AM Bryan Bende  wrote:

> +1 (binding)
>
> Verified everything in the release helper and built some flows with
> custom Python processors.
>
> Thanks David!
>
> On Tue, Oct 22, 2024 at 5:36 PM Lehel Boér  wrote:
> >
> > +1 (non-binding)
> >
> > Ran through release helper, verified successful build.
> >
> > Conf:
> > Apache Maven 3.9.9
> > openjdk version "21" 2023-09-19 LTS
> > OpenJDK Runtime Environment Corretto-21.0.0.35.1 (build 21+35-LTS)
> > OpenJDK 64-Bit Server VM Corretto-21.0.0.35.1 (build 21+35-LTS, mixed
> mode, sharing)
> > Default locale: en_US, platform encoding: UTF-8
> > ProductName: macOS
> > ProductVersion: 14.5
> > BuildVersion: 23F79
> >
> > Checked a few commits.
> >
> >
> > Thanks for RM'ing David!
> >
> > 
> > From: Kedvessy Péter 
> > Sent: Tuesday, October 22, 2024 15:52
> > To: dev@nifi.apache.org 
> > Subject: Re: [VOTE] Release Apache NiFi 2.0.0 (RC1)
> >
> > +1 non-binding
> >
> > Verified the followings:
> >   - checksum and signature
> >   - git commit hash and tag
> >   - NiFi build with contrib-check on the following environment:
> > - mac os x 14.3.1
> > - openjdk 21.0.3 2024-04-16 LTS
> >   OpenJDK Runtime Environment Temurin-21.0.3+9 (build 21.0.3+9-LTS)
> >   OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (build 21.0.3+9-LTS,
> mixed
> > mode)
> > - maven 3.9.9
> >   - simple flow execution
> >   - new minifi java agent features
> >
> > Thanks for managing this release, David.
> > Regards,
> > Peter
> >
> > Chris Sampson  ezt írta (időpont:
> 2024.
> > okt. 22., K, 22:10):
> >
> > > +1 (binding)
> > >
> > > Followed the release helper to verify and build NiFi on:
> > >
> > >1. MacOS 15.0.1
> > >2. Java: OpenJDK Runtime Environment Temurin-21.0.5+11 (build
> > >21.0.5+11-LTS)
> > >
> > > Built the NiFi, NiFi Registry, and NiFi Toolkit docker Images using
> Podman
> > > 5.2.5.
> > >
> > > Started and configured securely with custom certificates for 2-way
> mTLS and
> > > PKI Authentication.
> > >
> > > Configured multiple components, imported Flows, verified authenticated
> > > Site-To-Site communications, and sent data to an Elasticsearch instance
> > > from NiFi.
> > >
> > >
> > > Great work all, and thanks again David for RM'ing.
> > >
> > >
> > > Cheers,
> > >
> > > ---
> > > *Chris Sampson*
> > > Technical Lead, Solution Architect, Principal Software Engineer
> > > Naimuri
> > >
> > >
> > > Click here to join our newsletter
> > > <
> > >
> https://docs.google.com/forms/d/e/1FAIpQLSdkOWwC2zWL_vW0mlaoNl0RsbLvvvRi3R1L7V9DhcmRMlNmHw/viewform
> > > >
> > >
> > >
> > > On Tue, 22 Oct 2024 at 20:40, Joe Witt  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > We kicked off the discussion thread for doing a 2.0 release in July
> 2021
> > > :)
> > > >
> > > > Thanks Everyone!
> > > >
> > > > Joe
> > > >
> > > > On Tue, Oct 22, 2024 at 12:37 PM Robert Fellows <
> rob.fell...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > I focused mainly on the new user interface. looks really good but
> > > noted a
> > > > > few issues that should get addressed. Nothing that I would suggest
> > > > sinking
> > > > > the RC for though.
> > > > >
> > > > > Otherwise, It is looking good! So Exciting!
> > > > >
> > > > >- Light mode - Drag icons of components are nearly invisible
> > > > >   - https://issues.apache.org/jira/browse/NIFI-13920
> > > > >- Cancelling of edit dialog of current process group does not
> remove
> > > > the
> > > > >"/edit" from the route
> > > > >   - https://issues.apache.org/jira/browse/NIFI-13921
> > > > >
> > > > >
> > > > > Java Details:
> > > > > openjdk version "21.0.1" 2023-10-17 LTS
> > > > > OpenJDK Runtime Environment Zulu21.30+15-CA (build 21.0.1+12-LTS)
> > > > > OpenJDK 64-Bit Server VM Zulu21.30+15-CA (build 21.0.1+12-LTS,
> mixed
> > > > mode,
> > > > > sharing)
> > > > >
> > > > > Built on Mac OS 14.7 (Sonoma)
> > > > >
> > > > > On Tue, Oct 22, 2024 at 1:03 AM David Handermann <
> > > > > exceptionfact...@apache.org> wrote

Re: [DISCUSS] Preparing Release of Apache NiFi 2.0.0

[Scott Aslan]

The number of resolved issues is impressive and the results are something
we can all be proud of! +1! Thanks for RM'ing David!

On Wed, Oct 16, 2024 at 12:00 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> It has been almost one year since we released Milestone 1 of NiFi
> 2.0.0. Over the four milestone releases, we have resolved almost 2000
> Jira issues, added numerous capabilities, and removed large amounts of
> technical debt. Although there is always more that could be done, we
> have reached the point where we should release a stable 2.0.0 version.
>
> The current release version [1] has almost 300 Jira issues resolved.
> With the release of NiFi API 2.0.0 and the NiFi NAR Maven Plugin
> 2.1.0, we are in a solid position to go forward with a 2.0.0 version.
> Although there are bound to be additional areas we want to improve, we
> should consider those after a general availability release.
>
> With that background, I would be glad to handle Release Manager
> responsibilities for this version. Unless there are any critical
> blockers, I plan to start the release candidate process before the end
> of this week. That should allow time for a few more items to be
> completed.
>
> Regards,
> David Handermann
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354889
>

Re: [DISCUSS] Progress Update on new UI

[Scott Aslan]

Outstanding! The new UI is fun, fast, and fantastic. Gathering feedback
from the community will be invaluable, and the best way to do this is by
having them actively use the new UI.

On Thu, May 30, 2024 at 12:37 PM Matt Gilman 
wrote:

> Team,
>
> About a month ago a [DISCUSS] thread was sent regarding the UI updates and
> requesting that any future contributions target both old and new UIs. Since
> then there has been substantial progress as we continue to close the gap on
> feature parity with the old UI. Only a few features remain [1] [2] [3] [4].
>
> The updated UI was included in the most recent 2.0.0-M3 release [5]
> alongside the old UI. Since then we've received lots of helpful feedback
> and all reported bugs and differences from the existing UI have been
> addressed. A new JIRA has been filed [6] to remove the old UI and install
> the new UI as the default. This will be a great step forward to be able to
> move away from some frameworks that are no longer officially supported [7].
> When 2.0.0-M4 is released it will only contain the new UI. Until then
> please continue to provide any feedback.
>
> Additional work has begun that will establish a good path forward on
> modernizing the remaining UIs within NiFi (documentation, data viewers,
> custom UIs, etc) that also have outdated/unsupported dependencies. As we
> continue to make progress on the remaining features, work will begin to
> start modernizing these other UIs.
>
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-13316
> [2] https://issues.apache.org/jira/browse/NIFI-13317
> [3] https://issues.apache.org/jira/browse/NIFI-13318
> [4] https://issues.apache.org/jira/browse/NIFI-13319
> [5]
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
> [6] https://issues.apache.org/jira/browse/NIFI-13313
> [7] https://issues.apache.org/jira/browse/NIFI-11481
>

Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)

[Scott Aslan]

+1 binding

- Ran through the release helper.
- Verified signatures and hashes.

Thanks for RM'ing David.

On Mon, May 13, 2024 at 11:49 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 2.0.0-M3.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
>
> The source being voted on and the convenience binaries are available
> on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1269
>
> Git Tag: nifi-2.0.0-M3-RC1
> Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd
>
> Checksums of nifi-2.0.0-M3-source-release.zip
>
> SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a
> SHA512:
> cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file is available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> Issues resolved for this version: 411
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354155
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
>
> 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.
> Then please vote:
>
> [] +1 Release this package as nifi-2.0.0-M3
> [] +0 no opinion
> [] -1 Do not release this package because...
>

Re: [DISCUSS] UI Contributions

[Scott Aslan]

+1 Rob

On Wed, Apr 24, 2024 at 8:17 AM Robert Fellows 
wrote:

> The new UI has progressed quite well and I agree with this stance. However,
> with 2.0 getting close, one could argue that new UI features should
> definitely land in the new UI but only really need to land in the original
> UI if desired or to support backward compatibility.
>
> --Rob
>
> On Tue, Apr 23, 2024 at 7:55 PM Scott Aslan  wrote:
>
> > Thanks for sending this out Matt! I agree that at this point any new
> > features to the frontend should be implemented in both the new and the
> > existing UI. Updating the contributions guidelines seems appropriate as
> > well.
> >
> > -Scott
> >
> > On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman  wrote:
> >
> > > Team,
> > >
> > > Substantial progress has been made on modernizing the NiFi UI under [1]
> > and
> > > [2]. As detailed in the JIRAs, this effort has been largely motivated
> by
> > > moving away from deprecated and unsupported dependencies. As we begin
> the
> > > process to transition to the new UI, we are at a point where any UI
> > > contributions should target both the new UI and the existing UI. We've
> > > updated the PR template detailing this and the README for the new UI
> [3]
> > to
> > > help introduce folks making UI contributions to the layout of the
> > > repository. It discusses the steps needed to build NiFi with the new UI
> > > included and how to access it.
> > >
> > > Happy to discuss any questions folks may have.
> > >
> > > Matt
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-11481
> > > [2] https://issues.apache.org/jira/browse/NIFI-12400
> > > [3] https://github.com/apache/nifi/pull/8693
> > >
> >
>
>
> --
> ---
> Rob Fellows
>

Re: [DISCUSS] UI Contributions

[Scott Aslan]

Thanks for sending this out Matt! I agree that at this point any new
features to the frontend should be implemented in both the new and the
existing UI. Updating the contributions guidelines seems appropriate as
well.

-Scott

On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman  wrote:

> Team,
>
> Substantial progress has been made on modernizing the NiFi UI under [1] and
> [2]. As detailed in the JIRAs, this effort has been largely motivated by
> moving away from deprecated and unsupported dependencies. As we begin the
> process to transition to the new UI, we are at a point where any UI
> contributions should target both the new UI and the existing UI. We've
> updated the PR template detailing this and the README for the new UI [3] to
> help introduce folks making UI contributions to the layout of the
> repository. It discusses the steps needed to build NiFi with the new UI
> included and how to access it.
>
> Happy to discuss any questions folks may have.
>
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-11481
> [2] https://issues.apache.org/jira/browse/NIFI-12400
> [3] https://github.com/apache/nifi/pull/8693
>

Re: [VOTE] Release Apache NiFi 1.23.0 (RC3)

[Scott Aslan]

+1 (binding)

Verified signatures, hashes, build, etc. Tested various use cases.

On Thu, Jul 27, 2023 at 8:57 AM Arpad Boda  wrote:

> +1 (binding)
>
> Verified signature, hashes. Built on Mac with JDK 17, created and ran a
> simple flow.
>
> On Thu, Jul 27, 2023 at 1:49 AM Joe Witt  wrote:
>
> > +1 (binding)
> >
> > sigs/hashes
> > Full clean build with basic flow up and running
> > JDK 17
> >
> > On Wed, Jul 26, 2023 at 5:37 PM Emilio Setiadarma <
> > emiliosetiada...@gmail.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Verified signature and SHA256/512 hashes of the release.
> > > OS: MacOS Monterrey 12.6.5
> > > Java version: OpenJDK version 17.0.7
> > > Ran the latest build, booted up NiFi with no issues and started up a
> > simple
> > > NiFi flow
> > >
> > > Thanks David!
> > >
> > > On Wed, Jul 26, 2023 at 2:10 PM Matt Burgess 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Ran through release helper, verified H2 migration on Registry,
> > > > ExtractRecordSchema, various other flows to ensure no regressions.
> > > >
> > > > Thanks for RM'ing David!
> > > >
> > > > On Tue, Jul 25, 2023 at 5:33 PM David Handermann
> > > >  wrote:
> > > > >
> > > > > Team,
> > > > >
> > > > > I am pleased to be calling this vote for the source release of
> Apache
> > > > NiFi
> > > > > 1.23.0.
> > > > >
> > > > > Please review the following guide for how to verify a release
> > candidate
> > > > > build:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > > >
> > > > > The source being voted upon and the convenience binaries are
> > available
> > > on
> > > > > the Apache Distribution Repository:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.0/
> > > > >
> > > > > The build artifacts are available on the Apache Nexus Repository:
> > > > >
> > > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1233
> > > > >
> > > > > Git Tag: nifi-1.23.0-RC3
> > > > > Git Commit ID: 27a690a30a6ae77c217a47ac0601e85970777ca2
> > > > > GitHub Commit Link:
> > > > >
> > > >
> > >
> >
> https://github.com/apache/nifi/commit/27a690a30a6ae77c217a47ac0601e85970777ca2
> > > > >
> > > > > Checksums of nifi-1.23.0-source-release.zip:
> > > > >
> > > > > SHA256:
> > > 39c97d89804b005cc995c56a87a3df6f68c44ee42114dffe756bbac90a3593cf
> > > > > SHA512:
> > > > >
> > > >
> > >
> >
> f256ca731a67435e9883626931abc58f28cda9deb6a7d0a84ed97b78104e43b3b638ee2297d79f92bf5a1e19f62cc78e0a886fa0094593ab34b21d658c59eadd
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > >
> > > > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > > > >
> > > > > KEYS file available here:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > > 132 issues were closed/resolved for this release:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353320
> > > > >
> > > > > Release note highlights can be found here:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.
> > > Then
> > > > > please vote:
> > > > >
> > > > > [ ] +1 Release this package as nifi-1.23.0
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because...
> > > >
> > >
> >
>

[ANNOUNCE] Apache NiFi Flow Design System 0.3.0 release

[Scott Aslan]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi Flow
Design System 0.3.0.

Apache NiFi Flow Design System is an atomic reusable platform for providing
a consistent set of UI/UX components for open source friendly web
applications to consume.

More details on Apache NiFi FLow Design System can be found here:
https://nifi.apache.org/fds.html

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345959

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.0

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi Flow Design System 0.3.0

[Scott Aslan]

Apache NiFi Community,

I am pleased to announce that including my +1 (binding) vote the 0.3.0
release of Apache NiFi Flow Design System passes with
4 +1 (binding) votes
5 +1 (non-binding) votes
0 0 votes
0 -1 votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
https://lists.apache.org/thread/r8vd4mln6nmcb3pxw6kpwkc3zco19mw6

Apache NiFi 0.3.0 RC2 Release Helper Guide

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.3.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip

wget https://dist.apache.org/repos/dist/dev/

nifi/

nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc


wget https://dist.apache.org/repos/dist/dev/

nifi/

nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1


wget https://dist.apache.org/repos/dist/dev/

nifi/

nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256


wget https://dist.apache.org/repos/dist/dev/

nifi/

nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512



# Verify the signature

gpg --verify nifi-fds-0.3.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was
provided in the vote email thread

sha1sum nifi-fds-0.3.0-source-release.zip

sha256sum nifi-fds-0.3.0-source-release.zip

sha512sum nifi-fds-0.3.0-source-release.zip


# Unzip nifi-fds-0.3.0-source-release.zip


# Verify the build works and tests pass (npm version >= 8.1.2)

cd nifi-fds-0.3.0

npm run ci

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Run the demo-app and verify UI/UX components work as expected

cd target/frontend-working-directory/

npm run watch


NOTE: There will be some warnings displayed in the terminal in the browser.
These are the webpack dev server telling us that some of our dependencies
are not providing licenses. This is expected. Simply close the warning
overlay and you should be able to verify the UX/UI components included in
the demo application.


# Make sure the README, NOTICE, and LICENSE are present and correct


# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.


Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

[Scott Aslan]

Hello,

I am pleased to be calling this vote for the source release of Apache NiFi
Flow Design System nifi-fds-0.3.0.

The source zip, including signatures, etc. can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0

The Git tag is nifi-0.3.0-RC2
The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807

Checksums of nifi-fds-0.3.0-source-release.zip:
SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
SHA512:
74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9

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

17 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345959

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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.  Then
please vote:

[ ] +1 Release this package as nifi-fds-0.3.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0

[Scott Aslan]

Cancel this RC due to LICENSE, NOTICE, and README need some changes.

On Tue, Jan 25, 2022 at 12:06 PM Joe Witt  wrote:

> We also need to update the NOTICE file
>
> Apache NiFi Flow Design System
> Copyright 2014-2018 The Apache Software Foundation
>
> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
>
> On Tue, Jan 25, 2022 at 10:02 AM Joe Witt  wrote:
> >
> > -1 (binding)
> >
> > This vote thread appears to be the helper thread.  We need to be using
> > the vote template found in step 5
> > https://nifi.apache.org/fds-release-guide.html
> >
> > Need to ensure the JIRA with a set of changes is linked, the commit
> > IDs are there.  Let's fix the links that Rob found.  And let's make
> > sure the package/package-lock.json and any other appropriate files
> > reference 0.3.0 and not 0.3.0-SNAPSHOT.  We don't want to reference
> > any snapshots in source releases of course.
> >
> > Thanks
> > Joe
> >
> > On Tue, Jan 25, 2022 at 6:21 AM Robert Fellows 
> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > With the corrected download links I was able to download, verify
> signatures
> > > and hashes, build, and exercise FDS components.
> > >
> > > * Built with node 16.13.2 / npm 8.1.2
> > >
> > > Thanks for RM'ing Scott!
> > >
> > > On Mon, Jan 24, 2022 at 7:23 PM Scott Aslan 
> wrote:
> > >
> > > > Hello Apache NiFi community,
> > > >
> > > >
> > > > Please find the associated guidance to help those interested in
> > > > validating/verifying the release so they can vote.
> > > >
> > > >
> > > > # Download latest KEYS file:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> > > >
> > > >
> > > > # Import keys file:
> > > >
> > > > gpg --import KEYS
> > > >
> > > >
> > > > # Pull down nifi-fds-0.3.0 source release artifacts for review:
> > > >
> > > > wget
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
> > > >
> > > > wget
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc
> > > >
> > > > wget
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1
> > > >
> > > > wget
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256
> > > >
> > > > wget
> > > >
> > > >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512
> > > >
> > > >
> > > > # Verify the signature
> > > >
> > > > gpg --verify nifi-fds-0.3.0-source-release.zip.asc
> > > >
> > > >
> > > > # Verify the hashes (sha1, sha256, sha512) match the source and what
> was
> > > > provided in the vote email thread
> > > >
> > > > sha1sum nifi-fds-0.3.0-source-release.zip
> > > >
> > > > sha256sum nifi-fds-0.3.0-source-release.zip
> > > >
> > > > sha512sum nifi-fds-0.3.0-source-release.zip
> > > >
> > > >
> > > > # Unzip nifi-fds-0.3.0-source-release.zip
> > > >
> > > >
> > > > # Verify the build works and tests pass (npm version >= 8.1.2)
> > > >
> > > > cd nifi-fds-0.3.0
> > > >
> > > > npm run ci
> > > >
> > > > npm run clean:install
> > > >
> > > >
> > > > # Verify the contents contain a good README, NOTICE, and LICENSE.
> > > >
> > > >
> > > > # Verify the git commit ID is correct
> > > >
> > > >
> > > > # Verify the RC was branched off the correct git commit ID
> > > >
> > > >
> > > > # Run the demo-app and verify UI/UX components work as expected
> > > >
> > > > npm run watch
> > > >
> > > >
> > > > NOTE: There will be some warnings displayed in the terminal in the
> browser.
> > > > These are the webpack dev server telling us that some of our
> dependencies
> > > > are not providing licenses. This is expected. Simply close the
> warning
> > > > overlay and you should be able to verify the UX/UI components
> included in
> > > > the demo application.
> > > >
> > > >
> > > > # Make sure the README, NOTICE, and LICENSE are present and correct
> > > >
> > > >
> > > > # Send a response to the vote thread indicating a +1, 0, -1 based on
> your
> > > > findings.
> > > >
> > > >
> > > > Thank you for your time and effort to validate the release!
> > > >
> > >
> > >
> > > --
> > > ---
> > > Rob Fellows
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0

[Scott Aslan]

Thanks Rob! Copy/Paste error. I’ll be sure to update the RC template at
https://nifi.apache.org/fds-release-guide.html.

On Tue, Jan 25, 2022 at 8:08 AM Robert Fellows 
wrote:

> The links for the downloads are incorrect. It should read:
>
> # Pull down nifi-fds-0.3.0 source release artifacts for review:
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512
>
>
> On Mon, Jan 24, 2022 at 7:23 PM Scott Aslan  wrote:
>
> > Hello Apache NiFi community,
> >
> >
> > Please find the associated guidance to help those interested in
> > validating/verifying the release so they can vote.
> >
> >
> > # Download latest KEYS file:
> >
> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> >
> >
> > # Import keys file:
> >
> > gpg --import KEYS
> >
> >
> > # Pull down nifi-fds-0.3.0 source release artifacts for review:
> >
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
> >
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc
> >
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1
> >
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256
> >
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512
> >
> >
> > # Verify the signature
> >
> > gpg --verify nifi-fds-0.3.0-source-release.zip.asc
> >
> >
> > # Verify the hashes (sha1, sha256, sha512) match the source and what was
> > provided in the vote email thread
> >
> > sha1sum nifi-fds-0.3.0-source-release.zip
> >
> > sha256sum nifi-fds-0.3.0-source-release.zip
> >
> > sha512sum nifi-fds-0.3.0-source-release.zip
> >
> >
> > # Unzip nifi-fds-0.3.0-source-release.zip
> >
> >
> > # Verify the build works and tests pass (npm version >= 8.1.2)
> >
> > cd nifi-fds-0.3.0
> >
> > npm run ci
> >
> > npm run clean:install
> >
> >
> > # Verify the contents contain a good README, NOTICE, and LICENSE.
> >
> >
> > # Verify the git commit ID is correct
> >
> >
> > # Verify the RC was branched off the correct git commit ID
> >
> >
> > # Run the demo-app and verify UI/UX components work as expected
> >
> > npm run watch
> >
> >
> > NOTE: There will be some warnings displayed in the terminal in the
> browser.
> > These are the webpack dev server telling us that some of our dependencies
> > are not providing licenses. This is expected. Simply close the warning
> > overlay and you should be able to verify the UX/UI components included in
> > the demo application.
> >
> >
> > # Make sure the README, NOTICE, and LICENSE are present and correct
> >
> >
> > # Send a response to the vote thread indicating a +1, 0, -1 based on your
> > findings.
> >
> >
> > Thank you for your time and effort to validate the release!
> >
>
>
> --
> ---
> Rob Fellows
>

[VOTE] Release Apache NiFi Flow Design System 0.3.0

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.3.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.3.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was
provided in the vote email thread

sha1sum nifi-fds-0.3.0-source-release.zip

sha256sum nifi-fds-0.3.0-source-release.zip

sha512sum nifi-fds-0.3.0-source-release.zip


# Unzip nifi-fds-0.3.0-source-release.zip


# Verify the build works and tests pass (npm version >= 8.1.2)

cd nifi-fds-0.3.0

npm run ci

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Run the demo-app and verify UI/UX components work as expected

npm run watch


NOTE: There will be some warnings displayed in the terminal in the browser.
These are the webpack dev server telling us that some of our dependencies
are not providing licenses. This is expected. Simply close the warning
overlay and you should be able to verify the UX/UI components included in
the demo application.


# Make sure the README, NOTICE, and LICENSE are present and correct


# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.


Thank you for your time and effort to validate the release!

[DISCUSS] release nifi-fds 0.3.0

[Scott Aslan]

All,

I would like to kick out a release of nifi-fds. There are multiple npm
audit issues and the version of Angular is old. Puls, the nifi-fds v0.2.0
requires node v8.10.0 and npm v5.6.0 which are very old and already past
their respective end of life. These older versions of node and npm are also
blocking [1].

I can take care of putting together the release.

Thanks,

Scott

[1] https://issues.apache.org/jira/browse/NIFI-9554

Re: [VOTE] Release Apache NiFi 1.12.0

[Scott Aslan]

+1 (binding).

Ran through release helper.
Verified signatures, checksums, etc.
Full build.
Verified basic application functionality.
Verified slickgrid upgrades.

Thanks for RMing Joe!

On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid  wrote:

>   +1 (non-binding)
> Ran through the release helper. Deployed a 10 node cluster on Azure and
> verified the functionality of new ADLS processors with a standard flow.
> Looks good to me.
>
> Thanks,
> Muazma
>
> On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim 
> wrote:
>
> > +1 (binding)
> >
> > -Ran full clean install on OS X (Catalina 10.15.2)
> > -Tested secure NiFi with secure NiFi Registry 0.7.0
> > -Ran basic flows successfully; tested basic versioned flow functionality
> > -Reviewed documentation updates. Lots of a great additions in this
> release!
> > -Reviewed core UI fixes and improvements. Verified that controller
> > services are searchable [1], but filed a Jira for the navigation to the
> > controller service being broken [2].
> >
> > Drew
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-5925 <
> > https://issues.apache.org/jira/browse/NIFI-5925>
> > [2] https://issues.apache.org/jira/browse/NIFI-7742 <
> > https://issues.apache.org/jira/browse/NIFI-7742>
> >
> > > On Aug 13, 2020, at 4:31 PM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.12.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1165
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.0/
> > >
> > > A helpful reminder on how the release candidate verification process
> > works:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >
> > > The Git tag is nifi-1.12.0-RC1
> > > The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> > >
> > > Checksums of nifi-1.12.0-source-release.zip:
> > > SHA256:
> a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> > > SHA512:
> > >
> >
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> > >
> > > 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
> > >
> > > 335 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346778
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.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. Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.12.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
> >
>

Re: [VOTE] Release Apache NiFi 1.10.0 (rc3)

[Scott Aslan]

+1 (binding)

Verified signatures, hashes, build, etc. Tested various parameter use cases.

Thanks for RMing Joe!

On Fri, Nov 1, 2019 at 10:40 AM Matt Burgess  wrote:

> +1 (binding)
>
> Ran thru the release helper and tried a number of flows with various
> controller services and processors, LGTM
>
> Thanks for RM'ing Joe!
>
> On Tue, Oct 29, 2019 at 1:32 PM Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > nifi-1.10.0.
> >
> > As they say 'third time's a charm'.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1151
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.10.0/
> >
> > The Git tag is nifi-1.10.0-RC3
> > The Git commit ID is b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> >
> > Checksums of nifi-1.10.0-source-release.zip:
> > SHA256: e9b0a14b3029acd69c6693781b6b6487c14dda12676db8b4a015bce23b1029c1
> > SHA512:
> >
> b07258cbc21d2e529a1aa3098449917e2d059e6b45ffcfcb6df094931cf16caa8970576555164d3f2290cfe064b5780ba1a8bf63dad04d20100ed559a1cfe133
> >
> > 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
> >
> > 384 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12344993
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.10.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. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.10.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

Re: [ANNOUNCE] New Apache NiFi Committer Rob Fellows

[Scott Aslan]

Very much deserved! Congratulations Rob and thanks for all your
contributions!

On Wed, Sep 25, 2019 at 4:37 AM Alessandro D'Armiento <
alessandro.darmiento1...@gmail.com> wrote:

> Congratulations!
>
> Il giorno mer 25 set 2019 alle ore 09:44 Pierre Villard <
> pierre.villard...@gmail.com> ha scritto:
>
> > Congrats Rob!
> >
> > Le mer. 25 sept. 2019 à 04:13, Sivaprasanna 
> a
> > écrit :
> >
> > > Congratulations, Rob.
> > >
> > > On Wed, 25 Sep 2019 at 5:39 AM, Joe Witt  wrote:
> > >
> > > > Congrats and Thank You!
> > > >
> > > > On Tue, Sep 24, 2019 at 7:58 PM Andy LoPresto 
> > > > wrote:
> > > >
> > > > > Congratulations Rob. Well-earned and welcome to the extra work of
> > > > > committing PRs.
> > > > >
> > > > > Andy LoPresto
> > > > > alopre...@apache.org
> > > > > alopresto.apa...@gmail.com
> > > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > > >
> > > > > > On Sep 24, 2019, at 4: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
> > > > >
> > > > >
> > > >
> > >
> >
>

[ANNOUNCE] Apache NiFi Flow Design System 0.2.0 release

[Scott Aslan]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi Flow
Design System 0.2.0.

Apache NiFi Flow Design System is an atomic reusable platform for providing
a consistent set of UI/UX components for open source friendly web
applications to consume.

More details on Apache NiFi FDS can be found here:
https://nifi.apache.org/fds.html

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453&projectId=12316020

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi Flow Design System 0.2.0

[Scott Aslan]

Apache NiFi Community,

I am pleased to announce that including my +1 (binding) vote the 0.2.0
release of Apache NiFi Flow Design System passes with
4 +1 (binding) votes
4 +1 (non-binding) votes
0 0 votes
0 -1 votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
http://apache-nifi-developer-list.39713.n7.nabble.com/VOTE-Release-Apache-NiFi-Flow-Design-System-0-2-0-RC2-td20938.html

Apache NiFi Flow Design System 0.2.0 RC2 Release Helper Guide

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in

validating/verifying the Apache NiFi Flow Design System release so they can

vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.2.0 source release artifacts for review:


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.2.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was

provided in the vote email thread

sha1sum nifi-fds-0.2.0-source-release.zip

sha256sum nifi-fds-0.2.0-source-release.zip

sha512sum nifi-fds-0.2.0-source-release.zip


# Unzip nifi-fds-0.2.0-source-release.zip


# Verify the build works (npm version >= 5.6.0)
cd nifi-fds-0.2.0
npm run clean:install

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Run the demo-app and make sure it works as expected
cd target/frontend-working-directory
npm start

# Make sure the README, NOTICE, and LICENSE are present and correct
cd node_modules/@nifi-fds/core

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!

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

[Scott Aslan]

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&projectId=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

[ ] -1 Do not release this package because...

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

[Scott Aslan]

Cancel this RC due to LICENSE, NOTICE, and README need some changes.

On Tue, Jul 23, 2019 at 12:53 PM Joe Witt  wrote:

> -1 (binding)
>
> The LICENSE and NOTICE need some changes.  They're arguably minor but lets
> take this opportunity to fix it.  For dependencies which are ALv2 you do
> not need to copy/paste their LICENSE text in and in fact ALv2 dependencies
> should not even be referenced in the LICENSE.  They may require referencing
> in the NOTICE file if they have copyright/NOTICE considerations to carry
> forward.  I can work with you on that Scott.  See
> http://nifi.apache.org/licensing-guide.html
>
> Otherwise, things look good.  Am able to build locally and review the demo
> application.  I didn't yet verify sigs/hashes.
>
> Thanks
> Joe
>
> On Tue, Jul 23, 2019 at 12:25 PM Robert Fellows 
> wrote:
>
> > * Verified the signature
> > * Verified the hashes
> > * Build was successful
> > * Demo app works as expected
> >
> > I also npm link'd the new @nifi-fds/core in NiFi-Registry to verify it
> will
> > work.
> > However, it wasn't clear in the README that it requires upgrading
> > dependencies in the consuming app (angular, rxjs, angular-material, ...).
> > Once those changes were made, it worked. I think it worth documenting
> that
> > in the README and/or the Wiki. I created a JIRA for it
> > https://issues.apache.org/jira/browse/NIFI-6474.
> >
> > With that caveat:
> > +1 (non-binding) Release this package as nifi-fds-0.2.0
> >
> > -- Rob
> >
> >
> > On Mon, Jul 22, 2019 at 7:19 PM Scott Aslan 
> 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-RC1
> > >
> > > The Git commit ID is cee69170d68db602b8acac0959ee9e91c1000599
> > >
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=cee69170d68db602b8acac0959ee9e91c1000599
> > >
> > >
> > > Checksums of nifi-fds-0.2.0-source-release.zip:
> > >
> > > SHA1: 14e8f3e908ec0ddd3556ee52524c2a5a099b4370
> > >
> > > SHA256:
> ae92eebf2d0b818b44203c896cde95e8c0dbf9007f9d3909e0253b156cf4b102
> > >
> > > SHA512:
> > >
> > >
> >
> 86940d676ff63b7f23762dc4c3fc48ed19e1e67e97f4606cebce31b7f6b0976c60da487f6d23ce9476a293fb8fb790bfbaa3a8f1cfee5c8797658ac00718c3d9
> > >
> > >
> > > 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&projectId=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
> > >
> > > [ ] -1 Do not release this package because...
> > >
> >
> >
> > --
> > ---
> > Rob Fellows
> >
>

[VOTE] Release Apache NiFi Flow Design System 0.2.0

[Scott Aslan]

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-RC1

The Git commit ID is cee69170d68db602b8acac0959ee9e91c1000599

https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=cee69170d68db602b8acac0959ee9e91c1000599


Checksums of nifi-fds-0.2.0-source-release.zip:

SHA1: 14e8f3e908ec0ddd3556ee52524c2a5a099b4370

SHA256: ae92eebf2d0b818b44203c896cde95e8c0dbf9007f9d3909e0253b156cf4b102

SHA512:
86940d676ff63b7f23762dc4c3fc48ed19e1e67e97f4606cebce31b7f6b0976c60da487f6d23ce9476a293fb8fb790bfbaa3a8f1cfee5c8797658ac00718c3d9


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&projectId=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

[ ] -1 Do not release this package because...

Apache NiFi Flow Design System 0.2.0 RC1 Release Helper Guide

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in

validating/verifying the Apache NiFi Flow Design System release so they can

vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.2.0 source release artifacts for review:


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.2.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was

provided in the vote email thread

sha1sum nifi-fds-0.2.0-source-release.zip

sha256sum nifi-fds-0.2.0-source-release.zip

sha512sum nifi-fds-0.2.0-source-release.zip


# Unzip nifi-fds-0.2.0-source-release.zip


# Verify the build works

cd nifi-fds-0.2.0

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Look at the resulting convenience binary as found in

cd target/frontend-working-directory


# Make sure the README, NOTICE, and LICENSE are present and correct


# Run the resulting convenience binary and make sure it works as expected

npm start


# Send a response to the vote thread indicating a +1, 0, -1 based on

your findings.


Thank you for your time and effort to validate the release!

[DISCUSS] Apache NiFi FDS 0.2.0

[Scott Aslan]

Hello everyone,

I wanted to discuss releasing Apache NiFi FDS 0.2. in the coming
week or two. We have some updates to the specification as well as some very
useful updates to our build process. We also have upgraded to the latest
versions of Angular, jQuery, Covalent, and rxjs.

If everyone is amenable to a release, I will RM unless anyone else would
like
to take those duties.

Best Regards,
Scott Aslan

Re: Design track at ApacheCon Europe.

[Scott Aslan]

Hi Victoria,

Thank you for the kind words and thanks for reaching out. Let me check my
schedule and get back to you. If I can make it work I would be happy to
give a talk at ApacheCon Europe on the Apache NiFi Flow Design System and
how the community implemented a reuse-able set of UX components to be
leveraged across the Apache NiFi ecosystem.

-Scott Aslan

On Fri, May 24, 2019 at 6:53 AM Victoria Bondarchuk <
m...@victoriabondarchuk.com> wrote:

> Hi, my name is Victoria Bondarchuk and I'm a member of the Open Source
> Design community (https://opensourcedesign.net) and one of the
> co-organizers of the Design track at ApacheCon Europe.
>
>
> Apache NiFi community did an impressive job putting together a whole design
> system https://nifi.apache.org/fds.html so I was wondering in anyone would
> be interested in coming over and presenting about that work in Berlin in
> October?
>
>
> The CfP is open until May 26 but if interested, please do hesitate to
> submit just a title to reserve the spot.
>
>
> That would be a great opportunity to promote a design approach in open
> source for the broader Apache community.
>
>
> Please feel free to ask me in case of any further questions,
>
>
> Happy Friday,
>
> Victoria
>

Re: [VOTE] Release Apache NiFi Registry 0.4.0

[Scott Aslan]

+1 (binding) Release this package as nifi-registry-0.4.0

Ran through helper guide. Created 10 flows in 20 buckets via:

org/apache/nifi/registry/web/TestRestAPI.java

Added a bundle to a bucket via curl:

curl -v -F
file=@/path/to/your/nifi-registry/nifi-registry-core/nifi-registry-bundle-utils/src/test/resources/nars/nifi-foo-nar.nar
http://localhost:18080/nifi-registry-api/buckets//bundles/nifi-nar


Verified new bundle showed up in appropriate bucket. Verified UX
functionality. Everything looks good. Thanks for RMing Bryan!

On Thu, May 16, 2019 at 5:36 PM Bryan Bende  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry nifi-registry-0.4.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1145
>
> The Git tag is nifi-registry-0.4.0-RC1
> The Git commit ID is 4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> Checksums of nifi-registry-0.4.0-source-release.zip:
> SHA256: a8753372fbc24f7d293df6205c465edee7a4167d835811e84e27df3e609d2be1
> SHA512:
> 70ade1ba2dcf5363b6568669080a3607e5dfd3dffd28651ba5f6961db835e0f61ff7f9758757358800774e4e1063cdcfdd5d44a712a845e34052544cfce9b047
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 37 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12344183
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.4.0
>
> The vote will be open for 96 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-registry-0.4.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache NiFi Registry 0.3.0

[Scott Aslan]

+1 (binding)

Ran through release helper.

Thanks for RM'ing Kevin!

On Sat, Sep 22, 2018 at 9:54 AM Kevin Doran  wrote:

> Hello,
>
> I am pleased to call this vote for the source release of Apache NiFi
> Registry 0.3.0.
>
> The source zip, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.3.0/
>
> The Git tag is nifi-registry-0.3.0-RC1
> The Git commit ID is 2fef9fac2b627ee1f3428b07019b333c68f65f2d
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=2fef9fac2b627ee1f3428b07019b333c68f65f2d
>
> Checksums of nifi-registry-0.3.0-source-release.zip:
> SHA1:   4340068ef7e3ba099f614b86be4d2d77016845d9
> SHA256: c0a51f6b5855202993daa808015ddf26466843f3bc5727333f44661099c2ad5b
> SHA512:
> efc9882511eaccca4cc83117f5a870859f80b3667d8d3d9bf6e1fec9a1e4d1f37abee4476aaa28245468eca0eec30a3e84eba8e547a0fc1a97fdf6c289ab8b96
>
> Release artifacts are signed with the following key:
> Fingerprint = C09B A891 AED4 5B8C 2C23  1AFE 1FB6 6A91 F71B 6207
> Available at:
> https://people.apache.org/keys/committer/kdoran.asc
> https://pgp.mit.edu/pks/lookup?op=get&search=0x1FB66A91F71B6207
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> 15 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343483&styleName=Html&projectId=12320920
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
>
> 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. Then please vote:
>
> [ ] +1 Release this package as nifi-registry-${VERSION}
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: failed to build nifi 1.8.0-SNAPSHOT on OSX high sierra

[Scott Aslan]

Hi Charlie,

Sorry to hear you are having issues building NiFi. The
frontend-maven-plugin has been designed to use a local installation of
node. Using a globally installed version has been requested before
 but the
developer's position is that node does not take up much space and will only
download if missing. Installing node locally allows developers that have
not installed node globally or are using different versions to build the
project without having to do anything more complicated than mvn clean
install.

I assume you used brew to install node?

I am wondering if there is a permission issue and if you uninstall node
from your machine are you able to successfully build? Try brew uninstall
--force node and then try mvn clean install.

-Scott

On Thu, Aug 16, 2018 at 10:27 AM Charlie Meyer <
charlie.me...@civitaslearning.com> wrote:

> Hello,
>
> I'm attempting to build 1.8.0-snap on osx high sierra and am running into
> the following nodejs error:
>
> [INFO] Running 'npm --cache-min Infinity install' in
>
> /Users/cmeyer/opt/nifi/nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory
> [ERROR] module.js:549
> [ERROR] throw err;
> [ERROR] ^
> [ERROR]
> [ERROR] Error: Cannot find module '../lib/utils/unsupported.js'
> [ERROR] at Function.Module._resolveFilename (module.js:547:15)
> [ERROR] at Function.Module._load (module.js:474:25)
> [ERROR] at Module.require (module.js:596:17)
> [ERROR] at require (internal/module.js:11:18)
> [ERROR] at
>
> /Users/cmeyer/opt/nifi/nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory/node/node_modules/npm/bin/npm-cli.js:19:21
> [ERROR] at Object.
>
> (/Users/cmeyer/opt/nifi/nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory/node/node_modules/npm/bin/npm-cli.js:92:3)
> [ERROR] at Module._compile (module.js:652:30)
> [ERROR] at Object.Module._extensions..js (module.js:663:10)
> [ERROR] at Module.load (module.js:565:32)
> [ERROR] at tryModuleLoad (module.js:505:12)
> ...
> ...
> ...
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.4:npm (npm install) on project
> nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min Infinity
> install' failed. org.apache.commons.exec.ExecuteException: Process exited
> with an error: 1 (Exit value: 1) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :nifi-jolt-transform-json-ui
>
> I tried solutions suggested online such as reinstalling node, etc but have
> still not had luck. I've been able to replicate the error on 2 different
> machines, but only on osx (was able to build fine on ubuntu). Is this a
> known issue and is there a workaround?
>
> thanks!
>

Re: [ANNOUNCE] New NiFi PMC member Jeremy Dyer

[Scott Aslan]

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

[Scott Aslan]

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 1.7.0

[Scott Aslan]

+1 binding

Went through the release helper guide
Tested unsecured standalone NiFi + unsecured NiFi Registry (0.2.0)

Thanks for RM'ing A-Lo!

On Fri, Jun 22, 2018 at 2:17 PM Andrew Lim 
wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (10.11.6)
> -Tested integration with NiFi Registry (0.2.0)
> -Reviewed resolved “Core UI” component Jiras and spot checked inclusion in
> build
> -Reviewed documentation.  Found one minor issue with an image in the User
> Guide [1]
>
> Drew
>
> [1] https://issues.apache.org/jira/browse/NIFI-5330
>
>
> > On Jun 20, 2018, at 3:16 AM, Andy LoPresto  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-1.7.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1127
> >
> > and
> >
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.7.0
> >
> > The Git tag is nifi-1.7.0-RC1
> > The Git commit ID is 99bcd1f88dc826f857ae4ab33e842110bfc6ce21
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=99bcd1f88dc826f857ae4ab33e842110bfc6ce21
> >
> > Checksums of nifi-1.7.0-source-release.zip:
> > SHA1: 11086ef532bb51462d7e1ac818f6308d4ac62f03
> > SHA256: b616f985d486af3d05c04e375f952a4a5678f486017a2211657d5ba03aaaf563
> > SHA512:
> d81e9c6eb7fc51905d6f6629b25151fc3d8af7a3cd7cbc3aa03be390c0561858d614b62d8379a90fdb736fcf5c1b4832f4e050fdcfcd786e9615a0b5cc1d563d
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/alopresto.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 194 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342979&projectId=12316020
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.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. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.7.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because…
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
>
>

Re: [VOTE] Release Apache NiFi Registry 0.2.0

[Scott Aslan]

+1 binding,

-ran through release helper
-setup unsecured nifi, configured registry 0.2.0, created a bucket, placed
PG's under version control, all looks good

Thanks for RM'ing Kevin!

On Mon, Jun 18, 2018 at 7:10 AM Marc  wrote:

> +1 binding..
>
>   Stepped through helper guide for verification and validation. Looks
> great!
>
> On Mon, Jun 18, 2018, 4:18 AM Pierre Villard 
> wrote:
>
> > +1 binding,
> >
> > - Went through the release helper guide
> > - Tested the hook mechanism
> >
> > All looks good to me. Thanks for the release management Kevin and to all
> > the contributors!
> >
> > Pierre
> >
> > 2018-06-18 8:05 GMT+02:00 Koji Kawamura :
> >
> > > +1 (binding)
> > >
> > > - Run through Release Helper Guide
> > > - Tested other database other than H2
> > > - Tested Git persistence provider
> > >
> > > Few minor feedback:
> > >
> > > 1. Database user whose password is blank can not be used
> > >
> > > When I used HSQLDB, the default 'sa' user does not have password. If I
> > > configure a blank password property, I got following error.
> > > Work-around: create a user with password
> > > Caused by: java.lang.IllegalStateException: nifi.registry.db.password
> > > is required
> > > at
> > org.apache.nifi.registry.db.DataSourceFactory.createDataSource(
> > > DataSourceFactory.java:78)
> > > ~[na:na]
> > >
> > > 2. V2__Initial.sql uses 'TEXT' data type, which is not supported in
> some
> > > DBMS
> > >
> > > While many databases such as MySQL, PostgreSQL, SQL Server and Oracle
> > > ... etc support TEXT, it is not a standard data type and some other
> > > database engines do not support it (e.g. HSQLDB).
> > > Also, Microsoft docs mention that SQL Server may remove TEXT data type
> > > in the future release.
> > > https://docs.microsoft.com/en-us/sql/t-sql/data-types/ntext-
> > > text-and-image-transact-sql?view=sql-server-2017
> > >
> > > V1__Initial.sql uses 'VARCHAR(4096)' instead. That can support more
> > > databases.
> > > After changing V2__Initial.sql to use VARCHAR, I was able to use
> HSQLDB.
> > >
> > >
> > > Thanks,
> > > Koji
> > >
> > > On Sun, Jun 17, 2018 at 9:13 PM, Jeff Zemerick 
> > > wrote:
> > > > +1 non-binding
> > > >
> > > > Ran through the release helper guide with no issues. Good stuff!
> > > >
> > > > On Sat, Jun 16, 2018 at 5:47 PM Andy LoPresto <
> > > alopresto.apa...@gmail.com>
> > > > wrote:
> > > >
> > > >> Sorry everyone,
> > > >>
> > > >> Committers can provide binding votes on technical discussions (such
> as
> > > to
> > > >> call for a release), but only PMC members can provide binding votes
> on
> > > >> releases. This is an Apache policy.
> > > >>
> > > >> I’ll update the page on Monday to be a bit clearer on the
> distinction.
> > > >>
> > > >> Andy LoPresto
> > > >> alopre...@apache.org
> > > >> alopresto.apa...@gmail.com
> > > >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > >>
> > > >> > On Jun 16, 2018, at 14:34, Andy LoPresto <
> > alopresto.apa...@gmail.com>
> > > >> wrote:
> > > >> >
> > > >> > Abdelkrim,
> > > >> >
> > > >> > Thanks for validating the release and voting. Just to clarify,
> only
> > > PMC
> > > >> members and committers [1] can cast a “binding” vote. All other
> > > community
> > > >> members are welcome to cast a +1, 0, or -1 vote as well, but these
> are
> > > >> “non-binding”. Thanks again.
> > > >> >
> > > >> > [1] http://nifi.apache.org/people.html
> > > >> >
> > > >> > Andy LoPresto
> > > >> > alopre...@apache.org
> > > >> > alopresto.apa...@gmail.com
> > > >> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D
> EF69
> > > >> >
> > > >> >> On Jun 16, 2018, at 14:23, Abdelkrim Hadjidj <
> > > ahadj...@hortonworks.com>
> > > >> wrote:
> > > >> >>
> > > >> >> +1 (binding)
> > > >> >>
> > > >> >> - Tested everything from the release helper and everything worked
> > > fine
> > > >> >> - Tested the GitFlowPersistenceProvider with Github, works fine
> > > >> >> - The Switching from other Persistence Provider section of the
> > Admin
> > > >> Guide asks to move the H2 DB specified as
> nifi.registry.db.directory.
> > In
> > > >> the Registery 0.2, this property is set to "". So it doesn't apply
> > when
> > > you
> > > >> start a Registry 0.2 with FilePersistenceProvider and migrate to Git
> > > >> provider.
> > > >> >> - This is not an issue, but it seems that there no way to migrate
> > > >> previous flow file from File provider to Git provider, or from an
> > > existing
> > > >> Git provider with Git clone.
> > > >> >>
> > > >> >> Thanks
> > > >> >>
> > > >> >> On 6/16/18, 3:22 PM, "Bryan Bende"  wrote:
> > > >> >>
> > > >> >>+1 (binding) Release this package as nifi-registry-0.2.0
> > > >> >>
> > > >> >>- Ran through everything in the release helper and looked
> good,
> > > few
> > > >> minor
> > > >> >>things Andy mentioned
> > > >> >>- Tested upgrading an existing registry to 0.2.0 to test
> > database
> > > >> migration
> > > >> >>- Tested basic event hook logging

[ANNOUNCE] Apache NiFi Flow Design System 0.1.0 release

[Scott Aslan]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi
Flow Design System 0.1.0.

Apache NiFi Flow Design System is an atomic reusable platform for
providing a consistent set of UI/UX components for open source
friendly web applications to consume.

More details on Apache NiFi can be found here:
https://nifi.apache.org/fds.html

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12343357

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.0

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi Flow Design System 0.1.0

[Scott Aslan]

Apache NiFi Community,

I am pleased to announce that the 0.1.0 release of Apache NiFi Flow
Design System passes with
4 +1 (binding) votes
2 +1 (non-binding) votes
0 0 votes
0 -1 votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
http://apache-nifi-developer-list.39713.n7.nabble.com/VOTE-Release-Apache-NiFi-Flow-Design-System-0-1-0-RC3-td19004.html

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

[Scott Aslan]

Aldrin,

Yes we do need INFRA to help us delete the rel/nifi-registry-0.1.0. The
node_modules for the gh-pages branch, however, have been purposely
committed to support the github.io demo <https://apache.github.io/nifi-fds/>
.

On Tue, Jun 12, 2018 at 10:30 AM Kevin Doran  wrote:

> +1 (non-binding)
>
> Completed all the steps of the helper guide and played with the demo app.
> Verified the LN and Readme. Also verified version strings in the latest RC
> 3.
>
> Nice work on this everyone and thanks for RM'ing this initial release,
> Scott!
>
> Thanks,
> Kevin
>
> On 6/12/18, 10:12, "Matt Gilman"  wrote:
>
> +1 binding
>
> Ran through helper guide. Verified signatures, hashes, build, etc.
> Version
> strings look better with this RC. Provided other feedback regarding
> improvements to the demo app during RC1.
>
> Thanks for RMing this Scott!
>
> Matt
>
> On Tue, Jun 12, 2018 at 8:28 AM, Rob Moran  wrote:
>
> > +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 <
> > pierre.villard...@gmail.com>
> > 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
> > > > <https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=
> > > > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184>*
> > > >
> > > >
> > > > Checksums of nifi-fds-0.1.0-source-release.zip:
> > > >
> > > > SHA1:
> > > >
> > > > ce971d78cc0660299dcee2233bc22fa78e2940af
> > > >
> > > > SHA256:
> > > >
> > > > 7cb36f412b4147c0e071508f4f6d2ca76b2fe524382937d6552dbe7efe10a827
> 

[VOTE] Release Apache NiFi Flow Design System 0.1.0 RC3

[Scott Aslan]

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
*


Checksums of nifi-fds-0.1.0-source-release.zip:

SHA1:

ce971d78cc0660299dcee2233bc22fa78e2940af

SHA256:

7cb36f412b4147c0e071508f4f6d2ca76b2fe524382937d6552dbe7efe10a827

SHA512:

11e9cf4a529862da528bd616124e57f567503c25820e4b70e72d3d53f16bfed7c0c97f05f7c390267d2163cdae2c6151dc6d9a9bdf6c11be8a6dca4409b3bd15


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?projectId=12316020&version=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...

Apache NiFi Flow Design System 0.1.0 RC2 Release Helper Guide RC3

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in

validating/verifying the Apache NiFi Flow Design System release so they can

vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.1.0 source release artifacts for review:


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.1.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was

provided in the vote email thread

sha1sum nifi-fds-0.1.0-source-release.zip

sha256sum nifi-fds-0.1.0-source-release.zip

sha512sum nifi-fds-0.1.0-source-release.zip


# Unzip nifi-fds-0.1.0-source-release.zip


# Verify the build works (npm version >= 5.6.0)

cd nifi-fds-0.1.0

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Run the demo-app and make sure it works as expected
cd target

npm start


# Make sure the README, NOTICE, and LICENSE are present and correct

cd node_modules/@nifi-fds/core

# Send a response to the vote thread indicating a +1, 0, -1 based on

your findings.


Thank you for your time and effort to validate the release!

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

[Scott Aslan]

Cancel this RC due to another incorrect version string.

On Mon, Jun 11, 2018 at 1:11 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-RC2
>
> The Git commit ID is 633c0eba1d010fec93c29ec17292e52f60bf944d
>
> *https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=633c0eba1d010fec93c29ec17292e52f60bf944d
> <https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=633c0eba1d010fec93c29ec17292e52f60bf944d>*
>
>
> Checksums of nifi-fds-0.1.0-source-release.zip:
>
> SHA1:
>
> 096d4d395c9210caf2dfef5d4050c59600f0f51a
>
> SHA256:
>
> 8e80bb0a5a029c290b2b78b6d4bdafcf613db248fe602c21c35b3e604710cdce
>
> SHA512:
>
>
> 7227fc6ea547463c49a070a79764631cd0e2b84cd50c046706009f5e0a707116d519c572fd49a811d41fd2b37bdd75aa274971a9fd2db9024c225cc7849549d5
>
>
> 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?projectId=12316020&version=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...
>
>

Apache NiFi Flow Design System 0.1.0 RC2 Release Helper Guide

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in

validating/verifying the Apache NiFi Flow Design System release so they can

vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.1.0 source release artifacts for review:


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.1.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was

provided in the vote email thread

sha1sum nifi-fds-0.1.0-source-release.zip

sha256sum nifi-fds-0.1.0-source-release.zip

sha512sum nifi-fds-0.1.0-source-release.zip


# Unzip nifi-fds-0.1.0-source-release.zip


# Verify the build works (npm version >= 5.6.0)

cd nifi-fds-0.1.0

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Run the demo-app and make sure it works as expected
cd target

npm start


# Make sure the README, NOTICE, and LICENSE are present and correct

cd node_modules/@nifi-fds/core

# Send a response to the vote thread indicating a +1, 0, -1 based on

your findings.


Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi Flow Design System 0.1.0

[Scott Aslan]

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-RC2

The Git commit ID is 633c0eba1d010fec93c29ec17292e52f60bf944d

*https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=633c0eba1d010fec93c29ec17292e52f60bf944d
*


Checksums of nifi-fds-0.1.0-source-release.zip:

SHA1:

096d4d395c9210caf2dfef5d4050c59600f0f51a

SHA256:

8e80bb0a5a029c290b2b78b6d4bdafcf613db248fe602c21c35b3e604710cdce

SHA512:

7227fc6ea547463c49a070a79764631cd0e2b84cd50c046706009f5e0a707116d519c572fd49a811d41fd2b37bdd75aa274971a9fd2db9024c225cc7849549d5


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?projectId=12316020&version=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...

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

[Scott Aslan]

Good catch MattG!

The Apache NiFi Flow Design System 0.1.0 RC1 is canceled due to having the
incorrect version number in the package-lock.json. I will address this
issue under https://issues.apache.org/jira/browse/NIFI-5240.

I also filed NIFI-5294 and NIFI-5295 to address the demo-app load time and
display the FDS version number in the demo-app.

-Scott

On Mon, Jun 11, 2018 at 9:45 AM Matt Gilman  wrote:

> -1 binding
>
> Signatures, hashes, etc look right. Build was good and the demo application
> started up just fine. The demo application did load a little slowly so we
> may want to file a JIRA to improve this in the future.
>
> However, it appears that the version bump only happened in the package.json
> and not the package-lock.json. Because of this, the built artifacts that
> ended up in the node_modules had a version of 0.0.0 (not 0.1.0). It may
> make sense to render this version in the demo application to prevent this
> in the future. There's an added benefit that we'd also know what version of
> nifi-fds was being shown.
>
> Matt
>
> On Fri, Jun 8, 2018 at 8:03 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-RC1
> >
> > The Git commit ID is 35423f267de0755087a274ece79c81ef1a4ee641
> >
> > https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=
> > 35423f267de0755087a274ece79c81ef1a4ee641
> >
> >
> > Checksums of nifi-fds-0.1.0-source-release.zip:
> >
> > SHA1: 389b7bda654cfb9a79efa5f893eb37b9f73caaf5
> >
> > SHA256: b42de408e797df859ab8e11e39bd717c996df775179bfae82bf4392bb346a135
> >
> > SHA512:
> > 3b1cca1d5c3cd1786fb54deaa9e9761feb1b8bd2b365658ecef302ba617d
> > d3fe66766513d76ad8686ce7f87a25d6d6152ccdae1bf2dfb3d5dba3e352d53a4122
> >
> >
> > 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?
> > projectId=12316020&version=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...
> >
>

Apache NiFi Flow Design System 0.1.0 RC1 Release Helper Guide

[Scott Aslan]

Hello Apache NiFi community,


Please find the associated guidance to help those interested in

validating/verifying the Apache NiFi Flow Design System release so they can

vote.


# Download latest KEYS file:

https://dist.apache.org/repos/dist/dev/nifi/KEYS


# Import keys file:

gpg --import KEYS


# Pull down nifi-fds-0.1.0 source release artifacts for review:


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha512


# Verify the signature

gpg --verify nifi-fds-0.1.0-source-release.zip.asc


# Verify the hashes (sha1, sha256, sha512) match the source and what was

provided in the vote email thread

sha1sum nifi-fds-0.1.0-source-release.zip

sha256sum nifi-fds-0.1.0-source-release.zip

sha512sum nifi-fds-0.1.0-source-release.zip


# Unzip nifi-fds-0.1.0-source-release.zip


# Verify the build works

cd nifi-fds-0.1.0

npm run clean:install


# Verify the contents contain a good README, NOTICE, and LICENSE.


# Verify the git commit ID is correct


# Verify the RC was branched off the correct git commit ID


# Look at the resulting convenience binary as found in

cd target


# Make sure the README, NOTICE, and LICENSE are present and correct


# Run the resulting convenience binary and make sure it works as expected

npm start


# Send a response to the vote thread indicating a +1, 0, -1 based on

your findings.


Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi Flow Design System 0.1.0

[Scott Aslan]

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-RC1

The Git commit ID is 35423f267de0755087a274ece79c81ef1a4ee641

https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=35423f267de0755087a274ece79c81ef1a4ee641


Checksums of nifi-fds-0.1.0-source-release.zip:

SHA1: 389b7bda654cfb9a79efa5f893eb37b9f73caaf5

SHA256: b42de408e797df859ab8e11e39bd717c996df775179bfae82bf4392bb346a135

SHA512:
3b1cca1d5c3cd1786fb54deaa9e9761feb1b8bd2b365658ecef302ba617dd3fe66766513d76ad8686ce7f87a25d6d6152ccdae1bf2dfb3d5dba3e352d53a4122


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?projectId=12316020&version=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...

Re: [DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

Hey guys,

It looks like all of the outstanding issues have been resolved. I will go
ahead and start the RM process and kick out an RC.

-Scotty



On Fri, Jun 1, 2018 at 9:54 AM, Scott Aslan  wrote:

> Hello,
>
> The github repo [1] is now referenced as "Mirror of
> Apache NiFi Flow Design System".
>
> -Scott
>
> [1] https://github.com/apache/nifi-fds
>
> On Tue, May 29, 2018 at 12:31 PM, Scott Aslan 
> wrote:
>
>> I have submitted this to INFRA: https://issues.apache.o
>> rg/jira/browse/INFRA-16588
>>
>> On Mon, May 28, 2018 at 4:13 AM, Pierre Villard <
>> pierre.villard...@gmail.com> wrote:
>>
>>> Hey guys,
>>>
>>> Just a minor remark: the github repo [1] is still referenced as "Mirror
>>> of
>>> Apache NiFi Fluid Design System".
>>> I think we should file a JIRA to INFRA to get this fixed.
>>>
>>> Pierre
>>>
>>> [1] https://github.com/apache/nifi-fds
>>>
>>>
>>> 2018-05-25 23:36 GMT+02:00 Scott Aslan :
>>>
>>> > Ok guys, I added a page to the nifi-site for the nifi-fds subproject:
>>> > https://nifi.apache.org/fds.html
>>> >
>>> > -Scott
>>> >
>>> > On Fri, May 25, 2018 at 4:01 PM, Scott Aslan 
>>> > wrote:
>>> >
>>> > > Thanks Matt!
>>> > >
>>> > > Andy, yes it looks like we still need to add a page to the nifi-site
>>> for
>>> > > this new sub project. Sorry for the broken link.
>>> > >
>>> > > -Scott
>>> > >
>>> > > On Fri, May 25, 2018 at 2:48 PM, Matt Gilman <
>>> matt.c.gil...@gmail.com>
>>> > > wrote:
>>> > >
>>> > >> Scott,
>>> > >>
>>> > >> Thanks for offering to RM! I'm happy to help review the PR's for the
>>> > >> remaining JIRA's you've identified.
>>> > >>
>>> > >> Matt
>>> > >>
>>> > >> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
>>> > >> aichr...@protonmail.com>
>>> > >> wrote:
>>> > >>
>>> > >> > -BEGIN PGP SIGNED MESSAGE-
>>> > >> > Hash: SHA1
>>> > >> >
>>> > >> > > Team,
>>> > >> > >
>>> > >> > > There has been a lot of great work done on the NiFi Flow Design
>>> > System
>>> > >> > [1]
>>> > >> > > and although there are still a few 'in progress' issues ([3],
>>> [4],
>>> > >> [5])
>>> > >> > I think
>>> > >> > > we are probably very close to an initial release focused on a
>>> > reusable
>>> > >> > > platform providing a consistent set of UI/UX components across
>>> the
>>> > >> NiFi
>>> > >> > > ecosystem.
>>> > >> > >
>>> > >> > > Since NiFi Registry will have a dependency on client code
>>> provided
>>> > by
>>> > >> > the flow
>>> > >> > > design system, the first release of the flow design system would
>>> > need
>>> > >> to
>>> > >> > > occur before the next release of NiFi Registry that integrates
>>> with
>>> > >> it.
>>> > >> > The
>>> > >> > > work on the NiFi Registry side is being done as part of
>>> NIFIREG-39
>>> > >> [2].
>>> > >> > >
>>> > >> > > Let me know if anyone has any thoughts or comments.  I'm happy
>>> to
>>> > act
>>> > >> as
>>> > >> > RM
>>> > >> > > if no one else is interested in doing so, and we can start the
>>> > >> process of
>>> > >> > > going through JIRA to see what is left.
>>> > >> > >
>>> > >> > > Thanks,
>>> > >> > >
>>> > >> > > Scott
>>> > >> > >
>>> > >> > > [1] https://nifi.apache.org/fds.html
>>> > >> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
>>> > >> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
>>> > >> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
>>> > >> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
>>> > >> >
>>> > >> > Glad to see the progress! FYI, the FDS link [1] appears to be
>>> broken
>>> > >> (404
>>> > >> > Not
>>> > >> > Found)
>>> > >> >
>>> > >> > Regards,
>>> > >> >
>>> > >> > Andy I.C.
>>> > >> >
>>> > >> > [1] https://nifi.apache.org/fds.html
>>> > >> > -BEGIN PGP SIGNATURE-
>>> > >> > Version: GnuPG v2.0.22 (GNU/Linux)
>>> > >> >
>>> > >> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
>>> > >> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
>>> > >> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
>>> > >> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
>>> > >> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
>>> > >> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
>>> > >> > =q33Z
>>> > >> > -END PGP SIGNATURE-
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > ​Sent from ProtonMail, Swiss-based encrypted email.​
>>> > >> >
>>> > >> >
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>>
>>
>

Re: [ANNOUNCE] New NiFi PMC member Mike Thomsen

[Scott Aslan]

Congrats

On Wed, Jun 6, 2018, 9:03 PM Matt Burgess  wrote:

> Congratulations Mike! Great to have you aboard, I appreciate your
> commitment and work ethic and looking forward to continued great
> things!
>
> On Wed, Jun 6, 2018 at 6:22 PM, Tony Kurc  wrote:
> >  NiFi community,
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Mike
> > Thomsen has accepted the PMC's invitation to join the Apache NiFi PMC.
> We
> > greatly appreciate all of Mike's hard work and generous contributions to
> > the project. We look forward to continued involvement in the project.
> >
> > Mike was announced as a committer a few months ago, and in that time I'm
> > sure many have noticed Mike's increased involvement in the areas we look
> > for in PMC members - building the community by helping people with
> issues,
> > ensuring the project follows ASF best practices, participation in
> > discussions, and helping others contribute (in addition to contributing
> his
> > own code and documentation). He's been a great advocate of the project
> and
> > of the Apache Way.
> >
> > Congratulations and welcome, Mike!
> >
> > Tony
>

Re: [ANNOUNCE] New Apache NiFi Committer Sivaprasanna Sethuraman

[Scott Aslan]

Congrats!

On Tue, Jun 5, 2018 at 9:28 PM, Andrew Psaltis 
wrote:

> Congratulations Sivaprasanna!
>
> On Tue, Jun 5, 2018 at 12:25 PM, Pierre Villard <
> pierre.villard...@gmail.com
> > wrote:
>
> > Congrats, well deserved!
> >
> > 2018-06-05 18:14 GMT+02:00 Mike Thomsen :
> >
> > > Congratulations, Sivaprasanna!
> > >
> > > On Tue, Jun 5, 2018 at 10:22 AM Bryan Bende  wrote:
> > >
> > > > Congrats! and thank you for your contributions to the NiFi community.
> > > >
> > > > On Tue, Jun 5, 2018 at 10:16 AM, Kevin Doran 
> > wrote:
> > > > > Congrats, Sivaprasanna!
> > > > >
> > > > > On 6/5/18, 10:09, "Tony Kurc"  wrote:
> > > > >
> > > > > On behalf of the Apache NiFI PMC, I am very pleased to announce
> > > that
> > > > > Sivaprasanna has accepted the PMC's invitation to become a
> > > committer
> > > > on the
> > > > > Apache NiFi project. We greatly appreciate all of
> Sivaprasanna's
> > > > hard work
> > > > > and generous contributions to the project. We look forward to
> > > > continued
> > > > >  involvement in the project.
> > > > >
> > > > > Sivaprasanna has been working with the community on the mailing
> > > > lists, and
> > > > > has a big mix of code and feature contributions to include
> > features
> > > > and
> > > > > improvements to cloud service integrations like Azure, AWS, and
> > > > Google
> > > > > Cloud.
> > > > >
> > > > > Welcome and congratulations!
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

Hello,

The github repo [1] is now referenced as "Mirror of
Apache NiFi Flow Design System".

-Scott

[1] https://github.com/apache/nifi-fds

On Tue, May 29, 2018 at 12:31 PM, Scott Aslan  wrote:

> I have submitted this to INFRA: https://issues.apache.
> org/jira/browse/INFRA-16588
>
> On Mon, May 28, 2018 at 4:13 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
>> Hey guys,
>>
>> Just a minor remark: the github repo [1] is still referenced as "Mirror of
>> Apache NiFi Fluid Design System".
>> I think we should file a JIRA to INFRA to get this fixed.
>>
>> Pierre
>>
>> [1] https://github.com/apache/nifi-fds
>>
>>
>> 2018-05-25 23:36 GMT+02:00 Scott Aslan :
>>
>> > Ok guys, I added a page to the nifi-site for the nifi-fds subproject:
>> > https://nifi.apache.org/fds.html
>> >
>> > -Scott
>> >
>> > On Fri, May 25, 2018 at 4:01 PM, Scott Aslan 
>> > wrote:
>> >
>> > > Thanks Matt!
>> > >
>> > > Andy, yes it looks like we still need to add a page to the nifi-site
>> for
>> > > this new sub project. Sorry for the broken link.
>> > >
>> > > -Scott
>> > >
>> > > On Fri, May 25, 2018 at 2:48 PM, Matt Gilman > >
>> > > wrote:
>> > >
>> > >> Scott,
>> > >>
>> > >> Thanks for offering to RM! I'm happy to help review the PR's for the
>> > >> remaining JIRA's you've identified.
>> > >>
>> > >> Matt
>> > >>
>> > >> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
>> > >> aichr...@protonmail.com>
>> > >> wrote:
>> > >>
>> > >> > -BEGIN PGP SIGNED MESSAGE-
>> > >> > Hash: SHA1
>> > >> >
>> > >> > > Team,
>> > >> > >
>> > >> > > There has been a lot of great work done on the NiFi Flow Design
>> > System
>> > >> > [1]
>> > >> > > and although there are still a few 'in progress' issues ([3],
>> [4],
>> > >> [5])
>> > >> > I think
>> > >> > > we are probably very close to an initial release focused on a
>> > reusable
>> > >> > > platform providing a consistent set of UI/UX components across
>> the
>> > >> NiFi
>> > >> > > ecosystem.
>> > >> > >
>> > >> > > Since NiFi Registry will have a dependency on client code
>> provided
>> > by
>> > >> > the flow
>> > >> > > design system, the first release of the flow design system would
>> > need
>> > >> to
>> > >> > > occur before the next release of NiFi Registry that integrates
>> with
>> > >> it.
>> > >> > The
>> > >> > > work on the NiFi Registry side is being done as part of
>> NIFIREG-39
>> > >> [2].
>> > >> > >
>> > >> > > Let me know if anyone has any thoughts or comments.  I'm happy to
>> > act
>> > >> as
>> > >> > RM
>> > >> > > if no one else is interested in doing so, and we can start the
>> > >> process of
>> > >> > > going through JIRA to see what is left.
>> > >> > >
>> > >> > > Thanks,
>> > >> > >
>> > >> > > Scott
>> > >> > >
>> > >> > > [1] https://nifi.apache.org/fds.html
>> > >> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
>> > >> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
>> > >> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
>> > >> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
>> > >> >
>> > >> > Glad to see the progress! FYI, the FDS link [1] appears to be
>> broken
>> > >> (404
>> > >> > Not
>> > >> > Found)
>> > >> >
>> > >> > Regards,
>> > >> >
>> > >> > Andy I.C.
>> > >> >
>> > >> > [1] https://nifi.apache.org/fds.html
>> > >> > -BEGIN PGP SIGNATURE-
>> > >> > Version: GnuPG v2.0.22 (GNU/Linux)
>> > >> >
>> > >> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
>> > >> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
>> > >> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
>> > >> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
>> > >> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
>> > >> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
>> > >> > =q33Z
>> > >> > -END PGP SIGNATURE-
>> > >> >
>> > >> >
>> > >> >
>> > >> > ​Sent from ProtonMail, Swiss-based encrypted email.​
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: [DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

I have submitted this to INFRA:
https://issues.apache.org/jira/browse/INFRA-16588

On Mon, May 28, 2018 at 4:13 AM, Pierre Villard  wrote:

> Hey guys,
>
> Just a minor remark: the github repo [1] is still referenced as "Mirror of
> Apache NiFi Fluid Design System".
> I think we should file a JIRA to INFRA to get this fixed.
>
> Pierre
>
> [1] https://github.com/apache/nifi-fds
>
>
> 2018-05-25 23:36 GMT+02:00 Scott Aslan :
>
> > Ok guys, I added a page to the nifi-site for the nifi-fds subproject:
> > https://nifi.apache.org/fds.html
> >
> > -Scott
> >
> > On Fri, May 25, 2018 at 4:01 PM, Scott Aslan 
> > wrote:
> >
> > > Thanks Matt!
> > >
> > > Andy, yes it looks like we still need to add a page to the nifi-site
> for
> > > this new sub project. Sorry for the broken link.
> > >
> > > -Scott
> > >
> > > On Fri, May 25, 2018 at 2:48 PM, Matt Gilman 
> > > wrote:
> > >
> > >> Scott,
> > >>
> > >> Thanks for offering to RM! I'm happy to help review the PR's for the
> > >> remaining JIRA's you've identified.
> > >>
> > >> Matt
> > >>
> > >> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
> > >> aichr...@protonmail.com>
> > >> wrote:
> > >>
> > >> > -BEGIN PGP SIGNED MESSAGE-
> > >> > Hash: SHA1
> > >> >
> > >> > > Team,
> > >> > >
> > >> > > There has been a lot of great work done on the NiFi Flow Design
> > System
> > >> > [1]
> > >> > > and although there are still a few 'in progress' issues ([3], [4],
> > >> [5])
> > >> > I think
> > >> > > we are probably very close to an initial release focused on a
> > reusable
> > >> > > platform providing a consistent set of UI/UX components across the
> > >> NiFi
> > >> > > ecosystem.
> > >> > >
> > >> > > Since NiFi Registry will have a dependency on client code provided
> > by
> > >> > the flow
> > >> > > design system, the first release of the flow design system would
> > need
> > >> to
> > >> > > occur before the next release of NiFi Registry that integrates
> with
> > >> it.
> > >> > The
> > >> > > work on the NiFi Registry side is being done as part of NIFIREG-39
> > >> [2].
> > >> > >
> > >> > > Let me know if anyone has any thoughts or comments.  I'm happy to
> > act
> > >> as
> > >> > RM
> > >> > > if no one else is interested in doing so, and we can start the
> > >> process of
> > >> > > going through JIRA to see what is left.
> > >> > >
> > >> > > Thanks,
> > >> > >
> > >> > > Scott
> > >> > >
> > >> > > [1] https://nifi.apache.org/fds.html
> > >> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
> > >> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
> > >> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
> > >> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
> > >> >
> > >> > Glad to see the progress! FYI, the FDS link [1] appears to be broken
> > >> (404
> > >> > Not
> > >> > Found)
> > >> >
> > >> > Regards,
> > >> >
> > >> > Andy I.C.
> > >> >
> > >> > [1] https://nifi.apache.org/fds.html
> > >> > -BEGIN PGP SIGNATURE-
> > >> > Version: GnuPG v2.0.22 (GNU/Linux)
> > >> >
> > >> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
> > >> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
> > >> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
> > >> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
> > >> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
> > >> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
> > >> > =q33Z
> > >> > -END PGP SIGNATURE-
> > >> >
> > >> >
> > >> >
> > >> > ​Sent from ProtonMail, Swiss-based encrypted email.​
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>

Re: [DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

Ok guys, I added a page to the nifi-site for the nifi-fds subproject:
https://nifi.apache.org/fds.html

-Scott

On Fri, May 25, 2018 at 4:01 PM, Scott Aslan  wrote:

> Thanks Matt!
>
> Andy, yes it looks like we still need to add a page to the nifi-site for
> this new sub project. Sorry for the broken link.
>
> -Scott
>
> On Fri, May 25, 2018 at 2:48 PM, Matt Gilman 
> wrote:
>
>> Scott,
>>
>> Thanks for offering to RM! I'm happy to help review the PR's for the
>> remaining JIRA's you've identified.
>>
>> Matt
>>
>> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
>> aichr...@protonmail.com>
>> wrote:
>>
>> > -BEGIN PGP SIGNED MESSAGE-
>> > Hash: SHA1
>> >
>> > > Team,
>> > >
>> > > There has been a lot of great work done on the NiFi Flow Design System
>> > [1]
>> > > and although there are still a few 'in progress' issues ([3], [4],
>> [5])
>> > I think
>> > > we are probably very close to an initial release focused on a reusable
>> > > platform providing a consistent set of UI/UX components across the
>> NiFi
>> > > ecosystem.
>> > >
>> > > Since NiFi Registry will have a dependency on client code provided by
>> > the flow
>> > > design system, the first release of the flow design system would need
>> to
>> > > occur before the next release of NiFi Registry that integrates with
>> it.
>> > The
>> > > work on the NiFi Registry side is being done as part of NIFIREG-39
>> [2].
>> > >
>> > > Let me know if anyone has any thoughts or comments.  I'm happy to act
>> as
>> > RM
>> > > if no one else is interested in doing so, and we can start the
>> process of
>> > > going through JIRA to see what is left.
>> > >
>> > > Thanks,
>> > >
>> > > Scott
>> > >
>> > > [1] https://nifi.apache.org/fds.html
>> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
>> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
>> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
>> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
>> >
>> > Glad to see the progress! FYI, the FDS link [1] appears to be broken
>> (404
>> > Not
>> > Found)
>> >
>> > Regards,
>> >
>> > Andy I.C.
>> >
>> > [1] https://nifi.apache.org/fds.html
>> > -BEGIN PGP SIGNATURE-
>> > Version: GnuPG v2.0.22 (GNU/Linux)
>> >
>> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
>> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
>> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
>> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
>> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
>> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
>> > =q33Z
>> > -END PGP SIGNATURE-
>> >
>> >
>> >
>> > ​Sent from ProtonMail, Swiss-based encrypted email.​
>> >
>> >
>>
>
>

Re: [DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

Thanks Matt!

Andy, yes it looks like we still need to add a page to the nifi-site for
this new sub project. Sorry for the broken link.

-Scott

On Fri, May 25, 2018 at 2:48 PM, Matt Gilman 
wrote:

> Scott,
>
> Thanks for offering to RM! I'm happy to help review the PR's for the
> remaining JIRA's you've identified.
>
> Matt
>
> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
> aichr...@protonmail.com>
> wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > > Team,
> > >
> > > There has been a lot of great work done on the NiFi Flow Design System
> > [1]
> > > and although there are still a few 'in progress' issues ([3], [4], [5])
> > I think
> > > we are probably very close to an initial release focused on a reusable
> > > platform providing a consistent set of UI/UX components across the NiFi
> > > ecosystem.
> > >
> > > Since NiFi Registry will have a dependency on client code provided by
> > the flow
> > > design system, the first release of the flow design system would need
> to
> > > occur before the next release of NiFi Registry that integrates with it.
> > The
> > > work on the NiFi Registry side is being done as part of NIFIREG-39 [2].
> > >
> > > Let me know if anyone has any thoughts or comments.  I'm happy to act
> as
> > RM
> > > if no one else is interested in doing so, and we can start the process
> of
> > > going through JIRA to see what is left.
> > >
> > > Thanks,
> > >
> > > Scott
> > >
> > > [1] https://nifi.apache.org/fds.html
> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
> >
> > Glad to see the progress! FYI, the FDS link [1] appears to be broken (404
> > Not
> > Found)
> >
> > Regards,
> >
> > Andy I.C.
> >
> > [1] https://nifi.apache.org/fds.html
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v2.0.22 (GNU/Linux)
> >
> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
> > =q33Z
> > -END PGP SIGNATURE-
> >
> >
> >
> > ​Sent from ProtonMail, Swiss-based encrypted email.​
> >
> >
>

[DISCUSS] First Release of NiFi Flow Design System

[Scott Aslan]

Team,

There has been a lot of great work done on the NiFi Flow Design System [1]
and although there are still a few 'in progress' issues ([3], [4], [5]) I think
we are probably very close to an initial release focused on a reusable
platform providing a consistent set of UI/UX components across the NiFi
ecosystem.

Since NiFi Registry will have a dependency on client code provided by the flow
design system, the first release of the flow design system would need to
occur before the next release of NiFi Registry that integrates with it. The
work on the NiFi Registry side is being done as part of NIFIREG-39 [2].

Let me know if anyone has any thoughts or comments.  I'm happy to act as RM
if no one else is interested in doing so, and we can start the process of
going through JIRA to see what is left.

Thanks,

Scott

[1] https://nifi.apache.org/fds.html
[2] https://issues.apache.org/jira/browse/NIFIREG-39
[3] https://issues.apache.org/jira/browse/NIFI-5219
[4] https://issues.apache.org/jira/browse/NIFI-5216
[5] https://issues.apache.org/jira/browse/NIFI-5240

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

[Scott Aslan]

+1 (binding)

On Fri, May 18, 2018 at 10:18 AM, James Wing  wrote:

> +1 (binding)
>
> > On May 18, 2018, at 6:30 AM, Rob Moran  wrote:
> >
> > 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

[Scott Aslan]

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  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/#/
>

Re: Nifi UI improvement

[Scott Aslan]

Hello Jorge,

There are many efforts ongoing toward the improvement of the NiFi UI and
you can see a list of them here:
https://issues.apache.org/jira/browse/NIFI-5066?jql=project%20%3D%20NIFI%20AND%20component%20%3D%20%22Core%20UI%22.
Please feel free to continue this discussion to determine the scope of the
effort you are envisioning and to gather feedback from the community about
what other users may want and then you can create a JIRA issue that will be
placed on the backlog.

-Scotty

On Thu, Apr 12, 2018 at 3:33 AM, Jorge Machado  wrote:

> Hi guys,
>
> Is there any effort to improve the UI ? One nice feature to have would be:
> Have the possibility to limit searches on a canvas. Let’s say we are inside
> a processor group and we only want to search from there on.
>
> Regards
>
> Jorge Machado
>
>
>
>
>
>
>

Re: [VOTE] Release Apache NiFi 1.6.0 (RC3)

[Scott Aslan]

+1 (binding) Release this package as nifi-1.6.0

- Ran through release helper
- Verified with test flow

On Wed, Apr 4, 2018 at 5:20 PM, Bryan Bende  wrote:

> +1 (binding) Release this package as nifi-1.6.0
>
> - Ran through release helper
> - Ran sample flows and tested granular restricted components with
> versioned flows
>
> On Wed, Apr 4, 2018 at 4:40 PM, Matt Gilman 
> wrote:
> > +1 (binding) Release this package as nifi-1.6.0
> >
> > - Ran through release help
> > - Verified issued discovered by Andrew Lim in previous RC
> >
> > Thanks for RMing Joe!
> >
> > Matt
> >
> > On Wed, Apr 4, 2018 at 2:01 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> > wrote:
> >
> >> +1 binding
> >>
> >> - went through the release helper guide
> >> - full build on Mac OS X
> >> - confirmed that previous issues reported with RC1 and RC2 are fixed
> >> - tested secured/unsecured standalone/cluster deployments
> >>
> >> Minor remark for the RM documentation and the release helper guide.
> We're
> >> currently saying to run
> >> mvn clean install -Pcontrib-check,include-grpc
> >>
> >> I'd recommend to run all the existing "include" profiles to be on the
> safe
> >> side:
> >> mvn clean install -Pcontrib-check,include-grpc,
> >> include-atlas,include-ranger
> >>
> >> Pierre
> >>
> >>
> >>
> >> 2018-04-04 16:43 GMT+02:00 Marc :
> >>
> >> > +1 binding
> >> >
> >> >-- verified sigs and hashes.
> >> >-- confirmed a parallel build with tests
> >> >-- started secure cluster and interfaced with Apache NiFi MiNiFi
> C++
> >> >
> >> >
> >> >
> >> > On Wed, Apr 4, 2018 at 6:33 AM, Takanobu Asanuma <
> tasan...@yahoo-corp.jp
> >> >
> >> > wrote:
> >> > > Thanks for all your efforts, Joe.
> >> > >
> >> > > +1(non-binding).
> >> > >  - Verified all hashes
> >> > >  - Succeeded "mvn -T 2.0C clean install -Prpm,generateArchives
> >> > -DskipTests"
> >> > >  - Started a secure cluster with three NiFi nodes and three ZK nodes
> >> > using Docker (Verified the whitelist feature)
> >> > >  - Verified some dataflows work fine
> >> > >
> >> > > -Takanobu Asanuma
> >> > >
> >> > > -Original Message-
> >> > > From: Joe Witt [mailto:joew...@apache.org]
> >> > > Sent: Wednesday, April 04, 2018 8:49 AM
> >> > > To: dev@nifi.apache.org
> >> > > Subject: [VOTE] Release Apache NiFi 1.6.0 (RC3)
> >> > >
> >> > > Hello,
> >> > >
> >> > > I am pleased to be calling this vote for the source release of
> Apache
> >> > NiFi nifi-1.6.0.
> >> > >
> >> > > The source zip, including signatures, digests, etc. can be found at:
> >> > > https://repository.apache.org/content/repositories/
> orgapachenifi-1124
> >> > >
> >> > > The Git tag is nifi-1.6.0-RC3
> >> > > The Git commit ID is f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
> >> > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> >> > f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
> >> > >
> >> > > Checksums of nifi-1.6.0-source-release.zip:
> >> > > SHA1: d1e1c24f9af809bf812982962b61d07df4f1131e
> >> > > SHA256: 1e5028d594bb402aa36460f1b826d4
> e8a664ad6f0538deed20286cbf3c62
> >> 1fb8
> >> > > SHA512: 8cb10cbafa6feeed712dbc0cf07649
> 6d6bc014276aab71383ff3481d8ea7
> >> > 19cf1f39766abc76c75ba58ffca747df3bd6d9bac82e410de1c78673dcd16a5ddfee
> >> > >
> >> > > 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
> >> > >
> >> > > 162 issues were closed/resolved for this release:
> >> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > projectId=12316020&version=12342422
> >> > >
> >> > > Release note highlights can be found here:
> >> > > https://cwiki.apache.org/confluence/display/NIFI/
> >> > Release+Notes#ReleaseNotes-Version1.6.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.6.0 [ ] +0 no opinion [ ] -1
> Do
> >> > not release this package because...
> >> >
> >>
>

Re: Firefox - Slower movements when moving around the canvas

[Scott Aslan]

I just upgraded to Firefox 59.0.2 (from 58) on my Mac. I am also not seeing
any glaring performance difference between FF and Chrome and I also would
say FF 59 is faster than the previous version.

Pierre, are you running any other plugins for FF or any other software on
your Mac that may impact overall performance?

On Tue, Apr 3, 2018 at 4:30 PM, Matt Gilman  wrote:

> I have not had a chance to fully dig in but I upgraded from Firefox 57 to
> Firefox 59. While there is nothing quantitative behind this Firefox 59
> seemed to have better performance. I'll continue investigating and digging
> through some Firefox tickets to see if there is anything interesting.
> Additionally, Firefox 59 seemed to be on par with Chrome 65.
>
> Matt
>
> On Tue, Apr 3, 2018 at 4:10 PM, Michael Moser  wrote:
>
> > Adding a data point: using Firefox for Linux 64-bit, I see no difference
> > between Firefox 58.0.2 and 59.0.2.  Neither exhibit a slow canvas with
> the
> > NiFi UI.
> >
> > -- Mike
> >
> >
> > On Tue, Apr 3, 2018 at 3:24 PM, Pierre Villard <
> > pierre.villard...@gmail.com>
> > wrote:
> >
> > > Yep, same here Mike, back to square one I guess...
> > > One additional remark: paint event duration seems to be proportional
> with
> > > the number of elements to paint on the UI. Not really surprising but
> just
> > > wanted to add the info.
> > >
> > >
> > > 2018-04-03 21:12 GMT+02:00 Mike Thomsen :
> > >
> > > > Found on Reddit that you can toggle OMTP using this:
> > layers.omtp.enabled
> > > >
> > > > Disabled it and restarted. Didn't seem to do any good.
> > > >
> > > > On Tue, Apr 3, 2018 at 3:08 PM, Mike Thomsen  >
> > > > wrote:
> > > >
> > > > > Yeah, I'm using a Mac.
> > > > >
> > > > > On Tue, Apr 3, 2018 at 2:34 PM, Pierre Villard <
> > > > > pierre.villard...@gmail.com> wrote:
> > > > >
> > > > >> I've been trying to debug this one and here are my findings so
> > far...
> > > > >>
> > > > >> When debugging performance with the developer tools, the "Paint"
> > event
> > > > of
> > > > >> the page is what is taking so long (between 3.5s to 5.5s (!!!)
> when
> > I
> > > > move
> > > > >> from one place to another on the root canvas). Based on the
> release
> > > note
> > > > >> of
> > > > >> Firefox 59.0 [1], I see that there is something new for Mac users
> > > (Mike,
> > > > >> are you also using a Mac?): "Improved graphics rendering using
> > > > >> Off-Main-Thread Painting (OMTP) [2] for Mac users (OMTP for
> Windows
> > > was
> > > > >> released in Firefox 58)".
> > > > >>
> > > > >> So it seems to be related to this new feature(someone using
> Windows
> > > > could
> > > > >> help conf irming if it's also slow using Firefox 58.x.).
> > > > >> I tried to find existing bugs but didn't find anything really
> > > > relevant...
> > > > >>
> > > > >> [1] https://www.mozilla.org/en-US/firefox/59.0/releasenotes/
> > > > >> [2] https://mozillagfx.wordpress.com/2017/12/05/off-main-
> > > > thread-painting/
> > > > >>
> > > > >>
> > > > >>
> > > > >> 2018-04-03 16:00 GMT+02:00 Mike Thomsen :
> > > > >>
> > > > >> > I experienced it yesterday as well. I'm about to install a LTS
> > > version
> > > > >> of
> > > > >> > Firefox so I can keep going there.
> > > > >> >
> > > > >> > While someone from the UI side figures this out, I think it
> should
> > > be
> > > > >> filed
> > > > >> > as a bug report to Mozilla.
> > > > >> >
> > > > >> > On Sat, Mar 31, 2018 at 5:04 PM, Pierre Villard <
> > > > >> > pierre.villard...@gmail.com
> > > > >> > > wrote:
> > > > >> >
> > > > >> > > Just confirmed that behavior changed between Firefox 58.x and
> > > 59.x.
> > > > >> > > I'll let our UI gurus find the root cause and will probably
> use
> > > > >> Chrome in
> > > > >> > > the meantime :)
> > > > >> > >
> > > > >> > > 2018-03-31 22:02 GMT+02:00 Pierre Villard <
> > > > >> pierre.villard...@gmail.com>:
> > > > >> > >
> > > > >> > > > Hi guys,
> > > > >> > > >
> > > > >> > > > I'm running on master, using Firefox (59.0.2), and it seems
> it
> > > got
> > > > >> > slower
> > > > >> > > > to move around the canvas. In my case, I've around 10 PGs
> and
> > > > >> around 50
> > > > >> > > > processors. When trying to move from one place to another at
> > the
> > > > >> root
> > > > >> > > > level, it's really slow and movement is intermittent/broken
> > (not
> > > > >> > fluid).
> > > > >> > > > When accessing the same NiFi with Chrome, no issue at all.
> > > > >> > > >
> > > > >> > > > Problem is... I've also tried with a NiFi 1.5.0 and a NiFi
> > > 1.3.0 I
> > > > >> have
> > > > >> > > > locally with various workflows, and it's the same with the
> > older
> > > > >> > > versions.
> > > > >> > > >
> > > > >> > > > Wondering if this could be related to the upgrade to Firefox
> > > 59.x.
> > > > >> > > >
> > > > >> > > > Has anyone experienced the same?
> > > > >> > > >
> > > > >> > > > I can try to downgrade to Firefox 58.x to confirm but wanted
> > to
> > > > >> check
> > > > >> > > with
> > > > >> > > > the community first.
> > > 

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

[Scott Aslan]

+1 (binding)

- Ran through release helper
- Setup secure NiFi and verified a test flow

Sivaprasanna, I believe the issue you are seeing is due to npm not playing
well with your linux distro. If you checkout latest master it contains this
PR  which should allow you to
complete your build.

-Scott

On Wed, Mar 28, 2018 at 2:01 PM, Mark Payne  wrote:

> +1 (binding)
>
> Was able to build successfully and start application. Created some simple
> flows to verify expected behavior.
> Verified hashes and signing.
>
> Thanks
> -Mark
>
>
>
> > On Mar 26, 2018, at 11:34 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.6.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1123
> >
> > The Git tag is nifi-1.6.0-RC2
> > The Git commit ID is b5935ec81a7cbc048820781ac62cd96bbea5b232
> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> b5935ec81a7cbc048820781ac62cd96bbea5b232
> >
> > Checksums of nifi-1.6.0-source-release.zip:
> > SHA1: 009f1e2e3c17e38f21f27170b9c06228d11653c0
> > SHA256: 39941a5b25427e2b4cc5ba8206084ff92df58863f29ddd097d4ac1e85424beb9
> > SHA512: 1773417a48665e3cda22180ea7f401bc8190ebddbf3f7bc29831e46e7ab0
> a07694c6e478d252fa573209d4a3c8132a522a8507b6a8784669ab7364847a07e234
> >
> > 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
> >
> > 146 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12342422
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.6.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.6.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: [VOTE] Release Apache NiFi 1.6.0

[Scott Aslan]

+1 (binding)

- Ran through release helper
- Setup secure NiFi and verified a test flow

On Fri, Mar 23, 2018 at 3:29 PM, Bryan Bende  wrote:

> +1 (binding)
>
> - Ran through release helper and everything checked out
> - Verified some test flows with the restricted components + keytab CS
>
>
>
> On Fri, Mar 23, 2018 at 2:42 PM, Mark Payne  wrote:
> > +1 (binding)
> >
> > Was able to verify hashes, build with contrib-check, and start up
> application. Performed some basic functionality tests and all worked as
> expected.
> >
> > Thanks!
> > -Mark
> >
> >
> >> On Mar 23, 2018, at 6:02 AM, Takanobu Asanuma 
> wrote:
> >>
> >> Thanks for all your efforts, Joe.
> >>
> >> I have one question. The version of the generated package is
> nifi-1.7.0-SNAPSHOT. Is this correct at this stage? If it's ok,
> +1(non-binding).
> >>
> >> - Succeeded "mvn -T 2.0C clean install -DskipTests -Prpm"
> >> - Started secure cluster mode
> >> - Verified sample dataflows work fine
> >> - Verified the whitelist feature(NIFI-4761) works fine
> >>
> >> -Takanobu Asanuma
> >>
> >> -Original Message-
> >> From: Joe Witt [mailto:joew...@apache.org]
> >> Sent: Friday, March 23, 2018 1:12 AM
> >> To: dev@nifi.apache.org
> >> Subject: [VOTE] Release Apache NiFi 1.6.0
> >>
> >> Hello,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-1.6.0.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://repository.apache.org/content/repositories/orgapachenifi-1122
> >>
> >> The Git tag is nifi-1.6.0-RC1
> >> The Git commit ID is 49a71f4740c9fac38958961f78dd3cde874b0e45
> >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 49a71f4740c9fac38958961f78dd3cde874b0e45
> >>
> >> Checksums of nifi-1.6.0-source-release.zip:
> >> SHA1: 4fb82f386a0aa83614cc01449e540527443811ce
> >> SHA256: 4df6638ec87a5bee12e7978abc64137ee5da5fc8c399e34cf34ca1c3720a
> c891
> >> SHA512: 6fa536f9618c6c153c04df5db59913eaf3dd54ae2389368129ac6237f755
> 19e1eee7ba0ca70145a95de01517a1c3ea1f36975895d9d72bb04abb56b7934e013a
> >>
> >> 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
> >>
> >> 135 issues were closed/resolved for this release:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12342422
> >>
> >> Release note highlights can be found here:
> >> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.6.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.6.0 [ ] +0 no opinion [ ] -1 Do
> not release this package because...
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Mike Thomsen

[Scott Aslan]

Congrats!

On Wed, Mar 21, 2018 at 10:15 AM, Pierre Villard <
pierre.villard...@gmail.com> wrote:

> Congrats Mike, well deserved!
>
> 2018-03-21 14:55 GMT+01:00 Mike Thomsen :
>
> > Thanks everyone!
> >
> > On Wed, Mar 21, 2018 at 9:55 AM, Joe Witt  wrote:
> >
> > > Mike
> > >
> > > Thanks for all the great contributions and reviews and discussions and
> > > congratulations on the well deserved commit bit!
> > >
> > > Thanks
> > > Joe
> > >
> > > On Wed, Mar 21, 2018 at 1:53 PM, Kevin Doran 
> wrote:
> > > > Congrats, Mike!
> > > >
> > > > On 3/21/18, 09:42, "Tony Kurc"  wrote:
> > > >
> > > > On behalf of the Apache NiFI PMC, I am very pleased to announce
> > that
> > > Mike
> > > > has accepted the PMC's invitation to become a committer on the
> > > Apache NiFi
> > > > project. We greatly appreciate all of Mike's hard work and
> generous
> > > > contributions to the project. We look forward to his continued
> > > involvement
> > > > in the project.
> > > >
> > > > Mike has been contributing to the project for quite a while,
> > > contributing
> > > > features such as  enhancements to MongoDB and HBase processors as
> > > well as
> > > > things like improvements to Expression Language and
> LookupService.
> > > I'm sure
> > > > many of you have interacted with Mike on the mailing lists where
> he
> > > has
> > > > been giving great input on both the project and community. We
> also
> > > > appreciate his work reviewing and providing feedback on new
> > > contributions.
> > > >
> > > > Welcome and congratulations!
> > > > Tony
> > > >
> > > >
> > > >
> > >
> >
>

Re: [EXT] Re: Help with frontend-maven-plugin?

[Scott Aslan]

Ok, I see the problem now. Thank you for the javascript errors. I opened
this ticket to solve the issue:
https://issues.apache.org/jira/browse/NIFI-4998

Will you please cherry-pick from this PR:
https://github.com/apache/nifi/pull/2571 and confirm that it fixes the
issue you are seeing?

-Scott

On Tue, Mar 20, 2018 at 11:10 PM, Peter Wicks (pwicks) 
wrote:

> Scott, thanks for the response.
>
>
>
> As you can see in the log/error information I included, it is detecting my
> proxy settings; and the proxy information it shows (I removed parts of the
> hostname in my message) are correct.
>
>
>
> > [INFO] --- frontend-maven-plugin:1.1:npm (npm install) @ nifi-web-ui
>
> >  [INFO] Found proxies: [m-proxy{protocol='http', host='proxy..com',
>
> > port=8080}, m-proxy-https{protocol='https', host='proxy..com',
>
> > port=8080}] [INFO] Running 'npm --cache-min Infinity install
>
> > --https-proxy=
>
> > http://proxy..com:8080 --proxy=http://proxy..com:8080' in
>
> > C:\\nifi\nifi-nar-bundles\nifi-framework-bundle\nifi-
>
> > framework\nifi-web\nifi-web-ui\target\frontend-working-directory
>
> > [INFO]
>
>
>
> I also already tried changing NPM versions:
>
>
>
> > I tried just updating the version numbers for the components involved,
> and the
>
> > build does complete, but I'm left with a copy of NiFi Web UI that
> doesn't work after deployment.
>
>
>
> Since you have had success with running newer versions with the NiFi
> Registry build, I copied those version numbers over into NiFi Web UI's
> pom.xml. When I do this the build succeeds, but the Web UI will not load
> all the way in Chrome. In the JavaScript console I see several errors:
>
>
> Navigated to http://localhost:8080/nifi/
> localhost/:61 GET http://localhost:8080/nifi/assets/angular/angular.min.js
> net::ERR_ABORTED
> localhost/:62 GET http://localhost:8080/nifi/assets/angular-messages/
> angular-messages.min.js net::ERR_ABORTED
> localhost/:65 GET http://localhost:8080/nifi/assets/angular-aria/angular-
> aria.min.js net::ERR_ABORTED
> localhost/:66 GET http://localhost:8080/nifi/assets/angular-animate/
> angular-animate.min.js net::ERR_ABORTED
> (index):61 GET http://localhost:8080/nifi/assets/angular/angular.min.js
> net::ERR_ABORTED
> (index):62 GET http://localhost:8080/nifi/assets/angular-messages/
> angular-messages.min.js net::ERR_ABORTED
> angular-resource.js:8 Uncaught TypeError: Cannot read property '$$minErr'
> of undefined at angular-resource.js:8 at angular-resource.js:6
> angular-route.js:24 Uncaught TypeError: Cannot read property 'module' of
> undefined at angular-route.js:24 at angular-route.js:6
> (index):65 GET http://localhost:8080/nifi/assets/angular-aria/angular-
> aria.min.js net::ERR_ABORTED
> (index):66 GET http://localhost:8080/nifi/assets/angular-animate/
> angular-animate.min.js net::ERR_ABORTED
> angular-material.min.js:7 Uncaught TypeError: Cannot read property
> 'module' of undefined at angular-material.min.js:7 at
> angular-material.min.js:7 at angular-material.min.js:15
> jquery.min.js:2 jQuery.Deferred exception: Cannot read property 'module'
> of undefined TypeError: Cannot read property 'module' of undefined at
> HTMLDocument. (http://localhost:8080/nifi/
> js/nf/canvas/nf-canvas-all.js?1.6.0-SNAPSHOT:77:5364) at j (
> http://localhost:8080/nifi/assets/jquery/dist/jquery.min.js:2:29948) at k
> (http://localhost:8080/nifi/assets/jquery/dist/jquery.min.js:2:30262)
> undefined
> jquery.min.js:2 Uncaught TypeError: Cannot read property 'module' of
> undefined at HTMLDocument. (nf-canvas-all.js?1.6.0-SNAPSHOT:77)
> at j (jquery.min.js:2) at k (jquery.min.js:2)
>
>
>
> This is why I was hoping someone with more UI development experience could
> try updating the version numbers and see if they can work out the issues.
>
>
>
> Thanks!
>
>   Peter
>
>
>
> -Original Message-
> From: Scott Aslan [mailto:scottyas...@gmail.com]
> Sent: Tuesday, March 20, 2018 23:11
> To: dev@nifi.apache.org
> Subject: [EXT] Re: Help with frontend-maven-plugin?
>
>
>
> Hey there Peter,
>
>
>
> I am not sure that the frontend-maven-plugin is out of date or old (the
> last commit was November 2017). NiFi is running version 1.1 of this plugin
> and NiFi Registry is running version 1.5. The frontend-maven-plugin
> downloads versions of Node and npm from https://nodejs.org/dist, extracts
> them and puts them into a node folder created in your installation
> directory. You can change the version of this maven plugin here <
> https://github.com/

Re: Help with frontend-maven-plugin?

[Scott Aslan]

Hey there Peter,

I am not sure that the frontend-maven-plugin is out of date or old (the
last commit was November 2017). NiFi is running version 1.1 of this plugin
and NiFi Registry is running version 1.5. The frontend-maven-plugin
downloads versions
of Node and npm from https://nodejs.org/dist, extracts them and puts them
into a node folder created in your installation directory. You can change
the version of this maven plugin here
.
Node will only be "installed" locally to your project. It will not be
installed globally on the whole system (and it will not interfere with any
Node installations already present). Node then installs npm. If the issue
you are encountering is with the version of npm, then you can change the
version of node or npm in the pom.xml here

. If you have configured proxy settings for Maven
 in your
settings.xml file, the frontend-maven-plugin will automatically use the
proxy for downloading node and npm, as well as passing the proxy to npm
commands .

-Scott

On Tue, Mar 20, 2018 at 5:02 AM, Peter Wicks (pwicks) 
wrote:

> The version of "frontend-maven-plugin" used in NiFi is out of date, and
> the versions of NPM and Node referenced by it are also a bit old.
>
> I wouldn't bring this up, except there is a bug in this version of NPM
> that can cause issues when trying to download NPM packages via proxy server.
>
> This is the error I'm seeing:
>
> [INFO] --- frontend-maven-plugin:1.1:npm (npm install) @ nifi-web-ui ---
> [INFO] Found proxies: [m-proxy{protocol='http', host='proxy..com',
> port=8080}, m-proxy-https{protocol='https', host='proxy..com', port=8080}]
> [INFO] Running 'npm --cache-min Infinity install --https-proxy=
> http://proxy..com:8080 --proxy=http://proxy..com:8080' in
> C:\\nifi\nifi-nar-bundles\nifi-framework-bundle\nifi-
> framework\nifi-web\nifi-web-ui\target\frontend-working-directory
> [INFO]
>
> ...
>
> [ERROR] npm http GET https://registry.npmjs.org/d3/4.13.0
> [ERROR] npm ERR! TypeError: Request path contains unescaped characters.
> [ERROR] npm ERR! at new ClientRequest (_http_client.js:53:11)
> [ERROR] npm ERR! at TunnelingAgent.exports.request (http.js:31:10)
>
>
>
> I've been successful building if I leave the proxy behind, but I can only
> do that outside of work... which makes it hard.  I tried just updating the
> version numbers for the components involved, and the build does complete,
> but I'm left with a copy of NiFi Web UI that doesn't work after deployment.
>
> Thoughts? It would be great of one of the UI developers who's more
> familiar with NPM/Node could look at this maybe?
>
> Thanks,
>   Peter
>

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

[Scott Aslan]

All,

This vote has ended with:

15 binding +1s
2 non-binding +1s
0 <= 0

The vote to establish Fluid Design System as a sub-project of the Apache
NiFi TLP
has passed.

Thank you all for your participation in this important vote. I will
submit the necessary information to infra to get the ball rolling

Thanks,

Scott

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

[Scott Aslan]

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
*

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Sivaprasanna,

I don't think we want to use color to describe this sub project since the
theme (colors) of the UX components will be configurable.

Kevin/MattG,

"Fluid" made sense to me for its tie to NiFi terminology.  Also, the
components are meant to be responsive in order to support different screen
sizes and the theme of the components are configurable (fluid) as well. As
far as including the "Design System" in the title I do think this is a
helpful description for UI/UX developers/designers.

If no one has any other questions then I will go ahead and kick off a
vote...

-Scotty

On Thu, Mar 1, 2018 at 2:14 PM, Kevin Doran  wrote:

> I like NiFi Design System. A bit "boring" perhaps, but probably the most
> self-descriptive project name for newcomers.
>
> I like Fluid Design System as well if the intent is to be more generic,
> indicating that it is not intended just for NiFi projects but can be
> utilized anywhere (but "fluid" has a tie in to NiFi terminology as well).
>
> Thanks for the links to other examples - that was helpful as I don't have
> much background / knowledge in modern UX development.
>
> Kevin
>
> On 3/1/18, 10:08, "Scott Aslan"  wrote:
>
> Hello MikeM/everyone,
>
> One of the questions brought up in this discussion was centered around
> what
> a design system is. I stumbled upon a really great article this
> morning on
> this exact topic. It also links to several other really great articles
> and
> will help us all to understand.
> https://uxplanet.org/design-systems-in-2016-5415a660b29
>
> Also, I was thinking about the name what does everyone think about
> naming this sub-project NiFi Design System?
>
> -Scotty
>
> On Fri, Feb 23, 2018 at 10:20 AM, Scott Aslan 
> wrote:
>
> > TonyK,
> >
> > The intent is to use this this NgModule in NiFi Registry and
> eventually
> > NiFi. However, this would be released under ASLv2 so yes other
> projects
> > could use it.
> >
> > On Thu, Feb 22, 2018 at 10:46 PM, Tony Kurc 
> wrote:
> >
> >> Is some of the thinking that projects other than nifi projects
> would use
> >> this?
> >>
> >> On Feb 22, 2018 10:00 PM, "Scott Aslan" 
> wrote:
> >>
> >> > Sivaprasanna,
> >> >
> >> > I am not sure I follow exactly what you are saying...
> >> >
> >> > NiFi Registry would no longer continue to host a copy of the FDS
> >> NgModule.
> >> > Instead, NiFi Registry would just add the NiFi FDS sub-project as
> a
> >> client
> >> > side dependency in its package.json. This would be analogous to
> how NiFi
> >> > Registry depends on Angular Material, etc. npm supports the
> ability to
> >> > download published packages which are current with the latest
> stable
> >> > release of a package. npm *also* supports the ability to develop
> off
> >> > of the *master
> >> > branch (or any other branch really)* of the NiFi FDS. An example
> of this
> >> > can be found in the github.io demo here
> >> > <https://github.com/scottyaslan/fluid-design-system/blob/gh-
> >> pages/package.
> >> > json#L45>
> >> > . By placing that dependency in the package.json for the NiFi
> Registry
> >> each
> >> > subsequent clean build would automatically download the latest
> master
> >> > branch of the NiFi FDS sub-project and developers can leverages
> the
> >> latest
> >> > NiFi FDS components.
> >> >
> >> > This also brings up a good point about release management. I have
> also
> >> > included a prototype of one possible implementation of automating
> the
> >> > tagging of a branch and automatically updating release version
> numbers
> >> etc.
> >> > leveraging grunt-bump [1]. The FDS-0.0.1-RC.0 tag [2] was created
> with
> >> the
> >> > described grunt task.
> >> >
> >> > [1]
> >> > https://github.com/scottyaslan/fluid-design-system/blob/
> >> master/Gruntfile.
> >> > js#L47
> >> >
> >> > [2] https://github.com/scottyaslan/fluid-design-system/tree/FDS-
> >> 0.0.1-RC.0
> >> >
> >> > On Thu, Feb 22, 2018 at 12:39 PM, Sivaprasanna <
>   

Re: [DISCUSS] MiNiFi Flow Designer

[Scott Aslan]

e the user of the file handling and transformation
> > processes.  Additionally, this comes with caveats, among them that
> given
> > the ways in which C++ allows us different accesses, there are some
> > interesting processors that work better for that more native
> approach and
> > might not ever justify having an equivalent in Java.
> >
> > (2) Providing a first class experience in NiFi for MiNiFi flow
> designing
> > making use of the existing UI components as a base and a new design
> mode
> > specifically for providing a clean user experience, letting users
> operate
> > in a different context but a familiar environment.  Certainly
> preferred,
> > but how this fit was not clear.
> >
> > As a crash course in MiNiFi efforts, there have been some key
> > contributions that I believe when more strongly united can generate
> a very
> > complete authoring and flow update process.  Some of these items are:
> >
> >- C2 API Protocol specification and implementation in C++ [3]
>     >- C2 Server with the notion of serving different flows [4] backed
> by
> >varying implementations, one of which was via REST to access NiFi
> Templates
> >directly [5]
> >- Warm Redeploy in MiNiFi Java [6]
> >
> >
> > One of the first questions to come to mind was, “Is within NiFi the
> right
> > place?”
> >
> > I think there are several reasons that this is reasonable. Seeing
> some of
> > the discussion around the consolidation of common UI components
> presented
> > by Scott Aslan, I think sharing the core of the UI elements between
> the
> > traditional NiFi and MiNiFi flow designs is a logical extension.
> While
> > those flows in MiNiFi are not real-time changes we are dealing with
> the
> > same design elements in creating directed graphs.  Additionally,
> while
> > MiNiFi instances will likely not ever have the same breadth of
> extensions
> > supported, there is nothing inherently prohibitive of a more complex
> graph
> > comprised of larger numbers of edges and/or vertices.  In my view,
> the
> > mechanics are the same but just being performed in a different
> contexts.
> > In the case of MiNiFi, this is effectively an “offline” context.  By
> > "offline," I mean we are not strictly bound to loaded components
> such as
> > that in the current NiFi context consisting of items from unpacked
> NARs.
> >
> > How can we minimize the impact to NiFi?
> >
> > Given that this is a new capability, I don’t know that we
> necessarily need
> > to interfere with the existing APIs and could possibly also make
> this an
> > optional feature.  From this standpoint, we could develop new
> endpoints for
> > this specific context.  Some of this work would rely on external
> services
> > and/or definitions to drive the different context.  For example,
> without
> > NARs acting as the source of available components, something like
> the C2
> > server could provide extensions for MiNiFi instances it is aware of
> to help
> > drive the experience.  This data would be a skeletal view of a
> component
> > definition/interface without any of the inherent code backing it
> needed.
> >
> > How do we maximize the utility of these efforts?
> >
> > With the idea about powering MiNiFi flow design with specific sets of
> > components, I could see this extending to even NiFi itself.
> Consider the
> > use case where something like I wish to make use of additional
> artifacts
> > along the lines of [7] and an extension of the current Registry
> > implementation.  As a simple example, with an understanding of what
> the
> > universe of components is available to my system and not just those
> > currently loaded, it would be possible for users to design for other
> > instances.  With these hooks in place, there are a few permutations
> of this
> > relative concept that enable us to carry out some of the “nice to
> haves” we
> > haven’t quite been able to address.
> >
> > How does this all come together for MiNiFi?
> >
> > I have created a work of sheer artistic mastery on the Command and
> Control
> > proposal to illustrate a rough sequence and architecture. [8]  This
> diagram
> > shows from entering MiNiFi flow design through to an instance
> updating to
> > the new flow.
> >
> >
> > Overall, Registry was a tremendous step forward for the NiFi
> ecosystem.  I
> > think in our current state, we have reached a convergence of
> capabilities
> > that allow us to build higher level abstractions for dataflow
> management.
> > I think the approach of (2) is a great first foray into that realm
> that
> > provides an immediate solution for a gap in our MiNiFi efforts.
> > Additionally, this approach lays the foundation for additional
> applications
> > possibly inclusive of core NiFi.
> >
> > I look forward to your thoughts and commentary.  Certainly many
> details to
> > think and reason about, but I see some incredible potential with the
> work
> > we've done thus far both near and long term.
> >
> > Thanks for your time!
> > --aldrin
> >
> >
>
>
>
>

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Hello MikeM/everyone,

One of the questions brought up in this discussion was centered around what
a design system is. I stumbled upon a really great article this morning on
this exact topic. It also links to several other really great articles and
will help us all to understand.
https://uxplanet.org/design-systems-in-2016-5415a660b29

Also, I was thinking about the name what does everyone think about
naming this sub-project NiFi Design System?

-Scotty

On Fri, Feb 23, 2018 at 10:20 AM, Scott Aslan  wrote:

> TonyK,
>
> The intent is to use this this NgModule in NiFi Registry and eventually
> NiFi. However, this would be released under ASLv2 so yes other projects
> could use it.
>
> On Thu, Feb 22, 2018 at 10:46 PM, Tony Kurc  wrote:
>
>> Is some of the thinking that projects other than nifi projects would use
>> this?
>>
>> On Feb 22, 2018 10:00 PM, "Scott Aslan"  wrote:
>>
>> > Sivaprasanna,
>> >
>> > I am not sure I follow exactly what you are saying...
>> >
>> > NiFi Registry would no longer continue to host a copy of the FDS
>> NgModule.
>> > Instead, NiFi Registry would just add the NiFi FDS sub-project as a
>> client
>> > side dependency in its package.json. This would be analogous to how NiFi
>> > Registry depends on Angular Material, etc. npm supports the ability to
>> > download published packages which are current with the latest stable
>> > release of a package. npm *also* supports the ability to develop off
>> > of the *master
>> > branch (or any other branch really)* of the NiFi FDS. An example of this
>> > can be found in the github.io demo here
>> > <https://github.com/scottyaslan/fluid-design-system/blob/gh-
>> pages/package.
>> > json#L45>
>> > . By placing that dependency in the package.json for the NiFi Registry
>> each
>> > subsequent clean build would automatically download the latest master
>> > branch of the NiFi FDS sub-project and developers can leverages the
>> latest
>> > NiFi FDS components.
>> >
>> > This also brings up a good point about release management. I have also
>> > included a prototype of one possible implementation of automating the
>> > tagging of a branch and automatically updating release version numbers
>> etc.
>> > leveraging grunt-bump [1]. The FDS-0.0.1-RC.0 tag [2] was created with
>> the
>> > described grunt task.
>> >
>> > [1]
>> > https://github.com/scottyaslan/fluid-design-system/blob/
>> master/Gruntfile.
>> > js#L47
>> >
>> > [2] https://github.com/scottyaslan/fluid-design-system/tree/FDS-
>> 0.0.1-RC.0
>> >
>> > On Thu, Feb 22, 2018 at 12:39 PM, Sivaprasanna <
>> sivaprasanna...@gmail.com>
>> > wrote:
>> >
>> > > I agree with Matt. With clear documentation and guides, contributions
>> on
>> > > the sub-projects can be streamlined and be ensured that the necessary
>> > > changes are already available on the core project i.e NiFi. One
>> challenge
>> > > is that the committer of the sub-project should have the courtesy to
>> > check
>> > > wether the supporting changes are made available to the core project
>> and
>> > > track its status but given how contributions are being handled in
>> > > nifi-registry project, I don’t think it’s going to be that much of a
>> > > headache.
>> > >
>> > > We could also add to the helper doc mentioning that if the
>> contribution
>> > is
>> > > going to affect a core component, the contributor needs to add the
>> JIRA
>> > id
>> > > of the core project’s supporting changes in the sub-projects’ issue
>> > > description.
>> > >
>> > > On Thu, 22 Feb 2018 at 10:42 PM, Matt Gilman > >
>> > > wrote:
>> > >
>> > > > Joe, Joe,
>> > > >
>> > > > Regarding the release process... I think it could be similar to how
>> > folks
>> > > > verified and validated the NiFi Registry release. Guidance was given
>> > in a
>> > > > helper guide regarding how to obtain/build a branch or PR that
>> > references
>> > > > the new components. For the Registry release, there was a PR for
>> NiFi
>> > > that
>> > > > had the supporting changes already available.
>> > > >
>> > > > We may have this issue any time we release new versions that depend
>> on
&g

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

TonyK,

The intent is to use this this NgModule in NiFi Registry and eventually
NiFi. However, this would be released under ASLv2 so yes other projects
could use it.

On Thu, Feb 22, 2018 at 10:46 PM, Tony Kurc  wrote:

> Is some of the thinking that projects other than nifi projects would use
> this?
>
> On Feb 22, 2018 10:00 PM, "Scott Aslan"  wrote:
>
> > Sivaprasanna,
> >
> > I am not sure I follow exactly what you are saying...
> >
> > NiFi Registry would no longer continue to host a copy of the FDS
> NgModule.
> > Instead, NiFi Registry would just add the NiFi FDS sub-project as a
> client
> > side dependency in its package.json. This would be analogous to how NiFi
> > Registry depends on Angular Material, etc. npm supports the ability to
> > download published packages which are current with the latest stable
> > release of a package. npm *also* supports the ability to develop off
> > of the *master
> > branch (or any other branch really)* of the NiFi FDS. An example of this
> > can be found in the github.io demo here
> > <https://github.com/scottyaslan/fluid-design-
> system/blob/gh-pages/package.
> > json#L45>
> > . By placing that dependency in the package.json for the NiFi Registry
> each
> > subsequent clean build would automatically download the latest master
> > branch of the NiFi FDS sub-project and developers can leverages the
> latest
> > NiFi FDS components.
> >
> > This also brings up a good point about release management. I have also
> > included a prototype of one possible implementation of automating the
> > tagging of a branch and automatically updating release version numbers
> etc.
> > leveraging grunt-bump [1]. The FDS-0.0.1-RC.0 tag [2] was created with
> the
> > described grunt task.
> >
> > [1]
> > https://github.com/scottyaslan/fluid-design-system/blob/master/Gruntfile
> .
> > js#L47
> >
> > [2] https://github.com/scottyaslan/fluid-design-
> system/tree/FDS-0.0.1-RC.0
> >
> > On Thu, Feb 22, 2018 at 12:39 PM, Sivaprasanna <
> sivaprasanna...@gmail.com>
> > wrote:
> >
> > > I agree with Matt. With clear documentation and guides, contributions
> on
> > > the sub-projects can be streamlined and be ensured that the necessary
> > > changes are already available on the core project i.e NiFi. One
> challenge
> > > is that the committer of the sub-project should have the courtesy to
> > check
> > > wether the supporting changes are made available to the core project
> and
> > > track its status but given how contributions are being handled in
> > > nifi-registry project, I don’t think it’s going to be that much of a
> > > headache.
> > >
> > > We could also add to the helper doc mentioning that if the contribution
> > is
> > > going to affect a core component, the contributor needs to add the JIRA
> > id
> > > of the core project’s supporting changes in the sub-projects’ issue
> > > description.
> > >
> > > On Thu, 22 Feb 2018 at 10:42 PM, Matt Gilman 
> > > wrote:
> > >
> > > > Joe, Joe,
> > > >
> > > > Regarding the release process... I think it could be similar to how
> > folks
> > > > verified and validated the NiFi Registry release. Guidance was given
> > in a
> > > > helper guide regarding how to obtain/build a branch or PR that
> > references
> > > > the new components. For the Registry release, there was a PR for NiFi
> > > that
> > > > had the supporting changes already available.
> > > >
> > > > We may have this issue any time we release new versions that depend
> on
> > > > another (sub)project.
> > > >
> > > > Matt
> > > >
> > > > On Thu, Feb 22, 2018 at 11:39 AM, Joe Percivall <
> jperciv...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Scott,
> > > > >
> > > > > Definitely like the direction of standardizing NiFi and Registry
> > around
> > > > the
> > > > > same set of components, so the user has a common UX. Is there
> > precedent
> > > > for
> > > > > creating a new sub-project just for common components/modules to be
> > > used
> > > > by
> > > > > the top-level, and it's other sub-projects? My concerns are similar
> > to
> > > > > Joe's. Along those lines, if the core problems we're trying to
&g

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

MikeT,

Good question. Right now NiFi has a mix of design systems from Angular
Material, multiple jquery plugins (some of them custom and all of them have
their own approach to styling), jquery UI, and custom D3 visualizations. In
order to add a new UX feature in NiFi a developer needs to know each and
everyone of these different yet available widgets and when and how to use
them. The slider widget we use in NiFi is the jquery UI
https://jqueryui.com/slider/. However, the processors on the canvas are
custom visualizations (svg) drawn with D3 so the jquery UI slider will not
work in this case.

There is currently no documentation around when to use which design system
nor any documentation around adding custom controls to a processor but this
could certainly be something we can try to add some documentation around to
provide guidance to UI/UX contributors.

On Fri, Feb 23, 2018 at 8:42 AM, Joe Witt  wrote:

> MikeT
>
> Not disagreeing with your point about the UX/sliders for the case you
> mention - that would be cool - but as a heads up you can do what you
> describe today with RouteOnAttribute and specifying EL statements to
> cover the flowfile size ranges - would work pretty nicely.
>
> Thanks
>
> On Fri, Feb 23, 2018 at 8:41 AM, Mike Thomsen 
> wrote:
> > Scott,
> >
> > Where does the UI/documentation stand on adding custom controls to
> > processors? That's a feature that I could see being really useful. An
> > example is a processor I've thought about writing called
> > RouteOnFlowfileSize that would let users define relationships based on
> > flowfile size ranges. Having sliders would be critical to making that
> > user-friendly.
> >
> > On Fri, Feb 23, 2018 at 8:28 AM, Scott Aslan 
> wrote:
> >
> >> Mike Thomsen,
> >>
> >> The Ui is being standardized on Angular. NiFi is currently running
> >> AngularJS v1.5.11 while NiFi Registry is running Angular v4.4.6.
> >>
> >> On Fri, Feb 23, 2018 at 8:23 AM, Scott Aslan 
> >> wrote:
> >>
> >> > Micheal M.,
> >> >
> >> > A *Design System* is a collection of utilities, components, and
> >> > guidelines which define the overall structure and experience of an
> >> > application(s). Fluid is the name of this design system.
> >> >
> >> >
> >> >
> >> > On Thu, Feb 22, 2018 at 1:44 PM, Michael Moser 
> >> wrote:
> >> >
> >> >>  There are compelling pros and easily identifiable cons to placing UI
> >> >> components into their own project.  I don't have anything to add
> there.
> >> >>
> >> >> Please, however, consider a different name.  "Fluid Design System" is
> >> >> generic to the point of giving no cognitive clue about what it
> actually
> >> >> is.  And without that clue, it's no different than a shorter made-up
> >> word.
> >> >> Also, a quick Google search doesn't indicate that it's an industry
> >> >> accepted
> >> >> phrase that conveys meaning.
> >> >>
> >> >> Consider:
> >> >>
> >> >> Fluidifi
> >> >> NiFi Fluid UI
> >> >> NiFi UI Components
> >> >> NiFi FDS
> >> >>
> >> >> Thanks,
> >> >> -- Mike
> >> >>
> >> >>
> >> >> On Thu, Feb 22, 2018 at 1:43 PM, Scott Aslan 
> >> >> wrote:
> >> >>
> >> >> > Joe,
> >> >> >
> >> >> > Yes, extract out the FDS.
> >> >> >
> >> >> > As for a release schedule, I don't think there would need to be
> one.
> >> We
> >> >> > would put out new releases as needed for new features or
> components.
> >> >> These
> >> >> > releases would be totally independent of NiFi or NiFi Registry. The
> >> >> > intention with this project is to follow semantic versioning and
> avoid
> >> >> > making breaking changes so using this library in NiFi or the NiFi
> >> >> Registry
> >> >> > would be as simple as updating the version number in the
> package.json
> >> >> and
> >> >> > rebuilding the application.
> >> >> >
> >> >> > As for validation of releases I have a couple of ideas. I
> envisioned
> >> >> this
> >> >> > code base would follow a RTC paradigm and the initial release of

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Mike Thomsen,

The Ui is being standardized on Angular. NiFi is currently running
AngularJS v1.5.11 while NiFi Registry is running Angular v4.4.6.

On Fri, Feb 23, 2018 at 8:23 AM, Scott Aslan  wrote:

> Micheal M.,
>
> A *Design System* is a collection of utilities, components, and
> guidelines which define the overall structure and experience of an
> application(s). Fluid is the name of this design system.
>
>
>
> On Thu, Feb 22, 2018 at 1:44 PM, Michael Moser  wrote:
>
>>  There are compelling pros and easily identifiable cons to placing UI
>> components into their own project.  I don't have anything to add there.
>>
>> Please, however, consider a different name.  "Fluid Design System" is
>> generic to the point of giving no cognitive clue about what it actually
>> is.  And without that clue, it's no different than a shorter made-up word.
>> Also, a quick Google search doesn't indicate that it's an industry
>> accepted
>> phrase that conveys meaning.
>>
>> Consider:
>>
>> Fluidifi
>> NiFi Fluid UI
>> NiFi UI Components
>> NiFi FDS
>>
>> Thanks,
>> -- Mike
>>
>>
>> On Thu, Feb 22, 2018 at 1:43 PM, Scott Aslan 
>> wrote:
>>
>> > Joe,
>> >
>> > Yes, extract out the FDS.
>> >
>> > As for a release schedule, I don't think there would need to be one. We
>> > would put out new releases as needed for new features or components.
>> These
>> > releases would be totally independent of NiFi or NiFi Registry. The
>> > intention with this project is to follow semantic versioning and avoid
>> > making breaking changes so using this library in NiFi or the NiFi
>> Registry
>> > would be as simple as updating the version number in the package.json
>> and
>> > rebuilding the application.
>> >
>> > As for validation of releases I have a couple of ideas. I envisioned
>> this
>> > code base would follow a RTC paradigm and the initial release of this
>> FDS
>> > NgModule would include unit test coverage of all the existing
>> > features/components/utils. Any new features/components/utils would
>> require
>> > adequate test coverage before being merged to NiFi FDS master. We could
>> > also provide a demo application that users can build and deploy locally
>> to
>> > allow for human verification or even e2e testing...
>> >
>> > I took the liberty of standing up a repo to give everyone a better idea
>> of
>> > what we are all talking about.
>> > https://github.com/scottyaslan/fluid-design-system
>> >
>> > Since no server or backend is required to run these UI/UX components I
>> also
>> > stood a demo of this as a github.io page here:
>> > https://scottyaslan.github.io/fluid-design-system/
>> > <https://scottyaslan.github.io/fluid-design-system/>
>> >
>> > -Scotty
>> >
>> > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt  wrote:
>> >
>> > > Scott
>> > >
>> > > Ok so extract out the fluid design work you started with NiFi Registry
>> > > to its own codebase which can be rev'd and published to NPM making it
>> > > easier to consume/reuse across NiFi projects and offers better
>> > > consistency.  This sounds interesting.
>> > >
>> > > In thinking through the additional community effort or the effort
>> > > trade-off:
>> > > How often do you anticipate we'd be doing releases (and thus
>> > > validation/voting) for this?
>> > > How often would those differ from when we'd want to do a NiFi or NiFi
>> > > Registry release?
>> > > How do you envision the community would be able to help vet/validate
>> > > releases of these modules?
>> > >
>> > > Thanks
>> > > Joe
>> > >
>> > > On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan 
>> > > wrote:
>> > > > NiFi Community,
>> > > >
>> > > > I'd like to initiate a discussion around creating a sub-project of
>> NiFi
>> > > to
>> > > > encompass the Fluid Design System NgModule created during the
>> > development
>> > > > of the NiFi Registry. A possible name for this sub-project is simply
>> > > > "NiFi Fluid
>> > > > Design System". The idea would be to create a sub-project that
>> > > distributes
>> > > > an atomic set of high quality, reuse-able, theme-able, and testable
>> > UI/UX
>> > > > components, fonts, and other JS modules for use across the various
>> web
>> > > > applications throughout the NiFi universe (uNiFiverse???). Both NiFi
>> > and
>> > > > NiFi Registry web applications would eventually leverage this module
>> > via
>> > > > npm. This approach will enable us to provide our users with a
>> > consistent
>> > > > experience across web applications. Creating a sub-project would
>> also
>> > > allow
>> > > > the FDS code to evolve independently of NiFi/NiFi registry and be
>> > > released
>> > > > on it's own timeline. In addition, it would make tracking
>> issues/work
>> > > much
>> > > > clearer through a separate JIRA.
>> > > >
>> > > > Please discuss and provide and thoughts or feedback.
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Scotty
>> > >
>> >
>>
>
>

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Micheal M.,

A *Design System* is a collection of utilities, components, and guidelines
which define the overall structure and experience of an application(s).
Fluid is the name of this design system.



On Thu, Feb 22, 2018 at 1:44 PM, Michael Moser  wrote:

>  There are compelling pros and easily identifiable cons to placing UI
> components into their own project.  I don't have anything to add there.
>
> Please, however, consider a different name.  "Fluid Design System" is
> generic to the point of giving no cognitive clue about what it actually
> is.  And without that clue, it's no different than a shorter made-up word.
> Also, a quick Google search doesn't indicate that it's an industry accepted
> phrase that conveys meaning.
>
> Consider:
>
> Fluidifi
> NiFi Fluid UI
> NiFi UI Components
> NiFi FDS
>
> Thanks,
> -- Mike
>
>
> On Thu, Feb 22, 2018 at 1:43 PM, Scott Aslan 
> wrote:
>
> > Joe,
> >
> > Yes, extract out the FDS.
> >
> > As for a release schedule, I don't think there would need to be one. We
> > would put out new releases as needed for new features or components.
> These
> > releases would be totally independent of NiFi or NiFi Registry. The
> > intention with this project is to follow semantic versioning and avoid
> > making breaking changes so using this library in NiFi or the NiFi
> Registry
> > would be as simple as updating the version number in the package.json and
> > rebuilding the application.
> >
> > As for validation of releases I have a couple of ideas. I envisioned this
> > code base would follow a RTC paradigm and the initial release of this FDS
> > NgModule would include unit test coverage of all the existing
> > features/components/utils. Any new features/components/utils would
> require
> > adequate test coverage before being merged to NiFi FDS master. We could
> > also provide a demo application that users can build and deploy locally
> to
> > allow for human verification or even e2e testing...
> >
> > I took the liberty of standing up a repo to give everyone a better idea
> of
> > what we are all talking about.
> > https://github.com/scottyaslan/fluid-design-system
> >
> > Since no server or backend is required to run these UI/UX components I
> also
> > stood a demo of this as a github.io page here:
> > https://scottyaslan.github.io/fluid-design-system/
> > <https://scottyaslan.github.io/fluid-design-system/>
> >
> > -Scotty
> >
> > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt  wrote:
> >
> > > Scott
> > >
> > > Ok so extract out the fluid design work you started with NiFi Registry
> > > to its own codebase which can be rev'd and published to NPM making it
> > > easier to consume/reuse across NiFi projects and offers better
> > > consistency.  This sounds interesting.
> > >
> > > In thinking through the additional community effort or the effort
> > > trade-off:
> > > How often do you anticipate we'd be doing releases (and thus
> > > validation/voting) for this?
> > > How often would those differ from when we'd want to do a NiFi or NiFi
> > > Registry release?
> > > How do you envision the community would be able to help vet/validate
> > > releases of these modules?
> > >
> > > Thanks
> > > Joe
> > >
> > > On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan 
> > > wrote:
> > > > NiFi Community,
> > > >
> > > > I'd like to initiate a discussion around creating a sub-project of
> NiFi
> > > to
> > > > encompass the Fluid Design System NgModule created during the
> > development
> > > > of the NiFi Registry. A possible name for this sub-project is simply
> > > > "NiFi Fluid
> > > > Design System". The idea would be to create a sub-project that
> > > distributes
> > > > an atomic set of high quality, reuse-able, theme-able, and testable
> > UI/UX
> > > > components, fonts, and other JS modules for use across the various
> web
> > > > applications throughout the NiFi universe (uNiFiverse???). Both NiFi
> > and
> > > > NiFi Registry web applications would eventually leverage this module
> > via
> > > > npm. This approach will enable us to provide our users with a
> > consistent
> > > > experience across web applications. Creating a sub-project would also
> > > allow
> > > > the FDS code to evolve independently of NiFi/NiFi registry and be
> > > released
> > > > on it's own timeline. In addition, it would make tracking issues/work
> > > much
> > > > clearer through a separate JIRA.
> > > >
> > > > Please discuss and provide and thoughts or feedback.
> > > >
> > > > Thanks,
> > > >
> > > > Scotty
> > >
> >
>

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Sivaprasanna,

I am not sure I follow exactly what you are saying...

NiFi Registry would no longer continue to host a copy of the FDS NgModule.
Instead, NiFi Registry would just add the NiFi FDS sub-project as a client
side dependency in its package.json. This would be analogous to how NiFi
Registry depends on Angular Material, etc. npm supports the ability to
download published packages which are current with the latest stable
release of a package. npm *also* supports the ability to develop off
of the *master
branch (or any other branch really)* of the NiFi FDS. An example of this
can be found in the github.io demo here
<https://github.com/scottyaslan/fluid-design-system/blob/gh-pages/package.json#L45>
. By placing that dependency in the package.json for the NiFi Registry each
subsequent clean build would automatically download the latest master
branch of the NiFi FDS sub-project and developers can leverages the latest
NiFi FDS components.

This also brings up a good point about release management. I have also
included a prototype of one possible implementation of automating the
tagging of a branch and automatically updating release version numbers etc.
leveraging grunt-bump [1]. The FDS-0.0.1-RC.0 tag [2] was created with the
described grunt task.

[1]
https://github.com/scottyaslan/fluid-design-system/blob/master/Gruntfile.js#L47

[2] https://github.com/scottyaslan/fluid-design-system/tree/FDS-0.0.1-RC.0

On Thu, Feb 22, 2018 at 12:39 PM, Sivaprasanna 
wrote:

> I agree with Matt. With clear documentation and guides, contributions on
> the sub-projects can be streamlined and be ensured that the necessary
> changes are already available on the core project i.e NiFi. One challenge
> is that the committer of the sub-project should have the courtesy to check
> wether the supporting changes are made available to the core project and
> track its status but given how contributions are being handled in
> nifi-registry project, I don’t think it’s going to be that much of a
> headache.
>
> We could also add to the helper doc mentioning that if the contribution is
> going to affect a core component, the contributor needs to add the JIRA id
> of the core project’s supporting changes in the sub-projects’ issue
> description.
>
> On Thu, 22 Feb 2018 at 10:42 PM, Matt Gilman 
> wrote:
>
> > Joe, Joe,
> >
> > Regarding the release process... I think it could be similar to how folks
> > verified and validated the NiFi Registry release. Guidance was given in a
> > helper guide regarding how to obtain/build a branch or PR that references
> > the new components. For the Registry release, there was a PR for NiFi
> that
> > had the supporting changes already available.
> >
> > We may have this issue any time we release new versions that depend on
> > another (sub)project.
> >
> > Matt
> >
> > On Thu, Feb 22, 2018 at 11:39 AM, Joe Percivall 
> > wrote:
> >
> > > Scott,
> > >
> > > Definitely like the direction of standardizing NiFi and Registry around
> > the
> > > same set of components, so the user has a common UX. Is there precedent
> > for
> > > creating a new sub-project just for common components/modules to be
> used
> > by
> > > the top-level, and it's other sub-projects? My concerns are similar to
> > > Joe's. Along those lines, if the core problems we're trying to address
> is
> > > the release process and distribution, is there a less "heavy-weight"
> > > avenue?
> > >
> > > In the past, we've also talked about pulling out the core NiFi
> framework
> > to
> > > be shared between NiFi and MiNiFi-Java for similar reasons. How we go
> > about
> > > solving this for the UI could be used a model for the core framework as
> > > well.
> > >
> > > - Joe
> > >
> > > On Thu, Feb 22, 2018 at 10:58 AM, Mike Thomsen  >
> > > wrote:
> > >
> > > > Also, what sort of framework is the UI being standardized on?
> Angular?
> > > > React? Something else?
> > > >
> > > > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt 
> wrote:
> > > >
> > > > > Scott
> > > > >
> > > > > Ok so extract out the fluid design work you started with NiFi
> > Registry
> > > > > to its own codebase which can be rev'd and published to NPM making
> it
> > > > > easier to consume/reuse across NiFi projects and offers better
> > > > > consistency.  This sounds interesting.
> > > > >
> > > > > In thinking through the additional community effort or the effort
> >

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Joe P,

Apache Cordova has a sub-project that is used by the top-level and other
sub-projects: https://github.com/apache/cordova-lib

-Scotty

On Thu, Feb 22, 2018 at 11:39 AM, Joe Percivall 
wrote:

> Scott,
>
> Definitely like the direction of standardizing NiFi and Registry around the
> same set of components, so the user has a common UX. Is there precedent for
> creating a new sub-project just for common components/modules to be used by
> the top-level, and it's other sub-projects? My concerns are similar to
> Joe's. Along those lines, if the core problems we're trying to address is
> the release process and distribution, is there a less "heavy-weight"
> avenue?
>
> In the past, we've also talked about pulling out the core NiFi framework to
> be shared between NiFi and MiNiFi-Java for similar reasons. How we go about
> solving this for the UI could be used a model for the core framework as
> well.
>
> - Joe
>
> On Thu, Feb 22, 2018 at 10:58 AM, Mike Thomsen 
> wrote:
>
> > Also, what sort of framework is the UI being standardized on? Angular?
> > React? Something else?
> >
> > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt  wrote:
> >
> > > Scott
> > >
> > > Ok so extract out the fluid design work you started with NiFi Registry
> > > to its own codebase which can be rev'd and published to NPM making it
> > > easier to consume/reuse across NiFi projects and offers better
> > > consistency.  This sounds interesting.
> > >
> > > In thinking through the additional community effort or the effort
> > > trade-off:
> > > How often do you anticipate we'd be doing releases (and thus
> > > validation/voting) for this?
> > > How often would those differ from when we'd want to do a NiFi or NiFi
> > > Registry release?
> > > How do you envision the community would be able to help vet/validate
> > > releases of these modules?
> > >
> > > Thanks
> > > Joe
> > >
> > > On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan 
> > > wrote:
> > > > NiFi Community,
> > > >
> > > > I'd like to initiate a discussion around creating a sub-project of
> NiFi
> > > to
> > > > encompass the Fluid Design System NgModule created during the
> > development
> > > > of the NiFi Registry. A possible name for this sub-project is simply
> > > > "NiFi Fluid
> > > > Design System". The idea would be to create a sub-project that
> > > distributes
> > > > an atomic set of high quality, reuse-able, theme-able, and testable
> > UI/UX
> > > > components, fonts, and other JS modules for use across the various
> web
> > > > applications throughout the NiFi universe (uNiFiverse???). Both NiFi
> > and
> > > > NiFi Registry web applications would eventually leverage this module
> > via
> > > > npm. This approach will enable us to provide our users with a
> > consistent
> > > > experience across web applications. Creating a sub-project would also
> > > allow
> > > > the FDS code to evolve independently of NiFi/NiFi registry and be
> > > released
> > > > on it's own timeline. In addition, it would make tracking issues/work
> > > much
> > > > clearer through a separate JIRA.
> > > >
> > > > Please discuss and provide and thoughts or feedback.
> > > >
> > > > Thanks,
> > > >
> > > > Scotty
> > >
> >
>
>
>
> --
> *Joe Percivall*
> linkedin.com/in/Percivall
> e: jperciv...@apache.com
>

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

Joe,

Yes, extract out the FDS.

As for a release schedule, I don't think there would need to be one. We
would put out new releases as needed for new features or components. These
releases would be totally independent of NiFi or NiFi Registry. The
intention with this project is to follow semantic versioning and avoid
making breaking changes so using this library in NiFi or the NiFi Registry
would be as simple as updating the version number in the package.json and
rebuilding the application.

As for validation of releases I have a couple of ideas. I envisioned this
code base would follow a RTC paradigm and the initial release of this FDS
NgModule would include unit test coverage of all the existing
features/components/utils. Any new features/components/utils would require
adequate test coverage before being merged to NiFi FDS master. We could
also provide a demo application that users can build and deploy locally to
allow for human verification or even e2e testing...

I took the liberty of standing up a repo to give everyone a better idea of
what we are all talking about.
https://github.com/scottyaslan/fluid-design-system

Since no server or backend is required to run these UI/UX components I also
stood a demo of this as a github.io page here:
https://scottyaslan.github.io/fluid-design-system/
<https://scottyaslan.github.io/fluid-design-system/>

-Scotty

On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt  wrote:

> Scott
>
> Ok so extract out the fluid design work you started with NiFi Registry
> to its own codebase which can be rev'd and published to NPM making it
> easier to consume/reuse across NiFi projects and offers better
> consistency.  This sounds interesting.
>
> In thinking through the additional community effort or the effort
> trade-off:
> How often do you anticipate we'd be doing releases (and thus
> validation/voting) for this?
> How often would those differ from when we'd want to do a NiFi or NiFi
> Registry release?
> How do you envision the community would be able to help vet/validate
> releases of these modules?
>
> Thanks
> Joe
>
> On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan 
> wrote:
> > NiFi Community,
> >
> > I'd like to initiate a discussion around creating a sub-project of NiFi
> to
> > encompass the Fluid Design System NgModule created during the development
> > of the NiFi Registry. A possible name for this sub-project is simply
> > "NiFi Fluid
> > Design System". The idea would be to create a sub-project that
> distributes
> > an atomic set of high quality, reuse-able, theme-able, and testable UI/UX
> > components, fonts, and other JS modules for use across the various web
> > applications throughout the NiFi universe (uNiFiverse???). Both NiFi and
> > NiFi Registry web applications would eventually leverage this module via
> > npm. This approach will enable us to provide our users with a consistent
> > experience across web applications. Creating a sub-project would also
> allow
> > the FDS code to evolve independently of NiFi/NiFi registry and be
> released
> > on it's own timeline. In addition, it would make tracking issues/work
> much
> > clearer through a separate JIRA.
> >
> > Please discuss and provide and thoughts or feedback.
> >
> > Thanks,
> >
> > Scotty
>

[DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Scott Aslan]

NiFi Community,

I'd like to initiate a discussion around creating a sub-project of NiFi to
encompass the Fluid Design System NgModule created during the development
of the NiFi Registry. A possible name for this sub-project is simply
"NiFi Fluid
Design System". The idea would be to create a sub-project that distributes
an atomic set of high quality, reuse-able, theme-able, and testable UI/UX
components, fonts, and other JS modules for use across the various web
applications throughout the NiFi universe (uNiFiverse???). Both NiFi and
NiFi Registry web applications would eventually leverage this module via
npm. This approach will enable us to provide our users with a consistent
experience across web applications. Creating a sub-project would also allow
the FDS code to evolve independently of NiFi/NiFi registry and be released
on it's own timeline. In addition, it would make tracking issues/work much
clearer through a separate JIRA.

Please discuss and provide and thoughts or feedback.

Thanks,

Scotty

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

[Scott Aslan]

+1 (binding)

Ran through release helper with no issues
Started NiFi and configured a NiFi Registry Client
Performed SDLC functionalities on PG's

On Wed, Jan 10, 2018 at 11:13 AM, Chris Herrera 
wrote:

> +1 (non-binding)
>
> Built with contrib-check
> Verified keys and hashes
>
> Ran through several flows in an oidc secured environment including several
> custom processors. All seems working.
>
> Looks like a great release. Thanks guys!
>
> Regards,
> Chris
>
> On Jan 10, 2018, 9:37 AM -0600, Jeff Zemerick ,
> wrote:
> > +1 non-binding
> >
> > Built with contrib-check.
> > Stepped through release guide.
> >
> > Ran into a minor issue with the TestListenSMTP unit tests on OSX but it
> > might be pretty specific to my computer.
> >
> > https://issues.apache.org/jira/browse/NIFI-4760
> >
> >
> > On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard <
> > pierre.villard...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Went through release helper guide and all looks good to me.
> > > Tested integration with a running registry instance.
> > > Ran some test workflows in a secured env and tested recent fixed about
> > > authorizers.
> > >
> > > Thanks for taking care of the release Joe!
> > > Great job from all the community around this release! Integration with
> the
> > > registry is neat.
> > >
> > > Pierre
> > >
> > >
> > >
> > > 2018-01-10 16:16 GMT+01:00 Bryan Bende :
> > >
> > > > +1 (binding)
> > > >
> > > > - Ran through release helper with no issues
> > > > - Ran into a minor issue related to component versioning when using
> > > > the registry and created this JIRA [1], would be more of an issue for
> > > > next release
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-4763
> > > >
> > > >
> > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess  > > > wrote:
> > > > > +1 (binding), ran through release guide with no issues (verified
> sigs
> > > > > & sums), ran various flows using record processors, the new Jackson
> > > > > CSV parser, provenance reporting task with new filtering capability
> > > > > and output fields, etc.
> > > > >
> > > > > On Tue, 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: 40b155c4911414907835f2eb0d5a4d
> a798935f27f1e5134218d904fe6c94
> > > > 2d13
> > > > > >
> > > > > > 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&version=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...
> > > >
> > >
>

Re: [ANNOUNCE] New Apache NiFi Committer Kevin Doran

[Scott Aslan]

Congrats Kevin! Well deserved!

On Wed, Jan 3, 2018 at 9:45 AM, Matt Burgess  wrote:

> Congrats and welcome aboard Kevin!
>
> On Wed, Jan 3, 2018 at 9:17 AM, Bryan Bende  wrote:
> > On behalf of the Apache NiFi PMC, I am very pleased to announce that
> > Kevin Doran has accepted the PMC's invitation to become a committer on
> > the Apache NiFi project. We greatly appreciate all of Kevin's hard
> > work and generous contributions to the project. We look forward to his
> > continued involvement in the project.
> >
> > Kevin has made significant contributions to the NiFi Registry project,
> > especially around setting up the security model & REST APIs, and was a
> > major contributor to getting the first release out. You also may have
> > interacted with him on the mailing lists already, as he is always
> > willing to dig into questions/issues and help out.
> >
> > Welcome and congratulations!
>

Re: [VOTE] Release Apache NiFi Registry 0.1.0

[Scott Aslan]

+1 (binding), Ran through the release helper. verified hashed, LICENSE,
NOTICE, and README.

Tests
- setup kerberos based secure reg setup/test with Nifi
- attempted to reproduce the npm issue, all looks well (Aldrin, I am
curious as to what caused npm to fail? any other info? maybe some other
software installed on your machine is causing conflicts?)


On Sat, Dec 30, 2017 at 6:16 PM, James Wing  wrote:

> +1 (binding).  Ran through the release helper, verified hashes, LICENSE,
> NOTICE, and README.  Built the source and performed light testing of the
> resulting binary.
>
> On Thu, Dec 28, 2017 at 10:09 AM, Bryan Bende  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> > 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 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-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [ANNOUNCE] New NiFi PMC member Marc Parisi

[Scott Aslan]

Congrats!

On Thu, Dec 14, 2017 at 6:50 PM, Matt Burgess  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
>

Re: [ANNOUNCE] New NiFi PMC member Jeff Storck

[Scott Aslan]

Congrats!

On Tue, Dec 5, 2017 at 12:16 PM, Matt Gilman 
wrote:

> Congrats Jeff!
>
> On Tue, Dec 5, 2017 at 12:14 PM, Kevin Doran 
> wrote:
>
> > Congrats, Jeff!
> >
> > On 12/5/17, 11:49, "Tony Kurc"  wrote:
> >
> > NiFi community,
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Jeff
> > Storck
> > has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> > greatly
> > appreciate all of Jeff's hard work and generous contributions to the
> > project. We look forward to continued involvement in the project.
> >
> > For those of you enjoying NiFi 1.4.0 release, Jeff was the release
> > manager,
> > which is a huge complicated set of work. He's also been a long time
> > contributor, committer, and a strong member of the community.
> >
> > Congratulations and welcome, Jeff!
> >
> > Tony
> >
> >
> >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[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<https://aka.ms/o0ukef>
> >> 
> >> 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
> >>>
> >>
>

Re: [ANNOUNCE] New NiFi PMC member Mike Moser

[Scott Aslan]

Congrats!

On Mon, Nov 20, 2017 at 4:25 PM, Juan Sequeiros  wrote:

> Mike this is awesome. Congrats and thanks.
>
> On Mon, Nov 20, 2017 at 4:20 PM Joe Witt  wrote:
>
> > Congrats Mike!  Thanks for all your efforts
> >
> > On Mon, Nov 20, 2017 at 4:18 PM, Tony Kurc  wrote:
> > > NiFi community,
> > > On behalf of the Apache NiFi PMC, I am pleased to announce that Mike
> > Moser
> > > has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> > greatly
> > > appreciate all of Mike's hard work and generous contributions to the
> > > project. We look forward to continued involvement in the project.
> > >
> > > Mike has been a long time code contributor to NiFi, he performed the
> > final
> > > release management duties for the 0.x line, has been involved with
> > > verifying releases and always a delight on the mailing lists.
> > >
> > > Please join us in congratulating and welcoming Mike to the Apache NiFi
> > PMC.
> > >
> > > Congratulations and welcome, Mike!
> > >
> > > -- Tony
> >
>

Re: Automated Testing of Flows

[Scott Aslan]

Just brain storming here

You could use travis or Jenkins to setup a job where you use mvn and npm to
build and start NiFi. Assuming the test template was available from within
the environment maybe you could use the protractor e2e testing suite to
script the clicks necessary to load the template and run the flow...

On Wed, Nov 15, 2017 at 8:07 PM, Peter Wicks (pwicks) 
wrote:

> I would like to find a way to automatically run integration/upgrade tests
> on flows, rather than just one or two processors like the mock framework
> supports. Preferably something Template driven, where I can provide a
> template xml file, and an accompanying config file to setup the test, then
> run the flow and examine the results.
>
> Has anyone worked on something like this?
>

Re: [ANNOUNCE] New Apache NiFi Committer Andy Christianson

[Scott Aslan]

Congrats

On Tue, Nov 14, 2017 at 8:11 AM, Marc  wrote:

> Congrats
>
> On Nov 14, 2017 1:29 AM, "Pierre Villard" 
> wrote:
>
> Congrats!
>
> Le 14 nov. 2017 04:16, "Jeff"  a écrit :
>
> > Congrats, Andy!
> >
> > On Mon, Nov 13, 2017 at 9:44 PM Kevin Doran 
> > wrote:
> >
> > > Congrats, Andy! Thanks for all the hard work on MiNiFi CPP!
> > >
> > > On 11/13/17, 19:39, "Tony Kurc"  wrote:
> > >
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce
> that
> > > Andy
> > > has accepted the PMC's invitation to become a committer on the
> Apache
> > > NiFi
> > > project. We greatly appreciate all of Andy's hard work and generous
> > > contributions to the project. We look forward to his continued
> > > involvement
> > > in the project.
> > >
> > > In addition to contributing significant code to MiNiFi CPP, Andy
> has
> > > been
> > > leading discussions and been the focal point for several major
> > > improvements. His engagement with the community has been top notch,
> > and
> > > we're excited he accepted the PMC's invitation.
> > >
> > > Andy, Welcome and congratulations!
> > > Tony
> > >
> > >
> > >
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Mike Hogue

[Scott Aslan]

Congrats!

On Fri, Nov 10, 2017 at 3:22 AM, Pierre Villard  wrote:

> Congrats Mike, welcome on board!
>
> 2017-11-10 5:27 GMT+01:00 Jeff :
>
> > Congrats, Mike!
> >
> > On Thu, Nov 9, 2017 at 7:19 PM Jeremy Dyer  wrote:
> >
> > > Mike glad to have you and looking forward to working with you on things
> > in
> > > the future!
> > >
> > > On Thu, Nov 9, 2017 at 7:14 PM, Tony Kurc  wrote:
> > >
> > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Mike
> > > > Hogue has accepted the PMC's invitation to become a committer on the
> > > Apache
> > > > NiFi project. We greatly appreciate all of Mike's hard work and
> > generous
> > > > contributions to the project. We look forward to his continued
> > > involvement
> > > > in the project.
> > > >
> > > > In the past several months, Mike has contributed on a number of
> fronts.
> > > He
> > > > was primary author on several new features in 1.4.0 to include the
> gRPC
> > > > bundle. He also improved SSL/TLS controller services, and made great
> > > > documentation improvements on LICENSE and NOTICE best practices and
> has
> > > > helped work down our pull request backlog by reviewing new
> > contributions.
> > > >
> > > > Welcome and congratulations!
> > > >
> > > > Tony
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Peter Wicks

[Scott Aslan]

Congrats!

On Fri, Nov 10, 2017 at 3:21 AM, Pierre Villard  wrote:

> Congrats Peter, well deserved!
>
> 2017-11-10 5:26 GMT+01:00 Jeff :
>
> > Congrats, Peter!
> >
> > On Thu, Nov 9, 2017 at 7:18 PM Jeremy Dyer  wrote:
> >
> > > Welcome Peter excited to have you on board!
> > >
> > > On Thu, Nov 9, 2017 at 7:14 PM, Tony Kurc  wrote:
> > >
> > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > > Peter
> > > > Wicks has accepted the PMC's invitation to become a committer on the
> > > Apache
> > > > NiFi project. We greatly appreciate all of Peter's hard work and
> > generous
> > > > contributions to the project. We look forward to his continued
> > > involvement
> > > > in the project.
> > > >
> > > > Peter has been contributing for over a year. Many of you have
> benefited
> > > > from useful improvements and new features centered mainly around
> > > databases
> > > > and record-based processors. I'm sure many of you have had the
> pleasure
> > > of
> > > > interacting with him on the mailing lists, as he's always been
> willing
> > to
> > > > pitch in and make the Apache NiFi community stronger.
> > > >
> > > > Welcome and congratulations!
> > > >
> > > > Tony
> > > >
> > >
> >
>

Re: [VOTE] Release Apache NiFi 1.4.0 (RC2)

[Scott Aslan]

+1 (non-binding) Release this package as nifi-1.4.0

On Fri, Sep 29, 2017 at 11:52 AM, Mark Payne  wrote:

> +1 (binding)
>
> Verified hashes and checksum. Built with all unit tests and contrib-check
> on OSX.
>
> Was able to startup and test simple flows worked as expected.
>
> > On Sep 29, 2017, at 11:20 AM, Marc P.  wrote:
> >
> > +1 non-binding
> >
> >  -- verified contrib-check
> >  -- ran simple flows with MiNiFi
> >  -- sigs and hashes look good.
> >
> >  Thanks for sending this out Jeff!
> >
> >
> > On Fri, Sep 29, 2017 at 11:18 AM, Matt Gilman 
> > wrote:
> >
> >> +1 (binding) Release this package as nifi-1.4.0
> >>
> >> On Fri, Sep 29, 2017 at 11:07 AM, Bryan Bende  wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> - Ran through the release helper and everything checked out.
> >>> - Ran a couple of sample flows with no issues
> >>>
> >>>
> >>> On Fri, Sep 29, 2017 at 9:46 AM, James Wing  wrote:
>  Jeff, I agree the updated KEYS file has been published.  Thanks.
> 
>  On Fri, Sep 29, 2017 at 6:00 AM, Jeff  wrote:
> 
> > James,
> >
> > I had to do a hard reload of the page in Chrome, since the browser
> >> kept
> > showing me a cached version without my key.  After the hard reload, I
> >>> can
> > see my key at https://dist.apache.org/repos/dist/dev/nifi/KEYS.
> >> Could
> >>> you
> > try opening the KEYS link in incognito mode and verify that my key is
> > there?
> >
> > Thanks,
> > Jeff
> >
> > On Fri, Sep 29, 2017 at 1:06 AM James Wing  wrote:
> >
> >> +1 (binding). I ran through the release helper including signature,
> > hashes,
> >> build, and testing the binary.  I checked the LICENSE and NOTICE
> >>> files.
> >> Everything looks good to me.
> >>
> >> One thing I noted is that Jeff's GPG key is not yet in the public
> >> KEYS
> > file
> >> at https://dist.apache.org/repos/dist/dev/nifi/KEYS, but it is
> >> added
> >>> in
> >> the
> >> master branch KEYS file to be published with the release.  I believe
> >>> that
> >> is OK for the signature, we've done this before, and perhaps we
> >> should
> >> consider changing the helper text in the future.
> >>
> >> Thanks, Jeff, for putting this release together.
> >>
> >>
> >> On Thu, Sep 28, 2017 at 12:54 PM, Jeff  wrote:
> >>
> >>> Hello,
> >>>
> >>> I am pleased to be calling this vote for the source release of
> >>> Apache
> >> NiFi
> >>> nifi-1.4.0.
> >>>
> >>> The source zip, including signatures, digests, etc. can be found
> >> at:
> >>> https://repository.apache.org/content/repositories/
> >>> orgapachenifi-
> >>>
> >>> The Git tag is nifi-1.4.0-RC2
> >>> The Git commit ID is e6508ba7d3da5bba54abd6233a7a8f9dd4c32151
> >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> >>> e6508ba7d3da5bba54abd6233a7a8f9dd4c32151
> >>>
> >>> Checksums of nifi-1.4.0-source-release.zip:
> >>> MD5: 41e4083e602883a3e180032f32913414
> >>> SHA1: 26770625138126f45bed4989adb0a6b65a767aa2
> >>>
> >>> Release artifacts are signed with the following key:
> >>> https://people.apache.org/keys/committer/jstorck.asc
> >>>
> >>> KEYS file available here:
> >>> https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>>
> >>> 199 issues were closed/resolved for this release:
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> projectId=12316020&version=12340589
> >>>
> >>> Release note highlights can be found here:
> >>> https://cwiki.apache.org/confluence/display/NIFI/
> >>> Release+Notes#ReleaseNotes-Version-1.4.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.4.0
> >>> [ ] +0 no opinion
> >>> [ ] -1 Do not release this package because...
> >>>
> >>
> >
> >>>
> >>
>
>

Re: [VOTE] Release Apache NiFi 0.7.4

[Scott Aslan]

+1 (non-binding)

- Verified signatures, checksums, LICENSE, NOTICE, and README
- Built using a full clean build with contrib check successfully on OSX
- Run example data flows on OS X with Chrome Version 58.0.3029.110 (64-bit)
 on unsecured instance
- Run example data flows on OS X with Chrome Version 58.0.3029.110 (64-bit) on
secured instance

On Tue, Jun 6, 2017 at 1:17 PM, Pierre Villard 
wrote:

> +1 (binding)
> Release this package as nifi-0.7.4
>
> - Ran through release helper, all looks good (build on OSX)
> - Basic workflows running as expected
>
>
> 2017-06-06 17:44 GMT+02:00 Bryan Bende :
>
> > +1 (binding) Release this package as nifi-0.7.4
> >
> > - Ran through release helper and everything checked out
> > - Ran basic flow to test that binary works
> >
> > Minor note - The years in the NOTICE files still say 2014-2016.
> >
> >
> > On Tue, Jun 6, 2017 at 11:30 AM, Joe Skora  wrote:
> > > +1 (binding)
> > >
> > > * Verified GPG signature.
> > > * Verified hashes.
> > > * Built source with contrib-check profile.
> > > * Verified README, NOTICE, and LICENSE.
> > > * Verified commit ID.
> > > * Verified RC was branched from "support/nifi-0.7.x".
> > > * Ran binary and tested basic functionality.
> > >
> > > On Mon, Jun 5, 2017 at 9:29 PM, Koji Kawamura 
> > > wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> Verified gpg signature.
> > >> Verified all hashes on source zipfile.
> > >> Performed mvn clean install -Pcontrib-checks
> > >> Builds cleanly, all tests pass on Mac OS Sierra (10.12.4)
> > >> Oracle JDK 1.8.0_121-b13, maven 3.2.5
> > >> Ran simple flow and worked as expected.
> > >>
> > >> Thanks,
> > >> Koji
> > >>
> > >> On Tue, Jun 6, 2017 at 7:31 AM, Adam Taft  wrote:
> > >> > +1 (binding)
> > >> >
> > >> > Verified gpg signature.
> > >> > Verified all hashes on source zipfile.
> > >> > Performed mvn clean install -Pcontrib-checks
> > >> > Builds cleanly, all tests pass in docker container centos:latest w/
> > >> > openjdk-1.8.0 and maven 3.5.0
> > >> > LICENSE, NOTICE, README look good.
> > >> > Binary runs as expected with a simple dataflow.
> > >> >
> > >> > Cheers,
> > >> >
> > >> > Adam
> > >> >
> > >>
> >
>

Re: [VOTE] Release Apache NiFi 1.3.0

[Scott Aslan]

+1 (non-binding)

- Verified signatures, checksums, LICENSE, NOTICE, and README
- Built using a full clean build with contrib check successfully on OSX
- Run example data flows on OS X with Chrome Version 58.0.3029.110 (64-bit)
 on unsecured instance
- Run example data flows on OS X with Chrome Version 58.0.3029.110 (64-bit) on
secured instance

On Tue, Jun 6, 2017 at 12:44 PM, Joe Skora  wrote:

> +1 (binding)
>
> * Verified GPG signature.
> * Verified hashes.
> * Built source with contrib-check profile.
> * Verified README, NOTICE, and LICENSE.
> * Verified commit ID.
> * Verified RC was branched from master.
> * Ran binary and tested basic functionality.
>
>
> On Tue, Jun 6, 2017 at 10:27 AM, Bryan Bende  wrote:
>
> > +1 (binding) Release this package as nifi-1.3.0
> >
> > - Ran through release helper and everything checked out
> > - Ran some test flows with HDFS processors and verified they worked
> > correctly
> >
> > On Tue, Jun 6, 2017 at 12:42 AM, James Wing  wrote:
> > > +1 (binding).  I ran through the release helper -- verified signature
> and
> > > hashes, ran the full build, checked readme, license, and notice in
> source
> > > and output.  I ran a simple flow and verified that it still works.
> > >
> > > Thanks for putting this release together, Matt.
> > >
> > > James
> > >
> > >
> > > On Mon, Jun 5, 2017 at 10:54 AM, Matt Gilman 
> > wrote:
> > >
> > >> Hello,
> > >>
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > >> nifi-1.3.0.
> > >>
> > >>
> > >> The source zip, including signatures, digests, etc. can be found at:
> > >>
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1108
> > >>
> > >>
> > >> The Git tag is nifi-1.3.0-RC1
> > >>
> > >> The Git commit ID is ddb73612bd1512d8b2151b81f9aa40811bca2aaa
> > >>
> > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > >> ddb73612bd1512d8b2151b81f9aa40811bca2aaa
> > >>
> > >>
> > >> Checksums of nifi-1.3.0-source-release.zip:
> > >>
> > >> MD5: 8b115682ac392342b9edff3bf0658ecb
> > >>
> > >> SHA1: f11cdebbabdc0d8f1f0dd4c5b880ded39d17f234
> > >>
> > >> SHA256: 9ba5565729d98c472c31a1fdbc44e9dc1eee87a2cf5184e8428743f75314
> > 5b7f
> > >>
> > >>
> > >> Release artifacts are signed with the following key:
> > >>
> > >> https://people.apache.org/keys/committer/mcgilman.asc
> > >>
> > >>
> > >> KEYS file available here:
> > >>
> > >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>
> > >>
> > >> 110 issues were closed/resolved for this release:
> > >>
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > >> projectId=12316020&version=12340498
> > >>
> > >>
> > >> Release note highlights can be found here:
> > >>
> > >> https://cwiki.apache.org/confluence/display/NIFI/
> > >> Release+Notes#ReleaseNotes-Version1.3.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.3.0
> > >>
> > >> [ ] +0 no opinion
> > >>
> > >> [ ] -1 Do not release this package because...
> > >>
> >
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi Committer Marc Parisi

[Scott Aslan]

Congrats Marc!

On Thu, Jun 1, 2017 at 8:39 AM, Marc  wrote:

> Thank you, everyone! Amazing to be part of such a cohesive and flourishing
> community.
>
> I look forward to contributing and working with all of you!
>
> On Thu, Jun 1, 2017 at 8:35 AM, Mark Payne  wrote:
>
> > Welcome, Marc! Happy to have you aboard!
> >
> > > On Jun 1, 2017, at 5:20 AM, Pierre Villard <
> pierre.villard...@gmail.com>
> > wrote:
> > >
> > > Congrats Marc!
> > >
> > > 2017-06-01 6:14 GMT+02:00 Andrew Lim :
> > >
> > >> Congrats Marc!
> > >>
> > >>
> > >>> On May 31, 2017, at 11:45 PM, Joe Percivall 
> > >> wrote:
> > >>>
> > >>> Congrats Marc, excited to see what else you can create for MiNiFi!
> > >>>
> > >>> On Wed, May 31, 2017 at 11:00 PM, Joe Witt 
> wrote:
> > >>>
> > >>>> Congrats and welcome.  Kevin said it very well so I'll simply +1
> that.
> > >>>>
> > >>>> On Wed, May 31, 2017 at 10:45 PM, Kevin Doran <
> > kdoran.apa...@gmail.com>
> > >>>> wrote:
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>   Congratulations, Marc! Very well deserved. Thanks for
> > >>>> your contributions and generosity with sharing your technical
> > knowledge.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>   _
> > >>>>> From: Jeremy Dyer 
> > >>>>> Sent: Wednesday, May 31, 2017 10:23 PM
> > >>>>> Subject: Re: [ANNOUNCE] New Apache NiFi Committer Marc Parisi
> > >>>>> To:  
> > >>>>>
> > >>>>>
> > >>>>> Congratulations Marc! Have really enjoyed working and learning from
> > you
> > >>>> on the C++ side of the house. Look forward to your further work!
> > >>>>>
> > >>>>> Sent from my iPhone
> > >>>>>
> > >>>>>> On May 31, 2017, at 9:37 PM, Tony Kurc  wrote:
> > >>>>>>
> > >>>>>> On behalf of the Apache NiFI PMC, I am very pleased to announce
> that
> > >>>> Marc
> > >>>>>> Parisi has accepted the PMC's invitation to become a committer on
> > the
> > >>>>>> Apache NiFi project. We greatly appreciate all of Marc's hard work
> > and
> > >>>>>> generous contributions to the project. We look forward to his
> > >> continued
> > >>>>>> involvement in the project.
> > >>>>>>
> > >>>>>> Marc has been contributing heavily to MiNiFi C++ for the past
> > several
> > >>>>>> months, really bringing energy to that piece of the project. He's
> > been
> > >>>>>> making heavy code contributions, and as many of you have
> discovered,
> > >>>> active
> > >>>>>> and helpful on the mailing lists and is a willing reviewer. Marc
> > also
> > >>>>>> brings with him experience with another Apache project, Accumulo,
> > >> where
> > >>>> he
> > >>>>>> is a committer and PMC member.
> > >>>>>>
> > >>>>>> Welcome and congratulations!
> > >>>>>>
> > >>>>>> Tony
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> *Joe Percivall*
> > >>> linkedin.com/in/Percivall
> > >>> e: jperciv...@apache.com
> > >>
> > >>
> >
> >
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi Committer Drew Lim

[Scott Aslan]

Congrats!

On Thu, Jun 1, 2017 at 8:35 AM, Mark Payne  wrote:

> Congrats and welcome Drew!
>
> > On Jun 1, 2017, at 12:22 AM, Andrew Lim 
> wrote:
> >
> > Thanks everyone!  Very grateful to be a part of this awesome project and
> community.
> >
> > -Drew
> >
> >
> >> On May 31, 2017, at 11:46 PM, Joe Percivall 
> wrote:
> >>
> >> Congrats Drew! Very well deserved, always appreciated all your work on
> >> documentation and QA
> >>
> >> On Wed, May 31, 2017 at 10:49 PM, Koji Kawamura  >
> >> wrote:
> >>
> >>> Congratulations Drew!!
> >>>
> >>> On Thu, Jun 1, 2017 at 11:47 AM, Yolanda Davis
> >>>  wrote:
> >>>>
> >>>> Congratulations Drew!
> >>>>
> >>>>
> >>>>> On May 31, 2017, at 4:20 PM, Bryan Rosander 
> >>> wrote:
> >>>>>
> >>>>> Congrats Drew!
> >>>>>
> >>>>> On Wed, May 31, 2017 at 3:51 PM, Andrew Psaltis <
> >>> psaltis.and...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Congrats Drew! I spend a lot of time teaching people about NiFi and
> can
> >>>>>> honestly say the documentation -- built-in and on the wiki is a
> great
> >>>>>> selling point. Thanks for all the hard work.
> >>>>>>
> >>>>>>> On Wed, May 31, 2017 at 3:08 PM, Tony Kurc 
> wrote:
> >>>>>>>
> >>>>>>> On behalf of the Apache NiFI PMC, I am very pleased to announce
> that
> >>> Drew
> >>>>>>> Lim has accepted the PMC's invitation to become a committer on the
> >>> Apache
> >>>>>>> NiFi project. We greatly appreciate all of Drew's hard work and
> >>> generous
> >>>>>>> contributions to the project. We look forward to his continued
> >>>>>> involvement
> >>>>>>> in the project.
> >>>>>>>
> >>>>>>> In my opinion, one of the strengths of NiFi is that someone can
> launch
> >>>>>> the
> >>>>>>> UI, do some light (often built-in) reading, and get started "making
> >>> data
> >>>>>>> flow" in a short amount of time. Drew has been instrumental in
> making
> >>>>>> this
> >>>>>>> happen, over the past year contributing to the wiki and making the
> >>>>>> built-in
> >>>>>>> documentation correct and approachable. We all know the Apache
> adage
> >>>>>>> "Community > Code", and Drew's contributions are key to ensuring
> the
> >>>>>> health
> >>>>>>> of the community.
> >>>>>>>
> >>>>>>> Welcome and congratulations!
> >>>>>>>
> >>>>>>> --Tony
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> 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>
> >>>>>>
> >>>
> >>
> >>
> >>
> >> --
> >> *Joe Percivall*
> >> linkedin.com/in/Percivall
> >> e: jperciv...@apache.com
> >
>
>


-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

[Scott Aslan]

Congrats Koji!

On Tue, May 30, 2017 at 8:44 AM, Jeff  wrote:

> Contrats, Koji!
>
> On Sun, May 28, 2017 at 12:33 PM Matt Burgess 
> wrote:
>
> > Congratulations and welcome aboard Koji! Looking forward to even more
> > great contributions and blogs/docs!
> >
> > On Fri, May 26, 2017 at 10:09 PM, Tony Kurc  wrote:
> > > On behalf of the Apache NiFi PMC, I am pleased to announce that Koji
> > > Kawamura has accepted the PMC's invitation to join the Apache NiFi PMC.
> > We
> > > greatly appreciate all of Koji's hard work and generous contributions
> to
> > > the project. We look forward to continued involvement in the project.
> > >
> > > Koji has been contributing code NiFi since 2015, taking point on
> > important
> > > parts of the project like improving site-to-site. Beyond code, Koji is
> > > active in building the community through blogging on technical topics,
> > > generating interest on social media (@apachenifi #NiFi) like twitter,
> and
> > > giving talks at conferences. Koji has been keeping the project strong
> by
> > > being active in reviewing new contributions and verifying releases.
> > >
> > > Please join us in congratulating and welcoming Koji to the Apache NiFi
> > PMC.
> > >
> > > Congratulations and welcome, Koji!
> > >
> > > -- Tony
> >
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi PMC Member - Pierre Villard

[Scott Aslan]

Congrats Pierre!!!


On Tue, May 23, 2017 at 3:44 PM, Matt Burgess  wrote:

> Congrats and welcome Pierre, very well deserved!!
>
> On Mon, May 22, 2017 at 3:17 PM, Tony Kurc  wrote:
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Pierre
> > Villard has accepted the PMC's invitation to join the Apache NiFi PMC.
> We
> > greatly appreciate all of Pierre's hard work and generous contributions
> to
> > the project. We look forward to continued involvement in the project.
> >
> > Pierre has been a long time code contributor to both NiFi and MiNiFi. In
> > addition to that, he's spurred the community through his blogging -
> > teaching people how to use, operate, and monitor NiFi. He's a prolific
> > reviewer of contributions, and active in the important task of verifying
> > releases.
> >
> > Please join us in congratulating and welcoming Pierre to the Apache NiFi
> > PMC.
> >
> > Congratulations and welcome, Pierre!
> >
> > -- Tony
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [VOTE] Release Apache NiFi MiNiFi 0.2.0

[Scott Aslan]

+1 (non-binding)

Release this package as minifi-0.2.0

Thanks!

On Wed, May 17, 2017 at 4:42 PM, Andrew Psaltis 
wrote:

> +1 (non-binding)
>
>
> Verified signatures
> Verified hashes
> Built cleanly using contrib check
> Built simple flow to communicate with NiFi 1.2
>
> converted flow with toolkit
> ran flow
>
> Verified flowStatus JSON
>
>
>
> On Wed, May 17, 2017 at 4:18 PM, Tony Kurc  wrote:
>
> > +1 (binding)
> >
> > - verified signatures
> > - verified hashes
> > - build cleanly
> > - verified a simple flow
> > - I think c2 worked as expected
> > - ran toolkit's config.sh and did some converting without issue
> >
> >
> > On Mon, May 15, 2017 at 12:55 PM, Aldrin Piri  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > MiNiFi, minifi-0.2.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1107
> > >
> > > The Git tag is minifi-0.2.0-RC1
> > > The Git commit ID is 1813e87ccddffcc9ab75d25948c31901faf2f1ab
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=
> commit;h=
> > > 1813e87ccddffcc9ab75d25948c31901faf2f1ab
> > > * https://github.com/apache/nifi-minifi/commit/
> > > 1813e87ccddffcc9ab75d25948c31901faf2f1ab
> > >
> > > Checksums of minifi-0.2.0-source-release.zip:
> > > MD5:  e0f9bbd7afeb9547126a710b3e30face
> > > SHA1:  bcba77ccd4254de3275ecb2a732005e6b404706d
> > > SHA256:  c182d71ba298a41a336da139f435f10a253997d677fc4ae8820b261ea8c3
> > a4c2
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/aldrin.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 26 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > version=12338791&projectId=12319921
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/MINIFI/
> > > Release+Notes#ReleaseNotes-Version0.2.0
> > >
> > > The vote will be open for at least 72 hours and close at 5PM EDT, 18
> May
> > > 2017 [1].
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build
> > > from source, and test.  Then please vote:
> > >
> > > [ ] +1 Release this package as minifi-0.2.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> > > [1] You can determine this time for your local time zone at
> > > https://s.apache.org/minifi-0.2.0-rc1-close
> > >
> >
>
>
>
> --
> 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>
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi PMC Member - Yolanda Davis

[Scott Aslan]

In all seriousness though, Yolanda you are a true professional and I must
say I have the greatest respect for you and all that you do for our
community. Thank you and congrats again!

On Thu, May 18, 2017 at 8:33 AM, Matt Burgess  wrote:

> Congratulations Yolanda!  Very well deserved, looking forward to more
> of your awesome contributions and community involvement!
>
> On Wed, May 17, 2017 at 10:11 PM, Tony Kurc  wrote:
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Yolanda
> > Davis has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> > greatly appreciate all of Yolanda's hard work and generous contributions
> to
> > the project. We look forward to continued involvement in the project.
> >
> > I know many people have interacted with Yolanda maybe at one of her
> > conference talks, or had the pleasure of working with her on reviews, or
> > used some of the features she's contributed and put a lot of work into
> > making them well tested and easy to use. If so, I think you'd agree it is
> > hard to interact with Yolanda and not get excited about not only NiFi but
> > the entire Apache way. If not, you're in for a treat when you get the
> > chance!
> >
> > Please join us in congratulating and welcoming Yolanda to the Apache NiFi
> > PMC.
> >
> > Congratulations and welcome, Yolanda!
> >
> > -- Tony
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [ANNOUNCE] New Apache NiFi PMC Member - Yolanda Davis

[Scott Aslan]

Yolanda,

GRRRL SMH!!!

Congratulations and very much deserved! Thanks for all you do!

-Scotty

On Thu, May 18, 2017 at 7:41 AM, Marc  wrote:

>  Very awesome, Yolanda! Congrats!
>
> On Thu, May 18, 2017 at 6:45 AM, Joe Skora  wrote:
>
> > Congrats Yolanda!  Very much deserved.
> >
> > On Wed, May 17, 2017 at 10:11 PM, Tony Kurc  wrote:
> >
> > > On behalf of the Apache NiFi PMC, I am pleased to announce that Yolanda
> > > Davis has accepted the PMC's invitation to join the Apache NiFi PMC.
> We
> > > greatly appreciate all of Yolanda's hard work and generous
> contributions
> > to
> > > the project. We look forward to continued involvement in the project.
> > >
> > > I know many people have interacted with Yolanda maybe at one of her
> > > conference talks, or had the pleasure of working with her on reviews,
> or
> > > used some of the features she's contributed and put a lot of work into
> > > making them well tested and easy to use. If so, I think you'd agree it
> is
> > > hard to interact with Yolanda and not get excited about not only NiFi
> but
> > > the entire Apache way. If not, you're in for a treat when you get the
> > > chance!
> > >
> > > Please join us in congratulating and welcoming Yolanda to the Apache
> NiFi
> > > PMC.
> > >
> > > Congratulations and welcome, Yolanda!
> > >
> > > -- Tony
> > >
> >
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*

Re: [VOTE] Release Apache NiFi 1.2.0 (RC2)

[Scott Aslan]

+1 (non-binding)

- Verified signatures, checksums, LICENSE, NOTICE, and README
- Built using a full clean build with contrib check successfully on OSX
- Run example data flows on OS X with Chrome Version 58.0.3029.96 (64-bit) on
unsecured instance
- Run example data flows on OS X with Chrome Version 58.0.3029.96 (64-bit) on
secured instance

On Sun, May 7, 2017 at 8:57 AM, Jeff Zemerick  wrote:

> +1 non-binding
>
> Full contrib-check build on clean Ubuntu 16.04 image.
> Tested with some simple flows.
>
> A few sparse, intermittent unit test failures were added to JIRA.
>
> Jeff
>
>
> On Sun, May 7, 2017 at 8:27 AM, Matt Gilman 
> wrote:
>
> > +1 binding
> >
> > Verified hashes, signatures, etc
> > Full build with contrib-check
> >
> > Ran various configurations clustered vs standalone, secured vs unsecured,
> > different authentication strategies, etc. Also made sure that issues
> > discovered during VOTE of RC1 were corrected.
> >
> > Thanks
> >
> > Matt
> >
> > On Sun, May 7, 2017 at 1:36 AM, Koji Kawamura 
> > wrote:
> >
> > > +1 (non-binding)
> > > Full build with contrib check passed on Mac OS X
> > > Tested "Provenance Stream Record ReaderWriter" template, and other new
> > > features
> > >
> > > Thanks,
> > > Koji
> > >
> > > On Sun, May 7, 2017 at 7:43 AM, Richard St. John 
> > > wrote:
> > > > +1 non-binding
> > > > Built RPM on CentOS 6
> > > > Installed RPM on Amazon Linux
> > > > FlowFile from 1.1.x worked on 1.2.0
> > > >
> > > > Rick
> > > >
> > > > On Sat, May 6, 2017, 12:39 PM Haimo Liu 
> wrote:
> > > >
> > > >> +1 non-binding, release this as Apache NiFi 1.2.0
> > > >>
> > > >> Tested full clean install on OSX
> > > >>
> > > >> Tested RecordReader/Writer flow
> > > >> Tested CDC flow (MySql DB1 as source, MySql DB2 as target)
> > > >>
> > > >>
> > > >>
> > > >> On May 6, 2017 11:40 AM, "Joe Witt"  wrote:
> > > >>
> > > >> +1 (binding).
> > > >>
> > > >>
> > > >> Full clean build w/contrib check on OSX, Linux 3.10
> > > >> Builds clean on Windows10 but there are test failures due to os
> > > >> compatibility issues with the test.
> > > >>
> > > >> Tested the application on Windows, Linux and OSX.  All looks solid.
> > > >> License/Notice looks good.
> > > >>
> > > >> Provided a detailed template flow and instructions to use the new
> > > >> record reader/writer capability with internal schema registry to
> > > >> acquire, filter, and convert NiFi's own provenance stream into JSON,
> > > >> Avro, XML and CSV at once.
> > > >> https://cwiki.apache.org/confluence/display/NIFI/
> > > Example+Dataflow+Templates
> > > >>
> > > >> This is a really impressive release with tremendous community
> > > >> engagement!  Thanks all
> > > >>
> > > >> Joe
> > > >>
> > > >> On Fri, May 5, 2017 at 10:07 PM, Bryan Bende 
> > wrote:
> > > >> > Hello,
> > > >> >
> > > >> > I am pleased to be calling this vote for the source release of
> > Apache
> > > >> > NiFi nifi-1.2.0 (RC2).
> > > >> >
> > > >> > The source zip, including signatures, digests, etc. can be found
> at:
> > > >> > https://repository.apache.org/content/repositories/
> > orgapachenifi-1104
> > > >> >
> > > >> > The Git tag is nifi-1.2.0-RC2
> > > >> > The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > >> 3a605af8e0ac024fb0ba67262d49dab2727b2576
> > > >> >
> > > >> > Checksums of nifi-1.2.0-source-release.zip:
> > > >> > MD5: 90e298a9e23a9dab65358daddd8b5990
> > > >> > SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> > > >> > SHA256: c18398800c435dabff9f45ec55a450
> > ca78c3c1aec222aa295c0e2057912f
> > > eeb6
> > > >> >
> > > >> > Release artifacts are signed with the following key:
> > > >> > https://people

Re: Closing in on a NiFi 1.2.0 release?

[Scott Aslan]

Hey Bryan,

Please include the following in the release notes:


   - Core UI
  - Circular references have been removed and the code modularized.
  - Upgraded Node version to 6.9.3.
  - Upgraded npm version to 3.10.10.
  - Upgraded jQuery version to 3.1.1.
  - Upgraded D3 version to 3.5.17.
  - Reduced download size by removing bundled dependencies.
   - User Experience Improvements
   - Ever wish that it was easier to align components on the canvas? Me
  too...and now you can!
  - We now provide deep links to any component(s) on the canvas. This
  will help make collaborating and sharing more natural.
  - Users will enjoy a better understanding of the scope of Controller
  Services through an improved experience.
  - All actions available on the operate palette are now also available
  under the context menu too!

Thanks!

On Tue, May 2, 2017 at 10:17 AM, Bryan Bende  wrote:

> All,
>
> Looks like we are closer than we have ever been!
>
> Down to three outstanding JIRAs...
>
> - NIFI-1833 (Azure Processors) - Active review and discussion
> occurring, appears to be close
> - NIFI-3260 (Official Docker Image) - Active discussion, looks like
> this may be moved from the release to a separate effort
> - NIFI-3765 (Status operation for NodeManager) - Active review, looks
> like it could be merged relatively soon
>
> Once these are finalized we should be able to start the RC process.
>
> I've started putting together the release notes on the Wiki (still a
> work in progress):
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.2.0
>
> If anyone knows of anything that should be highlighted, feel free to
> mention it here and I can update the notes.
>
> Thanks!
>
> -Bryan
>
>
> On Thu, Apr 27, 2017 at 5:52 PM, Bryan Bende  wrote:
> > Looks like we are down to just a few tickets, and all of them seem to
> > have traction in terms of review and discussion.
> >
> > I'll keep an eye on the tickets and start trying to pull together
> > anything I can to get ready for the RC process. Seems like we are
> > close!
> >
> > On Tue, Apr 25, 2017 at 9:33 AM, Russell Bateman 
> wrote:
> >> Many thanks to all the industrious folk working on this tool that's
> become
> >> indispensable to so many. The community has my enduring gratitude and
> >> admiration!
> >>
> >> Russ
> >>
> >>
> >> On 04/24/2017 07:16 PM, Joe Witt wrote:
> >>>
> >>> Robert,
> >>>
> >>> We're about 10 or so JIRAs away at this point and all of them have PRs
> >>> and progress on them.  We need to close those down and do some
> >>> stabilization/testing then a release candidate can happen.  So perhaps
> >>> next week we'll be at that point and have a release.  This is the
> >>> right place to be watching to see it closing in.
> >>>
> >>> Thanks
> >>> Joe
> >>>
> >>> On Mon, Apr 24, 2017 at 5:40 AM, roboh  wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> is there any date set for 1.2.0 release yet?
> >>>> We are running into an  NIFI-3389
> >>>> <https://issues.apache.org/jira/browse/NIFI-3389>   issue and would
> like
> >>>> to
> >>>> know when we can expect 1.2.0 release to be available.
> >>>>
> >>>> Thanks,
> >>>> Robert
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>> http://apache-nifi-developer-list.39713.n7.nabble.com/
> Closing-in-on-a-NiFi-1-2-0-release-tp14907p15532.html
> >>>> Sent from the Apache NiFi Developer List mailing list archive at
> >>>> Nabble.com.
> >>
> >>
>



-- 
*Scott Aslan = new WebDeveloper(*
*{"location": {"city": "Saint Cloud","state": "FL",
"zip": "34771"},"contact": {"email":
"scottyas...@gmail.com ","linkedin":
"http://www.linkedin.com/in/scottyaslan
<http://www.linkedin.com/in/scottaslan>"}});*