nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Burgess <>
Subject Re: Apache NiFi Jan 2020 Board Report
Date Tue, 07 Jan 2020 18:37:33 GMT
Looks good to me, thanks for putting this together Joe!

On Tue, Jan 7, 2020 at 1:32 PM Joe Witt <> wrote:
> Team,
> Here is the content of the board report I submitted for us this quarter.
> Again great progress!
> Thanks
> Joe
> ## Description:
> The mission of NiFi is the creation and maintenance of software related to
> providing 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.
> Apache NiFi Flow Design System is 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.
> ## Issues:
> There are no issues requiring board attention at this time.
> ## Membership Data:
> Apache NiFi was founded 2015-07-14 (4 years ago)
> There are currently 47 committers and 30 PMC members in this project.
> The Committer-to-PMC ratio is roughly 3:2.
> Community changes, past quarter:
> - No new PMC members. Last addition was Peter Wicks on 2019-05-29.
> - Dániel Bakai was added as committer on 2019-10-19
> - Kotaro Terada was added as committer on 2019-10-19
> - Peter Turcsanyi was added as committer on 2019-10-25
> ## Project Activity:
> We are nearing release of Apache NiFi Registry 1.0.0.  The release includes
> support for common HTTP security headers, running on Java 11, updated to
> Ranger 2.0, and more.
> Released Apache NiFi 1.10.0.  This brings powerful features such as sourcing
> extensions from the latest NiFi Registry at runtime, far better model for
> parameterized version controlled flows, Java 11 compatibility, back pressure
> prediction and more.
> In the release candidate phase of Apache NiFi 1.11.0 which provides a range
> of
> bug fixes, improvements and a handful of new features.  This release will
> solve class-loader isolation to include native libraries as well.
> The release for MiNiFi CPP 0.7.0 is still being worked.  There are nearly
> 140
> closed JIRAs including many bug fixes and new features such as ensuring all
> inbound sockets are TLSv1.2 or newer, cron driven scheduling, support
> Kerberized connections to Kafka, support for packages with Python scripts,
> and
> ability to capture individual frames from an RTSP camera stream.
> ## Community Health:
> We have seen about a 15% decline in users and dev mailing list activity this
> quarter. This is likely due to the growing use of Slack for more
> direct/responsive interaction as well as seasonal considerations. We also
> saw
> a roughly 40% decrease in JIRA related activity.  This is certainly related
> to
> the completion of the very significant Apache NiFi 1.10.0 release as well as
> seasonal aspects.
> We've brought in several new committers in this timeline and hopefully the
> current committer base leads to additional PMC members soon. The community
> remains active on numerous release lines as well. Community health continues
> to be a strong point with a healthy committer and PMC pipeline as well as
> high
> activity from current PMC members. We see numerous release lines across the
> mentioned parts of the Apache NiFi project all with very active development
> across features, bug fixes, and improvements. Our mailing list continues to
> be
> highly active and our slack room is also super active.
> For the past few quarters we've reported 394, 523, and now 707 persistent
> users in our slack channels. Interestingly we see more non committer based
> collaboration here than we have on the mailing lists. People seem to prefer
> the collaboration style of Slack quite a lot as well as more subject
> dedicated
> rooms to talk in. It isn't clear that this is leading to more committers and
> PMC members but does help the community in general.

View raw message