The Apache Software Foundation

                  Board of Directors Meeting Minutes

                          December 18, 2024


1. Call to order

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

    Other Time Zones: https://timeanddate.com/s/44g6

    The meeting was held via teleconference, hosted by the Secretary
    via Zoom.

    The #asfboard channel on the-asf.slack.com was used for backup.

2. Roll Call

    Directors Present:

      Rich Bowen
      Shane Curcuru
      Willem Ning Jiang
      Jeff Jirsa
      Justin Mclean
      Jean-Baptiste Onofré
      Craig L Russell
      Sander Striker
      Kanchana Pradeepika Welagedara

    Directors Absent:

      none

    Executive Officers Present:

      Craig R. McClanahan
      Matt Sicker
      Ruth Suehle - joined :02

    Executive Officers Absent:

      David Nalley

    Guests:

      Brian Proffitt
      Daniel Augusto Veronezi Salvador
      Daniel Gruno
      Dave Fisher
      Drew Foulks
      Greg Stein
      Jarek Potiuk
      Melissa Logan - joined :14
      Mike Jumper
      Paul Irwin - joined :08
      Paul King
      Philipp Ottlinger
      Sally Khudairi

3. Minutes from previous meetings

    Published minutes can be found at:

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

    A. The meeting of November 20, 2024

       See: board_minutes_2024_11_20.txt

       Approved by General Consent.

4. Executive Officer Reports

    A. Board Chair [Shane Curcuru]

       As the year end holiday period approaches, open source work slows down
       just like most industries, and gives us a chance to reflect.  Even as
       most contributors are contributing to ASF projects simply for their
       own purposes, it's important to remember that the ASF is a public
       charity.  Much of the ASF's corporate behind-the-scenes workings are
       focused on the public good we provide.

       Similarly, the ASF relies on the charity of others: of our many
       sponsors: those with funding, and in-kind services; and our many, many
       individual contributors around the world.  We also rely heavily on our
       Membership to step up and pitch in with real work, since our Directors
       and operations officers are all unpaid volunteers, helping to oversee
       our projects and all other work at the ASF.

       As the EU's finalization of the CRA now has a specific implementation
       date in three years, we are continuing the groundwork to enable all of
       our projects to meet legislative requirements in the future.  Our VP,
       Public Affairs and other Members are active in the Eclipse Open
       Regulatory Compliance WG to ensure compliance steps make sense for
       open source.  And new VP, Tooling is hiring staff to begin the
       planning and implementation of the build tools our projects will need
       - along with our Infra team.

    B. President [Ruth Suehle]

       December is traditionally pretty quiet operations-wise, and this one
       seems to be no different, aside from getting our new VP Tooling
       rolling and a few small transitional things as I take over for David.

       - Have been invited to represent the ASF at OpenForum Europe EU Open
         Source Policy Summit 2025 on 31 January on the panel  “The Open
         Source Ecosystem: Navigating a World in Transformation”

       - Successfully changed our forwarding address to me, so I will now
         receive mail and deposit checks.

       - One of our biggest priorities right now should be
         finding/encouraging new volunteers for multiple reasons. Our
         workload is increasing, possibly more in the next couple of years
         than it has in quite some time. The board and officers have
         periodically discussed getting more folks to shadow them, but it's
         not simple. I'd love to hear some ideas about /how/ we encourage
         more participation from members. We have 797 "active" on the roster,
         but realistically a much smaller number who are truly active.

       Additionally, please see Attachments 1 through 10.


    C. Treasurer [Craig R. McClanahan]

       Things continue to progress normally, with the addition of assisting
       in transitions in several roles that imply responsibility changes on
       financial matters.

       With regards to Ramp cards in particular, I have not completed an
       entire review, but there are a few situations where individual
       (authorized) users have multiple responsibilities, without necessarily
       using separate cards (and thus each separate expense category) to
       match those responsibilities.  I will follow up as needed in those
       cases.

       Financial reports for November 2024 have been posted to board@ ... let
       me know if you have any questions about these.

    D. Secretary [Matt Sicker]

       In November 2024, the secretary received 35 ICLAs, 5 software grants,
       and one membership emeritus request.

    E. Executive Vice President [David Nalley]

       Nothing material to report.

    F. Vice Chair [Justin Mclean]

       Nothing to report again this month.

    Executive officer reports approved as submitted by General Consent.

5. Additional Officer Reports

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

       No report was submitted.

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

       See Attachment 12

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

       See Attachment 13

    Additional officer reports approved as submitted by General Consent.

6. Committee Reports

    Summary of Reports

     The following reports required further discussion:

        # Airflow [rbowen]
        # Iceberg [jbo]
        # OpenOffice [clr]
        # Portals [ningjiang]
        # Storm [clr]

    A. Apache Airavata Project [Suresh Marru / Rich]

       See Attachment A

    B. Apache Airflow Project [Bolke de Bruin / JB]

       See Attachment B

    C. Apache Allura Project [David Philip Brondsema / Justin]

       See Attachment C

    D. Apache Atlas Project [Madhan Neethiraj / Shane]

       See Attachment D

    E. Apache Avro Project [Ryan Skraba / Craig]

       No report was submitted.

    F. Apache Axis Project [Robert Lazarski / Kanchana]

       See Attachment F

    G. Apache Beam Project [Kenneth Knowles / Willem]

       See Attachment G

    H. Apache Bigtop Project [Masatake Iwasaki / Justin]

       See Attachment H

    I. Apache BVal Project [Matthew Jason Benson / Kanchana]

       See Attachment I

    J. Apache Camel Project [Andrea Cosentino / Sander]

       See Attachment J

    K. Apache Cayenne Project [Michael Ray Gentry / Shane]

       See Attachment K

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

       See Attachment L

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

       See Attachment M

    N. Apache Cordova Project [Bryan Ellis / Jeff]

       See Attachment N

    O. Apache cTAKES Project [Pei Chen / Craig]

       See Attachment O

    P. Apache Curator Project [Enrico Olivelli / JB]

       See Attachment P

    Q. Apache Daffodil Project [Mike Beckerle / Justin]

       See Attachment Q

    R. Apache DataFusion Project [Andrew Lamb / Rich]

       See Attachment R

    S. Apache Directory Project [Shawn McKinney / Kanchana]

       See Attachment S

    T. Apache Druid Project [Gian Merlino / Rich]

       No report was submitted.

    U. Apache ECharts Project [Wenli Zhang / Craig]

       See Attachment U

    V. Apache Felix Project [Karl Pauls / Jeff]

       See Attachment V

    W. Apache Flex Project [Harbs / Sander]

       See Attachment W

    X. Apache Flink Project [Robert Metzger / Shane]

       See Attachment X

    Y. Apache Gobblin Project [Abhishek Tiwari / Willem]

       See Attachment Y

    Z. Apache Guacamole Project [Mike Jumper / JB]

       See Attachment Z

    AA. Apache Gump Project [Stefan Bodewig / Craig]

       See Attachment AA

    AB. Apache Helix Project [Junkai Xue / Shane]

       See Attachment AB

    AC. Apache Hive Project [Naveen Gangam / JB]

       See Attachment AC

    AD. Apache Hudi Project [Vinoth Chandar / Justin]

       See Attachment AD

    AE. Apache Iceberg Project [Ryan Blue / Jeff]

       See Attachment AE

    AF. Apache Incubator Project [Justin Mclean]

       No report was submitted.

    AG. Apache IoTDB Project [Xiangdong Huang / Willem]

       See Attachment AG

    AH. Apache Jackrabbit Project [Marcel Reutegger / Kanchana]

       See Attachment AH

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

       See Attachment AI

    AJ. Apache Kvrocks Project [Mingyang Liu / Sander]

       See Attachment AJ

    AK. Apache Kyuubi Project [Kent Yao / Rich]

       See Attachment AK

    AL. Apache Libcloud Project [Tomaž Muraus / Justin]

       No report was submitted.

    AM. Apache Linkis Project [Shuai Di / Jeff]

       See Attachment AM

    AN. Apache Logo Development Project [Jeff Genender / Rich]

       See Attachment AN

    AO. Apache Lucene Project [Chris Hegarty / Willem]

       See Attachment AO

    AP. Apache Lucene.Net Project [Shad Storhaug / Sander]

       See Attachment AP

    AQ. Apache Mnemonic Project [Gordon King / Kanchana]

       No report was submitted.

    AR. Apache Mynewt Project [Szymon Janc / Justin]

       See Attachment AR

    AS. Apache NetBeans Project [Geertjan Wielenga / JB]

       See Attachment AS

    AT. Apache OFBiz Project [Jacopo Cappellato / Kanchana]

       See Attachment AT

    AU. Apache Olingo Project [Michael Bolz / Craig]

       See Attachment AU

    AV. Apache OpenDAL Project [Hao Ding / Shane]

       See Attachment AV

    AW. Apache OpenNLP Project [Jeff Zemerick / Kanchana]

       See Attachment AW

    AX. Apache OpenOffice Project [Dave Fisher / Craig]

       See Attachment AX

    AY. Apache OpenWebBeans Project [Mark Struberg / Jeff]

       No report was submitted.

    AZ. Apache Paimon Project [Jingsong Lee / Rich]

       See Attachment AZ

    BA. Apache Pekko Project [PJ Fanning / Rich]

       See Attachment BA

    BB. Apache Pig Project [Koji Noguchi / Sander]

       No report was submitted.

    BC. Apache Pivot Project [Roger Lee Whitcomb / JB]

       No report was submitted.

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

       See Attachment BD

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

       See Attachment BE

    BF. Apache Portals Project [Neil Griffin / Willem]

       See Attachment BF

       @Willem: pursue a roll call for PMC

    BG. Apache Pulsar Project [Matteo Merli / Justin]

       See Attachment BG

    BH. Apache Ranger Project [Selvamohan Neethiraj / Jeff]

       See Attachment BH

    BI. Apache Ratis Project [Tsz-wo Sze / JB]

       No report was submitted.

    BJ. Apache Royale Project [Yishay Weiss / Sander]

       See Attachment BJ

    BK. Apache Samza Project [Jagadish Venkatraman / Craig]

       See Attachment BK

    BL. Apache SeaTunnel Project [Jun Gao / Rich]

       No report was submitted.

    BM. Apache ServiceMix Project [Krzysztof Sobkowiak / Shane]

       See Attachment BM

    BN. Apache Shiro Project [Brian Demers / Justin]

       See Attachment BN

    BO. Apache SINGA Project [Wang Wei / Willem]

       See Attachment BO

    BP. Apache Sling Project [Robert Munteanu / Kanchana]

       See Attachment BP

    BQ. Apache SpamAssassin Project [Sidney Markowitz / Justin]

       See Attachment BQ

    BR. Apache Storm Project [Richard Zowalla / Shane]

       See Attachment BR

       @Craig: follow up with Infra about outstanding issue

    BS. Apache Synapse Project [Isuru Udana / JB]

       No report was submitted.

    BT. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Rich]

       See Attachment BT

    BU. Apache Tcl Project [Georgios Petasis / Jeff]

       See Attachment BU

    BV. Apache Tomcat Project [Mladen Turk / Kanchana]

       See Attachment BV

    BW. Apache TVM Project [Tianqi Chen / Willem]

       See Attachment BW

    BX. Apache UIMA Project [Richard Eckart de Castilho / Sander]

       See Attachment BX

    BY. Apache Unomi Project [Serge Huber / Craig]

       See Attachment BY

    BZ. Apache VCL Project [Josh Thompson / Justin]

       See Attachment BZ

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

       See Attachment CA

    CB. Apache Wicket Project [Andrea Del Bene / JB]

       See Attachment CB

    CC. Apache Yetus Project [Allen Wittenauer / Jeff]

       See Attachment CC

    CD. Apache ZooKeeper Project [Flavio Paiva Junqueira / Willem]

       See Attachment CD

    Committee reports approved as submitted by General Consent.

7. Special Orders

    A. Change the Apache Kylin Project Chair

       WHEREAS, the Board of Directors heretofore appointed Shao Feng Shi
       (shaofengshi) to the office of Vice President, Apache Kylin, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Shao Feng Shi from the office of Vice President, Apache Kylin, and

       WHEREAS, the Project Management Committee of the Apache Kylin project
       has chosen by vote to recommend Li Yang (liyang) as the successor to
       the post;

       NOW, THEREFORE, BE IT RESOLVED, that Shao Feng Shi is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache Kylin, and

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

    B. Change the Apache Calcite Project Chair

       WHEREAS, the Board of Directors heretofore appointed Benchao Li
       (libenchao) to the office of Vice President, Apache Calcite, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Benchao Li from the office of Vice President, Apache Calcite, and

       WHEREAS, the Project Management Committee of the Apache Calcite project
       has chosen by vote to recommend Ruben Q L (rubenql) as the successor to
       the post;

       NOW, THEREFORE, BE IT RESOLVED, that Benchao Li is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache Calcite, and

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

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

    C. Establish the Apache Answer Project

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

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

       RESOLVED, that the Apache Answer be and hereby is responsible for the
       creation and maintenance of software related to A Q-and-A platform
       software for teams at any scales; and be it further

       RESOLVED, that the office of "Vice President, Apache Answer" 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 Answer
       Project, and to have primary responsibility for management of the
       projects within the scope of responsibility of the Apache Answer
       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 Answer Project:

       * Zili Chen <tison@apache.org> 
       * Feng Dong <fenbox@apache.org> 
       * Christofer Dutz <cdutz@apache.org> 
       * Nadia Jiang <nadia@apache.org> 
       * Willem Ning Jiang <ningjiang@apache.org> 
       * Shuailing Li <shuai@apache.org> 
       * Luffy <lufei@apache.org> 
       * Fengjun Lv <mingcheng@apache.org> 
       * Justin Mclean <jmclean@apache.org> 
       * Ning Qi <joyqi@apache.org> 
       * Yubin Ren <robin0716@apache.org> 
       * Enxin Xie <linkinstar@apache.org> 
       * Guangfu Yang <kumfo@apache.org> 
       * Anne Zhu <annezhu@apache.org> 

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ning Qi be appointed to
       the office of Vice President, Apache Answer, 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 Answer Project be and hereby is tasked with
       the migration and rationalization of the Apache Incubator Answer
       podling; and be it further

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

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

    D. Change the Logo Development Committee Chair

       WHEREAS, the Board of Directors heretofore appointed Jeff Genender
       (jgenender) to the office of Vice President, Logo, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Jeff Genender from the office of Vice President, Logo, and

       WHEREAS, the Project Management Committee of the Logo Development
       committee has chosen to recommend Daniel Gruno (humbedooh) as the
       successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Jeff Genender is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Logo, and

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

       Special Order 7D, Change the Logo Development Committee Chair,
       was approved by Unanimous Vote of the directors present.

    E. 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 2024.

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

    F. Establish position of VP, ECMA Relations

       WHEREAS, the Board of Directors deems it to be in the best interests
       of the Foundation and consistent with the Foundation's purpose to
       appoint an officer responsible for maintaining the ASF's relation with
       ECMA International.

       NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President,
       ECMA Relations" be and hereby is created, the person holding such
       office to serve at the direction of the President, and to have primary
       responsibility of managing the ASF's relation with ECMA International.

       BE IT FURTHER RESOLVED, that Piotr P. Karwasz be and hereby is
       appointed to the office of Vice President, ECMA Relations, to serve in
       accordance with and subject to the direction of the President until
       death, resignation, retirement, removal or disqualification, or until
       a successor is appointed.

       Special Order 7F, Establish position of VP, ECMA Relations,
       was approved by Unanimous Vote of the directors present.

8. Discussion Items

9. Review Outstanding Action Items

    * Justin: follow up with PMC about board report sections
          [ TomEE 2024-06-19 ]
          Status:

    * David: follow up with report about shadow infrastructure budget
          [ President 2024-06-19 ]
          Status:

    * Shane: follow up about enforcement for privacy policies
          [ Data Privacy 2024-07-17 ]
          Status:

    * Justin: update trademark registration runbook
          [ Trademark management status briefing VP, Brand Management 2024-07-17 ]
          Status: Done

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

    * Justin: follow up on issue for board
          [ Kafka 2024-08-21 ]
          Status:

    * Justin: follow up with trademarks
          [ RocketMQ 2024-08-21 ]
          Status:

    * Justin: Discuss reporter tooling requirements
          [ Shiro 2024-09-18 ]
          Status:

    * Greg: Write up a proposed resolution to require tooling to validate email
          [ Discuss list subscription tools 2024-09-18 ]
          Status:

    * Jeff: Start discussion of communications on board@ specifically the use of
          [ New Business 2024-09-18 ]
          Status:

    * Kanchana: pursue a roll call for PMC
          [ CarbonData 2024-10-16 ]
          Status:

    * Willem: pursue an attic resolution
          [ jclouds 2024-10-16 ]
          Status: jclouds is planning to release 2.7.0 this year.
                  https://lists.apache.org/thread/cqhd78qqlw6fhfz88r5m1oz8865prbqd
                  We can go through the attic resolution after the release.

    * Justin: pursue a roll call for PMC
          [ Libcloud 2024-10-16 ]
          Status:

    * Rich: talk with PMC about certification request
          [ NuttX 2024-10-16 ]
          Status: Zero responses to my inquiry:
                  https://lists.apache.org/thread/h9tjhbn9x35mvff3rbs3hp89mklj366c

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

    * Rich: follow up with updates to reporting tool template regarding statistics
          [ Druid 2024-11-20 ]
          Status: Have not had time to work on this since last meeting.

    * Rich: follow up with Security regarding Geode
          [ Geode 2024-11-20 ]
          Status: Done: Security and the new Geode contributors are engaging,
                  and there is a plan to move forward early next year. No Board
                  action here.

    * Kanchana: pursue a roll call for Mnemonic
          [ Mnemonic 2024-11-20 ]
          Status:

    * Rich: follow up with details regarding AI tooling
          [ Superset 2024-11-20 ]
          Status: Have not had time to follow up on this since last meeting.

10. Unfinished Business

11. New Business

12. Announcements

13. Adjournment

    Adjourned at 21:32 UTC

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

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

Covering the period November 2024

* ISSUES FOR THE BOARD

None.


* OPERATIONS

- Approved the name searches for ANSWER and CLOUDBERRY.
- Advised that the ASF would not permit the proposed use of our MAVEN mark in
  a domain name.
- Provided advice regarding the use of our AIRFLOW mark in association with a
  third party initiative.
- Provided advice to the CLOUDBERRY podling regarding use of ™.
- Provided advice to DORIS regarding links to vendor provided services.


* REGISTRATIONS

The CLOUDSTACK registration in Spain has been renewed for a further 10 years.

The SERVICEMIX and ACTIVEMQ marks have been renewed for a further 10 years in
the US.


* INFRINGEMENTS

Worked with ICEBERG PMC to resolve an infringement on LinkedIn.

Continue to chase a downstream vendor regarding multiple infringements of ASF
marks.

Reached out to a vendor to request correct attribution of our marks on their
website.


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


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

Foundation Comms

* Planned and executed new president announcement:
** Wrote and issued press release announcing Ruth Suehle’s appointment
** Published blog attributed to Ruth Suehle to complement the press
   announcement with a more personalized, forward looking statement
** Issued on the wire
** Reached out to key open source journalists and analysts resulting in 5
   articles to-date
* Drafted press release for to support new fundraising initiatives campaign –
  timing to be determined; met with fundraising team to discuss strategy
* Issued second edition of the Plus One Newsletter, which currently has 71
  subscribers

Foundation Marketing

* Updated the website to support the Giving Tuesday campaign including adding
  a “donate” button to the homepage, sharing multiple posts, and promotion in
  the newsletter

Project Comms

* Received inbound requests and provided guidance for press releases and
  external promotions to the following projects:
** Solr
** Cloudberry
** Guacamole
** Subversion
** SeaTunnel

Foundation Content

* Drafted byline based on the CISA tabletop at Community Over Code to be
  pitched to a third-party publication
* Drafted byline highlighting the Community Over Code Keynotes for publication
  on Apache.org and syndication on DZone

Social Media Overview

In total, 61 posts were published: 46 Tweets + 15 LinkedIn. The highest
performing content was news of Ruth becoming ASF’s new president.

Social Highlights (X + LinkedIn)

* Total Audience: 140,987
* New Followers in November: 33#
* Total Impressions: 81,947 (11.5% increase MoM)
* Total Engagements: 3,400 (9.5% increase MoM)
* Post Link Clicks: 2,001 (5.6% increase MoM)

# ASF experienced a large drop (300+) in followers on X in November, which can
  likely be tied to the US presidential election results. Despite X, all key
  metrics marked an upward trend.

Website Analytics

* 895,063 visits, 895,012 unique visitors -7.1%
* 2 min 39s average visit duration +3.9%
* 45% visits have bounced (left the website after one page) +2.3%
* 9.6 actions (page views, downloads, outlinks, internal site searches) per
  visit -19.3%
* 10,007 max actions in one visit 0%
* 7,715,144 pageviews, 1,107,544 unique pageviews -26.9%
* 10 total searches on your website, 7 unique keywords +233.3%
* 473,658 downloads, 327,363 unique downloads -13.7%
* 361,339 outlinks, 218,309 unique outlinks +18.5%


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

General
=======

Infrastructure is operating as expected, and has no current issues
requiring escalation to the President or the Board.

Finances
========

- Infra is expecting a targeted donation to support replacement of
  some Cassandra build nodes.
- Personnel-related expenses will be under budget due to staffing
  changes.
- No significant changes related to the 2024/25 budget are expected.

Hiring
======

- Infra Admin working with VP Tooling on setting up the Tooling job
  posting
- Infra staff developing updated job description for sysadmin
  backfill position, likely to hire during Q1 2025.

Travel
======

- No upcoming travel

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

Code signing changes courtesy of Mark Thomas:

"We have moved to ssl.com's eSigner service. The new service was set
 up from scratch in less than 24 hours and all projects that use code
 signing have been moved over to the new service and completed a test
 signing."

Infrastructure Community Engagement
===================================

Infrastructure has been working to help enable the Builds community
with GitHub Actions resources. The end goal of the effort is to make
the GitHub builds systems managed primarily on a self-serve /
volunteer basis, including security notifications. To this end, we
deployed a GitHub Actions workflow scanner to notify communities of
policy infractions, insecure GitHub Action workflow configurations
and remediation strategies. We are actively working to implement
workflows to further help us secure and facilitate the use of our
GitHub Actions builds alongside the ASF Security team.

Infrastructure is working with ComDev to provide resources for some
upcoming ComDev POCs around community engagement efforts.

In November we had two roundtables, the first of which at a time
amenable to the EU/US and the second targeting APAC timezones. The
discussion focused on lessons learned from the CISA tabletop exercise
that Infra attended at the Denver gathering. The December 5th
Infrastructure Roundtable presentation was rescheduled to January
8th,
2025.

The "Serverside chat with Infrastructure" track at the Denver C/C was
successful. Our talks averaged 9-10 attendees and we had many good
interactions at the Infra table.

General
=======

- Infra continues to evaluate email system improvements to address
  ongoing issues with DMARC/DKIM/SPF and ezmlm mailing lists.

- Infra is iterating on the CISA tabletop results and industry best
  practices to improve our overall security posture, and is
  progressing on efforts surrounding MFA.


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

November through Dec 9

Onboarded as VP, Tooling. Working with the Infrastructure Admin Chris
Lambertus to post the Senior Engineer, Tooling position on Indeed. Worked with
the VP of Fundraising Bob Paulin on two possible funding sponsorships.

Plan for the Tooling position is as follows:
1. Hire for the position. I have some volunteers to help with the interview
   process.
2. Onboarding.
3. Review the status of the Apache Trusted Release initiative and create a
   Statement of Work to incorporate plan and deliverables.
4. Review the state of the Board Agenda tool and then create a Statement of
   Work to plan to deliver the updated tool. We should make progress on this
   list before adding additional tasks.


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

NA

Community Over Code NA 2025 site visits will happen in early January, and an
announcement about the dates and venue should be ready to be made in
mid-January.

EU

Community Over Code EU in 2025 will not be taking place. Instead, there will
be a shift to an alternating-year strategy, with NA in odd-numbered years and
EU in even-numbered years. This will enable the Conferences team to focus on
one event at a time, and ideally not pull sponsors' attention (aka budgets)
from between multiple events.

APAC

Paul King has taken the initiative to speak with Trifork, an events organizer
in Australia and the EU, about holding a small one-day event in Australia
around the September timeframe. This event, possibly a one- or two-track
single-day event, could possibly be colocated with one of Trifork's YOW! or
GOTO events. Paul, who has graciously agreed to run point on this, and BKP
will meet with Trifork after mid-January.

Willem Jiang has informed Conferences that Community Over Code Asia is looking
at a July date for that event. Details forthcoming.


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

Previous Events
===============

Community Over Code EU/Asia/NA 2024
----------------------------

Post event surveys are still coming in but need completing and posting
to the tac website. Needs a volunteer to collate the already collected
information.


Current Events
==============

No current events. Fosdem is the next event we usually support a few
people attending and so we should open up applications for that one
soon.

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

With no current events these meetings are ad-hoc. I will arrange one
for next month to talk about Fosdem at least.

TAC App
=======

TAC App is closed currently with no events happening. At some point
soon, we need to gather a set of improvements / bug tweaks for a quote
to improve the app.

Future Events
=============

Looking into other events.

Short/Medium Term Priorities
============================

Keeping an eye out for other smaller events to support. Post surveys
for Bratislava, Hangzhou and Denver.

Mailing List Activity
=====================

Not much activity this month

Membership
==========

No changes to the Committee this month.


-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion  [David Nalley]


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

# General

There are no issues that need urgent attention.
One question about handling of mailing lists may require board input:
Should posting to a mailing list without a subscription be allowed or not?
(details below).

Currently, 66 tracking codes were requested (+13).
22 Matomo sites don't receive traffic at this point (+7).

1 Person was added to the privacy committee.

## Shadowing and Privacy Committee

I have offered an opportunity to "shadow" and also
renewed the offer to join the "privacy committee." 
I plan to train a person to take over the privacy office
when it is time or at least have a group of people
in the committee, who feel responsible for handling the requests.

Niall Pemberton has accepted the offer to join the committee.
Alin Jerpelea has expressed interest in shadowing the privacy office.

## Privacy policies for downloadable products

Products that can be used for end users (like OpenOffice) may need a privacy policy regarding how they track users of their software. 
Some products (like Airflow) may use Scarf for user behavior tracking; some may not track at all. For both categories of products, a privacy policy that can be linked from within the product is needed.

* https://privacy.apache.org/policies/privacy-products-policy-high.html
* https://privacy.apache.org/policies/privacy-products-policy-medium.html

Both policies are still in discussion. Scarf is a problematic våendor, 
so please consider both policies as work in progress.

## Repeated Mailinglist archive requests

### Normal requests

Users have sent emails in the past and wish they had been redacted now.
The GDPR demands we remove those emails. We have previously stretched
and said, "No, because we can't." We considered the public distribution of the
emails and rejected it as excessive.

With Niall volunteering to help, we plan to redact
specific user information from emails if requested. The problem is that we will
need to adjust responses sometimes, too, since a signature might be quoted.

After some time, we will report how many archive modifications we have received and if this can be handled.

We have handled our first two of these kind of requests.
If you want to learn about the details, please see this thread:
https://lists.apache.org/thread/yqkfl9o37hjw0vq7f794g7ckt0k35ck8

### Requests that clearly demand redaction

Some projects allow users to click a button and post to a mailing list.
Users sometimes don't know that this is public and ask for redaction.
These redactions need to be made. To reduce the number of those requests,
I am recommending either:

a) add a clear warning to every button that the content will be public
b) remove the feature to post to the mailing list without a subscription, and receive proper information about the nature of a mailing list.

I ask the board to decide if a specific proposal is preferred.

## Responsibility for the Matomo VM

Currently asked in:
https://issues.apache.org/jira/browse/INFRA-26365

## Kapa.AI

Kapa changes were applied, and the service is now usable.
Once the signature is done, I will store the DPA in our repo.

# Open tasks

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


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

- The Cyber Resilience Act (CRA) was published in the EU Official Journal on
  November 20, 2024 as
 'EU 2024/2847' - the gazetteer/hansard in which laws get published. That
  means it came into effect on the 11th of December 2024; the requirements
  with regard to processes and notified bodies apply from 11th of June 2026;
  and the whole act coming into effect on the 11th of December 2027.

 The expected `panic' is materialising; but nowhere near as bad as we once
 feared. We probably should do some sort of blog post again.

- The ASF application for the CRA Expert Group was accepted[1]. Final lineup
  is quite balanced; with some strong technical individuals such as Prof.
  Praneel and with more open source considerate representation than expected
  (Eclipse, OpenSSF, Stackable, DE tech fund, Digital SME Alliance) but still
   nowhere near reflective of the relative market share/CRA impact of actually
   deployed software in Europe.

- Eclipse finally dotted most legal i&t's on the ORC-WG. We're not quite there
  yet - as the SIGs are not yet created.

- Meanwhile - there is a lot of good work going on in the OWASP community
  around SBOMs; and I am hoping the ORC-WG and this work will simply align -
  one for the code; the other for the standards and best practices.

-  While most of the ESOs (normative standards bodies) are still not
   responding to us - we are slowly seeing more open source aligned parties
   becoming members. In this light - Pjotr is volunteering to liaise with
   ECMA; and after discussion on public-affairs@ - I'd like to request the
   appointment per below resolution.

- We attended the LF workshop in Amsterdam on the CRA. OpenSSF@LF announced
  that they are creating a ORC-WG competing effort called the  "Global Policy
  WG" with 3 SIGs: (Standards, Awareness en Tooling). Which is goodness - more
  focus and more volunteers is needed. That said - there was considerable
  annoyance in the wider community present about this lack of cohesion or
  collaboration. LF however contents that this effort is very much focused on
  implementing the CRA within their own organisation - and stresses that the
  mission is very narrow and limtied. This is however not quite in line with
  the mission as stated on https://github.com/ossf/wg-globalcyberpolicy/.

- The wider open source community is picking up new US regulation that
  requires federal (eg. software) suppliers to disclose/track any foreign
  nationals involved:

 https://www.federalregister.gov/documents/2024/11/15/2024-26058/defense-federal-acquisition-regulation-supplement-disclosure-of-information-regarding-foreign

 and the relatively late addition of 'Section 239.7X03' that should exempt
 open source. There appears to be a lot of concern if this covers what we call
 open source; with the impact of the definition[2] getting debated.

- Ruth and I are trying to see if we can get some boots on the ground in
  Washington.

- There is an increasing awareness of the various open standards relevant
  regulation
 (like the USA financial stability act, the EU interop act, etc) and its
  interaction with open source and regulation. For a good introduction - see:
  https://opensource.org/blog/standards-and-the-presumption-of-conformity
  which is worth a read; as that directly impacts us -- there is no easier way
  to be interoperable that by using the same software - and netwerk
  effects/less friction always wins from the written standards).

1:
https://ec.europa.eu/transparency/expert-groups-register/screen/expert-groups/consult?lang=en&groupId=3967&fromMembers=true
2: Open source software means software for which the human-readable source
code is available for use, study, reuse, modification, enhancement, and
redistribution by the users of such software (section 1655, Pub. L. 115-232).
https://www.govinfo.gov/content/pkg/PLAW-115publ232/pdf/PLAW-115publ232.pdf


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


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

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

We're working with DLAPiper on two subpoenas -- no action required from the
board at this time -- since we're handling everything in a timely fashion, but
please see a private section below for a bit more color.

Sadly, given the amount of time spent on two subpoenas, I ran out of time on
adding the explanation of Sublicense vs. Relicense language to our LEGAL FAQ
(see LEGAL-687 for more details). I'm going to reach out to the rest of the
 committee members for help to unblock this.

We were contacted by the European Commission with a request to comment on a
merger deal (see private section for more details on this). The initial
questionnaire was clearly aimed at a traditional software organization
competing in the market. Since the ASF is nothing like that and has quite
unique role to play in the Open Source Software supply chain we engaged with
the EC representative to explain our charter and mission first. Quite to our
mutual delight that explanation alone resolved the matter completely
(without answering said detailed questionnaire).


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

November

* We helped several projects configure GitHub Actions securely and improved
  https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+Security

* We continue to encourage projects to describe their project-specific
  security model, recently StreamPark, CarbonData and DolphinScheduler

* We've started documenting the locations where projects share information
  on the (non)exploitability of issues in their dependencies, such as
  Solr and Kafka.

* We've disabled GitHub Private Vulnerability Reporting for several
  projects that still had it enabled from before their transition into
  Apache. We would still like to provide projects the option to use
  this feature, but are still missing some automation around
  notifications and access which are tracked in INFRA-25020.

* We're working on standardized messaging for the second step of the
  formal security escalation process,
  https://cwiki.apache.org/confluence/display/SECURITY/Project+Security+Response+Formal+Escalation

* We've further improved the SBOM tools at https://sbom.security.apache.org/
  to encourage projects to publish SBOMs.

Stats for November 2024:

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

Security reports: 84 (last months: 76, 72, 64)

        20 ['website or other infrastructure']
        6 ['huntr']
        5 ['airflow', 'httpd', 'tomcat']
        4 ['hertzbeat']
        3 ['solr']
        2 ['activemq', 'cloudstack', 'kafka', 'nifi', 'openoffice', 'superset']
        1 ['apr', 'arrow', 'camel', 'cassandra', 'cisa', 'cocoon', 'cpe',
           'doris', 'hive', 'ignite', 'inlong', 'jackrabbit', 'mxnet', 'ofbiz',
           'ranger', 'shiro', 'spamassassin', 'spark', 'streampark', 'thrift',
           'trafficserver', 'tvm', 'wicket', 'zookeeper']

In total, as of 1st December 2024, we're tracking 168 (last months:
175, 179) open issues across 59 projects, median age 117 days (last
months: 107, 69). 60 of those issues have CVE names assigned.  17
(last month: 15) of these issues, across 10 projects, are older than
365 days.

Updates for projects with 'red' status:

* oozie: Project is dormant. Oozie are unable to respond to security
  reports, with one outstanding, and another one which has been fixed
  for more than 6 months but not released. We are at the second step
  of our formal escalation process. (Last update: 2024-12-09)

Updates for projects with 'amber' status:

* ambari: PMC states they have a very small community delaying
  security issue response. We have advised them to seek help from
  experts outside the PMC on a case by case basis. (Last update:
  2024-11-28)

* commons: One issue in Commons is over 365 days old (Last update:
  2024-10-15)

* fineract: the PMC has been attempting to engage more of the wider
  Fineract ecosystem to help triage, fix and release security issues,
  but with limited effect so far. (Last update: 2024-11-01)

* geode: Four issues in Geode over 365 days old. (Last update:
  2024-11-26)

* hive: Three issues in Hive are over 365 days old (Last update:
  2024-11-28)

* openoffice: Two issues in OpenOffice over 365 days old (Last update:
  2024-11-21)

* zeppelin: Several open issues with a history of not dealing with
  security issues well (Last update: 2024-11-28)


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

## Description:
The mission of Apache Airavata is the creation and maintenance of software 
related to executing and managing computational jobs on distributed computing 
resources including local clusters, supercomputers, national grids, academic 
and commercial clouds.

## Project Status:
Current project status: The Project is active, and the community remains
small but healthy.
Issues for the board: No issues to report.

## Membership Data:
Apache Airavata was founded 2012-09-18 (12 years ago)
There are currently 44 committers and 27 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 Lahiru Jayathilake on 2024-04-07.
- No new committers. Last addition was Praneeth Chityala on 2024-04-25.

## Project Activity:
Apache Airavata just made a release (on 2024-12-10) of the security components
of the projects as a stand-alone Apache Airavata Custos. The activity is
progressing to also release other sub-systems.

## Community Health:
Community has been steady. It is welcoming to see recently joined PMC member
Lahiru was able to learn through the ropes of Apache releases and finished up
the process. Activity on GitHub remains slow but with study progress. We are
hoping unblocking the long pending releases will reenergize the community. We
will aspire to get back to periodic strident release schedule.


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

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

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

Issues for the board:

No issues for the board.


## Membership Data:
Apache Airflow was founded 2018-12-19 (6 years ago)
There are currently 68 committers and 35 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- Vikram Koka was added to the PMC on 2024-10-19
- Gopal Dirisala was added as committer on 2024-10-28
- Pavan Kumar was added as committer on 2024-10-29
- Karthikeyan Singaravelan was added as committer on 2024-10-28

## Project Activity:

- Development for Airflow 3 continues at a rapid pace, with several key
  features and enhancements actively being worked on. The target release is
  still set for March/April 2025. A good summary of the progress:
  https://lists.apache.org/thread/r6hcyx8h023h42zz2xz94sz524v1z81w

- The community continues to maintain and release updates for the 2.x series
  alongside the development of 3.0 to ensure stability and support for users
  during the transition. Airflow 2.10.2 and 2.10.3, alongwith 7 batch releases
  of providers were released in this period and
  2.10.4 is being voted on currently. Full release activity:

 - Provider packages 2024-11-24 was released on 2024-11-27.
 - Provider packages 2024-11-14 was released on 2024-11-18.
 - Apache Airflow 2.10.3 was released on 2024-11-05.
 - Provider packages 2024-11-03 was released on 2024-11-05.
 - Provider packages 2024-10-27 was released on 2024-10-31.
 - Provider packages 2024-10-10 was released on 2024-10-14.
 - Provider packages 2024-09-27 was released on 2024-10-01.
 - Provider packages 2024-09-21 was released on 2024-09-24.
 - Apache Airflow 2.10.2 was released on 2024-09-20.

- Security:

    We are proceeding with “Airflow Beach Cleaning” project with Alpha-Omega
    and Python Software Foundation with a goal to review and help all Airflow
    Python dependencies (700+) in terms of their security processes,
    willingness to cooperate and “cleaning” our part of the security beach. We
    are engaged with - currently < 20 initial projects and based on those
    conversations we will scale our efforts in the coming months and years -
    with the goal of sharing our practices and teaching others in the
    ecosystem to follow up similar patterns. We speak at FOSDEM and submitted
    talks to FOSS Backstage and Pycon US next year where we want to share our
    experience and enthuse others to follow.

- Meetups, Conferences & other community events
  - Fortnightly Airflow 3 dev calls have had ~30 attendees from various
    stakeholders: Astronomer, AWS, Bosch, Cloudera, Google. They have been
    very productive for Airflow 3 development. Meeting notes at
    https://cwiki.apache.org/confluence/x/8ApeEg . This is more focussed
    towards developers; we have a separate monthly Airflow Town Hall call for
    users which attract ~50 attendees too, e.g
    https://lists.apache.org/thread/015ormvpbj0172gfh2ftvyytj2vwrt5m

  - Videos from Airflow Summit 2024 have been uploaded on Airflow's YouTube
    channel: https://www.youtube.com/@ApacheAirflow/playlists

  - 100+ attendees in local meetups in London, NYC in the last quarter.
    Upcoming local meetups in Vancouver (in Feb 2025):
    https://www.meetup.com/paris-apache-airflow-meetup/

  - Planning is underway for Airflow Summit 2025


## Community Health:
- Commit velocity has shown a great increase (14% QoQ) owing to Airflow 3 
  developement with a 28% increase in new PRs opened.

- The Dev mailing list activity has reasonably decreased as we have moved on
  from planning phase to execution phase for Airflow 3.

- Committers have done a great job in creating a large number of "good first
  issues" to attract more contributors who could also help in Airflow 3
  development. This shows up in the numbers too: 14% increase with 233 code
  conitrbutors this quarter:

   https://github.com/apache/airflow/contribute

  A good example of one such project here which had tons of new contributors:
  https://github.com/apache/airflow/issues/42370
  https://lists.apache.org/thread/bkkww0lfj7qhsqlxlyywynzglng2v346

- Downloads of the main Apache Airflow package have jumped to over 31
  million/month (https://pypistats.org/packages/apache-airflow)
- GitHub stars: 31,552
- GitHub Contributors: 3,157
- Airflow Slack workspace members: 55,000
- Two new books have been published on Airflow
  - Data Pipelines with Apache Airflow, Second Edition from Manning
    Publication
  - Apache Airflow Best Practices: A practical guide to orchestrating data
    workflow with Apache Airflow from Packt Publishing


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

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

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

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

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

## Project Activity:
- dropped python 3.8 support
- converted API spec/docs from RAML to OpenAPI
- dependency upgrades
- some minor new features & speedups


## Community Health:
- API spec/docs changes were from a new contributor
- low but steady development from normal contributors


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

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

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

## Membership Data:
Apache Atlas was founded 2017-06-20 (7 years ago)
There are currently 49 committers and 32 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 Ashutosh Mestry on 2019-04-16.
- Chaitali Borole was added as committer on 2024-10-06

## Project Activity:
- Atlas community has started work to release 2.4.0, likely by end of
  December-2024
- UI fixes to improve entity details page
- Improve resiliency of migration import functionality
- JanusGraph version updated to 1.0.0
- Replaced the last remaining use of log4j with logback
- Python API fixes, released apache-atlas 0.0.16
- Code readability improvements: use of sortpom plugin to keep pom file
  contents in order
- Updated version of dependent libraries: Spring Security, xml2js, qs,
  decode-uri-component, minimatch, json5, http-cache-semantics, tough-cookie,
  node-sass, commons-fileupload, jetty, testng, protobuf-java, Spring
  Framework, Netty, spring-webmvc, send, serve-static and elliptic

## Community Health:
- dev@atlas.apache.org had a 49% increase in traffic in the past quarter (350
  emails compared to 235)
- 21 commits in the past quarter, an increase from 10 commits the previous
  quarter
- 7 code contributors in the past quarter, an increase from 4 in the previous
  quarter

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


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


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

# Apache Axis Board Report

## Description

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

## Issues

There are no issues requiring board attention at this time.

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

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

Community changes, past quarter:
 - Currently 62 PMC/ 63 Committers members.
 - No new committers were added in the last 90 days, last committer added
   was Bill Blough on December 7th 2017 who also was added to the PMC on
   May 9th 2018.

## Project Activity:
Recent releases:
 - Axis 2/Java 1.8.2 was released on July 14, 2022.
 - Axis 2/Rampart 1.8.0 was released on Dec 10, 2024.
 - Axis 2/C 1.6 was released on April 20, 2009.
 - Axis 1.4 was last released in 2006.
 
## Project state: Ongoing, with moderate activity

## Health report:

Apache Rampart 1.8.0 (WS-trust and WS-secure-conversation) was just released - 
the first release in over 7 years. It was a very challenging release with a 
several year dev cycle, because of the upgrades of Opensaml and Apache WSS4j that 
were both two major versions behind. 

The Rampart 1.8.0 release is also noteworthy because it was under maintained even 
before 2017 - with about 20 patches applied that were languishing for years, and
unfortunately, more than a decade in some cases. This is partly explained
by that no active committers currently use Rampart in their own projects. 

An upcoming Axis2 release is waiting on an Apache Axiom release from the Apache
Web Services project. Several Axis committers are also committers in the Web Services project. It's up to us, actually, to make all that happen.

Axis2 C PMC member Bill Blough last commit to axis-axis2-c-core was Feb 12 17:06:52 2023.  

This past quarter, the Axis2 Java team got busy with Rampart and Axis2 Java. 

We expect commits to axis-axis2-c-core this upcoming quarter as some of us 
Java people can program in C and have some use cases in their own projects that
will benefit the community by helping to put out the first release since 2010. 
 

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

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


## Axis2 Rampart Jira issues opened in the last 90 days: 0

## Axis2 Rampart Jira issues closed in the last 90 days: 28


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

## Description:

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

## Project Status:

Current project status: Ongoing
Issues for the board: none

## Membership Data:

Apache Beam was founded 2016-12-20 (8 years ago)
There are currently 96 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.

Community changes, past quarter:
- No new PMC members. Last addition was Alex Van Boxel on 2023-10-01.
- No new committers. Last addition was XQ Hu on 2024-06-24.

## Project Activity:

Recent releases:
- 2.61.0 was released on 2024-11-25.
- 2.60.0 was released on 2024-10-17.

New use case studies published:
- [Yelp](https://beam.apache.org/case-studies/yelp_streaming/)
- [Accenture](https://beam.apache.org/case-studies/accenture_baltics/)

Technical highlights:
- Iceberg / Configuration Driven / Managed Transforms: mentioned in June,
  there is a new direction with some momentum to make Beam transforms
  configuration-driven (see also: Beam YAML). This can also more easily enable
  a runner to read the configuration and understand the _intent_ of the
  pipeline, rather than having to simply execute user code as a black box.
  Since last report, the API to use this was added to Python SDK and many
  connectors have been added as capabilities. Most notably this is the primary
  way we are recommending users to use the new IcebergIO which has gotten a
  lot of attention and matured rapidly.
- The Prism runner, our at-long-last answer to having a fully capable
  multi-language runner, continues to approach full parity. A large number of
  model compliance tests pass. Soon it will be ready to be default for
  applicable users.
- Healthy breadth of work: Many other incremental features and optimizations
  (the lifeblood of a project) added to MqttIO, SparkRunner, compression
   support, RunInference, BigQueryIO, KafkaIO,

Dependencies/integrations updates:
- Added support for Flink 1.19 and removed support for Flink 1.15 and 1.16
  (our informal policy is to support three versions, currently 1.17, 1.18, and
   1.19)
- Removed support for Python 3.8 (it is approaching EOL)


## Community Health:

Discussions on dev@ seem to be slowing, but the ones that happen are
substantive, to the point, and resolve quickly with useful action. It has,
however, made it more difficult to identify new committers (we look at a wide
variety of data sources, but dev@ is critical).

- The amount of spam reaching human moderation and lack of round-robin to
  spread the moderation load makes it somewhat infeasible to filter actual
  user-authored moderated messages, but happily the spam does not read the
  user or dev community.


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

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

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

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

Community changes, past quarter:
- Yu Hou was added as committer on 2024-09-13

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

bigtop-manager[1] is actively developed. 61 pull requests are merged
in the past 3 months.

We are discussing and working on the next 3.4.0 release[2].
It is targeting upgrading supported distros to latest LTS releases and
major upgrade of Hive to 4.0 and Spark to 4.0.

[1] https://github.com/apache/bigtop-manager/
[2] https://issues.apache.org/jira/browse/BIGTOP-4218

## Community Health:
Community health is good. We added 1 new committer since the last report.

dev@bigtop.apache.org had a 5% decrease in traffic in the past quarter
 (375 emails compared to 391):
issues@bigtop.apache.org had a 1% decrease in traffic in the past quarter
 (266 emails compared to 267):


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

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

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

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

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

## Project Activity:
As per usual, low-level maintenance activity only.

## Community Health:
All indications are that project personnel remain sufficiently engaged
to manage releases as necessary, despite the mostly static nature of
our contributor base (committer added during Q3 notwithstanding).


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

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

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

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

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

## Project Activity:
Apache Camel:
- We released Camel 4.4.4
- We released Camel 4.8.0
- We released Camel 4.8.1
- We released Camel 4.8.2
- We released Camel 4.9.0
- Note: Camel releases have synchronized releases of Camel-Karaf and
  Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
  synchronized.
- The 4.4.x release is our LTS release train and we released the 4.4.4 patch
  release.
- 4.8.x is our last LTS release train. We released the main version 4.8.0 with
  two others patch releases 4.8.1 and 4.8.2
- The situation is really healthy and the community is super. We are
  introducing many new features and working on engaging the community more.
  Camel is growing even in terms of interest

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

Apache Camel Kamelets:
- We released Camel Kamelets 4.8.0
- We released Camel Kamelets 4.8.1
- We released Camel Kamelets 4.9.0
- Working on releasing 4.8.2
- The 4.8.x release train is matching the LTS release from Camel core and it's
  an important building block for starting with routes
- We introduced a lot of new Kamelets and we are improving the documentation
  by focusing on much more examples
- We released also 4.9.0 which is a development version

Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases with
  multiple releases
- We released Camel-quarkus 3.15.0
- We released Camel-quarkus 3.15.1
- We released Camel-quarkus 3.16.0
- We released Camel-quarkus 3.17.0
- The 3.15.x is matching the 4.8.x release train from the main project
- A lot of work has been done on testing side and many good features and
  extensions have been developed and improved.
- There is already the 3.17.0 based on 4.9.0 on vote. It should be out before
  the board meeting.

Apache Camel-Karavan:
- Camel-Karavan is improving and the community around the project is
  increasing in number of features and new issues reporting
- We released the 4.8.0
- We released the 4.8.1
- The 4.8.x is aligned to Camel 4.8.x LTS

Camel-Kafka-Connector:
- 4.4.3 has been released and we plan to align to the next patch release
- 4.8.0 has been released and based on the last LTS release train 4.8.0
- The community is active and we receive a lot of feedback and requests.

Apache Camel-Karaf:
- Camel-karaf main branch has been updated and now works with Camel 4.8.0 and
  Karaf 4.4.6+. Many new contributors are helping on this. The release 4.8.1
  has been done and is based on 4.8.x LTS release train.

Overall:
- The Camel project and all the subprojects are in a really good shape and all
  of them are growing in terms of community involvement and contributions.


## Community Health:
- At the time of writing the integration showing stats for Github wasn't
  working so I couldn't add those information.
- dev@camel.apache.org had a 39% increase in traffic in the past quarter (334
  emails compared to 240): Related to release planning and more heads up
- issues@camel.apache.org had a 11% decrease in traffic in the past quarter
  (2134 emails compared to 2375): Most of the projects are now using Github as
   first way of opening issues, to the decrease is somewhat expected.
- users@camel.apache.org had a 11% decrease in traffic in the past quarter
  (132 emails compared to 147): Users are starting to move and ask questions
   on Zulip, like the discussion for development, still some discussion is
   happening at mailing list level


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

# Apache Cayenne Board Report, December 2024

## Description

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

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

## Project Status

### Project State

Ongoing

### Issues for Board

None

## Membership Data

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

Community changes, past quarter:

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

## Project Activity

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

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

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

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

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

### Releases

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

## Community Health

Cayenne is healthy despite user and developer mailing list traffic being
down. The main activity concerned questions with the 4.2 release, which were
answered/resolved in a timely manner.

PRs and issues are also down for this quarter, although one of the PRs
was larger than normal and resulted in hundreds of files being changed.

A regressive bug was also found which impacts 4.2 and 4.1. A future
maintenance release will address the issue.


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

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

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

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

Community changes, past quarter:
- Alexandre Mattioli was added to the PMC on 2024-12-02
- Suresh Anaparti was added to the PMC on 2024-09-17
- No new committers. Last addition was Kiran Chavala on 2024-04-09.

## Project Activity:

Software development/management activity:

- The current version of Apache CloudStack is 4.20.0.0;

- The versions released in the past quarter are:
  - 4.20.0.0 was released on 2024-12-02.
  - 4.18.2.5 was released on 2024-11-12.
  - 4.19.1.3 was released on 2024-11-12.
  - 4.18.2.4 was released on 2024-10-16.
  - 4.19.1.2 was released on 2024-10-16.

- We released 4 security patches (4.18.2.4, 4.18.2.5, 4.19.1.2 and 4.19.1.3) to 
  solve 5 vulnerabilities. 

- The community is planning to release Apache CloudStack 4.19.2.0 by the end
  of January 2025.

- The latest CloudStack Terraform provider version (v0.5.0) was released on
  April 9, 2024. We started the discussion about a new version (v0.6.0).

Meetups and Conferences:
- We attended the Community Over Code NA 2024, and presented 6 talks related to
  CloudStack.

- We organized and attended the CloudStack European User Group: 
  https://cloudstack.apache.org/blog/cseug-2024/

- We organized and attended the CloudStack Collaboration Conference 2024: 
  https://www.cloudstackcollab.org/.

- We start planning the CloudStack Collaboration Conference 2025. 


## Community Health:

- There are new PMC members, added since the previous report. However, we have
  not discussed new committers in the past quarter.

- According to the reporter tool, the Community Health Score (Chi) is 7.96
  (Healthy). The number decreased from the past quarters due to decrease on new
  committers invited.

- Regarding the potential trademark issues mentioned in the past report, we took
  the recommendation of the VP, brand management, and took no action so far;
  however, we are monitoring the company and their media.

- We discussed and approved the use of the CloudStack trademark on an appliance,
  guaranteing that it follows the trademarks rules.

- We created an account on the BlueSky platform.

- We already started developing new features for a new version.

- We are working on updating our security response procedures and discussing our
  regular versioning procedures.

- Mailing lists statistics:
  - dev@cloudstack.apache.org had a 14% increase in traffic in the past quarter 
    (505 emails compared to 441).
  - issues@cloudstack.apache.org had a 152% increase in traffic in the past 
    quarter (91 emails compared to 36).
  - marketing@cloudstack.apache.org had a 31% decrease in traffic in the past 
    quarter (23 emails compared to 33).
  - users@cloudstack.apache.org had a 8% increase in traffic in the past quarter
    (1226 emails compared to 1125)
  - Changes (PRs) on the cloudstack-www are reflected on the 'issues' 
    mailing-list, therefore, explaining the increase in the traffic.
  - The fluctuation in the number of emails on the other mailing-lists is within
    the expected. 

- GitHub statistics:
  - 283 commits in the past quarter (-50% decrease)
  - 34 code contributors in the past quarter (-27% change)
  - 217 PRs opened on GitHub, past quarter (-15% change)
  - 176 PRs closed on GitHub, past quarter (-43% change)
  - 172 issues opened on GitHub, past quarter (-3% change)
  - 113 issues closed on GitHub, past quarter (-20% change)
  - We were on code freeze for the new version almost the whole past quarter,
    therefore, explaining the decrease in the number of new interations.


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

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

## Project Status:
Current project status: Apache Commons is an ongoing project with moderate
activity. Issues for the board: None.

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

Community changes, past quarter:
- Piotr Karwasz was added to the PMC on 2024-10-23
- No new committers. Last addition was Piotr Karwasz on 2024-08-27.

## Project Activity:
Apache Commons continues to release components regularly. In this reporting
period, we've released the following components:

- DBCP-2.13.0 was released on 2024-12-02.
- IO-2.18.0 was released on 2024-11-19.
- RELEASE-PLUGIN-1.8.3 was released on 2024-11-09.
- PARENT-78 was released on 2024-10-22.
- PARENT-77 was released on 2024-10-09.
- PARENT-76 was released on 2024-09-28.
- CSV-1.12.0 was released on 2024-09-25.
- IO-2.17.0 was released on 2024-09-18.
- PARENT-75 was released on 2024-09-18.

Further releases are planned. In general, we are still a Java 8 based project
but continue to monitor the rate of adoption of Java versions to determine
when we should update the platform requirement of each components.

## Community Health:
The statics show that we have overall decreased activity but we have an
increase in contributors. We welcomed Piotr Karwasz to the PMC this reporting
period. We monitor Jira tickets and GitHub pull requests (PRs). We discuss PRs
usually on GitHub and sometimes more generally on the dev mailing list when
reaching a wider audience is needed in case not all members monitor GitHub
PRs. We use Jira, not GitHub Issues.


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

## Status report for the Apache Cordova project - December 2024

## Description

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

## Project Status

**Current project status:**

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

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

**Issues for the board:**

There are no issues requiring board attention at this time.

## Membership Data

There are currently 99 committers and 96 PMC members in this project.

The Committer-to-PMC ratio is roughly 1:1.

**Community changes, past quarter:**

- No new PMC members. Last addition was Pieter Van Poyer on 2021-04-06.
- No new committers. Last addition was Pieter Van Poyer on 2021-04-06.

## Project Activity

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

**Releases:**

- cordova-plugin-file@8.1.3 was released on 2024-11-20.
- cordova-lib@12.0.2 was released on 2024-11-02.
- cordova-plugin-camera@8.0.0 was released on 2024-11-02.
- cordova-plugin-file@8.1.2 was released on 2024-10-30.
- cordova-plugin-file@8.1.1 was released on 2024-10-24.
- cordova-ios@8.0.0-beta.1 was released on 2024-10-21.

## Community Health

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

We continue to see contributions from a small group of dedicated
individuals. Things remain stable and the project continues to see good
traffic.

Several patches and major updates across our platforms, plugins, and
tooling have been released.

Some contributors focused on updating our file and camera plugins. The file
plugin received a few patch releases to improve the handling of specific
file paths in certain configured environments and to unify behavior between
iOS and Android.

Additionally, we prepared a major release for the camera plugin to comply
with Android's new permission requirements.

For our platforms, we published a beta release of cordova-ios to modernize
the codebase, add new features, and resolve localization issues through an
improved project structure. The goal of this beta release was to engage
with the community in testing these upcoming major and potentially breaking
changes. This engagement would also include plugin developers to ensure
they are able to prepare for the next release.

Feedback provided by the community and plugin developers was used to
address any reported issues, further development, and improvements to our
documentation to explain new behaviors or the rationale behind specific
changes.

Github discussions have become how our community supports each other. Our
discussion area is live at https://github.com/apache/cordova/discussions
and activity is forwarded to the 'issues' list.

## Mailing List Activity

- dev@cordova.apache.org had a 161% increase in traffic in the past quarter
(81 emails compared to 31)
- issues@cordova.apache.org had a 21% increase in traffic in the past
quarter (988 emails compared to 810)


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

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

## Project Status:
Current project status: Ongoing with moderate/low activity.

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

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

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

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

## Community Health:
dev@ctakes.apache.org had a decrease in traffic in the past quarter
(18 emails compared to 55): This is fairly avg for the project as there was
an increase in the last few quarters mainly related to the 5.x release.


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

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

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

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

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

## Project Activity:
We are cutting releases and this is a good sign. As usual we don't have much
traffic but  we have users reporting bugs and contributing fixes, and this is
the best sign that shows the project is widely used and there interest in the
community to keep it going.

Recent releases:
5.7.1 was released on 2024-10-13.
5.7.0 was released on 2024-06-15.
5.6.0 was released on 2024-01-08.

## Community Health:
As usual we don't have many PRs, but there are some and we are recently
seeing new contributors (from some big companies).
We hope to have newcommmitters.
Unfortunately it happens quite often that a new contributor 
contributes a couple of patches than they are happy 
and do not need to contribute much more.

It happens pretty often that people report issues 
directly to JIRA or send PRs, without passing from the mailing list.


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


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

## Project Status:
Current project status:

- Daffodil 3.9.0 was released on Sept 30, 2024 
- The Daffodil VSCode Extension 1.4.0 was released on Nov 13, 2024
- Our Daffodil SBT Plugin 1.2.0 was released on Nov 15, 2024.

Issues for the board: none

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

Community changes, past quarter:
- One PMC member stepped down from our PMC. Our greatest thanks to Dave Fisher
  for his mentoring and help from the earliest days of this project.

## Project Activity:

Work on the main Daffodil library has focused on reducing the bug count 
focusing on features that are in demand. 

## Community Health:

The project is healthy based on the pace of releases, 
mailing list and commit activity for both the
main library, VSCode extension sub-project, and our sbt plugin project.


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

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

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

## Membership Data:
Apache DataFusion was founded 2024-04-16 (8 months ago)
There are currently 42 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:1.

Community changes, past quarter:
- No new PMC members. Last addition was Jay Zhan on 2024-08-11.
- Piotr Findeisen was added as committer on 2024-12-03
- Jax Liu was added as committer on 2024-10-18
- Ifeanyi Ubah was added as committer on 2024-11-04
- Ruiqiu Cao was added as committer on 2024-12-10
- Michael Ward was added as committer on 2024-09-13

## Project Activity:
### Overall

We have completed adopting [sqlparser crate] into the project and made our
first release as part of the Apache Software Foundation.

[sqlparser crate]: https://github.com/apache/datafusion-sqlparser-rs

### DataFusion core

https://github.com/apache/datafusion

We continue the monthly release cadence versions. The [42.0.0 release] and
[43.0.0 release] had 73 and 96 unique contributors. We continue to [discuss
 the roadmap] in the open, and gathered a collection of [DataFusion
 related articles] onto our page.

We recently finished [significant performance improvements] as well as long
standing projects to migrate documentation to code and use the same API for
all user defined window functions. We also added FFI bindings to make it
easier to use multiple versions of DataFusion.

As more people build systems using DataFusion we are beginning to focus more
on keeping the core more stable, as it is [sometimes painful] to update to new
DataFusion versions.

[42.0.0 release]: https://github.com/apache/datafusion/
 blob/main/dev/changelog/42.0.0.md
[43.0.0 release]: https://github.com/apache/datafusion/
 blob/main/dev/changelog/42.0.0.md
[roadmap ticket]: https://github.com/apache/datafusion/issues/11442
[discuss the roadmap]: https://github.com/apache/datafusion/issues/13274
[DataFusion related articles]: https://datafusion.apache.org/
 user-guide/concepts-readings-events.html
[significant performance improvements]: https://datafusion.apache.org/blog/
 2024/11/18/datafusion-fastest-single-node-parquet-clickbench/
[sometimes painful]: https://github.com/apache/datafusion/issues/13525

### Sub project: DataFusion Python

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

We continue the monthly release cadence versions. The [datafusion-python
41.0.0] release and [datafusion-python 42.0.0] had 5 and 6 unique
contributors. Release for version 43.0.0 is underway at the time of this
writing.

We recently added support for [user defined window functions], including
significant updates to the user documentation on how to author user defined
functions. Additionally we released a [blog post on UDFs] demonstrating how
users can incorporate custom UDFs that can lead to 10x speed improvements by
writing Rust backed Python functions.

We added support for foreign table providers via the FFI bindings in the core
project. This enables external parties to provide Python interfaced table
providers that support features such as push down filtering, including across
different versions of DataFusion.

[datafusion-python 41.0.0]: https://github.com/apache/datafusion-python
/pull/866
[datafusion-python 42.0.0]: https://github.com/apache/datafusion-python
/pull/901
[blog post on UDFs]: https://datafusion.apache.org/blog
/2024/11/19/datafusion-python-udf-comparisons/


### Sub project: DataFusion Comet

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

The Comet project recently released version 0.4.0 with a focus on performance
& stability. See [Blog post] 

[Blog post]: https://datafusion.apache.org/blog/
2024/11/20/datafusion-comet-0.4.0/

Much of the current development focus is on improving complex type support,
particularly the ability to read complex types from Parquet and Iceberg
sources.

### Sub project: DataFusion Ballista

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

Since the last board report, the Ballista subproject has become much more
active and added new active maintainers.

The focus has changed from "Apache DataFusion Ballista Distributed Query
Engine" to "Making Apache DataFusion Applications Distributed"

The community has simplified the project by removing unfinished features and
refocusing as a way to scale out existing DataFusion applications by providing
a tighter integration with the core DataFusion project.

See more [details here]

[details here]: https://github.com/apache/datafusion/
issues/10157#issuecomment-2514694231

### Sub project: Sqlparser

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

The sqlparser project became part of the DataFusion project this quarter.

In addition to ongoing additions to SQL dialect support, we made our first
release as part of the Apache DataFusion project, and have started introducing
spans (source locations), a long requested feature.


## Community Health:
It is still hard to keep track of everything going on, which is a good thing.
While it is always a struggle to get enough code review capacity, we have many
active committers, and the community in general helps each other out with
reviews. We continue to actively grow our committer and PMC ranks.

We have upcoming in person meetups scheduled for Chicago, Boston, and
Amsterdam.


-----------------------------------------
Attachment S: Report from the Apache Directory Project  [Shawn McKinney]

## Description:

The Apache Directory TLP consists of the following sub-projects:

- ApacheDS: An extensible and embeddable directory server entirely written in
  Java, which has been certified LDAPv3 compatible by the Open Group.

- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
  replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
  This is a "schema aware” API with some convenient ways to access all types
  of LDAP servers.

- Studio: A complete directory tooling platform intended to be used with any
  LDAP server however it is particularly designed for use with ApacheDS. It is
  an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.

- Fortress: A standards-based authorization platform that provides role-based
  access control, delegated administration and password policy services with
  an LDAP backend.

- Kerby: An implementation of Kerberos v5 protocol and contains various tools
  to access and manage kerberos principals and keytabs. It provides a rich,
  intuitive and interoperable implementation, library, KDC and various
  facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
  environments such as cloud, Hadoop and mobile.

- Mavibot:  An embeddable key-value database library with MVCC (Multi Version
  Concurrency Control) support.

- SCIMple:  An implementation of SCIM v2.0 specification.

## Project Status:

Note: This report was also submitted last month. Nevertheless, we received a
reminder from it's it's (again) and so here it is again.

Membership continuing to decrease with 3 being moved to emeritus over the past
quarter, although two had not been active in the project for many years.
Despite the drop the core members continue the work to keep the project
running quietly and smoothly.

## Issues:

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

## Membership Data:

Apache Directory was founded 2005-02-22 (17 years ago) There are currently 58
committers and 19 PMC members in this project. The Committer-to-PMC ratio is
roughly 8:3.

Community changes, past quarter:
- Brian Demers was added to the PMC on 2023-10-23
- No new committers. Last addition was Fredrik Roubert on 2023-07-10.

## Project Activity:

Per sub-project:

- ApacheDS: low activity. Release in the works.
- LDAP API: released in last quarter. Release in the works.
- Studio:   low activity. No active maintainer. There's discussion on this and
  that a PMC member can step into the maintainer role in the future.
- Fortress: low activity.
- Kerby:    released in last quarter.
- Mavibot:  low activity. Release in the works.
- SCIMple:  low activity. Work being done to get Scimple tests going with LDAP
  backend.

## Community Health:

As stated earlier, the project activity is low with most of it realized via
pull requests and to a lesser extent Jira tickets. Nonetheless, the PMC
remains responsive on all project and security issues.

## Releases:
Apache Kerby 2.1.0 was released on 2024-08-14.
Apache LDAP API 2.1.7 was released on 2024-08-06.


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


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

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

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

## Membership Data:
Apache ECharts was founded 2020-12-16 (4 years ago)
There are currently 29 committers and 14 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 He Hao on 2022-07-06.
- No new committers. Last addition was Linghao Su on 2023-08-01.

We are voting for a new PMC member now.

## Project Activity:

We are testing and preparing for the next release 5.6.0, which is expected to
be voted before the end of this week.

We are also developing for the next major release 6.0.0, which is expected to
be completed around the end of February next year. This major release includes
a lot of exciting new features and we've completed about 70% of the features.

## Community Health:

Since we are mainly working for the next major release 6.0.0 and commits are
pushed to a separate branch instead of the main branch, the commit rate may
seem to have dropped but we believe the overall contribution is in a healthy
state.

We see some new contributors in the community and we try to encourage them to
contribute continuously and become one of our committers.


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

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

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

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

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

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

### Releases
- maven-bundle-plugin 6.0.0 was released on 2024-11-28.
- org.apache.felix.http.jetty-4.2.28 was released on 2024-11-17.
- org.apache.felix.http.jetty12-1.0.18 was released on 2024-11-17.
- org.apache.felix.http.wrapper-1.1.8 was released on 2024-11-17.
- org.apache.felix.webconsole-5.0.8 was released on 2024-09-19.
- org.apache.felix.http.jetty-5.1.26 was released on 2024-09-13.
- org.apache.felix.http.jetty12-1.0.16 was released on 2024-09-13.

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


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

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

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

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

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

## Project Activity:
No activity in the last quarter.
    Apache Flex BlazeDS 4.8.0 was released on 2023-04-17.
    flex-maven-tools/flex-sdk-converter 1.1.0 was released on 2023-02-20.
    Install Apache Flex 3.3.2 was released on 2018-07-09.

## Community Health:
There has been no activity in the last quarter. There's nothing significant
to report here.


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

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

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

## Membership Data:
Apache Flink was founded 2014-12-17 (10 years ago)
There are currently 117 committers and 52 PMC members in this project.
The Committer-to-PMC ratio is 9:4.

Community changes, past quarter: (last report: June 14th)
- No new PMC members. Last addition was Rui Fan on 2024-06-04.
- Junrui Lee was added as committer on 2024-11-12
- Xuannan Su was added as a committer on 2024-08-17
- Ferenc Caky was added as a committer on 2024-08-09
- Hang Ruan was added as a committer on 2024-06-13

## Project Activity:

Releases:
- cdc-3.2.1 was released on 2024-11-27.
- connector-kafka-3.4.0 was released on 2024-11-25.
- connector-aws-5.0.0 was released on 2024-11-11 with new AWS Kinesis Data
  Stream and DynamoDB Stream Sources
- connector-prometheus-1.0.0 was released on 2024-11-08.
- flink-kubernetes-operator 1.10 was released on 2024-10-25 with support new
  APIs for managing snapshots (checkpoints and savepoints) from the operator,
  and other autoscaler improvements.
- Flink 2.0-preview1 was released on 2024-10-23. The preview release is for
  previewing breaking changes, not for production use. In 2.0 we will remove
  old APIs and make other breaking changes, besides the addition of some
  exciting new features, which will be properly announced with the final 2.0
  release.
- connector-kafka-3.3.0 was released on 2024-10-17.
- cdc-3.2.0 was released on 2024-09-05.
- Flink 1.20 was released on 2024-08-02. 1.20 deprecates more APIs prior to the
  upcoming 2.0 release. Otherwise, various SQL syntax enhancements, performance
  improvements and more

Conferences:
- Flink Forward, hosted by Ververica and Alibaba Cloud is hosting conferences
  in Berlin, Germany (October), Shanghai, China (November), Jakarta, Indonesia
  (December). The conferences seem well-attended.
- Current 2024, hosted in Austin, TX in September featured a lot of Flink
  content.


## Community Health:
- Some community members have launched a "Community Health Initiative (CHI)".
  The problem the workgroup wants to address is a high number of unmerged PRs,
  improve the experience for new contributors and to merge / address
  critical issues in a timely manner. The work group wants to remove the need
  for the workgroup and go back to business-as-usual as soon as possible.
  Currently, the group meets weekly, alternating between eastern and western
  friendly timezones. All decisions will go through the dev list.
  The PMC supports this initiative, as the number of committers active in
  reviewing PRs is perceived to be lower than in the past.
- dev@ activity has gone down by 23%, while issues@ seems stable. For the other
  lists, data from the metrics seem to be incomplete. In the last report, we
  had an increase of 22% on the dev@ list. Maybe the provided metrics need to
  cover longer time-spans.


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

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

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

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

Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was Kip Kohn on 2024-07-09.

## Project Activity:
- Enhanced GoT observability with WorkUnitsSizeSummary and WorkUnitSizeInfo
- Simplify config by setting default authenticator in Yarn Temporal containers
- GoT YarnService integrated with DynamicScaling
- Prevent issues by avoiding Adhoc flow spec addition for non leasable entity
- Support for sending proxy jvm args to Yarn AM and Containers
- Streamlined log messages for easier debugging of GaaS multi-active DAG
  processing
- Fix NPE while overwrite if table has no previous snapshot
- Support to allow filtering of Hive datasets by underlying HDFS folder
  location
- Defined Gobblin-on-Temporal dynamic ScalingDirectives with parser and
  FsScalingDirectiveSource
- Added Azkaban fields in RMAppSummaryEvent for GoT jobs
- Support added for partial commit semantic from CopyDataPublisher
- Added default value for OpenTelemetry attribute
- Added Iceberg TableMetadata Validator
- Config support to set logExporter classname
- Optimization to only load added jars in the cache
- Support for configuring openTelemetry metric exporter as logExporter
- Added support for partition level copy in Iceberg distcp
- Support to copy table properties in iceberg distcp
- Fix bug where empty delete activity result was not deserialized

* Last Release date: 30th August, 2023

## Community Health:
- There have been 32 commits since September 2024.
- 15 commits have been from non-committers.
- Kip Kohn was voted in June, 2024 as a committer. We constantly
 look for consistent contributors to vote them in as Committers.


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

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

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

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

Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- No new committers. Last addition was Alexander Leitner on 2023-11-13.

## Project Activity:
The project is progressing the 1.6.0 release, but is taking significantly
longer than originally expected. In addition to outstanding documentation,
regressions have been found that will need to be resolved prior to release.

The project is also pleased at the successful registration of the "Guacamole"
trademark.

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

## Community Health:
The community continues to be active and healthy. There is a typical level of
engagement on the user@ list, and a recent uptick in companies wishing to be
listed as commercial support providers.


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

# Description

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

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

# Project Status

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

Issues: There are no issues requiring board attention.

# Membership Data

Apache Gump was founded 2004-02-18. There are currently 16 committers
and 10 PMC members in this project.
The Committer-to-PMC ratio is 8:5.

Community changes, past quarter:

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

# Project Activity

Mark set up a new instance running on a more recent version of Ubuntu
and we are using that for our regular builds now.

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

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

## Releases

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

# Community Health

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

Apart from foundation wide announcements or infrastructure team
messages nobody has posted any message to the Gump mailing list or
asked for a change who is not a member of the Gump PMC already for the
last five years.

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

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

## Project Status:
Current project status: Ongoing, Moderate
Issues for the board: No major issue.

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

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

## Project Activity:
- 1.4.2 was released on 2024-11-28
- 1.4.1 was released on 2024-09-23
- 1.4.0 was released on 2024-06-21
- 1.3.1 was released on 2023-09-28

## Community Health:
- Two more releases for Helix:
1) 1.4.1 for minor fixes.
2) 1.4.2 contains the new metadata clients with advanced features.

- Helix 2.0: Helix 2.0 stage 1 features development done. The testing
is in progress. When it is ready, it will merge into main branch and
release. Target for Jan 2025.

- Stage 2 discussion will be started. Proposing to have a library based
more light weighted shard management sharing same placement algorithms
and better performance. Leave more flexibility to users.


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

## Description:
The mission of Hive is the creation and maintenance of software related to Data 
warehouse infrastructure using the Apache Hadoop Database

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

## Membership Data:
Apache Hive was founded 2010-09-22 (14 years ago)
There are currently 111 committers and 56 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Zhihua Deng was added to the PMC on 2024-10-12
- Dmitriy Fingerman was added as committer on 2024-11-12
- Shohei Okumiya was added as committer on 2024-11-12

## Project Activity:
4.0.1 was released on 2024-10-02.
2.3.10 was released on 2024-05-09.
4.0.0 was released on 2024-03-29.

Discussions around having 4.1.0 release have started, the community is
discussing on the scope & timeline of the release.

## Community Health:

The community remains vibrant and engaged, with meaningful contributions and
active discussions on the mailing list. The recent Hive 4.x release has
generated interest, evidenced by several inquiries—an encouraging sign of its
growing adoption. Notably, projects like Apache Ranger, BigTop, and
ShardingSphere have already transitioned to using this latest release in their
codebases.

The community continues to support projects and individuals in adopting Hive
4.x, providing guidance and assistance when needed. So far, no significant
issues have been reported with the release.

Looking ahead, the community is focused on key initiatives, including adding
JDK-17 support for the next release, along with ongoing improvements and bug
fixes.

Additionally, we even announced: CVE-2022-41137.


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

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

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

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

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

## Project Activity:
Exciting times for the project. The community worked on two major releases.
Second version of hudi-rs 0.2.0 is now out, that expands the project into
broader rust/python community. hudi-rs has already been integrated into
popular query engines in the ecosystem like Ray and Daft, and the community is
planning a roadmap to bring hudi-rs on par with the core java feature set.

Hudi 1.0 GA release has been successfully voted upon and ratified by the
community. And will be announced next week with due process. 1.0 is the
largest release to date, with multiple beta versions spanning a year, which
has resulted in a large reimagination for the next few years. Notable
innovations the project is bringing to the community and space at large is :
secondary and different types of indexes, new streaming friendly concurrency
control and deep storage format optimizations to reduce write/read latency,
and much more.. Many of these are industry first features. So, we are proud of
the 62 or so contributors on this release (compared against 0.15.0)

Several leading companies including Amazon, Peloton have presented their usage
of Hudi to build data lakes in community syncs.

## Community Health:
We're seeing steady growth in community in terms of engagement on GitHub
(https://ossinsight.io/analyze/apache/hudi). dev list and users lists are
primarily used by community for low bandwidth communication. Github issues
continue to be main engagement model for community support for issues with the
project.


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

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

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

## Membership Data:
Apache Iceberg was founded 2020-05-19 (5 years ago)
There are currently 32 committers and 21 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 Amogh Jahagirdar on 2024-08-12.
- Matthew Topol was added as committer on 2024-12-09
- Scott Donnelly was added as committer on 2024-12-10

## Project Activity:

Releases
- 1.7.1 was released on 2024-12-06.
- 1.7.0 was released on 2024-11-08.
- PyIceberg 0.8.1 was released on 2024-12-06.
- PyIceberg 0.8.0 was released on 2024-11-18.
- Go 0.1.0 was released on 2024-11-18.

Table format (v3)
- Added deletion vectors and synchronous maintenance to improve row-level ops
- Added row lineage fields and requirements for fine-grained row tracking
- Proposal for geography and geometry types is close to consensus
- Update to add Parquet's variant type is approved, waiting on Parquet upstream
- Finalized new type promotion rules

Puffin format
- Added deletion vector blob type to support DVs in tables

REST catalog spec
- Added storage credentials passing
- Added credential refresh
- Created a docker image for catalog testing
- Discussing proposal for partial metadata commits
- Discussed partial metadata loading

Views
- Discussions about materialized view metadata are ongoing

Java
- Released new Kafka Connect sink
- Added default values implementation for Avro
- Added nanosecond timestamps
- Added v3 DV support in core, ongoing work in Spark
- Flink: Made FLIP-27 source the default
- Spark: Removed Spark 3.3 support
- Hive: Removing Hive 2.x and 3.x (Iceberg support is in Hive for 4.x and on)
- Pig: Removed the iceberg-pig module that is no longer used

PyIceberg
- Support: Added Python 3.12, dropped Python 3.8

Rust
- Support for default values and type promotion in reads
- Added TableMetadataBuilder
- Implemented table requirements

Go
- Produced the first go release!
- Supports scan planning and reading (data and metadata)
- Supports loading and listing tables with the Glue catalog
- Supports local and S3 storage

C++
- Added a C++ repository for a Puffin implementation

## Community Health:

The PMC has published guidelines for contributors that want to know more about
how they can become committers on the Iceberg site. This guide should help
contributors understand how Iceberg and other ASF communities decide and add
committers, and should set expectations clearly. This was the most important
follow up from discussions on the dev list earlier this year, where it became
clear that contributors did not understand the requirements or process.

The community has started planning a second Iceberg Summit, intended to be held
in Spring of 2025. The proposal details are being finalized (such as the members
of the selection committee) and will be submitted for approval in the next few
weeks.

The community added two new committers this quarter and had a slight increase in
the number of contributors.

There were also a number of commercial announcements from companies adding or
expanding support for Iceberg.


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


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

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

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

## Membership Data:
Apache IoTDB was founded 2020-09-16 (4 years ago)
There are currently 67 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- No new PMC members. Last addition was Qingxin Feng on 2024-06-29.
- Chuqing Qin was added as committer on 2024-11-30
- Xuan Wang was added as committer on 2024-11-19
- Pengcheng Zheng was added as committer on 2024-11-19

## Project Activity:
Recent releases:
IOTDB-1.3.3 was released on 2024-11-20.
IOTDB-1.3.2 was released on 2024-07-01.
IOTDB-1.3.1 was released on 2024-04-22.

Refine the memory control for queries to ensure that scenarios involving
massive sequences and queries with high overlap of seq and unseq files no
longer result in Out-Of-Memory (OOM) errors.

Optimizing the Memtable data structure to reduce lock contention between read
and write operations, thereby mitigating the mutual impact during
high-concurrency read and write operations.

Introduce a Blob Allocator module to pool large Binaries, reducing the
pressure on JVM GC and memory copying in scenarios with large Binary data, and
significantly improving write throughput in such scenarios.

Further enhance the stability of cluster scaling functions, making the IoTDB
cluster more resilient.

## Community Health:
Overall community health is good. 
Contributors are mainly working on a new timeseries table model, 
including writing, deleting, raw data querying, aggregate querying, 
downsampling querying, non-correlated subqueries, multi-table Join, etc., 
and the types of queries supported are richer than those of the tree model.


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

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

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

## Project Status:
The project is ongoing with moderate activity.

There are no issues requiring board attention at this time.

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

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

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

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

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

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

Work on migrating Jackrabbit Oak from Azure SDK 8.x to 12.x has been
picked up again and is ongoing. Azure SDK 8.x is no longer supported
and a migration to 12.x is now required.


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

In November, a vote was started to add a new committer and PMC member
to the project. The vote was canceled due to lack of votes. Concerns
raised on the private mailing list mentioned that the candidate has
not been active in the project long enough.

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

## Releases:
- jackrabbit-oak-1.22.21 was released on 2024-09-12
- jackrabbit-filevault-3.8.2 was released on 2024-09-25
- filevault-package-maven-plugin-1.4.0 was released on 2024-10-01
- jackrabbit-oak-1.70.0 was released on 2024-10-01
- jackrabbit-2.23.1-beta was released on 2024-10-12
- jackrabbit-oak-1.72.0 was released on 2024-11-14

## JIRA activity:
- 226 JIRA tickets created in the last 3 months
- 190 JIRA tickets closed/resolved in the last 3 months


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

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

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

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

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

## Project Activity:
Apache Karaf 4.4.7 release has been delayed in order to give time to
investigate refactoring options to fix KARAF-7174. In order to avoid
postponing 4.4.7 any longer, the release will be submitted to vote soon and
KARAF-7174 will be fixed in 4.4.8.

On the Karaf 4.5.0 front, we have a clear roadmap. This release series will:

* a new simplified/flat features service (the default feature service in the
  Karaf distribution will be still the current one)
* starting to provide Karaf "internal" services from some features as an
  alternative to some Pax * components (the default in the Karaf distribution
  will be still the Pax * components) This is also preparation steps for Karaf
  4.6.0 where the above features will be the default.

In parallel, we are preparing a new Karaf Decanter release that will include a
bunch of fixes and improvements (we are reviewing several PRs right now).

## Community Health:
The karaf-integration distribution is still planned for Karaf 4.5.0 (see
KARAF-7792 - Provide karaf-integration distribution Open ), possible
backported to 4.4.x series as optional feature/distribution.

This will need new camel-karaf release fixing issues we identified in the
camel-karaf project (like shutdown hook, etc).


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

## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed on-disk NoSQL database, including the compatibility
to Redis, and support of a rich range of Redis data structures and commands.

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

## Membership Data:
Apache Kvrocks was founded 2023-06-21 (a year ago)
There are currently 26 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Xuwei Fu on 2024-03-22.
- SiLe Zhou was added as committer on 2024-10-19

## Project Activity:
In the past quarter, the PMC has released Apache Kvrocks version 2.10.0 on Oct
6th, and version 2.10.1 on Oct 24th.

Recently, Kvrocks has added support for the Hyperloglog data structure in the
new version (2.10.0) and is now compatible with most of the Redis stream group
related commands. In addition, Kvrocks is working on strengthening transaction
and atomicity support to improve transaction guarantees for features such as
scripting and secondary indexing.

Kvrocks Search (including secondary indexing and vector search) functionality
has been further improved, which is expected to be released in the next
version. Additionally, Kvrocks Controller now has preliminary Web UI and Raft
support, with more updates planned for the next version.

## Community Health:

The issues have decreased (-25%) but the PRs have increased (+2%) in the past
quarter. I believe the community is steady and healthy.

Although the community's activity has not increased significantly, I can still
see some active newcomers in the community. In addition, Kvrocks Search and
major updates to Kvrocks Controller should enhance the attractiveness of
Kvrocks for people who are looking for Redis alternatives.


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

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

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

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

Community changes, past quarter:
- No new PMC members. Last addition was Binjie Yang on 2024-07-05.
- No new committers. Last addition was Senmiao Liu on 2024-06-25.

## Project Activity:

Software development activity:

 - We released the feature release 1.10.0 on 2024 Oct 27
 - We released the bug fix release 1.8.3 on 2024 Nov 27.
 - We released the bug fix release 1.9.3 on 2024 Dec 2.
 - We markd 1.8.3 as the EOL version for branch-1.8.
 - We are working on support for the new coming Spark 4.0.
 - We are working on support for Oracle db access.
 

Meetups and Conferences:

 - One of our PMC will give an online tech talk on DatafunSummit on 2024 Dec 14

## Community Health:
Some new contributors are helping with new features like Oracle support,
the community is still friendly, and welcoming new members.


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


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

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

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

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

Community changes, past quarter:
- No new PMC. Last addition was Jie Cheng on 2024-01-28.
- No new committers. Last addition was Yuechao Yan on 2024-06-27.

## Project Activity:

Apache Linkis V1.7.0 version is Under testing and is expected to be released
in Oct. Mainly includes the following features:
- Spark, hive, and shell tasks support cross-cluster submission.
- Support task pre-diagnosis, including syntax errors, join keyword mismatches
- Concurrent engine supports graceful exit.
- Added Monitor service, supporting data cleanup, disk cleanup, user-mode alarms

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


-----------------------------------------
Attachment AN: Report from the Apache Logo Development Project  [Jeff Genender]

## Description:
The mission of Apache Logo Development is the development of a brand
and logo for the Foundation

## Project Status:

Current project status: board concern: mild

### Work Efforts

The PMC is in-process of preparing a ballot for presentation to the
Membership. The current discussion is whether to try to rush this
before the late-December holidays, or simply wait until the New
Year. Given that ballot language has not been decided upon, and will
likely require much discussion, it certainly appears the ballot will
appear in January. The PMC will likely run a test/empty ballot in
December to test the desired process.

The set of candidate logos to be presented to the Members for
consideration has been finalized.

### Health

Many words have been written about the Logo Development PMC, and its
on-list discussions, about its participants, and whether there are
factions. All of this is arguably true or false, but is materially
irrelevant as long as the PMC is able to make progress. Thus, this
report is not going to cover “health” concerns that others may have
raised.

### Composition

The PMC has recently seen the resignation of Dave Fisher (wave) who is
performing new Foundation duties as VP, Tooling.

The prior VP Logo Development, Jeff Genender, has resigned his
position as of Dec. 6th, 2024. The PMC is recommending Daniel Gruno
(humbedooh) as the new PMC Chair to replace Jeff Genender (jgenender),
and a Resolution has been placed on the Board's agenda.


-----------------------------------------
Attachment AO: Report from the Apache Lucene Project  [Chris Hegarty]

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

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

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

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

## Project Activity:

- 8.11.4 was released on 2024-09-24
  - Addresses several significant and critical bug fixes
  - Release notes: https://lucene.apache.org/core/8_11_4/changes/Changes.html
- 9.12.0 was released on 2024-09-28
  - This is the last scheduled minor release of the 9.x series
  - Security bug fix for Apache Lucene Replicator: CVE-2024-45772
  - Addresses several significant and critical bug fixes
  - Release notes: https://lucene.apache.org/core/9_12_0/changes/Changes.html
- Lucene 10 was released on 2024-10-14
  - It's been ~2.75 years since Lucene 9.0 (December 2021)
  - Requires a minimum of Java 21
  - Adds support for sparse indices
  - Improved I/O concurrency
  - Decouple within-query concurrency from the index's segment geometry
  - ... and so much more
  - Release notes: https://lucene.apache.org/core/10_0_0/changes/Changes.html
- PyLucene 9.12.0 was released on 2024-10-11
  - https://svn.apache.org/repos/asf/lucene/pylucene/tags/pylucene_9_12_0
- PyLucene 10.0.0 was releasesd on 2024-10-20
  - https://svn.apache.org/repos/asf/lucene/pylucene/tags/pylucene_10_0_0

## Community Health:

Community interactions remain very healthy, with good activity in all
areas (discussions, PRs, etc).
- The dev@ mailing list had a moderate amount of traffic. Much of the
  technical discussion happens in GitHub issues and PRs, rather than the
  mailing list. There were no particularly contentious topics, but
  rather a healthy amount of discussion on a breath of subjects.
- Development remains very active. In this quarter:
  - 508 commits across all branches
  - 43 PRs opened
  - 193 PRs closed
  - This is down a little from the previous quarter, but still very healthy.
- PR volume remains healthy, with open PRs trending in a steady state
  while closed PRs remain steady
  (https://benchmarks.mikemccandless.com/github_pr_counts.html).


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

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

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

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

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

## Project Activity:
Apache Lucene.Net delivered the latest 4.8.0-beta00017 release on 2024-10-29,
the first release in over two years. Activity has picked up notably in the
past quarter. We are going to need one more beta release (4.8.0-beta00018) to
finish introducing necessary breaking changes, before focusing on finishing up
a 4.8.0 final release. 4.8.0-beta00018 is 46% complete by issue count at the
time of this writing, not including necessary changes to our dependencies J2N
and ICU4N, some of which are significant. Our goal is to deliver this beta in
the first quarter of 2025. The longer-term goal, post-4.8, is to catch up to a
more recent version of Lucene, which should be much easier with our current
foundation.

Our project has also been working on supporting the latest .NET versions,
improving performance through benchmarks, improving the documentation and unit
tests, automating various processes including API comparison, and continuing
to investigate and resolve issues submitted by the community.

## Community Health:
Activity has increased significantly on the project since the last board
report. Commits have increased to about 10.5 commits per week at time of
writing since the last board report, up from about 3.5 per week for the same
time period before that. Community interaction via GitHub issues continues to
be an effective means of communication. Discussions on Slack remain focused on
what is remaining to finish the 4.8 release and we have been putting all
efforts towards this goal.

- builds@lucenenet.apache.org had a 394% increase in traffic in the past
  quarter (94 emails compared to 19)
- dev@lucenenet.apache.org had a 500% increase in traffic in the past quarter
  (522 emails compared to 87)
- 79 commits since last board update (up from 8 in quarter prior to last board
  report)
- 7 code contributors since last board update (same)
- Last release: 2024-10-29 (4.8.0-beta00017) - over 90k downloads on nuget.org
  already


-----------------------------------------
Attachment AQ: Report from the Apache Mnemonic Project  [Gordon King]


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

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

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

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

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

## Project Activity:
Apache Mynewt-1.13.0 and Apache NimBLE-1.8.0 were released on 2024-11-25.

Work is ongoing in several areas, mainly improvements in BSP and MCU support
(Nordic nRF54 fmaily) and tooling (newt and scripts).
On Bluetooth support side there is ongoing work for LE Audio support and
Channel Sounding (BT 6). There is also work on implementing missing optional
features from previous Bluetooth Core Specifications (5.4 and older).


## Community Health:
Core developers are active on regular basis. We see more
new users support request recently (after latest release).


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

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

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

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

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

## Project Activity:
Recent releases:
- Apache NetBeans 24 was released on 2024-12-10.
- Apache NetBeans 23 was released on 2024-09-19.
- Apache NetBeans 22 was released on 2024-05-29.

## Community Health:
- A lot of discussion and back and forth, positive and productive, driven by a
  core group, which would be nice to extend, but is an ongoing challenge.
- dev@netbeans.apache.org had a 50% increase in traffic in the past quarter
  (191 emails compared to 127)
- users@netbeans.apache.org had a 50% increase in traffic in the past quarter
  (138 emails compared to 92)


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

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

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

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

Community changes, past quarter:
- Sebastian Tschikin was added to the PMC on 2024-09-18
- Ioan Eugen Stan was added as committer on 2024-09-23

## Project Activity:
* New releases:
** 18.12.17 was released on 2024-11-15.
* Security: With this release, we have fixed and announced two new
  vulnerabilities: CVE-2024-47208 and CVE-2024-48962.
* After a successful vote, the branch release24.09 has been created to
  stabilize the features in preparation for a new family of releases, which
  will supersede 18.12.*
* Trademarks: there are no trademark related concerns at the moment.

## Community Health:
During the last quarter, community activity has remained steady, with regular
participation in mailing list discussions and consistent code changes. A new
committer has joined our group, contributing to development efforts, and a new
member has been welcomed into the Project Management Committee (PMC),
supporting the project’s management and oversight.


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

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

## Project Status:
Current project status: Dormant
Issues for the board: noe
Comment feedback: 
@cdutz: Yes, was no progress in the last months,
but we plan to continue with the yearly maintenance releases.

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

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

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

The V2 feature release (version 3.0.0) 
and the V4 a maintenance release
are planned for December/January.
Unfortunately, the V2 release got
delayed, but will be done now. 

## Community Health:
Overall community health is okayish.
Activity on the mailing lists continues on a low level.
There were only few contributions, and JIRA items/PRs.
Roadmap for feature release was discussed and decided, resulting 
in the plan mentioned in project activity (only timeline changed).


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

## Description:

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

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

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

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

Community changes, past quarter:
- Wenchuang Gan was invited as committer on 2024-12-10

## Project Activity:

OpenDAL has the following release since last report:

- v0.50.2: 2024-11-07
- v0.50.1: 2024-10-23
- v0.50.0: 2024-09-18
- v0.49.2: 2024-08-29
- v0.49.1: 2024-08-20

## Community Health:

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

No, OpenDAL is in super healthy at the moment. I'm proud of that.

### Is the PMC capable of responding to security issues and performing a
    release of its projects if needed?

Yes, as I have demonstrated in the Project Activity, we release at least one
version per month and can release more if necessary. The PMC is also prepared
to handle security issues, although we haven't encountered any yet (thanks to
our Rust core).

### Does the PMC need anything from the Foundation to improve on contributing
    to our mission of delivering software for the public good?

Yes.

The OpenDAL PMC has switched its primary communication channel from the
mailing list to GitHub Discussions. A forward from GitHub Discussions to the
mailing list has been set up to ensure all discussions are archived and
accessible to mailing list subscribers. This change has been highly
beneficial, as we've seen increased participation in discussions and more
contributors joining as a result.

The next area we aim to improve is the release process. We want to create a
fully automated release workflow where committers only need to tag on GitHub,
and everything else can be handled automatically without human interaction.

We want the board to assist us in cleaning up the possibility: Can we set up a
bot account for the OpenDAL PMC to establish a workflow that allows it to
write to SVN?


-----------------------------------------
Attachment AW: Report from the Apache OpenNLP Project  [Jeff Zemerick]

## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text

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

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

Community changes, past quarter:
- No new PMC members. Last addition was Martin Wiesner on 2023-06-24.
- No new committers. Last addition was Atita Arora on 2023-02-28.

## Project Activity:
The project has made two model releases in the past period along with
releasing OpenNLP 2.5.0 and preparing for a 2.5.1 release. The models are
available under the Apache license. These releases added additional languages
and trained on updated data. This is a great step for the project.

## Community Health:
The community is healthy. OpenNLP was the subject of a presentation at
Community over Code. There has been significant community and development
activity around releasing models which is reflected in the mailing list
traffic increase.


-----------------------------------------
Attachment AX: Report from the Apache OpenOffice Project  [Dave Fisher]

## Description:
The mission of OpenOffice is the creation and maintenance of software related
to an open-source, office-document productivity suite

## Project Status
The project has at low activity.

## Membership Data
Apache OpenOffice was founded 2012-10-16 (12 years ago)
There are currently 141 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:2.
No new PMC members. The last addition was Czesław Wolański on 2023-01-14.
No new committers. The last addition was Francis Campos on 2022-06-06.

## Project Activity
4.1.15 was released on 2023-12-22
4.1.14 was released on 2023-02-27 
4.1.13 was released on 2022-07-22
Binary downloads (total over all) as of December 1:  383,417,801

### Codebase in OpenOffice repository
Work continues on the 4.2 future release; This included:
- Work on upgrading OpenSSL to a current version. 
- dev@openoffice.apache.org had steady traffic in the past quarter. 
- issues@openoffice.apache.org had an increase in traffic in the past quarter. 
- l10n@openoffice.apache.org had traffic limited to onboarding a new volunteer
  for Vietnamese.

### Documentation
The OpenOffice-docs repository is where the small documentation team makes
updates.
- The Chapters for the Writer Guide are completed and ready to published, and
  the compilation of the complete book is completed.
- The Chapters of the Calc Guide are ready for final review.
- Work has started on the update of the Impress Guide from the old 3.3 Version.
- doc@openoffice.apache.org had steady traffic in the past quarter.
- The OpenOffice-org repository has had the usual download count updates.

### User Support
- User Forums (forum.openoffice.org) remain active in English, Spanish, French,
  Hungarian, Italian, Japanese, Dutch, and Polish.
- The forum and media wiki vm was migrated to a new Data Center.
- The forums had a problem with gmail.com that appears to be fixed.
- users@openoffice.apache.org had a decrease in traffic in the past quarter. 
- users-de@openoffice.apache.org had an increase in traffic in the past quarter
  around the release.

### Translation Interface
Currently, we are adding a CI/CD environment to integrate translations in AOO.
Pootle is no longer maintained. Alternatives have been considered and there
are 2 options in the short list. Once we have the CI/CD up and running, a
switch is possible due to usage of standardized file format.

### Conventions
The project was present at the German open-source convention Bits & Bäume Saar
in Saarbrücken. The volunteers were able to tell numerous people, especially
so-called “Bäume”, about free office suites in general and Apache OpenOffice
in particular.

### Infrastructure
The move to the new datacenter has been concluded. We had some issues after the
migration, but these seem to be resolved. We are discussing working with the
Infrastructure Team to improve VM maintenance and deployment.

## Community Health
Community overall health is improving. We are seeing several developers taking
on ODF 1.3, Boost, NSS, icu4 and OpenSSL updates. Documentation is being
updated after a long time and we are getting translation volunteers.

### Binary Distributions
SourceForge mirrors are still the main way to get an OpenOffice binary
release. Windows builds are also published in the Microsoft Store (Windows
10/11). Windows users are by far our largest user group. Windows 10 and 11
users can also install the binaries via WinGet. On both systems, we sign only
the installers and are ready to use the new service provided by SSL.com. A PMC
discussion has been started if we can sign the complete product of AOO. Maybe
we can set up a CI/CD tooling for this to simplify the Release Manager's work.

### Facebook
We have one volunteer taking care of the presence. Work is underway to invite
more volunteers.

### X, formerly Twitter
The PMC voted to continue our handle, and we have new volunteer PMC members
who will handle our presence. The main purpose will be advertising new
releases.
### Unmaintained Python 2 code
Python 2 is unmaintained. We have in the development tree the external python3
support. Internal python 3 support is difficult. We are checking alternatives.
Planned for the next major release.

### OpenDocument Format (ODF) Version 1.3
Our default and best supported file format, the OpenDocument Format, has
received a new Standard update. As we plan to support this format, we started
work checking the ODF 1.3 specification and what we have to do to support
documents in OpenDocument Format version 1.3 (see
https://cwiki.apache.org/confluence/display/OOOUSERS/ODF+1.3+Changes), as well
as some early development.


-----------------------------------------
Attachment AY: Report from the Apache OpenWebBeans Project  [Mark Struberg]


-----------------------------------------
Attachment AZ: Report from the Apache Paimon Project  [Jingsong Lee]

## Description:
The mission of Apache Paimon is the creation and maintenance of software
related to a unified lake storage to build dynamic tables for both stream and
batch processing with big data compute engines, supporting high-speed data
ingestion and real-time data query

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

## Membership Data:
Apache Paimon was founded 2024-03-20 (9 months ago)
There are currently 20 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Yann Byron (Bi Yan) on 2024-03-20.
- Yu Xu was added as committer on 2024-11-16

## Project Activity:

Software development activity:
- We released the release 0.9.0 on 2024-09-13.
- We prepared the release candidates for 1.0.0.
- We have supported view, format table, object table in catalog layer.
- We have supported Iceberg compatibility, producing Iceberg snapshots.
- We prepared the release candidates for paimon python sdk.

## Community Health:

Overall community health is good.
- dev mail list had a 47% decrease in traffic in the past quarter (76 vs 141).
- Community is mainly focusing on discussions around Issues and Pull Requests.
- Multiple new contributors are contributing code.


-----------------------------------------
Attachment BA: Report from the Apache Pekko Project  [PJ Fanning]

## Description:

The mission of Apache Pekko is the creation and maintenance of software related
to a toolkit and an ecosystem for building highly concurrent, distributed,
reactive and resilient applications for Java and Scala

## Project Status:

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. The number of active contributors is small but I believe that we
should be able to respond to security issues.
We have no CVEs but we did fix some security issues prior to our first
release in 2023.

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

No known issues in this area.

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

We are well supported by the Foundation.

## Membership Data:
Apache Pekko was founded 2024-03-20 (6 months ago)
There are currently 27 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was JingZhang Chen on 2024-05-29.
- Jiafu Tang was added as committer on 2024-06-17

## Project Activity
We have released 1.1.x versions of our core modules and hope to get 1.1.x
releases for the rest of the modules done in the next few months.

## Community Health
There are a small number of new contributors who we should approach to add as
committers. The active contributor base is fairly small and it would be good to
increase its size.


-----------------------------------------
Attachment BB: Report from the Apache Pig Project  [Koji Noguchi]


-----------------------------------------
Attachment BC: Report from the Apache Pivot Project  [Roger Lee Whitcomb]


-----------------------------------------
Attachment BD: Report from the Apache PLC4X Project  [César García]

## Description:
The mission of the Apache PLC4X project is creating a set of libraries for 
communicating with industrial programmable logic controllers (PLCs) using a 
variety of protocols but with a shared API.

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

## Membership Data:
Apache PLC4X was founded 2019-04-16 (6 years ago)
There are currently 21 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was César García on 2021-09-30.
- No new committers. Last addition was Jinlin Hong on 2022-11-02.

## Project Activity:
There have been significant improvements in the Modbus, S7 and OPC-UA
libraries, especially in relation to performance and the implementation of
specific features of each driver.

The native implementations (SPI) of the libraries in Python, Java and Go have
also been improved, as well as the associated documentation.

Part of the team continues to work on options for the development of tools
that allow the expedited use of the libraries through gateways and through the
use of graphical interfaces and thus expand the user base of “plc4x”, from
programmers to end users.

A positive balance is maintained in the opening and closing of Issues on
Github.

Based on these improvements and bug fixes, it is expected that the issue
(0.13.0) will be made shortly.

## Community Health:
Our community has seen a 58% increase in mailing list traffic. The traffic
generated is mainly related to the addition of new features, bug fixes and,
to a lesser extent, the addition of new features which are managed by project
members and specific contributions.

The community made significant improvements to the website, improving its
presentation and dynamic display.

Part of the community actively promotes the use and benefits of Plc4x on
professional networks, as well as the technical achievements of the libraries
developed and their integration into different architectures.

In the specific case of LinkedIn, a record of more than 500 followers was
achieved on the Plc4x channel on LinkedIn.


-----------------------------------------
Attachment BE: Report from the Apache Portable Runtime (APR) Project  [Yann Ylavic]

## Description:
The mission of the Apache Portable Runtime (APR) project is to create and 
maintain software libraries that provide a predictable and consistent interface 
to underlying platform-specific implementations. The primary goal is to provide 
an API to which software developers may code and be assured of predictable if 
not identical behaviour regardless of the platform on which their software is 
built, relieving them of the need to code special-case conditions to work 
around or take advantage of platform-specific deficiencies or features.

## Project Status:
Current project status: ongoing
Issues for the board: no issues requiring board attention

## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (24 years ago)
There are currently 68 committers and 43 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 Steffen Land on 2023-03-02.
- No new committers. Last addition was Steffen Land on 2023-02-27.

## Project Activity:
No new release this quarter.
Low activity, nothing unusual, the CI set up in recent quarters is in place
and green.

## Community Health:
The activity was quiet too from the community, the recent release looks stable.
A regression needs addressing but not urgently (reported and fixed downstream 
already by the BSD team).


-----------------------------------------
Attachment BF: Report from the Apache Portals Project  [Neil Griffin]

## Description:
The mission of Portals is the creation and maintenance of software related to
Portal technology

## Project Status:
Current project status: Current project status: Apache Portals Pluto is a stable
implementation of a JCP standard and is currently in a maintenance mode.
Issues under consideration at this point largely (if not entirely) consist
of 3rd party dependency upgrades.
Issues for the board: None at this time.

## Membership Data:
Apache Portals was founded 2004-02-17 (21 years ago)
There are currently 40 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Neil Griffin on 2017-02-11.
- No new committers. Last addition was Ahmed on 2016-08-06.

## Project Activity:
No new activity since the last report, which mentioned the release of
Apache Portals Pluto 3.1.2 on December 20, 2023.

## Community Health:
There is no recent activity on the dev lists, and no recent community
contributions. Again, the project is in a maintenance mode.


-----------------------------------------
Attachment BG: Report from the Apache Pulsar Project  [Matteo Merli]

## Description:

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

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

## Project Activity:

  - 4.0.0 was released on October 21st 2024
  - 4.0.1 was released on December 2nd 2024
  - 3.3.3 was released on December 3rd 2024
  - 3.0.8 was released on December 2nd 2024
  

  - Pulsar C++ releases:
    - 3.6.0 on September 6st 2024

  - Pulsar Go releases:
    - 0.14.0 was released on September 29th 2024

  - Pulsar reactive client:
    - 0.5.9 was released on November 14th 2024
    - 0.5.8 was released on October 18th 2024
   

  - We continue to have a very high number of "Pulsar Improvement
    Proposal" getting submitted, discussed and voted by the
    community:
   
    PIP-389: Add Producer config compressMinMsgBodySize to improve compression
             performance
    PIP-391: Enable batch index ack by default
    PIP-392: Add configuration to enable consistent hashing to select active
             consumer for partitioned topic
    PIP-393: Improve performance of Negative Acknowledgement
    PIP-395: Add Proxy configuration to support configurable response headers
             for http reverse-proxy
               
  - Pulsar has reached 675 contributors on the main Github repo
    (It was 661 contributors in October 2024)


## Health report:
  - There is healthy growth in the community, and several users are starting
    to become contributors to the project and engage more and more with
    the community. In this quarter, 8 contributors were invited as
    committers to the project.

## Membership Data:
  Apache Pulsar was founded 2018-09-18 (6 years ago)
  There are currently 84 committers and 43 PMC members in this project.
  
  The Committer-to-PMC ratio is roughly 2:1.

  Community changes, past quarter:
   - No new PMC members. Last addition was Baodi Shi on 2024-04-10.
   - No new committers. Last addition was WenZhi Feng on 2024-07-02.

## Community Health:

 - Activity on the mailing lists remains high with a mixture of new users,
   contributors, and deeper, more experienced users and contributors sparking
   discussion and questions and filing bugs or new features.

 - users@pulsar.apache.org:
    - 46% increase in traffic in the past quarter (19 emails compared to 13)

 - dev@pulsar.apache.org:
    - 8% increase in traffic in the past quarter (430 emails compared to 396)


## Slack activity:
  - 10546 Members (10454 in October 2024)
  - 258 Active montly users (246 in October 2024)


## GitHub activity:
 - 741 commits in the past quarter (-40% decrease)
 - 90 code contributors in the past quarter (-34% change)
 - 451 PRs opened on GitHub, past quarter (-25% change)
 - 428 PRs closed on GitHub, past quarter (-24% change)
 - 174 issues opened on GitHub, past quarter (-24% change)
 - 95 issues closed on GitHub, past quarter (-55% change)


-----------------------------------------
Attachment BH: Report from the Apache Ranger Project  [Selvamohan Neethiraj]

## Description:
The mission of Apache Ranger 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, with high activity
Issues for the board: none

## Membership Data:
Apache Ranger was founded 2017-01-17 (8 years ago)
There are currently 39 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Bhavik Patel on 2024-09-04.
- Brijesh Bhalala was added as committer on 2024-09-25
- Fateh Singh was added as committer on 2024-10-14
- Mahesh Bandal was added as committer on 2024-09-25
- Subhrat Chaudhary was added as committer on 2024-09-13

## Project Activity:
- added support for Ozone in Tagsync
- added utility to migrate admin audit logs from x_trx_log table to
  x_trx_log_v2 table
- added a custom condition to support validity schedule in policy items
- performance fixes in Ozone plugin
- performance improvements in HBase plugin
- performance improvements in policy engine in finding tags for multi-level
  resources, authorizing multiple access-types in a single call
- performance improvements in GDS policy engine in finding data shares for
  accessed resource
- docker setup updated to support ubi9-minimal base image, Apache Ozone
- GDS API updates to support bulk add/remove of resources in data shares,
  manage incremental grants for datasets
- GDS policy engine updates to support data-masking and row-filtering
- fixes in Oracle DB support
- code readability improvements: use of sortpom maven plugin to keep contents
  of pom files in order
- code readability improvements: use of codestyle maven plugin to enforce
  uniform coding style across Ranger code base (work-in-progress)
- dependent library version updates: aircompressor, Spring framework, Hive
  4.0.1, Bootbox.js to Bootprompt.js

## Community Health:
- 94 commits in the past quarter, an increase from 88 commits in the previous
  quarter
- 26 code contributors in the past quarter, an increase from 24 in the previous
  quarter

## Recent Releases:
- Apache Ranger 2.5.0 was released on 2024-08-07.
- Apache Ranger 2.4.0 was released on 2023-03-30.
- Apache Ranger 2.3.0 was released on 2022-07-06.


-----------------------------------------
Attachment BI: Report from the Apache Ratis Project  [Tsz-wo Sze]


-----------------------------------------
Attachment BJ: Report from the Apache Royale Project  [Yishay Weiss]

## Description:
The mission of Apache Royale is the creation and maintenance of software 
related to improving developer productivity in creating applications for 
wherever Javascript runs (and other runtimes)

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

## Membership Data:
Apache Royale was founded 2017-09-20 (7 years ago)
There are currently 20 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- Alina Kazi was added to the PMC on 2024-11-03
- No new committers. Last addition was María José Esteve on 2021-11-23.

## Project Activity:
0.9.12 was released, the announcement is coming soon. 

## Community Health:
The community status remains stable. There has been some discussion on the
need to revitalize it, but no concrete plan on how to do so.


-----------------------------------------
Attachment BK: Report from the Apache Samza Project  [Jagadish Venkatraman]

## Description:
The mission of Samza is the creation and maintenance of software related to 
distributed stream processing framework

## Project Status:
Current project status: healthy
Issues for the board: no issues require the board's

## Membership Data:
Apache Samza was founded 2015-01-22 (10 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.

## Project Activity:
Continue to make improvements and fixes for Apache Samza. 

Notable improvements have been around AzureHttpClient and RocksDb storage. 

## Community Health:
New contributions from the community on AzureHttpClient(s)

Community changes, past quarter:
- No new PMC members. Last addition was Bharath Kumarasubramanian on 2020-02-13.
- No new committers. Last addition was Shekhar Sharma on 2024-04-21.


-----------------------------------------
Attachment BL: Report from the Apache SeaTunnel Project  [Jun Gao]


-----------------------------------------
Attachment BM: Report from the Apache ServiceMix Project  [Krzysztof Sobkowiak]

## Description:
The mission of Apache ServiceMix project is to create and maintain a flexible,
open-source integration container, powered by OSGi, that unifies the features
and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful
runtime platform you can use to build your own integrations solutions.

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

## Membership Data:
Apache ServiceMix was founded 2007-09-19 (17 years ago)
There are currently 50 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.

## Project Activity:
bundles-2024.11 release is in progress right now.

## Community Health:
Still in maintenance mode.
We are helping/working on new camel-karaf releases including fixes.
ServiceMix Bundles are still used in Karaf (not anymore in
camel-karaf). Karaf will use another approach soon.


-----------------------------------------
Attachment BN: Report from the Apache Shiro Project  [Brian Demers]

## Description:
The mission of Shiro is the creation and maintenance of software related to 
Powerful and easy-to-use application security framework

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

Issues for the board: None at this time

## Membership Data:
Apache Shiro was founded 2010-09-21 (14 years ago)
There are currently 14 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 7:6.

Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Lenny Primak on 2022-11-02.

## Project Activity:
The Shiro team is in the planning stages for 3.0 which aims to cut
some tech debt and help move the project forward (and by dropping
deprecated functionality). New functionality and fixes are still
accepted in 2.x, 1.x is security fix only.

Last release was:
- 2.0.2: 2024-11-06

## Community Health:
There was a slight uptick in mailing list traffic due to the latest release.


-----------------------------------------
Attachment BO: Report from the Apache SINGA Project  [Wang Wei]

## Description:
The mission of Apache SINGA is the creation and maintenance of software related 
to a distributed deep learning platform

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

## Membership Data:
Apache SINGA was founded 2019-10-16 (5 years ago)
There are currently 23 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.

## Project Activity:
The team has released SINGA 4.3.0 on 07 September 2024.

In the past quarter, the community is working on the following
features/changes:

- Create the healthcare model zoo that consists of different models for
  healthcare applications, including
  - detection of thyroid eye disease from CT images
  - diabetic retinopathy classification
  - more traninig datasets for the healthcare application examples
- Optimize the distributed training by updating the MSOptimizer and MSSGD
- Update the data processing for the benchmark dataset
- Update the online documentations for the model zoo

## Community Health:
According to the statistics, there are increases in PRs and decreases in
commits. The community is less active in feature development but is more
active in model/application development.


-----------------------------------------
Attachment BP: Report from the Apache Sling Project  [Robert Munteanu]

## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.

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

## Membership Data:
Apache Sling was founded 2009-06-17 (15 years ago)
There are currently 51 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- Julian Reschke was added to the PMC on 2024-10-22
- No new committers. Last addition was Henry Kuijpers on 2023-10-19.

## Project Activity:
We released version 12 of our sample application, the Sling Starter, on March
18th, 2022. We have begun preparations for releasing version 13.

In the meantime individual modules are being developed and released, with 22
releases for this reporting period.

## Community Health:
Community health is pretty good and contributions from various
individuals continue.


-----------------------------------------
Attachment BQ: Report from the Apache SpamAssassin Project  [Sidney Markowitz]

Apache SpamAssassin report to Board for December 2024

## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.

## Project Status:
Project state: Ongoing with low to moderate activity
Primary focus for development is now ongoing maintenance bug fixes to the
latest release, 4.0.1.
Issues for the board: None

## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (20 years ago)
There are currently 33 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- New PMC member Kent Oyer added on 2024-11-09.
- No new committers. Last addition was Kent Oyer on 2024-03-29.

## Project Activity:
Last release was Apache SpamAssassin version 4.0.1 on 29 March 2024.
We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility.

## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.


-----------------------------------------
Attachment BR: Report from the Apache Storm Project  [Richard Zowalla]

## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system

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

## Membership Data:
Apache Storm was founded 2014-09-17 (10 years ago)
There are currently 48 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Nikhil Singh on 2023-10-23.
- Purshotam Shah was added as committer on 2024-10-08

## Project Activity:

Project activity has slowed in recent years. Storm is essentially in
maintenance mode.

However, we have received a number of pull requests from outside the existing
committership from various individuals. In addition, we received new bug
reports and a slight increase in discussions or questions on our dev / user
list, which is a good sign that Storm is still being used.

We are really happy to have added a new committer and hope to see more
contributions from him in the near future.

In the last quarter, we also upgraded a lot of third-party libraries to newer
versions in order to reduce technical debt, and made two maintenance releases.
We hope to maintain this release cadence and release patches at a similar
frequency.

We continue to work on reducing third-party dependencies in Storm. Storm
depends on many third-party libraries. It remains a huge task to to reduce
this technical debt in order to have a controlled set of third-party
dependencies. For this reason, we are discussing to drop the support for Hive
in the next release and also raising the Java Runtime Level to 17 or 21
depending on the outcome of our discussuions.

On another technical note, the Storm UI has a lot of legacy and outdated
Javascript libraries in the Git repository. Unfortunately, we still
do not have dedicated and skilled frontend developers among the active
committers.

The project has decided to migrate issues from Jira to GitHub, but we have not
made any progress. We want to migrate our old issues to GitHub, but the issue
on the INFRA side is still stalled. We have followed up with INFRA but have
received no response. Therefore, we haven't made any progress in this area due
to the summer holidays.

We have approved the name of the StormCrawler Poddling in the Apache Incubator.

Recent releases:
2.7.1 was released on 2024-11-29.
2.7.0 was released on 2024-10-19.
2.6.4 was released on 2024-09-03.
2.6.3 was released on 2024-07-22.

## Community Health:
Community engagement is currently healthy, but could benefit from new
contributors or users.


-----------------------------------------
Attachment BS: Report from the Apache Synapse Project  [Isuru Udana]


-----------------------------------------
Attachment BT: Report from the Apache Tapestry Project  [Thiago Henrique De Paula Figueiredo]

## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework

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

## Membership Data:
Apache Tapestry was founded 2006-02-14 (19 years ago)
There are currently 30 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Ben Weidig on 2021-12-02.
- No new committers. Last addition was Christian Köberl on 2024-05-02.

## Project Activity:
We've published a second preview version of 5.9.0, the first version
with support for Jakarta EE. We've cleaned up more than a dozen pull
requests, either by merging them, closing them for being outdated
or implementing the action of the pull request without merging it.
A number of outdated dependencies with known security vulnerabilities
got upgraded.

## Community Health:
Both the dev (+44% traffic) and user (+23%) mailing lists got
more traffic than the previous quarter.


-----------------------------------------
Attachment BU: Report from the Apache Tcl Project  [Georgios Petasis]

## Description:
The mission of Tcl is the creation and maintenance of software related to
Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration
efforts. The purpose of our project is to combine the power of the Apache
web server with the capabilities of the mature, robust and flexible Tcl
scripting language. Currently only the Apache Rivet project is actively
maintained.

## Project Status:
Current project status: Ongoing Issues for the board: Delays in board
reporting, due to a series of personal events (my father died on October 25,
and my mother had a surgery on December 9).

## Membership Data:
Apache Tcl was founded 2000-07-24 (24 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Brice Hamon De Crevecoer on 2014-11-25.
- No new committers. Last addition was Brice B. Hamon on 2014-11-25.

## Project Activity:
During this reporting period, rivet 3.2.6 (released on 2024-11-12) has been
released. Rivet 3.2.6 improves DIO, an Itcl based DBMS access abstraction
layer, with a new connector that supports the TDBC series of connectors (all
these relate to connecting to relational DBs). There is a discussion whether
the whole infrastructure should be ported to TclOO, as it is better supported
in Tcl 9.0.

## Community Health:
The traffic of the mailing lists has increased in comparison to the
previous reporting period, which is normal for the project (as most traffic in
the list happens after new releases).


-----------------------------------------
Attachment BV: Report from the Apache Tomcat Project  [Mladen Turk]


## Description:
The Apache Tomcat® software is an open source implementation of the Jakarta
Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket,
Jakarta Annotations and Jakarta Authentication specifications. These
specifications are part of the Jakarta EE platform.

The Jakarta EE platform is the evolution of the Java EE platform. Tomcat 10
and later implement specifications developed as part of Jakarta EE. Tomcat 9
and earlier implement specifications developed as part of Java EE.

The Apache Tomcat software is developed in an open and participatory
environment and released under the Apache License version 2. The Apache Tomcat
project is intended to be a collaboration of the best-of-breed developers from
around the world. We invite you to participate in this open development
project. To learn more about getting involved, click here.

Apache Tomcat software powers numerous large-scale, mission-critical web
applications across a diverse range of industries and organizations. Some of
these users and their stories are listed on the PoweredBy wiki page.

Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat
project logo are trademarks of the Apache Software Foundation.

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


## Membership Data:
Apache Tomcat was founded 2005-05-18 (19 years ago)
There are currently 50 committers and 29 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 Han Li on 2023-03-06.
- No new committers. Last addition was Dimitris Soumis on 2024-07-05.

## Project Activity:
- Apache Tomcat 11.0.02 was released on 2024-12-09.
- Apache Tomcat 11.0.01 was released on 2024-11-10.
- Apache Tomcat 10.1.34 was released on 2024-12-09.
- Apache Tomcat 10.1.33 was released on 2024-11-11.
- Apache Tomcat 9.0.98 was released on 2024-12-09.
- Apache Tomcat 9.0.97 was released on 2024-11-09.

## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.


-----------------------------------------
Attachment BW: Report from the Apache TVM Project  [Tianqi Chen]

## Description:
The mission of Apache TVM is the creation and maintenance of software related 
to compilation of machine learning models to run on a wide range of hardware 
platforms

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

## Membership Data:
Apache TVM was founded 2020-11-17 (4 years ago)
There are currently 77 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- Star Yuan was added to the PMC on 2024-10-27
- Masahiro Hiramori was added as committer on 2024-09-23

We also continue to find new committers.

## Project Activity:

Recent releases:

- 0.18.0 was released on 2024-11-27.
- 0.17.0 was released on 2024-09-10.
- 0.16.0 was released on 2024-06-12.

The community continues to develop the project. Most of recent developments
has been on maintainace fronts. The community also start to phase out legacy
components to reduce overall complexity of the codebase. Notable developments
include

- KVCache attention kernel improvements for various backends
- Make ORCJIT LLVM executor the default one
- ONNX frontend coverage of the relax flow


## Community Health:

The project get about 225 commits in the past quarter. As the field of ML
moves fast, the community needs to keep up with the interest shift of the ML
community. We still see interesting needs on areas like LLM  inference and
generative AI models. The overall developments starts to shift to stablizing
and maintainace, with also mindful effort on bringing new momentums on the
latest generative AI fronts.


-----------------------------------------
Attachment BX: Report from the Apache UIMA Project  [Richard Eckart de Castilho]

## Description:
Apache UIMA (*) software provides frameworks, tools and annotators, 
facilitating the analysis of unstructured content such as text, audio and 
video. (*) Unstructured Information Management Architecture.

## Project Status:
Current project status: Ongoing (low)
Issues for the board: There as still board comments shown in the reporting tool
from 2024_06_19. These have been responded to in the last two reports.
Assuming the board has acknowledge the response, it would be great if the
comments should be removed now.

## Membership Data:
Apache UIMA was founded 2010-03-17 (14 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.

## Project Activity:
* uima-ruta-3.5.0 was released on 2024-12-04.
* uimaj-3.6.0 was released on 2024-11-27.

uimaFIT has been merged into uimaj and has ceased to exist as an independent
subproject.

## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list / issue tracker, but not much overall.


-----------------------------------------
Attachment BY: Report from the Apache Unomi Project  [Serge Huber]

## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee

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

## Membership Data:
Apache Unomi was founded 2019-02-20 (6 years ago)
There are currently 16 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- Jonathan Sinovassin-Naïk was added to the PMC on 2024-11-25
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.

## Project Activity:
The project has just released version 2.6.0, which includes bug fixes,
security fixes, improvements and a new health endpoint. Work on OpenSearch
support is also underway and should be landing soon. GraphQL changes for
the developer UI has also been merged.

## Community Health:
The community activity is cyclic, and is clearly picking up. The project has
just elected a new PMC member and direct feedback from the community at the
ASF's conference in Denver confirmed the interest in the project. Along with
that promotion and communication efforts have been done to make the project
more visible including a video on the FeatherCast (thanks to Rich Bowen). To
answer the question from the board, the commit activity has diversified again
and it not considered problematic at all.


-----------------------------------------
Attachment BZ: Report from the Apache VCL Project  [Josh Thompson]

## Description:
The mission of the Apache VCL project is to create and maintain of software 
related to a modular cloud computing platform which dynamically provisions and 
brokers remote access to compute resources.

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

## Membership Data:
Apache VCL was founded 2012-06-19 (12 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.

Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.

## Project Activity:
Sadly, progress toward our next release has stalled again. However, we are
working through something that came up on the private list recently.

## Community Health:
Apache VCL is still being used by at least a few colleges and
universities, and though activity is pretty light, it is not dormant.


-----------------------------------------
Attachment CA: Report from the Apache Web Services Project  [Daniel Kulp]

## Description:
Apache Web Services is a collection of shared technologies related to SOAP/XML
based Web Services that can be shared by different implementations. Spring-WS,
Axis2, CXF, and others use parts of the technology created within Apache Web
Services.


## Project Status:
Current project status: ongoing, very low activity
Issues for the board: none


## Membership Data:
Apache Web Services was founded 2003-01-22 (22 years ago)
There are currently 223 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.

Community changes, past quarter:
- No new PMC members. Last addition was Robert Lazarski on 2021-06-14.
- No new committers. Last addition was Alessio Soldano on 2014-09-14.

## Project Activity:
WebServices is a mature project based on standards that are also quite mature.
As such, there is not a significant amount of activity required. However, user
questions are being answered promptly, bugs are being fixed, and there are at
least 3 independent PMC members around making sure the project can continue to
produce releases as needed.   Since SOAP/XML based Web Services is no longer
considered state of the art, we don't expect a major uptick in new development
efforts, new committers, etc...

There was a patch release to WSS4J this period (3.0.4) to update to the latest
Santuario release and a few other dependency updates.  It also contains a new
feature related to some new Key Derivation parameters which was requested by a
user.

There was also a patch release to Neethi (3.2.1) to fix a single bug reported
by a user.

Latest Releases: 
WSS4J 3.0.4 was released on 2024-11-14 
Neethi-3.2.1 was released on 2024-10-30. 
XmlSchema-2.3.1 was released on 2023-09-07.
Axiom-1.4.0: 2022-05-14
Woden-1.0M10: 2015-09

## Community Health:
As mentioned, SOAP/WebServices is not considered state-of-the-art anymore and
we are getting very little contribution from anyone other than the 2 or 3
regulars" that are driving features and changes needed for CXF (which is
being driven by their employers).   Thus, we are not seeing any possibilities
for future new committers or PMC members.  However, there are plenty of
people around that can do releases and answer questions and respond to
security issues.  It's a mature project.


-----------------------------------------
Attachment CB: Report from the Apache Wicket Project  [Andrea Del Bene]

## Description:
The mission of Wicket is the creation and maintenance of software related to 
Component-based Java Web Application Framework.

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

## Membership Data:
Apache Wicket was founded 2007-06-20 (17 years ago)
There are currently 34 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
-No new PMC members. Last addition was Richard Eckart de Castilho on 2024-07-01.
-No new committers. Last addition was Richard Eckart de Castilho on 2024-07-01.


## Project Activity:
In the last quarter we had 2 maintenance releases for Wicket 10.x. We are about
to start rolling the version 10.3.0 and 9.19.0 that will fix CVE-2024-53299 
(thanks to Pedro Santos pedro@apache.org) 

## Community Health:
community stays healthy and participant. We received contribution for both 
bug fixes and improvements. Some of the later have been targeted for the next 
main release as they require APIs breaks or are meant for more recent Java 
releases.


-----------------------------------------
Attachment CC: Report from the Apache Yetus Project  [Allen Wittenauer]

## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.

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

## Membership Data:
Apache Yetus was founded 2015-09-15 (9 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.

Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.

## Project Activity:
Work continues on getting out a 0.15.1 release.  Primary focus remains updating
the docker container that is used by the Github Marketplace and other users.
I personally had some offline conversations with some users downstream 
that pointed out some issues that required further debugging, delaying
some things. 

## Community Health:
Low activity across all human-related metrics, but given the stable status of
the project that should not be surprising.  Still in use by other Apache
projects and others outside of the ASF.


-----------------------------------------
Attachment CD: Report from the Apache ZooKeeper Project  [Flavio Paiva Junqueira]

## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.

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

## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (14 years ago)
There are currently 33 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1. We did not extend invitations
to new committers or PMC members during this period.

Community changes, past quarter:
- No new PMC members. Last addition was Damien Diederen on 2024-04-16.
- No new committers. Last addition was Kezhu Wang on 2024-08-02.

## Project Activity:
The latest release is 3.9.3 released on 2024-10-24. On releases, there was
this comment from the board:

> I saw several vote threads that started with "RE" so I increased the
> search range and saw that the last release votes took almost a full month
> to reach the 3 binding +1 votes. - ZooKeeper 3.9.2: Started on 12th Feb, 
> Finished 11th Mar - ZooKeeper 3.8.4: Started on 12th Feb, Finished 4th Mar
> Not sure the project could fire out a release quickly, if needed.

Using 3.9.3 as a recent example: 
- There was a release prep thread that started on Sep. 17th and ended
on Oct. 1st. 
- The vote for rc0 started on Oct. 1st and closed on Oct. 8th
- The vote for rc1 started on Oct. 9th and closed on Oct. 17th.
- The vote for rc2 started on Oct. 18th and closed on Oct. 24th

It is accurate that the whole process took over a month, but the individual
discussion and vote threads took a very reasonable amount of time as
we give time for input and there were multiple release candidates. The PMC
consequently does not perceive a problem with our ability to release quickly.

## Community Health:
The project historically has had more activity in the dev list than in the
user list. It remains the same, and while we see some messages coming in the
user list, most of the activity for the period is in the dev list. There are
multiple contributions about maintaining the project and the code base. One 
noticeable point is that there has been some interest from the community about
a Rust client for ZooKeeper, and there is some initial effort ongoing:

https://github.com/fanyang89/fastkeeper


------------------------------------------------------
End of minutes for the December 18, 2024 board meeting.

Index

• Call to order
• Roll Call
• Minutes from previous meetings
• The meeting of November 20, 2024
• Executive Officer Reports
• Board Chair [Shane Curcuru]
• President [Ruth Suehle]
• Treasurer [Craig R. McClanahan]
• Secretary [Matt Sicker]
• Executive Vice President [David Nalley]
• Vice Chair [Justin Mclean]
• Additional Officer Reports
• VP of W3C Relations [Andy Seaborne / Sander]
• Apache Legal Affairs Committee [Roman Shaposhnik / Jeff]
• Apache Security Team Project [Mark J. Cox / Willem]
• Committee Reports
• Apache Avro Project [Ryan Skraba / Craig]
• Apache Druid Project [Gian Merlino / Rich]
• Apache Incubator Project [Justin Mclean]
• Apache Libcloud Project [Tomaž Muraus / Justin]
• Apache Mnemonic Project [Gordon King / Kanchana]
• Apache OpenWebBeans Project [Mark Struberg / Jeff]
• Apache Pig Project [Koji Noguchi / Sander]
• Apache Pivot Project [Roger Lee Whitcomb / JB]
• Apache Ratis Project [Tsz-wo Sze / JB]
• Apache SeaTunnel Project [Jun Gao / Rich]
• Apache Synapse Project [Isuru Udana / JB]
• Special Orders
• Change the Apache Kylin Project Chair
• Change the Apache Calcite Project Chair
• Establish the Apache Answer Project
• Change the Logo Development Committee Chair
• Decision Regarding 401k Matching and Profit Sharing
• Establish position of VP, ECMA Relations
• Discussion Items
• Review Outstanding Action Items
• Unfinished Business
• New Business
• Announcements
• Adjournment
• Report from the VP of Brand Management [Mark Thomas]
• Report from the VP of Fundraising [Bob Paulin]
• Report from the VP of Marketing and Publicity [Brian Proffitt]
• Report from the VP of Infrastructure [Myrle Krantz]
• Report from the VP of Tooling [Dave Fisher]
• Report from the VP of Conferences [Brian Proffitt]
• Report from the Apache Travel Assistance Committee [Gavin McDonald]
• Report from the VP of Diversity and Inclusion [David Nalley]
• Report from the VP of Data Privacy [Christian Grobmeier]
• Report from the VP of Public Affairs [Dirk-Willem van Gulik]
• Report from the VP of W3C Relations [Andy Seaborne]
• Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
• Report from the Apache Security Team Project [Mark J. Cox]
• Report from the Apache Airavata Project [Suresh Marru]
• Report from the Apache Airflow Project [Bolke de Bruin]
• Report from the Apache Allura Project [David Philip Brondsema]
• Report from the Apache Atlas Project [Madhan Neethiraj]
• Report from the Apache Avro Project [Ryan Skraba]
• Report from the Apache Axis Project [Robert Lazarski]
• Report from the Apache Beam Project [Kenneth Knowles]
• Report from the Apache Bigtop Project [Masatake Iwasaki]
• Report from the Apache BVal Project [Matthew Jason Benson]
• Report from the Apache Camel Project [Andrea Cosentino]
• Report from the Apache Cayenne Project [Michael Ray Gentry]
• Report from the Apache CloudStack Project [Daniel Augusto Veronezi Salvador]
• Report from the Apache Commons Project [Gary D. Gregory]
• Report from the Apache Cordova Project [Bryan Ellis]
• Report from the Apache cTAKES Project [Pei Chen]
• Report from the Apache Curator Project [Enrico Olivelli]
• Report from the Apache Daffodil Project [Mike Beckerle]
• Report from the Apache DataFusion Project [Andrew Lamb]
• Report from the Apache Directory Project [Shawn McKinney]
• Report from the Apache Druid Project [Gian Merlino]
• Report from the Apache ECharts Project [Wenli Zhang]
• Report from the Apache Felix Project [Karl Pauls]
• Report from the Apache Flex Project [Harbs]
• Report from the Apache Flink Project [Robert Metzger]
• Report from the Apache Gobblin Project [Abhishek Tiwari]
• Report from the Apache Guacamole Project [Mike Jumper]
• Report from the Apache Gump Project [Stefan Bodewig]
• Report from the Apache Helix Project [Junkai Xue]
• Report from the Apache Hive Project [Naveen Gangam]
• Report from the Apache Hudi Project [Vinoth Chandar]
• Report from the Apache Iceberg Project [Ryan Blue]
• Report from the Apache Incubator Project [Justin Mclean]
• Report from the Apache IoTDB Project [Xiangdong Huang]
• Report from the Apache Jackrabbit Project [Marcel Reutegger]
• Report from the Apache Karaf Project [Jean-Baptiste Onofré]
• Report from the Apache Kvrocks Project [Mingyang Liu]
• Report from the Apache Kyuubi Project [Kent Yao]
• Report from the Apache Libcloud Project [Tomaž Muraus]
• Report from the Apache Linkis Project [Shuai Di]
• Report from the Apache Logo Development Project [Jeff Genender]
• Report from the Apache Lucene Project [Chris Hegarty]
• Report from the Apache Lucene.Net Project [Shad Storhaug]
• Report from the Apache Mnemonic Project [Gordon King]
• Report from the Apache Mynewt Project [Szymon Janc]
• Report from the Apache NetBeans Project [Geertjan Wielenga]
• Report from the Apache OFBiz Project [Jacopo Cappellato]
• Report from the Apache Olingo Project [Michael Bolz]
• Report from the Apache OpenDAL Project [Hao Ding]
• Report from the Apache OpenNLP Project [Jeff Zemerick]
• Report from the Apache OpenOffice Project [Dave Fisher]
• Report from the Apache OpenWebBeans Project [Mark Struberg]
• Report from the Apache Paimon Project [Jingsong Lee]
• Report from the Apache Pekko Project [PJ Fanning]
• Report from the Apache Pig Project [Koji Noguchi]
• Report from the Apache Pivot Project [Roger Lee Whitcomb]
• Report from the Apache PLC4X Project [César García]
• Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
• Report from the Apache Portals Project [Neil Griffin]
• Report from the Apache Pulsar Project [Matteo Merli]
• Report from the Apache Ranger Project [Selvamohan Neethiraj]
• Report from the Apache Ratis Project [Tsz-wo Sze]
• Report from the Apache Royale Project [Yishay Weiss]
• Report from the Apache Samza Project [Jagadish Venkatraman]
• Report from the Apache SeaTunnel Project [Jun Gao]
• Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
• Report from the Apache Shiro Project [Brian Demers]
• Report from the Apache SINGA Project [Wang Wei]
• Report from the Apache Sling Project [Robert Munteanu]
• Report from the Apache SpamAssassin Project [Sidney Markowitz]
• Report from the Apache Storm Project [Richard Zowalla]
• Report from the Apache Synapse Project [Isuru Udana]
• Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
• Report from the Apache Tcl Project [Georgios Petasis]
• Report from the Apache Tomcat Project [Mladen Turk]
• Report from the Apache TVM Project [Tianqi Chen]
• Report from the Apache UIMA Project [Richard Eckart de Castilho]
• Report from the Apache Unomi Project [Serge Huber]
• Report from the Apache VCL Project [Josh Thompson]
• Report from the Apache Web Services Project [Daniel Kulp]
• Report from the Apache Wicket Project [Andrea Del Bene]
• Report from the Apache Yetus Project [Allen Wittenauer]
• Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]