The Apache Software Foundation Board of Directors Meeting Minutes March 22, 2023 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:02 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://s.apache.org/b20230322 The meeting was held via teleconference, hosted by the Secretary via Zoom. The #asfboard channel on the-asf.slack.com was used for backup. 2. Roll Call Directors Present: Rich Bowen Shane Curcuru Bertrand Delacretaz Christofer Dutz Sharan Foga Willem Ning Jiang Justin Mclean Craig L Russell Sander Striker Directors Absent: none Executive Officers Present: Craig R. McClanahan Matt Sicker Ruth Suehle Executive Officers Absent: David Nalley Guests: Andrew Musselman Brian Proffitt Claude Warren Daniel Gruno Dave Fisher Gavin McDonald Greg Stein - joined :05 Jarek Potiuk - joined 1h5m Ken Coar - joined :07 Mark Radcliffe - joined :02 Mark Thomas Roman Shaposhnik Sally Khudairi 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of February 15, 2023 See: board_minutes_2023_02_15.txt Tabled. 4. Executive Officer Reports A. Board Chair [Sander Striker] Earlier this month we had our Annual Members Meeting. I am happy to note that we could invite 49 new Members and welcome back 1 emeritus Member. While the members had a good number of candidates to chose from that hadn't served before we ended up with a new board composed of individuals that had already served as director in a prior term: https://www.apache.org/history/directors.html I'd like to thank Sam Ruby for his commitment in serving on the board, and the contributions he has made during that time. Similarly I would like to thank Roy Fielding for the structure he brought as Chair and continued to bring after. Lastly I want to thank Roman for his contributions as director next to his role as VP, Legal Affairs. The process for the members meeting was different to prior years, and allowed for more time for voting. Personally I call the meeting a success and would like to continue down the path of making it more asynchronous. Several process improvements have been suggested after the meeting. I will follow up on these while there is momentum. Next month my focus is back on the board meetings. B. President [David Nalley] Additionally, please see Attachments 1 through 8. C. Treasurer [Craig R. McClanahan] Continued the process of dealing with vendor payable portals. This is becoming more important as we are trying to wind down usage of our Citizens Bank account, and several donor payments over the last year have been sent to that account – in spite of payment instructions on nearly every one of those invoices to send payments to TD Bank instead. Although this was a continued focus in February, an event in March was also important to understand the impacts of – the failure of Silicon Valley Bank (followed by problems with Signature Bank and First Republic, as well as internationally at Credit Suisse). A brief summary from our perspective: DIRECT IMPACTS: None. We had no funds in any of the affected banks. INDIRECT IMPACTS (VENDORS): We have significant relationships with several vendors, including ADP (Payroll), Bill.Com (outbound payments), Ramp (virtual and physical credit cards), as well as other options for receiving donations (such as Stripe). Of these vendors, Bill.Com was the most seriously impacted (having money on deposit at SVB), but say that things are back on track. INDIRECT IMPACTS (SPONSORS): We don’t have knowledge of which banks sponsors that might have had funds at risk. However, one sponsor did send an interesting note – suggesting that if any of *their* vendors had money at SVB, they should update bank details to send payments somewhere else, to avoid delays in receiving payments. OTHER IMPACTS (COMMUNITY, DEVELOPERS, MEMBERS): Again, we have no direct knowledge of such impacts, but it will benefit everyone to be cognizant that there might be issues. D. Secretary [Matt Sicker] In February, the secretary received 55 ICLAs and 3 membership emeritus requests. E. Executive Vice President [Ruth Suehle] FY24 budget process has begun. F. Vice Chair [Shane Curcuru] Assisted chair with Member's meeting related tasks and improving tooling and runbook to make next year smoother. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Sharan] No report was submitted. B. Apache Legal Affairs Committee [Roman Shaposhnik / Craig] See Attachment 10 C. Apache Security Team Project [Mark J. Cox / Christofer] See Attachment 11 D. VP of Jakarta EE Relations [Rob Tompkins / Justin] No report was submitted. Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Bahir [rbowen] # Jakarta EE Relations [clr] # MXNet [rbowen] # OpenNLP [curcuru] # SINGA [rbowen] A. Apache Airflow Project [Bolke de Bruin / Willem] No report was submitted. B. Apache Allura Project [David Philip Brondsema / Bertrand] See Attachment B C. Apache Ambari Project [Roman Shaposhnik / Craig] See Attachment C D. Apache Any23 Project [Lewis John McGibbney / Willem] No report was submitted. @Willem: follow up with Any23 on report/chair E. Apache Archiva Project [Olivier Lamy / Shane] No report was submitted. F. Apache Atlas Project [Madhan Neethiraj / Sander] See Attachment F G. Apache Axis Project [Robert Lazarski / Rich] See Attachment G H. Apache Bahir Project [João Boto / Craig] See Attachment H @Rich: pursue a roll call for Bahir I. Apache Beam Project [Kenneth Knowles / Rich] See Attachment I J. Apache Bigtop Project [Yuqi Gu / Craig] See Attachment J K. Apache Bloodhound Project [Gary Martin / Justin] See Attachment K L. Apache bRPC Project [James Ge / Shane] See Attachment L M. Apache BVal Project [Matthew Jason Benson / Christofer] See Attachment M N. Apache Camel Project [Andrea Cosentino / Sander] See Attachment N O. Apache Cayenne Project [Michael Ray Gentry / Sharan] See Attachment O P. Apache Celix Project [Pepijn Noltes / Bertrand] See Attachment P Q. Apache CloudStack Project [Simon Weller / Willem] See Attachment Q R. Apache Commons Project [Gary D. Gregory / Sander] See Attachment R S. Apache Cordova Project [Jesse MacFadyen / Craig] See Attachment S T. Apache cTAKES Project [Pei Chen / Willem] See Attachment T U. Apache Curator Project [Enrico Olivelli / Christofer] See Attachment U V. Apache Daffodil Project [Mike Beckerle / Bertrand] See Attachment V W. Apache ECharts Project [Wenli Zhang / Justin] See Attachment W X. Apache Felix Project [Karl Pauls / Shane] See Attachment X Y. Apache Flex Project [Olaf Krüger / Sharan] See Attachment Y Z. Apache Flink Project [Robert Metzger / Rich] See Attachment Z AA. Apache Gobblin Project [Abhishek Tiwari / Willem] See Attachment AA AB. Apache Gora Project [Kevin Ratnasekera / Sharan] See Attachment AB AC. Apache Guacamole Project [Mike Jumper / Christofer] See Attachment AC AD. Apache Gump Project [Stefan Bodewig / Shane] See Attachment AD AE. Apache Helix Project [Junkai Xue / Craig] No report was submitted. @Craig: pursue a roll call for Helix AF. Apache Hive Project [Naveen Gangam / Rich] See Attachment AF AG. Apache Hudi Project [Vinoth Chandar / Justin] See Attachment AG AH. Apache Iceberg Project [Ryan Blue / Sander] No report was submitted. @Sander: pursue a roll call for Iceberg AI. Apache Incubator Project [Justin Mclean / Bertrand] See Attachment AI AJ. Apache IoTDB Project [Xiangdong Huang / Sander] See Attachment AJ AK. Apache Jackrabbit Project [Marcel Reutegger / Craig] See Attachment AK AL. Apache Karaf Project [Jean-Baptiste Onofré / Bertrand] See Attachment AL AM. Apache Kyuubi Project [Kent Yao / Rich] See Attachment AM AN. Apache Linkis Project [Shuai Di / Justin] See Attachment AN AO. Apache Lucene Project [Greg Miller / Willem] See Attachment AO AP. Apache Lucene.Net Project [Shad Storhaug / Sharan] No report was submitted. @Sharan: pursue a roll call for Lucene.Net AQ. Apache Mnemonic Project [Yanhui Zhao / Christofer] No report was submitted. AR. Apache MXNet Project [Sheng Zha / Shane] See Attachment AR @Justin: pursue a roll call for MXNet AS. Apache Mynewt Project [Szymon Janc / Willem] See Attachment AS AT. Apache NetBeans Project [Geertjan Wielenga / Sander] See Attachment AT AU. Apache OFBiz Project [Jacopo Cappellato / Sharan] See Attachment AU AV. Apache Olingo Project [Michael Bolz / Rich] See Attachment AV AW. Apache OODT Project [Imesha Sudasingha / Bertrand] No report was submitted. @Bertrand: pursue a potential Attic resolution for OODT AX. Apache OpenNLP Project [Jeff Zemerick / Shane] See Attachment AX @Shane: follow up with OpenNLP around issue raised in report AY. Apache OpenWebBeans Project [Mark Struberg / Christofer] No report was submitted. AZ. Apache Pig Project [Koji Noguchi / Craig] No report was submitted. BA. Apache Pinot Project [Kishore G / Bertrand] See Attachment BA BB. Apache Pivot Project [Roger Lee Whitcomb / Justin] No report was submitted. BC. Apache PLC4X Project [Christofer Dutz] See Attachment BC BD. Apache Portable Runtime (APR) Project [Yann Ylavic / Willem] See Attachment BD BE. Apache Portals Project [Neil Griffin / Rich] See Attachment BE BF. Apache Pulsar Project [Matteo Merli / Justin] See Attachment BF BG. Apache Roller Project [David M. Johnson / Sharan] See Attachment BG BH. Apache Royale Project [Piotr Zarzycki / Shane] See Attachment BH BI. Apache Sedona Project [Jia Yu / Bertrand] See Attachment BI BJ. Apache ServiceMix Project [Krzysztof Sobkowiak / Christofer] No report was submitted. BK. Apache Shiro Project [Brian Demers / Craig] See Attachment BK BL. Apache SINGA Project [Wang Wei / Sander] See Attachment BL BM. Apache Sling Project [Robert Munteanu / Sander] See Attachment BM BN. Apache SpamAssassin Project [Sidney Markowitz / Shane] See Attachment BN BO. Apache Storm Project [P. Taylor Goetz / Sharan] See Attachment BO BP. Apache Submarine Project [Liu Xun / Bertrand] No report was submitted. BQ. Apache Synapse Project [Isuru Udana / Craig] No report was submitted. BR. Apache Tomcat Project [Mladen Turk / Christofer] No report was submitted. BS. Apache TomEE Project [David Blevins / Justin] See Attachment BS BT. Apache TVM Project [Tianqi Chen / Willem] See Attachment BT BU. Apache UIMA Project [Richard Eckart de Castilho / Rich] See Attachment BU BV. Apache Unomi Project [Serge Huber / Justin] See Attachment BV BW. Apache VCL Project [Josh Thompson / Sander] See Attachment BW BX. Apache Wicket Project [Andrea Del Bene / Shane] See Attachment BX BY. Apache Xerces Project [Michael Glavassevich / Rich] See Attachment BY BZ. Apache Yetus Project [Allen Wittenauer / Sharan] See Attachment BZ CA. Apache Zeppelin Project [Lee Moon Soo / Christofer] See Attachment CA CB. Apache ZooKeeper Project [Flavio Paiva Junqueira / Bertrand] See Attachment CB Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Flex Project Chair WHEREAS, the Board of Directors heretofore appointed Olaf Krüger (okrueger) to the office of Vice President, Apache Flex, and WHEREAS, the Board of Directors is in receipt of the resignation of Olaf Krüger from the office of Vice President, Apache Flex, and WHEREAS, the Project Management Committee of the Apache Flex project has chosen by vote to recommend Harbs (harbs) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Olaf Krüger is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Flex, and BE IT FURTHER RESOLVED, that Harbs be and hereby is appointed to the office of Vice President, Apache Flex, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Flex Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Zeppelin Project Chair WHEREAS, the Board of Directors heretofore appointed Lee Moon Soo (moon) to the office of Vice President, Apache Zeppelin, and WHEREAS, the Board of Directors is in receipt of the resignation of Lee Moon Soo from the office of Vice President, Apache Zeppelin, and WHEREAS, the Project Management Committee of the Apache Zeppelin project has chosen by vote to recommend Jongyoul Lee (jongyoul) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Lee Moon Soo is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Zeppelin, and BE IT FURTHER RESOLVED, that Jongyoul Lee be and hereby is appointed to the office of Vice President, Apache Zeppelin, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache Zeppelin Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache EventMesh Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a fully serverless platform used to build distributed event-driven applications; NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache EventMesh Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache EventMesh be and hereby is responsible for the creation and maintenance of software related to a fully serverless platform used to build distributed event-driven applications; and be it further RESOLVED, that the office of "Vice President, Apache EventMesh" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache EventMesh Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache EventMesh Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache EventMesh Project: * Eason Chen * Junping Du * Von Gosling * Du Heng * XiaoShuang Li * Weiqiang Liang * Alex Luo * Justin Mclean * Jean-Baptiste Onofré * Francois Papon * Wenjun Ruan * ShannonDing * Xue Weiming * Yuwei Zhu NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed to the office of Vice President, Apache EventMesh, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. RESOLVED, that all responsibilities pertaining to the Apache Incubator EventMesh podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7C, Establish the Apache EventMesh Project, was approved by Unanimous Vote of the directors present. D. Change the Apache CloudStack Project Chair WHEREAS, the Board of Directors heretofore appointed Simon Weller (sweller) to the office of Vice President, Apache CloudStack, and WHEREAS, the Board of Directors is in receipt of the resignation of Simon Weller from the office of Vice President, Apache CloudStack, and WHEREAS, the Project Management Committee of the Apache CloudStack project has chosen by vote to recommend Rohit Yadav (rohit) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Simon Weller is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache CloudStack, and BE IT FURTHER RESOLVED, that Rohit Yadav be and hereby is appointed to the office of Vice President, Apache CloudStack, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache CloudStack Project Chair, was approved by Unanimous Vote of the directors present. E. Change the Apache Solr Project Chair WHEREAS, the Board of Directors heretofore appointed Houston Putman (houston) to the office of Vice President, Apache Solr, and WHEREAS, the Board of Directors is in receipt of the resignation of Houston Putman from the office of Vice President, Apache Solr, and WHEREAS, the Project Management Committee of the Apache Solr project has chosen by vote to recommend David Smiley (dsmiley) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Houston Putman is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Solr, and BE IT FURTHER RESOLVED, that David Smiley be and hereby is appointed to the office of Vice President, Apache Solr, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Change the Apache Solr Project Chair, was approved by Unanimous Vote of the directors present. F. Establish the Apache Flagon Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to thin-client behavioral logging capability useful for business analytics, usage analytics, usability and user testing; NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Flagon Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Flagon Project be and hereby is responsible for the creation and maintenance of software related to thin-client behavioral logging capability useful for business analytics, usage analytics, usability and user testing; and be it further RESOLVED, that the office of "Vice President, Apache Flagon" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Flagon Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Flagon Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Flagon Project: * Joshua Poore * Lewis John McGibbney * David Meikle * Tim Allison * Furkan Kamaci * Steve York * Michelle Beard * Robert Foley * Austin Bennett * Gedd Johnson NOW, THEREFORE, BE IT FURTHER RESOLVED, that Joshua Poore be appointed to the office of Vice President, Apache Flagon, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. RESOLVED, that all responsibilities pertaining to the Apache Incubator Flagon podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7F, Establish the Apache Flagon Project, was approved by Unanimous Vote of the directors present. G. Change the Apache ServiceComb Project Chair WHEREAS, the Board of Directors heretofore appointed Willem Ning Jiang (ningjiang) to the office of Vice President, Apache ServiceComb, and WHEREAS, the Board of Directors is in receipt of the resignation of Willem Ning Jiang from the office of Vice President, Apache ServiceComb, and WHEREAS, the Project Management Committee of the Apache ServiceComb project has chosen by vote to recommend Bao Liu (liubao) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Willem Ning Jiang is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache ServiceComb, and BE IT FURTHER RESOLVED, that Bao Liu be and hereby is appointed to the office of Vice President, Apache ServiceComb, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7G, Change the Apache ServiceComb Project Chair, was approved by Unanimous Vote of the directors present. H. Reboot the Apache MADlib Project PMC WHEREAS, the MADlib Project Management Committee (PMC) has fewer than 3 active members left, which is not enough to operate; and WHEREAS, several active MADlib committers and users (including two ASF members) have agreed to form a new PMC to help bring the project back to working status; NOW, THEREFORE, BE IT RESOLVED that the MADlib PMC is re-established, with the persons listed immediately below appointed to serve as its members: * Ed Espino * Venkatesh Raghavan * David Kimura * Roman Shaposhnik * Orhan Kislal * Nikhil Kak * Ekta Khanna * Atri Sharma * Hansome Yuan * Chris Hajas * Gregory Chase * Jingyu Wang NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ed Espino be appointed to the office of Vice President, Apache MADlib, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that current members of the MADlib PMC who are not included in the above list of members are discharged from any responsibilities pertaining to the MADlib PMC. Special Order 7H, Reboot the Apache MADlib Project PMC, was tabled. I. Change the Apache Cassandra Project Chair WHEREAS, the Board of Directors heretofore appointed Michael Semb Wever (mck) to the office of Vice President, Apache Cassandra, and WHEREAS, the Board of Directors is in receipt of the resignation of Michael Semb Wever from the office of Vice President, Apache Cassandra, and WHEREAS, the Project Management Committee of the Apache Cassandra project has chosen by vote to recommend Josh McKenzie (jmckenzie) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Michael Semb Wever is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Cassandra, and BE IT FURTHER RESOLVED, that Josh McKenzie be and hereby is appointed to the office of Vice President, Apache Cassandra, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7I, Change the Apache Cassandra Project Chair, was approved by Unanimous Vote of the directors present. J. Change the Apache OpenOffice Project Chair WHEREAS, the Board of Directors heretofore appointed Jim Jagielski (jim) to the office of Vice President, Apache OpenOffice, and WHEREAS, the Board of Directors is in receipt of the resignation of Jim Jagielski from the office of Vice President, Apache OpenOffice, and WHEREAS, the Project Management Committee of the Apache OpenOffice project has chosen by vote to recommend Dave Fisher (wave) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jim Jagielski is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache OpenOffice, and BE IT FURTHER RESOLVED, that Dave Fisher be and hereby is appointed to the office of Vice President, Apache OpenOffice, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7J, Change the Apache OpenOffice Project Chair, was approved by Unanimous Vote of the directors present. K. Change the corporate logo WHEREAS, a significant number of Members have expressed concern about our corporate logo, and its potential confusion with the Apache Nation; and WHEREAS, a change to our corporate logo could reduce the potential confusion; NOW, THEREFORE, BE IT RESOLVED, that the President shall direct the VP of Marketing and Publicity to develop, deploy, distribute, and promulgate a new logo that affirms the Foundation's mission of creation or maintenance of "open-source" software for distribution to the public at no charge, but which no longer associates with imagery of the Apache Nation. Special Order 7K, Change the corporate logo, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Election of Board Chair and Vice Chair At the first Board meeting after its election, the Board reviews Board Chair and Vice Chair appointments. The board appoints Sander Striker as Board Chair and Sharan Foga as Vice Chair. B. Board Calendar Determine the best time for the board meeting. Proposal: - April-September 21:00 UTC - October-March 22:00 UTC The April meeting will be scheduled soon while the remaining ones will be scheduled in the next board meeting. C. Use of the Board communications channels Briefly check that we have consensus on how we use our various channels for Board communications. D. Executive Session (22:45 UTC) Audience: Directors, Secretary Discussion of vendor controlled projects and what we might do to address them. The board discussed vendor neutrality of PMCs. The board will provide guidelines on the role of PMC chairs. The board decided to reach out to one particular PMC chair. 9. Review Outstanding Action Items * Roman: pursue a PMC roll call for Mahout [ Mahout 2023-01-18 ] Status: Done: roll call completed and PMC is active * Willem: pursue a new PMC chair for Any23 [ Any23 2023-02-15 ] Status: * Rich: shepherd a relationship with jclouds [ Brooklyn 2023-02-15 ] Status: Done: While a number of people have said that they're interested in stepping up to breathe life back into jclouds, nobody has actually done anything. It's looking like jclouds is going to attic, and Brooklyn (and possibly other projects?) will need to fork just the part of it that they rely on. * Rich: follow up with Giraph around absent PMC Chair [ Giraph 2023-02-15 ] Status: Done: Giraph chair has resurfaced, and says that their PMC email was being filtered to a folder where it was being ignored. They've been encouraged to mention on dev@ and/or user@ that there's the potential of going to the attic. However, neither of those lists has received any email since July, so it seems unlikely that there's going to be any interest. * Roman: follow up on pending interested PMC members to MADlib [ MADlib 2023-02-15 ] Status: Done: Resolution to reboot the Apache MADlib PMC submitted * Bertrand: pursue a roll call for OODT [ OODT 2023-02-15 ] Status: Roll call request sent on on March 21 to private@oodt.a.o. As of 14 hours before our March meeting, two replies from PMC members indicate a desire to move OODT to the Attic, https://s.apache.org/oodt-2023-03 * Roman: follow up with Subversion about VP Legal request [ Subversion 2023-02-15 ] Status: 10. Unfinished Business 11. New Business A. Review Renaming of ApacheCon to Community Over Code [requested by akm] The decision to rename ApacheCon was made without informing or getting the blessing of the Membership. This can be seen as a premature change given that the discussion of branding changes for the Foundation are in early stages. ApacheCon is a highly visible part of ASF outreach, and for many Members and Committers is an important part of the valuable branding of the Foundation. 12. Announcements 13. Adjournment Adjourned at 23:39 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period February 2023 * ISSUES FOR THE BOARD None. * OPERATIONS Responded to the following queries, liaising with projects as required: - Discovered there are BRAND and TM Jira project with some open issues. The Jira projects has been made read-only. The issues were reviewed, spam deleted and open issues moved to trademarks@ and then closed. - Provided advice regarding the "... for Apache Foo" naming style - wave restarted the work to update the list of marks on the website - provided advice to DATALAB regarding use of the full project name - discussed future registration options for COMMUNITY OVER CODE with VP Conferences * REGISTRATIONS Counsel attended a hearing in India regarding our request to extend our international registration for APACHE to India. The court will issue a decision in due course. APACHE DOLPHIN SCHEDULER has been registered in China. Worked to counsel on the assignment of NUTTX to the ASF. * INFRINGEMENTS Continued to work with counsel regarding a registration that potentially conflicts with our CASSANDRA mark in Columbia. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a --New: no new Sponsors have been onboarded during this timeframe. b --Renewals: one Platinum and five Bronze Sponsors have confirmed their renewals. c --Payments: 1 --New: we have not received payments from new Sponsors at this time. 1a --Incoming: we await payment from one Bronze Sponsor. 2 --Renewing: we received payment from one renewing Gold, and one Silver Sponsor. 2a --Incoming: we await payment from three Platinum, one Gold, one Silver, and five Bronze Sponsors. We await a purchase order to invoice one renewing Silver Sponsor. 2) Targeted Sponsors: we have set up the in-kind invoicing for a renewing Targeted Platinum Sponsor. We are finalizing our annual Targeted Sponsor audit. 3) Sponsor Relations: outreach continues to engage with new Sponsor points-of-contact and ensure renewals are processed smoothly. Several of our China-based Sponsors have now responded regarding the techno-trade impact on future renewals. 4) Event Sponsorship: we await notice from members of the Conferences Planning committee regarding future events. We are helping with collections on a few outstanding sponsorship payments from ApacheCon NA. 5) Individual Donations and Corporate Giving: we received $22.1K in individual and one-time corporate donations, which included two repeat annual corporate contributions. 6) Administrivia: we are working with the Treasurer and Accounting teams to resolve remaining Sponsor invoicing and payments issues. We continue to make progress with customizing the new Fundraising CMS. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] General ======= M&P is focused on improving existing procedures for TLP graduation releases and the annual report; updating the look, feel, and navigation of the apache.org web site; and responding to the Board's request to research information on rebranding options. Highlights ========== - FY2022 annual report report released - TLP announcements for Sedona and Steampipes - Community Over Code event and CfP announced - FOSSDA launch with ASF support - Website changes implemented - Feb social media report - Rebranding options gathered, M&P's proposal FY2022 Annual Report ===================== The (very delayed) FY2022 ASF annual report was posted to the apache.org site on Mar 7. A new process for getting the FY2023 report out in a much more timely manner will be launched and this month, so we can get back on track with annual report timing. Graduation releases ======================== TLP announcements for Sedona and Steampipes were made, via press release, blog posts, and social media. A new procedure streamlining the creation of graduation press releases was shared with the Incubator PMC this month, which should make the press releases more standardized for all TLP graduates, and ensure timely announcements. Community Over Code event announcement ================= Coordinating with VP, Conferences, the new Community Over Code event for North America was announced via press release, blog post, social media, and new event website (https://communityovercode.org/). The flagship event (formerly known as ApacheCon) will be held on Oct. 7-10, 2023 in Halifax, Nova Scotia. FOSSDA launch ================= Last month, the Free and Open Source Stories Digital Archive Foundation (FOSSDA) announced the launch of the FOSSDA Project to create digital recordings and archives of open source history. As an early supporter and participant of the project, the ASF took an active role in publicizing the launch. ASF teamed with its marketing partner, Constantia.io, to help FOSSDA create a communications strategy around the launch. Together, we drafted a press release, targeted media outreach list, and guidelines to help the FOSSDA Project leadership team post, pitch, and amplify the news. Website changes ================= On Feb 17, the Constantia team implemented an organizational change to the main apache.org web site, which was not easy to navigate. A new, simpler navigation scheme has been created, with these four goals in mind: * Help newcomers orient and get started with ASF * Help current contributors/committers find the resources they need * Incentivize people to incubate projects * Incentivize organizations to sponsor ASF Social media: Feb 2023 ================= Constantia's work around social media has been very effective, with a 89.1% increase in impressions on @TheASF Twitter account. LinkedIn impressions are up 7% in the same period. Rebranding options ================= Responding to a directive from the Board, via the President, M&P began researching options on what it could take to implement a rebranding of the ASF. As directed by the Board, the scope of such a rebranding operation could include: * Creating new imagery for our top-level brand * Updating the About and About Our Name pages to reflect our current position on the Apache name. Elements of this plan could also include: * Guidelines on the use of "ASF" as a referent to the Apache Software Foundation in formal press releases, reports, and informal use. * Guidelines on the naming and branding of constituent ASF projects. Note: this could be rebranding everything, or perhaps establishing guidelines for future projects. * Updating the "Trillions and Trillions Served" video Based on these parameters, here are the options available to the a rebranding effort: ## Phase I Deliverables * Creative brief * Logo design package * Updated brand guide Option 1 - This is a more lightweight process that involves fewer stakeholders. Constantia researches and summarizes ASF culture and identity from existing materials (e.g., ASF website and other resources such as the "Trillions" video). We would then present initial findings to a small, select group of stakeholders for validation and input - then deliver a Creative Brief. Once Creative Brief is approved, Constantia's graphic designer would give us dozens of ideas that we’d whittle down with the stakeholder group with up to 10 iterations. Process would take 3-6 weeks. Option 2 - This is a longer, more traditional process for visual brand design with a design partner that involves more stakeholders – more consensus-driven, if that’s a priority. We would host ~10 stakeholder interviews with individuals and/or groups of people selected by ASF M&P through an RFP process to capture thoughts on ASF’s culture and identity to produce a Creative Brief. Once approved, the selected design firm would present up to 10 options that we’d then finalize with up to five iterations. Process would take 6-15 weeks. ### Trillions and Trillions Served video updates Separate from Constantia, M&P approached the producers and director of the "Trillions" video (and the three additional videos in the series), to determine their recommended course of action. Their recommendation: * Change the visuals of the four movies that were produced for the ASF. The changes consists of the following sub-tasks * Replace the visuals according to the requirements by the ASF, assuming that the new visuals will be provided by the ASF * Re-export the movies * Review and if necessary minor adjustments incl. another export * Overall production effort * Add a disclaimer ahead of the movies explaining, that the ASF is in the process of re-branding or if the re-branding has been completed, then add a disclaimer explaining the re-branding, in respect to what has been changed since the movies have been produced. Time estimation is 4-10 hours for all four movies. ## Phase II Deliverables Some sub-brands will need to be changed e.g., "Powered By", "Support ASF", etc. If the Board feels constituent projects' sub-brands would also need changed, that was also included in this proposed plan. * Audit of brand updates needed tiered from “vital” to “nice to have” including, but not limited to: Website (this will be significant - both visually and textually); Foundation sub-brands (e.g., "Powered By", "Support ASF", etc.); and (if included) Project logos (e.g., Spam Assassin, Server Project). * Asset updates: Updating of sub-brand items above; creation of a brand library including templates for branded graphics accessible to Foundation and projects; recommend copy updates for the website. * Implement changes to brand properties to go live at an agreed-upon time. * Stakeholder guidebook for timeline and implementation (e.g., projects, sponsors, end users). Constantia could also help with stakeholder outreach if this isn’t something ASF has capacity to do. The goal of this phase is to create and execute a plan for implementing the changes, giving stakeholders enough advance notice to comply (e.g., sponsors, projects). We would first complete an audit of existing brand updates needed, update related assets, then implement the changes on Foundation brand properties at an agreed upon time. We would also create a simple guidebook for stakeholder compliance, and can help with outreach as needed. The timeline and pricing for this is our best guess based on initial research of what the audit may reveal. Process: 1-2 weeks for audit, 2-6 weeks for asset updates, 2-4 weeks for implementation, 1 week for stakeholder guidebook. ## Phase III Deliverables * “Next 25 Years” campaign to introduce logo and generate excitement for ASF and the next 25 years. * Brand starter kit for new projects including standardized logo “template” so they don’t have to create their own logo if it’s not a priority for them. The campaign would be part of Contantia's regular retainer – it would be their launch for the new brand to get people excited about it. The “brand starter kit” is a one-time design project to give any incubating projects a standard way of leveraging the ASF brand, also could be part of their retainer. Process: ongoing. ** M&P's proposal Even though it is the more costly and time-consuming option, it is my recommendation that we should undertake Option 2 of Phase I, because it is a more collaborative and community-focused path and befits the culture of the ASF, to change the main branding of the ASF. We want as much community participation and buy-in as possible. I would like to additionally propose that for Phase II, non-optional sub branding also be changed, and a stakeholder's guide be created around all of the new branding. For the project's branding: M&P proposes that all project logos be audited for the use of Native American imagery and naming, and subsequent changes be initiated. Finally: it is my recommendation that new TLP projects begin the use of the term "ASF _Project Name_," at a time to be set by the Board. This would include any projects "un-atticed" back to TLP status. ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Myrle Krantz] General ======= Infrastructure is operating as expected, and has no current issues requiring escalation to the President or the Board. Finances ======== - FY24 Budget process has begun. Short Term Priorities ===================== - Make our team meetup a success. - LDAP cutover to newer system and ACLs. Long Range Priorities ===================== - Switch to Bitwarden (for Infra and other ASF Officers) - Launch the Artifacts Distribution Platform General Activity ================ - New self-serve portal has launched. This is newer tech (similar to other server-based webapps Infra has), making it easier to maintain and to add future features. - The new self-serve is also used for an improved workflow for people to request a Jira account. It is now clearer and less work to request an account, less work for PMC members to review and approve creation of the Jira account. - Implemented new policy for GitHub PRs from outside contributors to require explicit approval before building/running the PR code using our GitHub Action allocation (think: uncontrolled usage; also some security concerns). Default is now that each PR must be approved, though some projects have opted for first-approval implies automatic future approval. - The Infra team helped set up and run our Apache STeVe instance for the Annual Members Meeting. The process completely successfully, and a couple runbooks were updated for Chair and Infra actions. - Blogs migration from Apache Roller to PMC-based choices continues. - TravisCI has been turned off, and Travis,Inc has been notified we will not renew our contract. Most projects converted to GitHub Actions (the two build systems are very similar). - Continued work on Gradle Enterprise and migration to the cloud versions of the Atlassian products. - New subversion server stood up. - Put together a request for cloud credits from one of our major sponsors. Should hear back later this week. - Work continues on the Agenda Tool, which should be ready for testing and use for the April Board meeting. - We plan to switch from LastPass to Bitwarden due to continuing issues with LP. We have solid references that BW is a better service. We have decided to use their hosted service rather than an on-premise installation. - Preparation for the Infra Team Meetup in Nashville, TN from April 13th to the 18th. - Implementing an autopatch/reboot process for project VMs. Build nodes for Jenkins and Buildbot got their own automated system. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] I’m excited to share that today the Apache Software Foundation announced the next iteration of its flagship event, ApacheCon, as we reach our 25th year of the event. The event, now named “Community Over Code,” will be the annual convention of the ASF, offering a chance for the community to gather in person and showcase content from many of the project communities at the ASF. More details at https://news.apache.org/foundation/entry/announcing-our-annual-event-community-over-code An Asia event is also being planned. The in-person conference will be held in Beijing China from August 18th to August 20th. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] === Current Events ============== Applications are open for Buzzwords Berlin. Judges to be chosen. Travel Policy ========== Submitted Policy awaiting approval by President and/or EVP TAC Sub Domain ============== tac.apache.org is now up, based on Jekyll. Adding more content is in progress. TAC App ======= TAC app is open for Buzzwords Berlin Future Events ============= Question sets being prepped for Community over Code coming in October, applications to open next month. Short/Medium Term Priorities ===================== Still keeping an eye out for other smaller events to support. We are keen to hear about projects events. Mailing List Activity ===================== No email activity this month. Membership ========== No changes to the membership this month ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas] ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 9: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] Past month has been pretty calm. Committee members took good care of resolving most issues on time. After resolving a handful of LEGAL issues, we are slightly up at 22 outstanding issues compared to 21 last month. ----------------------------------------- Attachment 11: Report from the Apache Security Team Project [Mark J. Cox] - We continue working with projects to publish 'security model' pages on their websites, which help users understand what to expect from the project security-wise and security researchers on where to best focus their efforts. In February such a page was published for Apache JMeter. - We have been reviewing the CPE's that were assigned to our CVE's by NIST's NVD programme, and suggesting fixes to some inconsistencies/misclassifications we identified. - We have done a similar review of the GitHub Security Advisory (GHSA) database, but found no inaccuracies here yet. - We have started taking inventory of how Apache scores in the OpenSSF Scorecards project. We plan to improve these, both by providing Apache projects insight and actionable suggestions, and by improving the tool. - We continue to work on https://cveprocess.apache.org, bringing our fork under the Apache GitHub organisation and sharing and documenting its deployment process. - We worked with the infra team to improve some security features on www.apache.org that are sometimes flagged by security researchers. Stats for February 2023: 23 [support request/question not security notification]] 20 [license confusion] 4 [report/question relating to dependencies] Security reports: 71 (last months: 59, 62, 84) 8 ['airflow'] 7 ['website or other infrastructure'] 6 ['tomcat'] 4 ['logging'] 3 ['commons', 'hadoop', 'httpd', 'openoffice'] 2 ['hive', 'inlong', 'kafka', 'superset', 'trafficserver'] 1 ['activemq', 'archiva', 'carbondata', 'cloudstack', 'couchdb', 'dolphinscheduler', 'druid', 'geode', 'guacamole', 'ibb', 'infra', 'iotdb', 'jspwiki', 'linkis', 'nifi', 'pdfbox', 'qpid', 'shenyu', 'shiro', 'sling', 'streampark', 'streampipes', 'submarine', 'zeppelin'] In total, as of 1 March 2023, we're tracking 154 (last months: 156, 160) open issues across 52 projects, median age 91 days (last months: 83, 59 days). 54 of those issues have CVE names assigned. 8 (last month: 7) of these issues, across 6 projects, are older than 365 days. ----------------------------------------- Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins] ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ----------------------------------------- Attachment B: Report from the Apache Allura Project [David Philip Brondsema] ## Description: The mission of Apache Allura is the creation and maintenance of software related to a software development infrastructure platform commonly known as a "forge" ## Issues: - No issues needing board attention. ## Membership Data: Apache Allura was founded 2014-03-18 (9 years ago) There are currently 17 committers and 17 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Guillermo Cruz on 2021-11-09. - No new committers. Last addition was Guillermo Cruz on 2021-11-09. ## Project Activity: - various linting improvements and warning fixes - Content-Security-Policy header support is stabilized now - library upgrades - minor other changes ## Community Health: - Last release was 1.14.0 on 2022-09-23 - Mailing list activity is ticket updates, and discussions from tickets - Fairly quiet and uninteresting the past few months ----------------------------------------- Attachment C: Report from the Apache Ambari Project [Roman Shaposhnik] ## Description: The mission of Apache Ambari is the creation and maintenance of software related to Hadoop cluster management ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ambari was founded 2022-06-15 (9 months ago) There are currently 19 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - Yu Hou was added as committer on 2023-03-04 ## Project Activity: - ambari-metrics-3.0.0 was released on 2023-03-13. - ambari-2.7.7 was released on 2022-12-11. ## Community Health: We did a lot of code forward-port work in 2022 Q4, but in 2023 Q1, we entered a normal development rhythm, so the reduction in the number of commits is within the expected range. We are actively preparing for the joint Meetup with other communities. There's a discussion about the new Ambari website. Ambari 2.8.0 is almost ready to release. ----------------------------------------- Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney] ----------------------------------------- Attachment E: Report from the Apache Archiva Project [Olivier Lamy] ----------------------------------------- Attachment F: Report from the Apache Atlas Project [Madhan Neethiraj] ## Description: The mission of Apache Atlas is the creation and maintenance of software related to a scalable and extensible set of core foundational governance services - enabling enterprises to effectively and efficiently meet their compliance requirements ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Atlas was founded 2017-06-20 (6 years ago) There are currently 47 committers and 32 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 Ashutosh Mestry on 2019-04-16. - No new committers. Last addition was Mandar Ambawane on 2022-09-12. ## Project Activity: - released Python client 0.0.13 - updated versions of Spring-security, Netty, Swagger, Jettison, Snakeyaml, Tinkerpop - UI fixes in handling of deleted entities - fix to address failure in admin audit APIs due to missed index creation ## Community Health: - dev@atlas.apache.org had a 22% decrease in traffic in the past quarter (680 emails compared to 868) ## Most Recent releases: 2.3.0 was released on 2022-12-06 2.2.0 was released on 2021-08-17 2.1.0 was released on 2020-07-15 0.8.4 was released on 2019-06-21 ----------------------------------------- Attachment G: Report from the Apache Axis Project [Robert Lazarski] # Apache Axis Board Report ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues There are no issues requiring board attention at this time. ## Membership Data: Axis was created on 2001-01-19 (22 years ago). There are currently 63 committers and 62 PMC members in this project, a vote in 2010 made all committers automatically PMC members. One PMC member resigned. Community changes, past quarter: - Currently 62 PMC/ 63 Committers members. - No new committers were added in the last 90 days, last committer added was Bill Blough on December 7th 2017 who also was added to the PMC on May 9th 2018. ## Project Activity: Recent releases: - Axis 2/Java 1.8.2 was released on July 14, 2022. - Axis 2/Rampart 1.7.1 was released on July 30, 2017. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Health report: Work continues on the upcoming release of our sub-project Rampart, an implementation of WS-Security standards that are quite old now. Rampart was last released in 2017. No active committers have maintained the project much since. However, we did receive a patch fron the community that renewed interest in development. As it turns out some important dependencies were not addressed in the patch and the changes required are enormous - namely upgrading OpenSAML from 2.x to 4.3.0 and Apache WS-WSS4J from 1.6 to 3.0.0. We'll have commits in the next few days showing progress. See RAMPART-449 for the full discussion. We may have a potential committer. For the upcoming quarter concerning Axis2, we'll be looking for some type of path forward to culminate the move from javax packages to jakarta. There is a strong interest for jakarta packages within the Axis community. See AXIS2-6051. While we tried to get ahead of this in AXIOM-506 a few years back, that effort is stalled for the moment. Our goal this quarter is to figure something out. Axis2 C PMC member Bill Blough continues to help users on the mailing list and he also participates in release votes. ## Axis2 java Jira issues opened in the last 90 days: 3 ## Axis2 java Jira issues closed in the last 90 days: 1 ----------------------------------------- Attachment H: Report from the Apache Bahir Project [João Boto] ## Description: Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Currently, Bahir provides extensions to multiple distributed analytic platforms, extending their reach with a diversity of streaming connectors and SQL data sources. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Bahir was founded 2016-05-18 (7 years ago) There are currently 40 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was João Boto on 2020-07-10. - No new committers. Last addition was Łukasz Antoniak on 2019-01-21. ## Project Activity: Apache Bahir community continues to see a steady medium flow of contributions enhancing the existing extensions. ### Spark extensions: The community is less active than usual in this extensions. ### Flink extensions: The community is more involved in this extensions: - Lasts verifications on adaptation to Flink 1.16.1 - Start adaptations of extensions to new formats ### Releases Apache Bahir for Apache Spark 2.4.0 released on 2019-09-23 Apache Bahir for Apache Spark 2.3.4 released on 2019-09-23 Apache Bahir for Apache Flink 1.14.5 released on 2022-08-05 ## Community Health: This quarter the community has been a less active. We need to find some active committers for Spark connectors as its not very active. ----------------------------------------- Attachment I: Report from the Apache Beam Project [Kenneth Knowles] ## Description: The mission of Apache Beam is the creation and maintenance of software related to a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Beam was founded 2016-12-20 (6 years ago) There are currently 90 committers and 24 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. Community changes, past quarter: - Jan Lukavský was added to the PMC on 2023-02-14 - No new committers. Last addition was Yi Hu on 2022-11-05. ## Project Activity: - Google Summer of Code processes are kicked off, and there are a few project proposals. - Beam Summit 2023 will be held in New York, and the CFP recently closed. Recent releases: - 2.46.0 was released on 2023-03-10 - 2.45.0 was released on 2023-02-15 ## Community Health: There is an across the board 20-30% reduction in many measures of community health traffic. This is not a cause for concern (yet). One could speculate about how global events and major disruptions in big tech could influence activity over this period. ----------------------------------------- Attachment J: Report from the Apache Bigtop Project [Yuqi Gu] ## Description: Bigtop is a project for the development of packaging and tests of the Apache Hadoop ecosystem. The primary goal of Bigtop is to build a community around the packaging and interoperability testing of Hadoop-related projects. This includes testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. In short we strive to be for Hadoop what Debian is to Linux. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Bigtop was founded 2012-09-19 (10 years ago) There are currently 41 committers and 29 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 Masatake Iwasaki on 2021-03-11. - Yoda Leona was added as committer on 2023-02-07 ## Project Activity: - 3.2.0 was released on 2023-01-17. In this release a number of core services were added into Bigtop Mpack Framework including Hive, Hbase, Solr, Ambari metrics,etc. And we also implemented Bigtop-stack-provisioner: One-Click deploying and testing Bigtop stack by Ambari with a simple script. Some new distros were also newly supported and many other components were upgraded for compatibility. - Definition of 3.3 BOM is in discussion on BIGTOP-3909. We are discussing about OpenEuler support, components upgrading and reducing the release burden (only support the latest LTS). ## Community Health: - The relative decrease was caused by moving Mpack development to resurrect Ambari project and PRs/Jiras silence (only accept blocker or critical bug fixes into the branch) when preparing for Bigtop 3.2.0 release. - dev@bigtop.apache.org had a 100% increase in traffic in the past quarter (380 emails compared to 190). - issues@bigtop.apache.org had a 78% increase in traffic in the past quarter (212 emails compared to 119). - 7 code contributors in the past quarter (-41% change) - 14 PRs opened on GitHub, past quarter (-77% change) - 8 PRs closed on GitHub, past quarter (-85% change) - 28 commits in the past quarter (-50% decrease) ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== There are no issues to raise to the Board at this time. Releases ======== There have been no releases since the last report. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Community & Development ======================= Development progress over the last three months remains slow. More Hackdays for March and April have recently been announced to try to move things along. ----------------------------------------- Attachment L: Report from the Apache bRPC Project [James Ge] ## Description - bRPC is an industrial-grade RPC framework for building reliable and high-performance services. - bRPC was graduated as Top Level Project in December 2022. ## Issues There are no Board-level issues at this time. ## Membership Data - PMC Members: 13 - Committers: 17 - Contributors: 129 - Date of newest committer: Feb. 13th, 2023 - Date of newest PMC Member: Jun. 22th, 2022 - Diversity: 129 contributors are from 20 more unique organizations, and 16 committers are from 9 unique organizations including Baidu, ByteDance, Google, 4Paradigm, Momemta. AI, Shopee, Tecent, JOYY. ## Project Activity - On Feb. 7th, 2023, we released bRPC v1.4.0 with new features such as the RDMA support and bazel third_party support, along with several bug fixes. ## Community Health - On Feb. 13th,Zhaogeng Li who has contributed the RDMA patch to bRPC became the new committer. - Committers take turns responding user emails and issues on a weekly basis. During the past quarter, about 100 new emails were received and answered weekly. ----------------------------------------- Attachment M: Report from the Apache BVal Project [Matthew Jason Benson] ## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention. ## Membership Data: Apache BVal was founded 2012-02-14 (11 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: We have seen a modest increase in activity, primarily arising from migration of API concerns from the Java to Jakarta namespace, this quarter. ## Community Health: Our normal mode continues to be that of maintenance and performing what tasks *need* to be done. As well, the metrics are perhaps artificially inflated due to the "participation" of dependabot which has generated several pull requests on the project. ----------------------------------------- Attachment N: Report from the Apache Camel Project [Andrea Cosentino] ## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (14 years ago) There are currently 85 committers and 43 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Pasquale Congiusti was added to the PMC on 2023-01-19 - Federico Mariani was added as committer on 2023-01-24 ## Project Activity: - We released Camel 3.18.5 - We released Camel 3.20.0 - We released Camel 3.20.1 - We released Camel 3.20.2 - We released Camel 4.0.0-M1 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - We started the work through Camel 4, we are already releasing some milestones and we are in good shape. - We are continuing release 3.18.x LTS release train. This will be around for a while. - We started the release train for 3.20.x LTS, and we are already at the second patch release. - We released Camel K 1.10.4, 1.11.0, 1.11.1 and 1.12.0, the first release based on Camel 3.20.x LTS Releases from main Camel project. - We released also Camel K 1.11.0 based on Camel 3.19.0 release (non LTS) - Related to Camel K we have also Camel K Runtime and Camel-Kamelets releases - We released Camel K Runtime 1.15.3 - We released Camel K Runtime 1.15.4 - We released Camel K Runtime 1.17.0 - We released Camel Kameletes 0.9.4 - We released Camel Kameletes 3.20.0 - We released Camel Kameletes 3.20.1 - We released Camel Kamelets 3.20.1.1 - We released Camel Kamelets 3.20.2 - We released Camel Kamelets 4.0.0-M1 - We are improving the Camel-K experience and Camel Kamelets is already looking at Camel 4 - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.13.2 - We released Camel-quarkus 2.16.0 - Camel-Kameleon and Camel-Karavan are improving and more and more contributors are starting to help. We are improving the projects by supporting new features and aligning with LTS releases 3.20.x - Camel Kafka Connector release based on Camel 3.20.1 has been released. - We are supporting Camel Kafka Connector aligning it to the Camel Core LTS Releases 3.20.x ## Community Health: - 310 issues opened in JIRA, past quarter (6% decrease) and 249 issues closed in JIRA, past quarter (11% decrease): We are in a stabilization phase for Camel 3.x and the LTS are more or less stable. Also with the new 3.20.x release train for LTS, we are going to improve the stability. Mostly new issues are about Camel 4.x - 213 issues opened on GitHub, past quarter (2% increase) and 194 issues closed on GitHub, past quarter (20% increase): We are adding new issues for aligning to Camel 4.x Camel/Camel-Karaf/Camel-Spring-Boot. There are some more issues opened on the Camel K subprojects, since the contributors and users are increasing. - 3919 commits in the past quarter (8% increase) and 120 code contributors in the past quarter (4% decrease): More or less we are stable. We have some new contributors coming from different subprojects and related to some documentation activities and bug fixes. Camel 4.x is mostly a work done by the Camel core team. - 1113 PRs opened on GitHub, past quarter (5% decrease) and 1113 PRs closed on GitHub, past quarter (5% decrease): on some of the subprojects the activity is slowing down for stabilization reasons, on some other like Camel K and Camel Quarkus there is so much activity for aligning to new Camel Releases for Camel 4.x - From this report the dev, users and issues mailing lists have been omitted because the ASF project statistics page for Apache Camel is not up-to-date ----------------------------------------- Attachment O: Report from the Apache Cayenne Project [Michael Ray Gentry] # Apache Cayenne Board Report, March 2023 ## Description Apache Cayenne is a Java database persistence framework. It takes a distinct approach to object graph persistence and provides an ORM runtime, remote persistence services, and a cross-platform GUI database mapping/modeling/development tool. ## Issues On the December Board Report, Rich Bowen commented: > 4 years since adding a committer, and 5 since adding a PMC > member, is concerning for the long-term sustainability of > the project. Have you recently had a hard look to see what > new contributors might be invited to join the project > community? Cayenne's core committers and PMC are rather stable. That said, there is an individual who has submitted several PRs and bug reports for rather non-trivial issues and we are planning to invite him to become a committer soon. Hopefully he will accept a role in the project. ## Membership Data Apache Cayenne was founded 2006-12-19 (16 years ago). There are currently 23 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Nikita Timofeev on 2017-06-25. - No new committers. Last addition was Arseni Bulatski on 2018-12-10. ## Project Activity Development is focused on Cayenne 4.2, but shifting to 5.0 (unreleased). Prior versions are maintenance-only. 4.2.RC2 was released released last quarter and had one serious regression issue which has been resolved. We expect to have an RC3 soon followed by a GA release. NOTE: We also did a legacy release last week of 4.0.3 (first in about 4 years for 4.0.x) to fix a compatibility issue with Cayenne Modeler running under Java 17. - Cayenne 4.0.x (stable) - Maintenance only. - Cayenne 4.1.x (stable) - Maintenance only. - Cayenne 4.2.x (release candidate) - Pre-release development work mainly. ### Releases - Cayenne 4.0.3 on 2023-03-02. - Cayenne 4.1.1 on 2021-12-24. - Cayenne 4.2.RC2 on 2022-12-06. ## Community Health Cayenne is healthy. JIRA, Git, and mailing list activity were slightly elevated over the last quarter due to bug fixes and releases for 4.2.x and 4.0.x. Questions on the user mailing list are actively addressed. ----------------------------------------- Attachment P: Report from the Apache Celix Project [Pepijn Noltes] ## Description: The mission of Celix is the creation and maintenance of software related to Implementation of the OSGi specification adapted to C ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Celix was founded 2014-07-16 (9 years ago) There are currently 17 committers and 10 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 Peng Zheng on 2022-10-16. - No new committers. Last addition was Zhenbao on 2022-10-19. ## Project Activity: The last release was 2.3.0 in 2022-07-14 There are several activity (PRs) for stability. This includes several memory leak fixes, a new error injection library to be able to check for NULL returns and a refactor of of the bundle/module part of the framework. Another activity is the preparation for a 3.0.0 release, where a large part of the public deprecated headers will become private headers. And there is activity for remote service invocation and discovery using shared memory an zeroconf (mdns). ## Community Health: Overall community health is good. We are seeing an significant increase in commits (180%) and this is due to 2 latest added committers. Note that most of the communicatie is done through pull requests, this includes some technical discussion. ----------------------------------------- Attachment Q: Report from the Apache CloudStack Project [Simon Weller] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage, and networking devices. ## Issues: No issues to report. ## Membership Data: Apache CloudStack was founded 2013-03-19 (10 years ago) There are currently 129 committers and 52 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. PMC changes: - Most recently added PMC member: Ivet Petrova was added to the PMC on 2023-02-10. Committer base changes: - There are no new committers since the last report. - Most recently added committers: Ivet Petrova and Slavka Peleva, both added as committers on 18 December 2021. ## Project Activity: - The Apache CloudStack project released the current LTS version 4.17.2.0 on the 16th of December 2022. - The previous LTS version received an updated release to 4.16.1.1 on July 18th, 2022. - Apache Cloudstack 4.18.0 is in Release Candidate (RC) status with numerous new features being tested by the community. - The PMC is actively discussing new PMC Candidates and new Committers. Thus far, 1 new PMC member has been added since the discussions commenced. We expect additional vote threads to be started in the coming days. - The PMC is currently discussing the possibility of moving to external hosting for the website and blog, with the ASF decommissioning the current Roller blog system. - The CloudStack PMC Chair rotation was voted on in early March. A resolution to the Apache Board was submitted to confirm Rohit Yadav to the role. ## Community Health: Apropos of the Project Activity report; the project is considered healthy. - According to the apache statistics, the project achieved the Community Health Score (Chi): 7.15 (Healthy) ## Releases: Latest: - 4.17.2.0 was released on 16th December 2022 -- EOL 1st Jan 2024. - 4.17.1.0 was released on 26th September 2022 -- EOL 1st Jan 2024. - 4.17.0.1 was released on 18th July 2022 -- EOL 1st Jan 2024. - 4.17.0.0 was released on 7th June 2022 -- EOL 1st Jan 2024. Reaching EOL: - 4.16.1.1 was released on 18th July 2022 -- EOL 1st June 2023. - 4.16.1.0 was released on 7th March 2022 -- EOL 1st June 2023. - 4.16.0.0 was released on 15th November 2021 -- EOL 1st June 2023. ----------------------------------------- Attachment R: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The mission of Apache Commons is the creation and maintenance of Java focused reusable libraries and components ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Commons was founded 2007-06-19 (16 years ago) There are currently 149 committers and 42 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Matt Juntunen on 2021-06-25. - No new committers. Last addition was Claude Warren on 2022-02-01. ## Project Activity: The Commons project is alive and well, we've released the following in this reporting period: - FILEUPLOAD-1.5 was released on 2023-02-13. - CSV-1.10.0 was released on 2023-02-02. - CRYPTO-1.2.0 was released on 2023-01-22. - PARENT-56 was released on 2023-01-02. ## Community Health: While the mailing list activity is down, we still get PRs on GitHub, and requests to release new versions. ----------------------------------------- Attachment S: Report from the Apache Cordova Project [Jesse MacFadyen] ## Status report for the Apache Cordova project - March 2023 ## Description: - A platform for building native mobile applications using HTML, CSS and JavaScript. ## Activity Current work continues to be keeping up with changes to iOS and Android, our most used platforms, and updating plugins. Github discussions has become how our community supports each other. There was a question last report about whether it made sense to send our slack digest to our dev list. We are hoping that github discussions takes the place of slack entirely, which has already started to happen. Github discussion also carry a lot more context, as they are close to the code, can easily link to code, pull requests and issues. ## Issues: - There are no issues requiring board attention at this time. ## Health report: Our status dashboard at http://status.cordova.io remain mostly all green - failures are usually due to external service issues that do device testing. Our nightly builds are still extremely stable. ASF Project Statistics gives the project a Community Health Score (Chi): 4.7 Healthy We continue to see contributions from a small group of dedicated individuals. Things remain stable and the project continues to see good traffic. Our discussion area is live at https://github.com/apache/cordova/discussions and activity has been shifting there and away from our #slack community. ## Membership Data: - There are currently 99 committers and 96 PMC members in this project. - The Committer-to-PMC ratio is roughly 1:1. ### Community changes, past quarter: - No new PMC members. Last addition was Pieter Van Poyer on 2021-04-05 - No new committers. Last addition was Pieter Van Poyer on 2021-04-05 ## Releases: - cordova-common@5.0.0 was released on 2023-03-09. - cordova-plugin-screen-orientation@3.0.3 was released on 2023-02-24. - cordova-serve@4.0.1 was released on 2023-02-01. - cordova-eslint@5.0.0 was released on 2023-01-18. - cordova-cli@11.1.0 was released on 2023-01-16. - cordova-create@4.1.0 was released on 2023-01-10. - cordova-lib@11.1.0 was released on 2023-01-10. ## Dev mailing list: - _mailing list stats seem to be inaccurate, but traffic was still low this quarter_ ## Github activity: Issue close rate of 245% - 96 issues opened on GitHub, past quarter (-10% change) - 235 issues closed on GitHub, past quarter (137% increase) PR close rate of 108% - 125 PRs opened on GitHub, past quarter (1% increase) - 135 PRs closed on GitHub, past quarter (33% increase) Commits - 141 commits in the past quarter (17% increase) - 15 code contributors in the past quarter (-11% change) ----------------------------------------- Attachment T: Report from the Apache cTAKES Project [Pei Chen] ## Description: The mission of cTAKES is the creation and maintenance of software related to Natural language processing (NLP) tool for information extraction from electronic medical record clinical free-text ## Issues: There are no issues requiring board attention at this time. Regarding last quarter's report on @dev vs @private mailing lists, a friendly reminder was sent to @private: https://lists.apache.org/thread/ot39xwkfwk6175dnztbhtc3vskb28zs0 ## Membership Data: Apache cTAKES was founded 2013-03-19 (10 years ago) There are currently 40 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. New committer (Dennis) was added as a committer this quarter. Community changes, past quarter: - No new PMC members. Last addition was Gandhi Rajan on 2018-07-12. - Dennis Johns was added as committer on 2023-01-06 ## Project Activity: - Committee continues to work on the future release (5.x.x) - Committee migrated the code repo to git - Last release was 4.0.0.1 patch on Jan 20 2021 - 4.0.0 was released on Apr 27 2017 - 3.2.2 was released on May 30 2015 ## Community Health: There has been an increase in the dev and user email traffic this quarter mainly regarding the next 5.x.x release. ----------------------------------------- Attachment U: Report from the Apache Curator Project [Enrico Olivelli] ## Description: The mission of Curator is the creation and maintenance of software related to Java libraries that make using Apache ZooKeeper easier ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Curator was founded 2013-09-18 (9 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Zili Chen on 2020-08-06. - No new committers. Last addition was Zili Chen on 2020-08-06. ## Project Activity: Recent releases: 5.4.0 was released on 2022-10-28. 5.3.0 was released on 2022-07-04. 5.2.1 was released on 2022-03-17. ## Community Health: The community is small but active. We recently received a few contributions and we started a discussion about inviting a new committer. He will be invited soon. ----------------------------------------- Attachment V: Report from the Apache Daffodil Project [Mike Beckerle] ## Description: The mission of Apache Daffodil is the creation and maintenance of an implementation (and related software) of the Data Format Description Language (DFDL) to convert between fixed format data and more readily processed forms such as XML/JSON text or EXI binary. ## Issues: There are no issues that require board attention. ## Membership Data: Apache Daffodil was founded 2021-02-16 (2 years ago) There are currently 17 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - Mike McGann was added to the PMC on 2023-02-27 - Mike McGann was added as committer on 2023-02-28 ## Project Activity: No new releases this past quarter. Contributors are fixing bugs in the daffodil library for a primarily bug-fix release (3.5.0) in April or May. Contributors are continuing to add new functionality to the daffodil-vscode extension for the next release (1.3.0) in April or May. ## Community Health: Our stats look good. We have 188 PRs closed on GitHub over the past quarter. This is a 66% increase. ----------------------------------------- Attachment W: Report from the Apache ECharts Project [Wenli Zhang] ## Description: The mission of Apache ECharts is the creation and maintenance of software related to a charting and data visualization library written in JavaScript ## Issues: NA ## Membership Data: Apache ECharts was founded 2020-12-16 (2 years ago) There are currently 28 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was He Hao on 2022-07-06. - No new committers. Last addition was He Hao on 2022-07-06. A new committer is under discussion. ## Project Activity: We are testing the next version 5.4.2 and is expected to release in two weeks. ## Community Health: There has been an increase in communication and engagement within the community. The mailing list experienced a significant increase in traffic, indicating that members are more actively participating in discussions and exchanging information. Overall, the community's health appears to be stable, with an increase in communication but a decrease in code contributions. It is crucial for us to continue monitoring and evaluating these metrics to ensure the community's continued growth and health. ----------------------------------------- Attachment X: Report from the Apache Felix Project [Karl Pauls] ## Description: Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Felix was founded 2007-03-28 (16 years ago) There are currently 68 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Georg Henzler on 2019-06-10. - No new committers. Last addition was Robert Munteanu on 2020-07-20. ## Project Activity: - Existing implementations have been improved/enhanced based on community feedback. - The http subproject is moving to the Jakarta API (away from javax.*). - Released 16 components (mostly bug fixes/minor improvements and RCs for the move away from Jakarta). ### Releases - org.apache.felix.http.jetty-4.2.8 was released on 2023-03-04. - org.apache.felix.http.base-4.2.4 was released on 2023-02-24. - org.apache.felix.http.base-5.0.2 was released on 2023-02-24. - org.apache.felix.http.bridge-4.2.6 was released on 2023-02-24. - org.apache.felix.http.bridge-5.0.4 was released on 2023-02-24. - org.apache.felix.http.jetty-4.2.6 was released on 2023-02-24. - org.apache.felix.http.jetty-5.0.4 was released on 2023-02-24. - org.apache.felix.webconsole-4.8.8 was released on 2023-02-24. - org.apache.felix.scr-2.2.6 was released on 2023-01-23. - org.apache.felix.http.base-5.0.0 was released on 2022-12-27. - org.apache.felix.http.bridge-5.0.0 was released on 2022-12-27. - org.apache.felix.http.inventoryprinter-1.0.0 was released on 2022-12-27. - org.apache.felix.http.jetty-5.0.0 was released on 2022-12-27. - org.apache.felix.http.proxy-4.0.0 was released on 2022-12-27. - org.apache.felix.http.sslfilter-2.0.0 was released on 2022-12-27. - org.apache.felix.http.webconsoleplugin-1.0.0 was released on 2022-12-27. ## Community Health: - Overall the project is in ok health. - There is a decline in community activity, fewer activity can be seen in issue trackers, emails and GitHub. In general, we don't see a lot of new development right now. We are at the lookout for new topics and contributors. - Questions on the user list are answered, development concerns are either discussed on the mailing list or directly in the JIRA issues. - We had no issues voting on releases and JIRA issues are generally addressed. ----------------------------------------- Attachment Y: Report from the Apache Flex Project [Olaf Krüger] ## Description: The mission of the Apache Flex project is to create and maintain software related to the development of expressive web applications that deploy to all major browsers, desktops and devices (including smartphones, tablets and tv) ## Issues: No issues at this time. ## Membership Data: Apache Flex was founded 2012-12-19 There are currently 68 committers and 46 PMC members in this project. Of those PMC members an estimated 5 or 6 are active. Community changes, past quarter: - Greg Dove was added as a PMC member. - No new committers. Last addition was Greg Dove on 2016-09-07. ## Project Activity: The project is stable. There is a need to update BlazeDS for security updates and support more modern dependencies. One necessary dependency was released on February 21. There is currently an ongoing vote to release a new version of BlazeDS. Harbs was voted and requested to become the new chair pending the upcoming board meeting. ## Community Health: The project is stable and there's little activity. There is little discussion. It took longer than desired to fix the BlazeDS issue. That's mostly because very few PMC members have experience with that piece of code. Most of the recent discussion was involving BlazeDS and switching the chair. ----------------------------------------- Attachment Z: Report from the Apache Flink Project [Robert Metzger] ## Description: The mission of Flink is the creation and maintenance of software related to platform for scalable batch and stream data processing ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Flink was founded 2014-12-17 (8 years ago) There are currently 100 committers and 46 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - Dong Lin was added to the PMC on 2023-02-16 - Anton Kalashnikov was added as committer on 2023-02-14 - Rui Fan was added as committer on 2023-02-14 - Weijie Guo was added as committer on 2023-02-11 - Jing Ge was added as committer on 2023-02-14 - Lincoln Lee was added as committer on 2023-01-07 - Sergey Nuyanzin was added as committer on 2023-02-16 - Yuxia Luo was added as committer on 2023-03-10 ## Project Activity: Releases: - kubernetes-operator-1.4.0 was released on 2023-02-22 (this is a major milestone, adding support for autoscaling) - Flink 1.16.1 was released on 2023-01-30. - flink-table-store 0.3.0 was released on 2023-01-13 - kubernetes-operator-1.3.1 was released on 2023-01-10. - connector-opensearch-1.0.0 was released on 2022-12-22. - connector-jdbc-3.0.0 was released on 2022-12-21. - connector-pulsar-3.0.0 was released on 2022-12-21. - connector-rabbitmq-3.0.0 was released on 2022-12-21. Upcoming releases: The community is close to finalizing the upcoming Flink 1.17.0 release with substantial batch and stream processing improvements. Other activity: - Part of the community decided to bring the flink-table-store project to the ASF incubator to establish this as a new project called Paimon. - There are discussions about improving the project website, initially from a design / UX perspective. The build system of the website has recently been upgraded to Hugo. - The PMC continues to handle security-related requests. - Our effort to externalize connectors from the main repo to separate ones has continued and almost all connectors are now separated. ## Community Health: The Flink community enjoys a community health score of 10 (super healthy). The project has just reached the milestone of 100 committers. As you can see from the membership data above, we've added quite a few committers and a new PMC member to the project in the last quarter, and the PMC continues to monitor and mentor promising contributors. After slight decreases in mailing list activity reported in the last quarter, we now this being stopped, with the number being steady (2% increase in dev@). Jira and GitHub activity is also good. ----------------------------------------- Attachment AA: Report from the Apache Gobblin Project [Abhishek Tiwari] ## Description: The mission of Apache Gobblin is the creation and maintenance of software related to a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems ## Issues: No issues to report. ## Membership Data: Apache Gobblin was founded 2021-01-19 (2 years ago) There are currently 19 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19. - No new committers. Last addition was William Lo on 2022-08-31. ## Project Activity: - Enhanced logging to help with debugging multi-hop flows creation, progression, and cleanup - Support added for xz-compressed Avro files - Observability related events added for GaaS - Fix for race-conditions in FS Template catalog - Improved error reporting for flow config resolution - Fix for state store change monitors - Support for extended ACLs and sticky bit in File based DistCP - Fix for Multi-hop jobs skipping flows intermitently - Improved and refactored manifest, reader, writer, and iterator for efficient reading - Support for Hadoop v2.10.0 added - Support for syncing directory metadata in manifest based data copy - Metrics added for measuring lag between producer and consumers - Fix constructor for KafkaJobStatusMonitor to make it injectable - Improve noisy logging about queue capacity to make it more consumable - Null value support for fields in GaaSObservabilityEvents - Support to help GMIP Hive metadata writer to fail gracefully and avoid aborts - Support to register guage metrics for change monitors - Added house-keeping support in DAG Manager to periodically sync in-memory state with database - Improved Helix offline instance purger to be thread safe - Improved state merging process for Flows pending resume - Support for multiple catalog types in Icerberg based DistCP - Improved logging in State Store to catch any possible memory leaks - GobblinMCEWriter was made public to build specialized Writers - Addition of capability to filter databases by union data types - Support for FACL in Manifest based data copy - Added optimization for not scheduling flows far into future ## Community Health: - There have been 52 commits since 1st December 2022. - 33 commits have been from non-committers. - William Lo was voted in Aug, 2022 as a committer. We constantly look for consistent contributors to vote them in as Committers. ----------------------------------------- Attachment AB: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: - The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key-value stores, document stores, distributed in-memory key-value stores, in-memory data grids, in-memory caches, distributed multi-model stores and hybrid in-memory architectures. Gora also enables analysis of data with extensive Apache Hadoop MapReduce, Apache Spark, Apache Flink, and Apache Pig support. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Gora was founded 2012-01-24 (11 years ago) There are currently 31 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Lahiru Jayasekara on 2020-04-30. - No new committers. Last addition was Lahiru Jayasekara on 2020-04-27. ## Project Activity: - Considerable work progress made on development for next release work, number of pull requests in backlog were reviewed and merged to main branch. - Received several contributions from external people. - Proposed one candidate for committership/PMC. ## Community Health: - We observed increased level of activity on mailing list and Github. This was mainly due to the work carried on remaining PR backlog merging process. Even though some remaining work is still left in PR backlog, we were able to make some progress compared to last quarterly report. We are planing to make our release next once critical tickets are addressed and resolved from PR backlog. ----------------------------------------- Attachment AC: Report from the Apache Guacamole Project [Mike Jumper] ## Description: The mission of Apache Guacamole is the creation and maintenance of software related to providing performant, browser-based remote access ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Guacamole was founded 2017-11-14 (5 years ago) There are currently 14 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 7:5. Community changes, past quarter: - Luke was added to the PMC on 2023-02-22 - No new committers. Last addition was Luke on 2020-02-07. ## Project Activity: The project produced its latest release last month (1.5.0), the culmination of roughly a year of effort, and discussion for scoping of next release is now underway. The project is also happy to welcome Luke to the PMC. Luke's consistent activity within the community resulted in his becoming a committer, and now our first new PMC member since the project began. Recent releases: - 1.5.0 was released on 2023-02-18. - 1.4.0 was released on 2022-01-01. - 1.3.0 was released on 2021-01-01. ## Community Health: The community continues to be active and healthy. The recent release of 1.5.0 has resulted in an increase in mailing list activity, as well as a modest increase in contributions. ----------------------------------------- Attachment AD: Report from the Apache Gump Project [Stefan Bodewig] ## Description Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and OpenSSL. ## Issues There are no issues requiring board attention. ## Membership Data Apache Gump was founded 2004-02-18 (17 years ago) There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: No new PMC members. Last addition was Mark Thomas on 2014-12-03. No new committers. Last addition was Konstantin Kolinko on 2015-02-11. ## Project Activity Triggered by the board feedback to the last report we've started a discussion on the future direction of Gump - see https://lists.apache.org/thread/sfxpor1svn96vpw128os0crnhoyr3z57 . The Tomcat community is the only one still using Gump actively and the only activity in Gump is around keeping the infrastructure alive and tweaking things for the benefit of Tomcat builds. We will certainly support any other project that wants to get the benefit of the early warning system for backwards incompatible changes Gump provides, but we are not actively recruiting projects. ## Releases Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. ## Community Health There isn't much happening but help is there when anybody needs it. Apart from foundation wide announcements or infrastructure team messages nobody has posted any message to the Gump mailing list or asked for a change who is not a member of the Gump PMC already for the last almost five years. ----------------------------------------- Attachment AE: Report from the Apache Helix Project [Junkai Xue] ----------------------------------------- Attachment AF: Report from the Apache Hive Project [Naveen Gangam] ## Description: The mission of Hive is the creation and maintenance of software related to Data warehouse infrastructure using the Apache Hadoop Database ## Issues: No issues requiring board attention this time. ## Membership Data: Apache Hive was founded 2010-09-21 (~12 years ago) There are currently 106 committers and 56 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: László Bodor was added to the PMC on 2023-01-26 Ayush Saxena was added to the PMC on 2022-12-19 Krisztian Kasa was added to the PMC on 2023-01-29 Stamatis Zampetakis was added to the PMC on 2023-01-12 Alessandro Solimando was added as committer on 2023-02-08 László Végh was added as committer on 2023-02-06 ## Project Activity: 4.0 alpha2 has been released in November 2022. Apache Hive 3.1.3 has been released in Feb 2022. Still working towards the 4.0GA release. Apache Hive 3.2 release with fixes for CVEs is also in planning. Jira activity: In the trailing 31 days, 67 jiras have been opened, 20 of which have been FIXED. A total of 58 jiras have been closed/resolved and a total of 48 have been FIXED. ## Community Health: Community Health Score (Chi): 10.0 (Super Healthy) Community activity is relatively healthy based on engagement. But compared to last quarter, overall activity (jira/github/dev lists) is slightly down this quarter. ----------------------------------------- Attachment AG: Report from the Apache Hudi Project [Vinoth Chandar] ## Description: The mission of Apache Hudi is the creation and maintenance of software related to providing atomic upserts and incremental data streams on Big Data ## Issues: [There are no issues requiring board attention. ## Membership Data: Apache Hudi was founded 2020-05-19 (3 years ago) There are currently 33 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - Y Ethan Guo was added to the PMC on 2023-03-13 - Yue Zhang was added as committer on 2022-12-31 ## Project Activity: Since the last report we put out two Hudi releases. 0.12.2 is a minor release on the 0.12.x release line, where the community is currently getting LTS to migrate from much older releases. In addition, we released a new major release 0.13.0 which brings significant improvements (new record merger APIs, new CLI bundle, Flink 1.16 support) as well brand new innovations like (new CDC format, consistent hashing index, eager conflict detection and much more). We put together a Hudi in 2022 blog, https://hudi.apache.org/blog/2022/12/29/Apache-Hudi-2022-A-Year-In-Review that showcases the various community events, and collaboration through 2022. Other similar blogs are featured at https://hudi.apache.org/blog Going forward, we are gearing up for our 1.0 release plans, which will be a major revamp of our underlying storage format, based on our learnings in the community and industry for the past 3+ years. ## Community Health: We continue to see very healthy engagement from the community. The code commits slow down is from the 0.13 release hogging up a lot of the committer cycles to review/land code. ----------------------------------------- Attachment AH: Report from the Apache Iceberg Project [Ryan Blue] ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for March 2023 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 31 podlings incubating. Podlings made 5 distinct releases. This month we were missing reports from Nemo, PageSpeed, Spot and Training. There are votes underway to retire PageSpeed and Spot and Marvin-AI has retired. Nemo and Training projects will be asked to report next month. The Training project is discussing how to move forward. Flagon and EventMesh have proposals to the board for graduation. Two new podlings Palimon and OpenDAL have joined the Incubator. There is ongoing discussion around a few new projects and the graduation of DataLab. ## Community ### New IPMC members: - Becket Qin - Yu Xiao ### People who left the IPMC: - Jim Jagielski ## New Podlings - OpenDAL - Paimon ## Podlings that failed to report, expected next month - Nemo - PageSpeed - Spot - Training ## Graduations - None The board has motions for the following: - EventMesh - Flagon ## Releases The following releases entered distribution during the month of March: - HugeGraph 1.0.0 - Kvrocks 2.3.0 - StreamPark 2.0.0 - DevLake 0.15.0 - NLPCraft 1.0.0 ## IP Clearance - [Kylin]Accept donation of Kylin new Modeling System ## Legal / Trademarks N/A ## Infrastructure N/A ## Miscellaneous N/A ## Table of Contents [Baremaps](#baremaps) [KIE](#kie) [NLPCraft](#nlpcraft) [OpenDAL](#opendal) [Uniffle](#uniffle) [Wayang](#wayang) -------------------- ## Baremaps Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps. Baremaps has been incubating since 2022-10-10. ### Three most important unfinished issues to address before graduating: 1. Getting the code in compliance with Apache standards 2. Making releases 3. Growing the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? The activity has been low in December and January, but the community has stayed steady. ### How has the project developed since the last report? - We addressed most of the critical licensing issues and identified minor issues with license of the data used in the tests - We improved the layout and the content of the web site - We launched a vote for a first release candidate with a DISCLAIMER-WIP file - Some of us will attend the OGC/OSGeo/ASF code sprint with the intent to work on Baremaps ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? When the project entered incubation. ### Have your mentors been helpful and responsive? Yes, the mentors have been very helpful on several topics (community building, licensing, etc.) ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [X] (baremaps) Julian Hyde Comments: Reviewing the first release candidate now, and quality looks good for a podling's first RC. Development has been rather narrow (in a few individuals), so I'm hoping to see broadening of community participation around the first release. - [X] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: -------------------- ## KIE KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows. KIE has been incubating since 2023-01-13. ### Three most important unfinished issues to address before graduating: 1. Software Grant completion, currently waiting on legal. 2. IP clearance. Question: Can this start before the grant has been finalized? 3. Create a release :) ### Are there any issues that the IPMC or ASF Board need to be aware of? Currently no. ### How has the community developed since the last report? This is our first report. We have a number of people signed up for the PPMC, but seeing as we don't have the code moved over yet, there isn't much else to be done at the moment. ### How has the project developed since the last report? We're working through legal both at IBM and Red Hat. This wasn't as quick as any of us had hoped it would be. ### How would you assess the podling's maturity? - [ ] Initial setup Mailing lists created Initial committers have signed the ICLA - [ ] Working towards first release We'll get there, need the software grant first - [ ] Community building Not much we can do on this front until the code has moved over - [ ] Nearing graduation N/A - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? Back in January when we were accepted into the Incubator ### Have your mentors been helpful and responsive? Brian has been very helpful in getting things started, no concerns about any of the mentors. ### Is the PPMC managing the podling's brand / trademarks? Still working on grants ### Signed-off-by: - [X] (kie) Brian Proffitt Comments: - [X] (kie) Claus Ibsen Comments: - [X] (kie) Andrea Cosentino Comments: Looks good. ### IPMC/Shepherd notes: -------------------- ## NLPCraft A Scala library for NLU applications NLPCraft has been incubating since 2020-02-13. ### Three most important unfinished issues to address before graduating: 1. Community growth. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? Community development wasn't grown last months. The main reason is probably due to core committers were engaged in a 1.0 release tests,documentatation and website update. But there were some initial developers requests to join and contribute during last months. ### How has the project developed since the last report? The project tests were extended, examples added, documentation and website updated, release 1.0.0. prepared. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2023-02-30 ### When were the last committers or PPMC members elected? August of 2021. ### Have your mentors been helpful and responsive? No issues with mentors to report. ### Is the PPMC managing the podling's brand / trademarks? No issues to report. ### Signed-off-by: - [ ] (nlpcraft) Roman Shaposhnik Comments: - [ ] (nlpcraft) Furkan Kamaci Comments: - [ ] (nlpcraft) Evans Ye Comments: - [ ] (nlpcraft) Paul King Comments: - [ ] (nlpcraft) Konstantin I Boudnik Comments: - [X] (nlpcraft) Dave Fisher Comments: ### IPMC/Shepherd notes: -------------------- ## OpenDAL Open Data Access Layer: Access data freely, painlessly, and efficiently. OpenDAL has been incubating since 2023-02-27. ### Three most important unfinished issues to address before graduating: 1. The majority of contributions to the OpenDAL project were made by only four committers, with Xuanwo being the most prolific contributor. 2. The adoption rate of OpenDAL has been relatively low, with only a few projects currently using it. ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? This is the first report of OpenDAL. Over the past two weeks, the project has successfully attracted four new contributors, one of whom has shown great promise and potential to be considered for committer status in the future. ### How has the project developed since the last report? This is the first report of OpenDAL. During the past two weeks, OpenDAL has added support for the append function and is currently working on developing Python and Node.js bindings. These updates are expected to be included in the upcoming Apache release. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: NOTE: it's not an Apache release, because our repo trasnfer is not DONE yet. 2023-03-02 ### When were the last committers or PPMC members elected? OpenDAL has been in incubation since February 27th, 2023. As of yet, no committers have been elected for the project. ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? N/A ### Signed-off-by: - [X] (opendal) tison Comments: - [X] (opendal) Willem Ning Jiang Comments: Just finished the project setup work - [ ] (opendal) Sheng Wu Comments: - [ ] (opendal) Ted Liu Comments: - [X] (opendal) Xiaoqiao He Comments: ### IPMC/Shepherd notes: -------------------- ## Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. Toree has been incubating since 2015-12-02. ### Three most important unfinished issues to address before graduating: 1.Increase active contributors ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? We still see much of the users asking questions in the gitter channel rather than using the mailing lists. ### How has the project developed since the last report? The community has received a contribution adding support for Scala 2.13 and Apache Spark 3.3 and are discussing how to better handle the support for both versions versus one. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2022-04-11 ### When were the last committers or PPMC members elected? Kevin Bates was added to the PPMC on 2019-08-14 ### Have your mentors been helpful and responsive? None ### Is the PPMC managing the podling's brand / trademarks? No Trademark issues ### Signed-off-by: - [X] (toree) Luciano Resende Comments: With my contributor hat, I am planning to try to move Toree trough graduation on the next couple months - [ ] (toree) Julien Le Dem Comments: - [ ] (toree) Ryan Blue Comments: - [ ] (toree) Weiwei Yang Comments: -------------------- ## Uniffle Uniffle is an high performance, general purpose remote shuffle service for distributed computing engines. Uniffle has been incubating since 2022-06-06. ### Three most important unfinished issues to address before graduating: Promote the project and grow the user and dev community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? 1. 4 new contributors from different affiliations contributed to Uniffle project. 2. 70 issues have been created, among this 75 were discussed and resolved. 3. 2 discussion were occurred ### How has the project developed since the last report? 1. 70 issues have been created, among this 75 were discussed and resolved. 234 PRs has been created, among this 144 PRs were merged. 2. We're preparing v0.7.0 release ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2022-12-09 ### When were the last committers or PPMC members elected? Xianjing Feng, elected as committer on 2023-02-08 ### Have your mentors been helpful and responsive? Yes, they're helpful in guiding the podding project ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (uniffle) Felix Cheung Comments: - [X] (uniffle) Junping Du Comments: - [X] (uniffle) Liu Xun Comments: - [X] (uniffle) Weiwei Yang Comments: - [X] (uniffle) Zhankun Tang Comments: ### IPMC/Shepherd notes: -------------------- ## Wayang Wayang is a cross-platform data processing system that aims at decoupling the business logic of data analytics applications from concrete data processing platforms, such as Apache Flink or Apache Spark. Hence, it tames the complexity that arises from the "Cambrian explosion" of novel data processing platforms that we currently witness. Wayang has been incubating since 2020-12-16. ### Three most important unfinished issues to address before graduating: 1. Community building 2. release a new version 3. redo website and documentation to guide interesting developer ### Are there any issues that the IPMC or ASF Board need to be aware of? Nothing ### How has the community developed since the last report? We got new contributors from different companies and Universities. ### How has the project developed since the last report? Better community traction, adding new features ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards a second release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2021-12-13 ### When were the last committers or PPMC members elected? 2022-01-18: Calvin Kirs ### Have your mentors been helpful and responsive? Nothing to add here. ### Is the PPMC managing the podling's brand / trademarks? Yes, Wayang got approved by the ™ team, we don't face any trademark related issues. ### Signed-off-by: - [X] (wayang) Christofer Dutz Comments: I can see quite a bit more activity in the podling in this period - [ ] (wayang) Lars George Comments: - [ ] (wayang) Bernd Fondermann Comments: - [X] (wayang) Jean-Baptiste Onofré Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AJ: Report from the Apache IoTDB Project [Xiangdong Huang] ## Description: The mission of Apache IoTDB is the creation and maintenance of software related to an IoT native database with high performance for data management and analysis ## Issues: no ## Membership Data: Apache IoTDB was founded 2020-09-16 (2 years ago) There are currently 56 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Chao Wang on 2022-12-12. - Qingxin Feng was added as committer on 2022-12-15 - Haiming Zhu was added as committer on 2022-12-29 - Junqing Wang was added as committer on 2022-12-15 - Hongyin Zhang was added as committer on 2022-12-15 - Yongzao Dan was added as committer on 2023-01-04 ## Project Activity: IOTDB-0.13.4 was released on 2023-02-23. IOTDB-1.0.1 was released on 2023-02-22. IOTDB-1.0.0 was released on 2022-12-03. After releasing v1.0.0, The development of IoTDB (v1.x) is in progress. The community devotes itself to fixing bugs, introducing new features, and keeping the new version more stable. DBA tools like one-click deployment tool are also in development. One thing that the project and community should consider is how to solve the incompatibility between v0.x and v1.x. ## Community Health: The community keeps growing (more stargazers, contributors, etc.). And, the interaction amng ASF communities grows: - one IoTDB contributor is nominated to Ratis committer and acts as release manager of Ratis. - An online meetup for European developers is hosted by IoTDB joint SeaTunnel on March 2nd. Mailing list traffic decreases, which the PMC should take care. ----------------------------------------- Attachment AK: Report from the Apache Jackrabbit Project [Marcel Reutegger] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (17 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Joerg Hoh on 2022-07-01. - No new committers. Last addition was Joerg Hoh on 2022-07-01. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project team decided to require Java 11 as the minimum version for new feature releases. Apache Jackrabbit Oak 1.48.0 is the last release supporting Java 8. A roadmap has been outlined how to update the Guava dependency. The next Jackrabbit Oak release will make usage of deprecated APIs exposing Guava more visible by logging warn and error messages. Later this year the team plans to introduce a wrapped Guava version for Jackrabbit Oak internal use and then remove deprecated APIs. ## Community Health: The project is healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - filevault-package-maven-plugin-1.3.2 was released on 2022-12-16 - jackrabbit-oak-1.46.0 was released on 2022-12-21 - jackrabbit-2.20.8 was released on 2023-01-09 - jackrabbit-filevault-3.6.8 was released on 2023-01-10 - jackrabbit-oak-1.22.14 was released on 2023-01-19 - jackrabbit-oak-1.48.0 was released on 2023-01-27 - jackrabbit-2.21.15 was released on 2023-02-10 - jackrabbit-2.20.9 was released on 2023-03-10 ## JIRA activity: - 168 JIRA tickets created in the last 3 months - 146 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AL: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: The mission of the Apache Karaf project is the creation and maintenance of open-source software related to a generic platform providing higher level features and services specifically designed for creating OSGi-based servers for distribution at no charge to the public. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Karaf was founded 2010-06-16 (13 years ago) There are currently 31 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2018-11-29. - No new committers. Last addition was Francois Papon on 2018-05-19. ## Project Activity: Recent releases: * karaf decanter 2.10.0 was released on 2023-02-24. * karaf osgi runtime 4.3.9 was released on 2023-01-14. * karaf osgi runtime 4.4.3 was released on 2023-01-10. * karaf minho 0.1 was released on 2023-01-07. ## Community Health: We discussed to move Karaf Minho as TLP under Sunny name. However the namesearch didn't pass for Sunny, so we plan to submit board resolution to accept Apache Minho as TLP. The resolution will be submitted to the next board meeting. We also discussed about providing a new Karaf distribution named karaf-integration (as we have karaf-minimal), providing basically the same features as Apache ServiceMix distribution. We also plan to move forward on new bundle URL handler, allowing us to avoid ServiceMix bundles release. We also voted to move Karaf Cave and Karaf Winegrower to attic (removing them from website). We discussed with the Camel community about camel-karaf. We proposed (and voted) to move camel-karaf governance to karaf. We didn't reach a consensus. The plan is now to be engaged more within camel-karaf to maintain it and move forward with new features/enhancements. ----------------------------------------- Attachment AM: Report from the Apache Kyuubi Project [Kent Yao] ## Description: Apache Kyuubi™ is a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Kyuubi was founded 2022-12-21 (2 months ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - Fu Chen was added to the PMC on 2023-01-31 - Bowen Liang was added as committer on 2023-01-18 - Kaifei Yi was added as committer on 2023-01-18 ## Project Activity: - [RELEASE] We currently vote for v1.7.0 in dev@, which will be the 1st release after graduation. - [FEATURE] An SQL Authorizaton Plugin for Apache Spark based on Apache Range will be General Availiable. ## Community Health: - Users and developers like to report issues/features and ask questions on github, the team take a active response on issue resolution. Average issue resolution time keeps lower than 1d. We use dev maliing list for both dev and user discussions. We didn‘t see much traffic for use questions compared to the discussions on github. But important decisions are made there. - The Commit activity has retrun to normal(90~140/month) after the Spring Festial is over. - we still oberseve stable community growth based on the increasing of contributor list. ----------------------------------------- Attachment AN: Report from the Apache Linkis Project [Shuai Di] ## Description: The mission of Apache Linkis is the creation and maintenance of software related to a distributed computation middleware to facilitate connection, governance and orchestration between the upper applications and the underlying data engines ## Issues: There are no issues requiring board attention ## Membership Data: Apache Linkis was founded 2022-12-21 There are currently 34 committers and 24 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Shihao Xi was added as committer on 2023-02-22 ## Project Activity: Apache Linkis is preparing to release 1.3.2. This version have 24+ contributors participated, 7 new contributors added (currently:135) and 30+ new features included. Apache Linkis 1.4.0 in development. Software development activity: - We plan to participate in Open Source Summer in 2023 - We are preparing to release 1.3.2 in the coming month. At this time, we are focusing on trying to develop 1.4.0, and 1.4.0 looks to achieve these goals: - Supports Entrance ha and tasks failover. - Uniformly use jackson to process json format. - Flink engine connect can supports flink 1.14.x. - Upgrade the default hadoop spark and hive version to latest. Meetups and Conferences: - Community meetings(1) to discuss the dependencies of spark, hive and hadoop. ## Community Health: Overall community health is good. - 67 PRs merged on GitHub in the past month. - 114 issues closed on GitHub in the past month. ----------------------------------------- Attachment AO: Report from the Apache Lucene Project [Greg Miller] ## Description: The mission of Lucene is the creation and maintenance of software related to Search engine library ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Lucene was founded 2005-01-18 (18 years ago) There are currently 98 committers and 63 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Greg Miller on 2022-06-06. - Ben Trent was added as committer on 2023-01-27 ## Project Activity: 9.5 was released on 2023-01-30 - Release notes are available at: https://lucene.apache.org/core/9_5_0/changes/Changes.html - Some highlights released with 9.5 include: -- New fields making indexing in multiple formats easier for users -- DocValuesNumbersQuery improved and promoted from the "sandbox" module -- Optimizations when sorting by certain index sorts ## Community Health: Community interactions remain healthy. - dev@ mailing list traffic increased 123% compared to last quarter (668 emails compared to 299). - PR volume remains healthy, with open PRs trending in a steady state while closed PRs continue to increase at the same trend (https://home.apache.org/~mikemccand/lucenebench/github_pr_counts.html). ----------------------------------------- Attachment AP: Report from the Apache Lucene.Net Project [Shad Storhaug] ----------------------------------------- Attachment AQ: Report from the Apache Mnemonic Project [Yanhui Zhao] ----------------------------------------- Attachment AR: Report from the Apache MXNet Project [Sheng Zha] ## Description: The mission of Apache MXNet is the creation and maintenance of software related to a flexible and efficient library for Deep Learning ## Issues: - The activity from the community has reduced significantly as the main contributing groups gradually disengaged. - Part of the issue is the value proposition. Given the changes in the competitive space of deep learning, the existing plan no longer appear sufficient to attract enough engagement. To mitigate the situation, the PMC will discuss on potential new positioning of MXNet and find value proposition that makes sense considering the current landscape. ## Membership Data: Apache MXNet was founded 2022-09-20 (6 months ago) There are currently 87 committers and 51 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Anirudh Subramanian on 2022-09-20. - No new committers were added. ## Project Activity: Maintenance changes for v1.9: - Fix binary building process - Fix a long standing issue that causes segfault at exit and dataloader memory leakage. ## Community Health: The code development has slowed and the community engagement has reduced. 30 commits in the past quarter (-76% change) 5 code contributors in the past quarter (-50% change) 14 PRs opened on GitHub, past quarter (55% increase) 27 PRs closed on GitHub, past quarter (440% increase) 13 issues opened on GitHub, past quarter (44% increase) 6 issues closed on GitHub, past quarter (-25% change) ----------------------------------------- Attachment AS: Report from the Apache Mynewt Project [Szymon Janc] ## Description: The mission of Apache Mynewt is the creation and maintenance of software related to an embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android ## Issues: None. ## Membership Data: Apache Mynewt was founded 2017-06-21 (6 years ago) There are currently 36 committers and 19 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 Jerzy Kasenberg on 2019-10-24. - No new committers. Last addition was Krzysztof Kopyściński on 2021-01-26. ## Project Activity: No new release was made in past quarter. Next release is tentatively planned on late Q1 (early Q2) 2023. Community work in several areas including: test facilities, tooling, improvements in MCU and BSP support, qualification fixes for Bluetooth stack, USB support, bug fixes. Initial work on adding support for Bluetooth LE Audio has started. ## Community Health: We see some new (first time) contributors recently to the project, currently their PRs are pending review. Mailing list see little activity as most discussions happen on Slack and Github. ----------------------------------------- Attachment AT: Report from the Apache NetBeans Project [Geertjan Wielenga] ## Description: The mission of Apache NetBeans is the creation and maintenance of software related to development environments, tooling platforms, and application frameworks. ## Issues: No issuss needing the board's attention. ## Membership Data: Apache NetBeans was founded 2019-04-17 (4 years ago) There are currently 81 committers and 65 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - No new PMC members. Last addition was Michael Bien on 2022-05-01. - No new committers. Last addition was Jan Horváth on 2022-03-23. ## Project Activity: - Apache NetBeans 16 was released on 2022-11-30. - Apache NetBeans 17 was released on 2023-02-21. - The related support for VS Code was also released. - Binaries for the above were released too. - Details on features, fixes, contributors, now automatically generated here: - https://github.com/apache/netbeans/releases/tag/16 - https://github.com/apache/netbeans/releases/tag/17 ## Community Health: - Previously mentioned low voting activity of PMC members has been mitigated by doing one vote thread for the whole release, instead of multiple separate vote threads for each binary, which significantly slowed down the release process as we waited for each binary to get sufficient votes, which probably was not needed in the first place since Apache releases source code only. - dev@netbeans.apache.org had a 35% increase in traffic in the past quarter (650 emails compared to 478) ----------------------------------------- Attachment AU: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source product for the automation of enterprise processes that includes framework components and business applications for ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset Management). Apache OFBiz provides a foundation and starting point for reliable, secure and scalable enterprise solutions. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OFBiz was founded 2006-12-20 (16 years ago) There are currently 58 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - Daniel Watford was added to the PMC on 2023-01-18 - No new committers. Last addition was Mekika Leila on 2022-09-28. ## Project Activity: - No release was published in the last quarter: the next release will be the first of the 22.01 series. - Experiments on Docker based deployments for our demo instances hosted by the Apache Infra. - Code review is in process for the Codenarc integration - Migration of the official blog from Roller, that is going to be discontinued, to Hugo - Various contributions and bug fixes have been contributed. ## Community Health: We have invited a new PMC member. No new committers have been added but a few new contributors joined the project. Community activity over the last quarter has been on average: - In the user list questions were posted by our users and discussed/addressed on various topics such as accounting setup, sales and purchase order processing, payment methods, tips on user interface development and on deployment - In the dev list, where most of the traffic is originated from the activity on our code repository and on our ticketing system, topics discussed include: testing required on JDK17 in preparation of the new release, leveraging containers for the management of deployments of the OFBiz demo instances hosted by the Apache Infra, code review for the Codenarc integration, migration of the OFBiz website content from PHP to Hugo ----------------------------------------- Attachment AV: Report from the Apache Olingo Project [Michael Bolz] ## Description: The Apache Olingo Project be and hereby is responsible for the creation and maintenance of software related to providing an implemention of the OASIS OData (Open Data Protocol) specifications, in server and client form; ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Olingo was founded 2014-03-19 (9 years ago) There are currently 25 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Ramya Vasanth on 2019-04-15. - No new committers. Last addition was Archana Rai on 2017-05-26. ## Project Activity: Recent releases: - V2 2.0.12 was released on 2022-04-24. - 4.9.0 was released on 2022-03-09. - 4.8.0 was released on 2020-12-27. Planned maintenance release for 4.x and 2.x are delayed. Both should be done by end of April 2023. ## Community Health: Overall community health is a bit unhealthy. Activity on the mailing lists in last quarter again decreased. Also less activity in JIRA items and on GitHub. More activity is expected when the release preparation starts in March (as release of V2 and V4 versions are already requested). ----------------------------------------- Attachment AW: Report from the Apache OODT Project [Imesha Sudasingha] ----------------------------------------- Attachment AX: Report from the Apache OpenNLP Project [Jeff Zemerick] ## Description: The mission of OpenNLP is the creation and maintenance of software related to Machine learning based toolkit for the processing of natural language text ## Issues: The project would like guidance from the board on how to release NLP models, specifically around the voting process. Are there any other Apache projects releasing trained model artifacts? ## Membership Data: Apache OpenNLP was founded 2012-02-14 (11 years ago) There are currently 25 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Koji Sekiguchi on 2017-10-09. - Atita Arora was added as committer on 2023-02-28 - Martin Wiesner was added as committer on 2022-12-08 ## Project Activity: - OpenNLP 2.1.1 was released on February 23, 2023. ## Community Health: The community has been more active that this time last year. The project has added 3 new committers in the past few months and development activity in terms of Jira issues and pull requests has increased. The OpenNLP community is healthy. ----------------------------------------- Attachment AY: Report from the Apache OpenWebBeans Project [Mark Struberg] ----------------------------------------- Attachment AZ: Report from the Apache Pig Project [Koji Noguchi] ----------------------------------------- Attachment BA: Report from the Apache Pinot Project [Kishore G] ## Description: The mission of Apache Pinot is the creation and maintenance of software related to distributed OLAP data store to provide Real-time Analytics to power wide variety of analytical use case ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Pinot was founded 2021-07-21 (2 years ago) There are currently 31 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. We are looking into the committer list for new PMC member. - Jia Guo was added as committer on 2023-01-12 - Saurabh Dubey was added as committer on 2023-02-06 ## Project Activity: - Apache Pinot 0.12.0 was released on 2023-01-26. - We are going to prepare 0.13.0 release in the next month. - We are actively adding JOIN support for Apache Pinot query engine. ## Community Health: - We have merged >80 commits in March with 34 authors. - We >1000 visitors/day for Github page. - We have 3569 users in Apache Pinot slack workspace. ----------------------------------------- Attachment BB: Report from the Apache Pivot Project [Roger Lee Whitcomb] ----------------------------------------- Attachment BC: Report from the Apache PLC4X Project [Christofer Dutz] ## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache PLC4X was founded 2019-04-17 (4 years ago) There are currently 21 committers and 13 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 César García on 2021-10-01. - No new committers. Last addition was Jinlin Hong on 2022-11-02. Diversity wise, we still don't have even two of the active PMC members working for the same company. ## Project Activity: The community has been chipping away with various initiatives. We are receiving a constant stream of smaller issues via GitHub. After fixing a few of these, we are expecting to be releasing a new version of PLC4X pretty soon. ## Community Health: The community is generally active, however not as active as it used to be. Email activity has dropped quite a bit. Commit activity has dropped too, but this is probably mostly related to the fact that one of our main committers currently not able to contribute at the same level, but this is probably going to be resolved pretty soon. In order to address the slowdown of the community, we are planning on doing a community meetup near Frankfurt within the next quarter. Hopefully this will spark the sense of community a bit more again. ----------------------------------------- Attachment BD: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic] ## Description: The mission of the Apache Portable Runtime (APR) project is to create and maintain software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. The primary goal is to provide an API to which software developers may code and be assured of predictable if not identical behaviour regardless of the platform on which their software is built, relieving them of the need to code special-case conditions to work around or take advantage of platform-specific deficiencies or features. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Portable Runtime (APR) was founded 2000-12-01 (22 years ago) There are currently 69 committers and 44 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Yann Ylavic as new PMC Chair on 2023-02-16. - Steffen Land was added as committer on 2023-02-27 - Steffen Land was added to the PMC on 2023-03-02 Big thanks to Nick Kew for his great service as APR PMC Chair for 6 years! ## Project Activity: The project has released one APR and one APR-util versions, including bug fixes and addressing three long standing security issues with moderate impact ratings. apr-1.7.2 and apr-util-1.6.3 were released on 2023-02-01 after a couple of release candidates and un-announced 1.7.1/1.6.2 with tarball issues (new release scripts borrowed from httpd left some -rcX in the base directory). A new github actions/ci system was put in place which greatly helps maintainers' work and confidence in the releases quality. It's testing the three linux, macos and windows systems. Huge thanks to Ivan Zhakov for this work! ## Community Health: The project remains broadly healthy, though quiet. Activity increased on the dev@ mailing list mainly due to the release process. Bugzilla activity decreased but nothing worrisome given the usual moderate traffic. ----------------------------------------- Attachment BE: Report from the Apache Portals Project [Neil Griffin] ## Description: The mission of Portals is the creation and maintenance of software related to Portal technology. ## Issues: ## Membership Data: Apache Portals was founded 2004-02-17 (19 years ago) There are currently 40 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Neil Griffin on 2017-02-11. - No new committers. Last addition was Ahmed on 2016-08-06. ## Project Activity: There has been no project activity since the last report. Since the project is in maintenance mode, activity will typically only occur at the time of the annual release. ## Community Health: There is no recent activity on the dev lists, and no recent community contributions. Again, the project is in a maintenance mode. ----------------------------------------- Attachment BF: Report from the Apache Pulsar Project [Matteo Merli] ## Description: Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. ## Issues: - There are no issues requiring board attention at this time. ## Project Activity: - 2.10.3 was released on January 3rd 2023 - 2.9.4 was released on January 4th 2023 - 2.11.0 was released on January 10th 2023 - The PMC has approved a new models of Long Term Support, LTS releases PIP-175: https://github.com/apache/pulsar/issues/15966 The next release will be 3.0 and it's scheduled for May 2nd - Pulsar C++ releases: - pulsar-client-cpp 3.1.1 on January 27th 2023 - pulsar-client-cpp 3.1.2 on February 15th 2023 - Pulsar Python releases: - 3.0.0 was released on December 26th 2022 - 3.1.0 was released on March 13th 2023 - Pulsar reactive client: - 0.2.2 was released on February 6th 2023 - Pulsar NodeJS client: - 1.8.0 was released on January 4th 2023 - 1.8.1 was released on March 6th 2023 - We continue to have a very high number of "Pulsar Improvement Proposal" getting submitted, discussed and voted by the community: PIP-231: Add metric for topic load failed PIP-232: Introduce thread monitor to check if thread is blocked for long time. PIP-234: Support using shared thread pool across multiple Pulsar client instance PIP-235: Add metric for subscription backlog size PIP-236: Record schema in the request and carry to the broker when subscribing with AUTO_CONSUME schema. PIP-237: Make PulsarAdmin accessible in SinkContext and SourceContext PIP-238: Change the aggregatePublisherStatsByProducerName config default to true PIP-239: MAX RECONSUME TIMES per Message PIP-240: A new API to unload subscriptions PIP-242: Topic name restrictions PIP-243: Register Jackson Java 8 support modules by default PIP-244: Refactor ByteBuf release method PIP-245: Make subscriptions of NonPersistentTopic non-durable PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using avro-protobuf PIP-247: Notifications for partitions update PIP-248: Add metrics for backlog quota event PIP-249: Pulsar website redesign PIP-250: Add proxyVersion to CommandConnect PIP-251: Add snapshot stats in TransactionBufferStats PIP-252: Configurable compact topic retention PIP-253: Expose ProducerStats for deadLetterProducer & retryLetterProducer in java client PIP-254: Support configuring client version with a description suffix PIP-255: Support for Idempotent Commit and Abort. PIP-256: Building Great Developer Experience with API Content PIP-257: Add Open ID Connect Support to Server Components PIP-258: Deprecation of the consumer subscribeTopicMode configuration PIP-255: Assign topic partitions to bundles by round robin PIP-259: Make the config httpMaxRequestHeaderSize of the pulsar web server to configurable - Pulsar has reached 604 contributors on the main Github repo (It was 594 contributors in December 2022) ## Health report: - There is healthy growth in the community, and several users are starting to become contributors to the project and engage more and more with the community. In this quarter, 8 contributors were invited as committers to the project. ## Membership Data: Apache Pulsar was founded 2018-09-18 (4 years ago) There are currently 75 committers and 36 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: * Bo Cong was added to the PMC on 2023-01-12 * Nicolò Boschi was added to the PMC on 2023-01-19 * Yunze Xu was added to the PMC on 2022-12-28 * Baodi Shi was added as committer on 2023-01-17 * Tao Jiuming was added as committer on 2023-01-30 * Yuri Mizushima was added as committer on 2023-02-22 * Yubiao Feng was added as committer on 2023-02-07 ## Community Health: - Activity on the mailing lists remains 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. - users@pulsar.apache.org: - 25% decrease in traffic in the past quarter (72 emails compared to 96): - dev@pulsar.apache.org: - 16% increase in traffic in the past quarter (1062 emails compared to 914) ## Slack activity: - 9672 Members (9536 in December 2022) - 212 Active weekly users (218 in December 2022) ## GitHub activity: - 1052 commits in the past quarter (-26% decrease) - 111 code contributors in the past quarter (-16% change) - 654 PRs opened on GitHub, past quarter (-29% change) - 623 PRs closed on GitHub, past quarter (-46% change) - 307 issues opened on GitHub, past quarter (-21% change) - 257 issues closed on GitHub, past quarter (-79% change) ----------------------------------------- Attachment BG: Report from the Apache Roller Project [David M. Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat, Postgres and MySQL, and is known to run on other Java servers and relational databases. ## Issues: No issues require the board's attention. ## Membership Data: Apache Roller was founded 2007-02-20 (16 years ago) There are currently 12 committers and 7 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 Michael Bien on 2021-05-24. - No new committers. Last addition was Yash Maheshwari on 2021-09-01. ## Project Activity: Roller 6.1.1 was released on April 3, 2022. This past quarter has been fairly quiet. There has been some recent activity around refactoring. ## Community Health: The Roller community is healthy enough to maintain Roller and make bug fix and security releases. We're always on the lookout for new contributors. ----------------------------------------- Attachment BH: Report from the Apache Royale Project [Piotr Zarzycki] Hello, Apache Royale report March 2023 below: DESCRIPTION Apache Royale implements the principles of Apache Flex to support development of applications designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale improves developer productivity in creating applications to run wherever JavaScript runs, including on browsers, in Apache Cordova applications, on Node, and on other platforms. ISSUES There are no issues requiring board attention at this time. Membership Data No new PMC members. Last addition was Hugo Ferreira on 2022-10-27. No new committers. Last addition was María José Esteve on 2021-11-23. Last release of Apache Royale 0.9.9 was on March 30 2022. Project Activity Our release preparation goes on hold due to some issues on PMC's machine, there wasn't any new volunteer who would pick up release. Apart from that, some of our committers are adding new small features to the framework based on their project usage. Additionally, one of our PMC members released Apache Flex SDK Converter, which helps prepare Maven artifacts for release. Community Health We are seeing fewer emails in our Users list, while our development list is more active recently. Thanks, -- Piotr Zarzycki ----------------------------------------- Attachment BI: Report from the Apache Sedona Project [Jia Yu] ## Description: The mission of Apache Sedona is the creation and maintenance of software related to a big geospatial data processing engine. It provides an easy to use APIs for spatial data scientists to manage, wrangle, and process geospatial data ## Issues: Currently, we don't have any issues. We are aware of the discussion of potential naming and branding issues of Apache Sedona. ## Membership Data: Apache Sedona was founded 2022-12-20 (3 months ago) There are currently 16 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: 1. We plan to release Sedona 1.4.0 in one week. 2. Since the last report, the community spent lots of efforts on Sedona R binding improvement. The previous main contributor of Sedona R is no longer active and a new community member takes over and puts lots of efforts here. 3. The community also spent efforts on fixing the styling and doc errors. This will make the entire source code easy to read and maintain. ## Community Health: I cannot see the community health metrics due to some unknown reasons. Anyway, I collected the statistics myself. We have 8 active contributors made 37 commits to the Sedona repo. We have lots of activities on our mailing list, JIRA tickets and GitHub issues. In total, we had around 150 messages over all these channels. ----------------------------------------- Attachment BJ: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ----------------------------------------- Attachment BK: Report from the Apache Shiro Project [Brian Demers] ## Description: The mission of Shiro is the creation and maintenance of software related to Powerful and easy-to-use application security framework ## Issues: We have no issues that require Board assistance at this time. ## Membership Data: Apache Shiro was founded 2010-09-21 (12 years ago) There are currently 14 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:6. Community changes, past quarter: - No new PMC members. Last addition was Lenny Primak on 2022-12-04. - No new committers. Last addition was Lenny Primak on 2022-11-02. ## Project Activity: The Shiro team is actively working on 2.0 and 1.x is in maintance mode. - 2.0.0-alpha-1 was released on 2023-02-28 - 1.11.0 was released on 2023-01-07 ## Community Health: Excluding automated emails, mailing list traffic is up. Mostly related to conversations around Shiro 2.0 and dropping support for Java 8 (and supporting Jakarta packages). ----------------------------------------- Attachment BL: Report from the Apache SINGA Project [Wang Wei] ## Description: The mission of Apache SINGA is the creation and maintenance of software related to a distributed deep learning platform ## Issues: The team is preparing for V4.0 release and would like to report in the next month. ## Membership Data: Apache SINGA was founded 2019-10-16 (3 years ago) There are currently 23 committers and 16 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 Chris Yeung on 2020-04-17. - No new committers. Last addition was Naili Xing on 2022-11-19. ## Project Activity N.A............................................. ## Community Health N.A............................................................................. ----------------------------------------- Attachment BM: Report from the Apache Sling Project [Robert Munteanu] ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Sling was founded 2009-06-17 (14 years ago) There are currently 49 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Joerg Hoh on 2022-06-13. - Julian Reschke was added as committer on 2023-02-08 ## Project Activity: We released version 12 of our sample application, the Sling Starter, on March 18th, 2022. We have not yet made plans for version 13, but individual modules are being developed and released, with 28 releases for this reporting period. An effort is underway to migrate various Apache Sling modules from the javax.json APIs to the Jakarta JSON ones. Adapt.To, a conference that, amongst others, targets Apache Sling enthusiasts will take place 25th-27th September 2023 at KulturBrauerei in Berlin. ## Community Health: Activity seems lower all accross the board, based on Jira and GitHub activity. For instance, we had 375 commits ( 39% fewer ) and 26 contributors ( 13% fewer ). While the trend is worrying, this is not yet a problem in terms of absolute numbers, which are still healthy. ----------------------------------------- Attachment BN: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for March 2023 SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Status and health report: The project activities, including running our rule update infrastructure and our dev and user mailing lists, are continuing smoothly. Primary focus for development is now ongoing maintenance bug fixes to the recently released 4.0.0. Releases: Last release: Apache SpamAssassin version 4.0.0 on 17 December 2022. Note that we maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. Committer/PMC changes: Most recent new committer: Paul Stead (pds) 12 September 2018 Most recent new PMC members: Paul Stead (pds) 23 March 2021 ----------------------------------------- Attachment BO: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: The mission of Storm is the creation and maintenance of software related to Distributed, real-time computation system ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Storm was founded 2014-09-16 (9 years ago) There are currently 42 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Bipin Prasad on 2020-11-15. - No new committers. Last addition was Bipin Prasad on 2020-11-16. ## Project Activity: Storm is a project in maintenance mode, and as expected, project activity is low. Several developers are actively working on updates/patches. ## Community Health: The community and PMC is active enough to remain a TLP. The PMC recently decided against moving to the attic, and recently elected a new PMC chair after the previous one became inactive. There are ongoing discussions about adding additional committers/PMC members and we expect to add additional contributors in the near future. ----------------------------------------- Attachment BP: Report from the Apache Submarine Project [Liu Xun] ----------------------------------------- Attachment BQ: Report from the Apache Synapse Project [Isuru Udana] ----------------------------------------- Attachment BR: Report from the Apache Tomcat Project [Mladen Turk] ----------------------------------------- Attachment BS: Report from the Apache TomEE Project [David Blevins] ## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Contributions from non-committers over the last quarter have largely been in the areas of upgrading libraries and cleaning up properties. The challenge is, that these contributions are often untested and might introduce regressions, so we need to carefully run CI builds for every (little) pull request manually. Given that a TomEE full build takes around 8 hours on ASF hardware, this is a cumbersome adventure to monitor and track. Hopefully, INFRA can make some progress in providing ephermal runners hosted on AWS to ease this burden. List traffic, commits and number of releases is up significantly from the previous quarter as is often the case in the first quarter of the year. ## Activity After a considerable amount work, the project was able to pass all test required to claim Jakarta EE 9.1 Web Profile certification with TomEE 9.0.0. In addition, TomEE 9.0.0 is fully Micro Profile 5 compatible. First work started to move on to TomEE 10 which will target Jakarta EE 10 and MicroProfle 6.0. There is a long backlog of changes to the server that we've been delaying for the next major version, such as redoing how the server is built, eliminating drop-in war files and more that we've been discussing and are anxious to start now. As Jakarta EE 10 is the first release to have major new features since Java EE 8 and most Apache implementations still use the javax namespace there will be a major effort to migrate all related sources to the jakarta namespace. We are making good progress with these migrations. However,some more discussions are needed especially regarding the so-called "CDI Light" in CDI 4.0. We'll need to figure out how it can be implemented within OpenWebBeans. In addition, there were major changes in the tools to run the related specification TCKs as well as in the platform TCK itself. Our current setup does not work anymore, so we are currently in the process to figure out how we can run these tests in a performant way again. The project has begun discussion on end-of-life policies. In the past releases for older branches would simply stop being shipped with no formal decision or disclosure on shipping future releases. There is now a desire to formally decide on the future end-of-life date so users are aware and use the time to move to newer versions. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.14 on January 17, 2023 - Apache TomEE 9.0.0 on January 3, 2023 - Apache TomEE Patch Plugin 0.10.0 on January 2, 2023 - Jakarta EE API 10.0-M1, on January 11, 2023 - Jakarta EE API 9.1, on January 10, 2023 ----------------------------------------- Attachment BT: Report from the Apache TVM Project [Tianqi Chen] ## Description: The mission of Apache TVM is the creation and maintenance of software related to compilation of machine learning models to run on a wide range of hardware platforms ## Issues: There are no specific issues that would need actions from the board. We would like to disclose the recent resolutions by PMC this quarter to unblock some of the development in the community. See more in project activity section. ## Membership Data: Apache TVM was founded 2020-11-17 (2 years ago) There are currently 66 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - xinqi was added to the PMC on 2023-01-31 - Hongyi Jin was added as committer on 2023-01-17 - Yaxing Cai was added as committer on 2023-01-27 ## Project Activity: Recent releases: - 0.10.0 was released on 2022-10-17. - 0.9.0 was released on 2022-07-19. The project continues to bring new contributions. The latest set of improvement include highlighted areas: - Better TVMScript printing/parsing support. - Micro tvm and embedded devices support. - Improved support for nvidia TensorCore. - Better arithmetic support. On January, the TVM PMC passed a procedural resolution to enable branch development following lessons from other ASF projects and helping unblock some of the stagnation. Last Aug, a new module was proposed to add to the project, and the proposal was welcomed by many community members from more than eight organizations. The proposal brings a new module that potentially overlaps functionalities with existing modules. Majority of members participating the discussions were not concerned about the overlap and welcomed the proposal. However, there were disagreements from some community members on procedural operations the proposal. The discussions mainly boiled down to procedural questions about whether a migration plan and commitment to migration are necessary for the new module proposal at the point of the proposal or if the new module can co-exist with existing ones and empower different community members to develop them. The discussions has stagnated around winter break. After the winter break, the PMC took steps to resolve the stagnation and empower the community given a lot of asks from community in the thread about the empowerment. The first step compromise was to enable such development first in a branch. This would gives opportunity to empower members who would like to participate in the development and provide examples to those who wants to see more feasibility analysis of migrating some modules. We do not think this is something that would need board action as the PMC operates normally to bring a resolution and provide oversight support as being empowered by the ASF mechanism. We would like to disclose this to the board in the report for visibility. Please see the following threads for full context: the original public thread and resolution[1](also mirrored in dev). [1] https://github.com/apache/tvm-rfcs/pull/89#issuecomment-1404170556 The new branch development was established, with many community members support and contributions to the unity branch developments. The members are also actively publishing discussion, tutorials, and examples so there will be more awareness and hopefully also bring more lights on questions other community members might have. ## Community Health: The community continues to receive new contributions. Every month we received contributions from ~70 authors with ~ 130 commits to main branch. With the stagnation resolved, there are also a good amount of influx and interest of new contributions since the unity branch get established both in terms of code, demos, and examples. The community will hold the online community conference in the incoming week. The conference will talks from both the TVM community members and speakers from the broader machine learning compilation community. The community members also self-organize local meetups. Local meetup in shanghai was organized last week with over 100 people attended and engaged in lively discussions and communications (along with public thread summary), covering topics around TVM for NPU, SYCL, and possible opportunities in TVM unity. ----------------------------------------- Attachment BU: Report from the Apache UIMA Project [Richard Eckart de Castilho] ## Description: Apache UIMA (*) software provides frameworks, tools and annotators, facilitating the analysis of unstructured content such as text, audio and video. (*) Unstructured Information Management Architecture. ## Issues: There are no board-level issues at this time. ## Membership Data: Apache UIMA was founded 2010-03-17 (13 years ago) There are currently 26 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Pablo Duboue was added as PMC member on 2023-03-07 - Pablo Duboue was added as committer on 2023-03-06 ## Project Activity: - uima-uimaj-io-jsoncas-0.5.0 was released on 2023-03-06 - uima-ruta-3.3.0 was released on 2023-02-24 - uima-uimaj-3.4.1 was released on 2023-02-24 - uima-uimafit-3.4.0 was released on 2023-02-08 - uima-uimaj-3.4.0 was released on 2023-02-02 - vote to retire of the UIMA DUCC subproject has passed - retirement in progress - vote to retire of all v2.x versions of UIMA subprojects has passed - retirement in progress - vote to retire of the UIMA C++ SDK has been canceled after a community member Pablo Duboue has stepped up volunteering to take over the maintainer role. Pablo has been onboarded as a PMC member to be able to take on the new role. ## Community Health: The community remains moderately active. ClearTK 3.0.0 has also been released now. Apache cTAKES has been informed and hopefully that now enables them (as well as some other UIMA users out there) to upgrade to UIMAv3. Anybody with a committer role on the UIMA project and an account on the ASF Slack has been invited into the Slack UIMA channel. ----------------------------------------- Attachment BV: Report from the Apache Unomi Project [Serge Huber] ## Description: The mission of Apache Unomi is the creation and maintenance of software related to providing a reference implementation of the OASIS Customer Data Platform specification currently being worked on by the OASIS Context Server Technical Committee ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Unomi was founded 2019-02-20 (4 years ago) There are currently 16 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Taybou on 2021-03-19. - No new committers. Last addition was Francois Gerthoffert on 2022-09-15. ## Project Activity: We are now working on two branches at the same time, our cutting edge 2.x release that contains a lot of improvements, most notably in terms of reducing hosting costs with Elastic Cloud by drastically reducing the number of required Elasticsearch indices, and a 1.x branch that is used in production by a growing number of users. Since the last report we released version 1.8.0 that contains backports from 2.x as well as some library upgrades. We have also added support for multi-architecture Docker images to support better Apple silicon. ## Community Health: Our community remains healthy, with regular newcomers mostly on Slack, and a continuous stream of PRs on Github. Recently some community members were interested in working on supporting other backends (such as OpenSearch) but that is a big effort, to be seen if they can invest the time into it, but existing users are willing to help. Non-automated traffic in mailing lists remains low, clearly users prefer Slack. ----------------------------------------- Attachment BW: Report from the Apache VCL Project [Josh Thompson] ## Description: The mission of the Apache VCL project is to create and maintain of software related to a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache VCL was founded 2012-06-19 (11 years ago) There are currently 10 committers and 8 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Mike Jennings on 2020-08-24. - No new committers. Last addition was Mike Jennings on 2019-01-04. ## Project Activity: - Last release: 2019-07-25 - There has been little project activity since our last board report. As before, current committers are hopeful to get back to development soon. We are very aware of how long it has been since our last release. ## Community Health: Nothing has changed here - VCL continues to be a small but functioning community. We still have committers, PMC members, and users. ----------------------------------------- Attachment BX: Report from the Apache Wicket Project [Andrea Del Bene] ## Description: The mission of Wicket is the creation and maintenance of software related to Component-based Java Web Application Framework. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Wicket was founded 2007-06-20 (16 years ago) There are currently 33 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Thomas Heigl on 2020-08-14. - No new committers. Last addition was Thomas Heigl on 2020-05-18. ## Project Activity: On the last quarter we didn't have any new release but we expect to start rolling out version 9.13 as soon as we complete a couple of JIRA issues targeted for this 9.x version. Speaking about the next main release (the 10th) we have been slow down by the dependency on Apache Commons FileUpload 2.0-SNAPSHOT which has no release date yet for a milestone or a GA version. In the end we decided to go ahead coping what we need in our code base and switch to the official release whenever it will be available. In this way we hope to release a Wicket 10 M1 in the next months. ## Community Health: Our community remains healthy,and we are seeing an increasing interest for a first milestone release of Wicket 10. We have received contributes for Wicket 10 from three active members of other notable Open Source projects: - Francesco Chicchiriccò, founder of Apache Syncope and PMC member of different other Apache projects. - Richard Eckart de Castilho, contributor of project INCEpTION (https://github.com/inception-project/inception) which depends on Wicket - Tim te Beek, contributor for project OpenRewrite and also for Spring Boot and Apache Kafka Their collaborations will be really precious to help shaping Wicket 10 and we could also consider to invite one (or more) of them to become Wicket PMC ----------------------------------------- Attachment BY: Report from the Apache Xerces Project [Michael Glavassevich] Description Apache Xerces is a collaborative software development project dedicated to providing robust, full-featured, commercial-quality, and freely available XML parsers and closely related technologies on a wide variety of platforms supporting several languages. ======== Xerces-J There was very little activity since the previous report and was limited to responses on a handful of JIRA issues and a brief discussion about why Xerces-J never implemented XML 1.0 fifth edition. As observed by the board, there are a few users who have posted on the mailing lists and in JIRA issues for a long time who could be potential committers. We should reach out to them while they're still engaged with the project. Mailing list traffic has been low; roughly 30 posts on the j-dev and j-users lists since the beginning of December 2022. No new releases since the previous report. The latest release is Xerces-J 2.12.2 (January 24th, 2022). ======== Xerces-C After the Xerces-C 3.2.4 release there hasn't been much activity. In response to a request from the ASF Infrastructure team, the Travis CI job for Xerces-C was disabled in GitHub. Mailing list traffic was been very low; roughly 5+ posts on the c-dev and c-users lists since the beginning of December 2022. No new releases since the previous report. The latest release is Xerces-C 3.2.4 (October 17th, 2022). ======== Xerces-P Nothing in particular to report. There was no development activity over the reporting period. ======== XML Commons No activity over the reporting period. ======== Committer / PMC Changes The most recent committers were added in April 2017 (Xerces-C) and May 2017 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. Two committers have committed changes to SVN and GitHub since December 2022. ----------------------------------------- Attachment BZ: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ## Issues: (These were from the community section in the last report, however given that these are direct responses to the Board from questions raised, I am putting them here.) From the last board report: >Considering the amount of commits being done, I guess manual editing of >release notes should not be a real problem. I apologize for miscommunicating the situation in the last board report. One of the tools that Apache Yetus' provides is a release notes generation tool. This tool currently does not support Github. While those downstream users of our tools could certainly manually generate their own release notes that would effectively make their usage of Apache Yetus' release notes tool non-existent. In addition to listening to our userbase, the project also attempts to predict future needs since many downstream users are also open source projects. Their concerns about the lack of Github support in the Apache Yetus release note tool becomes the Apache Yetus project's concern. >And could you please elaborate a >bit more on what you mean with the second concern? How does a change in the >GitHub API require projects do more frequent releases? Again, I apologize for the miscommunication. Apache Yetus ties in very strongly with the Github API in a variety of capacities, but in particular in its ability to write Github Check Runs capabilities to report the results of builds. Given Github has announced that they will be rolling that API on a regular basis, it will likely result in _Apache Yetus_ performing more frequent releases which will result in the Apache Yetus' downstream users also pulling in the project's releases more frequently. Since there appears to be some confusion as to what the Apache Yetus project actually provides to other ASF projects, non-ASF OSS projects, and commercial entities that use the tooling, I'd be more than happy to present to the board or individuals as desired and/or necessary. ## Membership Data: Apache Yetus was founded 2015-09-15 (7 years ago) There are currently 12 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Akira Ajisaka on 2018-12-17. - No new committers. Last addition was Akira Ajisaka on 2018-02-06. ## Project Activity: 0.14.1 was released on 2022-10-17. A quiet quarter post release of 0.14.1. Most of the activity has been discussion around enhancing Github authentication for Github Enterprise deployments. ## Community Health: Nothing noteworthy to report here given the usual lull post-release and the general stability of the project. ----------------------------------------- Attachment CA: Report from the Apache Zeppelin Project [Lee Moon Soo] ## Description: The mission of Zeppelin is the creation and maintenance of software related to A web-based notebook that enables interactive data analytics ## Issues: There is a vote to change the chair. - https://lists.apache.org/thread/odk3o4xcnf34y4hl6gdpnn8rrtq166p0 ## Membership Data: Apache Zeppelin was founded 2016-05-18 (7 years ago) There are currently 24 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Jeff Zhang on 2018-01-25. - No new committers. Last addition was Guanhua Li on 2022-12-03. ## Project Activity: There is an internal event at LINE, which one of PMC members work at, to contribute Apache Zeppelin by empolyees. ## Community Health: - +5 new code contributors since last report. 70 total. - users@zeppelin.apache.org: - 20 emails sent to list - dev@zeppelin.apache.org: - 533 emails sent to list ----------------------------------------- Attachment CB: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables the implementation of a variety of primitives and mechanisms that are critical for safety and liveness in distributed settings, e.g., distributed locks, master election, group membership, and configuration. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache ZooKeeper was founded 2010-11-17 (12 years ago) There are currently 31 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Mate Szalay-Beko on 2022-03-28. - Zili Chen was added as committer on 2023-01-31 ## Project Activity: - 3.8.1 was released on 2023-01-30 - 3.6.4 was released on 2022-12-30. ## Community Health: The community released two new versions of the software, both bug-fix releases. A new committer has been onboarded and the community is working towards future maintenance and major releases. ------------------------------------------------------ End of minutes for the March 22, 2023 board meeting.