[raw] the published text, which is the record. [2026] [main index]
The Apache Software Foundation
Board of Directors Meeting Minutes
July 15, 2026
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:04 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2026-07-15T21: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:
Shane Curcuru
Christofer Dutz
Emmanuel Lécharny
Justin Mclean - joined :05
Jean-Baptiste Onofré
Christopher Schultz
Greg Stein
Sander Striker
Directors Absent:
Zili Chen
Executive Officers Present:
Craig McClanahan
Matt Sicker
Craig L Russell
Daniel Ruggeri
Ruth Suehle
Executive Officers Absent:
none
Guests:
Daniel Gruno
Sally Khudairi
Paul King
Brian Proffitt
Jamie Goodyear
Alin Jerpelea
Andrew Wetmore
David Fisher
Andrew Musselman
Thomas Neidhart
Jarek Potiuk
Daniel Sahlberg
Daniel Ruggeri
Melissa Logan
Kanchana Pradeepika Welagedara
Danny Angus
Julien Le Dem - joined :07
Christopher Schultz - joined :13
Guilherme Henrique Caponetto
Henri Yandell - joined :17
Drew Foulks
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of June 17, 2026
See: board_minutes_2026_06_17.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
I attended UN Open Source week in New York last month - an event that has been
growing year on year. It is not surprising that a good portion of this year's
agenda had an AI perspective.
In preparation for this meeting I have spent more time on history than usual,
as a result of a proposed new Executive Committee. The last time we did that
was almost two decades ago.
Since last meeting I have also been able to make some small contributions to
the Board Agenda Tool; implementing features that will make it easier for a
next chair. Automated agenda creation and scheduled reminders are now part of
the system. I'd like to thank the Tooling team for their engagement and
responsiveness.
B. President [Ruth Suehle]
UN Open Source Week was again a resounding success, and it was great to see a
strong presence from ASF members as well.
Among the news of that week was LF's launch of Akrites, with only about 24
hours' notice to us and less to some other parts of the open source ecosystem.
The LF assures me that they intend to invite collaboration from across open
source projects, including us, on how Akrites actually works. Eclipse has
posted a response [1] as has Sonatype [2].
[1] https://blogs.eclipse.org/post/catharina-maracke/we-all-depend-open-source-one-country-should-not-hold-keys-defending-it
[2] https://central.sonatype.org/policies/care-policy/
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig McClanahan]
Normal operations continue, including progress on our audit. I have provided
KWC with read-only access to our Quickbooks Online account, so they can look
up answers to many of their questions themselves.
When considering the RAI proposal, it would be helpful for the Board to
provide some feedback on how we'd like the accounting to work for it.
D. Secretary [Matt Sicker]
In June 2026, the secretary received 36 ICLAs.
E. Executive Vice President [Daniel Ruggeri]
Nothing of interest to report this month - it's remained quiet!
F. Vice Chair [Justin Mclean]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Shane Curcuru]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Christofer Dutz]
See Attachment 13
C. Apache Security Team Project [Mark J. Cox / Emmanuel Lécharny]
See Attachment 14
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# AGE [jmclean]
# CarbonData [jmclean]
# Flagon [gstein]
# Fory [jmclean]
# Magpie [jmclean]
# Rya [elecharny]
A. Apache Accumulo Project [Ed Coleman / Sander Striker]
See Attachment A
B. Apache ActiveMQ Project [Christopher L. Shannon / Jean-Baptiste Onofré]
See Attachment B
C. Apache AGE Project [Jeff Jirsa / Greg Stein]
See Attachment C
D. Apache Airavata Project [Suresh Marru / Justin Mclean]
No report was submitted.
E. Apache Airflow Project [Bolke de Bruin / Christopher Schultz]
No report was submitted.
F. Apache Answer Project [Ning Qi / Zili Chen]
See Attachment F
G. Apache APISIX Project [Ming Wen / Christopher Schultz]
See Attachment G
H. Apache Aries Project [Dominik Przybysz / Zili Chen]
See Attachment H
I. Apache Arrow Project [Antoine Pitrou / Jean-Baptiste Onofré]
See Attachment I
J. Apache AsterixDB Project [Ian Maxon / Christofer Dutz]
See Attachment J
K. Apache Attic Project [Hervé Boutemy / Shane Curcuru]
No report was submitted.
L. Apache Avro Project [Ryan Skraba / Justin Mclean]
No report was submitted.
M. Apache bRPC Project [James Ge / Greg Stein]
See Attachment M
N. Apache Calcite Project [Mihai Budiu / Emmanuel Lécharny]
See Attachment N
O. Apache CarbonData Project [Liang Chen / Sander Striker]
See Attachment O
P. Apache Causeway Project [Jörg Rade / Shane Curcuru]
See Attachment P
Q. Apache Celix Project [Pepijn Noltes / Zili Chen]
No report was submitted.
R. Apache CouchDB Project [Jan Lehnardt / Justin Mclean]
See Attachment R
S. Apache Curator Project [Enrico Olivelli / Sander Striker]
No report was submitted.
T. Apache CXF Project [Andriy Redko / Greg Stein]
See Attachment T
U. Apache DataFu Project [Eyal Allweil / Jean-Baptiste Onofré]
See Attachment U
V. Apache DB Project [Jeffery Painter / Christopher Schultz]
See Attachment V
W. Apache Directory Project [Shawn McKinney / Christofer Dutz]
See Attachment W
X. Apache DolphinScheduler Project [Lidong Dai / Emmanuel Lécharny]
See Attachment X
Y. Apache Druid Project [Abhishek Agarwal / Jean-Baptiste Onofré]
See Attachment Y
Z. Apache Dubbo Project [Jun Liu / Shane Curcuru]
See Attachment Z
AA. Apache Fineract Project [James Dailey / Christofer Dutz]
See Attachment AA
AB. Apache Flagon Project [Joshua Poore / Greg Stein]
See Attachment AB
@Greg Stein: follow up about chair responsibilities
AC. Apache Flex Project [Harbs / Justin Mclean]
No report was submitted.
AD. Apache Fory Project [Chaokun Yang / Sander Striker]
See Attachment AD
AE. Apache Geronimo Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
AF. Apache Gluten Project [Weiting Chen / Emmanuel Lécharny]
See Attachment AF
AG. Apache Guacamole Project [Mike Jumper / Zili Chen]
See Attachment AG
AH. Apache Hadoop Project [Xiaoqiao He / Christopher Schultz]
See Attachment AH
AI. Apache HBase Project [Duo Zhang / Greg Stein]
See Attachment AI
AJ. Apache HertzBeat Project [Chao Gong / Justin Mclean]
See Attachment AJ
AK. Apache Hive Project [Naveen Gangam / Emmanuel Lécharny]
See Attachment AK
AL. Apache HugeGraph Project [Jermy Li / Christofer Dutz]
See Attachment AL
AM. Apache Incubator Project [Justin Mclean / Justin Mclean]
See Attachment AM
AN. Apache InLong Project [Charles Zhang / Sander Striker]
See Attachment AN
AO. Apache James Project [Benoit Tellier / Shane Curcuru]
See Attachment AO
AP. Apache Jena Project [Andy Seaborne / Christopher Schultz]
See Attachment AP
AQ. Apache JMeter Project [Bruno (Milamber) Demion / Jean-Baptiste Onofré]
See Attachment AQ
AR. Apache Johnzon Project [Jean-Louis Monteiro / Zili Chen]
No report was submitted.
AS. Apache JSPWiki Project [Alex O'Ree / Shane Curcuru]
See Attachment AS
AT. Apache Kudu Project [Andrew Wong / Christofer Dutz]
See Attachment AT
AU. Apache Livy Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré]
See Attachment AU
AV. Apache Lucene.Net Project [Shad Storhaug / Sander Striker]
No report was submitted.
AW. Apache MADlib Project [Ed Espino / Zili Chen]
No report was submitted.
AX. Apache Magpie Project [Jarek Potiuk / Christopher Schultz]
See Attachment AX
@Justin Mclean: follow up on clarification on chair/project authorizations
AY. Apache Mahout Project [Shannon Quinn / Justin Mclean]
See Attachment AY
AZ. Apache Maven Project [Hervé Boutemy / Jean-Baptiste Onofré]
No report was submitted.
BA. Apache MINA Project [Thomas Wolf / Greg Stein]
See Attachment BA
BB. Apache MyFaces Project [Bernd Bohmann / Emmanuel Lécharny]
See Attachment BB
BC. Apache Mynewt Project [Szymon Janc / Zili Chen]
No report was submitted.
BD. Apache NiFi Project [David Handermann / Greg Stein]
See Attachment BD
BE. Apache Nutch Project [Sebastian Nagel / Justin Mclean]
See Attachment BE
BF. Apache NuttX Project [Alin Jerpelea / Emmanuel Lécharny]
See Attachment BF
BG. Apache OpenJPA Project [Mark Struberg / Christopher Schultz]
See Attachment BG
BH. Apache OpenMeetings Project [Maxim Solodovnik / Zili Chen]
See Attachment BH
BI. Apache OpenOffice Project [Keith McKenna / Jean-Baptiste Onofré]
See Attachment BI
BJ. Apache OpenWebBeans Project [Mark Struberg / Christofer Dutz]
No report was submitted.
BK. Apache ORC Project [William Hyun / Shane Curcuru]
No report was submitted.
BL. Apache Parquet Project [Julien Le Dem / Sander Striker]
See Attachment BL
BM. Apache PDFBox Project [Andreas Lehmkühler / Shane Curcuru]
No report was submitted.
BN. Apache Pig Project [Koji Noguchi / Christofer Dutz]
See Attachment BN
BO. Apache PLC4X Project [César García / Jean-Baptiste Onofré]
See Attachment BO
BP. Apache Ranger Project [Selvamohan Neethiraj / Greg Stein]
No report was submitted.
BQ. Apache Ratis Project [Tsz-wo Sze / Zili Chen]
See Attachment BQ
BR. Apache Rya Project [Adina Crainiceanu / Sander Striker]
See Attachment BR
@Sander Striker: pursue a roll call
BS. Apache Samza Project [Jagadish Venkatraman / Justin Mclean]
No report was submitted.
BT. Apache SeaTunnel Project [Jun Gao / Christopher Schultz]
See Attachment BT
BU. Apache SINGA Project [Wang Wei / Emmanuel Lécharny]
See Attachment BU
BV. Apache SkyWalking Project [Sheng Wu / Zili Chen]
See Attachment BV
BW. Apache Steve Project [Greg Stein / Greg Stein]
No report was submitted.
BX. Apache Struts Project [René Gielen / Jean-Baptiste Onofré]
See Attachment BX
BY. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Emmanuel Lécharny]
See Attachment BY
BZ. Apache Tcl Project [Georgios Petasis / Justin Mclean]
No report was submitted.
CA. Apache Tez Project [László Bodor / Greg Stein]
See Attachment CA
CB. Apache Thrift Project [Jens Geyer / Christofer Dutz]
See Attachment CB
CC. Apache Tika Project [Tim Allison / Sander Striker]
See Attachment CC
CD. Apache TinkerPop Project [Kelvin Lawrence / Christopher Schultz]
See Attachment CD
CE. Apache Traffic Server Project [Bryan Call / Shane Curcuru]
No report was submitted.
CF. Apache Training Project [Justin Mclean / Justin Mclean]
See Attachment CF
CG. Apache Wayang Project [Zoi Kaoudi / Christofer Dutz]
No report was submitted.
CH. Apache Web Services Project [Daniel Kulp / Justin Mclean]
See Attachment CH
CI. Apache Yetus Project [Allen Wittenauer / Jean-Baptiste Onofré]
See Attachment CI
CJ. Apache Zeppelin Project [Jongyoul Lee / Zili Chen]
See Attachment CJ
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Create the Responsible AI Executive Committee
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to appoint an officer and create an
executive committee responsible for establishing, promoting,
and coordinating governance policies, models, agents, and best
practices for AI use within the ASF.
NOW, THEREFORE, BE IT RESOLVED that the office of "Vice
President, Responsible AI" be and hereby is created, the person
holding such office to serve at the direction of the Board of
Directors, and to have responsibility for establishing,
promoting, and coordinating governance policies, models,
agents, and best practices for AI use within the ASF.
BE IT FURTHER RESOLVED, that Jeff Genender be and hereby is
appointed to the office of Vice President, Responsible AI, to
serve in accordance with and subject to the direction of the
Board of Directors until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
BE IT FURTHER RESOLVED that the "Responsible AI Committee" be
and hereby is created, the members of which to serve at the
direction of the Board of Directors, and to have responsibility
to advise the Vice President, Responsible AI on establishing,
promoting, and coordinating governance policies, models,
agents, and best practices for AI use within the ASF.
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Responsible AI Committee:
* Danny Angus <danny@apache.org>
* Zili Chen <tison@apache.org>
* Bertrand Delacretaz <bdelacretaz@apache.org>
* Bruno Demion <milamber@apache.org>
* C David "Dave" Fisher <wave@apache.org>
* Jeff Genender <jgenender@apache.org>
* Jamie Goodyear <jgoodyear@apache.org>
* Qiang Guo <kirs@apache.org>
* Jim Jagielski <jim@apache.org>
* Sally Khudairi <sk@apache.org>
* Chris Lambertus <cml@apache.org>
* Justin Mclean <jmclean@apache.org>
* Alexandru-Robert Munteanu <rombert@apache.org>
* Andrew Musselman <akm@apache.org>
* Achim Nierbeck <anierbeck@apache.org>
* Craig L Russell <clr@apache.org>
* Greg Stein <gstein@apache.org>
* Kanchana Welagedara <kanchana@apache.org>
* Henri Yandell <bayard@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
BE IT FURTHER RESOLVED, that the Responsible AI Committee shall
obtain prior approval from the Board of Directors for any
budget allocations, and shall thereafter be free to expend such
funds in accordance with the approved budget.
Special Order 7A, Create the Responsible AI Executive Committee,
was not approved by roll call vote, with four yea votes
(Emmanuel Lecharny, Jean-Baptiste Onofré, Greg Stein, Sander Striker),
three nay votes (Shane Curcuru, Christofer Dutz, Justin Mclean), and
one abstention (Christopher Schultz). Bylaws 5.9 requires a
resolution establishing an Executive Committee to be adopted by
a majority of the full Board of Directors; four of nine is not
such a majority.
B. Change the Apache PLC4X Project Chair
WHEREAS, the Board of Directors heretofore appointed César García
(cgarcia) to the office of Vice President, Apache PLC4X, and
WHEREAS, the Board of Directors is in receipt of the resignation of César
García
from the office of Vice President, Apache PLC4X, and
WHEREAS, the Project Management Committee of the Apache PLC4X project
has chosen by vote to recommend Lukas Ott (otluk) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that César García is
relieved and discharged from the duties and responsibilities of the office of
Vice President, Apache PLC4X, and
BE IT FURTHER RESOLVED, that Lukas Ott be and hereby is
appointed to the office of Vice President, Apache PLC4X, to serve in
accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7B, Change the Apache PLC4X Project Chair, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Libcloud Project Chair
WHEREAS, the Board of Directors heretofore appointed Tomaž Muraus
(tomaz) to the office of Vice President, Apache Libcloud, and
WHEREAS, the Board of Directors is in receipt of the resignation of Tomaž
Muraus
from the office of Vice President, Apache Libcloud, and
WHEREAS, the Project Management Committee of the Apache Libcloud project
has chosen by vote to recommend Miguel Caballer (micafer) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Tomaž Muraus is
relieved and discharged from the duties and responsibilities of the office of
Vice President, Apache Libcloud, and
BE IT FURTHER RESOLVED, that Miguel Caballer be and hereby is
appointed to the office of Vice President, Apache Libcloud, to serve in
accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7C, Change the Apache Libcloud Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Community Development Project Chair
WHEREAS, the Board of Directors heretofore appointed Swapnil Mane
(swapnilmmane) to the office of Vice President, Apache Community Development,
and
WHEREAS, the Board of Directors is in receipt of the resignation of Swapnil
Mane from the office of Vice President, Apache Community Development, and
WHEREAS, the Project Management Committee of the Apache Community Development
project has chosen by vote to recommend Rich Bowen (rbowen) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Swapnil Mane is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Community Development, and
BE IT FURTHER RESOLVED, that Rich Bowen be and hereby is appointed to the
office of Vice President, Apache Community Development, 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 7D, Change the Apache Community Development Project
Chair, was approved by Unanimous Vote of the directors present.
E. Establish the Apache Fluss Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a streaming storage built for real-time analytics which can
serve as the real-time data layer for Lakehouse architectures.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Fluss Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Fluss Project be and hereby is responsible for
the creation and maintenance of software related to a streaming storage
built for real-time analytics which can serve as the real-time data
layer for Lakehouse architectures; and be it further
RESOLVED, that the office of "Vice President, Apache Fluss" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Fluss
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Fluss Project;
and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Fluss Project:
* Anton Borisov <aborisov@apache.org>
* Becket Qin <jqin@apache.org>
* Giannis Polyzos <ipolyzos@apache.org>
* Jark Wu <jark@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
* Jingsong Lee <lzljs3620320@apache.org>
* Keith Lee <leekei@apache.org>
* Mehul Batra <mehulbatra@apache.org>
* Michael Koepf <michaelkoepf@apache.org>
* Nicholas Jiang <nicholasjiang@apache.org>
* Yu Li <liyu@apache.org>
* Yunhong Zheng <yunhong@apache.org>
* Yuxia Luo <yuxia@apache.org>
* Zili Chen <tison@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jark Wu be appointed to the
office of Vice President, Apache Fluss, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it further
RESOLVED, that the Apache Fluss Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Fluss podling; and
be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Fluss podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7E, Establish the Apache Fluss Project, was
approved by Unanimous Vote of the directors present.
F. Change the Apache OpenOffice Project Chair
WHEREAS, the Board of Directors heretofore appointed Keith McKenna
(knmc) to the office of Vice President, Apache OpenOffice, and
WHEREAS, the Board of Directors is in receipt of the resignation of Keith
McKenna from the office of Vice President, Apache OpenOffice, and
WHEREAS, the Project Management Committee of the Apache OpenOffice project
has chosen by consensus to recommend David Fisher (wave) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Keith McKenna is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache OpenOffice, and
BE IT FURTHER RESOLVED, that David Fisher be and hereby is appointed to the
office of Vice President, Apache OpenOffice, 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 7F, Change the Apache OpenOffice Project Chair, was
approved by Unanimous Vote of the directors present.
G. Appoint Vice President, Legal Affairs
WHEREAS, the Board of Directors heretofore appointed Roman Shaposhnik
(rvs) to the office of Vice President, Legal Affairs; and
WHEREAS, the Board of Directors is in receipt of the resignation of
Roman Shaposhnik from the office of Vice President, Legal Affairs; and
WHEREAS, Justin Mclean has been nominated as a successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Roman Shaposhnik is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Legal Affairs, and
BE IT FURTHER RESOLVED, that Justin Mclean (jmclean) be and hereby is
appointed to the office of Vice President, Legal Affairs, 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 7G, Appoint Vice President, Legal Affairs, was
approved by Unanimous Vote of the directors present.
H. Change the Apache Accumulo Project Chair
WHEREAS, the Board of Directors heretofore appointed Ed Coleman
(edcoleman) to the office of Vice President, Apache Accumulo, and
WHEREAS, the Project Management Committee of the Apache Accumulo project
has chosen by vote to recommend Marc Parisi (phrocker) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Ed Coleman is
relieved and discharged from the duties and responsibilities of the office of
Vice President, Apache Accumulo, and
BE IT FURTHER RESOLVED, that Marc Parisi be and hereby is
appointed to the office of Vice President, Apache Accumulo, 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 7H, Change the Apache Accumulo Project Chair, was
approved by Unanimous Vote of the directors present.
I. Establish the Apache Pony Mail Project
WHEREAS, the Board of Directors deems it to be in the best interests of the
Foundation and consistent with the Foundation's purpose to establish a Project
Management Committee charged with the creation and maintenance of open-source
software, for distribution at no charge to the public, related to
mail archiving, archive viewing, and mailing list interaction services.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
be known as the "Apache Pony Mail Project", be and hereby is established
pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Pony Mail be and hereby is responsible for the
creation and maintenance of software related to mail archiving, archive
viewing, and mailing list interaction services; and be it
further
RESOLVED, that the office of "Vice President, Apache Pony Mail" be and
hereby is created, the person holding such office to serve at the direction of
the Board of Directors as the chair of the Apache Pony Mail Project, and
to have primary responsibility for management of the projects within the scope
of responsibility of the Apache Pony Mail Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Pony Mail
Project:
* Rich Bowen <rbowen@apache.org>
* Daniel Gruno <humbedooh@apache.org>
* David Fisher <wave@apache.org>
* Jim Jagielski <jim@apache.org>
* Sean Palmer <sbp@apache.org>
* Ulises <ucb@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Rich Bowen be
appointed to the office of Vice President, Apache Pony Mail, to serve in
accordance with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
RESOLVED, that the Apache Pony Mail Project be and hereby is
tasked with the migration and rationalization of the Apache
Incubator Pony Mail podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Pony Mail podling encumbered upon the Apache
Incubator PMC are hereafter discharged.
Special Order 7I, Establish the Apache Pony Mail Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Greg Stein: talk to Pinot PMC about communication channels
[ Pinot 2025-11-19 ]
Status:
* Greg Stein: follow up with TsFile PMC about publishing to PyPI
[ TsFile 2025-11-19 ]
Status:
* Greg Stein: follow up with board about PyPI policy
[ TsFile 2025-11-19 ]
Status:
* Shane Curcuru: follow up about licensing
[ SIS 2026-02-18 ]
Status: In progress: researching issues and contacts.
* 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
* 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.
* Shane Curcuru: roll call for BVAL
[ BVal 2026-05-20 ]
Status:
* Justin Mclean: suggest chair change
[ Hop 2026-05-20 ]
Status: Sent an email suggesting a chair change.
* Christopher Schultz: suggest ways to improve the board report
[ Spark 2026-05-20 ]
Status: https://lists.apache.org/thread/cztsg4vmzosyzzq5zpj4ptry10gcgwcg
* Shane Curcuru: message all PMCs to improve board reports and discuss "Emeritus" concept for PMCs.
[ Superset 2026-05-20 ]
Status:
* Christopher Schultz: discuss failed roll call and future direction
[ Kylin 2026-05-20 ]
Status: https://lists.apache.org/thread/fzy0hjl46fmy2w8c6woljjq0co5zff4j
* Justin Mclean: follow up with DevLake about incubator tags
[ DevLake 2026-06-17 ]
Status: Completed. Project corrected this
* Sander Striker: follow up about release candidate location
[ Gravitino 2026-06-17 ]
Status:
* Christopher Schultz: reach out about communication issues
[ IoTDB 2026-06-17 ]
Status: Will reach-out to IOTDB in mid-July.
* Christopher Schultz: follow up about AI code usage
[ OpenDAL 2026-06-17 ]
Status:
* Jean-Baptiste Onofré: follow up about Xerces-C EOL
[ Xerces 2026-06-17 ]
Status:
10. Unfinished Business
11. New Business
Greg Stein proposed a restructuring of the Apache Geronimo PMC.
JB Onofré proposed the Geronimo PMC should recommend where its components
should be maintained.
12. Announcements
13. Adjournment
Adjourned at 22:21 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period June 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:
- A query regarding a potential external product name based on
CLOUDBERRY
- Provided advice to AIRFLOW regarding how to reference trademarks when
reaching out regarding potential infringements
- Provided advice to OPENOFFICE regarding a request to use the mark in a
film
- Provided advice regarding a potential external product providing
extensions for ACTIVEMQ
- Provided advice to SIS regarding a new logo
* REGISTRATIONS
Worked with counsel to renew our PDFBOX registration in the US.
Worked with counsel to renew our FLINK registration in the US.
Worked with counsel to renew our ACCUMULO registration in the US.
The registration of the leaf logo in the US has completed.
The CLOUDSTACK registration in the EU has been provisionally refused.
Worked with counsel to transfer the SEATA mark.
* INFRINGEMENTS
No progress regarding a potential infringement of FOP.
No further progress regarding the downstream vendor with multiple
infringements of ASF marks.
There remains one issue with IOTDB to be solved.
The CLOUDSTACK PMC has reached out to several potentially infringing sites.
The SPARK PMC is making progress in addressing a range of product naming
issues with multiple 3rd parties.
Some progress regarding a site with a possible infringement of APISIX.
No progress regarding a website with potential infringements of KIE.
Working with counsel to oppose a conflicting registration of FLINK in the EU.
I've asked for an update from the XMLGRAPHICS PMC regarding progress of the
complaint with GitHub regarding a potential third-party infringement of FOP.
Still no progress from the GLUTEN PMC to address a range of product naming
issues with multiple 3rd parties.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we have not onboarded any new Sponsors during this time period.
b —Renewals: we are pursuing renewals with one Platinum, two Gold, one Silver,
and two Bronze Sponsors.
c —Payments: 1 —New: we received no new Sponsorship payments. 2 —Received: we
received one Platinum Sponsorship renewal payment as well as one new Targeted
Platinum payment to back the Tooling Initiative. 3 —Incoming: we await
renewal payments from three Platinum (one of which is a charitable
contribution), one Gold Sponsor (in extended arrears), and two Silver
Sponsors. In addition, we await sponsorship payments from one Bronze Targeted
Sponsor and three event sponsors.
2) Targeted Sponsors: we have clarified usage options with a beneficiary PMC
on ways they can apply Targeted Sponsorship funds received; we have also
finalized a new Bronze donation to benefit a specific PMC.
3) Sponsor Relations: we are working with a new Targeted Sponsor regarding
publicity opportunities. We held our Q2 Gold + Platinum Sponsor call in June;
the call focused on Sponsor promotional benefits, which was co-presented with
VP Marketing & Publicity.
4) Event Sponsorship: we continue to support sponsorships for 2026 Community
Over Code Europe and co-located events. Organizations wishing to sponsor the
ASF Travel Assistance program are able to do so year-round: those supporting
3+ attendees receive year-long recognition as an ASF Targeted Sponsor.
5) Individual Donations and Corporate Giving: we received $2,800 in individual
online donations via https://donate.apache.org/ . We have not received any
corporate contributions (above $500) during this timeframe.
6) Administrivia: we are standing by to update the ASF's profile on nonprofit
fundraising platforms (e.g., Candid/GuideStar, Charity Navigator, Foundation
Search...) once the completed audit report is available from the Treasury. Our
standing efforts with Accounting, Infrastructure, and Marketing & Publicity
teams continue, augmented by activities with the ASF's Tooling and Responsible
AI Initiatives.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Published blogs:
* Announcing New Top-Level Project, Apache Livy
* GSoC Mentor Summit by Priya Sharma
* Announcing New Top-Level Project, Apache Magpie
* Received final input on all but one section for the Annual Report. Began
design.
* Continued conversation with Financial Times reporter Jamie John on his story
about AI slop. He still plans to write. We sent him information on Apache
Magpie.
* Produced and issued June issue of Plus One newsletter
* Subscriber list now totals 4,435 (455 new subscribers in June)
* Total sent: 3,600 | Unique opens: 993 | Open rate: 27%
Digital
* Community Over Code advertising on LinkedIn from 5/1 to 6/1 including TAC
deadline
* Lakehouse Day single post boost on LinkedIn from 6/25 to 7/28
* Finalized Community Over Code website and prepared for staging; waiting for
Infra to create repo
Project Comms
* Outreach to find Apache Wicket (Attic) credentials for X
Social Media Overview
The highest performing pieces of content for June include project news, Daniel
Ruggeri’s appointment, and the Apache Iceberg spotlight.
Social Highlights (X + Bluesky + Fosstodon + LinkedIn)*
* Total Audience: 150,434
* X: 66,217
* Bluesky: 1,127
* Fosstodon: 219
* LinkedIn: 82,871
* Total Posts:
* X / Bluesky / Fosstodon / Bluesky: 38
* LinkedIn: 12
* Total Engagements: 2,847 (X 1,605 + LinkedIn 1,242; not including BlueSky)
*Bluesky analytics are still hard to get consistently without paying for a
separate service. As of March 2026, reporting also includes Fosstodon. We
hope Buffer will enhance reporting capabilities in the near future so that
ASF social reporting is more comprehensive.
Website Analytics
722,202 visits, 722,088 unique visitors -0.8%
2 min 4s average visit duration -12.1%
61% visits have bounced (left the website after one page) +1.7%
2.2 actions (page views, downloads, outlinks, internal site searches) per
visit 0%
1,189,417 pageviews, 880,306 unique pageviews -3.1%
10 total searches on your website, 8 unique keywords +100%
99,775 downloads, 70,562 unique downloads +0.6%
300,163 outlinks, 172,555 unique outlinks +12%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Danny Angus]
General
-------
No issues currently require the Board's attention.
DKIM/Mail Delivery Problems
---------------------------
Infra is working on a fix for outgoing DKIM signing of mailing list posts.
There has been a rise in reports of people not receiving list mail due to
lack of DKIM signing. The fix is anticipated by end of July.
MFA Rollout
-----------
MFA soft-rollout continues. Some UI/UX points of confusion have been
identified. Additional documentation is being developed, and Infra is
seeking engagement with UI/UX design experts to improve the workflow
experience.
Atlassian Cloud Migration Status
--------------------------------
No new updates for July.
Community News
--------------
The July 1st Roundtable, wherein Clay Johnson of Gradle presented the
AI-powered Predictive Test Selection product, was a resounding success.
The presentation itself was excellent and several TLPs seem interested in
expanding their use of our Gradle offerings. Additionally, the July Roundtable
generated conversation and ultimately yielded a project workflow optimization
effort. This is a community-led effort to optimize builds across the board to
increase the efficacy of our shared builder pools.
August 5, 1700 UTC - For the August Roundtable, the Tooling team will present
the current state of the Apache Trusted Releases (ATR) platform, along with
the new Contingent Approval Platform (CAP).
-----------------------------------------
Attachment 5: Report from the VP of Tooling [David Fisher]
### Apache Trusted Releases
Finishing important features to prepare for the ATR Beta release in late July.
Highlights include:
1. Catalog of Releases and Archived Releases.
- A complete inventory of ASF release artifacts to build a full catalog.
- Reseeding by PMC once complex sub-projects organization is confirmed.
- Watching svn:dist:release changes to non-ATR releases and release archival.
2. Project Policies and Metadata.
- Expedited releases are secret. (This was challenging.)
- Project definition in .asf.yaml files with yaml export of projects in ATR.
3. Self hosted GH Runner means the staff remains productive despite GH Runner
contention.
4. ATR Releases since June 1, 2026
- Apache Cordova iOS 8.1.1
- Apache Cordova In App Browser Plugin 7.0.0
- Apache Maven Resolver 2.0.20
- Maven Filtering 3.5.1
- Maven Help Plugin 3.5.2
- Apache Software FOundation Parent POM 39
- Apache Maven Executor 1.0.0
- Apache Tooling ATR Maven Plugin 1.0.0-alpha-1
### Board Agenda Tool
Sander and Thomas have been making a number of improvements to the tool
related to new agenda creation, presentation mode, and executive sessions. A
number of bugs were fixed along with dependency upgrades.
### Responsible AI Tooling
1. ASVS Security Audits
- Proven effective with Claude Opus 4.8
- Simplified the process for efficiency
- Controlled cost and time, predictability
- Cost savings, establishing a pattern for the foundation/RAI
- Cost: ~$50–$150 per project scan using credits allocated to tooling by Infra
2. Other scans being used to plan future ATR work:
- GitHub Actions Security Reviews
- Runner Usage Analysis
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
We are still planning for evening events around the conferences in Glasgow.
Rich Bowen is working on putting together the project hackathon track, as well
as coordinating the keynote speakers.
Sponsorships continue to come in for Lakehouse Day and Community Over Code
Glasgow, at a good rate.
The new communityovercode.org should be launched in July, after a bit of a
delay.
The planning team has tentatively secured a venue for the 2027 North America
Community Over Code. A site visit is scheduled for September, 2026.
Paul King and Justin Mclean have put together a venue for a two-day Community
Over Code Sydney event, to be held November 18-19. A CFP will be out very soon
as of the time of submitting this report.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
Community Over Code - Glasgow
-----------------------------
Flights continue to be booked with plenty of time.
We are awaiting Visa news from several applicants before
we would book their flights.
Hotel rooms are booked
Community Over Code - Beijing
-----------------------------
Flights and accommodation is also in progress for China.
Monthly Meetings
================
Next meeting is due 2nd week of week of August
Future Events
=============
None Currently
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support.
Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still
to be done.
Mailing List Activity
=====================
Mailing list activity is usually minimal, and will drop this
section from the report as not useful.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
Nothing to report this month.
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Niklas Merz and Bryan Ellis (niklasmerz@ and erisu@) have joined the W3C
Embedded Web Engines & Native Web Runtimes Community Group.
These are the first participants from ASF. ASF has signed the W3C Community
Contributor License Agreement.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
June was a quiet month on the public legal lists. There are currently 6 open
LEGAL JIRA issues.
A board agenda item proposes replacing the Legal Affairs chair / VP, with
Justin Mclean taking over the role. Our thanks to Roman Shaposhnik, who has
served as VP Legal Affairs for nearly eight years, for his stewardship of the
foundation's legal matters and guidance on licensing and IP questions over
that time. It has been invaluable to the ASF.
We are still looking for someone to fill the VP assistant role.
One new issue LEGAL-731, on whether the NOTICE file may use
pointers (as LICENSE can) to automate NOTICE aggregation for binary
distributions. Roy Fielding held that NOTICE contents must be self-contained.
No new other matters were raised on the public list during June.
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
June
* While still more than before June, the rise in incoming load seems to have
calmed down this month. Many projects have accumulated a backlog of
open security reports, so we'll be working with them to help get back to
normal. We'll focus both on projects with many and with old reports.
Stats for June 2026:
37 [license confusion]
23 [support request/question not security notification]
17 [report/question relating to dependencies]
5 [reports held back pending batch sampling]
Security reports: 574 (last months: 739, 515, 386, 200, 160, 98)
41 ['httpd']
26 ['dolphinscheduler']
24 ['airflow']
23 ['cloudstack']
22 ['tomcat']
19 ['superset']
17 ['apisix']
14 ['fineract']
12 ['activemq', 'commons']
11 ['shenyu', 'shiro']
10 ['httpcomponents', 'inlong', 'nuttx']
9 ['dubbo', 'trafficserver']
8 ['cxf', 'guacamole', 'kvrocks', 'mina', 'ofbiz']
7 ['directory', 'flink', 'thrift']
6 ['beam', 'hive', 'impala', 'kafka', 'nifi', 'opendal',
'rocketmq', 'tika']
5 ['answer', 'camel', 'cassandra', 'fory', 'web site or infra',
'kylin', 'spark', 'streampipes', 'syncope']
4 ['brpc', 'hugegraph', 'ignite', 'linkis', 'pdfbox', 'poi',
'ranger', 'seatunnel', 'streampark', 'zeppelin']
3 ['calcite', 'doris', 'hadoop', 'hertzbeat', 'iceberg',
'openoffice', 'paimon', 'pouchdb', 'seata', 'solr', 'tvm',
'ws', 'xerces']
2 ['age', 'amoro', 'arrow', 'artemis', 'avro', 'casbin',
'druid', 'fesod', 'geode', 'gravitino', 'hamilton', 'hbase',
'kie', 'ozone', 'parquet', 'shardingsphere', 'tez',
'tinkerpop']
1 ['axis', 'burr', 'cloudberry', 'devlake', 'echarts',
'eventmesh', 'gobblin', 'groovy', 'helix', 'iotdb', 'jena',
'karaf', 'knox', 'libcloud', 'logging', 'madlib', 'oozie',
'openwhisk', 'phoenix', 'pinot', 'serf', 'skywalking',
'velocity', 'wicket', 'xmlgraphics']
In total, as of 1st July 2026, we're tracking 1314 (last months: 1139, 856,
629, 440) open issues across 156 projects, median age 54 days
(last months: 51, 44, 47, 64). 262 of those issues have CVE names
assigned. 29 (last months: 25, 32, 28, 22) of these issues, across 17
projects, are older than 365 days.
* openoffice (Health red): Several issues in OpenOffice are over 365
days old. They are not severe enough to warrant stopping
distribution of OpenOffice. (Last update: 2026-07-01)
* 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 [Ed Coleman]
## 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 moderate activity
Issues for the board: The current PMC chair has not recently been active in
the project, and the last few board reports have been prepared by an alternate
volunteer. The PMC is currently in process of discussing nominations for a new
PMC Chair to nominate to the board.
## Membership Data:
Apache Accumulo was founded 2012-03-20 (14 years ago)
There are currently 43 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kevin Rathbun on 2024-07-24.
- No new committers. Last addition was John Kucera on 2025-06-04.
## Project Activity:
Project activity varied between several different efforts.
- Work on a separate access control library was updated to support Java 11 for
use with Accumulo 2.1 versions (1.0.0-beta3).
- Work on bug fixes and stability fixes for the Accumulo 2.1 release series has
been ongoing, with a 2.1.5 vote completed just prior to this submission.
- Work on improvements to the future 4.0 version to support more dynamic
scaling (elastic deployments) continues, with recent focus on updating Java,
Hadoop, and Thrift dependencies, producing and displaying metrics, and
command-line tool improvements. Some progress on new features has stalled
due to temporary inactivity of the main contributor for those features, but
this probably will not block any future release, and the work may be
deferred to a later version.
## Community Health:
Overall community health is good, and GitHub activity remains regular. The low
email traffic on the dev list reflects the community preference of using
GitHub projects and issues for planning and PRs for code discussions, but this
activity is also reflected in the notifications list, for anybody who prefers
not to engage on GitHub (this is rare for our community). We have observed
some new "drive-by" contributions for easy-to-fix typos and things that are
probably the result of contributors using AI to create PRs, but these haven't
resulted in any new active contributors, though we have seen at least one new
active contributor in the last quarter, and several existing community members
have provided some tips and mentoring on ASF's Slack and in PR comments. The
only serious concern is finding a replacement PMC Chair. We have a few
nominations on the private list, which we will discuss and vote on, and
present to the board for approval.
-----------------------------------------
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 (19 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:
The PMC has been almost entirely focused on addressing security reports for
the last 3 months. All other work was put on hold while triaging and fixing
the large number of security reports from AI scans. Over 20 CVEs have
been fixed and released. The number of reports has slowed down drastically
after the last round of fixes and we are starting to resume work on the 6.3.0
release.
Releases:
- 6.2.7 was released on 2026-06-29.
- 5.19.8 was released on 2026-06-29.
- 6.2.6 was released on 2026-05-31.
- 5.19.7 was released on 2026-06-31.
- 6.2.5 was released on 2026-04-23.
- 5.19.6 was released on 2026-04-23.
- 6.2.4 was released on 2026-04-09.
- 5.19.5 was released on 2026-04-09.
Other notes:
- Project is working towards v6.3.0 and other patch releases.
- Major updates include Jetty 12 and JDK 25 support.
## Community Health:
We have a sustained activity on the mailing lists. We also see new
contributors who submitted new PRs. We are are moving forward on JMS 3.1 and
preparing a proposal for runtime for ActiveMQ 7.
-----------------------------------------
Attachment C: Report from the Apache AGE Project [Jeff Jirsa]
## Description:
The mission of Apache AGE is the creation and maintenance of software related
to a multi-model database that enables graph and relational models built on
PostgreSQL
## Project Status:
Current project status: Ongoing, but low activity
Issues for the board: The board appointed PMC chair has asked to be replaced.
It is unclear if the board wants to appoint a new Chair, or allow the PMC to
elect its own chair. The PMC Chair asks the board to clarify its intent and
desire so the PMC may act appropriately.
## Membership Data:
Apache AGE was founded 2022-05-17 (4 years ago)
There are currently 20 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jeff Jirsa on 2025-05-11.
- Greg Felice was added as committer on 2026-06-05
## Project Activity:
The project recently elected a new committer. Release activity is steady /
adequate.
## Community Health:
Project interest appears to be growing, but organic contribution is low. There
are relatively few outside contributors of substance that can be grown into
committers / PMC members.
-----------------------------------------
Attachment D: Report from the Apache Airavata Project [Suresh Marru]
-----------------------------------------
Attachment E: Report from the Apache Airflow Project [Bolke de Bruin]
-----------------------------------------
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 (a year and a half 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.1 on May 29, completing the semantic search work started
last quarter: embedding support in AI chat, a vector search plugin, and a
vector sync service.
- v2.0.1 also bundled security hardening (API key scope checks, stricter
input validation and HTML escaping) and post-v2.0.0 regression fixes
(attachment upload, Helm chart port, dark mode rendering).
- Next-cycle development is underway: AI reasoning content in conversation
records, panic recovery middleware, optional email verification, and
ASCII transliteration for non-Latin question titles.
## Community Health:
- 4 new external contributors had pull requests merged this quarter,
contributing both features and fixes.
- 6 issues were filed by 6 unique reporters, covering AI/LLM integration,
search behavior, and upgrade regressions; post-v2.0.0 regressions were
fixed promptly.
- dev@ traffic remains low (18 emails across 13 threads, mostly release
votes); day-to-day development coordination happens on GitHub.
- Activity was quieter than last quarter's v2.0.0 push but steady.
-----------------------------------------
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:
The APISIX release cycle is now two months,
3.17.0 was released on 2026-06-15.
3.16.0 was released on 2026-04-07.
3.15.0 was released on 2026-02-05.
In the past two months, we've received a number of CVE reports.
The PMC has invested considerable effort in triaging and resolving them,
and has published new releases with the fixes.
Community Health:
The rise of AI has lowered the barrier to entry for developers
contributing to APISIX,
resulting in a noticeable increase in the number of PRs
submitted to the community.
-----------------------------------------
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: Largely maintenance mode with some developments ongoing.
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:
Mainly dependency upgrades and support for new Java versions.
Released Aries Typed Events 1.0.1.
A lot of
improvements have been made in Aries RSA module. Some potential TCK test suite
errors where found and reported in the OSGi repository.
## Community Health:
Slightly decreased activity. Development driven by a low number of active
committers.
-----------------------------------------
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 (high activity)
Issues for the board:
* (from the PMC chair) Again, it would be nice if the initial reminder for board
reports came earlier - say, 3 weeks before the deadline. 1 week is too short
for volunteer work, especially if we want to crowdsource the report for more
informative content.
## Membership Data:
Apache Arrow was founded 2016-01-20 (10 years ago). There are currently 117
committers and 61 PMC members in this project. The Committer-to-PMC ratio is
roughly 2:1.
We haven’t onboarded any new committers in the last quarter despite high
contribution levels, which is a deficiency on our part. We have begun the
process of looking for candidates.
It might make sense for the ASF to provide dedicated tooling to help look for
potential committers by analyzing (at least quantitatively) activity on GitHub
pull requests, code reviews and project mailing lists.
Community changes, past quarter:
* No new PMC members. Last addition was Rossi Sun on 2025-10-06.
* No new committers. Last addition was Ryan Johnson on 2026-01-30.
## Project Activity:
The project has an [active blog](https://arrow.apache.org/blog/) where you can
find more information on recent releases.
### Community Initiatives
The first Arrow / Parquet meetup in Paris was a success, with around 40
attendees. See post at
https://www.linkedin.com/feed/update/urn:li:activity:7474760529719308288/
### Community Organization
The Arrow project is increasingly organized as different communities focused
on the different Arrow language implementations (e.g C++ and bindings like
Python, Rust, Go, etc). These communities collaborate on the overall Arrow
specification and interoperability issues. This structure seems to be working
well as the project grows and matures.
### AI-Generated Contributions
The influx of AI-generated contributions seems to have dampened quite a bit.
Earlier this quarter we received and handled many “security reports” – most of
which turned out to be normal bugs. This prompted us to more formally define
our security and threat model, and we appreciate the ASF Security Teams
collaboration in managing them. More recently , “security reports” have become
very seldom.
### Handling of Security Reports
The workflow for dealing with security reports is awkward and taxing. Issues
are forwarded by e-mail to the PMC by the ASF Security Team and there is no
structured way to act on issues (such as: categorize them, change their
status, etc.). The Security Team are trialing a new read-only dashboard that
gives a summary of a project’s current security reports; however, all handling
still happens over unstructured e-mail. Ideally, a ticketing system shared
between PMC and Security Team would allow tracking security reports using
modern means.
### Recent Releases
RS-OS-0.14.0 was released on 2026-06-22.
RS-59.0.0 was released on 2026-06-09.
RS-56.2.1 was released on 2026-05-11.
RS-57.3.1 was released on 2026-05-11.
RS-58.3.0 was released on 2026-05-11.
DOTNET-23.0.0 was released on 2026-05-06.
RS-58.2.0 was released on 2026-05-02.
Go-18.6.0 was released on 2026-04-28.
24.0.0 was released on 2026-04-21.
ADBC-23 was released on 2026-04-07.
## Community Health:
Based on mailing-list volume, project activity remains steady.
Quarter-to-quarter variations can probably be attributed to random oscillation
rather than any structural change. Of note, several projects such as Arrow C++
and Arrow Rust have GitHub discussions enabled to help with user questions
(those are echoed on user@arrow.apache.org, so are still accounted for in the
stats below).
All metrics from https://reporter.apache.org/wizard/?arrow#, for posterity:
* builds@arrow.apache.org had a 40% increase in traffic in the past quarter
(682 emails compared to 486)
* dev@arrow.apache.org had a 14% increase in traffic in the past quarter (300
emails compared to 263)
* user@arrow.apache.org had a 68% increase in traffic in the past quarter (157
emails compared to 93)
-----------------------------------------
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 44 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Peeyush Gupta on 2025-12-02.
- Suryaa Charan was added as a committer on 2026-04-06
## Project Activity:
A number of changes went in to prepare for the next release. The web interface
was finally updated to not have a number of EOL dependencies that would have
been bad to ship with. There were also a number of issues fixed with the Async
Query API since the last report. There are now only a few remaining changes on
the agenda, and some documentation needed for the user side of some of the new
features added as APEs over the past few years.
APEs:
- APE 2 (Query Plan Cache) was revived and is under discussion and review
- APE 29 (Atomic Statements) was posted, as hopefully the last "retroactive"
- APE 31 (LSM Sampling) and 32 (Vector Indexing) are converging on review
- APE 33 (CLUSTER BY clause) is being refined and prototyped
- APE 34 (External Functions) was proposed and has a prototype implementation
## Community Health
GSoC is underway with some great preliminary results. We got a couple accepted
proposals. One is for an MCP server for AsterixDB. The other is for allowing
dynamic memory allocation for certain operators within AsterixDB. dev@ is
somewhat back to normal traffic levels from the surge of posts caused by the
start of GSoC. There was also a vote to add a new PMC member that succeeded,
but I forgot to send him the invite email, so hopefully by next report we will
have a new PMC member.
-----------------------------------------
Attachment K: Report from the Apache Attic Project [Hervé Boutemy]
-----------------------------------------
Attachment L: Report from the Apache Avro Project [Ryan Skraba]
-----------------------------------------
Attachment M: Report from the Apache bRPC Project [James Ge]
Description:
The mission of Apache bRPC is the creation and maintenance of software related
to an industrial-grade RPC framework for building reliable and
high-performance services
Project Status:
Current project status: ONGOING Issues for the board: NONE
Membership Data:
Apache bRPC was founded 2022-12-21 (3 years ago) There are currently 21
committers and 14 PMC members in this project. The Committer-to-PMC ratio is
3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Guangming Chen on 2025-01-06.
- No new committers. Last addition was Yang Liming on 2024-03-24.
Project Activity:
bRPC v1.17.0 was released on 2026-05-28 with the following new features:
- Add SingleIOBuf for efficient FlatBuffers serialization/deserialization
- Support native Redis Cluster channel and transport layer for
protocol extensions
- Support RDMA ECE and rate-limited backup request policy
- Fix multiple use-after-free issues and ARM memory visibility
- Extend fuzz testing coverage and improve Protobuf compatibility
Community Health:
Committers take turns responding user emails and issues on a weekly basis.
During the past quarter, about 30 new emails were received and answered
weekly.
-----------------------------------------
Attachment N: 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 81 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 of committers were added. We did have additions
in the prior quarter.
## Project Activity
In the last three months:
- Calcite 1.42.0 was released on 2026-05-31
- Avatica 1.29.0 was released on 2026-05-12
Other recent releases
- Calcite 1.41.0 was released on 2025-11-01
## Security Response
In the last quarter we have received several vulnerabilities reports.
As a consequence of the investigation we have allocated CVE-2026-46718
and CVE-2026-50611, which already have solutions; these solutions will
be part of the the next Calcite release. Some security
vulnerabilities were deemed as belonging to third-party libraries; to
clarify the scope of vulnerabilities Calcite will publish a threat
model; a PR describing the threat model is currently under review.
Many thanks are due to the community members for the quick response:
Julian Hyde, Stamatis Zampetakis, Ruben Quesada, Vladimir Sitnikov.
## Community Health
The community seems very actively engaged. We are seeing a substantial
increase in traffic, no doubt due to the barrier of entry to contributions
being lowered by AI tools.
We have discussed on the mailing raising the barrier for acceptance as
committer and PMC due to the use of AI tools; this partly explains the absence
of new members. We are considering to require more engagement, including
constructive code reviews, in order to promote participants as committers and
PMC members.
We have seen bug reports and contributions from a significant number of new
participants; e.g., we had 13 new JIRA accounts created.
- 174 JIRA tickets opened and 171 closed in the past quarter.
- dev@calcite.apache.org had a 53% increase in traffic in the past quarter
(384 emails compared to 226).
- issues@calcite.apache.org had a 84% increase in traffic in the past quarter
(1512 emails compared to 819)
Top committers for last 3 months:
https://github.com/apache/calcite/graphs/contributors?selectedMetric=commits
- mihaibudiu: 25 commits
- snuyanzin: 23 commits
- xuzifu666: 23 commits
- caicancai: 11 commits
- xiedeyantu: 11 commits
- zabetak: 10 commits
- iwanttobepowerful: 5 commits
Most active reviewers in the last 3 months:
- 178 mihaibudiu
- 107 xuzifu666
- 56 xiedeyantu
- 24 zzwqqq
- 24 iwanttobepowerful
- 17 snuyanzin
- 14 caicancai
- 11 cjj2010
- 8 dssysolyatin
- 7 zabetak
- 7 wasabii
- 7 darpan-e6
- 6 venkata91
- 5 tkalkirill
- 5 silundong
- 5 sbroeder
- 5 julianhyde
- 5 Dwrite
-----------------------------------------
Attachment O: 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:
- Optimized Agent_module
- Released new version 2.3.2, and Fixed security issues ： https://cveprocess.apache.org/cve5/CVE-2026-29171
- Fixed dependency issues and CI issues.
- Bug fix some feature issues
## Health Report:
- Commit activity:
- 20 commits in the past quarter
- 4 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
- dev@carbondata.apache.org:
- 153 subscribers (change 8):
## Github issues activity:
- 13 issues be handled
## Github PR activity:
- 16 PRs opened on GitHub, past quarter
- 13 PRs closed on GitHub, past quarter
-----------------------------------------
Attachment P: Report from the Apache Causeway Project [Jörg Rade]
## Description:
The mission of Causeway is the enable the creation and maintenance of
domain-driven apps in Java, using the naked objects architecture pattern.
## 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 the last quarter we released Causeway 4.0.0-M2 [1] which provided
initial support for OpenTelemetry. We also released 3.6.0 [2], a maintenance
release.
The 4.x branch is based on Spring Boot 4, making use of Java features beyond
version 17 and ending support for JDO persistence mechanism; in its place we
support EclipseLink JPA and we also are planning Hibernate support. v4.0.0 is
expected to be released in Q3 2026.
We continue to promote the framework to extend our user base. Dan presented at
Arnhem JUG in June 2026, and we are planning to have a community get together
end of August [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://apache-causeway-committers.github.io/causeway-nightly/relnotes/latest/2026/3.6.0/relnotes.html
[2] https://apache-causeway-committers.github.io/causeway-nightly/relnotes/latest/2026/4.0.0-M2/relnotes.html
[3] https://www.socrates-conference.de/
-----------------------------------------
Attachment Q: Report from the Apache Celix Project [Pepijn Noltes]
-----------------------------------------
Attachment R: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Apache CouchDB software is a document-oriented database that can be queried and
indexed in a MapReduce fashion using JavaScript. CouchDB also offers
incremental replication with bi-directional conflict detection and resolution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache CouchDB was founded 2008-11-19 (18 years ago)
There are currently 74 committers and 18 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 Glynn Bird on 2023-03-14.
- No new committers. Last addition was James Coglan on 2026-03-24.
## Project Activity:
We released bugfix version 3.5.2 in May and are continuing to prepare
a new feature release 3.6.0 in the near future.
## Community Health:
The project operates at the usual velocity for the time of year. We are
aiming to organise an in-person meet-up during CoC in Glasgow.
-----------------------------------------
Attachment S: Report from the Apache Curator Project [Enrico Olivelli]
-----------------------------------------
Attachment T: Report from the Apache CXF Project [Andriy Redko]
Description:
Apache CXF is an open source services framework. CXF helps you build and
develop services using frontend programming APIs, like JAX-WS and JAX-RS.
These services can speak a variety of protocols such as SOAP, XML/HTTP,
RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS
or JBI.
There is also a sub-project that leverages CXF:
Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.
Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
Membership Data:
Apache CXF was founded 2008-04-15 (18 years ago)
There are currently 44 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
No new PMC members. Last addition was Andy McCright on 2019-02-24.
No new committers. Last addition was Jamie Mark Goodyear on 2024-07-19.
Project Activity:
The project was struggling with very large number of CVE reports, mostly all
were addressed and landed in the recent release train.
Recent releases:
4.1.7 was released on 2026-06-10.
4.2.2 was released on 2026-06-10.
Community Health:
A lot of team's work was directed towards resolving CVEs, and the
reports are still coming (luckily, at considerably slower rate). Also,
the team decided to reverse the decision to EOL 3.6.x maintenance branch
since there are quite a few projects depending on it, new 3.6.x release
is expected to be out shortly. As always, we are responding to bug reports
and reviewing and merging pull requests promptly.
-----------------------------------------
Attachment U: Report from the Apache DataFu Project [Eyal Allweil]
## Description:
The mission of Apache DataFu is the creation and maintenance of software
related to well-tested libraries that help developers solve common data
problems in Hadoop and similar distributed systems
## Project Status:
Current project status: Ongoing (low)
Issues for the board: None
## Membership Data:
Apache DataFu was founded 2018-02-21 (8 years ago)
There are currently 20 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ohad Raviv on 2023-02-06.
- No new committers. Last addition was Ben Rahamim on 2025-02-19.
## Project Activity:
There is a new contributor who has done some nice work lately on our CI, and
on compatibility with the newer versions of Spark - this puts us closer to a
release.
The blog post we wanted to co-publish with the PayPal blog was delayed because
of internal PayPal issues but there are promising developments that may allow
us to do this soon.
## Community Health:
Our activity is still spread out in three places - GitHub (in the PRs), then
Jira, and finally the mailing list, and still pretty thin. At this point it's
mostly current and former PayPal employees - we haven't had any contributors
from "outside" converted to committers in ages. Still hoping a release and
blog post will attract more attention - we're not the only auxiliary library
for Spark-related code, and the others are also small.
-----------------------------------------
Attachment V: 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 remains active and responsive, with regular participation in
weekly project meetings and continued attention to release readiness, code
quality, security posture, and build infrastructure.
Recent work has focused on preparing the project for a future release. The
community has continued working through issues identified by the Trusted
Release process, including license header updates, RAT configuration issues,
and project POM changes needed to support release validation. Several related
pull requests were merged during the quarter, including fixes for Apache
license headers and build configuration changes. The project also identified
and reported a Trusted Release workflow issue in which a test vote was
sent to
the wrong mailing list, and the community is working with the appropriate ASF
teams to resolve this before proceeding further.
Release planning is currently tied to completion of the initial security-scan
work. The project expects to revisit a possible JDO 3.2.2 release once the
initial scan-related issues have been addressed.
Security review has become a significant area of activity this quarter. A draft project security threat model was proposed, along
with
SECURITY.md and AGENTS.md files to support external review. The project has
requested a security scan using these files. The community is also monitoring
ASF guidance and related work from other projects while questions around
model
access and external scanning are resolved.
In parallel, the project reviewed results from an AI-assisted scan of the
db-jdo repository, tracked under JDO-861. Several resulting issues were
investigated, including proposed fixes for IntIdentity/LongIdentity
comparison
overflow and LegacyJava/JDOHelper-related concerns. Some findings were
determined to be false positives or not applicable, while remaining items are
being addressed before JDO-861 is closed.
Code quality work also continued. The community is still reviewing SonarCloud
findings under JDO-819 and JDO-823, including raw type warnings and cognitive
complexity findings. Some reported issues require careful review because they
relate to public API constraints or TCK structure where a straightforward
code
change may not be appropriate. In these cases, the project is evaluating
whether to adjust code, annotate specific methods or interfaces, or otherwise
document why a finding should be ignored.
Additional ongoing technical discussions include:
* Continuing investigation of JDO-812, which would raise the minimum
supported Java version to JDK 11.
* Continued work on JDO-847 to generate SBOM files.
* Review of SPDX and CycloneDX-related warnings in the build.
* Follow-up on possible API enhancements, including Map.containsEntry-style
functionality.
* Long-running discussion items such as Android compatibility, Java Records,
and possible future specification work.
### Apache Torque
Activity in the Torque project remains relatively light, but there was
renewed
technical discussion and development activity during the quarter.
The main area of recent work has been support for the Java Time API. A new
improvement issue was opened to replace use of java.util.Date with the
java.time API. Initial patches were submitted for torque-runtime, followed by
updates covering torque-template, generated primary key handling, tests, and
documentation. The work has included mapping SQL date/time types to the
corresponding Java Time classes, including LocalDate, LocalTime,
LocalDateTime, OffsetDateTime, and OffsetTime.
Testing of the Java Time work has identified some database and
driver-specific
issues, particularly around Derby support. The project discussed whether
Derby
remains a suitable test target given its retirement and limited support
for the
Java Time API. Subsequent testing shifted toward HSQLDB and PostgreSQL, with
patches updated to address test failures and align behavior across supported
databases.
The community also discussed possible Java version upgrades for a future
Torque
release. One proposal suggested moving the next development version to Torque
8.0-SNAPSHOT and raising the Java baseline from Java 17 to Java 21. The main
motivation discussed was alignment with related Apache Turbine modernization
work and potential database dependency considerations. The discussion also
recognized that, as a library, Torque should be cautious about raising its
minimum Java requirement too quickly because downstream applications may
still
depend on older Java versions.
Other than these discussions and patches, project activity has remained
modest.
The Torque codebase remains stable, and the community continues to consider
future direction around Java baseline, database support, and modernization of
the runtime, templates, tests, and documentation.
### Project-Level Updates
No project-level issues require board attention at this time.
## Community Health:
The Apache DB project remains stable and in good health.
The JDO subproject continues to show steady development and maintenance
activity, with regular meeting participation, active review of pull requests,
and ongoing attention to release readiness, security posture, code
quality, and
infrastructure improvements. The community is responsive to ASF-wide guidance
around release process and security review.
The Torque subproject remains quieter, but recent discussion and patch
activity
around Java Time support and future Java version requirements show that the
community remains engaged in maintaining and modernizing the codebase.
PMC engagement remains solid, with active participation in project
discussions
and decision-making. There are no current concerns requiring board attention.
-----------------------------------------
Attachment W: Report from the Apache Directory Project [Shawn McKinney]
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely written in
Java, which has been certified LDAPv3 compatible by the Open Group.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
This is a "schema aware” API with some convenient ways to access all types
of LDAP servers.
- Studio: A complete directory tooling platform intended to be used with any
LDAP server however it is particularly designed for use with ApacheDS. It is
an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based authorization platform that provides role-based
access control, delegated administration and password policy services with
an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains various tools
to access and manage kerberos principals and keytabs. It provides a rich,
intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.
- Mavibot: An embeddable key-value database library with MVCC (Multi Version
Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Project Status:
Current project status:
There has been good activity across a few of the subprojects and low across
others. More detail to follow.
Issues for the board:
No issues to report at this time.
## Membership Data:
Apache Directory was founded 2005-02-22 (21 years ago)
There are currently 57 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Brian Demers on 2023-10-23.
- No new committers. Last addition was Fredrik Roubert on 2023-07-10.
## Project Activity:
Per sub-project:
- ApacheDS: med activity. Getting ready for a release. The LDAP API now
released no longer a blocker. There is a TLS issue with MINA that need to
be corrected.
- LDAP API: med activity. Released this quarter.
- Studio: low activity. Also soon to have a new release, using Java 25.
- Fortress: low activity. Needs a release. No activity from the community.
- Kerby: low activity. Released this quarter.
- Mavibot: low activity.
- SCIMple: low activity. Needs a release. Activity from the community, PR's
are being managed.
## Community Health:
Decent activity the last quarter over ApacheDS, API, Kerby and Scimple.
Members of the project are responsive to a batch of new security issues of
late. Subprojects that have had low activity are now picking up. Issues are
being addressed. Merge requests are being handled and the maintainers remain
active and responsive.
-----------------------------------------
Attachment X: Report from the Apache DolphinScheduler Project [Lidong Dai]
## Description:
Apache DolphinScheduler is a cloud-native workflow orchestration platform with
powerful user interface, dedicated to solving complex task dependencies in the
data pipeline and providing various types of jobs available `out of the box`
## Project Status:
Current project status:Health issues for the board: There are no issues for
the board at this time
## Membership Data:
Apache DolphinScheduler was founded 2021-03-17 (5 years ago) There are
currently 59 committers and 27 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 Xin Cheng on 2024-06-18.
- No new committers. Last addition was Hengliang Tan on 2024-07-02.
## Project Activity:
- 3.4.2 was released on 2026-06-05.
- 3.4.1 was released on 2026-03-06.
- 3.4.0 was released on 2026-01-20.
- 3.3.2 was released on 2025-10-26.
## Community Health:
- We have held one community online Meetups in last quarter and about ~80
people joined the Meetup and Xiaodong shared the topic: Practical Operations
& Demo of DolphinScheduler Agent.
-----------------------------------------
Attachment Y: Report from the Apache Druid Project [Abhishek Agarwal]
## 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, Hadoop 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 76 committers and 42 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 Cece Mei on 2026-03-09.
- No new committers. Last addition was Sasha Syrotenko on 2026-03-25.
We have started a voting thread to elect the new PMC chair.
## Project Activity:
We had one major releases since the last report
- 37.0.0 - 255 changes from 29 contributors
Druid typically does major releases 3–4 times a year. There is an
active discussion thread on 38.0.0 release.
Development Activity:
- 512 pull requests opened
- 387 pull requests merged/closed
The github activity is significantly higher compared to past quarter.
This also shows up in the github commit activity, indicating good
momentum.
## Community Health:
Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,418
members, up 53 members since our last report. The growth in slack community last
time was about 51. The flat growth indicates that the slack channel
growth has reached saturation.
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.
We need to bring in more contributors/committers. An active discussion
is underway for organizing office hours that should help boost
participation and improve community health.
-----------------------------------------
Attachment Z: Report from the Apache Dubbo Project [Jun Liu]
## Description:
Apache Dubbo is an easy-to-use RPC framework that provides different
language implementations, service discovery, traffic management,
observability, security, tools, and best practices for building
enterprise-ready microservices.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Dubbo was founded 2019-05-15 (7 years ago)
There are currently 119 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Yu Yu on 2025-12-29.
- Zerui Yang was added as committer on 2026-06-02
## Project Activity:
The last release was made around March, and there were no releases recently in
our community during this period. I have noticed that the community has
accumulated some issues from github issues submitted by users, as well as some
pull requests submitted (especially regarding TCP and TLS link management),
many of which have a significant impact on the stability of the framework.
Therefore, we plan to prioritize merging these pull requests in the coming
period and complete the version release.
In addition, some security vulnerabilities have been submitted, and I have
roughly scanned some of the emails. Most of them may not be real vulnerability
issues within our framework. We need to call on other PMC members to come in
and take a look, and provide clear responses and also label these
vulnerabilities first.
## Community Health:
The overall mailing list and GitHub activity of the community
have shown a slowly downward trend. The project has maintained a code change
and maintenance status, mainly focusing on fixing issues found in some
versions. Currently, active projects mainly include Java and Go language
implementations.
Meanwhile, based on past market accumulation and Maven
download data, the overall user base of the project remains large.
-----------------------------------------
Attachment AA: Report from the Apache Fineract Project [James Dailey]
## Description:
The mission of Apache Fineract is the creation and maintenance of software
related to a core banking platform that provides a reliable, robust, and
affordable solution for entrepreneurs, financial institutions, and service
providers to offer financial services to the world's underbanked and unbanked.
## Project Status:
Current project status: Ongoing
Issues for the board: 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:
Recently there's been a renewed focus on refactoring and on security issues.
We now have a Fineract security model in the main branch.
Last release was 1.14 in December 2025. We've announced a new release process
starting with Adam Monsen as the release manager again.
We have added four new GitHub repos to our project, expanding the potential
breadth of functionality while keeping the core project separate.
###fineract-loan-origination - this component is being coded by a GSOC
student as a POC of the kind of processing needed before a loan application
hits the Fineract core processing.
###fineract-consumer-facing. - this component is being coded by a GSOC
student as a POC to cover the end-user interactions. That is, this
component will provide the backend for the front end so that the "self
service" functionality removed from the core sits in the proper place in
the architecture.
###fineract-business-intelligence - this component is coded by a GSOC student
to allow for reports and analytics to run on the data extracted or
streamed from Fineract. This is also a POC.
### fineract-backoffice-ui - this component is intended to make the fineract
solution fully deployable with a UI to understand the main functionality.
While other vendors have solutions, the headless aspect of Fineract makes
it hard for audiences to understand - this hopefully resolves that within
the brand of Apache fineract.
## Community Health:
Community is working well, there's a healthy set of discussions. Attendance at
community calls has been good. GSOC students are working on projects and new
areas of development.
We have moved to Matrix for our chat tooling for the community. Matrix is a
federated open source tool.
-----------------------------------------
Attachment AB: Report from the Apache Flagon Project [Joshua Poore]
## Description:
The mission of Apache Flagon is the creation and maintenance of software
related to thin-client behavioral logging capability useful for business
analytics, usage analytics, usability and user testing
## Project Status:
Current project status: Considering the future Issues for the board: Either
Flagon will elect a new PMC Chair and change direction, or VOTE on retirement.
## Membership Data:
Apache Flagon was founded 2023-03-21 (3 years ago)
There are currently 20 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Evan Jones on 2024-07-10.
- No new committers. Last addition was Mederick Grivel on 2026-01-14.
## Project Activity:
Considering retiring due to failure on the PMC chair to effectively grow the
community. Currently soliciting self-nominations amongst PMC for new Chairs.
If nothing heard, we will hold a VOTE on retirement (after checking ASF
rules/policies).
## Community Health:
Over the quarter, PMC ran a successful roll-call and initiated discussion
about the future of the project. Some discussion was had. Of those who
participated, there was a feeling that project may have run its course in its
current form, or at ASF. Considerations included developments in the Open
Telemetry community and the emerging standards in Observabilty. Additionally,
while at least one PMC member indicated interest in the project, but indicated
trepedation of leading under the policies and processes of Apache. Hearing
little additional discussion, PMC chair solicited nominations for a new chair
in case someone wants to take the project in a new direction. If no one raises
their hand, PMC Chair will call a VOTE on retirement.
-----------------------------------------
Attachment AC: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment AD: Report from the Apache Fory Project [Chaokun Yang]
The Apache Fory is a high-performance, multi-language serialization framework
that enables efficient data exchange across systems and programming languages.
Leveraging JIT compilation and zero-copy techniques, Fory delivers
low-latency, high-throughput serialization for modern distributed
applications.
## Project Status: Ongoing with high activity.
Board-Level Issues: There are no issues requiring Board action at this time.
Over the past quarter, the Apache Fory project has made significant progress
in core development, documentation, and community growth: We released fory 1.0
and added grpc with fory serialization support across java/python/rust/go/
dart/scala/kotlin.
The community remains active and engaged, with steady contributions from both
long-standing and new contributors.
Recent Releases: The project has maintained a strong release cadence over the
past quarter:
v1.3.0 June 25, 2026
v1.2.0 June 16, 2026
v1.1.0 May 31, 2026
v1.0.0 May 21, 2026
v0.17.0 Apr 19, 2026
These releases include performance improvements, bug fixes, Security enhance
and grpc support.
## Project Activity:
Development activity remains robust, with ongoing work
across multiple fronts:
Continuous improvement of documentation for users and contributors;
Active development on Fory implementations in compiler, and grpc support
Current Plans: The project’s roadmap for the coming months includes:
Attracting new contributors via outreach and improved contribution guides
Further enhancing user and contributor documentation to lower entry barriers
We are also exploring opportunities for collaboration with other Apache
projects to demonstrate cross-project interoperability.
## New Committers and PMC Members:
Committer: Ayush Kumar was added on June 22, 2026
## Branding and Legal Considerations:
There are no known branding or legal issues
at this time. The project continues to use its name and marks in accordance
with Apache policies. All official project materials reflect proper branding
and attribution.
## Infrastructure and Strategic Needs:
No critical infrastructure issues have
been encountered. The project is satisfied with current tooling and services
provided by the Apache Infrastructure team.
-----------------------------------------
Attachment AE: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AF: Report from the Apache Gluten Project [Weiting Chen]
## Description:
The 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, stable.
Issues for the board: None.
## Membership Data:
Apache Gluten was founded 2026-02-18 (~5 months ago)
There are currently 45 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members since graduation.
- No new committers added since Ankita Victor (2026-04-16).
## Project Activity:
Release
- Latest official release: v1.6.0 (Mar 10, 2026) — first release as a
Top-Level Project.
- v1.7.0 release plan discussion initiated on dev@gluten.apache.org.
- v1.7.0-SNAPSHOT nightly convenience builds (Spark 3.4/3.5/4.0/4.1 on x86_64
and aarch64) began publishing to nightlies.apache.org on 2026-06-18,
indicating active release-branch stabilization.
- main branch bumped to 1.8.0-SNAPSHOT in mid-June, reflecting parallel
forward development.
Development
- Major feature work merged across Velox, ClickHouse, Flink, Iceberg, Delta,
and Paimon subprojects. Highlights:
- Broadcast Hash Join (BHJ) driver-side hash-table optimization landed,
aligning with Spark's BHJ semantics.
- New gluten-flink subproject actively receiving contributions (e.g.,
[GLUTEN-12397] [FLINK] Support WatermarkStatus propagation).
- Iceberg writer improvements (dictionary-size bytes write config) and
continued Delta 4 native write support for Spark 4.0.
- ClickHouse backend gained map_from_entries and other function coverage.
Spark 4.1 nightly bundle now published, marking the first regularly
published 4.1 artifacts.
- Community-level infrastructure discussions on dev@: CentOS 7 deprecation,
ASF shared GitHub runner consumption(the community is tracking the
mitigation in issue#12288), auto review-assignment automation, and interest
in the Community Over Code Glasgow 2026 hackathon.
## Community Health:
- GitHub activity remains healthy: repo now at ~1.6k stars and ~625 forks,
with weekly PR volume comparable to prior quarter.
- The 2026 community roadmap tracked in issue #11827 continues to see
contributions across Spark 4.0/4.1 GA, TIMESTAMP_NTZ, Variant, Parquet type
widening, ANSI mode, and multi-backend exploration.
- Governance and communication running smoothly on dev@gluten.apache.org; no
conduct or governance issues reported this period.
-----------------------------------------
Attachment AG: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Guacamole was founded 2017-11-14 (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:
- Corentin Soriano was added to the PMC on 2026-05-20
- No new committers. Last addition was Stephen Schiffli on 2026-04-06.
## Project Activity:
The project has been dealing with an influx of AI slop, but is otherwise
making progress towards 1.6.1, and tooling for applying updates automatically
is being developed to remove roadblocks from future releases. Releasing 1.6.1
is _the_ current priority.
- 1.6.0 was released on 2025-06-22.
- 1.5.5 was released on 2024-04-05.
- 1.5.4 was released on 2023-12-07.
## Community Health:
The community continues to be active and healthy. There has been no noteworthy
increase nor decrease in activity, with contributions and mailing list
activity continuing at normal levels.
-----------------------------------------
Attachment AH: 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 (17 years ago)
There are currently 249 committers and 126 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Cheng Pan was added as committer on 2026-04-11.
## Project Activity:
3.5.0 was released on 2026-04-02.
3.4.3 was released on 2026-02-24.
3.4.2 was released on 2025-08-28.
hadoop-thirdparty-1.4.0 was released on 2025-03-27.
3.4.1 was released on 2024-10-18.
## Community Health:
Overall, Hadoop remained healthy and active during 26Q2. The trunk branch
received 87 commits from approximately 37 contributors, with activity spanning
Common, HDFS, YARN, MapReduce, cloud storage connectors, security
dependencies, CI, and release maintenance.
Based on commit distribution, Common, HDFS, cloud storage connectors,
and CI were among the more active areas this quarter. The project continued to
invest in feature evolution, stability fixes, security maintenance, and build
infrastructure modernization.
- Release / Documentation
The project completed Hadoop 3.5.0 post-release maintenance, including updates
to release notes, changelog, API comparison files, and the project site
landing page. These updates support release documentation and compatibility
validation [1].
- CI / Build / GitHub Actions
The project continued improving its GitHub Actions build and test
infrastructure. Work included adding build workflows, enabling unit tests,
introducing CodeQL scanning, improving the website workflow, using image
caching to speed up CI, and adding S3A integration and scale tests to CI
coverage. Several flaky tests and build issues were also fixed, improving CI
stability [2][3].
- Security / Dependency Maintenance
The community continued security and dependency maintenance, including
upgrades to Netty, Jackson, Bouncy Castle, Log4j, Mina, zstd-jni, Maven, and
OWASP dependency-check. GitHub Actions security scanning and related
documentation were also improved [4][5].
- HDFS
HDFS work focused on stability and reliability. Key areas included follow-up
improvements for Router async RPC, NameNode edit log rolling controls,
DataNode error handling fixes, EC write reliability, block reader cleanup,
block location handling, and improved determinism for disk error tests [6][7].
- YARN
YARN activity focused mainly on stability and REST API fixes, including
ResourceManager REST JSON serialization support for RMQueueAclInfo. The
quarter also included fixes around NodeAttributesManager concurrent
modification handling [8].
- MapReduce
MapReduce work focused on security and RPC modernization, including task-level
security enforcement and migration of TaskUmbilicalProtocol to
ProtobufRPCEngine2 [9].
- Common / RPC / Compression
Common continued lower-level infrastructure improvements, including
removal of WritableRPCEngine, migration of MiniRPCBenchmark to
ProtobufRpcEngine2, enhanced find command expressions, replacement of native
Zstandard C bindings with zstd-jni, multi-threaded ZStandardCodec compression
support, and fixes for JDiff under Java 17 [10].
- Cloud Storage / ABFS / S3A / Vectored IO
Cloud storage connectors remained active, especially ABFS, S3A, and vectored
IO. Work included ABFS vectored read support, namespace detection fixes,
improved authentication and SAS token error diagnostics, hflush/close behavior
fixes, S3A classloader test coverage, and Local FileSystem vectored IO metrics
fixes [3][5].
Related Issues:
[1] https://issues.apache.org/jira/browse/HADOOP-19814
[2] https://issues.apache.org/jira/browse/HADOOP-19858
[3] https://issues.apache.org/jira/browse/HADOOP-19877
[4] https://issues.apache.org/jira/browse/HADOOP-19919
[5] https://issues.apache.org/jira/browse/HADOOP-19913
[6] https://issues.apache.org/jira/browse/HDFS-17909
[7] https://issues.apache.org/jira/browse/HDFS-17924
[8] https://issues.apache.org/jira/browse/YARN-11956
[9] https://issues.apache.org/jira/browse/MAPREDUCE-7523
[10] https://issues.apache.org/jira/browse/HADOOP-19864
-----------------------------------------
Attachment AI: 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: None
## Membership Data:
Apache HBase was founded 2010-04-21 (16 years ago)
There are currently 114 committers and 61 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 Nihal Jain on 2025-02-02.
- No new committers. Last addition was Xiao Liu on 2026-03-12.
## Project Activity:
hbase-thirdparty-4.1.14 was released on 2026-06-22.
2.5.15 was released on 2026-06-09.
2.6.6 was released on 2026-06-09.
3.0.0-beta-2RC0 is open for voting now.
https://lists.apache.org/thread/7cppkx9wogxps3mwfhlctd7f3d0zflkl
We had finished the Junit5 migration.
https://issues.apache.org/jira/browse/HBASE-23671
We added an AGENT.md for better integrating LLM based tools and HBase.
https://issues.apache.org/jira/browse/HBASE-30173
## Community Health:
- dev@hbase.apache.org:
964 subscribers(968 in the previous quarter)
467 emails sent to list(471 in the previous quarter)
- user@hbase.apache.org:
1974 subscribers(1976 in the previous quarter)
6 emails sent to list(28 in the previous quarter)
- user-zh@hbase.apache.org
83 subscribers(82 in the previous quarter)
4 emails sent to list(12 in the previous quarter)
- JIRA activity:
219 issues opened in JIRA, past quarter
202 issues closed in JIRA, past quarter
We finally started the release process for 3.0.0-beta-2, and will start the
release process for 3.0.0-GA soon after 3.0.0-beta-2 is out. This is the next
major version for HBase.
-----------------------------------------
Attachment AJ: 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: No
## Membership Data:
Apache HertzBeat was founded 2025-08-20 (10 months ago)
There are currently 30 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Qiwei Zheng on 2025-10-04.
- No new committers. Last addition was Ziqiu Guo on 2025-12-08.
## Project Activity:
Added 7 new contributors. New features are currently under development.
## Community Health:
In the past month, 11 authors have pushed 12 commits to master and 129 commits
to all branches. We are actively attracting more production users and
contributors by improving doc, enhancing stability and strengthening features.
-----------------------------------------
Attachment AK: Report from the Apache Hive Project [Naveen Gangam]
## Description:
The Apache Hive™ data warehouse software facilitates reading, writing, and
managing large datasets residing in distributed storage (Apache Hadoop) using
SQL.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hive was founded 2010-09-22 (16 years ago)
There are currently 114 committers and 59 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 Shohei Okumiya on 2025-12-08.
- No new committers. Last addition was Wechar Yu on 2026-03-30.
## Project Activity:
Apache Hive 4.2.0 was released on 2025-11-23.
There are ongoing discussions about 4.3.0 but there is no exact timeline in
place cause the community is trying to converge on what features should land
before making the release.
During the last quarter, the Apache Hive project focused heavily on advancing
its integration with Apache Iceberg, adding features such as support for
logical views, Parquet DECIMAL_64 vectorization, multi-table multi-statement
transactions, and Iceberg V3 specification updates including column defaults
and row lineage.
Significant enhancements were made to containerization and ecosystem
deployment, introducing a dedicated Kubernetes Operator with multi-tenancy and
auto-scaling alongside specialized, nightly Docker images for Tez AM, LLAP,
and Ozone.
The development team also prioritized performance optimizations, resolving
numerous vectorization bugs, improving histogram-based selectivity estimation
in the Cost-Based Optimizer (CBO), and streamlining the Hive Metastore by
refactoring modular stores and partitioning logic.
Finally, infrastructure and operational security were reinforced with the
addition of SSL auto-reloading for the HiveServer2 WebUI , the integration of
SSL inclusion protocols and cipher suites for the Hive Metastore and HTTP
modes , and routine dependency updates for log4j , Jackson , and OpenTelemetry
(OTEL).
## Community Health:
The dev@hive.apache.org had a 56% decrease in traffic in the past quarter (29
emails compared to 65). Nothing worrisome here as apart from release planning
the dev list is not used much.
The issues@hive.apache.org had a 18% increase in traffic in the past quarter
(1246 emails compared to 1049). Most of the development activity happens under
Jira tickets so 1K emails on the issues list is normal.
The user@hive.apache.org had a 48% decrease in traffic in the past quarter (10
emails compared to 19). The activity is always low in this list since users
actively using Hive are opting to create Jira tickets directly.
-----------------------------------------
Attachment AL: Report from the Apache HugeGraph Project [Jermy Li]
# HugeGraph project board report
## Description:
Apache HugeGraph is a full-stack graph database system, providing complete
graph data processing capabilities, include large-scale graph storage,
real-time querying, offline analysis, and graph AI. Supporting both Gremlin
and Cypher query languages.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache HugeGraph was founded 2026-01-21 (6 months ago).
There are currently 22 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is about 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was PPMC Member Yuchen Ding on 2024-12-18.
- No new committers. Last addition was Zhe Wang on 2025-09-01.
## Project Activity:
The HugeGraph release cycle is now 6 to 12 months,
and a new version is expected to be released in 2026.
- 1.7.0 was released on 2025-11-28.
Last month, we were preparing 1.8.0 release -- the first release after
graduation. we supported the docker deployment of distributed storage version,
and completed the enhancement of hugegraph-AI module. We expect to complete
1.8.0 release next month.
## Community Health:
Mail list dev@hugegraph.apache.org had a 23% decrease in traffic in the past
quarter (108 emails compared to 141).
The number of commits commits@hugegraph.apache.org increased by 42% in the
past quarter (240 commits compared to 169).
Last quarter, we were preparing gsoc and its proposal. and communicating with
a contributor in Europe to give a speech at ApacheCon 2026 Glasgow.
-----------------------------------------
Attachment AM: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for July 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 27 podlings under incubation. In June, the Incubator
made two releases, and some release votes are currently underway. There
were two additions and no removals to IPMC membership.
Mailing list discussion focused primarily on release voting activity and
two graduation discussions: a vote to graduate Apache Fluss is currently
underway, and an early discussion on graduating Apache ResilientDB has
begun on the general list. A new podling, Ossie, a data semantic
specification and framework, was accepted into the Incubator. Three project
did not report in time and will be asked to report next month.
During the Fluss graduation discussion, significant concerns were raised
about the composition of the proposed PMC, which largely reflected work
done prior to donation and contributors' company titles rather than merit
earned during incubation. After considerable discussion and encouragement
from the IPMC, this was resolved before the vote was called. Apache Fluss'
graduation vote has passed, and a board resolution to graduate has been
posted.
Caldera is showing very low mailing-list and code activity, and a slow
incubator start.
Casbin has 249 GitHub repositories, which is highly unusual for a podling.
The podling's response to questions about IP clearance conflated ICLA
signing with software grants, and it is not clear that proper software
grants have been completed for all repositories. The IPMC is following up.
Baremaps was retired in March 2026. Some post-retirement cleanup is still
outstanding.
OpenServerless has not yet made an ASF release despite over two years of
incubation. The IPMC has significant concerns about the project and is
discussing whether retirement is appropriate.
OzHera released version 2.2.6-incubating in June, addressing the concern
raised last month.
PouchDB has yet to correct the redirection of the legacy pouchdb.com site.
Toree has been incubating since December 2015. There was no dev list
activity in June. A new release candidate was being prepared in May but
there has been no visible progress since.
Pony Mail, which has been incubating since 2016, intends to start
graduation discussions.
The IPMC continues to monitor long-running podlings and will follow up on
any community concerns as needed.
All submitted reports have mentor signoff.
## Community
### New IPMC members:
- Danica Fine
- Russell Spitzer
### People who left the IPMC:
- none
## New Podlings
- Ossie
## Podlings that failed to report, expected next month
- Amoro
- HugeGraph
- Pegasus
## Graduations
- none
The board has motions for the following:
- none
## Releases
The following releases entered distribution during the month of
June:
- GeaFlow 0.8.0
- OzHera 2.2.6
## IP Clearance
- none
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[Caldera](#caldera)
[Casbin](#casbin)
[Fluss](#fluss)
[PonyMail](#ponymail)
[ResilientDB](#resilientdb)
--------------------
## 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. Community Growth
2. Grow the PPMC
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
Petitioned for an additional PPMC member; in process of vetting and voting
on them.
Github Stars are over 7.1k.
### How has the project developed since the last report?
9 new pull requests were opened on the GitHub repo.
### 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.
### When were the last committers or PPMC members elected?
At founding/incubation.
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Still working to update third-party references and branding references,
including documentation and website references as well as plugin repository
mentions and references.
### Signed-off-by:
- [ ] (caldera) Kevin Ratnasekera
Comments:
- [ ] (caldera) Francis Chuang
Comments:
- [X] (caldera) PJ Fanning
Comments: Mailing list traffic is close to non-existent. Git commit
activity is minimal. No sign of any momentum.
- [ ] (caldera) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## Casbin
Casbin is a powerful, efficient open-source access control framework that
provides a unified, model-driven approach to authorization. Built on the
PERM (Policy, Effect, Request, Matchers) metamodel and its domain-specific
language, Casbin brings ACL, RBAC, and ABAC together under one model so that
policies can be expressed flexibly and enforced at a fine-grained level. It
offers high-performance enforcement and a broad multi-language ecosystem
spanning Go, Java, Node.js, Python, .NET, C++, and Rust.
Casbin has been incubating since 2026-02-07.
### Three most important unfinished issues to address before graduating:
1. Complete the first official Apache incubating release.
2. Clarify repository scope, release plans, and IP/grant coverage for the
large set of Casbin repositories under the Apache GitHub organization.
3. Continue building a diverse, public, mailing-list-centered community and
keep project decisions visible on dev@casbin.apache.org.
### Are there any issues that the IPMC or ASF Board need to be aware of?
The podling is clarifying repository scope, IP/grant coverage, and release
policy expectations for its 249 GitHub repositories. This includes deciding
which repositories are intended for ASF releases, which should be archived,
and how current GitHub snapshot releases should be handled under ASF
release policy.
No board action is requested at this time. The discussion is happening on
the public dev list with mentor involvement.
### How has the community developed since the last report?
- dev@ had 10 messages across 3 threads, with 8 participants.
- The main public discussion was about repository scope, IP/grant coverage,
archive decisions, and ASF release policy for snapshot artifacts.
- The community has also moved the first Apache Casbin release review onto
the public dev list. This first RC is for the Go core repository
apache/casbin; Apache Casbin 3.11.0-incubating RC1 is currently in the dev@
release vote and review stage.
- The main apache/casbin repository reached about 20.2k GitHub stars.
### How has the project developed since the last report?
- Across the tracked Casbin Apache GitHub repositories, there were 3 merged
PRs and 5 closed issues from 2026-06-01 to 2026-06-28.
- Main repository work focused on CI workflow cleanup, README updates, CSV
policy persistence, and temporal-role behavior fixes.
- Ecosystem maintenance included casbin-ex crash handling, jCasbin keyGet3
support, Casbin.NET KeyMatch5 compatibility, and node-casbin Node/Vite
import and release automation issues.
- The first official Apache release moved from preparation to the RC review
stage for the Go core repository, apache/casbin.
### How would you assess the podling's maturity?
The podling has completed initial setup and is actively working through
release preparation and public governance questions. It is not yet nearing
graduation.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No official Apache release yet.
### When were the last committers or PPMC members elected?
2026-02-07
### Have your mentors been helpful and responsive?
Yes, mentors have been helpful and responsive. Mentors have helped with
reporting and have participated in governance and release-policy
discussions.
### Is the PPMC managing the podling's brand / trademarks?
The project name has been approved in PODLINGNAMESEARCH-251. The PPMC is
continuing to review release, website, and repository materials for Apache
branding and trademark requirements.
### Signed-off-by:
- [ ] (casbin) Hao Ding
Comments:
- [X] (casbin) Huajie Wang
Comments:
- [X] (casbin) Hulk Lin
Comments:
- [ ] (casbin) Jerry Shao
Comments:
- [X] (casbin) Zili Chen
Comments:
### IPMC/Shepherd notes:
None
--------------------
## Fluss
Fluss is a streaming storage built for real-time analytics which can serve
as the real-time data layer for Lakehouse architectures.
Fluss has been incubating since 2025-06-04.
### Three most important unfinished issues to address before graduating:
None. Earlier graduation-readiness concerns raised during the discussion
on general@incubator have been addressed. In particular, the PPMC has
refreshed the proposed PMC roster through a structured review and formal
vote, including only active members with governance contributions during
incubation, adding active committers to the proposed PMC, and confirming
forward-looking governance commitments.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time. The concerns raised during the graduation discussion
have been resolved or adopted, including the proposed PMC roster review,
download page verification improvements, release/disclaimer updates,
Docker Hub and Maven POM description updates, and branding/documentation
corrections.
### How has the community developed since the last report?
1. Elected 1 new committer: Anton Borisov.
2. Held regular [Monthly Community
Calls](https://s.apache.org/fluss-community-call)
in April, May. (June was postponed to 3rd July)
3. Participated in [Google Summer of Code
2026](https://summerofcode.withgoogle.com/programs/2026/projects/D5s5f4un)
through the Fluss project and mentored a GSoC contributor.
4. Community presentations and outreach continued:
- [Flink Forward Asia 2026](https://asia.flink-forward.org/) was held
on June 26-27 in Shenzhen, China, with many Fluss-related talks.
- OpenXData 2026 included Fluss talks and panels, including a Fluss
presentation by Mehul Batra and a community panel involving Yuxia Luo
from the Fluss PPMC.
- Anton Borisov presented a Fluss talk at a Data Streaming meetup in
London on May 7.
### How has the project developed since the last report?
- Released Apache Fluss 0.9.1-incubating on 2026-05-04. Apache Fluss 0.9.1
is currently the latest stable release.
- Completed the Apache release of fluss-rust 0.1.0-incubating, the first
official Rust, Python, and C++ client release for Apache Fluss.
- Completed the Fluss website redesign.
- Continued development toward Apache Fluss 1.0.0, including real-time AI
use cases, real-time lakehouse integrations, streaming analytics,
client SDKs, and security improvements.
- Published more technical and user-facing content, including articles on
pruning, real-time deduplication, Taobao Instant Commerce, storage
hierarchy, and tiering service operations.
### How would you assess the podling's maturity?
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
Commentary: The project has established a regular Apache release cadence
and has completed the maturity model. As summarized in the graduation
discussion, the community has 20 committers including mentors, from more
than 8 companies, with 14 PPMC members and 121 contributors. During
incubation, Fluss made 5 releases in 11 months with 4 different release
managers, and reported 10+ known production users. The project has opened
1,533 issues with 1,041 resolved, and 1,796 PRs with 1,551 merged or
closed. The PPMC has also refreshed the proposed PMC roster through a
structured review and formal vote, adding active committers to the
proposed PMC and confirming forward-looking governance commitments.
### Date of last release:
2026-05-04 (Apache Fluss 0.9.1-incubating)
### When were the last committers or PPMC members elected?
The most recent committer was Anton Borisov, elected in May. No new
PPMC member has been elected since the April report. Two existing
committers, Anton Borisov and Keith Lee, have been included in the
updated proposed PMC roster for graduation.
### Have your mentors been helpful and responsive?
Yes. The mentors have been helpful and responsive. The mentors provided
guidance during the graduation discussion, including on the proposed PMC
roster review and graduation-readiness follow-up items. No open issues at
this time.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The PPMC is actively managing the Apache Fluss (Incubating) brand and
trademarks. The PPMC has fixed several branding issues related to external
blogs and content, including pages on Alibaba Cloud and Ververica
websites.
During the graduation-readiness follow-up, the community also updated the
download page, release notes, Docker Hub descriptions, Maven POM
description, and related documentation/disclaimer text. There are no known
open brand or trademark issues at this time.
### Signed-off-by:
- [X] (fluss) Jean-Baptiste Onofré
Comments: The vote to graduate passed. The resolution proposal for
the board can be added.
- [X] (fluss) Becket Qin
Comments: Glad to see the project passing the graduation voting and
ready to become a new TLP!
- [X] (fluss) Yu Li
Comments: We had a constructive discussion on graduation and the vote
has passed with the updated PMC roster afterwards. I will submit the
resolution for the next board meeting.
- [ ] (fluss) Jingsong Lee
Comments:
- [X] (fluss) Zili Chen
Comments:
### IPMC/Shepherd notes:
--------------------
## PonyMail
Pony Mail is a mail-archiving, archive viewing, and interaction
service, that can be integrated with many email platforms.
Pony Mail has been incubating since 2016-05-27.
### Three most important unfinished issues to address before graduating:
1. Cut the first formal ASF release of the Foal (Python) rewrite.
2. Start the graduation discussion on general@incubator.
3. Migrate the project website to reflect current Foal documentation.
### Are there any issues that the IPMC or ASF Board need to be aware of?
CVE-2026-41873 (critical severity) was published 2026-04-28
disclosing an admin account takeover via HTTP request smuggling in
the legacy Lua implementation. The Lua version is retired and
unsupported; the Python Foal rewrite — which is the active
development line and powers lists.apache.org — is not affected.
This CVE is resolved from the project's perspective.
ASF Infrastructure requested confirmation on the
foal-demo.ponymail.apache.org DNS entry (INFRA-27692). The PPMC
will respond.
### How has the community developed since the last report?
Active contributors this quarter: rbowen, wave (Dave Fisher),
sbp (Sean Palmer), sebb, jmclean (Justin Mclean), Bob Thomson,
Arnout Engelen. Code review activity increased in June with
multiple PRs reviewed and merged collaboratively. The project
continues to benefit from the existing committer base who are
familiar with the codebase and operational deployment at the ASF.
### How has the project developed since the last report?
Significant documentation and code activity this quarter:
Merged PRs:
- #313: API documentation for all Foal HTTP endpoints
- #314: Search query syntax documentation
- #316: Configuration reference for all ponymail.yaml options
- #317: Comprehensive documentation suite (installation,
architecture, operator guide, user guide, admin guide, plugin
guide, API client guide, release process, AGENTS.md)
Open PRs:
- #315: URL-encode search queries in pushState URLs
- #318: Filter stopwords from word-cloud results
- #319: Expanded database schema documentation
Infrastructure:
- sebb fixed CI workflows (pinned Actions, mypy, indentation)
- ASF Infra applied branch protection rulesets to all repos
- Transitioned documentation from ElasticSearch to OpenSearch
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
Commentary: Pony Mail Foal is the production system powering
lists.apache.org for the entire ASF. The codebase is mature,
actively maintained, and has a robust PPMC. The project is
ready to begin the graduation process.
### Date of last release:
No formal ASF release yet. The software is deployed in production
at the ASF from the main branch.
### When were the last committers or PPMC members elected?
The PPMC roster has been stable. Current PPMC (11 members):
humbedooh, wave, jim, johndament, rbowen, rubys, sbp, sebb,
curcuru, pctony, ucb.
### Have your mentors been helpful and responsive?
Yes.
### Are things falling through the cracks? If so, please list any open
issues that need to be addressed.
No. The project intends to start the graduation discussion
following this report.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The Pony Mail name and brand are managed by the PPMC.
No known third-party misuse.
### 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. No issues. VP, Brand has approved the project name.
### Signed-off-by:
- [ ] (ponymail) John D. Ament
- [X] (ponymail) Dave Fisher
### Comments:
### IPMC/Shepherd notes:
We see no reason not to graduate. Thanks Rich for creating this report.
--------------------
## ResilientDB
ResilientDB is a distributed blockchain framework that is open-source,
lightweight, modular, and highly performant.
ResilientDB has been incubating since 2023-10-21.
### Three most important unfinished issues to address before graduating:
1. Graduate
2. Graduate
3. Graduate
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
Add 3 new Committers
### How has the project developed since the last report?
We are precessing the graduation process.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2026-3-10
### When were the last committers or PPMC members elected?
### Have your mentors been helpful and responsive?
JB is very helpful.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here.
### Signed-off-by:
- [ ] (resilientdb) Junping Du
Comments:
- [ ] (resilientdb) Kevin Ratnasekera
Comments:
- [X] (resilientdb) Jean-Baptiste Onofré
Comments: I think the podling is ready to graduate. I will help on
this (sorry for being late on that).
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AN: Report from the Apache InLong Project [Charles Zhang]
# Apache InLong Board Report
## Description
The mission of Apache InLong is the creation and maintenance of software
related to a one-stop data integration framework that provides automatic,
secure, and reliable data transmission capabilities. InLong supports both batch
and stream data processing at the same time, which offers great power to build
data analysis, modeling, and other real-time applications based on streaming
data.
## Project Status
Current project status: Ongoing, with moderate activity.
Issues for the board: There are no issues requiring board attention at this time.
## Membership Data
Apache InLong was founded 2022-06-15 (4 years ago).
There are currently 54 committers and 32 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 Doley Zi on 2025-11-25.
- No new committers. Last addition was Guang Li on 2025-09-05.
## Project Activity
The project is working on 2.4.0, which will be released
in July. The main features and improvements include:
- **SDK**: Transform SDK added multi-ProtoBuf file and nested-type
decode/encode, map node parsing, and List/Struct/Binary field encoding;
introduced `concat_struct`, `extract_struct`, and `extract_binary` functions;
Protobuf SQL alias parsing. DataProxy Go SDK improved worker selection,
connection timeout, and remote-address logging. Python SDK switched to
PEP-517 wheel builds. Common added a Json configuration module.
- **Manager & Security**: Fixed SQL injection and
`/api/cluster/testConnection` and `/api/node/testConnection` vulnerabilities;
added permission checks for streamsource deletion; set
`openapi.auth.enabled` default to `true`; various input-validation,
permission, and audit-query fixes.
- **Audit**: Fixed high-concurrency thread-safety issues; routing data source
now supports domain names; fixed a ClassLoader leak caused by a static
`ScheduledExecutorService` in PulsarSink.
- **Sort**: Fixed an NPE in `SortConfigUtil.checkUpdate` when
`DataFlowConfig.version` is null, which could stall config reload.
## Community Health
The community health looks good overall.
- dev@inlong.apache.org had a 12% increase in traffic in the past quarter
(46 emails compared to 41).
The dev mailing list traffic picked up a bit, and the project is still
undergoing normal iteration and evolution, with a slight rebound.
-----------------------------------------
Attachment AO: Report from the Apache James Project [Benoit Tellier]
## Description:
The Apache James Project delivers a rich set of open source modules and
libraries, written in Java, related to Internet mail which build into an
advanced extensible mail server running on the JVM.
## Project Status:
Current project status: Ongoing
Issues for the board: No specific issue requires the board attention
## Membership Data:
Apache James was founded 2003-01-22 (23 years ago)
There are currently 43 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was René Cordier on 2025-02-03.
- No new committers. Last addition was Quan Tran on 2025-02-05.
## Project Activity:
Recent releases:
JAMES-3.9.0 was released on 2025-10-03.
MIME4J-0.8.13 was released on 2025-07-25.
JDKIM-0.4 was released on 2025-03-04.
The project will soon release a set of minor versions corrections
for the Apache James project/
## Community Health:
We saw a decrease from the activity on our main development mailing list:
server-dev@james.apache.org had a 38% decrease in traffic in the past
quarter
(155 emails compared to 247)
Appart than this, the activity is stable.
The PMC identified recurring contributors and plan to propose them to become
comitter.
-----------------------------------------
Attachment AP: 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 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Arne Bernhardt on 2024-04-05.
- No new committers. Last addition was Øyvind Gjesdal on 2026-01-26.
## Project Activity:
The project released Apache Jena 6.1.0 on 2026-05-11. The theme was updating
RDF 1.2 so that uses could try out an implementation of the nearly-finished
standard.
Over the last year or so, release votes have taken more than 3 days. Had it
not been for some email address confusion, this time there would have been the
necessary votes in the usual 3 day window.
We are grateful for the input from security@ which has enabled the project to
refine and merge a security threat model.
## Community Health:
The users email list has seen only one new thread this quarter. Questions and
issue reports are almost entirely on github issues.
The issues@GH has been steady - a 9% decrease in traffic in the past quarter
(176 emails compared to 192).
pr@GH has seen several fixes and also help from a new contributor with
upgrading to the geospatial extension GeoSPARQL. geospatial is an area that
has it's own expertise and the code is now user community maintained.
-----------------------------------------
Attachment AQ: Report from the Apache JMeter Project [Bruno (Milamber) Demion]
## Description:
The mission of JMeter is the creation and maintenance of software related to
Java performance and functional testing
## Project Status:
Current project status: Ongoing, with low activity
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache JMeter was founded 2011-10-26 (14 years ago)
Jakarta JMeter, first version was released 1998-12-15 (28 years ago)
There are currently 13 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Vladimir Sitnikov on 2018-06-08.
- No new committers. Last addition was Maxime Chassagneux on 2017-02-15.
## Project Activity:
- Current (low) objective is to move the code base of JMeter to Java 17+
(from Java 8) for next major release (6.0)
- We have start a discuss to include (or not) some telemetry options
inside JMeter code to have some usage stats from users.
- We have an active discussion (on dev@) to use the new TLP Apache Magpie
project to JMeter, the hope that Magpie can help to manage the issues,
increase activities on JMeter. (This is related with the last report)
- Recent releases:
5.6.3 final was released on 2024-01-07.
## Community Health:
- The project has a low activity during last quarter.
-----------------------------------------
Attachment AR: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AS: 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.
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.4 was released 2026-04-02
- work on 2.12.5 is on going to mitigate additional CVEs
- work on 3.0.0 is on going and should be before end of the year.
## Community Health:
- dev@jspwiki.apache.org had a 90% increase in traffic in the past
quarter (103 emails compared to 54)
Most of this is due to going discussions on security related
reports
-----------------------------------------
Attachment AT: 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:
- Ashwani Raina was added to the PMC on 2026-06-29
- Martonka Zoltan was added to the PMC on 2026-06-29
- Ashwani Raina was added as committer on 2026-06-26
- Martonka Zoltan was added as committer 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 increased
(43 vs 58) and the number of unique developers is constant.
- Traffic to dev mailing lists is constant while traffic to issues and
reviews mailing lists has increased by 30%.
- Community activity measured in community Slack is as follows: the
number of weekly active users increased by 14%, and weekly public
posters dipped by 8%.
- Technical highlights:
- Major work done in prometheus to improve observability.
- The core engine became faster and more reliable: the RPC layer, LBM storage
startup, compaction accounting, and the auto-rebalancer all saw significant
performance and correctness improvements.
- Security improvements: TLS support for HMS/Thrift and third party
dependencies were updated to address CVEs.
-----------------------------------------
Attachment AU: Report from the Apache Livy Project [Jean-Baptiste Onofré]
## Description:
The mission of Apache Livy is the creation and maintenance of software related
to web service that exposes a REST interface for managing long running Apache
Spark contexts in your cluster. With Livy, new applications can be built on top
of Apache Spark that require fine grained interaction with many Spark contexts
## Project Status:
Current project status: Ongoing (first report as Top-Level Project)
Issues for the board: none
## Membership Data:
Apache Livy graduated from the Apache Incubator on 2026-06-04 (incubating
since 2017-06-05).
There are currently 25 committers and 21 PMC members in this project. The
Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter: Initial PMC and committer roster established
at graduation from the Apache Incubator.
## Project Activity:
- Apache Livy 0.9.0-incubating was released on 2026-01-09: this was the final
release made during the incubation period, providing Spark 3.x support
(Spark 3.0+ required) and binary distributions for Scala 2.11 and 2.12.
- The graduation resolution was submitted to the board by JB Onofré following
a successful IPMC vote (7 binding +1, 1 non-binding +1).
- Apache Livy is now a Top-Level Project, announced by the ASF on 2026-06-04.
- The PMC is planning the first TLP (1.0) release to remove the -incubating
suffix from artifact names and align the release infrastructure with TLP
requirements. Discussion is ongoing on the dev@ mailing list.
## Community Health:
- The dev@ and user@ mailing lists are active with discussions around the
post-graduation release roadmap and ongoing user support.
- The PMC is working on updating the project website and documentation to
reflect TLP status.
- Repository migration from apache/incubator-livy to apache/livy is in
progress.
- The community is focused on growing the contributor base beyond the existing
incubation community now that the project has full TLP visibility.
-----------------------------------------
Attachment AV: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AW: Report from the Apache MADlib Project [Ed Espino]
-----------------------------------------
Attachment AX: Report from the Apache Magpie Project [Jarek Potiuk]
## Description:
Apache Magpie is responsible for the creation and maintenance of software
related to agent-assisted repository maintainership and development —
including issue and pull-request triage, contributor mentoring, agent-drafted
remediation, developer-side development-cycle skills, and narrowly-scoped
fix-and-merge automation. Magpie is deliberately governance-agnostic: it is
built to be adopted by ASF projects and by non-ASF open-source projects alike,
with no ASF-only assumption baked into the install path.
## Project Status:
### Status:
New Top-Level Project, established directly by Board resolution (not via the
Incubator). Status: ongoing, high activity — in the bootstrapping phase. The
project is standing up its infrastructure and framework, onboarding its
founding PMC, and preparing its first Apache release. No issues require Board
attention at this time.
* Established: 2026-06-17 (name confirmed via PODLINGSEARCH during the 8–12
May 2026 naming discussion).
* PMC: 22 members at establishment.
* Chair: Jarek Potiuk.
* No committers or PMC members have been added or removed since establishment
(project is newly formed).
* Diversity: the founding PMC spans a broad set of ASF projects (Airflow,
Arrow, Iceberg, Polaris, Groovy, Grails, Superset, Beam, Pulsar,
Log4j/Logging Services, Mahout, Doris, Geode, Accumulo, HBase, Lucene/Solr,
Tomcat, ComDev, Incubator, Security, Training) and multiple organisational
affiliations, with no single employer holding a majority — a deliberate
design goal given the contributor-data surface the project touches.
* There are first new adopters discussing Magpie Adoption (Apache JMeter in
the ASF, but also we have a discussion with Eclipse Foundation Leadership
and we have active discussions with Python Software Foundation - and in the
week of 13-19 of July at Europython we are planning to work with release
managers and triagers of Python to help them to adopt Magpie and possibly
expose their SKILLs via trusted 3rd-party mechanism of Magpie.
### Issues for the board:
The announcement of Apache Magpie triggered immediate adoption interest
aligning perfectly with our core mission. This momentum extends well beyond
the ASF; we are seeing active usage and contributions from independent
maintainers, alongside formal interest from both the Python Software
Foundation and the Eclipse Foundation.
This "grass-roots" pull comes from maintainers seeking to reclaim their time
through Magpie's automation. While this outreach intersects with broader
initiatives like RAI, the PMC views this as project-specific work addressing
universal OSS maintainership challenges. We intend to continue these
cross-organizational collaborations—engaging Marketing & Publicity should they
evolve into formal public partnerships—to ensure Magpie remains a
governance-agnostic solution for the entire ecosystem.
Question to the board:
Does the Board have any objections to the PMC pursuing these relationships
with other open-source organizations, or do you have any other expectations or
constraints regarding them?
### Releases
* No releases yet. The project has made no Apache release to date
* The first release, Apache Magpie 0.1.0, is being run
https://lists.apache.org/thread/4cxf84q5vwxd85dj5yx6vhj2bzr46111.
* Magpie intended to cut its releases through the Apache Trusted Releases
(ATR) platform (ASF Tooling) with traditional manual release process as
fallback - dogfooding its own release process, which turned out to be good
idea as we could fallback to manual process when ATR hit some
un-workaroundable issues.
* Releasing Magpie using release SKILS in Magpie is a fantastic way to
dog-food what we are doing and shows the true value of Magpie - the whole
release process was generally following “release Magpie” Agentic command -
with conversational interface guiding release manager - including automated
installation of dependencies, generating keys etc. It was as easy as
following the instructions of the agent.
## Membership Data:
Apache Magpie was founded 2026-06-17 (22 days ago)
There are currently 22 committers and 22 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:
Since establishment the project has focused on infrastructure and framework
build-out:
* Repository and framework. github.com/apache/magpie is stood up with the
skills framework, contributor documentation, and CI. The framework ships as
reusable "skills" a project adopts via a snapshot-based adoption mechanism,
with per-adopter and per-user configuration layers and a strict
human-in-the-loop state-change discipline (the agent drafts; the human
acts).
* Magpie Website reflecting Maintainer focus and agreed Taxonomy Targeted to
maintainers who are main audience for Magpie has been published - promotion
of the “Give maintainers time back” theme is happening in various media to
attract contributors: https://magpie.apache.org/
* Skill families in place across the project's agentic modes: security-issue
handling (intake → triage → CVE allocation → fix → disclosure), release
management (full lifecycle, both svnpubsub and ATR backends), PR management
(triage, review, quick-merge, stats), issue management (triage,
deduplication, reproduction, stale sweeps), contributor/committer
(nomination, activity, onboarding), and audit (CI-runner, dependency,
license-compliance, flaky-test).
* Pilots. Onboarding friendly pilot projects — an ASF PMC running the full
security-issue flow (Apache Airflow, Apache Groovy, Apache Burr, Apache
JMeter)
* Trusted-release collaboration. Working with the ASF Tooling team on the ATR
platform, adopting it for Magpie's own first release as an early real-world
test.
* Vendor neutrality - discussions started on vendor neutrality of the project
being aspirational vs. achieved - this resulted in implementing components
and defining contracts that allow Magpie to claim Vendor neutrality status.
Vendor neutrality is automatically assessed at
https://magpie.apache.org/#vendor-neutrality The current state: 10/10
Capability contracts 100% work across 2+ vendors 69/69 Skills carry no
vendor lock-in 22/22 Agent harness 100% harness-neutral
* Organization agnosticism - discussions started with Python Software
Foundation and Eclipse Foundation on a way for Magpie to become a way to
also distribute other organization skills via trusted skills
https://magpie.apache.org/#organisation-agnostic
## Community Health:
Healthy for a project at this stage. Development activity is high (framework
and skill build-out proceeding steadily); the PMC is engaged and drawn from
experienced ASF contributors with a bias toward developer-experience and
community-development work.
Mailing lists (dev@, private@, commits@) and GitHub Issues are active for
coordination. The immediate community-building priorities are landing the
first release, converting pilot usage into external adopters, and beginning to
grow committership beyond the founding grant.
We have a great deal of contributions - mainly from involved founding team
members. Jarek Potiuk, Justin McLean - who both happen to have more time to
dedicate for Magpie - are most active contributors. However we make an effort
to get more feedback from other founding team members in the decision making
process and project daily operations - we also have founding team members
contributing and new, individual contributors who contribute occasionally.
We have active discussion on Slack #magpie channel created on ASF slack, and
we are discussing about adding extra channels (Discord) for ad-hoc discussions
and ASF slack adds friction in adding non-ASF community members - that have to
be personally invited and approved as guests, we want to make sure we are as
open as inclusive as possible to all kinds of organizations and individuals -
in- and out- of ASF.
The “Mischief Makers” is a term we seem to be coining to name community
members - which seems a pretty natural choice.
Thanks to Agentic assistance it progresses very fast - we have now 10
contracts, 5 substrates, 69 skills, 45 tools, 9 skill families that are ready
to serve Maintainers all-around globe.
-----------------------------------------
Attachment AY: Report from the Apache Mahout Project [Shannon Quinn]
## Description:
The mission of Mahout is scalable matrix math
## 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 34 committers and 12 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 Jie-Kai Chang on 2026-04-07.
- No new committers. Last addition was Jie-Kai Chang on 2026-01-26.
- PMC member Trevor Grant has changed his status to PMC Emeritus.
## Project Activity:
Apache Mahout continued its renewed development activity during Q2 2026, with
Qumat and QDP remaining the project’s primary focus.
The project released Apache Mahout Qumat 0.6.0 on 2026-05-31, following the
Qumat 0.5.0 release on 2026-02-02. The release included 111 pull requests
since the previous version and represented an important step toward reducing
GPU vendor lock-in for QDP by adding first-class AMD ROCm support alongside
the existing NVIDIA CUDA path.
During the reporting period, the project improved QDP’s GPU backend support,
data-loading pipeline, encoding performance, benchmark coverage,
documentation, packaging, and build reliability. Development also continued
after the release with further reader and pipeline improvements, CUDA runtime
hardening, API documentation generation, Trusted Publishing setup, website
validation, and ongoing dependency and security maintenance.
## Community Health:
Mahout remains in a strong community health position. The ASF Reporter
community health score is 9.60, marked “Super Healthy”. Development activity
remained high across code, documentation, release engineering, CI, and the
website, with continued participation from PMC members, committers, and
non-committer contributors.
Mailing list activity decreased compared with the previous quarter, but this
should be interpreted with context. As of 2026-07-04, dev@mahout.apache.org
had 26 emails in the past quarter compared with 1,158 in the previous quarter,
a 98% decrease. issues@mahout.apache.org had 201 emails compared with 502, a
60% decrease.
The large decrease in dev@ traffic appears to be primarily due to a reduction
in notification-style noise rather than a loss of project momentum. In the
previous quarter, dev@ included a large volume of GitHub-related
notifications, including pull requests, issues, and PR comments. As that noise
decreased or moved away from the main discussion flow, the reported dev@
volume became much lower and more reflective of actual human discussion.
This decrease therefore appears to reflect a normalization of mailing list
traffic after an unusually noisy previous quarter around project rejuvenation
and release activity. Q2 still included a major release, active post-release
development, website and documentation work, CI improvements, packaging and
release engineering work, and continued dependency and security maintenance.
-----------------------------------------
Attachment AZ: Report from the Apache Maven Project [Hervé Boutemy]
-----------------------------------------
Attachment BA: 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 28 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Gary D. Gregory on 2023-09-13.
- No new committers. Last addition was Gary D. Gregory on 2022-03-24.
## Project Activity:
* Apache MINA: an asynchronous I/O library. Mature & stable. Multiple patch
releases this quarter to address reported vulnerabilities. Latest releases
were 2.2.9 on 2026-06-19 and 2.0.31 and 2.1.15 on 2026-06-27. The project
had submitted an AI-driven vulnerability analysis, of which the results
with some 41 findings (some already dealt with before) came in late in May.
Currently busy analyzing and addressing findings.
* Apache MINA SSHD: library for client- and server-side SSH. The project
is mature & stable and is under active development. Two new releases
this quarter: 2.18.0 and 3.0.0-M4 on 2026-05-28. New patch releases 2.19.0
and 3.0.0-M5 to address some reported vulnerabilities (all moderate) are in
preparation.
* Apache MINA FtpServer: FTP server library. Project in maintenance
mode; low activity.
* Vysper & AsyncWeb are dormant.
## Community Health:
Our community is healthy but small. Interactions are polite, professional, and
usually timely. Projects use both Github and JIRA for issue tracking.
Of our 15 PMC members only about 6 are really active. This can sometimes delay
release votes since not everybody always is available to vote within a few days
(vacations, other obligations, whatnot). Also, analyzing, responding to, and
resolving vulnerability reports can quickly consume all available human
resources.
Both MINA and MINA SSHD got a few good code contributions from external
contributors via Github.
-----------------------------------------
Attachment BB: Report from the Apache MyFaces Project [Bernd Bohmann]
## Description:
The mission of MyFaces is the creation and maintenance of software related to
JavaServer(tm) Faces implementation and components
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: None
## Membership Data:
Apache MyFaces was founded 2005-02-23 (21 years ago)
There are currently 81 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Melloware on 2024-01-25.
- No new committers. Last addition was Milan Siebenbürger on 2024-01-24.
## Project Activity:
The myfaces community is working on performance improvements,
javascript fixes and spec updates.
Tobago is working on small features and playwright updates.
Recent releases:
- tobago-6.11.0 was released on 2026-05-16.
- myfaces-core-4.1.3 was released on 2026-05-05.
- tobago-6.10.0 was released on 2026-03-30.
## 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 BC: Report from the Apache Mynewt Project [Szymon Janc]
-----------------------------------------
Attachment BD: 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 NAR Maven Plugin is an extension for Apache Maven supporting
NiFi Archive creation for runtime isolated class loading.
Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
integrate with and leverage the command and control of NiFi. There are both
Java and C++ implementations.
Apache NiFi Registry is a centralized registry for key configuration items
including flow versions, assets, and extensions for Apache NiFi and Apache
MiNiFi.
## 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 55 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.
- No new committers. Last addition was Shane Ardell on 2025-11-21.
## Project Activity:
Apache NiFi released version 2.9.0 on 2026-04-10 and version 2.10.0 on
2026-06-18. These application releases incorporated public Apache NiFi API
release versions 2.8.0 and 2.9.0 respectively. Each of the application
releases incorporated over 150 Jira issues resolved, following the standard
practice of regular dependency upgrades along with other new features and
fixes.
Apache NiFi 2.10.0 is the first version to include the user interface
features for installing and configuring Connectors, a new extension strategy
that supports end-to-end data pipelines that build on standard Processors and
Controller Services. The project continues to iterate on the new Connector
API, introducing secrets management integration and migration capabilities.
Along with the release of Apache NiFi 2.10.0, the project published four
vulnerabilities in response to research and responsible reporting from several
individuals. Part of the resolution for some issues included better alignment
of framework authorization strategy with maintainable security boundaries,
removing some historical implementation for restricted authorization at the
component level.
## Community Health:
The project continues with active community participation in pull requests,
Jira issues, and discussions on the project Slack community. Mailing list
activity continues for standard project interactions, such as feature
discussions and release votes.
The project has close to 3,900 followers on LinkedIn, and over 4,000 members
on the Slack community. These numbers reflect consistent participation with
small changes from the previous quarter.
The Apache NiFi Security Team has observed an increase in the number of
reported findings, most of which reflect AI-driven concerns and often lack
more substantive consideration. The project continues to review and respond to
these reports, acknowledging and publishing vulnerabilities as needed, while
directing reporters to the project Security Model and other documentation when
necessary.
-----------------------------------------
Attachment BE: Report from the Apache Nutch Project [Sebastian Nagel]
## Description:
Apache Nutch is a highly extensible and scalable open source web crawler
software project based on Apache Hadoop® data structures and the MapReduce
data processing framework.
## Project Status:
Current project status: ongoing with medium to low activity
Issues for the board: none
## Membership Data:
Apache Nutch was founded 2010-04-21 (15 years ago)
There are currently 23 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Joe Gilvary on 2024-08-07.
- No new committers. Last addition was Joe Gilvary on 2024-08-07.
## Project Activity:
1.22 was released on 2026-02-12.
Nutch 1.23 should be released during the next weeks in July.
Work during the last quarter was mostly about code quality, code security and
major dependency upgrades. Nutch is now based on Hadoop 3.5.0 and will require
Java 17.
## Community Health:
The number of contributions (Jira issues, commits and GitHub pull requests) in
the past quarter was still above average. However, there was no traffic on the
user mailing list. We continued to receive contributions from new people.
-----------------------------------------
Attachment BF: 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 40 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Matteo Golin on 2025-11-10.
- Eren Terzioğlu was added as committer on 2026-05-20
## Project Activity:
Releases
13.0.0 released by community on 12.07.2026 marking a new major release
- over 500 contributions from community since the last release
12.13.0 was released on 2026-04-02.
The NuttX community is committed to provide high quality quarterly releases
## Community Health:
The community is active on
- mailing list (traffic decreased due to vacation period)
low quality AI generated contributions are discussed by community
- discord channel (daily casual conversation)
-----------------------------------------
Attachment BG: 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: Dormant
Issues for the board: none
## Membership Data:
Apache OpenJPA was founded 2007-05-16 (19 years ago)
There are currently 36 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13.
- No new committers. Last addition was Paulo Cristovão de Araújo Silva Filho
on 2025-05-30.
## Project Activity:
Work on Jakarta Persistence 3.2 implementation is currently in progress.
It takes lots of time due to
- the changes are huge
- the tests are slow
- free time is limited
Next major version will be released as soon as this work will be complete
Recent releases:
- 4.0.1 was released on 2024-09-27.
- 4.0.0 was released on 2024-02-14.
- 3.2.2 was released on 2022-03-16.
## Community Health:
We have voted one more committer. Emails are being answered. Mail flow is
increased due to Jakarta Persistence 3.2 work is in progress.
-----------------------------------------
Attachment BH: Report from the Apache OpenMeetings Project [Maxim Solodovnik]
## Description:
The mission of OpenMeetings is the creation and maintenance of software
related to OpenMeetings: Web-Conferencing and real-time collaboration
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache OpenMeetings was founded 2013-01-25 (13 years ago)
There are currently 30 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ali Alhaidary on 2021-03-22.
- No new committers. Last addition was Ali Alhaidary on 2021-04-07.
## Project Activity:
We are ready to release version 9.1.0 (recent last minute issue was just
addressed)
Recent releases:
- 9.0.0 was released on 2026-03-31.
- 8.1.0 was released on 2025-09-12.
- 8.0.0 was released on 2025-01-02.
## Community Health:
Mail flow is decreasing (increased dev@ mail traffic is due to dependabot
emails). There also no new users on the lists. We still have 3 active PMC
members. Emails are answered in timely manner, so, I guess, we are good.
-----------------------------------------
Attachment BI: Report from the Apache OpenOffice Project [Keith McKenna]
## 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
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 3: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:
Recent releases:
- 4.1.16 was released on 2025-11-10.
- 4.1.15 was released on 2023-12-22.
Planned release:
- 4.1.17 should be released soon.
LLMs are being used by developers to enable massive improvements and issue
triage.
Exciting new commits include:
- Native MacOS silicon support.
- Python 3.10 upgrade from Python 2.7.
- Windows 64 bit support.
These OS and dependency upgrades will be released as 4.2.0 when ready.
## Community Health:
The community dynamics are increased developer activity with the rest of the
community working at about the same levels.
Our PMC Chair has resigned and there will be a special order to replace them
in the current agenda.
-----------------------------------------
Attachment BJ: Report from the Apache OpenWebBeans Project [Mark Struberg]
-----------------------------------------
Attachment BK: Report from the Apache ORC Project [William Hyun]
-----------------------------------------
Attachment BL: Report from the Apache Parquet Project [Julien Le Dem]
## Description:
A column-oriented data file format designed for efficient data storage and
retrieval. It provides high performance compression and encoding schemes to
handle complex data in bulk and is supported in many programming languages and
analytics tools.
Parquet consists of a format specification (the Parquet format) and several
implementations, one of which (Parquet Java) is developed directly under the
umbrella of the Apache Parquet project. Several implementations such as
Parquet C++, Parquet Go, and Parquet Rust are developed as part of the Apache
Arrow project. Non-Apache implementations also exist, some of them closed
source.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Parquet was founded 2015-04-21 (11 years ago)
There are currently 41 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.
- Ed Seidl was added as committer on 2026-05-07
## Project Activity:
Recent releases:
Parquet-Format
Parquet-Format 2.13.0 was released on 2026-06-13.
Parquet-Java
Parquet-Java 1.17.1 was released on 2026-05-12.
Parquet-Java 1.17.0 was released on 2026-01-13.
Parquet-Rust
Arrow-RS-OS-0.14.0 was released on 2026-06-22.
Arrow-RS-59.0.0 was released on 2026-06-09.
Arrow-RS-56.2.1 was released on 2026-05-11.
Arrow-RS-57.3.1 was released on 2026-05-11.
Arrow-RS-58.3.0 was released on 2026-05-11.
Arrow-RS-58.2.0 was released on 2026-05-02.
Parquet-go:
Arrow-Go-18.6.0 was released on 2026-04-28.
Parquet-cpp
Arrow 24.0.0 was released on 2026-04-21.
(Note that Parquet Go, Rust and Cpp 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)
Seattle and Paris meetups have happened (the latter jointly with Apache Arrow,
see post at
https://www.linkedin.com/feed/update/urn:li:activity:7474760529719308288/ ).
There are many in progress discussions and proposals in the community.
Work in
progress:
New encodings:
The Adaptive Lossless Floating Point spec is close.
It has two implementations (C/C++, Java), a well reviewed spec and example
files.
As it is forward incompatible, waiting on clarity for how to release
it. See parquet versioning below
FSST Spec in progress,
high level alignment on the design, spec is being finalized.
Footer working group:
organized three sessions,
defined goals and target scenarios,
built footer microbenchmark,
and drafted the proposal.
Parquet versioning definition:
the community is working on consensus for how to communicate forward
incompatible changes,
such as an agreed on versioning scheme.
We have a new page to explain the current feature set:
https://parquet.apache.org/docs/file-format/versions/
Non-contiguous pages proposal in progress
New types:
File type
Fixed list type proposal
Vector proposal
Goal is to enable more efficient storage of (multidimensional) arrays
Three implementation approaches were proposed, prototyped and
benchmarked Discussion on merits of each proposed approach is in progress
## Community Health:
Community Health Score (Chi): 10.00 (Super 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 BM: Report from the Apache PDFBox Project [Andreas Lehmkühler]
-----------------------------------------
Attachment BN: Report from the Apache Pig Project [Koji Noguchi]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It provides
a high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs.
## Project Status:
Current project status: Dormant
## Membership Data:
Apache Pig was founded 2010-09-21 (16 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Koji Noguchi on 2016-08-04.
- No new committers. Last addition was Nándor Kollár on 2018-09-06.
## Project Activity:
Work is going for the next release 0.19.0 targeting some bug fixes
and version compatibility issues. The release was initially targeted
for the end of May. However due to delays, the release is now targeted
for the end of July.
## Community Health:
Overall activity is low as the project is in maintenance mode. Contributions
are mainly bug fixes and updating dependencies.
-----------------------------------------
Attachment BO: Report from the Apache PLC4X Project [César García]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache PLC4X was founded 2019-04-17 (7 years ago)
There are currently 21 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Unai Lería Fortea on 2025-09-29.
- No new committers. Last addition was Unai Lería Fortea on 2025-06-11.
## Project Activity:
Protocol Updates: Improved BACNet, OPC-UA, KNX, and AB-Ethernet/IP drivers;
fixed Modbus goroutine leaks.
Error Handling: Added transport validation and graceful PCAP library detection.
Maintenance: Removed deprecated PlcValues class; updated 10+ dependencies
(e.g., testcontainers, gson).
Security:
Adjusted coverage thresholds for pcap-replay, socket-can, and serial transports.
## Community Health:
Active contributions from Christofer Dutz, Sebastian Rühl, and others;
One new contributor showed up with an interesting Pullrequest on a new protocol.
-----------------------------------------
Attachment BP: Report from the Apache Ranger Project [Selvamohan Neethiraj]
-----------------------------------------
Attachment BQ: Report from the Apache Ratis Project [Tsz-wo Sze]
## Description:
The mission of Apache Ratis is the creation and maintenance of software related
to a highly customizable Raft protocol implementation in Java.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Ratis was founded 2021-02-16 (5 years ago)
There are currently 31 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Xinyu Tan on 2025-06-22.
- No new committers. Last addition was Xinyu Tan on 2024-08-27.
## Project Activity:
No new releases were finalized during this quarter. The primary technical
highlights are as follows:
- Added a new Streaming Read feature.
- Defined a public TraceProvider interface and moved the OpenTelemetry
TraceProvider implementation to a new ratis-trace-otel module.
The last Ratis release was 3.2.2, which was released on 2026-04-03.
## Community Health:
The project is healthy. In this quarter, we have lower traffic in both
the dev@ (75% decrease) and the user@ (90% decrease) mailing lists compared
to the previous quarter. The main reason probably is due to the release
discussion in the previous quarter. We have 98 JIRA tickets opened and 88
closed in this quarter.
-----------------------------------------
Attachment BR: Report from the Apache Rya Project [Adina Crainiceanu]
## Description:
The mission of Apache Rya is the creation and maintenance of software related
to scalable storage, retrieval, and analysis of RDF data
## Project Status:
Current project status: Dormant: Not much happening on the code, but at least
3 PMC members ready to engage if needed
Issues for the board: None. Please let us know if we should initiate a
roll call.
## Membership Data:
Apache Rya was founded 2019-09-18 (7 years ago)
There are currently 12 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Adina Crainiceanu on 2019-09-18.
- No new committers were added.
## Project Activity:
No active developments. Last release was 4.0.1 on 2020-12-22.
## Community Health:
There is no current activity in the project. The software is used in
production by users. The project is in "dormant" state: not much happening on
the code, but at least 3 PMC members ready to engage if needed.
dev@rya.apache.org had a 50% decrease in traffic in the past quarter
(1 emails compared to 2)
-----------------------------------------
Attachment BS: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment BT: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to a ultra-high-performance distributed data
integration tool that supports cdc and batch synchronization of massive
data
## Project Status:
Current project status: Health Issues for the board: There are no Board-level
issues at this time.
## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (3 years ago) There are currently 41
committers and 23 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 Shenghang Zhang on 2026-03-12.
- Xuepeng Wang was added as committer on 2026-04-28
- ZengYi was added as committer on 2026-05-20
## Project Activity:
- 2.3.13 was released on 2026-03-14
- 2.3.12 was released on 2025-09-12
now we're preparing for the next big version 3.0.0
## Community Health:
- We have held one community online Meetups in last quarter.
- dev@seatunnel.apache.org had a 420% increase in traffic in the past quarter
(78 emails compared to 15):
Overall community health is good. We are working on the next major version.
-----------------------------------------
Attachment BU: Report from the Apache SINGA Project [Wang Wei]
## Description:
The mission of Apache SINGA is the creation and maintenance of software
related
to a distributed deep learning platform
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SINGA was founded 2019-10-16 (5 years ago)
There are currently 23 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.
## Project Activity:
The team has released SINGA 5.1.0 on 2 April 2026.
The release note is at
https://github.com/apache/singa/blob/master/RELEASE_NOTES
The main features of this release include
1. Add the implementations for Parameter-Efficient Fine-Tuning (PEFT).
2. Update the healthcare model zoo.
3. Add more healthcare examples.
4. Add the implementations for more attention mechanisms.
5. Update the encoder layers for the transformer model.
6. Fix typos in Python module docstrings.
Apart from this release, the community has been working on:
1. Adding more datasets and model implementations for the PEFT.
2. Restructuring the folders, e.g., postgresql msmlp.
3. Fixing build and test compatibility.
4. Fixing CI for conda and ubuntu.
## Community Health:
According to the statistics, there are increase of email traffic and github
commits, which shows that the community is active in the development.
-----------------------------------------
Attachment BV: 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:
- Youliang Huang was added to the PMC on 2026-05-06
- Yi Wang was added as committer on 2026-06-02
- YiMing Shao was added as committer on 2026-04-11
## Project Activity:
We have over 10 releases in this quarter.
nodejs-0.9.0 was released on 2026-06-26
horizon-ui-0.7.0 was released on 2026-06-25
banyandb-0.10.3 was released on 2026-06-20
SWCK-0.10.0 was released on 2026-06-08.
horizon-ui-0.6.0 was released on 2026-06-04.
horizon-ui-0.5.0 was released on 2026-05-24.
banyandb-0.10.2 was released on 2026-05-06.
helm-4.9.0 was released on 2026-05-06.
banyandb-helm-0.6.0 was released on 2026-04-28.
banyandb-0.10.1 was released on 2026-04-03.
mcp-0.2.0 was released on 2026-04-03.
The developments and releases are rapid. Also, we refactored the website.
## Community Health:
The community is healthy. Still, we are expanding around the new BanyanDB
development. A series of blog post is published for the new UI subproject
Horizon. GitHub issues traffic is as normal, and a lot of basic QAs are
resolved by kapa, 100-200 QA(s) are tracked per week.
-----------------------------------------
Attachment BW: Report from the Apache Steve Project [Greg Stein]
-----------------------------------------
Attachment BX: 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 three releases in the reporting period:
- Struts 7.2.1 - Bug Fix, Improvements and Feature Release (2026-06-15) [1]
- Struts 6.10.0 - Bug Fix and Improvements Release (2026-05-25) [2]
- Apache Struts IntelliJ IDEA plugin ver. 261.19017.1 (2026-04-28)
The last Struts releases besides the core framework were
- Struts Annotations 2.0.0 - Enhancements and JDK 17 support (2025-07-03)
- Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06)
Within the last quarter, we saw again steady activity levels, very similar to
the preceding period.
IntelliJ Struts Plugin 261.19027.1 is currently under release vote.
We updated our security guidelines and process documentation to help reporters
on what and how to report.
We have no issues that require board assistance at this time.
## Community Health
### Development activity in the regular reporting period
23 JIRA tickets opened and 16 closed in the past quarter
We had 119 PRs opened and 108 closed in the main project.
### Mailing list activity in the regular reporting period:
- dev@struts.apache.org had a 193% increase in traffic in the past quarter (91
emails compared to 31)
- issues@struts.apache.org had a 26% decrease in traffic in the past quarter
(220 emails compared to 295)
- notifications@struts.apache.org had a 12% decrease in traffic in the past
quarter (660 emails compared to 747)
- user@struts.apache.org had a 37% decrease in traffic in the past quarter (14
emails compared to 22)
[1] https://struts.apache.org/announce-2026#a20260615
[2] https://struts.apache.org/announce-2026#a20260525
-----------------------------------------
Attachment BY: 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
Last release: 5.9.1 (2026-04-29)
## Project Status:
Current project status: ongoing.
Issues for the board: none.
## Membership Data:
Apache Tapestry was founded 2006-02-15 (20 years ago)
There are currently 30 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ben Weidig on 2021-12-03.
- No new committers. Last addition was Christian Köberl on 2024-05-02.
## Project Activity:
After the Gradle setup was finished as mentioned in the last report, we
focused on the user-facing side for the next release (5.10). It will contain
functional changes that will require minor user intervention to adapt, so we
have decided to delay the release to evaluate which additional features should
be included.
By postponing the release further, we believe we will deliver a more complete
package with a healthy mix of new features and bug fixes.
The new project homepage has not been released yet, as we are awaiting
feedback from Infra regarding hosting. However, we acknowledge that we also
failed to follow up in a timely manner.
In our last report, we mentioned we would not migrate our issue tracking to
GitHub. To utilize GitHub in a way that better serves the community without
migrating project management without a clear path back, we are experimenting
with a more transparent approach to feature development by using PRs, hoping
to make it easier for the community to see what is being worked on and to
participate. In addition to PRs, we want to evaluate if "Discussions,"
especially polls, could provide another easy way to get closer to the pulse of
the community and improve overall project planning.
## Community Health:
Without a new release, mailing list activity remains low as expected.
A community member released a Tapestry-compatible Gantt library:
https://github.com/MarineBerth/optogantt
JIRA activity was a mix of mostly new features and a few bugfixes,
plus some ideas open for discussion.
9 opened
7 closed
GitHub PRs:
5 merged/closed
3 open (1 fix, 1 security improvement, 1 dependabot)
1 draft (feature in discussion how to be done/merged)
2 stale/kept for reference
-----------------------------------------
Attachment BZ: Report from the Apache Tcl Project [Georgios Petasis]
-----------------------------------------
Attachment CA: 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:
Still doing 1.0.0 patches, valuable contributions keep coming in.
## Community Health:
Active contributor is still present, I'll start a [VOTE] on the private
channel to consider him as a committer.
-----------------------------------------
Attachment CB: 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: I opened INFRA-27807 earlier this year after noticing
flaws in the email system. Specifically, many important emails, such as
security reports and board meeting reminders (e.g. this one), were never
reaching my inbox. Although there was some initial activity, work on the
ticket eventually stalled completely. There has been total silence since the
end of May, so I have now marked it as "blocker" and wish to escalate the
matter. For a community that relies heavily and primarily on email working
properly (following the principle that "if it isn't on the mailing list, it
didn't happen"), the current situation is absolutely unsatisfactory. This
might not be a genuine "board issue," but it seems necessary to me to draw
attention to this annoyance. I also cannot imagine that I am the only one
affected by this.
## 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.
- Dmytro Shteflyuk was added as committer on 2026-04-15
- Volodymyr Panivko was added as committer on 2026-04-28
## Project Activity:
We released 0.23.0 in Aprtil this year and are working towards 0.24.0
## Community Health:
Overall, there is active participation from both existing and new
contributors. While the areas of focus shift over time, contributions are
regularly received for most target-language bindings. Since we began using
AI-powered tools for code reviews, we have observed an improvement in the
quality of contributions; this is a significant help, particularly for niche
languages where maintainers often have limited time.
-----------------------------------------
Attachment CC: Report from the Apache Tika Project [Tim Allison]
## Description:
Apache Tika is a dynamic toolkit for content detection, analysis, and
extraction. It allows a user to understand, and leverage information from, a
growing a list of over 1200 different file types including most of the major
types in existence (MS Office, PDF, Text, Images, Video, Code, and science
data) as recognized by IANA and other standards bodies.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Tika was founded 2010-04-20 (16 years ago)
There are currently 31 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05.
- No new committers. Last addition was Nicholas DiPiazza on 2021-06-03.
## Project Activity:
Released 4.0.0-beta-1 in early July, and we're on the cusp of a 3.3.2 release.
Some increase in security reports, mostly requiring hardening of our security
model documentation. There are two genuine CVEs that we'll report after the
3.3.2 release.
## Community Health:
Some increase in email traffic mostly centered on fellow devs coordinating
features for the 4.x release. We also have quite a bit of added (welcomed)
copilot traffic. Chi still in decent shape: 4.70 (Healthy).
-----------------------------------------
Attachment CD: 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:
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 is preparing for it's next set of releases which are likely to
come out later this month. This will include TinkerPop 3.7.7 and 3.8.2, which
will be maintenance releases primarily containing bug fixes and security
non-breaking improvements, in addition to TinkerPop 4.0.0-beta.3 which marks a
significant milestone on the path towards TinkerPop 4.
While past TP4 betas were focused on the mechanics of shifting to a pure HTTP
protocol, beta.3 builds on that foundation to deliver features which expand
the capabilities of the project. There are several notable additions. A new
declarative pattern-matching capability aligns Gremlin with the ISO GQL
standard [1]. An overhaul to how many Gremlin steps handle dynamic arguments
addresses what has arguably been the most frustrating limitation of the
language for years. Finally, all drivers see performance improvements through
the introduction of response streaming.
We have seen a sharp increase in community activity this quarter, with PR
submissions rising roughly 50% above our historical average. This has been
driven both by increased committer activity and by external community
submissions, with many notable TinkerPop 4 features driven in full or in part
by external contributors. One particularly noteworthy case is an external
contributor building gremlin-dart [2], an entirely new language variant for
Dart. We believe a trend of large submissions is forming, and in response we
have revived the Tinkubator [3] to give a temporary home as these projects
progress to maturity.
We've received a few security vulnerability reports from researchers this
quarter. None of the reports were deemed serious, and we've made plans to
address issues we felt needed attention.
### Releases:
3.7.6 was released on 2026-04-01.
3.8.1 was released on 2026-04-01.
4.0.0-beta.2 was released on 2026-04-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.
The community continues to hold regular TinkerPop Gathering meetings [4], open
to anyone who wishes to join, to enhance collaboration and provide real-time
discussion opportunities. Meeting notes are recorded on the dev list, with
recent topics including OLAP Modernization, the expansion of our data model to
include multiple labels, the development and potential TinkerPop applicability
of Hydra [5], and the open sourcing of Aerospike Graph Service [6].
This quarter featured three live events on Twitch [7]. It began with a
Contributorcast breaking down the releases from last April, followed by two
TinkerPop Wide presentations: one on Gremlinq [8], and another on building
text-enriched property graphs. All three recordings are available on our
YouTube channel [9]:
* TinkerPop Contributorcast: Breaking down TinkerPop 3.7.6, 3.8.1, and
4.0.0-beta.2 [10] Presenters: Yang Xia, Ken Hu, Cole Greer
* TinkerPop Wide: Every Hop, Strongly Typed - Gremlinq in Depth [11]
Presenters: Daniel Weber, Stephen Mallette
* TinkerPop Wide: Beyond Topology - Building and Querying Text-Enriched
Property Graphs [12] Presenters: Amir Hosseini, Stephen Mallette
## Report Links
[1]: https://www.iso.org/standard/76120.html
[2]: https://issues.apache.org/jira/browse/TINKERPOP-3251
[3]: https://github.com/apache/tinkerpop/tree/master/tinkubator
[4]: https://lists.apache.org/thread/06jq7cs987g3slv6jst4nmvl1lgnfc8t
[5]: https://github.com/CategoricalData/hydra
[6]: https://github.com/aerospike/aerospike-graph-service
[7]: https://www.twitch.tv/apachetinkerpop
[8]: https://docs.gremlinq.net/
[9]: https://www.youtube.com/@apachetinkerpop
[10]: https://youtu.be/IUtZgtmdLsw?si=tIMj6iThcwz2-7l2
[11]: https://youtu.be/179KLRA4W_o?si=BIOn0q42XXFGPU1A
[12]: https://youtu.be/3fHxEdVinvw?si=gd_klP7Spd7DaS0M
-----------------------------------------
Attachment CE: Report from the Apache Traffic Server Project [Bryan Call]
-----------------------------------------
Attachment CF: 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 (10 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.
There was some commit activity, with a number of starter presentation branches
created for projects including Superset, DataFu, Velocity, SpamAssassin,
Empire-db, Curator, and Xerces.
One idea was breought from work on the Apache Magpie project: an approach to
take existing training material and turn
it into an AI tutor prompt, allowing an interactive session where an LLM asks
questions, grades and corrects answers, and guides the user through the
material.
Some training content has been created for the Apache Magpie project. It is
not yet known whether this will end up in Apache Training in some form.
## Community Health:
The community remains small and quiet. There was no mailing list traffic
during this reporting period, though some commit activity continued. The
project tends to work on materials as needed, and this pattern of quiet
periods punctuated by bursts of activity is typical.
-----------------------------------------
Attachment CG: Report from the Apache Wayang Project [Zoi Kaoudi]
-----------------------------------------
Attachment CH: Report from the Apache Web Services Project [Daniel Kulp]
## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.
## Project Status:
Current project status: ongoing, low activity
Issues for the board: very minimal viability of project
## Membership Data:
Apache Web Services was founded 2003-01-22 (23 years ago)
There are currently 223 committers and 42 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Robert Lazarski on 2021-06-14.
- No new committers. Last addition was Alessio Soldano on 2014-09-14.
## Project Activity:
WebServices is a mature project based on standards that are also quite mature.
As such, there is not a significant amount of activity required. However, user
questions are being answered promptly, bugs are being fixed, and there are at
least 3 independent PMC members around making sure the project can continue to
produce releases as needed. Since SOAP/XML based Web Services is no longer
considered state of the art, we don't expect a major uptick in new development
efforts, new committers, etc...
There were four development efforts this period:
1) Dependabot updates (always ongoing)
2) Some work by veithen in Axiom to update to recent Java language semantics
3) Some security reports came in related to Neethi that coheigea is reviewing
and will likely have CVE's created. Expect a release soon.
Latest Releases:
Neethi-3.2.1 was released on 2026-04-28
XmlSchema-2.3.2 was released on 2025-11-04
WSS4J 4.0.1 was released on 2025-11-04
WSS4J 3.0.5 was released on 2025-11-04
Axiom-2.0.0 was released on 2025-02-06
Woden-1.0M10: 2015-09
## Community Health:
As mentioned in the Feb board report, I don't really consider the community
to be "Healthy" with only two people doing all the work (and in very separate
sub projects). We are curious to see if the results of the scans overwhelm
the couple of people doing the work or not. The Neethi vote in April did
get the required 3 binding votes (and one non-binding vote). No room for
error, but three people did show up to cast binding votes.
-----------------------------------------
Attachment CI: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Yetus was founded 2015-09-15 (11 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
Quite a bit of activity in March, April, and May with some big updates,
including switching the operating system of the base container. We are now
dealing with fallout from those changes with an eye towards making a 0.16
release later this year.
## Community Health:
Despite the lack of a board report last month (that's on aw@ being forgetful),
we're fine. While not a whole lot is happening in the mailing lists, there are
definitely signs of life in commits, github PRs, and JIRA issues. Two PMC
members being the most visible and others are watching so getting a release
out shouldn't be an issue.
-----------------------------------------
Attachment CJ: Report from the Apache Zeppelin Project [Jongyoul Lee]
## Description:
The mission of Zeppelin is the creation and maintenance of software
related to a web-based notebook that enables interactive data
analytics
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: Apache Zeppelin 0.12.1 has been released. The PMC is
reviewing newly reported security issues through the private security process.
The release is done, but we have not yet notified the reporters; that
follow-up is still pending.
## Membership Data:
Apache Zeppelin was founded 2016-05-18 (10 years ago).
There are currently 27 committers and 13 PMC members in this project. The
Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Cheng Pan on 2024-08-25.
- No new committers. Last committer additions were ChanHo Lee and Gyeongtae
Park on 2025-08-20.
## Project Activity:
Apache Zeppelin 0.12.1 was released during this period, moving the project
forward after the 0.12.0 release line.
The community focused less on adding broad new surface area and more on making
the codebase easier to maintain, safer to ship, and more approachable for
future contributors.
On the UI side, the modernization effort continued by moving the Angular UI to
a current stack, improving the React integration path, and fixing user-visible
issues around note switching, paragraph cloning, editor focus, and table
result copy support. This work helps reduce the gap between the legacy UI and
the newer UI.
On the runtime and interpreter side, the community continued pruning stale
integrations and updating supported ones. Deprecated Flink shims were removed
while newer Flink support was added, and outdated Alluxio and R/SparkR
interpreter paths were dropped. This keeps the supported surface clearer for
both users and contributors.
Security and maintainability also received attention. The project added
SECURITY.md and THREAT_MODEL.md, followed up on threat-model questions, and
made hardening changes around REST/WebSocket handling, path validation, LDAP
escaping, and dependency updates.
## Community Health:
The community remains moderate and code-review oriented. Public dev/users
mailing-list traffic is not high, but review and maintenance work continues
steadily around the areas that matter for the next release: UI modernization,
interpreter cleanup, security posture, and contributor onboarding.
The project is preparing for OSSCA again this year. The important part is not
only that new contributors may arrive, but that the PMC has prepared a set of
low-hanging-fruit issues for them. These issues are intentionally small and
well-scoped across documentation, UI, interpreter behavior, tests, and cleanup
work, so newcomers can make real contributions without needing to understand
the whole Zeppelin stack first.
This is meant to turn the onboarding period into a path toward sustained
contribution. The PMC is also actively inviting more contributors to grow into
committer and PMC member roles.
------------------------------------------------------
End of minutes for the July 15, 2026 board meeting.