The Apache Software Foundation

                  Board of Directors Meeting Minutes

                            March 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-03-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
      Zili Chen
      Shane Curcuru
      Jim Jagielski
      Justin Mclean
      Jean-Baptiste Onofré
      Greg Stein
      Sander Striker
      Kanchana Pradeepika Welagedara - joined :05

    Directors Absent:

      none

    Executive Officers Present:

      Craig R. McClanahan
      David Nalley
      Craig L Russell
      Matt Sicker
      Ruth Suehle

    Executive Officers Absent:

      none

    Guests:

      Alin Jerpelea
      Andrew Musselman
      Andrew Wetmore
      Brian Proffitt
      Christopher Schultz
      Daniel Augusto Veronezi Salvador
      Daniel Gruno
      Dave Fisher
      Dirk-Willem van Gulik
      Drew Foulks
      Gavin McDonald
      Jarek Potiuk
      Jeff Genender
      Julien Le Dem
      Melissa Logan
      Niall Pemberton
      Paul King
      Pavan Kumar
      Philipp Ottlinger
      Sally Khudairi
      Whitney P True

3. Minutes from previous meetings

    Published minutes can be found at:

        https://www.apache.org/foundation/board/calendar.html

    A. The meeting of February 19, 2025

       See: board_minutes_2025_02_19.txt

       Approved by General Consent.

4. Executive Officer Reports

    A. Board Chair [Shane Curcuru]

       The ASF's Annual Member Meeting ran very smoothly thanks to continuing
       volunteer work on process improvements.  We are lucky to have elected
       a number of new Members, as well as welcoming back a prior Emeritus
       Member.

       The Membership elects a new 9-member board each year, and had a record
       field of 20 nominated candidates for the electino this year.  The ASF
       welcomes back Greg Stein and Jim Jagielski to the board as returning
       directors, and a special welcome to Zili Chen (@tison) as a first-time
       director.  Many thanks for the service of our departing directors:
       Willem Ning Jiang, Jeff Jirsa, and Craig Russell!

       The past year on the board has been a productive one, with a variety
       of proposals refined at our F2F board strategy meeting continuing to
       bring improvements.  And many volunteer officers have done amazing
       work on the new ASF Initiatives sponsorship program, welcoming
       specific financial support for significant ASF needs.

       The first ASF Initiative to launch is the ASF Tooling Initiative,
       created to meet the growing global demand for ASF software by
       hardening ubiquitous Apache projects that benefit the greater open
       source ecosystem.  This support enables our VP, Tooling and operations
       officers to hire and build a team of developers to build critical
       tools that will help all ASF projects meet new legislative challenges
       and improve secure delivery of Apache software across the board.

    B. President [Ruth Suehle]

       The most exciting news this month is that our Alpha Omega grant to
       support the tooling initiative is officially approved and signed. I
       greatly appreciate everyone who has worked on this over the last few
       months. The tooling work is going to be very important to the
       foundation in the coming years, and this grant is going to make it
       much easier for us to make that happen.

       After a lengthy time of low activity, I'm pleased to appoint Daniel
       Gruno to the role of VP, Diversity and Inclusion. He has been working
       with Christian Grobmeier (and more recently, Melissa Logan has joined)
       on plans to revive the work.

       The operations folks have been further refining workflow, which is
       really exciting. For a few years, the call was rarely attended, and
       interaction among those officers on a regular basis was minimal. But
       now we've got a well-attended cadence of operations calls one week
       before each month's board meeting, now with a rolling agenda stored in
       Confluence, and more conversations happening on list and in Slack. The
       current most obvious outcome is the proposed budget also in this
       month's agenda for the board's review.

       Additionally, please see Attachments 1 through 11.


    C. Treasurer [Craig R. McClanahan]

       Normal operations continue, with a few notable things:

       * I am being shadowed by an ASF Member (Lewis McGibbney) to learn how
         Treasury things work.  As part of that process, I have granted him
         read-only access to the three primary services we use (bill.com,
         quickbooks online, and ramp.com) so that he can learn what's
         available.  We're also working on documenting tasks and roles for
         people within Apache that interact with Treasury should be aware of.

       * I recently met with TD Wealth - the group that manages investments
         for our Operating Reserve.  I agreed with their assessment that we
         should stay the course with our current investment strategy
         (investment grade corporate bonds).  We should expect continued slow
         but fairly steady returns, in spite of potential uncertainties.

       * They also suggested that we update the Investment Policy document
         that the Board approved in 2022, that outlined the strategy we
         (Treasury) should follow, and have been following.  Even if we don't
         want to change anything, just updating the date based on Board
         affirmation would be a good idea.

       * Separately, we had also (in 2022) set up the machinery for an
         "endowment" or whatever else we wanted to do with the $500k
         contribution that has been marked as "Conditional Gift" on our
         Balance Sheet.  We haven't funded anything there, because there has
         not been any Board action on it.

       This month's meeting already has a full agenda, so I'll be proposing
       the latter two topics for a future Board meeting.

    D. Secretary [Matt Sicker]

       In February 2025, the secretary received 66 ICLAs, 2 CCLAs, 3 software
       grants, 3 CoI affirmations, and 1 membership emeritus request.

       The secretary worked with the chair to hold our yearly members
       meeting. We also made some corrections to our records regarding
       involuntary membership emeritus statuses.

    E. Executive Vice President [David Nalley]

       Not much to report this month.

       I attended the members meeting, where I tried to field questions for
       the office of the president. Also worked on a personnel matter with
       other members of operations.

    F. Vice Chair [Justin Mclean]

       Another uneventful month as far as vice chair duties go.

    Executive officer reports approved as submitted by General Consent.

5. Additional Officer Reports

    A. VP of W3C Relations [Andy Seaborne / Kanchana]

       See Attachment 12

    B. Apache Legal Affairs Committee [Roman Shaposhnik / Sander]

       See Attachment 13

    C. Apache Security Team Project [Mark J. Cox / Zili]

       See Attachment 14

    Additional officer reports approved as submitted by General Consent.

6. Committee Reports

    Summary of Reports

     The following reports required further discussion:

        # Airflow [jim]
        # Daffodil [jim]
        # DeltaSpike [Kanchana]
        # Druid [rbowen]
        # Incubator [jim]
        # IoTDB [jim]
        # Kibble [jim]
        # Linkis [Kanchana]
        # Olingo [rbowen]
        # Portals [jim, striker]
        # Pulsar [jim, tison]
        # TomEE [Kanchana]
        # UIMA [jim]

    A. Apache Airflow Project [Bolke de Bruin / Justin]

       See Attachment A

       @Jim: respond to Airflow's board question

    B. Apache Allura Project [David Philip Brondsema / JB]

       See Attachment B

    C. Apache Answer Project [Ning Qi / Greg]

       See Attachment C

    D. Apache Atlas Project [Madhan Neethiraj / Jim]

       See Attachment D

    E. Apache Axis Project [Robert Lazarski / Rich]

       See Attachment E

    F. Apache Beam Project [Kenneth Knowles / Shane]

       See Attachment F

    G. Apache Bigtop Project [Masatake Iwasaki / Sander]

       See Attachment G

    H. Apache BVal Project [Matthew Jason Benson / Jim]

       See Attachment H

    I. Apache Camel Project [Andrea Cosentino / Greg]

       See Attachment I

    J. Apache Cayenne Project [Michael Ray Gentry / JB]

       See Attachment J

    K. Apache Celeborn Project [Keyong Zhou / Shane]

       See Attachment K

    L. Apache CloudStack Project [Daniel Augusto Veronezi Salvador / Justin]

       See Attachment L

    M. Apache Commons Project [Gary D. Gregory / Rich]

       See Attachment M

    N. Apache Cordova Project [Bryan Ellis / Kanchana]

       See Attachment N

    O. Apache cTAKES Project [Pei Chen / Zili]

       See Attachment O

    P. Apache Curator Project [Enrico Olivelli / Shane]

       See Attachment P

    Q. Apache Daffodil Project [Mike Beckerle / Rich]

       See Attachment Q

       @Rich: reach out to PMC about advice around contributors

    R. Apache DataFusion Project [Andrew Lamb / JB]

       See Attachment R

    S. Apache DeltaSpike Project [Mark Struberg / Kanchana]

       No report was submitted.

       @Kanchana: pursue an Attic proposal for DeltaSpike

    T. Apache Druid Project [Gian Merlino / Rich]

       See Attachment T

    U. Apache ECharts Project [Wenli Zhang / Sander]

       See Attachment U

    V. Apache Felix Project [Karl Pauls / Jim]

       See Attachment V

    W. Apache Flex Project [Harbs / Zili]

       See Attachment W

    X. Apache Flink Project [Robert Metzger / Greg]

       See Attachment X

    Y. Apache Gobblin Project [Abhishek Tiwari / Justin]

       See Attachment Y

    Z. Apache Guacamole Project [Mike Jumper / Kanchana]

       See Attachment Z

    AA. Apache Gump Project [Stefan Bodewig / Justin]

       See Attachment AA

    AB. Apache Helix Project [Junkai Xue / Greg]

       See Attachment AB

    AC. Apache Hive Project [Naveen Gangam / Jim]

       See Attachment AC

    AD. Apache Hop Project [Hans Van Akelyen / Zili]

       See Attachment AD

    AE. Apache Hudi Project [Vinoth Chandar / JB]

       See Attachment AE

    AF. Apache Iceberg Project [Ryan Blue / Sander]

       See Attachment AF

    AG. Apache Incubator Project [Justin Mclean / Rich]

       See Attachment AG

    AH. Apache IoTDB Project [Xiangdong Huang / Rich]

       See Attachment AH

    AI. Apache Jackrabbit Project [Marcel Reutegger / Shane]

       See Attachment AI

    AJ. Apache Karaf Project [Jean-Baptiste Onofré]

       See Attachment AJ

    AK. Apache Kibble Project [Sharan Foga / Greg]

       See Attachment AK

    AL. Apache Kvrocks Project [Mingyang Liu / Sander]

       See Attachment AL

    AM. Apache Kyuubi Project [Kent Yao / Jim]

       See Attachment AM

    AN. Apache Libcloud Project [Tomaž Muraus / Rich]

       See Attachment AN

    AO. Apache Linkis Project [Shuai Di / Kanchana]

       See Attachment AO

    AP. Apache Logo Development Project [Daniel Gruno / Zili]

       See Attachment AP

    AQ. Apache Lucene Project [Dawid Weiss / JB]

       See Attachment AQ

    AR. Apache Lucene.Net Project [Shad Storhaug / Justin]

       See Attachment AR

    AS. Apache Mynewt Project [Szymon Janc / Shane]

       See Attachment AS

    AT. Apache NetBeans Project [Geertjan Wielenga / Greg]

       See Attachment AT

    AU. Apache OFBiz Project [Jacopo Cappellato / JB]

       See Attachment AU

    AV. Apache Olingo Project [Michael Bolz / Jim]

       See Attachment AV

       @Jim: pursue a roll call for Olingo PMC

    AW. Apache OpenDAL Project [Hao Ding / Shane]

       See Attachment AW

    AX. Apache OpenNLP Project [Jeff Zemerick / Zili]

       See Attachment AX

    AY. Apache OpenWebBeans Project [Mark Struberg / Rich]

       No report was submitted.

    AZ. Apache Paimon Project [Jingsong Lee / Justin]

       See Attachment AZ

    BA. Apache Pekko Project [PJ Fanning / Sander]

       See Attachment BA

    BB. Apache Pig Project [Koji Noguchi / Kanchana]

       No report was submitted.

       @Sander: follow up with Pig PMC about reporting duties

    BC. Apache Pinot Project [Kishore G / JB]

       No report was submitted.

       @Jean-Baptiste: pursue a roll call vote for Pinot

    BD. Apache PLC4X Project [César García / Rich]

       See Attachment BD

    BE. Apache Portable Runtime (APR) Project [Yann Ylavic / Justin]

       No report was submitted.

    BF. Apache Portals Project [Neil Griffin / Zili]

       See Attachment BF

       @Zili: pursue a roll call for Portals

    BG. Apache Pulsar Project [Matteo Merli / Shane]

       See Attachment BG

    BH. Apache Royale Project [Yishay Weiss / Kanchana]

       See Attachment BH

    BI. Apache Samza Project [Jagadish Venkatraman / Greg]

       See Attachment BI

    BJ. Apache SeaTunnel Project [Jun Gao / Jim]

       See Attachment BJ

    BK. Apache ServiceMix Project [Krzysztof Sobkowiak / Sander]

       See Attachment BK

    BL. Apache Shiro Project [Brian Demers / Greg]

       See Attachment BL

    BM. Apache SINGA Project [Wang Wei / Sander]

       See Attachment BM

    BN. Apache Sling Project [Robert Munteanu / Justin]

       See Attachment BN

    BO. Apache SpamAssassin Project [Sidney Markowitz / Shane]

       See Attachment BO

    BP. Apache Storm Project [Richard Zowalla / Kanchana]

       See Attachment BP

    BQ. Apache StreamPark Project [Huajie Wang / Jim]

       See Attachment BQ

    BR. Apache Superset Project [Maxime Beauchemin / JB]

       See Attachment BR

    BS. Apache Synapse Project [Isuru Udana / Rich]

       No report was submitted.

    BT. Apache Tomcat Project [Mladen Turk / Zili]

       See Attachment BT

    BU. Apache TomEE Project [David Blevins / Kanchana]

       No report was submitted.

       @Kanchana: pursue a report for TomEE

    BV. Apache TVM Project [Tianqi Chen / Greg]

       See Attachment BV

    BW. Apache UIMA Project [Richard Eckart de Castilho / Shane]

       See Attachment BW

       @Shane: respond to question from UIMA about reporting tool

    BX. Apache Uniffle Project [He Qi / Jim]

       See Attachment BX

    BY. Apache Unomi Project [Serge Huber / Zili]

       See Attachment BY

    BZ. Apache VCL Project [Josh Thompson / JB]

       See Attachment BZ

    CA. Apache Velocity Project [Nathan Bubna / Rich]

       See Attachment CA

    CB. Apache Whimsy Project [Shane Curcuru]

       See Attachment CB

    CC. Apache Wicket Project [Andrea Del Bene / Justin]

       See Attachment CC

    CD. Apache Yetus Project [Allen Wittenauer / Sander]

       See Attachment CD

    CE. Apache ZooKeeper Project [Flavio Paiva Junqueira / Kanchana]

       See Attachment CE

    Committee reports approved as submitted by General Consent.

7. Special Orders

    A. Change the Apache SpamAssassin Project Chair

       WHEREAS, the Board of Directors heretofore appointed Sidney Markowitz
       (sidney) to the office of Vice President, Apache SpamAssassin, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Sidney Markowitz from the office of Vice President, Apache
       SpamAssassin, and

       WHEREAS, the Project Management Committee of the Apache SpamAssassin
       project has chosen by vote to recommend Giovanni Bechis (gbechis) as
       the successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Sidney Markowitz is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache SpamAssassin, and

       BE IT FURTHER RESOLVED, that Giovanni Bechis be and hereby is appointed
       to the office of Vice President, Apache SpamAssassin, to serve in
       accordance with and subject to the direction of the Board of Directors
       and the Bylaws of the Foundation until death, resignation, retirement,
       removal or disqualification, or until a successor is appointed.

       Special Order 7A, Change the Apache SpamAssassin Project
       Chair, was approved by Unanimous Vote of the directors
       present.

    B. Change the Apache CloudStack Project Chair

       WHEREAS, the Board of Directors heretofore appointed Daniel Augusto
       Veronezi Salvador (gutoveronezi) to the office of Vice President,
       Apache CloudStack, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Daniel Augusto Veronezi Salvador from the office of Vice President,
       Apache CloudStack, and

       WHEREAS, the Project Management Committee of the Apache CloudStack
       project has chosen by vote to recommend Nicolás Vázquez (nvazquez) as
       the successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Daniel Augusto Veronezi Salvador
       is relieved and discharged from the duties and responsibilities of the
       office of Vice President, Apache CloudStack, and

       BE IT FURTHER RESOLVED, that Nicolás Vázquez be and hereby is appointed
       to the office of Vice President, Apache CloudStack, 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 CloudStack Project Chair,
       was approved by Unanimous Vote of the directors present.

    C. Terminate the Apache Gora Project

       WHEREAS, the Project Management Committee of the Apache Gora project
       has chosen by vote to recommend moving the project to the Attic; and

       WHEREAS, the Board of Directors deems it no longer in the best interest
       of the Foundation to continue the Apache Gora project due to
       inactivity;

       NOW, THEREFORE, BE IT RESOLVED, that the Apache Gora 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 Gora Project; and be it
       further

       RESOLVED, that the office of "Vice President, Apache Gora" is hereby
       terminated; and be it further

       RESOLVED, that the Apache Gora PMC is hereby terminated.

       Special Order 7C, Terminate the Apache Gora Project, was
       approved by Unanimous Vote of the directors present.

8. Discussion Items

    A. Appoint Board Chair And Vice Chair

       Directors and the Secretary will hold an Executive Session at the
       START of the meeting to review and consider changes to Board 
       Chair/Vice Chair appointments.  No other business will be conducted
       during this executive session.

       The board appoints Sander Striker as the Chair and Rich Bowen as the
       Vice Chair both by consensus.

    B. Budget

       Draft FY2026 Budget

       Income
        Total Public Donations                                $100,000
        Total Sponsorship                                   $2,500,000
        Conference                                            $100,000

        Total Income                                        $2,705,000

        Expense
        General & Administrative                              $100,000
        Brand Management                                       $80,000
        ComDev                                                      $0[1]
        Conferences                                           $100,000[2]
        Fundraising                                           $118,300
        Infrastructure                                        $127,900[3]
        Privacy                                                 $5,000
        Programs                                                $1,200
        Public Affairs                                         $40,000
        Publicity                                             $242,500
        Staffing                                            $1,609,547[4]
        Tooling                                                $15,500
        Travel Assistance                                      $55,000
        Treasury                                               $26,280
        Security                                                $6,000
        Legal Affairs                                          $25,000

        Total Expense                                       $2,562,227

        Net                                                   $152,773

       [1] ComDev had a $0 budget last year on the assumption that most of the
        conferences swag would be new logo items produced by that budget, and thus
        the usual swag budget was moved to Conferences and M&P for promoting the new
        logo. It is assumed that will now happen in this FY and thus the same budget
        choice.
       [2] We have for many years set the Conferences budget at 100k. With the
        exception of last year, which took a small loss, we have generally at least
        broken even or had a bit of a surplus on the Conferences budget since we
        started producing it ourselves in 2018 (with the exception of the Vegas
        year). This year many countries and people outside the US are declining to
        travel to the US, and this may have a significant impact on our ability to
        meet minimums on contracts signed before that started happening. I suspect
        this is the riskiest budget line this year.
       [3] Salaries that have been included here in the past have been moved to a
        Staffing line that also includes the Tooling staffing.
       [4] All staffing now included in this new budget line. The increase for
        Tooling will be covered by the Alpha Omega grant.



    C. Regular Meeting Schedule

       Determine the best time for future board meetings this year.

       Proposal:
       - 21:00 UTC  April - October
       - 22:00 UTC  November - March

       The board has decided to use the updated schedule by consent.

    D. Officer Positions

       Discuss officer positions.

       The board discussed current executive officer positions. No actions
       were taken at this time.

9. Review Outstanding Action Items

    * Shane: update Incubation guidelines to include trademark grant
          [ Trademark management status briefing VP, Brand Management 2024-07-17 ]
          Status:

    * Craig McClanahan: pursue an audit on ramp cards
          [ Review expense accounting categories 2024-10-16 ]
          Status:

    * Rich: pursue a roll call for Druid
          [ Druid 2025-02-19 ]
          Status: Done: It looks like this was just an "I forgot" rather than
                  that there's any problem. Also the PMC discussed sharing the
                  report writing responsibility more broadly, so that this
                  doesn't happen again.
                  https://lists.apache.org/thread/ypz8mqg22w3sr2z9x4hzt2o0rmol1zkf

    * Shane: follow up with PMC about PMC merge with Accumulo
          [ Fluo 2025-02-19 ]
          Status: In progress on private@ fluo, accumulo. First step is energy
                  to technically migrate any code desired; later will be
                  Attic'ing Fluo.

    * Rich: follow up on list and clarify governance question
          [ Geode 2025-02-19 ]
          Status: Done: Discussed with Security and it appears that they are, in
                  fact, now having all discussions on a list where everyone is
                  present.

    * Rich: follow up with Gora about potential move to Attic
          [ Gora 2025-02-19 ]
          Status: Reached out to PMC. Will update prior to next meeting.

    * Rich: follow up with IPMC
          [ Incubator 2025-02-19 ]
          Status: Discussion with IPMC members indicates that they have motion
                  on several of the older incubating projects, and others are
                  considering retiring. Will continue to check up over the
                  coming months.

    * Kanchana: pursue a roll call for Samza
          [ Tez 2025-02-19 ]
          Status: Initiated a roll call - waiting on the responses Responses
                  +1--> 2 0--> 4 -1--> 2

    * Kanchana: pursue a roll call for Xalan
          [ Xalan 2025-02-19 ]
          Status: Initiated a roll call - waiting on responses +1--> 3 Turing
                  from 0 -> +1 soon -- > 1

    * Justin: follow up with trademarks about RocketMQ
          [ RocketMQ 2025-02-19 ]
          Status: PMC is dealing with it. May need trademarks help.

    * Rich: start document for board year hand-off
          [ Review F2F outcomes and recommendations 2025-02-19 ]
          Status: Done. Created
                  https://svn.apache.org/repos/private/foundation/board/handoff
                  for this doc, and for future handoff docs.

10. Unfinished Business

11. New Business

12. Announcements

13. Adjournment

    Adjourned at 22:22 UTC

============
ATTACHMENTS:
============

-----------------------------------------
Attachment 1: Report from the VP of Brand Management  [Mark Thomas]

Covering the period February 2025

* ISSUES FOR THE BOARD

None.


* OPERATIONS

- Provided information to COUCHDB regarding contact details for some legacy
  domains
- Approved events related to: ICEBERG x1, FLINK x1
- Provided guidance to M&P regarding trademark usage in press announcements
- Approved name searches for: OTAVA
- Responded to a trademark query from VP, Sponsor Relations
- Provided advice to the PINOT PMC regarding a project based YouTube channel
- Connector an external merchandise vendor with VP Fundraising so they can
  donate a percentage of their profits for ASF project based merchandise.


* REGISTRATIONS

The FREEMARKER registration in the US is now complete.


* INFRINGEMENTS

Continued to try and get the full project name for Apache HBase used on a 3rd
party website.

No progress in the last month regarding the downstream vendor with multiple
infringements of ASF marks.

Issues related to AGEDB appear to have been resolved but both the PMC and the
trademarks team will continue to monitor the issue.

A potential infringement of PDFBOX has been identified. I have reached out to
the relevant hosting provider to try and resolve it.

A potential infringement of APISIX has been identified. I am working with the
PMC to resolve it.


-----------------------------------------
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 have secured renewal commitments from one Silver and one
Bronze Sponsor.

c —Payments: 1 —New: we received no new Sponsor payments during this
timeframe.

    2a —Renewing: we received a renewal payment from one Silver Sponsor.

    2b —Incoming: we await payment from three renewing Platinum, one renewing
    Gold, one renewing Silver, two renewing Bronze Sponsors, plus a planned
    corporate contribution.


2) Targeted Sponsors: we have finalized one Targeted Platinum renewal and are
pursuing a new point-of-contact for a lapsed Targeted Sponsorship.


3) Sponsor Relations: we have been meeting with some new Sponsor
points-of-contact and helping with their orientation to the ASF Way and
related processes. We are also working with a Platinum Sponsor on legal
clearance for their renewal agreement. Our next quarterly call with Gold and
Platinum Sponsors will take place mid-March.


4) Event Sponsorship: we will be liaising sponsorships for Community Over Code
North America 2025 once the prospectus is announced.


5) Individual Donations and Corporate Giving: we received $925 in online
donations via https://donate.apache.org/ . We received no corporate
contributions during this timeframe.


6) Administrivia: in addition to our standing work with the Accounting and
Treasury teams, we are working with Marketing & Publicity on the new Tooling
Initiative and fundraising campaign.


-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity  [Brian Proffitt]

Foundation Comms

* Issued February edition of the Plus One Newsletter
    * 102 total  subscribers
* Announced Community Over Code NA dates and location via blog post and social
  media promotions
* Announced Community Over Code NA CFP via social media
* Reviewed and revised ASF boilerplate messaging for use in press materials
  and social channels
* Revised ASF Initiatives landing page and sent to Fundraising for approval

Project Comms

* Reviewed and distributed press release announcing Apache Sling 13.0
* Wrote and distributed press release announcing Apache Ignite 3.0
* Reviewed press release for Apache Ignite Summit 2025
* Reviewed C/C Asia blog post

Foundation Content

* Wrote and published blog recapping FOSDEM 2025; syndicated blog to DZone

Social Media Overview

The highest performing piece of content was news of Apache Answer and Apache
StreamPark’s graduation to TLP. M&P migrated to Buffer (from SproutSocial) for
social publishing and analytics tool, to support the addition of Bluesky.

Social Highlights (X + LinkedIn + Bluesky)

* Total Audience: 142,233
    * New Followers in February: 499
        * X: 0^
        * Bluesky: 101
        * LinkedIn: 398
* Total Posts: 87
    * X: 40
    * Bluesky: 40
    * LinkedIn: 15
* Total Engagements: 3,305

^ Buffer’s analytics slightly differs from SproutSocial; Buffer does not
  report loss in followers just net gain. ASF’s X channel lost 38 followers in
  February

Website Analytics

* 860,646 visits, 860,587 unique visitors +2.7%
* 2 min 39s average visit duration -5.9%
* 46% visits have bounced (left the website after one page) -2.1%
* 7 actions (page views, downloads, outlinks, internal site searches) per
  visit +18.8%
* 10,003 max actions in one visit (level)
* 4,848,449 pageviews, 1,065,044 unique pageviews +15%
* 5 total searches on your website, 5 unique keywords +66.7%
* 380,570 downloads, 274,646 unique downloads +10.1%
* 733,298 outlinks, 225,224 unique outlinks +122.6%


-----------------------------------------
Attachment 4: Report from the VP of Infrastructure  [Myrle Krantz]

General
=======

Infrastructure continues to operate at reduced staffing. Hiring
efforts are underway, but have met with challenges related to our
sourcing provider. We are looking at other options to better reach
European applicants.

No issues require the board's attention at this time.

Finances
========

- Infra has received and implemented a targeted donation of $25k/yr in
  support of Cassandra build nodes.
- FY25 Infra budget identified and submitted (pending VP review).

Travel
======

- Infra Team F2F planned for late May.

Major 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, planned for 25
  March.
- An organization-wide CSP (Content-Security-Policy) has been fully
  rolled out, improving our overall privacy posture.
- Next iteration of our .asf.yaml control file for Git repositories is
  to be announced soon along with a rollout plan. It has been
  available for opt-in since late February, and has been under active
  testing by several projects.
- A self-service "abuse tool" is in the final stages of development.
  This will allow recipients of automatic network abuse blocks a
  self-service method to determine why their IP address was blocked,
  along with remediation steps, which will reduce overall Infra
  workload in dealing with IP blocks due to accidental network abuse.
- MFA policy, discussions, suggestions, and implementation strategies
  are being curated by Infra and Security with a goal of presenting a
  plan to the Board in April.
- Testing is underway for a possible Jira and Confluence cloud
  migration. See previous board reports for further detail about this
  effort.


-----------------------------------------
Attachment 5: Report from the VP of Tooling  [Dave Fisher]

# Tooling Team Report

Our two contractors Sean B Palmer (sbp) and Thomas Neidhart (tn) are on board.
The website is up on tooling.apache.org (source is
https://github.com/apache/tooling-docs/).

## Projects

Working documentation can be found on github here:
https://github.com/apache/tooling-docs/.

### Apache Trusted Release

We are working on the platform here:
https://github.com/apache/tooling-trusted-release/. We just renamed this from
our experimental area. We are beginning to contribute fixes back upstream to
Infrastructure for some of the required dependencies.

We plan to provide guidance to projects about how to achieve reproducible
builds and produce SBOMs in their specific build pipelines.

### Board Agenda Tool

We will ramp up work on the Board Agenda Tool during this month's board
meeting. The tooling team is now responsible for assuring that
agenda-test.apache.org is running starting from the board meeting. We will
need to work with the Secretary and Chair to make sure that every requirement
is captured.

### Other Projects

There was a discussion after the Member's Meeting about where Daniel Gruno's
asfmm code might land. One thought is that Tooling could become more of a
committee, and could incorporate projects that are supported by member and
staff volunteers. There would need to be thought put into governance if it is
decided to expand tooling's scope.


-----------------------------------------
Attachment 6: Report from the VP of Conferences  [Brian Proffitt]

CFP for Community Over Code NA was launched on March 10, and will remain open
until April 21. Tracks in the CFP include:

* AI Plumbers
* Cassandra
* Community
* Data (compute, engineering, and storage)
* Developer experience
* Fintech: Building Secure Solutions
* Geospatial
* Groovy
* Incubator
* Industrial Internet of Things
* Infrastructure
* OpenLakehouse
* Performance engineering
* Search
* Security
* Streaming
* Web servers/Tomcat

There will also be a new "Community Hobbyist" track that expands from the
success of prior years' lightning talks, enabling attendees to share interests
and passions with their fellow ASF committers and members. This track will
have separate selection process, from the pool of attendees.

The 2025 prospectus is nearly ready to go, and should be published the week of
March 17, alongside a proactive outreach campaign to past sponsors.

After-event evening venues are getting lined up and contracts signed. Finally,
we are exploring specific invitations for students of local universities to
attend at special day-pass rates.


-----------------------------------------
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 are open for Beijing, and applications will close around
the 9th May. We have around a dozen applications so far. Volunteers
stepped up to be judges for this event

Monthly Meetings
================

The next meeting will be held first week of April.

TAC App
=======

TAC app is open for applications for China currently. We expect that
NA applications will open within the next two weeks.

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 couple of weeks.

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
=====================

Budget submitted, Volunteer call and acceptance for judges for China.

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]

# General

There are no issues that need urgent attention.

## Privacy Committee

The _privacy committee_ are volunteers actively working for more privacy
towards the ASF. Committee members have become more active supporting projects
for a few weeks.

## Privacy complaints / Removal requests

We received 4 requests since the start of 2025.
Several others came in directly to vp-privacy.

## Matomo

The ASF started hosting its own Matomo instance in March 2022 to provide
analytics for project websites that respected user's privacy:

    https://analytics.apache.org/

Currently, 67 Matomo _Tracking Codes_ have been issued, 9 since the start of
2025. There are 9 Matomo sites that don't receive traffic at this point.

#### Responsibility for the Matomo VM

Infra will take over the responsibility for the Matomo VM.
The current progress is tracked here:
https://issues.apache.org/jira/browse/INFRA-26367

## New services

Project websites can embed Kapa.AI for an improved documentation experience.
While a DPA is on file, ASF projects need to turn on the "explicit consent"
option provided by Kapa.AI.

## Content Security Policy

The Infrastructure team implemented a _Content Security Policy_ (CSP) at the
start of March 2025 which prevents project websites from using trackers or
loading resources which are not permitted by the ASF Privacy Policy.

Quite a few projects have issues to fix due to external resources that are
now blocked by the CSP. There have been discussions around some external usage
and whether they could be permitted under the Privacy Policy (e.g. sign a DPA)
or provide a technical solution that would make usage compliant.

## Analytics Usage Campaign

The _Privacy Committee_ receives a monthly report of ASF websites that utilise
external trackers/analytics that are not permitted by the _Privacy Policy_.
From December 2023 to January 2025, the number of ASF websites using
proscribed analytics had reduced from 113 to 103 (-9%).

In January 2025 the _Privacy Committee_ started a campaign to encourage
projects to remove those analytics. Issue Tickets were created for 87
projects which included PRs/patches for 67.

Over the last two months, the number of websites using proscribed analytics
on the monthly report has reduced from 103 to 52 (-50%). Of the remaining
52 sites, 27 are retired projects in the Attic.

While the use of external trackers is no longer an issue since the CSP started
blocking them, we believe its a good idea to encourage projects to clean up
their sites and point out that Matomo can provide analytics for them.

# Open tasks

- Provide guidelines for advertising user mailing lists
- Create a list of WordPress sites
- Create a list of domains that are allowed to connect because a DPA is covering it (improved Whimsy support)
- Better documentation about DPAs
- Add "canned responses" and instructions on how to run the privacy office to
 the website
- Investigate TAC for data privacy and develop a targeted version for the committee
- Clarify responsibility for the Matomo VM
 https://lists.apache.org/thread/6c7dn3ot494pxdlfxfn1pngbcpzj5g08
 https://issues.apache.org/jira/browse/INFRA-25432
- Clarify status of "donate.apache.org"
- Clarify status of "status.apache.org"


-----------------------------------------
Attachment 10: Report from the VP of Public Affairs  [Dirk-Willem van Gulik]

CRA:

      First definitions are starting to appear & with formal feedback
      requested:

  https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14449-Technical-description-of-important-and-critical-products-with-digital-elements_en

      In general - more things are getting fixed than getting broken. So we'll
      work with the Open Regulatory Working group (i.e. our peer foundations)
      on a response.

      First doubt in CENELEC community about meeting April deadlines. Also
      appears that they are also unable to get volunteers from the CENELEC
      community.

      Open Source people participating (the ASF needs more!) suggest that
      things are going into the right direction; with sensible pointers to ISO
      29147 and ISO 30111; that are already understood.

      For the SBOMs, word on the street is that they are looking at the
      CISA/NTIA requirements; so no surprises expected there.

      As expected - composition is a source of disagreement (the EC seems to
      push ideas of certification being in essence, `transitive'; e.g. as in
      `trust is transitive' -- which does not work well in the land of
      security).

ETSI:

        The work on the vertical standarts (So specifically for things like
        PKI, software that does authentication, etc) has now begon.

        The open source community does need to get more people into this
        process. But the good news here is that ETSI is a lot more
        accommodating and pro-active than CENELEC. And they seem to have
        really taken this regulatory need to `consult with the open source
        community' to heart.

ORC:

        Open Regulatory Compliance Working Group - nicely picking up the right
        things/progress & sufficiently low barrier/open
        (https://github.com/orcwg)

USA:

        Waiting for the waters to calm before trying to even make sense of
        that. Pretty much all contacts we had are either gone or too busy with
        other stuff.

 We'll probably need to consider having a native ASA volunteer as a VP of
 PubAffairs USA over there; as the alignment of the US with the other power
 blocks is gone.

 Slightly more concerning is that we're seeing, or hearing of, historic
 information flows becoming stilted.

UN:

         There is rough consensus that endorsing the United Nations Open
         Source Principles:

  https://unite.un.org/news/osi-first-endorse-united-nations-open-source-principles

 is a good thing and furthers the general good the ASF tries do to in the
 world. And unlike the previous 'compact' in which one becomes part of an
 agreement - these principles just call for endorsement.

 Unless I hear a loud Nay from the board - I'll work with our President, VP of
 Legal and VP of Marketing to go through the details and then, if it still
 makes sense, make this happen.


-----------------------------------------
Attachment 11: Report from the VP of ECMA Relations  [Piotr P. Karwasz]


-----------------------------------------
Attachment 12: Report from the VP of W3C Relations  [Andy Seaborne]

Nothing to report this month.


-----------------------------------------
Attachment 13: Report from the Apache Legal Affairs Committee  [Roman Shaposhnik]

Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are flat at
30 issues compared to the last month.

We're still working with DLAPiper on two subpoenas -- no action required from
the board at this time -- since we're handling everything in a timely fashion.
All the subpoenas (current and past) can be found in
svn@private/foundation/legal/subpoenas should board members be curious about
the details.

VP Legal has advised members tweaking ASF Release Policy on the language and
semantics of what it means to bypass a 72-hours mandatory release period. The
PR with the final language has been merged and is now available on our
website.

Once again, we received an inquiry from a procurement department of a
corporation using ASF projects asking us to ammend the language of the Apache
License v2. The request was denied with a brief explanation given on our
stance.

We have received a couple of DMCA takedown notices for the content of the
infamous AAR-xxx JIRA space. The offending links were promptly taken down.

Andrew Musselman expressed his interest in shadowing VP Legal and we're
scheduled to start that conversation next week.


-----------------------------------------
Attachment 14: Report from the Apache Security Team Project  [Mark J. Cox]

February

* An issue in Apache OFBiz, CVE-2024-45195, was added to CISA's Known
  Exploited Vulnerabilities (KEV) catalog

* We continue to work with projects on creating 'security model'
  pages, this month Answer
  (https://answer.apache.org/community/security-model/), Xerces-C++
  (https://xerces.apache.org/xerces-c/secadv.html)

* We continue to share knowledge with projects, infra and tooling on
  topics such as SBOM, VEX, reproducible builds and MFA.

Stats for February 2025:

        47      [license confusion]
        33      [support request/question not security notification]
        12      [report/question relating to dependencies]

Security reports: 67 (last months: 59, 67, 84, 76)

        8       ['website or other infrastructure']
        7       ['airflow']
        5       ['hertzbeat', 'tomcat']
        4       ['inlong']
        3       ['thrift']
        2       ['answer', 'apisix', 'cloudstack', 'felix', 'hadoop', 'iotdb',
                'kvrocks', 'ofbiz']
        1       ['activemq', 'airavata', 'ambari', 'camel',
                'cocoon', 'cxf', 'dolphinscheduler', 'geode', 'hc', 'jmeter',
                'kafka', 'linkis', 'nifi', 'openmeetings', 'pulsar',
                'sling', 'steve', 'streampark', 'zeppelin']

In total, as of 1st March 2025, we're tracking 199 (last months: 182,
179, 168) open issues across 67 projects, median age 92 days (last
months: 105, 86, 117). 60 of those issues have CVE names assigned. 12
(last month: 11, 15, 17) of these issues, across 10 projects, are
older than 365 days.

* dolphinscheduler (Health amber): three very old issues (Last update:
  2025-03-06)

* 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. (Last update: 2025-03-06)

* openoffice (Health amber): Three issues in OpenOffice over 365 days
  old and a number of other open issues not fully triaged. (Last
  update: 2025-02-24)

* zeppelin (Health amber): a number of triaged issues are awaiting
  fixes and releases (Last update: 2025-03-06)

-----------------------------------------
Attachment A: Report from the Apache Airflow Project  [Bolke de Bruin]

## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines

## Project Status:
Current project status: *Ongoing* with *high* activity

Question to the board:

Context:

We agreed ([1], lazy consented to [2]) and followed an “expedite release
policy” where we allow the release manager to shorten the time to vote to 24
hrs (as long as total voting time is not less than 72 hrs) in case of RC2/RCN+
candidates. This is at the discretion of the Release Manager where we detect
an error and re-do the releases of failed artifacts (this is mostly useful in
case of small (but important) issues have been found during testing and we
release RC which is **almost** the same as the previous one - and it is easy
to verify the difference. The main goal is to optimize our processes because
of large number of releases and artifacts we have, in cases where such
releases are uncontroversial, and unlikely to cause a problem with any of the
concerns stated in [3]  We started - with this report - to flag those expedite
releases - following the discussion at members@ and PR [2] which stresses that
such expedite voting should be listed in the report to the board.

The question to the board: Is this a concern that we have such a policy, and
do you see any problems or potential improvements we can implement other than
flagging such expedited releases to the board in our reports ? Or maybe you do
not see the need to even flag them ?

[1] https://lists.apache.org/thread/8rpq06pobp6rnm9phnbc9fz4ky32sm16
[2] https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
[3] https://github.com/apache/www-site/pull/457


## Membership Data:
There are currently 68 committers and 35 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 Vikram
Koka on 2024-10-19. No new committers. Last addition was Pavan Kumar on
2024-10-29. We’ve been pretty busy and headed down with the huge effort of
Airflow 3 (expected release in April), with breaking changes and big
architectural changes, where pretty much every community member actively
working on Airflow is fully focused on.

However, that gave an opportunity for quite a few new community members to
shine and we are voting in new committers (6 votes in progress with deadline
being the report date,  likely 4 of them will pass, the others being
considered as “need a bit more diverse contributions”). We deferred
discussions on new PMC members until Airflow 3 is out, we would like to
discuss and agree on reviewing and renewing and make more objective the
rules/understanding of how we should approach non-coding committers approvals
and new PMC members. This requires more thorough discussions and a bit more
time to think and discuss about it and the current Airflow 3 push does not
make it easy.


## Project Activity:

- Development for Airflow 3 continues at a rapid pace, with several key
  features and enhancements actively being worked on. The target release is
  still set for March/April 2025. We have regular dev calls which are being
  recorded and published and status information about the progress is
  published on our wiki: https://cwiki.apache.org/confluence/display/AIRFLOW/
  Airflow+3+Dev+call%3A+Meeting+Notes#Airflow3Devcall:MeetingNotes-6March2025,
  https://cw
  iki.apache.org/confluence/display/AIRFLOW/Airflow+3.0+Development+Milestones


- The community continues to maintain and release updates for the 2.x series
  alongside the development of 3.0 to ensure stability and support for users
  during the transition. Airflow 2.10.4 and 2.10.5 bug-fix releases and 5
  batch releases of providers were released in this period. Full release
  activity:

Provider packages 2025-02-21 was released on 2025-02-26. Apache Airflow 2.10.5
was released on 2025-02-10. Provider packages 2025-02-04 was released on
2025-02-08. Provider packages 2025-01-26 was released on 2025-01-27 Provider
packages 2025-01-22 was released on 2025-01-26 Provider packages 2024-12-30
was released on 2025-01-03. Provider packages 2024-12-22 was released on
2024-12-26. Apache Airflow 2.10.4 was released on 2024-12-16.

Out of those releases: 1(celery) of 59 provider’s RC1s (originally prepared
2025-01-22) was expedited (24 hrs) due to our RC2+ policies (bug found during
testing): https://lists.apache.org/thread/qqb3xhfszocsfm073shcm8fj5kzsgh8o

We have slowed down provider releases a bit, mostly because of a huge
refactoring (successful) of the way providers are structured in our monorepo.
This is now completed and we resume with more regular releases.

- Security:

We are proceeding with the “Airflow Beach Cleaning” project with Alpha-Omega
and Python Software Foundation -  albeit with a little slower pace due to
Airflow 3 -  with a goal to review and help all Airflow Python dependencies
(700+) in terms of their security processes, willingness to cooperate and
“cleaning” our part of the security beach. However as result of the reviews
(and related decisions) we already agreed on some dependency removals and
 upgrades. We are still engaged with - currently < 20 initial projects and
 based on those conversations  we will scale our efforts in the coming months
 and years - with the goal of sharing our practices and teaching others in the
 ecosystem to follow up similar patterns. We spoke at FOSDEM and FOSS
 Backstage where we want to share our experience and enthuse others to follow.
 There is also accepted talk about it at 2025 CVE First & Vulncon conference
 in Raleigh, North Carolina in April where we also talk about it and exchange
 our learnings at one of the most prominent security conferences.

## Community Health:

- Commit velocity has shown again even higher increase (26% QoQ) owing to
  Airflow 3 development with a 4% increase in new PRs opened (which shows a
  healthy trend of completing the work started in past quarter, while not
  slowing down the development of improvements and bugfixes)

- The Dev mailing list activity has increased by 19% as we have a number of
  discussions and clarifications about features being completed for Airflow 3
  and the need to make final decisions on those.

- We have slightly less (198  - 15%) of contributors this quarter, that mostly
  owing to the fact that we mostly focus on Airflow 3 and prioritize work on
  it - also some of the contributions are put on hold until “after Airflow 3”
  as we focus on stabilizing what we already have for Airlow 3 - effectively
  putting any new features “on hold” to make sure what we deliver is stable
  and tested.

Significant work is put on testing Airflow 3 - we started to regularly release
Alpha and beta versions of Airflow, we have a test plan
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.0+Test+Plan that
we follow and have a team of people focusing on testing according to the plan
reporting and fixing the issues - a snapshot of the status - we have: 40
issues closed in Alpha releases
https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aopen%20label%3Aaffected_version%3A3.0.0alpha
19 open, 12 closed in beta releases
https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aopen%20label%3Aaffected_version%3A3.0.0alpha
9 open, 72 closed in Airflow main
https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aopen%20label%3Aaffected_version%3Amain_branch%20

- We published the results of Annual Airflow Survey - 2024 edition - this has
  been a huge success in terms of promotion and gathering the responses, we
  got responses from more than 5200 people (which is more than 5 x growth
  comparing to Airflow Survey 2023)  from 116 countries and it shows how huge
  Airflow community is and how eager they participate and want to shape the
  future of Airflow. More than 90% of respondents claim Airlow is important to
  their business, 90% of them think that learning Airflow is important for
  their career, 30% already use Airflow already for Machine Learning / AI
  workflows despite only Airflow 3 aims to target those. We’ve learned a ton
  from the survey and this will help us to shape Airflow 3+ future better.

The results of the survey are published at
https://airflow.apache.org/blog/airflow-survey-2024/

- Downloads of the main Apache Airflow package are decreasing below 30
  million/month (https://pypistats.org/packages/apache-airflow) - we believe
  mostly due to anticipation of Airflow 3, as we did not have a minor release
  of Airflow since August 2024
- GitHub stars: 39K (Steady growth)
- GitHub Contributors: 3,229 (Steady growth)

- Meetups, Conferences & other community events Fortnightly Airflow 3 dev
  calls have had ~30 attendees from various stakeholders: Astronomer, AWS,
  Bosch, Cloudera, Google. They have been very productive for Airflow 3
  development. Meeting notes at https://cwiki.apache.org/confluence/x/8ApeEg
  This is more focusd towards developers We have a separate monthly Airflow
  Town Hall call for users which attract ~50 attendees too, e.g.
  https://lists.apache.org/thread/015ormvpbj0172gfh2ftvyytj2vwrt5m recorded
  and published at our mailing lists where we have regularly few dozens of
  attendees participating in presentation of the community members - recently
  focusing on upcoming Airlfow 3 and community growth We had few hundreds of
  attendees in local meetups in Vancouver, Korea, NYC, Lagos, in the last
  quarter.

- Planning is well in progress for Airflow Summit 2025, Airflow Summit will
  happen in Seattle, Oct 7-10, in the Hyatt Regency hotel. CFP is open,
  super-early bird tickets can be already purchased. It’s been approved by
  the trademarks/Conference Planning team in the ASF and we have all
  important stakeholders fully on-board and aligned and leading the
  organisation of the event, with Software Guru producing the event. We aim
  for 500+ attendees. This is going to be a huge Airflow 3 - focused event.
  The Keynote speakers are invited already and being selected in the coming
  weeks, We have already few attendees who purchased super-early birds -
  without any announcements about speakers yet - and more than 40 CFP
  proposals.


-----------------------------------------
Attachment B: Report from the Apache Allura Project  [David Philip Brondsema]


## Description:
The mission of Apache Allura is the creation and maintenance of software
related to a software development infrastructure platform commonly known as a
"forge"

## Project Status:
Current project status: Ongoing (moderate activity)
Issues for the board: none

## Membership Data:
Apache Allura was founded 2014-03-18 (11 years ago)
There are currently 18 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Carlos Cruz on 2024-06-26.
- No new committers. Last addition was Carlos Cruz on 2024-06-27.

## Project Activity:
- login security and password-reset improvements
- JS & python dependency upgrades
- some prep work for python 3.12+ support
- minor new features & fixes

## Community Health:
- steady development from various committers
- no new community members for a while


-----------------------------------------
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 (3 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:

- On 2025-02-06, we officially released version 1.4.2.
- We are currently discussing feature requirements for the upcoming v1.4.5
  release and drafting a corresponding roadmap.
- We have migrated our website’s analytics system to the Apache-hosted Matomo
  service for improved data insights and community-driven analytics.

## Community Health:

- New plugin contributor +1
- New translation contributor +1

A newly added contributor has begun contributing significant new features. We
are actively mentoring them and other newcomers to help ensure a smooth
onboarding process and foster deeper engagement within the community.


-----------------------------------------
Attachment D: Report from the Apache Atlas Project  [Madhan Neethiraj]

## Description:
The mission of Apache Atlas is the creation and maintenance of software related
to a scalable and extensible set of core foundational governance services -
enabling enterprises to effectively and efficiently meet their compliance
requirements

## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: none

## Membership Data:
Apache Atlas was founded 2017-06-20 (8 years ago)
There are currently 49 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- Pinal Shah was added to the PMC on 2025-01-29
- No new committers. Last addition was Chaitali Borole on 2024-10-06.

## Project Activity:
- Atlas 2.4.0 was released on 2025-01-04
- CI improvements with use of GitHub actions
- Moving to using pull-requests (from review board) to review and merge patches
- Code readability improvements across the code base, with use of checkstyle
- fixes in Atlas Java client
- fixes in migration to improve resiliency
- improvements in metrics API
- updated versions for Netty,  Sqoop, logback, commons-io, DOMPurify, UI
  libraries

## Community Health:
- dev@atlas.apache.org had a 60% increase in traffic in the past quarter (534
  emails compared to 333)
- 99 commits in the past quarter (54% increase)
- 16 code contributors in the past quarter (77% increase)
- 41 PRs opened on GitHub, past quarter (173% increase)
- 39 PRs closed on GitHub, past quarter (69% increase)

## Recent releases:
- Apache Atlas 2.4.0 was released on 2025-01-04.
- Apache Atlas 2.3.0 was released on 2022-12-06.
- Apache Atlas 2.2.0 was released on 2021-08-17.
- Apache Atlas 2.1.0 was released on 2020-07-15.


-----------------------------------------
Attachment E: Report from the Apache Axis Project  [Robert Lazarski]

# Apache Axis Board Report

## Description

The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).

## Issues

There are no issues requiring board attention at this time.

## Membership Data:
Axis was created on 2001-01-19 (24 years ago). It is listed as established in
2009-12 but really the first Apache commit was in 2001.

There are currently 65 committers and 64 PMC members in this project, a vote
in 2010 made all committers automatically PMC members. One PMC member
resigned.

Community changes, past quarter:
 - Currently 64 PMC/ 65 Committers members.
 - Two new committers were added in the last 90 days, Andreas Lehmkühler was
   added on January 28th, 2025 and Christian Ortlepp on January 2nd, 2025.
   Both were added to the PMC on January 28th, 2025.

## Project Activity:
Recent releases:
 - Axis 2/Java 2.0.0 was released on March 10, 2025.
 - Axis 2/Rampart 1.8.0 was released on Dec 10, 2024.
 - Axis 2/C 1.6 was released on April 20, 2009.
 - Axis 1.4 was last released in 2006.

## Project state: Ongoing, with moderate activity

## Health report:

The Axis project added two new committers this past quarter; both voted on our
java-dev mailing list for the recent Axis2 release, while Christian Ortlepp
has made outstanding contributions via numerous GitHub pull requests.

Apache Axis2 2.0.0 was just released - the first release in about 2.5 years.
It was a bittersweet release in that while the end result fixed 35 Jira issues
and upgraded many dependencies on the road to replace javax libs with jakarta
in order to run on the latest Tomcat and Wildfly, it took too long and
frustrated some in our community due to no firm release date from our
volunteer community.

Beyond the jakarta transition, these delays included unforeseen Apache Axis
site problems detailed in AXIS2-6066 and MSITE-1033. Some libraries such as
Apache HttpComponents are used in advanced ways for our implementation and
testing, making the major upgrade to version 5 difficult. We also support
Apache Rampart - an optional add on to Axis2 for WS-Sec* support - which has
difficult code to maintain due to many dependencies in complicated encryption,
signing, and SAML related code.

Challenges overcome in the last 90's days includes releasing Apache Axiom
2.0.0 - a prerequisite for Axis2 2.0.0 and while technically part of the
Apache Webservices TLP, it is de facto managed currently by Axis committers
who are on the PMC of both projects.

Our community is starting to see new projects again on the
java-user@axis.apache.org and java-dev@axis.apache.org mailing lists, no
longer about SOAP but rather with a focus on JSON support and our unique
features with the Moshi library. Our JSON support had documentation
improvements with our recent release, including an upgrade of our examples to
Spring Boot 3.

Axis2/C has a new email thread on c-user@axis.apache.org in progress
discussing a 2.0.0 release that includes three PMC members, indicating a
viable future of the project. This discussion resulted in a recent GitHub PR
and commit to our Axis2/C GitHub repo.

## Axis2 java Jira issues opened in the last 90 days: 2

## Axis2 java Jira issues closed in the last 90 days: 26


-----------------------------------------
Attachment F: Report from the Apache Beam Project  [Kenneth Knowles]

## Description:
The mission of Apache Beam is the creation and maintenance of software related
to a unified programming model for both batch and streaming data processing,
enabling efficient execution across diverse distributed execution engines and
providing extensibility points for connecting to different technologies and
user communities.

## Project Status:
Current project status: Ongoing
Issues for the board: none.

## Membership Data:
Apache Beam was founded 2016-12-20 (8 years ago)
There are currently 96 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.

Community changes, past quarter:
- Danny McCormick was added to the PMC on 2024-12-12
- No new committers. Last addition was XQ Hu on 2024-06-24.

## Project Activity:

Technical highlights:
 - Stateful processing added to the Spark Runner.
 - Beam reports lineage metadata starting in 2.63.0, with support added to the
   Dataflow Runner.
 - Managed IcebergIO: added time-based partitioning, BigQuery MetaStore
     support, large performance improvements, autosharding
 - BigQueryIO: create managed BigLake tables dynamically
 - ML: added RAG chunking embedding, LangChain chunking, BigQuery
   vector/embedding and HuggingFace embedding

Major maintenance/upgrades/breaking changes:
 - Minimum Go version for Beam Go updated to 1.22.10
 - Upgraded to protobuf 4
 - Dropped AWS V1 connectors
 - Upgraded ZetaSQL to 2024.11.1 (requires Java 11+)

See https://github.com/apache/beam/blob/master/CHANGES.md for detailed change
notes.

Recent releases: Automatically generated by reporter.apache.org
- 2.63.0 was released on 2025-02-18.
- 2.62.0 was released on 2025-01-21.
- 2.61.0 was released on 2024-11-25.

Highlights of community activities:
- The Beam College 2025 event (https://beamcollege.dev/) will be held May
  15-17, 2025, and will include new training videos and a hackathon.
- Beam Summit 2025 (https://beamsummit.org/) is back to New York City, which
  will be held on July 8th & 9th. CFP is open until Apr 18, 2025.
- Five GSOC projects
(https://issues.apache.org/jira/browse/GSOC-279) are proposed for the
 community.

## Community Health:

- Email, issues, commits, and pull requests are all steady.
- Pull Requests have been closed at the same rate they have been opened, so we
  are keeping up.
- Issues have also been closed at the same rate as being opened, which is
  unusual - healthy projects like Beam _always_ have more issues opened than
  closed. This may be a quarterly blip due to some special circumstance or it
  may reflect some change in how the project is communicating.


-----------------------------------------
Attachment G: Report from the Apache Bigtop Project  [Masatake Iwasaki]

## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.

## Project Status:
Current project status: Onoging
Issues for the board: None

## Membership Data:
Apache Bigtop was founded 2012-09-19 (12 years ago)
There are currently 45 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Zhiguo Wu on 2024-08-19.
- Haopeng Liu was added as committer on 2025-01-23
- Masahiro Tanaka was added as committer on 2025-01-28

## Project Activity:
Recent releases:
3.3.0 was released on 2024-07-08.
3.2.1 was released on 2023-08-22.
3.2.0 was released on 2023-01-17.

bigtop-manager is actively developed. 73 pull requests are merged
in the past 3 months.

We are preparing for the 3.4.0 release.
Release branch is cut and CI jobs for building packages are ready[2][3][4].

Kengo Seki proposed to add Apache Airflow to Bigtop stack[5]
and submitted PR[6].
We are reviewing the code targeting 3.5.0 release.

[1] https://github.com/apache/bigtop-manager/pulls?q=closed%3A%3E2024-12-01+
[2] https://ci.bigtop.apache.org/job/Bigtop-3.4.0-x86_64/
[3] https://ci.bigtop.apache.org/job/Bigtop-3.4.0-aarch64/
[4] https://ci.bigtop.apache.org/job/Bigtop-3.4.0-ppc64le/
[5] https://lists.apache.org/thread/9pv3jd769zh605os3gc7b82cqpod9lsw
[6] https://github.com/apache/bigtop/pull/1328

## Community Health:
Community health is good.
We added 2 new committers since the last report.
We should have more traffic for the release process of 3.4.0
in the next quarter.


-----------------------------------------
Attachment H: Report from the Apache BVal Project  [Matthew Jason Benson]

## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions

## Project Status:
Current project status: Ongoing-low/dormant
Issues for the board: none

## Membership Data:
Apache BVal was founded 2012-02-14 (13 years ago)
There are currently 17 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.

Community changes, past quarter:
- No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Markus Jung on 2024-07-08.

## Project Activity:
Voting is in progress for Apache BVal version 3.0.2.

## Community Health:
Situation is normal; we have a few committers engaged to handle
dependency upgrades as they arise and we are addressing bugs in
timely manner when they become known.


-----------------------------------------
Attachment I: Report from the Apache Camel Project  [Andrea Cosentino]

## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.

## Project Status:
Current project status: Ongoing with high activity
Issues for the board: There
are no issues requiring board attention at this time.

## Membership Data:
Apache Camel was founded 2008-12-17 (16 years ago)
There are currently 94 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Colm O hEigeartaigh on 2024-03-11.
- No new committers. Last addition was Thomas Diesler on 2024-11-22.

## Project Activity:

We had to deal with a security vulnerability now public so we had to do more
releases.

Apache Camel:
- We released Camel 3.22.4
- We released Camel 4.8.3
- We released Camel 4.8.4
- We released Camel 4.8.5
- We released Camel 4.10.0
- We released Camel 4.10.1
- We released Camel 4.10.2
- We are in the process of releasing 4.8.5 for the 4.8.x LTS line
- We are in the process of releasing 4.10.2 for the 4.10.x LTS line
- Note: Camel releases have synchronized releases of Camel-Karaf and
  Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
  synchronized.
- 4.8.x is our last LTS release train. We released the main version 4.8.0 with
  two others patch releases 4.8.3 and 4.8.4
- The situation is really healthy and the community is super. We are
  introducing many new features and working on engaging the community more.
  Camel is growing even in terms of interest

Apache Camel K:
- We released the 2.5.1 version
- We released the 2.6.0 version
- For Camel-K-runtime we released 3.15.2, for 2.5.x work.
- Camel K is in good shape and the community is expading with new contributors
  and many new good idea and many good interactions. The situation is healthy.

Apache Camel Kamelets:
- We released Camel Kamelets 4.8.3
- We released Camel Kamelets 4.8.4
- We released Camel Kamelets 4.8.5
- We released Camel Kamelets 4.10.0
- We released Camel Kamelets 4.10.1
- We released Camel Kamelets 4.10.2
- The 4.8.x release train is matching the LTS release from Camel core and it's
  an important building block for starting with routes
- We introduced a lot of new Kamelets and we are improving the documentation
  by focusing on much more examples. Also we improved the Kamelets
  description.

Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
  multiple releases
- We released Camel-quarkus 3.15.2
- We released Camel-quarkus 3.15.3
- We released Camel-quarkus 3.17.0
- We released Camel-quarkus 3.18.0
- We released Camel-quarkus 3.19.0
- The 3.15.x is matching the 4.8.x release train from the main project
- A lot of work has been done on testing side more new features and extensions
  have been developed and improved.

Apache Camel-Karavan:
- Camel-Karavan is improving and the community around the project is
  increasing in number of features and new issues reporting. It's growing.
- We released the 4.10.0
- We released the 4.8.1
- The 4.10.x is aligned to Camel 4.10.x LTS

Camel-Kafka-Connector:
- 4.8.3 has been released and based on the last LTS release train 4.8.0
- The community is active and we receive a lot of feedback and requests. We
  are improving the documentation.

Apache Camel-Karaf:
- Camel-karaf main branch has been updated and now works with Camel 4.9.0 and
  Karaf 4.4.7+. Many new contributors are helping on this.
- We released also 3.22.4 for this project.

## Community Health:
- dev@camel.apache.org had a 9% increase in traffic in the past quarter (361
  emails compared to 330): Related to release planning and more heads up
- issues@camel.apache.org had a 4% decrease in traffic in the past quarter
  (2138 emails compared to 2221): Most of the projects are now using Github as
   first way of opening issues, so the decrease is somewhat expected.
- users@camel.apache.org had a 31% increase in traffic in the past quarter
  (182 emails compared to 138): Users are starting to move and ask questions
   on Zulip, but we had many discussion around releasing and questions from
   users
- PRs opened: 1450, 18% decrease. This is because we slowed down on some
  subprojects.
- PRs closed: 1460, 17% decrease. Same reason.
- Issues opened 169, 34% decrease. The reason is related to the slowing down
  on some subprojects.
- Issues closed 190, 25 decrease. Same reason.


-----------------------------------------
Attachment J: Report from the Apache Cayenne Project  [Michael Ray Gentry]

# Apache Cayenne Board Report, March 2025

## Description

Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object graph persistence and provides an ORM
runtime, remote persistence services*, and a cross-platform GUI
database mapping/modeling/development tool.

*Remote persistence services is being phased out for 5.0 (milestone
stage) to simplify the product. We could only identify one user of this
feature and he is switching to RESTful services.

## Project Status

### Project State

Ongoing

### Issues for Board

None

## Membership Data

Apache Cayenne was founded 2006-12-19 (18 years ago).
There are currently 24 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.

Community changes, past quarter:

- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Jurgen Doll on 2024-08-27.

## Project Activity

After the release of 4.2.x, most development has shifted to 5.0. Versions
prior to 5.0 are maintenance-only.

- Cayenne 4.0.x (stable)
  - Maintenance only.

- Cayenne 4.1.x (stable)
  - Maintenance only.

- Cayenne 4.2.x (stable)
  - Maintenance only.

- Cayenne 5.0 (milestone)
  - New features and primary development.

Cayenne 4.2.2 (a maintenance/bug-fix release) is being worked on. The
initial release preparations uncovered a regression and therefore has
been paused until both issues are resolved.

### Releases

- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2.1 on 2024-06-20.
- Cayenne 5.0.M1 on 2024-09-09.

## Community Health

Cayenne is healthy.

Developer mailing list traffic increased primarily due to 5.0.x and 4.2.2
(the maintenance release mentioned above) being discussed.

Code commits also increased as a result of the 5.0.x and 4.2.2 work.

 User mailing list traffic was quiet, which hopefully means no significant
issues the user-base needs to discuss.


-----------------------------------------
Attachment K: Report from the Apache Celeborn Project  [Keyong Zhou]

## Description:
The mission of Apache Celeborn is the creation and maintenance of software
related to an intermediate data service for big data computing engines to boost
performance, stability, and flexibility

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Celeborn was founded 2024-03-20 (a year ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- Fei Wang was added to the PMC on 2024-12-31
- Sanskar Modi was added as committer on 2024-12-20
- Weijie Guo was added as committer on 2024-11-28

## Project Activity:
Software development activity:

 - Release 0.5.4 is in the process of discussion.
 - CIP-6 Support Flink hybrid shuffle is finished.
 - CIP-7 Celeborn CLI is finished.
 - CIP-8 Partition writer refactor is almost finished.
 - CIP-10 Introduce Celeborn Chaos Testing Framework is under development.
 - CIP-11 Support worker tags is finished.
 - CIP-12 Support HARD_SPLIT in PushMergedData is finished.
 - CIP-13 Support automatic scaling is under development.
 - CIP-14 Support CPP SDK is under development.
 - Skew partition optimization is almost finished.

Meetups and Conferences:

 - 1 talk was given in Apache Spark & Paimon Meetup 2024.
 - 2 talks were given in FFA 2024.

Recent releases:

- 0.5.3 was released on January 6th, 2025.
- 0.4.3 was released on December 10th, 2024.
- 0.5.2 was released on November 26th, 2024.

## Community Health:
Overall community health is good. In the past quarter, the dev mail list mail
number had a 6% decrease in the past quarter to 152, the issues mail list had
a 31% decrease to 1160, the PMC considered it as normal because the absolute
number is relatively high. We have been performing extensive outreach for our
users, and encouraging them to contribute back to the project. Also, we are
active in making a voice in various conferences to attract more users.


-----------------------------------------
Attachment L: Report from the Apache CloudStack Project  [Daniel Augusto Veronezi Salvador]

## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage, and
networking devices.

## Project Status:
Current project status: Ongoing, with high activity.
Issues for the board: None.

## Membership Data:
Apache CloudStack was founded on 2013-03-19 (12 years ago)
There are currently 141 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- João Jandre Paraquetti was added to the PMC on 2025-02-26
- Fabricio Duarte Junior was added as committer on 2025-02-13
- Jithin Raju was added as committer on 2025-02-13
- Swen Brueseke was added as committer on 2025-03-09

## Project Activity:

Software development/management activity:

- The current version of Apache CloudStack is 4.20.0.0;

- The versions released in the past quarter are:
  - 4.19.2.0 was released on 2025-03-03.

- The community is planning to release Apache CloudStack 4.20.1.0 between
  April and May 2025.

- The community is planning to release Apache CloudStack 4.21.0.0 by June
  2025.

- We are working on some security patches and expect to release them by end of
  March.

- The latest CloudStack-Go SDK version (v2.17.0) was released on December 31,
  2024.

Meetups and Conferences:
- We do not plan to attend the Community Over Code NA 2025 with a specific
  track.

- We are organizing the CloudStack Collaboration Conference 2025, which is
  expected to be held in Italy, between November 19-21th.

- CloudStack European User Group is scheduled for May 8, 2025 in Vienna,
  Austria: https://cloudstack.apache.org/blog/cseug-2025/

- CloudStack India User Group 2025 is being planned to be held in Delhi-NCR;
  the dates were not confirmed yet.

- The Apache CloudStack project will be exhibiting at CloudFest, from March
  17-20th, 2025 in Rust, Germany:
  https://cloudstack.apache.org/blog/cloudfest-2025/

## Community Health:

- There are new PMC members and committers added since the previous report.
  Furthermore, we are discussing new PMC members and committers.

- According to the reporter tool, the Community Health Score (Chi) is 10.00
  (Super Healthy). The number increased from the past quarter due to the new
   committers and PMC members invited.

- Mailing lists statistics:
  - dev@cloudstack.apache.org had a 34% increase in traffic in the past
    quarter (605 emails compared to 451);
  - issues@cloudstack.apache.org had an 18% increase in traffic in the past
    quarter (91 emails compared to 77);
  - marketing@cloudstack.apache.org had a 79% decrease in traffic in the past
    quarter (5 emails compared to 23);
  - users@cloudstack.apache.org had a 33% increase in traffic in the past
    quarter (1540 emails compared to 1151);
  - Changes (PRs) on the cloudstack-www repository are reflected on the
    'issues' mailing list, therefore, explaining the increase in traffic.
  - Discussions on the cloudstack repository are reflected on the 'users'
    mailing list, therefore, explaining the increase in traffic. Furthermore,
    we are observing new users trying CloudStack.
  - Between September and December 2024 we released several security patches
    and attended several events; thus, the traffic in the 'marketing' mailing
    list increased in that period. In the past quarter (December 2024 to
    February 2025), we did not need to release new security patches and we did
    not attend events; thus, the traffic in the 'marketing' mailing list
    expectedly decreased in that quarter.

- GitHub statistics:
  - 574 commits in the past quarter (94% increase);
  - 56 code contributors in the past quarter (51% increase);
  - 284 PRs opened on GitHub, past quarter (31% increase);
  - 283 PRs closed on GitHub, past quarter (66% increase);
  - 153 issues opened on GitHub, past quarter (-10% change);
  - 173 issues closed on GitHub, past quarter (54% increase);
  - Between September and December 2024 we had a code freeze for releasing
    version 4.20.0.0, which decreased the number of new interactions. After
    the release, we have returned to our normal pace.


-----------------------------------------
Attachment M: Report from the Apache Commons Project  [Gary D. Gregory]

## Description:
The mission of Apache Commons is the creation and maintenance of Java focused
reusable libraries and components

## Project Status:
Current project status: Ongoing.
Issues for the board: None.

## Membership Data:
Apache Commons was founded 2007-06-19 (18 years ago)
There are currently 151 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- Arnout Engelen was added to the PMC on 2024-12-22
- Arnout Engelen was added as committer on 2024-12-23

## Project Activity:
Apache Commons is continuing to release feature and maintenance release of its
various components. We've released the following components during this
reporting period:
- VFS-2.10.0 was released on 2025-02-14.
- BEANUTILS-1.10.1 was released on 2025-02-13.
- LOGGING-1.3.5 was released on 2025-02-08.
- PARENT-81 was released on 2025-01-30.
- PARENT-80 was released on 2025-01-29.
- CODEC-1.18.0 was released on 2025-01-27.
- POOL-2.12.1 was released on 2025-01-27.
- DAEMON-1.4.1 was released on 2025-01-14.
- BUILD-PLUGIN-1.15.0 was released on 2025-01-11.
- CSV-1.13.0 was released on 2025-01-11.
- RELEASE-PLUGIN-1.9.0 was released on 2025-01-11.
- BEANUTILS-1.10.0 was released on 2025-01-07.
- BEANUTILS-2.0.0-M1 was released on 2025-01-07.
- PARENT-79 was released on 2025-01-07.
- CODEC-1.17.2 was released on 2025-01-06.
- COLLECTIONS-4.5.0-M3 was released on 2024-12-18.
- TEXT-1.13.0 was released on 2024-12-13.

## Community Health:
Our commit activity is the same as the previous reporting period with the same
number of code contributors. On GitHub, pull request activity is down but
still proving valuable input for new features and bug fixes. Our email activity
is up on our user and development lists. Bug reports are also coming in through
both Jira and the mailing lists.


-----------------------------------------
Attachment N: Report from the Apache Cordova Project  [Bryan Ellis]

## Status report for the Apache Cordova project - March 2025

## Description

A platform for building native mobile applications using HTML, CSS and
JavaScript.

## Project Status

**Current project status:**

Our current work continues on staying updated with changes to iOS and Android,
our most utilized platforms, alongside ensuring regular updates to plugins.

Our status dashboard at http://status.cordova.io remains mostly all green and
our nightly builds are still extremely stable.

**Issues for the board:**

There are no issues requiring board attention at this time.

## Membership Data

There are currently 99 committers and 96 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 Pieter Van Poyer on 2021-04-06.
- No new committers. Last addition was Pieter Van Poyer on 2021-04-06.

## Project Activity

Our project made releases this quarter for our core platforms to keep up with
current requirements.

**Releases:**

- cordova-plugin-media-capture@6.0.0 was released on 2025-02-26.
- cordova-common@5.0.1 was released on 2025-02-02.
- cordova-plugin-file@8.1.3 was released on 2024-11-20.

## Community Health

Overall, the community health is strong. The ASF Project Statistics gives the
project a Community Health Score (Chi): 4.70 (Healthy)

We continue to see contributions from a dedicated group of individuals. The
project remains stable and continues to see good traffic.

This quarter, we released a few patch updates and a major release. The major
release focused on one of our plugins, ensuring compliance with Android's new
permission requirements.

A couple contributors continue to focus on improvements and preparations for
future major releases of Cordova-iOS and Cordova-Android. Some have gone above
and beyond by reaching out to Android to raise awareness of issues and discuss
solutions. This proactive approach provided clear direction, allowing us to
begin preparing necessary changes to address these issues.

On January 31st, Cordova hosted a virtual meetup to wrap up 2024 and kick off
the new year. The main goal was to highlight Cordova's accomplishments and
share what we hope to work on in 2025. We also gathered feedback from
community members to understand their experiences with Cordova, how they use
it, any questions they had, features they would like to see, or issues that
needed investigation. This was the first meetup we've hosted in a long time,
and we hope to continue these events for information sharing and community
engagement. A total of 117 people registered, with around 70 have attended.
Among the meetups attendees we have seen a sentiment that Cordova is stable
for many projects and users rely on it for their apps. We also saw some
interest in contributing and maintaining from new faces, but they don't know
where to start. For this reason we are discussing and working on some ideas to
make contributing, testing and releasing Cordova easier.

Github discussions is how our community supports each other and is live at
https://github.com/apache/cordova/discussions. All discussions are forwarded
to the 'issues' list.

## Mailing List Activity

- dev@cordova.apache.org had a 76% decrease in traffic in the past quarter
(20 emails compared to 81)
- issues@cordova.apache.org had a 31% decrease in traffic in the past quarter
  (685 emails compared to 980)


-----------------------------------------
Attachment O: Report from the Apache cTAKES Project  [Pei Chen]

## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text

## Project Status:

Current project status: Ongoing with moderate/low activity.

Issues for the board: There are no issues requiring board attention at this
time.

## Membership Data:
Apache cTAKES was founded 2013-03-19 (12 years ago)
There are currently 40 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.

Community changes, past quarter:
- No new PMC members. Last addition was Gandhi Rajan on 2018-07-12.
- No new committers. Last addition was Dennis Johns on 2023-01-06.

## Project Activity:
- Committee continues to work on the future release (7.x.x)
- 6.0.0 was released on Sept 16 2024
- 5.1.0 was released on May 10 2024
- 4.0.0.1 was released on Jan 20 2021
- 4.0.0 was released on Apr 27 2017

## Community Health:
There weren't many commits last quarter, but picked up this quarter.
notifications@ctakes.apache.org had a increase in traffic (16 emails compared
to 0)
27 commits in the past quarter (2700% increase)
5 code contributors in the past quarter (500% increase)


-----------------------------------------
Attachment P: Report from the Apache Curator Project  [Enrico Olivelli]

## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Curator was founded 2013-09-18 (11 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Kezhu Wang on 2023-03-25.
- No new committers. Last addition was Kezhu Wang on 2023-03-24.

## Project Activity:

Recent releases:
5.8.0 was released on 2025-03-06.
5.7.1 was released on 2024-10-13.
5.7.0 was released on 2024-06-15.

## Community Health:

The community is healthy. We are accepting patches from both committers and
non-committers and we have also cut a release recently. We still don't have
contributors on our radar that could be invited as committers.


-----------------------------------------
Attachment Q: Report from the Apache Daffodil Project  [Mike Beckerle]

## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data Format Description Language (DFDL)
used to convert between fixed format data and more readily processed forms such
as XML or JSON

## Project Status:
Current project status: Ongoing. High activity.
Issues for the board: none.

## Membership Data:
Apache Daffodil was founded 2021-02-16 (4 years ago)
There are currently 19 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Peter Katlic on 2024-03-17.
- No new committers. Last addition was Peter Katlic on 2024-03-17.

## Project Activity:
Apache Daffodil v3.10.0 was released on 2025-01-21.
The corresponding daffodil-sbt plugin v1.3.0 was released on 2025-01-31.

## Community Health:
Good activity level. A bit less email activity, but still good commit traffic.

Attracting new contributors with diverse interests and uses for the project
remains an ongoing challenge and in the long run, as with all projects, is a
risk factor.

Many contributors are employed explicitly for contributions to the project,
and these are funded from the US government. To date there has been no
disruption of this funding, but it is a short term risk factor.


-----------------------------------------
Attachment R: Report from the Apache DataFusion Project  [Andrew Lamb]

## Description:
The mission of Apache DataFusion is the creation and maintenance of software
related to an extensible query engine

## Project Status:
Current project status: New + Ongoing (high activity)
Issues for the board: None


## Membership Data:
Apache DataFusion was founded 2024-04-16 (a year ago)
There are currently 44 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.

Community changes, past quarter:
- Jonah Gao was added to the PMC on 2024-12-16
- Parth Chandra was added as committer on 2025-03-10
- Yongting You was added as committer on 2025-01-18


## Project Activity:

### Overall

DataFusion is participating in Google Summer of Code with a number of ideas
for projects with mentors already selected[1][2][3]. Additionally, some ideas
on how to make DataFusion an ideal selection for university database projects
such as the CMU database classes have been put forward.

[1]: https://github.com/apache/datafusion/issues/14577
[2]: https://summerofcode.withgoogle.com/programs/2025/organizations/apache-datafusion
[3]: https://datafusion.apache.org/contributor-guide/gsoc_application_guidelines.html


### DataFusion core

https://github.com/apache/datafusion

- 46.0.0 was released on 2025-03-07.
- 45.0.0 was released on 2025-02-07.
- 44.0.0 was released on 2024-12-31.

Releases continue monthly and the project has been very active with many
commits a day. It seems more new projects have been using DataFusion for query
processing, which brings more contributors but also means we are spending more
time fielding questions and figuring out how many more features to accept.

Bruce Ritchie recently authored a [blog] about some of the features and the
outlook for the next 6 months. A relevant quote:

> In the core DataFusion repo alone we reviewed and accepted almost 1600 PRs
  from 206 different committers, created over 1100 issues and closed 751 of
  them 🚀.

We have been focusing more recently on pre-release testing and making it
easier for downstream consumers to use DataFusion, which is still a challenge
given how fast the project is moving.

[blog]: https://datafusion.apache.org/blog/2025/02/20/datafusion-45.0.0/

### Sub project: DataFusion Python

https://github.com/apache/datafusion-python

- PYTHON-45.2.0 was released on 2025-02-23.
- PYTHON-44.0.0 was released on 2025-02-07.
- PYTHON-43.1.0 was released on 2024-12-12.

We have been working on making it easier to interoperate with other systems,
including support for FFI TableProvider ([#12920]) and new user documentation
on FFI [#1031]

[#12920]: https://github.com/apache/datafusion/pull/12920
[#1031]: https://github.com/apache/datafusion-python/pull/1031

### Sub project: DataFusion Comet

https://github.com/apache/datafusion-comet

- COMET-0.6.0 was released on 2025-02-17.
- COMET-0.5.0 was released on 2025-01-17.

You can read about the recent happenings in Comet in the [0.6.0 blog]


[0.6.0 blog]: https://datafusion.apache.org/blog/2025/02/17/datafusion-comet-0.6.0/


### Sub project: DataFusion Ballista

https://github.com/apache/datafusion-ballista

- BALLISTA-44.0.0 was released on 2025-03-05.

There has been some renewed interest in this project as the foundation for
distributed query engines, and we made a new release recently.

### (New!) Sub project: DataFusion Ray

https://github.com/apache/datafusion-ray

This is a new project aims to make it easier to run DataFusion in a
distributed environment using the https://www.ray.io/ compute engine

Contributors are working hard at the moment to get DataFusionRay 0.1.0 out!
Hopefully we can do that before the announcement and then there should be
plenty to add.

### Sub project: sqlparser-rs

https://github.com/apache/datafusion-sqlparser-rs

We have made two releases since sqlparser became part of DataFusion.

- SQLPARSER-0.55.0 was released on 2025-03-05.
- SQLPARSER-0.54.0 was released on 2025-01-23.
- SQLPARSER-0.53.0 was released on 2024-12-18.

Ifeanyi Ubah (iffyio) is doing a great job reviewing PRs to keep the code
consistent and flowing.

## Community Health:

While we as always struggle with code review capacity, we have many active
committers, and the community in general helps each other out with reviews. We
continue to actively grow our committer and PMC ranks.

We had several in person meetups in Chicago, Boston, and Amsterdam, and are
working on organizing one in London in April 2025[1].

[1]: https://github.com/apache/datafusion/discussions/14647


-----------------------------------------
Attachment S: Report from the Apache DeltaSpike Project  [Mark Struberg]


-----------------------------------------
Attachment T: Report from the Apache Druid Project  [Gian Merlino]

Report date: 2025-03-03

## Description

Apache Druid is a high performance real-time analytics database. It is
designed for workflows where low-latency query and ingest are the main
requirements. It implements ingestion, storage, and querying subsystems. Users
interface with Druid through built-in SQL and JSON APIs, as well as
third-party applications.

Druid has an extensive web of connections with other Apache projects: Calcite
for SQL planning, Curator and ZooKeeper for coordination, Kafka and Hadoop as
data sources, Avro, ORC, or Parquet as supported data input formats, and
DataSketches for scalable approximate algorithms. Druid can also be used as a
data source by Superset.

## Issues

There are no issues requiring board attention at this time.

## Activity

Our last major release was Druid 32.0.0, which contained over 220 new
features, bug fixes, performance enhancements, documentation improvements, and
additional test coverage from 52 contributors. The number of contributors is
somewhat lower than the last major Druid release (which had 65 contributors).
Druid typically does major releases 3–4 times a year.

Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,098
members, up 140 members (4.7%) since our last report. This is our most active
channel for user support and usage-oriented discussions. Development
discussions happen more on GitHub, and to some degree on the dev mailing list.

## Membership data

Apache Druid was founded 2019-12-17 (5 years ago) There are currently 70
committers and 39 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.

Community changes, past quarter:
- Adarsh Sanjeev was added to the PMC on 2025-01-16
- Akshat Jain was added as a committer on 2025-01-10

## Recent releases
 - 32.0.0, a major release, on 2025-02-13.
 - 31.0.1, a patch release, on 2024-12-25.
 - 31.0.0, a major release, on 2024-10-22.

## Development activity by the numbers

In the last 3 months:
 - 157 commits from 30 contributors
 - 212 pull requests opened
 - 233 pull requests merged/closed

In a comment to our September 2024 prior board report, Rich Bowen mentioned
that he seldom cares about the statistics reported by projects. If this is the
opinion of the board generally, please let me know, and I will remove this
section from future reports. It would save about 15 minutes per report.


-----------------------------------------
Attachment U: Report from the Apache ECharts Project  [Wenli Zhang]

## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript

## Project Status:
Current project status: Ongoing
Issues for the board: NA

## Membership Data:
Apache ECharts was founded 2020-12-16 (4 years ago)
There are currently 30 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- ShiZhao Pan was added to the PMC on 2025-01-09
- ShiZhao Pan was added as committer on 2025-01-05

## Project Activity:

We are working towards the next major release, Apache ECharts 6.0.0,
which is about 90% done and is expected to be released by the end of March
or early April. In this version, we are going to introduce a lot of new
features, like Matrix coordinate, Break axis, Chord series, Scatter jittering
and so on.

## Community Health:

The community is developing steadily. There are no major issues that are
particularly worthy of concern. We can look forward to more exciting progress
and achievements after the release of 6.0.0.


-----------------------------------------
Attachment V: Report from the Apache Felix Project  [Karl Pauls]

## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.

## Project Status:
Current project status: Ongoing, with low activity.
Issues for the board: none.

## Membership Data:
Apache Felix was founded 2007-03-28 (18 years ago)
There are currently 68 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- No new PMC members. Last addition was Georg Henzler on 2019-06-10.
- No new committers. Last addition was Paul Rütter on 2024-11-15.

## Project Activity:
- Existing implementations have been improved/enhanced based on community
 feedback.
- Released 6 components. Mostly bug fixes/minor improvements related to jetty
 updates.

### Releases
- org.apache.felix.webconsole-4.9.10 was released on 2025-02-05.
- org.apache.felix.webconsole-5.0.10 was released on 2025-02-05.
- org.apache.felix.http.base-5.1.10 was released on 2025-01-28.
- org.apache.felix.http.jetty-5.1.28 was released on 2025-01-28.
- org.apache.felix.http.jetty12-1.0.20 was released on 2025-01-28.
- org.apache.felix.http.jetty12-1.0.19 was released on 2024-12-17.


## Community Health:
- Overall the project is in ok health with little ongoing activity.
- The community activity remains on a low level and we continue to see little
  new development right now. We are at the lookout for new topics and
  contributors.
- Questions on the user list are answered, development concerns are either
  discussed on the mailing list or directly in the JIRA issues.
- We had no issues voting on releases and JIRA issues are generally addressed.


-----------------------------------------
Attachment W: Report from the Apache Flex Project  [Harbs]

## Description:
The mission of the Apache Flex project is to create and maintain software
related to the development of expressive web applications that deploy to all
major browsers, desktops and devices (including smartphones, tablets and tv)

## Project Status:
Current project status: Stable with little activity
Issues for the board: None

## Membership Data:
Apache Flex was founded 2012-12-19 (12 years ago)
There are currently 67 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Greg Dove on 2023-03-03.
- No new committers. Last addition was Greg Dove on 2016-09-07.

## Project Activity:
There has been almost no activity in the last quarter

## Community Health:
No change in community health. There were a couple of emails as well as a
single Github PR.


-----------------------------------------
Attachment X: Report from the Apache Flink Project  [Robert Metzger]

## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Flink was founded 2014-12-17 (10 years ago)
There are currently 119 committers and 52 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 Rui Fan on 2024-06-04.
- Feng Jin was added as committer on 2025-02-21
- Xuyang Zhong was added as committer on 2025-02-19

## Project Activity:

Releases:
- kubernetes-operator-1.11.0 was released on 2025-03-03.
- shaded-20.0 was released on 2025-02-24.
- 1.19.2 was released on 2025-02-12.
- 1.20.1 was released on 2025-02-12.
- connector-hive-3.0.0 was released on 2025-02-10.

Upcoming releases:
- Flink 2.0 RC2 vote is opened. 2.0-preview1 was released at the end of 2024.


## Community Health:
- Mailing list activity is going up again a bit (+15% on dev@), also the
  number of PRs closed has gone up.
- The PR closed number is going up, because the community decided to activate
  a stale PR cleanup bot.


-----------------------------------------
Attachment Y: Report from the Apache Gobblin Project  [Abhishek Tiwari]

## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Gobblin was founded 2021-01-20 (4 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-20.
- Abhishek Mahendra Jain was added as committer on 2025-01-19
- Vivek Rai was added as committer on 2025-01-19

## Project Activity:
- Stablized DagProcessingEngine thread termination through graceful exception
  handling
- Parameterized ActivityOptions creation
- Expanded Activity to support SubmitGTE activity
- Upgraded Hadoop-Azure-Datalake support
- Modified Temporal task queue name due to length constraints
- Fixed Temporal metrics by closing scope on job completion
- Added Temportal worker metrics
- Improved ExecutorService to do a graceful shutdown of Temporal Application
  Master
- Added ActivityType & HeartBeats for Temporal Activities
- Added ContainerCompletion callback support in DynamicScalingYarnService
- Defined Initializer.AfterInitializeMemento for Gobblin on Temporal to tunnel
  state from GenerateWorkUnits to CommitActivity
- Added support to emit Gobblin on Temporal GTEs to time WorkUnit preparation
- Added support for Gobblin on Temporal Dynamic Auto-Scaling using heuristics
  based on WorkUnitsSizeSummary
- Enhanced GoT observability with WorkUnitsSizeSummary and WorkUnitSizeInfo
- Support to set default authenticator in Yarn Temporal containers
- Support to proceed with commit in case of exception from Temporal workload
  execution
- Added Gobblin on Temporal YarnService Integration with DynamicScaling
- Fixed other issues like Nan while generating size summary, cleanup of
  workdir in Gobblin on Temporal execution, handling of non transient
  exceptions, avoid shutting down QueueProcessor on non-InterruptedException

* Last Release date: 30th August, 2023

## Community Health:
- There have been 34 commits since December 2024.
- 4 commits have been from non-committers.
- Abhishek Mahendra Jain and Vivek Rai were voted in Jan, 2025 as a
  committers. We constantly look for consistent contributors to vote them in
  as Committers.


-----------------------------------------
Attachment Z: Report from the Apache Guacamole Project  [Mike Jumper]

## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access

## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none.

## Membership Data:
Apache Guacamole was founded 2017-11-14 (7 years ago)
There are currently 16 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.

Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- Corentin Soriano was added as committer on 2025-01-18

## Project Activity:
The project is focused on finalizing the much-awaited 1.6.0 release.
Performance regressions noted in the past seem to be resolved. Remaining tasks
consist of resolving graphical artifacts (or deciding to move forward with
this known issue), correcting a regression specific to FreeRDP 3.x, and
completing outstanding documentation.

Recent releases:
- 1.5.5 was released on 2024-04-05.
- 1.5.4 was released on 2023-12-07.
- 1.5.3 was released on 2023-07-31.

## Community Health:
The community continues to be active and healthy. Activity on the lists
demonstrates considerable and understandable interest in the 1.6.0 release.


-----------------------------------------
Attachment AA: Report from the Apache Gump Project  [Stefan Bodewig]

# Description

Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well as
non-ASF projects and their dependencies. It started in the Java part
of the foundation but also builds projects like APR, HTTPd and
OpenSSL.

# Project Status

Current Status: dormant - when things need to be done, they get done

Issues: There are no issues requiring board attention.

# Membership Data

Apache Gump was founded 2004-02-18. There are currently 16 committers
and 10 PMC members in this project.

The Committer-to-PMC ratio is 8:5.

Community changes, past quarter:

    No new PMC members. Last addition was Mark Thomas on 2014-12-03.
    No new committers. Last addition was Konstantin Kolinko on 2015-02-11.

# Project Activity

We (Mark, actually) are ironing out a few problems with the latest
upgrades in our build environment which has created a bit more
activity than usual.

The Tomcat community is the only one still using Gump actively and the
only activity in Gump is around keeping the infrastructure alive and
tweaking things for the benefit of Tomcat builds.

We will certainly support any other project that wants to get the
benefit of the early warning system for backwards incompatible changes
Gump provides, but we are not actively recruiting projects.

## Releases

Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

# Community Health

There isn't much happening but help is there when anybody needs it.

-----------------------------------------
Attachment AB: Report from the Apache Helix Project  [Junkai Xue]

## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources

## Project Status:
Current project status: Ongoing, Moderate
Issues for the board: no issues

## Membership Data:
Apache Helix was founded 2013-12-17 (11 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- No new committers. Last addition was Molly Gao on 2023-06-06.

## Project Activity:
- 1.4.3 was released on 2025-02-04
- 1.4.2 was released on 2024-12-27
- 1.4.1 was released on 2024-09-23
- 1.4.0 was released on 2024-06-21

## Community Health:

Recently, the changes are majorly focusing on improving stability and
reliability of Helix. Release 1.4.3 are critical fixes that impact
other Apache projects, such as Apache Pinot.

Major projects for Helix 2.0 is still under development. Instead of supporting
language agnostic. We also plan to support following two directions:
1. Expand integration for modern cloud from only Azure to AWS.
2. Provides a more lightweight version of Helix component for simple sharding
usecases for easy usage and better performance.


-----------------------------------------
Attachment AC: Report from the Apache Hive Project  [Naveen Gangam]

## Description:
Apache Hive was founded 2010-09-22 (14 years ago)
The Apache Hive ™ data warehouse software facilitates reading, writing, and
managing large datasets residing in distributed storage (Apache Hadoop) using
SQL.

## Project Status:
ACTIVE. Apache Hive community remains fairly active with new features work on
master and new release.
Issues for the board: None

## Membership Data:
There are currently 111 committers and 56 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Zhihua Deng on 2024-10-11.
- No new committers. Last addition was Dmitriy Fingerman on 2024-11-12.

## Project Activity:
Latest release 4.0.1 was released on 2024-10-02.
4.1.0 Release activity underway with support for JDK17.

Commit activity
132 commits from 49 code contributors in the past quarter
134 PRs opened, 147 PRs closed on GitHub in the past quarter


## Community Health:
The community remains vibrant and engaged, with meaningful contributions and
active discussions on the mailing list. JDK17 support for the next release
will be a huge accomplishment given the dependencies. Requires an Apache Tez
release as well.

Community Health Score (Chi): 9.60 (Super Healthy)


-----------------------------------------
Attachment AD: Report from the Apache Hop Project  [Hans Van Akelyen]

## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Hop was founded 2021-12-15 (3 years ago)
There are currently 24 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Bart Maertens on 2021-12-15.
- No new committers. Last addition was Sergio De Lorenzis on 2024-06-11.

## Project Activity:
Since the last report, we have done 2 releases: 2.11.0 and 2.12.0. Our current
activity is stability, bug fixing and code documentation/cleanup.

## Community Health:
Enabeling GitHub discussions was a good move, we have more interaction there
with community members than on the mailing lists. In the past quarter, we have
seen a decrease in contributions, but can be explained due to the holiday
season.


-----------------------------------------
Attachment AE: Report from the Apache Hudi Project  [Vinoth Chandar]

## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Hudi was founded 2020-05-19 (5 years ago)
There are currently 40 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Sagar Sumit on 2023-11-05.
- No new committers. Last addition was Vova Kolmakov on 2024-09-13.

## Project Activity:
The community has been actively working on expanding the Hudi ecosystem with
significant progress in both the core Java implementation and the Rust/Python
ecosystem.

Hudi-rs 0.3.0 was released, adding more APIs to support Merge-On-Read (MOR)
table, file group reading and incremental queries, moving towards a set of
standardized APIs for query engine integrations.

Following the major milestone of Hudi 1.0 GA release in December 2024, Hudi
1.0.1 patch release was also published to stabilize the 1.0 milestone release
and improve user adoption.

## Community Health
We continue to see steady growth in community engagement on GitHub, with
active participation in code contributions and discussions. The dev and users
lists serve as primary channels for low-bandwidth communication, while GitHub
issues continue to be the main engagement model for community support.

The PMC started a series of developer sync calls
(https://hudi.apache.org/contribute/developer-sync-call/) to share the latest
 development of Hudi, discussing RFCs, and help developers to start
 contributing. This initiative aims to lower the barrier to entry for new
 contributors and facilitate deeper technical discussions within the
 community.


-----------------------------------------
Attachment AF: Report from the Apache Iceberg Project  [Ryan Blue]

## Description:
Apache Iceberg is a table format for huge analytic datasets that is designed
for high performance and ease of use.

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Iceberg was founded 2020-05-19 (5 years ago)
There are currently 34 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Amogh Jahagirdar on 2024-08-12.
- Huaxin Gao was added as committer on 2025-02-06
- Scott Donnelly was added as committer on 2024-12-12

## Project Activity:

Releases:
- Java 1.7.1 was released on 2024-12-06
- Java 1.8.0 was released on 2025-02-13
- Java 1.8.1 was released on 2025-02-28
- PyIceberg 0.8.1 was released on 2024-12-06
- PyIceberg 0.9.0 was released on 2025-03-06
- Rust 0.4.0 was released on 2024-12-23
- Go 0.1.0 was released on 2024-11-18

Java:
- License cleanup to ensure all distributed source and binaries are compliant
- Ongoing work to implement the v3 format before adoption
- Deletion vectors have been added
- Default value support was implemented
- Readers and writers for unknown, timestamp(9), and variant are committed
- Expression support for filtering on shredded variant metrics was completed
- Spark support for Datafusion Comet integration
- Added support for v3 row lineage to api/core
- Added InternalData to allow using columnar formats for table metadata

PyIceberg:
- Support for upsert operations
- Added residuals for scan tasks
- Use partition values from metadata
- Support for reading v3 DVs
- Write support for bucket and truncate transforms

Rust:
- Support for reading puffin file metadata
- Added manifest metadata table

Go:
- Added create/commit table support
- Completed commit updates/requirements for REST Catalog
- Add support for register table
- Add view support
- Add listing pagination support
- Improved manifest scanning

C++
- Added Schema and Types
- New language repository!

## Community Health:

The community has seen new first-time contributors across all projects with
recent releases including:
- Java: 37 new contributors as of 1.8.1 release
- Python: 33 new contributors as of 0.9.0 release
- Rust: 17 new contributors as of 0.4.0 release

This quarter also saw a 20% increase in the number of contributors.

The community has self-organized a significant number of Iceberg-focused
meetups spanning the globe with recent meetups in the following locations:
- Austin, TX
- Palo Alto, CA
- San Francisco, CA
- Seattle, WA
- Singapore
- Tokyo, Japan
- Hyderabad, India

The PMC will discuss and document guidelines for using the trademark to make it
easier for meetups to happen while meeting the ASF requirements.

A second Iceberg Summit will be April 8th & 9th 2025. It combines in-person
and virtual events.

Last, I want to clarify that what I said on PR 11670 was this:
> Right now, we're focusing on describing how the community operates, rather
> than discussing how it might operate in the future.


-----------------------------------------
Attachment AG: Report from the Apache Incubator Project  [Justin Mclean]

# Incubator PMC report for March 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 32 podlings incubating. In February, podlings executed
four distinct releases, and one IP clearance occurred. Several
incubating proposals have been discussed on the mailing list, and we have
one podling called Iggy. No podlings have retired, but a couple are talking
about it.
Baremaps, Gravitino, Toree and Training are close to graduation. A few
podlings failed to report and will be asked to report next month.

Conversations on the list have been chiefly about releases. There was a
conversation about performing trademark name searches early at the start of
the incubator process to ensure that polling names are not rejected close
to graduation.

A few podlings needed to update their data files to indicate that they had
graduated.

There is ongoing discussion on several new potential incubating projects,
and we have four proposals being worked on.

## Community

### New IPMC members:
  - None

### People who left the IPMC:
  - None

## New Podlings
 - Iggy

## Podlings that failed to report, expected next month
  - Iggy
  - Otava
  - PonyMail
  - Teaclave

## Graduations
  - Uniffle

  The board has motions for the following:

  - None

## Releases

  The following releases entered distribution during the month of
  March:
  - Baremaps 0.8.2
  - Fury 0.10.0
  - Polaris 0.9.0
  - Wayang 1.0.0

## IP Clearance
  - Cassandra Cluster Manager (CCM)

## Legal / Trademarks
  - N/A

## Infrastructure
  - N/A

## Table of Contents
[Baremaps](#baremaps)
[Cloudberry](#cloudberry)
[Gravitino](#gravitino)
[ResilientDB](#resilientdb)
[KIE](#kie)
[Nemo](#nemo)
[OpenServerless](#openserverless)
[OzHera](#ozhera)
[Polaris](#polaris)
[Teaclave](#teaclave)
[Training](#training)
[Wayang](#wayang)

--------------------
## Baremaps

Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.

Baremaps has been incubating since 2022-10-10.

### Three most important unfinished issues to address before graduating:

  1. 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?

  No.

### How has the community developed since the last report?

  Since the December release in 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 February release summarizes well the latest developments:
  https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [X] Nearing graduation
  - [ ] Other:

### Date of last release:

  2025-02-26

### When were the last committers or PPMC members elected?

  Sébastien Riollet in June 2024.

### Have your mentors been helpful and responsive?

  Yes, the mentors are helpful.

### Is the PPMC managing the podling's brand / trademarks?

  Yes.

### Signed-off-by:

  - [ ] (baremaps) Bertrand Delacretaz
     Comments:
  - [ ] (baremaps) Martin Desruisseaux
     Comments:
  - [X] (baremaps) Julian Hyde
     Comments: Project is indeed near graduation. I recommend that
       they start graduation discussions on dev@.
       My takeaway from the recent release is diversity of
       contributors; 12 issues fixed by 6 contributors is an
       indication that the project is becoming more broad-based.
  - [X] (baremaps) Calvin Kirs
     Comments:  We're going to start assessing what still needs to be done
before graduation.
  - [ ] (baremaps) George Percivall
     Comments:
  - [ ] (baremaps) Martin Desruisseaux
     Comments:

### IPMC/Shepherd notes:

--------------------

## Cloudberry

Cloudberry is an advanced and mature open-source Massively Parallel
Processing (MPP) database, derived from the open-source version of
Pivotal Greenplum Database®️ but built on a more modern PostgreSQL 14
kernel, whereas Greenplum is based on PostgreSQL 12. This upgrade
brings enhanced enterprise capabilities, making Cloudberry well-suited
for data warehousing, large-scale analytics, and AI/ML workloads.

Cloudberry has been incubating since 2024-10-11.

### Three most important unfinished issues to address before graduating:

  1. Complete the source code cleanup to ensure ASF compliance.
  2. Publish the first Apache release following ASF release processes.
  3. Expand the contributor base and community engagement to ensure
long-term sustainability.

### Are there any issues that the IPMC or ASF Board need to be aware of?
  No.

### How has the community developed since the last report?

  - Mailing List Activity: 63 messages on the Dev mailing list in Feb 2025,
  covering technical discussions and roadmap planning.
  - Slack Activity: 8 new threads on the `#general` channel, though no new
  users joined.
  - GitHub Discussions: 27 new discussions since Cloudberry entered
  incubation in October 2024, reflecting engagement on technical topics and
  project direction.
  - Outreach & Advocacy:
  - Promoted Cloudberry ecosystem updates (e.g., DBeaver and WAL-G support).
  - Encouraged community members to submit conference sessions.
  - Meetup: A Cloudberry Meetup hosted by HashData in Shanghai attracted
  40+ attendees.
  - Recent Webinar: Apache Cloudberry™ (Incubating): The Latest Database
  for SQL at Scale
    - Event: Postgres World Webinar Series 2024
    - Date: December 10, 2024
    - Webinar Link: https://s.apache.org/slop6
  - Upcoming Conference Talk: From Greenplum to Apache Cloudberry
    - Event: PostgresConf Global 2025
    - Date: March 20, 2025, 10:30 EDT
    - Conference Link: https://s.apache.org/6ufdx

### How has the project developed since the last report?

  - Codebase Updates:
  - Integrated key contributions from the open-source Greenplum project
  while aligning them with Cloudberry’s roadmap.
  - Ongoing source code cleanup to ensure ASF compliance and prepare for
  the first official release.
  - Continuous Integration & Testing:
  - CI is now in place for the Rocky Linux 9 platform.
  - Testing has been extensively expanded since incubation, covering all
  PRs and main branch submissions.
  - GitHub Actions Workflows leverage automated builds for required
  resources (e.g., Docker containers).
  - The developer community has played a key role in shaping the CI and
  development processes, contributing feedback, enhancements, and best
  practices.
  - We have adopted an Infrastructure as Code (IaC) methodology to manage
  CI resources efficiently.
  - Potential Integration of Apache MADlib:
  - There has been discussion within the community about potentially
  incorporating Apache MADlib into Cloudberry.
  - Current interest appears to be low, but we will hold an official vote
  on this topic soon to determine the next steps.
  - Documentation Improvements:
  - Added and updated technical documentation to improve onboarding for new
  users and contributors.

### 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?

  No new committers or PPMC members have been elected yet.

### Have your mentors been helpful and responsive?

  Yes, a lot of help on the license.

### Is the PPMC managing the podling's brand / trademarks?

  Yes.

### Signed-off-by:

  - [ ] (cloudberry) Roman Shaposhnik
     Comments:
  - [ ] (cloudberry) Willem Ning Jiang
     Comments:
  - [X] (cloudberry) Kent Yao
     Comments: LGTM

### IPMC/Shepherd notes:
  [PJF] Progress looks ok but there is still some missing data for the
  Incubator status https://incubator.apache.org/clutch/cloudberry.html

--------------------

### 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.Preparing the new repo folowing ASF policy to be released.

### 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?

  1. We are preparing a release for the Repo
  [ResVault](https://github.com/apache/incubator-resilientdb-resvault) and
  [ResilientDB-GraphQL](https://github.com/apache/incubator-resilientdb-graphql)
  which are built on ResilientDB platform to provide interfaces to access
  the blockchain system.
  2. We developed new smart contract features within current version on
  ResilientDB platform.

### 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:

  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:

--------------------
## Gravitino

Gravitino is a high-performance, geo-distributed, and federated metadata
lake designed to manage metadata seamlessly across diverse data sources,
vendors, and regions. Its primary goal is to provide users with unified
metadata access for both data and AI assets.

Gravitino has been incubating since 2024-06-04.

### Three most important unfinished issues to address before graduating:

  1. Fix all the potential license issues.
  2. Release a version with non-WIP disclaimer.
  3. Fill out the maturity model.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  No.

### How has the community developed since the last report?

  1. The Gravitino community added two new committers: Can Cai, Qian Xia.
  2. The Gravitino community added two PPMC members: He Qi, Hui Yu.

### How has the project developed since the last report?

  1. A new version 0.8.0-incubating has released.
  2. Reaching to 153 commmitters and with 5+ commits per day.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [X] Community building
  - [X] Nearing graduation
  - [ ] Other:

### Date of last release:

  2025-01-24

### When were the last committers or PPMC members elected?

  2025-03-13

### Have your mentors been helpful and responsive?

  The mentors are helpful, and there are no special issues that need to be
  addressed.

### Is the PPMC managing the podling's brand / trademarks?

  Yes, there's no branding issue, and 3rd parties use the name and brand
  correctly.

### Signed-off-by:

  - [ ] (gravitino) Daniel Dai
     Comments:
  - [ ] (gravitino) Junping Du
     Comments:
  - [X] (gravitino) Justin McLean
     Comments:
  - [ ] (gravitino) Shaofeng Shi
     Comments:
  - [ ] (gravitino) Larry McCay
     Comments:
  - [X] (gravitino) Jean-Baptiste Onofré
     Comments:

### IPMC/Shepherd notes:

--------------------
## KIE

KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.

KIE has been incubating since 2023-01-13.

We wrote a report last month, nothing has changed.

### Three most important unfinished issues to address before graduating:

  1. Build the community
  2. Make sure sure our dependencies are in compliance
  3. More releases

### 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?

  No change since last month

### How has the project developed since the last report?

  No meaningful changes since last month

### 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-11

### When were the last committers or PPMC members elected?

  A couple of months back.

### Have your mentors been helpful and responsive?

  Pretty good so far.

### Is the PPMC managing the podling's brand / trademarks?

  N/A

### Signed-off-by:

  - [ ] (kie) Brian Proffitt
     Comments:
  - [ ] (kie) Claus Ibsen
     Comments:
  - [ ] (kie) Andrea Cosentino
     Comments:

### IPMC/Shepherd notes:

--------------------
## Nemo

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

### Three most important unfinished issues to address before graduating:

  1. Remove the dependency on REEF
  2. Revitalize the community
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?
  - There is no activity in the community.

### How has the community developed since the last report?
  - There has been no notable activity since the last report.

### How has the project developed since the last report?
  - There has been no notable activity since the last report.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [ ] Nearing graduation
  - [X] Other:

### Date of last release:

  2022-09-22

### When were the last committers or PPMC members elected?
  September 28, 2021

### Have your mentors been helpful and responsive?

  N/A

### Is the PPMC managing the podling's brand / trademarks?

  Yes

### Signed-off-by:

  - [ ] (nemo) Hyunsik Choi
     Comments:
  - [X] (nemo) Byung-Gon Chun
     Comments:
  - [X] (nemo) Jean-Baptiste Onofré
     Comments:  Following the roll call, I think we should consider
     retirement.
  - [ ] (nemo) Markus Weimer
     Comments:

### IPMC/Shepherd notes:

  [PJF] It is sad to say but this podling looks like it is moribund. There
  is no active traffic on the mailing lists and there only a small response
  to a recent roll call
  (https://lists.apache.org/thread/5y2m4nglbh3qwgb7nkvqj6r4v4nx37rx)
  [JBO] Agree with PJ, according to the roll call, we should consider
  retirement.

--------------------
## 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. Continue the process of align documentation, since there are still
     several parts that neeed a review.
  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. The Apache OpenServerless and AI course - currently in Italian - is
     underway: it has involved many people and is a model to be proposed
     also in English with respect to a larger community.
  2. We're evaluating sessions to support those who need it in the
     installation of the development environment.
  3. Finally, we are trying to involve people in the development by
     proposing them to take charge of some open tasks on GitHub.

### How has the project developed since the last report?

  1. Closed 8 issues. Opened 3 new issues.
  2. We improved the Kubernetes operator, further optimizing the image
     size and introducing some new features.
  3. Introduced some new features also in the openserverless-task project.
  4. We improved the stability of the functions that affect the Apache
     OpenServerlesss IDE

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [X] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  None

### When were the last committers or PPMC members elected?

  2024-08-22

### Have your mentors been helpful and responsive?

  Yes, and we renew our thanks to all of them for their continued support
  in developing this project, allowing us to meet the required standards.

### Is the PPMC managing the podling's brand / trademarks?

  https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-222 approved

### Signed-off-by:

  - [ ] (openserverless) Bertrand Delacretaz
     Comments:
  - [ ] (openserverless) Enrico Olivelli
     Comments:
  - [ ] (openserverless) François Papon
     Comments:
  - [X] (openserverless) JB Onofré
     Comments:  Good progress! We should promote OpenServerless more to
grow the community.
  - [X] (openserverless) PJ Fanning
     Comments: Steady progress

### 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?
  Solved the existing problem of the website not complying with the ASF
standard.
  Merged 24 PRs.

### How has the project developed since the last report?
  Complete the version release revision work and initiate the version
release voting process.
  Completed log parsing related optimization.

### 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. Prepare 1.0.0 release including binary distribution
  2. Grow the community

### Are there any issues that the IPMC or ASF Board need to be aware of?

  No

### How has the community developed since the last report?

  Regarding the users community:
  - on Slack (#general channel), in February, we had questions from 11 new
  users, evaluating Polaris. These users are not active on the dev mailing
  list (only Slack).
  - on GitHub Issues, in February, we had 2 new issues created by non
  committers users, and non affiliated to initial committed companies. Some
  users are the same active on Slack (for instance
  https://github.com/apache/polaris/issues/996)

  Regarding the contributors community:
  - in February, we had 7 PRs from 5 new contributors (individual
  contributors, not affiliated to companies already active in Polaris)
  - in February, we had several GitHub issues and PRs created by 3 new
  contributors from Snowflake and a new contributor from Dremio.

  In February, we had several Community Meetings (recorded and shared on
  the dev mailing list and website):
  - 2 Polaris Community Meetings
  - Discussion about the Policy Management proposal
  - Discussion about Polaris Persistence improvement proposal

  On these meetings, we were pleased to see several new people (around 15
  people show up for the first time in February).

  We continue to promote Polaris in order to grow our community. We
  strongly believe 1.0.0 release (with the binary distributions) will help to
  grow even faster our community.

### How has the project developed since the last report?

  0.9.0 has been released. This release is the first one on the project,
  only including source distribution.
  We are now working on 1.0.0 release that will include binary
  distributions.

  We published a roadmap proposal
  (https://github.com/apache/polaris/discussions/1028), and we added a
  1.0-blocker label on GH Issues.

  In February, we had 3 new proposals in discussion (relayed on the dev
  mailing list):
  - Persistence layer improvement (https://github.com/apache/polaris/issues/985)
  - Policy Management (https://github.com/apache/polaris/issues/999)
  - Generic Table Support (https://github.com/apache/polaris/issues/1048)

  We are now focusing on 1.0.0 preparation, including fixes and the
  persistence layer improvement.

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2025-02-25

### When were the last committers or PPMC members elected?

  Last committer: Dennis Huo and Dmitri Bourlatchkov elected on 2024-12-23

### Have your mentors been helpful and responsive?
  Yes, helpful in release and report review.

### Is the PPMC managing the podling's brand / trademarks?
  Polaris PPMC is working with 3rd parties willing to use Polaris
  brand/trademarks, according to
  https://incubator.apache.org/guides/publicity.html and
  https://incubator.apache.org/guides/branding.html.

### Signed-off-by:

  - [ ] (polaris) Bertrand Delacretaz
     Comments:
  - [ ] (polaris) Holden Karau
     Comments:
  - [ ] (polaris) Kent Yao
     Comments:
  - [X] (polaris) Ryan Blue
     Comments: I think "working towards first release" can be unchecked.
     Thanks for the additional detail on community growth!
  - [X] (polaris) JB Onofre
     Comments: I'm looking forward 1.0.0 release !

### IPMC/Shepherd notes:

--------------------
## Toree

Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.

Toree has been incubating since 2015-12-02.

### Three most important unfinished issues to address before graduating:

  1.Increase active contributors

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None

### How has the community developed since the last report?

  Slow activity with discussions about 0.6 release before incorporating
  Scala 2.13 support

### How has the project developed since the last report?

  Few prs around Scala 2.13 and other small enhancements
  Updates to remove Google Analytics from website

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [X] Nearing graduation
  - [ ] Other:

### Date of last release:

  2022-04-11

### When were the last committers or PPMC members elected?

  - Cheng Pan was added to the PPMC on 2023-08-28

### Have your mentors been helpful and responsive?

  None

### Is the PPMC managing the podling's brand / trademarks?

  No trademark issues

### Signed-off-by:

  - [X] (toree) Luciano Resende
     Comments:  The podling should push for release and start graduation
     process
  - [ ] (toree) Ryan Blue
     Comments:
  - [ ] (toree) Weiwei Yang
     Comments:

### IPMC/Shepherd notes:

--------------------
## Training

The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various Apache
and non-Apache target projects.

Training has been incubating since 2019-02-21.

### Three most important unfinished issues to address before graduating:

  1. Name clearance
  2. n/a
  3. n/a

### 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?

  One new contributor in the past quarter.

### How has the project developed since the last report?

  We are working with several projects to improve, or create, their sample
  training decks.

  A new contributor is working on github actions to automatically build
  content to lower the barrier to entry.

  The podling is discussing graduation.

### 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/04

### When were the last committers or PPMC members elected?

  August 2024

### Have your mentors been helpful and responsive?

  Mentors have been helpful in discussions.

### Is the PPMC managing the podling's brand / trademarks?

  Attempting to start a name search.

### Signed-off-by:

  - [X] (training) Craig Russell
     Comments:
  - [ ] (training) Christofer Dutz
     Comments:
  - [X] (training) Justin Mclean
     Comments:
  - [ ] (training) Lars Francke
     Comments:

### IPMC/Shepherd notes:

--------------------
## Wayang

Apache Wayang is a layered ML framework that connects your applications to
various data processing platforms,
automatically translating your requests into a common format and optimizing
tasks for each platform.
Its flexible design also makes it easy to add new features or support
additional technologies dynamically.

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?

  Slowly growing

### How would you assess the podling's maturity?
  Please feel free to add your own commentary.

  - [X] Initial setup
  - [X] Structure setup, voting established
  - [ ] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2025-09-02

### 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, and approved.

### Signed-off-by:

  - [ ] (wayang) Christofer Dutz
     Comments:
  - [ ] (wayang) Lars George
     Comments:
  - [ ] (wayang) Bernd Fondermann
     Comments:
  - [X] (wayang) Jean-Baptiste Onofré
     Comments:  I don't think Wayang is in initial setup phase. I would say
     more community building.

### IPMC/Shepherd notes:


-----------------------------------------
Attachment AH: Report from the Apache IoTDB Project  [Xiangdong Huang]

## Description:
The mission of Apache IoTDB is the creation and maintenance of software related
to an IoT native database with high performance for data management and analysis

## Project Status:
Current project status: Ongoing with high activity.
Issues for the board: no.

## Membership Data:
Apache IoTDB was founded 2020-09-16 (4 years ago)
There are currently 71 committers and 30 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 Qingxin Feng on 2024-06-29.
- Xiangpeng Hu was added as committer on 2025-02-24
- Zhao Xin was added as committer on 2024-12-20
- Zhihao Shen was added as committer on 2025-02-26
- Zikun Ma was added as committer on 2025-02-27

## Project Activity:
- Recent releases: IOTDB-2.0.1-beta was released on 2025-02-16. IOTDB-1.3.3
  was released on 2024-11-20. IOTDB-1.3.2 was released on 2024-07-01.

- Main work of project: The first official version of the table model,
  2.0.1-beta has been released, including basic read and write functionality
  and future changes will ensure compatibility with the released version.
  Enhancing the security of the table model with the implementation of user
  management and permission control. User definied Scalar function and
  aggregate function has been added to the table model, and user defined table
  function is working in progress. Adding a trusted address configuration
  parameter for URI to prevent untrusted JAR packages from being loaded into
  the IoTDB process. The system’s stability has been further enhanced by
  fixing a series of memory leak-related bugs, such as memory leaks during
  SQL-based writes and inaccurate memory estimation when querying large text
  objects.

## Community Health:
Overall community health is good.
- A live stream was held online to introduce the table model, highlighting the
  features of the table model introduced in the 2.x series, its differences
  from the tree model, and the future version roadmap.
- dev@iotdb.apache.org had a 15% increase in traffic in the past quarter (76
  emails compared to 66), we discussed the release and version of table model
  of IoTDB.
- 1184 PRs opened on GitHub, past quarter (-34% change), due to the Chinese
  New Year holiday, the number of PRs has decreased.


-----------------------------------------
Attachment AI: Report from the Apache Jackrabbit Project  [Marcel Reutegger]

## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.

Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class websites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications, and it
is not a reference implementation.

## Project Status:
Current project status: Ongoing with moderate activity

Issues for the board: none

## Membership Data:
Apache Jackrabbit was founded 2006-03-15 (19 years ago).

There are currently 59 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is 1:1, because all committers automatically
become PMC members.

Community changes, past quarter:
- No new PMC members. Last addition was Nuno Santos on 2023-11-14.
- No new committers. Last addition was Nuno Santos on 2023-11-13.

## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.

Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.

The team is further reducing usage of Google's Guava library and
Jackrabbit Oak is now using Java features where possible. The long
term goal is to remove the dependency on Guava.

Work on migrating Jackrabbit Oak from Azure SDK 8.x to 12.x continues.
Azure SDK 8.x is no longer supported and a migration to 12.x is now
required.

## Community Health:
The project is generally healthy with a continuous stream of traffic
mostly on JIRA issues and GitHub pull requests reflecting activity of
the respective component.

The release of Jackrabbit Oak 1.76.0 had to be canceled due to a
regression reported by downstream users. This sparked a discussion
about lack of transparency because the details of the regression were
not fully understood by the community. After reverting changes that
were suspected to cause the regression, the release was re-started.

Commit activity is moderate, mirroring the activity on the
JIRA issues and the desire of the individual contributors to bring
features and improvements in for the next Jackrabbit Oak release.

## Releases:

- jackrabbit-oak-1.74.0 was released on 2025-01-16
- jackrabbit-oak-1.76.0 was released on 2025-02-13

## JIRA activity:

- 305 JIRA tickets created in the last 3 months
- 252 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AJ: Report from the Apache Karaf Project  [Jean-Baptiste Onofré]

## Description:
The mission of the Apache Karaf project is the creation and maintenance of
open-source software related to a generic platform providing higher level
features and services specifically designed for creating OSGi-based servers for
distribution at no charge to the public.

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Karaf was founded 2010-06-16 (15 years ago)
There are currently 32 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Robert Varga on 2023-10-31.

## Project Activity:
[Apache Karaf 4.4.7 has been released on 2025-01-24.

Apache Karaf 4.5.0 will be a new maintenance branch, with updated versions and
fixes.

We also decided to move to GitHub Issues and GitHub Actions for Karaf (see the
community health section).

Karaf Decanter moved to GitHub Issues and GitHub Actions. We are now preparing
a new Decanter release.

## Community Health:
We had a community discussion about the future of Karaf (4.5.x and 5.0.x):

https://lists.apache.org/thread/2v68pkdn089285sodolxgt6z4pgbnpx9

The community considers the changes are significant enough to start the 5.0.0
branch:
- a new "simple" features service (flat/simple resolver)
- new Karaf core services as alternatives to Pax * modules (replacing Pax
  Logging by karaf-logging, replace Pax URL by karaf-url (with just the JDK
  HTTP Client), ...
- more Karaf distributions, opinionated about the content: minimal (as today
  but without Pax * cooupliing), simple (with the simple features service, the
  alternatives to Pax *, ..), standard (the same as today but with updated
  versions, we will discuss to "promote" simple as standard for Karaf 4.6.x),
  integration (based on standard with Camel, ActiveMQ, ...), cloud (based on
  simple with opentelemetry, k8s support, ..., by default)


-----------------------------------------
Attachment AK: Report from the Apache Kibble Project  [Sharan Foga]

## Description:
The mission of Apache Kibble is the creation and maintenance of software
related to an interactive project activity analyzer and aggregator

## Project Status:
Current project status: Dormant, no real activity
Issues for the board: None

## Membership Data:
Apache Kibble was founded 2017-10-18 (7 years ago)
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.

Community changes, past quarter:
- No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
- No new committers. Last addition was Kaxil Naik on 2021-02-21.

## Project Activity:
The project has not yet made a release.

The project has had little or no activity since our last report. We did reach
out to VP Tooling to see if Kibble could be a potential project under its
umbrella. The feedback was that it might not be appropriate. Unless we do find
people willing to develop the project then we seriously need to consider
moving to the attic.

## Community Health:
The project community has always been small and we have never grown to a
sustainable size. I will make a final appeal to the community to see if there
are volunteers willing to take on a role to develop or move the project
forward. If not then we will propose a vote to retire the project and move it
to the attic.


-----------------------------------------
Attachment AL: Report from the Apache Kvrocks Project  [Mingyang Liu]

## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, with support of rich data
structures like Redis.

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Kvrocks was founded 2023-06-21 (2 years ago)
There are currently 26 committers and 12 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 Xuwei Fu on 2024-03-22.
- No new committers. Last addition was SiLe Zhou on 2024-10-19.

## Project Activity:
Apache Kvrocks has just released two versions in the past quarter, 2.11.0 and
2.11.1, where 2.11.1 is a patch release and includes one security fix of
CVE-2025-25069, while 2.11.0 includes a big feature, Kvrocks Search, for
secondary indexing and complex queries.

Currently the community is focusing on adding the support of the TDigest data
structure. Besides, we are participating GSoC to seek more
contributers and students to join the development of Kvrocks.

Also, Apache Kvrocks Controller has released version 1.1.0 in the past
quarter, with the support of an embedded Raft storage.

## Community Health:
In the past quarter, the opened PRs have -6% decrease and issues have -35%
decrease. But I am optimistic about this since we are participating GSoC (and
also OSPP in the near future) so more developers will be involved.
Also, there is at least one developer that we will open a committer vote soon.


-----------------------------------------
Attachment AM: Report from the Apache Kyuubi Project  [Kent Yao]

## Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses

## Project Status:
Current project status: Ongoing w/ moderate activity
Issues for the board: None

## Membership Data:
Apache Kyuubi was founded 2022-12-21 (2 years ago)
There are currently 29 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Binjie Yang on 2024-07-05.
- He Zhao was added as committer on 2025-01-02

## Project Activity:

Software development activity:
  - v1.10.1 was released on 2024 Dec 26
  - Apache Paimon authz support is in progress
  - Apache Spark 4.0 support is in progress

Meetups and Conferences:
  - One of our PMC member attended DataFunsummit2024 on 2024 Dec 14


## Community Health:

Some new contributors are helping with new features like Apache Paimon authz,
Apache Spark 4.0 support, the community is still friendly, and welcoming new
members. The statistics might be lower than usual due to the long holiday
season.


-----------------------------------------
Attachment AN: Report from the Apache Libcloud Project  [Tomaž Muraus]

## Description:
The mission of Libcloud is the creation and maintenance of software related to
Unified interface to the cloud

## Project Status:
Current project status: The project has received some activity on GitHub, but
we are struggling and lacking active maintainers.

Issues for the board: See section below on lack of active
maintainers / committers.

## Membership Data:
Apache Libcloud was founded 2011-05-19 (14 years ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Moraitis on 2021-05-07.
- No new committers. Last addition was Dimitris Moraitis on 2021-05-02.

## Project Activity:
In January, Justin Mclean performed a roll call, and we had difficulty reaching
enough 0's or +1's. I personally responded with 0 but continue to monitor the
project, focusing on security issues and dependency updates.

Last release was v3.8.0 in August, 2023.

We are currently wrapping up the 3.9.0 release, which should be out shortly.

Although I was less active in recent months due to moving and personal matters,
now that things have settled, I aim to dedicate a few hours each week to
project maintenance, ensuring dependencies and other things are kept up to date.

Additionally, the library is used by various upstream projects and is also
packaged and available in various package managers so we are trying to do
our best to keep things up to date for the users and package maintainers.

Just recently we have received a helpful feedback on obscure packaging bug
with 3.8.0 release which will be fixed in 3.9.0.

## Community Health:
While we have received some contributions, we continue to struggle with
attracting and retaining active maintainers (committers/PMC members) to review
community PRs.

In the near future, I plan to write a post on our blog asking and looking for
active contributors and maintainers to help keep the project alive and ensure
minimum required oversight.


-----------------------------------------
Attachment AO: Report from the Apache Linkis Project  [Shuai Di]

## Description:
The mission of Apache Linkis is the creation and maintenance of software
related to a distributed computation middleware to facilitate connection,
governance and orchestration between the upper applications and the
underlying data engines.

## Project Status:
Current project status: Ongoing.
Issues for the board: There are no issues requiring board attention.

## Membership Data:
Apache Linkis was founded 2022-12-21 (Two years ago)
There are currently 38 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.

Community changes, past quarter:
- No new PMC. Last addition was Jie Cheng on 2024-01-28.
- New committers. Last addition was King hao on 2024-12-04.

## Project Activity:

The Apache Linkis version 1.7.0 was released on 2025-01-10.
Mainly includes the following features:
- Spark, hive, and shell tasks support cross-cluster submission.
- Support task pre-diagnosis, including syntax errors, join keyword mismatches
- Concurrent engine supports graceful exit.
- Added Monitor service, supporting data cleanup, disk cleanup, user-mode alarms

The Apache Linkis version 1.8.0 is under development and is
expected to be released in June 2025. Mainly includes the following features:
- Pre - task diagnosis and support for bad job interception,
as well as post - task diagnosis reports.
- Data source display support for Ranger.
- Support for setting priorities for Linkis tasks.

## Community Health:
Overall community health is good.
- 12 PRs closed on GitHub, past quarter.
- 19 issues closed on GitHub, past quarter.


-----------------------------------------
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 activity
Issues for the board: There are no issues for the board

## Membership Data:
Apache Logo Development was founded 2024-08-20 (7 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-27.
- No new committers were added.

## Project Activity:
The first round poll for the best suited logo candidate has begun, and will
end on March 20th. Once we have the results from that poll, we will condense
the list of candidates for the second round and look at refining some of the
candidates to make them more viable for the final round(s).

## Community Health:
No changes to committee size. Overall the project is working as intended.
Nothing to report here, really.


-----------------------------------------
Attachment AQ: Report from the Apache Lucene Project  [Dawid Weiss]

## Description:
The mission of Lucene is the creation and maintenance of software related to
Search engine library

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Lucene was founded 2005-01-19 (20 years ago)
There are currently 101 committers and 68 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Ben Trent on 2024-02-22.
- No new committers. Last addition was Armin Braun on 2024-07-25.

## Project Activity:
- 10.1.0 was released on 2024-12-20.
 - https://lucene.apache.org/core/10_1_0/changes/Changes.html
 - This release focuses mostly on optimizations and bug fixes following the
   10.0.0 release.
- 9.12.1 was released on 2024-12-13.
 - https://lucene.apache.org/core/9_12_1/changes/Changes.html
 - This is a bugfix release correcting regressions introduced in 9.12.0.

## Community Health:
Community interactions remain healthy, with good activity in all areas
(discussions on the mailing list, github pull requests and discussions, etc).

Committer and PMC membership has been a bit stagnant. A new committer has been
invited this week and has accepted the invitation.

There is a notable decrease in mailing list traffic (48%) which can be
probably explained by the Winter holiday season (?).

The number of pull requests and commits remains steady and consistent with the
past. There were 179 commits to the main branch and 339 commits overall
between 2024-12-12 and 2025-03-05. 79 github issues were opened in that
period, and 48 of them were closed. The number of pull requests was 194, of
which 163 were closed.

We've noticed that project code stats on reporter.apache.org are incorrect and
we filed a corresponding jira ticket with community-dev. For the time being,
code stats are computed using a workflow polling github APIs [1].

Overall, the project seems to be in good shape.

[1] https://github.com/apache/lucene/actions/workflows/activity-report.yml


-----------------------------------------
Attachment AR: Report from the Apache Lucene.Net Project  [Shad Storhaug]

## Description:
The mission of Lucene.Net is the creation and maintenance of software related
to Search engine library targeted at .NET runtime users.

## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None

## Membership Data:
Apache Lucene.Net was founded 2012-08-14 (13 years ago)
There are currently 16 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 8:7.

Community changes, past quarter:
- No new PMC members. Last addition was Ron Clabo on 2022-03-02.
- No new committers. Last addition was Ron Clabo on 2021-06-02.

## Project Activity:
Apache Lucene.Net delivered the latest 4.8.0-beta00017 release on 2024-10-29.
Activity continues towards a final 4.8.0-beta00018 release, although activity
has slightly decreased since the last report. As of the last report, we were
46% complete by issue count towards the next release; currently we are about
80% complete by issue count once the open PRs are reviewed and merged, and
necessary dependencies are updated. While we hoped to have the release done by
the end of the first quarter of 2025, it now looks like the second quarter is
more likely.

We also have launched a new repository (lucenenet-codeanalysis-dev) for
contributor-use-only Roslyn analyzers to help detect code problems in an
automated way in PRs, as well as provide automated fixes for them in the
contributors' IDEs.

## Community Health:
Nearly all metrics indicate a slower quarter than last:
- dev@lucenenet.apache.org had a 29% decrease in traffic in the past quarter
  (402 emails compared to 564)
- 36 commits in the past quarter (-79% change)
- 3 code contributors in the past quarter (-62% change)
- 38 PRs opened on GitHub, past quarter (-36% change)
- 36 PRs closed on GitHub, past quarter (-41% change)
- 30 issues opened on GitHub, past quarter (-37% change)
- 37 issues closed on GitHub, past quarter (-21% change)

Despite this slowdown, we hope that getting the next release complete and
announcing to the community that we are closer to a final release will help
spur more activity.


-----------------------------------------
Attachment AS: Report from the Apache Mynewt Project  [Szymon Janc]

## Description:
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android

## Project Status:
Current project status: ongoing
Issues for the board: none

## Membership Data:
Apache Mynewt was founded 2017-06-21 (8 years ago)
There are currently 37 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Michał Górecki on 2024-06-27.

## Project Activity:
Work is ongoing in several areas, mainly improvements in BSP and MCU support.

Continued work on Nordic nRF54L15 support and Bluetooth 6.0 features (eg Channel
Sounding). There is also ongoing work on fixing NimBLE bugs that are affecting
Bluetooth Qualification (both host and controller).

Tentative plan for next release is June 2025.

## Community Health:
Core developers are active on regular basis. Most work is Bluetooth releated.
We see more interest from other projects in using NimBLE port.


-----------------------------------------
Attachment AT: Report from the Apache NetBeans Project  [Geertjan Wielenga]

## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environments, tooling platforms, and application
frameworks

## Project Status:
Current project status: Ongoing with moderate to high activity.
Issues for the board: None.

## Membership Data:
Apache NetBeans was founded 2019-04-16 (6 years ago)
There are currently 82 committers and 65 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.

Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2022-04-30.
- No new committers. Last addition was Tomas Hurka on 2023-05-24.

## Project Activity:
Apache NetBeans 25 was released on 2025-02-20.
Apache NetBeans 24 was released on 2024-12-10.

## Community Health:
- Stable contributions to each release, e.g., 26 contributors (3 new) for
  Apache NetBeans 25 and 22 contributors (6 new) for Apache NetBeans 24:
  - https://github.com/apache/netbeans/releases/tag/25
  - https://github.com/apache/netbeans/releases/tag/24
- dev@netbeans.apache.org had a 28% increase in traffic in the past quarter
  (211 emails compared to 164)
- users@netbeans.apache.org had a 18% increase in traffic in the past quarter
  (157 emails compared to 133)
- 195 commits in the past quarter (7% increase)
- 30 code contributors in the past quarter (30% increase)
- 91 issues opened on GitHub, past quarter (-30% change)
- 67 issues closed on GitHub, past quarter (24% increase)


-----------------------------------------
Attachment AU: Report from the Apache OFBiz Project  [Jacopo Cappellato]

## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.

## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.

## Membership Data:
Apache OFBiz was founded 2006-12-20 (18 years ago)
There are currently 60 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- No new PMC members. Last addition was Sebastian Tschikin on 2024-09-18.
- No new committers. Last addition was Ioan Eugen Stan on 2024-09-23.

## Project Activity:
* New releases:
** 18.12.18 was released on 2025-03-07.
* Security: With this release, we have fixed and announced one new
 vulnerability: CVE-2025-26865.
* Trademarks: there are no trademark related concerns at the moment.

## Community Health:
During the last quarter, community activity has remained steady, with regular
participation in mailing list discussions and consistent code contributions.
No new PMC members or committers have been invited, but new contributors have
joined the community.


-----------------------------------------
Attachment AV: Report from the Apache Olingo Project  [Michael Bolz]

## Description:
The Apache Olingo Project be and hereby is responsible for the creation and
maintenance of software related to providing an implemention of the OASIS OData
(Open Data Protocol) specifications, in server and client form;

## Project Status:
Current project status: Dormant
Issues for the board: no

## Membership Data:
Apache Olingo was founded 2014-03-19 (10 years ago)
There are currently 25 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Ramya Vasanth on 2019-04-15.
- No new committers. Last addition was Archana Rai on 2017-05-26.

## Project Activity:
Recent releases:
  - V4 5.0.0 was released on 2023-12-18.
  - 4.10.0 was released on 2023-10-22.
  - V2 2.0.13 was released on 2023-10-22.

The V2 feature release (version 3.0.0)
is on the way (March/April)
The V4 a maintenance release
will follow afterward.
Unfortunately, both got
delayed because of personal reason.

## Community Health:
Overall community health continues to be okay.
Activity on the mailing lists is on a low level.
There were a bit more contributions, and JIRA items.


-----------------------------------------
Attachment AW: Report from the Apache OpenDAL Project  [Hao Ding]

## Description:

OpenDAL is an Open Data Access Layer that enables seamless interaction with
diverse storage services.

OpenDAL's development is guided by its vision of One Layer, All Storage and
its core principles: Open Community, Solid Foundation, Fast Access, Object
Storage First, and Extensible Architecture.

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:

Apache OpenDAL was founded 2024-01-17 (a year ago)
There are currently 29 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- Lusheng Lyu was added to the PMC on 2025-01-09
- Wenchuang Gan was added as committer on 2024-12-12
- Shen Tianxiao was added as committer on 2025-02-24

## Project Activity:

OpenDAL has the following release since last report:

- v0.52.0 was released on 2025-02-24
- v0.51.2 was released on 2025-02-07
- v0.51.1 was released on 2025-01-13
- v0.51.0 was released on 2024-12-24

## Community Health:

### Are there any risks to the sustainability of a project?

OpenDAL is in excellent health at the moment. We merge about five PRs per day,
and our releases follow a stable pace.

### Is the PMC capable of responding to security issues and performing a
    release of its projects if needed?

Yes, as I demonstrated in the Project Activity, we release at least one
version per month and can release more if necessary. The PMC also does its
best to maintain good dependencies.

### Does the PMC need anything from the Foundation to improve on contributing
    to our mission of delivering software for the public good?

No requests for now.


-----------------------------------------
Attachment AX: Report from the Apache OpenNLP Project  [Jeff Zemerick]

## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache OpenNLP was founded 2012-02-14 (13 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Martin Wiesner on 2023-06-24.
- No new committers. Last addition was Atita Arora on 2023-02-28.

## Project Activity:
The project released version 2.5.3 on 2025-01-10 and will likely look to
release a new minor revision in the coming period. There have been commits
around updating dependencies and other maintenance tasks that will benefit
from a release.

## Community Health:
This period has had fewer code contributions and mailing list traffic than the
previous period. The community remains healthy.


-----------------------------------------
Attachment AY: Report from the Apache OpenWebBeans Project  [Mark Struberg]


-----------------------------------------
Attachment AZ: Report from the Apache Paimon Project  [Jingsong Lee]

## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Paimon was founded 2024-03-20 (a year ago)
There are currently 21 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- Junhao Ye was added to the PMC on 2025-02-25
- Xinyu Zou was added to the PMC on 2025-02-25
- Weijun Wang was added as committer on 2024-12-20

## Project Activity:

Software development activity:
- We released the PyPaimon 0.2.0 on 2024-12-19. Python SDK for Paimon.
- We released the release 1.0.0 on 2025-01-03.
- We released the release 1.0.1 on 2025-02-10.
- We have improved Iceberg compatibility, producing Iceberg snapshots.
- We are implementing REST Catalog, this is very beneficial for the ecology.

## Community Health:

Overall community health is good.
- dev mail list had a 53% increase in traffic in the past quarter (138 vs 88).
- user mail list had a 100% increase in traffic in the past quarter (22 vs 11).
- users and contributors in the community has increased due to version 1.0.


-----------------------------------------
Attachment BA: Report from the Apache Pekko Project  [PJ Fanning]

## Description:
The mission of Apache Pekko is the creation and maintenance of software related
to a toolkit and an ecosystem for building highly concurrent, distributed,
reactive and resilient applications for Java and Scala

## Project Status:
Current project status:
Making regular releases across all modules.
Not much growth in the community.
Issues for the board: Nothing to note.

## Membership Data:
Apache Pekko was founded 2024-03-20 (a year ago)
There are currently 28 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was JingZhang Chen on 2024-05-29.
- Domantas Petrauskas was added as committer on 2024-12-19

## Project Activity:
Finishing off 1.1.0 releases in a few lesser used modules.
1.2.0-M1 was released for the core modules.

## Community Health:
There has been a small decline in mailing list and general GitHub
interaction.
We are not seeing many new issues which is hopefully a good sign for
code quality but there is a chance that it is due to reduced interest.


-----------------------------------------
Attachment BB: Report from the Apache Pig Project  [Koji Noguchi]


-----------------------------------------
Attachment BC: Report from the Apache Pinot Project  [Kishore G]


-----------------------------------------
Attachment BD: Report from the Apache PLC4X Project  [César García]

## Description:
The mission of the Apache PLC4X project is creating a set of libraries for 
communicating with industrial programmable logic controllers (PLCs) using a 
variety of protocols but with a shared API.

## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board:none

## Membership Data:
Apache PLC4X was founded 2019-04-16 (6 years ago)
There are currently 21 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was César García on 2021-09-30.
- No new committers. Last addition was Jinlin Hong on 2022-11-02.

## Project Activity:
The team remains focused on the stability and robustness of the MODBUS,
S7, EIP, and OPC-UA drivers.

The progress on the implementation in the GO language shows 
considerable progress.

Work continues on developing a graphical interface for Java-based
PLC4X drivers.

Despite the drop in traffic, bugs and PRs are being addressed
by the development team, with a focus always on ensuring existing
features are maintained.

Based on these improvements and bug fixes, it is expected that 
the release (0.13.0) will be made shortly.

## Community Health:
Some of our key contributors have reported heavy workloads
in their personal tasks, putting some driver fixes or improvements
on hold. Members have also reported a drop in their participation
due to loss of interest or demotivation.

The community made significant improvements to the website,
improving its presentation and dynamic display, there are points
for improvement.

Part of the community actively promotes the use and benefits of
Plc4x on professional networks, as well as the technical achievements
of the libraries developed and their integration into different
architectures.

In the specific case of LinkedIn, a record of more than 537 followers
was achieved on the Plc4x channel on LinkedIn.


-----------------------------------------
Attachment BE: Report from the Apache Portable Runtime (APR) Project  [Yann Ylavic]


-----------------------------------------
Attachment BF: Report from the Apache Portals Project  [Neil Griffin]

## Description:
The mission of Portals is the creation and maintenance of software related to
Portal technology

## Project Status:
Current project status: Current project status: Apache Portals Pluto is a stable
implementation of a JCP standard and is currently in a maintenance mode.
Issues under consideration at this point largely (if not entirely) consist
of 3rd party dependency upgrades.
Issues for the board: None at this time.

## Membership Data:
Apache Portals was founded 2004-02-17 (21 years ago)
There are currently 40 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Neil Griffin on 2017-02-11.
- No new committers. Last addition was Ahmed on 2016-08-06.

## Project Activity:
Research has begun on whether or not it is feasible to migrate Apache
Pluto from Java EE 7 to Jakarta EE 10. Work on this task is being done
locally at this time and has not been committed to the source repo.

## Community Health:
There is no recent activity on the dev lists, and no recent community
contributions. Again, the project is in a maintenance mode.


-----------------------------------------
Attachment BG: Report from the Apache Pulsar Project  [Matteo Merli]

## Description:

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

## Project Status:
 - There are no issues requiring board attention at this time.


## Project Activity:

  - 4.0.2 was released on January 20th 2025
  - 3.3.4 was released on January 20th 2025
  - 3.0.9 was released on January 20th 2025
  - 3.0.10 was released on February 27th 2025
  - 3.3.5 was released on February 27th 2025
  - 4.0.3 was released on February 27th 2025

  - Pulsar C++ releases:
    - 3.7.0 on January 9th 2025

  - Pulsar Go releases:
    - 0.15.0 is in the process of getting released

  - Pulsar Python releases:
    - 3.6.0 on January 27th 2025
    - 3.6.1 on March 4th 2025

  - Pulsar NodeJS releases:
    - 1.13.0 on March 4th 2025
    - 1.13.1 on March 12th 2025

  - Pulsar reactive client:
    - 0.5.10 was released on December 14th 2024

  - We continue to have a very high number of "Pulsar Improvement
    Proposal" getting submitted, discussed and voted by the
    community:

    PIP-396: Align WindowFunction's WindowContext with BaseContext
    PIP-397: Support topic-level migration from blue cluster to green cluster
    PIP-398: Subscription replication on the broker, namespace and topic levels
    PIP-399: Fix Metric Name for Delayed Queue
    PIP-400: Support namespace-level configuration of migratedClusterUrl in
             blue-green migration feature
    PIP-401: Support set batching configurations for Pulsar Functions&Sources
    PIP-402: Role Anonymizer for Pulsar Logging
    PIP-404: Introduce per ledger properties
    PIP-405: Enhanced Dynamic Handling of Selective Consumers in
             MultiTopicConsumers
    PIP-406: Introduce metrics related to dispatch_throttled_count
    PIP-407: Add a newMessage API to create a message with a schema and
             transaction
    PIP-408: Add maxRetryRequestTimes in ClientConfigurationData and remove
             duplicate retry logic
    PIP-409: Support producer configuration for retry/dead letter topic producer
    PIP-410: Introduce pending publish buffer usage metrics

  - Pulsar has reached 683 contributors on the main Github repo
    (It was 675 contributors in December 2024)


## Health report:
  - There is healthy growth in the community, and several users are starting
    to become contributors to the project and engage more and more with
    the community. In this quarter, 8 contributors were invited as
    committers to the project.

## Membership Data:
  Apache Pulsar was founded 2018-09-18 (6 years ago)
  There are currently 84 committers and 43 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 Baodi Shi on 2024-04-10.
   - Zhangjian He was added as committer on 2025-01-27

## Community Health:

 - Activity on the mailing lists remains high with a mixture of new users,
   contributors, and deeper, more experienced users and contributors sparking
   discussion and questions and filing bugs or new features.

 - users@pulsar.apache.org:
    - 0% increase in traffic in the past quarter (23 emails compared to 23)

 - dev@pulsar.apache.org:
    - 19% decrease in traffic in the past quarter (356 emails compared to 437)

## Slack activity:
  - 10605 Members (10546 in December 2024)
  - 219 Active montly users (258 in December 2024)


## GitHub activity:
 - 658 commits in the past quarter (-17% decrease)
 - 67 code contributors in the past quarter (-15% change)
 - 244 PRs opened on GitHub, past quarter (-32% change)
 - 221 PRs closed on GitHub, past quarter (-40% change)
 - 109 issues opened on GitHub, past quarter (-36% change)
 - 63 issues closed on GitHub, past quarter (-42% change)


-----------------------------------------
Attachment BH: Report from the Apache Royale Project  [Yishay Weiss]

## Description:
The mission of Apache Royale is the creation and maintenance of software
related to improving developer productivity in creating applications for
wherever JavaScript runs (and other runtimes)

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Royale was founded 2017-09-20 (7 years ago)
There are currently 20 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Alina Kazi on 2024-11-03.
- No new committers. Last addition was María José Esteve on 2021-11-23.

## Project Activity:
Apart from routine maintenance there has been some activity aiming to reduce
our dependency on the Google Closure library which has been deprecated.

## Community Health:
While the users list activity is low we are seeing some user discussions made
on GitHub in the form of issue comments, indicating a continued interest.

There was a discussion in Dev on attracting new blood to the user/dev base. A
concern was raised that the source language, ActionScript 3, presents a
barrier to newcomers. TypeScript was suggested as an alternative, but the work
involved seems to be beyond our resources.


-----------------------------------------
Attachment BI: Report from the Apache Samza Project  [Jagadish Venkatraman]

## Description:
The mission of Samza is the creation and maintenance of software related to
distributed stream processing framework

## Project Status
Current project status: [Ongoing]
Issues for the board: No issues require attention of the board

## Membership Data:
Apache Samza was founded 2015-01-22 (10 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- No new PMC members. Last addition was Bharath Kumarasubramanian on 2020-02-13.
- No new committers. Last addition was Shekhar Sharma on 2024-04-21.

## Project Activity:
Notable fixes:
- fixes to improve checkpointing behavior: If an external utility attempts to
  reset a job's state by clearing backups and checkpoints, the local state
  still remains. Made fixes to clear the local rocksdb state of stateful jobs,
  if the inputs checkpoints don't exist.

## Community Health:
1 commit in the past quarter (-75% change)
1 code contributor in the past quarter (-50% change)
3 PRs opened on GitHub, past quarter (-50% change)
2 PRs closed on GitHub, past quarter (-60% change)


-----------------------------------------
Attachment BJ: 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).
- 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 BK: Report from the Apache ServiceMix Project  [Krzysztof Sobkowiak]

## Description:
The mission of Apache ServiceMix project is to create and maintain a flexible,
open-source integration container, powered by OSGi, that unifies the features
and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful
runtime platform you can use to build your own integration solutions.

## Project Status:
Current project status: Dormant
Issues for the board: None

## Membership Data:
Apache ServiceMix was founded 2007-09-19 (17 years ago)
There are currently 50 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.

## Project Activity:
No activity during the last quarter. We would like to reduce ServiceMix
Bundles release to encourage third party to use different approaches (private
package or wrap protocol).

## Community Health:
The project is now dormant:
- dependency projects (karaf, camel-karaf, ...) started to use wrap
protocol instead of ServiceMix Bundles (still ongoing)
- The Karaf integration distribution will cover most of the ServiceMix use cases
A roll call will be certainly performed soon to discuss the next step
for the project.


-----------------------------------------
Attachment BL: Report from the Apache Shiro Project  [Brian Demers]

## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework

## Project Status:
Current project status: Ongoing with low activity

Issues for the board: None at this time

## Membership Data:
Apache Shiro was founded 2010-09-21 (14 years ago)
There are currently 14 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 7:6.

Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Lenny Primak on 2022-11-02.

## Project Activity:
The Shiro team is in the planning stages for 3.0 which aims to cut
some tech debt and help move the project forward (and by dropping
deprecated functionality). New functionality and fixes are still
accepted in 2.x, 1.x is security fix only.

Last release was:
- 2.0.2: 2024-11-06

## Community Health:
Mailing list traffic is low.
Commits in the last quarter were mostly related to dependency updates.


-----------------------------------------
Attachment BM: Report from the Apache SINGA Project  [Wang Wei]

## Description:
The mission of Apache SINGA is the creation and maintenance of software related
to a distributed deep learning platform

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache SINGA was founded 2019-10-16 (5 years ago)
There are currently 23 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.

## Project Activity:
The team has released SINGA 4.3.0 on 07 September 2024.

In the past quarter, the community worked on the following
features/changes:

* Refactor the healthcare model zoo
  * Update the training files and model files for the detection of thyroid eye
   disease
  * Update the running script for the hematologic disease application
  * Update the datasets for the diabetic retinopathy classification
  * Add the implementations for the diabetic readmission application
* Optimize the distributed training by implementing the PEFT algorithm


## Community Health:
According to the statistics, there are more email traffic, commits and
contributors, which shows that the community is active in the development. But
the activities on Github are dropping.


-----------------------------------------
Attachment BN: Report from the Apache Sling Project  [Robert Munteanu]

## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Sling was founded 2009-06-17 (16 years ago)
There are currently 51 committers and 30 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 Julian Reschke on 2024-10-22.
- No new committers. Last addition was Henry Kuijpers on 2023-10-19.

## Project Activity:

We released version 13 of our sample application, the Sling Starter, on
January 17th, 2025. Work is ongoing towards Sling Starter 14.

The community is converging on a high-level approach to support the Jakarta
Servlet APIs.

In the meantime individual modules are being developed and released,
with 41 releases for this reporting period.

## Community Health:
Community health is pretty good and contributions from various
individuals continue.


-----------------------------------------
Attachment BO: Report from the Apache SpamAssassin Project  [Sidney Markowitz]

## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.

## Project Status:
Project state: Ongoing with low to moderate activity

Primary focus for development is now ongoing maintenance bug fixes to the
latest release, 4.0.1.

Issues for the board: Selection of Giovanni Bechis as new Chair has been
placed on Board agenda

## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (20 years ago)
There are currently 32 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2.5:1.

Community changes, past quarter:
- PMC members:
   Sidney Markowitz resigned as Chair, pending confirmation of his replacement
   Giovanni Bechis was selected as new Chair, to be confirmed by the Board
   Last addition was Kent Oyer on 2024-11-09.
   Michel Parker resigned on 2025-03-02, recognized as emeritus by PMC
   Henrik Krohns resigned on 2025-03-14, recognized as emeritus by PMC
- No new committers. Last addition was Kent Oyer on 2024-03-29.

## Project Activity:

Last release was Apache SpamAssassin version 4.0.1 on 29 March 2024.

We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility.

On 28 February 2025, the server that was donated to ASF by Sonic.net for
sa-update.spamassassin.org was decomissioned, replaced by newer infrastructure
we have available.

## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.


-----------------------------------------
Attachment BP: Report from the Apache Storm Project  [Richard Zowalla]

## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system

## Project Status:
Current project status: Ongoing (reactivated)
Issues for the board: none

## Membership Data:
Apache Storm was founded 2014-09-17 (10 years ago)
There are currently 48 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Nikhil Singh on 2023-10-23.
- Purshotam Shah was added as committer on 2024-10-08

## Project Activity:

Project activity has slowed in recent years, with Storm currently in
maintenance mode. However, we have received several pull requests from
contributors outside the existing committer group, along with new bug reports
and a slight uptick in discussions and questions on our dev/user list. This
indicates that Storm is still actively used, which is encouraging.

Over the past quarter, we upgraded numerous third-party libraries to newer
versions to reduce technical debt and released two maintenance updates. We aim
to maintain this release schedule and continue delivering patches at a similar
pace.

Efforts to reduce Storm’s third-party dependencies are ongoing. The project
relies on many external libraries, and managing this technical debt remains a
significant challenge. To streamline dependencies, we have dropped support for
Hive and raised the Java Runtime Level to 17.

As mentioned in previous reports, the Storm UI still contains outdated and
legacy JavaScript libraries in the repository. Unfortunately, among our active
committers, we lack dedicated frontend developers with the necessary expertise
to address this issue. On a positive note, the migration from Jira to GitHub
has been successfully completed. We appreciate INFRA’s efforts in handling the
transition and managing our extensive backlog of legacy tickets. Since the
migration, we have received a few new issues and contributions, which is an
encouraging sign.

Recent releases:
2.8.0 was released on 2025-01-24.
2.7.1 was released on 2024-11-29.
2.7.0 was released on 2024-10-19.

## Community Health:
Community engagement is currently healthy, but could benefit from new
contributors or users.


-----------------------------------------
Attachment BQ: 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 2024-01-23 (2 months ago)
There are currently 8 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 2:3.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.

## Project Activity:

- We have updated the project's website and README
- We are currently preparing to release v2.1.6
- We have collected and published the roadmap for version 2.2

## Community Health:

- New contributor +2
- New docs contributor +1
- New ASF Member +1

Our project is progressing well, with a steadily growing user base.
Additionally, We are revamping the official documentation to attract
more community contributors, offering dedicated support and guidance
for newcomers.


-----------------------------------------
Attachment BR: 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: Not
sure if this is the right place, but 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) into which we can scrape community
 stats/activity to 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.

2400 commits in the past quarter (162% increase) 95 code contributors in the
past quarter (3% increase) 611 PRs opened on GitHub, past quarter (-52%
change) 659 PRs closed on GitHub, past quarter (-46% change) 283 issues opened
on GitHub, past quarter (-46% change) 200 issues closed on GitHub, past
quarter (-49% change)

We still have issues and PRs coming in faster than we can close them out, but
we have daily PR and Issue 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 BS: Report from the Apache Synapse Project  [Isuru Udana]


-----------------------------------------
Attachment BT: Report from the Apache Tomcat Project  [Mladen Turk]

## Description:
The Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.

## Project Status:
Current project status: Ongoing
Issues for the board: There are no issues requiring board attention at this time

## Membership Data:
Apache Tomcat was founded 2005-05-18 (20 years ago)
There are currently 51 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- Dimitris Soumis was added to the PMC on 2025-02-19
- John Engebretson was added as committer on 2025-02-05

## Project Activity:
- Here are listed the most recent releases since
  the last report.
- Apache Tomcat 11.0.5 was released on 2025-03-05.
- Apache Tomcat 10.1.39 was released on 2025-03-07.
- Apache Tomcat 9.0.102 was released on 2025-03-06.
- Apache Tomcat Migration Tool for Jakarta EE 1.0.9 was released on 2025-01-21

## Community Health:
Continued healthy activity across multiple components and
responsiveness on both dev and user lists.


-----------------------------------------
Attachment BU: Report from the Apache TomEE Project  [David Blevins]


-----------------------------------------
Attachment BV: Report from the Apache TVM Project  [Tianqi Chen]

## Description:
The mission of Apache TVM is the creation and maintenance of software related
to compilation of machine learning models to run on a wide range of hardware
platforms

## Project Status:
Current project status: ongoung
Issues for the board: none

## Membership Data:
Apache TVM was founded 2020-11-17 (4 years ago)
There are currently 78 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- Mengshiun Yu was added as committer on 2025-02-13

## Project Activity:

Recent releases

- 0.19.0 was released on 2025-01-28
- 0.18.0 was released on 2024-10-27

The project started to bring more focus on the latest python-first compiler
strategies and LLM workloads. Some recent improvements include:

- Support for new data types, FP8, BF16 and F4
- Better support for Torch importers
- KVCache runtime for latest reasoning models
- Support for MLA kernels in deepseek models.
- OpenCLML offload for relax.

The project also started to phase out legacy components to clean up technical
debts and focus on coherent developments for python-first ML compiler.

## Community Health:

Generally, we see more interest in new models and generative AI workloads. The
community is focusing on new LLM-related directions to meet those interest
shifts. Overall, the project merges about 70 PRs per month. We are also spend
good amount of energy on architecting to ensure we can have a solid foundation
as we bring in support for new workloads.


-----------------------------------------
Attachment BW: Report from the Apache UIMA Project  [Richard Eckart de Castilho]

## Description:
Apache UIMA (*) software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video. (*) Unstructured Information Management Architecture.

## Project Status:
Current project status: Ongoing (low)
Issues for the board: The board comments shown in the reporting tool
from 2024_06_19 have now disappeared and been replaced by the comment
from 2024_12_18. To avoid confusion about outdated board questions, it
might be considered by the board to simply post a comment acknowledging
having received feedback from the project which will then replace the
question comment.

## Membership Data:
Apache UIMA was founded 2010-03-17 (15 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.

## Project Activity:
There have been no new releases since the last board report.
However, there has been some progress towards a UIMA-J 3.6.1
release in the form of some smaller bug fixes.

## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list / issue tracker / Matrix channel, but not much overall.
It seems automatically generated metrics are incorrect reporting zero activity.
We had at least 2 PRs merged in the last quarter and at last 1 issue closed.


-----------------------------------------
Attachment BX: Report from the Apache Uniffle Project  [He Qi]

## Description:
The mission of Apache Uniffle is the creation and maintenance of software
related to a unified remote shuffle service

## Project Status:
Current project status: New
Issues for the board: No issues

## Membership Data:
Apache Uniffle was founded 2025-02-19 (19 days ago)
There are currently 22 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.

## Project Activity:
0.9.1 is available on 2025-01-09
We are discussing about 0.10.0 release

## Community Health:
We are solving the left issues about graduation.
We are doing some refators to improve the code quality.
We are discussing a new language implementation of shuffle server.
We are helping more contributors to become committers.


-----------------------------------------
Attachment BY: Report from the Apache Unomi Project  [Serge Huber]

## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee

## Project Status:
Current project status: On-going, with high development activity
Issues for the board: none

## Membership Data:
Apache Unomi was founded 2019-02-20 (6 years ago)
There are currently 16 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Jonathan Sinovassin-Naïk on 2024-11-25.
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.

## Project Activity:
Major activity on the development side is currently on-going, with a focus on
the next major version 3.0. Alongside with that a new support for OpenSearch
has been developed and is in review that will now make it possible to no
longer just have a requirement for Elasticsearch.

Version 3.0 will include:
- Support for multi-tenancy at a data level to reduce the need for
  containerization to support multiple (true) tenants.
- A brand new scheduler with support for task persistence and cluster
  distribution
- A new unit test framework, maybe it a lot easier to test and refactoring
  code modifications
- Improved documentation with support for PlantUML diagrams
- Better developer experiences including an explain system for understanding
  request execution
- Lots of new Karaf Shell commands
- And a lot more to come
- Replaced the Karaf Cellar use with a custom persistence based communication
  system

Alongside with that bugfix releases are still being done on the
stable (2.x) version.

## Community Health:
The community is healthy and the new monthly meeting has been a great way to
exchange ideas and improve collaboration between developers. Meeting notes are
always produced and the meeting is being held at two alternating times to give
users across the world a change to participate. All decisions remain done
through mailing lists of course. Slack is still the most active asynchronous
communication. Activity will probably increase in the Github once the major
contributions for 3.0 are being reviewed but for the moment the focus is on
finishing the planned feature set.


-----------------------------------------
Attachment BZ: Report from the Apache VCL Project  [Josh Thompson]

## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.

## Project Status:
Current project status: Ongoing
Issues for the board: There are no issues requiring board attention.

## Membership Data:
Apache VCL was founded 2012-06-19 (13 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.

Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.

## Project Activity:
We are almost finished working on something that came up on the private list a
few months ago.

## Community Health:
As before, Apache VCL is still being used by at least a few colleges and
universities, and though activity is pretty light, it is not dormant.


-----------------------------------------
Attachment CA: Report from the Apache Velocity Project  [Nathan Bubna]

## Description:
The mission of Velocity is the creation and maintenance of software related to
A Java Templating Engine

## Project Status:
Current project status: Ongoing, Low Activity
Issues for the board: none

## Membership Data:
Apache Velocity was founded 2006-10-24 (18 years ago)
There are currently 15 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Thomas Mortagne on 2020-03-09.

## Project Activity:
Last release was Engine 2.4.1 on 2024-10-14
Ongoing discussions about dealing with Javax/Jakarta switch in Tools project.

## Community Health:
We had a very quiet quarter after last fall's burst of energy. Typical. Slow
and steady, par for the course.


-----------------------------------------
Attachment CB: Report from the Apache Whimsy Project  [Shane Curcuru]

## Description:
The mission of Apache Whimsy is the creation and maintenance of software
related to tools that help automate various administrative tasks or information
lookup activities

## Project Status:
Current project status: Ongoing; busier than usual quarter
Issues for the board: None

## Membership Data:
Apache Whimsy was founded 2015-05-19 (10 years ago)
There are currently 14 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Matt Sicker on 2020-04-11.
- Floor Drees was added as committer on 2025-03-14
- Whitney P True was added as committer on 2025-03-12

## Project Activity:
Whimsy had a very busy month, both with significant coding work building
new tools for the Member Meeting along with making some fixes, plus
several drive-by contributions in docs and minor issues.  We also
attracted several spam contributors as well, always exciting.

A number of issues and minor updates were made around Secretary tools.

## Community Health:
We have three PMC members available to address security issues in our live
server, although improvement requests and the like do not often find any
volunteers to work on them.  Whimsy does not otherwise release any software
products.

We look forward to future work by the ASF Tooling team to build replacements
for any tooling deemed critical by the organization.


-----------------------------------------
Attachment CC: Report from the Apache Wicket Project  [Andrea Del Bene]

## Description:
The mission of Wicket is the creation and maintenance of software related to
Component-based Java Web Application Framework.

## Project Status:
Current project status: ongoing
Issues for the board: no issue to report

## Membership Data:
Apache Wicket was founded 2007-06-20 (18 years ago)
There are currently 35 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- Matt Pavlovich was added to the PMC on 2025-01-27
- Matt Pavlovich was added as committer on 2025-01-27

## Project Activity:
Last quarter has seen a more release than usual. We had 2 release for 9.x branch
(9.19.0 which solves CVE-2024-53299 and 9.20.0), two release for 10. branch
(10.3.0 which solves CVE-2024-53299 and 10.4.0). We also ha a release for 8.x
with version 8.17.0 which solves CVE-2024-53299. We don't have yet a precise
plan for Wicket 11, which will be probably based on Java 21.

## Community Health:
Community still healthily and participate to framework improvements and release
requests. Download stats still height and steady.


-----------------------------------------
Attachment CD: Report from the Apache Yetus Project  [Allen Wittenauer]

## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.

## Project Status:
Current project status: Dormant
Issues for the board: none

## Membership Data:
Apache Yetus was founded 2015-09-15 (9 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.

Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.

## Project Activity:
We released 0.15.1 last week which updated some key components for all of our
downstream users, especially on GitHub.  We are waiting to see what happens
with INFRA's policies around actions given we use some from the `docker/*`
space to build multi-architecture containers.

## Community Health:
Low activity across all human-related metrics, but given the stable status of
the project that should not be surprising.  Still in use by other Apache
projects and others outside of the ASF.  Clearly capable of getting a release
out since we just did it.


-----------------------------------------
Attachment CE: Report from the Apache ZooKeeper Project  [Flavio Paiva Junqueira]

## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (14 years ago)
There are currently 33 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Damien Diederen on 2024-04-16.
- No new committers. Last addition was Kezhu Wang on 2024-08-02.

We need to focus on inviting new committers.

## Project Activity:
There hasn't been release activity during this period, the last release
was in Oct. 2024. There is email, commit and PR activity, but we haven't
driven a release. We will look into driving at least a maintenance release
in the next period.

## Community Health:
The metrics shown in reporter are broken, they say no commits or PRs, but
that's incorrect. The github repository shows otherwise, and we have started
an email thread to look into it (https://lists.apache.org/
thread/6w4qyg5mfcxhkk7z37scmv3xpxtt21yg).

As mentioned above, we haven't had release activity in this period, but we
have had a regular project activity around email exchanges, issues, PRs and
commits. We did notice that Apache Curator, which is a downstream project of
Apache ZooKeeper, cut a new release 5.8.0.


------------------------------------------------------
End of minutes for the March 19, 2025 board meeting.

Index

• Call to order
• Roll Call
• Minutes from previous meetings
• The meeting of February 19, 2025
• Executive Officer Reports
• Board Chair [Shane Curcuru]
• President [Ruth Suehle]
• Treasurer [Craig R. McClanahan]
• Secretary [Matt Sicker]
• Executive Vice President [David Nalley]
• Vice Chair [Justin Mclean]
• Additional Officer Reports
• VP of W3C Relations [Andy Seaborne / Kanchana]
• Apache Legal Affairs Committee [Roman Shaposhnik / Sander]
• Apache Security Team Project [Mark J. Cox / Zili]
• Committee Reports
• Apache DeltaSpike Project [Mark Struberg / Kanchana]
• Apache OpenWebBeans Project [Mark Struberg / Rich]
• Apache Pig Project [Koji Noguchi / Kanchana]
• Apache Pinot Project [Kishore G / JB]
• Apache Portable Runtime (APR) Project [Yann Ylavic / Justin]
• Apache Synapse Project [Isuru Udana / Rich]
• Apache TomEE Project [David Blevins / Kanchana]
• Special Orders
• Change the Apache SpamAssassin Project Chair
• Change the Apache CloudStack Project Chair
• Terminate the Apache Gora Project
• Discussion Items
• Appoint Board Chair And Vice Chair
• Budget
• Regular Meeting Schedule
• Officer Positions
• Review Outstanding Action Items
• Unfinished Business
• New Business
• Announcements
• Adjournment
• Report from the VP of Brand Management [Mark Thomas]
• Report from the VP of Fundraising [Bob Paulin]
• Report from the VP of Marketing and Publicity [Brian Proffitt]
• Report from the VP of Infrastructure [Myrle Krantz]
• Report from the VP of Tooling [Dave Fisher]
• Report from the VP of Conferences [Brian Proffitt]
• Report from the Apache Travel Assistance Committee [Gavin McDonald]
• Report from the VP of Diversity and Inclusion [David Nalley]
• Report from the VP of Data Privacy [Christian Grobmeier]
• Report from the VP of Public Affairs [Dirk-Willem van Gulik]
• Report from the VP of ECMA Relations [Piotr P. Karwasz]
• Report from the VP of W3C Relations [Andy Seaborne]
• Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
• Report from the Apache Security Team Project [Mark J. Cox]
• Report from the Apache Airflow Project [Bolke de Bruin]
• Report from the Apache Allura Project [David Philip Brondsema]
• Report from the Apache Answer Project [Ning Qi]
• Report from the Apache Atlas Project [Madhan Neethiraj]
• Report from the Apache Axis Project [Robert Lazarski]
• Report from the Apache Beam Project [Kenneth Knowles]
• Report from the Apache Bigtop Project [Masatake Iwasaki]
• Report from the Apache BVal Project [Matthew Jason Benson]
• Report from the Apache Camel Project [Andrea Cosentino]
• Report from the Apache Cayenne Project [Michael Ray Gentry]
• Report from the Apache Celeborn Project [Keyong Zhou]
• Report from the Apache CloudStack Project [Daniel Augusto Veronezi Salvador]
• Report from the Apache Commons Project [Gary D. Gregory]
• Report from the Apache Cordova Project [Bryan Ellis]
• Report from the Apache cTAKES Project [Pei Chen]
• Report from the Apache Curator Project [Enrico Olivelli]
• Report from the Apache Daffodil Project [Mike Beckerle]
• Report from the Apache DataFusion Project [Andrew Lamb]
• Report from the Apache DeltaSpike Project [Mark Struberg]
• Report from the Apache Druid Project [Gian Merlino]
• Report from the Apache ECharts Project [Wenli Zhang]
• Report from the Apache Felix Project [Karl Pauls]
• Report from the Apache Flex Project [Harbs]
• Report from the Apache Flink Project [Robert Metzger]
• Report from the Apache Gobblin Project [Abhishek Tiwari]
• Report from the Apache Guacamole Project [Mike Jumper]
• Report from the Apache Gump Project [Stefan Bodewig]
• Report from the Apache Helix Project [Junkai Xue]
• Report from the Apache Hive Project [Naveen Gangam]
• Report from the Apache Hop Project [Hans Van Akelyen]
• Report from the Apache Hudi Project [Vinoth Chandar]
• Report from the Apache Iceberg Project [Ryan Blue]
• Report from the Apache Incubator Project [Justin Mclean]
• -- Baremaps
• -- Cloudberry
• -- ResilientDB
• -- Gravitino
• -- KIE
• -- Nemo
• -- OpenServerless
• -- OzHera
• -- Polaris
• -- Toree
• -- Training
• -- Wayang
• Report from the Apache IoTDB Project [Xiangdong Huang]
• Report from the Apache Jackrabbit Project [Marcel Reutegger]
• Report from the Apache Karaf Project [Jean-Baptiste Onofré]
• Report from the Apache Kibble Project [Sharan Foga]
• Report from the Apache Kvrocks Project [Mingyang Liu]
• Report from the Apache Kyuubi Project [Kent Yao]
• Report from the Apache Libcloud Project [Tomaž Muraus]
• Report from the Apache Linkis Project [Shuai Di]
• Report from the Apache Logo Development Project [Daniel Gruno]
• Report from the Apache Lucene Project [Dawid Weiss]
• Report from the Apache Lucene.Net Project [Shad Storhaug]
• Report from the Apache Mynewt Project [Szymon Janc]
• Report from the Apache NetBeans Project [Geertjan Wielenga]
• Report from the Apache OFBiz Project [Jacopo Cappellato]
• Report from the Apache Olingo Project [Michael Bolz]
• Report from the Apache OpenDAL Project [Hao Ding]
• Report from the Apache OpenNLP Project [Jeff Zemerick]
• Report from the Apache OpenWebBeans Project [Mark Struberg]
• Report from the Apache Paimon Project [Jingsong Lee]
• Report from the Apache Pekko Project [PJ Fanning]
• Report from the Apache Pig Project [Koji Noguchi]
• Report from the Apache Pinot Project [Kishore G]
• Report from the Apache PLC4X Project [César García]
• Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
• Report from the Apache Portals Project [Neil Griffin]
• Report from the Apache Pulsar Project [Matteo Merli]
• Report from the Apache Royale Project [Yishay Weiss]
• Report from the Apache Samza Project [Jagadish Venkatraman]
• Report from the Apache SeaTunnel Project [Jun Gao]
• Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
• Report from the Apache Shiro Project [Brian Demers]
• Report from the Apache SINGA Project [Wang Wei]
• Report from the Apache Sling Project [Robert Munteanu]
• Report from the Apache SpamAssassin Project [Sidney Markowitz]
• Report from the Apache Storm Project [Richard Zowalla]
• Report from the Apache StreamPark Project [Huajie Wang]
• Report from the Apache Superset Project [Maxime Beauchemin]
• Report from the Apache Synapse Project [Isuru Udana]
• Report from the Apache Tomcat Project [Mladen Turk]
• Report from the Apache TomEE Project [David Blevins]
• Report from the Apache TVM Project [Tianqi Chen]
• Report from the Apache UIMA Project [Richard Eckart de Castilho]
• Report from the Apache Uniffle Project [He Qi]
• Report from the Apache Unomi Project [Serge Huber]
• Report from the Apache VCL Project [Josh Thompson]
• Report from the Apache Velocity Project [Nathan Bubna]
• Report from the Apache Whimsy Project [Shane Curcuru]
• Report from the Apache Wicket Project [Andrea Del Bene]
• Report from the Apache Yetus Project [Allen Wittenauer]
• Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]