Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
July 16, 2025
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:01 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones:
http://www.timeanddate.com//worldclock/fixedtime.html?iso=2025-07-16T21:00:00&msg=ASF+Board+Meeting
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Rich Bowen
Zili Chen
Shane Curcuru
Jim Jagielski
Jean-Baptiste Onofré
Greg Stein
Sander Striker
Kanchana Pradeepika Welagedara
Directors Absent:
Justin Mclean
Executive Officers Present:
Craig R. McClanahan
Craig L Russell
Matt Sicker
Ruth Suehle
Executive Officers Absent:
Jeff Jirsa
Guests:
Brian Proffitt
Daniel Gruno
Dave Fisher
Jarek Potiuk - joined :01
Julien Le Dem - joined :27
Melissa Logan - joined :14
Paul King
Sally Khudairi
Thomas Neidhart
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of June 18, 2025
See: board_minutes_2025_06_18.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
Thanks to Vice Chair Rich Bowen for running last month’s meeting.
While I was able to attend, it was impractical to run the meeting on
my laptop with hotel Wi-Fi. The meeting went smooth, and I’m looking
forward to seeing Rich wield the gavel at future meetings.
I’m continuing to use the new board agenda tool this month. I believe
it is coming along for running and following the meeting; I welcome
any feedback for the Tooling team.
Last month, I attended the UN Open Source Week (Wed/Thu sessions). The
format wasn’t ideal for on-site collaboration, but it did allow for
valuable networking. The ASF was praised in a breakout session for how
we operate. Ironically in the same session a vendor failed to be
transparent to mention the ASF project behind the technology they were
championing. There's an opportunity at the UN events to raise
awareness about how we work and how to engage. The co-organizing of
the Tech Over Hackathon as mentioned by the President in last month's
report is one way to help with that. The room was filled with
individuals passionate about building digital public infrastructure,
and it’s clear that many of our projects are already part of that
effort, whether recognized or not. As projects get applied in new use
cases, there’s lots of potential for new contributors and
collaborators here.
Between travel and the end of the school year, I’ve been slower this
month, hence the late report. Pre-approvals are working well, but as
of this morning, many reports were still missing quorum. Please review
and approve reports as you have time so we don’t miss out on approving
a report that was submitted on time.
B. President [Ruth Suehle]
Our D&O insurance has been renewed for another year very
easily. The rate increased $109 over last year.
The operations team is working on improving the future of all
of their roles by considering their approaches to and
availability of assistant VPs and where the information needed
to do their roles is stored. Dave Fisher noted that
committee-info will be frozen for a while and has proposed a
replacement option to the operations list. We're also working
on improving things like calendar usage and annual reminders
for recurring needs.
More broadly, the operations teams have a lot of great things
going on individually--please refer to their reports--but I
wanted to recognize that their engagement in getting good work
done during what are often a slow couple of months (during
what's summer for most of our folks) has been really
great. Kudos and thanks.
Additionally, please see Attachments 1 through 11.
C. Treasurer [Craig R. McClanahan]
As many of you have observed, I sent couple of CSV files (from
software that we, Treasury, have created to pull data from Ramp's APIs
so that it can be filtered and sorted locally) to the lead person of
each "Department" (that's what Ramp calls them). The files listed the
individual cards for people assigned to that Department, and a list of
all the Ramp transactions that these people did last fiscal year (May
2024 to April 2025).
I have not heard back from everyone yet, but one important thing has
become clear: many people who have different responsibilities are
using the same card across those responsibilities. On any particular
card, the expenses get assigned to one and only one account, which can
lead to incorrect classifications.
What I plan to do about this is to implement the following policies:
* For each Department, I will work with the Card Manager (can be the
lead person or someone they delegate the responsibility to) to
understand the mechanics of issuing and managing cards. The
required steps are documented on our Wiki, at the URL below.
* Educate Card Managers on the need to issue multiple cards to the
same person, if that person has responsibilities that need their
expenses assigned to different expense categories.
* Follow up on particular cases where individual card holders that
have only one card currently but should have more than one.
Documentation for Ramp Card Holders:
https://cwiki.apache.org/confluence/x/RZFEF
D. Secretary [Matt Sicker]
In June, the secretary received 57 ICLAs, 2 CCLAs, 1 software grant,
and 1 CoI affirmation.
E. Executive Vice President [Jeff Jirsa]
Nothing material to report
F. Vice Chair [Rich Bowen]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Greg]
See Attachment 12
B. Apache Legal Affairs Committee [Roman Shaposhnik / Zili]
No report was submitted.
C. Apache Security Team Project [Mark J. Cox / Shane]
See Attachment 14
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Airavata [striker]
# Brand Management [rbowen]
# DeltaSpike [striker]
# Fineract [jim]
# Fluo [striker]
# Griffin [striker]
# Incubator [jim]
# Kibble [striker]
# Mesos [jbo, rbowen]
# Olingo [jim]
# OpenMeetings [striker]
# Petri [jim]
# Samza [striker]
# Steve [tison]
A. Apache Accumulo Project [Ed Coleman / JB]
See Attachment A
B. Apache ActiveMQ Project [Christopher L. Shannon / Sander]
See Attachment B
C. Apache Airavata Project [Suresh Marru / Kanchana]
See Attachment C
D. Apache Answer Project [Ning Qi / Jim]
See Attachment D
E. Apache Ant Project [Jan Materne / Justin]
See Attachment E
F. Apache APISIX Project [Ming Wen / Rich]
See Attachment F
G. Apache Aries Project [Christian Schneider / Rich]
See Attachment G
H. Apache Arrow Project [Neal Richardson / Shane]
See Attachment H
I. Apache AsterixDB Project [Ian Maxon / JB]
See Attachment I
J. Apache Atlas Project [Madhan Neethiraj / Sander]
See Attachment J
K. Apache Attic Project [Hervé Boutemy / Jim]
See Attachment K
L. Apache Avro Project [Ryan Skraba / Zili]
No report was submitted.
M. Apache bRPC Project [James Ge / Justin]
See Attachment M
N. Apache BVal Project [Matthew Jason Benson / Greg]
See Attachment N
O. Apache Calcite Project [Ruben Q L / Kanchana]
See Attachment O
P. Apache CarbonData Project [Jacky Li / Jim]
No report was submitted.
Q. Apache Causeway Project [Jörg Rade / JB]
See Attachment Q
R. Apache Celix Project [Pepijn Noltes / Sander]
No report was submitted.
S. Apache CXF Project [Andriy Redko / Zili]
See Attachment S
T. Apache DataFu Project [Eyal Allweil / Justin]
No report was submitted.
U. Apache DB Project [Bryan Pendleton / Greg]
See Attachment U
V. Apache DeltaSpike Project [Mark Struberg / Kanchana]
See Attachment V
W. Apache Directory Project [Shawn McKinney / Shane]
See Attachment W
X. Apache DolphinScheduler Project [Lidong Dai / Kanchana]
See Attachment X
Y. Apache Druid Project [Abhishek Agarwal / Shane]
See Attachment Y
Z. Apache Dubbo Project [Jun Liu / Zili]
See Attachment Z
AA. Apache Fineract Project [James Dailey / Kanchana]
See Attachment AA
@Greg: clarify community overlap with Mifos and state of
community
AB. Apache Flagon Project [Joshua C. Poore / Jim]
See Attachment AB
AC. Apache Flex Project [Harbs / Rich]
No report was submitted.
AD. Apache Fluo Project [Keith Turner / Greg]
See Attachment AD
@Matt: ensure Fluo is removed from schedule for reporting
AE. Apache Geronimo Project [Jean-Louis Monteiro / Justin]
No report was submitted.
AF. Apache Gravitino Project [Jerry Shao / JB]
See Attachment AF
AG. Apache Griffin Project [William Guo / Sander]
No report was submitted.
@Sander: pursue Attic resolution for Griffin
AH. Apache Hadoop Project [Xiaoqiao He / Jim]
See Attachment AH
AI. Apache HBase Project [Duo Zhang / Rich]
See Attachment AI
AJ. Apache Hive Project [Naveen Gangam / Sander]
See Attachment AJ
AK. Apache Incubator Project [Justin Mclean]
See Attachment AK
@Sander: start board discussion around Incubator
AL. Apache InLong Project [Charles Zhang / Kanchana]
See Attachment AL
AM. Apache James Project [Benoit Tellier / JB]
See Attachment AM
AN. Apache Jena Project [Andy Seaborne / Shane]
See Attachment AN
AO. Apache JMeter Project [Bruno Demion / Zili]
See Attachment AO
AP. Apache Johnzon Project [Jean-Louis Monteiro / Justin]
No report was submitted.
AQ. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Greg]
See Attachment AQ
AR. Apache Kibble Project [Sharan Foga / Sander]
No report was submitted.
@Rich: follow up about Attic
AS. Apache Kudu Project [Andrew Wong / Zili]
See Attachment AS
AT. Apache Logo Development Project [Daniel Gruno / Sander]
See Attachment AT
AU. Apache Lucene.Net Project [Shad Storhaug / Justin]
No report was submitted.
AV. Apache MADlib Project [Ed Espino / Jim]
No report was submitted.
AW. Apache Mahout Project [Shannon Quinn / Greg]
See Attachment AW
AX. Apache Maven Project [Hervé Boutemy / Rich]
See Attachment AX
AY. Apache Mesos Project [Qian Zhang / Kanchana]
See Attachment AY
@Kanchana: pursue Attic for Mesos
AZ. Apache MINA Project [Thomas Wolf / JB]
See Attachment AZ
BA. Apache MyFaces Project [Bernd Bohmann / Kanchana]
See Attachment BA
BB. Apache Mynewt Project [Szymon Janc / Shane]
See Attachment BB
BC. Apache NiFi Project [Joe Witt / Justin]
See Attachment BC
BD. Apache Nutch Project [Sebastian Nagel / Rich]
See Attachment BD
BE. Apache NuttX Project [Alin Jerpelea / Greg]
See Attachment BE
BF. Apache Olingo Project [Michael Bolz / Jim]
See Attachment BF
@Jim: ensure an Attic resolution is filed
BG. Apache OpenJPA Project [Mark Struberg / Zili]
See Attachment BG
BH. Apache OpenMeetings Project [Maxim Solodovnik / Kanchana]
See Attachment BH
BI. Apache OpenOffice Project [Keith McKenna / Shane]
See Attachment BI
BJ. Apache ORC Project [William Hyun / Sander]
See Attachment BJ
BK. Apache Parquet Project [Julien Le Dem / Jim]
See Attachment BK
BL. Apache PDFBox Project [Andreas Lehmkühler / JB]
See Attachment BL
BM. Apache Petri Project [Greg Stein]
See Attachment BM
BN. Apache PLC4X Project [César García / JB]
See Attachment BN
BO. Apache Ranger Project [Selvamohan Neethiraj / Greg]
See Attachment BO
BP. Apache Ratis Project [Tsz-wo Sze / Shane]
No report was submitted.
BQ. Apache Rya Project [Adina Crainiceanu / Kanchana]
See Attachment BQ
BR. Apache Samza Project [Jagadish Venkatraman / Kanchana]
No report was submitted.
@Kanchana: follow up with Samza about potential for Attic
BS. Apache SeaTunnel Project [Jun Gao / Rich]
See Attachment BS
BT. Apache SkyWalking Project [Sheng Wu / Sander]
See Attachment BT
BU. Apache Steve Project [Daniel Gruno / Jim]
See Attachment BU
BV. Apache StormCrawler Project [Richard Zowalla / Justin]
See Attachment BV
BW. Apache StreamPark Project [Huajie Wang / Zili]
See Attachment BW
BX. Apache Struts Project [René Gielen / Rich]
See Attachment BX
BY. Apache Synapse Project [Isuru Udana / JB]
See Attachment BY
BZ. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Kanchana]
See Attachment BZ
CA. Apache Tcl Project [Georgios Petasis / Shane]
See Attachment CA
CB. Apache Tez Project [László Bodor / Sander]
See Attachment CB
CC. Apache Thrift Project [Jens Geyer / Greg]
See Attachment CC
CD. Apache Tika Project [Tim Allison / Justin]
See Attachment CD
CE. Apache TinkerPop Project [Kelvin Lawrence / Jim]
See Attachment CE
CF. Apache Traffic Server Project [Bryan Call / Zili]
No report was submitted.
CG. Apache Web Services Project [Daniel Kulp / Sander]
No report was submitted.
CH. Apache Wicket Project [Andrea Del Bene / Zili]
See Attachment CH
CI. Apache Zeppelin Project [Jongyoul Lee / Kanchana]
See Attachment CI
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Shiro Project Chair
WHEREAS, the Board of Directors heretofore appointed Brian Demers
(bdemers) to the office of Vice President, Apache Shiro, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Brian Demers from the office of Vice President, Apache Shiro, and
WHEREAS, the Project Management Committee of the Apache Shiro project
has chosen by vote to recommend Lenny Primak (lprimak) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Brian Demers is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Shiro, and
BE IT FURTHER RESOLVED, that Lenny Primak be and hereby is appointed to
the office of Vice President, Apache Shiro, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7A, Change the Apache Shiro Project Chair, was
approved by Unanimous Vote of the directors present.
B. Terminate the Apache Samza Project
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Samza project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Samza project is
hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with oversight
over the software developed by the Apache Samza Project; and be it
further
RESOLVED, that the office of "Vice President, Apache Samza" is hereby
terminated; and be it further
RESOLVED, that the Apache Samza PMC is hereby terminated.
Reference :
https://lists.apache.org/thread/jhzx3q7351wxzx74pcorqcosp7ypynv2
Special Order 7B, Terminate the Apache Samza Project, was
tabled.
C. Establish the Apache Fory 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 fast multi-language serialization framework
powered by JIT and zero-copy.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Fory Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Fory be and hereby is responsible for the
creation and maintenance of software related to fast multi-language
serialization framework powered by JIT and zero-copy; and be it further
RESOLVED, that the office of "Vice President, Apache Fory" 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 Fory
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Fory 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 Fory Project:
* Zili Chen <tison@apache.org>
* Hao Ding <xuanwo@apache.org>
* PJ Fanning <fanningpj@apache.org>
* Pan Li <pandalee@apache.org>
* Yu Li <liyu@apache.org>
* Mingyang Liu <twice@apache.org>
* Enrico Olivelli <eolivelli@apache.org>
* Weipeng Wang <wangweipeng@apache.org>
* Xin Wang <xinwang@apache.org>
* Chaokun Yang <chaokunyang@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chaokun Yang be appointed
to the office of Vice President, Apache Fory, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7C, Establish the Apache Fory Project, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Whimsy Project Chair
WHEREAS, the Board of Directors heretofore appointed Shane Curcuru
(curcuru) to the office of Vice President, Apache Whimsy, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Shane Curcuru from the office of Vice President, Apache Whimsy, and
WHEREAS, the Project Management Committee of the Apache Whimsy project
has chosen by vote to recommend Dave Fisher (wave) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Shane Curcuru is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Whimsy, and
BE IT FURTHER RESOLVED, that Dave Fisher be and hereby is appointed to
the office of Vice President, Apache Whimsy, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7D, Change the Apache Whimsy Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Sander: follow up about projected timeline for logo
[ Logo Development 2025-04-16 ]
Status: Done as per report.
* Rich: resolve the ComDev mission discrepancy
[ Community Development 2025-05-21 ]
Status: Done ... ish.
https://lists.apache.org/thread/t4ottj10n7xh1fg0pwccys004lm6yof6
Can't seem to find references to the reorg or re-chartering
that was vaguely remembered in discussion. If someone can
provide some more concrete pointers, that would be great.
Meanwhile, I agree that the "scope" of comdev has been
(intentionally?) vague for a long time, and that gives lots of
room for community-facing work to be done. This can be both
good and bad. Bad because it can tend to be a dumping ground
for "Oh, ComDev will handle that" when in reality we lack the
hands-on-deck to do much of that work.
* Justin: follow up with Libcloud PMC
[ Libcloud 2025-05-21 ]
Status: Done (twice now), but no real response from the PMC.
* Jim: follow up with Pinot PMC about PMC Chair change
[ Pinot 2025-05-21 ]
Status: COMPLETED
* Greg: broad reminder for PMC terminology
[ Pinot 2025-05-21 ]
Status:
* Kanchana: follow up with Samza PMC about change in PMC Chair
[ Samza 2025-05-21 ]
Status: Tried connecting with PMC chair and failed. I think the path
forward here is attic
* Jim: speak with VP Legal about reducing exposure to risk
[ Policies for Foundation internal venues 2025-05-21 ]
Status: ONGOING
* Zili: follow up with IoTDB PMC about project updates
[ IoTDB 2025-06-18 ]
Status: DONE See also
https://lists.apache.org/thread/m2qb837oc64lvh612p27svshfrw1fwvq
Timecho fellows agree to be more inclusive. We'd keep an eye
on its follow-ups.
* Jim: discuss Attic with PMC
[ Olingo 2025-06-18 ]
Status: COMPLETED
* Jim: coordinate with Portals PMC to find out more about potential Eclipse
[ Portals 2025-06-18 ]
Status: ON GOING
* Rich: pursue a roll call for SIS PMC
[ SIS 2025-06-18 ]
Status: DONE I neglected this until today, the day of the meeting, so
no response has been received yet. See
https://lists.apache.org/list?private@sis.apache.org:2025-6
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 21:59 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period June 2025
* ISSUES FOR THE BOARD
Recent interactions with the IoTDB PMC have raised concerns regarding the
independence of the PMC. The board is asked to review the current operation of
IoTDB PMC and take any action the board considers appropriate.
* OPERATIONS
- Responded to one report of potential phishing via sites using ASF marks
- Responded to requests to use the TOMCAT, SPARK and KAFKA logos
- The process of renaming FURY to FORY is complete
- Approved FLUSS and GEAFLOW as a project names
- Provided advice so someone looking to sell swag with ASF marks
- Provided advice to DORIS regarding how to resolve a perception of
(lack of) project independence issue
- AIRFLOW was added to the list of registered marks
- A request to use the IoTDB mark for an event was denied due to a date
conflict
- Strongly recommended that the current reorganisation of some Jakarta EE
related projects resulted in the GERONIMO name no longer being used.
* REGISTRATIONS
Worked with counsel to maintain the CLOUDSTACK registration in the US.
Worked with counsel regarding the possible transfer of the BIFROMQ marks.
Worked with counsel to renew the MADLIB mark in China.
Worked with counsel to renew HBASE, CTAKES, MANIFOLDCF and TOMCAT in the US.
* INFRINGEMENTS
No further progress regarding the downstream vendor with multiple
infringements of ASF marks.
Started to make progress regarding a potential infringement of PDFBOX.
The concerning content in a site potentially infringing of GUACAMOLE has been
removed. The site will be monitored for further issues.
Continued to work with the Logging PMC to resolve an issue with LOG4J usage.
The CASSANDRA PMC is making progress addressing some issues in a recent blog.
Provided advice to the KAFKA PMC regarding a potential infringement.
Discussed a 3rd party US registration with counsel that was refused in the US
due to a potential conflict with out DRUID mark.
No further progress for the GROOVY PMC addressing a potential infringement in
a GitHub project.
No progress regarding a site with a possible infringement of APISIX.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: we have not onboarded any new Sponsors during this timeframe.
b —Renewals: we have secured renewal commitment from one Platinum Sponsor.
c —Payments: 1 —New: we did not receive any new Sponsorship payments.
2a —Renewing: we received a renewal payment from one Platinum Sponsor
(upgraded).
2b —Incoming: we await payment from one Platinum and one Gold Sponsor,
plus payment for a partial Sponsorship-year (prior to their mid-year
renewal/upgrade).
2) Targeted Sponsors: we are exploring possible options for recognizing
organizations that support ASF Projects (directly or via third party service)
—this is separate from our existing Targeted Sponsors who provide in-kind
donations that are a) administered by ASF Infrastructure and b) benefit the
ASF as a whole or a named Project.
3) Sponsor Relations: our standing engagement continues; the Q2 call with Gold
and Platinum Sponsors at the end of June focused on Foundation updates and
Community Over Code (both Asia and North America). We're also coordinating a
variety of Fundraising campaigns with some Sponsors.
4) Event Sponsorship: we continue to promote 2025 Community Over Code events,
and handle sponsorship agreements and coordinate invoicing for North America.
We are promoting bundled sponsorship benefits for ASF Gold and Platinum
Sponsors (offered for the first time)
https://communityovercode.org/asf-sponsorship-discounts/ .
5) Individual Donations and Corporate Giving: we received $1,830 in individual
online donations via https://donate.apache.org/ . We received $2,500 as a
corporate contribution from an existing ASF Sponsor.
6) Administrivia: our work with the ASF Treasury, Accounting, Events, and
Marketing & Publicity teams continue to progress smoothly.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* Issued May edition of Plus One newsletter; delayed timing by one week to
ensure TLP and Community Over Code announcements could be included
* Issued June edition of Plus One newsletter touting CoC schedule, keynotes
and other key ASF updates
* Developed and published blog detailing United Nations Office for Digital and
Emerging Technologies (UN ODET) hackathon
* Developed social media graphics for fundraising campaign to highlight
sponsors
* Drafted Sponsor Marketing Kit and shared with Fundraising team
Project Comms
* Finalized and issued press release announcing two new TLPs: Gravitano and
StormCrawler
* Announced jclouds as an attic project in the June newsletter
Digital
* Continued coordination with infra team for self-hosting the Plus One
Newsletter vs. using the existing WordPress infrastructure
* Updated website to include Bluesky icon and Community Over Code Asia banner;
working on cohesive branding between all C/C events
* Continuous optimization of Google Ads campaign for C/C NA
Foundation Content
* Finalized social media offboarding workflow for attic’d projects; received
first request upon jclouds being attic’d
* FY25 annual report data mining continued; largely focused on uncovering
details from board meeting minutes
* Enlisted semiotics consultant to deliver a comprehensive report for the top
logo candidate selected by members
* Sent logo requirements to graphic designer; delivered updated logo options
to the logo development committee
* Drafted survey for Foundation members to provide input on M&P services and
strategies
Social Media Overview
The highest performing pieces of content were project release news, including
the weekly roundup posted every Friday on LinkedIn. Engagement for the month
represented 100% increase over May.
Social Highlights (X + LinkedIn + Bluesky)
* Total Audience: 143,544
* New Followers in June: 550
* X: 90
* Bluesky: 54
* LinkedIn: 406
* Total Posts: 87
* X: 31
* Bluesky: 31
* LinkedIn: 14
* Total Engagements: 3,043
Website Analytics
* 690,733 visits, 690,573 unique visitors -16.3%
* 3 min 14s average visit duration (level)
* 57% visits have bounced (left the website after one page) +11.8%
* 6.3 actions (page views, downloads, outlinks, internal site searches) per
visit +23.5%
* 3,921,493 pageviews, 879,628 unique pageviews +9.1%
* 2 total searches on your website, 1 unique keywords -50%
* 159,427 downloads, 113,091 unique downloads -45.5%
* 258,219 outlinks, 178,366 unique outlinks -11%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Danny Angus]
General
=======
The Infrastructure team continues to operate at reduced staffing.
Low staffing levels continue to cause delays with operational and
policy tasks (such as MFA) due to the need for prioritization of
day-to-day operations.
Lack of outgoing DKIM signing has been identified as a cause for mail
rejection to Hotmail and other Outlook-based domains. A solution is
being tested.
Finances
========
No major finance updates.
MFA Efforts
===========
Infra, Security, and Tooling continue to coordinate on next steps.
Keycloak does not provide a robust PAT framework, so we are now
evaluating Zitadel as a possible replacement that has a better UI/UX
and some level of PAT support. A POC related to Zitadel is expected by
end of July.
Major Projects
==============
DKIM signing -- Infra is preparing to roll out DKIM signing for
outgoing mail with a late July target, pending final testing.
Dockerhub Self Service -- Infra is preparing to roll out self-serve
features for Dockerhub, including repo creation and team management.
Deployment has moved to late summer due to operational priorities
around upgrading SVN to support Tooling.
Subversion upgrade -- Infra is testing the new replacement SVN server,
in conjunction with Tooling. Target migration date remains mid-July.
Testing is underway for a possible Jira and Confluence cloud
migration. See January/February board reports for further details
about this effort.
-----------------------------------------
Attachment 5: Report from the VP of Tooling [Dave Fisher]
# Tooling
The team continues to work hard building systems and playing well with others.
## Operations
### Apache Trusted Releases
We completed a round of updates to the ATR Alpha and have improved Candidate
checks and Voting process.
We've started on a Python CLI Client to the Server API endpoints. This will
enable RMs, GitHub workflows, and the general public to interact with the ATR.
We continued our research on the ASF project count, and while one could
interpret our results as there being at least 1023 "projects". After a
conversation on members@ the conclusion is that many of these are best thought
of as "products'. We will make an explicit or implicit identification of
products part of the ATR. There are PMCs that may release dozens of products
in a release. We will be able to accommodate this.
### Board Agenda Tool
The Vice Chair used the tool to run last month's Board Meeting. This allowed
attendees to follow as they navigated through the Agenda. The experience was
improved.
We have much of the editing capabilities completed, but due to the security
model in BAT we need to wait for Infrastructure to complete a software update
and migration of the ASF's svn servers. This is nearly completed.
### Workbench
No progress to report this month.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
We have obtained additional sponsorship revenue, in the form of one new silver
and bronze sponsorships, each. One potential gold sponsor has withdrawn.
The AV contract has been finalized. I have met with Cvent, our registration
vendor, to discuss using them for CFP and mobile app functionality. Our
current CFP vendor, Sessionize, has been fantastic, but having two separate
systems is not exactly efficient.
-----------------------------------------
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
------------------------
One visa applicant denied and another still waiting. Everything else
is booked and ready to go.
Community Over Code NA
------------------------
Applications for North America (Minneapolis) closed, and we had the
judges call on the 15th of June. The judges accepted 17 of out 26
applications and activity is under way for those that need visas.
Hotels are mostly booked, Flights will start to be booked over the
next couple of weeks.
Monthly Meetings
================
The next meeting will be held first week of August.
TAC App
=======
TAC app is currently closed.
Future Events
=============
None currently.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support. Post surveys
for Bratislava, Hangzhou and Denver still to be done.
Mailing List Activity
=====================
Judges call notification but nothing else this month.
Membership
==========
No changes to the Committee this month.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno]
Nothing to report this month.
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
# General
There are no issues that need urgent attention.
## Privacy Committee
The _privacy committee_ are volunteers actively working for more privacy
within the ASF. There are four members of the Privacy committee.
## Privacy complaints / Removal requests
We received 7 requests since the last report in March 2025, three of which
came in directly to vp-privacy.
## Data Privacy Policies
There are seven Data Privacy policies listed on the policies page:
https://privacy.apache.org/policies/
The website policy was ratified by the board in January 2023 and the
other six policies are all in DRAFT form.
### Telemetry Usage in Downloaded/Installed Software
At the end of 2024 the Apache Airflow project initiated a discussion about
the collection of telemetry data in installed Airflow instances. As a
result of that discussion a DRAFT policy was developed:
https://privacy.apache.org/policies/privacy-products-policy-medium.html
Airflow recently revived that discussion seeking clarity on what the ASF
policy is for their use-case and the committee is working with them on this
with the aim of having a ratified policy that they can comply with.
## Matomo
The ASF started hosting its own Matomo instance in March 2022 to provide
analytics for project websites that respected user's privacy:
https://analytics.apache.org/
Currently, 69 Matomo _Tracking Codes_ have been issued, 11 since the start of
2025. There are 7 Matomo sites that don't receive traffic at this point.
Seven projects that were not using the Matomo tracking code generated for them
were contacted in March to remind them that they were available for their use.
This resulted in one projected starting to use Matomo.
#### Responsibility for the Matomo VM
Infra will take over the responsibility for the Matomo VM.
The current progress is tracked here:
https://issues.apache.org/jira/browse/INFRA-26367
## New services
A request to be able to use "dynamic images" from pepy.tech was received and
the process to consider whether we want to sign a DPA with that Org is being
considered.
## Content Security Policy
The Infrastructure team implemented a _Content Security Policy_ (CSP) at the
start of March 2025 which prevents project websites from using trackers or
loading resources which are not permitted by the ASF Privacy Policy.
Quite a few projects have issues to fix due to external resources that are
now blocked by the CSP. There have been discussions around some external usage
and whether they could be permitted under the Privacy Policy (e.g. sign a DPA)
or provide a technical solution that would make usage compliant.
## Analytics Usage Campaign
The _Privacy Committee_ receives a monthly report of ASF websites that utilise
external trackers/analytics that are not permitted by the _Privacy Policy_.
From December 2023 to January 2025, the number of ASF websites using
proscribed analytics had reduced from 113 to 103 (-9%).
In January 2025 the _Privacy Committee_ started a campaign to encourage
projects to remove those analytics.
The number of websites using proscribed analytics on the monthly report has
now reduced to 9 (-91% since January 2025).
# Open tasks
- Provide guidelines for advertising user mailing lists
- Create a list of WordPress sites
- Create a list of domains that are allowed to connect because a DPA is covering it (improved Whimsy support)
- Better documentation about DPAs
- Add "canned responses" and instructions on how to run the privacy office to
the website
- Investigate TAC for data privacy and develop a targeted version for the committee
- Clarify responsibility for the Matomo VM
https://lists.apache.org/thread/6c7dn3ot494pxdlfxfn1pngbcpzj5g08
https://issues.apache.org/jira/browse/INFRA-25432
- Clarify status of "donate.apache.org"
- Clarify status of "status.apache.org"
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
EU - Cyber Resilience Act
Open Regulatory Working group work going well (& growing, passed 50 members)
with issues and edge cases either getting more specific in general. And also
seeing an influx of new stakeholders and re-explaining the basics which is
good. Some (expected) confusion that originates from the difference of how
USA law is written (common law) that is prevalent in the world of software
versus the Napoleonic code basis used in international and EU law.
No sign yet of the corrigendum/clarification on fines (having it is nice - as
it significantly simplifies the various FAQs on the CRA).
Minutes from the most recent expert meeting arrived with no surprises.
No surprises/concerns w.r.t. to the adjacent streams (interop, AI,
Product strict liability, etc)
EU - 1025 update (standardisation regulation)
As a USA organisation - we are not directly submitting an opinion at this
time - but contributing to the letter by Open Forum Europe.
Main points are that the ESO processes are increasingly a bottle-neck; from
speed to access to (paid for) standard. Yet also becoming essential for (open
source) software implementors to comply with rules and regulation. And that
open source is, for software, by far the dominant way by which any standards
actually become viable/visible in the market place. So the system needs
revising; and be patterned, or at least be conductive to, on open-source
software and open standards processes. And that it is in the interest of
policy makers to do so - as otherwise SMEs and open source software makers
either vote with their feet (and you do not have anything left to make policy
for) or innovation and commerce grinds to a halt.
EU - Expert Group for a Technology Roadmap on Encryption
There is an EU call out for an Expert Group for a Technology Roadmap on
Encryption:
https://ec.europa.eu/transparency/expert-groups-register/screen/expert-groups/consult?lang=en&groupID=4005
for which it is quite key to get actual experts that can realistically &
technically explain the mathematica and other limits of what is possible with
regard to things such as legal-intercept backdoors & the (virtually zero
realistic) ability of society to constraining the use of cryptography of bad
actors.
-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz]
* The ECMA General Assembly has officially confirmed the ASF as a full
member[1]. We now have full voting rights within the organization.
* The CycloneDX OSS Sustainability Workgroup is transitioning into a new task
group (TG4), provisionally named "Dugnar"[2].
* The estimated delivery timeline for TG1 Transparency Exchange API has been
revised, with completion now targeted for June 2026.
* Unfortunately, my recent call for volunteers[3] to represent the ASF in TG3
(Common Lifecycle Enumeration) and the upcoming TG4 (Dugnar) did not receive
any responses. At present, we have no ASF representatives participating in
these task groups.
[1] https://ecma-international.org/news/ecma-international-welcomes-new-members-9/
[2] https://docs.google.com/document/d/1Dlfq1vp2xXDN1oeUPVGffMEtagUUH1CQ2jWOTg4H9UE/edit?tab=t.0#heading=h.si64e7edhupe
[3] https://lists.apache.org/thread/jg342k6h0gvxykldv8cwjpd6mfjonz78
-----------------------------------------
Attachment 12: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
-----------------------------------------
Attachment 14: Report from the Apache Security Team Project [Mark J. Cox]
June
* To encourage the use of MFA at the ASF, we split the scope of that
project into phases and defined the first phase,
https://cwiki.apache.org/confluence/display/INFRA/MFA+project+phase+1%3A+Security
Stats for June 2025:
28 [license confusion]
11 [report/question relating to dependencies]
22 [support request/question not security notification]
Security reports: 77 (last months: 80, 63, 75)
24 ['website or other infrastructure']
8 ['tomcat']
5 ['httpd', 'superset']
4 ['airflow']
3 ['zeppelin']
2 ['jena', 'kafka', 'pekko']
1 ['apisix', 'devlake', 'doris', 'druid', 'flink', 'gravitino', 'guacamole', 'hadoop', 'hertzbeat', 'hop', 'jackrabbit', 'kylin', 'myfaces', 'nifi', 'ofbiz', 'openoffice', 'ozhera', 'qpid', 'rocketmq', 'seata', 'spark', 'struts']
In total, as of 1st July 2025, we're tracking 194 (last months: 214,
216) open issues across 70 projects, median age 115 days (last months:
97, 98). 67 of those issues have CVE names assigned. 21 (last month:
17) of these issues, across 9 projects, are older than 365 days.
* geode (Health red): Four issues in Geode over 365 days old. The
project has voted to move to the Attic, but there might be a chance
of revisiting that decision if relevant stakeholders successfully
join the effort. (Last update: 2025-06-20)
* openoffice (Health red): Several issues in OpenOffice are over 365
days old. They are not severe enough to warrant stopping
distribution of OpenOffice, and there is progress on finding an
architectural improvement to fix them, but we actively work to
improve the projects' ability to respond to security issues going
forward. (Last update: 2025-06-26)
* zeppelin (Health red): The project is still struggling with triage,
fixes, releases, and providing timely updates. (Last update:
2025-06-25)
* fineract (Health amber): the PMC has been attempting to engage more
of the wider Fineract ecosystem to help triage, fix and release
security issues, but with limited effect so far. (Last update:
2025-06-26)
* spark (Health amber): the project is not responsive to security
issues (Last update: 2025-06-26)
-----------------------------------------
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 with High Activity
Issues for the board: None
## Membership Data:
Apache Accumulo was founded 2012-03-20 (13 years ago)
There are currently 44 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.
- John Kucera was added as committer on 2025-06-04
## Project Activity:
The primary Accumulo project activity continues to remain focused on work
towards 2.1.4, 3.1, and 4.0 releases. The test release candidate 2.1.4-rc0
was created 2025-04-02.
### Accumulo Fluo.
As reported in the May update[1] the functionality of the fluo.apache.org
website has been restored.
There is no update on the INFRA Jira ticket[2] to perform the necessary
disposition tasks of the Fluo PMC permissions/groups/memberships and assign
permissions to the Accumulo PMC. 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 activity remains consistent. The
email traffic reflects the community preference of using GitHub projects and
issues for PRs discussions. We also use our slack channel for day-to-day
communications. We continue to use the mailing list for official Apache
business and it remains a channel for users to contact us.
## Links
[1] https://lists.apache.org/thread/ykg68x8t38012on2glcvy0b5w0q6p5zt
[2] https://issues.apache.org/jira/browse/INFRA-26799
-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project [Christopher L. Shannon]
## Description:
The mission of Apache ActiveMQ is the creation and maintenance of software
implementing a distributed messaging system
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ActiveMQ was founded 2007-01-16 (18 years ago)
There are currently 64 committers and 30 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 Matt Pavlovich on 2023-12-06.
- No new committers. Last addition was Anton Roskvist on 2024-02-09.
## Project Activity:
### ActiveMQ Classic
- 6.1.7 was released on 2025-06-22
- ActiveMQ Classic is heading to 6.2.0 release with new JMS 3.1 features
support
### ActiveMQ Artemis
- 2.41.0 was released on 2025-04-29
- 2.42.0 release is imminent
- Work is progressing toward 3.0
### ActiveMQ Artemis Console
- 1.2.1 was released on 2025-07-01
### ActiveMQ CPP
- Work has been done by the community to bring the C++ client up to date with
C++17 compliance and is heading towards a 3.9.6 release.
## Community Health:
We have a sustained activity on the mailing lists (for both Artemis and
Classic). We also see new contributors who submitted new PRs. On Classic, we
are moving forward on JMS 3.1 and preparing a proposal for runtime for
ActiveMQ 7. We will also start a discussion about rKahaDB within the
community.
-----------------------------------------
Attachment C: Report from the Apache Airavata Project [Suresh Marru]
## Description:
The mission of Apache Airavata is the creation and maintenance of software
related to executing and managing computational jobs on a distributed computing
resources, including local clusters, supercomputers, national grids, academic
and commercial clouds.
## Project Status:
Current project status: The community is energized and healthy. Recently
inducted committers and PMC members are proactively making the code
repositories more welcoming while technically improving the usefulness of
the project. Issues for the board: No issues to report.
## Membership Data:
Apache Airavata was founded 2012-09-18 (13 years ago)
There are currently 46 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Yasith Jayawardana was added to the PMC on 2025-04-06
- Ganning Xu was added as committer on 2025-04-09
## Project Activity:
Over the years, the Airavata code base has fragmented into 22 git repositories
to achieve modularity and make the project loosely integrated major
components, but this led to unwarranted proliferation. The current activity is
to condense the code into five repositories, deprecated, not actively used
code modules, and refactoring the actively developed components. By next
quarter, this is expected to be completed.
## Community Health:
Five Google Summer of Code students are actively contributing, and the
community is mentoring them effectively. By the end of summer, we are expecting
a significant overhaul of code navigation and documentation.
-----------------------------------------
Attachment D: Report from the Apache Answer Project [Ning Qi]
## Description:
The mission of Apache Answer is the creation and maintenance of software
related to A Q-and-A platform software for teams at any scales
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Answer was founded 2024-12-18 (7 months ago)
There are currently 18 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Anne Zhu on 2024-12-18.
- No new committers were added.
## Project Activity:
- Final 1.4-series update — Released v1.4.5, closing out the 1.4.x branch with
stability and security fixes.
- Major feature release — Shipped v1.5.0, introducing several headline
capabilities.
- Maintenance follow-up — Published v1.5.1 to address early feedback and minor
regressions from 1.5.0.
- Next milestone planning — Actively scoping and prioritizing features for the
upcoming v1.6.x series; discussion threads are open on dev@ and the public
roadmap has been drafted for community review.
## Community Health:
- Broader contributor base — Welcomed 3 new code contributors and 7 new
translation contributors, further diversifying both the feature pipeline and
language support.
- Improved communication practices — To align with ASF guidelines and increase
transparency, we’re shifting the bulk of design and development discussions
from GitHub Issues to the dev@answer.apache.org mailing list.
-----------------------------------------
Attachment E: Report from the Apache Ant Project [Jan Materne]
## Description:
The mission of Apache Ant is the creation and maintenance of the Ant
build
system and related software components.
It consists of the following main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
## Project Status:
Current project status: Primarily in bug fix mode and maintenance
mode.
Issues for the board: None for now.
## Membership Data:
Apache Ant was founded 2002-11-18 (22 years ago)
There are currently 29 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Magesh Umasankar on
2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-15.
Our current PMC chairman Jan Materne has expressed his desire to step
down from this role. We want to thank Jan for his service over the
past
years. Right now we are in the process of deciding whom to recommend
as
his successor and plan to propose a resolution to replace him in time
for the August board meeting.
## Project Activity:
The primary goal of Ant these days is to make sure that it can be used
to build projects using recent releases of Java. Ant 1.10.15 was
released on 29th August 2024 and that's our latest version of Ant.
Ivy 2.5.3 has been released on 23rd December 2024 which is our latest
version of Ivy.
Both Ant and Ivy have seen some development activity this quarter but
right now no new release has been discussed.
## Community Health:
Although we don't see too much development activity in Ant,
there are several active users of the Ant build tool. We
occasionally also see pull requests on GitHub.
For a project that's in maintenance mode, our amount of
activity, we believe, is decent.
-----------------------------------------
Attachment F: Report from the Apache APISIX Project [Ming Wen]
## Description:
The mission of Apache APISIX is the creation and maintenance of software
related to a cloud-native microservices API gateway
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache APISIX was founded 2020-07-15 (5 years ago)
There are currently 65 committers and 31 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 Ashish Tiwari on 2024-10-16.
- Yilia Lin was added as committer on 2025-06-03
## Project Activity:
apisix-ingress-controller 2.0.0-rc was released on 2025-07-02.
3.13.0 was released on 2025-06-27.
apisix-java-plugin-runner-0.6.0 was released on 2025-04-10.
3.12.0 was released on 2025-04-01.
## Community Health:
The community remains active.
The latest release 3.13 introduces new AI-related capabilities,
enabling engineers using Apache APISIX to
handle not only traditional API traffic
but also AI and LLM (Large Language Model) traffic.
Previously, the Apache APISIX Dashboard project
had compatibility issues with the APISIX project.
In the newly released version 3.13,
the redesigned Dashboard has been included,
allowing developers to manage APISIX through a more user-friendly UI.
The Apache APISIX Ingress Controller project
now offers more complete support for the Gateway API.
These new features and iterations
improve the developer experience with Apache APISIX.
-----------------------------------------
Attachment G: Report from the Apache Aries Project [Christian Schneider]
## Description:
Apache Aries software is a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Project Status:
Current project status: Largely maintenance mode with some developments ongoing.
Issues for the board: No issues at the moment.
## Membership Data:
Apache Aries was founded 2010-12-15 (14 years ago)
There are currently 56 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Carlos Sierra Andrés on 2018-07-03.
- No new committers. Last addition was Romain Manni-Bucau on 2020-01-29.
## Project Activity:
Major release of OSGi typed events.
We are working on cleaning up old subprojects that are not used anymore and
updating the maintained project builds. Major kudos to Dominik for doing most
of this work.
## Community Health:
Some increased activity but only from very few contributors.
We aborted the merge with Felix for now as there was not much support
from Felix project to go forward with this.
-----------------------------------------
Attachment H: Report from the Apache Arrow Project [Neal Richardson]
## Description:
The mission of Apache Arrow is the creation and maintenance of software related
to columnar in-memory processing and data interchange
## Project Status:
Current project status: Ongoing (high activity)
Issues for the board: none
## Membership Data:
Apache Arrow was founded 2016-01-19 (9 years ago)
There are currently 115 committers and 58 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Alenka Frim was added to the PMC on 2025-06-30
- No new committers. Last addition was Matthijs Brobbel on 2025-03-24.
## Project Activity:
### Community events
We will be holding an Arrow summit in October 2025, co-located with the PyData
Paris conference. ASF Trademarks & Brand Management has approved. The PMC has
selected a conference selection committee to review submissions, which are
currently open. [1]
### Splitting projects out of the monorepo
With many implementations in apache/arrow, the maintenance/release costs for
apache/arrow is high. So we’re extracting some implementations from
apache/arrow to apache/arrow-*
#### JavaScript
We extracted the JavaScript implementation from apache/arrow to
apache/arrow-js for ease of maintenance and releasing. We have released Apache
Arrow JavaScript from apache/arrow-js, which means that we completed the
extraction. We’ll be able to maintain/release the JavaScript implementation in
apache/arrow-js.
#### Swift
We also extracted the Swift implementation from apache/arrow-swift and have
released Apache Arrow Swift from apache/arrow-swift. Going forward, we will
maintain/release the Swift implementation in apache/arrow-swift.
#### C#
We reached consensus to extract the C# implementation from apache/arrow to
apache/arrow-dotnet, but we haven’t done it yet. We’ll do it this year.
#### Skyhook
We merged Skyhook, a Ceph integration, in 2022, but it is no longer
maintained. So we’ll extract it from apache/arrow to apache/arrow-skyhook.
### Tooling/LLMs
We’ve seen strong uptake of the Kapa.ai documentation assistant (~850
queries/month), which is helping users discover relevant docs and resolve
common questions without needing to open issues or join mailing lists.
There is renewed interest in community health tooling—such as dashboards
[2] tracking stale issues and unmaintained components—driven by a desire to
improve contributor visibility and sustainability.
That dashboard also makes use of an LLM to provide a summary of dev mailing
list traffic, which was used to help draft the following highlights:
### Intervals and Standards Alignment
The Iceberg community has proposed a new 128-bit ANSI SQL-compatible interval
type. Arrow contributors are considering whether this should be adopted
natively or handled as an extension type. This work is part of broader efforts
to ensure Arrow remains compatible with evolving lakehouse and SQL engine
standards.
The community is also discussing a proposal to canonicalize the variant
extension type across Arrow implementations. This would improve cross-language
interoperability for mixed-type columns (e.g., from Parquet). Contributors are
weighing whether Arrow should define and maintain a standard set of extension
types going forward.
### CI & Infrastructure
Thanks to newly granted AWS credits, we are expanding our CI and benchmarking
infrastructure. This includes adding GPU runners, improving performance
tracking, and supporting larger-memory workloads. These improvements are
expected to improve release robustness and enable performance monitoring
across languages.
### Benchmarks
Several contributors are working to make benchmarking more visible and
comparable across C++, Python, and R. This includes discussions around
standardized benchmark suites and dashboards to detect regressions
earlier—motivated in part by recent performance issues observed in Arrow R
19.x and 20.x.
### Recent Releases:
ADBC-19 was released on 2025-07-07.
SWIFT-21.0.0 was released on 2025-07-07.
JS-21.0.0 was released on 2025-07-04.
NANOARROW-0.7.0 was released on 2025-07-03.
RS-55.2.0 was released on 2025-06-26.
GO-18.3.1 was released on 2025-06-20.
RS-OS-0.12.2 was released on 2025-06-10.
JAVA-18.3.0 was released on 2025-05-13.
RS-55.1.0 was released on 2025-05-13.
RS-OS-0.12.1 was released on 2025-05-13.
GO-18.3.0 was released on 2025-05-09.
ADBC-18 was released on 2025-05-06.
20.0.0 was released on 2025-04-26.
RS-55.0.0 was released on 2025-04-11.
## Community Health:
Based on mailing list volume, project activity remains steady. While messages
on the dev mailing list dipped slightly, messages on the user list more than
doubled. And GitHub activity is up 25% over last quarter.
Metrics:
* builds@arrow.apache.org had a 3% decrease in traffic in the past quarter
(247 emails compared to 253)
* dev@arrow.apache.org had a 12% decrease in traffic in the past quarter (408
emails compared to 460)
* github@arrow.apache.org had a 25% increase in traffic in the past quarter
(16152 emails compared to 12911)
* issues@arrow.apache.org had a 38% increase in traffic in the past quarter
(1597 emails compared to 1150)
* user@arrow.apache.org had a 124% increase in traffic in the past quarter
(191 emails compared to 85)
[1]: https://sessionize.com/arrow-summit-2025/
[2]: https://arrow-maintenance.github.io/arrowdash/
-----------------------------------------
Attachment I: Report from the Apache AsterixDB Project [Ian Maxon]
## Description:
The mission of AsterixDB is the creation and maintenance of software related to
open source Big Data Management System
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache AsterixDB was founded 2016-04-19 (9 years ago)
There are currently 42 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Wail Y. Alkowaileet on 2023-11-21.
- Preetham Poluparthi was added as committer on 2025-04-09
## Project Activity:
Releases:
- Apache AsterixDB JDBC Driver 0.9.8.3 was released on 2024-04-03.
- apache-asterixdb-0.9.8.2 was released on 2024-03-04.
- apache-asterixdb-0.9.9 was released on 2024-03-04.
APEs:
- APE 20 (Multi-statement queries) underwent a nice discussion and is in the
process of being adopted. Technically it would fall under the expedited
process as well but since there were many comments I suggested it should
have a separate vote thread.
- APE 21 (Transform function keyword) was adopted and merged.
- APE 22 (Sparse column suport) and 23 (Multisegmented page 0 support)
recieved enough votes and were adopted and merged in via the expedited
process. There was also a little discussion about the details of the
proposal.
## Community Health:
APE is in my view starting to finally take firm root. None of the new APEs this
reporting period ended up in the trap that some had been falling into
previously, where the code itself was merged before the APE was posted to start
a discussion among everyone and not just the folks closest to that part of the
system. Sometimes the APEs themselves have some discussions before the proposal
itself and I have been encouraging committers to leave the draft as rough as
possible as to drive the discussion and commentary that follows about improving
the proposal onto the list.
I have also been encouraging folks when they have a question about how part of
the system works, rather than asking someone directly, to post it to dev@ and
then perhaps bring that post to their attention, if they don't otherwise see it.
This way more knowledge and discussion about things only a few people know can
be brought into the open.
There are again no entirely new contributors this period that I am aware of,
however some of the new ones from years past are now becoming very integral
to the project. One is in the process of becoming a committer, and another is
well on that path.
-----------------------------------------
Attachment J: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
The mission of Apache Atlas is the creation and maintenance of software related
to a scalable and extensible set of core foundational governance services -
enabling enterprises to effectively and efficiently meet their compliance
requirements
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache Atlas was founded 2017-06-21 (8 years ago)
There are currently 49 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pinal Shah on 2025-01-30.
- No new committers. Last addition was Chaitali Borole on 2024-10-07.
## Project Activity:
- updated Impala hook to capture lineage for SQL queries having WITH clause
- code readability improvements in Impala hook module
- optimization in incremental export
- performance improvements in entity-create, edge retrieval, notification
processing
- fixed handling of Ozone path references in Hive queries
- Spark notification processing performance improvements
- UI fixes and improvements
- upgraded versions of dependent components: DOMPurify, Swagger-UI, netty,
commons-io, axios, spring-ldap-core
- docker setup improvements
- WIP to support RDBM as backend store, instead of HBase/Cassandra
## Community Health:
- dev@atlas.apache.org had a 9% increase in traffic in the past quarter (501
emails compared to 456)
- user@atlas.apache.org had a 125% increase in traffic in the past quarter (9
emails compared to 4)
- 55 JIRA tickets opened and 31 closed in the past quarter.
- 50 commits in past 4 months (99 in the last report)
- 14 code contributors in past 4 months (16 in the last report)
## Recent releases:
- Apache Atlas 2.4.0 was released on 2025-01-04.
- Apache Atlas 2.3.0 was released on 2022-12-06.
- Apache Atlas 2.2.0 was released on 2021-08-17.
- Apache Atlas 2.1.0 was released on 2020-07-15.
-----------------------------------------
Attachment K: Report from the Apache Attic Project [Hervé Boutemy]
## Description:
The mission of Attic is the creation and maintenance of a home for dormant
projects.
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Attic was founded 2008-11-19 (17 years ago)
There are currently 19 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Niall Pemberton on 2025-04-04.
- No new committers. Last addition was Niall Pemberton on 2025-04-04.
## Project Activity:
Attic finished retiring 2 projects from previous quarter: Mnemonic and Gora,
and is currently retiring one project for this quarter: jclouds.
Privacy updates for retired project's websites have been completed.
Google Analytics was removed from 28 websites and rendering issues caused
by the CSP were fixed in 11 websites.
A lot of work has been done this quarter on Attic site modernization:
- we migrated source code to Git and CI to GH Actions,
- we migrated HTML rendering to Markdown + Jekyll.
The new site https://attic.apache.org/ is not only better looking, but it's
easier to maintain and eases our process to retire projects, as automation
has been improved a lot.
We also added M&P social media step to the retirement process: jclouds is the
first project that is applying this new step. We're learning from this
experience on all the coordination it requires between retired project, Attic
and M&P in addition to the technical hurdles.
## Community Health:
A lot has been done by the 3 most active contributors of Attic: let's hope that
modernization will permit attracting more contributors in the future.
-----------------------------------------
Attachment L: Report from the Apache Avro Project [Ryan Skraba]
-----------------------------------------
Attachment M: Report from the Apache bRPC Project [James Ge]
## Description:
The mission of Apache bRPC is the creation and maintenance of software related
to an industrial-grade RPC framework for building reliable and high-performance
services
## Project Status:
Current project status: ONGOING
Issues for the board: NONE
## Membership Data:
Apache bRPC was founded 2022-12-21 (3 years ago)
There are currently 21 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Guangming Chen on 2025-01-06.
- No new committers. Last addition was Yang Liming on 2024-03-24.
## Project Activity:
bRPC v1.13.0 was released on 2025-05-19 with the following new features:
- Support ProtoJson formatted http body
- support dynamic update method concurrency
- Support various payload of baidu-std: json, proto-json and proto-text
- Support AddressSanitizer
- Support keep session info in RedisConnContext
## Community Health:
We created a maillist at issues@brpc.apache.org to filter out issue-related
emails and make the brpc maillist more focused on inner discussions between
developers. Committers take turns responding user emails and issues on a
weekly basis.
-----------------------------------------
Attachment N: Report from the Apache BVal Project [Matthew Jason Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache BVal was founded 2012-02-14 (13 years ago)
There are currently 17 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Markus Jung on 2024-07-08.
## Project Activity:
bval-3.0.2 was released on 2025-03-13. Subsequent activity has been limited
to automated dependency upgrades.
## Community Health:
As per usual, Apache BVal continues to operate on a maintenance/skeleton
crew basis; we consider this "as expected" for a project whose purpose is
to implement a specification, the evolution of which follows a waterfall
lifecycle.
-----------------------------------------
Attachment O: Report from the Apache Calcite Project [Ruben Q L]
## Description:
Apache Calcite is a highly customizable framework for parsing and planning
queries on data in a wide variety of formats. It allows database-like access,
and in particular a SQL interface and advanced query optimization, for data
not residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for building
local and remote JDBC and ODBC database drivers. Avatica has an independent
release schedule and its own repository.
## Project Status:
Current project status: ongoing (high activity)
Issues for the board: none
## Membership Data:
Apache Calcite was founded 2015-10-22 (10 years ago)
There are currently 78 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- Xiong Duan was added to the PMC on 2025-03-29
- Alessandro Solimando was added to the PMC on 2025-05-01
- Zhen Chen was added as committer on 2025-05-19
## Project Activity:
Apache Calcite 1.40.0 was released on 2025-05-28. It contained contributions
from 20 contributors, and resolved 102 issues. The highlights of this release
were the addition of several improvements and additional optimization rules
(notably advanced set operation handling with new rules for converting
INTERSECT to semi-joins and EXISTS subqueries, MINUS to anti-joins and
filters, and optimizing UNIONs with common sources); join optimization is
improved through predicate expansion from disjunctions and specialized
handling of complex join conditions; additional optimizations include new
rules for MIN/MAX aggregates and smarter filter-sort interactions; addition of
Doris, DuckDB, SQLite, and Trino dialects, as well as improved support for
ClickHouse; support for aliases referencing lateral columns; and support for
defining which rule sets to apply for individual Quidem tests.
## Community Health:
The community continues on a "Super healthy" status. Looking at the metrics,
we have seen a small decrease (13%) in traffic on the dev mailing list, but a
small increase (14%) in traffic on the issues mailing list (with 150 JIRA
tickets opened and 146 closed in this quarter), which indicates less
discussion on the dev list, but still a significant amount of activity going
on in terms of contributions.
It is also worth noting that some of our most recent committers start to
appear on our "top reviewers" list, which means that new members of the
community are taking responsibility and helping out on this particular task,
where we traditionally struggle.
The number of non-committer (contributor) commits per month:
+------+-------+---------------------+
| year | month | contributor_commits |
+------+-------+---------------------+
| 2025 | 4 | 42 |
| 2025 | 5 | 27 |
| 2025 | 6 | 19 |
+------+-------+---------------------+
The number of active reviewers per month:
+------+-------+------------------+
| year | month | active_reviewers |
+------+-------+------------------+
| 2025 | 4 | 6 |
| 2025 | 5 | 7 |
| 2025 | 6 | 6 |
+------+-------+------------------+
Top reviewers in the last 3 months:
+---------------+---------+
| committer | reviews |
+---------------+---------+
| Mihai Budiu | 52 |
| NobiGo | 15 |
| Cancai Cai | 5 |
| Jensen | 5 |
| suibianwanwan | 3 |
+---------------+---------+
-----------------------------------------
Attachment P: Report from the Apache CarbonData Project [Jacky Li]
-----------------------------------------
Attachment Q: Report from the Apache Causeway Project [Jörg Rade]
## Description:
The mission of Causeway is the creation and maintenance of software related to
Framework for rapidly developing domain-driven apps in Java
## Project Status:
Current project status: This is a mature project and the framework is
generally stable. Issues for the board: None. Last quarter we reported on an
issue with Algolia search, but this has been addressed after privacy@a.o
approved Algolia for use and Infra effected the necessary change.
## Membership Data:
Apache Causeway was founded 2012-10-17 (13 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Martin Hesse on 2023-07-05.
- No new committers. Last addition was Martin Hesse on 2023-07-04.
## Project Activity:
In this quarter we released Causeway 3.4.0 (based on Spring Boot 3.5) [1], in
keeping with our regular release cadence. This was mostly a maintenance
release (bug fixes and dependency upgrades).
We have also started work on a v4 branch, targeting Spring Boot 4 which will
be released in Nov 25.
## Community Health:
We continue to promote the framework to extend our user base. Dan and Johan
presented at Spring.io in Barcelona in May [2]. An article about Causeway is
planned for javapro.io in the autumn [3].
[1] https://causeway.apache.org/relnotes/latest/2025/3.4.0/relnotes.html
[2] https://s.apache.org/owy27
[3] https://javapro.io/
-----------------------------------------
Attachment R: Report from the Apache Celix Project [Pepijn Noltes]
-----------------------------------------
Attachment S: Report from the Apache CXF Project [Andriy Redko]
## Description:
Apache CXF is an open source services framework. CXF helps you build and
develop services using frontend programming APIs, like JAX-WS and JAX-RS.
These services can speak a variety of protocols such as SOAP, XML/HTTP,
RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS
or JBI.
There is also a sub-project that leverages CXF:
Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache CXF was founded 2008-04-15 (17 years ago)
There are currently 44 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Andy McCright on 2019-02-24.
- No new committers. Last addition was Jamie Mark Goodyear on 2024-07-19.
## Project Activity:
Most of the activity for this period is put into kicking off Jakarta EE
11 platform support (the initial pull request is out). We are awaiting
the next milestones for Spring Framework 7 and Spring Boot 4 in order to
finalize the 4.2.x feature set (along with Jakarta EE 11 compatibility).
Recent releases:
3.6.7 was released on 2025-05-23.
4.0.8 was released on 2025-05-23.
4.1.2 was released on 2025-05-23.
Apache CXF Fediz 1.7.1 was released on 2025-04-10.
## Community Health:
For the most part, the project is making steady, but not stellar, progress.
Many of the protocols and specs that CXF implements are mature specs and don't
really change much. Thus, steady progress and regular releases are a good
thing. We are responding to bug reports, reviewing and merging pull requests,
and hopefully getting patch releases out soon.
The Jakarta EE 10 TCK tests are now passing. The focus has shifted
towards Jakarta EE 11 support (4.2.x release line) since the final
specs are released.
-----------------------------------------
Attachment T: Report from the Apache DataFu Project [Eyal Allweil]
-----------------------------------------
Attachment U: Report from the Apache DB Project [Bryan Pendleton]
## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software licensed
to the Foundation, for distribution at no charge to the public.
The Apache DB TLP consists of the following subprojects:
o Derby : a relational database implemented entirely in Java.
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache DB was founded 2002-07-16 (23 years ago)
There are currently 48 committers and 46 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 Max Philipp Wriedt on 2024-07-03.
- No new committers. Last addition was Max Philipp Wriedt on 2023-04-14.
## Project Activity:
DB project activity was steady but quiet this spring. Each of
the DB project communities continued planned work while addressing
queries and contributions from the community.
Recent releases:
Torque 6.0 was released on 2024-05-22.
Derby-10.17.1.0 was released on 2023-11-14.
The JDO community received a vulnerability report from security
regarding JDOHelper.getPersistenceManagerFactory. The community
evaluated the report with the assistance of the PMC and responded
to the reporter with their analysis.
The Torque community continue their discussions about possibly
switching their source control tooling to git. There is no
clear consensus yet so no switch has been made, nor ruled out.
Meanwhile the Torque community continue to resolve open issues.
The JDO community continued their work on the 3.2.2 release.
No critical features or bug fixes have been identified. During
this quarter, the JDO web site was updated based on advice
from Infrastructure that simplifies publishing the site.
The Derby community have recently been working to ensure Derby
compatibility with recent releases of Java. Derby changes to
be compatible with OpenJDK 24 were completed in the late winter
under DERBY-7171, and Derby changes to be compatible with
OpenJDK 25 were active during the spring under DERBY-7175.
## Community Health:
Community health across all three Apache DB communities
was low, but not atypically so. None of the communities
reported any concern about project health, and the DB PMC
remains active and engaged across all three communities.
-----------------------------------------
Attachment V: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap various CDI containers.
- JSF integration
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Testing support to allow low level unit testing of CDI enabled projects.
## Issues:
Development picked up speed again and site got improvemed as well.
As noted the last time we do not see a lack of PMC member activity on the
mailing list. We had 5 PMC members join the discussion about which parts
of DS we want to keep in the future. That's more than enough to do a
release. So while I agree that there was a phase of low activity, I
do not see that it is time for the attic.
Discussions to form a JavaEE umbrella project to host DeltaSpike and
a few other EE spec implementations + Geronimo parts did not yet take
place due to time constraints on my side. This will happen during the summer.
## Community changes, past quarter:
- No new PMC members. Last addition was Harald Wellmann on 2016-05-19.
- Thomas Frühbeck was added as committer on 2024-02-05
## Recent releases:
- 2.0.0 (Jakarta) was released on 2024-04-10.
- 1.9.6 was released on 2022-04-12.
- 1.9.5 was released on 2021-03-10.
-----------------------------------------
Attachment W: Report from the Apache Directory Project [Shawn McKinney]
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely written in
Java, which has been certified LDAPv3 compatible by the Open Group.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
This is a "schema aware” API with some convenient ways to access all types
of LDAP servers.
- Studio: A complete directory tooling platform intended to be used with any
LDAP server however it is particularly designed for use with ApacheDS. It is
an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based authorization platform that provides role-based
access control, delegated administration and password policy services with
an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains various tools
to access and manage kerberos principals and keytabs. It provides a rich,
intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.
- Mavibot: An embeddable key-value database library with MVCC (Multi Version
Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Project Status:
Current project status:Nothing has changed from the last report. The
subprojects are being maintained with one exception noted below. A small crew
remains responsive on the mailing lists, merging PR's, active on JIRA. Several
projects are due for a release and one has initiated a vote.
Issues for the board: No issues to report at this time.
## Membership Data:
Apache Directory was founded 2005-02-22 (20 years ago)
There are currently 57 committers and 17 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 Brian Demers on 2023-10-23.
- No new committers. Last addition was Fredrik Roubert on 2023-07-10.
## Project Activity:
Per sub-project:
- ApacheDS: low activity. Release in the works.
- LDAP API: low activity.
- Studio: low activity. Need someone to step up after previous maintainer's
departure from the project. Recenctly a PMC member has offered to do this.
- Fortress: low activity. A maintenance release in underway. There is work to
get off ehcache, which has numerous CVE's, but it is a big change and will
require a major release.
- Kerby: low activity.
- Mavibot: low activity.
- SCIMple: low activity. Needs to get a release out soon.
## Community Health:
As stated earlier, the project activity is low with most of it realized via
pull requests. The PMC remains responsive.
-----------------------------------------
Attachment X: Report from the Apache DolphinScheduler Project [Lidong Dai]
## Description:
Apache DolphinScheduler is a cloud-native workflow orchestration platform with
powerful user interface, dedicated to solving complex task dependencies in the
data pipeline and providing various types of jobs available `out of the box`
## Project Status:
Current project status:Health issues for the board: There are no issues for
the board at this time
## Membership Data:
Apache DolphinScheduler was founded 2021-03-17 (4 years ago)
There are currently 59 committee members and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Xin Cheng was added to the PMC on 2024-06-18
- Hengliang Tan was added as committee on 2024-07-02
## Project Activity:
- 3.3.0-alpha was released on 2025-04-09.
- 3.2.2 was released on 2024-07-18.
## Community Health:
- We have held one community online Meetups in last quarter.
- dev@dolphinscheduler.apache.org had a 5% increase
-----------------------------------------
Attachment Y: Report from the Apache Druid Project [Abhishek Agarwal]
Report date: 2025-07-11
## Description
Apache Druid is a high performance real-time analytics database. It is
designed for workflows where low-latency query and ingest are the main
requirements. It implements ingestion, storage, and querying subsystems. Users
interface with Druid through built-in SQL and JSON APIs, as well as
third-party applications.
Druid has an extensive web of connections with other Apache projects: Calcite
for SQL planning, Curator and ZooKeeper for coordination, Kafka, Hadoop and Iceberg as
data sources, Avro, ORC, or Parquet as supported data input formats, and
DataSketches for scalable approximate algorithms. Druid can also be used as a
data source by Superset.
## Issues
There are no issues requiring board attention at this time.
## Activity
Our last major release was Druid 33.0.0, which contained 190 new features, bug
fixes, performance enhancements, documentation improvements, and additional test
coverage from 44 contributors. Druid typically does major releases 3–4 times a year.
The major release for 33.0.0 was less than 3 months ago, and that too resulted in
slightly lower volume of contributor in this release.
Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,223
members, up 117 members (~4%) since our last report. This is our most active
channel for user support and usage-oriented discussions. Development discussions
happen more on GitHub, and to some degree on the dev mailing list. The growth is consistent
with what we have seen in the previous quarters.
We have also rotated the PMC chair for the first time, and elected Abhishek Agarwal
as the new chair. We have also decided to rotate the chair every year.
After consultation with community, we have started work to improve our security posture
by dropping support for older java versions and removing integrations not compatible with
these older java versions.
## Membership data
Apache Druid was founded 2019-12-17 (5 years ago)
There are currently 73 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Cece Mei was added as committer on 2025-06-04
- Phua Guan Wei was added as committer on 2025-06-04
- Jesse Tuğlu was added as committer on 2025-06-11
We sent an invitation to become committer to to Jan Werner,
who is yet to create an Apache Id.
## Recent releases
- 33.0.0, a major release, on 2025-04-29.
- 32.0.1, a patch release, on 2025-03-19.
- 31.0.2, a patch release, on 2025-03-19.
## Development activity by the numbers
Since the last report on 1st April:
- 264 commits from 36 contributors
- 336 pull requests opened
- 293 pull requests merged/closed
The numbers show an healthy uptick in contributions compared to the previous board report. There
is a drop in number of unique contributors but the volume of contributions have grown. We
added more committers as compared to the past quarter so as to recognise their efforts
and encourage them to continue contributing. We will continue to keep an eye for potential
committers in the project.
-----------------------------------------
Attachment Z: Report from the Apache Dubbo Project [Jun Liu]
## Description:
The mission of Apache Dubbo is the creation and maintenance of software related
to a high-performance, lightweight, java based RPC framework.
## Project Status:
Current project status: Ongoing: With high activity.
Issues for the board: No issue needs board attention.
## Membership Data:
Apache Dubbo was founded 2019-05-15 (6 years ago)
There are currently 116 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 Sean Yang on 2025-01-10.
- Liang He was added as committer on 2025-07-13
- Zeya Fang was added as committer on 2025-06-05
- Yu Yu was added as committer on 2025-07-11
- Wei Lao was added as committer on 2025-06-05
## Project Activity:
The community has just achieved a significant milestone on
apache/dubbo-kubernetes. The first milestone release of the
apache/dubbo-kubernetes project is now ready, including the dubboctl cli tool,
helm package, and dubbo-cp control plane image. These will be released as part
of the Dubbo microservice control plane system, providing enhanced management
and control capabilities for microservices built on Dubbo.
Apache/Dubbo has mainly focused on stability enhancements, and we have
recently released several bugfix versions of 3.3.x.
Other community activities and events:
1. The Google Summer of Code is currently progressing smoothly, and we will
conduct a summary during the mid-term report.
2. We will deliver about four Dubbo-related speeches at the CoC Asia
conference held in Beijing at the end of July
## Community Health:
From several perspectives, the community is highly active, with projects such
as apache/dubbo and apache/dubbo-kubernetes having very active issue/pr
records.
Although several PMC members have seen their participation decrease recently
due to various reasons, the project quickly had other core developers step in
to replace them, enabling them to continue to effectively advance various
community matters. The continuity of these matters has been maintained very
well.The majority of maintainers' decrease in activity is temporary, during
which other maintainers in the community receive more opportunities for
exercise
-----------------------------------------
Attachment AA: Report from the Apache Fineract Project [James Dailey]
## Description:
The mission of Apache Fineract is the creation and maintenance of software
related to a core banking platform that provides a reliable, robust, and
affordable solution for entrepreneurs, financial institutions, and service
providers to offer financial services to the world's underbanked and unbanked.
## Project Status:
Current project status: Active
Issues for the board: No public issues
## Membership Data:
Apache Fineract was founded 2017-04-18 (8 years ago)
There are currently 55 committers and 24 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 Adam Saghy on 2023-07-10.
- Adam Monsen was added as committer on 2025-05-16
## Project Activity:
The last release was in January 2025 and another one is planned for July 2025.
Discussion has begun on creating a better way to onboard users and
contributors - by having: 1) AdminUI part of the Fineract project rather than
only the one available from an outside vendor, 2) better documentation of the
APIs, and 3) better roadmap discussions on list.
These are still very nascent and echo themes in previous reports.
## Community Health:
The "broader" community has no issue with the vendor holding a key role in the
community.
A few contributors will be attending the Community Over Code conference North
America this Sept.
-----------------------------------------
Attachment AB: Report from the Apache Flagon Project [Joshua C. Poore]
## Description:
The mission of Apache Flagon is the creation and maintenance of software
related to thin-client behavioral logging capability useful for business
analytics, usage analytics, usability and user testing
## Project Status:
Current project status: Ongoing with healthy community participation
Issues for the board: No issues at this time
## Membership Data:
Apache Flagon was founded 2023-03-21 (2 years ago)
There are currently 19 committers and 12 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 Evan Jones on 2024-07-10.
- No new committers. Last addition was Ryan Thenhaus on 2025-02-08.
## Project Activity:
Project activity has been healthy in that the community has been steadily
working together on maintenance or new features. Newer PMC members have done
well in recruiting new contributors during this time. They have invested their
time in supporting projects that both maintain the projects and bolster the
community. First, the community discussed and completed a major migration to a
monorepo structure, which has been useful for expediting new onboarding for
contributors. Second, community members have taken it upon themselves to
address and updating our website, which is still underway. Finally, current
PMC members and new contributors addressed modernizing elements of UserALE's
browser plugin deployment methodology, migrating to Manifest v 3.
## Community Health:
Getting organic communication to occur within Apache lists remains
challenging, although some members of the community started running a weekly
synch earlier in the year. This did set some objectives that the community
started organizing around from a development standpoint. I also find that for
larger decisions (e.g., monorepo) about product direction, those discussions
are at least raised on lists before initiative is taken. For straightforward
maintenance issues, we see more individual or small group initiative to
address issues (e.g., Mv3 and Website). Notwithstanding, we are seeing some
new growth in that two contributors have shown interest in becoming
committers--there are VOTEs ongoing on private as of the date of this report.
In the next two quarters, I suspect PMC will open discussions on other
functional areas of the project, including additional back-end examples and
examples for integration with other instrumentation and telemetry packages, as
well as a push toward adopting firmer standards in logging that are consistent
with other communities (e.g., OpenTelemetry).
-----------------------------------------
Attachment AC: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment AD: Report from the Apache Fluo Project [Keith Turner]
## Description:
The mission of Apache Fluo is the creation and maintenance of software related
to the storage and incremental processing of large data sets
## Project Status:
Current project status: Dissolved (awaiting INFRA)
Issues for the board: The Fluo PMC was dissolved by a previous board
resolution, but remains "on the books", pending the resolution of the INFRA
actions at https://issues.apache.org/jira/browse/INFRA-26799. See the Accumulo
PMC report for more.
## Membership Data:
Apache Fluo was founded 2017-07-18 (8 years ago)
There are currently 15 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Brian Frank Loss on 2022-02-01.
- No new committers. Last addition was Brian Frank Loss on 2022-02-02.
## Project Activity:
This project was transitioned to the Accumulo PMC. See that PMC's report for
relevant project activity information.
## Community Health:
This project was transitioned to the Accumulo PMC. See that PMC's report for
relevant community health information.
-----------------------------------------
Attachment AE: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AF: Report from the Apache Gravitino Project [Jerry Shao]
## Description:
The mission of Apache Gravitino is the creation and maintenance of software
related to managing your data and AI assets seamlessly with a flexible,
unified governance framework, including lakehouse federation capabilities
## Project Status:
Current project status: New Issues for the board: none.
## Membership Data:
Apache Gravitino was founded 2025-05-21 (2 months ago) There are currently 27
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- Chenxi Pan was added as committer on 2025-07-07
- Eric Chang was added as committer on 2025-05-30
## Project Activity:
1. A new maintenance release (0.9.1) is onging.
2. The next major release (1.0.0) will be code-frozen by the end of July, and
ship in August.
Recent developments on Gravitino:
- Metadata authentication, features are actively developed on dev branch
(80%).
- Cache system is almost done (90%).
- Policy system, the API interface is merged, the following PRs are ongoing.
- Statistics system, the API interface is merged, other parts are onging.
- Job system, the API interface is proposed and get reviewed.
## Community Health:
1. A new maintenance release (0.9.1) is onging.
2. 72 issues were resolved in last 30 days; 109 issues were created in last 30
days.
3. 124 PRs were merged in last 30 days, 130 PRs were created in last 30 days.
4. dev@gravitino.apache.org had a 335% increase in traffic in the past quarter
(231 emails compared to 53)
-----------------------------------------
Attachment AG: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment AH: Report from the Apache Hadoop Project [Xiaoqiao He]
## Description:
The mission of Hadoop is the creation and maintenance of software related to
Distributed computing platform
## Project Status:
Current project status: Ongoing Issues for the board: None
## Membership Data:
Apache Hadoop was founded 2008-01-16 (17 years ago) There are currently 248
committers and 125 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 Shilun Fan on 2023-10-31.
- Jian Zhang was added as committer on 2025-03-10.
## Project Activity:
hadoop-thirdparty-1.4.0 was released on 2025-03-27.
3.4.1 was released on 2024-10-18.
3.4.0 was released on 2024-03-17.
## Community Health:
- JDK17 Compatibility & JUnit5 Migration Over the past three months,
approximately 95% of Hadoop modules have been successfully migrated from
JUnit4 to JUnit5, resolving many test failures caused by JDK17
incompatibilities[1]. The core module hadoop-common[2] has been fully
upgraded. Ongoing migration efforts are focused on hadoop-azure[3],
hadoop-aws[4], and hadoop-hdfs[5], with additional fixes expected soon. We
anticipate completing the full JUnit5 migration by end of July, and aim for
full JDK17 compatibility by end of September. Additionally, Hadoop now
compiles successfully with JDK21, thanks to these ongoing efforts.
- Initial Work on JDK23/JDK24 Early-stage work for JDK23 and JDK24 [6] has
started. Some relevant JIRAs have been opened and initial patches
submitted.
- ARM Compilation Fixes In the hadoop-3.4.1 release process, build issues on
ARM (related to Python2[7] and PhantomJS[8]) were identified and have now
been resolved.
- New HDFS Feature: Asynchronous Router RPC Development of the Asynchronous
Router RPC feature is in progress under HDFS-17716 [9], targeting inclusion
in Hadoop 3.5.0.
- YARN CGroup v2 Support Support for CGroup v2 in YARN[10] is nearly complete
and is planned for release in Hadoop 3.5.0.
- Windows Build and Test Enhancement Improvements to Hadoop’s build and test
process on Windows are underway, with some initial progress made.
- The release of Hadoop 3.4.2 is currently being prepared[11].
- The Project shows healthy engagement based on Mailing list/JIRA/Github
traffic.
[1] https://issues.apache.org/jira/browse/HADOOP-17177
[2] https://issues.apache.org/jira/browse/HADOOP-19413
[3] https://issues.apache.org/jira/browse/HADOOP-19425
[4] https://issues.apache.org/jira/browse/HADOOP-19424
[5] https://issues.apache.org/jira/browse/HDFS-12431
[6] https://issues.apache.org/jira/browse/HADOOP-19486
[7] https://issues.apache.org/jira/browse/YARN-11712
[8] https://issues.apache.org/jira/browse/YARN-11713
[9] https://issues.apache.org/jira/browse/HDFS-17716
[10] https://issues.apache.org/jira/browse/YARN-11669
[11] https://lists.apache.org/thread/mxrx4gm2hb5mx551znyk1bzgxctlh41f
-----------------------------------------
Attachment AI: Report from the Apache HBase Project [Duo Zhang]
## Description:
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of rows
with millions of columns atop non-specialized hardware.
hbase-thirdparty is a set of internal artifacts used by the project to
mitigate the impact of our dependency choices on the wider ecosystem.
hbase-connectors is a collection of integration points with other projects.
The initial release includes artifacts for use with Apache Kafka and Apache
Spark.
hbase-filesystem contains HBase project-specific implementations of the Apache
Hadoop FileSystem API. It is currently experimental and internal to the
project.
hbase-operator-tools is a collection of tools for HBase operators. Now it is
mainly for hosting HBCK2.
hbase-native-client is a client library in C/C++, in its early days.
hbase-kustomize is for deploying HBase on kubernetes, still under development.
## Project Status:
Current project status: Ongoing
Issues for the board:
## Membership Data:
Apache HBase was founded 2010-04-21 (15 years ago)
There are currently 112 committers and 62 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 Nihal Jain on 2025-02-02.
- Charles Connell was added as committer on 2025-06-12
- Chandra Kambham was added as committer on 2025-06-12
- Junegunn Choi was added as committer on 2025-06-12
- Peng Lu was added as committer on 2025-06-12
- Dávid Paksy was added as committer on 2025-06-13
## Project Activity:
hbase-thirdparty-4.1.11 was released on 2025-05-31.
After fixing several issues, we got a successful 10B ITBLL run on branch-3,
which is a big step for our final 3.0.0 release.
https://issues.apache.org/jira/browse/HBASE-27919
https://lists.apache.org/thread/j9z17zonrzqq8x12tndskh4tyblcgjmy
We started working on moving up to jetty 12, and also dealing with the
breaking changes in newer JDK version.
https://lists.apache.org/thread/bkrfm705kqd3bqzyvo7jv46t6p64x2n5
## Community Health:
- dev@hbase.apache.org:
962 subscribers(966 in the previous quarter)
452 emails sent to list(542 in the previous quarter)
- user@hbase.apache.org:
1978 subscribers(1983 in the previous quarter)
20 emails sent to list(35 in the previous quarter)
- user-zh@hbase.apache.org
81 subscribers(81 in the previous quarter)
11 emails sent to list(11 in the previous quarter)
We lowered the bar of committer nomination and added 5 new committers at once.
We finally finished a 10B ITBLL run on branch-3 which means the stability is
enough for cutting the final 3.0.0 release. This is a big progress. We are
optimistic that we can see the final 3.0.0 release in the near future.
-----------------------------------------
Attachment AJ: Report from the Apache Hive Project [Naveen Gangam]
## Description:
The mission of Hive is the creation and maintenance of software related to Data
warehouse infrastructure using the Apache Hadoop Database
## Project Status:
Current project status: Apache Hive project remains fairly active with new
feature and new releases being planned.
Issues for the board: No issues to report that require board attention at this
point in time.
## Membership Data:
Apache Hive was founded 2010-09-21 (15 years ago)
There are currently 111 committers and 56 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 Zhihua Deng on 2024-10-11.
- No new committers. Last addition was Dmitriy Fingerman on 2024-11-12.
## Project Activity:
4.1.0 release is nearly complete. Aiming for RC vote end of week.
Recent releases:
4.0.1 was released on 2024-10-02.
2.3.10 was released on 2024-05-09.
4.0.0 was released on 2024-03-29.
Jira Activity: 187 JIRA tickets opened and 425 closed in the past quarter. 127
resolved in the last month, 78 new jiras opened our of which 40 have been
resolved already.
## Community Health:
Overall the Apache Hive community is fairly healthy with increased activity in
email, commits, jiras, releases.
-----------------------------------------
Attachment AK: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for July 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 May, podlings executed 7
distinct releases, and one IP clearance occurred.
Several incubating proposals have been discussed, and we have two new
podlings, GeaFlow and Fluss. No projects graduated last month. Apache Fury
completed its name change to Apache Fory and is up for graduation this
month. Nemo has retired, but a couple of more podlings are in discussion
about retiring. A new project, Debo, was discussed, but it's probably too
early for graduation. One person was added to the IPMC, and two asked to be
removed.
Three podlings failed to report and will be asked to report next month.
Conversations on the list have been focused on releases, new incubating
projects, and mentor involvement. There was also discussion of mentor
onboarding and offboarding, and creation of a mentor onboarding document
and an update to mentor best practices.
Tracking projects that have been incubating for a long time, it looks like
the IPMC will retire Annotator, and Toree is slowly moving towards
graduation. The Livy PPMC had a positive roll call and is also slowly
moving towards graduation. NLPCraft appears to have an inactive PPMC and
community, and it would be beneficial to discuss retirement. Training is
discussing graduation.
## Community
### New IPMC members:
- Ian Maxon
### People who left the IPMC:
- Myrle Krantz
- Nathan Hartman
## New Podlings
- GeaFlow
- Fluss
## Podlings that failed to report, expected next month
- Annotator
- KIE
- Ponymail
## Graduations
- None
The board has motions for the following:
- Fory
## Releases
The following releases entered distribution during the month of
June:
- Fory 0.11.0
- Fory 0.11.1
- Gluten 1.4.0
- Seata 2.4.0
- Stormcrawler-3.3.0
- Teaclave Trustzone SDK 0.4.0
- XTable 0.3.0
## IP Clearance
- OpenDAL Reqsign
## Legal / Trademarks
N/A
## Infrastructure
N/A
## Table of Contents
[Amoro](#amoro)
[BifroMQ](#bifromq)
[Burr](#burr)
[Fluss](#fluss)
[Gluten](#gluten)
[Hamilton](#hamilton)
[HertzBeat](#hertzbeat)
[HugeGraph](#hugegraph)
[Iggy](#iggy)
[Livy](#livy)
[Pegasus](#pegasus)
[PouchDB](#pouchdb)
[ResilientDB](#resilientdb)
[Teaclave](#teaclave)
[Texera](#texera)
--------------------
## 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 4 new contributors
### How has the project developed since the last report?
* Released Amoro 0.8.0-incubating
* Merged 40+ PRs
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2025-05-08, released Amoro 0.8.0-incubating
### When were the last committers or PPMC members elected?
2025-06-09, PPMC member:Wang Tao(GitHub ID: Aireed)
### 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) Justn Mclean
Comments:
- [ ] (amoro) Zhongyi Tan
Comments:
- [X] (amoro) Yu Li
Comments: Good to see new contributor and PPMC member joining, as
well as new release published.
- [X] (amoro) Xinyu Zhou
Comments:
- [X] (amoro) Kent Yao
Comments: Nice to have new PPMC on board
### IPMC/Shepherd notes:
--------------------
## BifroMQ
BifroMQ is a Java-based, high-performance, distributed MQTT broker with
native multi-tenancy support, designed for large-scale connections and
message delivery.
BifroMQ has been incubating since 2025-04-22.
### Three most important unfinished issues to address before graduating:
1. The first incubator release
2. Community growth
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
* Migrated the official website to ASF infrastructure and updated the
contents to comply with ASF requirements.
* Published roadmap on the website to address common concerns from
potential contributors.
### How has the project developed since the last report?
We are still working on the first incubator release, but have completed the
following tasks:
* Added license headers to all source files and set up a corresponding CI
action for checking
* Updated LICENSE and NOTICE files with third-party dependency information
for both source and binary distributions
* Renamed all Java packages to `org.apache.bifromq.*`
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-02-25
### When were the last committers or PPMC members elected?
None since joining the incubator
### Have your mentors been helpful and responsive?
Yes, we get helpful and timely guidance from the mentors
### Is the PPMC managing the podling's brand / trademarks?
The transfer of BifroMQ’s trademark is in progress.
### Signed-off-by:
- [X] (bifromq) Christofer Dutz
Comments: So far not much discussion has been happening on any of the
mailing-lists.
- [ ] (bifromq) Xiangdong Huang
Comments:
- [X] (bifromq) Calvin Kirs
Comments: Things are going well, The new website looks great.
- [ ] (bifromq) Penghui Li
Comments:
- [ ] (bifromq) Sheng Wu
Comments:
### IPMC/Shepherd notes:
--------------------
## Burr
Burr is a lightweight in-process python framework that standardizes the
expression and execution of state machines as action-driven graphs, while
making graph execution easily observable. It is particularly suited for AI
agent workflows, simulations, and other dynamic systems, and comes with a
self-hostable observability UI that integrates with OpenTelemetry.
Burr has been incubating since 2025-05-24.
### Three most important unfinished issues to address before graduating:
1. Publish docs
2. Publish a release
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
N/A
### How has the community developed since the last report?
N/A
### How has the project developed since the last report?
Still setting up.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release -- current status
- [ ] 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?
Yes - responsive. On us PMC to get the ball rolling faster.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (burr) Kevin Ratnasekera
Comments:
- [X] (burr) Ayush Saxena
Comments: Setting up the project
- [X] (burr) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## Fluss
Fluss is a streaming storage built for real-time analytics which can serve
as the real-time data layer for Lakehouse architectures.
Fluss has been incubating since 2025-06-04.
### Three most important unfinished issues to address before graduating:
1. Ensure website and code are full compliance with ASF policie
2. Publish the first release under the ASF incubator
3. Grow the community and fill out the maturity model
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
We are still in the setup phase, but we have seen some active contributors
that deserved to be committer candidates.
Jark Wu is going to Flink Forward Asia 2025 (Singapore) to present Fluss on
July 3rd.
### How has the project developed since the last report?
The community is developing for the next release v0.8 which is expected to
be released at September.
The community has established the Fluss Improvement Proposal (FIP) process
[1] to facilitate design discussions for major features. Currently, there
are already five FIPs in progress.
[1]
https://cwiki.apache.org/confluence/display/FLUSS/Fluss+Improvement+Proposal
s
### 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:
We are still in the process of initial setup. We have migrated the GitHub
repository and website to the Apache organization. We will set up the CI/CD
pipelines to streamline future development and deployment.
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
N/A
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
N/A
### Signed-off-by:
- [X] (fluss) Jean-Baptiste Onofré
Comments: Good work on the initial setup. Congrats !
- [ ] (fluss) Becket Qin
Comments:
- [X] (fluss) Yu Li
Comments: Initial setup is completed and look forward to the further
development of the project.
- [X] (fluss) Jingsong Lee
Comments:
- [X] (fluss) Zili Chen
Comments:
### IPMC/Shepherd notes:
--------------------
## Gluten
Gluten is a middle layer responsible for offloading JVM-based SQL engines'
execution to native engines.
Gluten has been incubating since 2024-01-11.
### Three most important unfinished issues to address before graduating:
1. Apache Official Release: Quarterly publish Apache Official Release
2. Enhanced User Experience to update the latest documentations to the
site
3. Community Growth
### Are there any issues that the IPMC or ASF Board need to be aware of?
N/A
### How has the community developed since the last report?
* The number of fork is from 474 to 552.
* The number of star is from 1310 to 1379.
* The number of contributors is from 163 to 170.
* Add 4 new committers, currently with total 42 committers.
* Regular Monthly Meeting Minutes(May):
https://docs.google.com/document/d/1g-veyoNB1QYFJY4-TMdewAq8wMkQqltbEt46CPxB
rfE/edit?usp=sharing
### How has the project developed since the last report?
* Gluten 1.4.0 has been released as 4th Apache release(major update) on
Jun. 19th 2025.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [*] Nearing graduation
- [ ] Other:
### Date of last release:
2025-06-19
### When were the last committers or PPMC members elected?
2025-05-26 for vote result published
### Have your mentors been helpful and responsive?
Yes, they remain actively engaged with the project and provide valuable
input, such as reminders about the release process and insights into the
overall health of the community.
### Is the PPMC managing the podling's brand / trademarks?
Yes, everything is fine.
### Signed-off-by:
- [X] (gluten) Yu Li
Comments: Good to see new committers joining and new release
published. The community is built in a good shape.
- [X] (gluten) Wenli Zhang
Comments:
- [ ] (gluten) Kent Yao
Comments: Looks good to me for seeing new reliable releases
- [X] (gluten) Shaofeng Shi
Comments: Good to see the community is growing. Maybe it is time to
discuss the graduation plan.
- [ ] (gluten) Felix Cheung
Comments:
### IPMC/Shepherd notes:
--------------------
## Hamilton
Hamilton is a lightweight in-process framework to define, execute, and
observe directed acyclic graphs (DAGs) that express data transformations. In
Hamilton, one can express complex DAGs of transformations, e.g. from
dataframe transformations (using pandas, polars, PySpark), machine learning
pipelines, through to regular software engineering API request and LLM API
based workflows. Observability hooks are built into the framework. The
Hamilton UI is a self-hostable service to capture observability output from
workflow runs.
Hamilton has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Finally publish a release
2. Publish releases of all other components
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
Organizing a meet-up in July.
### How has the project developed since the last report?
Gotten some docs out -- still missing a few ASF things.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release -- currently here.
- [ ] 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?
No answer
### Signed-off-by:
- [ ] (hamilton) Kevin Ratnasekera
Comments:
- [X] (hamilton) Ayush Saxena
Comments:
- [X] (hamilton) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## HertzBeat
HertzBeat is an easy-to-use, open source, real-time monitoring system. It
features an agentless architecture, high-performance clustering, Prometheus
compatibility, and powerful custom monitoring and status page building
capabilities.
HertzBeat has been incubating since 2024-04-05.
### Three most important unfinished issues to address before graduating:
1. Grow the community and attract more users.
### 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. Now the community total has 271 contributors, attracted 12 new
contributors since last report.
2. Two new committer and a new PPMC join the community since last report.
3. The community participated in the Google Summer of Code and OSPP.
### How has the project developed since the last report?
1. Has publish the new version 1.7.1.
2. The new version 1.7.2 is in the process of release.
3. More features and bugfix, doc update
4. In the past month, excluding merges, 18 authors have pushed 21 commits
to master and 43 commits to all branches. On master, 88 files have changed
and there have been 1,654 additions and 830 deletions.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2025-05-30
### When were the last committers or PPMC members elected?
2025-06-17
### Have your mentors been helpful and responsive?
Yes, they are very nice.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (hertzbeat) Yonglun Zhang
Comments:
- [ ] (hertzbeat) Yu Xiao
Comments:
- [X] (hertzbeat) Justn Mclean
Comments:
- [ ] (hertzbeat) Francis Chuang
Comments:
### IPMC/Shepherd notes:
--------------------
## HugeGraph
A large-scale and easy-to-use graph database
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 1 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. Completed the internal trademark approval process, now awaiting the next
steps for transferring the trademark to the ASF.
2. Submitted 8+ tasks for open-source promotional activities and delivered
2 HugeGraph-related presentations at the Conference on Open Source (COC)
Asia.
3. Elected 1 new committer, with 2 more candidates currently in the
nomination process.
### How has the project developed since the last report?
1. Actively planning the 1.7.0 release as a key preparation step before
graduation.
2. Advancing the integration of an optional proprietary vector engine to
enhance the graph database's capabilities.
3. Further refactoring and merging the distributed storage and computation
layers for better synergy and performance.
4. Restructured the documentation and enriched it with extensive
LLM-powered source code analysis to improve developer onboarding.
### 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-07-02
### Have your mentors been helpful and responsive?
YES & Thanks
### Is the PPMC managing the podling's brand / trademarks?
Waiting the next steps for transferring the trademark to the ASF
### Signed-off-by:
- [ ] (hugegraph) Lidong Dai
Comments:
- [ ] (hugegraph) Trista Pan
Comments:
- [ ] (hugegraph) Xiangdong Huang
Comments:
- [ ] (hugegraph) Yu Li
Comments:
- [ ] (hugegraph) Willem Ning Jiang
Comments:
### IPMC/Shepherd notes:
[PJF] Hopefully will push towards graduation soon
--------------------
## 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. Expand connectors / external sinks ecosystem
3. Add more documentation on iggy.apache.org as we add more features
### Are there any issues that the IPMC or ASF Board need to be aware of?
Sometimes, INFRA jira tickets taking more time. Is there a way to expedite
the process there?
### How has the community developed since the last report?
1. Discord members count approaching 450, new contributors writing
proposals (discussions), submitting PRs for fixing issues, docs,
enhancements.
2. Github stars reached 2.7K
3. Crates downloads reached 141K+
4. Presented at Craft-IT Conference (https://craft-it.pl/#session-216)
5. Scheduled to present at ApacheCon in September
### How has the project developed since the last report?
The Iggy project has made significant progress in multiple areas during the
reporting period:
* *Repository Restructure*: Transitioned the codebase to a monorepo
structure to better support modular development across server, client SDKs,
connectors, and tooling.
* *Connectors Runtime*: Implemented the initial version of the Iggy
Connectors Runtime, enabling dynamic loading of source/sink plugins and
supporting custom data transformations.
* *SDK Migration*: Migrated SDKs for multiple languages including C#, Java,
Go, Node.js, Python, and C++ to align with the monorepo architecture and
latest server capabilities.
* *Web Dashboard*: Migrated the Iggy Web UI dashboard to the new repository
structure.
* *Benchmarking Platform*: Migrated the benchmarking platform and began
preparations to host it under
[benchmarks.iggy.apache.org|http://benchmarks.iggy.apache.org].
* *CI Improvements*: Enhanced the CI/CD pipelines to handle multiple
languages and projects independently within the monorepo.
* *Zero-Copy Support*: Added zero-copy support in the server and integrated
recent server changes across all existing SDKs.
* *Rust SDK Refactor*: Refactored the Rust SDK into smaller, reusable
packages shared between server and client implementations; also updated the
Rust edition and dependencies.
* *Runtime Refactor (Experimental)*: Published an experimental branch
featuring a new runtime architecture based on _io_uring_, thread-per-core
model, and shared-nothing design.
* *BDD Test Coverage*: Introduced Behavior-Driven Development (BDD)
scenarios using Cucumber for validating SDK functionality across multiple
languages.
* *Benchmarking Enhancements*: Extended the benchmarking CLI with a
high-level SDK abstraction, added TLS support, and improved result sharing
via unique URLs.
* *Website Redesign*: Completed a major website redesign, updated brand
assets, and aligned naming conventions with Apache guidelines.
* *Release Planning*: Initiated discussions and scoping for the upcoming
v0.5.0 release (https://github.com/apache/iggy/discussions/1931)
### 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?
- There are no known brand and naming issues as reported here.
- VP, Brand approved the project name.
### Signed-off-by:
- [X] (iggy) Hao Ding
Comments:
- [X] (iggy) Yonik Seeley
Comments:
- [ ] (iggy) Zili Chen
Comments:
- [X] (iggy) Hulk Lin
Comments:
### IPMC/Shepherd notes:
--------------------
## Livy
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
### Three most important unfinished issues to address before graduating:
1. Revitalization of the Community
2. Dependable Release Cadence
3. Keep the project up to date with security fixes and in terms of Spark
support
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time. There was a recent ping of the PPMC to make sure there
were enough folks monitoring the pivate@ list which resulted in 5 +1's and
a couple 0's.
### How has the community developed since the last report?
We have received PRs and merged mostly bug fixes and smaller enhancements.
### How has the project developed since the last report?
A new PR for the upcoming release is support for the latest Spark 3.5.x has
been submitted and is currently waiting for reviews. We will need to spin
up the next release within this next quarter.
### 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:
2023-10-10
### When were the last committers or PPMC members elected?
October 2023
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
No answer
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Luciano Resende
Comments:
- [X] (livy) Jean-Baptiste Onofré
Comments: I think it would be great to have a kind of roadmap about
releases (0.8.0-incubating is two years old) and community growth (blog
post, ...).
- [ ] (livy) Madhawa Kasun Gunasekara
Comments:
- [X] (livy) Larry McCay
Comments:
- [X] (livy) György Gál
Comments:
### IPMC/Shepherd notes:
--------------------
## Pegasus
Pegasus is a distributed key-value storage system which is designed to be
simple, horizontally scalable, strongly consistent and high-performance.
Pegasus has been incubating since 2020-06-28.
### Three most important unfinished issues to address before graduating:
1. There are still about 10 documents on the official website that need
to be provided and updated.
2. Improve the stability of project builds and unit tests.
3. Make more releases in ASF policy regularly.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
We saw more active users and contributors of Apache Pegasus.
### How has the project developed since the last report?
More useful features are continuously being merged. The upcoming release is
version 2.6.0, but since two major features — support for FQDN and the
refactoring of the metrics system — are still in progress, it may take a few
more months to complete.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2023-12-12
### When were the last committers or PPMC members elected?
2024-09-26
### Have your mentors been helpful and responsive?
Yes, our mentors gave us a lot of help, including version release,
holding meetup, prepare the graduation and etc.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (pegasus) Duo zhang
Comments:
- [ ] (pegasus) Liang Chen
Comments:
- [ ] (pegasus) Von Gosling
Comments:
- [ ] (pegasus) Liu Xun
Comments:
### IPMC/Shepherd notes:
--------------------
## PouchDB
PouchDB is an open-source JavaScript database inspired by Apache CouchDB
that is designed to run well within the browser.
PouchDB has been incubating since 2025-04-15.
### Three most important unfinished issues to address before graduating:
1. Get the project up and running (no blockers)
2. Follow the graduation progression, in particular make a new release
under the ASF Incubator.
3. Grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
We are still in the setup phase, IP clearance and source import is next.
### How has the project developed since the last report?
All but two CLAs are in place, in addition, two Code Grants have been
received from the former major PouchDB contributors in preparation for
IP clearance.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
n/a
### When were the last committers or PPMC members elected?
n/a
### Have your mentors been helpful and responsive?
Helpful and proactive.
### Is the PPMC managing the podling's brand / trademarks?
N/A
### Signed-off-by:
- [X] (pouchdb) PJ Fanning
Comments:
- [ ] (pouchdb) Jean-Baptiste Onofré
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?
Add one new PPMC
### How has the project developed since the last report?
We are preparing a new rc (v1.11.0)
### 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?
2025-5-20
### Have your mentors been helpful and responsive?
One of our mentors is not touchable (email is not available).
Currently we only have two mentors, would like to add one more.
### 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) Kevin Ratnasekera
Comments:
### IPMC/Shepherd notes:
--------------------
## Teaclave
Teaclave is a universal secure computing platform, enabling writing
memory-safe trusted applications in Rust running inside Trusted Execution
Environment.
Teaclave has been incubating since 2019-08-20.
The Teaclave community is now working towards graduation.
### Three most important unfinished issues to address before graduating:
1. Complete all requirements of the Project Maturity Assessment.
2. Practice future releases by adhering to a quarterly release schedule.
3. Conduct a thorough self-assessment to ensure all Apache graduation
criteria are met.
### Are there any issues that the IPMC or ASF Board need to be aware of?
As the Teaclave community works toward graduation, we welcome guidance
along the process. We also invite any active IPMC members interested in the
project to consider becoming mentors. Thank you.
### How has the community developed since the last report?
- We have a new mentor joining the project.
- We have a new participant contributing to the project.
- We have a new release manager working on the Teaclave TrustZone SDK
v0.5.0 release.
### How has the project developed since the last report?
- Initiated releasing Teaclave TrustZone SDK v0.5.0, pending for collecting
binding votes in the general incubator mailing list.
- Working on the Teaclave Maturity Assessment. During the assessment, we
identified several areas for improvement, including the website page and
repository reorganization. Work is in progress to address these and meet
all requirements.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2025-06-03
### When were the last committers or PPMC members elected?
2025-01-21
### Have your mentors been helpful and responsive?
We have faced challenges with slow release cycles, partly due to the
limited number of binding votes from mentors. To address this, we have
invited new mentors to join the community and are actively engaging with
contributors to ensure smoother release processes. We have also reached out
to existing mentors and received positive responses and renewed support. We
plan to continue this proactive approach in future releases to ensure
timely and successful outcomes.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (teaclave) Felix Cheung
Comments:
- [ ] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
- [X] (teaclave) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## Texera
Texera is an open-source system to support collaborative data science, AI,
and ML using GUI-based workflows. Our vision is to develop a system to
support cloud platforms on which users can easily analyze data and use AI/ML
techniques provided as operators. Users with various backgrounds,
irrespective of whether they know coding or not, can collaborate on the same
project to construct a pipeline. Experienced users can use programming
languages such as Python, R, Java, and Scala to implement customized
computation logic. The platform allows users to pause the execution of a
workflow to investigate the operator states, and resume the execution at a
later time. The platform can be used by a research community to publish
valuable resources such as data sets, workflows, and ML models to share
their domain-specific knowledge and support reproducibility of scientific
research. The platform also allows users to elastically request computing
resources from public clouds for computationally-intensive tasks.
Texera has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. Complete the SGA form.
2. Donate the Texera codebase from the
[Texera/texera](https://github.com/Texera/texera) GitHub repo to the
Apache/Texera repo.
3. Set up the Apache Texera webpage http://texera.apache.org/.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
- 2025-06-12: Ian Maxon (imaxon) has been added as a Texera mentor.
- 2025-06-25: We got approval from UCI on realeasing their copyright to us.
We are finalizing the paperwork. After this, we can sign and submit the SGA
form.
- 2025-06-30: We conducucted a monthly group sync meeting, meeting minutes
and recording can be found in [this email
thread](https://lists.apache.org/thread/hq6tsnzw05c00lqgb1trwf5w31kvvzg2).
- 2025-06-30: PPMC started voting for a new PPMC member.
- 2025-06-30: There were six more contributors onboarding.
- 2025-06-30: There were four more users showing interests through other
channels. We will gradually move to use general@texera.apache.org to let
potential users contact us.
### How has the project developed since the last report?
1. Logo & Branding: Complete refresh of branding assets (**NEW LOGO!**):
- Replaced the old logo with a redesigned new version and improved logo
loading behavior. [#3481](https://github.com/Texera/texera/pull/3481),
[#3483](https://github.com/Texera/texera/pull/3483),
[#3485](https://github.com/Texera/texera/pull/3485),
[#3486](https://github.com/Texera/texera/pull/3486),
[#3487](https://github.com/Texera/texera/pull/3487)
2. Execution Engine
- Improved schema propagation.
[#3501](https://github.com/Texera/texera/pull/3501)
- Refactored messaging classes for better semantic clarity:
`ControlPayload` → Direct Control Message (DCM), `ChannelMarker` → Embedded
Control Message (ECM). [#3492](https://github.com/Texera/texera/pull/3492),
[#3472](https://github.com/Texera/texera/pull/3472)
- Enhanced execution stability and correctness.
[#3488](https://github.com/Texera/texera/pull/3488),
[#3491](https://github.com/Texera/texera/pull/3491),
[#3470](https://github.com/Texera/texera/pull/3470),
[#3471](https://github.com/Texera/texera/pull/3471),
[#3482](https://github.com/Texera/texera/pull/3482)
3. Services & Configuration
- Introduced and extended Admin Site Settings service.
[#3453](https://github.com/Texera/texera/pull/3453),
[#3480](https://github.com/Texera/texera/pull/3480),
[#3489](https://github.com/Texera/texera/pull/3489)
4. UI & Usability
- Added Parquet as a supported export format and alpha channel support
for scatter plots. [#3478](https://github.com/Texera/texera/pull/3478),
[#3498](https://github.com/Texera/texera/pull/3498)
- Improved operator usability.
[#3479](https://github.com/Texera/texera/pull/3479),
[#3411](https://github.com/Texera/texera/pull/3411)
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-04-04
### When were the last committers or PPMC members elected?
We conducted a group sync meeting on 2025-06-30 (see [email
thread](https://lists.apache.org/thread/hq6tsnzw05c00lqgb1trwf5w31kvvzg2)
for meeting minutes, slides and recordings). We discussed about adding a
new PPMC member and voting the case on email list. the vote is to be
conducted on 2025-07-03.
### Have your mentors been helpful and responsive?
Yes, our mentors have been both helpful and highly responsive, and we
sincerely appreciate their continued support throughout the incubation
process. We would especially like to thank PJ Fanning for his outstanding
guidance and active engagement. We also warmly welcome our new mentor, Ian
Maxon, and look forward to benefiting from his valuable experience with the
successful incubation of Apache AsterixDB.
### Is the PPMC managing the podling's brand / trademarks?
Texera PPMC just released a new logo for branding purpose. The [new
logo](https://github.com/Texera/texera/raw/master/core/gui/src/assets/logos/
full_logo_small.png) is based on a peacock. Texera PPMC is working with
third parties who are willing to use Texera brand/trademarks, according to
https://incubator.apache.org/guides/publicity.html and
https://incubator.apache.org/guides/branding.html.
### Signed-off-by:
- [ ] (texera) Cezar Andrei
Comments:
- [X] (texera) Gordon King
Comments:
- [X] (texera) PJ Fanning
Comments:
- [X] (texera) Ian Maxon
Comments: Looks good to me. I think the project is making great
progress toward adopting good practices around project discussions and
license management.
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AL: Report from the Apache InLong Project [Charles Zhang]
## Description:
The mission of Apache InLong is the creation and maintenance of software
related to a one-stop data integration framework that provides automatic,
secure, and reliable data transmission capabilities. InLong supports both batch
and stream data processing at the same time, which offers great power to build
data analysis, modeling, and other real-time applications based on streaming
data.
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: There are no issues requiring board attention
at this time.
## Membership Data:
Apache InLong was founded on 2022-06-15 (3 years ago)
There are currently 53 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. The last addition was Wenwei Huang on 2025-02-07.
- No new committers. The last addition was Xiangming Zhou on 2024-12-16.
## Project Activity:
In the past quarter, InLong has successfully released 2.2.0,
and the project is working on 2.3.0, which will be released
In September. For the newly released 2.2.0, it closed about 87 issues,
including 3+ major features and 80+ optimizations, for example:
- DataProxy SDK Refactoring
- Enhanced Agent Stability and Resource Management
- Sort Traffic Control Enhancements
## Community Health:
The community health looks good overall.
dev@inlong.apache.org had a 53% decrease in traffic in the
past quarter (113 emails compared to 238)
The developing data experienced some decline, but it's within
expectations, and the project is still undergoing normal iteration and
evolution.
-----------------------------------------
Attachment AM: Report from the Apache James Project [Benoit Tellier]
## Description:
The Apache James Project delivers a rich set of open source modules and
libraries, written in Java, related to Internet mail which build into an
advanced extensible mail server running on the JVM.
## Project Status:
Current project status: Ongoing, moderate activity.
Issues for the board: There are no issues requiring board attention
at this time.
## Membership Data:
Apache James was founded 2003-01-22 (22 years ago)
There are currently 43 committers and 19 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 René Cordier on 2025-02-03.
- No new committers. Last addition was Quan Tran on 2025-02-05.
## Project Activity:
Recent releases:
- JDKIM-0.4 was released on 2025-03-04.
- JSPF-1.0.5 was released on 2025-03-03.
- JAMES-3.7.6 was released on 2025-02-05.
Project will work on releasing a new version for MIME4J that integrate
MIME-UTF8 support as well as some edge cases reported by the Tika
community, then the PMC will push for a James Server 3.9.0 release.
## Community Health:
Activity overall decresed in the past quarter but is on par with Q4 2024.
- server-dev@james.apache.org had a 80% decrease in traffic in the past
quarter (71 emails compared to 349)
- server-user@james.apache.org had a 78% decrease in traffic in the past
quarter (31 emails compared to 138)
MIME4J project saw activity (MIME-UTF8 and some other edge cases):
- mime4j-dev@james.apache.org had a 40% increase in traffic in the past
quarter (14 emails compared to 10
-----------------------------------------
Attachment AN: Report from the Apache Jena Project [Andy Seaborne]
## Description:
The mission of Jena is the creation and maintenance of software related to Java
framework for building Semantic Web applications
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Jena was founded 2012-04-18 (13 years ago)
There are currently 20 committers and 14 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 Arne Bernhardt on 2024-04-05.
- No new committers. Last addition was Sergei Zuev on 2024-08-01.
## Project Activity:
There are discussions about a major version release later this year inline
with the policy of supporting the last two Java LTS versions. This is also an
opportunity to make user-visible changes, retiring old features, and finishing
a migration to a new URI parser.
The project is also tracking and participating in the development of W3C
standards in the RDF and SPARQL Working Group. The project is active within
the working group. Jena version 5.4.0 was released at the end of April with a
partial implementation of the RDF 1.2 features.
## Community Health:
Github has seen a steady flow of reports and contributions. Over the last few
years, user questions have been slowly moving from the users mailing list to
using issues labelled "question" on github. This continues including with
several long term users making the switch.
-----------------------------------------
Attachment AO: Report from the Apache JMeter Project [Bruno Demion]
## Description:
The mission of JMeter is the creation and maintenance of software related to
Java performance and functional testing
## Project Status:
Current project status: Ongoing, with low activity
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache JMeter was founded 2011-10-26 (14 years ago)
Jakarta JMeter, first version was released 1998-12-15 (27 years ago)
There are currently 13 committers and 8 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 Vladimir Sitnikov on 2018-06-08.
- No new committers. Last addition was Maxime Chassagneux on 2017-02-15.
## Project Activity:
- Current (low) objective is to move the code base of JMeter to Java 17+
(from Java 8) for next major release (6.0)
- Recent releases:
5.6.3 final was released on 2024-01-07.
## Community Health:
- The project has a low activity during last quarter.
-----------------------------------------
Attachment AP: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
-----------------------------------------
Attachment AQ: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez]
## Description:
The mission of JSPWiki is the creation and maintenance of software related to
Leading open source WikiWiki engine, feature-rich and built around standard
JEE components (Java, servlets, JSP).
## Project Status:
Current project status: Ongoing, with low activity. Issues for the board:
There are no issues requiring board attention.
## Membership Data:
Apache JSPWiki was founded 2013-07-17 (13 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:
- Arturo Bernal was added to the PMC on 2023-06-21
- Arturo Bernal was added as committer on 2023-06-21
- Siegfried Goeschl requested to go emeritus on 2025-02-14
## Project Activity:
Quiet quarter regarding project activity, which has revolved around shipping
last fixes prior to 2.12.3, on master, and preparing the switch to jakarta, on
the jakarta branch.
Next steps: 2.12.3 should be released this month, and then switching to 3.0.0
(Jakarta + modern JDK).
We received one security vulnerability report, which was discarded, although
we made some code changes related to it, to avoid in the future similar
reports which may be flagged by automated tools.
## Community Health:
Work on latest master shows commits from 2 commiters and work from one
contributor (pull #362), work on Jakarta shows work from one committer + one
contributor.
No questions unanswered on MLs, although they continue to have very little
traffic.
Last, due increased spamming we have taken the decission to make our public
wiki instance at jspwiki-wiki.a.o largely read only, making mandatory to ask
for an account at either user or dev MLs, which is needed in order to have
edit permissions.
-----------------------------------------
Attachment AR: Report from the Apache Kibble Project [Sharan Foga]
-----------------------------------------
Attachment AS: Report from the Apache Kudu Project [Andrew Wong]
## Description:
The mission of Apache Kudu is the creation and maintenance of software related
to a distributed columnar storage engine built for the Apache Hadoop ecosystem.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kudu was founded 2016-07-19 (9 years ago)
There are currently 32 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ke Deng on 2024-09-13.
- No new committers. Last addition was Xixu Wang on 2024-09-14.
## Project Activity:
- 1.18.0 release in progress
- 1.17.1 was released on 2024-11-15.
- 1.17.0 was released on 2023-09-01.
- 1.16.0 was released on 2022-04-11.
## Community Health:
- Development activity measured in the number of commits has decreased by 30%.
This is due to projects being in the design phase/collaborating with other
projects. Development measured in the number of unique developers increased
by 1.
- Traffic to dev mailing lists decreased by 28%.
Traffic to issues and reviews mailing lists increased by 21% and 15%.
respectively.
- Community activity measured in community Slack has declined. (the number of
weekly active users -8%, and weekly public posters -11%).
-----------------------------------------
Attachment AT: 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, moderate activity
Issues for the board: No issues for the board at the moment.
## Membership Data:
Apache Logo Development was founded 2024-08-21 (a year ago)
There are currently 16 committers and 15 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 Melissa Logan on 2024-08-28.
- No new committers. Last addition was Chris Wells on 2025-04-11.
## Project Activity:
We are gearing up for the second round of polling for the new logo, and expect
to notify the membership next week (week starting July 14th). This will be a
ranked choice poll and possibly (but not guaranteed) the final poll conducted,
depending on whether we have a clear winner or not.
As far as an overall timeline for the Logo Development project is concerned,
I would say a conservative estimate would be two to three months before we
have a final recommendation for the board, depending on the outcome of the
second round of polling.
## Community Health:
No changes worth noting here. Activity ebbs and flows on an individual level.
-----------------------------------------
Attachment AU: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AV: Report from the Apache MADlib Project [Ed Espino]
-----------------------------------------
Attachment AW: Report from the Apache Mahout Project [Shannon Quinn]
## Description:
Mahout is a distributed linear algebra framework, mathematically expressive
DSL, and quantum computing layer designed to let mathematicians,
statisticians, and data scientists quickly implement their own algorithms.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Mahout was founded 2010-04-20 (15 years ago)
There are currently 30 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 3:1.
Community changes, past quarter:
- No new PMC members. Last addition was Shannon Quinn on 2023-02-12.
- Shannon Quinn made PMC Chair for the next year.
- Krishna Dave was added as committer on 2025-06-19.
## Project Activity:
Latest work efforts in quantum-based machine learning continue, including
parameterization, optimization, and post-processing. Dockerization of the
website has also begun, and work around splitting the repo to support
the multiple "flavors" of Mahout more specifically (see latest meeting minutes:
https://github.com/apache/mahout/discussions/541).
While there has been a decrease in traffic on the issues@ and dev@ lists, this
has coincided with increased dev chatter in the Slack and repo activity as
issues have been closed. We anticipate list activity will pick up again in Q3.
* user@mahout.apache.org had a 1600% increase in traffic in the past quarter
(17 emails compared to 1)
* 0.4 released on 2025-04-17
(https://github.com/apache/mahout/releases/tag/mahout-qumat-0.4)
* 47 commits in the past quarter (209% increase)
* 13 PRs opened on GitHub, past quarter (18% increase)
* 12 PRs closed on GitHub, past quarter (9% increase)
* 5 code contributors in the past quarter (no change)
## Community Health:
* Ongoing community meeting minutes found in GitHub Discussions
(https://github.com/apache/mahout/discussions/)
* "Qumat: Apache Mahout Quantum Compute" presented in June 2025 Berlin
Buzzwords.
-----------------------------------------
Attachment AX: Report from the Apache Maven Project [Hervé Boutemy]
## Description:
The mission of Maven is the creation and maintenance of software related to
Java project management and comprehension tools
## Project Status:
Current project status: ongoing with high activity.
Issues for the board: none.
## Membership Data:
Apache Maven was founded 2003-03-01 (22 years ago)
There are currently 72 committers and 30 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 Romain Manni-Bucau on 2023-10-16.
- Sandra Parsick was added as committer on 2025-06-04
## Project Activity:
Recent releases:
Apache Maven Enforce 3.6.0 was released on 2025-06-28.
Apache Maven GPG Plugin 3.2.8 was released on 2025-06-28.
Maven Resolver 1.9.24 was released on 2025-06-26.
Maven Resolver 2.0.10 was released on 2025-06-26.
Apache Maven 4.0.0-rc-4 was released on 2025-06-25.
Apache Maven Invoker Plugin 3.9.1 was released on 2025-06-23.
Apache Maven PMD Plugin 3.27.0 was released on 2025-06-21.
Apache Maven 3.8.9 was released on 2025-06-18.
Apache Maven EAR Plugin 3.4.0 was released on 2025-06-16.
Apache Maven Parent POMs 45 was released on 2025-06-14.
Apache Parent POM 35 was released on 2025-06-09.
Maven Indexer 7.1.6 was released on 2025-06-02.
Apache Maven 3.9.10 was released on 2025-06-01.
Apache Maven Clean Plugin 3.5.0 was released on 2025-05-27.
Maven Resolver 2.0.9 was released on 2025-05-18.
Maven Archetype 3.4.0 was released on 2025-05-13.
Apache Maven Changes Plugin 3.0.0-M3 was released on 2025-05-12.
Maven Resolver 1.9.23 was released on 2025-05-05.
Apache Maven Dependency Analyzer 1.16.0 was released on 2025-04-14.
A lot of work has been done on Jira to GitHub Issues migration:
- phase 1: Jira is now fully in "no new issues, comment only" mode
- phase 2: 80% of Jira projects past history has been copied to GHI to put
Jira in target read-only mode
Progress is tracked in our Wiki:
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
We did releases of the 3 maintained Maven branches:
- Maven 3.8.9: last 3.8 release with a few backports,
- Maven 3.9.10: bugfix release for the current stable branch,
- Maven 4.0.0-rc-4: should be last RC before stable release.
Focus is on stabilizing Maven 4.0.
## Community Health:
In addition to Maven 4, the recent change of publication to Maven Central
drives a lot of discussion on dev mailing list. Slack is used for fast,
informal, interactions on these topics, including with the Maven Central team.
-----------------------------------------
Attachment AY: Report from the Apache Mesos Project [Qian Zhang]
## Description:
The mission of Mesos is the creation and maintenance of software related to a
cluster manager that provides efficient resource isolation and sharing across
distributed applications
## Project Status:
Current project status: [No activities]
Issues for the board: [None]
## Membership Data:
Apache Mesos was founded 2013-06-19 (12 years ago)
There are currently 50 committers and 50 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Charles-François Natali on 2021-08-08.
- No new committers. Last addition was Charles-François Natali on 2021-08-07.
## Project Activity:
[There were no activities, no plan to do new releases.]
## Community Health:
[The community was not active, no new issues or PRs created, and no new
contributors.]
-----------------------------------------
Attachment AZ: Report from the Apache MINA Project [Thomas Wolf]
## 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 28 committers and 15 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 Gary D. Gregory on 2023-09-13.
- No new committers. Last addition was Gary D. Gregory on 2022-03-24.
Note: if one looks for *active* people, one finds 7 active PMC members
and 6 active committers (who are 6 of the 7 active PMC members).
## Project Activity:
We maintain five products:
* Apache MINA: an asynchronous I/O library. Latest releases were
2.0.27, 2.1.10, and 2.2.4 on 2024-12-19. Mature & stable; low
development activity. Issue tracker: JIRA.
* Apache MINA SSHD: library for client- and server-side SSH. Latest
release 2.15.0 on 2025-02-25. Mature & stable, active development.
It's the most active of the five and has begun development of a new
major release 3.0 that includes major refactoring and clean-up that
enable implementing new features. Issue tracker: Github.
* Apache MINA FtpServer: FTP server library. Latest release was
1.2.1 on 2025-02-02. Mature & stable, maintenance activity only.
Issue tracking in Github.
* Apache Vysper: XMPP (Jabber) library. Last release was 0.7 on
2011-02-13. (SIC!) No activity. Dormant.
* Apache AsyncWeb: asynchronous HTTP(S) web server library. No
activity. Dormant.
No releases this quarter.
## Community Health:
Community is healthy, though there only a few active people. We get
some contributions through Github PRs. Most communication with people
outside the project happens through Github issues, which are usually
responded to promptly. The mailing lists see much less traffic.
-----------------------------------------
Attachment BA: Report from the Apache MyFaces Project [Bernd Bohmann]
## Description:
The mission of MyFaces is the creation and maintenance of software related to
JavaServer(tm) Faces implementation and components
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: None
## Membership Data:
Apache MyFaces was founded 2005-02-23 (20 years ago)
There are currently 81 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Melloware on 2024-01-25.
- No new committers. Last addition was Milan Siebenbürger on 2024-01-24.
## Project Activity:
Normal project activity.
On June 6, 2025, Kyler Katz reported a CWE-598 bug in Apache MyFaces
Core 4.1.1 regarding a sensitive token embedded in URLs. Volodymyr
Siedlecki investigated and concluded it was intentional behavior on
specification level with no reasonable attack vector.
On June 11, 2025, Bernd Bohmann and Paul Nicolucci agreed, and
Volodymyr then informed the Apache Security Team that the PMC
concurred, suggesting the issue could be raised with the Eclipse
Foundation at a specification level.
- Recent releases:
myfaces-core-3.0.3 was released on 2025-07-01.
tobago-6.8.0 was released on 2025-06-14.
tobago-5.15.2 was released on 2025-05-17.
tobago-6.7.2 was released on 2025-05-17.
## Community Health:
- Apache MyFaces Core is healthy.
UI-Component Sets:
- Apache Tobago is healthy.
- Apache Trinidad is in maintenance mode.
Last developer commit was Sept 2017.
- Myfaces Tomahawk is in maintenance mode.
Last developer commit was May 2016.
Last commit on behalf of a contributor was May 2016.
Add-ons and Extensions:
- Apache MyFaces Portlet Bridge is in maintenance mode.
Last developer commit was Jan 2014.
Last commit on behalf of a contributor was May 2015.
- Apache MyFaces CODI is in maintenance mode.
CODI was replaced by Apache DeltaSpike so new development
happens there. Last commit March 2014.
- Apache MyFaces Orchestra is in maintenance mode.
New projects use CDI and DeltaSpike instead.
Last commit on behalf of a contributor was August 2016.
- Apache MyFaces ExtVal is in maintenance mode.
Last commit June 2014.
- Apache MyFaces Commons is in maintenance mode.
Last commit August 2012.
- Apache MyFaces Ext-Scripting is in maintenance mode.
Last commit Sept 2017.
- Apache MyFaces Test is in maintenance mode (Used by Myfaces Core).
Last commit May 2017.
-----------------------------------------
Attachment BB: Report from the Apache Mynewt Project [Szymon Janc]
## Description:
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Mynewt was founded 2017-06-21 (8 years ago)
There are currently 37 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Michał Górecki on 2024-06-27.
## Project Activity:
Work is ongoing in several areas, mainly improvements in BSP and MCU support
(eg. Nordic nRF54H20), as well as some core subsystems work (LVGL, shell,
logging etc).
Continued work on Nordic nRF54L15 support and Bluetooth 6.0 features
(eg Channel Sounding). Continued work on LE Audio (Broadcast Sink).
There is also ongoing work on fixing NimBLE bugs that are affecting Bluetooth
Qualification (both host and controller).
Github Actions CI improvements for helping PR handling.
Initially planned June release was postponed to July/August.
## Community Health:
Core developers are active on regular basis. Most work is Bluetooth related.
We see more interest from other projects in using NimBLE port (various bugfixes
contributed!).
-----------------------------------------
Attachment BC: Report from the Apache NiFi Project [Joe Witt]
## Description:
The mission of NiFi is the creation and maintenance of software related to
providing an easy to use, powerful, and reliable system to process and
distribute data.
Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
integrate with and leverage the command and control of NiFi. There are both
Java and C++ implementations.
Apache NiFi Registry is a centralized registry for key configuration items
including flow versions, assets, and extensions for Apache NiFi and Apache
MiNiFi.
Apache NiFi Nar Maven Plugin is a release artifact used for supporting the
NiFi classloader isolation model.
Apache NiFi Flow Design System is a theme-able set of high quality UI
components and utilities for use across the various Apache NiFi web
applications in order to provide a more consistent user experience.
## Project Status:
Current project status: Ongoing. High.
Issues for the board: None.
## Membership Data:
Apache NiFi was founded 2015-07-14 (10 years ago)
There are currently 68 committers and 38 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 Ferenc Kis on 2024-12-30.
- No new committers. Last addition was Lucas Ottersbach on 2024-11-12.
## Project Activity:
During the quarter the NiFi community produced four releases. These include
NiFI 2.4.0 on May 1st 2025
NiFi 2.4.0 includes more than 100 JIRAs and makes it easy to leverage
Bitbucket as a versioned flow registry, integrate with Box to grab data, and
several other improvements and bug fixes.
A NiFi Improvement Proposal (NIP-6) was approved which helps downstream
components understand the presence of upstream backpressure.
## Community Health:
JIRA and Mailing list activity remains active.
The Slack community remains growing and active with now 3,792 members in the
general channel versus 3,657 in the previous quarter.
We continue to enjoy significant release vote participation and release
activity.
PR activity in Gihub remains strong. However, we need to do a better job with
identifying community merit growth. Of the code contributions in the past 30
days that landed 5 of the 11 unique authors are not committers or PMC members
so we have plenty to work with. In the total reporting period we have 27
unique authors.
-----------------------------------------
Attachment BD: Report from the Apache Nutch Project [Sebastian Nagel]
## Description:
Apache Nutch is a highly extensible and scalable open source web crawler
software project based on Apache Hadoop® data structures and the MapReduce
data processing framework.
## Project Status:
Current project status: ongoing with medium to low activity
Issues for the board: none
## Membership Data:
Apache Nutch was founded 2010-04-21 (15 years ago)
There are currently 23 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Joe Gilvary on 2024-08-07.
- No new committers. Last addition was Joe Gilvary on 2024-08-07.
## Project Activity:
1.20 was released on 2024-04-24.
The work on Nutch 1.21 is ongoing. A release is planned during July.
## Community Health:
The number of contributions (Jira issues, commits, activity on the mailing
lists) is on a low, but steady level.
-----------------------------------------
Attachment BE: Report from the Apache NuttX Project [Alin Jerpelea]
## Description:
The mission of Apache NuttX is the creation and maintenance of software related
to a mature, real-time embedded operating system (RTOS)
## Project Status:
Current project status: Ongoing with high activity level
Issues for the board: no issues for the board
## Membership Data:
Apache NuttX was founded 2022-11-16 (3 years ago)
There are currently 36 committers and 23 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 Yanfeng Liu on 2024-08-15.
- Filipe do Ó Cavalcanti was added as committer on 2025-06-24
- Matteo Golin was added as committer on 2025-05-28
- Rodrigo Sim was added as committer on 2025-06-25
## Project Activity:
The project is happy to announce that on 2025-07-09 the latest quarterly
NuttX release (12.10.0) was published with over 400 contributions from
community providing support for new boards, new drivers, multiple
optimizations and fixes
## Community Health:
In the past quarter the 3 community members got recognized and were
invited to become committers.
With the new contribution guidelines the commit review from community
has improved, providing quality over quantity.
The community is preparing to host the yearly NuttX International Workshop
and checking for location availability. If there is no suitable location
the event will be hosted online. (the project will contact the events team
after location confirmation)
-----------------------------------------
Attachment BF: Report from the Apache Olingo Project [Michael Bolz]
## Description:
The Apache Olingo Project is responsible for the creation and
maintenance of software related to providing an implemention of the OASIS OData
(Open Data Protocol) specifications, in server and client form;
## Project Status:
Current project status: Dormant
Issues for the board:
Because of low time of the last
maintainers and the low interest of the
left over PMC members, it should
be discussed to move the project to the
Apache attic.
## Membership Data:
Apache Olingo was founded 2014-03-19 (10 years ago)
There are currently 25 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ramya Vasanth on 2019-04-15.
- No new committers. Last addition was Archana Rai on 2017-05-26.
## Project Activity:
Recent releases:
- V4 5.0.0 was released on 2023-12-18.
- 4.10.0 was released on 2023-10-22.
- V2 2.0.13 was released on 2023-10-22.
Both releases are delayed because of
technical issues with the new release
process, limited time of the
maintainers, and less interest
of the PMC members.
## Community Health:
Overall community health is okay-ish.
The community asks for the releases,
but because of mentioned issues those
are not available yet.
-----------------------------------------
Attachment BG: Report from the Apache OpenJPA Project [Mark Struberg]
## Description:
The mission of OpenJPA is the creation and maintenance of software related to
OpenJPA: Object Relational Mapping for Java
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: none
## Membership Data:
Apache OpenJPA was founded 2007-05-16 (18 years ago)
There are currently 36 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13.
- Paulo Cristovão de Araújo Silva Filho was added as committer on 2025-05-30
## Project Activity:
We have invited new committer and it seems he move the project:
JPA 3.1. issues are being fixed, the work on JPA 3.2 implementation has
been started
Recent releases:
- 4.0.1 was released on 2024-09-27.
- 4.0.0 was released on 2024-02-14.
- 3.2.2 was released on 2022-03-16.
## Community Health:
We have invited new committer and hopefully he will stay enough with project
to become PMC member and chair ;)
-----------------------------------------
Attachment BH: Report from the Apache OpenMeetings Project [Maxim Solodovnik]
## Description:
The mission of OpenMeetings is the creation and maintenance of software related
to OpenMeetings: Web-Conferencing and real-time collaboration
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache OpenMeetings was founded 2013-01-25 (12 years ago)
There are currently 30 committers and 28 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 Ali Alhaidary on 2021-03-22.
- No new committers. Last addition was Ali Alhaidary on 2021-04-07.
## Project Activity:
We are preparing 8.1.0 bug fix version to be released (hopefully
I'll start the VOTE next week)
- 8.0.0 was released on 2025-01-02.
- 7.2.0 was released on 2023-12-23.
- 7.1.0 was released on 2023-05-09.
## Community Health:
There is not much happening with the code, so email traffic is low
I doubt new release can change this. But we will see :))
-----------------------------------------
Attachment BI: 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 on 2012-10-16 (13 years ago) There are currently
141 committers and 28 PMC members in this project. The Committer-to-PMC ratio
is roughly 9:2. 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 July
1: 389,806,312
### Codebase in OpenOffice repository
Work continues on the 4.2 future release. This included:
Work on building a 64-bit Windows version.
Work on code spelling and code linting.
dev@openoffice.apache.org had a 65% decrease in traffic in the past quarter
(165 emails compared to 471):
issues@openoffice.apache.org had a 14% decrease in traffic in the past quarter
(40 emails compared to 46):
l10n@openoffice.apache.org had a big increase in traffic in the past quarter
(15 emails compared to 0):
### Documentation
The OpenOffice-docs repository is where the small documentation team makes
updates.
The chapters for the Writer Guide are completed and ready to be 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 slight Increase in traffic in the past
quarter. 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 22% increase in traffic in the past quarter
(71 emails compared to 58):
users-de@openoffice.apache.org had a 22% decrease in traffic in the past
quarter (33 emails compared to 42):
### 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.
The Template site has been completed
### 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
### 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 11
users 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.
We have started the work on a new approach to Python scripting support in AOO.
### 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 BJ: Report from the Apache ORC Project [William Hyun]
## Description:
The mission of ORC is the creation and maintenance of software related
to the smallest, fastest columnar storage for Hadoop workloads.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache ORC was founded 2015-04-21 (10 years ago)
There are currently 49 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
- Shaoyun Chen was added to the PMC on 2025-03-23.
- No new committers. Last addition was Yuanping Wu on 2024-05-14.
## Project Activity:
According to our release cadence, we released six maintenance releases
in this quarter and helped other Apache communities use them.
- 1.9.7 was released on 2025-07-04.
- 1.8.10 was released on 2025-06-26.
- 2.1.2 was released on 2025-05-06.
- 2.0.5 was released on 2025-05-06.
- 1.9.6 was released on 2025-05-06.
- 1.8.9 was released on 2025-05-06.
In addition, we are preparing the following milestones for the
upcoming quarters.
- 2.2.0 (July)
- 2.0.7 (October)
- 2.1.3 (November)
## Community Health:
In this quarter, we saw a healthy growth in the community
with a 88% increase in traffic for the dev mailing list
and 52% increase in the issues mailing list.
We are preparing for the 2.2.0 release and have started
a soft feature freeze in preparation.
-----------------------------------------
Attachment BK: Report from the Apache Parquet Project [Julien Le Dem]
## Description:
A column-oriented data file format designed for efficient data storage and
retrieval. It provides high performance compression and encoding schemes to
handle complex data in bulk and is supported in many programming languages and
analytics tools.
Parquet consists of a format specification (the Parquet format) and several
implementations, one of which (Parquet Java) is developed directly under the
umbrella of the Apache Parquet project. Non-Apache implementations also exist,
some of them closed source.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Parquet was founded 2015-04-22 (10 years ago)
There are currently 39 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Fokko Driesprong on 2025-01-24.
- No new committers. Last addition was Xuwei Fu on 2024-07-11.
## Project Activity:
Current work:
- Int96 timestamp deprecation discussion
- Variant type implementation is ongoing and progressing well
- Interval Type discussion
- Work in progress on defining the process to accept new Encodings with a
goal to add new numeric encodings
- Work in progress on defining a new metadata footer format.
- Work in progress to define floating point decimal data type
- Geo Types in progress
Recent releases:
- parquet-java 1.15.2 was released on 2025-05-01.
- parquet-Format 2.11.0 was released on 2025-03-23.
- parquet-java 1.15.1 was released on 2025-03-16.
## Community Health:
Discussions are regularly happening on the mailing list, in PRs/Issues on
Github and on a regular sync meeting held on zoom (notes are posted on the list)
-----------------------------------------
Attachment BL: Report from the Apache PDFBox Project [Andreas Lehmkühler]
## Description:
The mission of PDFBox is the creation and maintenance of software related to
Java library for working with PDF documents
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache PDFBox was founded 2009-10-21 (16 years ago)
There are currently 21 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matthäus Mayer on 2017-10-16.
- No new committers. Last addition was Joerg O. Henne on 2017-10-09.
## Project Activity:
Recent releases:
3.0.5 was released on 2025-05-01.
2.0.34 was released on 2025-04-24.
3.0.4 was released on 2025-01-23.
## Community Health:
- there is a steady stream of contributions, bug reports and questions on the
mailing lists
- we started to implement some improvements based on several proposals from Axel
Howind
- another 3.0.x and 2.0.x will most likely be released in a couple of weeks
-----------------------------------------
Attachment BM: Report from the Apache Petri Project [Greg Stein]
## Description:
The mission of Apache Petri is the creation and maintenance of software related
to assessment of, education in, and adoption of the Foundation's policies and
procedures for collaborative development and the pros and cons of joining the
Foundation
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Petri was founded 2019-11-19 (5 years ago)
There are currently 8 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Shahaf on 2019-11-19.
- No new committers. Last addition was Justin Erenkrantz on 2020-04-23.
## Project Activity:
Idle, until we have a project to assist.
## Community Health:
The project is currently idle, with little discussion. Some energy is
needed to revamp and clarify our mission, and update the website to
make it clear what Petri offers to projects seeking to become part of
the Foundation family of projects.
(this report is effectively the same as the prior report)
-----------------------------------------
Attachment BN: Report from the Apache PLC4X Project [César García]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: None
## Membership Data:
Apache PLC4X was founded 2019-04-16 (6 years ago)
There are currently 22 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Iñigo Angulo Otegi was added to the PMC on 2025-06-19
- Unai Lería Fortea was added as committer on 2025-06-11
## Project Activity:
- The S7-light driver has been added to the set of available drivers.
Work is also being done to improve the stability and reliability of
the S7 and Modbus drivers.
- The plc4x-build-tools was released on 04/24 in version 1.8.0
## Community Health:
- In general, the core community remains active on both the mailing list
and the Slack platform, as well as interacting on professional
social networks.
- The development list shows a decrease of 44% in traffic in the
past quarter (170 emails compared to 302).
- The traffic generated is mainly related to the addition of
new features, bug fixes and, to a lesser extent, the addition of
new features which are managed by project members and specific
contributions.
- The biggest drop in making list activity is due to us redirecting
pr emails away from dev (which mostly contained dependabot emails)
- On professional social networks, specifically LinkedIn, there is an
increase in interest in the project, currently having 571,
which indicates an approximate increase of 12%.
-----------------------------------------
Attachment BO: Report from the Apache Ranger Project [Selvamohan Neethiraj]
## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive data
security - consistently across various data processing services.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
- Apache Ranger was founded 2017-01-17 (8 years ago).
- There are 39 committers and 17 PMC members in this project.
- The Committer-to-PMC ratio is roughly 5:3.
##Community changes, past quarter:
- No new PMC members. Bhavik Patel was added to the PMC on 2024-09-04
- No new committers. Fateh Singh was added as committer on 2024-10-14
## Project Activity:
- Ranger 2.6.0 version is released on feb-15-2025.
- The community has started discussion on next release, 2.7.0, likely to be released by end of this month
- docker setup improvements: published ranger-base image to docker hub, making it faster to build local Ranger docker images
- Ranger 3.0.0 version is progressing well
-- 1375 issues are resolved for this release.
-- 27 open issues to be addressed
-- 29 issues are being worked on.
-- contains 661 bug-fixes, 535 new improvements and 22 new features
- Key issues/features addressed in 3.0.0 release in the past quarter:
-- Able to filter audits by federated users
-- Refactor of audit modules based on it's audit destination
-- Optimize config handling during "Thread-Safe check" on metric collection
-- Enhanced dataset search filtering
-- Added more unit tests for RangerAtlasAuthorizer and RangerKeyStoreProvider
-- Fixed audit log generation for dataset modifications
-- Upgrade of libraries (jacoco->0.8.13)
-- Improved CI process using generated code coverage report
-- Code improvements in RangerOzoneAuthorizer
## Community Health:
Traffic on some of the mailing lists were high due to release activities in the previous quarter.
As we have completed the release 2.6.0, there are lot less mailing activities in this quarter.
Also, similar reason for reduction on closing of pull requests in this quarter compared to the previous one.
No concerns as of now and these activities will pickup once 3.0.0 is scheduled for release.
- 474 emails in dev@ranger.apache.org in this quarter (-133% change from past quarter)
- 13 emails in user@ranger.apache.org in this quarter (- 23% change from past quarter)
- 53 issues opened in JIRA in this quarter (- 84% change from past quarter)
- 36 issues closed in JIRA in this quarter (- 83% change from past quarter)
- 15 PRs opened on GitHub in this quarter (+ 20% change from past quarter)
- 15 PRs closed on GitHub in this quarter (- 53% change from past quarter)
## Most Recent releases:
- Apache Ranger 2.6.0 was released on 2025-02-15
- Apache Ranger 2.5.0 was released on 2024-08-07
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
-----------------------------------------
Attachment BP: Report from the Apache Ratis Project [Tsz-wo Sze]
-----------------------------------------
Attachment BQ: Report from the Apache Rya Project [Adina Crainiceanu]
## Description:
The mission of Apache Rya is the creation and maintenance of software related
to scalable storage, retrieval, and analysis of RDF data
## Project Status:
Current project status: dormant
Issues for the board: none
## Membership Data:
Apache Rya was founded 2019-09-17 (6 years ago)
There are currently 12 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
No new PMC members since project became a top-level project.
Last addition was David Lotts on 2016-11-17.
- No new committers were added.
## Project Activity:
No new activity. Last release 4.0.1 was on 2020-12-22
## Community Health:
There is no current activity in the project. The software is used in production
by users. The project is in "dormant" state: not much happening on the code,
but at least 3 PMC members ready to engage if needed
dev@rya.apache.org had a 100% increase in traffic in the past quarter
(2 emails compared to 1)
-----------------------------------------
Attachment BR: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment BS: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to a very easy-to-use ultra-high-performance distributed data
integration platform that supports cdc and batch synchronization of massive
data
## Project Status:
Current project status: Health Issues for the board: There are no Board-level
issues at this time.
## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (2 years ago) There are currently 37
committers and 21 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 Guangdong Liu on 2024-05-15.
- Chao Wang was added as committer on 2025-04-14
## Project Activity:
- 2.3.11 was released on 2025-05-21
- 2.3.10 was released on 2025-03-21
- 2.3.9 was released on 2025-01-18
- 2.3.8 was released on 2024-10-12
- We have held one community online Meetups in last quarter.
## Community Health:
- 56% decrease in dev mailing list in traffic in the past quarter, which means
we need to discussed issues or features more frequently.
- We have solved all of the security issues
Overall community health is good. We have been performing extensive outreach
to related projects, in order to attract new contributors, and are seeing a
steady influx of new people wishing to join and contribute, both programming-
and documentation-wise.
We are currently recruiting contributors and enriching the project structure
documentation to allocate "good first issues" to help them get started
quickly.
-----------------------------------------
Attachment BT: Report from the Apache SkyWalking Project [Sheng Wu]
## Description:
The mission of Apache SkyWalking is the creation and maintenance of software
related to application performance management and monitoring (APM)
## Project Status:
Current project status: Ongoing
Issues for the board: No
## Membership Data:
Apache SkyWalking was founded 2019-04-17 (6 years ago)
There are currently 62 committers and 35 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 Zixin Zhou on 2024-12-30.
- No new committers. Last addition was Claire Chen on 2024-05-27.
## Project Activity:
We have active deployments for the project. Several projects released
in this quarter.
nodejs-0.8.0 was released on 2025-05-11
python-1.2.0 was released on 2025-05-11
go-0.6.0 was released on 2025-04-28
php-1.0.0 was released on 2025-04-22.
rust-0.9.0 was released on 2025-04-08.
banyandb-0.8.0 was released on 2025-04-07.
The community started a new project, skywalking-mcp,
to adopt AI integration better.
## Community Health:
dev@skywalking.apache.org had a 24% increase in traffic in the
past quarter (138 emails compared to 111).
The community is healthy. We have active code contributions, discussions on
GitHub and ASF Slack. A new direction of BanyanDB has been made, and we
are confident that this will improve the long-existing issue - the cost of
SkyWalking deployment.
-----------------------------------------
Attachment BU: Report from the Apache Steve Project [Daniel Gruno]
## Description:
The mission of Steve is the creation and maintenance of software related to
Apache's Python based single transferable vote software system
## Project Status:
Current project status: Largely dormant, low activity.
Issues for the board: No issues for the board at the moment.
## Membership Data:
Apache Steve was founded 2012-07-25 (13 years ago)
There are currently 10 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jim Jagielski on 2022-04-16.
- No new committers. Last addition was Sean Palmer on 2022-03-04.
## Project Activity:
No noteworthy activity this quarter. As with previous quarters, the project
has sufficient oversight, but with a slow development pace.
## Community Health:
-----------------------------------------
Attachment BV: Report from the Apache StormCrawler Project [Richard Zowalla]
## Description:
The mission of Apache StormCrawler is the creation and maintenance of software
related to an open source collection of resources for building low-latency,
scalable web crawlers on Apache Storm
## Project Status:
Current project status: active
Issues for the board: none
## Membership Data:
Apache StormCrawler was founded 2025-05-21 (a month ago)
There are currently 10 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
StormCrawler graduated from the Apache Incubator about two months ago. The
project has made our first official release as a TLP.
We have also implemented a new external module that leverages generative AI
for text extraction — offering a modern alternative to the existing rule-based
and XPath-based approaches. This enhancement brings StormCrawler's
capabilities closer to leading Python-based crawlers and reflects our
commitment to innovation and usability.
StormCrawler has maintained a stable user base over the past decade and
continues to be well-regarded. Although the number of committers and
contributors remains relatively small, the project's activity level is on par
with other established TLPs.
We’ve begun to receive contributions from outside the usual suspects, which is
encouraging. We hope some of these new contributors will stay and become
longer-term participants in the StormCrawler community.
We have started work on improved documentation to simplify onboarding for both
users and potential contributors. We also plan to begin working on
trademark-related tasks in the coming weeks, to ensure proper branding and
compliance as part of our transition to a full TLP.
Recent releases:
3.4.0 was released on 2025-06-27.
## Community Health:
The StormCrawler community remains active and stable. We’ve started to see
contributions from new participants outside the core group, which is a positive
sign for long-term growth. While the number of committers has not changed,
there is increased engagement from external contributors, and we hope some of
them will stay involved and eventually take on larger roles.
With work on improved documentation now underway, we aim to make it easier for
new users and contributors to get started and participate more actively. These
efforts are expected to further strengthen the project's community over time.
-----------------------------------------
Attachment BW: Report from the Apache StreamPark Project [Huajie Wang]
## Description:
Make stream processing easier! Easy-to-use streaming application
development framework and operation platform.
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none
## Membership Data:
Apache StreamPark was founded 2025-01-23 (6 months ago)
There are currently 8 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 2:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jie Cheng on 2024-08-06.
- No new committers were added.
## Project Activity:
- New version 2.1.6 released.
- Cleared the roadblocks for v2.2 release, preparing for the 2.2 release.
- Supported apache flink 1.20
- Compatibility improvement for parsing Flink config file.
## Community Health:
- Welcomed 1 new code contributors.
- Add a new release manager.
- We need to further boost developer engagement.
-----------------------------------------
Attachment BX: Report from the Apache Struts Project [René Gielen]
## Description:
The Apache Struts MVC framework is a solution stack for creating modern and
elegant action-based Java web applications. It favours convention over
configuration, is extensible using a plugin architecture, and ships with
plugins to support patterns and technologies such as REST, AJAX and JSON.
## Project Status:
Current project status: Ongoing Issues for the board: none
## Membership Data:
Apache Struts was founded 2004-03-17 (21 years ago) There are currently 60
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 Kusal Kithul-Godage on 2024-02-24.
- No new committers. Last addition was Kusal Kithul-Godage on 2023-08-03.
## Project Activity:
The Struts team made no framework releases in the reporting period.
The last releases were
- Struts 7.0.3 - Bug Fix and Improvements Release (2025-03-03) [1]
- Struts 6.7.4 - Bug Fix and Improvements Release (2025-03-05) [2]
We made one release of a supporting library:
- Struts Annotations 2.0.0 - Enhancements and JDK 17 support (2025-07-03)
The last Struts releases besides the core framework were
- Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06)
After more busy times in the months before, we experienced a rather quiet
quarter. Preparations for the Struts 7.1 release are underway.
We have no issues that require board assistance at this time.
## Community Health
### Development activity in the reporting period
13 JIRA were tickets opened and 7 closed in the past quarter.
We had 41 PRs opened and 41 closed in the main project, which is a moderate
activity compared to other quarters.
### Mailing list activity:
- dev@struts.apache.org had a 91% decrease in traffic in the past quarter (13
emails compared to 143)
- issues@struts.apache.org had a 76% decrease in traffic in the past quarter
(109 emails compared to 453)
- notifications@struts.apache.org had a 51% decrease in traffic in the past
quarter (261 emails compared to 526)
-----------------------------------------
Attachment BY: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high-performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Project Status:
Current project status: Active
Issues for the board: None
## Membership Data:
Apache Synapse was founded on 2007-12-19 (18 years ago). There are currently
36 committers and 27 PMC members in this project. The Committer-to-PMC ratio
is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Shafreen on 2021-05-09.
- No new committers. Last addition was Nuwan Jayawardene on 2022-11-19.
We have identified active new contributors to the Synapse-Go project and plan
to initiate committership discussions soon.
## Project Activity:
Activity on the main Synapse project was lower this quarter, but the
Synapse-Go effort continues to see contributions. In the past quarter, 4 pull
requests were submitted for the Go-based implementation, including over 30
commits. While overall project momentum has dipped slightly, the Synapse-Go
initiative is progressing.
## Community Health:
The dev@synapse.apache.org mailing list saw a 52% decrease in traffic this
past quarter, with 17 emails compared to 35 in the previous quarter. Despite
the drop in mailing list activity, the community remains engaged, and we are
seeing meaningful contributions from new participants. We aim to sustain this
by recognizing contributors and expanding the committer base.
-----------------------------------------
Attachment BZ: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework
## Project Status:
Current project status: ongoing (moderate/low)
Issues for the board: none
## Membership Data:
Apache Tapestry was founded 2006-02-15 (19 years ago)
There are currently 30 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ben Weidig on 2021-12-03.
- No new committers. Last addition was Christian Köberl on 2024-05-02.
## Project Activity:
After adding the support to Jakarta EE last quarter, the project is updating
more components to build a more modern foundation. ES6 module support is nearing
completion, as is rebuilding the Gradle setup based on the latest version and
best practices. This is a crucial step to keep up with Java's more rapid
releases so the project can provide support for the latest versions.
Additionally, the maintenance load over time should decrease, making
participation in the community easier.
Furthermore, the transition of the project homepage and documentation from the
legacy Confluence setup to Antora is ongoing, as it's done mostly manually by
community members.
We concentrate on improving the foundation and documentation before defining
the next "big thing" to work on.
## Community Health:
Overall, community activity is going well. Questions on the mailing lists are
on the low end, but we still interpret this as a positive sign, given the
significance of the last release.
One of the more prominent Tapestry community projects by a PMC member, Tynamo,
has created updated releases for JakartaEE. We want to use this opportunity to
increase community engagement and create more opportunities to participate by
providing support if needed.
Moving to GitHub to increase engagement, thanks to the myriad of features, was
put on hold until after finishing the documentation transition. Regarding the
comment in the last report, we are glad to collect and share our experiences
of that approach with ComDev.
JIRA activity stats for the last quarter: 5 open/active issues 2
closed/resolved
-----------------------------------------
Attachment CA: 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: No issues to report.
## 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:
Work on making Tcl 9 the primary supported Tcl version still continues.
## Community Health:
The traffic of the mailing lists has decreased in comparison to the previous
reporting period, which is normal for the project (as most traffic in the list
happens after new releases).
-----------------------------------------
Attachment CB: 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:
The latest release was 0.10.5 on 2025-05-30 with important bugfixes. The
master branch started to have 1.0.0-SNAPSHOT as a preparation for a
near-future Tez 1.0 release.
## Community Health:
2 active PMC members + a few PMC members that are ready to vote if needed. A
few new contributors are present on github, not yet close to become
committers.
-----------------------------------------
Attachment CC: Report from the Apache Thrift Project [Jens Geyer]
## Description:
Apache Thrift is a high performance cross platform RPC and serialization
solution.
## Project Status:
Current project status: Ongoing moderate
Issues for the board: none
## Membership Data:
Apache Thrift was founded 2010-10-20 (15 years ago)
There are currently 41 committers and 22 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 Liu Jiayu on 2025-03-16.
- No new committers. Last addition was Liu Jiayu on 2022-06-25.
## Project Activity:
We released 0.22.0 on 2025-05-23 being mostly maintenance releases.
For certain language bindings, particularly Swift, there appear to be no
active maintainers left. A direct "call to action" in a Swift forum to find
potential maintainers yielded little success.
## Community Health:
Similar to past quarters, there is a steady flow of contributions, both
improvements and bug fixes, on varying levels, mostly via Jira/Github.
-----------------------------------------
Attachment CD: Report from the Apache Tika Project [Tim Allison]
## Description:
Apache Tika is a dynamic toolkit for content detection, analysis, and
extraction. It allows a user to understand, and leverage information from, a
growing a list of over 1200 different file types including most of the major
types in existence (MS Office, PDF, Text, Images, Video, Code, and science
data) as recognized by IANA and other standards bodies.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Tika was founded 2010-04-20 (15 years ago)
There are currently 32 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05.
- No new committers. Last addition was Nicholas DiPiazza on 2021-06-03.
## Project Activity:
We made our final Java 8 release in May (2.9.4). We're in the process of our
next 3.2.x bug fix release, and we continue work on our next major branch
(main/4.x).
We published a new security model page at the recommendation of Arnout Engelen
and security@: https://tika.apache.org/security-model.html
## Community Health:
Our CHI is 4.7 (Healthy), but we could improve our health by identifying and
adding new PMC/committers.
-----------------------------------------
Attachment CE: Report from the Apache TinkerPop Project [Kelvin Lawrence]
## Description:
Apache TinkerPop is a graph computing framework for both graph databases
(OLTP) and graph analytic systems (OLAP).
## Project Status:
The project is ongoing with relatively high activities this past quarter.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Community changes, past quarter:
- Cole Greer was added to the PMC on 2025-06-02
- No new committers. Last addition was Norio Akagi on 2024-10-31.
## Project Activity:
Development momentum remains strong in this quarter, with community efforts
concentrated on TinkerPop 3.8.0 features, which is targeting a release in
2025. This version serves as a crucial transitional release, offering
forward-compatible functionality to streamline the eventual migration to
TinkerPop 4.0. The 3.8.0 release will include essential bug resolutions,
selected feature improvements ported back from 4.0.0-beta.1, as well as new
functionalities such as number casting [1].
Development effort has largely shifted from the HTTP migration in TinkerPop 4,
towards the query semantics improvements for 3.8.0. The focus on semantics
improvement now continues to progress the TinkerPop 4 agenda and gives gremlin
a more stable foundation such that users can expect less frequent breaking
changes in future releases. It is expected that the focus on TinkerPop 4 will
ramp back up following the 3.8.0 release, and we plan to release 4.0.0-beta.2
later this year.
### Releases:
4.0.0-beta.1 was released on 2025-01-17.
3.7.3 was released on 2024-10-23.
## Community Health:
The TinkerPop community has held consistent momentum with regular
contributions from core committers as well as regular questions and engagement
from new and existing users in our community discord server.
We've learned about the development of two new TinkerPop providers which would
give the project support in almost 30 graph systems. The first is called
YouTrackDB [2] whose developers are interested in high-performance computing
use cases around the Gremlin graph query language for their implementation.
The second implementation involves development of a TinkerPop provider that
uses Google Firestore as a backend for a graph database and could introduce an
interesting way to interact with TinkerPop in Google Cloud. With TinkerPop,
new providers are an excellent indicator of good community health as it
reaffirms our value proposition to database vendors, exposes new users to the
TinkerPop ecosystem, and gives existing users more choice and flexibility.
A new TinkerPop provider has been added to Apache Airflow [3], which enables
Airflow to query graph data from any TinkerPop enabled graph database via our
gremlin-python driver. Ahmad Farhan, the contributor of this provider,
delivered a TinkerPop Wide presentation [4] and demo on our Twitch channel [5]
to introduce Airflow and the new provider to the TinkerPop community.
## Report Links
[1]: https://s.apache.org/rjr3u
[2]: https://youtrackdb.io/
[3]: https://s.apache.org/t8mgc
[4]: https://www.youtube.com/watch?v=26pY6sNLIIg
[5]: https://www.twitch.tv/apachetinkerpop
-----------------------------------------
Attachment CF: Report from the Apache Traffic Server Project [Bryan Call]
-----------------------------------------
Attachment CG: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment CH: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
The mission of Wicket is the creation and maintenance of software related to
Component-based Java Web Application Framework.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Wicket was founded 2007-06-20 (18 years ago)
There are currently 35 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Pavlovich on 2025-01-27.
- No new committers. Last addition was Matt Pavlovich on 2025-01-27.
## Project Activity:
In the last quarter we have released the following versions:
- 10.5.0 was released on 2025-04-25.
- 9.21.0 was released on 2025-04-25.
- 8.17.0 was released on 2025-01-31.
Version 10.6.0 is under voting, so we expect to release it in the next days.
Since we are going toward Java 25, we might consider a new main release (11)
based on Java 21 and the last Jakarta EE.
As side note,speaking of Java 25 it's nice to see they have introduced Stable
Values (JEP 502) which are a kind of Wicket Models at JDK level :-) .
## Community Health:
Community is stable and stays healthy and active. Also download statistic stay
high and with a positive trend over the last quarter and year.
-----------------------------------------
Attachment CI: Report from the Apache Zeppelin Project [Jongyoul Lee]
## Description:
The mission of Zeppelin is the creation and maintenance of software related to
A web-based notebook that enables interactive data analytics
## Project Status:
Current project status: Dormant
Issues for the board: The project has some security issues that haven't been
resolved for a long time. They are mostly related to the JDBC connection
string. The PMC and the community try to modify the security model to avoid
JDBC connection string issues.
## Membership Data:
Apache Zeppelin was founded on 2016-05-18 (9 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. The last addition was Cheng Pan on 2024-08-25.
- No new committers. The last addition was Cheng Pan on 2024-08-25.
## Project Activity:
The project follows up supporting the latest version of interpreters and
dependencies, including Apache Spark 4 and PostgreSQL 42.7.7. It also makes
tests stable by fixing flaky tests.
## Community Health:
Open Source Software Contribution Academy(OSSCA), which is supported by The
Korean government started on July 7th this year. 27 new contributors were
invited, and they will participate in the contribution program for 5 months.
It aims to become an active part of the community.
ref. https://s.apache.org/fev1t
------------------------------------------------------
End of minutes for the July 16, 2025 board meeting.
Index