Index
Links: 2025 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
February 19, 2025
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:02 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones:
http://www.timeanddate.com//worldclock/fixedtime.html?iso=2025-02-19T21: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
Shane Curcuru
Willem Ning Jiang
Jeff Jirsa
Justin Mclean - joined :32
Jean-Baptiste Onofré
Craig L Russell
Sander Striker
Kanchana Pradeepika Welagedara
Directors Absent:
none
Executive Officers Present:
Craig R. McClanahan
Matt Sicker
Ruth Suehle
Executive Officers Absent:
David Nalley
Guests:
Alin Jerpelea
Daniel Gruno
Danny Angus
Dave Fisher - joined :07
Gavin McDonald
Greg Stein
Jarek Potiuk
Julien Le Dem
Melissa Logan - joined :04
Myrle Krantz
Niall Pemberton
Paul King
Philipp Ottlinger
Sally Khudairi
Zili Chen
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of January 15, 2025
See: board_minutes_2025_01_15.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Shane Curcuru]
Our recently appointed volunteer VP, Tooling has made great progress
in hiring a team and organizing plans for critical internal tooling
projects that will help all ASF projects meet future legislative
challenges, as well as improve some key internal operations. Many
people have worked on parts of this capacity building, and the future
process improvements this team are working on are a big win for the
ASF as a whole.
The ASF is also holding our Annual Member Meeting next month, where
our nearly 800-strong active Membership will elect new Members to the
corporation as well as a new board to serve for a one year term. The
ASF's broad-based group of individuals who have been elected as
Members - similar to shareholders, each with one vote for the board -
is one of our most important strengths. Our large and active group of
Members elected over the past 25 years ensures our independence from
commercial influences, and ensures electing a board that represents
the breadth of our projects.
B. President [Ruth Suehle]
Budget: Shane requested a preliminary look at next year's budget
plans--this is not an FY26 budget for voting, just a status update.
The operations officers have been gathering their requests for the
FY26 budget. Those are as follows, with notes about FY25 spend so
far:
*General & Administrative $125,000
This was the request for FY25 and was not nearly used. However,
see comment about splits below.
*Brand Management $80,000
This was also the request for FY25; only 45k was needed. Historically similar.
*ComDev $0
Has not made a request. In the FY25 budget, swag spend was
assigned to M&P to promote the new logo; I assume that is likely
to be repeated for FY26.
*Conferences $100,000
*Fundraising $0
Has not made a request. FY25 spend so far was $90,010.
*Infrastructure $1,737,447
Reflects Tooling team additions.
*Privacy $0
Has not made a request. FY25 spend so far was $0.
*Publicity $242,500
*Travel Assistance $55,000
*Treasury $26,280
FY25 actuals so far: $17,297
*Tooling $15,500
*Security $0
Has not made a request. FY25 spend so far was $1,184.
*Governmental Affairs $0
Has not made a request. FY25 spend so far was $16,920.
*Legal Affairs $0
Has not made a request. FY25 spend so far was $0.
Total Expense $2,256,727
Our income for FY25 has been well below target, currently at
~$1,380,000 in sponsorships and public donations against a target of
$2,750,000. We are likely to operate at a loss this year and should
take that into consideration when planning next year's budget. The
new expenses for tooling staff will be offset by donations for that
purpose.
Additionally, please see Attachments 1 through 10.
C. Treasurer [Craig R. McClanahan]
Normal operations continue, with a few specific activities:
* Get Dave Fisher set up in bill.com and ramp.com in prep for managing
the new service providers, along with accounting configuration.
* Assist various officers with information to support budgeting
(including details of transactions in their area of responsibility).
* Assisting one Platinum Sponsor in getting their invoice accepted by
bypassing Coupa (they are set up there, but ability to enter
invoices is not configured yet).
* Initial work on "runbook" type documentation for the various roles
related to Treasury.
D. Secretary [Matt Sicker]
In January 2025, the secretary received 37 ICLAs, one CCLA, one
software grant, and 3 CoI affirmations.
E. Executive Vice President [David Nalley]
No report was submitted.
F. Vice Chair [Justin Mclean]
Nothing of note happened this month. I remain available to support the
Chair when and if needed.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Jeff]
See Attachment 11
B. Apache Legal Affairs Committee [Roman Shaposhnik / Shane]
No report was submitted.
C. Apache Security Team Project [Mark J. Cox / Rich]
See Attachment 13
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# CarbonData [rbowen, jbo]
# Druid [rbowen]
# Fluo [jmclean]
# Geode [rbowen]
# Gora [striker]
# Hop [Kanchana]
# Incubator [rbowen]
# Mnemonic [Kanchana]
# Perl [jmclean]
# RocketMQ [jmclean]
# Samza [rbowen]
# Tez [Kanchana]
# Xalan [Kanchana]
A. Apache AGE Project [Jeff Jirsa]
See Attachment A
B. Apache Ambari Project [Brahma Reddy Battula / JB]
See Attachment B
C. Apache Answer Project [Ning Qi / Kanchana]
See Attachment C
D. Apache Ant Project [Jan Materne / Sander]
See Attachment D
E. Apache BookKeeper Project [Enrico Olivelli / Willem]
See Attachment E
F. Apache Brooklyn Project [Juan D. Cabrerizo / Justin]
See Attachment F
G. Apache BuildStream Project [Tristan Van Berkom / Craig]
See Attachment G
H. Apache CarbonData Project [Liang Chen / Kanchana]
See Attachment H
I. Apache Cassandra Project [Dinesh Joshi / Kanchana]
See Attachment I
J. Apache Celeborn Project [Keyong Zhou / Rich]
No report was submitted.
K. Apache Community Development Project [Swapnil Mane / JB]
See Attachment K
L. Apache CouchDB Project [Jan Lehnardt / Jeff]
See Attachment L
M. Apache Creadur Project [Philipp Ottlinger / Sander]
See Attachment M
N. Apache DataFu Project [Eyal Allweil / Kanchana]
See Attachment N
O. Apache DataSketches Project [Lee Rhodes / Shane]
See Attachment O
P. Apache DeltaSpike Project [Mark Struberg / Willem]
No report was submitted.
Q. Apache Doris Project [Mingyu Chen / Justin]
See Attachment Q
R. Apache Drill Project [Charles Givre / Craig]
See Attachment R
S. Apache Druid Project [Gian Merlino / Rich]
No report was submitted.
@Rich: pursue a roll call for Druid
T. Apache Dubbo Project [Jun Liu / Justin]
See Attachment T
U. Apache Empire-db Project [Rainer Döbele / Willem]
See Attachment U
V. Apache EventMesh Project [Eason Chen / Sander]
See Attachment V
W. Apache Fluo Project [Keith Turner / Shane]
See Attachment W
@Shane: follow up with PMC about PMC merge with Accumulo
X. Apache FreeMarker Project [Dániel Dékány / Craig]
See Attachment X
Y. Apache Geode Project [Mark Bretl / JB]
See Attachment Y
@Rich: follow up on list and clarify governance question
Z. Apache Gora Project [Kevin Ratnasekera / Rich]
See Attachment Z
@Rich: follow up with Gora about potential move to Attic
AA. Apache Groovy Project [Paul King / Jeff]
See Attachment AA
AB. Apache Hop Project [Hans Van Akelyen / Kanchana]
No report was submitted.
AC. Apache HTTP Server Project [Joe Orton / Sander]
See Attachment AC
AD. Apache HttpComponents Project [Michael Osipov / JB]
See Attachment AD
AE. Apache Ignite Project [Dmitry Pavlov / Shane]
See Attachment AE
AF. Apache Impala Project [Zoltán Borók-Nagy / Kanchana]
See Attachment AF
AG. Apache Incubator Project [Justin Mclean / Rich]
See Attachment AG
@Rich: follow up with IPMC
AH. Apache James Project [Benoit Tellier / Craig]
See Attachment AH
AI. Apache Juneau Project [James Bognar / Jeff]
See Attachment AI
AJ. Apache Kafka Project [Mickael Maison / Justin]
See Attachment AJ
AK. Apache Kibble Project [Sharan Foga / Willem]
No report was submitted.
AL. Apache Knox Project [Larry McCay / Justin]
See Attachment AL
AM. Apache Kylin Project [Li Yang / Rich]
See Attachment AM
AN. Apache Libcloud Project [Tomaž Muraus / Justin]
No report was submitted.
@Jean-Baptiste: pursue an Attic resolution for Libcloud
AO. Apache Logging Services Project [Piotr Karwasz / Justin]
See Attachment AO
AP. Apache Logo Development Project [Daniel Gruno / Shane]
See Attachment AP
AQ. Apache ManifoldCF Project [Piergiorgio Lucidi / Rich]
See Attachment AQ
AR. Apache Mnemonic Project [Gordon King / Kanchana]
No report was submitted.
AS. Apache Oozie Project [Dénes Bodó / Willem]
No report was submitted.
AT. Apache OpenOffice Project [Dave Fisher / Sander]
See Attachment AT
AU. Apache OpenWhisk Project [Dave Grove / Kanchana]
See Attachment AU
AV. Apache Ozone Project [Sammi Chen / Craig]
See Attachment AV
AW. Apache Perl Project [Steve Hay / JB]
See Attachment AW
@Jean-Baptiste: follow up with Perl PMC about Infra supported
services for binaries
AX. Apache Phoenix Project [Istvan Toth / Jeff]
See Attachment AX
AY. Apache Pig Project [Koji Noguchi / Craig]
No report was submitted.
AZ. Apache Pinot Project [Kishore G / JB]
No report was submitted.
BA. Apache POI Project [Dominik Stadler / Justin]
See Attachment BA
BB. Apache Qpid Project [Robbie Gemmell / Jeff]
See Attachment BB
BC. Apache Ranger Project [Selvamohan Neethiraj / Shane]
See Attachment BC
BD. Apache RocketMQ Project [Xiaorui Wang / Justin]
See Attachment BD
@Justin: follow up with trademarks about RocketMQ
BE. Apache Roller Project [David M. Johnson / Kanchana]
See Attachment BE
BF. Apache Samza Project [Jagadish Venkatraman / Rich]
No report was submitted.
BG. Apache Santuario Project [Colm O hEigeartaigh / Willem]
See Attachment BG
BH. Apache SDAP Project [Nga Thien Chung / Sander]
See Attachment BH
BI. Apache SeaTunnel Project [Jun Gao / Willem]
See Attachment BI
BJ. Apache Sedona Project [Jia Yu / Jeff]
See Attachment BJ
BK. Apache Serf Project [Daniel Sahlberg / Sander]
See Attachment BK
BL. Apache ServiceComb Project [Bao Liu / Rich]
See Attachment BL
BM. Apache ShardingSphere Project [Liang Zhang / JB]
See Attachment BM
BN. Apache ShenYu Project [Yu Xiao / Justin]
See Attachment BN
BO. Apache SIS Project [Martin Desruisseaux / Shane]
See Attachment BO
BP. Apache Solr Project [Jason Gerlowski / Craig]
See Attachment BP
BQ. Apache Spark Project [Matei Alexandru Zaharia / Kanchana]
See Attachment BQ
BR. Apache Steve Project [Daniel Gruno / Sander]
See Attachment BR
BS. Apache StreamPark Project [Huajie Wang / Jeff]
See Attachment BS
BT. Apache StreamPipes Project [Philipp Zehnder / Justin]
See Attachment BT
BU. Apache Subversion Project [Nathan Hartman / Craig]
See Attachment BU
BV. Apache Superset Project [Maxime Beauchemin / Rich]
See Attachment BV
BW. Apache Syncope Project [Francesco Chicchiriccò / Shane]
See Attachment BW
BX. Apache SystemDS Project [Matthias Boehm / Willem]
See Attachment BX
BY. Apache Tez Project [László Bodor / Kanchana]
See Attachment BY
@Kanchana: pursue a roll call for Samza
BZ. Apache TomEE Project [David Blevins / Justin]
No report was submitted.
CA. Apache Traffic Control Project [Eric Friedrich / Rich]
See Attachment CA
CB. Apache Traffic Server Project [Bryan Call / JB]
See Attachment CB
CC. Apache TsFile Project [Jialin Qiao / Rich]
See Attachment CC
CD. Apache Turbine Project [Georg Kallidis / Sander]
See Attachment CD
CE. Apache Velocity Project [Nathan Bubna / Shane]
No report was submitted.
CF. Apache Web Services Project [Daniel Kulp / Willem]
See Attachment CF
CG. Apache Whimsy Project [Shane Curcuru]
No report was submitted.
CH. Apache Xalan Project [Gary D. Gregory / Kanchana]
See Attachment CH
@Kanchana: pursue a roll call for Xalan
CI. Apache Xerces Project [Michael Glavassevich / Craig]
See Attachment CI
CJ. Apache XML Graphics Project [Clay Leeds / JB]
See Attachment CJ
CK. Apache YuniKorn Project [Wilfred Spiegelenburg / Justin]
See Attachment CK
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Establish the Apache Uniffle Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a unified remote shuffle service.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Uniffle Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Uniffle be and hereby is responsible for the
creation and maintenance of software related to a unified remote
shuffle service; and be it further
RESOLVED, that the office of "Vice President, Apache Uniffle" 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 Uniffle
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Uniffle
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 Uniffle
Project:
* Felix Cheung <felixcheung@apache.org>
* Colin <colin@apache.org>
* Junping Du <junping_du@apache.org>
* Meng Duan <macduan@apache.org>
* Yang Jie <yangjie01@apache.org>
* Zhifang Li <zhifgli@apache.org>
* He Qi <roryqi@apache.org>
* Jerry Shao <jshao@apache.org>
* Zhankun Tang <ztang@apache.org>
* Liu Xun <liuxun@apache.org>
* Weiwei Yang <wwei@apache.org>
* Xianjin Ye <xianjin@apache.org>
* Junfan Zhang <zuston@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that He Qi be appointed to the
office of Vice President, Apache Uniffle, 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.
RESOLVED, that the Apache Uniffle Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Uniffle
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Uniffle podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7A, Establish the Apache Uniffle Project, was
approved by Unanimous Vote of the directors present.
B. Change the Apache ActiveMQ Project Chair
WHEREAS, the Board of Directors heretofore appointed Bruce Snyder
(bsnyder) to the office of Vice President, Apache ActiveMQ, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Bruce Snyder from the office of Vice President, Apache ActiveMQ, and
WHEREAS, the Project Management Committee of the Apache ActiveMQ
project has chosen by vote to recommend Christopher L. Shannon
(cshannon) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Bruce Snyder is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache ActiveMQ, and
BE IT FURTHER RESOLVED, that Christopher L. Shannon be and hereby is
appointed to the office of Vice President, Apache ActiveMQ, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7B, Change the Apache ActiveMQ Project Chair,
was approved by Unanimous Vote of the directors present.
C. Change the Apache CarbonData Project Chair
WHEREAS, the Board of Directors heretofore appointed Liang Chen
(chenliang613) to the office of Vice President, Apache CarbonData, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Liang Chen from the office of Vice President, Apache CarbonData, and
WHEREAS, the Project Management Committee of the Apache CarbonData
project has chosen by vote to recommend Jacky Li (jackylk) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Liang Chen is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache CarbonData, and
BE IT FURTHER RESOLVED, that Jacky Li be and hereby is appointed to the
office of Vice President, Apache CarbonData, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache CarbonData Project Chair,
was approved by Unanimous Vote of the directors present.
D. Change the Apache Lucene Project Chair
WHEREAS, the Board of Directors heretofore appointed Chris Hegarty
(chegar) to the office of Vice President, Apache Lucene, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Chris Hegarty from the office of Vice President, Apache Lucene, and
WHEREAS, the Project Management Committee of the Apache Lucene project
has chosen by vote to recommend Dawid Weiss (dweiss) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Chris Hegarty is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Lucene, and
BE IT FURTHER RESOLVED, that Dawid Weiss be and hereby is appointed to
the office of Vice President, Apache Lucene, 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 Lucene Project Chair, was
approved by Unanimous Vote of the directors present.
E. Change the Apache AsterixDB Project Chair
WHEREAS, the Board of Directors heretofore appointed Till Westmann
(tillw) to the office of Vice President, Apache AsterixDB, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Till Westmann from the office of Vice President, Apache AsterixDB, and
WHEREAS, the Project Management Committee of the Apache AsterixDB
project has chosen by vote to recommend Ian Maxon (imaxon) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Till Westmann is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache AsterixDB, and
BE IT FURTHER RESOLVED, that Ian Maxon be and hereby is appointed to
the office of Vice President, Apache AsterixDB, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7E, Change the Apache AsterixDB Project Chair,
was approved by Unanimous Vote of the directors present.
F. Change the Apache Maven Project Chair
WHEREAS, the Board of Directors heretofore appointed Karl Heinz
Marbaise (khmarbaise) to the office of Vice President, Apache Maven,
and
WHEREAS, the Board of Directors is in receipt of the resignation of
Karl Heinz Marbaise from the office of Vice President, Apache Maven,
and
WHEREAS, the Project Management Committee of the Apache Maven project
has chosen by vote to recommend Hervé Boutemy (hboutemy) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Karl Heinz Marbaise is relieved
and discharged from the duties and responsibilities of the office of
Vice President, Apache Maven, and
BE IT FURTHER RESOLVED, that Hervé Boutemy be and hereby is appointed
to the office of Vice President, Apache Maven, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7F, Change the Apache Maven Project Chair, was
approved by Unanimous Vote of the directors present.
G. Change the Apache OpenOffice Project Chair
WHEREAS, the Board of Directors heretofore appointed Dave Fisher (wave)
to the office of Vice President, Apache OpenOffice, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Dave Fisher from the office of Vice President, Apache OpenOffice, and
WHEREAS, the Project Management Committee of the Apache OpenOffice
project has chosen by vote to recommend Keith McKenna (knmc) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Dave Fisher is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache OpenOffice, and
BE IT FURTHER RESOLVED, that Keith McKenna be and hereby is appointed
to the office of Vice President, Apache OpenOffice, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7G, Change the Apache OpenOffice Project Chair,
was approved by Unanimous Vote of the directors present.
H. Terminate the Apache Oozie Project
WHEREAS, the Board of Directors deems it no longer in the best interest of the
Foundation to continue the Apache Oozie project due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Oozie 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 Oozie Project; and be it further
RESOLVED, that the office of "Vice President, Apache Oozie" is hereby
terminated; and be it further
RESOLVED, that the Apache Oozie PMC is hereby terminated.
Special Order 7H, Terminate the Apache Oozie Project, was
approved by Unanimous Vote of the directors present.
I. Terminate the Apache Mnemonic Project
WHEREAS, the Board of Directors deems it no longer in the best interest
of the Foundation to continue the Apache Mnemonic project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Mnemonic 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 Mnemonic Project; and be it
further
RESOLVED, that the office of "Vice President, Apache Mnemonic" is
hereby terminated; and be it further
RESOLVED, that the Apache Mnemonic PMC is hereby terminated.
Special Order 7I, Terminate the Apache Mnemonic Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Simplifying key mailing list moderation
Review ideas for simplifying volunteer work in key lists moderation.
B. MFA
MFA is widely understood to be critical to security, with the CISA
recommending it be enabled for any internet-facing application
https://www.cisa.gov/sites/default/files/publications/MFA-Fact-Sheet-Jan22-508.pdf
Within the ASF, those who would implement MFA have paused on the
assertion that the foundation does not currently collect enough
information to handle MFA reset requests, which makes enforcing MFA
itself problematic. This is complicated by the reality that the team
that would implement MFA (Infra) is not in charge of the data
collection (Secretary), and the workflow and tooling that the
Secretary uses today is likely insufficient at managing refreshing
contact information for use in an MFA flow.
This agenda item is to discuss and agree on a path forward, such as:
- The board confirming that this is a desired capability to build
- Identifying existing offices and officers who need to define policy
or create tooling requirements
- Prioritizing the implementation of that tooling against other
proposed tooling
The board reviewed this and agrees with the security team
recommendations.
C. Review F2F outcomes and recommendations
Brief discussion of 2024 Board F2F action outcomes and reflection on
any unfinished proposals that the current board wishes to recommend
that next year's board review or consider.
@Rich: start document for board year hand-off
9. Review Outstanding Action Items
* Shane: update Incubation guidelines to include trademark grant
[ Trademark management status briefing VP, Brand Management 2024-07-17 ]
Status:
* Jeff: Start discussion of communications on board@ specifically the use of
[ New Business 2024-09-18 ]
Status:
* Kanchana: pursue a roll call for PMC
[ CarbonData 2024-10-16 ]
Status: Roll call handled in Nov 2024 . only 2 PMC responded.
https://lists.apache.org/list?private@carbondata.apache.org:2024-11
(+1 and -1)
* Craig McClanahan: pursue an audit on ramp cards
[ Review expense accounting categories 2024-10-16 ]
Status:
* Kanchana: pursue a roll call for Mnemonic
[ Mnemonic 2024-11-20 ]
Status: We didn't have PMC votes.
* Kanchana: pursue a roll call for DataFu
[ DataFu 2025-01-15 ]
Status: Performed the roll call on Feb-04 and got 3 PMCs votes
* Kanchana: follow up with PMC Chair and PMC regarding community health
[ Fineract 2025-01-15 ]
Status: Rich and I virtually met and observed the different dynamics
of their fintech representatives on a zoom meet up and
listened to their challenges. Private list communication is
available here.
https://lists.apache.org/list.html?dev@fineract.apache.org The
major issue they face is a cultural challenge in —users are
not contributing back and have not learned from past
experiences of failing to do so. Thanks to Justin, Rich and I
reviewed their internal community data and found that most of
the heavy PR work is handled by just two PMC members, while
contributors are not actively participating—year-over-year
contribution by contributors remains at 0%. The organizations
that have signed up for the project do not appear to have
teams or divisions focused on open source , inner sourcing or
CoC to educate contributors . Those present were mostly
enthusiastic about seeking the board’s help in educating these
entities and are looking to take action. The upcoming CoC and
Fineract track will be valuable opportunities to bring their
community together and talk about supply chain and SSDF . Rich
and I have offered our continued support to shape up their
community health.
* Sander: pursue a roll call of PMC
[ Griffin 2025-01-15 ]
Status: Not done. Instead of singling out this project to do a roll
call after 6 months of no release, I'm going to work this into
the reporting proposal to make roll call for this reason
expected rather than seemingly arbitrary in the context of all
other projects.
* Rich: ensure IPMC is helping with board reports
[ Incubator 2025-01-15 ]
Status: DONE
https://lists.apache.org/thread/byzl9ckvxty4lozf91fygn603hdh0hg3
* Rich: follow up with roll call for Mesos PMC
[ Mesos 2025-01-15 ]
Status: DONE
https://lists.apache.org/thread/978860xg20k8kss56cob8vff5sbxpd6m
Based on that response, the project just barely meets the
absolute minimum of project oversight, although not sufficient
to be considered an active project.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 21:56 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period January 2025
* ISSUES FOR THE BOARD
None.
* OPERATIONS
- Reviewed event requests for ICEBERG and CLOUDSTACK
- Provided advice on how the ASF allows logos to be used
- Provided advice to GRAILS
* REGISTRATIONS
Worked with counsel to progress the registration of OPENDAL.
* INFRINGEMENTS
Provided OPENOFFICE with advice regarding a potential infringement.
Discussed a potential infringement of our GUACAMOLE mark with the PMC.
Discussed a potential infringement with the KAFKA PMC.
Discussed an ongoing, potential infringement with the AGE PMC.
Made some progress regarding the downstream vendor with multiple infringements
of ASF marks.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a —New: no new Sponsors were onboarded during this timeframe.
b —Renewals: we successfully secured renewal commitments from two Platinum,
one Gold, two Silver, and one Bronze Sponsor. In addition, we have confirmed a
renewal upgraded to the Platinum level.
c —Payments: 1 —New: we received no new Sponsor payments during this
timeframe.
2a —Renewing: we received renewal payments from three Gold, one Silver,
and one Bronze Sponsor.
2b —Incoming: we await payment from two renewing Platinum, two renewing
Silver, and one renewing Bronze Sponsor.
2) Targeted Sponsors: we have successfully finalized two Targeted Platinum and
one Targeted Silver Sponsorship renewals. We are also in discussions with a
potential lead funder for the new ASF Tooling Initiative.
3) Sponsor Relations: our Sponsor communications are ongoing, with additional
one-on-one meetings to discuss charitable giving options. We are planning our
next quarterly call with Gold and Platinum Sponsors, which will likely take
place towards the end of Q1.
4) Event Sponsorship: we are standing by to assist with new event sponsorship
benefits extended to ASF Platinum and Gold Sponsors once details are available
for Community Over Code North America 2025.
5) Individual Donations and Corporate Giving: we received $5,450 in online
donations via https://donate.apache.org/ , which included one corporate
contribution.
6) Administrivia: we continue to liaise with the Accounting and Treasury teams
on invoicing and recovering payments. We are working with Marketing &
Publicity to announce the ASF’s new Tooling Initiative and launch its
fundraising campaign.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Foundation Comms
* 2024 Year in Review and 2025 Strategic Planning
* Issued January edition of the Plus One Newsletter
* ASF gained 15 new subscribers in January totalling 98 subscribers
* Launched the ASF’s Bluesky channel
* Discussed with Fundraising other ways to support sponsors with publicity
* TechTarget story on CRA requesting input from Dirk-Willem van Gulik
Project Comms
* Wrote and distributed press release touting two newly graduated TLPs: Apache
Answer and Apache StreamPark
Foundation Content
* Published twelfth #ASFFirstContribution blog post featuring code
contributors for Apache Arrow, Apache Cassandra, Apache Directory, Apache
Flink, and Apache Kafka.
Social Media Overview ASF’s Bluesky was launched in January 2025 and the
response so far has been positive. ASF’s Twitter channel continues to lose
followers (net follower growth for 2024 was -75). LinkedIn is the ASF’s
largest source of channel engagement.
Social Highlights (X + LinkedIn + Bluesky)
* Total Audience: 141,734
* New Followers in January: 534
* Twitter: -248
* Bluesky: 386
* LinkedIn: 396
* Total Posts: 87
* Twitter: 36
* Bluesky: 36
* LinkedIn: 15
* Total Engagements: 3,413 (1.0% increase MoM)
Social Media Channel Analysis
#1 LinkedIn
* Number of members: 1 billion
* Largest age group: 25-34 (60%)
* Gender distribution: 43.7% female, 56.3% male
LinkedIn’s daily active, engaged users are on the rise, making it ideal for
B2B content marketing. For ASF, LinkedIn has shown nearly 2% YoY increase in
engagement and nearly 8% YoY increase in followers.
#2 Bluesky
* Number of users: 27.44 million (gains ~5.4 users/second)
* Largest age group: 25-34 (22%%)
* Gender distribution: 50% female, 50% male
ASF launched Bluesky in Jan 2025, so there is limited data for ROI. However,
ASF gained 300+ followers in January alone, equivalent to the number of
followers ASF lost on X in the same month.
#3 X (formerly Twitter)
* Number of monthly active users: 368 million
* Largest age group: 25-34 (38.5%)
* Gender distribution: 37% female, 63% male (overwhelmingly large male user
base)
While X has more active users than Bluesky, the data trends for ASF’s X
channel mark an 82% decline in engagement and a <1% increase in audience (the
ASF loses more followers than gains MoM).
#4 Mastodon
* Number of monthly active users: 10 million
* Largest age group: 25-34 (26.24%)
* Gender distribution: 35% female, 65% male (overwhelmingly large male user
base)
ASF has yet to pursue Mastodon due to declining user base and barriers to
entry for new users.
Website Analytics
* 837,973 visits, 837,935 unique visitors +23.5%
* 2 min 49s average visit duration -1.2%
* 47% visits have bounced (left the website after one page) -2.1%
* 5.9 actions (page views, downloads, outlinks, internal site searches) per
visit +1.7%
* 10,001 max actions in one visit (level)
* 4,217,286 pageviews, 1,046,333 unique pageviews +36.7%
* 3 total searches on your website, 3 unique keywords -62.5%
* 345,597 downloads, 254,131 unique downloads +24.9%
* 329,474 outlinks, 210,806 unique outlinks -39.3%
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Myrle Krantz]
General
=======
Infrastructure is operating at reduced staffing, and support gaps are
becoming apparent. Hiring is due to commence mid-Q1 2025. Per VP Infra
we will be opening two junior/mid-level sysadmin staff positions to
hire hopefully in Q1.
Finances
========
- Infra has received a targeted donation of $25k/yr in support of Cassandra
build nodes.
- 2024 Personnel-related expenses were significantly under budget due to
staffing changes.
- FY25 Infra budget identified and submitted (pending VP review).
Hiring
======
- Infra staff developing updated job description(s) for the open sysadmin
position(s), to hire during Q1 2025.
Travel
======
- Infra Team F2F likely to happen in late May/early June 2025.
Major Projects
==============
- The Jira -> GitHub Issues migration tool is working and has successfully
migrated several projects.
- In cooperation with a number of volunteers within our Builds/CI community,
a process to streamline and democratize the approval of GitHub Actions is
in the initial phases of rollout.
- Infra continues to work with our partners at Gradle to improve the functionality
and performance of our donated Gradle Develocity stack. A large upgrade was
successful in January.
- An organization-wide CSP (Content-Security-Policy) is slated to be rolled out on
February 1st (brownout), going into full effect on March 1st, 2025. Initial
brownout found a number of affected sites, and remediation work in ongoing.
- Next iteration of our .asf.yaml control file for Git repositories is to be
announced soon along with a rollout plan.
-----------------------------------------
Attachment 5: Report from the VP of Tooling [Dave Fisher]
Tooling Team Report
We are contracting two Senior Software Engineers, Tooling. One started on
February 1, and the other officially starts on March 1. Those are the contract
dates. The team has already established a good working relationship.
## Projects
Working documentation can be found on github here:
- https://github.com/apache/tooling-docs/.
### Apache Trusted Release
1. We have requirements and a framework plan for the first part of the work.
2. Work has started in an "experimental repository".
### Board Agenda Tool
1. An experimental whimsy installation was created so that we have a working
reference to study.
2. We will study the read only tool to see what the remaining requirements
are.
3. We will be ready to confirm true requirements once the new Board has
established itself in March.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Brian Proffitt]
Community Over Code NA 2025
The event will be held at the Hyatt Regency Minneapolis, in Minneapolis, MN,
Sept 11-14, 2025. Right now, call for tracks is open until Feb 24, and then we
hope to open CFP the first week of March, and registration for attendees by
the end of March. The prospectus will be ready to share, ideally, in early
March.
We already have potential venues for the TAC, speaker, and all-attendee
events, and will be coordinating with all relevant parties in the weeks ahead.
We are pretty excited about this year's event, because we are going to
introduce new community-building sessions and activities that will enable ASF
participants to share the things that interest them, and create event content
in an even more collaborative manner.
Community Over Code Asia 2025
The Community Over Code Asia 2025 has about 16 tracks so far. Comparing to
last year， organizers added Rust and Observer tracks, and removed the
Performance track.
Except for the general and keynote, we have 33 track chairs to help us with
the conference.
We will announce the CFP of the CoC Asia 2025 shortly.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Previous Events
===============
Community Over Code EU/Asia/NA 2024
----------------------------
Without a volunteer to complete surveys from these 3 events, Gavin
will look forward to doing them over the next few weeks.
Current Events
==============
Community Over Code Asia
------------------------
Applications just opened up yesterday for Beijing, and applications
will close around the 9th May.
Monthly Meetings
================
The next meeting will be held first week of March.
TAC App
=======
TAC app is open for applications for China currently.
Future Events
=============
Community over Code NA has been announced to be held in Minneapolis in
September. TAC looks forward to opening up applications for that event
in the next month or so.
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
=====================
Some activity around the new Budget, and opening of applications for
China.
We also got asked to help out a project with their Travel plans/budget
for their event happening in April (Apache Iceberg Summit). Gavin is
working with them on the scope of that need - do they require the app,
for example, or just advise, or liaise with a travel agent etc.
Membership
==========
No changes to the Committee this month.
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [David Nalley]
-----------------------------------------
Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
Per request of Criag - as a link so he can edit it easier:
https://docs.google.com/document/d/1x4clsd2MnNFIQopGGSz__zdQtwGUG5jsvONt7jVzyIE/edit?tab=t.0
Open Source / Policy Week Brussels
- The ASF, with a bunch of our open source peers, met face to face with
ENISA/CISA in the days before FOSDEM.
Meeting positive; starting to build understanding and convey how security is
handled in the IT industry in general and in open source in particular.
Arnoud, Lars, Mark, Jarek and I represented the ASF. With Eclipse, OpenSSF,
Python, Rust, OWASP, etc present.
We only covered a fraction of the agenda - so will see if we can do another
cycle to actually cover some of the agenda; it appeared there was appetite
for this / was found useful.
Ideally I’d like to get to a situation where the next edition is hosted by
CISA (perhaps colocated with a large event in the US). And, slightly longer
term, I would like to see if we can also gently ask the Chinese and other
equivalents of CISA/ENISA if they want to be involved/host this on some
rotating basis.
- This was followed by the Open Source Academy Award; a new thing. Which is an
attempt to give open source some of the instruments that fields such as
science have to more easily integrate into polite society. Organised by OFE
and supported by the EC, the hope here is that this can become something
akin the various Royal Academies of Sciences or the Académie Française.
Well attended. Well received.
- Open Source Policy day was held on Friday - very well attended; with clearly
every year a larger group of key policy/decision makers. Ruth represented
the ASF on stage in one of the panels.
- Good set of F2F workshops around the CRA; hosted by the Open Regulatory
Working Group. Well organised.
With a solid/near complete attendance of all main open source and a lot of
the relevant industry players present.
Very positive - the community as a whole is now well beyond the point of
upset, anger or inactivity. Instead the event quickly turned into a real
workshop with real work being done. Main place is https://github.com/orcwg -
and increasingly using the tools and habits of open source.
Also - focus is now clearly shifting from politics to practical
implementation and technology. We can use a bit more ASF voice (and I should
communicate a bit more publicly now to those who only know about the CRA/PLD
from HN and slashdot) - but no concerns/going into the right direction.
Ill timed OFAC list concerns voiced by LF
- LF publicly expressed concerns about its ability to interact with people and
entities on the OFAC list.
Which was easily/generally misunderstood or misread as a very generic
`lawyers now suddenly say that we as open source people cannot work with our
Russian peers’. Forgoing the specifics of LF, the way it finances/interacts
and so on. With people jumping to conclusions and assuming it is a `new
disastrous thing’.
Worked with Ruth/Roman to be in a position to explain the situation from an
ASF perspective & had to emphasise to various policy makers that there are
large differences between our type of open source and other, more
commercial/contractor-ran open source.
But mostly repeat that while the ASF of course will adhere to US law and
regulation and that we have taken things as the OFAC list, Export
Administration Regulation, Denied parties list and embargoed destination
serious for over 25 years. And that this is nothing new, etc, etc for us.
- FOSDEM - good show by all involved; special policy room on the CRA. Not seen
the output of the interactive sessions yet - but engagement was positive and
pro-active. If we are not careful :grin: Open Source may end up pushing the
security/resiliance aspect of the CRA harder than the policy makers
intended.
- Meeting of most open source foundations F2F on the CRA and the AI act; under
OFE chatham house rules.
Was helpful to prepare of the CRA Expertmeeting (a formal body of the EC in
which the ASF has a seat to help with the details/guidance of the CRA as it
is implemented). The situation for non-affiliated open source contributors
shapes up in the right direction (i.e. the CRA impacts the downstream; not
them so much). But my main concern is still with both budding, new, not yet
formalised open source (much like the ‘Apache Group’ was for 5+ years), and
peers, such as for example in the Linux distribution space; who are too ill
defined. So lets hope that we can use the CRA-Expert meeting to get some
formal guidance/fixes for this.
Also clear from this meeting - and the statements made earlier at the ORC
workgroup - is that open source participation in the normative standards
organisation is still a complete no-go area. These organisation are not
moving one inch. I’ll be posting about a `hack’ the EU has dreamt up to work
around this (basically grants of 5, 10 and 30k euro/year for private
individuals) & associated call to action early March. But this too falls well
short. So the ORC work at Eclipse and the work of people, like Lars & other
people at companies that have access, in our community become crucial.
Attended by Craig (both) and me (just CRA).
CRA Expert meeting First meeting; ASF present as one of the 3 organisations
representing open source. Quite a good and productive meetings as things go.
Public minutes expected at the beginning of next week.
USA - well :) let’s not wait with bated breath. We may turn purple. But would hope that at some point work on the various open source policies goes back to normal scheduled programming.
-----------------------------------------
Attachment 11: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 12: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
-----------------------------------------
Attachment 13: Report from the Apache Security Team Project [Mark J. Cox]
January
* Following our escalation process we will move Apache Oozie to the
attic. As there has been some activity around the known security
issues we have set the date for retirement to February 15, 2025, to
give the project a chance to create a final release with those fixes
before that.
* We have continued work on the Apache SBOM navigator, making
deployment more reliably and adding project-specific views (e.g.
https://sbom.security.apache.org/project.html?pmc=orc)
* We published an 'unsupported when assigned' CVE for an open issue in
Cocoon, who have retired to the Attic.
* We participated in a number of events around FOSDEM including on the
CRA together with public policy, CISA, ENISA and other foundations,
and security and license compliance tooling.
Stats for January 2025:
63 [license confusion]
18 [support request/question not security notification]
13 [report/question relating to dependencies]
Security reports: 59 (last months: 67, 84, 76, 72)
6 ['website or other infrastructure']
5 ['huntr']
4 ['airflow', 'tomcat']
3 ['spark']
2 ['activemq', 'httpd', 'nifi', 'openoffice', 'superset', 'zookeeper']
1 ['answer', 'arrow', 'camel', 'cassandra', 'cloudstack',
'commons', 'directory', 'echarts', 'flink',
'geronimo', 'hertzbeat', 'hugegraph', 'iceberg',
'jackrabbit', 'kafka', 'kylin', 'lens', 'nuttx',
'pdfbox', 'pinot', 'plc4x', 'shiro', 'sling',
'trafficserver', 'xerces']
In total, as of 1st February 2025, we're tracking 182 (last months:
179, 168) open issues across 65 projects, median age 105 days (last
months: 86, 117). 60 of those issues have CVE names assigned. 11
(last month: 15, 17) of these issues, across 10 projects, are older
than 365 days.
* oozie: not making releases (Health red): Project is dormant, unable
to respond to security reports, and will be moved to the
Attic. Oozie community have been notified that Oozie will move to
the Attic on February 15
2025. https://lists.apache.org/thread/zbc1xxt0v7n6lffpqbtjltkkq9vhtosg
(Last update: 2025-01-15)
* 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:
2024-11-01)
* geode (Health amber): Four issues in Geode over 365 days old. The
project has voted to move to the Attic, but there might be a chance
of revisiting that decision if relevant stakeholders successfully
join the effort. We continue to engage with Geode to return to
health. (Last update: 2025-02-03)
* openoffice (Health amber): Three issues in OpenOffice over 365 days
old and a number of other open issues not fully triaged. (Last
update: 2024-11-21)
* zeppelin (Health amber): has a history of not dealing with security
issues (Last update: 2025-02-03)
-----------------------------------------
Attachment A: Report from the Apache AGE Project [Jeff Jirsa]
## Description:
The mission of Apache AGE is the creation and maintenance of software related
to a multi-model database that enables graph and relational models built on
PostgreSQL
## Project Status:
Current project status: Ongoing, though low activity
Issues for the board: Ongoing conversation with trademarks@, but no additional
help required from the board
## Membership Data:
Apache AGE was founded 2022-05-17 (3 years ago) There are currently 18
committers and 12 PMC members in this project. The Committer-to-PMC ratio is
3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Rafsun Masud on 2024-01-28.
- No new committers. Last addition was Zainab Saad on 2024-01-31.
## Project Activity:
The last commit to the main branch of the the primary AGE repository was 5
months ago. There is work in flight for postgres 17 compatibility.
The PMC chair has sent out two emails to the PMC inquiring:
- Which community members may be appropriate for additional merit
(contributors becoming committers, committers becoming PMC members).
- Which existing PMC members are active and willing to help with releases.
Multiple positive responses have been received, but the email was not yet
72h old at the time of this report.
## Community Health:
The community has noticed the drop in commits and have asked reasonable
questions. It will be important in the coming quarter to demonstrate that the
project is healthy with the existing committers, or that the project can find
new contributors, or evaluate whether or not the project needs to go to the
attic.
Given the churn, this should not be rushed, but the current trend is
unsustainable.
-----------------------------------------
Attachment B: Report from the Apache Ambari Project [Brahma Reddy Battula]
## Description:
The mission of Apache Ambari is the creation and maintenance of software
related to Hadoop cluster management
## Project Status:
Current project status: Ongoing with moderate
Issues for the board: none
## Membership Data:
Apache Ambari was founded 2022-06-15 (3 years ago)
There are currently 21 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Mohammad Arshad on 2024-05-05.
- No new committers. Last addition was Jialiang Cai on 2024-07-26.
- There are ongoing discussions on committer and PMC
## Project Activity:
Planning to release ambari-3.0 which is major release.
Recent releases:
2.7.9 was released on 2024-12-20.
## Community Health:
Overall Health is good. Activy developement is happening on UI/spring upgrade.
-----------------------------------------
Attachment C: 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: New
Issues for the board: none
## Membership Data:
Apache Answer was founded 2024-12-18 (2 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 (project graduated recently).
- No new committers were added.
## Project Activity:
- We have completed all major tasks for graduating from the incubator.
- We updated the relevant information on our official website and published a
press release to celebrate our graduation.
- We started using the new release process for publishing version
- We've released version 1.4.2-RC2. Since most of the development team is on
Chinese New Year holiday, the official release is postponed to mid-February.
## Community Health:
In January, we welcomed 1 new plugin contributor and 7 new translation
contributors to the project, reflecting ongoing community interest in
expanding our plugin ecosystem and making Apache Answer more accessible in
multiple languages. While there were no new committers added this quarter, we
continue to identify and mentor potential candidates for committership.
Overall, the mailing lists remain active with steady user and developer
engagement, and we look forward to further growth and collaboration in the
coming months.
-----------------------------------------
Attachment D: 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.
## 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.
On the Ivy project front, during the last year we had discussions
with the community to let them know that the current Ant PMC is finding
it difficult to manage and relase Ivy project. We were hoping that
it would encourage users of Ivy to consider maintaining the project.
Maarten Coene, who's part of the Ant PMC volunteered to help manage
the Ivy project and help with bug fixes and releases
https://lists.apache.org/thread/nj1mlk81q01kvmgffsd7s7ztt4qb7jw7.
That's very good news.
Continuing with that, thanks to Maarten, we recently released
Ivy 2.5.3 version
https://lists.apache.org/thread/k74o3roz1x9r32hj8o60w1mt5lhr3by1
## 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, this amount of
activity, I believe, is decent.
Ivy project has recently seen a new release, which is good
news too.
-----------------------------------------
Attachment E: Report from the Apache BookKeeper Project [Enrico Olivelli]
## Description:
The mission of BookKeeper is the creation and maintenance of software related
to Replicated log service which can be used to build replicated state machines
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache BookKeeper was founded 2014-11-19 (10 years ago)
There are currently 32 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Zhangjian He on 2024-06-14.
- Zhangjian He was added as committer on 2025-01-27
## Project Activity:
We need to cut new releases, as latest releases happened months ago. The main
reason is that we have not found criticial issues recently and so the
motivation for cutting releases is lower.
4.16.6 was released on 2024-06-26.
4.17.1 was released on 2024-06-26.
4.16.5 was released on 2024-04-03.
## Community Health:
PRs are coming, especially from new contributors, this is kind of new for us.
But on the other end we are accomulating some backlog of PRs to review. We
will follow up within the PMC to push for more reviews.
Overall I would say that we are in a better health than months ago when we had
fewer patches coming from new contributors.
-----------------------------------------
Attachment F: Report from the Apache Brooklyn Project [Juan D. Cabrerizo]
## Description:
The mission of Apache Brooklyn is the creation and maintenance of software
related to a software framework for modeling, monitoring and managing cloud
applications through autonomic blueprints.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Brooklyn was founded 2015-11-18 (9 years ago)
There are currently 20 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Iuliana Cosmina on 2021-06-04.
- No new committers. Last addition was Mykola Mandra on 2022-03-08.
## Project Activity:
Added production-readiness features:
* better retries when working with vault and other secrets managers
* better logging for security, including log-in/log-out and
suppression of sensitive values in script output
* UI support for choosing between default values and inherited
values when deploying a blueprint
* LDAP support for recursive group membership when determining
permissions
* REST responses security: do not return webserver version, option
to omit stack traces
## Community Health:
21 commits in the past quarter
One of the key topics in the last period was to prevent leak information on
logs, reported by a new group of users
-----------------------------------------
Attachment G: Report from the Apache BuildStream Project [Tristan Van Berkom]
## Description:
The mission of Apache BuildStream is the creation and maintenance of software
related to efficiently and correctly developing, building and integrating
software stacks
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache BuildStream was founded 2022-09-21 (2 years ago)
There are currently 6 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Abderrahim Kitouni on 2022-09-21.
- No new committers were added.
## Project Activity:
Fairly high activity with the addition of SourceMirror plugins released in
december with BuildStream & buildstream-plugins 2.4.0.
## Community Health:
Regular activity in github as usual.
Discussion on extending APIs for creating SBoMs on the list.
Considering onboarding new committers.
-----------------------------------------
Attachment H: Report from the Apache CarbonData Project [Liang Chen]
## Description:
- The Apache CarbonData is data store solution for fast
analytics on Big Data platforms (including Apache Hadoop, Apache Spark,
Apache Flink among others) to help speed up queries an order of magnitude
faster over petabytes of data, with the aim of using a unified file format
to satisfy all kinds of data analysis cases.
## Issues:
- The community need to consider, just maintain the existing feature for
version stability or encourage new contributors to do more new features,
need to discuss in community.
## Activity:
- As CarbonData PMC discussion, we already submitted : Change CarbonData
Chair, the resolution will be reviewed by board meeting of Feb
- Optimize the community building https://github.com/apache/carbondata/pull/4358
- Upgrade Thrift version : https://github.com/apache/carbondata/pull/4355,
https://github.com/apache/carbondata/pull/4356
- Upgrade spark version : https://github.com/apache/carbondata/pull/4354
- hulk as new contributor, optimized documents
## Health Report:
- Commit activity:
- 8 commits in the past quarter
- 4 code contributors in the past quarter
## Releases:
* currently , community is working for upgrade spark version :
https://github.com/apache/carbondata/pull/4354
* 2.3.1 was released on 2023-11-25.
* 2.3.0 was released on 2022-01-24.
* 2.2.0 was released on 2021-08-05.
-
## Project Composition:
There are currently 28 committers and 19 PMC members in this project.
- The Committer-to-PMC ratio is roughly 7:5
Community changes, past quarter:
- Bo Xu was added to the PMC on 2023-04-22
- Brijoo Bopanna was added to the PMC on 2022-09-24
- Indhumathi was added to the PMC on 2022-02-16
- Vikram Ahuja was added as committer on 2022-02-10
- Akash R Nilugal was added to the PMC on 2021-04-11
## Notable mailing list trends:Mailing list activity stays at a high level
- dev@carbondata.apache.org:
- 155 subscribers (change 8):
- dev@carbondata.apache.org had a 59% decrease in traffic in the past
quarter (14 emails compared to 34):
## Github issues activity:
- 5 issues be handled
## Github PR activity:
- 3 PRs opened on GitHub, past quarter
- 4 PRs closed on GitHub, past quarter
-----------------------------------------
Attachment I: Report from the Apache Cassandra Project [Dinesh Joshi]
Are you able to provide adequate oversight of your project? That is, are there
at least three PMC members who are engaged enough to respond in the event of a
CVE or similar crisis?
Yes. There are many PMC members actively participating in dev and private list
conversations. The recent roll call was responded to by 22 PMC members
compared to 19 in the previous roll call.
Are there current or upcoming risks that threaten the sustainability of your
project? This could be anything from a change in employment of prolific
contributors, to an acquisition affecting a significant corporate contributor,
to a change in the technology landscape that makes your project less (or more)
relevant.
No current or upcoming risks known at this time. We continue to expand the
roster of the PMC with individuals with diverse corporate sponsorship
backgrounds as well as representation of our sub-projects. The PMC has been
discussing ways to establish a list of candidates for Committers and PMC
members. There are 2 active VOTE threads for Committers on going and
discussions around adding new PMC members with healthy debate. As mentioned in
the past report, 2024 saw a shift in resourcing in companies’ investment of
employees’ time to the project. We have seen the void being filled by other
individual contributors from the community which is a good sign that the
community is adapting to shifting resourcing. It is also creating space for
new contributors to drive different areas of the project. The project released
new versions of the Cassandra server and Java drivers. The project also
addressed concerns about content violating ASF’s trademarks.
What can the Foundation do to more effectively make your project more
successful in its mission of providing software for the public good?
Same as last report – It would be helpful for the Foundation to support the
project in areas such as infrastructure to periodically scan for security
vulnerabilities, PMC-private vulnerability report tracking, additional self
service options for qbot configuration, dockerhub repository creation, etc.
-----------------------------------------
Attachment J: Report from the Apache Celeborn Project [Keyong Zhou]
-----------------------------------------
Attachment K: Report from the Apache Community Development Project [Swapnil Mane]
## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: None
## Membership Data:
Apache Community Development was founded 2009-11-01 (15 years ago)
There are currently 52 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Drew Foulks on 2024-08-30.
- No new committers. Last addition was MJ Foulks on 2024-10-29.
## Project Activity:
### ComDev Website Improvements
We revamped the Community website’s [ComDev1] home page by updating its layout.
The new design removes large text-only boxes and replaces them with images that
link to relevant sections of the website, making it easier for users to find
information on each topic.
We also rewrote the Contributors’ page [ComDev2]. It provides essential
details and links to resources that guide new contributors on how
to get started and progress with Apache projects.
Thanks to Rich Bowen and Bertrand Delacretaz for these improvements.
[ComDev1] - https://community.apache.org/
[ComDev2] - https://community.apache.org/contributors/
### Google Summer of Code 2025
We have submitted the application for Google Summer of Code 2025 and started
collecting project ideas [GSOC1]. The GSoC team is
currently reviewing all applications. The list of accepted mentoring
organizations will be published on February 27, 2025.
Interested students have begun engaging in this activity and are asking their
queries on the mailing list.
[GSOC1] - https://s.apache.org/gsoc2025ideas
### ALC
ALC Beijing and other ALCs are actively preparing for the Community Over Code
Asia 2025 conference, which will take place in Beijing, China, from July 25 to
July 27, 2025.
There is interest in establishing an ALC in Islamabad, Pakistan. However, we
did not find enough ASF and PMC members for it. Given Alina Kazi’s
(Apache Royale PMC member) commitment, we are exploring options to assign
mentors from existing ALCs to support this ALC establishment. Hopefully, we will
reach a final decision on this within this quarter.
### Others
We also had discussions on the list around consensus to make
release candidates publicly accessible during the voting period.
And to update project maturity model to include trademark and branding.
Background: During the graduation of podlings from incubation, we
actively evaluate their treatment for trademark and branding. However,
this is not reflected in our maturity model and can result in the
friction of tribal knowledge.
Thanks to Zili Chen for taking care of this. The Trademark and Branding
section is added to Apache Project Maturity Model page and is live at
https://s.apache.org/pmm-trademark-and-branding
## Community Health:
This quarter, we saw moderate activity on mailing list (29% decrease in
mailing list traffic compared to the previous quarter). Seems this was
mainly due to two reasons: first, we wrapped up Community Over Code in
October, post confererence, causing a slight slowdown in mailing list
as many ComDev members participated in the conference; and second, the
holiday season in late December and early January.
Despite moderate activity on the mailing list, we had a good quarter with
significant and impactful activities.
-----------------------------------------
Attachment L: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Apache CouchDB software is a document-oriented database that can be queried and
indexed in a MapReduce fashion using JavaScript. CouchDB also offers
incremental replication with bi-directional conflict detection and resolution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache CouchDB was founded 2008-11-19 (16 years ago)
There are currently 72 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Glynn Bird on 2023-03-14.
- No new committers. Last addition was Jiahui Li on 2023-08-24.
## Project Activity:
- multiple new features for a new feature release are in development
- starting the next release round for both feature and bug fix releases
- monthly developer meetings continue to be useful
## Community Health:
- while the winter break slowed down the mailing lists a bit, GitHub
discussions and chat support are as active as ever.
-----------------------------------------
Attachment M: Report from the Apache Creadur Project [Philipp Ottlinger]
## Description:
The mission of Creadur is the creation and maintenance of software related to
comprehension and auditing of software distributions
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Creadur was founded 2012-04-18 (13 years ago)
There are currently 13 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Claude Warren on 2024-01-23.
- No new committers. Last addition was Jean-Baptiste Onofré on 2024-01-23.
## Project Activity:
Heavy development going on in Creadur RAT to allow more flexibility
and harmonisation among Ant, Maven und CLI runs.
It is so wonderful that we are able to use Github's infrastructure
to discuss on the PR.
Due to the migration of Maven plugins and site-doxia-stack we are
in contact with the committers over there and hope to implement
our 0.17-homepage with the new versions and layout.
## Community Health:
Development of new release still going on.
Due to regressions and a de-facto rewrite of Creadur RAT core
the development takes longer and is still ongoing.
Any requests/bug reports are being handled and discussed properly.
-----------------------------------------
Attachment N: Report from the Apache DataFu Project [Eyal Allweil]
## Description:
The mission of Apache DataFu is the creation and maintenance of software
related to well-tested libraries that help developers solve common data
problems in Hadoop and similar distributed systems
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache DataFu was founded 2018-02-21 (7 years ago) There are currently 20
committers and 12 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ohad Raviv on 2023-02-06.
- Ben Rahamim (he has not yet completed the new committer process). Last
addition was Ohad Raviv on 2019-07-27.
## Project Activity:
There were a few issues we hoped to finish before doing our next release, and
we finished almost all of them in this past quarter - there's one more left.
In this quarter we will finish it and make a release.
## Community Health:
The relatively dormant status of the project has somewhat improved after the
roll calls started in the last quarter - a new committer (invited after
finishing his second contribution), more reviews, more activity. Hopefully
this increase will be sustained and a new release will help maintain or
improve our status.
-----------------------------------------
Attachment O: Report from the Apache DataSketches Project [Lee Rhodes]
## Description:
The mission of Apache DataSketches is the creation and maintenance of software
related to an open source, high-performance library of streaming algorithms
commonly called "sketches" in the data sciences. Sketches are small, stateful
programs that process massive data as a stream and can provide approximate
answers, with mathematical guarantees, to computationally difficult queries
orders-of-magnitude faster than traditional, exact methods
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache DataSketches was founded 2020-12-15 (4 years ago)
There are currently 16 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Charlie Dickens on 2023-07-04.
- No new committers. Last addition was Pierre Lacave on 2024-03-12.
- One new committer in process.
## Project Activity:
It is now official that the GoogleCloudPlatform/bigquery-utils
repository incorporates the DataSketches Library for use by
any users of Google BigQuery SQL services. See this link:
https://github.com/GoogleCloudPlatform/
bigquery-utils/blob/master/udfs/datasketches/README.md
The link on that page points to our
Apache/datasketches/bigquery repo, which contains all of
our sketch adaptors for BQ/SQL.
Our DataSketches-java library is now available supporting Java 17.
We are making progress on supporting Java 21.
## Community Health:
Our project is healthy. We have a small, loyal and growing community
of users that contact us when they have questions or issues. We are experiencing
growing interest from major corporations in our multi-language libraries.
The Google adoption is strong evidence of that.
We continue to get interest from scientists around the world who
offer ideas for new sketches for our library based on recent research.
-----------------------------------------
Attachment P: Report from the Apache DeltaSpike Project [Mark Struberg]
-----------------------------------------
Attachment Q: Report from the Apache Doris Project [Mingyu Chen]
## Description:
The mission of Apache Doris is the creation and maintenance of software related
to a MPP-based interactive SQL data warehousing for reporting and analysis
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Doris was founded 2022-06-15 (3 years ago)
There are currently 81 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- Pan Xiaolei was added to the PMC on 2024-11-12
- Dechao Hu was added as committer on 2024-11-05
- Wen Luo was added as committer on 2024-12-09
- Jian Hu was added as committer on 2024-11-12
- Yuexi Zhou was added as committer on 2024-11-12
- Shilei Fu was added as committer on 2024-11-05
- Vallish Pai was added as committer on 2024-12-12
- Yulei Yang was added as committer on 2025-01-05
## Project Activity:
Software development activity:
- We released the bug fix release 2.1.8 on 2025-01-24 and 3.0.3 on 2024-12-02
- Not much new feature being added to the new version, but we are working on
adding more test cases to make project stable.
Meetups and Conferences:
- Doris Summit Asia 2024 was held in ShenZhen, China on 2024-12-16, with more
than 500 attendees.
## Community Health:
Overall community health is good. And we made a more strick PR merge rule to
let our project more stable. On the other hand, we are inviting more vendors
to join the community and develop main features together.
-----------------------------------------
Attachment R: Report from the Apache Drill Project [Charles Givre]
## Description:
The mission of Drill is the creation and maintenance of software related to
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage
## Project Status:
Current project status: Ongoing
No issues which require Board attention.
## Membership Data:
Apache Drill was founded 2014-11-18 (10 years ago)
There are currently 62 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was James Turton on 2022-01-23.
- No new committers. Last addition was Maksym Rymar on 2022-10-19.
## Project Activity:
We will likely release Drill 1.22 this quarter as we have not had a
major release in some time.
Recent releases:
1.21.1 was released on 2023-04-29.
1.21.0 was released on 2023-02-21.
1.20.3 was released on 2023-01-07.
## Community Health:
We had a fairly quiet quarter as reflected by the metrics below, however
there is traffic on our Slack channel for which we do not have great
metrics. We will likely release Drill 1.22 this quarter.
dev@drill.apache.org had a 50% decrease in traffic in the past quarter
issues@drill.apache.org had a 67% decrease in traffic in the past quarter
16 commits in the past quarter (-30% change)
4 code contributors in the past quarter (-60% change)
10 PRs opened on GitHub, past quarter (-58% change)
10 PRs closed on GitHub, past quarter (-33% change)
8 issues opened on GitHub, past quarter (14% increase)
3 issues closed on GitHub, past quarter (50% increase)
-----------------------------------------
Attachment S: Report from the Apache Druid Project [Gian Merlino]
-----------------------------------------
Attachment T: Report from the Apache Dubbo Project [Jun Liu]
## Description:
Apache Dubbo is an easy-to-use RPC framework that provides different
language implementations, service discovery, traffic management,
observability, security, tools, and best practices for building
enterprise-ready microservices.
## Project Status:
Current project status: With high activity.
Issues for the board: no issue.
## Membership Data:
Apache Dubbo was founded 2019-05-15 (6 years ago)
There are currently 109 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- Sean Yang was added to the PMC on 2025-01-10
- Chen Cai and Taibo He has been voted as committers, invitations sent.
- No new committers. Last addition was Long Qiang on 2024-08-28.
## Project Activity:
Recent releases:
dubbo-python 3.0.0b1 was released on 2025-01-27.
3.3.3 was released on 2025-01-26.
3.3.2 was released on 2024-11-07.
## Community Health:
Overall community health is good, especially with the main repo apache/dubbo,
the Java implementation.
The community is seeing activity decrease in some of the side projects in the
past quarters. Mainly for the deactive of the core developers of some of these
projects, the PMC members should pay more attention to finding and cultivating
new developers to 'lead' the development of these side projects.
-----------------------------------------
Attachment U: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
Empire-db is a lightweight relational database access library dealing with all
aspects of storing, manipulating, retrieving and modelling data in relational
database management systems (RDBMS). As an alternative to traditional
OR-Mapping solutions, it provides an SQL centric, no-compromise approach that
uses a Java-Object-Model rather than Mapping Files or Annotations.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Empire-db was founded 2012-01-24 (13 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jan Glaubitz on 2016-07-10.
- No new committers. Last addition was Ralf Eichinger on 2022-03-15.
## Project Activity:
Latest release is empire-db-3.2.0 released on 2024-06-25.
Since our last release last June we have collected 26 Jira tickets
of which 17 are improvements and 9 are declared as bugfixes.
Most of the tickets have been resolved and recently activity
has slowed down indicating that it would be sensible release the
changes. Therefore, I (the chair) have asked the community for their
feedback and consent about the readiness for a new release.
Given no objections I would then shortly begin initiating a vote
for preparing and publishing the new release.
## Community Health:
Our community although small is still alive and healthy.
Given most of the work is done by 2 committers, we have
conducted a roll call last Summer (see 2024-08 report) that
had 5 committers repsonding that hey were either active or
paying attention.
10 new Jira-Tickets were opened
40 commits in the past quarter
-----------------------------------------
Attachment V: Report from the Apache EventMesh Project [Eason Chen]
## Description:
The mission of Apache EventMesh is the creation and maintenance of software
related to a fully serverless platform used to build distributed event-driven
applications
## Project Status:
Current project status: Ongoing: With moderate activity
Issues for the board: none
## Membership Data:
Apache EventMesh was founded 2023-03-22 (2 years ago)
There are currently 54 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jianbo Liu on 2024-01-05.
- Zikang Chen was added as committer on 2025-01-28
- Karson To was added as committer on 2025-01-28
- Ruimin Fang was added as committer on 2025-01-28
## Project Activity:
Apache EventMesh v1.11.0 release
New Feature EventMesh Dashboard is ready for review
## Community Health:
The new features were under designing or developing,
so the commits and PR activity seems decrease.
The community plans to bring the dashboard feature into the next version.
-----------------------------------------
Attachment W: 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: At risk
Issues for the board: We need assistance from the board on understanding the
next steps for dissolving the Fluo PMC and getting approval to transfer
control of the repositories to the Accumulo PMC.
## 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:
The number of active PMC members has fallen substantially, and very little
development activity is ongoing. The diminished contributor activity itself is
not unusual, because the project is very niche, and slow moving, and depends
on other relatively slow-moving projects (especially Apache Accumulo) for very
infrequent releases. However, the lack of interest to maintain active
involvement from the current PMC members is unusual and puts the project at
risk of not being able to make decisions and perform releases.
A roll was called [1], and an insufficient number of members identified
themselves as interested in remaining active.
Given the nature of the project's relationship to Apache Accumulo, it was
suggested to move the project to a subproject of Accumulo, where it can be
occassionally used as an example for Accumulo, and some of its tooling can
continue to be maintained by Accumulo PMC members for testing Accumulo. This
was raised with the Accumulo PMC[2], and the consensus was in favor of doing
that. The Fluo PMC now requires assistance/advice on the next procedural steps
to make that happen. We suspect that dissolution of the Fluo PMC is warranted,
and help from INFRA is needed to grant the Accumulo PMC the appropriate
permissions. I have inquired with INFRA on what we might need to be able to
do, and my understanding is that we need approval from the board first, then
we can just put in tickets with INFRA.
Since the roll call, I (ctubbsii) have personally spoken to several PMC
members who indicated that they would at least be willing to participate in a
final vote, if that were necessary, to resolve a transfer to the Accumulo PMC
or other final dissolution of the project, if a vote were necessary. However,
I think board intervention may obviate the need for such a vote from the PMC
members. If the board were to approve the dissolution of the Fluo PMC, and
approve the conversion of Fluo to a subproject of Accumulo's PMC, then that
should be sufficient to absolve the PMC members who wish to be inactive from
performing any more responsibilities.
[1]: https://lists.apache.org/thread/16k0j5vzpbtzgpjn2zc0hdgwr860hq6w
[2]: https://lists.apache.org/thread/lhgvkkoqtvmlol7h64n8jytlcyynw268
## Community Health:
The project is currently unhealthy, due to a lack of PMC members interested in
remaining active. See other sections for details.
-----------------------------------------
Attachment X: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was moderate in recent months.
## Health report:
Activity is relatively low, as usual for this project. The 2.3.34 release was
voted on and done. User questions (mostly on StackOverflow) and new Jira
issues are being answered. PR-s slowly but eventually getting reviewed and
merged. Next the goal on the 2.x line is to finishing the java.time support
(FREEMARKER-35) is next priority. The long term goal is continuing the ongoing
development on the 3.0 branch, so that the project can innovate, and the code
base can become much cleaner and more attractive for new committers.
## PMC changes:
- Currently 9 PMC members.
- Added Alon Ziv on 2024-12-23
- Added Christoph Rueger on 2025-01-01
## Committer base changes:
- Currently 12 committers.
- Last added (non-PMC): Siegfried Goeschl on 2020-01-07
## Releases:
- 2.3.34 was released on 2024-12-22
-----------------------------------------
Attachment Y: Report from the Apache Geode Project [Mark Bretl]
## Description:
The mission of Apache Geode is the creation and maintenance of software
related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud
architectures.
## Project Status:
Current project status: Ongoing - Low
Issues for the board: None
## Membership Data:
Apache Geode was founded 2016-11-15 (8 years ago)
There are currently 118 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Calvin Kirs on 2022-11-14.
- No new committers. Last addition was Calvin Kirs on 2022-11-15.
## Project Activity:
Beginning to see some traction from new contributors working through
security
issues.
## Community Health:
In the month of January 2025, there was a kickoff meeting with a new group of
possible contributors and now we are starting to see some discussions on the
private list about open security issues. The conversations are mostly driven
by ASF Security as there is not much knowledge on the current PMC. The hope
is that this can bring in more activity and breath a little bit of life into
the project, however, it is still unknown if it will be sustainable in the
long-term.
-----------------------------------------
Attachment Z: Report from the Apache Gora Project [Kevin Ratnasekera]
## Description:
The mission of Gora is the creation and maintenance of software related to ORM
framework for column stores such as Apache HBase and Apache Cassandra with a
specific focus on Hadoop.
## Project Status:
Current project status:
Issues for the board: Dormant. The Gora PMC last made a release on 2019-08-15.
## Membership Data:
Apache Gora was founded 2012-01-23 (13 years ago)
There are currently 31 committers and 29 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 Lahiru Jayasekara on 2020-04-29.
- No new committers. Last addition was Lahiru Jayasekara on 2020-04-27.
## Project Activity:
Small contributions in the last 6 months but no action taken by committers.
## Community Health:
We will perform a healthcheck to determine project viability as activity is very
low. There are literally no new mailing list threads on dev@.
-----------------------------------------
Attachment AA: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No issues requiring board attention at this time.
## Membership Data:
Apache Groovy was founded 2015-11-18 (9 years ago)
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Soeren Glasius was added to the PMC on 2024-11-06
- Jonny Carter was added as committer on 2024-11-12
- Sergio del Amo was added as committer on 2024-12-20
## Project Activity:
Recent releases:
- 4.0.25: 2025-01-25
- 5.0.0-alpha-12: 2025-01-25
- 3.0.23: 2024-11-08
- 4.0.24: 2024-11-08
- 5.0.0-alpha-11: 2024-11-08
The Groovy PMC voted to accept Geb (previously gebish.org) as a Groovy
subproject last quarter. There is a draft website and snapshots available
currently, but first releases under the ASF are likely next quarter.
The Groovy PMC voted (closed Jan 25) to sponsor incubation of the Grails
project (grails.org) to become a new TLP when ready. We anticipate
further work carrying out that role in the next quarter. We expect to
provide more details of how that is progressing in our next report.
The other major goal over the next quarter is to move
Groovy 5 towards a GA release.
## Community Health:
Overall activity has increased but work on the main Groovy project
is slightly down. Work on helping Geb become a subproject is well
advanced. Work helping Grails to enter incubation is expected to
ramp up over the next little while. We expect work on the main Groovy
project will go back to normal once other onboarding activities have
settled down. The current activity within the Grails community seems
very healthy. This should be a great positive for the ASF and we expect
the (related) Groovy community to also benefit. There has always been
some overlap between the Grails and Groovy communities.
-----------------------------------------
Attachment AB: Report from the Apache Hop Project [Hans Van Akelyen]
-----------------------------------------
Attachment AC: Report from the Apache HTTP Server Project [Joe Orton]
## Description:
The mission of HTTP Server is the creation and maintenance of software related
to Apache Web Server (httpd)
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: None
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (30 years ago)
There are currently 127 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Giovanni Bechis on 2021-06-11.
- No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05.
## Project Activity:
The project released httpd 2.4.63 in January this year, following up on the
2.4.62 release in July 2024. The focus for this release was almost purely bug
fixes, with some small feature additions too. The patches addressing a complex
set of security issues in 2.4.62 had broken some user configurations,
particularly involving mod_rewrite, hopefully these are now all addressed in
the new release.
Other than the activity around the release, there was renewed discussion about
switching from Subversion to git, following the project vote on this which
was now nearly two years ago(!)
## Community Health:
As usual for a quarter featuring a release, both commits and mailing list
activity were up significantly from last quarter. Incoming bugs and user
discussion was a bit quieter - unsurprising as mentioned in my previous report
that these had spiked after the issues around the previous 2.4.6x releases.
Healthy turnover of GitHub pull requests continues, though we are developing a
significant triage/review backlog here.
-----------------------------------------
Attachment AD: Report from the Apache HttpComponents Project [Michael Osipov]
## Description:
The mission of HttpComponents is the creation and maintenance of software
related to Java toolset of low level HTTP components
## Project Status
- There are no issues requiring board attention at this time.
## Membership Data:
Apache HttpComponents was founded 2007-11-14 (17 years ago)
There are currently 20 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Arturo Bernal on 2023-10-27.
- No new committers. Last addition was Arturo Bernal on 2023-06-20.
## Project Activity:
- Development on master is 5.5 for Client and 5.4 for Core
## Community Health:
- Overall the project remains active. Issues and dicussions are
resolved in time.
## Releases:
- HttpClient 5.4.2 GA: 2025-02-03
- HttpCore 5.3.3 GA: 2025-01-29
- HttpCore 5.3.2 GA: 2025-01-13
-----------------------------------------
Attachment AE: Report from the Apache Ignite Project [Dmitry Pavlov]
## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Ignite was founded 2015-08-19 (9 years ago)
There are currently 78 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Amelchev on 2023-11-20.
- No new committers. Last addition was Roman Puchkovskiy on 2024-04-24.
## Project Activity:
- 3.0.0 was released on 2025-02-10 – A major rework of Apache Ignite:
-- Based on Raft-based consensus protocol
-- Apache Calcite SQL support
-- Improved transaction protocol
-- Dynamic cluster configuration
- 2.17.0 was released on 2025-02-13:
-- Transaction-Aware Queries: SQL and Scan queries (READ_COMMITTED level,
Calcite engine)
-- Completed Java 11 migration from Java 8
-- Control utility now defaults to the thin client protocol
-- Apache Calcite SQL Enhancements
## Community Health:
- Mailing list and code activity have grown noticeably. Issues@ and the user@
lists have grown by 30-40%, while commits have increased by 40%.
- dev@ list traffic nearly tripled (+280%), driven by two parallel releases
and a previously low activity base.
- Apache Ignite summit 2025 is scheduled for February 25,
https://ignite-summit.org/2025
-----------------------------------------
Attachment AF: Report from the Apache Impala Project [Zoltán Borók-Nagy]
## Description:
The mission of Apache Impala is the creation and maintenance of software
related to a high-performance distributed SQL engine
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: none
## Membership Data:
Apache Impala was founded 2017-11-15 (7 years ago)
There are currently 72 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Riza Suminto on 2024-03-06.
- No new committers. Last addition was Stephen Carlin on 2024-11-01.
## Project Activity:
- New release is in progress: Impala 4.5.0
- Added user quotas to Admission Control
- Calcite planner integration
- MERGE statement
- Improvement for Iceberg integration: puffin stats, memory usage optimizations
- Query timelines
- OAuth support
- Various perf improvements
## Community Health:
reviews@ is the most reliable metric of Impala community activity level.
There were 3320 emails to that list in December, January,
and February (until 10th)
-----------------------------------------
Attachment AG: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for February 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 33 podlings incubating. In January, podlings executed
three distinct releases, and no IP clearance occurred. Several incubating
proposals have been discussed on the mailing list, and we have one new
podling who will join the incubator called Iggy. YuniKorn graduated last
month
and no podlings have retired. DevLake and Wayang are close to graduation.
Several podlings failed to report and will be asked to report next month.
The incubator hasn't reported for several months. While there have been no
urgent issues for the board, and thing have been progresing as normal, this
is not an ideal state of affairs. The incubator, unlike other projects,
needs to report every month, and it takes a lot of work to put the report
together. This month, several IPMC members helped out with the
reporting.Hopefulkly this will continue to ensure that reports are
submitted every month, and people involved and the wider IPMC will be
encouraged to help out.
Conversations on the list have been mostly about releases. A few other
topics have been discussed recently, which will be included in next month's
report.
The project maturity model has been updated to include a section on
trademark and branding, as there have been a number of recent podlings that
have had issues with this.
There is ongoing discussion on several new potential incubating projects.
## Community
### New IPMC members:
- Anshum Gupta (anshum)
- Yonik Seeley (yonik)
- Lari Hotari (lhotari)
### People who left the IPMC:
- Guillaume Nodet (gnodet)
## New Podlings
- Iggy
- Hunter (Nov 2024)
## Podlings that failed to report, expected next month
- Gravitino
- Nemo
- Pony Mail
- Teaclave
- Toree
- Training
## Graduations
- StreamPark
- Answer (Dec 2024)
The board has motions for the following:
- Uniffle
## Releases
The following releases have entered distribution since the last report:
Jan 2025:
- Gravitino 0.8.0
- Gluten 1.3.0
- Uniffle 0.9.2
Dec 2024:
- BareMaps 0.8.1
- HugeGraph 1.5.0
- HoraeDB python client 2.0.0
- Gluten 1.2.1
- KIE 10.0.0
- StormCrawler 3.2.0
- Uniffle 0.9.1
Nov 2024:
- Answer 1.4.1
- Amoro 0.7.1
- HoraeDB 2.1.0
- Fury 0.9.0
- XTable 0.2.0
Oct 2024:
- Hertzbeat 0.6.1
- Gravitino 0.6.1
- StreamPark 2.1.5
- Fury 0.8.0
## IP Clearance
- Apache Groovy receiving Geb
## Legal / Trademarks
Updated project maturity model.
## Infrastructure
N/A
## Table of Contents
[Baremaps](#baremaps)
[Cloudberry](#cloudberry)
[DevLake](#devlake)
[Fury](#fury)
[GraphAr](#graphar)
[HertzBeat](#hertzbeat)
[HoraeDB](#horaedb)
[Hunter](#hunter)
[KIE](#kie)
[NLPCraft](#nlpcraft)
[OpenServerless](#openserverless)
[OzHera](#ozhera)
[Polaris](#polaris)
[ResilientDB](#resilientdb)
[Seata](#seata)
[StormCrawler](#stormcrawler)
[Uniffle](#uniffle)
[Wayang](#wayang)
[XTable](#xtable)
--------------------
## Baremaps
Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.
Baremaps has been incubating since 2022-10-10.
### Three most important unfinished issues to address before graduating:
1. Reviewing compliance with Apache standards.
2. Expanding the community.
3. Making releases.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Several animated discussions allowed us to address licensing issues.
The fact that practices vary widely across top-level projects does not
make
the process easier.
### How has the community developed since the last report?
Since the last release in December 2024, there has been an uptick in
contributions.
We still struggle with the pace of releases, but the overall involvement
seems to be increasing.
### How has the project developed since the last report?
The last release effectively summarizes the project's development since
the
previous report.
https://github.com/apache/incubator-baremaps/releases/tag/v0.8.1
More recently, we welcomed three new contributors.
Yongjun Hong contributed issue templates and github actions to facilitate
the onboarding of new commers.
Alex Gacon fixed performance issues affecting the latest release.
Rohit Yaduvanshi improved the maven artifacts.
### 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:
0.8.1 in December 2024
### When were the last committers or PPMC members elected?
Sébastien Riollet in June 2024
### Have your mentors been helpful and responsive?
Julian Hyde and Calvin Kirs provided valuable feedback.
More generally, we struggle to get sufficient votes from PPMC members on
our dev mailing list, which slows down the release process.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (baremaps) Bertrand Delacretaz
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
- [ ] (baremaps) Julian Hyde
Comments:
- [X] (baremaps) Calvin Kirs
Comments:
- [ ] (baremaps) George Percivall
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
### IPMC/Shepherd notes:
Justin Mclean:
I would take care in copying what TLP do, as you may not understand why they
did things in a certain way, you are better off following teh current
Incubator guidances.
--------------------
## Cloudberry
Cloudberry is one advanced and mature open-source Massively Parallel
Processing (MPP) database, which evolves from the open-source version of
the Pivotal Greenplum Database®️ but features a newer PostgreSQL kernel and
more advanced enterprise capabilities. It can serve as a data warehouse and
can also be used for large-scale analytics and AI/ML workloads.
Cloudberry has been incubating since 2024-10-11.
### Three most important unfinished issues to address before graduating:
1. Finish the source code cleanup.
* Rename the old brand:
https://github.com/apache/cloudberry/pull/731.
* Update the NOTICE and LICENSE files
https://github.com/apache/cloudberry/pull/812.
* Check the Apache License headers.
2. Publish the first Apache release.
3. Grow the community and attract more contributors and 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. We shared project updates across social channels and encouraged
community members to submit sessions for upcoming conferences.
2. Our Slack community has grown to 128 members.
3. Key topics are actively discussed on the mailing list (92
messages in Nov 2024, 110 messages in Dec 2024, and 49 messages in Jan
2025).
4. 6 new contributors to the main repo since joining the Apache
Incubator.
### How has the project developed since the last report?
- We established a basic CI/CD workflow using GitHub Actions to support
daily development activities.
- We initiated and finalized the Cloudberry roadmap discussion.
Currently, we’re focusing on high-priority tasks, including cherry-picking
commits from the open-source Greenplum project into Cloudberry.
- Additionally, we’ve been enriching documentation and enhancing the site
user experience.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
No new committers or PPMC members have been elected yet.
### Have your mentors been helpful and responsive?
Yes, a lot of help on the project bootstrap and community growth.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues. The VP, Brand has approved
the project name. (PODLINGNAMESEARCH-227)
### Signed-off-by:
- [ ] (cloudberry) Roman Shaposhnik
Comments:
- [X] (cloudberry) Willem Ning Jiang
Comments: Good to see the project moving to ASF smoothly
- [X] (cloudberry) Kent Yao
Comments: Glad to see community growth
### IPMC/Shepherd notes:
--------------------
## DevLake
DevLake is a development data platform, providing the data infrastructure
for developer teams to analyze and improve their engineering productivity.
DevLake has been incubating since 2022-04-29.
### Three most important unfinished issues to address before graduating:
1. Grow the community and attract more users.
2. Add more committers and PPMC members.
3. Grow the project, support more data sources and use cases, and improve
the user experience.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We would like to seek guidance regarding the graduation of DevLake. Please
let us know what we should do step by step. Thank you.
### How has the community developed since the last report?
1. 25 new contributors have joined the community (181 contributors in
total)
2. 156 new community members in Slack (1458 in total)
3. 2 new committers were elected, and 1 PPMC was elected.
### How has the project developed since the last report?
1. Made a major release v1.0.1 with no compliance issues.
2. Fix the data sync error in the incremental mode.
3. Optimize the scope config configurations.
4. Optimize the DORA related metrics and dashboards.
5. Tons of UX refinement.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2024-9-23
### When were the last committers or PPMC members elected?
2024-12-7
### Have your mentors been helpful and responsive?
Yes, the mentors helped tremendously throughout version releases and
community governance.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (devlake) Felix Cheung
Comments:
- [ ] (devlake) Liang Zhang
Comments:
- [ ] (devlake) Lidong Dai
Comments:
- [ ] (devlake) Sijie Guo
Comments:
- [X] (devlake) Jean-Baptiste Onofré
Comments: I think DevLake is close to graduation. Maybe we should
make a pass on Maturity Model
(https://community.apache.org/apache-way/apache-project-maturity-model.html)
to evaluate the current state.
- [X] (devlake) Willem Ning Jiang
Comments: Let's go through the graduation evaluation process.
### IPMC/Shepherd notes:
--------------------
## Fury
A blazing fast multi-language serialization framework powered by jit and
zero-copy
Fury has been incubating since 2023-12-15.
### Three most important unfinished issues to address before graduating:
1. Grow the community(attracting more committers, contributors, and
users).
2. Improve project documentation and align the implementation of
Java/Python/JavaScript/Golang/Rust.
3. Add more PPMC members and release managers.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
Steady progress
### How has the project developed since the last report?
2 releases. The most recent was v0.9.0 on Nov 10, 2024.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-11-10
### When were the last committers or PPMC members elected?
2024-11-30, added new committer pandalee99
### Have your mentors been helpful and responsive?
Yes, the mentors helped a lot for version releases and community
governance.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (fury) tison
Comments:
- [X] (fury) PJ Fanning
Comments: Steady Progress
- [ ] (fury) Yu Li
Comments:
- [X] (fury) Xin Wang
Comments: Steady progress
- [ ] (fury) Enrico Olivelli
Comments:
- [ ] (fury) Hao Ding
Comments:
### IPMC/Shepherd notes:
--------------------
## GraphAr
GraphAr is an open-source and language-independent data file format designed
for efficient graph data storage and retrieval.
GraphAr has been incubating since 2024-03-25.
### Three most important unfinished issues to address before graduating:
1.Growing the community(attracting more committers, contributors and
users).
2.Release more ASF-compliant versions.
3.Improve the robustness of GraphAr's submodules.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. Voted and accepted 1 new committer.
2. Attracted 1 contributor from the OSPP 2024 and we plan to
make him as our new committer.
### How has the project developed since the last report?
1. Merged 50 PRs since the last report.
2. Initialized the CLI submodule of GraphAr library.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-07-02
### When were the last committers or PPMC members elected?
2024-08-15
### Have your mentors been helpful and responsive?
Yes, the mentors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approved the project name.
(PODLINGNAMESEARCH-221)
### Signed-off-by:
- [X] (graphar) Calvin Kirs
Comments:
- [ ] (graphar) tison
Comments:
- [ ] (graphar) Xiaoqiao He
Comments:
- [ ] (graphar) Yu Li
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.
2. Publish more Apache release by different committers.
### 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. 26 contributors submit 251 commits.
2. Now the community total has 251 contributors.
3. Students participate in OSPP activities all have done a good job.
### How has the project developed since the last report?
1. New version v1.6.1 has released.
2. The version 1.7.0 is under active development
3. Integration with Apache Arrow.
4. New alarm module has been developed.
5. More features and bugfix, doc update
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-11-22
### When were the last committers or PPMC members elected?
2024-09-09
### 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:
- [ ] (hertzbeat) Justn Mclean
Comments:
- [X] (hertzbeat) Francis Chuang
Comments:
### IPMC/Shepherd notes:
--------------------
## HoraeDB
HoraeDB is a high-performance, distributed, cloud native time-series
database.
HoraeDB has been incubating since 2023-12-11.
### Three most important unfinished issues to address before graduating:
1. Release more version
2. Grow community(attract more users/committers)
3. Finish the new metrics engine
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
One committer added.
### How has the project developed since the last report?
We are starting our new metric engine. It's currently a bit slow, and
we'll
dedicate more time to its development after the Chinese New Year holidays.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-12-10
### When were the last committers or PPMC members elected?
- Neo Chen, at 2024-12-25
### Have your mentors been helpful and responsive?
Yes, they are helpful when release version and other trivial things.
### Is the PPMC managing the podling's brand / trademarks?
Yes, we're doing well with this.
### Signed-off-by:
- [ ] (horaedb) tison
Comments:
- [X] (horaedb) Shaofeng Shi
Comments: Hope to see more use cases or tech blogs from Horeadb
community, so that users know how mature it is.
- [X] (horaedb) Gang Li
Comments:
- [ ] (horaedb) Von Gosling
Comments:
### IPMC/Shepherd notes:
--------------------
## Hunter
Hunter performs statistical analysis of performance test results
and finds change-points and notifies about possible performance
regressions. A typical use-case of hunter is as follows:
* A set of performance tests is scheduled repeatedly.
* The resulting metrics of the test runs are stored in a time
series database (e.g, Graphite) or appended to CSV files.
* Hunter is launched by a Jenkins/Cron job (or an operator) to
analyze the recorded metrics regularly.
* Hunter notifies about significant changes in recorded metrics
by outputting text reports or sending Slack notifications.
Hunter has been incubating since 2024-11-27.
### Three most important unfinished issues to address before graduating:
1. Finish project setup:
a. Rename - PODLINGNAMESEARCH-230.
b. Add Apache License headers https://github.com/apache/hunter/issues/31.
2. Create a project website.
3. Publish the first release under the new name.
### Are there any issues that the IPMC or ASF Board need to be aware of?
The original project name has been rejected in
[PODLINGNAMESEARCH-228](https://issues.apache.org/jira/browse/PODLINGNAMESEA
RCH-228)
and the proposal for the new name
[PODLINGNAMESEARCH-230](https://issues.apache.org/jira/browse/PODLINGNAMESEA
RCH-230)
has been blocked on review for a couple of weeks.
### How has the community developed since the last report?
We have the first engagements in GH issues. We do not have any new
contributors,
but also we haven’t been promoting the project because we do not have the
new approved name to promote.
### How has the project developed since the last report?
Since the incubation started, there have been several notable
developments:
1. The project has migrated from datastax-labs/hunter to apache/hunter
repository ([HUNTER-1](https://issues.apache.org/jira/browse/HUNTER-1)).
2. Nyrkiö upstreamed all changes from their private fork -
https://github.com/apache/hunter/pull/27.
3. A complete overhaul of documentation has been done to lower the entry
barrier - https://github.com/apache/hunter/pull/28.
### How would you assess the podling's maturity?
We are finishing the initial setup.
### Signed-off-by:
- [X] (hunter) Dave Fisher
Comments:
- [ ] (hunter) Enrico Olivelli
Comments:
- [ ] (hunter) Lari Hotari
Comments:
- [ ] (hunter) Michael Semb Wever
Comments:
### IPMC/Shepherd notes:
Justin MClean:
VP, Brand Management has approved the new name.
--------------------
## KIE
KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.
KIE has been incubating since 2023-01-13.
### Three most important unfinished issues to address before graduating:
1. Licensing issues (some MPL, Hibernate, EPL)
2. Migrating some builds to Apache Infra
3. Continued releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
I don't believe so, things have been discussed on lists or JIRA.
### How has the community developed since the last report?
We just voted two new community members in earlier this week, however,
they
haven't accepted yet. There was also one other member voted in August.
### How has the project developed since the last report?
We're making progress. It is a little painful right now, but we're making
progress. We're trying to simplify our builds, better understand how to
communicate as a whole and move forward. Slower progress than I'd like to
see, but progress nonetheless.
### 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 - I don't think we're close just yet, maybe
toward the end of the year?
- [ ] Other:
### Date of last release:
2024-12-12
### When were the last committers or PPMC members elected?
Two this past week.
### Have your mentors been helpful and responsive?
Doing okay now, I believe. We do need to get the info out to the new
committers though, but it has only been a couple of days.
### Is the PPMC managing the podling's brand / trademarks?
Yes, we're doing well with this.
### Signed-off-by:
- [X] (kie) Brian Proffitt
Comments:
- [ ] (kie) Claus Ibsen
Comments:
- [ ] (kie) Andrea Cosentino
Comments:
### IPMC/Shepherd notes:
--------------------
## NLPCraft
A Scala library for NLU applications
NLPCraft has been incubating since 2020-02-13.
### Three most important unfinished issues to address before graduating:
1. Community growth.
2. Extending the technology stack
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
- We engaged with Python community developers interested in contributing.
- We began investigating LLM integration to enhance current functionality
(especially sLLMs).
- We initiated discussions with potential customers and users, including
LoomHR.ai and Humatron.ai, whose developers may join the community.
### How has the project developed since the last report?
- Examples extended.
- Technical PRs processed.
- Research and investigation tasks related to sLLMs
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2023-02-30
### When were the last committers or PPMC members elected?
August of 2021.
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (nlpcraft) Roman Shaposhnik
Comments:
- [ ] (nlpcraft) Furkan Kamaci
Comments:
- [ ] (nlpcraft) Evans Ye
Comments:
- [ ] (nlpcraft) Paul King
Comments:
- [ ] (nlpcraft) Konstantin I Boudnik
Comments:
### IPMC/Shepherd notes:
--------------------
## OpenServerless
OpenServerless is an open source, cloud-agnostic, serverless platform. It
offers a complete environment for serverless applications development, based
on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an
unified developer experience with a plethora of services (SQL or noSQL
databases, key-value stores, object storage, LLMs services, function
schedulers) managed by the platform's core: the operator, along with tooling
(the CLI) to simplify (and interact with) deployments, integrated ide and
starter application and optimized runtimes integrated with the staters.
OpenServerless has been incubating since 2024-06-17.
### Three most important unfinished issues to address before graduating:
1. Community Building
2. Review the status of all subprojects and align documentation
3. Assess the requirements for the First Release
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. We tried, through posts on various social networks, to give visibility
to the project
2. We organized and publicized a training course focused on the use of
Apache OpenServerless and IA.
3. Started a Discord channel to support people learning OpenServerless
with the AI course
### How has the project developed since the last report?
1. The porting from the community version of Nuvolaris has been completed
2. We have therefore focused on making the system stable, making the CLI
more robust and the openserverless-tasks sub-project that collects the
automation and integration scripts more organic
3. We have brought the test suite to verify the functioning of the
Kubernetes operator on all supported versions (k3s, k8s, docker, aks, eks,
gks, openshift)
4. We have published the site with the official documentation and made
various updates to it
### How would you assess the podling's maturity?
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None Yet
### When were the last committers or PPMC members elected?
2024-08-22
### Have your mentors been helpful and responsive?
Yes, and we renew our thanks to all of them for their continued support in
developing this project, allowing us to meet the required standards.
### Is the PPMC managing the podling's brand / trademarks?
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved
### Signed-off-by:
- [ ] (openserverless) Bertrand Delacretaz
Comments:
- [ ] (openserverless) Enrico Olivelli
Comments:
- [ ] (openserverless) François Papon
Comments:
- [X] (openserverless) JB Onofré
Comments: Nice progress !
- [X] (openserverless) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## OzHera
OzHera is an application observation platform (APM) in the era of cloud
native, with the application as its core, integrating capabilities such as
metric monitoring, trace tracking, logging, and alerting
OzHera has been incubating since 2024-07-11.
### Three most important unfinished issues to address before graduating:
1.Set up necessary resources in ASF.
2.Make the first apache release.
3.Build a diverse 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?
Updated the website layout and added necessary ASF website page elements.
Added a new committer.
Added a new contributor.
Merged 30 PRs.
### How has the project developed since the last report?
We have completed the overall cleanup of the code and started the first
release.
Complete the basic construction of the intelligent agent module.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
There is no apache release yet.
### When were the last committers or PPMC members elected?
2025-01-13
### Have your mentors been helpful and responsive?
Yes, mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Not yet.
### Signed-off-by:
- [ ] (ozhera) Yu Xiao
Comments:
- [ ] (ozhera) Yu Li
Comments:
- [ ] (ozhera) Kevin Ratnasekera
Comments:
- [ ] (ozhera) Duo Zhang
Comments:
### IPMC/Shepherd notes:
--------------------
## Polaris
Polaris is a catalog for data lakes. It provides new levels of choice,
flexibility and control over data, with full enterprise security and Apache
Iceberg interoperability across a multitude of engines and infrastructure.
Polaris has been incubating since 2024-08-09.
### Three most important unfinished issues to address before graduating:
1. Finalize the first 0.9.0 release
2. Grow the community, especially in terms of contributors
3. Following 0.9.0 release, we are heading to 1.0.0 that will be a larger
release, including binary distributions.
### 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?
- All discussions (design proposals, process improvements) are discussed
on
the mailing list (94 messages on the dev mailing in Dec 24, 196 in Jan 25
for instance)
- New users showed on Slack:
- New contributors interested to work on key features for Polaris (2
expressed interest for storage backend and TMS)
- Two new committers have been elected during the last quarter (Dmitri
Bourlatchkov, Dennis Huo)
### How has the project developed since the last report?
We are working on a lot of important changes for the project, allowing
Polaris to support more use case (especially storage backends).
We also have discussions about new features: Table Maintenance Policy,
Federated Catalogs, ... (on the mailing list with the GitHub Issues for
tracking).
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
New committers have been elected on Jan 13, 2025.
### Have your mentors been helpful and responsive?
Yes, a lot of help for LICENSE/NOTICE fixes.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (polaris) Bertrand Delacretaz
Comments:
- [ ] (polaris) Holden Karau
Comments:
- [ ] (polaris) Kent Yao
Comments:
- [X] (polaris) Ryan Blue
Comments: Fixed some formatting in the report. For community
development, are there more specific data points (other than "more")?
How
many contributions are coming from contributors outside of the
original set
of contributors and companies? In these reports, try to focus more on
community growth and development than project development.
- [X] (polaris) JB Onofre
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.Release more applications.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
Regular meeting continues every week.
### How has the project developed since the last report?
We are preparing a bunch of new applications and will release them in a
few
weeks.
1. New Projects:
Coinsensus - A decentralized financial application integrating ResilientDB
for real-time transactions, fraud detection, and group budgeting.
GitHub: https://github.com/ResilientApp/Coinsensus-Backend
ResCanvas - A decentralized collaborative drawing platform leveraging
ResilientDB for real-time multi-user drawings.
GitHub: https://github.com/ResilientApp/ResCanvas
ResAuc - A blockchain-based online auction platform ensuring transparent
and tamper-proof bidding.
GitHub: https://github.com/ResilientApp/DDS-Backend-main
ResVote - A scalable and secure online voting system built on ResilientDB
to ensure election integrity.
GitHub: https://github.com/ResilientApp/ResVote
MemLens - A continuous profiling tool for ResilientDB, providing real-time
performance monitoring and debugging insights.
GitHub: https://github.com/ResilientEcosystem/MemLens
ResCash - A secure and user-friendly financial accounting solution
integrating ResilientDB for transaction transparency.
GitHub: https://github.com/ResilientApp/ResCash
2. NPM Module Updates:
create-resilient-app - A CLI tool for scaffolding React/Vue projects with
ResVault SDK integration, supporting both JS and TS.
Features: Automatic setup, interactive prompts, and streamlined project
initialization.
NPM: https://www.npmjs.com/package/create-resilient-app
resvault-sdk - A lightweight SDK to integrate ResVault into web
applications for secure transactions and communication.
Features: Simplified API, event listening, and transaction handling via
postMessage.
NPM: https://www.npmjs.com/package/resvault-sdk
resilient-node-cache - A TypeScript library for syncing ResilientDB data
with MongoDB via WebSocket and HTTP, ensuring seamless reconnection.
Features: Automatic reconnection, real-time sync, and high-performance
batching.
NPM: https://www.npmjs.com/package/resilient-node-cache
3. PyPI Module Updates:
resilient-python-cache - A Python library for real-time synchronization
between ResilientDB and MongoDB via WebSocket and HTTP.
Features: Auto-reconnection, configurable sync intervals, and efficient
data fetching.
PyPI: https://pypi.org/project/resilient-python-cache/
4. ResVault Enhancements:
ResVault Smart Contract Key Management—This feature now supports smart
contract key management, enabling the generation of an owner’s key from
public/private key pairs and registering the owner’s address with ResDB
smart contract services. It also facilitates smart contract deployment for
enhanced decentralized application interactions.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
Apache ResilientDB v1.10.0-incubation (2024-7-11)
### When were the last committers or PPMC members elected?
November of 2023
### Have your mentors been helpful and responsive?
The mentors helped tremendously throughout the project build-up and
transfer.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported here.
### Signed-off-by:
- [ ] (resilientdb) Junping Du
Comments:
- [ ] (resilientdb) Calvin Kirs
Comments:
- [ ] (resilientdb) Kevin Ratnasekera
Comments:
- [ ] (resilientdb) Roman Shaposhnik
Comments:
- [ ] (resilientdb) Christian Grobmeier
Comments:
### IPMC/Shepherd notes:
Dave Fisher:
Why are new sub-projects all in a third party org (ResilientApp) with
releases coming in weeks?
Substantial work remains to move to the Incubator and this includes
careful work on branding.
Justin Mclean:
Thanks, Dave, for noticing this. I've brought it up with the project. I
also not that code
in those repos do not follow ASF policy i.e. no code headers or NOTICE
files.
--------------------
## Seata
Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to-
use and high-performance distributed transaction solution, used to solve the
data consistency problem.
Seata has been incubating since 2023-10-29.
### Three most important unfinished issues to address before graduating:
1. More international contributors are joining the community.
2. Handle security vulnerabilities more efficiently and set up a security
page for the project.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at the moment.
### How has the community developed since the last report?
1. 40 new code contributors have joined the community (550 contributors in
total)
2. 8 new committers were elected, and 2 PPMC members were elected.
3. On the Seata GitHub page, there are around 3,500 "used by" listings,
which means over 500 more projects are now depending on Seata since the
last report.
### How has the project developed since the last report?
1. Since the last report, we've merged 268 PRs, which include over 21 new
features, plus a bunch of optimizations and bug fixes.
2. Since the last report, versions 2.1.0 and 2.2.0 have been released.
We're currently voting on 2.3.0. Additionally, the Golang SDK project has
completed its first major milestone for entering the ASF and is preparing
for release.
3. Since the last report, we have received several vulnerability reports,
and we have fixed four of them. We disclosed one CVE, and the other three
vulnerabilities (two CVEs) will be closed with the release of version
2.3.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:
2024-10-12
### When were the last committers or PPMC members elected?
2025-01-02
### Have your mentors been helpful and responsive?
Our mentors have been very helpful and responsive. During this period, we
added a new mentor, Xin Wang.
### Is the PPMC managing the podling's brand / trademarks?
A company attempted to register some domains related to Seata, and we
responded with a rejection.
### Signed-off-by:
- [X] (seata) Sheng Wu
Comments:
- [X] (seata) Justin Mclean
Comments:
- [X] (seata) Huxing Zhang
Comments:
- [X] (seata) Heng Du
Comments:
- [X] (seata) Xin Wang
Comments: Steady progress
### IPMC/Shepherd notes:
--------------------
## StormCrawler
StormCrawler is a collection of resources for building low-latency,
customisable and scalable web crawlers on Apache Storm.
StormCrawler has been incubating since 2024-03-19.
### Three most important unfinished issues to address before graduating:
1. Community building
2.
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?
StormCrawler remains a rather mature and stable project, continuing to
serve its niche effectively. While there isn’t much new to report in terms
of major developments, we did have a contributor show up recently and
provide some pull requests, which is always a positive sign.
It’s worth noting that, even in the age of AI, the number of people
conducting their own large-scale web crawls remains relatively low. Many
opt to leverage datasets like Common Crawl rather than setting up and
maintaining their own crawling infrastructure. This makes community
contributions even more valuable, as StormCrawler continues to be a
reliable solution for those who do require custom crawling capabilities.
### How has the project developed since the last report?
A new release of StormCrawler was made.
However, one area of concern is the level of engagement among the initial
committers. Out of the five original committers, only three have been
actively contributing, while the remaining two have shown little to no
involvement since the project's incubation. While it's not uncommon to see
fluctuations in contributor activity due to shifting priorities and time
constraints, this does highlight the need to expand the committer base.
Therefore, we are happy that we could add an additional committer and PPMC
member since incubation.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2024-12-03
### When were the last committers or PPMC members elected?
2024-09-21
### Have your mentors been helpful and responsive?
Nothing of note.
### Is the PPMC managing the podling's brand / trademarks?
The name was approved by VP, Brand after consulting the Apache Storm
project.
### Signed-off-by:
- [X] (stormcrawler) Dave Fisher
Comments: The podling knows that community growth is required.
- [ ] (stormcrawler) Lewis John McGibbney
Comments:
- [X] (stormcrawler) Ayush Saxena
Comments:
- [X] (stormcrawler) PJ Fanning
Comments:
### IPMC/Shepherd notes:
--------------------
## Uniffle
Uniffle is an unified Remote Shuffle Service
Uniffle has been incubating since 2022-06-06.
### Three most important unfinished issues to address before graduating:
The vote of graduation passed in the mail list of incubatr.
### 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?
374 pull requests are merged. 201 issues are closed.
### How has the project developed since the last report?
374 pull requests are merged. 201 issues are closed.
### 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-01-09.
### When were the last committers or PPMC members elected?
Baolong Mao, elected at 2024-10-28.
### Have your mentors been helpful and responsive?
Yes. They are helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes, the project name is approved.
### Signed-off-by:
- [ ] (uniffle) Felix Cheung
Comments:
- [ ] (uniffle) Junping Du
Comments:
- [X] (uniffle) Liu Xun
Comments:
- [ ] (uniffle) Weiwei Yang
Comments:
- [ ] (uniffle) Zhankun Tang
Comments:
### IPMC/Shepherd notes:
--------------------
## Wayang
Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.
Wayang has been incubating since 2020-12-16.
### Three most important unfinished issues to address before graduating:
1. Growing the community / attracting more committers and developers
2. Automate release process
3. Build FedML further
### 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?
Stagnate
### How has the project developed since the last report?
Slow progress
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2023-09-20
### When were the last committers or PPMC members elected?
2024-09-16
### Have your mentors been helpful and responsive?
All good.
### Is the PPMC managing the podling's brand / trademarks?
Yes, approved.
### Signed-off-by:
- [ ] (wayang) Christofer Dutz
Comments:
- [ ] (wayang) Lars George
Comments:
- [ ] (wayang) Bernd Fondermann
Comments:
- [X] (wayang) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
[PJF] Have been discussing graduation. Some issues with invalid content in
releases but these are being addressed.
--------------------
## XTable
XTable is an omni-directional converter for table formats that facilitates
interoperability across data processing systems and query engines.
has been incubating since 2024-02-11.
### Three most important unfinished issues to address before graduating:
1. Strengthening community building by actively engaging with users.
2. Increasing adoption by implementing key features requested in GitHub
issues and discussions.
3. Establishing a consistent ASF release cadence, targeting a well
planned release every 2 months to align with ASF best practices and ensure
stability
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
1. Launched a bi-weekly 45min developer sync to discuss features, ideas
and
issues with growing attendance in each session.
2. Created a slack channel to reduce friction in collaboration.
3. Welcomed four first time contributors last month and two new people
planning to contribute this month.
### How has the project developed since the last report?
1. ASF release process streamlined and 0.2.0 release published in November
2024.
2. Created an RFC process for working on new features in collaboration
with
the community, with one of them close to completion, one in progress and
one of them in early stage.
3. GH issues are being actively triaged and closed, 34 PR's merged since
Nov 2024.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
Nov 8, 2024
### When were the last committers or PPMC members elected?
Feb 2024
### Have your mentors been helpful and responsive?
Yes, our mentors have been really helpful on the release process.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [X] (xtable) Jesús Camacho Rodríguez
Comments:
- [X] (xtable) Stamatis Zampetakis
Comments:
- [X] (xtable) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
--------------------
-----------------------------------------
Attachment AH: 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: The PMC struggled to achieve quorum on votes
(releases and nominations) due ti inactivity of part of the PMC.
The situation was unlocked by direct solicitation of PMC members, and
with new nominations achieving quorum will no longer be an issue.
## 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:
- Jean Helou was added to the PMC on 2025-01-30
- René Cordier was added to the PMC on 2025-02-03
- Quan Tran was added as committer on 2025-02-05
## Project Activity:
Recent releases:
JAMES-3.7.6 was released on 2025-02-05. JAMES-3.8.2 was released on
2025-02-05. MIME4J-0.8.12 was released on 2025-01-09.
James releases focuses on fixing CVEs.
Work on master branch mostly focuses on bug-fixes and enhancements of the
existing feature set.
The PostgreSQL branch which simplifies the set up of James without
compromising performance is awaiting merge. Following its merge I expect
further work to make the project more accessible to happen:
- Better documentation
- Improve the default configuration
- Modernize the configuration structure
Very good quality contributions on the JSPF library from new contributors.
## Community Health:
The noticeable trend is a sharp increase in user activity on mailing lists:
server-user@james.apache.org had a 180% increase in traffic in the past
quarter (84 emails compared to 30)
Filtering outliers the development is rather stable:
- 17 code contributors in the past quarter (no change)
- 140 PRs opened on GitHub, past quarter (9% increase)
-----------------------------------------
Attachment AI: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Project Status:
Project is mostly dormant at the moment but still fixing minor security
issues. Still have enough members to engage if needed. Still have future
plans for feature enhancements but no PMC members have had time to engage.
Issues for the board: None to report.
## Membership Data:
Apache Juneau was founded 2017-10-17 (7 years ago)
There are currently 14 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Gary D. Gregory on 2023-04-02.
- No new committers. Last addition was Aditya Kanthale on 2024-10-22.
## Project Activity:
8.1.4 was released on 2024-11-15. Minor bug fixes.
9.0.0 was released on 2023-02-27. Major release.
## Community Health:
Community is still responsive, but overall traffic has decreased.
dev@juneau.apache.org had a 2% decrease in traffic in the past quarter (72
emails compared to 73)
-----------------------------------------
Attachment AJ: Report from the Apache Kafka Project [Mickael Maison]
## Description:
The mission of Kafka is the creation and maintenance of software related to
Distributed publish-subscribe messaging system
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kafka was founded 2012-11-21 (12 years ago)
There are currently 65 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Josep Prat on 2024-09-06.
- Andrew Schofield was added as committer on 2024-12-05
## Project Activity:
In the past quarter we released Kafka 3.7.2 which is a bugfix release.
Kafka 4.0.0 is currently in progress.
This release will remove ZooKeeper support. The release is currently
in code freeze. We expect to have the 1st release candidate in the
coming weeks.
## Community Health:
The project activity on mailing lists, Jira and GitHub is high.
The increase in commits and PRs opened is mostly due to the work
around ZooKeeper removal.
The massive increase in PRs closed is due to old PRs being
automatically closed by the stale PR GitHub action we put in place a
few months ago.
-----------------------------------------
Attachment AK: Report from the Apache Kibble Project [Sharan Foga]
-----------------------------------------
Attachment AL: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters
## Project Status:
Current project status: Ongoing and mature project with low to moderate
activity. There have been jenkins build issues cropping up in github mirror
for PRs that have taken some time. Possibly due to server changes with
increased concurrency. A new release has been discussed a couple time over the
last quarter but those issues and others have gotten in the way. We will
likely target a release early in this quarter. We have had some new
contributors recently that show promise for possible committership. Will
continue to track.
Issues for the board: none.
## Membership Data:
Apache Knox was founded 2014-02-18 (11 years ago)
There are currently 24 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marton Balázs on 2022-11-27.
- No new committers. Last addition was Marton Balázs on 2022-11-28.
## Project Activity:
We will start a new release discussion shortly with the number of changes and
dependency upgrades in place, it is definitely time. The addition of new
community members is encouraging. While Knox is a mature project, it is being
used in new and interesting ways such as in containerized deployments for use
as an istio external authorizer in kubernetes. We are tracking new community
members for committership and hope to invite one or more in coming weeks.
## Community Health:
dev@knox.apache.org had a 34% increase in traffic in the past quarter (374
emails compared to 279) - I believe some of this increase is due to the build
failures that were being encountered.
29 commits in the past quarter (11% increase) - some new contributors bring
patches to the community.
7 code contributors in the past quarter (40% increase) 32 PRs opened on
GitHub, past quarter (18% increase) 30 PRs closed on GitHub, past quarter
(-11% change) - decrease in closed PRs is absolutely related to the jenkins
checks failures that were encountered. We need a few rebases for dependabot
PRs to close them down.
Previous board comments regarding PMC members that are not active anymore have
been noted and we may take action to remove them. This just hasn't been a
priority. We have enough active PMC members for any call to action at this
time as well.
-----------------------------------------
Attachment AM: Report from the Apache Kylin Project [Li Yang]
## Description:
The mission of Apache Kylin is the creation and maintenance of software
related to a distributed and scalable OLAP engine, with a focus on
pre-computation according to learned query patterns.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Kylin was founded 2015-11-18 (9 years ago) There are currently 52
committers and 23 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08.
- Lu Cao, Pengfei Zhan, Longfei Jiang, Yinghao Lin was added as committer in
Nov 2024, based on their significant contribution to Kylin v5.0.
## Project Activity:
Apart from the decreased stats below, Kylin 5.1 development went well in the
past months. KYLIN-5983 is the main enhancement of 5.1, to greatly improve the
"smartness" of cube creation and maintenance. And there are a few security
improvements too. We plan to get Kylin 5.1 out in a few weeks.
With the committers coming back from the lunar new year holidays, and with the
5.1 release getting closer, the stats are expected to re-bounce in the next
quarter.
## Community Health:
- dev@kylin.apache.org had a 66% decrease in traffic in the past quarter (15
emails compared to 43)
- issues@kylin.apache.org had a 89% decrease in traffic in the past quarter (76
emails compared to 658)
- user@kylin.apache.org had a 43% decrease in traffic in the past quarter (4
emails compared to 7)
- 7 commits in the past quarter (-87% change)
- 7 code contributors in the past quarter (-30% change)
- 9 PRs opened on GitHub, past quarter (-79% change)
- 10 PRs closed on GitHub, past quarter (-78% change)
-----------------------------------------
Attachment AN: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AO: Report from the Apache Logging Services Project [Piotr Karwasz]
## Description:
The mission of the Apache Logging Services project is to create and maintain
software for managing the logging of application behavior and related
software components.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Logging Services was founded 2003-12-17 (21 years ago)
There are currently 46 committers (18 active)
and 23 PMC members (15 active) in this project.
The Committer-to-PMC ratio is 2:1 (1:1 for active members).
Community changes, past quarter:
- No new PMC members. Last addition was Fred am Nil on 2024-08-07.
- Jay Katariya was added as committer on 2025-01-22
## Project Activity:
At the time of the last report (2024-11-20), Apache Logging Services had
3 active projects (log4cxx, log4net, Log4j). This situation has not changed
and their status is:
Log4cxx:
The project is active, with a high activity.
Many OSS-Fuzz tests were submitted by Google's partner ADA Logics[1] and the
team is actively analyzing and fixing the problems that were discovered.
None of the problems resulted in vulnerabilities.
Last release: log4cxx-1.3.0 was released on 2024-10-18
[1]
https://github.com/apache/logging-log4cxx/issues?q=is%3Apr+author%3AAdamKorcz
Log4j:
The project is active, with a moderate activity.
The project has added GraalVM support and is actively testing its
compatibility with Android[2]. Additional migration tools were developed
to help users migrate from Log4j 1 (EOL-ed 10 years ago)[3].
Log4j activity has declined following the conclusion of funding from the
Sovereign Tech Agency
Releases:
LOG4J-2.24.3 was released on 2024-12-13.
LOG4J-2.24.2 was released on 2024-11-21.
LOG4J-3.0.0-BETA3 was released on 2024-11-12.
[2] https://github.com/apache/logging-log4j2/issues/2833
[3] https://github.com/apache/logging-log4j2/issues/3220
Log4net:
The project is active, with a moderate activity.
The project is currently concentrating on migrating the website to Antora and
improving the build automation[1], which explains the decrease in code commits.
In the meantime log4net 3.x released in September has reached 1.2 million
downloads on NuGet.
Last release: log4net-3.0.3 was released on 2024-11-07
[4] https://github.com/apache/logging-log4net/pull/204
[5] https://www.nuget.org/packages/log4net#versions-body-tab
## Community Health:
The community behind the project is healthy and continuously provides us
feedback and guidance.
On our side we tend to answer user questions and reports within a couple of
days.
-----------------------------------------
Attachment AP: 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 currently
## Membership Data:
Apache Logo Development was founded 2024-08-21 (6 months ago)
There are currently 17 committers and 16 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 Melissa Logan on 2024-08-28.
- No new committers were added.
## Project Activity:
The committee has successfully set up a test vote that allows for both a
summary and in-depth view of all the design candidates, and is currently
testing to make sure everything works as intended.
The tentative plan (being worked on right now) is to call for a first round of
voting on March 13th through 20th (a seven day period), then assess the
results, refine the candidate list and have the final candidate ideas reviewed
and polished by professional designers. We will then call a second round of
votes at a later point in time. We hope the chair will also announce this
first date at the annual members' meeting in March.
Once the date has been set for the first round, we'll work on an instructional
document that relays our intentions and expectations for the first round to
the membership.
## Community Health:
No material changes in the makeup of the committee this past quarter.
This was expected, so there really isn't anything to report on.
-----------------------------------------
Attachment AQ: Report from the Apache ManifoldCF Project [Piergiorgio Lucidi]
## Description:
The mission of ManifoldCF is the creation and maintenance of software related
to Framework for connecting source content repositories to target repositories
or indexes.
## Issues:
None
## Membership Data:
Apache ManifoldCF was founded 2012-05-15 There are currently 25
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, since last report in August:
- No new PMC member. Last addition was made on 2023-08-03.
- No new committers. Last addition was on 2019-08-17.
## Project Activity:
SDK 1.02 released on 2025-02-10
2.28 was released on 2025-01-15
2.27 was released on 2024-09-26
2.26 was released on 2023-11-01
2.25 was released on 2023-06-01
The Community is continuing to follow these goals:
- Creating a brand new Roadmap
Now that we have 2.28 released with the SDK I think that we
are now ready to put on the table the discussion related to the next steps.
We are asking to the community which priorities they want in terms of effort:
resiliency, security and so on.
What we should discuss can be summarized here:
- Removing legacy connectors
- Updating connectors
- Adding new connectors (RAG Output Connectors)
- Upgrade of the architecture (from In-Process to Out-Of-Process)
- Making the platform more resilient (external agents / external connectors)
- Security
- Solving vulnerabilities
We have currently solved many vulnerabilities updating the libraries and we
have to continue in this way. Unfortunately it's something not easy to do due
to the high amount of dependencies included in the connectors classloader.
- Making the release scripts agnostic
We finally have a GPG key, thanks to the Apache Security Team, enabled on
GitHub in order to publish RCs and Maven artifacts. We still have to update the
GitHub workflows in order to use it correctly. The current effort was
invested in finalizing the brand new ManifoldCF SDK.
## Community Health:
We didn't receive any pull request at the moment but we have one contributor
that is helping us on finding bugs and solving vulnerabilities.
-----------------------------------------
Attachment AR: Report from the Apache Mnemonic Project [Gordon King]
-----------------------------------------
Attachment AS: Report from the Apache Oozie Project [Dénes Bodó]
-----------------------------------------
Attachment AT: Report from the Apache OpenOffice Project [Dave Fisher]
## Description
The mission of OpenOffice is the creation and maintenance of software related
to an open-source, office-document productivity suite.
## Project Composition
- Apache OpenOffice was founded 2012-10-16 (12 years ago)
- There are currently 141 committers and 28 PMC members in this project.
- The Committer-to-PMC ratio is roughly 5:1.
- No new PMC members. The last addition was Czesław Wolański on 2023-01-14.
- One new committer. John Bampton was added 2025-01-07.
## Project Activity
### Recent Releases
- 4.1.15 was released on 2023-12-22
- 4.1.14 was released on 2023-02-27
- 4.1.13 was released on 2022-07-22
- Binary downloads (total over all) as of February 1: 385,284,081
### Codebase in OpenOffice repository
Work continues on the 4.2 future release; This included:
- Work on building a 64bit Windows version.
- Work on code spelling and code linting.
- dev@openoffice.apache.org traffic nearly tripled in the past quarter.
- issues@openoffice.apache.org doubled in traffic in the past quarter.
- l10n@openoffice.apache.org had traffic limited to onboarding a new volunteer
for Vietnamese.
### Documentation
- The OpenOffice-docs repository is where the small documentation team makes
updates.
- The Chapters for the Writer Guide are completed and ready to published, and
the compilation of the complete book is completed.
- The Chapters of the Calc Guide are ready for final review.
- Work has started on the update of the Impress Guide from the old 3.3
Version.
- doc@openoffice.apache.org had a slight decrease 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 an increase in traffic in the past quarter.
- users-de@openoffice.apache.org had a significant decrease in traffic in the
past quarter.
### 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.
- Extensions and Templates downloadable artifacts will remain at SourceForge.
- The static html will be hosted on a project vm.
### Community Health
Community overall health is improving. We are seeing several developers taking
on Win64, ODF 1.3, Boost, NSS, icu4 and OpenSSL updates. Documentation is
being updated after a long time and we are getting translation volunteers.
## Infrastructure
We had some issues on the wiki/forum host and these configuration issues are
fixed with some assistance.
### 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.
### 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 AU: Report from the Apache OpenWhisk Project [Dave Grove]
## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: none
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (6 years ago)
There are currently 54 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cosmin Stanciu on 2022-02-22.
- No new committers. Last addition was Luke Roy on 2023-03-06.
## Project Activity:
No significant project activity since the November board report.
No releases were made since the November board report.
The most recent releases were part of a wave of openwhisk-runtime
releases made in August/September 2024:
+ openwhisk-runtime-java-1.20.0 was released on 2024-09-23.
+ openwhisk-runtime-php-1.21.0 was released on 2024-09-23.
+ openwhisk-runtime-python-1.20.0 was released on 2024-09-23
## Community Health:
There are sufficient PMC members paying attention to handle security issues,
vote on releases, and answer the relatively low volume of user questions that
we get.
We did get a handful of PRs with minor bug fixes from users that were merged
in a timely manner. However, there is no significant new development happening
in the project (either from committers or from community members). With the
exception of a small number of academic research projects, users of OpenWhisk
have moved on to other serverless platforms. Given the significant size of the
code base, the lack of ongoing development effort, and the declining usage of
openwhisk, the project appears to be winding down and may need to seriously
discuss a transition to the Attic in 2026.
-----------------------------------------
Attachment AV: Report from the Apache Ozone Project [Sammi Chen]
## Description
Apache Ozone is a scalable, redundant, and distributed object and file
store,
designed to scale to billions of objects/files and run on clusters of
thousands
of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop
Compatible File System implementation.
## Issues
None.
## Membership Data
- Apache Ozone was founded 2020-10-21.
- There are currently 82 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
- In the past quarter,
Xi Chen was added to the PMC on 2025-02-08
## Project Activity
- Continuous Recon feature and OM snapshot feature enhancements.
- File/Object deletion improvement, make directory deletion
multi-threading, add new metrics, fix the ratis request ID reuse problem,
etc.
- Command line enhancements, interactive mode ozone shell, command to
repair broken FSO tree, command to show internal component versions,
command to create RocksDB checkpoint, CLI layout refactor, etc.
- SCM safemode enhancement, support EC containers, refactor safe mode exit
rule efficiency, etc.
- Container reconciliation development is ongoing.
- Use symmetric key instead of asymmetric key to sign delegation token.
- S3 gateway, support object tags support, use individual port for S3 web
admin UI, etc.
- Streaming write supports Hsync and Hflush.
- Documentation improvement, hive integration guide, distCP integration
guide, impala integration guide, etc.
- Continuous github build and CI improvements, flaky unit test fixing,
refactor unit test to reduce execution time, etc.
- Ozone 1.4.1 release is completed. Next release will be Ozone 2.0.0.
- Migrate Hadoop common dependency from 3.3.6 to 3.4.1.
- LegacyReplicationManager support is removed.
- File per chunk layout on Datanode is deprecated. Datanode will fallback
to file per block layout if file per chunk layout is configured.
- Non-Ratis support for OM and SCM is under removal.
## Releases Data
- 1.0.0 was released on 2020-09-02.
- 1.1.0 was released on 2021-04-20.
- 1.2.0 was released on 2021-11-17.
- 1.2.1 was released on 2021-12-22.
- 1.3.0 was released on 2022-12-18.
- 1.4.0 was released on 2024-01-19.
- 1.4.1 was released on 2024-11-24.
## Community Health
Last board report was sent on 12th Nov 2024. Since last report,
- 36 code contributors who have commits in the past quarter (-3% change)
- dev@ozone.apache.org had 72 emails in the past quarter (-22% change)
- 338 PRs closed on GitHub, past quarter (+28% change)
- 335 PRs opened on GitHub, past quarter (+25% change)
- 286 commits in the past quarter (+28% change)
Note: The commit & PR count excludes the ones from user "app/dependabot",
who has many commits for dependency jar version upgrade.
-----------------------------------------
Attachment AW: Report from the Apache Perl Project [Steve Hay]
## Description:
The mission of Perl is the creation and maintenance of software related to
Dynamic websites using Perl
## Project Status:
Current project status: Ongoing, with low activity
Issues for the board: none
## Membership Data:
Apache Perl was founded 2000-03-10 (25 years ago)
There are currently 21 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hay on 2012-03-01.
- No new committers were added.
## Project Activity:
The last release was mod_perl-2.0.13 on 2023-10-21.
No new release is planned yet since there has been little activity in the last
quarter, but will certainly be produced whenever necessary.
## Community Health:
Mailing lists have been quiet, but that is not unusual.
We still need to find a new home for binary builds since the demise of
home.apache.org. It's a shame the ASF has no solution for this. Presumably it
affects other projects too.
-----------------------------------------
Attachment AX: Report from the Apache Phoenix Project [Istvan Toth]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Project Status:
Current project status: Ongoing
Issues for the board: No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-21 (11 years ago)
There are currently 58 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jacob Isaac on 2023-11-07.
- No new committers. Last addition was Palash Chauhan on 2024-06-11.
## Project Activity:
Apache Phoenix had its last main release 5.2.1 on 2024-11-12.
5.2.2 release is planned for early spring, pending the release of HBase 2.6.2
and 2.5.11 which will significantly reduce our transitive CVE exposure.
In the past quarter:
* Landed several improvements to the Change Data Capture feature:
* PHOENIX-7500 Add PARENT_PARTITION_ID to SYSTEM.CDC_STREAM table's composite
pk
* PHOENIX-7473 Eliminating index maintenance for CDC index
* PHOENIX-7469 Partitioned CDC Index for partitioned tables
* PHOENIX-7460 Update stream metadata when a data table region splits
* PHOENIX-7459 Bootstrap stream metadata when CDC is enabled/created on a
table
* PHOENIX-7458 Create new SYSTEM tables for tracking CDC Stream metadata
* PHOENIX-7425 Partitioned CDC Index for eliminating salting
* Landed some other notable new features
* PHOENIX-7434 Extend atomic support to single row delete with condition on
non-pk columns
* PHOENIX-7462 Single row Atomic Upsert/Delete returning result should return
ResultSet
* PHOENIX-7424 Support toStringBinary/toBytesBinary conversion
* About a dozen other commits: smaller features, bugfixes, build and
dependency changes
## Community Health:
Overall community health is good. We have released a new maitenance release,
and major feature work continues on the CDC feature. Most of the development
is still done by our core team of about a dozen active developers.
Activity has decreased this quarter, some of which is due to the festive
season and the increased activity related to the 5.2.1 release at the end of
the last quarter.
-----------------------------------------
Attachment AY: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment AZ: Report from the Apache Pinot Project [Kishore G]
-----------------------------------------
Attachment BA: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats.
The Apache POI PMC also handles bugfixes for the XMLBeans project:
XMLBeans is a tool that allows you to map XML files to generated Java
classes via XML Schema definitions.
## Project Status:
- Overall: Low activity/Mostly maintenance only
- Activity on the project is low with no-one willing/able to invest time to
look for new committers. It seems the number of people willing to be part
of an old/established project is low in general. So this project is
steering towards a mostly-maintenance mode unless someone new starts to
invest time.
- Note: None of the active committers wants to spend time looking for new
people, so suggesting to reach out to others or invest in "marketing" will
likely not lead to much improvement.
## Membership Data:
Apache POI was founded 2007-05-16 (18 years ago) There are currently 41
committers and 34 PMC members in this project. The Committer-to-PMC ratio
is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marius Volkhart on 2020-12-27.
- No new committers. Last addition was Marius Volkhart on 2020-12-19.
## Project Activity:
- Bugfix releases for Apache XmlBeans and Apache POI were done, providing
mostly bugfixes and smaller adjustments.
- Automated fuzzing via OSS-Fuzz continues, this provides cases where
potential bugs and security issues can be detected, see
https://github.com/google/oss-fuzz and
https://bz.apache.org/bugzilla/show_bug.cgi?id=66425 for more details.
- Some support for "reproducible" builds and reproducible output formats
was released in 5.4.0 release, see
https://poi.apache.org/help/faq.html#faq-reproducible-build-and-output
## Project Release Activity:
- Apache POI 5.4.0 was released on 2025-01-08.
- XMLBeans-5.3.0 was released on 2024-12-13.
- XMLBeans-5.2.2 was released on 2024-11-05.
## Community Health:
- There are a few bug-reports and user-questions which indicates that Apache
POI is in use. Questions via email or on Stackoverflow usually get
answers.
- Bug-numbers slowly increase over time. Some newly reported issues are
fixed, but we usually get more bugs/questions reported than are addressed
by the small number of active committers, so some bugs do not get
attention any more.
- We have a very small number of active committers. There are very few
potential candidates and no-one plans to spend effort to go looking for
new ones.
### XMLBeans
- It seems there are is a small but active set of users of XMLBeans besides
Apache POI itself.
- Bug influx for XMLBeans is very low in general because it is a stable
project in maintenance-only mode.
## Bug Statistics:
### Apache POI
- 621 bugs are open overall (-1)
- Having 144 enhancements (+-0)
- Thus having 477 actual bugs (-1)
- 117 of these are waiting for feedback (-1)
- Thus having 360 actual workable bugs (+-0)
- 3 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {XSSF=101, HSSF=80, SS
Common=44, HWPF=34, XSLF=30, XWPF=22, POI Overall=14, SXSSF=8, POIFS=7,
HSMF=6, OPC=5, HPSF=4, HSLF=3, HPBF=1, SL Common=1}
### Apache XMLBeans
- 163 open issues (+-0)
- 117 Bug (+1)
- 28 Improvement (+-0)
- 15 New Feature (-1)
- 2 Wish (+-0)
- 1 Task (+-0)
-----------------------------------------
Attachment BB: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, .Net, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid JMS 2.6.1 was released on 4th October 2024.
- Qpid JMS 1.12.1 was released on 4th October 2024.
- Qpid Proton 0.40.0 was released on 25th November 2024.
# Community:
- The main user and developer mailing lists continue to be active and
JIRAs are being raised and addressed in line with prior activity levels.
- There were no new PMC member additions in this quarter.
The most recent new PMC member is Daniil Kirilyuk, added 22nd January 2024
- There were no new committer additions in this quarter.
The most recent new committer is Daniil Kirilyuk, added 17th February 2023
# Development:
- Proton had its 0.40.0 release, cleaning up older areas of Proton C and its
language bindings, and with improvements around flow control and delivery
fairness. Work continues on adding transaction support for the C++ binding
and other API cleanup towards a followup release, and working towards a
later removal of deprecated APIs/features in a new major version.
- Progress continues toward a ProtonJ2 1.0.0-M23 release, likely in the next
week, including some bug fixes and removal of experimental support for
Netty 5 now that the 4.2 stream is actually the next route forward.
- Qpid JMS had 1.12.1 and 2.6.1 bug fix releases to address a connection
closure issue introduced in the prior releases. New releases are planned
next week with mostly dependency updates.
- A Proton-Dotnet 1.0.0-M11 release is intended some time this month.
- Work continues on Broker-J towards a 9.2.1 release in the coming weeks,
and then later a 10.0.0 release bumping the minimum Java version required
to Java 17 in order to facilitate also moving to use of Jetty 12.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BC: 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:
- Bhavik Patel was added to the PMC on 2024-09-04
- Fateh Singh was added as committer on 2024-10-14
## Project Activity:
- Ranger 2.6.0 version is being voted on by the community
-- Expected to be released in Feb-2025.
-- Contains 70 bug-fixes, 49 improvements and 2 new features
--- Ranger Base image on UBI9 with memory and build optimizations
--- Feature to import/export individual policies
- Ranger 3.0.0 version is progressing well
-- 38 open issues to be addressed
-- 21 patches to be reviewed to address open issues.
-- contains 608 bug-fixes, 487 new improvements and 22 new features
- Key features addressed in 3.0.0 release in the past quarter:
-- Enhanced KMS capabilities
-- Ranger Plugin Configuration to support to initalize kerberos identity
-- Docker setup to support SQLServer and Oracle database
-- key library upgrades to fix security and/or other issues
-- Improvements on HA implementation
-- Improvements to Ranger REST API for audit access logs to return
additional event times.
-- Log cleanup
## Community Health:
Traffic on some of the mailing lists were high due to release activities.
No other significant changes to mailing list traffic.
- 1651 emails in dev@ranger.apache.org in this quarter
(+ 84% change from past quarter)
- 27 emails in user@ranger.apache.org in this quarter
(- 58% change from past quarter)
- 114 issues opened in JIRA in this quarter
(+ 21% change from past quarter)
- 125 issues closed in JIRA in this quarter
(+ 38% change from past quarter)
- 27 PRs opened on GitHub in this quarter
(- 15% change from past quarter)
- 13 PRs closed on GitHub in this quarter
(- 35% change from past quarter)
## Most Recent releases:
- 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 BD: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
The mission of Apache RocketMQ is the creation and maintenance of software
related to a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data
## Project Status:
Current project status: Ongoing: With moderate activity,
Issues for the board: none
## Membership Data:
Apache RocketMQ was founded 2017-09-20 (7 years ago)
There are currently 76 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Zhouxiang Zhan on 2023-09-21.
- No new committers. Last addition was Chaoyang Liu on 2024-08-10.
## Project Activity:
Learning Sites Upgrade: The RocketMQ Learning Sites have been
fully upgraded, with a significant increase in Chinese learning content.
Upcoming Book: A book related to RocketMQ is soon to be published, with
a foreword written by a RocketMQ technology enthusiast.
## Community Health:
The overall activity level of the Apache RocketMQ community has remained
consistent with previous periods.
the upgrade of learning sites indicate a healthy and growing community
-----------------------------------------
Attachment BE: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat, Postgres and MySQL, and is known to run on other Java servers
and relational databases. Latest release is 6.1.4 on 2024-10-09.
## Project Status:
The project is mostly dormant with most activity around updating
dependencies, making sure the code runs on the latest Java releases and
security fixes.
## Membership Data:
Apache Roller was founded 2007-02-20 (16 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2021-05-24.
- No new committers. Last addition was Yash Maheshwari on 2021-09-01.
## Project Activity:
Roller 6.1.4 was released on October 9, 2024. The team is preparing
for a 6.1.5 release in the next month.
## Community Health:
The Roller community is healthy enough to maintain Roller and make bug
fix and security releases. We're always on the lookout for new contributors.
-----------------------------------------
Attachment BF: Report from the Apache Samza Project [Jagadish Venkatraman]
-----------------------------------------
Attachment BG: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
The mission of Santuario is the creation and maintenance of software related to
XML Security in Java
## Project Status:
Current project status: The Java project is actively maintained and PRs are
getting merged and releases made.
Issues for the board: Nothing to report
## Membership Data:
Apache Santuario was founded 2006-06-27 (19 years ago)
There are currently 18 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Joze Rihtarsic on 2024-05-14.
## Project Activity:
It was a very quiet quarter for the project, just some dependency PRs and one
minor update merged.
## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC
-----------------------------------------
Attachment BH: Report from the Apache SDAP Project [Nga Thien Chung]
## Description:
The mission of Apache SDAP is the creation and maintenance of software related
to an integrated data analytic center for Big Science problems
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SDAP was founded 2024-04-16 (10 months ago)
There are currently 22 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Grace Llewellyn on 2024-06-23.
- Truc Nguyen was added as committer on 2025-01-18
## Project Activity:
Last SDAP release was 1.4.0 on 2024-11-04.
Two CS students taking Cal Poly Pomona Parallel Processing class gave a
presentation on their project of running SDAP within Apache Airflow on
12/4/24.
A poster titled "Open-Source Framework for Earth System Digital Twins"
featuring Apache SDAP was presented at AGU24 in Washington, D.C on 12/13/24.
## Community Health:
### Mailing List
Since last quarter, dev@sdap.apache.org had 5 new threads.
### Contributors
Since last quarter, the SDAP community has merged 1 PR and created/updated
2 Jira issues.
-----------------------------------------
Attachment BI: 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 real-time 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 35 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Guangdong Liu on 2024-05-15.
- Shenghang Zhang was added as committer on 2024-12-16
## Project Activity:
- 2.3.9 was released on 2025-01-18
- 2.3.8 was released on 2024-10-12
- We're develop for the 2.3.10 now
- We have held two community online Meetups in last quarter.
## Community Health:
- 21% decrease in dev mailing list in traffic in the past quarter, which means
we need to discussed issues or features more frequently.
- 201 issues closed on GitHub, past quarter (4% increase).
- Added more than 10 first-time contributors
- We try to gather our PMC and a few committer members to solve the security
issues, and the good news is we have classified these issues and are
handling them now.
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 BJ: Report from the Apache Sedona Project [Jia Yu]
## Description:
The mission of Apache Sedona is the creation and maintenance of software
related to a big geospatial data processing engine. It provides an easy to use
APIs for spatial data scientists to manage, wrangle, and process geospatial data
## Project Status:
Current project status: The project is ongoing.
Issues for the board: No issues here.
## Membership Data:
Apache Sedona was founded 2022-12-20 (2 years ago)
There are currently 21 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Furqaan Khan on 2024-08-20.
- Pranav Toggi was added as committer on 2025-01-10
## Project Activity:
Sedona 1.7.0 release was made in December 2024. This release is a major
release that includes new features, improvements, bug fixes, API breaking
changes, and behavior changes. 6 new people contributed to this release. A few
important updates in this release: (1) Add a new join algorithm for
distributed K Nearest Neighbor Join and a corresponding ST_KNN function (2)
Add new spatial statistics algorithms DBSCAN, Local Outlier Factor, and Getis
Ord Hot Spot Analysis (3) Add new DataFrame based readers for Shapefile, and
GeoPackage. We will make a new minor release 1.7.1 in a few weeks.
## Community Health:
The community is thriving! We’re encouraging contributors to use GitHub issues
instead of JIRA, leading to a surge in activity. As a result, we’re seeing
more GitHub issues opened and a growing number of code contributors.
-----------------------------------------
Attachment BK: Report from the Apache Serf Project [Daniel Sahlberg]
## Description:
The mission of the Apache Serf project is creating and maintaining of software
related to HTTP and associated protocols.
## Project Status
The project has sufficient PMC oversight.
There are no threats to the sustainability or resillence of the project,
although the project is very much dormant due to lack of need/requirements
from our users.
The project has no requests for the Foundation.
## Membership Data:
Apache Serf was founded 2015-08-18 (9 years ago).
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
## Community changes, past quarter:
No new PMC members. Last addition was Daniel Sahlberg and Nathan Hartman on
2023-10-05.
No new committers. Last addition was Daniel Sahlberg and Nathan Hartman on
2023-10-09.
## Project Activity
Recent releases:
* 1.3.10 was released on 2023-05-31.
* 1.3.9 was released on 2016-08-31.
## Community Health:
In January, a new contributer sent a minor patch related to the CMake build
system. He has previously made valuable contributions to Subversion. We don't
know if he is interested in future contributions but we will keep our eyes
open.
-----------------------------------------
Attachment BL: Report from the Apache ServiceComb Project [Bao Liu]
## Description:
The mission of Apache ServiceComb is the creation and maintenance of software
related to a microservice framework that provides a set of tools and components
to make development and deployment of cloud applications easier.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ServiceComb was founded 2018-10-17 (6 years ago)
There are currently 38 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Cheng Youling on 2024-10-12.
- Chen Zhida was added as committer on 2025-01-16
## Project Activity:
ServiceComb Java Chassis 2.8.22 was released on 2025-01-07.
ServiceComb Java Chassis 3.2.4 was released on 2024-12-31.
ServiceComb Java Chassis 3.2.3 was released on 2024-11-26.
## Community Health:
Overall, community health is good. ServiceComb Java Chassis made 3 releases,
and there are some new features developed in 3.x.
There are some development around the ServiceCenter.
We added one new Committer.
-----------------------------------------
Attachment BM: Report from the Apache ShardingSphere Project [Liang Zhang]
## Description:
The mission of Apache ShardingSphere is the creation and maintenance of
software related to a database clustering system providing data sharding,
distributed transactions, and distributed database management
## Project Status:
Current project status: OK
Issues for the board: None
## Membership Data:
Apache ShardingSphere was founded 2020-04-15 (5 years ago)
There are currently 63 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Longtao Jiang on 2024-03-28.
- No new committers. Last addition was Chenyang Ma on 2024-05-27.
## Project Activity:
Released version 5.5.2 and developing for version 5.5.3
## Community Health:
The project has become very mature, everything is running smoothly.
Keep the pace of releasing a version each quarter.
-----------------------------------------
Attachment BN: Report from the Apache ShenYu Project [Yu Xiao]
## Description:
ShenYu is a Java native API Gateway for service proxy,
protocol conversion and API governance.
## Project Status:
Current project status: Good Healthy.
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache ShenYu was founded 2022-07-20 (3 years ago)
There are currently 57 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Yunlong Lee on 2024-02-04.
- No new committers. Last addition was Shinan Chen on 2024-08-30.
## Project Activity:
We are released version 2.7.0 on 2025-1-20.
Software development activity:
- We added support plugin enabled apated namespace.
- We added support selector copy and rule copy adapted to namespace .
- We added support namespace import sync front.
- We added support namespace config import.
- We added support for gray release in divide-plugin.
- We added support namespace adapt middleware sync.
- We added support springcloud dynamic register.
- We added support dubbo method configure.
- We added support namespace export operation.
- We added export support plugin template data.
- We fixed bug when using http-polling mode.
- We fixed active plugin filtered by enable.
- We fixed outOfMemoryError for logging plugin.
- We fixed duplicate header for request plugin.
- We fixed loadbalance config for dubbo plugin.
- We refactor bodyParamUtils with Caffeine cache.
- We refactor plugin-jwt SPI extension for parsing JWT.
- We refactor code for shenyu-kubernetes-controller.
- We refactor code for shenyu-registry.
- We refactor code for shenyu-sync-data.
- We refactor code for shenyu-client.
Meetups and Conferences:
- Community meetings(4) to discuss development tasks and how to build
an open governance community.
## Community Health:
Overall community health is good.
Since the last report, add new 5 contributors added (currently:399).
add +3 subscribers to dev@shenyu.apache.org mailing (currently:511)
-----------------------------------------
Attachment BO: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
The mission of Apache SIS is the creation and maintenance of software providing
data structures for developing geospatial applications compliant with the model
of OGC/ISO international standards.
## Project Status:
Current project status: ongoing with high activity
(not visible because currently occurring on a clone until ready).
Issues for the board: none
## Membership Data:
Apache SIS was founded 2012-09-19 (12 years ago)
There are currently 22 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Alexís Manin on 2021-05-27.
- No new committers. Last addition was Bruno P. Kinoshita on 2021-06-23.
## Project Activity:
Work on Apache SIS 1.5 release is still ongoing. The last release was 1.5
years ago, which is much longer than desired. The reason for this delay is
because we participated to a Testbed from the Open Geospatial Consortium (OGC)
in which Apache SIS has been used (together with other software) for
prototyping a new data format. This effort (not only in development, but also
in discussions), together with the effort required for the integration of
GeoPackage and GDAL contributions mentioned in the previous report, have
delayed the work needed for the release. The work needed for the release is an
upgrade to the latest ISO 19111 international standard (Referencing by
coordinates), which is core to Apache SIS mission. Because that work was
ongoing before we switched to Testbed and other works, it should be completed
before release if we want to avoid a half-backed release.
There is plan to organize another OGC / OSGeo / ASF joint code sprint in
June 2025, hosted by the Living Planet Symposium [1] organized by the
European Space Agency (ESA). We have the okay from press at this time,
and we are waiting for confirmation from OGC and ESA.
[1] https://lps25.esa.int/
[2] https://lists.apache.org/thread/ow3wns2v11d75r0hljoqtfqck0004brj
## Community Health:
The community has been quiet in the last 3 months,
in part because of focus on OGC Testbed effort.
-----------------------------------------
Attachment BP: Report from the Apache Solr Project [Jason Gerlowski]
## Description:
The mission of Apache Solr is the creation and maintenance of software related
to highly scalable distributed document search and analytics
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Solr was founded as a TLP 2021-02-16 (4 years ago) after 15 years within
the Lucene project. There are currently 98 committers and 61 PMC members in
this project. The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Gibney on 2022-12-20.
- Pierre Salagnac was added as committer on 2024-12-05
## Project Activity:
Recent releases:
* Solr 9.8.0 was released on 2025-01-23
* Solr Operator 0.9.0 was released on 2025-01-22
Areas of development & interest:
* Index+Query Time integration with LLM Model Providers
* API renovation and migration continues
* Transitioning from Apache to Jetty HttpClient
* Introduce Apache Curator usage for ZK connection management
* Deprecations and other Preparation for an approaching 10.0 release
* Deprecation+Removal of 'hdfs' and 'hadoop-auth' modules
## Community Health:
Commit activity has held roughly steady when compared to this same quarter
last year, while discussion on our 'dev@' and 'users@' mailing lists is up
10-15% in that same time.
Qualitatively the community feels active, vibrant, and healthy. Discussion
on our 'dev' list has brought up a number of fresh ideas (LinkedIn and social
media engagement, changelog management, etc.) recently. And developers are
looking forward to our Solr 10 release, which many expect to come out later
this year.
-----------------------------------------
Attachment BQ: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Description:
Apache Spark is a fast and general purpose engine for large-scale data
processing. It offers high-level APIs in Java, Scala, Python, R and SQL as
well as a rich set of libraries including stream processing, machine learning,
and graph analytics.
Issues for the board:
- None
Project status:
- The Spark 4.0 branch has been cut and has entered the QA stage. We encourage
the community to test it out and give feedback to help with the release!
- We released Spark 3.5.4 on December 20th, 2024.
- The PMC voted to add one new committer (Bingkun Pan) and one new PMC member
(Jie Yang) to the project.
- The proposal to "Use plain text logs by default" was successfully passed.
Trademarks:
- No changes since last report.
Latest releases:
- Spark 3.5.4 was released on Dec 20, 2024
- Spark 3.4.4 was released on Oct 27, 2024
- Spark 4.0 Preview 2 was released on Sept 26, 2024
Committers and PMC:
- The latest committer was added on Nov 13, 2024 (Bingkun Pan).
- The latest PMC member was added on Jan 21st, 2025 (Jie Yang).
-----------------------------------------
Attachment BR: 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: Ongoing, low activity.
Issues for the board: There are no issues for the board currently.
## 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:
- Work is still ongoing for STeVe version 3
- Version 2 (aka pysteve) has had an sqlite database backend added. This has,
in part, helped our own infrastructure team ditch the older elasticsearch
backend, ensuring a quicker migration of voting services from one machine to
a newer one.
- The upcoming annual members meeting will also be using the new infra-backed
"voter gateway", designed to eliminate the need to manually create and
assist with ballots.
## Community Health:
No changes of note in community health over the past quarter and change, but
also no signs of issues being ignored.
-----------------------------------------
Attachment BS: Report from the Apache StreamPark Project [Huajie Wang]
## Description:
StreamPark is a streaming application development framework and cloud-native
real-time computing platform.
Its vision is make stream processing easier.
## Project Status:
Current project status: New Issues for the board: none
## Membership Data:
Apache StreamPark was founded 2025-01-23 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 (project graduated recently).
- No new committers were added.
## Project Activity:
- We have completed all major tasks for graduating from the incubator.
- We redesigned the website and updated the project information on our
official website
- We published a press release to celebrate our graduation.
- We have updated the README, added instructions for Docker-based project
deployment, and included a one-click installation video tutorial for the
project.
- We started using the new release process for publishing version
- We are preparing version 2.1.6 and plan to complete and release it within
three weeks.
## Community Health:
Since the last report, 9 new developers have joined our community, bringing
the total number of contributors to 155. We have released version 2.1.5 of
Apache, and based on our data, over 90 users (issue/163) are currently using
it in production.
We are in the process of planning to nominate a new committer. Our project is
progressing well, with a steadily growing user base. Additionally, we plan to
participate in more meetup events to raise awareness of the project and
encourage further development.
-----------------------------------------
Attachment BT: Report from the Apache StreamPipes Project [Philipp Zehnder]
## Description:
The mission of Apache StreamPipes is the creation and maintenance of software
related to a self-service Industrial IoT toolbox which enables non-technical
users to connect, analyze and explore IoT data streams
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache StreamPipes was founded 2022-11-16 (2 years ago)
There are currently 33 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Zhenyu Luo on 2023-10-17.
- Marcel Frueholz was added as committer on 2025-01-23
## Project Activity:
- We are currently preparing for the upcoming 0.97.0 release.
- The old Live Dashboard has been removed and replaced with the
new Data Explorer dashboard for improved data visualization and analysis.
- The asset concept has been further integrated
into the software, enhancing its usability.
## Community Health:
- Several new feature ideas were submitted by the community
via GitHub discussion
-----------------------------------------
Attachment BU: Report from the Apache Subversion Project [Nathan Hartman]
## Description:
The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control
solution characterized by its reliability as a safe haven for valuable
data; the simplicity of its model and usage; and its ability to
support the needs of a wide variety of users and projects, from
individuals to large-scale enterprise operations.
## Project Status:
Current project status: Ongoing, mature.
Issues for the board: None at this time.
## Membership Data:
Apache Subversion was founded 2010-02-16 (15 years ago). Prior to
joining ASF, the project began in February of 2000 (25 years ago).
There are currently 88 committers and 49 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Timofei Zhakov on 2024-06-24.
- No new committers. Last addition was Timofei Zhakov on 2024-06-24.
## Project Activity:
This quarter we released Subversion 1.14.5. This was a security and
bugfix release.
Preparatory work for a new feature, called 'xpatch'. Since
Subversion's inception, Subversion supports a 'diff' and 'patch'
workflow, utilizing patch files in a traditional unidiff format
supported by several version control systems and Unix utilities. Some
types of committable changes cannot be conveyed in this format, such
as empty files and directories. Also, Subversion's patch application
logic is limited as compared to the merge and conflict resolution
possible with in-tree data. The 'xpatch' feature hopes to provide for
these possibilities by implementing a Subversion-specific binary patch
format ('xpatch') which can convey all types of committable changes
and by using Subversion's existing merge and conflict resolution logic
to apply such patches. In addition to being useful in its own right,
this feature should (hopefully) make it possible to improve upon the
currently experimental shelving functionality. This feature is in
addition to (not a replacement for) Subversion's traditional diff and
patch workflows, which will remain unchanged. The preparatory work
done in this quarter mostly revolved around refactoring the existing
diff and merge code to lay the groundwork for the new feature
implementation. This has taken place on a separate 'apply-processor'
branch.
Continuous Integration (CI) using GitHub Actions (GHA): Initially
begun in the prior quarter, this has been improved significantly this
quarter. Support has been added for building the libsvn_auth_kwallet
and libsvn_auth_gnome_keyring credential libraries in the Linux
workflow; testing of libsvn_ra_serf has been enabled, testing of the
(experimental) shelving v2 and v3 tests has been enabled, and tests
are now run in parallel. We worked with Infra to ensure our
notifications@ list will receive status messages from GHA. Since our
repository is Subversion and GitHub is a read-only mirror, Infra
implemented special handling to make this possible. Thanks, Infra!
Note that previously Subversion used BuildBot for CI testing, with
numerous machines and operating systems. Unfortunately, our BuildBot
workflows broke when builds@ upgraded from version 0.8 to 3.2 around
2021. Though we did succeed to restore some of our BuildBot services,
it seems we lack volunteers with experience in BuildBot to adequately
maintain this. Therefore, it is likely that we will eventually
consolidate all CI to use GitHub Actions in the future (unless new
volunteers emerge to maintain BuildBot as well).
Attempted to restart the discussion about the 1.15.0 release line and
worked on the 1.15 draft release notes. This release line has been in
the works for some time now, with nice features awaiting release, like
Pristines on Demand, Streamy Checkouts, and other improvements. There
is a longstanding stumbling block regarding client side checksum
storage. We hope to overcome this issue in some amicable manner.
Ongoing maintenance and quality improvements: Subversion's SWIG
bindings, test suite, unix-build, other tools and scripts used by
Subversion developers and release managers, and the website.
## Community Health:
The community appears healthy for a mature and stable project. We have
made security/bugfix releases each of the last two quarters. Multiple
developers monitor the mailing lists and respond when needed. User
questions usually receive helpful responses on the mailing lists, from
both project developers and community members. Substantial new
developments are taking place in the codebase.
Our community is fully volunteer-driven and we would like to thank
everyone for their support.
-----------------------------------------
Attachment BV: Report from the Apache Superset Project [Maxime Beauchemin]
## Description:
The mission of Apache Superset is the creation and maintenance of software
related to data exploration, analysis, visualization, and dashboarding
## Project Status:
Current project status: Ongoing, with high levels of contributor activity, and
a small but highly engaged subset of PMC members.
Issues for the board: None, really... but a couple of passing updates:
* Regaerding the ongoing discussion of AI integrations for docs site will be
taken up with VP Privacy. It sounds like a DPA and opt-in mechanism for
Kapa.ai is in place, so we'll investigate further.
* There's an open Infra ticket (INFRA-25690) that would be helpful to
discuss/resolve. We're hoping to get an ASF-hosted database
(Postgres/RDS/whatever) to scrape community stats/activity into and populate
a Superset example dashboard with live updates. We hope this dashboard of
open work items and leaderboards on the project/community will boost project
contribution.
## Membership Data:
Apache Superset was founded 2020-11-17 (4 years ago)
There are currently 68 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Joe Li was added to the PMC on 2024-12-01
- Enzo Martellucci was added as committer on 2024-12-12
- Hai Do was added as committer on 2025-02-09
## Project Activity:
4.0.2 was released on 2024-07-02.
4.0.1 was released on 2024-05-13.
3.1.3 was released on 2024-05-09.
5.0.0 is currently in testing/voting, and is shaping up to be our smoothest
major version release yet.
Several significant project proposals (SIPs) are in progress to push forward
major initiatives (theming, extensions/extensibility, testing refactoring, a
new developer portal, and more). We expect significant foundational progress
in 2025.
## Community Health:
Slack grew by ~1100 members in the last quarter.
88 code contributors in the past quarter (-4% change) 878 PRs opened on
GitHub, past quarter (-16% change) 893 PRs closed on GitHub, past quarter (-7%
change) 319 issues opened on GitHub, past quarter (-36% change) 276 issues
closed on GitHub, past quarter (-12% change)
We still have issues and PRs coming in faster than we can close them out, but
we have daily PR syncs and weekly repo maintenance syncs with a variety of
contributors participating, and seem to be keeping all urgent items at bay.
General site/repo traffic remains steady. Efforts are being made by
contributors to speak at various conferences, and try to raise awareness of
this project in the BI/data space in general.
-----------------------------------------
Attachment BW: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
The mission of Syncope is the creation and maintenance of software related to
Managing digital identities in enterprise environments
## Project Status:
Current project status: healthy.
Issues for the board: none.
## Membership Data:
Apache Syncope was founded 2012-11-21 (12 years ago)
There are currently 25 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Lorenzo Di Cola on 2023-05-22.
- No new committers. Last addition was Samuel Garofalo on 2022-07-29.
## Project Activity:
At the end of last year we have cut the maintenance release 3.0.10 and the
very first milestone of next stable release 4.0.0.
Since then, we are continuing with regular maintenance, which should bring
3.0.11 soon. Moreover, the work towards the final 4.0.0 is continuing with
rebase on the latest version of supporting frameworks and dependencies.
Recent releases:
* 4.0.0-M0 was released on 2024-12-24
* 3.0.10 was released on 2024-12-24
* 3.0.9 was released on 2024-10-21.
## Community Health:
We continue to observe a slight raise of questions and support requests from
newcomers.
Discussions about new features and improvements keep appearing and being
followed up in dev@.
-----------------------------------------
Attachment BX: Report from the Apache SystemDS Project [Matthias Boehm]
## Description:
Apache SystemDS is a machine learning (ML) system for the end-to-end
data science lifecycle from data preparation and cleaning, over
efficient ML model training, to scoring and debugging. ML algorithms
or pipelines are specified in a high-level language with R-like syntax,
or related Python and Java APIs, and the system automatically generates
hybrid runtime plans of local, in-memory operations and distributed
operations on Apache Spark.
## Issues for the Board:
- None
## Project Status:
- Current work focuses on adding the missing primitives for
a number benchmarks such as TPCx-AI and MLPerf on SystemDS, new APIs
for the alignment of multimodal datasets, an exploration of Java's
new vector and foreign memory API, and incremental refinements
of major internal components for compression, reuse, as well as
multiple GPU devices, and distributed and federated operations.
- We are in the process of preparing the release of SystemDS 3.3
(last release on JDK 11, afterwards switch to JDK 17)
## Membership Data:
- Apache SystemDS was founded 2017-05-16 (incubator process entered
2015-11-02)
- Last PMC members added 2024-03-28 (Olga Ovcharenko)
- Last committer added 2024-09-09 (Elias Strauss)
- There are currently 36 committers and 27 PMC members in the project.
## Activity and Health:
- Code activity is healthy with 141 commits (+7%) in the last 3 months.
- Community growth is healthy with 19 active contributors (+-36%)
in the last 3 months
- Communication is healthy, mailing list activity is improving,
additional work on better documentation.
## Releases:
- Apache SystemDS 3.2.0 was released on 2024-03-17.
- Apache SystemDS 3.1.0 was released on 2023-03-13.
- Apache SystemDS 3.0.0 was released on 2022-06-20.
- Apache SystemDS 2.2.2 was released on 2022-06-25.
- Apache SystemDS 2.2.1 was released on 2021-12-02.
- Apache SystemDS 2.2.0 was released on 2021-10-30.
- Apache SystemDS 2.1.0 was released on 2021-06-28.
- Apache SystemDS 2.0.0 was released on 2020-10-14.
- Apache SystemML 1.2.0 was released on 2018-08-24.
-----------------------------------------
Attachment BY: 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:
Merged lots of patches for a possible release 0.10.5, also discussed moving to
1.x release line.
## Community Health:
With the new PMC Auysh Saxena, we kept reviewing incoming patches, also
reviewed a lot of long-pending (but valuable) PRs, so we're hoping the
community's health is going in a better direction.
-----------------------------------------
Attachment BZ: Report from the Apache TomEE Project [David Blevins]
-----------------------------------------
Attachment CA: Report from the Apache Traffic Control Project [Eric Friedrich]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning a large
scale content delivery network (CDN)
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (7 years ago)
There are currently 31 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hamrick on 2023-02-07.
- No new committers. Last addition was Abdulrahman Elawady on 2023-09-21.
## Project Activity:
Minimal Activity since the last release 8.0.2 release on Oct 2, 2024
## Community Health:
Discussion on both mailing lists and Slack channel is minimal. There are
still several PMC members active and ready to engage on security fixes
or releases if needed.
-----------------------------------------
Attachment CB: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
The mission of Traffic Server is the creation and maintenance of software
related to a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant
caching proxy server.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Traffic Server was founded 2010-04-20 (15 years ago)
There are currently 71 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Mo Chen on 2024-04-15.
- No new committers. Last addition was Josiah VanderZee on 2024-01-07.
## Project Activity:
We released 4 bug fix and security releases in the last quarter. Two major
companies are testing the next major release of ATS (ATS 10.x) in production
and will be rolling it out to more production servers in Q1 of 2025. We are
also getting ready for our next minor version (10.1.0) of ATS.
## Community Health:
We held our ATS Fall Summit in Denver, CO. We focused mainly on the
development of ATS and put together a release schedule with features and
enhancements for the next year. There were about 20 people in attendance and
we also had remote participation.
We continue to hold our weekly bug and issue scrubs every Monday, where
committers are assigned to review PRs and address issues submitted by the user
community.
-----------------------------------------
Attachment CC: Report from the Apache TsFile Project [Jialin Qiao]
## Description:
Apache TsFile is a columnar storage file format designed specifically for time
series data, with a focus on efficient storage, high throughput for read and
write operations, and compatibility with various data processing frameworks.
TsFile is intended to integrate seamlessly with existing time series
databases, such as IoTDB, and data processing frameworks like Apache Spark and
Apache Flink, facilitating the adoption of TsFile in IoT big data processing
ecosystems.TsFile aims to become a widely adopted standard for time series
data storage.
## Project Status:
Current project status: Ongoing with high activity
Issues for the board: no
## Membership Data:
Apache TsFile was founded 2023-11-15 (a year ago)
There are currently 19 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Gaofei Cao on 2023-11-15.
- hongzhigao was added as committer on 2025-01-11
## Project Activity:
- 2.0.1 was released on 2025-02-10
- 2.0.0 was released on 2025-01-17
- 1.1.0 was released on 2024-11-10
### Main work of project:
- TsFile V4 format with Table Model was released
- The new read and write interfaces for TsFile V4 which is aiming to make the
interfaces in different programming languages more stylistically consistent
in use are finished. Java SDK was firstly released, other languages(like
C/C++, Python) are on the way.
- Support dictionary encoding for STRING data type
## Community Health:
The mail list is active. We discussed the release and version of TsFile.
Besides, the doc management is also discussed and updated.
dev@tsfile.apache.org had a 15% increase in traffic in the past quarter (67
emails compared to 58)
-----------------------------------------
Attachment CD: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related to A
Java Servlet Web Application Framework and associated component library
## Project Status:
Current project status: Ongoing with low activity and at least 3 active PMC
members.
Issues for the board: None
## Membership Data:
Apache Turbine was founded 2007-05-16 (18 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers. Last addition was Youngho on 2021-12-06.
## Project Activity:
Released Components this quarter:
- Fulcrum Intake 4.0.0 was released on 2025-01-03.
- Fulcrum Localization 2.0.0 was released on 2025-01-03.
- Fulcrum Security 4.0.0 was released on 2025-01-03.
- Fulcrum Upload 2.0.0 was released on 2025-01-03.
- Turbine Fulcrum Parser 4.0.0 was released on 2024-12-09.
We approach hopefully next quarter stage 5 (that is Turbine core) in what is
our major release:
https://lists.apache.org/thread/55vgl4823mbxlzmvjo8ys283t42jw2xm)
## Community Health:
Turbine version 7.0 release continues to be in preparation, and the main
Turbine core is next, after finalizing two more RC votings.
Activity in contributions continue on a low level.
-----------------------------------------
Attachment CE: Report from the Apache Velocity Project [Nathan Bubna]
-----------------------------------------
Attachment CF: Report from the Apache Web Services Project [Daniel Kulp]
## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.
## Project Status:
Current project status: ongoing, low activity
Issues for the board: none
## Membership Data:
Apache Web Services was founded 2003-01-22 (22 years ago)
There are currently 223 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Robert Lazarski on 2021-06-14.
- No new committers. Last addition was Alessio Soldano on 2014-09-14.
## Project Activity:
WebServices is a mature project based on standards that are also quite mature.
As such, there is not a significant amount of activity required. However, user
questions are being answered promptly, bugs are being fixed, and there are at
least 3 independent PMC members around making sure the project can continue to
produce releases as needed. Since SOAP/XML based Web Services is no longer
considered state of the art, we don't expect a major uptick in new development
efforts, new committers, etc...
The efforts this period centered on two subprojects:
Axiom - Axiom 2.0.0 was released on 2025-02-06. This has been a long time
coming, but it's an important release as it moves the api over to using the
Jakarta packages while also fixing some bugs.
WSS4j 4.0.0 - work here is centered around upgrading some dependencies to
latest versions as well as updating the minimal JDK requirement to Java17.
It also contains a few new encryption/signing options/algorithms that
were requested by users. This release is being voted on now and will
likely be released by the time the board meeting happens.
Latest Releases:
Axiom-2.0.0 was released on 2025-02-06
WSS4J 3.0.4 was released on 2024-11-14
Neethi-3.2.1 was released on 2024-10-30
XmlSchema-2.3.1 was released on 2023-09-07
Woden-1.0M10: 2015-09
## Community Health:
As mentioned, SOAP/WebServices is not considered state-of-the-art anymore and
we are getting very little contribution from anyone other than the 2 or 3
regulars" that are driving features and changes needed for CXF (which is
being driven by their employers). Thus, we are not seeing any possibilities
for future new committers or PMC members. However, there are plenty of
people around that can do releases and answer questions and respond to
security issues. It's a mature project.
-----------------------------------------
Attachment CG: Report from the Apache Whimsy Project [Shane Curcuru]
-----------------------------------------
Attachment CH: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components in order to engender such improvements.
## Project Status:
Current project status: Ongoing with low activity.
Issues for the board: None.
## Membership Data:
Apache Xalan was founded 2004-09-30 (20 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. Last addition was Joseph Kessselman on 2023-08-07.
- No new committers. Last addition was Joseph Kessselman on 2023-06-29.
## Project Activity:
Despite our best intentions, we've not had a release of any components this
reporting period. We are working toward the adding XSLT 3 functionality to
Xalan-J. We plan on completing porting the build from Ant to Maven, fixing
bugs, and releasing a new version.
## Community Health:
Email traffic has decreased on the development list by half. There has been no
activity on the user list. Overall the project has very low activity but we do
intend to create a maintenance release for Xalan-J 2.x and a feature release
for XSLT 3.
-----------------------------------------
Attachment CI: Report from the Apache Xerces Project [Michael Glavassevich]
Apache Xerces is a collaborative software development project dedicated to
providing robust, full-featured, commercial-quality, and freely available XML
parsers and closely related technologies on a wide variety of platforms
supporting several languages.
========
Xerces-J
Work has been underway to modernize the Xerces-J build so that it will work
with more recent versions of Java. A couple new contributors have been helping
with this effort and one of them is currently being considered to become a new
committer and PMC member.
Mailing list traffic has been low; roughly 35+ posts on the j-dev and j-users
lists since the beginning of November 2024.
No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022).
========
Xerces-C
Most of the activity was in conversations on JIRA issues. One community member
opened a PR in GitHub that has not been reviewed yet.
The Apache security team has been following up on an old issue from 2012. The
PMC has been responding and was still discussing this issue as of last week.
Mailing list traffic has been low; roughly 45+ posts on the c-dev and c-users
lists since the beginning of November 2024.
The latest release is Xerces-C 3.2.5 (December 20th, 2023).
========
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
========
XML Commons
A copy of the XML Commons source was brought into GitHub under a branch in the
Xerces-J project. There was no other development activity over the reporting
period.
========
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and September
2023 (Xerces-J).
The most recent addition to the PMC was in September 2023.
Three committers have committed changes to GitHub since November 2024.
-----------------------------------------
Attachment CJ: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report
==================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
Issues for the Board
=====================
We have migrated the Apache XML Graphics repositories for XML Graphics
Commons, FOP, FOP PDF Images and Batik to GitHub:
https://github.com/apache/xmlgraphics-fop.git
Activity
========
* All XMLGraphics project repositories have been migrated from Subversion to
GitHub/GitBox: https://github.com/apache/xmlgraphics-fop.git
* A proposal to migrate XMLGraphics projects from Jira to GitHub issues was
passed. Preliminary work to effect this migration has started. The migration
is ongoing.
Latest Versions of Apache XML Graphics Project Projects:
* Apache Batik 1.18 2024-10-09
* Apache FOP 2.10 released 2024-10-09
* Apache FOP PDF Images 2.10 released 2024-10-09
* Apache XML Graphics Commons 2.10 released 2024-10-09
Project Health Report
=======================
The level of community and developer activity remains at a consistent,
moderate, level with respect to the previous reporting period.
Recent PMC Changes
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds was approved for XML Graphics PMC Chair position on March 26,
2018.
Committers
==========
Currently 21 committers.
* 1 new committer added in the last 3 months
* Last committer added was Joao Goncalves at in October 2024
Most Recent Releases
====================
* Apache Batik 1.18 2024-10-09
* Apache FOP 2.10 released 2024-10-09
* Apache FOP PDF Images 2.10 released 2024-10-09
* Apache XML Graphics Commons 2.10 released 2024-10-09
= SUB PROJECTS =
================
APACHE BATIK
=====
Batik is a Java-based toolkit for applications or applets that want to use
images in the Scalable Vector Graphics (SVG) format for various purposes, such
as display, generation or manipulation.
Latest Release
------------
Apache XML Graphics Apache Batik 1.18 was released on October 9, 2024
* Bug fixes
APACHE FOP
===
Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL
formatting objects (XSL-FO) and an output independent formatter. It is a Java
application that reads a formatting object (FO) tree and renders the resulting
pages to a specified output. Output formats currently supported include PDF,
PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a
lesser extent, RTF and TXT. The primary output target is PDF.
Latest Release
--------------
Apache XML Graphics Apache FOP 2.10 was released on October 9, 2024 Apache XML
Graphics Apache FOP PDF Images 2.10 was released on October 9, 2024
* Bug fixes
XML GRAPHICS COMMONS
====================
Apache XML Graphics Commons is a library that consists of several reusable
components used by Apache Batik and Apache FOP. Many of these components can
easily be used separately outside the domains of SVG and XSL-FO. You will find
components such as a PDF library, an RTF library, Graphics2D implementations
that let you generate PDF & PostScript files, and much more.
Latest Release
------------
Apache XML Graphics Commons 2.10 was released on October 9, 2024
* Bug fixes
-----------------------------------------
Attachment CK: Report from the Apache YuniKorn Project [Wilfred Spiegelenburg]
## Description:
The mission of Apache YuniKorn is the creation and maintenance of software
related to a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds
## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: none
## Membership Data:
Apache YuniKorn was founded 2022-03-16 (3 years ago)
There are currently 37 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Chia-Ping Tsai on 2024-03-07.
- No new committers. Last addition was Kuan Po Tseng on 2024-03-15.
## Project Activity:
Recent releases:
1.6.1 was released on 2025-01-24.
1.6.0 was released on 2024-09-17.
1.5.2 was released on 2024-07-29.
The instability issue detected in release 1.6.0 was tracked back after a lot
of community testing. 1.6.1 was released with the stability fix and other
critical bug fixes.
A 1.6.2 release is considered solely for updated Kubernetes release support.
Scale testing is still an issue. The first changes to add scale testing are in
progress. Delivery is still planned for 1.7.0.
## Community Health:
9 new Jira accounts were requested. 63 new Jiras created and 56 resolved,
with corresponding GitHub PRs: 57 created and 56 resolved.
Christmas and Chinese new year have impacted the activity in the community more
than in previous years. Expecting activity to pick up again in the next period.
------------------------------------------------------
End of minutes for the February 19, 2025 board meeting.
Index