Team, Here is what I've submitted for us for Oct. Thank you all again for all the great effort!
## 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. With the last board report JM continued the questions around communication channels and noted we should beware the auto closing stale PRs can be bad for community growth and that we should consider consolidating channels. Regarding auto close of PRs, we agree there is downside and this is why we've been slow to make changes here despite the clear challenges of action and inaction. We will eventually move beyond admiring this problem to some clear path with pros and cons. Regarding consolidation of the communication channels - we try to be where the community is. We use that presence to direct communications to the mailing list. Limiting spread to twitter, stackoverflow, etc.. is its own challenge as various community members have their own communication style and preferred channel. What we can influence is the convergence to channels we can as a community maturely support. It is going well overall but the popularity of the on-demand communication style of Slack is certainly significant. ## Membership Data: Apache NiFi was founded 2015-07-14 (5 years ago) There are currently 48 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Arpad Boda on 2020-05-24. - Marton Szasz was added as a committer on 2020-07-13 ## Project Activity: Apache NiFi 1.12.0 released on Aug 20 2020 with a stability release of Apache NiFi 1.12.1 following behind on Sep 29 2020. These releases include significant features, bug fixes, improvements, and resolved CVEs. Apache NiFi Maven Plugin Released on Sep 21 2020. This plugin helps Maven users building NiFi extensions take advantage of our classloader isolation model. Apache NiFi Registry 0.7.0 released on Jul 20 2020. Consistent with the last report there have not been any Apache NiFi MiNiFi Java releases in some time. What is happening now is https://issues.apache.org/jira/browse/MINIFI-422 which will merge MiNiFi Java back into NiFi as a headless form of NiFi supporting both broad use case patterns well and reduce the release/codebase burden. Important work is on going and almost made it into the NiFi 1.12 release but had to be reverted as it created regressions. Apache NiFi MiNiFi CPP 0.8.0 is in progress with over 92 issues resolved. ## Community Health: Mailing list activity returned to growth across each of our lists notably including dev with 15% growth and users with 8% growth this quarter. This is in terms of number of emails of course. We see strong growth in commit activity at 23% with 314 commits over that time speaking of just Apache NiFi itself. Along with that though we saw a decrease in Github PRs opened and closed on the order of a 10% decline. The Apache NiFi slack channel activity continues to grow with now over 1250 users dwelling in the general channel alone growing from 1071 in the previous quarter. Activity on twitter, stackoverflow, youtube, blogs remains interesting as it has for many quarters now. Our number of stale PRs has again grown and this remains an important topic for us to determine a path forward. We find community members are much more motivated in contributing PRs than they are in reviewing them. Though building a strong and broad reviewer base is important and indeed this is where people really learn the framework. We have not yet focused on resolving this problem as current options we see happening in other communities like auto-stale PR closure also have downsides as noted in the board feedback above.
