Re: [DISCUSS] CI / Travis / Jenkins

[Joe Witt]

Great news!  So for the first time in a long time we now have
travis-ci builds passing!

I incorporated Dustin's PR which changed to the -Ddir-only instead of
-P, added Andre's idea of dropping the -quiet flag, and dropped the
number of builds in the config to a single parallel build with contrib
check now that we're seeing those pass with rat/checkstyle.

https://travis-ci.org/apache/nifi/builds/311660398

A couple failed due to test failures and I filed JIRAs to convert
these into integration tests or resolve.
 -https://issues.apache.org/jira/browse/NIFI-4660,
https://issues.apache.org/jira/browse/NIFI-4659

One actually finished as you can see in its raw log but travis seems
to have gotten confused.

Two passed completely.  I think to reduce strain on Travis-CI
infrastructure we should drop two of the environments.

Current it is in .travis.yml

env:
  - USER_LANGUAGE=en USER_REGION=US'
  - USER_LANGUAGE=fr USER_REGION=FR'
  - USER_LANGUAGE=ja USER_REGION=JP'
  - USER_LANGUAGE=pt USER_REGION=BR'
  - USER_LANGUAGE=default USER_REGION=default

I think we should drop it to

env:
  - USER_LANGUAGE=en USER_REGION=US'
  - USER_LANGUAGE=fr USER_REGION=FR'
  - USER_LANGUAGE=ja USER_REGION=JP'

If no objections i'll do that soon.  But, good news is the builds are
coming back to life on Travis-CI and will help streamline review
cycles again!

Thanks

On Mon, Dec 4, 2017 at 8:29 PM, Joe Witt  wrote:
> nope. will take a look at this tonight though.
>
> On Dec 4, 2017 8:09 PM, "Andre"  wrote:
>>
>> Joe & Joey,
>>
>> I believe setting the maven compilation job to noisy - instead of the
>> current quiet setting - should help solving the issue.
>>
>> Have we tried that?
>>
>> Cheers
>>
>>
>> On 5 Dec 2017 6:26 AM, "Joe Witt"  wrote:
>>
>> I agree this would be extremely nice to get back on track.  The
>> changes made last night/today to the poms do appear to mean that
>> parallel builds with contrib-check are working.  Perhaps that helps us
>> a little with travis (or not).  I have reviewed a couple PRs though
>> recently that did not even compile much less have clean contrib-checks
>> so it is really nice to have Travis being more reliable.  Does anyone
>> have any sense of the current reasons for issues?  When I've looked
>> the errors made no sense at all.
>>
>> On Mon, Dec 4, 2017 at 2:21 PM, Joey Frazee 
>> wrote:
>> > I’m sure everyone has noticed that Travis CI fails, incorrectly, more
>> than it succeeds, often due to timeouts and not b/c of the incorrectness
>> of
>> a commit or PR.
>> >
>> > This has been discussed previously, but it’s carried on, and become a
>> > low
>> information signal about the PRs, which has two big impacts: (1) it’s
>> ignored by experienced contributors and reviewers, and (2) it’s confusing
>> or misleading to new contributors.
>> >
>> > So, we really need to find a solution. I can think of a few:
>> >
>> > 1. Continue to push on INFRA to setup Jenkins for NiFi and its
>> sub-projects.
>> >
>> > 2. Implement some kind of quick-test profile and shell script that
>> > checks
>> the most important things along with the subdirectories affected by the
>> PR,
>> and continue to use Travis CI.
>> >
>> > 3. Use some other service like Circle CI or Codeship, which probably
>> isn’t quite what ASF wants but it might make the CI more useful (it also
>> might not).
>> >
>> > 4. Find a sponsor to support a more premium tier of Travis CI (or
>> > equiv.)
>> so the build has enough resources to to succeed. This too probably isn’t
>> preferable but I’m sure we can find a precedent.
>> >
>> > I’m partial to pursuing (1) and (2) together because (1) would give us a
>> long term solution and (2) would have some value for local builds (no need
>> to run the full build) as well as making Travis CI tell us something. The
>> first should be pretty low effort. The second will be labor intensive I
>> think — to identify what counts as quick and change the poms — so it can’t
>> be the answer on its own unless we want to wait longer to see Travis CI
>> become informative.
>> >
>> > What do the rest of you think?
>> >
>> > -joey

Re: [DISCUSS] CI / Travis / Jenkins

[Joe Witt]

nope. will take a look at this tonight though.

On Dec 4, 2017 8:09 PM, "Andre"  wrote:

> Joe & Joey,
>
> I believe setting the maven compilation job to noisy - instead of the
> current quiet setting - should help solving the issue.
>
> Have we tried that?
>
> Cheers
>
>
> On 5 Dec 2017 6:26 AM, "Joe Witt"  wrote:
>
> I agree this would be extremely nice to get back on track.  The
> changes made last night/today to the poms do appear to mean that
> parallel builds with contrib-check are working.  Perhaps that helps us
> a little with travis (or not).  I have reviewed a couple PRs though
> recently that did not even compile much less have clean contrib-checks
> so it is really nice to have Travis being more reliable.  Does anyone
> have any sense of the current reasons for issues?  When I've looked
> the errors made no sense at all.
>
> On Mon, Dec 4, 2017 at 2:21 PM, Joey Frazee 
> wrote:
> > I’m sure everyone has noticed that Travis CI fails, incorrectly, more
> than it succeeds, often due to timeouts and not b/c of the incorrectness of
> a commit or PR.
> >
> > This has been discussed previously, but it’s carried on, and become a low
> information signal about the PRs, which has two big impacts: (1) it’s
> ignored by experienced contributors and reviewers, and (2) it’s confusing
> or misleading to new contributors.
> >
> > So, we really need to find a solution. I can think of a few:
> >
> > 1. Continue to push on INFRA to setup Jenkins for NiFi and its
> sub-projects.
> >
> > 2. Implement some kind of quick-test profile and shell script that checks
> the most important things along with the subdirectories affected by the PR,
> and continue to use Travis CI.
> >
> > 3. Use some other service like Circle CI or Codeship, which probably
> isn’t quite what ASF wants but it might make the CI more useful (it also
> might not).
> >
> > 4. Find a sponsor to support a more premium tier of Travis CI (or equiv.)
> so the build has enough resources to to succeed. This too probably isn’t
> preferable but I’m sure we can find a precedent.
> >
> > I’m partial to pursuing (1) and (2) together because (1) would give us a
> long term solution and (2) would have some value for local builds (no need
> to run the full build) as well as making Travis CI tell us something. The
> first should be pretty low effort. The second will be labor intensive I
> think — to identify what counts as quick and change the poms — so it can’t
> be the answer on its own unless we want to wait longer to see Travis CI
> become informative.
> >
> > What do the rest of you think?
> >
> > -joey
>

Re: [DISCUSS] CI / Travis / Jenkins

[Andre]

Joe & Joey,

I believe setting the maven compilation job to noisy - instead of the
current quiet setting - should help solving the issue.

Have we tried that?

Cheers


On 5 Dec 2017 6:26 AM, "Joe Witt"  wrote:

I agree this would be extremely nice to get back on track.  The
changes made last night/today to the poms do appear to mean that
parallel builds with contrib-check are working.  Perhaps that helps us
a little with travis (or not).  I have reviewed a couple PRs though
recently that did not even compile much less have clean contrib-checks
so it is really nice to have Travis being more reliable.  Does anyone
have any sense of the current reasons for issues?  When I've looked
the errors made no sense at all.

On Mon, Dec 4, 2017 at 2:21 PM, Joey Frazee  wrote:
> I’m sure everyone has noticed that Travis CI fails, incorrectly, more
than it succeeds, often due to timeouts and not b/c of the incorrectness of
a commit or PR.
>
> This has been discussed previously, but it’s carried on, and become a low
information signal about the PRs, which has two big impacts: (1) it’s
ignored by experienced contributors and reviewers, and (2) it’s confusing
or misleading to new contributors.
>
> So, we really need to find a solution. I can think of a few:
>
> 1. Continue to push on INFRA to setup Jenkins for NiFi and its
sub-projects.
>
> 2. Implement some kind of quick-test profile and shell script that checks
the most important things along with the subdirectories affected by the PR,
and continue to use Travis CI.
>
> 3. Use some other service like Circle CI or Codeship, which probably
isn’t quite what ASF wants but it might make the CI more useful (it also
might not).
>
> 4. Find a sponsor to support a more premium tier of Travis CI (or equiv.)
so the build has enough resources to to succeed. This too probably isn’t
preferable but I’m sure we can find a precedent.
>
> I’m partial to pursuing (1) and (2) together because (1) would give us a
long term solution and (2) would have some value for local builds (no need
to run the full build) as well as making Travis CI tell us something. The
first should be pretty low effort. The second will be labor intensive I
think — to identify what counts as quick and change the poms — so it can’t
be the answer on its own unless we want to wait longer to see Travis CI
become informative.
>
> What do the rest of you think?
>
> -joey

Re: [DISCUSS] CI / Travis / Jenkins

[Joe Witt]

I agree this would be extremely nice to get back on track.  The
changes made last night/today to the poms do appear to mean that
parallel builds with contrib-check are working.  Perhaps that helps us
a little with travis (or not).  I have reviewed a couple PRs though
recently that did not even compile much less have clean contrib-checks
so it is really nice to have Travis being more reliable.  Does anyone
have any sense of the current reasons for issues?  When I've looked
the errors made no sense at all.

On Mon, Dec 4, 2017 at 2:21 PM, Joey Frazee  wrote:
> I’m sure everyone has noticed that Travis CI fails, incorrectly, more than it 
> succeeds, often due to timeouts and not b/c of the incorrectness of a commit 
> or PR.
>
> This has been discussed previously, but it’s carried on, and become a low 
> information signal about the PRs, which has two big impacts: (1) it’s ignored 
> by experienced contributors and reviewers, and (2) it’s confusing or 
> misleading to new contributors.
>
> So, we really need to find a solution. I can think of a few:
>
> 1. Continue to push on INFRA to setup Jenkins for NiFi and its sub-projects.
>
> 2. Implement some kind of quick-test profile and shell script that checks the 
> most important things along with the subdirectories affected by the PR, and 
> continue to use Travis CI.
>
> 3. Use some other service like Circle CI or Codeship, which probably isn’t 
> quite what ASF wants but it might make the CI more useful (it also might not).
>
> 4. Find a sponsor to support a more premium tier of Travis CI (or equiv.) so 
> the build has enough resources to to succeed. This too probably isn’t 
> preferable but I’m sure we can find a precedent.
>
> I’m partial to pursuing (1) and (2) together because (1) would give us a long 
> term solution and (2) would have some value for local builds (no need to run 
> the full build) as well as making Travis CI tell us something. The first 
> should be pretty low effort. The second will be labor intensive I think — to 
> identify what counts as quick and change the poms — so it can’t be the answer 
> on its own unless we want to wait longer to see Travis CI become informative.
>
> What do the rest of you think?
>
> -joey

[DISCUSS] CI / Travis / Jenkins

[Joey Frazee]

I’m sure everyone has noticed that Travis CI fails, incorrectly, more than it 
succeeds, often due to timeouts and not b/c of the incorrectness of a commit or 
PR.

This has been discussed previously, but it’s carried on, and become a low 
information signal about the PRs, which has two big impacts: (1) it’s ignored 
by experienced contributors and reviewers, and (2) it’s confusing or misleading 
to new contributors.

So, we really need to find a solution. I can think of a few:

1. Continue to push on INFRA to setup Jenkins for NiFi and its sub-projects.

2. Implement some kind of quick-test profile and shell script that checks the 
most important things along with the subdirectories affected by the PR, and 
continue to use Travis CI.

3. Use some other service like Circle CI or Codeship, which probably isn’t 
quite what ASF wants but it might make the CI more useful (it also might not).

4. Find a sponsor to support a more premium tier of Travis CI (or equiv.) so 
the build has enough resources to to succeed. This too probably isn’t 
preferable but I’m sure we can find a precedent.

I’m partial to pursuing (1) and (2) together because (1) would give us a long 
term solution and (2) would have some value for local builds (no need to run 
the full build) as well as making Travis CI tell us something. The first should 
be pretty low effort. The second will be labor intensive I think — to identify 
what counts as quick and change the poms — so it can’t be the answer on its own 
unless we want to wait longer to see Travis CI become informative.

What do the rest of you think?

-joey

Updated maven plugins, apache parent, and changed dir-only profile

[Joe Witt]

Team

https://issues.apache.org/jira/browse/NIFI-4652

In that JIRA the various maven plugins we use for key build processes
were updated.  This brings us more in-line with latest apache parent
pom which helps with builds and consistency.  But, also we fixed usage
of mavens profile activation method 'activeByDefault' which did not
work as I think many of us assumed it did.

The primary change that impacts folks is those who do builds with the
-Pdir-only profile.  This profile can save you roughly  30-40 seconds
during the build as it avoids making the zip/tar.gz and instead just
makes a directory.  However, this is now accomplished by setting a
system propery during the build called 'dir-only'. Therefore the only
difference is -Pdir-only becomes -Ddir-only.  So a build such as 'mvn
clean install -Ddir-only' works great and saves some seconds.

Andre: Did you have this documented anywhere you recall?  I though it
was on the contrib guide or someplace but I dont see it so will likely
leave it alone for now.

Just a heads up otherwise.

Thanks

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Andrew Psaltis]

Congrats Scott!! All of your work on the UI is greatly appreciated by
everyone that uses NiFi.

On Sat, 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
>



-- 
Thanks,
Andrew

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Jeff]

Congrats, Scott.  You are really crushing it!

On Mon, Dec 4, 2017 at 9:11 AM Michael Moser  wrote:

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

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Michael Moser]

Thank you for your work, Scott, and congrats on joining the PMC!

-- Mike


On Mon, Dec 4, 2017 at 7:02 AM, Rob Moran  wrote:

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

Need Advice for Development

[Mohammad Reza Karimi]

Hello Dear Agent ;

 

We want to use Apache NiFi for commercial purpose in my company and extend
to other companies .

So , could I develop own server side (is any library for?) or need to use
rental services like HDF , AWS , . ?

Is there any simple or free charge solution for customize NiFi for me ? I
want to add register library in it at next level .

 

Best Regards ;

M.R.K.


 

Yours Sincerely,

Mohammad Reza Karimi

Research & Development Expert

 

Email:   kar...@vareshco.com

 

Tehran Office : 

Unit 20, 6th floor,No. 242,Ferdos bldg,

Molasadra Ave,Vanak Sq,Tehran-Iran

Tel: +98 21 89 37 8000

Fax: +98 21 88 61 1760

UAE Office : 

No.705, Al Abraj St., Business Bay, UAE

Tel: +971 4 4296005-8

Fax: +971 4 4296009

London Office : 

S6, Shakespeare Avenue, Londen N11, 1ay

Mob: 00447404405334

 

  www.vareshco.com

 

 

 

 

 

 

 

 




 

 

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Rob Moran]

Awesome – congrats Scott!!

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

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

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Pierre Villard]

Congrats Scott, well deserved!

2017-12-03 13:58 GMT+01:00 Scott Aslan :

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