[raw] the published text, which is the record. [2026] [main index]
The Apache Software Foundation
Board of Directors Meeting Minutes
October 21, 2026
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:02 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2026-10-21T21:00:00&msg=ASF+Board+Meeting
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Zili Chen
Shane Curcuru
Christofer Dutz
Emmanuel Lécharny
Justin Mclean
Jean-Baptiste Onofré
Christopher Schultz
Greg Stein
Sander Striker
Directors Absent:
none
Executive Officers Present:
Craig McClanahan
Ruth Suehle
Matt Sicker
Craig L Russell
Executive Officers Absent:
Daniel Ruggeri
Guests:
Daniel Gruno - joined :03
Sally Khudairi
Alin Jerpelea
Andrew Wetmore
Thomas Neidhart
Dave Fisher
Andrew Musselman
Rich Bowen
Danny Angus
Jarek Potiuk
Whitney P True - joined :03
Daniel Ruggeri - joined :06
Julien Le Dem - joined :06
Henri Yandell - joined :19
Melissa Logan - joined :24
Paul King - joined :25
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of September 16, 2026
See: board_minutes_2026_09_16.txt
Tabled.
B. The meeting of July 15, 2026
See: board_minutes_2026_07_15.txt
Approved by General Consent.
4. Actions Without a Meeting
A. Change the Apache BuildStream Project Chair
WHEREAS, the Board of Directors heretofore appointed Abderrahim Kitouni
(akitouni) to the office of Vice President, Apache BuildStream, and
WHEREAS, the Board of Directors is in receipt of the resignation of Abderrahim
Kitouni 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 Jürg Billeter (juergbi) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Abderrahim Kitouni is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache BuildStream, and
BE IT FURTHER RESOLVED, that Jürg Billeter 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.
Adopted by the unanimous written consent of the Board of Directors on
October 21, 2026 as an Action Without a Meeting (Bylaws 5.12).
5. Executive Officer Reports
A. Board Chair [Sander Striker]
I had the pleasure of attending Community over Code Glasgow. It was great to
see both familiar faces and new faces. I am grateful for the many
conversations that I was able to have there.
I have discussed the reporting direction with representation from tooling and
Community Development, so that the infrastructure gaps that I'm currently
seeing can be addressed.
Community over Code had a hackathon as well, which was well attended. I
definitely enjoyed being in that room and learning a few things.
B. President [Ruth Suehle]
This has been a month of events. Much of my time has been occupied by the
usual flurry leading up to Community Over Code. Thanks to Brian Proffitt, of
course, but everyone from the volunteers to the attendees who had a part in
making our largest post-covid conference a huge success.
Before C/C, we also produced a small event, the fourth Open Source Congress,
which brings together the leaders and policy representatives of open source
foundations around issues of common interest. Past event had been hosted by
LF, Eclipse, and OpenAtom. The event was highly praised for feeling very
"Apache way," and I think for the first time we were able to establish ongoing
work instead of having a once-a-year gathering.
And today, I'll be participating on the ASF's behalf in the OSI's first AI
Salon (https://opensource.org/ai-salon), and thus my apologies if I am unable
to join the meeting.
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig McClanahan]
As I mentioned on the [email protected] list, IgniteSpot (our accounting provider) is
moving bill payments from bill.com to ramp.com instead. Progress is being made
on this, but I will be acquiring more details on how this will impact us
shortly.
One thing you can do if you are a bill approver on bill.com - if you do not
also have a ramp.com user account, ping me and I will send you an invite.
D. Secretary [Matt Sicker]
In September, 47 ICLAs were received and recorded.
E. Executive Vice President [Daniel Ruggeri]
No news is good news: nothing to surface to the board for attention.
F. Vice Chair [Justin Mclean]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
6. Additional Officer Reports
A. VP of Responsible AI [Jeff Genender / Justin Mclean]
See Attachment 12
B. VP of W3C Relations [Andy Seaborne / Emmanuel Lécharny]
See Attachment 13
C. VP of Legal Affairs [Justin Mclean / Justin Mclean]
See Attachment 14
D. VP of Security [Mark J. Cox / Christofer Dutz]
See Attachment 15
Additional officer reports approved as submitted by General Consent.
7. Committee Reports
Summary of Reports
The following reports required further discussion:
# Airavata [jmclean]
# Ambari [jmclean]
# Arrow [elecharny]
# Attic [striker]
# CarbonData [elecharny]
# Directory [gstein]
# Geronimo [jmclean]
# HBase [schultz]
# Johnzon [gstein]
# Legal Affairs [schultz]
# PDFBox [elecharny]
# Pinot [jmclean]
# Ranger [jmclean]
# RocketMQ [jmclean]
# SkyWalking [jmclean]
# Training [striker]
A. Apache Accumulo Project [Marc Parisi / Jean-Baptiste Onofré]
See Attachment A
B. Apache ActiveMQ Project [Christopher L. Shannon / Shane Curcuru]
See Attachment B
C. Apache Airavata Project [Suresh Marru / Jean-Baptiste Onofré]
No report was submitted.
@Jean-Baptiste Onofré: pursue roll call
D. Apache Airflow Project [Bolke de Bruin / Emmanuel Lécharny]
No report was submitted.
E. Apache Ambari Project [Brahma Reddy Battula / Shane Curcuru]
No report was submitted.
@Shane Curcuru: pursue a roll call
F. Apache Answer Project [Ning Qi / Zili Chen]
See Attachment F
G. Apache APISIX Project [Ming Wen / Greg Stein]
See Attachment G
H. Apache Aries Project [Dominik Przybysz / Christopher Schultz]
See Attachment H
I. Apache Arrow Project [Antoine Pitrou / Sander Striker]
See Attachment I
J. Apache AsterixDB Project [Ian Maxon / Christopher Schultz]
See Attachment J
K. Apache Atlas Project [Madhanmohan Neethiraj / Christofer Dutz]
No report was submitted.
L. Apache Attic Project [Hervé Boutemy / Sander Striker]
See Attachment L
M. Apache Auron Project [Lei Wang / Jean-Baptiste Onofré]
See Attachment M
N. Apache Avro Project [Ryan Skraba / Christofer Dutz]
No report was submitted.
O. Apache BookKeeper Project [Enrico Olivelli / Emmanuel Lécharny]
See Attachment O
P. Apache bRPC Project [James Ge / Emmanuel Lécharny]
See Attachment P
Q. Apache BuildStream Project [Abderrahim Kitouni / Sander Striker]
See Attachment Q
R. Apache Calcite Project [Mihai Budiu / Shane Curcuru]
See Attachment R
S. Apache CarbonData Project [Liang Chen / Zili Chen]
See Attachment S
@Jean-Baptiste Onofré: pursue roll call and potential attic
T. Apache Causeway Project [Jörg Rade / Greg Stein]
See Attachment T
U. Apache Celeborn Project [Keyong Zhou / Christopher Schultz]
See Attachment U
V. Apache Celix Project [Pepijn Noltes / Justin Mclean]
No report was submitted.
W. Apache Curator Project [Enrico Olivelli / Emmanuel Lécharny]
See Attachment W
X. Apache CXF Project [Andriy Redko / Zili Chen]
See Attachment X
Y. Apache DataFu Project [Eyal Allweil / Sander Striker]
No report was submitted.
Z. Apache DB Project [Jeffery Painter / Justin Mclean]
See Attachment Z
AA. Apache Directory Project [Shawn McKinney / Greg Stein]
See Attachment AA
AB. Apache DolphinScheduler Project [Lidong Dai / Shane Curcuru]
See Attachment AB
AC. Apache Druid Project [Karan Kumar / Christopher Schultz]
See Attachment AC
AD. Apache Dubbo Project [Jun Liu / Emmanuel Lécharny]
No report was submitted.
AE. Apache EventMesh Project [Eason Chen / Sander Striker]
See Attachment AE
AF. Apache Fineract Project [James Dailey / Christofer Dutz]
See Attachment AF
AG. Apache Flagon Project [Joshua Poore / Greg Stein]
No report was submitted.
AH. Apache Flex Project [Harbs / Christopher Schultz]
See Attachment AH
AI. Apache Fluss Project [Jark Wu / Jean-Baptiste Onofré]
See Attachment AI
AJ. Apache Fory Project [Chaokun Yang / Jean-Baptiste Onofré]
See Attachment AJ
AK. Apache Geronimo Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
@Greg Stein: pursue roll call or possible attic
AL. Apache Gluten Project [Weiting Chen / Emmanuel Lécharny]
See Attachment AL
AM. Apache Gravitino Project [Jerry Shao / Sander Striker]
See Attachment AM
AN. Apache Guacamole Project [Mike Jumper / Zili Chen]
See Attachment AN
AO. Apache Hadoop Project [Xiaoqiao He / Greg Stein]
See Attachment AO
AP. Apache HBase Project [Duo Zhang / Christopher Schultz]
See Attachment AP
@Christopher Schultz: follow up about CI issues with infra and security.
AQ. Apache HertzBeat Project [Chao Gong / Sander Striker]
See Attachment AQ
AR. Apache Hive Project [Naveen Gangam / Christofer Dutz]
See Attachment AR
AS. Apache Iggy Project [Kranti Parisa / Justin Mclean]
No report was submitted.
AT. Apache Incubator Project [Justin Mclean / Justin Mclean]
See Attachment AT
AU. Apache InLong Project [Charles Zhang / Zili Chen]
No report was submitted.
AV. Apache James Project [Benoit Tellier / Christofer Dutz]
See Attachment AV
AW. Apache Jena Project [Andy Seaborne / Shane Curcuru]
See Attachment AW
AX. Apache JMeter Project [Bruno Demion / Greg Stein]
See Attachment AX
AY. Apache Johnzon Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
@Jean-Baptiste Onofré: follow up about chair
AZ. Apache JSPWiki Project [Alex O'Ree / Emmanuel Lécharny]
See Attachment AZ
BA. Apache Kudu Project [Andrew Wong / Zili Chen]
See Attachment BA
BB. Apache Kvrocks Project [Mingyang Liu / Shane Curcuru]
See Attachment BB
BC. Apache Lucene.Net Project [Shad Storhaug / Emmanuel Lécharny]
See Attachment BC
BD. Apache Mahout Project [Jie-Kai Chang / Jean-Baptiste Onofré]
See Attachment BD
BE. Apache Maven Project [Hervé Boutemy / Shane Curcuru]
See Attachment BE
BF. Apache MINA Project [Thomas Wolf / Justin Mclean]
See Attachment BF
BG. Apache MyFaces Project [Bernd Bohmann / Christopher Schultz]
See Attachment BG
BH. Apache NiFi Project [David Handermann / Christofer Dutz]
See Attachment BH
BI. Apache Nutch Project [Sebastian Nagel / Sander Striker]
See Attachment BI
BJ. Apache NuttX Project [Alin Jerpelea / Greg Stein]
See Attachment BJ
BK. Apache OpenJPA Project [Mark Struberg / Sander Striker]
See Attachment BK
BL. Apache OpenMeetings Project [Maxim Solodovnik / Justin Mclean]
See Attachment BL
BM. Apache OpenOffice Project [Dave Fisher / Shane Curcuru]
See Attachment BM
BN. Apache OpenWebBeans Project [Mark Struberg / Christopher Schultz]
See Attachment BN
BO. Apache ORC Project [William Hyun / Christopher Schultz]
No report was submitted.
BP. Apache Parquet Project [Julien Le Dem / Zili Chen]
See Attachment BP
BQ. Apache PDFBox Project [Andreas Lehmkühler / Emmanuel Lécharny]
See Attachment BQ
@Emmanuel Lécharny: follow up about report accuracy
BR. Apache Pig Project [Koji Noguchi / Emmanuel Lécharny]
No report was submitted.
BS. Apache Pinot Project [Kishore G / Greg Stein]
No report was submitted.
@Greg Stein: pursue roll call
BT. Apache Pony Mail Project [Rich Bowen / Christofer Dutz]
See Attachment BT
BU. Apache Ranger Project [Selvamohan Neethiraj / Emmanuel Lécharny]
No report was submitted.
@Emmanuel Lécharny: pursue possible chair rotation
BV. Apache Ratis Project [Tsz-wo Sze / Jean-Baptiste Onofré]
See Attachment BV
BW. Apache Reqsign Project [Zili Chen / Zili Chen]
See Attachment BW
BX. Apache ResilientDB Project [Mohammad Sadoghi / Christopher Schultz]
See Attachment BX
BY. Apache RocketMQ Project [Xiaorui Wang / Greg Stein]
No report was submitted.
@Greg Stein: pursue roll call
BZ. Apache Rya Project [Adina Crainiceanu / Sander Striker]
No report was submitted.
CA. Apache Samza Project [Jagadish Venkatraman / Shane Curcuru]
No report was submitted.
CB. Apache SeaTunnel Project [Jun Gao / Christopher Schultz]
See Attachment CB
CC. Apache ServiceComb Project [Zhangjian He / Justin Mclean]
No report was submitted.
CD. Apache Shiro Project [Lenny Primak / Zili Chen]
See Attachment CD
CE. Apache SkyWalking Project [Sheng Wu / Sander Striker]
See Attachment CE
CF. Apache Sourcelume Project [Jamie Goodyear / Zili Chen]
See Attachment CF
CG. Apache Steve Project [Greg Stein / Greg Stein]
See Attachment CG
CH. Apache StreamPark Project [Huajie Wang / Shane Curcuru]
See Attachment CH
CI. Apache Struts Project [René Gielen / Jean-Baptiste Onofré]
See Attachment CI
CJ. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Justin Mclean]
See Attachment CJ
CK. Apache Tcl Project [Georgios Petasis / Shane Curcuru]
No report was submitted.
CL. Apache Tez Project [László Bodor / Emmanuel Lécharny]
See Attachment CL
CM. Apache Thrift Project [Jens Geyer / Greg Stein]
See Attachment CM
CN. Apache Tika Project [Tim Allison / Christofer Dutz]
See Attachment CN
CO. Apache TinkerPop Project [Kelvin Lawrence / Jean-Baptiste Onofré]
See Attachment CO
CP. Apache Traffic Server Project [Bryan Call / Sander Striker]
See Attachment CP
CQ. Apache Training Project [Justin Mclean / Justin Mclean]
See Attachment CQ
CR. Apache Wayang Project [Zoi Kaoudi / Emmanuel Lécharny]
See Attachment CR
CS. Apache Web Services Project [Daniel Kulp / Justin Mclean]
No report was submitted.
CT. Apache Zeppelin Project [Jongyoul Lee / Christopher Schultz]
See Attachment CT
Committee reports approved as submitted by General Consent.
8. Special Orders
A. Terminate the Office of Vice President, Finance
WHEREAS, the Board of Directors deems it no longer necessary to maintain the
office of Vice President, Finance;
NOW, THEREFORE, BE IT RESOLVED, that the office of "Vice President, Finance"
is hereby terminated.
Special Order 8A, Terminate the Office of Vice President,
Finance, was approved by Unanimous Vote of the directors present.
B. Increase Staffing Budget
WHEREAS, the Board of Directors has determined that additional
capacity is required to support the Foundation's operations;
and
WHEREAS, the Apache Software Foundation maintains a
consolidated Staffing budget line in order to protect the
privacy of individual compensation arrangements; and
WHEREAS, the process of assembling and managing the
Foundation's annual budget is directed by the President;
NOW, THEREFORE, BE IT RESOLVED, that the Staffing budget line
be and hereby is increased by $500,000 for the current fiscal
year; and be it further
RESOLVED, that the President is authorized and directed to
incorporate this adjustment into the Foundation's budget in the
ordinary course of budget assembly and management.
Special Order 8B, Increase Staffing Budget, was tabled.
C. Change the Apache OpenNLP Project Chair
WHEREAS, the Board of Directors heretofore appointed Jeffrey T. Zemerick
(jzemerick) to the office of Vice President, Apache OpenNLP, and
WHEREAS, the Board of Directors is in receipt of the resignation of Jeffrey T.
Zemerick from the office of Vice President, Apache OpenNLP, and
WHEREAS, the Project Management Committee of the Apache OpenNLP project has
chosen by vote to recommend Martin Wiesner (mawiesne) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Jeffrey T. Zemerick is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache OpenNLP, and
BE IT FURTHER RESOLVED, that Martin Wiesner be and hereby is appointed to the
office of Vice President, Apache OpenNLP, 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 8C, Change the Apache OpenNLP Project Chair, was
approved by Unanimous Vote of the directors present.
9. Discussion Items
10. Review Outstanding Action Items
* Zili Chen: follow up about trademark issue
[ Brand Management 2026-09-16 ]
Status: Done. The GLUTEN PMC has replied.
* https://lists.apache.org/thread/t9m98lzsc79937z7634np2y1bfomh0xm
* https://github.com/apache/gluten/issues/11438#issuecomment-5661629938
There may still be ongoing issues, but the specific board issue reported
from the Brand Committee that the PMC didn't respond to has been resolved.
* Sander Striker: pursue roll call
[ cTAKES 2026-09-16 ]
Status:
* Jean-Baptiste Onofré: The 1.0.3 betas listed as releases haven't been
voted on
[ DevLake 2026-09-16 (created by Justin Mclean) ]
Status:
* Greg Stein: follow up about chair responsibilities
[ Flagon 2026-07-15 ]
Status:
* Christopher Schultz: pursue roll call
[ Flex 2026-09-16 ]
Status:
* Greg Stein: pursue roll call
[ Geronimo 2026-04-15 ]
Status: attention is present, but so far it sounds like the
correct approach is "spin out components" rather than a
complete TLP move to the Attic. "spin out" to a new TLP
designated to support those? To Tomcat or TomEE or
Commons? ... still waiting on further feedback/roll-call
* Justin Mclean: Follow up with the Helix PMC. The 2.0.0 and 2.0.1 release
votes each had only two binding +1s from PMC members.
[ Helix 2026-09-16 (created by Justin Mclean) ]
Status: Completed. email sent / PMC responded / advice given
* Jean-Baptiste Onofré: follow up about websites
[ Iceberg 2026-09-16 ]
Status:
* Shane Curcuru: Ask whether the Ignite 3 project is still a going concern,
and if not, when will users be notified?
[ Ignite 2026-08-19 (created by Justin Mclean) ]
Status:
* Christopher Schultz: reach out about communication issues
[ IoTDB 2026-06-17 ]
Status: Will reach-out to IOTDB in mid-July.
* Christopher Schultz: discuss failed roll call and future direction
[ Kylin 2026-05-20 ]
Status: https://lists.apache.org/thread/fzy0hjl46fmy2w8c6woljjq0co5zff4j
The PMC has sent invitations to some new committers and PMC members.
2026-09-15: One PMC member has been added
(https://lists.apache.org/thread/b2zb753ntshywl0ntd94s3lqcqcfyr3r).
One new committer has been invited, but I don't see an acceptance of that
invitation yet.
I'm still concerned about the project's ability to build its community, though
it is making slow progress.
I'm also concerned about the slow response to a number of security issues that
seems to be accumulating.
* Justin Mclean: Determine the board's position on whether security triage
and release management are "paying for development" under
the Targeted Sponsorship Policy, and report back.
[ Logging Services 2026-08-19 (created by Justin Mclean) ]
Status:
* Emmanuel Lécharny: follow up on roll call
[ Lucene.Net 2026-09-16 ]
Status: Completed. The role call passed.
* Zili Chen: follow up about project viability
[ MADlib 2026-04-15 ]
Status: Follow up - https://lists.apache.org/thread/781rspl421vcmclzjdqlstzq8b5vgf4m
Seems MADlib didn't reply to Cloudberry's collaboration suggestion.
* Christopher Schultz: follow up about AI code usage
[ OpenDAL 2026-06-17 ]
Status:
* Greg Stein: talk to Pinot PMC about communication channels
[ Pinot 2025-11-19 ]
Status:
* Christopher Schultz: let know about release vote guidelines
[ Pulsar 2026-09-16 ]
Status:
* Sander Striker: pursue a roll call
[ Rya 2026-07-15 ]
Status: Done. https://lists.apache.org/thread.html/gg9r7gowb1d94l3z81rykwdpqb3f00mk:
2 +1, 1 +0. I do want to point out the comment by @rbowen in
https://agenda.apache.org/meetings/2026-01-21#rya as a reminder in discussion.
* Shane Curcuru: pursue roll call
[ Samza 2026-09-16 ]
Status: Done. No responses; proposed next step emailing dev@/private@ saying Samza will
likely move to Attic at November board meeting.
* Justin Mclean: roll call
[ SDAP 2026-08-19 ]
Status: Completed. email sent 4 PMC members responded with +1
* Shane Curcuru: follow up about licensing
[ SIS 2026-02-18 ]
Status: Can be closed: this is a longer-term strategy issue that doesn't have a
current board solution.
* Shane Curcuru: message all PMCs to improve board reports and discuss
"Emeritus" concept for PMCs.
[ Superset 2026-05-20 ]
Status:
* Justin Mclean: Roll Call for Xalan
[ Xalan 2026-08-19 (created by Sander Striker) ]
Status: email sent only 2 PMC members responded with +1
* Jean-Baptiste Onofré: follow up about Xerces-C EOL
[ Xerces 2026-06-17 ]
Status:
11. Unfinished Business
12. New Business
13. Announcements
14. Adjournment
Adjourned at 21:59 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period September 2026
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Daan Hoogland continues to provide some very welcome assistance with trademark
issues.
Responded to the following queries, liaising with projects as required:
- Approved name search for YINYANG (with caveats), REQSIGN, POUCHDB,
- OPENOFFICE approved the use of their mark in a book
- Worked with FLUSS PMC to correct the marketing of a FLUSS based event
- Provided product naming advice for a series of products based on Apache
projects
- Updated the list of registered and unregistered marks
- Provided advice that the ASF would object to a proposed product name
- Approved the use of project logos for a conference booth
- Passed request to use the foundation logo to represent Maven projects in a
software tool to M&P
- Reviewed new logo for SOURCELUME
* REGISTRATIONS
Started the process to register the GRAILS logos and work mark.
The SEATA mark has been transferred to the ASF.
Instructed counsel to allow the class 38 registration for BROOKLYN to lapse.
* INFRINGEMENTS
The GLUTEN PMC is working through resolving a series of issues.
The AGE PMC were advised to start a registration for AGE to assist with
addressing repeated potential infringements.
The potentially conflicting registration of FLINK in the EU is likely to be
resolved by limited in the registration and putting a co-existence agreement
in place.
Counsel have been instructed to start cancellation proceedings against a
FREEMARKER registration the ASF considers to have been made in bad faith.
GitHub have handed control of the AIRFLOW related NPM names that had been
registered by a squatter to the ASF.
A proposed co-existence agreement has been received by the CLOUDSTACK PMC in
response to them reaching out to a potentially confusing product.
No progress from the SPARK PMC regarding a potential infringement.
The SPARK PMC appears to have stalled making progress in addressing a range of
product naming issues with multiple 3rd parties.
The issues with a downstream vendor with multiple infringements of ASF marks
appear to have been resolved by a website redesign.
No update from the XMLGRAPHICS PMC regarding progress of the complaint with
GitHub regarding a potential third-party infringement of FOP.
-----------------------------------------
Attachment 2: Report from the VP of Conferences [Brian Proffitt]
The 2026 Community Over Code Glasgow is done, and on behalf of the planners, I
am pleased to report the event was a very strong success.
In total, 465 people attended both the Lakehouse Day and Community Over Code
events, out of 479 registered, a 97.1% attendance rate, and a 63% increase
from Community Over Code Minneapolis. We will be gathering data in a
post-conference survey soon, but my initial anecdotal findings point to the
European location, the very strong community feeling many people reported from
the 2025 conference, and an excellent set of content, including the co-located
Airflow Contributor Day and Lakehouse Day events.
The Community Over Code Sydney event, to be held November 18-19, had its
schedule posted on Oct. 16[1]. Ticket sales are low, but now that the Glasgow
event is over, the Sydney planning team will be in full gear to prepare and
market the event.
Finally, the Open Source Congress event was hosted by the ASF in Halifax, Nova
Scotia, on September 22-23, with multiple foundations across the open source
ecosystem engaging in lively and productive discussions. A report, formatted
under Chatham House Rule, will be created sometime in November and shared
publicly.
[1] https://communityovercode.apache.org/events/sydney-2026/schedule
-----------------------------------------
Attachment 3: Report from the VP of Data Privacy [Christian Grobmeier]
Nothing special to report.
Several privacy issues from individuals where handled.
A detailled report migth follow next month.
-----------------------------------------
Attachment 4: Report from the VP of Diversity and Inclusion [Daniel Gruno]
-----------------------------------------
Attachment 5: Report from the VP of ECMA Relations [Piotr Karwasz]
TC-54 submitted three standard proposals to the Ecma Executive Committee
(ExeCom):
- **Package URL (PURL), second edition** —
https://ecma-tc54.github.io/ECMA-427/
- **Transparency Exchange API (TEA), first edition** — a format-agnostic
protocol for exchanging supply-chain artefacts (SBOMs, VEX documents,
attestations, lifecycle events) between publishers and consumers:
https://ecma-tc54.github.io/ECMA-xxx-TEA/
- **Version Range Specifier (VERS), first edition** — a URI-based syntax for
expressing software version ranges, developed alongside and complementing
PURL: https://ecma-tc54.github.io/ECMA-xxx-VERS/
The ExeCom met in Geneva on 7–8 October; the proposals now go forward to the
132nd Ecma General Assembly on 8–9 December 2026 for adoption. All three are
directly relevant to ASF projects publishing supply-chain metadata.
Work in the TC-54 task groups otherwise continues as usual.
-----------------------------------------
Attachment 6: Report from the VP of Fundraising [Bob Paulin]
-----------------------------------------
Attachment 7: Report from the VP of Infrastructure [Danny Angus]
General
-------
CI limitations remain one of the top Infra issues projects face under the
onslaught of AI based PRs, both security and for other purposes. Infra
continues to increase CI provisioning where possible, and at the Community
Over Code conference solicited input and opinions on what projects in the
Foundation need and expect from Infra. We welcome feedback from across the
Foundation and our users.
DKIM/Mail Delivery Problem Resolution
-------------------------------------
Infra continues to tighten controls around DKIM, but most delivery issues have
now been resolved.
MFA Rollout
-----------
Infra has rolled out MFA as part of the recent lists.apache.org update, and is
now in full production status.
Atlassian Cloud Migration
-------------------------
Migration preparation continues, with only a few blockers remaining. Active
migrations are expected to begin before the end of calendar 2026.
Community News
--------------
The Infra team was present in force at Community Over Code Glasgow, offering a
full track of talks and discussions, and engaging in hallway conversations
with all and sundry who had infrastructure-related questions or suggestions.
The Infra track had 7 sessions, most of which attracted audiences of between
15-40 people. VP-Infra's State of Infra Discussion ran long and touched on
topics ranging from what projects expect from infrastructure to how to
optimize builds.
Ricardo Anguiano, at his first ASF conference, gave a 40-minute talk entitled
"Distributed Denial of Service: Traffic Characterization and Mitigation".
Presentation slides and a video recording will be available later.
About fifty people took active and enthusiastic part in Games Night,
confirming the role that event plays in creating a space for joy at the ASF.
A key takeaway for Infra from the conference was that community is our
greatest strength, especially when it comes to sharing our resources. The
build optimization workshop didn't just yield suggestions for build
optimizations, but also made abundantly clear that all of the projects are
expected to share our limited resources.
Another pleasant 'win' from the conference was the number of people who
indicated they would like to get more involved in supporting or extending ASF
infrastructure.
The regular series of online roundtables will see some changes starting with
the session on November 4, 1700UTC. There will be two topic presentations
instead of one, one from Infra and one from Tooling. Participants will be
asked to hold questions and comments for the discussion period after second
presentation. The roundtables will expand from 60 to 90 minutes to accommodate
these changes.
-----------------------------------------
Attachment 8: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Communications
* Press releases
* Announced Keynote Speakers for Community Over Code Glasgow 2026
* Announce FY26 annual report
* Published blog
* Security scanning at Foundation scale
* Dev.to blog syndication
* ASF Plus One Newsletter: August 2026
* Apache Geode 2.0, Part III: Lessons Learned and the Path Forward
* Beyond the Hardware Hub: How ALC Taipei Turned Computex 2026 into a
Milestone for the Apache Way
* From Friction to Flow: How ASF Tooling Is Lowering Barriers for
Maintainers
* Security scanning at Foundation scale
* Issued September issue of Plus One newsletter
* Subscriber list now totals 5,802 (+539 new subscribers in September)
* Total sent: 4,800 | Unique opens: 1,014 | Open rate: 21%
* Ongoing: Social media for Community Over Code Glasgow and Sydney events
* Updated the PR boilerplate for the Foundation to remove individual projects
and numbers
Foundation Brand
* Published updated brand guide with new oak leaf trademark
* Provided RAI with 2nd round of logo revisions
Foundation Digital
* Continued updating CommunityOverCode.org archived events along with
additional updates to the main site
* Completed C/C digital advertising for the Glasgow event
* Researched social analytics for Foundation vs event channels to determine
whether to separate event content from the main channels going forward
Social Media Overview
The highest-performing pieces of content for September include the RAI blog
and the ASF Plus One newsletter.
Social Highlights (X + Bluesky + Fosstodon + LinkedIn)
* Total Audience: 152,570
* X: 66,568
* Bluesky: 1,253
* Fosstodon: 241
* LinkedIn: 84,508
* Total Posts:
* X / Bluesky / Fosstodon / Bluesky: 85
* LinkedIn: 15
* Total Engagements: 3,691 (X 3,702 + LinkedIn 501 + BlueSky 118)
Website Analytics
701,058 visits, 700,917 unique visitors -3.3%
2 min 5s average visit duration +5%
59% visits have bounced (left the website after one page) 0%
2.3 actions (page views, downloads, outlinks, internal site searches) per
visit 0%
1,237,391 pageviews, 911,729 unique pageviews -2.3%
23 total searches on your website, 13 unique keywords -55.8%
94,258 downloads, 66,963 unique downloads -0.3%
264,993 outlinks, 193,587 unique outlinks -6.7%
-----------------------------------------
Attachment 9: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
Report deferred to next month. Nothing urgent.
-----------------------------------------
Attachment 10: Report from the VP of Tooling [Dave Fisher]
## Apache Trusted Releases
We fixed a number of bugs and a couple of feature gaps. We demonstrated and
discussed our current state at Community over Code Glasgow. We are in a good
state. We collected several good ideas about CI builds and support for
Security driven release scenarios.
- https://releases.apache.org
We discussed next steps around handling distribution channels in order to
co-ordinate full knowlege of all of an ASF project release.
One request was to assure that source only release SBOMs are easy to create.
We will investigate
- https://release-catalog.apache.org
We need PMCs to help curate their identified list of sub-projects.
Including the following is an important part of the CRA compliance
attestations.
- ECMA-424 CycloneDX Bill of materials specification
- ECMA-427 Package-URL (PURL) specification
- ECMA-428 Common Lifecycle Enumeration (CLE) specification
- https://lists.apache.org/[email protected]
This mailing list records releases identified by ATR as they are made.
ATR Releases since September 1, 2026
- ATR Maven Plugin 1.0.0-beta-1
- Maven Compiler Plugin 3.16.0
- Maven Dependency Analyzer 1.17.2
- Maven Plugin Tools 3.16.0
- Maven Plugin Tools 4.0.0-beta-3
- Asyncband (Incubating) 0.7.2
- Maven Deploy Plugin 3.2.0
- Maven Install Plugin 3.2.0
- OpenDAL 0.59.2-rc.2
- Maven Deploy Plugin 4.0.0-beta-3
- Maven Install Plugin 4.0.0-beta-3
- Maven Artifact Plugin 3.7.0
- Maven Resolver 2.0.23
- OpenDAL 0.59.3-rc.1
- Parent POM 40
- Maven Project Parent POMs 50
- Asyncband (Incubating) 0.7.3
- Maven Resolver 2.0.24
- OpenDAL 0.59.4-rc.2
## Board Agenda Tool
Sander is working on splitting out a Roster tool and an LDAP tool from BAT
with the use of a PubSub event stream to communicate. Work has begun on
accumulating the requirements for the Secretary's Workbench
## Responsible AI Tooling
We did ASVS scans using self-hosted models. These produce very good results.
ATR has no critical findings, less than 10 medium findings, and many small low
findings.
## Next Tooling Projects
We are going to focus on these small projects:
1. A developer sandbox application template. This will support new volunteers
trying out their whimsy.
2. Improvements to the asfquart framework. Many of our recent ASVS findings
are in this framework.
3. A noisy-token python module. This is the correct direction for work already
built.
-----------------------------------------
Attachment 11: Report from the VP of Travel Assistance [Gavin McDonald]
Current Events
==============
Community Over Code - Glasgow
------------------------------
This event was a great success, for the community but also
for our 21 TAC recipients whom all did a great job and helped
make the event a huge success.
Post Conference surveys are due to go out soon.
Monthly Meetings
================
An in person TAC meeting was due to take place in Glasgow but
we could not get together unfortunately. Will organize an online
one soon.
Future Events
=============
Looking into supporting a few people to go to Fosdem.
TAC has agreed to provide budget for a welcome meal for students and TAC
members/volunteers for the Sydney C/C event in November.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support.
Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still
to be done.
TAC App
=======
The Groovy/Grails folks during C/C Glasgow started a replacement version to be
trialed over the coming months.
-----------------------------------------
Attachment 12: Report from the VP of Responsible AI [Jeff Genender]
* Survey for AI usage completed and results completed.
* LLMAO is passing traffic from ASVS scans and other pipelines on Gofannon
along with coding agents including Claude Code, Grok Build, pi, and Copilot.
Projects onboarded include Spark, Airflow, Solr, Sourcelume, Sling,
Fineract, and Groovy.
* Refractory (RAI platform) with Memory design docs and work plan drafted and
distributed.
* Presented on a panel covering "AI Policy for Open Source" at the Open Source
Congress, leading to discussions with other foundations about adopting and
contributing to the RAI platform.
* Public fork of Gofannon set up for regular upstream updates back to AI
Alliance pulled from our maintenance fork
(at https://github.com/apache/tooling-gofannon-fork)
* RAI Hackathon at Community Over Code for setting up LLMAO occurred
on Oct 12 -
Signed up Apache Sling, Apache Solr, Apache Sourcelume,
Apache Spark, and others for using our hosted LLMs.
* RAI Roundtable at Community Over Code occurred on Oct 12 - Successful
Roundtable with standing-room attendance. Great discussion with the panel
and special thanks to Professor Tim Storer for attending and contributing.
* Blog post explaining items RAI has completed so far at
https://news.apache.org/foundation/entry/what-the-asf-responsible-ai-initiative-has-built-so-far
* Request for budget for platform development and operation entered in Special
Order 7-B Increase Staffing Budget
* Working with Fundraising regarding
1. current RAI-related in-kind contributions
2. vetting proposed a Targeted Donation of an AI cybersecurity
code review platform, and a Targeted cash donation to benefit a
named Apache project
3. a possible AI tool entering the Incubator
* Spoke to VP of Legal and will introduce him to the proposed legal firm for
pro-bono work once the law firm approves us via their pro-bono Board.
-----------------------------------------
Attachment 13: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 14: Report from the VP of Legal Affairs [Justin Mclean]
September was quieter on the public legal lists than August, with most of the
traffic on the terms of AI tools. There are currently five open LEGAL JIRA
issues. Two new issues were raised during September and one so far in October,
and none have been closed since the last report.
LEGAL-737 asks how Apache Fesod (Incubating) should handle Alibaba copyright
headers in files derived from EasyExcel. LEGAL-738 asks whether Hive can host
internal test datasets as GitHub release assets.
The board passed the resolution dissolving the Legal Affairs Committee and
making VP Legal Affairs responsible for the Foundation’s legal policies.
Nothing changes in practice: committee members stay on, and the lists, LEGAL
JIRA and the pages under /legal/ remain as they are. The board also confirmed
that the AI policy threads can continue on legal-discuss.
The proposal to make the Generated-by record mandatory had no support, so it
stays a recommendation. The generative tooling guidance now lists
Co-authored-by alongside Generated-by, as that is what most tools add by
default. A duplicated paragraph on copyrightability was also removed.
SpaceXAI’s updated terms for Grok led to a long discussion. Its acceptable use
policy now bars using the service or its output to help develop products or
services that compete with SpaceXAI.
The licensing FAQ now has an entry saying the ASF endorses no translation of
the Apache License, and links, without endorsement, to OpenAtom’s Chinese
translation, which has had its publisher’s own legal review.
The release policy FAQ now mentions the Apache Trusted Releases platform,
currently in beta, for staging release candidates.
RAI has published a draft best practice page on the risks of using AI tools,
which covers some of the same vendor terms. The RAI pages are currently not in
line with ASF policy. I discussed this with VP RAI, who agreed that the RAI
site will link to the existing legal policy rather than restate it. We also
discussed changes to the existing legal page. VP RAI will introduce me to the
pro bono counsel.
-----------------------------------------
Attachment 15: Report from the VP of Security [Mark J. Cox]
September
* MFA progress, now enabled for list archives. The next steps are code repos
(notably gitbox and svn) and cwiki/jira.
https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=MFA+project+phase+1%3A+Security
* The volume of incoming security reports was stable compared to last month,
but improvements to handle this kind of load remain a priority. The number
of open reports is still rising, we're planning more active escalations.
* The DKIM improvements we helped Infra with have been rolled out, which
should improve email deliverability for ASF mailing lists.
* Security Team will be represented at C/C Glasgow, including "office hours"
sessions and a talk on responsible release automation.
Stats for Sept 2026:
22 [license confusion]
28 [support request/question not security notification]
2 [report/question relating to dependencies]
1 [reports held back pending batch sampling]
Security reports: 1043 (last months: 1259, 750, 574, 739, 515, 386)
49 ['httpd']
35 ['tomcat']
31 ['casbin', 'cloudstack']
28 ['camel']
26 ['nifi']
25 ['airflow', 'ozhera']
20 ['commons']
18 ['celix']
17 ['ofbiz', 'streampark']
16 ['dolphinscheduler', 'guacamole', 'hbase', 'ranger',
'superset']
15 ['nuttx', 'solr', 'thrift']
14 ['dubbo', 'openoffice', 'resilientdb']
13 ['answer', 'hugegraph', 'seatunnel']
12 ['website or other infrastructure']
12 ['arrow', 'inlong', 'pulsar']
11 ['artemis']
10 ['apisix', 'ignite', 'roller', 'skywalking']
9 ['spark']
8 ['activemq', 'hertzbeat', 'kafka', 'paimon', 'syncope']
7 ['airavata', 'linkis', 'mina', 'zookeeper']
6 ['allura', 'avro', 'beam', 'burr', 'couchdb', 'directory',
'doris', 'jspwiki', 'struts', 'wicket', 'xmlgraphics']
5 ['age', 'atlas', 'brpc', 'devlake', 'druid', 'jackrabbit',
'knox', 'kvrocks', 'mynewt', 'plc4x', 'rocketmq', 'shiro',
'subversion', 'tapestry', 'tomee', 'yunikorn']
4 ['datasketches', 'fluss', 'impala', 'iotdb', 'logging',
'openmeetings', 'pinot', 'rivet', 'sling', 'spamassassin',
'trafficserver', 'unomi']
3 ['ambari', 'apr', 'aries', 'auron', 'buildstream', 'cordova',
'hive', 'hudi', 'iggy', 'jena', 'juneau', 'kylin', 'kyuubi',
'myfaces', 'pekko', 'polaris', 'rya', 'seata', 'serf',
'shardingsphere', 'sis', 'storm', 'tez', 'tika', 'velocity',
'zeppelin']
2 ['bval', 'cxf', 'datafusion', 'eventmesh', 'flink',
'gravitino', 'hop', 'karaf', 'ossie', 'otava', 'ozone',
'parquet', 'pdfbox', 'poi', 'qpid', 'shenyu', 'singa', 'ws']
1 ['ant', 'axis', 'bigtop', 'caldera', 'cassandra', 'celeborn',
'cloudberry', 'drill', 'fesod', 'fineract', 'fory',
'freemarker', 'geode', 'gobblin', 'grails', 'hamilton',
'httpcomponents', 'iceberg', 'james', 'kie', 'livy',
'lucenenet', 'maven', 'opendal', 'orc', 'pig', 'ratis',
'samza', 'servicecomb', 'steve', 'stormcrawler',
'streampipes', 'tinkerpop', 'xerces']
In total, as of 1st October 2026, we're tracking 2858 (last months: 2356,
1574, 1314) open issues across 212 projects, median age 54 days (last months:
43, 63, 54). 547 of those issues have CVE names assigned. 58 (last months: 44,
48, 29) of these issues, across 27 projects, are older than 365 days.
* openoffice (Health red): Several issues in OpenOffice, including
CVE-2026-59265 which is already public but only fixed in 4.1.17 which is
expected before October 17th. (Last update: 2026-10-07)
* apr (Health amber): releases are few and far-between (Last update:
2026-06-29)
* spark (Health amber): the project has a backlog of security reports to be
triaged (Last update: 2026-05-06)
* superset (Health amber): while the project is actively publishing fixes
to security issues each release, there is concern about a growing backlog.
(Last update: 2026-07-01)
-----------------------------------------
Attachment A: Report from the Apache Accumulo Project [Marc Parisi]
## Description:
The mission of Apache Accumulo is the creation and maintenance of software
related to a robust, scalable, distributed key/value store with cell-based
access control and customizable server-side processing.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: None
## Membership Data:
Apache Accumulo was founded 2012-03-20 (14 years ago)
There are currently 44 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 11:8.
Community changes, past quarter:
- Arbaaz Khan was added to the PMC and as a committer on 2026-08-24.
- Eight PMC members moved to emeritus status on 2026-09-30, following a roll
call for inactive PMC members.
## Project Activity:
- 2.1.5 [1] contained bug fixes and stability improvements.
- 2.1.6 [2] fixed CVE-2026-62764 [3], which let an authenticated user
without system permissions shut down Accumulo services in 2.1.4 and 2.1.5.
- 4.0.0-alpha-1 [4] is the first preview of 4.0, which supports elastic
deployments and multiple active Managers. Work continues toward a final
4.0.0 [5].
- We added a SECURITY.md [6] describing our threat model and how to report
vulnerabilities.
- With help from INFRA [7], we renamed several side repositories to remove
Fluo from their names and archived those no longer maintained.
### Releases:
- accumulo-4.0.0-alpha-1 was released on 2026-09-24.
- accumulo-2.1.6 was released on 2026-07-17.
- accumulo-2.1.5 was released on 2026-07-08.
## Community Health:
Overall community health is good and GitHub activity remains consistent, with
about 80 commits this quarter. The board approved a new PMC Chair, resolving
the concern from our last report. The dev list (44 emails this quarter)
carried release votes and design discussions, including Java 21 virtual
threads, a standard key format for command-line tools, and whether to create
a separate security mailing list.
## Links
[1] https://accumulo.apache.org/release/accumulo-2.1.5/
[2] https://accumulo.apache.org/release/accumulo-2.1.6/
[3] https://www.cve.org/CVERecord?id=CVE-2026-62764
[4] https://accumulo.apache.org/release/accumulo-4.0.0-alpha-1/
[5] https://github.com/apache/accumulo/milestone/25
[6] https://github.com/apache/accumulo/blob/main/SECURITY.md
[7] https://issues.apache.org/jira/browse/INFRA-28238
-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project [Christopher L. Shannon]
## Description:
The mission of Apache ActiveMQ is the creation and maintenance of software
implementing a distributed messaging system
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ActiveMQ was founded 2007-01-16 (20 years ago)
There are currently 65 committers and 29 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 Matt Pavlovich on 2023-12-06.
- No new committers. Last addition was Jean-Louis Monteiro on 2026-02-03.
## Project Activity:
- 6.2.10 was released on 2026-09-22.
- 5.19.11 was released on 2026-08-29.
- 6.3.2 was released on 2026-08-29.
- 6.3.1 was released on 2026-08-06.
- 6.2.9 was released on 2026-08-06.
- 5.19.10 was released on 2026-08-06.
- 6.3.0 was released on 2026-07-24.
- 6.2.8 was released on 2026-07-24.
- 5.19.9 was released on 2026-07-24.
- 5.19.8 was released on 2026-06-29.
- 6.2.7 was released on 2026-06-29.
- 5.19.7 was released on 2026-05-31.
- Project is working towards v6.4.0 and other patch releases.
The PMC has been focused on addressing additional security reports as well as
resuming work towards v6.4.0, which is due to be released in the next couple
of weeks. The number of security reports has slowed down and allowed progress
to be made towards adding multiple new JMS 3.1 features for v6.4.0. Several
other major new features are being planned including JMS shared subscription
support and KahaDB journal compaction. It was recently announced that the
5.19.x version of ActiveMQ is deprecated and no longer supported as of
02-28-2027.
## Community Health:
We have a sustained activity on the mailing lists. We also see new
contributors who submitted new PRs. We are are moving forward on JMS 3.1 and
future 6.x releases as well as preparing a proposal for runtime for ActiveMQ
7.
-----------------------------------------
Attachment C: Report from the Apache Airavata Project [Suresh Marru]
-----------------------------------------
Attachment D: Report from the Apache Airflow Project [Bolke de Bruin]
-----------------------------------------
Attachment E: Report from the Apache Ambari Project [Brahma Reddy Battula]
-----------------------------------------
Attachment F: Report from the Apache Answer Project [Ning Qi]
## Description:
The mission of Apache Answer is the creation and maintenance of software
related to A Q-and-A platform software for teams at any scales
## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: none
## Membership Data:
Apache Answer was founded 2024-12-18 (2 years ago)
There are currently 18 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Anne Zhu on 2024-12-18.
- No new committers were added.
## Project Activity:
- Released v2.0.2 on July 21, adding AI reasoning content in conversation
records, optional email verification, configurable new-question email
intervals, and panic recovery middleware.
- v2.0.2 also fixed six privately reported security vulnerabilities
(e.g. OAuth account binding, revision audit authorization, stale admin
API key access); the corresponding CVEs have been published.
- Released v2.0.3 on October 9, migrating the frontend build from Create
React App to Vite, adding Helm support for existing persistent volumes,
and further tightening authorization checks across content and MCP
access paths.
- Discussion of the next set of AI features has started, including AI
translation of questions and answers (raised on dev@ around using
Answer at the foundation level) and agent access via personal access
tokens.
## Community Health:
- 11 external contributors had pull requests merged this quarter, 9 of
them first-time contributors (up from 4 last quarter); contributions
ranged from the Vite migration to Helm, translations and bug fixes.
- 24 issues were filed by 12 unique reporters, with a growing share of
feature proposals (AI translation, agent access, spam cleanup tooling)
alongside bug reports.
- dev@ traffic rose to 49 emails across 18 threads from 10 participants
(18 emails last quarter), driven by two release votes, CVE announcements
and a substantive design discussion on AI translation.
- Security report volume increased this quarter; the PMC is working
through them with the ASF Security team, and further advisories are
in preparation.
-----------------------------------------
Attachment G: Report from the Apache APISIX Project [Ming Wen]
## Description:
The mission of Apache APISIX is the creation and maintenance of software
related to a cloud-native microservices API gateway
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache APISIX was founded 2020-07-15 (6 years ago)
There are currently 65 committers and 31 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 Ashish Tiwari on 2024-10-16.
- No new committers. Last addition was Yilia Lin on 2025-06-03.
## Project Activity:
Recent releases:
3.19.0 was released on 2026-09-28.
3.18.0 was released on 2026-08-20.
3.17.0 was released on 2026-06-15.
We are addressing security vulnerabilities,
including reviewing some AI-generated reports
that turned out to be false positives.
APISIX have also accelerated releases to deliver security fixes sooner.
## Community Health:
AI has lowered the barrier to contributing code to APISIX,
which is a positive development,
but it also requires committers to review code more carefully.
APISIX continues to see active commits and merges on GitHub.
However, developers are focusing more on AI than middleware,
so the community is not as active as it used to be.
-----------------------------------------
Attachment H: Report from the Apache Aries Project [Dominik Przybysz]
## Description:
Apache Aries software is a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: none
## Membership Data:
Apache Aries was founded 2010-12-15 (16 years ago)
There are currently 56 committers and 38 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 Grzegorz Grzybek on 2018-07-03.
- No new committers. Last addition was Romain Manni-Bucau on 2020-01-29.
## Project Activity:
Released some artifacts:
- parent-3.1.0 was released on 2026-07-23.
- testsupport-unit-2.0.0 was released on 2026-07-23.
- util-2.0.0 was released on 2026-07-23.
- versioning-checker-0.4.0 was released on 2026-07-23.
- versioning-plugin-0.4.0 was released on 2026-07-23.
- parent-3.2.0 was released on 2026-09-20.
- spifly-1.3.8 was released on 2026-09-20.
Planning releases of the next modules (e.g. proxy artifacts).
## Community Health:
Community is not very active.
3 pull requests from external developers were merged.
A lot of old jira issues were closed, generating a lot of emails.
-----------------------------------------
Attachment I: Report from the Apache Arrow Project [Antoine Pitrou]
## Description:
The mission of Apache Arrow is the creation and maintenance of software related
to columnar in-memory processing and data interchange
## Project Status:
Current project status: Ongoing
Issues for the board:
* (from the PMC chair) I’ve just noticed some comments had been posted by
board members on the [previous
report](https://agenda.apache.org/meetings/2026-07-15#arrow). I don’t
remember getting an e-mail notification about these and I might just as
well have missed them. Should something be done to ensure that such
feedback is not missed by the Chair and other PMC members?
## Membership Data:
Apache Arrow was founded 2016-01-20 (11 years ago)
There are currently 120 committers and 62 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Jeffrey Vo was added to the PMC on 2026-08-03
- Kosta Tarasov was added as committer on 2026-09-04
- Tadeja Kadunc was added as committer on 2026-08-14
- Zehua Zou was added as committer on 2026-08-19
## Project Activity:
The project has an [active blog](https://arrow.apache.org/blog/) where
you can find more information on recent releases.
### Community Organization
The Arrow project is organized as different communities focused on the
different Arrow language implementations (e.g C++ and bindings like
Python, Rust, Go, etc). These communities collaborate on the overall Arrow
specification and interoperability issues. This structure seems to be
working well as the project grows and matures.
### AI-Generated Contributions
We have started tightening the rules on contributions . New contributors
cannot have more than 3 PRs open at the same time on the apache/arrow GH
repo, hosting Arrow specs and C++-based implementations (other Arrow
implementations may follow other rules). In that repository, the new PR
template explicitly asks whether the contribution was AI- or
human-generated, and reviewed before submission. We have also disabled
automated issue assignment (using the “take” keyword) on the issue
tracker, now requiring collaborator interaction for
assigning issues.
### Paid infrastructure
We ran out of donated cloud services provider credits we used to run our
continuous benchmarking infrastructure. We attempted to secure more
credits, but were redirected to ASF Infra who told us there are no credits
available and there is no timeline when they might become available. Also,
the Enterprise GitHub subscription we use for extra CI capacity expired.
We paid another year of subscription and shuffled managing users of the
subscription account. Both of these items were covered with adhoc
donations that we can’t rely on in the future.
## Community Health:
Based on mailing-list volume, project activity remains steady.
Quarter-to-quarter variations can probably be attributed to random
oscillation rather than any structural change. Of note, several projects
such as Arrow C++ and Arrow Rust have GitHub discussions enabled to help
with user questions (those are echoed on [email protected], so are
still accounted for in the mailing-list stats).
-----------------------------------------
Attachment J: Report from the Apache AsterixDB Project [Ian Maxon]
## Description:
The mission of AsterixDB is the creation and maintenance of software related to
open source Big Data Management System
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache AsterixDB was founded 2016-04-19 (10 years ago)
There are currently 48 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Shiva Jahangiri was added to the PMC on 2026-10-12
- Ahmed Eldawy was added to the PMC on 2026-08-26
- Calvin Dani was added as committer on 2026-09-28
- Ahmed Eldawy was added as committer on 2026-08-27
- Hongyu Shi was added as committer on 2026-09-23
## Project Activity:
There has been discussion about making the long-awaited next release before
the end of the year on the list. Many of the long-awaited things blocking it
have been worked on over the past year. There was also a discussion about
migrating our rather peculiar build and code review setup to GitHub entirely.
The sentiment seems positive, so I have been actively prototyping it and hope
to share a working example with the community soon. This migration also should
greatly ease the technical difficulty of making a release, which is one of the
roadblocks to it.
A number of AsterixDB Proposed Enhancements (APEs) were proposed or finished:
- APE 33 (CLUSTER BY) was accepted and the related patches were merged
- APE 35 (Dynamic memory) was proposed and is being discussed
- APE 31 (Vector Indexing) was merged into master, along with APE 32 (LSM
Sampling) which uses it as a basis
- APE 28 (Enhanced Async API) was merged into master
- APE 36 (AsterixDB MCP) Was proposed as a result of Vivek's GSoC work
## Community Health:
Some of the fruits of community building paid off this quarter. Two long-time
contributors (Hongyu and Calvin) became committers. It is great to have them
on board. The same work also paid off in Shiva being voted into the PMC, she
was added as a committer many years ago. Her leadership in guiding Hongyu and
Calvin in their contributions to the project was pivotal. Ahmed was also voted
into the PMC, his expertise in geospatial systems was invaluable when
designing in the CRS support that Suryaa added. I was very surprised to find
we had not added him as a committer previously; he has been deeply involved in
the project since shortly after graduation. I think this was an oversight from
many years ago, when the majority of the contributors were already in the PMC
from being in the initial incubating contributors. I would say that overall,
many of the efforts started over the past years to drive traffic to the list
(APE, and simply reminding people that the list is the only place project
decisions can take place) has paid off to a degree. Things are much better
than this time last year, but we still have work to do in my estimation.
-----------------------------------------
Attachment K: Report from the Apache Atlas Project [Madhanmohan Neethiraj]
-----------------------------------------
Attachment L: Report from the Apache Attic Project [Hervé Boutemy]
## Description:
The mission of Attic is the creation and maintenance of a home for dormant
projects.
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Attic was founded 2008-11-19 (18 years ago)
There are currently 19 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Niall Pemberton on 2025-04-04.
- No new committers. Last addition was Niall Pemberton on 2025-04-04.
## Project Activity:
No retirement happened since the last report.
There is a discussion in progress about MADLib: we're waiting on October's
board meeting results to finally move it to Attic or not.
We started a discussion about creating a logo for Attic: help welcome from
anybody interested in such an effort.
## Community Health:
3 active members continue to drive operations based on our documentation.
We'll challenge the documentation again for the next retirement.
-----------------------------------------
Attachment M: Report from the Apache Auron Project [Lei Wang]
Project description:
Apache Auron is an open‑source accelerator for big‑data query engines, powered
by native vectorized execution. Auron has completed integrations with compute
engines including Apache Spark™ and Apache Flink®, as well as open‑source
lakehouse formats Apache Paimon™, Apache Iceberg™ and Apache Hudi. Apache
Auron has passed all TPC‑DS/TPC‑H benchmark cases. Compared to Apache
Spark‑3.5, Apache Auron runs ~2× faster and saves ~50% cluster resources.
Project state: Ongoing, with high activity.
Auron graduated from the Apache Incubator and became a top-level project in
September 2026. Development has remained very active throughout the reporting
period: the master branch carried 179 commits over the six months ending late
September 2026 (roughly 90 commits in July–September alone), with a balanced
mix of new native operator/function coverage, correctness fixes, performance
work, and the housekeeping required by graduation (site rebranding, TLP
release infrastructure, repository and README updates).
Current activity (last quarter)
The past quarter was focused on three areas:
New natively executed functions and operators: date_add, date_sub, datediff,
add_months, unix_date/date_from_unix_date, dayofyear; extended
residual-condition handling in native sort-merge joins; shared CPU
join-condition evaluation; ORC reader batch-size support; identity partition
values in native Iceberg scans; and pruning of full-data-file Iceberg
changelog delete tasks.
Correctness and robustness: Fixes for NULL predicate handling in aggregate
filters, float-to-decimal precision loss, native broadcast nested-loop join
diff checks, partial merge aggregation with sliced batches, and spill error
handling.
Performance and post-graduation consolidation. Caching of maximum
accumulator indices, avoiding identity copies in GenerateExec, reduced native
broadcast task serialization, and lower serialization overhead via
NativePartition. The release script was migrated to the project's TLP dist
repositories, the internal codebase was fully renamed from "blaze" to "auron",
and the GitHub repository and README were updated for the new project
identity.
The [email protected] list has been active, with monthly volume
ranging from a handful to more than 60 messages during the period (61 in
August). Activity includes design discussion on AIP-4 (Flink BATCH mode
support for Calc/Agg/Join), which is being explored as a possible future
integration direction.
Releases
Apache Auron 8.0.0 — 2026-07-04 (most recent release, made just before the end
of incubation activities). No release has been cut since graduation; the first
post-graduation release is being prepared end-to-end against the new TLP
release process (see Plans).
Community
The dev list answers contributions and questions in a timely manner; GitHub
issues and pull requests are being actively and promptly reviewed. Beyond
automated dependency updates, commits in the past six months came from 20+
distinct contributors, including recent external (non-committer) contributors,
which is a healthy sign for the community. Contributions continue to be driven
by multiple organizations. The PMC established at graduation has 22 members:
the 18 committers elevated by the graduation resolution, plus the four former
incubator mentors who remain on the committee. The roster matches the ASF
committee record.
Committers and PMC
Most recent committer addition: prior to graduation; the committer roster
stood at 18 when the graduation vote was held, and no new committers have been
elected since graduation.
Most recent PMC member addition: September 2026 — per the graduation
resolution, all 18 existing Auron committers became PMC members, and the four
former incubator mentors remain on the PMC (22 members in total).
Diversity: the PMC and committer rosters span more than ten distinct
organizations, and no single employer dominates the project.
Plans
Cut the first post-graduation release (targeting the v8.x line) end-to-end
through the TLP release flow, including the dist/release repositories, KEYS,
and signed artifacts, and exercise the new monthly/quarterly release cadence.
Issues
There are no Board-level issues at this time.
Health report The project is healthy.
Development velocity is high and sustained, the community is growing with
new external contributors across multiple organizations, user questions
are answered on dev@, production deployments are reported at scale, and
governance transitioned cleanly to a 22-member TLP PMC at graduation.
The PMC is following the monthly reporting obligation for newly graduated
projects and is completing the remaining post-graduation housekeeping
(TLP release tooling, branding cleanup).
Branding, legal and infrastructure
Branding: the website (auron.apache.org) and the GitHub repository
consistently use the Apache Auron name and logo; Incubating references were
removed from both upon graduation. Any remaining website-checklist items will
be completed in coordination with the Brand Committee.
Legal: no legal issues to report.
Infrastructure: no infrastructure issues. The release process now targets the
project's TLP dist repositories.
-----------------------------------------
Attachment N: Report from the Apache Avro Project [Ryan Skraba]
-----------------------------------------
Attachment O: 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 (12 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 recently cut a new major relase 4.18.0 and some minor releases.
We have recently added some new client facing features, as small API changes.
Recent releases:
4.18.1 was released on 2026-09-11.
4.18.0 was released on 2026-06-10.
4.17.4 was released on 2026-07-28.
## Community Health:
Most of the constributions in the community come from existing committers, so
this is not great. We have received a few security reports, that are not
actually real problems affecting BookKeeper users. Usually BookKeeper is
indeed used a library and it is hidden inside other products, like Apache
Pulsar.
We could do better at involving new uses. As reported previously we use Slack,
most of the times it is to ask for reviews. Mailing lists are barely used.
-----------------------------------------
Attachment P: Report from the Apache bRPC Project [James Ge]
Description:
The mission of Apache bRPC is the creation and maintenance of software related
to an industrial-grade RPC framework for building reliable and
high-performance services
Project Status:
Current project status: ONGOING
Issues for the board: NONE
Membership Data: Apache bRPC was founded 2022-12-21 (4 years ago) There are
currently 22
committers and 14 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Guangming Chen on 2025-01-06.
- Chuang Zhang who works on Unified Bus for Huawei (the NVLink like in
Huawei's ecosystem) was added as committer on 2026-09-16
Project Activity:
bRPC v1.18.0 was released on 2026-09-25 with notably 35 CVEs
fixed, 16 of them are high-risk, 19 are mid-risk. Some highlights of the
changes:
- Add MySQL client protocol with clean-room auth, text protocol, transactions
and prepared statements by @rajvarun77 (#3330)
- Support TLSv1.3 by @neilxxxxx (#3319)
- Support RDMA handshake protocol V3 by @chenBright (#3350, #3326)
- Support end-to-end ECE negotiation in RDMA handshake V3 by @chenBright
(#3352)
- Add Power-of-Two-Choices Peak-EWMA (p2c) load balancer by @rajvarun77
(#3367)
- Add bounded-load consistent hashing (c_murmurhash_bl) load balancer by
@rajvarun77 (#3502)
- Support Protobuf v35 by @wasphin (#3429)
- Support flow-controlled gRPC client requests by @wasphin (#3430)
- Add TLS peer name verification for clients by @wwbmmm (#3408)
- Interconnect via UBShmTransport based on LD/ST shared-memory semantics by
@zchuango (#3290)
- Harden HTTP/2 receive path against unbounded resource growth by @wwbmmm
(#3474)
- Reject HTTP/1 header forms that desync framing by @chenBright (#3521)
- Add RISC-V Zvbc vector CRC32C acceleration by @Felix-Gong (#3332)
Community Health:
Committers take turns responding user emails and issues on a
weekly basis.
During the past quarter, about 110 new emails were received and answered
weekly.
-----------------------------------------
Attachment Q: Report from the Apache BuildStream Project [Abderrahim Kitouni]
## Description:
The mission of Apache BuildStream is the creation and maintenance of software
related to efficiently and correctly developing, building and integrating
software stacks
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache BuildStream was founded 2022-09-21 (4 years ago)
There are currently 6 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abderrahim Kitouni on 2022-09-21.
- No new committers were added.
## Project Activity:
* New release 2.8.0 with a host of bugfixes and a couple new features
* Received our first report through ASF Security
* Fixed in a release 2.8.1
* Received more reports through ASF Security, we're clearly getting more
visibility
* I (Abderrahim Kitouni) presented at All Systems Go! about integration between
mkosi (a tool to make OS images) and BuildStream.
* ASF PlusOne interview with a community member: https://youtu.be/qyDMXX7tfqA
* Invited a new Committer / PMC member: Javier Jardon. They still haven't
completed their ICLA.
## Community Health:
Community health is getting better, we have more new contributors in the past
few months.
Ubuntu 26.10 just released, and it includes the newly released BuildStream
2.8.1, the first time Ubuntu includes a 2.x (ASF) release
-----------------------------------------
Attachment R: Report from the Apache Calcite Project [Mihai Budiu]
## Description:
The mission of Calcite is the creation and maintenance of software
related to Dynamic data management framework
Apache Calcite is a highly customizable framework for parsing and
planning queries on data in a wide variety of formats. It allows
database-like access, and in particular a SQL interface and advanced
query optimization, for data not residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for
building local and remote JDBC and ODBC database drivers. Avatica has
an independent release schedule and its own repository.
## Project Status:
Current project status: ongoing (high activity)
Issues for the board: none
## Membership Data:
Apache Calcite was founded 2015-10-21 (11 years ago)
There are currently 82 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 2.5:1.
Community changes, past quarter:
* No new PMC members. Last addition was Zhen Chen on 2026-03-11.
* Weiqing Zhou was added as committer on 2026-08-22
* We have just extended a new committer invitation to Xiaojun Wu, and he has
accepted, but the process has not yet been finalized
## Project Activity
- Calcite 1.42.0 was released on 2026-05-31
- Avatica 1.28.0 was released on 2026-05-12
- Avatica 1.29.0 was released on 2026-09-20
A new Calcite release is planned relatively soon.
## Security Response
We have received some reports generated automatically by AI agents
and all the critical and important issues have received patches
or are currently are under review.
## Community Health
The community seems very actively engaged. We are seeing a substantial
increase first-time contributions, no doubt due to the barrier of entry to
contributions being lowered by AI tools. The suprising trend of closing more
tickets than opening has continued into this quarter. This is due to the
dilligence of people like Yu Xu (xuzifu666) who are closing old issues.
- 196 JIRA tickets opened and 204 closed in the past quarter.
- [email protected] has been flat in the past quarter (334 emails
compared to 336).
- [email protected] has also been flat (1424 compared to 1441)
Top committers for last 3 months:
https://github.com/apache/calcite/graphs/contributors?selectedMetric=commits
52 mihaibudiu
27 xuzifu666
22 rubenada
9 zabetak
7 zzwqqq
6 tkalkirill
6 snuyanzin
5 anxkhn
5 1fanwang
4 xiedeyantu
Most active reviewers in the last 3 months:
159 mihaibudiu
71 rubenada
54 xuzifu666
28 sbroeder
21 zzwqqq
20 vlsi
16 julianhyde
13 wasabii
11 xiedeyantu
10 snuyanzin
9 1fanwang
8 FrankChen021
7 ehds
6 zabetak
6 vldpyatkov
6 copilot-pull-request-reviewer
Our scarcest resource is currently reviewer time. The project could certainly
benefit from some agentic reviews to supplement the human reviews. It would
be very nice if the Apache Foundation could offer reviews as a service for
its projects.
-----------------------------------------
Attachment S: Report from the Apache CarbonData Project [Liang Chen]
## Description:
- The Apache CarbonData is data store solution for fast analytics on Big Data
platforms (including Apache Hadoop, Apache Spark, Apache Flink among others)
to help speed up queries an order of magnitude faster over petabytes of
data, with the aim of using a unified file format to satisfy all kinds of
data analysis cases.
## Issues:
- The community need to consider, just maintain the existing feature for
version stability or encourage new contributors to do more new features,
need to discuss in community.
## Activity:
- Released new version 2.3.2
- Fixed CVE issues : unauthenticated Java deserialization RCE on the
Distributed Index Server IPC endpoint
- Fixed dependency issues and CI issues.
- Bug fix some feature issues
## Health Report:
- Commit activity:
- 12 commits in the past quarter
- 5 code contributors in the past quarter
## Releases:
* 2.3.2 was released on 2026-03-27.
* 2.3.1 was released on 2023-11-25
## Project Composition:
There are currently 28 committers and 19 PMC members in this project.
- The Committer-to-PMC ratio is roughly 7:5
Community changes, past quarter:
- Bo Xu was added to the PMC on 2023-04-22
- Brijoo Bopanna was added to the PMC on 2022-09-24
- Indhumathi was added to the PMC on 2022-02-16
- Vikram Ahuja was added as committer on 2022-02-10
- Akash R Nilugal was added to the PMC on 2021-04-11
## Notable mailing list trends:Mailing list activity stays at a high level
- [email protected]:
- 152 subscribers (change 8):
## Github issues activity:
- 8 issues be handled
## Github PR activity:
- 9 PRs opened on GitHub, past quarter
- 7 PRs closed on GitHub, past quarter
-----------------------------------------
Attachment T: Report from the Apache Causeway Project [Jörg Rade]
## Description:
The mission of Causeway is the creation and maintenance of software related to
Framework for rapidly developing domain-driven apps in Java
## Project Status:
Current project status: This is a mature project and the framework is
generally stable. There are no issues requiring board attention at this time.
Issues for the board: None
## Membership Data:
Apache Causeway was founded 2012-10-17 (14 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Martin Hesse on 2023-07-05.
- No new committers. Last addition was Martin Hesse on 2023-07-04.
## Project Activity:
In Q2/26 we released Causeway 3.6.0 [1] which was mostly a security
release. Pending security fixes are scheduled for 4.0.0 - backporting
to 3.x is optional.
We are working on the 4.x branch, based on Spring Boot 4, which
makes use of Java features beyond version 17 and ends the support for JDO.
This is planned for release in Q4 of 2026. Andi and Dan are
working on support of OpenTelemetry.
We continue to promote the framework to extend our user base.
Dan presented at SoCraTes 2026 in Soltau in August [4].
There is also an article about Causeway up on devm.io [3].
## Community Health:
We continue to see engagement on our slack channel, which the community seems
to much prefer over the users mailing list. Nevertheless, we continue to
ensure that all relevant information are cross-posted to users@ and dev@ where
necessary.
## References (links)
[1] https://causeway.apache.org/relnotes/latest/about.html
[2] https://spring.io/events/spring-io-2026
[3] https://devm.io/ddd/apache-causeway-introduction
[4] https://www.socrates-conference.de/
-----------------------------------------
Attachment U: 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 on 2024-03-20.
There are currently 28 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 7:4.
Community changes, past quarter:
- No new PMC members. The last addition was Fei Wang on 2024-12-31.
- No new committers. The last addition was Xianming Lei on 2026-04-20.
## Project Activity:
Software development activity:
- Apache Celeborn 0.7.0 was released on 2026-08-16.
- The 0.7.0 release expanded engine support to Spark 4.1/4.2 and Flink
2.1/2.2/2.3, and improved the maturity of the Spark 4.0 and Flink 2.0
clients.
- The C++ native client (CIP-14) made substantial progress toward feature
parity with the Java client, including the push/merge data path,
compression, retry logic, native transport, and hybrid integration tests.
- Encryption at rest (CIP-22) progressed with the Spark-side implementation
included in 0.7.0.
- The release also improved remote storage support for S3, OSS, and HDFS;
observability; performance; shuffle integrity; durability; reliability; and
security.
- A standalone LifecycleManager and a Rust SDK were introduced, together with
further Helm chart improvements.
Meetups and Conferences:
- One talk was given in CoC Asia 2026.
Recent releases:
- Apache Celeborn 0.7.0, released on 2026-08-16.
## Community Health:
Overall community health remains healthy, with a Community Health Score (Chi)
of 6.33.
In the past quarter, traffic on [email protected] decreased by 6%, from
56 to 53 emails. Traffic on [email protected] increased by 21%, from
834 to 1,013 emails. The development mailing list therefore remained broadly
stable, while issue-related activity increased.
During the same period, 100 JIRA tickets were opened and 68 were closed. This
shows continued development activity, while the difference between opened and
closed tickets is something the community should continue to monitor.
There were no new committers or PMC members during the quarter. The community
will continue encouraging active contributors to deepen their participation
and will monitor contributor growth and issue resolution in the coming
quarter.
There are no immediate community health concerns requiring Board attention.
-----------------------------------------
Attachment V: Report from the Apache Celix Project [Pepijn Noltes]
-----------------------------------------
Attachment W: 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: Dormant
Issues for the board: None
## Membership Data:
Apache Curator was founded 2013-09-18 (13 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Kezhu Wang on 2023-03-25.
- No new committers. Last addition was Kezhu Wang on 2023-03-24.
## Project Activity:
There is almost no activity in the project. We have received some security
reports but they do not really represents bugs in Curator code base. It is
worth to note that we are not quick at responding to such security reports.
While we raised a discussion to merge Curator into ZooKeeper, we have never
followed up. Maybe it is time to revive that thread.
## Community Health:
But We have received a contribution for a bug fix recently by a new
contributor. So it's kind of a good sign.
-----------------------------------------
Attachment X: Report from the Apache CXF Project [Andriy Redko]
## Description:
Apache CXF is an open source services framework. CXF helps you build and
develop services using frontend programming APIs, like JAX-WS and JAX-RS.
These services can speak a variety of protocols such as SOAP, XML/HTTP,
RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS
or JBI.
There is also a sub-project that leverages CXF:
Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache CXF was founded 2008-04-15 (18 years ago)
There are currently 44 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
## Community changes, past quarter:
No new PMC members. Last addition was Andy McCright on 2019-02-24.
No new committers. Last addition was Jamie Mark Goodyear on 2024-07-19.
## Project Activity:
The project is still struggling with very large number of CVE reports, largely
addressed and landed in the recent release train. In addition, the team goes
over the security scanning reports that was performed Mythos/ASV.
On the releases side, due to many asks from the community, a large number of
CVE fixes were backported to older releases.
Recent releases:
3.6.13 was released on 2026-10-08.
4.1.9 was released on 2026-10-08.
4.2.4 was released on 2026-10-08.
### Community Health:
Resolving CVEs (and addressing Mythos/ASV findings) still takes considerable
amount of time and will be the main focus for a while. The rate of
improvements / fixes has slowed down however the team goes extra mile
responding to bug reports and reviewing and merging pull requests promptly.
-----------------------------------------
Attachment Y: Report from the Apache DataFu Project [Eyal Allweil]
-----------------------------------------
Attachment Z: Report from the Apache DB Project [Jeffery Painter]
## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software
licensed to the Foundation, for distribution at no charge to the public.
The Apache DB TLP consists of the following sub-projects:
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Project Status:
Current project status: ongoing
Issues for the board: none
Please see the Project Activity section of our report for recent updates.
## Membership Data:
Apache DB was founded 2002-07-16 (24 years ago).
There are currently 48 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
* No new PMC members. Last addition was Max Philipp Wriedt on 2024-07-03.
* No new committers. Last addition was Max Philipp Wriedt on 2023-04-15.
## Project Activity:
### Apache JDO
The JDO project continues to hold regular project meetings, with recent work
focused on review of security-related changes, compatibility considerations,
and preparation for future releases.
The community has continued work related to the Glasswing security-scan
effort and review of proposed fixes. Recent pull requests address JNDI,
service discovery, privileged-operation fallback, enhancer behavior, and
classpath handling. These proposals remain under community review.
Particular attention has been given to proposed changes involving user-defined
object identity classes and XML document builder configuration. The community
identified potential backward compatibility concerns and is revising the
proposals to distinguish necessary fixes from changes that could restrict
existing application behavior. Testing of an object identity patch also
identified a problem in the run-once tests, prompting further work.
Release planning includes consideration of JDO 3.2.2 and JDO 3.3, with
discussion of which fixes can be included in a maintenance release and
which changes may require a release that accommodates compatibility changes.
No completed release is recorded in the supplied quarterly activity.
The Trusted Release voting-list issue noted in the previous report was fixed
and closed during August. This resolves the reported routing problem for JDO
release votes and represents progress toward use of the Trusted Release
workflow.
Other continuing discussion and maintenance topics include:
* Raising the minimum supported Java version to JDK 11 (JDO-812), together
with consideration of release scope and Derby dependency updates.
* Generation of SBOM files (JDO-847).
* SonarCloud code quality findings (JDO-819 and JDO-823), including cognitive
complexity and raw type warnings.
* Dependency maintenance, including review of a Log4j API update for the TCK.
### Apache Torque
Torque activity remains relatively light, with substantive discussion during
the quarter about repository migration, integration testing, and the scope of
a future major release.
The community renewed discussion of migrating Torque from Subversion to Git.
A developer volunteered to carry out the migration, and the proposal received
support. Discussion covered repository layout, whether to separate the
integration-test module, and the implications for CI, pull requests, issue
tracking, and site deployment. The supplied discussions do not record a
completed migration.
Jenkins build failures were investigated and attributed to path-resolution
issues when running the Torque integration tests from the project root. A
proposal would simplify the build by running the database integration tests
separately, removing the Jenkins-specific profiles, and excluding the test
module from release deliverables. This would require documenting a separate
integration-test step before preparing a release. The proposal received
support, but implementation is not confirmed in the supplied activity.
Future release discussion includes a possible move to Torque 8.0 to reflect
breaking changes associated with Java Time API support (TORQUE-375) and the
retirement of Derby. The community also discussed declaring Derby unsupported
for the upcoming release and addressing CI issues alongside the repository
migration. Work on ORM generation improvements (TORQUE-376) was mentioned in
the migration discussion.
No completed Torque release is recorded in the supplied quarterly activity.
### Project-Level Updates
No project-level issues requiring board attention have been identified in the
supplied activity. The previously reported JDO Trusted Release voting-list
issue has been resolved.
## Community Health:
The Apache DB community remains engaged in maintaining its two subprojects.
JDO continues to show regular participation in project meetings and careful
review of proposed changes, with attention to release planning, security
review, and compatibility for existing users.
Torque has a lower volume of activity, but the repository migration proposal,
investigation of integration-test failures, and discussion of future release
scope show continued developer engagement.
No concerns requiring board attention have been identified in the supplied
materials.
-----------------------------------------
Attachment AA: Report from the Apache Directory Project [Shawn McKinney]
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely written in
Java, which has been certified LDAPv3 compatible by the Open Group.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
This is a "schema aware” API with some convenient ways to access all types
of LDAP servers.
- Studio: A complete directory tooling platform intended to be used with any
LDAP server however it is particularly designed for use with ApacheDS. It is
an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based authorization platform that provides role-based
access control, delegated administration and password policy services with
an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains various tools
to access and manage kerberos principals and keytabs. It provides a rich,
intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.
- Mavibot: An embeddable key-value database library with MVCC (Multi Version
Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Project Status:
Quite a busy quarter as there were code scans by the
Glasswing scanner that have generated reports that have led to many CVE's,
along with those incoming from independent researchers.
Issues for the board: No issues to report at this time.
## Membership Data:
Apache Directory was founded 2005-02-22 (22 years ago)
There are currently 57 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Brian Demers on 2023-10-23.
- No new committers. Last addition was Fredrik Roubert on 2023-07-10.
## Project Activity:
Just this week fixed a critical issue in MINA that was blocking usage of TLS
1.3. After the MINA release, another for the LDAP API and then finally Studio.
Per sub-project:
- ApacheDS: med activity. Also being actively maintained with internal fixes
and incoming pull requests.
- LDAP API: med activity. Another release this quarter with the maintainer
staying busy and fixing many bugs.
- Studio: med activity. Currently work is being done in preparation of a
well needed release.
- Fortress: low activity. Low activity. Internal discussions about moving
project into attic.
- Kerby: med activity. Also being actively maintained with security scans
and incoming pull requests.
- Mavibot: low activity.
- SCIMple: low activity. Needs a release. Activity from the community, PR's
are being managed.
## Community Health:
Again a busy quarter for the project's maintainers keeping up with the
incoming scans and the necessary code changes. This activity isn't viewable by
the outside community but has required attention from us.
-----------------------------------------
Attachment AB: Report from the Apache DolphinScheduler Project [Lidong Dai]
## Description:
Apache DolphinScheduler is a modern data orchestration platform that empowers
agile, low-code development of high-performance workflows.
## Project Status:
Current project status: Healthy
Issues for the board: There are no Board-level issues at this time.
## Membership Data:
Apache DolphinScheduler was founded on 2021-03-16 (6 years ago). There are
currently 59 committers and 27 PMC members. The Committer-to-PMC ratio is
roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Xin Cheng on 2024-06-17.
- No new committers. Last addition was Hengliang Tan on 2024-07-02.
## Project Activity:
- 3.4.3 was released on 2026-09-06.
## Community Health:
- [email protected] had a 26% increase in traffic in the past
quarter (19 emails compared to 15).
- We held one online meetup and there're 100+ users join the meetup.
The project has a Community Health Score of 4.70 (Healthy).
-----------------------------------------
Attachment AC: Report from the Apache Druid Project [Karan Kumar]
## Description:
Apache Druid is a high-performance real-time analytics database. It is
designed for workflows where low-latency query and ingest are the main
requirements. It implements ingestion, storage, and querying subsystems. Users
interface with Druid through built-in SQL and JSON APIs, as well as
third-party applications.
Druid has an extensive web of connections with other Apache projects: Calcite
for SQL planning, Curator and ZooKeeper for coordination, Kafka, HDFS and
Iceberg as data sources, Avro, ORC, or Parquet as supported data input
formats, and DataSketches for scalable approximate algorithms. Druid can also
be used as a data source by Superset.
## Project Status:
Ongoing - with High activity
### Issues
There are no issues requiring board attention at this time.
## Membership Data:
Apache Druid was founded 2019-12-18 (7 years ago) There are currently 77
committers and 42 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:5.
Community changes since our last report:
- No new PMC members. Last addition was Cece Mei on 2026-03-09.
- Andreas Maechler was added as committer on 2026-09-28.
The PMC chair election mentioned in our last report is complete: Karan Kumar
was appointed chair on 2026-08-19, succeeding Abhishek Agarwal. This follows
the PMC's decision to rotate the chair every year.
## Project Activity:
We had one major release since the last report:
- 38.0.0 (2026-10-01) - 250+ changes from 35 contributors
Highlights of 38.0.0:
- Java 25 is now supported and recommended. Java 21 is still supported, and
Java 17 support has been dropped.
- The legacy ZooKeeper-based task runner and segment announcement/discovery
were removed. The HTTP-based implementations, which have been the defaults
for several releases, are now the only options. ZooKeeper is still used for
leader election and service discovery.
- New community extension: an OpenLineage emitter.
Druid typically does major releases 3-4 times a year.
Development Activity (since our last report, 2026-07-13):
- 842 pull requests opened (417 excluding automated dependency updates)
- 874 pull requests closed, 708 of them merged
- 324 commits from 45 contributors, plus 360 automated dependency updates
GitHub activity is significantly higher than in our last reporting period (512
pull requests opened and 387 merged/closed over about four months). A large
share of the increase comes from automated dependency-update PRs. Excluding
those, the rate of human-authored PRs is also up: about 140 per month (417 in
three months), compared with about 110 per month in the last reporting period.
Work leading up to the 38.0.0 release and the next release, Druid 39.0.0, also
contributed. 39.0.0 has a code freeze in mid-October and targets a release in
mid-November.
## Community Health:
Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,437
members, up 19 members since our last report (3,418). In the previous
reporting period it grew by 53. Slack growth has saturated.
Slack is our most active channel for user support and usage-oriented
discussions. As before, development discussions happen more on GitHub, and
sometimes on the dev mailing list.
Since our last report, the dev mailing list saw two outreach threads from
outside contributors:
- The Apache TsFile community proposed a TsFile input format, which would be a
cross-project collaboration with another ASF project. They were invited to
start with a prototype as a community extension.
- A contributor from Adyen contributed an Open Policy Agent (OPA) authorizer,
originally developed by Stackable, as a community extension. It was merged
on 2026-09-01 and will ship in 39.0.0.
We still need to bring in more contributors and committers. As discussed in
our last report, we started monthly community office hours. The first session
was held on 2026-09-24, and we plan to keep holding them regularly.
-----------------------------------------
Attachment AD: Report from the Apache Dubbo Project [Jun Liu]
-----------------------------------------
Attachment AE: Report from the Apache EventMesh Project [Eason Chen]
## Description:
The mission of Apache EventMesh is the creation and maintenance of software
related to a fully serverless platform used to build distributed event-driven
applications
## Project Status:
Current project status: Ongoing Issues for the board: none
## Membership Data:
Apache EventMesh was founded 2023-03-22 (3 years ago) There are currently 54
committers and 16 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:2.
## Community changes, past quarter:
- No new PMC members. Last addition was Jianbo Liu on 2024-01-05.
- No new committers. Last addition was Zikang Chen on 2025-01-28.
## Project Activity:
Unified State & Delivery Reliability — Built a control-plane store SPI with
durable DLQ, atomic offsets, and the new PARTITION_OWNED_PULL topology. Single
Protocol Path — Made EventMeshFrame the one immutable message flowing across
HTTP, filter chain, and TCP. Architecture Modularization & Guardrails —
Repartitioned core modules, split SPIs, and enforced architecture rules in CI
FAIL mode. Production-HA Hardening Sprint — Closed a 10-issue push on fencing,
quota, and fail-closed security. A2A Gateway & Agent Framework —
Productionized the A2A gateway and added
AgentTool/LlmClient/ConversationMemory extension points. Connectors, Storage &
Deployment — Completed 16 connectors, added memory storage, K8s/Docker/CI
setup, and bumped to 2.0.0-SNAPSHOT. Documentation Overhaul — Restructured
docs/ by audience and synced it with the real implementation.
## Community Health:
The new features were under designing or developing, so the commits and PR
activity seems decrease. Contributors increased slightly compared to the
previous quarter. Overall community health is good.
-----------------------------------------
Attachment AF: Report from the Apache Fineract Project [James Dailey]
## Description:
The mission of Apache Fineract is the creation and maintenance of software
related to a core banking platform that provides a reliable, robust, and
affordable solution for entrepreneurs, financial institutions, and service
providers to offer financial services to the world's underbanked and unbanked.
## Project Status:
Current project status: ongoing with high activity
Issues for the board: not at this time
## Membership Data:
Apache Fineract was founded 2017-04-18 (9 years ago)
There are currently 57 committers and 25 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 Adam Monsen on 2025-11-05.
- No new committers. Last addition was Attila Budai on 2026-03-30.
## Project Activity:
Our last release was 1.15.0 on 2026.07.14
We have one committer about to be voted upon.
## Community Health:
Over the past 21 months, 134 unique individuals contributed over 1300 Pull
Requests to the core Fineract project. (stats from Adam Saghy)
In August, we completed a successful first season of GSOC at Fineract with
students continuing to be involved and new people asking about next year.
We created four new code sub-projects within the Fineract project that add to
the full architecture of the solution. These sub-projects are not yet at a
release level.
We had a day of sessions at the ASF Community Over Code in Glasgow with a
total of four members of the community participating, down from our peak of 15
at the Halifax conference.
Robert observed astutely that Boards of Banks decide to use Fineract unlike
any other project at the ASF - where developers make the decisions.
-----------------------------------------
Attachment AG: Report from the Apache Flagon Project [Joshua Poore]
-----------------------------------------
Attachment AH: 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 (14 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 has been very little activity, but there was a release not too long ago
and we've recently discussed moving to the attic and the consensus was not
yet.
## Community Health:
Low activity, but there's still enough of a PMC. I missed reporting a number
of times due to personal issues. I tried reporting last month, but I missed
the deadline. Sorry about that.
-----------------------------------------
Attachment AI: Report from the Apache Fluss Project [Jark Wu]
## Description:
Apache Fluss is a streaming storage system built for real-time analytics and
AI, serving as the real-time data layer for Lakehouse architectures.
## Project Status:
Current project status: New, with high activity.
The community released Apache Fluss 1.0.0 in September, its first release as
an Apache top-level project. The focus is now shifting from the 1.0 milestone
to a more regular release cadence, broader participation in release
management, and the 1.1 roadmap.
Issues for the board: Assistance with Confluence account creation.
Nearly every recent Confluence account approval for a new contributor has
failed, requiring an Infra ticket or manual assistance through Infra Slack
[5]. This delays participation and creates a poor onboarding experience. We
would appreciate an estimated timeframe for fixing the approval process, or
guidance on recommended alternatives for collaborative design proposals and
documentation.
## Membership Data:
Apache Fluss was established as a top-level project on 2026-07-15.
There are currently 23 committers and 15 PMC members in the project. The
Committer-to-PMC ratio is roughly 3:2.
Community changes during the past quarter:
- Hongshun Wang was added to the PMC on 2026-09-30.
- Junbo Wang was invited as a committer on 2026-09-29.
- Yang Wang was added as a committer on 2026-08-06.
## Project Activity:
Apache Fluss 1.0.0 was released on 2026-09-21 [1]. The release includes the
Fluss Gateway, expanded Rust, Python and C++ client capabilities, Apache Hudi
integration, improvements to Flink and Spark integration, and operational
features such as Coordinator high availability.
The September community call reviewed the release and discussed a shorter,
two-to-three-month release cadence. Planning for 1.1 is under way [2]. Current
priorities include deletion vector support, Kafka producer protocol
compatibility and native DataFusion query support for the Rust-based Gateway.
The community is preparing a Fluss hackathon at Community Over Code in Glasgow
on October 13 [3], with scoped tasks to help new contributors get started and
work alongside existing contributors.
## Community Health:
The Fluss community remains healthy and active. Apache Reporter provides the
following quarterly comparisons as of 2026-10-05 [4]:
- dev@: 401 emails compared with 316 in the previous quarter (26% increase, as
reported by Reporter).
- issues@: 4,084 emails compared with 3,566 (14% increase, as reported by
Reporter).
The increased dev@ discussion and GitHub issue and pull-request activity
mirrored on issues@ reflect the community's renewed focus on development after
graduation. Together with the successful 1.0 release and ongoing 1.1 planning,
this is a positive sign of healthy community development. Reporter also gives
Fluss a Community Health Score (Chi) of 10.00 (Super Healthy) [6].
Review capacity and sharing release responsibilities are areas the community
is actively addressing. Contributors have proposed pairing FIP authors with
volunteer reviewers and tracking that ownership in the roadmap. Nicholas Jiang
volunteered to manage the 1.1 release, and Lorenzo Affetti offered to assist
and learn the release process. These discussions aim to reduce review
bottlenecks and grow the pool of people able to support future releases.
The PMC reviewed concerns about community involvement and the branding of
Fluss Forward, a third-party event organised by Ververica, and sought ASF
Brand Management guidance [7][8]. Following these discussions, the organiser
clarified the event's independent positioning, the event was removed from the
ASF events calendar, and the PMC published a clarification on dev@ and user@
[9]. In the end, the organiser decided to postpone Fluss Forward London to
allow PMC and wider community participation from the start of planning, a new
date had not been finalised yet.
## References:
[1] https://fluss.apache.org/blog/releases/1.0/
[2] https://github.com/apache/fluss/discussions/3819
[3] https://events.apache.org/events/2026/community-over-code/fluss.html
[4] https://reporter.apache.org/wizard/statistics?fluss
[5] https://issues.apache.org/jira/browse/INFRA-28254
[6] https://reporter.apache.org/chi.py#fluss
[7] https://lists.apache.org/thread/k35y8p31vq73vk1r6ggtf2lk6qnp9qpw
[8] https://lists.apache.org/thread/hlqmrfsvf5jvc6qjjo2czpm5rjt9lzjm
[9] https://lists.apache.org/thread/0jmt7gj6y91f2sc3olyp788yd3t5x13p
-----------------------------------------
Attachment AJ: Report from the Apache Fory Project [Chaokun Yang]
# Apache Fory Board Report — September 2026
Reporting period: June 26–September 30, 2026.
Apache Fory is a high-performance, multi-language serialization framework
that enables efficient data exchange across systems and programming languages.
Through JIT compilation, code generation, and zero-copy techniques, Fory
delivers low-latency, high-throughput serialization for modern distributed
applications.
## Project Status: Ongoing with high activity.
Board-Level Issues: The project would appreciate assistance in moving forward
the pending Infrastructure request for CI-based release automation, as
described
under Infrastructure and Strategic Needs below. No other issues require Board
action at this time.
Since the last report, Apache Fory has made significant progress in
serialization capabilities, cross-language support, documentation, and
community participation. A major milestone was the introduction of Fory JSON
for Java, followed by dedicated Kotlin and Scala support, extending Fory
to standard JSON use cases alongside its binary serialization capabilities.
[Java JSON release](https://fory.apache.org/blog/fory_1_4_0_release/),
[Kotlin&Scala JSON release](https://fory.apache.org/blog/fory_1_7_0_release/).
The community remains active, with continued contributions from established
members and first-time contributors across language implementations,
compiler support, testing, and documentation.
## Recent Releases:
The project has maintained a strong release cadence, delivering eleven
formal releases since the previous report:
- v1.7.6 — September 30, 2026
- v1.7.5 — September 25, 2026
- v1.7.4 — September 20, 2026
- v1.7.3 — September 16, 2026
- v1.7.2 — September 11, 2026
- v1.7.1 — September 4, 2026
- v1.7.0 — August 28, 2026
- v1.6.1 — August 16, 2026
- v1.6.0 — August 7, 2026
- v1.5.0 — July 31, 2026
- v1.4.0 — July 20, 2026
These releases include new JSON capabilities, performance improvements,
security hardening, broader language and platform support, and bug fixes.
Release details are available in the
[project announcements](https://fory.apache.org/blog/)
and
[latest release notes](https://github.com/apache/fory/releases/tag/v1.7.6).
## Project Activity:
Development activity remains robust across several areas:
- Introduced and expanded Fory JSON for Java, Kotlin, and Scala, including
configurable object mapping, incremental decoding of JSON arrays and
newline-delimited JSON, and Android and GraalVM Native Image support.
- Extended gRPC code generation to C++ and Swift, building on the language
integrations reported last quarter.
- Added external-type serialization for Rust, Dart, Swift, and C#, enabling
applications to serialize third-party types without modifying their source.
- Aligned and enhanced Rust Row Format support and added Standard Row Format
support for Go.
- Continued improving serialization performance, deserialization resource
limits, input validation, and cross-language correctness.
- Reorganized documentation around project capabilities and expanded
getting-started guides, benchmarks, and integration examples.
These developments are documented in the
[1.5.0](https://github.com/apache/fory/releases/tag/v1.5.0),
[1.6.0](https://github.com/apache/fory/releases/tag/v1.6.0),
[1.7.0](https://fory.apache.org/blog/fory_1_7_0_release/), and
[1.7.3](https://github.com/apache/fory/releases/tag/v1.7.3) release notes.
## Current Plans:
The project's priorities for the coming months include:
- Further improving performance, reliability, and cross-language consistency.
- Continuing to develop Fory JSON, compiler support, and integration examples.
- Improving user and contributor documentation to lower entry barriers.
- Attracting and mentoring new contributors and encouraging broader
participation in development, reviews, and releases.
- Exploring collaboration with other Apache projects to demonstrate
interoperability and practical integration.
## New Committers and PMC Members:
Committer: Peiyang He was added on July 8, 2026.
https://community.apache.org/blog/2026_07_committers.html .
No new PMC members were added during this reporting period.
[Current PMC roster](https://whimsy.apache.org/public/committee-info.json).
## Branding and Legal Considerations:
There are no known branding or legal issues at this time. The project
continues to use its name and marks in accordance with Apache policies.
Official project materials maintain appropriate branding and attribution.
## Infrastructure and Strategic Needs:
The project would like to automate source release packaging, artifact signing,
and Maven publishing through CI to reduce manual release work. This requires
support from the Apache Infrastructure team. We have requested assistance in
[INFRA-28319](https://issues.apache.org/jira/browse/INFRA-28319) a month ago,
but the request has not yet been addressed.
Assistance in moving this request forward would
help us improve the efficiency and reliability of our release process.
-----------------------------------------
Attachment AK: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AL: Report from the Apache Gluten Project [Weiting Chen]
## Description:
YouThe mission of Apache Gluten is the creation and maintenance of software
related to software related to a pluggable middleware that enables native,
vectorized execution engines to accelerate Apache SparkSQL workloads;
## Project Status:
Current project status: Ongoing, with active development and release
management as an Apache top-level project. Work continues on Spark
compatibility, native execution performance and correctness, and integration
with lakehouse table formats.
Issues for the board: No issue requiring Board intervention was identified in
the public material reviewed.
## Membership Data:
Apache Gluten was founded 2026-02-18 (8 months ago) There are currently 45
committers and 28 PMC members in this project. [1] The Committer-to-PMC ratio
is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Chang Chen on 2026-02-18.
- No new committers. Last addition was Ankita Victor on 2026-04-16. [2]
## Project Activity:
- Release: Apache Gluten 1.7.0 was released in August, with the GitHub release
published on 2026-08-26. It remains the latest official release. Changes
include Spark 4.0/4.1 compatibility work, Delta 4 native writes for Spark
4.0, native function and data-type coverage improvements, broadcast-join
optimization, and correctness fixes. [3]
- Development: During the reporting period, 627 pull requests were opened and
372 merged, including automated maintenance changes. 139 issues were opened
and 96 closed. These are separate activity counts, not counts for a single
cohort of issues or PRs. [4]
- Compatibility and integration: Development continued on Spark 4.0/4.1, with
initial Spark 4.2 build profiles, shims, and a unit-test module merged.
Lakehouse work included Iceberg data-file rewrite support and native Delta
write-limit enforcement. These development-branch changes should not be
interpreted as released Spark 4.2 support. [5]
- Performance and reliability: Merged work included eager aggregation
improvements, Parquet map-key pruning, memory-lifetime fixes, and expanded
regression-test coverage. [6]
- Release oversight: Community review identified licensing and
source-packaging issues in earlier 1.7.0 release candidates. Subsequent
candidates incorporated corrections; the RC2 review documented successful
checks of signatures, checksums, licensing, notices, and source headers
before release. [7]
## Community Health:
The project continues to show active participation in development, issue
reporting, and public release review. The 372 merged pull requests came from
60 distinct author accounts, including 58 accounts after excluding the
identified automation accounts. Dependabot and GlutenPerfBot accounted for 76
merged pull requests. [4]
The 1.7.0 release notes recognize 12 first-time contributors. This is a
release-wide figure spanning the 1.7.0 development cycle, not a count of
newcomers specifically during this reporting quarter. [3]
Public release-vote discussions demonstrate substantive community oversight:
reviewers raised concerns about early candidates and reviewed the corrected
candidate before publication. Formal PMC and committer membership remained
unchanged during the quarter. [1][7]
At collection time, 910 issues and 141 pull requests remained open. Continued
issue triage, timely reviews, and recognition of sustained contributors are
appropriate areas of attention. These backlog figures alone do not establish a
community-health problem. [4]
[1] ASF public PMC roster and project membership data, updated October 14,
2026.
[2] Published Gluten Board-report history, including the establishment
resolution and May report recording Ankita Victor’s addition.
[3] Gluten 1.7.0 release notes, ASF downloads, and release announcement.
[4] GitHub API searches scoped to repo:apache/gluten , using
2026-07-15..2026-10-14 with created: , merged: , or closed: and
separate is:pr / is:issue filters. Merged PR evidence; new issues.
Contributor counts were calculated from all 372 returned merged PRs; live
counts may change.
[5] Representative merged work: Spark 4.2 shims/profile, Spark 4.2 test
module, Iceberg rewrites, and Delta write limits.
[6] Eager aggregation, Parquet map-key pruning, and memory-lifetime fix.
[7] Public RC0 review and RC2 approval with validation details.
-----------------------------------------
Attachment AM: 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 with high activity
Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-21 (a year ago) There are currently 30
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Minghuang Li on 2026-03-27.
- No new committers. Last addition was Bharath Krishna on 2026-03-28.
## Project Activity:
Software Development Progress in this period:
1. Apache Gravitino 1.3.0 was released on June 29, 2026 (it was in the RC vote
phase at the time of the last report).
2. Apache Gravitino 1.3.1 was released on September 30, 2026.
3. The main branch is now working towards Apache Gravitino 2.0.0. Major work
in this period includes:
- Iceberg V3 support (variant, geometry/geography, nanosecond timestamps)
and new Iceberg REST endpoints.
- Semantic Model management as a new metadata object type.
- Secret management, KMS, and client/server HTTPS and mTLS support.
- Access control enhancements: active roles, policy-on-tag, tag assignment
values, bulk access-control APIs, and Lance REST authorization.
- Spark 4.0 and Flink 2.1 connector support, and Starburst SPI
compatibility for the Trino connector.
- Built-in Iceberg table maintenance jobs and job system improvements.
4. Four CVEs (CVE-2025-53648, CVE-2026-41041, CVE-2026-41042, CVE-2026-49876)
were fixed and publicly disclosed in this period.
Community Activity:
1. Attended COC Asia and presented Gravitino with different sessions.
2. Community meetings.
## Community Health:
1. [email protected] had a 12% decrease in traffic in the past quarter
(118 emails compared to 134). The previous quarter included the six RC vote
threads of the 1.3.0 release.
2. 718 issues were created in the past quarter, a 68% increase (718 compared
to 428).
3. 1082 PRs were created in the past quarter, a 37% increase (1082 compared to
787). 767 PRs were merged (compared to 584).
4. 551 commits landed on the main branch from 52 authors in the past quarter
(compared to 394 commits from 52 authors), including 23 first-time
contributors.
-----------------------------------------
Attachment AN: 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 (9 years ago)
There are currently 17 committers and 11 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 Corentin Soriano on 2026-05-20.
- No new committers. Last addition was Stephen Schiffli on 2026-04-06.
## Project Activity:
The project has been working to finalize 1.6.1 and get RC1 ready. The main
issue blocking this for months has been GUACAMOLE-2118, which has finally been
resolved with the addition of a broad watchdog thread. Finishing up
GUACAMOLE-2118 lead to identifying segfaults that are likely causes of the
GUACAMOLE-2118 behavior, and should be fixed as part of 1.6.1.
See: https://issues.apache.org/jira/browse/GUACAMOLE-2118
## Community Health:
There has been a decrease in mailing list traffic, though it's unclear whether
this is due to anything specific vs. the typical end-of-year lull. The
community is otherwise active any healthy. If this is due to release cadence,
activity would be expected to pick up once we finally have 1.6.1 out.
-----------------------------------------
Attachment AO: Report from the Apache Hadoop Project [Xiaoqiao He]
## Description:
The mission of Hadoop is the creation and maintenance of software related to
Distributed computing platform.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hadoop was founded 2008-01-16 (19 years ago)
There are currently 251 committers and 126 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 Ahmar Suhail on 2025-11-13.
- No new committers. Last addition was Cheng Pan on 2026-04-12.
## Project Activity:
3.5.0 was released on 2026-04-01.
3.4.3 was released on 2026-02-24.
hadoop-thirdparty-1.5.0 was released on 2025-10-20.
3.4.2 was released on 2025-08-28.
hadoop-thirdparty-1.4.0 was released on 2025-03-27.
## Community Health:
The trunk branch received 79 commits from over 40 committers and
contributors, spanning Common, HDFS, YARN, MapReduce, and cloud storage
connectors modules.
- Security and Dependency Maintenance
The community continued process security and dependency maintenance, with
timely upgrades of third-party dependencies in response to CVEs and security
advisories. The Hadoop security model was documented in a new SECURITY.md file
and several security hardening improvements landed across RPC, shuffle, and
authorization paths [1][2]. The community are lagging in responding to all
the reported CVEs.
Given the dependency updates, and the number of critical bugs reported,
including from mythos, it may be best if we do a 3.5.1 release with the
critical fixes in, and then do a followup release with the next batch of
fixes, and get into a cadence of monthly/bimonthly releases. This is only
possible by automating as much of the release process, including as much
of the testing.
- JDK 22+ Compatibility and Adaptation in Progress
Subject propagation on JDK 22+ was restored via an InheritableThreadLocal
cascade in SubjectUtil, ensuring correctness in security scenarios such as
Kerberos [3].
- CI / Build / Test Stability
The project kept investing in its GitHub Actions build and test infrastructure
including GHA upgrades to ASF-allowed versions, improved CI coverage for fork
PRs, and replacing Clover with JaCoCo for code coverage. A series of fixes for
leaked mini-cluster instances and other flaky tests further improved CI
stability [4]. Also try to get set up for apache trusted release[5] which
would allow for semi-automated release and a higher cadence.
- HDFS Stability and Observability
HDFS work focused on correctness and operational safety, including fixes for
snapshot count drift during edit log replay, DataNode OOM under NameNode
unreachability, resource cleanup in block readers and short-circuit reads, and
a libhdfs heap-use-after-free. Observability improved with new router and
DataNode metrics, and a standalone DataNode read/write stress tester was added
[6][7].
- YARN Robustness and Hadoop-native MCP Server
YARN activity focused on robustness, including memory enforcement and queue
placement fixes. Notably, a Hadoop-native MCP (Model Context Protocol) HTTP
server framework was added in hadoop-common, opening Hadoop operations to
AI-agent integration [8].
- Cloud Storage Connectors
The cloud connectors remained active: ABFS gained Photon (Apache Arrow)
ListBlobs support, S3A received KMS Encryption Context support and AWS SDK
maintenance improvements, and the Baidu BOS file system implementation was
incorporated into the project [9].
- The Project shows healthy engagement based on Mailing list/JIRA/Github
traffic.
[1] https://issues.apache.org/jira/browse/HADOOP-19968
[2] https://issues.apache.org/jira/browse/HADOOP-19925
[3] https://issues.apache.org/jira/browse/HADOOP-19906
[4] https://issues.apache.org/jira/browse/HADOOP-19963
[5] https://github.com/apache/hadoop/pull/8811
[6] https://issues.apache.org/jira/browse/HDFS-17960
[7] https://issues.apache.org/jira/browse/HDFS-17953
[8] https://issues.apache.org/jira/browse/YARN-11977
[9] https://issues.apache.org/jira/browse/HDFS-11161
-----------------------------------------
Attachment AP: Report from the Apache HBase Project [Duo Zhang]
## Description:
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of rows
with millions of columns atop non-specialized hardware.
hbase-thirdparty is a set of internal artifacts used by the project to
mitigate the impact of our dependency choices on the wider ecosystem.
hbase-connectors is a collection of integration points with other projects.
The initial release includes artifacts for use with Apache Kafka and Apache
Spark.
hbase-filesystem contains HBase project-specific implementations of the Apache
Hadoop FileSystem API. It is currently experimental and internal to the
project.
hbase-operator-tools is a collection of tools for HBase operators. Now it is
mainly for hosting HBCK2.
hbase-native-client is a client library in C/C++, in its early days.
hbase-kustomize is for deploying HBase on kubernetes, still under development.
## Project Status:
Current project status: Ongoing
Issues for the board:
## Membership Data:
Apache HBase was founded 2010-04-21 (16 years ago)
There are currently 114 committers and 65 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- Charles Connell was added to the PMC on 2026-09-21
- Junegunn Choi was added to the PMC on 2026-09-21
- Xiao Liu was added to the PMC on 2026-09-21
- Dávid Paksy was added to the PMC on 2026-09-21
- No new committers. Last addition was Xiao Liu on 2026-03-12.
## Project Activity:
2.5.16 was released on 2026-10-01.
2.6.7 was released on 2026-10-01.
3.0.0 was released on 2026-08-05.
3.0.0-beta-2 was released on 2026-07-15.
We have released 3.0.0-beta-2 and the final 3.0.0 GA.
https://lists.apache.org/thread.html/jjbcwflpoxmrz5flq48kkg7m7ny5dj9f
https://lists.apache.org/thread.html/bj76g246wl67014vc1l7bqmryvq4nbvl
https://lists.apache.org/thread.html/tz5x5x67od8g3cs1gmsnr2gf8md3b7bd
## Community Health:
- [email protected]:
959 subscribers(964 in the previous quarter)
- [email protected]:
1972 subscribers(1974 in the previous quarter)
- [email protected]
83 subscribers(83 in the previous quarter)
- JIRA activity:
187 issues opened in JIRA, past quarter
156 issues closed in JIRA, past quarter
We have finally released 3.0.0, the next major release line for HBase. In this
version we have dropped some legacy dependencies and supports like JDK8 and
Hadoop 2, we believe this could make the project move more rapidly in the
future.
-----------------------------------------
Attachment AQ: Report from the Apache HertzBeat Project [Chao Gong]
## Description:
The mission of Apache HertzBeat is the creation and maintenance of software
related to a real-time monitoring system with agentless, performance cluster,
prometheus-compatible, custom monitoring and status page building capabilities
## Project Status:
Current project status: Ongoing
Issues for the board:
## Membership Data:
Apache HertzBeat was founded 2025-08-20 (a year ago) There are currently 31
committers and 21 PMC members in this project. The Committer-to-PMC ratio is
roughly 4:3.
Community changes, past quarter:
- SiGuo Duan was added to the PMC on 2026-09-20
- yu luo was added to the PMC on 2026-09-20
- Junwei Yao was added as committer on 2026-09-24
## Project Activity:
The new version HertzBeat v1.9.0 has been released. We are developing in the
next version 2.0.0.
## Community Health:
In the past month, 9 authors have pushed 28 commits to master and 31 commits
to all branches. We are actively attracting more production users and
contributors by improving doc, enhancing stability and strengthening features.
-----------------------------------------
Attachment AR: Report from the Apache Hive Project [Naveen Gangam]
## Description:
The mission of Hive is the creation and maintenance of software related to Data
warehouse infrastructure using the Apache Hadoop Database
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hive was founded 2010-09-21 (16 years ago)
There are currently 114 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Sai Hemanth Gantasala was added to the PMC on 2026-09-06
- No new committers. Last addition was Wechar Yu on 2026-03-30.
## Project Activity:
Apache Hive 4.2.1 released on Aug 24th 2026
CVEs from project glasswing being actively addressed
## Community Health:
Health score: 7.96
217% increase in dev community traffice
8% increase in gitbox traffic
34% increases in jira traffic
268 JIRA tickets opened and 162 closed in the past quarter
-----------------------------------------
Attachment AS: Report from the Apache Iggy Project [Kranti Parisa]
-----------------------------------------
Attachment AT: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for October 2026
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 24 podlings under incubation. In September, the
Incubator made two releases. IPMC membership saw one addition and no
removals and two IP clearances were completed.
NullAway entered incubation at the very end of September. Auron and
ResilientDB graduated at the September board meeting.
The Aegis MCP Governance Gateway proposal is on the wiki and in discussion
with possible mentors, including its relationship to Apache Knox.
Mailing list discussion otherwise focused on release voting, the IPMC
release vote process, and new podling proposals.
Eight release candidates were cancelled during the month, compared with
none in August and two in July. Most were withdrawn after IPMC reviewers
found LICENSE and NOTICE problems, third-party code under ASF headers, or
bundled files that should not be in a source release. One podling also had
unreleased versions published to Docker Hub before the vote, which it has
agreed to remove. The increase seems to be partly due to use of AI on both
sides. Podlings use AI to help prepare releases, which introduces some
mistakes. Reviewers use AI to check them, which can catch issues a human
reviewer might miss.
The IPMC voted to explicitly permit podlings to run the PPMC and IPMC
release votes concurrently. The vote passed with 14 binding +1 votes, one
binding 0 and one binding -1, and the policy and guides have been updated.
A separate proposal for a faster path, where three IPMC votes on the
podling dev list would conclude a release, did not gain support.
A follow-on discussion explored better ways to verify licensing in release
candidates, including using AI agents to help reviewers check source
provenance. A hybrid release candidate checker, with a deterministic script
and an AI review step, was added to the Incubator repo and discussed on the
general list. It was tested blind against 50 past release candidates with a
good success rate. The IPMC and ComDev also agreed to host the governance
configuration values that the Magpie onboarding skill uses, with no skills
moving between projects for now.
After its 0.7.0 release candidate was cancelled, Asyncband published 0.7.0
to crates.io outside the ASF release process. It yanked that version and
published 0.7.1 as an interim non-ASF release.
Maka is eager to release for a new podling. It brought its first release
candidate to the IPMC about a month after entering incubation, and replaced
it with a second after review. The RC2 vote is underway, but potentially
has an issue. About a third of the surviving code was written before the
repository had a licence, and ICLAs have not been confirmed for one of its
larger contributors from that period. This is also a minor issue with its
nightly desktop builds on GitHub.
Toree's mentor responded to last month's status discussion. The podling
says a new release candidate for 0.6.0-incubating is close, to be followed
by a release supporting a more recent Spark version.
Neither the Pegasus PPMC nor its mentors have responded to last month's
retirement discussion. The podling has been asked to address its future in
its October report. The report was not submitted.
PouchDB has agreed to announce its triage meetings and post summaries to
the dev list, but none has been posted yet. It still has no ASF release
after 17 months.
OzHera's dev list had no traffic in September. Its September report said a
security fix would ship in a release planned for mid-October.
## Community
### New IPMC members:
- Chia-Ping Tsai
### People who left the IPMC:
- none
## New Podlings
- NullAway
## Podlings that failed to report, expected next month
- Amoro
- Pegasus
## Graduations
- Auron
- ResilientDB
The board has motions for the following:
- none
## Releases
The following releases entered distribution during the month of
September:
- Asyncband 0.7.2
- Asyncband 0.7.3
## IP Clearance
- Cloudberry Command Center
- Grails IntelliJ Plugin
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[Amoro](#amoro)
[Asyncband](#asyncband)
[Caldera](#caldera)
[Maka](#maka)
--------------------
## Asyncband
Asyncband is a runtime-agnostic library providing essential synchronization
primitives for asynchronous Rust programming.
Asyncband has been incubating since 2026-08-18.
### Three most important unfinished issues to address before graduating:
1. Grow a diverse, sustained contributor base and recognize contributors as
committers and PPMC members.
2. Establish a regular ASF release process shared by multiple release
managers, with consistent licensing and artifact verification.
3. Broaden participation in reviews and public decision-making so that
project maintenance does not depend on a small number of individuals.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
The initial 0.7.0 release vote was cancelled after IPMC review identified
third-party licensing and attribution issues. The community corrected the
source notices and LICENSE file, strengthened release checks, and
subsequently completed the approved 0.7.2 release. The non-ASF 0.7.0 crate
was yanked, and release candidate tags no longer trigger publication to
crates.io.
### How has the community developed since the last report?
Since entering incubation, 18 contributors have had pull requests merged
into the main repository, covering new primitives, performance,
correctness, tests, and documentation.
Bohao Zhang (iqwqi) joined as a committer and PPMC member. Release
responsibilities are also expanding: Haixu Ouyang (orthur) is managing
0.7.3, following Zili Chen (tison) as release manager for 0.7.2.
GitHub Discussions are mirrored to the public development mailing list,
with links back to the archived threads.
### How has the project developed since the last report?
The repository, website, and mailing lists are operating on ASF
infrastructure. The project completed its first ASF-approved release,
Apache Asyncband (Incubating) 0.7.2, on 2026-09-11.
Development since that release has added competing MPMC and SPMC queues,
bounded lossless broadcast channels, an auto-reset event, and dynamic phase
coordination. Contributors also improved channel performance, cancellation
handling, and API documentation.
The project is using Apache Trusted Releases (ATR), with automated source
archive composition, signing, and staging. Version 0.7.3 has been released
as well by a new release manager Haixu
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-09-29 (Apache Asyncband (Incubating) 0.7.3)
### When were the last committers or PPMC members elected?
Bohao Zhang (iqwqi) joined as a committer and PPMC member in September 2026.
### Have your mentors been helpful and responsive?
Yes. Mentors have participated in release reviews and voting and provided
guidance on ASF processes. There are no outstanding issues requiring
additional mentor attention.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The project uses Apache Asyncband (Incubating) branding on its website
and repository. No third-party misuse is known.
VP, Brand approved the Apache Asyncband name on 2026-08-16 through
PODLINGNAMESEARCH-257.
### Signed-off-by:
- [ ] (asyncband) Hao Ding
Comments:
- [X] (asyncband) Zili Chen
Comments:
- [X] (asyncband) Jean-Baptiste Onofré
Comments:
- [X] (asyncband) Mingyang Liu
Comments:
### IPMC/Shepherd notes:
--------------------
## Caldera
Caldera provides a modular platform for modeling, scripting, and executing
adversary behavior. It allows users to construct emulation plans, provides
agents for communicating with the command and control server,
and enables users to evaluate security detections in a
structured, scalable, and repeatable way. With the use of plug-
ins and community-contributed features, Caldera supports a range of use
cases including adversary emulation, purple teaming, detection
engineering, and continuous security validation. Using Caldera,
defenders can emulate known threat actor behavior and perform
other red team activity to evaluate their organization’s defensive
capabilities, test analytics, and find detection gaps. As a modular tool
based on the MITRE ATT&CK framework, Caldera is designed to be
extensible, intelligence-driven, and automation-friendly.
Caldera has been incubating since 2025-12-19.
### Three most important unfinished issues to address before graduating:
1. Rebuild contributor momentum and broaden the committer base.
Contribution has slowed since late August, and all five non-mentor
PPMC members work at MITRE. Graduation needs at least three legally
independent committers, so this is our top priority. We are
re-engaging contributors through a developer guide, workshops and
our Discord community, and we plan to invite regular outside
contributors to become committers.
2. Prepare a first Apache release. We have reviewed what a first
release needs. Open items: ASF source headers; LICENSE entries for
bundled JavaScript and CSS; two LGPL-3.0 dependencies (ldap3,
svglib) to make optional or replace; compiled binaries and
third-party payloads in the plugins; a KEYS file; a written release
process; and a license check in CI.
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
This report is late, and we apologize. Activity slowed in September,
and the PPMC is now focused on getting the project back on track. Our
immediate steps are to clear the review queue (67 open pull requests,
66 of which need an approving review), to re-engage contributors, and
to move project discussion onto dev@.
We would welcome mentor guidance on two questions:
- How should we bring the MITRE-hosted plugin repositories into the
ASF: software grant coverage or IP clearance?
- Can third-party security tools used as test payloads be included in
an Apache release? We plan to raise this with Legal Affairs.
### How has the community developed since the last report?
- New contributors are arriving. Five people outside the PPMC opened
six pull requests: hardening file uploads against path traversal,
building Docker images on tag pushes, a payload encoder fix, a
dependency fix, a documentation fix and a new plugin. Reviewing
these is our first priority.
- To rebuild contributor momentum, we proposed a getting-started guide
for developers on dev@ (2026-08-28) and are now preparing it, along
with workshops for new contributors [ADD dates if set].
- Our Discord community is growing [ADD a number]. We plan to announce
workshops on dev@ and users@, and to bring discussions that affect
the project back to dev@.
- No new committers or PPMC members were added. We plan to finish
onboarding the remaining initial committers named in the proposal.
- dev@ was quiet, with three messages in September. We are following
up on a user question about ATT&CK v19.1 support.
- GitHub stars passed 7.4k, up from 7.2k at the last report.
### How has the project developed since the last report?
- Five pull requests were merged on 2026-08-26 and 2026-08-27:
security-related updates for aiohttp, cryptography and asyncssh;
three front-end dependency updates; and a change that routes GitHub
notifications to [email protected].
- We completed a graduation readiness review covering licensing,
releases, the website and branding. Its findings drive items 2 and 3
above.
- Four issues were opened and three were closed.
- There have been no commits to master since 2026-08-27 and no release
yet. Clearing the review queue is the next step.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No Apache release yet. The last release before incubation was 5.3.0
(2025-04-24)
### When were the last committers or PPMC members elected?
Yes. PJ Fanning has been consistently active
and helpful, including on infrastructure and reporting, and Francis
Chuang helped with the website move. One item needs attention: the
podling status page has not been updated since 2025-12-19. We will
work with our mentors to bring it up to date.
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
Yes
Remaining work we have identified:
"Apache Caldera (Incubating)" naming and the incubation disclaimer
in the README, the website title and the documentation on Read the
Docs, which is still titled "MITRE Caldera".
### Signed-off-by:
- [ ] (caldera) Kevin Ratnasekera
Comments:
- [ ] (caldera) Francis Chuang
Comments:
- [X] (caldera) PJ Fanning
Comments:
- [ ] (caldera) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## Maka
Maka is a local-first AI agent runtime and workspace. It records model
messages, tool calls, tool results, permission decisions, and termination
events in append-only logs.
Maka has been incubating since 2026-08-13.
### Three most important unfinished issues to address before graduating:
1. Complete IP clearance for the initial codebase: record the mentors'
sign-off on the contributor review, now that the material
contributors have ICLAs on file, and publish the podling status page.
2. Make the first Apache release, 0.2.0-incubating, and keep developer
nightly builds (GitHub prereleases, npm nightly tag) unpromoted and
labelled with the incubation disclaimer.
3. File the podling name search and grow the committer and PPMC base
beyond the initial contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing requires Board action. For IPMC awareness: the IPMC vote on
0.2.0-incubating RC2 has three binding +1 votes and one binding -1.
The -1 concerns ICLA coverage for a material contributor from before
the repository had a license, and public nightly builds. That
contributor has since been elected a committer and the Secretary has
his ICLA on file. Nightly builds are no longer linked from the website
or README, and their release pages are gaining the incubation
disclaimer. The PPMC is following up on the vote thread.
### How has the community developed since the last report?
This is the first report. Since 2026-08-13:
- Elected 14 new committers: Chengbo Zhang, Blake Yang, Yilin Wang,
Yunpei Zhou, Junwei Yao, Guangdong Liu, Xiao Liu, Qinyu Wan,
Guoliang Sun, Xinhao Xu, Jiahao Zhang, Zhiyi Wang, Chong Wang and
Jiaxiong Liu (account pending).
- Elected two new PPMC members, Zhiyi Wang and Jiahao Zhang.
- 116 distinct contributors had pull requests merged, 20 of them for
the first time.
- GitHub Discussions are mirrored to dev@, which carried about 40
design threads, including the website rebuild, the pull request
flow, and the committer nomination process.
- Held two release votes on dev@ (RC1 and RC2).
### How has the project developed since the last report?
- Moved the repository to apache/maka and set up the mailing lists
and the maka.apache.org website.
- Merged 1,495 pull requests; 899 issues were opened and 760 closed.
- Prepared the first source release: ASF headers, LICENSE and NOTICE
review, DISCLAIMER-WIP, and removal of code with unclear provenance.
RC1 was cancelled after IPMC feedback; RC2 is under IPMC vote.
- Product work focused on WorkHub, a single conversational entry
point for delegating work, and on hardening the Runtime Host, which
owns session execution and storage.
### 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:
None yet. 0.2.0-incubating RC2 is under IPMC vote.
### When were the last committers or PPMC members elected?
September 2026: Chong Wang as a committer and Jiahao Zhang as a PPMC
member.
### Have your mentors been helpful and responsive?
Yes. Mentors reviewed and voted on the release candidates and advised
on IP clearance and the release process. Open item: the mentors'
sign-off on the contributor review for the initial codebase.
### Is the PPMC managing the podling's brand / trademarks?
The website and README use "Apache Maka (incubating)". No podling name
search has been filed yet; the PPMC will file one. No third-party
misuse is known.
### Signed-off-by:
- [ ] (maka) Hao Ding
Comments:
- [X] (maka) Huajie Wang
Comments:
- [ ] (maka) Zhuoran Shang
Comments:
- [ ] (maka) Xinyu Tan
Comments:
- [X] (maka) Zili Chen
Comments:
- [X] (maka) Mingyang Liu
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AU: Report from the Apache InLong Project [Charles Zhang]
-----------------------------------------
Attachment AV: Report from the Apache James Project [Benoit Tellier]
## Description:
The Apache James Project delivers a rich set of open source modules
and libraries, written in Java, related to Internet mail which build
into an advanced enterprise mail server.
## Project Status:
Current project status: Ongoing
Issues for the board: No issue require board attention
## Membership Data:
Apache James was founded 2003-01-22 (24 years ago)
There are currently 44 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was René Cordier on 2025-02-03.
- Felix Auringer was added as committer on 2026-09-04
## Project Activity:
Recent releases: JAMES-3.9.1 was released on 2026-10-05. MIME4J-0.8.15 was
released on 2026-09-10. JAMES-3.9.0 was released on 2025-10-03.
Project works on a more modern version of the website, with better content
organisation.
Project plans an upcoming 3.10.0 release.
## Community Health:
Last 3 months saw new contributor (at least 4) starting contributing to
James. This is possible thanks to AI tooling but newcomers engage on
discussions on the mailing list, which raises interesting discussions.
Below stats highlight this matter of fact.
[email protected] had a 66% increase in traffic in the past quarter
(10 emails compared to 6) [email protected] had a 56% increase in
traffic in the past quarter (1321 emails compared to 843)
[email protected] had a 52% increase in traffic in the past quarter
(257 emails compared to 168) [email protected] had a 454% increase
in traffic in the past quarter (61 emails compared to 11) 24 JIRA tickets
opened and 16 closed in the past quarter.
Project does best effort to onboard those new contributors.
-----------------------------------------
Attachment AW: Report from the Apache Jena Project [Andy Seaborne]
## Description:
The mission of Jena is the creation and maintenance of software related to Java
framework for building Semantic Web applications
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Jena was founded 2012-04-18 (14 years ago)
There are currently 21 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- Øyvind Gjesdal was added to the PMC on 2026-08-13
- No new committers. Last addition was Øyvind Gjesdal on 2026-01-26.
## Project Activity:
Apache Jena v6.2.0 was released 2026-07-31. The release included contributions
from outside the usual contributors, and this has continued into the current
development cycle.
## Community Health:
The project has received a considerable number of reported issues. Many are
valid but at the same they generate a lot of review work. The project does not
have additional resources to call in. What will happen is to have a steady, if
slow, processing of the backlog. There are some PRs to match, also generated;
these too need careful review and add to the workload.
-----------------------------------------
Attachment AX: Report from the Apache JMeter Project [Bruno Demion]
## Description:
The mission of JMeter is the creation and maintenance of software related to
Java performance and functional testing
## Project Status:
Current project status: Ongoing, with medium activity
Issues for the board: There are no issues requiring board attention at
this time.
## Membership Data:
Apache JMeter was founded 2011-10-26 (15 years ago)
Jakarta JMeter, first version was released 1998-12-15 (28 years ago)
There are currently 13 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Vladimir Sitnikov on 2018-06-08.
- No new committers. Last addition was Maxime Chassagneux on 2017-02-15.
## Project Activity:
- Current objective is to move the code base of JMeter to Java 17+
(from Java 8) for next major release (6.0)
- Recent releases:
5.6.3 final was released on 2024-01-07.
## Community Health:
- The project has a low activity during last quarter.
-----------------------------------------
Attachment AY: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AZ: Report from the Apache JSPWiki Project [Alex O'Ree]
## Description:
The mission of JSPWiki is the creation and maintenance of software related to
Leading open source WikiWiki engine, feature-rich and built around standard
J2EE components (Java, servlets, JSP).
## Project Status:
Current project status: Ongoing, with low activity, primarily with
addressing reported security issues.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache JSPWiki was founded 2013-07-16 (13 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 Alex O'Ree on 2025-11-05.
- No new committers. Last addition was Alex O'Ree on 2025-11-06.
## Project Activity:
- 2.12.5 was released 2026-08-22
- 3.0.0 was released 2026-08-22
- 2.12.4 was released on 2026-04-08.
- work on 2.12.6 is on going to mitigate additional CVEs
- work on 3.0.1 is on going and should be before end of the year.
## Community Health:
- [email protected] had a 78% increase in traffic in the past quarter
(186 emails compared to 104) - mostly due to pull request traffic and
discussions on technical fixes for open issues.
- [email protected] had a 700% increase in
traffic in the past quarter (24 emails compared to 3).
Mostly due to release announcements and some day to day operations
off of jspwiki.apache.org's website (login/permissions issues).
- JIRA activity
- 3 public JIRA tickets opened and 2 closed in the past quarter.
- 30 JIRA tickets opened related to security findings
-----------------------------------------
Attachment BA: Report from the Apache Kudu Project [Andrew Wong]
## Description:
The mission of Apache Kudu is the creation and maintenance of software related
to a distributed columnar storage engine built for the Apache Hadoop ecosystem.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kudu was founded 2016-07-19 (10 years ago)
There are currently 35 committers and 35 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ashwani Raina on 2026-06-29.
- No new committers. Last addition was Ashwani Raina on 2026-06-26.
## Project Activity:
- 1.18.1 was released on 2026-01-09
- 1.18.0 was released on 2025-07-10
- 1.17.1 was released on 2024-11-15.
## Community Health:
- Development activity measured in the number of commits has marginally
increased (58 vs 60) and the number of unique developers went up from 10 to
12.
- Traffic to dev mailing lists is constant while traffic to dev and issues
mailing lists has decreased by 25%.
- Community activity measured in community Slack is as follows: (the number of
weekly active users dipped by 5%, and weekly public posters dipped by 22%).
- Technical highlights:
- Compaction now skips fewer rowsets and can be tuned without a restart.
- Diff scans can now return rows that were inserted and deleted within the
scan window.
- The leader rebalancer spreads leaders more evenly across servers and
prefers moving followers.
- The Prometheus metrics endpoint can now export fewer, more targeted metrics.
- Builds can use pre-built third-party libraries and support newer compilers
and platforms.
- Java moved to Gradle 9 and JDK 25, and Python packaging was updated.
-----------------------------------------
Attachment BB: Report from the Apache Kvrocks Project [Mingyang Liu]
## Description:
Apache Kvrocks is a distributed key-value NoSQL database that uses
RocksDB as its storage engine and supports the Redis protocol.
## Project Status:
Current project status: Ongoing.
Issues for the Board: None.
This report covers activity since the June 2026 report.
## Membership Data:
The project has 30 committers and 14 PMC members.
- Ji Huayu (jihuayu) joined the PMC on 2026-08-30.
- The most recently reported committer addition was Xiaojun Yuan on
2026-02-24.
## Project Activity:
Two releases were made since the previous report:
- Apache Kvrocks 2.16.0 on 2026-06-21.
- Apache Kvrocks 2.17.0 on 2026-09-19.
These releases improved Redis compatibility, operational visibility,
and reliability. Notable additions include conditional SET operations
and client traffic controls in 2.16.0, and JSON-formatted INFO output,
configurable client output-buffer limits, and TDIGEST.CDF in 2.17.0.
The releases also included security fixes and hardening improvements.
Development continued on Hash Field Expiration, including replication,
migration, and export support. This feature remains disabled in 2.17.0
and is not yet available in a stable release.
## Community Health:
The project continues to receive contributions from new participants;
the 2.17.0 release notes credit nine first-time contributors.
Following the contribution-quality concerns described in the previous
report, the community added automated reminders directing contributors
to its AI-assisted contribution guidelines and asking them to understand
and explain their changes.
-----------------------------------------
Attachment BC: Report from the Apache Lucene.Net Project [Shad Storhaug]
## Description:
Apache Lucene.NET is a port of the Lucene search engine library, written in C#
and targeted at .NET runtime users.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Lucene.Net was founded 2012-08-14 (14 years ago)
There are currently 18 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- Elad Margalit was added to the PMC on 2026-06-21
- Elad Margalit was added as committer on 2026-06-21
## Project Activity:
In June 2026, we released 4.8.0-beta00018 primarily to fix some
vulnerabilities. We are nearly dev complete with what should be our final beta
release, consisting of many significant performance and correctness
improvements, improved test coverage, and streamlined operations. Work has
been ongoing to get our dependencies J2N, ICU4N, and NOpenNLP ready for
integration into the final beta release, and that work is nearly complete. We
hope to report in the next board report that our final beta has been released.
Recent releases:
Apache-Lucene.Net-4.8.0-beta00018 was released on 2026-06-22.
Apache-Lucene.Net-4.8.0-beta00017 was released on 2024-10-29.
Apache-Lucene.Net-4.8.0-beta00016 was released on 2022-02-17.
## Community Health:
We have had approximately 110 PRs opened or merged since the last board report
including those by 8 new contributors to the project.
Mailing lists:
- [email protected] had a 216% increase in traffic in the past quarter
(79 emails compared to 25)
- [email protected] had a 22% increase in traffic in the past quarter
(501 emails compared to 409)
-----------------------------------------
Attachment BD: Report from the Apache Mahout Project [Jie-Kai Chang]
## Description:
The mission of Mahout is the creation and maintenance of software related to
Scalable machine learning library
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Mahout was founded 2010-04-21 (16 years ago)
There are currently 36 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Rich Huang was added to the PMC on 2026-09-01
- Yu-Chen Lai was added as committer on 2026-09-04
## Project Activity:
Apache Mahout continued steady development during Q3 2026, with Qumat and QDP
remaining the project's primary focus.
No release was made this quarter. The most recent release remains Apache
Mahout Qumat 0.6.0, released on 2026-05-31. Following the release-heavy Q2,
this quarter concentrated on post-release hardening, documentation, website,
and project governance work.
## Community Health:
Mahout remains in a strong community health position. The ASF Reporter
community health score is 10.00, marked "Super Healthy". The project added one
new PMC member and one new committer this quarter, and code contributions came
from PMC members, committers, and non-committer contributors.
Commit volume on the main branch was lower than in Q2. Part of this is
expected, since Q2 included the 0.6.0 release cycle. In addition, a
significant share of the core contributors' time this quarter went into
preparing and delivering talks at Community Over Code Asia and Community Over
Code Glasgow, as well as organizing the Mahout hackathon session in Glasgow,
which temporarily slowed the pace of development.
The project was active at ASF community events this quarter. Jie-Kai
Chang and Guan-Hua Wen presented "Accelerating Quantum Machine Learning:
Building a GPU-Accelerated Data Plane in Apache Mahout" at Community Over
Code Asia 2026 in Beijing on 2026-08-08. At the time of writing, Mahout is
also participating in Community Over Code 2026 in Glasgow (2026-10-11 to
2026-10-14), where Guan-Ming Chiu and Kuan-Hao Huang are presenting
"Accelerating Quantum Machine Learning: Building a GPU-Accelerated Data Plane
(QDP) with Rust and CUDA in Apache Mahout". Mahout is also hosting a session
in the conference's first-year hackathon pilot on 2026-10-13, giving new and
existing contributors dedicated time to work on real project tasks.
Mailing list activity decreased compared with the previous quarter. As of
2026-10-09, [email protected] had 15 emails in the past quarter compared
with 26 in the previous quarter, a 43% decrease. [email protected]
had 90 emails compared with 207, a 57% decrease.
As noted in the previous report, dev@ traffic now largely reflects human
discussion rather than GitHub notification noise, and most day-to-day
coordination happens on GitHub pull requests and issues. The decrease in
issues@ traffic is consistent with the lower PR and issue volume of a
non-release quarter following the 0.6.0 release cycle in Q2. The recent
change to route GitHub Discussions to dev@ (2026-09-21) is expected to bring
more community discussion back onto the mailing list in the coming quarter.
-----------------------------------------
Attachment BE: Report from the Apache Maven Project [Hervé Boutemy]
Maven Board Report - October 2026
---------------------------
## Description:
The mission of Maven is the creation and maintenance of software related to
Java project management and comprehension tools.
## Project Status:
Current project status: ongoing with high activity.
Issues for the board: none.
## Membership Data:
Apache Maven was founded 2003-03-01 (24 years ago)
There are currently 76 committers and 31 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 Matthias Bünger on 2026-06-07.
- Per Nyfelt was added as committer on 2026-08-24
- Sergey Chernov was added as committer on 2026-09-07
## Project Activity:
Releases since last report:
- Maven Resource Plugin 4.0.0-beta-3 was released on 2026-10-12.
- Maven Filtering 4.0.0-beta-2 was released on 2026-10-12.
- Maven Clean Plugin 4.0.0-beta-3 was released on 2026-10-12.
- Apache Maven 3.10.0 was released on 2026-10-01.
- Maven Resolver 2.0.24 was released on 2026-10-01.
- Maven DOAP Plugin 3.0.0-M2 was released on 2026-09-26.
- Maven Script Interpreter 1.9 was released on 2026-09-26.
- Maven Shared JAR 3.2.1 was released on 2026-09-26.
- Maven Shared Utils 3.5.0 was released on 2026-09-26.
- Apache Maven 4.0.0-RC7 was released on 2026-09-24.
- Apache Maven Parent POMs 50 was released on 2026-09-17.
- Apache Parent POM 40 was released on 2026-09-17.
- Maven Resolver 2.0.23 was released on 2026-09-17.
- Maven Artifact Plugin 3.7.0 was released on 2026-09-15.
- Maven Shared IO 3.1.0 was released on 2026-09-14.
- Maven Deploy Plugin 3.2.0 was released on 2026-09-11.
- Maven Deploy Plugin 4.0.0-beta-3 was released on 2026-09-11.
- Maven Install Plugin 3.2.0 was released on 2026-09-11.
- Maven Install Plugin 4.0.0-beta-3 was released on 2026-09-11.
- Apache Maven Plugin Tools 3.16.0 was released on 2026-09-06.
- Apache Maven Plugin Tools 4.0.0-beta-3 was released on 2026-09-06.
- Apache Maven Dependency Analyzer 1.17.2 was released on 2026-09-05.
- Apache Maven Surefire 3.6.0 was released on 2026-09-03.
- Apache Maven Script Interpreter 1.8 was released on 2026-09-01.
- Maven Compiler Plugin 3.16.0 was released on 2026-08-30.
- Maven Compiler Plugin 4.0.0-beta-5 was released on 2026-08-26.
- Maven Resolver 2.0.22 was released on 2026-08-24.
- Apache Maven Build Cache Extension 1.3.0 was released on 2026-08-16.
Maven Shared IO, Maven Shared Incremental are now retired, and Maven Verifier
retirement is in progress.
Our Maven 4 plan is progressing well:
- We released Maven 3.10.0 as a transition release to gather feedback on key
updates, including Maven Resolver 2, stricter controls, Reproducible Builds by
default, and other changes that can be adopted before Maven 4 introduces more
structural changes.
- We released Maven 4.0.0-RC-7, which is expected to be the final release
candidate: Feedback and experience from 3.10 will be incorporated before we do
4.0.0 GA soon.
- We will reach out to tool vendors again to collect feedback on their tools'
readiness for Maven 4, helping users adopt the new Maven version more easily.
Support for Java Modules in Maven 4.0 is also progressing well.
We're working with the ATR team to prepare for full-scale ATR usage across our
80 projects, including the addition of necessary features.
We're also verifying and fixing Maven projects' configurations in ATR.
Two Maven PMC members have joined the GLASSWING initiative at the ASF and are
working on hardening Maven:
- Together with the security team, we have prepared the Maven Threat Model
for AI security scanners and propagated it to all Maven subprojects.
- The first AI security scans were conducted in August 2026, and we're now
analyzing the results. Some of the issues have already been fixed in
Maven Resolver 2, Maven 3.10.0, and several Maven plugins.
## Community Health:
Based on in-person feedback at conferences and local meetups, more and more
users are aware of Maven 4 and want to upgrade soon, putting themselves in a
good position for future upgrades. They are particularly interested in better
support for Java Modules and mixins (the latter are planned for Maven 4.1).
They also support the decision not to rush the Maven 4 final release in favor
of delivering a more stable version with fewer bugs.
With Maven 3.10.0 introducing a new phase of evolution, we're seeing increased
community engagement, with users reporting new issues and contributing code.
Some contributors are students looking for mentorship, while others are
experienced users who can now contribute by leveraging their knowledge of
Maven and AI-assisted coding tools. This presents new opportunities to renew
our community, but we'll need to organize onboarding.
The use of AI by maintainers is generating a very high volume of commits, pull
request reviews, builds, and other activity across Maven subprojects. This is
causing some friction, with human PR reviews getting lost among automated
reviews and updates, and large-scale updates reducing the signal-to-noise
ratio. We're trying to establish guardrails that preserve the benefits of this
new automation, but this remains challenging.
-----------------------------------------
Attachment BF: Report from the Apache MINA Project [Thomas Wolf]
## Description:
The mission of MINA is the creation and maintenance of software related
to Multipurpose Infrastructure for Network Application
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache MINA was founded 2006-10-25 (20 years ago)
There are currently 29 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 Gary D. Gregory on 2023-09-13.
- Marcin Lamparski was added as committer on 2026-09-21
## Project Activity:
* Apache MINA: an asynchronous I/O library. Mature & stable. Still
working through vulnerability findings from an AI scan; otherwise
calmer than last quarter. Two vulnerabilities reported through e-mail
in triage.
* Apache MINA SSHD: library for client- and server-side SSH. The project
is mature & stable and is under active development. Releases 2.19.0
and 3.0.0-M5 published 2026-07-09; releases 2.20.0 and 3.0.0-M6
addressing 8 vulnerabilities reported via e-mail were released
2026-09-28. A fix for one still open reported vulnerability is in the
works.
* Apache MINA FtpServer: FTP server library. Project in maintenance
mode; no activity this quarter.
* Vysper & AsyncWeb are dormant. We got a vulnerability report against
Vysper; we plan to accept and publish it as "unsupported when
assigned", and update the Vysper web pages to clearly state the
project is dormant.
## Community Health:
Our community is healthy but small. Marcin Lamparski joined as a new
committer. Projects use Github and JIRA as issue trackers; both MINA and
MINA SSHD got some contributions via Github.
-----------------------------------------
Attachment BG: Report from the Apache MyFaces Project [Bernd Bohmann]
## Description:
The mission of MyFaces is the creation and maintenance of software related to
JavaServer(tm) Faces implementation and components
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: None
## Membership Data:
Apache MyFaces was founded 2005-02-23 (22 years ago)
There are currently 81 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Melloware on 2024-01-25.
- No new committers. Last addition was Milan Siebenbürger on 2024-01-24.
## Project Activity:
Release highlights for MyFaces Core and Apache Tobago over the past three
months (July – October 2026):
MyFaces Core Releases
MyFaces Core 4.1.4, 4.0.4, 3.0.4, and 2.3.12 (September 2026):
Security Patches:
Addressed the CVE-2026-68536 vulnerability concerning EL-bound src
attributes in ui:include that allowed unauthorized local file access.
CVE-2026-76646 is a Denial of Service (DoS) vulnerability caused by
unbounded partial rendering IDs.
Classpath Scanning:
Resolved resource-scanning issues in virtual file system
(VFS) environments like JBoss (MYFACES-4767).
Quarkus Extensionless Mapping:
Fixed automatic mapping to correctly register and resolve views located in
subfolders (MYFACES-4729).
Apache Tobago Releases
Tobago 6.12.2 (September 2026):
Maintenance release
Tobago 6.12.1 (September 2026):
Minor update .
Tobago 6.12.0 (September 2026):
Major feature update including: Client-Side Collapsible API: Added expand() and
collapse() methods to collapsible custom elements (tobago-box,
tobago-offcanvas, tobago-panel, tobago-popup, and tobago-section). Popover
Trigger Attribute: Introduced trigger and helpTrigger attributes allowing
popovers to be activated via "click", "focus", or "hover". Cancelable Dropdown
Events: Made tobago.dropdown.show and tobago.dropdown.hide events cancelable
via .preventDefault().
## Community Health:
- Apache MyFaces Core is healthy.
UI-Component Sets:
- Apache Tobago is healthy.
- Apache Trinidad is in maintenance mode.
Last developer commit was Sept 2017.
- Myfaces Tomahawk is in maintenance mode.
Last developer commit was May 2016.
Last commit on behalf of a contributor was May 2016.
Add-ons and Extensions:
- Apache MyFaces Portlet Bridge is in maintenance mode.
Last developer commit was Jan 2014.
Last commit on behalf of a contributor was May 2015.
- Apache MyFaces CODI is in maintenance mode.
CODI was replaced by Apache DeltaSpike so new development
happens there. Last commit March 2014.
- Apache MyFaces Orchestra is in maintenance mode.
New projects use CDI and DeltaSpike instead.
Last commit on behalf of a contributor was August 2016.
- Apache MyFaces ExtVal is in maintenance mode.
Last commit June 2014.
- Apache MyFaces Commons is in maintenance mode.
Last commit August 2012.
- Apache MyFaces Ext-Scripting is in maintenance mode.
Last commit Sept 2017.
- Apache MyFaces Test is in maintenance mode (Used by Myfaces Core).
Last commit May 2017.
-----------------------------------------
Attachment BH: Report from the Apache NiFi Project [David Handermann]
## Description:
The mission of NiFi is the creation and maintenance of software related to
providing an easy to use, powerful, and reliable system to process and
distribute data.
Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
integrate with and leverage the command and control of NiFi. There are both
Java and C++ implementations.
Apache NiFi NAR Maven Plugin is an extension for Apache Maven supporting
NiFi Archive creation for runtime isolated class loading.
Apache NiFi Registry is a centralized registry for key configuration items
including flow versions, assets, and extensions for Apache NiFi and Apache
MiNiFi.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: None
## Membership Data:
Apache NiFi was founded 2015-07-14 (11 years ago)
There are currently 56 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Mark Bathori on 2025-11-11.
- Bob Paulin was added as committer on 2026-09-11
## Project Activity:
Apache NiFi released version 2.11.0 on 2026-08-03 and version 2.12.0 on
2026-09-08. These releases built on the Apache NiFi API versions 2.10.0,
2.11.0, and 2.12.0, as well as releases of Apache NiFi NAR Maven Plugin 2.4.0.
The project has followed a shorter release vote cycle for minor Apache NiFi
API releases that include only one or two method changes while maintaining the
regular 72 hour voting window for standard application releases. Although
maintaining independent release versioning for the public API requires some
amount of the additional work, the decoupled versioning and the NiFi
Improvement Proposal process continue to promote careful consideration of
changes that impact external extension capabilities and internal framework
direction.
Recent project releases continue to extend the Connector framework and support
for external versioning using Flow Registry Clients. Version 2.12.0 deprecated
several historical file packaging formats and also deprecated fine-grained
component authorization for removal, providing the foundation for future
streamlining of the project security model. The project continues to follow a
rapid adoption strategy for upgrading third-party dependencies, minimizing
transitive security issues while striving to maintain compatibility with
current features.
## Community Health:
The project continues to have active community participation in pull requests,
Jira issues, and discussions on the project Slack community. Project
improvement proposals and discussions continue to use mailing lists for public
visibility and archiving. The project has just under 4,000 followers on
LinkedIn, and over 4,000 members on the Slack community, reflecting stable
interaction as compared to the previous quarter.
The project security team continues to observe an increase in the stream of
AI-generated findings, with a mixture of applicable and non-applicable issues.
The project has published a number of security vulnerabilities in
response to these findings using the standard coordinated release process.
-----------------------------------------
Attachment BI: Report from the Apache Nutch Project [Sebastian Nagel]
## Description:
Apache Nutch is a highly extensible and scalable open source web crawler
software project based on Apache Hadoop® data structures and the MapReduce
data processing framework.
## Project Status:
Current project status: ongoing with medium to low activity
Issues for the board: none
## Membership Data:
Apache Nutch was founded 2010-04-21 (15 years ago)
There are currently 23 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Joe Gilvary on 2024-08-07.
- No new committers. Last addition was Joe Gilvary on 2024-08-07.
## Project Activity:
Nutch 1.23 was released on 2026-09-08. The release addressed and shipped three
CVEs.
Over the last three months, work has focused on improving the security and
quality of the code, as well as enhancing the testing and continuous
integration workflows. The dominant work during the next quarter is likely to
be handling incoming security reports and providing fixes. Improving the
security also includes transferring security fixes found in related projects,
such as Apache StormCrawler.
## Community Health:
The number of contributions (Jira issues, commits and GitHub pull requests) is
on a steady level. We continued to receive contributions from new people.
The release of version 1.23 took longer than expected. The first release
candidate was withdrawn due to a late-discovered regression. Testing and
reviewing the second release candidate took longer than expected, as did
waiting for the three binding votes. While this can be explained by the
holiday period, we need to address the issue of ensuring that enough PMC
members are available at any given time to guarantee the project's management.
-----------------------------------------
Attachment BJ: Report from the Apache NuttX Project [Alin Jerpelea]
## Description:
The mission of Apache NuttX is the creation and maintenance of software related
to a mature, real-time embedded operating system (RTOS)
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: no issues for the board
## Membership Data:
Apache NuttX was founded 2022-11-16 (4 years ago)
There are currently 41 committers and 24 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 Matteo Golin on 2025-11-10.
- Jorge Guzman was added as committer on 2026-08-28
## Project Activity:
Security release
13.0.1 was released on 2026-09-15.
Quarterly release
13.1.0 was released on 2026-10-04.
The project is adapting to the CVE influx and added a security release
between the regular quarterly releases
## Community Health:
Following Zephir vendor HAL colaboraiton several vendors want to host
the HAL code on a common place and maintain the code together with the
community.
Espressif is investigating if they can move the code under ASF while
other vendors would like to have a separate repository outside ASF
We have several discussions and ongoing vote on this topic reflected in the
[email protected] which had a 137% increase in traffic in the past
quarter (539 emails compared to 227)
-----------------------------------------
Attachment BK: Report from the Apache OpenJPA Project [Mark Struberg]
## Description:
The mission of OpenJPA is the creation and maintenance of software related to
OpenJPA: Object Relational Mapping for Java
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache OpenJPA was founded 2007-05-16 (19 years ago) There are currently 37
committers and 18 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 Maxim Solodovnik on 2019-04-13.
- Richard Zowalla was added as committer on 2026-07-16
## Project Activity:
There is active development of Jakarta Persistence 3.2 implementation right
now. Most work is done by Richard Zowalla with the help of Paulo Cristovão de
Araújo Silva Filho. Hopefully we will release 4.2.0 as soon as all remaining
issue will be addressed
## Community Health:
Hopefully we will invite 2 new PMC members
So, I guess, we good :)
-----------------------------------------
Attachment BL: Report from the Apache OpenMeetings Project [Maxim Solodovnik]
## Description:
The mission of OpenMeetings is the creation and maintenance of software
related to OpenMeetings: Web-Conferencing and real-time collaboration
## Project Status:
Current project status: Dormant
Issues for the board: none.
## Membership Data:
Apache OpenMeetings was founded 2013-01-25 (14 years ago) There are currently
30 committers and 28 PMC members in this project. The Committer-to-PMC ratio
is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ali Alhaidary on 2021-03-22.
- No new committers. Last addition was Ali Alhaidary on 2021-04-07.
## Project Activity:
Current development efforts are focused on addressing security issues. 1 is
being fixed right now, 3 going to be rejected. We are going to release 9.2.0
as soon as last issue will be fixed and Apache Wicket (we are based on) will
be released
Recent releases:
- 9.1.0 was released on 2026-07-08.
- 9.0.0 was released on 2026-03-31.
- 8.1.0 was released on 2025-09-12.
## Community Health:
We have not much email traffic and user queries these days. All emails are
being answered as soon as possible :)
-----------------------------------------
Attachment BM: Report from the Apache OpenOffice Project [Dave Fisher]
## Description:
The mission of OpenOffice is the creation and maintenance of software related
to an open-source, office-document productivity suite
## Project Status:
Current project status: Ongoing Moderate
Issues for the board: None
## Membership Data:
Apache OpenOffice was founded 2012-10-16 (14 years ago)
There are currently 141 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:1.
Community changes, past quarter:
- No new PMC members. Last addition was Czesław Wolański on 2023-01-14.
- No new committers. Last addition was John Bampton on 2025-01-07.
## Project Activity:
- 4.1.17 will be released by 2026-10-17. RC2 is building 10-08.
- 4.1.16 was released on 2025-11-10
We had to disclose a critical vulnerability on October 2 before the reporters
gave public demonstration. There was a HackerNews story on October 6:
https://thehackernews.com/2026/10/libreoffice-and-openoffice-flaws-let.html?m=1
We want to thank Arnout and Piotr from the ASF Security team for all of their
guidance and help.
Developers are making great use of coding assistants to solve many long standing
issues. A 5.0 dev or alpha release is planned before the end of the year. This
will modernize the operating system / chips we build to include macOS Silicon
and Windows 64. Python 3.11 + support is also planned.
## Community Health:
The work on fixing the long standing issues has reinvigorated the community.
One committer returned by asking "am I still a committer?". Merit does not
expire and this is a great example.
Mailing list activity shows the reengagement:
- [email protected] had a 101% increase in traffic in the past quarter
(352 emails compared to 175)
- [email protected] had a 427% increase in traffic in the past
quarter (153 emails compared to 29):
- 0 BugZilla tickets opened and 34 closed in the past quarter
-----------------------------------------
Attachment BN: 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, CDI-4.1).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Last quarter was a bit more quiet than before.
We've shipped meecrowave-2.1.1 and will soon prepare for more updates.
## 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:
- 4.1.1 was released on 2026-08-07.
- 4.1.0 was released on 2026-05-03.
- meecrowave-2.1.1 was released on 2025-08--18.
-----------------------------------------
Attachment BO: Report from the Apache ORC Project [William Hyun]
-----------------------------------------
Attachment BP: Report from the Apache Parquet Project [Julien Le Dem]
Parquet Report October 2026
Due date: Oct 14, 2026
Board Meeting date: Oct 21, 2026
## Description:
A column-oriented data file format designed for efficient data storage and
retrieval. It provides high performance compression and encoding schemes to
handle complex data in bulk and is supported in many programming languages and
analytics tools.
Parquet consists of a format specification (the Parquet format) and several
implementations, one of which (Parquet Java) is developed directly under the
umbrella of the Apache Parquet project. Several implementations such as
Parquet C++, Parquet Go, and Parquet Rust are developed as part of the Apache
Arrow project. Non-Apache implementations also exist, some of them closed
source.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Parquet was founded 2015-04-21 (11 years ago)
There are currently 42 committers and 32 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 Andrew Lamb on 2026-01-20.
- Rok Mihevc was added as committer on 2026-07-29
## Project Activity:
Recent releases:
Parquet-Format
2.13.0 on 2026-06-13
Parquet-Java
1.17.1 on 2026-05-12
1.17.0 on 2026-01-13
Parquet-Rust (in Arrow-RS)
60.0.0 on 2026-09-15
59.3.0 on 2026-09-01
59.2.0 on 2026-08-06
58.4.0 on 2026-07-22
Parquet-go (in Arrow-GO)
18.8.0 on 2026-09-08
18.7.0 on 2026-07-21
Parquet-cpp (in Arrow)
26.0.0 on 2026-10-09
25.0.1 on 2026-08-10
25.0.0 on 2026-07-10
(Note that Parquet Go, Rust and C++ implementations are part of
the Arrow code base and released with Arrow. Parquet Go’s and
Parquet Rust’s governance is managed by the Arrow PMC)
Ongoing work:
New encodings:
- The Adaptive Lossless Floating Point spec has been released.
It has three implementations (C/C++, Java, Rust), a well reviewed spec
and example files.
Rust Impl Merged and released as part of arrow-RS 60.0.0
C++ Impl approved, working through final merge gates
Jave Impl : is a work in progress
Golang Impl : will be taken up next.
As it is forward incompatible, we’re working on clarity for how to
release it.
See parquet versioning discussion.
Blog post
https://parquet.apache.org/blog/2026/09/22/
alp-adaptive-lossless-floating-point-encoding-in-apache-parquet/
- PFOR has shown great promise over current encoding schemes by a large factor
We have separated it from Fastlanes discussion.
Currently exploring:
1) Augmenting the encoding with an added delta mode
(for saw-tooth like patterns, or timestamp like patterns)
2) Augmenting the encoding with value interleaving or possibly
using fastlanes.
Both these experiments are very meaningful and we plan to go ahead with PFOR
with future extensibility in mind.
- FSST/OnPair (8,12,16 bits codes) Spec is being finalized.
Following Onpair, we saw great improvements with larger bit codecs that allow
larger symbol tables and faster decoding speeds.
We’re iterating over the design and performance numbers before finalizing
the spec.
Footer working group: final round of feedback requested to finalize the spec.
Parquet versioning definition: We are finalizing the mechanism. Ongoing
discussion thread on the dev list.
Non-contiguous pages proposal in progress.
New types: Finalizing Vector
Release automation: ready to go.
## Community Health:
Community Health Score (Chi): 8.37 (Healthy)
Discussions are regularly happening on the mailing list,
in PRs/Issues on Github and on a regular public meeting
held on google meet (notes are posted on the list)
-----------------------------------------
Attachment BQ: Report from the Apache PDFBox Project [Andreas Lehmkühler]
## Description:
The mission of PDFBox is the creation and maintenance of software related to
Java library for working with PDF documents
## Project Status:
Current project status:Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache PDFBox was founded 2009-10-21 (17 years ago)
There are currently 21 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matthäus Mayer on 2017-10-16.
- No new committers. Last addition was Joerg O. Henne on 2017-10-09.
## Project Activity:
Recent releases:
2.0.37 was released on 2026-07-15.
3.0.8 was released on 2026-07-11.
3.0.5 JBIG2 was released on 2026-05-20.
## Community Health:
- there is a steady stream of contributions, bug reports and questions on the
mailing lists
- we are still working on the security scanner results
- Patrick Corless contributes some code to support hinting for truetype fonts
and Tilman is working with him to incoporate the code
- Volker Kunert contributes some code for alternative glyph positioning
engines to achieve more accurate results especially to support
DIN-SPEC-91379 a mandatory specification in the german public sector
-----------------------------------------
Attachment BR: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BS: Report from the Apache Pinot Project [Kishore G]
-----------------------------------------
Attachment BT: Report from the Apache Pony Mail Project [Rich Bowen]
# Apache Pony Mail — Board Report, October 2026
## Description
Apache Pony Mail provides mail-archiving, archive browsing, and mailing list
interaction services.
## Project Status
Current project status: New (recently graduated)
Issues for the board: None.
This is the third and final of the three required monthly reports following
graduation (August, September, October 2026). Beginning with the next cycle,
Pony Mail moves to its assigned quarterly reporting rotation.
## Membership Data
Apache Pony Mail was established 2026-07-15 (three months ago). There are
currently 11 committers and 6 PMC members in this project.
No new committers or PMC members have been added since graduation. The PMC is
discussing potential committer candidates among the external contributors who
have been active since graduation (see Community Health).
## Project Activity
Development has continued at a steady, healthy pace in the period since the
August report (August-October 2026). The Git repository rename that was
outstanding at graduation has completed, so all work now happens under the
renamed apache/ponymail-foal (and sibling) repositories.
Notable development work in this period:
- Short-term session tokens - A new, trimmed-down approach to programmatic
access (#340, contributed by Jarek Potiuk). It supersedes the earlier
long-term API-token work (#312/#321): rather than long-lived tokens that
cannot track permission changes, a logged-in user can hand an external tool
(CLI, script, MCP server) a short-lived, read-only token bound to their
browser session. The design borrows from the ASF Vulnogram short-term token
model. This drew sustained review discussion on dev@.
- OpenSearch support - Added support for OpenSearch as a backend (contributed
by Claude Brisson / arkanovicz).
- OAuth standards-compliance review - A review of the OAuth implementation for
conformance to the relevant standards (arkanovicz).
- Session handling fix - Advance the cached last_accessed value so a real
hourly session save occurs (arkanovicz).
- Word cloud / setup fix - Fixed a crash when the --wordcloud flag is used in
setup.py (arkanovicz).
- UI improvements - "Copy permalink" affordance for messages (rbowen); added a
login link to the 404 error dialog (#263, contributed by new contributor
basantjamwal).
- Security hardening - A pull request to enforce per-list authorization for
private lists and fail closed, addressing the reported can_access_list()
over-broad access issue (#330).
- Original author re-engagement - Daniel Gruno (Humbedooh), Pony Mail's
original author, contributed a prototype social upvote counter for emails.
- Dependency updates - certifi, google-auth, aiosmtplib, and multipart were
all updated to current versions via Dependabot.
Open issues under discussion include duplicate message display in threaded
views (#345), negative search not working for headers, and follow-through on
the private-list authorization hardening.
## Releases
No releases have been made since graduation. The most recent release remains
0.10-incubating. With the repository rename now complete, the PMC intends to
prepare the project's first Top-Level-Project release in the coming cycle;
this is the project's top near-term housekeeping item.
## Community Health
The dev@ mailing list saw roughly two dozen messages across the August-October
window, driven primarily by GitHub pull-request and issue traffic.
Participation remains healthy for a project of this size, with contributions
from PMC members and several external contributors - notably Jarek Potiuk
(session tokens), Claude Brisson/arkanovicz (OpenSearch, OAuth review, fixes),
and basantjamwal (first contribution). The return of original author Daniel
Gruno (Humbedooh) with a feature prototype is a welcome signal. The users@
list remains quiet, which is expected given the project's niche audience of
mailing-list administrators and the ASF infrastructure itself.
As noted in prior reports, the project is unlikely ever to have a large
contributor community given its specialized domain. The existing PMC has
sufficient depth - multiple active committers across different organizations -
to sustain and develop the software, and the recent influx of external PRs
suggests the pipeline for future committers is healthier than its size alone
would imply.
## Plans
Near-term priorities:
1. Prepare and ship the first TLP release under the new project identity
2. Resolve the private-list authorization hardening and other open
security/correctness issues
3. Continue improving documentation and contributor onboarding, building on
the documentation suite completed earlier in the year
4. Finish a handful of graduation-related tasks
## Reporting Schedule
With this October report, Pony Mail completes the three required monthly
post-graduation reports. The project will file on its assigned quarterly
rotation thereafter.
-----------------------------------------
Attachment BU: Report from the Apache Ranger Project [Selvamohan Neethiraj]
-----------------------------------------
Attachment BV: Report from the Apache Ratis Project [Tsz-wo Sze]
## Description:
The mission of Apache Ratis is the creation and maintenance of software related
to a highly customizable Raft protocol implementation in Java.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Ratis was founded 2021-02-16 (6 years ago)
There are currently 34 committers and 20 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 Xinyu Tan on 2025-06-22.
- Rui Wang was added as committer on 2026-08-26
- Ivan Andika was added as committer on 2026-10-06
- Shilun Fan was added as committer on 2026-10-06
## Project Activity:
We released Ratis 3.3.0 and 3.3.1 on 2026-08-12 and 2026-09-22, respectively.
Ratis 3.3.0 was a minor release adding DataStream streaming reads and
first-class OpenTelemetry tracing support. It also included improvements to
linearizable reads, Raft replication, snapshot handling, TLS configuration,
resource management, APIs, and operational tooling.
Ratis 3.3.1 was a maintenance release with multiple improvements and bug fixes.
## Community Health:
The project is healthy. In this quarter, we had much traffic in the dev@
mailing list (727% increase) due to the release discussion and voting.
We had 137 JIRA tickets opened and 119 closed in the past quarter.
-----------------------------------------
Attachment BW: Report from the Apache Reqsign Project [Zili Chen]
## Description:
Apache Reqsign is a Rust library for signing HTTP requests to cloud
services and obtaining the credentials needed to authenticate them.
It supports multiple cloud providers without requiring their full SDKs
and can be used independently or through projects such as Apache OpenDAL.
## Project Status:
Current project status: New, with ongoing development.
Issues for the board: None.
This is the first Board report for Apache Reqsign, established as a
top-level project on 2026-09-16 after operating as a subproject of
Apache OpenDAL for years. The community is completing the transition
to independent project infrastructure and governance.
## Membership Data:
Apache Reqsign has 9 committers and 9 PMC members, at a 1:1 ratio.
Zili Chen serves as the initial PMC Chair.
The initial PMC was appointed on 2026-09-16. All initial PMC members
previously served on the OpenDAL PMC. There have been no additional
committer or PMC appointments since establishment.
## Project Activity:
Work during this initial reporting period has focused on the TLP
transition and maintaining release continuity:
- The repository was renamed from apache/opendal-reqsign to
apache/reqsign. Repository notification configuration now directs
discussions to [email protected] and development notifications
to [email protected].
- Project branding, repository references, security contacts, and
release documentation have been updated for Apache Reqsign.
Separate development and release distribution areas, including
a Reqsign KEYS file, are in place. Work on the project website
remains outstanding.
- Version 0.20.7 was released on 2026-09-25 under the Apache OpenDAL
Reqsign name and through the OpenDAL distribution area during the
transition. No release under the standalone Apache Reqsign name
has been made as of this report.
- That release expanded cloud credential support, including Aliyun
role assumption, caller-provided identity tokens for AWS, Azure,
and Google, and Google service-account impersonation. It also
improved credential handling and expanded tests against live
Azure and Google services.
## Community Health:
### Are there any risks to the project's sustainability?
The community remains active, and the new PMC brings together
contributors already involved in Reqsign development and release
review under OpenDAL.
The main sustainability risk is the concentration of day-to-day
development and release preparation in a small number of maintainers.
Broadening routine review and release management across the new PMC,
and encouraging additional contributors to take on these roles,
remain priorities.
### Is the PMC capable of responding to security issues and performing
releases if needed?
Yes. Members of the new PMC have experience preparing, reviewing,
and approving Reqsign releases under OpenDAL. The 0.20.7 release
received three binding approval votes from members of the new PMC.
The project has a documented release process and security policy.
Security reports are directed to [email protected], with
the ASF Security Team available for coordination.
### Does the PMC need anything from the Foundation to improve on
contributing to our mission of delivering software for the public good?
No additional requests at this time beyond routine Infrastructure
coordination to complete the TLP transition.
-----------------------------------------
Attachment BX: Report from the Apache ResilientDB Project [Mohammad Sadoghi]
## Description:
Apache ResilientDB is an open-source, modular blockchain framework for
building distributed ledger applications and exploring consensus, storage, and
transaction execution.
## Project Status:
New.
Apache ResilientDB became a top-level project on 16 September 2026. This is
its first Board report as a TLP. Work during this reporting period has focused
on the transition from the Incubator and publishing the first release under
the ResilientDB PMC.
## Issues for the Board:
There are no issues requiring Board attention at this time.
## Community:
The project has 40 committers, including 25 PMC members. The initial TLP PMC
was established on 16 September 2026, with Mohammad Sadoghi as Chair. No
subsequent PMC additions are recorded in the current roster.
The most recently recorded committer addition in the Incubator status record
is Josh Hutton, on 13 May 2026.
Community work this month has centered on graduation handover and release
preparation and review. The 1.13.0 RC1 vote ran for more than 72 hours and
received three binding +1 votes from PMC members, demonstrating participation
in release oversight.
## Releases:
Apache ResilientDB 1.13.0, the project's first release as a TLP, was published
on 12 October 2026 following the PMC vote. The approved source archive,
signature, and checksum are now available from the Apache download site. The
GitHub release has also been published as the latest stable release.
## Development Activity:
The 1.13.0 release brings together work completed before graduation, including
Raft consensus and recovery, Thunderbolt smart contract concurrency, an
optional DuckDB-backed SQL execution path, composite-key storage primitives,
Ubuntu and ARM64 build fixes, and the ResShare file-sharing toolkit.
Since graduation, repository changes have focused on README and logo updates
and repository cleanup. The immediate focus is updating the website download
links and release documentation to reflect 1.13.0.
## Graduation Handover:
The PMC roster, Chair access, and reporting schedule have been checked.
Incubator metadata and the project status page now record the graduation date.
The project website uses Apache ResilientDB branding, and TLP distribution
directories and the public KEYS file are in place.
The GitHub repository still uses the incubator-resilientdb name; repository
naming and remaining references to incubation are items to follow up during
the handover.
-----------------------------------------
Attachment BY: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment BZ: Report from the Apache Rya Project [Adina Crainiceanu]
-----------------------------------------
Attachment CA: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment CB: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to an ultra-high-performance distributed data integration tool that
supports CDC and batch synchronization of massive data.
## Project Status:
Current project status: Healthy
Issues for the board: There are no Board-level issues at this time.
## Membership Data:
Apache SeaTunnel was founded on 2023-05-16 (3 years ago). There are currently
42 committers and 24 PMC members. The Committer-to-PMC ratio is 7:4.
Community changes, past quarter:
- Chao Wang was added to the PMC on 2026-08-30.
- Zhiwei Niu was added as committer on 2026-08-31.
## Project Activity:
- 3.0.0 was released on 2026-09-29.
## Community Health:
- [email protected] had a 36% increase in traffic in the past quarter
(102 emails compared to 75). The project has a Community Health Score of
9.19 (Healthy).
-----------------------------------------
Attachment CC: Report from the Apache ServiceComb Project [Zhangjian He]
-----------------------------------------
Attachment CD: Report from the Apache Shiro Project [Lenny Primak]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None at this time
## Membership Data:
Apache Shiro was founded 2010-09-21 (16 years ago)
There are currently 16 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Steinar Bang on 2026-01-12.
## Project Activity:
We released Shiro 2.2.1 on 6/17/2026, 3.0.0 on 06/29/2026, 3.0.1 on 08/24/2026
Shiro 2.x line is now EOL
We received 40 security reports and dealt with all of them
We closed 11 issues, fixed over 20 security vuln and published 3 CVEs
Working on Project Glasswing as top concerned in the list of ASF projects
## Community Health:
Mailing list traffic is low.
There has been a further significant increase of security vulnerability reports.
-----------------------------------------
Attachment CE: Report from the Apache SkyWalking Project [Sheng Wu]
## Description:
The mission of Apache SkyWalking is the creation and maintenance of software
related to application performance management and monitoring (APM)
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SkyWalking was founded 2019-04-17 (7 years ago) There are currently 64
committers and 36 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 Youliang Huang on 2026-05-06.
- No new committers. Last addition was Yi Wang on 2026-06-02.
## Project Activity:
We released several versions this quarter.
- ai-sessonizer-0.5.0: 2026-09-24
- banynabd-0.11.1: 2026-09-20
- ai-sessionizer-0.4.0: 2026-09-18
- ai-sessionizer-0.3.0: 2026-09-17
- graalvm-distro-0.4.0: 2026-09-10
- banyandb-helm-0.7.0: 2026-09-01
- helm-5.0.0: 2026-09-01
- swck-0.11.0: 2026-09-01
- 11.0.0: 2026-08-28
- banyandb-0.11.0: 2026-08-28
- eyes-0.9.0: 2026-08-28
- horizon-ui-1.0.0: 2026-08-28
- java-9.7.0: 2026-08-14
- python-1.3.0: 2026-08-14
- go-0.7.0: 2026-08-07
- nodejs-0.9.0: 2026-06-26
- horizon-ui-0.7.0: 2026-06-25
- banyandb-0.10.3: 2026-06-20
A new subproject is established for AI agent observability.
## Community Health:
Community is healthy. We received a lot of positive feedback. The user group
is adopting the new 11.0 with Horizon UI. BanyanDB 0.11 got more attention as
well.
-----------------------------------------
Attachment CF: Report from the Apache Sourcelume Project [Jamie Goodyear]
## Description:
Apache Sourcelume provides a metadata spec, registry, and signing pipeline —
for publishing and independently verifying provenance records of AI training
datasets.
## Project Status:
Current project status: New
Issues for the board: none
## Membership Data:
Apache Sourcelume was founded 2026-08-18
There are currently 8 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
- Apache Sourcelume has selected a logo via community submissions and vote.
Logo has been reviewed by Trademarks and M&P teams.
- Community has held deep technical discussions on it's dev list regarding
Sourcelume Registry, implementing several spikes using different frameworks
for discussion, and has started to implement the Registry.
- Apache Sourcelume members have registered a hackathon session for Community
over Code Glasgow 2026.
https://events.apache.org/events/2026/community-over-code/sourcelume.html
## Community Health:
Our community has just started from our PMC group. Our dev email list is alive
with architecture and technical discussions. We have begun to accept PRs from
the community at large and have seen a steady increase in community engagement
and participation.
-----------------------------------------
Attachment CG: Report from the Apache Steve Project [Greg Stein]
Apache STeVe reported last month. No changes.
-----------------------------------------
Attachment CH: Report from the Apache StreamPark Project [Huajie Wang]
## Description:
Apache StreamPark is a framework and cloud-native platform for developing and
managing streaming applications. Its goal is to make stream processing easier.
## Project Status:
Current project status: Ongoing
Issues for the Board: None
## Membership Data:
Apache StreamPark became a top-level project on 2025-01-23. It currently has 8
committers and 12 PMC members, a committer-to-PMC ratio of 2:3.
Since the last report, no new committers or PMC members have been added. Three
contributors had their first pull requests merged.
## Project Activity:
The community has decided to make 3.0.0 the next major release. Most of the
foundational work and associated pull requests have been completed. The
remaining work includes integration, validation, and release preparation.
The community also plans to refactor authentication and authorization to
address underlying issues associated with multiple reported CVEs. This work
remains in progress and will require review and verification.
No formal release was completed during this reporting period. The latest
release remains Apache StreamPark 2.1.7.
## Community Health:
Development and contributor participation continue. The community has also
reviewed its issue backlog and closed many outdated reports. Completing and
verifying 3.0.0 will require sustained maintainer attention.
-----------------------------------------
Attachment CI: Report from the Apache Struts Project [René Gielen]
## Description:
The Apache Struts MVC framework is a solution stack for creating modern and
elegant action-based Java web applications. It favours convention over
configuration, is extensible using a plugin architecture, and ships with
plugins to support patterns and technologies such as REST, AJAX and JSON.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Struts was founded 2004-03-17 (22 years ago) There are currently 60
committers and 23 PMC members in this project. The Committer-to-PMC ratio is
roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Kusal Kithul-Godage on 2024-02-24.
- No new committers. Last addition was Kusal Kithul-Godage on 2023-08-03.
## Project Activity:
The Struts team made five releases in the reporting period:
- Struts 7.3.0 - Bug Fix, Improvements and Feature Release (2026-08-01) [1]
- Struts 6.11.0 - Bug Fix and Improvements Release (2026-08-01) [1]
- Struts 7.4.0 - Bug Fix, Improvements and Feature Release (2026-10-02) [2]
- Struts 6.12.0 - Bug Fix and Improvements Release (2026-10-02) [2]
- Apache Struts IntelliJ IDEA plugin v261.19027.1 (2026-07-13) [3]
The last Struts releases besides the core framework were
- Struts Annotations 2.0.0 - Enhancements and JDK 17 support (2025-07-03)
- Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06)
We released nine security bulletins in the last quarter, with mostly moderate
to low impact rating. Only one issue, CVE-2026-104713 [10], was rated
“Important”:
- CVE-2026-73635: Unbounded growth of localized-text caches driven by the
request locale (2026-08-14) [4]
- CVE-2026-73634: Unbounded read of a Content Security Policy violation report
(2026-08-14) [5]
- CVE-2026-73633: Unbounded read of a JSON request body (2026-08-14) [6]
- CVE-2026-73632: Shared serialization state in the JSON plugin(2026-08-14)
[7]
- CVE-2026-73631: Shared parsing state in the JSON plugin (2026-08-14) [8]
- CVE-2026-104714: Shared message formatter exposes date and time values
across concurrent requests (2026-10-05) [9]
- CVE-2026-104713: Unbounded request body read in the REST plugin (2026-10-05)
[10]
- CVE-2026-104712: Disproportionate response size when rendering BigDecimal
request parameters (2026-10-05) [11]
- CVE-2026-104711: OGNL injection in the legacy RESTful action mapper
(2026-10-05) [12]
The last quarter was an extraordinarily busy one regarding development and
general involvement. Besides steady regular activity, we saw hardening and
security related issues spiking.
The Project Glasswing Scanning Reports for Apache Struts reached us at
2026-08-17. No critical issues were reported, yet quite a few interesting and
important findings were included. Other findings leading to security bulletins
came in by external reporters. Both the number and quality of external reports
is on the rise.
Thanks to the Apache Security Team as well as the Apache Glasswing Team for
their excellent support.
We have no issues that require board assistance at this time.
## Community Health
### Development activity in the regular reporting period
153 JIRA tickets opened and 136 closed in the past quarter
We had 260 PRs opened and 267 closed in the main project.
### Mailing list activity in the regular reporting period:
- [email protected] had a 55% decrease in traffic in the past quarter (42
emails compared to 93)
- [email protected] had a 453% increase in traffic in the past quarter
(1521 emails compared to 275)
- [email protected] had a 96% increase in traffic in the past
quarter (1342 emails compared to 684)
- [email protected] had a 146% increase in traffic in the past quarter
(37 emails compared to 15)
[1] https://struts.apache.org/announce-2026#a20260801
[2] https://struts.apache.org/announce-2026#a20261002
[3] https://lists.apache.org/thread.html/wwnf059oyo4784f6rbf43boo5ftyg9wo
[4] https://cwiki.apache.org/confluence/display/WW/S2-074
[5] https://cwiki.apache.org/confluence/display/WW/S2-073
[6] https://cwiki.apache.org/confluence/display/WW/S2-072
[7] https://cwiki.apache.org/confluence/display/WW/S2-071
[8] https://cwiki.apache.org/confluence/display/WW/S2-070
[9] https://cwiki.apache.org/confluence/display/WW/S2-078
[10] https://cwiki.apache.org/confluence/display/WW/S2-077
[11] https://cwiki.apache.org/confluence/display/WW/S2-076
[12] https://cwiki.apache.org/confluence/display/WW/S2-075
-----------------------------------------
Attachment CJ: Report from the Apache Tapestry Project [Thiago H. de Paula Figueiredo]
## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework
## Project Status:
Current project status: ongoing.
Issues for the board: none.
## Membership Data:
Apache Tapestry was founded 2006-02-14 (21 years ago)
There are currently 30 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ben Weidig on 2021-12-02.
- No new committers. Last addition was Christian Köberl on 2024-05-02.
## Project Activity:
- We've been very busy setting up Tapestry for Project Glasswing and then
analyzing its results.
- We have a current voting thread to move the project site from the current,
unsupported Confluence-export-based one to a new one based on Antora and
AsciiDoc, something that should dramatically lower the bar for site and
documentation contributions. We thank Volker Lamp for leading this project.
- We've also greatly improved our Jenkins and Gradle setup so it's easier
to have CI over a large range of Java versions instead of just a few
versions set up manually.
- We've also worked on a number of smaller enhancements and bugs.
- The ES 5 support has been stabilized and is ready for a release.
## Community Health:
- [email protected] had a 80% decrease in traffic in the past quarter
(11 emails compared to 53)
- [email protected] had a 90% decrease in traffic in the past quarter
(1 emails compared to 10)
- 7 JIRA tickets opened and 13 closed in the past quarter.
With no releases in the quarter, the mailing lists weren't busy.
-----------------------------------------
Attachment CK: Report from the Apache Tcl Project [Georgios Petasis]
-----------------------------------------
Attachment CL: Report from the Apache Tez Project [László Bodor]
## Description:
Apache Tez is an effort to develop a generic application framework which can
be used to process arbitrarily complex DAGs of data-processing tasks and also
a re-usable set of data-processing primitives which can be used by other
projects.
## Project Status:
Current project status: Ongoing.
Issues for the board: None.
## Membership Data:
Apache Tez was founded 2014-07-16 (12 years ago) There are currently 36
committers and 33 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ayush Saxena on 2024-09-17.
- No new committers. Last addition was Ayush Saxena on 2024-01-09.
## Project Activity:
Patches continue to come in as the project progresses toward the upcoming
1.0.0 release. Security concerns are being actively addressed through ongoing
fixes and improvements.
## Community Health:
A recent committer vote for a committer
did
not pass. I have shared constructive feedback with him, encouraging further
core contributions and deeper involvement in the project before
reconsideration.
-----------------------------------------
Attachment CM: Report from the Apache Thrift Project [Jens Geyer]
## Description:
Apache Thrift is a high performance cross platform RPC and serialization
solution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Thrift was founded 2010-10-20 (16 years ago)
There are currently 44 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Liu Jiayu on 2025-03-16.
- No new committers. Last addition was Volodymyr Panivko on 2026-04-28.
## Project Activity:
We released 0.24.0 in July, the 0.25.0 rc-1 vote is still running at the time of
writing.
## Community Health:
Participation has slightly increased over the last weeks, also new
contributors that started to work at areas that had a lack of maintenace
earlier this year, particularly the Rust bindings.
The mailimg list stats are a bit skewed because we switched certain traffic
from dev over to notifications. This is a one-time effect.
-----------------------------------------
Attachment CN: Report from the Apache Tika Project [Tim Allison]
## Description:
The mission of Tika is the creation and maintenance of software related to
Content Analysis and Detection Toolkit
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Tika was founded 2010-04-21 (16 years ago)
There are currently 31 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-06.
- No new committers. Last addition was Nicholas DiPiazza on 2021-06-03.
## Project Activity:
Released 4.1.0 and a maintenance/dependency upgrade 3.3.3.
In progress to release minors for each by the end of October.
Had a Tika talk at Community Over Code.
## Community Health
Healthy. Uptick in emails and JIRA tickets. Two new
ongoing contributors we’re keeping an eye on to invite
to join.
-----------------------------------------
Attachment CO: Report from the Apache TinkerPop Project [Kelvin Lawrence]
## Description:
Apache TinkerPop is a graph computing framework for both graph databases
(OLTP) and graph analytic systems (OLAP).
## Project Status:
The project is ongoing with high activities this past quarter. There are no
issues requiring board attention.
## Membership Data:
Apache TinkerPop was founded 2016-05-17 (10 years ago)
There are currently 31 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Cole Greer on 2025-06-02.
- No new committers. Last addition was Andrea Child on 2025-08-11.
## Project Activity:
The project maintained strong development momentum this quarter, with the
release of TinkerPop 4.0.0-beta.3 in July [1], followed by maintenance
releases of TinkerPop 3.7.7 and 3.8.2 in September [2] [3].
Security has been a core focus of these releases. As AI lowers the barrier for
threat actors to discover and exploit software vulnerabilities, the community
continues to prioritize a stronger security posture across both the maintenance
lines and the 4.0 development effort.
TinkerPop 4.0.0-beta.3 advances the next major version with a redesigned
match() step based on TinkerGQL, an integration of the ISO standard query
language for graphs. It also introduces optional multi-labelled vertices and
improved handling for dynamic traversal arguments in steps such as has(),
resolving a long-standing pain point for users.
Alongside these features, the release enables Java 21 and 25 support and
continues to round out the 4.0 feature set. The community continues active
development on maintenance updates for the 3.7.x/3.8.x lines and on stabilizing
TinkerPop 4.0 toward a full release.
### Releases:
4.0.0-beta.3 was released on 2026-07-20.
3.7.7 was released on 2026-09-01.
3.8.2 was released on 2026-09-01.
## Community Health:
The TinkerPop community maintains strong engagement with consistent
contributions from core committers and active participation from users on the
dev list and in our Discord server.
This quarter featured two live ContributorCast sessions on Twitch [4]
reviewing the releases. Recordings will be available on our YouTube channel
[5]:
* ContributorCast: Apache TinkerPop 4.0.0-beta.3 Post-Release Review [6]
Presenters: Stephen Mallette, Zhouchunyang (Yang) Xia, Cole Greer
* ContributorCast: Post-Release Review of 3.7.7, 3.8.2 and 4.0.0-beta.3,
Part 2 [7]
Presenters: Zhouchunyang (Yang) Xia, Ken Hu, Guian Gumpac, Cole Greer
## Report Links
[1]: https://lists.apache.org/thread/s05srhz2084ckp8v30l4qn5rkkozog79
[2]: https://lists.apache.org/thread/c5f4h4ldbzhh22ohzh12y81vozvqw55n
[3]: https://lists.apache.org/thread/245p1253srn1wyyjtrotdph77khqfybz
[4]: https://www.twitch.tv/apachetinkerpop
[5]: https://www.youtube.com/@apachetinkerpop
[6]: https://youtu.be/sts9hgWFMWY?si=LeDzA3gNQvnOj4LC
[7]: https://youtu.be/5UylghjAj_w?si=matuO2tdCws43z6Z
-----------------------------------------
Attachment CP: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
The mission of Traffic Server is the creation and maintenance of a
high-performance, scalable HTTP/1.1 and HTTP/2 caching proxy server that
powers major CDNs worldwide.
## Project Status:
Current project status: Ongoing
Issues for the board: none.
## Membership Data:
Apache Traffic Server was founded 2010-04-20 (16 years ago)
There are currently 72 committers and 58 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Mo Chen on 2024-04-15.
- No new committers. Last addition was Jake Champion on 2026-04-06.
## Project Activity:
We released 10.2.0 on August 17. It is our first feature release in over a
year and was in vote when we filed the last report. There have been no
other releases since.
Since then, most of our work has gone into reliability and code quality:
- Traffic Server now reuses its HTTP/2 connections to the servers behind it
more reliably, and no longer rejects some valid responses from them.
- We added an experimental plugin that protects against abusive clients.
It limits how fast a single address can send requests or open
connections, and it can temporarily block clients that go over those
limits.
- We started running more automated tools that find bugs in the source
code, and fixed a large batch of the problems they reported.
- We continued updating Traffic Server to work with the newest versions of
the encryption libraries it depends on.
The next major release, 11.0.0, does not have a target date yet. Deciding
what goes into it and when it ships is the main topic of our Fall Summit
in December.
## Community Health:
Participation is growing. Comparing the 8 weeks since the last report with
the 8 weeks before it, the number of contributors went up from 22 to 25 and
the number of changes merged went up from 166 to 181.
We have not added a PMC member since April 2024 or a committer since April
2026. With more regular contributors than a year ago, we want to bring more
of them on as committers.
We will hold a virtual Fall Summit on December 2-3, 2026, over two
half-days. Topics include what goes into 11.0.0 and when it ships, how
often we release, and using AI tools in development and code review. We
will also plan the move of our automated testing to AWS, because its
current hosting arrangement is ending.
We continue to hold weekly bug and issue scrubs every Monday.
New issues doubled (29 -> 58) while closed issues fell (178 -> 48). The
earlier period was the end of a deliberate push to close our oldest issues,
so fewer closures was expected. There are 231 open issues and 69 open pull
requests, up from 217 and 67 at the last report.
-----------------------------------------
Attachment CQ: Report from the Apache Training Project [Justin Mclean]
## Description:
The mission of Apache Training is the creation and maintenance of software
related to training materials for Apache projects and the Apache Software
Foundation
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Training was founded 2025-08-20 (14 months ago)
There are currently 18 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- No new PMC members. Last addition was Andrew Wetmore on 2025-08-20.
- No new committers were added.
## Project Activity:
There has been no traffic on the dev@ mailing list this reporting period. The
only commit activity was automated dependency updates. No new training content
was added.
## Community Health:
The community remains small and quiet. There was no mailing list traffic and
no new contributors during this reporting period. The project tends to work on
materials as needed, and quiet periods like this one are typical.
-----------------------------------------
Attachment CR: 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: Current project status: Active (3,230 commits)
- new pull requests through early October 2026. The last release is 1.1.1
(Feb, 2026) Issues for the board: none
## Membership Data:
Apache Wayang was founded 2025-11-19 (a year 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. Last addition was Alexander Alten on 2025-11-19.
- No new committers were added.
## Project Activity:
The GitHub repository (apache/wayang) shows 3,230 commits, 274 stars, 141
forks and 16 watchers. It has 26 open pull requests, 524 closed pull requests
and about 105 open issues. Commits and mailing list traffic for the quarter:
(as at 2026-10-09) [email protected] had a 86% decrease in traffic in the
past quarter (8 emails compared to 55, however most of the emails in the last
quarter where due to the GSoC.)
Community over code talk and hackathon conducted in Glasgow this week
by the PMC chair.
Work in flight, mostly from contributors outside the PMC:
- New platforms and sources: DuckDB platform support with a Parquet source and
cost model (#794), and SQL support for Parquet sources (#793).
- JDBC and SQL: a JDBC driver and server (#792, #719), TableSource column
projection (#721), and type validation between SQL and Java operators
(#803).
- APIs: a draft DataFrame API (#716).
- Security hardening: an ObjectInputFilter allowlist for legacy
deserialization (#838) and escaping of table identifiers in JDBC sinks
(#839).
- Correctness fixes: Record.compareTo() ClassCastException (#814) and
empty-list handling in JavaReduceByOperator (#837).
- Dependencies: Dependabot updates to Jackson (#829, #841) and Spark 3.5.8
(#840).
- Onboarding: a Docker development environment for the Glasgow hackathon (#801).
## Community Health:
Contributor interest is growing: at least nine accounts have open pull
requests, most of them new to the project, and PR numbers reached #841 on
2026-10-11. The constraint is review capacity. No one has been added as a
committer this quarter. Of the 14 most recent open issues, 9 are automated
todo issues created by GitHub Actions, so the open issue count overstates
user-reported problems.
-----------------------------------------
Attachment CS: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment CT: Report from the Apache Zeppelin Project [Jongyoul Lee]
## Description:
Apache Zeppelin is a web-based notebook that enables interactive data
analytics through multiple interpreters.
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No specific Board action is requested at this time.
Security follow-up has taken longer than it should. We plan to work with the
expanded PMC to prioritize the outstanding security work over the coming
quarter and improve the timeliness of follow-up with reporters.
Security reports are handled through [email protected] in
coordination with [email protected], following the ASF security process.
This is what the July report referred to as the private security process.
## Membership Data:
Apache Zeppelin was founded on 2016-05-18 (10 years ago). There are currently
28 committers and 14 PMC members.
The July report did not reflect the following membership additions:
- ChanHo Lee joined the PMC on 2026-07-09, the latest PMC addition.
- Yongjae Lee joined as a committer on 2026-07-12, the latest committer
addition.
## Project Activity:
No new release has been published since the July report. The most recent
release is Apache Zeppelin 0.12.1, released on 2026-06-12.
Frontend quality was a major focus. The community expanded unit and end-to-end
tests for notebook editing, collaboration, paragraph behavior, and
visualization rendering. It also corrected tests that could pass without
checking the intended behavior and improved CI reliability. User-facing fixes
covered editor behavior, revision comparison, exports, themes, and
accessibility.
UI modernization continued through incremental React integration within the
Angular UI. Shared Notebook Core work added transport contracts, read state,
and adapters, providing a foundation for the transition while checking
compatibility with existing notebook behavior.
Beyond the frontend, contributors improved notebook persistence and concurrent
operations, interpreter lifecycle and resource management, and WebSocket
connection handling. JDK 17 support was added. Documentation, build tooling,
and dependency maintenance also received attention.
AI assistant work has progressed from discussion and a proof of concept to
server-side notebook chat support. Frontend integration remains in progress.
These changes have not yet been included in a new release.
## Community Health:
OSSCA has brought sustained contribution activity across UI quality, tests,
documentation, and runtime maintenance. As of 2026-10-15, the contribution
dashboard records 276 pull requests, of which 244 have been merged, across
apache/zeppelin and apache/zeppelin-site. Of these, mentees authored 177 pull
requests, with 156 merged. These are cumulative tracker figures since
2026-04-07, rather than counts limited to this quarter.
The dashboard tracks 28 mentees and six mentors; 24 mentees and all six
mentors have authored pull requests in the tracked period. The volume of
contributions is encouraging, and the most visible outcome is stronger
frontend testing and more reliable notebook behavior.
The contribution history also shows work beyond frontend fixes, including
notebook storage, interpreter reliability, and documentation. Our next
community goal is to turn this activity into continued contribution and review
participation after the program, while giving the outstanding security
follow-up focused PMC attention in the coming quarter.
------------------------------------------------------
End of minutes for the October 21, 2026 board meeting.