The Apache Software Foundation Board of Directors Meeting Minutes March 18, 2026 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:01 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2026-03-18T22:00:00&msg=ASF+Board+Meeting 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: Zili Chen Shane Curcuru Christofer Dutz Emmanuel Lécharny Justin Mclean Jean-Baptiste Onofré Christopher Schultz Greg Stein Sander Striker Directors Absent: none Executive Officers Present: Craig McClanahan Ruth Suehle Matt Sicker Craig L Russell Rich Bowen Executive Officers Absent: Jeff Jirsa Guests: Daniel Gruno Sally Khudairi Paul King Andrew Wetmore Thomas Neidhart Brian Proffitt Dave Fisher Danny Angus Alin Jerpelea Jarek Potiuk Kanchana Pradeepika Welagedara Henri Yandell Jens Scheffler Julien Le Dem - joined :04 Melissa Logan - joined :20 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of February 18, 2026 See: board_minutes_2026_02_18.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander Striker] This is the first meeting of the newly elected board following the Annual Members Meeting. I'd like to take a moment to acknowledge the outgoing directors and welcome the incoming ones. Thank you to Jim Jagielski, Rich Bowen, and Kanchana Pradeepika Welagedara for their service and their contributions to the foundation during their tenure on the board. Their dedication to the Apache Way and the health of the Foundation has been greatly appreciated. Welcome back to Christofer Dutz, and welcome to new Directors Christopher Schultz and Emmanuel Lécharny. We have already seen good engagement with the Board Agenda Tool, which is encouraging. As we settle in, it may be useful to calibrate on a few recurring questions: what does "dormant" mean in the context of a project? When do we typically suggest the Attic? How do we handle missing reports? And when do we flag a committee report? These are worth aligning on as a board early in the term. I also want to welcome the new members who were voted in at the Members Meeting. It is always good to see the membership grow. The Members Meeting itself is a significant undertaking, and I want to acknowledge the considerable effort that goes into running it. It is a process I am keen to continue improving. I am still working on finalizing attendance numbers — once I am confident that the last five years of data, including the most recent meeting, is accurate, I will communicate who would be the involuntary emeritus candidates for the next Members Meeting in 2027. This is by no means meant as a punitive measure, but strictly so we can continue to make quorum every year. Rich Bowen's last meeting as Vice Chair is a milestone worth marking. While Rich will be missed as both a Director and Vice Chair, I am very much looking forward to seeing the fruits of his efforts in Community Development — his enthusiasm for that work is, as many of us know, thoroughly contagious. We will hold an Executive Session at the end of this meeting, as is customary for the first board meeting of the term, to appoint the Board Chair and Vice Chair. On the topic of board meetups: I have not put a face-to-face meeting on the agenda for this term. I am open to opportunistic gatherings — for instance at Community Over Code — but I intend to keep those informal rather than structured working meetings. I will plan a separate teleconference for us to get to know each other better as a new board. B. President [Ruth Suehle] Two new subpoenas were received this month and forwarded to VP, Legal. Met with Sen. Becker (CA)'s staff to discuss Apache license and potential impacts of proposed AI policies on open source software. First draft budget is under the budget agenda item. Thanks to all of the budget area owners for all their work here! Because markdown doesn't yet work in discussion items, the below is identical to the Budget discussion item, but presented here for those who prefer the formatting. |Income| | | | |---|---|---|---:| | |Total Public Donations| |$100,000| | |Total Sponsorship | |$2,320,350| | |Conference Sponsorships| |$220,000| |Total Income| |   |$2,640,350|

|Expense| | | | |---|---|---|---:| | |General & Administrative| |$49,200[1] | | |Brand Management| |$80,000 | | |ComDev| |$0[2] | | |Conferences| |$100,000 | | |Fundraising| |$118,300 | | |Infrastructure| |$0[3] | | |Privacy| |$5,000 | | |Programs| |$1,200 | | |Public Affairs| |$40,000| | |Publicity| |$205,000 | | |Staffing| |$1,609,547[4] | | |Tooling| |$16,000| | |Travel Assistance| |$80,000 | | |Treasury| |$45,140[5] | | |Security| |$6,000 | | |Legal Affairs| |$0[6]| |Total Expense| |   |$2,562,227|
|Net| |   |$284,963|

[1] This eliminates the 100k President's Discretionary that dates back a few years. It does not include a Board F2F, so if the board wishes to hold one, please estimate a budget. It also proposes a 25k general travel fund to cover not only President travel (last year roughly $2,200), but also for officers and directors for ASF events and related to promote the foundation. [2] Last year, the usual ComDev budget for swag was moved to M&P and Conferences to launch the new logo. I have not yet received a request for budget from ComDev for this year. [3] Last year's Infra spend to date was $172,457 (as of several weeks ago). I do not have a projection from them yet for FY27. [4] Includes tooling and eliminates projected fundraising position. [5] This significant increase over last year requests funding for an audit, for which we are due. [6] I do not yet have a request for FY27 from VP, Legal. However, some legal counsel fees are accounted under "General and Administrative." Additionally, please see Attachments 1 through 11. C. Treasurer [Craig McClanahan] Normal operations continue, with the following specific notes: * Reviewed our Form 990 (the version of an income statement for non-profits) for the 2024-2025 fiscal year, and authorized sending it to the IRS. * Provided detailed information to Fundraising in support of their budget preparation. (We can do the same for other people that need it). * Completed Treasury's budget proposal for the next fiscal year. It includes funding for an audit, which we are overdue on having completed. (We aim for every three years, but it has been longer than that.) * Over time, we (Treasury) have received ad hoc requests for detailed information, especially during budget times as we are now. We've been working on some software that will provide information from both Bill and Ramp, specific to your area of responsibility, on a monthly basis. Look for an email from treasurer@apache.org requesting a time to meet briefly and discuss this with each of you in the near future. D. Secretary [Matt Sicker] In January, the secretary received 52 ICLAs and 2 CCLAs. In February, the secretary received 38 ICLAs, one CCLA, and one software grant. The secretary worked with the chair of the board to host the annual members meeting. E. Executive Vice President [Jeff Jirsa] The Executive Vice President has nothing material to report for March, but again encourages the new board to appoint a new Executive Vice President who will have sufficient free time to properly assist where needed. F. Vice Chair [Rich Bowen] Sent notification to all members converted to emeritus via Article 4, Section 4 of the bylaws. (Copied to secretary@ for permanent record.) Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Jean-Baptiste Onofré] See Attachment 12 B. Apache Legal Affairs Committee [Roman Shaposhnik / Sander Striker] See Attachment 13 C. Apache Security Team Project [Mark J. Cox / Greg Stein] See Attachment 14 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # AGE [elecharny] # Druid [schultz] # Helix [gstein] # Hudi [jmclean] # Incubator [elecharny] # Jackrabbit [schultz] # Kylin [cdutz] # Legal Affairs [cdutz, striker] # Linkis [gstein] # StreamPark [schultz] # VCL [schultz] A. Apache AGE Project [Jeff Jirsa / Shane Curcuru] See Attachment A B. Apache Airflow Project [Bolke de Bruin / Christofer Dutz] See Attachment B C. Apache Allura Project [Dave Brondsema / Emmanuel Lécharny] See Attachment C D. Apache Atlas Project [Madhanmohan Neethiraj / Justin Mclean] See Attachment D E. Apache Axis Project [Robert Lazarski / Christopher Schultz] See Attachment E F. Apache Beam Project [Kenneth Knowles / Zili Chen] No report was submitted. G. Apache Bigtop Project [Masatake Iwasaki / Greg Stein] See Attachment G H. Apache BookKeeper Project [Enrico Olivelli / Shane Curcuru] See Attachment H I. Apache BuildStream Project [Abderrahim Kitouni / Christopher Schultz] No report was submitted. J. Apache BVal Project [Matt Benson / Sander Striker] No report was submitted. K. Apache Camel Project [Andrea Cosentino / Christofer Dutz] See Attachment K L. Apache Cayenne Project [Michael Gentry / Emmanuel Lécharny] No report was submitted. M. Apache Celeborn Project [Keyong Zhou / Zili Chen] See Attachment M N. Apache CloudStack Project [Nicolás Vázquez / Jean-Baptiste Onofré] See Attachment N O. Apache Commons Project [Gary D. Gregory / Justin Mclean] See Attachment O P. Apache Cordova Project [Bryan Ellis / Christofer Dutz] See Attachment P Q. Apache cTAKES Project [Pei J Chen / Justin Mclean] See Attachment Q R. Apache Curator Project [Enrico Olivelli / Emmanuel Lécharny] See Attachment R S. Apache Daffodil Project [Mike Beckerle / Christopher Schultz] See Attachment S T. Apache DataFusion Project [Andrew Lamb / Greg Stein] See Attachment T U. Apache DevLake Project [Hezheng Yin / Zili Chen] See Attachment U V. Apache Doris Project [Mingyu Chen / Shane Curcuru] See Attachment V W. Apache Druid Project [Abhishek Agarwal / Sander Striker] See Attachment W X. Apache ECharts Project [Wenli Zhang / Jean-Baptiste Onofré] See Attachment X Y. Apache Felix Project [Karl Pauls / Emmanuel Lécharny] See Attachment Y Z. Apache Flex Project [Harbs / Justin Mclean] No report was submitted. AA. Apache Flink Project [Robert Metzger / Sander Striker] See Attachment AA AB. Apache Geronimo Project [Jean-Louis Monteiro / Zili Chen] No report was submitted. AC. Apache Gluten Project [Weiting Chen / Jean-Baptiste Onofré] See Attachment AC AD. Apache Gobblin Project [Abhishek Tiwari / Greg Stein] See Attachment AD AE. Apache Gravitino Project [Jerry Shao / Shane Curcuru] No report was submitted. AF. Apache Guacamole Project [Mike Jumper / Christofer Dutz] No report was submitted. AG. Apache Gump Project [Stefan Bodewig / Christopher Schultz] See Attachment AG AH. Apache Helix Project [Junkai Xue / Christofer Dutz] See Attachment AH @Christofer Dutz: follow up about roll call AI. Apache Hive Project [Naveen Gangam / Greg Stein] See Attachment AI AJ. Apache Hudi Project [Vinoth Chandar / Justin Mclean] See Attachment AJ @Justin Mclean: follow up about use of votes AK. Apache HugeGraph Project [Jermy Li / Sander Striker] See Attachment AK AL. Apache Iceberg Project [Ryan Blue / Zili Chen] See Attachment AL AM. Apache Incubator Project [Justin Mclean / Jean-Baptiste Onofré] See Attachment AM AN. Apache IoTDB Project [Xiangdong Huang / Emmanuel Lécharny] See Attachment AN AO. Apache Jackrabbit Project [Marcel Reutegger / Christopher Schultz] See Attachment AO AP. Apache Karaf Project [Jean-Baptiste Onofré / Shane Curcuru] See Attachment AP AQ. Apache Kvrocks Project [Mingyang Liu / Greg Stein] See Attachment AQ AR. Apache Kylin Project [Yang Li / Christopher Schultz] See Attachment AR @Christopher Schultz: pursue a roll call AS. Apache Kyuubi Project [Cheng Pan / Zili Chen] See Attachment AS AT. Apache Linkis Project [Shuai Di / Sander Striker] See Attachment AT AU. Apache Lucene Project [Ben Trent / Emmanuel Lécharny] See Attachment AU AV. Apache Lucene.Net Project [Shad Storhaug / Christofer Dutz] No report was submitted. AW. Apache MADlib Project [Ed Espino / Justin Mclean] No report was submitted. AX. Apache Mynewt Project [Szymon Janc / Shane Curcuru] See Attachment AX AY. Apache NetBeans Project [Geertjan Wielenga / Jean-Baptiste Onofré] See Attachment AY AZ. Apache OFBiz Project [Jacopo Cappellato / Christofer Dutz] See Attachment AZ BA. Apache OpenDAL Project [Hao Ding / Shane Curcuru] See Attachment BA BB. Apache OpenNLP Project [Jeffrey T. Zemerick / Emmanuel Lécharny] See Attachment BB BC. Apache OpenWebBeans Project [Mark Struberg / Greg Stein] No report was submitted. BD. Apache Paimon Project [Jingsong Lee / Zili Chen] See Attachment BD BE. Apache Pekko Project [PJ Fanning / Jean-Baptiste Onofré] See Attachment BE BF. Apache Pig Project [Koji Noguchi / Sander Striker] No report was submitted. BG. Apache Pinot Project [Kishore G / Justin Mclean] No report was submitted. BH. Apache PLC4X Project [César García / Christopher Schultz] No report was submitted. BI. Apache Polaris Project [Jean-Baptiste Onofré / Christofer Dutz] See Attachment BI BJ. Apache Portable Runtime (APR) Project [Yann Ylavic / Sander Striker] See Attachment BJ BK. Apache Pulsar Project [Matteo Merli / Greg Stein] See Attachment BK BL. Apache RocketMQ Project [Xiaorui Wang / Christopher Schultz] See Attachment BL BM. Apache Royale Project [Andrew Wetmore / Emmanuel Lécharny] See Attachment BM BN. Apache SeaTunnel Project [Jun Gao / Zili Chen] See Attachment BN BO. Apache ServiceComb Project [Zhangjian He / Shane Curcuru] See Attachment BO BP. Apache ServiceMix Project [Krzysztof Sobkowiak / Justin Mclean] No report was submitted. BQ. Apache Shiro Project [Lenny Primak / Jean-Baptiste Onofré] See Attachment BQ BR. Apache SINGA Project [Wang Wei / Greg Stein] See Attachment BR BS. Apache Sling Project [Robert Munteanu / Shane Curcuru] See Attachment BS BT. Apache SpamAssassin Project [Giovanni Bechis / Emmanuel Lécharny] See Attachment BT BU. Apache Storm Project [Richard Zowalla / Zili Chen] See Attachment BU BV. Apache StreamPark Project [Huajie Wang / Jean-Baptiste Onofré] See Attachment BV @Jean-Baptiste Onofré: provide template for next board report BW. Apache Synapse Project [Isuru Udana / Christopher Schultz] No report was submitted. BX. Apache Teaclave Project [Zhaofeng Chen / Sander Striker] See Attachment BX BY. Apache Tomcat Project [Christopher Schultz / Justin Mclean] See Attachment BY BZ. Apache TVM Project [Tianqi Chen / Christofer Dutz] See Attachment BZ CA. Apache UIMA Project [Richard Eckart de Castilho / Christofer Dutz] See Attachment CA CB. Apache Unomi Project [Serge Huber / Greg Stein] See Attachment CB CC. Apache VCL Project [Josh Thompson / Christopher Schultz] See Attachment CC CD. Apache Wicket Project [Andrea Del Bene / Jean-Baptiste Onofré] See Attachment CD CE. Apache Xerces Project [Michael Glavassevich / Shane Curcuru] See Attachment CE CF. Apache Yetus Project [Allen Wittenauer / Emmanuel Lécharny] See Attachment CF CG. Apache ZooKeeper Project [Flavio Junqueira / Zili Chen] See Attachment CG Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache CloudStack Project Chair WHEREAS, the Board of Directors heretofore appointed Nicolás Vázquez (nvazquez) to the office of Vice President, Apache CloudStack, and WHEREAS, the Board of Directors is in receipt of the resignation of Nicolás Vázquez 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 Wido den Hollander (widodh) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Nicolás Vázquez is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache CloudStack, and BE IT FURTHER RESOLVED, that Wido den Hollander 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 7A, Change the Apache CloudStack Project Chair, was approved by Unanimous Vote of the directors present. B. Terminate the Apache ServiceMix Project WHEREAS, the Project Management Committee of the Apache ServiceMix project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache ServiceMix project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache ServiceMix project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache ServiceMix Project; and be it further RESOLVED, that the office of "Vice President, Apache ServiceMix" is hereby terminated; and be it further RESOLVED, that the Apache ServiceMix PMC is hereby terminated. Special Order 7B, Terminate the Apache ServiceMix Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Budget The budget-owning officers have been working on submitting their needs for the coming year. Notes about any significant changes from the previous year are below. The final Budget will be presented in the April meeting. Income ======= Total Public Donations $100,000 Total Sponsorship $2,320,350 Conference Sponsorships $220,000 Total Income $2,640,350 Expense ======== General & Administrative $49,200[1] Brand Management $80,000 ComDev $0[2] Conferences $100,000 Fundraising $118,300 Infrastructure $0[3] Privacy $5,000 Programs $1,200 Public Affairs $40,000 Publicity $205,000 Staffing $1,609,547[4] Tooling $16,000 Travel Assistance $80,000 Treasury $45,140[5] Security $6,000 Legal Affairs $0[6] Total Expense $2,355,387 Net $284,963 [1] This eliminates the 100k President's Discretionary that dates back a few years. It does not include a Board F2F, so if the board wishes to hold one, please estimate a budget. It also proposes a 25k general travel fund to cover not only President travel (last year roughly $2,200), but also for officers and directors for ASF events and related to promote the foundation. [2] Last year, the usual ComDev budget for swag was moved to M&P and Conferences to launch the new logo. I have not yet received a request for budget from ComDev for this year. [3] Last year's Infra spend to date was $172,457 (as of several weeks ago). I do not have a projection from them yet for FY27. [4] Includes tooling and eliminates projected fundraising position. [5] This significant increase over last year requests funding for an audit, for which we are due. [6] I do not yet have a request for FY27 from VP, Legal. However, some legal counsel fees are accounted under "General and Administrative." B. [Executive Session] Appoint Board Chair and Vice Chair Audience: Directors, Secretary At the first Board meeting after its election, the Board reviews Board Chair and Vice Chair appointments. By consent, the Board approved Sander Striker to continue to serve as Board Chair. C. Regular Meeting Schedule Determine the best time for future board meetings this year. Proposal: - 21:00 UTC April - October - 22:00 UTC November - March D. [Executive Session] Fundraising Audience: Directors, Secretary, President, Fundraising Fundraising would like to give an update on the sponsorship proposal that was presented in February to the outgoing Board. Began at 17:55. Ended at 18:06. The board was informed about a fundraising opportunity. No decisions were made at this time. E. [Executive Session] Appoint Executive Vice President Audience: Directors, Secretary, President Began at 18:09, ended 18:28. Executive Vice President: the board appointed Daniel Ruggeri. Vice Chair: the board appointed Justin Mclean. The board keeps the remaining executive officers. 9. Review Outstanding Action Items * Jean-Baptiste Onofré: pursue potential Attic for CarbonData [ CarbonData 2025-08-20 ] Status: Done. I started a discussion: https://lists.apache.org/thread/jf385z0yw00kfjqgg58yfwg3s30sz6k5 Clear sign of new activity, both in the contribution and governance (new PMC Chair). I'm proposing to follow up the next board reports and re-evaluate. * Sander Striker: discuss Policy for Inactive Committers with project PMC [ NiFi 2025-10-15 ] Status: https://lists.apache.org/thread/wnph5t6xn9rts4smhtd2gmfpjktyqjv8 * Greg Stein: talk to Pinot PMC about communication channels [ Pinot 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Greg Stein: follow up with TsFile PMC about publishing to PyPI [ TsFile 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Greg Stein: follow up with board about PyPI policy [ TsFile 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Jim Jagielski: pursue roll call for Ambari [ Ambari 2026-01-21 ] Status: Roll call request sent and replies are rolling in * Kanchana Pradeepika Welagedara: pursue roll call for Rya [ Rya 2026-01-21 ] Status: Roll call has been sent. It's less than a week. Need to give them more time /So far only 1 (0) * Jim Jagielski: explain trademark process [ Wayang 2026-01-21 ] Status: * Jean-Baptiste Onofré: pursue roll call for XML Graphics [ XML Graphics 2026-01-21 ] Status: Roll call started: https://lists.apache.org/thread/6jnfh77mx8tmjv1m8xgcxv8jnxhllg5h * Rich Bowen: explain Attic [ OpenWhisk 2026-02-18 ] Status: * Zili Chen: follow up about reporting and chair requirements [ RocketMQ 2026-02-18 ] Status: Discussed with the current PMC chair. I'll send the email to private@rocketmq.a.o later. * Jean-Baptiste Onofré: follow up moving to Attic [ ServiceMix 2026-02-18 ] Status: Resolution to move to attic submitted. * Shane Curcuru: follow up about licensing [ SIS 2026-02-18 ] Status: * Rich Bowen: remind about reporting [ Velocity 2026-02-18 ] Status: * Kanchana Pradeepika Welagedara: connect with downstream PMCs [ Web Services 2026-02-18 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 23:29 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period February 2026 * ISSUES FOR THE BOARD None * OPERATIONS Daan Hoogland has started to provide some very welcome assistance with trademark issues. Responded to the following queries, liaising with projects as required: - Approved the name POLARIS - Provided advice on proposed new business card templates - Provided advice to AIRFLOW regarding branding customisation * REGISTRATIONS Started the process to register the SUPERSET mark. The transfer of the GRAILS marks to the ASF is in progress. The transfer of the HUGEGRAPH marks to the ASF is in progress. * INFRINGEMENTS In conjunction with the PMC, the decision has been made to take no further enforcement steps at this time and continue to monitor the situation. No progress regarding a site with a possible infringement of APISIX. There has been some progress regarding the downstream vendor with multiple infringements of ASF marks. The Tomcat PMC dealt with an external party making incorrect statements regarding the level of support provided by the community. The XMLGRAPHICS PMC is progressing a complaint with GitHub regarding a potential third-party infringement of FOP. No progress from the GLUTEN PMC to address a range of product naming issues with multiple 3rd parties. No progress for The KAFKA PMC in addressing a potential infringement of KAFKA. The ICEBERG PMC has resolved issues with a LinkedIn page. There has been significant progress for the ongoing IOTDB issues with just one final issue to resolve. No progress for the SPARK PMC in addressing a range of product naming issues with multiple 3rd parties. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: we are onboarding a corporate contributor that will be recognized as a Silver Sponsor. b —Renewals: we have secured renewals with one Platinum, one Gold, and one Silver Sponsor (downgraded from Platinum). c —Payments: 1 —New: we received no payments towards new Sponsorships during this time period; 2 —Received: we received Sponsorship renewal payments from one Platinum Sponsor; 3 —Incoming: we await renewal payments from two Platinum, four Gold, and two Silver Sponsors, plus a corporate contribution that would provide the donor Silver Sponsor level recognition 2) Targeted Sponsors: we have confirmed a new Platinum Targeted Sponsor to back the ASF Tooling Initiative. Additionally, we are negotiating a new Targeted Sponsorship. We resolved a long-standing identity management issue with onboarding onto a vendor payment platform that’s increasingly being used by more Sponsors. 3) Sponsor Relations: our standing engagement activities continue, including renewals, new Sponsor cultivation, and Targeted Sponsorship proposal development. 4) Event Sponsorship: we have begun to promote sponsorships for 2026 for Community Over Code Europe as well as Lakehouse Day, and are working with VP Conferences on the Sponsorship Agreements for one Platinum, one Silver, and one Lakehouse Day sponsor. We have also launched standalone Travel Assistance/TAC sponsorships that can be coupled with existing conference packages or support attendees at a future event. Those who are providing sponsorship support at a recognized Targeted Sponsorship threshold will be recognized at their respective level for one calendar year from the date of funds received. https://apache.org/foundation/sponsorship.html#foundation-sponsorship 5) Individual Donations and Corporate Giving: we received $2,000 in online donations via https://donate.apache.org/ . 6) Administrivia: we have been coordinating activities with the ASF Infrastructure team on a Targeted Sponsorship, as well as with VP Tooling on needs for CY2026. Our activities with Accounting, Treasury, Marketing & Publicity, and Conference are ongoing with no outstanding issues at this time. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] Foundation Comms * Produced and issued January issue of Plus One newsletter * Produced and issued February issue of Plus One newsletter * Subscriber list now totals 2,515 (440 new subscribers in February) * Total sent: 2,200 | Unique opens: 589 | Open rate: 26% * Published blog touting the CFP for Community Over Code and introduced Lakehouse Day * Coordinated interview with The ASF and The Stack for an article about incubating projects from China * Finalized and launched first annual spring survey for ASF members Project Comms * Issued press release announcing Apache HugeGraph as a TLP * Developed and published Part I of a three-part series featuring Apache Geode Brand Project * Finalized #ASFNewLeaf social media giveaway by shipping ASF-branded swag to contest winners * Continued coordination between Apache projects and graphic designer to update logos that contain feather or native imagery * Continued development and coordination for “ATR Certified” logo options for Apache Tooling Digital * Updated navigation to remove Infra from the Downloads section * Developed posting guidelines for ASF Mastodon Contributors to follow * Posted guidelines for YouTube/video content creation Social Media Overview Social Highlights (X + LinkedIn + Bluesky)* * Total Audience: 147,562 * X: 66,087 * Bluesky: 1,006 * LinkedIn: 80,469 * Total Posts: X: 32 * Bluesky: 32 * LinkedIn: 13 * Total Engagements: 3,476 Bluesky analytics are still hard to get consistently without paying for a separate service. We hope Buffer will add this reporting capability soon. Website Analytics * 659,894 visits, 659,823 unique visitors -2.9% * 2 min 22s average visit duration -6% * 62% visits have bounced (left the website after one page) -- * 2.3 actions (page views, downloads, outlinks, internal site searches) per visit -4.2% * 1,158,625 pageviews, 818,242 unique pageviews -8.1% * 4 total searches on your website, 2 unique keywords -80% * 103,917 downloads, 74,251 unique downloads -9.9% * 236,325 outlinks, 157,649 unique outlinks -9.1% ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Danny Angus] General ======= No issues currently require the Board's attention. Budget ====== FY27 Budget planning is underway. STeVe v3 in the Recent Members Meeting ====================================== We are pleased to report that the Infra successfully utilized STeVe v3 to conduct the election process of the latest Member's meeting. The platform offered an improved experience over its predecessor, STeVe v2. The new workflow of loading votes and processing results was a significant improvement. Critical support from the STeVe PMC, notably Greg Stein, was instrumental in ensuring a smooth rollout. Based on this positive experience, Infra intends to continue using STeVe v3 for future elections. ASF Members Meeting Platform (ASFMM) in the recent Members Meeting ================================================================== The meeting platform used for the annual members meeting worked as expected, and ensured a mostly problem-free meeting. Some issues that surfaced this year have been reported and issues and pull requests are being set up to track them. MFA Efforts =========== Testing and rollout was paused to assess issues which arose during a routine upgrade of the MFA platform. A resolution is pending, but a production instance of the authentication system is being deployed and soft-launch will be continuing as of or before 13 April. Other News ========== Per Infra's February Board report, the ReviewBoard service is slated for retirement 31 March. Infra has received no pushback or concerns from Projects related to this. Atlassian Cloud migration testing continues. Infra will be presenting a summary of the project and what committers can expect at the 1 April Infra Roundtable. Community News ============== Roundtable: Infra's next Roundtable will be April 1. See https://infra.apache.org/roundtable for how to join the Roundtable channel and take part in the monthly meetings. Community over Code: Infra will be sharing a series of presentations and events at Community Over Code Glasgow, and are open to community (including board@) suggestions for content. ----------------------------------------- Attachment 5: Report from the VP of Tooling [Dave Fisher] # Tooling This month's report will consist of a quick progress report. ## Apache Trusted Releases (ATR) Our current development focus includes the following tasks. 1. Our ASVS security review generated about 150 GH issues. We now have less than 20 remaining before we re-run L1 and run L2 requirements. The exercise has been a very helpful code review. 2. We added the quarantine phase to validate upload artifact archives as safe for expansion and free from zip bombs, path traversal, duplicate paths, etcetera. This work proceeds with tightening up preparations for a vote. 3. We refactored the codebase for type safety. 4. Preparing for a quick Alpha 3 in late March or early April. 5. Beta is planned for sometime in Q2. ## Board Agenda Tool (BAT) The reporter.apache.org website is fully integrated. Also, Whimsy is now only doing minutes views. We are ready to discuss what improvements the new board of directors would like implemented. We have a test instance for working on reporter changes and are open to volunteer help. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Brian Proffitt] CFP for Community Over Code Glasgow 2026 continues until March 20[1], along with the CFP for the co-located Lakehouse Day[2]. The prospectus for all of these events was released[3] in late February. I am pleased to report we already have sponsorship agreements in process from new and returning sponsors this year. Community Over Code Asia was announced, to take place August 7 to 9，2026 in Beijing, China. I am also in consultation with the web team that revamped www.apache.org to update and expand communityovercode.org into something as robust and flexible as apachecon.com. [1] https://s.apache.org/CFP2026 [2] https://sessionize.com/lakehouse-day-2026/ [3] https://communityovercode.org/wp-content/uploads/2026/02/Community-Over-Code-Prospectus-2026.pdf [4] https://asia.communityovercode.org/ ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== Community Over Code Glasgow --------------------------- Applications for Community over Code 2026 being held in Glasgow opened up last month and we have 13 applications in at this early stage. Community over Code Asia - Beijing ---------------------------------- Applications for Beijing will be opening up soon. Budget ------ TAC has submitted its budget for the next Financial Year. Monthly Meetings ---------------- Monthly meetings will resume in April Future Events ------------- None currently Short/Medium Term Priorities ---------------------------- Keeping an eye out for other smaller events to support. Berlin Buzzwords is one we have supported before and if we have budget would like to have some people attend that one. Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still to be done. Mailing List Activity --------------------- TAC Co-ordinators chosen to lead Glasgow and Beijing Membership ---------- No changes to the Committee this month. ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno] ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik] Nothing that needs board attention this month. EU published its guidance - which, by and large, is good & solid; and clarifies a lot of the edge cases exactly as it should be/we had expected based on the gist of the regulation -- and with a good understanding of open source and its interactions with industry. We're working with our peers to provide comments. But even if none of that bears fruit - things are good enough; and we, as open source, navigated past this hazard unscathed. Likewise - the Expert meeting saw no surprises. There is still a mild concern about the progress/availability of the reporting platform (that we need to interact with from September) - and some more concerns on the completeness and quality of the normative standards. But nothing new or significantly worse. With the guidance done - attention is more and more shifting to attestation; and here to - a coalition of open source foundation and our industrial community is coming together well at the open regulatory working group (hosted well at Eclipse). ----------------------------------------- Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz] Within the various ECMA TC54 task groups: * TG-1 (Transparency Exchange API – TEA) TG-1 will not submit a first version of the Transparency Exchange API to ECMA in June. Instead, version 1.0 will first be released as a “community version”, with standardization expected in September. Since TEA has grown significantly in size since its inception, there is an ongoing discussion within ASF Tooling regarding which parts of the specification should be supported by Apache Trusted Releases (ATR): https://github.com/apache/tooling-trusted-releases/issues/614 * TG-2 (Package URL – PURL and VERS) TG-2 is currently focused on the proposed “SCID” PURL type: https://github.com/package-url/purl-spec/issues/516 This proposal introduces a Package URL type for non-packaged software. It could be relevant to the ASF for identifying not only C/C++ projects and other languages without traditional packaging systems but also binary executable distributions produced by many projects. During discussions it was also noted that publishing PURLs for ASF artifacts might warrant consultation with ASF Legal, since ASF binaries are “convenience binaries” rather than official foundation releases. Using identifiers containing “apache.org” or “The Apache Software Foundation” may therefore have legal implications. * TG-4 (OSS Sustainability) TG-4 continues work on a model to express project sustainability needs in a machine-readable form. Recent discussions have focused on representing both traditional OSS contribution needs (e.g., “triagers needed”) and potential funding opportunities (e.g., “additional triaging bandwidth available if funded”). It may be worth evaluating whether committers could express these needs within ASF repositories, or whether doing so would conflict with ASF bylaws. ----------------------------------------- Attachment 12: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 13: 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. Many thanks to Henri Yandell for making us go to the lowest number of outstanding LEGAL issues ever (which is 9). We have formally onboarded Jude Smith as an ASF "committer" on the LEGAL committee and he is now known as jasmith@apache.org DLAPiper has gotten back to us with the good news on the outstanding subpoena indicating that they checked the court docket, and the company that issued the subpoena to ASF has filed a joint request with the plaintiff to dismiss the case with prejudice. The bad news is that our outstanding pipeline of subpoenas is now at 3 and that's WAY more than what our volunteer workforce can handle. We are working with DLAPiper to help but they have been really slow when it comes to a formal engagement. This may turn into a significant risk for the foundation. ----------------------------------------- Attachment 14: Report from the Apache Security Team Project [Mark J. Cox] February * We're seeing a sharp increase in incoming security reports, with AI as likely driver. While it's too early to determine the validity rate of these reports, we are factoring the increased volume into our budget planning for the next financial year. * We continue to help projects define a security model, this month Apache Arrow, DevLake, and POI. * We're closely following Infra's progress in rolling out MFA and intend to provide feedback and assistance. * We're rolling out an ASF-wide overview of disclosed security vulnerabilities in our software, e.g. https://security.apache.org/projects/arrow/ * We reported in November 2025 that a ransomware group had claimed it would release a cache of documents related to Apache OpenOffice. It now appears the claim was based on incorrectly scraped company name information and did not affect Apache OpenOffice or the Apache Software Foundation. * We're help projects audit their GitHub Actions usage. Stats for February 2026: 35 [license confusion] 29 [support request/question not security notification] 8 [report/question relating to dependencies] Security reports: 200 (last months: 160, 98, 85) 19 ['logging'] 18 ['airflow'] 12 ['ofbiz', 'tomcat'] 9 ['httpd'] 8 ['website or other infrastructure'] 7 ['arrow'] 5 ['commons', 'fineract', 'flink'] 4 ['answer', 'apisix', 'doris', 'hertzbeat', 'zeppelin'] 3 ['druid', 'dubbo', 'iotdb', 'kylin', 'spark', 'superset'] 2 ['activemq', 'ambari', 'artemis', 'beam', 'camel', 'hugegraph', 'ignite', 'inlong', 'jspwiki', 'kafka', 'nifi', 'nuttx', 'openmeetings', 'openoffice', 'rocketmq', 'skywalking'] 1 ['avro', 'celeborn', 'cloudstack', 'couchdb', 'cxf', 'devlake', 'dolphinscheduler', 'echarts', 'eventmesh', 'fory', 'guacamole', 'hbase', 'http', 'kie', 'lucene', 'pdfbox', 'poi', 'polaris', 'ranger', 'roller', 'shardingsphere', 'solr', 'struts', 'teaclave', 'tika', 'trafficserver', 'tvm', 'velocity', 'wicket', 'xmlgraphics'] In total, as of 2nd Mar 2026, we're tracking 440 (last months: 359, 297) open issues across 102 projects, median age 64 days (last months: 79, 105). 90 of those issues have CVE names assigned. 22 (last months: 25, 20) of these issues, across 11 projects, are older than 365 days. No Health red issues to report. * carbondata (Health amber): PMC is not responsive (Last update: 2026-03-03) * fineract (Health amber): there are a number of open issues over a year old. The PMC is making progress with documentation and architectural changes, and more focus expected to close out these issues. (Last update: 2026-01-06) * openoffice (Health amber): Several issues in OpenOffice are over 365 days old. They are not severe enough to warrant stopping distribution of OpenOffice. The November release fixed the most serious and complex ones, making space to now focus on the remaining issues. (Last update: 2026-02-05) * spark (Health amber): the project has a backlog of security reports to be triaged (Last update: 2026-03-03) * superset (Health amber): while the project is actively publishing fixes to security issues each release, there is concern about a growing backlog. (Last update: 2026-03-03) * thrift (Health amber): the PMC does not appear to have the bandwidth to triage incoming reports in a timely fashion (Last update: 2026-02-05) ----------------------------------------- Attachment A: Report from the Apache AGE Project [Jeff Jirsa] ## Description: The mission of Apache AGE is the creation and maintenance of software related to a multi-model database that enables graph and relational models built on PostgreSQL ## Project Status: Current project status: Slow but steady activity, including active releases this quarter. Issues for the board: No help needed at this time ## Membership Data: Apache AGE was founded 2022-05-17 (4 years 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: - No new PMC members. Last addition was Jeff Jirsa on 2025-05-11. - No new committers. Last addition was Jeff Jirsa on 2025-05-12. ## Project Activity: This quarter saw important releases, with 1.7.0 releases for both Postgres 17 ( https://lists.apache.org/thread/ypj8mdl9wxfkwrsy01mp6spcgtt5o5jj ) and Postgres 18 ( https://lists.apache.org/thread/593b5y8q9w0k90hv4qn4zq0wffwcm7l9 ) ## Community Health: As the project has increased its velocity, signs of new organic contributions are also appearing. There is a private@ thread discussing two potential committers, which would be the first in quite some time. Total contribution is still lower than past years, but higher than 2025. ----------------------------------------- Attachment B: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: The mission of Apache Airflow is the creation and maintenance of software related to workflow automation and scheduling that can be used to author and manage data pipelines ## Project Status: Current project status: Ongoing, very high activity Issues for the board: No issues for the board The PMC congratulates the new board selected in March elections and looks forward to cooperation in the coming year. We continue maturing Airflow 3 major release - with the goal of releasing Airflow 3.2 which is the first version from the Airflow 3 series that will have not only new features but also pretty much full parity with Airflow 2 - making it much more viable for pretty much all users to migrate to Airflow 3. We are undergoing a stabilization phase and recently 3.1.* releases focus on fixing some of the - still annoying in some cases - issues for our users - such as making sure that enterprise logging features work, that some edge cases in distributed deployments, stability of the UI, handling initial flood of (low severity) security issues resulting from imperfectness our new API structure and us learning the secure patterns. We also released security-focused 2.11.1 (and upcoming 2.11.2) releases, solving some of the long-standing issues with 3rd-party dependencies with known security vulnerabilities, Airflow 2.11.2 will likely be the last release in Airflow 2 series as Airflow 2 reaches End-Of-Live in April and will no longer receive any updates - including security updates. We will encourage all users to migrate to Airflow 3. We actively participated in ATR testing, being one of the first (and biggest) users of ATR, we helped to crank out a number of issues, and we are looking forward to switching to ATR releases when it goes out of beta and improve and further automate our release process. Airflow 3.2 will be the first release where long awaited “task isolation” will materialize as a security feature and make enterprise deployments easier and more modular - with experimental multi-team features added. This is not yet complete security isolation but we are - step-by-step - departing from the original “all Dag Authors can do everything” approach that allows enterprise users to have more hardened, easier to secure deployments of Airflow. We are also heavily investing in AI / LLM case integration. According to Airflow Survey 2025, Airflow is already heavily used to handle AI and LLM related data pipelines, but we are continuing adding new capabilities such as Human-In-The-Loop capability and recently AIP-99 Common Data Access Pattern with AI [1], where Airflow gets AI/LLM native capabilities that will allow to add LLM / AI features directly to 1000s of integrations (Hooks) airflow already has and allow them to be natively used with LLM assistance - driven by Dag Authors using those integrations. We are also - in connection with that - revising the way how we manage the lifecycle of the integrations (providers) - more of that in the Community section. The Yearly Survey for 2025 was a resounding success. We had more than 6000 users responding to the survey and providing us valuable insights on how Airflow is being used, what our users need, and how things are changing in the AI world for us. We believe that this is one of the biggest ASF project surveys conducted regularly. PMC wants to thank Astronomer for running the survey, processing its results and also making rounds all over the world meetups (From US to Australia) presenting the results of the survey at Airflow Meetups with the “State of Apache Airflow(R)” series of events and releasing “State of Apache Airflow(R) 2026” report - with involvement, participation and overlook of the PMC. We also improved our Survey, Monthly Meetings processes and documented it meticulously, in order to avoid misinterpretation of Astronomer involvement in the whole process - following concerns raised by VP branding last year. ## Membership Data: Apache Airflow was founded 2018-12-19 (7 years ago) There are currently 77 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Bugra Ozturk was added to the PMC on 2026-01-14 - Rahul Vats was added to the PMC on 2026-01-14 - Shahar Epstein was added to the PMC on 2025-12-23 - Yeonguk Choo was added as committer on 2025-12-29 - David Blain was added as committer on 2025-12-29 - Dheeraj Turaga was added as committer on 2026-01-07 ## Project Activity: Recent releases: * Provider packages 2026-03-03 was released on 2026-03-04. * Provider packages 2026-02-26 was released on 2026-03-02. * Apache Airflow Ctl 0.1.2 was released on 2026-02-25. * Apache Airflow 2.11.1 was released on 2026-02-20. * Apache Airflow Providers Fab 1.5.4 was released on 2026-02-20. * Apache Airflow Helm Chart 1.19.0 was released on 2026-02-17. * Provider packages 2026-02-14 was released on 2026-02-14. * Apache Airflow 3.1.7 was released on 2026-02-04. * Task SDK 1.1.7 was released on 2026-02-04. * Provider packages 2026-01-27 was released on 2026-02-02. * Apache Airflow Python Client 3.1.6 was released on 2026-01-22. * Provider packages 2026-01-17 was released on 2026-01-21. * Apache Airflow 3.1.6 was released on 2026-01-13. * Apache Airflow Ctl 0.1.1 was released on 2026-01-13. * Provider packages 2026-01-13 was released on 2026-01-13. * Task SDK 1.1.6 was released on 2026-01-13. * Provider packages 2025-12-30 was released on 2026-01-02. * Provider packages 2025-12-09 was released on 2025-12-13. * Apache Airflow 3.1.5 was released on 2025-12-12. * Task SDK 1.1.5 was released on 2025-12-12. There were a few “rc2” accelerated votes resulting from releasing rc2+ candidates after bugs were found in previous candidates, following a regular process agreed by the PMC. The project is highly active - and even more active than usual due to Gen-AI slop (see community health) ## Community Health: Besides the danger of burnout resulting from AI slop (described below)- the community is very healthy - we keep on having great collaboration and cooperation between individual community members and stakeholders in Airflow, who continue investing in Airflow heavily. We invited quite a number of new contributors and PMC members - with a healthy ratio of people from the biggest and most involved stakeholder - Astronomer, and people from the general community. We also introduced a huge change (and we are going to build on that) in the way we treat providers (Airflow integrations) and how we engage various stakeholders. We discussed, proposed and implemented a new governance framework for Airflow integration where we figured out a way to engage our stakeholders in the governance process, while keeping the process following the letter and spirit of the Apache Way. That took a long time - first discussions happened more than a year ago and some initial ideas were consulted with a number of ASF members at Community Over Code in Minneapolis. That resulted in the AIP-95 Provider lifecycle update [2]. We are adding first providers following this framework and we already have interesting discussions which result in stakeholder explicit engagement. We are gearing up for Airflow Summit 2026 (Austin, TX) - CFP is about to close in a week - and we are also working on “Airflow Contributor Days” Track at Community Over Code. While Airflow Summit is more focused on users, the “Airflow Contributor Days” is targeted towards contributors and contributing users - mostly from Europe. We hear and understand that the geopolitical situation heavily impacts the decisions of people to take part in the events in the US. We also wanted to give the people who would not want or be able to attend Airflow Summit, to meet other community members in Glasgow. This is all done with a close cooperation between Airflow Summit, Airflow Contributor Days and Community Over Code - bridging some of the past issues with Sponsors and Attendee overlap, attempting to manage it in a fully transparent way that is beneficial to everyone involved. That seems to work very well. Two of Airflow PMC members(Jens Scheffler and Amogh Desai) have just been voted in to be ASF members and they accepted - bringing the total number of ASF members to 8. We also have a lot of new community activity in Korea - where we have a strong community organized by a new committer Yeonguk Choo - the community there organises local workshops and meetups. Similarly new community meetups in Stuttgart organized by Jens Scheffler - PMC member, all that on top of 20+ other regular meetups we have all around the globe. Like almost all OSS projects - we are suffering from AI slop in our issues and pull requests. But in the case of Airflow it is magnified by the fact that Airflow is a very popular project with over 3.600 contributors and that somehow people seem to consider being “airflow contributor” even if all that you did was getting assigned to an issue is some kind of “badge of pride or career”. We’ve seen - anecdotally - people boasting they were contributors to Airflow right after being assigned an issue and not doing any contributions. The numbers of PRs and Issues created in the Airflow project rapidly increased last quarter, similarly the number of security issues raised to Airflow with a lot of those PRs and issues being low-quality, AI-generated and not reviewed contributions, which distract maintainers and makes them head towards the burnout zone. We are literally drowning in the sea of contributions and barely getting some air left. We have started a few initiatives to change the way we work to adapt to the new reality, while keeping the openness, transparency, inclusivity and collaboration spirit of OSS and Apache Way: * We are employing Agentic AI to help us to deal with it. We applied a number of remediations already. Better AGENTS and SKILL instructions so that people using agents can generate better PRs following our expectations. * We are looking towards automating the agentic code review process for those who use agents, by providing copilot instructions for reviews. We gave up on assigning external collaborators to “good first issues” tasks (still encouraging them to contribute) - because we have a lot of tasks assigned and never completed. * We are experimenting with tooling that will allow us to automatically triage incoming PRs (including AI / LLM assessment ) - but we do it in the way where Human-In-The-Loop and maintainer <-> contributor relationships are kept, rather than fully replacing maintainers with automation. More ideas are being discussed and we gradually introduce them and experiment with them, also we carefully follow similar industry discussions (many of them happening right now) - listening and participating in GitHub attempts to improve the situation and we apply the learning and changes from GitHub to our workflows. We will report next quarter about the results, also we are going to talk about it at Community Over Code in Glasgow and share our experiences. [1] AIP-99 Common Data Access Patterns with AI https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618285 [2] AIP-95 Provider lifecycle update proposal: https://cwiki.ap ache.org/confluence/display/AIRFLOW/AIP-95+Provider+lifecycle+update+proposal ----------------------------------------- Attachment C: Report from the Apache Allura Project [Dave 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" ## Project Status: Current project status: Ongoing (moderate activity) Issues for the board: none ## Membership Data: Apache Allura was founded 2014-03-18 (12 years ago) There are currently 19 committers and 19 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Daniel Castillo was added to the PMC on 2026-02-23 - Daniel Castillo was added as committer on 2026-02-24 ## Project Activity: - new background task options - improve markdown list parsing - improve markdown performance in some cases - redact some sensitive info in server-side logs - python dependency upgrades ## Community Health: - added a long-time contributor as committer and PMC member - development is slow, mostly in maintenance mode, but "active maintenance" keeping up with new versions of things and improving security posture ----------------------------------------- Attachment D: Report from the Apache Atlas Project [Madhanmohan 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 ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: none ## Membership Data: Apache Atlas was founded 2017-06-20 (9 years ago) There are currently 50 committers and 33 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 Pinal Shah on 2025-01-29. - No new committers. Last addition was Disha Talreja on 2025-07-11. ## Project Activity: - upgrade dependent component versions: JanusGraph 1.1.0, Hadoop 3.4.2, HBase 2.6.4, dashboard - Planning to release Apache Atlas 2.5.0 by end of this month - improve test coverage in multiple modules - UI fixes in search, business metadata, entity details pages - replace use of commons-lang with commons-lang3 - fix in reindexing feature ## Community Health: - 74 JIRA tickets opened and 53 closed in the past quarter. - dev@atlas.apache.org had a 32% increase in traffic in the past quarter (671 emails compared to 508) - 40 commits in the past quarter (41 in the last report) - 8 code contributors in the past quarter (11 in the last report) ## Recent releases: - Apache Atlas 2.4.0 was released on 2025-01-04. - Apache Atlas 2.3.0 was released on 2022-12-06. - Apache Atlas 2.2.0 was released on 2021-08-17. - Apache Atlas 2.1.0 was released on 2020-07-15. ----------------------------------------- Attachment E: Report from the Apache Axis Project [Robert Lazarski] ## Description: The Apache Axis Project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components. ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: none ## Membership Data: Apache Axis was founded 2009-12-15 (16 years ago) There are currently 65 committers and 64 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 Christian Ortlepp on 2025-01-27. - No new committers. Last addition was Andreas Lehmkühler on 2025-01-29. ## Project Activity: Recent releases: - Axis 2/Java 2.0.0 was released on March 10, 2025. - Axis 2/Rampart 1.8.0 was released on Dec 10, 2024. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Community Health: Axis2/C and Axis2/Java both had very productive development in the last 90 days, and release votes for each project are about to start. The last Axis2/C release was in 2009 and the project had been long under maintained in general but that changed this last year with HTTP/2 and native JSON support added the previous quarter, and a whopping 201 Jira issues closed this past quarter that wiped out the backlog. Modern AI tools via Claude commits and then a Google Gemini code review helped quite a bit, with the dev model being lots of markdown files explaining what it is doing. This Axis2/C momentum is partly due to Android support being added that turns phone apps into JSON based web services via an embedded Apache httpd server for remote Curl based transport control i.e. stop and start, with examples for a camera app shown in https://github.com/apache/axis-axis2-c-core/blob/master/docs/HTTP2_ANDROID.md . Axis2/C gained Google OSS Fuzz support to prevent polymporphic malware this past quarter and a Github pull request has been made at https://github.com/google/oss-fuzz/pull/14879 . Axis2/Java added more tests this past quarter to compliment the OSS-Fuzz contribution from 2023. See https://github.com/apache/axis-axis2-c-core/blob/master/docs/OSS-FUZZ.md , Axis2/Java continues to add contempory JSON based features to attract new projects and committers, and this past quarter OpenAPI aka Swagger support was added and perhaps unique as Axis2/Java may be the first project that includes http/2 protcol usage for OpenAPI. Axis2/Java does have some areas of concern about the legacy deps for SOAP in the disintegrating Apache Web Services project that is in a long running roll call still in progress, Apache Web Services has about 5 deps Axis2 needs - some with very old specs that never really took off. WS-AXIOM historically has been an essential dep for SOAP however future releases are unclear, see https://issues.apache.org/jira/browse/AXIOM-525. Some refactoring to depend on these libs less may be essential, as the software world continues to move rapidly from SOAP and XML into JSON. The Axis2/Java sub project Rampart that adds optional WS-Security* had no commits this past quarter though there was some Java 25 interest in the project as shown this past quarter in the Jira issue at https://issues.apache.org/jira/browse/RAMPART-454. We expect a Rampart release this next quarter, after the Axis2/Java release. ----------------------------------------- Attachment F: Report from the Apache Beam Project [Kenneth Knowles] ----------------------------------------- Attachment G: Report from the Apache Bigtop Project [Masatake Iwasaki] ## 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. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Bigtop was founded 2012-09-19 (13 years ago) There are currently 46 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: * No new PMC members. Last addition was Zhiguo Wu on 2024-08-19. * No new committers. Last addition was Liqiang Fu on 2025-05-13. ## Project Activity: Recent releases: bigtop-manager-1.1.0 was released on 2025-12-04. 3.5.0 was released on 2025-09-07. 3.4.0 was released on 2025-05-30. We are preparing for the next 3.6.0 release starting from upgrading Hadoop to 3.4[1]. We need some more effort for aligning the versions of product in the stack since some downstream products dropped Java 8 support while Hadoop 3.4 requires Java 8 for release build. [1] https://issues.apache.org/jira/browse/BIGTOP-4520 ## Community Health: We had low activity in the past quarter: * dev@bigtop.apache.org had a 45% decrease in traffic in the past quarter (44 emails compared to 80) * issues@bigtop.apache.org had a 50% decrease in traffic in the past quarter (22 emails compared to 44) * 9 JIRA tickets opened and 3 closed in the past quarter. While it would be nice to add more active contributors and committers, we can still catch up with the products in the stack since the ecosystem of Apache Hadoop on which the Apache Bigtop is based on is matured and follows a longer release cadence. ----------------------------------------- Attachment H: Report from the Apache BookKeeper Project [Enrico Olivelli] ## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache BookKeeper was founded 2014-11-19 (11 years ago) There are currently 32 committers and 20 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Shiji Lu on 2025-05-14. - No new committers. Last addition was Zhangjian He on 2025-01-27. ## Project Activity: There is not much activity on code (bug fixes, new features) at the moment, almost only housekeeping: upgrading dependencies, modernizing CI, the website. Recent releases: 4.16.7 was released on 2025-07-07. 4.17.2 was released on 2025-07-07. 4.16.6 was released on 2024-06-26. ## Community Health: Almost all the conversations happen on GitHub issues and there is something on our Apache BookKeeper slack. IT would be better to use the mailing lists, but the only conversations happening on slack are about people pinging to ask for review for PRs, so not really technical discussions or asks for help from users. We have sporadic contributions from people who are not committers, but not enough to invite such contributors as committers. ----------------------------------------- Attachment I: Report from the Apache BuildStream Project [Abderrahim Kitouni] ----------------------------------------- Attachment J: Report from the Apache BVal Project [Matt Benson] ----------------------------------------- Attachment K: 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. ## Project Status: Current project status: Ongoing with high activity Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (17 years ago) There are currently 95 committers and 48 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 Federico Mariani on 2025-07-22. - Luigi De Masi was added as committer on 2026-02-27 ## Project Activity: Apache Camel: - We released Camel 4.10.9 - We released Camel 4.14.1 - We released Camel 4.14.3 - We released Camel 4.14.4 - We released Camel 4.14.5 - We released Camel 4.17.0 - We released Camel 4.18.0 - 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. - 4.18.x is our last LTS release train together with 4.14.x. 4.10.9 was the last patch release for 4.10.x LTS. - The situation is really healthy and the community is increasing presence and engagement. We are introducing many new features and components. We are also aggressively deprecating old components and modernize the code for the next LTS. We are removing support for JDK 17 and focus only on JDK 21 and 25. Apache Camel K: - We released Camel K 2.9.0 - We released Camel K 2.9.1 - We focused heavily on operator stability and reducing the memory footprint of the operator pod. - Camel K is in good shape and the community is expading with more contributors and feedback. The situation is healthy. Apache Camel Kamelets: - We released Camel Kamelets 4.10.8 - We released Camel Kamelets 4.14.3 - We released Camel Kamelets 4.14.4 - We released Camel Kamelets 4.14.5 - We released Camel Kamelets 4.17.0 - We released Camel Kamelets 4.18.0 - The Kamelet catalog keep growing - Documentation has been improved even more. - The 4.14.x release train is matching the LTS release from Camel core and we are supporting also 4.18.x LTS now. Apache Camel Quarkus: - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 3.20.4 - We released Camel-quarkus 3.27.2 - We released Camel-quarkus 3.27.3 - We released Camel-quarkus 3.31.0 - We released Camel-quarkus 3.32.0 - We are increasing the number of Camel Quarkus Extension to match the core components. We are supporting 4.14.x LTS and 4.18.x LTS. - The community is active and we are seeing increased interest. Apache Camel-Karavan: - Camel-Karavan is still growing. - We released version 4.14.2, supporting the latest LTS release. - Work is on-going to support 4.18.x LTS. Camel-Kafka-Connector: - Work for supporting 4.18.x LTS has been done and we are going to release soon. - The community is active and we receive a lot of feedback and requests. We are improving the documentation and we're trying to keep the same cadence as core. - The project is slowing down a bit for the lack of developers working on it, but we are aligning. Apache Camel-Karaf: - Camel-karaf 4.10.7 has been released. - It's a patch version supporting LTS 4.10.x - The plan is to support 4.14.x LTS in the next period. - A patch release for 4.8.x has been released too. 4.8.9. Apache Camel-Upgrade-Recipes: - Camel-Upgrade-Recipes 4.17.0 has been released - Camel-Upgrade-Recipes 4.18.0 has been released - This version supports upgrades up to 4.18.0 - The plan is to keep supporting 4.14.x LTS and 4.18.x LTS ## Community Health: dev and issues mailing lists increased in usage in this quarter, this is mainly because we wanted to discuss about some deprecation and removals and drop of JDK 17.We are mainly consolidating our work on Camel, by introducing new components and new features but also by working on backlog. Now that we released 4.18.x, we are introducing new features and we are refactoring the codebase a bit, so we expect more discussions on dev and issues. There was a decrease on the users mailing list, mainly because we are using Zulip for discussing and sometimes contributors use Zulip as first interaction point instead of the ML. In terms of Github engagement we are doing really well and we see new contributors and reporters. I think the community is really growing. ----------------------------------------- Attachment L: Report from the Apache Cayenne Project [Michael Gentry] ----------------------------------------- Attachment M: Report from the Apache Celeborn Project [Keyong Zhou] ## Description: The mission of Apache Celeborn is the creation and maintenance of software related to an intermediate data service for big data computing engines to boost performance, stability, and flexibility ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Celeborn was founded 2024-03-20 (2 years ago) There are currently 27 committers and 16 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 Fei Wang on 2024-12-31. - Erik Fang was added as committer on 2025-12-03. ## Project Activity: - Release 0.6.2 is released on 8 December. - CIP-13 Support auto scaling is under development. - CIP-14 Support cpp client for shuffle write is finished. - CIP-19 Support app priority is under development. - CIP-20 Dynamically optimize shuffle write parallelism is under development. - CIP-21 Support Flink JM failover is under discussion. - Support Ray is under discussion. Meetups and Conferences: - 1 talk was given in a local meetup in ShangHai. Recent releases: - Release 0.6.2 is released on 8 December. - Release 1.0.0 is under initial discussion. ## Community Health: Overall community health is good. In the past quarter, the dev mail list mail number had a 7% increase in the past quarter. The issues mail list had a 30% decrease to 610, the PMC considered it as normal because the absolute number is relatively high. We have been performing extensive outreach for our users, and encouraging them to contribute back to the project. Also, we are active in making a voice in various conferences to attract more users. ----------------------------------------- Attachment N: Report from the Apache CloudStack Project [Nicolás Vázquez] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage, and networking devices. ## Project Status: Current project status: Ongoing, with high activity Issues for the board: None ## Membership Data: Apache CloudStack was founded 2013-03-19 (13 years ago) There are currently 147 committers and 63 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - Fabricio Duarte Junior was added to the PMC on 2026-02-26 - Kiran Chavala was added to the PMC on 2026-02-26 - Abhisar Sinha was added as committer on 2026-03-02 - Henrique Sato was added as committer on 2026-03-02 - Manoj Kumar was added as committer on 2026-03-07 - Rositsa Kyuchukova was added as committer on 2026-03-11 ## Project Activity: Software development/management activity: - The current version of Apache CloudStack is 4.22.0.0. - No versions were released since the past quarter. - The community is planning to release Apache CloudStack version 4.20.3.0 in March 2026 - The community is planning to release Apache CloudStack version 4.22.1.0 in April 2026. - The community is planning to release Apache CloudStack version 4.23.0.0 by May 2026. - We are working on some security patches and expect to release them soon. - The latest CloudStack Kubernetes Provider version 1.2.0 was released on December 29, 2025. - The latest CloudStack Terraform provider version 0.6.0 was released on October 28, 2025. - The CloudStack PMC Chair rotation was voted on in February. A resolution to the Apache Board was submitted to confirm Wido den Hollander to the role. Meetups and Conferences: - The Apache CloudStack project will be exhibiting at CloudFest, from March 23-26th, 2026 in Rust, Germany: https://cloudstack.apache.org/blog/cloudfest-2026 - The CloudStack European User Group 2026 is scheduled for May 21, 2026 in Hague, Netherlands: https://cloudstack.apache.org/blog/cseug-2026 - The CloudStack community will attend the Community Over Code EU 2026 on October 11-14 in Glasgow, Scotland; with a confirmed track for CloudStack: https://cloudstack.apache.org/blog/coceu26 - The CloudStack Collaboration Conference 2026 is scheduled for November 18-20 in Edinburgh, Scotland: https://www.cloudstackcollab.org/. ## Community Health: - According to the reporter tool, the Community Health Score (Chi) is 10.00 (Super Healthy). Mailing lists statistics: - dev@cloudstack.apache.org had a 59% decrease in traffic in the past quarter (399 emails compared to 969) - issues@cloudstack.apache.org had a 58% decrease in traffic in the past quarter (41 emails compared to 96) - marketing@cloudstack.apache.org had a 35% decrease in traffic in the past quarter (13 emails compared to 20) - users@cloudstack.apache.org had a 14% decrease in traffic in the past quarter (1439 emails compared to 1658) Recent Releases: - 4.22.0.0 was released on 2025-11-11. - 4.20.2.0 was released on 2025-10-27. - 4.21.0.0 was released on 2025-08-28. ----------------------------------------- Attachment O: 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 ## Project Status: Current project status: Ongoing. Issues for the board: None. ## Membership Data: Apache Commons was founded 2007-06-19 (19 years ago) There are currently 150 committers and 44 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 Arnout Engelen on 2024-12-22. - No new committers. Last addition was Arnout Engelen on 2024-12-23. ## Project Activity: This reporting period saw the release of the following Apache Commons components: - PARENT-97 was released on 2026-02-26. - FILEUPLOAD-2.0.0-M5 was released on 2026-02-17. - JEXL-3.6.2 was released on 2026-02-09. - BUILD-PLUGIN-1.16.1 was released on 2026-01-31. - RELEASE-PLUGIN-1.9.2 was released on 2026-01-31. - CODEC-1.21.0 was released on 2026-01-29. - BCEL-6.12.0 was released on 2026-01-22. - PARENT-96 was released on 2026-01-21. - PARENT-95 was released on 2026-01-11. - PARENT-94 was released on 2026-01-02. - POOL-2.13.1 was released on 2026-01-02. - DAEMON-1.5.1 was released on 2025-12-16. - DBCP-2.14.0 was released on 2025-12-16. - JEXL-3.6.1 was released on 2025-12-14. - POOL-2.13.0 was released on 2025-12-09. - TEXT-1.15.0 was released on 2025-12-07. A Commons Logging release candidate is in flight. ## Community Health: There is a steady stream of pull requests on GitHub, fewer than a handful a day. Overall mailing list activity is down by about a third, but JIRA and GitHub is up. There have been 66 JIRA tickets opened and 79 closed in the past quarter. ----------------------------------------- Attachment P: Report from the Apache Cordova Project [Bryan Ellis] ## Status report for the Apache Cordova project - March 2026 ## Description A platform for building native mobile applications using HTML, CSS and JavaScript. ## Project Status **Current project status:** Our current work focuses on staying up to date by making improvements to our release process, plugins, and core platforms. Our status dashboard at https://apache.github.io/cordova-status/ remains mostly all green. **Issues for the board:** There are no issues requiring board attention at this time. ## Membership Data There are currently 100 committers and 97 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 Manuel Beck on 2025-04-04. - No new committers. Last addition was Manuel Beck on 2025-04-04. ## Project Activity The following releases to our project this quarter focused on the Cordova-Android platform, CLI, and internal libraries. **Releases:** - cordova-android@15.0.0 was released on 2026-03-06. - cordova-eslint@6.0.1 was released on 2026-02-18. - cordova-cli@13.0.0 was released on 2025-11-25. **Other:** Some committers continue to bring Cordova's perspective and use cases of WebViews to the W3C community groups. The Open Source Initiative enabled open source maintainers to contribute feedback on ETSI standards that are currently in development for the Cyber Resilience Act. We're happy to provide the editors with information on how embedded browsers are used. The CRA will likely introduce new standards and new security requirements and we would like to make sure use-case like Cordova are covered. Example: https://labs.etsi.org/rep/stan4cra/en-304-617/-/issues/5 ## Community Health Overall, the community health is strong. The ASF Project Statistics gives the project a Community Health Score (Chi): 6.33 (Healthy) This quarter, we primarily focused on improving our plugins and release process. Additionally, we finalized and successfully released the next major version of Cordova-Android 15 and Cordova-CLI 13. As part of our release process improvements, we have been rewriting our release guidelines and have started implementing release workflows throughout our project to make use of the upcoming Apache Trusted Releases (ATR) tool. As we rework our release process and guidelines, this allows us to review and improve areas where we may be lacking and make the necessary corrections to realign them. Additionally, we would like to note that the last two packages were successfully released using the new ATR tool. We have been making various improvements to our project's website, including archiving documentation for older versions so that only the current live documentation is hosted, adding a download page, making use of deploying to staging for reviewing, and resolving several outstanding minor visual bugs. We also continue to see valuable contributions from a group of dedicated individuals who actively test, report issues, and submit PRs to address their findings for future releases. A large portion of this quarter's activity has been focused on our plugins, particularly In-App-Browser and Camera. Overall, the project remains stable and continues to see strong activity. GitHub discussions is how our community supports each other and is live at https://github.com/apache/cordova/discussions. All discussions are forwarded to the 'issues' list. ## Mailing List Activity - dev@cordova.apache.org had a 8% increase in traffic in the past quarter (62 emails compared to 57) - issues@cordova.apache.org had a 56% increase in traffic in the past quarter (1172 emails compared to 751) ----------------------------------------- Attachment Q: Report from the Apache cTAKES Project [Pei J 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 ## Project Status: Current project status: Ongoing with moderate/low activity. Issues for the board: There are no issues requiring board attention at this time. There was a roll call suggested by board. The results of the roll call were: https://lists.apache.org/thread/2onk61q0lc84cygpx46354omd3o9qm87 +1: 5 0: 5 -1: 3 ## Membership Data: Apache cTAKES was founded 2013-03-19 (13 years ago) There are currently 40 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - New PMC addition this quarter was Dennis Johns on 2026-03-10. - No new committers. Last addition was Dennis Johns on 2023-01-06. ## Project Activity: - Committee continues to work on the future release (7.x.x) - 6.0.0 was released on Sept 16 2024 - 5.1.0 was released on May 10 2024 - 4.0.0.1 was released on Jan 20 2021 - 4.0.0 was released on Apr 27 2017 ## Community Health: Mailing list traffic was similar to last quarter. Dennis was added as a new PMC member. ----------------------------------------- Attachment R: 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 ## Project Status: Current project status: ongoing Issues for the board: None ## Membership Data: Apache Curator was founded 2013-09-18 (12 years 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. Last addition was Kezhu Wang on 2023-03-25. - No new committers. Last addition was Kezhu Wang on 2023-03-24. ## Project Activity: There was not much activity in the past quarters Recent releases: 5.9.0 was released on 2025-07-23. 5.8.0 was released on 2025-03-06. 5.7.1 was released on 2024-10-13. ## Community Health: Actually community was not active in the past quarter, we have committed no patches and there were no conversations on the mailing list. For NOW I don't see this as a problem, as usual Curator is widely used, but it is generally stable. It is also strictly linked to the activity (new releases) of Apache ZooKeeper. Doing this report to the board is actually useful, because it is a good reason for the PMC to have conversations about how to revive the community. ----------------------------------------- Attachment S: Report from the Apache Daffodil Project [Mike Beckerle] ## Description: The mission of Apache Daffodil is the creation and maintenance of software related to an implementation of the Data Format Description Language (DFDL) used to convert between fixed format data and more readily processed forms such as XML or JSON ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Daffodil was founded 2021-02-16 (5 years ago) There are currently 21 committers and 20 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Ryan Cover was added as committer on 2026-02-01 - Jeremy Yao was added as committer on 2026-01-07 - Ryan Cover was added to the PMC on 2026-03-05 - Jeremy Yao was added to the PMC on 2026-03-05 ## Project Activity: - Daffodil Extension for Visual Studio Code 1.5.0 was released on 2026-01-14 - Daffodil 4.1.0 was released on 2026-02-05 - Daffodil SBT plugin 1.6.0 was released on 2026-02-05 ## Community Health: Developer email and commit activity are still good. Some decrease in activity due to retirement (from his employer, not from the project) of Mike Beckerle, who remains our PMC Chair but is less active doing actual development work now. The cybersecurity community, which is the major user community for Daffodil, is notoriously silent about usage, so despite known new users in Canada, there is very little activity on the users mailing list. In early march we added access for a new contributor. ----------------------------------------- Attachment T: Report from the Apache DataFusion Project [Andrew Lamb] ## Description: The mission of Apache DataFusion is the creation and maintenance of software related to an extensible query engine ## Project Status: Current project status: New + Ongoing (high activity) Issues for the board: None ## Membership Data: Apache DataFusion was founded 2024-04-16 (2 years ago) There are currently 56 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - Adrian Garcia Badaracco was added to the PMC on 2026-02-01 - Marko Milenković was added to the PMC on 2025-12-18 - Martin Tzvetanov Grigorov was added as committer on 2026-02-14 - Nuno Faria was added as committer on 2026-01-26 ## Project Activity: Note that almost all communication for DataFusion and its subprojects happens on github and so our dev mailing list traffic is fairly light. ### DataFusion core https://github.com/apache/datafusion - 52.2.0 was released on 2026-03-01. - 52.1.0 was released on 2026-01-23. - 52.0.0 was released on 2026-01-12. Our releases continue to result from over 100 distinct contributors, and we still average around [7.8 commits per day] to the main repo. [7.8 commits per day]: git rev-list --count apache/main --since='2026-02-09 00:00:00' --until='2026-03-09 23:59:59' The community continues to write blogs highlighting our work https://datafusion.apache.org/blog/2026/02/02/datafusion_case https://datafusion.apache.org/blog/2026/01/30/datafusion-comet-0.13.0 https://datafusion.apache.org/blog/2026/01/12/datafusion-52.0.0 https://datafusion.apache.org/blog/2026/01/12/extending-sql https://datafusion.apache.org/blog/2025/12/15/avoid-consecutive-repartitions We continue to hold small scale in person meetups in various locations, which have been successful in bringing together contributors. You can see a list here: https://datafusion.apache.org/user-guide/ concepts-readings-events.html#community-events The overall number of PRs in need of review has been growing, likely due to increasing use of AI coding tools and the overall growth of the community. We will likely discuss how to make it easier to understand the overall project in the next quarter. The community [guidelines] for AI assisted contributions seem to be working well and we haven’t seen as many “AI Dumps” [guidelines]: https://datafusion.apache.org/contributor-guide/ index.html#ai-assisted-contributions ### Sub project: DataFusion Python https://github.com/apache/datafusion-python DATAFUSION-PYTHON-52.0.0 was released on 2026-02-23. DATAFUSION-PYTHON-51.0.0 was released on 2026-01-09. ### Sub project: DataFusion Comet COMET-0.13.0 was released on 2026-01-29. https://github.com/apache/datafusion-comet You can read about the recent happenings in Comet in the blogs: https://datafusion.apache.org/blog/2026/01/30/datafusion-comet-0.13.0 ### Sub project: DataFusion Ballista https://github.com/apache/datafusion-ballista - BALLISTA-52.0.0 was released on 2026-03-07. - BALLISTA-51.0.0 was released on 2026-01-19. There has been an increase of number contributions to ballista, and PR reviews, which is very positive. I hope this trend is going to persist in the future. ### Sub project: sqlparser-rs - SQLPARSER-0.61.0 was released on 2026-02-10. https://github.com/apache/datafusion-sqlparser-rs Ifeanyi Ubah (iffyio) continues to review most PRs in this repo. ## Community Health: While we as always struggle with code review capacity, we have many active committers, and the community in general helps each other out with reviews. We continue to actively grow our committer and PMC ranks. We continue to merge multiple PRs a day from multiple committers and have contributions from a wide variety of individuals with a wide variety of employers, organizations, and backgrounds. ----------------------------------------- Attachment U: Report from the Apache DevLake Project [Hezheng Yin] DevLake — Board Report (Month 4-8 as Top-Level Project) Reporting period: Oct 2025 - Feb 2026 Submitted by: Henry (Hezheng) Yin (PMC Chair, Apache DevLake) - Project description Apache DevLake is an open-source DevData platform that collects, transforms, and visualizes engineering and DevOps data from sources like GitHub, Jenkins, and Jira to help teams understand and improve their software delivery performance through metrics and dashboards. - Project status Status: Ongoing / Growth phase The project continues to mature as a Top-Level Project. We have released several beta versions of v1.0.3, focusing on performance, AI-metrics, and GitHub Copilot integration. - Community and project activity No new committer in this period Significant engineering activity has been observed in: - AI Integration: Added GitHub Copilot Connection and associated dashboards (#8728, #8674). - Performance: Optimized change lead time calculation using batch queries (#8726, #8714). - DORA & Metrics: New AI Adoption metrics (#8713) and improved deployment tracking. - Releases v1.0.3-beta9 — Released 2026-01-15 v1.0.3-beta8 — Released 2025-11-07 v1.0.3-beta7 — Released 2025-10-20 - Issues for the Board No critical Board-level issues at this time. - Community health Active committers this period: ~10 (Estimated). Mailing list traffic: Moderate. GitHub Activity: High engagement on AI features and performance improvements. - Roadmap / upcoming work AI & Copilot — Finalizing GitHub Copilot metrics and AI adoption tracking. Performance — Continuing optimizations for large-scale data calculations (change lead time). Integrations — Improving GitHub App support and token management. Documentation — Onboarding improvements and documentation for new AI features. - Additional commentary We are seeing strong interest in AI-related metrics. Focus remains on stabilizing v1.0.3 for ga release. ----------------------------------------- Attachment V: Report from the Apache Doris Project [Mingyu Chen] ## Description: The mission of Apache Doris is the creation and maintenance of software related to a MPP-based interactive SQL data warehousing for reporting and analysis ## Project Status: Current project status: Ongoing Issues for the board: No ## Membership Data: Apache Doris was founded 2022-06-14 (4 years ago) There are currently 94 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 3:1. Community changes, past quarter: - No new PMC members. Last addition was Gavin Chou on 2025-09-11. - Shixin Zhang was added as committer on 2026-01-14 - Si Wu was added as committer on 2026-02-25 - Zhang Dong was added as committer on 2026-02-26 ## Project Activity: Over the past three months, the Apache Doris community has continued to move quickly with a series of incremental improvements and maintenance work across the 3.x and 4.x branches. Several minor releases were completed during this period, delivering a range of stability improvements, performance optimizations, and bug fixes. These releases focused primarily on improving reliability and operational experience for production users while continuing to refine recently introduced features. In addition to regular releases, the community has continued to expand Doris’s capabilities in areas such as lakehouse analytics, semi-structured data processing, and query performance optimization. Enhancements to external table support, improvements in query execution, and continued work on storage efficiency have been key themes during this period. Expanding lakehouse capabilities, enabling more seamless querying of open table formats such as Iceberg and Paimon. Enhancing support for semi-structured data and flexible schema workloads Continuing to improve query performance, scalability, and operational simplicity for large-scale analytical workloads The Apache Doris community remains highly active. As always, new contributors and users are welcome to join the discussions and help shape the future of the project. Action: We also have an TODO task to move the downloadable materials from the official website to storage locations maintained by the Apache Software Foundation, which is currently in progress. ## Community Health: Overall community health for Apache Doris remains strong. Over the past three months, the project has continued to see steady participation from both existing and new contributors across development, documentation, and community support. We have also continued outreach and collaboration with related projects in the data infrastructure ecosystem, which has helped attract new users and contributors. ----------------------------------------- Attachment W: Report from the Apache Druid Project [Abhishek Agarwal] Report date: 2026-03-08 ## Description Apache Druid is a high performance real-time analytics database. It is designed for workflows where low-latency query and ingest are the main requirements. It implements ingestion, storage, and querying subsystems. Users interface with Druid through built-in SQL and JSON APIs, as well as third-party applications. Druid has an extensive web of connections with other Apache projects: Calcite for SQL planning, Curator and ZooKeeper for coordination, Kafka, Hadoop and Iceberg as data sources, Avro, ORC, or Parquet as supported data input formats, and DataSketches for scalable approximate algorithms. Druid can also be used as a data source by Superset. ## Project Status Ongoing - with High activity ### Issues There are no issues requiring board attention at this time. ### Recent releases - 36.0.0, a major release, on 2026-02-09. - 35.0.1, a patch release, on 2025-12-15. ## Security issues No security issues pending resolution. ## Project Activity We had two major releases since the last report - 35.0.0 - 220 changes from 29 contributors - 36.0.0 - 189 changes from 44 contributors Druid typically does major releases 3–4 times a year. any users had complained of long periods without a release in past. But project is following sustained release activity now, with timely quarterly releases. ## Community Health Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,365 members, up 51 members since our last report. The growth in slack community is lower this time. We will need to keep monitoring it to see if its one-off or the slack channel growth is reaching saturation. Slack is our most active channel for user support and usage-oriented discussions. As before, development discussions happen more on GitHub, and sometimes on the dev mailing list. ### Development activity by the numbers Since the last report on 2025-11-03 - 274 commits from 35 contributors - 359 pull requests opened - 332 pull requests merged/closed There is slight decrease in number of pull requests since last report. The number of contributors have not changed though our top contributors continue to consistently contribute. ## Membership Data Apache Druid was founded 2019-12-17 (8 years ago) There are currently 75 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. In the last report, we idenfied the need of adding more committers and PMC members. To that effect, We have added 2 committers and 1 PMC member since last report. There are two open discussion threads for adding new committers/PMC members. ----------------------------------------- Attachment X: 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 ## Project Status: Current project status: Ongoing, with low activity Issues for the board: NA ## Membership Data: Apache ECharts was founded 2020-12-16 (5 years ago) There are currently 31 committers and 15 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 ShiZhao Pan on 2025-01-09. - No new committers. Last addition was Zisen Jin on 2025-11-01. ## Project Activity: At present, the functionality of the project is relatively complete. Most of the code modifications mainly focus on bug fixes. We are currently engaged in the release work of the next version, 6.1.0. Previously, due to the inclusion of some relatively complex new features in the plan, the release time is a bit later than expected. We hope that the release frequency in the future can be maintained at least one version every six months. ## Community Health: The community for our project is at a medium level of activity. There is an average number of pull requests and issue reports, with a fair amount of them being addressed in a timely manner. Overall, while the community is steadily contributing, there is still room for growth to increase the level of engagement and the speed at which projects are advanced. ----------------------------------------- Attachment Y: 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. ## Project Status: Current project status: Ongoing, with very low activity. Issues for the board: none. ## Membership Data: Apache Felix was founded 2007-03-28 (19 years ago) There are currently 68 committers and 25 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 Paul Rütter on 2025-06-16. - No new committers. Last addition was Paul Rütter on 2024-11-15. ## Project Activity: Existing implementations have been improved/enhanced based on community feedback. Released 3 components. Mostly bug fixes/minor improvements. ### Recent releases: - maven-bundle-plugin 6.0.2 was released on 2026-02-27. - org.apache.felix.http.jetty12-1.1.8 was released on 2026-02-27. - org.apache.felix.http.jetty12-1.1.6 was released on 2025-11-27. ## Community Health: - Overall the project is in ok health with very little ongoing activity. - The community activity remains on a low level and we continue to see little new development right now. - Questions on the user list are answered, development concerns are either discussed on the mailing list or directly in the JIRA issues. Traffic has been very low. - We had no issues voting on releases (but some wait time) and JIRA issues are generally addressed. - 2 PMC members did go emeritus. ----------------------------------------- Attachment Z: Report from the Apache Flex Project [Harbs] ----------------------------------------- Attachment AA: 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 ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Flink was founded 2014-12-17 (11 years ago) There are currently 125 committers and 58 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Ferenc Csaky was added to the PMC on 2026-02-10 - Gabor Somogyi was added to the PMC on 2026-02-10 - Ruan Hang was added to the PMC on 2026-01-12 - David Radley was added as committer on 2026-01-26 - Yuepeng Pan was added as committer on 2025-12-18 ## Project Activity: The project released Apache Flink 2.2.0 in early December 2025, the first release in the 2.2 series. Planning for Flink 2.3 began in January with David Anderson, Hao Li, and Yuepeng Pan volunteering as release managers. Feature freeze is set for March 31, 2026, with a final release targeted for end of April 2026. The Flink Kubernetes Operator 1.14.0 was released in February, adding support asd for Blue/Green deployments. The community is actively designing Phase 2 of Blue/Green deployments (FLIP-504) with record-level coordination for exactly-once semantics. Flink Agents, a new sub-project for AI agent workflows on Flink, shipped two releases: 0.1.1 (December) and 0.2.0 (February), showing rapid iteration on this emerging area. On the connector side, flink-connector-aws shipped both a v5.1.0 (for Flink 1.x) and v6.0.0 (for Flink 2.x). The v6.0.0 release required five release candidates due to issues with NOTICE files, Java compilation targets, and license headers. flink-connector-parent v2.0.0 was released, dropping JDK 8 support in alignment with Flink 2.x. flink-shaded 21.0 was also released. A new flink-connector-http v1.0.0 and flink-connector-kafka v5.0.0 (with Kafka client 4.x) are in preparation. The community accepted 11 FLIPs this quarter, with notable highlights including: FLIP-555 (native S3 filesystem eliminating the Hadoop dependency), FLIP-561 (major documentation restructuring using the Diataxis framework, which received strong community support with 13 votes), FLIP-564 and FLIP-566 (advancing the Process Table Function ecosystem), and FLIP-558 (improving changelog handling with ON CONFLICT semantics). Another 8 FLIPs are under active discussion, including Language Server Protocol support for Flink SQL and a test harness for Process Table Functions. The community discussed the future of the Stateful Functions (StateFun) sub-project, which has seen no commits since its 3.3.0 release in September 2023. Consensus leans toward sunsetting the project. A proposal to revive a monthly Flink community digest blog was well received. ## Community Health: The user@flink mailing list saw a 63% decline in the last 3 quarters. It seems that many emails don't get answered on the user@ list anymore. People are moving to other places like the Flink Slack Group, Stack Overflow, or just asking LLMs or coding agents directly. The dev@ list is at a 3% decline, which I consider within normal fluctuations of the numbers. One area of concern is connector ecosystem maintenance: the flink-connector-aws repository struggles to attract reviewers and release voters outside of the primary vendor contributor. The PMC discussed strategies for cultivating new committers for connector repos. Similarly, the Stateful Functions sub-project has become dormant and is a candidate for retirement. CI infrastructure experienced disruptions in February due to Docker version incompatibilities on Azure and GitHub runner images, but fixes were merged. CVE-related dependency updates were consolidated under a single tracking ticket (FLINK-39060) for better coordination. ----------------------------------------- Attachment AB: Report from the Apache Geronimo Project [Jean-Louis Monteiro] ----------------------------------------- Attachment AC: Report from the Apache Gluten Project [Weiting Chen] ## Description: The mission of Apache Gluten is the creation and maintenance of software related to software related to a pluggable middleware that enables native, vectorized execution engines to accelerate Apache SparkSQL workloads; ## Project Status: Current project status: Ongoing, stable (Incubating). [1] Issues for the board: None. ## Membership Data: Apache Gluten was founded 2026-02-18 (19 days ago) There are currently 44 committers and 28 PMC members in this project. [2] The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: v1.6.0 is currently under community review and vote[3]. Development activity during the quarter was steady, focused on incremental improvements, bug fixes, and stability. ## Community Health: Contributor activity is moderate and stable: - dev@gluten.apache.org had a 25% increase in traffic in the past quarter (160 emails compared to 128). - Dozens of PRs opened weekly in recent activity. - The issue tracker remains active, with approximately 790 open issues and over 2,700 issues closed overall. No conduct or governance issues were reported during this period. [1] https://projects.apache.org/project.html?gluten [2] https://projects.apache.org/projects.html?number [3] https://lists.apache.org/thread/wxzkfpy2b6oks85qq5dzsq3cxb3bm7b7 ----------------------------------------- Attachment AD: 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 ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Gobblin was founded 2021-01-19 (5 years ago) There are currently 23 committers and 12 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 Abhishek Tiwari on 2021-01-19. - No new committers. Last addition was Abhishek Mahendra Jain on 2025-01-18. ## Project Activity: - Enabled independent dynamic scaling for different activities within a workflow, including memory and container configuration per stage and proper queue routing. - Added fast-failure support for workflows on quota-exceeded and other non-retryable exceptions to surface errors sooner. - Implemented Orchestration Layer issue capturing to surface and emit service-layer errors as structured issues. - Added configurable timeout to GoblinTaskRunner shutdown and improved metrics reporting lifecycle ordering. - Enhanced Iceberg source lineage tracking by adding fsUri and missing source/destination metadata to dataset descriptors. - Added a configurable skip-permission-check flag for files already existing at the target location, improving copy-discovery performance. - Fixed incorrect job execution ID resolution when fetching job status in GaaS flows, with safe fallback handling and added unit tests. - Added cleanup logic for staging directories during graceful flow shutdown, including GRACEFUL_SHUTDOWN signaling in the Yarn launcher. - Made Orchestrator MDM metric dimensions configurable for job-success events. - Updated JAR cache directory partitioning to bi-monthly intervals. ## Community Health: - Since Sep 2025, there have been 12 commits - 9 were from relatively new, non-committer contributors. - Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as committers. We constantly look for consistent contributors to vote them in as Committers. ----------------------------------------- Attachment AE: Report from the Apache Gravitino Project [Jerry Shao] ----------------------------------------- Attachment AF: Report from the Apache Guacamole Project [Mike Jumper] ----------------------------------------- Attachment AG: 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. ## Project Status Current Status: dormant - when things need to be done, they get done Issues: There are no issues requiring board attention. ## Membership Data Apache Gump was founded 2004-02-18. 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 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. ----------------------------------------- Attachment AH: Report from the Apache Helix Project [Junkai Xue] ## Description: The mission of Helix is the creation and maintenance of software related to A cluster management framework for partitioned and replicated distributed resources ## Project Status: Current project status: moderate, ongoing Issues for the board: N/A ## Membership Data: Apache Helix was founded 2013-12-17 (12 years ago) There are currently 28 committers and 18 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 Jiajun Wang on 2022-11-02. - No new committers. Last addition was Molly Gao on 2023-06-06. ## Project Activity: - 1.3.2 was released on 2025-08-29 - 1.4.3 was released on 2025-02-04 ## Community Health: - Final round of 2.0 pre release: Helix 2.0 code are feature completed and tested. Before 2.0 release, there are recent fixings for unstable tests from 50% pass rate to 80% (latest 10 CIs on main branch). - Potential 1.3.x release Seemed to be a lot of users staying with 1.3.x. There are recent bug fix PRs preferred to backport to 1.3.x. If more people asks, 1.3.x releases will perform. - More new contributors Observing more contributors from users point view trying Helix. Activities increased a lot comparing as before. - Light weight helix-tendril project in planning Once 2.0 release is done. A light weighed Helix management lib should be started with development. ----------------------------------------- Attachment AI: Report from the Apache Hive Project [Naveen Gangam] ## Description: The Apache Hive™ data warehouse software facilitates reading, writing, and managing large datasets residing in distributed storage (Apache Hadoop) using SQL. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Hive was founded 2010-09-21 (15 years ago) There are currently 113 committers and 59 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 Shohei Okumiya on 2025-12-07. - Soumyakanti Das was added as committer on 2025-12-14 ## Project Activity: Apache Hive 4.2.0 was released on 2025-11-23. Hive 4.3.0 planning is underway. ## Community Health: Project is super health (Score: 10) There has been a 43% decrease in the activity of the dev list compared to the previous quarter. Gitbox activity has decreased by 19% from last quarter and is consistent with the prior quarters before. Jira Activity: 130 JIRA tickets opened and 92 closed in the past quarter. Overall healthy development and release activity in the Apache Hive community ----------------------------------------- Attachment AJ: 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 ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Hudi was founded 2020-05-19 (6 years ago) There are currently 42 committers and 20 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 Yue Zhang on 2025-06-30. - Shawn Chang was added as committer on 2025-12-21 ## Project Activity: Hudi 1.1.1, released in Dec 2025, focused on stabilizing the 1.1.0 milestone and improving user adoption. Hudi 1.2, expected late March, is currently under active development, introducing key code-path refactoring to establish a stronger foundation for future features. In parallel, the community is preparing patch releases (1.1.2, 1.0.3, 0.14.2, and 0.15.1) to address bug fixes and improve stability, while also working on Hudi-rs 0.5.0 to support newer Hudi table versions and the metadata table. ## Community Health: We continue to see steady growth in community engagement on GitHub, with active participation in code contributions and discussions. The dev and users lists serve as primary channels for low-bandwidth communication, while GitHub issues continue to be the main engagement model for community support. The PMC continues to host the weekly developer sync meetings. ----------------------------------------- Attachment AK: Report from the Apache HugeGraph Project [Jermy Li] # HugeGraph project board report ## Description: Apache HugeGraph is a full-stack graph database system, providing complete graph data processing capabilities, include large-scale graph storage, real-time querying, offline analysis, and graph AI. Supporting both Gremlin and Cypher query languages. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache HugeGraph was founded 2026-01-21 (1 month ago). There are currently 22 committers and 12 PMC members in this project. The Committer-to-PMC ratio is about 2:1. Community changes, past quarter: - No new PMC members. Last addition was PPMC Member Yuchen Ding on 2024-12-18. - No new committers. Last addition was Zhe Wang on 2025-09-01. ## Project Activity: The HugeGraph release cycle is now 6 to 12 months, and a new version is expected to be released in 2026. - 1.7.0 was released on 2025-11-28. Last month, we were preparing 1.8.0 release -- the first release after graduation. We expect to complete the release within the next 2 months. ## Community Health: Mail list dev@hugegraph.apache.org had a 39% increase in traffic in the past quarter (141 emails compared to 101). Last quarter, we mainly focused on [1.7.0 release](https://s.apache.org/u1quh) and preparing for apache graduation. ----------------------------------------- Attachment AL: Report from the Apache Iceberg Project [Ryan Blue] ## Description: Apache Iceberg is a table format for huge analytic datasets that is designed for high performance and ease of use. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Iceberg was founded 2020-05-19 (6 years ago) There are currently 37 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - Prashant Singh was added to the PMC on 2026-02-23 - Sung Yun was added to the PMC on 2026-02-23 - Drew Gallardo was added as committer on 2026-02-23 ## Project Activity: Releases: - Go 0.5.0 was released on 2026-03-05 - PyIceberg 0.11.1 was released on 2026-03-02 - PyIceberg 0.11.0 was released on 2026-02-09 - C++ 0.2.0 was released on 2026-01-26 - Rust 0.8.0 was released on 2026-01-16 - Java 1.10.1 was released on 2025-12-22 REST specs: - Adopted a spec for exchanging SQL UDFs - Added referenced-by to table/view loading to support secure DEFINER views v4 table spec: - Design docs for v4 are reaching consensus and next up are the spec changes - Prototypes are going into Iceberg Java for content stats and adaptive metadata - Added column overwrite and append to the v4 goals - Discussing extending the expressions that can be exchanged for new use cases - Ongoing discussion for adding secondary indexes, but the timeline is unclear Java: - Adding remote scan planning implementation - Committed the pluggable file format APIs - Implemented freshness-aware table loading for REST catalog - Implemented idempotency tokens for REST catalog updates - Made separator character configurable for REST catalogs - Spark: Added module for version 4.1 - Spark: Added schema evolution in MERGE commands - Flink: Added maintenance that does not require other engines - Dropped support for Java 11 PyIceberg: - Added Python 3.13 support - Added rollback support - Added REST scan planning support - Added support for storage-credentials - Now supports timestamptz, geometry, and geography Rust: - Discussing how to refactor and modularize - Added Arrow schema conversion with field IDs - Adding more DataFusion integrations: create/drop table, LIKE, LIMIT - Added support for v2 to v3 upgrades with existing data - Added storage trait for FileIO implementations, replacing direct OpenDAL - Added support for compressed metadata.json files Go: - Added support for AuthManager - Added support for views - Working on row lineage support from v3 - Added support for unknown type - Improving write support with overwrite, copy-on-write, and merge-on-read - Supports rolling at file size limit - Added Hive Catalog client C++: - Website is live at https://cpp.iceberg.apache.org/ - Adding update and write support, including fast appends - Added REST catalog auth API, basic auth - Implemented DataWriter for Parquet and Avro files - Implemented SnapshotManager Created a new repo for a terraform provider and added a Flink quickstart guide. ## Community Health: We are happy to welcome Prashant and Sung as a PMC members and Drew as a new committer! The community shows steady health metrics this quarter. There was an increase in dev list traffic, but this metric tends to fluctuate based on development cycles and other factors like holidays. Unfortunately, PR and git metrics were not available. The community is also planning the third Iceberg Summit in early April 2026. See https://www.icebergsummit.org/ for the agenda and details. ----------------------------------------- Attachment AM: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for March 2026 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. As of February, there are 28 podlings under incubation. Five releases were made during the month, and no IP clearances were completed. Two podlings graduated, Gluten and Polaris, and no podlings retired. However, there are votes underway to retire BareMaps and HoraeDB. There were no additions or removals to IPMC membership. Mailing list traffic during the month focused on release voting, graduation discussions, and discussion and votes on retirement. Auron was invited to take part in a 6-month review. Iggy also requested to participate in a review. Most podlings continue to make steady progress toward graduation. Caldera is off to a slow start. Livy has voted to graduate on its mailing list, and Toree's latest release seems to be taking longer than expected. ResilientDB is likely to graduate soon. Pegasus is still experiencing some community difficulties and may need follow-up. There is some concern about the progress of OpenServerless, as they state they are nearing graduation, but have not made a release. Two podlings, Caldera and OzHera, failed to submit a report and will be asked to report next month. All submitted podling reports had mentors' sign-off. ## Community ### New IPMC members: - none ### People who left the IPMC: - none ## New Podlings - Casbin ## Podlings that failed to report, expected next month - Caldera - OzHera ## Graduations - Gluten - Polaris   The board has motions for the following: - None ## Releases The following releases entered distribution during the month of February: - Fesod 2.0.1 - Gluten 1.6.0 - Iggy 0.7.0 - Livy 0.9.0 - Seata 2.6.0 ## IP Clearance - None ## Legal / Trademarks - N/A ## Infrastructure - N/A ## Table of Contents [Auron](#auron) [Baremaps](#baremaps) [BifroMQ](#bifromq) [Caldera](#caldera) [Iggy](#iggy) [KIE](#kie) [OpenServerless](#openserverless) [Otava](#otava) [OzHera](#ozhera) [Polaris](#polaris) [PouchDB](#pouchdb) [GeaFlow](#geaflow) -------------------- ## Auron Auron accelerates Apache Spark SQL by providing an alternative vectorized execution layer implemented in Rust, enabling native performance while maintaining full Spark compatibility. Auron has been incubating since 2025-08-05. ### Three most important unfinished issues to address before graduating: 1. Increase public communication on dev@ and ensure all project decisions and planning are captured on the mailing list. 2. Grow the community and attract more contributors and users. 3. Enhance community diversity and sustainability. ### 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. One new committer added: Mang Zhang. 2. 10 new contributors since last release. 3. Continued active development with code quality improvements. ### How has the project developed since the last report? 1. Published 7.0.0-incubating release with 251 new commits. 2. Added three Improvement Proposals for Flink support, correctness testing, and CI integration testing. 3. Introduced new AuronConfiguration system and fixed major correctness issues. 4. Enhanced native function support with 20+ new functions. 5. Added Spark 4.0.2/3.5.8 and JDK 21 compatibility. 6. Improved CI/CD with JUnit 5 and code quality plugins. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2026-03-04 ### When were the last committers or PPMC members elected? 2025-12-19 ### Have your mentors been helpful and responsive? Yes, all the mentors are helpful and responsive on the community growth and project development. ### Is the PPMC managing the podling's brand / trademarks? Yes. The podling name "Auron" has been reviewed by the VP, Brand. We are not aware of any misuse by third parties. ### Signed-off-by: - [X] (auron) Becket Qin Comments: Happy to see the development of Flink support. - [X] (auron) Calvin Kirs Comments: Good to see the new version released. - [ ] (auron) Hao Ding Comments: - [ ] (auron) Nicholas Jiang Comments: ### IPMC/Shepherd notes: -------------------- ## 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. ### How has the project developed since the last report? Baremaps has voted to retire from the Incubator, the corresponding Incubator PMC vote is ongoing. ### Have your mentors been helpful and responsive? Mentors have been involved in the retirement decision. ### Signed-off-by: - [X] (baremaps) Bertrand Delacrétaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [ ] (baremaps) Julian Hyde Comments: - [X] (baremaps) Calvin Kirs Comments: Voting on retirement. - [ ] (baremaps) George Percivall Comments: ### IPMC/Shepherd notes: -------------------- ## BifroMQ BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery. BifroMQ has been incubating since 2025-04-22. ### Three most important unfinished issues to address before graduating: 1. Increase public exposure to expand the community user base and improve project visibility. 2. Continue delivering regular releases, streamline the release management process, and rotate the Release Manager role among key contributors. 3. Grow community participation beyond the original contributors, including attracting new reviewers and contributors. ### Are there any issues that the IPMC or ASF Board need to be aware of? We understand that the trademark transfer has been completed based on publicly available trademark ownership information (e.g. via https://aiqicha.baidu.com/mark/s?q=BIFROMQ&t=7). However, we would appreciate receiving an official confirmation from ASF (a scanned copy of the signed transfer agreement would be sufficient) so that our company can properly archive the transfer documentation for internal compliance purposes. ### How has the community developed since the last report? We have observed increasing activity on GitHub and the dev@ mailing list. Our mentor (Chris) helped initiate a valuable discussion with the Apache IoTDB community, which may lead to potential collaboration between the two projects. We have set up a WeChat Account (“BifroMQ”) to publish Chinese translations of release announcements. All published content is derived from or links back to the official Apache BifroMQ website, and the account is not used for community discussions. ### How has the project developed since the last report? We completed our first incubating release after 3 RC votes. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2026-01-28 ### When were the last committers or PPMC members elected? None so far ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. Our mentors have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? We attempted to rename our WeChat account by adding the “Apache” prefix, based on PPMC consensus reached on the private mailing list. However, the request was rejected by the WeChat platform due to tightened naming policies, which now require an official authorization document from ASF to use “Apache” as an account prefix. We would appreciate guidance on whether there is a formal ASF process to request such an authorization letter for external platform compliance purposes. ### Signed-off-by: - [ ] (bifromq) Christofer Dutz Comments: - [ ] (bifromq) Xiangdong Huang Comments: - [X] (bifromq) Calvin Kirs Comments: - [ ] (bifromq) Penghui Li Comments: - [ ] (bifromq) Sheng Wu Comments: ### IPMC/Shepherd notes: -------------------- ## Iggy Iggy is a high-performance, ultra-low latency and large-scale persistent message streaming platform written in Rust. Iggy has been incubating since 2025-02-04. ### Three most important unfinished issues to address before graduating: 1. Continue expanding the community, release more versions under ASF 2. Increase the use of GitHub Discussions/Issues integrated with mailing lists ### 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? - Discord members count ~650, new contributors writing proposals (discussions), submitting PRs for fixing issues, docs, enhancements. - Github stars reached 3.9K+ - Crates downloads reached 185K+ - Recent blog post on Apache Iggy's migration journey to thread-per-core architecture powered by io_uring (https://iggy.apache.org/blogs/2026/02/27/thread-per-core-io_uring) drew a lot of attention on other sites and social media and attracted critical talent - Attending RustINDIA Conference 2026 - The community continues to grow. We are pleased to welcome Łukasz Zborek as a new Apache Iggy committer. Łukasz has been a core contributor to the C# SDK and is currently the #8 contributor in the repository. Beyond building a high-quality C# SDK, he has contributed across the project including CI improvements, BDD testing, TLS support, reconnection handling, and high-level consumer/publisher APIs. ### How has the project developed since the last report? - Released 2 versions [0.6.0](https://github.com/apache/iggy/releases/tag/server-0.6.0) and [0.7.0](https://github.com/apache/iggy/releases/tag/server-0.7.0). - 0.7.0 release had 188 commits from 19 contributors and over 1,200 files changed - Deterministic tick-based timeout mechanism for VSR — improves reliability for Viewstamped Replication workflows, a core building block toward clustering and distributed coordination. - New cluster primitives (on_replicate, send_prepare_ok, replicate, view change, partitions trait) to solidify cluster control paths and prepare for future distributed expansions. - Metadata state machine foundation & snapshot interface — essential groundwork for robust metadata handling and future high-availability features. - Embedded Web UI now included in the server and enabled by default — no extra deployment step required for the dashboard experience. - NUMA awareness — improves performance on multi-socket hardware by aligning memory and CPU locality. - Http.web_ui config option gives users control over Web UI exposure and configuration. - Graceful shard shutdown on panic, enhanced async disk I/O availability handling, and improved critical task failure handling — all contribute to greater server resilience. - Retry mechanism and detailed logging for connector HTTP configuration — increasing robustness when integrating with external systems. - Prometheus metrics and stats endpoints now exposed for connectors so observability is first-class. - Extended Postgres sink & source plugins with integration tests for richer pipeline ingestion. - Connector runtime --version flag & other quality-of-life improvements for ops tooling. - Java SDK enhancements: fluent builder API, better tests, and async serialization improvements. - Python SDK: async iterator support for consumer — smoother integration for modern async apps. - Go leader redirection scenario addition — improved client routing logic. - C# SDK: expanded API surface and .NET 10 support. - Linux edge binary builds + ARM64 support — expands platform compatibility for pre-release runners. - Automated artifacts & enhanced CI workflows (auto-publish, better shared caches, native runners) to speed iteration and ensure release quality. - Pre-commit hooks, TOML formatting, auto-publish workflows across SDKs and languages — boosts contribution hygiene. - Expanded API tests, integration tests, watchdogs, and crash detection — better confidence in deployment and regression risk reduction. - Rust toolchain bump (1.92.0) and widespread dependency updates. - Replace unmaintained serialization (msgpack replacing old libs) — steers toward more sustainable and performant internals. - Migration to up-to-date ecosystem dependencies (e.g., Yew & yew-router) for UI stack improvements. - Many other improvements, ecosystem expansion tickets are in progress. ### 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 - [X] Nearing graduation - [X] Other: Expanding Ecosystem ### Date of last release: 2026-02-25 ### When were the last committers or PPMC members elected? 2026-01-13 [Łukasz Zborek is the last committer elected] ### Have your mentors been helpful and responsive? Yes, mentors are available for voting and approvals. That said, having a few more active mentors would be beneficial to ensure continuity and help us address any gaps as we move toward graduation. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues as reported here. VP, Brand approved the project name. ### Signed-off-by: - [ ] (iggy) Hao Ding Comments: - [ ] (iggy) Yonik Seeley Comments: - [ ] (iggy) Zili Chen Comments: - [X] (iggy) Hulk Lin 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. Finish the remaining Category X removal 2. Community Building  3. More releases ### Are there any issues that the IPMC or ASF Board need to be aware of? Nope. ### How has the community developed since the last report? New contributor submitting PRs with new functionalities. ### How has the project developed since the last report? Large chunks of Category X codebase has been removed. Hibernate has been upgraded to latest ASLv2 release, removing another major graduation blocker. Right now new release has been branched and Release Manager working on it. ### 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 - [X] Other: With the large cleanup of Category X issues, we believe the next couple of releases will unlock graduation. ### Date of last release: 2025-07-10 ### When were the last committers or PPMC members elected? 2025-11-26 ### Have your mentors been helpful and responsive? Mentors have been good so far. No issues. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (kie) Brian Proffitt Comments: - [ ] (kie) Claus Ibsen Comments: - [X] (kie) Andrea Cosentino Comments: All good. Project is healthy. ### IPMC/Shepherd notes: -------------------- ## OpenServerless OpenServerless is an open source, cloud-agnostic, serverless platform. It offers a complete environment for serverless applications development, based on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an unified developer experience with a plethora of services (SQL or noSQL databases, key-value stores, object storage, LLMs services, function schedulers) managed by the platform's core: the operator, along with tooling (the CLI) to simplify (and interact with) deployments, integrated ide and starter application and optimized runtimes integrated with the staters. OpenServerless has been incubating since 2024-06-17. ### Three most important unfinished issues to address before graduating: 1. reactivate the build system that was phased out because of expired cloud credits - Nuvolaris provided the resources and we requestes also 2. create a self-contained distribution that builds from sources - already in place a kit to do that creating images in a local docker and the loading into a cluster 3. embed tasks in the cli binary as we cannot distribute something that self-updates from the cloud ### Are there any issues that the IPMC or ASF Board need to be aware of? we are asking for resources to AWS to test in cloud ### How has the community developed since the last report? New contributors and more adopters, including cloud providers like the Italian Government Cloud, the Polo Strategico Nazionale and 2 cloud italian ### How has the project developed since the last report? We are completing the major features like the devcontainer and the embedded registry for custom actions auto-created ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: XXXX-XX-XX ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? Yes Are things falling through the cracks? If so, please list any open issues that need to be addressed. We need more visibility in the international community. We have huge visibility in Italy but basically absent outside. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? ### Signed-off-by: - [ ] (openserverless) Bertrand Delacrétaz Comments: - [X] (openserverless) Enrico Olivelli Comments: - [ ] (openserverless) François Papon Comments: - [X] (openserverless) JB Onofré Comments: Can we have an update on release ? The podling seems to struggle about growing the community and very low activity on the mailing lists. It would be great to have an update and plan. - [X] (openserverless) PJ Fanning Comments: No obvious progress on a 1st release and podling is nearly 2 years old. Mailing list traffic is minimal. Really just GitHub automated msgs. I would disagree with the report's assertion that the podling is nearing graduation. ### IPMC/Shepherd notes: -------------------- ## Otava Apache Otava (incubating), a command-line tool, written in Python, detects and alerts about statistically significant changes in performance test results (more generally, time-series data) stored in CSV files or a number of supported databases. A typical use-case of Otava is as follows: 1. A set of performance tests is scheduled repeatedly, such as after each commit is pushed. 2. The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files. 3. Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly. 4. Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications. 5. Otava is capable of finding even small, but persistent shifts in metric values, despite noise in data. It adapts automatically to the level of noise in data and tries to notify only about persistent, statistically significant changes, be it in the system under test or in the environment. Otava has been incubating since 2024-11-27. Otava entered Incubation as Hunter. ### Three most important unfinished issues to address before graduating: 1. Establish frequent releases as a routine, repeatable process 2. Improve documentation to lower the entry barrier for users and contributors. 3. Define and document the desired long-term architecture. The goals of the long-term architecture are: a. Modularity: Keep the core library lightweight while making external dependencies (data sources and notification channels) pluggable. b. API stabilization: Clearly define and stabilize public interfaces prior to a 1.0.0 release. ### 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 community added one new committer and a PMC member, who contributeda a rewrite of the core changepoint detection algorithm and authored an introductory doc on changepoint detection theory in Otava. Since the last report, there have been 4 additional contributors participated through patches and discussions. One contributor is a developer from RedPanda, who reports using Otava extensively for both continuous benchmarking and finding regressions in PRs. Another contributor developed a visualization tool that allows users to model and explore changepoint detection results across different time series. This tool improves understanding of the algorithm’s behavior and provides a practical aid for internal development and experimentation. Additionally, open-source projects that position performance as a key feature (e.g., [hardwood](https://github.com/hardwood-hq/hardwood/issues/25)) have expressed interest in using Otava for continuous benchmarking. ### How has the project developed since the last report? The project addressed 3 out of 4 main previously stated priorities: 1. Upgraded to supported Python versions. Re-implement the core changepoint detection algorithm and drop the dependency on signal-processing-algorithms. 2. Added a new PPMC member. 3. Publicity around the project. Since the last report, Henrik Ingo did a talk about Continuous Performance Engineering at FOSDEM 2026. The remaining issue is making frequent releases a routine. As a first step, the project added a step-by-step release guide to facilitate repeatable releases. ### 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: We are seeing a slow positive trend in community building, but not yet nearing graduation. A self review based on https://s.apache.org/727vc Code 5/5 Licenses and Copyright: 5/5 Releases: 5/5 Quality: 5/5 Community: 7/7 Consensus: 4/5 (Missing: CS10) Independence: 2/2 Brand: 4/4 ### Date of last release: 2025-12-12 ### When were the last committers or PPMC members elected? March 2 2026 ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? VP, Brand approved the new project name in February 2025. Our life as an ASF incubating project really only started after that date. We are not aware of any trademark issues related to the new project name. ### Signed-off-by: - [X] (otava) Dave Fisher Comments: - [X] (otava) Enrico Olivelli Comments: - [X] (otava) Lari Hotari Comments: - [X] (otava) Mick Semb Wever Comments: ### IPMC/Shepherd notes: -------------------- ## PouchDB PouchDB is an open-source JavaScript database inspired by Apache CouchDB that is designed to run well within the browser. PouchDB has been incubating since 2025-04-15. ### Three most important unfinished issues to address before graduating: 1. Making a release 2. Adding contributors 3. Finish infrastructure migration (currently working on the website) ### Are there any issues that the IPMC or ASF Board need to be aware of? After delays last year and the promise to keep project momentum up, this has been the case. ### How has the community developed since the last report? - We have added a new committer and PPMC member. - Work continues on a first release ### How has the project developed since the last report? We have migrated our website tech to a more modern platform that can make use of the ASF website hosting infrastructure. Final steps are taken at the moment of writing. We also have received multiple external contributions from people previously not affiliated with the project at a volume and quality that exceeds the usual pace. Finally, we have formalised our stance on LLM-generated code. ### 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: n/a ### When were the last committers or PPMC members elected? January 28th 2026 ### Have your mentors been helpful and responsive? Mentors continue to be active and helpful ### Is the PPMC managing the podling's brand / trademarks? PPMC have not yet requested a Podling Suitable Names Search ### Signed-off-by: - [X] (pouchdb) PJ Fanning Comments: - [X] (pouchdb) Jean-Baptiste Onofré Comments: Any plan for a first release ? ### IPMC/Shepherd notes: -------------------- ## GeaFlow GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis. GeaFlow has been incubating since 2025-06-06. ### Two most important unfinished issues to address before graduating: 1. Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions. 2. Implement predictable release cycles and maintain high project stability to encourage broad participation and adoption. ### 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 GeaFlow community has maintained its core contributor base over the past month, with existing contributors continuing to drive development. The community has remained active with ongoing contributions including new features, optimizations, and bugfix. Additionally, several PRs are currently under review. ### How has the project developed since the last report? Over the past month, the GeaFlow project has continued its progress with a focus on feature enhancements, code quality improvements, and infrastructure updates. Key developments include: - Introduced the CASTS operator to enhance GeaFlow's reasoning capabilities within the AI component (#737). - Refactored varint encoding/decoding constants to improve code readability and maintainability (#744). - Updated repository references in documentation to reflect the official Apache location (#746). - Fixed typos in log messages and comments across multiple files (#752). - New issues were opened, covering topics such as architecture design, documentation consistency, contributor guidance, and potential overflow bugs, indicating active community scrutiny and roadmap discussions. These updates demonstrate continued advancement in Graph+AI functionality, codebase health, project branding alignment, and community-driven evolution. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: The last version was released on November 19, 2025. ### When were the last committers or PPMC members elected? The last committers were elected on January 4, 2026. ### Have your mentors been helpful and responsive? Yes, we have received helpful guidance. ### Is the PPMC managing the podling's brand / trademarks? N/A. ### Signed-off-by: - [X] (GeaFlow) Willem Ning Jiang - [X] (GeaFlow) xinwang - [ ] (GeaFlow) lzljs3620320 - [ ] (GeaFlow) jmclean - [ ] (GeaFlow) paulk ### IPMC/Shepherd notes: ----------------------------------------- Attachment AN: 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. ## Project Status: Current project status: Ongoing with high activity. Issues for the board: no. ## Membership Data: Apache IoTDB was founded 2020-09-16 (5 years ago) There are currently 82 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 3:1. Community changes, past quarter: - No new PMC members. Last addition was Hongyin Zhang on 2025-11-07. - Zhenyu Shi was added as committer on 2026-01-13 - Weihao Li was added as committer on 2026-01-13 - Zhengming Zhang was added as committer on 2026-01-16 ## Project Activity: - We released version 1.3.6 and 1.3.7 in past quarter, which fixed some bugs and security issues in 1.3.X series. - For 2.X series, We have significantly expanded the data query capabilities for our table model. Key updates include the introduction of select-into clause, and the addition of the MATCH RECOGNIZE feature, which now supports aggregate functions to efficiently capture, analyze, and calculate continuous data streams. Furthermore, we enriched the system's analytical toolkit by adding built-in scalar functions for bit manipulation and a pushdown-enabled EXTRACT time function, all specifically designed to optimize table model queries. - The community has taken a significant step forward in online schema evolution. We now support data type modifications in both the tree and table models. This presents a formidable challenge for our LSM-Tree storage engine, which is built upon the immutable TsFile format. ## Community Health: Overall community health is good. - dev@iotdb.apache.org had a 235% increase in traffic in the past quarter (238 emails compared to 71) - There has been a lot of discussion within the community recently regarding AI-assisted programming[1][2]. Our goal is to transform the IoTDB project into an AI-Native database. In early January, Apache IoTDB was officially included in the Google Code Wiki. - Developer Experience Enhancements: To better support our user base and streamline the onboarding process, we integrated a new "Ask AI" function into the official Apache IoTDB homepage. This feature provides developers with instant, intelligent assistance for navigating documentation and resolving technical queries more efficiently - GSoC: We are actively participating in Google Summer of Code (GSoC) 2026 to foster new contributors. Community members, including Yuan Tian, Haonan, Xuan, and Yongzao, have submitted four project ideas. These proposals have already successfully attracted prospective students and sparked active technical discussions within the community. [1] https://lists.apache.org/thread/43fh7z2q3h1mmy1z9grgd13dnx1xd0w7 [2] https://lists.apache.org/thread/jl94gcrv9973jj7cwfhl7zrkhr19thqr ----------------------------------------- Attachment AO: Report from the Apache Jackrabbit Project [Marcel Reutegger] Apache Jackrabbit: Board Report March 2026 (draft) ========================================== ## 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. ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: none ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (20 years ago). There are currently 60 committers and 60 PMC members in this project. The Committer-to-PMC ratio is 1:1, because all committers automatically become PMC members. Community changes, past quarter: - No new PMC members. Last addition was Alejandro Moratinos on 2025-08-27. - No new committers. Last addition was Alejandro Moratinos on 2025-08-27. ## 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 oak-blob-azure module was upgraded from Azure SDK V8 to V12, a major dependency and API change. The project also raised the minimum Java version to 17 across build and CI (OAK-11952), and delivered simplified index management (OAK-12010 / OAK-12110), introducing a new index management path with diff index support and refinements across multiple releases. Segment store reliability saw important improvements. The oak-segment-azure component received memory optimisations (UUID and GCGeneration handling, structure changes), and test stability fixes to address OutOfMemory issues by ensuring proper cleanup of FileStores and closeable resources (OAK-12085). The GCGeneration class was moved into an exported SPI package (OAK-12084), clarifying the public API for segment and GC generation. The ongoing effort to reduce dependence on Google Guava continued. Guava’s Monitor, Guard, SettableFuture, Striped locks, Uninterruptibles (await, sleep, join, drain), ThreadFactoryBuilder, and related utilities were replaced with JDK or oak-commons equivalents. Guava dependencies were removed from several modules as part of the long-term goal to drop the Guava dependency. ## Community Health: The project is generally 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: - jackrabbit-2.23.3-beta released on 2025-12-11 - jackrabbit-oak-1.90.0 was released on 2026-01-07 - jackrabbit-2.22.3 was released on 2026-01-16 - jackrabbit-filevault-4.2.0 was released on 2026-02-27 - jackrabbit-oak-1.92.0 was released on 2026-03-03 ## JIRA activity: - 129 JIRA tickets created in the last 3 months - 108 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: 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. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Karaf was founded 2010-06-16 (16 years ago) There are currently 34 committers and 16 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 Francois Papon on 2018-11-29. - Holger Friedrich was added as committer on 2026-03-02 ## Project Activity: * Apache Karaf 4.4.9 has been released on 2025-12-15 * Apache Karaf 4.4.10 has been released on 2026-02-13: this maintenance release continues the stability of the 4.4.x series, providing critical dependency updates and bug fixes. * Apache Karaf Integration: as part of the 4.4.x updates, the "Integration Distribution" is now fully available. This serves as a primary migration path for users of the dormant Apache ServiceMix project, providing a modern, supported alternative. * We are already preparing Karaf 4.4.11 release, including new fixes and better Java 21 support. * Karaf 4.5.0 roadmap: development is progressing for the 4.5.x series. Key focus area include: ** Java 25 support. ** Update feature resolver. ** Refined Karaf services. ** Removal of legacy specs bundles to streamline the runtime. Apache Karaf Decanter 3.0.0 is in preparation with a lot of updates, fixes and refactoring. This is plan for the next quarter. ## Community Health: * We are happy to welcome a new committer: Holger Friedrich. * We see dev@karaf.apache.org had a 161% increase in traffic in the past quarter (94 emails compared to 36) and user@karaf.apache.org had a 23% increase in traffic in the past quarter (58 emails compared to 47): user@ mailing list remains active with troubleshooting and migration queries, while dev@ mailing list is centered around the 4.5.0 roadmap and security patching. * Security (CVE-2026-24656): a vulnerability was identified in Apache Karaf Decanter involving deserialization of untrusted data in the log socket collector. The community acted switfly, releasing Decanter 2.12.0 to address this flaw. Users are strongly encouraged to upgrade or implement firewall rules to restrict access to the collector port (4560). * Infrastructure: the project has successfully transitioned to GitHub Issues and GitHub Action, with the legacy Jira instance now in read-only mode. ----------------------------------------- Attachment AQ: Report from the Apache Kvrocks Project [Mingyang Liu] ## Description: The mission of Apache Kvrocks is the creation and maintenance of software related to a distributed key-value NoSQL database, supporting the rich data structure. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kvrocks was founded 2023-06-21 (3 years ago) There are currently 30 committers and 13 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 Aleks Lozoviuk on 2025-05-06. - Xiaojun Yuan was added as committer on 2026-02-24 ## Project Activity: Apache Kvrocks 2.15.0 was released at the end of February. Xiaojun Yuan was invited to become a new Kvrocks committer in recognition of his contributions to cluster-related features, in February. Recently, Kvrocks development has been focused mainly on clustering, including optimizations to master-replica replication. There has been less progress in other areas. In terms of Redis compatibility, the main improvements have been support for more Redis commands and compatibility with Redis’s multi-database mechanism. ## Community Health: In terms of data, the number of issues was similar to the previous quarter, but the number of PRs dropped by 30%. It seems there was a certain decline in contributor activity during this period. Kvrocks may need some fresh momentum and new demand to attract broader participation. This is also related to the fact that several key maintainers, myself included, have had less time to devote to the project due to work and other commitments. ----------------------------------------- Attachment AR: Report from the Apache Kylin Project [Yang Li] ## Description: The mission of Apache Kylin is the creation and maintenance of software related to a distributed and scalable OLAP engine, with a focus on pre-computation according to learned query patterns. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kylin was founded 2015-11-18 (10 years ago) There are currently 52 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08. - No new committers. Last addition was Pengfei Zhan on 2024-11-12. ## Project Activity: - A draft implementation of Kylin MCP that allows LLM to explore table metadata and run SQL queries in natural language. The code is temporarily hosted at https://github.com/jlfsdtc/Kylin-MCP and will merge back to official repo after more tests. - A few other bug fixes as always. ## Community Health: The lower activity metrics is due to 1) Chinese new year, many developers were taking leaves; 2) the MCP work run as a side project does not reflect in the metrics. I'm working to move it back to the normal dev process. ----------------------------------------- Attachment AS: Report from the Apache Kyuubi Project [Cheng Pan] ## Description: The mission of Apache Kyuubi is the creation and maintenance of software related to a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kyuubi was founded 2022-12-21 (3 years ago) There are currently 29 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 Binjie Yang on 2024-07-05. - No new committers. Last addition was He Zhao on 2025-01-02. ## Project Activity: Released Apache Kyuubi v1.11.0 at 2025-12-31; Released Apache Kyuubi v1.10.3 at 2026-01-02; The community discussing the release of Apache Kyuubi v1.11.1. The community has been working closely with other ASF projects, like Hadoop and Spark, to perpare for JDK 25 support. ## Community Health: dev@kyuubi.apache.org had a 1250% increase in traffic in the past quarter (27 emails compared to 2); notifications@kyuubi.apache.org had a 20% increase in traffic in the past quarter (550 emails compared to 457); The overall traffic is low, but still at a good state because the project itself is mature enough. Exploring the combination of Kyuubi and AI could be a potential way to increase community engagement. ----------------------------------------- Attachment AT: Report from the Apache Linkis Project [Shuai Di] ## Description: The mission of Apache Linkis is to build a distributed computation middleware to facilitate connection, governance, extensibility and orchestration between the upper applications and the underlying data engines. ## Project Status: Current project status: Ongoing Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache Linkis was founded 2022-12-21 (3 years ago) There are currently 39 committers and 26 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Jie Cheng on 2024-01-28. - Kazutoiris is applying to become a committer. ## Project Activity: Apache Linkis v1.9.0 is currently under development, with the following key features planned: - Enhanced EC reuse, supporting resource verification and Python version validation. - Enabled coexistence of Spark 2 and Spark 3 runtime environments. - Optimized task log display on the management console to support UDF log viewing. - Increased the maximum number of concurrent tasks supported by the concurrency engine configuration. - Fixed incorrect resource display issues. ## Community Health: Overall community health is good. - 9 PRs closed on GitHub, past quarter. - 14 issues closed on GitHub, past quarter. ----------------------------------------- Attachment AU: Report from the Apache Lucene Project [Ben Trent] ## Description: The mission of Lucene is the creation and maintenance of software related to Search engine library ## Project Status: Current project status: Active, ongoing Issues for the board: None ## Membership Data: Apache Lucene was founded 2005-01-18 (21 years ago) There are currently 111 committers and 70 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Shubham Chaudhary was added as committer on 2026-01-07 - Zhou Hui was added as committer on 2025-12-19 ## Project Activity: Release 10.4.0 of Apache Lucene was released on 2026-02-25. This was a significant release improving search latency, expanding and improving knn vector search capabilities, and laying ground work for further performance improvements. In addition, there have been many developer quality of life improvements in the build system, switching to prek for precommit checks, and improving test runtimes for developers. ## Community Health: Between the dates 2025-12-08 and 2026-03-04 there were 248 pull requests, 204 of them closed. 203 commits in total to the main branch, 68 new issues and 34 of them successfully closed. Apache Lucene has also seen an influx of agentic/LLM created issues and PRs. This has led to a PMC discussion on how to address and guide new contributors so that they learn, instead of simply being an in-between for agents. ----------------------------------------- Attachment AV: Report from the Apache Lucene.Net Project [Shad Storhaug] ----------------------------------------- Attachment AW: Report from the Apache MADlib Project [Ed Espino] ----------------------------------------- Attachment AX: 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 ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Mynewt was founded 2017-06-21 (9 years ago) There are currently 37 committers and 19 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 Jerzy Kasenberg on 2019-10-24. - No new committers. Last addition was Michał Górecki on 2024-06-27. ## Project Activity: Added CI workers that run tests on selected real HW boards. More imported code is removed in favor of using external modules (avoid code copying and makes updates much easier). Removal of deprecated code is ongoing to reduce maintenance burden. IP stack related work is ongoing. Various bugfixes are being committed. On Bluetooth side qualification bugfixes and Channel Sounding is being owrked on. ## Community Health: Core developers are active on regular basis. We increased number of security related reports. ----------------------------------------- Attachment AY: 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. ## Project Status: Current project status: Ongoing with moderate activity. Issues for the board: None. ## Membership Data: Apache NetBeans was founded 2019-04-17 (7 years ago) There are currently 83 committers and 66 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - Brad Walker was added to the PMC on 2026-01-26 - Haidu Bogdan was added as committer on 2026-01-29 ## Project Activity: - Apache NetBeans 29 was released on 2026-02-23. - Apache NetBeans 28 was released on 2025-11-10. ## Community Health: - The identification, engagement, and integration of new PMC members and committers has already borne fruit, as can be seen above, and we're working on bringing more in. - dev@netbeans.apache.org had a 33% decrease in traffic in the past quarter (103 emails compared to 153) - users@netbeans.apache.org had a 9% decrease in traffic in the past quarter (114 emails compared to 125): - For the 29 release: 19 contributors, 258 commits, and 3053 files changed. - For the 28 release: 34 contributors, 272 commits, and 2189 files changed. ----------------------------------------- Attachment AZ: 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. ## Project Status: Current project status: ongoing with moderate activity Issues for the board: none. ## Membership Data: Apache OFBiz was founded 2006-12-20 (19 years ago) There are currently 62 committers and 37 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 Sebastian Tschikin on 2024-09-18. - No new committers. Last addition was Florian Motteau on 2025-10-31. ## Project Activity: - Apache OFBiz 24.09.05 was released on January 20, 2026. The 24.09 branch continues to serve as the current stable release line. - Trademarks: The project is not aware of any trademark-related issues at this time. - To improve the handling of security disclosures and communication with both reporters and users, the project has prepared a document [1] describing the OFBiz "Security Model". This document aims to clarify how security is managed within the project and to support a more structured response process for future reports. [1] https://github.com/apache/ofbiz-framework/blob/trunk/SECURITY.md ## Community Health: Community engagement has remained steady during this quarter. The mailing lists have hosted constructive discussions and coordination around several areas, including improvements to documentation, deployment of official demos hosted by ASF Infra, ongoing framework refactoring, the introduction of new features, and the exploration of tools that support AI-assisted development. No new committers or PMC members were added during this reporting period, although the community continues to monitor several promising contributors as potential candidates for future roles. One individual who had been elected and invited to join the PMC in the previous quarter has not yet responded due to personal circumstances; therefore, the invitation has been placed on hold for the time being. ----------------------------------------- Attachment BA: Report from the Apache OpenDAL Project [Hao Ding] ## Description: OpenDAL is an Open Data Access Layer that enables seamless interaction with diverse storage services. Its development is guided by the vision "One Layer, All Storage" and the following principles: - Open Community - Solid Foundation - Fast Access - Object Storage First - Extensible Architecture ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache OpenDAL was founded on 2024-01-17 (a little over two years ago). There are currently 36 committers and 22 PMC members in the project. The committer-to-PMC ratio is roughly 1.6. Community changes, past quarter: - The project added one new committer during this quarter. - The PMC roster remained unchanged during this quarter. ## Project Activity: - No new core stable release was cut in this quarter; the latest stable release remains v0.55.0, released on 2025-11-24. - Development remained active, with 191 PRs merged from 47 authors between 2025-12-01 and 2026-03-10. - The project continued modularization work by splitting more services and layers into separate crates and repositories so components can evolve at different paces. - Major implementation work this quarter included reqsign v2 migrations across multiple services, continued .NET binding work, and new capabilities across Swift, S3, and local key-value backends. - Weekly "This Week in OpenDAL" discussions continued on GitHub Discussions alongside ongoing community Q&A. ## Community Health: ### Are there any risks to the sustainability of the project? OpenDAL remains healthy. While this quarter did not include a new core stable release, the project maintained strong development velocity and broad contributor participation. The project now has 36 committers and 22 PMC members, and recent work shows continued progress on modularization, integrations, and cross-language bindings. OpenDAL continues to be used by multiple database systems and infrastructure tools. The PMC's earlier decision to split more components into separate repositories is translating into concrete engineering work, which should improve long-term maintainability without reducing community cohesion. ### Is the PMC capable of responding to security issues and performing releases if needed? Yes. The PMC has an established release process, has demonstrated the ability to handle routine dependency maintenance, and continues to make coordinated technical changes across services, layers, and bindings. If needed, the PMC can organize releases and respond to security issues in a timely manner. ### Does the PMC need anything from the Foundation to improve on contributing to our mission of delivering software for the public good? No requests at this time. ----------------------------------------- Attachment BB: Report from the Apache OpenNLP Project [Jeffrey T. 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 ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache OpenNLP was founded 2012-02-14 (14 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: - No new PMC members. Last addition was Atita Arora on 2025-07-19. - No new committers. Last addition was Nishant Shrivastava on 2025-07-29. ## Project Activity: The project released the first milestone of a 3.0.0 release. This version brings a more modular approach to the project giving users more control over which components are included. ## Community Health: The community health remains consistent - mailing list activity is low but the project is healthy with a core group of active committers with development goals for the project. ----------------------------------------- Attachment BC: Report from the Apache OpenWebBeans Project [Mark Struberg] ----------------------------------------- Attachment BD: Report from the Apache Paimon Project [Jingsong Lee] ## Description: The mission of Apache Paimon is the creation and maintenance of software related to a unified lake storage to build dynamic tables for both stream and batch processing with big data compute engines, supporting high-speed data ingestion and real-time data query ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Paimon was founded 2024-03-20 (2 years ago) There are currently 25 committers and 14 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 Junhao Ye on 2025-02-25. - Hongbo Xiao was added as committer on 2026-02-24 ## Project Activity: Software development activity: - We are developing BTree index to significantly accelerate lake queries. - We are currently releasing version 1.4.0. - We discussed in dev: next step is 2.0, aimed at a multimodal data lake. ## Community Health: - dev mail list had a 1% increase (73 emails compared to 72). - user email list had a 7% increase (30 emails compared to 28). - issue mail list had 37% increase (2675 emails compared to 1947). - PR contributions continue to increase significantly. ----------------------------------------- Attachment BE: Report from the Apache Pekko Project [PJ Fanning] ## Description: The mission of Apache Pekko is the creation and maintenance of software related to a toolkit and an ecosystem for building highly concurrent, distributed, reactive and resilient applications for Java and Scala ## Project Status: Current project status: Community is still pretty active. Issues for the board: none. ## Membership Data: Apache Pekko was founded 2024-03-20 (2 years ago) There are currently 28 committers and 20 PMC members in this project. The Committer-to-PMC ratio is 7:5. Community changes, past quarter: - No new PMC members. Last addition was Domantas Petrauskas on 2025-11-20. - No new committers. Last addition was Domantas Petrauskas on 2024-12-19. ## Project Activity: 2.0 Milestones have been released and progress towards a full release is ongoing. Some bugs have reported so we plan some patch releases too. Akka releases become Apache licensed 3 years after release and some of these changes have become available for Pekko to copy. ## Community Health: Community engagement via mailing lists and GitHub Issues and Discussions is still pretty good. ----------------------------------------- Attachment BF: Report from the Apache Pig Project [Koji Noguchi] ----------------------------------------- Attachment BG: Report from the Apache Pinot Project [Kishore G] ----------------------------------------- Attachment BH: Report from the Apache PLC4X Project [César García] ----------------------------------------- Attachment BI: Report from the Apache Polaris Project [Jean-Baptiste Onofré] ## Description: The mission of Apache Polaris is the creation and maintenance of software related to a catalog for data lakes. It provides new levels of choice, flexibility and control over data, with full enterprise security and Apache Iceberg interoperability across a multitude of engines and infrastructure ## Project Status: Current project status: Ongoing (recently graduated) Issues for the board: None ## Membership Data: Apache Polaris was founded 2026-02-18 (20 days ago) There are currently 30 committers and 18 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members (project graduated recently). - Adam Christian was added as committer on 2026-03-07 - Adnan Hemani was added as committer on 2026-03-07 - Danica Fine was added as committer on 2026-02-27 ## Project Activity: * Releases: - Work began on Apache Polaris 1.4.0, the first release under the new TLP status. This release prep is a bit longer, as it needs updates on LICENSE/NOTICE, including new artifacts (like Python CLI). - Catalog Migrator 1.0.0 (RC2): A critical tool for migrating tables from Glue/Hive to Polaris entered its final voting stage in early March. - We will also consider releases for new tools soon (Polaris Console, Polaris MCP server, ...) * Technical Roadmap & Feature Development: Following the successful 1.3.0 release in mid-January, the development team shifted focus toward enterprise hardening and interoperability. - Scan Metrics Persistence: A major architectural effort is underway to integrate query scan metrics into the catalog, enabling better observability for downstream engines like Spark and Trino. - Credential Vending Enhancements: Significant PR activity has focused on refining AWS IAM AssumeRole flows and expanding support for storage-scoped credentials, reducing security overhead for multi-tenant data lakes. - Generic Table Stability: The "Generic Table" feature officially graduated from beta. This allows Polaris to manage metadata for Delta Lake and Apache Hudi tables alongside Iceberg, positioning it as a universal catalog. * Governance & Graduation Infrastructure The transition to a TLP required significant "Project Hygiene" to ensure compliance with the Apache Way: - Release Process Modernization: The community moved to a unified CI/CD pipeline, merging six disparate workflows into one. This has stabilized the build process and automated the generation of convenience binaries and Docker images. - Legal & Licensing: Conducted a comprehensive audit of all dependencies. Resolved a key legal blocker regarding third-party library nesting to ensure the upcoming 1.4.0 release (the first as a TLP) is fully compliant. * Ecosystem Integration - Engine Support: Verified compatibility and performance benchmarks for the latest versions of Apache Doris and StarRocks, which now use Polaris as their default external Iceberg catalog. - Community Engagement: Recorded high attendance at the February 19th community sync, where the transition to TLP was celebrated and the 2026 roadmap—including AI/ML metadata extensions—was first socialized. ## Community Health: * Governance Independence The project has achieved a high level of organizational maturity and is no longer reliant on its founding contributors. - Diverse PMC: The Project Management Committee (PMC) now includes 13 members representing seven different organizations, including Dremio, Snowflake, Databricks, Microsoft, Confluent, LanceDB, Red Panda. - Organic Leadership: Of the current PMC, 46% (6 members) were elected during the incubation period based on their merit and contributions, rather than being part of the initial donation. Similarly, 5 out of 8 current committers were promoted from within the community during incubation. * Engagement & Outreach Metrics (Feb – March 2026) The "graduation window" saw a spike in community engagement, particularly from new enterprise adopters. - Contributor Growth: The project surpassed the 100-contributor milestone in February. Since the end of January, 13 new individual contributors have had their first pull requests merged. - Mailing List Activity: The dev@ mailing list saw a 25% increase in traffic during February, focused on TLP transition logistics, the 1.4.0 roadmap, and the resolution of legal hygiene tasks. - Meetups: * Warsaw (Feb 18): A community-led meetup focused on Iceberg V4 and Polaris performance. * Redmond (Feb 26): Hosted by Microsoft, focusing on Polaris integration within the Azure/Fabric ecosystem. * Participation Quality Unlike many projects that see "drive-by" contributions, Polaris has seen a rise in "deep" technical participation: - Feature Design: Significant community-led design discussions occurred in February regarding Scan Metrics Persistence and ExternalCatalogFactory refactoring. - Integration Support: Third-party projects like Apache Doris, StarRocks, and Fivetran have integrated Polaris as their default Iceberg REST catalog, contributing back stability fixes and performance optimizations. * Documentation & Onboarding To ensure continued health, the community has prioritized "contributor experience": - Unified CI/CD: A major effort in February consolidated several disparate CI pipelines, reducing PR feedback loops and making it easier for new developers to verify their work. - Blog & Roadmap: The project launched several technical blogs in early 2026, including guides on policy-driven table maintenance and AI-native storage integration with LanceDB. ----------------------------------------- Attachment BJ: 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. ## Project Status: Current project status: ongoing with low activity Issues for the board: none ## Membership Data: Apache Portable Runtime (APR) was founded 2000-12-01 (25 years ago) There are currently 68 committers and 43 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 Daniel Sahlberg on 2025-08-07. - No new committers. Last addition was Daniel Sahlberg on 2025-08-07. ## Project Activity: Some discussions around using the OpenSSL checksum implementations. Last APR release was apr-1.7.6 on 2025-05-16. Last APR-UTIL release was apr-util-1.6.3 on 2024-02-01 ## Community Health: Activity was quiet this quarter, nothing unusual: - ~6 messages on bugs@ (All of them SPAM) - ~7 messages on dev@ ----------------------------------------- Attachment BK: 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. ## Project Status: - There are no issues requiring board attention at this time. ## Project Activity: - 4.1.3 was released on February 19th 2026 - 4.0.9 was released on February 19th 2026 - 3.0.16 was released on February 16th 2026 - Pulsar C++ releases: - 4.0.1 on January 28th 2026 - Pulsar Go releases: - 0.18.0 on December 14th 2025 - Pulsar Python releases: - 3.10.0 on February 5th 2026 - Pulsar NodeJS releases: - 1.16.0 on December 29th 2025 - Pulsar DotPulsar releases: - 5.2.2 release vote in progress (March 2026) - A discussion has been started on a potential redesign of the Java client API (Pulsar Cli ent API v5), to be shipped as a new separate module (pulsar-client-api-v5), starting from the next LTS version 5.0. - We continue to have a very high number of "Pulsar Improvement Proposal" getting submitted, discussed and voted by the community: PIP-455: Support Namespace Bundle Lookup and Topic Preloading PIP-456: Add subscriptionPrefixToSkipServerMarkerCheck Configuration to Allow RawReader to Read Marker Messages PIP-457: Remove Support for V1 Topic Names and V1 Admin API PIP-458: Add Async Resource List Filtering API to AuthorizationProvider PIP-459: Batch Status Summary and Filtered Listing for Pulsar Functions PIP-460: Scalable Topics PIP-461: Add Queued Latency Metrics for Offloader Executors - Pulsar has reached 712 contributors on the main Github repo (It was 712 contributors in the February 2026 report) ## 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. ## Membership Data: Apache Pulsar was founded 2018-09-18 (7 years ago) There are currently 85 committers and 47 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Cong Zhao was added to the PMC on 2025-09-18 - No new committers added this quarter. Last addition was Mingze Han on 2025-07-05. ## 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: - 7% decrease in traffic in the past quarter (14 emails compared to 15) - dev@pulsar.apache.org: - 16% decrease in traffic in the past quarter (182 emails compared to 216) ## Slack activity: - 10863 Members (10852 in the February 2026 report) - 137 Active monthly users (162 in the February 2026 report) ----------------------------------------- Attachment BL: Report from the Apache RocketMQ Project [Xiaorui Wang] ## Description: The mission of Apache RocketMQ is the creation and maintenance of software related to a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache RocketMQ was founded 2017-09-20 (8 years ago) There are currently 75 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - No new PMC members. Last addition was Zhouxiang Zhan on 2023-09-21. - No new committers. Last addition was Chaoyang Liu on 2024-08-10. ## Project Activity: Recent releases: - ROCKETMQ-5.4.0 was released on 2025-12-24. - ROCKETMQ-5.3.4 was released on 2025-11-26. ## Community Health: The Apache RocketMQ community continues to maintain steady development activity. Over the past quarter, contributors have remained active on GitHub with ongoing bug fixes, dependency upgrades, and stability improvements across the broker, client libraries, and related ecosystem components. Recent work has also focused on addressing security-related dependency updates and improving system reliability. Community collaboration remains consistent through GitHub discussions and mailing list communication. Issues and pull requests continue to be actively reviewed and resolved by maintainers and contributors. Overall, the RocketMQ community remains stable, with sustained participation from contributors and ongoing maintenance and improvement of the project and its ecosystem. ----------------------------------------- Attachment BM: Report from the Apache Royale Project [Andrew Wetmore] ## Description: The mission of Apache Royale is the creation and maintenance of software related to improving developer productivity in creating applications for wherever JavaScript runs (and other runtimes) ## Project Status: Current project status: The project is productive, and beginning work on the long-awaited 1.0.0 release. A number of conversations are in progress about possible future work. There are no issues for the Board at this time. ## Membership Data: Apache Royale was founded 2017-09-19 (8 years ago) There are currently 20 committers and 17 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 Alina Kazi on 2024-11-02. - No new committers. Last addition was María José Esteve on 2021-11-23. ## Project Activity: The project is showing a jump of activity on the dev@, issues@ and royale-builds@ mailing lists, partly related to efforts to complete certain enhancements before moving into work on creating the next release. In addition to improving the typedefs objects and bringing Royale into sync with the latest ActionScript3 improvements, there is work to make Apache Flex's Blaze Data Services tool more available to Royale users. ## Community Health: The project membership, though small, continues active and engaged. We have not mapped out a plan yet for trying to attract more participants from the ActionScript world. ----------------------------------------- Attachment BN: Report from the Apache SeaTunnel Project [Jun Gao] ## Description: The mission of Apache SeaTunnel is the creation and maintenance of software  related to a very easy-to-use ultra-high-performance distributed data  integration platform that supports cdc and batch synchronization of massive data ## Project Status: Current project status: Health Issues for the board: There are no Board-level issues at this time. ## Membership Data: Apache SeaTunnel was founded 2023-05-17 (2 years ago) There are currently 38 committers and 22 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 Naijie Liu on 2025-07-08. By the way, a new PMC member is been voting. - Xiaochen Zhou was added as committer on 2025-12-20 ## Project Activity: - 2.3.13 is being released - 2.3.12 was released on 2025-09-12 - 2.3.11 was released on 2025-05-21 ## Community Health: - We have held one community online Meetups in last quarter. - dev@seatunnel.apache.org had a 5% increase in traffic in the past quarter Overall community health is good. We have been performing extensive outreach to related projects, in order to attract new contributors, and are seeing a steady influx of new people wishing to join and contribute, both programming- and documentation. ----------------------------------------- Attachment BO: Report from the Apache ServiceComb Project [Zhangjian He] Hi Team, Here is the board report of ServiceComb for February 2026. Please let me know if you have any questions or concerns about the report. ## Description: The mission of Apache ServiceComb is the creation and maintenance of software related to a microservice framework that provides a set of tools and components to make development and deployment of cloud applications easier. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache ServiceComb was founded 2018-10-17 (8 years ago) There are currently 38 committers and 22 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 Cheng Youling on 2024-10-12. - No new committers. Last addition was Zhangjian He on 2025-01-28. ## Project Activity: Since version 2.8.28, the project has maintained an active release cycle with significant updates to both the 2.8.x (LTS) and 2.9.x branches. Key releases include: - **ServiceComb Java Chassis 2.9.3** released on 2026-01-31. - Upgraded Spring Boot dependencies to 3.4.9. - Upgraded Netty and Vert.x versions for improved performance and security. - Fixed an issue where service instances could not be immediately pulled upon registry changes. - **ServiceComb Java Chassis 2.8.30** released on 2026-01-31. - Upgraded Netty and Vert.x versions. - Fixed the service instance pulling delay issue in the registry center. - **ServiceComb Java Chassis 2.8.29** released on 2025-11-25. - Upgraded Tomcat embed core to 9.0.108. - Fixed microservice registration issues when enabling RBAC authentication in dual-engine disaster recovery scenarios. The community continues to focus on stability, dependency upgrades, and fixing critical issues in distributed scenarios. ## Community Health: Overall, community health is good. The project has successfully delivered 3 releases since version 2.8.28, addressing key technical debts and user-reported bugs. We are seeing consistent contributions from existing committers, particularly in maintaining the LTS branch and upgrading core dependencies. Plans are underway to evaluate new PMC candidates to further strengthen community governance. ----------------------------------------- Attachment BP: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ----------------------------------------- Attachment BQ: Report from the Apache Shiro Project [Lenny Primak] ## Description: The mission of Shiro is the creation and maintenance of software related to Powerful and easy-to-use application security framework ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: None at this time ## Membership Data: Apache Shiro was founded 2010-09-21 (15 years ago) There are currently 16 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Lenny Primak on 2022-12-04. - Steinar Bang was added as committer on 2026-01-12 ## Project Activity: The Shiro team has been actively working on Shiro 3.x, culminating with a release of 3.0.0-alpha-1 at the end of February 2026 We also released Shiro 2.0.6 on 11/05/2025 and Shiro 2.1.0 on 2/7/2026 We also closed 2 security issues and published 2 CVEs ## Community Health: Mailing list traffic is low. We opened up GitHub Discussions at the end of 2025. We achieved merging all PRs and closing many issues in the first part of 2026. ----------------------------------------- Attachment BR: 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 ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache SINGA was founded 2019-10-16 (5 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: The team has released SINGA 5.0.0 on 14 April 2025. In the past quarter, the community is working on the following features/changes: -- Prepare the artifacts and documentations for SINGA 5.1.0 release. -- Add the implementations for more types of autograd models, e.g., convolutional, generative, etc. -- Add the implementations for more advanced attention mechanisms. -- Update the encoder layers for the transformer model. -- Add the implementations for unsupervised models in the peft example. ## Community Health: According to the statistics, there are more commits and issues resolved in the Github, which shows that the community is active in the development. ----------------------------------------- Attachment BS: Report from the Apache Sling Project [Robert Munteanu] ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Project Status: Current project status: Ongoing. Issues for the board: none. ## Membership Data: Apache Sling was founded 2009-06-17 (17 years ago) There are currently 53 committers and 30 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 Julian Reschke on 2024-10-22. - No new committers. Last addition was Nicola Scendoni on 2025-11-10. ## Project Activity: We released version 13 of our sample application, the Sling Starter, on January 17th, 2025. The Sling Starter 14 release process is underway and is expected to complete in by mid-March. In the meantime individual modules are being developed and released, with 29 releases for this reporting period. ## Community Health: Community health is pretty good and contributions from various individuals continue. ----------------------------------------- Attachment BT: Report from the Apache SpamAssassin Project [Giovanni Bechis] ## Description: The mission of SpamAssassin is the creation and maintenance of software related to Mail filter to identify spam ## Project Status: Project state: Ongoing with low to moderate activity Apache SpamAssassin 4.0.2 has been released on 30 August 2025, primary focus for development is now ongoing maintenance bug fixes to the latest release, 4.0.2. We also started developing new plugins. ## Membership Data: Apache SpamAssassin was founded 2004-06-01 (22 years ago) There are currently 32 committers and 13 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 Kent Oyer on 2024-11-09. - No new committers. Last addition was Kent Oyer on 2024-03-28. ## Project Activity: Last release was Apache SpamAssassin version 4.0.2 on 30 August 2025. We maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. ## Community Health: Maintenance of our rule update infrastructure, developer community submissions for rule update testing, and our dev and user mailing lists, are continuing smoothly. ----------------------------------------- Attachment BU: Report from the Apache Storm Project [Richard Zowalla] ## Description: The mission of Storm is the creation and maintenance of software related to Distributed, real-time computation system ## Project Status: Current project status: Ongoing (reactivated) Issues for the board: none ## Membership Data: Apache Storm was founded 2014-09-17 (11 years ago) There are currently 48 committers and 47 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 Purshotam Shah on 2025-05-21. - No new committers. Last addition was Purshotam Shah on 2024-10-08. ## Project Activity: Overall activity remains low, with the project continuing in maintenance mode. Most progress this quarter has been focused on dependency updates and similar housekeeping tasks, along with targeted bug fixes as issues are reported. Encouragingly, we received a few external Pull Requests from the community, reflecting that Storm continues to see active use. A vote for a new release is currently ongoing and should be closed soon. Recent releases: 2.8.3 was released on 2025-11-02. 2.8.2 was released on 2025-07-26. 2.8.1 was released on 2025-06-03. ## Community Health: Community engagement is modest but stable. A few long-time contributors continue to monitor the mailing list. The external Pull Requests received this quarter are a positive signal, and we hope this external interest translates into sustained contributor involvement going forward, so we can add new people as committers and/or PMC members. ----------------------------------------- Attachment BV: Report from the Apache StreamPark Project [Huajie Wang] ## Description: The mission of StreamPark is a streaming application development framework and cloud-native real-time computing platform. Its vision is make stream processing easier. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache StreamPark was founded 2025-01-23(a year ago) There are currently 8 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 2:3. Community changes, past quarter: - No new PMC members, Last addition was Jie Cheng on 2024-08-06. - No new committers were added. - New contributor +2 ## Project Activity: - 3 CVEs have been confirmed - Plan to release a CVE vulnerability fix version ----------------------------------------- Attachment BW: Report from the Apache Synapse Project [Isuru Udana] ----------------------------------------- Attachment BX: Report from the Apache Teaclave Project [Zhaofeng Chen] # Apache Teaclave Board Report - March 2026 ## Description Apache Teaclave provides SDKs for building memory-safe applications on Trusted Execution Environments (TEEs). ## Project Status **Status:** Ongoing, with moderate activity. Apache Teaclave graduated as a Top-Level Project on August 21, 2025. This quarter, the community released `teaclave-trustzone-sdk v0.8.0` by introducing the `cargo-optee` build tool, enabling stable Rust support, improving build compatibility, and keeping pace with upstream OP-TEE changes. ## Summary of Project Health and Status Since the last report, Apache Teaclave has maintained steady progress with a new release, improved developer tooling, and growing community engagement. The v0.8.0 release shipped on schedule with contributions from both existing committers and new contributors. The mailing list saw increased activity driven by the release cycle and substantive code review discussions. Current focus areas include simplifying the TEE development experience through better Cargo tooling and strengthening memory-safety patterns in the SDK. ## Issues for Board Attention There are no Board-level issues at this time. ## Recent Releases - 2026-01-26: Teaclave TrustZone SDK v0.8.0 ## Project Activity ### Development Activity - Introduced `cargo-optee`, a Cargo subcommand that simplifies building and running TEE trusted applications with minimal setup. - Enabled stable Rust toolchain support and improved build compatibility with optional static TEEC linkage. - Approximately 30 commits merged in the past three months. ### Community Activity - Developer mailing list: increased activity (~128 messages across ~39 threads in the past three months). - New Release Manager completed the latest release process. - Two first-time contributors joined with merged PRs, representing potential future committers. ## Current Plans - **Short term (next quarter):** - Complete next quarterly release of Teaclave TrustZone SDK, aligned with OP-TEE's release schedule. - Finalize safe buffer access API for volatile ParamMemref interactions. - Continue enhancing `cargo-optee` with toolchain management and onboarding improvements. - **Medium term:** - Open source additional real-world SDK use cases. - Maintain alignment with OP-TEE's quarterly release cadence. ## Community Changes - Current: 16 PMC members, 7 committers; no new additions since the last report. - PMC membership represents a healthy diversity of organizations. ## Project Branding - No branding issues. - Website and download pages comply with Apache branding requirements. ## Legal Issues - No legal issues to report. ## Infrastructure - No infrastructure concerns at this time. ----------------------------------------- Attachment BY: Report from the Apache Tomcat Project [Christopher Schultz] ## Description: Apache Tomcat® software is an open source implementation of the Jakarta Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket, Jakarta Annotations and Jakarta Authentication specifications. These specifications are part of the Jakarta EE platform. The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10 and later implement specifications developed as part of Jakarta EE. Tomcat 9 and earlier implement specifications developed as part of Java EE. ## Project Status: The Tomcat project is ongoing with moderate activity, having a strong and active community of both users and committers. We maintain 3 major release version numbers, and have a release cadence of approximately one release per major-version per month. Issues for the board: none ## Membership Data: Apache Tomcat was founded 2005-05-17 (21 years ago) There are currently 50 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 Dimitris Soumis on 2025-02-18. - No new committers. Last addition was John Engebretson on 2025-02-05. ## Project Activity: * Tomcat Native 2.1.14 was released on 2026-03-10 * Tomcat Native 1.3.7 was released on 2026-03-10 * Tomcat Native 2.1.13 was released on 2026-02-11 * Tomcat Native 1.3.6 was released on 2026-02-11 * Tomcat 10.1.52 was released on 2026-01-27. * Tomcat 11.0.18 was released on 2026-01-26. * Tomcat 9.0.115 was released on 2026-01-23. * Tomcat 11.1.15 was released on 2025-12-08. * Tomcat 10.1.50 was released on 2025-12-08. * Tomcat 9.0.113 was released on 2025-12-07. We have secured a grant from the HeroDevs' Open Source Sustainability Fund which will be a directed donation to the ASF. We expect to use this grant to fund additional "Security Day" events such as the one we hosted after the CoC Conference in Bratislava. ## Community Health: Continued healthy activity across multiple components and responsiveness on both dev and user lists. ----------------------------------------- Attachment BZ: 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 ## Project Status: Current project status: Ongoing Issues for the board: N/A ## Membership Data: Apache TVM was founded 2020-11-17 (5 years ago) There are currently 83 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 3:1. Community changes, past quarter: - No new PMC members. Last addition was Yong Wu on 2025-09-11. - Guan-Ming Chiu was added as committer on 2026-01-27 ## Project Activity: - tvm 0.1.5 was released on 2025-12-08. - tvm-ffi v0.1.4 was released on 2025-11-30. The community continues to bring improvement in directions of frontend support, backend enablement, and FFI conventions. - Robustify relax support - Improved runtime to reduce host overheads in Metal and WebGPU settings. - Improved the low-level codegen infrastructure. - tvm-ffi module starts to stabilize and enable adoptions an open ABI and FFI for machine learning systems projects. ## Community Health: We see continued contributions to the project, with about 100 commits monthly in the past quarter. AI’s capability is also getting stronger and we see AI reviews to help improve the review process. We also see modularized components like tvm-ffi start to bring in community interest. We likely expected to see more modular components. As we are in the age of generative AI. We start to see growing interest in new models like supporting LLMs as well as integrating with existing ecosystems. ----------------------------------------- Attachment CA: 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. ## Project Status: Current project status: Ongoing (dormant) Issues for the board: none ## Membership Data: Apache UIMA was founded 2010-03-17 (16 years ago) There are currently 25 committers and 17 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 Pablo Duboue on 2023-03-07. - No new committers. Last addition was Pablo Duboue on 2023-03-06. ## Project Activity: uima-ruta-3.5.1 was released on 2025-10-13. uimaj-3.6.1 was released on 2025-10-01. ## Community Health: There has not really been any particularly notable or significant activity to report. ----------------------------------------- Attachment CB: 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 ## Project Status: Current project status: Ongoing, moderate activity Issues for the board: none ## Membership Data: Apache Unomi was founded 2019-02-20 (7 years ago) There are currently 17 committers and 8 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 Jonathan Sinovassin-Naïk on 2024-11-25. - No new committers. Last addition was Jerome Blanchard on 2025-09-13. ## Project Activity: Work this quarter focused on a mix of user-facing improvements and core reliability hardening. The project website was significantly modernized in unomi-site, with improved structure, accessibility/SEO, and ASF compliance follow-up. On the core unomi codebase, recent changes targeted operational quality: startup/logging fixes, healthcheck behavior, REST API error handling, and test/build reliability improvements. JIRA activity also reflects a practical stabilization cycle: several reports around invalid payload handling, rule/segment validation, and startup/runtime behavior were raised and actively worked on. In parallel, the team continues the staged integration of the 3.x workstream by splitting a large body of changes into smaller, reviewable PRs, with tooling support to keep the process manageable. ## Community Health: The community remains engaged and responsive. Most visible mailing-list traffic is development workflow traffic (commits/PR/JIRA notifications), while substantive discussion threads this quarter centered on the website modernization proposal and regular project sync/reporting topics. User/support interaction continues to happen more through JIRA and Slack than through the users mailing list, with new reports and feedback still arriving and being handled. Overall, collaboration and throughput remain healthy, with no governance or community risk requiring board attention. ----------------------------------------- Attachment CC: 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. ## Project Status: Current project status: Dormant Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache VCL was founded 2012-06-19 (14 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: 2025-03-24 - no activity in the last quarter ## Community Health: The same as the last report - the project is still being used by various organizations, and we do have PMC members watching things. There is some good development going on at the primary contributing organization that we hope to be able to contribute in a few months. I'd really like to get some of that contributed. It's just hard to make the time to do so. ----------------------------------------- Attachment CD: 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. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Wicket was founded 2007-06-20 (19 years ago) There are currently 35 committers and 34 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 Matt Pavlovich on 2025-01-27. - No new committers. Last addition was Matt Pavlovich on 2025-01-27. ## Project Activity: Last month we started working on the next main release (Wicket 11) using our master branch and applying the first main dependencies update for the project (i.e. JUnit 6 and Spring 7). The minimum Java version required for Wicket 11 will be Java 21. We also received through the Apache Security Team a security vulnerability report about a session fixation vulnerability of the framework. The fix for this problem is quite simple and we will include it in the next versions of Wicket 10 and 9. Recent releases are: 10.8.0 released on 2025-12-21. 9.22.0 released on 2025-12-15. 10.7.0 released on 2025-09-30. ## Community Health: Community is stable and healthy and we still receive PR to improve the framework. Recently Dutch company Squins got in contact with us because they are organizing a Wicket User Day on the first of April in Dordrecht, although the event could be postponed to a later date. If so, some of your PMC members could take part to the event. ----------------------------------------- Attachment CE: 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. ## Project Status: Current project status: Ongoing (low activity). All sub-projects are in bug fix mode and maintenance mode. Only Xerces-J has had recent activity. Issues for the board: None. ## Membership Data: Apache Xerces was founded 2005-02-22 (21 years ago) There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members. Last addition was Elliotte Rusty Harold on 2025-06-19. - No new committers. Last addition was Elliotte Rusty Harold on 2025-06-20. ## Project Activity: The focus for Xerces-J and Xerces-C continues to be maintenance. No new features are in development. 7 PRs were merged for Xerces-J since December 2025, mostly representing minor enhancements and fixes to Javadoc and other documentation. One of these contributors is not a committer yet. There has been some discussion on the mailing lists about having a new Xerces-J release at the request of the Xalan community. This was the catalyst for getting some of the recent PRs reviewed and merged. There was no visible activity on Xerces-C or any of the other Xerces subprojects since the previous report. No new releases since the previous report. The latest release is Xerces-J 2.12.2 (January 24th, 2022). The latest release is Xerces-C 3.3.0 (October 14th, 2024). ## Community Health: Our project for more than the last decade has had a handful of dedicated active committers. Some less active PMC members continue to monitor the project and respond to queries on security issues as needed. The recent discussion on having a new Xerces-J release shows that we need more volunteers that take action and to recruit new committers such as the recently active contributor to Xerces-J. It may be time for a check up on the health of Xerces-C. The PMC members that contribute to Xerces-C have been silent for awhile though there has been nothing for them to respond to. ----------------------------------------- Attachment CF: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache Yetus was founded 2015-09-15 (10 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: Not much to report. We are probably due for another release soon to at least update the Github actions with latest and greatest. ## Community Health: A handful of commits over the past quarter to deal with some issues that some of the projects are having and to take advantage of some new Github functionality. ----------------------------------------- Attachment CG: Report from the Apache ZooKeeper Project [Flavio 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. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache ZooKeeper was founded 2010-11-17 (15 years ago) There are currently 34 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - Kezhu Wang was added to the PMC on 2026-01-19 - No new committers. Last addition was Christopher Tubbs on 2025-11-18. ## Project Activity: Recent releases: 3.9.5 was released on 2026-03-05. 3.8.6 was released on 2026-02-11. ## Community Health: It has been a good quarter for the project with a couple of maintenance releases, a new PMC member and the community health score of 9.6 indicates a good amount of activity. Thanks community! https://reporter.apache.org/wizard/statistics?zookeeper ------------------------------------------------------ End of minutes for the March 18, 2026 board meeting.