Thanks Jeff - submitted edited report fixing 0.10.0 to 1.10.0 Andy the ratio value is auto generated by the report generation tool and has some specific intent for the board I guess. Not quite sure but I understand your point.
thanks On Wed, Oct 2, 2019 at 2:41 AM Jeff <[email protected]> wrote: > Joe, > > Thanks for submitting the report! I noticed in the Project Activity > section, Apache NiFi's next release candidate is specified for version > 0.10.0, instead of 1.10.0. > > On Wed, Oct 2, 2019 at 12:30 AM Andy LoPresto <[email protected]> > wrote: > > > Joe, > > > > Looks great. Thanks for putting this together. One comment: the commuter > > to PMC ratio is listed as 3:2 (44 to 30). I think the 44 number includes > > all PMC members as well, so I would present the ratio as 1:2. But perhaps > > I’m misunderstanding the point of that distinction. > > > > Andy LoPresto > > [email protected] > > [email protected] > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > > On Oct 1, 2019, at 19:00, Joe Witt <[email protected]> wrote: > > > > > > Team, > > > > > > Here is the board report I've submitted for us this October. Great > > > progress! > > > > > > For those familiar with the format we've typically used this is a bit > > > different. I used a new tool that helps structure and capture data for > > the > > > report a bit differently than the previous approach. We'll see what > the > > > feedback from the board is. > > > > > > 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 44 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. > > > - Rob Fellows was added as committer on 2019-09-24 > > > > > > ## Project Activity: > > > Released Apache NiFi Registry 0.5.0 providing better proxy permissions, > > > support for Apache Knox, and the ability to make buckets accessible by > > > anonymous users. > > > > > > Apache NiFi 0.10.0 will have a release candidate likely by the time of > > this > > > October board report. It includes more than 330+ JIRAs. This brings > > > powerful > > > features such as sourcing extensions from the latest NiFi Registry at > > > runtime, > > > far better model for paramaterized version controlled flows, Java 11 > > > compatibility, back pressure prediction and more. > > > > > > The release for MiNiFi CPP 0.7.0 is closing in. There are nearly 100 > > 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: > > > 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. > > > > > > As reported in the previous quarter we had 394 users in our slack room > > but > > > now > > > there are 523 and growing. This is a great sign of the interest in the > > > community and the engagement level we see across PMC, committer, and > > > pipeline > > > for future committers. > > > > > > We continue to see highly active use and commentary related to Apache > > NiFi > > > in > > > social media, meetups, blogs, and conferences in various parts of the > > > world. A > > > NiFi PMC member presented on NiFi at the recent ApacheCon in Vegas. A > > recent > > > tweet reads "Work with ApacheNiFi is very fast and productive. > Counting > > now > > > +290 processors to build both batch and streaming ETL data pipelines > for > > any > > > type of data source and destination you want." Another reads > "ApacheNiFi > > > thanks for the usual level of nonsensical obfuscated badly described > > prose > > > on > > > your homepage trying to describe your framework/product. As usual > > > obfuscation > > > is your the forte of the Apache Foundation..." Fortunately patches are > > > welcome. > > > > > > This quarter we're seeing higher engagement across mailing lists, JIRA > > > activity both opened and closed, commits, PRs opened and closed. This > is > > > likely due to the range of release activities for the NiFi Registry as > > well > > > as > > > the impending release of Apache NiFi 1.10.0 which is a huge feature, > bug > > > fix, > > > and improvement release representing one of the longer gaps we've ever > > had > > > since the previous feature bearing release. > > >
