Index Links: 2025 - All years - Original
                    The Apache Software Foundation

                  Board of Directors Meeting Minutes

                          November 19, 2025


1. Call to order

    The meeting was scheduled for 22:00 UTC and began at 22:01 when
    a sufficient attendance to constitute a quorum was recognized by
    the chair.

            Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2025-11-19T22: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:

        Jim Jagielski
        Zili Chen
        Greg Stein
        Rich Bowen
        Shane Curcuru
        Justin Mclean
        Jean-Baptiste Onofré
        Kanchana Pradeepika Welagedara

    Directors Absent:

        Sander Striker

    Executive Officers Present:

      Craig McClanahan
      Craig L Russell
      Matt Sicker
      Ruth Suehle

    Executive Officers Absent:

      Jeff Jirsa

    Guests:

        Daniel Gruno
        Sally Khudairi
        Alin Jerpelea
        Dave Fisher
        Thomas Neidhart
        Andrew Wetmore
        Paul King
        Whitney P True - joined :41

3. Minutes from previous meetings

    Published minutes can be found at:

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

    A. The meeting of October 15, 2025

       See: board_minutes_2025_10_15.txt

       Approved by General Consent.

4. Executive Officer Reports

    A. Board Chair [Sander Striker]

       No report was submitted.

    B. President [Ruth Suehle]

       The operations team discussed this month better documenting its
       processes and policies. Officers have begun doing so to find where our
       existing information, accounts, and policies is tracked and plans to
       try to have that filled out next month. One proposed outcome is
       possibly an a.o/policies section, and a standard template and process
       for those to make them easier to find.

       I've been helping Conferences seek venues for C/C next year. Finding
       affordable venues of a large enough size in Europe has been a bit of a
       challenge. Local volunteers who speak the language and can help with
       coordination would be extremely helpful to broadening the options.

       I did an interview with ODBMS Industry Watch this month:
       https://www.odbms.org/blog/2025/11/community-over-code-ruth-suehle-on-leading-the-apache-software-foundation-into-the-future/

       And a blog post for OSI that basically is a recap of the panel I
       moderated at All Things Open: https://opensource.org/blog/sustaining-open-source-the-next-25-years-depend-on-what-we-do-together-now

       Additionally, please see Attachments 1 through 11.

    C. Treasurer [Craig McClanahan]

       Normal operations continue.  In addition, we (Treasury) are focused on
       improving our documentation for both our own operations, and those of ASF
       users of our bill.com and ramp.com services.

    D. Secretary [Matt Sicker]

       In October, the secretary received 28 ICLAs, one CCLA, and one
       software grant.

    E. Executive Vice President [Jeff Jirsa]

       Modest progress continues on formalizing the Code of Conduct. This month, 
       aligned with VP Legal on both intent and challenges with the Code of Conduct 
       as written. VP Legal suggests bifurcating policy (code of conduct) between a 
       less rigid code of conduct for general communication and a more rigid and 
       formalized language that applies to those with a fiduciary duty to the 
       Foundation. VP Legal has offered to engage outside counsel (pro-bono to start) 
       to inquire about standard policies/documents in this space and confirm the 
       approach is sound and appropriate for the Foundation.

    F. Vice Chair [Rich Bowen]

       Nothing to report.

    Executive officer reports approved as submitted by General Consent.

5. Additional Officer Reports

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

       See Attachment 12

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

       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:

        # Creadur [striker]
        # DB [striker]
        # Libcloud [tison]
        # Logging Services [striker]
        # Mahout [striker]
        # ManifoldCF [jmclean]
        # Pinot [gstein]
        # SIS [striker]
        # ServiceComb [striker]
        # Spark [jim]
        # TsFile [striker]

    A. Apache AGE Project [Jeff Jirsa / Jim]

       See Attachment A

    B. Apache Airavata Project [Suresh Marru / Justin]

       No report was submitted.

    C. Apache Ambari Project [Brahma Reddy Battula / Kanchana]

       No report was submitted.

    D. Apache Ant Project [J Pai / Rich]

       See Attachment D

    E. Apache Avro Project [Ryan Skraba / Sander]

       See Attachment E

    F. Apache BookKeeper Project [Enrico Olivelli / Greg]

       No report was submitted.

    G. Apache Brooklyn Project [Juan D. Cabrerizo / Rich]

       See Attachment G

    H. Apache BuildStream Project [Tristan Van Berkom / Sander]

       No report was submitted.

    I. Apache BVal Project [Matt Benson / Shane]

       No report was submitted.

    J. Apache CarbonData Project [Jacky Li / JB]

       No report was submitted.

    K. Apache Cassandra Project [Ekaterina Dimitrova / Jim]

       See Attachment K

    L. Apache Celeborn Project [Keyong Zhou / Greg]

       No report was submitted.

    M. Apache Celix Project [Pepijn Noltes / Justin]

       See Attachment M

    N. Apache Community Development Project [Swapnil Mane / Kanchana]

       See Attachment N

    O. Apache CouchDB Project [Jan Lehnardt / Zili]

       See Attachment O

    P. Apache Creadur Project [Philipp Ottlinger / JB]

       See Attachment P

    Q. Apache DataSketches Project [Lee Rhodes / Justin]

       See Attachment Q

    R. Apache DB Project [Bryan Pendleton / Sander]

       See Attachment R

    S. Apache DeltaSpike Project [Mark Struberg / Jim]

       See Attachment S

    T. Apache DevLake Project [Hezheng Yin / Rich]

       No report was submitted.

    U. Apache DolphinScheduler Project [Lidong Dai / Zili]

       See Attachment U

    V. Apache Doris Project [Mingyu Chen / Zili]

       See Attachment V

    W. Apache Drill Project [Charles Givre / Greg]

       See Attachment W

    X. Apache Druid Project [Abhishek Agarwal / Shane]

       See Attachment X

    Y. Apache Dubbo Project [Jun Liu / Kanchana]

       No report was submitted.

    Z. Apache Empire-db Project [Rainer Döbele / JB]

       See Attachment Z

    AA. Apache EventMesh Project [Eason Chen / Shane]

       See Attachment AA

    AB. Apache FreeMarker Project [Dániel Dékány / Jim]

       See Attachment AB

    AC. Apache Geode Project [Mark Bretl / Zili]

       See Attachment AC

    AD. Apache Grails Project [James Fredley / Sander]

       See Attachment AD

    AE. Apache Groovy Project [Paul King / Justin]

       See Attachment AE

    AF. Apache Hadoop Project [Xiaoqiao He / Greg]

       See Attachment AF

    AG. Apache HertzBeat Project [Chao Gong / Kanchana]

       See Attachment AG

    AH. Apache Hop Project [Hans Van Akelyen / Rich]

       No report was submitted.

    AI. Apache HTTP Server Project [Joe Orton / JB]

       See Attachment AI

    AJ. Apache HttpComponents Project [Michael Osipov / Justin]

       See Attachment AJ

    AK. Apache Ignite Project [Dmitry Pavlov / Rich]

       No report was submitted.

    AL. Apache Impala Project [Zoltán Borók-Nagy / JB]

       See Attachment AL

    AM. Apache Incubator Project [Justin Mclean / Justin]

       See Attachment AM

    AN. Apache Juneau Project [James Bognar / Greg]

       See Attachment AN

    AO. Apache Kafka Project [Mickael Maison / Kanchana]

       See Attachment AO

    AP. Apache Knox Project [Larry McCay / Jim]

       See Attachment AP

    AQ. Apache Kylin Project [Yang Li / Sander]

       See Attachment AQ

    AR. Apache Libcloud Project [Tomaž Muraus / Shane]

       No report was submitted.

       @Zili: follow up about Attic

    AS. Apache Logging Services Project [Piotr Karwasz / Zili]

       See Attachment AS

       @Kanchana: follow up with Logging Services PMC about RTC

    AT. Apache Mahout Project [Shannon Quinn / Shane]

       See Attachment AT

       @Shane: follow up with Mahout about professional status

    AU. Apache ManifoldCF Project [Piergiorgio Lucidi / Zili]

       See Attachment AU

       @Justin: discuss path to Attic

    AV. Apache Maven Project [Hervé Boutemy / Sander]

       See Attachment AV

    AW. Apache OpenJPA Project [Mark Struberg / Justin]

       See Attachment AW

    AX. Apache OpenWhisk Project [Dave Grove / Jim]

       See Attachment AX

    AY. Apache Ozone Project [Sammi Chen / Greg]

       See Attachment AY

    AZ. Apache Parquet Project [Julien Le Dem / JB]

       See Attachment AZ

    BA. Apache Perl Project [Steve Hay / Rich]

       See Attachment BA

    BB. Apache Phoenix Project [Istvan Toth / Kanchana]

       See Attachment BB

    BC. Apache Pinot Project [Kishore G / Greg]

       See Attachment BC

       @Greg: talk to Pinot PMC about communication channels
       @Rich: add paragraph about Slack v. mailing lists in upcoming PMC communications

    BD. Apache POI Project [Dominik Stadler / Jim]

       See Attachment BD

    BE. Apache Qpid Project [Robbie Gemmell / Shane]

       See Attachment BE

    BF. Apache RocketMQ Project [Xiaorui Wang / Kanchana]

       No report was submitted.

    BG. Apache Roller Project [Dave Johnson / Justin]

       See Attachment BG

    BH. Apache Santuario Project [Colm O hEigeartaigh / Greg]

       See Attachment BH

    BI. Apache SDAP Project [Nga Thien Chung / JB]

       See Attachment BI

    BJ. Apache SeaTunnel Project [Jun Gao / Rich]

       See Attachment BJ

    BK. Apache Sedona Project [Jia Yu / Zili]

       See Attachment BK

    BL. Apache Serf Project [Daniel Sahlberg / Sander]

       See Attachment BL

    BM. Apache ServiceComb Project [Bao Liu / Jim]

       See Attachment BM

    BN. Apache ShardingSphere Project [Liang Zhang / Greg]

       No report was submitted.

    BO. Apache ShenYu Project [Yu Xiao / Rich]

       See Attachment BO

    BP. Apache SIS Project [Martin Desruisseaux / Justin]

       See Attachment BP

       @Rich: follow up about private communications

    BQ. Apache Solr Project [Alessandro Benedetti / Sander]

       See Attachment BQ

    BR. Apache Spark Project [Matei Zaharia / Kanchana]

       See Attachment BR

    BS. Apache StormCrawler Project [Richard Zowalla / Zili]

       See Attachment BS

    BT. Apache StreamPipes Project [Philipp Zehnder / JB]

       See Attachment BT

    BU. Apache Subversion Project [Nathan Hartman / Shane]

       See Attachment BU

    BV. Apache Superset Project [Maxime Beauchemin / Jim]

       See Attachment BV

    BW. Apache Syncope Project [Francesco Chicchiriccò / Justin]

       See Attachment BW

    BX. Apache SystemDS Project [Matthias Boehm / Rich]

       See Attachment BX

    BY. Apache Teaclave Project [Zhaofeng Chen / Greg]

       See Attachment BY

    BZ. Apache TomEE Project [David Blevins / Sander]

       See Attachment BZ

    CA. Apache Traffic Server Project [Bryan Call / Shane]

       No report was submitted.

    CB. Apache Training Project [Justin Mclean / Justin]

       See Attachment CB

    CC. Apache TsFile Project [Jialin Qiao / Kanchana]

       See Attachment CC

       @Greg: follow up with TsFile PMC about publishing to PyPI
       @Greg: follow up with board about PyPI policy

    CD. Apache Turbine Project [Georg Kallidis / Zili]

       See Attachment CD

    CE. Apache Uniffle Project [He Qi / JB]

       See Attachment CE

    CF. Apache Velocity Project [Nathan Bubna / JB]

       No report was submitted.

    CG. Apache Web Services Project [Daniel Kulp / Kanchana]

       No report was submitted.

    CH. Apache Whimsy Project [Dave Fisher / Rich]

       See Attachment CH

    CI. Apache Xalan Project [Gary D. Gregory / Jim]

       See Attachment CI

    CJ. Apache Xerces Project [Michael Glavassevich / Sander]

       See Attachment CJ

    CK. Apache XML Graphics Project [Clay Leeds / Zili]

       No report was submitted.

    CL. Apache YuniKorn Project [Wilfred Spiegelenburg / Shane]

       See Attachment CL

    Committee reports approved as submitted by General Consent.

7. Special Orders

    A. Change the Apache Arrow Project Chair

       WHEREAS, the Board of Directors heretofore appointed Neal Richardson
       (npr) to the office of Vice President, Apache Arrow, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Neal Richardson from the office of Vice President, Apache Arrow, and

       WHEREAS, the Project Management Committee of the Apache Arrow project
       has chosen by vote to recommend Antoine Pitrou (apitrou) as the
       successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Neal Richardson is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache Arrow, and

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

    B. Establish the Apache Artemis Project

       WHEREAS, the Board of Directors deems it to be in the best interests
       of the Foundation and consistent with the Foundation's purpose to
       establish a Project Management Committee charged with the creation and
       maintenance of open-source software, for distribution at no charge to
       the public, related to implementing a distributed messaging system.

       NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
       (PMC), to be known as the "Apache Artemis Project", be and hereby is
       established pursuant to Bylaws of the Foundation; and be it further

       RESOLVED, that the Apache Artemis Project be and hereby is responsible
       for the creation and maintenance of software related to allowing
       application developer to build messaging based applications; and be it
       further

       RESOLVED, that the office of "Vice President, Apache Artemis" be and
       hereby is created, the person holding such office to serve at the
       direction of the Board of Directors as the chair of the Apache Artemis
       Project, and to have primary responsibility for management of the
       projects within the scope of responsibility of the Apache Artemis
       Project; and be it further

       RESOLVED, that the persons listed immediately below be and hereby are
       appointed to serve as the initial members of the Apache Artemis
       Project:

       * Arthur Naseef <artnaseef@apache.org>
       * Brian McCallister <brianm@apache.org>
       * Domenico Francesco Bruscino <brusdev@apache.org>
       * Bruce Snyder <bsnyder@apache.org>
       * Christian Posta <ceposta@apache.org>
       * Hiram R. Chirino <chirino@apache.org>
       * Clebert Suconic <clebertsuconic@apache.org>
       * Christopher L. Shannon <cshannon@apache.org>
       * Dain Sundstrom <dain@apache.org>
       * Dejan Bosanac <dejanb@apache.org>
       * Daniel Kulp <dkulp@apache.org>
       * Gert Vanthienen <gertv@apache.org>
       * Guillaume Nodet <gnodet@apache.org>
       * Gary Tully <gtully@apache.org>
       * Krzysztof Porębski <havret@apache.org>
       * Matt Richard Hogstrom <hogstrom@apache.org>
       * Justin Graham Bertram <jbertram@apache.org>
       * Jean-Baptiste Onofré <jbonofre@apache.org>
       * Jeff Genender <jgenender@apache.org>
       * Jim Gomes <jgomes@apache.org>
       * John Sisson <jsisson@apache.org>
       * James Strachan <jstrachan@apache.org>
       * Martyn Taylor <martyntaylor@apache.org>
       * Matt Pavlovich <mattrpav@apache.org>
       * Michael André Pearce <michaelpearce@apache.org>
       * Francesco Nigro <nigrofranz@apache.org>
       * Robbie Gemmell <robbie@apache.org>
       * Roman Kalukiewicz <romkal@apache.org>
       * Timothy A. Bish <tabish@apache.org>

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Christopher L. Shannon
       appointed to the office of Vice President, Apache Artemis, to serve in
       accordance with and subject to the direction of the Board of Directors
       and the Bylaws of the Foundation until death, resignation, retirement,
       removal or disqualification, or until a successor is appointed.

       RESOLVED, that the Apache Artemis Project be and hereby is tasked with
       the migration and rationalization of the Apache ActiveMQ Artemis
       sub-project; and be it further

       RESOLVED, that the Apache Artemis Project be and hereby is tasked with
       the migration and rationalization of the Apache ActiveMQ Artemis
       Console sub-project; and be it further

       RESOLVED, that all responsibilities pertaining to the Apache ActiveMQ
       Artemis sub-projects encumbered upon the Apache ActiveMQ Project are
       hereafter discharged.

       Special Order 7B, Establish the Apache Artemis Project, was
       approved by Unanimous Vote of the directors present.

    C. Establish the Apache Wayang Project

       WHEREAS, the Board of Directors deems it to be in the best interests of the
       Foundation and consistent with the Foundation's purpose to establish a Project
       Management Committee charged with the creation and maintenance of open-source
       software, for distribution at no charge to the public, related to cross-engine
       data processing that aims at (i) decoupling applications from underlying data
       processing engines, such as Apache Flink, Apache Spark, databases, or ML
       systems, and (ii) automatically determining the optimal combination of engines
       to execute a given data pipeline using an optimizer.

       NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
       (PMC), to be known as the "Apache Wayang Project", be and hereby is
       established pursuant to Bylaws of the Foundation; and be it further

       RESOLVED, that the Apache Wayang Project be and hereby is responsible for the
       creation and maintenance of software related to cross-engine data processing
       that aims at (i) decoupling applications from underlying data processing
       engines, such as Apache Flink, Apache Spark, databases, or ML systems, and
       (ii) automatically determining the optimal combination of engines to execute a
       given data pipeline using an optimizer; and be it further

       RESOLVED, that the office of "Vice President, Apache Wayang" be and hereby is
       created, the person holding such office to serve at the direction of the Board
       of Directors as the chair of the Apache Wayang Project, and to have primary
       responsibility for management of the projects within the scope of
       responsibility of the Apache Wayang Project; and be it further

       RESOLVED, that the persons listed immediately below be and hereby are
       appointed to serve as the initial members of the Apache Wayang Project:

       * Alexander Alten      <aloalt@apache.org>
       * Calvin Kirs          <kirs@apache.org>
       * Jean-Baptiste Onofré <jbonofre@apache.org>
       * Juri Petersen        <juri@apache.org>
       * Kaustubh Beedkar     <kbeedkar@apache.org>
       * Mads Sejer Pedersen  <sejer@apache.org>
       * Mirko Kämpf          <kamir@apache.org>
       * Yasser Idris         <yidris@apache.org>
       * Zoi Kaoudi           <zkaoudi@apache.org>

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Zoi Kaoudi be appointed to the
       office of Vice President, Apache Wayang, 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; and be it further

       RESOLVED, that the Apache Wayang Project be and hereby is tasked with the
       migration and rationalization of the Apache Incubator Wayang podling; and be
       it further

       RESOLVED, that all responsibilities pertaining to the Apache Incubator Wayang
       podling encumbered upon the Apache Incubator PMC are hereafter discharged.

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

    D. Decision Regarding 401k Matching and Profit Sharing

       WHEREAS, the 401k plan adopted by the Foundation, provided to
       its US employees via ADP TotalSource and Voya, requires a formal
       end of year decision regarding 401k contribution matching and
       profit sharing;

       NOW, THEREFORE, BE IT RESOLVED, that no 401k contribution matching,
       nor profit sharing, will occur during Plan Year 2025.

       Special Order 7D, Decision Regarding 401k Matching and Profit
       Sharing, was approved by Unanimous Vote of the directors present.

    E. Change the Apache ServiceComb Project Chair

       WHEREAS, the Board of Directors heretofore appointed Bao Liu
       (liubao) to the office of Vice President, Apache ServiceComb, and

       WHEREAS, the Board of Directors is in receipt of the resignation of Bao Liu
       from the office of Vice President, Apache ServiceComb, and

       WHEREAS, the Project Management Committee of the Apache ServiceComb project
       has chosen by vote to recommend Zhangjian He (hezhangjian) as the successor to
       the post;

       NOW, THEREFORE, BE IT RESOLVED, that Bao Liu is relieved and discharged from
       the duties and responsibilities of the office of Vice President, Apache
       ServiceComb, and

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

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

8. Discussion Items

    A. Schedule the annual members meeting

       The proposed date is Thu, March 5th 2026 at 20:00 UTC
       https://s.apache.org/f0cs7

       Note that the intent to run the meeting like last year: a single
       meeting slot in which voting results are announced. Questions
       regarding voting, as well as any other topics are ideally managed
       asynchronously in fora that are for-purpose.

9. Review Outstanding Action Items

    * Greg: clarify community overlap with Mifos and state of community
          [ Fineract 2025-07-16 ]
          Status: Ongoing. James Dailey has indicated progress on creating distinct identities of Apache Fineract, and Mifos.

    * JB: pursue potential Attic for CarbonData
          [ CarbonData 2025-08-20 ]
          Status: I started a discussion:
                  https://lists.apache.org/thread/jf385z0yw00kfjqgg58yfwg3s30sz6k5

    * JB: pursue a roll call for Velocity
          [ Velocity 2025-08-20 ]
          Status: https://lists.apache.org/thread/j6yw7w18j22yx1qdkj4z4xgrf6961blw

    * Zili: ask Doris PMC to address issues raised by Brand Management in next quarterly report
          [ Doris 2025-10-15 ]
          Status: See https://lists.apache.org/thread/md36fnsfdxsbs3jqtxf8c30wy5v2bbl6. Waiting on Doris PMC report and follow up.

    * Justin: pursue a roll call for MADlib
          [ MADlib 2025-10-15 ]
          Status: , waiting for PMC response.

    * Sander: discuss Policy for Inactive Committers with project PMC
          [ NiFi 2025-10-15 ]
          Status: https://lists.apache.org/thread/wnph5t6xn9rts4smhtd2gmfpjktyqjv8

    * Shane: discuss Attic with Olingo PMC
          [ Olingo 2025-10-15 ]
          Status: In progress: very low response from PMC, but we should probably let dev@ know before attic'ing to be polite.  Suggest attic next month.

    * Greg: pursue a roll call for Pinot
          [ Pinot 2025-10-15 ]
          Status: Failed Roll Call. Two (2) responses in 8 days.

10. Unfinished Business

11. New Business

12. Announcements

13. Adjournment

    Adjourned at 22:57 UTC


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

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

Covering the period October 2025

* ISSUES FOR THE BOARD

No issues.


* OPERATIONS

Responded to the following queries, liaising with projects as required:
- Provided advice to a vendor looking to name a SaaS offering for an ASF
  project.
- Approved the use of the CASSANDRA logo in an architecture diagram.
- Approved a name search for ARTEMIS.
- Approved the use of the GLUTEN mark for a conference.
- Denied a request to use the ASF logo as part of a vendor's bid for a US
  Government contract. Suggested the project logos could be used, if used
  appropriately.
- Approved a request to create some NETBEANS stickers.


* REGISTRATIONS

Continue to work with GRAILS to transfer marks to the ASF.

HBASE, CTAKES, MANIFOLDCF and TOMCAT registrations have been renewed in the
US.

Working with counsel to transfer the BIFROMQ marks to the ASF.

Working with counsel to transfer the SEATA marks to the ASF.

Started the process to register the new logo in the US.


* INFRINGEMENTS

Worked with a vendor to correct some misrepresentations in their support for
EOL software offering.

Kafka resolved a naming issue with a non-ASF project.

Fineract addressed an issue with an "Apache Fineract" organisation being
created on GitHub.

No progress regarding a potential infringement of PDFBOX.

No progress regarding a site with a possible infringement of APISIX.

No update on the formal trademark infringement complaint submitted to GitHub
regarding an NPM package on behalf of the logging PMC.

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

No further progress for IOTDB.

No progress for The KAFKA PMC in addressing a potential infringement of KAFKA.

No progress working with the XMLGRAPHICS PMC to resolve a potential
infringement of FOP.


-----------------------------------------
Attachment 2: Report from the VP of Fundraising  [Bob Paulin]

1) ASF Sponsors:

a —New: we are onboarding two organizations that will be recognized as both
Sponsors and corporate contributors.

b —Renewals: we have secured renewals with one Platinum, two Gold, four Silver
(two of which have downgraded from Gold), and two Bronze Sponsors.

c —Payments: 1 —New: no new Sponsorship payments have been received. 2
—Received: we received Sponsorship renewal payments from one Platinum and one
Bronze Sponsor. 3 —Incoming: we await renewal payments from two Platinum,
three Gold, three Silver, and two Bronze Sponsors.

2) Targeted Sponsors: we have renewed three Targeted Sponsors, and continue
our end-of-year renewal engagement.

3) Sponsor Relations: in addition to onboarding two new Sponsors + corporate
contributors, our standing outreach and renewal activities continue per usual.
We will be holding our Q4 call with Gold and Platinum Sponsors in December and
plan to highlight the ASF Tooling Initiative. Additionally, we are in
discussions with two potential new backers of the Tooling Initiative.

4) Event Sponsorship: we are finalizing the remaining sponsorships from
Community Over Code North America and have begun discussing sponsorship
options for 2026.

5) Individual Donations and Corporate Giving: we received $1,270 in online
donations via https://donate.apache.org/ .

6) Administrivia: we continue to work closely with ASF Treasury, Accounting,
and Marketing & Publicity teams. There are no outstanding issues at this time.


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

Foundation Comms

* Produced October issue of Plus One newsletter
   * Subscriber list now totals 381 (186 new subscribers in October)
   * Total sent: 258 | Unique opens: 100 | Open rate: 39%
* Published and promoted blog in collaboration with Fundraising team to raise
  awareness around corporate contributions
* Published and promoted blog to tout Apache Trusted Releases platform
  beginning second Alpha Omega phase

Project Comms

* Developed and issued press release announcing Apache DevLake and Apache
  Grails as new Top-Level Projects
* Began writing case study highlighting DiDi Global’s use of Apache Ozone
* Collaborated with Apache Grails PMC to develop and issue press release
  touting a major milestone release - 7.0

Brand Project

* Completed blog redesign of news.apache.org
* Finalized Phase II of brand assets including social media graphics,
  snackable images, sponsorship badges, letterheads, emeritus, ICLA,  and
  business cards
* Continued outreach to third-party partners (e.g., Eclipse, Ecma) to request
  logo updates
* Began integrating new brand assets across social media channels and
  Apache.org blog postings
* Continued coordination between Apache projects and designer to update logos
  that contain feather or native imagery
* Added Brand Assets page to the private wiki for sharing templates that all
  members and officers may use
* Developed strategy and execution outline for social media giveaway contest
  (coordinated with Legal) to encourage community engagement and excitement
   around the new ASF logo

Social Media Overview

The highest performing pieces of content for October included the Community
Over Code video recap provided by Even Media and HeroDevs and news of Apache
DevLake and Apache Grails becoming Top-Level Projects.

Social Highlights (X + LinkedIn + Bluesky)

* Total Audience: 145,954
   * New Followers in September: 565
      * X: 10
      * Bluesky: 39
      * LinkedIn: 516
* Total Posts: 77
   * X: 27
   * Bluesky: 27
   * LinkedIn: 16
* Total Engagements: 3,373

Website Analytics

* 730,844 visits, 730,838 unique visitors -5.1%
* 2 min 54s average visit duration -5.9%
* 60% visits have bounced (left the website after one page) +1.7%
* 5.7 actions (page views, downloads, outlinks, internal site searches) per
  visit +18.8%
* 3,612,156 pageviews, 903,525 unique pageviews +13.6%
* 10 total searches on your website, 8 unique keywords -65.5%
* 163,752 downloads, 111,210 unique downloads -12.3%
* 378,548 outlinks, 179,251 unique outlinks +31.8%


-----------------------------------------
Attachment 4: Report from the VP of Infrastructure  [Danny Angus]

General
=======

Updates to the ASF email infrastructure are planned for rollout 20
November 2025. The updates will improve delivery to gmail, outlook,
and other hosted domains who have increased the rigor of their inbound
mail rejection policies. Once the updates have been rolled out, Infra
will begin planning for full DKIM signing of all outgoing email. More
information is available from the Infra announcement message:

https://lists.apache.org/thread/4709w2rt5o3yjd0kpmtm8kvhs778ycmn

DDOS
====

Infra service availability has been spotty due to a world-wide large
scale DDOS attack. Significant efforts are underway to identify and
block the problematic traffic.

MFA Efforts
===========

An internal demo of the POC for Authentik MFA presented at the
November Infra Roundtable was well received. Members of Tooling,
Security, Infra, and several project representatives were present.
Rollout of the service is planned for end-of-year, with opt-in
onboarding as the initial target. A full implementation roadmap and
timeline will be presented in December.

Major Projects
==============

- Atlassian:
  - Confluence Upgrades in progress to achieve cloud feature parity
    and improve existing on-prem service
  - Jira/Confluence Atlassian Cloud Migration Testing continues

- Major infrastructure operating system upgrades to improve security
  posture and reduce technical debt.

- Ongoing MFA testing and deployment automation buildout


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

# Tooling

The team continues to work hard building systems.

## Apache Trusted Releases (ATR)

The ASF published a blog post announcing the second alpha. The announcement
included information about how to contribute to the stack. The alpha is going
very well.

Our current development focus is on the following tasks.

1. Supporting PMC Alpha 2 testing with bug fixes and feature improvements
2. ASVS security review and necessary fixes
3. Changes needed for proper production configuration

## Board Agenda Tool (BAT)

The tool is now stable and essentially complete. There are some improvements
waiting for volunteer developer time. Please let the tooling team know if
there are any urgent issues.

## Secretary's Workbench

The repository is now open to all foundation members. Per a conversation with
the Chair at the C/C Conference the Roster tool is in scope. While our focus
is on ATR, we will validate if the requirements differ from the current Whimsy
implementations.

## Staffing

We are still searching for a replacement developer. We are getting some
support from volunteers.


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

Met with cvent to discuss possibly switching to their call-for-presentation
system for future events, so we have one unified system to handle sessions and
registration, vs. two. Waiting for a bid to consider.

Continuing to explore potential venues in EU and UK for Community Over Code EU
2026. Several bid requests sent to venues, bids are still coming in.

Planners met with Lisa Cao to discuss possibility of doing one or two smaller
"roadshow"-like events in 2026. These events could be smaller (one- to
 three-tracks, probably single-day) and be held at venues with lower costs
 requirements, such as academic and public venues. Still finalizing the
 details.

Met with VP, Fundraising and VP, Sponsor Relations to confirm we will continue
the corporate sponsor/conference sponsorship program


-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee  [Gavin McDonald]

Current Events
============== 
None currently.

Monthly Meetings
================ 
Monthly Meetings on hold until another event comes up

TAC App
======= 
TAC app is currently closed.

Future Events
============= 
None currently. Looking into opening up for FOSDEM for a few <6
committers to attend.

Short/Medium Term Priorities
============================ 
Keeping an eye out for other smaller events to support. 
Post surveys for Bratislava, Hangzhou, Denver, 
Beijing and Minneapolis still to be done.

Mailing List Activity
===================== 
No activity this month.

Membership
========== 
No changes to the Committee this month.


-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion  [Daniel Gruno]

Due to other engagements, I have not had the time to prepare a report for this
month, but will follow up with more zest next month.


-----------------------------------------
Attachment 9: Report from the VP of Data Privacy  [Christian Grobmeier]


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

CRA / Europe

With the exception of the horizontal standards - things continuing & no major
concerns. With the open source community slowly but surely building a very
usable set of documents at https://github.com/orcwg.

The `article 25' attestation programmes for open source foundations is picking
up steam; with a fair amount of appetite among our peers and their downstream
communities to do this. And a good workshop in Brussels
(https://github.com/orcwg/cra-attestations,
https://github.com/sCC4CRA/sCC4CRA).

The earlier reported, strongly felt, aspect of punishing downstream
freeloaders appears to make place for a, from a community perspective, more
healthy approach of `what does our (downstream) community need' -- and how
much of that can we do collectively.

I'll be working with our treasurer/legal to make sure that, should some PMCs
in our community want to do the same, that this works within the 503(c)(3)
and other limits (which I expect not to be an issue at all); and that we're
aligned with our peer USA based brethren.

Rest of world

No actions - but I think we're overdue for a sync with our communities in Asia
- to make sure they are aware of the state of play. Will try to reach out.


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

No new activity this month, as the Common Lifecycle Enumeration, Package URL,
and CycloneDX 1.7 proposals await Executive Committee and December General
Assembly decisions.


-----------------------------------------
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
24 issues compared to the last month.

We received a request to review proposed ASF Brand Contest Rules -- plan to be
done with the review by the end of this week.


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

October

* Help Infra with the mailinglist DMARC issues, both to improve the 
deliverability of security-relevant emails and to clear the path for ongoing 
MFA work.

* Complete coaching Geode towards a release and disclosure of fixed security 
issues - the project is now back to health security-wise.

* Various discussions on how MFA and more fine-grained credentials can improve 
our operational security going forward.

* A ransomware group announced they are going to release a cache of documents 
relating to Apache OpenOffice.  There has been no reported ransom demand 
within the Foundation or from the project, and much of the data types 
described in the claim are ones we do not collect or own.  We continue to 
monitor the situation and work with the markpub team on reactive press 
statements.

Stats for October 2025:

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

Security reports: 66 (last months: 103, 99, 119)

        10	['website or other infrastructure']
        7	['tomcat']
        6	['logging']
        5	['airflow', 'httpd']
        3	['commons', 'iotdb', 'superset']
        2	['seatunnel', 'spark']
        1	['ambari', 'apisix', 'bigtop', 'camel', 'causeway', 'directory', 
        'dolphinscheduler', 'dubbo', 'fory', 'freemarker', 'guacamole', 
        'hive', 'hop', 'kie', 'maven', 'ofbiz', 'orc', 'shardingsphere', 
        'solr', 'texera']

In total, as of 3rd November 2025, we're tracking 244 (last months: 264,
249) open issues across 79 projects, median age 100 days (last months:
71, 83). 78 of those issues have CVE names assigned. 23 (last months:
20, 25) of these issues, across 10 projects, are older than 365 days.

* fineract (Health amber): there are a number of open issues approaching a 
year old. The PMC has started to make progress and has made documentation 
and architectural changes, with more focus expected to close out these 
issues. (Last update: 2025-10-08)

* openoffice (Health amber): Several issues in OpenOffice are over 365 days 
old. They are not severe enough to warrant stopping distribution of 
OpenOffice, and there is progress on finding an architectural improvement to 
fix them, but we actively work to improve the projects' ability to respond 
to security issues going forward.  A release fixing a number of 
long-standing issues is in progress and expected in the coming days. 
(Last update: 2025-11-10)

* spark (Health amber): the project is not responsive to security issues 
(Last update: 2025-10-15)

* thrift (Health amber): the PMC does not appear to have the bandwidth to 
triage incoming reports in a timely fashion, or accept help with this. 
(Last update: 2025-11-07)


-----------------------------------------
Attachment A: Report from the Apache AGE Project  [Jeff Jirsa]

## Description:
The mission of Apache AGE is the creation and maintenance of software related 
to a multi-model database that enables graph and relational models built on 
PostgreSQL

## Project Status:
Current project status: Ongoing, but low activity
Issues for the board: None at this time

## Membership Data:
Apache AGE was founded 2022-05-17 (3 years ago)
There are currently 19 committers and 13 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 Jeff Jirsa on 2025-05-11.
- No new committers. Last addition was Jeff Jirsa on 2025-05-12.

## Project Activity:
In August, this report noted that the first commits to the primary branch
since September 2024 landed in May, and have accelerated in August. Commits
continue to trickle in, though the number of unique contributors is low.

The project approved two releases:

PG17-1.6.0 was released on 2025-10-12. PG16-1.6.0 was released on 2025-09-16.

The last release before these was 2024-03-19.


## Community Health:
Contribution volume is low, but increasing.


-----------------------------------------
Attachment B: Report from the Apache Airavata Project  [Suresh Marru]


-----------------------------------------
Attachment C: Report from the Apache Ambari Project  [Brahma Reddy Battula]


-----------------------------------------
Attachment D: Report from the Apache Ant Project  [J Pai]

## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build
system and related software components.

It consists of the following main projects:

- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager

## Project Status:
Current project status: Primarily in bug fix mode and maintenance mode.
Issues for the board: None for now.

## Membership Data:
Apache Ant was founded 2002-11-18 (22 years ago)
There are currently 29 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.

Community changes, past quarter:
- No new PMC members. Last addition was Magesh Umasankar on 2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-15.


## Project Activity:
The primary goal of Ant these days is to make sure that it can be used
to build projects using recent releases of Java. Ant 1.10.15 was
released on 29th August 2024 and that's our latest version of Ant.

Ivy 2.5.3 has been released on 23rd December 2024 which is our latest
version of Ivy.

Some minor bug fixes have accumulated in the Ant project since the
last release, so we might consider doing a release in the upcoming
weeks.

## Community Health:
Although we don't see too much development activity in Ant,
there are several active users of the Ant build tool. We
occasionally also see pull requests on GitHub.
For a project that's in maintenance mode, our amount of
activity, we believe, is decent.


-----------------------------------------
Attachment E: Report from the Apache Avro Project  [Ryan Skraba]

## Description:

Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema-driven serialized data. The unique
features of Avro include automatic schema resolution: when the reader's
expected schema is different from the actual schema with which the data was
serialized the data is automatically adapted to meet reader's requirements.

## Project Status:
Current project status: Ongoing
Issues for the board: Declining PMC and committer engagement

## Membership Data:

Apache Avro was founded 2010-04-21 (16 years ago) There are currently 38
committers and 25 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 Oscar Westra van Holthe - Kind on
  2024-08-27.
- No new committers. Last addition was Christiaan Biesterbosch on 2025-08-04.

We have had two graceful PMC resignations, but that's not really an issue or
unexpected for a long-lived project.

## Project Activity:

We had a release for the Rust SDK this quarter, and managed to do two minor
releases for the other language SDKs, addressing the accumulated bug and
security fixes. This has been long-awaited. We've seen some improvements to
the release process but it still remains a chore for the release manager, and
it can take some time to get enough votes to validate the release candidate.

## Community Health:

Mailing Lists:
- dev@avro.apache.org had 339 emails (+7% change)
- issues@avro.apache.org (mostly notifications) had 496 emails (-3% change)
- user@avro.apache.org continues to have very little traffic

JIRA:
- 25 issues opened (-41% change)
- 16 issues closed (-69% change)

Code Repository:
- 47 commits in the past quarter (-34% change)
- 13 code contributors in the past quarter (-48% change)

GitHub:
- 78 PRs opened on GitHub, past quarter (5% change)
- 81 PRs closed on GitHub, past quarter (-32% change)

Community activity is in line with our expectations, but we need to be more
reactive to pull requests and issues.


-----------------------------------------
Attachment F: Report from the Apache BookKeeper Project  [Enrico Olivelli]


-----------------------------------------
Attachment G: Report from the Apache Brooklyn Project  [Juan D. Cabrerizo]

## Description:
The mission of Apache Brooklyn is the creation and maintenance of software 
related to a software framework for modeling, monitoring and managing cloud 
applications through autonomic blueprints.

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

## Membership Data:
Apache Brooklyn was founded 2015-11-18 (10 years ago)
There are currently 20 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Iuliana Cosmina on 2021-06-04.
- No new committers. Last addition was Mykola Mandra on 2022-03-08.

## Project Activity:
Fixed identified bugs on:
* duration calculation
* password generator

## Community Health:
The team keeps offering support and the user community has contacted the
mail list for reporting issues that have been addressed.

Some documentation changes have been proposed and need to be discussed as part
future updates


-----------------------------------------
Attachment H: Report from the Apache BuildStream Project  [Tristan Van Berkom]


-----------------------------------------
Attachment I: Report from the Apache BVal Project  [Matt Benson]


-----------------------------------------
Attachment J: Report from the Apache CarbonData Project  [Jacky Li]


-----------------------------------------
Attachment K: Report from the Apache Cassandra Project  [Ekaterina Dimitrova]

-----------8<----------

> Are you able to provide adequate oversight of your project? That is, are
> there at least three PMC members who are engaged enough to respond in the
> event of a CVE or similar crisis?

Yes, we maintain adequate project oversight and can address CVEs. Twenty-five
PMC members responded to the last roll call. Numerous PMC members actively
participate in both dev and private list discussions, ensuring that we have
more than the requisite three members available for rapid response to a CVE
or similar event.

> Are there current or upcoming risks that threaten the sustainability of
> your project? This could be anything from a change in employment of
> prolific contributors, to an acquisition affecting a significant corporate
> contributor, to a change in the technology landscape that makes your
> project less (or more) relevant.

We currently do not see any specific risks threatening the project's
sustainability. We are focused on long-term health through deliberate
diversification and expansion of our contributor base.

This quarter, we successfully added 1 new PMC member and 4 new committers,
and another PMC addition is currently under discussion.

Additional indicators of Project Health and Growth this Quarter:

   - Infrastructure: We successfully implemented pre-commit CI (available at
     pre-ci.cassandra.apache.org), made possible by a generous infrastructure
     donation from Amazon.
   - Releases: We shipped new versions of the:
     - Cassandra server
     - Java drivers
     - GoCQL drivers
     - Sidecar
     - dtest-api
   - Community: The PMC supervised several successful new meetups and
     organized a popular and well-attended Cassandra track at ApacheCon.
   - Software grants: The ASF received software grants from DataStax (IBM)
     for python-driver, cpp-driver, nodejs-driver, csharp-driver.  The first
     three are in progress (the latter is still being considered for acceptance
     by the project – if there are enough maintainers for it present).

> What can the Foundation do to more effectively make your project more
> successful in its mission of providing software for the public good?

None at this time
----------->8----------


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


-----------------------------------------
Attachment M: Report from the Apache Celix Project  [Pepijn Noltes]

## Description:
Apache Celix is a framework for C and C++14 to develop dynamic modular
software applications using component and in-process service-oriented
programming. Apache Celix is inspired by the OSGi specification adapted for C
and C++.

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

## Membership Data:
Apache Celix was founded 2014-07-16 (11 years ago)
There are currently 17 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- No new PMC members. Last addition was Peng Zheng on 2022-10-16.
- No new committers. Last addition was Zhenbao on 2022-10-19.

## Project Activity:
- Workflow and code was updated to support MacOS 15, 
  including fixes for additional compiler warnings
- Several fixes (memleak, curl usage, race conditions 

## Community Health:
Development activities have increased again. 
Still a small project with minimal activity, but 
the activities slowly work towards a new release.


-----------------------------------------
Attachment N: Report from the Apache Community Development Project  [Swapnil Mane]

## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects

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

## Membership Data:
Apache Community Development was founded 2009-11-01 (16 years ago)
There are currently 52 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.

Community changes, past quarter:
- No new PMC members. Last addition was Drew Foulks on 2024-08-30.
- No new committers. Last addition was Chris Wells on 2025-04-11.

## Project Activity:

### Google Summer of Code 2025
The GSoC 2025 season has progressed smoothly. Final submission and evaluation
for 25 out of 27 projects have been completed, and the remaining evaluations
will be finished later this week. The final results will be available after the
program ends in November.

The GSoC Mentor Summit 2025 was held in Munich, Germany, and was attended by
our GSoC admin Priya Sharma, who represented the ASF.

### Apache Local Communities (ALC)

#### ALC Taipei
ALC Taipei organized four in-person meetups and knowledge-sharing sessions
this quarter. Activities included technical talks from open-source contributors,
discussions on enterprise adoption of open source, and the chapter’s inaugural
meeting, which gathered more than 100 attendees from domestic companies and
other organizations.

### Community Over Code NA 2025
We had 14 talks in the Community Track at Community Over Code NA 2025. These
sessions were well received and attracted a good audience turnout,
reflecting the continued interest in community-focused topics. Thanks to our
Community Track Chairs Rich Bowen, Sanyam Goel, and Chris Wells for their
support and coordination throughout the event.

## Community Health:
We had a good quarter with active contributions across various areas,
particularly GSoC, ALC activities, and Community Over Code NA. This reflects
strong engagement from our community members.
Although we observed a drop in activity on our dev mailing list, which
was expected, as many community members were occupied with preparations
and participation in Community Over Code NA 2025.


-----------------------------------------
Attachment O: Report from the Apache CouchDB Project  [Jan Lehnardt]

## Description:
Apache CouchDB software is a document-oriented database that can be queried and 
indexed in a MapReduce fashion using JavaScript. CouchDB also offers 
incremental replication with bi-directional conflict detection and resolution.

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

## Membership Data:
Apache CouchDB was founded 2008-11-19 (17 years ago)
There are currently 73 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- No new PMC members. Last addition was Glynn Bird on 2023-03-14.
- No new committers. Last addition was Tony Schmidt on 2025-03-31.

## Project Activity:
- CouchDB has applied to the Sovereign Tech Agency (STA) Bug Resilience
  Programme and has been accepted. The work items being tackled
  under the programme will be developer experience and automated
  testing improvements, that will make CouchDB easier to contribute
  to by new and existing contributors. It will also reduce maintenance
  burden.
  - The STA partner for doing this work is CouchDB PMC Chair Jan Lehnardt’s
    company Neighbourhoodie. Jan has abstained from any project decisions
    about this to avoid a conflict of interest. In addition, the STA is
    aware of all this and all safeguards are in place to avoid any potential
    issues.
- A set of major new features have been merged into main that will address
  very longstanding issues with CouchDB when it comes to storing time-series
  data. We are still refining some configuration API details, but a new feature
  version 3.6.0 will include the new fixes.
- In the meantime, the vote to release bugfix version 3.5.1 is underway at the
  time of writing.

## Community Health:
It’s a normal y/y quarter for CouchDB, development has picked up after the
northern hemisphere summer quarter as per usual.


-----------------------------------------
Attachment P: Report from the Apache Creadur Project  [Philipp Ottlinger]

## Description:
The mission of Creadur is the creation and maintenance of software related to 
Comprehension and auditing of software distributions

## Project Status:
Current project status: Ongoing
Issues for the board: RFC: development of RAT under the tooling umbrella?
As the PMC remains to be rather small I'd like to ask the board for
their insight on the future development of RAT. 
Would it make sense/be possible to support the Creadur PMC
from the tooling project?

## Membership Data:
Apache Creadur was founded 2012-04-18 (14 years ago)
There are currently 11 committers and 10 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 Claude Warren on 2024-01-23.
- No new committers. Last addition was Jean-Baptiste Onofré on 2024-01-23.

## Project Activity:
Apache RAT 0.17 was released on 2025-10-17 with many new changes and
a new webpage, which was a big chunk of work!
Development of RAT 1.0.0 started with architecture discussions.
Subprojects Tentacles and Whisker remain in dormant mode and mostly
only get dependency updates and infrastructure changes.

## Community Health:
Two new contributors started interacting with the PMC/project in order
to get a RAT Gradle plugin and a RAT GitHubAction.
Unfortunately 2 PMC members resigned just after the release vote started 
for RAT 0.17.


-----------------------------------------
Attachment Q: Report from the Apache DataSketches Project  [Lee Rhodes]

## Description:
The mission of Apache DataSketches is the creation and maintenance of software 
related to an open source, high-performance library of streaming algorithms 
commonly called "sketches" in the data sciences. Sketches are small, stateful 
programs that process massive data as a stream and can provide approximate 
answers, with mathematical guarantees, to computationally difficult queries 
orders-of-magnitude faster than traditional, exact methods

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

## Membership Data:
Apache DataSketches was founded 2020-12-15 (5 years ago)
There are currently 18 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 6:5.

Community changes, past quarter:
- Pierre Lacave was added to the PMC on 2025-08-12
- Will Lauer was added to the PMC on 2025-08-12
- No new committers. Last addition was Nikunj Bhartia on 2025-06-11.

## Project Activity:
The datasketches-java (ds-java) library has been moving quickly to keep
pace with the new Java language releases. DS-java 8.0.0 was released in
April supporting Java 21. We are currently busy refactoring the entire
ds-java library to migrate to the new Java FFM API, which had its
first LTS release with the Java 25 this past September. We hope to have
this release out by next quarter.
This migration will eliminate the current dependency on the
datasketches-memory repo, which was created 10 years ago to enable
fast off-heap management of data structures and state-machines.

## Community Health:
Our project is healthy. We have a small, loyal and growing community
of users that contact us when they have questions or issues. We are experiencing
growing interest from major corporations in our multi-language libraries.
The Google adoption is strong evidence of that.

We continue to get interest from scientists around the world who
offer ideas for new sketches for our library based on recent research.


-----------------------------------------
Attachment R: Report from the Apache DB Project  [Bryan Pendleton]

## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software licensed
to the Foundation, for distribution at no charge to the public.

The Apache DB TLP consists of the following subprojects:
 o Derby    : a relational database implemented entirely in Java.
 o JDO      : focused on building the API and the TCK for compatibility
              testing of Java Data Object implementations providing data
              persistence.
 o Torque   : an object-relational mapper for Java.

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

## Membership Data:
Apache DB was founded 2002-07-16 (23 years ago)
There are currently 48 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Max Philipp Wriedt on 2024-07-03.
- No new committers. Last addition was Max Philipp Wriedt on 2023-04-14.

## Project Activity:

Recent releases:
- Torque 7.0 was released on 2025-08-13.
- Torque 6.0 was released on 2024-05-22.
- Derby-10.17.1.0 was released on 2023-11-14.

## Community Health:

The DB community have reached consensus that the Derby software
is no longer actively being maintained and should be retired. 
A public vote on the derby-dev list confirmed that consensus,
and the PMC are working to implement a subset of the Apache Attic
process to reflect that decision and to make the status be clearly
communicated to future visitors of the Db project site.

The JDO and Torque communities do not expect any major issues 
with our use of Derby when the Derby project retires.

The Torque community voted on the Torque 7.0 release and it
was approved and released on 2025-08-13. The Torque developers
are working on a new approach to a performance problem in the 
processRow method of RecordMappers (TORQUE-364).

The JDO team continues to work toward the next release, 3.2.2. 
No date yet but we have a number of fixes and improvements that 
make it seem like a good time to make a dot release. JDO have 
put SBOM creation into the normal build process. Two flavors 
of SBOM have been built. and we expect to incorporate them into 
the release process. The JDO team are working on the alpha version 
of Apache Trusted Release; nothing official yet.

The JDO team helped with the DB project logo update to use 
the Oak Leaf instead of the Feather.


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

## Description:
 Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
 Injection) extensions intended to make application development easier when
 working with CDI and Java EE.  Some of its key features include:

 - A core runtime that supports component configuration, type safe messaging
 and internationalization, and exception handling.
 - A suite of utilities to make programmatic bean lookup easier.
 - A plugin for Java SE to bootstrap various CDI containers.
 - JSF integration
 - JPA integration and transaction support.
 - A Data module, to create an easy to use repository pattern on top of JPA.
 - Testing support to allow low level unit testing of CDI enabled projects.

## Issues
 There are no issues requiring board attention at this time.
 I might add one note regarding to the TLP discussion spanning multiple EE
 projects. There was not much response to the proposal from the other TLPs.
 DeltaSpike passed it's last release with plenty of PMC activity (6 +1) and 
 thus I'll likely will not push further towards it. Ofc if there is a need 
 again then it feels like the most sensitive route to pursue.

## Activity
 The last quarter was really quiet. After the last release we mostly
 updated out site and cleaned up documentation.

## Community changes, past quarter:
- No new PMC members. Last addition was Harald Wellmann on 2016-05-19.
- Thomas Frühbeck was added as committer on 2024-02-05

## Recent releases:
 - 2.0.1 (JakartaEE) was released on 2025-08-11.
 - 2.0.0 (JakartaEE) was released on 2024-04-10.
 - 1.9.6 was released on 2022-04-12.


-----------------------------------------
Attachment T: Report from the Apache DevLake Project  [Hezheng Yin]


-----------------------------------------
Attachment U: Report from the Apache DolphinScheduler Project  [Lidong Dai]

## Description:
Apache DolphinScheduler is a cloud-native workflow orchestration platform with
powerful user interface, dedicated to solving complex task dependencies in the
data pipeline and providing various types of jobs available `out of the box`

## Project Status:
Current project status:Health issues for the board: There are no issues for
the board at this time

## Membership Data:
Apache DolphinScheduler was founded 2021-03-17 (5 years ago) There are
currently 59 committers and 27 PMC members in this project. The
Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Xin Cheng on 2024-06-18.
- No new committers. Last addition was Hengliang Tan on 2024-07-02.

## Project Activity:
- 3.3.2 was released on Oct 30. 
- 3.3.1 was released on Aug 25. 
- 3.3.0-alpha was released on April 9. 

## Community Health:
- We have held two community online Meetups in last quarter.
- 65 commits in the past quarter(2025-08-03 - 2025-11-02)


-----------------------------------------
Attachment V: Report from the Apache Doris Project  [Mingyu Chen]

## Description:
The mission of Apache Doris is the creation and maintenance of software
related to a MPP-based interactive SQL data warehousing for reporting and
analysis

## Project Status:

Current project status: Ongoing

Issues for the board: No

## Membership Data:

Apache Doris was founded 2022-06-15 (3 years ago) There are currently 89
committers and 25 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:1.

Community changes, past quarter:
- Gavin Chou was added to the PMC on 2025-09-12
- Wenchi Wu was added as committer on 2025-09-23
- Siyu Yang was added as committer on 2025-11-07
- Zhen Chen was added as committer on 2025-11-03

## Project Activity:

Software development activity:

 - We released a major 4.0.0 on 2025-10-14, and following bug fixed version
   4.0.1 on 2025-11-08
 - We also released a bug fixed version 3.1.2 and are preparing to release
   3.1.3

Meetups and Conferences:

 - We held the Doris Summit 2025 Virtual on November 4–5, 2025, with around
   30,000 online attendees joining more than 40 sessions.

## Community Health:

Overall, the community is in great health. We now have more than 700
contributors, and we also co-host or participate in in-person meetups in North
America — such as Iceberg Meetups, to connect and exchange ideas with people
from other communities.

## Remaining Issues:

- Branding issue: There is still an existing "x2doris" name in some of Doris'
  website materials. SelectDB expect to retire this branding next quarter.
- Materials: Doris PMC will upload and maintain the updated materials on the
  nightlies going forward.


-----------------------------------------
Attachment W: Report from the Apache Drill Project  [Charles Givre]

## Description:
The mission of Drill is the creation and maintenance of software related to 
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage

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

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

Community changes, past quarter:
- Maksym Rymar was added to the PMC on 2025-09-30
- No new committers. Last addition was Maksym Rymar on 2022-10-19.

## Project Activity:
* 1.22.0 was released on 2025-06-28.
* 1.21.1 was released on 2023-04-29.
* 1.21.0 was released on 2023-02-21.

Since the release of Drill 1.22, there have been some significant updates both 
committed and in progress. Many of these are what I would classify as
"major surgery", even though they do not sound like it.  As a result of these
updates, the next version of Drill drops support for Hadoop 2, and Java 8
and 11.

Additionally, we are working on updating Drill's Hive dependencies which have 
not been updated in some time.  Drill currently has dependencies for Hive 3.1.x
for which there are many CVEs and requires Java 8.  Updating Drill's dependency
to Hive 4 is a major update and requires a complete refactoring of the test 
infrastructure for this plugin.  It is in progress but we do not have a PR
yet for that. 

(Merged)
* DRILL-3962: Add Support For ROLLUP, CUBE, GROUPING SETS, 
GROUPING, GROUPING_ID,GROUP_ID (Merged)
* DRILL-8534: Update Kafka to 3.9 / 3.9.1 (Non-trivial update)
* DRILL-8531: Update Libraries due to CVEs (Non-trivial updates)
* DRILL-8528: HBase Limit Pushdown 

(In Progress)
* DRILL-8540: Update Jetty to Version 12 (Non-trivial update)
* DRILL-8474: Apache Daffodil Integration 
* DRILL-8537: Update Calcite (Very Non-Trivial Update)


## Community Health:
Note that we do not have metrics for our Slack channel. 

* dev@drill.apache.org had a 7% increase in traffic in the past quarter 
(128 emails compared to 119)
* user@drill.apache.org had a 50% increase in traffic in the past quarter 
(15 emails compared to 10)
* 12 JIRA tickets opened and 0 closed in the past quarter.


-----------------------------------------
Attachment X: Report from the Apache Druid Project  [Abhishek Agarwal]

Report date: 2025-11-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, Hadoop and 
Iceberg as
data sources, Avro, ORC, or Parquet as supported data input formats, and
DataSketches for scalable approximate algorithms. Druid can also be used as a
data source by Superset. 

## Project Status

Ongoing - with High activity

### Issues

There are no issues requiring board attention at this time.

### Recent releases
 - 34.0.0, a major release, on 2025-08-11.

## Project Activity

Our last major release was Druid 34.0.0, which contained 270 new features, 
bug fixes, performance enhancements, documentation improvements, 
and additional test coverage from 48 contributors. 
Druid typically does major releases 3–4 times a year. 
This release had many more contributions compared to the release before (190). 

## Community Health
Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at 3,314
members, up 91 members since our last report. This number is similar to the 
kind of members growth we have seen so far. 
Slack is our most active channel for user support and usage-oriented 
discussions. As before, development discussions
happen more on GitHub, and sometimes on the dev mailing list. 


We removed the support for Java 11 but were able to retain the Hadoop 
integration that is still used by many community members.

We recently merged in druid-operator, commonly used to run druid on kubernetes, 
into the mainline druid repo. Many community members came forward and 
helped push this effort. 

### Development activity by the numbers

Since the last report on 11th August
 - 287 commits from 36 contributors
 - 370 pull requests opened
 - 315 pull requests merged/closed

These numbers are similar to what was reported in the previous quarter.


## Membership Data

Apache Druid was founded 2019-12-17 (8 years ago)
There are currently 73 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

We haven't added any PMC or committer since last report though we did start a
discussion thread to make druid-operator contributors committers. Now that
project is completed, we can proceed with formal voting thread. Though this
still requires some attention and we do need to find more potential 
committers.


-----------------------------------------
Attachment Y: Report from the Apache Dubbo Project  [Jun Liu]


-----------------------------------------
Attachment Z: Report from the Apache Empire-db Project  [Rainer Döbele]

## Description:
Empire-db is a lightweight relational database access library dealing with all
aspects of storing, manipulating, retrieving and modelling data in relational
database management systems (RDBMS). As an alternative to traditional
OR-Mapping solutions, it provides an SQL centric, no-compromise approach that
uses a Java-Object-Model rather than Mapping Files or Annotations.

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

## Membership Data:
Apache Empire-db was founded 2012-01-24 (14 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.

Community changes, past quarter:
- No new PMC members. Last addition was Jan Glaubitz on 2016-07-10.
- No new committers. Last addition was Ralf Eichinger on 2022-03-15.

## Project Activity:
Latest release is empire-db-3.4.0 released on 2025-10-22.
We are happy to announce that we have been able to complete
and approve 16 improvments and 6 bugfixes which we have
published with our latest release on Oct. 22.

## Community Health:
Our community is still alive and healthy.
6 JIRA tickets opened and 26 closed in the past quarter.
A new Jira ticket has been created by a non-committer and 
a new Jira account has been requested by a new user.


-----------------------------------------
Attachment AA: Report from the Apache EventMesh Project  [Eason Chen]

## Description:
The mission of Apache EventMesh is the creation and maintenance of software 
related to a fully serverless platform used to build distributed event-driven 
applications

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

## Membership Data:
Apache EventMesh was founded 2023-03-22 (2 years ago)
There are currently 54 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.

Community changes, past quarter:
- No new PMC members. Last addition was Jianbo Liu on 2024-01-05.
- No new committers. Last addition was Zikang Chen on 2025-01-28.

## Project Activity:
For AI agent and workflow feature is under developing
Part of new feature EventMesh Dashboard has been merged.
Enhancement for EventMesh netty io thread improve has been merged.


## Community Health:
The new features were under designing or developing,
so the commits and PR activity seems decrease.
Contributors increased slightly compared to the previous quarter.
Overall community health is good.


-----------------------------------------
Attachment AB: Report from the Apache FreeMarker Project  [Dániel Dékány]

## Description:

Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.

FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

Activity was very low in recent months.

## Health report:

Activity was very low in recent months. User questions (mostly on
StackOverflow) and new Jira issues are still being answered. Most PR-s slowly
but eventually getting reviewed and merged. Next goal is to do the next minor
release as enough smaller changes accumulated. Bigger task still unfinished in
2.x line is the java.time support (FREEMARKER-35). The even longer term goal
is continuing the ongoing development on the 3.0 branch, so that the project
can innovate, and the code base can become more modern and attractive for new
committers.

## PMC changes:

 - Currently 9 PMC members.
 - Last added on 2025-01-01

## Committer base changes:

 - Currently 12 committers.
 - Last added (non-PMC): Siegfried Goeschl on 2020-01-07

## Releases:

 - 2.3.34 was released on 2024-12-22


-----------------------------------------
Attachment AC: Report from the Apache Geode Project  [Mark Bretl]

## Description:
The mission of Apache Geode is the creation and maintenance of software related 
to a data management platform that provides real-time, consistent access to 
data-intensive applications throughout widely distributed cloud architectures.

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

## Membership Data:
Apache Geode was founded 2016-11-15 (9 years ago)
There are currently 121 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.

Community changes, past quarter:
- Jinwoo Hwang was added to the PMC on 2025-09-19
- William Hodges was added to the PMC on 2025-09-25
- Arnout Engelen was added as committer on 2025-08-14
- William Hodges was added as committer on 2025-09-26

## Project Activity:
The community came together and released version 1.15.2, the first Geode
version in three years. The release included many security fixes and
dependency updates. The community is now planning release 2.0, which will
focus on new features and upgrading JDK versions

## Community Health:
The community is doing well and currently in a healthy state. After the
release of 1.15.2, we added two new PMC members who were key contributors and
continuing to see involvement from new committers. While the last release was
focused on fixing items, there is interest to make Geode better and create new
features.


-----------------------------------------
Attachment AD: Report from the Apache Grails Project  [James Fredley]

## Description:
The mission of Apache Grails is the creation and maintenance of software 
related to the development of a powerful Groovy-based web application framework 
for the JVM built on top of Spring Boot

## Project Status:
Current project status: Ongoing With high activity
Issues for the board: No issues requiring board attention at this time.

## Membership Data:
Apache Grails was founded 2025-09-23 (2 months ago) 
There are currently 16 committers and 12 PMC members in this project. 
The Committer-to-PMC ratio is 4:3.

Community changes, past quarter: 
No new PMC members (project graduated
recently). Walter Duque de Estrada added 8/25/2025 
Committers: Thomas Rasmussen added 8/25/2025, Jonas Pammer added 9/4/2025

## Project Activity:
Recent releases:
CORE-7.0.2 was released on 2025-11-10.
CORE-7.0.1 was released on 2025-11-02.
SPRING-SECURITY-7.0.0 was released on 2025-10-28.
REDIS-5.0.0 was released on 2025-10-22.
QUARTZ-4.0.0 was released on 2025-10-20.
CORE-7.0.0 was released on 2025-10-19.
GRAILS-PUBLISH-0.0.2 was released on 2025-10-13.
ACTIONS-1.0.1 was released on 2025-10-12.

## Community Health:
Overall, community activity has increased this quarter. The project has
generated significant buzz around graduation and three 7.0.x releases with
many end users submitting issues and pull requests, as they upgrade.

Apache Grails 7.0.0 was features a press release from M&P and was included in
PlusOne Newsletter and current episode of Podcast.

The Apache Grails website is now consistently a top 20 site, based on
analytics.apache.org.


-----------------------------------------
Attachment AE: Report from the Apache Groovy Project  [Paul King]

## Description:

Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language

## Project Status:

Current project status: Ongoing with moderate activity.
Issues for the board: No issues requiring board attention at this time.

## Membership Data:

Apache Groovy was founded 2015-11-18 (10 years ago).
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Soeren Glasius on 2024-11-06.
- No new committers. Last addition was Sergio del Amo on 2024-12-20.

## Project Activity:

4.0.29 was released on 2025-10-18.
5.0.2 was released on 2025-10-18.
geb-8.0.0 was released on 2025-09-12.
5.0.1 was released on 2025-09-10.
5.0.0 was released on 2025-08-24.

## Community Health:

Overall, community activity in terms of commits, PRs, issues fixed, and
mailing list activity was about average this quarter. But despite average
statistics, it was not average in terms of excitement with four significant
highlights for the quarter.

Several years in the making, the project released Groovy 5 with 400+ changes
since Groovy 4. We see encouraging signs on Groovy 5 adoption as numerous
downstream projects look like upgrading to Groovy 5 soon. Early planning for
Groovy 6 will commence shortly.

The Geb subproject had its first release as part of the ASF. Further work is
underway to streamline releases. Some of those involved in Geb who aren't
already Groovy committers are good candidates for future committers.

Work helping Grails on their incubation journey is complete in the sense that
their graduation was approved at the last board meeting. They were a joy to
work with and we wish them every success going forward. We still anticipate
working very closely with the Grails project.

We had an exciting time contributing to the Community over Code NA conference
in Minneapolis in September. Talks on Groovy, Geb and Grails featured in the
Groovy and Incubator tracks. We wish to thank all of the organisers and
participants for making the event so worthwhile.


-----------------------------------------
Attachment AF: Report from the Apache Hadoop Project  [Xiaoqiao He]

## Description:

The mission of Hadoop is the creation and maintenance of software related to
Distributed computing platform

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

## Membership Data:
Apache Hadoop was founded 2008-01-16 (17 years ago)
There are currently 248 committers and 126 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- Suhail Ahmar was added as PMC on 2025-10-14.
- Jian Zhang was added as committer on 2025-03-10.

## Project Activity:
3.4.2 was released on 2025-08-28.
hadoop-thirdparty-1.4.0 was released on 2025-03-27.
3.4.1 was released on 2024-10-18.
3.4.0 was released on 2024-03-17.

## Community Health:

- JUnit5 Migration

The Hadoop project has fully migrated its unit testing framework from
JUnit 4 to JUnit 5[1].
This upgrade resolves previous compatibility warnings that occurred
under mixed JUnit4/5 execution modes, significantly improving the
consistency and stability of the testing framework.
By leveraging JUnit 5’s extended capabilities—such as parameterized
and dynamic tests—the project has also achieved higher test coverage
and improved maintainability.

- Full Support for JDK 17 and JDK 21

The Hadoop trunk branch now fully supports building and compiling with
JDK 17 and JDK 21[2].
This enables Hadoop to take advantage of the performance optimizations
and new language features introduced in modern JDKs, such as enhanced
switch expressions, record classes, and virtual threads.
Following the SpotBugs plugin upgrade, some new static analysis
warnings were reported;
the community is actively working on resolving them to maintain high
code quality and consistency in static checks.

- Integration of Volcano Engine TOS Module

The TOS module from Volcano Engine has been successfully merged into
the Hadoop trunk branch[3].
This module provides native Hadoop support for Volcano Engine Object
Storage and includes comprehensive unit tests to ensure compatibility
and stability under high-concurrency and distributed scenarios.
Its inclusion further strengthens Hadoop’s adaptability to multi-cloud
and hybrid-cloud environments.

- JDK 22+ Compatibility and Adaptation in Progress

The Hadoop community has started compatibility testing and feature
validation for JDK 22 and later versions.
The ongoing work focuses on module system adaptation, reflection
mechanism changes, and potential API deprecations.
As newer JDK versions are released, Hadoop will continue to ensure
stable operation within the evolving Java ecosystem.

JDK 22+ client issues have been resolved[4], and work is underway to
fix remaining UGI compatibility problems[5].

- Native Support for Google Cloud Storage (GCS)

Apache Hadoop now includes native support for Google Cloud Storage
(GCS)[6], featuring a FileSystem implementation accessible via the
gs:// URI scheme.
This integration allows users to access and process GCS data directly
through Hadoop ecosystem tools such as MapReduce, Spark, and
Hive—significantly enhancing Hadoop’s flexibility and interoperability
in multi-cloud data analytics scenarios.

- The Project shows healthy engagement based on Mailing list/JIRA/Github
traffic.

[1] https://issues.apache.org/jira/browse/HADOOP-14693
[2] https://issues.apache.org/jira/browse/HADOOP-19638
[3] https://issues.apache.org/jira/browse/HADOOP-19236
[4] https://issues.apache.org/jira/browse/HADOOP-19212
[5] https://github.com/apache/hadoop/pull/7434
[6] https://issues.apache.org/jira/browse/HADOOP-19343


-----------------------------------------
Attachment AG: Report from the Apache HertzBeat Project  [Chao Gong]

## Description:
The mission of Apache HertzBeat is the creation and maintenance of software 
related to a real-time monitoring system with agentless, performance cluster, 
prometheus-compatible, custom monitoring and status page building capabilities

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

## Membership Data:
Apache HertzBeat was founded 2025-08-20 (2 months ago)
There are currently 29 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- Qiwei Zheng was added to the PMC on 2025-10-04
- SiGuo Duan was added as committer on 2025-11-01

## Project Activity:
- Our community in the OSPP 2025 project has been successfully completed
- Already planning for the release of version 1.8.0.

## Community Health:
- Compared with last month, the contribution level declined by roughly 30%.
  14 authors have pushed 24 commits to master and 105 commits to all branches.
  24 pull requests merged by 10 people.

Overall the project is progressing well. We are actively attracting more
production users and contributors by improving doc, enhancing stability and
strengthening features.


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


-----------------------------------------
Attachment AI: Report from the Apache HTTP Server Project  [Joe Orton]

## Description:
The mission of HTTP Server is the creation and maintenance of software related 
to Apache Web Server (httpd)

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

## Membership Data:
Apache HTTP Server was founded 1995-02-27 (31 years ago)
There are currently 126 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Giovanni Bechis on 2021-06-11.
- No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05.

## Project Activity:
The project released httpd 2.4.64 and 2.4.65 since my last report in February.
As well some features and bug fixes backported from the trunk, the 2.4.64
release in July addressed a set of eight outstanding security issues (all
assessed with Low or Moderate severity). Unfortunately one of the mod_rewrite
changes included in the release opened up another security issue in some
configurations, and 2.4.65 was released a couple of weeks later to address
that issue.

As usual we had a spike of project activity preparing and reviewing backports
around the releases. One of the 2.4.64 security fixes to mod_ssl proved
particularly  controversial for users by restricting access to SSL virtual
hosts (see BZ 69872) in some configurations; this will be addressed with a new
configuration directive in a future update.

A couple of new modules ("mod_random and "mod_replace") were also proposed for
inclusion, which prompted some list discussion.

## Community Health:
Mailing list activity on dev@ and users@ was generally quieter than usual this
quarter. GitHub continues to see a very healthy flow of PRs with some complex
feature submissions coming in from non-committers, generally at a faster 
pace than committers are reviewing and merging (or rejecting) them; leading to 
a slow-growing backlog of unreviewed PRs.


-----------------------------------------
Attachment AJ: Report from the Apache HttpComponents Project  [Michael Osipov]

## Description:
The mission of HttpComponents is the creation and maintenance of software
related to Java toolset of low level HTTP components

## Project Status
- There are no issues requiring board attention at this time.

## Membership Data:
Apache HttpComponents was founded 2007-11-14 (17 years ago)
There are currently 20 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Arturo Bernal on 2023-10-27.
- No new committers. Last addition was Arturo Bernal on 2023-06-20.

## Project Activity:
  - Development on master is 5.6 for Client and 5.4 for Core

## Community Health:
 - Overall the project remains active. Issues and dicussions are
   resolved in time.

## Releases:
- HttpClient 5.6-alpha1: 2025-10-27
- HttpCore 5.4-alpha1: 2025-10-13
- HttpClient 5.5.1 GA: 2025-09-29
- HttpCore 5.3.6 GA: 2025-09-22


-----------------------------------------
Attachment AK: Report from the Apache Ignite Project  [Dmitry Pavlov]


-----------------------------------------
Attachment AL: Report from the Apache Impala Project  [Zoltán Borók-Nagy]

## Description:
The mission of Apache Impala is the creation and maintenance of software 
related to a high-performance distributed SQL engine

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

## Membership Data:
Apache Impala was founded 2017-11-15 (8 years ago)
There are currently 72 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- Jason Fehr was added to the PMC on 2025-09-10
- No new committers. Last addition was Noémi Pap-Takács on 2025-03-12.

## Project Activity:
- In progress integration with Apache Calcite
- Iceberg REST support improvements
- Multi catalog support
- Initial work on Apache Paimon support
- Integration with OpenTelemetry
- Tuple caching enhancements
- Hierarchical event processor
- Optimizations for JDBC tables
- Test infra improvements
- Enable aggregated runtime profiles

## Community Health:
reviews@ is the most reliable metric of Impala community activity level.
There were 2916 emails to that list in September, October,
and November (until 11th)


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

# Incubator PMC report for November 2025

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.  As of 
October, there are 30 podlings under incubation. Five releases
were made during the month, and no IP clearance was completed. No podlings
retired during the month, and one person left the IPMC, as they have 
retired.

Mailing-list traffic in October covered the usual Incubator topics,
including new proposals, release votes, and discussions on graduation 
readiness.

The Incubator wiki and Training Hub have been expanded to include 
additional materials. Some existing resources were converted into other 
formats (e.g., guides into slide decks and videos) to accommodate different 
learning preferences. Several new guides were created in response to minor 
recurring issues observed across podlings, including communication and 
third-party branding.

A consolidated guide, the **Mentor Handbook**, now serves as a single entry 
point that links to all materials, including guides, decks, short videos, 
and case studies, so mentors and podlings can find consistent references in 
one place.

**Guides**  
- **Podling Orientation Guide**: Overview of entering incubation, including 
roles and expectations.  
- **Graduation & Beyond**: Practical outline of what happens after 
graduation.  
- **Vendor Neutrality**: Governance considerations for balanced 
decision-making, avoiding corporate dominance, and sustaining community 
independence.  
- **Mentor’s Tough Conversations Guide**: Approaches for sensitive 
situations such as lack of engagement, governance misunderstandings, or 
interpersonal issues.  
- **Governance in Practice**: Explains how consensus, merit, and "community 
over code" operate throughout incubation.  
- **How to Use the ASF Maturity Model**: Guidance on applying the maturity 
framework for self-assessment.  
- **International / Cultural Awareness**: Tips for cross-cultural 
communication and collaboration.  
- **Interacting with ASF Infrastructure**: Practical information for 
working effectively with Infra processes and expectations.  
- **Communication in Apache Projects**: Mailing list use, decision records, 
and public-by-default norms.  
- **Graduation Criteria**: Explains how the IPMC assesses whether a podling 
is ready to graduate, outlining expectations for community maturity, 
diversity, and governance.  
- **Measuring Podling Health**: Simple indicators for monitoring podling 
progress.  
- **Legal Basics**: Key points about licensing, NOTICE and HEADER 
practices, and where to ask legal questions.  
- **Privacy and Data Handling**: Guidance on managing contributor data, 
such as ICLAs, and maintaining privacy in podlings.

There is also new content based on the existing Incubator case studies. 
These are works in progress and include:  
- **IPMC Reflection and Oversight Guide**: Case-based learning resource for 
recognising patterns in community health and effective oversight.  
- **Extended Incubator Case Studies**: Case studies organised into 
community growth and diversity, corporate independence, complex incubation, 
lifecycle, and global collaboration.  
- **Release Vote Insights**: Analysis of release-vote email traffic over 
ten years. This is being adapted by M&P into a blog post.

Additionally, based on the incubator case studies, several interactive 
scenarios have been developed.

All of this content is linked from the Training section of the Incubator 
site, which now includes a resources index grouping materials by topic and 
a lifecycle-based view that organises them along the incubation journey 
from onboarding to graduation. These resources directly support podling 
readiness and are already being used by several projects preparing for 
graduation.

A new Mentor Topic of the Month thread series has also been launched to 
encourage ongoing mentor engagement and knowledge sharing. The first 
discussion focused on how to grow new contributors. It's also a way to 
share some of the new training material. If this proves helpful, we'll 
continue it.

An experiment inviting podlings to take part in a structured six-month 
community health review is underway. The review helps projects reflect on 
progress, identify blockers, and discuss support needs with their mentors 
and the IPMC. Hamilton, PouchDB, and Texera were invited to participate. 
Hamilton is actively discussing this.  The review offers an optional 
lightweight opportunity for projects to reflect on their progress, identify 
blockers, and discuss support needs with mentors and the IPMC.

There is a concern about HoraeDB; most of the original developers have 
departed, and the podling has been asked to outline a plan for attracting 
and developing new contributors. A minor website issue was noted with 
Gluten and GeaFlow. There was also a discussion regarding KIE hosting 
non-ASF releases and how this aligns with Incubator policy.

The usual discussions on release votes and incubation proposals continue, 
and we have accepted one new project, Caldera, into the Incubator. A vote 
to graduate Apache Wayang is underway.

Most podlings continue to make progress toward graduation, and the IPMC 
will continue to monitor long-running podlings. Both Livy and Toree are now 
actively discussing graduation, and several other projects are likely to 
graduate in the next couple of months. Pegasus was discussing graduation, 
but that has stalled as several core developers have left the project.

All podlings reported this month. Again, a couple of projects were 
contacted regarding issues in their reports and were pointed to the new 
reporting guide. Pegasus did not have mentor sign-off when the report
was submitted.

## Community

### New IPMC members:
  - none

### People who left the IPMC:
  - Jochen Wiedmann

## New Podlings
 - Caldera

## Podlings that failed to report, expected next month
 - None

## Graduations
  - DevLake

  The board has motions for the following:

  - Wayang

## Releases

  The following releases entered distribution during the month of
  September:
  - Gluten 1.5.0
  - Hamilton 1.89.0
  - ResilientDB 1.10.0
  - Polaris 1.2.0
  - Seata-go 2.0.0

## IP Clearance
 - none

## Legal / Trademarks
 - N/A

## Infrastructure
 - N/A

## Table of Contents  
[Burr](#burr)  
[Cloudberry](#cloudberry)  
[Fesod](#fesod)  s
[GeaFlow](#geaflow)  
[GraphAr](#graphar)  
[Hamilton](#hamilton)  
[HoraeDB](#horaedb)  
[Pegasus](#pegasus)  
[Pony Mail](#ponymail)  
[Seata](#seata)  
[Texera](#texera)  
[Toree](#toree)  
[XTable](#xtable)  

--------------------
## Burr

Burr is a lightweight in-process python framework that standardizes the
expression and execution of state machines as action-driven graphs, while
making graph execution easily observable. It is particularly
suited for AI agent workflows, simulations, and other dynamic
systems, and comes with a self-hostable observability UI that
integrates with OpenTelemetry.

Burr has been incubating since 2025-05-24.

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

  1. Release
  2. Build PPMC release muscle
  3. Build community

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

  N/A

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

  New issues from new users and new small time contributions added.

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

  We're gearing up for the first release. Most of the PPMC is on Hamilton
  so we're taking those learnings and applying them here.

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

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

### Date of last release:

  N/A -- almost there!

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

  May 2025

### Have your mentors been helpful and responsive?

  N/A

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

  N/A

### Signed-off-by:

  - [ ] (burr) Kevin Ratnasekera  
     Comments:  
  - [ ] (burr) Ayush Saxena  
     Comments:  
  - [X] (burr) PJ Fanning  
     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. Grow the contributor and community to ensure long-term sustainability.
  2. Publish a few more Apache releases following the ASF release processes.

### 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: 210 new emails on the Dev mailing list since the
  last report, covering community, technical and Apache-related discussions.
  - GitHub Discussions: 14 new threads since last report.
  - New Committers:
    - Sep 25, 2025 - Leonid Borchuk (leborchuk)
  - Events:
    - Apache Cloudberry Meetup organized in Beijing on August 16, 2025,
  which attracted 30~ attendees. This meetup focused on the new features and
  highlights of the 2.0.0 release and the Apache way. See recap post at
  https://s.apache.org/xqyi9.
    - Our committer Leonid Borchuk presented a talk, "PAX — column store
  for Apache Cloudberry/Postgres 14", at PGConf.SPb 2025 in Saint Petersburg
  on September 29, 2025. See details at https://pgconf.ru/talk/2484244.

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

  - Publish the first Apache Cloudberry (Incubating) 2.0.0 release on
  August 25, 2025. See announcement email at https://s.apache.org/fn13p
  - PostgreSQL Kernel upgrade (14~>16): the work has been in progress. See
  the monthly report at https://s.apache.org/kp3lj
  - 113 new commits to the main branch since the last report, focusing on
  CI, performance, bug fixes, and new features.
  - Sub-repositories:
    - Archived the `apache/cloudberry-devops-release` repo and migrated
  these files to the `devops/` directory of the main repository.
    - For the backup tool repos:
      - The `cloudberry-gpbackup` repo has been renamed to
  `cloudberry-backup`, reflecting the project’s independence and alignment
  with the Cloudberry brand. Its codebase has synced with the GP’s archived
  version.
      - The core files from `apache/cloudberry-gpbackup-s3-plugin` have been
  merged into the `cloudberry-backup` repos under `plugins/s3plugin`. Now,
  the S3 plugin will be installed together with Cloudberry Backup.
    - The `cloudberry-pxf` is still in progress on the archived Greenplum
  commits sync to Cloudberry.
    - `cloudberry-go-libs` has synced with the GP’s archived version.
  - Started the discussion on the next release 2.1.0. See discussion at
  https://s.apache.org/rx7s8
  - It has been one year since Cloudberry joined the ASF Incubator. Here is
  our Roadmap recap at https://s.apache.org/5fxn9
  - Ecosystem:
    - The community developers are working with the Apache MADlib team to
  add support for Cloudberry to MADlib upstream. See the PR at
  https://github.com/apache/madlib/pull/627
    - The PostGIS for Cloudberry has been upgraded from 2.5 to 3.3.2

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

  - August 25, 2025

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

  - Sep 25, 2025 - Leonid Borchuk (leborchuk)

### Have your mentors been helpful and responsive?

  Yes. Appreciated their help and support on the release process.

### 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:  Pleased to see cooperations between cloudberry and madlib

### IPMC/Shepherd notes:

  [PJF] The community seems healthy. Maybe it's time to move towards 
  graduation.

--------------------
## Fesod

Fesod is a high-performance and memory-efficient Java library for reading
and             writing Excel files, designed to simplify development and
ensure reliability.

Fesod has been incubating since 2025-09-17.

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

  1. Ensure that the website and codebase are fully compliant with ASF 
  policies. 
  2. Publish the first release under the Apache Incubator. 
  3. Continue to grow the community and word towards the ASF 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. We have update project's website, now you can see details in [Apache 
  Analytics](https://s.apache.org/2w3sw). 
  2. We have 5 new contributors. 

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

  The community is actively working on the first release under the Apache 
  Incubator, which is currently planned for December.
  1. Developement of new features is in progressing. 
  2. The project executed the Fuzz chaos test and fix bugs at the 
  suggestion of the mentor.

### How would you assess the podling's maturity?

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

### Date of last release:

  N/A

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

  N/A

### Have your mentors been helpful and responsive?

  Yes.They are very nice and actively.
  1. Dave Fisher pointed some wrong process about the election of 
  committer(fixed). 
  2. PJ Fanning give suggestions about project-module and jdk-version. 
  3. Huajie Wang help community on how to design logo. 
  4. tison tells many of the small but important copyright details.

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

  Yes, everything is fine.

### Signed-off-by:

  - [X] (fesod) tison  
     Comments:  
  - [X] (fesod) Dave Fisher  
     Comments:  
  - [X] (fesod) Huajie Wang  
     Comments:  
  - [X] (fesod) PJ Fanning  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## GeaFlow

GeaFlow is a streaming graph computing engine for distributed large-scale 
real-time graph storage and analysis. It supports trillion-level graph 
storage, hybrid graph and table processing, real-time/offline graph 
computing, and interactive graph analysis.

GeaFlow has been incubating since 2025-06-06.

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

  1. Enhance the diversity of the community (attracting more committers, 
  contributors, and users).   
  2. Release more versions under the ASF.  

### 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. Four new contributors have joined the community.
  2. Participated in [2025 CSDI Summit in Shenzhen, 
  China](https://www.csdisummit.com/?page=555582&), and presented work in 
  the field of AI. 
  3. Participated in the open source initiative [OSPP 
  2025](https://github.com/summer-ospp) and helped new contributors resolve 
  specific project issues.  

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

  1. Five new features have been merged, including support for the 
  distributed Paimon graph store, a new algorithm implementation for the 
  incremental minimum spanning tree, JDK 11 compatibility and more. Several 
  bug fixes and other improvements have also been made.
  2. The Apache GeaFlow website is published with both Chinese and English 
  support. 
  3. The first community release is in the second round of voting 
  ([v0.7.0-rc2](https://github.com/apache/geaflow/releases/tag/v0.7.0-rc2))

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

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

### Date of last release:
  N/A

### When were the last committers or PPMC members elected?   
  None since entering the incubator.
  We have several active community members and PPMC will review recent 
  contributors and consider the committer nominations.

### Have your mentors been helpful and responsive?
  Yes, we have received helpful guidance.

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

### Signed-off-by:

  - [ ] (geaflow) Willem Ning Jiang  
     Comments:  
  - [X] (geaflow) Xin Wang  
     Comments:  
  - [X] (geaflow) Jingsong Lee  
     Comments:  
  - [ ] (geaflow) Paul Klingelhuber  
     Comments:  
  - [X] (geaflow) Justin Mclean  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## GraphAr

GraphAr is an open-source and language-independent data file format designed
for efficient graph data storage and retrieval.

GraphAr has been incubating since 2024-03-25.

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

  1. Growing the community(attracting more committers, contributors and 
  users)
  2. Release more ASF-compliant versions

### 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. Released a new version V0.13.0 
  2. 5 new contributors completed PR merge 

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

  1. Merged 27 PRs since the last report 
  2. The java-info module changed user-facing API 
  3. Improve the ci test and coverage report

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

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

### Date of last release:

  2025-08-29

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

  2025-07-14

### Have your mentors been helpful and responsive?

  The mentors are very helpful and responsive.

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

  There are no known brand and naming issues.

### Signed-off-by:

  - [ ] (graphar) Calvin Kirs  
     Comments:  
  - [X] (graphar) tison  
     Comments:  
  - [ ] (graphar) Xiaoqiao He  
     Comments:  
  - [ ] (graphar) Yu Li  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Hamilton

Hamilton is a lightweight in-process framework to define, execute, and
observe             directed acyclic graphs (DAGs) that express data
transformations. In Hamilton, one can             express complex DAGs of
transformations, e.g. from dataframe transformations (using
pandas, polars, PySpark), machine learning pipelines, through to regular
software             engineering API request and LLM API based workflows.
Observability hooks are built into             the framework. The Hamilton
UI is a self-hostable service to capture observability             output
from workflow runs.

Hamilton has been incubating since 2025-04-12.

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

  1. Release other packages under apache process.
  2. Train more of PPMC to run a release.
  3. Have more releases.

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

  N/A

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

  Several new contributors to the repo.

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

  We published our first main package under apache!

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

  2025-10-11

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

### Have your mentors been helpful and responsive? Are things falling 
  through the cracks? If so, please list any
  open issues that need to be addressed.

  We're not a java project, so things aren't as straightforward to release 
  -- which most of the documentation is geared towards.

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

  Yes -- no 3rd parties with issues.

### Signed-off-by:

  - [ ] (hamilton) Kevin Ratnasekera  
     Comments:  
  - [ ] (hamilton) Ayush Saxena  
     Comments:  
  - [X] (hamilton) PJ Fanning  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## HoraeDB

HoraeDB is a high-performance, distributed, cloud native time-series
database.

HoraeDB has been incubating since 2023-12-11.

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

  1. Release more version
  2. Grow community(attract more users/committers)
  3. Finish the new metrics engine

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

  Several core developers have left the project, causing a slowdown in 
  development this year. We expect development to get back on track next 
year.

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

  Attend the OSPP 2025 with one project.

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

  An in-house prometheus remote write format parser has been merged.

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

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

### Date of last release:  

  2024-12-10

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

  Neo Chen, at 2024-12-25

### Have your mentors been helpful and responsive?

  Yes, they are helpful when release version and other trivial things.

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

  Yes, we're doing well with this.

### Signed-off-by:

  - [X] (horaedb) tison  
     Comments:  
  - [ ] (horaedb) Shaofeng Shi  
     Comments:  
  - [X] (horaedb) Gang Li  
     Comments:  
  - [X] (horaedb) Von Gosling  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Pegasus

Pegasus is a distributed key-value storage system which is designed to be
simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

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

  1. The graduation discussion has been initiated, but not enough PPMC 
  members have participated yet; therefore, the discussion is currently 
  blocked.
  2.
  3.

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

  Many core members of the project have left, leading to a decline in 
  community activity and consequently blocking the graduation discussion.

  However, there are still some PPMC members and contributors maintaining 
  the project.

  The reason there has been no release for nearly two years since December 
  2023 is that several major features were planned for Pegasus 2.6.0, such 
  as FQDN support and a refactored metrics framework. However, due to the 
  inactivity of many core members, progress on these major features has 
  been difficult. At present, the remaining active members are doing their
  best to move things forward.

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

  Some new contributors have joined the project development.

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

  Introduce some new features, enhancements and fixes, including:
  - support encrypted password file during SASL authentication for 
  ZooKeeper C client
  - the underlying network communication and the write path have been 
  optimized
  - some bugs of replica server, scripts, java and go client have been fixed
  - some dependencies of java client have been upgraded to the secure 
  versions

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

  2023-12-12

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

  2024-09-26

### Have your mentors been helpful and responsive?
  Yes.

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

### Signed-off-by:

  - [ ] (pegasus) Duo zhang  
     Comments:  
  - [ ] (pegasus) Liang Chen  
     Comments:  
  - [ ] (pegasus) Von Gosling  
     Comments:  
  - [ ] (pegasus) Liu Xun  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## PonyMail

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

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

  1. Make a release of Pony Mail Foal
  2. Decide on the future direction of the project. PMC or retirement.
  3.

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

  Nothing at this time.

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

  The community is slowly discussing their exit strategy.

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

  Responding to some concerns

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

  2019-04-05 Pony Mail 0.11

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

  2021-04-02 Sean B Palmer

### Have your mentors been helpful and responsive?

  See above.

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

  If not what actions has the PPMC taken to correct this?

  Has the VP, Brand approved the project name? Yes

### Signed-off-by:

  - [ ] (ponymail) John D. Ament  
     Comments:  
  - [X] (ponymail) Dave Fisher  
     Comments: Doing my best slowly move the podling one way or another.  

### IPMC/Shepherd notes:

--------------------
## Seata

Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to-
use and high-performance distributed transaction solution, used
to solve the data consistency problem.

Seata has been incubating since 2023-10-29.

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

  1. Complete the transfer of Seata's existing trademarks to the ASF. 
  Currently awaiting feedback from ASF trademark counsel.

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

  No issues at the moment.

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

  1. 26 new code contributors have joined the community (622 contributors 
  in total)
  2. 3 new committers were elected, and 1 PPMC members were elected.
  3. In the open-source programming events, OSPP and GSoC, through the 
  joint efforts of multiple mentors and students, we completed the 
  finalization of 5 projects, including 3 AI-related ones.

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

  1. Since the last report, we've merged 145 PRs, which include over 10 new 
  features.
  2. Since the last report, we have released one official versions: 
  seata-go 2.0.0.
  3. Since the last report, we have fixed more than 25 dependency 
  vulnerabilities.  

### 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-10-06

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

  2025-10-16

### Have your mentors been helpful and responsive?

  Our mentors have been very helpful and responsive.

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

  No Trademark issues.

### Signed-off-by:

  - [X] (seata) Sheng Wu  
     Comments: Project community keeps active. The PMC is finishing the 
     preparation for the graduation.
  - [ ] (seata) Justin Mclean  
     Comments:  
  - [X] (seata) Huxing Zhang  
     Comments: The project is in good shape towards graduation.  
  - [ ] (seata) Heng Du  
     Comments:  
  - [X] (seata) Xin Wang  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Texera

Texera is an open-source system to support collaborative data science, AI,
and             ML using GUI-based workflows. Our vision is to develop a
system to support cloud             platforms on which users can easily
analyze data and use AI/ML techniques provided as             operators.
Users with various backgrounds, irrespective of whether they know coding or
not, can collaborate on the same project to construct a pipeline.
Experienced users can             use programming languages such as Python,
R, Java, and Scala to implement customized             computation logic.
The platform allows users to pause the execution of a workflow to
investigate the operator states, and resume the execution at a later time.
The platform             can be used by a research community to publish
valuable resources such as data sets,             workflows, and ML models
to share their domain-specific knowledge and support
reproducibility of scientific research. The platform also allows users to
elastically             request computing resources from public clouds for
computationally-intensive tasks.

Texera has been incubating since 2025-04-12.

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

  1. The Apache website (texera.apache.org) is still ongoing
  2. We still have one library (rpy2) that is not Apache friendly

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

### How has the community developed since the last report?
  We had three new external contributors and also an external contributor 
  who helped us to identify the security issue.

### How has the project developed since the last report?
  The followings are some of the important updates on project development:
  - Reorganize the code base: previously, the naming convention was 
  `edu.uci.ics` and its now changed to `org.apache.texera` to be compliance 
  with Apache
  - Add ML training operators for linear and logistic regression
  - Add a new micro-service named access control service which secures 
  socket connection between computing unit and user

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

  NA

### When were the last committers or PPMC members elected?
  July 4 2025

### Have your mentors been helpful and responsive?
  Yes, PJ and Ian helped us in many ways including:
  - PJ raised many PRs including replace Akka actor since its license is 
  not Apache friendly
  - Ian gave us insight on how to improve our security

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

### Signed-off-by:

  - [ ] (texera) Cezar Andrei  
     Comments:  
  - [ ] (texera) Gordon King  
     Comments:  
  - [X] (texera) PJ Fanning  
     Comments:  Getting web site up and running would be useful. 
  - [X] (texera) Ian Maxon  
     Comments:  Looking forward to the first incubating release, great to 
     see the package name change.

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

  None

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

  None, Nothing much of news from previous report

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

  Release 0.6 has been voted by PPMC and is being reviewed in incubator 
  general mailing list. The new release brings Scala 2.13 and Spark 3.4.4
  support.

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

  Release 0.6.0 preparation and votes

### 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 graduation after release is out
     process
  - [X] (toree) Ryan Blue  
     Comments:  Good to see a discussion about graduation in the community.
     You may want to update the "unfinished issues" section and remove #1.
  - [ ] (toree) Weiwei Yang  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## XTable

XTable is an omni-directional converter for table formats that facilitates
interoperability across data processing systems and query engines.

XTable has been incubating since 2024-02-11.

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

  1. Strengthening community building by actively engaging with users.   
  2. Increasing adoption by implementing key features planned - Deletion 
  Vectors, Syncing to New Catalogs, Supporting new Table Formats  
  3. Fixing packaging issues for bundled jars for new features.

### 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. An XTable contributor presented an integration talk with one of Apache 
  Polaris PMC during Community Over Code 2025
  2. Two new first time contributors have merged their first PR's.
  3. More users are trying to use XTable in production environments and the 
  community has been helping them succeed.
  4. We have added two new members to the PPMC.

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

  1. The implementation for the XTable REST Service was introduced in the 
  release 0.3.0.
  2. The implementation for adding a conversion source for Apache Parquet 
  files was recently landed.
  3. Community is working on adding support for Delta Lakes Kernel APIs for 
  handling conversion.
  4. Community is currently working on supporting an Apache Paimon 
  Conversion Source.

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

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

  2025-11-04

### Have your mentors been helpful and responsive?

  Our mentors have been helpful and responsive.

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

### Signed-off-by:

  - [ ] (xtable) Jesús Camacho Rodríguez  
     Comments:  
  - [X] (xtable) Stamatis Zampetakis  
     Comments: It's nice to see that the community is growing. Looking 
     forward seeing more involved in the oversight of the project. 
  - [X] (xtable) Jean-Baptiste Onofré  
     Comments:  Good progress in the podling. The community is active and I 
     agree that building the community is the main action item right now.

### IPMC/Shepherd notes:


-----------------------------------------
Attachment AN: Report from the Apache Juneau Project  [James Bognar]

## Description:
The mission of Apache Juneau is the creation and maintenance of software 
related to a toolkit for marshalling POJOs to a wide variety of content types 
using a common framework, and for creating sophisticated self-documenting REST 
interfaces and microservices using VERY little code

## Project Status:
Current project status: Active development ongoing for the next release, 9.2.0
Issues for the board: None

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

Community changes, past quarter:
- Two retirements in the past quarter:  Jochen Wiedmann, Craig Russell

## Project Activity:
Last release was 9.1.0 made on June 19, 2025.

Currently working heavily on modernizing the codebase to use newer Java
language features.  Will be release as 9.2.0 in the next 1-2 months.

Website and documentation has been completely overhauled using Docusaurus:
https://juneau.apache.org/about

Many improvements made to documentation in general.

## Community Health:
Community is small, but commits occurring from multiple contributors.
11 Jira tickets closed this quarter.


-----------------------------------------
Attachment AO: Report from the Apache Kafka Project  [Mickael Maison]

## Description:
The mission of Kafka is the creation and maintenance of software
related to Distributed publish-subscribe messaging system

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

## Membership Data:
Apache Kafka was founded 2012-11-21 (13 years ago)
There are currently 69 committers and 39 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 Lucas Brutschy on 2025-07-14.
- No new committers. Last addition was PoAn Yang on 2025-07-12.

## Project Activity:
In the past quarter we released Kafka 4.0.1 and 4.1.0.

Kafka 4.1.0 includes:
- Queues for Kafka now in preview
- New Streams rebalance protocol
- Mechanism for plugins to register metrics
- Support for running multiple versions on Connectors
- Support for OAuth jwt-bearer grant type

We have 2 releases in progress:
- 4.1.1: Planned for November, the vote on RC2 is currently ongoing
- 4.2.0: Planned for January

## Community Health:
The project activity on mailing lists, Jira and GitHub is stable 
and stays relatively high.


-----------------------------------------
Attachment AP: Report from the Apache Knox Project  [Larry McCay]

## Description:
The mission of Knox is the creation and maintenance of software related to 
Simplify and normalize the deployment and implementation of secure Hadoop 
clusters

## Project Status:
Current project status: Ongoing: With high, moderate or low activity, which
you may quantify if appropriate Issues for the board: none

## Membership Data:
Apache Knox was founded 2014-02-18 (12 years ago)
There are currently 26 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.

Community changes, past quarter:
- Tamás Marcinkovics was added to the PMC on 2025-11-10
- Tamás Hanicz was added to the PMC on 2025-11-10
- Tamás Marcinkovics was added as committer on 2025-10-17
- Tamás Hanicz was added as committer on 2025-10-15

## Project Activity:
2.1.0 was released on 2025-09-26
New committers added 2025-10-17 and 2025-10-15

## Community Health:
dev@knox.apache.org had a 12% decrease in traffic in the past quarter (516
emails compared to 582) user@knox.apache.org had a 100% decrease in traffic in
the past quarter (0 emails compared to 8) 31 JIRA tickets opened and 34 closed
in the past quarter.

These decreases are only minimumal smaller in numbers rather than percentage.
They are inline with our status as a mature ongoing project and the time of
year.

We are planning an upcoming 3.0.0 release wherein Java 8 is finally dropped.


-----------------------------------------
Attachment AQ: Report from the Apache Kylin Project  [Yang Li]

## Description:
The mission of Apache Kylin is the creation and maintenance of software related 
to a distributed and scalable OLAP engine

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

## Membership Data:
Apache Kylin was founded 2015-11-18 (10 years ago)
There are currently 52 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08.
- No new committers. Last addition was Pengfei Zhan on 2024-11-12.

## Project Activity:
Released Apache Kylin 5.0.3 on 2025-09-28, covering a few bug fixes and 
some small enhancements that were previously planned for 5.1.

The next release 5.1 is slightly shifted towards the integration with AI
tools, by supporting MCP etc.

## Community Health:
Reminded a few key developers to update their progress on a daily basis.
The activity metrics went back to normal. Good habits still require 
constant reminders, even after they've been established.

- dev@kylin.apache.org had a 2100% increase 
  in traffic in the past quarter (22 emails compared to 1)
- issues@kylin.apache.org had a 11500% increase 
  in traffic in the past quarter (116 emails compared to 1)
- 10 JIRA tickets opened and 9 closed in the past quarter.


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


-----------------------------------------
Attachment AS: Report from the Apache Logging Services Project  [Piotr Karwasz]

## Description:

The mission of the Apache Logging Services project is to create and
maintain of software for managing the logging of application behavior,
and for related software components.

## Project Status:

Current project status: Ongoing
Issues for the board:

The project has faced some pushback regarding the required code review
process, which effectively places committers and external contributors
on the same footing when submitting code changes.

At the same time, user expectations and emerging industry standards such
as SLSA increasingly call for two-party reviews (not necessarily from
two trusted parties).

Some guidance from the Board on how to best balance these expectations
with the *merit* and *trust* earned by committers would be appreciated.

Reference mailing list threads:

* https://lists.apache.org/thread/l23k5n6spfgs05ds06t4hpgmmssqpzvd
* https://lists.apache.org/thread/sznkno4qxzyfmtthl9xh3hyj9nk0k4dr

## Membership Data:

- Founded: 2003-12-17 (22 years ago)
- Committers: 47 (19 active)
- PMC Members: 23 (15 active)
- Committer-to-PMC ratio: 2:1 overall; 1:1 among active members

Community changes, past quarter:
- No new PMC members. Last addition was Fred am Nil on 2024-08-07.
- No new committers. Last addition was Jeff Thomas on 2025-02-27.

## Project Activity:


During the August–October 2025 quarter, the three active components
(Log4cxx, Log4net and Log4j) showed moderate activity overall.

### Log4cxx (activity: moderate)

- Continued work on a larger performance improvement initiative.
- Disclosed two vulnerabilities: CVE-2025-54812 and CVE-2025-54813.
- Release: log4cxx-1.5.0 (2025-08-03)

### Log4j (activity: moderate)

- Focused on improving Spring Boot integration and ensuring Log4j 2.25.x
  inclusion in the upcoming Spring Boot 4.x release.
- Engaged in extensive community discussion around the code review 
  policy introduced in May.
- Release: log4j-2.25.2 (2025-09-22)

### Log4net (activity: moderate)

- Ongoing maintenance with a focus on bug fixes and stability improvements.
- Next release: log4net-3.2.1 planned for December 2025, primarily addressing
minor bug fixes.
- Release: log4net-3.2.0 (2025-08-22)

## Community Health:

The project community remains active and engaged, with a few new regular
contributors who may be invited as committers in the future. Activity
from several long-term contributors has gradually declined over the
years, although one long-standing PMC member has indicated that the
stricter review requirements introduced in May contributed to his
reduced involvement.

The user and downstream project communities continue to provide valuable
feedback, reinforcing that the logging ecosystem remains active and
evolving.


-----------------------------------------
Attachment AT: Report from the Apache Mahout Project  [Shannon Quinn]

## Description:
The mission of Mahout is the creation and maintenance of software related to 
Scalable machine learning library

## Project Status:
Current project status: We are slowly but surely coming out of 'dormant' /
hibernation. Code activity has been picking up, driven by our two new
committers. We continue to pivot from scalable machine learning to quantum
computing, which is driving a non-trivial bit of interest. We all still have
day jobs, which hinders progress, but the new contributors are students who
make commits when on holiday or to procrastinate from assignments which helps
a lot, and in tern demands attention from PMC with day jobs who think "well, i
don't really have time to implement the yak shaver, but i suppose i should at
least review the PR from this kid who did" and as such we're coming back to
life. Issues for the board: Thanks for dropping the feather, we _just_ got
that incorporated into our logo after idk how many years. Lol.

Issues for the board: PMC is focusing on (and driving committers to help on)
releasing on PyPi using the new ASF tool that is being developed. That and
none of us are here full time is me forward selling- things may appear to slow
down in the codebase over the next 3 mo, but in actually we're just doing
stuff to help ASF and spending time w/ loved ones.

## Membership Data:
Apache Mahout was founded 2010-04-20 (16 years ago)
There are currently 31 committers and 10 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 Shannon Quinn on 2023-02-12.
- Guan-Ming Chiu was added as committer on 2025-11-04

## Project Activity:
Working on getting a release to PyPi, also will be slower than it would be
otherwise as we're helping pathfind with the new Apache Release Tool

## Community Health:
The potentially useful metrics are laughably not for small projects such as
ours.

dev@mahout.apache.org had a 6912% increase in traffic in the past quarter
(4067 emails compared to 58) issues@mahout.apache.org had a 566% increase in
 traffic in the past quarter (20 emails compared to 3) user@mahout.apache.org
 had a 100% decrease in traffic in the past quarter (0 emails compared to 6)

Suffice to say I think we're healthy- the 6 emails on user @ last quarter were
probably spam or ApacheCon (whatever it's called now) announcement emails, or
something like that. That list isn't really used much.

But as (iirc) tison said, we're adding new committers, which is (also in my
opinion) the strongest metric for good health.


-----------------------------------------
Attachment AU: Report from the Apache ManifoldCF Project  [Piergiorgio Lucidi]

## Description:
The mission of ManifoldCF is the creation and maintenance of software related
to Framework for connecting source content repositories to target repositories
or indexes.

## Issues:
None

## Membership Data:
Apache ManifoldCF was founded 2012-05-15 There are currently 25
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.

Community changes, since last report in August:
- No new PMC member.  Last addition was made on 2023-08-03.
- No new committers. Last addition was on 2019-08-17.

## Project Activity:
We have released ManifoldCF 2.29 in September and we started a new branch for upgrading to OpenJDK 21.

We started to remove legacy connectors and we currently have some test suites to migrate to JUnit 5.
I have to encourage greater involvement from all the contributors, again.

I don't see contributions coming from the community and I'm struggling to find time for this due to personal 
issues that I should solve in a couple of months. Even if I'm still active in the project, 
it's impossible for me to give the right attention to it because it's too much work to do.

I'm wondering if we should start considering ManifoldCF for the Attic.

Recent releases:
2.29 was released on 2025-09-12
SDK 1.02 released on 2025-02-10
2.28 was released on 2025-01-15
2.27 was released on 2024-09-26
2.26 was released on 2023-11-01
2.25 was released on 2023-06-01

## Community Health:
No new pull requests at the moment, we started to work on the new branch for OpenJDK 21 


-----------------------------------------
Attachment AV: Report from the Apache Maven Project  [Hervé Boutemy]

## Description:
The mission of Maven is the creation and maintenance of software related to 
Java project management and comprehension tools

## Project Status:
Current project status: ongoing with high activity.
Issues for the board: none.

## Membership Data:
Apache Maven was founded 2003-03-01 (23 years ago)
There are currently 73 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- No new PMC members. Last addition was Romain Manni-Bucau on 2023-10-16.
- Christoph Läubrich was added as committer on 2025-11-07

## Project Activity:

Recent releases:
- Apache Maven Build cache extension 1.2.1: 2025-10-31
- Apache Maven Plugin Testing 3.4.0: 2025-10-28
- Apache Maven WAR Plugin 3.5.0: 2025-10-22
- Apache Maven Plugin Tools 3.15.2: 2025-10-20
- Apache Maven Plugin Tools 4.0.0-beta-2: 2025-10-20
- Apache Maven AntRun 3.2.0: 2025-10-17
- Apache Maven Compiler Plugin 4.0.0-beta-3: 2025-10-15
- Maven Resolver 2.0.13: 2025-10-10
- Apache Maven Archiver 3.6.5 and 4.0.0-beta-5: 2025-10-08
- Apache Maven PMD Plugin 3.28.0: 2025-10-07
- Maven Archetype 3.4.1: 2025-10-03
- Apache Maven Artifact Plugin 3.6.1: 2025-10-02
- Apache Maven Dependency Plugin 3.9.0: 2025-09-29
- Apache Maven Enforce 3.6.2: 2025-09-28
- Maven SCM 2.2.1: 2025-09-25
- Apache Maven Compiler Plugin 3.14.1: 2025-09-22
- Maven Javadoc Plugin 3.12.0: 2025-09-21
- Apache Maven mvnd 1.0.3: 2025-09-20
- Apache Maven Shade plugin 3.6.1: 2025-09-14
- Apache Maven Surefire 3.5.4: 2025-09-14
- Maven Resolver 2.0.11: 2025-09-11
- Maven Wrapper 3.3.4: 2025-09-11
- Apache Maven Wrapper 3.3.3: 2025-08-26
- Apache Maven Javadoc 3.11.3: 2025-08-17
- Apache Maven Resolver Ant Tasks 1.6.0: 2025-08-14
- Apache Maven Archiver 3.6.4 and 4.0.0-beta-4: 2025-08-11
- Apache Maven 3.9.11: 2025-07-12
- Apache Maven Enforce 3.6.1: 2025-07-12

Jira to GitHub Issues migration is now fully done: now Jira is read-only.

We are working with Apache Trusted Release project to test the project and
make sure we know how to update our release process to benefit from ATR when
it will be GA.
Progress tracked on our Wiki:
https://cwiki.apache.org/confluence/display/MAVEN/ATR+integration

Maven 4 is on its way:
- RC 5 vote is in progress, which is expected to be the last RC,
- 4.0.0 should follow quite soon.

## Community Health:
Users mailing list remains quite low.
For developers, mailing list is used for votes and a few discussion: a lot of
discussion happens on Slack, that is the location where people are very active
and a lot happens.


-----------------------------------------
Attachment AW: Report from the Apache OpenJPA Project  [Mark Struberg]

## Description:
 The mission of OpenJPA is the creation and maintenance of software related to
 Apache OpenJPA: Object Relational Mapping for Java

## Issues:
 There are no issues requiring board attention.

## Project Activity:
 We are currenly implementing Jakarta JPA-3.2 updates.
 Most of the work happens in the OPENJPA-2940 branch, so not much to see
 yet on the master in the repo. But work is progressing.

## Membership Data:
 Apache OpenJPA was founded 2007-05-16 (18 years ago)
 There are currently 36 committers and 18 PMC members in this project.
 The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
 - No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13.
 - Paulo Cristovão de Araújo Silva Filho was added as committer on 2025-05-30


-----------------------------------------
Attachment AX: Report from the Apache OpenWhisk Project  [Dave Grove]

## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software 
related to a platform for building serverless applications with functions

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

## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (6 years ago)
There are currently 54 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Cosmin Stanciu on 2022-02-22.
- No new committers. Last addition was Luke Roy on 2023-03-06.

## Project Activity:
The main activity in this quarter was a set of code changes 
from a long-standing project committer that migrated the core OpenWhisk
system from Akka to Apache Pekko.

The most recent releases were part of a wave of openwhisk-runtime releases
made in August/September 2024:

openwhisk-runtime-java-1.20.0 was released on 2024-09-23.
openwhisk-runtime-php-1.21.0 was released on 2024-09-23.
openwhisk-runtime-python-1.20.0 was released on 2024-09-23
openwhisk-runtime-swift-1.19.0: was released on 2024-09-23
openwhisk-runtime-dotnet-1.18.0: was released on 2024-09-13
openwhisk-runtime-docker-1.16.0: was released on 2024-09-07
openwhisk-runtime-nodejs-1.23.0: was released on 2024-09-07
openwhisk-runtime-go-1.25.0: was released on 2024-09-05

## Community Health:
Although accomplishing the migration of the core system from Akka to
Apache Perkko was definitely a positive development, I see no fundamental
change to the overall health of the project since the May report,
which is repeated below.

There are sufficient PMC members paying attention to handle security issues,
vote on releases, and answer the relatively low volume of user questions that
we get (mainly via GitHub issues).

With the exception of a small number of academic research projects, users of
OpenWhisk have moved on to other serverless platforms. Given the significant
size of the code base, the lack of ongoing development effort, and the
declining usage of OpenWhisk, the project appears to be winding down and may
need to seriously discuss a transition to the Attic in 2026.


-----------------------------------------
Attachment AY: Report from the Apache Ozone Project  [Sammi Chen]

## Description
Apache Ozone is a scalable, redundant, and distributed object and file
store,
designed to scale to billions of objects/files and run on clusters of
thousands
of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop
Compatible File System implementation.

## Issues
None.

## Membership Data
- Apache Ozone was founded 2020-10-21.
- There are currently 85 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
- In the past quarter,
Aryan Gupta was added to the PMC on 2025-10-06
Abhishek Pal was added as committer on 2025-11-07

## Project Activity
- Snapshot Feature
- Bucket quota to support Snapshot(HDDS-13730) is completed. Now Ozone
bucket quota will work correctly when there are snapshots created in the
bucket.
- OM follower bootstrap failures with snapshots issue is
fixed(HDDS-12090). A lock is introduced to prevent the race condition
during snapshotted OM bootstrap.
- Snapshot Defragmentation to reduce storage footprint(HDDS-13003)
continuous. This task aims to reduce the space occupied by snapshots so the
snapshot number can better scale.
- Support listener OM(HDDS-11523) is finished. Documentation about how to
enable listener OM is also ready.
- Container reconciliation(HDDS-10239), after being merged back to master
branch, a few enhancements and bug fixes are raised and under
implementation.
- Storage Capacity Distribution(HDDS-13177), an effort to show the storage
wise and namespace wise data distribution on Recon, continuous.
- Disk Balancer feature(HDDS-5713) receives feedback during vote
discussion, improvements are under implementation.
- S3 Object LifeCycle Management feature(HDDS-8342) development is ongoing.
- Recon improvements, such as accelerating namespace usage calculation,
improving bulk deletes and cleanup performance of OM tasks, cluster new
capacity UI, etc.
- Disk space utilization management improvement phase two(HDDS-12564) has
completed, phase three(HDDS-13748) is ongoing. The major goal is to prevent
disk space from being fully occupied.
- Continuous Ozone document improvements, with the popular AI tools' help,
new/existing documents are added and improved.
- Ozone debug and repair tools improvement(HDDS-8097) continuous. The goal
is to document, fix bugs in existing tools, and add new ones if needed.
- S3G Support uploading objects with a presigned URL(HDDS-5195) is
implemented.
- Hadoop dependency is updated to 3.4.2(HDDS-13626).
- Tracing framework used is migrated from openTracing to
openTelemetry(HDDS-13680).
- Clean up dependencies(HDDS-11276), fixes the problems reported by "mvn
dependency:analyze", continuous.
- New features are kicked off
- Security Token Service(HDDS-13323), builds a Amazon AWS Security Token
Service (STS) API compatible service in Ozone, to support hybrid cloud
usage for Ozone.
- Ozone Event Notification Support(HDDS-13513), provides an event
notification mechanism for Ozone, to notify event receiver specific Ozone
write type operations.
- 2.1.0 release is in progress. RC1 is rolled out.

## Releases Data
- 1.0.0 was released on 2020-09-02.
- 1.1.0 was released on 2021-04-20.
- 1.2.0 was released on 2021-11-17.
- 1.2.1 was released on 2021-12-22.
- 1.3.0 was released on 2022-12-18.
- 1.4.0 was released on 2024-01-19.
- 1.4.1 was released on 2024-11-24.
- 2.0.0 was released on 2025-04-30.

## Community Health
Last board report was sent on 5th September 2025, and was postponed by one
month. Since 5th August,
- 36 code contributors who have commits in the past quarter
- dev@ozone.apache.org had 47 emails in the past quarter
- 308 PRs opened on GitHub, past quarter
- 287 PRs closed on GitHub, past quarter
- 259 commits in the past quarter
Note: The commit & PR count excludes the ones from user "app/dependabot",
who has many commits for dependency jar version upgrade.


-----------------------------------------
Attachment AZ: Report from the Apache Parquet Project  [Julien Le Dem]

Parquet Report November 2025

## Description:
A column-oriented data file format designed for efficient data storage and
retrieval. It provides high performance compression and encoding schemes to
handle complex data in bulk and is supported in many programming languages and
analytics tools.

Parquet consists of a format specification (the Parquet format) and several
implementations, one of which (Parquet Java) is developed directly under the
umbrella of the Apache Parquet project. Non-Apache implementations also exist,
some of them closed source.

## Project Status:
Current project status: Ongoing
Recent addition of Variant and geo types. 
Ongoing work for addition of new SIMD/GPU friendly encodings like ALP and FSST
Issues for the board: none

## Membership Data:
Apache Parquet was founded 2015-04-21 (11 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 Fokko Driesprong on 2025-01-23.
- Andrew Lamb was added as committer on 2025-09-30

## Project Activity:
Recent releases:
Java 1.16.0 was released on 2025-09-03.
Format 2.12.0 was released on 2025-08-28.
1.15.2 was released on 2025-05-01.

In particular we recently added support for:
- the new Variant type 
- geo related types.

Ongoing projects for addition of:
- ALP encoding for floating points
- FSST encoding for strings
- flatbuffer based footer

## Community Health:
The community is collaborating well on adding new functionality to the project
and integrating them in the broader ecosystem of vendors.
Healthy discussions on the mailing list and collaboration in regular online
syncs.
Website updates are happening, focusing on community and broader ecosystem


-----------------------------------------
Attachment BA: Report from the Apache Perl Project  [Steve Hay]

## Description:
The mission of Perl is the creation and maintenance of software related to 
Dynamic websites using Perl

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

## Membership Data:
Apache Perl was founded 2000-03-10 (26 years ago)
There are currently 21 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Steve Hay on 2012-03-01.
- No new committers were added.

## Project Activity:
The last release was mod_perl-2.0.13 on 2023-10-21.

There hasn't been any development in the last quarter, which isn't unusual.
The project has long since reached a stage where changes are mostly of a
maintenance variety, and none has been required recently.

## Community Health:
In line with the project activity observations, mailing lists have also been
quiet.


-----------------------------------------
Attachment BB: Report from the Apache Phoenix Project  [Istvan Toth]

## Description:
The mission of Phoenix is the creation and maintenance of software related to 
High performance relational database layer over Apache HBase for low latency 
applications

## Project Status:
Current project status: Ongoing
Issues for the board: No issues to report to the board at this time.

## Membership Data:
Apache Phoenix was founded 2014-05-21 (11 years ago)
There are currently 61 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

Community changes, past quarter:
- No new PMC members. Last addition was Jacob Isaac on 2023-11-07.
- Nihal Jain was added as committer on 2025-08-05

## Project Activity:
Development activity was lower in this quarter as most activity was
concentrated on finalizing features for the 5.3.0 release and bug fixes.

The project has released Phoenix 5.3.0 which added JSON and BSON data types
and CDC (Change Data Capture) capabilities, as well as improvements to the
High Availability and Time To Live features.

We are in the process of adding a new sub-project that provides an API
compatible drop-in replacement for AWS DynamoDB using Phoenix.

Notable changes and new features in the quarter (most included in 5.3.0):

Dependency version updates: 
PHOENIX-7708 Update Jackson to 2.18.4.1
PHOENIX-7697 Update Gson to 2.13.1 
PHOENIX-7698 Update Netty to 4.1.126
PHOENIX-7699 Update Jetty to 9.4.58.v20250814 
PHOENIX-7696 Update Hadoop 3.4 version to 3.4.2 
PHOENIX-7687 Wrong Hadoop version used for Hbase 2.5.0 profile

CDC Feature related: 
PHOENIX-7718 : CDC Stream improvements

BSON feature related: 
PHOENIX-7692: Path validations for bson update expression 
PHOENIX-7691 : Handle empty bson doc in bson update expression function

HA feature related: 
PHOENIX-7695 : ParallelPhoenixResultSet keeps the unused
result set open for too long 
PHOENIX-7426 Generating index mutations for immutable tables on the server side

Other notable changes and fixes:

PHOENIX-7370 Server to server system table RPC calls should use separate RPC
handler pool
PHOENIX-7711 Make Phoenix test jar available for consumption by
applications 
PHOENIX-7709 Index committer post writer lazy mode - Async RPC
call for verified index mutations 
PHOENIX-7707 Phoenix server paging on valid rows 
PHOENIX-7705 Support for a row size function 
PHOENIX-7582 Accept phoenix.skip.system.tables.existence.check from 
hbase-site.xml 
PHOENIX-7701 UngroupedAggregateRegionScanner doesn't release rpc handler on page
timeouts
PHOENIX-7702 Backward compatibility test framework support for phoenix 5.2 and
hbase 2.6 
PHOENIX-7700 Update default values for schema change retry policy
PHOENIX-7638 Creating a large number of views leads to OS thread exhaustion
PHOENIX-7690 Add a config to enable using bloom filters for multi-key point
lookups 
PHOENIX-7651 Support RETURNING * with UPSERT and DELETE 
PHOENIX-7670 Region level threadpool for uncovered index to scan data table
PHOENIX-7684 Introduce Segment Scan PHOENIX-7682 Review and simplify 
compatibility modules
PHOENIX-7628 Don't add Apache Snapshot Maven Repo by Default

## Community Health:
Overall community health is good. We have added a new committer in the quarter.


-----------------------------------------
Attachment BC: Report from the Apache Pinot Project  [Kishore G]

## Description:
The mission of Apache Pinot is the creation and maintenance of software related
to distributed OLAP data store to provide Real-time Analytics to power wide
variety of analytical use case

## Project Status:
Current project status: Ongoing (high activity)
Issues for the board: There are no Board-level issues at this time

## Membership Data:
Apache Pinot was founded 2021-07-21 (4 years ago)
There are currently 44 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
Recent PMCs added
Ankit Sultana on 2025-07-17
No new committers. Last addition was Sonam Mandal on 2025-04-14.

## Project Activity:
Recent releases:
Pinot 1.4.0 was released on 2025-09-16.
[Release notes](https://github.com/apache/pinot/releases/) include:
- Multistage Engine Lite Mode (beta)
- Multistage Engine Physical Optimizer (beta)
- ASOF JOIN Support
- Query Cancellation for MSQE with Client-Provided ID
- Pauseless Consumption
The previous release was 1.3.0, released on 2025-02-17.
No new release is expected in the next few months. However, we are focused on
improving Multistage Query performance, and the community has been asking for
modern Java runtime support, and we may explore that during the next quarter.

## Community Health:
The Pinot community doesn’t usually use email lists; it uses Slack instead.
The community members (including existing and new contributors, committers,
PMCs) are very responsive on slack, answering user questions, helping debug etc
(~5772 members in the #general channel, which is an increase of ~300 since
the last report)
Meetups and Conferences:
- The Mountain View meetup group has met 4 times since July.
- The Bangalore meetup group has met once since July.


-----------------------------------------
Attachment BD: Report from the Apache POI Project  [Dominik Stadler]

Report from the Apache POI committee [Dominik Stadler]

## Description:
 - Apache POI is a Java library for reading and writing Microsoft Office file
   formats.

   The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
   is a tool that allows you to map XML files to generated Java classes via
   XML Schema definitions.

## Project Status:
 - Overall: Low activity/Mostly maintenance only
 - Activity on the project is low with no-one willing/able to invest time to
   look for new committers. This project is in a mostly-maintenance mode
   unless someone new starts to invest time.
 - Note: None of the active committers wants to spend time looking for new
   people, so suggesting to reach out to others or invest in "marketing" will
   likely not lead to much improvement.
 - The project still has enough active PMC members to vote on issues and
   perform releases

## Membership Data:
   Apache POI was founded 2007-05-16 (18 years ago) There are currently 41
   committers and 34 PMC members in this project. The Committer-to-PMC ratio
   is roughly 6:5.

   Community changes, past quarter:
   - No new PMC members. Last addition was Marius Volkhart on 2020-12-27.
   - No new committers. Last addition was Marius Volkhart on 2020-12-19.

## Project Activity:
  - Source code hosting on GitBox/GitHub works well as handling of
    Pull-Requests became easier
  - Discussion about moving from minimum Java 8 to Java 11/17 was done with
    the result to do a release 5.5.0 with support for Java 8 soon and then
    upgrade minimum requirements to Java 11 or 17.

## Project Release Activity:
  - 5.4.1 was released on 2025-04-06.
  - 5.4.0 was released on 2025-01-08.
  - XMLBeans-5.3.0 was released on 2024-12-13.

## Community Health:
 - There are a few bug-reports and user-questions which indicates that Apache
   POI is still in use. Questions via email or on Stackoverflow usually get
   answers.

 - Bug-numbers slowly increase over time. Some newly reported issues are
   fixed, but we usually get more bugs/questions reported than are addressed
   by the small number of active committers, so some bugs do not get attention
   any more.

 - We have a very small number of active committers. There are very few
   potential candidates and no-one plans to spend effort to go looking for new
   ones.

### XMLBeans
 - It seems there are is a small but active set of users of XMLBeans besides
   Apache POI itself.

 - Bug influx for XMLBeans is very low in general because it is a stable
   project in maintenance-only mode.

## Bug Statistics:

### Apache POI

 - 635 bugs are open overall (+8)
 - Having 146 enhancements (+3)
 - Thus having 489 actual bugs (+5)
 - 121 of these are waiting for feedback (+1)
 - Thus having 368 actual workable bugs (+4)
 - 0 of the workable bugs have patches available (-3)
 - Distribution of workable bugs across components: {XSSF=108, HSSF=80, SS
   Common=45, HWPF=35, XSLF=32, XWPF=18, POI Overall=14, SXSSF=8, POIFS=7,
   HSMF=6, OPC=6, HPSF=4, HSLF=3, HPBF=1, SL Common=1}

### Apache XMLBeans

 - 165 open issues (+-0)
 - 118 Bug (+-0)
 - 28 Improvement (+-0)
 - 15 New Feature (+-0)
 - 2 Wish (+-0)
 - 2 Task (+-0)


-----------------------------------------
Attachment BE: Report from the Apache Qpid Project  [Robbie Gemmell]

Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, .Net, Go, Java/JMS, Python, and Ruby.

# Releases:

- Qpid JMS 2.8.0 was released on August 25th.
- Qpid JMS 1.14.0 was released on August 25th.
- Qpid ProtonJ2 1.0.0 was released on August 29th.
- Qpid JMS 2.9.0 was released on September 16th.
- Qpid JMS 1.15.0 was released on September 16th.
- Qpid Broker-J 10.0.0 was released on October 10th.

# Community:

- The main user and developer mailing lists continue to be active and
  JIRAs are being raised and addressed in line with prior activity levels.

- There were no new PMC member additions in this quarter.
  The most recent new PMC member is Daniil Kirilyuk, added 22nd January 2024

- There were no new committer additions in this quarter.
  The most recent new committer is Daniil Kirilyuk, added 17th February 2023

# Development:

- Broker-J had its 10.0.0 release, bumping the minimum required Java
  version to Java 17 to facilitate use of Jetty 12, along with various
  other dependency updates and cleanups. Work on more improvements and
  bug fixes is underway towards a 10.0.1 followup.

- ProtonJ2 had its 1.0.0 release including various bug fixes, dependency
  updates, and improvements such as usability tweaks, new APIs
  for the test peer, and the ability to use with either Netty 4.1 or 4.2.
  Work continues on more towards a 1.1.0 followup release.

- Work is ongoing around cleaning up older areas of the Proton core and its
  language bindings, with improvements around flow control and delivery
  fairness, and various updates to the Python binding. Work continues on
  adding transaction support for the C++ binding and other API cleanup
  towards the next release and a later removal of deprecated APIs/features
  in a new major version.

# Issues:

There are no Board-level issues at this time.


-----------------------------------------
Attachment BF: Report from the Apache RocketMQ Project  [Xiaorui Wang]


-----------------------------------------
Attachment BG: Report from the Apache Roller Project  [Dave Johnson]

## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat, Postgres and MySQL, and is known to run on other Java servers
and relational databases. Latest release is 6.1.5 on 2025-04-19.

## Project Status:
The project is mostly dormant with most activity around updating 
dependencies, making sure the code runs on the latest Java releases and 
security fixes.

## Membership Data:
Apache Roller was founded 2007-02-20 (16 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2021-05-24.
- No new committers. Last addition was Yash Maheshwari on 2021-09-01.

## Project Activity:
Except for the Roller 6.1.5 releaase, pretty minimal.

## Community Health:
The Roller community is healthy enough to maintain Roller and make bug
fix and security releases. We're always on the lookout for new contributors.


-----------------------------------------
Attachment BH: Report from the Apache Santuario Project  [Colm O hEigeartaigh]

## Description:
The mission of Santuario is the creation and maintenance of software related to 
XML Security in Java and C++

## Project Status:
Current project status: The Java project is actively maintained and PRs are
getting merged and releases made.
Issues for the board: Nothing to report

## Membership Data:
Apache Santuario was founded 2006-06-27 (19 years ago)
There are currently 18 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- No new PMC members. Last addition was Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Joze Rihtarsic on 2024-05-14.

## Project Activity:
Low activity this quarter. Some dependency updates were merged as well as a
bug fix contributed by a user. We will likely get releases out over the next
quarter with this and another one or two fixes.

## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC


-----------------------------------------
Attachment BI: Report from the Apache SDAP Project  [Nga Thien Chung]

## Description:
The mission of Apache SDAP is the creation and maintenance of software related 
to an integrated data analytic center for Big Science problems

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

## Membership Data:
Apache SDAP was founded 2024-04-16 (2 years ago)
There are currently 22 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Grace Llewellyn on 2024-06-23.
- No new committers. Last addition was Truc Nguyen on 2025-01-18.

## Project Activity:
Last SDAP release was 1.4.0 on 2024-11-04.

Over the summer, Riley Kuttruff mentored a summer intern on one of the 
projects that utilizes SDAP to develop a service for handling insitu datasets 
(as well as, potentially, polygonal datasets (ie, census data)) leveraging 
Apache Sedona and GeoParquet.

The goal of this was to replace the existing insitu service such projects
have been using, as it would not be practical to refactor them into a state
compatible with release under the SDAP project.

The proof of concept developed over the course of this internship showed
great promise, and is a high-priority item to be explored for future
integration into the project.

## Community Health:
Since last quarter, dev@sdap.apache.org had 4 new threads.

### Contributors
Since last quarter, the SDAP community has merged 3 PR and created/updated 
3 Jira issues.

The SDAP community has kept up with its monthly community meetings during which 
members recognize that activity has been low. Members recognize that SDAP is 
overdue for a new release and have discussed changes that should go into a near-
term 1.5.0 release. However, progress is slow going as most active SDAP 
contributors work on NASA funded projects that are impacted by budget cuts. 
Contributions to SDAP are expected to increase as stability is regained and new 
projects that plan to leverage SDAP start in earnest.


-----------------------------------------
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 cdc and batch synchronization of massive
data

## Project Status:
Current project status: Health Issues for the board: There are no Board-level
issues at this time.

## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (2 years ago) There are currently 37
committers and 22 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Naijie Liu on 2025-07-08.
- No new committers. Last addition was Chao Wang on 2025-04-14.

## Project Activity:
- 2.3.12 was released on 2025-09-12
- 2.3.11 was released on 2025-05-21
- 2.3.10 was released on 2025-03-21

## Community Health:
- We have held one community online Meetups in last quarter.

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.


-----------------------------------------
Attachment BK: Report from the Apache Sedona Project  [Jia Yu]

## Description:
The mission of Apache Sedona is the creation and maintenance of software 
related to a big geospatial data processing engine. It provides an easy to use 
APIs for spatial data scientists to manage, wrangle, and process geospatial data

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

## Membership Data:
Apache Sedona was founded 2022-12-20 (3 years ago)
There are currently 24 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.

Community changes, past quarter:
- Feng Zhang was added to the PMC on 2025-10-04
- Dewey Dunnington was added as committer on 2025-10-06
- Peter Nguyen was added as committer on 2025-10-31

## Project Activity:
We achieved several key milestones in the past quarter. In September, we
released Sedona 1.8.0, a major version that introduces Spark 4.0 support and a
new GeoPandas-style API for Python users, significantly enhancing usability
and performance. In addition, we launched two new subprojects under the Sedona
umbrella: SedonaDB, a high-performance single-node database engine for
geospatial data, and SpatialBench, a benchmark suite designed to evaluate and
compare geospatial SQL analytics performance across different database
systems.

## Community Health:
The Sedona community continues to thrive with strong contributor engagement
and growing visibility. In the past quarter, several new contributors joined and
actively submitted numerous PRs, reflected by the sharp increase in activity
across the issues and dev mailing lists. The newly launched SedonaDB
repository gained over 300 GitHub stars within two months, demonstrating
strong community interest. In recognition of outstanding contributions, we
added two new committers and one new PMC member to the project.


-----------------------------------------
Attachment BL: Report from the Apache Serf Project  [Daniel Sahlberg]

## Description:

The mission of the Apache Serf project is creating and maintaining of software 
related to HTTP and associated protocols.

## Project Status:

The project has sufficient PMC oversight.

There are no threats to the sustainability or resilience of the project,
although the project is in general very much dormant due to lack of
need/requirements from our users.

The project has no requests for the Foundation.

## Membership Data:

Apache Serf was founded 2015-08-18 (10 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 Graham Leggett on 2025-06-28.
- No new committers. Last addition was Graham Leggett on 2025-06-28.

## Project Activity:

Recent releases:
* 1.3.10 was released on 2023-05-31.
* 1.3.9 was released on 2016-08-31.

## Community Health:

Serf and Subversion have a significant overlap of committers and PMC members
and Subversion is the only (known) open source project using Serf. New
features in Subversion are therefore the primary driver for development in Serf.

After significant activity last quarter, activity died down due to lack of time.

There are still plans for making a new minor release in the near future.

Our community is fully volunteer-driven and we would like to thank
everyone for their support.


-----------------------------------------
Attachment BM: Report from the Apache ServiceComb Project  [Bao Liu]

## Description:
The mission of Apache ServiceComb is the creation and maintenance of software 
related to a microservice framework that provides a set of tools and components 
to make development and deployment of cloud applications easier.

## Project Status:
Current project status: Ongoing
Issues for the board: change the Chair to Zhangjian He (hezhangjian)

## Membership Data:
Apache ServiceComb was founded 2018-10-17 (7 years ago)
There are currently 38 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Cheng Youling on 2024-10-12.
- No new committers. Last addition was Zhangjian He on 2025-01-28.

## Project Activity:
ServiceComb Java Chassis 2.8.28 was released on 2025-10-20.
ServiceComb Java Chassis 2.9.2 was released on 2025-10-14.
ServiceComb Java Chassis 2.8.27 was released on 2025-09-04.
ServiceComb Java Chassis 2.8.26 was released on 2025-08-30.
ServiceComb Java Chassis 2.9.1 was released on 2025-08-25.

## Community Health:
Overall, community health is good. ServiceComb Java Chassis made 5 releases, 
and there are some bug fixes and improments. We are going to add new PMC 
members and change the chair.


-----------------------------------------
Attachment BN: Report from the Apache ShardingSphere Project  [Liang Zhang]


-----------------------------------------
Attachment BO: Report from the Apache ShenYu Project  [Yu Xiao]

## Description:

ShenYu is a Java native API Gateway for service proxy,

protocol conversion and API governance.


## Project Status:

Current project status: Good Healthy.

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


## Membership Data:

Apache ShenYu was founded 2022-07-20 (3 years ago)
There are currently 58 committers and 26 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 Hongyu Liu on 2025-05-15.
- yu luo was added as committer on 2025-11-05


## Project Activity:


We are released version 2.7.0.2 (2025-08-20)


Software development activity:


 - We added add ai response transformer plugin.

 - We added ai proxy enhanced with SpringAI.

 - We added object and array param for mcp server.

 - We added more friendly prompt information to facilitate debugging.

 - We fixed http sync data password error.

 - We fixed multiple selectors connecting to different registry centers.

 - We fixed mcp auto register bug.

 - We fixed data sync bug.

 - We refactor some infra module.

 - We refactor registry reserved keyword fields.

 - We refactor rule reserved keyword fields.


Meetups and Conferences:


 - Community meetings(4) to discuss development tasks and how to build

an open governance community.

 - 3 topic for ospp (done)

## Community Health:

Overall community health is good.

Since the last report, add new 6 contributors added (currently:415).

add +3 subscribers to dev@shenyu.apache.org mailing (currently:514)


-----------------------------------------
Attachment BP: Report from the Apache SIS Project  [Martin Desruisseaux]

## Description:
The mission of Apache SIS is the creation and maintenance of software providing 
data structures for developing geospatial applications compliant with the model 
of OGC/ISO international standards.

## Project Status:
Current project status: ongoing with high activity from 3 developers
(not all visible yet on the code repository).

Issues for the board: how to help to attract more participants
(see "community health" below).

## Membership Data:
Apache SIS was founded 2012-09-19 (13 years ago)
There are currently 22 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.

Community changes, past quarter:
- No new PMC members. Last addition was Alexís Manin on 2021-05-27.
- No new committers. Last addition was Bruno P. Kinoshita on 2021-06-23.

## Project Activity:
Apache SIS 1.5 has been released last month. It was two years after the previous
release (1.4), which is admittedly too long. This delay was not caused by
inactivity, but by difficulty to focus the work on the most blocking issue
(upgrade of EPSG dependency, which had structural changes). Unfortunately, the
SIS 1.5 release arrived too late for Apache Sedona, which decided to keep their
LGPL dependency in their latest release. The Sedona developers asked for a 1.4.1
release for fixing a bug in SIS 1.4 considered as blocking, but at that time we
thought that removing from SIS 1.5 roadmap all tasks other than EPSG upgrade
would allow us to deliver SIS 1.5 in time. It has not been the case.

A third developer is becoming more active, but his work is on a clone
for now [1]. A pull request will be prepared after more review.

Regarding the difficulty to build SIS, work on Maven 4 made great progress.
The Maven Compiler Plugin 4.0.0-beta-3 is now fully capable to compile SIS,
and work on Maven JAR Plugin is in progress. The current state of full Java
module support in Maven is summarized at [2]. After all items on that list
have been completed, we will be able to switch back the SIS build from
Gradle to Maven with no more hacks.

A question on the SIS developers mailing list about whether we should switch
issues tracking from JIRA to GitHub received positive answers [3]. There is
apparently a consensus that it would help the project's visibility.

[1] https://github.com/Geomatys/sis/commits/feat/Zarr/
[2] https://s.apache.org/dtplk
[3] https://lists.apache.org/thread/1l3l4jog2zv15j7ph0s7jz1vz5kz9jpv

## Community Health:
Communication with Apache Sedona happened on a private channel of Slack,
and stopped after the end of the free trial period used by SIS developers.
We don't know if Sedona still consider the use of Apache SIS as a partial
replacement of current LGPL dependency, neither if the SIS 1.5 release
addressed the issue that Sedona faced with SIS 1.4.

There is some aspects in which the board may help:
* What should we do about PMC members inactive for years? We have done
  roll calls in the past, but refrained to move to emeritus anyone who
  didn't replied with this request.
* How to attract contributors on documentation? SIS has a developer guide [4]
  for trying to help users and contributors, but this guide has not been
  updated for years. Contributing to this documentation may be a useful step
  before contributing to actual code (because it may help to understand the
  international standards followed by SIS, which are not simple),
  but this is usually not the kind of tasks that contributors like to do.

[4] https://sis.apache.org/book/en/developer-guide.html


-----------------------------------------
Attachment BQ: Report from the Apache Solr Project  [Alessandro Benedetti]

## Description:
The mission of Apache Solr is the creation and maintenance of software related 
to highly scalable distributed document search and analytics

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

## Membership Data:
Apache Solr was founded 2021-02-17 (5 years ago)
There are currently 99 committers and 61 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Michael Gibney on 2022-12-21.
- No new committers. Last addition was Matthew Biscocho on 2025-04-30.

## Project Activity:
Recent releases: No new release in the quarter.

Areas of development & interest:
* Work and finalisation of the last 9.x release (released just after the end
  of the quarter)
* Candidate branch for 10.0 release has been cut; minor changes are happening
* API renovation and migration continue
* Changelogs: now using an automated system that eliminates merge conflicts
* Dense vector search improvements and new features are catching up with
  Apache Lucene
* Learning to rank optimisations
* Setup of the solr mcp Apache incubating project:
  https://github.com/apache/solr-mcp (for LLM Solr interaction)
* experimental support for GPU-accelerated vector indexing
## Community Health:
The quarter has been quite active thanks to various initiatives:

- Conferences: Community Over Code(https://communityovercode.org) is one of
  the major conferences on search (from the Apache Software Foundation
  community), There were many talks about Apache Solr (or partially referring
  to it with interesting ideas):
*Search Hackathon, organised by David Smiley and Nazerke Seidan
*Achieving zero downtime and zero cost index upgrade in Apache Solr, Rahul
 Goswami
*Query Alerting (with a Little Help from Apache Solr), Luke Kot-Zaniewski
*Modernizing Metrics in Apache Solr: A New Path for Observability, Matthew
 Biscocho
*Using Modern NLP Models from Apache OpenNLP with Solr, Eric Pugh, Jeff
 Zemerick
*Bring in the Robots!, Eric Pugh
*Exploratory Data Analysis with Solr, Christopher Ball

- Dense Vector Group: Following an idea of a contributor (Kevin Liang), we
  kept going with the dense vector group initiative, meeting monthly. I'm
  personally coordinating it via Jira
(https://i 
 ssues.apache.org/jira/secure/RapidBoard.jspa?projectKey=SOLR&rapidView=633),
 and we have seen a lot of activity with many Pull Requests merged, targeting
 Solr 10.

- New book on Apache Solr "Inside Apache Solr and Lucene: Algorithms and
  Engineering Deep Dive" by Rauf Aliev :
  https://solr.apache.org/resources.html#solr-books

The community feels healthy, active, and with new contributors (that hopefully
will become committers and PMC members).


-----------------------------------------
Attachment BR: Report from the Apache Spark Project  [Matei Zaharia]

Description:

Apache Spark is a fast and general purpose engine for large-scale data
processing. It offers high-level APIs in Java, Scala, Python, R and SQL as
well as a rich set of libraries including stream processing, machine learning,
and graph analytics.

Issues for the board:

- None

Project Status:

- The Apache Spark 4.1 branch has been cut, and Spark 4.1 has entered the QA
  stage.
- Released Apache Spark 4.1.0 preview2 on Sept 28, 2025 and preview3 releases
  on Oct 29, 2025.
- Released Apache Spark 4.0.1 on Sept 7, 2025.
- Released Apache Spark 3.5.7 on Sept 29, 2025.
- Released Apache Spark Kubernetes Operator 0.5.0 on Oct 3, 2025; 0.6.0 on Nov
  7, 2025
- Released Apache Spark Connect Swift Client 0.4.0 on Oct 1, 2025.
- Two SPIPs were recently accepted by the community:
  1. JDBC Driver for Spark Connect
  2. Add llms.txt files to Spark Documentation

Trademarks:

- We engaged with one company that used Spark in a product name.

Latest releases:

- Spark 3.5.7 was released on Sept 29, 2025
- Spark 4.0.1 was released on Sept 7, 2025
- Spark 3.5.6 was released on May 29, 2025

Committers and PMC:

- The latest committer was added on July 1, 2025 (Anton Okolnychyi).
- The latest PMC member was added on Jan 21st, 2025 (Jie Yang).


-----------------------------------------
Attachment BS: Report from the Apache StormCrawler Project  [Richard Zowalla]

## Description:
The mission of Apache StormCrawler is the creation and maintenance of software 
related to an open source collection of resources for building low-latency, 
scalable web crawlers on Apache Storm

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

## Membership Data:
Apache StormCrawler was founded 2025-05-21 (5 months ago)
There are currently 11 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. 
- Dávid Szigecsán was added as committer on 2025-09-23

## Project Activity:
Outside contributions continue to arrive regularly, demonstrating interest and
participation from the broader community. We’re pleased to have added a new
committer, which further strengthens our core team. In addition,
we’ve established our security model to ensure clearer processes for handling
potential vulnerabilities with the ASF security team.
Trademark-related tasks remain in the early planning stages.

Recent releases: 
stormcrawler-3.5.0 was released on 2025-09-16.
stormcrawler-3.4.0 was released on 2025-06-27.

## Community Health:
The StormCrawler community remains active and stable. We continue to receive
pull requests from external contributors and first-time participants, most of
whom address GitHub issues labeled as “good first issue.” These labels have
proven effective in attracting new contributions. Our ongoing focus on
improving documentation aims to further lower the barrier to entry and
encourage continued engagement.


-----------------------------------------
Attachment BT: Report from the Apache StreamPipes Project  [Philipp Zehnder]

## Description:
The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

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

## Membership Data:
Apache StreamPipes was founded 2022-11-16 (3 years ago)
There are currently 33 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- Sven Oehler was added to the PMC on 2025-10-30
- No new committers. Last addition was Marcel Frueholz on 2025-01-23.

## Project Activity:
- Preparing release v0.98.0
- Integrated Develocity for enhanced build insights
- Added translation support to improve accessibility
- Implemented a LoadBalancer for StreamPipes with:
 - Three allocation strategies
 - Dynamic migration algorithms to maintain runtime balance.
 - New monitoring metrics for adapter/pipeline counts and migration performance.

## Community Health:
- Successfully supervised an OSPP project
- Increased discussions and reported issues from users on GitHub


-----------------------------------------
Attachment BU: Report from the Apache Subversion Project  [Nathan Hartman]

## Description:

The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control
solution characterized by its reliability as a safe haven for valuable
data; the simplicity of its model and usage; and its ability to
support the needs of a wide variety of users and projects, from
individuals to large-scale enterprise operations.

## Project Status:

Current project status: Ongoing, mature.
Issues for the board: None at this time.

## Membership Data:

Apache Subversion was founded 2010-02-16 (16 years ago). Prior to
joining ASF, the project began in February of 2000 (25 years ago).
There are currently 90 committers and 49 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Graham Leggett on 2025-07-12.
- No new committers. Last additions were Graham Leggett on 2025-07-13
  and Peter Balogh on 2025-07-11.

## Project Activity:

Subversion supports bindings for several popular languages through
SWIG. This quarter included some maintenance work in our SWIG Python
bindings to support the recent Python 3.14 release.

Subversion supports several credential stores, including KDE's
KWallet. Currently there is work-in-progress to update our KWallet
support to KDE 6.

## Community Health:

Activity tends to come in waves. After several busy quarters, this
late summer / early autumn season has been noticeably quieter.
However, developers monitor the mailing lists and respond when needed.
User questions usually receive helpful responses on the mailing lists,
from both project developers and community members. The codebase,
website, and project infrastructure continue to be improved.

Our community is fully volunteer-driven and we would like to thank
everyone for their support.


-----------------------------------------
Attachment BV: Report from the Apache Superset Project  [Maxime Beauchemin]

## Description:
The mission of Apache Superset is the creation and maintenance of software 
related to data exploration, analysis, visualization, and dashboarding

## Project Status:
Current project status: Healthy, active, and growing! 
Issues for the board: None

## Membership Data:
Apache Superset was founded 2020-11-17 (5 years ago)
There are currently 70 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- No new PMC members. Last addition was Antonio Rivero on 2025-07-16.
- Kuznetsov Nikolay was added as committer on 2025-10-31

## Project Activity:
Still patching our way toward a solid 6.0 release. We've pulled in a ton of
fixes since our last RC, and expect to put up a new one shortly. A lot of
features and fixes are merging daily, with involvement from many new
contributors.

As always, our PMC and Committer rosters are mostly disengaged individuals who
we wish could be set to some form of "inactive" status officially/publicly. In
general, the software itself is moving along steadily, and we're already
working on implementations of our new Extensions framework and MCP service.
7.0 is going to be a Big Deal.

If anything, our biggest struggle is that we have a lot of usage, which means
a lot of Github activity and security issue reporting, but have a seemingly
limited number of people willing to engage in the more operational aspects of
managing this incoming traffic. 

## Community Health:
In trying to raise awareness, we've been hitting the conference circuit. Aside
from Community over Code, we've had a presence at IBM TechXchange, and most
recently OSA CON. We're always open to more opportunities for
evangelism/press/speaking/blogs/podcasts/etc., if there are any to recommend.
Slack is up to 21.5K members, GitHub is only a few Stars away from hitting
69K.

The project is growing, and getting better by the day. The main goal now is to
raise awareness and find more people who are willing to engage/volunteer in
managing it more attentively.


-----------------------------------------
Attachment BW: Report from the Apache Syncope Project  [Francesco Chicchiriccò]

## Description:
The mission of Syncope is the creation and maintenance of software related to 
Managing digital identities in enterprise environments

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

## Membership Data:
Apache Syncope was founded 2012-11-21 (13 years ago)
There are currently 25 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Lorenzo Di Cola on 2023-05-22.
- Alberto Bogi was added as committer on 2025-11-07
- Matteo Tatoni was added as committer on 2025-11-07

## Project Activity:
We are maintaining 3 active branches at present:

* 3_0_X - Syncope 3.0.X maintenance
* 4_0_X - Syncope 4.0.X maintenance
* master - preparation for upcoming Syncope 4.1.X

The maintenance work keeps going on 3_0_X and 4_0_X branches,
which are expected to deliver new releases in the next months.

Recent releases:
* 3.0.14 was released on 2025-10-17.
* 4.0.2 was released on 2025-10-17.
* 3.0.13 was released on 2025-08-08.
* 4.0.1 was released on 2025-08-08.

## Community Health:
We continue to observe questions and support requests from newcomers.

After some time, the PMC voted two new committers, which both accepted.


-----------------------------------------
Attachment BX: Report from the Apache SystemDS Project  [Matthias Boehm]

## Description:
Apache SystemDS is a machine learning (ML) system for the end-to-end
data science lifecycle from data preparation and cleaning, over
efficient ML model training, to scoring and debugging. ML algorithms
or pipelines are specified in a high-level language with R-like syntax,
or related Python and Java APIs, and the system automatically generates
hybrid runtime plans of local, in-memory operations and distributed
operations on Apache Spark.

## Issues for the Board:
- None

## Project Status:
- Current work focuses on adding the missing primitives for a number
  benchmarks, a new API for the alignment of multimodal datasets,
  a new backend for singlenode out-of-core operations, and incremental
  refinements of major internal components for compression, GPUs,
  federated operations, and the use of the Java vector API.

## Membership Data:
- Apache SystemDS was founded 2017-05-16 (incubator process entered
  2015-11-02)
- Last PMC members added 2025-04-30 (Elias Strauss)
- Last committers added 2025-04-30 (Christina Dionysio)
- There are currently 37 committers and 28 PMC members in the project.

## Activity and Health:
- Code activity is healthy with 61 commits (+-0%) in the last 3 months.
- Community growth is healthy with 15 active contributors (-25%)
  in the last 3 months
- Communication is healthy, mailing list activity is improving,
  additional work on better documentation.

## Releases:
- Apache SystemDS 3.3.0 was released on 2025-04-22.
- Apache SystemDS 3.2.0 was released on 2024-03-17.
- Apache SystemDS 3.1.0 was released on 2023-03-13.
- Apache SystemDS 3.0.0 was released on 2022-06-20.
- Apache SystemDS 2.2.2 was released on 2022-06-25.
- Apache SystemDS 2.2.1 was released on 2021-12-02.
- Apache SystemDS 2.2.0 was released on 2021-10-30.
- Apache SystemDS 2.1.0 was released on 2021-06-28.
- Apache SystemDS 2.0.0 was released on 2020-10-14.
- Apache SystemML 1.2.0 was released on 2018-08-24.


-----------------------------------------
Attachment BY: Report from the Apache Teaclave Project  [Zhaofeng Chen]

# Apache Teaclave Board Report - November 2025

## Description
Apache Teaclave provides SDKs for building memory-safe applications on Trusted
Execution Environments (TEEs).

## Project Status
**Status:** New Apache Teaclave graduated as a Top-Level Project on August 21,
  2025. Since graduation, the community has:
1. (1st report) Completed the transition to TLP infrastructure, including
   GitHub repositories, distribution servers, website updates, and project
   documentation.
2. (2st report) Released `teaclave-trustzone-sdk v0.6.0`, the first release as
   a TLP.
3. (this report) Working on the release of teaclave-trustzone-sdk v0.7.0 by
   supporting OP-TEE 4.8.0, enhancing CI/CD infrastructure with automated
   testing, and improving developer tooling and documentation.

## Summary of Project Health and Status
Since the last report, Apache Teaclave has maintained steady progress with
infrastructure updates, version upgrades, and enhanced developer tooling. The
community remains active with steady development and moderate mailing list
discussions. Current focus areas include strengthening coding practices for
the Rust codebase and improving the TEE development experience to allow users
to build and experiment with minimal effort.

## Issues for Board Attention
There are no Board-level issues at this time.

## Recent Releases
- 2025-09-12: Teaclave TrustZone SDK v0.6.0 (first TLP release)

## Project Activity

### Development Activity
- Integrating with OP-TEE to version 4.8.0
- Strengthening CI/CD pipelines with daily automated testing
- Improving developer experience through better error messages and
  documentation.
- Approximately 40 commits merged in the past three months.

### Community Activity
- Developer mailing list: moderate activity (~20 topics in the past 30 days).
- No new committers or PMC members since the last report.
- New contributors joined since the last report, representing potential future
  committers.

## Current Plans
- **Short term (next quarter):**
  - Complete next quarterly release of Teaclave TrustZone SDK, aligned with
    OP-TEE’s release schedule.
  - Enhance onboarding and TEE development experience by simplifying the
    process of building and running TEE examples with minimal effort,
    including Cargo subcommands build and toolchain management.

- **Medium term:**
  - Open source additional real-world SDK use cases (e.g., Web3 scenarios).
  - Maintain alignment with OP-TEE’s quarterly release cadence.

## Community Changes
- Current: 18 PMC members; no new additions since the last report.
- PMC membership represents a healthy diversity of organizations.

## Project Branding
- No branding issues.
- Website and download pages comply with Apache branding requirements.

## Legal Issues
- No legal issues to report.

## Infrastructure
- No infrastructure concerns at this time.


-----------------------------------------
Attachment BZ: Report from the Apache TomEE Project  [David Blevins]

## Description:

Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.

## Health

Overall contributions are still very low for a project of our scope.  Roughly
30 commits from 3 committers in the 2 months since last report.

In July we saw our first PR from a non-committer all year.  There have been
no new PRs from new contributors or non-committers in the last 2 months.

## Activity

Latest activity has been around starting a branch for the implementation of
Jakarta EE 11 and TomEE 11.  The main branch is still dedicated to TomEE 10.x
as of now.

A significant portion of the early work involves deciding which Java versions
will be supported and work associated with the removal of the Java Security
Manager in Java 21.  Additionally, there is work associated with tracking the
progress of our various dependencies such as CXF, MyFaces, OpenJPA and
OpenWebBeans.

All this work is early.  We have a number of failing tests due to security
manager changes.  Switching the main branch from TomEE 10 to TomEE 11 may be
delayed until the build is once again passing.  Discussion there has started.

## PMC changes:

- Currently 13 PMC members.
- Last PMC addition Markus Jung on July 23rd, 2025

## Committer base changes:

- Currently 35 committers.
- Last committer added was Markus Jung on September 12th, 2024
- Previous committer added was Thomas Andraschko on March 25th, 2024

## Releases:

 - Apache TomEE Quartz Shade 2.5.1 on October 31st, 2025


-----------------------------------------
Attachment CA: Report from the Apache Traffic Server Project  [Bryan Call]


-----------------------------------------
Attachment CB: Report from the Apache Training Project  [Justin Mclean]

## Description:
The mission of Apache Training is the creation and maintenance of software 
related to training materials for Apache projects and the Apache Software 
Foundation

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

## Membership Data:
Apache Training was founded 2025-08-20 (2 months ago)
There are currently 18 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.

## Project Activity:
Since the last report, Apache Training has created more training content. New
slide decks have been produced covering community building, voting and
consensus, ASF governance, podling orientation, banding and identity, and
vendor neutrality. Other content created included interactive
scenarios/stories for mentors in the ASF incubator.

## Community Health:
The community is small but active. Contributor activity has been steady, with
a couple of committers regularly involved and a consistent flow of
contributions. There was not much discussion on the mailing list this month,
and although activity is higher than last quarter, we have not had any
contributions from people not previously involved in the project.


-----------------------------------------
Attachment CC: Report from the Apache TsFile Project  [Jialin Qiao]

## Description:
The mission of Apache TsFile is the creation and maintenance of software 
related to a columnar storage file format designed for time series data

## Project Status:
Current project status: Ongoing with high activity. 
Issues for the board: Is there a standard convention 
for publishing the Python dependency package of
tsfile on PyPI? Currently, it’s being published under a community
contributor’s personal account.

## Membership Data:
Apache TsFile was founded 2023-11-15 (2 years ago)
There are currently 21 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 7:6.

Community changes, past quarter:
- No new PMC members. Last addition was Gaofei Cao on 2023-11-15.
- No new committers. Last addition was Xinhao Gu on 2025-04-22.

## Project Activity:
### Recent releases:
- 1.1.2 was released on 2025-09-08.
- 2.1.1 was released on 2025-08-18.
- 2.1.0 was released on 2025-07-11.

### Main work of project:
We’ve released two minor versions to fix some issues. The new 2.x interfaces
are mainly designed for the table model. In the near future, we plan to unify
the write and query interfaces, which means the tsfile read/write layer will
need to support both the tree and table models. To achieve this, we need to
explore a way to automatically convert between models — mapping the original
tree-model files to the table model — so that the new interfaces can read and
write tsfile files generated by the tree model (i.e., version 1.x).

## Community Health:
The activity of the development mailing list has seen a slight decline
recently, because there was a long holiday in China for the National Day and
Mid-Autumn Festival.


-----------------------------------------
Attachment CD: Report from the Apache Turbine Project  [Georg Kallidis]

## Description:

The mission of Turbine is the creation and maintenance of software related to A 
Java Servlet Web Application Framework and associated component library

## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Turbine was founded 2007-05-16 (18 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.

Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers. Last addition was Youngho Cho on 2021-12-06.

## Project Activity:

Recent releases: Turbine 7.0 was released on 2025-06-16. Turbine Parent POM 14
was released on 2025-04-17.

Still in preparation is the Turbine archetype for v7.0 (Turbine + Torque) to be
expected next quarter.

## Community Health:

Code activity is at medium to low levels, including changes for new logo. Next
steps beyond the archetype release are expected to be a next release plan,
probably including updating Fulcrum modules with discussing as usual in the
dev e-mailing list. Further notifications could be considered e.g. by adding
jira or git issues, e.g. with "most wanted" tag.


-----------------------------------------
Attachment CE: Report from the Apache Uniffle Project  [He Qi]

## Description:
The mission of Apache Uniffle is the creation and maintenance of software 
related to a unified remote shuffle service

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

## Membership Data:
Apache Uniffle was founded 2025-02-19 (9 months ago)
There are currently 24 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Xianjing Feng on 2025-05-07.
- No new committers. Last addition was Lu Yuan on 2025-04-10.

## Project Activity:
Apache Foo just completed the release process for 0.10.0.
The verisioncontained a few new features,
but were largely maintenance releases carrying a number of bug fixes.
The project is focusing many improvements
Data Correctness:
1. Add the verification about records between stages
2. Fix the issue of reporting metadata
Performance
1. Decouped the dependency between data process and decompression
2. Cache shuffle handle information reduce RPC cost
3. Read plan helps shuffle to read ahead
Stability
1. Adde safety switch for map-stage combiner
2. Ignore unnecessary error when reporting metrics

## Community Health:
Overall community health is good.
The core contributors continously improve the performance and stability.
Especially for data correctness, the community contributors from different
companies cowork to solve this issue, and the community have a good solution.


-----------------------------------------
Attachment CF: Report from the Apache Velocity Project  [Nathan Bubna]


-----------------------------------------
Attachment CG: Report from the Apache Web Services Project  [Daniel Kulp]


-----------------------------------------
Attachment CH: Report from the Apache Whimsy Project  [Dave Fisher]

## 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: Dormant
Issues for the board: None

## Membership Data:
Apache Whimsy was founded 2015-05-19 (10 years ago)
There are currently 13 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.

Community changes, past quarter:
- No new PMC members. Last addition was Dave Fisher on 2025-07-15.
- No new committers. Last addition was Dave Fisher on 2025-07-16.

## Project Activity:
Project activity is low and is mostly about policy corrections. Generally
little activity occurs, the tools are mature. The Board Agenda Tool has
replaced the Whimsy Reporting tool although the reporter tool managed by
Comdev needs to start submitting reports to agenda.apache.org.

## Community Health:
Community is just healthy enough to fix any problems that may arise. Since
Whimsy is a "Standing Committee" which never releases software the need for
a roll call with three +1 is not critical.


-----------------------------------------
Attachment CI: Report from the Apache Xalan Project  [Gary D. Gregory]

## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible 
Stylesheet Language Transformations) as a compelling paradigm that transforms 
XML documents, thereby facilitating the exchange, transformation, and 
presentation of knowledge. The ability to transform XML documents into usable 
information has great potential to improve the functionality and use of 
information systems. We intend to build freely available XSLT processing 
components in order to engender such improvements.

## Project Status:
Current project status: The project activity has been low to moderate.
Issues for the board: None.

## Membership Data:
Apache Xalan was founded 2004-09-30 (21 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.

Community changes, past quarter:
- No new PMC members. Last addition was Joseph Kessselman on 2023-08-07.
- No new committers. Last addition was Joseph Kessselman on 2023-06-29.

## Project Activity:
We are still, very slowly, progressing towards three Xalan-Java goals:
Another 2.x release, a
3.x alpha or beta release, and migration of the build from Ant to Maven.

## Community Health:
Our project health is moderate with a small but passionate handful of active
committers. The mailing list, GitHub, and Jira activity are low.


-----------------------------------------
Attachment CJ: Report from the Apache Xerces Project  [Michael Glavassevich]

## Description:
Apache Xerces is a collaborative software development project dedicated to
providing robust, full-featured, commercial-quality, and freely available XML
parsers and closely related technologies on a wide variety of platforms
supporting several languages.

## Project Status:
Current project status: Xerces-J activity has been increasing with the newer
contributors. Nothing notable to report on Xerces-C or the other components in
the last quarter.
Issues for the board: None.

## Membership Data:
The most recent committers were added in April 2017 (Xerces-C) and June 2025
(Xerces-J). The most recent addition to the PMC was in June 2025.

Community changes, past quarter:
- No new PMC members. Last addition was Elliotte Rusty Harold in June 2025.
- No new committers. Last addition was Elliotte Rusty Harold in June 2025.

## Project Activity:
The focus for Xerces-J and Xerces-C is maintenance. No new features are in
development. Activity on Xerces-J increased in the last quarter with several
PRs merged from a potential new committer. Along with the newest committer
they have been completing various clean up tasks. There was almost no activity
on Xerces-C in the last quarter (just a response to a JIRA issue that was
opened by the community).

No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022). The latest release is Xerces-C 3.2.5 (December
20th, 2023).

## Community Health:
Our project for more than the last decade has had a handful of dedicated
active committers. Some less active PMC members continue to monitor the
project and respond to queries on security issues as needed. Mailing list,
GitHub, and JIRA activity have been moderate for Xerces-J and very low for
Xerces-C.


-----------------------------------------
Attachment CK: Report from the Apache XML Graphics Project  [Clay Leeds]


-----------------------------------------
Attachment CL: Report from the Apache YuniKorn Project  [Wilfred Spiegelenburg]

## Description:
The mission of Apache YuniKorn is the creation and maintenance of software 
related to a standalone resource scheduler responsible for scheduling batch 
jobs and long-running services on large scale distributed systems running in 
on-premises environments as well as different public clouds

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

## Membership Data:
Apache YuniKorn was founded 2022-03-15 (4 years ago)
There are currently 38 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.

Community changes, past quarter:
- No new PMC members. Last addition was Chia-Ping Tsai on 2024-03-06.
- No new committers. Last addition was Junyan Ling on 2025-06-25.

## Project Activity:
Recent releases:
1.7.0 was released on 2024-07-28.
1.6.3 was released on 2025-05-06.
1.6.2 was released on 2025-03-18.

Release 1.8.0 is planned for a beta in December and an official release late 
January 2026.

## Community Health:
8 new Jira accounts were requested. 36 new Jiras created and 20 resolved,
with corresponding GitHub PRs: 31 created and 25 resolved.

Planning for the 1.8.0 release has been finished. A new version of Kubernetes, 
1.34, to be added to the test and support matrix based on the release cycle.
A design document for a major new feature was shared for discussion on the dev@
list.

New users of the project have joined the slack room. Raising issues based on 
their own testing. They are actively working on providing test cases for these 
issues and helping test fixes.


------------------------------------------------------
End of minutes for the November 19, 2025 board meeting.

Index