The Apache Software Foundation Board of Directors Meeting Minutes September 24, 2025 1. Call to order The meeting was scheduled for 21:00 UTC and began at 21:04 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2025-09-24T21: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 Greg Stein Rich Bowen Shane Curcuru Justin Mclean Sander Striker Jean-Baptiste Onofré - joined at :08 Kanchana Pradeepika Welagedara Zili Chen Directors Absent: none Executive Officers Present: Craig McClanahan Craig L Russell Jeff Jirsa Executive Officers Absent: Matt Sicker Guests: Daniel Gruno Sally Khudairi Dave Fisher Thomas Neidhart Alin Jerpelea Paul King Giovanni Bechis Danny Angus Andrew Wetmore Brian Proffitt Jarek Potiuk Melissa Logan Whitney P True 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of August 20, 2025 See: board_minutes_2025_08_20.txt Approved by General Consent. B. The meeting of August 25, 2025 See: board_minutes_2025_08_25.txt Approved by General Consent. C. Action Without a Meeting See board_minutes_2025_08_24.png Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander Striker] Since last month’s meeting we had an Action Without a Meeting and an Executive Session. These are in the minutes section separately for approval. The Logo Dev PMC recommended a new logo for the foundation, and to accommodate ordering materials for the Community over Code event, we wanted to cover approval of the action in an expedited fashion. I had to rediscover how to perform an Action Without a Meeting. This has triggered my interest in making this easier and maybe routine so that the next time we need this it’s normal. The Community over Code event was a great time to connect with various people face to face. I received very positive reactions to the event. The Board Agenda Tool is now being used for most actions. I've discovered one gap that may impact a number of projects this month, the ability to see reports that were posted via email only and not via the tool. I've posted them using the old tool, and they may as such appear later than actually submitted. B. President [Ruth Suehle] Of course the biggest news this month is that we've just wrapped up Community Over Code, and by all indications, it was a resounding success. Attendance grew over last year, but more importantly, there was an increasing stream of people independently coming to me and Brian to gush about what a wonderful experience they had had. On day 1, I took a quick hand-raise poll before State of the Foundation, asking how many people were there for the first time. I'd estimate it was at least half the room. And over and over again, they came to us to say that this conference had been more welcoming than any other they'd ever been to. One commented, "You actually read my name tag and cared who I was." Several described being welcomed like an old friend by various projects and tracks, despite never having met any of the people there before. Community Over Code truly put the community before the code, and I'm incredibly proud of every single attendee for that. The new logo launch went likewise quite well, and I've been more than pleased at its reception by the general public. Kudos again to everyone who has helped get us here. I spent the next week in Brussels, first for Open Source Congress (meeting with our peer foundation leaders Tuesday, followed by industry stakeholders Wednesday), then representing us and the other other affiliate members at OSI board meetings Thursday and Friday. Additionally, please see Attachments 1 through 11. C. Treasurer [Craig McClanahan] Normal operations continue, with a few extra items focused on supporting Community Over Code (which was still upcoming in August). Additionally, we (Lewis and I) are spending time focused on refining user-level documentation of roles and tasks related to Treasury on the Confluence Wiki. D. Secretary [Matt Sicker] In August, 24 ICLAs, two CCLAs, and one Software Grant were received. E. Executive Vice President [Jeff Jirsa] The Executive Vice President thanks the board for their thoughtful consideration of the topic raised during the Executive Session in August. 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 / Greg] No report was submitted. C. Apache Security Team Project [Mark J. Cox / Justin] See Attachment 14 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Airflow [rbowen] # Brand Management [rbowen] # CarbonData [jmclean, jim, kanchana] # EventMesh [kanchana] # IoTDB [kanchana] # Portals [jmclean] # ServiceMix [kanchana] # Shiro [rbowen] # Xerces [rbowen] # ZooKeeper [jim, kanchana] A. Apache Airflow Project [Bolke de Bruin / Zili] See Attachment A @Rich: follow up on Matomo question B. Apache Allura Project [Dave Brondsema / Shane] See Attachment B C. Apache Atlas Project [Madhanmohan Neethiraj / JB] See Attachment C D. Apache Axis Project [Robert Lazarski / Sander] See Attachment D E. Apache Beam Project [Kenneth Knowles / Jim] See Attachment E F. Apache Bigtop Project [Masatake Iwasaki / Kanchana] See Attachment F G. Apache BookKeeper Project [Enrico Olivelli / Zili] See Attachment G H. Apache BuildStream Project [Tristan Van Berkom / Jim] See Attachment H I. Apache BVal Project [Matt Benson / Greg] No report was submitted. J. Apache Camel Project [Andrea Cosentino / Rich] See Attachment J K. Apache CarbonData Project [Jacky Li / JB] See Attachment K @JB: discuss attic L. Apache Cayenne Project [Michael Gentry / Sander] See Attachment L M. Apache CloudStack Project [Nicolás Vázquez / Kanchana] See Attachment M N. Apache Commons Project [Gary D. Gregory / Shane] See Attachment N O. Apache Cordova Project [Bryan Ellis / Justin] See Attachment O P. Apache cTAKES Project [Pei J Chen / Rich] See Attachment P Q. Apache Curator Project [Enrico Olivelli / JB] See Attachment Q R. Apache Daffodil Project [Mike Beckerle / Sander] See Attachment R S. Apache DataFusion Project [Andrew Lamb / Greg] See Attachment S T. Apache Doris Project [Mingyu Chen / Jim] No report was submitted. U. Apache ECharts Project [Wenli Zhang / Zili] See Attachment U V. Apache EventMesh Project [Eason Chen / Shane] See Attachment V W. Apache Felix Project [Karl Pauls / Kanchana] See Attachment W X. Apache Flex Project [Harbs / Justin] See Attachment X Y. Apache Flink Project [Robert Metzger / Shane] See Attachment Y Z. Apache Fory Project [Chaokun Yang / Sander] See Attachment Z AA. Apache Geode Project [Mark Bretl / Greg] See Attachment AA AB. Apache Geronimo Project [Jean-Louis Monteiro / Kanchana] No report was submitted. AC. Apache Gobblin Project [Abhishek Tiwari / JB] See Attachment AC AD. Apache Gravitino Project [Jerry Shao / Zili] See Attachment AD AE. Apache Griffin Project [William Guo / Sander] No report was submitted. AF. Apache Guacamole Project [Mike Jumper / Justin] See Attachment AF AG. Apache Gump Project [Stefan Bodewig / Jim] See Attachment AG AH. Apache Helix Project [Junkai Xue / Rich] See Attachment AH AI. Apache HertzBeat Project [Chao Gong / Greg] See Attachment AI AJ. Apache Hive Project [Naveen Gangam / Rich] No report was submitted. AK. Apache Hop Project [Hans Van Akelyen / Sander] No report was submitted. AL. Apache HttpComponents Project [Michael Osipov / JB] See Attachment AL AM. Apache Hudi Project [Vinoth Chandar / Justin] See Attachment AM AN. Apache Iceberg Project [Ryan Blue / Shane] No report was submitted. AO. Apache Incubator Project [Justin Mclean / Justin] See Attachment AO AP. Apache IoTDB Project [Xiangdong Huang / Kanchana] See Attachment AP AQ. Apache Jackrabbit Project [Marcel Reutegger / Jim] See Attachment AQ AR. Apache Johnzon Project [Jean-Louis Monteiro / Zili] No report was submitted. AS. Apache Juneau Project [James Bognar / Kanchana] See Attachment AS AT. Apache Karaf Project [Jean-Baptiste Onofré / JB] See Attachment AT AU. Apache Knox Project [Larry McCay / Zili] See Attachment AU AV. Apache Kvrocks Project [Mingyang Liu / Shane] No report was submitted. AW. Apache Kyuubi Project [Kent Yao / JB] See Attachment AW AX. Apache Libcloud Project [Tomaž Muraus / Greg] No report was submitted. AY. Apache Linkis Project [Shuai Di / Rich] See Attachment AY AZ. Apache Lucene Project [Dawid Weiss / Sander] See Attachment AZ BA. Apache Lucene.Net Project [Shad Storhaug / Jim] See Attachment BA BB. Apache Mynewt Project [Szymon Janc / Justin] See Attachment BB BC. Apache NetBeans Project [Geertjan Wielenga / Zili] See Attachment BC BD. Apache OFBiz Project [Jacopo Cappellato / Rich] See Attachment BD BE. Apache Olingo Project [Michael Bolz / Shane] No report was submitted. BF. Apache OpenDAL Project [Hao Ding / Kanchana] See Attachment BF BG. Apache OpenNLP Project [Jeffrey T. Zemerick / Justin] See Attachment BG BH. Apache OpenWebBeans Project [Mark Struberg / JB] See Attachment BH BI. Apache Ozone Project [Sammi Chen / Jim] See Attachment BI BJ. Apache Paimon Project [Jingsong Lee / Sander] See Attachment BJ BK. Apache Pekko Project [PJ Fanning / Greg] See Attachment BK BL. Apache Pig Project [Koji Noguchi / Justin] See Attachment BL BM. Apache Pinot Project [Kishore G / Greg] No report was submitted. BN. Apache PLC4X Project [César García / Jim] See Attachment BN BO. Apache Portable Runtime (APR) Project [Yann Ylavic / Zili] No report was submitted. BP. Apache Portals Project [Neil Griffin / Greg] See Attachment BP BQ. Apache Pulsar Project [Matteo Merli / Shane] See Attachment BQ BR. Apache RocketMQ Project [Xiaorui Wang / JB] No report was submitted. BS. Apache Royale Project [Yishay Weiss / Rich] No report was submitted. BT. Apache SeaTunnel Project [Jun Gao / Sander] No report was submitted. BU. Apache ServiceMix Project [Krzysztof Sobkowiak / Kanchana] See Attachment BU BV. Apache Shiro Project [Lenny Primak / Zili] See Attachment BV BW. Apache SINGA Project [Wang Wei / Greg] See Attachment BW BX. Apache Sling Project [Robert Munteanu / Jim] See Attachment BX BY. Apache SpamAssassin Project [Giovanni Bechis / Justin] See Attachment BY BZ. Apache Storm Project [Richard Zowalla / Kanchana] See Attachment BZ CA. Apache StreamPark Project [Huajie Wang / Shane] See Attachment CA CB. Apache Synapse Project [Isuru Udana / Rich] No report was submitted. CC. Apache Teaclave Project [Zhaofeng Chen / JB] See Attachment CC CD. Apache Tomcat Project [Christopher Schultz / Sander] See Attachment CD CE. Apache TomEE Project [David Blevins / Shane] See Attachment CE CF. Apache Traffic Server Project [Bryan Call / Rich] See Attachment CF CG. Apache Training Project [Justin Mclean / Justin] See Attachment CG CH. Apache TsFile Project [Jialin Qiao / Jim] See Attachment CH CI. Apache TVM Project [Tianqi Chen / Sander] See Attachment CI CJ. Apache UIMA Project [Richard Eckart de Castilho / Justin] See Attachment CJ CK. Apache Unomi Project [Serge Huber / JB] See Attachment CK CL. Apache VCL Project [Josh Thompson / Zili] See Attachment CL CM. Apache Web Services Project [Daniel Kulp / Greg] See Attachment CM CN. Apache Wicket Project [Andrea Del Bene / Kanchana] See Attachment CN CO. Apache Xerces Project [Michael Glavassevich / Zili] See Attachment CO CP. Apache Yetus Project [Allen Wittenauer / Sander] See Attachment CP CQ. Apache ZooKeeper Project [Flavio Junqueira / Kanchana] See Attachment CQ Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Cassandra Project Chair WHEREAS, the Board of Directors heretofore appointed Dinesh Joshi (djoshi) to the office of Vice President, Apache Cassandra, and WHEREAS, the Board of Directors is in receipt of the resignation of Dinesh Joshi from the office of Vice President, Apache Cassandra, and WHEREAS, the Project Management Committee of the Apache Cassandra project has chosen by vote to recommend Ekaterina Dimitrova (edimitrova) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Dinesh Joshi is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Cassandra, and BE IT FURTHER RESOLVED, that Ekaterina Dimitrova be and hereby is appointed to the office of Vice President, Apache Cassandra, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Cassandra Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Kyuubi Project Chair WHEREAS, the Board of Directors heretofore appointed Kent Yao (yao) to the office of Vice President, Apache Kyuubi, and WHEREAS, the Board of Directors is in receipt of the resignation of Kent Yao from the office of Vice President, Apache Kyuubi, and WHEREAS, the Project Management Committee of the Apache Kyuubi project has chosen by vote to recommend Cheng Pan (chengpan) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Kent Yao is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Kyuubi, and BE IT FURTHER RESOLVED, that Cheng Pan be and hereby is appointed to the office of Vice President, Apache Kyuubi, 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 Kyuubi Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache Grails 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 the development of a powerful Groovy-based web application framework for the JVM built on top of Spring Boot. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Grails Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Grails be and hereby is responsible for the creation and maintenance of software related to a powerful Groovy-based web application framework for the JVM built on top of Spring Boot.; and be it further RESOLVED, that the office of "Vice President, Apache Grails" 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 Grails Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Grails 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 Grails Project: * Brian Koehmstedt * David Estes * Graeme Rocher * James Daugherty * James Fredley * Lari Hotari * Mattias Reichel * Paul King * Puneet Behl * Sergio del Amo * Soeren Glasius * Walter Duque de Estrada NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Fredley be appointed to the office of Vice President, Apache Grails, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Grails Project be and hereby is tasked with the migration and rationalization of the Apache Grails podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Grails podling encumbered upon the Apache Groovy Project are hereafter discharged. Special Order 7C, Establish the Apache Grails Project, was approved by Unanimous Vote of the directors present. D. Terminate the Apache Portals Project WHEREAS, the Project Management Committee of the Apache Portals project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Portals project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Portals project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Portals Project; and be it further RESOLVED, that the office of "Vice President, Apache Portals" is hereby terminated; and be it further RESOLVED, that the Apache Portals PMC is hereby terminated. Special Order 7D, Terminate the Apache Portals Project, was approved by Unanimous Vote of the directors present. E. Establish the Apache DevLake 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 development data platform, providing the data infrastructure for developer teams to analyze and improve their engineering productivity. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache DevLake Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache DevLake be and hereby is responsible for the creation and maintenance of software related to a development data platform, providing the data infrastructure for developer teams to analyze and improve their engineering productivity; and be it further RESOLVED, that the office of "Vice President, Apache DevLake" 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 DevLake Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache DevLake 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 DevLake Project: * Ji Bin * Warren Chen * Felix Cheung * Julien Chinapen * Lidong Dai * Sijie Guo * Lynwee Hou * Willem Ning Jiang * Jonathan O'Donnell * Jean-Baptiste Onofré * Cong Wang * Maxim Wheatley * Klesh Wong * Hezheng Yin * Kaiyun Zhang * Liang Zhang * Liang Zhang * Zikuan NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hezheng Yin be appointed to the office of Vice President, Apache DevLake, 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 DevLake Project be and hereby is tasked with the migration and rationalization of the Apache Incubator DevLake podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator DevLake podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7E, Establish the Apache DevLake Project, was approved by Unanimous Vote of the directors present. F. Terminate the Apache Griffin Project WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Griffin project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Griffin project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Griffin Project; and be it further RESOLVED, that the office of "Vice President, Apache Griffin" is hereby terminated; and be it further RESOLVED, that the Apache Griffin PMC is hereby terminated. Special Order 7F, Terminate the Apache Griffin Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Code of Conduct Discuss preparation steps enabling a decision. Jim: Fine with policy as written in wiki as a starting point Justin: What is missing? Greg: A committee with teeth is needed before approval Rich: More review is needed by everyone possibly affected. Good starting point. Jim: Suggest discussing whether an enforcement committee is needed. Justin: We should not block progress pending all details being clarified. Sander: We want an enforceable CoC. Need a volunteer to drive the process. Jeff? Shane: For making progress sooner. Greg: We have never made a call for volunteers to staff the enforcement committee. Shane: Propose putting an agenda item on next month's board calendar. Jim: Enacting board-level CoC is a whole other level. Need serious discussion on this aspect. Sander: Ask Jeff Jirsa to drive the process forward. All directors voted in favor of asking Jeff Jirsa to drive the process forward. B. Reporting Reporting expectations and future direction of reporting. Rich: A year ago we started a project to facilitate reporting. Instead of detailed questions, ask: - sufficient PMC oversight? - any threats or risks to the project? - any requests from the Foundation? Shane: Can we have one page on the wiki summarizing what the direction is? Rich: The page exists. Sander: We need to point folks to the page. Jim: Rarely the PMC chair reports limited information, making oversight difficult. Rich: We need to make sure oversight is not just rubber stamping. Jim: The director shepherd role needs to be emphasized. Sander: Some of the information in board reports belongs to M&P. Kanchana: Are there any CRA compliance issues? Justin: Some experimental information is being generated for podlings. Sander: Do we have consensus that the path that Rich and Sander are following are good? Yes C. 5 Year Strategic Plan for the Apache Software Foundation Discussion regarding whether we wish to refresh the existing 5 year plan. An alternative is to set some objectives that actions can be weighed against, e.g. "The Developer Experience working on an ASF project is similar or better than industry standard". Sander: The 5 year plan does not seem to be successful. Do we need a strategic goals document? Greg: Agree. A more useful thing might be to take Action Item Plan and carry forward a list of high level actions. We should discuss progress each board meeting. Jim: Coming up with a list of goal posts might fit in with a 5 year plan. Justin: Look at the member survey where this was discussed. Feedback: focus on shorter term items. Kanchana: Discussing at Community over Code, I can follow up on some of the threads. Sander: Useful to have short term goals, but also good to have more strategic plans. Greg: Emphasize building the list to pass on to next board. Sander: We should have a process in place. Ok to delete the current 5 year plan? Yes, consensus to delete or "retire" the 5 year plan 9. Review Outstanding Action Items * Greg: broad reminder for PMC terminology [ Pinot 2025-05-21 ] Status: Bertrand's comdev site change was merged in May. I'll draft a message on Slack for a little bit of review, and then send to pmcs@apache.org https://community.apache.org/contributor-ladder.html#terminology-pmc-and-pmc-member Rich is going to send a bundle of content to pmcs@, and this will be part of that. * Matt: ensure Fluo is removed from schedule for reporting [ Fluo 2025-07-16 ] Status: @Matt: Fluo is still showing up as a project even thought it has been merged into another project * Greg: clarify community overlap with Mifos and state of community [ Fineract 2025-07-16 ] Status: * Sander: pursue Attic resolution for Griffin [ Griffin 2025-07-16 ] Status: See https://agenda.apache.org/meetings/2025-09-24#pursue-attic-resolution-for-griffin * Rich: follow up about Attic [ Kibble 2025-07-16 ] Status: Done. The consensus appears to be that it's time for the attic. I will work with the PMC to provide a resolution next month. There is now a DISCUSS thread, and I expect to start a VOTE later this week or early next week. * JB: pursue potential Attic for CarbonData [ CarbonData 2025-08-20 ] Status: * Zili: speak with PMC about moving to the Attic [ TrafficControl 2025-08-20 ] Status: Informed https://lists.apache.org/thread/47tbh81jt1z3nnv8f7xbdz4stlzx0t1m The PMC is discussing about moving to attic https://lists.apache.org/thread/9j1b3x6qrg36pfjnh7wnrjyc3dcyd30n I'll keep watching on the process and update accordingly. * JB: pursue a roll call for PMC [ Velocity 2025-08-20 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:30 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period August 2025 * ISSUES FOR THE BOARD The DORIS PMC is not responding to issues raised by trademarks in a timely manner. * OPERATIONS Responded to the following queries, liaising with projects as required: - Approved SEATA, AURON and HUGEGRAPH as project names. - Provided advice to the TRAINING PMC regarding the use of ASF and other ASF project logos. - Provided advice to HUGEGRAPH on the process for transferring existing trademarks to the ASF on graduation - Responded to a query regarding the trademarks associated with the former WEEX podling. - Approved one event for DORIS * REGISTRATIONS Worked with counsel to maintain our DRUID registration in the US. Responded to counsel questions regarding our GROOVY registration application. Worked with counsel and Baidu towards transferring BifroMQ to the ASF. * INFRINGEMENTS It was noticed an appropriate trademark attribution was missing from a third-party event. It was quickly fixed when requested. The Grails podling has, with a little support, has identified and resolved a potentially infringing new OSS project. Submitted a formal trademark infringement complaint to GitHub regarding an NPM package on behalf of the logging PMC. Resolved the remaining issues with a recent blog referencing CASSANDRA. Resolved issues with a support provider making misleading claims regarding the level of involvement of ASF communities in the support they are providing. No further progress regarding a potential infringement of PDFBOX. The most serious issues have already been addressed. Slow progress regarding the downstream vendor with multiple infringements of ASF marks. A company claiming the ASF as a customer and using the ASF logo has removed the logo at our request. There has been some progress but some issues still remain for IOTDB. The BOOKKEEPER PMC has addressed an issue with a vendor's product name. The KAFKA PMC is working to address a potential infringement of KAFKA. Continued working with the XMLGRAPHICS PMC to resolve a potential infringement of FOP. The KAFKA PMC is working to address a potential infringement of KAFKA. No further progress for the GROOVY PMC addressing a potential infringement in a GitHub project. Will need the GROOVY registration to progress this further. No progress regarding a site with a possible infringement of APISIX. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: no new Sponsors have been onboarded during this time period. b —Renewals: we have secured renewal commitments from one Platinum Sponsor, and two Silver Sponsors (downgraded from Gold). c —Payments: 1 —New: no new Sponsorship payments have been received. 2a —Renewing: we received a partial payment from a renewing Sponsor who has upgraded to a new level during its current Sponsorship term. 2b —Incoming: we await payment from two Platinum, one Gold, three Silver, and one Bronze Sponsor. 2) Targeted Sponsors: we secured renewal commitment from one Platinum Targeted Sponsor, and continue to explore possible options for recognizing organizations supporting ASF Projects (independently from our existing Targeted Sponsor offerings). 3) Sponsor Relations: ongoing outreach and engagement continues. The Q3 call with Gold and Platinum Sponsors is scheduled to take place mid-September and will feature ASF Infrastructure as the primary discussion topic. We are working on the third Fundraising blog post as part of our promotional activities through the end of the year. 4) Event Sponsorship: Community Over Code North America is taking place 11-14 September; we received ~$53,000 event in sponsorship payments during this timeframe. 5) Individual Donations and Corporate Giving: we received $1,200 in individual online donations via https://donate.apache.org/ . 6) Administrivia: we continue to work closely with the ASF Treasury, Accounting, Events, and Marketing & Publicity teams. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] New Logo Launch At the time of this report's submission, we are one day away from launching the new logo (details of the massive scope of this in the Brand Project section below). There are too many people to thank for their efforts in getting this over the finish line, both in terms of conception and implementation. This has been a complicated journey, and the efforts of the Brand Steering Committee, the Logo-Dev PMC, and the M&P team who have worked hard to get this done cannot be praised enough. This Foundation is a vital part of the global open source ecosystem, and moving forward into the next quarter-century with a new brand is a great step in keeping the recognition of the values and strengths of our Foundation strong. Foundation Comms * Issued press release announcing the availability of the FY25 annual report * Compiled and distributed August edition of Plus One newsletter * Subscriber list now totals 143 * Wrote and issued press release touting Community Over Code NA schedule and keynote highlights, as well as social media content * Continued coordination for fundraising awareness campaign with Fundraising team; promoted second blog showcasing individual donors. * Created graphics to support blog and social promotions. Project Comms * Developed and issued press release touting a major release for Apache Ozone (release 2.0). * Began coordination for case study with Apache Ozone / DiDi Global Brand Project * Reviewed final report from semiotics and Indigenous consultants to inform final logo design choices (color, font size/style, etc) * Coordinated with ASF Trademark to ensure logo compliance and inform web design * Coordinated with ASF Trademark to run trademark search (which found no issues) * Engaged with logo designer to finalize the wordmark * Resumed Apache.org web redesign with logo selection complete * Performed website logo audit * Updated project action items and timeline including: * Logo styling * Brand narrative * Website redesign * Brand assets including favicons, fundraising logos, PPT deck, social headers & more * ASF Project Guidance, including Project logo request form * Drafted and will post Brand launch blog * New logo campaign for social channels * Wiki updates drafted Digital * Continuous optimization of Google Ads campaign for C/C NA Social Media Overview The highest performing pieces of content for August include project major release news (Ozone 2.0) and the Community Over Code schedule and keynote announcement. Social Highlights (X + LinkedIn + Bluesky) Total Audience: 144,842 New Followers in July: 700 X: 109 Bluesky: 43 LinkedIn: 548 Total Posts: 77 X: 33 Bluesky: 33 LinkedIn: 14 Total Engagements: 2,843 Website Analytics 765,377 visits, 765,309 unique visitors +2.8% 3 min 19s average visit duration +9.3% 60% visits have bounced (left the website after one page) +1.7% 6 actions (page views, downloads, outlinks, internal site searches) per visit-3.2% 4,055,898 pageviews, 939,986 unique pageviews -3.7% 3 total searches on your website, 2 unique keywords +200% 160,921 downloads, 112,228 unique downloads -2.4% 373,087 outlinks, 179,207 unique outlinks +47.4% ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Danny Angus] General ======= Infra has hired a full-time contractor to start on 22 September. Infra and Security have been working on mail delivery issues related to ezmlm and DMARC. We are in the process of forking and modifying the ezmlm source code to fix these problems long-term, and to situate us for further modernization efforts of our email delivery systems. Finances ======== Incurred expected C/C conference expenses in September. Infra is now effectively fully staffed from an FY26 budget perspective. MFA Efforts =========== Infra, Security, and Tooling continue to coordinate on next steps. Authentik has been chosen as the MFA platform, and deployed as a POC. Authentication flows and MFA reset flows need to be established for the POC. Tooling will be contributing to this effort. Initial POC deployment and integration with ATR testing is expected by mid-October. Major Projects ============== MFA and DMARC updates continue to be Infra's highest priority. Atlassian has announced the EOL of its Data Center (on-prem) licensing for Jira and Confluence in March 2029. Infra continues to evaluate the possibility of a migration to Atlassian Cloud. ----------------------------------------- Attachment 5: Report from the VP of Tooling [Dave Fisher] # Tooling The team continues to work hard building systems. ## Operations ## Apache Trusted Releases (ATR) We have begin to code SBOM checking process while building release candidates with a goal to handle various dependency checks like licenses and vulnerability checks. We will use some third party tools for some of this functionality. These checks will help the Release Manager learn if there are license changes or vulnerabilities in their dependencies. We will be announcing a second Alpha at C/C Minneapolis and are confirming our list of "Customer 0" PMCs. ## Board Agenda Tool (BAT) The Board Agenda Tool should be ready to perform almost every meeting step completely. The September meeting should not require use of the Whimsy tool. ## Workbench Nothing much to report. ## MFA It is a priority of the team to have MFA in place before releasing an ATR Beta. We will be actively assisting INFRA with MFA implementation. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Brian Proffitt] At the time of this report, the Community Over Code event is about to begin. We have 238 registered attendees, and expect the event to go very well. Signage and swag have all been updated with the new logo. Thanks go to the many speakers, track chairs, the TAC volunteers and committee, and co-organizers for all of their tremendous support for this event. A final rundown of the financials will be available in next month's board report. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald] Previous Events =============== Community Over Code NA ------------------------ We ended up with 12 people attending, after a couple more last minute visa denials. Overall, the TAC team for this year were excellent and really worked well together as a group. Comments from Organizers and other attendees were positive. The TAC dinner as usual was a big hit and really helped to start the event off knowing each other and also the invited guests. From 7am on the first day the TAC folks were there to help setup registrations and banners and t-shirts etc. The reg desk and community booth were occupied all week and Speakers were also attended to where needed. Community Over Code EU/Asia/NA 2024 and Asia 2025 still to finalize survey results. Current Events ============== None currently. Monthly Meetings ================ The next meeting is planned for the first week of October. 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 and Beijing still to be done. Mailing List Activity ===================== No activity this month other than a cwiki acct request. Membership ========== No changes to the Committee this month. ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno] Nothing of note to report this month. I attended Community over Code in Minneapolis, and we managed to get more people interested in joining the dev mailing list and help out. A more comprehensive report on progress is expected next month. ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik] Not much over the summer holiday - but processes starting in earnest again this week. - Very positive comments on new logo from policy makers. - Open Source Congress this week (but to close to the meeting for me to do a report; will do next month) - Several feedback requests from NIST and the EU that need attention - FYI - after this summers letter to Eclipse on OpenAtom and OpenHarmony on Huawei (https://selectcommitteeontheccp.house.gov/sites/evo-subsites/selectcommitteeontheccp.house.gov/files/evo-media-document/ Letter%20to%20the%20Eclipse%20Foundation-HarmonyOS%20%28June%202025%29.pdf); a similar letter went out to FutureWei (https://selectcommitteeontheccp.house.gov/media/letters/letter-to-futurewei-technologies-inc -requesting-information-on-huawei-s-us-proxy-role-and-ccp-technology-agenda) on OpenHarmony and Oniro with, this time, ISOC and the Linux Foundation in the firing line. - Personal disclosure: OSI is creating a European Entity in NL to allow it to work easier with European institution; as a not for profit, public benefit organisation with a, by regulation, non-remunerated board. I am volunteering as a board member as I do not see a conflict of interest with my ASF work at this time. I will update affiliations.txt once the minutes of the first board meeting, etc, are complete (and I hear no objections from the board). ----------------------------------------- Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz] Two TC54 task groups have prepared draft standards that will be submitted for discussion at the September TC54 meeting: * TG2: Package URL (https://github.com/package-url/purl-spec) * TG3: Common Lifecycle Enumeration (https://github.com/Ecma-TC54/tg3/blob/main/SPECIFICATION.md) If endorsed by TC54, these drafts will be forwarded to the ECMA Executive Committee and, if approved, ratified by the ECMA General Assembly in December. ----------------------------------------- Attachment 12: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] ----------------------------------------- Attachment 14: Report from the Apache Security Team Project [Mark J. Cox] August * Help Infra with the mailinglist DMARC issues, both to improve the deliverability of security-relevant emails and to clear the path for ongoing MFA work. * Coach Geode towards refining their security model and working towards a release * Start collecting feedback on the 2025 CISA SBOM Minimum Elements document Stats for August 2025: 45 [license confusion] 13 [report/question relating to dependencies] 14 [support request/question not security notification] Security reports: 91 (last months: 119, 77, 80) 23 ['commons'] 11 ['tomcat'] 5 ['cloudstack', 'httpd'] 2 ['airflow', 'arrow', 'fory', 'ofbiz', 'pulsar', 'ranger', 'solr', 'superset', 'tika', 'website or other infrastructure'] 1 ['allura', 'beam', 'brooklyn', 'brpc', 'cxf', 'datafusion', 'directory', 'fineract', 'hadoop', 'iotdb', 'kafka', 'karaf', 'kyuubi', 'livy', 'logging', 'mina', 'nifi', 'openmeetings', 'seata', 'seatunnel', 'synapse', 'syncope', 'tez', 'tinkerpop', 'trafficserver', 'xalan', 'zeppelin'] In total, as of 1st September 2025, we're tracking 249 (last months: 234, 194) open issues across 77 projects, median age 83 days (last months: 89, 115). 68 of those issues have CVE names assigned. 25 (last months: 27, 21) of these issues, across 12 projects, are older than 365 days. * geode (Health red): Five issues in Geode over 365 days old. The project had voted to move to the Attic, but new assistance was offered, and the issues are being worked through. (Last update: 2025-08-27) * openoffice (Health red): Several issues in OpenOffice are over 365 days old. They are not severe enough to warrant stopping distribution of OpenOffice, and there is progress on finding an architectural improvement to fix them, but we actively work to improve the projects' ability to respond to security issues going forward. (Last update: 2025-08-01) * fineract (Health amber): there are a number of open issues approaching a year old. The PMC has started to make progress and has made documentation and architectural changes, with more focus expected to close out these issues. (Last update: 2025-08-28) * spark (Health amber): the project is not responsive to security issues (Last update: 2025-08-01) ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: The mission of Apache Airflow is the creation and maintenance of software related to workflow automation and scheduling that can be used to author and manage data pipelines ## Project Status: Current project status: Ongoing, very high activity Issues for the board: Notice to the board! We have been discussing how to responsibly use Matomo to track on prem installations and features usage of Airflow (following fully GDPR and other privacy regulations). This has been extensively discussed in https://lists.apache.org/thread/fw4f51bmkyvkoo2b4wk2cpbbtssdj6ky . We discussed with the privacy team to help with making the privacy policy more ready for official board approval but in the meantime we are going to try out what we come up with and enable ASF Matomo installation/configuration tracking. We seem to come to the proposal that respects all concerns of the Privacy team and we would like to see if there is any objection from the board that we start doing it, without yet fully fleshed and approved privacy policy. ## Membership Data: Apache Airflow was founded 2018-12-19 (7 years ago) There are currently 73 committers and 36 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Amogh Desai was added to the PMC on 2025-06-26 - No new committers. Last addition was Rahul Vats on 2025-03-31. ## Project Activity: Apache Airflow is going through an intensive period of early days of Airflow 3 which was the biggest release ever for Airflow and one that we bet a lot on making Airflow a modern orchestrator suitable to handle productionizing new AI/ML workflows and being an even more flexible and prolific Data Engineering platform. We iterated on bugfixes and fixed teething problems with initial versions of Airflow 3 and we see significant adoption among the users, even if Airflow 3.0 did not yet have full feature parity with Airflow 2. We are working on closing the gap and Airflow 3.1 is the release that will deliver almost complete parity and a number of UI improvements and new features including Human-In-The-Loop functionality that we consider as very important for a number of AI/ML workflows. We also managed to employ AI effectively to boost collaboration in the community and achieved something that would be impossible without AI/ML support - Airflow UI in 3.1 is going to be translated into at least 15 (!) languages - multiple language families - with more than 700 phrases translated in all the languages. We build a strong and cooperating team of translators in our community that collaborate and support each other, and with all that we make Airflow much more accessible and welcoming for the international community. We worked out a sustainable process and tooling that will help us to maintain it and add more languages in the future. More about it in the ASF blog “AI and Open Source: Expanding Apache Airflow's Global Impact Through Collaboration” - https://share.google/b7Hi1JZ0pwPIKJYEO Recent releases: * Provider packages 2025-09-05 was released on 2025-09-09. * Apache Airflow 3.0.6 was released on 2025-08-29. * Task SDK 1.0.6 was released on 2025-08-29. * Apache Airflow 3.0.5 was released on 2025-08-20. * Task SDK 1.0.5 was released on 2025-08-20. * Provider packages 2025-08-12 was released on 2025-08-17. * Provider packages 2025-08-07 was released on 2025-08-11. * Apache Airflow 3.0.4 was released on 2025-08-08. * Task SDK 1.0.4 was released on 2025-08-08. * Provider packages 2025-07-29 was released on 2025-08-02. * Provider packages 2025-07-17 was released on 2025-07-18. * Apache Airflow 3.0.3 was released on 2025-07-14. * Task SDK 1.0.3 was released on 2025-07-14. * Apache Airflow Helm Chart 1.18.0 was released on 2025-07-13. * Provider packages 2025-07-08 was released on 2025-07-12. * Provider packages 2025-07-03 was released on 2025-07-06. * Provider packages 2025-06-20 was released on 2025-06-24. * Apache Airflow Helm Chart 1.17.0 was released on 2025-06-23. * Provider packages 2025-06-15 was released on 2025-06-18. * Apache Airflow Python Client 3.0.2 was released on 2025-06-13. * Apache Airflow 3.0.2 was released on 2025-06-10. * Task SDK 1.0.2 was released on 2025-06-10. Following the expectation of the board - we mention that there were several accelerated votes - 3.0.5rc3 and 3.0.3rc4 mostly due to late bugs found after extensively testing previous rcs (several) where the voting would cause unnecessary prolonging of waiting for fixes by the users. Each of the combined periods for rc1 - N was more than a week in total and with our reproducibility checks we could easily verify that only few bug fixes were added since previous rcs so we decided to shorten voting periods for those after deliberate considerations. We also eventually yanked 3.0.5 due to another issue found in some common configurations even after all the extensive testing. But we released 3.0.6 fairly quickly after. ## Community Health: The community is healthier than ever. Despite the holiday season, Airflow 3 release poured a new energy in the community. Over the last 6 months (including holidays season) we have sustained the velocity of ~600 PRs merged a month (average ~20/day, 7 days/week !) and regularly ~150 contributors contributing on a monthly basis. A number of users are engaging and helping us to test and perfect Airflow 3. We are gearing up for the 6th Airflow Summit in Seattle, US, with expected attendance of 600+ attendees, around 170 speakers and 130 sessions over 3 days 7-9 October. We also recognized the fact that many of our community members would not be able or willing (currently) to get to the US for physical gathering so we decided to follow the in-person event with an Online Reconnect Summit in the week following the in-person Summit. We give both - attendees and speakers an opportunity to connect in this way. More information: “Airflow Summit” https://share.google/oauPlbl7kuCsUui5l We also used the Targeted Sponsorship from Bloomberg to cover the costs of travel and accommodation for several members of our community who could not afford the trip otherwise to bring them to the Summit. As usual (that became sort of tradition) before the summit we are gearing up and starting discussions on inviting a number of collaborators to become committers so that we can announce them at the Summit in front of the audience. Due to high volume and multiple contributions during Airflow 3, we have quite diverse pool of candidates - especially in the area of UI that had traditionally been understaffed, but we seemed to have amazing UI contributions from a number of new contributors - including the fact that last voting for PR of the month actually ended up with selecting 3 (!) UI PRs to become collective winners. After the holiday period we seem to be ready to evaluate and assess new candidates. ----------------------------------------- Attachment B: Report from the Apache Allura Project [Dave Brondsema] ## Description: The mission of Apache Allura is the creation and maintenance of software related to a software development infrastructure platform commonly known as a "forge" ## Project Status: Current project status: Ongoing (moderate activity) Issues for the board: none ## Membership Data: Apache Allura was founded 2014-03-18 (11 years ago) There are currently 18 committers and 18 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Carlos Cruz on 2024-06-26. - No new committers. Last addition was Carlos Cruz on 2024-06-27. ## Project Activity: - added support for Python 3.12 and 3.13 - removed deprecated pkg_resources code - HTML sanitization improvements - python dependency upgrades ## Community Health: - made a release! - development is slow, mostly in maintenance mode, but "active maintenance" keeping up with new versions of things and improving security posture - no new community members for a while ----------------------------------------- Attachment C: Report from the Apache Atlas Project [Madhanmohan Neethiraj] ## Description: The mission of Apache Atlas is the creation and maintenance of software related to a scalable and extensible set of core foundational governance services - enabling enterprises to effectively and efficiently meet their compliance requirements ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: none ## Membership Data: Apache Atlas was founded 2017-06-20 (8 years ago) There are currently 50 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Pinal Shah on 2025-01-29. - Disha Talreja was added as committer on 2025-07-11 ## Project Activity: - added support for TLS 1.3 - fix import-hive utilty failure in handling shell entities - fix in Hive hook handling of Apache Ozone paths - fix to address stale transaction warnings - fix to eliminate auto-creation of JanusGraph properties - performance improvements in processing notifications from Spark hook - performance improvements in authorizing entity access - code readability improvements in Impala, Storm, Sqoop, Kafka, typedef modules - Docker setup updated with addition of healthcheck - improve async-import module initialization - improve unittest coverage in Hive and Impala modules - multiple UI fixes - dependent library version upgrades: spring-ldap-core, poi-ooxml - WIP to support Trino metadata - WIP to support RDBMS as backend store for JanusGraph, instead of HBase/Cassandra ## Community Health: - dev@atlas.apache.org had a 12% increase in traffic in the past quarter (535 emails compared to 474) - 47 JIRA tickets opened and 41 closed in the past quarter. - 46 commits in the past quarter. - 15 code contributors in the past quarter (14 in the last report) ## Recent releases: - Apache Atlas 2.4.0 was released on 2025-01-04. - Apache Atlas 2.3.0 was released on 2022-12-06. - Apache Atlas 2.2.0 was released on 2021-08-17. - Apache Atlas 2.1.0 was released on 2020-07-15. ----------------------------------------- Attachment D: Report from the Apache Axis Project [Robert Lazarski] # Apache Axis Board Report ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues There are no issues requiring board attention at this time. ## Membership Data: Axis was created on 2001-01-19 (24 years ago). It is listed as established in 2009-12 but really the first Apache commit was in 2001. There are currently 65 committers and 64 PMC members in this project, a vote in 2010 made all committers automatically PMC members. One PMC member resigned. Community changes, past quarter: - Currently 64 PMC/ 65 Committers members. - No new committers were added in the last 90 days, Andreas Lehmkühler was added on January 28th, 2025 and Christian Ortlepp on January 2nd, 2025. Both were added to the PMC on January 28th, 2025. ## Project Activity: Recent releases: - Axis 2/Java 2.0.0 was released on March 10, 2025. - Axis 2/Rampart 1.8.0 was released on Dec 10, 2024. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Project state: Ongoing, with moderate activity ## Health report: Now that our community is stabilized by adding two new committers this year to the PMC and after an exhausting Axis2/Java 2.0.0 release to support jakarta, we finally can return the Axis team focus to areas that need the most help - with the arrival of modern AI tools being good timing. Axis2/C has been maintained in recent years by PMC member Bill Blough and he is still active on the mailing list, while one of the early contributors to the project and PMC member Nandika Jayawardana has made commits this year. There was a community contribution adding JSON support a few years ago to Axis2/C, allowing the use of the lib in modern workflows that abandoned SOAP and XML long ago. That support has some Java developers who know enough C/C++ to give it a look where JSR-223 projects such as Rhino and Javet and not performant enough to run huge JavaScript projects initiated by JSON. See recent commits in Axis2/C and future roadmap discussions on the Axis2/C mailing list. Axis2/Java had a quite quarter, though we did upgrade XMLBeans from 3.x to 5.3.0. A special thanks to Apache POI, for rescuing the project out of the attic a few years ago. The Axis2 community still lacks committers for Apache Rampart (ws-security*) who use it in their own projects, while there are too may users to simply ignore it. Our volunteer community released Rampart 1.8.0 last year, and are committed to supporting a Apache Rampart 2,0.0 this upcoming quarter, with the jakarta support provided by Axis2/Java as it is not a standalone project. ## Axis2 java Jira issues opened in the last 90 days: 1 ## Axis2 java Jira issues closed in the last 90 days: 2 ----------------------------------------- Attachment E: Report from the Apache Beam Project [Kenneth Knowles] ## Description: The mission of Apache Beam is the creation and maintenance of software related to a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Beam was founded 2016-12-20 (9 years ago) There are currently 99 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 4:1. Community changes, past quarter: - No new PMC members. Last addition was Danny McCormick on 2024-12-12. - Joey Tran was added as committer on 2025-08-20 ## Project Activity: - Beam Summit 2025: The annual Beam Summit was held in New York City on July 8th and 9th. We also held the mini-online session on July 30. All the videos are available at Apache Beam YouTube channel (https://www.youtube.com/channel/UChNnb_YO_7B0HlW6FhAXZZQ). - Google Summer of Code (GSoC) 2025: The Beam project has several proposed projects for the 2025 Google Summer of Code, which were finished successfully. The proposed projects include work on the JupyterLab sidepanel, Beam YAML, integrations with vector databases and feature stores, and enhancements to the platform's infrastructure and accessibility . - Beam 3.0: A community-led effort has started to define the scope of a future "Beam 3.0" major version and the progress is tracked by https://github.com/apache/beam/milestone/31. Some deprecations and removals are done for Beam 3.0: - Java 8 support is now deprecated and is scheduled for removal in Beam 3.0. - Additionally, cross-language pipelines using the IO expansion-service now require a Java 11+ runtime. - The previous