Team Below is what I've submitted to the board for this quarter. Thanks again!
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. ## Project Status: Current project status: Ongoing. High. Issues for the board: None. ## Membership Data: Apache NiFi was founded 2015-07-14 (9 years ago) There are currently 67 committers and 37 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Gabor Gyimesi on 2024-06-26. - No new committers. Last additional was Lehel Boer on 2024-06-16. ## Project Activity: The big push remains focused on making Apache NiFi 2.0.0 happen. We've completed four huge milestone releases to that and it looks likely our next release will be officially NiFi 2.0.0 and for GA usage. Toward making NiFi 2.0.0 official we've broken out into its own release the NiFi API which helps codify our core contract of backwards compatibility and points of extension for the project. We released the Apache NiFi API 2.0.0 on September 23, 2024. To leverage packaging NARs that understand the split of the NiFi API vs the core framework version now we also have the latest NiFi Nar Maven Plugin 2.1.0 as of Sep 26th. MiNiFi CPP continues to see JIRAs and PR activity as well. ## Community Health: JIRA and Mailing list activity remains consistent. The slack community grew by another 160 participants in the general channel alone increasing from 3,284 in our previous report and consistent with quarter over quarter growth for some time. Slack is generally quite busy with threads from people needing general user help or questions, development ideas, and review requests. As noted above we've split out the NiFi API. Part of this was so we can introduce a NiFI Improvement Process for changes to our core API. This process was inspired by the tremendous growth the communities of Kafka and Airflow have produced and these communities have healthy discussions on how to introduce changes to critical sections. We continue to produce frequent releases in the NiFi community and enjoy rather active vote participation. Releases we generate are substantial along all key dimensions of feature, improvements, bug fixes, and emphasis on security. The NiFi 2.0 release line is among the most vulnerability free we've ever had when it comes to dependency management. Mailing lists remain quite active despite the continued increase of activity in Slack.
