Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
May 21, 2025
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:00 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones:
http://www.timeanddate.com//worldclock/fixedtime.html?iso=2025-05-21T21: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
Craig L Russell - joined :01
Matt Sicker
Ruth Suehle - joined :02
Executive Officers Absent:
none
Guests:
Alin Jerpelea
Brian Proffitt
Daniel Augusto Veronezi Salvador - joined :01
Daniel Gruno
Dave Fisher
Drew Foulks - joined :09
Julien Le Dem - joined :02
Melissa Logan
Niall Pemberton
Paul King
Sally Khudairi
Thomas Neidhart
Whitney P True - joined :13
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of April 16, 2025
See: board_minutes_2025_04_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
One highlight this reporting period was receiving a demo from the
Tooling team showcasing the new presenter functionality. This feature
significantly improves our virtual meeting facilitation, and I plan to
use it during the board meeting. The Board Agenda Tool is becoming
more feature rich, and from my understanding we are getting closer to
being able to use the tool for preparation for the meeting as well.
The agenda is seemingly short today, with only one discussion item.
For next month I will take an extra look at the list of topics we
would like to cover and ensure to pull at least one in if the agenda
does not already contain multiple discussion items.
B. President [Ruth Suehle]
This month I had the pleasure of keynoting the Eclipse Foundation's
Automotive Open Source Summit on behalf of the ASF. A lot of these
folks are newer to the open source ecosystem, which I'm always glad to
see and help with.
Thanks to those who volunteered to be mentors or judges at the UN Tech
Over Hackathon in June. They're very excited to have ASF
participation. We did have a huge number of responses, so my biggest
disappointment is that we can't invite everyone who was interested.
But I do hope that this will be an annual event with many more
opportunities in the future.
Niall Pemberton will be taking on the role of Assistant VP, Data
Privacy, to help out Christian Grobmeier.
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig R. McClanahan]
Normal operations continue, with a few notes of interest:
* Lewis and I have made significant progress in being able to analyze
Ramp data (via their APIs) in more detail, and in ways not visible
through their UI. This will make finding issues like expenses
directed to incorrect accounts, and cards that should be turned off
because they are no longer in use (or because of personnel
turnover).
* The month-end financials for April 2025 have been posted to the
board@ mailing list. This is also the end of our fiscal year, so
this will be the source of information for our overall annual
report.
* Starting in May 2025, all staffing expense reporting will be moved
from account 6435 (labelled "Infrastructure Staffing") to new
account 7500 (labelled "Foundation Staffing") to reflect the reality
that it includes more staffing than just Infra.
D. Secretary [Matt Sicker]
In April 2024, the secretary received 69 ICLAs, 1 CCLA, and 1 software
grant.
E. Executive Vice President [Jeff Jirsa]
Nothing 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 / Justin]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Zili]
See Attachment 13
C. Apache Security Team Project [Mark J. Cox / Kanchana]
See Attachment 14
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Community Development [jim]
# DeltaSpike [striker]
# EventMesh [striker]
# Geode [jim]
# Libcloud [rbowen]
# Logo Development [striker]
# POI [striker]
# Pinot [jim]
# SIS [jim]
# Samza [striker]
# Web Services [striker]
A. Apache Accumulo Project [Ed Coleman / Rich]
See Attachment A
B. Apache AGE Project [Jeff Jirsa / Jim]
See Attachment B
C. Apache Ambari Project [Brahma Reddy Battula / Sander]
See Attachment C
D. Apache Ant Project [Jan Materne / Greg]
No report was submitted.
E. Apache BookKeeper Project [Enrico Olivelli / Shane]
See Attachment E
F. Apache Brooklyn Project [Juan D. Cabrerizo / JB]
See Attachment F
G. Apache BuildStream Project [Tristan Van Berkom / Rich]
See Attachment G
H. Apache CarbonData Project [Jacky Li / Zili]
See Attachment H
I. Apache Cassandra Project [Dinesh Joshi / Jim]
See Attachment I
J. Apache Celeborn Project [Keyong Zhou / Justin]
See Attachment J
K. Apache Celix Project [Pepijn Noltes / Shane]
See Attachment K
L. Apache Community Development Project [Swapnil Mane / JB]
See Attachment L
@Rich: resolve the ComDev mission discrepancy
M. Apache CouchDB Project [Jan Lehnardt / Kanchana]
See Attachment M
N. Apache Creadur Project [Philipp Ottlinger / Rich]
See Attachment N
O. Apache DataSketches Project [Lee Rhodes / Sander]
See Attachment O
P. Apache DeltaSpike Project [Mark Struberg / Kanchana]
No report was submitted.
Q. Apache Doris Project [Mingyu Chen / Greg]
See Attachment Q
R. Apache Drill Project [Charles Givre / Jim]
No report was submitted.
S. Apache Empire-db Project [Rainer Döbele / Sander]
See Attachment S
T. Apache EventMesh Project [Eason Chen / Justin]
See Attachment T
@Justin: follow up about security issue status
U. Apache FreeMarker Project [Dániel Dékány / Shane]
See Attachment U
V. Apache Geode Project [Mark Bretl / Greg]
See Attachment V
@Greg: speak with Geode PMC about onboarding and security
concerns
Geode PMC to report again in June.
W. Apache Griffin Project [William Guo / Rich]
No report was submitted.
X. Apache Groovy Project [Paul King / Zili]
See Attachment X
Y. Apache Hop Project [Hans Van Akelyen / JB]
No report was submitted.
Z. Apache HTTP Server Project [Joe Orton / Kanchana]
See Attachment Z
AA. Apache HttpComponents Project [Michael Osipov / Kanchana]
See Attachment AA
AB. Apache Ignite Project [Dmitry Pavlov / Zili]
See Attachment AB
AC. Apache Impala Project [Zoltán Borók-Nagy / Greg]
See Attachment AC
AD. Apache Incubator Project [Justin Mclean]
See Attachment AD
AE. Apache Juneau Project [James Bognar / Rich]
See Attachment AE
AF. Apache Kafka Project [Mickael Maison / Sander]
See Attachment AF
AG. Apache Kibble Project [Sharan Foga / Shane]
No report was submitted.
AH. Apache Knox Project [Larry McCay / Jim]
See Attachment AH
AI. Apache Kylin Project [Li Yang / JB]
See Attachment AI
AJ. Apache Libcloud Project [Tomaž Muraus / Justin]
See Attachment AJ
@Justin: follow up with Libcloud PMC
AK. Apache Logging Services Project [Piotr Karwasz / Shane]
See Attachment AK
AL. Apache Logo Development Project [Daniel Gruno / Sander]
See Attachment AL
AM. Apache ManifoldCF Project [Piergiorgio Lucidi / Sander]
See Attachment AM
AN. Apache MINA Project [Guillaume Nodet / JB]
See Attachment AN
AO. Apache OpenOffice Project [Keith McKenna / Rich]
See Attachment AO
AP. Apache OpenWhisk Project [Dave Grove / Zili]
See Attachment AP
AQ. Apache Ozone Project [Sammi Chen / Greg]
See Attachment AQ
AR. Apache Perl Project [Steve Hay / Jim]
See Attachment AR
AS. Apache Phoenix Project [Istvan Toth / Kanchana]
See Attachment AS
AT. Apache Pinot Project [Kishore G / Jim]
See Attachment AT
@Jim: follow up with Pinot PMC about PMC Chair change
@Greg: broad reminder for PMC terminology
AU. Apache POI Project [Dominik Stadler / Justin]
See Attachment AU
AV. Apache Qpid Project [Robbie Gemmell / JB]
See Attachment AV
AW. Apache RocketMQ Project [Xiaorui Wang / Jim]
No report was submitted.
AX. Apache Roller Project [David M. Johnson / Zili]
See Attachment AX
AY. Apache Samza Project [Jagadish Venkatraman / Kanchana]
No report was submitted.
@Kanchana: follow up with Samza PMC about change in PMC Chair
AZ. Apache Santuario Project [Colm O hEigeartaigh / Shane]
See Attachment AZ
BA. Apache SDAP Project [Nga Thien Chung / Justin]
See Attachment BA
BB. Apache Sedona Project [Jia Yu / Kanchana]
See Attachment BB
BC. Apache Serf Project [Daniel Sahlberg / Rich]
See Attachment BC
BD. Apache ServiceComb Project [Bao Liu / Sander]
See Attachment BD
BE. Apache ShardingSphere Project [Liang Zhang / Greg]
See Attachment BE
BF. Apache ShenYu Project [Yu Xiao / Zili]
See Attachment BF
BG. Apache SIS Project [Martin Desruisseaux / Jim]
No report was submitted.
BH. Apache Solr Project [Jason Gerlowski / Justin]
See Attachment BH
BI. Apache Spark Project [Matei Alexandru Zaharia / Sander]
See Attachment BI
BJ. Apache Steve Project [Daniel Gruno / JB]
No report was submitted.
BK. Apache StreamPipes Project [Philipp Zehnder / Shane]
See Attachment BK
BL. Apache Subversion Project [Nathan Hartman / Rich]
See Attachment BL
BM. Apache Superset Project [Maxime Beauchemin / Greg]
See Attachment BM
BN. Apache Syncope Project [Francesco Chicchiriccò / Kanchana]
See Attachment BN
BO. Apache SystemDS Project [Matthias Boehm / Jim]
See Attachment BO
BP. Apache Tcl Project [Georgios Petasis / Rich]
See Attachment BP
BQ. Apache Tez Project [László Bodor / Zili]
See Attachment BQ
BR. Apache TomEE Project [David Blevins / Kanchana]
No report was submitted.
BS. Apache Traffic Control Project [Eric Friedrich / Justin]
See Attachment BS
BT. Apache Traffic Server Project [Bryan Call / Greg]
No report was submitted.
BU. Apache TsFile Project [Jialin Qiao / JB]
See Attachment BU
BV. Apache Turbine Project [Georg Kallidis / Sander]
See Attachment BV
BW. Apache Uniffle Project [He Qi / Kanchana]
See Attachment BW
BX. Apache Velocity Project [Nathan Bubna / Shane]
See Attachment BX
BY. Apache Web Services Project [Daniel Kulp / Sander]
No report was submitted.
@Sander: follow up with Web Services PMC about activity
BZ. Apache Whimsy Project [Shane Curcuru]
No report was submitted.
CA. Apache Xalan Project [Gary D. Gregory / Kanchana]
See Attachment CA
CB. Apache Xerces Project [Michael Glavassevich / Justin]
No report was submitted.
CC. Apache XML Graphics Project [Clay Leeds / Greg]
See Attachment CC
CD. Apache YuniKorn Project [Wilfred Spiegelenburg / JB]
See Attachment CD
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Establish the Apache StormCrawler Project
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to an open source collection of resources for
building low-latency, scalable web crawlers on Apache Storm.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache StormCrawler Project", be and hereby
is established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache StormCrawler be and hereby is responsible
for the creation and maintenance of software related to an open source
collection of resources for building low-latency, scalable web
crawlers on Apache Storm; and be it further
RESOLVED, that the office of "Vice President, Apache StormCrawler" be
and hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache
StormCrawler Project, and to have primary responsibility for
management of the projects within the scope of responsibility of the
Apache StormCrawler Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache StormCrawler
Project:
* Tim Allison <tallison@apache.org>
* Sebastian Nagel <snagel@apache.org>
* Julien Nioche <jnioche@apache.org>
* Markos Volikas <mvolikas@apache.org>
* Richard Zowalla <rzo1@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Zowalla be
appointed to the office of Vice President, Apache StormCrawler, 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, Establish the Apache StormCrawler Project,
was approved by Unanimous Vote of the directors present.
B. Establish the Apache Gravitino Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to managing your data and AI assets seamlessly with
a flexible, unified governance framework, including lakehouse
federation capabilities.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Gravitino Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Gravitino be and hereby is responsible for
the creation and maintenance of software related to managing your data
and AI assets seamlessly with a flexible, unified governance framework,
including lakehouse federation capabilities; and be it further
RESOLVED, that the office of "Vice President, Apache Gravitino" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache
Gravitino Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache Gravitino
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Gravitino
Project:
* Daniel Dai <daijy@apache.org>
* Junping Du <junping_du@apache.org>
* Nicholas Jiang <nicholasjiang@apache.org>
* Larry McCay <lmccay@apache.org>
* Justin Mclean <jmclean@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
* Yu Qi <yuqi4733@apache.org>
* Jerry Shao <jshao@apache.org>
* Shao Feng Shi <shaofengshi@apache.org>
* Ashish Singh <asingh@apache.org>
* Liu Xun <liuxun@apache.org>
* Xing Yong <yxac@apache.org>
* Kang Zhou <zhoukang@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jerry Shao be appointed to
the office of Vice President, Apache Gravitino, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7B, Establish the Apache Gravitino Project,
unanimous with Justin Mclean recusal
C. Change the Apache MINA Project Chair
WHEREAS, the Board of Directors heretofore appointed Guillaume Nodet
(gnodet) to the office of Vice President, Apache MINA, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Guillaume Nodet from the office of Vice President, Apache MINA, and
WHEREAS, the Project Management Committee of the Apache MINA project
has chosen by vote to recommend Thomas Wolf (twolf) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Guillaume Nodet is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache MINA, and
BE IT FURTHER RESOLVED, that Thomas Wolf be and hereby is appointed to
the office of Vice President, Apache MINA, 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 MINA Project Chair, was
approved by Unanimous Vote of the directors present.
D. Update Legal Affairs Committee Membership
WHEREAS, the Legal Affairs Committee of The Apache Software Foundation
(ASF) expects to better serve its purpose through the periodic update
of its membership; and
WHEREAS, the Legal Affairs Committee is an Executive Committee whose
membership must be approved by Board resolution.
NOW, THEREFORE, BE IT RESOLVED, that the following contributor be
added as a Legal Affairs Committee member:
Andrew Musselman <akm@apache.org>
Special Order 7D, Update Legal Affairs Committee Membership,
was approved by Unanimous Vote of the directors present.
E. Change the Apache Solr Project Chair
WHEREAS, the Board of Directors heretofore appointed Jason Gerlowski
(gerlowskija) to the office of Vice President, Apache Solr, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Jason Gerlowski from the office of Vice President, Apache Solr, and
WHEREAS, the Project Management Committee of the Apache Solr project
has chosen by vote to recommend Alessandro Benedetti (abenedetti) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jason Gerlowski is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Solr, and
BE IT FURTHER RESOLVED, that Alessandro Benedetti be and hereby is
appointed to the office of Vice President, Apache Solr, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7E, Change the Apache Solr Project Chair, was
approved by Unanimous Vote of the directors present.
F. Change the Apache Druid Project Chair
WHEREAS, the Board of Directors heretofore appointed Gian Merlino
(gian) to the office of Vice President, Apache Druid, and
WHEREAS, the Board of Directors is in receipt of the resignation of Gian
Merlino from the office of Vice President, Apache Druid, and
WHEREAS, the Project Management Committee of the Apache Druid project has
chosen by vote to recommend Abhishek Agarwal (abhishek) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Gian Merlino is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Druid, and
BE IT FURTHER RESOLVED, that Abhishek Agarwal be and hereby is appointed to
the office of Vice President, Apache Druid, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7F, Change the Apache Druid Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Policies for Foundation internal venues
@Jim: speak with VP Legal about reducing exposure to risk
9. Review Outstanding Action Items
* Shane: update Incubation guidelines to include trademark grant
[ Trademark management status briefing VP, Brand Management 2024-07-17 ]
Status:
* Craig McClanahan: pursue an audit on ramp cards
[ Review expense accounting categories 2024-10-16 ]
Status: In progress as per
https://whimsy.apache.org/board/agenda/2025-05-21/Treasurer
* Shane: follow up with PMC about PMC merge with Accumulo
[ Fluo 2025-02-19 ]
Status: Done as per
https://whimsy.apache.org/board/agenda/2025-05-21/Accumulo
* Kanchana: pursue an Attic proposal for DeltaSpike
[ DeltaSpike 2025-03-19 ]
Status: Roll Call was Failed . Proposed to. collaborate with MyFaces
* Jim: pursue a roll call for Olingo PMC
[ Olingo 2025-03-19 ]
Status: Proposed Attic 2025-05-05
* Rich: seek follow up board report next month
[ Accumulo 2025-04-16 ]
Status: Done. (Report is submitted.)
* Jim: follow up about the CSP and trademark issues
[ APISIX 2025-04-16 ]
Status: Follow-up initiated 2025-05-05
* Zili: follow up with bRPC PMC about conduct policy
[ bRPC 2025-04-16 ]
Status: Done 2025-05-18. Almost resolved as
https://lists.apache.org/thread/wy1p69qg1154hddwyxlf43q3oqk6owh7.
I'll keep this item open for a while to see how the PMC
handles new incoming Chinese user questions.
* Kanchana: connect PMC with DeltaSpike and Geronimo about synergy
[ MyFaces 2025-04-16 ]
Status: Connected PMCs of Delta Spike , Geronimo projects and MyFace.
It seems that DeltaSpike had contributed CODI and couple of
more features in the past. Looks like they had some
collaboration. However, there is no clear indication that the
three projects are actively communicating with one another;
instead, discussions seem to remain within each individual
project.
* Greg: follow up about single vendor dependency on making a usable product
[ Fineract 2025-04-16 ]
Status: Done. There was a thread on private@ along this line
of thought, which I responded to. Also reviewed dev@ and
reached out for longer conversation with the PMC Chair
James. He has taken a personal Action Item to discuss the
concern about neutrality (conversely: reliance upon third
parties) with the community. It appears the Board has no
further actions or concerns at this time.
* Ruth: pursue a CI continuity plan from infra regarding HBase
[ HBase 2025-04-16 ]
Status: Continuity ensured via stopgap solution as per
https://whimsy.apache.org/board/agenda/2025-05-21/Infrastructure
* Rich: pursue an Attic resolution for jclouds
[ jclouds 2025-04-16 ]
Status:
* Sander: follow up about projected timeline for logo
[ Logo Development 2025-04-16 ]
Status: https://lists.apache.org/thread/6xf8mkz4vfnq4cr2oc21yjbtz3k002dy
* Jim: suggest a new PMC Chair
[ Pinot 2025-04-16 ]
Status: Completed: 2025-05-05
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 22:00 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period April 2025
* ISSUES FOR THE BOARD
None.
* OPERATIONS
- Approved project names for PAIMON, IGGY, FORY, TEXERA, HAMILTON and BIFROMQ
- Provided advice regarding obtaining funding for working on ASF projects
- Responded to request to use Apache mark the name for an externally provided
service
- Restarted work on the naming policy for managed services
* REGISTRATIONS
Worked with counsel on the renewal for IMPALA in Mexico.
Worked with counsel to maintain our DRUID registration in the USA.
* INFRINGEMENTS
Attempting to contact owner of a site with a possible infringement of APISIX.
No response so far regarding a potential infringement of PDFBOX.
Formal complaint submitted regarding a potential infringement of GUACAMOLE.
No real progress regarding the downstream vendor with multiple infringements
of ASF marks.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: whilst we received a small handful of queries, no new Sponsors were
onboarded during this timeframe.
b —Renewals: we continue to secure renewal commitments from several Sponsors.
Some Bronze level Sponsors who originally supported the ASF for SEO rankings
have chosen not to renew due to new industry algorithmic updates.
c —Payments:
—New: we did not receive any new Sponsorship payments.
—Renewing: we received renewal payments from one Platinum and one Bronze
Sponsor.
—Incoming: we await payment from three renewing Platinum Sponsors, plus
payment for a partial Sponsorship-year (for the time period prior to the
organization upgrading their Sponsorship level).
2) Targeted Sponsors: we are finalizing an audit of our Targeted Sponsorships.
Under advice from ASF Infrastructure we are phasing out Targeted Sponsorships
involving in-kind donations that are administered by third parties. We are
exploring benefits options with those directly supporting an ASF Project vs.
financial contributions towards services administered by ASF Infrastructure
aimed at the ASF as a whole, or a specific beneficiary Project.
3) Sponsor Relations: our outreach and engagement continues, including
informing and fundraising for the ASF Tooling Initiative
https://www.apache.org/foundation/initiatives .
4) Event Sponsorship: we continue to promote both 2025 Community Over Code
events, as well as special event package rates extended to those ASF Gold and
Platinum Sponsors interested in Sponsoring Community Over Code North America
https://communityovercode.org/asf-sponsorship-discounts/ .
5) Individual Donations and Corporate Giving: we received $700 in online
donations via https://donate.apache.org/ .
6) Administrivia: our work systems with the Accounting and Treasury teams
continue to run smoothly. We are also coordinating with Events on Community
Over Code sponsorship and Marketing & Publicity on various promotional targets
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Issued April edition of the Plus One Newsletter
* 120 total subscribers
* Published blog announcing Jeff Jirsa as the new ASF Board EVP
* Published blog announcing 45 new ASF members
* Developed #FirstASFContribution blog #13 to highlight users who have
contributed bug fixes to ASF projects
* Updated ASF social media channels to reflect new messaging
* Created an internal-facing bulletin for the ASF President to send timed with
Plus One to better streamline communications and raise awareness of
activities across the ASF ecosystem
Project Comms
* Developed guidance to help projects navigate analyst relations
Foundation Content
* Drafted PR and marketing policy for project-hosted events and added to the
wiki[1]
* Developed social media guidance policy for attic’d projects; began work with
Attic PMC on pull request and process moving forward
* Continued work on FY25 annual report
* Created FY2026 M&P strategy
Social Media Overview
The highest performing pieces of content included the March TLP announcement
and Community Over Code NA and Asia updates.
Social Highlights (X + LinkedIn + Bluesky)
* Total Audience: 143,247
* New Followers in April: 452
* X: -22
* Bluesky: 56
* LinkedIn: 396
* Total Posts: 87
* X: 31
* Bluesky: 31
* LinkedIn: 14
* Total Engagements: 2,679
Website Analytics
* 900,777 visits, 900,697 unique visitors -9.1%
* 2 min 47s average visit duration -0.6%
* 48% visits have bounced (left the website after one page) +4.3%
* 5.` actions (page views, downloads, outlinks, internal site searches) per
visit -8.9%
* 10,003 max actions in one visit (level)
* 3,858,510 pageviews, 1,113,010 unique pageviews -18.9%
* 1 total searches on your website, 1 unique keywords -50%
* 376,774 downloads, 276,666 unique downloads -14%
* 327,721 outlinks, 209,377 unique outlinks -4.7%
[1] https://cwiki.apache.org/confluence/display/PRESS/Project+Event+Support
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Myrle Krantz]
General
=======
Infrastructure 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.
Concerns around supply chain security prompted shifts in donation
acceptance policies for VM/Cloud hosting. This has caused some
collateral damage with HBase having trouble continuing to fund their
CI infrastructure. Infra will be providing a stopgap solution to
address their immediate needs.
Concerns regarding performance of ASF websites in Mainland China have
arisen again. VP Infra has prepared a statement regarding this, and we
will be seeking direction from the Board.
Followup
========
Infra requests feedback and followup on the action item:
https://whimsy.apache.org/board/agenda/2025-04-16/flagged/HBase See
also: https://lists.apache.org/thread/tk3jxt0vlph9ozwmkh2142d859q0y7n9
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 and Security are coordinating on next steps. Current plans
involve re-evaluating the technical landscape for F/OSS MFA solutions
as the existing Keycloak POC needs considerable effort to be made
sustainable. There may be better options now. The two primary steps
(operating in parallel) are to flesh out our MFA Reset Policy and to
bring the Keycloak POC to a viable state
(or move forward with a different product.)
Major Projects
==============
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]
The Tooling team is currently working on these projects.
1. Apache Trusted Release (ATR) platform where we are about to announce an
Alpha test to the whole membership. This version shows an end to end
release process that follows current Release Policy.
2. Board Agenda Tool (BAT) where the UX is improved and we are starting to
show support for agenda updates.
3. Working with Infrastructure on proposed improvements to committee-info.txt
beyond being a fragile text format.
4. Working with Treasury to provide a framework for their use on a Workbench
platform.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
Community Over Code Asia
The CFP for C/C Asia 2025 officially closed on April 29, and Nadia Jiang
reported that they have received a total of 250 session applications from 232
unique speakers for the event. Evaluations were closed on May 6.
Community Over Code NA
258 sessions were submitted for C/C NA 2025, a 30% increase over last year's
amount. Evaluations have ended, and I hope to have the conference schedule
completed during the week of this board meeting.
Sponsorships are going well, with four confirmed Gold-level sponsorships in
process, and one Gold sponsorship invoiced. Add-on sponsorship opportunities
such as lanyard and lightning-talk sponsorship have also been picked up. We
are also in conversations with two additional vendors on potentially
sponsoring the event.
With the influx of revenue, the planners are moving forward with venue
reservations for the all-conference reception.
-----------------------------------------
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
------------------------
Applications closed for this event on May 9th. Four judges had a call
on the 10th and of 26 applications they accepted 9 of those, with one
pending more information and one in reserve.
The hard yards now begins with supporting Visa applications, booking
of Hotel Rooms and flights (for those with confirmed Visas or Visa not
required.)
Community Over Code NA
------------------------
Applications for North America (Minneapolis) opened up on the 7th
April and will close on the 14th June. We have 14 applications in so
far. Judges and Shepherds have volunteered and are ready to go.
Monthly Meetings
================
The next meeting will be held first week of June.
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]
I have received numerous ideas and suggestions for initial steps towards
rebooting the DEI effort, both on the diversity mailing list as well as
off-list remarks, and I've begun working on a broad call to action for our
membership and various project communities.
In accordance with the Jump Start Plan[1], this will be entirely opt-in, with
emphasis on working with both projects that wish to expand DEI efforts in and
around their project, as well as projects with narrower scopes in mind.
I expect we will have some discussions starting up on our mailing list very
shortly, refining the call to action and some overall themes.
[1] https://cwiki.apache.org/confluence/display/EDI/2025+EDI+jumpstart+plan
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
CRA: No surprises - which is good.
Open Source people participating (the ASF needs more!) suggest that
things are going into the right direction.
The Open Regulatory Compliance Working Group still progressing & sufficiently
low barrier/open to grow in members. (https://github.com/orcwg)
CRA Expert meeting, breakout on Open Source attended by Lars & me.
Related to this is a general meeting about wether the EU (or the world,
really) needs a new standards organisation for, specifically, Software or
similar:
https://openforumeurope.org/event/assessing-the-challenges-in-software-standardisation-does-the-eu-need-a-new-european-standardisation-organisation/
I.e distinct from the world of telecommunications, electrical and telecom
standards (the electronics standards tend to be non-normative/industrial).
OFE Capital Series:
Through Jarek; open source and our apache community should get some
visibility as part of the Polish presidency to policy makers. Danmark
is next.
USA: Waiting for the waters to calm before trying to even make sense of that.
Pretty much all contacts we had are either gone or too busy withother
stuff.
Not yet had a volunteer for the US side - will discuss this with our
President.
As said in the last board meeting; we had concerns about historic information
flows becoming stilted and that we were probing what the likelihood is of
others, outside the USA, for taking on this role. That took on a bit more
urgency by this happening much faster - with CISA pulling the funding of
MITRE key to the CVE system (and finding a 5+6 month temporary reprieve a few
days later).
As `a` global CVE system is pretty much essential (or assumed to exist) for
the implementation of the CRA - some people in this community seem to step
up; and they understand open source well.
USA - DoD:
There is a range of RFI's that touch on open source, security and its
pro-curability.
My read is that this is by and large for the (US) industry to comment on; as
there I see no indication that the role/status of Open Source in products
supplied to the DOD is being changed; this focuses on the industrial area
downstream from us.
UN: I've dropped the ball on the UN open source principles.
Will try to fix that before the next board meeting.
UN Open Source Week 2025:
Several of us (e.g. Ruth, Sander) are likely to attend the UN Open
Source meeting in June in NY; and Ruth has offered help with
mentoring/coaching their hackaton.
ECMA: Several relevant activities in ECMA. See report from VP, ECMA for details.
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
The ECMA TC 54 (Software Transparency) committee is currently working on three
standards, due to be published at the end of 2025, and updates to the
CycloneDX standard:
1. Transparency Exchange API[1]: The standard will specify a common HTTP API
to query security-related documents (SBOMs, vulnerability disclosures,
attestations, end-of-life dates, etc.) from a software vendor.
A beta1 of TEA was released on May 9th. The standard is still not stable
with frequent changes to the specification. When it will become stable,
around September, it would interesting to integrate it into ATR.
[1] https://github.com/CycloneDX/transparency-exchange-api
2. Package URL: The standard aims at assigning an identifier to each software
package and replace the CPE standard that is used in vulnerability
disclosures.
The standard is mature and will not introduce any breaking changes. The CVE
Project is considering PURL as a replacement for CPE and
`collectionURL/packageName` identifiers currently used to designate
affected packages.
PURLs are used to designate the "convenience binaries" that the ASF
publishes to ecosystem-specific repositories, but there is also a
proposal[2] to create a PURL type for the source and binary archives
publishes on `downloads.apache.org`.
[2] https://github.com/package-url/purl-spec/issues/305
3. Common Lifecycle Enumeration: The purpose of the standard is to provide
end-of-life and other lifecycle information for software releases in a
uniform way. Currently there is only a draft of the standard available at
[3].
The types of events considered by CLE are mostly targeted at commercial
companies. Some input from the ASF might be required to include the
lifecycle events of OSS projects. Since I am unable to attend CLE meetings,
I will ask for volunteers among ASF members.
Since lifecycle information (EOL dates) are very hard to find, even in
human-readable form, it might be useful to ask PMCs to include a webpage
that lists the support status of all the published software releases.
[3] https://github.com/Ecma-TC54/tg3/pull/3
4. Related to CLE, an OSS Sustainability WG[4] was created inside CycloneDX.
Its purpose is to mark projects that lack active maintenance, like projects
in the Attic or the dormant subprojects of TLPs.
I am not actively participating in the meetings of this group.
[4]: https://cyclonedx.org/participate/working-groups/
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. In fact, we got a ~50% reduction of the outstanding JIRAs
going from 30 last month to only 17 this month. A lot of the credit here goes
to Andrew Musselman for shepherding this kind of backlog grooming.
We're still working with DLAPiper on two subpoenas -- no action required from
the board at this time -- since we're handling everything in a timely fashion.
The committee has decided to extend invitation to Andrew Musselman and offer
him joining the committee as a full member. The resolution has been submitted
to the board this cycle.
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
April
* Some deserialization issues in Avro (CVE-2024-47561) also affected
Parquet (CVE-2025-46762/CVE-2025-30065) and got some press
https://www.bleepingcomputer.com/news/security/max-severity-rce-flaw-discovered-in-widely-used-apache-parquet/
* A low-severity issue in Roller accidentally got a high CVSS score,
leading to some attention
(https://thehackernews.com/2025/04/critical-apache-roller-vulnerability.html). The
CVSS score was adjusted.
* An issue in Tomcat, CVE-2025-24813 was added to CISA's Known
Exploited Vulnerabilities (KEV) database.
* We continue to work with projects to set expectations about security
properties, this month Xerces2-J
(https://xerces.apache.org/xerces2-j/security.html).
* The description of the Attic in
https://security.apache.org/blog/data-processing-compliance-statements-and-sla/
was improved.
* For the Camel issue that got leaked on the reporting side
prematurely (CVE-2025-27636/CVE-2025-29891/CVE-2025-30177) we put
together a retrospective.
* To encourage the use of MFA at the ASF, we started splitting the
scope of that project into phases and defining the first phase,
https://cwiki.apache.org/confluence/display/INFRA/MFA+project+phase+1%3A+Security
Stats for April 2025:
26 [support request/question not security notification]
25 [license confusion]
7 [report/question relating to dependencies]
Security reports: 63 (last months: 75, 78, 59)
8 ['airflow']
5 ['tomcat']
4 ['kyuubi']
3 ['guacamole', 'hertzbeat', 'httpd', 'superset']
2 ['avro', 'dolphinscheduler', 'ignite', 'nifi', 'thrift', 'trafficserver', 'website or other infrastructure']
1 ['apisix', 'couchdb', 'ctakes', 'doris', 'jackrabbit', 'jspwiki',
'linkis', 'maven', 'netbeans', 'nuttx', 'openoffice', 'orc',
'parquet', 'pekko', 'rocketmq', 'skywalking', 'spark', 'streampipes',
'trafficcontrol', 'tvm']
In total, as of 1st May 2025, we're tracking 216 (last months: 209,
199, 182) open issues across 66 projects, median age 98 days (last
months: 99, 92, 105). 69 of those issues have CVE names assigned. 20
(last month: 15, 12, 11) of these issues, across 111 projects, are
older than 365 days.
* carbondata (Health amber): PMC is not responsive (Last update:
2025-05-07)
* eventmesh (Health amber): An issue in eventmesh is over 365 days
old. (Last update: 2025-05-07)
* 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-05-06)
* 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-05-06)
* 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 Accumulo Project [Ed Coleman]
## Description:
The mission of Apache Accumulo is the creation and maintenance of software
related to a robust, scalable, distributed key/value store with cell-based
access control and customizable server-side processing.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Accumulo was founded 2012-03-20 (13 years ago)
There are currently 43 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kevin Rathbun on 2024-07-24.
- No new committers. Last addition was Kevin Rathbun on 2024-07-25.
## Project Activity:
The primary Accumulo project activity remains focused on work towards 2.1.4,
3.1, and 4.0 releases, as reported in our normal quarterly report last month.
Some draft release notes were added to the accumulo.apache.org website to
prepare for publishing for when those releases are performed.
In addition, the PMC was asked to provide a report this month to communicate
our progress migrating the Apache Fluo TLP to be a subproject of Accumulo, as
per the resolution from the April board meeting. We are making progress in
this regard. To date, we have:
1) sent an email notification to relevant list subscribers of dev@fluo,
dev@accumulo, user@accumulo, and also a courtesy copy to dev@rya, since we
were aware that Apache Rya has an optional dependency on Fluo. The email sent
was https://lists.apache.org/thread/g809tdpfrbry8vpploogksgrj93607rl
2) restored the functionality of the fluo.apache.org website; it had been
non-functional due to the use of 3rd party JavaScript and CSS web assets that
no longer work on apache.org sites, due to policy changes, and
3) created a ticket for INFRA to perform the necessary disposition tasks of
the Fluo PMC permissions/groups/memberships and assign permissions to the
Accumulo PMC (https://issues.apache.org/jira/browse/INFRA-26799). We
identified at least one possible issue that we will need to work with INFRA to
determine the best path forward. Specifically, we encountered a rule that
prevents setting a notification or commits email address in a git repo's
".asf.yaml" file to a domain other than the inferred TLP domain based on the
git repo's name. INFRA may suggest a different solution, but the two obvious
solutions appear to be to either keep the current mailing lists (at least as
an alias for their corresponding @accumulo lists), or rename the git repos
to match the conventions currently enforced. We will likely rely on INFRA's
advice for the best path forward for that.
We are currently awaiting INFRA to make the changes in the ticket. However,
this is not a blocker. While we wait on INFRA, we will continue to focus on
the main Accumulo project work, and continue to make updates to the Fluo
website, as needed.
## Community Health:
Overall community health is good and GitHub and mailing list activity remains
consistent (no substantial change to report from our regular quarterly report
provided last month).
-----------------------------------------
Attachment B: Report from the Apache AGE Project [Jeff Jirsa]
## Description:
The mission of Apache AGE is the creation and maintenance of software related
to a multi-model database that enables graph and relational models built on
PostgreSQL
## Project Status:
Current project status: The project continues to have reduced activity when
compared to the same period Year-over-Year. However, the first commits to the
primary branch since last September landed in May, which is an encouraging
change in trend.
Issues for the board: None at this time.
## Membership Data:
Apache AGE was founded 2022-05-17 (3 years ago)
There are currently 19 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- Muhammad Taha was added to the PMC
- Nick Sorrell resigned from the PMC
## Project Activity:
The project continues to have very low organic activity and has not released
software in over 12 months.
While a roll call recently revealed enough engagement within the PMC to
provide adequate governance if releases are needed, the number of active code
contributors is very low. At least one contributor is working on a large,
necessary release for Postgres 17 support, though that work is slow and
difficult.
One new PMC member was added from the existing committer base. One PMC member
resigned due to lack of time to contribute.
## Community Health:
Github user comments routinely ask for status updates and inquire about the life
and activity of the project, but the number of non-committer / non-PMC code
contributions is incredibly low. The opportunity to add new committers is
limited by lack of organic community contributions.
-----------------------------------------
Attachment C: Report from the Apache Ambari Project [Brahma Reddy Battula]
## Description:
The mission of Apache Ambari is the creation and maintenance of software
related to Hadoop cluster management
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Ambari was founded 2022-06-15 (3 years ago)
There are currently 22 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- Jialiang Cai was added to the PMC on 2025-04-26
- Yu Zhang was added as committer on 2025-02-20
## Project Activity:
Working on the UI modernization,Spring upgrade,docker based deployment
Recent releases:
3.0.0 was released on 2025-04-06
## Community Health:
Overall community health is good based on the above project ongoing activities.
-----------------------------------------
Attachment D: Report from the Apache Ant Project [Jan Materne]
-----------------------------------------
Attachment E: Report from the Apache BookKeeper Project [Enrico Olivelli]
## Description:
The mission of BookKeeper is the creation and maintenance of software related
to Replicated log service which can be used to build replicated state machines
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache BookKeeper was founded 2014-11-19 (11 years ago)
There are currently 32 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- Shiji Lu was added to the PMC on 2025-05-14
- No new committers. Last addition was Zhangjian He on 2025-01-27.
## Project Activity:
We are discussing about cutting a new series of releases from the active
branches.
4.16.6 was released on 2024-06-26.
4.17.1 was released on 2024-06-26.
4.16.5 was released on 2024-04-03.
## Community Health:
Community is doing well, our pace is not very fast, as now the project is
stable and the current users are pretty happy. We are committing bugfixes,
performance improvements and libraries upgrades.
We added recently a new PMC member.
Some stats
* dev@bookkeeper.apache.org had a 57% increase in traffic in the past quarter
(22 emails compared to 14)
* 140 commits in the past quarter (351% increase)
* 35 code contributors in the past quarter (105% increase)
* 35 PRs opened on GitHub, past quarter (66% increase)
* 38 PRs closed on GitHub, past quarter (11% increase)
-----------------------------------------
Attachment F: Report from the Apache Brooklyn Project [Juan D. Cabrerizo]
## Description:
The mission of Apache Brooklyn is the creation and maintenance of software
related to a software framework for modeling, monitoring and managing cloud
applications through autonomic blueprints.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Brooklyn was founded 2015-11-18 (9 years ago)
There are currently 20 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Iuliana Cosmina on 2021-06-04.
- No new committers. Last addition was Mykola Mandra on 2022-03-08.
## Project Activity:
- Fix deserialization issue on `WrappedValue` on nested DSL objects
- Support for override machine configuration using WinRM locations
- Improvements on the blueprint composer
- Removal of Google Analytics from web site
- Removal of old SNAPSHOT, RC and Milestone docs from the site
## Community Health:
Commit activity has decreased, but the community remains healthy—actively
resolving issues and enhancing the user experience.
-----------------------------------------
Attachment G: Report from the Apache BuildStream Project [Tristan Van Berkom]
## Description:
The mission of Apache BuildStream is the creation and maintenance of software
related to efficiently and correctly developing, building and integrating
software stacks
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache BuildStream was founded 2022-09-21 (3 years ago)
There are currently 6 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abderrahim Kitouni on 2022-09-21.
- No new committers were added.
## Project Activity:
Lots of activity in the last quarter, especially the development of
having Source plugins contribute to generation of SBoMs which has
landed in buildstream and is almost landed in buildstream-plugins,
expect a 2.5 feature release very soon.
## Community Health:
There has been talk of expanding our committers, I believe Sander is on that
and has reached out to a regular contributor to make him an official committer
but have not seen evidence of that being concluded.
Not a lot of movement on expanding community health or involvement in this
quarter.
-----------------------------------------
Attachment H: Report from the Apache CarbonData Project [Jacky Li]
## Description:
- The Apache CarbonData is data store solution for fast analytics on Big Data
platforms (including Apache Hadoop, Apache Spark, Apache Flink among others)
to help speed up queries an order of magnitude faster over petabytes of
data, with the aim of using a unified file format to satisfy all kinds of
data analysis cases.
## Issues:
- After 8 years of development, CarbonData's existing features are stable.
Currently new feature development in the community is less than expect.
Actions need to be taken to grow community development.
- Since now the technology trend in data analytics world is towards AI and
Cloud, as a new PMC chair is assigned, I suggest to enbrance the AI and
Cloud technology and discuss in community on how to add new features in
CarbonData to bring more developement in CarbonData community
## Activity:
- A new PMC chair is assigined after the resolution reviewed by board meeting
of Feb.
- CarbonData's future direction is discussed through dev maillist, including
spark version upgrade, presto version upgrade and more catalog feature
enhancement.
- Upgrade Thrift version : https://github.com/apache/carbondata/pull/4355,
https://github.com/apache/carbondata/pull/4356
- Upgrade spark version : https://github.com/apache/carbondata/pull/4354
## Health Report:
- Commit activity:
- 2 commits in the past quarter (100% increase)
- 2 code contributors in the past quarter (100% increase)
## GitHub issues:
2 issues opened on GitHub, past quarter (200% increase) 1 issue closed on
GitHub, past quarter (100% increase)
carbondata/pull/4365[HOTFIX] Fix outdated packages
carbondata/issues/4362[Task] Update dependency versions - Presto
carbondata/pull/4363Update presto dependency version to 0.291
## Releases:
* currently , community is working for upgrade spark version :
https://github.com/apache/carbondata/pull/4354
* 2.3.1 was released on 2023-11-25.
* 2.3.0 was released on 2022-01-24.
* 2.2.0 was released on 2021-08-05.
## Project Composition:
There are currently 28 committers and 19 PMC members in this project.
- The Committer-to-PMC ratio is roughly 7:5
Community changes, past quarter:
- Bo Xu was added to the PMC on 2023-04-22
- Brijoo Bopanna was added to the PMC on 2022-09-24
- Indhumathi was added to the PMC on 2022-02-16
- Vikram Ahuja was added as committer on 2022-02-10
- Akash R Nilugal was added to the PMC on 2021-04-11
## Notable mailing list trends:Mailing list activity stays at a high level
- dev@carbondata.apache.org:
- 155 subscribers (change 8):
- dev@carbondata.apache.org had a 59% decrease in traffic in the past
quarter (14 emails compared to 34):
-----------------------------------------
Attachment I: Report from the Apache Cassandra Project [Dinesh Joshi]
Are you able to provide adequate oversight of your project? That is, are there
at least three PMC members who are engaged enough to respond in the event of a
CVE or similar crisis?
Yes. There are many PMC members actively participating in dev and private list
conversations. The recent PMC roll call was 25 compared to 22 the last time.
The level of engagement in the PMC is high with active conversations and
debates.
Are there current or upcoming risks that threaten the sustainability of your
project? This could be anything from a change in employment of prolific
contributors, to an acquisition affecting a significant corporate contributor,
to a change in the technology landscape that makes your project less (or more)
relevant.
No current or upcoming risks known at this time. Over the past 3 months we
have welcomed 7 new Committers and 4 PMC members with diverse corporate
backgrounds and functional roles in the project. This represents a healthy
pace of growth and broadening of skill sets in our community.
What can the Foundation do to more effectively make your project more
successful in its mission of providing software for the public good?
N/A.
-----------------------------------------
Attachment J: Report from the Apache Celeborn Project [Keyong Zhou]
## Description:
The mission of Apache Celeborn is the creation and maintenance of software
related to an intermediate data service for big data computing engines to boost
performance, stability, and flexibility
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Celeborn was founded 2024-03-20 (a year ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Fei Wang on 2024-12-31.
- No new committers. Last addition was Sanskar Modi on 2024-12-20.
## Project Activity:
Software development activity:
- Release 0.5.4 is released on 13 March.
- Release 0.6.0 is under discussion.
- CIP-8 Refactor Partition Data Writer is finished.
- CIP-10 Introduce Celeborn Chaos Testing Framework is under development.
- CIP-13 Support automatic scaling is under development.
- CIP-14 Cpp sdk for shuffle read is finished.
- CIP-16 Merge transport proto and resource proto files is under development.
- CIP-17 Interruption Aware Slot Selection is under discussion.
- Dynamically adjust partition write parallelism is under development.
Recent releases:
- 0.5.4 was released on March 13th, 2025.
- 0.5.3 was released on January 6th, 2025.
## Community Health:
Overall community health is good. In the past quarter, the dev mail
list mail number had a 67% decrease in the past quarter to 59. The
issues mail list had a 8% decrease to 1183, the PMC considered it as
normal because the absolute number is relatively high. We have been
performing extensive outreach for our users, and encouraging them to
contribute back to the project. Also, we are active in making a voice
in various conferences to attract more users.
-----------------------------------------
Attachment K: Report from the Apache Celix Project [Pepijn Noltes]
## Description:
The mission of Celix is the creation and maintenance of software related to
Implementation of the OSGi specification adapted to C
## Project Status:
Current project status: Ongoing with low activity the last quarter
Issues for the board: None
## Membership Data:
Apache Celix was founded 2014-07-16 (11 years ago)
There are currently 17 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Peng Zheng on 2022-10-16.
- No new committers. Last addition was Zhenbao on 2022-10-19.
## Project Activity:
Although the development of new features had a low activity over the last
quarter, we had multiple fixes for the build environment to guarantee that
every submitted pull request can still be built.
## Community Health:
Overall health of the project is good, keeping in mind the size of the Celix
community. Traffic was a bit low the first quarter, but will probably increase
again in the second quarter.
-----------------------------------------
Attachment L: Report from the Apache Community Development Project [Swapnil Mane]
## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Community Development was founded 2009-11-01 (16 years ago)
There are currently 52 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Drew Foulks on 2024-08-30.
- Chris Wells was added as committer on 2025-04-11
## Project Activity:
### Google Summer of Code 2025
The ASF has once again been accepted as a GSoC mentoring organisation and has
received 27 contributor slots. While we had initially requested 35 slots, the
allocation of 27 is a solid outcome and reflects the community’s continued
commitment to mentoring and fostering open source collaboration through the GSoC
program. We thank all the mentors and projects who participated in the proposal
phase and special thanks to our GSoC org admins—Maxim Solodovnik, Sanyam Goel,
and Priya Sharma for their continued support and making it happen.
### ALC
ALC Beijing is actively involved in preparations for Community Over Code Asia
2025, including participation in bi-weekly planning meetings, with multiple
members serving as track chairs to evaluate session proposals.
ALC Shenzhen is also preparing to participate in both ApacheCon Asia 2025
and Summer Code 2025 in China. The group has been engaging in discussions
around AI-related topics, particularly the integration of Model Context
Protocol (MCP) into open-source ecosystems.
ALC Xi’an members have been focused on preparations for the Community Over
Code Asia Incubator Track.
We received requests to establish new ALC chapters in Taipei and
Florianópolis region. Both proposals have garnered interest from
multiple community members and are currently under evaluation.
### ComDev Website Improvements
We made minor improvements to the Community Development Events site, including
clearer instructions for manually triggering the calendar workflow and renaming
the calendar data file to avoid accidental edits. Thanks to Bertrand Delacretaz
and Roy Lenferink for their contributions.[WS-1]
[WS-1] https://s.apache.org/comdev-events-site-pr
### Others
We had several small discussions on various topics this quarter, but one
particularly interesting thread focused on how projects can document their
origin stories in a fair and community-oriented way. The consensus encouraged
creating dedicated history pages that provide context without disproportionately
highlighting individuals or entities.
Thanks to Zili Chen for initiating the discussion and to others who shared
their perspectives.[OTH1]
[OTH1] https://s.apache.org/b610y
## Community Health:
Our dev mailing list had almost the same traffic as the past quarter, while
gsoc@community.apache.org saw a 494% increase in traffic (101 emails compared to
17), mainly due to discussions around Google Summer of Code 2025. Overall, it
was a good quarter with active participation in various activities—thanks to our
community members.
-----------------------------------------
Attachment M: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Apache CouchDB software is a document-oriented database that can be queried and
indexed in a MapReduce fashion using JavaScript. CouchDB also offers
incremental replication with bi-directional conflict detection and resolution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache CouchDB was founded 2008-11-19 (16 years ago)
There are currently 73 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Glynn Bird on 2023-03-14.
- Tony Schmidt was added as committer on 2025-03-31
## Project Activity:
- 3.4.3 bugfix release went out fine.
- Final prep being done for the 3.5.0 feature release. It’ll have an exciting
new feature that enables even more throughput at high read/write concurrency.
- Feature planning, design and implementation for the next three feature
releases is commencing with above average speed.
- 3.4.x beta feature Nouveau, the new Lucene integration, is getting good
traction based on support requests and issues we are seeing filed.
## Community Health:
- We’re seeing a healthy hum on all channels. Mailing list and GitHub metrics
are all trending upwards after the usually slower end-of-year quarter.
-----------------------------------------
Attachment N: Report from the Apache Creadur Project [Philipp Ottlinger]
## Description:
The mission of Creadur is the creation and maintenance of software related to
Comprehension and auditing of software distributions
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Creadur was founded 2012-04-18 (13 years ago)
There are currently 13 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Claude Warren on 2024-01-23.
- No new committers. Last addition was Jean-Baptiste Onofré on 2024-01-23.
## Project Activity:
Development activity slowed a bit down, but we are still working on Rat 0.17.
Apart from that minor changes were applied to Whisker and Tentacles and
the webpages were updated (not yet released
due to interactions with Maven folks/plugin errors)
## Community Health:
No changes, development takes place slowly and steadily
as we are working on longer running branches, that take in new functionality.
Most discussions take place on the GitHub PRs directly!
-----------------------------------------
Attachment O: Report from the Apache DataSketches Project [Lee Rhodes]
## Description:
The mission of Apache DataSketches is the creation and maintenance of software
related to an open source, high-performance library of streaming algorithms
commonly called "sketches" in the data sciences. Sketches are small, stateful
programs that process massive data as a stream and can provide approximate
answers, with mathematical guarantees, to computationally difficult queries
orders-of-magnitude faster than traditional, exact methods
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache DataSketches was founded 2020-12-15 (4 years ago)
There are currently 17 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Charlie Dickens on 2023-07-04.
- Frank Grimes was added as committer on 2025-02-13
## Project Activity:
The Apache/datasketches/bigquery (ds-bq) repo continues to make progress
with more users making suggestions for improvements, and we have responded
with a few bug releases and a minor release (e.g., ds-bq 1.0.3, 1.1.0).
We are also making progress moving the java repos forward to new java versions,
e.g., both ds-java and ds-memory are now running on Java 21.
We have a growing interest from the Go community. We hope to have a Go
repository release soon.
## Community Health:
Our project is healthy. We have a small, loyal and growing community
of users that contact us when they have questions or issues. We are experiencing
growing interest from major corporations in our multi-language libraries.
The Google adoption is strong evidence of that.
We continue to get interest from scientists around the world who
offer ideas for new sketches for our library based on recent research.
-----------------------------------------
Attachment P: Report from the Apache DeltaSpike Project [Mark Struberg]
-----------------------------------------
Attachment Q: Report from the Apache Doris Project [Mingyu Chen]
## Description:
The mission of Apache Doris is the creation and maintenance of software related
to a MPP-based interactive SQL data warehousing for reporting and analysis
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Doris was founded 2022-06-15 (3 years ago)
There are currently 83 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- No new PMC members. Last addition was Pan Xiaolei on 2024-11-12.
- Zhongjian Xiong was added as committer on 2025-04-29
## Project Activity:
Software development activity:
- We released the bug fix release 2.1.9, 2.1.10, 3.0.4, 3.0.5 from 2025-02-28
to 2025-05-17
- We are preparing to making release candidates for 3.0.6 in the coming week.
- We created 2 new repos: doris-mcp-server and doris-opentelemetry-demo
## Community Health:
Overall community health is good. We host several webinar and in-person meetup
to meet our users and developers.
-----------------------------------------
Attachment R: Report from the Apache Drill Project [Charles Givre]
-----------------------------------------
Attachment S: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
Empire-db is a lightweight relational database access library dealing with all
aspects of storing, manipulating, retrieving and modelling data in relational
database management systems (RDBMS). As an alternative to traditional
OR-Mapping solutions, it provides an SQL centric, no-compromise approach that
uses a Java-Object-Model rather than Mapping Files or Annotations.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Empire-db was founded 2012-01-24 (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 Jan Glaubitz on 2016-07-10.
- No new committers. Last addition was Ralf Eichinger on 2022-03-15.
## Project Activity:
As announced in our previous report, we have completed the release
process for empire-db-3.3.0 and published the release on March 11
with the new release featuring 17 improvements and 9 bugfixes.
We currently continue development at a modest rate with some new
improvements already in progress.
## Community Health:
Our community is still alive and healthy.
8 new Jira-Tickets were opened since March 14
39 commits in the past 3 months
-----------------------------------------
Attachment T: Report from the Apache EventMesh Project [Eason Chen]
## Description:
The mission of Apache EventMesh is the creation and maintenance of software
related to a fully serverless platform used to build distributed event-driven
applications
## Project Status:
Current project status: Ongoing: With moderate activity
Issues for the board: none
## Membership Data:
Apache EventMesh was founded 2023-03-22 (2 years ago)
There are currently 54 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jianbo Liu on 2024-01-05.
- No new committers. Last addition was Zikang Chen on 2025-01-28.
## Project Activity:
New Feature EventMesh Dashboard is ready for review
Enhancement for EventMesh netty io thread improve is ready for review
Enhancement for EventMesh http/tcp server has been merged
For AI agent and workflow feature is under design
## Community Health:
The new features were under designing or developing,
so the commits and PR activity seems decrease.
Contributors increased slightly compared to the previous quarter.
Overall community health is good.
-----------------------------------------
Attachment U: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was moderate in recent months.
## Health report:
Activity was quite low in recent months, though such periods are not unusual
for this project. User questions (mostly on StackOverflow) and new Jira issues
are still being answered. Most PR-s slowly but eventually getting reviewed and
merged. Next goal is to do the next minor release as enough smaller changes
accumulated. Bigger task still unfinished in 2.x line is the java.time support
(FREEMARKER-35). The even longer term goal is continuing the ongoing
development on the 3.0 branch, so that the project can innovate, and the code
base can become more modern and attractive for new committers.
## PMC changes:
- Currently 9 PMC members.
- Added Alon Ziv on 2024-12-23
- Added Christoph Rueger on 2025-01-01
## Committer base changes:
- Currently 10 committers.
- Last added (non-PMC): Siegfried Goeschl on 2020-01-07
## Releases:
- 2.3.34 was released on 2024-12-22
-----------------------------------------
Attachment V: Report from the Apache Geode Project [Mark Bretl]
## Description:
The mission of Apache Geode is the creation and maintenance of software related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud architectures.
## Project Status:
Current project status: Dormant to Low
Issues for the board: None at the moment
## Membership Data:
Apache Geode was founded 2016-11-15 (8 years ago)
There are currently 118 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Calvin Kirs on 2022-11-14.
- No new committers. Last addition was Calvin Kirs on 2022-11-15.
## Project Activity:
We are seeing some new developement to upgrade Java version and some other bug
issues. No release scheduled at this time
## Community Health:
There are a growing number of open PRs and security reports which a becoming
stale that the community needs to address. Recently the community has seen
some new contributors working on items and the PMC is involved with
discussions to add them as committers to the community. It is a small increase
in activity and we hope it will continue.
-----------------------------------------
Attachment W: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment X: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language and related projects from the Groovy ecosystem
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No issues requiring board attention at this time.
## Membership Data:
Apache Groovy was founded 2015-11-18 (9 years ago)
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
No new PMC members. Last addition was Soeren Glasius on 2024-11-06.
No new committers. Last addition was Sergio del Amo on 2024-12-20.
## Project Activity:
Recent releases:
4.0.26 was released on 2025-02-28.
3.0.24 was released on 2025-02-27.
4.0.25 was released on 2025-01-25.
The Groovy PMC voted to accept Geb (previously gebish.org) as a Groovy
subproject late last year. There is a draft website and snapshots are currently
available. A first release under the ASF is expected in the next few weeks.
The Groovy PMC voted earlier in the year to sponsor incubation of the Grails
project (grails.org) to become a new TLP when ready. The Grails PPMC is
working well.
* the major Grails repos are now under the ASF organization
* they have voted in new committers and PPMC members
* extensive work has taken place to prepare for a first release
(including consolidation, licensing and reproducibility for the
couple of hundred artifacts that are part of a Grails release)
* community activity has been high with nearly 3000 emails across
the dev and commits mailing lists over the last quarter including
many discussions and votes
The other major goal of the Groovy PMC over the next quarter is
to move Groovy 5 towards a GA release.
## Community Health:
Overall, community activity has increased this quarter.
Work on incorporating Geb as a subproject is well advanced.
Work helping Grails on their incubation journey is well advanced.
The main Groovy project is preparing its first non-alpha release
of Groovy 5 which is expected shortly.
-----------------------------------------
Attachment Y: Report from the Apache Hop Project [Hans Van Akelyen]
-----------------------------------------
Attachment Z: Report from the Apache HTTP Server Project [Joe Orton]
## Description:
The mission of HTTP Server is the creation and maintenance of software related
to Apache Web Server (httpd)
## Project Status:
Current project status: Ongoing, low activity
Issues for the board: None
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (30 years ago)
There are currently 127 committers and 54 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 Giovanni Bechis on 2021-06-11.
- No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05.
## Project Activity:
It has been a notably quiet quarter for the project, with no new releases and
development activity being unusually low. Ongoing development was mostly
focused on minor bug fixes and backports from trunk to the stable 2.4.x
branch. Steps toward adapting release management scripts for the planned
GitHub migration continued.
## Community Health:
As with the development activity the development community metrics are all
particularly low this quarter across mailing lists, commits and use of GitHub
PRs. Activity can be cyclical and usually spikes around releases, so hopefully
this quarter is a blip; user mailing list discussion volumes continue to be very
healthy.
-----------------------------------------
Attachment AA: Report from the Apache HttpComponents Project [Michael Osipov]
## Description:
The mission of HttpComponents is the creation and maintenance of software
related to Java toolset of low level HTTP components
## Project Status
- There are no issues requiring board attention at this time.
## Membership Data:
Apache HttpComponents was founded 2007-11-14 (17 years ago)
There are currently 20 committers and 9 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 Arturo Bernal on 2023-10-27.
- No new committers. Last addition was Arturo Bernal on 2023-06-20.
## Project Activity:
- Development on master is 5.5 for Client and 5.4 for Core
## Community Health:
- Overall the project remains active. Issues and dicussions are
resolved in time.
## Releases:
- HttpClient 5.4.4 GA: 2025-04-28
- HttpClient 5.4.3 GA: 2025-03-27
- HttpCore 5.3.4 GA: 2025-03-20
- HttpClient 5.5-alpha1: 2025-02-17
-----------------------------------------
Attachment AB: Report from the Apache Ignite Project [Dmitry Pavlov]
## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Ignite was founded 2015-08-19 (10 years ago)
There are currently 78 committers and 40 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 Nikita Amelchev on 2023-11-20.
- No new committers. Last addition was Roman Puchkovskiy on 2024-04-24.
## Project Activity:
No recent releases. Previous were:
- 3.0.0 was released on 2025-02-10
- 2.17.0 was released on 2025-02-13
Ignite 3.x focused on SQL engine improvements (CAST/FORMAT, timestamp
handling), performance optimizations (B-Tree, BinaryTuple), .NET Thin client
support, and architectural fixes in replication and timestamp processing.
Ignite 2.x delivered improvements in internal API encapsulation (Binary
objects), SQL planner reliability, administrative tooling (WAL support),
documentation accuracy, and test coverage.
## Community Health:
- Despite reduced mailing list traffic (dev@ -62%, user@ -54%), code activity
remains strong (commits +22%, PRs activity +16%).
- Contributor count dipped slightly (62, -7%).
- The mailing list drop is partly due to a high base effect: the previous
quarter included two parallel releases (2.17.0 and 3.0.0), which
significantly elevated traffic at that time.
- Discussions and votes on new committer/PMC nominations are currently in
progress
-----------------------------------------
Attachment AC: Report from the Apache Impala Project [Zoltán Borók-Nagy]
## Description:
The mission of Apache Impala is the creation and maintenance of software
related to a high-performance distributed SQL engine
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: none
## Membership Data:
Apache Impala was founded 2017-11-15 (7 years ago)
There are currently 73 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Peter Rozsa was added to the PMC on 2025-03-21
- Noémi Pap-Takács was added as committer on 2025-03-12
## Project Activity:
- Improvements to the Iceberg integration
- Adding support for Iceberg REST Catalog
- Continuous work on the new Calcite planner
- Fixes in the legacy planner
- Intermediate result caching
- AI functions
- Web UI improvements
## Community Health:
reviews@ is the most reliable metric of Impala community activity level.
There were around 4000 emails to that list in March, April,
and May (until 9th)
-----------------------------------------
Attachment AD: Report from the Apache Incubator Project [Justin Mclean]
# 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 AE: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Juneau was founded 2017-10-17 (8 years ago)
There are currently 14 committers and 13 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 Gary D. Gregory on 2023-04-02.
- No new committers. Last addition was Aditya Kanthale on 2024-10-22.
## Project Activity:
8.1.4 was released on 2024-11-15.
9.0.0 was released on 2023-02-27.
Will be releasing maintenance releases in the next 30 days.
## Community Health:
Community is keeping up with security PRs. Not much development going on.
That may change in the future with possible plans for supporting integration
with Spring Boot 6 and Apache HttpClient 5.
-----------------------------------------
Attachment AF: Report from the Apache Kafka Project [Mickael Maison]
## Description:
The mission of Kafka is the creation and maintenance of software related to
Distributed publish-subscribe messaging system
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kafka was founded 2012-11-21 (12 years ago)
There are currently 67 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Josep Prat on 2024-09-06.
- TengYao Chi was added as committer on 2025-04-09
- Apoorv Mittal was added as committer on 2025-04-09
## Project Activity:
In the past quarter we released Kafka 4.0.0 which is a major milestone
for the project.
This release removes ZooKeeper support and also introduces several new major
features and changes:
- New consumer group rebalance is now production ready
- Support for Queues in early access
- Improvements to KRaft
- Removal of Java 8 support. Clients now require 11, brokers require 17
- Upgrade to log4j2
- Removal of old protocol APIs (older than Kafka 2.1)
We have 2 releases in progress:
- 3.9.1: Vote for release is on-going
- 4.1.0: Planned for July
## Community Health:
The project activity on mailing lists, Jira and GitHub remains high.
The decrease in commits (-48%) and emails on the dev list (-14%) is
a return to normal activity after last quarter which was extremely
busy due to the work around the 4.0.0 release.
The decrease in PRs closed (-59%) is also also a return to normal activity as
last quarter we enabled the stale PR GitHub action which closed a huge
number of old PRs.
-----------------------------------------
Attachment AG: Report from the Apache Kibble Project [Sharan Foga]
-----------------------------------------
Attachment AH: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters in bare metal, VM and kubernetes based workload clusters.
## Project Status:
Current project status: This is an ongoing project with moderate activity.
Release cadence is lower than I like but have an active DISCUSS thread for
our next 2.1.0 release as well as moving to a 3.0 for Java 8 deprecation.
Issues for the board: None
## Membership Data:
Apache Knox was founded 2014-02-18 (11 years ago)
There are currently 24 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marton Balázs on 2022-11-27.
- No new committers. Last addition was Marton Balázs on 2022-11-28.
- There are a couple contributors being tracked for invitation. Would
like to see a bit more community engagement but will likely extend an
invitation based on code contributions in the next quarter.
## Project Activity:
Last release is reported as 2.0.0 from 2023-02-27. We have an active
DISCUSS for next releases now. 2.1.0 and 3.0.0 for a last release with
Java 8 support and 3.0.0 to move to 17+. We are also working on moving
our documentation to git pages using mkdocs to simplify the process of
contributing to the docs.
## Community Health:
This has been a more active quarter with increases across the board.
There have been contributions from new community members that are being
tracked for committership. I have noticed some recent contributions that are
trivial in nature without a meaningful motivation to drive someone to fix them.
Without such motivation the description of problem statement and testing ends up
being missing or under specified. Keeping an eye on this and will discuss within
the community. It is an interesting consideration when the issues are
technically real but the impact of the fix can be so trivial that the time spent
in review and asking for details don't seem worth it. Not a big problem on this
project yet but an interesting topic.
-----------------------------------------
Attachment AI: Report from the Apache Kylin Project [Li Yang]
## Description:
The mission of Apache Kylin is the creation and maintenance of software
related to a distributed and scalable OLAP engine, with a focus on
pre-computation according to learned query patterns.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kylin was founded 2015-11-18 (9 years ago)
There are currently 52 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08.
- No new committers. Last addition was Pengfei Zhan on 2024-11-12.
## Project Activity:
Apache Kylin 5.0.2 was released on 27/Mar/25. Apart from normal
bug fixes, a few long-lasting security issues were finally closed.
There is a learning curve about how to deal with security issue.
We have learned and will be much easier handling later security issues.
## Community Health:
The activity metrics peak, due to the return from Lunar new year
and the release of 5.0.2. The team has got a tendency of wrapping
up and posting works till the last days before release, which means
the activity of the next quarter will likely decline.
- dev@kylin.apache.org had a 650% increase
in traffic in the past quarter (105 emails -compared to 14)
- issues@kylin.apache.org had a 1080% increase
in traffic in the past quarter (862 emails compared to 73)
- 90 commits in the past quarter (400% increase)
- 18 code contributors in the past quarter (125% increase)
- 84 PRs opened on GitHub, past quarter (740% increase)
- 87 PRs closed on GitHub, past quarter (690% increase)
-----------------------------------------
Attachment AJ: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
The mission of Libcloud is the creation and maintenance of software related to
Unified interface to the cloud.
## Project Status:
Current project status: The project has received some activity on GitHub, but
we are struggling and lacking active maintainers.
Issues for the board: See section below on lack of active
maintainers / committers.
## Membership Data:
Apache Libcloud was founded 2011-05-19 (14 years ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Moraitis on 2021-05-07.
- No new committers. Last addition was Dimitris Moraitis on 2021-05-02.
## Project Activity:
We are currently wrapping up the 3.9.0 release. I have started the vote thread
for this release, but we are still one vote short.
## Community Health:
We still struggle with active maintainers. At this point, there are only two
active maintainers: myself and another PMC member who has been active on GitHub
but rarely participated on the mailing list. I contacted them and they confirmed
they will participate in the voting threads and perform the minimum required
oversight.
That said, this still leaves us one person short of the required minimum. On
the Libcloud blog, I posted a call to action
(https://libcloud.apache.org/blog/2025/03/19/call-to-action-the-future-of-libcloud.html)
looking for new contributors.
There is one community member who has been active and is passionate about the
project and ecosystem. I plan to reach out to them soon to see if they would be
interested in becoming a PMC member / maintainer. I have not contacted them
yet, nor have I started the vote thread since I am unsure what the process is
if we are unable to reach the minimum of three votes.
At this point, my plan is to reach out to them. If they are interested and
accept, I believe we can meet the required minimum oversight and can continue
project operations. Otherwise, we should begin a discussion and vote on moving
the project to the Attic.
I would appreciate guidance from the board on how to proceed with a new PMC
member vote in the event that we cannot reach quorum despite community interest.
-----------------------------------------
Attachment AK: Report from the Apache Logging Services Project [Piotr Karwasz]
## Description:
The mission of the Apache Logging Services project is to create and maintain
software for managing the logging of application behavior, and for related
software components.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Logging Services was founded 2003-12-17 (21 years ago)
There are currently 47 committers (19 active)
and 23 PMC members (15 active) in this project.
The Committer-to-PMC ratio is 2:1 (1:1 for active members).
Community changes, past quarter:
- No new PMC members. Last addition was Fred am Nil on 2024-08-07.
- Jeff Thomas was added as committer on 2025-02-27
## Project Activity:
At the time of the last report (2025-02-19), Apache Logging Services had
3 main non dormant projects (log4cxx, log4net, Log4j). Their status is:
Log4cxx:
The project is active, with a moderate activity.
Releases:
- log4cxx-1.4.0 was released on 2025-03-01
Log4j:
The project is active, with a low activity.
In April the project has switched to RTC rules for all commits[1].
Log4j is working on releasing version 2.25.0 and 3.0.0-beta4, but due to a net
decrease in activity, their release had to be moved to end of May or beginning
of June.
[1] https://lists.apache.org/thread/8ffdw1zqrvwrsdr0ng0m2rgtdnpzg4hk
Log4net:
The project is active, with a moderate activity.
In the past quarter the project finished the migration of its website to Antora
and made two releases.
Releases:
- log4net-3.0.4 was released on 2025-02-21
- log4net-3.1.0 was released on 2025-05-12
## Community Health:
The community behind the project seems healthy, with a steady flow of bug
reports. We are working on some ways to attract more code and documentation
contributors.
-----------------------------------------
Attachment AL: Report from the Apache Logo Development Project [Daniel Gruno]
Description: The mission of Apache Logo Development is the creation and
maintenance of software related to Creation and development of a brand and
logo for the Foundation
Project Status: Current project status: Ongoing, low-to-moderate activity
Membership Data:
Apache Logo Development was founded 2024-08-20 (9 months
ago).
There are currently 16 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- One PMC member resigned on 2025-05-05
- Chris Wells was added as committer on 2025-04-10
Project Activity:
After some initial conversations about the outcome of the
first poll, it was decided to move forward with cleaning up and revising the
_top three_ logos from the last members' poll, and action was taken to send
these logo concepts to the designer used initially by the BSC, for refinement
using specs outlined by the project[2].
When this refinement has concluded, we will announce the second round of
polling to the membership.
Community Health:
Progress is being made, albeit slowly. Some lazy consensus
decisions have (from what I have observed) helped move the needle in some more
technical areas of the process where conversations have stalled a bit.
[1] https://lists.apache.org/thread/6xf8mkz4vfnq4cr2oc21yjbtz3k002dy
[2] https://lists.apache.org/thread/gfghccodsq98bvr5ws7kfqqkpllx69b1
-----------------------------------------
Attachment AM: Report from the Apache ManifoldCF Project [Piergiorgio Lucidi]
## Description:
The mission of ManifoldCF is the creation and maintenance of software related
to Framework for connecting source content repositories to target repositories
or indexes.
## Issues:
None
## Membership Data:
Apache ManifoldCF was founded 2012-05-15 There are currently 25
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, since last report in August:
- No new PMC member. Last addition was made on 2023-08-03.
- No new committers. Last addition was on 2019-08-17.
## Project Activity:
No significant new development at the moment, we are currently working on
2.29 as an hotfix version including some fixes related to bugs raised by
the community. We started a discussion about the roadmap and now we have
to understand how to approach these big changes. Upgrading to OpenJDK 21
probably means that some of the connectors must be removed or rewritten
from scratch.
Practically we have to figure out how to proceed for:
- Removing legacy connectors
- Updating connectors
- Resolving vulnerabilities
- Adding new connectors (RAG Output Connectors)
- Upgrade of the software architecture (from In-Process to Out-Of-Process)
I have to encourage greater involvement from all the contributors about
those topics.
SDK 1.02 released on 2025-02-10
2.28 was released on 2025-01-15
2.27 was released on 2024-09-26
2.26 was released on 2023-11-01
2.25 was released on 2023-06-01
## Community Health:
No new pull requests at the moment but we had two contributors that are
helping us on finding and solving bugs.
-----------------------------------------
Attachment AN: Report from the Apache MINA Project [Guillaume Nodet]
## Description:
The mission of MINA is the creation and maintenance of software related to
Multipurpose Infrastructure for Network Application
## Project Status:
Current project status: ongoing.
Issues for the board: none.
## Membership Data:
Apache MINA was founded 2006-10-25 (19 years ago)
There are currently 29 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Gary D. Gregory on 2023-09-13.
- No new committers. Last addition was Gary D. Gregory on 2022-03-24.
## Project Activity:
Recent releases:
* Apache MINA FtpServer 1.2.1 was released on 2025-02-02.
## Community Health:
A rather calm quarter with 7 commits in the past quarter, mostly bug fixes in
SSHD. We've vote to nominate a new chair (see attached resolution).
-----------------------------------------
Attachment AO: Report from the Apache OpenOffice Project [Keith McKenna]
## Description
The mission of OpenOffice is the creation and maintenance of software related
to an open-source, office-document productivity suite
## Project Composition
Apache OpenOffice was founded 2012-10-16 (12 years ago) There are currently
141 committers and 28 PMC members in this project. The Committer-to-PMC ratio
is roughly 5:1. No new PMC members. The last addition was Czesław Wolański on
2023-01-14. One new committer. John Bampton was added 2025-01-07.
## Project Activity
### Recent Releases
— 4.1.15 was released on 2023-12-22
— 4.1.14 was released on 2023-02-27
— 4.1.13 was released on 2022-07-22
— Binary downloads (total over all) as of May 1: 388,154,716
### Codebase in OpenOffice repository
Work continues on the 4.2 future release; This includes:
— Work on building a 64bit Windows version.
— Work on code spelling and code linting.
— dev@openoffice.apache.org had a 43% increase in traffic in the past quarter
(391 emails compared to 272).
— issues@openoffice.apache.org had a 25% increase in traffic in the past
quarter
(49 emails compared to 39).
### Documentation
— The OpenOffice-docs repository is where the small documentation team makes
updates.
— The Chapters for the Writer Guide are completed and ready to published, and
the compilation of the complete book is completed.
— The Chapters of the Calc Guide are ready for final review. Work has started
on the update of the Impress Guide from the old 3.3 Version.
— doc@openoffice.apache.org had a 55% decrease in traffic in the past quarter
(10 emails compared to 22) The OpenOffice-org repository has had the usual
download count updates.
### User Support
— User Forums (forum.openoffice.org) remain active in English, Spanish,
French, Hungarian, Italian, Japanese, Dutch, and Polish.
— users@openoffice.apache.org had a 38% increase in traffic in the past
quarter (75 emails compared to 54)
— users-de@openoffice.apache.org had a 104% increase in traffic in the past
quarter (45 emails compared to 22)
### Translation Interface
— Currently, we are adding a CI/CD environment to integrate translations in
AOO.
— Pootle is no longer maintained. Alternatives have been considered and there
are 2 options in the short list. Once we have the CI/CD up and running, a
switch is possible due to usage of standardized file format.
### Templates and Extensions Site
— These sites will be transitioned to static HTML sites by SourceForge.
### Community Health
Community overall health is improving. We are seeing several developers taking
on Win64, ODF 1.3, Boost, NSS, ICU and OpenSSL updates. Documentation is being
updated after a long time and we are getting translation volunteers.
## Infrastructure
— We had some issues on the wiki/forum host and these configuration issues are
fixed with some assistance.
— Both the forums and wiki have undergone numerous phases of DDoS attacks from
a farm of nearly 5000 bots. We have made countless mitigations and have
blocked two /16 networks in a cloud datacenter.
### Binary Distributions
— SourceForge mirrors are still the main way to get an OpenOffice binary
release.
— Windows builds are also published in the Microsoft Store (Windows 10/11).
— Windows users are by far our largest user group.
— Windows 10 and 1 1users can also install the binaries via WinGet.
— On both systems, we sign only the installers and are ready to use the new
service provided by SSL.com.
— A PMC discussion has been started if we can sign the complete product of
AOO.
### Facebook
We have one volunteer taking care of the presence. Work is underway to invite
more volunteers.
### X, formerly Twitter
The PMC voted to continue our handle, and we have new volunteer PMC members
who will handle our presence. The main purpose will be advertising new
releases.
### Unmaintained Python 2 code
Python 2 is unmaintained. We have in the development tree the external python3
support. Internal python 3 support is difficult. We are checking alternatives.
Planned for the next major release.
### OpenDocument Format (ODF) Version 1.3
Our default and best supported file format, the OpenDocument Format, has
received a new Standard update. As we plan to support this format, we started
work checking the ODF 1.3 specification and what we have to do to support
documents in OpenDocument Format version 1.3 (see
https://cwiki.apache.org/confluence/display/OOOUSERS/ODF+1.3+Changes), as well
as some early development.
-----------------------------------------
Attachment AP: Report from the Apache OpenWhisk Project [Dave Grove]
## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (6 years ago)
There are currently 54 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cosmin Stanciu on 2022-02-22.
- No new committers. Last addition was Luke Roy on 2023-03-06.
## Project Activity:
There is no significant new development happening in the project (either from
committers or from community members).
The most recent releases were part of a wave of openwhisk-runtime
releases made in August/September 2024:
+ openwhisk-runtime-java-1.20.0 was released on 2024-09-23.
+ openwhisk-runtime-php-1.21.0 was released on 2024-09-23.
+ openwhisk-runtime-python-1.20.0 was released on 2024-09-23
+ openwhisk-runtime-swift-1.19.0: 2024-09-23
+ openwhisk-runtime-dotnet-1.18.0: 2024-09-13
+ openwhisk-runtime-docker-1.16.0: 2024-09-07
+ openwhisk-runtime-nodejs-1.23.0: 2024-09-07
+ openwhisk-runtime-go-1.25.0: 2024-09-05
## Community Health:
There are sufficient PMC members paying attention to handle security issues,
vote on releases, and answer the relatively low volume of user questions that
we get (mainly via GitHub issues).
With the exception of a small number of academic research projects, users of
OpenWhisk have moved on to other serverless platforms. Given the significant
size of the code base, the lack of ongoing development effort, and the
declining usage of OpenWhisk, the project appears to be winding down and may
need to seriously discuss a transition to the Attic in 2026.
-----------------------------------------
Attachment AQ: Report from the Apache Ozone Project [Sammi Chen]
## Description
Apache Ozone is a scalable, redundant, and distributed object and file
store,
designed to scale to billions of objects/files and run on clusters of
thousands
of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop
Compatible File System implementation.
## Issues
None.
## Membership Data
- Apache Ozone was founded 2020-10-21.
- There are currently 83 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
- In the past quarter,
Tejaskriya was added as committer on 2025-03-09
Ivan Andika was added to the PMC on 2025-04-27
## Project Activity
- Ozone 2.0.0 is released, with 1700+ new commits since 1.4.1. Non-Ratis
support for OM and SCM have been removed since 2.0.0.
- Recon improvements, some data inconsistencies issue fixes, memory
footprint optimization, etc.
- Ozone debug tool enhancement, include command to force compact RocksDB,
command to skip some unwanted raft record, command replica chunk-info
output improvement, etc.
- Container reconciliation(HDDS-10239) development continues.
- OM Snapshot feature bug fix and performance tuning continues.
- Observility, new grafana diagrams added for cluster space utilization
growth rate, deletion service latency, RocksDB statistics, etc.
- Source code improvements
- HDDS-12251, enforce import order, and same licence header.
- HDDS-12401, enforce some PMD rules, PMD is a static code analyzer tool.
- Code cleanup and improvement, some unused codes are removed. One of the
improvements is SCM data structure(HDDS-12828).
- Test improvements(HDDS-9000), rewrite integration tests to reusing
MiniOzoneCluster if possible to speed up test execution.
- Disk space utilization management improvements(HDDS-12564), to prevent
disk space from being fully occupied.
- Disk balancer feature(HDDS-5713) development continues.
- S3 Object LifeCycle Management feature(HDDS-8342) development is kicked
off.
- Ozone S3 gateway feature enhancements(HDDS-12716) is kicked off.
- Configuration keys with 'dfs' prefix are renamed to 'hdds' prefix.
- Integration test support for Hadoop 3.1.2 is dropped.
- Ozone fat client jar, the shade mode of third dependency packages is
changed from including specific packages to excluding specific packages.
## Releases Data
- 1.0.0 was released on 2020-09-02.
- 1.1.0 was released on 2021-04-20.
- 1.2.0 was released on 2021-11-17.
- 1.2.1 was released on 2021-12-22.
- 1.3.0 was released on 2022-12-18.
- 1.4.0 was released on 2024-01-19.
- 1.4.1 was released on 2024-11-24.
- 2.0.0 was released on 2025-04-30.
## Community Health
Last board report was sent on 10th Feb 2025. Since last report,
- 36 code contributors who have commits in the past quarter (+0% change)
- dev@ozone.apache.org had 104 emails in the past quarter (+65% change)
- 732 PRs opened on GitHub, past quarter (+116% change)
- 632 PRs closed on GitHub, past quarter (+89% change)
- 474 commits in the past quarter (+65% change)
Note: The commit & PR count excludes the ones from user "app/dependabot",
who has many commits for dependency jar version upgrade.
-----------------------------------------
Attachment AR: Report from the Apache Perl Project [Steve Hay]
## Description:
The mission of Perl is the creation and maintenance of software related to
Dynamic websites using Perl
## Project Status:
Current project status: Ongoing, with low activity
Issues for the board: none
## Membership Data:
Apache Perl was founded 2000-03-10 (25 years ago)
There are currently 21 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hay on 2012-03-01.
- No new committers were added.
## Project Activity:
The last release was mod_perl-2.0.13 on 2023-10-21.
No new release is planned yet since there has been no development activity in
the last quarter, but will certainly be produced whenever necessary.
## Community Health:
The user mailing list has been a little busier of late. It's nice to see that
there are still people out there actively working on mod_perl deployments and
seeking the best ways of doing things with it.
Thanks for the feedback regarding possible new homes for binary builds since
the demise of home.apache.org. I wasn't aware that dist.apache.org was suitable
for that, but if that is going to be sunset eventually then perhaps the other
suggestion of nightlies.apache.org is the way to go, although the builds are
produced manually (not via any kind of nightly build process) so the URLs to be
publicized won't match the content being served :-/
-----------------------------------------
Attachment AS: Report from the Apache Phoenix Project [Istvan Toth]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Project Status:
Current project status: Ongoing
Issues for the board: No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-21 (11 years ago)
There are currently 60 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jacob Isaac on 2023-11-07.
- Hari Krishna Dara was added as committer on 2025-04-21
- Sanjeet Malhotra was added as committer on 2025-04-16
## Project Activity:
Apache Phoenix had its last main release 5.2.1 on 2024-11-12.
The Apache Omid subproject has released version 1.1.3 on 2025-04-17 with new
Hadoop and HBase versions, and multiple component version updates.
Phoenix 5.2.2 release is still planned for the near future, and discussions
about the 5.3.0 release have started.
Notable changes and new features in the quarter:
Dependency version updates: Updated default Hadoop version to 3.4.1.
PHOENIX-7532 Update default Hbase 2.6 version to 2.6.2
PHOENIX-7539 Update default HBase 2.5 version to 2.5.11
PHOENIX-7572 Update OMID to 1.1.3 Other
Component updates (mostly CVE) in preparation for the new release
CDC related improvements:
PHOENIX-7507 Update ROW_KEY_MATCHER column type to be VARBINARY_ENCODED
PHOENIX-7499 : Update stream metadata when data table regions merge
PHOENIX-7510 VARBINARY_ENCODED should support using hex format in WHERE...
PHOENIX-7499 : Update stream metadata when data table regions
PHOENIX-7518 Fix Flapper test in CDCQueryIT
HA related improvements:
PHOENIX-7493 Graceful Failover with Phoenix HA
PHOENIX-7502 :- Decouple principal from HAGroupInfo
PHOENIX-7495 :- Support for HBase Registry Implementations in Phoenix...
Other new features:
PHOENIX-7107 Add support for indexing on SYSTEM.CATALOG table
PHOENIX-7515: Add metric for count of Phoenix client batches used by ...
PHOENIX-7463 New ANTLR grammar to evaluate BSON's SQL styleexpressions
PHOENIX-7186 Support Square Brackets Notation for IPv6 in JDBC URL
PHOENIX-7170 Conditional TTL
As well as more than a dozen dozen other bug fixes, test fixes and
improvements and build/CI system fixes.
## Community Health:,
Overall community health is good. We have released a new Omid version and are
preparing for the 5.3.0 and 5.2.2 releases. Most of the development is still
done by our core team of about a dozen active developers.
Activity in February was low, but has picked up in March and April, especially
in the Omid subproject, related to the new release.
-----------------------------------------
Attachment AT: Report from the Apache Pinot Project [Kishore G]
## Description:
The mission of Apache Pinot is the creation and maintenance of software related
to distributed OLAP data store to provide Real-time Analytics to power wide
variety of analytical use case
## Project Status:
Current project status: Ongoing (high activity)
Issues for the board: None
## Membership Data:
Following new committers and PMCs have been added in the last 6-8 months --
Recent committers added
Sonam Mandal (April ‘25)
Chris Peck (Mar ‘25)
Abhishek Sharma (Oct ‘24)
Recent PMCs added
Gonzalo Ortiz (Feb ‘25)
## Project Activity:
The mailing list is active for release discussions, votes. The private mailing
list is active amongst the PMC for discussion of any new proposal,
committership proposal, PMC proposal.
The community members (including existing and new contributors, committers,
PMCs) are very responsive on slack answering user questions, helping debug etc
(~5442 members in the #general channel)
There is a good mix of new feature development along with continued focus on
improving the existing machinery
New feature development -
- Continue to add features to Multi Stage Query Engine
- Physical Optimizer
- Off-Heap Based Query Processing
- Query Workload Management
E.g improvements:
- Rebalancer usability and observability
- Query engine performance
- Improving health of builds by adding automated checks/verifiers during PR
check-in to detect bad API changes, non-compliant dependency changes.
## Community Health:
The project is continuing to do great with an increasing number of
contributors and users.
There is reasonable Github issue hygiene allowing the contributors to identify
different projects/ enhancements / bugs / onboarding issues etc.
Vast majority of the ongoing work is geared towards scalability/performance,
resiliency and reliability while also adding net new OLAP features.
PMCs would like to think about having a somewhat deterministic release
schedule and holding each other accountable for sticking to it.
Previous Release info --
Version 1.3.0 - Feb 17th ‘25 Version 1.2.0 - Aug 24th ‘25
-----------------------------------------
Attachment AU: Report from the Apache POI Project [Dominik Stadler]
[REPORT] Apache POI (and XMLBeans)
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats.
The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
is a tool that allows you to map XML files to generated Java classes via
XML Schema definitions.
## Project Status:
- Overall: Low activity/Mostly maintenance only
- Activity on the project is low with no-one willing/able to invest time to
look for new committers. It seems the number of people willing to be part
of an old/established project is low in general. So this project is is in a
mostly-maintenance mode unless someone new starts to invest time.
- Note: None of the active committers wants to spend time looking for new
people, so suggesting to reach out to others or invest in "marketing" will
likely not lead to much improvement.
## Membership Data:
Apache POI was founded 2007-05-16 (18 years ago) There are currently 41
committers and 34 PMC members in this project. The Committer-to-PMC ratio
is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marius Volkhart on 2020-12-27.
- No new committers. Last addition was Marius Volkhart on 2020-12-19.
## Project Activity:
- A bugfix release for Apache POI was done, providing mostly bugfixes and
smaller adjustments.
- Automated fuzzing via OSS-Fuzz continues, this provides cases where
potential bugs and security issues can be detected, see
https://github.com/google/oss-fuzz and
https://bz.apache.org/bugzilla/show_bug.cgi?id=66425 for more details.
## Project Release Activity:
- 5.4.1 was released on 2025-04-06.
- 5.4.0 was released on 2025-01-08.
- XMLBeans-5.3.0 was released on 2024-12-13.
## Community Health:
- There are a few bug-reports and user-questions which indicates that Apache
POI is still in use. Questions via email or on Stackoverflow usually get
answers.
- Bug-numbers slowly increase over time. Some newly reported issues are
fixed, but we usually get more bugs/questions reported than are addressed
by the small number of active committers, so some bugs do not get attention
any more.
- We have a very small number of active committers. There are very few
potential candidates and no-one plans to spend effort to go looking for new
ones.
### XMLBeans
- It seems there are is a small but active set of users of XMLBeans besides
Apache POI itself.
- Bug influx for XMLBeans is very low in general because it is a stable
project in maintenance-only mode.
## Bug Statistics:
### Apache POI
- 624 bugs are open overall (+3)
- Having 143 enhancements (-1)
- Thus having 481 actual bugs (+4)
- 121 of these are waiting for feedback (+4)
- Thus having 360 actual workable bugs (+-0)
- 3 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {XSSF=102, HSSF=80, SS
Common=43, HWPF=35, XSLF=31, XWPF=20, POI Overall=13, SXSSF=8, POIFS=7,
HSMF=6, OPC=5, HPSF=4, HSLF=3, HPBF=1, SL Common=1, XDDF=1}
### Apache XMLBeans
- 163 open issues (+-0)
- 117 Bug (+-0)
- 28 Improvement (+-0)
- 15 New Feature (+-0)
- 2 Wish (+-0)
- 1 Task (+-0)
-----------------------------------------
Attachment AV: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, .Net, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid JMS 2.7.0 was released on 19th February 2025.
- Qpid JMS 1.13.0 was released on 19th February 2025.
- Qpid ProtonJ2 1.0.0-M23 was released on 19th February 2025.
- Qpid Proton Dotnet 1.0.0-M11 was released on 19th February 2025.
# Community:
- The main user and developer mailing lists continue to be active and
JIRAs are being raised and addressed in line with prior activity levels.
- There were no new PMC member additions in this quarter.
The most recent new PMC member is Daniil Kirilyuk, added 22nd January 2024
- There were no new committer additions in this quarter.
The most recent new committer is Daniil Kirilyuk, added 17th February 2023
# Development:
- Work is ongoing around cleaning up older areas of the Proton core and its
language bindings, with improvements around flow control and delivery
fairness, and various updates to the Python binding. Work continues on
adding transaction support for the C++ binding and other API cleanup
towards the next release and a later removal of deprecated APIs/features
in a new major version.
- Work continues on Broker-J towards a 10.0.0 release, bumping the minimum
Java version required to Java 17 to facilitate use of Jetty 12, various
other dependency updates, and changes replacing usages of Guava.
- ProtonJ2 had a 1.0.0-M23 release, with various small bug fixes or
improvements made since then towards the next release.
- Qpid JMS had 1.13.0 and 2.7.0 releases with various dependency updates.
More of the same continues along with bug fix or improvements identified.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment AW: Report from the Apache RocketMQ Project [Xiaorui Wang]
-----------------------------------------
Attachment AX: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat, Postgres and MySQL, and is known to run on other Java servers
and relational databases. Latest release is 6.1.3 on 2025-04-09.
## Project Status:
The project is mostly dormant with most activity around updating
dependencies, making sure the code runs on the latest Java releases and
security fixes.
## Membership Data:
Apache Roller was founded 2007-02-20 (16 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2021-05-24.
- No new committers. Last addition was Yash Maheshwari on 2021-09-01.
## Project Activity:
The main activity recently was the creation, testing and release of
Roller 6.1.3 in response to a vulnerabilty report (CVE-2024-46911 ).
The release also included a set of dependency updates.
## Community Health:
The Roller community is healthy enough to maintain Roller and make bug
fix and security releases. We're always on the lookout for new contributors.
-----------------------------------------
Attachment AY: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment AZ: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
The mission of Santuario is the creation and maintenance of software related to
XML Security in Java
## Project Status:
Current project status: The Java project is actively maintained and PRs are
getting merged and releases made.
Issues for the board: Nothing to report
## Membership Data:
Apache Santuario was founded 2006-06-27 (19 years ago)
There are currently 18 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Joze Rihtarsic on 2024-05-14.
## Project Activity:
In the last quarter we did two new minor bugfix releases: Versions 4.0.4 and
3.0.6 of the Apache XML Security for Java library.
## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC
-----------------------------------------
Attachment BA: Report from the Apache SDAP Project [Nga Thien Chung]
## Description:
The mission of Apache SDAP is the creation and maintenance of software related
to an integrated data analytic center for Big Science problems
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SDAP was founded 2024-04-16 (a year ago)
There are currently 22 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Grace Llewellyn on 2024-06-23.
- No new committers. Last addition was Truc Nguyen on 2025-01-18.
## Project Activity:
Last SDAP release was 1.4.0 on 2024-11-04.
Two CS students taking Cal Poly Pomona Parallel Processing class developed a
way to track SDAP tiling progress using Solr and fixed an SDAP forward slash
issue for Windows.
## Community Health:
### Mailing List
Since last quarter, dev@sdap.apache.org had 6 new threads.
### Contributors
Since last quarter, the SDAP community has merged 8 PR and created/updated
4 Jira issues.
-----------------------------------------
Attachment BB: Report from the Apache Sedona Project [Jia Yu]
## Description:
The mission of Apache Sedona is the creation and maintenance of software
related to a big geospatial data processing engine. It provides an easy to use
APIs for spatial data scientists to manage, wrangle, and process geospatial data
## Project Status:
Current project status: ongoing
Issues for the board: all good
## Membership Data:
Apache Sedona was founded 2022-12-20 (2 years ago)
There are currently 22 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Furqaan Khan on 2024-08-20.
- Feng Zhang was added as committer on 2025-03-31
## Project Activity:
We made a new release of Sedona, 1.7.0, on March 16, 2025. It introduces
several major enhancements for spatial analytics and interoperability.
Highlights include a new SQL interface for geospatial statistics with
functions like ST_DBSCAN, ST_GLocal, and ST_LocalOutlierFactor [SEDONA-689],
and support for broadcast joins in distributed KNN joins [SEDONA-690]. This
release improves DataFrame integration with GeoArrow-enhanced GeoPandas I/O
and exposes spatial partitioning structures for optimized GeoParquet writing
[SEDONA-695]. It also adds native readers for STAC catalogs [SEDONA-704] and
OpenStreetMap PBF files [SEDONA-713], boosts rasterization performance
[SEDONA-707], and introduces new spatial functions like
ST_RemoveRepeatedPoints.
## Community Health:
The Sedona community remains active and healthy, with a strong focus on
development and collaboration. In the past quarter, the project saw a 65%
increase in code commits (443 total), reflecting vibrant technical discussions
and issue tracking. GitHub activity remains steady with nearly 100 PRs opened
and closed, and 19 contributors actively participating in the project.
-----------------------------------------
Attachment BC: Report from the Apache Serf Project [Daniel Sahlberg]
## Description:
The mission of the Apache Serf project is creating and maintaining of software
related to HTTP and associated protocols.
## Project Status
The project has sufficient PMC oversight.
There are no threats to the sustainability or resillence of the project,
although the project is very much dormant due to lack of need/requirements
from our users.
The project has no requests for the Foundation.
## Membership Data:
Apache Serf was founded 2015-08-18 (9 years ago).
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
No new PMC members. Last addition was Daniel Sahlberg and Nathan Hartman on
2023-10-05.
No new committers. Last addition was Daniel Sahlberg and Nathan Hartman on
2023-10-09.
## Project Activity
Recent releases:
* 1.3.10 was released on 2023-05-31.
* 1.3.9 was released on 2016-08-31.
## Community Health:
No activity last quarter except for one comment on an existing feature
request.
-----------------------------------------
Attachment BD: Report from the Apache ServiceComb Project [Bao Liu]
## Description:
The mission of Apache ServiceComb is the creation and maintenance of software
related to a microservice framework that provides a set of tools and components
to make development and deployment of cloud applications easier.
## Project Status:
Current project status: [Ongoing]
Issues for the board: none
## Membership Data:
Apache ServiceComb was founded 2018-10-17 (7 years ago)
There are currently 38 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cheng Youling on 2024-10-12.
- No new committers. Last addition was Zhangjian He on 2025-01-28.
## Project Activity:
ServiceComb Java Chassis 2.8.24 was released on 2025-03-28.
ServiceComb Java Chassis 2.8.23 was released on 2025-02-24.
ServiceComb Java Chassis 3.2.5 was released on 2025-02-17.
## Community Health:
Overall, community health is good. ServiceComb Java Chassis made 3 releases,
and there are some bug fixes and improments.PMC member is working on 2.9.x to
compatible with 2.8.x with some 3rd party upgrading.
-----------------------------------------
Attachment BE: Report from the Apache ShardingSphere Project [Liang Zhang]
## Description:
The mission of Apache ShardingSphere is the creation and maintenance of
software related to a database clustering system providing data sharding,
distributed transactions, and distributed database management
## Project Status:
Current project status: OK
Issues for the board: OK
## Membership Data:
Apache ShardingSphere was founded 2020-04-15 (5 years ago)
There are currently 63 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Longtao Jiang on 2024-03-28.
- No new committers. Last addition was Chenyang Ma on 2024-05-27.
## Project Activity:
Currently, the focus is on thinking about integrating
AI and ShardingSphere.
There are no plans for a version release at the moment.
## Community Health:
The existing features are already quite stable,
and the community is stabilizing.
Currently, there are many new ideas in the trend of
AI that may revolutionize ShardingSphere,
which are still being thought out and constructed.
-----------------------------------------
Attachment BF: Report from the Apache ShenYu Project [Yu Xiao]
## Description:
ShenYu is a Java native API Gateway for service proxy,
protocol conversion and API governance.
## Project Status:
Current project status: Good Healthy.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache ShenYu was founded 2022-07-20 (3 years ago)
There are currently 57 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Yunlong Lee on 2024-02-04.
- No new committers. Last addition was Shinan Chen on 2024-08-30.
## Project Activity:
We are released version 2.7.0.1 on 2025-5-4.
Software development activity:
- We added ai proxy plugin .
- We added ai token limiter plugin .
- We added ai prompt plugin .
- We added shenyu infra module .
- We added parse return type when build api
- We added Logging-Kafka and Logging-rocketmq e2e.
- We fixed some bug when using http-polling.
- We fixed namespace delete error .
- We fixed fix h2 database wrong json.
- We fixed upload jar checkfile .
- We fixed ensure data consistency by adding .
- We refactor optimize code for shenyu-sync-data.
- We refactor optimize code for shenyu-registry.
- We refactor optimize BodyParamUtils with Caffeine cache.
- We refactor optimize code for shenyu-kubernetes-controller .
- We refactor optimize code for shenyu-spring-boot-starter.
Meetups and Conferences:
- Community meetings(4) to discuss development tasks and how to build
an open governance community.
- 3 topic for ospp (successed)
## Community Health:
Overall community health is good.
Since the last report, add new 4 contributors added (currently:403).
add -3 subscribers to dev@shenyu.apache.org mailing (currently:508)
-----------------------------------------
Attachment BG: Report from the Apache SIS Project [Martin Desruisseaux]
-----------------------------------------
Attachment BH: Report from the Apache Solr Project [Jason Gerlowski]
## Description:
The mission of Apache Solr is the creation and maintenance of software related
to highly scalable distributed document search and analytics
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Solr was founded 2021-02-16 (4 years ago)
There are currently 99 committers and 61 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Gibney on 2022-12-20.
- Matthew Biscocho was added as committer on 2025-04-30
## Project Activity:
Recent releases:
* Solr 9.8.1 was released on 2025-03-11
* Solr Operator 0.9.1 was released on 2025-03-25
Areas of development & interest:
* Prepare for upcoming 10.0 release
* API renovation and migration continues
* OTEL Metrics Migration
## Community Health:
This has been a quieter quarter for us, with mailing list discussion down
a good bit compared to the same quarter last year.
However the community still feels healthy and active despite this.
Monthly meetups continue to be well-attended. And recent months have seen us
gain a new committer and start an initiative to modernize how we report
metrics. There's been increased focus as we prepare for our 10.0
release, that's (loosely) planned for this summer.
-----------------------------------------
Attachment BI: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Description:
Apache Spark is a fast and general purpose engine for large-scale data
processing. It offers high-level APIs in Java, Scala, Python, R and SQL as
well as a rich set of libraries including stream processing, machine learning,
and graph analytics.
Issues for the board:
- None
Project Status:
- Release candidates for Spark 4.0 have been created and the release has
entered the voting stage, currently on release candidate 6.
- Four SPIPs were recently accepted:
1. Introduction of the time data type
2. Support for constraints in DataSource V2 (DSv2)
3. Declarative pipelines
4. Add geospatial types to Spark
- The following votes have successfully passed:
1. Publish an additional Spark distribution with Spark Connect enabled
2. Release Apache Spark 3.5.5, deprecating spark.databricks.*
configuration
3. Retain migration logic for incorrect spark.databricks.*
configurations in Spark 4.0.x
- The PySpark User Guide has been merged into the official Spark documentation
site: https://github.com/apache/spark/pull/50589
Latest Releases:
- Spark 3.5.5 was released on February 27, 2025
- Spark 3.5.4 was released on December 20, 2024
- Spark 3.4.4 was released on October 27, 2024
Committers and PMC:
- The latest committer was added on Nov 13, 2024 (Bingkun Pan).
- The latest PMC member was added on Jan 21st, 2025 (Jie Yang).
-----------------------------------------
Attachment BJ: Report from the Apache Steve Project [Daniel Gruno]
-----------------------------------------
Attachment BK: Report from the Apache StreamPipes Project [Philipp Zehnder]
## Description:
The mission of Apache StreamPipes is the creation and maintenance of software
related to a self-service Industrial IoT toolbox which enables non-technical
users to connect, analyze and explore IoT data streams
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache StreamPipes was founded 2022-11-16 (2 years ago)
There are currently 33 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Zhenyu Luo on 2023-10-17.
- No new committers. Last addition was Marcel Frueholz on 2025-01-23.
## Project Activity:
- We released version 0.97.0 (2025-02-17)
- Introduced a new processing element, MultiModelPromptProcessor
- This processor enables users to forward stream data to an
LLM and incorporate its response directly within the pipeline
- Added a new data sink, TsFileSink
- This sink allows users to persist data in TS file format
- Enhanced the Data Explorer with expanded features (e.g., status heatmap)
- Implemented multi-language support across several modules
## Community Health:
- The number of blog posts has steadily increased over the past few months
- In addition to blog posts, we have expanded our
presence on social media platforms
-----------------------------------------
Attachment BL: Report from the Apache Subversion Project [Nathan Hartman]
## Description:
The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control
solution characterized by its reliability as a safe haven for valuable
data; the simplicity of its model and usage; and its ability to
support the needs of a wide variety of users and projects, from
individuals to large-scale enterprise operations.
## Project Status:
Current project status: Ongoing, mature.
Issues for the board: None at this time.
## Membership Data:
Apache Subversion was founded 2010-02-16 (15 years ago). Prior to
joining ASF, the project began in February of 2000 (25 years ago).
There are currently 88 committers and 49 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Timofei Zhakov on 2024-06-24.
- No new committers. Last addition was Timofei Zhakov on 2024-06-24.
## Project Activity:
Continuous Integration (CI) using GitHub Actions (GHA). In the past,
Subversion used BuildBot for CI testing. Two or three quarters ago, we
began migrating our CI to GHA since our available volunteers are
better equipped to maintain that system. Work has continued on it this
quarter, with expanded test coverage now including mod_dav_svn, our
support for the GNOME keyring, and testing on ubuntu-latest and
ubuntu-22.04-arm.
Improvements to our development tooling, specifically with regards to
backport management. We have long had two systems for managing
backports; one was codified in Perl (backport.pl), the other in Python
(backport.py), with some overlap (duplicated functionality) between
them, and some functionality that could only be done with one or the
other. It has long been on our community's wishlist to consolidate
these, and to do so in a single Python implementation since this
language is more familiar to our current volunteers. This effort has
been advanced significantly this quarter, with some of the Perl-coded
uses having been migrated.
Website improved with regards to reporting bugs and feature requests.
We have improved our "Reporting Issues" page at
https://subversion.apache.org/reporting-issues.html to help those
who wish to report a potential bug in Subversion. The new text
includes a template which users can copy-and-paste into an email and
fill in with relevant information. So far, one report of a potential
bug has been received with the help of the new template. (We are
trying to reproduce that issue and are awaiting a follow-up reply from
the reporter.)
Important fixes related to new and upcoming C compilers. It looks like
GCC 15, just released days ago, tries much harder than earlier
versions to automatically vectorize loops for increased performance,
making it unnecessary for us to hand-code such micro-optimizations.
Unfortunately, the new compiler doesn't seem to appreciate when we
hand-code them anyway. We received a report that certain hand-
vectorized code paths, which worked reliably for years, were failing
when built with GCC 15. We have replaced these with the simpler and
safer non-hand-vectorized implementations. If the compiler wishes to
do that work for us, we're happy to let it!
Work towards an eventual 1.15 release. Parts of the draft 1.15 release
notes have been overhauled to more clearly explain the new features
(Pristines On Demand and Multi-WC). The text (still a draft, as 1.15
has not been released yet) is found on the staging site, at
https://subversion-staging.apache.org/docs/release-notes/1.15.html.
Additional improvements were made to streamy checkouts, another new
feature to be included in the 1.15 release.
## Community Health:
The community appears healthy for a mature and stable project.
Multiple developers monitor the mailing lists and respond when needed.
User questions usually receive helpful responses on the mailing lists,
from both project developers and community members. The codebase,
website, and project infrastructure continue to be improved.
Our community is fully volunteer-driven and we would like to thank
everyone for their support.
-----------------------------------------
Attachment BM: Report from the Apache Superset Project [Maxime Beauchemin]
## Description:
The mission of Apache Superset is the creation and maintenance of software
related to data exploration, analysis, visualization, and dashboarding
## Project Status:
Current project status: Active and growing!
Issues for the board: None
## Membership Data:
Apache Superset was founded 2020-11-17 (5 years ago)
There are currently 69 committers and 36 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 Joe Li on 2024-12-01.
- Mehmet Yavuz was added as committer on 2025-03-24
## Project Activity:
Recent releases:
4.1.2 was released on 2025-03-24.
4.1.1 was released on 2024-11-15.
4.1.0 was released on 2024-11-01.
4.1.3 will be coming soon to get more fixes (including security patches).
5.0.0 is still forthcoming, awaiting a few final fixes.
## Community Health:
We're happy to see some more new contributors coming onboard. New PRs and
Issues are down (this seems fine), and we're actively trimming away at old PRs
and Issues, tring to get the backlog into a more manageable/sustainable state.
114 code contributors in the past quarter (29% increase)
618 PRs opened on GitHub, past quarter (-37% change)
651 PRs closed on GitHub, past quarter (-34% change)
260 issues opened on GitHub, past quarter (-26% change)
467 issues closed on GitHub, past quarter (59% increase)
We're up to 66,287 stars and 19,903 Slack members, and growing! All is well.
-----------------------------------------
Attachment BN: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
The mission of Syncope is the creation and maintenance of software related to
Managing digital identities in enterprise environments
## Project Status:
Current project status: healthy.
Issues for the board: none.
## Membership Data:
Apache Syncope was founded 2012-11-21 (12 years ago)
There are currently 25 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Lorenzo Di Cola on 2023-05-22.
- No new committers. Last addition was Samuel Garofalo on 2022-07-29.
## Project Activity:
The work to finalize 4.0.0 is almost completed: after releasing M1 a couple of
months ago, the one is expected very soon, possibly in the coming weeks.
Following discussion on dev@, the 4_0_X maintenance branch was detached from
master and aligned with next major versions of Spring and CAS.
We are also continuing with regular maintenance from the 3_0_X branch, which
should bring 3.0.12 soon as well.
Recent releases:
* 4.0.0-M1 was released on 2025-03-07
* 3.0.11 was released on 2025-03-07
## Community Health:
We continue to observe a slight raise of questions and support requests from
newcomers.
Discussions about new features and improvements keep appearing and being
followed up in dev@.
-----------------------------------------
Attachment BO: Report from the Apache SystemDS Project [Matthias Boehm]
## Description:
Apache SystemDS is a machine learning (ML) system for the end-to-end
data science lifecycle from data preparation and cleaning, over
efficient ML model training, to scoring and debugging. ML algorithms
or pipelines are specified in a high-level language with R-like syntax,
or related Python and Java APIs, and the system automatically generates
hybrid runtime plans of local, in-memory operations and distributed
operations on Apache Spark.
## Issues for the Board:
- None
## Project Status:
- Current work focuses on adding the missing primitives for
a number benchmarks such as TPCx-AI and MLPerf on SystemDS, new APIs
for the alignment of multimodal datasets, the integration of Java's
new vector and foreign memory API, and incremental refinements
of major internal components for compression, reuse, as well as
multiple GPU devices, and distributed and federated operations.
- We just released SystemDS 3.3 and switched from JDK11 to JDK17.
## Membership Data:
- Apache SystemDS was founded 2017-05-16 (incubator process entered
2015-11-02)
- Last PMC members added 2025-04-30 (Elias Strauss)
- Last committers added 2025-04-30 (Christina Dionysio)
- There are currently 37 committers and 28 PMC members in the project.
## Activity and Health:
- Code activity is healthy with 69 commits (-51%) in the last 3 months
(the reduction is largely due to careful release preparation).
- Community growth is healthy with 17 active contributors (-11%)
in the last 3 months
- Communication is healthy, mailing list activity is improving,
additional work on better documentation.
## Releases:
- Apache SystemDS 3.3.0 was released on 2025-04-22.
- Apache SystemDS 3.2.0 was released on 2024-03-17.
- Apache SystemDS 3.1.0 was released on 2023-03-13.
- Apache SystemDS 3.0.0 was released on 2022-06-20.
- Apache SystemDS 2.2.2 was released on 2022-06-25.
- Apache SystemDS 2.2.1 was released on 2021-12-02.
- Apache SystemDS 2.2.0 was released on 2021-10-30.
- Apache SystemDS 2.1.0 was released on 2021-06-28.
- Apache SystemDS 2.0.0 was released on 2020-10-14.
- Apache SystemML 1.2.0 was released on 2018-08-24.
-----------------------------------------
Attachment BP: Report from the Apache Tcl Project [Georgios Petasis]
## Description:
The mission of Tcl is the creation and maintenance of software related to
Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration
efforts. The purpose of our project is to combine the power of the Apache
web server with the capabilities of the mature, robust and flexible Tcl
scripting language. Currently only the Apache Rivet project is actively
maintained.
## Project Status:
Current project status: Ongoing
Issues for the board: Delays in board reporting,
due to a series of personal events (my father died on October 25,
my mother had a surgery on December 9, and
I was diagnosed with cancer on January 23).
## Membership Data:
Apache Tcl was founded 2000-07-24 (25 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Brice Hamon De Crevecoer on 2014-11-25.
- No new committers. Last addition was Brice B. Hamon on 2014-11-25.
## Project Activity:
As Tcl 9 has been released, work has started to make it a first class option
for building mod_rivet too. Clif Flynt will expand the coverage of Rivet for
the 4'th edition of his book "Tcl/Tk: A Developer's Guide", and Massimo Manghi
has volunteered to review the relevant chapter.
## Community Health:
The mailing lists have been more active than usual in this reporting period,
with questions concerning usage, and fixes suggestions to the issue tracker
and web pages.
-----------------------------------------
Attachment BQ: Report from the Apache Tez Project [László Bodor]
## Description:
Apache Tez is an effort to develop a generic application framework which can be
used to process arbitrarily complex DAGs of data-processing tasks and also a
re-usable set of data-processing primitives which can be used by other projects.
## Project Status:
Current project status: Ongoing.
Issues for the board: none.
## Membership Data:
Apache Tez was founded 2014-07-16 (11 years ago)
There are currently 36 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ayush Saxena on 2024-09-17.
- No new committers. Last addition was Ayush Saxena on 2024-01-09.
## Project Activity:
A new release 0.10.5 is currently being created, and created branch-0.10
to let Tez go for the 1.0.0 in the future.
## Community Health:
Keep getting contributions and had discussions regarding some issues with
0.10.4 which led to proper fixes and ultimately the 0.10.5 release.
-----------------------------------------
Attachment BR: Report from the Apache TomEE Project [David Blevins]
-----------------------------------------
Attachment BS: Report from the Apache Traffic Control Project [Eric Friedrich]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning a large
scale content delivery network (CDN)
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (7 years ago)
There are currently 31 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hamrick on 2023-02-07.
- No new committers. Last addition was Abdulrahman Elawady on 2023-09-21.
## Project Activity:
Minor project activity - almost no new development is ongoing.
## Community Health:
Slack channels have a few messages a week, we have a small but active user
community.
-----------------------------------------
Attachment BT: Report from the Apache Traffic Server Project [Bryan Call]
-----------------------------------------
Attachment BU: Report from the Apache TsFile Project [Jialin Qiao]
## Description:
The mission of Apache TsFile is the creation and maintenance of software
related to a columnar storage file format designed for time series data
## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: no
## Membership Data:
Apache TsFile was founded 2023-11-15 (a year ago)
There are currently 21 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Gaofei Cao on 2023-11-15.
- Colin Lee was added as committer on 2025-02-11
- Xinhao Gu was added as committer on 2025-04-22
## Project Activity:
### Recent releases:
- 1.1.1 was released on 2025-04-14.
- 2.0.2 was released on 2025-04-11.
- 2.0.1 was released on 2025-02-10.
### Main work of project:
The new read and write interfaces of TsFile for C/C++ and Python are still in
testing progress and almost done. Currently, the Python interface for tsfile
only supports Python versions 3.9 and below. This is because our Python
interface is built using a C wrapper, and Python 3.10 introduced incompatible
changes to the C wrapper implementation. As a result, support for Python
versions above 3.10 is still under active development, and we are working to
adapt the tsfile python interface for these newer Python versions.
## Community Health:
The activity of the development mailing list has seen a slight decline
recently, partly because some discussions have migrated to GitHub issues.
Additionally, due to some feature developments and discussions taking place
internally within Timecho, the company has started sending weekly updates to
the mailing list since last month. This initiative aims to ensure better
transparency and keep the entire community informed about their weekly
progress.
Recently, we have been exploring advancements in time-series large model
training file storage formats. Our work on tsfile, which offers high
compression rates and low query latency, has attracted interest from
contributors of open-source time-series large models on Hugging Face. Some are
experimenting with replacing Apache Arrow with tsfile for storing training
data, leveraging its efficiency advantages. They're trying to develop a
TsFileDataSet based on Tsfile query interface and wishing to join and
contribute to us.
-----------------------------------------
Attachment BV: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related to A
Java Servlet Web Application Framework and associated component library
## Project Status:
Current project status: Ongoing with low activity and at least 3 active PMC
members.
Issues for the board: None this quarter
## Membership Data:
Apache Turbine was founded 2007-05-16 (18 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers. Last addition was Youngho on 2021-12-06.
## Project Activity:
Released Components this quarter:
- Turbine Parent POM 14 was released on 2025-04-17.
- Fulcrum Quartz 2.0.0 was released on 2025-02-04.
- Fulcrum Cache 2.0.1 was released on 2025-02-03.
The project is now ready for a soon upcoming Turbine Core Release v7.0
with all required dependencies up-to-date.
## Community Health:
Turbine version 7.0 release continues to be in preparation (see last report).
The user mailing list has some activity about upcoming events and with sharing
results, how the project could be helpful. Turbine nevertheless needs to become
more attractive to gain more community.
-----------------------------------------
Attachment BW: Report from the Apache Uniffle Project [He Qi]
## Description:
The mission of Apache Uniffle is the creation and maintenance of software
related to a unified remote shuffle service
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Uniffle was founded 2025-02-19 (3 months ago)
There are currently 24 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Xianjing Feng was added to the PMC on 2025-05-07
- Lu Yuan was added as committer on 2025-04-10
- Zhou Bin was added as committer on 2025-04-01
## Project Activity:
There are some new features in the community.
The community is developing Uniffle Spark UI.
It will improve the observation of the Uniffle Spark and user experience.
On the other hand, the community rework the stage retry.
This feature can improve the fault tolerance of the Uniffle.
There are also some bugfixes and minor improvements for Uniffle.
## Community Health:
The community elected a new PMC.
There are 10 issues after the last report.
There are 24 pull requests which are merged after the last report.
The community also had many discussion about the project in the issues
and the code review of the pull request.
-----------------------------------------
Attachment BX: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
The mission of Velocity is the creation and maintenance of software related to
A Java Templating Engine
## Project Status:
Current project status: Ongoing, low activity
Issues for the board: none
## Membership Data:
Apache Velocity was founded 2006-10-24 (19 years ago)
There are currently 15 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Thomas Mortagne on 2020-03-09.
## Project Activity:
Quiet. Some work on updates to the low-use DataSourceResourceLoader.
Would still be good if we got a new Velocity Tools release out, but
it isn't urgent.
## Community Health:
Stable community. Committers are mostly content with state of the project
so development remains low. New energy would be welcome, but isn't needed
for ongoing updates and oversight.
-----------------------------------------
Attachment BY: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment BZ: Report from the Apache Whimsy Project [Shane Curcuru]
-----------------------------------------
Attachment CA: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components to engender such improvements.
## Project Status:
Current project status: The project is ongoing with low activity.
Issues for the board: None.
## Membership Data:
Apache Xalan was founded 2004-09-30 (21 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. The last addition was Joseph Kessselman on 2023-08-07.
- No new committers. The last addition was Joseph Kessselman on 2023-06-29.
## Project Activity:
Our goal is to provide, as soon as time permit,s a 2.x maintenance release and
a
3.0.0 pre-release, labeled as an alpha, beta, or milestone. But, there has been
little progress this reporting period.
## Community Health:
Our community activity is low, but we do want to create releases. There are
ongoing discussions on the mailing list and progress is tracked through Jira
tickets. The metrics in wizard show there has been no coding activity but
there has been work done in forks/branches. Some of our
speed bumps is updating our builds from Ant to Maven.
-----------------------------------------
Attachment CB: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment CC: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report
==================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
Issues for the Board
=====================
We have migrated the Apache XML Graphics repositories for XML Graphics
Commons, FOP, FOP PDF Images and Batik to GitHub:
https://github.com/apache/xmlgraphics-commons.git
https://github.com/apache/xmlgraphics-fop.git
https://github.com/apache/xmlgraphics-fop-pdf-images.git
https://github.com/apache/xmlgraphics-batik.git
Activity
========
* New versions of Apache Batik 1.19, Apache FOP 2.11, Apache FOP PDF Images
2.11 and Apache XML Graphics Commons 2.11 were released
* All XMLGraphics project repositories have been migrated from Subversion to
GitHub/GitBox: https://github.com/apache/xmlgraphics-fop.git
* A proposal to migrate XMLGraphics projects from Jira to GitHub issues was
passed. Preliminary work to effect this migration has started. The migration
is ongoing.
Latest Versions of Apache XML Graphics Project Projects:
* Apache Batik 1.19 2025-05-06
* Apache FOP 2.11 released 2025-05-06
* Apache FOP PDF Images 2.11 released 2025-05-06
* Apache XML Graphics Commons 2.11 released 2025-05-06
Project Health Report
=======================
New versions of Apache Batik 1.19, Apache FOP 2.11, Apache FOP PDF Images 2.11
and Apache XML Graphics Commons 2.11 were released.
The level of community and developer activity remains at a consistent,
moderate, level with respect to the previous reporting period.
Recent PMC Changes
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds was approved for XML Graphics PMC Chair position on March 26,
2018.
Committers
==========
Currently 21 committers.
* No new committers added in the last 3 months
* Last committer added was João André Gonçalves Thursday, November 7, 2024
Most Recent Releases
====================
* Apache Batik 1.19 2025-05-06
* Apache FOP 2.11 released 2025-05-06
* Apache FOP PDF Images 2.11 released 2025-05-06
* Apache XML Graphics Commons 2.11 released 2025-05-06
= SUB PROJECTS =
================
APACHE BATIK
=====
Batik is a Java-based toolkit for applications or applets that want to use
images in the Scalable Vector Graphics (SVG) format for various purposes, such
as display, generation or manipulation.
Latest Release
------------
Apache XML Graphics Apache Batik 1.19 was released on May 6, 2025
* Bug fixes
APACHE FOP
===
Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL
formatting objects (XSL-FO) and an output independent formatter. It is a Java
application that reads a formatting object (FO) tree and renders the resulting
pages to a specified output. Output formats currently supported include PDF,
PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a
lesser extent, RTF and TXT. The primary output target is PDF.
Latest Release
--------------
Apache XML Graphics Apache FOP 2.11 was released on May 6, 2025
* Ads support for using PDF images in fo:external-graphic elements when you
generate PDF files
* Upgrade to PDFBox 3
* Add support for PDF object streams
* Add option to lazy load fonts for PNG/TIFF/PCL output
* Add option to combine AFP page groups
* Add option to convert image to CMYK
* Add option for static content structure element per page
* Bug fixes
APACHE FOP: PDF Images Plug-In
===
Apache FOP: PDF Images Plug-In extends Apache FOP in order to add support for
using PDF images in fo:external-graphic elements when generating PDF files.
Latest Release
--------------
Apache XML Graphics Apache FOP PDF Images 2.11 was released on May 6, 2025
* Ads support for using PDF images in fo:external-graphic elements when you
generate PDF files
* Bug fixes
XML GRAPHICS COMMONS
====================
Apache XML Graphics Commons is a library that consists of several reusable
components used by Apache Batik and Apache FOP. Many of these components can
easily be used separately outside the domains of SVG and XSL-FO. You will find
components such as a PDF library, an RTF library, Graphics2D implementations
that let you generate PDF & PostScript files, and much more.
Latest Release
------------
Apache XML Graphics Commons 2.11 was released on May 6, 2025
* Bug fixes
-----------------------------------------
Attachment CD: Report from the Apache YuniKorn Project [Wilfred Spiegelenburg]
## Description:
The mission of Apache YuniKorn is the creation and maintenance of software
related to a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds
## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: none
## Membership Data:
Apache YuniKorn was founded 2022-03-16 (3 years ago)
There are currently 37 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Chia-Ping Tsai on 2024-03-07.
- No new committers. Last addition was Kuan Po Tseng on 2024-03-15.
## Project Activity:
Recent releases:
1.6.2 was released on 2025-03-18.
1.6.1 was released on 2025-01-24.
1.6.0 was released on 2024-09-17.
1.6.2 was released with critical bug fixes only. A 1.6.3 release is being
prepared to fix a crash in the scheduler discovered in 1.6.2.
Scale testing is still an issue. Code for a testing framework is progressing
slowly. Delivery has slipped out of 1.7.0.
YuniKorn 1.7.0 has passed it feature freeze and jira cleanup has started for a
release in the next quarter. 1.7.0 is planned for late May, early June 2025.
## Community Health:
11 new Jira accounts were requested. 52 new Jiras created and 54 resolved,
with corresponding GitHub PRs: 51 created and 46 resolved.
------------------------------------------------------
End of minutes for the May 21, 2025 board meeting.
Index