Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
June 18, 2025
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:01 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones:
http://www.timeanddate.com//worldclock/fixedtime.html?iso=2025-06-18T21: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é
Greg Stein
Sander Striker
Kanchana Pradeepika Welagedara
Directors Absent:
none
Executive Officers Present:
Jeff Jirsa
Craig R. McClanahan
Matt Sicker
Executive Officers Absent:
Craig L Russell
Ruth Suehle
Guests:
Alin Jerpelea
Christopher Schultz
Daniel Gruno
Danny Angus
Dave Fisher
Jarek Potiuk
Melissa Logan - joined :04
Niall Pemberton
Paul King
Sally Khudairi
Whitney P True - joined :03
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of May 21, 2025
See: board_minutes_2025_05_21.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
This week I am partially attending UN Open Source week, from Wednesday
on. I'll report back what I learn at the event.
Last month I ran the meeting using the Board Agenda Tool that is under
development by Tooling. I fully intend to do that again this month,
and am looking forward to see the tool evolve further.
The agenda is relatively light, but due to travel I have asked the
Vice Chair to run the meeting in the event my setup ends up suboptimal
to run the meeting.
B. President [Ruth Suehle]
After graciously serving for two years in the role, Myrle Krantz has
stepped down as VP, Infra. Danny Angus has been shadowing her, and I
am appointing him to replace her. Please join me in thanking Myrle for
all her work in one of our most challenging roles and welcome Danny.
This week I am representing the ASF at UN Open Source Week, including
as a co-organizer/sponsor (in effort, not funding) of the Tech Over
Hackathon. The UN has had a growing enthusiasm for open source the
last few years and has been a great Bridge among foundations and
collaborators.
Next in collaboration with our peers, the Open Source Congress event
will be held for the third year in September in Brussels, and I'm
working with several other foundations to shape that program.
This month I'm particularly pleased with the significant uptick in
sponsorships for Community Over Code NA and greatly appreciate Brian
Proffitt's work in that area. We had been lagging, and not
uniquely--our peers across the industry are seeing similar problems in
budgets this year.
On a lighter note, that influx of sponsorships means I finally felt
secure in signing a contract on our evening event for the conference,
and I'm excited to share the historic Mill City Museum with all of you
in Minneapolis!
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig R. McClanahan]
Normal operations continue.
We've accumulated a bunch of information from Ramp (via their API)
that will assist folks in monitoring the cards they are responsible
for, and the charges that have been made on them. If you are
responsible for expenses in a particular area (department or role),
look for an email in the coming week or so that contains two
attachments (the data is conveniently in CSV format, so you can load
them into your favorite spreadsheet easily):
* List of Ramp cards ever issued to someone in your department,
including whether they are currently active or not, and what limits
have been placed on that card.
* List of Ramp transactions for last fiscal year in your category of
expenses (it's really easy to request a particular date range if you
need something else), including whose card was used, what the
merchant name was, and various other details.
The email will also include a link to the recently updated information
on what a Card Manager can do on Ramp via their API.
Next step will be to do similar work on bill.com data via their API.
D. Secretary [Matt Sicker]
In May 2025, the secretary received 38 ICLAs, 2 CCLAs, 1 software
grant, and 4 CoI affirmations.
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 / Sander]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Zili]
No report was submitted.
C. Apache Security Team Project [Mark J. Cox / Justin]
See Attachment 14
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# DeltaSpike [striker]
# IoTDB [jmclean]
# Logo Development [striker]
# OpenDAL [jmclean]
# Paimon [jmclean]
# Portals [jmclean]
# SIS [rbowen]
# Whimsy [striker]
A. Apache Airflow Project [Bolke de Bruin / Kanchana]
See Attachment A
B. Apache Allura Project [David Philip Brondsema / JB]
See Attachment B
C. Apache Ant Project [Jan Materne / Greg]
No report was submitted.
D. Apache Atlas Project [Madhan Neethiraj / Shane]
No report was submitted.
E. Apache Axis Project [Robert Lazarski / Rich]
See Attachment E
F. Apache Beam Project [Kenneth Knowles / Jim]
See Attachment F
G. Apache Bigtop Project [Masatake Iwasaki / JB]
See Attachment G
H. Apache BVal Project [Matthew Jason Benson / Shane]
No report was submitted.
I. Apache Camel Project [Andrea Cosentino / Greg]
See Attachment I
J. Apache Cayenne Project [Michael Ray Gentry / Justin]
See Attachment J
K. Apache CloudStack Project [Nicolás Vázquez / Rich]
See Attachment K
L. Apache Commons Project [Gary D. Gregory / Sander]
See Attachment L
M. Apache Cordova Project [Bryan Ellis / Jim]
See Attachment M
N. Apache cTAKES Project [Pei Chen / Kanchana]
See Attachment N
O. Apache Curator Project [Enrico Olivelli / Zili]
See Attachment O
P. Apache Daffodil Project [Mike Beckerle / Greg]
See Attachment P
Q. Apache DataFusion Project [Andrew Lamb / Sander]
See Attachment Q
R. Apache DeltaSpike Project [Mark Struberg / Kanchana]
See Attachment R
DeltaSpike to report again next month.
S. Apache Drill Project [Charles Givre / Justin]
See Attachment S
T. Apache ECharts Project [Wenli Zhang / Zili]
See Attachment T
U. Apache Felix Project [Karl Pauls / JB]
See Attachment U
V. Apache Flex Project [Harbs / Kanchana]
No report was submitted.
W. Apache Flink Project [Robert Metzger / Jim]
See Attachment W
X. Apache Gobblin Project [Abhishek Tiwari / Rich]
See Attachment X
Y. Apache Gravitino Project [Jerry Shao / Shane]
See Attachment Y
Z. Apache Griffin Project [William Guo / Sander]
No report was submitted.
AA. Apache Guacamole Project [Mike Jumper / Greg]
See Attachment AA
AB. Apache Gump Project [Stefan Bodewig / Rich]
See Attachment AB
AC. Apache Helix Project [Junkai Xue / Zili]
See Attachment AC
AD. Apache Hive Project [Naveen Gangam / Justin]
No report was submitted.
AE. Apache Hop Project [Hans Van Akelyen / Kanchana]
See Attachment AE
AF. Apache Hudi Project [Vinoth Chandar / Jim]
See Attachment AF
AG. Apache Iceberg Project [Ryan Blue / Shane]
See Attachment AG
AH. Apache Incubator Project [Justin Mclean]
See Attachment AH
AI. Apache IoTDB Project [Xiangdong Huang / JB]
See Attachment AI
@Zili: follow up with IoTDB PMC about project updates
AJ. Apache Jackrabbit Project [Marcel Reutegger / Sander]
See Attachment AJ
AK. Apache Karaf Project [Jean-Baptiste Onofré]
See Attachment AK
AL. Apache Kibble Project [Sharan Foga / Jim]
No report was submitted.
AM. Apache Kvrocks Project [Mingyang Liu / JB]
See Attachment AM
AN. Apache Kyuubi Project [Kent Yao / Justin]
See Attachment AN
AO. Apache Linkis Project [Shuai Di / Zili]
See Attachment AO
AP. Apache Logo Development Project [Daniel Gruno / Sander]
No report was submitted.
AQ. Apache Lucene Project [Dawid Weiss / Kanchana]
See Attachment AQ
AR. Apache Lucene.Net Project [Shad Storhaug / Shane]
No report was submitted.
AS. Apache Mynewt Project [Szymon Janc / Greg]
No report was submitted.
AT. Apache NetBeans Project [Geertjan Wielenga / Rich]
See Attachment AT
AU. Apache OFBiz Project [Jacopo Cappellato / JB]
See Attachment AU
AV. Apache Olingo Project [Michael Bolz / Jim]
No report was submitted.
@Jim: discuss Attic with PMC
AW. Apache OpenDAL Project [Hao Ding / Sander]
See Attachment AW
AX. Apache OpenNLP Project [Jeff Zemerick / Jim]
See Attachment AX
AY. Apache OpenWebBeans Project [Mark Struberg / Shane]
See Attachment AY
AZ. Apache Paimon Project [Jingsong Lee / Zili]
See Attachment AZ
BA. Apache Pekko Project [PJ Fanning / Kanchana]
See Attachment BA
BB. Apache Pig Project [Koji Noguchi / Justin]
See Attachment BB
BC. Apache PLC4X Project [César García / Rich]
No report was submitted.
BD. Apache Portable Runtime (APR) Project [Yann Ylavic / Greg]
See Attachment BD
BE. Apache Portals Project [Neil Griffin / Jim]
See Attachment BE
@Jim: coordinate with Portals PMC to find out more about
potential Eclipse move
BF. Apache Pulsar Project [Matteo Merli / Greg]
See Attachment BF
BG. Apache RocketMQ Project [Xiaorui Wang / Zili]
See Attachment BG
BH. Apache Royale Project [Yishay Weiss / Kanchana]
See Attachment BH
BI. Apache Samza Project [Jagadish Venkatraman / Kanchana]
No report was submitted.
BJ. Apache SeaTunnel Project [Jun Gao / Shane]
No report was submitted.
BK. Apache ServiceMix Project [Krzysztof Sobkowiak / JB]
See Attachment BK
BL. Apache Shiro Project [Brian Demers / Justin]
See Attachment BL
BM. Apache SINGA Project [Wang Wei / Sander]
See Attachment BM
BN. Apache SIS Project [Martin Desruisseaux / Rich]
See Attachment BN
@Rich: pursue a roll call for SIS PMC
BO. Apache Sling Project [Robert Munteanu / Justin]
See Attachment BO
BP. Apache SpamAssassin Project [Giovanni Bechis / Shane]
See Attachment BP
BQ. Apache Steve Project [Daniel Gruno / Jim]
No report was submitted.
BR. Apache Storm Project [Richard Zowalla / Rich]
See Attachment BR
BS. Apache StormCrawler Project [Richard Zowalla / Kanchana]
See Attachment BS
BT. Apache StreamPark Project [Huajie Wang / JB]
No report was submitted.
BU. Apache Synapse Project [Isuru Udana / Sander]
No report was submitted.
BV. Apache Tomcat Project [ / Greg]
See Attachment BV
BW. Apache TomEE Project [David Blevins / Zili]
See Attachment BW
BX. Apache Traffic Server Project [Bryan Call / Jim]
See Attachment BX
BY. Apache TVM Project [Tianqi Chen / Greg]
See Attachment BY
BZ. Apache UIMA Project [Richard Eckart de Castilho / Rich]
See Attachment BZ
CA. Apache Unomi Project [Serge Huber / Shane]
See Attachment CA
CB. Apache VCL Project [Josh Thompson / JB]
See Attachment CB
CC. Apache Web Services Project [Daniel Kulp / Sander]
See Attachment CC
CD. Apache Whimsy Project [Shane Curcuru]
See Attachment CD
Whimsy PMC to report next month.
CE. Apache Wicket Project [Andrea Del Bene / Justin]
No report was submitted.
CF. Apache Xerces Project [Michael Glavassevich / Kanchana]
See Attachment CF
CG. Apache Yetus Project [Allen Wittenauer / Sander]
See Attachment CG
CH. Apache ZooKeeper Project [Flavio Paiva Junqueira / Zili]
See Attachment CH
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Tomcat Project Chair
WHEREAS, the Board of Directors heretofore appointed Mladen Turk
(mturk) to the office of Vice President, Apache Tomcat, and
WHEREAS, the Board of Directors is in receipt of the notification of
the death of Mladen Turk, and
WHEREAS, the Project Management Committee of the Apache Tomcat project
has chosen by consensus to recommend Christopher Schultz (schultz) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Christopher Schultz be and hereby
is appointed to the office of Vice President, Apache Tomcat, 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 Tomcat Project Chair, was
approved by Unanimous Vote of the directors present.
B. Terminate the Apache jclouds Project
WHEREAS, the Board of Directors deems it no longer in the best interest
of the Foundation to continue the Apache jclouds project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache jclouds 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 jclouds Project; and be it
further
RESOLVED, that the office of "Vice President, Apache jclouds" is hereby
terminated; and be it further
RESOLVED, that the Apache jclouds PMC is hereby terminated.
Special Order 7B, Terminate the Apache jclouds Project, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Mahout Project Chair
WHEREAS, the Board of Directors heretofore appointed Andrew Musselman
(akm) to the office of Vice President, Apache Mahout, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Andrew Musselman from the office of Vice President, Apache Mahout, and
WHEREAS, the Project Management Committee of the Apache Mahout project
has chosen by vote to recommend Shannon Quinn (squinn) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Andrew Musselman is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Mahout, and
BE IT FURTHER RESOLVED, that Shannon Quinn be and hereby is appointed
to the office of Vice President, Apache Mahout, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache Mahout Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Board Charter
Discuss acceptance of a Board charter.
Discussion to continue on mailing lists.
9. Review Outstanding Action Items
* Jim: pursue a roll call for Olingo PMC
[ Olingo 2025-03-19 ]
Status: COMPLETED Back in March
* Kanchana: connect PMC with DeltaSpike and Geronimo about synergy
[ MyFaces 2025-04-16 ]
Status: Completed. Both PMC chairs and PMC members from MyFaces met.
They are not merging. Geronimo folks didn't join.
* Rich: pursue an Attic resolution for jclouds
[ jclouds 2025-04-16 ]
Status: Done
https://lists.apache.org/thread/ksq98zb3jrjbb5lz079go9mwltbt5n2z
Retirement resolution is on the agenda.
* Sander: follow up about projected timeline for logo
[ Logo Development 2025-04-16 ]
Status: Reminder sent
https://lists.apache.org/thread/58s2cyynj0sbsz1xl9jomdtsscfknj4m.
* Rich: resolve the ComDev mission discrepancy
[ Community Development 2025-05-21 ]
Status:
* Justin: follow up about security issue status
[ EventMesh 2025-05-21 ]
Status: Done. As there was no response from PMC, I initiated a PMC
roll call and brought it to the attention of ASF security, who
will follow up on this.
* Greg: speak with Geode PMC about onboarding and security concerns
[ Geode 2025-05-21 ]
Status: no status change
* Justin: follow up with Libcloud PMC
[ Libcloud 2025-05-21 ]
Status: Sent possible options on next steps, including adding PMC
members. No real response. Sent follow-up. Currently, a
release is blocked because it lacks sufficient PMC votes.
* Jim: follow up with Pinot PMC about PMC Chair change
[ Pinot 2025-05-21 ]
Status: Ongoing. Keep open.
* Greg: broad reminder for PMC terminology
[ Pinot 2025-05-21 ]
Status: no status change
* Kanchana: follow up with Samza PMC about change in PMC Chair
[ Samza 2025-05-21 ]
Status: Just contacted the PMC (My bad , I addressed this AI late)
* Sander: follow up with Web Services PMC about activity
[ Web Services 2025-05-21 ]
Status: https://whimsy.apache.org/board/agenda/2025-06-18/Web-Services
self reports.
* Jim: speak with VP Legal about reducing exposure to risk
[ Policies for Foundation internal venues 2025-05-21 ]
Status: Ongoing but not yet spoken to VP Legal
10. Unfinished Business
11. New Business
12. Announcements
The board acknowledges the passing of Mladen Turk and appreciates
his work.
13. Adjournment
Adjourned at 21:32 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period May 2025
* ISSUES FOR THE BOARD
None.
* OPERATIONS
- Approved use of Apache marks in event marketing material with a minor change
- Progress has been made on the new policy for service naming
- Provided advice the Arrow PMC on registration of sub-components
- Provided advice to a company that was considering using an ASF mark in a
project name
- Approved BURR as a project name
- Provided advice to a developer looking to publish YouTube videos about
AIRFLOW
- Provided advice to a company that wanted to use a modified TOMCAT logo
* REGISTRATIONS
Started the registartion process for GROOVY in the US.
Started the process to transfer BifroMQ marks to the ASF.
* INFRINGEMENTS
An infringement of APISIX has been resolved but it is unclear whether that is
as a result of communications from the ASF or time passing.
Some progress regarding the downstream vendor with multiple infringements of
ASF marks.
Working with the GROOVY PMC to address a potential infringement in a GitHub
project.
The CASSANDRA PMC is addressing some issues in a recent blog.
No progress regarding a site with a possible infringement of APISIX.
No response so far regarding a potential infringement of PDFBOX.
No progress regarding a potential infringement of GUACAMOLE.
The Logging PMC is working to resolve an issue with LOG4J usage.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we are engaging with a few candidate Sponsors, but none have committed
yet during this timeframe.
b —Renewals: we have secured renewal commitments from one Platinum and one
Gold Sponsor.
c —Payments: 1 —New: we did not receive any new Sponsorship payments.
2a —Renewing: we received renewal payments from two Platinum Sponsors.
2b —Incoming: we await payment from two renewing Platinum Sponsors, one
Gold Sponsor, plus payment for a partial Sponsorship-year (prior to the
organization upgrading their Sponsorship level).
2) Targeted Sponsors: we continue to explore benefits options for those
directly supporting an ASF Project (whether directly or via third party
service) vs. financial contributions towards services administered by ASF
Infrastructure that benefit the ASF as a whole, or a named Project.
3) Sponsor Relations: our outreach and engagement continues, including our
next quarterly call with Gold and Platinum Sponsors, which is scheduled to
take place at the end of June.
4) Event Sponsorship: we are promoting both 2025 Community Over Code events
(Asia and North America), and are handling sponsorship agreements / invoicing
coordination for North America. We have also extended bundled sponsorship
benefits for ASF Gold and Platinum Sponsors
https://communityovercode.org/asf-sponsorship-discounts/ .
5) Individual Donations and Corporate Giving: we received $1,070 in online
donations via https://donate.apache.org/ . This reflects a downward trend for
us, with reduced donations over previous years —May 2024: $1,282, May 2023:
$2,745, May 2022: $2,404. These figures are consistent with a report by The
Chronicle of Philanthropy, which states that donations to US charitable
organizations continue to shrink for the fourth year in a row.
6) Administrivia: we continue to work closely with the Accounting and Treasury
teams, as well as Events and Marketing & Publicity on various activities.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Developed strategic plan outlining M&P activities and priorities for FY2026
and added to the private wiki
* Created Community Over Code event marketing plan, including advertising
options, to bolster brand awareness and event attendance
* Developed statement in response to Synadia / CNCF dispute
* Drafted announcement to release schedule for Community Over Code NA
* Created Community Over Code scripts for the ASF member community to help
solicit event sponsors
* Began work with Fundraising committee for efforts that support sponsor
retention as well as new sponsor recruitment
Website
* Met with infra team to explore options for self-hosting the Plus One
Newsletter vs. using the existing WordPress infrastructure
Project Comms
* Drafted press release announcing two new TLPs: Gravitano and StormCrawler;
began coordination with project PMCs
Foundation Content
* Finalized work on social media guidance policy for attic’d projects; updated
pull request for public posting
* Continued work on FY25 annual report including data gathering from ASF
officers
* Developed member-focused survey to gather valuable YoY data as well as
actionable insights to inform FY26 M&P work
Social Media Overview
The highest performing pieces of content included #FirstASFContribution blogs,
project release news, and Community Over Code promotions.
Social Highlights (X + LinkedIn + Bluesky)
* Total Audience: 143,152#
* New Followers in May: 82
* X: -392
* Bluesky: 44
* LinkedIn: 430
* Total Posts: 74
* X: 32
* Bluesky: 32
* LinkedIn: 10
* Total Engagements: 1,994
(# Total network size declined by 105 followers due to a substantial loss of
followers on X)
Website Analytics
* 824,919 visits, 824,861 unique visitors -8.4%
* 3 min 14s average visit duration +16.2%
* 51% visits have bounced (left the website after one page) +6.3%
* 5.1 actions (page views, downloads, outlinks, internal site searches) per
visit (level)
* 10,001 max actions in one visit (level)
* 3,595,094 pageviews, 1,019,642 unique pageviews -6.8%
* 4 total searches on your website, 4 unique keywords +300%
* 292,786 downloads, 214,895 unique downloads -22.3%
* 290,085 outlinks, 193,774 unique outlinks -11.5%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Myrle Krantz]
General
=======
The Infrastructure team continues to operate at reduced staffing.
Hiring problems have caused delays with operational and policy tasks
(such as MFA) due to the need for prioritization of day-to-day
operations with reduced staffing.
From May's board report, Infra has provided HBase a stopgap regarding
their CI hosting. Policy review and publication is still pending with
a targeted completion date of July 2025.
Concerns regarding performance of ASF websites for site visitors in
Mainland China have arisen again. VP Infra provided the following
statement:
https://lists.apache.org/thread/sd0sbwb0630b1j9o7y0vg3k4672zjzvs
Finances
========
Some budget items may need to be revised if HBase requests a budget
from the Board for operation of CI nodes due to their current
predicament as noted above. Infra has provided temporary cloud nodes
as a stopgap.
MFA Efforts
===========
Infra, Security, and Tooling continue to coordinate on next steps.
Tooling has provided time and expertise to assist in standing up a
more current version of Keycloak, along with some recommendations
around managing personal access tokens (PATs). Next steps involve
fleshing out and documenting the Keycloak workflow and deploying a POC
for PATs with an expected POC/Demo ready by the end of July.
Major Projects
==============
Dockerhub Self Service -- Infra is preparing to roll out self-serve
features for Dockerhub, including repo creation and team management,
with an estimated deployment date of late June.
Subversion upgrade planning -- Infra is finalizing plans to upgrade
svn.apache.org to the latest operating system, which includes
modifications to various Subversion components for Python 3
compatibility. Target migration date is mid-July.
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 has been working hard building systems and playing well with others.
## Apache Trusted Releases.
We started an internal Alpha Test at release-test.apache.org with seven PMCs
so far:
- Airflow
- Commons
- Logging Services
- Maven
- Pekko
- Sling
- Tomcat
Great feedback through several issues which we are handling. The Alpha will be
announced to ASF Members once a couple of workflow issues are handled.
We worked with ComDev to enhance their project json feed to include TLPs
without DOAP files. We believe that the 385 projects number is an
understatement. We are planning to make it easy for PMCs to declare projects
in .asf.yaml files.
We are discussing what additional metadata file formats should be maintained
and offered to the public.
We had a discussion with our targeted sponsor about leveraging an update of
repository.apache.org to Nexus3 and how that can enhance release metadata,
sbom generation, and potentially handle multiple distribution channels.
## Board Agenda Tool
The Chair used the tool to run last month's Board Meeting. This allowed
attendees to follow the Chair as they navigated through the Agenda.
We added views of foundation leadership, committees, and committers which are
both generally useful and will support the Secretary's actions when a Special
Order passes.
We are working with Infra so that commits to the agenda will have the correct
author.
## Workbench
We met with the Treasurers and are making plans to support the tooling they
are building to support their operations.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
Community Over Code NA
We have obtained additional sponsorship revenue, with two confirmed
Platinum-level, five Gold-level, and one Silver-level sponsorships in process.
With the Platinum sponsorships, and the great efforts of the planning team, we
have also obtained keynote speakers for all four event days.
The AV contract is being finalized now. Thanks go to the Treasurer for helping
to get the MN tax exemption form filled out, which will save us quite a bit of
money in sales tax we will not have to pay.
-----------------------------------------
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.
Current Events
==============
Community Over Code Asia
------------------------
Visa applications under way for 3 applicants. Starting to book flights
for the rest (With our appointed travel agent). Hotel to be organized.
Community Over Code NA
------------------------
Applications for North America (Minneapolis) opened up on the 7th
April and will close on the 14th June. We have 25 applications in so
far.
Monthly Meetings
================
The next meeting will be held first week of July.
TAC App
=======
TAC app is open for applications for NA.
Future Events
=============
None currently.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support. Post surveys
for Bratislava, Hangzhou and Denver still to be done.
Mailing List Activity
=====================
Call for Judges/Shepherds traffic, not much else.
Membership
==========
No changes to the Committee this month.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
Nothing to report this month.
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
Nothing to report this month.
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
Apologies; I did not manage to get the report ready in time. Will be posted to
board@ as soon as possible.
That said - for Europe - the short of it is that in most policy areas there is
healthy progress; with generally sufficient open source (foundations,
community, our industry) input & sensible adjustment that benefit
society/industry & are in line with our mission. The main exception are still
the bodies/normative standards - in particular those at CENELEC.
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
- The expected deadline for the submission of the Transparency Exchange API
standard was moved from December 2025 to June 2026.
- No other significant news.
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
May
* To encourage the use of MFA at the ASF, we split the scope of that
project into phases and defined the first phase,
https://cwiki.apache.org/confluence/display/INFRA/MFA+project+phase+1%3A+Security
Stats for May 2025:
38 [license confusion]
24 [support request/question not security notification]
16 [report/question relating to dependencies]
Security reports: 80 (last months: 63, 75, 78, 59)
9 ['tomcat']
7 ['airflow', 'httpd']
8 ['website or other infrastructure']
3 ['nuttx', 'trafficserver']
2 ['activemq', 'cloudstack', 'commons', 'hc', 'mynewt', 'openoffice', 'zookeeper']
1 ['allura', 'axis', 'baremaps', 'brpc', 'camel', 'cassandra', 'cxf', 'db', 'dolphinscheduler', 'doris', 'flink', 'hop', 'iotdb', 'kafka', 'kie', 'logging', 'lucene', 'netbeans', 'ozone', 'parquet', 'pekko', 'roller', 'solr', 'storm', 'superset', 'thrift', 'tika', 'xmlgraphics', 'zeppelin']
In total, as of 2nd June 2025, we're tracking 214 (last months: 216,
209) open issues across 69 projects, median age 97 days (last months:
98, 99). 75 of those issues have CVE names assigned. 17 (last month:
20) of these issues, across 8 projects, are older than 365 days.
* carbondata (Health amber): PMC is not responsive (low-severity issue) (Last update: 2025-05-09)
* 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-04-04)
* geode (Health amber): 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-06-03)
* openoffice (Health amber): 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-06-03)
* spark (Health amber): the project is not responsive to security
issues (Last update: 2025-06-02)
* zeppelin (Health amber): The project is still struggling with
triage, fixes, releases, and providing timely updates. (Last update:
2025-04-04)
-----------------------------------------
Attachment A: Report from the Apache Airflow Project [Bolke de Bruin]
## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines
## Project Status:
Current project status: Ongoing, high activity
Issues for the board: no issues
## Membership Data:
Apache Airflow was founded 2018-12-19 (6 years ago)
There are currently 73 committers and 35 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 Vikram Koka on 2024-10-19.
- Bugra Ozturk was added as committer on 2025-03-15
- Zhe You Liu was added as committer on 2025-03-15
- Kalyan Reddy was added as committer on 2025-03-15
- Rahul Vats was added as committer on 2025-03-31
- Shubham Raj was added as committer on 2025-03-17
## Project Activity:
We have released Airflow 3.0 and subsequently Airflow 3.0.1 and Airflow 3.0.2.
This was a highly anticipated release and our biggest one yet since Airflow 2.
It has been extremely well received with users, community and commercial
stakeholders.
## Community Health:
The flurry of contributions towards Airflow 3.0 has put us for a while in the
top 10 ofmost active projects on ossrank.com. Above for example Python. We
have risen to 3318 or 3601 contributors depending who you ask.
Airflow 3 was a mutual endeavor across the community and commercial vendors.
This is pretty exemplary of a very healthy community and collaboration
and we are a little bit proud at ourselves (just a little).
-----------------------------------------
Attachment B: Report from the Apache Allura Project [David Philip Brondsema]
## Description:
The mission of Apache Allura is the creation and maintenance of software
related to a software development infrastructure platform commonly known as a
"forge"
## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: none
## Membership Data:
Apache Allura was founded 2014-03-18 (11 years ago)
There are currently 18 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Carlos Cruz on 2024-06-26.
- No new committers. Last addition was Carlos Cruz on 2024-06-27.
## Project Activity:
- minor new features: admin notes for new projects, logout Clear-Site-Data
header
- python dependency upgrades
## Community Health:
- not a lot of updates this quarter, but still some
- no new community members for a while
-----------------------------------------
Attachment C: Report from the Apache Ant Project [Jan Materne]
-----------------------------------------
Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj]
-----------------------------------------
Attachment E: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary
components (both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Membership Data:
Axis was created on 2001-01-19 (24 years ago). It is listed as
established in 2009-12 but really the first Apache commit was in 2001.
There are currently 65 committers and 64 PMC members in this project,
a vote in 2010 made all committers automatically PMC members. One PMC
member resigned.
Community changes, past quarter:
- Currently 64 PMC/ 65 Committers members.
- No new committers were added in the last 90 days, Andreas Lehmkühler was added on January 28th, 2025 and Christian Ortlepp on January 2nd, 2025. Both were added to the PMC on January 28th, 2025.
## Project Activity:
Recent releases:
- Axis 2/Java 2.0.0 was released on March 10, 2025.
- Axis 2/Rampart 1.8.0 was released on Dec 10, 2024.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## Project state: Ongoing, with moderate activity
## Health report:
After completing a several year development cycle of Axis2 2.0.0 to support jakarta and not bleed users with day job
pressure to migrate, it was a relatively quiet quarter - presumably to pay off technical debt at our own
day jobs on jakarta.
The Axis2 community still has work to do on releasing Apache Rampart 2,0.0 this upcoming quarter with
jakarta support, made more difficult by lacking committers who use Rampart in their own projects - while having some
of our Axis2 community maintaining their own branches to get thru jakarta the best they can.
Axis2/C has an email thread in progress on c-user@axis.apache.org discussing a 2.0.0 release that includes
three PMC members - indicating a viable future for the project.
The goals for the Axis2/C 2.0.0 release are continuing to be discussed, though it is clear that some of the committers are motivated by seeing the community contributed JSON support being released officially.
We expect the Axis2/C release to pick up momentum this upcoming quarter as our distractions elsewhere clear up in
Axis2/Java as described above.
## Axis2 java Jira issues opened in the last 90 days: 13
## Axis2 java Jira issues closed in the last 90 days: 4
-----------------------------------------
Attachment F: Report from the Apache Beam Project [Kenneth Knowles]
## Description:
The mission of Apache Beam is the creation and maintenance of software related
to a unified programming model for both batch and streaming data processing,
enabling efficient execution across diverse distributed execution engines and
providing extensibility points for connecting to different technologies and
user communities.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Beam was founded 2016-12-20 (8 years ago)
There are currently 98 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Danny McCormick on 2024-12-12.
- Shunping Huang was added as committer on 2025-05-29
- Vitalii Terentev was added as committer on 2025-03-24
## Project Activity:
Recent releases:
- 2.65.0 was released on 2025-05-12.
- 2.64.0 was released on 2025-03-31.
Technical highlights:
- Developments in the the new Managed API (which is configuration-driven and
easy for runners to host and manage, versus Beam's traditional code-driven
API): Both Java and Python support key I/O connectors Iceberg, Kafka, and
BigQuery.
- In the YAML SDK, managed is becoming the default as connectors become
available, and that now includes the Kafka connector.
- Beam reports lineage metadata starting in 2.63.0, with support added to the
Dataflow Runner.
- Increased integration with Apache Iceberg:
- Added a streaming source
- Available in Python and YAML SDKs
Community highlights:
- The Beam College 2025 event (https://beamcollege.dev/) was held May 15-18,
2025, including new training videos and a hackathon. Hackathon challenges
include AI-Powered Data Processing, building data pipelines without coding
using Beam YAML, Real-time Anomaly Detection, leveraging Managed I/O with
Iceberg/Kafka/BigQuery, and an Open Challenge.
- Beam Summit 2025 (https://beamsummit.org/) will be held in New York City on
July 8th & 9th. The Call for Papers (CFP) was open until April 2025. And
the proposed schedule is available (https://beamsummit.org/program/). Four
- Google Summer of Code (GSoC) 2025 projects for Apache Beam have been
proposed:
- Enhancing Apache Beam JupyterLab Sidepanel for JupyterLab 4.x and
Improved UI/UX
([GSOC-277](https://issues.apache.org/jira/browse/GSOC-277)).
- Beam ML Vector DB/Feature Store integrations
([GSOC-279](https://issues.apache.org/jira/browse/GSOC-279)).
- Simplify management of Beam infrastructure, access control and
permissions via Platform features
([GSOC-273](https://issues.apache.org/jira/browse/GSOC-273)).
- Beam YAML ML, Iceberg, and Kafka User Accessibility
([GSOC-278](https://issues.apache.org/jira/browse/GSOC-278)).
- Some community members have begun gathering changes that they propose to be
part of a "Beam 3" major version bump: i
https://github.com/apache/beam/milestone/31
## Community Health:
Community health is steady. No great increase or decrease in dev@ or user@
traffic. What discussion there is tends to be more focused on specific design
and implementation proposals. A minor note that will have an interesting effect
on metrics and visibility is new automation to mark old issues stale after
180 days and close after a further 30.
-----------------------------------------
Attachment G: Report from the Apache Bigtop Project [Masatake Iwasaki]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Bigtop was founded 2012-09-19 (13 years ago)
There are currently 47 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhiguo Wu on 2024-08-19.
- Liqiang Fu was added as committer on 2025-05-13
- Gu Jiawei was added as committer on 2025-04-29
## Project Activity:
Recent releases:
- 3.4.0 was released on 2025-05-30.
- bigtop-manager-1.0.0 was released on 2025-04-24.
- 3.3.0 was released on 2024-07-08.
The first major release of bigtop-manager (1.0.0) was rolled out on 2025-04-24.
We released Apache Bigtop 3.4.0[1] too on 2025-05-30.
We are starting to prepare for the next 3.5.0 release.
Bigtop 3.5.0 will contain changes such as
- adding Apache Airflow to the stack
- upgradeing Hadoop from 3.3 to 3.4
- upgrading Fedora from 40 to 42 or 43
[1] https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+3.4.0+Release
## Community Health:
Community health is good.
We added 1 new committer since the last report.
Gu Jiawei (gujiaweijoe) was accidentally added as committer of Bigtop.
Since the intention was to add the committer to BifroMQ(incubating),
I removed gujiaweijoe from Bigtop committer list.
-----------------------------------------
Attachment H: Report from the Apache BVal Project [Matthew Jason Benson]
-----------------------------------------
Attachment I: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: There
are no issues requiring board attention at this time.
## Membership Data:
Apache Camel was founded 2008-12-17 (16 years ago)
There are currently 94 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Colm O hEigeartaigh on 2024-03-11.
- No new committers. Last addition was Thomas Diesler on 2024-11-22.
## Project Activity:
Apache Camel:
- We released Camel 4.8.6
- We released Camel 4.10.3
- We released Camel 4.10.4
- We released Camel 4.10.5
- We released Camel 4.11.0
- We released Camel 4.12.0
- Note: Camel releases have synchronized releases of Camel-Karaf and
Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
synchronized.
- 4.10.x is our last LTS release train. The next LTS will be 4.13.0
- The situation is really healthy and the community is super. We are
introducing many new features and working on engaging the community more.
Camel is growing even in terms of interest and there is an ongoing effort
for AI stuff.
Apache Camel K:
- There were no releases for camel-k
- Camel K is in good shape and the community is expading with new contributors
and many new good idea and many good interactions. The situation is healthy.
Apache Camel Kamelets:
- We released Camel Kamelets 4.10.3
- We released Camel Kamelets 4.10.4
- We released Camel Kamelets 4.10.5
- We released Camel Kamelets 4.11.0
- We released Camel Kamelets 4.12.0
- The 4.10.x release train is matching the LTS release from Camel core and
it's an important building block for starting with routes
- We introduced a lot of new Kamelets and we are improving the documentation
by focusing on much more examples. Also we improved the Kamelets
description.
Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
multiple releases
- We released Camel-quarkus 3.20.0
- We released Camel-quarkus 3.20.1
- We released Camel-quarkus 3.22.0
- We released Camel-quarkus 3.23.0
- A lot of work has been done on testing side more new features and extensions
have been developed and improved.
- The engagement of the community is improving
Apache Camel-Karavan:
- Camel-Karavan is improving and the community around the project is
increasing in number of features and new issues reporting. It's growing.
- We released the 4.10.2
- The 4.10.x is aligned to Camel 4.10.x LTS
Camel-Kafka-Connector:
- 4.10.2 and 4.10.3 have been released and based on the last LTS release train
4.10.x
- The community is active and we receive a lot of feedback and requests. We
are improving the documentation.
Apache Camel-Karaf:
- Camel-karaf 4.10.3 has been released.
- It's the first version supporting LTS 4.10.x
- Other 4.8.x patch releases have been released too
## Community Health:
- dev@camel.apache.org had a 4% increase in traffic in the past quarter (371
emails compared to 356): Related to release planning and more heads up
- At the time of writing this was the only statistic available in the report
helper.
- What we could say is that the community is growing on all of the projects and
subprojects. There is interest, new issues, new discussions and we are happy
to see new engaging feedback from users.
-----------------------------------------
Attachment J: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, June 2025
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object graph persistence and provides an ORM
runtime, remote persistence services*, and a cross-platform GUI
database mapping/modeling/development tool.
*Remote persistence services is being phased out for 5.0 (milestone
stage) to simplify the product. We could only identify one user of this
feature and he is switching to RESTful services.
## Project Status
### Project State
Ongoing
### Issues for Board
None
## Membership Data
Apache Cayenne was founded 2006-12-19 (18 years ago).
There are currently 24 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Jurgen Doll on 2024-08-27.
## Project Activity
After the release of 4.2.x, most development has shifted to 5.0. Versions
prior to 5.0 are maintenance-only.
- Cayenne 4.0.x (stable)
- Maintenance only.
- Cayenne 4.1.x (stable)
- Maintenance only.
- Cayenne 4.2.x (stable)
- Maintenance only.
- Cayenne 5.0 (milestone)
- New features and primary development.
Cayenne 4.2.2 (a maintenance/bug-fix release) was released in March.
### Releases
- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2.2 on 2025-03-14.
- Cayenne 5.0.M1 on 2024-09-09.
## Community Health
Cayenne is healthy.
Developer mailing list traffic was about the 4.2.2 release. (The
maintenance release mentioned above).
Code commits were for the 5.0.x and 4.2.2 work.
User mailing list traffic was focused on how to work around a deficiency
which was reported regarding a subclassing issue (to be fixed in 5.0.x)
and answering questions on how to implement solutions for custom Java
types and database mappings.
-----------------------------------------
Attachment K: Report from the Apache CloudStack Project [Nicolás Vázquez]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors,
storage, and networking devices.
## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: None
## Membership Data:
Apache CloudStack was founded 2013-03-19 (12 years ago)
There are currently 142 committers and 60 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Pearl Dsilva was added to the PMC on 2025-04-02
- Jason Hollis (CodeBleu) was added as committer on 2025-05-17
## Project Activity:
Software development/management activity:
- The current version of Apache CloudStack is 4.20.1.0;
- The community is planning to release Apache CloudStack 4.21.0.0 by July 2025.
- The versions released in the past quarter are:
- 4.19.3.0 was released on 2025-06-10.
- 4.20.1.0 was released on 2025-06-10.
- We worked on some security patches and they were included on the
last releases 4.19.3.0 and 4.20.1.0.
Meetups and Conferences:
- We do not plan to attend the Community Over Code NA 2025 with a
specific track.
- The CloudStack European User Group was held on May 8, 2025 in
Vienna, Austria: https://cloudstack.apache.org/blog/cseug-2025/
- CloudStack India User Group 2025 is scheduled for July 11, 2025 in
Delhi-NCR: https://cloudstack.apache.org/blog/csiug-2025
- CloudStack Collaboration Conference 2025 is scheduled for November
19-21, 2025 in Milan, Italy: https://www.cloudstackcollab.org/
## Community Health:
- According to the reporter tool, the Community Health Score (Chi) is
10.00 (Super Healthy).
- Mailing lists statistics:
- dev@cloudstack.apache.org had a 16% increase in traffic in the past
quarter (700 emails compared to 603)
- issues@cloudstack.apache.org had a 18% decrease in traffic in the
past quarter (73 emails compared to 89)
- users@cloudstack.apache.org had a 9% increase in traffic in the past
quarter (1532 emails compared to 1401)
- GitHub statistics:
- 449 commits in the past quarter (-22% decrease)
- 43 code contributors in the past quarter (-25% change)
- 275 PRs opened on GitHub, past quarter (-6% change)
- 255 PRs closed on GitHub, past quarter (-11% change)
- 145 issues opened on GitHub, past quarter (-7% change)
- 126 issues closed on GitHub, past quarter (-29% change)
- Recent releases:
- 4.20.1.0 was released on 2025-06-10.
- 4.19.3.0 was released on 2025-06-10.
- 4.19.2.0 was released on 2025-03-03.
-----------------------------------------
Attachment L: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java-focused
reusable libraries and components.
## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: None.
## Membership Data:
Apache Commons was founded 2007-06-19 (18 years ago)
There are currently 150 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Arnout Engelen on 2024-12-22.
- No new committers. Last addition was Arnout Engelen on 2024-12-23.
## Project Activity:
The project is active with 16 releases during this reporting period.
These were:
- FILEUPLOAD-1.6.0 was released on 2025-06-06 as an Expedited Release
(24 hours) for a yet to be announced CVE in coordination with Tomcat.
- FILEUPLOAD-2.0.0-M4 was released on 2025-06-16 as an Expedited Release
(24 hours) for a yet to be announced CVE in coordination with Tomcat.
- BEANUTILS-1.11.0 was released on 2025-05-27.
- BEANUTILS-2.0.0-M2 was released on 2025-05-27.
- FILEUPLOAD-2.0.0-M3 was released on 2025-05-27.
- EXEC-1.5.0 was released on 2025-05-23.
- PARENT-84 was released on 2025-05-20.
- IMAGING-1.0.0-alpha6 was released on 2025-04-30.
- PARENT-83 was released on 2025-04-30.
- CONFIGURATION-2.12.0 was released on 2025-04-28.
- PARENT-82 was released on 2025-04-25.
- COLLECTIONS-4.5.0 was released on 2025-04-22.
- JXPATH-1.4.0 was released on 2025-04-18.
- JEXL-3.5.0 was released on 2025-04-16.
- IO-2.19.0 was released on 2025-04-12.
- TEXT-1.13.1 was released on 2025-04-10.
- CSV-1.14.0 was released on 2025-03-19.
We've also published the following CVEs:
- BEANUTILS: CVE-2025-48734
- CONFIGURATION: CVE-2025-46392
- VFS: CVE-2025-27553, CVE-2025-30474
## Community Health:
The Commons Community Health is good. We have a steady input of pull requests
on GitHub as well as requests for Jira accounts, and users create Jira tickets
regularly. We are responding to user issues and requests on GitHub, Jira, and
mailing lists, including the security mailing list, in a timely manner. We
are getting requests for releases to many components to pick up bug fixes,
new features, and dependency updates.
-----------------------------------------
Attachment M: Report from the Apache Cordova Project [Bryan Ellis]
## Status report for the Apache Cordova project - June 2025
## Description
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Project Status
**Current project status:**
Our current work continues on staying updated with changes to iOS and Android,
our most utilized platforms, alongside ensuring regular updates to plugins and
tooling.
Our status dashboard at http://status.cordova.io remains mostly all green and
our nightly builds are still stable.
**Issues for the board:**
There are no issues requiring board attention at this time.
## Membership Data
There are currently 100 committers and 97 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
**Community changes, past quarter:**
This quarter, we welcomed Manuel Beck to the Apache Cordova team.
- Last addition was Manuel Beck was added to the PMC on 2025-04-04
- Last addition was Manuel Beck was added as committer on 2025-04-04
## Project Activity
The following releases made to our project this quarter focused on core
platforms and plugins to keep up with current requirements.
**Releases:**
- cordova-android@14.0.1 was released on 2025-04-30.
- cordova-android@14.0.0 was released on 2025-03-25.
- cordova-plugin-media-capture@6.0.0 was released on 2025-02-26.
## Community Health
Overall, the community health is strong. The ASF Project Statistics gives the
project a Community Health Score (Chi): 10.00 (Super Healthy)
This quarter was a little less active compared to the previous one, but we
continue to see valuable contributions from a group of dedicated individuals.
The project remains stable and continues to see good traffic.
Our Android platform package had both a major and a patch release. These
releases focused on providing support for building with the latest major
version of Android.
The Media Capture plugin also received a major update aimed at removing
unnecessary permissions on the Android platform, allowing end users to
evaluate their specific needs and enable only the necessary media-related
permissions.
A few contributors continue to make improvements and prepare for future major
releases of Cordova-iOS. Majority of the large tasks have been completed.
Currently, contributors are reviewing and completing smaller tasks, testing
recent changes, and awaiting the next beta release of iOS to test against.
Github discussions is how our community supports each other and is live at
https://github.com/apache/cordova/discussions. All discussions are forwarded
to the 'issues' list.
## Mailing List Activity
- dev@cordova.apache.org had a 10% increase in traffic in the past quarter
(22 emails compared to 20)
-----------------------------------------
Attachment N: Report from the Apache cTAKES Project [Pei Chen]
## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache cTAKES was founded 2013-03-19 (12 years ago)
There are currently 40 committers and 31 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 Gandhi Rajan on 2018-07-12.
- No new committers. Last addition was Dennis Johns on 2023-01-06.
## Project Activity:
- Committee continues to work on the future release (7.x.x)
- 6.0.0 was released on Sept 16 2024
- 5.1.0 was released on May 10 2024
- 4.0.0.1 was released on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
## Community Health:
There is a steady amount of traffic on dev@ mailing lists.
dev@ctakes.apache.org had a 400% increase in traffic in the past quarter
(15 emails compared to 3):
-----------------------------------------
Attachment O: Report from the Apache Curator Project [Enrico Olivelli]
## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Curator was founded 2013-09-18 (12 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Kezhu Wang on 2023-03-25.
- No new committers. Last addition was Kezhu Wang on 2023-03-24.
## Project Activity:
Recent releases:
5.8.0 was released on 2025-03-06.
5.7.1 was released on 2024-10-13.
5.7.0 was released on 2024-06-15.
## Community Health:
In the past months there has been not much activity on the mailing list and on
GitHub. We started a discussion inside the PMC about inviting new committers.
As this is a small community with a pretty stable codebase I don't think that
this is a big deal, we are used to have waves of contributions, usually
related to ZooKeeper releases or new features.
-----------------------------------------
Attachment P: Report from the Apache Daffodil Project [Mike Beckerle]
## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data Format Description Language (DFDL)
used to convert between fixed format data and more readily processed forms such
as XML or JSON
## Project Status:
Current project status: Ongoing. High activity.
Issues for the board: None.
## Membership Data:
Apache Daffodil was founded 2021-02-16 (4 years ago)
There are currently 19 committers and 18 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 Peter Katlic on 2024-03-17.
- No new committers. Last addition was Peter Katlic on 2024-03-17.
## Project Activity:
As of this writing, new releases of all our outputs are in the works. Daffodil
3.11.0, sbt-daffodil 1.4.0, and the Daffodil VSCode extension v1.4.1 are all
in the works with votes and RCs happening.
For the main library, and supporting sbt-daffodil plugin, the project is
engaged in updating the version of Scala we are using, as we are 2 revisions
behind the current modern Scala. This means we're focused on these painful
infrastructure transitions, and not on fixes or new functionality.
For the VSCode Extension for Daffodil, work has been on better overall error
handling, improved reliability of Data Editor, correcting several schema
completion usability issues and creating new-user onboarding and new developer
onboarding documentation.
## Community Health:
Good activity level in email and commit activity.
Attracting new contributors with diverse interests and uses for the
project remains an ongoing challenge and in the long run, as with all
projects, is a risk factor.
In our prior report we raised concern about risk to the project
because of USG funding uncertainty. The current primary user
community for Daffodil is in cyber security, and this remains a USG
funding priority according to statements from the current USG
administration. So our concern has been lessened about sudden loss of
current funding for our contributors.
-----------------------------------------
Attachment Q: Report from the Apache DataFusion Project [Andrew Lamb]
## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine
## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache DataFusion was founded 2024-04-16 (a year ago)
There are currently 47 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Berkay Şahin was added to the PMC on 2025-04-26
- Xudong Wang was added to the PMC on 2025-05-23
- Adrian Garcia Badaracco was added as committer on 2025-05-23
- Dmitrii Blaginin was added as committer on 2025-04-30
- Marko Milenković was added as committer on 2025-03-17
## Project Activity:
Note that almost all communication for DataFusion and its subprojects happens
on github and so our dev mailing list traffic is fairly light.
### DataFusion core
- 48.0.0 was released on 2025-06-11.
- 47.0.0 was released on 2025-04-20.
- 46.0.1 was released on 2025-03-19.
- 46.0.0 was released on 2025-03-07.
https://github.com/apache/datafusion
Releases continue monthly and the project has been very active with many
commits a day. Our community roadmap discussion is public[1] and gives insight
into where we are heading. As always we are light on communicating in
non-github ways about the status of the project, but hope to write a blog post
soon.
We held a DataFusion meetup in San Francisco in June 2025[2]
We also have written several [blog] posts such as on [user defined window
functions], and a [TPCH data generator]
[1]: https://github.com/apache/datafusion/issues/15878
[2]: https://github.com/apache/datafusion/discussions/15657
[blog]: https://datafusion.apache.org/blog/
[user defined window functions]: https://datafusion.apache.org/blog/
2025/04/19/user-defined-window-functions/
[TPCH data generator]: https://datafusion.apache.org/blog/
2025/04/10/fastest-tpch-generator/
### Sub project: DataFusion Python
https://github.com/apache/datafusion-python
- PYTHON-47.0.0 was released on 2025-05-28.
- PYTHON-46.0.0 was released on 2025-03-30.
We recently added support for user defined [scalar and aggregate functions],
and [window functions]
[scalar and aggregate functions]: https://github.com/apache/
datafusion-python/pull/1040
[window functions]: https://github.com/apache/datafusion-python/pull/1061
### Sub project: DataFusion Comet
https://github.com/apache/datafusion-comet
- COMET-0.8.0 was released on 2025-04-26.
- COMET-0.7.0 was released on 2025-03-17.
You can read about the recent happenings in Comet in the [0.8.0 blog]
[0.8.0 blog]: https://datafusion.apache.org/blog/
2025/05/06/datafusion-comet-0.8.0/
### Sub project: DataFusion Ballista
https://github.com/apache/datafusion-ballista
- BALLISTA-46.0.0 was released on 2025-05-17.
- BALLISTA-45.0.0 was released on 2025-04-08.
### Sub project: DataFusion For Ray
We are still working towards an initial release in DataFusion For Ray. Thanks
to feedback from our last report, we have updated the project name to make it
clear this is not part of the Ray project itself.
### Sub project: sqlparser-rs
https://github.com/apache/datafusion-sqlparser-rs
- SQLPARSER-0.56.0 was released on 2025-05-02.
Ifeanyi Ubah (iffyio) continues to do a great job reviewing PRs to keep the
code consistent and flowing and we are keeping up the pace with bi-montly
releases.
## Community Health:
While we as always struggle with code review capacity,
we have many active committers, and the community in general helps each
other out with reviews. We continue to actively grow our committer
and PMC ranks.
We continue to merge multiple PRs a day from multiple committers and
have contributions from a wide variety of individuals with a wide
variety of employers.
-----------------------------------------
Attachment R: 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 is not much active development, but while discussing the future of DS
it turned out that we got more than a hand full of PMC replies.
Definitely more than enough to do votes.
Imo there is thus no need to act immediately, but we surely need to do
have a plan for the future development. We started by listing up all the
features we want to still support in the future. We also need to create
some documentation about migration scenarios for features we don't want
to support in the future. This is all regarding the health of DS itself.
Another thing which became clear is that quite a few EE projects are
suffering from spec release related bursts of activity followed by
phases of low activity. There are a few TLP which suffer from this effect
and those mostly contain of the same people anyway. So it might make
sense to establish a new TLP and move some projects with not so high
activity as subprojects under this new TLP. Ofc this needs proper planning
and time to prepare.
## 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.0 (Jakarta) was released on 2024-04-10.
- 1.9.6 was released on 2022-04-12.
- 1.9.5 was released on 2021-03-10.
-----------------------------------------
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:
We are still working out some bugs but will have a bug fix and major release
out shortly.
Recent releases:
1.21.1 was released on 2023-04-29.
1.21.0 was released on 2023-02-21.
1.20.3 was released on 2023-01-07.
## Community Health:
Community health is ongoing but relatively quiet. We are getting a
steady flow of issues and PRs resolves. Much of the user activity
is on an apparently unofficial Slack channel for which we do not have
metrics.
I see that the reporting tool has removed the mailing list stats, as
well as code commit statistics. It would be helpful if those were restored.
-----------------------------------------
Attachment T: Report from the Apache ECharts Project [Wenli Zhang]
## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript
## Project Status:
Current project status: Ongoing
Issues for the board: NA
## Membership Data:
Apache ECharts was founded 2020-12-16 (4 years ago)
There are currently 30 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was ShiZhao Pan on 2025-01-09.
- No new committers. Last addition was ShiZhao Pan on 2025-01-05.
## Project Activity:
We are working towards our next major release 6.0.0 and should start release
voting in about two weeks. In this version, we are going to release important
features like matrix layout, advanced custom series, chord series, and so on.
## Community Health:
The community is developing steadily. There are no major issues that are
particularly worthy of concern. We can look forward to more exciting progress
and achievements after the release of 6.0.0.
-----------------------------------------
Attachment U: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Project Status:
Current project status: Ongoing, with low activity.
Issues for the board: none.
## Membership Data:
Apache Felix was founded 2007-03-27 (18 years ago)
There are currently 68 committers and 26 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 Georg Henzler on 2019-06-09.
- No new committers. Last addition was Paul Rütter on 2024-11-15.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- Released 8 components. Mostly bug fixes/minor improvements related to jetty
updates.
### Releases
- org.apache.felix.http.base-5.1.16 was released on 2025-06-08.
- org.apache.felix.http.jetty12-1.0.34 was released on 2025-06-06.
- org.apache.felix.http.jetty12-1.0.32 was released on 2025-05-26.
- org.apache.felix.http.base-5.1.14 was released on 2025-05-14.
- org.apache.felix.http.bridge-6.0.0 was released on 2025-05-14.
- org.apache.felix.http.jetty-5.1.34 was released on 2025-05-14.
- org.apache.felix.http.jetty12-1.0.30 was released on 2025-05-14.
- org.apache.felix.webconsole-5.0.12 was released on 2025-05-13.
- org.apache.felix.http.base-5.1.12 was released on 2025-04-25.
- org.apache.felix.http.jetty12-1.0.28 was released on 2025-04-25.
- org.apache.felix.healthcheck.core-2.3.0 was released on 2025-04-18.
- org.apache.felix.http.servlet-api-6.1.0 was released on 2025-04-18.
- org.apache.felix.http.wrapper-6.1.0 was released on 2025-04-18.
- org.apache.felix.http.jetty-5.1.32 was released on 2025-03-24.
- org.apache.felix.http.jetty12-1.0.26 was released on 2025-03-24.
- org.apache.felix.http.jetty-5.1.30 was released on 2025-03-13.
- org.apache.felix.http.jetty12-1.0.22 was released on 2025-03-13.
- org.apache.felix.http.wrapper-1.0.8 was released on 2025-03-13.
- org.apache.felix.http.wrapper-1.1.10 was released on 2025-03-13.
- org.apache.felix.http.webconsoleplugin-1.2.2 was released on 2025-03-12.
## Community Health:
- Overall the project is in ok health with little ongoing activity.
- The community activity remains on a low level and we continue to see little
new development right now.
- We voted on a new PMC member, acceptance is pending.
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues.
- We had no issues voting on releases and JIRA issues are generally addressed.
-----------------------------------------
Attachment V: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment W: Report from the Apache Flink Project [Robert Metzger]
## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Flink was founded 2014-12-17 (10 years ago)
There are currently 121 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Sergey Nuyanzin was added to the PMC on 2025-04-03
- Zakelly Lan was added to the PMC on 2025-03-31
- Yanquan Lv was added as committer on 2025-04-17
- Xiqian Yu was added as committer on 2025-04-21
## Project Activity:
Releases:
- Flink Kubernetes Operator 1.12 on 2025-06-03
- cdc-3.4.0 was released on 2025-05-16.
- connector-kafka-4.0.0 was released on 2025-04-24.
- connector-jdbc-3.3.0 was released on 2025-04-22.
- connector-jdbc-4.0.0 was released on 2025-04-22.
- Flink 2.0 was released on 2025-03-24 with many new features and
cleanups in the APIs, configuration etc.
Other activity:
- The community decided to start a new flink-agents repository to
explore agentic AI use-cases for Flink
- We are working towards Flink 2.1 with a feature freeze by June 21
## Community Health:
The metrics suggest an increase of activity on the dev@ mailing list.
There tends to be a lack of PR reviewers for PRs from
new contributors, or parts of Flink that lack active committers,
such as some connectors.
We try to address this by experimenting with a community review process,
where contributors can pre-review PRs.
-----------------------------------------
Attachment X: Report from the Apache Gobblin Project [Abhishek Tiwari]
## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Gobblin was founded 2021-01-19 (4 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was Abhishek Mahendra Jain on 2025-01-18.
- Vivek Rai was added as committer on 2025-01-18.
## Project Activity:
- Fixed ACL mismatch during manifest-based copy by removing destination ACLs
after directory creation and copying source directory ACLs.
- Made the temporal unique classifier GaaS attempt-aware for better tracking
of job attempts.
- Fixed the issue of an extra permission bit being set in Manifest-based
DistCp.
- Added a data quality field in GaaSJobObservabilityEvent to enhance
observability of job quality.
- Support added for Delete Manifests in Apache Iceberg Full Table Replication.
- Support added for more fine grained tracking by switching from cumulative to
delta aggregation in Open Telemetry metrics.
- Handled exceptions in DagProcessingEngine to log errors instead of throwing
exceptions, preventing thread termination and allowing continued Dag
processing.
- Made Orchestrator support generic by replacing Azkaban execution ID with
GaaS execution ID, while ensuring backward compatibility.
- Added support for dynamic container scaling, based on target completion time
and work unit count, to optimize resource allocation and improve job
efficiency.
* Last Release date: 30th August, 2023.
## Community Health:
- There have been 12 commits since Mar 2025.
- 8 commits have been from non-committers.
- Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as
committers. We constantly look for consistent contributors to vote them in
as Committers.
-----------------------------------------
Attachment Y: Report from the Apache Gravitino Project [Jerry Shao]
## Description:
Apache Gravitino is a high-performance, geo-distributed, and federated
metadata lake. It manages metadata directly in different sources, types, and
regions, providing users with unified metadata access for data and AI assets.
## Project Status:
Current project status: New Issues for the board: No
## Membership Data:
Apache Gravitino was founded 2025-05-20 (15 days ago) There are currently 26
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
2:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- Eric Chang was added as committer on 2025-05-29
## Project Activity:
- Gravitino 0.9.0 was released on 2025-05-07.
Recent developments on Gravitino:
- Metadata authentication features are actively developed on the dev branch.
- Cache mechanism, the development is smoothly ongoing.
- Policy system, the API interface is merged, the following PRs are ongoing.
- Statistics system, the API interface is ongoing.
- Various good first issues have been resolved.
- Documents, websites, and other sources have been updated to reflect the TLP.
- Adjust the PMC roster.
## Community Health:
The Gravitino community continues to be healthy, with a large number of
commits and individual contributors over the last month. 85 PRs got merged,
106 issues were created, and 49 issues were resolved in the last month.
The activities of commits compared to the previous month are slightly
decreased, this is mainly because a new version has just been released, most
of the contributors are working on designing the next version's features. The
activities of issues and discussion are still quite healthy.
The PMC roster has been adjusted, however, there is still a minor issue with a
couple of non-PMC members subscribed to the private mailing list.
Several Gravitino talks have been accepted for upcoming conferences, including
the Open Source Summit and Community over Code NA and Community over Code
Asia.
-----------------------------------------
Attachment Z: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment AA: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Guacamole was founded 2017-11-14 (8 years ago)
There are currently 16 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- No new committers. Last addition was Corentin Soriano on 2025-01-18.
## Project Activity:
The first RC of 1.6.0 needed to be cancelled to address regressions. The
project is now moving forward with fixing those regressions in preparation for
RC2.
Recent releases:
- 1.5.5 was released on 2024-04-05.
- 1.5.4 was released on 2023-12-07.
- 1.5.3 was released on 2023-07-31.
## Community Health:
The community continues to be active and healthy. Activity on the mailing
lists has been steady, including extremely helpful testing during and after
the first RC of 1.6.0.
-----------------------------------------
Attachment AB: Report from the Apache Gump Project [Stefan Bodewig]
## Description
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well as
non-ASF projects and their dependencies. It started in the Java part
of the foundation but also builds projects like APR, HTTPd and
OpenSSL.
## Project Status
Current Status: dormant - when things need to be done, they get done
Issues: There are no issues requiring board attention.
## Membership Data
Apache Gump was founded 2004-02-18. There are currently 16 committers
and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
### Community changes, past quarter:
No new PMC members. Last addition was Mark Thomas on 2014-12-03.
No new committers. Last addition was Konstantin Kolinko on 2015-02-11.
## Project Activity
The Tomcat community is the only one still using Gump actively and the
only activity in Gump is around keeping the infrastructure alive and
tweaking things for the benefit of Tomcat builds.
We will certainly support any other project that wants to get the
benefit of the early warning system for backwards incompatible changes
Gump provides, but we are not actively recruiting projects.
### Releases
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
## Community Health
There isn't much happening but help is there when anybody needs it.
-----------------------------------------
Attachment AC: Report from the Apache Helix Project [Junkai Xue]
## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: Nothing
## Membership Data:
Apache Helix was founded 2013-12-17 (11 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- No new committers. Last addition was Molly Gao on 2023-06-06.
## Project Activity:
- 1.4.3 was release 2025-01-28
- 1.4.2 was release 2024-11-18
## Community Health:
Two major items the community are working on:
1. Helix 2.0 release: Helix 2.0 features are completed in development. The
tests were performed. Waiting for final walk through then merge to main
branch. Target to release in July.
2. Usability and stability improvements: a couple of usability and stability
improvements are in reviewing including test fixing, npe avoidance and etc.
3. Seeing more new contributors start investigating Helix codebase.
-----------------------------------------
Attachment AD: Report from the Apache Hive Project [Naveen Gangam]
-----------------------------------------
Attachment AE: Report from the Apache Hop Project [Hans Van Akelyen]
## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hop was founded 2021-12-15 (3 years ago)
There are currently 24 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bart Maertens on 2021-12-15.
- No new committers. Last addition was Sergio De Lorenzis on 2024-06-11.
## Project Activity:
We have had 2 releases since the latest report. We have also decided to go to
a fixed release schedule to make it clearer to the end users when they can
expect a new release that needs testing. Our release schedule will be
quarterly with a 1-month offset.
## Community Health:
I think our metrics are healthy, we have a steady inflow of interacitons
on issues, discussions and pull requests. Mailing lists interaction
is limited but everything happing on GitHub is funneled there.
I think we have seen a small uptick in first time contributors over
the past months.
-----------------------------------------
Attachment AF: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hudi was founded 2020-05-19 (5 years ago)
There are currently 40 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Sagar Sumit on 2023-11-05.
- No new committers. Last addition was Vova Kolmakov on 2024-09-13.
## Project Activity:
The community has been actively working on Hudi core Java implementation and
Hudi-rs native implementation. Hudi 1.0.2 was released to further stabilize
the 1.0 milestone release and improve user adoption. Hudi 1.1 is under active
development with refactoring on key code paths to lay out a solid foundation
for building new features. Hudi-rs 0.4.0 is under development with new C++
APIs and full MOR support to be featured in the release.
## Community Health:
We continue to see steady growth in community engagement on GitHub, with
active participation in code contributions and discussions. The dev and
users lists serve as primary channels for low-bandwidth communication,
while GitHub issues continue to be the main engagement model for
community support. The PMC continues to host the monthly developer sync calls.
-----------------------------------------
Attachment AG: Report from the Apache Iceberg Project [Ryan Blue]
## Description:
Apache Iceberg is a table format for huge analytic datasets that is designed
for high performance and ease of use.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Iceberg was founded 2020-05-19 (5 years ago)
There are currently 34 committers and 21 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 Amogh Jahagirdar on 2024-08-12.
- No new committers. Last addition was Huaxin Gao on 2025-02-06.
## Project Activity:
Releases:
- Table spec v3 was adopted on 2025-05-22
- Java 1.9.1 was released on 2025-05-28
- Java 1.9.0 was released on 2025-04-28
- Java 1.7.2 was released on 2025-03-19
- PyIceberg 0.9.1 was released on 2025-04-30
- Rust 0.5.1 was released on 2025-05-31
- Rust 0.5.0 was released on 2025-05-26
- Go 0.3.0 was released on 2025-05-29
- Go 0.2.0 was released on 2025-03-26
Table spec:
- v3 of the Iceberg spec was adopted by a community vote! Full support for v3 is
targeted for the upcoming Java 1.10.0 release and other implementations are
adding support.
- Planning for Iceberg v4 has started, with groups self-organizing around
projects like faster commits, columnar metadata, and relative path support
Java:
- Added support for Spark 4.0, removing support for 3.3
- Implemented v3 row lineage support in Spark MERGE and UPDATE
- Added a connector for the BigQuery catalog
- Added support for Flink 2.0 and removed Flink 1.18
- Ongoing work to develop a dynamic Flink sync handles table schema changes
- Added Zookeeper locking for Flink table maintenance
- Refactored REST catalog client to use AuthManager
- Added reader/writer for partition stats files
- Completed the core implementation of Variant type
PyIceberg:
- Exceeded 500,000 downloads in a single day
- Refactoring OAuth for REST catalogs with an AuthManager, like Java
- Working on adding optimistic concurrency
- Added support for decimal backed by int32/int64
- Fixed "upsert" with complex types
Rust:
- Adding support for v3 metadata fields and encryption fields
- Now exports DataFusion table provider to Python bindings
- Added support to add existing Parquet files
- Added support for Apache Arrow dictionary type
- Added support for writing Puffin files
- Runs sqllogictests using DataFusion
Go:
- Added write and commit support
- Added support for the Glue catalog
- Supports REST catalog integration tests
C++:
- Added virtual classes for API concepts: Catalog, Table, file readers/writers
- Added manifest and manifest list structures
- Added TypeVisitor, support for converting schemas to Avro
- Added expressions, sort orders, and partition specs
- Added support for configuration files similar to those used by PyIceberg
## Community Health:
Health metrics:
- Code contributors increased by 23%, on top of a 20% rise last quarter!
- Most metrics were stable; issues closed dropped due to an outlier day
Iceberg Summit 2025 was held April 8th (in person) and 9th (virtual). 62 talks
are now available from the project's youtube channel.
https://www.youtube.com/playlist?list=PLkifVhhWtccxMcqWlXXFvjJybisFF7ESh
In the 11 months between Iceberg Summit 2024 and 2025, there were:
- 16 releases across Java, Python, Rust, and Go
- 250 new contributors
- 7 new committers
- 5 new PMC members
- 1 new language implementation (C++)
-----------------------------------------
Attachment AH: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for June 2025
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 35 podlings incubating. In May, podlings executed six
distinct releases, and two IP clearances occurred. Several incubating
proposals have been discussed and are presently undergoing voting on the
mailing list (GeaFlowa and Fluss), and a new project Caldera, is being
discussed. We also have one new podling called Burr, and two projects,
Gravitinto and StormCrawler graduated last month. One person was added to
the IPMC.
No podlings have retired, but a couple are still talking about it. Five
podlings failed to report and will be asked to report next month.
Conversations on the list have been focused on releases, new incubating
projects, and the incubation process.
Tracking projects that have been incubating for a long time, Annotator is
discussing retirement, Nemo is votng for it, and Toree is slowly moving
towards graduation. The Livy PPMC has been slow to respond, and there
is a roll call to see if they have an active PMC. NLPCraft did report
this month, but the roll call sent a month ago has received two responses.
Training is ready to graduate.
Finally, note that last month’s incubator report was submitted on time but
did not receive sufficient Director sign-offs. It has been appened to the
bottom of this report.
## Community
### New IPMC members:
- Nicholas Jiang
### People who left the IPMC:
- None
## New Podlings
- Burr
## Podlings that failed to report, expected next month
- Annotator
- Grails
- Iggy
- KIE
- PonyMail
## Graduations
- Gravitino
- StormCrawler
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
May:
- Amoro 0.8.0
- Fury 0.10.2
- Fury 0.10.3
- Gravitino 0.8.1
- Gravitino 0.9.0
- Hertzbeat 1.7.1
## IP Clearance
- Arrow Flight SQL ODBC Driver
- easy-cass-stress
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[Baremaps](#baremaps)
[BifroMQ](#bifromq)
[Hamilton](#hamilton)
[Nemo](#nemo)
[NLPCraft](#nlpcraft)
[OpenServerless](#openserverless)
[Otava](#otava)
[OzHera](#ozhera)
[Polaris](#polaris)
[PouchDB](#pouchdb)
[Teaclave](#teaclave)
[Texera](#texera)
[Training](#training)
[Wayang](#wayang)
--------------------
## Baremaps
Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.
Baremaps has been incubating since 2022-10-10.
### Three most important unfinished issues to address before graduating:
1. Expanding the community
2. Making releases
3. Starting the graduation process
### 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?
There has been an uptick in activity early this year, which has since
slowed down.
One difficulty we face is related to the onboarding and retention of new
contributors.
We have a number of easy bug fixes that are suitable for newcomers, but we
also have advanced features that require a deeper understanding of the
codebase.
This can be intimidating for new contributors, leading to a lack of
engagement after initial contributions.
### How has the project developed since the last report?
We released version 0.8.2 in February 2025.
Since then, we have added support for Apache Calcite, which will open the
door to spatial SQL queries on various data sources (flatgeobuf, PostGIS,
geopackage, geoparquet, etc.).
We also fixed a number of bugs and upgraded dependencies.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-07
### When were the last committers or PPMC members elected?
Sébastien Riollet in June 2024
### Have your mentors been helpful and responsive?
Yes, Julian Hyde and Calvin Kirs provided valuable feedback.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (baremaps) Bertrand Delacretaz
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
- [ ] (baremaps) Julian Hyde
Comments:
- [X] (baremaps) Calvin Kirs
Comments:
- [ ] (baremaps) George Percivall
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
### IPMC/Shepherd notes:
PJF: The BareMaps active community remains small. Possibly, too small to
be be able to become a self-managing PMC on graduation.
JM: They have added 3 committers. I would suggest they look to see if any
of those or any other committers can be made PPMC members.
--------------------
## 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. Successful repository migration and completion of the first release
process
2. Website building and grow the community
3. Complete the Trademark Assignment process
### Are there any issues that the IPMC or ASF Board need to be aware of?
Baidu manages the SGA, CCLA, and Trademark Assignment as a unified
"Corporate Contract" workflow. The SGA and CCLA documents have been
successfully submitted to the ASF.
We are eager to advance the Trademark Assignment process to finalize the
Corporate Contract workflow, rather than delaying it until graduation from
the incubator.
### How has the community developed since the last report?
- Added 2 contributors since incubation began
### How has the project developed since the last report?
- Two repositories have been transferred to the Apache GitHub organization
(apache/bifromq, apache/bifromq-sites).
### 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-02-25
### When were the last committers or PPMC members elected?
None since joining 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?
Yes, The name 'BifroMQ' has passed the name search:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-237
### Signed-off-by:
- [ ] (bifromq) Christofer Dutz
Comments:
- [ ] (bifromq) Xiangdong Huang
Comments:
- [X] (bifromq) Calvin Kirs
Comments: Progress is going well.
- [ ] (bifromq) Penghui Li
Comments:
- [ ] (bifromq) Sheng Wu
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 captureobservability output from workflow
runs. Apache Software Foundation incubation will establish
Hamilton as a community-driven standard.
Hamilton has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Finish repo setup.
2. Go through first release process.
3.
### 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?
N/A
### How has the project developed since the last report?
N/A
### 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:
No apache release yet.
### When were the last committers or PPMC members elected?
2025-04-12
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
Name is approved:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-235
### Signed-off-by:
- [ ] (hamilton) Kevin Ratnasekera
Comments:
- [X] (hamilton) Ayush Saxena
Comments: In the initial stage: setting up resource & gearing up for
the first ASF release
- [X] (hamilton) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
### Three most important unfinished issues to address before graduating:
1. Remove the dependency on REEF
2. Revitalize the community
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
- There is no activity in the community.
### How has the community developed since the last report?
- There has been no notable activity since the last report.
### How has the project developed since the last report?
- There has been no notable activity 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
- [ ] Community building
- [ ] Nearing graduation
- [X] Other:
### Date of last release:
2022-09-22
### When were the last committers or PPMC members elected?
September 28, 2021
### Have your mentors been helpful and responsive?
N/A
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (nemo) Hyunsik Choi
Comments:
- [X] (nemo) Byung-Gon Chun
Comments: The podling is considering retirement.
- [X] (nemo) Jean-Baptiste Onofré
Comments: The podling is retired.
- [ ] (nemo) Markus Weimer
Comments:
### IPMC/Shepherd notes:
CalvinKirs[kirs]: The podling is considering retirement.
JM: There is a vote underway to retire the project.
--------------------
## NLPCraft
A Scala library for NLU applications
NLPCraft has been incubating since 2020-02-13.
### Three most important unfinished issues to address before graduating:
1. Take a clear niche in NLP development by focusing on supporting
deterministic functions and their advantages over the LLM-based approach
in
some application domains.
2. Extending the technology stack
3. Community growth.
### 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?
- We continue investigating LLM integration and experimenting with the MCP
approach.
- We continue research mini-projects with potential customers and users,
including LoomHR.ai and Humatron.ai, whose developers may join the
community.
### How has the project developed since the last report?
- Technical PRs processed.
- Research and investigation tasks related to sLLMs and MCP approach.
### 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:
2023-02-30
### When were the last committers or PPMC members elected?
August of 2021.
### Have your mentors been helpful and responsive?
No Answer.
### Is the PPMC managing the podling's brand / trademarks?
No Answer.
### Signed-off-by:
- [X] (nlpcraft) Furkan Kamaci
Comments:
- [ ] (nlpcraft) Evans Ye
Comments:
- [ ] (nlpcraft) Paul King
Comments:
- [ ] (nlpcraft) Konstantin I Boudnik
Comments:
### IPMC/Shepherd notes:
PJF: The NLPCraft active community is quite small. Possibly, too small to
be able to operate as a self-managing PMC on graduation.
JM: The recent roll call got one person who wants to continue development
and one who wants to continue mentoring. A dev list email on next steps got
no responses. The IPMC may have to consider retiring the project.
--------------------
## OpenServerless
OpenServerless is an open source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an
unified developer experience with a plethora of services (SQL or noSQL
databases, key-value stores, object storage, LLMs services, function
schedulers) managed by the platform's core: the operator, along with tooling
(the CLI) to simplify (and interact with) deployments, integrated ide and
starter application and optimized runtimes integrated with the staters.
OpenServerless has been incubating since 2024-06-17.
### Three most important unfinished issues to address before graduating:
1. Strengthen the community
2. Assess the requirements for the First Release
3. continue the process of documenting the entire platform.
### 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. The Apache OpenServerless and AI course - currently in Italian - was
completed by at least a couple hundred developers and some of them are
using actively the platform.
2. The AI course is being extended to support also MCP api.
3. Two new contributors joined the projects.
4. We're in the process of release some videos to show installation on
local machines and cloud servers.
5. We've published an article on the
[Opensource.net](https://opensource.net/apache-openserverless-is-the-easiest
-way-to-build-your-cloud-native-ai-application/) blog.
### How has the project developed since the last report?
1. We improved various parts of the project, fixing bugs and reviewed the
documentation.
2. Closed 19 issues. Opened 6 new issues.
3. Improved the OpenServerless streamer (openserverless-streamer),
introducing new code and documentation.
4. Preparing an upgrade to OpenWhisk 2.
5. We have opened a new PR towards the Apache OpenWhisk project to
support JDK17 based builds.
6. We have added a new openserverless-build project with the objective of
preparare OpenWhisk 2 multiplatform images tailor made for our project and
we aim to provide a native executable for the standalone component, with
the objective of providing a lighter development environment.
### 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:
None
### When were the last committers or PPMC members elected?
2024-08-22
### Have your mentors been helpful and responsive?
Yes, and we renew our thanks to all of them for their continued support
in developing this project, allowing us to meet the required standards.
### Is the PPMC managing the podling's brand / trademarks?
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved
### Signed-off-by:
- [ ] (openserverless) Bertrand Delacretaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [ ] (openserverless) François Papon
Comments:
- [X] (openserverless) JB Onofré
Comments:
- [X] (openserverless) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## Otava
Apache Otava (incubating) performs statistical analysis of performance
test results stored in CSV files, PostgreSQL, BigQuery, or Graphite
database. It finds change-points and notifies about possible performance
regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze
the recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the
environment.
* Otava has been incubating since 2024-11-27. Otava entered Incubation
as Hunter. The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Publish the first release under the new name.
( htts://s.apache.org/ahsxx) We are still iterating on getting
Incubator PMC passed.
2. Publish the existence of Apache Otava (Incubating), and our first
release.
3. ???
### How has the community developed since the last report?
Unchanged. Everone is now waiting for the first release.
Henrik participated in International Conference on Performance
Engineering 2025 and gave a short presentation on the 8 year history
of Otava. (The talk had initially been proposed to the conference
before we became and Apache incubating project. We learned of some
users that we weren't previously aware of. Most notably Red Hat
uses Otava (née Hunter) to analyze performance test results from
OpenShift.
### How has the project developed since the last report?
We are focused on making our first release.
### How would you assess the podling's maturity?
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [X] Other:
A self review based on https://s.apache.org/727vc
* Code 3/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
The first release was happening as this report was submitted
### Date of last release:
We are actively working on our first release, trying to get
all the details of the release process right.
### When were the last committers or PPMC members elected?
The major contributors during the past 8 years were listed
as PPMC members in the project application pase. We have not
elected any new members after that.
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
This isn't yet an issue, as the new name of the project is quite
unknown yet.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [X] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
JM: Thanks for the detailed report and the maturity model self-review.
--------------------
## OzHera
OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such as
metric monitoring, trace tracking, logging, and alerting
OzHera has been incubating since 2024-07-11.
### Three most important unfinished issues to address before graduating:
1.Make more apache release.
2.Build and grow 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.Collectively discuss plans for community promotion and development.
2.Actively participate in community activities and seek development
channels for projects(Apply propsal for Community Over Asia Session 2025).
### How has the project developed since the last report?
1.Completed the first version release of apache.
2.Development of basic functions for intelligent analysis of link root
causes.
3.Expand business indicator alarm capabilities.
4.Log function iteration and optimization.
5.Clean up and correct historical error paths and information references.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-03-26
### When were the last committers or PPMC members elected?
2025-01-13
### Have your mentors been helpful and responsive?
Yes, mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Not yet.
### Signed-off-by:
- [ ] (ozhera) Yu Xiao
Comments:
- [ ] (ozhera) Yu Li
Comments:
- [ ] (ozhera) Kevin Ratnasekera
Comments:
- [ ] (ozhera) Duo Zhang
Comments:
### IPMC/Shepherd notes:
--------------------
## Polaris
Polaris is a catalog for data lakes. It provides new levels of choice,
flexibility and control over data, with full enterprise security and Apache
Iceberg interoperability across a multitude of engines and infrastructure.
Polaris has been incubating since 2024-08-09.
### Three most important unfinished issues to address before graduating:
1. Finalize "complete" release (including binary distributions and
artifacts), and adopt regular releases pace
2. Grow the community
3. Fill out the maturity model
### 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?
Regarding the user community:
* On Slack, since March, we have 17 threads from new users (28 new users
in May, 53 new users in April, 53 new users in March)
* On GitHub Issues, we had 11 new issues created by new users.
* On the dev mailing list, we had 196 messages in March, 144 in April, 279
in May, mostly from Polaris committers/contributors. It seems the users
prefer to ask questions on Slack.
Regarding the dev community:
* We had 7 Pull Requests from 7 new contributors
* We are discussing with the Apache XTable community (for multi table
formats support)
* Community meetings happened on 2025-04-03 and 2025-04-17 (recorded and
publicly available)
In order to build/grow the Polaris community, we participated to
different events (meetups, etc) to introduce Apache Polaris:
* Open Source Data Deep Dive: London (2025-05-21)
* Current 25 London (2025-05-20)
* Open Source Data Deep Dive: Barcelona (2025-05-15)
* Munich Database Meetup: Analytics Data Stack (2025-05-13)
### How has the project developed since the last report?
We added the polaris-tools repo (https://github.com/apache/polaris-tools)
to host parts of the project (benchmark tool, catalogs migrator, ...) not
directly related to the Polaris "catalog server".
Highlights in the project developed:
* We refactored the persistence layer to use pure JDBC now and we
deprecated EclipseLink use.
* We are working on gather server and tool in an unique distribution
* Several proposals are in discussion right now (event/observe API, async
tasks, spark client, ...)
In preparation for 1.0-incubating release, we are voting 0.10-incubating
release.
We are focusing on 1.0-incubating release, the release process should
start
quickly after 0.10-incubating release vote pass.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-25
### When were the last committers or PPMC members elected?
Last committers: Ajantha Bhat, Pierre Laporte, Prashant Singh, Jonas Jiang
elected on 2025-04-30
Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on
2025-03-25
### Have your mentors been helpful and responsive?
Yes, helpful in releases review and reporting issues.
### Is the PPMC managing the podling's brand / trademarks?
Polaris PPMC is working with 3rd parties willing to use Polaris
brand/trademarks, according to
https://incubator.apache.org/guides/publicity.html and
https://incubator.apache.org/guides/branding.html.
### Signed-off-by:
- [ ] (polaris) Bertrand Delacretaz
Comments:
- [ ] (polaris) Holden Karau
Comments:
- [X] (polaris) Kent Yao
Comments: LGTM
- [ ] (polaris) Ryan Blue
Comments:
- [X] (polaris) JB Onofré
Comments:
### IPMC/Shepherd notes:
--------------------
## PouchDB
PouchDB is an open-source JavaScript database inspired by Apache CouchDB
that is designed to run well within the browser.
PouchDB has been incubating since 2025-04-15.
### Three most important unfinished issues to address before graduating:
1. Get the project up and running (no blockers)
2. Follow the graduation progression, in particular make a new release
under the ASF Incubator.
3. Grow 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?
We are still in the setup phase.
### How has the project developed since the last report?
TLD & mailing lists have been created, initial committers have started
filing their CLAs.
We have cleared all remaining code-import issues with Infra.
Once CLAs are all in place, we can tackle IP-clearance and coder import.
### 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:
N/A
### When were the last committers or PPMC members elected?
N/A
### Have your mentors been helpful and responsive?
Helpful and proactive.
### Is the PPMC managing the podling's brand / trademarks?
N/A
### Signed-off-by:
- [X] (pouchdb) PJ Fanning
Comments:
- [X] (pouchdb) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
--------------------
## Teaclave
Teaclave is a universal secure computing platform, enabling writing
memory-safe trusted applications in Rust running inside Trusted Execution
Environment.
Teaclave has been incubating since 2019-08-20.
The Teaclave community is now working towards graduation.
### Three most important unfinished issues to address before graduating:
1. Complete all requirements of the Project Maturity Assessment.
2. Practice future releases by adhering to a quarterly release schedule.
3. Conduct a thorough self-assessment to ensure all Apache graduation
criteria are met.
### Are there any issues that the IPMC or ASF Board need to be aware of?
As the Teaclave community works toward graduation, we welcome guidance
along the process. We also invite any active IPMC members interested in
the
project to consider becoming mentors. Thank you.
### How has the community developed since the last report?
- Two new participants have joined the project.
- Ecosystem growth: The newly published crates on `crates.io` have
collectively surpassed 4,000 downloads.
### How has the project developed since the last report?
- Completed the process for releasing Teaclave TrustZone SDK v0.4.0.
- Initiated the Teaclave Maturity Assessment. During the assessment, we
identified several areas for improvement, including the website page and
repository documentation. Work is in progress to address these and meet
all
requirements.
### 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:
2025-06-03 Apache Teaclave TrustZone SDK (incubating) v0.4.0
### When were the last committers or PPMC members elected?
2025-01-21
### Have your mentors been helpful and responsive?
We appreciate the support of our mentors. However, due to the length of
the
incubation period, some mentors have become less active. This has impacted
our release process, with the most recent release vote taking
approximately
10 weeks to close, involving two binding votes from our mentors.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [X] (teaclave) Felix Cheung
Comments:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
- [ ] (teaclave) Gordon King
Comments:
### IPMC/Shepherd notes:
JM: Feel free to remove inactive mentors and ask for new ones on the IPMC
mailing list.
--------------------
## 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 that
supports 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 operator states and resume 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. Complete the SGA form.
2. Donate the Texera codebase from the
[Texera/texera](https://github.com/Texera/texera) GitHub repo to the
Apache/Texera repo.
3. Set up the Apache Texera webpage http://texera.apache.org/.
### 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?
- 2025-04-12: The project enters the incubation phase.
- 2025-05-12: We have expanded our PPMC members to 12 members. All of them
have signed and submitted their iCLA forms. The latest members (excluding
mentors) are listed as follows:
| # | ID | GitHub Username | Public Name |
|----|--------------|------------------|----------------|
| 1 | aicam | aicam | Ali Risheh |
| 2 | chenli | | Chen Li |
| 3 | kunwp1 | | Chris Park |
| 4 | jiadongb | | Jiadong Bai |
| 5 | shengquan | | Shengquan Ni |
| 6 | xiaozhenliu | | Xiaozhen Liu |
| 7 | linxinyuan | aglinxinyuan | Xinyuan Lin |
| 8 | yiconghuang | Yicong-Huang | Yicong Huang |
| 9 | yunyd | | Yunyan Ding |
- 2025-05-12: We have identified 3 mentors:
| # | ID | GitHub Username | Public Name |
|----|------------|------------------|------------------------|
| 1 | cezar | cezarfx | Cezar Cristian Andrei |
| 2 | garyw | bigdata-memory | Gordon King |
| 3 | fanningpj | pjfanning | PJ Fanning |
- 2025-05-12: 10/12 PPMC members (excluding two mentors) have subscribed
to
mailing lists.
- 2025-05-18: We have gathered 52 approvals (in the form of email replies)
from past codebase committers to donate the
[Texera/texera](https://github.com/Texera/texera) codebase to
Apache/Texera.
- 2025-05-25: We are in discussion with Ian Maxon (Apache ID: imaxon), PMC
Chair of Apache AsterixDB and a long-time contributor, about his joining
as
a mentor for Apache Podling-Texera. Ian is currently in the process of
self-nominating to join the Incubator PMC in order to become eligible to
serve as a mentor.
- 2025-06-01: As Texera is a research project conducted at University of
California, Irvine (UCI), the university owns the copyright of the
codebase/software. We are talking to the UCI licensing office about
releasing their copyright to the committers of the codebase, with Chen Li
as the representative. After the UCI licensing office releases the
copyright, we will prepare the SGA form.
- 2025-06-01: As of today, we are actively designing a new logo for
Texera.
### How has the project developed since the last report?
- We released Texera
[v1.0.0](https://github.com/Texera/texera/releases/tag/1.0.0) on April 04,
2025.
- Many codebase clean ups to prepare codebase for the donation to Apache.
- Created a `NOTICE` file to comply with ASF requirements
[#3388](https://github.com/Texera/texera/pull/3388)
- Added ASF license headers to JOOQ-generated files
[#3414](https://github.com/Texera/texera/pull/3414)
- Added ASF license headers to source files and enabled Release Audit
Tool (RAT)) in CI [#3415](https://github.com/Texera/texera/pull/3415)
- New major features:
- Added new visualization operators: Bullet Chart
[#3362](https://github.com/Texera/texera/pull/3362), RangeSlider
[#3374](https://github.com/Texera/texera/pull/3374), Nested Table
[#3397](https://github.com/Texera/texera/pull/3397), and Volcano Plot
[#3418](https://github.com/Texera/texera/pull/3418)
- Improved file handling with MultipartUpload implementation for file
uploads [#3396](https://github.com/Texera/texera/pull/3396) and pre-checks
for file size/type before preview
[#3427](https://github.com/Texera/texera/pull/3427)
- Enhanced result exportation with support for the HTML format and
large Apache Arrow files
[#3429](https://github.com/Texera/texera/pull/3429)
- Added size metadata to a workflow JSON for better visibility
[#3256](https://github.com/Texera/texera/pull/3256)
- Enabled email notifications to users and administrators for inactive
or unauthorized login attempts
[#3391](https://github.com/Texera/texera/pull/3391),
[#3393](https://github.com/Texera/texera/pull/3393)
- Added admin account configuration and restricted local sign-ups
[#3387](https://github.com/Texera/texera/pull/3387)
- Added support for new R libraries and fixed job ordering in the Helm
chart [#3386](https://github.com/Texera/texera/pull/3386)
- Enabled adjustable shared memory settings for the computing unit
[#3451](https://github.com/Texera/texera/pull/3451)
- UI improvements
- Improved the layout and interface, including the change to the
"terminate button icon"
[#3424](https://github.com/Texera/texera/pull/3424)
and dynamic height adjustment of the operator property sidebar
[#3437](https://github.com/Texera/texera/pull/3437)
- Enhanced interactivity with auto-expansion of the result panel on an
operator click [#3435](https://github.com/Texera/texera/pull/3435) and
improved the comment box usability
[#3436](https://github.com/Texera/texera/pull/3436)
- Added individual progress indicators for concurrent file uploads
[#3426](https://github.com/Texera/texera/pull/3426)
- General UI consistency and refinements
[#3359](https://github.com/Texera/texera/pull/3359),
[#3372](https://github.com/Texera/texera/pull/3372)
- Refactoring
- Reimplemented the User Quota Service to remove the MongoDB dependency
[#3402](https://github.com/Texera/texera/pull/3402)
- Replaced cache source operators with input port materialization
reader threads [#3425](https://github.com/Texera/texera/pull/3425)
- Bug fixes
- Fixed the Helm chart metric resolution, cluster export issues, and
Envoy HTTP timeout/configuration problems
[#3376](https://github.com/Texera/texera/pull/3376),
[#3378](https://github.com/Texera/texera/pull/3378),
[#3380](https://github.com/Texera/texera/pull/3380),
[#3382](https://github.com/Texera/texera/pull/3382)
- Updated the base image in Dockerfile for compatibility
[#3413](https://github.com/Texera/texera/pull/3413)
- Fixed the UI layout and state issues, including centering operators,
incorrect workflow reloading, and auto-persistence logic
[#3342](https://github.com/Texera/texera/pull/3342),
[#3344](https://github.com/Texera/texera/pull/3344),
[#3412](https://github.com/Texera/texera/pull/3412)
- Resolved errors in dataset display for unauthenticated users and
improved handling of compressed files in File Scan operator
[#3373](https://github.com/Texera/texera/pull/3373),
[#3385](https://github.com/Texera/texera/pull/3385)
- Fixed multiple ChannelMarker issues across Java and Python layers,
including transmission, partitioning, and worker routing
[#3434](https://github.com/Texera/texera/pull/3434),
[#3439](https://github.com/Texera/texera/pull/3439),
[#3445](https://github.com/Texera/texera/pull/3445),
[#3448](https://github.com/Texera/texera/pull/3448)
- Corrected backend query versioning and execution order, and fixed
Python Lambda operator compilation
[#3410](https://github.com/Texera/texera/pull/3410),
[#3438](https://github.com/Texera/texera/pull/3438)
### 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
### When were the last committers or PPMC members elected?
On 2025-05-12, the last Texera PPMC members (yunyad, aicam) were added.
### Have your mentors been helpful and responsive?
Yes, our mentors have been both helpful and highly responsive. We are
grateful for their continued support throughout the incubation process. In
particular, we would like to extend a special thanks to PJ Fanning for his
outstanding guidance and engagement.
### Is the PPMC managing the podling's brand / trademarks?
Texera PPMC is working with third parties who are willing to use Texera
brand/trademarks, according to
https://incubator.apache.org/guides/publicity.html and
https://incubator.apache.org/guides/branding.html. Texera PPMC is also
working on a new design of the Texera logo/trademark.
Name is approved:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-233
### Signed-off-by:
- [ ] (texera) Cezar Andrei
Comments:
- [ ] (texera) Gordon King
Comments:
- [X] (texera) PJ Fanning
Comments: I will ask the Texera team to provide a shorter report in
future. The SGA is not yet signed so we have not yet transferred the
code.
### 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.
For the last few months we have been discussing graduation, and getting our
various ducks in rows. We believe we are ready to graduate, but have only
four people who have elected to stay on as PMC members, which seems to us
too small a number. So right now we are discussing what the next steps are
-- go ahead and graduate, or attempt to grow that number a little.
### Three most important unfinished issues to address before graduating:
A. Grow the community a little more.
-- or --
B. Decide that a small dedicated community is better than languishing in
obscurity forever.
### 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?
While discussing graduation, we had a number of people indicate that they
are no longer engaged enough to move to that final step.
### How has the project developed since the last report?
We have continued to slowly work on content. And one of our number got a
talk accepted at Community Over Code 2025 to present about the project, so
hopefully several of us will be there for that.
### How would you assess the podling's maturity?
We believe that we're ready to move out of our parents' basement and into
the real world. Any day now.
- [ x ] Nearing graduation
### Date of last release:
2024-09-30
### When were the last committers or PPMC members elected?
rbowen was added to the PPMC in September 2024.
### Have your mentors been helpful and responsive?
The mentors are awesome.
### Is the PPMC managing the podling's brand / trademarks?
Our brand/trademarks are fine, and we have done a name check.
### Signed-off-by:
- [ ] (training) Craig Russell
Comments:
- [ ] (training) Christofer Dutz
Comments:
- [X] (training) Justin Mclean
Comments:
- [ ] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
JM: I agree the mentors are awesome. :-)
--------------------
## Wayang
Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.
Wayang has been incubating since 2020-12-16.
### Three most important unfinished issues to address before graduating:
1. Working on one more release before graduation.
### 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 more PPMC member, 7 new contributors, 1 new slack member since the last
report.
### How has the project developed since the last report?
Progress on multiple fronts:
- Upgraded to Java 17
- Extended functionality for Wayang's ML capabilities
- Extended functionality for Wayang's FL capabilities
- Extended functionality for Wayang's Scala API
- Extended functionality for Wayang's SQL API
- Several new operators
### 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:
2025-02-07
### When were the last committers or PPMC members elected?
2025-02-05
### Have your mentors been helpful and responsive?
Yes, they have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (wayang) Christofer Dutz
Comments:
- [ ] (wayang) Lars George
Comments:
- [ ] (wayang) Bernd Fondermann
Comments:
- [X] (wayang) Jean-Baptiste Onofré
Comments: We will review the maturity model in preparation for
graduation proposal
### IPMC/Shepherd notes:
# Incubator PMC report for May 2025
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 36 podlings incubating. In April, podlings executed
four distinct releases, and no IP clearances occurred. Several incubating
proposals have been discussed on the mailing list, and we have three
podlings called BifroMQ, Hamilton and PouchDB. The discussion around
SAFplus found some licensing and activity issues, and it's unlikely to be
accepted as an incubating project. Two people were added to the IPMC.
No podlings have retired, but a couple are talking about it. A few podlings
failed to report and will be asked to report next month.
Conversations on the list have been chiefly about releases and new
incubating projects. The discussion to perform name searches early at the
start of the incubator process continued. This originally came up as a
podling Fury needing to change its name close to graduation.
Several projects have been incubating for a long time. Toree looks to be
starting that process. Annotator has not replied and has failed to report
again this month. Livy is discussing what to do slowly. NLPCraft also
failed to report this month, and a roll call sent two weeks ago has
received no response.
There was also a discussion on selecting which reporting group a podling
goes in.
## Community
### New IPMC members:
- Jingsong Lee
- Keyong Zhou
### People who left the IPMC:
- None
## New Podlings
- Hamilton
- BifroMQ
- PouchDB
## Podlings that failed to report, expected next month
- Annotator
- NLPCraft
- PonyMail
- Teaclave
- Training
- Texera
## Graduations
- None
The board has motions for the following:
- Gravitino
- StormCrawler
## Releases
The following releases entered distribution during the month of
May:
- Amoro 0.8.0
- Fury 0.10.1
- Iggy 0.4.300
- Hertzbeat 1.7.0
## IP Clearance
- None
## Legal / Trademarks
See discussion on approving podlings' names.
## Infrastructure
N/A
## Table of Contents
[Amoro](#amoro)
[Cloudberry](#cloudberry)
[DevLake](#devlake)
[Fury](#fury)
[HugeGraph](#hugegraph)
[GraphAr](#graphar)
[HoraeDB](#horaedb)
[Iggy](#iggy)
[ResilientDB](#resilientdb)
[Otava](#otava)
[PouchDB](#pouchdb)
[Seata](#seata)
[Toree](#toree)
[XTable](#xtable)
--------------------
## Amoro
Amoro is a Lakehouse management system built on open data lake formats like
Apache Iceberg and Apache Paimon.
Amoro has been incubating since 2024-03-11.
### Three most important unfinished issues to address before graduating:
1. Polish our website and document.
2. Release more versions under ASF.
3. Build and grow community
### Are there any issues that the IPMC or ASF Board need to be aware of?
Currently no.
### How has the community developed since the last report?
- Added 1 new PPMC member
- Added 11 new contributors
- Hosted an online Amoro meetup, inviting 5 Amoro users to share their best
practices in using Amoro in 2024-12-21.
### How has the project developed since the last report?
- Released Amoro 0.7.1-incubatiing
- Amoro 0.8.0-incubating is currently undergoing a release vote in the
incubator.
- Merged 200 PRs
### 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:
2024-11-20
### When were the last committers or PPMC members elected?
2024-12-02, PPMC member:Congxian Qiu(GitHub ID: Klion26)
### Have your mentors been helpful and responsive?
Yes, Amoro's mentors actively participate in the project, contribute
insights, and help advance the project towards graduation.
### Is the PPMC managing the podling's brand / trademarks?
Yes, everything is fine.
### Signed-off-by:
- [X] (amoro) Justin Mclean
Comments:
- [ ] (amoro) Zhongyi Tan
Comments:
- [ ] (amoro) Yu Li
Comments:
- [X] (amoro) Xinyu Zhou
Comments:
- [ ] (amoro) Kent Yao
Comments:
### 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. Complete the source code cleanup to ensure ASF compliance.
2. Publish the first Apache release following ASF release processes.
3. 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?
No.
### How has the community developed since the last report?
- Mailing list Activity: 59 messages and 92 messages on the Dev mailing
list in March and April 2025, covering technical and Apache-related
discussions.
- Slack Activity: 16 new threads in `general` channel, 27 new members since
last report.
- GitHub Discussions: 4 new threads in March and 7 new threads in April.
- New Committer: welcomed our first committer since joining the incubator.
- Mar 19, 2025 - Xiong Tong
- Events:
- Join OSPP 2025 to attract university students to join the open-source
development
- A Cloudberry Meetup hosted by HashData in Hangzhou attracted 30~
attendees.
- The contributor @Leonid Borchuk and PPMC Member @Kirill Reshke
presented their talks on Cloudberry at the sql-ninja conference in Moscow
on 03/22, 2025.
- PPMC member Shine Zhang presented "From Greenplum to Apache Cloudberry"
at Postgres Conference 2025, Orlando / United States, March 20, 2025
- 6+ Cloudberry proposals are submitted to CommunityOverCode NA/Asia 2025
(still in review and waiting for the final approval).
- Create website pages to guide on how to invite the new committer.
### How has the project developed since the last report?
- Create the Wiki space in GitHub to organize the collective knowledge from
community practices, including the release process.
- Security:
- Integrated two code analysis tools to enhance our code quality and
identify potential issues in the development process: Coverity Scan and
SonarQube Scan.
- Fix the PostgreSQL security issue CVE-2025-1094.
- CICD:
- Working on adding the Ubuntu build and test environment support to
Cloudberry
- Codebase Updates:
- Evolve the Cloudberry code following the Roadmap: Contributed back the
row-column hybrid storage engine -PAX to the Cloudberry codebase;
- Completed the first stage of cherry-picking commits from the
open-source Greenplum project to Cloudberry (80%+ progress of plan).
- Work for the first Apache Cloudberry (Incubating) 2.0.0 release
- Pull Request management through the GitHub project:
https://github.com/orgs/apache/projects/490
- License-related updates:
- Update the NOTICE and LICENSE files.
- List the third-party licenses under the `licenses` directory.
- Replace the Pylint with a license-compatible one - ruff.
- Update the license headers with the Apache license header for the
newly created files.
- Add RAT license audit config and compliance metadata.
- Brand updates: rebrand old names to the latest Apache Cloudberry brand
both in the main codebase and the site source.
- Cleanup the old unused files from the source code for a clearer
codebase and ASF compliance (including concourse/*, hd-ci/*, deploy/*, and
so on).
### 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?
- Mar 19, 2025 - Xiong Tong (committer)
### Have your mentors been helpful and responsive?
Yes, we can get quick responses on the license-related issues, and glad to
see the mentors' guidance to the PPMC on the new committer's workflow.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (cloudberry) Roman Shaposhnik
Comments:
- [X] (cloudberry) Willem Ning Jiang
Comments:
- [ ] (cloudberry) Kent Yao
Comments:
### 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. Grow the project, support more data sources and use cases, and improve
the user experience.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We are currently working toward the graduation of DevLake, but we’re
concerned that the recent drop in contribution metrics (e.g., number of
commits) might not meet the graduation criteria.
At this stage, DevLake is in a stable phase. Over the past few months, our
focus has shifted primarily to bug fixes and maintenance, rather than the
development of new features—hence the decline in contribution statistics.
That said, our community remains active. You'll find ongoing engagement in
our Slack workspace, especially in the #questions channel, where committers
and PPMC members continue to support users.
We’d really appreciate your guidance on what we should prioritize or pay
special attention to during this maintenance-focused phase to ensure we
remain on track for graduation.
### How has the community developed since the last report?
1. 13 new contributors have joined the community (194 contributors in
total)
2. 103 new community members in Slack (1561 in total)
### How has the project developed since the last report?
1. Introduce a new QA domain to DevLake, allowing users to integrate with
the test data.
2. Bug fixes and UX refinement.
3. Initiate the releasing process for a new ASF version 'v1.0.2-rc1'.
### 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:
2024-09-23. There is one in progress.
### When were the last committers or PPMC members elected?
2024-12-7
### 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?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (devlake) Felix Cheung
Comments:
- [ ] (devlake) Liang Zhang
Comments:
- [ ] (devlake) Lidong Dai
Comments:
- [ ] (devlake) Sijie Guo
Comments:
- [X] (devlake) Jean-Baptiste Onofré
Comments: Thanks for sharing your concern about graduation and
activity. If it's a "temporary" reduce of activity, it's not a problem, and
not a blocker for graduation. If this lower activity is related to change
in the community, that's a good point to share. I would say that the
maturity matrix is also welcome to evaluate graduation.
- [X] (devlake) Willem Ning Jiang
Comments:
### IPMC/Shepherd notes:
Justin Mclean: As JB states, it is not a graduation concern, but I suggest
you look at graduating sooner rather than later.
--------------------
## Fury
A blazing fast multi-language serialization framework powered by jit and
zero-copy
Fury has been incubating since 2023-12-15.
### Three most important unfinished issues to address before graduating:
1. Grow the community(attracting more committers, contributors, and
users).
2. Add more PPMC members and release managers
### 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?
Steady progress. Made 3 releases, and added two new release managers.
### How has the project developed since the last report?
3 releases. The most recent was v0.10.2 on May 6, 2025.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-05-06
### When were the last committers or PPMC members elected?
2025-04-06, added new committer LofiSu
### Have your mentors been helpful and responsive?
Yes, the mentors helped a lot for version releases and community governance.
### Is the PPMC managing the podling's brand / trademarks?
Apache Fury will renamed to Apache Fory. The VP has approved the new name.
### Signed-off-by:
- [X] (fury) tison
Comments:
- [X] (fury) PJ Fanning
Comments: Project name is due to change to Fory over the next few
months.
- [ ] (fury) Yu Li
Comments:
- [X] (fury) Xin Wang
Comments:
- [ ] (fury) Enrico Olivelli
Comments:
- [ ] (fury) Hao Ding
Comments:
### IPMC/Shepherd notes:
--------------------
## HugeGraph
A large-scale and easy-to-use graph database/computing/AI system
HugeGraph has been incubating since 2022-01-23.
### Three most important unfinished issues to address before graduating:
1. Release new graph dashboard & make graph computer easy to use
2. Release a stable Graph LLM/AI system
3. At least 2 new PPMC & 5 committers selected and take deep part in the
community
### Are there any issues that the IPMC or ASF Board need to be aware of?
Some PPMC members are inactive for a while, an adjustment may be required
before graduation
### How has the community developed since the last report?
1. Release 1.5.0(include the new distributed design) , the most important
version before graduating
2. Submit a task in GSoC & 4+ tasks in OSPP (Open Source Activity)
3. 12+ new contributors take part in the community (with PR/code)
4. Elected first new PPMC + 1 committer
### How has the project developed since the last report?
1. Move forward to 1.7.0 (Maybe the last version before graduating)
2. Enhance GraphAI system/repo to follow the user needs
3. Release the most important/major change (distributed storage system PD
& Store) & keep improving it
4. The new graph dashboard/UI & graph computing system are also on the
way (should be done in next release)
### 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:
2024-12-10
### When were the last committers or PPMC members elected?
2025-04-21
### Have your mentors been helpful and responsive?
Yes, thanks all of them
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (hugegraph) Lidong Dai
Comments:
- [ ] (hugegraph) Trista Pan
Comments:
- [ ] (hugegraph) Xiangdong Huang
Comments:
- [ ] (hugegraph) Yu Li
Comments:
- [X] (hugegraph) Willem Ning Jiang
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. Implementing key features requested in GitHub issues and discussions.
### 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 one new committer.
2. Attracted one new contributor.
### How has the project developed since the last report?
1. Merged 9 PRs since the last report.
2. Remove Hadoop dependency and shade protobuf dependency in Java SDK.
### 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:
2024-07-02
### When were the last committers or PPMC members elected?
2025-02-17
### 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:
- [ ] (graphar) Calvin Kirs
Comments:
- [X] (graphar) tison
Comments:
- [ ] (graphar) Xiaoqiao He
Comments:
- [ ] (graphar) Yu Li
Comments:
### IPMC/Shepherd notes:
--------------------
## Hamilton
Hamilton is a lightweight declarative python DAG framework with an optional
observability solution.
Hamilton has been incubating since 2025-05-01.
### Three most important unfinished issues to address before graduating:
1. Get podling resources set up
2. Expand community
3.
### 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?
### How has the project developed since the last report?
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
N/A
### Have your mentors been helpful and responsive?
N/A
### Is the PPMC managing the podling's brand / trademarks?
N?A
### Signed-off-by:
- [X] (hamilton) PJ Fanning
Comments: Still setting up
- [ ] (hamilton) Ayush Saxena
Comments:
- [ ] (hamilton) Kevin Ratnasekera
Comments:
### 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?
No
### How has the community developed since the last report?
We submit one [OSPP
task](https://summer-ospp.ac.cn/org/prodetail/2544e0062?lang=en&list=pro)
to attract more developers.
### How has the project developed since the last report?
The structure of the new metric engine is finished, other components are in
WIP status.
### 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:
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:
- [ ] (horaedb) Shaofeng Shi
Comments:
- [X] (horaedb) Gang Li
Comments:
- [ ] (horaedb) Von Gosling
Comments:
### IPMC/Shepherd notes:
--------------------
## Iggy
Iggy is a high-performance, ultra-low latency and large-scale persistent
message streaming platform written in Rust.
Iggy has been incubating since 2025-02-04.
### Three most important unfinished issues to address before graduating:
1. Continue expanding the community, release more versions under ASF
2. Migrate all the repos from previous OSS repo
https://github.com/orgs/iggy-rs/repositories to apache/iggy repo (mono repo
with independent CI/CD)
3. Enhance iggy.apache.org with more details, guides, docs, blogs,
benchmarks etc
### How has the community developed since the last report?
1. Discord members count approaching 400, new contributors writing
proposals (discussions), submitting PRs for fixing issues, docs,
enhancements.
2. Github stars approaching 2.5k from 2.4k
3. Creates downloads crosses 124k vs 115k at the time of last report
4. Presented at [Rustmeet 2025](https://www.youtube.com/watch?v=v3bpw7fcjp0)
5. Presented at [Rustikon Conference
2025](https://www.youtube.com/watch?v=GkV306PyvqM)
### How has the project developed since the last report?
1. Apache Iggy (Incubating) [v0.4.300
released](https://lists.apache.org/thread/q3r6l0gcc27k1nj1q8frqwh40o0mhs4h)
2. Enhanced performance and efficiency: zero-copy (de)serialization
[implemented](https://iggy.apache.org/blogs/2025/05/08/zero-copy-deserializa
tion) for the server & updated SDK client
3. Restructuring the repository to support monorepo with multiple SDKs and
other tooling (eg benchmarks)
4. Started migrating the SDKs from old repo (dotnet, java, node, web UI etc)
5. Successful POCs (with quickwit) for steaming messages into external
connectors/sinks
6. Submitted detailed report for trademarks and received the [approval for
the name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236)
"Iggy", "Apache Iggy" from Apache's Brand Management Team (Mark Thomas)
### 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
- [X] Other: Expanding ecosystem
### Date of last release:
2025-04-17
### When were the last committers or PPMC members elected?
February 2025, at the time of onboarding to Apache Incubator Program.
### Have your mentors been helpful and responsive?
Yes, the mentors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
VP, Brand [approved the project
name](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-236)
### Signed-off-by:
- [ ] (iggy) Hao Ding
Comments:
- [X] (iggy) Yonik Seeley
Comments:
- [X] (iggy) Zili Chen
Comments:
- [X] (iggy) Hulk Lin
Comments:
### IPMC/Shepherd notes:
--------------------
## ResilientDB
ResilientDB is a distributed blockchain framework that is open-source,
lightweight, modular, and highly performant.
ResilientDB has been incubating since 2023-10-21.
### Three most important unfinished issues to address before graduating:
1.Grow the community by facilitating more applications being built on
ResDB.
2.Improve and extend documentation to help external users to set up easily.
3.
### 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?
Regular meeting continues every week.
### How has the project developed since the last report?
We are preparing a new
[release](https://dist.apache.org/repos/dist/dev/incubator/resilientdb/1.11.
0-rc0/) to publish new applicatioins built on top of ResilientDB core
platform.
### 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:
Apache ResilientDB v1.10.0-incubation (2024-7-11)
### When were the last committers or PPMC members elected?
November of 2023
### Have your mentors been helpful and responsive?
The mentors helped tremendously throughout the project build-up and
transfer.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here.
### Signed-off-by:
- [ ] (resilientdb) Junping Du
Comments:
- [ ] (resilientdb) Calvin Kirs
Comments:
- [ ] (resilientdb) Kevin Ratnasekera
Comments:
- [ ] (resilientdb) Roman Shaposhnik
Comments:
- [ ] (resilientdb) Christian Grobmeier
Comments:
### IPMC/Shepherd notes:
--------------------
## Otava
Apache Otava (incubating) performs statistical analysis of performance test
results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It
finds change-points and notifies about possible performance regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the environment.
Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter.
The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Publish the first release under the new name.
(https://github.com/apache/otava/issues/51) The first release was under
voting as the deadline to submit this report to the Incubator PMC passed.
2. Publish the existence of Apache Otava (Incubating), and our first
release.
3. Nurture a growing community that includes also new
members/contributors that have not used Otava (Hunter) before we joined
Apache Incubator
4. Make more releases. In particular, the first release intentionally is
not that different from what already existed before we became an Incubator
project. It is merely a change of project name and ownership (ASF) and the
license, and a re-union of many forks into a clear upstream project. For
future releases we hope to modernize python version, build tooling, and of
course add new features and integrations.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing is blocking us now.
### How has the community developed since the last report?
We recently accepted the first (documentation) contribution from a user who
does not belong to the pre-ASF group of Otava users and contributors. A
handful of more people submitted issues or sent an email to the mailing
list. This level of attention is already more than we are used to receiving
during the previous 8 years developing this code base.
The interactions we had, were mostly held back by the fact we have not yet
made our first release, and that until then, Otava only supported python
3.8, which is no longer officially supported. We expect interest in the
project to increase after the first release (as ASF incubating project) and
upgrading python version. (The release will include support for python 3.9
and 3.10 and will likely happen within hours after the deadline to submit
this report.
### How has the project developed since the last report?
The last time we submitted a report was in February 2025.
We apologize for twice failing to submit a report. There seems to still be
teething issues with basic project governance tasks and responsibilities.
We know we can do better, there's just a lot to absorb when becoming a
proper ASF project for the first time.
Shortly after our previous report, a new name "Otava" was approved for the
project. Otava is the Finnish name for the "Big Bear" constellation, one of
the largest and brightest star constellations in the Northern night sky.
Otava historically had an important function in navigating, as it was
commonly used to find the North Star, which is at the other end of a
straight line drawn from the right most 2 stars in Otava.
Most work in the project since then was to
* Change the project name across ASF infrastructure
* Change the project name everywhere in code and documentation. This
includes file names, executable names and tar file name.
* Publish a project website at otava.apache.org
* As this report was submitted, our first release was undergoing voting on
the incubator general mailing list.
### How would you assess the podling's maturity?
A self review based on
https://community.apache.org/apache-way/apache-project-maturity-model.html
* Code 3/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
### Date of last release:
The first release was happening as this report was submitted
### When were the last committers or PPMC members elected?
So far, the initial committers and PPMC members were those listed in the
initial proposal.
Some of those, haven't actually showed up in the incubator project now that
we are active.
### Have your mentors been helpful and responsive?
Yes!
Submitting this report is a routine we need to get more accustomed to doing.
### Is the PPMC managing the podling's brand / trademarks?
Not an issue yet, as the name is new.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [ ] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
--------------------
## PouchDB
PouchDB is an open-source JavaScript database inspired by [Apache CouchDB]
(http://couchdb.apache.org/) that is designed to build offline-capable web
applications.
PouchDB has been incubating since 2025-04-15.
### Three most important unfinished issues to address before graduating:
1. Get the project up and running (no blockers)
2. Follow the graduation progression, in particular make a new release
under the ASF Incubator.
3. Grow 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?
N/A, still in setup phase.
### How has the project developed since the last report?
N/A, still in setup phase.
### 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:
N/A, still in setup phase.
### When were the last committers or PPMC members elected?
N/A, still in setup phase.
### Have your mentors been helpful and responsive?
N/A, still in setup phase.
### Is the PPMC managing the podling's brand / trademarks?
N/A, still in setup phase.
### Signed-off-by:
- [ ] (pouchdb) Jan Lehnardt
Comments:
- [X] (pouchdb) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## 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. More international contributors are joining the community.
2. Put more time into double-checking the compliance checklist to catch
any gaps.
### 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. 22 new code contributors have joined the community (572 contributors
in total)
2. 4 new committers were elected, and 1 PPMC members were elected.
3. The community actively participates in various open-source events.
We've submitted 3 project proposals for GSoC, 3 projects for OSPP (an
open-source event similar to GSoC), and 3 topics for CommunityOverCode Asia
2025, all guided by different mentors.
4. On the Seata GitHub page, there are around 3,500 "used by" listings.
### How has the project developed since the last report?
1. Since the last report, we've merged 136 PRs, which include over 10 new
features.
2. Since the last report, versions 2.3.0 have been released. We're
currently voting on 2.4.0.
3. Since the last report, we have received and addressed several
vulnerability reports and published CVE-2024-47552 and
CVE-2024-54016.Additionally, we resolved 17 dependency vulnerabilities
through project dependency upgrades.
### 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-03-19
### When were the last committers or PPMC members elected?
2025-05-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: The community begins to consider starting pre-graduation
check.
- [X] (seata) Justin Mclean
Comments:
- [X] (seata) Huxing Zhang
Comments: The project looks in good shape towards graduation.
- [X] (seata) Heng Du
Comments:
- [X] (seata) Xin Wang
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 incorporating
Scala 2.13 support
Release activity started
### How has the project developed since the last report?
Few prs around Scala 2.13 and other small enhancements
Updates to remove Google Analytics from website
### 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:
--------------------
## 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. Strengthening community building by actively engaging with users.
2. Increasing adoption by implementing key features planned - XTable REST
service in collaboration with Apache Polaris(Incubating) community,
Deletion Vectors, CatalogSync support for new catalogs etc.
3. Ironing out license issues with bundled jars for new features.
### 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. Slack channel grew to zero to 67 members in last 2 months.
2. Three new first time contributors have merged their first PR's.
3. More users are trying to use XTable in production environments and
community has been helping them succeed.
### How has the project developed since the last report?
1. The RFC for catalog sync was implemented and is planned for inclusion in
the upcoming 0.3.0 release.
2. Three new RFC's - Deletion Vectors support, ACL Policy synchronization
and XTable REST service are actively in progress.
3. There has been active engagement on slack/GH with the community -
addressing issues, answering questions and fixing bugs reported by users
running XTable in production.
### 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:
Nov 8,2024
### When were the last committers or PPMC members elected?
Feb 2024
### Have your mentors been helpful and responsive?
Yes, our mentors have been helpful and responsive overall. However for the
licensing of new bundled jars, there's conflicting interpretations of the
ASF documentation between the dev vote, the general incubator vote. We
would benefit from additional guidance and support specifically on
resolving these licensing issues for bundled jars and "what content" to
write in LICENSE/NOTICE files.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### 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:
-----------------------------------------
Attachment AI: Report from the Apache IoTDB Project [Xiangdong Huang]
## Description:
The mission of Apache IoTDB is the creation and maintenance of software related
to an IoT native database with high performance for data management and analysis
## Project Status:
Current project status: ongoing with high activity.
Issues for the board: no
response for board question on March 19th:
> jim: Was the live stream recorded? If so, is it available someplace?
No, we have not build such a live stream store. If we do so, a lot of things
should be concerned, such as getting the authorization of the speaker.
And, I think it is fine for current situation, as live stream is not like
official documentation.
## Membership Data:
Apache IoTDB was founded 2020-09-16 (5 years ago)
There are currently 75 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Qingxin Feng on 2024-06-29.
- Colin Lee was added as committer on 2025-03-21
- Chen Zhehan was added as committer on 2025-04-22
- Yuheng Li was added as committer on 2025-04-10
- Shu Wenwei was added as committer on 2025-04-14
## Project Activity:
IoTDB v1.x version, is still be maintained, v1.3.4.x are released.
IoTDB v2.x version, is also released, which brings many new features:
- new data access schema (using SQL standard), which is friendly for developers;
- introduce new cluster consensus algorithm, which has high throughput;
- data sync among IoTDB instances improvement;
- AI feature improvement
- ecosystem integration: DBeaver official plugin provided
IOTDB-2.0.3 was released on 2025-05-30.
IOTDB-1.3.4-1 was released on 2025-05-20.
IOTDB-2.0.2-1 was released on 2025-05-20.
IOTDB-1.3.4 was released on 2025-04-17.
IOTDB-2.0.2 was released on 2025-04-17.
## Community Health:
Overall, the community health is good.
The community accepts suggestions and publishes weekly update information,
which makes it easy for more people to follow the community's updates.
-----------------------------------------
Attachment AJ: Report from the Apache Jackrabbit Project [Marcel Reutegger]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class websites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications, and it
is not a reference implementation.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Jackrabbit was founded 2006-03-15 (19 years ago).
There are currently 59 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is 1:1, because all committers automatically
become PMC members.
Community changes, past quarter:
- No new PMC members. Last addition was Nuno Santos on 2023-11-14.
- No new committers. Last addition was Nuno Santos on 2023-11-13.
## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.
The team is further reducing usage of Google's Guava library and
Jackrabbit Oak is now using Java features where possible. The long
term goal is to remove the dependency on Guava.
The Solr integration module has been removed from Jackrabbit Oak,
after deprecating it last year. Instead, the team invested heavily
into integration with Elasticsearch and added AI/ML inference capabilities.
## Community Health:
The project is generally healthy with a continuous stream of traffic
mostly on JIRA issues and GitHub pull requests reflecting activity of
the respective component.
Commit activity is moderate, mirroring the activity on the
JIRA issues and the desire of the individual contributors to bring
features and improvements in for the next Jackrabbit Oak release.
## Releases:
- jackrabbit-oak-1.22.22 was released on 2025-03-27
- jackrabbit-filevault-3.8.4 was released on 2025-03-28
- jackrabbit-oak-1.78.0 was released on 2025-04-08
- jackrabbit-oak-1.80.0 was released on 2025-05-21
## JIRA activity:
- 190 JIRA tickets created in the last 3 months
- 186 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
The mission of the Apache Karaf project is the creation and maintenance of
open-source software related to a generic platform providing higher level
features and services specifically designed for creating OSGi-based servers for
distribution at no charge to the public.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Karaf was founded 2010-06-15 (15 years ago)
There are currently 32 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 Francois Papon on 2018-11-28.
- No new committers. Last addition was Robert Varga on 2023-10-31.
## Project Activity:
Apache Karaf 4.4.8 is in preparation, especially with fixes and dependency
updates, but also providing new BoM for more flexibility for the users.
Apache Karaf 4.5.0 will be a new maintenance branch, with updated versions and
fixes.
We are merging the last changes for Karaf Decanter 2.12.0 release. The vote
will start soon.
## Community Health:
Following the discussion about Karaf future
(https://lists.apache.org/thread/2v68pkdn089285sodolxgt6z4pgbnpx9),
we agreed (with the community) about:
- Maintenance on the 4.4.x branch (with 4.4.8 release coming as
said earlier)
- Introduce 4.5.x branch with Pax * and other significant updates
(like the optional flat resolver, new distributions)
- Move main to 5.0.0 with new Karaf services, etc
-----------------------------------------
Attachment AL: Report from the Apache Kibble Project [Sharan Foga]
-----------------------------------------
Attachment AM: Report from the Apache Kvrocks Project [Mingyang Liu]
## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, supporting Redis-like data
structures.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kvrocks was founded 2023-06-21 (2 years ago)
There are currently 27 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Aleks Lozoviuk was added to the PMC on 2025-05-06
- Edward Xu was added as committer on 2025-04-29
## Project Activity:
In the past quarter, two versions of Apache Kvrocks (2.12.0, 2.12.1) have been
released. The PMC voted for a new committer and a new PMC member (previously a
committer of Kvrocks).
The t-digest data structure in Kvrocks is currently in developing and expected
to be released in the next version (probably 2.13.0). And we are participating
OSPP for seeking students to join the development of the timeseries module of
Kvrocks.
Also, we are participating GSoC and a student is joining us in developing the
new Web UI of Apache Kvrocks Controller. And it is expected to be released in
the next version of the controller.
## Community Health:
Overall community health is good. We have about 105 new PRs (11% increase)
and 39 new issues (69% increase) in this quarter.
And I believe that, with the participation of GSoC and OSPP, more new
contributors and community members will appear and join our journey.
-----------------------------------------
Attachment AN: Report from the Apache Kyuubi Project [Kent Yao]
## Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses
## Project Status:
Current project status: Ongoing w/ moderate activity
Issues for the board: None
## Membership Data:
Apache Kyuubi was founded 2022-12-21 (2 years ago)
There are currently 29 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Binjie Yang on 2024-07-05.
- No new committers. Last addition was He Zhao on 2025-01-02.
## Project Activity:
### Software development activity:
- We released the bug fix release 1.10.2 on May 27, 2025.
- We released the bug fix release 1.9.4 on May 27, 2025.
- We helped the Spark 4.0.0 release, and made the above 2 releases to
support
- We released the kyuubi-shaded package 0.5.0 on May 22, 2025.
### Meetups and Conferences:
- N/A
## Community Health:
- We are making sustainable releases for kyuubi users
- The code develop in main code base became a bit lower than avg
-----------------------------------------
Attachment AO: Report from the Apache Linkis Project [Shuai Di]
## Description:
The mission of Apache Linkis is the creation and maintenance of software
related to a distributed computation middleware to facilitate connection,
governance and orchestration between the upper applications and the
underlying data engines.
## Project Status:
Current project status: Ongoing.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Linkis was founded 2022-12-21 (Two years ago)
There are currently 38 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC. Last addition was Jie Cheng on 2024-01-28.
- No new committers. Last addition was King hao on 2024-12-04.
## Project Activity:
The Apache Linkis version 1.8.0 is under development and is expected
to be released in September 2025. Mainly includes the following features:
- Pre - task diagnosis and support for bad job interception,
as well as post - task diagnosis reports.
- Data source display support for Ranger.
- Support for setting priorities for Linkis tasks.
- Linkis supports Azure object storage.
- Data source management supports both Oracle and PostgreSQL
- Token expiration policy optimization
- Add UDF log query to task details
## Community Health:
Overall community health is good.
- 5 PRs closed on GitHub, past quarter.
- 9 issues closed on GitHub, past quarter.
-----------------------------------------
Attachment AP: Report from the Apache Logo Development Project [Daniel Gruno]
-----------------------------------------
Attachment AQ: Report from the Apache Lucene Project [Dawid Weiss]
## Description:
The mission of Lucene is the creation and maintenance of software related to
Search engine library
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Lucene was founded 2005-01-19 (20 years ago)
There are currently 103 committers and 69 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Michael Froh was added as committer on 2025-03-06
- Stefan Vodita was added to the PMC on 2025-04-22
- Ankit Jain was added as committer on 2025-05-06
## Project Activity:
- 10.2.0 was released on 2025-04-10.
- https://lucene.apache.org/core/10_2_0/changes/Changes.html
- this release includes a bunch of new features and performance improvements;
a good indicator of the project's continued growth.
- 10.2.1 was released on 2025-05-01.
- https://lucene.apache.org/core/10_2_1/changes/Changes.html
- this release includes a bunch of bug fixes following 10.2.0 major release.
- Lucene embraced github's dependabot service to
keep up with security updates and new dependency versions.
## Community Health:
The project is in good shape, with stable activity in all areas
(discussions on the mailing list, github pull requests, commits).
In the period between 2025-03-06 and 2025-06-09, there were 290
commits to the main branch, 107 issues filed (46 resolved), 322
pull requests opened (and 274 closed).
Two new committers have been added to the project (Michael Froh,
Ankit Jain) and one committer has agreed to join the
PMC (Stefan Vodita).
-----------------------------------------
Attachment AR: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AS: Report from the Apache Mynewt Project [Szymon Janc]
-----------------------------------------
Attachment AT: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environments, tooling platforms, and application
frameworks.
## Project Status:
Current project status: Ongoing with moderate to high activity.
Issues for the board: None.
## Membership Data:
Apache NetBeans was founded 2019-04-17 (6 years ago)
There are currently 82 committers and 65 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 Michael Bien on 2022-05-01.
- No new committers. Last addition was Tomas Hurka on 2023-05-24.
## Project Activity:
- Apache NetBeans 26 was released on 2025-05-19.
## Community Health:
- We should focus on getting more committers and PMC members, been a while.
- Stable contributions, e.g., 21 contributors (5 new) for Apache NetBeans 26.
- dev@netbeans.apache.org 10% increase in traffic (222 emails compared to 201)
-----------------------------------------
Attachment AU: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (18 years ago)
There are currently 60 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Sebastian Tschikin on 2024-09-18.
- No new committers. Last addition was Ioan Eugen Stan on 2024-09-23.
## Project Activity:
* Apache OFBiz 18.12.19 was released on 2025-04-01. This is the final release
of the 18.12 series, and following its publication, we announced the end of
life for this series.
* As part of the 18.12.19 release, we fixed and disclosed a new security
vulnerability: CVE-2025-30676.
* Apache OFBiz 24.09.01 was released on 2025-04-07. This is the first release
of the new 24.09 series, which is the successor to the 18.12 series.
* Trademarks: There are no trademark-related concerns at this time.
* An OFBiz meetup, "European OFBiz Days 2025," was held from May 26th to 28th
in Rosières, France. A special thanks for the initiative and organization
goes to the French group of our PMC members and committers. This informal
and friendly gathering brought together participants from France, Italy, and
Romania, who delivered presentations, shared valuable feedback, and
brainstormed on various topics related to Apache OFBiz. We are optimistic
that this initiative will pave the way for a new series of regular events in
Europe, attracting more participants in the future. For those who could not
attend, the talks were streamed live, recorded, and are available for
viewing on YouTube.
## Community Health:
Over the past quarter, community engagement has remained
stable, with ongoing participation in mailing list discussions and
contributions to both code and documentation. No new PMC members or
committers have been added during this period, though some new individuals
have started to contribute.
-----------------------------------------
Attachment AV: Report from the Apache Olingo Project [Michael Bolz]
-----------------------------------------
Attachment AW: Report from the Apache OpenDAL Project [Hao Ding]
## Description:
OpenDAL is an Open Data Access Layer that enables seamless interaction with
diverse storage services. Its development is guided by the vision “One Layer,
All Storage” and the following principles:
- Open Community
- Solid Foundation
- Fast Access
- Object Storage First
- Extensible Architecture
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache OpenDAL was founded 2024-01-17 (a year ago)
There are currently 33 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Wenchuang Gan was added to the PMC on 2025-03-14
- Asuka Minato was added as committer on 2025-04-29
- Erick Guan was added as committer on 2025-04-01
- Miro Kwok was added as committer on 2025-04-17
- Yi Hong was added as committer on 2025-03-24
## Project Activity:
- v0.53.3 was released on 2025-05-26
- v0.53.2 was released on 2025-05-13
- v0.53.1 was released on 2025-04-19
- v0.53.0 was released on 2025-04-05
## Community Health:
### Are there any risks to the sustainability of the project?
OpenDAL remains in excellent health. The core crate has nearly
800 dependents on github and is used in production by multiple
database systems (Databend, GreptimeDB, RisingWave) and tools
(e.g., sccache, Vector). Development velocity is steady,
with 3–5 PRs merged daily.
### Is the PMC capable of responding to security issues and
performing releases if needed?
Yes. The PMC has repeatedly demonstrated the ability to quickly
release fixes and monthly tagged versions. Releases are made in
a timely manner and dependency hygiene is maintained actively.
### Does the PMC need anything from the Foundation to improve on
contributing to our mission of delivering software for the public good?
No requests at this time.
-----------------------------------------
Attachment AX: Report from the Apache OpenNLP Project [Jeff Zemerick]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache OpenNLP was founded 2012-02-14 (13 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Martin Wiesner on 2023-06-24.
- No new committers. Last addition was Atita Arora on 2023-02-28.
## Project Activity:
Version 2.5.4 is the latest release. Work toward a 3.0 release has begun with
the creation of a 2.x branch and changing main branch to be for 3.0. The
general plan for 3.0 is outlined in Jira tickets and work will follow their
path. OpenNLP will be represented at the ONNX Meetup and at Apache CoC NA.
## Community Health:
The community status remains about the same. It is relatively low activity
but healthy.
-----------------------------------------
Attachment AY: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR), JSR-365 (CDI-2.0) and
Jakarta CDI (CDI-4.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We did a maintenance release for CDI-2.0 with a few bugfixes.
Our CDI-4.0 release is well received and working fine.
## PMC changes:
- Currently 13 PMC members, 20 committers
- Last PMC addition was Reinhard Sandtner on 2017-10-09.
- Last committer addition was John D. Ament on 2017-10-09.
## Recent Releases
- 2.0.28 was released on 2025-05-19
- 4.0.3 was released on 2024-12-14
- 4.0.2 was released on 2024-02-14.
-----------------------------------------
Attachment AZ: Report from the Apache Paimon Project [Jingsong Lee]
## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Paimon was founded 2024-03-20 (a year ago)
There are currently 21 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Junhao Ye on 2025-02-25.
- No new committers. Last addition was Weijun Wang on 2024-12-20.
There are three committer candidates to consider nominating them next quarter.
## Project Activity:
Software development activity:
- We released the release 1.1.0 on 2025-04-17.
- We released the release 1.1.1 on 2025-05-16.
- We integrated Iceberg's latest deletion vector to real-time sync.
- We introduced RESTApi to make REST more easy to use.
## Community Health:
- builds mail list had a 49% decrease in traffic in the past quarter (14 vs 27).
- dev mail list had a 60% decrease in traffic in the past quarter (52 vs 129).
Various fixes and improvements are still underway, no many major features.
-----------------------------------------
Attachment BA: Report from the Apache Pekko Project [PJ Fanning]
## Description:
The mission of Apache Pekko is the creation and maintenance of software related
to a toolkit and an ecosystem for building highly concurrent, distributed,
reactive and resilient applications for Java and Scala
## Project Status:
Current project status:
Project remains pretty active with moderate levels of community engagement.
Issues for the board: None
## Membership Data:
Apache Pekko was founded 2024-03-20 (a year ago)
There are currently 28 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was JingZhang Chen on 2024-05-29.
- No new committers. Last addition was Domantas Petrauskas on 2024-12-19.
## Project Activity:
We are still making regular releases with some bug fixes and some
small enhancements.
## Community Health:
The community remains relatively small. Issues and Discussions are
still looked at quite quickly.
-----------------------------------------
Attachment BB: Report from the Apache Pig Project [Koji Noguchi]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It provides
a high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs.
## Project Status:
Current project status: Dormant
Issues for the board:
## Membership Data:
Apache Pig was founded 2010-09-21 (15 years ago) There are currently 31
committers and 17 PMC members in this project. The Committer-to-PMC ratio is
roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Koji Noguchi on 2016-08-04.
- No new committers. Last addition was Nándor Kollár on 2018-09-06.
## Project Activity:
Driving the release. 0.18 branch cut. Close to starting the vote. There have
been a bit more involvement and help from other PMCs in submitting reports and
helping with questions in release steps.
## Community Health:
Overall activity is low as the project is mostly stable. Contributions are
mainly bug fixes and updating dependencies.
-----------------------------------------
Attachment BC: Report from the Apache PLC4X Project [César García]
-----------------------------------------
Attachment BD: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
## Description:
The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The primary goal is to provide
an API to which software developers may code and be assured of predictable if
not identical behaviour regardless of the platform on which their software is
built, relieving them of the need to code special-case conditions to work
around or take advantage of platform-specific deficiencies or features.
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (25 years ago)
There are currently 67 committers and 42 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 Steffen Land on 2023-03-02.
- No new committers. Last addition was Steffen Land on 2023-02-27.
## Project Activity:
apr-1.7.6 was released on 2025-05-16.
apr-util-1.6.4 is being worked on.
## Community Health:
The apr-1.7.6 release has generated the usual increase of activity on dev@ and
svn@, things have become quieter (as usual still) since then, probably meaning
that 1.7.6 is working as expected.
-----------------------------------------
Attachment BE: Report from the Apache Portals Project [Neil Griffin]
## Description:
The mission of Portals is the creation and maintenance of software related to
Portal technology
## Project Status:
Current project status:
The Pluto sub-project of Apache Portals remains active. Historically, the Git
repo has been home to four specific items:
1) Source code location for the javax.portlet Java API
2) Source documents for the Java Portlet Specification
3) Source code for the Technology Compatibility Kit (TCK)
4) Source code for Pluto Reference Implementation (RI) of the Portlet API/Spec
The most current version of the Portlet Specification is version 3.0.1, as
defined under the Java Community Process under JSR 362:
https://www.jcp.org/en/jsr/detail?id=362
Now, it is my honor to inform the ASF board that the Jakarta EE Specification
Committee has voted to approve and ratify the creation of the Jakarta Portlet
project and the plan for the Jakarta Portlet 4.0 specification:
https://www.eclipse.org/lists/jakarta.ee-spec/msg04130.html
The corresponding Jakarta Portlet project proposal can be found here:
https://projects.eclipse.org/proposals/jakarta-portlet
What does this mean for the Apache Portals project?
It means that items 1, 2, and 3 will have a new home at the
following Git repository for Jakarta Portlet 4.0+:
https://github.com/jakartaee/portlet
Item 4 (the Pluto RI) will REMAIN part of the Apache Portals project. The master
branch will contain an implementation of Jakarta Portlet 4.x, whereas other
branches will continue to house legacy code for Portlet 3.x, 2.x, and 1.x:
https://github.com/apache/portals-pluto
The source code for Apache Pluto has already been migrated to Jakarta EE and
Jakarta Portlet. The code is scheduled to be pushed to the master branch once
items 1, 2, and 3 have been pushed to the Eclipse Git repository.
Issues for the board: None at this time
## Membership Data:
Apache Portals was founded 2004-02-17 (21 years ago)
There are currently 40 committers and 17 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 Neil Griffin on 2017-02-11.
- No new committers. Last addition was Ahmed on 2016-08-06.
## Project Activity:
The project has no recent activity, but will have a flurry of activity in the
coming weeks/months as the Jakarta Portlet project moves forward.
## Community Health:
There is no recent activity on the dev lists, and no recent community
contributions since project is in a maintenance mode. Increase activity will
likely occur once the Jakarta Portlet project moves forward.
-----------------------------------------
Attachment BF: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
## Project Status:
- There are no issues requiring board attention at this time.
## Project Activity:
- 4.0.3 was released on Febraury 27th 2025
- 4.0.4 was released on April 9th 2025
- 4.0.5 was released on May 22nd 2025
- 3.3.5 was released on February 27th 2025
- 3.3.6 was released on April 9th 2025
- 3.3.7 was released on May 22nd 2025
- 3.0.11 was released on April 9th 2025
- 3.0.12 was released on May 22th 2025
- Pulsar C++ releases:
- 3.7.1 on May 7th 2025
- Pulsar Go releases:
- 0.15.0 on April 23rd 2025
- 0.15.1 on May 26th 2025
- Pulsar Python releases:
- 3.7.0 on May 13th 2025
- Pulsar NodeJS releases:
- 1.13.2 on May 29th 2025
- Pulsar reactive client:
- 0.6.0 was released on April 21st 2025
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-411: Expose Peek Messages API to Non-Admin Clients
PIP-413: Expose Index Through Message ID to Clients
PIP-414: Enforce topic consistency check
PIP-416: Add a new topic method to implement trigger offload by size
threshold
PIP-417: Enable SpotBugs FindPublicAttributes Check
PIP-418: Determine the behaviors for components that rely on BookKeeper when
BookKeeper is not used
PIP-419: Support consumer message filter on broker-side for specific
subscription
PIP-420: Provide ability for Pulsar clients to integrate with third-party
schema registry service
PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK
PIP-422: Support global topic-level policy: replicated clusters and new API
to delete topic-level policies
PIP-423: Add a new admin API to acknowledge a single message
PIP-424: Support Getting Message ID by Index in ManagedLedger Interface
PIP-425: Support connecting with next available endpoint for multi-endpoint
serviceUrls
PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking
for Exclusive and Failover Subscriptions
- Pulsar has reached 687 contributors on the main Github repo
(It was 683 contributors in March 2025)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (7 years ago)
There are currently 84 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Chris Bono was added to the PMC on 2025-06-03
- Xiangying Meng was added to the PMC on 2025-06-03
- Zixuan Liu was added to the PMC on 2025-05-01
- No new committer added this quarter
## Community Health:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper, more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 0% increase in traffic in the past quarter (23 emails compared to 23)
- dev@pulsar.apache.org:
- 19% decrease in traffic in the past quarter (356 emails compared to 437)
## Slack activity:
- 10679 Members (10605 in March 2025)
- 275 Active montly users (219 in December 2024)
## GitHub activity:
- 658 commits in the past quarter (-17% decrease)
- 67 code contributors in the past quarter (-15% change)
- 244 PRs opened on GitHub, past quarter (-32% change)
- 221 PRs closed on GitHub, past quarter (-40% change)
- 109 issues opened on GitHub, past quarter (-36% change)
- 63 issues closed on GitHub, past quarter (-42% change)
-----------------------------------------
Attachment BG: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
The mission of Apache RocketMQ is the creation and maintenance of software
related to a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache RocketMQ was founded 2017-09-20 (8 years ago)
There are currently 75 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhouxiang Zhan on 2023-09-21.
- No new committers. Last addition was Chaoyang Liu on 2024-08-10.
## Project Activity:
Recent releases:
- ROCKETMQ-CLIENTS-GO-5.1.2 was released on 2025-05-13.
- ROCKETMQ-5.3.3 was released on 2025-05-12.
- ROCKETMQ-SPRING-2.3.3 was released on 2025-03-20.
- ROCKETMQ-5.3.2 was released on 2025-03-12.
## Community Health:
The Apache RocketMQ community showed notable growth in mailing list activity,
with significant increases in both developer and user engagement.
Code contributions remained steady, while the number of contributors slightly
declined.
GitHub activity saw healthy growth, with more PRs and issues being opened and
closed compared to the previous quarter.
Overall, the community remains active and engaged.
-----------------------------------------
Attachment BH: Report from the Apache Royale Project [Yishay Weiss]
## Description:
The mission of Apache Royale is the creation and maintenance of software
related to improving developer productivity in creating applications for
wherever JavaScript runs (and other runtimes)
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Royale was founded 2017-09-20 (8 years ago) There are currently 20
committers and 17 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Alina Kazi on 2024-11-03.
- No new committers. Last addition was María José Esteve on 2021-11-23.
- Carlos Rovira has been removed from PMC list and has been moved to Emeritus
status
## Project Activity:
Improvements were made to API documentation application. Also, a new and
simpler way of integrating JS and CSS files was introduced to the compiler.
## Community Health:
There are no notable changes in the community health. One PMC member has asked
to change his status to Emeritus, but as he himself noted, he had stopped in
fact being involved in the project several years prior.
-----------------------------------------
Attachment BI: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment BJ: Report from the Apache SeaTunnel Project [Jun Gao]
-----------------------------------------
Attachment BK: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
## Description:
The mission of Apache ServiceMix project is to create and maintain a flexible,
open-source integration container, powered by OSGi, that unifies the features
and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful
runtime platform you can use to build your own integrations solutions.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (18 years ago)
There are currently 50 committers and 21 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 Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.
## Project Activity:
Following ask from the community, we released ServiceMix Bundles 2025.05.
## Community Health:
The project is now almost dormant:
- we do ServiceMix Bundles release on community demand (as it's still
heavily used)
- dependency projects (karaf, camel-karaf, ...) started to use wrap
protocol instead of ServiceMix Bundles (still ongoing)
- The Karaf integration distribution will cover most of the ServiceMix use cases
A roll call will be certainly performed soon to discuss the next step
for the project.
-----------------------------------------
Attachment BL: Report from the Apache Shiro Project [Brian Demers]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: None at this time
## Membership Data:
Apache Shiro was founded 2010-09-21 (15 years ago)
There are currently 14 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Lenny Primak on 2022-11-02.
## Project Activity:
The Shiro team is in the planning stages for 3.0 which aims to cut
some tech debt and help move the project forward (and by dropping
deprecated functionality). New functionality and fixes are still
accepted in 2.x, 1.x is security fix only.
Last release was:
- 2.0.4: 2025-04-16
## Community Health:
Mailing list traffic is low.
(Actual statistical changes are less useful when the traffic volume is low)
-----------------------------------------
Attachment BM: Report from the Apache SINGA Project [Wang Wei]
## Description:
The mission of Apache SINGA is the creation and maintenance of software related
to a distributed deep learning platform
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SINGA was founded 2019-10-16 (5 years ago)
There are currently 23 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.
## Project Activity:
The team has released SINGA 5.0.0 on 14 April 2025.
The release note is at
https://github.com/apache/singa/blob/master/RELEASE_NOTES
The main features of this release include
1. Add the implementations of the healthcare model zoo.
2. Optimize the distributed training by updating the MSOptimizer and
MSSGD.
3. Improve the efficiency of the transformer example.
4. Add the sparsification version of the model for the model selection
example.
5. Update data processing for the benchmark dataset.
Apart from this release, the community has been working on:
1. Adding more datasets and model implementations for the healthcare model
zoo.
2. Improving data processing for the benchmark dataset.
3. Continuing optimizing the distributed training.
## Community Health:
According to the statistics, there are increase of email traffic,
commits and github issue activities, which shows
that the community is active in the development.
-----------------------------------------
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. The commits are less
numerous than in previous reports, but tend to contain larger amount of work.
Issues for the board: none.
## 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:
The last Apache SIS release was almost 2 years ago. The reasons why it is
taking so long to create a new release were mentioned in the previous reports.
The reasons were 1) participation in a Testbed of the Open Geospatial
Consortium (OGC) in which Apache SIS has been used (together with other
software) for prototyping, and 2) upgrade to the latest ISO 19111
international standard (Referencing by coordinates), which is core to Apache
SIS mission. Because the latter work is already in progress, releasing SIS
before the completion of this work would be a half-backed release.
It not the first time that an Apache SIS release takes so long. There is often
1~2 years between releases, and previous attempts to reduce that delay have
not been successful. The typical pattern is: an upgrade to the latest version
of some important OGC/ISO standard started, is stopped in the middle of the
work because of other task considered urgent, resumes months later, is stopped
again because of another urgent task, etc., and the wish to not release a
half-backed SIS causes the release to be delayed until the completion of the
standard upgrade. However, we have not received complain yet, maybe because
compliance to OGC/ISO standards is a primary reason why the users that we know
choose SIS over alternatives.
## Community Health:
The mailing lists are quite silent despite the activity in commits.
Creations of JIRA issues are notified on the developer mailing list but rarely
bring a discussion before resolution. Emails sent directly to the mailing list
for explaining the ongoing work something cause a small discussion, but we have
not done that as much as we should. More often, users or potential users asked
for a communication on Slack or used private emails.
The Apache Sedona project recently upgraded from Java 8 to Java 11. This
upgrade resolved one of the blocking points that prevented them from replacing
their GeoTools dependency (under LGPL license) by Apache SIS. There is plan to
move forward with them, but we don't know yet through which communication
channels, as it depends in part how they wish to work.
-----------------------------------------
Attachment BO: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Sling was founded 2009-06-17 (16 years ago)
There are currently 52 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Julian Reschke on 2024-10-22.
- Sagar Miglani was added as committer on 2025-03-24
## Project Activity:
We released version 13 of our sample application, the Sling Starter, on
January 17th, 2025. Work is ongoing towards Sling Starter 14. While invididual
modules can keeping targeting Java 11, we will only support Java 17 or newer
for the Sling Starter 14 distribution.
The initial work for supporting to the Jakarta Servlet specification is complete
and we plan start the release process for the affected modules in the next
weeks.
The migration to slf4j 2.0 was also completed, following a long community
effort.
In the meantime individual modules are being developed and released,
with 29 releases for this reporting period.
## Community Health:
Community health is pretty good and contributions from various
individuals continue.
-----------------------------------------
Attachment BP: Report from the Apache SpamAssassin Project [Giovanni Bechis]
## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
## Project Status:
Project state: Ongoing with low to moderate activity Primary focus for
development is now ongoing maintenance bug fixes to the latest release, 4.0.1.
## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (21 years ago) There are currently
32 committers and 13 PMC members in this project. The Committer-to-PMC ratio
is roughly 2.5:1.
Community changes, past quarter:
- PMC members: Giovanni Bechis is new Chair Last addition was Kent Oyer on
2024-11-09.
- No new committers. Last addition was Kent Oyer on 2024-03-29.
## Project Activity:
Last release was Apache SpamAssassin version 4.0.1 on 29 March 2024.
We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility. On 19 May 2025, GitHub Pull requests have been enabled
for the project in order to try to attract more developers.
## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.
-----------------------------------------
Attachment BQ: Report from the Apache Steve Project [Daniel Gruno]
-----------------------------------------
Attachment BR: Report from the Apache Storm Project [Richard Zowalla]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Project Status:
Current project status: Ongoing (reactivated)
Issues for the board: none
## Membership Data:
Apache Storm was founded 2014-09-17 (11 years ago)
There are currently 48 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Purshotam Shah was added to the PMC on 2025-05-21
- No new committers. Last addition was Purshotam Shah on 2024-10-08.
## Project Activity:
Project activity has slowed in recent years, and Storm is currently in
maintenance mode. Nonetheless, we still receive occasional bug reports and
user questions, indicating that Storm continues to see active use which is an
encouraging sign.
During the past quarter, we updated several third-party libraries to their
latest versions. We intend to maintain our release cadence and continue
delivering patches at a steady pace. At the same time, efforts to reduce
Storm’s reliance on external dependencies are ongoing. Managing this technical
debt remains a significant challenge for the project.
As noted in previous reports, the Storm UI still includes outdated and legacy
JavaScript libraries. Unfortunately, none of our current active committers
have the frontend development expertise required to modernize this part of the
codebase and attracting new people in that area is hard.
On a positive note: We are especially pleased to welcome a new PMC member,
Purshotam Shah, who contributed a new feature and accompanying documentation
in the area of mTLS.
Recent releases:
2.8.0 was released on 2025-01-24.
2.7.1 was released on 2024-11-29.
2.7.0 was released on 2024-10-19.
## Community Health:
Community engagement is currently healthy, but could benefit from new
contributors or users.
-----------------------------------------
Attachment BS: Report from the Apache StormCrawler Project [Richard Zowalla]
## Description:
StormCrawler is a collection of resources for building low-latency,
customisable and 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 (15 days 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:
StormCrawler graduated from the Apache Incubator about three weeks ago. The
project is now in the process of removing references to the Incubator and
establishing itself as a top-level project (TLP).
StormCrawler has maintained a stable user base over the past decade and
continues to be well-regarded. Although the number of committers and
contributors remains relatively small, the project's activity level is on par
with other established TLPs.
We recognize that StormCrawler can be challenging for new users to adopt. To
address this, we plan to develop comprehensive documentation aimed at
simplifying onboarding for both users and potential contributors.
Additionally, we are considering the development of a new external module that
leverages generative AI for text extraction —offering an alternative to the
current rule-based and XPath-based approaches. This enhancement would align
our feature set more closely with leading Python-based crawlers, and we hope
it will attract a broader community of users and developers by offering
modern, state-of-the-art capabilities paired with our easy-to-use
documentation initiative.
## Community Health:
While the community remains active and stable, there is room for growth
through the engagement of new contributors.
-----------------------------------------
Attachment BT: Report from the Apache StreamPark Project [Huajie Wang]
-----------------------------------------
Attachment BU: Report from the Apache Synapse Project [Isuru Udana]
-----------------------------------------
Attachment BV: Report from the Apache Tomcat Project []
## Description:
The Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.
The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10
and later implement specifications developed as part of Jakarta EE. Tomcat 9
and earlier implement specifications developed as part of Java EE.
Apache Tomcat software powers numerous large-scale, mission-critical web
applications across a diverse range of industries and organizations. Some of
these users and their stories are listed on the PoweredBy wiki page.
## Project Status:
Current project status: The Tomcat project has a strong and active community,
both of users and committers.
Issues for the board: none
## Membership Data:
Apache Tomcat was founded 2005-05-17 (20 years ago) There are currently 50
committers and 29 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.
Personal note: we are sad to announce the passing of Mladen Turk, Apache
Tomcat PMC Chairman for nearly *18 years*. He was a source of guidance and
mirth to everyone on the project, and will be missed both professionally and
personally.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Soumis on 2024-07-05.
- No new committers members. Last addition was John Engebretson on 2025-02-05.
- A recommendation had been made to the board for a new PMC chairperson.
## Project Activity:
- Apache Tomcat 9.0.106 was released on 2025-06-10.
- Apache Tomcat 11.0.8 was released on 2025-06-09.
- Apache Tomcat 10.1.42 was released on 2025-06-09.
- Apache Tomcat Native 2.0.9 was released on 2025-05-29.
- Apache Tomcat 11.0.7 was released on 2025-05-13.
- Apache Tomcat 9.0.105 was released on 2025-05-12.
- Apache Tomcat 10.1.41 was released on 2025-05-12
- Apache Tomcat 11.0.6 was released on 2025-04-09.
- Apache Tomcat 9.0.104 was released on 2025-04-09.
- Apache Tomcat 10.1.40 was released on 2025-04-08.
## Community Health:
Continued healthy activity across multiple components and responsiveness on
both dev and user lists.
-----------------------------------------
Attachment BW: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Health
Overall contributions are still very low for a project of our scope. Roughly
17 commits in the last two months from 5 committers.
## Activity
As noted in the prior report, major activity in the community was the release
of TomEE 10.0.0 in December and 10.0.1 in March. Activity remains focused
on minor bug fixes and library upgrades to address CVEs.
Some discussion on potentially removing support for MicroProfile in all
but the "MicroProfile" distribution of TomEE due to complexities with the
OpenTelemetry support added in TomEE 10. After discussion it was concluded
that we would instead update the MicroProfile version from 6.0 to 6.1 and
release that as TomEE 10.1.0 to reflect the change.
Most this work was done through library upgrades and some minor fixes.
The proposed final TomEE 10.1.0 binaries are up for a vote now and is
expected to pass.
## PMC changes:
- Currently 13 PMC members.
- Last PMC addition Richard Zowalla on May 23rd, 2022
## Committer base changes:
- Currently 35 committers.
- Last committer added was Markus Jung on September 12th, 2024
- Previous committer added was Thomas Andraschko on March 25th, 2024
## Releases:
- Apache TomEE 10.0.0 on December 20th, 2025
- Apache TomEE 10.0.1 on March 27, 2025
-----------------------------------------
Attachment BX: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
The mission of Traffic Server is the creation and maintenance of software
related to a fast, scalable, and extensible HTTP/1.1 and HTTP/2 compliant
caching proxy server.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Traffic Server was founded 2010-04-20 (15 years ago)
There are currently 70 committers and 58 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Mo Chen on 2024-04-15.
- No new committers. Last addition was Josiah VanderZee on 2024-01-07.
## Project Activity:
In the past quarter, we released 3 bug fix and security updates. The adoption
of ATS 10.x continues to progress, with two major companies expanding their
production deployments following successful testing. Preparations for the next
minor version, ATS 10.1.0, are on track, with a planned release in July 2025.
Development focus remains on performance enhancements and new feature
integration based on community feedback.
## Community Health:
We successfully hosted the ATS Spring Summit 2025 virtually, focusing on
roadmap planning for ATS 10.X and ATS 11.x releases and discussing scalability
improvements. Approximately 21 participants joined, fostering strong
collaboration. We are planning on having a half day summit at the end of
August, for our first Summer Summit.
Weekly bug and issue scrubs continue every Monday, ensuring timely review of
pull requests and resolution of user-reported issues. Community engagement
remains steady, with active participation in discussions and contributions
from both new and existing contributors.
-----------------------------------------
Attachment BY: Report from the Apache TVM Project [Tianqi Chen]
## Description:
The mission of Apache TVM is the creation and maintenance of software related
to compilation of machine learning models to run on a wide range of hardware
platforms
## Project Status:
Current project status: ongoing
Issues for the board: N/A
## Membership Data:
Apache TVM was founded 2020-11-17 (5 years ago)
There are currently 80 committers and 29 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 Star Yuan on 2024-10-27.
- Charlie Ruan was added as committer on 2025-05-17
- Shushi Hong was added as committer on 2025-04-21
## Project Activity:
Recent releases:
0.20.0 was released on 2025-04-27.
0.19.0 was released on 2025-01-27.
The community landed a major improvement to modernize the FFI foundation of
the project by introduce a new minimal and lightweight module. The model
summarizes the lessons in the past few years and unifieds the object and cross
language function calling conventions. Other improvements include
- Better PyTorch integration for relax
- Latest LLVM support and RISCV varlen enablement
- Support for low precision datatype in latest hardware backends such as
Blackwell GPU.
## Community Health:
The community landed 180 commits into main in the past quarter from 40 authors.
As we are in the age of generative AI, we start to see growing interest in new
models like supporting LLMs as well as integrating with existing ecosystems
like FlashInfer kernel library, as well as downstream verticals compilers such
as mlc llm. The ffi module would help such interactions.
-----------------------------------------
Attachment BZ: Report from the Apache UIMA Project [Richard Eckart de Castilho]
## Description:
Apache UIMA (*) software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video. (*) Unstructured Information Management Architecture.
## Project Status:
Current project status: Ongoing (low)
Issues for the board: none
## Membership Data:
Apache UIMA was founded 2010-03-17 (15 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.
## Project Activity:
There have been no new releases since the last board report.
Hopefully we'll find some time in summer to release the UIMA Java SDK 3.6.1.
## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list / issue tracker / Matrix channel, but again not much overall.
-----------------------------------------
Attachment CA: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Unomi was founded 2019-02-20 (6 years ago)
There are currently 16 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Jonathan Sinovassin-Naïk on 2024-11-25.
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.
## Project Activity:
A lot of work is going on by the community on the next major version, 3.0
which will include features such as multi-tenancy. It is now in the phase of
validating and correcting issues with automated testing. Aside from that the
activity has been rather low as the current major released version has worked
well for the users.
## Community Health:
The community activity has been a little low, again because of the fact that not
many issues were reported against the latest stable release, and a lot of
activity on the next major release is currently underway. Despite this, the
community is quite strong and will have an opportunity to meet in person with
two talks about the project accepted at Community over Code NA 2025.
-----------------------------------------
Attachment CB: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.
## Project Status:
Current project status: [Ongoing, with low activity
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (13 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
We finished working through CVE-2024-53678 and CVE-2024-53679. We released
2.5.2 on March 24th, 2025, along with individual patches and information on
how to patch existing installations.
## Community Health:
This has become our standard response. Apache VCL is still being used by at
least a few colleges and universities, and though activity is pretty light,
it is not dormant.
-----------------------------------------
Attachment CC: Report from the Apache Web Services Project [Daniel Kulp]
## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.
## Project Status:
Current project status: ongoing, very low activity
Issues for the board: none
## Membership Data:
Apache Web Services was founded 2003-01-22 (22 years ago)
There are currently 223 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Robert Lazarski on 2021-06-14.
- No new committers. Last addition was Alessio Soldano on 2014-09-14.
## Project Activity:
WebServices is a mature project based on standards that are also quite mature.
As such, there is not a significant amount of activity required. However, user
questions are being answered promptly, bugs are being fixed, and there are at
least 3 independent PMC members around making sure the project can continue to
produce releases as needed. Since SOAP/XML based Web Services is no longer
considered state of the art, we don't expect a major uptick in new development
efforts, new committers, etc...
After the release of WSS4J 4.0, there was very few changes this period other
than than dependabot and other dependency updates.
Latest Releases:
WSS4J 4.0.0 was released on 2025-02-14
Axiom-2.0.0 was released on 2025-02-06
WSS4J 3.0.4 was released on 2024-11-14
Neethi-3.2.1 was released on 2024-10-30
XmlSchema-2.3.1 was released on 2023-09-07
Woden-1.0M10: 2015-09
## Community Health:
As mentioned, SOAP/WebServices is not considered state-of-the-art anymore and
we are getting very little contribution from anyone other than the 2 or 3
regulars" that are driving features and changes needed for CXF (which is
being driven by their employers). Thus, we are not seeing any possibilities
for future new committers or PMC members. However, there are plenty of
people around that can do releases and answer questions and respond to
security issues. It's a mature project.
-----------------------------------------
Attachment CD: Report from the Apache Whimsy Project [Shane Curcuru]
## 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: Ongoing, Low Activity
Issues for the board: Chair is resigning.
## Membership Data:
Apache Whimsy was founded 2015-05-19 (10 years ago)
There are currently 12 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Sicker on 2020-04-11.
- No new committers. Last addition was Matt Sicker on 2020-04-09.
## Project Activity:
Slightly lower level of activity due to vacations and the slow but
steady move of some functionality to Tooling team applications.
We continue to get the occasional drive-by minor fix, and questions
are still answered when relevant.
## Community Health:
While we have sufficient PMC members to handle emergencies, the active
future of the Whimsy project is in question given the long-term move to
providing some of the major Whimsy features as fully-supported Tooling
team applications.
Issue: Shane is resigning as PMC Chair as of the June board meeting;
we do not yet have a volunteer Chair to recommend.
-----------------------------------------
Attachment CE: Report from the Apache Wicket Project [Andrea Del Bene]
-----------------------------------------
Attachment CF: Report from the Apache Xerces Project [Michael Glavassevich]
Apache Xerces is a collaborative software development project dedicated to
providing robust, full-featured, commercial-quality, and freely available XML
parsers and closely related technologies on a wide variety of platforms
supporting several languages.
========
Xerces-J
We recently completed a successful vote for a new committer and PMC and plan
to extend the invitation to this individual soon.
A member of the Apache Security team contributed a PR to add some statements
about Xerces-J's security model to the website. This contains recommendations
for users on how they should configure Xerces-J to protect their applications
when they are processing untrusted data. This will hopefully reduce the number
of reports sent to security@apache.org for issues with application
configuration that do not represent security vulnerabilities in Xerces.
The other notable activity has been review of another PR from the community
which enhances the DOM support to help the Apache Daffodil project. The
contributor of this PR may be a good candidate for another Xerces committer.
Mailing list traffic has been low; roughly 60+ posts on the j-dev and j-users
lists since the beginning of February 2025.
No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022).
========
Xerces-C
Most of the activity (which occurred in March) was in making improvements to
the documentation, most notably to better communicate information about
Xerces-C's security model so that users better understand expectations for how
they should be protecting their applications which process untrusted data.
Mailing list traffic has been low; roughly 15+ posts on the c-dev and c-users
lists since the beginning of February 2025.
The latest release is Xerces-C 3.2.5 (December 20th, 2023).
========
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
========
XML Commons
No activity over the reporting period.
========
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and September
2023 (Xerces-J).
The most recent addition to the PMC was in September 2023.
Three committers have committed changes to SVN and GitHub since February 2025.
-----------------------------------------
Attachment CG: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Yetus was founded 2015-09-15 (10 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
Not much news after the last release in March from downstream users so that's a
positive. Currently discussion what to do about our Python support
since what we have in place needs to get replaced in order to support
Python 3.13 properly.
## Community Health:
Low activity across all human-related metrics, but given the stable status of
the project that should not be surprising. Still in use by other Apache
projects and others outside of the ASF. Clearly capable of getting a release
out since we just did it.
-----------------------------------------
Attachment CH: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Project Status:
Current project status: Ongoing, low activity
Issues for the board: None
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (15 years ago)
There are currently 33 committers and 18 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 Damien Diederen on 2024-04-16.
- No new committers. Last addition was Kezhu Wang on 2024-08-02.
## Project Activity:
There is code activity on the dev list, but it is not materializing into
a release. There is a thread started for the rc0 of 3.9.4, but it has
not completed. Overall, it is missing more committer and PMC activity. There
are questions about upcoming releases, showing interest, but again, not
enough dev activity.
## Community Health:
We seem to have an issue of committer and PMC participation in the
community. We observe questions and discussion threads on the project
lists, but not enough committer and PMC engagement to drive the work
forward. We would need more engagement to be able to work with current
developers to eventually offer them committership and ensure that the
community can continue to grow and thrive.
------------------------------------------------------
End of minutes for the June 18, 2025 board meeting.
Index