The Apache Software Foundation Board of Directors Meeting Minutes January 21, 2026 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:08 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-01-21T22: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: Jim Jagielski Zili Chen Greg Stein Rich Bowen Shane Curcuru Justin Mclean Sander Striker - parted :31 Jean-Baptiste Onofré - parted :32 Kanchana Pradeepika Welagedara Directors Absent: none Executive Officers Present: Craig McClanahan Ruth Suehle Matt Sicker Craig L Russell Executive Officers Absent: Jeff Jirsa Guests: Daniel Gruno Andrew Wetmore Paul King Alin Jerpelea Thomas Neidhart Dave Fisher Jarek Potiuk Melissa Logan Brian Proffitt Whitney P True Julien Le Dem Keith McKenna - joined :24 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of December 17, 2025 See: board_minutes_2025_12_17.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander Striker] My focus has been on refamiliarizing myself with the current Members Meeting process. The 2026 meeting structure has been created and messages have been scheduled. I observe that we have more projects that have not reported for multiple months. The Members Meeting and the Code of Conduct are going to be my focus for the upcoming month. B. President [Ruth Suehle] Next week I will be in Brussels for Open Source Week events, again representing ASF on a panel at the EU Open Policy Summit, as well as in a talk and a panel at FOSDEM. There's a lot of really interesting stuff happening in all our offices, but I think the individual officer reports cover all that pretty well. Apologies for my report being so late. Additionally, please see Attachments 1 through 11. C. Treasurer [Craig McClanahan] Normal operations continue. In particular, Lewis and I are collaborating on more detailed reports for the transactions related to the areas for which officers have budgetary responsibility. D. Secretary [Matt Sicker] In December, the secretary received 42 ICLAs and 1 CCLA. E. Executive Vice President [Jeff Jirsa] Code of Conduct email to outside counsel delayed from December to January due to concerns with pro-bono limit; VP Legal indicated it would send this week. Progress remains slow. EVP encourages the board to add additional humans to push. F. Vice Chair [Rich Bowen] Nothing to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Rich] See Attachment 12 B. Apache Legal Affairs Committee [Roman Shaposhnik / Kanchana] See Attachment 13 C. Apache Security Team Project [Mark J. Cox / Shane] See Attachment 14 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Ambari [striker] # Arrow [gstein] # CarbonData [jbonofre] # Dubbo [striker] # Fory [gstein] # HBase [tison] # Legal Affairs [kanchana] # Libcloud [striker] # RocketMQ [striker] # Rya [kanchana] # ServiceMix [jbonofre] # Velocity [jbonofre] # Wayang [rbowen] # Web Services [jbonofre, kanchana] # XML Graphics [striker] A. Apache Accumulo Project [Ed Coleman / Zili] No report was submitted. B. Apache ActiveMQ Project [Christopher L. Shannon / JB] See Attachment B C. Apache Airavata Project [Suresh Marru / Justin] No report was submitted. D. Apache Ambari Project [Brahma Reddy Battula / Jim] No report was submitted. @Jim: pursue roll call E. Apache Answer Project [Ning Qi / Greg] See Attachment E F. Apache APISIX Project [Ming Wen / Sander] No report was submitted. G. Apache Aries Project [Christian Schneider / Justin] See Attachment G H. Apache Arrow Project [Antoine Pitrou / Sander] See Attachment H I. Apache Artemis Project [Christopher L. Shannon / JB] See Attachment I J. Apache AsterixDB Project [Ian Maxon / Kanchana] See Attachment J K. Apache Attic Project [Hervé Boutemy / Jim] See Attachment K L. Apache Avro Project [Ryan Skraba / Zili] No report was submitted. M. Apache Beam Project [Kenneth Knowles / Greg] No report was submitted. N. Apache bRPC Project [James Ge / Rich] See Attachment N O. Apache BuildStream Project [Abderrahim Kitouni / Shane] See Attachment O P. Apache Calcite Project [Mihai Budiu / Sander] See Attachment P Q. Apache CarbonData Project [Jacky Li / JB] No report was submitted. R. Apache Causeway Project [Jörg Rade / Shane] See Attachment R S. Apache Celix Project [Pepijn Noltes / Kanchana] See Attachment S T. Apache CXF Project [Andriy Redko / Jim] See Attachment T U. Apache DataFu Project [Eyal Allweil / Justin] See Attachment U V. Apache DB Project [Bryan Pendleton / Zili] See Attachment V W. Apache Directory Project [Shawn McKinney / Rich] See Attachment W X. Apache DolphinScheduler Project [Lidong Dai / JB] No report was submitted. Y. Apache Druid Project [Abhishek Agarwal / Greg] No report was submitted. Z. Apache Dubbo Project [Jun Liu / Sander] No report was submitted. @Rich: suggest PMC chair rotation AA. Apache Fineract Project [James Dailey / Shane] See Attachment AA AB. Apache Flagon Project [Joshua Poore / Jim] See Attachment AB AC. Apache Fory Project [Chaokun Yang / Kanchana] See Attachment AC AD. Apache Geronimo Project [Jean-Louis Monteiro / JB] No report was submitted. AE. Apache Gump Project [Stefan Bodewig / Greg] See Attachment AE AF. Apache Hadoop Project [Xiaoqiao He / Rich] See Attachment AF AG. Apache HBase Project [Duo Zhang / Justin] See Attachment AG AH. Apache HertzBeat Project [Chao Gong / Zili] See Attachment AH AI. Apache Incubator Project [Justin Mclean / Justin] See Attachment AI AJ. Apache InLong Project [Charles Zhang / Kanchana] No report was submitted. AK. Apache James Project [Benoit Tellier / Rich] See Attachment AK AL. Apache Jena Project [Andy Seaborne / Greg] See Attachment AL AM. Apache JMeter Project [Bruno (Milamber) Demion / Jim] See Attachment AM AN. Apache Johnzon Project [Jean-Louis Monteiro / Sander] No report was submitted. AO. Apache JSPWiki Project [Juan Pablo Santos / Justin] See Attachment AO AP. Apache Kudu Project [Andrew Wong / Zili] See Attachment AP AQ. Apache Libcloud Project [Tomaž Muraus / Zili] No report was submitted. AR. Apache Lucene.Net Project [Shad Storhaug / JB] No report was submitted. AS. Apache MADlib Project [Ed Espino / Justin] No report was submitted. AT. Apache Mahout Project [Shannon Quinn / Shane] See Attachment AT AU. Apache Maven Project [Hervé Boutemy / Shane] See Attachment AU AV. Apache MINA Project [Thomas Wolf / Justin] See Attachment AV AW. Apache MyFaces Project [Bernd Bohmann / Shane] See Attachment AW AX. Apache NiFi Project [David Handermann / Sander] See Attachment AX AY. Apache Nutch Project [Sebastian Nagel / Sander] See Attachment AY AZ. Apache NuttX Project [Alin Jerpelea / Zili] See Attachment AZ BA. Apache OpenJPA Project [Mark Struberg / Greg] No report was submitted. BB. Apache OpenMeetings Project [Maxim Solodovnik / JB] See Attachment BB BC. Apache OpenOffice Project [Keith McKenna / Rich] See Attachment BC BD. Apache ORC Project [William Hyun / Kanchana] No report was submitted. BE. Apache Parquet Project [Julien Le Dem / Jim] See Attachment BE BF. Apache PDFBox Project [Andreas Lehmkühler / Rich] See Attachment BF BG. Apache Petri Project [Greg Stein / Greg] No report was submitted. BH. Apache PLC4X Project [César García / Justin] See Attachment BH BI. Apache Portable Runtime (APR) Project [Yann Ylavic / Sander] No report was submitted. BJ. Apache Pulsar Project [Matteo Merli / Kanchana] No report was submitted. BK. Apache Ranger Project [Selvamohan Neethiraj / JB] See Attachment BK BL. Apache Ratis Project [Tsz-wo Sze / Jim] See Attachment BL BM. Apache RocketMQ Project [Xiaorui Wang / Greg] No report was submitted. @Greg: pursue roll call BN. Apache Royale Project [Yishay Weiss / Shane] No report was submitted. BO. Apache Rya Project [Adina Crainiceanu / Zili] See Attachment BO @Kanchana: pursue roll call BP. Apache Samza Project [Jagadish Venkatraman / Jim] See Attachment BP BQ. Apache ServiceMix Project [Krzysztof Sobkowiak / Rich] No report was submitted. BR. Apache SINGA Project [Wang Wei / Kanchana] See Attachment BR BS. Apache SkyWalking Project [Sheng Wu / Zili] See Attachment BS BT. Apache Steve Project [Greg Stein / Greg] No report was submitted. BU. Apache StreamPark Project [Huajie Wang / Greg] See Attachment BU BV. Apache Struts Project [René Gielen / JB] See Attachment BV BW. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Sander] See Attachment BW BX. Apache Tcl Project [Georgios Petasis / Justin] No report was submitted. BY. Apache Tez Project [László Bodor / Shane] See Attachment BY BZ. Apache Thrift Project [Jens Geyer / Justin] See Attachment BZ CA. Apache Tika Project [Tim Allison / Rich] See Attachment CA CB. Apache TinkerPop Project [Kelvin Lawrence / Zili] See Attachment CB CC. Apache Traffic Server Project [Bryan Call / Greg] See Attachment CC CD. Apache Training Project [Justin Mclean / Justin] See Attachment CD CE. Apache Velocity Project [Nathan Bubna / JB] See Attachment CE @JB: follow up about Attic CF. Apache Wayang Project [Zoi Kaoudi / Jim] See Attachment CF @Jim: explain trademark process CG. Apache Web Services Project [Daniel Kulp / Kanchana] No report was submitted. @Kanchana: pursue roll call or attic CH. Apache XML Graphics Project [Clay Leeds / JB] No report was submitted. @JB: pursue roll call CI. Apache Zeppelin Project [Jongyoul Lee / Shane] See Attachment CI Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache HugeGraph Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a convenient, efficient, and adaptable graph database compatible with the Apache TinkerPop3 framework and the Gremlin query language. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache HugeGraph Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache HugeGraph be and hereby is responsible for the creation and maintenance of software related to a convenient, efficient, and adaptable graph database compatible with the Apache TinkerPop3 framework and the Gremlin query language; and be it further RESOLVED, that the office of "Vice President, Apache HugeGraph" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache HugeGraph Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache HugeGraph Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache HugeGraph Project: * Lidong Dai * Xiangdong Huang * Yu Li * Cong Zhao * Imba Jin * Jermy Li * NingRui Li * Juan Pan * Yan Zhang * Willem Ning Jiang * Yuchen Ding * Shiming Zhang NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jermy Li be appointed to the office of Vice President, Apache HugeGraph, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. RESOLVED, that the Apache HugeGraph Project be and hereby is tasked with the migration and rationalization of the Apache Incubator HugeGraph podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator HugeGraph podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7A, Establish the Apache HugeGraph Project, was approved by Unanimous Vote of the directors present. B. Change the Apache DB Project Chair WHEREAS, the Board of Directors heretofore appointed Bryan Pendleton (bpendleton) to the office of Vice President, Apache DB, and WHEREAS, the Board of Directors is in receipt of the resignation of Bryan Pendleton from the office of Vice President, Apache DB, and WHEREAS, the Project Management Committee of the Apache DB project has chosen by vote to recommend Jeffery Painter (painter) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Bryan Pendleton is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache DB, and BE IT FURTHER RESOLVED, that Jeffery Painter be and hereby is appointed to the office of Vice President, Apache DB, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache DB Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache Lucene Project Chair WHEREAS, the Board of Directors heretofore appointed Dawid Weiss (dweiss) to the office of Vice President, Apache Lucene, and WHEREAS, the Board of Directors is in receipt of the resignation of Dawid Weiss from the office of Vice President, Apache Lucene, and WHEREAS, the Project Management Committee of the Apache Lucene project has chosen by vote to recommend Ben Trent (benwtrent) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Dawid Weiss is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Lucene, and BE IT FURTHER RESOLVED, that Ben Trent be and hereby is appointed to the office of Vice President, Apache Lucene, 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 7C, Change the Apache Lucene Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * JB: pursue potential Attic for CarbonData [ CarbonData 2025-08-20 ] Status: I started a discussion: https://lists.apache.org/thread/jf385z0yw00kfjqgg58yfwg3s30sz6k5 * JB: pursue a roll call for Velocity [ Velocity 2025-08-20 ] Status: https://lists.apache.org/thread/j6yw7w18j22yx1qdkj4z4xgrf6961blw * Zili: ask Doris PMC to address issues raised by Brand Management in next quarterly report [ Doris 2025-10-15 ] Status: Done. See https://lists.apache.org/thread/md36fnsfdxsbs3jqtxf8c30wy5v2bbl6. Waiting on Doris PMC report and follow up. * Justin: pursue a roll call for MADlib [ MADlib 2025-10-15 ] Status: Completed Only 1 active PMC member. Informed of the next steps, most likely retirement. * Sander: discuss Policy for Inactive Committers with project PMC [ NiFi 2025-10-15 ] Status: https://lists.apache.org/thread/wnph5t6xn9rts4smhtd2gmfpjktyqjv8 * Zili: follow up about Attic [ Libcloud 2025-11-19 ] Status: See https://lists.apache.org/thread/mlgbmoqdr2hmnj8nxl2f10bbol05hsns * Shane: follow up with Mahout about professional status [ Mahout 2025-11-19 ] Status: * Justin: discuss path to Attic [ ManifoldCF 2025-11-19 ] Status: Completed. Email sent. * Greg: talk to Pinot PMC about communication channels [ Pinot 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Rich: follow up about private communications [ SIS 2025-11-19 ] Status: Done * Greg: 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: follow up with board about PyPI policy [ TsFile 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Greg: pursure a roll call for BVal [ BVal 2025-12-17 ] Status: * Zili: follow up on roll call for cTAKES [ cTAKES 2025-12-17 ] Status: Done. Roll call passed. I counted from https://lists.apache.org/thread/bvrmcz1grvnys5wz1dyf2l2cz4wx2wtg Johns, Dennis +1 Murali Minnah +1 Finan, Sean +1 * Justin: follow up on license and trademark issues [ IoTDB 2025-12-17 ] Status: Completed. Email sent. * Jim: followup regarding possible MOU for FriendsOfNetBeans [ NetBeans 2025-12-17 ] Status: * Justin: clarify that their earlier report was approved [ Teaclave 2025-12-17 ] Status: Done. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:36 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period December 2025 * ISSUES FOR THE BOARD None * OPERATIONS Responded to the following queries, liaising with projects as required: - approved one request to use multiple project logos within the dashboard of an external product - added two events to the events calendar - I have requested an up to date list of all registered marks from counsel with a view to updating the list on the ASF website - Requested additional information for PNS-249 (LIVY) - Approved CALDERA is a project name (with Board approval) - provided advice regarding the "original creators" language * REGISTRATIONS Continued to work on the transfer of the HUGEGRAPH marks to the ASF. * INFRINGEMENTS Provided advice regarding a potential infringement of our APACHE mark. Provided support to AIRFLOW as they addressed issues with an external blog article. Provided advice regarding a potential infringement of our MAVEN mark. Provided advice to FLINK regarding a potential infringement. AIRFLOW identified and addressed an issue with an upcoming book. No progress regarding a potential infringement of PDFBOX. No progress regarding a site with a possible infringement of APISIX. No update on the formal trademark infringement complaint submitted to GitHub regarding an NPM package on behalf of the logging PMC. No progress this month regarding the downstream vendor with multiple infringements of ASF marks. No further progress for IOTDB. No progress for The KAFKA PMC in addressing a potential infringement of KAFKA. No progress working with the XMLGRAPHICS PMC to resolve a potential infringement of FOP. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: we are in the final stages of onboarding a corporate contributor that will be recognized as a Bronze Sponsor. b —Renewals: we continue to actively pursue and advance Sponsor renewals and retention. Over the course of 2025 we observed growing Sponsor challenges with reduced/reallocated budgets and staffing layoffs, coupled with protracted decision-making processes. c —Payments: 1 —New: we did not receive any new Sponsor payments during this timeframe. 2 —Received: we received Sponsorship renewal payments from one Platinum, two Silver, and one Bronze Sponsor. We also received renewal payments from two Silver Targeted Sponsors. 3 —Incoming: we await renewal payments from one Platinum, three Gold, one Silver, and one Bronze Sponsor. We also await a Gold Targeted Sponsorship payment. 2) Targeted Sponsors: we are in the final stages of onboarding a new Gold Targeted Sponsor. 3) Sponsor Relations: we worked with Marketing & Publicity to promote ASF end-of-year fundraising programs in tandem with the Giving Tuesday global day of giving on 2 December. We published the final blog post in our 4-part series on ways to support the ASF, and also contributed the "Continued Growth Requires Continued Support" entry for the ASF 2025 Year in Review post. We held our Q4 call with Gold and Platinum Sponsors on 10 December and featured the ASF Tooling Initiative, with presentations and participation by VP Tooling and Initiative seed funder Alpha Omega. We continue our outreach efforts to encourage those needing to deploy end-of-year budgets to consider the ASF as a worthy not-for-profit, community-led charitable organization. 4) Event Sponsorship: we continue to pursue the final outstanding sponsorship payment from Community Over Code North America, and are ready to engage with the ASF Conferences team on sponsorships for 2026 for Community Over Code Europe. We are pleased to receive confirmation from some Sponsors that they already have budgets allocated for the event. 5) Individual Donations and Corporate Giving: we received $19,450 in online donations via https://donate.apache.org/ —this includes $5,750 in corporate contributions by European organizations, paid in EUR and CHF. Our online donation platform is proving to be increasingly valuable to those seeking to make donations outside of traditional business hours, as well as non-US based organizations who benefit from the ease and convenience of credit card donations in multiple currencies. We also received additional corporate contributions from employee incentive programs that convert their volunteer hours to charitable dollars as well as matching gifts programs. Once again this year we received charitable contributions from donor-advised funds (DAFs) —as these are only distributed via paper check, processing them puts additional administrative demand with the office of the President to ensure their receipt and deposit prior to the end of the calendar year. Despite stating on the Fundraising Web pages that we no longer accept donations via paper check, we do continue to receive approximately one dozen donations mailed to our virtual office this time of year. 6) Administrivia: we appreciate the ASF Treasury and Accounting teams for their support during one of the busiest months of the year. We continue working with the Infrastructure team on scaling Targeted Sponsorships to meet growing PMC usage and plan for future demand. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] Foundation Comms * Produced December issue of Plus One newsletter * Subscriber list now totals 1,591 (740 new subscribers in December) * Total sent: 1,100 | Unique opens: 371 | Open rate: 34% * Published blog highlighting ASF reaching 10k committers * Published blog touting the launch of ALC Taipei * Coordinated with ASF officers to develop an end-of-year blog recapping milestones and highlighting major achievements across The ASF and open source community in 2025 Project Comms * Issued press release announcing Apache Artemis and Apache Wayang as new Top-Level Projects * Continued coordination for Apache Ozone / DiDi Global case study Brand Project * Created business card template for ASF community to leverage * Continued #ASFNewLeaf social media giveaway, selecting winners to send ASF-branded swag to in the new year * Updated brand guidelines to differentiate between project use of leaf and 3rd party use and published guidelines to Apache.org * Updated “Powered by Apache” guidelines in Press Kit on Apache.org * Continued coordination between Apache projects and designer to update logos that contain feather or native imagery Digital * Created web page for updated ASF infra policies Social Media Overview The highest performing pieces of content for December include project news, the ASF’s end of year roundup blog post and the 10k committers milestone. Social Highlights (X + LinkedIn + Bluesky)* * Total Audience: 146,407 * X: 65,907 * Bluesky: 935 * LinkedIn: 79,565 * Total Posts: * X: 31 * Bluesky: 31 * LinkedIn: 13 * Total Engagements: 4,458 *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 681,837 visits, 681,761 unique visitors -2.3% 2 min 52s average visit duration +10.3% 60% visits have bounced (left the website after one page) +1.7% 2.7 actions (page views, downloads, outlinks, internal site searches) per visit -31.6% 1,359,973 pageviews, 886,159 unique pageviews -38% 7 total searches on your website, 6 unique keywords +40% 129,606 downloads, 91,010 unique downloads -12.4% 325,707 outlinks, 168,223 unique outlinks -4.9% ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Danny Angus] General ======= Increased infrastructure donations have allowed us to migrate a number of machines off of paid hosting into donated hosting. These migrations were performed during planned operating system upgrades, and reduced Infra's ongoing cash spend. Our ability to perform these migrations seamlessly reflects positively on our commitment to Infrastructure as Code, and long- term reduction in technical debt. MFA Efforts =========== Authentik MFA work continues with the primary implementation, backups, and DR plans complete. Some gaps in performance and reliability arose during internal acceptance testing. These have been mostly resolved, and wider UI/UX and load testing is expected to begin within the week. Abuse Response Handling ======================= A sharp uptick in incidents and service outages caused by distributed abuse and attacks on our infrastructure prompted an upgrade in our tooling for mitigating harmful requests. This upgrade has allowed us to respond to and resolve incidents much faster, and continue to work on a plan for reaching out to the involved parties and working with them to resolve the matter. Our March roundtable will feature an introduction to these new tools, along with a retrospective on the increased abuse in the past months. ----------------------------------------- Attachment 5: Report from the VP of Tooling [Dave Fisher] # Tooling Our new team member has settle in. The team is happy to have him. I have extended our extra developer through March 31, 2026. ## Apache Trusted Releases (ATR) Our current development focus is on the following tasks. 1. Publishing to Distribution channels with a focus on Nexus3 first 2. Completing the candidate checks in the composition phase 3. ASVS security review and necessary fixes 4. Aligning work issues to completion of features for the Beta 5. Preparing policy discussions related to the ATR The repository is open for contributions and we have had several third party contributions, few of which are any good. We have improved our developer documentation and these are less of a distraction. ## Board Agenda Tool (BAT) The tool is now stable and nearly complete. There are some improvements waiting for volunteer developer time. Reporter integration with BAT is progressing. We have a volunteer. ## Improvements to projects.apache.org and reporter.apache.org We completed a long discussion on board@ about the reasons and plans for Tooling to take charge of these services. The plan was brought to dev@community. We now have the expected volunteer. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Brian Proffitt] Announced flagship event for 2026: Community Over Code Europe will be held October 11-14, 2026 in Glasgow, Scotland. The event will feature at least one co-located event, to be announced. Track chairs and track options are being recruited now, with the plan to launch the call for presentations right after FOSDEM week. OpenUK has already reached out to us for event collaboration, and we also already have an interested corporate sponsor. This, and given that we are working about one month ahead of last year's schedule, gives me great confidence in pulling off yet-another successful event in terms of quality and fiscal impact. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== None currently. Monthly Meetings ================ Monthly Meetings on hold until another event comes up TAC App ======= TAC app is currently closed. Future Events ============= None currently. Short/Medium Term Priorities ============================ Keeping an eye out for other smaller events to support. Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still to be done. Mailing List Activity ===================== No activity this month. Membership ========== No changes to the Committee this month. ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno] With FOSDEM coming up in two weeks, I will be sending out an email to all PMCs this week to gauge interest in D&I work within the projects and solicit feedback on our first planned[1] segment of analysis[2], Inclusion. This work will be fully opt-in going forward, so the introductory email will also ask the projects whether they wish to hear more from the D&I team and collaborate on our work, or if they wish to handle their community health at their own leisure, in which case we will leave them be for 2026 and focus on the projects that have the time and interest to pursue this. We have hit some issues with the survey solution which further delayed progress, but this should be addressed now. I have received several asks about informal D&I discussions at FOSDEM, and I am hopeful that we can use that interest to put some energy back into this committee. At a later date (TBD), we'll be sending out a survey to the projects that have indicated they want to participate in our D&I efforts. This survey will be based in part on our existing data and frameworks, and in part on what the projects indicate they feel or know is important to inclusion in their project. [1] https://s.apache.org/36mif [2] https://lists.apache.org/thread/lo792r8hqwkoy68kcf3753o3dp8l17fq ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier] # General There are no issues that need urgent attention. The last Data Privacy Report was in July 2025 and this report is for the period since the last report. ## Privacy Committee The _privacy committee_ are volunteers actively working for more privacy within the ASF. There are four members of the Privacy committee. ## Privacy complaints / Removal requests We received 2 requests since the last report in July 2025. ## Data Privacy Policies There are seven Data Privacy policies listed on the policies page: https://privacy.apache.org/policies/ The website policy was ratified by the board in January 2023 and the other six policies are all in DRAFT form. ### Telemetry Usage in Downloaded/Installed Software No work has been done on this since the last report. The Airflow PMC asked the Board about their Telemetry usage in their Board Report in September 2025 and received positive feedback. The current policy is still in DRAFT format: https://privacy.apache.org/policies/privacy-products-policy-medium.html ## Matomo The ASF started hosting its own Matomo instance in March 2022 to provide analytics for project websites that respected user's privacy: https://analytics.apache.org/ In November 2025 the handover of the Matomo instance and VM to the Infrastructure team was completed. The Privacy team appreciates all the work Infra has done to achieve this and the fact that Infra is now supporting Matomo. https://issues.apache.org/jira/browse/INFRA-26367 Currently, 78 Matomo _Tracking Codes_ have been issued, 9 since the last report in July 2025. There are 9 Matomo sites that don't receive traffic at this point. ## Content Security Policy (CSP) We continue to receive queries from projects about permissable modification of the Content Security Policy for their websites. ## Analytics Usage Campaign The _Privacy Committee_ receives a monthly report of ASF websites that utilise external trackers/analytics that are not permitted by the _Privacy Policy_. The number of websites using proscribed analytics on the monthly report has reduced from 103 to 3 in the last 12 months (-97%). # Open tasks - Provide guidelines for advertising user mailing lists - Create a list of WordPress sites - Create a list of domains that are allowed to connect because a DPA is covering it (improved Whimsy support) - Better documentation about DPAs - Add "canned responses" and instructions on how to run the privacy office to the website - Investigate TAC for data privacy and develop a targeted version for the committee - Clarify status of "donate.apache.org" - Clarify status of "status.apache.org" ----------------------------------------- Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik] Pretty much all going along as expected - and not much change owing to the end of year festivities. That said - some things worth highlighting: 1) An opportunity to have our say on the "European Open Digital Ecosystem Strategy" that will set out: * a strategic approach to the open source sector in the EU that addresses the importance of open source as a crucial contribution to EU technological sovereignty, security and competitiveness * a strategic and operational framework to strengthen the use, development and reuse of open digital assets within the Commission, building on the results achieved under the 2020-2023 Commission Open Source Software Strategy. See https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16213-European-Open-Digital-Ecosystems_en and Isabel her post to members@. 2) FOSDEM is coming up - and it is bracketed by even more, and higher profile, public policy events -- https://opensourceweek.eu has a fairly good list. As to FOSDEM - I am expecting most of our work will be to continue to inform our community & downstreams of the impact of the CRA with increasing fidelity. And secondly that the practical side of things (SBOMs, (Paid for) Attestations, etc) will get a boost from the informal contacts. 3) I'll see if I can tempt someone (ideally European) to take my/foundations seat in the steering committee of ORC at Eclipse -- as this is certainly something we want to keep supporting/furthering. May continue for another year myself if needed (as I do not want to distract any of our ASF volunteer doing useful work for this somewhat more symbolic/governance specific role). ----------------------------------------- Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz] There were no noteworthy developments this month. ----------------------------------------- Attachment 12: Report from the VP of W3C Relations [Andy Seaborne] Niklas Merz has joined the W3C WebDX Community Group. This is the first member of this Community Group and the Foundation has signed the Community Group agreement. ----------------------------------------- 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. After resolving a handful of LEGAL issues, we are flat at 25 issues compared to the last month. We started working with DLAPiper on two new subpoenas. Note that one came with additional weird summon via snail mail that we need to understand how to address. Even if DLAPiper won't be able to help us long term with these -- we expect and answer on how to handle the additional summon this week. In general, we need to, once again solicit additional pro-bono legal counsel hours since with DLAPiper (however excellent their support has been) we're constantly running into cross-representations issue and that slows things down at best (they need to obtain a waiver) or blocks us from using their services at worst. I started poking around legal committee members to see if they know any lawyers who may want to do this kind of work for us, but I would also encourage board members to do the same. We've officially offered committer privileges to Jude Smith (something that had a lazy consensus about two months ago on Legal Committee mailing list -- but just slipped through the cracks on my TODO list -- sorry about that). Based on conversation with some of the board members around the Code of Conduct, VP Legal has sent a clarification to the board@ mailing list and is awaiting further instructions from the board. The US DoJ was interested in understanding more about how the foundation works, the license, and specifically the situation with Fivetran's Proposed Acquisition of dbt Labs. Ruth Suehle took the lead on taking care of that interview. We have received one more request for detailed export compliance statement from Thales Global Services and responded with our general policy. Proposal for Updating Apache License 2.0 to Version 3.0 (brought by an outside contributor) has been rejected. ----------------------------------------- Attachment 14: Report from the Apache Security Team Project [Mark J. Cox] December * We continue to help projects define a security model, this month Hudi. * We're providing feedback in the Alpha release of Apache Trusted Release * We're closely following Infra's progress in rolling out MFA and intend to provide feedback and assistance. Stats for December 2025: 41 [license confusion] 19 [report/question relating to dependencies] 25 [support request/question not security notification] Security reports: 91 (last months: 85, 66) 17 ['logging'] 10 ['airflow'] 6 ['cassandra'] 5 ['superset'] 4 ['cloudstack'] 3 ['james', 'tvm', 'website or other infrastructure'] 2 ['druid', 'fineract', 'hertzbeat', 'jackrabbit', 'nifi', 'pdfbox', 'solr', 'tomcat', 'zookeeper'] 1 ['arrow', 'axis', 'beam', 'cxf', 'dubbo', 'flink', 'guacamole', 'hadoop', 'hc', 'httpd', 'hugegraph', 'kafka', 'manifoldcf', 'mynewt', 'ofbiz', 'ranger', 'sis', 'spark', 'struts', 'syncope', 'texera', 'tika'] In total, as of 1st Jan 2026, we're tracking 297 (last months: 268, 244) open issues across 90 projects, median age 105 days (last months: 103, 100). 74 of those issues have CVE names assigned. 20 (last months: 20, 23) of these issues, across 11 projects, are older than 365 days. * 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. A recent release fixed the most serious and complex ones, making space to now focus on the remaining issues. (Last update: 2026-01-06) * spark (Health amber): the project has a backlog of security reports to be triaged (Last update: 2025-12-01) * thrift (Health amber): the PMC does not appear to have the bandwidth to triage incoming reports in a timely fashion (Last update: 2026-01-06) ----------------------------------------- Attachment A: Report from the Apache Accumulo Project [Ed Coleman] ----------------------------------------- Attachment B: Report from the Apache ActiveMQ Project [Christopher L. Shannon] ## Description: The mission of Apache ActiveMQ is the creation and maintenance of software implementing a distributed messaging system ## Project Status: Current project status: Ongoing Issues for the board: None Note: ActiveMQ Artemis was split into its own TLP, Apache Artemis Project, effective 2025-11-29 ## Membership Data: Apache ActiveMQ was founded 2007-01-16 (19 years ago) There are currently 64 committers and 29 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 Matt Pavlovich on 2023-12-06. - No new committers. Last addition was Anton Roskvist on 2024-02-09. ## Project Activity: ### ActiveMQ - 6.2.0 was released on 2025-11-14 - NMS ActiveMQ 2.2.0 was released on 2025-11-27. - Project is working towards v6.3.0 and other patch releases. - Major updates include Jetty 12 and JDK 25 support. - Major improvement in reducing total unit test execution time is underway. - Updates to project test coverage for JDKs and architectures using GitHub Actions and weekly s390x build jobs. ### ActiveMQ Artemis (final releases before split) - ActiveMQ Artemis 2.44.0 was released on 2025-11-03. - ActiveMQ Artemis 2.43.0 was released on 2025-10-16. - ActiveMQ Artemis Console 1.4.0 was released on 2025-11-11. ## Community Health: We have a sustained activity on the mailing lists. We also see new contributors who submitted new PRs. We are are moving forward on JMS 3.1 and preparing a proposal for runtime for ActiveMQ 7. Discussions have been started for several new committers. ----------------------------------------- Attachment C: Report from the Apache Airavata Project [Suresh Marru] ----------------------------------------- Attachment D: Report from the Apache Ambari Project [Brahma Reddy Battula] ----------------------------------------- Attachment E: Report from the Apache Answer Project [Ning Qi] ## Description: The mission of Apache Answer is the creation and maintenance of software related to A Q-and-A platform software for teams at any scales ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Answer was founded 2024-12-18 (a year 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 Anne Zhu on 2024-12-18. - No new committers were added. ## Project Activity: - 1.7-series releases — Shipped v1.7.0 and follow-up v1.7.1 to stabilize the 1.7 line and address early feedback. - Next milestone planning — Opened discussions for v1.8.x feature scope and schedule. - AI initiative — Began design work to introduce AI-powered capabilities (proposal/RFCs in progress), targeting assistive moderation, content quality, and developer ergonomics in the 1.8.x cycle. ## Community Health: - Added 8 new core code contributors, expanding engineering bandwidth and review coverage. - Added 5 new translation contributors, strengthening localization depth and turnaround. ----------------------------------------- Attachment F: Report from the Apache APISIX Project [Ming Wen] ----------------------------------------- Attachment G: Report from the Apache Aries Project [Christian Schneider] ## Description: Apache Aries software is a set of plugable Java components enabling an enterprise OSGi application programming model. ## Project Status: Current project status: Largely maintenance mode with some developments ongoing. Issues for the board: None at this time. ## Membership Data: Apache Aries was founded 2010-12-15 (15 years ago) There are currently 56 committers and 40 PMC members in this project. The Committer-to-PMC ratio is 7:5. Community changes, past quarter: - No new PMC members. Last addition was Carlos Sierra Andrés on 2018-07-03. - No new committers. Last addition was Romain Manni-Bucau on 2020-01-29. ## Project Activity: Mainly dependency upgrades and support for new Java versions. ## Community Health: Slightly decreased activity. Development driven by a low number of active committers. ----------------------------------------- Attachment H: Report from the Apache Arrow Project [Antoine Pitrou] ## Description: The mission of Apache Arrow is the creation and maintenance of software related to columnar in-memory processing and data interchange ## Project Status: Current project status: Ongoing (high activity) Community Health Score (Chi): 10.00 (Super Healthy) * Score note: More than 4 emails per day to all MLs combined in the past quarter (+1.00氣) * Score note: New members() added to the LDAP committee group within the last six months (+0.50氣) * Score note: New committer(s) invited within the last three months (+0.75氣) Issues for the board: * A release announcement for ADBC-22 was rejected by announce@apache.org, though the format is the same as previous announcements. Are there new requirements? Are the rules for posting to announce@a.o spelled out clearly somewhere? ## Membership Data: Apache Arrow was founded 2016-01-19 (10 years ago! 🎉) There are currently 116 committers and 61 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: * Rossi Sun was added to the PMC on 2025-10-06 * Kyle Barron was added as committer on 2025-10-07 We don’t have any diversity stats (gender, nationality, etc.) but there’s probably a massive imbalance. We would welcome opinions from the ASF board on how to gather such data and improve things in that regard. Another topic that might be worth addressing is whether we need some kind of emeritus status for long-time inactive project members. ## Project Activity: The project has an [active blog](https://arrow.apache.org/blog/) where you can find more information on recent releases. ### Community events We have held the [first Arrow summit] (https://www.meetup.com/pydata-paris/events/310646396/) in October 2025, co-located with the PyData Paris conference. The event was open to everyone and entrance was free. There were around 35 attendees, half experienced Arrow contributors and half interested onlookers. The day consisted mostly of small presentations and free discussions around the attendees. We consider the event to be a success as it allowed tightening social bonds among a rather diverse community comprised of numerous sub- and side-projects. No recording is available as we didn’t have any A/V apparatus in the room. ### Final demise of Voltron Data Voltron Data, who until 2024 employed many Arrow contributors, has finally ended all activity. This isn’t affecting the project’s sustainability as most Arrow contributors had already been laid off one year ago, but some pieces of infrastructure that were still managed by Voltron Data had to be migrated urgently. We have averted all immediate risks and development has resumed as normal, though a couple minor issues remain to be resolved. ### Final end of the monorepo We have completed the envisioned codebase splits to organize the various language implementations as independent git repositories (still under the Apache Arrow umbrella, though). The ex-monorepo (`apache/arrow` on GitHub) lives on as the home for the C++ implementation and its dependent language bindings (Python, R, Ruby, MATLAB, C/GLib). ### Community Organization The Arrow project is increasingly organized as different communities focused on the different Arrow language implementations (e.g C++ and bindings like Python, Rust, Go, etc). These communities collaborate on the overall Arrow specification and interoperability issues. This structure seems to be working well as the project grows and matures and there are newly separate repositories for arrow-go, arrow-dotnet, arrow-julia, arrow-swift. ### Recent Releases: * RS-OS-0.13.0 was released on 2025-12-23. * GO-18.5.0 was released on 2025-12-12. * RS-57.1.0 was released on 2025-11-24. * ADBC-21 was released on 2025-11-07. * 22.0.0 was released on 2025-10-24. * RS-57.0.0 was released on 2025-10-23. * DOTNET-22.1.0 was released on 2025-10-17. * JS-21.1.0 was released on 2025-10-07. #### arrow-rs The Rust implementation continues a monthly release cadence. We have been focusing on expanding coverage for newer Arrow array types such as ListView and RunEndEncoded. We have also invested heavily in the Rust parquet reader, which is described in several blogs [1] [2]. A new optimized reader to read avro to Arrow arrays was also released, see [3]. [1]: https://s.apache.org/parquet-rs-late-materialization-deep-dive [2]: https://arrow.apache.org/blog/2025/10/23/rust-parquet-metadata/ [3]: https://arrow.apache.org/blog/2025/10/23/introducing-arrow-avro/ ## Community Health: Based on mailing-list volume, project activity remains steady. Quarter-to-quarter variations can probably be attributed to random oscillation rather than any structural change. Of note, several projects such as Arrow C++ and Arrow Rust have GitHub discussions enabled to help with user questions (those are echoed on user@arrow.apache.org, so are still accounted for in the stats below). All metrics from https://reporter.apache.org/wizard/?arrow#, for posterity: * builds@arrow.apache.org had a 55% increase in traffic in the past quarter (462 emails compared to 297) * dev@arrow.apache.org had a 60% increase in traffic in the past quarter (290 emails compared to 181) * github@arrow.apache.org had a 4% increase in traffic in the past quarter (15882 emails compared to 15201) * issues@arrow.apache.org had a 69% increase in traffic in the past quarter (1737 emails compared to 1022) * user@arrow.apache.org had a 40% decrease in traffic in the past quarter (98 emails compared to 162) ----------------------------------------- Attachment I: Report from the Apache Artemis Project [Christopher L. Shannon] ## Description: The mission of Apache Artemis is the creation of a high-performance, multi-protocol open source messaging platform designed to power modern microservices and cloud-native applications. ## Project Status: Current project status: New Issues for the board: None ## Membership Data: Apache Artemis was founded 2025-11-18 There are currently 64 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: The Artemis TLP membership was initially a full copy of the ActiveMQ TLP with the same PMC members and committers so everyone retained the same rights as before the split. Andy Taylor was added as a PMC member on 11th December 2025. ## Project Activity: Apache Artemis was established on 2025-11-18 after splitting out from Apache ActiveMQ. Since then, work has continued towards completing the migration with aim towards being ready to do the first Apache Artemis releases. Business is also continuing as usual in terms of addressing user bug reports and functionality requests. Since the December report, many more updates have been made towards readying for Apache Artemis releases. Work was undertaken to update the management console branding / visual identity to reflect the separation and give the new Apache Artemis releases an distinct look. Many updates have been made to the documentation to address the new project identity. The next release version was advanced from 2.45.0 to 2.50.0 to add a small gap to signal the transition, and generally just serve as a nicer transition reference point going forward. The Maven module groupId was switched to org.apache.artemis in the artemis, artemis-console, and artemis-examples repos, with relocation poms to redirect users from the previous ActiveMQ Artemis modules to signal the switch and allow for them to transition their builds over time. A candidate for Apache Artemis Console 1.5.0 is currently under vote, towards being used soon in an Apache Artemis 2.50.0 release once some remaining work on the transition is complete. ## Community Health: The community is healthy and there continues to be little impact to users as everything transitions to the new TLP. ----------------------------------------- Attachment J: Report from the Apache AsterixDB Project [Ian Maxon] ## Description: The mission of AsterixDB is the creation and maintenance of software related to open source Big Data Management System ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache AsterixDB was founded 2016-04-19 (10 years ago) There are currently 43 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Peeyush Gupta was added to the PMC on 2025-12-02 - Shahrzad Haji Amin Shirazi was added as a committer on 2026-01-13 ## Project Activity: Releases: The next release is still pending on some documentation and packaging work. Part of this was solved by the Containerized Packaging (APE 27) but there still needs to be a walk through on how to set the system up on top of object storage so that some of the new features (Atomic Statements, etc.) can be used. APEs: - APE 28 (Improved Async API) was accepted and related changes merged - APE 29 (Atomic Statements) is still drafting, the discussion has not started yet in earnest. - APE 30 (Sandboxed UDFs) was proposed and saw a little discussion on the dev list, but not enough yet. - APE 31 (Vector Indexing) was proposed. Some smaller patches related to it are already under review ## Community Health: I continued to try and draw more activity to both the dev@ list and ASF Slack's #asterixdb channel. For the former I am not sure why the traffic is so far down- I think this just tends to be a quarter where folks are busy with other things for one reason or another. Hopefully it picks up in the next quarter. For the latter, I am trying to use it as a place where little questions and notifications about day-to-day development issues. For example, if I notice (or cause) a test breakage I post about it there first to try and encourage that as an avenue to quickly find out what might be going on. Kind of treating it like IRC. Peeyush was added to the PMC, and it's great to have him. He was responsible for the design of many new features (Atomic statements, COPY FROM/TO, etc.) so it will be great to have him take part in deciding the future direction of the project. Shahrzad was added as a committer just in time for this report, and it is likewise great to have her on board. She has been involved in the project for many years, and has been in charge of the implementation of Heterogeneous-type indexes, which is an awesome feature. ----------------------------------------- Attachment K: Report from the Apache Attic Project [Hervé Boutemy] ## Description: The mission of Attic is the creation and maintenance of a home for dormant projects. ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Attic was founded 2008-11-19 (17 years ago) There are currently 19 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 Niall Pemberton on 2025-04-04. - No new committers. Last addition was Niall Pemberton on 2025-04-04. ## Project Activity: Attic worked on retiring 5 projects: - Griffin and Portals, finishing from previous quarter, - Kibble and Traffic Control, - Olingo, still work in progress. Progress tracked at https://attic.apache.org/tracking.html A first "after 6 months" feedback has been shared with M&P on Social Media accounts update from retired projects: https://lists.apache.org/thread/jbvovbxp17mws35bhwfgv7rv7bklwm41 Some rework will have to happen with M&P on Social Media management, as it appears getting access to account *after* project has been retired (= when Attic is involved) is not easy: we'll contact M&P. We are working with Tooling ATR project to make sure retirement of committees and move of their projects to Attic Committee works. ## Community Health: 3 active members continue to drive operations, with new small improvements found on process and tools. Having more people involved in actual retirement would be useful to spread the load and check our documentation is complete. ----------------------------------------- Attachment L: Report from the Apache Avro Project [Ryan Skraba] ----------------------------------------- Attachment M: Report from the Apache Beam Project [Kenneth Knowles] ----------------------------------------- Attachment N: Report from the Apache bRPC Project [James Ge] ## Description: The mission of Apache bRPC is the creation and maintenance of software related to an industrial-grade RPC framework for building reliable and high-performance services ## Project Status: Current project status: ONGOING Issues for the board: NONE ## Membership Data: Apache bRPC was founded 2022-12-21 (3 years ago) There are currently 21 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Guangming Chen on 2025-01-06. - No new committers. Last addition was Yang Liming on 2024-03-24. ## Project Activity: bRPC v1.15.0 was released on 2025-10-27 with the following new features: - Support custom ParkingLot number - Add pb2json depth limit - Tens of bug fix and enhancement ## Community Health: Committers take turns responding user emails and issues on a weekly basis. During the past quarter, about 52 new emails were received and answered weekly. ----------------------------------------- Attachment O: Report from the Apache BuildStream Project [Abderrahim Kitouni] ## Description: The mission of Apache BuildStream is the creation and maintenance of software related to efficiently and correctly developing, building and integrating software stacks ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache BuildStream was founded 2022-09-21 (3 years ago) There are currently 6 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Abderrahim Kitouni on 2022-09-21. - No new committers were added. ## Project Activity: We had a new release in October, and we're on track for another release this month. We're keeping up with a more or less quarterly release schedule. In terms of new features, we got a new source information API that allows source plugins to communicate to the BuildStream core the provenance of the sources it downloaded. This allows building tools to generate SBoM (Software Bill of Materials) for BuildStream projects. We also got a feature to allow software running inside the BuildStream sandbox to access Remote Execution API (REAPI). This allows things such as running Bazel inside the BuildStream sandbox and taking advantage of the cache or remote execution. ## Community Health: There has been a increase in the mailing list traffic this past quarter, mainly due to the discussion around extending the nested REAPI to preemptively schedule build actions. We also had two new contributors sending (small) pull requests. ----------------------------------------- Attachment P: Report from the Apache Calcite Project [Mihai Budiu] ## Description: Apache Calcite is a highly customizable framework for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. Avatica is a sub-project within Calcite and provides a framework for building local and remote JDBC and ODBC database drivers. Avatica has an independent release schedule and its own repository. ## Project Status: Current project status: ongoing (high activity) Issues for the board: none ## Membership Data: Apache Calcite was founded 2015-10-21 (10 years ago) There are currently 81 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 Alessandro Solimando on 2025-04-30. - Silun Dong was added as committer on 2025-12-14 - Thomas Rebele was added as committer on 2025-12-19 - Yu Xu was added as committer on 2025-12-16 ## Project Activity Recent releases: - ‎Calcite 1.41.0 was released on 2025-11-01 - ‎Avatica 1.27.0 was released on 2025-09-30 - Calcite 1.40.0 was released on 2025-05-28 ## Community Health The community seems very actively engaged. We are closing issues faster than they are opened; this is unusual. (A big credit is due to Zhen Chen, who has been closing many old and new issues.) Besides fixing many bugs and adding new features, we have seen some significant contributions, such as a new query decorrelation algorithm contributed by Silun Dong. I think the last year has seen a marked improvement of the reliability of Calcite, especially in handling complex queries. - ‎142 JIRA tickets opened and 151 closed in the past quarter. - dev@calcite.apache.org had a 20% increase in traffic in the past quarter (338 emails compared to 281). - issues@calcite.apache.org had a 31% increase in traffic in the past quarter (1531 emails compared to 1162) Top committers for last 3 months: https://github.com/apache/calcite/graphs/contributors?selectedMetric=commits - xiedeyantu: 45 commits - mihaibudiu: 17 commits - iwanttobepowerful: 6 commits - xuzifu: 6 commits - rubenada: 6 commits Most active reviewers: - xiedeyantu - mihaibudiu - NobiGo - asolimando - xuzifu666 - silundong - iwanttobepowerful ----------------------------------------- Attachment Q: Report from the Apache CarbonData Project [Jacky Li] ----------------------------------------- Attachment R: Report from the Apache Causeway Project [Jörg Rade] ## Description: The mission of Causeway is to enable the rapid development of maintainable domain-driven apps in Java. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Causeway was founded 2012-10-17 (13 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 Martin Hesse on 2023-07-05. - No new committers. Last addition was Martin Hesse on 2023-07-04. ## Project Activity: In the last quarter we released Causeway 3.5.0 [1] which was mostly a security release (CVE-2025-64408). In parallel we are working on the 4.x branch, based on Spring Boot 4, which makes use of Java features beyond version 17 and ends the support for JDO. We continue to promote the framework to extend our user base, there has been a series of articles on devm.io [2,3,4,5], and a new series of articles on javapro [6, 7]. [1] https://causeway.apache.org/relnotes/latest/2025/3.5.0/relnotes.html [2] https://devm.io/ddd/apache-causeway-introduction/ [3] https://devm.io/spring/apache-causeway-app-testing/ [4] https://devm.io/java/apache-causeway-modularity-app [5] https://devm.io/java/apache-causeway-extending-spring-boot/ [6] https://javapro.io/2025/09/30/apache-causeway-an-introduction/ [7] https://javapro.io/2026/01/01/apache-causeway-going-further/ ## Community Health: We continue to see engagement on our slack channel, which the community seems to much prefer over the users mailing list. Nevertheless, we continue to ensure that all relevant information are cross-posted to users@ and dev@ where necessary. ----------------------------------------- Attachment S: Report from the Apache Celix Project [Pepijn Noltes] ## Description: Apache Celix is a framework for C and C++14 to develop dynamic modular software applications using component and in-process service-oriented programming. Apache Celix is inspired by the OSGi specification adapted for C and C++. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Celix was founded 2014-07-16 (11 years ago) There are currently 17 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Peng Zheng on 2022-10-16. - No new committers. Last addition was Zhenbao on 2022-10-19. ## Project Activity: - Last release was 2023-09-29 - Not a lot of activity, several small fixes ## Community Health: Development activities have increased again. Still a small project with minimal activity, but the activities slowly work towards a new release. ----------------------------------------- Attachment T: Report from the Apache CXF Project [Andriy Redko] ## Description: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. There is also a sub-project that leverages CXF: Fediz - Fediz helps you to secure your web applications via the standard WS-Federation Passive Requestor Profile. ## Project Status: Current project status: Ongoing, moderate activity Issues for the board: none ## Membership Data: Apache CXF was founded 2008-04-15 (18 years ago) There are currently 44 committers and 26 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 Andy McCright on 2019-02-24. - No new committers. Last addition was Jamie Mark Goodyear on 2024-07-19. ## Project Activity: Jakarta EE 11 platform support is about to be released, the preparation is well underway and the vote is expected to be sent this week for Apache CXF 4.2.0 release. The team decided to go ahead with Undertow 2.4.0.Alpha1 release, instead of removing Undertow support altogether. Recent releases: 3.6.9 was released on 2025-11-17. 4.0.10 was released on 2025-11-17. 4.1.4 was released on 2025-11-17. ## Community Health: For the most part, the project is making steady, but not stellar, progress (although 4.2.0 / Jakarta EE 11 is big deal). Many of the protocols and specs that CXF implements are mature specs and don't really change much. Thus, steady progress and regular releases are a good thing. We are responding to bug reports, reviewing and merging pull requests, and hopefully getting patch releases out soon, along with 4.2.0 release. ----------------------------------------- Attachment U: Report from the Apache DataFu Project [Eyal Allweil] ## Description: The mission of Apache DataFu is the creation and maintenance of software related to well-tested libraries that help developers solve common data problems in Hadoop and similar distributed systems ## Project Status: Current project status: Ongoing (low) Issues for the board: None ## Membership Data: Apache DataFu was founded 2018-02-21 (8 years ago) There are currently 20 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Ohad Raviv on 2023-02-06. - No new committers. Last addition was Ben Rahamim on 2025-02-19. ## Project Activity: Most of the activity in this quarter has been defining task for the next version and writing/reviewing the blog post about one of the contributions from the last release. ## Community Health: Most of the activity this quarter has been around the definition of new issues in Jira and the blog post. We definitely need to increase our use of the mailing list (as Rich Bowen wrote recently) because too much of our activity takes place off of it. ----------------------------------------- Attachment V: Report from the Apache DB Project [Bryan Pendleton] ## Description: The mission of the Apache DB project is to create and maintain commercial-quality, open-source, database solutions based on software licensed to the Foundation, for distribution at no charge to the public. The Apache DB TLP consists of the following subprojects: o JDO : focused on building the API and the TCK for compatibility testing of Java Data Object implementations providing data persistence. o Torque : an object-relational mapper for Java. ## Project Status: Current project status: ongoing Issues for the board: none Please see the Project Activity section of our report for some significant updates. ## Membership Data: Apache DB was founded 2002-07-16 (23 years ago) There are currently 48 committers and 46 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 Max Philipp Wriedt on 2024-07-03. - No new committers. Last addition was Max Philipp Wriedt on 2023-04-14. ## Project Activity: The JDO project is working on cleaning up the TCK to make multithreaded queries more efficient and has encountered some underlying issues that are taking a while to resolve. Once these are resolved, we will start looking at making a release. Two significant changes are underway in the DB project: - Apache DB have voted to select a new PMC chair, Jeffery Painter, and approved the proposal with 10 positive votes. The Special Order to ratify the new chair is in this month's agenda. - The Derby codebase has been moved to read-only state. This includes the website (https://db.apache.org/derby/), mailing lists, wiki (https://cwiki.apache.org/confluence/display/DERBY/FrontPage), Subversion repository, and JIRA bug tracker. Official distributions remain available on an as-is basis at https://db.apache.org/derby/derby_downloads.html. ## Community Health: Although the action to move the Derby codebase to read-only state reflects a general decline in community interest in the Derby software, overall the DB project remains in good health. Both the JDO and Torque communities experience steady activity, with ongoing development and periodic releases in both codebases. PMC participation in the recent decisions described above was strong, with a dozen PMC members participating in the discussions and broad consensus to make the changes described, including from 3 PMC members in the Derby community. ----------------------------------------- Attachment W: Report from the Apache Directory Project [Shawn McKinney] ## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Project Status: Low activity but the subprojects are being maintained. No issues to report at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (21 years ago) There are currently 57 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Brian Demers on 2023-10-23. - No new committers. Last addition was Fredrik Roubert on 2023-07-10. ## Project Activity: Per sub-project: - ApacheDS: low activity. Release in the works. - LDAP API: low activity. Release in the works. - Studio: low activity. Needs a release. - Fortress: low activity. - Kerby: low activity. Release soon. - Mavibot: low activity. - SCIMple: low activity. Needs a release. ## Community Health: Pull requests are being reviewed and applied. Mailing list items are being attended to. A blocker for a release to API and Directory server has been resolved. The maintainer is busy with other work but is committed to getting the release done. ----------------------------------------- Attachment X: Report from the Apache DolphinScheduler Project [Lidong Dai] ----------------------------------------- Attachment Y: Report from the Apache Druid Project [Abhishek Agarwal] ----------------------------------------- Attachment Z: Report from the Apache Dubbo Project [Jun Liu] ----------------------------------------- Attachment AA: Report from the Apache Fineract Project [James Dailey] ## Description: The mission of Apache Fineract is the creation and maintenance of software related to a core banking platform that provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world's underbanked and unbanked. ## Project Status: Current project status: Ongoing Issues for the board: None at this time ## Membership Data: Apache Fineract was founded 2017-04-18 (9 years ago) There are currently 55 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Adam Monsen was added to the PMC on 2025-11-05 - No new committers. Last addition was Adam Monsen on 2025-05-16. ## Project Activity: The project was able to achieve a quarterly release schedule for all of 2025. The most recent release was done using ATR in early test phase. Security fixes were made. Test coverage has been improving throughout the year and new documentation has been added. There are new modularization efforts underway, although this remains a major area of work. This is an active development project, growing interest. ## Community Health: At a high level, the community is generally ok. * Participation at Community Over Code conference - and Fintech Security Track. Successful engagement by several community members. * Great example in 2025 -engaging Dev discussion about Build issues, approachability and ease of build as a key driver, good engagement, resolution and transparent. Called out by PMC chair to celebrate. https://lists.apache.org/thread/f983bj5328zd0cnwtpqqx8vfd0wnpj0o * AI policy discussions - how to use AI appropriately - started discussion. https://lists.apache.org/thread/xxoqt3jn8trhwo1lnxjy46r1dkolfg1h There are active and important discussions of functionality and direction on the list. Conversation that occur on Mifos Slack #fineract channel are being generally summarized back to the email list. There has been a recent and growing flood of people to the project, with many coming as candidates for GSOC - adding to volumes on the list. These are Mifos GSOC participants. Community meeting held just before last board meeting - successfully noted progress and identified gaps 2025-10-08 Meeting notes https://cwiki.apache.org/confluence/display/FINERACT/2025-10-08+Meeting+notes ----------------------------------------- Attachment AB: Report from the Apache Flagon Project [Joshua Poore] ## Description: The mission of Apache Flagon is the creation and maintenance of software related to thin-client behavioral logging capability useful for business analytics, usage analytics, usability and user testing ## Project Status: Current project status: Active but Quiet Issues for the board: None at this time ## Membership Data: Apache Flagon was founded 2023-03-21 (3 years ago) There are currently 19 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Evan Jones on 2024-07-10. - No new committers. Last addition was Ryan Thenhaus on 2025-02-08. - Am following up on ICLAs for M. Grivel, and A. Fluck, who were voted in as committers and officially invited to join as committers. ## Project Activity: Project activity was extremely low this quarter. PMC will push for maintainance activities in the upcoming quarters. I know there is interest in doing more work with Open Telemetry integration, and so PMC will work to coordinate more effort in that direction in the new year. ## Community Health: The community regularly corresponds and PMC is aware of some ad hoc meetings between members. However, driving correspondence through official community challenges remains very challenging. Additionally, the project remains visible and relevant as there has been a surge of interest in business analytics, particularly in easy-to-use and maintain client packages that can log in Open Telemetry Logging Protocol (OTLP). I believe that we'll see a surge of new code coming in from committers in that that direction as well as a the typical annual maintenance that the community and PMC reliably does on core products like UserALE.js. Overall, while it's too early to see if the monorepo structure has an impact on organic project growth, it hasn't seemed to deter end-users. I am continually surprised to hear in correspondence with the PMC and in my own work anecdotes of how a variety of industries (including the AAA gaming industry) are aware of Flagon and consider it a viable tool for their own purposes. ----------------------------------------- Attachment AC: Report from the Apache Fory Project [Chaokun Yang] The Apache Fory is a high-performance, multi-language serialization framework that enables efficient data exchange across systems and programming languages. Leveraging JIT compilation and zero-copy techniques, Fory delivers low-latency, high-throughput serialization for modern distributed applications. Project Status: Ongoing with high activity. Over the past quarter, the Apache Fory project has made significant progress in core development, documentation, and community growth. Key efforts have focused on advancing rust/python/go/java implementations, and enhancing user experience through better documentation. The community remains active and engaged, with steady contributions from both long-standing and new contributors. Recent Releases: The project has maintained a strong release cadence over the past quarter: v0.14.1 Dec 26, 2025 v0.14.0 Dec 15, 2025 v0.13.2 Dec 05, 2025 v0.13.1 Nov 06, 2025 v0.13.0 — Oct 27, 2025 These releases include performance improvements, bug fixes, expanded language support, and enhanced developer tooling. We released official support for Fory Rust and C++ in last quarter. Project Activity: Development activity remains robust, with ongoing work across multiple fronts: Continuous improvement of documentation for users and contributors; Active development on Fory implementations in Rust, Python, and Go Current Plans: The project’s roadmap for the coming months includes: Reaching General Availability (GA) status for the C++, and Go language bindings Expanding adoption through outreach and integration examples Attracting new contributors via outreach and improved contribution guides Further enhancing user and contributor documentation to lower entry barriers We are also exploring opportunities for collaboration with other Apache projects to demonstrate cross-project interoperability. New Committers and PMC Members: Committer: Yuyang Liu was added on Oct 04, 2025 PMC Member: Pan Li was added on June 4, 2025 These additions reflect the project’s healthy growth and commitment to empowering active contributors. Branding and Legal Considerations: There are no known branding or legal issues at this time. The project continues to use its name and marks in accordance with Apache policies. All official project materials reflect proper branding and attribution. Infrastructure and Strategic Needs: No critical infrastructure issues have been encountered. The project is satisfied with current tooling and services provided by the Apache Infrastructure team. Board-Level Issues: There are no issues requiring Board action at this time. ----------------------------------------- Attachment AD: Report from the Apache Geronimo Project [Jean-Louis Monteiro] ----------------------------------------- Attachment AE: 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 AF: Report from the Apache Hadoop Project [Xiaoqiao He] ## Description: The mission of Hadoop is the creation and maintenance of software related to Distributed computing platform ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Hadoop was founded 2008-01-16 (18 years ago) There are currently 250 committers and 126 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Ahmar Suhail was added to the PMC on 2025-11-13. - Haobo Zhang was added as committer on 2026-01-02. - HuaLong Zhang was added as committer on 2025-12-20. ## Project Activity: 3.4.2 was released on 2025-08-28. hadoop-thirdparty-1.4.0 was released on 2025-03-27. 3.4.1 was released on 2024-10-18. 3.4.0 was released on 2024-03-17. ## Community Health: - Full Support for JDK 17 and JDK 21 To achieve full support for JDK 17 and JDK 21, we advanced upgrades to code quality tools compatibility, API documentation generation tools, and the build system. 1. We fixed new warnings introduced by the SpotBugs plugin upgrade across modules, such as Common, HDFS, YARN, and MapReduce ensuring stable builds in JDK 17/21 environments (HADOOP-19731[1]). 2. At the same time, we refactored and reintegrated the JDiff tool (which no longer supported JDK 9+) based on JDK 17 restoring API change comparison capabilities and providing assurance for version releases and compatibility checks (HADOOP-19402[2]). 3. In addition, we completed upgrades the build and CI pipelines unifying the base build JDK to JDK 17, covering local builds and continuous integration processes, and laying a solid foundation for subsequent validation and formal support of JDK 21. - JDK 22+ Compatibility and Adaptation in Progress We continue to advance Hadoop's compatibility with JDK 22 and higher versions, focusing on changes in Java security model and thread semantics. 1. By introducing SubjectInheritingThread / SubjectPreservingThread, we restored the propagation semantics of Subject across threads ensuring correctness in security scenarios such as Kerberos. 2. Simultaneously, we refactored historical dependencies on SecurityManager avoiding deprecation or termination warnings in JDK 24+ environments. 3. Related changes have been progressively validated by module and partially merged into the main branch laying the foundation for formal support of JDK 24/25 (HADOOP-19668[3], HADOOP-19670[4], HADOOP-19744[5]). - New CapacityScheduler Web UI Support We advanced the visualization capabilities of YARN Capacity Scheduler, introducing a brand-new CapacityScheduler Web UI that supports hierarchical display of queue structures, resource quotas, and runtime status, while providing visualized viewing and management of scheduling configurations. This feature has been integrated into the ResourceManager, and continues to be refined through multiple PRs, and improves the observability and usability of scheduler configuration and operations (YARN-11885[6]). - The Project shows healthy engagement based on Mailing list/JIRA/Github traffic. [1] https://issues.apache.org/jira/browse/HADOOP-19731 [2] https://issues.apache.org/jira/browse/HADOOP-19402 [3] https://issues.apache.org/jira/browse/HADOOP-19668 [4] https://issues.apache.org/jira/browse/HADOOP-19670 [5] https://issues.apache.org/jira/browse/HADOOP-19744 [6] https://issues.apache.org/jira/browse/YARN-11885 ----------------------------------------- Attachment AG: Report from the Apache HBase Project [Duo Zhang] ## Description: Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. hbase-thirdparty is a set of internal artifacts used by the project to mitigate the impact of our dependency choices on the wider ecosystem. hbase-connectors is a collection of integration points with other projects. The initial release includes artifacts for use with Apache Kafka and Apache Spark. hbase-filesystem contains HBase project-specific implementations of the Apache Hadoop FileSystem API. It is currently experimental and internal to the project. hbase-operator-tools is a collection of tools for HBase operators. Now it is mainly for hosting HBCK2. hbase-native-client is a client library in C/C++, in its early days. hbase-kustomize is for deploying HBase on kubernetes, still under development. ## Project Status: Current project status: Ongoing Issues for the board: ## Membership Data: Apache HBase was founded 2010-04-21 (16 years ago) There are currently 112 committers and 62 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 Nihal Jain on 2025-02-02. - No new committers. Last addition was Dávid Paksy on 2025-06-13. ## Project Activity: hbase-operator-tools-1.3.0 was released on 2025-12-06. 2.5.13 was released on 2025-11-14. 2.6.4 was released on 2025-11-14. We have updated our website to be more modern style. https://lists.apache.org/thread/o1dfnhsqlwgjfgmzq6d08gzsz5oxc8qh https://lists.apache.org/thread/qt1hjnntzd6rt20qyshdvm3q7gbpnbwo https://issues.apache.org/jira/browse/HBASE-29689 https://hbase.apache.org/ We have reached 500+ contributors on GitHub. ## Community Health: - dev@hbase.apache.org: 964 subscribers(964 in the previous quarter) 403 emails sent to list(471 in the previous quarter) - user@hbase.apache.org: 1975 subscribers(1977 in the previous quarter) 14 emails sent to list(20 in the previous quarter) - user-zh@hbase.apache.org 81 subscribers(81 in the previous quarter) It was Christmas so the community was less active in the last month of this quartar. We have released hbase-operator-tools-1.3.0, which targets the 3.0.0 release. When running big integration tests for 3.0.0 release we have found several critical bugs, and we are still working on fixing them so we can make the 3.0.0 release soon. ----------------------------------------- Attachment AH: Report from the Apache HertzBeat Project [Chao Gong] ## Description: The mission of Apache HertzBeat is the creation and maintenance of software related to an AI-powered real-time observability system. Unified metrics and logs, centralized alerting, intelligent management and analysis. ## Project Status: Current project status: Ongoing Issues for the board: No ## Membership Data: Apache HertzBeat was founded 2025-08-20 (5 months ago) There are currently 30 committers and 19 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 Qiwei Zheng on 2025-10-04. - Ziqiu Guo was added as committer on 2025-12-08 - SiGuo Duan was added as committer on 2025-11-01 ## Project Activity: The new version 1.8.0 will be released soon. The project AI mission was discussed in the latest monthly meeting. ## Community Health: Compared with last month, the contribution level increased by roughly 20%. 16 authors have pushed 30 commits to master and 34 commits to all branches. 30 pull requests merged by 12 people. Overall the project is progressing well. We are actively attracting more production users and contributors by improving doc, enhancing stability and strengthening features. ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for January 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 December, there are 30 podlings under incubation. One successful release was made during the month, and no IP clearances were completed. No podlings graduated, and no podlings retired. There were no additions or removals to IPMC membership. Mailing list traffic during the month focused on release voting, graduation discussions, and follow-ups on reporting and potential retirement, along with updates to Incubator training materials. Two new navigation paths for the Incubator Training site were introduced: browsing by theme and browsing by topic, making it easier to locate relevant material. A search page for Incubator training resources was also added to improve discoverability across the training content. Burr, Fluss and Geaflow were invited to take part in their six-month reviews and all accepted. Several new Incubator Field Guides were published. These provide practical, experience-based advice for mentors, PPMCs and IPMC members. The guides were created by reviewing and analysing real Incubator mailing list discussions from the past five years, documenting governance in action and how the Incubator has handled recurring issues, with some AI assistance to identify patterns. Topics added include community governance, community proposals, edge cases, graduation identity, graduation readiness, graduation votes, incubation readiness, initial committer selection, licensing and provenance, naming and branding, naming and trademarks, proposal discussions, release announcements, release review issues, releases and release votes. A discussion took place regarding how podlings may establish official WeChat channels, along with broader guidance on the responsible use of chat and instant messaging platforms within incubation. A new guide on the use of emerging technologies was added, focusing on applying ASF values rather than creating new policy, preserving human accountability and highlighting privacy and licensing risks. The experimental podling health reports are being adopted and are showing measurable improvements in the quality and consistency of podling reporting. OpenServerless has begun discussion of its first release. Most podlings continue to make steady progress toward graduation. Livy continues graduation discussions, and Toree completed a release this month and plans to begin graduation discussions after the vote concludes. HugeGraph voted to graduate. A graduation discussion for Gluten uncovered several third-party branding issues, which the podling is addressing. ResilientDB and Polaris are likely to graduate soon. Baremaps is likely to retire. Pegasus is experiencing significant community attrition, with many core members having left, which has slowed development and is currently blocking both graduation discussions and release progress. The podling is working to encourage new contributors and plans to add additional committers and PPMC members in early 2026. Fesod attempted its first incubating release, which surfaced a number of ASF compliance issues. The podling is addressing those issues and plans to begin a new release vote. One podling, PonyMail, 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 - None ## Podlings that failed to report, expected next month - Pony Mail ## Graduations - None The board has motions for the following: - HugeGraph ## Releases The following releases entered distribution during the month of December: - Iggy 0.6.0 ## IP Clearance - None ## Legal / Trademarks - N/A ## Infrastructure - N/A ## Table of Contents [Amoro](#amoro) [Fesod](#fesod) [Fluss](#fluss) [Gluten](#gluten) [HugeGraph](#hugegraph) [Livy](#livy) [Pegasus](#pegasus) [ResilientDB](#resilientdb) [GeaFlow](#geaflow) -------------------- ## Amoro Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon. Amoro has been incubating since 2024-03-11. ### Three most important unfinished issues to address before graduating: 1. Fix possible and potential security vulnerability issues. 2. Release more versions under ASF. 3. Build and grow a community. ### Are there any issues that the IPMC or ASF Board need to be aware of? Currently no. ### How has the community developed since the last report? * Added 1 new Committers * Added 11 new contributors ### How has the project developed since the last report? * Merged 82 PRs ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: * 2025-09-11, released Amoro 0.8.1-incubatiing ### When were the last committers or PPMC members elected? * 2026-01-07, committer:Fei Wang(turboFei) ### Have your mentors been helpful and responsive? Yes, Amoro's mentors actively participate in the project, contribute insights, and help advance the project towards graduation. ### Is the PPMC managing the podling's brand / trademarks? Yes, everything is fine. ### Signed-off-by: - [ ] (amoro) Justin Mclean Comments: - [ ] (amoro) Zhongyi Tan Comments: - [X] (amoro) Yu Li Comments: Good to see new committer joining and community starting to prepare for graduation. - [ ] (amoro) Xinyu Zhou Comments: - [X] (amoro) Kent Yao Comments: Nice to see the community grow rapidly and come close to graduate ### IPMC/Shepherd notes: -------------------- ## Fesod Fesod is a high-performance and memory-efficient Java library for reading and writing Excel files, designed to simplify development and ensure reliability. Fesod has been incubating since 2025-09-17. ### Three most important unfinished issues to address before graduating: 1. Ensure that the website and codebase are fully compliant with ASF policies. 2. Release First version(2.0.0) under the Apache Incubator. 3. Continue to grow the community and word towards the ASF maturity Model. ### 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. The project now has already has several regular contributors. 2. Some contributors have begun proactively designing new features for project. ### How has the project developed since the last report? 1. Development of new features for the project is still ongoing. 2. We attempted to release 2.0.0-RC1 at the end of Dec, 2025 (many issues needed improvement). 3. We will begin the release attempt for 2.0.0-RC2 this week. ### How would you assess the podling's maturity? We are currently addressing issues in RC1 that do not comply with ASF specifications. We plan to initiate the release process for 2.0.0-RC2 this week. - [ ] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? N/A ### Have your mentors been helpful and responsive? We extend our special thanks to our mentors for their assistance. Particular gratitude goes to @PJ Fanning for the questions raised during the release. @tison and @Huajie Wang also provided substantial support as we worked toward releasing RC1. ### Is the PPMC managing the podling's brand / trademarks? Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246 ### Signed-off-by: - [X] (fesod) tison Comments: - [ ] (fesod) Dave Fisher Comments: - [ ] (fesod) Huajie Wang Comments: - [X] (fesod) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## Fluss Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures. Fluss has been incubating since 2025-06-04. ### Three most important unfinished issues to address before graduating: 1. The second release (v0.9.0) under the ASF incubator 2. Grow the community and attract more committers, contributors and users. 3. Fill out the maturity model ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. ### How has the community developed since the last report? 1. Add 2 new committers, currently with total 17 committers. 2. The Fluss PPMC created a [LinkedIn page](https://s.apache.org/fluss-linkedin), which now has 1,302 followers, doubling organically over the past three months. 3. [Regular Monthly Community Call](s.apache.org/fluss-community-call) for October and November; December’s call was skipped due to the holiday season. 4. An “Apache Fluss × Apache Iceberg” joint webinar is scheduled for January 20, 2026, featuring contributors from both communities. 5. Community presentations and outreach: * Jark Wu and Giannis Polyzos presented at Flink Forward Barcelona (2025-10-15) * Leonard Xu presented Fluss at QCon Shanghai (2025-10-24) * Giannis Polyzos spoke at Big Data Europe (2025-11-19) * Jark Wu presented to the CMU Database Group (2025-12-08) ### How has the project developed since the last report? - Released v0.8.0 on 2025-11-09 which is the project’s first official release under the Apache Incubator. This milestone represents 4 months of collaborative development with 400+ commits from the community. - 8 new Fluss Improvement Proposals (FIPs) were submitted over the past quarter; several have already been approved and implemented. - Active development is underway for v0.9.0, targeted for release by end of January 2026. ### How would you assess the podling's maturity? - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: Commentary: The project has successfully shipped its first Apache release and is actively growing its contributor and user base. Community engagement is strong, with regular calls, public talks, and cross-project collaboration. While still in its incubation, Fluss is steadily progressing toward graduation readiness. ### Date of last release: 2025-11-09 (v0.8.0) ### When were the last committers or PPMC members elected? 2025-11-28 ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes, everything is fine. ### Signed-off-by: - [X] (fluss) Jean-Baptiste Onofré Comments: The podling is operating great. The community is smoothly growing up. - [X] (fluss) Becket Qin Comments: - [X] (fluss) Yu Li Comments: Good to see new committers joining and vibrant community activities. - [X] (fluss) Jingsong Lee Comments: - [X] (fluss) Zili Chen Comments: ### IPMC/Shepherd notes: -------------------- ## Gluten Gluten is a middle layer responsible for offloading JVM-based SQL engines' execution to native engines. Gluten has been incubating since 2024-01-11. ### Three most important unfinished issues to address before graduating: 1. Complete more Apache releases: Plan for Gluten v1.6.0 in January. 2. Grow the community: Continue attracting and onboarding contributors to strengthen community diversity. 3. Finalize graduation preparations: Complete documentation and community consensus for transition to a top-level project. ### Are there any issues that the IPMC or ASF Board need to be aware of? Yes, under discussing a graduation proposal. ### How has the community developed since the last report? Two new Committers and Two new PPMC members joined on 2025-10-29, currently with 44 committers and 35 PPMC members ### How has the project developed since the last report? The project made significant progress in the last quarter. Apache Gluten (incubating) 1.5.0 was released on 2025-10-29, marking the fifth incubating release. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-10-29 ### When were the last committers or PPMC members elected? 2 new PPMC members were joint on 2025/10/29. ### Have your mentors been helpful and responsive? Yes. The podling’s mentors (Apache members guiding Gluten’s incubation) have been very supportive and responsive. ### Is the PPMC managing the podling's brand / trademarks? Yes. The PPMC is adequately managing Apache Gluten’s branding and trademarks. There have been no naming conflicts or misuse of the Apache brand identified. ### Signed-off-by: - [X] (gluten) Yu Li Comments: The community is well-prepared for graduation. - [X] (gluten) Wenli Zhang Comments: - [X] (gluten) Kent Yao Comments: Glad to see Gluten entering graduation progress - [X] (gluten) Shaofeng Shi Comments: - [ ] (gluten) Felix Cheung Comments: ### IPMC/Shepherd notes: -------------------- ## HugeGraph A large-scale and easy-to-use graph database HugeGraph has been incubating since 2022-01-23. ### Three most important unfinished issues to address before graduating: 1. Release 1.7.0 (Already done) 2. Prepare trademark docs / communication (Doing) 3. Start a community discussion for graduation ### 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. Add 3 new Committers (before graduation) 2. Finished GSoC & OSPP & GLCC (student OSS activities) 3. 2 topic in COC Asia ### How has the project developed since the last report? 1. Release 1.7.0 (include a string of improvement / refactor) 2. AI repo/module have got a great change 3. Support ToplingDB as RocksDB Plus ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-11-28 ### When were the last committers or PPMC members elected? 2025-09-01 ### Have your mentors been helpful and responsive? Yes, thanks for them ### Is the PPMC managing the podling's brand / trademarks? Trademark transfer is in progress. ### Signed-off-by: - [ ] (hugegraph) Lidong Dai Comments: - [ ] (hugegraph) Trista Pan Comments: - [ ] (hugegraph) Xiangdong Huang Comments: - [X] (hugegraph) Yu Li Comments: The community is well-prepared for graduation. - [ ] (hugegraph) Willem Ning Jiang Comments: ### IPMC/Shepherd notes: -------------------- ## Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. ### Three most important unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Keep the project up to date with security fixes and in terms of Spark support ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. Currently working on releasing a new version, RC voting will be restarted in a few days. ### How has the community developed since the last report? We have received PRs and merged several PRs, dev mailing list is more active. ### How has the project developed since the last report? PRs merged including JDK 17 upgrade, Spark 2 and Python 2 decommission. New release branch and RC has been created. ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I think it's worth to start discussion graduation. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [ ] (livy) Larry McCay Comments: - [X] (livy) Gyorgy Gal Comments: ### IPMC/Shepherd notes: -------------------- ## Pegasus Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance. Pegasus has been incubating since 2020-06-28. ### Three most important unfinished issues to address before graduating: 1. The graduation discussion has been initiated, but not enough PPMC members have participated yet; therefore, the discussion is still blocked. And we are working to request the current PPMC members and promote active committers to become PPMC members in order to continue this process. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? Many core members of the project have left, leading to a decline in community activity and consequently blocking the graduation discussion and releases. We are working to encourage other contributors in the community to help us accelerate the release process, with the goal of producing a new release within 2026. In addition, we will promote voting to elect active contributors as new committers or PPMC members. ### How has the community developed since the last report? There are 2 new contributors who have joined the project development. ### How has the project developed since the last report? A total of 18 commits from 6 contributors were merged, including fixes for some bugs in unit tests, shell tools and the Go/Python clients, work on the Go collector, as well as some code refactoring. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2023-12-12 ### When were the last committers or PPMC members elected? 2024-09-26 ### Have your mentors been helpful and responsive? No issues were encountered that required mentor assistance. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [X] (pegasus) Duo Zhang Comments: - [X] (pegasus) Liang Chen Comments: - [ ] (pegasus) Von Gosling Comments: - [ ] (pegasus) Liu Xun Comments: ### IPMC/Shepherd notes: -------------------- ## ResilientDB ResilientDB is a distributed blockchain framework that is open-source, lightweight, modular, and highly performant. ResilientDB has been incubating since 2023-10-21. ### Three most important unfinished issues to address before graduating: 1. Nothing more to be done. 2. 3. ### 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? Add three new PPMC members ### How has the project developed since the last report? We are preparing for the graduation process. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-10 (1.11.0) ### When were the last committers or PPMC members elected? 2025-11 ### Have your mentors been helpful and responsive? No issues. ### Is the PPMC managing the podling's brand / trademarks? No ### Signed-off-by: - [ ] (resilientdb) Junping Du Comments: - [ ] (resilientdb) Kevin Ratnasekera Comments: - [X] (resilientdb) Jean-Baptiste Onofré Comments: The podling is close to graduation. I would suggest a new release at least. ### 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. ### Three 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, documentation updates, and dependency maintenance. Additionally, several PRs are currently under review. ### How has the project developed since the last report? Over the past month, the GeaFlow project has focused on feature enhancements, optimizations, and dependency updates. Key changes are including: + Adding support for vector stores (#637). + Implementing a classifier to address ISSUE701 (#720). + Optimizing hardcoded constants and magic numbers (#674). + Updating documentation URLs (#721). + Upgrading the lz4-java dependency from 1.9.0 to 1.10.1 (#715). + Updating the version to 0.8.0-SNAPSHOT after cherry-picking fixes from the 0.7.0 release (#712). These updates demonstrate continued development in functionality expansion, code quality improvements, and dependency management. ### 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 first community version was released on November 19th. ### When were the last committers or PPMC members elected? This month, we held committer votes for two candidates: Leomrlin has been approved, while kitalkuyo-gita remains under observation to assess whether his contributions align with our project requirements. ### 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: - [ ] (GeaFlow) Willem Ning Jiang - [X] (GeaFlow) xinwang - [X] (GeaFlow) lzljs3620320 - [ ] (GeaFlow) jmclean - [ ] (GeaFlow) paulk ----------------------------------------- Attachment AJ: Report from the Apache InLong Project [Charles Zhang] ----------------------------------------- Attachment AK: Report from the Apache James Project [Benoit Tellier] ## Description: The Apache James Project delivers a rich set of open source modules and libraries, written in Java, related to Internet mail which build into an advanced extensible mail server running on the JVM. ## Project Status: Current project status: Ongoing, moderate activity. Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache James was founded 2003-01-22 (23 years ago) There are currently 43 committers and 19 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 René Cordier on 2025-02-03. - No new committers. Last addition was Quan Tran on 2025-02-05. ## Project Activity: Recent releases: - JAMES-3.9.0 was released on 2025-10-03. - MIME4J-0.8.13 was released on 2025-07-25. - JDKIM-0.4 was released on 2025-03-04. We received promising contributions regarding ARC (RFC-8617) that contributors are actively working on. Works is also going on to integrate ManageSieve with OIDC. ## Community Health: server-dev@james.apache.org had a 16% decrease in traffic in the past quarter (113 emails compared to 134) server-user@james.apache.org had a 58% decrease in traffic in the past quarter (18 emails compared to 42) While the developer traffic tend to be stable we have a decrease in user traffic ----------------------------------------- Attachment AL: Report from the Apache Jena Project [Andy Seaborne] ## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Jena was founded 2012-04-18 (14 years ago) There are currently 20 committers and 14 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 Arne Bernhardt on 2024-04-05. - No new committers. Last addition was Sergei Zuev on 2024-08-01. ## Project Activity: Jena 5.6.0 was released on 2025-10-15. The next release is planned to be Jena 6.0.0 and this is under development. This next release is an opportunity to remove old features, which where signalled for removal in version 5.6.0, and to move to supporting the last two Java LTS, 21 and 2 in keeping with the project policy. ## Community Health: The github issues continues to be the primary channel for external users to report bugs and to ask questions as well as being the record of development. There are about the same number of closed issues for version 6.0.0 as for version 5.6.0. ----------------------------------------- Attachment AM: Report from the Apache JMeter Project [Bruno (Milamber) Demion] ## Description: The mission of JMeter is the creation and maintenance of software related to Java performance and functional testing ## Project Status: Current project status: Ongoing, with low activity Issues for the board: There are no issues requiring board attention at this time. - Question from board: > Data indicates that no new committers or PMC members > have been added to the project recently. What challenges is your community > facing in bringing in new contributors? Have you considered initiatives like > GSoC or lowering the committer selection bar to encourage participation? - Response: The project is functionally very complete and has an active ecosystem of extensions outside of ASF, for adding and developing new features. Therefore, activity around the core JMeter is relatively low. We are not actively seeking to recruit new contributors for new features. But we missing some active committers to triage and fix bugs in Github issues. ## Membership Data: Apache JMeter was founded 2011-10-26 (14 years ago) Jakarta JMeter, first version was released 1998-12-15 (28 years ago) There are currently 13 committers and 8 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 Vladimir Sitnikov on 2018-06-08. - No new committers. Last addition was Maxime Chassagneux on 2017-02-15. ## Project Activity: - Current (low) objective is to move the code base of JMeter to Java 17+ (from Java 8) for next major release (6.0) - Recent releases: 5.6.3 final was released on 2024-01-07. ## Community Health: - The project has a low activity during last quarter. - The JMeter's users continue to send issues in Github (we have ~50 issues that still opens for year 2025), but we missing some active committers to triage / fix the tickets. ----------------------------------------- Attachment AN: Report from the Apache Johnzon Project [Jean-Louis Monteiro] ----------------------------------------- Attachment AO: Report from the Apache JSPWiki Project [Juan Pablo Santos] ## Description: The mission of JSPWiki is the creation and maintenance of software related to Leading open source WikiWiki engine, feature-rich and built around standard JEE components (Java, servlets, JSP). ## Project Status: Current project status: Ongoing, with low activity. Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache JSPWiki was founded 2013-07-17 (12 years ago) There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - Alex O'Ree was added to the PMC on 2025-11-06 - Alex O'Ree was added as committer on 2025-11-07 ## Project Activity: Alex O'Ree joined JSPWiki this quarter, bringing a lot of energy to the project. Most notable activity this quarter revolved around fixing long-standing issues, security findings, administration-related capabilities and dependency updates. A big portion of the security findings have been sitting on JIRA for a very long time, and never were discussed on private. Most probably they were filed on JIRA under incubation, but ended up falling through the cracks. We're still discussing one security issue, after which we will focus on releasing 3.0.0. ## Community Health: Work on latest master shows commits from three committers. No questions unanswered on MLs, although they continue to have very little traffic, aside from JIRA/GitHub generated mails. ----------------------------------------- Attachment AP: Report from the Apache Kudu Project [Andrew Wong] ## Description: The mission of Apache Kudu is the creation and maintenance of software related to a distributed columnar storage engine built for the Apache Hadoop ecosystem. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kudu was founded 2016-07-19 (9 years ago) There are currently 33 committers and 33 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Chovan Zoltan was added to the PMC on 2025-11-17 - Chovan Zoltan was added as committer on 2025-11-17 ## Project Activity: - 1.18.1 was released on 2026-01-09 - 1.18.0 was released on 2025-07-10 - 1.17.1 was released on 2024-11-15. ## Community Health: - Development activity measured in the number of commits and the number of unique developers has remained constant. - Traffic to dev mailing lists increased by 177%. This is primarily due to release process related mails. - Traffic to reviews mailing lists dropped by 34% due to the holiday season. - Community activity measured in community Slack is as follows: (the number of weekly active users dipped by 1.6%, and weekly public posters increased by 21%). ----------------------------------------- Attachment AQ: Report from the Apache Libcloud Project [Tomaž Muraus] ----------------------------------------- Attachment AR: Report from the Apache Lucene.Net Project [Shad Storhaug] ----------------------------------------- Attachment AS: Report from the Apache MADlib Project [Ed Espino] ----------------------------------------- Attachment AT: Report from the Apache Mahout Project [Shannon Quinn] ## Description: The mission of Mahout is scalable matrix math ## Project Status: Current project status: 10/10 community health Issues for the board: None ## Membership Data: Apache Mahout was founded 2010-04-20 (16 years ago) There are currently 33 committers and 11 PMC members in this project. The Committer-to-PMC ratio is 3:1. Community changes, past quarter: - Guan-Ming Chiu was added to the PMC on 2025-11-24 - Guan-Ming Chiu was added as committer on 2025-11-04 - Ryan Huang was added as committer on 2026-01-14 - Rich Huang was added as committer on 2025-12-02 ## Project Activity: Several new contributors have built out our new Quantum Data Plane (QDP). It merged last week. We're working with the Apache Trusted Releases (ATR) pipeline to cut our next release. ## Community Health: Continued community meetings with some great new contributors, who have in turn recruited their friends from real life. ----------------------------------------- Attachment AU: Report from the Apache Maven Project [Hervé Boutemy] ## Description: The mission of Maven is the creation and maintenance of software related to Java project management and comprehension tools ## Project Status: Current project status: ongoing with high activity. Issues for the board: none. ## Membership Data: Apache Maven was founded 2003-03-01 (23 years ago) There are currently 73 committers and 30 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 Romain Manni-Bucau on 2023-10-16. - Christoph Läubrich was added as committer on 2025-11-07 ## Project Activity: Releases since last report: - Apache Parent POM 37 was released on 2026-01-09. - Apache Maven Parent POMs 47 was released on 2026-01-09. - Apache Maven Plugin Testing 3.5.0 was released on 2026-01-07. - Apache Maven Parent POMs 46 was released on 2026-01-03. - Apache Parent POM 36 was released on 2026-01-03. - Maven Resolver 2.0.14 was released on 2025-12-15. - Apache Maven 3.9.12 was released on 2025-12-13. - Maven Release 3.3.1 was released on 2025-12-09. - Maven Resolver 1.9.25 was released on 2025-12-06. - Maven Release 3.3.0 was released on 2025-11-30. - Maven ACR Plugin 3.2.0 was released on 2025-11-25. - Apache Maven WAR Plugin 3.5.1 was released on 2025-11-24. - Maven DOAP Plugin 3.0.0-M1 was released on 2025-11-24. - Maven Assembly Plugin 3.8.0 was released on 2025-11-22. - Maven Resources Plugin 3.4.0 was released on 2025-11-22. - Maven Source Plugin 3.4.0 was released on 2025-11-22. - Maven EJB plugin 3.3.0 was released on 2025-11-16. - Apache Maven 4.0.0-rc-5 was released 2025-11-13. - Apache Maven JAR Plugin 3.5.0 was released on 2025-11-11. - Maven RAR plugin 3.1.0 was released on 2025-11-09. - Maven Release 3.2.0 was released on 2025-11-08. Maven 4.0 RC-5 has been released, work is in progress for a final RC-6 before doing the final 4.0.0. Work is progressing on better Java Module support with modular sources. ## Community Health: Users mailing list activity remains quite low. For developers, mailing list is used for votes and a few discussions focused on Maven code and evolution: a lot of unstructured and diverse discussions happen on Slack, like debugging or very diverse interests about Maven wider ecosystem. ----------------------------------------- Attachment AV: Report from the Apache MINA Project [Thomas Wolf] ## Description: The mission of MINA is the creation and maintenance of software related to Multipurpose Infrastructure for Network Applications. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache MINA was founded 2006-10-25 (19 years ago) There are currently 28 committers and 15 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 Gary D. Gregory on 2023-09-13. - No new committers. Last addition was Gary D. Gregory on 2022-03-24. ## Project Activity: * Apache MINA: an asynchronous I/O library. Latest release was 2.2.5 on 2025-11-28. The release contained a bug fix for which back-porting to the 2.0.x and 2.1.x branches is being considered. The project is mature & stable; there is low development activity. * Apache MINA SSHD: library for client- and server-side SSH. The project is mature & stable and sees active development. Work towards 3.0.0 continues; a second milestone pre-release 3.0.0-M2 was released on 2025-10-25. A new release 2.17.0 for the mainline branch is planned for January. * Apache MINA FtpServer: FTP server library. Project in maintenance mode; no activity. * Vysper & AsyncWeb are dormant. One Github PR (pull request) was merged in November in Vysper. ## Community Health: The community is small but healthy. We get occasional PRs through Github, but most users of the libraries contribute only by reporting issues. Posts on the mailing lists or as JIRA or Github issues get replies promptly. Activity this quarter was even lower than usual, presumably due to the holiday season. ----------------------------------------- Attachment AW: Report from the Apache MyFaces Project [Bernd Bohmann] ## Description: The mission of MyFaces is the creation and maintenance of software related to JavaServer(tm) Faces implementation and components ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: None ## Membership Data: Apache MyFaces was founded 2005-02-23 (21 years ago) There are currently 81 committers and 47 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 Melloware on 2024-01-25. - No new committers. Last addition was Milan Siebenbürger on 2024-01-24. ## Project Activity: The community is working on Quarkus improvements and spec updates and small fixes in myfaces-core. In tobago adding small features and fixes. Recent releases: - tobago-6.9.0 was released on 2025-11-30. - myfaces-core-4.1.2 was released on 2025-11-17. - tobago-6.8.1 was released on 2025-09-05. ## Community Health: - Apache MyFaces Core is healthy. UI-Component Sets: - Apache Tobago is healthy. - Apache Trinidad is in maintenance mode. Last developer commit was Sept 2017. - Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016. Last commit on behalf of a contributor was May 2016. Add-ons and Extensions: - Apache MyFaces Portlet Bridge is in maintenance mode. Last developer commit was Jan 2014. Last commit on behalf of a contributor was May 2015. - Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache DeltaSpike so new development happens there. Last commit March 2014. - Apache MyFaces Orchestra is in maintenance mode. New projects use CDI and DeltaSpike instead. Last commit on behalf of a contributor was August 2016. - Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014. - Apache MyFaces Commons is in maintenance mode. Last commit August 2012. - Apache MyFaces Ext-Scripting is in maintenance mode. Last commit Sept 2017. - Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last commit May 2017. ----------------------------------------- Attachment AX: Report from the Apache NiFi Project [David Handermann] ## Description: The mission of NiFi is the creation and maintenance of software related to providing an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi MiNiFi is an edge data collection agent built to seamlessly integrate with and leverage the command and control of NiFi. There are both Java and C++ implementations. Apache NiFi Registry is a centralized registry for key configuration items including flow versions, assets, and extensions for Apache NiFi and Apache MiNiFi. Apache NiFi NAR Maven Plugin is an extension for Apache Maven supporting NiFi Archive creation for runtime isolated class loading. Apache NiFi Flow Design System is a theme-able set of high quality UI components and utilities for use across the various Apache NiFi web applications in order to provide a more consistent user experience. ## Project Status: Current project status: Ongoing with high activity Issues for the board: None ## Membership Data: Apache NiFi was founded 2015-07-14 (10 years ago) There are currently 55 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - Mark Bathori was added to the PMC on 2025-11-11 - Rob Fellows was added to the PMC on 2025-11-11 - Shane Ardell was added as committer on 2025-11-21 ## Project Activity: Apache NiFi released version 2.7.0 on 2025-12-09. This release included several important bugs related to renaming component properties, which exposed some issues with automated framework upgrades processes. These issues prompted the rapid release of version 2.7.1 on 2025-12-12 and 2.7.2 on 2025-12-17. Although the initial 2.7.0 version highlighted some gaps in framework upgrade features, the identification, resolution, and subsequent releases highlight strong community engagement and the responsiveness of project contributors. The project also released Apache NiFi API 2.4.0 on 2025-10-16 and Apache NiFi API 2.5.0 on 2025-11-08. The decoupled release process for the Apache NiFi API and the Apache NiFi application continue provide a useful implementation strategy for features that impact public-facing extension interfaces and classes. The project published CVE-2025-66524 on 2025-12-19 in response to a notification from Jaeyeong Lee. Although the vulnerability is high severity due to deserialization of untrusted data, the impact was limited in scope to a particular extension component, making it straightforward to resolve and mitigate for current installations. Apache NiFi 2.7.0 resolved the vulnerability, and the disclosure notice described an optional mitigation. ## Community Health: Community health remains strong, with the addition of two PMC members and one committer, all of whom have contributed steadily to the project over multiple years. Mailing list activity remains steady, with an incremental increase in traffic on the users list over the previous quarter. Participation on Slack also remains steady, approaching 4000 members. The number of followers on Linked has passed 3500, adding over 300 from the previous quarter. The community has had several important discussions on the future of the MiNiFi and NiFi Registry sub-projects. These discussions have included proposals to decouple MiNiFi from the main NiFi project, and a proposal to deprecate NiFi Registry in favor of alternatives that now provide direct access to versioning services such as GitHub and GitLab. The discussion on MiNiFi did not result in any definitive changes for now. The discussion on NiFi Registry is ongoing. The PMC continues to engage actively with committers and interested users, balancing historical and desired features with available maintainer cycles and future project direction. ----------------------------------------- Attachment AY: Report from the Apache Nutch Project [Sebastian Nagel] ## Description: Apache Nutch is a highly extensible and scalable open source web crawler software project based on Apache Hadoop® data structures and the MapReduce data processing framework. ## Project Status: Current project status: ongoing with medium to low activity Issues for the board: none ## Membership Data: Apache Nutch was founded 2010-04-21 (15 years ago) There are currently 23 committers and 23 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Joe Gilvary on 2024-08-07. - No new committers. Last addition was Joe Gilvary on 2024-08-07. ## Project Activity: 1.21 was released on 2025-07-21. Work ongoing or finished in the last quarter include a rework and consolidation of the job metrics, support for ZStandard HTTP Content-Encoding, full support to build Nutch using Java 17, moving from Ant to Gradle as build system and multiple dependency upgrades. ## Community Health: The number of contributions (Jira issues, commits, activity on the mailing lists) is on a low, but steady level. ----------------------------------------- Attachment AZ: Report from the Apache NuttX Project [Alin Jerpelea] ## Description: The mission of Apache NuttX is the creation and maintenance of software related to a mature, real-time embedded operating system (RTOS) ## Project Status: Current project status: Ongoing: With high activity Issues for the board: No issues ## Membership Data: Apache NuttX was founded 2022-11-16 (3 years ago) There are currently 38 committers and 24 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Matteo Golin was added to the PMC on 2025-11-10 - Michal Lenc was added as committer on 2025-11-19 The project is attracting new contributors with various backgrounds which improves not only the code quality but also security and documentation ## Project Activity: The project is commited on releasing every quarter and we are proud to announce that NuttX 12.12.0 was released on 2025-12-31. The project implemented the SPDX headers to facilitate the SBOM compliance. ## Community Health: Project communication on mailing list is increasing for meaningful topics while casual conversation is happening on Discord The community has worked on several iterations of contribution guidelines and enforced them through CI which improved a lot maintainers life, readability and education. ----------------------------------------- Attachment BA: Report from the Apache OpenJPA Project [Mark Struberg] ----------------------------------------- Attachment BB: Report from the Apache OpenMeetings Project [Maxim Solodovnik] ## Description: The mission of OpenMeetings is the creation and maintenance of software related to OpenMeetings: Web-Conferencing and real-time collaboration ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache OpenMeetings was founded 2013-01-25 (13 years ago) There are currently 30 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. Community changes, past quarter: - No new PMC members. Last addition was Ali Alhaidary on 2021-03-22. - No new committers. Last addition was Ali Alhaidary on 2021-04-07. ## Project Activity: We are currently working at 8.2.0 release (including dependencies and site update). The work was delayed due to my vacation Recent releases: - 8.1.0 was released on 2025-09-12. - 8.0.0 was released on 2025-01-02. - 7.2.0 was released on 2023-12-23. ## Community Health: The project seems to be very silent. We are answering emails in timely manner, but there are not many of them. ----------------------------------------- Attachment BC: Report from the Apache OpenOffice Project [Keith McKenna] 2026 January ## Description The mission of OpenOffice is the creation and maintenance of software related to an open-source office-document productivity suite. ## Project Composition Apache OpenOffice was founded on 2012-10-16 (13 years ago). There are currently 141 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. No new PMC members. The last addition was Czesław Wolański on 2023-01-14. One new committer. John Bampton was added on 2025-01-07. ## Project Activity ### Recent Releases 4.1.16 was released on 2025-11-10 4.1.15 was released on 2023-12-22 4.1.14 was released on 2023-02-27 4.1.13 was released on 2022-07-22 Binary downloads (total overall) as of 2026-01-04: 395,976,603 ### Codebase in OpenOffice repository Work continues on the 4.2 future release. This included work on building a 64-bit Windows version. Work on code spelling and code linting. dev@openoffice.apache.org had a 70% increase in traffic in the past quarter (273 emails compared to 160): We have initiated a discussion about a roadmap. ### Documentation The OpenOffice-docs repository is where the small documentation team makes updates. The chapters and complete Book of the Calc Guide have been published. The Chapters and the complete book of the Impress Guide have been published. doc@openoffice.apache.org had a 53% decrease in traffic in the past quarter (22 emails compared to 46): The OpenOffice.org repository has had the usual Download count updates. ### User Support User Forums (forum.openoffice.org) remain active in English, Spanish, French, Hungarian, Italian, Japanese, Dutch, and Polish. users@openoffice.apache.org had a 32% increase in traffic in the past quarter (57 emails compared to 43): users-de@openoffice.apache.org had a 23% decrease in traffic in the past quarter (31 emails compared to 40): ### Translation Interface The migration progresses slowly. We have managed to push the local from the local repository on the machine to GitBox. This gives us more flexibility. The next step is to establish the translation process between Pootle files and SDF files. The latter are used by OpenOffice. In parallel, we investigate Weblate as a replacement for Pootle. If a transition can be done smoothly, we will directly migrate to Weblate. If blockers pop up, we return to the Pootle migration. ### Templates and Extensions Site These sites will be transitioned to static HTML sites by SourceForge. The template site has been completed. We are investigating and planning a new service. ### Community Health Community overall health is improving. We are seeing several developers taking on Win64, ODF 1.3, Boost, NSS, ICU, and OpenSSL updates. Documentation is being updated after a long time, and we are getting translation volunteers. ## Infrastructure ### Binary Distributions SourceForge mirrors are still the main way to get an OpenOffice binary release. Windows builds are also published in the Microsoft Store (Windows 10/11). Windows users are by far our largest user group. Windows 10 and 11 Users can also install the binaries via WinGet. On both systems, we sign only the installers and are ready to use the new service provided by SSL.com. A PMC discussion has been started about whether we can sign the complete product of AOO. ### OpenGrok OpenGrok now runs on a Docker setup. We see some minor issues. ### Facebook We have one volunteer taking care of the presence. Work is underway to invite more volunteers. There are some comments in the comment section, mostly user support. ### X, formerly Twitter The PMC voted to continue our handle, and we have new volunteer PMC members who will handle our presence. The main purpose will be advertising new releases. ### Unmaintained Python 2 code Python 2 is unmaintained. We have in the development tree the external python3 support. Internal Python 3 support is difficult. We are checking alternatives. Planned for the next major release. We have started the work on a new approach to Python scripting support in AOO. ### OpenDocument Format (ODF) Version 1.3 Our default and best-supported file format, the OpenDocument Format, has received a new standard update. As we plan to support this format, we started Work checking the ODF 1.3 specification and what we have to do to support documents in OpenDocument Format version 1.3 (see https://cwiki.apache.org/confluence/display/OOOUSERS/ODF+1.3+Changes), as well as some early development. ----------------------------------------- Attachment BD: Report from the Apache ORC Project [William Hyun] ----------------------------------------- Attachment BE: Report from the Apache Parquet Project [Julien Le Dem] ## Description: A column-oriented data file format designed for efficient data storage and retrieval. It provides high performance compression and encoding schemes to handle complex data in bulk and is supported in many programming languages and analytics tools. Parquet consists of a format specification (the Parquet format) and several implementations, one of which (Parquet Java) is developed directly under the umbrella of the Apache Parquet project. Several implementations such as Parquet C++, Parquet Go, and Parquet Rust are developed as part of the Apache Arrow project. Non-Apache implementations also exist, some of them closed source. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Parquet was founded 2015-04-21 (11 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: - No new PMC members. Last addition was Fokko Driesprong on 2025-01-23. - No new committers. Last addition was Andrew Lamb on 2025-09-30. ## Project Activity: Parquet Java 1.16.0 was released on 2025-09-03. Java 1.17.0 was released on 2026-01-13. Parquet Format 2.12.0 was released on 2025-08-28. Parquet rust (part of arrow-rust): Arrow RS-57.2.0 was released on 2026-01-11. Parquet cpp (part of arrow-cpp): Arrow 22.0.0 was released on 2025-10-24. Parquet go (part of arrow-go): Arrow GO-18.5.0 was released on 2025-12-12 Work in progress: - New encoding POCs in progress: ALP: The spec is ready for review. Numbers from the evaluation are strong. FSST: Active proposal, currently being finalized by the community. FSST PoC implementation is ready, we should be able to move forward to the implementation stage in ~2 weeks after the community review. PFOR: initial PoC and discussion started New discussion started on supporting composite encodings in Parquet: Active proposals and benchmarks are released, currently being reviewed by the community. - New flatbuffer based metadata: spec in review ## Community Health: Discussions are regularly happening on the mailing list, in PRs/Issues on Github and on a regular sync meeting held on zoom (notes are posted on the list) https://reporter.apache.org/chi.py#parquet Chi for Apache Parquet: Healthy (7.96) ----------------------------------------- Attachment BF: Report from the Apache PDFBox Project [Andreas Lehmkühler] ## Description: The mission of PDFBox is the creation and maintenance of software related to Java library for working with PDF documents ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: none ## Membership Data: Apache PDFBox was founded 2009-10-21 (16 years ago) There are currently 21 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Matthäus Mayer on 2017-10-16. - No new committers. Last addition was Joerg O. Henne on 2017-10-09. ## Project Activity: Recent releases: 3.0.6 was released on 2025-10-16. 2.0.35 was released on 2025-10-02. 3.0.5 was released on 2025-05-01. ## Community Health: - there is a steady stream of contributions, bug reports and questions on the mailing lists - another 3.0.x will likely be released in a couple of days (delay due to a telekom problem) - another 2.0.x will likely be released a week after that ----------------------------------------- Attachment BG: Report from the Apache Petri Project [Greg Stein] ----------------------------------------- Attachment BH: Report from the Apache PLC4X Project [César García] ## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Project Status: Current project status: Ongoing with medium activity Issues for the board: None ## Membership Data: Apache PLC4X was founded 2019-04-16 (7 years ago) There are currently 21 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Unai Lería Fortea on 2025-09-28. - No new committers. Last addition was Unai Lería Fortea on 2025-06-11. ## Project Activity: - We released version 0.13.1 which fixed some bugs in 0.13.0. - Work is underway on a new version of the basic services (SPI3), which aims to eliminate dependence on other libraries. - The project secured funding from Nlnet, which will allow time to be invested in reducing outstanding issues. ## Community Health: - In general, the core community remains active on both the mailing list and the Slack platform, as well as interacting on professional social networks. - The traffic generated is mainly related to the addition of new features, bug fixes and, to a lesser extent, the addition of new features which are managed by project members and specific contributions. - On professional social networks, specifically LinkedIn, there is an increase in interest in the project, currently having 671, which indicates an approximate increase of 17,5%. ----------------------------------------- Attachment BI: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic] ----------------------------------------- Attachment BJ: Report from the Apache Pulsar Project [Matteo Merli] ----------------------------------------- Attachment BK: Report from the Apache Ranger Project [Selvamohan Neethiraj] ## Description: Apache Ranger is a framework for centralized, policy-based authorization, auditing, and governance across multiple data processing and storage services. ## Issues: There are no issues requiring Board attention at this time. ## Membership Data: - Apache Ranger was founded on 2017-01-17. - The project has 39 committers and 18 PMC members. - The PMC remains active in releases, reviews, and project governance. ## Community changes, past quarter: - No new PMC members. - No new committers. - Last PMC addition: Abhishek Kumar on 2025-09-18. - Last committer addition: Fateh Singh on 2024-10-14. ## Project Activity: - Ranger 2.8.0 release is in progress and targeted for Q1 2026, with the release process proceeding normally under active PMC oversight. - 2.8.0 release will address 35+ bugs and multiple functional and operational improvements. - Key improvements in 2.8.0 release - Optimized role cache modification in Ranger Admin - Upgraded to later version of Elasticsearch - Improvements to Search Filters - Improvements to AuditLogFilters to exclude based on resource names. - Upgrades libraries (axios, bouncycastle, tomcat, ...) - Support for Kerberized Solr in Ranger Admin Installation - Update Docker setup for latest supported Trino release ## Community Health: Community activity remains steady with a modest quarter-over-quarter normalization across mailing lists, issue tracking, and code contributions. Lower activity on user@ reflects reduced support traffic this quarter rather than loss of adoption. - 686 emails in dev@ranger.apache.org in this quarter (- 20% change from past quarter) - 0 emails in user@ranger.apache.org in this quarter (-100% change from past quarter) - 77 issues opened in JIRA in this quarter (- 34% change from past quarter) - 60 issues closed in JIRA in this quarter (- 23% change from past quarter) - 88 PRs opened on GitHub in this quarter (- 5% change from past quarter) - 74 PRs closed on GitHub in this quarter (- 17% change from past quarter) - 62 Commits on the master branch in this quarter (- 13% change from past quarter) - 19 code contributors (authors) in this quarter (- 11% change from past quarter) ## Most Recent releases: The project has maintained a regular release cadence over the past year. - Apache Ranger 2.7.0 was released on 2025-07-30. - Apache Ranger 2.6.0 was released on 2025-02-15. - Apache Ranger 2.5.0 was released on 2024-08-07. ----------------------------------------- Attachment BL: Report from the Apache Ratis Project [Tsz-wo Sze] ## Description: The mission of Apache Ratis is the creation and maintenance of software related to a highly customizable Raft protocol implementation in Java. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Ratis was founded 2021-02-16 (5 years ago) There are currently 31 committers and 20 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 Xinyu Tan on 2025-06-22. - No new committers. Last addition was Xinyu Tan on 2024-08-27. ## Project Activity: We released Ratis 3.2.1 on 2025-11-12. The release was a maintenance release with Ratis Thirdparty upgrade, bug fixes and minor improvements over the 3.2.0 release. Both Apache Ozone and Apache IoTDB have been upgraded to Ratis 3.2.1. We added a weekly CVE vulnerability check github action workflow. It uses org.owasp:dependency-check-maven to scan the dependencies. ## Community Health: The project is healthy. In this quarter, we have higher traffic in the user@ (7 emails compared to 2) but a lower traffic in the dev@ (32 emails compared to 42) mailing lists compared to the previous quarter. We have roughly 44 JIRAs resolved while 34 JIRAs have been created in the last 90 days. ----------------------------------------- Attachment BM: Report from the Apache RocketMQ Project [Xiaorui Wang] ----------------------------------------- Attachment BN: Report from the Apache Royale Project [Yishay Weiss] ----------------------------------------- Attachment BO: Report from the Apache Rya Project [Adina Crainiceanu] ## Description: The mission of Apache Rya is the creation and maintenance of software related to scalable storage, retrieval, and analysis of RDF data ## Project Status: Current project status: dormant Issues for the board: none ## Membership Data: Apache Rya was founded 2019-09-17 (6 years ago) There are currently 12 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members since project became a top-level project. Last addition was David Lotts on 2016-11-17 - No new committers were added. ## Project Activity: No new activity. Last release 4.0.1 was on 2020-12-22 ## Community Health: There is no current activity in the project. The software is used in production by users. The project is in "dormant" state: not much happening on the code, but at least 3 PMC members ready to engage if needed. dev@rya.apache.org had a 0% decrease in traffic in the past quarter (3 emails compared to 3) ----------------------------------------- Attachment BP: Report from the Apache Samza Project [Jagadish Venkatraman] ## Description: The mission of Samza is the creation and maintenance of software related to distributed stream processing framework ## Project Status: Current project status: Dormant Issues for the board:no issues require attention of the board ## Membership Data: Apache Samza was founded 2015-01-22 (11 years ago) There are currently 31 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Bharath Kumarasubramanian on 2020-02-13. - No new committers. Last addition was Shekhar Sharma on 2024-04-21. ## Project Activity: Project activity has plateaued over the last quarters. Samza continues to power critical stream processing workloads at several companies. ## Community Health: Had an in person and online community meetup on Nov 18, 2025 that was well attended: "Stream Processing with Apache Kafka, Samza, and Flink" ----------------------------------------- Attachment BQ: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ----------------------------------------- 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: - Add the implementations of the autograd models for SINGA PEFT. - Add the multiprocess implementations for SINGA PEFT. - Add the implementation of distributed models for SINGA PEFT. - Update the documentation and implementations of the candidiasis disease application. - Update the documentation and implementations of the cardiovascular disease application. - Restructure the healthcare application folders. ## Community Health: According to the statistics, there are more email traffic and commits in the Github, which shows that the community is active in the development. ----------------------------------------- Attachment BS: Report from the Apache SkyWalking Project [Sheng Wu] ## Description: The mission of Apache SkyWalking is the creation and maintenance of software related to application performance management and monitoring (APM) ## Project Status: Current project status: Ongoing Issues for the board: No ## Membership Data: Apache SkyWalking was founded 2019-04-17 (7 years ago) There are currently 62 committers and 35 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 Zixin Zhou on 2024-12-30. - No new committers. Last addition was Claire Chen on 2024-05-27. ## Project Activity: SkyWalking released the following versions. - helm-4.8.0: 2025-12-29 - banyandb-helm-0.5.3: 2025-12-07 - banyandb-0.9.0: 2025-11-27 - banyandb-helm-0.5.2: 2025-11-24 - banyandb-helm-0.5.1: 2025-11-17 - banyandb-helm-0.5.0: 2025-11-01 - eyes-0.8.0: 2025-10-27 - banyandb-java-client-0.9.1: 2025-10-15 - banyandb-java-client-0.9.0: 2025-09-30 BanyanDB is the community's major focus. Some new users have began to move from Elasticsearch(Elastic License) to BanyanDB(APLv2) due to both license concern and better performance provided. ## Community Health: The community is healthy. GitHub discussion and Slack channels are active. 10.3.0 + 0.9 BanyanDB is out, new adoptions just begin. Although no new committer is selected, the community scale keeps growing. The number of contributors(GitHub based) is 968. We are looking forward to the 1000th contributor milestone. ----------------------------------------- Attachment BT: Report from the Apache Steve Project [Greg Stein] ----------------------------------------- Attachment BU: 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. # Project Activity: We have updated the project's website and README The proposal to support Cloud Serverless Flink is under discussion. New version 2.1.7 released. 3 CVE fixed ----------------------------------------- Attachment BV: Report from the Apache Struts Project [René Gielen] ## Description: The Apache Struts MVC framework is a solution stack for creating modern and elegant action-based Java web applications. It favours convention over configuration, is extensible using a plugin architecture, and ships with plugins to support patterns and technologies such as REST, AJAX and JSON. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Struts was founded 2004-03-17 (22 years ago) There are currently 60 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Kusal Kithul-Godage on 2024-02-24. - No new committers. Last addition was Kusal Kithul-Godage on 2023-08-03. ## Project Activity: The Struts team made two framework releases in the reporting period: - Struts 7.1.1 - Bug Fix, Improvements and Feature Release (2025-10-18) [1] - Struts 6.8.0 - Bug Fix and Improvements Release (2025-10-05) [2] The last Struts releases besides the core framework were - Struts Annotations 2.0.0 - Enhancements and JDK 17 support (2025-07-03) - Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06) Within the last quarter, we saw slightly decreased activity compared to the preceding period. Nevertheless, the team made two GA releases and worked behind the scenes on security reports. This resulted into two newly released Security Bulletins: - S2-068 - File leak in multipart request processing causes disk exhaustion (DoS) [3] - S2-069 - XXE vulnerability in XWork component [4] We thank the reporters, as well as the Apache Security team for their help and support. We have no issues that require board assistance at this time. ## Community Health ### Development activity in the reporting period 26 JIRA were tickets opened and 24 closed in the past quarter. We had 143 PRs opened and 143 closed in the main project. It is notable that we had an unusual high number of automated PRs created by dependabot, due to dependency upgrades. ### Mailing list activity: - dev@struts.apache.org had a 52% decrease in traffic in the past quarter (32 emails compared to 66) - issues@struts.apache.org had a 35% decrease in traffic in the past quarter (219 emails compared to 332) - user@struts.apache.org had a 27% increase in traffic in the past quarter (47 emails compared to 37) [1] https://cwiki.apache.org/confluence/display/WW/Version+Notes+7.1.1 [2] https://cwiki.apache.org/confluence/display/WW/Version+Notes+6.8.0 [3] https://cwiki.apache.org/confluence/display/WW/S2-068 [4] https://cwiki.apache.org/confluence/display/WW/S2-069 ----------------------------------------- Attachment BW: Report from the Apache Tapestry Project [Thiago H. de Paula Figueiredo] ## Description: The mission of Tapestry 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 Tapestry was founded 2006-02-14 (20 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 Ben Weidig on 2021-12-02. - No new committers. Last addition was Christian Köberl on 2024-05-02. ## Project Activity: We're finishing up a new major release, 5.10.0, with support for ES (i.e. JavaScript) modules. In addition, we're progressing on the process of getting a new site, using the Antora site generator, instead of relying on Confluence exports. This is a prerequisite for using more GitHub features, planned to make easier participation from the community. We're also establishing a monthly Jour Fixe (a video meeting) for better, synchronous coordination. ## Community Health: No releases, so no public user mailing list traffic. We had some discussions on the #tapestry Slack channel. ----------------------------------------- Attachment BX: Report from the Apache Tcl Project [Georgios Petasis] ----------------------------------------- Attachment BY: Report from the Apache Tez Project [László Bodor] ## Description: Apache Tez is an effort to develop a generic application framework which can be used to process arbitrarily complex DAGs of data-processing tasks and also a re-usable set of data-processing primitives which can be used by other projects. ## Project Status: Current project status: Ongoing. Issues for the board: None. ## Membership Data: Apache Tez was founded 2014-07-16 (11 years ago) There are currently 36 committers and 33 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 Ayush Saxena on 2024-09-17. - No new committers. Last addition was Ayush Saxena on 2024-01-09. ## Project Activity: Few tickets are being addressed for 1.0.0, still no clear scope until pressure from upstream projects. ## Community Health: Same, quite a few PMC members, and no new committer candidate, but we have people from related projects actively commenting on PRs. ----------------------------------------- Attachment BZ: Report from the Apache Thrift Project [Jens Geyer] ## Description: Apache Thrift is a high performance cross platform RPC and serialization solution. ## Project Status: Current project status: Ongoing medium Issues for the board: none ## Membership Data: Apache Thrift was founded 2010-10-20 (15 years ago) There are currently 42 committers and 22 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 Liu Jiayu on 2025-03-16. - Hasnain Lakhani was added as committer on 2025-07-29 ## Project Activity: Working towards next regular release. Last release was 0.22.0 at May 14th, 2025. ## Community Health: Participation varies highly across the 20+ target languages supported by Thrift, but it also fluctuates over time. For example, during Nov/Dec 2025 we had a signifinact increase in the number of pull requests coming in particularly for Ruby, fixing issues as well as adding improvements. ----------------------------------------- Attachment CA: Report from the Apache Tika Project [Tim Allison] ## Description: Apache Tika is a dynamic toolkit for content detection, analysis, and extraction. It allows a user to understand, and leverage information from, a growing a list of over 1200 different file types including most of the major types in existence (MS Office, PDF, Text, Images, Video, Code, and science data) as recognized by IANA and other standards bodies. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Tika was founded 2010-04-20 (16 years ago) There are currently 31 committers and 31 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05. - No new committers. Last addition was Nicholas DiPiazza on 2021-06-03. ## Project Activity: We're on the cusp of a 3.3.0 release. We've made quite a bit of progress on a major refactor for the first 4.x release -- more modularity, easier configuration. ## Community Health: More email traffic, probably driven by 4.x development conversations and CVE remediation discussions. Chi still in decent shape: 4.70 (Healthy). ----------------------------------------- Attachment CB: Report from the Apache TinkerPop Project [Kelvin Lawrence] ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). ## Project Status: The project is ongoing with high activities this past quarter. There are no issues requiring board attention. ## Membership Data: Apache TinkerPop was founded 2016-05-17 (10 years ago) There are currently 31 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Cole Greer on 2025-06-02. - No new committers. Last addition was Andrea Child on 2025-08-11. ## Project Activity: The project delivered a significant milestone this quarter with the release of TinkerPop 3.8.0 on November 12, 2025 [1]. This transitional release introduces substantial improvements to Gremlin language consistency and usability, including standardized scoping behavior, simplified grammar syntax, and enhanced interoperability between related steps. Key features include new type conversion steps and filtering capabilities for mixed-type properties, and initial support for Model Context Protocol (MCP) with the gremlin-mcp server. Along with 3.8.0, we published a maintenance release of TinkerPop 3.7.5 with critical bug fixes and non-breaking improvements [2]. Following the successful 3.7.5 and 3.8.0 release, development focus has returned to TinkerPop 4.0. The community continues active development on both maintenance updates for the 3.7.x/3.8.x line and major architectural improvements for the 4.0 release. ### Releases: 3.7.5 was released on 2025-11-12. 3.8.0 was released on 2025-11-12. ## Community Health: The TinkerPop community maintains strong engagement with consistent contributions from core committers and active participation from users on the dev list and in our Discord server. We have observed increased dev list activity, particularly driven by YouTrackDB discussions. Given this growth and the limitations of Discord voice channels, the community decided to introduce regular Microsoft Teams meetings [3], open to anyone who wishes to join, to enhance collaboration and provide real-time discussion opportunities. Meeting notes are recorded on the dev list, with the first meeting held on December 9 [4]. This quarter featured three live events on Twitch [5]: TinkerPop Wide sessions exploring graph-enhanced AI memory and NetworkX cloud analytics with Amazon Neptune, and two-part Contributorcast sessions reviewing the 3.8.0 post-release. All recordings are available on our YouTube channel [6]: * TinkerPop Wide: Graph-Enhanced AI Memory and NetworkX Cloud Analytics with Amazon Neptune [7] Presenters: Andy Kwok, Andrew Carbonetto * Contributorcast: Apache TinkerPop 3.8.0 Post-release Review - Part I [8] Presenters: Stephen Mallette, Cole Greer, Ken Hu, Andrea Child, Yang Xia * Contributorcast: Apache TinkerPop 3.8.0 Post-release Review - Part II [9] Presenters: Cole Greer, Ken Hu, Andrea Child, Yang Xia ## Report Links [1]: https://lists.apache.org/thread/yzyox295yn0x5vt24vns2qb4kzrrdfjv [2]: https://lists.apache.org/thread/fz0px655fq9kjjrnqjnxdkwr62lyvkrh [3]: https://lists.apache.org/thread/06jq7cs987g3slv6jst4nmvl1lgnfc8t [4]: https://lists.apache.org/thread/xonq8jdlchrpff11x17ov9j5w4f2r8jf [5]: https://www.twitch.tv/apachetinkerpop [6]: https://www.youtube.com/@apachetinkerpop [7]: https://www.youtube.com/watch?v=alpGRXRa-p8 [8]: https://www.youtube.com/watch?v=o124-WSL_rk [9]: https://www.youtube.com/watch?v=yfP2kAULZJA ----------------------------------------- Attachment CC: Report from the Apache Traffic Server Project [Bryan Call] ## Description: The mission of Traffic Server is the creation and maintenance of a high-performance, scalable HTTP/1.1 and HTTP/2 caching proxy server that powers major CDNs worldwide. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Traffic Server was founded 2010-04-20 (16 years ago). There are currently 71 committers and 58 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 Mo Chen on 2024-04-15. - No new committers. Last addition was Jasmine Emanouel on 2025-09-26. ## Project Activity: Notable work this quarter includes adding Zstandard (zstd) compression support, completing the migration from PCRE to PCRE2, adding USDT probes for cache directory operations, adding a per-client connection exempt list feature, adding certificate info retrieval in the Lua plugin, and multiple cache stability and HTTP compliance fixes. Development remains healthy with 25 active contributors merging 183 pull requests. The project closed nearly twice as many issues as were opened, continuing to reduce our backlog. We are currently working toward ATS 10.1.1 and 9.2.12 bug fix releases. The next feature release, 10.2.0, is planned for late Q1, and ATS 11.0.0 is targeted for late summer. ## Community Health: We held a Fall Summit remotely on October 15-16, 2025. Travel budgets continue to be tight for some companies. We continue to hold weekly bug and issue scrubs every Monday, ensuring timely review of pull requests and resolution of user-reported issues. The project continues to close more issues than are opened, indicating good maintenance of the codebase. There is active participation in code reviews and discussions on the dev mailing list. ----------------------------------------- Attachment CD: Report from the Apache Training Project [Justin Mclean] ## Description: The mission of Apache Training is the creation and maintenance of software related to training materials for Apache projects and the Apache Software Foundation ## Project Status: Current project status: New Issues for the board: None ## Membership Data: Apache Training was founded 2025-08-20 (5 months ago) There are currently 18 committers and 5 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 Andrew Wetmore on 2025-08-20. - No new committers were added. ## Project Activity: November saw a small amount of activity with updates to training materials, including additions related to vendor neutrality and governance topics. December was a very quiet month with little visible activity in either the repository or mailing list. This reflects the typical activity pattern for Apache Training where the project has a small contributor base and work tends to occur in bursts driven by external needs, particularly around conferences and related ASF training efforts, rather than as steady month-to-month development. ## Community Health: The community is small and stable. Most work continues to come from a small number of existing contributors. Mailing list traffic was minimal in December following limited activity in November, and there were no new contributors during this period. ----------------------------------------- Attachment CE: Report from the Apache Velocity Project [Nathan Bubna] ## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Ongoing, verging upon dormant Issues for the board: none ## Membership Data: Apache Velocity was founded 2006-10-24 (19 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - 1 new committer incoming. Last addition was Thomas Mortagne on 2020-03-09. Incoming is Claude Warren. Vote passed, but we're admittedly slow in acting on it. Intention is for him to join the PMC soon too, as he is well-experienced in ASF work. ## Project Activity: Velocity Master POM 8 - 2025-11-15 APT and MD support added to Velocity Tools Whitespace handling work in Velocity Engine ## Community Health: "Hyper stable" as always. We handled the roll call vote in November just fine. We may not be fast movers as projects go, but neither do we need to be. Things are working fine and the project has reliable oversight, even if we are a bit sloth-like. ----------------------------------------- Attachment CF: Report from the Apache Wayang Project [Zoi Kaoudi] ## Description: The mission of Apache Wayang is the creation and maintenance of software related to cross-engine data processing that aims at (i) decoupling applications from underlying data processing engines, such as Apache Flink, Apache Spark, databases, or ML systems, and (ii) automatically determining the optimal combination of engines to execute a given data pipeline using an optimizer ## Project Status: Current project status: New TLP, graduated a few weeks ago. Issues for the board: Nothing major. We just noticed that our project is not listed under the unregistered trademarks: https://www.apache.org/foundation/marks/list/#unreg_w ## Membership Data: Apache Wayang was founded 2025-11-19 There are currently 18 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: The last quarter we mainly focused on addressing some issues that came from the IPMC and fixed bugs in the Python API, while improving our website before graduation. We are currently working on fixing some issues with the FileObjectSources and updating the Flink platform to the latest DataStream API. One major thing we have planned is a significant improvement of our documentation. We are planning a new release for the end of January. ## Community Health: Community activity has remained steady over the last quarter. Traffic on the dev list has increased and discussions have been constructive, with an emphasis on preparing for graduation and coordinating the remaining IPMC-related tasks. Participation has been consistent, and we continue to respond promptly to PRs and technical questions. We are also seeking more contributors not only for code, but also for documentation, blogs, and other areas. We have seen increased interest since we became a TLP. ----------------------------------------- Attachment CG: Report from the Apache Web Services Project [Daniel Kulp] ----------------------------------------- Attachment CH: Report from the Apache XML Graphics Project [Clay Leeds] ----------------------------------------- Attachment CI: Report from the Apache Zeppelin Project [Jongyoul Lee] ## Description: The mission of Zeppelin is the creation and maintenance of software related to A web-based notebook that enables interactive data analytics ## Project Status: Current project status: Onging with moderate activity Issues for the board: Made security issues private in cwiki ## Membership Data: Apache Zeppelin was founded 2016-05-18 (10 years ago) There are currently 27 committers and 13 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 Cheng Pan on 2024-08-25. - No new committers. Last addition was ChanHo Lee on 2025-08-20. ## Project Activity: OSSCA finished successfully. Through the program, over 100 issues were raised, and 69 issues were merged. Moreover, we now have 10 new contributors. The community is actively contributing new UI, including e2e tests. After making the new UI stable, we plan to release a new version with UI changes. ## Community Health: Comparing with the period of OSSCA, the community activity has decreased, but overall looks good. The new topic is AI-related, and we will try to include an AI feature on the project. ------------------------------------------------------ End of minutes for the January 21, 2026 board meeting.