Index
Links: 2025 - All years
- Original 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 <bkoehm@apache.org>
* David Estes <davydotcom@apache.org>
* Graeme Rocher <grocher@apache.org>
* James Daugherty <jdaugherty@apache.org>
* James Fredley <jamesfredley@apache.org>
* Lari Hotari <lhotari@apache.org>
* Mattias Reichel <matrei@apache.org>
* Paul King <paulk@apache.org>
* Puneet Behl <puneetb@apache.org>
* Sergio del Amo <sdelamo@apache.org>
* Soeren Glasius <sbglasius@apache.org>
* Walter Duque de Estrada <borinquenkid@apache.org>
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 <jibin@apache.org>
* Warren Chen <warren@apache.org>
* Felix Cheung <felixcheung@apache.org>
* Julien Chinapen <e2corporation@apache.org>
* Lidong Dai <lidongdai@apache.org>
* Sijie Guo <sijie@apache.org>
* Lynwee Hou <lynwee@apache.org>
* Willem Ning Jiang <ningjiang@apache.org>
* Jonathan O'Donnell <joncodo@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
* Cong Wang <narro@apache.org>
* Maxim Wheatley <maximwheatley@apache.org>
* Klesh Wong <klesh@apache.org>
* Hezheng Yin <hez@apache.org>
* Kaiyun Zhang <zky@apache.org>
* Liang Zhang <zhangliang@apache.org>
* Liang Zhang <zhangliang2022@apache.org>
* Zikuan <abeizn@apache.org>
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 previously deprecated Beam ZetaSQL component has been removed, and
users are advised to migrate to Calcite SQL with the BigQuery dialect.
- The native SpannerIO in the Python SDK is now deprecated in favor of
the cross-language wrapper.
- The Samza and Twister2 runners are deprecated and scheduled for removal
in Beam 3.0.
**Interesting Technical Discussions**
- Modernizing GCS Integration: A proposal has been drafted to modernize the
GCSUtil in the Beam Java SDK
(https://s.apache.org/beam-gcsutil-modernization).
- IcebergIO Improvements: There have been discussions around improving
timestamp handling in IcebergIO
(https://s.apache.org/beam-timestamp-strategy) and addressing gaps in metadata
management for better usability.
- Portable Raw Type: a proposal to allow Beam to further embrace structured
data by allowing easier embedding of less-structured data within structured
rows (https://s.apache.org/beam-portable-raw-type)
- Multimodal embeddings: design for supporting these in Beam Python/ML
https://s.apache.org/beam-multimodal-embeddings
## Community Health:
Community activity remains essentially flat. The user list is more and more
rarely used, which may be a sign of the times. The dev list has roughly the
same amount of design and discussion.
-----------------------------------------
Attachment F: Report from the Apache Bigtop Project [Masatake Iwasaki]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Bigtop was founded 2012-09-19 (13 years ago)
There are currently 46 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhiguo Wu on 2024-08-19.
- No new committers. Last addition was Liqiang Fu on 2025-05-13.
## Project Activity:
Recent releases:
- 3.4.0 was released on 2025-05-30.
- bigtop-manager-1.0.0 was released on 2025-04-24.
- 3.3.0 was released on 2024-07-08.
Release vote of Bigtop 3.5.0 is ongoing[1].
This is the first release including Apache Airflow[2] in the stack.
[1] https://lists.apache.org/thread/8xd84b84zlt8k5f9d6pc22ngngbjjxbd
[2] https://issues.apache.org/jira/browse/BIGTOP-4360
## Community Health:
No committer/PMC member was added in the past quarter.
It would be nice to add more active contributors and committers.
Since our cycles are consumed for preparing 3.5.0 release in this quarter,
the statistics shows slight decrease in the activity.
- dev@bigtop.apache.org had a 8% decrease in traffic in the past quarter
(232 emails compared to 251):
- issues@bigtop.apache.org had a 12% decrease in traffic in the past quarter
(163 emails compared to 185):
- 58 JIRA tickets opened and 56 closed in the past quarter.
-----------------------------------------
Attachment G: Report from the Apache BookKeeper Project [Enrico Olivelli]
## Description:
The mission of BookKeeper is the creation and maintenance of software related
to Replicated log service which can be used to build replicated state machines
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache BookKeeper was founded 2014-11-19 (11 years ago)
There are currently 32 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Shiji Lu on 2025-05-14.
- No new committers. Last addition was Zhangjian He on 2025-01-27.
## Project Activity:
Recent releases:
4.16.7 was released on 2025-07-07.
4.17.2 was released on 2025-07-07.
4.16.6 was released on 2024-06-26.
## Community Health:
Community is in good shape. We are accepting contributions, most of them come
from committers. We cut some releases in the past months. I can see
discussions on Slack from users not coming from Apache Pulsar, that is
currently the main consumer of BookKeeper, and this is a good sign.
-----------------------------------------
Attachment H: Report from the Apache BuildStream Project [Tristan Van Berkom]
## 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:
There have been some releases since the last board report, I believe I missed
the last board report because I had a hard time resetting my password at the
time with id.apache.org.
Generally speaking, we have made a lot of progress with supporting functionality
for the generation of SBoMs, and ongoing soon to be released work includes
exposing CAS digests of artifacts on the command line (optimizing binary
comparisons for reproducibility checks), and much progress has been made towards
running REAPI tools such as recc and bazel from within the build sandbox.
## Community Health:
Community health is stable, I believe we tried to onboard a new committer
and that has not concluded yet.
There have been some contributions from new people since the last report,
including some work towards a new `bst inspect` command as a more practical
and machine readable alternative to `bst show`
-----------------------------------------
Attachment I: Report from the Apache BVal Project [Matt Benson]
-----------------------------------------
Attachment J: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: There
are no issues requiring board attention at this time.
## Membership Data:
Apache Camel was founded 2008-12-17 (17 years ago)
There are currently 94 committers and 48 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Federico Mariani was added to the PMC on 2025-07-22
- No new committers. Last addition was Thomas Diesler on 2024-11-22.
## Project Activity:
Apache Camel:
- We released Camel 4.8.7
- We released Camel 4.8.8
- We released Camel 4.10.6
- We released Camel 4.13.0
- We released Camel 4.14.0
- Note: Camel releases have synchronized releases of Camel-Karaf and
Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
synchronized.
- 4.14.x is our last LTS release train together with 4.10.x
- The situation is really healthy and the community is increasing presence and
engagement. We are introducing many new features and working. Camel is
growing even in terms of interest and new contributors.
Apache Camel K:
- Camel K 2.7.0 has been released in June.
- Camel K is in good shape and the community is expading with new contributors
and many new good idea and many good interactions and feedback. The
situation is healthy.
- We are planning on supporting the latest LTS 4.14.x on the next Camel K
release.
Apache Camel Kamelets:
- We released Camel Kamelets 4.10.6
- We released Camel Kamelets 4.13.0
- We released Camel Kamelets 4.14.0
- The 4.10.x release train is matching the LTS release from Camel core and
it's an important building block for starting with routes
- Now we are supporting also the last LTS Release train 4.14.x, with the
4.14.0 release.
- We are improving the documentation and increasing the number of Kamelets.
Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
multiple releases
- We released Camel-quarkus 3.20.2
- We released Camel-quarkus 3.24.0
- We released Camel-quarkus 3.25.0
- We released Camel-quarkus 3.26.0
- A lot of work has been done on testing side more new features and extensions
have been developed and improved. We are increasing the number of Camel
Quarkus Extension to match the core components.
- The community is vibrant and we have a lot of new issues and requests.
Apache Camel-Karavan:
- Camel-Karavan is still growing.
- There were no new releases at this stage.
- The 4.10.x is aligned to Camel 4.10.x LTS
- We are planning to support 4.14.x LTS with the next release.
Camel-Kafka-Connector:
- 4.11.0 have been released and based on the a development version.
- We want to release a 4.14.x based version
- The community is active and we receive a lot of feedback and requests. We
are improving the documentation.
- The project is slowing down a bit for the summer break, but we are working
on it.
Apache Camel-Karaf:
- Camel-karaf 4.10.5 has been released.
- It's a patch version supporting LTS 4.10.x
- The plan is to support 4.14.x LTS.
Apache Camel-Upgrade-Recipes:
- Camel-Upgrade-Recipes 4.14.0 has been released
- This version supports upgrades up to 4.14.0
- The plan is to keep supporting 4.10.x patches (if needed) and 4.14.x LTS
## Community Health:
dev, users and issues mailing lists decreased in usage in this quarter, this
is mainly because we are receving a lot of issues and requests on Zulip chat,
so the mailing lists activities are slowing down, but the engagement is still
really high. We are mainly consolidating our work on Camel, by introducing new
components and new features but also by working on backlog. In terms of Github
engagement we are doing really well and we see new contributors and reporters.
-----------------------------------------
Attachment K: Report from the Apache CarbonData Project [Jacky Li]
Duraing last two month (Jul ~ Aug):
1. CarbonData merged 1 full request which is a security issue fix:
https://github.com/apache/carbondata/pull/4367
2. New direction of CarbonData is discussed in maillist and github issue page:
https://github.com/apache/carbondata/issues/4368
Since there is not many new features are required and CarbonData is quite
stable now, developers in the community is discussing some new directions for
next step of CarbonData, like data storage for AI and data loop framework for
AI Agents.
Now is the transition time for CarbonData project, I think community will keep
discussing and come up with some cool features in the coming month.
-----------------------------------------
Attachment L: Report from the Apache Cayenne Project [Michael Gentry]
# Apache Cayenne Board Report, September 2025
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object graph persistence and provides an ORM
runtime, remote persistence services*, and a cross-platform GUI
database mapping/modeling/development tool.
*Remote persistence services are being phased out for 5.0 (milestone
stage) to simplify the product. We could only identify one user of this
feature and he is switching to RESTful services.
## Project Status
### Project State
Ongoing
### Issues for Board
None
## Membership Data
Apache Cayenne was founded 2006-12-19 (19 years ago).
There are currently 24 committers and 9 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 Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Jurgen Doll on 2024-08-27.
## Project Activity
After the release of 4.2.x, most development has shifted to 5.0. Versions
prior to 5.0 are maintenance-only.
- Cayenne 4.0.x (stable)
- Maintenance only.
- Cayenne 4.1.x (stable)
- Maintenance only.
- Cayenne 4.2.x (stable)
- Maintenance only.
- Cayenne 5.0 (milestone)
- New features and primary development.
Cayenne 4.2.2 (a maintenance/bug-fix release) was released in March.
### Releases
- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2.2 on 2025-03-14.
- Cayenne 5.0.M1 on 2024-09-09.
## Community Health
Cayenne is healthy, but activity over the summer was slow. Developer and
user mailing list traffic was down with no new release.
Code commits were for the 5.0.x and 4.2.x branches.
-----------------------------------------
Attachment M: Report from the Apache CloudStack Project [Nicolás Vázquez]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors,
storage, and networking devices.
## Project Status:
Current project status: Ongoing, with high activity
Issues for the board: None
## Membership Data:
Apache CloudStack was founded 2013-03-19 (12 years ago)
There are currently 143 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Pearl Dsilva on 2025-04-02.
- Bernardo De Marco Gonçalves was added as committer on 2025-07-11.
- Jamie Pell was added as committer on 2025-07-23.
## Project Activity:
Software development/management activity:
- The current version of Apache CloudStack is 4.21.0.0.
- The versions released in the past quarter are:
- 4.21.0.0 was released on 2025-08-28.
- The community is planning to release Apache CloudStack 4.20.2.0 by end of
September 2025
- The community is planning to release Apache CloudStack 4.22.0.0 by October
2025.
- The latest Apache CloudStack CLI (CloudMonkey) version 6.5.0 was released on
September 2 2025.
- The latest CloudStack-Go SDK version 2.17.1 was released on June 20 2025.
- The community is planning to release a new version of the CloudStack
Terraform Provider (version 0.6.0) by end of September 2025.
Meetups and Conferences:
- CloudStack India User Group 2025 was held on July 11, 2025 in Delhi-NCR:
https://cloudstack.apache.org/blog/csiug-2025
- CloudStack European User Group is scheduled for September 18, 2025 in
London, UK: https://cloudstack.apache.org/blog/cseug-2025-london
- CloudStack Collaboration Conference 2025 is scheduled for November 19-21,
2025 in Milan, Italy: https://www.cloudstackcollab.org/
## Community Health:
- According to the reporter tool, the Community Health Score (Chi) is
10.00 (Super Healthy).
- Mailing lists statistics:
- dev@cloudstack.apache.org had a 82% increase in traffic in the past
quarter (1076 emails compared to 588)
- issues@cloudstack.apache.org had a 26% increase in traffic in the past
quarter (92 emails compared to 73)
- marketing@cloudstack.apache.org had a 733% increase in traffic in the
past quarter (25 emails compared to 3)
- users@cloudstack.apache.org had a 4% decrease in traffic in the past
quarter (1385 emails compared to 1442)
- Recent releases:
- 4.21.0.0 was released on 2025-08-28.
- 4.19.3.0 was released on 2025-06-10.
- 4.20.1.0 was released on 2025-06-10.
-----------------------------------------
Attachment N: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java-focused
reusable libraries and components
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: None.
## Membership Data:
Apache Commons was founded 2007-06-19 (18 years ago)
There are currently 150 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Arnout Engelen on 2024-12-22.
- No new committers. Last addition was Arnout Engelen on 2024-12-23.
## Project Activity:
The project is active with the following releases in this reporting period:
- PARENT-87 was released on 2025-08-24.
- PARENT-86 was released on 2025-08-19.
- CLI-1.10.0 was released on 2025-08-02.
- NET-3.12.0 was released on 2025-08-01.
- CSV-1.14.1 was released on 2025-07-30.
- COMPRESS-1.28.0 was released on 2025-07-29.
- RELEASE-PLUGIN-1.9.1 was released on 2025-07-26.
- TEXT-1.14.0 was released on 2025-07-24.
- BUILD-PLUGIN-1.16.0 was released on 2025-07-22.
- CODEC-1.19.0 was released on 2025-07-22.
- IO-2.20.0 was released on 2025-07-18.
- LANG-3.18.0 was released on 2025-07-09.
- VALIDATOR-1.10.0 was released on 2025-07-09.
- PARENT-85 was released on 2025-06-19.
- FILEUPLOAD-2.0.0-M4 was released on 2025-06-16.
## Community Health:
We are busy handling pull requests, Jira tickets, and responding to reports on
the security mailing list. We've approved many requests for Jira accounts
where we are dealing with bug reports and requests for new features.
-----------------------------------------
Attachment O: Report from the Apache Cordova Project [Bryan Ellis]
## Status report for the Apache Cordova project - Sept 2025
## Description
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Project Status
**Current project status:**
Our current work focuses on staying up to date by making improvements to
internal tooling, core platforms, and the CLI.
Our status dashboard at http://status.cordova.io remains mostly all green
and our nightly builds are still stable.
**Issues for the board:**
There are no issues requiring board attention at this time.
## Membership Data
There are currently 100 committers and 97 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
**Community changes, past quarter:**
- Last addition was Manuel Beck was added to the PMC on 2025-04-04
- Last addition was Manuel Beck was added as committer on 2025-04-04
## Project Activity
The following releases made to our project this quarter focused on core
platforms and plugins to keep up with current requirements.
**Releases:**
- cordova-app-hello-world@7.0.0 was released on 2025-08-29.
- cordova-fetch@5.0.0 was released on 2025-08-29.
- cordova-common@6.0.0 was released on 2025-08-08.
- cordova-eslint@6.0.0 was released on 2025-07-25.
## Community Health
Overall, the community health is strong. The ASF Project Statistics gives
the project a Community Health Score (Chi): 10.00 (Super Healthy)
This quarter, we primarily focused on improving our internal packages used
by the CLI and platforms. These packages form part of the CLI's tree
structure, which we are preparing for the next major release. Additionally,
some of these internal packages and libraries are also used by our core
platforms, making them essential for upcoming platform releases as well.
We continue to see valuable contributions from a group of dedicated
individuals. The project remains stable and continues to see good traffic.
Github discussions is how our community supports each other and is live at
https://github.com/apache/cordova/discussions. All discussions are
forwarded to the 'issues' list.
## Mailing List Activity
- dev@cordova.apache.org had a 100% increase in traffic in the past quarter
(44 emails compared to 22)
- issues@cordova.apache.org had a 113% increase in traffic in the past
quarter (1072 emails compared to 503)
-----------------------------------------
Attachment P: Report from the Apache cTAKES Project [Pei J Chen]
## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache cTAKES was founded 2013-03-19 (12 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 Gandhi Rajan on 2018-07-12.
- No new committers. Last addition was Dennis Johns on 2023-01-06.
## Project Activity:
- Committee continues to work on the future release (7.x.x)
- 6.0.0 was released on Sept 16 2024
- 5.1.0 was released on May 10 2024
- 4.0.0.1 was released on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
## Community Health:
dev@ctakes.apache.org had a 94% decrease in traffic in the past quarter
(1 emails compared to 15 as of 2025-09-08). Mail traffic has always been light
hence the % is more dramatic from report to report. Historically, the summer
is also generally slower than usual.
-----------------------------------------
Attachment Q: Report from the Apache Curator Project [Enrico Olivelli]
## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Curator was founded 2013-09-18 (12 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Kezhu Wang on 2023-03-25.
- No new committers. Last addition was Kezhu Wang on 2023-03-24.
## Project Activity:
Recent releases:
5.9.0 was released on 2025-07-23.
5.8.0 was released on 2025-03-06.
5.7.1 was released on 2024-10-13.
## Community Health:
Community is doing well, while the activity on the project is pretty low. This
is not a new thing for Curator, as the project is stable, we are almost doing
bug fixes, together with keeping the pace with ZooKeeper releases. We don't
have many contributions from users that are not already committers, this is
not generally a good thing, but given the little amount of patches we (PMC)
don't find often good candidates for committership:usually people contribute
one one or two patches and then they are done. You can see this from GH
contributors page:
https://github.com/apache/curator/graphs/contributors?from=11%2F9%2F2024&to=9%2F14%2F2025
-----------------------------------------
Attachment R: Report from the Apache Daffodil Project [Mike Beckerle]
## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data Format Description Language (DFDL)
used to convert between fixed format data and more readily processed forms such
as XML or JSON
## Project Status:
Current project status: Ongoing. Moderate activity.
Issues for the board: None.
## Membership Data:
Apache Daffodil was founded 2021-02-16 (4 years ago)
There are currently 19 committers and 18 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 Peter Katlic on 2024-03-17.
- No new committers. Last addition was Peter Katlic on 2024-03-17.
## Project Activity:
The past 6 to 8 months, the project has mostly been dealing with the evolution
of our underlying Scala platform. Porting from Scala 2.12 to Scala 2.13 was
quite challenging, as much of the Scala built-in XML support that we were
strongly dependent on, was removed in Scala 2.13. The subsequent port to Scala
3 required significant changes that will impact all API-level Daffodil users.
Daffodil 3.11.0 was released on 2025-06-17 along with the matching Daffodil
SBT plugin 1.4.0. This is the last release using Scala 2 technology,
specifically the LTS Scala 2.13 version. If necessary we can support this
longer term as needed for Daffodil library users who have fielded products
using our Scala 2 code base who are unable to upgrade (more on this below) to
the forthcoming Daffodil 4.0.0 any time soon.
The Daffodil VSCode Extension 1.4.1 was released on 2025-06-30. The current
project activity includes better overall error handling, improved reliability
of Data Editor, Optimize and enhance the DFDL Schema syntax and semantic
support tools (e.g., Intellisense) to support Namespace-aware element
suggestions, several bug-fixes and enhancements to TDML functionality.
Daffodil 4.0.0 is in preparation. This major release uses Scala 3 technology,
and includes an entirely new and improved API necessitated by Scala-Java
interoperability changes in Scala 3. The Daffodil API no longer has a
Java/Scala dual API. It is defined entirely in Java. In addition to this
major API discontinuity, we have chosen to fix issues that would also require
a major version change - some non-conformities to the DFDL specification are
fixed, for example. This release requires our users to adapt to the new API,
but also to re-test all their DFDL schemas for sensitivities to the DFDL
language changes where they might have been depending on prior
non-DFDL-language conforming behavior. For example we know of users with 300+
DFDL Schemas in their company DFDL schema library. Few will be sensitive to
the DFDL language behavior changes, as they are in somewhat obscure aspects of
the DFDL language, but testing on the DFDL schemas available to us did show a
few schemas were incompatible and need updates for Daffodil 4.0.0. Ultimately
Daffodil 4.0.0 is clearly better than the prior versions and the API is more
supportable, but the vast bulk of the required changes added no value for our
users, who may wait for more value-add in subsequent releases before going
through the upgrade pain.
## Community Health:
Good activity level in developer email and commit activity.
User list activity is low. But regardless of this, it has been reported to us
that 14 corporations have embedded Daffodil in their products. Since they are
in the cybersecurity space, they don't participate in open-source forums nor
can we identify most of them here. One is the Broadcom Layer 7 API Gateway,
and a web search for that plus "DFDL" will find content about it.
Based on this we expect we have a reasonable user count despite the low level
of forum activity.
-----------------------------------------
Attachment S: Report from the Apache DataFusion Project [Andrew Lamb]
## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine
## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache DataFusion was founded 2024-04-16 (a year ago)
There are currently 50 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Tim Saucer was added to the PMC on 2025-06-14
- Siew Kam Onn was added as committer on 2025-06-17
- Matt Butrovich was added as committer on 2025-06-12
- Qi Zhu was added as committer on 2025-08-05
## Project Activity:
Note that almost all communication for DataFusion and its subprojects happens
on github and so our dev mailing list traffic is fairly light.
### DataFusion core
https://github.com/apache/datafusion
- 49.0.2 was released on 2025-08-25.
- 49.0.1 was released on 2025-08-18.
- 49.0.0 was released on 2025-07-26.
- 48.0.1 was released on 2025-07-07.
The DataFusion core project continues to mature, and we typically merge
multiple commits a day from a large variety of contributors. We are also
discussing [formalizing the process] for communicating and planning larger new
features. The community focus continues to be performance, and extensibility,
with relatively limited new feature work in the core
We have also improved the upgrade experience with [upgrade guides] and release
blogs such as for [48.0.0] and [49.0.0]
[upgrade guides]: https://datafusion.apache.org/
library-user-guide/upgrading.html
[formalizing the process]: https://github.com/apache/datafusion/issues/16886
[48.0.0]: https://datafusion.apache.org/blog/2025/07/16/datafusion-48.0.0
[49.0.0]: https://datafusion.apache.org/blog/2025/07/28/datafusion-49.0.0
### Sub project: DataFusion Python
https://github.com/apache/datafusion-python
DATAFUSION-PYTHON-49.0.0 was released on 2025-08-29. PYTHON-48.0.0 was
released on 2025-07-12.
### Sub project: DataFusion Comet
COMET-0.9.1 was released on 2025-08-25. COMET-0.9.0 was released on
2025-07-04.
https://github.com/apache/datafusion-comet
You can read about the recent happenings in Comet in the [0.9.0 blog]
[0.9.0 blog]: https://datafusion.apache.org/
blog/2025/07/01/datafusion-comet-0.9.0/
### Sub project: DataFusion Ballista
BALLISTA-48.0.0 was released on 2025-08-05. BALLISTA-47.0.0 was released on
2025-06-25.
https://github.com/apache/datafusion-ballista
### Sub project: DataFusion For Ray
We have archived this subproject as the original contributor and proposed
maintainer has taken a different approach to their project.
### Sub project: sqlparser-rs
SQLPARSER-0.58.0 was released on 2025-07-24. SQLPARSER-0.57.0 was released on
2025-06-23.
https://github.com/apache/datafusion-sqlparser-rs
Ifeanyi Ubah (iffyio) continues to do a great job reviewing PRs to keep the
code consistent and flowing and we are keeping up the pace with bi-monthly
releases.
## Community Health:
While we as always struggle with code review capacity,
we have many active committers, and the community in general helps each
other out with reviews. We continue to actively grow our committer
and PMC ranks.
We continue to merge multiple PRs a day from multiple committers and
have contributions from a wide variety of individuals with a wide
variety of employers.
-----------------------------------------
Attachment T: Report from the Apache Doris Project [Mingyu Chen]
-----------------------------------------
Attachment U: Report from the Apache ECharts Project [Wenli Zhang]
## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript
## Project Status:
Current project status: Ongoing
Issues for the board: NA
## Membership Data:
Apache ECharts was founded 2020-12-16 (5 years ago)
There are currently 30 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was ShiZhao Pan on 2025-01-09.
- No new committers. Last addition was ShiZhao Pan on 2025-01-05.
## Project Activity:
On July 30th, we released the major version Apache ECharts 6.0 and
carried out promotional activities, receiving warm praise from the
community. In this version, we have upgraded 12 major features,
including new themes, dynamic theme switching, chord charts,
beeswarm charts, broken axes, and reusable custom series.
## Community Health:
The release of Apache ECharts 6.0 was well received
by the community. With the 12 major feature upgrades, the community
has been developing in a stable and orderly manner. Community
members are actively contributing. This positive atmosphere is
fueling the continuous growth and enhancement of Apache ECharts 6.0.
-----------------------------------------
Attachment V: Report from the Apache EventMesh Project [Eason Chen]
## Description:
The mission of Apache EventMesh is the creation and maintenance of software
related to a fully serverless platform used to build distributed event-driven
applications
## Project Status:
Current project status: Ongoing:With moderate activity
Issues for the board: none
## Membership Data:
Apache EventMesh was founded 2023-03-22 (2 years ago)
There are currently 54 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jianbo Liu on 2024-01-05.
- No new committers. Last addition was Zikang Chen on 2025-01-28.
## Project Activity:
For AI agent and workflow feature is under developing
Part of new feature EventMesh Dashboard has been merged.
Enhancement for EventMesh netty io thread improve has been merged.
## Community Health:
The new features were under designing or developing,
so the commits and PR activity seems decrease.
Contributors increased slightly compared to the previous quarter.
Overall community health is good.
-----------------------------------------
Attachment W: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Project Status:
Current project status: Ongoing, with low activity.
Issues for the board: none.
## Membership Data:
Apache Felix was founded 2007-03-28 (18 years ago)
There are currently 68 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Paul Rütter was added to the PMC on 2025-06-16
- No new committers. Last addition was Paul Rütter on 2024-11-15.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- Released 3 components. Mostly bug fixes/minor improvements.
### Releases
- org.apache.felix.scr-2.2.14 was released on 2025-09-04.
- org.apache.felix.webconsole-5.0.14 was released on 2025-08-27.
- org.apache.felix.http.base-5.1.16 was released on 2025-06-08.
## Community Health:
- Overall the project is in ok health with little ongoing activity.
- The community activity remains on a low level and we continue to see little
new development right now.
- We added a new PMC member!
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues. Traffic has
been very low.
- We had no issues voting on releases and JIRA issues are generally addressed.
-----------------------------------------
Attachment X: Report from the Apache Flex Project [Harbs]
## Description:
The mission of the Apache Flex project is to create and maintain software
related to the development of expressive web applications that deploy to all
major browsers, desktops and devices (including smartphones, tablets and tv)
## Project Status:
Current project status: For the first time in years, one of the PMC members is
doing work to update some of the components.
Issues for the board: None
## Membership Data:
Apache Flex was founded 2012-12-19 (13 years ago) There are currently 67
committers and 45 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 Greg Dove on 2023-03-03.
- No new committers. Last addition was Greg Dove on 2016-09-07.
## Project Activity:
There was an uptick in activity this month due to work being done.
## Community Health:
The community is quiet but stable. There was discussion a couple of months ago
about possibly retiring the project and the consensus was that it's not
appropriate at this time.
-----------------------------------------
Attachment Y: Report from the Apache Flink Project [Robert Metzger]
## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Flink was founded 2014-12-17 (11 years ago)
There are currently 121 committers and 55 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Ron Liu was added to the PMC on 2025-08-13
- No new committers. Last addition was Xiqian Yu on 2025-04-21.
## Project Activity:
The Flink PMC is operating in a steady state of reviewing committers
/ PMC candidates / releases / trademark / security reports.
We've released Flink 2.1 early August with features around supporting
AI models in Flink SQL, process table functions in Flink SQL as a
really flexible user-defined functions model, and SQL runtime
optimizations.
We also released bugfix version for Flink 1.19.3, 1.20.2 and a 4.0.1
for the Flink Kafka connector.
flink-agents.git has been added as a new sub repository to explore
Flink for agentic AI.
Flink 2.2 is scheduled for end of November.
## Community Health:
Community health is looking good. There's a bit of a decrease
in mailing list activity, but based on our experience, this is caused
by the summer vacation season.
The paper about Disaggregated State Management in
Apache Flink® 2.0 has been accepted by VLDB 2025.
Flink Forward Asia happened in Singapore early July, with a lot of
interesting talks.
There's an initiative in the community to allow external reviewers
to review and get more attention to reviewed pull requests. This
initiative is using GitHub Pull Request labels.
-----------------------------------------
Attachment Z: 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 language implementations, improving release
infrastructure, 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:
1) v0.12.1 September 1, 2025
2) v0.12.0 August 18, 2025
3) v0.11.2 — July 10, 2025
4) v0.11.1 June 27, 2025
5) v0.11.0 June 17, 2025
These releases include performance improvements, bug fixes, expanded language
support, and enhanced developer tooling.
Project Activity: Development activity remains robust, with ongoing work
across multiple fronts:
1) Continuous improvement of documentation for users and contributors;
2) Refinement of the release pipeline to improve reliability and automation
3) Active development on Fory implementations in Rust, Python, and Go
Current Plans: The project’s roadmap for the coming months includes:
1) Reaching General Availability (GA) status for the Python, Rust, and Go language bindings
2) Expanding adoption through outreach and integration examples
3) Attracting new contributors via outreach and improved contribution guides
4) 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:
1) Committer: Emre Şafak was added on August 28, 2025
2) 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 AA: Report from the Apache Geode Project [Mark Bretl]
## Description:
The mission of Apache Geode is the creation and maintenance of software related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud architectures.
## Project Status:
Current project status: Ongoing, increased from dormant
Issues for the board: None
## Membership Data:
Apache Geode was founded 2016-11-15 (9 years ago)
There are currently 120 committers and 31 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 Calvin Kirs on 2022-11-14.
- Arnout Engelen was added as committer on 2025-08-14
- Jinwoo Hwang was added as committer on 2025-08-07
## Project Activity:
The community is in the beginning steps to create a release for the first time
in over three years with several bug fixes. The release is expected in
September.
## Community Health:
There has been an increase in overall activity and health of the community.
Recently there has been a group of users that have stepped up after learning
the project was on the way to being deactivated and hopes to keep the project
alive. The community was able to identify some bugs to fix intially and work
with the new committers to test and check in the code for a release. We hope
we will be able to continue this momentum with creating more stable releases.
-----------------------------------------
Attachment AB: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AC: Report from the Apache Gobblin Project [Abhishek Tiwari]
## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Gobblin was founded 2021-01-19 (4 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was Abhishek Mahendra Jain on 2025-01-18.
- Vivek Rai was added as committer on 2025-01-18.
## Project Activity:
- Added an error-classification framework that prioritizes and tags job
failures using configurable pattern matching, integrated with existing issue
handling.
- Added emission of a flow-level event when a flow deadline is exceeded to
improve SLA tracking.
- Added emission of metrics when DAG action fails, improving observability of
orchestration failures.
- Enhanced tasks with no effective copy work to be marked for data quality
evaluation, alongwith bytes-read/bytes-written metrics.
- Optimized Apache Iceberg data-file payloads from byte array to base64
strings for significantly faster (and lower-memory) (de)serialization.
- Enhanced construction of Apache Iceberg data-file lists during the commit
step (instead of accumulating everything earlier), reducing heavy
serialization/deserialization and proven on a 35 TB/66k-partition copy.
- Added improvement to propagate file-system job properties into WorkUnit
metadata to carry FS context through workflows.
- Removed an unnecessary CopyEntity deserialization by reusing the in-scope
object, shaving overhead in copy flows.
- Added a write-path optimization for serialized WorkUnits.
- Last Release date: 30th August, 2023.
## Community Health:
- Since June 2025, there have been 17 commits - all made by relatively new,
non-committer contributors.
- Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as committers.
We constantly look for consistent contributors to vote them in as
Committers.
-----------------------------------------
Attachment AD: Report from the Apache Gravitino Project [Jerry Shao]
## Description:
The mission of Apache Gravitino is the creation and maintenance of software
related to managing your data and AI assets seamlessly with a flexible,
unified governance framework, including lakehouse federation capabilities
## Project Status:
Current project status: New Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-21 (4 months 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 Ashish Singh on 2025-05-21.
- Abyss-lord was added as committer on 2025-07-07
## Project Activity:
Software Development Progress:
1. We're under the release of the Apache Gravitino 1.0.0.
2. Next release milestone has settled.
3. Next release targeted features are under development.
Community activities:
1. Community Over Code NA Apache Gravitino talk.
2. QCon Shanghai Apache Gravitino talk has been accepted.
## Community Health:
1. dev@gravitino.apache.org had a 36% decrease in traffic in the past quarter
(142 emails compared to 221)
2. 186 issues were created in the last 30 days. 292 issues have closed in the
last 30 days.
3. 285 PRs have been created in the last 30 days. 209 PR has been merged in
the last 30 days.
-----------------------------------------
Attachment AE: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment AF: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Guacamole was founded 2017-11-14 (8 years ago)
There are currently 16 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- No new committers. Last addition was Corentin Soriano on 2025-01-18.
## Project Activity:
The 1.6.0 release has finally gone out and development efforts have shifted
toward addressing any regressions and preparing a 1.6.1 patch/bugfix release.
An RC within the next few weeks seems likely.
- 1.6.0 was released on 2025-06-22.
- 1.5.5 was released on 2024-04-05.
- 1.5.4 was released on 2023-12-07.
## Community Health:
The community continues to be active and healthy. Activity on the mailing list
shows good usage of 1.6.0, as well as bug reports that are feeding into plans
for 1.6.1.
-----------------------------------------
Attachment AG: Report from the Apache Gump Project [Stefan Bodewig]
## Description
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well as
non-ASF projects and their dependencies. It started in the Java part
of the foundation but also builds projects like APR, HTTPd and
OpenSSL.
## Project Status
Current Status: dormant - when things need to be done, they get done
Issues: There are no issues requiring board attention.
## Membership Data
Apache Gump was founded 2004-02-18. There are currently 16 committers
and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
No new PMC members. Last addition was Mark Thomas on 2014-12-03.
No new committers. Last addition was Konstantin Kolinko on 2015-02-11.
## Project Activity
The Tomcat community is the only one still using Gump actively and the
only activity in Gump is around keeping the infrastructure alive and
tweaking things for the benefit of Tomcat builds.
We will certainly support any other project that wants to get the
benefit of the early warning system for backwards incompatible changes
Gump provides, but we are not actively recruiting projects.
## Releases
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
## Community Health
There isn't much happening but help is there when anybody needs it.
-----------------------------------------
Attachment AH: Report from the Apache Helix Project [Junkai Xue]
## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: N/A
## Membership Data:
Apache Helix was founded 2013-12-17 (12 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- No new committers. Last addition was Molly Gao on 2023-06-06.
## Project Activity:
- 1.3.2 was released on 2025-07-02.
- 1.4.3 was released on 2024-02-04.
- 1.4.2 was released on 2024-11-28.
## Community Health:
- Apache 2.0 final testing: there was a performance testing result lost.
Before merge the code to main branch, would like to perform the testing
in a reasonable environment again. Looking for release Apache Helix 2.0
by end of 2025.
- Minor bug fixings for several other open source projects such as: Venice,
Apache Pinot.
- Revisiting the major feature for cloud support: virtual topology grouping
collaborating users to enhance the feature.
-----------------------------------------
Attachment AI: Report from the Apache HertzBeat Project [Chao Gong]
## Description:
The mission of Apache HertzBeat is to deliver an open, user-friendly, and
intelligent real-time observability platform that enables users worldwide to
efficiently monitor and understand their systems, reduce operational
complexity, and enhance service reliability.
## Project Status:
Current project status: New.
New Issues for the board: none.
## Membership Data:
Apache HertzBeat was founded 2025-08-21 (10 days ago). There are currently 10
Committers and 18 PMC members in this project. The Committer-to-PMC ratio is
5:9.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
- Our community is participating in the GSOC 2025.
- Our community is participating in the OSPP 2025.
- We have confirmed the release manager for version 1.7.3 and are preparing to
release new version.
- Held one community online meetups in last quarter.
## Community Health:
- New contributor +3
- In the past month, 25 authors have pushed 75 commits to master and 131
commits to all branches, 75 PRs merged.
Overall the project is progressing well. We are actively attracting more
production users and contributors by improving documentation, enhancing
stability, and strengthening features.
-----------------------------------------
Attachment AJ: Report from the Apache Hive Project [Naveen Gangam]
-----------------------------------------
Attachment AK: Report from the Apache Hop Project [Hans Van Akelyen]
-----------------------------------------
Attachment AL: Report from the Apache HttpComponents Project [Michael Osipov]
## Description:
The mission of HttpComponents is the creation and maintenance of software
related to Java toolset of low level HTTP components
## Project Status
- There are no issues requiring board attention at this time.
## Membership Data:
Apache HttpComponents was founded 2007-11-14 (17 years ago)
There are currently 20 committers and 9 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 Arturo Bernal on 2023-10-27.
- No new committers. Last addition was Arturo Bernal on 2023-06-20.
## Project Activity:
- Development on master is 5.6 for Client and 5.5 for Core
## Community Health:
- Overall the project remains active. Issues and dicussions are
resolved in time.
## Releases:
- HttpCore 5.3.5 GA: 2025-09-02
- HttpClient 5.5 GA: 2025-05-26
-----------------------------------------
Attachment AM: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hudi was founded 2020-05-19 (5 years ago)
There are currently 40 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- Yue Zhang was added to the PMC on 2025-06-30
- No new committers. Last addition was Vova Kolmakov on 2024-09-13.
## Project Activity:
The community has been actively working on the Hudi core Java implementation
and the Hudi-rs native Rust implementation. Hudi 1.1 is targeted for release
around the end of September, with key code path refactoring to lay a solid
foundation for building new features. In parallel, the community is also
preparing Hudi 1.0.3 and 0.15.1 patch releases for bug fixes and stability
improvements. Hudi-rs 0.4.0 was released in July with new C++ APIs and full
MOR table read support.
## Community Health:
We continue to see steady growth in community engagement on GitHub, with
active participation in code contributions and discussions. The community has
voted on and approved the decision to enable GitHub Discussions; as a result,
both the Hudi and Hudi-rs GitHub projects have started syncing these
conversations to the dev mailing list. The community also voted to use GitHub
Issues instead of JIRA for issue tracking. To foster more active discussions,
the PMC changed the cadence of developer sync calls from monthly to weekly.
-----------------------------------------
Attachment AN: Report from the Apache Iceberg Project [Ryan Blue]
-----------------------------------------
Attachment AO: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for September 2025
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 August, there are 31 podlings in incubation. Podlings executed 7
releases during the month, and no IP clearances were completed.
Several new proposals were discussed. Three podlings, Teaclave, HeertzBeat
and Training, graduated to Top-Level Projects. One new podling entered
incubation, Auron (previously named Blaze), no podlings retired, and no IP
clearances were completed this month. No changes were made to IPMC
membership.
Only PonyMail failed to submit a report and will be asked again to report
next month. Given its repeated lapses, it may be time to revisit earlier
discussions about the project’s future, as past conversations have not
reached a clear consensus.
Several talks were given at Community Over Code Asia in the Incubator Track.
A discussion on the mailing list in August focused on graduations, with
Teaclave and DevLake both moving toward top-level status. A proposal was
raised for OpenOffice Cloud+AI. Discussions also covered mentor engagement,
including reminders about missing reports, handling inactive mentors, and
onboarding guidance for new mentors. Work continued on training resources,
and some cleanup of retired podlings.
Among the long-term podlings, both Toree and Livy appear to have stalled in
their progress toward graduation and have been contacted regarding their
progress. All other long-running podlings have either graduated or retired.
Note: OzHera did not have a mentor sign-off when submitted; they have been
contacted about this.
## Community
### New IPMC members:
- Huajie Wang
- Ed Espino
### People who left the IPMC:
- Sharan Foga
- Woonsan Ko
## New Podlings
- Auron
## Podlings that failed to report, expected next month
- PonyMail
## Graduations
- HertzBeat
- Teaclave
- Training
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
August:
- Cloudberry 2.0.0
- Fluss Shaded 1.0
- GraphAr 0.13.0
- Iggy 0.5.0
- Seata 2.5.0
- Polaris 1.0.1
- Wayang 1.1.0
## IP Clearance
- None
## Legal / Trademarks
N/A
## Infrastructure
N/A
## Table of Contents
[Auron](#auron)
[Baremaps](#baremaps)
[BifroMQ](#bifromq)
[Burr](#burr)
[GeaFlow](#geaflow)
[Iggy](#iggy)
[KIE](#kie)
[OpenServerless](#openserverless)
[Otava](#otava)
[OzHera](#ozhera)
[Polaris](#polaris)
[PouchDB](#pouchdb)
[Texera](#texera)
[Wayang](#wayang)
--------------------
## Auron
The Auron accelerator for big data engine (e.g., Spark, Flink) leverages
native vectorized execution to accelerate query processing. It combines the
power of the Apache DataFusion library and the scale of the distributed
computing framework.
Auron has been incubating since 2025-08-05.
### Three most important unfinished issues to address before graduating:
1. Finish the source code cleanup.
2. Publish the first Apache release.
3. Grow the community and attract more contributors and users
### 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?
One new committer joined the project.
### How has the project developed since the last report?
No
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
Sept. 1, 2025 - Fei Wang(turboFei)
### Have your mentors been helpful and responsive?
Yes, all the mentors are helpful and responsive on the project
bootstrap and community growth.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (auron) Becket Qin
Comments:
- [X] (auron) Calvin Kirs
Comments: Progressing well.
- [X] (auron) Hao Ding
Comments:
- [X] (auron) Nicholas Jiang
Comments:
### IPMC/Shepherd notes:
--------------------
## Baremaps
Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.
Baremaps has been incubating since 2022-10-10.
### Three most important unfinished issues to address before graduating:
1. Expanding the community
2. Making releases
3. Discussing the future of the project
### Are there any issues that the IPMC or ASF Board need to be aware of?
We recognize the need to further expand the community and strengthen
contributor retention. We aim to make progress on this in the coming
year.
If these challenges cannot be addressed, we will initiate a discussion on
the project’s future, including the possibility of retiring it from the
Apache Incubator. In that case, development may continue under a lighter
process within its original organization.
### How has the community developed since the last report?
The project activity slowed during the summer but is expected to resume
in the coming months.
### How has the project developed since the last report?
We have addressed security issues and introduced security guidelines.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-07
### When were the last committers or PPMC members elected?
In June 2024.
### Have your mentors been helpful and responsive?
Yes, Julian Hyde and Calvin Kirs remain responsive and provide support as
needed.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (baremaps) Bertrand Delacretaz
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
- [X] (baremaps) Julian Hyde
Comments:
- [X] (baremaps) Calvin Kirs
Comments: The community has shown very little activity.
- [ ] (baremaps) George Percivall
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
### IPMC/Shepherd notes:
--------------------
## BifroMQ
BifroMQ is a Java-based, high-performance, distributed MQTT broker with
native multi-tenancy support, designed for large-scale connections and
message delivery.
BifroMQ has been incubating since 2025-04-22.
### Three most important unfinished issues to address before graduating:
1. Complete the first incubator release.
2. Gain more public exposure and user base.
3. Attract more contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We received confirmation from Mark that the paperwork for the trademark
transfer has been submitted. The process is expected to take around six
months to complete.
### How has the community developed since the last report?
1. One contributor joined the community.
2. A press release was published via a company media channel to promote
Apache BifroMQ.
3. One of the largest smart home appliance companies adopted Apache
BifroMQ.
### How has the project developed since the last report?
1. Working toward a code freeze for the first incubator release (9 PRs
merged).
2. Fixed multiple issues identified in real production usage.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-25
### When were the last committers or PPMC members elected?
None since entering the incubator.
### Have your mentors been helpful and responsive?
Yes, we have received helpful guidance.
### Is the PPMC managing the podling's brand / trademarks?
The transfer of BifroMQ’s trademark is in progress.
### Signed-off-by:
- [ ] (bifromq) Christofer Dutz
Comments:
- [ ] (bifromq) Xiangdong Huang
Comments:
- [X] (bifromq) Calvin Kirs
Comments:
- [X] (bifromq) Penghui Li
Comments: Good progress on stabilizing the project and preparing for
the first release. Encouraging to see ongoing community growth.
- [ ] (bifromq) Sheng Wu
Comments:
### IPMC/Shepherd notes:
--------------------
## Burr
Burr is a lightweight in-process python framework that standardizes the
expression and execution of state machines as action-driven graphs, while
making graph execution easily observable. It is particularly suited for AI
agent workflows, simulations, and other dynamic systems, and comes with a
self-hostable observability UI that integrates with OpenTelemetry.
Burr has been incubating since 2025-05-24.
### Three most important unfinished issues to address before graduating:
1. Finish docs
2. Add licenses to all files
3. Make a release
### Are there any issues that the IPMC or ASF Board need to be aware of?
We're slow.
### How has the community developed since the last report?
New discord members.
### How has the project developed since the last report?
We have a user wanting to contribute a major UI feature.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
May
### Have your mentors been helpful and responsive?
We're just slow to get through all the red-tape to release.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (burr) Kevin Ratnasekera
Comments:
- [X] (burr) Ayush Saxena
Comments: Progressing slowly
- [X] (burr) PJ Fanning
Comments: This podling has member overlap with Hamilton and the focus
appears to be on Hamilton right now so Burr progress is slow
### 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. Release the first version.
2. Establish a well-defined community governance framework.
3. Enhance the diversity of community (attracting more committers,
contributors, and users).
4. Drive the community forward in accordance with the technial roadmap in
issues.
### 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. Several active users and contributors joined the community since the
last report.
2. Update the community governance.
[#586](https://github.com/apache/geaflow/pull/586)
3. Participated in open source activities such as GLCC and OSPP, and
assisted students with coding tasks.
4. TuGraph × AWS User Group Tech Meetup: LITAO LIN attended the event and
presented an introduction of Apache GeaFlow to the audience. The Meetup
attracted over 150 technical professionals and AI enthusiasts. [Meetup
introduction](https://mp.weixin.qq.com/s/CdMctsfFR8dDwnolgGcFTw) (in
chinese)
### How has the project developed since the last report?
1. Since the last report, 4 new features have been merged, including
support for asynchronous writing in Paimon, Paimon source, Hive source,
and MCP. Additionally, several bug fixes and improvements have been made.
2. All content for the GeaFlow website is now fully prepared, and we are
currently seeking support from the Apache Infra team to deploy the site.
We expect it to go live within the next month.
3. Prepare for the first release version.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release (IMPORTANT)
- [X] Update the community governance
- [ ] Update the doucments
- [ ] Community building
- [ ] Nearing graduation
- [ ] Others
### Date of last release:
We will launch the first version int the next one weeks.
### When were the last committers or PPMC members elected?
None since entering the incubator.
### 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
Comments:
- [X] (geaflow) xinwang
Comments:
- [ ] (geaflow) lzljs3620320
Comments:
- [ ] (geaflow) jmclean
Comments:
- [ ] (geaflow) paulk
Comments:
### IPMC/Shepherd notes:
--------------------
## Iggy
Iggy is a high-performance, ultra-low latency and large-scale persistent
message streaming platform written in Rust.
Iggy has been incubating since 2025-02-04.
### Three most important unfinished issues to address before graduating:
1. Continue expanding the community, release more versions under ASF
2. Expand connectors / external sinks ecosystem, Clustering
3. Add more documentation on iggy.apache.org as we add more features
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- Discord members count 470+, new contributors writing proposals
(discussions), submitting PRs for fixing issues, docs, enhancements.
- Github stars reached ~2.9K
- Crates downloads reached 157K+
- Presented Apache Iggy at the Rust Poland Meetup:
https://www.meetup.com/rust-poland-meetup/events/308832371
- Scheduled to present at ApacheCon in September
### How has the project developed since the last report?
Version 0.5.0 has been released
- Here is the release notes
https://github.com/apache/iggy/releases/tag/server-0.5.0
- Release Announcement thread
https://lists.apache.org/thread/tn5onstopj3pxh8vdo651jscsp4lfsgf
Dependencies & Build
- Upgraded Rust dependencies across the project
- Fixed Docker setup action and publishing workflow issues
SDKs: Enhancements & CI
- Java SDK: version updated, Nexus credentials managed via environment,
published to Apache Maven and SNAPSHOTs
- Node.js SDK: updated package metadata, proper typings for async
methods, packaging fixes
- Go SDK: added Go getting-started example and test script, implemented
Go publish workflow, integrated BDD tests (godog) across SDK changes, CI
workflows, BDD tests added for multiple SDKs, replaced Box with
ClientWrapper enum
- Python SDK: renamed from iggy_py to apache‑iggy, added support for
consumer groups, BDD tests and restructured test layout
- C# SDK: updated version header in .csproj, improved package metadata,
added CI workflow
- Fixed Rust SDK: resolved monotonic time bug
Connectors & Core Engine
- Various Connectors runtime enhancements
- Added state storage using local files
- Introduced FlatBuffers schema support
- Added PostgreSQL sink and source connectors
- Extended runtime with protobuf support and initial HTTP API
- Refactored socket handling to better support large messages; added
examples; improved singleConsumerStream logic
Server & Benchmarks
- Updated message header to include decrypted payload length and fixed
encrypted message index calculation
- Introduced Model Context Protocol (MCP) server
- Optimized benchmarking: parallelized report builder, updated platform
links, typo fixes
- Added Helm chart for Iggy server
Web UI & Documentation
- Improved message browsing in Web UI for a smoother experience
- Readme updates, grammar and wording improvements; added missing license
headers across modules
- Integrated with DeepWiki for additional documentation on Github
- Extended iggy-server --help documentation
Infrastructure, CI/CD, and Testing
- Established branch protection for io_uring runtime branch
- Removed OpenSSL dependency in favor of Rustls for TLS
- Consolidated server tests using test matrices; added segment cache
index variants to server‑restart tests; fixed restart index saving issues
- Workflow improvements: markdown linter, improved CI workflows,
publishing for bench and connectors, Docker and examples fixes
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [X] Other: Expanding ecosystem
### Date of last release:
2025-08-10
### When were the last committers or PPMC members elected?
February 2025, at the time of onboarding to Apache Incubator Program.
### Have your mentors been helpful and responsive?
Yes, mentors are helpful and in general responsive. Some of them might be
busy with other commitments. Maybe we could benefit from 1 or 2 new
mentors to increase the coverage.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here.
VP, Brand approved the project name.
### Signed-off-by:
- [X] (iggy) Hao Ding
Comments: Actively working project
- [ ] (iggy) Yonik Seeley
Comments:
- [X] (iggy) Zili Chen
Comments:
- [ ] (iggy) Hulk Lin
Comments:
### IPMC/Shepherd notes:
--------------------
## KIE
KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.
KIE has been incubating since 2023-01-13.
KIE REPORTED IN AUGUST. There has been no material change since the report
last month. Unsure why we are being asked to report each month.
### Three most important unfinished issues to address before graduating:
1. Continuing to build the community
2. Removing dependencies which do not comply (almost there)
3. Ensuring branding is correct
### Are there any issues that the IPMC or ASF Board need to be aware of?
No, we’re moving along well. Slowly, but still making progress.
### How has the community developed since the last report?
Last report last month, nothing has changed.
### How has the project developed since the last report?
Last report last month, nothing has changed.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-07-10
### When were the last committers or PPMC members elected?
Start of the year
### Have your mentors been helpful and responsive?
Nothing to the report. The mentors are doing well.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (kie) Brian Proffitt
Comments: Not much changed since last month's report, all set here.
- [ ] (kie) Claus Ibsen
Comments:
- [X] (kie) Andrea Cosentino
Comments: All looks good.
### IPMC/Shepherd notes:
--------------------
## OpenServerless
OpenServerless is an open source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an
unified developer experience with a plethora of services (SQL or noSQL
databases, key-value stores, object storage, LLMs services, function
schedulers) managed by the platform's core: the operator, along with tooling
(the CLI) to simplify (and interact with) deployments, integrated ide and
starter application and optimized runtimes integrated with the staters.
OpenServerless has been incubating since 2024-06-17.
### Three most important unfinished issues to address before graduating:
1. Community Building.
2. Consolidation and alignment of the documentation site project.
3. The verification of the requirements for the first release is still
underway: the project has undergone a series of changes based on community
requests.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- After completing the first course, a second course is being implemented
focusing on modern AI topics according to the serverless paradigm.
- Opened a Discord server with over 300 users.
- Updated the tutorial [OpenServerless
Tutorial](https://github.com/apache/openserverless-tutorial).
- We are trying to bring the product closer to the user: infact, based on
community requests, we have created a version of OpenServerless called
"mini", capable of running on desktop systems by scaling down the RAM and
CPU requirements, but preserving all the components for local development
(from the OpenWhisk controller to the vector database, streamer, runtimes,
database, etc.) and installable with one single command. Documented on
Apache OpenServerless website.
- Recently we published two articles about Apache OpenServerless on
[Opensource.net](https://opensource.net).
### How has the project developed since the last report?
- 24 issues closed since last update. There are about 30 open tasks,
divided between additional features (for which community support is
required), bug fixes and new features.
- We have spent several efforts in trying to simplify the setup and make
it easier and more understandable.
- We are aiming to refactor the operator, to make it modular.
- Another important challenge is to make OpenServerless task scripts
completely cross-platform as well.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None
### When were the last committers or PPMC members elected?
2024-08-22
### Have your mentors been helpful and responsive?
Yes, and we renew our thanks to all of them for their continued support
in developing this project, allowing us to meet the required standards.
### Is the PPMC managing the podling's brand / trademarks?
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved
### Signed-off-by:
- [ ] (openserverless) Bertrand Delacretaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [X] (openserverless) François Papon
Comments: Same comment as PJ Fanning, actual installation process is
with curl that is not possible with bit.ly. A solution needs to be
find.
- [ ] (openserverless) JB Onofré
Comments:
- [X] (openserverless) PJ Fanning
Comments: No official release yet and users are being encouraged to
download via a bit.ly link that loads the app from OpenServerless'
GitHub repo. I don't think that this should go on indefinitely.
### IPMC/Shepherd notes:
--------------------
## Otava
Apache Otava (incubating) performs statistical analysis of performance
test results stored in CSV files, PostgreSQL, BigQuery, or Graphite
database. It finds change-points and notifies about possible performance
regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the
environment.
* Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter. The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Upgrade to support the latest versions of Python, including upgrading
to
the latest signal-processing-algorithms library.
2. Do more releases, so that it is a routine, repeatable process.
3. Grow the community and ultimately vote to admit new committers and PPMC
members. Do more publicity around the releases and the project in general.
This is an item where we certainly hope to see new contributors.
### 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?
We've seen engagement in the mailing lists and/or PRs from four out of
five of the project's committers since the last report.
Three new contributors have reached out via the mailing list and/or
GitHub, showing interest in the project and starting work on open issues.
### How has the project developed since the last report?
* We have completed our first release.
* Updated our build system to use `uv` instead of `poetry`.
* Changed our configuration management for ease of use.
* Starting the work to migrate to modern python versions.
### How would you assess the podling's maturity?
* [ ] Initial setup
* [ ] Working towards first release
* [X] Community building
* [ ] Nearing graduation
* [ ] Other:
A self review based on https://s.apache.org/727vc
* Code 5/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
### Date of last release:
The last release was on July 17, 2025.
### When were the last committers or PPMC members elected?
The major contributors during the past 8 years were listed as PPMC members
in the project application phase. We have not elected any new members after
that.
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
Nothing is falling through the cracks.
### Is the PPMC managing the podling's brand / trademarks?
This isn't yet an issue, as the new name of the project is quite unknown
yet.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [ ] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
--------------------
## OzHera
OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such as
metric monitoring, trace tracking, logging, and alerting
OzHera has been incubating since 2024-07-11.
### Three most important unfinished issues to address before graduating:
1.Make more apache release.
2.Build and grow community.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
Improve the community website and prepare to deploy the online demo in
the new environment.
Develop more committers and contributors.
### How has the project developed since the last report?
1、Enhance intelligent link analysis capabilities.
2、Optimize trace data collection strategy and processing performance,
with an added degradation control switch.
3、Introduce intelligent log analysis functionality.
4、Optimize log collection across multiple dimensions, including
configuration management, distribution logic, and dedicated collection
thread pool.
5、Refactor the custom metric monitoring SDK.
6、Add business metrics support in the monitoring module.
### 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:
2025-03-26
### When were the last committers or PPMC members elected?
2025-01-13
### Have your mentors been helpful and responsive?
Yes, mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Not yet.
### Signed-off-by:
- [ ] (ozhera) Yu Xiao
Comments:
- [ ] (ozhera) Yu Li
Comments:
- [ ] (ozhera) Kevin Ratnasekera
Comments:
- [ ] (ozhera) Duo Zhang
Comments:
### IPMC/Shepherd notes:
--------------------
## Polaris
Polaris is a catalog for data lakes. It provides new levels of choice,
flexibility and control over data, with full enterprise security and Apache
Iceberg interoperability across a multitude of engines and infrastructure.
Polaris has been incubating since 2024-08-09.
### Three most important unfinished issues to address before graduating:
1. Review 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?
Regarding the user community:
* On Slack, we note an increase of 7% of the number of messages (with a
peak of 580 messages during last month). These Slack messages happen 77%
on public channels and 21% as direct messages (which is a good ratio). NB:
we are using the free plan for Slack, meaning that the messages retention is
90 days. It's interesting to note that we got messages from 21 threads
started by new Slack users.
* On GitHub Issues, we had 19 issues created by new users.
* On the dev mailing list, we had 196 messages in August, 278 messages in
July, and 311 messages in June.
Regarding the dev community:
* We had 46 Pull Requests from 13 new contributors
* Community meetings happened on 2025-06-12, 2025-06-26, 2025-07-24,
2025-08-28, all recorded and shared publicly (on the dev mailing list and
the website, see https://polaris.apache.org/community/meetings/)
We participated in events to promote Apache Polaris:
* Apache Beam Summit 25 New York City
* Apache Iceberg Meetup Paris June 25
* Snowflake Summit SF June 25
* Data and AI - Lakehouse MiniSummit SF June 25
### How has the project developed since the last report?
We released 1.0.0-incubating, which is an important milestone for the
podling:
* Binary distributions (.tgz/.zip) and Docker images
* Official Helm chart for Kubernetes
* Quarkus runtime for fast startup
* Policy store with built-in data TMS policies
* Rollback compaction on conflicts
* 3rd Party IdP integration
* Federation and generic table support (experimental)
We also released 1.0.1-incubating, mostly to fix an issue on the Helm
chart.
In order to faster ship fixes and new features, we agreed about a monthly
release cadence.
We are also discussing several proposals:
* Table Source
* Client/Authentication API
* Event API
* Async & Reliable Tasks
* Commit Deconfliction
* Row and Column Based Access Control
* S3 Remote Signing
* FGAC
* ...
### 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:
2025-08-16
### When were the last committers or PPMC members elected?
Last committers: Yun Zou elected on 2025-06-08
Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on
2025-03-25
### Have your mentors been helpful and responsive?
Yes, helpful in releases review mostly.
### Is the PPMC managing the podling's brand / trademarks?
Polaris PPMC is working with 3rd parties willing to use Polaris
brand/trademarks, according to
https://incubator.apache.org/guides/publicity.html and
https://incubator.apache.org/guides/branding.html.
### Signed-off-by:
- [ ] (polaris) Bertrand Delacretaz
Comments:
- [ ] (polaris) Holden Karau
Comments:
- [X] (polaris) Kent Yao
Comments: The community is very active in project developing,
delivering releases and community building.
- [X] (polaris) Ryan Blue
Comments: Good progress on the project. I think that the community is
getting more used to the Apache Way but still needs guidance. This is
based on uncertainty about when to use the private list and when to use
a vote (vs asking for further discussion).
- [X] (polaris) JB Onofre
Comments: I'm happy to see new contributors and people active in the
Polaris community. Also the podling did good progress on the releases
front.
### IPMC/Shepherd notes:
--------------------
## PouchDB
PouchDB is an open-source JavaScript database inspired by Apache CouchDB
that is designed to run well within the browser.
PouchDB has been incubating since 2025-04-15.
### Three most important unfinished issues to address before graduating:
1. Get the project up and running (no blockers, currently working on
crypto and import)
2. Follow the graduation progression, in particular make a new release
under the ASF Incubator.
3. Grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
No changes, still booting up.
### How has the project developed since the last report?
We started looking at crypto notice requirements and cleared up all
questions we had.
Next up is code import prep.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] 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?
All good.
### Is the PPMC managing the podling's brand / trademarks?
n/a
### Signed-off-by:
- [X] (pouchdb) PJ Fanning
Comments: Not much activity generally in the podling. Minimal mailing
list activity, source not yet imported to ASF git, no website.
- [X] (pouchdb) Jean-Baptiste Onofré
Comments: Podling is in "starting mode" for now.
### IPMC/Shepherd notes:
--------------------
## Texera
Texera is an open-source system to support collaborative data science, AI,
and ML using GUI-based workflows. Our vision is to develop a system to
support cloud platforms on which users can easily analyze data and use AI/ML
techniques provided as operators. Users with various backgrounds,
irrespective of whether they know coding or not, can collaborate on the same
project to construct a pipeline. Experienced users can use programming
languages such as Python, R, Java, and Scala to implement customized
computation logic. The platform allows users to pause the execution of a
workflow to investigate the operator states, and resume the execution at a
later time. The platform can be used by a research community to publish
valuable resources such as data sets, workflows, and ML models to share
their domain-specific knowledge and support reproducibility of scientific
research. The platform also allows users to elastically request computing
resources from public clouds for computationally-intensive tasks.
Texera has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Set up the Apache Texera webpage
[http://texera.apache.org/](http://texera.apache.org/).
Work is underway to consolidate user guides, developer setup
instructions, and governance policies.
We are analyzing the documentation structures of successful projects
like Apache Flink and Spark to
ensure an optimal user experience.
### 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. **August 06, 2025:** The repository has officially transferred to
Apache organization
2. **August 28, 2025:** We conducted our monthly group sync meeting with
the PPMC members, committers, and contributors.
### How has the project developed since the last report?
* Cloud Deployment: Investigated on AWS ECS for low cost deployment of
Texera.
* Preparing for NIH: Added option to allow owner to give download access
to public datasets.
* UI Enhancements:
* Added user's activeness to admin dashboard
* Displayed file upload speed and time
* Added dashboard tab for computing units
* Docs: All design decisions are documented in `issues` tab in Github.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release: 2025-04-04 (not an ASF release)
### When were the last committers or PPMC members elected?
July 4 2025.
### Have your mentors been helpful and responsive?
Yes, our mentors were highly responsive and joined our meetings. They
also actively worked on our JIRA tickets.
### Signed-off-by:
- [X] (texera) PJ Fanning
Comments: Next priority must be to get the web site working
- [X] (texera) Ian Maxon
Comments: It's great to see the code donation cleared up. Looking
forward to an incubating release in the near future!
### IPMC/Shepherd notes:
--------------------
## Wayang
Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.
Wayang has been incubating since 2020-12-16.
### Three most important unfinished issues to address before graduating:
1. We are prepared for, and ready to initiate discussion for graduation.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues.
### How has the community developed since the last report?
Stagnated.
### How has the project developed since the last report?
We've completed a release with various new functionality, current
progress has focus on bug fixes related to that 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-07-24
### When were the last committers or PPMC members elected?
2025-02-05
### Have your mentors been helpful and responsive?
Yes, mentors have been helpful. No issues to be addressed.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (wayang) Christofer Dutz
Comments:
- [ ] (wayang) Lars George
Comments:
- [ ] (wayang) Bernd Fondermann
Comments:
- [X] (wayang) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AP: Report from the Apache IoTDB Project [Xiangdong Huang]
## Description:
The mission of Apache IoTDB is the creation and maintenance of software
related to an IoT native database with high performance for data management
and analysis.
## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: no.
## Membership Data:
Apache IoTDB was founded 2020-09-16 (4 years ago)
There are currently 78 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- Yongzao Dan was added to the PMC on 2025-08-18
- Zhijia Cao was added as committer on 2025-07-29
- Junzhi Peng was added as committer on 2025-07-06
- Yuchen Ding was added as committer on 2025-07-07
## Project Activity:
We have just released versions 2.0.4 and 2.0.5, which significantly enhance
IoTDB's query and analysis capabilities:
- Building on UDSF and UDAF, we have expanded support to include UDTF; added
support for window functions and RPR in standard SQL, providing users with
convenient built-in syntax to explore trends between different rows; and
extended support for ASOF JOIN (this syntax originally comes from the Python
pandas library).
- Users can create table-model views based on tree-model data, enabling
existing tree-model users to perform analytical queries using standard SQL
for table models without data migration.
- The AINode comes with built-in support for the Sundial time-series large
model[1].
## Community Health:
Overall community health is good.
- In July, we held the IoTDB 2.0 launch event, where we introduced numerous
new features of IoTDB 2.0 to everyone.
- Since some of the features developed in the previous quarter are defined in
standard SQL, there were established specifications to reference, and thus
not many conflicting points required discussion on the mailing list.
Naturally, any existing discussions took place directly during the PR
reviews on GitHub, so dev@iotdb.apache.org had a 43% decrease in traffic in
the past quarter (103 emails compared to 178). We are also guiding community
contributors to send the function definitions of these non-controversial
development items to the mailing list, so that interested members of the
community can participate together.
- Contributions from Timecho are now summarized weekly and sent to the mailing
list.
[1] Liu, Yong, et al. "Sundial: A family of highly capable time series
foundation models." arXiv preprint arXiv:2502.00816 (2025).
-----------------------------------------
Attachment AQ: Report from the Apache Jackrabbit Project [Marcel Reutegger]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class websites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications, and it
is not a reference implementation.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Jackrabbit was founded 2006-03-15 (19 years ago).
There are currently 60 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is 1:1, because all committers automatically
become PMC members.
Community changes, past quarter:
- Alejandro Moratinos was added to the PMC on 2025-08-27
- Alejandro Moratinos was added as committer on 2025-08-27
## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.
The team is further reducing usage of Google's Guava library and
Jackrabbit Oak is now using Java features or Apache Commons alternatives
where possible. The long term goal is to remove the dependency on Guava.
Jackrabbit Oak release 1.84.0 updated the MongoDB driver from 3.12.14 to
5.2.1. This update required many code changes because the new MongoDB
driver version is not backward compatible. The new driver version ensures
compatibility with future MongoDB server versions and officially supports
Java 21.
Early July a security vulnerability (CVE-2025-53689) was reported. The
team released fixes for multiple versions of Jackrabbit on July 14th.
## Community Health:
The project is generally healthy with a continuous stream of traffic
mostly on JIRA issues and GitHub pull requests reflecting activity of
the respective component.
Commit activity is moderate, mirroring the activity on the
JIRA issues and the desire of the individual contributors to bring
features and improvements in for the next Jackrabbit Oak release.
## Releases:
- jackrabbit-oak-1.82.0 was released on 2025-07-03
- jackrabbit-2.20.17 was released on 2025-07-14
- jackrabbit-2.22.1 was released on 2025-07-14
- jackrabbit-2.23.2-beta was released on 2025-07-14
- jackrabbit-filevault-4.0.0 was released on 2025-07-31
- jackrabbit-2.22.2 was released on 2025-08-01
- jackrabbit-oak-1.84.0 was released on 2025-08-14
## JIRA activity:
- 187 JIRA tickets created in the last 3 months
- 158 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AS: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Project Status:
Current project status: Active
Issues for the board: None
## Membership Data:
Apache Juneau was founded 2017-10-17 (8 years ago)
There are currently 14 committers and 13 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 Gary D. Gregory on 2023-04-02.
- No new committers. Last addition was Aditya Kanthale on 2024-10-22.
## Project Activity:
8.1.4 was released on 2024-11-15.
9.0.0 was released on 2023-02-27.
Currently working on modernizing the codebase to Java 17 and JUnit 5.
## Community Health:
Community activity is low but active. The code has been mostly in maintenance
mode, but work is now being done to modernize the code to use newer Java
features.
-----------------------------------------
Attachment AT: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
The mission of the Apache Karaf project is the creation and maintenance of
open-source software related to a generic platform providing higher level
features and services specifically designed for creating OSGi-based servers for
distribution at no charge to the public.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Karaf was founded 2010-06-16 (14 years ago)
There are currently 32 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Robert Varga on 2023-10-31.
## Project Activity:
Apache Karaf 4.4.8 has been released, including a lot of fixes, dependency
updates and improvements.
We already plan 4.4.9 fixing a couple of minor issues found in 4.4.8.
Apache Karaf 4.5.0 will be a new maintenance branch, with updated versions and
fixes.
Apache Karaf Cellar 4.4.8 release is currently on vote, fully supporting Karaf
4.4.x. A new Karaf Decanter release is also in preparation (not yet in vote).
## Community Health:
Following the previous report, we polished the Karaf runtime future plan:
* Still maintaining 4.4.x branch
* Latest JDK support on the 4.5.x series with best effort on introducing new
features (flat features resolver, new Karaf services, ...)
* Main will move forward with semver (4.6.x, 4.7.x, ...)
* We will have a separate target for 5.0.0 (optionally leveraging Minho)
-----------------------------------------
Attachment AU: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters
## Project Status:
Current project status: Apache Knox is an Ongoing project with a rather mature
feature set. Activity is low to moderate. We have an active VOTE thread for the
2.1.0 release with many improvements, bug fixes and dependency upgrades.
Issues for the board: None at this time.
## Membership Data:
Apache Knox was founded 2014-02-18 (12 years ago)
There are currently 24 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marton Balázs on 2022-11-27.
- No new committers. Last addition was Marton Balázs on 2022-11-28.
## Project Activity:
The Knox community has been working on a 2.1.0 release and has an active VOTE
thread going for a second release candidate. We have been working to move our
documentation into the github pages for the project to keep the docs with the
source and simplify updates and maintenance. We have added many improvements,
bug fixes and security related dependency upgrades.
We will also be spinning up a 3.0.0 release to drop support for Java 8 and move
onto 17+.
## Community Health:
dev@knox.apache.org had a 3% decrease in traffic in the past quarter
(638 emails compared to 656)
user@knox.apache.org had a 38% decrease in traffic in the past quarter
(5 emails compared to 8)
30 JIRA tickets opened and 35 closed in the past quarter.
These metrics represent the mature but moderately active project status. With
numbers generally stable across the compared quarters. Vacation times likely
are reflected in the slight decrease in activity.
We are tracking a couple contributors for committership and will likely move
forward with invitations after this 2.1.0 release.
-----------------------------------------
Attachment AV: Report from the Apache Kvrocks Project [Mingyang Liu]
-----------------------------------------
Attachment AW: Report from the Apache Kyuubi Project [Kent Yao]
## Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kyuubi was founded 2022-12-21 (3 years ago)
There are currently 29 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Binjie Yang on 2024-07-05.
- No new committers. Last addition was He Zhao on 2025-01-02.
- The PMC hass submitted the req of the PMC Chair change.
## Project Activity:
- We released Kyuubi Shaded 0.6.0 on 2025 Jul 24.
## Community Health:
The overall health of the community is good. We've noticed a lot of recent
interest in AuthZ and the Lineage plugin, and committers are also actively
reviewing PRs.
-----------------------------------------
Attachment AX: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AY: Report from the Apache Linkis Project [Shuai Di]
## Description:
The mission of Apache Linkis is to build a distributed computation middleware to facilitate connection,
governance, extensibility and orchestration between the upper applications and the
underlying data engines.
## Project Status:
Current project status: Ongoing.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Linkis was founded 2022-12-21 (Two years ago)
There are currently 38 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC. Last addition was Jie Cheng on 2024-01-28.
- No new committers. Last addition was king hao on 2024-12-04.
## Project Activity:
The Apache Linkis version 1.8.0 is under development and is expected
to be released in September 2025. Mainly includes the following features:
- Pre - task diagnosis and support for bad job interception,
as well as post - task diagnosis reports.
- Data source display support for Ranger.
- Support for setting priorities for Linkis tasks.
- Linkis supports Azure object storage.
- Data source management supports both Oracle and PostgreSQL
- Token expiration policy optimization
- Add UDF log query to task details
- Support azure object storage
- OAuth2 authentication support
## Community Health:
Overall community health is good.
- 14 PRs closed on GitHub, past quarter.
- 11 issues closed on GitHub, past quarter.
-----------------------------------------
Attachment AZ: Report from the Apache Lucene Project [Dawid Weiss]
## Description:
The mission of Lucene is the creation and maintenance of software related to
Search engine library
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Lucene was founded 2005-01-19 (21 years ago)
There are currently 106 committers and 70 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Vigya Sharma was added to the PMC on 2025-08-02
- Ge Song was added as committer on 2025-08-11
- Pan Guixin was added as committer on 2025-07-19
- Simon Cooper was added as committer on 2025-06-20
## Project Activity:
The project is in good shape, with stable activity in all areas
(discussions on the mailing list, github pull requests,
member community invitations, commits).
In the period between 2025-06-10 and 2025-09-01, there were 257
commits to the main branch, 94 issues filed (48 resolved), 280
pull requests opened (and 236 closed).
Lucene had two releases in the reporting period (10.2.2 and 9.12.2),
with another release already scheduled for September (10.3).
## Community Health:
Three new committers have been added to the project (Ge Song,
Pan Guixin and Simon Cooper). One committer has agreed to join the
PMC (Vigya Sharma). There is an ongoing discussion to invite two
more people to become project members.
-----------------------------------------
Attachment BA: Report from the Apache Lucene.Net Project [Shad Storhaug]
## Description:
The mission of Lucene.Net is the creation and maintenance of software related
to Search engine library targeted at .NET runtime users.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Lucene.Net was founded 2012-08-14 (13 years ago) There are currently 16
committers and 14 PMC members in this project. The Committer-to-PMC ratio is
8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ron Clabo on 2022-03-02.
- No new committers. Last addition was Ron Clabo on 2021-06-02.
Update: A vote is underway to add one new committer and one new PMC member as of
2025-09-08.
## Project Activity:
Apache Lucene.Net delivered the latest 4.8.0-beta00017 release on 2024-10-29.
Activity continues towards a final 4.8.0-beta00018 release, and activity has
increased since the last report. We are still focusing on completing work on
ICU4N and upgrading J2N to support System.Memory types to allow for more
efficient memory management. Lucene.Net is undergoing several breaking API
changes to stabilize the API for for the 4.8.0-beta00018 release. A project
for Google Summer of Code to provide packages with deeper integration with
.NET dependency injection APIs recently concluded, and is in the process of
being merged into a new lucenenet-extensions repo. We are also working on a
set of code analysis tools and code fixes for automating project-specific
code issues and formatting to automate managing code consistency across the
codebase and automation to release them with minimal manual effort. GitHub
Discussions has been enabled on our repository as an alternative to using
mailing lists to share ideas.
## Community Health:
- dev@lucenenet.apache.org had a 1% increase in traffic in the past quarter
(179 emails compared to 177)
- NOTE: The prior report mentioned a 91% decrease in traffic (19 vs 198
emails). This was significantly due to Google Summer of Code activity (the
main focus the past couple months) happening off-mailing-list via Slack
and PRs. Now that that has concluded, our mailing list activity has
returned to normal (179 vs 177). This discrepancy is also partially due to
the board reports not perfectly aligning with calendar quarters.
- 13 commits in the past quarter
- 4 code contributors in the past quarter
- 15 PRs opened on GitHub, past quarter
- 14 PRs closed on GitHub, past quarter
- 8 issues opened on GitHub, past quarter
- 9 issues closed on GitHub, past quarter
-----------------------------------------
Attachment BB: Report from the Apache Mynewt Project [Szymon Janc]
## Description:
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Mynewt was founded 2017-06-21 (8 years ago)
There are currently 37 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Michał Górecki on 2024-06-27.
## Project Activity:
Work is ongoing in several areas, mainly improvements in BSP and MCU support
(eg. Nordic nRF54H20), as well as some core subsystems work (LVGL, shell,
logging etc).
Continued work on Nordic nRF54L15 support and Bluetooth 6.0 features
(eg Channel Sounding). Continued work on LE Audio (Broadcast Sink).
There is also ongoing work on fixing NimBLE bugs that are affecting Bluetooth
Qualification (both host and controller).
Various bugfixes in preparation for next release. Project is also working
on adding more automated tests on real hardware to reduce regressions and
manual testing for releases.
## Community Health:
Core developers are active on regular basis. Most work is Bluetooth related.
New contributors showing up.
-----------------------------------------
Attachment BC: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environment, tooling platform, and application framework
## Project Status:
Current project status: Ongoing with moderate to high activity
Issues for the board: None
## Membership Data:
Apache NetBeans was founded 2019-04-17 (6 years ago)
There are currently 82 committers and 65 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2022-05-01.
- No new committers. Last addition was Tomas Hurka on 2023-05-24.
## Project Activity:
VSNetBeans 27.0.1 was released on 2025-09-04.
Apache NetBeans 27 was released on 2025-08-21.
HTMLJAVAAPI-1.8.2 was released on 2025-06-27.
## Community Health:
- Latest release shows 27 contributors, including two new ones:
https://github.com/apache/netbeans/releases/tag/27
- We've been investigating expanding the PMC and the list of committers and
are working on identifying the right people, in general the community is
stable but not growing significantly
- users@netbeans.apache.org had a 15% increase in traffic in the past quarter
(155 emails compared to 134)
- dev@netbeans.apache.org had a 54% decrease in traffic in the past quarter
(102 emails compared to 218):
-----------------------------------------
Attachment BD: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (19 years ago)
There are currently 60 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Sebastian Tschikin on 2024-09-18.
- No new committers. Last addition was Ioan Eugen Stan on 2024-09-23.
## Project Activity:
- Apache OFBiz 24.09.02 was released on 2025-08-04.
- As part of this release, we fixed and disclosed a new security
vulnerability: CVE-2025-54466.
- Trademarks: There are no trademark-related concerns at this time.
## Community Health:
The last quarter has been slightly quieter than usual, likely due to the
summer season. However, the community remains active, with ongoing discussions
on our mailing lists covering both technical topics and feature-related
questions. The project has also received various non code related
contributions in documentation, which continue to improve the
accessibility of our resources. There's currently an open thread in the PMC
mailing list about potential new candidates for the PMC and committer roles,
as it has been some time since our last additions.
-----------------------------------------
Attachment BE: Report from the Apache Olingo Project [Michael Bolz]
-----------------------------------------
Attachment BF: Report from the Apache OpenDAL Project [Hao Ding]
## Description:
OpenDAL is an Open Data Access Layer that enables seamless interaction with
diverse storage services. Its development is guided by the vision “One Layer,
All Storage” and the following principles:
- Open Community
- Solid Foundation
- Fast Access
- Object Storage First
- Extensible Architecture
## Project Status:
Current project status: Ongoing Issues for the board: None
## Membership Data:
Apache OpenDAL was founded 2024-01-17 (a year ago) There are currently 34
committers and 19 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:5.
Community changes, past quarter:
- Kingsword was added as committer on 2025-07-31
## Project Activity:
- v0.54.0 was released on 2025-07-17
- v0.54.1 is ongoing.
## Community Health:
### Are there any risks to the sustainability of the project?
OpenDAL remains in excellent health. The core crate has nearly 1000 dependents
on github and is used in production by multiple database systems (Databend,
GreptimeDB, RisingWave) and tools
(e.g., sccache, Vector). Development velocity is steady, with one PRs merged
daily.
The OpenDAL PMC has decided to accept reqsign as a sub-project. The IP
clearance process has been completed, and the code has been imported. The
OpenDAL PMC is now working on building the first ASF release for
opendal-reqsign.
### Is the PMC capable of responding to security issues and
performing releases if needed?
Yes. The PMC has repeatedly demonstrated the ability to quickly release fixes
and monthly tagged versions. Releases are made in a timely manner and
dependency hygiene is maintained actively.
### Does the PMC need anything from the Foundation to improve on
contributing to our mission of delivering software for the public good?
No requests at this time.
-----------------------------------------
Attachment BG: Report from the Apache OpenNLP Project [Jeffrey T. Zemerick]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache OpenNLP was founded 2012-02-14 (14 years ago)
There are currently 26 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Atita Arora was added to the PMC on 2025-07-19
- Nishant Shrivastava was added as committer on 2025-07-29
## Project Activity:
The project had a 2.5.5 release and 1.3 models release. OpenNLP will be
represented by at least two talks at Community over Code NA.
## Community Health:
Since the last report, the project added 1 new committer and 1 new PMC member.
The project is healthy having had recent releases and contributions. Mailing
list traffic remains around the usual volume.
-----------------------------------------
Attachment BH: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR), JSR-365 (CDI-2.0) and
Jakarta CDI (CDI-4.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Last quarter was really silent. We now got to work on doing a
JakartaEE release of OpenWebBeans Meecrowave.
We'll probably also do an OWB maintenance release with dependency
and TCK upgrades soonish.
## PMC changes:
- Currently 13 PMC members, 20 committers
- Last PMC addition was Reinhard Sandtner on 2017-10-09.
- Last committer addition was John D. Ament on 2017-10-09.
## Recent Releases
- 2.0.28 was released on 2025-05-19
- 4.0.3 was released on 2024-12-14
- 4.0.2 was released on 2024-02-14.
-----------------------------------------
Attachment BI: Report from the Apache Ozone Project [Sammi Chen]
## Description
Apache Ozone is a scalable, redundant, and distributed object and file
store,
designed to scale to billions of objects/files and run on clusters of
thousands
of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop
Compatible File System implementation.
## Issues
None.
## Membership Data
- Apache Ozone was founded 2020-10-21.
- There are currently 84 committers and 42 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
- In the past quarter,
Swaminathan Balachandran was added to the PMC on 2025-08-20
Chung-En Lee was added to the PMC on 2025-07-14
Chu Cheng Li was added as committer on 2025-05-24
## Project Activity
- Container reconciliation(HDDS-10239) development was finished and merged
from feature branch to master branch.
- Container and volume scanners phase II(HDDS-8387), to improve container
and volume scanner, continuous.
- Improvements for large scale deletion(HDDS-11506) are finished.
- Ozone Snapshot Garbage Collection Issues(HDDS-12558), to improve the
efficiency and reliability of snapshot garbage collection and fix bugs, is
finished.
- Ozone Snapshot Phase 3(HDDS-12940), scale up snapshot sperations, is
going on.
- Disk space utilization management improvements(HDDS-12564) continuous, to
prevent disk space from being fully occupied.
- Ozone S3 gateway Phase 4(HDDS-12716), to improve the S3 compatibility,
enrich the Ozone S3 document, and fix bugs, is going on.
- Storage Capacity Distribution(HDDS-13177), an effort to show the storage
wise and namespace wise data distribution on Recon, is under development.
- Disk Balancer feature(HDDS-5713) development is close to finishing,
merging back to master branch is under vote.
- S3 Object LifeCycle Management feature(HDDS-8342) development is kicked
off.
- Support listener OM(HDDS-11523) is under development.
- Continuous Ozone document improvements, with the popular AI tools' help,
new/existing documents are added and improved.
- Clean up dependencies(HDDS-11276), fix the problems reported by "mvn
dependency:analyze", and finish.
- Ozone 2.0.0 release promotion
- Press Release:
https://finance.yahoo.com/news/apache-software-foundation-announces-apache-160000761.html
- Apache Blog:
https://news.apache.org/foundation/entry/the-apache-software-foundation-announces-apache-ozone-2-0-0
- ASF X: https://x.com/TheASF/status/1957835925448167746
- ASF LinkedIn:
https://www.linkedin.com/posts/the-apache-software-foundation_opensource-activity-7363602499347357696-_Uo8
- Apache CoC Asia 2025 Talks (https://ozone.apache.org/events/)
- Apache Ozone: Balance Data Through Disk Balancer.
- Apache Ozone Best Practices at Shopee.
- Ozone blog, contributed by contributors from DiDi.
https://ozone.apache.org/blogs/.
- 2.1.0, 2.0.1 and 1.4.2 releases were kicked off and under discussion.
## Releases Data
- 1.0.0 was released on 2020-09-02.
- 1.1.0 was released on 2021-04-20.
- 1.2.0 was released on 2021-11-17.
- 1.2.1 was released on 2021-12-22.
- 1.3.0 was released on 2022-12-18.
- 1.4.0 was released on 2024-01-19.
- 1.4.1 was released on 2024-11-24.
- 2.0.0 was released on 2025-04-30.
## Community Health
Last board report was sent on 13th May 2025. Since last report,
- 32 code contributors who have commits in the past quarter (-9% change)
- dev@ozone.apache.org had 68 emails in the past quarter (-32% change)
- 495 PRs opened on GitHub, past quarter (-32% change)
- 461 PRs closed on GitHub, past quarter (-27% change)
- 397 commits in the past quarter (-17% change)
Note: The commit & PR count excludes the ones from user "app/dependabot",
who has many commits for dependency jar version upgrade.
-----------------------------------------
Attachment BJ: Report from the Apache Paimon Project [Jingsong Lee]
## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Paimon was founded 2024-03-20 (a year ago)
There are currently 23 committers and 14 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 Junhao Ye on 2025-02-25.
- Jerry Jing was added as committer on 2025-08-01
- Yunfeng Zhou was added as committer on 2025-06-24
## Project Activity:
Software development activity:
- We released the release 1.2.0 on 2025-07-16.
- We developed PyPaimon pure Python version without the need of a JVM.
- We developed Row Tracking feature to align with Apache Iceberg and Delta.
## Community Health:
- dev mail list had a 42% increase (70 emails compared to 49).
- We guided some discussions from GitHub to the dev mailing list.
- user email list had a 163% increase (29 emails compared to 11).
- technical questions in user email list, and promptly responded.
-----------------------------------------
Attachment BK: Report from the Apache Pekko Project [PJ Fanning]
## Description:
The mission of Apache Pekko is the creation and maintenance of software related
to a toolkit and an ecosystem for building highly concurrent, distributed,
reactive and resilient applications for Java and Scala
## Project Status:
Current project status:
Steady set of releases. Issues and Discussions are engaged with.
The active community remains small.
Issues for the board: Nothing of note.
## Membership Data:
Apache Pekko was founded 2024-03-20 (a year ago)
There are currently 28 committers and 19 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 JingZhang Chen on 2024-05-29.
- No new committers. Last addition was Domantas Petrauskas on 2024-12-19.
## Project Activity:
Pekko 1.2.0 was just released. Work starting on 2.0.0.
Signs are good that Pekko remains reasonably popular in the dev community.
## Community Health:
We are seeing more cases where active community members reduce their
participation than of new community members increasing their participation.
Situation is ok but the project is at risk of participation levels dropping
to unsustainable levels.
-----------------------------------------
Attachment BL: Report from the Apache Pig Project [Koji Noguchi]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It provides
a high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs.
## Project Status:
Current project status: Dormant
## Membership Data:
Apache Pig was founded 2010-09-21 (15 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 Koji Noguchi on 2016-08-04.
- No new committers. Last addition was Nándor Kollár on 2018-09-06.
## Project Activity:
After starting the vote for 0.18rc0, Rohini found a regression bug
https://issues.apache.org/jira/browse/PIG-5474 and stopped the vote. Patch
was uploaded, reviewed and committed this week. Started a new vote for rc1.
## Community Health:
Overall activity is low as the project is mostly stable. Contributions are
mainly bug fixes and updating dependencies.
-----------------------------------------
Attachment BM: Report from the Apache Pinot Project [Kishore G]
-----------------------------------------
Attachment BN: 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 low activity
Issues for the board: None
## Membership Data:
Apache PLC4X was founded 2019-04-16 (6 years ago)
There are currently 22 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Iñigo Angulo Otegi was added to the PMC on 2025-06-19
- Unai Lería Fortea was added as committer on 2025-06-11
## Project Activity:
- The S7-light driver has been added to the set of available drivers. Work is
also being done to improve the stability and reliability of the S7 and
Modbus drivers.
- The main Plc4x project 0.13.1
- The Plc4x-extras project 0.13.0 was released on 02-09-2025
## 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 development list shows a decrease of 34% in traffic in the past quarter
(96 emails compared to 223).
- 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.
- The biggest drop in making list activity is due to us redirecting pr emails
away from dev (which mostly contained dependabot emails)
- On professional social networks, specifically LinkedIn, there is an increase
in interest in the project, currently having 601 followers, which is an
increase of 5,25%
- The team decided to abandon Java 11 as the minimum version, and it is now
officially supported starting with Java 21.
-----------------------------------------
Attachment BO: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
-----------------------------------------
Attachment BP: Report from the Apache Portals Project [Neil Griffin]
## Description:
The mission of Portals is the creation and maintenance of software related to
Portal technology
## Project Status:
Current project status: The Apache Portals PMC has voted in favor of
the following:
1) Retire the Apache Pluto sub-project and move it to the attic
2) Retire the Apache Portals parent project and move it to the attic
3) Dissolve the Apache Portals PMC
See: https://lists.apache.org/thread/lyzjhj5nd373hn0zmmt3jpkwk1879612
Issues for the board: Please take the necessary steps to decommission the
project and PMC. Thank you for your help and support.
## Membership Data:
Apache Portals was founded 2004-02-17 (22 years ago)
There are currently 40 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Neil Griffin on 2017-02-11.
- No new committers. Last addition was Ahmed on 2016-08-06.
## Project Activity:
No activity on the project aside from the vote taken by the PMC.
## Community Health:
No activity in the community, even though an email was sent to the
dev list, asking for community input.
-----------------------------------------
Attachment BQ: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
## Project Status:
- There are no issues requiring board attention at this time.
## Project Activity:
- 4.1.0 was released on September 8th 2025
- 4.0.6 was released on July 31st 2025
- 3.3.8 was released on July 31st 2025
- 3.0.13 was released on July 31st 2025
- Pulsar C++ releases:
- 3.7.2 on July 6th 2025
- Pulsar Go releases:
- 0.16.0 on August 4th 2025
- Pulsar Python releases:
- 3.8.0 on July 18th 2025
- Pulsar NodeJS releases:
- 1.14.0 on July 1st 2025
- Pulsar reactive client:
- 0.7.0 was released on June 13th 2025
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-427: Align pulsar-admin Default for Mark-Delete Rate with Broker
Configuration
PIP-428: Change TopicPoliciesService interface to fix consistency issues
PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload
Buffer Parsing
PIP-430: Pulsar Broker Cache Improvements: Refactoring Eviction and Adding a
New Cache Strategy Based on Expected Read Count
PIP-431: Add Creation and Last Publish Timestamps to Topic Stats
PIP-432: Add isEncrypted field to EncryptionContext
PIP-433: Optimize the conflicts of the replication and automatic creation
mechanisms, including the automatic creation of topics and schemas
PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to
pulsar conf and pause receive requests when channel is unwritable
PIP-435: Add startTimestamp and endTimestamp for consuming messages in
client cli
PIP-436: Add decryptFailListener to Consumer
PIP-437: Granular and Fixed-Delay Policies for Message Delivery
PIP-438: add namespace topics limit metric
PIP-439: Adding Transaction Support to Pulsar Functions Through Managed
Transaction Wrapping
PIP-440: WaitForExclusive priority queueing
PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data
PIP-442: Add memory limits for CommandGetTopicsOfNamespace and
CommandWatchTopicList on Broker and Proxy
- Pulsar has reached 699 contributors on the main Github repo
(It was 687 contributors in June 2025)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (7 years ago)
There are currently 85 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Mingze Han was added as committer on 2025-07-05
- No new PMC members added this quarter
## Community Health:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper, more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 52% decrease in traffic in the past quarter (12 emails compared to 25)
- dev@pulsar.apache.org:
- 22% decrease in traffic in the past quarter (349 emails compared to 286)
## Slack activity:
- 10767 Members (10679 in June 2025)
- 404 Active montly users (275 in June 2025)
## GitHub activity:
- 658 commits in the past quarter (-17% decrease)
- 67 code contributors in the past quarter (-15% change)
- 244 PRs opened on GitHub, past quarter (-32% change)
- 221 PRs closed on GitHub, past quarter (-40% change)
- 109 issues opened on GitHub, past quarter (-36% change)
- 63 issues closed on GitHub, past quarter (-42% change)
-----------------------------------------
Attachment BR: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment BS: Report from the Apache Royale Project [Yishay Weiss]
-----------------------------------------
Attachment BT: Report from the Apache SeaTunnel Project [Jun Gao]
-----------------------------------------
Attachment BU: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
## Description:
The mission of Apache ServiceMix project is to create and maintain a flexible,
open-source integration container, powered by OSGi, that unifies the features
and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful
runtime platform you can use to build your own integration solutions.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (17 years ago)
There are currently 50 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.
## Project Activity:
We released ServiceMix Bundles 2025.07.
We already preparing new ServiceMix Bundles release as asked by the community.
## Community Health:
The project is now almost dormant:
- we do ServiceMix Bundles release on community demand (as it's still
heavily used)
- dependency projects (karaf, camel-karaf, ...) started to use wrap
protocol instead of ServiceMix Bundles (still ongoing)
- The Karaf integration distribution will cover most of the ServiceMix use cases
A roll call will be certainly performed soon to discuss the next step
for the project.
We plan to encourage projects to consider alternatives to ServiceMix
Bundles, either using Pax URL or Karaf URL service (coming).
-----------------------------------------
Attachment BV: Report from the Apache Shiro Project [Lenny Primak]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: None at this time
## Membership Data:
Apache Shiro was founded 2010-09-21 (15 years ago)
There are currently 14 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Lenny Primak on 2022-11-01.
## Project Activity:
The Shiro team is in the planning stages for 3.0 which aims to cut
some tech debt and help move the project forward (and by dropping
deprecated functionality). New functionality and fixes are still
accepted in 2.x, 1.x is security fix only.
## Last Release was:
- 2.0.5: 2025-07-01
## Community Health:
Mailing list traffic is low.
We are planning to open up GitHub Discussions this year.
-----------------------------------------
Attachment BW: 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.
The comment from last report about new committers is noted and new
committers will be nominated.
## Project Activity:
The team has released SINGA 5.0.0 on 14 April 2024.
In the past quarter, the community is working on the following features/changes:
-- Add the implementations of the candidiasis disease application.
-- Add the implementations of the cardiovascular disease application.
-- Add the implementations of models for SINGA PEFT.
-- Add the implementations of tuners for SINGA PEFT.
-- Add the implementations for LORA.
-- Update the docs for the healthcare example datasets.
## Community Health:
According to the statistics, there are more commits in the Github, which shows
that the community is active in the development.
-----------------------------------------
Attachment BX: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Project Status:
Current project status: Ongoing.
Issues for the board: none.
## Membership Data:
Apache Sling was founded 2009-06-17 (16 years ago)
There are currently 52 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Julian Reschke on 2024-10-22.
- No new committers. Last addition was Sagar Miglani on 2025-03-24.
## Project Activity:
We released version 13 of our sample application, the Sling Starter, on
January 17th, 2025. Work is ongoing towards Sling Starter 14.
Most of the work for the Jakarta EE migration has been done and the released
modules will be included in the development version of the Sling Starter.
In the meantime individual modules are being developed and released,
with 30 releases for this reporting period.
## Community Health:
Community health is pretty good and contributions from various
individuals continue.
-----------------------------------------
Attachment BY: Report from the Apache SpamAssassin Project [Giovanni Bechis]
## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
## Project Status:
Project state: Ongoing with low to moderate activity
Apache SpamAssassin 4.0.2 has been released on 30 August 2025, primary focus
for development is now ongoing maintenance bug fixes to the latest release,
4.0.2.
## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (21 years ago)
There are currently 32 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2.5:1.
Community changes, past quarter:
- PMC members:
Last addition was Kent Oyer on 2024-11-09.
- No new committers. Last addition was Kent Oyer on 2024-03-29.
## Project Activity:
Last release was Apache SpamAssassin version 4.0.2 on 30 August 2025.
We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility.
## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.
-----------------------------------------
Attachment BZ: Report from the Apache Storm Project [Richard Zowalla]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Project Status:
Current project status: Ongoing (reactivated)
Issues for the board: none
## Membership Data:
Apache Storm was founded 2014-09-17 (11 years ago)
There are currently 48 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Purshotam Shah on 2025-05-21.
- No new committers. Last addition was Purshotam Shah on 2024-10-08.
## Project Activity:
Project activity has slowed in recent years, and Storm is currently in
maintenance mode. Nonetheless, we still receive occasional bug reports and
user questions, indicating that Storm continues to see active use which is an
encouraging sign.
Over the past quarter, we upgraded several third-party libraries to their
latest versions and plan to maintain our regular release cadence with steady
patch deliveries. In parallel, work continues to reduce Storm’s reliance on
external dependencies, though managing this technical debt remains an ongoing
challenge.
We also decided to drop Calcite support due to a lack of community engagement
and limited knowledge among active maintainers. This change did not raise
concerns, so it should be fine moving forward. The Storm UI remains an open
task, but it’s not considered critical at this point. On a positive note, we
successfully cut a release, and the necessary votes came in quickly.
Recent releases:
2.8.2 was released on 2025-07-26.
2.8.1 was released on 2025-06-03.
2.8.0 was released on 2025-01-24.
## Community Health:
Community engagement is currently healthy, but could benefit from new
contributors or users.
-----------------------------------------
Attachment CA: Report from the Apache StreamPark Project [Huajie Wang]
## Description:
Apache StreamPark™ is a streaming application development framework
and one-stop cloud-native real-time computing platform.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache StreamPark was founded on 2025-01-23 (8 months ago)
There are currently 8 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:3.
Community changes, past quarter:
- No new PMC committer. Last addition was Jie Cheng on 2024-08-10.
## Project Activity:
- We released StreamPark 2.1.6 on 2025-07-09
## Community Health:
The overall health of the community is good. We are currently planning
to release 2.1.7.
The PMC is working actively with the Apache Security team to process
the reported issues.
-----------------------------------------
Attachment CB: Report from the Apache Synapse Project [Isuru Udana]
-----------------------------------------
Attachment CC: Report from the Apache Teaclave Project [Zhaofeng Chen]
# Apache Teaclave Board Report - September 2025
## Description
Apache Teaclave provides SDKs for building memory-safe applications on Trusted
Execution Environments.
## Project Status
**Status:** New
Apache Teaclave graduated as a Top-Level Project on August 21,
2025. Since graduation, the community has completed the transition to TLP
infrastructure, including GitHub repositories, distribution servers, website
updates, and project documentation.
## Summary of Project Health and Status
Since graduation, Apache Teaclave has completed the transition from
incubation, updated all references to reflect TLP status, and is preparing its
first release as a TLP. The community remains active with steady development
and moderate mailing list discussions. Current focus is on completing the
v0.6.0 release and strengthening developer tooling for building applications
on TEEs.
## Issues for Board Attention
There are no Board-level issues at this time.
## Recent Releases
- 2025-07-17: Teaclave TrustZone SDK v0.5.0
- WIP: Teaclave TrustZone SDK v0.6.0 (first release as a TLP)
## Project Activity
### Development Activity
- Ongoing work to improve build/test environment for TEE applications.
- Introduced new branches showcasing Web3 use cases, with plans to merge into
the main branch.
- Active effort to eliminate all `cargo clippy` warnings and enforce stricter
CI checks.
- ~30–40 commits merged this quarter.
### Community Activity
- Developer mailing list: moderate activity (~20 threads since graduation).
- No new committers or PMC members since graduation.
## Current Plans
- **Short term:**
- Release Teaclave TrustZone SDK v0.6.0.
- Enforce strict CI checks (clippy, lint, tests) to enhance codebase
quality.
- **Medium term:**
- Open source additional real-world SDK use cases (e.g., Web3 scenarios).
- Align release cadence with OP-TEE’s quarterly releases.
## Community Changes
- At graduation: 18 initial PMC members.
- Current: 18 PMC members, no new additions.
- No new committers or PMC members elected since graduation.
- PMC membership represents a healthy diversity of organizations.
## Project Branding
- No branding issues.
- Website and download pages comply with Apache branding requirements.
## Legal Issues
- No legal issues to report.
## Infrastructure
- No infrastructure concerns at this time.
---
**Submitted by:** [Zhaofeng Chen](zfc@apache.org), Apache Teaclave PMC Chair — September 2025
-----------------------------------------
Attachment CD: Report from the Apache Tomcat Project [Christopher Schultz]
## Description:
The Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.
The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10
and later implement specifications developed as part of Jakarta EE. Tomcat 9
and earlier implement specifications developed as part of Java EE.
## Project Status:
The Tomcat project has a strong and active community,
both of users and committers. We maintain 3 major release version numbers, and
have a release cadence of approximately one release per major-version per
month.
Issues for the board: none
## Membership Data:
Apache Tomcat was founded 2005-05-17 (20 years ago)
There are currently 50 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Soumis on 2024-07-05.
- No new committers members. Last addition was John Engebretson on 2025-02-05.
- PMC chair was changed to Christopher Schultz on 2025-06-18.
## Project Activity:
- Apache Tomcat 11.0.10 was released on 2025-08-06.
- Apache Tomcat 11.0.9 was released on 2025-07-04.
- Apache Tomcat 10.1.44 was released on 2025-08-07
- Apache Tomcat 10.1.43 was released on 2025-07-04.
- Apache Tomcat 9.0.108 was released on 2025-08-06.
- Apache Tomcat 9.0.107 was released on 2025-07-04.
- Apache Tomcat Native 2.0.9 was released on 2025-05-29.
The Apache Tomcat team has issued and fixed the following CVEs during the
previous quarter. All CVEs apply to Tomcat 9, 10.1, and 11 except for
2025-52434 which only affects Tomcat 9.
CVE-2025-48976 - DoS in Commons FileUpload
CVE-2025-48988 - DoS in multipart upload
CVE-2025-48989 - DoS in HTTP/2 due to client triggered stream reset
CVE-2025-49124 - Side-loading via Tomcat installer for Windows
CVE-2025-49125 - Security constraint bypass for PreResources and PostResources
CVE-2025-52520 - DoS due to overflow in file upload limit
CVE-2025-52434 - APR/Native Connector crash leading to DoS
CVE-2025-53506 - DoS via excessive HTTP/2 streams
CVE-2025-55668 - Session fixation possible via rewrite valve
The project is taking part in the upcoming ASF Conference Community Over Code
in Minneapolis, MN in September, with PMC members attending.
The PMC have had discussions with HeroDevs that may lead to the project
receiving funding from HeroDevs. Our working plan is that any funding
received would be used to facilitate one or more security-focused
committer meetups - potentially around CoC 2026. This would repeat the
pattern established by our use of funds provided by Google that resulted in
our very successful Tocat Security Day in Bratislava following the Community
Over Code EU conference in 2024.
We have been notified that Apache Tomcat will be included as a "key target" in
an event called zeroday.cloud which will be hosted by Wiz Research this
December, in partnership with their sponsors AWS, Microsoft, and Google Cloud.
Wiz Research will communicate any findings with the Apache Tomcat Security Team
in a coordinated disclosure process.
The PMC received an offer for a free "AI Support Engineer" from RunLLM.
After review, the consensus was to decline the offer.
We have begun to receive what look like AI-generated vulnerability reports.
While they initially look plausible, they turn out to be nonsense.
The volume is low and isn't causing notable issues so far.
## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
-----------------------------------------
Attachment CE: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Health
Overall contributions are slightly up, yet still very low for a project of
our scope. Roughly 41 commits from 4 committers in the 3 months since June
16th. Up from roughly 17 commits from 5 committers in the prior two months.
In July we saw our first PR from a non-committer all year. Though it did
introduce issues, it also sparked some good list conversation and knowledge
sharing which resulted in other changes.
## Activity
As noted in the prior report, the project proceeded with upgrading the
MicroProfile version from 6.0 to 6.1 and released a TomEE 10.1 reflecting
that change. The majority of work was in this area.
Some discussion occured on potentially upgrading the JPA API version from
the version included in Jakarta 10, on which TomEE 10 is based, to the JPA
version included in Jakarta EE 11. This would have resulted in TomEE 10
including a mix of Jakarta EE 10 and 11 features. It was ultimately decided
to focus time on Jakarta EE 11.
Discussion on starting work towards Jakarta EE 11 has just started and is
days old.
Markus Jung has been added to the TomEE PMC and has since lead three
releases from the project.
## PMC changes:
- Currently 13 PMC members.
- Last PMC addition Markus Jung on July 23rd, 2025
## Committer base changes:
- Currently 35 committers.
- Last committer added was Markus Jung on September 12th, 2024
- Previous committer added was Thomas Andraschko on March 25th, 2024
## Releases:
- Apache TomEE 10.1.0 on June 16, 2025
- Jakarta EE API 10.0.1 on August 5, 2025
- Apache TomEE 10.1.1 on August 19, 2025
- Apache TomEE 10.1.2 on September 19, 2025
-----------------------------------------
Attachment CF: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
The mission of Traffic Server is to develop and maintain a high-performance,
scalable, and extensible caching proxy server that fully supports HTTP/1.1 and
HTTP/2 protocols.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Traffic Server was founded 2010-04-20 (15 years ago)
There are currently 70 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 Josiah VanderZee on 2024-01-07.
## Project Activity:
Over the past quarter, our team successfully delivered three critical updates,
focusing on bug fixes and enhanced security measures. We are actively
developing the next major feature release, version 10.2.0, slated for launch
in Q1 of next year. Additionally, we continue to maintain two active release
branches: the 9.2.x Long-Term Support (LTS) and the 10.1.x Stable Release,
ensuring ongoing stability and reliability for our users.
## Community Health:
We’re excited to announce the planning of our upcoming ATS Fall Summit, which
will be hosted virtually to connect our global community.
Our weekly bug and issue scrubs, held every Monday, remain a cornerstone of
our commitment to quality, facilitating prompt review of pull requests and
resolution of user-reported issues. Community engagement is on the rise, with
growing participation and collaboration across our platforms.
-----------------------------------------
Attachment CG: 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 on 2025-08-20 (1 month 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 (the project graduated recently).
- No new committers were added (the project graduated recently).
## Project Activity:
During August, there were discussions across areas such as content generation,
infrastructure, and badge issuance. The most active thread focused on whether
and how to issue open badges for training courses. Other discussions covered
the structure of starter training decks, the transition to GitHub issues
rather than JIRA, and broader questions about how best to present and generate
content.
## Community Health:
Apache Training is in good health. As a newly established top-level project,
community activity in August was steady, with a focus on laying the
foundations for our training materials and refining our infrastructure. The
project will also be featured in a talk at the upcoming Community Over Code NA
conference.
-----------------------------------------
Attachment CH: Report from the Apache TsFile Project [Jialin Qiao]
Hi,
The following is the quarter report of TsFile:
## Description:
The mission of Apache TsFile is the creation and maintenance of software
related to a columnar storage file format designed for time series data
## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: no
## Membership Data:
- There are currently 21 committers and 18 PMC members in this project.
- The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Gaofei Cao on 2023-11-15.
- No new committers. Last addition was Xinhao Gu on 2025-04-22.
## Project Activity:
### Recent releases:
- 2.1.0 was released on 2025-07-11.
- 2.0.3 was released on 2025-05-26.
- 1.1.1 was released on 2025-04-14.
### Main work of project:
The TsFile project has made substantial progress recently. With the release
of
version 2.1.0, a number of new features have been introduced. Notably, the
Cpp/C/Python implementations now support TsFile Table reader and writer,
marking a significant expansion of the project's multi-language interface
capabilities. We are also attempting to implement some state-of-the-art
time-series data encoding algorithms(like Camel[1]) in tsfile, aiming to
improve the compression ratio of tsfile.
## Community Health:
The activity of the development mailing list has seen a slight decline
recently, still because some discussions have migrated to GitHub issues.
Recently, a research team from Chongqing University specializing in
floating-point number encoding and compression algorithms[2,3] has contacted
the community, expressing their intention to contribute the compression
algorithm published in their paper to the built-in encoding list of tsfile.
The development and discussion process will take place on the mailing list.
Meanwhile, we are committed to making tsfile a favorite in the academic
community. Going forward, encoding and compression algorithms from relevant
papers can all be implemented in tsfile, and end-to-end experiments can be
conducted based on tsfile to form fair comparisons.
[1] Yao, Yuanyuan, et al. "Camel: Efficient Compression of Floating-Point
Time
Series." Proceedings of the ACM on Management of Data 2.6 (2024): 1-26.
[2] Ruiyuan Li, Zheng Li, Yi Wu, Chao Chen, Songtao Guo, Ming Zhang, and Yu
Zheng. 2023. Erasing-based lossless compression method for streaming
floating-point time series. CoRR abs/2306.16053.
[3] Ruiyuan Li, Zheng Li, Yi Wu, Chao Chen, and Yu Zheng. 2023. Elf:
Erasing-based Lossless Floating-Point Compression. Proc. VLDB Endow. 16, 7,
1763–1776.
-----------------------------------------
Attachment CI: Report from the Apache TVM Project [Tianqi Chen]
## Description:
The mission of Apache TVM is the creation and maintenance of software related
to compilation of machine learning models to run on a wide range of hardware
platforms
## Project Status:
Current project status: ongoing
Issues for the board: N/A
## Membership Data:
Apache TVM was founded 2020-11-17 (5 years ago)
There are currently 81 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- Ongoing vote on adding new PMC member.
- Qingchao Shen was added as committer on 2025-06-11
## Project Activity:
Recent releases:
0.21.0 was released on 2025-07-16.
0.20.0 was released on 2025-04-27.
The community continues to bring improvement in directions of frontend
support, backend enablement, and ffi mechanism improvements:
- Improved PyTorch integration for relax
- Improvements in ONNX support
- Support the new reflection mechanism based on FFI refactor
- Improvements in tensormap support
- Community start discussion on bringing up the FFI module into
separate repo
## Community Health:
The community landed 170 commits into main in the past quarter from 38
authors. As we are in the age of generative AI. We start to see growing
interest in new models like supporting LLMs as well as integrating with
existing ecosystems. The recent FFI module refactor helps toward the
direction. It is also interesting to consider continued support and
integrations with PyTorch and other framework ecosystems.
-----------------------------------------
Attachment CJ: Report from the Apache UIMA Project [Richard Eckart de Castilho]
## Description:
Apache UIMA (*) software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video. (*) Unstructured Information Management Architecture.
## Project Status:
Current project status: Ongoing (low)
Issues for the board: none
## Membership Data:
Apache UIMA was founded 2010-03-17 (15 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.
## Project Activity:
There have been no new releases since the last board report.
Still planning to do a UIMA Java SDK 3.6.1 soon.
## Community Health:
Over the course of the summer, there has not really been any particularly
notable or significant activity to report.
-----------------------------------------
Attachment CK: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Unomi was founded 2019-02-20 (7 years ago)
There are currently 16 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Jonathan Sinovassin-Naïk on 2024-11-25.
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.
We currently have a vote open for a new committer, which will close soon.
## Project Activity:
At the time of writing, a new version has been prepared and is being voted on
(v2.7.0), which is mostly a maintenance release for the V2 branch. A lot of
work is happening now on the next major version, V3, and that is now the main
focus of the development effort. V3 is one of the most important releases in
the project's history, bringing major features such as multi-tenancy,
improved clustering support, and a lot of other improvements to the server.
It will also feature a V2 API compatibility mode to address the migration of
existing users. A lot of effort has also been put into the quality of the
changes by increasing the code coverage performed by automated tests (unit
and integration tests)
## Community Health:
To address rbowen's board feedback: the community has been very active under
the hood, but, indeed, that was not being reflected in the mailing list
or Slack communication. The amount of work has been significant, but
communication around it was delayed because a lot of things were only
communicated once they were completed, which is mostly the case now. The
community is therefore very active, but could improve its internal
communication. The monthly meetings are a good step towards this
improvement, and the focus on making sure that no decision happens during these
meetings is still a critical focus. Serge Huber (PMC Chair) will also be on
location for the Community-over-Code conference in Minneapolis and will
present the project in two separate sessions to grow the community.
Once the V3 is near release (and after that), a lot of communication effort
will be planned to make sure the word gets out.
-----------------------------------------
Attachment CL: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.
## Project Status:
Current project status: Dormant
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (13 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
- Last release: 2025-03-24
- We had some momentum got, but it seems to have died out.
## Community Health:
The project is still being used by various organizations, and we do have PMC
members watching things.
-----------------------------------------
Attachment CM: Report from the Apache Web Services Project [Daniel Kulp]
## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.
## Project Status:
Current project status: ongoing, very low activity
Issues for the board: none
## Membership Data:
Apache Web Services was founded 2003-01-22 (23 years ago)
There are currently 223 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Robert Lazarski on 2021-06-14.
- No new committers. Last addition was Alessio Soldano on 2014-09-14.
## Project Activity:
WebServices is a mature project based on standards that are also quite mature.
As such, there is not a significant amount of activity required. However, user
questions are being answered promptly, bugs are being fixed, and there are at
least 3 independent PMC members around making sure the project can continue to
produce releases as needed. Since SOAP/XML based Web Services is no longer
considered state of the art, we don't expect a major uptick in new development
efforts, new committers, etc...
There was very few changes this period other than than dependabot and other
dependency updates. There were a couple of JIRAs filed, but fixes were
already in place in the latest snapshots with hopes to get updated
releases out soon.
Latest Releases:
WSS4J 4.0.0 was released on 2025-02-14
Axiom-2.0.0 was released on 2025-02-06
WSS4J 3.0.4 was released on 2024-11-14
Neethi-3.2.1 was released on 2024-10-30
XmlSchema-2.3.1 was released on 2023-09-07
Woden-1.0M10: 2015-09
## Community Health:
As mentioned, SOAP/WebServices is not considered state-of-the-art anymore and
we are getting very little contribution from anyone other than the 2 or 3
regulars" that are driving features and changes needed for CXF (which is
being driven by their employers). Thus, we are not seeing any possibilities
for future new committers or PMC members. However, there are plenty of
people around that can do releases and answer questions and respond to
security issues. It's a mature project.
-----------------------------------------
Attachment CN: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
The mission of Wicket is the creation and maintenance of software related to
Component-based Java Web Application Framework.
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Wicket was founded 2007-06-20 (18 years ago)
There are currently 35 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Pavlovich on 2025-01-27.
- No new committers. Last addition was Matt Pavlovich on 2025-01-27.
## Project Activity:
Last quarter was pretty quiet, as it usually happened during summer time. We had
just a release for branch 10.x with Wicket 10.6.0. As for many other projects,
the upcoming release of the next LTS of Java (25) is an important milestone and
we will probably consider to roll out a new main release (the 11th) to stay up
to date with the entire Java ecosystem that will switch to Java 21 as minimum
required version.
## Community Health:
Although we didn't have many interactions during the last quarter, community
remain healthy and stable contributing to bug solving. Downloads are still high
and most of them are for the last main branch 10.x
-----------------------------------------
Attachment CO: Report from the Apache Xerces Project [Michael Glavassevich]
Apache Xerces is a collaborative software development project dedicated to
providing robust, full-featured, commercial-quality, and freely available XML
parsers and closely related technologies on a wide variety of platforms
supporting several languages.
========
Xerces-J
Elliotte Rusty Harold was elected as a new committer and PMC member in June
and has made many contributions to clean up the Xerces build and testing.
Multiple old JIRA issues have been updated and resolved. A couple PRs from the
community were also merged to GitHub.
Mailing list traffic has been high; roughly 270+ posts on the j-dev and
j-users lists since the beginning of June 2025. Most of this activity was in
June and July.
No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022).
========
Xerces-C
There was no development activity since the last report. Boris Kolpackov
recently agreed to take over release duties for Xerces-C as Scott Cantor steps
back from that role. Thanks to Scott for driving this for many years.
Mailing list traffic has been very low; roughly 5+ posts on the c-dev and
c-users lists since the beginning of June 2025.
The latest release is Xerces-C 3.2.5 (December 20th, 2023).
========
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
========
XML Commons
No activity over the reporting period.
========
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and June 2025
(Xerces-J).
The most recent addition to the PMC was in June 2025.
One committer has committed changes to GitHub since June 2025.
-----------------------------------------
Attachment CP: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Yetus was founded 2015-09-15 (10 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
Nothing of particular interest really, other than it appears that
Github has changed something again that causes multi-platform docker builds
to break, based upon reports from our CI.
## Community Health:
Low activity across all human-related metrics, but given the stable status of
the project that should not be surprising. Still in use by other Apache
projects and others outside of the ASF. Clearly capable of getting a release
out since 0.15.1 was released earlier this year.
-----------------------------------------
Attachment CQ: Report from the Apache ZooKeeper Project [Flavio Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (15 years ago)
There are currently 33 committers and 18 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 Damien Diederen on 2024-04-16.
- No new committers. Last addition was Kezhu Wang on 2024-08-02.
## Project Activity:
Recent releases:
3.9.4 was released on 2025-08-29.
3.8.5 being voted
## Community Health:
The same observation from the last report still holds about committer and PMC
participation, although we have improved participation metrics in this period
from the email and jira metrics. We are copying the observation from the last
report here for completeness.
We seem to have an issue of committer and PMC participation in the community.
We observe questions and discussion threads on the project lists, but not
enough committer and PMC engagement to drive the work forward. We would need
more engagement to be able to work with current developers to eventually offer
them committership and ensure that the community can continue to exist, grow
and thrive.
------------------------------------------------------
End of minutes for the September 24, 2025 board meeting.
Index