Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
August 20, 2025
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:00 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones:
http://www.timeanddate.com//worldclock/fixedtime.html?iso=2025-08-20T21: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:
Rich Bowen
Zili Chen
Shane Curcuru
Jim Jagielski
Justin Mclean
Jean-Baptiste Onofré
Sander Striker
Kanchana Pradeepika Welagedara
Directors Absent:
Greg Stein
Executive Officers Present:
Craig R. McClanahan
Craig L Russell
Matt Sicker
Ruth Suehle
Executive Officers Absent:
Jeff Jirsa
Guests:
Alin Jerpelea
Andrew Wetmore
Brian Proffitt
Daniel Gruno
Daniel Sahlberg
Dave Fisher
Jarek Potiuk
Julien Le Dem - joined :03
Melissa Logan - joined :05
Niall Pemberton
Paul Irwin
Paul King
Sally Khudairi
Thomas Neidhart
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of July 16, 2025
See: board_minutes_2025_07_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
This month I've seen the term summer vacation more than a few times. I'm
definitely seeing impact of being out for a bit; it takes more effort to catch
up. I also note that we seem to have a few more missing reports, and notably
more reports that didn't receive enough pre-approvals at the day of the
meeting.
I've been able to use the board agenda tool for all my interactions this
month, which is great. I'm looking forward to creating next months agenda
with it too.
B. President [Ruth Suehle]
I want to underline a note from the Conferences report regarding the hotel for
Community Over Code NA. The hotel unfortunately filled for the night of September
10. That relieves us of our financial obligation for that night, but not for
the rest of the room block. This means that if people don't stay in the
conference hotel because they could not book that first night, we will owe the
hotel money for not fulfilling our block.
I know it is a huge inconvenience to change hotels, but it is also a huge
favor to the Conferences budget. If you have not booked your room yet, you
have until August 20 to help us out with the room block, but you will have to
stay nearby for the night of September 10. My recommendation if you do so would
be to come with your bags on Thursday morning and check them with the front
desk of the Hyatt. If anybody has any questions about doing so, please feel
free to message me directly or the #communityovercode channel in Slack, and I
am happy to help. The foundation's budget, Conferences, and I appreciate your
help!
***Edited to add 8/19: This morning the Hyatt has extended our room block to
August 27 to buy us a bit more time and is doing their best to support us in
trying to get to our numbers.
Directly after that event, I'll be participating on the ASF's behalf in the
third Open Source Congress. It is now being organized collaboratively by the
participating foundations with a new structure. Day 1 will be only for
non-profit open source foundations leadership. Day 2 is a Stakeholder Day,
open to industry participants, public policy bodies, and anyone else in the
open source ecosystem. I'll be moderating a panel on Sustainability and the
Open Ecosystem on day 1.
Notes of thanks and kudos, which is not at all to minimize a lot of good Big
Work going on, but a couple of Smaller Things that are super helpful and
important as well:
- Mark T, working on finding a replacement for a swag store--this is
time-consuming, and I know some of the vendors have been frustrating!
- Chris L for updating and consolidating our Zoom accounts, helping everyone
have smoother meetings.
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig R. McClanahan]
As reported last month, I have provided detailed Ramp Card transactions to
people who manage "Departments" (as Ramp calls them). I've heard from and
worked with a few such people, but not very many, so nothing significant to
report on progress here.
However, recent enhancements to Ramp's APIs now allow me to build reports for
transactions that have been charged to an account within your account range,
no matter whose card was used to do that. Given the concerns earlier this
year about "mischarged expenses", I would hope people responsible for expense
areas would be interested in that. Let me know if you are indeed interested.
D. Secretary [Matt Sicker]
In July, the secretary received 47 ICLAs, 4 CCLAs, and 3 software
grants.
E. Executive Vice President [Jeff Jirsa]
Nothing material to report.
F. Vice Chair [Rich Bowen]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Zili]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / JB]
See Attachment 13
C. Apache Security Team Project [Mark J. Cox / Shane]
See Attachment 14
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Brand Management [striker]
# Celix [jim]
# Incubator [jim]
# Logo Development [striker]
# MADlib [jim]
# Marketing and Publicity [striker]
# Traffic Control [rbowen]
# Velocity [rbowen]
A. Apache AGE Project [Jeff Jirsa / Jim]
See Attachment A
B. Apache Ambari Project [Brahma Reddy Battula / Kanchana]
See Attachment B
C. Apache Ant Project [Jan Materne / Rich]
See Attachment C
D. Apache Avro Project [Ryan Skraba / Justin]
See Attachment D
E. Apache BookKeeper Project [Enrico Olivelli / Greg]
No report was submitted.
F. Apache Brooklyn Project [Juan D. Cabrerizo / Sander]
See Attachment F
G. Apache BuildStream Project [Tristan Van Berkom / Zili]
No report was submitted.
H. Apache CarbonData Project [Jacky Li / JB]
No report was submitted.
@Jean-Baptiste: pursue potential Attic for CarbonData
I. Apache Cassandra Project [Dinesh Joshi / Shane]
See Attachment I
J. Apache Celeborn Project [Keyong Zhou / Kanchana]
See Attachment J
K. Apache Celix Project [Pepijn Noltes / Rich]
See Attachment K
L. Apache Community Development Project [Swapnil Mane / Rich]
See Attachment L
M. Apache CouchDB Project [Jan Lehnardt / Jim]
See Attachment M
N. Apache Creadur Project [Philipp Ottlinger / Greg]
See Attachment N
O. Apache DataFu Project [Eyal Allweil / Sander]
See Attachment O
P. Apache DataSketches Project [Lee Rhodes / Justin]
See Attachment P
Q. Apache DeltaSpike Project [Mark Struberg / JB]
See Attachment Q
R. Apache Doris Project [Mingyu Chen / Justin]
No report was submitted.
S. Apache Drill Project [Charles Givre / Kanchana]
See Attachment S
T. Apache Empire-db Project [Rainer Döbele / Zili]
See Attachment T
U. Apache EventMesh Project [Eason Chen / Sander]
No report was submitted.
V. Apache Flex Project [Harbs / Rich]
See Attachment V
W. Apache Fory Project [Chaokun Yang / Greg]
No report was submitted.
X. Apache FreeMarker Project [Dániel Dékány / Shane]
See Attachment X
Y. Apache Geode Project [Mark Bretl / Jim]
No report was submitted.
Z. Apache Geronimo Project [Jean-Louis Monteiro / Sander]
No report was submitted.
AA. Apache Gravitino Project [Jerry Shao / Rich]
See Attachment AA
AB. Apache Griffin Project [William Guo / Sander]
No report was submitted.
AC. Apache Groovy Project [Paul King / Jim]
See Attachment AC
AD. Apache Hop Project [Hans Van Akelyen / Zili]
No report was submitted.
AE. Apache HTTP Server Project [Joe Orton / Greg]
See Attachment AE
AF. Apache HttpComponents Project [Michael Osipov / Kanchana]
No report was submitted.
AG. Apache Ignite Project [Dmitry Pavlov / Shane]
See Attachment AG
AH. Apache Impala Project [Zoltán Borók-Nagy / Justin]
See Attachment AH
AI. Apache Incubator Project [Justin Mclean / Sander]
See Attachment AI
AJ. Apache Johnzon Project [Jean-Louis Monteiro / JB]
No report was submitted.
AK. Apache Juneau Project [James Bognar / Shane]
No report was submitted.
AL. Apache Kafka Project [Mickael Maison / Kanchana]
See Attachment AL
AM. Apache Kibble Project [Sharan Foga / Rich]
See Attachment AM
AN. Apache Knox Project [Larry McCay / Sander]
No report was submitted.
AO. Apache Kylin Project [Li Yang / Justin]
See Attachment AO
AP. Apache Libcloud Project [Tomaž Muraus / Justin]
No report was submitted.
AQ. Apache Logging Services Project [Piotr Karwasz / Greg]
See Attachment AQ
AR. Apache Logo Development Project [Daniel Gruno / Sander]
See Attachment AR
AS. Apache Lucene.Net Project [Shad Storhaug / JB]
See Attachment AS
AT. Apache MADlib Project [Ed Espino / Zili]
See Attachment AT
AU. Apache ManifoldCF Project [Piergiorgio Lucidi / Rich]
See Attachment AU
AV. Apache OpenWhisk Project [Dave Grove / Jim]
See Attachment AV
AW. Apache Ozone Project [Sammi Chen / Rich]
No report was submitted.
AX. Apache Perl Project [Steve Hay / Zili]
See Attachment AX
AY. Apache Phoenix Project [Istvan Toth / Sander]
See Attachment AY
AZ. Apache Pinot Project [Kishore G / Greg]
No report was submitted.
BA. Apache POI Project [Dominik Stadler / Jim]
See Attachment BA
BB. Apache Qpid Project [Robbie Gemmell / Justin]
See Attachment BB
BC. Apache Ratis Project [Tsz-wo Sze / Greg]
See Attachment BC
BD. Apache RocketMQ Project [Xiaorui Wang / Kanchana]
No report was submitted.
BE. Apache Roller Project [David M. Johnson / Shane]
See Attachment BE
BF. Apache Samza Project [Jagadish Venkatraman / Kanchana]
See Attachment BF
BG. Apache Santuario Project [Colm O hEigeartaigh / JB]
See Attachment BG
BH. Apache SDAP Project [Nga Thien Chung / Justin]
See Attachment BH
BI. Apache Sedona Project [Jia Yu / Greg]
See Attachment BI
BJ. Apache Serf Project [Daniel Sahlberg / Rich]
See Attachment BJ
BK. Apache ServiceComb Project [Bao Liu / Zili]
See Attachment BK
BL. Apache ShardingSphere Project [Liang Zhang / Jim]
See Attachment BL
BM. Apache ShenYu Project [Yu Xiao / Shane]
See Attachment BM
BN. Apache SIS Project [Martin Desruisseaux / Rich]
See Attachment BN
BO. Apache Solr Project [Alessandro Benedetti / Sander]
See Attachment BO
BP. Apache Spark Project [Matei Alexandru Zaharia / JB]
See Attachment BP
BQ. Apache StormCrawler Project [Richard Zowalla / Kanchana]
See Attachment BQ
BR. Apache StreamPipes Project [Philipp Zehnder / JB]
See Attachment BR
BS. Apache Subversion Project [Nathan Hartman / Zili]
See Attachment BS
BT. Apache Superset Project [Maxime Beauchemin / Kanchana]
See Attachment BT
BU. Apache Syncope Project [Francesco Chicchiriccò / Sander]
See Attachment BU
BV. Apache SystemDS Project [Matthias Boehm / Greg]
See Attachment BV
BW. Apache TomEE Project [David Blevins / Justin]
No report was submitted.
BX. Apache Traffic Control Project [Eric Friedrich / Shane]
See Attachment BX
@Zili: speak with PMC about moving to the Attic
BY. Apache Traffic Server Project [Bryan Call / Rich]
No report was submitted.
BZ. Apache TsFile Project [Jialin Qiao / Jim]
No report was submitted.
CA. Apache Turbine Project [Georg Kallidis / Justin]
See Attachment CA
CB. Apache Uniffle Project [He Qi / Kanchana]
See Attachment CB
CC. Apache Velocity Project [Nathan Bubna / JB]
See Attachment CC
@Jean-Baptiste: pursue a roll call for PMC
CD. Apache Web Services Project [Daniel Kulp / Shane]
No report was submitted.
CE. Apache Whimsy Project [Dave Fisher / Zili]
See Attachment CE
CF. Apache Xalan Project [Gary D. Gregory / Sander]
See Attachment CF
CG. Apache Xerces Project [Michael Glavassevich / Greg]
No report was submitted.
CH. Apache XML Graphics Project [Clay Leeds / Jim]
See Attachment CH
CI. Apache YuniKorn Project [Wilfred Spiegelenburg / Rich]
See Attachment CI
CJ. Apache IoTDB Project [Xiangdong Huang / Sander]
See Attachment CJ
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Steve Project Chair
WHEREAS, the Board of Directors heretofore appointed Daniel Gruno
(humbedooh) to the office of Vice President, Apache Steve, and
WHEREAS, the Board of Directors is in receipt of the resignation of Daniel
Gruno from the office of Vice President, Apache Steve, and
WHEREAS, the Project Management Committee of the Apache Steve project has
chosen to recommend Greg Stein (gstein) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Daniel Gruno is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Steve, and
BE IT FURTHER RESOLVED, that Greg Stein be and hereby is appointed to the
office of Vice President, Apache Steve, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7A, Change the Apache Steve Project Chair, was
approved by Unanimous Vote of the directors present.
B. Terminate the Apache Logo Development Project
WHEREAS, the Board of Directors deems it no longer necessary to continue the
Apache Logo Development project due to its objective having been completed;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Logo Development project is
hereby terminated; and be it further
RESOLVED, that the office of "Vice President, Apache Logo Development" is
hereby terminated; and be it further
RESOLVED, that the Apache Logo Development PMC is hereby terminated.
Special Order 7B, Terminate the Apache Logo Development
Project, was approved by Unanimous Vote of the directors
present.
C. Terminate the Apache Mesos Project
WHEREAS, the Project Management Committee of the Apache Mesos project has
chosen by vote to recommend moving the project to the Attic; andWHEREAS, the
Board of Directors deems it no longer in the best interest of the Foundation
to continue the Apache Mesos project due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Mesos 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 Mesos Project; and be it further
RESOLVED, that the office of "Vice President, Apache Mesos" is hereby
terminated; and be it further
RESOLVED, that the Apache Mesos PMC is hereby terminated.
Special Order 7C, Terminate the Apache Mesos Project, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Ant Project Chair
WHEREAS, the Board of Directors heretofore appointed Jan Materne (jhm)
to the office of Vice President, Apache Ant, and
WHEREAS, the Board of Directors is in receipt of the resignation of Jan
Materne from the office of Vice President, Apache Ant, and
WHEREAS, the Project Management Committee of the Apache Ant project has
chosen by vote to recommend Jaikiran Pai (jaikiran) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Jan Materne is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Ant, and
BE IT FURTHER RESOLVED, that Jaikiran Pai be and hereby is appointed to
the office of Vice President, Apache Ant, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7D, Change the Apache Ant Project Chair, was
approved by Unanimous Vote of the directors present.
E. Establish the Apache HertzBeat Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a real-time monitoring system with agentless,
performance cluster, prometheus-compatible, custom monitoring and
status page building capabilities.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache HertzBeat Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache HertzBeat be and hereby is responsible for
the creation and maintenance of software related to a real-time
monitoring system with agentless, performance cluster,
prometheus-compatible, custom monitoring and status page building
capabilities; and be it further
RESOLVED, that the office of "Vice President, Apache HertzBeat" 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
HertzBeat Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache HertzBeat
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 HertzBeat
Project:
* Francis Chuang <francischuang@apache.org>
* Chen Gao <gaochen@apache.org>
* Xingcun Gao <gaoxingcun@apache.org>
* Chao Gong <gongchao@apache.org>
* Dongdong Hu <hudongdong@apache.org>
* Hongyu Liu <liuhongyu@apache.org>
* Tianyou Liu <liutianyou@apache.org>
* Justin Mclean <jmclean@apache.org>
* Jianing Wang <jianingwang@apache.org>
* QingHua Wang <huacheng@apache.org>
* Xiangdong Zhang <xixihaha@apache.org>
* Yu Xiao <xiaoyu@apache.org>
* Shenghang Zhang <shenghang@apache.org>
* Yang Zhang <zhangyang2024@apache.org>
* Yonglun Zhang <zhangyonglun@apache.org>
* Qingran Zhao <zhaoqingran@apache.org>
* Chenxin Zheng <ceilzcx@apache.org>
* Shusheng Zhou <shushengzhou@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chao Gong be appointed to
the office of Vice President, Apache HertzBeat, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7E, Establish the Apache HertzBeat Project, was
approved by Unanimous Vote of the directors present.
F. Change the Apache NiFi Project Chair
WHEREAS, the Board of Directors heretofore appointed Joe Witt (joewitt)
to the office of Vice President, Apache NiFi, and
WHEREAS, the Board of Directors is in receipt of the resignation of Joe
Witt from the office of Vice President, Apache NiFi, and
WHEREAS, the Project Management Committee of the Apache NiFi project
has chosen by vote to recommend David Handermann (exceptionfactory) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Joe Witt is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache NiFi, and
BE IT FURTHER RESOLVED, that David Handermann be and hereby is
appointed to the office of Vice President, Apache NiFi, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7F, Change the Apache NiFi Project Chair, was
approved by Unanimous Vote of the directors present.
G. Establish the Apache Teaclave 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 SDKs for building memory-safe applications on Trusted
Execution Environments.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Teaclave Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Teaclave Project be and hereby is responsible
for the creation and maintenance of software related to SDKs for building
memory-safe applications on Trusted Execution Environments; and be it further
RESOLVED, that the office of "Vice President, Apache Teaclave" 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 Teaclave Project, and to have
primary responsibility for management of the projects within the scope of
responsibility of the Apache Teaclave 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 Teaclave Project:
* Duan Ran <rduan@apache.org>
* Furkan Kamaci <kamaci@apache.org>
* Gang Wang <garyw@apache.org>
* Hao Ding <xuanwo@apache.org>
* He Sun <hsun@apache.org>
* Mingshen Sun <mssun@apache.org>
* Pei Wang <uraj@apache.org>
* Rundong Zhou <rundongzhou@apache.org>
* Shaojun Wang <shaojunwang@apache.org>
* Tao Wei <lenxwei@apache.org>
* Tongxin Li <litongxin1991@apache.org>
* Willem Ning Jiang <ningjiang@apache.org>
* Yiming Jing <yjing@apache.org>
* Yu Ding <dingyu@apache.org>
* Yuan Zhuang <yuanz@apache.org>
* Yulong Zhang <yulongzhang@apache.org>
* Zhaofeng Chen <zfc@apache.org>
* Zili Chen <tison@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Zhaofeng Chen be appointed to the
office of Vice President, Apache Teaclave, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7G, Establish the Apache Teaclave Project, was
approved by Unanimous Vote of the directors present.
H. Establish the Apache Training 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 training
materials for Apache projects and the Apache Software Foundation;
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
be known as the "Apache Training Project", be and hereby is established
pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Training PMC be and hereby is responsible for the
creation and maintenance of software related to training materials for Apache
projects and the Apache Software Foundation; and be it further
RESOLVED, that the office of "Vice President, Apache Training" 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 Training Project, and
to have primary responsibility for management of the projects within the scope
of responsibility of the Apache Training 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 Training
Project:
* Justin Mclean <jmclean@apache.org>
* Rich Bowen <rbowen@apache.org>
* Andrew Wetmore <andreww@apache.org>
* Craig L Russell <clr@apache.org>
* Christofer Dutz <cdutz@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Justin Mclean be appointed to the
office of Vice President, Apache Training, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7H, Establish the Apache Training
Project, was approved by Unanimous Vote of the directors
present.
I. ASF Board Charter
WHEREAS, the members of the Board of Directors of The Apache Software
Foundation have reviewed the proposed ASF Board Charter;
WHEREAS, the Board recognizes that the Charter is a descriptive document
intended to clarify and document the roles, responsibilities, and operating
procedures of the Board;
WHEREAS, the Board acknowledges that the Charter reflects the current
practices and expectations of the Board as exercised in the fulfillment of its
duties under the Bylaws of The Apache Software Foundation;
NOW, THEREFORE, BE IT RESOLVED, that the Board of Directors hereby adopts the
ASF Board Charter as a non-binding but accurate reference on the Board’s
operations and governance practices;
BE IT FURTHER RESOLVED, that the Board may review and amend the Charter from
time to time, as needed, to ensure it remains accurate and aligned with the
evolving needs of the Foundation.
Special Order 7I, ASF Board Charter, was tabled.
J. Establish Position of Assistant VP, Marketing and Publicity
WHEREAS, the Board of Directors deems it to be in the best interests of the
Foundation and consistent with the Foundation's purpose to appoint an
Assistant Vice President, Marketing and Publicity;
NOW, THEREFORE, BE IT RESOLVED that the office of "Assistant Vice President,
Marketing and Publicity" be and hereby is created, the person holding such
office to serve at the direction of the President, and to share
responsibilities with and support the Vice President, Marketing and Publicity;
and be it further
RESOLVED, that Andrew Wetmore (andreww) be and hereby is appointed to the
office of Assistant Vice President, Marketing and Publicity, to serve in
accordance with and subject to the direction of the President
Special Order 7J, Establish Position of Assistant VP,
Marketing and Publicity, was approved by Unanimous Vote of the
directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Greg: broad reminder for PMC terminology
[ Pinot 2025-05-21 ]
Status:
* Jim: speak with VP Legal about reducing exposure to risk
[ Policies for Foundation internal venues 2025-05-21 ]
Status: Completed. COMPLETE (deferred to Justin, Rich and Jeff's CoC effort)
* Jim: coordinate with Portals PMC to find out more about potential Eclipse
[ Portals 2025-06-18 ]
Status: Completed. Will bring board up-to-speed at meeting
* Rich: pursue a roll call for SIS PMC
[ SIS 2025-06-18 ]
Status: Completed. Completed. SIS has reported and discussed their struggles.
* Matt: ensure Fluo is removed from schedule for reporting
[ Fluo 2025-07-16 ]
Status:
* Zili: follow up with IoTDB about branding issue
[ Brand Management 2025-07-16 ]
Status: Done.
The IoTDB PMC has made progress, and the remaining issues can be continuously addressed and reflected in the following report.
* Greg: clarify community overlap with Mifos and state of community
[ Fineract 2025-07-16 ]
Status:
* Sander: pursue Attic resolution for Griffin
[ Griffin 2025-07-16 ]
Status:
* Sander: start board discussion around Incubator
[ Incubator 2025-07-16 ]
Status: Done. Late, but started https://lists.apache.org/thread/mxhj5zbnrry6zy4v81272yfy59gl17r5
* Rich: follow up about Attic
[ Kibble 2025-07-16 ]
Status: https://lists.apache.org/thread/hvw4kr632klj3qygnkkonqcyb2s25nml
Will follow up as that conversation progresses.
Update: Even that thread has had insufficient responses to make a decision. I'll follow up with the project to put together an attic resolution.
* Kanchana: pursue Attic for Mesos
[ Mesos 2025-07-16 ]
Status: Mesos is in Attic, effort led by the PMC chair and there's an
resolution included in the agenda for this board meeting.
* Jim: ensure an Attic resolution is filed
[ Olingo 2025-07-16 ]
Status: Completed. COMPLETE (Email sent to Sander Aug 4)
* Kanchana: follow up with Samza about potential for Attic
[ Samza 2025-07-16 ]
Status: Summary: Samza missed reporting for consecutive months.
Following this, the board initiated a discussion to change the
PMC chair. Due to a lack of timely responses, and as an action
item from the last board meeting, we continued the
conversation. The PMC chair later reported a technical issue
with not receiving emails and justified the project’s active
status in this thread:
https://lists.apache.org/thread/khg1vy77d1hlhv4pwcvbll645tlq9npc
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 21:38 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period July 2025
* ISSUES FOR THE BOARD
None
* OPERATIONS
- While also wearing a ComDEv hat, worked on identifying possible replacements
for the ASF swag store. Doing this while also wearing the VP Brand hat
simplifies a lot of the "Do you have the rights to do this?" questions.
- Provided advice on creating a certification for CLOUDSTACK
- Denied an event request to use IOTDB mark due to date conflict with CoC
Asia.
- Approved a request to use the ARROW mark for an event
- Provided advice to STORMCRAWLER regarding registration
- Approved the use of the SUPERSET logo in a video
- Responded to a query regarding the purchase of swag
- Approved a request to use the NUTTX mark for an event
- Responded to a query regarding the use the Apache Web Server logo
- Responded to a query regarding the sale of physical copies of OPENOFFICE
- Approved a request to use the FLINK mark for an event
- Approved the name HERTZBEAT
- Approved (with VP Press & Marketing) a use of the ASF logo
- Provided naming advice to a vendor looking to integrate with SPARK
* REGISTRATIONS
Worked with counsel to maintain our CLOUDSTACK registration in the US.
The US registration for OpenOffice.org will be allowed to lapse.
Worked with counsel to renew our HBASE, cTAKES, MANIFOLDCF and TOMCAT
registrations in the US.
Worked with counsel and Baidu towards transferring BifroMQ to the ASF.
MADLIB has been renewed in China.
* INFRINGEMENTS
No further progress regarding the downstream vendor with multiple
infringements of ASF marks.
Continued progress regarding a potential infringement of PDFBOX. The most
serious issues have been addressed.
There has been some progress but some issues still remain for IOTDB.
Resolved various issues with references to projects in a China-based Open
Source Award listing.
Working with the DORIS PMC to resolve multiple issues.
Working with the XMLGRAPHICS PMC to resolve a potential infringement of FOP.
Worked with the GRAILS project on a potential infringement.
No progress resolving an issue with LOG4J usage.
No progress addressing some issues in a recent blog referencing CASSANDRA.
No progress regarding a potential infringement of KAFKA.
No further progress for the GROOVY PMC addressing a potential infringement in
a GitHub project.
No progress regarding a site with a possible infringement of APISIX.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we have secured a three-year commitment from a corporate contributor
who is donating the value of a Platinum Sponsorship each year. We are in the
process of onboarding the organization, and will recognize their contribution
(listed as a Sponsor, named or anonymous, etc.) according to their preference.
b —Renewals: we have secured renewal commitments from one Silver and one
Bronze Sponsor.
c —Payments: 1 —New: we received a Platinum-level corporate contribution.
2a —Renewing: we received a renewal payment from one Gold Sponsor.
2b —Incoming: we await payment from one Platinum, one Gold, and one Silver
Sponsor, plus payment for a partial Sponsorship-year (prior to their
mid-year renewal/upgrade).
2) Targeted Sponsors: we continue to explore options for recognizing
organizations that support ASF Projects (independently from our existing
Targeted Sponsor offerings).
3) Sponsor Relations: ongoing outreach and engagement; the Q3call with Gold
and Platinum Sponsors is scheduled to take place in mid-September. We issued
the second Fundraising blog post (first post: Sponsorship; second: Individual
Giving)
https://news.apache.org/foundation/entry/individual-donors-help-keep-apache-software-free-for-billions-of-users-worldwide
4) Event Sponsorship: Community Over Code North America is taking place 11-14
September; we are handling sponsorships and coordinating invoicing (bundled
sponsorship benefits for ASF Gold and Platinum Sponsors have been offered for
the first time) https://communityovercode.org/asf-sponsorship-discounts/ . We
await $76,500 in sponsorship payments for Community Over Code North America.
5) Individual Donations and Corporate Giving: we received $1,200 in individual
online donations via https://donate.apache.org/ .
6) Administrivia: we continue to successfully collaborate with the ASF
Treasury, Accounting, Events, and Marketing & Publicity teams.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Announcement
I am very pleased to announce that Andrew Wetmore has graciously accepted the
invitation to be the Asst VP, M&P, beginning this month. Andrew has been
working with the M&P team for the past few months, and his input and expertise
has proven invaluable!
Foundation Comms
* Issued July edition of Plus One newsletter promoting Community Over Code
Asia, new content on Apache.org, and Plus One podcast
* Coordinated fundraising awareness campaign with Fundraising team; promoted
first blog featuring quotes from Sentry and Visa
* Published blog thanking Myrle Krantz for her service as VP, Infrastructure
* Developed and published blog #14 in the #FirstASFContribution campaign
series to feature code writing contributions
* Brainstormed ideas for an Incubator awareness campaign
Project Comms
* Coordinated blog with Apache Airflow community detailing AI’s role within
open source for i18n project; pitched blog to The New Stack and published on
Apache.org as well as the ASF’s social media channels
Digital
* Continued coordination with infra team for self-hosting the Plus One
Newsletter vs. using the existing WordPress infrastructure
* Continuous optimization of Google Ads campaign for C/C NA
* Updated Apache.org banner to promote Community Over Code NA
Foundation Content
* Finalized social media offboarding workflow for Attic projects including
transfer of jclouds social accounts
* Began compilation of FY25 annual report and circulated written draft to
officers to ensure thoroughness and accuracy
* Facilitated a presentation by semiotics consultant so that ASF members could
understand the work done to inform logo design
* Finalized Sponsor Marketing Kit to help sponsors leverage their benefits;
published to wiki
Brand Project
* Engaged with semiotics consultant to review final logo choice from logo-dev
PMC
* Engaged with logo designer to finalize the word mark
* Developing Plus One logo for the podcast and newsletter
* Updated project action items and timeline including:
* Logo styling
* Brand narrative
* Website redesign
* Brand assets
* Brand book
* ASF Project Guidance
* Press release
* Brand blog
* New logo future campaign
Social Media Overview
The highest performing pieces of content for July include project release news
and a project spotlight blog featuring Apache Airflow and its use of AI.
Social Highlights (X + LinkedIn + Bluesky)
* Total Audience: 144,142
* New Followers in July: 598
* X: 79
* Bluesky: 66
* LinkedIn: 453
* Total Posts: 77
* X: 32
* Bluesky: 32
* LinkedIn: 13
* Total Engagements: 2,214
Website Analytics
* 745,712 visits, 745,616 unique visitors +8%
* 3 min 2s average visit duration -6.2%
* 59% visits have bounced (left the website after one page) +3.5%
* 6.2 actions (page views, downloads, outlinks, internal site searches) per
visit -1.6%
* 4,213,470 pageviews, 935,928 unique pageviews +7.4%
* 1 total searches on your website, 1 unique keywords -50%
* 164,896 downloads, 115,444 unique downloads +3.4%
* 253,197 outlinks, 183,726 unique outlinks -1.9%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Danny Angus]
General
=======
Infra has hired a new half-time contractor as of 5 August.
Issues with DKIM signing of outgoing mail became an emergent priority
due to Microsoft rejecting our email. Infra implemented a stopgap
solution to sign personal email sent via our mail relay system, e.g.
mail sent by an a.o account to an external entity. Considerable work
remains to apply a similar solution to outgoing mailing list traffic,
due to significant changes required to bring legacy ezmlm and qmail up
to modern standards. Infra continues to evaluate the scope and
timeline of the necessary changes.
Finances
========
A new hire will begin accruing expected expenses against the Infra
staffing budget.
MFA Efforts
===========
Infra, Security, and Tooling continue to coordinate on next steps. Per
prior report, we have evaluated Zitadel, which has a better UI/UX but
unfortunately no meaningful PAT support for our use case. We will
evaluate Authentik but it seems likely that our PAT support will need
to be self-developed. For clarity, PAT support is needed to support
per-service passwords, e.g. SVN, SMTP auth, and any authentication
layers which do not leverage a web browser UI.
Major Projects
==============
DKIM signing on outgoing personal (non-list) email has been completed.
ASF SVN has migrated to a new, upgraded system. Kudos to those who
worked on this and provided a nearly seamless cutover.
Dockerhub Self Service -- Infra is preparing to roll out self-serve
features for Dockerhub, including repo creation and team management.
Deployment has moved to late summer due to operational priorities
around upgrading SVN to support Tooling.
Testing is underway for a possible Jira and Confluence cloud
migration. See January/February board reports for further details
about this effort.
-----------------------------------------
Attachment 5: Report from the VP of Tooling [Dave Fisher]
# Tooling
The team continues to work hard building systems and playing well with others.
# Operations
## Apache Trusted Releases
We completed the initial Python CLI Client and Server API endpoints. We added
support for PAT and JWT Tokens. We adding Distribution Channel declaration.
Once that is done we will begin work on GitHub actions and will prepare for a
second Alpha round.
We will initially continue with an implicit identification of products
releases through the ATR.
## Board Agenda Tool
This month the new tool is being used for the whole Board Report cycle. We are
planning for the complete cycle through creating the September agenda.
## Secretary's Workbench
The repository is set up for the Secretary's workbench and later this month we
will review requirements and begin building the tool.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
In June, one potential gold sponsor withdrew, but in July another Gold sponsor
stepped in, as well as other lower-tier sponsors so we are pretty well covered
for revenue for this year's event.
We are managing the situation with the room block, especially on Night 1
(Sept. 10), which filled up rapidly, and cannot be expanded due to a very
oversold hotel that night (they are even diverting flight crews to other
hotels, which a big deal because those contracts are very solid money makers
for hotels). We continue to ask people to book at other locations for that
night, and then transfer to the venue hotel for the remaining nights, so we
don't risk losing money to attrition.
This, coupled with anecdotal evidence of un-approved travel visas, raises
concerns that we will not be increasing our attendance levels for the 2025
event vs. 2024. We are continuing to work with local companies and
universities to get more local people in the door on the days of the event.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Previous Events
===============
Community Over Code EU/Asia/NA 2024 Gavin still to finalize survey results.
Community Over Code Asia - Beijing July 2025
--------------------------------------------
7 people attended as TAC recipients, mainly from China and Taiwan. A great
success by all accounts, the organizers were happy with their level of
assistance during the event.
The TAC Dinner the night before the event start as usual was well received -
the TAC attendees getting to mix with board members, TAC Committee, and
Incubator Chair.
A very well run event, TAC attendees also received a volunteer recognition
award which was a nice touch.
Current Events
==============
Community Over Code NA
------------------------
Everything is about ready. One or two final flights to be done if Visas are
approved in the next week or so. Hotels are confirmed booked.
Liaise with the Organisers begins now to define the scope of help they need
this year.
Monthly Meetings
================
The next meeting is planned for the first week of September.
TAC App
=======
TAC app is currently closed.
Future Events
=============
None currently.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support. Post surveys for
Bratislava, Hangzhou, Denver and Beijing still to be done.
Mailing List Activity
=====================
Judges call notification but nothing else this month.
Membership
==========
No changes to the Committee this month.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
D&I bids a hearty welcome to Chris Wells, who joined the committee on July
31st.
An offspring of the 2025 jump-start document[1], the IDEA initiative, has been
kicked off with an introductory preamble on the public dev mailing list[2].
The purpose of this is to outline the basic premise for gathering and
circulating information and ideas for future work in a format that will
hopefully ensure a steady cadence and equal time, effort, and attention on
various areas that comprise the larger D&I field. The initial response has
been positive and constructive, which is always a joy to behold.
In parallel to getting these first conversations up and running, we are
exploring open-source, privacy-aware options for conducting surveys and
supplying training material in anticipation of the data gathering and
disseminating that many of these conversations will result in. I hope the
experience gained from this can be applied more widely to the foundation and
act as a framework for other areas of the foundation wanting to utilize
similar tools.
[1] https://cwiki.apache.org/confluence/display/EDI/2025+EDI+jumpstart+plan
[2] https://lists.apache.org/thread/lo792r8hqwkoy68kcf3753o3dp8l17fq
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
All quiet on the Eastern front.
And still plenty of concern and widespread unhappiness about the specification
processes and (lack of) progress at the normative standards bodies (CENELEC,
ETSI) -- and the fact that these are pretty much inaccessible to open source
concerns (and despite the CRA requiring OSS to be included) with all sorts of
artificial hurdles thrown in.
Nothing that to report that needs board level action this month.
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
There were no significant developments in ECMA TC54 this month.
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are
slightly up at 22 outstanding issues in the LEGAL JIRA.
Secretary reached out requesting clarifications around University of
California Release of Rights for the codebase related to the Apache Texera
(Incubating) and we provided the needed guidance on accepting the code.
Additionally we provided guidance to the Secretary on receiving official
documents from the Ant group (China).
I have presented in the Apereo MicroConference on the Generative AI Tool
guidance that was developed at the ASF.
One of the Subpoenas we were working on reached a milestone with the
litigating counsels receiving all the information they requested from us.
Nothing else to do here (and no additional involvement from the DLA Piper
required).
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
July
* We continue to work with projects to define their security model, this month
Baremaps, RocketMQ and traffic server
* Improved tooling to associate new and historical messages with security
issues
* Helped Zeppelin refine their security model, which will make triage and
follow-up much easier going forward.
Stats for July 2025:
45 [license confusion]
24 [support request/question not security notification]
10 [report/question relating to dependencies]
Security reports: 119 (last months: 77, 80, 63)
11 ['dolphinscheduler']
11 ['website or other infrastructure']
9 ['airflow', 'pinot']
8 ['superset']
6 ['httpd', 'tomcat']
5 ['sedona']
4 ['brpc', 'cloudstack', 'logging', 'streampark']
3 ['ofbiz', 'spark']
2 ['beam', 'commons', 'hertzbeat', 'nifi', 'zeppelin']
1 ['apisix', 'arrow', 'doris', 'druid', 'flink', 'groovy', 'guacamole', 'jackrabbit', 'netbeans', 'openoffice', 'pulsar', 'seata', 'shenyu', 'skywalking', 'solr', 'stormcrawler', 'struts', 'tapestry', 'thrift', 'tika', 'trafficserver', 'uniffle']
In total, as of 1st August 2025, we're tracking 234 (last months: 194, 214)
open issues across 78 projects, median age 89 days (last months: 115, 97). 62
of those issues have CVE names assigned. 27 (last months: 21, 17) of these
issues, across 13 projects, are older than 365 days.
* geode (Health red): Four issues in Geode over 365 days old. The project has
voted to move to the Attic, but there might be a chance of revisiting that
decision if relevant stakeholders successfully join the effort. (Last
update: 2025-08-01)
* openoffice (Health red): Several issues in OpenOffice are over 365 days old.
They are not severe enough to warrant stopping distribution of OpenOffice,
and there is progress on finding an architectural improvement to fix them,
but we actively work to improve the projects' ability to respond to
security issues going forward. (Last update: 2025-08-01)
* fineract (Health amber): the PMC has been attempting to engage more of the
wider Fineract ecosystem to help triage, fix and release security issues,
but with limited effect so far. (Last update: 2025-06-26)
* spark (Health amber): the project is not responsive to security issues (Last
update: 2025-08-01)
-----------------------------------------
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: Ongoing, but low activity
Issues for the board: None at this time
## Membership Data:
Apache AGE was founded 2022-05-17 (3 years ago)
There are currently 19 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.
- No new committers. Last addition was Jeff Jirsa on 2025-05-12.
## Project Activity:
In May, the board report noted that the project continues to have reduced
activity when compared to the same period Year-over-Year. However, the first
commits to the primary branch since last September landed in May, and have
accelerated in August.
## Community Health:
There are still few organic contributions from non-committers from which to
expand the pool of contributors, but the merging of AGE for Postgres 17 (
PR #2197 ) was a widely requested community feature and should be of
significant benefit for users.
-----------------------------------------
Attachment B: Report from the Apache Ambari Project [Brahma Reddy Battula]
## Description:
The mission of Apache Ambari is the creation and maintenance of software
related to Hadoop cluster management
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Ambari was founded 2022-06-15 (3 years ago)
There are currently 22 committers and 19 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 Jialiang Cai on 2025-04-26.
- No new committers. Last addition was Yu Zhang on 2025-02-20.
## Project Activity:
Recent releases:
3.0.0 was released on 2025-04-06.
2.7.9 was released on 2024-12-20.
2.7.8 was released on 2024-02-01.
## Community Health:
Community health little slow,But Actively working upon the Ambari UI
-----------------------------------------
Attachment C: Report from the Apache Ant Project [Jan Materne]
## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build
system and related software components.
It consists of the following main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
## Project Status:
Current project status: Primarily in bug fix mode and maintenance mode.
Issues for the board: None for now.
## Membership Data:
Apache Ant was founded 2002-11-18 (22 years ago)
There are currently 29 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Magesh Umasankar on 2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-15.
Our current PMC chairman Jan Materne has expressed his desire to step
down from this role. We want to thank Jan for his service over the past
years. The Ant PMC internally discussed the proposal to change the PMC
chair and decided to nominate Jaikiran Pai as the new PMC chair.
A new agenda item to change the Ant PMC chair has been added to the
upcoming board meeting agenda.
## Project Activity:
The primary goal of Ant these days is to make sure that it can be used
to build projects using recent releases of Java. Ant 1.10.15 was
released on 29th August 2024 and that's our latest version of Ant.
Ivy 2.5.3 has been released on 23rd December 2024 which is our latest
version of Ivy.
Both Ant and Ivy have seen some development activity this quarter but
right now no new release has been discussed.
## Community Health:
Although we don't see too much development activity in Ant,
there are several active users of the Ant build tool. We
occasionally also see pull requests on GitHub.
For a project that's in maintenance mode, our amount of
activity, we believe, is decent.
Thanks to Maarten Coene, who is part of the Ant PMC and who volunteered
to keep Ivy project alive, the project has seen some new activity in the
recent weeks. We also have a new contributor Eric Milles who has been
contributing bug fixes in the Ivy project in the recent weeks.
-----------------------------------------
Attachment D: Report from the Apache Avro Project [Ryan Skraba]
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema-driven serialized data. The unique
features of Avro include automatic schema resolution: when the reader's
expected schema is different from the actual schema with which the data was
serialized the data is automatically adapted to meet reader's requirements.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Avro was founded 2010-04-21 (15 years ago) There are currently 40
committers and 27 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 Oscar Westra van Holthe - Kind on
2024-08-27.
- Christiaan Biesterbosch was added as committer on 2025-08-04
## Project Activity:
There were two releases of the Avro Rust SDK this quarter. Having a separate
repository and release cycle makes it easier for the active Rust developers in
the project to provide timely features and fixes, so it was a good choice. The
other language SDKs are still released in one big process. We've accumulated
bug and security fixes, and it is increasingly important that our current
releases (1.12.0 and 1.11.4 in August 2024 last year) are updated. Since the
release process is so involved, we need to make sure we have good support for
the committers doing the release.
## Community Health:
Mailing Lists:
- dev@avro.apache.org had 315 emails (-7% change)
- issues@avro.apache.org (mostly notifications) had 509 emails (-20% change)
- user@avro.apache.org continues to have very little traffic, 11 total
JIRA:
- 43 issues opened (+104% change)
- 27 issues closed (+92% change)
Code Repository:
- 72 commits in the past quarter (+1% change)
- 25 code contributors in the past quarter (+66% change)
GitHub:
- 74 PRs opened on GitHub, past quarter (+4% change)
- 81 PRs closed on GitHub, past quarter (-3% change)
Activity is in line with our expectations.
-----------------------------------------
Attachment E: Report from the Apache BookKeeper Project [Enrico Olivelli]
-----------------------------------------
Attachment F: Report from the Apache Brooklyn Project [Juan D. Cabrerizo]
## Description:
The mission of Apache Brooklyn is the creation and maintenance of software
related to a software framework for modeling, monitoring and managing cloud
applications through autonomic blueprints.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Brooklyn was founded 2015-11-18 (10 years ago)
There are currently 20 committers and 19 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 Iuliana Cosmina on 2021-06-04.
- No new committers. Last addition was Mykola Mandra on 2022-03-08.
## Project Activity:
During the last reporting period, the project experienced low activity.
## Community Health:
The team remains available to provide support, and occasional discussions
continue on the mailing list. Two unannounced Jira account requests prompted
us to decide to remove the project-specific account request form in order to
prevent spam.
-----------------------------------------
Attachment G: Report from the Apache BuildStream Project [Tristan Van Berkom]
-----------------------------------------
Attachment H: Report from the Apache CarbonData Project [Jacky Li]
-----------------------------------------
Attachment I: Report from the Apache Cassandra Project [Dinesh Joshi]
Are you able to provide adequate oversight of your project? That is, are there
at least three PMC members who are engaged enough to respond in the event of a
CVE or similar crisis?
Yes. There are many PMC members actively participating in dev and private list
conversations.
Are there current or upcoming risks that threaten the sustainability of your
project? This could be anything from a change in employment of prolific
contributors, to an acquisition affecting a significant corporate contributor,
to a change in the technology landscape that makes your project less (or more)
relevant.
No current or upcoming risks known at this time. We are continuing to see
robust new contributions coming in from diverse corporate contributors. The
PMC has been considering several new individuals for Committer and PMC roles.
There are active discussions out. Of note, the project also released the first
version of the Cassandra Sidecar and Cassandra Analytics sub-projects. These
sub-projects have attracted new contributions from contributors with diverse
corporate backgrounds.
What can the Foundation do to more effectively make your project more
successful in its mission of providing software for the public good?
None at this time.
-----------------------------------------
Attachment J: Report from the Apache Celeborn Project [Keyong Zhou]
## Description:
The mission of Apache Celeborn is the creation and maintenance of software
related to an intermediate data service for big data computing engines to boost
performance, stability, and flexibility
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Celeborn was founded 2024-03-20 (a year ago)
There are currently 26 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Fei Wang on 2024-12-31.
- Jiaming Xie was added as committer on 2025-05-20
- Zhentao Shuai was added as committer on 2025-07-07
## Project Activity:
Software development activity:
- Release 0.6.0 is released on 5 July.
- CIP-13 Support auto scaling is under design discussion.
- CIP-14 Support cpp client is under development.
- CIP-16 Merge transport and resource proto files has completed.
- CIP-17 Interruption Aware Slot Selection is under development.
- CIP-18 Support read skew partition has completed.
- CIP-19 Support app priority is under discussion.
- CIP-21 Support Flink JM failover is under discussion.
- Support Flink 2.1 has completed.
- MapPartition supports DFS has completed.
Meetups and Conferences:
- 4 talks were given in CoC Asia 2025.
Recent releases:
- Release 0.6.0 is released on 5 July.
## Community Health:
Overall community health is good. In the past quarter, the dev mail list mail
number had a 71% increase in the past quarter to 77. The issues mail list had
a 1% increase to 1186, the PMC considered it as normal because the absolute
number is relatively high. We have been performing extensive outreach for our
users, and encouraging them to contribute back to the project. Also, we are
active in making a voice in various conferences to attract more users.
-----------------------------------------
Attachment K: Report from the Apache Celix Project [Pepijn Noltes]
## Description:
Apache Celix is a framework for C and C++14 to develop dynamic modular
software applications using component and in-process service-oriented
programming. Apache Celix is inspired by the OSGi specification adapted for C
and C++
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache Celix was founded 2014-07-16 (11 years ago)
There are currently 17 committers and 10 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 Peng Zheng on 2022-10-16.
- No new committers. Last addition was Zhenbao on 2022-10-19.
## Project Activity:
Development over the past few months has been very slow. Apache Celix is a
relatively small project community-wise, and activity is currently dormant. No
releases have been made in the past year.
## Community Health:
Communication and development activity are in decline, but this could be
temporary. One of the challenges is the next release, we have decided to make
this a major (breaking) release but this also entails a lot needed change
before a breaking release is possible.
-----------------------------------------
Attachment L: Report from the Apache Community Development Project [Swapnil Mane]
## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: None
## Membership Data:
Apache Community Development was founded 2009-11-01 (16 years ago)
There are currently 52 committers and 43 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 Drew Foulks on 2024-08-30.
- No new committers. Last addition was Chris Wells on 2025-04-11.
## Project Activity:
### Mission Statement Update
Dear board, thank you for your feedback on updating our mission statement in
the last board report.
Rich and Swapnil are working on this and aim to make good progress this
quarter in drafting a statement that is in line with our current
activities, and will share it with the team for feedback.
### Google Summer of Code 2025
During the past quarter, we completed the community bonding phase and
started the coding process. The midterm evaluation for all projects was
completed on time in July, with all 27 students passing. Kudos to the
mentors for their unwavering dedication.
The GSoC Mentor Summit 2025 will be held in Munich, Germany, and will
be attended by our GSoC admins Priya Sharma and Sanyam Goel.
### Apache Local Community (ALC)
#### ALC Taipei
We established a new ALC chapter – ALC Taipei, China, receiving strong
interest from the community. A total of 17 volunteers expressed
interest, including 5 ASF members.
This quarter, the chapter organized multiple in-person meetups, shared
open-source technologies at universities and research institutes,
participated in Community Over Code Asia 2025, and hosted community
dinners and policy discussions with government officials and industry
leaders.
#### ALC Beijing
ALC Beijing successfully hosted Community Over Code Asia 2025.
Highlights:
- Three-day conference with 180 speakers
- 263 sessions submitted, 160 accepted (30 English, 130 Chinese)
- Keynote live-streamed over seven media channels, 138K total views
- 1,288 registered and paid attendees, 906 checked in on-site
#### ALC Florianópolis
We received interest to establish a new ALC Florianópolis, Brazil. The
PMC has approved it, and it will be established soon. ALC Florianópolis
will be a valuable addition to spreading Apache and open-source
awareness in the Brazil region.
### Website and Content Updates
Rich reviewed and improved the phrasing of the ComDev website content,
eliminating duplication. He also contributed to working group efforts
and resumed work on Feathercast, now rebranded as PlusOne, which
overlaps ComDev and M&P work. Thank you, Rich.
## Community Health:
We observed a drop in activity on our dev mailing list, which was
expected after the spike in the previous quarter due to GSoC inquiries
and related activity. However, overall engagement remained strong, with
active participation across various initiatives, thanks to the efforts
of our community members.
-----------------------------------------
Attachment M: 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 (17 years ago)
There are currently 73 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 Tony Schmidt on 2025-03-31.
## Project Activity:
- multiple parallel feature developments are ongoing.
## Community Health:
- northern hemisphere summer makes things a little slower as usual,
but nothing unusual to report.
-----------------------------------------
Attachment N: Report from the Apache Creadur Project [Philipp Ottlinger]
## Description:
The mission of Creadur is the creation and maintenance of software related to
Comprehension and auditing of software distributions
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Creadur was founded 2012-04-18 (13 years ago)
There are currently 13 committers and 12 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 Claude Warren on 2024-01-23.
- No new committers. Last addition was Jean-Baptiste Onofré on 2024-01-23.
## Project Activity:
The current 0.17-SNAPSHOT is still in development to harmonise
the usage of RAT among all available UIs.
Apart from that maintenance is happening in RAT and its subprojects.
## Community Health:
We are still working on the current 0.17 release.
Apart from final bugfixes and implementation improvements
work on the homepage has started, but is stalled due to the
vacation season.
Mailing list traffic mainly increased due to commit messages.
-----------------------------------------
Attachment O: Report from the Apache DataFu Project [Eyal Allweil]
## Description:
The mission of Apache DataFu is the creation and maintenance of software
related to well-tested libraries that help developers solve common data
problems in Hadoop and similar distributed systems
## Project Status:
Current project status: Ongoing (low)
Issues for the board: none
## Membership Data:
Apache DataFu was founded 2018-02-21 (7 years ago)
There are currently 20 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ohad Raviv on 2023-02-06.
- No new committers. Last addition was Ben Rahamim on 2025-02-19.
## Project Activity:
DATAFU-SPARK-2.1.0 was released on 2025-04-20.
In the beginning of this last period there was a lot of release related
activity. Our current plan is to add support for the two new versions of Spark
that are not currently available, 3.5.x and 4.0.x, and publish a blog post
about the features in our most recent release.
## Community Health:
We don't have any new contributions in this last quarter, so the only thing
being discussed in our mailing list is the the new Spark versions to support
and our usual questions of how to publicize the project more.
-----------------------------------------
Attachment P: Report from the Apache DataSketches Project [Lee Rhodes]
## Description:
The mission of Apache DataSketches is the creation and maintenance of software
related to an open source, high-performance library of streaming algorithms
commonly called "sketches" in the data sciences. Sketches are small, stateful
programs that process massive data as a stream and can provide approximate
answers, with mathematical guarantees, to computationally difficult queries
orders-of-magnitude faster than traditional, exact methods
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache DataSketches was founded 2020-12-15 (5 years ago)
There are currently 18 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Charlie Dickens on 2023-07-04.
- Nikunj Bhartia was added as committer on 2025-06-11
- 2 new PMC members are in process of being approved
## Project Activity:
The Apache/datasketches/bigquery (ds-bq) library continues to make progress
with more users making suggestions for improvements, and we have responded
with a minor release and a bug release (e.g., ds-bq 1.1.0, 1.1.1).
The datasketches-java (ds-java) library has been moving quickly to keep
pace with the new Java language releases. DS-java 8.0.0 was released in
April supporting Java 21. We are currently busy refactoring the entire
ds-java library to migrate to the new Java FFM API, which will have its
first LTS release with the upcoming Java 25 this coming September.
This migration will eliminate the current dependency on the
datasketches-memory repo, which was created 10 years ago to enable
fast off-heap management of data structures and state-machines.
We are still working on a GO release, but our principal committer is on
leave for several weeks. We hope to continue with that effort when he
returns. There is increased interest in developing a parallel Rust library
in the near future.
## Community Health:
Our project is healthy. We have a small, loyal and growing community
of users that contact us when they have questions or issues. We are experiencing
growing interest from major corporations in our multi-language libraries.
The Google adoption is strong evidence of that.
We continue to get interest from scientists around the world who
offer ideas for new sketches for our library based on recent research.
-----------------------------------------
Attachment Q: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap various CDI containers.
- JSF integration
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Testing support to allow low level unit testing of CDI enabled projects.
## Issues
There are no issues requiring board attention at this time.
## Activity
We fixed a few open tickets and resolved some community requests.
We did a release with 6 +1. So plenty activity.
## Community changes, past quarter:
- No new PMC members. Last addition was Harald Wellmann on 2016-05-19.
- Thomas Frühbeck was added as committer on 2024-02-05
## Recent releases:
- 2.0.1 (JakartaEE) was released on 2025-08-11.
- 2.0.0 (JakartaEE) was released on 2024-04-10.
- 1.9.6 was released on 2022-04-12.
-----------------------------------------
Attachment R: Report from the Apache Doris Project [Mingyu Chen]
-----------------------------------------
Attachment S: 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 (11 years ago)
There are currently 62 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was James Turton on 2022-01-23.
- No new committers. Last addition was Maksym Rymar on 2022-10-19.
## Project Activity:
In June, we released Drill 1.22 which contained many bug fixes, maintenance
updates and new functionality. Release notes here:
https://drill.apache.org/docs/apache-drill-1-22-0-release-notes/
We recently merged some significant performance
improvements to the Hive and HBase plugins--specificially filter and limit
pushdowns for Hive and limit pushdown for HBase. Work continues on the
integration with Apache Daffodil.
(No the em-dash was not generated by ChatGPT. I use them in my writing)
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:
The Drill community continues to develop Drill, albeit at a somewhat slower
pace than in the past.
dev@drill.apache.org had a 84% increase in traffic in the past quarter
(122 emails compared to 66)
issues@drill.apache.org had a 126% increase in traffic in the past quarter
(93 emails compared to 41)
user@drill.apache.org had a big increase in traffic in the past quarter
(16 emails compared to 0)
4 JIRA tickets opened and 12 closed in the past quarter.
15 Pull requests merged in the last quarter.
A minor issue, but I did appreciate the statistics from
GitHub that used to appear in the reporting tool. Most of the Drill
community activity occurs in Slack and via Github, so the activity metrics
reported here reflect less activity than there actually is.
-----------------------------------------
Attachment T: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
Empire-db is a lightweight relational database access library dealing with all
aspects of storing, manipulating, retrieving and modelling data in relational
database management systems (RDBMS). As an alternative to traditional
OR-Mapping solutions, it provides an SQL centric, no-compromise approach that
uses a Java-Object-Model rather than Mapping Files or Annotations.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Empire-db was founded 2012-01-24 (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 Jan Glaubitz on 2016-07-10.
- No new committers. Last addition was Ralf Eichinger on 2022-03-15.
## Project Activity:
Latest release is empire-db-3.3.0 released on 2025-03-11.
The project is steadily maintained and several new bugfixes and improvements
have been started or completed since our last release in March.
It is thus likely that we will put up our next release up for voting during
the upcoming quarter.
## Community Health:
Our community albeit small is still alive and healthy.
11 new Jira-Tickets were opened and 1 closed this quarter
38 commits in the past quarter.
-----------------------------------------
Attachment U: Report from the Apache EventMesh Project [Eason Chen]
-----------------------------------------
Attachment V: Report from the Apache Flex Project [Harbs]
## Description:
The mission of the Apache Flex project is to create and maintain software
related to the development of expressive web applications that deploy to all
major browsers, desktops and devices (including smartphones, tablets and tv)
## Project Status:
Current project status: Stable and very little activity Issues for the board:
None
## Membership Data:
Apache Flex was founded 2012-12-19 (13 years ago) There are currently 67
committers and 45 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Greg Dove on 2023-03-03.
- No new committers. Last addition was Greg Dove on 2016-09-07.
## Project Activity:
No change. We missed filing the report the last two months. There was a brief
discussion about retiring the project a few weeks ago. One PMC member
expressed a desire to implement some new features. The consensus was that
there was no reason to retire the project at this time.
## Community Health:
There has been very little activity, but there is clearly still enough of the
PMC around to maintain the project.
-----------------------------------------
Attachment W: Report from the Apache Fory Project [Chaokun Yang]
-----------------------------------------
Attachment X: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was very low in recent months.
## Health report:
Activity was very low in recent months, though such periods are not unusual
for this project. User questions (mostly on StackOverflow) and new Jira issues
are still being answered. Most PR-s slowly but eventually getting reviewed and
merged. Next goal is to do the next minor release as enough smaller changes
accumulated. Bigger task still unfinished in 2.x line is the java.time support
(FREEMARKER-35). The even longer term goal is continuing the ongoing
development on the 3.0 branch, so that the project can innovate, and the code
base can become more modern and attractive for new committers.
## PMC changes:
- Currently 9 PMC members.
- Last added on 2025-01-01
## Committer base changes:
- Currently 12 committers.
- Last added (non-PMC): Siegfried Goeschl on 2020-01-07
## Releases:
- 2.3.34 was released on 2024-12-22
-----------------------------------------
Attachment Y: Report from the Apache Geode Project [Mark Bretl]
-----------------------------------------
Attachment Z: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AA: Report from the Apache Gravitino Project [Jerry Shao]
## Description:
The mission of Apache Gravitino is the creation and maintenance of software
related to managing your data and AI assets seamlessly with a flexible,
unified governance framework, including lakehouse federation capabilities
## Project Status:
Current project status: New Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-21 (3 months ago) There are currently 27
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- Abyss-lord was added as committer on 2025-07-07
- Eric Chang was added as committer on 2025-05-30
## Project Activity:
1. A new maintenance release (0.9.1) is released on July 21.
2. The next major release (1.0.0) is feature freezed, under testing and
release preparation.
Recent developments on Gravitino:
- Metadata authentication, features are actively developed on dev branch
(90%).
- Cache system is almost done (95%).
- Policy system, the dev works are done, under reviewing.
- Statistics system, the dev works are done, under reviewing.
- Job system, the dev workd are done, under reviewing.
## Community Health:
1. 65 issues were resolved in last 30 days; 163 issues were created in last 30
days.
2. 112 PRs were merged in last 30 days, 158 PRs were created in last 30 days.
3. dev@gravitino.apache.org had a 13% increase in traffic in the past quarter
(181 emails compared to 160)
4. Several talks related to Gravitino were presented in CoC Asia 2025.
-----------------------------------------
Attachment AB: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment AC: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No issues requiring board attention at this time.
## Membership Data:
Apache Groovy was founded 2015-11-18 (10 years ago)
There are currently 23 committers and 13 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 Soeren Glasius on 2024-11-06.
- No new committers. Last addition was Sergio del Amo on 2024-12-20.
## Project Activity:
Recent releases:
5.0.0-rc-1 was released on 2025-08-06.
4.0.28 was released on 2025-07-23.
5.0.0-beta-2 was released on 2025-07-23.
3.0.25 was released on 2025-05-27.
4.0.27 was released on 2025-05-27.
5.0.0-beta-1 was released on 2025-05-27.
The Groovy PMC voted to accept Geb (previously gebish.org) as a Groovy
subproject late last year. There is a draft website and snapshots are currently
available. A first release under the ASF is taking a little longer than
expect but we are adapting the build process to use some recent advances
spearheaded by the Grails project.
The Groovy PMC voted earlier in the year to sponsor incubation of the Grails
project (grails.org) to become a new TLP when ready. The Grails PPMC is
working well.
* the major Grails repos are now under the ASF organization
* the project has performed self-assessment via the maturity model
which indicates the project is close to being ready for graduation
* they have voted in new committers and PPMC members
* community activity has been high including many discussions and votes
* numerous releases have been undertaken including:
Core: 7.0.0-M4, 7.0.0-M5, 7.0.0-RC1
Plugins:
quartz: 4.0.0-M3
redis: 5.0.0-M4, 5.0.0-M5,
spring-security: 7.0.0-M4, 7.0.0-M5
The other major goal of the Groovy PMC over the next quarter is
to move Groovy 5 towards a GA release. We recently released 5.0.0-RC-1.
We are working with VP Brand management on potential branding issues
for Groovy and Grails with other projects popping up with similar names.
## Community Health:
Overall, community activity has increased this quarter.
Work on incorporating Geb as a subproject is well advanced.
Work helping Grails on their incubation journey is well advanced.
The main Groovy project is preparing its final RC release(s)
of Groovy 5 before the 5.0.0 release is undertaken.
We look forward to contributing to the upcoming Community over Code
conference in Minneapolis next month. Talks on Groovy, Geb and Grails
feature in the Groovy track.
-----------------------------------------
Attachment AD: Report from the Apache Hop Project [Hans Van Akelyen]
-----------------------------------------
Attachment AE: Report from the Apache HTTP Server Project [Joe Orton]
## Description:
The mission of HTTP Server is the creation and maintenance of software related
to Apache Web Server (httpd)
## Project Status:
Current project status: Ongoing, low activity
Issues for the board: None
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (30 years ago)
There are currently 126 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Giovanni Bechis on 2021-06-11.
- No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05.
## Project Activity:
Development activity this quarter was concentrated around two new releases
from the 2.4.x branch, with 2.4.64 released on July 10th and 2.4.65 on July
23rd. The 2.4.64 release as usual included various new features and bug fixes
backported from the trunk, and addressed outstanding security issues. Eight
different vulnerabilities were fixed in this release, including a particularly
complex longstanding TLS protocol de-synchronisation attack (CVE-2025-49812).
As I've commented before in these reports, it is notable that almost all the
security issues being discovered and addressed in httpd are attacks against
logic or protocol handling, rather than due to C language memory handling
safety issues - though we are certainly not entirely free of those. The fix
for CVE-2025-49812 was to remove support for an unused protocol feature, for
example.
After the 2.4.64 release was shipped, a regression (with security impact) was
found in one of the bug fixes, and 2.4.65 was spun to address that.
## Community Health:
Other than discussion around the releases, the development list was again
fairly quite. We have seen a couple of poor quality GitHub pull requests which
may be AI-generated, but it is hard to be certain. User discussion in Bugzilla
was quite active with reports on configurations which stopped working
after the security fixes 2.4.64 (both expected and unexpected).
-----------------------------------------
Attachment AF: Report from the Apache HttpComponents Project [Michael Osipov]
-----------------------------------------
Attachment AG: Report from the Apache Ignite Project [Dmitry Pavlov]
## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Ignite was founded 2015-08-19 (10 years ago)
There are currently 78 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Maksim Timonin was added to the PMC on 2025-05-14
- No new committers. Last addition was Roman Puchkovskiy on 2024-04-24.
## Project Activity:
No recent releases. Previous were:
- 3.0.0 was released on 2025-02-10
- 2.17.0 was released on 2025-02-13
Community tooling: Apache Ignite abbreviation plugin updated.
Ignite 3.x: Reduced lambda/array allocations, improved partition write
latency, fixed Netty buffer leaks and message compatibility, enhanced JDBC
with thin client APIs.
Ignite 2.x: Focused on stability — added transaction deadlock metrics, fixed
stability issues, strengthened tests for unstable networks, extended CDC
PostgreSQL type support.
## Community Health:
- All Apache Ignite mailing lists saw a decline in traffic last quarter, with
drops ranging from 9% to 16%
- Rolling upgrade initiative (to support node-by-node updates without
downtime)
-- Active discussions, planning, and refactoring of messaging/internal APIs
-- Several new contributors submitted patches for message serialization and
protocol refactoring as part of this effort.
-----------------------------------------
Attachment AH: Report from the Apache Impala Project [Zoltán Borók-Nagy]
## Description:
The mission of Apache Impala is the creation and maintenance of software
related to a high-performance distributed SQL engine
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: none
## Membership Data:
Apache Impala was founded 2017-11-15 (8 years ago)
There are currently 73 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Peter Rozsa on 2025-03-21.
- No new committers. Last addition was Noémi Pap-Takács on 2025-03-12.
## Project Activity:
- Working on Iceberg REST catalog integration
- Command for remove orphan files of Iceberg table
- Calcite planner integration
- Planner enhancements
- ipv6 support
- CatalogD stabilization
- Tuple cache improvements
- Commands for query cancellation
- Enhancements to Impala's web UI
## Community Health:
reviews@ is the most reliable metric of Impala community activity level.
There were 3761 emails to that list in June, July,
and August (until 12th)
-----------------------------------------
Attachment AI: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for August 2025
The Apache Incubator is the entry path into the ASF for projects and
codebases seeking to join the Foundation.
As of July, there are 34 podlings in incubation. Podlings executed 10
releases during the month, and two IP clearances were completed.
ResilientDB encountered difficulties in following the correct ASF release
process.
Several new proposals were discussed, and one new podling, Blaze, entered
incubation. Fory graduated last month, while Annotator and NLPCraft were
retired by the IPMC. No changes were made to IPMC membership.
Only PonyMail failed to submit a report and will be asked to report next
month. Given its repeated lapses, it may be time to revisit earlier
discussions about the project’s future, as past conversations have not
reached a clear consensus.
Several talks were given at Community Over Code Asia in the Incubator Track.
Discussion on the mailing list in July focused on releases, new projects
and graduations, mentor involvement, clarification of ICLA requirements for
non-committers, and further development of mentor onboarding and training
materials, including scenario-based learning material for mentors and IPMC
members. There is concern about the lack of activity in HoraeDB.
Among the long-term podlings, Toree continues to make very gradual progress
toward graduation, and the Livy PPMC is also moving forward slowly. All
other long-running podlings have either graduated or retired.
## Community
### New IPMC members:
- none
### People who left the IPMC:
- none
## New Podlings
- Blaze (renamed Auron)
## Podlings that failed to report, expected next month
- PonyMail
## Graduations
- Fory
The board has motions for the following:
- Teaclave
- Training
## Releases
The following releases entered distribution during the month of
July:
- Devlake 1.0.2
- Fory 0.11.2
- Gluten 1.4.0
- Hertzbeat 1.7.2
- KIE 10.1.0
- Seata 2.4.0
- Teaclave 0.5.1
- Otava 0.6.1
- Polaris 1.0.0
- XTable 0.3.0
## IP Clearance
- OpenDAL Reqsign
- Spark Connect Rust
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[BifroMQ](#bifromq)
[Burr](#burr)
[Cloudberry](#cloudberry)
[DevLake](#devlake)
[GeaFlow](#geaflow)
[GraphAr](#graphar)
[Hamilton](#hamilton)
[HoraeDB](#horaedb)
[KIE](#kie)
[NLPCraft](#nlpcraft)
[Seata](#seata)
[Texera](#texera)
[Toree](#toree)
[Training](#training)
[XTable](#xtable)
--------------------
## BifroMQ
BifroMQ is a Java-based, high-performance, distributed MQTT broker with
native multi-tenancy support, designed for large-scale connections and
message delivery.
BifroMQ has been incubating since 2025-04-22.
### Three most important unfinished issues to address before graduating:
1. Complete the first incubator release
2. Gain more public exposure and grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
The signed documents for transferring the trademark have been accepted.
We are waiting for the process to be completed and for a copy of the
ASF-stamped agreement, so we can complete the donation contract workflow.
### How has the community developed since the last report?
I attended Apache Community Over Code Asia and spoke at the Incubator
Track, making connections with potential users and adopters.
### How has the project developed since the last report?
* We are working toward a code freeze for the first incubator release
* Updated the website with a detailed contribution guide in the community
section
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-25
### When were the last committers or PPMC members elected?
None since entering the incubator
### Have your mentors been helpful and responsive?
Yes, we get helpful and timely guidance from the mentors
### Is the PPMC managing the podling's brand / trademarks?
The transfer of BifroMQ’s trademark is in progress.
### 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:
--------------------
## Burr
Burr is a lightweight in-process python framework that standardizes the
expression and execution of state machines as action-driven graphs, while
making graph execution easily observable. It is particularly suited for AI
agent workflows, simulations, and other dynamic systems, and comes with a
self-hostable observability UI that integrates with OpenTelemetry.
Burr has been incubating since 2025-05-24.
### Three most important unfinished issues to address before graduating:
1. Finish check list to be able to make a release
2. Start releasing
3. Enable more contributors
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
Flat. Discord continues to trickle in.
One user wants to contribute a UI.
### How has the project developed since the last report?
1. One new feature was merged.
2. Some PRs were merged for licensing etc. But still more work needed for
first release.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release <== here
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
May 2025
### Have your mentors been helpful and responsive?
Time for the committers has been an issue this summer to get through
the checklist required to release under Apache.
### Is the PPMC managing the podling's brand / trademarks?
I think so. No issues thus far.
### Signed-off-by:
- [ ] (burr) Kevin Ratnasekera
Comments:
- [X] (burr) Ayush Saxena
Comments:
- [X] (burr) PJ Fanning
Comments: Podling name is approved. We got it approved before setting
up ASF resources.
### IPMC/Shepherd notes:
--------------------
## Cloudberry
Cloudberry is an advanced and mature open-source Massively Parallel
Processing (MPP) database, derived from the open-source version of Pivotal
Greenplum Database®️ but built on a more modern PostgreSQL 14 kernel,
whereas Greenplum is based on PostgreSQL 12. This upgrade brings enhanced
enterprise capabilities, making Cloudberry well-suited for data
warehousing, large-scale analytics, and AI/ML workloads.
Cloudberry has been incubating since 2024-10-11.
### Three most important unfinished issues to address before graduating:
1. Publish the first Apache release following ASF release processes.
2. Grow the contributor and community to ensure long-term sustainability.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We're working on the first ever Apache release. Hope to get enough
reviews and binding votes when the first Release vote email is sent to the
Incubator mailing list.
### How has the community developed since the last report?
- Mailing list Activity: 221 new emails on the Dev mailing list since the
last report (98 emails in May, 60 emails in June and 63 emails in July),
covering technical and Apache-related discussions.
- Slack Activity: 15 new threads in `general` channel, 5 new members
since last report.
- GitHub Discussions: 16 new threads since last report (8 new in May, 5
new in June, 3 new in July).
- New Committers:
- May 21, 2025 - Wenchao Zhang (zhangwenchao-123)
- July 9, 2025 - Xun Gong (gongxun0928)
- Events:
- Community Over Code Asia 2025: six presentations on Cloudberry at
this conference, covering AI, Data Warehouse, OLAP and Incubator tracks.
There was one Cloudberry booth.
- HOW2025: PostgreSQL & IvorySQL Eco Conference in Jinan, China: PPMC
members Dianjin Wang and Max Yang attended this conference and introduced
Apache Cloudberry to the audience.
- 10-minute T3D session on Apache Cloudberry from PPMC Member Tushar
Pednekar with the host Joshua Drake: https://youtu.be/0mPCoEXG0XU
- PPMC member Tushar Pednekar had a presentation on Cloudberry + Flink
at Flink Forward Asia, Singapore 2025:
https://www.youtube.com/watch?v=K9d572vOvNY
- Presentation recording available at
https://www.youtube.com/watch?v=lMYqOoE4p5A, by contributor @Leonid
Borchuk
and PPMC Member @Kirill Reshke at the sql-ninja conference.
### How has the project developed since the last report?
- Compliance with ASF policy:
- Renamed `greenplum_path` to `cloudberry-env.sh` for better compliance
with ASF rules.
- Updated Apache RAT license metadata for release.
- Changed PAX's cpp-stub from submodule to subdir to avoid introducing
binary files.
- Changed Python modules for gpMgmt from bundling their source tarballs
to downloading them during the build process via `pip3 install`.
- Working on the first Apache Cloudberry (Incubating) 2.0.0 release:
- Already had RC1 & RC2 rounds and fixed some license issues, will have
an RC3 round for the dev vote and Apache Incubator vote.
- PostgreSQL Kernel upgrade: the community developer has started the
kernel upgrade work from PG 14.4 to PG 16.6.
- 130 new commits to main branch since the last report, focusing on
performance improvements, bug fixes and new features.
- Ecosystem:
- Apache SeaTunnel added official connector support for Apache
Cloudberry in its latest 2.3.11 release (See https://s.apache.org/baj30).
- Flink JDBC Connector v3.3.0+ now supports Cloudberry via PR
https://s.apache.org/jt29r
- Our GitHub main repo has reached 1k+ GitHub stars!
### 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:
N/A
### When were the last committers or PPMC members elected?
- May 21, 2025 - Wenchao Zhang (zhangwenchao-123)
- July 9, 2025 - Xun Gong (gongxun0928)
### Have your mentors been helpful and responsive?
Yes, we can get suggestions and support on licensing and release matters.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (cloudberry) Roman Shaposhnik
Comments:
- [X] (cloudberry) Willem Ning Jiang
Comments: PPMC is trying they best to cut the first release by
following ASF release policy.
- [X] (cloudberry) Kent Yao
Comments: The community is active
### IPMC/Shepherd notes:
--------------------
## DevLake
DevLake is a development data platform, providing the data infrastructure
for developer teams to analyze and improve their engineering productivity.
DevLake has been incubating since 2022-04-29.
### Three most important unfinished issues to address before graduating:
1. Grow the community and attract more users.
2. Add more committers and PPMC members.
3. Maintain the project, fix bugs, and improve the user experience based
on the feedback from the community.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
1. 11 new contributors have joined the community (205 contributors in
total).
2. 79 new community members in Slack (1640 in total).
3. 2 new committers were elected, and 2 PPMCs were elected.
### How has the project developed since the last report?
1. Support importing QA domain data via CSV templates.
2. Release a new ASF version 'v1.0.2'.
3. Bugfixes and UX refinement.
### 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:
With the help of our mentors, we have started the graduation process of
DevLake. We just finished the maturity analysis and will start the vote in
our dev channel. Check details at:
https://devlake.apache.org/community/maturity
### Date of last release:
2025-07-02
### When were the last committers or PPMC members elected?
2025-06-25
### Have your mentors been helpful and responsive?
Yes, the mentors helped tremendously throughout version releases and
community governance.
### Is the PPMC managing the podling's brand / trademarks?
Yes. There are no known brand and naming issues.
### Signed-off-by:
- [X] (devlake) Felix Cheung
Comments:
- [ ] (devlake) Liang Zhang
Comments:
- [X] (devlake) Lidong Dai
Comments:
- [ ] (devlake) Sijie Guo
Comments:
- [X] (devlake) Jean-Baptiste Onofré
Comments: I would suggest to start discussion about graduation.
- [X] (devlake) Willem Ning Jiang
Comments: The project is a good sharp of graduation.
### IPMC/Shepherd notes:
--------------------
## GeaFlow
GeaFlow is a streaming graph computing engine for distributed large-scale
real-time graph storage and analysis. It supports trillion-level graph
storage, hybrid graph and table processing, real-time/offline graph
computing, and interactive graph analysis.
GeaFlow has been incubating since 2025-06-06.
### Three most important unfinished issues to address before graduating:
1. Release the first version.
2. Establish a well-defined community governance framework.
3. Enhance the diversity of community (attracting more committers,
contributors, and users).
4. Drive the community forward in accordance with the technial roadmap in
issues.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. 4 new contributors have joined the community.
2. Submit a task in OSPP(Open Source Promotion Plan)2025.
### How has the project developed since the last report?
1. Group id, documents and ASF configuration file updates.
2. Some fixes by community developers.
3. The feature development of the first release version.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
We are actively preparing for the first release version.
### When were the last committers or PPMC members elected?
When the incubator GeaFlow project is officially approved through voting.
### Have your mentors been helpful and responsive?
Yes, the montors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
N/A
### Signed-off-by:
- [X] (geaflow) Willem Ning Jiang
Comments: Get started
- [X] (geaflow) Xin Wang
Comments:
- [X] (geaflow) Jingsong Lee
Comments:
- [X] (geaflow) Paul King
Comments:
- [X] (geaflow) Justin Mclean
Comments:
### IPMC/Shepherd notes:
--------------------
## GraphAr
GraphAr is an open-source and language-independent data file format designed
for efficient graph data storage and retrieval.
GraphAr has been incubating since 2024-03-25.
### Three most important unfinished issues to address before graduating:
1. Growing the community(attracting more committers, contributors and
users)
2. Release more ASF-compliant versions
3. Extend the GraphAr format to support more systems
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. Voted and accepted 1 new committer.
2. Attend the OSPP 2025 activity with two projects.
### How has the project developed since the last report?
1. Merged 14 PRs since the last report
2. Support WriterOption in SDK to allow users to configure writer options
3. Support multi-property in GraphAr format and C++ SDK
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-07-02
### When were the last committers or PPMC members elected?
2025-07-14
### Have your mentors been helpful and responsive?
Yes, the mentors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [X] (graphar) Calvin Kirs
Comments:
- [ ] (graphar) tison
Comments:
- [ ] (graphar) Xiaoqiao He
Comments:
- [ ] (graphar) Yu Li
Comments:
### IPMC/Shepherd notes:
--------------------
## Hamilton
Hamilton is a lightweight in-process framework to define, execute, and
observe directed acyclic graphs (DAGs) that express data transformations. In
Hamilton, one can express complex DAGs of transformations, e.g. from
dataframe transformations (using pandas, polars, PySpark), machine learning
pipelines, through to regular software engineering API request and LLM API
based workflows. Observability hooks are built into the framework. The
Hamilton UI is a self-hostable service to capture observability output from
workflow runs.
Hamilton has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Finish check list to be able to make a release
2. Start releasing
3. Enable more contributors
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
Flat. Slack continues to trickle in.
Non PPMC users contributed some code.
### How has the project developed since the last report?
1. We have many merged features that haven't been released.
2. Some PRs were merged for licensing etc. Docs were updated.
3. But still more work needed for first release.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release <== here
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
April 2025
### Have your mentors been helpful and responsive?
Time for the committers has been an issue this summer to get through
the checklist required to release under Apache.
### Is the PPMC managing the podling's brand / trademarks?
I think so. No issues thus far.
### Signed-off-by:
- [ ] (hamilton) Kevin Ratnasekera
Comments:
- [X] (hamilton) Ayush Saxena
Comments:
- [X] (hamilton) PJ Fanning
Comments: Podling name is approved. We got it approved before setting
up ASF resources.
### IPMC/Shepherd notes:
--------------------
## HoraeDB
HoraeDB is a high-performance, distributed, cloud native time-series
database.
HoraeDB has been incubating since 2023-12-11.
### Three most important unfinished issues to address before graduating:
1. Release more version
2. Grow community(attract more users/committers)
3. Finish the new metrics engine
### Are there any issues that the IPMC or ASF Board need to be aware of?
Several core developers have left the project, causing a slowdown in
development this year.
We expect development to get back on track next year.
### How has the community developed since the last report?
Attend the OSPP 2025 with one project.
### How has the project developed since the last report?
There has been no significant progress since the last report.
### 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:
2024-12-10
### When were the last committers or PPMC members elected?
Neo Chen, at 2024-12-25
### Have your mentors been helpful and responsive?
Yes, they are helpful when release version and other trivial things.
### Is the PPMC managing the podling's brand / trademarks?
Yes, we're doing well with this.
### Signed-off-by:
- [x] (horaedb) tison
Comments: See https://lists.apache.org/thread/jrwdwsyodmjow5cclddx7rjgppq989lg
- [ ] (horaedb) Shaofeng Shi
Comments:
- [ ] (horaedb) Gang Li
Comments:
- [ ] (horaedb) Von Gosling
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. Continuing to build the community
2. Removing dependencies which do not comply (almost there)
3. Ensuring branding is correct
### Are there any issues that the IPMC or ASF Board need to be aware of?
No, we’re moving along well. Slowly, but still making progress.
### How has the community developed since the last report?
We have some new people submitting changes and are looking at add more to
the list of committers, but we would like them to be more active on the
mailing lists besides just submitting code.
### How has the project developed since the last report?
We're in the process of redirecting the old community sites to the new
Apache KIE website. We released 10.1.0 July 10th!
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-07-10
### When were the last committers or PPMC members elected?
Start of the year
### Have your mentors been helpful and responsive?
Nothing to the report. The mentors are doing well.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (kie) Brian Proffitt
Comments: Thank you for the clarifications.
- [X] (kie) Claus Ibsen
Comments:
- [X] (kie) Andrea Cosentino
Comments: All good.
### IPMC/Shepherd notes:
[PJF] GPL licensed source and libs (and similar Category X licenses) are
proving to be a major roadblock on the path to graduation.
--------------------
## Seata
Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to-
use and high-performance distributed transaction solution, used to solve the
data consistency problem.
Seata has been incubating since 2023-10-29.
### Three most important unfinished issues to address before graduating:
1. Complete the transfer of Seata's existing trademarks to the ASF.
2. Finalize pre-graduation discussions and address any remaining gaps in
required tasks.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at the moment.
### How has the community developed since the last report?
1. 24 new code contributors have joined the community (596 contributors
in total)
2. 5 new committers were elected, and 1 PPMC members were elected.
3. We presented two sessions on Apache Seata at the CommunityOverCode
Asia conference and organized a face-to-face community meetup offline.
4. We have finalized the Apache Seata (incubating) [Maturity Model
Assessment](https://seata.apache.org/docs/next/developers/maturity) and
facilitated community-driven discussions.
### How has the project developed since the last report?
1. Since the last report, we've merged 194 PRs, which include over 10 new
features.
2. Since the last report, we have released two official versions: 2.4.0
and 2.5.0.
3. Since the last report, we have addressed and disclosed two CVEs:
CVE-2025-32897 and CVE-2025-53606.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2025-08-05
### When were the last committers or PPMC members elected?
2025-08-06
### Have your mentors been helpful and responsive?
Our mentors have been very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
No Trademark issues.
### Signed-off-by:
- [X] (seata) Sheng Wu
Comments: Work on
- [X] (seata) Justin Mclean
Comments:
- [X] (seata) Huxing Zhang
Comments: The project is in good progress working towards graduation.
- [X] (seata) Heng Du
Comments:
- [X] (seata) Xin Wang
Comments:
### IPMC/Shepherd notes:
[PJF] Discussing Graduation
--------------------
## Texera
Texera is an open-source system to support collaborative data science, AI,
and ML using GUI-based workflows. Our vision is to develop a system to
support cloud platforms on which users can easily analyze data and use AI/ML
techniques provided as operators. Users with various backgrounds,
irrespective of whether they know coding or not, can collaborate on the same
project to construct a pipeline. Experienced users can use programming
languages such as Python, R, Java, and Scala to implement customized
computation logic. The platform allows users to pause the execution of a
workflow to investigate the operator states, and resume the execution at a
later time. The platform can be used by a research community to publish
valuable resources such as data sets, workflows, and ML models to share
their domain-specific knowledge and support reproducibility of scientific
research. The platform also allows users to elastically request computing
resources from public clouds for computationally-intensive tasks.
Texera has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Donate the codebase to Apache.
2. Clean up parts in the codebase that are conflicting with Apache
3. Set up the Apache Texera webpage http://texera.apache.org/. Work is
underway to consolidate user guides, developer setup instructions, and
governance policies. We are analyzing the documentation structures of
successful projects like Apache Flink and Spark to ensure an optimal user
experience.
### 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?
* August 02, 2025: We have completed the SGA form. It has been submitted
and documented by Apache. We are ready to donate codebase now!
* July 30, 2025: We conducted our monthly group sync meeting with the
PPMC members, committers, and contributors.
* July 31, 2025: Zuozhi Wang joined as a PPMC member.
* We have engaged in significant community outreach and educational
activities this month, increasing the users, including 17 undergraduate
students, 34 students from high schools and community colleges, and 32
middle school students.
* Texera has been deployed and used for research at the UCI Department of
Ophthalmology.
### How has the project developed since the last report?
* Cloud Deployment: Texera now runs on AWS EKS with better resource
management.
* Machine Learning: Added scikit-learn training operators.
* UI Enhancements: Dynamic workflow setup and richer port-level metrics.
* Performance: Faster Texera Hub resource access.
* Docs: New tutorial videos in the works.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-04-04 (non ASF)
### When were the last committers or PPMC members elected?
The PPMC voted to add a new member on July 4 2025.
### Have your mentors been helpful and responsive?
Yes, our mentors were highly responsive and joined our meetings. We thank
PJ for guiding us on the SGA form. We also thank Ian for his help with his
experience from Apache AsterixDB.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (texera) Cezar Andrei
Comments:
- [ ] (texera) Gordon King
Comments:
- [X] (texera) PJ Fanning
Comments: SGA is now accepted by ASF Secretary and Git repo has been
moved to ASF
- [ ] (texera) Ian Maxon
Comments:
### IPMC/Shepherd notes:
--------------------
## Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.
Toree has been incubating since 2015-12-02.
### Three most important unfinished issues to address before graduating:
1.Increase active contributors
### Are there any issues that the IPMC or ASF Board need to be aware of?
None, Nothing much of news from previous report
### How has the community developed since the last report?
Slow activity with discussions about 0.6 release before merging
Scala 2.13 support. Having said that, actions started and slowed down.
### How has the project developed since the last report?
Few prs and activity around release started
### 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:
2022-04-11
### When were the last committers or PPMC members elected?
- Cheng Pan was added to the PPMC on 2023-08-28
### Have your mentors been helpful and responsive?
None
### Is the PPMC managing the podling's brand / trademarks?
No trademark issues
### Signed-off-by:
- [X] (toree) Luciano Resende
Comments: The podling should push for release and start graduation
process
- [ ] (toree) Ryan Blue
Comments:
- [ ] (toree) Weiwei Yang
Comments:
### IPMC/Shepherd notes:
--------------------
## Training
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various Apache
and non-Apache target projects.
Training has been incubating since 2019-02-21.
A graduation discussion has been started at
https://lists.apache.org/thread/5d87do2wl6yxvgt6kxwx6b90p7zb8dro
and there's a vote underway for graduation.
### Three most important unfinished issues to address before graduating:
1. Nothing. We are ready to graduate.
### How has the community developed since the last report?
We have determined to graduate. Please see link above.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Ready for graduation
### Date of last release:
While we have done a formal release, this is more of a content-producing
project, rather than releasing software artifacts. The most recent content
artifact was an update to the Airflow presentation, which lives at
https://training.apache.org/presentations/airflow/index.html#/table-of-conte
nts
### When were the last committers or PPMC members elected?
### Have your mentors been helpful and responsive?
Mentors have been very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes. Since our name is "Training", which is generic, we use the full
"Apache Training", which is unique and protected by the ASF name. We have
passed a name search.
### Signed-off-by:
- [ ] (training) Craig Russell
Comments:
- [ ] (training) Christofer Dutz
Comments:
- [X] (training) Justin Mclean
Comments:
- [ ] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
--------------------
## XTable
XTable is an omni-directional converter for table formats that facilitates
interoperability across data processing systems and query engines.
XTable has been incubating since 2024-02-11.
### Three most important unfinished issues to address before graduating:
1. Ironing out license issues with bundled jars for new features. This is
becoming increasingly relevant as we add new modules for integrations with
other projects and for our own REST service that allows
2. Strengthening community building by actively engaging with users.
3. Removing dependency on Spark for our project. This dependency adds
friction for users and makes it harder to quickly build and run the project.
### 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?
1. We have been collaborating with the Polaris community to provide a
conversion service that their catalog service can use to convert metadata
between table formats.
2.
### How has the project developed since the last report?
1. A REST Service was added so that users can run the project as a long
running service and call an endpoint to perform the conversion. This will
help users more easily integrate with the project, especially when callers
are not in the Java ecosystem.
2. We release 0.3.0 which includes the ability to sync tables to catalogs
in multiple table formats. The sync to a catalog was required for users to
query their data in the table format of their choice and helps
operationalize this data.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-06-05
### When were the last committers or PPMC members elected?
Feb 2024
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [X] (xtable) Jesús Camacho Rodríguez
Comments:
- [X] (xtable) Stamatis Zampetakis
Comments:
- [X] (xtable) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
[PJF] Mailing list traffic remains low. It seems like most of the
interactions happen in GitHub.
-----------------------------------------
Attachment AJ: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AK: Report from the Apache Juneau Project [James Bognar]
-----------------------------------------
Attachment AL: Report from the Apache Kafka Project [Mickael Maison]
## Description:
The mission of Kafka is the creation and maintenance of software
related to Distributed publish-subscribe messaging system
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kafka was founded 2012-11-21 (13 years ago)
There are currently 69 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- José Armando García Sancio was added to the PMC on 2025-06-15
- Lucas Brutschy was added to the PMC on 2025-07-14
- Omnia Ibrahim was added as committer on 2025-06-25
- PoAn Yang was added as committer on 2025-07-12
## Project Activity:
In the past quarter we released Kafka 3.9.1.
We have 2 releases in progress:
- 4.1.0: Planned for August, RC0 and RC1 out already, working on a new RC
- 4.0.1: Planned for August, RC0 out already, working on a new RC
## Community Health:
The community health is good. The number of contributors remains steady,
and the community is working on new big features (diskless).
The traffic on the mailing lists has decreased but still remains high with
over 1500 emails on the dev list this quarter.
-----------------------------------------
Attachment AM: Report from the Apache Kibble Project [Sharan Foga]
## Description:
The mission of Apache Kibble is the creation and maintenance of software
related to an interactive project activity analyzer and aggregator
## Project Status:
Current project status: Dormant (considering retirement)
Issues for the board:None
## Membership Data:
Apache Kibble was founded 2017-10-18 (8 years ago)
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
- No new committers. Last addition was Kaxil Naik on 2021-02-21.
## Project Activity:
The project has not yet made a release.
There has been no real activity since our last report. The question of
retirement was raised earlier in the year [1] and the responses show that we
no longer have sufficient resources available to maintain or develop the
project.
A dependency to the reporter.apache.org tool was identified where its code
makes a call to the Kibble API to retrieve project statistics. If
Kibble does move the attic then the functionality used by the reporter tool
needs to be extracted or a replacement feature needs to be created to extract
any necessary statistics.
The next step would be to begin a vote on the dev list to retire the project.
## Community Health:
The community has always been fairly small and the majority don't currently
have the bandwidth to contribute to the project.
A vote to retire the project is the next logical step. And if there are anyone
interested in progressing the project then they have an opportunity to save
the project from potential retirement.
[1] https://s.apache.org/vo4a6
-----------------------------------------
Attachment AN: Report from the Apache Knox Project [Larry McCay]
-----------------------------------------
Attachment AO: Report from the Apache Kylin Project [Li Yang]
## Description:
The mission of Apache Kylin is the creation and maintenance of software related
to a distributed and scalable OLAP engine
## Project Status:
Current project status: Ongoing with low activity for the last quarter
Issues for the board: none
## Membership Data:
Apache Kylin was founded 2015-11-18 (10 years ago)
There are currently 52 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08.
- No new committers. Last addition was Pengfei Zhan on 2024-11-12.
## Project Activity:
5.0.2 was released on 2025-03-27. We are still in the early days of Kylin v5.
A couple of users are testing the new version, especially its vector engine
capability with the integration with Apache Gluten (https://gluten.apache.org/).
Some reported a 4x-5x performance improvement comparing to Kylin v4. Yet more
testing is required before production deployment.
## Community Health:
Not much coding was taking place, except for one or two bug fixes.
The next minor release 5.0.3 is planned around end of August. By the
activity metrics shall climb.
-----------------------------------------
Attachment AP: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AQ: Report from the Apache Logging Services Project [Piotr Karwasz]
## Description:
The mission of the Apache Logging Services project is to create and maintain
software for managing the logging of application behavior, and for related
software components.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
- Founded: 2003-12-17 (22 years ago)
- Committers: 47 (19 active)
- PMC Members: 23 (15 active)
- Committer-to-PMC ratio: 2:1 overall; 1:1 among active members
Community changes, past quarter:
- No new PMC members. Last addition was Jan Friedrich on 2024-08-07.
- No new committers. Last addition was Jeff Thomas on 2025-02-27.
## Project Activity:
At the time of the last report (2025-05-14), Apache Logging Services had
three main active components: Log4cxx, Log4net, and Log4j.
Their current status:
Log4cxx: Active, moderate activity.
- Releases: log4cxx-1.5.0 (2025-08-03)
Log4j: Active, moderate activity.
- The project is adapting to Review-then-Commit, balancing contributors’
immediate needs with a more collaborative, consensus-driven approach.
- Released version 2.25.0, with 3.0.0-beta4 development in progress.
- Releases: log4j-2.25.0 (2025-06-16), log4j-2.25.1 (2025-07-11)
Log4net: Active, low activity.
- Release 3.2.0 is in progress, with completion delayed due to the
holiday period.
- Releases: None this quarter (last: log4net-3.1.0, 2025-05-12)
## Community Health:
The project community remains healthy, supported by a steady flow of bug
reports and the emergence of new contributors. Increased traffic on
`dev@logging` is largely due to GitHub Discussions being mirrored to the
mailing list.
-----------------------------------------
Attachment AR: Report from the Apache Logo Development Project [Daniel Gruno]
The Logo Development committee concluded its second round of polling in July
of 2025. The consensus of the committee is that we have found a logo candidate
with general approval of the foundation membership, and will be presenting the
proposed candidate to the board.
The committee has furthermore agreed, by consensus, to submit a resolution to
disband the logo development committee, should the board be satisfied that the
task of the committee has been completed.
Some members of the committee that have expressed the idea of continuing with
a logo development committee for the sake of aiding projects looking for
either new logos or redesigning older ones, though the general feeling seems
to be that this is outside the mission/remit of the committee, and would be
better suited for Marketing & Publicity to handle.
-----------------------------------------
Attachment AS: Report from the Apache Lucene.Net Project [Shad Storhaug]
## Description:
The mission of Lucene.Net is the creation and maintenance of software related
to Search engine library targeted at .NET runtime users.
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: None
## Membership Data:
Apache Lucene.Net was founded 2012-08-15 (13 years ago)
There are currently 16 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ron Clabo on 2022-03-03.
- No new committers. Last addition was Ron Clabo on 2021-06-03.
## Project Activity:
Apache Lucene.Net delivered the latest 4.8.0-beta00017 release on 2024-10-29.
Activity continues towards a final 4.8.0-beta00018 release, although activity
has decreased since the last report. We are still focusing on completing work
on ICU4N and upgrading J2N to support System.Memory types to allow for more
efficient memory management. Lucene.Net is undergoing several breaking API
changes to stabilize the API for for the 4.8.0-beta00018 release.
We are working on a project for the Google Summer of Code to provide packages
with deeper integration with .NET dependency injection APIs.
We are also working on a set of code analysis tools and code fixes for
automating project-specific code issues and formatting to automate managing
code consistency across the codebase.
## Community Health:
- dev@lucenenet.apache.org had a 91% decrease in traffic in the past quarter
(19 emails compared to 198)
- 36 commits in the past quarter
- 3 code contributors in the past quarter
- 8 PRs opened on GitHub, past quarter
- 7 PRs closed on GitHub, past quarter
- 14 issues opened on GitHub, past quarter
- 10 issues closed on GitHub, past quarter
-----------------------------------------
Attachment AT: Report from the Apache MADlib Project [Ed Espino]
## Description:
The mission of Apache MADlib is the creation and maintenance of software
related to a scalable, Big Data, SQL-driven machine learning framework for Data
Scientists
## Project Status:
Current project status: At risk
Issues for the board: Can the board provide guidance on the official
protocol for formally proposing the inclusion of Apache MADlib under
the Apache Cloudberry (Incubating) project? Without such inclusion,
the MADlib project is effectively in a state approaching the Apache
Attic.
## Membership Data:
Apache MADlib was founded 2017-07-18 (8 years ago)
There are currently 17 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ed Espino on 2023-03-22.
- No new committers. Last addition was Ed Espino on 2023-03-23.
## Project Activity:
Recent releases:
v2.1.0 was released on 2023-09-08.
v2.0.0 was released on 2023-06-23.
v1.21.0 was released on 2023-03-01.
## Community Health:
There is essentially zero community activity. This is due to the
Broadcom community withdrawl as they took the Greenplum product
closed source.
-----------------------------------------
Attachment AU: Report from the Apache ManifoldCF Project [Piergiorgio Lucidi]
## Description:
The mission of ManifoldCF is the creation and maintenance of software related
to Framework for connecting source content repositories to target repositories
or indexes.
## Issues:
None
## Membership Data:
Apache ManifoldCF was founded 2012-05-15 There are currently 25
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, since last report in August:
- No new PMC member. Last addition was made on 2023-08-03.
- No new committers. Last addition was on 2019-08-17.
## Project Activity:
No significant new development at the moment, we are currently releasing
2.29 still waiting for the final votes. I'll ping all the contributors in order
to receive feedback. Upgrading to OpenJDK 21 remains the big change and probably
some connectors must be removed or rewritten from scratch.
We still have to figure out how to proceed for:
- Removing legacy connectors
- Updating connectors
- Resolving vulnerabilities
- Adding new connectors (RAG Output Connectors)
- Upgrade of the software architecture (from In-Process to Out-Of-Process)
I have to encourage greater involvement from all the contributors about
those topics.
Recent releases:
SDK 1.02 released on 2025-02-10
2.28 was released on 2025-01-15
2.27 was released on 2024-09-26
2.26 was released on 2023-11-01
2.25 was released on 2023-06-01
## Community Health:
No new pull requests at the moment and we don't have activity at the moment.
-----------------------------------------
Attachment AV: Report from the Apache OpenWhisk Project [Dave Grove]
## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (6 years ago)
There are currently 54 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cosmin Stanciu on 2022-02-22.
- No new committers. Last addition was Luke Roy on 2023-03-06.
## Project Activity:
Since the May board report, there have been a handful of code contributions.
The most significant one was a set of changes from an Apache OpenServerless
(incubating) community member to upgrade some of the core OpenWhisk Java
components from Java 11 to Java 17 and enhance our build to produce
multi-arch Docker images. The other contributions were routine PRs by a
current OpenWhisk committer to openwhisk-runtime-go and openwhisk-runtime-python
to maintain currency with the upstream language runtimes.
The most recent releases were part of a wave of openwhisk-runtime releases
made in August/September 2024:
openwhisk-runtime-java-1.20.0 was released on 2024-09-23.
openwhisk-runtime-php-1.21.0 was released on 2024-09-23.
openwhisk-runtime-python-1.20.0 was released on 2024-09-23
openwhisk-runtime-swift-1.19.0: was released on 2024-09-23
openwhisk-runtime-dotnet-1.18.0: was released on 2024-09-13
openwhisk-runtime-docker-1.16.0: was released on 2024-09-07
openwhisk-runtime-nodejs-1.23.0: was released on 2024-09-07
openwhisk-runtime-go-1.25.0: was released on 2024-09-05
## Community Health:
Despite the blip of activities, I see no fundamental change since the May
report, which is repeated below.
There are sufficient PMC members paying attention to handle security issues,
vote on releases, and answer the relatively low volume of user questions that
we get (mainly via GitHub issues).
With the exception of a small number of academic research projects, users of
OpenWhisk have moved on to other serverless platforms. Given the significant
size of the code base, the lack of ongoing development effort, and the
declining usage of OpenWhisk, the project appears to be winding down and may
need to seriously discuss a transition to the Attic in 2026.
-----------------------------------------
Attachment AW: Report from the Apache Ozone Project [Sammi Chen]
-----------------------------------------
Attachment AX: Report from the Apache Perl Project [Steve Hay]
## Description:
The mission of Perl is the creation and maintenance of software related to
Dynamic websites using Perl
## Project Status:
Current project status: Ongoing, with low activity
Issues for the board: none
## Membership Data:
Apache Perl was founded 2000-03-10 (25 years ago)
There are currently 21 committers and 11 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 Steve Hay on 2012-03-01.
- No new committers were added.
## Project Activity:
The last release was mod_perl-2.0.13 on 2023-10-21.
No new release is planned yet since there has been no development activity in
the last quarter, but will certainly be produced whenever necessary.
## Community Health:
Mailing list traffic has been quieter in this quarter, but that's not unusual.
It normally fluctuates between periods of quietness and flurries of activity
around some topic or other.
As per previous feedback, old Windows binary builds are now housed at
nightlies.apache.org/perl. I hope to produce a new build of the latest version
soon, though the apparent lack of Apache httpd/APR support for GCC on Windows
is hampering my attempts at making a build compatible with the popular
Strawberry Perl build on Windows (which is built with GCC).
-----------------------------------------
Attachment AY: Report from the Apache Phoenix Project [Istvan Toth]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Project Status:
Current project status: Ongoing
Issues for the board: No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-21 (11 years ago)
There are currently 61 committers and 38 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 Jacob Isaac on 2023-11-07.
- Nihal Jain was added as committer on 2025-08-05
## Project Activity:
Development activity was average, feature development concentrated on
improving CDC (Change Data Capture), TTL (Time to Live) and BSON support.
Phoenix 5.3.0 is now considered feature complete, and we plan to release it in
the next quarter. Phoenix 5.2.2 is still delayed due to lack of manpower to
coordinate the release.
Notable changes and new features in the quarter:
Dependency version updates:
PHOENIX-7683 Bump Apache Commons Lang 3 to 3.18.0 due to CVE-2025-48924
PHOENIX-7681 Update HBase 2.5 profile default version to 2.5.12
PHOENIX-7668 Update HBase 2.6 profile default version to 2.6.3
PHOENIX-7606 Remove HBase 2.4 support from master branch
PHOENIX-7600 Replace commons-logging with slf4j
HBase API usage updates in preparation for HBase 3.0:
PHOENIX-7476 HBase 3 compatibility changes for Filters, ByteStringer,
and Paging
PHOENIX-7478 HBase 3 compatibility changes: Replace ClusterConnection
with Connection API
PHOENIX-7481 HBase 3 compatibility changes: Cleanup deprecated APIs, HTable
and HTableDescriptor
PHOENIX-7505 HBase 3 compatibility changes: Update zookeeper handling
Reformatting the codebase with Spotless:
PHOENIX-7676 Update checkstyle checker.xml based on spotless rules
PHOENIX-7443 Add Spotless to the pre-commit checks
PHOENIX-7442 Apply Spotless to reformat the entire codebase
PHOENIX-7675 Update spotless plugin to also format IT classes
PHOENIX-7441 Integrate the Spotless plugin and update the code template
CDC Feature related:
PHOENIX-7677 TTL_DELETE CDC event to use batch mutation
PHOENIX-7671 Fix CDCStreamIT for HBase 2.6
PHOENIX-7664 Remove EmptyColumnOnlyFilter and FirstKeyOnlyFilter for
CDC scanners
PHOENIX-7658 CDC event for TTL_DELETE to exclude pre-image if PRE
scope is not selected
PHOENIX-7584 Conditional TTL on SYSTEM.CDC_STREAM
PHOENIX-7653 New CDC Event for TTL expired rows
PHOENIX-7652 : Clear CDC Stream metadata when table is dropped
PHOENIX-7643 : Add parent partition start time to CDC_STREAM table
PHOENIX-7636 CDC on table with case-sensitive pk columns fails to read change
records
PHOENIX-7634 : Change stream name delimiter
PHOENIX-7609 : CDC creation fails when data table has case sensitive name
TTL feature related:
PHOENIX-7677 TTL_DELETE CDC event to use batch mutation
PHOENIX-7661 Clean up old framework for TTL masking and expiration
PHOENIX-7674 Fix Bson3IT for HBase 2.6
PHOENIX-7667 Strict vs Relaxed TTL
BSON feature related:
PHOENIX-7551 BSON_VALUE_TYPE function to return the data type of
BSON field value
PHOENIX-7673 BSON Condition Function size()
PHOENIX-7663 : BSON Condition Function field_type()
PHOENIX-7674 Fix Bson3IT for HBase 2.6
PHOENIX-7662 BSON Condition Function contains()
PHOENIX-7545 BSON_VALUE() to support returning sub-document
PHOENIX-7585 New BSON Condition Function begins_with()
PHOENIX-7654 Restrict BSON datatype in composite PK as last part of
the pk column
PHOENIX-7650 Default value support in BSON_VALUE() for all supported types
PHOENIX-7647 : BSON_UPDATE_EXPRESSION() set value if field key does not exist
PHOENIX-7641 Support placeholder for document field keys in BSON condition
expression
PHOENIX-7631 BSON_VALUE() to support returning binary value with
VARBINARY_ENCODED data type
PHOENIX-7617 BSON serialization should retain ByteBuffer offset
Other notable changes:
PHOENIX-7659: Leverage = ANY() instead of big IN list to do huge number of
point lookups in a single query
PHOENIX-7612 Fix Cell references in IndexRegionObserver
PHOENIX-7666 Index query failure with SkipScanFilter
PHOENIX-7671 Sync maxLookback from data table to indexes
PHOENIX-7626: Add metrics to capture HTable thread pool utilization and
contention
PHOENIX-7648 Introduce new Atomic Operation - ON DUPLICATE KEY UPDATE_ONLY
PHOENIX-7645 HighAvailabilityGroup can leak zookeeper connections
PHOENIX-7646 New PhoenixStatement API to return old row state in Atomic Updates
PHOENIX-7630: Return ResultSet for UPSERT with ON DUPLICATE KEY
PHOENIX-7639 Improve error handling in PhoenixMasterObserver
PHOENIX-7619 Excess HFiles are being read to look for more than required
column versions
PHOENIX-7627 Atomic Delete return row fails for case-sensitive schema and
table names
PHOENIX-7358 Upsert select result wrong when use order by in query
PHOENIX-7615: Fix NPE in handling NULL value
PHOENIX-7616 NPE when there are Conditional expressions on indexed columns
PHOENIX-7599: Fix count of rows scanned metric for uncovered indexes
PHOENIX-7610 Using CAST() on pk columns always result in full table scan
PHOENIX-7614 : Fix atmoic update return result with case sensitive table name
PHOENIX-7605 Adding ability to configure threadpool at CQSI level
PHOENIX-7608 : Partial index creation fails when creating it on a table
with case sensitive table name
PHOENIX-7586 :- Handle Role transitions for ActiveToStanby role in
Failover HAPolicy
## Community Health:
Overall community health is good. Most of the development is still done by our
core team of about a dozen active developers.
-----------------------------------------
Attachment AZ: Report from the Apache Pinot Project [Kishore G]
-----------------------------------------
Attachment BA: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats.
The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
is a tool that allows you to map XML files to generated Java classes via
XML Schema definitions.
## Project Status:
- Overall: Low activity/Mostly maintenance only
- Activity on the project is low with no-one willing/able to invest time to
look for new committers. This project is is in a mostly-maintenance mode
unless someone new starts to invest time.
- Note: None of the active committers wants to spend time looking for new
people, so suggesting to reach out to others or invest in "marketing" will
likely not lead to much improvement.
- The project still has enough active PMC members to vote on issues and
perform releases
## Membership Data:
Apache POI was founded 2007-05-16 (18 years ago) There are currently 41
committers and 34 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 Marius Volkhart on 2020-12-27.
- No new committers. Last addition was Marius Volkhart on 2020-12-19.
## Project Activity:
- Source code hosting was switched from Subversion to GitBox/GitHub in order
to make integrating Pull-Requests easier. This went smoothly and reduces
maintenance effort visibly.
- Discussion about moving from minimum Java 8 to Java 11 was done with the
result to do a last release with support for Java 8 and then upgrade
minimum requirements to Java 11.
## Project Release Activity:
- 5.4.1 was released on 2025-04-06.
- 5.4.0 was released on 2025-01-08.
- XMLBeans-5.3.0 was released on 2024-12-13.
## Community Health:
- There are a few bug-reports and user-questions which indicates that Apache
POI is still in use. Questions via email or on Stackoverflow usually get
answers.
- Bug-numbers slowly increase over time. Some newly reported issues are
fixed, but we usually get more bugs/questions reported than are addressed
by the small number of active committers, so some bugs do not get attention
any more.
- We have a very small number of active committers. There are very few
potential candidates and no-one plans to spend effort to go looking for new
ones.
### XMLBeans
- It seems there are is a small but active set of users of XMLBeans besides
Apache POI itself.
- Bug influx for XMLBeans is very low in general because it is a stable
project in maintenance-only mode.
## Bug Statistics:
### Apache POI
- 627 bugs are open overall (+3)
- Having 143 enhancements (-1)
- Thus having 484 actual bugs (+3)
- 120 of these are waiting for feedback (-1)
- Thus having 364 actual workable bugs (+4)
- 3 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {XSSF=105, HSSF=80, SS
Common=43, HWPF=35, XSLF=31, XWPF=20, POI Overall=14, SXSSF=8, POIFS=7,
HSMF=6, OPC=5, HPSF=4, HSLF=3, HPBF=1, SL Common=1, XDDF=1}
### Apache XMLBeans
- 165 open issues (+2)
- 118 Bug (+1)
- 28 Improvement (+-0)
- 15 New Feature (+-0)
- 2 Wish (+-0)
- 2 Task (+1)
-----------------------------------------
Attachment BB: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, .Net, Go, Java/JMS, Python, and Ruby.
# Releases:
- There were no releases this quarter.
# Community:
- The main user and developer mailing lists continue to be active and
JIRAs are being raised and addressed in line with prior activity levels.
- There were no new PMC member additions in this quarter.
The most recent new PMC member is Daniil Kirilyuk, added 22nd January 2024
- There were no new committer additions in this quarter.
The most recent new committer is Daniil Kirilyuk, added 17th February 2023
# Development:
- ProtonJ2 is nearing its 1.0.0-M24 release including various bug fixes,
dependency updates, and improvements such as usability tweaks, new APIs
for the test peer, and the ability to use with either Netty 4.1 or 4.2.
- Qpid JMS is nearing its 1.14.0 and 2.8.0 releases with dependency
updates, and improvements around use with either Netty 4.1 or 4.2.
- Progress continues on Broker-J towards a 10.0.0 release, bumping the
minimum required Java version to Java 17 to facilitate use of Jetty 12,
various other cleanups, dependency updates, and changes to replace
usages of Guava with built-in Java methods or focused alternative deps
such as caffeine.
- Work is ongoing around cleaning up older areas of the Proton core and its
language bindings, with improvements around flow control and delivery
fairness, and various updates to the Python binding. Work continues on
adding transaction support for the C++ binding and other API cleanup
towards the next release and a later removal of deprecated APIs/features
in a new major version.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BC: Report from the Apache Ratis Project [Tsz-wo Sze]
## Description:
The mission of Apache Ratis is the creation and maintenance of software related
to a highly customizable Raft protocol implementation in Java.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Ratis was founded 2021-02-16 (4 years ago)
There are currently 31 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- Xinyu Tan was added to the PMC on 2025-06-22
- No new committers. Last addition was Xinyu Tan on 2024-08-27.
## Project Activity:
We released Ratis 3.2.0 on 2025-06-24. It was a minor release with
improvements and bug fixes. It also updated the Ratis-Thirdparty dependency
to 1.0.9.
We also released Ratis-Thirdparty 1.0.9 on 2025-05-02. It mainly updated
the versions of gRPC and Netty dependencies to 4.1.119.Final and 1.71.0,
respectively. In release 1.0.8, the versions of gRPC and Netty were
1.69.0 and 4.1.115.Final, respectively. It was known to the gRPC community
that gRPC 1.69.0 had a HTTP2 frame corruption bug with Netty 4.1.115.Final.
It indeed caused test failures on our upstream Apache Ozone project.
## Community Health:
The project is healthy. In this quarter, we have higher traffic in both the
dev@ (104% increase) and the user@ (220% increase) mailing lists. It
probably is due to the release discussion and voting. We also have 32 JIRAs
opened and 39 JIRA closed.
-----------------------------------------
Attachment BD: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment BE: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat, Postgres and MySQL, and is known to run on other Java servers
and relational databases.
## Project Status:
The project is mostly dormant with most activity around updating
dependencies, making sure the code runs on the latest Java releases and
security fixes.
## Membership Data:
Apache Roller was founded 2007-02-20 (18 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:
- No new PMC members. Last addition was Michael Bien on 2021-05-24.
- No new committers. Last addition was Yash Maheshwari on 2021-09-01.
## Project Activity:
We released Roller 6.1.5 in April 2025 oh yeah!!
## Community Health:
The Roller community is healthy enough to maintain Roller and make bug
fix and security releases.
-----------------------------------------
Attachment BF: 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: Healthy, we continue to make fixes to Samza
## Membership Data:
Apache Samza was founded 2015-01-22 (11 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:
We continue to make fixes to Samza, as we identify issues. Notable fixes:
* Resolve multiple concurrency issues
* Fixed Race conditions in pathing Samza jar manifest creation
* Recent Discussion on fixing process leaks in Posix Based
Statistics Getter; Please see https://github.com/apache/samza/pull/1717
## Community Health:
Activity has been relatively low in recent months, with limited
contributions and fewer discussions on the mailing lists.
We remain committed to the project’s goals.
-----------------------------------------
Attachment BG: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
The mission of Santuario is the creation and maintenance of software related to
XML Security in Java
## Project Status:
Current project status: The Java project is actively maintained and PRs are
getting merged and releases made.
Issues for the board: Nothing to report
## Membership Data:
Apache Santuario was founded 2006-06-27 (19 years ago)
There are currently 18 committers and 7 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 Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Joze Rihtarsic on 2024-05-14.
## Project Activity:
It was a quiet quarter for the project with no new releases or significant
issues fixed.
## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC
-----------------------------------------
Attachment BH: Report from the Apache SDAP Project [Nga Thien Chung]
## Description:
The mission of Apache SDAP is the creation and maintenance of software related
to an integrated data analytic center for Big Science problems
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SDAP was founded 2024-04-16 (a year ago)
There are currently 22 committers and 15 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 Grace Llewellyn on 2024-06-23.
- No new committers. Last addition was Truc Nguyen on 2025-01-18.
## Project Activity:
Last SDAP release was 1.4.0 on 2024-11-04.
A JPL summer intern has been leveraging Apache Sedona to analyze Earth
Science in situ data and is looking at the possibility of integrating
Sedona within the SDAP ecosystem.
The AIST Fire Alarm Digital Twins team delivered a hands-on tutorial to students
from NASA's Student Airborne Research Program at UC Irvine on 2025-07-14. The
tutorial included an introduction to SDAP.
## Community Health:
### Mailing List
Since last quarter, dev@sdap.apache.org had 3 new threads.
### Contributors
Since last quarter, the SDAP community has merged 1 PR and created/updated
1 Jira issues.
There has been much lower activity this quarter than usual because most
community members have been focused on maintaining operational deployments
of SDAP for various NASA projects. There are a few in progress PRs
(automated AWS credential management and automated data ingest) that the
community will try to wrap up and release soon.
-----------------------------------------
Attachment BI: Report from the Apache Sedona Project [Jia Yu]
## Description:
The mission of Apache Sedona is the creation and maintenance of software
related to a big geospatial data processing engine. It provides an easy to use
APIs for spatial data scientists to manage, wrangle, and process geospatial data
## Project Status:
Current project status: ongoing. high activities.
Issues for the board: No issues.
## Membership Data:
Apache Sedona was founded 2022-12-20 (3 years ago)
There are currently 22 committers and 18 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 Furqaan Khan on 2024-08-20.
- No new committers. Last addition was Feng Zhang on 2025-03-31.
## Project Activity:
We released Sedona 1.7.2 in July this year as a maintenance update. Our next
major release, 1.8.0, is planned for next month. We are actively working on
the following key features for Sedona 1.8.0:
1. Java 11 support
2. Geography type and operators
3. Spark 4.0 support
4. GeoPandas API integration with Sedona
5. PyFlink support
6. More accurate ST_Transform
## Community Health:
The community remains healthy. We recently transitioned from the JIRA ticket
system to GitHub Issues to improve collaboration with new contributors.
Several new contributors joined the project over the summer and made
significant contributions. We also moved all PR notifications from the dev
mailing list to the issues mailing list, so you may notice a significant
change in traffic between the two lists.
-----------------------------------------
Attachment BJ: Report from the Apache Serf Project [Daniel Sahlberg]
## Description:
The mission of the Apache Serf project is creating and maintaining of software
related to HTTP and associated protocols.
## Project Status:
The project has sufficient PMC oversight.
There are no threats to the sustainability or resilience of the project,
although the project is in general very much dormant due to lack of
need/requirements from our users. However, see Community Health for an update
on the last quarter.
The project has no requests for the Foundation.
## Membership Data:
Apache Serf was founded 2015-08-18 (10 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:
- Graham Leggett was added as committer and to the PMC on 2025-06-28
- Timofei Zhakov was added as committer and to the PMC on 2025-06-21
(The project standard operating procedure is committer === PMC member, the two
exceptions are persons retiring from the PMC but staying as committers).
## Project Activity:
Recent releases:
* 1.3.10 was released on 2023-05-31.
* 1.3.9 was released on 2016-08-31.
## Community Health:
Serf and Subversion have a significant overlap of committers and PMC members
and Subversion is the only (known) open source project using Serf. New
features in Subversion are therefore the primary driver for development in Serf.
The last quarter saw a significant rush of activity starting by a Subversion
user inquiring about the possibility to add built-in MFA authentication to
Subversion. We have exciting new development on trunk related to adding
user defined authentication schemes that will be helpful to implementing MFA
authentication in Subversion.
There is also new support for using URIs to identify certificates (previously
only files were possible), this should make it easier to work with for
example Windows Certificate store. To improve error reporting there is a new
error callback that can relay information from the underlying SSL engine.
We have also seen work on making the CMake based build system feature
compatible with the primary SCons build system. It has been suggested to
deprecate one build system to simplify maintenance but no decision was made.
Several people chimed in to support providing a CMake build system. The next
release will most probably support both build systems.
Finally we've added support for asynchronous DNS lookup using either the
Unbound DNS resolver or by creating a background tread to call APR's resolver.
Discussion was started regarding making a new minor release. 1.4.x was
branched from trunk in 2018 but never made it to release, we will probably
declare 1.4.x as "never released" and the next release will be 1.5.0. Hopefully
we will make a new release during the next three months.
-----------------------------------------
Attachment BK: Report from the Apache ServiceComb Project [Bao Liu]
## Description:
The mission of Apache ServiceComb is the creation and maintenance of software
related to a microservice framework that provides a set of tools and components
to make development and deployment of cloud applications easier.
## Project Status:
Current project status: [Ongoing]
Issues for the board: [None]
## Membership Data:
Apache ServiceComb was founded 2018-10-17 (7 years ago)
There are currently 38 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cheng Youling on 2024-10-12.
- No new committers. Last addition was Zhangjian He on 2025-01-28.
## Project Activity:
ServiceComb Java Chassis 3.3.0 was released on 2025-06-24.
ServiceComb Java Chassis 2.9.0 was released on 2025-06-23.
ServiceComb Java Chassis 2.8.25 was released on 2025-06-17.
ServiceComb Java Chassis 3.2.6 was released on 2025-06-03.
## Community Health:
Overall, community health is good. ServiceComb Java Chassis made 4 releases,
and there are some bug fixes and improvements. PMC member released 2.9.0 to
compatible with 2.8.x with some 3rd party upgrading.
-----------------------------------------
Attachment BL: Report from the Apache ShardingSphere Project [Liang Zhang]
## Description:
The mission of Apache ShardingSphere is the creation and maintenance of
software related to a database clustering system providing data sharding,
distributed transactions, and distributed database management
## Project Status:
Current project status: Good
Issues for the board: None
## Membership Data:
Apache ShardingSphere was founded 2020-04-15 (5 years ago)
There are currently 63 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Longtao Jiang on 2024-03-28.
- No new committers. Last addition was Chenyang Ma on 2024-05-27.
## Project Activity:
We are preparing to release the final version of 5.x,
currently wrapping up remaining issues,
which involves significant development efforts.
Additionally, our community has gained new users in Eastern Europe
and achieved full support for the Firebird database,
it is a welcome development.
## Community Health:
The community has matured and stabilized on existing features.
The new growth driver,
MCP server, will be fully launched in version 6.0.
-----------------------------------------
Attachment BM: Report from the Apache ShenYu Project [Yu Xiao]
## Description:
ShenYu is a Java native API Gateway for service proxy,
protocol conversion and API governance.
## Project Status:
Current project status: Good Healthy.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache ShenYu was founded 2022-07-20 (3 years ago)
There are currently 57 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Hongyu Liu was added to the PMC on 2025-05-15
- No new committers. Last addition was Shinan Chen on 2024-08-30.
## Project Activity:
We are pre release version 2.7.0.2
Software development activity:
- We added bootstrap instances status.
- We added mcp server plugin.
- We added ai-request-transformer plugin.
- We added mcp streamable http.
- We fixed data buffer leak.
- We fixed modify addproxyselector function have some error.
- We fixed not change singletion config .
- We fixed AiTokenLimiterPlugin appendResponse .
- We fixed h2 ai proxy sql lack of selector handle .
- We refactor update badge.
- We refactor useless empty paths.
- We refactor modify dubbo plugin configuration based on selector.
Meetups and Conferences:
- Community meetings(4) to discuss development tasks and how to build
an open governance community.
- 3 topic for ospp (ing)
## Community Health:
Overall community health is good.
Since the last report, add new 6 contributors added (currently:409).
add +3 subscribers to dev@shenyu.apache.org mailing (currently:511)
-----------------------------------------
Attachment BN: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
The mission of Apache SIS is the creation and maintenance of software providing
data structures for developing geospatial applications compliant with the model
of OGC/ISO international standards.
## Project Status:
Current project status: ongoing with high activity, but from 2 developers.
Issues for the board: following the June report, the board has expressed
concerns about SIS sustainability.
## Membership Data:
Apache SIS was founded 2012-09-19 (13 years ago)
There are currently 22 committers and 17 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 Alexís Manin on 2021-05-27.
- No new committers. Last addition was Bruno P. Kinoshita on 2021-06-23.
## Project Activity:
A release of Apache SIS is in preparation, with a tentative RC1 by August 12.
This release is made possible by the quasi-completion of the upgrade of a
feature considered as essential to SIS, which needed work because of changes
external to SIS (related to progress in geodesy). More details are in [1]. In
parallel, we discussed on a private channel (for now) with developers of the
Apache Sedona project, which were testing Apache SIS as an alternative to
their LGPL dependency for coordinate transformations. The exchanges were very
positive. Because of a bug in Apache SIS 1.4, the Sedona developers expressed
the wish for a 1.4.1 release soon. Since it would have been a release based on
2-years old code, we proposed (with the agreement of Sedona developers) to
rather make a SIS 1.5 release sooner, by moving to the SIS 1.6 roadmap all
the tasks that were remaining on the SIS 1.5 roadmap [2], except the above-cited
essential upgrade.
The developers of Apache Sedona have expressed concerns about the long delay
between Apache SIS releases, and expressed a desire for faster cadence. Having
users expressing this need is sufficient for producing releases more often. It
was not done before because, before Sedona, the known Apache SIS users were
interested mostly in above-cited essential upgrade. For those users, a release
of SIS without that upgrade was equivalent to no release.
[1] https://lists.apache.org/thread/gfo4f0b1t4916g888oqzzqwvqvov7mvy
[2] https://issues.apache.org/jira/projects/SIS/versions/12352679
## Community Health:
While Apache SIS is currently a project with 1~2 active developers, these
developers were not at the project's origin. Apache SIS has been created by
contributors from NASA and others. The 17 PMC members are in majority
developers from these early days, and the current developers joined SIS later.
The flow of commits caused the other developers to become progressively less
active, but mostly because it was difficult to follow the amount of changes
when programming is not their primary job. In 2023 we asked by private emails
who would like to become emeritus, but got a response from a minority of
members. We moved to emeritus only the members who expressed that wish.
A barrier for contributors is the current build system of Apache SIS. The
project moved to module source hierarchy [3], because this is the only way to
manage a multi-modules (in JPMS sense) project with maximum safety (i.e., with
warnings when referring to non-existent modules). Unfortunately, despite the
fact that module source hierarchy exists since Java 9, none of the major build
tools (Maven or Gradle) supports it. Because Gradle is highly customizable, it
was possible to tweak the build for making it works. But opening the SIS
project in an IDE gives bad results. We got it to work at least partially in
NetBeans with a customized Ant + Ivy NetBeans project that we maintain in
parallel with the official Gradle build, but this is highly unsatisfying.
Reports of this problem to Maven or Gradle initially faced incomprehension, as
few peoples are aware of module source hierarchy or see its advantage. On the
Maven developer mailing list, some peoples having bad experiences with JPMS in
their own projects blamed JPMS without realizing that their difficulties were
rather due to they way that Maven 3 "supports" JPMS. For resolving this issue,
we had to become contributors of Maven 4. We started this effort two years
ago, and Martin is now a Maven committer. We pushed for a fundamental change in
the way that source codes are declared in Maven 4 projects (a new `<Source>`
element in POM), which resolves (pending upgrade of all impacted Maven
plugins) not only the module source hierarchy problem, but also
opportunistically makes easier to do multi-releases project and uniformises
the management of different kinds of sources (Java, resources, etc.). This
change is already released in Maven 4.0.0-rc-4, together with the resolution
of other difficulties that SIS was facing (control on whether to put
dependencies on the class-path or module-path). We rewrote the Maven Compiler
Plugin for leveraging these new features, together with writing new user
guides [4]. Most (but not yet all) of this work is already integrated in the
main branch of the Maven Compiler Plugin. The compiler plugin at [4] is
already capable to compile Apache SIS cleanly, without any of the hack that we
had to do for Gradle. Upgrades of Maven Clean Plugin and Maven Resource Plugin
are underway. The Maven Surefire Plugin and Maven JAR Plugin will follow
later. After all these plugins have been upgraded, we will be able to replace
the hacked Gradle build system by a clean Maven 4 build system. The last step
will be IDE integration, but this work is already in progress on NetBeans
side. An upgrade of NetBeans to Maven 4 is in progress, and we had an exchange
with a NetBeans contributor about this new `<Source>` Maven element.
It could be argued that Apache SIS should rollback to a more traditional
package source hierarchy [3] until all the Maven work is completed. But it
would be a significant effort better spent on Maven itself, especially since
we would have to rollback again to the module source hierarchy after Maven 4
is ready. Furthermore, the large effort that we spent in setting up the
current Apache SIS build system has been critical for understanding the issues
with Maven and Gradle. The contributions that we are doing now in Maven would
not have been possible without this experience. And we still need the current
Apache SIS project layout for testing the new Maven plugins (we already have
an Apache SIS branch which is partially built with Maven 4). In the meantime,
while opening the Apache SIS project in an IDE is difficult, it is not
impossible.
Another barrier for newcomers is that contributing to Apache SIS requires not
only some Java skills, but also some knowledge of OGC/ISO international
standards. For example, it is very tempting to write Java code as if the Earth
was a flat two-dimensional plane. Integration with OGC/ISO standards forces
the developer to consider the fact that the Earth is round, flattened at poles
and located in a coordinate system having also vertical and temporal axes,
among other difficulties. On one side, asking new contributors to master this
complexity is asking too much. On the other side, we cannot integrate code in
the core modules of Apache SIS without consideration for those problems. For
example, if we want to take in account the temporal axis, we need to do that
at every steps of a chain of coordinate operations. A single step not handling
time correctly is sufficient for breaking the whole chain. As a compromise, we
separated the Apache SIS modules in 3 groups: "endorsed", "incubator" and
"optional" (the latter is for licensing constraints). Contributions that have
not yet be reviewed for above-cited constraints go in "incubator". After they
have been carefully reviewed, they move to "endorsed". This layout has been
established a few years ago, as a side-effect of the move to module source
hierarchy.
[3] https://s.apache.org/javac-directory-hierarchies
[4] https://github.com/Geomatys/maven-compiler-plugin/wiki
-----------------------------------------
Attachment BO: Report from the Apache Solr Project [Alessandro Benedetti]
## Description:
The mission of Apache Solr is the creation and maintenance of software related
to a highly scalable, distributed document search and analytics
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Solr was founded as a TLP on the 16/02/2021 (4 years ago) after 15
years within the Lucene project. There are currently 99 committers and 61 PMC
members in this project. The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. The last addition was Michael Gibney on 20/12/2022.
- No new committers. The last addition was Matthew Biscocho on 25/04/2025.
## Project Activity:
Recent releases:
* Solr 9.9.0 was released on 24/07/2025
Areas of development & interest:
* Prepare for the upcoming 10.0 release (including the big Lucene upgrade)
* API renovation and migration continue
* LLM integration out of the box in Solr for text vectorisation
(query/indexing time)
* Dense vector search improvements and new features catching up with Apache
Lucene
## Community Health:
The quarter has been quite active thanks to various initiatives:
- Search technology survey to explore the latest trends of interest and areas
of improvement in Solr (the survey has been designed by members of the PMC
and independent contributors). Results: https://docs.google.com/
document/u/1/d/1qK3Zkm_T1c_aewrjL3N1k0EqmvA-gl3CdFcpuB0XT0I/edit?usp=sharing
- Conferences: Berlin Buzzwords (https://2025.berlinbuzzwords.de/sessions/) is
one of the major conferences on search (industry target), Mices
(https://mices.co/#programme) is a satellite event happening in the same
week in Berlin, focused on e-commerce search. There were many talks about
Apache Solr (or partially referring to it with interesting ideas):
* Performance Tuning Apache Solr for Dense Vectors, Kevin Liang
*AI-Powered Search Results Navigation with LLMs & JSON Schema, Ilaria Petreti,
Anna Ruggero, Edward Lambe
*End-to-End Semantic Search with Apache Solr 9.8 LLM Module, Alessandro
Benedetti
*Taking an abandoned Solr search from zero to GenAI hero, Torsten Bøgh Köster
*Learning-To-Rank Framework - farm your ranking models, Ilan Dubois and Marcin
Gumkowski
- Dense Vector Group: Following an idea of a contributor (Kevin Liang), we
started the dense vector group initiative, meeting monthly. I'm personally
coordinating it via Jira
(https://i
ssues.apache.org/jira/secure/RapidBoard.jspa?projectKey=SOLR&rapidView=633),
and we are seeing a lot of activity with many Pull Requests under review.
-Hackathon scheduled for next Community Over Code
The community feels healthy, active and with new contributors (that hopefully
will become committers).
-----------------------------------------
Attachment BP: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Project Status:
- We released Apache Spark 4.0 on May 23, 2025, and Apache Spark 3.5.6 on May
29, 2025.
- We released Apache Spark Connect Swift Client 0.1.0 on May 8, 2025;
0.2.0 on May 20, 2025; and 0.3.0 on June 4, 2025.
- We released Apache Spark Kubernetes Operator 0.2.0 on May 29, 2025, and
0.3.0 on June 4, 2025.
- We implemented release automation using GitHub Actions workflow, with Spark
3.5.6 as the first release under this new system.
- "Apache Spark 4.1 Preview 1" and "Apache Spark Connect Go Client
0.1.0" have successfully passed; the community is actively preparing the final
releases.
- Two SPIPs were recently accepted:
1. Real-Time Mode in Apache Spark Structured Streaming
2. Monthly Preview Release
- The PMC voted to add three new committers: Anton Okolnychyi, Daniel
Tenedorio and Anish Shrigondekar
Trademarks:
- No changes since last report.
Latest releases:
- Spark 3.5.6 was released on May 29, 2025
- Spark 4.0.0 was released on May 23, 2024
- Spark 3.5.5 was released on Feb 27, 2025
Committers and PMC:
- The latest committer was added on July 1, 2025 (Anton Okolnychyi).
- The latest PMC member was added on Jan 21st, 2025 (Jie Yang).
-----------------------------------------
Attachment BQ: Report from the Apache StormCrawler Project [Richard Zowalla]
## Description:
The mission of Apache StormCrawler is the creation and maintenance of software
related to an open source collection of resources for building low-latency,
scalable web crawlers on Apache Storm
## Project Status:
Current project status: active
Issues for the board: none
## Membership Data:
Apache StormCrawler was founded 2025-05-21 (3 months ago)
There are currently 10 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
As we are now in the European summer holiday period, contributions have
temporarily slowed — which is expected and typical for this time of year.
Despite this, we continue to receive pull requests and interest from outside
contributors, which is a strong and encouraging sign of ongoing engagement
with the project. There has also been discussion around the existing project
logo, particularly the need to convert it into an SVG format to better support
branding needs. While no final decision has been made yet, this conversation
marks a positive step toward improving our visual identity as part of our
broader TLP transition.
We’ve also started work on overhauling our documentation to support better
onboarding and contributor engagement. Trademark-related tasks are in the
early planning stages.
## Community Health:
The StormCrawler community remains healthy and stable. Although activity has
slightly slowed due to the start of the summer holiday season in Europe,
contributions from new participants continue to arrive — including pull
requests and outreach from individuals outside the established group. Our
current focus on improved documentation should lower the barrier to entry for
new users and contributors. We hope that these efforts will further strengthen
engagement and participation over time.
-----------------------------------------
Attachment BR: Report from the Apache StreamPipes Project [Philipp Zehnder]
## Description:
The mission of Apache StreamPipes is the creation and maintenance of software
related to a self-service Industrial IoT toolbox which enables non-technical
users to connect, analyze and explore IoT data streams
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache StreamPipes was founded 2022-11-16 (3 years ago)
There are currently 33 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 Zhenyu Luo on 2023-10-17.
- No new committers. Last addition was Marcel Frueholz on 2025-01-23.
## Project Activity:
- Added support for OPC UA certificate-based authentication to enhance security
- Improved Data Explorer functionality
- Addressed minor issues and implemented various bug fixes to
improve overall system stability and performance
## Community Health:
- Mentored a student as part of the Google Summer of Code program,
supporting contributions to the project
- There will be a StreamPipes presentation by members of the
community at the upcoming Community Over Code
-----------------------------------------
Attachment BS: Report from the Apache Subversion Project [Nathan Hartman]
## Description:
The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control
solution characterized by its reliability as a safe haven for valuable
data; the simplicity of its model and usage; and its ability to
support the needs of a wide variety of users and projects, from
individuals to large-scale enterprise operations.
## Project Status:
Current project status: Ongoing, mature.
Issues for the board: None at this time.
## Membership Data:
Apache Subversion was founded 2010-02-16 (15.5 years ago). Prior to
joining ASF, the project began in February of 2000 (25 years ago).
There are currently 90 committers and 49 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Graham Leggett was added to the PMC on 2025-07-12
- Graham Leggett was added as committer on 2025-07-13
- Peter Balogh was added as committer on 2025-07-11
## Project Activity:
Added two committers, one direct-to-PMC.
Numerous improvements to the codebase. Some highlights:
* Extensive build system improvements, especially regarding the newer
CMake build system and its support for pkg-config, APR 2.x, Serf
2.x, macOS, clang, and newer GCC
* CI improvements in the GitHub Actions (GHA) workflows
* Test suite improvements, including Subversion's SWIG Python
bindings, ra_serf, and XML validation
* Documentation cleanups
* Improvements in the mailer.py hook script, which is used in ASF's
infrastructure to send notification emails about commits to the
ASF's Subversion repository
* Improvements in mod_dav_svn to allow configuring Subversion
repository locations via LocationMatch when served via Apache httpd
* Reimplemented macOS keychain support, as the older implementation
relied on macOS APIs which have been deprecated
* Improvements in locale encoding handling, including ongoing work to
process UTF-8 command line arguments and printing of locale
information in the 'svn --version --verbose' command
* Improvements in svnmucc and svnlook to make them more consistent
with the other Subversion binaries such as svn and svnadmin
* Improvements in stream I/O
* Numerous other refactorings and code cleanups throughout
Pending completion of support in Serf, there is an ongoing effort to
support Two-Factor Authentication (2FA) in Subversion.
Voted to adopt and adopted the ASF's Code of Conduct (CoC) as the
project's official CoC.
Discussion about dropping support for Python 2, which is End of Life
since 2020. Currently we only backport changes that do not break
support for Python 2 to Subversion's 1.14.x Long Term Support (LTS)
release line. (Subversion does not require Python, except for building
Subversion from sources, using Subversion's SWIG Python bindings, or
running any Python-coded hook scripts or other tooling.)
## Community Health:
The community appears healthy for a mature and stable project.
Activity has slowly but surely increased over the last few quarters.
Multiple developers monitor the mailing lists and respond when needed.
User questions usually receive helpful responses on the mailing lists,
from both project developers and community members. The codebase,
website, and project infrastructure continue to be improved.
Our community is fully volunteer-driven and we would like to thank
everyone for their support.
-----------------------------------------
Attachment BT: Report from the Apache Superset Project [Maxime Beauchemin]
## Description:
The mission of Apache Superset is the creation and maintenance of software
related to data exploration, analysis, visualization, and dashboarding
## Project Status:
Current project status: Active and buzzing!
Issues for the board: None
## Membership Data:
Apache Superset was founded 2020-11-17 (5 years ago)
There are currently 69 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Antonio Rivero was added to the PMC on 2025-07-16
- No new committers. Last addition was Mehmet Yavuz on 2025-03-24.
## Project Activity:
5.0.0 was released on 2025-06-23.
4.1.2 was released on 2025-03-24.
4.1.1 was released on 2024-11-15.
We're currently working to stabilize/test/release features including Theming
and more, to release a 6.0 version. We're also logging issues that might be
needed for a 5.0.1 release.
We're taking an active effort (as we have been for a while now) in whittling
away at older issues/PRs, and the repo is more "under control" by the day.
AI is (perhaps unsprisingly) playing a larger role in the lives of many
developers on the project, and we're seeing a new surge in activity. Humans
are thus far doing a great job of both leveraging these tools to create and
review code, and human oversight seems to be keeping things stable and on
track.
Lots of features and fixes, and more "grand plan" inititiatives remain in the
works. We're quite optimistic about the capabilities (and adoption) of
Superset over the coming months.
## Community Health:
Community Health Score (Chi): 9.60 (Super Healthy) 20,739 members on Slack,
67,537 GitHub Stars, and growing. Thanks to humans, we're seeing more issues
and PRs merged/closed, and seeing continual engagement from new contributors.
Thanks to bots, we're seeing a lower time to response on all issues/PRs, and
contributors are getting less "stuck" In general, sentiment, engagement seems
as high as ever!
-----------------------------------------
Attachment BU: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
The mission of Syncope is the creation and maintenance of software related to
Managing digital identities in enterprise environments
## Project Status:
Current project status: healthy.
Issues for the board: none.
## Membership Data:
Apache Syncope was founded 2012-11-21 (13 years ago)
There are currently 25 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Lorenzo Di Cola on 2023-05-22.
- No new committers. Last addition was Samuel Garofalo on 2022-07-29.
## Project Activity:
We are maintaining 3 active branches at present:
* 3_0_X - Syncope 3.0.X maintenance
* 4_0_X - Syncope 4.0.X maintenance
* master - preparation for upcoming Syncope 4.1.X
The work in the last weeks was headed to refine and bug-fix the code from
3_0_X and 4_0_X branches, which has recently brought the new releases 3.0.13 and
4.0.1.
Recent releases:
* 4.0.1 was released on 2025-08-08
* 3.0.13 was released on 2025-08-08
* 4.0.0 was released on 2025-05-23
* 3.0.12 was released on 2025-05-23
## Community Health:
We continue to observe a slight raise of questions and support requests from
newcomers.
Discussions about new features and improvements keep appearing and being
followed up in dev@.
-----------------------------------------
Attachment BV: Report from the Apache SystemDS Project [Matthias Boehm]
## Description:
Apache SystemDS is a machine learning (ML) system for the end-to-end
data science lifecycle from data preparation and cleaning, over
efficient ML model training, to scoring and debugging. ML algorithms
or pipelines are specified in a high-level language with R-like syntax,
or related Python and Java APIs, and the system automatically generates
hybrid runtime plans of local, in-memory operations and distributed
operations on Apache Spark.
## Issues for the Board:
- None
## Project Status:
- Current work focuses on adding the missing primitives for a number
benchmarks, a new API for the alignment of multimodal datasets,
a new backend for singlenode out-of-core operations, and incremental
refinements of major internal components for compression, GPUs,
federated operations, and the use of the Java vector API.
## Membership Data:
- Apache SystemDS was founded 2017-05-16 (incubator process entered
2015-11-02)
- Last PMC members added 2025-04-30 (Elias Strauss)
- Last committers added 2025-04-30 (Christina Dionysio)
- There are currently 37 committers and 28 PMC members in the project.
## Activity and Health:
- Code activity is healthy with 61 commits (-12%) in the last 3 months.
- Community growth is healthy with 20 active contributors (+17%)
in the last 3 months
- Communication is healthy, mailing list activity is improving,
additional work on better documentation.
## Releases:
- Apache SystemDS 3.3.0 was released on 2025-04-22.
- Apache SystemDS 3.2.0 was released on 2024-03-17.
- Apache SystemDS 3.1.0 was released on 2023-03-13.
- Apache SystemDS 3.0.0 was released on 2022-06-20.
- Apache SystemDS 2.2.2 was released on 2022-06-25.
- Apache SystemDS 2.2.1 was released on 2021-12-02.
- Apache SystemDS 2.2.0 was released on 2021-10-30.
- Apache SystemDS 2.1.0 was released on 2021-06-28.
- Apache SystemDS 2.0.0 was released on 2020-10-14.
- Apache SystemML 1.2.0 was released on 2018-08-24.
-----------------------------------------
Attachment BW: Report from the Apache TomEE Project [David Blevins]
-----------------------------------------
Attachment BX: Report from the Apache Traffic Control Project [Eric Friedrich]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning a large
scale content delivery network (CDN)
## Project Status:
Current project status: At risk Issues for the board: Challenges getting
sufficient review for PRs
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (7 years ago)
There are currently 31 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hamrick on 2023-02-07.
- No new committers. Last addition was Abdulrahman Elawady on 2023-09-21.
## Project Activity:
Project is mostly dormant of new development. Two new bugfix PRs were opened
by an contributor, but also did not receive reviews.
## Community Health:
Minimal mailing list traffic. Infrequent comments/questions on Slack channels,
but these are mainly from users. Minimal PMC responses, its more often users
helping users.
-----------------------------------------
Attachment BY: Report from the Apache Traffic Server Project [Bryan Call]
-----------------------------------------
Attachment BZ: Report from the Apache TsFile Project [Jialin Qiao]
-----------------------------------------
Attachment CA: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related to A
Java Servlet Web Application Framework and associated component library
## Project Status:
Current project status: Ongoing with low activity and at least 3 active PMC
members.
Issues for the board: none
## Membership Data:
Apache Turbine was founded 2007-05-16 (18 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 Jeffery Painter on 2017-11-12.
- No new committers. Last addition was Youngho on 2021-12-06.
## Project Activity:
Recent releases: Turbine 7.0 was released on 2025-06-16.
This was finally the (almost) last step in the release cycle for a major
release. What's missing is the release of the Turbine archetype module, which
is almost ready and may be finished next quarter and some optional Fulcrum
modules releases.
## Community Health:
As last quarter report mentioned Turbine might get some attention in an
upcoming event. Turbine project - as other projects - might need a community
manager to better communicate the efforts, achievements and processes outside
the Apache community, but within provided channels (general/user mailing lists,
website cleanup, github actions/environment..).
-----------------------------------------
Attachment CB: Report from the Apache Uniffle Project [He Qi]
## Description:
The mission of Apache Uniffle is the creation and maintenance of software
related to a unified remote shuffle service
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Uniffle was founded 2025-02-19 (6 months ago)
There are currently 24 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Xianjing Feng on 2025-05-07.
- No new committers. Last addition was Lu Yuan on 2025-04-10.
## Project Activity:
The community have some important features to improve the
Uniffle stabilityand performance.
The overlapping compression can improve 20% performance in
the production environment.
Meanwhile, LAB allocation can improve the stabiliy in the
production environment and reduce GC time of the Uniffle server.
Spark add a new UI. It will improve the system observation.
Users can know the Uniffle performance easily.
There are collaboration with other projects.
More native execution engines have supported Uniffle, such as Blaze.
## Community Health:
Overall community health is good.
The core contributors continously improve the performance and stability.
There are also some new contributors who joined the community.
More and more production optimization are contributed to the community.
-----------------------------------------
Attachment CC: 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 (19 years ago)
There are currently 15 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Thomas Mortagne on 2020-03-09.
## Project Activity:
Last release was Engine 2.4.1 on 2024-10-14
A new release is wanted by some contributors, but no dev has stepped up yet.
## Community Health:
There's been more email in the past quarter, but developer response has
slacked in a way that i think is more unhealthy than usual. I have no doubt
it will all be taken care of eventually, and suspect summer holidays and
travels and pinched the extra time people would otherwise contribute to
Velocity.
-----------------------------------------
Attachment CD: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment CE: Report from the Apache Whimsy Project [Dave Fisher]
## Description:
The mission of Apache Whimsy is the creation and maintenance of software
related to tools that help automate various administrative tasks or information
lookup activities
## Project Status:
- Current project status: Very low, Maintenance
- Issues for the board: None at this time
## Membership Data:
Apache Whimsy was founded 2015-05-19 (10 years ago)
There are currently 13 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- Dave Fisher was added to the PMC on 2025-07-15
- Dave Fisher was added as committer on 2025-07-16
## Project Activity:
We initiated a discussion on the mailing list about whether or not the PMC
is willing to develop whimsical tools using the same Python approach used
by both Infrastructure and Tooling - asfquart with asf oauth. It remains to be
seen what the Consensus will be. Stayed tuned.
## Community Health:
For some time there has been no need to develop the Agenda Tool, but there have
been quite a few developments elsewhere.
Development has slowed because the rest of the code is quite mature. There is a
downward trend in emails on the development mailing list. We will see if Whimsy
will become more like the STeVe project and support only the features that
remain, or if it shifts to increased activity as a place for members to develop
modern whimsical tools.
-----------------------------------------
Attachment CF: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components in order to engender such improvements.
## Project Status:
Current project status: The project activity is moderate.
Issues for the board: None.
## Membership Data:
Apache Xalan was founded 2004-09-30 (21 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. Last addition was Joseph Kessselman on 2023-08-07.
- No new committers. Last addition was Joseph Kessselman on 2023-06-29.
## Project Activity:
We are slowing inching towards three Xalan-Java goals: Another 2.x release, a
3.x alpha or beta release, and migrating the build from Ant to Maven.
## Community Health:
Our project health is moderate with a small handful of active committers. The
mailing list and Jira activity are low.
-----------------------------------------
Attachment CG: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment CH: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report
==================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
Issues for the Board
=====================
A trademark issue for FOP was identified related to a NuGet package name[1]
and we are working through resolution with help from trademarks@.
[1] FOP.dll 1.1.0
https://www.nuget.org/packages/FOP.dll
Activity
========
* No new releases since the last Board Report
* New versions of Apache Batik 1.19, Apache FOP 2.11, Apache FOP PDF Images
2.11 and Apache XML Graphics Commons 2.11 were released 2025-05-06
* All XMLGraphics project repositories have been migrated from Subversion to
GitHub/GitBox: https://github.com/apache/xmlgraphics-fop.git
* A proposal to migrate XMLGraphics projects from Jira to GitHub issues was
passed. Preliminary work to effect this migration has started. The migration
is ongoing.
Latest Versions of Apache XML Graphics Project Projects:
* Apache Batik 1.19 2025-05-06
* Apache FOP 2.11 released 2025-05-06
* Apache FOP PDF Images 2.11 released 2025-05-06
* Apache XML Graphics Commons 2.11 released 2025-05-06
We have migrated the Apache XML Graphics repositories for XML Graphics
Commons, FOP, FOP PDF Images and Batik to GitHub:
https://github.com/apache/xmlgraphics-commons.git
https://github.com/apache/xmlgraphics-fop.git
https://github.com/apache/xmlgraphics-fop-pdf-images.git
https://github.com/apache/xmlgraphics-batik.git
Project Health Report
=======================
New versions of Apache Batik 1.19, Apache FOP 2.11, Apache FOP PDF Images 2.11
and Apache XML Graphics Commons 2.11 were released 2025-05-06.
The level of community and developer activity remains at a consistent,
moderate, level with respect to the previous reporting period.
Recent PMC Changes
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds was approved for XML Graphics PMC Chair position on March 26,
2018.
Committers
==========
Currently 21 committers.
* No new committers added in the last 3 months
* Last committer added was João André Gonçalves Thursday, November 7, 2024
Most Recent Releases
====================
* Apache Batik 1.19 2025-05-06
* Apache FOP 2.11 released 2025-05-06
* Apache FOP PDF Images 2.11 released 2025-05-06
* Apache XML Graphics Commons 2.11 released 2025-05-06
= SUB PROJECTS =
================
APACHE BATIK
=====
Batik is a Java-based toolkit for applications or applets that want to use
images in the Scalable Vector Graphics (SVG) format for various purposes, such
as display, generation or manipulation.
Latest Release
------------
Apache XML Graphics Apache Batik 1.19 was released on May 6, 2025
* Bug fixes
APACHE FOP
===
Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL
formatting objects (XSL-FO) and an output independent formatter. It is a Java
application that reads a formatting object (FO) tree and renders the resulting
pages to a specified output. Output formats currently supported include PDF,
PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a
lesser extent, RTF and TXT. The primary output target is PDF.
Latest Release
--------------
Apache XML Graphics Apache FOP 2.11 was released on May 6, 2025
* Ads support for using PDF images in fo:external-graphic elements when you
generate PDF files
* Upgrade to PDFBox 3
* Add support for PDF object streams
* Add option to lazy load fonts for PNG/TIFF/PCL output
* Add option to combine AFP page groups
* Add option to convert image to CMYK
* Add option for static content structure element per page
* Bug fixes
APACHE FOP: PDF Images Plug-In
===
Apache FOP: PDF Images Plug-In extends Apache FOP in order to add support for
using PDF images in fo:external-graphic elements when generating PDF files.
Latest Release
--------------
Apache XML Graphics Apache FOP PDF Images 2.11 was released on May 6, 2025
* Ads support for using PDF images in fo:external-graphic elements when you
generate PDF files
* Bug fixes
XML GRAPHICS COMMONS
====================
Apache XML Graphics Commons is a library that consists of several reusable
components used by Apache Batik and Apache FOP. Many of these components can
easily be used separately outside the domains of SVG and XSL-FO. You will find
components such as a PDF library, an RTF library, Graphics2D implementations
that let you generate PDF & PostScript files, and much more.
Latest Release
------------
Apache XML Graphics Commons 2.11 was released on May 6, 2025
* Bug fixes
-----------------------------------------
Attachment CI: Report from the Apache YuniKorn Project [Wilfred Spiegelenburg]
## Description:
The mission of Apache YuniKorn is the creation and maintenance of software
related to a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds
## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: none
## Membership Data:
Apache YuniKorn was founded 2022-03-16 (3 years ago)
There are currently 38 committers and 29 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 Chia-Ping Tsai on 2024-03-07.
- Junyan Ling was added as committer on 2025-06-25
## Project Activity:
Recent releases:
1.7.0 was released on 2024-07-28.
1.6.3 was released on 2025-05-06.
1.6.2 was released on 2025-03-18.
YuniKorn 1.6.3 was released to fix a crash in the scheduler discovered in 1.6.2.
YuniKorn 1.7.0 was released after slipping from the early June 2025 planned
release. A beta for 1.7.0 was released to allow for scale and compatibility
testing by the community. Scale testing is still an issue. Code for a testing
framework is progressing. Delivery has slipped out of 1.7.0.
## Community Health:
4 new Jira accounts were requested. 37 new Jiras created and 29 resolved,
with corresponding GitHub PRs: 42 created and 35 resolved.
-----------------------------------------
Attachment CJ: Report from the Apache IoTDB Project [Xiangdong Huang]
## Update on trademark concerns
The IoTDB has worked with a vendor to address concerns raised regarding
several aspects of the vendor's website. The vendor responded promptly
and the concerns have been resolved.
------------------------------------------------------
End of minutes for the August 20, 2025 board meeting.
Index