Re: RTC clarification

[James Wing]

We should definitely encourage review feedback from non-committers.
Getting additional perspectives, interest, and enthusiasm from users is
critical for any project, doubly so for an integrating application where
committers cannot be experts in all the systems we are integrating with.  I
believe NiFi could use more review bandwidth.  Are missing out on potential
reviewers because of the current policy?

I do not have any experience with non-committer "binding reviews" as
described in the Apache Gossip thread.  How would that work?  Wouldn't a
committer have to review the review and decide to commit?  If we knew the
reviewer well enough to accept their judgement, why not make them a
committer?

My expectation is that many non-committer reviews are helpful and
constructive, but not necessarily 100% comprehensive.  Reviewers might
comment on the JIRA ticket without working with the PR, or try the proposed
change without reviewing the code, tests, etc.  All great stuff, but
backstopped by committers.

Thanks,

James

On Thu, Jul 6, 2017 at 7:30 PM, Joe Witt  wrote:

> It is undefined at this point and I agree we should reach consensus
> and document it.
>
> I am in favor making non-committer reviews binding.
>
> Why do we do RTC:
> - To help bring along new committers/grow the community
> - To help promote quality by having peer reviews
>
> Enabling non-committer reviews to be binding still allows both of
> those to be true.
>
> On Thu, Jul 6, 2017 at 10:10 PM, Tony Kurc  wrote:
> > All, I was having a discussion with Mike Hogue - a recent contributor -
> off
> > list, and he had some questions about the review process. And largely the
> > root of the question was, if a non-committer reviews a patch or PR (which
> > Mike has spent some time doing), is that considered a "review"? I didn't
> > have the answers, so I went on a hunt for documentation. I started with
> the
> > Contributor Guide [1]. The guide describes reviewing, and calls out a
> > Reviewer role, but doesn't specifically point out that Reviewer is a
> > committer, just that a committer "can actively promote contributions into
> > the repository", and goes on to imply the non-committers can review.
> >
> > Given this, I was unable to answer this question:
> > If a committer "X" submits a patch or PR, it is reviewed by a
> non-committer
> > "Y", does that review satisfy the RTC requirement, and "X" may merge in
> the
> > patch?
> >
> > I found a related discussion on the email list in March [2], which I
> think
> > implies at least some of the community assumed the canonical review must
> be
> > by a committer. I also went back a bit to early days [3], where Benson
> > implied a much less "formal" review process.
> >
> > What I'm hoping for is hopefully come to a consensus of what our project
> > expectations are and document in the Contributor Guide. My expectation
> was
> > that non-committers could review, similar to what Sean discussed on this
> > thread for Apache Gossip (incubating) [4]. However, I don't believe this
> is
> > the current consensus.
> >
> > Thoughts?
> >
> > Tony
> >
> > 1.
> > https://cwiki.apache.org/confluence/display/NIFI/Contributor
> +Guide#ContributorGuide-CodeReviewProcess
> > 2.
> > https://mail-archives.apache.org/mod_mbox/nifi-dev/201703.mb
> ox/%3CCALJK9a7onOKo%3DXtAEmL7PSBUEBEqOOhcT9WSz-RZaNxqV6q%
> 3Dmg%40mail.gmail.com%3E
> > 3.
> > https://mail-archives.apache.org/mod_mbox/nifi-dev/201501.mb
> ox/%3CCALhtWkf67UpOe9W9HQ3RSn00xb_=C6ZMxN+_SEfWthpQrU5fsg@
> mail.gmail.com%3E
> > 4.
> > http://mail-archives.apache.org/mod_mbox/incubator-gossip-de
> v/201606.mbox/%3CCAN5cbe6P8aEEOLMA%2BPrfpQg9c_AWeSfvvmom8jAp%3Dk7wUpoVgQ%
> 40mail.gmail.com%3E
>

Re: RTC clarification

[Joe Witt]

It is undefined at this point and I agree we should reach consensus
and document it.

I am in favor making non-committer reviews binding.

Why do we do RTC:
- To help bring along new committers/grow the community
- To help promote quality by having peer reviews

Enabling non-committer reviews to be binding still allows both of
those to be true.

On Thu, Jul 6, 2017 at 10:10 PM, Tony Kurc  wrote:
> All, I was having a discussion with Mike Hogue - a recent contributor - off
> list, and he had some questions about the review process. And largely the
> root of the question was, if a non-committer reviews a patch or PR (which
> Mike has spent some time doing), is that considered a "review"? I didn't
> have the answers, so I went on a hunt for documentation. I started with the
> Contributor Guide [1]. The guide describes reviewing, and calls out a
> Reviewer role, but doesn't specifically point out that Reviewer is a
> committer, just that a committer "can actively promote contributions into
> the repository", and goes on to imply the non-committers can review.
>
> Given this, I was unable to answer this question:
> If a committer "X" submits a patch or PR, it is reviewed by a non-committer
> "Y", does that review satisfy the RTC requirement, and "X" may merge in the
> patch?
>
> I found a related discussion on the email list in March [2], which I think
> implies at least some of the community assumed the canonical review must be
> by a committer. I also went back a bit to early days [3], where Benson
> implied a much less "formal" review process.
>
> What I'm hoping for is hopefully come to a consensus of what our project
> expectations are and document in the Contributor Guide. My expectation was
> that non-committers could review, similar to what Sean discussed on this
> thread for Apache Gossip (incubating) [4]. However, I don't believe this is
> the current consensus.
>
> Thoughts?
>
> Tony
>
> 1.
> https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
> 2.
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201703.mbox/%3CCALJK9a7onOKo%3DXtAEmL7PSBUEBEqOOhcT9WSz-RZaNxqV6q%3Dmg%40mail.gmail.com%3E
> 3.
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201501.mbox/%3CCALhtWkf67UpOe9W9HQ3RSn00xb_=c6zmxn+_sefwthpqru5...@mail.gmail.com%3E
> 4.
> http://mail-archives.apache.org/mod_mbox/incubator-gossip-dev/201606.mbox/%3CCAN5cbe6P8aEEOLMA%2BPrfpQg9c_AWeSfvvmom8jAp%3Dk7wUpoVgQ%40mail.gmail.com%3E

RTC clarification

[Tony Kurc]

All, I was having a discussion with Mike Hogue - a recent contributor - off
list, and he had some questions about the review process. And largely the
root of the question was, if a non-committer reviews a patch or PR (which
Mike has spent some time doing), is that considered a "review"? I didn't
have the answers, so I went on a hunt for documentation. I started with the
Contributor Guide [1]. The guide describes reviewing, and calls out a
Reviewer role, but doesn't specifically point out that Reviewer is a
committer, just that a committer "can actively promote contributions into
the repository", and goes on to imply the non-committers can review.

Given this, I was unable to answer this question:
If a committer "X" submits a patch or PR, it is reviewed by a non-committer
"Y", does that review satisfy the RTC requirement, and "X" may merge in the
patch?

I found a related discussion on the email list in March [2], which I think
implies at least some of the community assumed the canonical review must be
by a committer. I also went back a bit to early days [3], where Benson
implied a much less "formal" review process.

What I'm hoping for is hopefully come to a consensus of what our project
expectations are and document in the Contributor Guide. My expectation was
that non-committers could review, similar to what Sean discussed on this
thread for Apache Gossip (incubating) [4]. However, I don't believe this is
the current consensus.

Thoughts?

Tony

1.
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
2.
https://mail-archives.apache.org/mod_mbox/nifi-dev/201703.mbox/%3CCALJK9a7onOKo%3DXtAEmL7PSBUEBEqOOhcT9WSz-RZaNxqV6q%3Dmg%40mail.gmail.com%3E
3.
https://mail-archives.apache.org/mod_mbox/nifi-dev/201501.mbox/%3CCALhtWkf67UpOe9W9HQ3RSn00xb_=c6zmxn+_sefwthpqru5...@mail.gmail.com%3E
4.
http://mail-archives.apache.org/mod_mbox/incubator-gossip-dev/201606.mbox/%3CCAN5cbe6P8aEEOLMA%2BPrfpQg9c_AWeSfvvmom8jAp%3Dk7wUpoVgQ%40mail.gmail.com%3E

Re: [DRAFT][REPORT] Apache NiFi - July 2017

[Pierre Villard]

+1

2017-07-06 14:09 GMT+02:00 Joe Skora :

> +1  Release this package as NiFi Board Report July 2017
>
> On Thu, Jul 6, 2017 at 7:46 AM, Tony Kurc  wrote:
>
> > I don't have any concerns, looks good!
> >
> > On Thu, Jul 6, 2017 at 2:01 AM, Aldrin Piri 
> wrote:
> >
> > > Looks good.  Thanks for compiling this, Joe.
> > >
> > > On Tue, Jul 4, 2017 at 9:50 AM, Joe Witt  wrote:
> > >
> > > > Team,
> > > >
> > > > It's that time again to submit our board report for Apache NiFi.
> > > > Please see below draft.  If you have any suggestions/fixes, edits
> > > > please advise.
> > > >
> > > > I'll submit the report in a few days.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > > > +_+_+_+_+_+_+_
> > > >
> > > > ## Description:
> > > >  - Apache NiFi is an easy to use, powerful, and reliable system to
> > > >process and distribute data.
> > > >  - Apache NiFi MiNiFi is an edge data collection agent built to
> > > seamlessly
> > > >integrate with and leverage the command and control of NiFi. There
> > are
> > > >both Java and C++ implementations.
> > > >  - Apache NiFi Registry is a centralized registry for key
> configuration
> > > > items
> > > >including flow versions, assets, and extensions for Apache NiFi
> > > >and Apache MiNiFi.
> > > >  - Apache NiFi Nar Maven Plugin is a release artifact used for
> > supporting
> > > >the NiFi classloader isolation model.
> > > >
> > > > ## Issues:
> > > >  - There are no issues requiring board attention at this time.
> > > >
> > > > ## Activity:
> > > >  - Based on board feedback in last report the descriptions above have
> > > been
> > > >simplified to avoid confusing child/subproject terminology.  We
> have
> > > >successfully conducted and completed name searches for the MiNiFi
> > and
> > > >Registry efforts.
> > > >  - Conducted numerous releases as listed below.  The 0.7.x releases
> > > focused
> > > >on providing simple bug fixes and resolving reported CVEs.  The
> 1.x
> > > >releases brought about stability, performance improvements, and
> > > > addressed
> > > >reported CVEs.  Further, in the 1.x releases numerous substantive
> > > > features
> > > >were introduced including the ability to run multiple versions of
> > the
> > > > same
> > > >components and support for both format and schema aware record
> > > > processors
> > > >to easily handle cases like acquisition, SQL based routing,
> > > enrichment,
> > > >conversion, and delivery of record oriented data.  These make many
> > > > common
> > > >record oriented use cases far more performant, intuitive, and
> retain
> > > the
> > > >full power of NiFi's provenance features.
> > > >
> > > > ## Health report:
> > > >  - Health of the community is strong and indicators of strength
> > continue
> > > >trending in the right direction. Mailing list and JIRA activity is
> > > > strong.
> > > >ASF Hipchat is serving as an on-ramp for new users to our mailing
> > list
> > > > and
> > > >JIRA systems. We continue to see new users and contributors. The
> PMC
> > > and
> > > >committer ranks grew again during this reporting cycle and the
> > > pipeline
> > > >is encouraging. We're generating many releases with new release
> > > managers
> > > >stepping up often. The team handles security reports swiftly and
> > > follows
> > > >ASF security team published processes effectively.
> > > >
> > > > ## PMC changes:
> > > >
> > > >  - Currently 22 PMC members.
> > > >  - New PMC members:
> > > > - Koji Kawamura was added to the PMC on Fri May 26 2017
> > > > - Pierre Villard was added to the PMC on Sun May 21 2017
> > > > - Yolanda Davis was added to the PMC on Wed May 17 2017
> > > >
> > > > ## Committer base changes:
> > > >
> > > >  - Currently 34 committers.
> > > >  - New commmitters:
> > > > - Marc Parisi was added as a committer on Thu Jun 01 2017
> > > > - Andrew M. Lim was added as a committer on Wed May 31 2017
> > > >
> > > > ## Releases:
> > > >
> > > >  - Apache NiFi 1.3.0 was released June 9 2017.
> > > >  - Apache NiFi 0.7.4 was released June 9 2017.
> > > >  - Apache NiFi MiNiFi (java) 0.2.0 was released May 19 2017.
> > > >  - Apache NiFi 0.7.3 was released May 19 2017.
> > > >  - Apache NiFi MiNiFi (cpp) 0.2.0 was released May 14 2017.
> > > >  - Apache NiFi 1.2.0 was released May 10 2017.
> > > >
> > > > ## Mailing list activity:
> > > >
> > > >  - Activity on the mailing lists remains extremely high with a
> mixture
> > > >of new users, contributors, and deeper more experienced users and
> > > >contributors sparking discussion and questions and filing bugs or
> > > >new features.
> > > >
> > > >  - us...@nifi.apache.org:
> > > > - 512 subscribers (up 39 in the last 3 months):
> > > > - 936 emails sent to list (846 in previous quarter)
> > > >
> > > >  - dev@nifi.apache.org:
> > > > - 367 

Re: [DRAFT][REPORT] Apache NiFi - July 2017

[Joe Skora]

+1  Release this package as NiFi Board Report July 2017

On Thu, Jul 6, 2017 at 7:46 AM, Tony Kurc  wrote:

> I don't have any concerns, looks good!
>
> On Thu, Jul 6, 2017 at 2:01 AM, Aldrin Piri  wrote:
>
> > Looks good.  Thanks for compiling this, Joe.
> >
> > On Tue, Jul 4, 2017 at 9:50 AM, Joe Witt  wrote:
> >
> > > Team,
> > >
> > > It's that time again to submit our board report for Apache NiFi.
> > > Please see below draft.  If you have any suggestions/fixes, edits
> > > please advise.
> > >
> > > I'll submit the report in a few days.
> > >
> > > Thanks
> > > Joe
> > >
> > > +_+_+_+_+_+_+_
> > >
> > > ## Description:
> > >  - Apache NiFi is an easy to use, powerful, and reliable system to
> > >process and distribute data.
> > >  - Apache NiFi MiNiFi is an edge data collection agent built to
> > seamlessly
> > >integrate with and leverage the command and control of NiFi. There
> are
> > >both Java and C++ implementations.
> > >  - Apache NiFi Registry is a centralized registry for key configuration
> > > items
> > >including flow versions, assets, and extensions for Apache NiFi
> > >and Apache MiNiFi.
> > >  - Apache NiFi Nar Maven Plugin is a release artifact used for
> supporting
> > >the NiFi classloader isolation model.
> > >
> > > ## Issues:
> > >  - There are no issues requiring board attention at this time.
> > >
> > > ## Activity:
> > >  - Based on board feedback in last report the descriptions above have
> > been
> > >simplified to avoid confusing child/subproject terminology.  We have
> > >successfully conducted and completed name searches for the MiNiFi
> and
> > >Registry efforts.
> > >  - Conducted numerous releases as listed below.  The 0.7.x releases
> > focused
> > >on providing simple bug fixes and resolving reported CVEs.  The 1.x
> > >releases brought about stability, performance improvements, and
> > > addressed
> > >reported CVEs.  Further, in the 1.x releases numerous substantive
> > > features
> > >were introduced including the ability to run multiple versions of
> the
> > > same
> > >components and support for both format and schema aware record
> > > processors
> > >to easily handle cases like acquisition, SQL based routing,
> > enrichment,
> > >conversion, and delivery of record oriented data.  These make many
> > > common
> > >record oriented use cases far more performant, intuitive, and retain
> > the
> > >full power of NiFi's provenance features.
> > >
> > > ## Health report:
> > >  - Health of the community is strong and indicators of strength
> continue
> > >trending in the right direction. Mailing list and JIRA activity is
> > > strong.
> > >ASF Hipchat is serving as an on-ramp for new users to our mailing
> list
> > > and
> > >JIRA systems. We continue to see new users and contributors. The PMC
> > and
> > >committer ranks grew again during this reporting cycle and the
> > pipeline
> > >is encouraging. We're generating many releases with new release
> > managers
> > >stepping up often. The team handles security reports swiftly and
> > follows
> > >ASF security team published processes effectively.
> > >
> > > ## PMC changes:
> > >
> > >  - Currently 22 PMC members.
> > >  - New PMC members:
> > > - Koji Kawamura was added to the PMC on Fri May 26 2017
> > > - Pierre Villard was added to the PMC on Sun May 21 2017
> > > - Yolanda Davis was added to the PMC on Wed May 17 2017
> > >
> > > ## Committer base changes:
> > >
> > >  - Currently 34 committers.
> > >  - New commmitters:
> > > - Marc Parisi was added as a committer on Thu Jun 01 2017
> > > - Andrew M. Lim was added as a committer on Wed May 31 2017
> > >
> > > ## Releases:
> > >
> > >  - Apache NiFi 1.3.0 was released June 9 2017.
> > >  - Apache NiFi 0.7.4 was released June 9 2017.
> > >  - Apache NiFi MiNiFi (java) 0.2.0 was released May 19 2017.
> > >  - Apache NiFi 0.7.3 was released May 19 2017.
> > >  - Apache NiFi MiNiFi (cpp) 0.2.0 was released May 14 2017.
> > >  - Apache NiFi 1.2.0 was released May 10 2017.
> > >
> > > ## Mailing list activity:
> > >
> > >  - Activity on the mailing lists remains extremely high with a mixture
> > >of new users, contributors, and deeper more experienced users and
> > >contributors sparking discussion and questions and filing bugs or
> > >new features.
> > >
> > >  - us...@nifi.apache.org:
> > > - 512 subscribers (up 39 in the last 3 months):
> > > - 936 emails sent to list (846 in previous quarter)
> > >
> > >  - dev@nifi.apache.org:
> > > - 367 subscribers (up 24 in the last 3 months):
> > > - 1018 emails sent to list (925 in previous quarter)
> > >
> > >  - iss...@nifi.apache.org:
> > > - 42 subscribers (up 4 in the last 3 months):
> > > - 7936 emails sent to list (6592 in previous quarter)
> > >
> > >
> > > ## JIRA activity:
> > >
> > >  - 573 JIRA 

Re: [DRAFT][REPORT] Apache NiFi - July 2017

[Tony Kurc]

I don't have any concerns, looks good!

On Thu, Jul 6, 2017 at 2:01 AM, Aldrin Piri  wrote:

> Looks good.  Thanks for compiling this, Joe.
>
> On Tue, Jul 4, 2017 at 9:50 AM, Joe Witt  wrote:
>
> > Team,
> >
> > It's that time again to submit our board report for Apache NiFi.
> > Please see below draft.  If you have any suggestions/fixes, edits
> > please advise.
> >
> > I'll submit the report in a few days.
> >
> > Thanks
> > Joe
> >
> > +_+_+_+_+_+_+_
> >
> > ## Description:
> >  - Apache NiFi is an easy to use, powerful, and reliable system to
> >process and distribute data.
> >  - Apache NiFi MiNiFi is an edge data collection agent built to
> seamlessly
> >integrate with and leverage the command and control of NiFi. There are
> >both Java and C++ implementations.
> >  - Apache NiFi Registry is a centralized registry for key configuration
> > items
> >including flow versions, assets, and extensions for Apache NiFi
> >and Apache MiNiFi.
> >  - Apache NiFi Nar Maven Plugin is a release artifact used for supporting
> >the NiFi classloader isolation model.
> >
> > ## Issues:
> >  - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >  - Based on board feedback in last report the descriptions above have
> been
> >simplified to avoid confusing child/subproject terminology.  We have
> >successfully conducted and completed name searches for the MiNiFi and
> >Registry efforts.
> >  - Conducted numerous releases as listed below.  The 0.7.x releases
> focused
> >on providing simple bug fixes and resolving reported CVEs.  The 1.x
> >releases brought about stability, performance improvements, and
> > addressed
> >reported CVEs.  Further, in the 1.x releases numerous substantive
> > features
> >were introduced including the ability to run multiple versions of the
> > same
> >components and support for both format and schema aware record
> > processors
> >to easily handle cases like acquisition, SQL based routing,
> enrichment,
> >conversion, and delivery of record oriented data.  These make many
> > common
> >record oriented use cases far more performant, intuitive, and retain
> the
> >full power of NiFi's provenance features.
> >
> > ## Health report:
> >  - Health of the community is strong and indicators of strength continue
> >trending in the right direction. Mailing list and JIRA activity is
> > strong.
> >ASF Hipchat is serving as an on-ramp for new users to our mailing list
> > and
> >JIRA systems. We continue to see new users and contributors. The PMC
> and
> >committer ranks grew again during this reporting cycle and the
> pipeline
> >is encouraging. We're generating many releases with new release
> managers
> >stepping up often. The team handles security reports swiftly and
> follows
> >ASF security team published processes effectively.
> >
> > ## PMC changes:
> >
> >  - Currently 22 PMC members.
> >  - New PMC members:
> > - Koji Kawamura was added to the PMC on Fri May 26 2017
> > - Pierre Villard was added to the PMC on Sun May 21 2017
> > - Yolanda Davis was added to the PMC on Wed May 17 2017
> >
> > ## Committer base changes:
> >
> >  - Currently 34 committers.
> >  - New commmitters:
> > - Marc Parisi was added as a committer on Thu Jun 01 2017
> > - Andrew M. Lim was added as a committer on Wed May 31 2017
> >
> > ## Releases:
> >
> >  - Apache NiFi 1.3.0 was released June 9 2017.
> >  - Apache NiFi 0.7.4 was released June 9 2017.
> >  - Apache NiFi MiNiFi (java) 0.2.0 was released May 19 2017.
> >  - Apache NiFi 0.7.3 was released May 19 2017.
> >  - Apache NiFi MiNiFi (cpp) 0.2.0 was released May 14 2017.
> >  - Apache NiFi 1.2.0 was released May 10 2017.
> >
> > ## Mailing list activity:
> >
> >  - Activity on the mailing lists remains extremely high with a mixture
> >of new users, contributors, and deeper more experienced users and
> >contributors sparking discussion and questions and filing bugs or
> >new features.
> >
> >  - us...@nifi.apache.org:
> > - 512 subscribers (up 39 in the last 3 months):
> > - 936 emails sent to list (846 in previous quarter)
> >
> >  - dev@nifi.apache.org:
> > - 367 subscribers (up 24 in the last 3 months):
> > - 1018 emails sent to list (925 in previous quarter)
> >
> >  - iss...@nifi.apache.org:
> > - 42 subscribers (up 4 in the last 3 months):
> > - 7936 emails sent to list (6592 in previous quarter)
> >
> >
> > ## JIRA activity:
> >
> >  - 573 JIRA tickets created in the last 3 months
> >  - 421 JIRA tickets closed/resolved in the last 3 months
> >
>

Re: [DRAFT][REPORT] Apache NiFi - July 2017

[Aldrin Piri]

Looks good.  Thanks for compiling this, Joe.

On Tue, Jul 4, 2017 at 9:50 AM, Joe Witt  wrote:

> Team,
>
> It's that time again to submit our board report for Apache NiFi.
> Please see below draft.  If you have any suggestions/fixes, edits
> please advise.
>
> I'll submit the report in a few days.
>
> Thanks
> Joe
>
> +_+_+_+_+_+_+_
>
> ## Description:
>  - Apache NiFi is an easy to use, powerful, and reliable system to
>process and distribute data.
>  - Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
>integrate with and leverage the command and control of NiFi. There are
>both Java and C++ implementations.
>  - Apache NiFi Registry is a centralized registry for key configuration
> items
>including flow versions, assets, and extensions for Apache NiFi
>and Apache MiNiFi.
>  - Apache NiFi Nar Maven Plugin is a release artifact used for supporting
>the NiFi classloader isolation model.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>  - Based on board feedback in last report the descriptions above have been
>simplified to avoid confusing child/subproject terminology.  We have
>successfully conducted and completed name searches for the MiNiFi and
>Registry efforts.
>  - Conducted numerous releases as listed below.  The 0.7.x releases focused
>on providing simple bug fixes and resolving reported CVEs.  The 1.x
>releases brought about stability, performance improvements, and
> addressed
>reported CVEs.  Further, in the 1.x releases numerous substantive
> features
>were introduced including the ability to run multiple versions of the
> same
>components and support for both format and schema aware record
> processors
>to easily handle cases like acquisition, SQL based routing, enrichment,
>conversion, and delivery of record oriented data.  These make many
> common
>record oriented use cases far more performant, intuitive, and retain the
>full power of NiFi's provenance features.
>
> ## Health report:
>  - Health of the community is strong and indicators of strength continue
>trending in the right direction. Mailing list and JIRA activity is
> strong.
>ASF Hipchat is serving as an on-ramp for new users to our mailing list
> and
>JIRA systems. We continue to see new users and contributors. The PMC and
>committer ranks grew again during this reporting cycle and the pipeline
>is encouraging. We're generating many releases with new release managers
>stepping up often. The team handles security reports swiftly and follows
>ASF security team published processes effectively.
>
> ## PMC changes:
>
>  - Currently 22 PMC members.
>  - New PMC members:
> - Koji Kawamura was added to the PMC on Fri May 26 2017
> - Pierre Villard was added to the PMC on Sun May 21 2017
> - Yolanda Davis was added to the PMC on Wed May 17 2017
>
> ## Committer base changes:
>
>  - Currently 34 committers.
>  - New commmitters:
> - Marc Parisi was added as a committer on Thu Jun 01 2017
> - Andrew M. Lim was added as a committer on Wed May 31 2017
>
> ## Releases:
>
>  - Apache NiFi 1.3.0 was released June 9 2017.
>  - Apache NiFi 0.7.4 was released June 9 2017.
>  - Apache NiFi MiNiFi (java) 0.2.0 was released May 19 2017.
>  - Apache NiFi 0.7.3 was released May 19 2017.
>  - Apache NiFi MiNiFi (cpp) 0.2.0 was released May 14 2017.
>  - Apache NiFi 1.2.0 was released May 10 2017.
>
> ## Mailing list activity:
>
>  - Activity on the mailing lists remains extremely high with a mixture
>of new users, contributors, and deeper more experienced users and
>contributors sparking discussion and questions and filing bugs or
>new features.
>
>  - us...@nifi.apache.org:
> - 512 subscribers (up 39 in the last 3 months):
> - 936 emails sent to list (846 in previous quarter)
>
>  - dev@nifi.apache.org:
> - 367 subscribers (up 24 in the last 3 months):
> - 1018 emails sent to list (925 in previous quarter)
>
>  - iss...@nifi.apache.org:
> - 42 subscribers (up 4 in the last 3 months):
> - 7936 emails sent to list (6592 in previous quarter)
>
>
> ## JIRA activity:
>
>  - 573 JIRA tickets created in the last 3 months
>  - 421 JIRA tickets closed/resolved in the last 3 months
>