Index
Links: 2026 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
June 17, 2026
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:01 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-06-17T21:00:00&msg=ASF+Board+Meeting
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Zili Chen
Shane Curcuru
Christofer Dutz
Emmanuel Lécharny
Justin Mclean
Jean-Baptiste Onofré
Christopher Schultz
Greg Stein
Sander Striker
Directors Absent:
none
Executive Officers Present:
Craig McClanahan
Ruth Suehle
Matt Sicker
Craig L Russell
Daniel Ruggeri
Executive Officers Absent:
none
Guests:
Daniel Gruno
Sally Khudairi
Dave Fisher
Daniel Sahlberg
Jeff Genender
Thomas Neidhart
Andrew Musselman
Brian Proffitt
Jarek Potiuk
Drew Foulks
Andrew Wetmore
Paul King
Philipp Ottlinger
Kanchana Pradeepika Welagedara
Rich Bowen
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of May 20, 2026
See: board_minutes_2026_05_20.txt
Approved by General Consent.
B. The meeting of March 18, 2026
See: board_minutes_2026_03_18.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
The world seems to be moving faster than ever, and yet it feels
like a familiar pattern. The Foundation has been through, and
contributed to, massive change in the industry. AI is the
current wave of massive change, which by the current trend,
will continue for a while.
I have been able to submit some changes to the Board Agenda Tool
this period. I am keen to get to the point where the agenda
creation and reminder sending is fully automatic.
Lastly, I will be attending UN Open Source week in NYC.
B. President [Ruth Suehle]
This month I keynoted Berlin Buzzwords. It was great to meet a ton of Apache
contributors I had not before and to hear about their work. This month I will
be representing us at UN Open Source Week in several events during the week
and expect to see quite a few ASF folks there as well.
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig McClanahan]
Normal operations continue, with two notes:
* Had a kickoff meeting with KWC, the firm that will be doing our audit.
Typical timeframe is about two months. I will be granting them readonly
access to our QuickBooks account so they should be able to address many
questions they might ask without having to talk to us about them.
* If you are responsible for an area that incurs expenses, you will have
received a request from Lewis McGibney (our Assistant Treasurer) to set up a
quick meeting to review upcoming reports of detailed monthly data on
expenditures from both Bill.com and Ramp.com. Please respond to his request
for a short meeting to discuss these reports, and answer any questions.
D. Secretary [Matt Sicker]
In May, the secretary received 47 ICLAs and one CCLA.
E. Executive Vice President [Daniel Ruggeri]
As with prior months, there is little official business to discuss. Most
things continue being a well-oiled machine.
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 / Jean-Baptiste Onofré]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Greg Stein]
No report was submitted.
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:
# DevLake [jmclean]
# Geronimo [jmclean, gstein]
# Gravitino [jmclean]
# IoTDB [cdutz]
# OpenDAL [jmclean]
# Wicket [jmclean]
# Xerces [striker]
A. Apache AGE Project [Jeff Jirsa / Justin Mclean]
No report was submitted.
B. Apache Airflow Project [Bolke de Bruin / Sander Striker]
No report was submitted.
C. Apache Allura Project [Dave Brondsema / Christofer Dutz]
See Attachment C
D. Apache Ant Project [J Pai / Christopher Schultz]
See Attachment D
E. Apache Atlas Project [Madhanmohan Neethiraj / Shane Curcuru]
See Attachment E
F. Apache Axis Project [Robert Lazarski / Zili Chen]
See Attachment F
G. Apache Beam Project [Kenneth Knowles / Justin Mclean]
See Attachment G
H. Apache Bigtop Project [Masatake Iwasaki / Christofer Dutz]
See Attachment H
I. Apache BVal Project [Matt Benson / Shane Curcuru]
See Attachment I
J. Apache Camel Project [Andrea Cosentino / Greg Stein]
See Attachment J
K. Apache Cayenne Project [Michael Gentry / Shane Curcuru]
See Attachment K
L. Apache CloudStack Project [Wido den Hollander / Emmanuel Lécharny]
See Attachment L
M. Apache Commons Project [Gary D. Gregory / Christopher Schultz]
See Attachment M
N. Apache Cordova Project [Bryan Ellis / Jean-Baptiste Onofré]
See Attachment N
O. Apache CouchDB Project [Jan Lehnardt / Zili Chen]
No report was submitted.
P. Apache cTAKES Project [Pei J Chen / Sander Striker]
See Attachment P
Q. Apache Curator Project [Enrico Olivelli / Christofer Dutz]
No report was submitted.
R. Apache Daffodil Project [Steve Lawrence / Greg Stein]
See Attachment R
S. Apache DataFusion Project [Andrew Lamb / Christopher Schultz]
See Attachment S
T. Apache DevLake Project [Hezheng Yin / Sander Striker]
See Attachment T
@Justin Mclean: follow up with DevLake about incubator tags
U. Apache Drill Project [Charles Givre / Jean-Baptiste Onofré]
See Attachment U
V. Apache Druid Project [Abhishek Agarwal / Zili Chen]
No report was submitted.
W. Apache ECharts Project [Wenli Zhang / Justin Mclean]
See Attachment W
X. Apache Felix Project [Karl Pauls / Emmanuel Lécharny]
See Attachment X
Y. Apache Flex Project [Harbs / Shane Curcuru]
No report was submitted.
Z. Apache Flink Project [Robert Metzger / Christofer Dutz]
See Attachment Z
AA. Apache Geronimo Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
AB. Apache Gobblin Project [Abhishek Tiwari / Christopher Schultz]
See Attachment AB
AC. Apache Gravitino Project [Jerry Shao / Sander Striker]
See Attachment AC
@Sander Striker: follow up about release candidate location
AD. Apache Guacamole Project [Mike Jumper / Emmanuel Lécharny]
No report was submitted.
AE. Apache Gump Project [Stefan Bodewig / Jean-Baptiste Onofré]
See Attachment AE
AF. Apache Helix Project [Junkai Xue / Justin Mclean]
See Attachment AF
AG. Apache Hive Project [Naveen Gangam / Zili Chen]
No report was submitted.
AH. Apache Hop Project [Hans Van Akelyen / Justin Mclean]
See Attachment AH
AI. Apache Hudi Project [Vinoth Chandar / Greg Stein]
See Attachment AI
AJ. Apache HugeGraph Project [Jermy Li / Shane Curcuru]
No report was submitted.
AK. Apache Iceberg Project [Ryan Blue / Shane Curcuru]
See Attachment AK
AL. Apache Incubator Project [Justin Mclean / Justin Mclean]
See Attachment AL
AM. Apache IoTDB Project [Xiangdong Huang / Christopher Schultz]
See Attachment AM
@Christopher Schultz: reach out about communication issues
AN. Apache Jackrabbit Project [Marcel Reutegger / Justin Mclean]
See Attachment AN
AO. Apache Karaf Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré]
See Attachment AO
AP. Apache Kvrocks Project [Mingyang Liu / Sander Striker]
See Attachment AP
AQ. Apache Kyuubi Project [Cheng Pan / Greg Stein]
See Attachment AQ
AR. Apache Linkis Project [Shuai Di / Christofer Dutz]
See Attachment AR
AS. Apache Livy Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré]
See Attachment AS
AT. Apache Lucene Project [Ben Trent / Emmanuel Lécharny]
See Attachment AT
AU. Apache Lucene.Net Project [Shad Storhaug / Zili Chen]
No report was submitted.
AV. Apache Mynewt Project [Szymon Janc / Jean-Baptiste Onofré]
No report was submitted.
AW. Apache NetBeans Project [Geertjan Wielenga / Justin Mclean]
See Attachment AW
AX. Apache OFBiz Project [Jacopo Cappellato / Christofer Dutz]
See Attachment AX
AY. Apache OpenDAL Project [Hao Ding / Jean-Baptiste Onofré]
See Attachment AY
@Christopher Schultz: follow up about AI code usage
AZ. Apache OpenNLP Project [Jeffrey T. Zemerick / Greg Stein]
See Attachment AZ
BA. Apache OpenOffice Project [Keith McKenna / Emmanuel Lécharny]
No report was submitted.
BB. Apache OpenWebBeans Project [Mark Struberg / Christopher Schultz]
No report was submitted.
BC. Apache Paimon Project [Jingsong Lee / Sander Striker]
See Attachment BC
BD. Apache Pekko Project [PJ Fanning / Zili Chen]
See Attachment BD
BE. Apache Pig Project [Koji Noguchi / Shane Curcuru]
No report was submitted.
BF. Apache PLC4X Project [César García / Sander Striker]
No report was submitted.
BG. Apache Portable Runtime (APR) Project [Yann Ylavic / Zili Chen]
See Attachment BG
BH. Apache Pulsar Project [Matteo Merli / Christofer Dutz]
See Attachment BH
BI. Apache Ranger Project [Selvamohan Neethiraj / Christopher Schultz]
See Attachment BI
BJ. Apache Royale Project [Andrew Wetmore / Greg Stein]
See Attachment BJ
BK. Apache SeaTunnel Project [Jun Gao / Emmanuel Lécharny]
No report was submitted.
BL. Apache Shiro Project [Lenny Primak / Shane Curcuru]
See Attachment BL
BM. Apache SINGA Project [Wang Wei / Justin Mclean]
No report was submitted.
BN. Apache Sling Project [Robert Munteanu / Jean-Baptiste Onofré]
See Attachment BN
BO. Apache SpamAssassin Project [Giovanni Bechis / Christopher Schultz]
See Attachment BO
BP. Apache Storm Project [Richard Zowalla / Christofer Dutz]
See Attachment BP
BQ. Apache StreamPark Project [Huajie Wang / Jean-Baptiste Onofré]
See Attachment BQ
BR. Apache Synapse Project [Isuru Udana / Shane Curcuru]
See Attachment BR
BS. Apache Tcl Project [Georgios Petasis / Emmanuel Lécharny]
See Attachment BS
BT. Apache Teaclave Project [Zhaofeng Chen / Sander Striker]
See Attachment BT
BU. Apache Tomcat Project [Christopher Schultz / Christopher Schultz]
See Attachment BU
BV. Apache TomEE Project [David Blevins / Jean-Baptiste Onofré]
See Attachment BV
BW. Apache TVM Project [Tianqi Chen / Greg Stein]
See Attachment BW
BX. Apache UIMA Project [Richard Eckart de Castilho / Justin Mclean]
See Attachment BX
BY. Apache Unomi Project [Serge Huber / Zili Chen]
See Attachment BY
BZ. Apache VCL Project [Josh Thompson / Greg Stein]
See Attachment BZ
CA. Apache Web Services Project [Daniel Kulp / Christopher Schultz]
See Attachment CA
CB. Apache Wicket Project [Andrea Del Bene / Justin Mclean]
See Attachment CB
CC. Apache Xerces Project [Michael Glavassevich / Jean-Baptiste Onofré]
See Attachment CC
@Jean-Baptiste Onofré: follow up about Xerces-C EOL
CD. Apache Yetus Project [Allen Wittenauer / Christofer Dutz]
No report was submitted.
CE. Apache ZooKeeper Project [Flavio Junqueira / Emmanuel Lécharny]
See Attachment CE
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Phoenix Project Chair
WHEREAS, the Board of Directors heretofore appointed Istvan Toth
(stoty) to the office of Vice President, Apache Phoenix, and
WHEREAS, the Board of Directors is in receipt of the notification of the
death of Istvan Toth, and
WHEREAS, the Project Management Committee of the Apache Phoenix project has
chosen by vote to recommend Viraj Jasani (vjasani) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Viraj Jasani be and hereby is appointed
to the office of Vice President, Apache Phoenix, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7A, Change the Apache Phoenix Project Chair, was
approved by Unanimous Vote of the directors present.
B. 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 providing the Foundation
and PMCs access to AI models and tooling including
project-level ecosystem support, community engagement, and
global participation.
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 providing the
Foundation and PMCs access to AI models and tooling including
project-level ecosystem support, community engagement, and
global participation.
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
for providing the Foundation and PMCs access to AI models and
tooling including project-level ecosystem support, community
engagement, and global participation.
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>
* Qiang Guo <kirs@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>
* Craig L Russell <clr@apache.org>
* Greg Stein <gstein@apache.org>
* Henri Yandell <bayard@apache.org>
* Kanchana Welagedara <kanchana@apache.org>
Special Order 7B, Create the Responsible AI Executive Committee,
was tabled.
C. Establish the Apache Magpie 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 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.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Magpie Project", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED, that the Apache Magpie Project be and hereby is
responsible for the creation and maintenance of software
related to 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; and be it further
RESOLVED, that the office of "Vice President, Apache Magpie" 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 Magpie Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache Magpie 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 Magpie Project:
* Rich Bowen <rbowen@apache.org>
* Zili Chen <tison@apache.org>
* Amogh Desai <amoghdesai@apache.org>
* Mike Drob <mdrob@apache.org>
* James Fredley <jamesfredley@apache.org>
* Elad Kalif <eladkal@apache.org>
* Piotr Karwasz <pkarwasz@apache.org>
* Paul King <paulk@apache.org>
* Calvin Kirs <kirs@apache.org>
* Pavan Kumar <gopidesu@apache.org>
* Rémy Maucherat <remm@apache.org>
* Justin Mclean <jmclean@apache.org>
* Ismaël Mejía <iemejia@apache.org>
* Andrew Musselman <akm@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
* Jarek Potiuk <potiuk@apache.org>
* Evan Rusackas <rusackas@apache.org>
* Craig L Russell <clr@apache.org>
* Russell Spitzer <russellspitzer@apache.org>
* Coty Sutherland <csutherl@apache.org>
* Matthew Topol <zeroshade@apache.org>
* Richard Zowalla <rzo1@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jarek Potiuk be
appointed to the office of Vice President, Apache Magpie, 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, Establish the Apache Magpie Project, was
approved by Unanimous Vote of the directors present.
D. Terminate the Apache Petri Project
WHEREAS, the Project Management Committee of the Apache Petri
project has chosen to recommend moving the project to the
Attic; and
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Petri project
due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Petri project
is hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with
oversight over the content of the Apache Petri Project; and be
it further
RESOLVED, that the office of "Vice President, Apache Petri" is
hereby terminated; and be it further
RESOLVED, that the Apache Petri PMC is hereby terminated.
Special Order 7D, Terminate the Apache Petri Project, was
approved by Unanimous Vote of the directors present.
E. Change the Apache Logging Services Project Chair
WHEREAS, the Board of Directors heretofore appointed Piotr Karwasz
(pkarwasz) to the office of Vice President, Apache Logging Services, and
WHEREAS, the Board of Directors is in receipt of the resignation of Piotr
Karwasz from the office of Vice President, Apache Logging Services, and
WHEREAS, the Project Management Committee of the Apache Logging Services
project has chosen by vote to recommend Jan Friedrich (freeandnil) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Piotr Karwasz is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Logging Services, and
BE IT FURTHER RESOLVED, that Jan Friedrich be and hereby is appointed to the
office of Vice President, Apache Logging Services, 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 7E, Change the Apache Logging Services Project
Chair, 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.
* Jean-Baptiste Onofré: provide template for next board report
[ StreamPark 2026-03-18 ]
Status: Done. Project now use the report template.
* Justin Mclean: monitor roll call or call for one
[ Flagon 2026-04-15 ]
Status: Done. Roll call done - 5 PMC members responded.
* 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.
* Justin Mclean: follow up about contributor
[ PDFBox 2026-04-15 ]
Status: Completed. Committer has high volume contributions, PRs closed but suggestions have been
applied with attribution, possibly due to read only mirror workflow? Asked
about committer nomination and project responded - up to them how they
proceed.
* Christofer Dutz: follow up on dev list about viability
[ Rya 2026-04-15 ]
Status: Completed. Sent a follow up email to private@ (on 17th of Mai) ... had missed this AE and
therefore it's probably too late for results in this meeting, just keep it
open and assigned to me.
Update 11.06.2026: Within almost one month to my latest post I didn't get a
single answer. I think it's time for a roll call on the dev list.
* Justin Mclean: look into contributor issue
[ Wayang 2026-04-15 ]
Status: Completed. Multiple PRs from contributors, including GSoC applicants, with no review.
Email sent and project responded.
* 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.
* Justin Mclean: include the last release date in the report
[ Impala 2026-05-20 ]
Status: Completed. email sent
* Justin Mclean: follow up with VP Privacy on Deep Wiki use
[ Ozone 2026-05-20 ]
Status: Completed. Email sent.
* 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:
* Emmanuel Lécharny: roll call for Xalan
[ Xalan 2026-05-20 ]
Status: Completed. The role call was unnecessary. In a discussion with Gary Gregory on the PMC
mailing list, he told me that a release has been done recently, and that there
are 3PMC member being active (Gary Gregory, Joseph Kesselman and Mukul
Gandhi)..
The thread is https://lists.apache.org/thread/9tk5wn6sjshyzqx83gd6lp74g9bkx92q
The security issues are going to be addressed.
* Christopher Schultz: discuss failed roll call and future direction
[ Kylin 2026-05-20 ]
Status: https://lists.apache.org/thread/fzy0hjl46fmy2w8c6woljjq0co5zff4j
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 21:47 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period May 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:
- Provided early naming advice to what became MAGPIE
- Approved the MAGPIE name
- Approved the use of ICEBERG and SPARK logos for conference booth material
- Responded to a request to use the KAFKA within a software product UI
- Provided early naming advice to SOLR for ORBIT
- Approved the TEXERA name
* REGISTRATIONS
Instructed counsel to renew our APACHE registration in Brazil.
Instructed counsel to renew our FLINK registration in the US.
Instructed counsel to renew our PDFBOX registration in the US.
Instructed counsel to renew our ACCUMULO registration in the US.
The transfer of the GRAILS marks to the ASF has completed.
Directed counsel to allow the OPENWHISK registrations in France to lapse.
* INFRINGEMENTS
Reached out regarding a website with potential infringements of KIE.
Requested advice from counsel regarding a registration application in the EU
that potentially conflicts with FLINK.
Took control of various namespaces created at codeberg.org using ASF marks.
A concern was raised regarding a downstream distribution of CAMEL. Closer
inspection did not identify any issues. The vendor was going the right things.
Feedback was provided to a vendor regarding the wording of an email marketing
campaign that referred to PULSAR.
No progress for the SPARK PMC in addressing a range of product naming issues
with multiple 3rd parties.
No progress regarding a site with a possible infringement of APISIX.
No further progress regarding the downstream vendor with multiple
infringements of ASF marks.
The XMLGRAPHICS PMC is progressing a complaint with GitHub regarding a
potential third-party infringement of FOP.
No progress from the GLUTEN PMC to address a range of product naming issues
with multiple 3rd parties.
There remains one issue with IOTDB to be solved.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Published blogs:
* Announcing Community Over Code Glasgow 2026
* Apache Geode 2.0, Part II by Jinwoo Hwang
* How Open Source Governs Itself: The Story Behind Apache STeVe v3 by Greg
Stein
* Approved content:
* MiMo 100T Token Grant
* Continued development of Annual Report, Alpha-Omega case study
* Mark Cox interviewed with Financial Times reporter Jamie John on the deluge
of AI slop and its effect on OSS maintainers
* Produced and issued May issue of Plus One newsletter
* Subscriber list now totals 3,980 (336 new subscribers in May)
* Total sent: 3,600 | Unique opens: 888 | Open rate: 25%
Project Comms
* Approved content:
* MITRE PR for Apache Caldera Incubator
* Snowflake PR for Apache Iceberg and Apache Polaris
Digital
* Community Over Code advertising on LinkedIn from 5/1 to 6/1 for TAC
* Community Over Code website project continued - finalized content,
wireframes, design, new logo design, Cvent schedule and registration page
review, newsletter
Social Media Overview
The highest performing pieces of content for May include project news, Daniel
Ruggeri’s appointment, and the Apache Iceberg spotlight.
Social Highlights (X + Bluesky + Fosstodon + LinkedIn)*
* Total Audience: 149,751
* X: 66,158
* Bluesky: 1,099
* Fosstodon: 212
* LinkedIn: 82,282
* Total Posts:
* X / Bluesky / Fosstodon / Bluesky: 41
* LinkedIn: 15
* Total Engagements: 4,890 (X 1,715 + LinkedIn 1,070 + BlueSky GraphTracks)
*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
727,845 visits, 727,725 unique visitors -9.3%
2 min 21s average visit duration -3.4%
60% visits have bounced (left the website after one page) -4.8%
2.2 actions (page views, downloads, outlinks, internal site searches) per
visit -4.3%
1,227,490 pageviews, 894,468 unique pageviews -11.9%
5 total searches on your website, 5 unique keywords -76.2%
99,204 downloads, 74,736 unique downloads -15%
268,067 outlinks, 180,724 unique outlinks -11.4%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Danny Angus]
General
-------
No issues currently require the Board's attention.
MFA Efforts
-----------
MFA soft-launch is ongoing with no service issues reported. Some UI/UX
suggestions were received and are being evaluated. Progress on migrating to a
more user-friendly hostname met with significant technical challenges which
have now been overcome, with finishing touches expected by the end of the week
of 15 June, followed by internal scaling up of service adoption.
Other News
----------
Infra, in collaboration with Tooling and Security, is developing a service
called the Contingent Approval Platform (CAP) which is intended to streamline
and automate procedural and technical votes. CAP provides a single ASF-wide
platform for recording project decisions, votes, approvals, and outcomes with
consistent rules and a permanent audit trail. It gives ASF projects and
services a shared, secure process for decision tracking, replacing ad hoc
voting logic with one canonical record and resolution link.
In our previous board report, Infra noted that a series of GitHub pull
requests containing suggestions for enabling security features in the
.asf.yaml service file was in the process of being deployed to all projects.
As of June 15th, all of the outstanding pull requests for this effort were
automatically merged by Infra to enforce ASF security standards.
Work continues to progress on the Atlassian Jira/Confluence cloud migration
project. A number of blockers have been resolved via collaborative efforts
with our Atlassian partners.
Community News
--------------
The June Infra Roundtable resulted in productive and on-going discussions
related to improving efficiency and equity of project utilization of the ASF's
GitHub runners. The July 1 Roundtable will feature a presentation on
predictive test analysis.
-----------------------------------------
Attachment 5: Report from the VP of Tooling [Dave Fisher]
## Tooling
### Apache Trusted Releases (ATR)
We are finishing all of the UI improvements and have soft launched Alpha3 in
early June. New features include releasing to a test repository: dist/atr. We
are working delivering important features including a full release catalog and
a .asf.yaml project feature.
In May the following releases were made using ATR:
- Cordova iOS 8.1.0
- Cordova Network Information Plugin 3.1.0
- Mahout 0.6
- Maven 3.9.16
- Maven Changelog Plugin 3.0.0-M2
- Maven Dependency Analyzer 1.17.1
- Maven Dependency Plugin 3.11.0
- Maven Enforcer 3.6.3
- Maven Parent POMs 48
- Maven Resolver 2.0.18
- NetBeans Maven Utilities 14.5
- (Maven) Apache Software Foundation Parent POM 38
Draft release candidates:
- DB JDO 3.3
- Maven Build Cache Extension 1.2.3
### Tooling President's Committee
In order to support contributions to tooling by non-staff volunteers we are
forming a Tooling committee: Dave Fisher, Thomas Neidhart, Sean Palmer,
Andrew Musselman, Alastair McFarlane, Hervé Boutemy, Tamás Cservenák,
Slawomir Jaranowski, and Daniel Gruno.
### ATR Maven Plugin
Some of the Maven PMC have joined with the tooling team to build a maven
plugin that will allow an ATR draft release to be uploaded with a mvn command.
### Board Agenda Tool (BAT)
Thomas continues to support BAT as a volunteer and Sander has been working on
some improvements.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
We are 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.
The co-located Lakehouse Day organized by Danica Fine has announced its
schedule, and registration for that on-day event is now open..
Work is still ongoing with the web team to update and expand
communityovercode.org, which should be launched this month.
The planning team has tentatively secured a venue for the 2027 North America
Community Over Code. A site visit is scheduled for September, 2026.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
===============
Community Over Code - Glasgow
---------------------------
Applications for this event closed on the 3rd June. A judges call happened on
the 7th June - the 2nd judges call for this event.
We ended up accepting 4 people from the 2nd round applicants of which there
were 27 applicants. We went back and accepted a further 8 from the initial
round applicants. Therefore a total 20 accepted from the 1st round and 4 from
the 2nd round.
Summary then is that we accepted 24 people from 63 applications, a record
amount of applicants.
Visa application supporting documentation provided to those that request it.
Flights and Hotels and Conference Tickets are all in progress of being booked
and paid for. (For those needing Visas, we only book and pay for these things
once we have a confirmed Visa approval)
Community over Code Asia - Beijing
----------------------------------
Applications for Beijing closed on May 31st; And a judges call happened on the
31st May. There were 23 applications altogether for this event and the Judges
ended up accepting 14 of those.
Flights and Hotel Bookings are under way for those that have Visas or are
local and do not need a Visa.
Monthly Meetings
=================
Trying to organize a meeting date to suit everyone.
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
=====================
No activity for May/June on the mailing list, other than commit activity for
website updates.
Membership
==========
No changes to the Committee this month. As membership changes rarely, I might
drop this section from the regular report and only add in when changes occur.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
# General
There are no issues that need urgent attention.
## Privacy Committee
The _privacy committee_ is a group of volunteers actively working for more
privacy towards the ASF. Committee members have become more active in
supporting projects for a few weeks.
## Privacy complaints / Removal requests
We have received multiple requests directed at VP-Privacy. The number of
private complaints is generally rising, and the requests usually look valid,
not automated.
## Drafting an AI recommendation
I have been drafting a recommendation on the use of AI from a privacy
perspective. Although I have already progressed far, I haven't yet completed
it. This draft will be sent to the privacy@ list for further feedback and
discussion first.
Several questions came up in the past weeks, asking for clarification.
# Open tasks
I am currently reviewing the accuracy of our documentation. For that reason, I
have not added any more open tasks.
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
EU Tech Sovereignty Package has been released
(https://digital-strategy.ec.europa.eu/en/policies/eu-tech-sovereignty) - with
a lot of attention paid to open source, open source community/ecosystems,
along with financial packages to directly support this.
Also published was the rules under which sharing the information of a security
vulnerability can be delayed:
https://eur-lex.europa.eu/eli/reg_del/2026/881/oj/eng. The delegated act on
the EU Common Criteria is expected later this month (no surprises expected).
CRA Expert Meeting, Brussels: As we're getting towards the implementation
phase; focus is shifting from what & how to do things - to execution and
keeping informed.
With that -- our attendance/role is no long that crucial/gets less meaningful.
i.e. this is winding down.
We see the national level regulators and market surveillance authorities now
engaging in earnest - and asking for clarifications (often much along the
lines of open source in the earlier phases). And we're seeing various
workstreams started to help the industry. The same is the case for SBOMs.
The IT community made good use of the guidance feedback opportunity; final
review is expected late this month. A lot of feedback/questions centred on the
edge cases of substantial change & combined works. It was made clear that the
guidance will not touch on the voluntary security attestation for FOSS and
interplay between them. Missing/delayed was the update/details on voluntary
attestation.
There was a demo of the Single Reporting Platform (into which we will need to
report from mid September onwards).
The ASF should participate
in testing early next month. Still pushback on the issue of ENISA as an entity
of last resort to report to (as the text does not allow for it) - but a
promise that some guidance will be given.
The issue of capacity with regard to notified bodies is now firmly on the
agenda - as is the fact that this means several orders of magnitude more
entities under a CE like all of a sudden.
-----------------------------------------
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]
Nothing to report this month.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
May
* The load of incoming security reports continues to grow significantly,
leaving limited time for other responsibilities. Taking on Piotr as
part-time contractor has been a great help, and we are working on automation
to more effectively handle the load. To help migitate this we also:
* Introduced an early preview of https://dash.security.apache.org/ ,
(auth and mfa required) which allows PMCs to self-service getting an
overview of their currently in-flight security reports.
* Made first steps towards setting up agent assistance to help support
initial triage.
* Process change experiments. We're seeing an increase in new reporters
reporting large batches of reports, where the majority look to be invalid.
We're asking the reporter to pick a low number of particularly severe and
convincing reports, so we can first triage these, and based on that decide
how to treat the rest of the batch. This has led to the new "reports held
back pending batch sampling" category in the report below.
* We're continuing to work with projects to make sure they're well-prepared
to have their codebases scanned by AI security tools.
Stats for May 2026:
47 [license confusion]
33 [reports held back pending batch sampling]
28 [support request/question not security notification]
20 [report/question relating to dependencies]
Security reports: 739 (last months: 515, 386, 200, 160, 98)
47 ['httpd']
46 ['airflow']
44 ['iceberg']
41 ['apisix', 'tomcat']
34 ['camel']
26 ['activemq']
23 ['superset']
22 ['polaris']
20 ['cxf']
16 ['web site or infra']
13 ['kafka']
12 ['cloudstack', 'commons', 'hertzbeat']
11 ['arrow', 'logging']
10 ['ofbiz', 'spark']
9 ['cassandra', 'dolphinscheduler', 'flink', 'pulsar',
'shenyu', 'zookeeper']
8 ['devlake', 'nifi', 'struts']
7 ['dubbo', 'mina', 'rocketmq', 'thrift']
6 ['doris', 'trafficserver']
5 ['answer', 'fory', 'inlong', 'parquet', 'shiro', 'vince']
4 ['druid', 'hadoop', 'hive', 'hugegraph', 'linkis', 'nuttx',
'orc', 'poi', 'skywalking', 'streampark']
3 ['artemis', 'fineract', 'hc', 'iotdb', 'lucenenet', 'pinot',
'pouchdb', 'seatunnel', 'solr', 'zeppelin']
2 ['beam', 'calcite', 'echarts', 'guacamole', 'ignite', 'james',
'knox', 'kvrocks', 'maven', 'openoffice', 'pdfbox', 'qpid',
'shardingsphere', 'tika', 'tvm', 'wicket', 'xmlgraphics']
1 ['amoror', 'archiva', 'atlas', 'avro', 'axis', 'baremaps',
'brpc', 'casbin', 'cordova', 'directory', 'eventmesh',
'fesod', 'gravitino', 'groovy', 'hamilton', 'hbase',
'hudi', 'iggy', 'jmeter', 'juneau', 'kylin', 'kyuubi',
'lucene', 'mxnet', 'netbeans', 'openmeetings', 'opennlp',
'paimon', 'plc4x', 'ranger', 'roller', 'sis', 'sling',
'syncope', 'velocity', 'ws']
In total, as of 1st June 2026, we're tracking 1139 (last months: 856, 629,
440) open issues across 149 projects, median age 51 days (last months: 44,
47, 64). 228 of those issues have CVE names assigned. 25 (last months: 32,
28, 22) of these issues, across 15 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-05-06)
* fineract (Health amber): there is one remaining open issues that is over a
year old, and quite a few untriaged. The PMC is making progress with
documentation, architectural changes and expanding the team, but not yet out
of the weeds. (Last update: 2026-05-06)
* 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-03-03)
-----------------------------------------
Attachment A: Report from the Apache AGE Project [Jeff Jirsa]
-----------------------------------------
Attachment B: Report from the Apache Airflow Project [Bolke de Bruin]
-----------------------------------------
Attachment C: Report from the Apache Allura Project [Dave Brondsema]
## Description:
The mission of Apache Allura is the creation and maintenance of software
related to a software development infrastructure platform commonly known as a
"forge"
## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: none
## Membership Data:
Apache Allura was founded 2014-03-18 (12 years ago)
There are currently 19 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Castillo on 2026-02-23.
- No new committers. Last addition was Daniel Castillo on 2026-02-24.
## Project Activity:
- starting to convert some PII fields to be encrypted
- change unexpected login email to use a link instead of code
- show domain on external links
- package updates
## Community Health:
- development is slow, mostly in maintenance mode, but "active maintenance"
keeping up with new versions of things and improving security posture
- RE: elecharny comment from board "Some activity, but isn't the project
entered into the "Open source is one person" category? Any way to get more
people involved?" There are several active contributors, albeit from one
employer that uses Allura. Overall adoption of Allura is quite low (and not
a very common thing for an individual to use themselves) so hard to get more
people involved.
-----------------------------------------
Attachment D: Report from the Apache Ant Project [J Pai]
## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build
system and related software components.
It consists of the following main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
## Project Status:
Current project status: Primarily in bug fix mode and maintenance mode.
Issues for the board: None for now.
## Membership Data:
Apache Ant was founded 2002-11-18 (24 years ago)
There are currently 29 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Magesh Umasankar on 2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-15.
## Project Activity:
The primary goal of Ant these days is to make sure that it can be used
to build projects using recent releases of Java. A new version of
Ant, 1.10.17, was released on April 10, 2026. This is a bug fix release.
A new Ant library has been recently created, which allows applications to
generate Software Bill Of Materials (SBOM) as part of their build. The
project, named "Apache CycloneDX Ant Library", resides at
https://ant.apache.org/antlibs/cyclonedx/index.html. Version 0.1 of that
library has recently been released.
The Ant project and Ant Ivy projects will be using this library, in their
build process, to generate a SBOM of their own for their releases.
A new release of Ant Ivy is currently being planned to release some bug
fixes that have accumulated in that project.
## Community Health:
Although we don't see too much development activity in Ant,
there are several active users of the Ant build tool. We
occasionally also see pull requests on GitHub. Recent work, by Stefan,
related to the Apache CycloneDX Ant Library has seen fresh activity
in the Ant and Ant Ivy projects.
For a project that's in maintenance mode, our amount of
activity, we believe, is decent.
-----------------------------------------
Attachment E: Report from the Apache Atlas Project [Madhanmohan Neethiraj]
## Description:
The mission of Apache Atlas is the creation and maintenance of software related
to a scalable and extensible set of core foundational governance services -
enabling enterprises to effectively and efficiently meet their compliance
requirements
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Atlas was founded 2017-06-20 (9 years ago)
There are currently 51 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- Radhika Kundam was added to the PMC on 2026-05-23
- Farhan Khan was added as committer on 2026-05-14
## Project Activity:
- Apache Atlas 2.5.0 was released on 2026-04-30
- performance improvements in asynchronous import
- fix performance issue in deleting array type business attribute
- Impala hook fix handling of INSERT OVERWRITE operation
- added aupport for typedef patch to disable index on attributes
- fix in import-kafka utility
- fixes and improvements in search APIs
- UI fixes
- upgraded dependent component libraries
## Community Health:
- 77 JIRA tickets opened and 79 closed in the past quarter.
- dev@atlas.apache.org had a 81% increase in traffic in the past quarter (1092
emails compared to 603)
- 40 commits in the past quarter (40 in the last report)
- 14 code contributors in the past quarter (8 in the last report)
## Recent releases:
- Apache Atlas 2.5.0 was released on 2026-04-30.
- Apache Atlas 2.4.0 was released on 2025-01-04.
- Apache Atlas 2.3.0 was released on 2022-12-06.
- Apache Atlas 2.2.0 was released on 2021-08-17.
- Apache Atlas 2.1.0 was released on 2020-07-15.
-----------------------------------------
Attachment F: Report from the Apache Axis Project [Robert Lazarski]
## Description:
The Apache Axis Project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components.
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Axis was founded 2009-12-15 (16 years ago, first commit was in 2001)
There are currently 65 committers and 64 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Christian Ortlepp on 2025-01-27.
- No new committers. Last addition was Andreas Lehmkühler on 2025-01-29.
## Project Activity:
Recent releases:
- Axis 2/Java 2.0.0 was released on May 27, 2026.
- Axis 2/Rampart 1.8.0 was released on Dec 10, 2024.
- Axis 2/C 1.6 was released on April 27, 2026.
- Axis 1.4 was last released in 2006.
## Community Health:
Both Axis2/Java (2.0.1) and Axis2/C (2.0.0) had releases this past quarter,
with nearly 100% of the same new contemporary features that further move the
projects from legacy SOAP and into the JSON era.
This includes http/2 protocol support, MCP protocol support for AI agents,
OpenAPI 3.0 support, field selection filtering to eliminate JSON response
params, and pagination of request data.
The Axis2/C community had 3 active committers in 2025 doing commits, though
not all of them are actively doing JSON development to modernize the project
in order to attract new committers - but they lurk the mailing lists and vote.
See the Android effort that intends to expand the devices that Axis2/C runs on
to gain attention, using Apache httpd for REST based transport control via
JSON:
https://github.com/apache/axis-axis2-c-core/blob/master/docs/HTTP2_ANDROID.md
The Axis2/Java community has different challenges to grow the active
committers due to the abundance of choices for REST and Java, but the
alternatives lack the new features that we added in 2.0.1 that we are
promoting as "One service, three protocols": JSON-RPC, MCP and REST+OpenAPI.
No other Java framework offers this; we expect some will find these features
compelling since our day jobs are demanding it.
Axis2/Java added two committers last year. We aim to attract more via
compelling features like those released in 2.0.1.
Apache Rampart 2.0.0 is nearly ready for release, but there are still open
issues that can be tracked below. It is a difficult project to support that
does WS-Security from two decades ago, with no active committers using it -
but a small community that does use it:
https://issues.apache.org/jira/projects/RAMPART/versions/12355237
-----------------------------------------
Attachment G: Report from the Apache Beam Project [Kenneth Knowles]
## Description:
The mission of Apache Beam is the creation and maintenance of software related
to a unified programming model for both batch and streaming data processing,
enabling efficient execution across diverse distributed execution engines and
providing extensibility points for connecting to different technologies and
user communities.
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Beam was founded 2016-12-20 (9 years ago)
There are currently 102 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Danny McCormick on 2024-12-12.
- Derrick Williams was added as committer on 2026-04-28
## Project Activity:
Recent releases:
- 2.74.0 was released on 2026-06-02.
- 2.73.0 was released on 2026-04-30.
First, highlighting major events:
- Beam College took place in late april
- Beam Summit will take place in a week
A theme of CDC work taking place in a few ways:
- Iceberg CDC support improved
- BigQuery CDC made more efficient
- BigQuery CDC streaming source for Python (previously just Java)
- Spanner ChangeStreams can union of TVF streams
- Persisting Debezium CDC offsets across pipeline restarts
- At the core of the Beam model, new per-element metadata being leveraged to
make streaming of CDC data through all transforms a "default" way of
processing
Compatibility / new versions / dropping dead versions
- added Flink 2.0 support
- added Spark 4 support
- added Python 3.14 support
- dropped Java 8 support
- minimum Go version to 1.26.1
- dropped SamzaRunner support
Google Summer of Code projects active & ongoing:
- Portable Kafka Streams Runner [kafka]
- Native Python Streaming Transforms [nativepy]
- Test Optimization & Monitoring System Integration [testopt]
[kafka] https://issues.apache.org/jira/browse/GSOC-305
[nativepy] https://issues.apache.org/jira/browse/GSOC-315
[testopt] https://issues.apache.org/jira/browse/GSOC-273
AI features:
- Qdrant vector database sink
- Google ADK Agent Handler
- Huggingface and Tensorflow image embedding for RAG
Connectors:
- Iceberg source had a ton of work
- Delta Lake source designed and implemented
- MQTT connector made available for Python use via multi-language pipelines
Other Designs
- Rust-based Python tooling [pyrust]
- Python Memory Profiling Capabilities: [pymem]
- AsyncDoFn for Java [async]
[pyrust] https://s.apache.org/beam-python-rust-tooling
[async] https://lists.apache.org/thread/x9jbvjvy8njnljo57y1f9lmssltxk022
[pymem] https://s.apache.org/beam-python-memory-profiling
## Community Health:
Nothing novel to report. Steady community health. We see a marked increase in
github@beam.apache.org emails which is a notification list that indicates dev
activity. There's been a lot of AI code and AI reviews which tend to move
quickly and generate noise.
-----------------------------------------
Attachment H: Report from the Apache Bigtop Project [Masatake Iwasaki]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around
the packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is
to Linux.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Bigtop was founded 2012-09-19 (14 years ago) There are currently 46
committers and 30 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhiguo Wu on 2024-08-19.
- No new committers. Last addition was Liqiang Fu on 2025-05-13.
## Project Activity:
Recent releases:
- bigtop-manager-1.1.0 was released on 2025-12-04.
- 3.5.0 was released on 2025-09-07.
- 3.4.0 was released on 2025-05-30.
We are preparing for the next 3.6.0 release addressing upgrading Hadoop to 3.4
[1][2]. We need some more effort for aligning the versions of product in the
stack since some downstream products dropped Java 8 support while Hadoop 3.4
requires Java 8 for release build.
ARM virtual machnines provided by Linaro are no longer available. We are using
local Mac of release manager for building and testing ARM binaries now.
[1] https://issues.apache.org/jira/browse/BIGTOP-4520
[2] https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/
## Community Health:
- dev@bigtop.apache.org had a 152% increase in traffic in the past quarter
(101 emails compared to 40):
- issues@bigtop.apache.org had a 76% increase in traffic in the past quarter
(37 emails compared to 21):
- 14 JIRA tickets opened and 17 closed in the past quarter.
-----------------------------------------
Attachment I: Report from the Apache BVal Project [Matt Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache BVal was founded 2012-02-14 (14 years ago)
There are currently 17 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Markus Jung on 2024-07-08.
## Project Activity:
Recent activity has been limited to dependency management.
## Community Health:
No change in activity; BVal remains dormant despite a jump in mailing list
activity.
-----------------------------------------
Attachment J: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Camel was founded 2008-12-17 (17 years ago)
There are currently 95 committers and 49 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Aurélien Pupier was added to the PMC on 2026-05-11
- No new committers. Last addition was Luigi De Masi on 2026-02-27.
## Project Activity:
Apache Camel:
- We released Camel 4.14.6
- We released Camel 4.14.7
- We released Camel 4.18.1
- We released Camel 4.18.2
- We released Camel 4.19.0
- We released Camel 4.20.0
- Note: Camel releases have synchronized releases of Camel-Spring-Boot too
for 4.x.
- 4.18.x and 4.14.x are our LTS release trains. 4.14.x LTS will reach end
of support on 2026-08-20.
- Camel 4.19.0 is the first release to support Spring Boot v4. Spring Boot v3
is no longer supported starting from 4.19.
- We introduced the Camel MCP Server, a Model Context Protocol server that
exposes the Apache Camel Catalog and specialized tools to AI coding
assistants. In 4.19.0 the MCP Server received significant improvements,
bringing the total tools to 19.
- Four new components providing Jackson 3 support were added in 4.19.0.
- The situation is really healthy and the community is increasing presence and
engagement. We are removing support for JDK 17 and focusing only on JDK 21
and 25. Java 25 compatibility work is ongoing.
Apache Camel K:
- We released Camel K 2.10.0
- The release includes GitOps support extended to Pipes, and the ability to
combine GitOps with dry-build for complete build and deployment pipelines
without running the application on a development environment.
- The operator was built with Golang 1.25 and Kubernetes API aligned with
version 1.35.
- Camel K is in good shape and the community is expanding with more
contributors and feedback. The situation is healthy.
Apache Camel Kamelets:
- We released Camel Kamelets 4.18.1
- We released Camel Kamelets 4.18.2
- We released Camel Kamelets 4.19.0
- We released Camel Kamelets 4.20.0
- We released Camel Kamelets 4.14.6
- We released Camel Kamelets 4.14.7
- The Kamelet catalog keeps growing.
- Documentation has been improved even more.
- The 4.14.x and 4.18.x release trains are matching the LTS releases from
Camel core.
Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
multiple releases.
- We released Camel-Quarkus 3.27.3
- We released Camel-Quarkus 3.27.4
- We released Camel-Quarkus 3.33.0
- We released Camel-Quarkus 3.33.1
- We released Camel-Quarkus 3.35.0
- We are increasing the number of Camel Quarkus Extensions to match the core
components. We are supporting 4.14.x LTS and 4.18.x LTS.
- The community is active and we are seeing increased interest.
Apache Camel-Karavan:
- Camel-Karavan is still growing.
- We released version 4.18.0, supporting the latest LTS release.
- The new version includes editable built-in documentation, light and dark
mode support, and was updated to PatternFly 6.x.
Camel-Kafka-Connector:
- We released Camel-Kafka-Connector 4.18.0
- We released Camel-Kafka-Connector 4.14.5
- These are the first releases supporting the latest Camel LTS 4.18.0 and
aligning with the Kamelets catalog.
- The community is active and we receive a lot of feedback and requests. We
are improving the documentation and we're trying to keep the same cadence as
core.
Apache Camel-Karaf:
- We released Camel-Karaf 4.14.5
- We released Camel-Karaf 4.14.7
- We released Camel-Karaf 4.18.1
- We released Camel-Karaf 4.8.9
- We are now supporting both 4.14.x LTS and 4.18.x LTS.
Apache Camel-Upgrade-Recipes:
- Camel-Upgrade-Recipes 4.19.0 has been released
- Camel-Upgrade-Recipes 4.20.0 has been released
- This version supports upgrades up to 4.20.0 and supports Java 17, 21 and
- The plan is to keep supporting 4.14.x LTS and 4.18.x LTS.
## Community Health:
Dev and issues mailing lists remained active this quarter, with discussions
around the Spring Boot v4 migration and Jackson 3 adoption. The move to
Spring Boot v4 in 4.19.0 was a significant milestone that generated healthy
discussion. The MCP Server introduction attracted interest from the AI
community. There was a slight decrease on the users mailing list, mainly
because we are using Zulip for discussing and sometimes contributors use
Zulip as first interaction point instead of the ML. In terms of Github
engagement we are doing really well and we see new contributors and
reporters. We had 25 unique contributors on the core repository this quarter
with over 2300 commits across all branches. I think the community is really
growing and the pace of releases this quarter demonstrates the project's
vitality.
-----------------------------------------
Attachment K: Report from the Apache Cayenne Project [Michael Gentry]
# Apache Cayenne Board Report, June 2026
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object graph persistence and provides an ORM
runtime, remote persistence services*, and a cross-platform GUI
database mapping/modeling/development tool.
*Remote persistence services are being phased out for 5.0 (milestone
stage) to simplify the product. We could only identify one user of this
feature and he is switching to RESTful services.
## Project Status
### Project State
Ongoing
### Issues for Board
None
## Membership Data
Apache Cayenne was founded 2006-12-19 (19 years ago).
There are currently 24 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Jurgen Doll on 2024-08-27.
## Project Activity
After the release of 4.2.x, most development has shifted to 5.0. Versions
prior to 5.0 are maintenance-only.
Release artifacts for 5.0 Milestone 2 are currently being prepared.
- Cayenne 4.0.x (stable)
- Maintenance only.
- Cayenne 4.1.x (stable)
- Maintenance only.
- Cayenne 4.2.x (stable)
- Maintenance only.
- Cayenne 5.0 (milestone)
- New features and primary development.
### Releases
- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2.3 on 2025-11-19.
- Cayenne 5.0.M1 on 2024-09-09.
## Community Health
Cayenne is healthy.
Development mailing list traffic is up due to 5.0 Milestone 2 preparations
and discussions.
User mailing list traffic is up due to user questions and 5.0 Milestone 2
feedback and notices of planned changes (such as needing Java 21). Questions
continue to be answered in a timely manner.
Jira/Git activity was up due to 5.0 Milestone 2 preparations.
-----------------------------------------
Attachment L: Report from the Apache CloudStack Project [Wido den Hollander]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage, and
networking devices.
## Project Status:
Current project status: Ongoing, with high activity
Issues for the board: None
## Membership Data:
Apache CloudStack was founded 2013-03-19 (13 years ago)
There are currently 147 committers and 63 PMC members in this project.
The Committer-to-PMC ratio is 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Fabricio Duarte Junior on 2026-02-26.
- Rositsa Kyuchukova was added as committer on 2026-03-11
## Project Activity:
Software development/management activity:
- The current version of Apache CloudStack is 4.22.1.0.
- The versions released in the past quarter are:
- 4.22.1.0 was released on 2026-05-26
- 4.20.3.0 was released on 2026-04-27
- 4.22.0.1 was released on 2026-04-27 (Security Release)
- We are working on more security reports and working on their fixes.
- The latest CloudStack Kubernetes Provider version 1.2.0 was released on
December 29, 2025.
- The latest CloudStack Terraform provider version 0.6.0 was released on
October 28, 2025.
Meetups and Conferences:
- The Apache CloudStack project exhibited at CloudFest on March 23-26th, 2026
in Rust, Germany: https://cloudstack.apache.org/blog/cloudfest-2026
- The CloudStack European User Group 2026 was held on May 21, 2026 in
Hague, Netherlands: https://cloudstack.apache.org/blog/cseug26-roundup
- The CloudStack community will attend the Community Over Code EU 2026 on
October 11-14 in Glasgow, Scotland; with a confirmed track for CloudStack:
https://cloudstack.apache.org/blog/coceu26
- The CloudStack Collaboration Conference 2026 is scheduled for November 18-20
in Edinburgh, Scotland: https://www.cloudstackcollab.org/.
## Community Health:
- According to the reporter tool, the Community Health Score (Chi) is
10.00 (Super Healthy).
Mailing lists statistics:
- dev@cloudstack.apache.org had a 11% decrease in traffic in the past quarter
(339 emails compared to 379
- issues@cloudstack.apache.org had a 110% increase in traffic in the past
quarter (82 emails compared to 39)
- marketing@cloudstack.apache.org had a 46% increase in traffic in the past
quarter (19 emails compared to 13)
- users@cloudstack.apache.org had a 28% decrease in traffic in the past
quarter (1027 emails compared to 1408)
Recent releases:
- 4.22.1.0 was released on 2026-05-26.
- 4.22.0.1 was released on 2026-04-27.
- 4.20.3.0 was released on 2026-04-27.
-----------------------------------------
Attachment M: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java focused
reusable libraries and components
## Project Status:
Current project status: Ongoing.
Issues for the board: None.
## Membership Data:
Apache Commons was founded 2007-06-19 (19 years ago)
There are currently 150 committers and 44 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Arnout Engelen on 2024-12-22.
- No new committers. Last addition was Arnout Engelen on 2024-12-23.
## Project Activity:
Activity in this reporting period includes a small number of releases:
- PARENT-101 was released on 2026-06-03.
- STATISTICS-1.3 was released on 2026-05-05.
- RNG-1.7 was released on 2026-04-21.
- NUMBERS-1.3 was released on 2026-04-20.
- NET-3.13.0 was released on 2026-03-18.
More releases are forthcoming, driven by many AI generated reports, as well as
regular pull requests on GitHub, and Jira tickets.
We are considering the addition of a new small component called XML Commons
focused on providing secure JAXP XML Objects.
We've had a successful interaction with a user to merge a large batch of fixes
based AI generated reports and code to the Common Lang project.
We've signed up our active repositories to our Mythos/Glasswing effort.
## Community Health:
I would say the health is balanced in the sense that while we have a small
number of active committers, we are regularly merging pull requests. We are
actively engaged with the Apache Security Team in triage, and coordinating
issues.
-----------------------------------------
Attachment N: Report from the Apache Cordova Project [Bryan Ellis]
## Status report for the Apache Cordova project - June 2026
## Description
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Project Status
**Current project status:**
Our current work focuses on staying up to date by making improvements to our
release process, plugins, and core platforms.
Our status dashboard at https://apache.github.io/cordova-status/ remains
mostly all green.
**Issues for the board:**
There are no issues requiring board attention at this time.
## Membership Data
There are currently 100 committers and 97 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
**Community changes, past quarter:**
- No new PMC members. Last addition was Manuel Beck on 2025-04-04.
- No new committers. Last addition was Manuel Beck on 2025-04-04.
## Project Activity
The following releases were made to our project this quarter:
**Releases:**
- cordova-plugin-inappbrowser@6.0.1 was released on 2026-06-07.
- cordova-ios@8.1.0 was released on 2026-05-31.
- cordova-plugin-network-information@3.1.0 was released on 2026-05-16.
- cordova-ios@8.0.1 was released on 2026-03-12.
The following security issue(s) were also resolved:
- [CVE-2026-47430: Cordova Plugin InAppBrowser: iOS: Arbitrary Cordova
callback IDs can be dispatched without validation from InAppBrowser
WebViews.](https://cordova.apache.org/announcements/2026/06/07/inappbrowser-release-6.0.1.html)
## Community Health
Overall, the community health is strong. The ASF Project Statistics gives the
project a Community Health Score (Chi): 4.70 (Healthy)
This quarter, we primarily focused on improving our iOS platform, plugins, and
release process.
We continue to see valuable contributions from a dedicated group of
individuals who actively test, report issues, and submit PRs to address their
findings in future releases. A large portion of this quarter's activity has
focused on improvements to the In-App Browser plugin, as well as the iOS and
Android platforms. There have also been a small number of contributions to
other plugins, tooling, and platforms.
Overall, the project remains stable and continues to see strong activity.
Github discussions is how our community supports each other and is live at
https://github.com/apache/cordova/discussions. All discussions are forwarded
to the 'issues' list.
## Mailing List Activity
- dev@cordova.apache.org had a 64% increase in traffic in the past quarter (92
emails compared to 56)
- issues@cordova.apache.org had a 28% increase in traffic in the past quarter
(1445 emails compared to 1122)
-----------------------------------------
Attachment O: Report from the Apache CouchDB Project [Jan Lehnardt]
-----------------------------------------
Attachment P: Report from the Apache cTAKES Project [Pei J Chen]
## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache cTAKES was founded 2013-03-19 (13 years ago) There are currently 40
committers and 30 PMC members in this project. The Committer-to-PMC ratio is
4:3.
Community changes, past quarter:
- Dennis Johns was added to the PMC on 2026-03-10
- No new committers. Last addition was Dennis Johns on 2023-01-06.
- After a roll-call, two PMC members requested to be removed since they were no
longer involved.
## Project Activity:
- Committee continues to work on the future release (7.x.x)
- 6.0.0 was released on Sept 16 2024
- 5.1.0 was released on May 10 2024
- 4.0.0.1 was released on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
## Community Health:
Mailing lists are fairly low on traffic. dev@ctakes.apache.org had a 50%
increase in traffic in the past quarter
(3 emails compared to 2)
Discussions should be done on the mailing lists, but there are occasional
items on git issues tracking: https://github.com/apache/ctakes/issues.
-----------------------------------------
Attachment Q: Report from the Apache Curator Project [Enrico Olivelli]
-----------------------------------------
Attachment R: Report from the Apache Daffodil Project [Steve Lawrence]
## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data Format Description Language (DFDL)
used to convert between fixed format data and more readily processed forms
such as XML or JSON
## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: None
## Membership Data:
Apache Daffodil was founded 2021-02-16 (5 years ago) There are currently 22
committers and 21 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- Hitesh Dalsania was added to the PMC on 2026-06-04
- Steve Lawrence approved as new chair on 2026-04-15
- Larry Barber passed vote for PMC, awaiting documentation
## Project Activity:
- Daffodil SBT plugin 1.7.0 was released on 2026-03-18
- Daffodil and Daffodil SBT plugin have an expected release at the end of
June, including a number of new features and bug fixes
- In the last quarter, 33 pull requests have been created and 25 pull requests
have been merged
## Community Health:
Developer and commit activity are still good. Most activity takes place on
Github/JIRA so email activity on the dev and users lists is fairly quiet.
Project saw a couple of pull requests from first-time contributors. There are
approximately a dozen core active contributors across the main Daffodil
library and Daffodil VS Code projects.
-----------------------------------------
Attachment S: Report from the Apache DataFusion Project [Andrew Lamb]
## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine
## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache DataFusion was founded 2024-04-16 (2 years ago)
There are currently 58 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Adrian Garcia Badaracco on 2026-02-01.
- Bhargava Vadlamani was added as committer on 2026-04-28
- Kumar Ujjawal was added as committer on 2026-04-28
## Project Activity:
Note that almost all communication for DataFusion and its subprojects happens
on github and so our dev mailing list traffic is fairly light.
### DataFusion core
https://github.com/apache/datafusion
54.0.0 was released on 2026-06-09.
53.1.0 was released on 2026-04-16.
53.0.0 was released on 2026-03-23.
52.5.0 was released on 2026-04-11.
52.4.0 was released on 2026-03-22.
52.3.0 was released on 2026-03-12.
Our releases now consist of contributions from over 120 distinct contributors
(was 100), and we average around [9.2 commits per day] to the main repo (up
from [7.8 commits per day])
[9.2 commits per day]: git rev-list --count apache/main --since='2026-03-10
00:00:00' --until='2026-06-08 23:59:59'
[7.8 commits per day]: git rev-list --count apache/main --since='2026-02-09
00:00:00' --until='2026-03-09 23:59:59'
The community continues to write blogs highlighting our work, see
https://datafusion.apache.org/blog/
We continue to hold small scale in person meetups in various locations, which
have been successful in bringing together contributors. We had events in
Portland, Seattle, NYC, and Stockholm, and are trying to hold more in Asia,
such as in China. See a list here:
https://datafusion.apache.org/user-guide/concepts-readings-events.html#community-events
The overall number of PRs in need of review has been growing, likely due to
increasing use of AI coding tools and the overall growth of the community.
As the project matures, time is extending between major releases, likely due
to increased testing and attention to quality.
### Sub project: DataFusion Python
https://github.com/apache/datafusion-python DATAFUSION-PYTHON-53.0.0 was
released on 2026-04-12. DATAFUSION-PYTHON-52.3.0 was released on 2026-03-16.
In version 53.0.0 we introduced new AI workflows into the project. The primary
outcome of this is to provide a method to ensure we have consistent coverage
between the exposed datafusion-python APIs and the upstream functions in the
core repository. This workflow exposed 55 function gaps between the two
repositories that were then corrected.
Additionally the datafusion-python project went through a massive overhaul in
the documentation of the API surface area to include usage docstrings directly
aimed at improving the ability for LLM agents to write effective
datafusion-python code.
We have additionally released an agent skill that improves the ability of LLMs
to write idiomatic datafusion-python code. This has been tested against the
TPC-H queries where agents can now faithfully reproduce queries to pass these
tests using only the text description of the query.
Since the release of 53.0.0 we have added two new LLM skills to complement the
above work. First we added a skill that ensures all of the newly exposed
functions are “pythonic” in nature rather than just exposing the Rust
interface directly. Second we have a skill that verifies that the user facing
skill to write idiomatic code is kept up to date with the API surface area of
the project.
We have published a blog based on the experience of writing these agent
skills. You can read it here:
https://datafusion.apache.org/blog/2026/05/28/writing-agent-skills/
### New sub project: DataFusion Java
We have added Java Bindings as a subproject. You can read about it here:
https://datafusion.apache.org/blog/output/2026/05/26/datafusion-java-0.1.0/
### Sub project: DataFusion Comet
COMET-0.16.0 was released on 2026-01-29.
https://github.com/apache/datafusion-comet
You can read about the recent happenings in Comet in the blogs:
https://datafusion.apache.org/blog/2026/05/07/datafusion-comet-0.16.0
### Sub project: DataFusion Ballista
https://github.com/apache/datafusion-ballista BALLISTA-53.0.0 was released on
2026-05-24 BALLISTA-52.0.0 was released on 2026-03-07. BALLISTA-51.0.0 was
released on 2026-01-19.
The community has published new post outlining changes to ballista in last 12
months
https://datafusion.apache.org/blog/output/2026/05/24/datafusion-ballista-53.0.0/
There has been an increase of number contributions to Ballista, and PR
reviews, which is very positive. Efforts were focused on improving
observability of running jobs and usability. With hope to improve ballista
robustness and performance for SF1000+ workloads. I hope this trend of
increased contributions is going to persist in the future.
### Sub project: sqlparser-rs
SQLPARSER-0.62.0 was released on 2026-05-27.
https://github.com/apache/datafusion-sqlparser-rs
Ifeanyi Ubah (iffyio) continues to review most PRs in this repo.
## Community Health:
While we as always struggle with code review capacity,
we have many active committers, and the community in general helps each
other out with reviews. We continue to actively grow our committer
and PMC ranks.
We continue to merge multiple PRs a day from multiple committers and
have contributions from a wide variety of individuals with a wide
variety of employers, organizations, and backgrounds.
-----------------------------------------
Attachment T: Report from the Apache DevLake Project [Hezheng Yin]
Apache DevLake — Board Report (Month 9-11 as Top-Level Project)
Reporting period: Mar 2026 - May 2026
Submitted by: Henry (Hezheng) Yin (PMC Chair, Apache DevLake)
- Project description
Apache DevLake is an open-source DevData platform that collects, transforms,
and visualizes engineering and DevOps data from sources like GitHub, Jenkins,
and Jira to help teams understand and improve their software delivery
performance through metrics and dashboards.
- Project status
Status: Ongoing / Growth phase
The project continues to mature as a Top-Level Project. We released three
beta versions of v1.0.3 during this period, with a strong focus on AI
integration, security hardening, and expanding the plugin ecosystem.
Community activity remains healthy with continued contributions from both
established and new contributors.
- Community and project activity
Two new committers were voted in this period:
- Tomoya Kawaguchi
- Eldrick Wega
Significant engineering activity has been observed in:
- AI Integration & Q-Dev Dashboards: Continued expansion of AI-related
analytics with new dashboards including Multi-AI Tool Comparison (#8794),
Language AI Heatmap (#8796), Developer AI Productivity Hours (#8797),
Kiro AI Model ROI (#8795), and AI Cost-Efficiency (#8793). GitHub Copilot
plugin received multiple stability fixes (#8825, #8826, #8804, #8779).
- New Integrations: Added Rootly incident-management plugin (#8877, #8892),
Claude Code metrics integration (#8808),
and Tempo (Jira Timesheets) support.
- Security Hardening: Migrated AES encryption from CBC to GCM with backward
compatibility (#8895), fixed multiple credential-leak paths in gitextractor
(#8872), implemented encryption for Asana connection tokens (#8873), and
hardened dbt pipeline inputs (#8878).
- Authentication & UI: Implemented OIDC authentication and session management
(#8854) and introduced a dark theme for the UI (#8865).
- GitHub Improvements: Added incremental data collection (#8858) and fixed
GraphQL client token refresh issues (#8788, #8855).
- Releases
v1.0.3-beta12 — Released 2026-04-26
v1.0.3-beta11 — Released 2026-04-25
v1.0.3-beta10 — Released 2026-03-12
- Issues for the Board
No critical Board-level issues at this time.
- Community health
Active committers this period: ~12
New committers: 2 (Tomoya Kawaguchi, Eldrick Wega)
New PMC members: None this period
Merged PRs: 80 (73 apache/devlake, 7 apache/devlake-website)
Issues created: 62 / closed: 56
Mailing list traffic: Moderate
No major conflicts or community issues reported
- Roadmap / upcoming work
AI & Copilot — Finalize GitHub Copilot metrics and continue expanding
q-dev AI analytics dashboards.
Performance — Continue optimizations for large-scale data calculations
and incremental collection stability.
Integrations — Complete Tempo plugin, improve GitHub App support and
token management.
Security — Complete remaining security audit items and harden plugin
isolation boundaries.
Documentation — Onboarding improvements and documentation for new AI
features and integrations.
- Additional commentary
We are seeing strong interest in AI-related metrics and security hardening.
Focus remains on stabilizing v1.0.3 for general availability release while
expanding the integration ecosystem.
-----------------------------------------
Attachment U: Report from the Apache Drill Project [Charles Givre]
## Description:
The mission of Drill is the creation and maintenance of software related to
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage
## Project Status:
Current project status: Ongoing
Issues for the board: No issues for board consideration.
## Membership Data:
Apache Drill was founded 2014-11-18 (12 years ago)
There are currently 62 committers and 28 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 Maksym Rymar on 2025-09-30.
- No new committers. Last addition was Maksym Rymar on 2022-10-19.
The PMC approved Steve Lawrence as a new committer and his paperwork is
in progress.
## Project Activity:
We are preparing a new release and will likely release it in the end of June
or early July.
There are several large segments of work in flight:
1. A complete UI refactor. (Very major)
2. Support for Materialized Views
3. Storage plugin for Microsoft Sentinel
4. Update to Apache Calcite to version 1.42.
The long awaited integration between Apache Daffodil and Drill has been
approved and will be merged shortly.
Recent Releases
1.22.0 was released on 2025-06-28.
1.21.1 was released on 2023-04-29.
1.21.0 was released on 2023-02-21.
## Community Health:
This quarter was fairly quiet. However, there is additional activity on the
"unofficial" slack channel, but I've not found metrics on that.
* dev@drill.apache.org had a 16% decrease in traffic in the past quarter
(50 emails compared to 59)
* issues@drill.apache.org had a 65% decrease in traffic in the past quarter
(14 emails compared to 40)
* user@drill.apache.org had a 60% decrease in traffic in the past quarter
(8 emails compared to 20)
* 2 JIRA tickets opened and 0 closed in the past quarter.
-----------------------------------------
Attachment V: Report from the Apache Druid Project [Abhishek Agarwal]
-----------------------------------------
Attachment W: Report from the Apache ECharts Project [Wenli Zhang]
## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript
## Project Status:
Current project status: Ongoing
Issues for the board: NA
## Membership Data:
Apache ECharts was founded 2020-12-16 (5 years ago) There are currently 31
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was ShiZhao Pan on 2025-01-09.
- No new committers. Last addition was Zisen Jin on 2025-11-01.
## Project Activity:
We released v6.1.0 recently on 2026-05-19 and are working towards v6.1.1,
which will contain some small bug fixes. Recently, we have fixed a series of
reported or publicized the potential security issues of ECharts.
## Community Health:
The overall community health of ECharts is good. There's a steady influx of
new developers contributing to the project. Regular discussions on GitHub
issues and mailing lists keep the ideas flowing. Bugs are identified and fixed
in a timely manner. The release of new versions with enhanced features
showcases the community's vitality and collaborative efforts to keep ECharts
evolving.
-----------------------------------------
Attachment X: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Project Status:
Current project status: Ongoing, with very low activity.
Issues for the board: none.
## Membership Data:
Apache Felix was founded 2007-03-28 (19 years ago)
There are currently 68 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Paul Rütter on 2025-06-16.
- No new committers. Last addition was Paul Rütter on 2024-11-15.
## Project Activity:
Existing implementations have been improved/enhanced based on community
feedback.
Released 3 components.
Recent releases:
* org.apache.felix.http.jetty12-1.2.0 was released on 2026-06-02.
* org.apache.felix.http.jetty12-2.0.0 was released on 2026-06-01.
* org.apache.felix.http.bridge-6.1.2 was released on 2026-03-15.
## Community Health:
Overall the project is in ok health with very little ongoing activity.
The community activity remains on a low level and we continue to see little
new development right now.
Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues. Traffic has
been very low.
We had no issues voting on releases (but some wait time) and JIRA issues are
generally addressed.
-----------------------------------------
Attachment Y: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment Z: Report from the Apache Flink Project [Robert Metzger]
## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing
## Project Status:
Current project status: None
Issues for the board: None
## Membership Data:
Apache Flink was founded 2014-12-17 (11 years ago)
There are currently 128 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- David Anderson was added to the PMC on 2026-05-06
- Gustavo de Morais was added as committer on 2026-05-20
- Peter Huang was added as committer on 2026-04-28
- Wenjin Xie was added as committer on 2026-04-10
- Hao Li was elected as committer (vote concluded 2026-06-05); onboarding in
progress.
## Project Activity:
The 2.3 release is in its final stages. Following the March 31 feature freeze
and an April 15 branch cut, the release is now in release-candidate voting
(RC3 cut on June 5), managed by David Anderson, Hao Li, and Yuepeng Pan.
* The community shipped a coordinated maintenance wave across all supported
release lines in May, driven largely by a RCE CVE we've published: 1.20.4
(May 6), 2.0.2 and 2.1.2 (both May 11), and 2.2.1 (May 15), with 1.20.5
currently in RC.
* Flink Kubernetes Operator 1.15.0 was released on May 26.
* Flink CDC 3.6.0 (March 30)
* Flink Agents 0.2.1 (March 26)
The community accepted roughly 10 FLIPs this quarter.
Following last quarter's discussion, the proposal to sunset the dormant
Stateful Functions (StateFun) sub-project was formalized as FLIP-569 and moved
to a vote on May 26 with strong community support.
The quarter saw a sharp rise in security reports — roughly two dozen distinct
vulnerabilities (versus the usual handful) and at least two reserved CVEs —
spanning Flink core (SQL Gateway SSRF, deserialization-based RCE), the
Kubernetes Operator, and the CDC and Agents sub-projects. We assume the
increased volume is due to LLMs. We've published a first version of a thread
model on our website to help evaluate reports more quickly.
## Community Health:
Mailing-list trends continue to diverge: dev@ is healthy and rebounded to
~580 messages in May (its highest month in over a year, +39% in the past Q),
while user@ has fallen to ~15 messages/month (down roughly 80%
year-over-year) as user questions move to Slack, Stack Overflow, and LLM
assistants.
Connector maintenance remains a standing concern — repositories such as
flink-connector-aws still struggle to attract reviewers and release voters
beyond their primary vendors — though this quarter's Kafka, Pulsar, and HTTP
connector releases reflect progress.
-----------------------------------------
Attachment AA: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AB: Report from the Apache Gobblin Project [Abhishek Tiwari]
## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Gobblin was founded 2021-01-19 (5 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was Abhishek Mahendra Jain on 2025-01-18.
## Project Activity:
_ Removed WARN log aggregation from AutomaticTroubleshooter to reduce noisy
issue reporting.
- Fixed RecursiveCopyableDataset handling for empty source directories by
skipping directory entries during recursive copy.
- Restored backward compatibility in Gobblin-Iceberg partition handling where
CURRENT_DATE produces the expected '-00' suffix.
- Fixed a null pointer exception when accessing the current snapshot for
Iceberg tables with no snapshot.
- Increased Temporal gRPC retry budget to better tolerate throttling and
improve workflow resilience.
- Added configurable partition filtering with hourly lookback support for
Gobblin-Iceberg workflows.
- Added flow-group prefix based concurrency overrides for better control of
workflow execution.
- Added batched parallel processing to ManifestBasedDataset to improve
copy-discovery and manifest-processing performance.
- Tuned RPC retry policy to tolerate short Temporal gRPC throttling windows.
- Parallelized flow compilation on the submission path to improve GaaS
submission latency.
## Community Health:
Since the Mar 2026 report, there have been 10 commits. Activity this quarter
continued to focus on Gobblin reliability, GaaS orchestration
performance, Iceberg compatibility, and manifest-based copy improvements.
Recent contributions came from multiple contributors across the Gobblin
community, including both established and relatively newer contributors.
Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as committers. We
constantly look for consistent contributors to vote them in as Committers.
-----------------------------------------
Attachment AC: Report from the Apache Gravitino Project [Jerry Shao]
## Description:
The mission of Apache Gravitino is the creation and maintenance of software
related to managing your data and AI assets seamlessly with a flexible, unified
governance framework, including lakehouse federation capabilities
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-20 (a year ago)
There are currently 30 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- Minghuang Li was added to the PMC on 2026-03-26
- He Qi was added to the PMC on 2026-03-26
- Bharath Krishna was added as committer on 2026-03-27
## Project Activity:
Software Development Progress in this period:
1. Apache Gravitino 1.2.1 released at May 11, 2026.
2. Apache Gravitino 1.3.0 is in RC vote phase.
Community Activity:
1. Monthly Data & AI meetup in Bay Area to have Gravitino talk.
2. Held a China-local Gravitino user meeting at May.
## Community Health:
1. dev@gravitino.apache.org had a 19% increase in traffic in the past quarter
(142 emails compared to 119)
2. 432 issues were created last quarter, which had a 6% slight decrease (438
compared to 464).
3. 710 PRs were created last quarter, which had a 20% increase (710 compared to
592).
-----------------------------------------
Attachment AD: Report from the Apache Guacamole Project [Mike Jumper]
-----------------------------------------
Attachment AE: Report from the Apache Gump Project [Stefan Bodewig]
## Description
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well as
non-ASF projects and their dependencies. It started in the Java part
of the foundation but also builds projects like APR, HTTPd and
OpenSSL.
## Project Status
Current Status: dormant - when things need to be done, they get done
Issues: There are no issues requiring board attention.
## Membership Data
Apache Gump was founded 2004-02-18. There are currently 16 committers
and 10 PMC members in this project. The Committer-to-PMC ratio is
8:5.
Community changes, past quarter:
No new PMC members. Last addition was Mark Thomas on 2014-12-03.
No new committers. Last addition was Konstantin Kolinko on 2015-02-11.
## Project Activity
The Tomcat community is the only one still using Gump actively and the
only activity in Gump is around keeping the infrastructure alive and
tweaking things for the benefit of Tomcat builds.
We will certainly support any other project that wants to get the
benefit of the early warning system for backwards incompatible changes
Gump provides, but we are not actively recruiting projects.
## Releases
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
## Community Health
There isn't much happening but help is there when anybody needs it.
-----------------------------------------
Attachment AF: Report from the Apache Helix Project [Junkai Xue]
## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources
## Project Status:
Current project status: Ongoing, Low
Issues for the board: N/A
## Membership Data:
Apache Helix was founded 2013-12-17 (12 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- No new committers. Last addition was Molly Gao on 2023-06-06.
## Project Activity:
- 2.0.0 was released on 2026-06-03
- 1.3.2 was released on 2025-07-02
- 1.4.3 was release on 2025-01-29
## Community Health:
- Apache Helix 2.0.0 release out: finally released Apache Helix 2.0.0 including
major feature change gateway for language agnostic support. Also removed risky
and deprecated UI components.
- Repo stabilization: Apache Helix main branch tests has been stabilized with
several fixes and rewrite of test cases.
- Glasswing scan: project requested glasswing scan and reviewing the security
mode.
- Light weighted Helix library (Tendril): plan to start this project to have
better support and K8s native based shard management. But need to consider
whether still have active committers to perform it.
-----------------------------------------
Attachment AG: Report from the Apache Hive Project [Naveen Gangam]
-----------------------------------------
Attachment AH: Report from the Apache Hop Project [Hans Van Akelyen]
## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Hop was founded 2021-12-15 (4 years ago)
There are currently 24 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bart Maertens on 2021-12-15.
- No new committers. Last addition was Sergio De Lorenzis on 2024-06-11.
## Project Activity:
We had a new release (2.18.0) in early June. This release, unfortunately
contained some major regressions. We are working on our first patch release to
mitigate these issues. We are also taking part in the Glasswing security scan
project.
## Community Health:
The project is growing in momentum, and we see new people popping up on GitHub
to discuss ideas or make their first contributions to the project. Our latest
release had 11 first-time contributors and 24 contributors in total.
-----------------------------------------
Attachment AI: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hudi was founded 2020-05-19 (6 years ago)
There are currently 43 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Yue Zhang on 2025-06-30.
- Peter Huang was added as committer on 2026-06-04
## Project Activity:
Hudi 1.2.0, was released in June 2026. Hudi 1.2.0 expands lakehouse
platform to natively support AI/ML workloads.
1.2.0 introduces three new logical data types (VECTOR, VARIANT, BLOB).
And dedicated Spark SQL functions, and native Lance file format
support. For Flink streaming usecase, it brings full Record Level
Index support. An opt-in FLIP-27 source with stronger push-down
capabilities is supported.
In May and June 2026 two minor releases - 0.14.2 and 0.15.1 were
released. They add bug fixes and improve stability to their
corresponding major releases.
The community is currently focussed on planning Hudi 1.3.0 roadmap.
Hudi-rs 0.5.0 is being actively worked on. It will add support for
newer Hudi table versions and the metadata table.
## Community Health:
We continue to see steady growth in community engagement on GitHub, with
active participation in code contributions and discussions. The dev and
users lists serve as primary channels for low-bandwidth communication,
while GitHub issues continue to be the main engagement model for
community support. The PMC continues to host the weekly developer sync meetings.
-----------------------------------------
Attachment AJ: Report from the Apache HugeGraph Project [Jermy Li]
-----------------------------------------
Attachment AK: Report from the Apache Iceberg Project [Ryan Blue]
## Description:
Apache Iceberg is a table format for huge analytic datasets that is designed
for high performance and ease of use.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Iceberg was founded 2020-05-19 (6 years ago)
There are currently 39 committers and 25 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 Prashant Singh on 2026-02-23.
- Andrei Tserakhau was added as committer on 2026-04-28
- Shawn Chang was added as committer on 2026-04-13
## Project Activity:
Releases
- Go 0.6.0 was released on 2026-05-28
- Java 1.11.0 was released on 2026-05-20
- Java 1.10.2 was released on 2026-05-18
- Rust 0.9.1 was released on 2026-05-06
- Rust 0.9.0 was released on 2026-03-18
Specs:
- Created drafts for expressions exchange and an embedded bitmap format
- REST protocol: Added list/load for functions, unregister table, S3 signing,
and clarified identifier handling. Read restrictions are close to completion
- v4 tables: added relative path support and columnar stats to the spec, added
column overwrite and append to scope
- Indexes: determined scope, definition is progressing
Java
- Added new CI validation for Jars in bundled artifacts
- Thoroughly reviewed LICENSE and NOTICE for 1.10 and 1.11 releases
- Kafka connect publishing is blocked until LICENSE/NOTICE is fixed
- Adding classes to support v4: TrackedFile, Tracking, etc.
- Spark: Added variant shredding
- Flink: Added variant support +shredding
- Added FileIO to the scan API for server-side planning to inject FileIO config
Python:
- Added support for Python 3.14 to CI and build
- Added support for paginated REST catalog listing
- Added View object API and REST catalog interactions
Rust:
- Added encryption manager with KEK/DEK envelope encryption
- Implemented AES-GCM stream encryption
- Updated to honor metadata.json compression settings
Go:
- Added golden round-trip tests
- Added variant type support (non-shredded)
- Added maintenance CLI command
- Added OCC conflict validation framework with isolation levels and validators
- Added DV support for v3
- Added row lineage support for v3
- Added write-default and initial-default support during Arrow projection
C++:
- Added Puffin file reader and writer with compression support
- Adding support for merge-based snapshot operations
- Added delete filter support for merge-on-read
- Added changelog scanning
## Community Health:
The community continues to be healthy.
Iceberg Summit 2026 was a success! Videos of talks are posted on the youtube
channel. Discussion for 2027 has already begun. We are also looking forward to
the Lakehouse Day EU that just announced several Iceberg sessions.
There is a lot of progress happening on new specs for storing/exchanging
expressions, indexes, v4 tables, and catalog interaction. The community also
quickly solved CI resource consumption.
The community also addressed 44 security reports this quarter. The majority were
AI-generated and specious. This put a notable strain on PMC bandwidth, despite
updating our procedure to streamline evaluating AI-generated reports. Even using
LLM-based tools to assist in evaluation, it took real human time to understand
both analyses (original and triaged) and respond. We don't have a great solution
for this problem yet.
-----------------------------------------
Attachment AL: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for June 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 28 podlings under incubation. In May, the Incubator made
five releases, and some release votes are currently underway. There were
one addition and no removals to IPMC membership.
Mailing list discussion focused primarily on release voting activity and two
graduation discussions: an active discussion on graduating Apache Fluss, and
the graduation discussion and vote for Apache Livy, which passed.
There was also substantial mentor and release-policy discussion during the
month, covering a potential issue with GitHub releases, use of Docker Hub
images, PyPI packages, and whether a dependencies file is required for
non-bundled dependencies in source releases, and Incubator graduation
requirements.
There was also continued discussion of MCP-based tooling for
Incubator insights and ASF policy questions and a new Trademark MCP has been
created. There was a discussion on using these tools to generate podling
reports.
Baremaps was retired by IPMC vote in March 2026. Some post-retirement
cleanup is still outstanding.
OpenServerless has been incubating for about two years and has not yet made
an ASF release. The podling has responded to the IPMC's concerns. It reports
continuous development across its subrepositories, has started adding
committers who contributed useful work, and has begun moving toward a
release. Separately, much of the podling's discussion has taken place on
Discord rather than on the public dev list, and the podling has been asked
to move project and technical discussion to the public list.
OzHera has not made an ASF release in over a year despite ongoing
development. The project has been asked to outline the current status of
release preparation, what is blocking the next release, and to address low
mentor engagement across recent reporting periods. They were slow to
respond, but are working on a new release.
Caldera engagement has improved since the concerns raised last cycle. The
project is now active on its dev list with healthy development activity.
Casbin discussion has begun moving onto the dev list.
PouchDB has yet to correct the redirection of the legacy pouchdb.com site.
Toree has been incubating since December 2015. The project is on a
new release candidate, but the going is slow.
The IPMC continues to monitor long-running podlings and will follow up on
any community concerns as needed.
When submitted, Otava lacked a mentor sign-off, they have been reminded to
sign off the report
## Community
### New IPMC members:
- Russell Spitzer
### People who left the IPMC:
- none
## New Podlings
- none
## Podlings that failed to report, expected next month
- Pony Mail
## Graduations
- Livy
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
May:
- Burr 0.42.0
- Fesod 2.0.2
- Fluss 0.9.1
- Otava 0.8.0
- Texera 1.1.0
## IP Clearance
- Apache Arrow Erlang library
- Apache Arrow pyarrow-stubs
## Legal / Trademarks
-N/A
## Infrastructure
- N/A
## Table of Contents
[Auron](#auron)
[BifroMQ](#bifromq)
[Caldera](#caldera)
[Casbin](#casbin)
[Iggy](#iggy)
[KIE](#kie)
[OpenServerless](#openserverless)
[Otava](#otava)
[OzHera](#ozhera)
[PouchDB](#pouchdb)
--------------------
## Auron
Auron accelerates Apache Spark SQL by providing an alternative vectorized
execution layer implemented in Rust, enabling native performance while
maintaining full Spark compatibility.
Auron has been incubating since 2025-08-05.
### Three most important unfinished issues to address before graduating:
1. Increase public communication on dev@ and ensure all project decisions
and planning are captured on the mailing list.
2. Grow the community and attract more contributors and users.
3. Enhance community diversity and sustainability.
### 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?
Two new committers added: Shilun Fan and Shreyesh Arangath.
### How has the project developed since the last report?
140 commits since the last report, including Flink integration with Kafka
source and Calc operator conversion, native scan support for Iceberg and
Hudi tables, the first native ORC write via InsertIntoHiveTable, new native
functions and window functions, critical stability fixes for panics and
NPEs, Spark 4.0/4.1 build compatibility, JNI-layer Spark decoupling, and a
multi-version correctness testing framework.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-03-04
### When were the last committers or PPMC members elected?
2026-03-31
### Have your mentors been helpful and responsive?
Yes, all the mentors are helpful and responsive on the community growth and
project development.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The podling name "Auron" has been reviewed by the VP, Brand. We are
not aware of any misuse by third parties.
### Signed-off-by:
- [X] (auron) Becket Qin
Comments: I agree that we can start to discuss the graduation of the
project.
- [X] (auron) Calvin Kirs
Comments: I think this podling is ready to graduate.
- [ ] (auron) Hao Ding
Comments:
- [X] (auron) Nicholas Jiang
Comments: Current status is worth discussion of gradutation.
### IPMC/Shepherd notes:
--------------------
## BifroMQ
BifroMQ is a Java-based, high-performance, distributed MQTT broker with
native multi-tenancy support, designed for large-scale
connections and message delivery.
BifroMQ has been incubating since 2025-04-22.
### Three most important unfinished issues to address before graduating:
1. Continue growing the contributor base outside the original team.
2. Encourage more user questions, feedback, and technical discussions to
happen on the public dev mailing list.
3. Continue regular Apache releases and share release management work
across more contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
Community activity continued on GitHub and the dev mailing list.
We are in the process of adding liaodongnian (GitHub: @liaodn) as a
committer and PPMC member. He has been using BifroMQ in real deployments
and has contributed issues, proposals, and patches.
The community also started public design discussions for Tenon, a BifroMQ
satellite project intended to provide data flow and data integration
capabilities around BifroMQ.
### How has the project developed since the last report?
Development continued steadily on the main repository. A new satellite
repository, incubator-bifromq-tenon, has been added.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-01-28
### When were the last committers or PPMC members elected?
None so far. The vote to add liaodongnian (GitHub: @liaodn) as a committer
and PPMC member has passed. The follow-up invitation and onboarding work is
still in progress.
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
BifroMQ trademark has been transferred to ASF. We are not aware of any
third-party misuse of the BifroMQ name or brand.
### Signed-off-by:
- [ ] (bifromq) Christofer Dutz
Comments:
- [ ] (bifromq) Xiangdong Huang
Comments:
- [X] (bifromq) Calvin Kirs
Comments: Great to see new PPMC member!
- [X] (bifromq) Penghui Li
Comments: Great to see the project keep moving forward
- [ ] (bifromq) Sheng Wu
Comments:
### IPMC/Shepherd notes:
--------------------
## Caldera
Caldera provides a modular platform for modeling, scripting, and executing
adversary behavior. It allows users to construct emulation plans, provides
agents for communicating with the command and control server,
and enables users to evaluate security detections in a
structured, scalable, and repeatable way. With the use of plug-
ins and community-contributed features, Caldera supports a range of use
cases including adversary emulation, purple teaming, detection
engineering, and continuous security validation. Using Caldera,
defenders can emulate known threat actor behavior and perform
other red team activity to evaluate their organization’s defensive
capabilities, test analytics, and find detection gaps. As a modular tool
based on the MITRE ATT&CK framework, Caldera is designed to be
extensible, intelligence-driven, and automation-friendly.
Caldera has been incubating since 2025-12-19.
### Three most important unfinished issues to address before graduating:
1. Community growth
2. Grow 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 new PPMC members and in process of vetting and
voting on these folks
Github Stars has now crossed the 7,000 star mark.
### How has the project developed since the last report?
The github repo has transferred and is available under /apache/caldera.
The website is stood up and found at caldera.apache.org.
5 Pull Requests have been merged since last report.
### 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:
### 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?
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:
- [X] (caldera) Francis Chuang
Comments: The team has made good progress with moving their git
repository and website to the ASF.
- [ ] (caldera) PJ Fanning
Comments: Initial setup is not complete.
- [ ] (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 (DSL), 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.
Incubation at the Apache Software Foundation aims to make Casbin a
community-driven, standardized authorization solution.
Casbin has been incubating since 2026-02-07.
### Three most important unfinished issues to address before graduating:
1. Define an ASF-aligned release process and cut Casbin's first official
Apache release.
2. Broaden the contributor base across organizations and keep moving
day-to-day discussion onto the Apache mailing lists.
3. Finalize the transfer of domains and trademarks to the ASF.
### 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?
- The Apache dev list (dev@casbin.apache.org) is now the project's primary
channel: it carried 17 messages in May (29 in March, 20 in April), covering
the incubation report cycle, dependency updates, and ASF infrastructure
changes. Traffic has been lighter than the first weeks of incubation,
reflecting a shift from setup work toward steady-state maintenance.
- GitHub stars on the main repository continued their slow, steady climb,
reaching roughly 20.15k.
- Automated dependency maintenance (Dependabot) stayed active across
several of the Node.js and core SDK repositories, keeping the ecosystem's
dependencies current.
### How has the project developed since the last report?
- Prepared and circulated the project's first Apache Incubator monthly
report for community review, establishing a regular reporting rhythm with
the mentors and IPMC.
- Worked with ASF INFRA to roll out default branch protection rulesets
across the project's repositories — a governance step that brings the repos
in line with foundation practice.
- Carried out routine maintenance across the multi-language repositories.
May was a deliberately quiet, housekeeping-focused month: 1 PR was merged
and 2 issues were closed across the project, with the remaining activity
being bot-driven dependency and infrastructure changes.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No Apache release yet.
### When were the last committers or PPMC members elected?
2026-02-07
### Have your mentors been helpful and responsive?
Yes, very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Name is approved:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-251
### Signed-off-by:
- [ ] (casbin) Hao Ding
Comments:
- [ ] (casbin) Huajie Wang
Comments:
- [X] (casbin) Hulk Lin
Comments:
- [X] (casbin) Jerry Shao
Comments:
- [X] (casbin) Zili Chen
Comments:
### IPMC/Shepherd notes:
None
--------------------
## Iggy
Iggy is a high-performance, ultra-low latency and large-scale persistent
message streaming platform written in Rust.
Iggy has been incubating since 2025-02-04.
### Three most important unfinished issues to address before graduating:
1. Continue expanding the community
2. Increase the use of GitHub Discussions/Issues integrated with mailing
lists
### Are there any issues that the IPMC or ASF Board need to be aware of?
Lately, a lot of GitHub CI/CD issues. Hope ASF is actively looking into it.
### How has the community developed since the last report?
- Discord members count ~700, new contributors writing proposals
(discussions), submitting PRs for fixing issues, docs, enhancements.
- Github stars reached 4.3K+
- Crates downloads reached ~220K+
- 2 new committers have been added
- Presented at [Rust India 2026
conference](https://hasgeek.com/rustbangalore/rust-india-conference-2026/sub
/building-apache-iggy-how-rust-powers-ultra-low-tai-Nh82Mb2cvJXmgH39Yaez8x)
### How has the project developed since the last report?
- Released
[0.8.0](https://github.com/apache/iggy/releases/tag/server-0.8.0), a major
release focused on architecture, clustering readiness, security, SDK
maturity, connectors, and infrastructure.
- More than 300 commits since the last report (Mar 2026)
- Completed a wire protocol unification, removing redundant serialization
paths and simplifying the protocol foundation.
- Added new zero-copy message primitives, improving the internal data path
and preparing the project for higher-performance messaging workloads.
- Introduced **`iggy-server-ng`**, a new server binary that serves as the
foundation for future cluster-ready Iggy deployments.
- Advanced VSR-based clustering, including shard routing, plane
abstractions, WAL-backed client tracking, namespaced commit pipelines,
deterministic simulator improvements, and persistent WAL journal support.
- Improved security and credential handling with user-header encryption,
random JWT secret generation, `SecretString` usage, consensus header
validation, and regression tests to prevent plaintext secret persistence.
- Fixed multiple reliability and correctness issues, including consumer
offset handling, segment deletion behavior, hostname handling, CLI
behavior, and connector runtime behavior.
- Expanded the SDK ecosystem with major improvements across Rust, C++,
Java, C#, Go, Python, and Node.js clients, including better transport, TLS,
async APIs, testing, and usability.
- Added new connectors for InfluxDB, MongoDB, and generic HTTP sinks, along
with connector hot-reload support.
- Improved developer and operator experience through benchmark dashboard
updates, Web UI enhancements, Helm chart improvements, and CLI usability
fixes.
- Strengthened CI/CD and release quality, including parallel Rust testing,
dependency-DAG-scoped test selection, broader Codecov coverage, hardened
publish pipelines, Helm chart validation, binary artifact detection, typo
checks, version bump tooling, and ASF GitHub Actions allowlist compliance.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [X] Other: Expanding Ecosystem
### Date of last release:
2026-04-22
### When were the last committers or PPMC members elected?
- 2026-05-11 [Krishna Vishal]
- 2026-05-22 [Atharva Lade]
### Have your mentors been helpful and responsive?
Yes, very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here. VP, Brand
approved the project name.
### Signed-off-by:
- [ ] (iggy) Hao Ding
Comments:
- [ ] (iggy) Yonik Seeley
Comments:
- [X] (iggy) Zili Chen
Comments:
- [X] (iggy) Hulk Lin
Comments:
### IPMC/Shepherd notes:
JM - Sent an email to the project about CI/CD issues.
--------------------
## KIE
KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.
KIE has been incubating since 2023-01-13.
### Three most important unfinished issues to address before graduating:
1. Finish the remaining Category X dependencies removal (progress made in
10.2)
2. Community building
3. More frequent releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
Not at the moment.
### How has the community developed since the last report?
The community has agreed on a restructuring plan to simplify its codebase
and contributions models in an attempt to attract new contributors and
expedite releasing new versions more frequently to its existing user base.
### How has the project developed since the last report?
10.2 was released on late April'26. That's the 3rd release since
inception in Apache's incubation in 2023.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation (we believe we can seriously start looking into
graduation efforts before EOY 2026)
- [ ] Other:
### Date of last release:
2026-04-29 (10.2.0)
### When were the last committers or PPMC members elected?
2025-11-26
### Have your mentors been helpful and responsive?
Mentors have been good so far. No issues.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (kie) Brian Proffitt
Comments:
- [X] (kie) Claus Ibsen
Comments:
- [ ] (kie) Andrea Cosentino
Comments:
### IPMC/Shepherd notes:
--------------------
## OpenServerless
OpenServerless is an open source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it
provides an unified developer experience with a plethora of
services (SQL or noSQL databases, key-value stores, object
storage, LLMs services, function schedulers) managed by the platform's core:
the operator, along with tooling (the CLI) to simplify (and
interact with) deployments, integrated ide and starter
application and optimized runtimes integrated with the staters.
OpenServerless has been incubating since 2024-06-17.
### Three most important unfinished issues to address before graduating:
1. Making releases
2. Growth of the community
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
### How has the project developed since the last report?
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
- Michele Manzani as a new committer (2026-05-14)
### Have your mentors been helpful and responsive?
no answer
### Is the PPMC managing the podling's brand / trademarks?
no answer
### Signed-off-by:
- [ ] (openserverless) Bertrand Delacrétaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [X] (openserverless) François Papon
Comments: Making progress on the release process.
- [X] (openserverless) Jean-Baptiste Onofré
Comments: I think we (the mentors) should be more involved in the
podling to provide good practice and guideline (mailing list, community
building, etc).
- [X] (openserverless) PJ Fanning
Comments: Not enough use of the mailing lists still.
### IPMC/Shepherd notes:
--------------------
## Otava
Otava, a command-line tool, written in Python, that detects statistically
significant changes in time-series data stored either in databases or CSV
files.
A typical use-case of Otava is as follows:
A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
The resulting metrics of the test runs are stored in a time series database
(Graphite) or appended to CSV files.
Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
Otava notifies about significant changes in recorded metrics by outputting
text reports or sending Slack notifications.
Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the environment.
Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter
### Three most important unfinished issues to address before graduating:
1. Establish frequent releases as a routine, repeatable process
2. Improve documentation to lower the entry barrier for users and
contributors.
3. Define and document the desired long-term architecture. The goals of the
long-term architecture are: a. Modularity: Keep the core library
lightweight while making external dependencies (data sources and
notification channels) pluggable. b. API stabilization: Clearly define and
stabilize public interfaces prior to a 1.0.0 release.
### 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?
- Denis Shchepakin was elected as a PPMC member (announced on dev@ in March
2026).
- 6 new external contributors opened PRs in the project.
- We started a new helper project:
https://github.com/apache/otava-playground. This project contains test data
generators and visualization that can be used to compare Otava EDivisive
against several other formulas and heuristics often used for change
detection. We are also using it to compare different variants of Otava
itself.
### How has the project developed since the last report?
- The project made the most significant release since the incubation
started - 0.8.0-incubating. In this release, Apache Otava supports Python
versions 3.10-3.14. Starting with this release, Otava aims to support all
actively supported Python versions. That was possible thanks to a core
algorithm rewrite.
- Release process documentation has been improved based on feedback from
0.8.0-incubating.
- There are active discussions between PPMCs and external contributors
about further core algorithm improvements.
- There is an ongoing refactoring work for internal data structures. This
is a prerequisite to officially supporting public Python API.
### How would you assess the podling's maturity?
Same slow positive trend in community building, but not yet nearing
graduation.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-05-08
### When were the last committers or PPMC members elected?
Denis Shchepakin was elected as a PPMC member in March 2026.
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
no answer
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [X] (otava) Lari Hotari
Comments:
- [X] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
--------------------
## OzHera
OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such
as metric monitoring, trace tracking, logging, and alerting
OzHera has been incubating since 2024-07-11.
### Three most important unfinished issues to address before graduating:
1. Complete the next Apache release and improve the release process.
2. Grow the contributor base and elect more committers/PPMC members.
3. Move more design, release, and community discussions to the public
dev mailing list.
### Are there any issues that the IPMC or ASF Board need to be aware of?
The project is preparing the next Apache release in early June. The
release has not been completed yet. The community is reviewing the
remaining release blockers and will work with mentors to complete
the release process.
### How has the community developed since the last report?
The community continued development and code review on GitHub.
Several contributors participated in recent pull requests,
including work on log stream processing, Agent interfaces,
permission checks, configuration delivery, and stability
improvements.
One new committer was elected in April 2026.
The project will continue to encourage more technical discussions,
release planning, and community decisions to happen on the public
dev mailing list.
### How has the project developed since the last report?
The project continued to improve observability features and stability.
Recent development work includes:
1. Improved log stream processing, including OpenCLAW log path parsing,
null pointer checks, trace application log retrieval, and handling
of truncated log content.
2. Added and improved Agent-related interfaces, including new interfaces
that the Agent can call and better request validation for valid JSON
payloads.
3. Improved permission and configuration support, including space/store
permission checks, configuration parameter support, and a sending
frequency limit function.
4. Optimized Agent channel lookup by prioritizing IP-based lookup.
5. Improved log processing and configuration delivery logic.
6. Fixed smaller issues such as PromQL naming corrections, Redis
import path fixes, and other stability improvements.
The last release was v2.2.5-incubating on 2025-03-26. The community
is preparing the next Apache release in early June. The release has
not been completed yet.dev mailing list
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-03-26
### When were the last committers or PPMC members elected?
One new committer was elected in April 2026.
### Have your mentors been helpful and responsive?
Yes, mentors have been helpful and responsive. The project will
ask mentors to review the release plan and help with the next
Apache release.
### Is the PPMC managing the podling's brand / trademarks?
The PPMC is working on this and will continue to review the website,
documentation, repository, and release materials for Apache branding
and trademark requirements.
### Signed-off-by:
- [X] (ozhera) Yu Xiao
Comments:
- [X] (ozhera) Yu Li
Comments: It's good to see a new committer join the project. However,
the absence of a release for over two months is concerning. Look forward to
a detailed and actionable plan for the next release.
- [ ] (ozhera) Kevin Ratnasekera
Comments:
- [ ] (ozhera) Duo Zhang
Comments:
### IPMC/Shepherd notes:
--------------------
## PouchDB
PouchDB is an open-source JavaScript database inspired by Apache CouchDB
that is designed to run well within the browser.
PouchDB has been incubating since 2025-04-15.
### Three most important unfinished issues to address before graduating:
1. Making a release
2. Adding contributors
3. Finish infrastructure migration
### Are there any issues that the IPMC or ASF Board need to be aware of?
There is no “issue” per-se, but we want to highlight that we have
made slow progress on knocking down incubation progress in favour of
advancing the project and its infrastructure a bit more before
going after next steps.
See project development section for details.
### How has the community developed since the last report?
We continue receiving non-committer contributions, albeit at
a slightly slower pace than last quarter, as that had a boost
due to STA funding. The current pace is more in line with
pre-ASF project momentum. Candidates for committership are
emerging and we’ll start those processes when appropriate.
### How has the project developed since the last report?
- Added major features in preparation for a new feature release.
- Revamped the website onto a modern website toolkit and migrating
towards ASF-policy-friendly hosting with additional major docs
feature of versioning nearly ready for shipping.
- h/t to ASF infra for helping move this forward
- Started roadmap discussions for next few releases as we have
to deprecate some legacy parts of PouchDB while making sure all
users have a smooth migration path.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
n/a
### When were the last committers or PPMC members elected?
January 28th 2026
### Have your mentors been helpful and responsive?
Mentors continue to be active and helpful
### Is the PPMC managing the podling's brand / trademarks?
PPMC have not yet requested a Podling Suitable Names Search
### Signed-off-by:
- [X] (pouchdb) JB Onofre
Comments: Still ramping up but progress.
- [X] (pouchdb) PJ Fanning
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AM: Report from the Apache IoTDB Project [Xiangdong Huang]
## Description:
The mission of Apache IoTDB is the creation and maintenance of software
related to an IoT native database with high performance for data management
and analysis.
## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: some trademark issues (legacy issues and new problems)
are proposed. PMC will try to solve it in the coming quarter.
## Membership Data:
Apache IoTDB was founded 2020-09-16 (5 years ago) There are currently 83
committers and 32 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 Hongyin Zhang on 2025-11-07.
- Xinhao Gu was added as committer on 2026-06-04
## Project Activity:
- AINode introduced integration with Chronos-2, bringing covariate-aware
forecasting capabilities to IoTDB’s AI analytics stack. By enabling
forecasting models to leverage both historical observations and external
variables, IoTDB continues its evolution toward a comprehensive platform for
intelligent time-series management and AI-driven decision support.
- The community continued refining the Table Model SQL experience by
introducing a series of compatibility and usability enhancements. Inspired
by widely adopted SQL dialects, these improvements make queries more concise
and intuitive, lowering migration costs for users coming from traditional
relational and analytical databases while improving overall developer
productivity.
- In March, the community hosted a meetup in Hangzhou, China, centered on the
application of IoTDB and AI technologies in industrial scenarios. The event
provided a platform for users and contributors to exchange experiences,
showcase practical deployments, and discuss the future of AI-powered
time-series data management.
## Community Health:
Overall community health is good.
- dev@iotdb.apache.org had a 6% increase in traffic in the past quarter (243
emails compared to 228)
- The proposal “ThingsBoard IoTDB 2.x Table Model Integration” was accepted
into Google Summer of Code (GSoC). The program attracted several new
contributors, including some applicants who were not selected but continued
participating in project development and community activities throughout the
reporting period.
-----------------------------------------
Attachment AN: Report from the Apache Jackrabbit Project [Marcel Reutegger]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class websites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications, and it
is not a reference implementation.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Jackrabbit was founded 2006-03-15 (20 years ago).
There are currently 60 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is 1:1, because all committers automatically
become PMC members.
Community changes, past quarter:
- No new PMC members. Last addition was Alejandro Moratinos on 2025-08-27.
- No new committers. Last addition was Alejandro Moratinos on 2025-08-27.
## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.
Jackrabbit Oak 2.0.0 was released as the first major Oak release that
requires Java 17. This follows the earlier work to raise the minimum
Java version across build and CI, and gives the project a current Java
baseline for future development while maintenance branches continue to
serve older runtime requirements.
The ongoing effort to reduce dependence on Google's Guava library made
substantial progress. Oak introduced its own cache API and Caffeine based
implementations, added compatibility tests, and migrated cache usage in
document store, search, segment store, blob, S3 and Azure components.
Follow-up work refined cache statistics, eviction behaviour and exception
handling to preserve compatibility with existing Guava based behaviour.
Indexing and query processing continued to receive significant attention.
Changes improved index cost estimation, LIMIT aware index selection,
Lucene and Elastic index version handling, Elastic async response
processing, subtree deletion handling and diagnostics. Additional tests
were added for facets, KNN queries, deleted Lucene documents and related
query edge cases.
## Community Health:
The project is generally healthy with a continuous stream of traffic
mostly on JIRA issues and GitHub pull requests reflecting activity of
the respective component.
Commit activity is moderate, mirroring the activity on the
JIRA issues and the desire of the individual contributors to bring
features and improvements in for the next Jackrabbit Oak release.
## Releases:
- jackrabbit-2.23.4-beta was released on 2026-04-10
- jackrabbit-oak-2.0.0 was released on 2026-04-21
- jackrabbit-oak-1.22.24 was released on 2026-04-28
- jackrabbit-oak-2.2.0 was released on 2026-06-02
## JIRA activity:
- 131 JIRA tickets created in the last 3 months
- 101 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AO: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
The mission of the Apache Karaf project is the creation and maintenance of
open-source software related to a generic platform providing higher level
features and services specifically designed for creating OSGi-based servers for
distribution at no charge to the public.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Karaf was founded 2010-06-16 (16 years ago)
There are currently 34 committers and 16 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 Francois Papon on 2018-11-29.
- No new committers. Last addition was Holger Friedrich on 2026-03-02.
## Project Activity:
Apache Karaf 4.4.11 has been released on 2026-04-30.
This maintenance release brings:
- Shell console improvements on Windows platform
- Improvements on the karaf-maven-plugin feature and assembly goal
- A lot of dependency updates
Note: the release required two release candidates; rc0 was cancelled after an
issue was found during the vote, and rc1 passed successfully.
The [DISCUSS] Heading to Karaf 4.5.0 thread (started May 2026) is very active,
with 20 participants contributing to the roadmap discussion. Key topics include:
- Pax * and dependency modernization
- Updated feature resolver
- Karaf distributions and naming (see also the dedicated [DISCUSS] thread)
- Java 25 support
- Removal of legacy specs bundles
Apache Karaf Decanter 3.0.0 preparation is ongoing, with major updates including
JDK 21+ support, refactoring of the event and alerting layers.
## Community Health:
- dev@karaf.apache.org had a significant increase in traffic this quarter:
March 2026: 6 emails / 4 participants April 2026: 22 emails / 12
participants (dominated by the 4.4.11 release vote) May 2026: 79 emails / 20
participants (dominated by the 4.5.0 roadmap discussion) This represents a
very healthy and engaged developer community, with the highest monthly
volume since August 2025.
- The 4.5.0 roadmap discussion is the most active thread seen in several
quarters, reflecting strong community investment in the project's future
direction.
- Infrastructure: the project has fully transitioned to GitHub Issues and
GitHub Actions, with the legacy Jira instance now in read-only mode.
-----------------------------------------
Attachment AP: Report from the Apache Kvrocks Project [Mingyang Liu]
## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, supporting the rich data
structures.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kvrocks was founded 2023-06-21 (3 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 Aleks Lozoviuk on 2025-05-06.
- No new committers. Last addition was Xiaojun Yuan on 2026-02-24.
## Project Activity:
In recent months, the Kvrocks community has been working on support for the
hash field expiration feature. Basic support is now complete. We will release
it once the feature is sufficiently stable and complete.
In addition, the community is preparing for the release of version 2.16.0.
## Community Health:
This quarter, the number of issues remained the same as last quarter; the
number of PRs increased by 50% compared to last quarter.
This indicates that contributions are more active than ever before. Part of
this is due to the impact of AI, making it easier for people to contribute.
Unfortunately, however, most of these contributions cannot be merged because
the contributors themselves lack the relevant knowledge and rely solely on AI,
making communication between them and the community difficult.
-----------------------------------------
Attachment AQ: Report from the Apache Kyuubi Project [Cheng Pan]
Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses
Project Status:
Current project status: Ongoing.
Issues for the board: None.
Membership Data:
Apache Kyuubi was founded on 2022-12-21 (3 years ago). There are currently 30
committers and 16 PMC members in this project. The Committer-to-PMC ratio is
roughly 2:1.
Community changes, past quarter:
No new PMC members. Last addition was Binjie Yang on 2024-07-05.
Zhigang Wang was added as committer on 2026-05-29
Project Activity:
Released Apache Kyuubi v1.11.1 at 2026-03-26;
We recently introduced the Data Agent engine, which enables Kyuubi to
integrate more effectively with the AI ecosystem.
Kyuubi PMC is working closely with the Apache security team to actively
analyze and resolve security issues reported from the community.
Community Health:
dev@kyuubi.apache.org had a 25% decrease in traffic in the past quarter
(22 emails compared to 29); notifications@kyuubi.apache.org had a 107%
increase in traffic in the past quarter (1036 emails compared to 500);
The overall traffic is low, but still at a good state because the project
itself is mature enough. Recent community events have seen a significant
increase in AI involvement, and we are actively adapting to and embracing
the changes brought about by AI.
-----------------------------------------
Attachment AR: Report from the Apache Linkis Project [Shuai Di]
## Description:
The mission of Apache Linkis is to build a distributed
computation middleware to facilitate connection,
governance, extensibility and orchestration between the
upper applications and the underlying data engines.
## Project Status:
Current project status: Ongoing.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Linkis was founded on 2022-12-21 (More than three years ago).
There are currently 39 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jie Cheng on 2024-01-28.
- Kazuto Iris was added as committer on 2026-06-02
## Project Activity:
The Apache Linkis V1.9.0 is currently in active development.
- Restrict Hive SQL from specifying LOCATION during table creation
- Processing of user sensitive information
- Show newly supported engine versions within task history records
- Support for configuring a second queue in Spark
- Fix isolation entrance and concurrency calculation exceptions in user jobs
The Apache Linkis V1.8.0 was released on October 17, 2025.
- EC reuse enhancement, supports resource and Python version judgment.
- Supports coexistence of Spark 2 and Spark 3.
- Optimize resources to highlight error issues.
- Batch queue resource acquisition
- StarRocks task retry mechanism
- Spark timeout task diagnosis
- Log level filtering
- Hadoop user login control
- Data source proxy user support
- Result set field truncation
- CI/CD enhancement
- Optimization of engine creation and reuse service performance
- Monitor optimization and monitoring module
- BMLClient connection pool parameter optimization
- Manager thread pool optimization
## Community Health:
Overall community health is good.
- 37 PRs closed on GitHub, past quarter.
- 39 issues closed on GitHub, past quarter.
-----------------------------------------
Attachment AS: Report from the Apache Livy Project [Jean-Baptiste Onofré]
# Description
Apache Livy is a service that enables easy interaction with an Apache Spark
cluster over a REST interface. It supports easy submission of Spark jobs or
snippets of Spark code, synchronous or asynchronous result retrieval, as well
as Spark Context management, all via a simple REST interface or an RPC client
library. Apache Livy also simplifies the interaction between Spark and
application servers, thus enabling the use of Spark for interactive web/mobile
applications.
# 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 AT: Report from the Apache Lucene Project [Ben Trent]
## Description:
The mission of Lucene is the creation and maintenance of software related to
Search engine library
## Project Status:
Current project status: Active, Ongoing
Issues for the board: None
## Membership Data:
Apache Lucene was founded 2005-01-18 (21 years ago)
There are currently 112 committers and 70 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Tim Brooks was voted in as a Committer on 2026-06-02.
## Project Activity:
A new release, Apache Lucene 10.5, has been suggested.
It will occur in the next quarter.
A significant new work has begun to improve columnar data performance.
This not only contains numerous search time improvements on Lucene's
but includes a large refactoring to Lucene's document indexing path
that is optimized for columnar data[0].
AI assisted development has also provided useful work in improving vector
search. Notably, this includes testing and drafting a format with Google's
TurboQuant[1] algorithm. This pivoted into a discussion about how
to bring pieces of the algorithm into Lucene[2].
There has been a notable increase in smaller performance based improvements and
changes. This seems largely driven by AI assisted development.
## Community Health:
A reduction in overall email traffic on dev@lucene.apache.org (59% decrease).
The reason for this is unknown, but overall community communication has
increased on Github issues and PRs.
421 across the branches (275 to main).
315 total Pull Requests (266 of those closed or merged)
63 new issues (26 of those closed).
These statistics are in line with previous quarters and very similar to second
quarter of last year. Showing consistent health
[0]https://github.com/apache/lucene/pull/15990
[1]https://research.google/blog/turboquant-redefining-ai-efficiency-with-extreme-compression/
[2]https://github.com/apache/lucene/pull/16092
-----------------------------------------
Attachment AU: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AV: Report from the Apache Mynewt Project [Szymon Janc]
-----------------------------------------
Attachment AW: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environments, tooling platforms, and application
frameworks.
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No issues for the board at this time.
## Membership Data:
Apache NetBeans was founded 2019-04-17 (7 years ago)
There are currently 83 committers and 66 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 Brad Walker on 2026-01-26.
- No new committers. Last addition was Haidu Bogdan on 2026-01-29.
## Project Activity:
- Apache NetBeans 30 was released on 2026-05-18, with 20 contributors, 2 for
the first time.
- Apache NetBeans 29 was released on 2026-02-23, with 19 contributors, 2 for
the first time.
## Community Health:
- The key ongoing discussion at the moment is the status and future of
installers, with various options, including dropping them, on the table.
- The project is led by a core group of strong leaders, while we've also grown
in PMC members and committers over the past 6 months and that focus
continues.
- dev@netbeans.apache.org had a 5% increase in traffic in the past quarter
(109 emails compared to 103), indicating a stable developer community.
-----------------------------------------
Attachment AX: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Project Status:
Current project status: Ongoing
Issues for the board: none.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (19 years ago) There are currently 64
committers and 37 PMC members in this project. The Committer-to-PMC ratio is
roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Sebastian Tschikin on 2024-09-18.
- Anahita Goljahani was added as committer on 2026-04-28
- Yashwant Dhakad was added as committer on 2026-04-29
## Project Activity
* Apache OFBiz 24.09.06 was released on May 19, 2026.
* Apache OFBiz 24.09.07 was released on June 10, 2026.
* These releases addressed all outstanding vulnerability reports and were
accompanied by the publication of 19 CVEs. During 2026, the project has
experienced a significant increase in vulnerability reports, which has
required substantial effort from the security team.
* Several new features were contributed by community members and successfully
merged during the reporting period, reflecting continued development
activity and contributor engagement.
* The 24.09 branch continues to serve as the current stable release line. The
community has begun discussing an eventual end-of-life timeline for this
branch and the preparation of its successor.
* The PMC has established a new private GitHub repository to support project
governance and operational activities, including tracking potential
candidates for committer and PMC membership, as well as coordinating the
handling of security vulnerabilities.
## Community Health
During the reporting period, the community remained highly active across
several areas. Mailing list discussions were frequent and productive, and
contributors reviewed and merged a substantial number of pull requests.
Significant effort was also devoted to the design and implementation of
security improvements, enhancements to the project's CI/CD workflows, and
refinements to community practices and conventions aimed at streamlining the
contribution process.
Two new committers were added during this reporting period. The project also
continues to identify promising contributors who may become future committers
and PMC members.
-----------------------------------------
Attachment AY: Report from the Apache OpenDAL Project [Hao Ding]
## Description:
OpenDAL is an Open Data Access Layer that enables seamless interaction with
diverse storage services. Its development is guided by the vision "One Layer,
All Storage" and the following principles:
- Open Community
- Solid Foundation
- Fast Access
- Object Storage First
- Extensible Architecture
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache OpenDAL was founded on 2024-01-17. There are currently 39 committers
and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 1.7.
Community changes, past quarter:
- Hao Jiang (dentiny) was added as committer on 2026-03-30
- Fatorin was added as committer on 2026-04-03
- Krisztian Szucs was added as committer on 2026-05-28
- Hao Jiang (dentiny) was added as PMC member on 2026-06-02
## Project Activity:
OpenDAL has the following releases since the last report:
- Apache OpenDAL Reqsign v0.20.0 was released on 2026-03-23
- Apache OpenDAL v0.56.0 was released on 2026-05-01
- Apache OpenDAL v0.57.0 was released on 2026-06-01
- Apache OpenDAL Reqsign v0.20.1 was released on 2026-06-01
Notable project activity this quarter:
- The Rust core has been split into a facade crate plus smaller core, service,
and layer crates. This makes service and layer development more independent
while preserving the user-facing facade.
- The community continued to improve OpenDAL's cross-language bindings,
including Ruby publication work, .NET binding work, Python and Node.js API
coverage, Java platform support, and Go/C layer support.
- The core APIs gained richer operation metadata, including copy/read
metadata, copier support, and service-operation labels for HTTP metrics.
- Storage service coverage and behavior continued to expand, including
Volcengine TOS, GooseFS, OPFS, Hugging Face improvements, user-defined
metadata support, and stronger S3-compatible service behavior.
- Apache OpenDAL Reqsign delivered two releases, adding Volcengine TOS
support, Google external account credential providers, expanded Aliyun OSS
support, and dependency hygiene improvements.
Since 2026-03-18, the main OpenDAL repository merged 264 pull requests from 43
contributors and closed 91 issues. The opendal-reqsign repository merged 42
pull requests from 6 contributors.
## Community Health:
### Are there any risks to the sustainability of the project?
OpenDAL remains in good health. The project continues to receive steady code,
documentation, release, CI, and binding contributions from both existing
committers and new contributors. The main repository currently has more than
5,100 GitHub stars and more than 760 forks, and development velocity remained
steady throughout the quarter.
The PMC is also continuing to grow the committer pipeline. The vote to add
Trim21 as a committer has passed and an invitation has been sent; the roster
change is still pending acceptance and ASF account completion.
### Is the PMC capable of responding to security issues and performing
releases if needed?
Yes. The PMC continues to make regular Apache releases for both OpenDAL and
OpenDAL Reqsign, and release processes are documented and repeatable. The PMC
is also capable of responding to security reports and coordinating with the
ASF Security Team when needed.
### Does the PMC need anything from the Foundation to improve on contributing
to our mission of delivering software for the public good?
The PMC would benefit from more GitHub Actions runner capacity for the large
cross-platform CI matrix, especially for release validation and behavior tests
across storage services and language bindings.
PMC members would also benefit from access to token quota for state-of-the-art
AI models. We expect to use this for project maintenance work such as code
review assistance, issue triage, release preparation, documentation updates,
and debugging complex cross-language or cross-service failures.
-----------------------------------------
Attachment AZ: Report from the Apache OpenNLP Project [Jeffrey T. Zemerick]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache OpenNLP was founded 2012-02-14 (14 years ago)
There are currently 27 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Atita Arora on 2025-07-19.
- Kristian Rickert was added as committer on 2026-05-05
## Project Activity:
The project did two releases this quarter - 2.5.8 and 2.5.9, and 3.0.0-M2 and
3.0.0-M3 - and we are continuing toward a 3.0.0 release. Several CVEs were
addressed in both of these releases. The project is continuing to progress to
a 3.0.0 release.
## Community Health:
The project added a new committer in this quarter. Commits were mainly from
core developers but did have two others contributor. Community involvement
remains low but the project is healthy with a core set of contributors.
-----------------------------------------
Attachment BA: Report from the Apache OpenOffice Project [Keith McKenna]
-----------------------------------------
Attachment BB: Report from the Apache OpenWebBeans Project [Mark Struberg]
-----------------------------------------
Attachment BC: Report from the Apache Paimon Project [Jingsong Lee]
## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Paimon was founded 2024-03-20 (2 years ago)
There are currently 27 committers and 14 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 Junhao Ye on 2025-02-25.
- Chenghui Chen was added as committer on 2026-05-29
- Wenhai Zhao was added as committer on 2026-04-28
## Project Activity:
Software development activity:
- Releasing version 1.4.1. Bug fix version.
- Releasing paimon-rust 0.1.0 and 0.2.0. Rust Implementation.
- Releasing paimon-mosaic 0.1.0. Columnar hybrid format for wide tables.
- We discussed in dev: next step is 2.0, aimed at a multimodal data lake.
## Community Health:
- dev mail list had 167% increase (187 emails compared to 70).
- issue mail list had 96% increase (5050 emails compared to 2541).
- user email list had 64 decrease (11 emails compared to 30), not used much.
- Contribution and activity of the community have significantly increased.
-----------------------------------------
Attachment BD: Report from the Apache Pekko Project [PJ Fanning]
## Description:
The mission of Apache Pekko is the creation and maintenance of software related
to a toolkit and an ecosystem for building highly concurrent, distributed,
reactive and resilient applications for Java and Scala
## Project Status:
Current project status:
Project is active and releases are happening regularly.
Issues for the board:
None
## Membership Data:
Apache Pekko was founded 2024-03-20 (2 years ago)
There are currently 29 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 Domantas Petrauskas on 2025-11-20.
- Philippus Baalman was added as committer on 2026-03-21
## Project Activity:
Bug fix releases for the 1.x releases are typically turned around pretty
quickly. Version 2.0.0 is making progress with most modules having milestone
releases and snapshots available for testing.
## Community Health:
Small number of active committers and some more who are occasionally
active. Pekko libraries are used fairly widely. There are a few occasional
contributors from outside the committer team but nobody is very active.
-----------------------------------------
Attachment BE: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BF: Report from the Apache PLC4X Project [César García]
-----------------------------------------
Attachment BG: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
## Description:
The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The primary goal is to provide
an API to which software developers may code and be assured of predictable if
not identical behaviour regardless of the platform on which their software is
built, relieving them of the need to code special-case conditions to work
around or take advantage of platform-specific deficiencies or features.
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: None
## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (26 years ago)
There are currently 68 committers and 43 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 Daniel Sahlberg on 2025-08-07.
- No new committers. Last addition was Daniel Sahlberg on 2025-08-07.
## Project Activity:
The metrics show increased activity on the public dev list where
various topics around support for some dead OS or build systems took
place and resulted in some commits.
## Community Health:
-----------------------------------------
Attachment BH: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
## Project Status:
- There are no issues requiring board attention at this time.
## Project Activity:
- Work on the 5.0.0-M1 release is well underway. This will be the first
preview of Pulsar 5, introducing the new Scalable Topics API — the
culmination of the multi-PIP "Topics v5" initiative described below.
- Pulsar 4.2.0, the latest feature release, was released on March 31st
2026. Maintenance releases across the 4.2.x, 4.0.x, and 3.0.x lines
continue on a regular cadence:
- 4.2.2 was released on June 8th 2026
- 4.0.11 was released on June 8th 2026
- 4.2.1 was released on April 27th 2026
- 4.0.10 was released on April 27th 2026
- 3.0.17 was released on April 27th 2026
- 4.2.0 was released on March 31st 2026
- 4.1.3 was released on February 19th 2026
- 4.0.9 was released on February 19th 2026
- 3.0.16 was released on February 16th 2026
- Pulsar C++ releases:
- 4.2.0 on June 14th 2026
- 4.1.0 on March 30th 2026
- Pulsar Go releases:
- 0.19.0 on April 15th 2026
- Pulsar Python releases:
- 3.12.0 on May 20th 2026
- 3.11.0 on April 16th 2026
- Pulsar NodeJS releases:
- 1.17.0 on April 9th 2026
- We continue to have a very high number of "Pulsar Improvement
Proposal" being submitted, discussed and voted by the community.
This quarter was exceptionally active, with nearly 30 PIPs seeing
activity (PIP-457 through PIP-485) — roughly double the previous
quarter. A major theme is the multi-PIP "Scalable Topics (Topics v5)"
initiative, which introduces topics that scale elastically while
preserving key ordering (PIP-460, 466, 468, 473, 475, 483) and which
will ship as a preview in Pulsar 5.0.0-M1, alongside a broad
platform-modernization effort (PIP-457, 462, 463, 465, 467, 472).
A selection:
PIP-457: Remove support for V1 topic names and V1 Admin API
PIP-460: Scalable Topics (Topics v5)
PIP-462: Remove Etcd metadata store backend
PIP-463: Migrate Build System from Maven to Gradle
PIP-464: Deprecate legacy Jackson JsonSchema format for SchemaType.JSON
PIP-465: Split IO Connectors into Separate Repository
PIP-466: New Java Client API (V5) with Scalable Topic Support
PIP-467: Adopt slog for structured logging across Pulsar
PIP-468: Scalable Topic Controller
PIP-469: Legacy-aware topic policies backend routing and
metadata-store topic policies
PIP-470: Close inactive topics without deleting their data
PIP-471: Authorization operation metrics
PIP-472: Migrate from javax.* to jakarta.* APIs
PIP-473: Metadata-Driven Transactions for Scalable Topics
PIP-474: Key_Shared Hot Key Overflow Mechanism
PIP-475: Regular-to-Scalable Topic Migration
PIP-476: Extensible Key_Shared Dispatcher Mechanism
PIP-477: Dynamic Bookie Cluster Switching for Brokers
PIP-478: Asynchronous v5 client auth plugin and TLS material
provider plugin interfaces
PIP-480: Add readEntries method to ManagedLedger
PIP-481: Retain Ended Transaction Status for Precise Error Reporting
PIP-482: Peek messages from topic subscription with messagePosition
PIP-483: Scalable Topic Auto Split/Merge
PIP-484: Expose incremental window events via IncrementalWindowFunction
PIP-485: Configurable mTLS principal mapping
- Pulsar has reached 724 contributors on the main GitHub repo
(It was 712 in February 2026)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. The volume of Pulsar Improvement Proposals and the
associated dev@ list discussion grew markedly this quarter, driven in
large part by the Scalable Topics initiative leading up to the Pulsar 5
preview.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (7 years ago)
There are currently 85 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 Cong Zhao on 2025-09-16.
- No new committers. Last addition was Mingze Han on 2025-07-05.
## Community Health:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper, more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 15% increase in traffic in the past quarter (15 emails compared to 13)
- dev@pulsar.apache.org:
- 82% increase in traffic in the past quarter (319 emails compared to 175)
## Slack activity:
- 10910 Members (10852 in February 2026)
- 133 Active monthly users (162 in February 2026)
-----------------------------------------
Attachment BI: Report from the Apache Ranger Project [Selvamohan Neethiraj]
## Description:
The mission of Apache Ranger is the creation and maintenance of software
related to a data management platform that provides real-time, consistent
access to data-intensive applications throughout widely distributed cloud
architectures.
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Ranger was founded 2017-01-17 (9 years ago)
There are currently 40 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Pradeep Agrawal was added to the PMC on 2026-05-19
- No new committers. Last addition was Vikas Kumar on 2026-01-16.
## Project Activity:
- Apache Ranger 2.8.0 was released on 2026-02-26
- Ranger authorization support for Apache Polaris added in Polaris 1.5.0
release
- community is working on 2.9.0 release, tentatively around end of June
- added Ranger policy decision point (PDP) server, making it easier for
non-Java services to use Ranger authorization
- added audit server to reduce library dependencies in Ranger plugins and make
configurations simpler
- added HTTP header-based authentication to support K8S deployments
- master branch requires JDK17 i.e., JDK8 is no more supported
- updated ranger-plugins-commons library to eliminate several dependent
libraries
- updated tagsync module to Trino entities
- fix in KMS modules
- docker setup improvements
- performance improvements in policy CRUD
- dependent component version updates: commons-configuration2
## Community Health:
- dev@ranger.apache.org had a 13% increase in traffic in the past quarter
(1117 emails compared to 987)
- 126 JIRA tickets opened and 74 closed in the past quarter.
- 74 commits in the past quarter (82 in the past quarter)
- 18 code contributors (authors) in this quarter (23 in the past quarter)
## Most Recent releases:
The project has maintained a regular release cadence over the past year.
- Apache Ranger 2.8.0 was released on 2026-02-26.
- Apache Ranger 2.7.0 was released on 2025-07-30.
- Apache Ranger 2.6.0 was released on 2025-02-15.
- Apache Ranger 2.5.0 was released on 2024-08-07.
-----------------------------------------
Attachment BJ: Report from the Apache Royale Project [Andrew Wetmore]
**Description**: The mission of Apache Royale is the creation and maintenance
of software related to improving developer productivity in creating
applications for wherever JavaScript runs (and other runtimes).
**Project Status**: Current project status: The project is productive, and
working on the 1.0.0 release. Conversations are in progress about future
extensions of Royale.
There are no issues for the Board at this time.
**Membership Data**: Apache Royale was founded 2017-09-19 (8 years ago) There
are currently 20 committers and 17 PMC members in this project. The
Committer-to-PMC ratio is roughly 1:1.
No new PMC members. Last addition was Alina Kazi on 2024-11-02. No new
committers. Last addition was María José Esteve on 2021-11-23.
**Project Activity**: There are active conversations, many related to work on
the coming releases, and to make Apache Flex's Blaze Data Services tool more
available to Royale users.
On May 24 the community voted to approve the release of Apache Royale Compiler
Build Tools 1.2.2. This is a suite of tools that simplifies and monitors the
Royale build process.
**Community Health**: The project membership, though small, continues active.
We have not mapped out a plan yet for trying to attract more participants
from the ActionScript world.
-----------------------------------------
Attachment BK: Report from the Apache SeaTunnel Project [Jun Gao]
-----------------------------------------
Attachment BL: Report from the Apache Shiro Project [Lenny Primak]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None at this time
## Membership Data:
Apache Shiro was founded 2010-09-21 (16 years ago)
There are currently 16 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Steinar Bang on 2026-01-12.
## Project Activity:
We released Shiro 2.2.0 on 5/26/2026.
We also fixed 5 security issues and published 4 CVEs
Working on Project Glasswing as top concerned in the list of ASF projects
## Community Health:
Mailing list traffic is low.
There has been a significant increase of security vulnerability reports.
-----------------------------------------
Attachment BM: Report from the Apache SINGA Project [Wang Wei]
-----------------------------------------
Attachment BN: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Sling was founded 2009-06-17 (17 years ago)
There are currently 53 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Julian Reschke on 2024-10-22.
- No new committers. Last addition was Nicola Scendoni on 2025-11-10.
## Project Activity:
We released version 14 of our sample application, the Sling Starter, on
March 9th, 2026.
In the meantime individual modules are being developed and released,
with 16 releases for this reporting period.
## Community Health:
Community health is pretty good and contributions from various
individuals continue.
-----------------------------------------
Attachment BO: Report from the Apache SpamAssassin Project [Giovanni Bechis]
## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
## Project Status:
Project state: Ongoing with low to moderate activity
Apache SpamAssassin 4.0.2 has been released on 30 August 2025, primary focus
for development is now ongoing maintenance bug fixes to the latest release,
4.0.2. sa-vm.a.o is frequently targeted by DDoS attacks, we're strengthening
firewall rules to minimize the impact.
## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (21 years ago) There are currently
32 committers and 13 PMC members in this project. The Committer-to-PMC ratio
is roughly 2:1.
Community changes, past quarter:
- PMC members: Last addition was Kent Oyer on 2024-11-09.
- No new committers. Last addition was Kent Oyer on 2024-03-29.
## Project Activity:
Last release was Apache SpamAssassin version 4.0.2 on 30 August 2025.
We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility.
## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.
-----------------------------------------
Attachment BP: Report from the Apache Storm Project [Richard Zowalla]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Project Status:
Current project status: Ongoing (reactivated)
Issues for the board: none
## Membership Data:
Apache Storm was founded 2014-09-17 (12 years ago)
There are currently 48 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Purshotam Shah on 2025-05-21.
- No new committers. Last addition was Purshotam Shah on 2024-10-08.
## Project Activity:
The project remains in maintenance mode, but this was an unusually active
quarter on the release front. We handled an influx of (AI-)assisted CVE
reports, triaging and working through them. This effort surfaced 5 genuine
CVEs, which we addressed and shipped across several releases in a short
period.
Recent releases:
2.8.8 was released on 2026-05-18.
2.8.7 was released on 2026-05-01.
2.8.6 was released on 2026-04-12.
2.8.5 was released on 2026-03-23.
2.8.4 was released on 2026-03-06.
## Community Health:
We are candid that the active PMC base is small; we are effectively operating
near the minimum of three active members needed to reach quorum on releases
and formal votes. The PMC has opened an honest, deliberate conversation about
sustainability and how to broaden the active base, rather than letting the
question answer itself.
The outlook - however - here is encouraging. This quarter's release activity
shows the project can still move quickly when it needs to, and we have seen a
welcome uptick in external contributions. We are actively working to grow the
PMC: a vote to bring in a new individual (a Storm user with strong recent
contributions) is currently in progress, and we see real latent capacity in
the StormCrawler community and among other downstream users that we intend to
invite if they demonstrate sustained engagement.
We are optimistic that this momentum will translate into a broader, more
resilient active base going
-----------------------------------------
Attachment BQ: Report from the Apache StreamPark Project [Huajie Wang]
## Description:
StreamPark is a streaming application development framework and cloud-native
real-time computing platform. Its vision is to make stream processing easier.
##Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache StreamPark was founded on 2025-01-23. There are currently 8 committers
and 12 PMC members in this project. The Committer-to-PMC ratio is 2:3.
## Community changes, past quarter:
No new PMC members were added.
No new committers were added.
The GitHub contributor count increased from 155 to 160 (+5). In the reporting
period, four first-time code contributors had PRs merged:
sprybee, thiscodecc, limc5462, and niumy0701.
## Project Activity:
The main project activity during this period has been preparing Apache
StreamPark 2.1.8 as a focused security and maintenance release.
During this period, the project recorded 14 new PRs, 11 merged PRs, 10 new
issues, and 3 closed issues. Other maintenance work included CI/e2e test
stability improvements, configuration cleanup, user environment script
improvements, and minor Web UI fixes.
No formal Apache StreamPark release was completed during this reporting period.
The latest release remains Apache StreamPark v2.1.7, released on 2025-11-05.
Apache StreamPark v2.1.8 is currently being prepared.
## Community Health:
The community remains active, with continued user reports and contributor PRs.
Security response is currently the PMC's highest priority. The PMC has accepted
the reported issues, is coordinating through the ASF security/CVE process, and
plans to resolve the confirmed CVEs and related reports together in the
upcoming 2.1.8 release.
The issue backlog remains significant, and issue closure during this period was
lower than issue creation. The PMC will continue focusing on security fixes,
issue triage, reviewer availability, and preparing the next release.
No major community conflicts were observed.
-----------------------------------------
Attachment BR: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high-performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Project Status:
Current project status: Active
Issues for the board: None
## Membership Data:
Apache Synapse was founded 2007-12-19 (18 years ago)
There are currently 37 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- Thisara Weerakoon was added to the PMC on 2026-05-18
- No new committers. Last addition was Thisara Weerakoon on 2025-12-29.
## Project Activity:
Project activity increased during the quarter. The codebase, build pipeline,
etc. were updated to work with JDK 17. Apache Synapse was also enrolled in the
GLASSWING security scanning program, and the repositories are currently being
prepared to participate in that process. In addition, the community is
currently working on addressing a reported security issue. A new release is
planned in the near future to deliver the fix. These efforts have contributed
to renewed development activity and maintenance work across the project.
## Community Health:
The dev@synapse.apache.org mailing list saw a 28% increase in traffic this
past quarter, with 50 emails compared to 39 in the previous quarter. The
addition of a new PMC member and the increased coordination around JDK 17
support and security scanning indicate that the project has become active
again and is seeing renewed community engagement.
-----------------------------------------
Attachment BS: Report from the Apache Tcl Project [Georgios Petasis]
## Description:
The mission of Tcl is the creation and maintenance of software related to
Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration
efforts. The purpose of our project is to combine the power of the Apache
web server with the capabilities of the mature, robust and flexible Tcl
scripting language. Currently only the Apache Rivet project is actively
maintained.
## Project Status:
Current project status: Ongoing.
Issues for the board: none.
## Membership Data:
Apache Tcl was founded 2000-07-24 (26 years ago)
There are currently 12 committers and 7 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 Brice Hamon De Crevecoer on
2014-11-25.
- No new committers. Last addition was Brice B. Hamon on 2014-11-25.
## Project Activity:
We are still working on making rivet Tcl 9 ready, although the next release
(probably rivet 3.3.0) is not yet ready.
## Community Health:
The mailing lists traffic has been low in this reporting period,
mainly with discussions handling of cookies.
-----------------------------------------
Attachment BT: Report from the Apache Teaclave Project [Zhaofeng Chen]
## Description
Apache Teaclave provides SDKs for building memory-safe applications on Trusted
Execution Environments (TEEs).
## Project Status
**Status:** Ongoing, with healthy activity.
This quarter the community shipped `teaclave-trustzone-sdk v0.9.0`, aligned
with upstream OP-TEE 4.10.0, completed the migration of the no-std/std build
path from `xargo` to `cargo -Z build-std`, landed the long-planned safe
volatile-buffer access API, and welcomed a new PMC member.
## Summary of Project Health and Status
Activity remained steady-to-strong since the last report. The v0.9.0 release
was cut through a formal vote (three binding +1s) and announced on 2026-05-23.
Contributions came from existing committers and from new organizational
contributors (Amazon, Amlogic). The community also invested in
cross-repository hardening — a documented security model and
trust-boundary/TCB analysis spanning the TrustZone SDK, SGX SDK, crates, and
main Teaclave repos, plus branch-protection rulesets. Current focus areas are
developer tooling (`cargo-optee`), memory-safety APIs at the Normal/Secure
World boundary, and staying aligned with OP-TEE's release cadence.
## Issues for Board Attention
There are no Board-level issues at this time.
## Recent Releases
- 2026-05-23: Teaclave TrustZone SDK v0.9.0 (bumps OP-TEE to 4.10.0)
## Project Activity
### Development Activity
- Released v0.9.0, aligned with OP-TEE 4.10.0 and migrating the std build
from
`xargo` to `cargo -Z build-std`.
- Landed the safe volatile-buffer access API (`VolatileBuf`) and
bidirectional memory references for safer Normal/Secure World boundary
interactions.
- Approximately 40 commits merged in the past three months.
### Community Activity
- Developer mailing list: ~130 messages across ~60 threads over the past
three months, driven by the release vote and active code review.
- New organizational contributors landed their first merged PRs this
quarter.
- Prepared a cross-repository security model (trust boundaries / TCB) across
the TrustZone SDK, SGX SDK, crates, and main Teaclave repos, laying
groundwork for AI-assisted security scanning.
## Current Plans
- **Short term (next quarter):**
- Continue the quarterly release cadence aligned with OP-TEE.
- Further harden boundary-safety APIs (build on `VolatileBuf` / access
API).
- Keep enhancing `cargo-optee` (toolchain management, onboarding).
- **Medium term:**
- Open source additional real-world SDK use cases.
- Maintain alignment with OP-TEE's quarterly release cadence.
## Community Changes
- **New PMC member: Zehui Chen (ivila)** — the quarter's most active
contributor, announced on the dev list in April 2026.
- Committers: no new committer added this period.
- 19 PMC members / 10 committers
## Project Branding
- No branding issues; website and download pages comply with Apache
requirements.
## Legal Issues
- No legal issues to report.
## Infrastructure
- No concerns. Default branch-protection rulesets were rolled out across
project repositories this quarter.
-----------------------------------------
Attachment BU: Report from the Apache Tomcat Project [Christopher Schultz]
## Description:
Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.
The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10
and later implement specifications developed as part of Jakarta EE. Tomcat 9
and earlier implement specifications developed as part of Java EE.
## Project Status:
The Tomcat project is ongoing with moderate activity, having a strong and
active community of both users and committers. We maintain 3 major release
version numbers, and have a release cadence of approximately one release per
major-version per month.
Issues for the board: none
## Membership Data:
Apache Tomcat was founded 2005-05-17 (21 years ago)
There are currently 50 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Soumis on 2025-02-18.
- No new committers. Last addition was John Engebretson on 2025-02-05.
## Project Activity:
Tomcat 9.0.116 was released on 2026-03-20.
Tomcat 10.1.53 was released on 2026-03-23.
Tomcat 11.0.20 was released on 2026-03-20.
Tomcat 9.0.117 was released on 2026-04-03.
Tomcat 10.1.54 was released on 2026-04-02.
Tomcat 11.0.21 was released on 2026-04-03.
Tomcat 9.0.118 was released on 2026-05-10.
Tomcat 10.1.55 was released on 2026-05-11.
Tomcat 11.0.22 was released on 2026-05-05.
Tomcat Migration Tool for Jakarta EE 1.0.12 was released 2026-06-05.
We have secured a grant from HeroDevs' Open Source Sustainability Fund
which will be a directed donation to the ASF. We expect to use this grant to
fund a "Security Day" attached to the upcoming CoC in Glasgow in the fall.
We have signed-up for the ASF's GLASSWING scan, but nothing has actually
happened, yet. Since we haven't gotten anything from GLASSWING, a group of
committers has started using their own local models as well as
employer-sponsored services to begin analyzing the source code. Several
real-world security- and non-security bugs have been identified and fixed
through this process.
## Community Health:
Continued healthy activity across multiple components and responsiveness on
both dev and user lists.
-----------------------------------------
Attachment BV: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache TomEE was founded 2007-05-16 (19 years ago)
There are currently 36 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Markus Jung on 2025-07-28.
- No new committers. Last addition was Markus Jung on 2024-09-12.
## Project Activity:
Significant progress has been made on the next major version of Apache TomEE,
with our implementations for Jakarta Data 1.0, Jakarta Concurrency 3.1 and
Jakarta Security 4.0 all having landed in main this quarter. The first
milestone release 11.0.0-M1 is being voted on right now.
Releases in the past quarter:
- Apache TomEE 10.1.5, released on 2026-05-05
- Apache TomEE JakartaEE API 11.0.0-M1, released on 2026-06-08
## Community Health:
Overall contributions are still low for a project of our size, TomEE 11 being
a new feature release has made development more active though. We have seen a
new face being promising and contributing a bigger chunk of code quality
improvements in February and being involved in discussions and release votes.
The ongoing work on Apache TomEE 11.x caused lifted activity on the dev@ mailing
list. There has also been an influx of users asking questions that have all been
answered within a couple days on the users@ list.
-----------------------------------------
Attachment BW: Report from the Apache TVM Project [Tianqi Chen]
## Description:
The mission of Apache TVM is the creation and maintenance of software related
to compilation of machine learning models to run on a wide range of hardware
platforms
## Project Status:
Current project status: ongoing
Issues for the board: N/A
## Membership Data:
Apache TVM was founded 2020-11-17 (6 years ago) There are currently 84
committers and 30 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Yong Wu on 2025-09-11.
- Akaash Raghunathan Parthasarathy was added as committer on 2026-05-05
## Project Activity:
Recent releases:
- tvm v0.24 was released on 2026-05-08
- tvm-ffi v0.1.11 was released on 2026-05-04.
The community continues to bring improvement and refactoring to modularize the
components for to enable lightweight kernel compilations. Improvements include
- Modularize per backend libraries for packaging
- Cleanup of utilities and make use of tvm-ffi package as much as possible
- Improvements over frontend coverages
- Codegen support for latest GPUs (B200)
## Community Health:
We see continued contributions to the project, with about 100 commits monthly
in the past quarter. AI’s capability is also getting stronger and we see AI
PRs. AI reviews continues to help streamline some burdens but there is a
stronger need in clean architecture and modularization boundaries. We will
expect to see more modular components developments. One next component that is
shaping up is minimal components for FFI and low-level LLVM code generation
integration.
-----------------------------------------
Attachment BX: Report from the Apache UIMA Project [Richard Eckart de Castilho]
## Description:
Apache UIMA* software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video.
* Unstructured Information Management Architecture.
## Project Status:
Current project status: Ongoing (dormant with a recent wake period)
Issues for the board: none
## Membership Data:
Apache UIMA was founded 2010-03-17 (16 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.
## Project Activity:
* uima-ruta-3.5.1 was released on 2025-10-13.
* uimaj-3.6.1 was released on 2025-10-01.
* uima-ruta-3.5.0 was released on 2024-12-04.
## Community Health:
There has not really been any particularly notable or significant
activity to report.
-----------------------------------------
Attachment BY: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Unomi was founded 2019-02-20 (7 years ago)
There are currently 17 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jonathan Sinovassin-Naïk on 2024-11-25.
- No new committers. Last addition was Jerome Blanchard on 2025-09-13.
## Project Activity:
This quarter was focused on the staged integration of the Unomi 3.x
multi-tenant platform, landed as a series of reviewable PRs, alongside test
infrastructure hardening and developer tooling improvements. No bugs were
reported against 3.0.0 that required an immediate patch; all fixes have been
folded into 3.1.0, which is expected to release once the remaining PRs are
reviewed and tests validated.
## Community Health:
Monthly meetings were well attended and held regularly this quarter, used for
discussion and coordination only — all decisions are made on the mailing lists
as per ASF requirements. Topics included, for example, the use of stacked PRs
to manage large contributions more reviewably. Commit activity this quarter is
concentrated on one contributor because the project is in an active
pre-release integration phase for 3.1.0; once that release ships, activity is
expected to broaden to maintenance and more incremental contributions.
-----------------------------------------
Attachment BZ: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.
## Project Status:
Current project status: Dormant
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (14 years ago) There are currently 10
committers and 8 PMC members in this project. The Committer-to-PMC ratio is
5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
- Last release: 2025-03-24
- no activity in the last quarter
## Community Health:
Continuing the theme of the last few reports of being a used project but
little to no activity.
-----------------------------------------
Attachment CA: Report from the Apache Web Services Project [Daniel Kulp]
## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.
## Project Status:
Current project status: ongoing, very low activity
Issues for the board: 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...
A large majority of the changes in each project are just Dependabot updates.
There was a patch release of Neethis to address three CVE's that were
discovered and are now public. Axiom has also had a bunch of updates
as it gets updated for some more modern patterns. Another chunk of work
was to get the WS repositories ready for the Glasswing/Anthropic scans.
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). A third did volunteer to backup Colm for the Glasswing scans.
We are curious to see if the results of the scans overwhelm the couple of
people doing the work or not. The Neethi vote 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 CB: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
The mission of Wicket is the creation and maintenance of software related to
Component-based Java Web Application Framework.
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: no issue to report
## Membership Data:
Apache Wicket was founded 2007-06-20 (19 years ago)
There are currently 35 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Pavlovich on 2025-01-27.
- No new committers. Last addition was Matt Pavlovich on 2025-01-27.
## Project Activity:
In the last quarter we have been pretty busy reviewing and fixing CVE found
with the IA, which currently it's probably the hottest topic in the IT
industry :-).
We had 4 releases in the last quarter
10.9.1 was released on 2026-05-20.
8.18.0 was released on 2026-05-15.
9.23.0 was released on 2026-05-13.
10.9.0 was released on 2026-05-05.
With the exception of version 10.9.1 which contains a JavaScript hotfix,
the other releases contains a fix for the following CVEs:
CVE-2026-43646 crafted URLs can bypass PackageResourceGuard
CVE-2026-42509 crafted strings can break out of the JavaScript sequence
CVE-2026-40010 possible session fixation using AuthenticatedWebSession
CVE-2026-43975 Possible malicious path traversal in FolderUploadsFileManager
(This last not in the 8.18.0)
## Community Health:
Community is very healthy and active. On the 3th of May we held the first
"Wicket User Day" in Dordrecht, The Netherlands. The event had about 20
participants both physically and remotely. Among them we had some PCMs, new
friends and our founder Jonathan Locke.
It was very amazing seeing these people loving our work and putting new energy
and ideas into the project. We hope to develop some of their feedback in
the next months.
Speaking of which, we are trying to regain control on our old X (Twitter)
account as some people brought to our attention that the state we left this
account suggests that Apache Wicket is no more active and developed.
I tried to reach out for the original account owner (Francois Meillet) to ask
for help but so far we had no reply. I don't know if the ASF can help us
contacting X and regaining control on our account.
PS: I (Andrea Del Bene) personally planned to join it physically but I got
my flight cancelled last minute :-( .
-----------------------------------------
Attachment CC: Report from the Apache Xerces Project [Michael Glavassevich]
## Description:
Apache Xerces exists to promote the use of XML. We view XML as a compelling
paradigm that structures data as information, thereby facilitating the
exchange, transformation, and presentation of knowledge. The ability to
transform raw data into usable information has great potential to improve the
functionality and use of information systems. We intend to build freely
available XML parsers and closely related technologies in order to engender
such improvements.
## Project Status:
Current project status: Ongoing (low activity). All sub-projects are in bug
fix mode and maintenance mode. Xerces-J and XML Commons have had recent
activity. Issues for the board: None
## Membership Data:
Apache Xerces was founded 2005-02-22 (21 years ago)
There are currently 19 committers and 15 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 Gary D. Gregory on 2026-02-27.
- No new committers. Last addition was Gary D. Gregory on 2026-02-28.
## Project Activity:
The focus for Xerces continues to be maintenance. No new features are in
development. The developers have been cleaning up the automated build and
tests for Xerces-J and have explored how to protect the repository against
supply chain attacks. 15 PRs have been merged in Xerces-J since the beginning
of March. Aside from a couple PRs that were opened by new contributors, there
was no visible activity on Xerces-C. The status of XML Commons in GitHub was
discussed. The code was mirrored into Xerces-J's repository during the
migration from SVN to GitHub, but perhaps these branches belong as part of
their own separate repository. Multiple old XML Commons JIRA issues were
resolved and closed.
No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022). The latest release is Xerces-C 3.3.0 (October
14th, 2024).
## Community Health:
Our project for more than the last decade has had a handful of dedicated
active committers. Some less active PMC members continue to monitor the
project and respond to queries on security issues as needed. We still have a
TODO to check for signs of life on Xerces-C. The recently active and new
members of the PMC are all Java developers. For the PRs that were opened for
Xerces-C no one has reviewed or responded to them yet.
-----------------------------------------
Attachment CD: Report from the Apache Yetus Project [Allen Wittenauer]
-----------------------------------------
Attachment CE: Report from the Apache ZooKeeper Project [Flavio Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (16 years ago)
There are currently 34 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kezhu Wang on 2026-01-19.
- No new committers. Last addition was Christopher Tubbs on 2025-11-18.
## Project Activity:
No release during the period, although there has been a noticeable increase
project traffic, see traffic in lists such as dev@ and issues@. The community
plans to continue working towards the next maintenance release of 3.9 and a
major 3.10.0 release.
## Community Health:
The mailing list metrics indicate an increase in project traffic, which
is clearly positive from a project health perspective.
- dev@zookeeper.apache.org had a 105% increase in traffic in the
past quarter (123 emails compared to 60)
- issues@zookeeper.apache.org had a 110% increase in traffic in the
past quarter (221 emails compared to 105)
- notifications@zookeeper.apache.org had a 106% increase in traffic
in the past quarter (305 emails compared to 148)
- user@zookeeper.apache.org had a 34% decrease in traffic in the past
quarter (8 emails compared to 12)
- 29 JIRA tickets opened and 17 closed in the past quarter.
------------------------------------------------------
End of minutes for the June 17, 2026 board meeting.
Index