[raw] the published text, which is the record. [2026] [main index]
The Apache Software Foundation
Board of Directors Meeting Minutes
September 16, 2026
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:02 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2026-09-16T21: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
Andrew Wetmore
Jamie Goodyear
Alin Jerpelea
Dave Fisher
Jeff Genender
Jarek Potiuk - joined :04
Henri Yandell
Paul King
Brian Proffitt
Andrew Musselman
Drew Foulks - joined :04
Danny Angus - joined :04
Rich Bowen - joined :10
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of August 19, 2026
See: board_minutes_2026_08_19.txt
Approved by General Consent.
B. The meeting of July 15, 2026
See: board_minutes_2026_07_15.txt
Tabled.
4. Actions Without a Meeting
A. Change the Apache AGE Project Chair
WHEREAS, the Board of Directors heretofore appointed Jeff Jirsa (jjirsa) to
the office of Vice President, Apache AGE, and
WHEREAS, the Board of Directors is in receipt of the resignation of Jeff Jirsa
from the office of Vice President, Apache AGE, and
WHEREAS, the Project Management Committee of the Apache AGE project has chosen
by vote to recommend Muhammad Shoaib (shoaib88) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jeff Jirsa is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
AGE, and
BE IT FURTHER RESOLVED, that Muhammad Shoaib be and hereby is appointed to the
office of Vice President, Apache AGE, to serve in accordance with and subject
to the direction of the Board of Directors and the Bylaws of the Foundation
until death, resignation, retirement, removal or disqualification, or until a
successor is appointed.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
B. Change the Apache Mahout Project Chair
WHEREAS, the Board of Directors heretofore appointed Shannon Quinn (squinn) to
the office of Vice President, Apache Mahout, and
WHEREAS, the Board of Directors is in receipt of the resignation of Shannon
Quinn from the office of Vice President, Apache Mahout, and
WHEREAS, the Project Management Committee of the Apache Mahout project has
chosen by vote to recommend Jie-Kai Chang (jiekaichang) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Shannon Quinn is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Mahout, and
BE IT FURTHER RESOLVED, that Jie-Kai Chang be and hereby is appointed to the
office of Vice President, Apache Mahout, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
C. Change the Apache Portable Runtime (APR) Project Chair
WHEREAS, the Board of Directors heretofore appointed Yann Ylavic (ylavic) to
the office of Vice President, Apache Portable Runtime (APR), and
WHEREAS, the Board of Directors is in receipt of the resignation of Yann
Ylavic from the office of Vice President, Apache Portable Runtime (APR), and
WHEREAS, the Project Management Committee of the Apache Portable Runtime (APR)
project has chosen by vote to recommend Rüdiger Plüm (rpluem) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Yann Ylavic is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Portable Runtime (APR), and
BE IT FURTHER RESOLVED, that Rüdiger Plüm be and hereby is appointed to the
office of Vice President, Apache Portable Runtime (APR), to serve in
accordance with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
D. Terminate the Apache MADlib Project
WHEREAS, the Board of Directors deems it no longer in the best interest of the
Foundation to continue the Apache MADlib project due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache MADlib project is hereby
terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the
software developed by the Apache MADlib Project; and be it further
RESOLVED, that the office of "Vice President, Apache MADlib" is hereby
terminated; and be it further
RESOLVED, that the Apache MADlib PMC is hereby terminated.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
E. Establish the Apache ResilientDB 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 ResilientDB
is a distributed blockchain framework that is open-source, lightweight,
modular, and highly performant..
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
be known as the "Apache ResilientDB Project", be and hereby is established
pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache ResilientDB be and hereby is responsible for the
creation and maintenance of software related to ResilientDB is a distributed
blockchain framework that is open-source, lightweight, modular, and highly
performant.; and be it further
RESOLVED, that the office of "Vice President, Apache ResilientDB" 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 ResilientDB Project, and to
have primary responsibility for management of the projects within the scope of
responsibility of the Apache ResilientDB 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 ResilientDB
Project:
* Junping Du <junping_du@apache.org>
* Kevin Ratnasekera <djkevincr@apache.org>
* Roman Shaposhnik <rvs@apache.org>
* Junchao Chen <junchao@apache.org>
* Mohammad Sadoghi <msadoghi@apache.org>
* Suyash Gupta <suyashgupta@apache.org>
* Divjeet Singh Jas <divjeet@apache.org>
* Haskell Macaraig <hmacaraig@apache.org>
* Thamir Qadah <qadahtm@apache.org>
* Glenn Chen <gchen@apache.org>
* Priya Holani <priyaholani@apache.org>
* Shreenath Iyer <shreenathiyer@apache.org>
* Gopal Nambiar <gopuman@apache.org>
* Seongwoo Choi <swchoi1994@apache.org>
* Dakai Kang <dakaikang@apache.org>
* Apratim Shukla <apratim@apache.org>
* Priyal Soni <priyal@apache.org>
* Dhruv Krishnan <dhruvkris@apache.org>
* Sajjad Rahnama <sajjadrahnama@apache.org>
* Arindaam Roy <aroy@apache.org>
* Shubham Pandey <shubhampandey@apache.org>
* Julieta Duarte <juduarte@apache.org>
* Shaokang Xie <shaokang@apache.org>
* Bisman Anand <bisman@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mohammad Sadoghi be appointed to
the office of Vice President, Apache ResilientDB, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the Apache ResilientDB Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator ResilientDB podling; and
be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
ResilientDB podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
F. Establish the Apache Reqsign 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 signing HTTP
requests to cloud services.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
be known as the "Apache Reqsign Project", be and hereby is established
pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Reqsign be and hereby is responsible for the
creation and maintenance of software related to signing HTTP requests to cloud
services; and be it further
RESOLVED, that the office of "Vice President, Apache Reqsign" 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 Reqsign Project, and to have primary
responsibility for management of the projects within the scope of
responsibility of the Apache Reqsign 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 Reqsign
Project:
* Erick Guan <erickguan@apache.org>
* Chojan Shang <psiace@apache.org>
* Hao Ding <xuanwo@apache.org>
* Han Xu <suyanhanx@apache.org>
* Zili Chen <tison@apache.org>
* Hao Jiang <dentiny@apache.org>
* Mingzhuo Yin <silver@apache.org>
* Qinxuan Chen <koushiro@apache.org>
* Liuqing Yue <liuqingyue@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Zili Chen be appointed to the
office of Vice President, Apache Reqsign, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the Apache Reqsign Project be and hereby is tasked with the
migration and rationalization of the Apache OpenDAL Reqsign sub-project; and
be it further
RESOLVED, that all responsibilities pertaining to the Apache OpenDAL Reqsign
sub-project encumbered upon the Apache OpenDAL Project are hereafter
discharged.
Adopted by the unanimous written consent of the Board of Directors on
September 16, 2026 as an Action Without a Meeting (Bylaws 5.12).
5. Executive Officer Reports
A. Board Chair [Sander Striker]
Last month I mentioned that I intended to make our decision-making more
asynchronous and to normalize written consent, so that uncontroversial matters
don't sit for any longer than they need to. Given the large number of special
orders this month, I am disappointed that we were not able to at least pass
one Action without a Meeting. In part this was due to a issue with
configuration. I expect us to do better next month, and request your help in
doing so.
Like I mentioned last month, I've been investing in progress on reporting
changes discussed in June 2024 (8C) and re-affirmed in September 2025 (8B).
Tooling is now at a point where it can serve as a foundation for this change.
Early adoption should be doable by the November meeting. I expect that as a
side effect missing, or rather delayed, reports will go down; this has been
sitting around 19% in the past years.
As a last minute update, about two hours before our meeting, I am pleased to
see that we did take some actions without a meeting.
B. President [Ruth Suehle]
Nothing particularly interesting from me this month; just supporting all these
awesome folks and the things they're doing:
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig McClanahan]
Normal operations continue.
Starting with the September 2026 report, you will start to see charges to the
new accounts for the Responsible API budget that was approved recently.
Following the lead of how Infra does things, we've assigned individual Ramp
cards for each vendor where we are paying for tokens or whatever - but also
going to be splitting them in the financial reports per vendor, based on the
RAI approved budget.
D. Secretary [Matt Sicker]
In July, we received 44 ICLAs, 2 CCLAs, and 1 software grant. In August, we
received 59 ICLAs, 3 CCLAs, and 1 software grant.
E. Executive Vice President [Daniel Ruggeri]
No news is good news - actively following the various threads, but nothing to
report to the board that isn't already well covered.
F. Vice Chair [Justin Mclean]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
6. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Christopher Schultz]
See Attachment 12
B. Apache Legal Affairs Committee [Justin Mclean / Greg Stein]
See Attachment 13
C. Apache Security Team Project [Mark J. Cox / Justin Mclean]
See Attachment 14
D. VP of Responsible AI [Jeff Genender / Sander Striker]
See Attachment 15
Additional officer reports approved as submitted by General Consent.
7. Committee Reports
Summary of Reports
The following reports required further discussion:
# Flex [jmclean]
# HugeGraph [jmclean, schultz]
# Iceberg [jmclean]
# Legal Affairs [gstein, schultz]
# Lucene.Net [jmclean]
# OpenDAL [schultz]
# Pulsar [jmclean]
# Responsible AI [jmclean]
# Samza [elecharny]
# Security Team [schultz]
# cTAKES [jmclean]
A. Apache AGE Project [Jeff Jirsa / Zili Chen]
See Attachment A
B. Apache Airavata Project [Suresh Marru / Jean-Baptiste Onofré]
No report was submitted.
C. Apache Airflow Project [Bolke de Bruin / Emmanuel Lécharny]
No report was submitted.
D. Apache Allura Project [Dave Brondsema / Sander Striker]
See Attachment D
E. Apache Ambari Project [Brahma Reddy Battula / Shane Curcuru]
No report was submitted.
F. Apache Atlas Project [Madhanmohan Neethiraj / Christofer Dutz]
No report was submitted.
G. Apache Axis Project [Robert Lazarski / Christofer Dutz]
See Attachment G
H. Apache Beam Project [Kenneth Knowles / Justin Mclean]
See Attachment H
I. Apache Bigtop Project [Masatake Iwasaki / Jean-Baptiste Onofré]
See Attachment I
J. Apache BookKeeper Project [Enrico Olivelli / Emmanuel Lécharny]
No report was submitted.
K. Apache BuildStream Project [Abderrahim Kitouni / Sander Striker]
No report was submitted.
L. Apache BVal Project [Matt Benson / Greg Stein]
See Attachment L
M. Apache Camel Project [Andrea Cosentino / Zili Chen]
See Attachment M
N. Apache Cayenne Project [Michael Gentry / Shane Curcuru]
See Attachment N
O. Apache Celeborn Project [Keyong Zhou / Christopher Schultz]
No report was submitted.
P. Apache CloudStack Project [Wido den Hollander / Justin Mclean]
See Attachment P
Q. Apache Commons Project [Gary D. Gregory / Zili Chen]
See Attachment Q
R. Apache Cordova Project [Bryan Ellis / Christopher Schultz]
See Attachment R
S. Apache CouchDB Project [Jan Lehnardt / Jean-Baptiste Onofré]
See Attachment S
T. Apache cTAKES Project [Pei J Chen / Sander Striker]
See Attachment T
@Sander Striker: pursue roll call
U. Apache Curator Project [Enrico Olivelli / Emmanuel Lécharny]
No report was submitted.
V. Apache Daffodil Project [Steve Lawrence / Shane Curcuru]
See Attachment V
W. Apache DataFusion Project [Andrew Lamb / Christofer Dutz]
See Attachment W
X. Apache DevLake Project [Hezheng Yin / Greg Stein]
See Attachment X
Y. Apache Drill Project [Charles Givre / Shane Curcuru]
See Attachment Y
Z. Apache ECharts Project [Wenli Zhang / Justin Mclean]
See Attachment Z
AA. Apache EventMesh Project [Eason Chen / Sander Striker]
No report was submitted.
AB. Apache Felix Project [Karl Pauls / Greg Stein]
See Attachment AB
AC. Apache Flex Project [Harbs / Christopher Schultz]
No report was submitted.
@Christopher Schultz: pursue roll call
AD. Apache Flink Project [Robert Metzger / Christofer Dutz]
See Attachment AD
AE. Apache Fluss Project [Jark Wu / Jean-Baptiste Onofré]
See Attachment AE
AF. Apache Geronimo Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
AG. Apache Gobblin Project [Abhishek Tiwari / Emmanuel Lécharny]
See Attachment AG
AH. Apache Gravitino Project [Jerry Shao / Sander Striker]
No report was submitted.
AI. Apache Guacamole Project [Mike Jumper / Zili Chen]
No report was submitted.
AJ. Apache Gump Project [Stefan Bodewig / Jean-Baptiste Onofré]
See Attachment AJ
AK. Apache Helix Project [Junkai Xue / Justin Mclean]
See Attachment AK
AL. Apache Hive Project [Naveen Gangam / Christofer Dutz]
No report was submitted.
AM. Apache Hudi Project [Vinoth Chandar / Sander Striker]
See Attachment AM
AN. Apache HugeGraph Project [Jermy Li / Emmanuel Lécharny]
See Attachment AN
AO. Apache Iceberg Project [Ryan Blue / Zili Chen]
See Attachment AO
@Jean-Baptiste Onofré: follow up about websites
AP. Apache Iggy Project [Kranti Parisa / Christopher Schultz]
See Attachment AP
AQ. Apache Incubator Project [Justin Mclean / Justin Mclean]
See Attachment AQ
AR. Apache IoTDB Project [Xiangdong Huang / Christopher Schultz]
See Attachment AR
AS. Apache Jackrabbit Project [Marcel Reutegger / Shane Curcuru]
See Attachment AS
AT. Apache Johnzon Project [Jean-Louis Monteiro / Greg Stein]
No report was submitted.
AU. Apache Karaf Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré]
See Attachment AU
AV. Apache Knox Project [Larry McCay / Zili Chen]
See Attachment AV
AW. Apache Kvrocks Project [Mingyang Liu / Shane Curcuru]
No report was submitted.
AX. Apache Kyuubi Project [Cheng Pan / Emmanuel Lécharny]
See Attachment AX
AY. Apache Linkis Project [Shuai Di / Sander Striker]
See Attachment AY
AZ. Apache Livy Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré]
See Attachment AZ
BA. Apache Lucene Project [Ben Trent / Christopher Schultz]
See Attachment BA
BB. Apache Lucene.Net Project [Shad Storhaug / Justin Mclean]
No report was submitted.
@Emmanuel Lécharny: follow up on roll call
BC. Apache MADlib Project [Ed Espino / Zili Chen]
No report was submitted.
BD. Apache Magpie Project [Jarek Potiuk / Greg Stein]
See Attachment BD
BE. Apache Mynewt Project [Szymon Janc / Jean-Baptiste Onofré]
See Attachment BE
BF. Apache NetBeans Project [Geertjan Wielenga / Christofer Dutz]
See Attachment BF
BG. Apache OFBiz Project [Jacopo Cappellato / Jean-Baptiste Onofré]
See Attachment BG
BH. Apache OpenDAL Project [Hao Ding / Christopher Schultz]
See Attachment BH
BI. Apache OpenNLP Project [Jeffrey T. Zemerick / Sander Striker]
See Attachment BI
BJ. Apache OpenWebBeans Project [Mark Struberg / Christopher Schultz]
No report was submitted.
BK. Apache ORC Project [William Hyun / Christofer Dutz]
See Attachment BK
BL. Apache Paimon Project [Jingsong Lee / Zili Chen]
See Attachment BL
BM. Apache Pekko Project [PJ Fanning / Greg Stein]
See Attachment BM
BN. Apache Pig Project [Koji Noguchi / Emmanuel Lécharny]
No report was submitted.
BO. Apache Pinot Project [Kishore G / Greg Stein]
No report was submitted.
BP. Apache PLC4X Project [Lukas Ott / Justin Mclean]
See Attachment BP
BQ. Apache Pony Mail Project [Rich Bowen / Shane Curcuru]
See Attachment BQ
BR. Apache Portable Runtime (APR) Project [Yann Ylavic / Christofer Dutz]
See Attachment BR
BS. Apache Pulsar Project [Matteo Merli / Sander Striker]
See Attachment BS
@Christopher Schultz: let know about release vote guidelines
BT. Apache Ranger Project [Selvamohan Neethiraj / Emmanuel Lécharny]
No report was submitted.
BU. Apache RocketMQ Project [Xiaorui Wang / Greg Stein]
No report was submitted.
BV. Apache Royale Project [Andrew Wetmore / Jean-Baptiste Onofré]
See Attachment BV
BW. Apache Samza Project [Jagadish Venkatraman / Shane Curcuru]
See Attachment BW
@Shane Curcuru: pursue roll call
BX. Apache SeaTunnel Project [Jun Gao / Christopher Schultz]
No report was submitted.
BY. Apache ServiceComb Project [Zhangjian He / Justin Mclean]
No report was submitted.
BZ. Apache Shiro Project [Lenny Primak / Zili Chen]
No report was submitted.
CA. Apache SINGA Project [Wang Wei / Zili Chen]
See Attachment CA
CB. Apache Sling Project [Alexandru-Robert Munteanu / Jean-Baptiste Onofré]
See Attachment CB
CC. Apache Sourcelume Project [Jamie Goodyear / Christofer Dutz]
See Attachment CC
CD. Apache SpamAssassin Project [Giovanni Bechis / Justin Mclean]
See Attachment CD
CE. Apache Steve Project [Greg Stein / Greg Stein]
See Attachment CE
CF. Apache Storm Project [Richard Zowalla / Emmanuel Lécharny]
See Attachment CF
CG. Apache StreamPark Project [Huajie Wang / Shane Curcuru]
No report was submitted.
CH. Apache Synapse Project [Isuru Udana / Sander Striker]
See Attachment CH
CI. Apache Tcl Project [Georgios Petasis / Greg Stein]
See Attachment CI
CJ. Apache Teaclave Project [Zhaofeng Chen / Christopher Schultz]
See Attachment CJ
CK. Apache Tomcat Project [Christopher Schultz / Christopher Schultz]
See Attachment CK
CL. Apache TsFile Project [Jialin Qiao / Christopher Schultz]
See Attachment CL
CM. Apache TVM Project [Tianqi Chen / Justin Mclean]
See Attachment CM
CN. Apache UIMA Project [Richard Eckart de Castilho / Zili Chen]
See Attachment CN
CO. Apache Unomi Project [Serge Huber / Emmanuel Lécharny]
See Attachment CO
CP. Apache VCL Project [Josh Thompson / Jean-Baptiste Onofré]
See Attachment CP
CQ. Apache Velocity Project [Nathan Bubna / Christofer Dutz]
See Attachment CQ
CR. Apache Wicket Project [Andrea Del Bene / Sander Striker]
See Attachment CR
CS. Apache Xerces Project [Michael Glavassevich / Jean-Baptiste Onofré]
See Attachment CS
CT. Apache Yetus Project [Allen Wittenauer / Shane Curcuru]
See Attachment CT
CU. Apache ZooKeeper Project [Flavio Junqueira / Greg Stein]
See Attachment CU
Committee reports approved as submitted by General Consent.
8. Special Orders
A. Dissolve Legal Affairs as a Board Committee
WHEREAS, the Legal Affairs Committee was established as an Executive Committee
of the Board of Directors by resolution of 28 March 2007 (Special Order 6C),
responsible for establishing and managing legal policies; and
WHEREAS, those functions have in practice been carried out through the office
of Vice President, Legal Affairs, and the Board deems it to be in the best
interests of the Foundation that they continue under a clear delegation of
authority to that office;
NOW, THEREFORE, BE IT RESOLVED, that the Legal Affairs Committee is hereby
dissolved as a committee of the Board, and all actions taken by or under its
authority are hereby ratified and affirmed; and be it further
RESOLVED, that the office of Vice President, Legal Affairs, appointed by and
serving at the direction of the Board, be and hereby is continued, with
responsibility for the legal affairs of the Foundation, including
custodianship of the Apache License and the Foundation's other licensing and
contribution instruments, establishing and maintaining legal policy binding on
the Foundation's projects and officers, and resolving legal questions raised
by projects and officers, with such resolutions binding on the requesting
party, in each case unless the Board directs otherwise. The legal affairs of
the Foundation are any matter concerning the licensing, provenance, or terms
governing contributions to and releases of the Foundation's projects; the
Foundation's intellectual property; contracts and agreements concerning the
Foundation's projects, software, or intellectual property; and the regulatory
and statutory obligations applicable to the Foundation or its projects; and be
it further
RESOLVED, that guidance issued by other officers and committees within their
own areas of responsibility shall be consistent with legal policy so
established, with questions of interpretation of such policy resolved by the
Vice President, Legal Affairs; and be it further
RESOLVED, that all policies and guidance previously adopted by or under the
authority of the Legal Affairs Committee, including those published at
https://www.apache.org/legal/ (4e9377d), remain in full force and effect as
policies of the Vice President, Legal Affairs until amended or revoked by
that officer; and be it further
RESOLVED, that matters concerning the Bylaws of the Foundation, the initiation
or settlement of litigation, and modification of the Apache License remain
reserved to the Board, and that trademark and brand management matters remain
delegated to the Vice President, Brand Management; and be it further
RESOLVED, that the Vice President, Legal Affairs may delegate responsibilities
to a legal team of the Vice President's choosing, shall document the scope and
current policies of the office at https://www.apache.org/legal/, and shall
continue to report monthly to the Board.
Special Order 8A, Dissolve Legal Affairs as a Board Committee,
was approved (yes: Zili Chen, Shane Curcuru, Christofer Dutz,
Emmanuel Lécharny, Justin Mclean, Jean-Baptiste Onofré,
Christopher Schultz, Sander Striker; no: Greg Stein).
B. Establish the Apache Auron 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 an
accelerator for big data engines that leverages native vectorized execution to
accelerate query processing.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
be known as the "Apache Auron Project", be and hereby is established pursuant
to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Auron Project be and hereby is responsible for the
creation and maintenance of software related to an accelerator for big data
engines that leverages native vectorized execution to accelerate query
processing; and be it further
RESOLVED, that the office of "Vice President, Apache Auron" 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 Auron Project, and to have primary
responsibility for management of the projects within the scope of
responsibility of the Apache Auron 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 Auron Project:
* Becket Qin <jqin@apache.org>
* Qiang Guo <kirs@apache.org>
* Hao Ding <xuanwo@apache.org>
* Nicholas Jiang <nicholasjiang@apache.org>
* Yijie Shen <yjshen@apache.org>
* Shaoyun Chen <csy@apache.org>
* Zhen Wang <wangzhen@apache.org>
* Junfan Zhang <zuston@apache.org>
* Lei Wang <wanglei@apache.org>
* Yuance Li <liyuance@apache.org>
* Li Zhang <richox@apache.org>
* Hao Li <lihao@apache.org>
* Jiashu Xiong <rexxiong@apache.org>
* Fei Wang <feiwang@apache.org>
* Ruilei Ma <maruilei@apache.org>
* Mang Zhang <zhangmang@apache.org>
* Shreyesh Arangath <shreyesh@apache.org>
* Shilun Fan <slfan1989@apache.org>
* Hai Zhou <yew1eb@apache.org>
* Gui Huawen <guihuawen@apache.org>
* Weiqing Yang <weiqing@apache.org>
* Ming Wei <mingwei@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lei Wang be appointed to the
office of Vice President, Apache Auron, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the Apache Auron Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Auron podling; and be it
further
RESOLVED, that all responsibilities pertaining to the Apache Incubator Auron
podling encumbered upon the Apache Incubator PMC are hereafter discharged.
Special Order 8B, Establish the Apache Auron Project, was
approved by Unanimous Vote of the directors present.
C. Establish the Office of Assistant Vice President, Security
WHEREAS, the Board of Directors deems it to be in the best interests of the
Foundation to establish the office of Assistant Vice President, Security;
NOW, THEREFORE, BE IT RESOLVED, that the office of "Assistant Vice President,
Security" be and hereby is created, the person holding such office to serve at
the direction of and reporting to the Vice President, Security, and to assist
that officer in the organization and oversight of efforts to maintain the
security of software produced by the Foundation's projects; and be it further
RESOLVED, that the Assistant Vice President, Security be and hereby is
authorized to exercise any and all authority granted by the Board to the
office of Vice President, Security, except the authority to appoint and remove
persons under this resolution and such other authority as the Board may
explicitly exclude, any exercise of such authority to be reported promptly to
the Vice President, Security; and be it further
RESOLVED, that the Vice President, Security be and hereby is authorized to
appoint persons to, and remove persons from, the office of Assistant Vice
President, Security; and be it further
RESOLVED, that Henri Yandell (bayard) be and hereby is appointed to the office
of Assistant Vice President, Security, to serve in accordance with and subject
to the Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 8C, Establish the Office of Assistant Vice
President, Security, was approved by Unanimous Vote of the
directors present.
D. Officer Contracting Authority; Ratification of Prior Instruments
WHEREAS, Bylaw 13.5 permits the Board to authorize officers to
enter into contracts and execute instruments on behalf of the
Foundation, generally or in specific instances; and
WHEREAS, officers have from time to time executed instruments
in the ordinary course of their assigned duties;
NOW, THEREFORE, BE IT RESOLVED, that the President, Executive
Vice President, Treasurer, Assistant Treasurer, Secretary,
Assistant Secretary, each Vice President charged with a
Foundation-wide function, and the Infrastructure Administrator
are authorized to execute and deliver contracts and other
instruments on behalf of the Foundation within the ordinary
course of that office, consistent with approved budgets and
Foundation policy; and be it further
RESOLVED, that a Vice President serving solely as chair of a
Project Management Committee has no such authority by that
office alone; and be it further
RESOLVED, that this authority does not extend to loans,
guarantees, real-property conveyances, or other extraordinary
transactions reserved to this Board; and be it further
RESOLVED, that instruments heretofore executed in good faith by
an officer within the apparent scope of that officer's duties
are ratified and confirmed as acts of the Foundation as of
their original dates, except for acts that were fraudulent or
in knowing violation of law or of a then-effective Board
resolution; and be it further
RESOLVED, that the President or Secretary may certify these
resolutions to third parties, who may rely on such
certification until the Board provides otherwise.
Special Order 8D, Officer Contracting Authority; Ratification of
Prior Instruments, was tabled.
9. Discussion Items
10. Review Outstanding Action Items
* Greg Stein: follow up about chair responsibilities
[ Flagon 2026-07-15 ]
Status:
* Greg Stein: pursue roll call
[ Geronimo 2026-04-15 ]
Status: attention is present, but so far it sounds like the
correct approach is "spin out components" rather than a
complete TLP move to the Attic. "spin out" to a new TLP
designated to support those? To Tomcat or TomEE or
Commons? ... still waiting on further feedback/roll-call
* Sander Striker: follow up about release candidate location
[ Gravitino 2026-06-17 ]
Status: Completed. https://lists.apache.org/list?dev@gravitino.apache.org:gte=0d:[vote]
* Shane Curcuru: Ask whether the Ignite 3 project is still a going concern,
and if not, when will users be notified?
[ Ignite 2026-08-19 (created by Justin Mclean) ]
Status:
* Christopher Schultz: reach out about communication issues
[ IoTDB 2026-06-17 ]
Status: Will reach-out to IOTDB in mid-July.
* Christopher Schultz: discuss failed roll call and future direction
[ Kylin 2026-05-20 ]
Status: https://lists.apache.org/thread/fzy0hjl46fmy2w8c6woljjq0co5zff4j
The PMC has sent invitations to some new committers and PMC members.
2026-09-15: One PMC member has been added
(https://lists.apache.org/thread/b2zb753ntshywl0ntd94s3lqcqcfyr3r).
One new committer has been invited, but I don't see an acceptance of that
invitation yet.
I'm still concerned about the project's ability to build its community, though
it is making slow progress.
I'm also concerned about the slow response to a number of security issues that
seems to be accumulating.
* Justin Mclean: Determine the board's position on whether security triage
and release management are "paying for development" under
the Targeted Sponsorship Policy, and report back.
[ Logging Services 2026-08-19 (created by Justin Mclean) ]
Status:
* Zili Chen: follow up about project viability
[ MADlib 2026-04-15 ]
Status: Follow up - https://lists.apache.org/thread/781rspl421vcmclzjdqlstzq8b5vgf4m
Seems MADlib didn't reply to Cloudberry's collaboration suggestion.
* Christopher Schultz: follow up about AI code usage
[ OpenDAL 2026-06-17 ]
Status:
* Greg Stein: talk to Pinot PMC about communication channels
[ Pinot 2025-11-19 ]
Status:
* Sander Striker: pursue a roll call
[ Rya 2026-07-15 ]
Status: Roll call initiated. Two swift responses. I do want to point out the comment
by @rbowen in https://agenda.apache.org/meetings/2026-01-21#rya as a reminder
in discussion.
* Justin Mclean: roll call
[ SDAP 2026-08-19 ]
Status: email sent
* Shane Curcuru: follow up about licensing
[ SIS 2026-02-18 ]
Status: Can be closed: this is a longer-term strategy issue that doesn't have a
current board solution.
* Shane Curcuru: message all PMCs to improve board reports and discuss
"Emeritus" concept for PMCs.
[ Superset 2026-05-20 ]
Status:
* Justin Mclean: Roll Call for Xalan
[ Xalan 2026-08-19 (created by Sander Striker) ]
Status: email sent
* Jean-Baptiste Onofré: follow up about Xerces-C EOL
[ Xerces 2026-06-17 ]
Status:
* Justin Mclean: Follow up with the Helix PMC. The 2.0.0 and 2.0.1 release
votes each had only two binding +1s from PMC members.
[ Helix 2026-09-16 (created by Justin Mclean) ]
Status: email sent
* Justin Mclean: Notice to the PMC that subprojects don't go to the attic
[ Axis 2026-09-16 (created by Justin Mclean) ]
Status: Done. email sent
* Jean-Baptiste Onofré: The 1.0.3 betas listed as releases haven't been
voted on
[ DevLake 2026-09-16 (created by Justin Mclean) ]
Status:
11. Unfinished Business
12. New Business
13. Announcements
14. Adjournment
Adjourned at 22:15 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period August 2026
* ISSUES FOR THE BOARD
The GLUTEN PMC is still not responding to trademarks@a.o. The PMC has
completely ignored a direction from the board on 21 August 2026 to provide an
update ASAP.
* OPERATIONS
Daan Hoogland continues to provide some very welcome assistance with trademark
issues.
Responded to the following queries, liaising with projects as required:
- provided advice to ATR on trademark text for web site footer
- provided advice to an external party looking to distribute software under
the downstream distribution policy
- provided guidance to former PMC members looking to fork LUCY from the attic
to provide some security fixes
- provided advice to an external party looking to use ASF project logos in
their product
- provided guidance to an external product on using the "ABC for Apache TLP"
naming style
- Approved name searches for COMET, SOURCELUME and ASYNCBAND
* REGISTRATIONS
Worked with counsel to maintain the APISIX registration in the US.
* INFRINGEMENTS
The issues with https://apisix.org have been resolved. The domain registration
lapsed so it has been purchased for a period of 5 years and configured to
redirect to the APISIX project page. Thanks due to Zili Chen who spotted that
the registration had expired.
At the request of the Airflow PMC I have submitted a formal trademark
compliant to GitHub regarding a trademark squatter.
Still no progress from the GLUTEN PMC to address a range of product naming
issues with multiple 3rd parties.
The SPARK PMC is working on a potential infringement.
The SPARK PMC is making progress in addressing a range of product naming
issues with multiple 3rd parties.
No further progress regarding the downstream vendor with multiple
infringements of ASF marks.
No progress regarding a website with potential infringements of KIE.
No updated on the opposition to a conflicting registration of FLINK in the EU.
No update from the XMLGRAPHICS PMC regarding progress of the complaint with
GitHub regarding a potential third-party infringement of FOP.
-----------------------------------------
Attachment 2: Report from the VP of Conferences [Brian Proffitt]
Evening events for the Glasgow conference are set. Keynote speakers (guests
and sponsored) are also ready and announced. Instead of swag giveaways, we are
organizing a book exchange for attendees. Anyone who has registered will
receive details on how to recommend a book for the book swap.
We are very excited to report that at the time of this report, 365 attendees
are registered for Glasgow.
The planning team has tentatively secured a venue for the 2027 North America
Community Over Code. A site visit is scheduled for September, 2026.
The CFP for the Community Over Code Sydney event, to be held November 18-19,
has closed, and session review is pretty much complete, so the schedule should
be out soon. The venue contract is signed, and now all we need to do is
arrange food and beverage.
-----------------------------------------
Attachment 3: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 4: Report from the VP of Diversity and Inclusion [Daniel Gruno]
Nothing major to report for this month,
Daniel Sahlberg was added to the initiative on Aug 7th 2026. The bulk of the
D&I folks will be at Community over Code in October, hoping to get a hold of
ideas for our first outreach campaign.
-----------------------------------------
Attachment 5: Report from the VP of ECMA Relations [Piotr Karwasz]
Work in all ECMA TC-54 task groups is continuing, with two draft
specifications scheduled for a TC-54 vote on Thursday before being forwarded
to the ECMA ExeCom:
- TG1 has released a draft of the Transparency Exchange API (TEA), a
format-agnostic protocol for exchanging supply-chain artefacts such as
SBOMs, VEX documents, attestations, and lifecycle events between publishers
and consumers: https://ecma-tc54.github.io/ECMA-xxx-TEA/
- TG2 has released a draft of the Version Range Specifier (VERS), a URI-based
syntax for expressing software version ranges, complementing PURL
(ECMA-427): https://ecma-tc54.github.io/ECMA-xxx-VERS/
-----------------------------------------
Attachment 6: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we onboarded no new Sponsors.
b —Renewals: we are processing renewals for one Platinum and one Bronze
Sponsor, and are discussing renewals with two Platinum, two Gold, three
Silver, and one Bronze Sponsor.
c —Payments: 1 —New: we received no new Sponsorship payments. 2 —Received: we
received payment from one Bronze Sponsorship renewal. 3 —Incoming: we await
renewal payments from one Platinum and one Silver ASF Sponsor, as well as one
Bronze Targeted Sponsor. One Gold Sponsor that was in extended arrears has
been removed from the Sponsorship program due to non-payment. 4 —Events: we
await payment from four Community Over Code sponsors.
2) Targeted Sponsors: we are discussing increasing donated services with two
Platinum Targeted Sponsors. We renewed a Targeted Platinum Sponsor for three
years with added Foundation-wide benefit. We are reviewing a potential new
Platinum Targeted Sponsor whose services would benefit the Responsible AI
Initiative, and met with an industry consortium whose activities may intersect
(collaboratively) with the ASF.
3) Sponsor Relations: we're connecting with new points-of-contact with several
Sponsors and are meeting to discuss renewals as well as track down outstanding
payments. We met with a Sponsor's new OSPO team to review sponsorship options
and possible upgrades. We also discussed promotion opportunities with a
Platinum sponsor.
4) Event Sponsorship: we are working with the Conferences and Treasury teams
on event sponsorship invoicing and payments.
5) Individual Donations and Corporate Giving: we received $1,600 in individual
online donations via https://donate.apache.org/ . We have not received any
online corporate contributions (above $500) during this timeframe.
6) Administrivia: our day-to-day activities with Accounting, Infrastructure,
Marketing & Publicity, and Conferences teams are ongoing and efficient. We
discussed agreements pertaining to a Targeted Sponsorship with Legal and
continue to coordinate with the ASF's Tooling and Responsible AI Initiatives'
teams.
-----------------------------------------
Attachment 7: Report from the VP of Infrastructure [Danny Angus]
General
-------
CI limitations remain one of the top Infra issues projects face under the
onslaught of AI based PRs, both security and otherwise. Infra continues to
increase CI provisioning where possible.
DKIM/Mail Delivery Problem Resolution
-------------------------------------
Infra has identified additional DKIM-related problems related to downstream
handling of DMARC policies. We are currently testing a workaround expected to
roll out fully by the end of September.
MFA Rollout
-----------
MFA soft rollout continues. Some users continue to report confusion with
enrollment, and Infra continues to try to improve the documentation.
Atlassian Cloud Migration Status
--------------------------------
Migration preparation continues, with only a few blockers remaining. Active
migrations are expected to begin before the end of calendar 2026.
Community News
--------------
The September Roundtable featured a walkthrough of the new Contingent Approval
Platform (CAP), which addresses the voting needs of ASF projects and other
bodies. This more than voting on releases (noted that Apache Trusted Releases
has its own structure for such votes): a project member can create a question
on any subject of interest to their project, and reliably record vote tallies.
From Infra's point of view, using CAP will simplify verifying and recording
that a request from a project represents the will of the project. CAP is in
early beta.
At Community Over Code Glasgow, in October, Infra will present a rich track of
talks and discussions, along with the popular Games Night. The October
Rountable will be an in-person event at the conference.
-----------------------------------------
Attachment 8: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Communications
* Completed and released annual report in late August, earlier than the past
few years. Thanks to all who collaborated on this document!
* Connected reporter with Log4j PMC regarding bug bounty decision
* Monitored Log4j vulnerability reporting
* Discussed communications strategy with Anthropic regarding blogs related to
the company’s donation and work with RAI
* Press releases
* Announced four new TLPs: Apache Fluss, Apache Pony Mail, Apache Iggy, and
Apache Sourcelume
* Announced FY26 annual report: ASF Advances Open Source Infrastructure and
Celebrates Community Growth in FY26
* Published blogs
* From Friction to Flow: How ASF Tooling Is Lowering Barriers for
Maintainers
* Apache Geode 2.0, Part III
* Issued August issue of Plus One newsletter
* Subscriber list now totals 5,263 (+433 new subscribers in August)
* Total sent: 4,800 | Unique opens: 910 | Open rate: 19%
Foundation Brand
* Updated Brand Guide with new registered trademark logos, including updated
usage guidance
Foundation Digital
* Restarted work to port Community Over Code archival events to the new
website including the most recent Asia event
* Created site for Community Over Code Sydney on the new website and promoted
the extended CFP
* Added sponsor logos to Community Over Code website
* Updated sponsor logos on the website including Circle.com, IBM
Social Media Overview
The highest-performing pieces of content for August include top-level project
announcements for Apache Fluss & Apache Pony Mail and Apache Iggy & Apache
Sourcelume, and the third part of the Apache Geode 2.0 post.
Social Highlights (X + Bluesky + Fosstodon + LinkedIn)
* Total Audience: 152,051
* X: 66,442
* Bluesky: 1,204
* Fosstodon: 233
* LinkedIn: 84,172
* Total Posts:
* X / Bluesky / Fosstodon / Bluesky: 70
* LinkedIn: 16
* Total Engagements: 7,506 (X 6,503 + LinkedIn 906; Bluesky 97)
Website Analytics
724,624 visits, 724,510 unique visitors -8.3%
1 min 59s average visit duration -18.5%
59% visits have bounced (left the website after one page) -1.7%
2.3 actions (page views, downloads, outlinks, internal site searches) per
visit +4.5%
1,266,326 pageviews, 947,860 unique pageviews -8.9%
52 total searches on your website, 13 unique keywords +225%
94,497 downloads, 67,213 unique downloads -7.6%
284,155 outlinks, 208,979 unique outlinks +4.5%
-----------------------------------------
Attachment 9: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
1) To everyone their surprise - the European Commission clarified via an FAQ
that the 11 September deadline for mandatory reporting does not apply to open
source stewards. Subsequently - documentation and instructions at ENISA, the
agency acting as a clearing house for the reporting, was also updated.
This FAQ has no real legal weight. And this clarification hinges on a very
narrow reading of a specific article in the CRA - as opposed to the general
intend of the articles (as is the usual approach in most EU legal systems).
However - especially given the fact that regulators and the rest of the system
is far from ready - the general consensus in the open source steward
communities (e.g. via the Open Regulatory Working Group that the ASF part of)
- is that, for now, we can rely on this.
We will however continue implementing the processes (low impact, most work
with @security, some with @infra) - so that we have them well established by
December next year. And can voluntary practice.
2) We've provided letters of support to several ASF members that applied for
positions in the EU Multi Stakeholder Platform (manages/guides the
rules/processes that create the standards define the technical standards that
are to be implemented as part of the law/normative-complinace) and the newly
fangled "Digital Commons European Digital Infrastructure Consortium (DC-EDIC)"
that is potentially defining for the future of open source in Europe.
3) It is ASF turn, with our President in the role as the local host, for the
Open Source Congress (Halifax, Canada, 22-23 September, with a stakeholder day
following)
-----------------------------------------
Attachment 10: Report from the VP of Tooling [Dave Fisher]
## Apache Trusted Releases
We have released and stood up the ATR Beta at the production url:
- https://releases.apache.org
This supports the full release process within the platform especially now
writes to `svn:dist:release`. SBOMs are encouraged. CI based and expedited
releases are available.
We have all of the release manager signing keys still found in the archives
and have matched these to all of the artifacts those keys have signed. PMCs
whould opt-in to ATR managing their KEYS files.
We have detected all of the actual "sub-projects" with releases from each
PMC. When we send out the beta announcement we will ask each PMC to check.
We are fixing a few small bugs and cleaning up our SBOM story.
- https://release-catalog.apache.org
We have a catalog every release found in the nearly 30 year history of ASF
releases from https://archive.apache.org.
The catalog includes support ECMA standards like:
- ECMA-424 CycloneDX Bill of materials specification
- ECMA-427 Package-URL (PURL) specification
- ECMA-428 Common Lifecycle Enumeration (CLE) specification
- https://lists.apache.org/list.html?releases@tooling.apache.org
This mailing list records releases identified by ATR as they are made.
ATR Releases since August 1, 2026
- Maven Plugin Tools 4.0.0-beta-3
- Maven Plugin Tools 3.16.0
- Maven Dependency Analyzer 1.17.2
- Maven Script Interpreter 1.8
- Maven Compiler Plugin 3.16.0
- Tooling ATR Maven Plugin 1.0.0-beta-1
- Maven Project Parent POMs 49
- Maven Resolver 2.0.22
- Cordova File Transfer Plugin 2.0.1
## Board Agenda Tool
Sander and Thomas have released a brand new look and feel. Additional progress
is made with minutes and deciding how to propagate changes to TLPs as they
happen during the Board Meeting
## Responsible AI Tooling
We succeeded in producing scans for over 75 PMCs. So far the vast majority of
the feedback is positive. Many PMCs have acted to triage the findings into
either a vulnerability to resolve or a hardening fix.
We started work with RAI to build out the tooling framework which we are
calling the Refractoru.
## Next Tooling Projects
Soon it will be time to start work on the next tooling initiative project.
There are two leading candidates: (a) Secretary's Workbench and (b) Roster
Tool. Both of these are components of Whimsy. I recommend (b) Roster Tool.
-----------------------------------------
Attachment 11: Report from the VP of Travel Assistance [Gavin McDonald]
Current Events
==============
Community Over Code - Glasgow
-----------------------------
The last three people awaiting Visa news were all denied. That still leaves a
healthy 21 recipients attending this year!
All flights are booked, Hotels booked, Conference tickets obtained.
Now we are planning for the event itself, letting recipients know what that
will be helping with during the event and other things like providing travel
tips , getting from the Airport to Hotel etc.
Community Over Code - Beijing
-----------------------------
TAC supported attendees at Community Over Code Asia 2026 in Beijing, August
7–9. Nine recipients were funded, covering travel, accommodation, and
conference fees. Feedback from recipients was positive, citing the value of
in-person contact with the wider Apache community and exposure to how users in
Asia are using our projects at scale. Willem Jiang and Chris Wells handled
arrangements on the ground.
Monthly Meetings
================
An in person TAC meeting will take place in Glasgow as many TAC Committee
members will be present.
Future Events
=============
Will begin to discuss having some people attend Fosdem.
TAC has agreed to provide budget for a welcome meal for students and TAC
members/volunteers for the Sydney C/C event in November.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support.
Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still
to be done. (One aim to to go through these with help in Glasgow.)
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Svante Schubert has joined the W3C Publishing Maintenance Working Group.
As a working group, it operates under the "Antitrust and competition policy"
which includes the W3C Patent Policy.
https://www.w3.org/policies/antitrust-2024/
This is the first participant from the ASF and the ASF has signed
the "Antitrust and competition policy".
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Justin Mclean]
August was a busy month on the public legal lists, with most of the traffic on
AI-related matters following the EU AI Act's transparency obligations coming
into force on 2 August. There are currently 2 open LEGAL JIRA issues. One new
issue was raised during August, and four have been closed since the last
report.
LEGAL-733 has been determined and closed: a three-line SPDX form covering
licence, copyright and contributor is accepted as an alternative to the
standard source header; a bare SPDX-License-Identifier line is not. The policy
page has been updated.
The generative tooling guidance was updated, and several new draft pages were
published under /legal/. The changes cover why ICLA Section 7 is not a
practical route for AI-generated material, the limits of establishing
reasonable certainty about similarity to training data, publishing
AI-generated content publicly under Article 50 of the EU AI Act, what belongs
in an AGENTS.md file, and how to check the terms of use of AI tools, with a
reviewed list of tools sorted into A/B/X categories. A proposal to make the
Generated-by record mandatory for AI-assisted contributions was discussed at
length; views were divided and no change has been made.
A review of ASF projects for exposure under the EU AI Act was posted to
legal-discuss, and the four projects most affected have been contacted
directly. The Incubator proposal template now asks three AI-related questions
of incoming projects. The Cyber Resilience Act's vulnerability and incident
reporting obligations for open source stewards start on 11 September; a note
went to Security and Infrastructure and a discussion was opened on
legal-discuss. Security has indicated it has been preparing.
OpenAtom asked the ASF to formally recognise its Chinese translation of the
Apache License. The licensing FAQ has said since 2002 that translations are
for convenience only and the English text is authoritative, and no translation
will be endorsed; I could find no record of the ASF ever having refused one.
OpenAtom has accepted the position. I intend to add a FAQ entry saying the ASF
endorses no translation and linking, without endorsement, to translations that
have had their publisher's own legal review.
The resolution to dissolve the Legal Affairs Committee and continue the office
of VP Legal was tabled in August, revised in light of feedback, and is on the
September agenda. The parallel Security resolution passed in August.
The three bylaws items noted last month remain under discussion.
Thanks to the board for appointing Zili Chen (tison) as Assistant VP Legal
Affairs last month.
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
August
* There is a stark increase in incoming reports again, not all of
which can be attributed to the LLM scans coming in.
* We've further improved the PMC security dashboard at
https://dash.security.apache.org and have announced it
on security-discuss
* We've upgraded the CVE preparation and publication tool
(cveprocess/vulnogram),
unlocking/simplifying further automation, initial support for Package URLs,
runs on updated infrastructure, and integrates with
https://dash.security.apache.org
* We've assisted Infra preparing for further improvements to the DKIM
infrastructure, which should ultimately improve email deliverability.
* There was some media attention for an invalid report against
Log4j. With the help of the Logging PMC, M&P and Sonatype we
were able to clarify the issue before it spread too widely.
* Scanning mentioned at
https://news.apache.org/foundation/entry/security-scanning-at-foundation-scale
* Security section and statistics published in Annual report
https://news.apache.org/foundation/entry/the-apache-software-foundation-advances-open-source-infrastructure-and-celebrates-community-growth-in-fy26
Stats for Aug 2026:
106 [reports held back pending batch sampling]
19 [license confusion]
11 [report/question relating to dependencies]
19 [support request/question not security notification]
Security reports: 1259 (last months: 750, 574, 739, 515, 386)
35 ['tomcat']
34 ['airflow']
31 ['ofbiz']
26 ['superset']
25 ['httpd', 'syncope']
24 ['apisix', 'dubbo']
23 ['kafka']
22 ['wicket']
21 ['openmeetings']
20 ['cxf', 'linkis']
19 ['shenyu']
18 ['commons', 'dolphinscheduler']
17 ['kyuubi', 'streampark']
16 ['camel', 'ranger']
15 ['cloudstack', 'hive', 'roller']
14 ['ambari', 'ozone']
13 ['amoro', 'doris', 'flink', 'logging', 'rocketmq', 'uniffle']
12 ['allura', 'nifi', 'streampipes']
11 ['directory', 'fineract', 'inlong', 'trafficserver']
10 ['artemis', 'brpc', 'iotdb', 'nuttx', 'solr', 'ws']
9 ['geaflow', 'kylin', 'openwhisk', 'uima'
8 ['infrastructure']
8 ['accumulo', 'answer', 'beam', 'caldera', 'cassandra',
'druid', 'geode', 'johnzon', 'jspwiki', 'shiro', 'spark']
7 ['airavata', 'bifromq', 'casbin', 'celeborn', 'karaf', 'livy',
'pegasus', 'qpid', 'servicecomb', 'struts', 'texera',
'zeppelin']
6 ['activemq', 'arrow', 'atlas', 'eventmesh', 'hbase',
'hugegraph', 'knox', 'pdfbox', 'pulsar', 'storm', 'thrift']
5 ['calcite', 'ignite', 'jackrabbit', 'kvrocks', 'olingo',
'pinot', 'plc4x', 'seatunnel', 'skywalking', 'tez']
4 ['devlake', 'fluss', 'gravitino', 'hop', 'hudi', 'james',
'manifoldcf', 'openoffice', 'paimon', 'seata', 'sis',
'stormcrawler', 'unomi', 'xmlgraphics']
3 ['age', 'bookkeeper', 'couchdb', 'drill', 'hadoop',
'httpcomponents', 'iceberg', 'jena', 'jmeter', 'mina',
'parquet', 'sedona', 'shardingsphere', 'zookeeper']
2 ['ant', 'avro', 'baremaps', 'bigtop', 'celix', 'guacamole',
'helix', 'maven', 'opendal', 'ozhera', 'pekko', 'phoenix',
'polaris', 'resilientdb', 'samza', 'sling', 'synapse',
'tapestry', 'tinkerpop', 'tomee', 'tsfile', 'tvm', 'vcl',
'velocity', 'wayang']
1 ['apr', 'asterixdb', 'brooklyn', 'buildstream', 'carbondata',
'causeway', 'cloudberry', 'cocoon', 'curator', 'db', 'fory',
'freemarker', 'gluten', 'grails', 'hertzbeat', 'iggy',
'jclouds', 'juneau', 'kie', 'myfaces', 'mynewt', 'nutch',
'opennlp', 'orc', 'poi', 'ponymail', 'pouchdb', 'ratis',
'spamassassin', 'submarine', 'subversion', 'systemds',
'teaclave', 'tika', 'torque', 'turbine', 'yunikorn']
In total, as of 1st September 2026, we're tracking 2356 (last months: 1574,
1314, 1139, 856) open issues across 203 projects, median age 43 days
(last months: 63, 54, 51). 450 of those issues have CVE names
assigned. 44 (last months: 48, 29) of these issues, across 20
projects, are older than 365 days.
* openoffice (Health red): Several issues in OpenOffice are over 365
days old. They are not severe enough to warrant stopping
distribution of OpenOffice. (Last update: 2026-07-01)
* apr (Health amber): releases are few and far-between (Last update:
2026-06-29)
* spark (Health amber): the project has a backlog of security reports
to be triaged (Last update: 2026-05-06)
* superset (Health amber): while the project is actively publishing
fixes to security issues each release, there is concern about a
growing backlog. (Last update: 2026-07-01)
-----------------------------------------
Attachment 15: Report from the VP of Responsible AI [Jeff Genender]
**Description**
The ASF Responsible AI Initiative (RAI) is a program to support the open
source technologies that underpin modern artificial intelligence, and to help
Apache communities adopt AI in a way that is open, transparent, and aligned
with the ASF's values. The initiative is grounded in the ASF's guidelines for
the responsible use of AI — human oversight, licensing integrity, security,
and documentation — core principles rooted in the Foundation's longstanding
philosophy of community over code.
To fulfill its charter, the RAI is undertaking efforts to facilitate:
1. Access to AI models and tooling
2. Ecosystem support for Projects
3. Community engagement and outreach
**Status**
- Auto-deployment of cloud GPU instances is progressing well. This capability
is being integrated into our system to manage donated credits, budgeted
token allocations, and inference services for Foundation communities.
- Consulted with the Treasurer on accounting processes and completed Ramp
setup in accordance with the approved budget.
- Met with two candidate sponsors to explore potential donations that would
expand access to additional AI tools.
- Met with RAI backers to align on future donated services.
- Began developing a set of Best Practice recommendations.
- Submitted candidate logos to Marketing & Publicity (M&P) to finalize the RAI
logo and ensure brand-usage compliance.
- Sourcelume has been successfully bootstrapped with initial infrastructure
(email lists, website, and repositories) and will now handle its own
reporting going forward. We are supportive of their progress and will
continue to assist as needed.
- Organizing a RAI Hackathon and Birds-of-a-Feather (BOF) panel for Community
Over Code Glasgow.
- Drafting the RAI work plan for the Refractory Platform Project. The
Refractory is an internal holistic Project to specify a managed AI platform
providing governance, metering, and budgeting for donated funds, compute
time, and inference tokens. Describes the tooling and services to enable
projects to take advantage of self-serve security scans and other workloads,
and to have access to models and agents.
- Distributed a survey on AI usage to Project Management Committees (PMCs).
- Completed security scans across more than 230 repositories, resulting in
CVEs and other hardening measures that are already complete or underway
https://news.apache.org/foundation/entry/security-scanning-at-foundation-scale
- Created a public email list at general@rai.apache.org
- Currently speaking to a law firm based out of DC that specializes in
technical/IP law on a pro bono basis to review agreements, best practices,
as well as other areas of legal interest.
**Upcoming**
Will be gathering the survey information to detemine project needs with AI and
begin forming information for AI usage and provide the begining of planning to
support the needs as well as solidifying Best Practices.
-----------------------------------------
Attachment A: Report from the Apache AGE Project [Jeff Jirsa]
## Description:
The mission of Apache AGE is the creation and maintenance of software related
to a multi-model database that enables graph and relational models built on
PostgreSQL
## Project Status:
Current project status: Active. Acceptable governance, but low activity.
Issues for the board: The AGE PMC has elected a new chair. A resolution has
been submitted to change the chair in the September 2026 board meeting.
## Membership Data:
Apache AGE was founded 2022-05-17 (4 years ago)
There are currently 20 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jeff Jirsa on 2025-05-11.
- Greg Felice was added as committer on 2026-06-05
## Project Activity:
Commits, reviews, and releases continue as before. Total activity is stable.
Recent releases:
PG18-1.8.0 was released on 2026-08-06.
PG17-1.7.0 was released on 2026-03-06.
PG18-1.7.0 was released on 2026-02-04.
## Community Health:
Identification of new committers remains slow, as true organic, repeat
contributors are rare, where fly-by AI contributions are more common.
-----------------------------------------
Attachment B: Report from the Apache Airavata Project [Suresh Marru]
-----------------------------------------
Attachment C: Report from the Apache Airflow Project [Bolke de Bruin]
-----------------------------------------
Attachment D: 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:
- released versions 1.19.1, 1.20.0, and 1.21.0 because of vulnerabilities
reported and fixed
- continued field-level encryption of some fields
- package updates, other changes
## Community Health:
- we've been receiving a lot of security vulnerability reports in the past few
months.
- development is slow, mostly in maintenance mode, but "active maintenance"
keeping up with new versions of things and improving security posture
-----------------------------------------
Attachment E: Report from the Apache Ambari Project [Brahma Reddy Battula]
-----------------------------------------
Attachment F: Report from the Apache Atlas Project [Madhanmohan Neethiraj]
-----------------------------------------
Attachment G: 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 (17 years ago)
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.1 was released on May 17, 2026.
- Axis 2/Rampart 1.8.0 was released on Dec 10, 2024.
- Axis 2/C 2.0.0 was released on April 26, 2026.
- Axis 1.4 was last released in 2006.
## Community Health:
Now that both Axis2/Java and Axis2/C have been modernized to support
contemporary features such as HTTP/2, JSON and MCP we can now focus
on promotion in general to attract new committers.
Axis2/C supports Android that includes sample projects using cameras
and audio capture with phones acting as servers doing verbs like
start / stop / sftp, among others, using Apache httpd and
mod_axis2. There is little competition in the area and is the
largest area for potetial growth.
Axis2/Java competes with frameworks such as Spring so growth is
expected to be modest and targeting REST with JSON users who
need advanced features such as advanced HTTP/2 support, MCP,
pagination, and field selection filtering for return messages.
An Axis2/Java 2.0.2 release is imminent and is largely a patch release.
The Axis2 wikipedia page has started some edits, with more on the way
as we work through the learning curve on the Talk page.
Some cleanup for the upcoming quarter includes sending these projects
to the attic: Axis 1, Sandesha2, Kandula.
-----------------------------------------
Attachment H: 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.76.0 was released on 2026-08-31.
- 2.75.0 was released on 2026-07-08.
Beam Summit:
- took place just after last report, in June
- 29 sessions, most of which are now available at
https://beamsummit.org/sessions/2026/
Notable design threads on dev list:
- Delta Lake CDC
[https://lists.apache.org/thread/c2f2qnboft22vzo1lp8opdyvs1goyoj8]
- Model monitoring
[https://lists.apache.org/thread/qbltpy4b369pqko3zjy5pc3sylpv2q3y]
- Improving Bundle Isolation so stragglers don't hold up work
[https://lists.apache.org/thread/ghbqgwt0hr3qtx0wlffh1qxj1xpt8zk8]
- FlareDB - a Beam-native streaming database / portable runner in Rust
[https://lists.apache.org/thread/wt4thbpys3341h25qmj98vqvonpzfm1z]
- Multi-stage builds for Beam Python Debian containers for smaller images,
faster worker startup
[https://lists.apache.org/thread/js767751x753d67vrzg2qk7k5pd1rqvq]
- Portable Kafka Streams Runner (a GSoC project)
[https://lists.apache.org/thread/yql98lyh2k8nqy6z6mryo4zph7z1lztm]
- Portable Beam transforms (these already exist as requested, but are not
widely advertised
[https://lists.apache.org/thread/mwhkofr96fmkl1g3o7plrz008wf4wkwh]
## Community Health:
There are a lot of good design discussions. The dev list is still a place
where people share their ideas and comment on others. However, some newcomer
emails are not getting attention. There is also a large proportion of traffic
that are automated which reduces the motivation to seriously follow dev@.
These issues seems like typical open source mailing list stuff, not cause for
any concern.
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Masatake Iwasaki]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around
the packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is
to Linux.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Bigtop was founded 2012-09-19 (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:
* 3.6.0 was released on 2026-08-14
* 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 addressed upgrading Hadoop to 3.4 in Bigtop 3.6.0. We are going to upgrade
Hadoop to 3.5 on the next Bigtop 3.7.0. It will affect toolchain and
downstream products a lot since Hadoop 3.5 bumped the minimum Java version
to 17.
We are looking into 2 vulnerability reports mentioning bigtop-manager.
## Community Health:
* dev@bigtop.apache.org had a 1% increase in traffic in the past quarter (81
emails compared to 80)
* issues@bigtop.apache.org had a 26% increase in traffic in the past quarter
(43 emails compared to 34)
-----------------------------------------
Attachment J: Report from the Apache BookKeeper Project [Enrico Olivelli]
-----------------------------------------
Attachment K: Report from the Apache BuildStream Project [Abderrahim Kitouni]
-----------------------------------------
Attachment L: Report from the Apache BVal Project [Matt Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache BVal was founded 2012-02-14 (15 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:
Some work has been undertaken in the direction of implementing
forthcoming changes to the Java Bean Validation specification.
Customary housekeeping in the form of dependency version chasing
continues as well.
## Community Health:
As usual we are largely dormant but the current activity is demonstrative of
the fact, on which we perennially insist, that our community engagement is
sufficient to effectively maintain the project, patch bugs, and sync with
upstream spec changes.
-----------------------------------------
Attachment M: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.
## Project Status:
Current project status: Ongoing with high activity Issues for the board:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Camel was founded 2008-12-17 (18 years ago)
There are currently 96 committers and 49 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 Aurélien Pupier on 2026-05-11.
- Adriano Machado was added as committer on 2026-06-24
## Project Activity:
Feedback on the previous report:
- We were asked which Zulip we meant and whether all important things are
brought back to the mailing list. The Zulip we use is
https://camel.zulipchat.com. It is an instance of Zulip, the open-source
threaded chat application (the server is Apache-2.0 licensed); zulip.com
is the vendor that hosts the instance for us. It is not Slack, although
the two are superficially similar. Anyone can create an account and join
without an invitation, but the content is not readable anonymously, so we
do not treat Zulip as a project record. Project decisions are made and
recorded on the mailing lists. In this quarter, every release vote, vote
result and release announcement, the roadmap discussion about promoting
4.22.x to LTS and ending support for 4.14.x, all 39 security advisories,
the monthly static code analysis report and related went through
dev@camel.apache.org, with private@camel.apache.org used only where the
ASF process requires it. Zulip is used for user support and quick informal
questions, and when a thread there turns into a design discussion or a
decision we move it to dev@ or to Jira. We will keep reinforcing that
expectation with the community.
- We were asked us to provide a one sentence description of each release
artifact, noting that a name such as "Apache Camel Quarkus" is unclear to
the average reader. We have added a short description to every sub-project
in the Project Activity section below, and we will keep doing so in future
reports.
Security: This quarter the PMC completed and disclosed the results of a
large, systematic security audit of the component set. 39 CVEs were
published in July and August 2026, in the following classes:
- Header injection (24 CVEs): components that mapped externally supplied
message metadata into the Camel Exchange without a HeaderFilterStrategy,
or that used Exchange header constants without the Camel prefix and
therefore bypassed the upstream HTTP header filter. This allowed an
untrusted client to override routing or operation headers. Affected
components included camel-cxf, camel-solr, camel-kafka, camel-salesforce,
camel-jira, camel-dns, camel-mongodb-gridfs, camel-nats, camel-aws2-sqs,
camel-cometd, camel-elasticsearch-rest-client, camel-vertx-websocket,
camel-atmosphere-websocket, camel-knative and others.
- Unsafe Java deserialization (5 CVEs): paths reading untrusted payloads
through ObjectInputStream with no JEP-290 ObjectInputFilter
(camel-hazelcast, camel-pqc, camel-jms), plus a hardening of Camel's own
default filter pattern.
- Path traversal (3 CVEs): cloud storage download operations that built the
local target path from the remote object name without constraining it to
the configured directory (camel-azure-storage-blob,
camel-azure-storage-datalake, camel-google-storage).
- Authentication and authorization (3 CVEs): token validation gaps in
camel-keycloak and in the platform-http-main JWT mechanism.
- Information disclosure (2 CVEs): HTTP consumers returning full Java stack
traces in the response body because muteException defaulted to false
(camel-netty-http, camel-undertow).
- Injection into back-end queries (2 CVEs): Cypher injection in camel-neo4j
and JavaMail session property override in camel-mail.
Every one of them was remediated across all supported release lines,
shipping in 4.14.9, 4.18.4 and 4.22.0. Beyond the individual fixes, the
audit drove systematic hardening that is not tied to a single CVE: JEP-290
deserialization filters are now applied by default on Camel's shared object
input stream and on camel-spring-redis, the remote file consumers (FTP,
SFTP, FTPS, SMB, azure-files) now jail resolved paths inside the polled
directory, and a project-wide sweep renamed non-prefixed header constants so
that they are covered by the header filter strategies.
The process worked as intended: all reports were handled privately through
security@apache.org and the ASF process, fixes were prepared and released
across every supported line, and the advisories were published only after
the releases were available. The volume reflects the depth of the audit
rather than a degradation of the codebase, and we consider this a sign of a
healthy and functioning security process.
Apache Camel: Apache Camel is the core project: a Java integration framework
and runtime that routes, transforms and mediates messages between systems
using Enterprise Integration Patterns, shipping more than 350 ready-made
connectors to external systems. It is released as a set of Maven libraries
plus a command line tool.
- We released Camel 4.21.0
- We released Camel 4.14.8 (LTS)
- We released Camel 4.18.3 (LTS)
- We released Camel 4.22.0 (LTS)
- We released Camel 4.14.9 (LTS)
- We released Camel 4.18.4 (LTS)
- Note: Camel releases have synchronized releases of Camel-Spring-Boot too
for 4.x. Camel Spring Boot packages Camel to run on the Spring Boot
runtime and provides a Spring Boot starter for each Camel component.
- Camel 4.22.0 is our new LTS release train. The 4.14.x LTS train reached
end of support on 2026-08-20 as announced, with 4.14.9 as its final
release. Our active LTS trains are now 4.18.x and 4.22.x.
- In 4.22.0 the Camel CLI (Camel JBang), the Camel TUI and the Camel MCP
Server were all promoted from Preview to Stable support level. The TUI
also gained a switchable light/dark theme and a settings panel.
- AI-related work continued at a good pace: new camel-ai-tool and embeddable
camel-mcp-server components, a camel-a2a component implementing the
Agent2Agent protocol, and the start of an AI observability module. The CLI
AI prompt now auto-detects Azure OpenAI and supports Google Gemini
natively.
- New components shipped in 4.21.0 and 4.22.0: camel-shell, camel-a2a,
camel-ai-tool, camel-mcp-server, camel-clickhouse, camel-duckdb,
camel-jactl and camel-dataweave.
- The camel-api module now ships optional JSpecify null-safety annotations,
so applications and tooling can do compile-time null checking against the
Camel API.
- Post-quantum readiness improved: more components can now be configured
through SSLContextParameters, which allows selecting post-quantum named
groups such as X25519MLKEM768 on JDK 25+.
- Development of 4.23.0 is well underway, with a new camel-alibaba component
family (9 modules), camel-spiffe, a camel-state-store family,
camel-python3, camel-quickjs, camel-toon, camel-ubl, camel-rest-postman
and camel-hivemq. It also removes a set of long-deprecated modules whose
upstream libraries are unmaintained (camel-csimple, camel-irc,
camel-ironmq, camel-iec60870, camel-digitalocean, camel-headersmap,
camel-json-patch and camel-langchain4j-tools).
- Java 25 compatibility work is ongoing.
- The situation is really healthy and the community keeps increasing its
presence and engagement.
Apache Camel K: Apache Camel K is a Kubernetes operator that takes a Camel
route file and builds, containerises and deploys it as a native Kubernetes
workload, so an integration can be run on a cluster without the user
assembling an application or a container image by hand.
- No release was cut during this quarter. Camel K 2.11.0, 2.10.2 and 2.9.3
are currently under vote and we expect them to be released shortly.
- Camel K 2.11.0 deprecates the IntegrationPlatform API as part of an
ongoing simplification of the operator API surface, and continues the
controller cleanup.
- The operator keeps tracking recent Golang and Kubernetes API versions.
- Camel K is in good shape and the community keeps growing with more
contributors and feedback. The situation is healthy.
Apache Camel Kamelets: Apache Camel Kamelets is a catalog of reusable,
parameterised route templates written in YAML, which let a user connect to
an external system such as a queue, a database or a SaaS API by supplying a
handful of properties instead of writing a route. The catalog is consumed by
Camel core, Camel K, Karavan and Camel Kafka Connector.
- We released Camel Kamelets 4.21.0
- We released Camel Kamelets 4.18.3
- We released Camel Kamelets 4.22.0
- The Kamelet catalog keeps growing and is now at 254 Kamelets.
- Documentation has been improved even more.
- The 4.18.x and 4.22.x release trains are matching the LTS releases from
Camel core.
Apache Camel Quarkus: Apache Camel Quarkus is the set of extensions that
make the Camel components run on the Quarkus runtime, including
ahead-of-time compilation to a GraalVM native executable for fast startup
and low memory footprint. It has its own release train because it has to
track both Camel and Quarkus versions.
- The Camel-Quarkus work is going ahead following the main camel releases
with multiple releases.
- We released Camel-Quarkus 3.27.5 (Camel 4.14.8 LTS)
- We released Camel-Quarkus 3.33.2 (Camel 4.18.3 LTS)
- We released Camel-Quarkus 3.38.0 (Camel 4.21.0)
- We released Camel-Quarkus 3.39.0 (Camel 4.22.0 LTS)
- We are increasing the number of Camel Quarkus Extensions to match the core
components and we are now at 277 extensions. We are supporting 4.18.x LTS
and 4.22.x LTS, and we shipped the final 4.14.x LTS alignment before that
train went end of support.
- The community is active and we are seeing increased interest.
Apache Camel-Karavan: Apache Camel Karavan is a low-code visual designer for
Camel integrations, shipped as a web application and as a Visual Studio Code
extension, which lets users build, run and deploy routes graphically instead
of writing them by hand.
- No release was cut during this quarter. The last release was 4.18.0 in the
previous quarter.
- Development continued steadily and a new release is currently being
prepared.
- Work in this period focused on the Kubernetes service layer, the
properties panel and dependency updates across the VS Code extension.
Camel-Kafka-Connector: Camel Kafka Connector exposes every Camel component
as an Apache Kafka Connect source or sink connector, so Kafka users can move
data in and out of any Camel-supported system through Kafka Connect
configuration alone, without writing code.
- No release was cut during this quarter. The last releases were
Camel-Kafka-Connector 4.18.0 and 4.14.5 in the previous quarter.
- Development continued at a lower pace, focused on maintenance and on
keeping the connector catalog aligned with the Kamelets catalog.
- We plan to align the project with the new 4.22.x LTS train.
Apache Camel-Karaf: Apache Camel Karaf provides the OSGi packaging and the
Karaf features needed to run Camel inside the Apache Karaf container.
- No release was cut during this quarter. Camel-Karaf 4.14.7 and 4.18.2 were
both released just before the start of this reporting period.
- We keep supporting the 4.18.x LTS train and we will align to 4.22.x LTS.
Apache Camel-Upgrade-Recipes: Apache Camel Upgrade Recipes is a set of
OpenRewrite recipes that automatically rewrite user source code when
migrating between Camel versions, removing much of the manual work of an
upgrade.
- Camel-Upgrade-Recipes 4.21.0 has been released
- Camel-Upgrade-Recipes 4.22.0 has been released
- This version supports upgrades up to 4.22.0.
- The plan is to keep supporting 4.18.x LTS and 4.22.x LTS.
## Community Health:
Dev and issues mailing lists remained active this quarter. The dev list
carried the usual release votes plus the discussion around promoting the
Camel CLI, TUI and MCP Server to Stable, the security disclosures, etc. The
issues list saw a very large increase in traffic, going from roughly 1,200
messages in June to 2,661 in July and 1,619 in August, driven by the
security audit work and by the volume of contributions. The users mailing
list remains lower in volume, mainly because we are using Zulip for
discussions and contributors often use Zulip as their first interaction
point instead of the mailing list.
In terms of GitHub engagement we are doing really well. On the core
repository we had 78 unique human contributors this quarter, with roughly
3,240 commits across all branches (about 2,500 excluding automated
dependency and CI bots) and 2,295 pull requests merged. On Jira we had 964
issues created and 1,015 issues resolved in the same period, so we are
closing more than we open and the backlog is shrinking. The project has
6,300+ stars and 5,100+ forks on GitHub.
We also introduced a monthly static code analysis report on the dev list,
which gives the community a recurring view of code quality trends and has
already led to a number of clean-up contributions.
Overall the community is growing, the pace of releases and the successful
delivery of a new LTS train this quarter demonstrate the project's vitality,
and the way the security audit was handled shows the processes around the
project are working well.
-----------------------------------------
Attachment N: Report from the Apache Cayenne Project [Michael Gentry]
# Apache Cayenne Board Report, September 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 (20 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.
5.0 Milestone 2 and 5.0 Milestone 3 were released during the past quarter.
- 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.
- Cayenne 5.0.M2 on 2026-07-06.
- Cayenne 5.0.M3 on 2026-08-27.
## Community Health
Cayenne is healthy.
Development mailing list traffic was up due to 5.0 Milestone 2 and
Milestone 3 preparations and discussions.
User mailing list traffic was down, but still active and questions
continue to be answered in a timely manner.
Jira/Git activity was up due to the Milestone releases with
59 JIRA tickets opened and 73 closed in the past quarter.
-----------------------------------------
Attachment O: Report from the Apache Celeborn Project [Keyong Zhou]
-----------------------------------------
Attachment P: Report from the Apache CloudStack Project [Wido den Hollander]
## Description:
The mission of CloudStack is the creation and maintenance of software related
to Infrastructure as a Service solution
## Project Status:
Current project status: Healthy community with active committers and users
Issues for the board: None
## Membership Data:
Apache CloudStack was founded 2013-03-20 (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-27.
- No new committers. Last addition was Rositsa Kyuchukova on 2026-03-11.
Active VOTE threads on the mailinglists to add new committers
and PMC members.
## Project Activity:
### Security
The project is active and receiving pull requests from
existing committers and new users to the project.
At the same time the project is seeing an increased amount
of security reports which are sometimes difficult to handle
by the project due to the amount of reports being filed.
Reports need to be manually verified, fixes written and tested.
This is putting strain on the developers.
Active discussions are ongoing on how to address this.
### Releases
- Versions 4.22.1.1 and 4.20.3.1 were released in August 2026
- Version 4.23 was released on September 2nd 2026.
The project has deciced to drop the "4." as a prefix and
therefor the next release will be 24.0.0
## Community Health:
Commiters, users and others are active.
The project is preparing for the collaboration conference
on 20-21 November 2026 in Edinburgh.
-----------------------------------------
Attachment Q: 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:
We've started to process Glasswing/Mythos reports: BCEL and LANG have been
processed and are readying releases. This will be followed by the allocation
of many CVEs.
We have a new component: Apache Commons Secure XML.
In this reporting period, we've released the following components:
- PARENT-105 was released on 2026-09-07.
- SECUREXML-1.0.0 was released on 2026-09-06.
- SKIN-5.3.0 was released on 2026-09-01.
- PARENT-104 was released on 2026-08-22.
- COLLECTIONS-4.6.0 was released on 2026-08-10.
- VALIDATOR-1.11.0 was released on 2026-07-31.
- CODEC-1.22.1 was released on 2026-07-30.
- PARENT-103 was released on 2026-07-21.
- JEXL-3.7.0 was released on 2026-07-02.
- JEXL-3.6.4 was released on 2026-06-28.
- JEXL-3.6.3 was released on 2026-06-23.
- LOGGING-1.4.0 was released on 2026-06-17.
- DAEMON-1.6.1 was released on 2026-06-11.
- PARENT-102 was released on 2026-06-11.
- BCEL 6.13.0 is currently a release candidate.
## Community Health:
We've seen a near doubling of issue activity. There is also lively and
constant stream of pull requests on GitHub. Folks have really taken on to
using AI. The mailing list traffic on the other hand has decreased in traffic
by half. It's quite likely that pull requests on GitHub and Jira tickets is
where the activity has shifted towards.
-----------------------------------------
Attachment R: Report from the Apache Cordova Project [Bryan Ellis]
## Status report for the Apache Cordova project - Sept 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 fixes and
improvements to our core platforms and plugins.
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-file-transfer@2.0.1 was released on 2026-08-10.
- cordova-android@15.1.0 was released on 2026-07-22.
- cordova-ios@8.1.1 was released on 2026-07-07.
- cordova-plugin-inappbrowser@7.0.0 was released on 2026-06-22.
## Community Health
Overall, the community health is strong. The ASF Project Statistics gives the
project a Community Health Score (Chi): 4.70 (Healthy)
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.
This quarter, we primarily focused on improving some plugins and platforms.
A large portion of this quarter's activity was focused on improving the In-App
Browser plugin, as well as fixing the status bar and edge-to-edge
functionality of the Android core platform. There is still on going
improvements toward the status bar functionality to be more inlined with the
behavior of the iOS core platform. There were contributions that landed in a
patch release for the iOS core platform and file transfer plugin.
We are also updating the repository's Dependabot configuration to include
GitHub Actions dependencies, so that our workflows remain up-to-date.
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 13% increase in traffic in the past quarter (78
emails compared to 69):
- issues@cordova.apache.org had a 19% increase in traffic in the past quarter
(1640 emails compared to 1371):
-----------------------------------------
Attachment S: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Apache CouchDB software is a document-oriented database that can be queried and
indexed in a MapReduce fashion using JavaScript. CouchDB also offers
incremental replication with bi-directional conflict detection and resolution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache CouchDB was founded 2008-11-19 (18 years ago)
There are currently 74 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Glynn Bird on 2023-03-14.
- No new committers. Last addition was James Coglan on 2026-03-24.
## Project Activity:
- Continued work on next feature and bugfix releases.
- Nano sub-project (Node.js client library) plans major new releases
to achieve a no-dependencies situation for improved supply-chain
security. Current stable release will be supported for 12 more
months after the new release comes out. No API changes expected.
## Community Health:
- slower as-per northern-hemisphere summer time activities across the
board, but still continued stream of contributions, issues etc.
-----------------------------------------
Attachment T: Report from the Apache cTAKES Project [Pei J Chen]
## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache cTAKES was founded 2013-03-19 (13 years ago)
There are currently 40 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Dennis Johns on 2026-03-10.
- No new committers. Last addition was Dennis Johns on 2023-01-06.
## Project Activity:
- Committee continues to work on the future release (7.x.x)
- 6.0.0 was released on Sept 16 2024
- 5.1.0 was released on May 10 2024
- 4.0.0.1 was released on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
## Community Health:
dev@ctakes.apache.org had a 67% decrease in traffic in the past quarter
(1 emails compared to 3)
Summertime has been historically quiet.
-----------------------------------------
Attachment U: Report from the Apache Curator Project [Enrico Olivelli]
-----------------------------------------
Attachment V: 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.5 years ago)
There are currently 23 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- Larry Barber was added to the PMC on 2026-06-21
## Project Activity:
- Daffodil 4.2.0 was released on 2026-07-07
- Daffodil SBT Plugin 1.8.0 was released on 2026-07-07
- Daffodil and Daffodil SBT plugin have an expected release 2026-11
## 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. There are approximately a dozen core active contributors across
the main Daffodil library and Daffodil VS Code projects.
- 14 JIRA tickets opened and 12 closed
- 11 GitHub issues opened and 24 closed
- 50 pull requests created and 45 merged/closed
-----------------------------------------
Attachment W: Report from the Apache DataFusion Project [Andrew Lamb]
## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine
## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache DataFusion was founded 2024-04-16 (2 years ago)
There are currently 61 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- Matt Butrovich was added to the PMC on 2026-06-15
- Qi Zhu was added to the PMC on 2026-08-04
- Adam Gutglick was added as committer on 2026-07-20
- Manu Zhang was added as committer on 2026-08-20
- Neil Conway was added as committer on 2026-06-14
## 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
55.0.0 was released on 2026-08-18.
54.1.0 was released on 2026-07-18.
54.0.0 was released on 2026-06-08.
Our releases now consist of contributions from over 170 distinct contributors
(was 120), and we average around [11.2 commits per day] to the main repo (up
from [9.2 commits per day])
[11.2 commits per day]: git rev-list \
--count apache/main --since='2026-06-09 00:00:00' \
--until='2026-09-08
23:59:59'
[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'
The community continues to write blogs highlighting our work, see
https://datafusion.apache.org/blog/
Likewise we continue to hold in person meetups as community members have
bandwidth to organize them, see:
https://datafusion.apache.org/user-guide/concepts-readings-events.html#community-events
We have been discussing the best process and setup to help maintain the Apache
Iceberg’s Rust Implementation’s DataFusion Integration. The communities are
working together to find a consensus solution. See the [mailing list topic]
for more details
[mailing list topic]:
https://lists.apache.org/thread/53lqjw7371myww42l19vx923cjzrgg68
### Sub project: DataFusion Python
https://github.com/apache/datafusion-python
DATAFUSION-PYTHON-54.0.0 was
released on 2026-06-29.
### Sub project: DataFusion Java
https://github.com/apache/datafusion-java
There has been very little activity this quarter, since this is a new
subproject (created in the previous quarter) and is not widely known about or
adopted yet.
### Sub project: DataFusion Comet
https://github.com/apache/datafusion-comet
COMET-1.0.0 was released on
2026-08-07. COMET-0.17.1 was released on 2026-07-17. COMET-0.17.0 was released
on 2026-06-20.
Comet reached its 1.0.0 milestone this quarter. You can read about the recent
happenings in Comet in the release blogs:
https://datafusion.apache.org/blog/2026/08/07/datafusion-comet-1.0.0
https://datafusion.apache.org/blog/2026/06/20/datafusion-comet-0.17.0
The community also published a post about their experience running Spark
workloads with Comet on Amazon EKS:
https://datafusion.apache.org/blog/2026/06/03/comet-eks
There is a discussion about promoting Comet to a top level ASF project:
https://github.com/apache/datafusion-comet/issues/5184
### Sub project: DataFusion Ballista
https://github.com/apache/datafusion-ballista BALLISTA-54.1.0 was released on
2026-08-09. BALLISTA-54.0.0 was released on 2026-07-15.
Release blog posts: Apache DataFusion Ballista 54.0.0 Released Apache
DataFusion Ballista 54.1.0 Released
Ballista has seen an increase in activity in this quarter, with 13 first time
contributors, and a 64% increase in merged PRs as of 8/27 (366 PRs merged vs
223 in previous quarter).
Active areas of work include: Adaptive Query Execution (AQE): AQE is now
enabled by default, with dynamic join selection, and broadcast joins.
Stability: New HA chaos harness, improvements to recovery from executor loss.
TPC-H and TPC-DS are now tested in CI to avoid regressions Performance:
Shuffle implementation improved, order-preserving range partitioning, KLL
sketches for runtime stats. Multi-partition tasks, parallel window functions
Usability: Upgrade guide, generated configuration docs, improved kubernetes
support & documentation
### Sub project: sqlparser-rs
https://github.com/apache/datafusion-sqlparser-rs
There were no new sqlparser-rs releases this quarter (SQLPARSER-0.62.0 was
released on 2026-05-27). We plan the next one in September 2026.
We are actively working to help Ifeanyi Ubah (iffyio), the primary maintainer,
to identify additional community members who can help maintain the project.
## Community Health:
The rise of AI coding tools, and the popularity of DataFusion in the ecosystem
means we are moving code faster than ever before. Our code review capacity is
never enough, but 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 and the future looks bright.
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. Recently, we have had some bursts
of spam PRs, where multiple PRs are opened by new contributors in a short
amount of time, with no follow up on any PR feedback. We have been discussing
if a new "Policy on uptick of LLM PRs from new contributors" is warranted. See
[24413] for more details
[24413]: https://github.com/apache/datafusion/discussions/24413
-----------------------------------------
Attachment X: Report from the Apache DevLake Project [Hezheng Yin]
Apache DevLake — Board Report (Month 12-14 as Top-Level Project)
Reporting period: Jun 2026 - Aug 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 expanding
the plugin ecosystem, AI-metrics integration, and platform modernization.
Community activity remains healthy with broad contributions from both
established committers and new contributors.
- Community and project activity
No new committers or PMC members were voted in this period.
Significant engineering activity has been observed in:
- New Data Source Plugins: Added ClickUp (#9009), Linear (#8900),
incident.io (#9023), Jira Tempo Timesheets (#8884), and Azure DevOps
On-Premises Support (#9014). The DBT plugin was deprecated (#8971).
- AI & Copilot: Added AI credit usage billing metrics (#9019), Copilot
team adoption dashboards (#8966), Copilot metrics parity gap closures
(#8889), enterprise slug handling fixes (#8935), and Claude Code
organization support via the Console API (#8978).
- Jira Improvements: Persisted Sprint Report snapshots for accurate sprint
velocity (#9010), added Jira Cloud support via Atlassian API Gateway
(#9024), introduced JIRA_SKIP_UNPARSEABLE_ISSUES (#9026), and added extra
JQL filtering support (#8972, #9035).
- Grafana & Dashboards: Upgraded dashboards and provisioning for Grafana 13
(#8992), added PostgreSQL datasource support (#8870), and fixed Grafana
variable interpolation for string team/user IDs in MySQL dashboards (#8926).
- Security & Authentication: Added OIDC allowlist restrictions (#8984),
fixed webhook authorization when AUTH_ENABLED=true (#9008), ensured
authentication is disabled by default (#8951), and updated nginx-unprivileged
to 1.30.3 (#8940).
- Platform Modernization: Bumped Python runtime from 3.9 to 3.11 (#9005),
modernized the frontend toolchain and framework stack (#9006), and upgraded
core dependencies including go-git, libgit2/git2go, pgx/v5, and mockery.
- Releases
v1.0.3-beta15 — Released 2026-07-19
v1.0.3-beta14 — Released 2026-07-10
v1.0.3-beta13 — Released 2026-06-19
- Issues for the Board
No critical Board-level issues at this time.
- Community health
Active committers this period: ~14
New committers: None this period
New PMC members: None this period
Merged PRs: 91 (87 apache/devlake, 4 apache/devlake-website)
Issues created: 51 / closed: 65
Mailing list traffic: Moderate
No major conflicts or community issues reported
- Roadmap / upcoming work
AI & Copilot — Continue expanding Copilot and Claude Code metrics analytics
and dashboards.
Integrations — Stabilize newly added plugins (ClickUp, Linear, incident.io,
Tempo, Azure DevOps On-Premises) and improve Jira Cloud support.
Platform — Complete Python 3.11 migration, continue frontend modernization,
and finalize Grafana 13 compatibility.
Security — Continue hardening authentication (OIDC) and plugin isolation.
Stabilization — Drive v1.0.3 toward general availability release.
- Additional commentary
We are seeing strong momentum in the plugin ecosystem with five new data
source plugins added this quarter. Focus remains on stabilizing v1.0.3 for
GA release while continuing to expand AI-metrics and integration coverage.
-----------------------------------------
Attachment Y: 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 requiring board attention.
## Membership Data:
Apache Drill was founded 2014-11-18 (12 years ago)
There are currently 64 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.
- Huafeng Shi was added as committer on 2026-08-05
- Steve Lawrence was added as committer on 2026-06-10
## Project Activity:
This quarter we merged some significant work into Drill including:
* Drill-8543: Support for Marterialized Views
* Drill-8474: Add Daddodil Format Plugin
Additionally, there are some significant enhancements in review including:
* Drill-8552: Storage Plugin for Apache Accumulo
* Drill-8546: Storage Plugin for Microsoft Sentinel
* Drill-8537: Update Calcite to Version 1.42
A new committer has begun work on an integration between Drill and Apache
Ranger, which will add well needed access controls to Drill. We
have contacted the Ranger community and the author will be
contributing code there as well to support the integration. (Drill-8548)
### Drill MCP Server
We've also begun work on an official Drill MCP Server which we hope to
release officially in the coming weeks: https://github.com/apache/drill-mcp
### UI Refactor
The PMC Chair (C.Givre) has been working on a major UI refactor which includes
numerous new features including visualizations, notebooks, dashboards,
automated queries, alerting, and more. It also incorporates AI in virtually
all aspects of the interface, but not as an afterthought.
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:
Drill community is healthy.
dev@drill.apache.org had a 220% increase in traffic in the past quarter
(160 emails compared to 50)
issues@drill.apache.org had a 442% increase in traffic in the past quarter
(76 emails compared to 14)
user@drill.apache.org had a 63% decrease in traffic in the past quarter
(3 emails compared to 8)
7 JIRA tickets opened and 3 closed in the past quarter.
-----------------------------------------
Attachment Z: Report from the Apache ECharts Project [Wenli Zhang]
## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: NA
## Membership Data:
Apache ECharts was founded 2020-12-16 (6 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’re preparing the next version for testing. This release includes fixes
for several bugs found in previous versions, along with improvements to
overall stability and performance. We’re planning to submit the release
candidate sometime next week.
## Community Health:
The community continues to see contributions from multiple contributors,
with ongoing activity around pull requests and code contributions.
Contributors continue to propose improvements and participate in the
ongoing development of the project.
-----------------------------------------
Attachment AA: Report from the Apache EventMesh Project [Eason Chen]
-----------------------------------------
Attachment AB: 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 14 components.
Recent releases:
* maven-bundle-plugin 6.1.2 was released on 2026-09-02.
* org.apache.felix.http.base-6.0.2 was released on 2026-09-02.
* org.apache.felix.http.jetty-5.2.6 was released on 2026-09-02.
* org.apache.felix.http.jetty12-1.2.6 was released on 2026-09-02.
* org.apache.felix.http.jetty12-2.0.6 was released on 2026-09-02.
* maven-bundle-plugin 6.1.0 was released on 2026-07-30.
* org.apache.felix.http.jetty12-1.2.4 was released on 2026-07-27.
* org.apache.felix.http.jetty12-2.0.4 was released on 2026-07-27.
* org.apache.felix.http.base-6.0.0 was released on 2026-07-14.
* org.apache.felix.http.jetty-5.2.4 was released on 2026-07-14.
* org.apache.felix.http.jetty12-1.2.2 was released on 2026-07-14.
* org.apache.felix.http.jetty12-2.0.2 was released on 2026-07-14.
* org.apache.felix.log-1.3.2 was released on 2026-07-13.
* org.apache.felix.cm.json-2.0.8 was released on 2026-06-22.
## Community Health:
Overall the project is in ok health with very little ongoing activity. The
community activity remains on a low level and we continue to see little new
development right now. Questions on the user list are answered, development
concerns are either discussed on the mailing list or directly in the JIRA
issues. Traffic has been very low. We had no issues voting on releases (but
some wait time) and JIRA issues are generally addressed.
-----------------------------------------
Attachment AC: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment AD: Report from the Apache Flink Project [Robert Metzger]
## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Flink was founded 2014-12-17 (12 years ago)
There are currently 131 committers and 59 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 David Anderson on 2026-05-06.
- Samrat Deb was added as committer on 2026-08-28
- Hao Li was added as committer on 2026-06-08
- Weiqing Yang was added as committer on 2026-08-27
## Project Activity:
Big releases:
* Flink 2.3.0 was released by end of June, with any Flink SQL improvements
around PTFs, materialized tables, as well as a new native S3 connector,
scheduler improvements and many more.
* Flink Connector releases
* JDBC 4.1.0 and 3.4.0
* Kafka 5.0.0
* Pulsar 4.2.0
* HTTP 1.0.0
* Flink Agents released 0.3.0 (June 21) and 0.3.1 (July 25)
* Flink Kubernetes Operator 1.16 is ongoing RC voting
We also released Flink 1.20.5 and 2.1.3 in June.
13 FLIPs have been accepted this quarter.
## Community Health:
Alibaba hosted Flink Forward Asia 2026 in Shenzhen by end of June.
The dev mailing list enjoys very solid activity (up 23% from last quarter),
the user mailing lists (EN and ZH) keep declining (43%, 45%), most likely due
to the widespread usage of LLMs.
-----------------------------------------
Attachment AE: Report from the Apache Fluss Project [Jark Wu]
## Description:
Apache Fluss is a streaming storage system built for real-time analytics and
AI, serving as the real-time data layer for Lakehouse architectures.
## Project Status:
Current project status: Active.
Issues for the board: None.
Following Fluss's graduation as an Apache top-level project, the community
announced the graduation and completed substantially all post-graduation
transition work, including updates to project infrastructure, governance
information, release resources, and reporting arrangements.
## Membership Data:
Apache Fluss was established as a top-level project on 2026-07-15.
There are currently 22 committers and 14 PMC members in the project. The
Committer-to-PMC ratio is roughly 3:2.
Community changes during the past quarter:
- No new PMC members. The project graduated recently.
- Yang Wang was added as a committer on 2026-08-06.
There have been no additional membership changes since the previous report.
## Project Activity:
The community's main development focus during this period was completing the
remaining features for Apache Fluss 1.0 and preparing the project for release
stabilization. This will be the project's first release as an Apache top-level
project.
At the August 28 community call, the community targeted a feature freeze,
followed by creating the 1.0 release branch and starting release testing. The
final release date remains dependent on testing and the ASF voting process.
The remaining work mainly consists of documentation, dependency updates, and
correctness and stability fixes.
The 1.0 release will follow the release process for an Apache top-level
project. The required release resources, documentation, and release guide have
been updated accordingly.
Notable development and governance activities include:
- Following a public discussion [1] and vote [2] on dev@fluss.apache.org, the
PMC approved use of the Fluss name for the independently operated
fluss-contrib GitHub organization. The organization is explicitly separate
from the ASF and is intended to host ecosystem projects that do not fit the
ASF release lifecycle.
- Yang Wang and Yuxia Luo participated in Community Over Code 2026 Asia, held
from August 7 to 9, 2026, and presented Apache Fluss. Two additional
Fluss-related sessions were presented by other community contributors,
demonstrating growing interest and participation beyond the core project
team.
- The community held its monthly community call in August, focusing on the
remaining Apache Fluss 1.0 features, the feature-freeze plan, release
testing, and the next steps toward the project's first release as an Apache
top-level project. See the August community call summary [3] for details.
The most recent release is Apache Fluss 0.9.1-incubating, released on
2026-05-04.
## Community Health:
- dev@fluss.apache.org: 145 emails in July and 150 emails in August,
representing a 3.4% month-over-month increase.
- issues@fluss.apache.org: 1,095 emails in July and 1,518 emails in August,
representing a 38.6% month-over-month increase.
As Apache Fluss is reporting monthly for the first three months following its
graduation, we have reported mailing-list statistics for each month since
graduation rather than using quarter-over-quarter comparisons.
Traffic on the dev@ mailing list remained stable, with a modest increase in
August. The community completed most graduation and post-graduation
coordination work and shifted its focus back to completing the remaining
Apache Fluss 1.0 features, code reviews, release preparation, and
stabilization.
Traffic on the issues@ mailing list increased significantly in August. This
list primarily mirrors GitHub issue, pull-request, review, and CI activity,
rather than direct community discussion. The 38.6% increase reflects renewed
development activity as the community worked toward the 1.0 feature freeze and
prepared for release testing.
A new "Who is using Apache Fluss?" [4] GitHub discussion received nine
detailed responses from organizations using Fluss, including Alibaba, iQIYI,
Ververica, Fresha, RedNote, Ant Group, JD, and Cisco. This provided
encouraging evidence of adoption across end users, vendors, and ecosystem
contributors.
Overall, the month-over-month mailing-list data indicates that community
development activity is healthy and increasing as Apache Fluss moves closer to
its first release as an Apache top-level project.
## References:
[1] https://lists.apache.org/thread/8w412cn28256o8gnxcn8j78z9gpk66z3
[2] https://lists.apache.org/thread/r66k6po71l3tjpbd605zxpk97zz01fc2
[3] https://lists.apache.org/thread/rhpyq9v78jmoqh7f7cn7sorsxdqf0j74
[4] https://github.com/apache/fluss/discussions/4033
-----------------------------------------
Attachment AF: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AG: 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 (6 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:
Development activity was primarily centered around reliability and operational
improvements.
- Improved Temporal-on-YARN job completion handling so application outcomes
and terminal status are propagated reliably.
- Updated the YARN application launcher to wait for terminal application state
and cleanly shut down launcher-owned resources.
- Improved YARN application reconnection so applications can be rediscovered
across all application states, including terminal states.
- Added rename-order support for Iceberg table replication.
- Improved GaaS latency observability by propagating DAG action timing
information.
- Added snapshot and partition copy metrics to Gobblin
observability and job-status surfaces.
## Community Health:
There have been 7 commits since last report. Activity was focused on
production use cases, particularly YARN/Temporal reliability, Iceberg
replication, and operational observability.
No new committers or PMC members were added this quarter. We continue to look
for sustained contributors who may be candidates for committership and PMC
membership.
-----------------------------------------
Attachment AH: Report from the Apache Gravitino Project [Jerry Shao]
-----------------------------------------
Attachment AI: Report from the Apache Guacamole Project [Mike Jumper]
-----------------------------------------
Attachment AJ: 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 AK: Report from the Apache Helix Project [Junkai Xue]
## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources
## Project Status:
Current project status: low, moderate
Issues for the board:
## Membership Data:
Apache Helix was founded 2013-12-17 (13 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.1 was released on 2026-07-06
- 2.0.0 was released on 2026-06-15
## Community Health:
Minimized effort in development. Focusing on security things as security
scan has been done.
Officially announced 2.0.0 release. Start planning new components development
soon - light weighted compatible shard library (Tendril).
-----------------------------------------
Attachment AL: Report from the Apache Hive Project [Naveen Gangam]
-----------------------------------------
Attachment AM: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hudi was founded 2020-05-19 (6 years ago)
There are currently 44 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.
- Chaoyang Liu was added as committer on 2026-06-17
## Project Activity:
The community is currently voting on the Hudi-rs 0.5.0 release, which adds
support for newer Hudi table versions and the metadata table. RC1 did not pass
the vote, and RC2 is being voted, with the release targeted for the end of
the month. In parallel, the community is preparing the 1.2.1 patch release to
address bug fixes and improve stability, while also focusing on planning the
Hudi 1.3.0 release roadmap.
## 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 and office hours.
-----------------------------------------
Attachment AN: Report from the Apache HugeGraph Project [Jermy Li]
# HugeGraph project board report
## Description:
Apache HugeGraph is a full-stack graph database system, providing complete
graph data processing capabilities, include large-scale graph storage,
real-time querying, offline analysis, and graph AI. Supporting both Gremlin
and Cypher query languages.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache HugeGraph was founded 2026-01-21 (8 months ago).
There are currently 22 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is about 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was PPMC Member Yuchen Ding on 2024-12-18.
- No new committers. Last addition was Zhe Wang on 2025-09-01.
## Project Activity:
The HugeGraph release cycle is now 6 to 12 months, and a new version is
expected to be released in 2026.
- 1.7.0 was released on 2025-11-28.
Last quarter, we were preparing 1.8.0 release -- the first release after
graduation. we supported the docker deployment of distributed storage version,
supported k8s deployment of helm, adapted to tinkerpop 3.7/3.8 and Java 17,
and completed the enhancement of hugegraph-AI module. We expect to complete
1.8.0 release next month.
## Community Health:
Mail list dev@hugegraph.apache.org had a 5% decrease in traffic in the past
quarter (139 emails compared to 147).
The number of commits commits@hugegraph.apache.org increased by 2% in the past
quarter (299 commits compared to 292).
Last quarter, we were preparing for OSPP 2026 proposal by supporting the
RISC-V platform.
-----------------------------------------
Attachment AO: 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 40 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Prashant Singh on 2026-02-23.
- Maximilian Michels was added as committer on 2026-07-25
## Project Activity:
Releases:
- Terraform Provider 0.1.0 was released on 2026-09-02
- PyIceberg 0.12.0 was released on 2026-08-31
- Rust 0.10.1 was released on 2026-08-01
- Rust 0.10.0 was released on 2026-07-20
- C++ 0.3.0 was released on 2026-06-14
Specs:
- Iceberg REST catalog spec added read restrictions to support fine-grained
access control use cases, and labels to exchange catalog-owned metadata.
- Expressions: Added the expression spec for storing and exchanging expressions,
Updated REST protocol to include extended expressions.
- Indexes: A draft spec for scalar indexes is in review
- Tables: A draft spec for CHECK constraints is in review
- Tables: The changes for v4 adaptive metadata is in review
PyIceberg 0.12.0:
- Support for Python 3.14
- Commit retry support
- New file format API
- View support
- Geometry and Geography type support
Rust 0.10.x:
- Schema evolution: addition and removal of columns are now supported
- Added ExpireSnapshotsAction to expire old snapshots according to table policy
- Tokio runtime is now configurable
- Parquet content-defined chunking table properties are now respected
- Catalogs now support purge operations; some existing operations renamed from
drop to purge
- REST Catalog can now be queried for optional supported endpoints
C++ 0.3.0:
- Added commit retries and merging snapshot updates
- Implemented reachability-based garbage collection
- Updated FileIO to support streams and bulk deletes
- Implemented merge-on-read
- Added nanosecond timestamp support
- Added a Puffin reader and writer
- Implemented OAuth2 token refresh for REST
- Added metrics reporting for scan and commit
- Added SQL catalog implementation
Terraform 0.1.0:
- Initial release of the Terraform provider!
## Community Health:
The community continues to be healthy and make swift progress. To keep up with
the pace, this and future reports, project activity for implementations will be
based on released changes, not what has been committed.
The community is preparing the next Iceberg Summit, scheduled for April 2027.
Contributors have reported that GMail has begun to classify Iceberg dev@ emails
as spam in many cases. There appears to be no solution other than to add a rule
to prevent this. Other communities appear to be affected by the issue as well.
-----------------------------------------
Attachment AP: Report from the Apache Iggy Project [Kranti Parisa]
Description:
----
Apache Iggy is a high-performance, persistent message streaming platform
written in Rust, designed for predictable ultra-low latency, high throughput,
and efficient resource utilization.
Project Status:
----
Current project status: Active.
Issues for the board: None.
Apache Iggy graduated as an Apache Top-Level Project on August 19, 2026, after
entering the Apache Incubator in February 2025. Following graduation, the
community announced the milestone [1] and has been completing the
corresponding project infrastructure, governance, website, documentation, and
release-process updates.
Membership Data:
----
Apache Iggy was established as a top-level project on 2026-08-19.
There are currently 20 committers and 9 PMC members in the project, including
the PMC Chair. The project has more than 130 contributors overall.
Community changes during the past quarter:
----
The existing PPMC transitioned to the Apache Iggy PMC following graduation.
Several active contributors who had demonstrated sustained contributions were
also added as committers around the graduation period.
There have been no additional PMC membership changes since graduation.
Project Activity:
----
The community’s primary development focus during this period has been Apache
Iggy 0.9.0, which is planned to be the project’s first release as an Apache
Top-Level Project.
Apache Iggy 0.9.0 is a significant release and introduces built-in multi-node
clustering and data replication based on Viewstamped Replication Revisited
(VSR), together with a redesigned binary wire protocol shared across the
supported SDKs. The release discussion describes approximately 412 commits
from approximately 41 contributors since 0.8.0. [2]
Additional development work includes continued improvements across connectors,
SDKs, reliability, testing, observability, and developer experience. The
community is also actively developing a Kafka wire-protocol gateway for
interoperability with existing Kafka clients and tools, and a Swift SDK is
currently under review.
The most recent Apache release is Apache Iggy 0.8.0-incubating, released on
2026-04-22.
Community Health:
----
Development activity remains high. As of September 11, the repository has
approximately 2,900 pull requests completed or in progress, with 43 currently
open and 2,859 closed. There are approximately 144 open issues. [3]
The project has more than 130 contributors. At graduation, the community also
reported more than 4,500 GitHub stars, 2,700 pull requests, 700 Discord
members, and more than 500,000 cumulative downloads across distribution
channels. [1]
GitHub Discussions continues to be actively used for architectural and
community discussions, including VSR clustering, Kafka compatibility, tiered
storage, connectors, delivery semantics, and other roadmap topics.
The community has also started documenting organizations evaluating or using
Apache Iggy through the project’s “Powered by Iggy” page. Current publicly
documented users and integrations include RocketRide, Serro, VeloDB, and
VideoDB. [4]
Overall, Apache Iggy has maintained strong development and contributor
activity following graduation. The immediate community focus is completing and
validating the 0.9.0 release, particularly the new VSR-based clustering
capabilities, and preparing the project’s first release as an Apache Top-Level
Project.
References:
----
[1] https://iggy.apache.org/blogs/2026/08/24/apache-iggy-top-level-project-tlp-graduation/
[2] https://github.com/apache/iggy/discussions/3885
[3] https://github.com/apache/iggy
[4] https://iggy.apache.org/powered-by/
-----------------------------------------
Attachment AQ: Report from the Apache Incubator Project [Justin Mclean]
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 25 podlings under incubation. In August, the Incubator
made four releases, and a release vote for one podling is currently
underway. There were three additions and no removals to IPMC membership.
Two podlings entered incubation in August: Apache Maka and Apache Asyncband.
Apache NullAway shoudl be added next month. The graduation votes passed for
Apache ResilientDB and Apache Iggy, and Iggy has graduated. JB was on
holiday, so the board will see ResilientDB this month. Auron also discussed
graduation.
Mailing list discussion otherwise focused on new podling proposals, release
voting, and the status of several long-running podlings. Related
discussions covered metrics and guidelines for adding committers, and
handling of multiple podling status files.
Casbin's second release candidate passed, making the podling's first ASF
release.
Texera raised a question on the general list about the sites it is running
alongside its ASF website, which mentors are following up.
Pegasus has been in incubation since June 2020 with no release since
December 2023. The IPMC is discussing whether it should be retired. Neither
the podling nor its mentors have responded so far.
Toree, which has been incubating since December 2015, was the subject of a
similar status discussion. The March release vote was never completed; the
replacement candidate discussed in May has not appeared. A PPMC member has
since said the podling should be retired; the mentors have not responded.
OpenServerless has still not made an ASF release after more than two years
of incubation. Development activity remains high, but the first source
release discussed in late July has not happened. The podling acknowledges
that much coordination still happens on WhatsApp and in private meetings
rather than on the dev list.
PouchDB has now been incubating for 16 months without an ASF release. Its
dev list has been silent for two consecutive months. The legacy pouchdb.com
site now redirects to pouchdb.apache.org. The podling reports that
discussion is happening on Slack and in triage meetings rather than on the
dev list.
XTable released 0.4.0-incubating in August, its first release since June
2025, and is planning future releases.
OzHera is handling its first security vulnerability report with mentor
guidance.
Five proposals were under discussion during August: Aegis MCP Governance
Gateway, NullAway, OpenCrawling, MEA and Quilzo.
The IPMC discussed adding AI-related questions to the podling proposal
template, following the code provenance issues raised during the Maka
discussion.
Two sets of AI tooling have been added to the incubator repo and are open
for review: a set of skills covering common IPMC tasks such as report
review, release vote checking, graduation packets, and branding sweeps, and
several AI tutor lessons for Incubator training with a roadmap of
multiple lessons across eight different tracks. Both were drafted with AI
assistance and human-reviewed against the policy and guidance pages.
## Community
### New IPMC members:
- Chojan Shang
- Raúl Cumplido
- Xinyu Tan
### People who left the IPMC:
- None
## New Podlings
- Asyncband
- Maka
## Podlings that failed to report, expected next month
- None
## Graduations
- Iggy
The board has motions for the following:
- ResilientDB
## Releases
The following releases entered distribution during the month of
August:
- Casbin 3.11.0
- Burr 0.43.0
- Texera 1.2.0
- XTable 0.4.0
## IP Clearance
- none
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[Auron](#auron)
[BifroMQ](#bifromq)
[KIE](#kie)
[OpenServerless](#openserverless)
[Ossie](#ossie)
[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:
None.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Following community discussions and voting, we believe the Auron project
has largely met the graduation criteria, and intend to initiate a formal
discussion within the Incubator.
### How has the community developed since the last report?
1. Elected 4 new committer: Hai Zhou, Huawen Gui, Weiqing Yang, Ming Wei
2. Elected 2 new PPMC member: Ruilei Ma, Shilun Fan
3. Community presentations and outreach continued:
Yizhong Zhang presented a Auron talk at Apache DataFusion Meetup
Shanghai 2026
Li Zhang presented a Auron talk at Community Over Code Asia 2026 in
Beijing, August 8
### How has the project developed since the last report?
- Released Apache Auron v8.0.0-incubating on 2026-07-22.
- 82 commits since the last report, including significantly expands Flink
integration, native scan support for Apache Iceberg, Apache Hudi, and
Apache Paimon, native expression and function coverage, cross-version
compatibility, and runtime reliability.
- Completed a brand-new independent registration for the Auron WeChat
account. This account will be managed collectively by Auron PMC members
moving forward.
- Fixed the minor website defects mentioned by Justin and Calvin, also
carried out a full-site brand compliance self-inspection afterward to
eliminate similar hidden issues.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
Commentary: The project has established a regular Apache release cadence
and has completed the maturity model. As summarized in the community
graduation discussion, the community has 21 committers including mentors,
from more than 13 different companies, with 15 PPMC members and 67
contributors. During incubation, Auron made 3 releases in 11 months with 3
different release managers, used in production by 10+ well-known entities.
The project has opened 791 issues with 683 resolved, and 1655 PRs with 1621
merged or closed.
### Date of last release:
2026-07-22 (Apache Auron v8.0.0-incubating)
### When were the last committers or PPMC members elected?
The most recent committer was Ming Wei and Weiqing Yang, elected in
August.
The most recent new PPMC member was Ruilei Ma, elected in August.
### Have your mentors been helpful and responsive?
Yes. The mentors have been helpful and responsive. The mentors provided
guidance for the graduation discussion. No open issues at this time.
### Is the PPMC managing the podling's brand / trademarks?
Yes. The PPMC is actively managing the Apache Auron (Incubating) brand
and trademarks. The PPMC has fixed several branding issues related to
WeChat official account and minor website defects. There are no known open
brand or trademark issues at this time.
### Signed-off-by:
- [X] (auron) Becket Qin
Comments: Looking forward to graduation
- [X] (auron) Calvin Kirs
Comments: Graduation vote in progress
- [X] (auron) Hao Ding
Comments: looking forward to the graduation
- [X] (auron) Nicholas Jiang
Comments: Looking forward to graduation
### 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. Add more active committers and PPMC members from outside the original
team.
2. Make the next Apache release and involve more PPMC members in the
release process.
3. Expand the community user base and improve project visibility
### 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?
liaodongnian (GitHub: @liaodn) completed onboarding as a committer and
PPMC member, and contributed a fix for API store-range boundary encoding.
Contributors improved the project website and documentation, including
MQTT guidance, the security model, and site discovery.
Joined the open-source marketplace at Community Over Code Asia 2026 in
Beijing.
### How has the project developed since the last report?
Received issue reports from external users. 4 of the 7 PRs merged in the
main repository were contributed by people outside the original team.
Website work covered documentation, search discovery, ASF-hosted
Matomo,navigation fixes, and build checks.
### 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?
2026-06-04: liaodongnian (GitHub: @liaodn) completed onboarding as a
committer and PPMC member.
### 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:
- [ ] (bifromq) Penghui Li
Comments:
- [ ] (bifromq) Sheng Wu
Comments:
### IPMC/Shepherd notes:
--------------------
## KIE
KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.
KIE has been incubating since 2023-01-13.
### Three most important unfinished issues to address before graduating:
1. Readjust CI for 10.3.0 - supposed to be a release will be completely
clean of Category X
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nope.
### How has the community developed since the last report?
New committers elected. New release 10.2.0
### How has the project developed since the last report?
A huge unification of repositories been made, that aims to simplify our
build system. Supposed to have all Category X code and dependencies removed.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2026-04-29
### When were the last committers or PPMC members elected?
2026-07-23 - Committer
### Have your mentors been helpful and responsive?
Overall slow progress towards graduation. True that our reports are often
a bit behind.
### Is the PPMC managing the podling's brand / trademarks?
No response
### Signed-off-by:
- [X] (kie) Brian Proffitt
Comments: We should start making a targeted list of incubation hurdles
to cross (if any) to get this over the line to TLP
- [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. 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 has remained active, but much of the work has happened behind
the scenes. There are two main reasons for this: the project is heavily
structured around submodules, and many developers still coordinate through
WhatsApp and private meetings.
This is not aligned with the Apache Way. Unless we actively ask
contributors to move discussions to email, people tend to continue using
chat messages instead of the public mailing list. This creates a real
problem in how project activity is perceived.
The developers who have contributed code recently are:
- Michele Sciabarra
- Bruno Salzano
- Michele Manzani
- Daniele Cremonini
- Francesco Tiberi
Alessio Marinelli also proposed merging a significant new feature, a
Spark operator, which we decided to postpone to a later phase.
### How has the community developed since the last report?
- We added a new committer, Michele Manzani.
- We have seen new contributions through direct pull requests to the
OpenServerless MCP repository.
- A book on OpenServerless has been written by Alessio Marinelli and is
currently under review by Manning.
The project is still somewhat overlooked. However, it is the engine
behind other open source products expected to launch soon, including an
open source vibe-coding engine similar to Lovable.dev, and it has been
adopted by the Italian Government Cloud. For these reasons, we expect the
community to grow.
The Italian government adoption is expected to be finalized by
2026-12-31, and the Lovable-like project is expected to launch by
2026-09-30.
### How has the project developed since the last report?
We worked hard to prepare the first release.
The build has been completely reorganized to allow for a complete,
standalone source build.
The source build is ready, builds successfully, and passes the tests.
Some PPMC members tried it and verified that it works, but some
additional changes were required:
Changes completed: rebranding and properly addressing security issues.
Changes still to do: rebuild the images using tags that comply with ASF
usage rules, and document the contributing process.
We expect to call the vote for the first release as soon as those issues
are solved.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
### When were the last committers or PPMC members elected?
One new committer was elected in July 2026.
### Have your mentors been helpful and responsive?
Honestly, there has been some tension. We believed things were
progressing acceptably, but later understood that the podling was at risk
because we had not completed an Apache source release. We had mistakenly
treated regular Docker image publication and repository updates as
sufficient release activity.
In hindsight, we should have understood the Apache release expectations
much earlier. Once the issue became clear, we rushed to prepare a source
release and made substantial progress, though several additional problems
surfaced near the end.
We did the work together, made mistakes, and were corrected. Some of the
feedback was difficult for us to receive, especially given our limited
experience with the Apache release process, but we understand that the
release requirements are important.
The project is complex, and we still believe it has strong potential.
With the emergence of Private AI, the need for private serverless
infrastructure is growing, and we believe OpenServerless can become a large
and widely used project as significant use cases emerge.
### 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:
- [ ] (openserverless) Bertrand Delacrétaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [X] (openserverless) François Papon
Comments: The release process is on the way but need some works to be
mastered by the podling.
- [ ] (openserverless) Jean-Baptiste Onofré
Comments: We are discussing with the podling to accelerate on
releases, security reports and community grow. That's important
"questions" for me on the podling right now.
- [X] (openserverless) PJ Fanning
Comments: Some progress towards a first RC. The initial attempt was
added without signing files and digest files and no vote email was sent.
### IPMC/Shepherd notes:
--------------------
## Ossie
Apache Ossie comes from Open Semantic Interchange. It is an open
specification that defines a vendor-neutral format for
expressing business metrics, dimensions, and their
relationships. It enables any tool to consume and produce semantic
definitions without loss of meaning.
Ossie has been incubating since 2026-06-19.
### Three most important unfinished issues to address before graduating:
1. Complete the migration onto ASF infrastructure (git, dev/private
mailing lists, website/DNS, issue tracking) and retire the legacy OSI
resources; complete IP clearance / Software Grant so the spec and codebase
are cleanly under the ASF. This is almost done, final checks are in
progress.
2. Produce a first Apache release of the specification (and reference
tooling) following ASF release policy — establishing a repeatable,
mentor-verified release process with correct LICENSE/NOTICE and
source-release conventions. (Spec is currently at v0.1, pre-Apache-release.)
3. Grow a diverse, independent contributor and PPMC base beyond the
founding vendors, and demonstrate that spec/roadmap decisions are made in
public via the Apache Way (discussion + lazy consensus / votes on dev@). We
are happy to see already new contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
* The multi-vendor coalition behind Ossie continues to broaden: the
contributor/participant base has grown past 50 organizations, well beyond
the original launch partners.
* Kyvos, Veezo, SAAL, Honeydew, Saiku, Wingarc1st, Gravity, XSOLCORP,
PuppyGraph, ThoughtSpot joined the Ossie ecosystem.
* Several Working Groups remains active, shaping proposals to evolution
in the Spec.
* Public rename/incubation announcements (OSI -> Apache Ossie) went out
via the project blog and partner channels, driving dev@ subscriptions and
awareness.
### How has the project developed since the last report?
* The apache/ossie repository is active on ASF infrastructure (the
codebase predates incubation: 100+ commits and 35+ merged PRs since the
repo opened in Nov 2025 as OSI).
* Work has centered on the ASF governance/infrastructure transition and
on the specification roadmap: an expression-language spec, advanced metric
logic (windowing, complex relationships), additional platform converters, a
standardized semantic-query spec, and Apache Polaris integration for
catalog-level discoverability of semantic models.
* We already received contributions for several new converters from
different models, using different technologies (Python, Java).
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None yet — no Apache release has been made since entering incubation.
### When were the last committers or PPMC members elected?
* Initial committers (12) and PPMC (7) were seeded at the start of
incubation (2026-06).
* Josh Klark has been added to the PPMC on 2026-08-04
* Yong Zheng has been elected as committer on 2026-08-25
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
The project was deliberately renamed from OSI to "Ossie" ahead of
incubation to avoid acronym confusion.
The project name search has been done and approved by ASF Trademark team
(see https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-254).
The PPMC is carefully managing the brand/trademark.
### Signed-off-by:
- [X] (ossie) Jean-Baptiste Onofré
Comments:
- [ ] (ossie) Zili Chen
Comments:
- [ ] (ossie) Russell Spitzer
Comments:
- [ ] (ossie) Holden Karau
Comments:
### 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, keeping the
core library lightweight, making integrations pluggable, and
stabilizing the public API before 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?
* Five external contributors had changes merged across the main and
website repositories. Four contributed to the main repository, and a new
contributor proposed a website and documentation overhaul on dev@ and
delivered significant website improvements.
* The Playground website is now running at playground.otava.apache.org. It
provides a public way to compare Otava with other change-detection
approaches.
* External contributions covered the core library, integrations,
documentation and the project website.
* No new committers or PPMC members were announced during this period.
### How has the project developed since the last report?
* Continued refactoring the internal architecture toward a stable public
Python API and a clearer separation between the core library,
persistence, reporting, and external integrations.
* Expanded and simplified data-source integrations, including support for
InfluxDB and more consistent command-line configuration.
* Improved correctness, maintainability, and release readiness through
additional tests, typing fixes, dependency updates, and CI maintenance.
* Improved documentation and the newcomer experience through a buildable
documentation site, a redesigned project website, and clearer links to
the public Playground.
* Enhanced the Playground website to make comparisons between
change-detection algorithms easier to explore.
* No new release was made during this reporting period.
### 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:
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:
- [ ] (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?
No issues require IPMC or Board attention at this time. We are currently
handling our first security vulnerability report. Our mentors have already
provided remediation guidance, and we are carrying out the fix according to
their advice.
### How has the community developed since the last report?
- The project continued to receive steady contributions from around five
active contributors during this period (xs3508198, Xue, EricDing, lhhhhf,
dingtao).
- Merged several PRs focused on release hygiene and quality:
unifying/updating dependency versions, correcting Apache license file
headers, removing SNAPSHOT dependencies from the intelligence module,
cleaning up private dependency packages, and SQL/query optimizations (e.g.
#663, #666, #667, #669, #672, #674).
- We did not elect new committers/PPMC members this period; growing the
contributor base and identifying committer candidates remains an active
focus.
### How has the project developed since the last report?
- Published Apache OzHera 2.2.6-incubating on 2026-06-17, our latest
incubating release, with incremental improvements to the release process.
- Since the release, work has centered on commit-by-commit review and
codebase cleanup (dependency alignment, license headers, removing
SNAPSHOT/private dependencies).
- A SQL injection vulnerability was identified in the 2.2.6-incubating
release. The community is now remediating it, and this is the first time
the project is following the Apache security/vulnerability-handling process
end to end.
- We plan to publish the next incubating release in mid-October 2026,
which will deliver new features together with the fix for this
vulnerability.
### 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-06-17
### 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, our mentors have been helpful and responsive. For our current
security fix — the first time the project is going through
the Apache security-handling process — our mentors have already provided
guidance, and we are carrying out the remediation according to their
advice. No issues are currently falling through the cracks.
### 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:
- [ ] (ozhera) Yu Li
Comments:
- [ ] (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. Completing the ASF incubation process
2. Grow the PouchDB community and form better connections with sporadic
contributors
3. More and quicker releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- The project is regularly receiving contributions from a handful of
regulars and the occasional new contributor, and we are also receiving
good-quality issue reports.
- There is gradually more regular activity in the Slack channel, and
semi-regular triage meetings to work through the issue backlog.
- Added a new PPMC member (see below)
- Omitted from the last report was a well-received PouchDB presentation
we did at FOSDEM in Brussels early 2026, notes and videos here:
https://fosdem.org/2026/schedule/event/SDHGJY-local-first-meet-pouchdb-couch
db/
### How has the project developed since the last report?
We are making good progress in four areas:
- Moving the project towards replacing the underlying storage adapter in
a future release, which will allow us to remove a lot of outdated
dependencies and slim down the codebase
- General modernisation of the codebase
- We've completed migrating the website/docs to a modern system that is
easier to set up, use and onboard contributors to
- We've completed the move of the website to ASF domains and updated the
site to fulfill the ASF website requirements
Specific highlights:
- [Incorporated a new Node SQLite storage
adapter](https://github.com/apache/pouchdb/pull/9223), this step lays the
groundwork for deprecating and removing the LevelDB Subsystem that PouchDB
currently depends on, and that we want to move away from. This will shrink
the codebase and number of dependencies, and generally make the project
more nimble and easier to maintain.
- Completed migration of the old website and documentation from
Ruby/Jekyll to JavaScript/Eleventy for a modern developer experience in the
same language as the project itself, lower barrier to entry, less setup
hassle and faster builds. This included a new build and automatic
deployment pipeline that deploys to `https://pouchdb.apache.org` on merge
to `main`.
- The project website also now adheres to the ASF project and podling
requirements, incorporating the ASF/incubator logos and mentioning the ASF
and incubator in various places. The site code was also modernized to drop
some older dependencies, and no longer relies on external CDNs for assets
and libraries.
- [Fixed flaky tests with unpredictable timeout
errors](https://github.com/apache/pouchdb/pull/9205), which improved DX a
lot and made most CI runs much faster.
- Built out a new "versioned documentation" feature to allow docs per
release, the same way CouchDB does it, with versioning by release, `stable`
and `latest`. This is [technically
ready](https://github.com/apache/pouchdb/pull/9262), we are currently in
the process of backfilling the last few version's docs and
updating/rewriting the most recent release's documentation, guide and
learning pages.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
We're gradually aligning our processes with ASF expectations, but we
don't have a mailing list culture and this form of communication and
organization takes a bit of getting used to. Mailing list volume is low for
that reason. Apart from that, we've made a lot of progress in terms of
aligning our public communication with ASF policies, and are in the process
of adapting our release procedure. This is rather involved and takes longer
than expected.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
Jun 21, 2024 (pre-incubation). However, we are currently preparing a
9.1.0 release with the new SQLite storage layer, with the goal of making it
an ASF release with a WIP-release disclaimer.
### When were the last committers or PPMC members elected?
August 4th, 2026 Alex Feyerke (@espy)
### Have your mentors been helpful and responsive?
They have been, yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes, there are no issues to report, see here:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-260
### Signed-off-by:
- [X] (pouchdb) PJ Fanning
Comments: Dev list very quiet. GitHub activity in decline (compared
with Spring 2026).
- [X] (pouchdb) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AR: 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: none.
## Membership Data:
Apache IoTDB was founded on 2020-09-16 (5 years ago). There are currently 83
committers and 33 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:2.
Community changes, past quarter:
- Xuan Wang was added to the PMC on 2026-08-17.
- No additional committers were added after the previous report. The latest
addition remains Xinhao Gu on 2026-06-04.
## Project Activity:
- Apache IoTDB 2.0.10 was released in July.[1] The release expanded Table
Model SQL support with common table expressions, set operations, and new
built-in functions; introduced a C client SDK with parameter binding and
multi-node failover; improved cluster administration and observability;
and strengthened AINode model management and CPU inference stability.
- Development on the Table Model continued toward richer in-database analytics
and easier ecosystem integration. The community added the read_tsfile table
function for querying external TsFiles,[2] lateral column aliases in SELECT
lists,[3] Prometheus-style rate, increase, irate, and delta aggregate
functions,[4] and an FFT table function for frequency-domain analysis.[5]
- Reliability and deployment flexibility remained important focus areas. User,
role, and permission operations were integrated into the metadata
lease/self-fencing framework for high availability.[6]
- An IoTDB Edge distribution was also merged for a future release; it runs
ConfigNode and DataNode in one JVM with resource-constrained defaults
validated on Raspberry Pi-class devices.[7]
## Community Health:
Overall community health is good.
- dev@iotdb.apache.org had almost same traffic as the past quarter (253 emails
compared with 255). Discussions covered the 2.0.10 release and
future roadmap, Table Model analytics, the IoTDB Edge distribution, high
availability, and new client and ecosystem integrations.
- The Google Summer of Code project for integrating the IoTDB 2.x Table Model
with ThingsBoard made substantial progress. Telemetry, latest-value, and
attribute DAOs, together with aggregation support, documentation, and a
write-path benchmark, were merged into apache/iotdb-extras.[8]
- Following a community discussion and vote, the apache/iotdb-client-rust
repository was created. It now contains a working client for both the Tree
and Table Models, including session pools, multi-node failover, tablet
writes, paged query decoding, and TLS support.[9]
- On August 22, the 2026 Time Series Data Technology Innovation Summit was
held in Beijing. The event brought together users, developers, researchers,
and industry practitioners for discussions on time-series data management,
AI, open-source innovation, and Apache IoTDB use cases.[10]
- All trademarks issues that borads addressed are solved.
[1] https://github.com/apache/iotdb/releases/tag/v2.0.10
[2] https://github.com/apache/iotdb/pull/17951
[3] https://github.com/apache/iotdb/pull/17960
[4] https://github.com/apache/iotdb/pull/18334
[5] https://github.com/apache/iotdb/pull/18006
[6] https://github.com/apache/iotdb/pull/18425
[7] https://github.com/apache/iotdb/pull/18538
[8]
https://github.com/apache/iotdb-extras/tree/master/iotdb-thingsboard-table
[9] https://github.com/apache/iotdb-client-rust
[10] https://timecho.com/archives/1787553862296
-----------------------------------------
Attachment AS: 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.
Two more Jackrabbit Oak 2.x feature releases were cut in this period,
Oak 2.4.0 in July and Oak 2.6.0 in August, continuing the regular
release cadence on the current Java 17 baseline. The oak-blob-azure
module gained support for the Azure SDK V12, a large change
that modernizes the Azure blob storage integration. The build was also
updated to Apache Parent POM 39, and Groovy was upgraded to 4.0.33 so
that the project builds on Java 26. Routine dependency maintenance
continued at a steady pace across the MongoDB, AWS, Netty, Jackson,
Tomcat and testing libraries.
Query processing and indexing again saw the most concentrated work,
mostly on the Elasticsearch backend. Improvements covered index
provisioning and more graceful handling of missing indexes, reduced
document counts for dynamic boost, and better use of thread pools for
async response processing. Fulltext indexing was made more robust
around indexing-rule changes, overlong facet properties and other
query edge cases.
Work on the caching layer continued the migration towards Caffeine,
with cache maintenance now running asynchronously, precomputed element
count and weight in the persistent disk cache, a fixed bound for the
disk cache and a new cache for service lookups. Several obsolete
feature toggles were removed as the features they guarded became the
default (full GC, embedded verification and the prefetch code path,
among others). In addition, a project-level security threat model was
contributed and wired for automated discoverability through
THREAT_MODEL.md and the AGENTS.md / SECURITY.md chain.
## 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.5-beta was released on 2026-07-06
- jackrabbit-oak-2.4.0 was released on 2026-07-14
- jackrabbit-2.22.4 was released on 2026-08-06
- jackrabbit-oak-2.6.0 was released on 2026-08-24
## JIRA activity:
- 166 JIRA tickets created in the last 3 months
- 123 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AU: 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.12 is now in preparation, bringing several fixes on top of
4.4.11.
Development effort otherwise centered on turning the 4.5.0 roadmap items from
the previous report into actual code:
- The simple/flat feature resolver, bypassing OSGi capabilities resolution,
was merged into main, along with a new "karaf-light" distribution built on
it (the first concrete distribution to land from the 4.5.0 roadmap
discussion).
- The former "apache-karaf-integration" distribution was renamed to
"apache-karaf-mix" as part of clarifying the distribution naming (also a
roadmap item). Remaining org.apache.servicemix.specs BOM entries were
removed, continuing the legacy specs bundles cleanup.
- Pax Web has been upgraded from Pax Web 8 to 11, moving the Jakarta namespace
support forward and using recent Jetty version. It's an important (and long
due) update.
- Continuous dependency modernization: ActiveMQ, Hibernate, CXF, Jetty, JLine,
Jackson, SSHD, bnd, Plexus, Felix HTTP/Jetty12, and others were bumped
throughout the quarter (mostly via dependabot, reviewed and merged by the
PMC). Several CI/test stability fixes landed (flaky SSH integration tests on
Windows, itest teardown speed, JDBC example test robustness).
Release effort on the subprojects (Decanter, Cellar, Cave) is being held until
after Karaf 4.5.0 lands, so no subproject releases are expected this quarter.
Decanter 3.0.0 preparation (JDK 21+ support, event/alerting layer refactor)
continues in the background but isn't the current priority.
Karaf 4.5.0 itself
is now pretty close, with the feature resolver and distribution
naming/simplification work landed this quarter closing out the last major
roadmap items.
## Community Health:
GitHub activity this quarter was carried mainly by JB Onofré, Holger
Friedrich, Robert Varga, and Colm O hEigeartaigh, plus routine dependabot PRs
(the same contributor base as last quarter, consistent with no new
committers).
The project remains fully on GitHub Issues and GitHub Actions, with the legacy
Jira instance still read-only.
A talk about Karaf, introducing Karaf 4.5.0, is schedule for CommunityOverCode
26 Glasgow. We anticipate a community growth thanks for the Karaf 4.5.0 and we
plan an effort on the website (communication and content).
-----------------------------------------
Attachment AV: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none.
## Membership Data:
Apache Knox was founded 2014-02-18 (13 years ago)
There are currently 26 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Tamás Marcinkovics on 2025-11-10.
- No new committers. Last addition was Tamás Marcinkovics on 2025-10-17.
## Project Activity:
* 3.0.0 was released 2026-09-11
* Handling security reports with increased detail from security triage
* Have a 2.1.0 release candidate that is in testing now
## Community Health:
Lots of work being done on a new feature set under the moniker of KnoxIDF.
This is approaching Knox as a federated OIDC provider with agentic identity
capabilities.
dev@knox.apache.org had a 102% increase in traffic in the past quarter
(2312 emails compared to 1140)
109 JIRA tickets opened and 150 closed in the past quarter.
-----------------------------------------
Attachment AW: Report from the Apache Kvrocks Project [Mingyang Liu]
-----------------------------------------
Attachment AX: 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. No new
committers. Zhigang Wang was added as committer on 2026-05-29
Project Activity:
Released Apache Kyuubi v1.12.0 at 2026-07-28;
Adapting to new versions of compute engines is a routine task; this quarter,
we completed adaptations for Spark 4.1 and 4.2 as well as Flink 2.0 through
2.3, with AI significantly accelerating the pace of these adaptations.
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 30% decrease in traffic in the past quarter (17
emails compared to 24); notifications@kyuubi.apache.org had a 16% increase in
traffic in the past quarter (1121 emails compared to 964);
The overall traffic is low, but still at a good state because the project
itself is mature enough. With AI playing an increasingly prominent role in
recent community events, we are actively adjusting to and embracing this
transformation.
-----------------------------------------
Attachment AY: Report from the Apache Linkis Project [Shuai Di]
## Description:
The mission of Apache Linkis is to build a distributed computation middleware
to facilitate connection, governance, extensibility and orchestration between
the upper applications and the underlying data engines.
## Project Status:
Current project status: Ongoing.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Linkis was founded 2022-12-21 (4 years ago) There are currently 40
committers and 26 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 Jie Cheng on 2024-01-28.
- No new committers. Last addition was Kazuto Iris on 2026-06-03.
## Project Activity:
Apache Linkis V1.9.0 is currently in the testing phase.
- Restrict Hive SQL from specifying LOCATION during table creation.
- Support masking sensitive fields and truncating oversized fields in result
sets.
- Show newly supported engine versions in task history records.
- Support configuring a second queue in Spark.
- Fix exceptions in user job isolation entry and concurrency calculation.
- Security fixes with Apache security team:
- Completed the CVE-2023-49566 fix for non-MySQL JDBC drivers.
- Blocked JDBC URL-option injection via the DB2 instance field.
- Removed the hardcoded default cryptKey, refuse to start without a secure
key.
- Added source IP allowlist to the ignore-timeout cookie fallback in session
ticket auth.
- Enforced server-side session map check in the ignore-timeout path.
- Removed public documentation of the auth bypass from Knife4jConfig.
- Upgraded session ticket cipher from DES to AES-256-GCM,
backward-compatible.
## Community Health:
Overall community health is good. dev@linkis.apache.org had a 55% decrease in
traffic in the past quarter (113 emails compared to 252);
commits@linkis.apache.org (repo notifications) had a 59% increase in traffic
in the past quarter (266 emails compared to 167).
On GitHub, 16 PRs and 10 issues were closed in the past quarter. Activity
concentrated on the 1.9.0 security hardening cycle, with 7 merged security
PRs closing an auth-bypass chain and completing the CVE-2023-49566 fix.
-----------------------------------------
Attachment AZ: Report from the Apache Livy Project [Jean-Baptiste Onofré]
## Description:
The mission of Apache Livy is the creation and maintenance of software related
to web service that exposes a REST interface for managing long running Apache
Spark contexts in your cluster. With Livy, new applications can be built on top
of Apache Spark that require fine grained interaction with many Spark contexts
## Project Status:
Current project status: Ongoing
Issues for the board: None
Note: This is Livy's third and final
monthly report under the post-graduation reporting schedule; going
forward the PMC will report quarterly per the standard cycle.
## Membership Data:
Apache Livy was founded 2026-05-20 (4 months ago)
There are currently 25 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Alex Bozarth on 2026-05-20.
- No new committers were added.
## Project Activity:
Development:
- Spark 3.5.x support (merged around graduation) and Spark 4.x support work
ongoing.
- JDK 17 support merged. Along with that include Python 3.14 and Scala 2.13
fixes (in preparation for the Spark 4 upgrade)
- Spark 4 support PR is closed to be merged
- Log4j2 upgrade (replacing Reload4j).
- ZooKeeper SASL and TLS support added.
- There are also a few Kubernetes related improvements under code review.
Post-graduation infrastructure migration: Migration off the incubator
namespace (website, mailing lists, git, Jira) is complete.
## Community Health:
Continuing to follow up with PMC members who aren't yet active on private@/dev@.
With infrastructure migration behind us, focus is shifting to
community growth and promoting the project now that it has full TLP
visibility.
-----------------------------------------
Attachment BA: 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 (22 years ago)
There are currently 112 committers and 70 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Vigya Sharma on 2025-08-01.
- Tim Brooks was added as committer on 2026-06-05
## Project Activity:
A new minor release 10.5.0 shipped on 2026-06-25. It provided significant
columnar API focused changes, numerous vector search and hybrid
search improvements, and sundry optimizations.
A bug fix release 10.5.1 was completed on 2026-08-12.
Many community members are planning on meeting at future community over code.
As LLM usage continues to grow in programming, folks have continued discussing
how the Apache Lucene committers think about LLM usage in contributions.
Mainly, this is around LLM generated text.
Contribution guidelines are being added that encourage contributors
to not use LLMs when talking with other members of the community.
Apache Lucene has seen a substantial increase in the number of
reported security issues, many of which were erroneous; typically
concerning tampered index files or unsanitized input, which Lucene by
design trusts for performance reasons. A SECURITY.md file is being
added to the project to clarify Lucene's security model and posture
and how to report security issues according to ASF guidelines.
## Community Health:
Significant increase in all email lists. But most importantly
dev@lucene.apache.org had a 193% increase in traffic.
Contributing factors for this increase:
* the two releases (discussion and vote)
* welcoming Tim Brooks
* Community over code and LLM usage discussions.
Additionally, Github activity has continued to be healthy.
commits to the main branch: 284
issues filed: 66
closed issues out of those filed: 20
These numbers are fairly consistent compared with the previous quarter.
-----------------------------------------
Attachment BB: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment BC: Report from the Apache MADlib Project [Ed Espino]
-----------------------------------------
Attachment BD: Report from the Apache Magpie Project [Jarek Potiuk]
## Description:
Apache Magpie is responsible for the creation and maintenance of software
related to agent-assisted repository maintainership and development —
including issue and pull-request triage, contributor mentoring, agent-drafted
remediation, developer-side development-cycle skills, and narrowly-scoped
fix-and-merge automation. Magpie is deliberately governance-agnostic: it is
built to be adopted by ASF projects and by non-ASF open-source projects alike,
with no ASF-only assumption baked into the install path.
## Project Status:
Ongoing, high activity (with some low-activity period due to ASF events and
vacations). Almost all of this period went into the two things early adopters
complained about after 0.1.0: Magpie was hard to install, and once installed
it asked for approval too often to be useful.
* Marketplace distribution ready. Following industry standards adopted in
July/August Magpie can now be installed from a (distributed) agent
marketplace instead of committing framework machinery into the adopting
repository, and skills can be taken family by family rather than all at
once. The primary commands were renamed from adopt/unadopt to
install/uninstall, which is what people expected them to be called. This was
the largest single piece of work in the period and the direct answer to the
adoption friction reported last month.
* Permission-prompt reduction is underway, starting with the security family
and generalising from there. The aim is for a session to run to a useful
stopping point without a human approving each individual step, while keeping
the human in the loop for anything that changes state.
* No release this period. Apache Magpie 0.1.0 (2026-07-18) is still the only
Apache release. The 0.2.0 is being prepared around the installation and
permissions work. Though it’s likely we might call it 1.0.0 if it proves to
be prime-time-ready - based on feedback of early users.
No new issues for the board
Thanks to the board for answering our question in the last report. The
exploratory conversations with the Python Software Foundation and the Eclipse
Foundation continue, and remain exploratory. Nothing formal will be done
without engaging VP Marketing & Publicity first.
## Releases
* Apache Magpie 0.1.0 — 2026-07-18. Still the only release. Nothing
released in this period.
* 0.2.0 waits on the marketplace-installation and
permission-handling work landing complete rather than on a date.
## Membership Data:
Apache Magpie was founded 2026-06-17 (3 months ago)
There are currently 25 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- Andre Ahlert was added as committer on 2026-08-17
- Arnav was added as committer on 2026-08-13
- Yeonguk Choo was added as committer on 2026-08-17
## Project Activity:
* 89 pull requests merged in the period, from 20 distinct authors (19 people
plus Dependabot)
* The security skill family became a complete lifecycle. The threat-model
skills used to prepare over 70 ASF PMCs for the foundation's security
scanning effort has been made public on 3rd of September
https://news.apache.org/foundation/entry/security-scanning-at-foundation-scale
were brought into Magpie, so the family now runs from preparing a threat
model through triage, CVE allocation, fix and disclosure. Integration with
https://dash.security.apache.org/ and a skill that drives an external code
scanner are in progress. This matters because the scanning effort has left a
lot of PMCs asking how to handle the resulting influx of reports, which is
exactly what this family is for.
* Security work landed: security-model prepare/verify/update skills; a
finder-credit policy with a timing gate; a policy covering reporter-supplied
proof-of-concept code; and RFC-AI-0008, which describes handling reports
relayed through an intermediary rather than sent by the finder directly (the
ASF security team, a disclosure platform, an internal SOC).
* Consistency tooling. A set of deterministic checks now runs as commit hooks
across specs, evals, docs and the skill/tool tree, catching drift, stale
counts and broken cross-references. This is a deliberate response to a real
problem: agent-written content moves fast and quietly goes stale, and we
would rather catch that mechanically than by reading.
* Framework is at 74 skills and 46 tools, distributed as 10 family plugins.
* Vendor neutrality remains measured and published at 100%: 10/10 capability
contracts, 74/74 skills carrying no vendor lock-in, 22/22 substrate tools
harness-neutral. https://magpie.apache.org/#vendor-neutrality
* Governance note, for transparency. Last month we reported that
approval-before-merge had been turned on for main. That requirement is
currently and deliberately lifted while the installation and permissions
rework lands, because that work arrives as many small iterations that need
testing against a real merged main and a per-PR approval round-trip stalls
it for hours at a time. It is time-boxed and documented in .asf.yaml, not a
governance change: CI status checks, review-thread resolution and linear
history are all still gate main. Effectively, CTR (Commit-Then-Review) mode
is used for now rather than RTC (Review-Than-Commit). It goes back on when
this work is done (unless we decide otherwise).
* Submitted proposal for Devroom at FOSDEM: “Agentic Automation for OSS
Maintainers”
## Community Health:
* Three committers added — Arnav Purohit (2026-08-13), André Ahlert and
Yeonguk Choo (both 2026-08-17). These are the project's first committer
additions since establishment. No PMC additions or removals. 25 committers,
22 PMC members.
* Contribution is still concentrated. Of the 89 PRs merged this period, the
Chair authored 43. The PMC is clear that this is the main community-health
risk. The three new committers and the growing tail of contributors are the
counterweight; it will take more than one period to show.
* The other 19 authors were mostly people outside the founding PMC, so the
newcomer path is working even though the commit share is not yet balanced.
The good-first-issue programme is now at 111 curated issues, 81 closed.
* Community Over Code Asia - the Chair gave security keynote and a Magpie
“community” talk at the Community Over Code Asia in Beijing in August - the
reception was very warm and a lot of discussions at the event resulted in
reaffirming that security issue management and triage are a common pain
point among the community, but that easiness of use and low friction is a
key for Magpie’s popularity.
* Someone is using it on a real problem without being asked to. A community
member has been running Magpie against Apache Iceberg (iceberg-go) to work
through security scanner findings, and has been recommending it to the rest
of that PMC. That is the adoption shape we want — a maintainer with a
backlog, not a demo - first time where our Marketing
(speaking to others about us) turns into PR (others talking about us).
* Community Over Code Glasgow: A hackathon slot is reserved for Tuesday 12
September to get PMCs onto the security skill family, alongside the security
team's office hours. Four community members have already volunteered to help
run it. The intent is to convert "people don't know Magpie exists or that it
solves their problem" into projects actually using it.
* Skill quality is being addressed by hand. The PMC agreed that most skills,
having been written by agents, are longer and less predictable than skills
written by people. Before 0.2.0 we are going through the important ones and
rewriting them in plain human English — shorter, clearer and inside the
context budget. The agreed method is to use a skill first and then rewrite
it from that experience, which doubles as onboarding for PMC members who
have not yet used the framework closely.
* Still open from the last two reports: ASF Slack requires guest invites for
non-ASF participants, which works against being open to adopters outside the
foundation. The PMC has not yet chosen between Matrix and Discord for an
open channel.
-----------------------------------------
Attachment BE: Report from the Apache Mynewt Project [Szymon Janc]
## Description:
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android
## Project Status:
Current project status: ongoing
Issues for the board: ongoing
## Membership Data:
Apache Mynewt was founded 2017-06-21 (9 years ago)
There are currently 37 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Michał Górecki on 2024-06-27.
## Project Activity:
More work on CI workers on real HW (14 boards currently, various STM and Nordic
chips). More deprecated code removal (including unsupported boards/MCUs). Added
support for new STM32H5 chip family. Removal of deprecated crypto library
(tinycrypr), currently only mbedTLS is supported. Plans to move forward with PSA
API for crypto. NimBLE stack is continuing work on bugfixes and new Bluetooth
features.
Release (Mynewt 1.15, NimBLE 1.10) done June 2026. Project took part in
Glasswing program, results are being analyzed.
## Community Health:
We see increase flow of PRs from new commiters (partly due to LLMs being used
to fix random issues around the code).
-----------------------------------------
Attachment BF: 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: none.
## 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 31 was released on 2026-08-10.
- Apache NetBeans 30 was released on 2026-05-18.
- Apache NetBeans 29 was released on 2026-02-23.
## Community Health:
- Memorandum of Understanding between Friends of Apache NetBeans and Apache
NetBeans PMC has been voted on and accepted:
https://lists.apache.org/thread/rjor0cx6dggyf80lxvof6yg09b9jn7hw
- Friends of Apache NetBeans installers are now listed on the Apache NetBeans
Download page: https://netbeans.apache.org/front/main/download/nb31/
- dev@netbeans.apache.org had a 17% increase in traffic in the past quarter
(108 emails compared to 92)
-----------------------------------------
Attachment BG: 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 (20 years ago)
There are currently 66 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Konstantinos Marinos was added as committer on 2026-06-26
- Lukas Finster was added as committer on 2026-06-26
- Konstantinos Marinos was added to the PMC on 2026-08-09
- Lukas Finster was added to the PMC on 2026-08-10
- Anahita Goljahani was added to the PMC on 2026-08-10
## Project Activity:
* No new releases were published during the reporting period (the last release
was published on 2026-06-10); however, a new release is upcoming.
* The 24.09 branch continues to serve as the current stable release line. The
community has also defined the roadmap for the upcoming releases:
** Create the new release branch in November 2026, named release26.11.
** After an adequate branch stabilization period, publish the first release
from the release26.11 branch no later than March 2027.
** Set the end-of-life date for the release24.09 branch to coincide with the
publication of the first release from the release26.11 branch, no later
than March 2027.
* Several new features were contributed by community members and successfully
merged during the reporting period, reflecting continued development
activity and contributor engagement.
* The OFBiz security team is handling an increasing number of security
reports. While the team continues to work through the backlog, handling
security reports presents particular challenges because this work differs
significantly from standard bug fixing. Standard bugs can be openly
discussed and addressed by the broader community of volunteers, with
contributors picking up tasks according to their interests and availability.
Security reports, by contrast, require prompt resolution and need to be
handled by a smaller group of contributors (those in the security team/PMC),
while also requiring additional administrative work, including CVE creation,
coordination with reporters, and preparation of security announcements. As a
result, this process does not benefit from some of the key advantages of
open source development, such as the ability to distribute work among a
larger pool of volunteers based on their availability. The current
security-reporting process is therefore proving challenging for the
community and appears to be better aligned with a more traditional
development model, where a dedicated team can be consistently assigned and
available to handle this type of work.
## Community Health:
During the reporting period, the community remained highly active across
several areas, continuing the efforts of previous reporting periods. These
included new features, bug fixes, the design and implementation of security
improvements, and enhancements to the project's CI/CD workflows. Mailing list
discussions were frequent and productive, and contributors reviewed and merged
a substantial number of pull requests. Two new committers were added during
this reporting period and were subsequently elected as PMC members. One
additional PMC member was also elected.
-----------------------------------------
Attachment BH: 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, with high activity.
Issues for the board: The OpenDAL PMC has approved the proposal to establish
Reqsign as a standalone Apache top-level project. The suitable-name review was
approved on 2026-09-07. The proposal awaits Board approval; Reqsign remains
under the OpenDAL PMC during this process.
## Membership Data:
Apache OpenDAL was founded on 2024-01-17. There are currently 40 committers
and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 1.7.
Community changes since the last report:
- Yuang Gao (yuang) was added as a committer on 2026-09-04 and welcomed
publicly on 2026-09-07.
- No new PMC members. The latest addition was Hao Jiang (dentiny) on
2026-06-02.
## Project Activity:
OpenDAL has made the following releases since the last report:
- Apache OpenDAL v0.58.0 on 2026-07-16.
- Apache OpenDAL v0.58.1 on 2026-07-31.
- Apache OpenDAL v0.58.2 on 2026-08-21.
- Apache OpenDAL v0.59.0 on 2026-09-04.
- Apache OpenDAL Reqsign v0.20.2 on 2026-07-10.
- Apache OpenDAL Reqsign v0.20.3 on 2026-07-27.
- Apache OpenDAL Reqsign v0.20.4 on 2026-08-04.
- Apache OpenDAL Reqsign v0.20.5 on 2026-08-07.
- Apache OpenDAL Reqsign v0.20.6 on 2026-08-24.
Notable project activity this quarter:
- Storage functionality expanded with S3 Express authentication, object
restoration, conditional operations, a Google Cloud Storage gRPC service,
and object composition. C++ and .NET bindings gained additional operation
coverage, alongside continued Python and other binding improvements.
- The project established shared specifications for behavior across language
bindings and improved upgrade guidance and release validation for ecosystem
integrations.
- Package publishing moved to short-lived OIDC credentials for Rust, Python,
Node.js, .NET, and Ruby. Work also began on automated source-candidate
preparation and staging through the Apache Trusted Releases service.
- Reqsign improved cloud credential handling and added AWS SigV4a and S3
Express support. Its proposed transition to a standalone project would give
its community direct responsibility for releases, security, and governance.
From 2026-06-10 through the 2026-09-08 data collection, the main repository
merged 340 pull requests, including 300 from 53 human contributors. The
Reqsign repository merged 56 pull requests, including 46 from 8 human
contributors. The remaining pull requests were dependency-bot updates.
## Community Health:
### Are there any risks to the sustainability of the project?
OpenDAL remains active, with continued contributor participation and regular
releases. Maintaining the cross-language and storage-service test matrix,
reviewing contributions, and verifying release artifacts require sustained
maintainer attention. Several release candidates needed packaging or license
material corrections this quarter. The community is improving release checks
and automation to reduce that workload. A weekly release cadence is under
discussion; independent artifact verification and PMC votes remain necessary.
Following the previous report's discussion of AI use, the project added an
AI-assisted contribution policy. It requires meaningful human involvement,
disclosure of material AI assistance, and verification of submitted claims.
Service-specific bug reports require reproduction against the actual service.
The human contributor remains accountable for the submission. These rules aim
to protect reviewer attention while allowing useful AI-assisted work.
### Is the PMC capable of responding to security issues and performing releases if needed?
Yes. Multiple PMC members participated in release verification and voting this
quarter, supporting nine formal releases across OpenDAL and Reqsign. The PMC
maintains a documented security reporting process and can coordinate with the
ASF Security Team. Trusted publishing and stronger source-package checks also
improve the release process.
OpenDAL v0.59.1 is currently under vote to correct a missing changelog in the
published opendal-core crate; it is not included in the release count above.
### Does the PMC need anything from the Foundation to improve on contributing to our mission of delivering software for the public good?
The PMC seeks Board approval of the Reqsign TLP proposal and, following
approval, Infrastructure support for the transition.
As in the previous report, additional GitHub Actions capacity and access to
advanced AI models would help with cross-platform validation and project
maintenance. AI-assisted work remains subject to human review and the
project's contribution policy.
-----------------------------------------
Attachment BI: 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 (15 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.
- No new committers. Last addition was Kristian Rickert on 2026-05-05.
## Project Activity:
OpenNLP 1.9.5 was released on June 22 to address CVEs. The PMC then voted to
end-of-life 1.9.x and direct users to OpenNLP 2.x instead. OpenNLP had two 2.x
releases to address CVEs and minor improvements. Version 3.0 is in active
development and had two milestone releases, while version 2.x had two minor
releases.
## Community Health:
Community activity remains low but healthy. Recent releases benefited from two
new contributors. Mailing list traffic is mostly consistent with previous
periods, and same with GitHub activity.
-----------------------------------------
Attachment BJ: Report from the Apache OpenWebBeans Project [Mark Struberg]
-----------------------------------------
Attachment BK: Report from the Apache ORC Project [William Hyun]
## Description:
The mission of ORC is the creation and maintenance of software related to the
smallest, fastest columnar storage for Hadoop workloads
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache ORC was founded 2015-04-21 (11 years ago)
There are currently 50 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Yuanping Wu on 2025-08-29.
- Hao Zou was added as committer on 2026-08-05
## Project Activity:
According to our release cadence, we released two maintenance releases
in this quarter and helped other Apache communities use them.
- 2.3.1 was released on 2026-07-16.
- 1.9.9 was released on 2026-07-08.
## Community Health:
Overall community health is looking steady, with traffic increase of 45% and 20%
respectively in the dev mailing list and issues mailing list.
-----------------------------------------
Attachment BL: 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 32 committers and 14 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 Junhao Ye on 2025-02-25.
- Chenghui Chen was added as committer on 2026-05-29
- Kerwin Zhang was added as committer on 2026-08-24
- Xinyu Liu was added as committer on 2026-08-23
- Quake Wang was added as committer on 2026-06-16
- Xinyu Wang was added as committer on 2026-07-12
- Yuxia Luo was added as committer on 2026-08-24
## Project Activity:
Software development activity:
- Releasing 2.0.0. Advances Paimon as a unified multimodal lakehouse.
- Releasing paimon-cpp 0.1.0. Cpp Implementation for Paimon.
- Releasing paimon-rust 0.3.0. Rust Implementation for Paimon.
- Releasing paimon-vindex 0.4.0. Vector Index for Paimon.
Multiple languages, multiple implementations, cover Java, python, rust, cpp.
## Community Health:
- dev mail list had 129% increase (266 emails compared to 116).
- issue mail list had 167% increase (9231 emails compared to 3455).
- user email list had 60% decrease (8 vs 20), using GitHub Issues and PRs.
- Contributions increased significantly, with a large number of pull requests.
-----------------------------------------
Attachment BM: 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 reasonably healthy. Releases are still happening regularly and
hopefully, we should start releasing our full 2.0.0 releases soon.
Issues for the board: None
## Membership Data:
Apache Pekko was founded 2024-03-20 (2 years ago)
There are currently 29 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- Philippus Baalman was added to the PMC on 2026-08-26
- No new committers. Last addition was Philippus Baalman on 2026-03-21.
## Project Activity:
Bug Fix Releases are being made. The 2.0.0 releases should start happening
soon after a number of milestones. Could take a while to get 2.0.0 releases
for all of our modules.
## Community Health:
There is a relatively small active committer base compared with the
amount of code that we manage but the health is ok.
-----------------------------------------
Attachment BN: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BO: Report from the Apache Pinot Project [Kishore G]
-----------------------------------------
Attachment BP: Report from the Apache PLC4X Project [Lukas Ott]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Project Status:
Current project status: Apache PLC4X continues to advance its mission of
providing unified libraries for PLC communication. The 1.0.0 release (recently
finalized) delivered: New drivers (UMAS, SLMP, BACnet/IP, etc.). Protocol
enhancements (OPC-UA, S7, Modbus, EtherNet/IP). Performance optimizations
(virtual-thread I/O, subscription emulation). Security hardening (TLS
defaults, certificate validation).
Issues for the board: No issues for the board.
## Membership Data:
Apache PLC4X was founded 2019-04-17 (7 years ago)
There are currently 22 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Unai Lería Fortea on 2025-09-29.
- Luis Rodriguez was added as committer on 2026-07-20
## Project Activity:
Apache PLC4X continues to advance its mission of providing unified libraries
for PLC communication. The 1.0.0 release (recently finalized) delivered: New
drivers (UMAS, SLMP, BACnet/IP, etc.). Protocol enhancements (OPC-UA, S7,
Modbus, EtherNet/IP). Performance optimizations (virtual-thread I/O,
subscription emulation). Security hardening (TLS defaults, certificate
validation). Key Focus Areas: SPI3 migration for all drivers. Java 21 baseline
(API module remains Java 17-compatible). Standardized array addressing and
configuration syntax.
## Community Health:
Strengths: Technical innovation and release of 1.0.0. Community growth
lagging. AI Pullrequests with no interest in the community itself. We aim to
improve communication around pull requests and introducing on the mailing list
to see if the person is actually interested in contributing , joining the
community and not only AI vibe coding to "farm" code contributions on
Opensource projects.
-----------------------------------------
Attachment BQ: Report from the Apache Pony Mail Project [Rich Bowen]
# Apache Pony Mail — Board Report, September 2026
## Description
Apache Pony Mail provides mail-archiving, archive browsing, and mailing list
interaction services.
## Project Status
Current project status: Ongoing (recently graduated)
Issues for the board: None.
## Membership Data
Apache Pony Mail was established 2026-07-15 (11 weeks ago). There are
currently 11 committers and 6 PMC members in this project.
No new committers or PMC members have been added since graduation.
## Project Activity
The primary development focus this month has been on security hardening of the
private-list authorization system.
## Mailing List Activity
The dev@ mailing list saw 5 messages across 3 threads in August 2026. The
threads covered the INFRA repository rename status and the security-related
PRs.
## Releases
No releases have been made since graduation. The most recent release was
0.11-incubating (March 2019).
## Community Health
The project has active participation from PMC members and has attracted
external engagement.
The project continues to acknowledge that its contributor community will
remain small given the specialized domain, but the existing PMC has sufficient
depth to sustain development.
## Reporting Schedule
This is the second of three required monthly reports following graduation
(August, September, October 2026). After October, the project will move to its
assigned quarterly rotation.
-----------------------------------------
Attachment BR: 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:
There was an increase in development activity last quarter although the mailing
list stats show otherwise. As a result of this we finally released
APR Util 1.6.4 (2026-08-06) the first release of APR Util since Februrary
2023 which addressed 6 smaller issues and 5 CVE's: 4 reported in March this
year and one low severity long runner from June 2024. We also introduced a new
security reports page on our site that makes it easy for our users to get an
overview of the fixed CVE's (https://apr.apache.org/security_report.html).
Shortly afterwards APR Util 1.6.5 (2026-08-10) was released to fix a
regression in APR Util 1.6.4.
The build also caused quite some improvements to the deployment and
build scripts that should ease the creation of further releases.
## Community Health:
-----------------------------------------
Attachment BS: 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:
- Pulsar 5.0.0-M1, the first preview of Pulsar 5, was released on June
23rd 2026. It is a milestone build meant to gather early feedback ahead
of the 5.0 LTS release, and previews the major changes of 5.0:
- Scalable Topics: a new kind of topic (topic:// scheme) that sizes
itself to its actual load. The broker splits hot key-range segments
and merges cold ones at runtime, with no downtime and without
breaking per-key ordering, so there is no partition count to choose
up front (PIP-460, 466, 468, 473, 475, 483).
- A new V5 Java client (pulsar-client-v5): a clean-slate redesign with
three purpose-built consumers (Stream, Queue, Checkpoint). It works
against existing topics and can subscribe to an entire namespace.
- Oxia is now the recommended metadata store for new clusters, with a
live, zero-downtime migration from ZooKeeper (PIP-454, 469). The etcd
backend is removed (PIP-462).
- Structured logging (PIP-467), IO connectors moved to a dedicated
repository (PIP-465), the javax.* to jakarta.* migration (PIP-472)
and the move from Maven to Gradle (PIP-463).
- The second milestone, 5.0.0-M2, is under vote as of this writing
(release candidate published September 12th). Pulsar 5.0.0, the next
LTS release, is targeted for this fall.
- Pulsar 4.2.0 remains the latest feature release (March 31st 2026).
Maintenance releases across the 4.2.x and 4.0.x (LTS) lines continue on
a regular cadence; the 3.0.x LTS line has reached end of support:
- 4.2.4 was released on August 3rd 2026
- 4.0.13 was released on August 3rd 2026
- 4.2.3 was released on July 6th 2026
- 4.0.12 was released on July 6th 2026
- 5.0.0-M1 was released on June 23rd 2026
- Pulsar C++ releases:
- No new release this quarter (latest is 4.2.0, June 14th 2026)
- Pulsar Go releases:
- 0.21.0 on July 20th 2026
- 0.20.0 on June 15th 2026
- Pulsar Python releases:
- 3.13.0 on July 6th 2026
- Pulsar NodeJS releases:
- 1.18.0 on June 26th 2026
- Pulsar C# (DotPulsar) releases:
- 5.3.3 on August 26th 2026
- 5.3.2 on August 14th 2026
- Pulsar Helm Chart releases:
- 4.7.0 on July 13th 2026
- 4.6.1 on June 18th 2026
- The connectors repository, split out of the main repo under PIP-465,
saw a large integration-test and bug-fix pass in July (32 PRs merged),
adding real integration tests for a dozen connectors and fixing the
runtime bugs that surfaced as a result.
- The flow of "Pulsar Improvement Proposals" remains strong. After the
exceptional burst leading up to 5.0.0-M1, this quarter saw 17 PIPs with
activity, 9 of them new (PIP-486 through PIP-494). Themes include
follow-ups to the Scalable Topics initiative (PIP-486, 494), a set of
security and authentication proposals (PIP-478, 485, 488, 489, 490),
operability and metrics (PIP-470, 487, 492) and consumer delivery
semantics (PIP-491, 493):
PIP-486: Scalable Topic Key-Shared Consumption
PIP-487: Add event count metrics for InflightReadsLimiter acquire and
release operations
PIP-488: Pluggable authentication audit-event hook
PIP-489: FIPS 140-3 compliance mode for Apache Pulsar
PIP-490: Zero-downtime token signing-key rotation for the built-in JWT
provider
PIP-491: Prevent delivery stalls by making the client return exactly
the permits used by the broker
PIP-492: Add subscription-level storage backlog age metric and stats
field
PIP-493: Key-ordered negative acknowledgement for Key_Shared
subscriptions
PIP-494: Scalable Topics Client Specification — authoritative reference
and change process
- Pulsar has reached 732 contributors on the main GitHub repo
(It was 724 in June 2026)
## Health report:
- The community remains healthy. The first Pulsar 5 preview shipped in
June with a second milestone now under vote, maintenance releases
continue monthly on both supported lines, and PIP activity, while down
from the exceptional pre-5.0.0-M1 burst of last quarter, is in line
with its historical level. A new committer was added this quarter, the
first since July 2025. Most day-to-day user interaction continues to
happen on Slack and GitHub rather than on the users@ list.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (8 years ago)
There are currently 86 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.
- Zhuohan Zhou was added as committer on 2026-08-05
## Community Health:
- Activity on the dev@ list returned to its typical level this quarter,
after the previous quarter's spike driven by the Scalable Topics PIPs
ahead of the 5.0.0-M1 release. Traffic is a mixture of release votes,
PIP discussions and design threads from both long-time and newer
contributors.
- users@pulsar.apache.org:
- 0% change in traffic in the past quarter (15 emails compared to 15)
- dev@pulsar.apache.org:
- 48% decrease in traffic in the past quarter (166 emails compared to 319)
## Slack activity:
- 10917 Members (10910 in June 2026)
- 56 Active monthly users (133 in June 2026)
-----------------------------------------
Attachment BT: Report from the Apache Ranger Project [Selvamohan Neethiraj]
-----------------------------------------
Attachment BU: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment BV: Report from the Apache Royale Project [Andrew Wetmore]
BoardReport 2026 09
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 prepare Royale for AI-related submissions and use. A
codegraph generator for Royale framework code is in development. The objective
is to make AI agents more efficient and effective when working with Royale
applications. We have started discussing whether to make use of the Apache
Trusted Releases (ATR) platform when it becomes available.
We released Apache Royale Compiler Build Tools 1.2.2 and Apache Royale
Compiler JBurg Types 1.1.1.
Voting is in progress on the Apache Royale 1.0.0 release.
Community Health: The project membership, though small, continues active, with
the return of some committers who had been unavailable for months.
-----------------------------------------
Attachment BW: Report from the Apache Samza Project [Jagadish Venkatraman]
## Description:
The mission of Samza is the creation and maintenance of software related to
distributed stream processing framework
## Project Status:
Current project status: Dormant
Issues for the board: No issues require attention of the board
## Membership Data:
Apache Samza was founded 2015-01-22 (12 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Bharath Kumarasubramanian on 2020-02-13.
- No new committers. Last addition was Shekhar Sharma on 2024-04-21.
## Project Activity:
Project activity has been relatively minimal, with just one community event last
quarter
## Community Health:
We held an in person meetup on Stream Processing with Apache Kafka,
Samza, and Flink at the LinkedIn HQ on Jun 24, 2026 that was well
received.
We had 3 talks focussed on stream procesing anomaly detection,
shared logs and operability at scale.
https://www.meetup.com/stream-processing-meetup-linkedin/
-----------------------------------------
Attachment BX: Report from the Apache SeaTunnel Project [Jun Gao]
-----------------------------------------
Attachment BY: Report from the Apache ServiceComb Project [Zhangjian He]
-----------------------------------------
Attachment BZ: Report from the Apache Shiro Project [Lenny Primak]
-----------------------------------------
Attachment CA: Report from the Apache SINGA Project [Wang Wei]
## Description:
The mission of Apache SINGA is the creation and maintenance of software
related to a distributed deep learning platform
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SINGA was founded 2019-10-16 (5 years ago) There are currently 23
committers and 16 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.
## Project Activity:
The team has released SINGA 5.1.0 on 2 April 2026.
In the past quarter, the community is working on the following
features/changes:
1. Updating the implementations of datasets for the PEFT application.
2. Adding the implementations for the model storage layer.
3. Restructuring the folders for the model selection application.
4. Adding the datasets for the transformer application.
5. Removing the obsolete information in README.
6. Updating the Ubuntu runner image.
## Community Health:
According to the statistics, there are increase of email traffic and github
commits, which shows that the community is active in the development.
-----------------------------------------
Attachment CB: Report from the Apache Sling Project [Alexandru-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 17 releases for this reporting period.
## Community Health:
Community health is pretty good and contributions from various
individuals continue.
-----------------------------------------
Attachment CC: Report from the Apache Sourcelume Project [Jamie Goodyear]
## Description:
Apache Sourcelume provides a metadata spec, registry, and signing pipeline —
for publishing and independently verifying provenance records of AI training
datasets.
## Project Status:
Current project status: New
Issues for the board: none
No current releases.
## Membership Data:
Apache Sourcelume was founded 2026-08-18
There are currently 8 PMC members / committers in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
- Apache Sourcelume has created its email lists, website, and started initial
repos.
- PMC helped Apache Marketing and Publicity with Apache Sourcelume's TLP news
release.
- Apache Sourcelume members have registered a hackathon session for Community
over Code Glasgow 2026.
https://events.apache.org/events/2026/community-over-code/sourcelume.html
## Community Health:
Our community has just started from our PMC group. Our dev email list is alive
with architecture and technical discussions. We have begun our outreach to
attract contributors, seeing dev list subscribes from outside the PMC.
-----------------------------------------
Attachment CD: 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 development and we plan to release a 4.0.3
version in the upcoming months. sa-vm.a.o is frequently targeted by DDoS
attacks, firewall rules and rate limiting in our cgi code have minimized 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 CE: Report from the Apache Steve Project [Greg Stein]
## Description:
The mission of Steve is the creation and maintenance of software related to
Apache's Python based single transferable vote software system
## Project Status:
Current project status: low activity
Issues for the board: none
## Membership Data:
Apache Steve was founded 2012-07-24 (14 years ago)
There are currently 11 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Zili Chen was added to the PMC on 2026-09-02
- No new committers. Last addition was Zili Chen on 2025-10-31.
## Project Activity:
Very little activity has been occurring. The repository has been cleaned up,
along with fixes to the website. We've seen a few issues filed, for us to
track needed work.
## Community Health:
We need more committers, but this is a very specific project that does not
engender broad appeal. We're not sure where interest will come from, beyond
internal Foundation interest.
-----------------------------------------
Attachment CF: 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 (maintenance mode)
Issues for the board: none
## Membership Data:
Apache Storm was founded 2014-09-17 (12 years ago) There are currently 49
committers and 48 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- Gianluca Graziadei was added to the PMC on 2026-07-22
- Gianluca Graziadei was added as committer on 2026-06-16
## Project Activity:
The project remains in maintenance mode. Following last quarter's burst of
security releases, this quarter was quieter on the release front and focused
on triage, dependency maintenance and review of incoming contributions.
The influx of (AI-)assisted vulnerability reports we described last quarter
has continued. We keep triaging these as they arrive; so far this quarter no
further genuine CVEs have been confirmed beyond the five already addressed and
shipped.
Recent releases: 3.0.0 was released on 2026-07-23
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.
A further maintenance release is expected once the current triage backlog and
pending dependency updates have settled.
## Community Health:
The most encouraging development this quarter is that the PMC has grown for
the first time in over a year: Gianluca Graziadei was invited as a committer
on 2026-06-16 and joined the PMC on 2026-07-22. This is the direct result of
the deliberate effort we described in our last report to broaden the active
base, and it moves us off the bare minimum we were operating at.
We remain candid that the active base is still small, and one addition does
not by itself resolve the sustainability question. We are continuing the
conversation within the PMC and continue to watch the StormCrawler community
and other downstream users for contributors who demonstrate sustained
engagement, with the intent to invite them.
Mailing list and issue tracker traffic remain low but healthy for a project in
maintenance mode, and we continue to see a welcome level of external
contributions.
-----------------------------------------
Attachment CG: Report from the Apache StreamPark Project [Huajie Wang]
-----------------------------------------
Attachment CH: 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 (19 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:
- No new PMC members. Last addition was Thisara Weerakoon on 2026-05-18.
- No new committers. Last addition was Thisara Weerakoon on 2025-12-29.
## Project Activity:
The project has been working towards the Synapse 3.0.3 release. The release
process was started during the quarter but had to be postponed due to bugs
identified during the release process. Several security issues were also
reported around the same time. The community is currently working on
addressing these issues, with the goal of completing the fixes and proceeding
with the 3.0.3 release.
The project also received the GLASSWING security scanning report and is
currently analyzing the findings and working on addressing the identified
issues. Security fixes and release preparation are currently the main areas of
development activity.
## Community Health:
Community activity has been focused primarily on release preparation, bug
fixing, and addressing security issues. Despite the postponement of the
release, the community continues to actively work on resolving the identified
issues and improving the project's security posture.
-----------------------------------------
Attachment CI: 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:
rivet.3.3.0 was released on 2026-07-30, which supports Tcl 9.x and Tcl 8.6.
Then, on 2026-09-05 rivet-3.3.1 was released, which contains fixes for a few
incompatibilities that emerged as Tcl9 channels don't accept -encoding binary
as option and this breaks uploading files to channels. A test was added to
check this sort of regressions.
## Community Health:
The mailing lists have been more active than usual in this reporting period,
mainly due to the two releases and some usage questions related to porting
code from Tclhttpd to Apache/Rivet.
-----------------------------------------
Attachment CJ: 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 moderate activity. Since the last report the community
focused on API hardening of the TrustZone SDK (typed parameter API,
session-lifetime fixes, safer shared-memory access), refreshed the Rust
toolchain for std TAs, improved developer tooling (cargo-optee), and prepared
the project repositories for the ASF GLASSWING security scanning program.
## Summary of Project Health and Status
Development continued at a steady pace, concentrated on the TrustZone SDK. No
release was cut this period; the next release will track the upcoming OP-TEE
4.11 release (OP-TEE 4.10.0 remains the latest upstream release).
Contributions came from existing committers and from an organizational
contributor (Amlogic). The project is prepared for GLASSWING security scanning
(security-model documentation, AGENTS.md discoverability files,
branch-protection rulesets across repositories) and is awaiting scan results
to review.
## 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) No new
releases this period.
## Project Activity
### Development Activity
- TrustZone SDK: 11 PRs merged (17 commits) since last report.
- Introduced a typed parameter API (`FromRawParameter`) with a migration
guide, replacing raw parameter handling in all examples and projects.
- Hardened the TA session model: fixed session parameter lifetime issues and
enforced session context type consistency at the macro level.
- Improved safety of memref shared-memory access; an opaque copy-in/copy-out
MEMREF API is agreed as the follow-up direction (issue #273).
- Refreshed the std TA toolchain to Rust nightly-2026-08-05 (Rust 1.99 ported
std/libc in teaclave-crates), resolving a long-standing HashSet
write-permission fault.
- Refactored crates to hide low-level OP-TEE dependencies behind a prelude,
centralized workspace dependencies, and reorganized examples into TA and CA
workspaces.
- cargo-optee: added support for standard OP-TEE environment paths; further
CLI and toolchain-management improvements are planned.
- Enhanced Object APIs (private REE/RPMB storage constants) contributed by
Amlogic.
### Community Activity
- Developer mailing list: ~55 messages across ~20 threads since 2026-06-18,
mostly code-review traffic.
## Current Plans
Short term (next quarter):
- Cut the next release aligned with OP-TEE 4.11 once it ships.
- Land the opaque copy-based MEMREF API and finish boundary-safety hardening.
- Continue cargo-optee improvements (cargo-transparent CLI, toolchain
management).
- Review and triage GLASSWING scan results; follow up on findings.
Medium term:
- Open source additional real-world SDK use cases.
- Maintain alignment with OP-TEE's quarterly release cadence.
## Community Changes
- No new PMC members or committers this period (last PMC addition: April
2026).
- 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.
-----------------------------------------
Attachment CK: 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 native 1.3.8 was released on 2026-06-15.
Tomcat native 2.0.15 was released on 2026-06-15.
Tomcat 9.0.119 was released on 2026-06-23.
Tomcat 10.1.56 was released on 2026-06-23.
Tomcat 11.0.23 was released on 2026-06-22.
Tomcat 9.0.120 was released on 2026-07-07.
Tomcat 10.1.57 was released on 2026-07-07.
Tomcat 11.0.24 was released on 2026-07-08.
Tomcat 9.0.121 was released on 2026-08-18.
Tomcat 10.1.59 was released on 2026-08-20.
Tomcat 11.0.25 was released on 2026-08-18.
Tomcat native 1.3.9 was released on 2026-09-17.
Tomcat native 2.0.16 was released on 2026-09-17.
We have a "Security Day" planned the day after the Community Over Code
conference in Glasgow with an expected attendance of 4 Security Team members
(3 in-person, 1 remote) and two guests (from ASF Security).
## Community Health:
Continued healthy activity across multiple sub-projects and responsiveness on
both dev and user lists.
-----------------------------------------
Attachment CL: Report from the Apache TsFile Project [Jialin Qiao]
## Description:
The mission of Apache TsFile is the creation and maintenance of software
related to a columnar storage file format designed for time series data
## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: No.
## Membership Data:
Apache TsFile was founded 2023-11-15 (2 years ago) There are currently 21
committers and 18 PMC members in this project. The Committer-to-PMC ratio is
7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Gaofei Cao on 2023-11-15.
- No new committers. Last addition was Xinhao Gu on 2025-04-22.
## Project Activity:
### Recent releases:
- 2.4.0 was released on 2026-07-23.
- 2.3.1 was released on 2026-06-01.
- 2.3.0 was released on 2026-04-27.
### Main work of project:
This quarter, the project focused on improving performance, stability and
usability across the Java, C++ and Python implementations. TsFileDataFrame
gained support for tree-model files, and the C++ read, write and
metadata-query paths were optimized. Several cross-language compatibility,
large-file writing, null handling and memory issues were also fixed.
The project also added command-line tools for inspecting and importing TsFile
files, improved CSV, Parquet and Arrow conversion, and strengthened Windows
and Python build support.
## Community Health:
dev@tsfile.apache.org had an 80% increase in traffic in the past quarter (63
emails compared to 35).
Overall community health remains good. Development continued across the Java,
C++, Python and tooling areas. No community-health concerns require the
Board's attention.
As a follow-up to the previous quarterly report, the pull request adding
TsFile support to Hugging Face Datasets[1], which was awaiting review at that
time, was merged on 2026-06-01. This allows users to load `.tsfile` files
through the Datasets library and is a positive sign of adoption in the
machine-learning ecosystem.
[1] https://github.com/huggingface/datasets/pull/8160
-----------------------------------------
Attachment CM: 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 31 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 Yaxing Cai on 2026-06-07.
- No new committers. Last addition was Akaash Raghunathan Parthasarathy on
2026-05-05.
## Project Activity:
Recent releases:
- tvm v0.26 was released on 2026-08-11
- tvm-ffi v0.1.13 was released on 2026-07-30.
The community continues to bring improvement and refactoring to modularize the
components to enable lightweight kernel compilations.
- TIRx support for frontier GPU programmings
- Modularization to make IR nodes more reusable
- Experimentation of rust interop support
## Community Health:
We see continued contributions to the project, with about 100 commits monthly
in the past quarter. We are seeing a trend of more AI changes, so it is
important to think about clean architecture and modularization boundaries.
The community continue to move toward the next component goal on bringing
minimal components for FFI and low-level LLVM code generation integration.
-----------------------------------------
Attachment CN: 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 26 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Giuseppe Abrami was added to the PMC on 2026-08-05
- Giuseppe Abrami was added as committer on 2026-08-05
## 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.
* progress towards uimaj 3.7.0 coming along slowly but steadily
## Community Health:
There has not really been any particularly notable or significant
activity to report.
-----------------------------------------
Attachment CO: 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, high activity
Issues for the board: none
## Membership Data:
Apache Unomi was founded 2019-02-20 (8 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:
3.0.1 was released on 2026-07-20 (RM: Jonathan Sinovassin-Naïk; 5 binding
PMC +1). Work is now on 3.1.0 (multi-tenancy, OpenSearch 3, V2 API
compat, platform upgrades). The feature epic is closed; remaining test
and review issues are being fixed before a vote.
We received security reports from two independent researchers and from
the Anthropic Glasswing project. Fixes are in progress and will ship in
upcoming releases via the usual ASF process.
Recent releases:
3.0.1 was released on 2026-07-20.
3.0.0 was released on 2025-11-10.
2.7.0 was released on 2025-09-02.
## Community Health:
The Board reviewers asked in June whether Unomi is a one-person project. We take
that seriously. Serge Huber is putting most of his time into getting
3.1.0 out the door (integration, testing, and issues found in that
process). Once it ships he is expected to be much less active. In the
meantime others keep contributing at a regular pace: Jonathan
cut 3.0.1 (five PMC +1 votes), and Jérôme landed the 3.0.1 fix and has
an active 3.1 PR. Monthly meetings continued (minutes on-list).
Growing the community is a PMC focus. We plan more on-boarding work,
including website improvements, and better use of ASF public channels
(press@ / announcements). Getting users onto the mailing lists remains
hard: they prefer Slack or JIRA.
dev@unomi.apache.org had a 559% increase in traffic in the past quarter
(1101 emails compared to 167), mostly GitHub/JIRA/git notifications from
the 3.1 landing.
41 JIRA tickets opened and 65 closed in the past quarter.
-----------------------------------------
Attachment CP: 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
- Though it is not reflected in commits yet, work has started to identify what
features have been added at NCSU's installation of VCL that need to get
committed to the project for a new release to be made.
## Community Health:
Though there is no noticable activity from our lists, the project is still
being used and being monitored for any issues that should arise.
-----------------------------------------
Attachment CQ: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
The mission of Velocity is the creation and maintenance of software related to
A Java Templating Engine
## Project Status:
Current project status: Ongoing, Low Activity
Issues for the board: None
## Membership Data:
Apache Velocity was founded 2006-10-24 (20 years ago)
There are currently 16 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Claude Warren on 2026-04-12.
- No new committers. Last addition was Claude Warren on 2026-04-13.
## Project Activity:
Work progresses slowly toward an Engine 2.5 release.
There has been a recent uptick in PRs and security reports.
None of those are critical, as all require trusting 3rd party templates.
But one of us devs needs to make some time to address them, even if
it holds up the 2.5 release further.
## Community Health:
We're still a small crew with only a subset of those watching and weighing in
actually working on the code with any meaningful frequency. Recent contributors
should probably be groomed and encouraged toward becoming committers.
-----------------------------------------
Attachment CR: 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
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, as a result of the massive adoption of AI based tools, we
also received several security related report that lead to a corresponding CVE.
We handled most of them with the 3 releases of this quarter:
- 10.11.0 released on 2026-08-30.
- 8.19.0 released on 2026-08-30.
- 9.24.0 released on 2026-08-30.
Both the number of CVEs and the productivity boost we experienced with AI tools
have lead our team to consider a new fixed release schedule and a new versions
support policy for Wicket. We still debating on the details of it but we all
agree on producing new release more often to make Wicket more active and up to
date with the new Java releases.
As a consequence we are also planning to release Wicket 11 in the very next
months, possibly on October or November.
Speaking about our old X account we are trying to regain, unfortunately we still
stuck with no account credentials. We managed to reconnect with the original
owner (Francois Meillet) but we didn't have a feedback on our credentials
request yet.
If ASF could help us contacting X to solve this problem it would fantastic
(thank you in advance).
## Community Health:
After the virtual meetup of June community engagement has definitely grown,
partially (again) because of the widespread adoption of AI.
We have seen more PR than usual and we intensified the interaction of our core
team using Slack both for chatting and for virtual meetings.
-----------------------------------------
Attachment CS: 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 Xerces-C have had recent
activity.
Issues for the board: none
## Membership Data:
Apache Xerces was founded 2005-02-22 (22 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. Activity for Xerces-J continues to be on modernization of tests
to JUnit and improvements to the build automation. Several PRs have been
reviewed and merged for these tests. A member of the community started a
broader discussion about modernizing Xerces-J, including conversion of the
build from Ant to Gradle. This individual has been helping with PR reviews and
may be a good candidate for committer status. Some recent commits have been
made to Xerces=C to address bugs and potential security issues and it appears
there is intent to have a 3.3.1 patch release that would include these fixes.
## 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 recently had
a roll call on the Xerces-C PMC members to check for signs of life and received
immediate responses from two of the more previously active PMC members with
their intent to continue contributing.They have since responded to security
reports and have committed some fixes to GitHub. Without new developers there
will come a time to retire the project but we are not there yet.
-----------------------------------------
Attachment CT: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Yetus was founded 2015-09-15 (11 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
Summer doldrums as usual and so not much happening as we have all been
distracted with our responsibilities.
## Community Health:
The project is still in use by lots of projects and very stable. We have PMCs
around and still intend to get a release out. Hopefully over the next
quarter.
-----------------------------------------
Attachment CU: 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 35 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.
- Dávid Paksy was added as committer on 2026-08-06
## Project Activity:
Releases 3.9.6 and 3.8.7 are currently being voted:
https://lists.apache.org/thread/tof0vxjqwcq97nlpck7xc509q6tg5vnt
https://lists.apache.org/thread/k924xh7q914od7o65w13rh2smgcrf0gj
## Community Health:
The activity observed in the project has been around the preparation
of the upcoming releases. There has been a decrease in project traffic in the
last quarter, perhaps due to the summer months which tend to be more quiet. We
have also added one new committer, and as usual, we are looking for more
candidates to mentor and to extend committership.
------------------------------------------------------
End of minutes for the September 16, 2026 board meeting.