Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
December 17, 2025
1. Call to order
The meeting was scheduled for 22:00 UTC and began at N/A 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-12-17T22:00:00&msg=ASF+Board+Meeting
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Jim Jagielski
Zili Chen
Greg Stein
Rich Bowen
Shane Curcuru
Justin Mclean
Sander Striker
Jean-Baptiste Onofré
Kanchana Pradeepika Welagedara
Directors Absent:
none
Executive Officers Present:
Craig McClanahan
Ruth Suehle
Craig L Russell
Jeff Jirsa
Executive Officers Absent:
Matt Sicker
Guests:
Daniel Gruno
Sally Khudairi
Andrew Wetmore
Thomas Neidhart
Alin Jerpelea
Paul King
Dave Fisher
Jarek Potiuk
Brian Proffitt
James Dailey - joined :13
Melissa Logan - joined :15
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of November 19, 2025
See: board_minutes_2025_11_19.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
First I'd like to thank our Vice Chair for running the November meeting.
It's that time of year. The days are still getting shorter. Many of us are
trying to wrap up items before the end of year. All the while trying to avoid
the yearly cold or flu. With varying level of success.
Personally I am looking forward to the holidays, to take some time to clear
items from my ASF TODO list. I intend to work on preparing for the Members
Meeting for the date set in March. Which is a reminder that there are only
two meetings left before the end of this board term.
I wish everyone a great end of year, and look forward to seeing everyone in
2026.
B. President [Ruth Suehle]
Ops team is continuing to work towards better documentation of each officer's
tasks and where they store information related to their office.
I've been invited to represent the ASF on a panel again at The EU Open Source
Policy Summit before FOSDEM, as well as at the Software Heritage Symposium
(also during Open Source Week).
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig McClanahan]
Normal operations continue.
On the Balance Sheet, you will notice a new bank account ("Ramp Business
Account") on the Balance Sheet. This is a bank account, separate from TD
Bank, that is managed by Ramp but processed by another bank. This will not
only pay interest, but also spread accounts over which we have FDIC Insurance
Coverage.
D. Secretary [Matt Sicker]
In November secretary received and filed 25 ICLAs.
E. Executive Vice President [Jeff Jirsa]
Status of Code of Conduct effort unchanged from last month.
No other material topics to report.
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 / Zili]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Greg]
See Attachment 13
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, jim, kanchana]
# Atlas [gstein]
# BVal [striker]
# Brand Management [striker]
# CarbonData [jbonofre]
# IoTDB [jmclean]
# Legal Affairs [striker]
# NetBeans [jim]
# Synapse [kanchana]
# Teaclave [striker]
# Wayang [jmclean]
# cTAKES [rbowen, kanchana]
A. Apache Airavata Project [Suresh Marru / Sander]
See Attachment A
B. Apache Airflow Project [Bolke de Bruin / Kanchana]
See Attachment B
C. Apache Allura Project [Dave Brondsema / JB]
See Attachment C
D. Apache Ambari Project [Brahma Reddy Battula / Shane]
No report was submitted.
E. Apache Artemis Project [Christopher L. Shannon / Rich]
See Attachment E
F. Apache Atlas Project [Madhanmohan Neethiraj / Jim]
See Attachment F
G. Apache Axis Project [Robert Lazarski / Rich]
See Attachment G
H. Apache Beam Project [Kenneth Knowles / Sander]
No report was submitted.
I. Apache Bigtop Project [Masatake Iwasaki / Zili]
See Attachment I
J. Apache BookKeeper Project [Enrico Olivelli / Shane]
See Attachment J
K. Apache BuildStream Project [Tristan Van Berkom / Jim]
No report was submitted.
L. Apache BVal Project [Matt Benson / Greg]
See Attachment L
@Greg: roll call
M. Apache Camel Project [Andrea Cosentino / Justin]
See Attachment M
N. Apache CarbonData Project [Jacky Li / JB]
No report was submitted.
O. Apache Cayenne Project [Michael Gentry / Kanchana]
See Attachment O
P. Apache Celeborn Project [Keyong Zhou / JB]
See Attachment P
Q. Apache CloudStack Project [Nicolás Vázquez / Sander]
See Attachment Q
R. Apache Commons Project [Gary D. Gregory / Greg]
See Attachment R
S. Apache Cordova Project [Bryan Ellis / Jim]
See Attachment S
T. Apache cTAKES Project [Pei J Chen / Zili]
See Attachment T
@Zili: follow up on roll call
U. Apache Curator Project [Enrico Olivelli / Shane]
See Attachment U
V. Apache Daffodil Project [Mike Beckerle / Justin]
See Attachment V
W. Apache DataFusion Project [Andrew Lamb / Kanchana]
See Attachment W
X. Apache DevLake Project [Hezheng Yin / Rich]
See Attachment X
Y. Apache Dubbo Project [Jun Liu / JB]
No report was submitted.
Z. Apache ECharts Project [Wenli Zhang / Zili]
See Attachment Z
AA. Apache Felix Project [Karl Pauls / Sander]
See Attachment AA
AB. Apache Flex Project [Harbs / Kanchana]
See Attachment AB
AC. Apache Flink Project [Robert Metzger / Justin]
See Attachment AC
AD. Apache Gobblin Project [Abhishek Tiwari / Rich]
See Attachment AD
AE. Apache Grails Project [James Fredley / Greg]
See Attachment AE
AF. Apache Gravitino Project [Jerry Shao / JB]
See Attachment AF
AG. Apache Guacamole Project [Mike Jumper / Shane]
See Attachment AG
AH. Apache Gump Project [Stefan Bodewig / Jim]
No report was submitted.
AI. Apache Helix Project [Junkai Xue / Sander]
See Attachment AI
AJ. Apache Hive Project [Naveen Gangam / Jim]
See Attachment AJ
AK. Apache Hop Project [Hans Van Akelyen / JB]
See Attachment AK
AL. Apache Hudi Project [Vinoth Chandar / Greg]
See Attachment AL
AM. Apache Iceberg Project [Ryan Blue / Kanchana]
See Attachment AM
AN. Apache Ignite Project [Dmitry Pavlov / Zili]
See Attachment AN
AO. Apache Incubator Project [Justin Mclean / Justin]
See Attachment AO
AP. Apache IoTDB Project [Xiangdong Huang / Rich]
See Attachment AP
@Justin: follow up on license and trademark issues
AQ. Apache Jackrabbit Project [Marcel Reutegger / Shane]
See Attachment AQ
AR. Apache Karaf Project [Jean-Baptiste Onofré / JB]
See Attachment AR
AS. Apache Kvrocks Project [Mingyang Liu / Justin]
See Attachment AS
AT. Apache Kyuubi Project [Cheng Pan / Shane]
See Attachment AT
AU. Apache Libcloud Project [Tomaž Muraus / Zili]
No report was submitted.
AV. Apache Linkis Project [Shuai Di / Greg]
See Attachment AV
AW. Apache Lucene Project [Dawid Weiss / Kanchana]
See Attachment AW
AX. Apache Lucene.Net Project [Shad Storhaug / JB]
No report was submitted.
AY. Apache Mynewt Project [Szymon Janc / Zili]
See Attachment AY
AZ. Apache NetBeans Project [Geertjan Wielenga / Jim]
See Attachment AZ
@Jim: followup regarding possible MOU for FriendsOfNetBeans
BA. Apache OFBiz Project [Jacopo Cappellato / Sander]
See Attachment BA
BB. Apache Olingo Project [Michael Bolz / Shane]
No report was submitted.
BC. Apache OpenDAL Project [Hao Ding / Rich]
See Attachment BC
BD. Apache OpenNLP Project [Jeffrey T. Zemerick / Justin]
See Attachment BD
BE. Apache OpenWebBeans Project [Mark Struberg / Zili]
See Attachment BE
BF. Apache Paimon Project [Jingsong Lee / Sander]
See Attachment BF
BG. Apache Pekko Project [PJ Fanning / Rich]
See Attachment BG
BH. Apache Pig Project [Koji Noguchi / Greg]
See Attachment BH
BI. Apache PLC4X Project [César García / Kanchana]
No report was submitted.
BJ. Apache Portable Runtime (APR) Project [Yann Ylavic / Jim]
No report was submitted.
BK. Apache Pulsar Project [Matteo Merli / Justin]
No report was submitted.
BL. Apache RocketMQ Project [Xiaorui Wang / JB]
No report was submitted.
BM. Apache Royale Project [Yishay Weiss / Shane]
No report was submitted.
BN. Apache SeaTunnel Project [Jun Gao / Sander]
See Attachment BN
BO. Apache ServiceMix Project [Krzysztof Sobkowiak / Greg]
No report was submitted.
BP. Apache ShardingSphere Project [Liang Zhang / Kanchana]
See Attachment BP
BQ. Apache Shiro Project [Lenny Primak / JB]
See Attachment BQ
BR. Apache SINGA Project [Wang Wei / Zili]
No report was submitted.
BS. Apache Sling Project [Robert Munteanu / Justin]
See Attachment BS
BT. Apache SpamAssassin Project [Giovanni Bechis / Shane]
See Attachment BT
BU. Apache Storm Project [Richard Zowalla / Jim]
See Attachment BU
BV. Apache StreamPark Project [Huajie Wang / Rich]
No report was submitted.
BW. Apache Synapse Project [Isuru Udana / Shane]
See Attachment BW
BX. Apache Teaclave Project [Zhaofeng Chen / JB]
See Attachment BX
@Justin: clarify that their earlier report was approved
BY. Apache Tomcat Project [Christopher Schultz / Kanchana]
See Attachment BY
BZ. Apache Traffic Server Project [Bryan Call / Rich]
No report was submitted.
CA. Apache TVM Project [Tianqi Chen / Zili]
See Attachment CA
CB. Apache UIMA Project [Richard Eckart de Castilho / Greg]
See Attachment CB
CC. Apache Unomi Project [Serge Huber / Justin]
See Attachment CC
CD. Apache VCL Project [Josh Thompson / Sander]
See Attachment CD
CE. Apache Velocity Project [Nathan Bubna / JB]
No report was submitted.
CF. Apache Wayang Project [Zoi Kaoudi / Jim]
See Attachment CF
CG. Apache Web Services Project [Daniel Kulp / Rich]
No report was submitted.
CH. Apache Wicket Project [Andrea Del Bene / Zili]
See Attachment CH
CI. Apache XML Graphics Project [Clay Leeds / Justin]
No report was submitted.
CJ. Apache Yetus Project [Allen Wittenauer / Sander]
See Attachment CJ
CK. Apache ZooKeeper Project [Flavio Junqueira / Shane]
See Attachment CK
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Calcite Project Chair
WHEREAS, the Board of Directors heretofore appointed Ruben Q L
(rubenql) to the office of Vice President, Apache Calcite, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Ruben Q L from the office of Vice President, Apache Calcite, and
WHEREAS, the Project Management Committee of the Apache Calcite project
has chosen by vote to recommend Mihai Budiu (mbudiu) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Ruben Q L is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Calcite, and
BE IT FURTHER RESOLVED, that Mihai Budiu be and hereby is appointed to
the office of Vice President, Apache Calcite, 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 Calcite Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache BuildStream Project Chair
WHEREAS, the Board of Directors heretofore appointed Tristan Van Berkom
(tvb) to the office of Vice President, Apache BuildStream, and
WHEREAS, the Board of Directors is in receipt of the resignation of Tristan
Van Berkom from the office of Vice President, Apache BuildStream, and
WHEREAS, the Project Management Committee of the Apache BuildStream project
has chosen by vote to recommend Abderrahim Kitouni (akitouni) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Tristan Van Berkom is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache BuildStream, and
BE IT FURTHER RESOLVED, that Abderrahim Kitouni be and hereby is appointed to
the office of Vice President, Apache BuildStream, 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 BuildStream Project Chair,
was approved by Unanimous Vote of the directors present.
C. Update Apache Security Team Membership
WHEREAS, the Apache Software Foundation (ASF) Board Commmittee,
known as the Apache Security Team expects to better serve
its purpose through the periodic update of its membership; and
WHEREAS, the Apache Security Team is a Board-appointed committee
whose membership must be approved by Board resolution;
NOW, THEREFORE, BE IT RESOLVED, that the following ASF
members be added as Apache Security Team members:
Piotr P. Karwasz https://whimsy.apache.org/roster/committer/pkarwasz
Special Order 7C, Update Apache Security Team Membership, was
approved by Unanimous Vote of the directors present.
D. Terminate the Apache Olingo Project
WHEREAS, the Board of Directors deems it no longer in the best interest of the
Foundation to continue the Apache Olingo project due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Olingo 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 Olingo Project; and be it further
RESOLVED, that the office of "Vice President, Apache Olingo" is hereby
terminated; and be it further
RESOLVED, that the Apache Olingo PMC is hereby terminated.
Special Order 7D, Terminate the Apache Olingo Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Greg: clarify community overlap with Mifos and state of community
[ Fineract 2025-07-16 ]
Status: Done. I periodically chat with James Dailey. Progress is being made.
* JB: pursue potential Attic for CarbonData
[ CarbonData 2025-08-20 ]
Status: I started a discussion:
https://lists.apache.org/thread/jf385z0yw00kfjqgg58yfwg3s30sz6k5
* JB: pursue a roll call for Velocity
[ Velocity 2025-08-20 ]
Status: https://lists.apache.org/thread/j6yw7w18j22yx1qdkj4z4xgrf6961blw
* Zili: ask Doris PMC to address issues raised by Brand Management in next quarterly report
[ Doris 2025-10-15 ]
Status: See https://lists.apache.org/thread/md36fnsfdxsbs3jqtxf8c30wy5v2bbl6. Waiting on Doris PMC report and follow up.
* Justin: pursue a roll call for MADlib
[ MADlib 2025-10-15 ]
Status: , waiting for PMC response.
* Sander: discuss Policy for Inactive Committers with project PMC
[ NiFi 2025-10-15 ]
Status: https://lists.apache.org/thread/wnph5t6xn9rts4smhtd2gmfpjktyqjv8
* Shane: discuss Attic with Olingo PMC
[ Olingo 2025-10-15 ]
Status: Done. Attic resolution submitted. Roll call got three responses of -1 or -0 votes.
In progress: very low response from PMC, but we should probably let dev@ know before attic'ing to be polite. Suggest attic next month.
* Greg: pursue a roll call for Pinot
[ Pinot 2025-10-15 ]
Status: Done. There were three respondents; barely. The PMC uses Slack too much (separate issue).
* Zili: follow up about Attic
[ Libcloud 2025-11-19 ]
Status:
* Kanchana: follow up with Logging Services PMC about RTC
[ Logging Services 2025-11-19 ]
Status: Completed. Status : The core issue with the Logging Service was a request to implement a feature that supports RTC statistics. The project prefers RTC over CTR and therefore requires a mechanism to monitor commit logs (No commits are merged without being reviewed first)
). This appears to be a custom feature request specific to this project, and there is no data indicating that it would benefit other Apache projects. LS PMC chair is trying to work on data. The board recommended resolving this through community collaboration or by exploring a simple automation/ configurations or GitHub App–based solution that infrastructure team could help either configuring or installing in ASF's GHEC. The relevant discussion is captured in this thread: https://lists.apache.org/thread/lpjr4p9o4to7zb71rx30f1wgoqq81sz3
. At this stage, the Tooling/Infrastructure VP has also been engaged. The LS community has since identified a solution(https://github.com/ossf/scorecard/blob/main/clients/githubrepo/graphql.go) that may work for them and investigating:
On a side note: community thinks that having a feature implemented to address : SLSA Source track helps (https://slsa.dev/spec/v1.2/) supply security chain, waiting on feedback from @wave on this.
Note :This community would like to hear the Board’s feedback on whether CTR or RTC is more aligned with the Apache Way and the ASF’s mission. My individual opinion was that it's the PMC and community preference.
* Shane: follow up with Mahout about professional status
[ Mahout 2025-11-19 ]
Status:
* Justin: discuss path to Attic
[ ManifoldCF 2025-11-19 ]
Status:
* Greg: talk to Pinot PMC about communication channels
[ Pinot 2025-11-19 ]
Status:
* Rich: add paragraph about Slack v. mailing lists in upcoming PMC communications
[ Pinot 2025-11-19 ]
Status: Done. See https://lists.apache.org/thread/md36fnsfdxsbs3jqtxf8c30wy5v2bbl6. Waiting on Doris PMC report and follow up.
* Rich: follow up about private communications
[ SIS 2025-11-19 ]
Status:
* Greg: follow up with TsFile PMC about publishing to PyPI
[ TsFile 2025-11-19 ]
Status:
* Greg: follow up with board about PyPI policy
[ TsFile 2025-11-19 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 22:51 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period November 2025
* ISSUES FOR THE BOARD
I would appreciate a board view on PODLINGNAMESEARCH-248.
* OPERATIONS
Responded to the following queries, liaising with projects as required:
- provided advice to STREAMPARK regarding a vendor's product comparison page
- provided clarification on the requirements for links to sponsors
- provided advice to AIRFLOW regarding vendor support of the annual community
survey
- provided advice to AIRFLOW regarding meeetups
* REGISTRATIONS
Worked with counsel to progress our OPENDAL registration in the US.
Worked with counsel to transfer the SEATA marks to the ASF.
* INFRINGEMENTS
AIRFLOW addressed an issue with an external website.
KAFKA addressed an issue with an external product.
No progress regarding a potential infringement of PDFBOX.
No progress regarding a site with a possible infringement of APISIX.
No update on the formal trademark infringement complaint submitted to GitHub
regarding an NPM package on behalf of the logging PMC.
No progress this month regarding the downstream vendor with multiple
infringements of ASF marks.
No further progress for IOTDB.
No progress for The KAFKA PMC in addressing a potential infringement of KAFKA.
No progress working with the XMLGRAPHICS PMC to resolve a potential
infringement of FOP.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we successfully onboarded a new Silver Sponsor and are in the process
of completing onboarding of a corporate contributor that will be recognized as
a Bronze Sponsor.
b —Renewals: we have secured one renewing Platinum Sponsor and continue to
actively advance renewals and retention, as well as reactivation with lapsed
Sponsors (Busy Season for Fundraising!).
c —Payments: 1 —New: we received payment from one new Silver Sponsor. 2
—Received: we received Sponsorship renewal payments from one Platinum, one
Silver, and one Bronze Sponsor. 3 —Incoming: we await renewal payments from
two Platinum, three Gold, five Silver, and three Bronze Sponsors. We also
await a Gold Targeted Sponsorship payment.
2) Targeted Sponsors: we are in the process of onboarding a new Gold Targeted
Sponsor. Our Targeted Sponsor outreach efforts continue, including end-of-year
renewal engagement.
3) Sponsor Relations: our standing outreach and renewal activities continue,
per usual, with an uptick in activity for those needing to deploy end-of-year
budgets. We are preparing for Giving Tuesday on 2 December, and worked with
Marketing & Publicity on publishing the final blog post in our 4-part series
on ways to support the ASF. We met one-on-one with two Sponsors, and provided
further information on supporting the Tooling Initiative. We have updated
Fundraising/Sponsorship presentation materials for candidate supporting
organizations. Our Q4 call with Gold and Platinum Sponsors will be held 10
December and will highlight the ASF Tooling Initiative.
4) Event Sponsorship: aside from final collections from two outstanding
sponsorship payments from Community Over Code North America, we are standing
by to engage with the ASF Conferences team on sponsorships for 2026.
5) Individual Donations and Corporate Giving: we received $2,975 in online
donations via https://donate.apache.org/ . We also received a Silver
Sponsorship payment via our online donation platform. In addition, this month
we received a corporate contribution from an employee incentive program that
converts their volunteer hours to charitable dollars.
6) Administrivia: we continue to work particularly closely with ASF Treasury
and Accounting teams as the volume of invoicing/re-invoicing/PO processing and
registering/onboarding onto Sponsor payment platforms increase during this
time of year. We are also working with Infrastructure regarding the
administrative management process of a recurring Targeted Sponsorship that is
scaling up to meet growing PMC demand.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Produced November issue of Plus One newsletter
* Subscriber list now totals 851 (470 new subscribers in November)
* Total sent: 604 | Unique opens: 194 | Open rate: 32%
* Collaborated with ASF Fundraising to develop a blog and execute a social
campaign for #GivingTuesday and to encourage donations to The ASF
* Published blog highlighting Apache Fineract being recertified as a United
Nations digital public good
Project Comms
* Developed and issued press release announcing Apache Artemis and Apache
Wayang as new Top-Level Projects
* Published and promoted project spotlight featuring Apache Geode
* Pitched case study featuring Apache Ozone / DiDi Global to The New Stack
Brand Project
* Launched #ASFNewLeaf, a social media giveaway to drive awareness around The
ASF’s new logo and spur community engagement
* Drafted website policy on archival or deleting pages and published to public
Wiki
* Continued integrating new brand assets across social media channels and
Apache.org blog postings
* Continued coordination between Apache projects and designer to update logos
that contain feather or native imagery
Social Media Overview
The highest performing pieces of content for November include news from the
announce list, the #ASFNewLeaf campaign launch, and Apache Fineract’s
recertification as a UN Digital public good.
Social Highlights (X + LinkedIn + Bluesky)@
* Total Audience: 145,901
* X: 65,744
* Bluesky: 903
* LinkedIn: 79,254
* Total Posts: 92
* X: 36
* Bluesky: 36
* LinkedIn: 20 Total Engagements: 3,060
@ Bluesky analytics are still hard to get consistently without paying for a
separate service. We hope Buffer will add this reporting capability soon.
Website Analytics
697,752 visits, 697,676 unique visitors -4.5%
2 min 36s average visit duration -10.3%
59% visits have bounced (left the website after one page) -1.7%
3.9 actions (page views, downloads, outlinks, internal site searches) per
visit -31.6%
2,195,196 pageviews, 874,975 unique pageviews -39.2%
5 total searches on your website, 5 unique keywords -50%
147,943 downloads, 105,048 unique downloads -9.7%
342,359 outlinks, 170,211 unique outlinks -9.6%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Danny Angus]
General
=======
November's email updates surrounding DKIM and mailing lists have concluded
with no issues, paving the way for additional delivery improvements scheduled
for Q1 2026. These updates, which improve delivery to many large email
providers, were made possible by a collaboration between Security and Infra,
and greatly reduced technical debt and reliance on legacy customizations.
Staffing
========
Infra's new staffers join the on-call rotation!
MFA Efforts
===========
Authentik MFA work continues with the primary implementation, backups, and DR
policies essentially complete. The initial rollout will consist of a limited
beta test to evaluate the system's scaling under load, and to get feedback on
UI/UX; still on target for end-of-year.
Major Projects
==============
Ansible and Terraform are in the early phases of adoption within Infra, with a
goal of modernizing and improving configuration management and
infrastructure-as-code.
Matomo (analytics.apache.org) has been transitioned from a POC developed by
the Privacy team to an Infra-supported service.
-----------------------------------------
Attachment 5: Report from the VP of Tooling [Dave Fisher]
# Tooling
With help from many in amplifying our job search we found and contracted a
well qualified engineer. We also contracted a short term engineer. We remain
below the tooling staff budget.
## Apache Trusted Releases (ATR)
The Alpha 2 testers have found several bugs and edges which are repairing.
Our current development focus is on the following tasks.
1. Supporting PMC Alpha 2 testing with bug fixes and feature improvements
2. ASVS security review and necessary fixes
3. SBOM analysis and generation
4. Preparing policy discussions related to the ATR
The repository is open for contributions and we have had one succesful "drive
by" PR and a few bad ones. We are requiring that new contributers introduce
themselves on the dev mailing list. We have had commits contributed by nine
developers.
We plan to add re-platforming of projects.apache.org as part of our Release
Catalog in the Beta development plan.
## Board Agenda Tool (BAT)
The tool is now stable and nearly complete. There are some improvements
waiting for volunteer developer time.
Reporter integration needs to be done which will require careful planning for
re-platforming of reporter.apache.org. An additional volunteer here would be
helpful.
## Secretary's Workbench
It has become clear that we will need to wait a few more months until we can
focus on this task.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
Accepted cvent bid to switch to their call-for-presentation system for future
events, starting in 2026. As mentioned last month, we will now have one
unified system to handle sessions and registration, vs. two.
Continuing to explore potential venues in the EU and UK for Community Over Code EU
2026. Several bid requests sent to venues, bids are still coming in. Thanks go
to Mark Cox for being our diligent UK location scout!
Met with Danica Fine to discuss the possibility of co-locating a
datalake-oriented event with C/C EU. This seems to be firmly happening. Also
discussing the possibility of a streaming co-located event at the same
conference.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
None currently.
Monthly Meetings
================
Monthly Meetings on hold until another event comes up
TAC App
=======
TAC app is currently closed.
Future Events
=============
None currently.
Looked into Fodsem support. With no real budget left and time contstaints
it is looking unlikely we will support Fosdem again this year.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support.
Post surveys forBratislava, Hangzhou, Denver, Beijing and Minneapolis still to be done.
Mailing List Activity
======================
No activity this month.
Membership
==========
No changes to the Committee this month.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
EU - CRA/PLD: Some of the vertical standards are now becoming available. The
quality is generally not good (though not as worrisome as with the horizontal
standards) -- but that is more of an issue for our industry & our community.
As opposed to hampering us, as (potential) open source stewards.
Likewise - more implementation details and other guidance is becoming
available from the EU itself; with this nicely getting integrated into the ORC
work https://cra.orcwg.org/faq/official/ and with specific sections for SMEs
(https://digital-strategy.ec.europa.eu/en/policies/cra-msmes), open source
stewards and so on. No surprises there - but not very complete either. So the
ORC work needs to continue for quite a bit longer.
Finally - lots of events planned in the week before FOSDEM.
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
At the ECMA General Assembly on December 10th, the following TC54 standards
were ratified:
1. CycloneDX Bill of Materials Specification (2nd edition; ECMA-424)
https://ecma-international.org/publications-and-standards/standards/ecma-424/
This standard has also been submitted to ISO/IEC JTC1 for fast-track
standardization. CycloneDX, together with SPDX (ISO 5962), is directly
relevant to Apache Trusted Releases.
2. Package URL (PURL) Specification (ECMA-427)
https://ecma-international.org/publications-and-standards/standards/ecma-427/
This standard has likewise been submitted to ISO/IEC JTC1 for fast-track
standardization.
3. Common Lifecycle Enumeration (ECMA-428)
https://ecma-international.org/publications-and-standards/standards/ecma-428/
CLE forms the conceptual model for the Apache Trusted Release catalog:
https://github.com/apache/tooling-trusted-releases/issues/183
At the TC54 meeting on December 11th, the committee approved a change in
convenors for TC54-TG4 (OSS Sustainability). Steve Springett (ServiceNow)
stepped down and the role will now be jointly held by Chris de Almeida (IBM)
and myself on behalf of the ASF.
-----------------------------------------
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]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are flat at
24 issues compared to the last month.
The two subpoenas were dealt with. No further action is required on our part
at this point. Many thanks to Jude Smith for providing pro-bono help on this.
The discussion around Generative AI tools is going on on members@ and VP Legal
has provided a purely legal take on the concerns. The rest of the discussion
(that has nothing to do with legal) seems to still go on.
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
November
* Completed our DMARC assistance to Infra: the update version of ezmlm to
improve deliverability of emails on our lists has now been deployed. This
clears the way to doing what we can to expedite the rollout of MFA.
* Helped out with https://github.com/apache/infrastructure-actions for more
secure use of GitHub actions.
Stats for November 2025:
29 [license confusion]
27 [support request/question not security notification]
2 [report/question relating to dependencies]
Security reports: 85 (last months: 66, 103)
6 ['airflow', 'logging']
5 ['cloudstack', 'httpd', 'website or other infrastructure']
3 ['commons', 'cordova', 'seata', 'solr', 'tomcat']
2 ['amoro', 'doris', 'dubbo', 'fory', 'hertzbeat', 'hugegraph', 'maven',
'spark', 'tvm', 'zeppelin']
1 ['activemq', 'answer', 'burr', 'camel',
'cassandra', 'dolphinscheduler', 'iotdb', 'james', 'kafka', 'kyuubi', 'livy',
'ofbiz', 'openoffice', 'orc', 'ozone', 'superset', 'syncope', 'texera',
'tika', 'trafficserver', 'wayang', 'xmlgraphics', 'zookeeper']
In total, as of 1st December 2025, we're tracking 268 (last months: 244, 264)
open issues across 86 projects, median age 103 days (last months: 100, 71). 74
of those issues have CVE names assigned. 20 (last months: 23, 20) of these
issues, across 11 projects, are older than 365 days.
* 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-10-08)
* openoffice (Health amber): Several issues in OpenOffice are over 365 days
old. They are not severe enough to warrant stopping distribution of
OpenOffice. A recent release fixed the most severe and complex ones, making
space to now focus on the remaining issues. (Last update: 2025-11-12)
* thrift (Health amber): the PMC does not appear to have the bandwidth to
triage incoming reports in a timely fashion, or accept help with this. (Last
update: 2025-11-07)
* spark (Health amber): the project has a backlog of security reports to be
triaged (Last update: 2025-12-01)
-----------------------------------------
Attachment A: Report from the Apache Airavata Project [Suresh Marru]
## Description:
The mission of Apache Airavata is the creation and maintenance of software
related to executing and managing computational jobs on distributed computing
resources including local clusters, supercomputers, national grids, academic
and commercial clouds.
## Project Status:
Current project status: The project is healthy with activity in pull requests
and commits steady. Issues for the board: No issues to report.
## Membership Data:
Apache Airavata was founded 2012-09-18 (13 years ago)
There are currently 46 committers and 28 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 Yasith Jayawardana on 2025-04-06.
- No new committers. Last addition was Ganning Xu on 2025-04-09.
## Project Activity:
Pull requests and commits have focused on simplifying the project and
improving the usability of the software artifacts. With increased focus on
community building, we will next work on creating a repository of usage
examples and illustrating integration into downstream usecases.
## Community Health:
The contributors to projects outside the ASF context have received a US
National Science Foundation grant to support open-source ecosystems around the
topics Apache Airavata contributes to. Volunteer effort to the project will
help improve the documentation, clarify the scope of the project artifact, and
conduct outreach events.
-----------------------------------------
Attachment B: Report from the Apache Airflow Project [Bolke de Bruin]
## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines
## Project Status:
Current project status: Ongoing, very high activity
Issues for the board:
## Membership Data:
Apache Airflow was founded 2018-12-19 (7 years ago)
There are currently 74 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Vincent Beck was added to the PMC on 2025-10-02
- Wei Lee was added to the PMC on 2025-09-30
- Guan-Ming Chiu was added as committer on 2025-10-01
## Project Activity:
Apache Airflow is going through an intensive period of maturing 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 even more significant adoption among the users, as we are
getting much closer to parity with Airflow 2. The upcoming (next year) Airflow
3.2 is the release that is aimed to finally deliver full feature parity
(including SLA/Deadlines) and deliver the promise of completing task isolation
that should improve security and enterprise-readiness of Airflow -
specifically it will allow us to decrease the surface of Supply Chain
security problems that are currently on the raise.
We continue engaging our community with “proper” AI-driven contributions, we
do not complain, do not plan to ban AI contributions, we rather embrace them
by engaging the community into discussion on how to do the AI contributions
properly - teaching them about ASF policies, explaining our expectations and
providing better tooling and instructions to Agents to increase quality of AI
contributions (with quite a success, we are not suffering from excessive AI
slop, while it’s clear that a number of those contributions that are AI driven
is quite high.
We are currently completing a vote (which turns out to be a complete
consensus) about improving and perfecting our provider process. With almost
100 providers we are already one of the largest project when it comes to a
number of releases and artifacts we produce, but we see a demand and
expectation on even more and we decided to respond to the demand by improving
our process and opening up for more contribution there, while strengthening
our automation and involving stakeholders in maintenance process that is
aligned with Apache Way, leaving the PMC with full control, while shifting
maintenance responsibility to stakeholders interested in keeping the providers
they have stakes in. Initial ideas about this have been discussed with ASF
folks at Community Over Code in Minneapolis, getting their positive feedback -
we are the final stage of arriving at consensus on it and we hope we might set
some blueprints on how other ASF projects might do similar processes. More
details in [3].
Following lack of time and energy of long-time Release Manager for Providers
(who had done fantastic job for years and is still with us but with lower
capacity) we introduced rotation of Provider Release Management and formal
Release Plan where we attempt to stabilise our cadence of releases for
providers - also in anticipation of future needs resulting from the improved
provider governance process. We attempt to communicate it better to our users
and agree expectations for release cadence and the result of that experiment
will be used in other parts of the process.
We also closely work with the ASF Tooling team and we are part of the Alpha
tests of the ATR (Apache Trusted Releases) - we’ve already run a few of our
releases through the ATR platform and we continue raising issues and test
fixes. We are looking forward to the ATR platform going out of the testing
phase. We believe it will be a great way to improve our release process and
prepare for the increased release velocity and increase the number of
providers we will have to handle. The cooperation already led to improvements
in our release processes and tooling to be even more compliant with ASF
expectations - proving also that the ATR platform might be the key to
improving processes for other PMCs.
[3] https://lists.apache.org/thread/jqjd801g9161dqyv7l2xbsw0v7mp77z1
Recent releases:
* Provider packages 2025-12-01 was released on 2025-12-02 [ACCELERATED].
* Provider packages 2025-11-27 was released on 2025-11-27
* Apache Airflow Python Client 3.1.3 was released on 2025-11-25.
* Provider packages 2025-11-18 was released on 2025-11-19 [ACCELERATED]
* Provider packages 2025-11-14 was released on 2025-11-17.
* Apache Airflow 3.1.3 was released on 2025-11-14.
* Task SDK 1.1.3 was released on 2025-11-14.
* Apache Airflow Ctl 0.1.0 was released on 2025-11-11.
* Provider packages 2025-11-03 was released on 2025-11-08.
* Apache Airflow 3.1.2 was released on 2025-11-05.
* Task SDK 1.1.2 was released on 2025-11-05.
* Apache Airflow Python Client 3.1.0 was released on 2025-10-29.
* Apache Airflow 3.1.1 was released on 2025-10-27.
* Task SDK 1.1.1 was released on 2025-10-27.
* Provider packages 2025-10-22 was released on 2025-10-26.
* Provider packages 2025-10-04 was released on 2025-10-06 [ACCELERATED]
* Provider packages 2025-10-01 was released on 2025-10-04.
* Provider packages 2025-09-28 was released on 2025-09-29.[ACCELERATED]
* Provider packages 2025-09-25 was released on 2025-09-28.
* Apache Airflow 3.1.0 was released on 2025-09-25 [ACCELERATED]
* Task SDK 1.1.0 was released on 2025-09-25 [ACCELERATED]
* Provider packages 2025-09-18 was released on 2025-09-22.
Following the expectation of the board - we mark accelerated votes we did in
the past quarter - those are all technical RCN accelerated votes where we
found issues with RCN-1 and - following our agreed process - accelerated the
votes on distributions with incremental changes added - fixing only those
found issues.
## Community Health:
The community is healthier than ever. We have sustained the velocity of ~600
PRs merged a month (average ~20/day, 7 days/week !) and regularly more than
150 contributors contributing on a monthly basis. We have a significant influx
of new contributors - both inexperienced and seasoned ones and we are working
with them to make the best use of their energy - ranging from translating UI
to debugging low-level memory issues and improving our tooling to diagnose
them.
The 6th Airflow Summit in Seattle, US, was a success with attendance of 520+
attendees, around 170 speakers and 130 sessions over 3 days 7-9 October.
Followed by moderately successful Online Reconnect Summit in the week
following the in-person Summit. The organisers of the summit have some
learnings from both applied to next year’s planning - we have just got
approval and announced the next Airflow Summit that will be held in Austin,
TX, 31-Aug - 2 Sep 2026. We settled on it early and fast, in order to be able
to secure more sponsorship budget, as we know budgets for such events continue
to be tight.
We invited two PMC members and a committer, and we are already discussing
accepting 3 new committers and possibly 2 PMC members with an additional
number of contributors and committers identified as good candidates in the
near future.
-----------------------------------------
Attachment C: Report from the Apache Allura Project [Dave Brondsema]
## Description:
The mission of Apache Allura is the creation and maintenance of software
related to a software development infrastructure platform commonly known as a
"forge"
## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: none
## Membership Data:
Apache Allura was founded 2014-03-18 (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.14
- dropped support for Python 3.10
- option for email verification reminder
- update social network options
- python dependency upgrades
## Community Health:
- a few emails from new users, which we engaged with but nothing further (yet)
- one contribution from a non-committer
- development is slow, mostly in maintenance mode, but "active maintenance"
keeping up with new versions of things and improving security posture
-----------------------------------------
Attachment D: Report from the Apache Ambari Project [Brahma Reddy Battula]
-----------------------------------------
Attachment E: Report from the Apache Artemis Project [Christopher L. Shannon]
## Description:
The mission of Apache Artemis is the creation of a high-performance,
multi-protocol open source messaging platform designed to power modern
microservices and cloud-native applications.
## Project Status:
Current project status: New
Issues for the board: None
## Membership Data:
Apache Artemis was founded 2025-11-18 (20 days ago)
There are currently 64 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
The Artemis TLP membership is initially a full copy of the ActiveMQ TLP
with the same PMC members and committers so everyone retains the same rights
as before the split.
## Project Activity:
Apache Artemis was established 20 days ago after splitting out from Apache
ActiveMQ. Activity has thus far centered mostly on working with with Infra
to set up the new project resources, and then updating websites etc for both
Artemis and ActiveMQ accordingly as they became available.
- New mailing lists were established.
- A new website was established.
- Worked with the ASF M&P team who announced the new TLP.
- The git repositories have been renamed and moved to the Artemis TLP.
- The ARTEMIS Jira project was moved to the Artemis TLP.
- Emails such as commits/PRs/issues updates have been switched to the
appropriate new Artemis mailing lists.
- The ActiveMQ website has been updated to remove the Artemis content, with
a few small hints/notices left to aid users understand the change,
and redirects to the Artemis website for key Artemis content subtrees.
Business is continuing as usual as resources are being updated with aim
towards being able to do the first Apache Artemis releases soon.
## Community Health:
The community is healthy and there should be little impact to users as
everything transitions to the new TLP.
-----------------------------------------
Attachment F: 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.
- No new committers. Last addition was Disha Talreja on 2025-07-11.
## Project Activity:
- support for using RDBMS as backend for JanusGraph
- support for Trino metadata in Atlas
- enhancement to automatically purge deleted entities
- unit test coverage improvements
- UI improvements
- fixes in handling of concurrent import requests
- metrics updates to capture notification stats at topic-partition level
- dependent library updates: netty, axios, node-sass
## Community Health:
- dev@atlas.apache.org had a 13% increase in traffic in the past quarter (526
emails compared to 463)
- 66 JIRA tickets opened and 44 closed in the past quarter
- 41 commits in the past quarter (46 in the last report)
- 11 code contributors in the past quarter (15 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 G: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Membership Data:
Axis was created on 2001-01-19 (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:
As the Axis community acknowledges our 25th anniversary next month with new
releases planned for all 3 active projects to inspire keeping Axis around for
another 25 years, we are introducing new contemporary features in both Axis2/C
and Axis2/Java - while our active committer count of 5 for 2025 is a peak for
about the last decade.
In Axis2/C, we are now feature complete for a 2.0.0 release and the code in
git is in a review period for the truly revolutionary http/2 support intended
for JSON based REST web services, in the form of mod_axis2 that runs on Apache
httpd that can be built for either http 1.1 and SOAP or http/2 for JSON.
This http/2 support for JSON in Axis2/C was made possible by the
implementation that happened in Axis2/Java first using the Apache
HTTPComponents API, and was then ported to Axis2/C. The port required
significant more work but with the payoff of the expected huge performance
gains realized in every category, and the community growth potential in the
much larger Apache httpd install base.
Our volunteer community continued to support Rampart this past quarter, and
several Jira issues were opened concerning the user guide samples. This is
very difficult code to support that concerns old WS-Security standards - with
no committers who use it themselves. Nevertheless, we fixed the Jiras and a
2.0.0 release will be the last of the 3 projects in the schedule.
The full disclosure of the work this last quarter is that it marks the rapid
rise in AI tools such as Claude code in our day jobs that generously pay for
our time and want it to be productive, while the ICLA of the committers
demands the personal responsibility that passes the ASF review and due
diligence to support Axis releases.
The model for AI development that has been chosen for Axis for starters relies
heavily on markdown files that may not record every request but they can
record development state and decisions that arguably far exceeds any real time
model until now. It helps that our coding domain relies exclusively on Apache
licensed code and most deps are Apache projects.
These planned releases coincide with this quarterly report, and we invite all
eyes to review the Axis2/C markdown files - 8 of them which go into great
detail - in docs/*HTTP* and particularly docs/HTTP_LEGAL. The intent of these
docs is not just to teach AI tools about Axis, but verify this is not the
typical copy and paste code off of the internet but to show that experienced
developers can get the most out of their tools in legal ways, just like
always.
## Axis2/Java Jira issues opened in the last 90 days: 2
## Axis2/Java Jira issues closed in the last 90 days: 2
## Axis2/C Jira issues opened in the last 90 days: 2
## Axis2/C Jira issues closed in the last 90 days: 13
-----------------------------------------
Attachment H: Report from the Apache Beam Project [Kenneth Knowles]
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Masatake Iwasaki]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Bigtop was founded 2012-09-19 (13 years ago)
There are currently 46 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhiguo Wu on 2024-08-19.
- No new committers. Last addition was Liqiang Fu on 2025-05-13.
## Project Activity:
Recent releases: bigtop-manager-1.1.0 was released on 2025-12-04.
3.5.0 was released on 2025-09-07.
3.4.0 was released on 2025-05-30.
We are preparing for the next 3.6.0 release starting from upgrading
Hadoop to 3.4 or later[1].
we talked about Apache Airflow added to the stack in Bigtop 3.5.0.
[1] https://issues.apache.org/jira/browse/BIGTOP-4437
[2] https://airflowsummit.org/sessions/2025/airflow-bigtop-modernize-and-integrate-time-proven-oss-stack-with-apache-airflow/
## Community Health:
No committer/PMC member was added in the past quarter.
We had low activity in the past quarter:
dev@bigtop.apache.org had a 63% decrease in traffic in the past quarter(84
emails compared to 224):
issues@bigtop.apache.org had a 73% decrease in traffic in the past quarter(45
emails compared to 162):
While it would be nice to add more active contributors and committers, we can
still catch up with the products in the stack since the ecosystem of Apache
Hadoop on which the Apache Bigtop is based on is matured and follows a longer
release cadence.
-----------------------------------------
Attachment J: 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:
Project keeps receiving code contributions, mostly from committers, but we
also have a few users contributing smaller changes.
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:
Most of the conversations happen in Slack, both in the BookKeeper slack
workspace and in the Apache Pulsar slack workspace. Most of BookKeeper users
that interact with us come from Pulsar community at the moment, but BookKeeper
is still used by other projects, it is only that Pulsar community is pretty
vibrant and BookKeeper is a core piece of that project.
-----------------------------------------
Attachment K: Report from the Apache BuildStream Project [Tristan Van Berkom]
-----------------------------------------
Attachment L: Report from the Apache BVal Project [Matt Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache BVal was founded 2012-02-14 (14 years ago)
There are currently 17 committers and 15 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 Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Markus Jung on 2024-07-08.
## Project Activity:
Apache BVal has seen no activity during this quarter.
## Community Health:
As ever, this project continues to sit idle until a some deficiency presents in
the form of a defect or an updated specification.
-----------------------------------------
Attachment M: 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.10.7
- We released Camel 4.10.8
- We released Camel 4.14.1
- We released Camel 4.14.2
- We released Camel 4.15.0
- We released Camel 4.16.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 (EOL)
- The situation is really healthy and the community is increasing presence and
engagement. We are introducing many new features and components. Camel is
growing even in terms of interest and new contributors.
Apache Camel K:
- We released Camel K 2.8.0
- This release brings full support for the Camel 4.14.x LTS runtime.
- We focused heavily on operator stability and reducing the memory footprint
of the operator pod.
- The community has provided excellent feedback on the new trait
configurations introduced in the previous quarter.
- 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.
Apache Camel Kamelets:
- We released Camel Kamelets 4.10.7
- We released Camel Kamelets 4.14.1
- We released Camel Kamelets 4.14.2
- We released Camel Kamelets 4.15.0
- We released Camel Kamelets 4.16.0
- The Kamelet catalog keep growing
- Documentation has been improved more.
- 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
Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
multiple releases
- We released Camel-quarkus 3.27.0
- We released Camel-quarkus 3.27.1
- We released Camel-quarkus 3.29.0
- We released Camel-quarkus 3.30.0
- We are increasing the number of Camel Quarkus Extension to match the core
components.
- The community is active and we are seeing increased interest.
Apache Camel-Karavan:
- Camel-Karavan is still growing.
- The 4.10.x is aligned to Camel 4.10.x LTS
- We released version 4.14.2, supporting the latest LTS release.
Camel-Kafka-Connector:
- 4.14.0 have been released and based on the LTS version 4.14.0
- The community is active and we receive a lot of feedback and requests. We
are improving the documentation and we're trying to keep the same cadence as
core.
- The project is slowing down a bit for the lack of developers working on it,
but we are keeping the updates aligned.
Apache Camel-Karaf:
- Camel-karaf 4.10.7 has been released.
- It's a patch version supporting LTS 4.10.x
- The plan is to support 4.14.x LTS in the next period.
Apache Camel-Upgrade-Recipes:
- Camel-Upgrade-Recipes 4.14.0 has been released
- Camel-Upgrade-Recipes 4.14.0.1 has been released
- Camel-Upgrade-Recipes 4.15.0 has been released
- Camel-Upgrade-Recipes 4.16.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 increased in usage in this quarter, this
is mainly because we revived some discussion we had about future developments
and what to do with new releases.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. I think the community is really growing.
-----------------------------------------
Attachment N: Report from the Apache CarbonData Project [Jacky Li]
-----------------------------------------
Attachment O: Report from the Apache Cayenne Project [Michael Gentry]
# Apache Cayenne Board Report, December 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.3 (a maintenance/bug-fix release) was released in November.
Release notes: https://cayenne.apache.org/2025/11/cayenne-423-released/
### Releases
- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2.3 on 2025-11-19.
- Cayenne 5.0.M1 on 2024-09-09.
## Community Health
Cayenne is healthy.
User mailing list traffic increased substantially due to several users
migrating from legacy versions of Cayenne or from other ORMs and needing
assistance with their migrations and Cayenne features.
Developer mailing list traffic also increased as the 4.2.3 maintenance
release was being prepared, voted on, etc. Jira and Git traffic likewise
saw an increase in traffic as a result of the release.
Code commits were for the 5.0.x and 4.2.3 branches.
-----------------------------------------
Attachment P: Report from the Apache Celeborn Project [Keyong Zhou]
## Description:
The mission of Apache Celeborn is the creation and maintenance of software
related to an intermediate data service for big data computing engines to
boost performance, stability, and flexibility
## Project Status:
Current project status: Ongoing Issues for the board: None
## Membership Data:
Apache Celeborn was founded 2024-03-20 (2 years ago). There are currently 26
committers and 16 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Fei Wang on 2024-12-31.
- No new committers. Last addition was Zhentao Shuai on 2025-07-07.
## Project Activity:
Software development activity:
- Release 0.6.1 is released on 10 September.
- Release 0.6.2 is under discussion.
- CIP-13 Support auto scaling is under development.
- CIP-14 Support cpp client for shuffle write is under development.
- CIP-16 Merge transport and resource proto files is finished.
- CIP-17 Interruption Aware Slot Selection is finished.
- CIP-18 Support read skew partition is finished.
- CIP-19 Support app priority is under development.
- CIP-21 Support Flink JM failover is under discussion.
Meetups and Conferences:
- 1 talk was given in CoC NA 2025.
Recent releases:
- Release 0.6.1 is released on 10 September.
## Community Health:
Overall community health is good. In the past quarter, the dev mail list mail
number had a 15% decrease in the past quarter to 54. The issues mail list had
a 28% decrease to 745. 91 JIRA tickets opened and 69 closed in the past
quarter. The PMC considered it as normal because the absolute number is
relatively high. We have been performing extensive outreach for our users, and
encouraging them to contribute back to the project. Also, we are active in
making a voice in various conferences to attract more users.
-----------------------------------------
Attachment Q: Report from the Apache CloudStack Project [Nicolás Vázquez]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage, and
networking devices.
## Project Status:
Current project status: Ongoing, with high activity
Issues for the board: None
## Membership Data:
Apache CloudStack was founded 2013-03-19 (13 years ago) There are currently
143 committers and 61 PMC members in this project. The Committer-to-PMC ratio
is roughly 9:4.
Community changes, past quarter:
- Vishesh Jindal was added to the PMC on 2025-11-04
- No new committers. Last addition was Jamie Pell on
2025-07-23.
## Project Activity:
Software development/management activity:
- The current version of Apache CloudStack is 4.22.0.0.
- The versions released in the past quarter are:
- 4.22.0.0 was released on 2025-11-11.
- 4.20.2.0 was released on 2025-10-27.
- The latest CloudStack Go SDK v2.19.0 (with support of 4.22.0 APIs) was
released on November 28, 2025.
- The latest CloudStack Terraform provider version 0.6.0 was released on
October 28, 2025.
Meetups and Conferences:
- The CloudStack Collaboration Conference 2025 was held on November 19-21 in
Milan, Italy.
- A CloudStack European User Group is being planned to be held in the
Netherlands in May 2026; the dates are not confirmed yet.
- We start planning the CloudStack Collaboration Conference 2026 in Edinburgh,
Scotland: https://www.cloudstackcollab.org/.
## Community Health:
- According to the reporter tool, the Community Health Score (Chi) is
9.60 (Super Healthy).
Mailing lists statistics:
- dev@cloudstack.apache.org had a 1% decrease in traffic in the past quarter
(987 emails compared to 996)
- issues@cloudstack.apache.org had a 1% increase in traffic in the past
quarter (96 emails compared to 95)
- marketing@cloudstack.apache.org had a 24% decrease in traffic in the past
quarter (20 emails compared to 26)
- users@cloudstack.apache.org had a 27% increase in traffic in the past
quarter (1712 emails compared to 1344)
Recent Releases:
- 4.22.0.0 was released on 2025-11-11.
- 4.20.2.0 was released on 2025-10-27.
- 4.21.0.0 was released on 2025-08-28.
-----------------------------------------
Attachment R: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java-focused
reusable libraries and components.
## 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 44 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Arnout Engelen on 2024-12-22.
- No new committers. Last addition was Arnout Engelen on 2024-12-23.
## Project Activity:
We are releasing components regularly. The reporting period was the following
component releases:
- POOL-2.13.0 was released on 2025-12-09.
- TEXT-1.15.0 was released on 2025-12-07.
- EXEC-1.6.0 was released on 2025-12-02.
- DAEMON-1.5.0 was released on 2025-11-28.
- CONFIGURATION-2.13.0 was released on 2025-11-26.
- PARENT-93 was released on 2025-11-22.
- VALIDATOR-1.10.1 was released on 2025-11-17.
- LANG-3.20.0 was released on 2025-11-16.
- JEXL-3.6.0 was released on 2025-11-14.
- CLI-1.11.0 was released on 2025-11-12.
- PARENT-92 was released on 2025-11-10.
- IO-2.21.0 was released on 2025-11-06.
- CODEC-1.20.0 was released on 2025-11-05.
- PARENT-91 was released on 2025-10-30.
- PARENT-90 was released on 2025-10-21.
- BCEL-6.11.0 was released on 2025-10-13.
- PARENT-89 was released on 2025-10-08.
- LANG-3.19.0 was released on 2025-09-24.
- PARENT-88 was released on 2025-09-19.
- STATISTICS-1.2 was released on 2025-09-17.
## Community Health:
The community is doing well. We have activity on all mailing lists and
GitHub with a steady flow of pull requests on GitHub for everything from
documentation nits, bug fixes, and new features. We are also responding to our
security mailing list for reports and queries on vulnerabilities.
-----------------------------------------
Attachment S: Report from the Apache Cordova Project [Bryan Ellis]
## Status report for the Apache Cordova project - December 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 https://apache.github.io/cordova-status/ 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:**
- No new PMC members. Last addition was Manuel Beck on 2025-04-04.
- No new committers. Last addition was Manuel Beck on 2025-04-04.
## Project Activity
The following releases to our project this quarter focused on the Cordova-iOS
platform, the CLI, and internal libraries.
**Releases:**
- cordova-cli@13.0.0 was released on 2025-11-25.
- cordova-ios@8.0.0 was released on 2025-11-23.
- cordova-lib@13.0.0 was released on 2025-11-05.
- cordova-create@6.0.0 was released on 2025-10-22.
## Community Health
Overall, the community health is strong. The ASF Project Statistics gives the
project a Community Health Score (Chi): 6.33 (Healthy)
This quarter, we primarily focused on improving and releasing internal
packages used by the CLI. These packages form part of the CLI's dependency
tree. This work continued from the previous quarter, with the goal of
delivering the next major CLI release within this timeframe, which we
successfully achieved.
Additionally, we finalized and released the next major version of Cordova-iOS:
8.0.0.
We continue to see valuable contributions from a group of dedicated
individuals who actively test, report issues, and submit PRs to address their
findings for future releases.
Recent discussion threads have been opened, showing interest in improving the
project's current release process by introducing some level of automation and
adopting the new Apache Trusted Release process. There is also interest in
finding ways to refactor and improve documentation and plugin testing.
Overall, the project remains stable and continues to see strong activity.
Github discussions is how our community supports each other and is live at
https://github.com/apache/cordova/discussions. All discussions are forwarded
to the 'issues' list.
## Mailing List Activity
- dev@cordova.apache.org had a 29% increase in traffic in the past quarter
(57 emails compared to 44)
- issues@cordova.apache.org had a 20% decrease in traffic in the past quarter
(857 emails compared to 1064)
-----------------------------------------
Attachment T: 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 (13 years ago)
There are currently 40 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- 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:
There were some new user questions asked directly on GitHub rather than usual
dev@ mailing lists. For example: https://github.com/apache/ctakes/issues/74
Mailing lists have been fairly quiet this quarter.
dev@ctakes.apache.org had a 100% decrease in traffic in the past quarter
(0 emails compared to 1)
-----------------------------------------
Attachment U: Report from the Apache Curator Project [Enrico Olivelli]
## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier
## 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:
We have a bunch on commits on the repository, just minor improvements and
fixes. This is kind of expected as the project is pretty stable and we don't
have big features planned ahead.
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:
We don't have much activity in the Community, but we have been to cut a
release in July (past quarter). Nothing to worry about, it is about the nature
of the project. Curator is still widely used, but it is stable.
It would be great to involve new people but there is nobody in the community
that is actually spending time to do that.
-----------------------------------------
Attachment V: 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:
With the release of Daffodil 4.0.0 we are finally past the evolution of our
code base to Scala 3.
As of this writing the Daffodil VSCode extension v1.5.0 release is out for an
RC1 vote, so there is significant progress there also as there is toward a
v4.1.0 of the primary daffodil library.
In addition, DFDL training and best-practices content has been added to
the Daffodil project web site.
## Community Health:
We still have a good activity level in developer email and commit activity.
User list activity is low, but not non-existent. The cybersecurity community,
which is the major user community for Daffodil, is notoriously silent about
usage.
We have recently had some interest from new contributors, and some
contributors to the VSCode extension sub-project have become much
more active.
-----------------------------------------
Attachment W: Report from the Apache DataFusion Project [Andrew Lamb]
## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine
## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache DataFusion was founded 2024-04-16 (2 years ago)
There are currently 54 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Jeffrey Vo was added to the PMC on 2025-11-23
- Yongting You was added to the PMC on 2025-11-23
- Gabriel Musat was added as committer on 2025-10-31
- Raz Luvaton was added as committer on 2025-10-01
- Zhen Wang was added as committer on 2025-10-02
- Yoav Cohen was added as committer on 2025-09-17
## 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
- 51.0.0 was released on 2025-11-19.
- 50.3.0 was released on 2025-10-24.
- 50.1.0 was released on 2025-10-02.
- 50.0.0 was released on 2025-09-16.
The most recent release (~ 2 months of contributions) had 128 distinct
contributors, which we think is a record and shows the project is able to
attract and sustain a large community. Development is now largely focused on
more advanced optimizations, and we have been able to attract a significant
amount of engineering investment from the community
We have gotten better about writing about our releases externally, including
several blogs:
https://datafusion.apache.org/blog/2025/11/25/datafusion-51.0.0
https://datafusion.apache.org/blog/2025/09/29/datafusion-50.0.0
https://datafusion.apache.org/blog/2025/09/21/custom-types-using-metadata
https://datafusion.apache.org/blog/2025/09/10/dynamic-filters
We have also held several in person meetups in various locations, which have
been successful in bringing together contributors.
Finally, as always, the biggest bottleneck for increasing project velocity is
reviewer capacity. The rise of AI powered coding assistants has made this
bottleneck more acute as it makes it easier to create large PRs. The community
has written up [guidelines] for AI assisted contributions which seems to have
improved the overall PR quality.
[guidelines]: https://datafusion.apache.org/
contributor-guide/index.html#ai-assisted-contributions
### Sub project: DataFusion Python
https://github.com/apache/datafusion-python
- DATAFUSION-PYTHON-50.1.0 was released on 2025-10-20.
- DATAFUSION-PYTHON-50.0.0 was released on 2025-09-23.
The DataFusion Python project has mostly focused on quality of life
improvements, including adding support for SQL expressions within DataFrame
operations. We have seen a slight increase in issues reported lately,
demonstrating growth in the user community.
### Sub project: DataFusion Comet
https://github.com/apache/datafusion-comet
- COMET-0.12.0 was released on 2025-12-01.
- COMET-0.11.0 was released on 2025-10-16.
- COMET-0.10.0 was released on 2025-09-16.
You can read about the recent happenings in Comet in the blogs:
https://datafusion.apache.org/blog/2025/12/04/datafusion-comet-0.12.0
https://datafusion.apache.org/blog/2025/10/21/datafusion-comet-0.11.0
https://datafusion.apache.org/blog/2025/09/16/datafusion-comet-0.10.0
### Sub project: DataFusion Ballista
https://github.com/apache/datafusion-ballista
- BALLISTA-50.0.0 was released on 2025-11-22.
- BALLISTA-49.0.0 was released on 2025-10-06.
### Sub project: sqlparser-rs
https://github.com/apache/datafusion-sqlparser-rs
- SQLPARSER-0.59.0 was released on 2025-09-24.
- SQLPARSER-0.60.0 was released on 2025-12-07.
Ifeanyi Ubah (iffyio) continues to review most PRs in this repo. We added a
new committer Yoav Cohen focused on sqlparser in an attempt to increase the
review bandwidth available.
## 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 X: Report from the Apache DevLake Project [Hezheng Yin]
Apache DevLake — Board Report (Month 3 as Top-Level Project)
Reporting period: October 2025 - November 2025
Submitted by: Richard Boisvert (Apache DevLake)
- Project description
Apache DevLake is an open-source DevData platform that collects,
transforms,
and visualizes engineering and DevOps data from sources like GitHub,
Jenkins,
and Jira to help teams understand and improve their software delivery
performance through metrics and dashboards.
- Project status
Status: Ongoing / Growth phase
DevLake continues to mature as a Top-Level Project. This reporting period
saw
significant plugin development with two new integrations and ongoing
improvements to existing connectors.
- Community and project activity
Released v1.0.3-beta7 (October 20, 2025) and v1.0.3-beta8 (November 7,
2025).
7 contributors active during this period with 10 commits merged including
new
features and bug fixes.
Key developments: Initial implementation of ArgoCD plugin with image
extraction
and revision tracking (issue #5207, #8630). Amazon Q Developer
integration with
DORA metrics dashboard. Bitbucket API token authentication support (issue
#8520). Bug fixes for GitHub GraphQL pagination (issue #8615).
- Releases
v1.0.3-beta7 — Released October 20, 2025
v1.0.3-beta8 — Released November 7, 2025
- Issues for the Board
No critical Board-level issues at this time.
- Community health
Active committers this period: ~10 New committers: None this period New
PMC
members: None this period Mailing list traffic: lighter than usual as
contributors focus on planning No major conflicts or community issues
reported
- Roadmap / upcoming work
Plugin ecosystem expansion — Continue ArgoCD development (issue #5207),
add
Azure DevOps on-prem support (issue #7115), and improve GitHub Apps
refresh
token handling (issue #8532). Metrics accuracy improvements — Add bot
account
exclusion for accurate contributor metrics (issue #8646) and support
CANCELLED
as a pipeline result (issue #8570). Config UI enhancements — Add UI for
custom
column management (issue #8643) and regex validation for GitLab
deployments
(issue #8641). Documentation & community growth — Fix broken Slack invite
links (issue #8591).
- Additional commentary
We anticipate renewed momentum heading into 2026 with several integration
in progress.
-----------------------------------------
Attachment Y: Report from the Apache Dubbo Project [Jun Liu]
-----------------------------------------
Attachment Z: 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 31 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was ShiZhao Pan on 2025-01-09.
- Zisen Jin was added as committer on 2025-11-01
## Project Activity:
We released our major version 6.0.0 on July 30, 2025. Currently, we are testing
the next iteration, version 6.0.1, which is scheduled for release in the coming
weeks. The project is now in a phase of moderate-paced development, primarily
focused on integrating and reviewing pull requests from our community
contributors.
## Community Health:
Following the well-received launch of Apache ECharts 6.0 with its twelve
significant features, our community remains energized. Development continues
at a steady pace, sustained by the valuable contributions from our members.
This collective momentum is actively strengthening the project, and we invite
everyone to join in shaping its future.
-----------------------------------------
Attachment AA: 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 (19 years ago)
There are currently 68 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Paul Rütter on 2025-06-16.
- No new committers. Last addition was Paul Rütter on 2024-11-15.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- Released 3 components. Mostly bug fixes/minor improvements.
### Releases
- org.apache.felix.http.jetty12-1.1.6 was released on 2025-11-27.
- org.apache.felix.http.jetty12-1.1.4 was released on 2025-10-13.
- org.apache.felix.http.jetty12-1.1.2 was released on 2025-09-23.
- org.apache.felix.webconsole-5.0.18 was released on 2025-09-22.
## Community Health:
- Overall the project is in ok health with very little ongoing activity.
- The community activity remains on a low level and we continue to see little
new development right now.
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues. Traffic has
been very low.
- We had no issues voting on releases and JIRA issues are generally addressed.
-----------------------------------------
Attachment AB: 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: Stable 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 work done recently by one PMC member to update documentation which
used to be hosted by Adobe.
## Community Health:
There has been a few emails to the lists. Although it's been quiet there is
still enough PMC to handle anything which comes up.
-----------------------------------------
Attachment AC: 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 123 committers and 55 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was liu ron on 2025-08-13.
- Hongshun Wang was added as committer on 2025-11-28
- Yunfeng Zhou was added as committer on 2025-11-28
## Project Activity:
Recent releases:
* agents-0.1.1 was released on 2025-12-09.
* 2.2.0 was released on 2025-12-04.
* 2.0.1 was released on 2025-11-10.
* 2.1.1 was released on 2025-11-10.
* agents-0.1.0 was released on 2025-10-15.
* 1.20.3 was released on 2025-10-09.
* cdc-3.5.0 was released on 2025-09-26.
Flink 2.2 is a big Flink release with features around connecting to LLMs
from Flink SQL as well as other SQL improvements such as vector
search, materialized table improvements and SQL performance improvements.
There are also runtime and connector framework improvements.
## Community Health:
The mailing list activity remains the the same on the dev list remains roughly
the same.
There is an ongoing discussion in the PMC around the health of Flink connectors,
which are not receiving sufficient attention from committers for
merging PRs, updating them to be compatible with recent Flink versions
as well as releasing them.
-----------------------------------------
Attachment AD: Report from the Apache Gobblin Project [Abhishek Tiwari]
## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Gobblin was founded 2021-01-19 (5 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was Abhishek Mahendra Jain on 2025-01-18.
## Project Activity:
- Added certificate-based authentication support in MySQL shared-Gobblin
modules.
- Enhanced commit policies by enabling partial commits only when explicitly
configured.
- Introduced PushMessagesSync API to support synchronous GTE emission.
- Improved Apache Iceberg-based ingestion:
- - Added pre-publish steps for IcebergSource
- - Added partition-aware extractors for Iceberg file copy
- - Enabled schema evolution for partition copies
- - Enabled constructing Iceberg data files during commit for efficiency
- - Removed unsupported cipher suites from default SSL settings.
- Made AvroUtils compatible with Avro 1.10 to ensure broader schema
interoperability.
- Cleaned up stats by removing dataset-URN-specific properties.
- Fixed multiple file-system permission/ACL consistency issues for paths that
already exist at the destination.
- Added ability to access the datastate store during work discovery.
- Emitted job-level metrics at RM level for improved observability.
- Made DAG action/spec store monitor initialization configuration-driven.
- Rewrote and optimized WorkUnit serialization, including introducing random
IDs when recovery helper is not initialized.
- Last Release date: 30th August, 2023.
## Community Health:
- Since Sep 2025, there have been 19 commits - 13 were from relatively new,
non-committer contributors.
- Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as committers.
We constantly look for consistent contributors to vote them in as
Committers.
-----------------------------------------
Attachment AE: Report from the Apache Grails Project [James Fredley]
## Description:
The mission of Apache Grails is the creation and maintenance of software
related to the development of a powerful Groovy-based full-stack web
application framework for the JVM built on top of Spring Boot
## Project Status:
Current project status: Ongoing With high activity
Issues for the board: No issues requiring board attention at this time.
## Membership Data:
Apache Grails was founded 2025-09-23 (2 months ago)
There are currently 16 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
No new PMC members (project graduated
recently). Walter Duque de Estrada added 8/25/2025
Committers: Thomas Rasmussen added 8/25/2025, Jonas Pammer added 9/4/2025
## Project Activity:
Recent releases:
CORE-7.0.4 was released on 2025-12-01.
GRAILS-PUBLISH-0.0.3 was released on 2025-12-01.
CORE-7.0.3 was released on 2025-11-23.
## Community Health:
Overall, community activity has increased this quarter. The project has
generated significant buzz around graduation and five 7.0.x releases with many
end users submitting issues and pull requests, as they upgrade.
The project has held weekly planning meetings via Google Meet for 18 months
and they continue to provide an effective communication path to move the
project forward.
dev@grails.apache.org had a 31% increase in traffic in the past quarter (342
emails compared to 261)
-----------------------------------------
Attachment AF: 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: Ongoing - high Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-21 (7 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.
- No new committers. Last addition was Abyss-lord on 2025-07-07.
## Project Activity:
Software Development Progress:
1. Apache Gravitino 1.0.0 released on Sep 30, 2025.
2. Apache Gravitino 1.0.1 released on Nov 19, 2025.
3. We're under the release of the Apache Gravitino 1.1.0.
4. Next release milestone has settled.
Community activities:
1. QCon Shanghai Apache Gravitino.
2. Data for AI meetup (Bay Area) Apache Gravitino talk.
3. COSCon Beijing Apache Gravitino talk.
4. Data for AI meetup (Shanghai) Apache Gravitino talk.
## Community Health:
1. dev@gravitino.apache.org had a 5% increase in traffic in the past quarter
(139 emails compared to 132)
2. 348 issues were created in the last 90 days. 355 issues have closed in the
last 90 days. 544 PRs have been created in the last 90 days. 539 PR has
been merged in the last 90 days. Both the issues and PRs show the high
activity of the community.
3. 2 committer candidates nomination process is undergoing.
-----------------------------------------
Attachment AG: 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.1 release seems near an RC (pending resolution of outstanding bugs),
though velocity has slowed somewhat. Current project activity is focused on
this release.
- 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 is active and healthy. New users posting to the mailing lists
are engaged by established community members, and there is notable interest in
a 1.6.1 bugfix release.
-----------------------------------------
Attachment AH: Report from the Apache Gump Project [Stefan Bodewig]
-----------------------------------------
Attachment AI: 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: Low, Ongoing
Issues for the board: N/A
## Membership Data:
Apache Helix was founded 2013-12-17 (12 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- No new committers. Last addition was Molly Gao on 2023-06-06.
## Project Activity:
- 1.3.2 was released on 2025-08-29
- 1.4.3 was released on 2025-02-04
- 1.4.2 was released on 2024-12-07
## Community Health:
- The Apache Helix Gateway Service has been tested and merged
into the main branch. It is language-agnostic and serves as a
modern sharding solution for containerized environments. Documentation
and tutorials are in progress.
- The Apache 2.0 release is targeted for the first quarter of 2026.
This release will include major gateway features and the removal of
several deprecated components.
- With many major contributors on holiday, development velocity has
slowed.
- Additionally, most new contributors are coming from the same company.
Apache Helix PMCs and Committers are working to maintain feature quality,
as some recent check-ins have introduced issues and did not adhere to
coding standards.
-----------------------------------------
Attachment AJ: Report from the Apache Hive Project [Naveen Gangam]
## Description:
The Apache Hive™ data warehouse software facilitates reading, writing, and
managing large datasets residing in distributed storage (Apache Hadoop) using
SQL.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hive was founded 2010-09-21 (15 years ago)
There are currently 112 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Dmitriy Fingerman was added to the PMC on 2025-12-01
- Shohei Okumiya was added to the PMC on 2025-12-07
- No new committers. Last addition was Seonggon Namgung on 2025-07-15.
## Project Activity:
Apache Hive 4.2.0 was released on 2025-11-23. This release comes in less than
4 months after Apache Hive 4.1.0 was released on 2025-08-02, bringing in about
187 new commits includes features like:
* JDK 21 support
* Enhanced Iceberg Table support (deletion vectors, auto compaction,
ViewCatalog, column defaults, Z-ordering variant-type)
* Optional Iceberg REST Catalog service for iceberg clients
* Support for multiple partitions in RELOAD event, support for drop partitions
by names
* Separation of metastore client code into a module
* This release works with Hadoop 3.4.1, Tez 0.10.5
## Community Health:
The community is super healthy (9.60).
There has been a 53% decrease in the activity of the dev list compared to the
previous quarter but consistent with the quarters prior. Last quarter was an
anomaly due the release related activity. Gitbox activity has decreased by 33%
from last quarter and is consistent with the prior quarters before. 18%
decrease in issues which is good. Overall healthy development and release
activity in the Apache Hive community.
-----------------------------------------
Attachment AK: Report from the Apache Hop Project [Hans Van Akelyen]
## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hop was founded 2021-12-15 (4 years ago)
There are currently 24 committers and 10 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 Bart Maertens on 2021-12-15.
- No new committers. Last addition was Sergio De Lorenzis on 2024-06-11.
## Project Activity:
We had a new release in November. We are mainly working on UI improvements,
code hardening and bug fixing.
## Community Health:
The growth in community activity that we saw earlier appears to be continuing.
New contributors have shown up, are sticking around and remain active. The
process has not started yet but we would like to start onboarding some of them
and give the committer status. Our last release had contributions by 22
contributors, of which 8 were first time contributors. This is even higher
than the previous release, which already was the highest we had seen.
-----------------------------------------
Attachment AL: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hudi was founded 2020-05-19 (6 years ago)
There are currently 41 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Yue Zhang on 2025-06-30.
- Tim Brown was added as committer on 2025-11-26
## Project Activity:
The community has been actively working on Hudi 1.1, which was released in
November. The release focused on key code path refactoring, performance
improvements, adding and updating ecosystem integrations, and laying a solid
foundation for building new features. In parallel, the community is also
preparing patch releases 1.1.1, 1.0.3, 0.15.1, and 0.14.2 for bug
fixes and stability improvements. The community is also working on Hudi-rs
0.5.0, aiming to add support for new Hudi table versions and metadata table.
## Community Health:
We continue to see steady growth in community engagement on GitHub, with
active participation in GitHub discussions, code contributions, and weekly dev
sync meetings. The community has voted on decisions such as dropping Java 8,
moving to Java 11, and declaring end-of-life for old releases. The community has
imported all open JIRA issues to GitHub for easier project management, and
polished up the overall website design for better visual appearance and
organization.
-----------------------------------------
Attachment AM: Report from the Apache Iceberg Project [Ryan Blue]
## Description:
Apache Iceberg is a table format for huge analytic datasets that is designed
for high performance and ease of use.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Iceberg was founded 2020-05-19 (6 years ago)
There are currently 36 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Kevin Liu was added to the PMC on 2025-11-16
- Matthew Topol was added to the PMC on 2025-11-23
- Gang Wu was added as committer on 2025-10-15
## Project Activity:
Releases:
- Go 0.4.0 was released on 2025-10-13.
- Rust 0.7.0 was released on 2025-10-11.
Project:
- Separated CI emails to a new ci-jobs ML
- Removed blogs/ and talks/ pages from the site
- Added ASF-approved web analytics
- Added markdown and yaml lint checks
REST catalog spec:
- Added min-rows-requested to server-side planning
- Added storage credentials to server-side planning
- Added idempotency tokens to the spec
- Discussing adding etags to responses
UDF spec is nearing completion, added null handling and has settled on structure
Java:
- File format API reviews are ongoing; close to completion
- Merged encryption integration and tests for Hive catalog
- Flink: Added write support for v3 DVs
- Added support for custom internal types with Parquet files
- Added BigQuery catalog support to to runtime Jars
PyIceberg:
- Removed Python 3.9 support
- Added support for v3 row lineage
- Added expression serialization
- Improvements to CI and build
Rust:
- Added support for v3 metadata
- Added update_table for MemoryCatalog and GlueCatalog
- Introduced catalog loader for multiple catalogs.
- Added PartitionSplitter, RollingFileWriter, and partition-aware locations.
- DataFusion: Added write and commit execution plans enabling INSERT INTO.
- Added support for loading equality deletes during scans.
- DataFusion v48 support.
Go:
- Improvements to unit tests and docker images for testing configurations
- Fixing a crash when writing a map column with multiple entries per row
- Several improvements to the release scripts
- Support for writing to a Partitioned Iceberg tables!
- Initial support for v3 metadata
- Implemented the views spec
- Added schema evolution support and timestamp(9)
C++:
- Can write Avro metadata files
- Added REST request/response models
- Implemented TableMetadataBuilder
- Added scaffolding for expressions
- Added binary literal serialization
## Community Health:
We are happy to welcome Gang as a new committer and Matt Topol and Kevin Liu as
new PMC members!
The Iceberg PMC has encouraged community-driven meetups by providing guidelines
for meetup organizers. This has been very successful and there have been meetups
in many different locations: Amsterdam, Bangalore, Paris, Warsaw, Budapest,
Pittsburgh, Hamburg, Goteborg, Munich, Atlanta, Seattle, London, North Carolina,
and Menlo Park. The community has also worked to improve these guidelines and
ensure that they are small events that do not conflict with ASF events, since
there was an event almost too large near Community over Code.
-----------------------------------------
Attachment AN: Report from the Apache Ignite Project [Dmitry Pavlov]
## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Ignite was founded 2015-08-19 (10 years ago)
There are currently 80 committers and 41 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 Maksim Timonin on 2025-05-14.
- Stanislav Lukyanov was added as committer on 2025-11-17
## Project Activity:
Apache Ignite 3x:
- 3.1.0 was released on 2025-10-29.
-- The release brings improvements in stability, observability and correctness
across the storage and SQL engines, Raft-based replication, and
transactions.
-- Also introduces data-migration tooling from Ignite 2 to Ignite 3.
Apache Ignite 2x:
- No recent releases; the previous version was 2.17.0 on 2025-02-13.
-- Nodes with persistence can now use multiple disks, increasing throughput by
removing the I/O bottleneck. Smaller clusters can handle the same load.
-- The community has resumed testing compatibility with Java 21
-- Community members are refactoring internal messaging protocols.
-- Several improvements for multi-datacenter deployments are in progress for
the upcoming Ignite 2.18 release.
## Community Health:
- User list discussions decreased slightly. Development and issue-tracking
activity roughly doubled, and notifications increased by about a third.
- Discussions are focused on recent releases and optimizations for
multi-datacenter deployments.
- Massive refactoring in the 2.x core has introduced some newbie issues which
also makes it easier for newcomers to start contributing.
-----------------------------------------
Attachment AO: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for December 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 November, there are 29 podlings under incubation. Three releases were
made during the month, and three IP clearances were completed. One podling,
Apache Wayang, graduated during the month, and no podlings retired. There
were no additions to IPMC membership, and one person stepped down.
Mailing list traffic in November covered the usual Incubator topics,
including release votes, graduation, IP clearance, and incubation
governance and mentor practices.
A discussion was held on how podlings can use existing tooling and
automation to validate releases. It was noted that there has been a shift
from release issues that these tools can detect toward issues that require
greater human judgment and review.
A new public Mentor attribution page was created, listing mentors and the
podlings they have supported over time. This improves transparency and
recognition of mentoring contributions, provides an additional oversight
signal for identifying mentor load, and assists the IPMC in selecting
mentors for new incubation projects.
The Incubator Training Hub and wiki were expanded with additional materials.
New Incubator guides include:
- Neutrality in Practice: a practical guide on maintaining neutrality in
projects.
- Mentor Engagement Patterns: examines how mentoring impacts podling
health, independence, and graduation.
- Mentor Trends: reviews long-term changes in podling challenges and mentor
focus areas.
- Mentor Replacement: guidance on how and when to replace mentors.
- Select Your Mentors: guidance on how to select mentors for a podling.
New Incubator case studies:
- Incubator Health: a review of the Incubator over 20 years.
- 10 Years of the Incubator: a detailed look at the last decade.
- IPMC Governance: analysis of participation, continuity, and how
governance capacity rises and falls with podling load.
- Governance Patterns: a broader view of governance patterns in the
Incubator.
- Podling Governance Patterns: how podlings develop governance practices
during incubation.
- Community and Governance Growth: analysis based on data from more than
100 podlings.
- Incubator Discussion Trends: analysis of 10 years of Incubator
discussions.
This detailed analysis of 20 years of Incubator data, covering governance
threads, release votes, subject-line activity, podling population records,
and contributor participation, shows consistent long-term improvement in
the Incubator's operations. Governance activity tracks podling load, with
lower podling numbers corresponding to more predictable behaviour and
steadier reviewer availability. Across the last decade, release cadence has
improved, first-release success rates are significantly higher, repeated
release candidates are less common, and release-vote data show a higher
number of releases over time. These improvements reflect more precise
guidance, stronger documentation, and sustained mentor support. Podling
reporting reliability has also strengthened, with far fewer missed or
incomplete reports and closer alignment with expectations. Graduation and
retirement patterns remain consistent with historical norms. The Incubator
no longer experiences the governance irregularities, bottlenecks, or shock
events that appeared in earlier years.
A small program-level risk remains that fewer opportunities for new
contributors to participate in governance activities may slow future
renewal. However, recent improvements in mentor onboarding, documentation
of cultural knowledge, and broader availability of guidance for both
podlings and mentors are likely to offset this.
Practising the Apache Way was also delivered as reusable learning
materials, a workshop, and a micro-learning course.
The Mentor Topic of the Month discussion continued, with October’s topic
focused on engaging new contributors. November’s topic focused on using
chat and instant messaging responsibly during incubation.
An optional six-month community health review experiment is underway, with
BifroMQ invited to participate. This uncovered some governance issues that
the podling is now addressing. BifroMQ is also continuing with the
trademark registration in China.
There was a minor documentation update to clarify how podlings should add
PPMC members, as the previous guidance was outdated.
The experimental podling health reports are being adopted and are showing
direct improvements in podling reporting.
There is ongoing discussion about the future of Apache Baremaps, and the
project may retire if activity does not improve.
Apache PouchDB reported that earlier incubation delays have now been
resolved, and the project is working toward the first Apache-compliant
release.
Apache Polaris continues to show strong and sustained activity. Several
IPMC members have suggested the podling should begin discussions about
graduation.
OpenServerless has not made a release yet and has been encouraged to do so,
and to move more of its discussion to the mailing list. The project has now
started a discussion on its first release.
Most podlings continue to make progress toward graduation. Both Livy and
Toree are working on their next releases, and once those are completed,
they are expected to continue discussing and working toward graduation.
Those with keen eyes may notice that this is the second Incubator report in
a row where all podling reports have been submitted.
## Community
### New IPMC members:
- None
### People who left the IPMC:
- Lewis McGibbney
## New Podlings
- None
## Podlings that failed to report, expected next month
- None
## Graduations
- Wayang
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
November:
- Apache Fluss 0.8.0
- Apache GeaFlow 0.7.0
- Apache HugeGraph 1.7.0
## IP Clearance
- Cassandra Python driver
- Cassandra CPP driver
- Phoenix Adapters
## Legal / Trademarks
N/A
## Infrastructure
N/A
## Table of Contents
[Auron](#auron)
[Baremaps](#baremaps)
[BifroMQ](#bifromq)
[Fesod](#fesod)
[Gealfow](#geaflow)
[Iggy](#iggy)
[KIE](#kie)
[OpenServerless](#openserverless)
[Otava](#otava)
[OzHera](#ozhera)
[Polaris](#polaris)
[PouchDB](#pouchdb)
--------------------
## Auron
Auron accelerates Apache Spark SQL by providing an alternative vectorized
execution layer implemented in Rust, enabling native performance while
maintaining full Spark compatibility.
Auron has been incubating since 2025-08-05.
### Three most important unfinished issues to address before graduating:
1. Ensure that the website and codebase are fully compliant with ASF
policies.
2. Increase public communication on dev@ and ensure all project decisions
and planning are captured on the mailing list.
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?
1. One new committers added: Ruilei Ma
2. 20 active code contributors, including 10 new contributors.
3. made a presentation at RustChinaConf 2025.
### How has the project developed since the last report?
1. The community has published its first incubating release
(apache-auron-incubating-v6.0.0)
2. 179 commits since 2025-08-31
3. The community continues to improve Spark on Auron, including the
implementation of numerous native functions, enhancements to test cases,
and improvements to build scripts.
4. The community is making progress on Flink on Auron, having completed
the design proposal document, and refactored the common core module
(auron-core).
### 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-10-17
### When were the last committers or PPMC members elected?
2025-09-22
### 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. The podling name “Auron” has been reviewed by the VP, Brand. We are
not aware of any misuse by third parties.
### Signed-off-by:
- [X] (auron) Becket Qin
Comments:
- [X] (auron) Calvin Kirs
Comments:
- [X] (auron) Hao Ding
Comments: keep working
- [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. Discussing the future of the project
### Are there any issues that the IPMC or ASF Board need to be aware of?
The project is used in production by a few companies, but we struggle to
build a sustainable community. We will initiate a discussion on the
project's future early in 2026. A possibility would be to retire it from
the Apache Incubator and to continue the development under a lighter
process within its original organization.
### How has the community developed since the last report?
The project activity decreased further since the last report.
### How has the project developed since the last report?
We fixed minor issues.
### 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.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (baremaps) Bertrand Delacrétaz
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
- [X] (baremaps) Julian Hyde
Comments: Activity is low, and even though Baremaps has users
in production, the community is not increasing in size. The
project should consider retirement. (And it is.)
- [ ] (baremaps) Calvin Kirs
Comments:
- [ ] (baremaps) George Percivall
Comments:
### IPMC/Shepherd notes:
--------------------
## BifroMQ
BifroMQ is a Java-based, high-performance, distributed MQTT broker with
native multi-tenancy support, designed for large-scale
connections and message delivery.
BifroMQ has been incubating since 2025-04-22.
### Three most important unfinished issues to address before graduating:
1. Complete the first Apache Incubator release and establish a regular
release cadence.
2. Increase public communication on dev@ and ensure all project decisions
and planning are captured on the mailing list.
3. Grow community participation beyond the original contributors, including
attracting new reviewers and contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
The primary concern is low traffic on the dev@ list and limited visibility
of development discussions.
Recent mentor feedback highlighted the need to move architectural
decisions, release planning, and prioritization discussions onto dev@ to
comply with ASF governance expectations.
In addition, regarding the “BifroMQ” trademark transfer in China: in
response to a time-limited office action from the China National
Intellectual Property Administration (CNIPA), Baidu submitted the requested
supplemental materials before the deadline. We are now waiting for an
update from ASF on the status and next steps.
### How has the community developed since the last report?
Community activity on GitHub remains steady, but public communication has
been low.
Following mentor feedback, the PPMC began improving transparency by
starting public discussion threads, including a DISCUSS thread for the
first release.
We also launched the “BifroMQ” WeChat Official Account to support outreach
to the Chinese-speaking community. The account name currently uses
“BifroMQ” (without the “Apache” prefix) because the platform requires
formal authorization to use “Apache” in the account name. The account
description clearly identifies the project as “Apache BifroMQ (Incubating)”.
Official project discussions and decisions continue to happen on the
mailing list.
### How has the project developed since the last report?
Work toward the first incubator release has been completed, including
architectural refactoring, API stabilization, and Apache compliance work
(LICENSE/NOTICE, headers, package renaming, distribution scripts).
A DISCUSS thread(https://github.com/apache/bifromq/discussions/192) for the
4.0.0-incubating release has been opened to gather community feedback
before preparing RC1.
A significant amount of work came from supporting an early enterprise
adopter running BifroMQ in production, resulting in important optimizations
and bug fixes now included in the upcoming release.
### 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?
No new committers or PPMC members have been added since incubation started.
### Have your mentors been helpful and responsive?
Yes, our mentors are very helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The podling name “BifroMQ” has been reviewed by the VP, Brand. We are
not aware of any misuse by third parties.
For outreach to the Chinese-speaking community, we have created a WeChat
Official Account currently named “BifroMQ”. The platform requires an
authorization document to use “Apache” in the account name, so we are
temporarily using “BifroMQ” as the account name while clearly stating
“Apache BifroMQ (Incubating)” in the description.
We would appreciate guidance from ASF (Incubator and Brand) on the proper
process to obtain authorization for using the full “Apache BifroMQ” name
for this account, so that we can align fully with the Incubator publicity
policy.
### Signed-off-by:
- [X] (bifromq) Christofer Dutz
Comments: The "last release" was a pre-Apache release. Since I last
brought up the issue of the lack of public discussions, more discsussions
are showing up. I hope the project will continue doing that and not only
for trivial things.
- [ ] (bifromq) Xiangdong Huang
Comments:
- [ ] (bifromq) Calvin Kirs
Comments:
- [X] (bifromq) Penghui Li
Comments: LGTM
- [ ] (bifromq) Sheng Wu
Comments:
### IPMC/Shepherd notes:
--------------------
## Fesod
Fesod is a high-performance and memory-efficient Java library for reading
and writing Excel files, designed to simplify development and
ensure reliability.
Fesod has been incubating since 2025-09-17.
### Three most important unfinished issues to address before graduating:
1. Ensure that the website and codebase are fully compliant with ASF
policies.
2. Publish the first release under the Apache Incubator.
3. Continue to grow the community and word towards the ASF maturity Model.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. The project now has several active new contributors.
2. We have created a Slack channel (under ASF) to facilitate
communication.
### How has the project developed since the last report?
We will initiate the community vote for the first release within the next
two weeks,
1. We refactored several core classes to ensure full compliance with
licensing requirements.
2. Formal preparation for the project's first official release has
commenced.
### 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:
N/A
### When were the last committers or PPMC members elected?
N/A
### Have your mentors been helpful and responsive?
Yes. They are very nice and helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246
### Signed-off-by:
- [X] (fesod) tison
Comments:
- [X] (fesod) Dave Fisher
Comments:
- [X] (fesod) Huajie Wang
Comments:
- [X] (fesod) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## Geaflow
GeaFlow is a streaming graph computing engine for distributed large-scale
real-time graph storage and analysis. It supports trillion-level graph
storage, hybrid graph and table processing, real-time/offline graph
computing, and interactive graph analysis.
GeaFlow has been incubating since 2025-06-06.
### Three most important unfinished issues to address before graduating:
1. Cultivate a more diverse community by engaging contributors and
committers from varied organizations and global regions.
2. Implement predictable release cycles and maintain high project stability
to encourage broad participation and adoption.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. Two new contributors have joined the community.
### How has the project developed since the last report?
1. Over the past month，12 pull requests have been merged, development has
focused on new features, code quality, and documentation. Key additions
include a Paimon stream source and support for Jaccard similarity.
Infrastructure saw the introduction of a cluster coefficient and GitHub
Actions condition checks. Code health was improved by standardizing editor
configs, removing unnecessary files/methods, and fixing a data loss bug
after failover.
2. The first community edition: V0.7.0 has been released on November 19th.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
+ [ ] Initial setup
+ [ ] Working towards first release
+ [X] Community building
+ [ ] Nearing graduation
+ [ ] Other:
### Date of last release:
The first community version was released on November 19th.
### When were the last committers or PPMC members elected?
After reviewing our active community contributors, we have selected two
qualified candidates. The process now advances to a period of discussion
followed by a formal voting process.
### Have your mentors been helpful and responsive?
Yes, we have received helpful guidance.
### Is the PPMC managing the podling's brand / trademarks?
N/A.
### Signed-off-by:
- [ ] (GeaFlow) Willem Ning Jiang
- [X] (GeaFlow) xinwang
- [X] (GeaFlow) lzljs3620320
- [X] (GeaFlow) jmclean
- [ ] (GeaFlow) paulk
### IPMC/Shepherd notes:
--------------------
## Iggy
Iggy is a high-performance, ultra-low latency and large-scale persistent
message streaming platform written in Rust.
Iggy has been incubating since 2025-02-04.
### Three most important unfinished issues to address before graduating:
1. Continue expanding the community, release more versions under ASF
2. Increase the use of GitHub Discussions/Issues integrated with mailing
lists.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- Discord members count 560+, new contributors writing proposals
(discussions), submitting PRs for fixing issues, docs, enhancements.
- Github stars reached 3.3K+
- Crates downloads reached 168K+
- Presented Apache Iggy at the ApacheCon in September
- Recent blog post on Building WebSocket Protocol in Apache Iggy using
io_uring and Completion Based I/O Architecture
(https://iggy.apache.org/blogs/2025/11/17/websocket-io-uring) drew a lot of
attention on other sites and social media and attracted critical talent
### How has the project developed since the last report?
- Release 0.6.0 is under voting process
- Rewrite the server to use io_uring with thread-per-core, shared-nothing
architecture using compio runtime
- Implement WebSocket transport with custom compio-ws library designed for
completion-based I/O
- Add helpful diagnostic messages for io_uring runtime failures
(RLIMIT_MEMLOCK, seccomp)
- Harden security with auto-generated root password and Argon2 password
hashing (replacing bcrypt)
- Replace CRC32 checksums with xxHash3 and use UUIDv4 for random message IDs
- Implement GetClusterMetadata command with leader-aware connect mechanism
in SDKs
- Add foundation for clustering with consensus, metadata modules, and
TransportEndpoints
- Introduce Iceberg sink connector with S3 storage, REST catalogs, and
fan-out routing
- Add Elasticsearch sink and source connectors with rustls TLS support
- Implement Flink processor and processor infrastructure for stream
processing
- Extend connectors runtime with configuration provider trait, HTTP config
provider, and E2E test suite
- Add high-level IggyPublisher and IggyConsumer clients to C# SDK with TCP
reconnection, TLS, and AES encryption
- Implement async/non-blocking Java SDK client using Netty with
CompletableFutures
- Add TLS TCP support to Java and C# SDKs
- Extend Python SDK with connection string support, bytes data, typing
stubs, and musllinux wheels
- Improve Go SDK with DeleteConsumerOffset, error handling refactor, and
deserialization fixes
- Add virtual commands (ensureStream, ensureTopic, ensureGroup) and
nullable returns to Node.js SDK
- Implement builder pattern for Rust SDK client and unify TransportProtocol
enum across codebase
- Fix multiple consumer group bugs (offset storage, deletion, validation,
hashmap usage)
- Fix active segment position inconsistency and Murmur3 hash shard
assignment skew
- Unify Helm charts for server and UI with environment variable support
- Overhaul CI/CD with intelligent change detection, dual caching, and
multi-arch Docker builds (~40% faster)
- Update to Rust 1.90 and fix Docker builds for macOS (ARM64 support)
- Improve Web UI with autocomplete, keyboard navigation, large number
rendering, and security fixes
- Add -c/--consumer-group flag to CLI for consumer offset commands
### 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 (new release 0.6.0 is expected to land by 2025-12-12)
### 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.
### 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: Nice work!
- [X] (iggy) Yonik Seeley
Comments:
- [ ] (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.
### Three most important unfinished issues to address before graduating:
1. Category X libraries (we're making progress, next release should
substantially cut down the number of Category X issues)
2. Community Building
3. More releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
We just finished a vote for a new committer today!
### How has the project developed since the last report?
Working towards another release, early 2026.
### 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-07-10
### When were the last committers or PPMC members elected?
Today!
### Have your mentors been helpful and responsive?
Mentors have been good so far. No issues.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (kie) Brian Proffitt
Comments:
- [X] (kie) Claus Ibsen
Comments:
- [X] (kie) Andrea Cosentino
Comments: All 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 is still under effort.
2. Consolidation and alignment of the documentation site project.
3. Started a discussion on ML on how to make the build ASF compliant.
### 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?
Since last report, nothing changed.
### How has the project developed since the last report?
Since the last report the project was extended / improved by:
- adding a
[devcontainer](https://github.com/apache/openserverless-devcontainer) with
a development environment integrated inside the platform.
- adding an [Admin API
component](https://github.com/apache/openserverless-admin-api) with some
REST api (for authentication purposes and for building custom runtime
images on the fly)
- replacing MinIO component inside the operator with SeaweedFS (which is
under Apache License 2.0)
### 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?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (openserverless) Bertrand Delacrétaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [X] (openserverless) François Papon
Comments: Low activity on the mailing list, no release since the
start of the incubation, no new committer.
- [ ] (openserverless) JB Onofré
Comments: OpenServerless report ?
- [X] (openserverless) PJ Fanning
Comments: I agree with what François says above
### IPMC/Shepherd notes:
--------------------
## Otava
Apache Otava (incubating), a command-line tool, written in Python, detects
and alerts about statistically significant changes in performance test
results (more generally, time-series data) stored in CSV files or a number
of supported databases.
A typical use-case of Otava is as follows:
1. A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
2. The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
3. Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
4. Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
5. Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the environment.
Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter.
### Three most important unfinished issues to address before graduating:
1. 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?
In our previous report we already shared our successfully completing the
first release as an Apache Incubator process. This first release was mostly
focused on a) bringing together various github forks under the a unified
ASF upstream project, and b) releasing one release with the new project
name, and following the ASF process, but one that did not in itself contain
a lot of new features or changes beyond (a).
With such an inaugural release out of the way, we have seen over the past 4
months a handful of patches that make more substantive changes to the
codebase. We still have a couple foundational tasks remaining that are
holding us back from accepting new code contributors and contributions
without any friction, but the door is at least more open than it was before
the July release (0.6.1).
The remaining foundational tasks are:
1. Doing another release, 0.7.x, that is still focused on backward
compatibility with our past, and merely introduces small fixes in the
functionality itself, as well as the release process. Re-rehearsing the
actions related to releasing, and related collaboration among the project
committers seems a significant part of the process of becoming a fully
graduated ASF project.
2. Cutting the dependency on an external implementation of the "E-Divisive
means" algorithm, which is the very heart of what Otava does. This is the
so called "signal-processing-algorithms" pip module released by MongoDB
under the Apache 2.0 License, but not donated to ASF. We have come to the
conclusion we need this very core functionality to be part of our own code
base and version control, and since we didn't manage to get the MongoDB
team's attention, we decided to rewrite an independent implementation.
3. Upgrading from the unsupported python versions 3.8 and 3.9 to the most
recent versions.
1 above is already undergoing voting, and 2 is in review and approved,
waiting to be merged.
The 0.7.x release also brings back an additional distribution format:
docker images.
For the rewrite of the E-Divisive algorithm we are glad to report we found
a completely new contributor to the project, with sufficient mathematical
education to take on this somewhat daunting task. In the process of
re-implementing the algorithm directly from its academic publication, the
contributor managed to discover a bug/omission in the implementation we
have been using for almost a decade now. The effect of this discovery is
that the new implementation will find change points that the original
algorithm tends to miss, in situations where there are 2 or more changes
close to each other.
The fact that the new implementation of the E-divisive algorithm was done
by a completely new contributor, that did not look at the MongoDB
implementation before creating the new implementation, means that our new
implementation ought to qualify as a properly independent, clean room
implementation. While this was not a strict requirement for this task, now
that this is the outcome, we wish to record it in the board minutes.
Altogether we have during our first year as an ASF incubator now received
code contributions from 3 founding project members and 3 new contributors
and one of the project mentors. In addition to these 7 there have been
several more that contributed either a bug report or participated in an
email thread, or voting for a release. One of these was a developer from
the Tarantool open source database, that started using Otava as part of
their Continuous Benchmarking. As discussed in this update, we believe
there are more interested contributors that are still held back by our old
python version and untangling a major legacy dependency.
We have not yet approved new committers or PPMC members to the project, as
there was not yet sufficient time and opportunity to demonstrate
significant and sustained contributions to the project. We are optimistic
that we are moving in the right direction where this could be happening in
a near future.
On the topic of committers and PPMC members it is notable that several of
the past contributors that were listed in our project proposal a year ago,
and approved as founding PPMC members, have not actually shown up on the
ASF mailing list during our first year. We will follow up with these
individuals to confirm their desired status with the project, and take
appropriate action based on that outreach. (From a community diversity and
robustness perspective, it should be mentioned that the 3 founding
contributors that have been the most active, still represent 3 different
employers, and to the best of our knowledge, the new contributors are also
employed by 3 net new employers.)
### How has the project developed since the last report?
(See above, it felt meaningful to combine these two answers.)
### 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:
We are progressing well with the community building, but not yet nearing
graduation.
A self review based on https://s.apache.org/727vc
Code 5/5
Licenses and Copyright: 5/5
Releases: 4/5
Quality: 5/5
Community: 7/7
Consensus: 4/5 (Missing: CS10)
Independence: 2/2
Brand: 4/4
### Date of last release:
2025-07-25
### When were the last committers or PPMC members elected?
None yet.
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
VP, Brand approved the new project name in February. Our life as an ASF
incubating project really only started after that date.
We are not aware of any trademark issues related to the new project name.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments: An amazing amount of detail, thanks.
- [X] (otava) Enrico Olivelli
Comments:
- [X] (otava) Lari Hotari
Comments:
- [X] (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?
More contributors have become active and have collectively completed a
total of 16 PR submissions.
Expand our contributor base continuously, and actively cultivate and
develop future committers and PPMC members.
### How has the project developed since the last report?
The primary accomplishments include the iteration of system optimization
and intelligent analysis.
1.System Stability & Performance Optimization.
Memory and Resource Management: Enhanced memory handling to prevent
out-of-memory errors; introduced inode change detection to prevent resource
leaks;
optimized resource cleanup to improve long-term operational stability.
File and Logging Management: Added file read exception retry mechanism;
increased frequency of file truncation detection and log rotation; resolved
data loss issues to ensure logging continuity.
Task Scheduling and Execution: Optimized the message-sending order in
PingTask and added server list validation to prevent startup blocking;
supports customizable collection intervals and control state export
periods.
2.Enhanced Analysis and Problem Diagnosis.
Core Feature: Implemented traceId-based root cause analysis, enabling rapid
tracing and pinpointing of issue origins.
Module Enhancement: Refactored the intelligent analysis module to improve
log processing and automated issue identification, providing stronger
support for operational decision-making.
### 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:
- [X] (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. Check the Polaris existing trademarks at the ASF (transfer has been
done, to be verified)
2. Perform a namesearch (for the record as previous point)
### 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?
Between 2025-07-31 and 2025-10-31:
- 2 new releases
- 17 new contributors
- 649 PRs opened / 517 PR merged
- 745 messages on the dev@ mailing list
We are happy to see new contributors who contributed important new features:
- OPA support.
- Polaris Console (UI) is coming.
- S3 KMS support.
### How has the project developed since the last report?
We did 1.1.0-incubating and 1.2.0-incubating releases since the last report.
1.3.0-incubating release is also in preparation.
Here's the highlights about project development since the last report:
- Improvement on the website, adding new blog posts (StarRocks and Polaris
integration)
- Moving forward on NoSQL support
- New OPA Authorizer
- New MetricsReport interface
- New JDBC schema evolution support
- A lot of improvements on Python (CLI, ...)
- Enhanced support for S3-compatible (on-prem) storage
- Automated release workflows are in place, ongoing work to support ATR
- Apache Polaris website is now integrated to analytics.apache.org
### 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-10-27
### When were the last committers or PPMC members elected?
Last PPMC member has been elected on 2025-11-19 (Yong Zheng).
### Have your mentors been helpful and responsive?
Mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes, the podling manages the brand/trademarks, especially working with 3rd
parties organizing meetups.
### Signed-off-by:
- [ ] (polaris) Holden Karau
Comments:
- [ ] (polaris) Kent Yao
Comments:
- [ ] (polaris) Ryan Blue
Comments:
- [X] (polaris) Jean-Baptiste Onofré
Comments: Again a solid activity on the podling, I can see new
contributors and consistent interest. Maybe the podling should consider
starting discussion about graduation soon?
- [X] (polaris) François Papon
Comments: As new mentor, I can see a lot of dicussion on the mailing
list, the community looks to be safe and growing. The project has released
several version and it's closed to the graduation.
### 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. Finish the initial code import (see below)
2. Making a release
3. Adding contributors
### Are there any issues that the IPMC or ASF Board need to be aware of?
After a good start in Q2, the project was stalled in Q3 and first month
of Q4 because of champion unavailability. The champion (me, jan@) had
communicated to the rest of the incubating PPMC to clear out everything
needed for the initial code import and then had to step away for
personal reasons.
Those have resolved now, the code is now in ASF territory and we are
doing the initial adjustments (file headers etc) as we speak and the
following tasks are starting to be distributed among the rest of the
team, so a single-person bottleneck should not hold the project back.
### How has the community developed since the last report?
No noticeable changes yet, but some external contribution activity
has occurred.
### How has the project developed since the last report?
After clearing all hurdles with importing a 15 year old code base,
we have the sources finally under ASF control. We are aiming to
get to be in an ASF-releasable state in a few weeks.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
n/a
### When were the last committers or PPMC members elected?
n/a
### Have your mentors been helpful and responsive?
Mentors have flagged the slow progress and contributed to
things resolving and moving forward.
### Is the PPMC managing the podling's brand / trademarks?
PPMC have not yet requested a Podling Suitable Names Search
### Signed-off-by:
- [X] (pouchdb) PJ Fanning
Comments: Some progress happening now. No Podling Suitable Names
Search done yet and that could cause issues if name is rejected.
- [X] (pouchdb) Jean-Baptiste Onofré
Comments: Slow start in the podling, but now it seems to move
forward. If the podling doesn't have time to report this month, maybe
report next month ?
### 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 79 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- Hongyin Zhang was added to the PMC on 2025-11-07
- Xintao Lin was added as committer on 2025-09-09
## Project Activity:
- We released version 1.3.5 in past quarter, which fixed some bugs in 1.3.X
series.
- For 2.X series, the compatibility of the table model with standard SQL has
been further enhanced, achieving full support for all set operations,
optimizing the data query performance in memtables, and enabling the
modification of encoding and compression types for sequences in the tree
model.
- The community has three key focus areas for its future development:
1. Attempt to extend a new data type (OBJECT) designed for storing large
binary objects, enabling IoTDB to be applied to data storage scenarios in
meteorological, audio and video fields.
2. Integrate Python-based User-Defined Functions (UDFs) to further enhance
IoTDB’s data analytics capabilities.
3. Online Schema Change: support online modification of table names and
column names. This is a highly challenging task. To maintain the
self-parsability of TsFile, we redundantly store certain metadata in each
data file, which means conventional methods would require rewriting nearly
all TsFiles.
## Community Health:
Overall community health is good.
- dev@iotdb.apache.org had a 23% decrease in traffic in the past quarter (74
emails compared to 96)
- A PhD candidate from Renmin University of China developed a project named
CompressIoTDB[1] based on IoTDB, pioneering the introduction of Homomorphic
Compression (HC) theory into the time series domain. This work is designed
to address the core trade-off between compression and query performance in
traditional time series databases. By executing queries directly on
compressed data, it significantly improves query throughput and reduces
resource consumption, and has been published in PVLDB 2025.[2]
- Given that IoTDB’s release cycle may be relatively long, Colin Shi, a
contributor to the IoTDB community, developed a tool. Powered by AI, this
tool can search for commits related to error-causing issues, enabling the
copying of such commits to the branch of the previous official release
(ahead of IoTDB’s next official release) to generate a functional
package.[3]
[1] https://github.com/yuxin370/CompressIoTDB
[2] Tang, Yuxin, et al. "Improving Time Series Data Compression in Apache
IoTDB." Proceedings of the VLDB Endowment 18.10 (2025): 3406-3420.
[3] https://lists.apache.org/thread/q1mzqwwb2ohjyodf6h3cq5m9f3qpcsw7
-----------------------------------------
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 (20 years ago).
There are currently 60 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is 1:1, because all committers automatically
become PMC members.
Community changes, past quarter:
- No new PMC members. Last addition was Alejandro Moratinos on 2025-08-27.
- No new committers. Last addition was Alejandro Moratinos on 2025-08-27.
## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.
The 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.88.0 updated a first module to use the new AWS
SDK for Java 2.x version. The previous version 1.x will be end-of-life
by the end of 2025. Additional work is ongoing to update remaining usage
of AWS SDK 1.x in future Jackrabbit Oak releases.
## 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.86.0 was released on 2025-09-22
- jackrabbit-oak-1.22.23 was released on 2025-10-03
- jackrabbit-filevault-4.1.4 was released on 2025-10-24
- jackrabbit-oak-1.88.0 was released on 2025-11-04
## JIRA activity:
- 174 JIRA tickets created in the last 3 months
- 148 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: 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 33 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29
- Matt Pavlovich was added as committer on 2025-09-16
## Project Activity:
Apache Karaf 4.4.9 is in vote, bringing a lot of improvements and fixes. It
especially includes karaf-integration distribution as an alternative to
ServiceMix.
The plan for Karaf 4.5.0 is now clearer, and Karaf 4.5.0 is planned for Jan
26.
Also, Apache Karaf Decanter 2.12.0 has been released (2025-11-14), bringing a
lot of improvements and important fixes (including a security fix):
https://github.com/apache/karaf-decanter/releases/tag/decanter-2.12.0
Karaf Decanter main branch bumped to 3.0.0 series, preparing major update
(JDK21+ support, refactoring of the event layer, refactoring of the alerting
layer, ...).
Karaf (and subprojects) fully moved from Jira to GitHub Issues, and from
Jenkins to GitHub Actions. Jira is now read-only.
## Community Health:
Following the previous report:
- dev@karaf.apache.org had a 67% decrease in traffic in the past quarter (36
emails compared to 109) / user@karaf.apache.org had a 80% increase in
traffic in the past quarter (47 emails compared to 26).
- Karaf 4.4.x is still maintained, and the community agreed to do monthly
release (best effort) to ship fixes and improvements faster.
- karaf-integration distribution will be available in Karaf 4.4.9, providing
alternative to ServiceMix.
- We will work with the ServiceMix community to decide of the next step.
- Karaf 4.5.x plan is clear now about the feature resolver, karaf services,
JDK release, specs bundles removal, ...
-----------------------------------------
Attachment AS: Report from the Apache Kvrocks Project [Mingyang Liu]
## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, supporting many data
structures as Redis.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kvrocks was founded 2023-06-21 (2 years ago)
There are currently 29 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Aleks Lozoviuk on 2025-05-06.
- Rongxing Xiao was added as committer on 2025-10-04
## Project Activity:
In November, Apache Kvrocks released version 2.14.0. In October, Apache
Kvrocks Controller released version 1.2.0. The Controller is currently
preparing the 1.3.0 release.
Over the past few months, the community’s progress has been relatively steady.
There haven’t been many particularly exciting milestones, but a lot of
development is ongoing. The Timeseries and TDigest features have attracted
some new contributors, who are refining these features and adding support for
more Redis commands. Rongxing Xiao was nominated as a committer in October for
his work on supporting the Timeseries data structure. There was also another
committer nomination in October, but the nominee declined the nomination for
various reasons.
## Community Health:
The number of PRs hasn’t changed much. The number of issues has decreased a
bit, which I think is because there are fewer tracking issues. A single
tracking issue can lead to the creation of many issues.
I think the community as a whole is running smoothly. We’re considering adding
support for hash field expiration, but the community has not yet reached a
consensus on the technical approach. I hope we can resolve this in the coming
months.
-----------------------------------------
Attachment AT: Report from the Apache Kyuubi Project [Cheng Pan]
## Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses
## Project Status:
Current project status: Ongoing Issues for the board: none
## Membership Data:
Apache Kyuubi was founded 2022-12-21 (3 years ago) There are currently 29
committers and 16 PMC members in this project. The Committer-to-PMC ratio is
roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Binjie Yang on 2024-07-05.
- No new committers. Last addition was He Zhao on 2025-01-02.
- Change the Project Chair (Cheng Pan, VP) on 2025-09-12.
## Project Activity:
The community is actively working on Spark 4.1 support, and the PMC is
actively cooperating with the Apache security team to address potential CVEs.
## Community Health:
Overall community health is good. In the past quarter, the notifications mail
list mail number, which represents GitHub code repo activities, had a 35%
decrease in the past quarter to 475. The PMC considered it as normal because
the absolute number is relatively high. Kyuubi committer maintains a proactive
and high-quality code review process to ensure project quality, thereby
attracting more users and contributors.
-----------------------------------------
Attachment AU: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AV: 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 39 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jie Cheng on 2024-01-28.
- King Hao was added as committer on 2025-09-18
## Project Activity:
The Apache Linkis version 1.8.0 was released on 2025-10-17.
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.
The Apache Linkis version 1.9.0 is under development.
Mainly includes the following features:
- EC reuse enhancement, supporting resource and Python version
number judgment.
- Supports coexistence of spark2 and spark3.
- Management desk task log optimization supports viewing UDF logs.
- Increase the total number of tasks supported by the concurrency
engine configuration.
- Optimize resources to display wrong issues.
## Community Health:
Overall community health is good.
- 37 PRs closed on GitHub, past quarter.
- 39 issues closed on GitHub, past quarter.
-----------------------------------------
Attachment AW: 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: Active, ongoing
Issues for the board: None
## Membership Data:
Apache Lucene was founded 2005-01-19 (21 years ago)
There are currently 108 committers and 70 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
## Project Activity:
The project is in good shape, with stable, although a tad slower
activity in all areas (discussions on the mailing list,
github pull requests, member community invitations, commits).
In the period between 2025-09-01 and 2025-12-08, there were 234
commits to the main branch, 87 issues filed (37 resolved), 254
pull requests opened (and 201 closed).
There were four releases since last report - three to 10x
branch and one bugfix to 9.x branch.
On the main branch, there have been a number of improvements to
the vector module (hnsw) as well as infrastructure cleanups
related to the build system (gradle).
## Community Health:
No new PMC members have been added since last report. Three new committers
have agreed to join the community (Trevor McCulloch, Ramakrishna Chilaka,
Kaival Parikh).
-----------------------------------------
Attachment AX: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AY: 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 mainly focused on bugfixes (both in core and NimBLE Bluetooth stack)
related to release which is planned in December 2025. Continued work on
automated tests on real hardware.
## Community Health:
Core developers are active on regular (yet slightly less frequent) basis.
Most work is Bluetooth related.
-----------------------------------------
Attachment AZ: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environments, tooling platforms, and application
frameworks.
## Project Status:
Current project status: Ongoing with continuous activity
Issues for the board: None
## Membership Data:
Apache NetBeans was founded 2019-04-17 (7 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:
- Apache NetBeans 28 was released on 2025-11-10.
- Apache NetBeans 27 was released on 2025-08-21.
## Community Health:
- In an attempt to not be as dependent on our great installer contributor Neil
C. Smith and his organization codelerity (codelerity.com), the newly formed
external organization Friends of Apache NetBeans
(friendsofapachenetbeans.org) is picking up this activity, with the aim to
broaden the possibilities for contributing aspects that fall outside of the
scope of the Apache Software Foundation and Apache NetBeans, see
installers.friendsofapachenetbeans.org.
- The awareness that we need more committers and PMC members continues to
exist and this has been discussed and will continue to be discussed and
remains the key aspect of this project that requires attention and focus.
- 23 contributors, 2 for the first time for Apache NetBeans 27:
https://github.com/apache/netbeans/releases/tag/27
- 28 contributors, 2 for the first time for Apache NetBeans 28:
https://github.com/apache/netbeans/releases/tag/28
- dev@netbeans.apache.org had a 62% increase in traffic in the past quarter
(156 emails compared to 96)
- users@netbeans.apache.org had a 19% decrease in traffic in the past quarter
(127 emails compared to 155)
-----------------------------------------
Attachment BA: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Project Status:
Current project status: ongoing with moderate activity
Issues for the board: none.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (19 years ago) There are currently 62
committers and 37 PMC members in this project. The Committer-to-PMC ratio is
roughly 8:5.
Community changes, past quarter:
- No new PMC members have been added, although the PMC has voted for and
invited a new candidate, and we are currently awaiting their acceptance
email. Last addition was Sebastian Tschikin on 2024-09-18.
- Florian Motteau was added as committer on 2025-10-31
- Gaetan Chaboussie was added as committer on 2025-10-31
## Project Activity:
- Apache OFBiz 24.09.03 was released on 2025-11-10. As part of this release,
we fixed and disclosed two security vulnerabilities: CVE-2025-59118 and
CVE-2025-61623.
- Apache OFBiz 24.09.04 was released on 2025-12-02.
- Trademarks: There are no trademark-related concerns at this time.
## Community Health:
Over the past quarter, community engagement has remained stable, with
productive coordination and discussions on the mailing lists regarding
documentation, framework code refactoring, new features, and the migration to
Java 21. Two new committers have been added, and one individual has been
elected and invited to join the PMC. This person has requested some time to
address personal matters before accepting the nomination, which is still
pending.
-----------------------------------------
Attachment BB: Report from the Apache Olingo Project [Michael Bolz]
-----------------------------------------
Attachment BC: 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 35
committers and 22 PMC members in this project. The Committer-to-PMC ratio is
roughly 1.6.
Community changes, past quarter:
- Erick Guan was added as PMC Member on 2025-10-13
- Jianping Huang was added as PMC Member on 2025-10-16
- Tenny Zhuang was added as committer on 2025-10-22
- Qinxuan Chen was added as PMC Member on 2025-11-17
## Project Activity:
- v0.54.1 was released on 2025-09-11
- v0.55.0 was released on 2025-11-24
## 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 split more OpenDAL components into multiple
GitHub repositories to enable them to develop at different paces.
### 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 BD: Report from the Apache OpenNLP Project [Jeffrey T. Zemerick]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache OpenNLP was founded 2012-02-14 (14 years ago)
There are currently 26 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Atita Arora on 2025-07-19.
- No new committers. Last addition was Nishant Shrivastava on 2025-07-29.
## Project Activity:
The project released versions 2.5.6 and 2.5.6.1. There are now pre-trained
models available for 36 languages. The releases addressed various
improvements, dependency updates, and bug fixes.
## Community Health:
Mailing list traffic remained about the same as previous periods. Generally,
traffic is low but the project is healthy as there is a set of core committers
who are active. There have been a few new contributors over the past period,
and Apache Solr merged a PR that includes ONNX model support via OpenNLP which
could help expand the community size.
-----------------------------------------
Attachment BE: 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:
The new CDI spec is lurking in and thus we had a bit of an uptick
in activity. And I expect it to become even more over the next quarter.
We also invited a new committer.
I also expect a new Meecrowave release soonish as we got some feedback
for the 2.0.0 release.
## PMC changes:
- Currently 13 PMC members, 20 committers
- No new PMC members. Last addition was Reinhard Sandtner on 2017-10-09.
- Jonathan Gallimore was added as committer on 2025-12-04
## Recent releases:
- meecrowave-2.0.0 was released on 2025-10-21.
- 2.0.28 was released on 2025-05-19.
- 4.0.3 was released on 2024-12-14.
-----------------------------------------
Attachment BF: Report from the Apache Paimon Project [Jingsong Lee]
## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Paimon was founded 2024-03-20 (2 years ago)
There are currently 24 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.
- Lei Li was added as committer on 2025-12-03.
## Project Activity:
Software development activity:
- We released the release 1.3.0 on 2025-11-12.
- We released the release 1.3.1 on 2025-11-20.
- We released PyPaimon pure Python version in release 1.3.
- We developed Incremental Clustering feature for low latency query.
## Community Health:
- dev mail list had a 5% increase (74 emails compared to 70).
- user email list had a 10% increase (32 emails compared to 29).
- issue mail list had 0% increase (2023 emails compared to 2021).
- Community PR contributions have increased significantly.
-----------------------------------------
Attachment BG: 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:
Project remains quite active with a small but committed core of committers.
The team should be able to react to any major bugs or security reports.
Issues for the board:
Nothing of note
## Membership Data:
Apache Pekko was founded 2024-03-20 (2 years ago)
There are currently 28 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- Domantas Petrauskas was added to the PMC on 2025-11-20
- No new committers. Last addition was Domantas Petrauskas on 2024-12-19.
## Project Activity:
Regular bug fix releases.
Moving towards releasing 2.0.0-M1.
## Community Health:
Not many new contributors but a few are involved. The core committers
remain active.
The Pekko libraries continue to be actively used in the Java and Scala
ecosystems.
-----------------------------------------
Attachment BH: 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
Issues for the board: none
## 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:
The vote on release candidate 0.18rc1 was successful; consequently, version
0.18 has been finalized and released.
Recent releases:
- 0.18.0 was released on 2025-09-15.
- 0.17.0 was released on 2017-06-16.
## Community Health:
Overall activity is low as the project is mostly stable. Contributions are
mainly bug fixes and updating dependencies.
-----------------------------------------
Attachment BI: Report from the Apache PLC4X Project [César García]
-----------------------------------------
Attachment BJ: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
-----------------------------------------
Attachment BK: Report from the Apache Pulsar Project [Matteo Merli]
-----------------------------------------
Attachment BL: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment BM: Report from the Apache Royale Project [Yishay Weiss]
-----------------------------------------
Attachment BN: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to a very easy-to-use ultra-high-performance distributed data
integration platform that supports cdc and batch synchronization of massive
data
## Project Status:
Current project status: Health Issues for the board: There are no Board-level
issues at this time.
## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (2 years ago) There are currently 37
committers and 22 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Naijie Liu on 2025-07-08.
- No new committers. Last addition was Chao Wang on 2025-04-14.
## Project Activity:
- 2.3.12 was released on 2025-09-12
- 2.3.11 was released on 2025-05-21
- 2.3.10 was released on 2025-03-21
## Community Health:
- We have held one community online Meetups in last quarter.
Overall community health is good. We have been performing extensive outreach
to related projects, in order to attract new contributors, and are seeing a
steady influx of new people wishing to join and contribute, both programming-
and documentation.
-----------------------------------------
Attachment BO: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
-----------------------------------------
Attachment BP: Report from the Apache ShardingSphere Project [Liang Zhang]
## Description:
The mission of Apache ShardingSphere is the creation and maintenance of
software related to a database clustering system providing data sharding,
distributed transactions, and distributed database management
## Project Status:
Current project status: Good
Issues for the board: None
## Membership Data:
Apache ShardingSphere was founded 2020-04-15 (6 years ago)
There are currently 62 committers and 22 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 Longtao Jiang on 2024-03-28.
- No new committers. Last addition was Chenyang Ma on 2024-05-27.
## Project Activity:
Continued progress toward the release of version 5.5.3.
- Focus areas include PostgreSQL protocol enhancements,
improved SQL parser accuracy, and performance optimizations.
- Addressed accumulated community issues
and pull requests in preparation for feature freeze.
- Leveraged Codex and Claude Code to process issues, PRs,
and improve test coverage, resulting in noticeable efficiency gains.
- Version 5.5.3 is planned for release in November.
Future Plans
- Introduce a unified MCP entry for database management.
- Optimize the Proxy’s memory and execution model to
reduce pressure under large-query workloads.
## Community Health:
Community Contribution
- The number of active contributors remains stable,
with new contributors continuously joining—particularly
in the SQL Parser, Data Pipeline,
and PostgreSQL-related modules.
- Multiple community members continue to submit high-quality PRs,
including enhancements to the type system, optimizer improvements,
bug fixes, and protocol compatibility updates.
- Review quality has improved,
with more senior contributors participating in design discussions,
issue triage, and architectural guidance.
Community Engagement
- GitHub issues, PRs, and discussions remain highly active,
with many questions receiving responses within 24 hours.
- Community demand continues to grow in areas such as Proxy performance,
data pipelines, and complex SQL support.
Risks & Challenges
- The project’s broad scope leads to accumulated technical debt
and blurred module boundaries, creating additional maintenance pressure.
A plan is in progress to streamline and deprecate
non-core peripheral modules.
Overall Health
- The project remains active, and contribution quality continues to improve.
- Current challenges primarily stem from technical complexity
and long-standing architectural debt, rather than any decline
in community engagement.
-----------------------------------------
Attachment BQ: Report from the Apache Shiro Project [Lenny Primak]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with 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 15 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- Boris Petrov was added as committer on 2025-10-31
## 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.6 was released on 2025-11-05.
## Community Health:
Mailing list traffic is low.
We opened up GitHub Discussions in December 2025.
We eased contributions by offering "squash and merge" functionality on GitHub.
-----------------------------------------
Attachment BR: Report from the Apache SINGA Project [Wang Wei]
-----------------------------------------
Attachment BS: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Project Status:
Current project status: Ongoing.
Issues for the board: none.
## Membership Data:
Apache Sling was founded 2009-06-17 (16 years ago)
There are currently 53 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Julian Reschke on 2024-10-22.
- Nicola Scendoni was added as committer on 2025-11-10
## Project Activity:
We released version 13 of our sample application, the Sling Starter, on
January 17th, 2025. We plan to release Sling Starter 14 in the near future.
We have also released version 1.3.0 of our IDE tooling plug-in for Eclipse.
The Jakarta EE migration has been completed and Sling now supports both the
JavaX and Jarakta Servlet APIs in parallel.
In the meantime individual modules are being developed and released,
with 33 releases for this reporting period.
## Community Health:
Community health is pretty good and contributions from various
individuals continue.
-----------------------------------------
Attachment BT: Report from the Apache SpamAssassin Project [Giovanni Bechis]
## Description:
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. We have launched a logo contest on users mailing list in
order to have a new logo that doesn't include Apache feather.
## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.
-----------------------------------------
Attachment BU: Report from the Apache Storm Project [Richard Zowalla]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Project Status:
Current project status: Ongoing (reactivated)
Issues for the board: none
## Membership Data:
Apache Storm was founded 2014-09-17 (11 years ago)
There are currently 48 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Purshotam Shah on 2025-05-21.
- No new committers. Last addition was Purshotam Shah on 2024-10-08.
## Project Activity:
Project activity has tapered off in recent years, and Storm is currently in
maintenance mode. Even so, we still receive occasional bug reports, showing
that Storm is actively used, which is encouraging. Since most users now rely
on GitHub for reporting issues, the user mailing list stays quiet for the most
part.
In the past quarter, we updated several third-party libraries to their latest
versions, and we plan to continue our regular release schedule with consistent
patch updates.
Recent releases:
- 2.8.3: 2025-11-02
- 2.8.2: 2025-07-26
- 2.8.1: 2025-06-03
## Community Health:
Community engagement is currently healthy, but could benefit from new
contributors or users. A few long-time contributors still monitor the
mailing list and occasionally step in to answer questions, particularly when
historical context or legacy decisions are involved.
-----------------------------------------
Attachment BV: Report from the Apache StreamPark Project [Huajie Wang]
-----------------------------------------
Attachment BW: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high-performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Project Status:
Current project status: Active
Issues for the board: None
## Membership Data:
Apache Synapse was founded on 2007-12-19 (18 years ago).
There are currently 36 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Shafreen on 2021-05-09.
- No new committers. Last addition was Nuwan Jayawardene on 2022-11-19.
- A committer vote is currently in progress.
## Project Activity:
The Synapse-Go project continued to receive contributions this quarter, though
the volume of activity was lower than in previous periods. To support ongoing
development and improve contributor effectiveness, the PMC initiated a vote to
add a new committer who has been actively contributing to the Synapse-Go
effort. We expect to close the vote soon so that the contributor can
participate more seamlessly in the project.
## Community Health:
Mailing list activity remained low this quarter, with only a few
exchanges—primarily related to the Synapse-Go project and the active committer
vote. Although overall engagement was minimal, the steps taken to recognize
new contributors are expected to strengthen community participation moving
forward.
-----------------------------------------
Attachment BX: Report from the Apache Teaclave Project [Zhaofeng Chen]
# Apache Teaclave Board Report - December 2025
## Description
Apache Teaclave provides SDKs for building memory-safe applications on Trusted
Execution Environments (TEEs).
## Project Status
**Status:** New
Apache Teaclave graduated as a Top-Level Project on August 21,
2025. Since graduation, the community has:
1. (1st report) Completed the transition to TLP infrastructure, including
GitHub repositories, distribution servers, website updates, and project
documentation.
2. (2st report) Released `teaclave-trustzone-sdk v0.6.0`, the first release as
a TLP.
3. (Nov. & this report) Released `teaclave-trustzone-sdk v0.7.0` by supporting
OP-TEE 4.8.0, enhancing CI/CD infrastructure with automated testing, and
improving developer tooling and documentation.
For unknown reasons, our Nov. report is not approved. So I combine updates in
Nov. and Dec. together in this Report.
## Summary of Project Health and Status
Since the last report, Apache Teaclave has maintained steady progress with
infrastructure updates, version upgrades, and enhanced developer tooling. The
community remains active with steady development and moderate mailing list
discussions. Current focus areas include strengthening coding practices for
the Rust codebase and improving the TEE development experience to allow users
to build and experiment with minimal effort.
## Issues for Board Attention
There are no Board-level issues at this time.
## Recent Releases
- 2025-12-03: Teaclave TrustZone SDK v0.7.0 (2nd TLP release)
## Project Activity
### Development Activity
- Integrating with OP-TEE to version 4.8.0
- Strengthening CI/CD pipelines with daily automated testing
- Improving developer experience through better error messages and
documentation.
- Approximately 40 commits merged in the past three months.
### Community Activity
- Developer mailing list: moderate activity (~20 topics in the past 30 days).
- No new committers or PMC members since the last report.
- New contributors joined since the last report, representing potential future
committers.
## Current Plans
- **Short term (next quarter):**
- Complete next quarterly release of Teaclave TrustZone SDK, aligned with
OP-TEE’s release schedule.
- Enhance onboarding and TEE development experience by simplifying the
process of building and running TEE examples with minimal effort,
including Cargo subcommands build and toolchain management.
- **Medium term:**
- Open source additional real-world SDK use cases (e.g., Web3 scenarios).
- Maintain alignment with OP-TEE’s quarterly release cadence.
## Community Changes
- Current: 18 PMC members; no new additions since the last report.
- PMC membership represents a healthy diversity of organizations.
## Project Branding
- No branding issues.
- Website and download pages comply with Apache branding requirements.
## Legal Issues
- No legal issues to report.
## Infrastructure
- No infrastructure concerns at this time.
-----------------------------------------
Attachment BY: Report from the Apache Tomcat Project [Christopher Schultz]
## Description:
Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.
The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10
and later implement specifications developed as part of Jakarta EE. Tomcat 9
and earlier implement specifications developed as part of Java EE.
## Project Status:
The Tomcat project 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 (21 years ago)
There are currently 50 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Soumis on 2025-02-18.
- No new committers. Last addition was John Engebretson on 2025-02-05.
## Project Activity:
* Tomcat 10.1.50 was released on 2025-12-08.
* Tomcat 11.0.15 was released on 2025-12-08.
* Tomcat 9.0.113 was released on 2025-12-07.
* Tomcat Migration tool for Jakarta EE 1.0.10
* Tomcat 11.0.14 was released on 2025-11-10.
* Tomcat 10.1.49 was released on 2025-11-10.
* Tomcat 9.0.112 was released on 2025-11-10.
* Tomcat 11.0.13 was released on 2025-10-14.
* Tomcat 10.1.48 was released on 2025-10-13.
* Tomcat 9.0.111 was released on 2025-10-13.
* Tomcat 11.0.12 was released on 2025-10-08.
* Tomcat 10.1.47 was released on 2025-10-07.
* Tomcat 9.0.110 was released on 2025-10-06.
* Tomcat 10.1.46 was released on 2025-09-12.
* Tomcat 10.1.45 was released on 2025-09-08.
* Tomcat 9.0.109 was released on 2025-09-05.
The PMC have been continuing discussions with HeroDevs that may lead to the
project receiving funding from HeroDevs. At this point, we have submitted
documentation to support our first grant application.
## Community Health:
Continued healthy activity across multiple components and responsiveness on
both dev and user lists.
-----------------------------------------
Attachment BZ: Report from the Apache Traffic Server Project [Bryan Call]
-----------------------------------------
Attachment CA: 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 82 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- Yong Wu was added to the PMC on 2025-09-11
- Yaoyao Ding was added as committer on 2025-11-18
## Project Activity:
- tvm v0.22.0 was released on 2025-10-24.
- tvm-ffi v0.1.5 was released on 2025-12-08.
- tvm-ffi v0.1.4 was released on 2025-11-30.
The community continues to bring improvement in directions of frontend
support, backend enablement, and FFI conventions.
- Improved PyTorch integration for relax
- Improvements on the web runtime to support WebLLM use cases
- tvm-ffi now released as a separate module, serving as an open ABI and FFI
for machine learning systems.
## Community Health:
We see continued contributions to the project, with about 100 commits monthly
in the past quarter. 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 tvm-ffi bring up helps to bring in
community interests to use tvm-ffi as open ABI and FFI convention for machine
learning systems.
-----------------------------------------
Attachment CB: 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.
UIMA: 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 (16 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.
## Project Activity:
uima-ruta-3.5.1 was released on 2025-10-13.
uimaj-3.6.1 was released on 2025-10-01.
## Community Health:
There has not really been any particularly notable or significant
activity to report.
2025_09_24:
gstein:
Always specify the last release date.
"Not in last quarter" could mean one year ago, or five years.
rec: I have no clue what you are talking about. The only "quarter"
in the 09 board report was "past quarter" which is part of the
report template. Besides, I assume all reports come with a date
attached so "last quarter" should be easily resolvable. Also,
there was no release in the period of the last report, so for
no release, no date can be given.
-----------------------------------------
Attachment CC: 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 17 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jonathan Sinovassin-Naïk on 2024-11-25.
- Jerome Blanchard was added as committer on 2025-09-13
## Project Activity:
Version 3.0 of Apache Unomi has been released, addressing key
technical debt by upgrading support to the latest versions of Apache
Karaf and Elasticsearch v9. This update was particularly important
given that Elasticsearch 7 reaches end of support in January 2026
(https://www.elastic.co/support/eol). The upcoming 3.1 release will
shift focus to delivering new features and improvements, including
support for OpenSearch 3, multi-tenancy, and several other
enhancements. Development for 3.1 is complete, with code passing all
unit and integration tests, and the changes are now being reviewed and
integrated in smaller increments. The project will highlight these
additions and improvements as part of its next release communication.
## Community Health:
The community has been very active on the V3.0 release, mostly on github, Slack,
meetings, and the mailing lists, and will continue to be quite active until
V3.1 will be out the door. We now have active contributors from 3 different
companies contributing to the project, which is a very good sign that diversity
is improving. Once 3.1 is out, we hope to be able to reach even more varied
contributors.
-----------------------------------------
Attachment CD: 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
- no activity in the last quarter
## Community Health:
The project is still being used by various organizations, and we do have PMC
members watching things. There is some good development going on at the
primary contributing organization that we hope to be able to contribute in a
few months.
-----------------------------------------
Attachment CE: Report from the Apache Velocity Project [Nathan Bubna]
-----------------------------------------
Attachment CF: Report from the Apache Wayang Project [Zoi Kaoudi]
## Description:
The mission of Apache Wayang is the creation and maintenance of software
related to cross-engine data processing that aims at (i) decoupling
applications from underlying data processing engines, such as Apache Flink,
Apache Spark, databases, or ML systems, and (ii) automatically determining the
optimal combination of engines to execute a given data pipeline using an
optimizer
## Project Status:
Current project status: New TLP, graduated a few weeks ago.
Issues for the board: Nothing major. We just noticed that our project is not
listed under the unregistered trademarks:
https://www.apache.org/foundation/marks/list/#unreg_w
## Membership Data:
Apache Wayang was founded 2025-11-19 (21 days ago)
There are currently 18 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
The last quarter we mainly focused on addressing some issues that came from the
IPMC and fixed bugs in the Python API, while improving our website before
graduation.
We are currently working on fixing some issues with the FileObjectSources and
updating the Flink platform to the latest DataStream API. One major thing we
have planned is a significant improvement of our documentation.
## Community Health:
Community activity has remained steady over the last quarter. Traffic on the
dev list has increased and discussions have been constructive, with an
emphasis on preparing for graduation and coordinating the remaining
IPMC-related tasks.
Participation has been consistent, and we continue to respond promptly to PRs
and technical questions. We are also seeking more contributors not only for
code, but also for documentation, blogs, and other areas.
-----------------------------------------
Attachment CG: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment CH: 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: no issue to report
## 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:
Not many noteworthy events to report for the last quarter, but we agreed to
start working on the next main release, the 11th, based on Spring 7 and JUnit
6 which both came out in the last quarter.
## Community Health:
Community is stable and collaborative, the number of cumulative downloads stays
high. User Hans Schäfer proved to be very collaborative and nice to work with.
-----------------------------------------
Attachment CI: Report from the Apache XML Graphics Project [Clay Leeds]
-----------------------------------------
Attachment CJ: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
The mission of Yetus is the creation and maintenance of software related to
Collection of 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-16 (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-18.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
We've had a quiet quarter, nothing specific to report.
## 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 CK: Report from the Apache ZooKeeper Project [Flavio Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (15 years ago)
There are currently 34 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Damien Diederen on 2024-04-16.
- Christopher Tubbs was added as committer on 2025-11-18
## Project Activity:
- 3.8.5 was released on 2025-09-18.
- Community focus is on 3.10.0 and 4.0.0 as per this email thread:
https://lists.apache.org/thread/q2jcnlfyw2yc4o87b7kppwvw25p1kq0s
## Community Health:
The metrics show a drop in the dev activity post release 3.8.5. There
was an initial burst of interest in the following releases right after
3.8.5, but it did persist throughout this past period. I don't have a
good explanation for the drop, perhaps it can be attributed to contributors
switching context to other things, but again, there is no data to back it.
On the comments from the board on the last report, thanks for raising the
point about the bar being high and Tison for bringing a new committer
forward. It doesn't seem to be a matter of a high bar, but more of PMC
members grooming/mentoring contributors to become committers. Perhaps a
good course of action for the present PMC would be to identify and refresh
the PMC with some new members. It hasn't happened in a while and it is needed.
As part of preparing this report, I am going to propose to the remainder of
the PMC that look into potential candidates from the present active committers
and invite accordingly.
------------------------------------------------------
End of minutes for the December 17, 2025 board meeting.
Index