The Apache Software Foundation

                  Board of Directors Meeting Minutes

                            June 21, 2023


1. Call to order

    The meeting was scheduled for 07:30 UTC and began at 7:30 when a
    sufficient attendance to constitute a quorum was recognized by
    the chair.

    Other Time Zones: https://s.apache.org/b20230621

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

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

2. Roll Call

    Directors Present:

      Rich Bowen
      Shane Curcuru
      Bertrand Delacretaz
      Christofer Dutz
      Sharan Foga
      Willem Ning Jiang
      Justin Mclean
      Craig L Russell
      Sander Striker

    Directors Absent:

      none

    Executive Officers Present:

      David Nalley
      Matt Sicker

    Executive Officers Absent:

      Craig R. McClanahan
      Ruth Suehle

    Guests:

      Brian Proffitt
      Daniel Gruno
      Dirk-Willem van Gulik
      Gavin McDonald
      Greg Stein
      Jarek Potiuk

3. Minutes from previous meetings

    Published minutes can be found at:

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

    A. The meeting of May 17, 2023

       See: board_minutes_2023_05_17.txt

       Tabled.

4. Executive Officer Reports

    A. Board Chair [Sander Striker]

       Most of this month has been spent on preparing on the Board face to
       face meeting, which is currently in progress.  There are learnings
       to be had from this meeting, which we'll look back on next month.

    B. President [David Nalley]

       I worked with Dirk on figuring out our priorities around CRA and PLD

       I also prepared for and attended the board face-to-face meeting.

       Additionally, please see Attachments 1 through 8.


    C. Treasurer [Craig R. McClanahan]

       I sent to the board@apache.org mailing list the financial results for
       both the entire 2022-2023 fiscal year, and the results for May 2023. 
       To ensure they are recorded in the board meeting minutes, here are the
       comments I included with that email:

       NOTES FOR THE FISCAL YEAR REPORT:
       * Financially, we operate on an accrual basis.  The impact of this is
         most notable in the "Sponsorship Program" income, where we receive
         the entire amount of each sponsorship ahead of time, but allocate
         the revenue across the relevant months in 12 equal portions.
       * In accordance with the Board-approved resolution, we transferred
         funds not needed for current operations ($2 million) to an Operating
         Reserve fund.  That investment earned us just over $48,000 in
         interest, which is being reinvested.
       * Overall for the year, revenues exceeded expenses by just over
         $200,000.
       * As I mentioned in my previous Board Report, we have successfully
         collected the funds formerly deposited with Citizen's Bank, and
         transferred them to our TD Bank account.  This happened over the
         fiscal year-end boundary, so it shows on the Balance Sheet as an
         entry in account 1060 (Temporary Clearing) along with zeroing the
         balance of 1010 (Citizen's Checking).
       * Account 1072 (Unrealized Gains/Losses) on the balance sheet reflects
         the fact that, if we had to sell all of our investments today, we
         would lose money - which won't happen.  The cause for this is the
         long string of Federal Reserve interest rate increases, which drives
         down the list price for bonds.  As those bonds mature, we will
         receive the original par value for them, as well as the interest we
         earn in the meantime.
       * We continue to record the $500,000 "Conditional Gift" in account
         2210.  This cash remains in our Checking Account, until the Board
         decides what we want to do with it.

       NOTES FOR THE MAY 2023 REPORT:
       * Expenses related to the Board Face-to-Face meeting happening in
         Berlin are accumulating in account 6010 (Chairmans Discretionary). 
         There will be additional expenses related to this trip in June.

    D. Secretary [Matt Sicker]

       In May, the secretary received 39 ICLAs, 3 CCLAs, and 1 CoI
       affirmation.

    E. Executive Vice President [Ruth Suehle]

       Planning for Community Over Code NA proceeds well.

       As mentioned last month, preparing to attend Open Source Congress with
       David on behalf of the ASF next month

    F. Vice Chair [Sharan Foga]

       Main work has been helping prepare for Board Face to Face in Berlin
       Currently assisting with:
       - Meeting logistics, planning and organisation
       - Finalisation and preparation of the meeting agenda

    Executive officer reports approved as submitted by General Consent.

5. Additional Officer Reports

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

       No report was submitted.

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

       See Attachment 10

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

       See Attachment 11

       @Bertrand: Follow up with Zeppelin roll call

    D. VP of Jakarta EE Relations [Rob Tompkins / Christofer]

       No report was submitted.

    Additional officer reports approved as submitted by General Consent.

6. Committee Reports

    Summary of Reports

     The following reports required further discussion:

        # Airflow [striker]
        # Ant [striker]
        # Axis [striker]
        # Bahir [striker]
        # MXNet [striker]
        # Mnemonic [jmclean]
        # Mynewt [clr]
        # Portable Runtime (APR) [jmclean]
        # Security Team [striker]
        # Wicket [striker]

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

       See Attachment A

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

       See Attachment B

    C. Apache Ambari Project [Roman Shaposhnik / Justin]

       See Attachment C

    D. Apache Ant Project [Jan Materne / Sander]

       See Attachment D

    E. Apache Any23 Project [Lewis John McGibbney / Willem]

       No report was submitted.

    F. Apache Archiva Project [Olivier Lamy / Sharan]

       See Attachment F

    G. Apache Atlas Project [Madhan Neethiraj / Craig]

       See Attachment G

    H. Apache Axis Project [Robert Lazarski / Rich]

       See Attachment H

    I. Apache Bahir Project [João Boto / Rich]

       See Attachment I

    J. Apache Beam Project [Kenneth Knowles / Shane]

       See Attachment J

    K. Apache Bigtop Project [Yuqi Gu / Sharan]

       See Attachment K

    L. Apache Bloodhound Project [Gary Martin / Christofer]

       No report was submitted.

    M. Apache BVal Project [Matthew Jason Benson / Justin]

       See Attachment M

    N. Apache Camel Project [Andrea Cosentino / Willem]

       See Attachment N

    O. Apache Cayenne Project [Michael Ray Gentry / Sander]

       See Attachment O

    P. Apache CloudStack Project [Rohit Yadav / Bertrand]

       See Attachment P

    Q. Apache Commons Project [Gary D. Gregory / Justin]

       See Attachment Q

    R. Apache Cordova Project [Jesse MacFadyen / Sharan]

       See Attachment R

    S. Apache CouchDB Project [Jan Lehnardt / Bertrand]

       See Attachment S

    T. Apache cTAKES Project [Pei Chen / Willem]

       See Attachment T

    U. Apache Curator Project [Enrico Olivelli / Christofer]

       See Attachment U

    V. Apache Daffodil Project [Mike Beckerle / Shane]

       See Attachment V

    W. Apache DeltaSpike Project [Mark Struberg / Rich]

       See Attachment W

    X. Apache ECharts Project [Wenli Zhang / Craig]

       See Attachment X

    Y. Apache EventMesh Project [Eason Chen / Sander]

       See Attachment Y

    Z. Apache Felix Project [Karl Pauls / Willem]

       See Attachment Z

    AA. Apache Flagon Project [Joshua C. Poore / Shane]

       See Attachment AA

    AB. Apache Flex Project [Harbs / Sharan]

       See Attachment AB

    AC. Apache Flink Project [Robert Metzger / Justin]

       See Attachment AC

    AD. Apache Giraph Project [Dionysios Logothetis / Christofer]

       No report was submitted.

       @Christofer: pursue a report for Giraph

    AE. Apache Gobblin Project [Abhishek Tiwari / Bertrand]

       See Attachment AE

    AF. Apache Gora Project [Kevin Ratnasekera / Craig]

       See Attachment AF

    AG. Apache Guacamole Project [Mike Jumper / Rich]

       See Attachment AG

    AH. Apache Gump Project [Stefan Bodewig / Sander]

       See Attachment AH

    AI. Apache Helix Project [Junkai Xue / Craig]

       See Attachment AI

    AJ. Apache Hive Project [Naveen Gangam / Christofer]

       See Attachment AJ

    AK. Apache Hudi Project [Vinoth Chandar / Craig]

       See Attachment AK

    AL. Apache Iceberg Project [Ryan Blue / Willem]

       See Attachment AL

    AM. Apache Incubator Project [Justin Mclean]

       See Attachment AM

    AN. Apache IoTDB Project [Xiangdong Huang / Sharan]

       See Attachment AN

    AO. Apache Jackrabbit Project [Marcel Reutegger / Sander]

       See Attachment AO

    AP. Apache Karaf Project [Jean-Baptiste Onofré / Justin]

       See Attachment AP

    AQ. Apache Kibble Project [Sharan Foga]

       See Attachment AQ

    AR. Apache Kyuubi Project [Kent Yao / Bertrand]

       See Attachment AR

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

       No report was submitted.

       @Shane: pursue a report for Libcloud

    AT. Apache Linkis Project [Shuai Di / Rich]

       See Attachment AT

    AU. Apache Lucene Project [Greg Miller / Shane]

       See Attachment AU

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

       No report was submitted.

    AW. Apache Mnemonic Project [Yanhui Zhao / Christofer]

       See Attachment AW

       @Shane: Follow up with Mnemonic about PMC Chair

    AX. Apache MXNet Project [Sheng Zha / Justin]

       See Attachment AX

       @Justin: Follow up with the PMC Chair

    AY. Apache Mynewt Project [Szymon Janc / Justin]

       See Attachment AY

    AZ. Apache NetBeans Project [Geertjan Wielenga / Rich]

       See Attachment AZ

    BA. Apache OFBiz Project [Jacopo Cappellato / Willem]

       See Attachment BA

    BB. Apache Olingo Project [Michael Bolz / Sharan]

       See Attachment BB

    BC. Apache OpenNLP Project [Jeff Zemerick / Shane]

       See Attachment BC

    BD. Apache OpenWebBeans Project [Mark Struberg / Bertrand]

       See Attachment BD

    BE. Apache Pig Project [Koji Noguchi / Craig]

       No report was submitted.

    BF. Apache Pivot Project [Roger Lee Whitcomb / Craig]

       See Attachment BF

    BG. Apache PLC4X Project [Christofer Dutz]

       See Attachment BG

    BH. Apache Portable Runtime (APR) Project [Yann Ylavic / Bertrand]

       See Attachment BH

    BI. Apache Portals Project [Neil Griffin / Justin]

       See Attachment BI

    BJ. Apache Pulsar Project [Matteo Merli / Christofer]

       See Attachment BJ

    BK. Apache Royale Project [Piotr Zarzycki / Willem]

       See Attachment BK

    BL. Apache SeaTunnel Project [Calvin Kirs / Shane]

       See Attachment BL

    BM. Apache Serf Project [Justin Erenkrantz / Rich]

       No report was submitted.

    BN. Apache ServiceMix Project [Krzysztof Sobkowiak / Sharan]

       See Attachment BN

    BO. Apache Shiro Project [Brian Demers / Sander]

       See Attachment BO

    BP. Apache SINGA Project [Wang Wei / Bertrand]

       See Attachment BP

    BQ. Apache Sling Project [Robert Munteanu / Sander]

       See Attachment BQ

    BR. Apache SpamAssassin Project [Sidney Markowitz / Shane]

       See Attachment BR

    BS. Apache Storm Project [P. Taylor Goetz / Craig]

       No report was submitted.

    BT. Apache Submarine Project [Liu Xun / Justin]

       See Attachment BT

    BU. Apache Synapse Project [Isuru Udana / Willem]

       See Attachment BU

    BV. Apache Tomcat Project [Mladen Turk / Sharan]

       See Attachment BV

    BW. Apache TomEE Project [David Blevins / Rich]

       See Attachment BW

    BX. Apache TVM Project [Tianqi Chen / Christofer]

       See Attachment BX

    BY. Apache UIMA Project [Richard Eckart de Castilho / Sharan]

       See Attachment BY

    BZ. Apache Unomi Project [Serge Huber / Craig]

       See Attachment BZ

    CA. Apache VCL Project [Josh Thompson / Justin]

       See Attachment CA

    CB. Apache Velocity Project [Nathan Bubna / Bertrand]

       See Attachment CB

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

       See Attachment CC

    CD. Apache Yetus Project [Allen Wittenauer / Sander]

       See Attachment CD

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

       See Attachment CE

    Committee reports approved as submitted by General Consent.

7. Special Orders

    A. Terminate the Apache Any23 Project

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

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

       NOW, THEREFORE, BE IT RESOLVED, that the Apache Any23 project is hereby
       terminated; and be it further

       RESOLVED, that the Attic PMC be and hereby is tasked with oversight
       over the software developed by the Apache Any23 Project; and be it
       further

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

       RESOLVED, that the Apache Any23 PMC is hereby terminated.

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

    B. Change the Apache SeaTunnel Project Chair

       WHEREAS, the Board of Directors heretofore appointed Calvin Kirs (kirs)
       to the office of Vice President, Apache SeaTunnel, when establishing
       the project, and

       WHEREAS, the project had instead intended for Jun Gao (gaojun2048) to
       be the PMC chair of the newly established project, a choice with which
       the Board agrees,

       NOW, THEREFORE, BE IT RESOLVED, that Calvin Kirs is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache SeaTunnel, and

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

    C. Change the Apache BookKeeper Project Chair

       WHEREAS, the Board of Directors heretofore appointed Sijie Guo (sijie)
       to the office of Vice President, Apache BookKeeper, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Sijie Guo from the office of Vice President, Apache BookKeeper, and

       WHEREAS, the Project Management Committee of the Apache BookKeeper
       project has chosen by vote to recommend Enrico Olivelli (eolivelli) as
       the successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Sijie Guo is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache BookKeeper, and

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

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

    D. Establish the Apache Kvrocks 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 distributed key-value NoSQL database,
       supporting the rich data structure.

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

       RESOLVED, that the Apache Kvrocks Project be and hereby is responsible
       for the creation and maintenance of software related to a distributed
       key-value NoSQL database, supporting the rich data structure; and be it
       further

       RESOLVED, that the office of "Vice President, Apache Kvrocks" 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 Kvrocks
       Project, and to have primary responsibility for management of the
       projects within the scope of responsibility of the Apache Kvrocks
       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 Kvrocks
       Project:
         
       * Alfejik Liu <alfejik@apache.org>    
       * Hulk Lin <hulk@apache.org>       
       * Jean-Baptiste Onofré <jbonofre@apache.org>     
       * Liang Chen <chenliang613@apache.org>               
       * Mingyang Liu <twice@apache.org>             
       * Von Gosling <vongosling@apache.org>              
       * Xiaoqiao He <hexiaoqiao@apache.org>              
       * Yaroslav Stepanchuk <torwig@apache.org>      
       * Yuan Wang <wangyuan@apache.org>    
       * Zili Chen <tison@apache.org>    

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed to
       the office of Vice President, Apache Kvrocks, to serve in accordance
       with and subject to the direction of the Board of Directors and the
       Bylaws of the Foundation until death, resignation, retirement, removal
       or disqualification, or until a successor is appointed; and be it
       further

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

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

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

    E. Change the Apache Brooklyn Project Chair

       WHEREAS, the Board of Directors heretofore appointed Geoff Macartney
       (geomacy) to the office of Vice President, Apache Brooklyn, and

       WHEREAS, the Board of Directors is in receipt of the resignation of
       Geoff Macartney from the office of Vice President, Apache Brooklyn, and

       WHEREAS, the Project Management Committee of the Apache Brooklyn
       project has chosen by vote to recommend Juan D. Cabrerizo (jcabrerizo)
       as the successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Geoff Macartney is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache Brooklyn, and

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

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

    F. Establish Position of VP, Public Policy

       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 and related to public policy,
       including but not limited to maintaining situational awareness of
       regulatory and legislative issues, reactively proposing public policy
       positions to the board for approval, and educating the public sector.

       NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President,
       Public Policy" be and hereby is created, the person holding such
       office to serve at the direction of the President, and to have
       exclusive responsibility of managing the ASF's position related to
       public policy, including but not limited to maintaining situational
       awareness of regulatory and legislative issues, reactively proposing
       public policy positions to the board for approval, and educating the
       public sector.

       BE IT FURTHER RESOLVED, that Dirk-Willem van Gulik be and hereby is
       appointed to the office of Vice President, Public Policy, 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, Public Policy, was
       approved by Unanimous Vote of the directors present.

8. Discussion Items

    A. Budget

        Income
          Total Public Donations                        $130,000
          Total Sponsorship                           $1,825,000
          Conference                                    $150,000
          -----------------------------------------------
          Total Income                                $2,105,000

       Expense
          General & Administrative                      $131,900
                Bank charges                    $6,000
                Board F2F                      $30,000
                General Office                  $5,000
                Legal Counsel Fees             $25,000
                Licenses/Insurance              $2,000
                Office Supplies                 $7,000
                President Discretionary        $50,000
                Shipping                          $900
          Brand Management                              $80,000
                   Trademark Management        $80,000
          ComDev                                        $24,000
                Swag                            $10,000
                Travel Assistance               $10,000
                Misc Stickers                    $4,000
          Conferences                                  $100,000
                ApacheCon NA                   $100,000
          Fundraising                                  $108,000
                HALO Fundraising Admin          $72,000
                HALO Ambassador Services        $36,000
          Infrastructure                             $1,536,000
                Staffing                     $1,425,000
                Credit Card                      $1,200
                Hetzner                         $42,000
                Dinosource (lists.apache)       $24,000
                SSL/DNS Renewals                   $800
                Code Signing                     $2,700
                Bitwarden                        $1,200
                Amazon Web Services                  $0
                Meetups                         $40,000
          Privacy                                        $10,000
          Publicity                                     $210,000
                PR Services / Editorial        $180,000
                Promotional / Giveaway           $5,000
                Press release / distribution     $4,000
                A/V production                   $3,711
                Misc. Subscription svcs          $5,000
                Analytics & Stats (Snoot)       $12,289
          Travel Assistance                              $55,000
                Community Over Code NA          $55,000
          Treasury                                       $31,210
                Accounting Services             $20,160
                Software (bill.com)              $2,100
                Banking Fees                     $5,000
                990 Preparation                  $2,000
                1099 Preparation                    $50
                D&O Insurance                    $1,900
          -----------------------------------------------
          Total Expense                               $2,286,110

       The board has approved this budget.

       @David: Follow up with VP, Legal, on budget

    B. Public Policy Position

       Discussion on the creation of a public policy position.

       Planned workflow/change:

       We proactively plan to listen for legislative/regulatory/standards activity
       that would impact the ASF, our project communities, or our users in
       jurisdictions that the Board prioritizes.

       If VP Public Policy identifies something that does have impact, they will
       highlight that issue and bring it to the board with a proposed position that
       the ASF may want to hold.

       If the Board agrees with the policy position and that the issue will impact
       the ASF the Board may choose to authorize engagement/education.

       We may choose to engage a service that collates activity for us to be aware
       of. (Potential incremental budget ask coming in the future) 

       This will ensure that there is a single owner inside the Foundation that owns
       our engagement on public policy issues.

       Things we won't do: 

       Have non-ASF folks speaking on behalf of the Foundation.

       Proactively engage with the public sector sans board sanction.



9. Review Outstanding Action Items

    * Craig: pursue PMC to elect a new chair
          [ Helix 2023-04-19 ]
          Status: Done. No longer pursuing chair change.

    * Rich: continue with PMC advice around communication tooling
          [ ASF practices in the context of tooling landscape developments 2023-04-19 ]
          Status:

    * Bertrand: Update https://reporter.apache.org/wizard/ with new project states
          [ Board 2023-05-17 ]
          Status: Done, thanks humbedooh for your help!

    * Willem: pursue an Attic resolution
          [ Any23 2023-05-17 ]
          Status: Done. See 7A.

    * Sander: follow up on comments from board
          [ BuildStream 2023-05-17 ]
          Status: Not done. This is an issue that is feedback from the board
                  that I myself signed up for in the project. Let's say that the
                  board f2f and other issues have been eating up my time.

    * Craig: follow up with monthly reporting for next three months
          [ Helix 2023-05-17 ]
          Status: First of three reports received.

    * Rich: follow up with Ozone PMC about committers
          [ Ozone 2023-05-17 ]
          Status: There has been a discussion -
                  https://lists.apache.org/thread/g52mr6fghcrpw6lrmrjpnp3mxok51ws3
                  - but no actual action.

    * Sander: follow up on the issues section for Subversion
          [ Subversion 2023-05-17 ]
          Status:

    * Sander: follow up with security team about CVE data on sites
          [ Superset 2023-05-17 ]
          Status:

10. Unfinished Business

11. New Business

    Informal discussion around updating the PMC Guide page
    <https://github.com/apache/www-site/pull/230>.

12. Announcements

13. Adjournment

    Adjourned at 9:18 UTC

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

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

Covering the period May 2023

* ISSUES FOR THE BOARD

None.


* OPERATIONS

Responded to the following queries, liaising with projects as required:
- Provided advice to an external company on how to best describe their
  employee's contribution to an ASF project.
- Reviewed two proposed t-shirt designs using ASF marks.
- Provided advice to SOLR regarding use of the mark in a third-party domain
  name.
- Provided advice to KAFKA regarding use of the mark in a third-party domain
  name.
- Provided advice to KAFKA regarding use of the mark docker image names.
- Denied three 3rd-party events due to date conflicts. Two requests were then
  escalated to VP Conferences.
- The Brand Management team now has access to the ASF events calendar and will
  add events as they are approved.
- Reminded an event organizer of the need to request permission to use our
  marks for their event.
- Approved one event after dates were shifted to avoid CoC 2023.


* REGISTRATIONS

Provided advice to AIRFLOW regarding registration.

Transfer of the DORIS marks to the ASF is now complete.


* INFRINGEMENTS

Continued to work with counsel regarding a registration that potentially
conflicts with our CASSANDRA mark in Columbia.

The BEAM PMC is addressing a potential infringement with a series of 3rd-party
produce names.

Requested removal of the ASF logo from a 3rd-party site.


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

1) ASF Sponsors:

a --New: we’re in the process of onboarding a new Silver Sponsor.

b --Renewals: one Silver Sponsor has confirmed their renewal. One Gold Sponsor
has confirmed they are unable to renew this year.

c --Payments: 1 --New: no new Sponsor payments were received.

     2a --Renewing: we received payment from two renewing Platinum, two Gold,
     one Silver, and one Bronze Sponsor.

     2b --Incoming: we await payment from one Platinum, one Gold, one Silver,
     and one Bronze Sponsor.

2) Targeted Sponsors: we are exploring additional ways to support the ASF
through the Targeted Sponsorship program. No changes with our Targeted
Sponsors during this timeframe.

3) Sponsor Relations: we met with the OSPO heads of two Sponsor organizations.
We are discussing options to augment Sponsor communications and engagement at
events to better connect with Sponsor contacts who are new to the ASF
community/ecosystem.

4) Event Sponsorship: a handful of ASF Sponsors await the prospectus for the
upcoming Community Over Code Conference(s). We are standing by to support 2023
event sponsorship activities and continue to assist with collections on
several outstanding sponsorship payments from ApacheCon NA (October 2022).

5) Individual Donations and Corporate Giving: we received $2.7K in individual
donations this month.

6) Administrivia: we continue to work with the Treasury and Accounting teams
on resolving a few remaining Sponsor invoicing issues.


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

Foundation Comms
* Announced SeaTunnel as TLP via the ASF blog, wire, and social channels.
* Began stakeholder outreach for FY 2023 Annual Report content.
* Provided feedback on the academic diversity study.

Proactive Storytelling
* Continued #FirstContributions Campaign: new blog post[1] and social cards.
* Began email outreach to stakeholders for story platform[2]; scheduling
  interviews.

Branding Project
* Reviewed initial proposals and met with several vendors. We have either not
  had a good fit, not been able to afford them, or (in the case of one vendor)
  been rejected as a customer because we would not be changing the Apache name
  at this time.
* Steering Committee: No activity yet, because until we get a vendor, there
  isn't much to discuss. This is because nearly every vendor has a variation
  of a guided discussion about re-brand goals and objectives, and I am
  conservatively waiting to have that conversation with a selected vendor all
  at the same time. If the delay continues, though, I plan to start the
  discussion with the committee before the end of June.
* BKP attended the Board F2F to discuss how the general process will go, and
  have a dialog to ensure re-branding goals are aligned. Questions about
  re-naming and project branding, currently outside the remit of M&P and the
  steering committee, were discussed.

* Continued to monitor and counsel on reactive communications around ASF
  branding.

Annual Report M&P would love to get this posted in July, but we are missing
reports from:
* Rich Bowen (he's working on his)
* Myrle Krantz
* Craig McClanahan
* David Nalley
* Bob Paulin
* Katia Rojas

Website
* Continued updating multiple pages in preparation for navigation/restructure.
* Draft[3] available to peruse now

Social Media Posts In May, we continued to drive community engagement across
social media, sharing:
* 56 Tweets + 16 LinkedIn posts covering ASF, project, and industry news.
  Posts included project releases, Community Over Code Asia promotion (call
  for speakers), case studies and how-to articles.
* Continued to react to select posts in which we were mentioned or tagged.

Social Analysis ASF social SOV amongst other large foundations continues to
float around the single digits at 6.9% with a net negative social sentiment
this month of 18.2%.
* May 27.3% positive vs 45.5% negative
* YTD average : 16% positive vs 18% negative (2% net negative)

Social Engagement Stats (Twitter + LinkedIn)
* Total engagement: 6,917 (down 27% from April)
* Total clicks: 3,052 (down 36% from April)
* Click to engagement ratio: 44% (down 6% from April)
* New followers: 821 (up 2% from April)


[1] https://news.apache.org/foundation/entry/3-ways-to-contribute-to-open-source-that-dont-involve-coding
[2] https://docs.google.com/document/d/1DFXrtkI0Xw3aagLbDDobYMLMFq0hSTsIAx37TfUIvV4/edit?usp=sharing
[3] https://www-paulau.staged.apache.org/


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

Highlights
==========
- blogs.apache.org has been turned off, with active blogs moved to
  selfserve by the projects, and redirects to their new location.
  Blogs not migrated remain active, in readonly form.

General Activity
================
- Continued work on a keycloak proof-of-concept to provide an OIDC
  (and OAuth) endpoint to services. It will also provide MFA on top of
  our LDAP accounts.
- Moving along an ansible test for secrets management, as a test of
  Ansible rollout and replacement for EYAML in our Puppet configs.
- Jira account management has been revised towards a more self-serve
  approach, and to simplify the workflow for a PMC. This includes a
  new "reactivate" feature in case Infra deactivates an account for
  idle-ness, and the contributor returns.
- Ephemeral GitHub Action nodes in Azure are up and running. This will
  allow projects to choose specific node types for their GHA workflows
  (eg. ARM or large memory nodes).
- blogs.apache.org has been made readonly. Projects with active blogs
  have moved to a selfserve approach (via asf.yaml). For projects that
  have migrated, redirects are in place on blogs.a.o. Eventually, an
  aggregator will be deployed for all projects' blogs.
- Gradle moves along, and more projects are getting their builds
  looped into the service.
- Work on migrating BitWarden accounts, so that we can turn off
  LastPass when our contract ends in August.


-----------------------------------------
Attachment 5: Report from the VP of Conferences  [Rich Bowen]

Planning for Community Over Code, North America, 2023, proceeds. The sponsor
prospectus is now available. The CFP is still open. Details are available at
https://communityovercode.org/

Planning for Community Over Code, Asia, 2023, also proceeds. Details are
available at https://apachecon.com/acasia2023/

And finally, planning for Community Over Code, Europe, 2024, is under way.
Details for that are still primarily on the planners@apachecon.com mailing
list.

Due to the late publication of dates for the two 2023 events, we found
ourselves in conflict with a number of our PMC-produced events. Exceptions
have been granted for several of these, which are, unfortunately, very close
in both time and location to our main events. VP Conferences is making a much
more concerted effort to stay up to date on event branding requests on the
trademarks@ list, and VP Trademarks has graciously been adding those events to
the list on events.apache.org, which is now much more accurate that ever in
the past


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

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

1. Community Over Code Beijing China 
2. Community Over Code Halifax Canada

Both above events being fully supported by TAC and applications are now open
for both.


TAC App
=======

TAC app is currently open supporting 2 events.

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

None Currently.


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

Still keeping an eye out for other smaller events to support. We are keen to
hear about projects events.

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

Some list activity, a call for more volunteers has so far gone unanswered, we
may reach out to the membership as we have in the past.

Membership
==========

No changes to the membership this month
===


-----------------------------------------
Attachment 7: Report from the VP of Diversity and Inclusion  [Katia Rojas]


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

# General

No issues requiring board attention at this time.

## First online meeting on 28 Jun 2023

One of the roles of the DPO is to educate. I am trying a new format in the
form of an online meeting to respond to all questions committers might have
around their projects, websites or just in general.

# Recommendations

## Add subscription information to every new subscriber of a mailing list

Tracked as: https://issues.apache.org/jira/browse/INFRA-23011?filter=-2
(open since 18/Mar/22)

Adding this kind of information will tell users how mailing lists work and we
can act based on user consent.

## Access to ICLAs should be more restrictive
This task is currently work in progress.


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


-----------------------------------------
Attachment 10: 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
22 outstanding issues.

Henri Yandell prepared the first draft of formal guidance for ASF contributors
on using generative AI code assist tools (e.g. GitHub Co-pilot, etc.). Next
step is to settle it with the legal committee and then members@.

There appears to be some level of disagreement and the need for further
clarification around split of Legal responsibilities between the office of the
President of the ASF and the Legal Committee/VP Legal. See public emails
discussion threads on legal-discuss@ and, likely, on board@ soon. Roman and
David are scheduled to spend some time 1-1 to figure out the proposal here.


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

- An older Tomcat JMX issue, CVE-2016-8735, was selected to be included in the
  CISA Known Exploited Vulnerabilities (KEV) catalog.

- We have engaged with the Trivy SBOM/security scanner project to discuss how
  we can help reduce noise and make security reports more accurate, possibly
  using VEX. This is challenging because it requires the scanner to build not
  just a list, but the graph of dependencies.

- We are working with NIST/NVD to improve the consistency of CPE's, and have
  stopped distinguishing between 'incubating' and 'regular' Apache projects in
  the CPE, to avoid missing associations.

- The Airflow project has formed a security@airflow.apache.org group, which
  hopefully will help clear their considerable backlog.

- We continue working with projects to publish 'security model' information on
  their websites, this month PDFBox.

- We have started exploring creating a single place to find security contact
  information and advisories for all Apache projects on
  https://security.apache.org and also moved our blog there

Stats for May 2023:

        22 [license confusion]
        11 [support request/question not security notification]]
        2 [report/question relating to dependencies]

Security reports: 59 (last months: 73, 64, 71)

        8 ['superset']
        6 ['vince', 'website or other infrastructure']
        4 ['rocketmq']
        3 ['airflow', 'inlong', 'tomcat']
        2 ['commons', 'dolphinscheduler']
        1 ['activemq', 'apisix', 'atlas', 'codeql', 'cpe',
        'fedramp', 'flink', 'hadoop', 'hive', 'ibb', 'ignite', 'infra',
        'nifi', 'openoffice', 'poi', 'ranger', 'shiro', 'solr', 'spark',
        'storm', 'streampark', 'trafficserver']

     In total, as of 1 June 2023, we're tracking 165 (last months: 173, 153)
     open issues across 56 projects, median age 76 days
     (last months: 69, 78). 46 of those issues have CVE names assigned.

     12 (last month: 7) of these issues, across 6 projects, are older than 365
     days.


-----------------------------------------
Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins]


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

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

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

## Membership Data:
Apache Airflow was founded 2018-12-19 (4 years ago)
There are currently 53 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Brent Bovenzi was added to the PMC on 2023-03-15
- Hussein Awala was added as committer on 2023-04-12
- Pankaj Singh was added as committer on 2023-06-13

## Project Activity:
* We reached some milestones in the last quarters that indicate strong
  community and healthy activity: 30K stars on GitHub, 2500 contributors who
  contributed, 20K commits overall.
* We released the 2.6 feature release - as planned. It included new
  interesting features - notification support that seems to be anecdotally
  (and somewhat surprisingly) highly valued and prised by our users,
   improvements to Grid View, solving a long time “tasks stuck in Queue”
   problems and making Async logs available in in the integrated logging,
   continuous timetable
* We are steadily releasing Airflow core patchlevel/bugfix releases (with
  roughly monthly cadence) and gearing up to Airflow 2.7 feature release in
  the coming month. The 2.7 will contain AIP-52 (setup/teardown) and if we
  manage to implement it also AIP-44 (internal API), improved UI, and a number
  of other features we work on.
* We are also steadily releasing 80+ provider packages that extend Airflow
  capabilities and allow for integration with external services/software with
  roughly bi-weekly cadence.
* The important events in the last quarter was getting rid of Python 3.7
  support (Python 3.7 reaches end-of-life status in June 2023 and many of our
  dependencies already dropped support for it. We proposed, discussed, voted
  and updated our policies, deciding on a bit more relaxed timing for dropping
  the support before the actual end-of-life date (we already dropped support
  in `main` which will apply to the upcoming Airflow 2.7 version).
* We’ve implemented a series of optimizations and stabilizations of our CI
  builds, leading to lower build time utilization as well as faster feedback
  and more stability for committers and contributors. We have not measured the
  overall impact but we can talk roughly about 20-30% improvements in feedback
  time, 20-30% improvements in build time utilization and (hopefully as a
  result) dramatic improvements in stability of the builds and decreasing
  flakiness of the CI. We are looking forward to future improvements
  especially coming from some of the Github releases (K8S Controller they
  released and ASF Infrastructure options like self-hosted runners).
* Big news (voted PR of the month) was adding Python 3.11 support. We worked
  closely with our dependencies (for example Apache Beam, Papermill), and
  stakeholders of libraries (Google) that held us back from supporting Python
  3.11 (Released in October 2023) and finally we managed to bring Python 3.11
  support to `main` - this opened up for a huge bump in versions of our
  dependencies that were held back so far, increasing the security of the
  supply chain of ours. The upcoming 2.6.2 release already supports Python
  3.11. Also we worked out, discussed and voted on policies for suspending
  providers that hold us back and we applied it to “Yandex” provider (we
  informed Yandex library maintainers that we are suspending new releases
  until they fix their dependency issues). The policy is documented here:
  https://github. 
  com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers
* Our provider released bumped minimum version of Airflow supported to 2.4
  following our policies which are part of the effort of incentivising our
  users to upgrade to newer versions of Airlfow quicker
  https://github.com/apache/airflow/blob/main/PROVID 
  ERS.rst#minimum-supported-version-of-airflow-for-community-managed-providers
* There is an on-going work including efforts led by the stakeholders and
  community members that have not been as active before: Open Telemetry
  integration (AIP-49), Open Lineage integration (AIP-53), External
  Authentication and Authorisation framework (AIP-56 - part of Multi-Tenancy),
  Automatic Setup/Teardown (AIP-52, Airflow Internal API (AIP-44 part of
  Multi-Tenancy), Removing Executor Coupling (AIP-51). Most of the efforts
  have a common theme of making Airflow more of an extensible workflow
  platform than just an end-user solution.
* Since we got substantially more security issues reported to us by security
  researchers - result of Airflow being part of Hacker One bounty, we are in
  the process of improving and redefining a process for handling security
  issues. This process is somewhat experimental (we work closely with the ASF
  security team) as it involves not only PMC members and committers, but also
  other stakeholders and external security researchers who are not (yet)
  committers. This is somewhat at odds with the established policy of who
  should be on the security team but we got approval of VP Security of the ASF
  for the process and we are working on putting that into practice to evaluate
  if that can help in handling the reports in a more timely fashion, at the
  same time allowing external stakeholders to participate in the process
  following very well defined process. The process has been discussed, voted
  and applied already, we are working on making a routine. The security team
  is established, and working on the issues, we are going to intensify the
  work and discussions there. Part of the discussion is also general
  improvement in the process including adding SBOM exports and generally
  improving the way how we communicate security issues to our users. More
  information about the process we are following is here:
  https://github.com/apach 
  e/airflow/blob/main/.github/SECURITY.rst#handling-security-issues-in-airflow

## Community Health:
* We have regular monthly newsletter and voting on PR of the month that
  regularly gets somewhat enthusiastic reactions from the community We have a
  number of discussion redirected from PR/Slack chats to the devlist, we
  actively redirect “substantial” discussions requiring architectural changes
  to devlist to make sure we have an inclusive community
* The rules on what we consider breaking changes that we started to
  communicate with the upcoming 2.6 release already had effect and helped to
  facilitate some discussion on “what is breaking” - with
  3rd-parties/downstream projects that use Airflow (external Helm Chart).
  Hopefully they will make expectations better aligned.
* We have more people publishing in our medium “Airflow” Publication
  https://medium.com/apache-airflow that seems to pick up the steam. We have
  13 new blog posts published by authors from all-over-the community
  (including authors from various stakeholders) since March 21 (2 months). We
  also have almost 800 followers. This is a significant uptick (there are in
  total 34 articles since Feb 2021).
* We are reaching 2500 contributors on GitHub this month (2495 currently so
  just 16 more contributors left). We continue to increase our lead over Spark
  which is the second biggest project of Apache Software Foundation on GitHub
  regarding the number of contributors . We see continuous interest in new
  contributors joining Airflow

## Events

The community is getting ready for Airflow Summit 2023 that is happening
September 19-21 in Toronto, Canda. We are already past the selection of 80% of
the content and the Early Birds ticket ended on 10th of June. We have a
substantial audience already who purchased tickets. We decided to give free
passes to all the committers and we have a healthy set of sponsors and we are
increasing our promotional efforts in cooperation with Software Guru who are
producers of the event. The event is organized by representatives of the
biggest stakeholders (Amazon, Google, Astronomer), PMC members and other
community members).

We had a number of local Airflow Meetups: London, New York, Paris, Charlotte,
NC, New York and others.


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

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

## Project Status:
- Ongoing, with low activity
- Issues for the board: none.

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

Community changes, past quarter:
- No new PMC members. Last addition was Guillermo Cruz on 2021-11-09.
- No new committers. Last addition was Guillermo Cruz on 2021-11-09.

## Project Activity:
- support python 3.10 and 3.11
- fixed more deprecation warnings
- library upgrades
- minor other changes

## Community Health:
- Last release was 1.14.0 on 2022-09-23
- Good maintenance and support of the codebase continues
- But no interesting development or discussion lately


-----------------------------------------
Attachment C: Report from the Apache Ambari Project  [Roman Shaposhnik]

## Description:
The mission of Apache Ambari is the creation and maintenance of software
related to Hadoop cluster management.

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

## Membership Data:
Apache Ambari was founded 2022-06-15. There are currently 19 committers and 16
PMC members in this project. The Committer-to-PMC ratio is roughly 5:4.

Community changes, past quarter:
- Yu Hou was added as committer on 2023-03-04

## Project Activity:
- ambari-metrics-3.0.0 was released on 2023-03-13.
- ambari-2.7.7 was released on 2022-12-11.

## Community Health:
Ambari 2.8.0 release vote is still in progress. Community is looking into a
few low-risk CVEs reported over the past months.


-----------------------------------------
Attachment D: Report from the Apache Ant Project  [Jan Materne]

## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build 
system and related software components. 
It consists of 3 main projects:
 - Ant - core and libraries (AntLibs)
 - Ivy - Ant based dependency manager
 - IvyDE - Eclipse plugin to integrate Ivy into Eclipse
Additionally Ant provides several extensions to Ant (antlibs).

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

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

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

## Project Activity:
Recent releases:

    Ant 1.10.13 was released on 2023-01-10.
    Ant 1.9.16 was released on 2021-07-13.
    AntUnit 1.4.1 was released on 2021-07-07.
    Ivy 2.5.1 was released on 2022-11-04.    

## Community Health:
For Ant and Ivy web basically are in "maintenance mode". There isn't much
development. For IvyDE we lack the knowledge of building Eclipse plugins on
actual Eclipse versions.

But it get's harder to get enough votes for releases as most of the PMC
members are more involved in other projects.


-----------------------------------------
Attachment E: Report from the Apache Any23 Project  [Lewis John McGibbney]


-----------------------------------------
Attachment F: Report from the Apache Archiva Project  [Olivier Lamy]

## Description:
The mission of Archiva is the creation and maintenance of software related to 
Build Artifact Repository Manager

## Project Status:
Current project status: Not much happening on the code, 
but at least 3 PMC members ready to engage if needed
Issues for the board: None

## Membership Data:
Apache Archiva was founded 2008-03-19 (15 years ago)
There are currently 21 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 7:3.

Community changes, past quarter:
- No new PMC members. Last addition was Martin Stockhammer on 2017-04-10.
- No new committers. Last addition was Martin Schreier on 2016-09-22.

## Project Activity:
Last release 2.1.10 20th March 2023.
Low activity focused on security.

## Community Health:
Not much activity except some user bug reports.
This is explained by no much new development currently


-----------------------------------------
Attachment G: 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: There are no issues requiring board attention.

## Membership Data:
Apache Atlas was founded 2017-06-20 (6 years ago)
There are currently 48 committers and 32 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 Ashutosh Mestry on 2019-04-16.
- One new committers. Last addition was Umesh Padashetty on 2023-06-13.

## Project Activity:
- released Python client 0.0.14
- updated versions of Storm, JanusGraph, TinkerPop
- added APIs to download search results to file; updated UI to download results
- Hive hook fix in handling of notifications having an entity in both inputs
- support building Atlas using JDK versions higher than 8
- UI updates to remove unused libraries from build package

## Community Health:
- dev@atlas.apache.org had a 46% increase in traffic in the past quarter (226
  emails compared to 154)
- 29 issues opened in JIRA, past quarter (61% increase)
- 11 issues closed in JIRA, past quarter (no change)
- 33 commits in the past quarter (6% increase)
- 11 code contributors in the past quarter (57% increase)

## Most Recent releases:
2.3.0 was released on 2022-12-06
2.2.0 was released on 2021-08-17
2.1.0 was released on 2020-07-15
0.8.4 was released on 2019-06-21


-----------------------------------------
Attachment H: 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 (22 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.7.1 was released on July 30, 2017.
 - Axis 2/C 1.6 was released on April 20, 2009.
 - Axis 1.4 was last released in 2006.

## Health report:

This past quarter a lot of progress was made adapting Apache Axiom
SNAPSHOT release changes into Axis2. 

Work has also started on AXIOM-506, a requirement for moving Axis2 off of 
the old javax packages and into new jakarta packages. See AXIS2-6051.

Separately, a major refactoring effort of Apache Rampart - 
an implementation of WS-Security standards - has resulted 
in commits upgrading OpenSAML from 2.x to 4.3.0, and Apache WS-WSS4J 
from 1.6 to 3.0.0. See RAMPART-449.

Axis2 C PMC member Bill Blough continues to help users on the mailing list
and he also participates in release votes.

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

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


-----------------------------------------
Attachment I: Report from the Apache Bahir Project  [João Boto]

## Description:
Apache Bahir provides extensions to distributed analytic platforms such as
Apache Spark and Apache Flink. Currently, Bahir provides extensions to
multiple distributed analytic platforms, extending their reach with a
diversity of streaming connectors and SQL data sources.

## Project Status:
Current project status: At risk: Not enough active PMC members (roll call made)
Issues for the board: Advice as to how to proceed in this situation

## Membership Data:
Apache Bahir was founded 2016-05-18 (7 years ago)
There are currently 40 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- No new PMC members. Last addition was João Boto on 2020-07-10.
- No new committers. Last addition was Łukasz Antoniak on 2019-01-21.

## Project Activity:
### Spark extensions:
No movement around spark connector, only small discussion around
https://github.com/apache/bahir/pull/101

### Flink extensions:
Some movement around some connectors with PRs open and merged 
- Redis connector: PRs open and merged to add new commands
- Kudu connector: PRs open and merged to fix functionality 
  and new features requested (BAHIR-322)
- Updated flink to last version 1.17

## Community Health:
We don't have enough active PMC members to new version (asked several times).
We also have a pending email to the list of users commenting on the status 
of the project and that if there is no interest in helping to maintain the
project we will consider going for the artic.


-----------------------------------------
Attachment J: 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 (6 years ago)
There are currently 91 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:2.

Community changes, past quarter:
- No new PMC members. Last addition was Jan Lukavský on 2023-02-14.
- Anand Inguva was added as committer on 2023-04-21.
- Damon Douglas was added as committer on 2023-04-21.

## Project Activity:

- 2.48.0 was released on 2023-06-03.
- 2.47.0 was released on 2023-05-10.

Highlights of community activities:

- Beam Summit 2023 (https://beamsummit.org/) was just held June 13-15. Summit
  reached 500+ registrations. This is the 6th iteration of this annual
  community-organized summit.
- Interactive Beam Playground updated with lots of new features
  (https://lists.apache.org/thread/15phr0h5q007pjgfotwqcvdr7hyotks1).
- Google Cloud Skills Boost launched a Beam "quest"
  (https://www.cloudskillsboost.google/quests/310), paid educational content
   where users earn a completion "badge".

Some technical highlights relevant to community development:

- Python 3.11 support added
- Flink 1.16.x support added
- The Go SDK is now very nearly at feature parity with Python and Java. The
  gaps are small enough that they are more than compensated for by the
  qualitative differences between the SDKs, and the existing gaps and bugs in
  each. It has arrived!
- "Experimental" annotation cleanup: the annotation and concept have been
   removed from Beam to avoid the misperception of code as "not ready". They
   were there to signal that something might change or disappear, but in
   practice we rarely did so and we almost always neglected to "graduate"
   features from this status. We will just make case-by-case judgment.
- A new local Beam runner called the "Prism Runner" is authored in Go and
  poised to become the definitive local portable runner, serving as a proper
  reference for the Beam model. Rapid developments in Beam have resulted in a
  major gap in this area, with no runner supporting every corner of the model
  so users could reliably test their work prior to running on a cloud service.

## Community Health:

Traffic on various communication channels is roughly stable. The number and
variety of attendees at the Beam Summit shows a very healthy diversity of
stakeholders in Beam and interest in the project's development. There were
many talks of unexpected and interesting work that took place outside the
project's communication channels and code repository. Creating an ecosystem
bigger than itself is a good sign, but also some of these may be opportunities
to invite work to merge into Beam itself to grow committers and PMC members
from those stakeholders.


-----------------------------------------
Attachment K: Report from the Apache Bigtop Project  [Yuqi Gu]

## 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:
Ongoing: 3.2.1 patch release is currently underway.

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

## Membership Data:
Apache Bigtop was founded 2012-09-19 (11 years ago)
There are currently 42 committers and 29 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 Masatake Iwasaki on 2021-03-11.
- Zhiguo Wu was added as committer on 2023-05-17

## Project Activity:
- We are working on the 3.2.1 patch release to address security issues fixed
by Hadoop 3.3.5.
- We defined the Bigtop-3.3 release scope on BIGTOP-3909 which will include:
    1.Support New components like Ranger debian, bigtop-select (for Ambari).
    2.Adapt Bigtop Mpack to new Ambari-2.8.
    3.Dropping old supported distros and only support the latest LTS.
    4.Sub components upgrading.
-In addition, we had a brainstorming discussion about openEuler support and
the related work has been kicked off:
https://github.com/apache/bigtop/pulls?q=is%3Apr+is%3Aopen++openEuler 

## Community Health:
- Community health is good. Several contributors were actively fixing issues
and developing the 3.2.1 release. The number of the commits was a bit
decreased, but all other metrics were positive and reflect our active
development and interactions.
- 10 code contributors in the past quarter (42% increase)
- 24 PRs opened on GitHub, past quarter (50% increase)
- 20 PRs closed on GitHub, past quarter (122% increase)
- 24 commits in the past quarter (-17% decrease)
- 33 issues opened in JIRA, past quarter (57% increase)
- 19 issues closed in JIRA, past quarter (90% increase)
- dev@bigtop.apache.org had a 105% increase in traffic in the past quarter
(246 emails compared to 120)


-----------------------------------------
Attachment L: Report from the Apache Bloodhound Project  [Gary Martin]


-----------------------------------------
Attachment M: 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 (11 years ago)
There are currently 16 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17.

## Project Activity:
Recent activity has been limited to responding to automated dependency
upgrade suggestions.

## Community Health:
No changes in community health, which is to say our community remains
small and "reactive." We do continue to have a sufficient number of PMC members
who will perform required tasks out of duty if nothing else. As part of the
suite of implementations of Java Community Specifications as implemented at
the ASF, we see BVal as being essential and thus plan to maintain it in dormant
state indefinitely.


-----------------------------------------
Attachment N: 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:
Project status: Ongoing with high activity
Issues: There are no issues requiring board attention at this time.

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

Community changes, past quarter:
- Nicolas Filotto was added to the PMC on 2023-04-05
- Christoph Deppisch was added as committer on 2023-05-25
- Marcin Grzejszczak was added as committer on 2023-04-20

## Project Activity:
- We released Camel 3.14.8
- We released Camel 3.18.6
- We released Camel 3.18.7
- We released Camel 3.20.3
- We released Camel 3.20.4
- We released Camel 3.20.5
- We released Camel 4.0.0-M2
- We released Camel 4.0.0-M3
- 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.
- We are near releasing the first release candidate for Camel 4.0.0, it will
  be done in this month and we plan to complete 4.0.0 release in September.
- We are continuing release 3.18.x LTS release train and we are in the process
  of releasing the next patch release.
- We started the release train for 3.20.x LTS, and we are already at the fifth
  patch release.
- We are still supporting Camel 3.14.x, an LTS train, but it's going EOL, so
  there will be one last release.
- For Camel K we are working on releasing the first patch release for 1.12.x,
  but the focus is on the 2.x work. We are focusing on giving to the community
  a new experience.
- For Camel-Kamelets releases
- We released Camel Kameletes 0.9.4
- We released Camel Kameletes 3.20.3
- We released Camel Kameletes 3.20.4
- We released Camel Kameletes 3.20.5
- We released Camel Kamelets 4.0.0-M2
- We released Camel Kamelets 4.0.0-M3
- We are improving the Camel-K experience and Camel Kamelets is already
  looking at Camel 4
- Camel-Kamelets is not only related to camel k anymore so it could be used
  with all the Camel's flavours
- The Camel-Quarkus work is going ahead following the main camel releases with
  multiple releases
- We released Camel-quarkus 2.13.3
- We released Camel-quarkus 3.0.0-M1
- We released Camel-quarkus 3.0.0-M2
- Camel-Kameleon and Camel-Karavan are improving and more and more
  contributors are starting to help. We are improving the projects by
  supporting new features and aligning with LTS releases 3.20.x as in the last
  report
- Camel Kafka Connector release based on Camel 3.20.1 has been released.
- We are supporting Camel Kafka Connector aligning it to the Camel Core LTS
  Releases 3.20.x and we released camel-kafka-connector 3.20.3
- Generally speaking we are working on supporting Camel 4 in all the runtimes
  provided and this is taking a lot of effort.

## Community Health:
- 265 issues opened in JIRA, past quarter (25% decrease) and 284 issues closed
  in JIRA, past quarter (3% decrease): We are in a stabilization phase for
  Camel 3.x and the LTS are more or less stable. Mostly new issues are about
  Camel 4.x, but since we are closing down the work for releasing Camel 4.0.0
  there is less new issues opened.
- 211 issues opened on GitHub, past quarter (13% decrease) and 203 issues
  closed on GitHub, past quarter (4% decrease): Since we are working on
  releasing Camel 4.0.0 some of the subprojects using gh issues are seeing
  less focused work, Camel is using JIRA for tracking the work
- 4648 commits in the past quarter (3% increase) and 120 code contributors in
  the past quarter (no change): More or less we are stable. The camel core
  team is focusing on Camel 4.x. We saw sporadic contributions from new
  contributors.
- 1362 PRs opened on GitHub, past quarter (7% increase) and 1366 PRs closed on
  GitHub, past quarter (7% increase): on some of the subprojects the activity
  is slowing down for stabilization reasons, we also cleaned up some of the
  subprojects gh PR and there was a lot of work on Camel-Kamelets from this
  pov
- dev@camel.apache.org had a 32% decrease in traffic in the past quarter (304
  emails compared to 441): This is mostly because the work done on Camel 4
  side is about moving to support Jakarta, there was some discussions but
  mostly about releasing.
- issues@camel.apache.org had a 0% increase in traffic in the past quarter
  (1901 emails compared to 1891): We are more or less stable here. There was
  activity in JIRA mostly for Camel 4 work and cleaning up.
- users@camel.apache.org had a 26% decrease in traffic in the past quarter
  (263 emails compared to 352): The activity is less because of the work on
  Camel 4 but also because users is asking and discussing on the provided
  Zulip chat


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

# Apache Cayenne Board Report, June 2023

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

## Project Status

### Project State

Ongoing

### Issues for Board

On the December Board Report, Rich Bowen commented:
>> 4 years since adding a committer, and 5 since adding a PMC
>> member, is concerning for the long-term sustainability of
>> the project. Have you recently had a hard look to see what
>> new contributors might be invited to join the project
>> community?

Cayenne reported on March Board Report:
> Cayenne's core committers and PMC are rather stable. That said, there
> is an individual who has submitted several PRs and bug reports for rather
> non-trivial issues and we are planning to invite him to become a committer
> soon. Hopefully he will accept a role in the project.

This still needs to be addressed.

## Membership Data

Apache Cayenne was founded 2006-12-19 (16 years ago).
There are currently 23 committers and 9 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 Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Arseni Bulatski on 2018-12-10.

## Project Activity

Cayenne 4.2 released:

https://cayenne.apache.org/2023/05/cayenne-42-final-released/

Development is shifting to 5.0 (unreleased).

Prior versions 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 (unreleased)
  - Features being defined.

### Releases

- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2 on 2023-05-25.

## Community Health

Cayenne is healthy.

JIRA, Git, and user mailing list activity were lower as 4.2 stabilized
prior to release. Developer mailing list slightly higher due to 4.2
being released and 5.0 feature set discussions.

Questions on the user mailing list are actively addressed.


-----------------------------------------
Attachment P: Report from the Apache CloudStack Project  [Rohit Yadav]

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

No issues to report.

## Membership Data:

- There are currently 129 committers and 52 PMC members in this project.
- The Committer-to-PMC ratio is roughly 9:4.

PMC changes:
- Most recently added PMC member: Ivet Petrova was added to the PMC on
2023-02-10.

Committer base changes:
- There are no new committers since the last report.
- Most recently added committers: Ivet Petrova and Slavka Peleva, both
added as committers on 18 December 2021.

## Project Activity:

- The Apache CloudStack project released the current LTS version
4.18.0.0 on 20th March 2023.

- The previous LTS version received an updated release to 4.17.2.0 on
16th December, 2022.

- Apache Cloudstack 4.18.1 and 4.19.0 are the next releases the
community is working towards, with a tentative release timeline
discussed during Q3 and Q4 of 2023.

- The PMC is actively discussing new PMC Candidates and new
Committers. There are no new PMC members or committers added since the
previous report.

- The Apache CloudStack old Roller based blog has been successfully
migrated to a static-site generator based system published at
https://cloudstack.apache.org/blog.

- The project is now working to migrate to a new website that uses the
same static-site generator as the blog. This is work in progress and
shared with the community for feedback, review and testing. The
staging site is accessible at https://cloudstack.staged.apache.org

- The annual community organised CloudStack Collaboration conference
has been announced with registration and CFP open. The two-day hybrid
event will be taking place on November 23-24th in Paris and online.
https://www.cloudstackcollab.org

## Community Health:

Apropos of the activity report; the project is considered healthy.

- According to the apache statistics, the project achieved the
Community Health Score (Chi): 7.15 (Healthy)

- Commit activity:
  341 commits in the past quarter (7% increase)
  31 code contributors in the past quarter (-24% change)
- GitHub PR activity:
  171 PRs opened on GitHub, past quarter (-28% change)
  160 PRs closed on GitHub, past quarter (-33% change)
- GitHub issues:
  149 issues opened on GitHub, past quarter (-3% change)
  116 issues closed on GitHub, past quarter (-9% change)

- Mailing lists Statistics:
-- dev@cloudstack.apache.org had a 9% increase in traffic in the past
quarter (609 emails compared to 554):
-- issues@cloudstack.apache.org had a 2800% increase in traffic in the
past quarter (116 emails compared to 4):
-- marketing@cloudstack.apache.org had a 33% increase in traffic in
the past quarter (36 emails compared to 27):
-- users@cloudstack.apache.org had a 0% increase in traffic in the
past quarter (630 emails compared to 624):

## Releases:

Latest:
- 4.18.0.0 was released on 20th March 2023 -- EOL 1st Oct 2024.

Reaching EOL:
- 4.17.2.0 was released on 16th December 2022 -- EOL 1st Jan 2024.
- 4.17.1.0 was released on 26th September 2022 -- EOL 1st Jan 2024.
- 4.17.0.1 was released on 18th July 2022 -- EOL 1st Jan 2024.
- 4.17.0.0 was released on 7th June 2022 -- EOL 1st Jan 2024.


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

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

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

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

Community changes, past quarter:
- No new PMC members. Last addition was Matt Juntunen on 2021-06-25.
- No new committers. Last addition was Claude Warren on 2022-02-01.

## Project Activity:
Our releases this quarter are:
- IO-2.13.0 was released on 2023-06-07.
- PARENT-58 was released on 2023-05-23.
- IO-2.12.0 was released on 2023-05-16.
- DAEMON-1.3.4 was released on 2023-05-12.
- PARENT-57 was released on 2023-04-26.
- CONFIGUATION-2.9.0 was released on 2023-03-29.
- JEXL-3.3 was released on 2023-03-27.
- COMPRESS-1.23.0 was released on 2023-03-22.

## Community Health:
The Commons project is stable, we are releasing components reasonably
regularly. We are handling a steady and manageable flow of interactions on the
dev, user, and security mailing lists, as well as Jira, and GitHub. GitHub
continues to prove itself enormously valuable as a continuous integration and
pull request resource. Most of the raw statistics except Jira for the
projects are down but not a concern.


-----------------------------------------
Attachment R: Report from the Apache Cordova Project  [Jesse MacFadyen]

## Status report for the Apache Cordova project - June 2023

## Description:
 - A platform for building native mobile applications using HTML, CSS and
   JavaScript.

## Activity

Current work continues to be keeping up with changes to iOS and Android, our
most used platforms, and updating plugins.

Github discussions has become how our community supports each other.

Committers made some large releases this quarter with major version updates to
cordova-android, the cli and cordova-lib.

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

## Health report:

Our status dashboard at http://status.cordova.io remain mostly all green -
failures are usually due to external service issues that do device testing.
Our nightly builds are still extremely stable.

ASF Project Statistics gives the project a Community Health Score (Chi): 4.7
Healthy

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

Our discussion area is live at https://github.com/apache/cordova/discussions
and activity has been shifting there and away from our #slack community.


## 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-05.
- No new committers. Last addition was Pieter Van Poyer on 2021-04-05.

## Releases:

- cordova-android@12.0.0 was released on 2023-05-23.
- cordova-cli@12.0.0 was released on 2023-05-23.
- cordova-lib@12.0.1 was released on 2023-05-23.
- cordova-browser@7.0.0 was released on 2023-05-16.
- cordova-create@5.0.0 was released on 2023-05-16.
- cordova-lib@12.0.0 was released on 2023-05-16.
- cordova-ios@6.3.0 was released on 2023-04-17.
- cordova-fetch@4.0.0 was released on 2023-04-13.


## Github activity:

Issue close rate of 197%

112 issues opened on GitHub, past quarter (8% increase) 221 issues closed on
GitHub, past quarter (-8% change)

PR close rate of 121%

145 PRs opened on GitHub, past quarter (10% increase) 175 PRs closed on
GitHub, past quarter (25% increase)

Commits

196 commits in the past quarter (33% increase) 22 code contributors in the
past quarter (46% increase)


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

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

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

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

Community changes, past quarter:
- Ronny Berndt was added to the PMC on 2023-03-04
- No new committers. Last addition was Ronny Berndt on 2022-04-08.

## Project Activity:

- Next feature release (3.4.0) planning started, major new feature:
 - new modern Lucene integration for full-text and multi-facet search
- New JS evaluation infrastructure (first attempt to refactor this core
  part of CouchDB. Feature complete, but some build issues remaining.
  Slated for 3.5.0 unless miraculously ready in time for 3.4.0.
- slow but steady progress of other keystone features for future 3.x
  releases.

## Community Health:
- the community engagement is steady as usual with the expected uptick
  around new releases.


-----------------------------------------
Attachment T: 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 (10 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 (5.x.x)
- Committee migrated the code repo to git
- Committee migrating the website repo to git
- Last release was 4.0.0.1 patch on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
- 3.2.2 was released on May 30 2015

## Community Health:
There has been an decrease in the dev and user email traffic this
quarter.  This quarter is inline with the normal traffic since there was 
an uptick last quarter with a discussion around the new release.
dev@ctakes.apache.org had a 75% decrease in traffic in the past quarter
(15 emails compared to 58)
user@ctakes.apache.org had a 50% decrease in traffic in the past quarter
(3 emails compared to 6)


-----------------------------------------
Attachment U: 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: Issues for the board: none.

## Membership Data:
Apache Curator was founded 2013-09-18 (10 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:
- Kezhu Wang was added to the PMC on 2023-03-25
- Kezhu Wang was added as committer on 2023-03-24

## Project Activity:
Recent releases:

5.5.0 was released on 2023-04-28.
5.4.0 was released on 2022-10-28.
5.3.0 was released on 2022-07-04.

## Community Health:
The community is is good health. We are committing patches and cutting releases.
We added a new committer. This is a small community but it is active.


-----------------------------------------
Attachment V: 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:
There are no issues that require board attention. 

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

Community changes, past quarter:
- No new PMC members. Last addition was Mike McGann on 2023-02-27.
- No new committers. Last addition was Mike McGann on 2023-02-28.

(We are in the middle of adding 2 more PMC members who have accepted, but the
 rest of the process is still churning, so they're not official yet.)

## Project Activity:
No new releases this past quarter.

Daffodil 3.5.0 (primarily bug fix release) is still in the works, with a
revised target of late June 2023. As of this writing the last critical bug fix
was just merged. So we believe we are on track now.

The Daffodil 1.3.0 of the Daffodil VSCode Extension (IDE) is in preparation
currently at RC2 status.

In late June we will be presenting Apache Daffodil and its status at a
cyber-security conference.

## Community Health:
Community activity in bug fixing on the main Apache Daffodil library has
slowed somewhat, due to some active contributors getting busier with other
commitments. This is evidenced by the decrease in PR rates.

Counterbalancing this is an uptick in activity on our Daffodil VSCode
Extension IDE project which has generated more email traffic on all our lists.


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

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

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

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

## Activity
 We have been working on 2.0 with JakartaEE-3.0 support and are roughly done.
 Small changes are still waiting to be applied and reviewd though. Expect
 to see a release in the next quarter.

## Community Health
 Still a few around, although not as many as we'd love to see.

## Releases
 - 1.9.6 was released on 2022-04-12.
 - 1.9.5 was released on 2021-03-10.
 - 1.9.4 was released on 2020-06-12.

## Project Composition:
- There are currently 35 committers and 19 PMC members in this project.
- The Committer-to-PMC ratio is roughly 9:5.

## Community changes, past quarter:
- No new PMC members. Last addition was Harald Wellmann on 2016-05-19.
- No new committers. Last addition was Christian Beikov on 2019-10-21.




-----------------------------------------
Attachment X: 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: With consistent releases and an engaged developer 
base, Apache ECharts remains highly relevant in the open source ecosystem.
Issues for the board: NA

## Membership Data:
Apache ECharts was founded 2020-12-16 (2 years ago)
There are currently 28 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 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 He Hao on 2022-07-06.

## Project Activity:
Apache ECharts has maintained a consistent and reliable release cycle, 
delivering new versions to users and incorporating valuable updates and 
bug fixes. Recent releases include:

5.4.2, released on 2023-03-23.
5.4.1, released on 2022-12-09.
5.4.0, released on 2022-09-25.
These releases demonstrate the project's commitment to providing timely 
improvements and enhancements to its users, ensuring the stability and 
quality of the software.

## Community Health:
The Apache ECharts community is vibrant and active, with increased mailing 
list engagement and ongoing development efforts. The project maintains a 
healthy flow of pull requests on GitHub, responsive issue resolution, and 
a dedicated group of contributors, ensuring a positive and collaborative 
environment.


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

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

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

## Membership Data:
Apache EventMesh was founded 2023-03-22 (3 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 (project graduated recently).
- No new committers were added.

## Project Activity:
Software development activity:
 - openconnect merged.
 - rocketmq source/sink connector merged.
 - cloudevents grpc protocol optimization merged.
ready to release v1.9.0

Meetups and Conferences:
 - GLCC tasks created.
 - Community Over Code Asia topics created.

## Community Health:
More than 5 new contributors have been added, and 21 authors 
have pushed 76 commits to master and 93 commits to all branches.

The development mailing list had a 67% decrease in traffic, 
because we redirect some git-related emails into the issues 
mailing list, so the issues mailing list had a big increase 
in traffic. We adopt the suggestion given by
cdutz and tried to set up the .asf.yaml follow
https://github.com/apache/plc4x/blob/develop/.asf.yaml#L62
(hope to see the change next month).


-----------------------------------------
Attachment Z: 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 (16 years ago)
There are currently 68 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.

Community changes, past quarter:
- No new PMC members. Last addition was Georg Henzler on 2019-06-10.
- No new committers. Last addition was Robert Munteanu on 2020-07-20.

## Project Activity:
- Existing implementations have been improved/enhanced based on community
 feedback.
- The http subproject is moving to the Jakarta API (away from javax.*).
- Released 3 components (bug fixes/minor improvements).

### Releases
- maven-bundle-plugin 5.1.9 was released on 2023-05-18.
- org.apache.felix.http.jetty-4.2.12 was released on 2023-05-06.
- org.apache.felix.framework.security-2.8.4 was released on 2023-05-02.

## Community Health:
- Overall the project is in ok health with very little ongoing activity.
- There is a decline in community activity, fewer activity can be seen in
 issue trackers, emails and GitHub. In general, we don't see a lot of new
 development right now. We are at the lookout for new topics and contributors.
- Questions on the user list are answered, development concerns are either
 discussed on the mailing list or directly in the JIRA issues.
- We had no issues voting on releases and JIRA issues are generally addressed.


-----------------------------------------
Attachment AA: Report from the Apache Flagon Project  [Joshua C. Poore]

## Description:
The mission of Apache Flagon is the creation and maintenance of software 
related to thin-client behavioral logging capability useful for business 
analytics, usage analytics, usability and user testing

## Project Status:
No issues at this time. Project is still a new TLP.

## Membership Data:
Apache Flagon was founded 2023-03-21 (2 months ago)
There are currently 17 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- No new PMC members (project graduated recently).
- Jason Young was added as committer on 2023-04-22
- Some discussion of adding new PMC members

## Project Activity:
- Coordinated development activity among committers, PMC on new project features
- Coordinated on updating maintaining website and other utilities
- Likely will release new version of UserALE.js, discuss plans for Distill

## Community Health:
The current community maintains activity this month in addressing new PRs and
issues, as well as coordinating on migration steps for other products and
project resources (e.g., website). May was a slow month with respect to
activity with some discussion on lists, and GitHub issues. Expect additional
discussion in coming months about more infra modernization, and releases. Next
we will focus on releases of our Python product Distill. We believe these
steps will drive additional community growth. Furthermore, we will explore
additional integration examples with Apache Superset, Apache Kafka, Apache
Druid, and Streamlit to drive community growth.


-----------------------------------------
Attachment AB: 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
Issues for the board: None

## Membership Data:
Apache Flex was founded 2012-12-19 (10 years ago)
There are currently 68 committers and 46 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:
A security update of BlazeDS was released on 2023-04-17.

## Community Health:
The community is largely unchanged. There has been little activity since the
chair change and the BlazeDS release.


-----------------------------------------
Attachment AC: 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, with a moderate to high level of activity.
Issues for the board: There are no Board-level issues at this time.

## Membership Data:
Apache Flink was founded 2014-12-17 (8 years ago)
There are currently 101 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.

Community changes, past quarter:
- Leonard Xu was added to the PMC on 2023-04-18
- Qingsheng Ren was added to the PMC on 2023-04-18
- Etienne Chauchot was added as committer on 2023-04-21
- Gabor Somogyi was added as committer on 2023-04-20
- Yuxia Luo was added as committer on 2023-03-10

The PMC is continuously monitoring for new committers and PMC members.

## Project Activity:

We'll start of this report with some great recognition of the Flink communities
work:
Apache Flink is getting the SIGMOD systems award 2023 for its significant 
impact on stream data-processing. SIGMOD is the biggest database research
conference in the world.

Here's an overview over the project activity:

* Releases: In the reporting timeframe, there were 19 releases: Mostly from the
connector externalization, some bugfix releases (1.16.2, 1.17.1, 1.15.4) and
a big release: Flink 1.17.0 with major improvements on batch processing,
efficiency and the interfaces.

* There is a discussion about the future of the "Flink Statefun" subproject.
Most of the active contributors have moved on, so there's little to no activity
in Stateful Functions currently. The PMC has reached out to the
dev@ list to check if there's people willing to take ownership in the project.
The discussion is still ongoing. It seems that current users of the project 
like it and the idea, but there doesn't seem to be a bigger group of
new contributors at the moment. There are ideas about a fork outside of the
ASF, or maintaining it with some help from committers in the ASF for some more
time.

* 2.0 discussion: A discussion about Flink 2.0 has been started. Flink
1.0 is 7 years ago. The discussion is about a long-term plan, not an immediate
2.0 release, as this will disrupt a lot of things (ongoing development, breaking
API changes, ...).
There is wide consensus in the community that a 2.0 release should happen and is
overdue. There were discussions on the scope of the release.

Follow up discussions from the initial 2.0 discussion: 
* The community is preparing a discussion for the project roadmap, 
triggered by the 2.0.0 discussion and the outdated roadmap on the website.
* API and general compatibility between 1.x and 2.x
* Work items for 2.0 release to be collected in the Wiki

There were  branding requests for Flink-conferences in Beijing 
(Flink Forward Asia 2023), Singapore (rejected by the ApacheCon planners) 
and Seattle (Flink Forward Seattle 2023). As well as branding requests
by AWS and Confluent.

Flink 1.18 feature freeze is scheduled by end of June.


## Community Health:
- From the project activity report, you can see there were some healthy
  discussions around Flink 2.0, roadmap and various releases and FLIPs.
- Looking at the statistics (comparing to the previous quarter), there is a
  +29% increase on the user-zh@flink.apache.org list, all other metrics are in
  a slight decline: dev@ ML -12%, Jira's opened -15%, Jira's closed: -19%.
  However, these activities are still at high base numbers: 886 issues opened,
  841 commits, etc.


-----------------------------------------
Attachment AD: Report from the Apache Giraph Project  [Dionysios Logothetis]


-----------------------------------------
Attachment AE: 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: No issues worth board attention

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

Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was William Lo on 2022-08-31.

## Project Activity:
- Ensured Task Reliability: Handle Job Cancellation and Graceful Exits for
  Error-Free Completion
- Support added for watermark for the most recent hour for quiet topics
- Emit completeness watermark information in SnapshotCommitEvent
- Emit warning instead of failing job in retention
- Added usage of flowexecutionid in kafka monitor and jobnames
- Improved Container Transition Tracking in Streaming Data Ingestion
- Improved Container Calculation and Allocation Methodology
- Fixed bug where the wrong workunit event was being tracked
- Implemention of Timeout for Creating Writer Functionality
- Added check that if nested field is optional and has a non-null default
- Fail Hive retention job if deleting underlying files fail
- Improved efficiency of Work Planning in Manifest-Based DistCp Jobs
- Addition of Logging for Abnormal Helix Task States
- Allow flow execution ID propagate to the Job ID if it exists
- Added null default value to observability events
- Logging of helix workflow information and timeout information during
  submission wait / polling
- Support for general Iceberg catalog (support configurable behavior for
  metadata retention policy)
- Initilaize yarn clients in yarn app launcher so that a child class can
  override the yarn client creation logic
- Apache Helix workflows submission timeouts made configurable
- Added job properties and GaaS instance ID to observability event
- Added MRJobLauncher configurability for any failing mapper to be fatal to
  the MR job
- Fixed Apache Iceberg Registration Serialization
- Support for general Iceberg catalog in IcebergMetadataWriter
- Yarn app launchers refactor to support class extension for custom usecases
- Added new lookback version finder for use with Apache Iceberg retention
- Emit dataset summary event post commit and its integration into
  GaaSObservabilityEvent
- Code cleanup: Merged similar logic between
  FlowConfig{,V2}ResourceLocalHandler.update into single base class
  implementation
- Added mechanism to reject flow config updates that would fail compilation by
  returning service error
- Added capability to register Apache Iceberg table metadata update with
  destination side catalog
- Fixed add spec and actual number flows scheduled metrics
- Added backoff retry when accessing db for flow spec or dag action
- Added logging of startup command when container fails to startup
- Updated Manifest based copy to support facl
- Added defaults to newly added fields in observability events
- Added metrics to measure and isolate bottleneck for init
- Added protection to prevent the adding of flowspec compilation errors to the
  scheduler
- Added and changed appropriate job status fields for observability events
- Ability to filter datasets that contain non optional unions
- Capability to create Generic Apache Iceberg Data Node to Support Different
  Types of Catalogs
- Ability to delete multiple watermarks in a state store
- Support for Other Catalog Types for Apache Iceberg Distcp

Last Release date: 0.16.0 on 3rd Feb, 2022. New release of version 0.17.0 is in
progress

Question in last release:: jmclean: Please include the date(s) of your last
release(s) in future reports. It has been more than a year since your last
release are you planning to have a new release?

Answer:: abti: We have included date of last release in the report. Thanks for
pointing that out. We are also working on a new release (0.17.0), and we will
establish a more defined release cadence going forward.

## Community Health:
- There have been 51 commits since March 2023.
- 28 commits have been from non-committers.
- William Lo was voted in Aug, 2022 as a committer. We constantly look for
 consistent contributors to vote them in as Committers.


-----------------------------------------
Attachment AF: Report from the Apache Gora Project  [Kevin Ratnasekera]

## Description:
- The Apache Gora open source framework provides an in-memory data model and
  persistence for big data. Gora supports persisting to column stores,
  key-value stores, document stores, distributed in-memory key-value stores,
  in-memory data grids, in-memory caches, distributed multi-model stores and
  hybrid in-memory architectures. Gora also enables analysis of data with
  extensive Apache Hadoop MapReduce, Apache Spark, Apache Flink, and Apache
  Pig support.

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

## Membership Data:
Apache Gora was founded 2012-01-24 (11 years ago) There are currently 31
committers and 29 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Lahiru Jayasekara on 2020-04-30.
- No new committers. Last addition was Lahiru Jayasekara on 2020-04-27.

## Project Activity:
- Received several contributions from external people.
- Several PMC members volunteered in mentoring GSoC for this year, we were
  granted with 2 slots for this year GSoC programme.
- Except for activity related preparation of GSoC project, we have not been
  able to make significant progress on our next major release, 0.9 was
  released on 2019-08-15 and it has been quite while since last release.


## Community Health:
- We observed the usual activity level on both Github and mailing lists for
  the past quarter. So nothing significant that worth mentioning for the this
  quarterly report compared to previous reports. Activity level for past
  quarter on Github and mailing lists was mainly influenced by the GSoC
  preparation work. For the past few years, GSoC has been an excellent source
  for bringing new contributors to our project. Most of our recent elected
  committers are previous GSoC participants who continued to remain in the
  project.


-----------------------------------------
Attachment AG: 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
Issues for the board: none

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

Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- No new committers. Last addition was Luke on 2020-02-07.

## Project Activity:
The project has adopted a new minor/bugfix release cycle that allows for more
frequent releases between the larger feature releases, and has produced two
additional releases since last report, with a third currently underway (1.5.3).

Recent releases:
- 1.5.2 was released on 2023-05-25.
- 1.5.1 was released on 2023-04-13.
- 1.5.0 was released on 2023-02-18.

## Community Health:
The community continues to be active and healthy. With increasing release
frequency, there are corresponding increases in activity across all mailing
lists and increases in contributions from the community.


-----------------------------------------
Attachment AH: 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 (17 years ago) There are currently
16 committers and 10 PMC members in this project.  The
Committer-to-PMC ratio is 8:5.

## Community changes, past quarter:

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

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. During the past
quarter Gump was migrated to run builds using Java 21 because Tomcat
will start requiring this as baseline for Tomcat 11.x.

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 almost five years.

-----------------------------------------
Attachment AI: 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 activity
Issues for the board: 

## Membership Data:
Apache Helix was founded 2013-12-17 (9 years ago)
There are currently 27 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

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

## Project Activity:
- 1.2.0 was released on 2023-05-02
- 1.1.0 was released on 2023-01-04.
- 1.0.4 was released on 2022-06-09.

## Community Health:
- 89 PRs opened on GitHub, past quarter (58% increase)
  91 PRs closed on GitHub, past quarter (68% increase)
  172 commits in the past quarter (117% increase)

  Helix recently done with branch development of multi quarter project, 
  Metaclient. It generalized the store from Zookeeper expanding to other
  potential better solutions.

- Next quarter, we will focus on improving the multi dimension assignment 
  with better performance. And will start thinking about container management
  integration proposal.


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

## Description:
The Apache Hive ™ data warehouse software facilitates reading, writing, and
managing large datasets residing in distributed storage (Apache Hadoop) using
SQL.

## Project Status:
Current project status: Active
Issues for the board: No issues requiring board attention this time.

## Membership Data:
Apache Hive was founded 2010-09-21 (~13 years ago) There are currently 106
committers and 56 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4. One long time member of Apache Hive PMC, Alan Gates, resigned in
April. Membership data above does not reflect this resignation.

Community changes, past quarter:
- No new PMC members. Last addition was Krisztian Kasa on 2023-01-29.
- No new committers. Last addition was Alessandro Solimando on 2023-02-08.

## Project Activity:
Still working towards the 4.0GA release. Community has decided to do one more
release before our 4.0.0 GA release & 4.0.0-beta-1 is in the planning stage,
release “most probably” before end of June. 
Apache Hive 3.2 release with fixes
for CVEs is also in planning. 

Jira activity: In the trailing 31 days, 99 jiras
have been opened, 29 of which have been FIXED. A total of 73 jiras have been
closed/resolved and a total of 65 have been FIXED.

## Community Health:
Community Health Score (Chi): 0.62 (Mostly Okay)

Community activity is relatively healthy based on engagement. Emails activity
has reduced but compared to last quarter, there was a significant increase in
overall activity (jira/github/dev lists).


-----------------------------------------
Attachment AK: 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, with high activity (400+ contributors,~1500
commits/quarter) 
Issues for the board: Issues for the board: none.

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

Community changes, past quarter:
- No new PMC members. Last addition was Y Ethan Guo on 2023-03-13.
- No new committers. Last addition was Yue Zhang on 2022-12-31.

## Project Activity:
Since the last report, we made two patch releases - 0.12.3 to the 0.12.X LTS
release line, 0.13.1 to the latest major release. Community is working on
0.14.0 which adds several new features again, and 550+ commits have been
landed already. Plan is to code complete by end of june.

Outside of the 0.X releases, the most exciting development is the RFC for Hudi
1.X, which is a powerful re-imagination of Hudi as a database for multi modal
data lakes. https://github.com/apache/hudi/pull/8679 has seen very active
engagement and prototyping is underway to define fully what constitutes the
alpha, beta and first stable 1.0 release.
## Community Health:
Like noted in the previous report, we spent efforts landing a lot of PRs and
backporting bugfixes, which have all resulted in increased project activity
across the board.


-----------------------------------------
Attachment AL: 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 (3 years ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- Fokko Driesprong was added to the PMC on 2023-04-06
- Steven Wu was added to the PMC on 2023-04-06
- Szehon Ho was added to the PMC on 2023-04-20
- Yufei Gu was added to the PMC on 2023-04-06
- Amogh Jahagirdar was added as committer on 2023-04-25
- Eduard Tudenhoefner was added as committer on 2023-04-25

## Project Activity:

* 1.3.0 was released on 2023-05-26
* 1.2.1 was released on 2023-04-01
* 1.2.0 was released on 2023-03-20

The 1.3.0 release added support for Spark 3.4 and Flink 1.17. It also included
several updates and fixes, including:
* Better Spark file distribution for row-level plans like MERGE
* Improved bit density in the object storage layout
* Readable metrics in metadata tables
* Optimized vectorized reads for decimal types
* Spark timestamp_ntz and UUID support

The Python implementation is nearing an 0.4.0 release that will include:
* Delete file support
* Metadata updates for tables
* Improved compatibility

The community is also continuing to build a view specification, expand REST
catalog support, and add encryption to the table spec.

## Community Health:

The community continues to be healthy, with most metrics steady this quarter.


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

# Incubator PMC report for June 2023

The Apache Incubator is the entry path into the ASF for projects and 
codebases wishing to become part of the Foundation's efforts.
There are presently 26 podlings incubating. 
This month we were missing reports from Toree and Training. SeaTunnel has 
graduated, and Kvrocks have a proposal to the board for graduation. 
podlings 
executed 4 distinct releases.   
Toree has had little activity in the past six months, and they have missed 
many reports, a PPMC roll call will be taken and they asked if they should 
consider retirement. 
Datalab has initiated graduation discussions, but they may not be ready to 
graduate yet as they don't seem in alignment with the Apache Way. 

## Community

### New IPMC members:
  - None

### People who left the IPMC:
  - None

## New Podlings
- None

## Podlings that failed to report, expected next month

- Toree
- Traning

## Graduations

- SeaTunnel

The board has motions for the following:

- Kvrocks

## Releases

  The following releases entered distribution during the month of
  May:
  - Teaclave 0.5.1
  - SDAP 1.1.0
  - StreamPark 2.1.0
  - Kvrocks 2.4.0

## IP Clearance
- none

## Legal / Trademarks
- N.A

## Infrastructure
- N/A

## Table of Contents  
[Baremaps](#baremaps)  
[KIE](#kie)  
[Nemo](#nemo)  
[NLPCraft](#nlpcraft)  
[OpenDAL](#opendal)  
[Paimon](#paimon)   
[SDAP](#sdap)  
[Toree](#toree)  
[Training](#training)  
[Uniffle](#uniffle)  
[Wayang](#wayang)  

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

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

Baremaps has been incubating since 2022-10-10.

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

  1. Getting the code in compliance with Apache standards
  2. Making releases
  3. Growing the community

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

  Someone submitted our website to HackerNews and we remained on the
  frontpage for about 16 hours [1]. Our demonstration server hosted on
  Hetzner (16 cores; 128GB of RAM; 8TB of NVMe SSD) successfully sustained
  this load and served more than 40GB of tiles from Postgis during this
  period of time [2]. Additionally, the OpenStreetMap Wiki now offers the
  possibility to display vector maps based on Baremaps on its pages [3]. 
This
  raises the following question: Could the demonstration server be hosted by
  the ASF at some point?

  [1] https://news.ycombinator.com/item?id=36106695

  [2] https://demo.baremaps.com/#14/46.5197/6.6323

  [3] https://wiki.openstreetmap.org/wiki/Template:Vector_map

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

  The activity has increased. Five people made their first contribution to
  the code base since the last report, one of whom has been elected as a
  committer in May. The activity on the mailing list is very low, but the
  number of exchanges on GitHub increased.

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

  We significantly improved the basemap at low zoom levels
  We improved the layout and the content of the web site
  We continued to address licensing issues
  We attended the OGC/OSGeo/ASF code sprint and improve support for OGC API
  We fixed bugs and addressed issues

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

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

### Date of last release:

  2023-04-04

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

  Leonard Cseres was elected as a committer in May.

### Have your mentors been helpful and responsive?

  Yes, the mentors have been very helpful on several topics (community
  building, licensing, etc.). The discussions with Martin Desruisseaux at 
the
  OGC/OSGeo/ASF code sprint greatly helped at identifying avenues to address
  our licensing issues.

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

  Yes

### Signed-off-by:

  - [ ] (baremaps) Bertrand Delacretaz  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  
  - [X] (baremaps) Julian Hyde  
     Comments:  Congratulations on the HN coverage and traffic.
       (Back in the day, getting Slashdotted was a rite of passage.)
       I'd say this puts you in the 'community building' phase.
       Regarding hosting, let's discuss on dev,
       with the aim of creating an INFRA case if necessary.
  - [X] (baremaps) Calvin Kirs  
     Comments:  
  - [ ] (baremaps) George Percivall  
     Comments:  
  - [ ] (baremaps) Martin Desruisseaux  
     Comments:  

### IPMC/Shepherd notes:

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

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

KIE has been incubating since 2023-01-13.

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

  1. Getting the code into Apache git repos
  2. Finishing the software grant
  3. Release

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

  No

### How has the community developed since the last report?
  It has been a slow quarter for us. Red Hat had a round of layoffs this
  quarter which affected their legal team, and the ones working on the
  Software Grant for Apache.
  It has pushed us back quite a ways as we've had to redo a bunch of the 
work.
  We're now targeting the end of June to have all the legal issues finished
  and the software grant completed.

### How has the project developed since the last report?
  See the above question.

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

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

### Date of last release:
  N/A

### When were the last committers or PPMC members elected?
  Back in December when we were accepted as a podling

### Have your mentors been helpful and responsive?
  No issues with the mentors

### Is the PPMC managing the podling's brand / trademarks?
  So far, yes.

### Signed-off-by:

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

### IPMC/Shepherd notes:

  We need to keep an eye on the legal issue of the podling project.
  Hope Redhat can address this issue this June.
--------------------
## Nemo

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

Nemo has been incubating since 2018-02-04.

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

  1. Address remaining items before graduation
  2. Motivate growth in the community
  3. A new release after finalizing new features in our codebase

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

  None.

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

  - In order to develop the community, we are working on reinforcing the
  documentations for better usability with visual aids.
  - We have also integrated Disqus on our website for better communication
  with the users.

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

  - Discussions for graduation
  - Finalizing the code cleanup and documentations for new features and
  filing existing PRs (e.g., for supporting features regarding offloading
  bottleneck tasks to serverless frameworks)

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

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

### Date of last release:

  2022-09-02

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

  September 28, 2021

### Have your mentors been helpful and responsive?
  - The mentors have been helpful.

### Is the PPMC managing the podling's brand / trademarks
  - The PPMC manages the podling's brand / trademarks.

### Signed-off-by:

  - [ ] (nemo) Hyunsik Choi  
     Comments:  
  - [X] (nemo) Byung-Gon Chun  
     Comments:  
  - [ ] (nemo) Jean-Baptiste Onofré  
     Comments:  
  - [ ] (nemo) Markus Weimer  
     Comments:  

### IPMC/Shepherd notes:

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

## NLPCraft

A Scala library for NLU applications.

NLPCraft has been incubating since 2020-02-13.

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

  1. Community growth.
  2. 
  3. 

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

  None.

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

  - We have communicated with developers which have interest to contribute 
  to the project, especially with Python developers.

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

  - Research related to usage in the project last AI technologies.
  - Site updated, examples extended.

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

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

### Date of last release:

  2023-02-30

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

  August of 2021.

### Have your mentors been helpful and responsive?
  No issues with mentors to report.

### Is the PPMC managing the podling's brand / trademarks?
  No issues with mentors to report.

  ### Signed-off-by:

  - [ ] (nlpcraft) Roman Shaposhnik  
     Comments:  
  - [X] (nlpcraft) Furkan Kamaci  
     Comments:  
  - [ ] (nlpcraft) Evans Ye  
     Comments:  
  - [ ] (nlpcraft) Paul King  
     Comments:  
  - [ ] (nlpcraft) Konstantin I Boudnik  
     Comments:  
  - [ ] (nlpcraft) Dave Fisher  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## OpenDAL

Open Data Access Layer: Access data freely, painlessly, and efficiently.

OpenDAL has been incubating since 2023-02-27.

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

  1. Making the first release.
  2. Grow the community.
  3. Collect more use cases.

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

  None.

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

  In the past month, we have welcomed 5 new contributors, bringing the total
  number to 91.

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

  In the past month, we added new services integrations like sftp, supabase,
  vercel artifacts and cos.

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

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

### Date of last release:

  2023-05-23

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

  2023-05-29

### Have your mentors been helpful and responsive?

  Yes.

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

  Yes.

### Signed-off-by:

  - [ ] (opendal) tison  
     Comments:  
  - [X] (opendal) Willem Ning Jiang  
     Comments: Good to see OpenDAL made a big step to cut the first Apache 
     release.
  - [ ] (opendal) Sheng Wu  
     Comments:  
  - [ ] (opendal) Ted Liu  
     Comments:  
  - [ ] (opendal) Xiaoqiao He  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Paimon

Paimon is 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. 

Paimon has been incubating since 2023-03-12.

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

  1.Publish our first release
  2.Grow the community
  3.Improve our website to contain security page, committer/ppmc list, 
  contributor guide, and etc.

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

  N/A

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

  1. Committed our LOGO
  2. Several PIPs are in discussion on the dev mailing list, and several 
  have agreed to start development:
  
https://cwiki.apache.org/confluence/display/PAIMON/Paimon+Improvement+Proposals

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

  1. First release under voting in general@incubator.apache.org
  2. Support Kafka CDC data ingestion
  3. Support Consumer-id to consume from the previous progress without 
  resuming from the state

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

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

### Date of last release:

  XXXX-XX-XX

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

  N/A

### Have your mentors been helpful and responsive?

  Our mentors have been very helpful and responsive.

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

  The VP, Brand has approved the project name.

### Signed-off-by:

  - [ ] (paimon) Becket Qin  
     Comments:  
  - [X] (paimon) Robert Metzger  
     Comments:  No concerns.
  - [X] (paimon) Stephan Ewen  
     Comments: Team seems to operate maturely and to understand community 
     processes well (which is not surprising, given they are all committers 
in
     other projects).
  - [X] (paimon) Yu Li  
     Comments: Team is actively working towards the first apache release 
     (after entering incubation) and has addressed several legal issues 
found
     during IPMC review. Meantime discussions happen frequently and 
adequately
     on the dev mailing list, which indicates a good community build-up.

### IPMC/Shepherd notes:

--------------------
## SDAP

SDAP is an integrated data analytic center for Big Earth Science problems.

SDAP has been incubating since 2017-10-22.

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

  1. Make a third release that addresses exceptions in the WIP-DISCLAIMER  
  2. Start dev discussion thread on graduating
  3.

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

### How has the community developed since the last report?
  Discussion and development is active.

  Worked through process of creating second official SDAP release
  with different release manager.

### How has the project developed since the last report?
  Second SDAP release (v1.1.0) is available for download at
  https://sdap.apache.org/downloads

  27 issues closed and 13 issues new/updated.

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

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

### Date of last release:

  2023-05-16 (Version 1.1.0)

### When were the last committers or PPMC members elected?
  Jason Kang was added as a committer on 2023-05-22

### Have your mentors been helpful and responsive?
  Yes. Our mentor, Julian Hyde, continues to provide guidance in SDAP
  releases and graduation.

### Is the PPMC managing the podling's brand / trademarks?
  PPMC is not aware of any issues.

### Signed-off-by:

  - [X] (sdap) Julian Hyde  
     Comments:  SDAP is ready to graduate. They have not yet had
       a graduation discussion on dev but they should. They are working
       on resolving issues in WIP-DISCLAIMER don't I hope these don't
       delay graduation too much.
  - [ ] (sdap) Jörn Rottmann  
     Comments:  
  - [ ] (sdap) Trevor Grant  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Uniffle

Uniffle is an unified Remote Shuffle Service

Uniffle has been incubating since 2022-06-06.

### Three most important unfinished issues to address before graduating:
  Promote the project and grow the user and dev community.

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

### How has the community developed since the last report?
  1. 9 new contributors from different affiliations contributed to Uniffle
  project.
  2. 75 issues have been created, among 57 issues were discussed and 
resolved.

### How has the project developed since the last report?
  1. 75 issues have been created, among 57 issues were discussed and 
resolved.
  2. 109 prs have been created, among 90 prs have been merged.
  3. We released 0.7.0

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

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

### Date of last release:

  2023-04-10

### When were the last committers or PPMC members elected?
  Jingxiong Zhong, elected as committer on 2023-03-16

### Have your mentors been helpful and responsive?
  Yes, they're helpful in guiding the podding project.

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

### Signed-off-by:

  - [ ] (uniffle) Felix Cheung  
     Comments:  
  - [X] (uniffle) Junping Du  
     Comments:  
  - [X] (uniffle) Liu Xun  
     Comments:  
  - [X] (uniffle) Weiwei Yang  
     Comments:  
  - [X] (uniffle) Zhankun Tang  
     Comments:  

### IPMC/Shepherd notes:

  [Calvin Kirs]2 mentors and multiple PPMCs are not subscribed to the 
private
  mailing list, also,
  it seems that more than half of the PPMC members are not active, which is
  normal, but I am curious about what happened.

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

Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.

Wayang has been incubating since 2020-12-16.

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

  1. Release 1.0 (in progress)
  2. Update Website (we have issues to get the pipeline running, its messed 
  a bit and INFRA could not help)
  3.

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

### How has the community developed since the last report?
  We got significant traction, received commits from multiple individuals 
and
  organizations.

### How has the project developed since the last report?
  Activity increasing, commits and dev activity climbing.

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

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

### Date of last release:    
  2021-12-13

### When were the last committers or PPMC members elected?
  2023 - 26 - 04

### Have your mentors been helpful and responsive?
  Only the website pipeline.

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

### Signed-off-by:

  - [ ] (wayang) Christofer Dutz  
     Comments:  
  - [ ] (wayang) Lars George  
     Comments:  
  - [ ] (wayang) Bernd Fondermann  
     Comments:  
  - [ ] (wayang) Jean-Baptiste Onofré  
     Comments:  

### IPMC/Shepherd notes:1


-----------------------------------------
Attachment AN: 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: none.

## Membership Data:
Apache IoTDB was founded 2020-09-16 (3 years ago)
There are currently 58 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Chao Wang on 2022-12-12.
- Peichen Chou was added as committer on 2023-05-05
- Yuhua Ren was added as committer on 2023-05-31

## Project Activity:

IoTDB has evolved into v1.1.x, while v0.13.x is still maintained.
The community is working on v1.2.0, which has some new features e.g., 
more complex time-series-oriented queries, more stable cluster.

Recent releases:
IOTDB-1.1.1 was released on 2023-06-14.
IOTDB-1.1.0 was released on 2023-04-03.
IOTDB-0.13.4 was released on 2023-02-23.


## Community Health:

The community looks healthy and we are trying to develop its ecosystem.

- Two new committers, who come from different organizations/companies 
are elected.
- We host several meetups, e.g., IoTDB x EMQ on 15th April and 31th May.  
- Some committers introduced IoTDB on some international conferences, 
e.g., buildingIoT in Germany, Open Sourse Summit in Chongqing China.


-----------------------------------------
Attachment AO: 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 (17 years ago)
There are currently 59 committers and 59 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- Rishabh Daim was added to the PMC on 2023-04-06
- Rishabh Daim was added as committer on 2023-04-06

## 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 project team started to replace the plain Guava dependency in 
Jackrabbit Oak with a shaded version. This allows us to more easily
update Guava without interfering with users of Jackrabbit Oak.

Maintenance of Jackrabbit 2.16.x and Jackrabbit Oak 1.8.x ended in
May. Announcements have been sent to inform users to migrate to
more recent versions.

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

Concerns were raised on the private email list about lack of or little
constructive participation by Jackrabbit committers on the FileVault
subproject. There is a split within the committers. Some would like to
actively evolve FileVault, while others are mostly happy with the status
quo and prefer fewer changes. 

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.50.0 was released on 2023-03-23
- jackrabbit-2.21.16 was released on 2023-04-05
- jackrabbit-oak-1.22.15 was released on 2023-04-07
- jackrabbit-2.20.10 was released on 2023-05-08
- jackrabbit-oak-1.52.0 was released on 2023-05-15 

## JIRA activity:

- 167 JIRA tickets created in the last 3 months
- 134 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AP: 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:
There are no issues requiring board attention.

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

Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Francois Papon on 2018-05-19.

## Project Activity:
Releases preparation:
* karaf osgi runtime 4.3.10 and 4.4.4 are in preparation
* karaf decanter 2.11.0 and 3.0.0 are in preparation
* karaf osgi runtime 4.5.0 preparation will start just after 4.3.10 and 4.4.4
  releases

## Community Health:
This past quarter was mostly preparation for the summer releases set. The
karaf-integration will be part of new releases. The new bundle URL handler
implementation also started and a PR will be created soon. Following the vote,
Karaf Cave and Karaf Winegrower have been removed from the mailing list.


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

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

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

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

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

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

Very little activity again during the quarter and still trying to find free
cycles to work on a release of previous Kibble version and a roadmap for what
the new Kibble could look like.

We've had a documentation contribution [1] from a new contributor and also
some interest from someone trying out an install [2].

## Community Health:
The community is small and we know that we need to start focussing on building
it up to be more sustainable but we first need to work on defining the
project vision and roadmap of where we want the project to go. I still think
putting out a Kibble-1 release will help separate the previous version from
the new one that we'd like to build.

[1] https://github.com/apache/kibble/pull/16 
[2] https://s.apache.org/zm5ej


-----------------------------------------
Attachment AR: 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 high activity
Issues for the board: N/A.

## Membership Data:
Apache Kyuubi was founded 2022-12-21 (5 months ago)
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Fu Chen on 2023-01-31.
- Denis Krivenko was added as committer on 2023-04-08
- Paul Lin was added as committer on 2023-06-02
- Tianlin Liao was added as committer on 2023-04-08
- Yaodong Zhang was added as committer on 2023-04-01

## Project Activity:

- [RELEASE] Apache Kyuubi 1.7.0 released on 2023-03-08
- [RELEASE] Apache Kyuubi 1.7.1 released on 2023-05-05
- [RELEASE] Apache Kyuubi Shaded 0.1.0 released on 2023-05-21


## Community Health:

- The contributor list, PMC, and committer group continue to grow and
become more diverse
  - We have recruited our first committer from Europe
  - We have recruited our first lady committer
  - We have recruited our first PMC in the Healthcare industry
- The user group also continues to grow rapidly. We've received a lot
of success stories from our users, such as AWS and Cloudera.
- Issue resolution, commits activity and mailing list traffic are
 moderate and matches the rate of the last quarter.


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


-----------------------------------------
Attachment AT: 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: New
Issues for the board: There are no issues requiring board attention

## Membership Data:
Apache Linkis was founded 2022-12-21 (6 months ago)
There are currently 35 committers and 24 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 Chen Xia on 2023-02-06.
- Fei Guo was added as committer on 2023-05-31

## Project Activity:
Apache Linkis released version 1.3.2 on April 3rd. This version involved 
more than 24 contributors, including 7 new contributors (currently: 140), 
and contained over 30 new features. Apache Linkis 1.4.0 and 1.5.0 are currently 
under development.

Software development activity:
We are preparing to release 1.4.0 in the coming month.
At this time, we are focusing on trying to develop 1.5.0,
and 1.5.0 looks to achieve these goals:

1. Entrance supports task HA (running task support is taken over)
2. Support task submission to the K8S cluster
3. Support Nacos registration center
4. Entrance supports Orchestrator pluggable
5. The once-mode task supports recording information through the entrance
6. The data source module supports data source SQL generation and supports
more data sources with the Spark ETL function
7. Spring Cloud gateway upgrade version, spring boot upgrade version

Meetups and Conferences:
- On June 13th, Linkis and the OceanBase community jointly organized a Meetup: 
"Apache Linkis and OceanBase Integration: Improving Data Analysis Speed".
- We plan to participate in Open Source Summer in 2023.
- We plan to participate in CFP-ApacheCon Asia 2023.
- We plan to participate in GitLink Code Camp in 2023.

## Community Health:
- Overall community health is good.
- 212 PRs merged on GitHub, past quarter.
- 198 issues closed on GitHub, past quarter.
- Community Health Score (Chi): 10.00 (Super Healthy)


-----------------------------------------
Attachment AU: Report from the Apache Lucene Project  [Greg Miller]

## 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-18 (18 years ago)
There are currently 98 committers and 63 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 Greg Miller on 2022-06-06.
- No new committers. Last addition was Ben Trent on 2023-01-27.

## Project Activity:
9.6 was released on 2023-05-09
- Release notes are available at:
https://lucene.apache.org/core/9_6_0/changes/Changes.html
- Some highlights released with 9.6 include:
-- New KeywordField introduced to provide simple and efficient filtering, 
sorting and faceting
-- Java 20 foreign memory API support added for users running Java 19/20
-- Improved performance for TermInSetQuery, PrefixQuery, WildcardQuery 
and TermRangeQuery
-- Lower memory usage for BloomFilteringPostingsFormat
-- Faster merges for HNSW indexes and improvements to concurrent 
indexing throughput under heavy load
-- TermAutomatonQuery supports the "explain" API

PyLucene 9.6 was released on 2023-06-03
- Tracks core 9.6 release changes
- Release notes are available at:
https://svn.apache.org/repos/asf/lucene/pylucene/tags/pylucene_9_6_0/CHANGES

## Community Health:
Community interactions remain healthy.
- dev@ mailing list traffic increased 183% compared to last quarter
(371 emails compared to 131).
-- Discussion related to KNN search dimension limits was particularly active,
 accounting for 137 of the dev@ list emails
- Development activity has picked up this past quarter compared to last, with:
-- 60 commits (+900%)
-- 51 PRs opened (+466%)
-- 53 PRs closed (+960%)
- PR volume remains healthy, with open PRs trending in a steady state
while closed PRs continue to increase at the same trend 
(https://home.apache.org/~mikemccand/lucenebench/github_pr_counts.html).


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


-----------------------------------------
Attachment AW: Report from the Apache Mnemonic Project  [Yanhui Zhao]

## Description:
Apache Mnemonic is an open-source Java library for durable object-oriented
programming on hybrid storage-class memory(e.g. NVM) space. It comes up with
durable object model (DOM) and durable computing model(DCM) and takes full
advantages of storage-class memory to simplify the code complexity, avoid
SerDe/(Un)Marshal, mitigate caching for constructing next generation computing
platforms. Mnemonic makes the storing and transmitting of massive linked
objects graphs simpler and more efficient. The performance tuning could also
be mostly converged to a single point of tuning place if based on Mnemonic to
process and analyze linked objects. The programmer is able to focus on the
durable object oriented business logic instead of worrying about how to
normalize/join, SerDe(un)marshal, cache and store their linked business
objects with arbitrary complexity.

## Project Status:
Current project status: Dormant/At risk
Issues for the board: Vote for PMC chair change following the board's suggestion

## Membership Data:
Apache Mnemonic was founded 2020-11-30 (3 years ago)
There are currently 21 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Chenyang Li on 2020-11-04.
- No new committers. Last addition was Chunyong on 2021-10-05.

## Project Activity:
We had 0.17.0 release done, but the project seems losing momentum. We hope to
change the PMC chair hoping PMC could help to better drive the community
effort and engagement

## Community Health:
As the data shown, we will need some way to improve the community engagement
by laying clear project roadmap and end goal. Otherwise it is hard to attract
and motivate developers 8 issues opened in JIRA, past quarter (14% increase) 2
issues closed in JIRA, past quarter (-50% change) 4 commits in the past
quarter (-50% change) 3 code contributors in the past quarter (no change) 3
PRs opened on GitHub, past quarter (50% increase) 3 PRs closed on GitHub, past
quarter (50% increase)


-----------------------------------------
Attachment AX: Report from the Apache MXNet Project  [Sheng Zha]

## Description:
The mission of Apache MXNet is the creation and maintenance of software related 
to a flexible and efficient library for Deep Learning

## Project Status:
Current project status: Considering moving to the Attic
Issues for the board: The project's current positioning is not gaining traction
in light of the development in the open source deep learning framework space.
Code development has mostly halted and community engagement slowed.
While roll call of the MXNet PMC received responses from 21 PMC members, the
PMC still needs either to find a critical mass to continue drive maintenance,
or to find alternative position that MXNet can pivot to so that the community
can gain traction in attracting new joiners. The discussion is happening on dev@

## Membership Data:
Apache MXNet was founded 2022-09-20 (9 months ago)
There are currently 87 committers and 51 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 Anirudh Subramanian on 2022-09-20.
- No new committers were added.

## Project Activity:
Software development activity:
- 4 pull requests created in the last 3 months.

## Community Health:
Community engagement has slowed significantly compared to last year, despite
that the GenAI/large language model boom sparked increased general interest
in deep learning and scalable systems.


-----------------------------------------
Attachment AY: 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 (6 years ago)
There are currently 36 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.

Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Krzysztof Kopyściński on 2021-01-26.

## Project Activity:
Community work in several areas including:
test facilities, tooling, improvements in MCU and BSP support, qualification
fixes for Bluetooth stack, USB support, bug fixes.

Support for GUI (via LVGL) and various touchscreens was added.

Working on support for Bluetooth LE Audio (broadcast support).

## Community Health:
Number of contributors is stable, "core" developers are contributing code on
regular basis.

Mailing list see little activity as most discussions happen on Slack and Github.


-----------------------------------------
Attachment AZ: 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 steady activity.
Issues for the board: None.

## Membership Data:
Apache NetBeans was founded 2019-04-17 (4 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.
- Tomas Hurka was added as committer on 2023-05-24

## Project Activity:
- 18 was released on 2023-05-30, with 31 contributors, including 5 who
contributed for the first time.
- 17 was released on 2023-02-21, with 36 contributors, including 7 who
contributed for the first time.

## Community Health:
- The key challenge in the project is that, since it is so large and
  everything is done via e-mail, it is not easy keeping everyone in sync, such
  as during moments of hand off in the release process, sometimes a few days
  go by before the next step in the process is picked up due to communication
  challenges. Maybe quick weekly Zoom calls are needed during the release
  process for those on the release team to remain in sync.
- In general the project is in a steady ongoing state with a strong core team,
  continual contributors, including new contributors, as can be seen in the
  Project Activity section above.
- Mailing list activity is down: in the past quarter dev@netbeans.apache.org
  had a 40% decrease in traffic (386 emails compared to 639) and
  users@netbeans.apache.org had a 36% decrease in traffic
  (235 emails compared to 363). On the topics that were of greatest interest,
   a lot of discussion took place, i.e., "[Lazy Consensus] Minimum JDK build
   and run policy (dropping JDK 8)" and "[VOTE] Minimum JDK build and run
   policy (dropping JDK 8)" were the busiest email threads.
- Apache NetBeans swag being worked on and in progress with
  dev@community.apache.org.


-----------------------------------------
Attachment BA: 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 (16 years ago)
There are currently 58 committers and 33 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 Daniel Watford on 2023-01-18.
- No new committers. Last addition was Mekika Leila on 2022-09-28.

## Project Activity:
- various contributions and bug fixes have been contributed and integrated
  into our codebase
- two new releases have been published since our last report; they are both
  bug fix releases in the 18.12 series:
-- 18.12.07 was released on 2023-04-10
-- 18.12.08 was released on 2023-06-01
- security handling: the release 18.12.07 has fixed a security vulnerability
  (CVE-2022-47501) and currently we do not have open vulnerability reports on
   our plate
- release plans: in the next quarter we will continue using the 18.12 branch
  as the basis to publish bug fix releases as needed, while we complete the
  stabilization of the new 21.01 branch that will support Java 17
- the effort to migrate the official blog from Roller to Hugo is still ongoing
  and a bit behind of schedule; in the meantime, as agreed with the Infra
  team, archived posts are hosted on https://blogsarchive.apache.org/#ofbiz
  and any new post will be on ofbiz.apache.org/blog

## Community Health:
No new committers or PMC members have been invited during the last quarter
but we have some candidates in our watchlist. Community activity over the last
quarter has been on average and similar to previous periods: various user
questions have been posted and answered on topics including OFBiz
configuration and deployment, data model customisations, bill of materials,
inventory items etc...


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

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

## Project Status:
Current project status: Dormant
Issues for the board: No issues requiring board attention at this time.

## Membership Data:
Apache Olingo was founded 2014-03-19 (9 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:
  - V2 2.0.12 was released on 2022-04-24.
  - 4.9.0 was released on 2022-03-09.

Planned maintenance release for 4.x and 2.x 
are further delayed. 
Current plan is to have an issue consolidation 
phase till end of June and releases by end of July.

## Community Health:
Overall community health is good.
However, activity on the mailing lists increased in the last quarter.
More new JIRA items got created and more PRs got opened.
Unfortunately, progress on JIRA items was low 
and not all PRs could be closed.
Resulting in only 6 commits (minor decrease).
Release of V2 and V4 versions are planned.


-----------------------------------------
Attachment BC: 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: There is a low priority
email thread from the 2023-03-22 board meeting regarding how to release NLP
models. This email thread is pending a response from the OpenNLP PMC, but if
the board has any additional thoughts please also reply.

## Membership Data:
Apache OpenNLP was founded 2012-02-14 (11 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 Koji Sekiguchi on 2017-10-09.
- No new committers. Last addition was Atita Arora on 2023-02-28.

## Project Activity:
The project is healthy. OpenNLP 2.2.0 was released on April 22, 2023. The
project has been trying to have more frequent releases.

## Community Health:
The community remains healthy even with a decline in activity on the mailing
lists since the last board report.


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

## Description:
 Apache OpenWebBeans is an ALv2-licensed implementations of the
 "Contexts and Dependency Injection for the Java EE platform"
 specifications which are defined as JSR-299 (CDI-1.0), JSR-346
 (CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0).

 The OWB community also maintains a small server as
 Apache Meecrowave subproject. Meecrowave bundles latest releases of
 the ASF projects Tomcat9 + OpenWebBeans + CXF + Johnzon + log4j2.

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

## Activity:
 We've got our CDI-4.0 implementation ready and pass most TCK tests.
 Thinking about rolling an alpha release as TCK testing within TomEE 
 still takes a bit.

## Community Health
 Quite okish for such an old project. 


## PMC changes:
 - Currently 13 PMC members, 20 committers
 - Last PMC addition was Reinhard Sandtner on 2017-10-09.
 - Last committer addition was John D. Ament on 2017-10-09.

## Recent Releases
 - 2.0.27 was released on 2022-06-07.
 - meecrowave-1.2.14 was released on 2022-05-11.
 - 2.0.26 was released on 2022-02-08.



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


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

## Description:
The mission of Pivot is the creation and maintenance of software related to 
Rich Internet applications in Java

## Project Status:
Current project status: The project is very quiet currently. No appreciable
activity in the last couple of years, apart from some discussion of a security
problem last quarter.
Issues for the board: As noted in the board comments from last time, a dev@
email should go out (again) related to probable move to the Attic.

## Membership Data:
Apache Pivot was founded 2009-12-15 (14 years ago)
There are currently 10 committers and 7 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 Gavin McDonald on 2022-04-13.
- No new committers. Last addition was Gavin McDonald on 2022-04-14.

## Project Activity:
Essentially nothing since the last report. Since it has only been two months
since the last (delayed) status, nothing has happened. Expect a new dev@
mailing this week about a move to the Attic. I also expect to make some new
commits now that summer is here and there is a little more time.

## Community Health:
There is sufficient oversight still on the PMC, but we are essentially
finished, with the (increasingly unlikely) potential to make a terminal
release (now delayed by 3-4 years).


-----------------------------------------
Attachment BG: Report from the Apache PLC4X Project  [Christofer Dutz]

## 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-17 (4 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-10-01.
- No new committers. Last addition was Jinlin Hong on 2022-11-02.

Even if we managed to attract some new folks after switching to GitHub 
Issues, PRs and Discussions, still we haven't identified anyone to invite as 
committer or promote to PMC membership. But we know that it would be good 
for the project and we're keeping an eye on potential candidates.

And regarding diversity of the PMC and committership, nothing has changed 
and from the active members of our community not more than one person works 
for the same company.

## Project Activity:
There have been multiple initiatives from the community. Probably the most note-
worthy would be an updated S7 driver able to do cyclic communication. A new 
Apache Hop integration and updates to the EtherNet/IP driver. Currently there 
is one ongoing initiative to bring the Profinet driver forward.

Unfortunately, some of these have brought the project in a somewhat unstable
state and we'll be investing quite some time to re-stabilize this in the 
next few months.

In PLC4Go a lot of work has been put into streamlining the API, SPI and the
C-Bus driver, fixing issues with edge cases and fixing several bugs. Test 
got extended greatly which lead now to a coverage above 80% in the above 
mentioned components.

We are also planning on investing some time to refactor some of the core 
mechanisms to handle multi-connection drivers.

## Community Health:
Commit-activity has increased by 34% in the last quarter and we have 15 
individual contributors on file. Communication has decreased by 18%, but 
is still at levels we would still call ok (540 vs 653). This quarter we 
added Github Discussions as new communication channel and are starting to
use it.


-----------------------------------------
Attachment BH: 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 (23 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:
The project has released two APR versions this quarter, 1.7.3 with bugfixes and 
improvements (no security issue) and 1.7.4 to address a regression in 1.7.3.
An apr-1.8.0 version is being prepared with no (needed) rush.

## Community Health:
The project remains healthy, though quiet.
Low to moderate (at release time) activity on the dev@ mailing list.
Low activity on bugzilla/github too, vendors/distros usually provide the patch 
to build with new versions of a dependency software when a compatibility issue 
arises.


-----------------------------------------
Attachment BI: 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:
Apache Pluto is a stable implementation of a JCP standard and is currently in
a maintenance mode. As a mature project, issues are rarely filed by the
community. The annual release is scheduled for Q4 2023, which is expected to
simply be an update of 3rd party dependencies if any security vulnerabilities
are reported by that time.

Issues for the board: No issues at this time.

## Membership Data:
Apache Portals was founded 2004-02-17 (19 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:
There has been no project activity since the last report. Since the project is
in maintenance mode, activity will typically only occur at the time of the
annual release.

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

  - 3.0.0 was released on May 2nd 2023
    This was the first LTS release and the first time the Pulsar community
    committed to a specific scheduled date plan.
  - 2.10.4 was released on April 18th 2023
  - 2.9.5 was released on April 19th 2023
  - 2.11.1 was released on April 18th 2023

  - Pulsar C++ releases:
    - 3.2.0 on May 15th 2023

  - Pulsar Python releases:
    - 3.2.0 was released on June 4th 2023

  - Pulsar reactive client:
    - 0.3.0 was released on April 26th 2023
   
  - Pulsar NodeJS client:
    - 1.8.2 was released on April 20th 2023


  - We continue to have a very high number of "Pulsar Improvement
    Proposal" getting submitted, discussed and voted by the
    community:
    

    PIP-260: Client consumer filter received messages PIP Stale
    PIP-261: Restructure Getting Started section
    PIP-262: A limitation for the max size of ack records to persistent PIP
             Stale
    PIP-264: Enhanced OTel-based metric system
    PIP-265: PR-based system for managing and reviewing PIPs
    PIP-266: Support batch deletion of tenants, namespaces, topics, and
             subscriptions using input files and regex in Pulsar CLI
    PIP-267: Support multi-topic messageId deserialization to ack messages
    PIP-266: Support batch deletion of tenants, namespaces, topics, and
             subscriptions using input files and regex in Pulsar CLI 
    PIP-268: Add support of topic stats/stats-internal using client api 
    PIP-269: Add an epoch of cursor to discard outdated reading
    PIP-270 Add config to set metadata size threshold for compression.
    PIP-271: Add broker health check status into prometheus metrics
    PIP-272: Add stateStorageConfig to WorkerConfig
    PIP-274: Add metric prefix for topic_load_times 

  - Pulsar has reached 623 contributors on the main Github repo
    (It was 604 contributors in March 2023)


## 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 (4 years ago)

  There are currently 75 committers and 37 PMC members in this project.
  The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
 * Qiang Zhao was added to the PMC on 2023-03-28
 * No new committers. Last addition was Yuri Mizushima on 2023-02-22.
   There are though several discussions and open votes for new committers.

## 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:
    - 25% decrease in traffic in the past quarter (72 emails compared to 96):

 - dev@pulsar.apache.org:
    - 16% increase in traffic in the past quarter (1062 emails compared to 914)


## Slack activity:
  - 9807 Members (9672 in March 2023)
  - 222 Active weekly users (212 in December 2022)


## GitHub activity:
 - 823 commits in the past quarter (-23% change)
 - 95 code contributors in the past quarter (-14% change)
 - 525 PRs opened on GitHub, past quarter (-21% change)
 - 518 PRs closed on GitHub, past quarter (-18% change)
 - 239 issues opened on GitHub, past quarter (-23% change)
 - 337 issues closed on GitHub, past quarter (27% increase)


-----------------------------------------
Attachment BK: Report from the Apache Royale Project  [Piotr Zarzycki]

## 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: 
No new PMC members. 
Last addition was Hugo Ferreira on 2022-10-27. 
No new committers. 
Last addition was María José Esteve on 2021-11-23.

Last release of Apache Royale 0.9.10 was on June 05 2023.

Issues for the board: no issue at this moment

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

## Project Activity:
In the result of team effort Apache Royale was successfully released on June
5th. This is the first release performed on a new Azure CI instance. We now
have two functional CIs owned by different PMC members. This should help both
in reducing the project's dependency on a single PMC member, and in dealing
with downtimes of the older CI. We have provided a new version with various
fixes in emulation component and Jewel module. Improvement was also provided
in RoyaleUnit. In addition, significant efforts have been made to ensure
binary reproducibility. With the next release we are going to continue
providing fixes and improvements according to need of our users in their
projects. One of our PMC members shared his large application written fully in
Apache Royale - deployed across Mobile and Desktop.

## Community Health:
We are seeing fewer emails in our Users list, while our development list is
more active recently.


-----------------------------------------
Attachment BL: Report from the Apache SeaTunnel Project  [Calvin Kirs]

## Description:

SeaTunnel is a very easy-to-use, ultra-high-performance, distributed data
integration platform that supports real-time synchronization of massive
data.It can synchronize tens of billions of data stably and efficiently every
day,and it has been used by more and more companies.

## Project Status:

Current project status: Apache SeaTunnel Ongoing with high, we have 145 issues
closed and 160 PRs closed Issues for the board: None

## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (a month 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 (project graduated recently).
- No new committers were added.

## Project Activity:
We are currently releasing version 2.3.2
Shenzhen SeaTunnel meetup
Hangzhou Meetup is currently preparing

## Community Health:

The community ushers in 13 new contributors, bringing the total number to 189
now,160+ pull requests have been merged since SeaTunnel entered the last
report.

dev@seatunnel.apache.org Found 85 emails by 28 authors, divided into 26
topics.


-----------------------------------------
Attachment BM: Report from the Apache Serf Project  [Justin Erenkrantz]


-----------------------------------------
Attachment BN: 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:
No issue requiring board attention.

## Membership Data:
Apache ServiceMix was founded 2007-09-19 (16 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:
Recent releases:
- bundles-2023.04 was released on 2023-05-29.
- bundles-2023.03 was released on 2023-04-22.
- bundles-2023.02 was released on 2023-03-25.

## Community Health:
We had a discussion on the dev mailing list to "move" ServiceMix (main
distribution) in Apache Karaf as karaf-integration distribution. It has been
accepted and the Karaf community will work on it and provide this
distribution. Once done, we will announce this distribution on ServiceMix
mailing lists and website. That's the first step of the "move" to Apache
Karaf. The second step will the ServiceMix Bundles using the new "bundle"
handler/deployer in development at Karaf.


-----------------------------------------
Attachment BO: 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: 
We have no issues that require Board assistance at this time.

## Membership Data:
Apache Shiro was founded 2010-09-21 (13 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 actively working on 2.0, and 1.x is in maintenance mode.
- 2.0.0-alpha-2 was released on 2023-05-04
- patch releases for v1 and v2 are expected shortly

## Community Health:
- Mailing list traffic is down a bit this quarter.
- Shiro recently started using GitHub Issues. Hopefully, this makes it easier 
for folks to report issues (or otherwise contribute).


-----------------------------------------
Attachment BP: 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: working on v4.1.0
Issues for the board: N.A


## Membership Data:
Apache SINGA was founded 2019-10-16 (3 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.0.0 on 07 April 2023.

In the past quarter, the community is fixing some bugs of V4.0.0, as well as
working on the following features/changes:

* Adding support for deep learning models to run on top of PostgreSQL
* Adding support for more flexible setting of training configurations for
  models
* Adding an example for the healthcare malaria detection
* Adding implementations for adaptive relation modeling for structured data
* Continue optimizing the distributed training

## Community Health:
According to the statistic, there are increases of email traffic, code
contributors, closed Github issues and PR activities, which shows that the
community is active in the development and more people are interested in the
development of SINGA.


-----------------------------------------
Attachment BQ: 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, with moderate activity.
Issues for the board: none.

## Membership Data:
Apache Sling was founded 2009-06-17 (14 years ago)
There are currently 49 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 Joerg Hoh on 2022-06-13.
- No new committers. Last addition was Julian Reschke on 2023-02-08.

## Project Activity:
We released version 12 of our sample application, the Sling Starter, on March
18th, 2022. We have not yet made plans for version 13, but individual modules
are being developed and released, with 34 releases for this reporting period.

We have migrated the modules part of the Sling Starter application to use the
newer Jakarta JSON APIs.

adaptTo(), a conference that, amongst others, targets Apache Sling enthusiasts,
will take place 25th-27th September 2023 at KulturBrauerei in Berlin.

## Community Health:
The community activity is at a healthy level and has bounced back compared to
last quarter.

Some of this is related to activating automatic updates for the Sling Starter
repository using renovate, but at the same time we saw the number of
contributors increasing by 33% to 36, and also more Jira activity ( 99 issues
openend, 11% more).


-----------------------------------------
Attachment BR: Report from the Apache SpamAssassin Project  [Sidney Markowitz]

Apache SpamAssassin report to Board for June 2023

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.

Status and health report:

The project activities, including running our rule update infrastructure
and our dev and user mailing lists, are continuing smoothly.

Primary focus for development is now ongoing maintenance bug fixes to
the recently released 4.0.0.

Releases:

Last release: Apache SpamAssassin version 4.0.0 on 17 December 2022.

Note that we maintain online rule updates that are continuously updated
through a combination of developer contributions and automated
processing via our mass-check facility.

Committer/PMC changes:

Most recent new committer:

Paul Stead (pds) 12 September 2018

Most recent new PMC members:

Paul Stead (pds) 23 March 2021


-----------------------------------------
Attachment BS: Report from the Apache Storm Project  [P. Taylor Goetz]


-----------------------------------------
Attachment BT: Report from the Apache Submarine Project  [Liu Xun]

## Description:
The mission of Apache Submarine is the creation and maintenance of software 
related to allowing infrastructure engineers and data scientists to build deep 
learning applications (TensorFlow, PyTorch, etc.) end to end on cluster 
management platforms (like YARN/K8s)

## Project Status:
Current project status: Ongoing: low activity
Issues for the board: Only a few companies are using the open source project,
 and many Chinese developers have reduced their work on the project 
due to the deteriorating working environment

## Membership Data:
Apache Submarine was founded 2019-10-16 (4 years ago)
There are currently 36 committers and 11 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 Xiang Chen on 2023-01-06.
- No new committers. Last addition was Brandon Lin on 2022-07-26.

## Project Activity:
The functions of the current project can meet the needs of use, 
so there is no new function to add.

## Community Health:
The community is considering being able to support OpenAI, 
large model training, and the combination. 
I got some good feedback from developers and hope to 
add vitality to the project.


-----------------------------------------
Attachment BU: Report from the Apache Synapse Project  [Isuru Udana]

## Description:
Apache Synapse is a high-performance, flexible, lightweight
Enterprise Service Bus (ESB) and a mediation framework.

## Project Status:
Ongoing

## Membership Data:
Apache Synapse was founded 2007-12-19 (15 years ago)
There are currently 36 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is 4:3.

Community changes, past quarter:
- No new PMC members. Last addition was Shafreen on 2021-05-09.
- No new committers. Last addition was Nuwan Jayawardene on 2022-11-19.

## Project Activity:
We managed to complete the long waited Synapse 3.0.2 release in May. 
It was done almost after 6 years.
Now we need to work on automating the release process to 
make it simpler to do a release.  


## Community Health:
dev@synapse.apache.org had a 204% increase in traffic in the past quarter (61
emails compared to 20) 
2 issues opened in JIRA, past quarter (200% increase) 
8 issues closed in JIRA, past quarter (800% increase) 
15 commits in the past quarter (200% increase) 
2 code contributors in the past quarter (100% increase) 
7 PRs opened on GitHub, past quarter (133% increase) 6 PRs closed on
GitHub, past quarter (200% increase)

All stats have gone up due to the activities related to the last release.


-----------------------------------------
Attachment BV: Report from the Apache Tomcat Project  [Mladen Turk]

## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation
and Jakarta EE equivalents.

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

## Membership Data:
- Apache Tomcat was founded 2005-05-18 (18 years ago)
- There are currently 48 committers and 29 PMC members in this project.
- Han Li was added to the PMC on 2023-03-06.
- No new committers. Last addition was Han Li on 2022-08-23.


## Project Activity:
- Apache Tomcat 11.0.0-M7 was released on 2023-06-08.
This release is a milestone release and is targeted at Jakarta EE 11.
- Apache Tomcat 10.1.10 was released on 2023-06-12.
- Apache Tomcat 10.1.9 was released on 2023-05-19.
- Apache Tomcat 10.1.8 was released on 2023-04-19.
- Apache Tomcat 9.0.76 was released on 2023-06-09.
- Apache Tomcat 9.0.75 was released on 2023-05-10.
- Apache Tomcat 9.0.74 was released on 2023-04-18.
- Apache Tomcat 8.5.90 was released on 2023-06-12.
- Apache Tomcat 8.5.89 was released on 2023-05-19.
- Apache Tomcat 8.5.88 was released on 2023-04-18.
- Apache Tomcat Native 2.0.4 was released on 2023-06-02.
- Apache Tomcat Native 1.2.37 was released on 2023-06-02.

## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- The Apache Tomcat will end support for
Apache Tomcat 8.5.x on 31 March 2024.
https://tomcat.apache.org/tomcat-85-eol.html

## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.


-----------------------------------------
Attachment BW: Report from the Apache TomEE Project  [David Blevins]

## Description:

Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.

## Health

Contributions over the last quarter have been slower over the previous
quarter.  I suspect some of this is due people focusing on other initiatives
post-TomEE 9.0.0 final release.  TomEE 9 took nearly 3 years and was
effectively created twice due to the change of direction in how we approached
the javax-to-jakarta migration.

We had noted issues with build times taking excessively long due to the size
of our codebase and age of the build machines, which are over 10 years old.
The project is currently incorporating the recently completed work to enable
builds in AWS, which should have very significant impact the project as we
struggle with 5-hour builds on any change.

The project would like to send great thanks to all the Infra team for thier
support and bringing this to life.  We are very excited and look forward to
reporting more on this in future reports.

## Activity

Work on TomEE 10 did start immediately after the release of TomEE 9.0.0 with
a handful of PRs to increase the level of various specifications and upgrade
to the newest implementations.  Unfortunately, nearly all the PRs broke the
build and we quickly wound up with a few hundred test failures.  We did have
this exact experience at the start of TomEE 9 and the build ended up staying
broken for over a year.  The 5-hour build time did contribute to that, though
is not the cause.  The cause is as stated in the previous report; PRs that
break the build being submitted and merged and the submitter infrequently
helping to address the failures.  An attempt to manage this was made by
putting all the broken PRs into a dedicated branch, so work could continue in
main.  The obvious impact the temporary branch had 90% of the activity and
work could not happen on main without merge conflicts.  It was pointed out as
a bad idea and the temporary branch with all the broken PRs was closed and
people were told to resubmit their PRs to main once they are able to pass a
build.  So far no one has done this and work on Jakarta EE 10 remains nacent.
We do think the shorter build times made possible through Infra's AWS work
will have positive impact.  Most the PRs that break the build come from
well-meaning contributors who don't have that much time to contribute.  These
people, who only have a few hours to spare, are the most impacted by the
several-hour build times.

Most work has been on maintenance of TomEE 9, which relied on the now
discontinued Tomcat 10.0.  To remedy this a TomEE 9.1 release was created
based on Tomcat 10.1, which is actively maintained.  The impact of this is
that TomEE 9.1.0 can no longer be Jakarta EE 9.1 certified as Tomcat 10.1
uses a newer Servlet version than is allowed in a Jakarta EE 9.1 certified
implementation (TomEE 9.0.0).  This unfortunately means our celebration about
being Java EE / Jakarta EE certified again after more than 10 years was very
short lived; about 4 months.  Our next chance will be when TomEE 10 is
complete, which will likely be at least another year or more.

The project concluded discussions on end-of-life policies, which were
mentioned last report.  As noted the paragraph above, maintaining releases is
signficantly harder.  Most patches cannot be backported due to changes in the
javax-to-jakarta namespace.  Most libraries are in a great deal of flux in
how they intend to manage old javax code vs newer jakarta code.  The result
is libraries we need (old and new) are getting dropped, patches can't easily
be backported and all maintenance is harder.

The end-of-life policy decided on is to maintian the current major release
and discontinue the previous major release six months after the new major
version goes final.  We think this more honestly reflects the resources we
have based on the contributions we get.  The end-of-life policy adopted for
TomEE 8 is longer, however, and goes till December 31st, 2023.  This was
published in March and we hope that it gives people the awareness they need
to spend the year migrating.

## PMC changes:

- Currently 13 PMC members.
- Last PMC addition Richard Zowalla on May 23rd, 2022

## Committer base changes:

- Currently 33 committers.
- Last committer added was Richard Zowalla on January 6th 2021

## Releases:

- Apache TomEE 8.0.15 on May 17, 2023
- Jakarta EE API 9.1.1 on May 21, 2023
- Apache TomEE 9.1.0 on June 12, 2023


-----------------------------------------
Attachment BX: 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 with active contributions.

Issues for the board: nothing atm

## Membership Data:
Apache TVM was founded 2020-11-17 (3 years ago)
There are currently 70 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 xinqi on 2023-01-31.
- Zihao Ye was added as committer on 2023-04-15
- Jiang Jiajun was added as committer on 2023-06-03
- Nicola Lancellotti was added as committer on 2023-05-02
- Anirudh Sundar Subramaniam was added as committer on 2023-05-12

There are also on going discussions on new members.

## Project Activity:

Recent releases:
- 0.12.0 was released on 2023-05-13.
- 0.11.0 was released on 2023-03-09.


The project continues to make strides on various fronts. There are several
improvements in frontends and TensorIR. The unity branch development also
starts gaining community traction, especially in enabling new emerging
areas, such as large-language and stable diffusion models that show value to
the community. 

The community also continues to publish tutorials to help community members to
get updates on the latest unity development. Specifically, tutorials on BYOC
(bring your own codegen) as well as vertical-focused applications such as
how to run language models.

## Community Health:

Overall we get ~150 commits from ~50 authors monthly. We also start to see a a
growing interest in TVM unity branch to enable stable diffusion and language
models.

Recap on TVMCon: the talks at TVMCon are now online at https://www.tvmcon.org/
This year we had speakers from diverse backgrounds in industry and academia
talking about their use in TVM and ML compilation in general. One highlight
was the ability to leverage TVM and bring models like stable diffusion onto
server, web browsers and eventually mobile devices.

Bringing in new members: the PMC is mindful in welcoming new contributors and
members and bring a healthy community. One recent priority of some of us is to
bring volunteer contributors from different backgrounds. These contributors
usually have more spread-out contributions but are super valuable to the
community. We identified several such members in the past quarters and would
strive to continue to do so. The unity branch development also serves as a way
to encourage new members of the community to participate in the emerging areas
they are interested in, hopefully bringing a broader set of members to the
community.

Supporting the community in the age of generative AI: with the arrival of
generative AI, such as stable diffusion and language models, the community's
interest also start to arise in these new domains. Supporting these new models
require different technical considerations from the traditional models we
support. Unity branch development brings these new capabilities to the
community. We have seen growing community interest in related areas and unity
development, with active recent community meetups and contributions to support
LLMs.


-----------------------------------------
Attachment BY: 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: none

## Membership Data:
Apache UIMA was founded 2010-03-17 (13 years ago)
There are currently 26 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- Pablo Duboue was added to the PMC on 2023-03-07
- Pablo Duboue was added as committer on 2023-03-06

## Project Activity:
There have been no releases during this reporting period.

## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list, but not much overall.


-----------------------------------------
Attachment BZ: 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 high activity
Issues for the board: none

## Membership Data:
Apache Unomi was founded 2019-02-20 (4 years ago)
There are currently 16 committers and 7 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 Taybou on 2021-03-19.
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.

## Project Activity:
We have released two versions since the last report:
- On the maintenance branch: 1.9.0 which contains some bug fixes, performance
  improvements and library upgrades
- On the main branch: 2.3.0 which contains the same improvements as 1.9.0 as
  well as new features such as an event validation service, other libraries
  upgrades and stability and performance improvements.

Work is still very active on the main branch, developing new features and
improving migration from the older branch as well as a strong focus on
providing updates for maintenance as well are quite nice to see.

## Community Health:

We are seeing regular activity in the Unomi Slack channel from both existing
and new users. We are seeing less active users answer newcomers with is as
well, a good thing. All the main required communication is still happening on
the mailing lists. Here are some stats:

- dev@unomi.apache.org had a 48% increase in traffic in the past quarter (676
  emails compared to 454)
- 34 issues opened in JIRA, past quarter (30% increase)
- 33 issues closed in JIRA, past quarter (83% increase)
- 89 commits in the past quarter (7% increase)
- 9 code contributors in the past quarter (-18% change)
- 40 PRs opened on GitHub, past quarter (33% increase)
- 45 PRs closed on GitHub, past quarter (66% increase)


-----------------------------------------
Attachment CA: 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: Dormant
Issues for the board: There are no issues requiring board attention.

## Membership Data:
Apache VCL was founded 2012-06-19 (11 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:
- Last release: 2019-07-25
- We are in the same state as given on our last board report.  There has been
  little project activity since our last board report. As before, current
  committers are hopeful to get back to development soon.  We are very aware
  of how long it has been since our last release.

## Community Health:
I like the addition of the project status with the option of specifying
dormant.  That's where the VCL community is though we have hopes of becoming
more active again.


-----------------------------------------
Attachment CB: Report from the Apache Velocity Project  [Nathan Bubna]

## Description:
The mission of Velocity is the creation and maintenance of software related to 
A Java Templating Engine

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

## Membership Data:
Apache Velocity was founded 2006-10-24 (17 years ago)
There are currently 15 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 5:3.

Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Thomas Mortagne on 2020-03-09.

## Project Activity:
Recently voted (03-25-2023) to release a new master POM file in anticipation
of a few upcoming releases.

## Community Health:
Most work is being handled by two PMC members. Others are tracking
conversations but dormant, as usual.


-----------------------------------------
Attachment CC: Report from the Apache Wicket Project  [Andrea Del Bene]

## Description:
The mission of Wicket is the creation and maintenance of software related to 
Component-based Java Web Application Framework.

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

## Membership Data:
Apache Wicket was founded 2007-06-20 (16 years ago)
There are currently 33 committers and 32 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 Thomas Heigl on 2020-08-14.
- No new committers. Last addition was Thomas Heigl on 2020-05-18.

## Project Activity:

During the last quarter we released versions:

- 9.12.0 on 2022-10-15
- 9.13.0 on 2023-04-18
- 9.14.0 on 2023-05-28

We released also version 8.15.0 on 2023-05-02 for 8.x branch. 
Talking about our next main release (wicket 10), as of the writing of this 
report we have the first 10 milestone under vote and we should release it 
in the very next days. Needles to say that we are eager to receive feedback 
from our community about this first release of the 10.x branch :-) .
  
## Community Health:
Our community remains healthy and collaborative, with an increasing number of 
PRs on GitHub. As we said in the last report, there are a number of external
contributors interested in testing Wicket 10 M1 with other OOS projects.
One of them,  Richard Eckart de Castilho, is taking part to the M1 vote.
This is particular important as some of these projects (like Spring Boot 3,
 Hibernate 6) have already moved to Jakarta EE like we did with Wicket 10.


-----------------------------------------
Attachment CD: Report from the Apache Yetus Project  [Allen Wittenauer]

## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.

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

In the last report the board asked the following question:

> It's been a long time since you have added any committer or
> PMC members. Do you have any candidates you can consider or
> perhaps it time to consider lowering the bar to those
> positions?

The vast majority of people who contribute that are not already
committers or PMC are "drive-by" contributors.  They submit one
or two patches and are never heard from again. Therefore, no,
there are no candidates in the pipeline and there are no considerations
for lowering the bar at the present time.

## Membership Data:
Apache Yetus was founded 2015-09-15 (8 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:

0.14.1 was released on 2022-10-17.

Work has started on getting a new release out soon-ish, primarily
geared towards updating the container images and a few tweaks for
private repositories.

## Community Health:

As usual when releases start to happen, activity goes up:

12 issues opened in JIRA, past quarter (300% increase)
7 issues closed in JIRA, past quarter (600% increase)


-----------------------------------------
Attachment CE: Report from the Apache ZooKeeper Project  [Flavio Paiva Junqueira]

## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.

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

## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (13 years ago)
There are currently 32 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Mate Szalay-Beko on 2022-03-28.
- Li Wang was added as committer on 2023-03-17

## Project Activity:
The most recent release is 3.8.1, which was released on 2023-01-30. There
is an ongoing thread about cutting a 3.9.0 major release, and minor releases
for the 3.7.and 3.8 branches.

## Community Health:
We have added a new committer, and the community is discussing the scope
and management of upcoming releases, major and minor. The dev traffic metrics
are low, and it is possibly due to the absence of release in the period. User
traffic has increased compared to the previous period.

- dev@zookeeper.apache.org had a 73% decrease in traffic
in the past quarter (47 emails compared to 168)
- notifications@zookeeper.apache.org had a 64% decrease
in traffic in the past quarter (131 emails compared to 359)
- user@zookeeper.apache.org had a 106% increase in traffic
in the past quarter (31 emails compared to 15)
- 23 issues opened in JIRA, past quarter (-32% change)
- 27 issues closed in JIRA, past quarter (-3% change)
- 7 commits in the past quarter (-91% change)
- 4 code contributors in the past quarter (-78% change)
- 15 PRs opened on GitHub, past quarter (-51% change)
- 11 PRs closed on GitHub, past quarter (-71% change)


------------------------------------------------------
End of minutes for the June 21, 2023 board meeting.

Index

• Call to order
• Roll Call
• Minutes from previous meetings
• The meeting of May 17, 2023
• Executive Officer Reports
• Board Chair [Sander Striker]
• President [David Nalley]
• Treasurer [Craig R. McClanahan]
• Secretary [Matt Sicker]
• Executive Vice President [Ruth Suehle]
• Vice Chair [Sharan Foga]
• Additional Officer Reports
• VP of W3C Relations [Andy Seaborne / Shane]
• Apache Legal Affairs Committee [Roman Shaposhnik / Craig]
• Apache Security Team Project [Mark J. Cox / Rich]
• VP of Jakarta EE Relations [Rob Tompkins / Christofer]
• Committee Reports
• Apache Any23 Project [Lewis John McGibbney / Willem]
• Apache Bloodhound Project [Gary Martin / Christofer]
• Apache Giraph Project [Dionysios Logothetis / Christofer]
• Apache Libcloud Project [Tomaž Muraus / Shane]
• Apache Lucene.Net Project [Shad Storhaug / Sander]
• Apache Pig Project [Koji Noguchi / Craig]
• Apache Serf Project [Justin Erenkrantz / Rich]
• Apache Storm Project [P. Taylor Goetz / Craig]
• Special Orders
• Terminate the Apache Any23 Project
• Change the Apache SeaTunnel Project Chair
• Change the Apache BookKeeper Project Chair
• Establish the Apache Kvrocks Project
• Change the Apache Brooklyn Project Chair
• Establish Position of VP, Public Policy
• Discussion Items
• Budget
• Public Policy Position
• 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 Conferences [Rich Bowen]
• Report from the Apache Travel Assistance Committee [Gavin McDonald]
• Report from the VP of Diversity and Inclusion [Katia Rojas]
• Report from the VP of Data Privacy [Christian Grobmeier]
• 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 VP of Jakarta EE Relations [Rob Tompkins]
• Report from the Apache Airflow Project [Bolke de Bruin]
• Report from the Apache Allura Project [David Philip Brondsema]
• Report from the Apache Ambari Project [Roman Shaposhnik]
• Report from the Apache Ant Project [Jan Materne]
• Report from the Apache Any23 Project [Lewis John McGibbney]
• Report from the Apache Archiva Project [Olivier Lamy]
• Report from the Apache Atlas Project [Madhan Neethiraj]
• Report from the Apache Axis Project [Robert Lazarski]
• Report from the Apache Bahir Project [João Boto]
• Report from the Apache Beam Project [Kenneth Knowles]
• Report from the Apache Bigtop Project [Yuqi Gu]
• Report from the Apache Bloodhound Project [Gary Martin]
• 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 [Rohit Yadav]
• Report from the Apache Commons Project [Gary D. Gregory]
• Report from the Apache Cordova Project [Jesse MacFadyen]
• Report from the Apache CouchDB Project [Jan Lehnardt]
• 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 DeltaSpike Project [Mark Struberg]
• Report from the Apache ECharts Project [Wenli Zhang]
• Report from the Apache EventMesh Project [Eason Chen]
• Report from the Apache Felix Project [Karl Pauls]
• Report from the Apache Flagon Project [Joshua C. Poore]
• Report from the Apache Flex Project [Harbs]
• Report from the Apache Flink Project [Robert Metzger]
• Report from the Apache Giraph Project [Dionysios Logothetis]
• Report from the Apache Gobblin Project [Abhishek Tiwari]
• Report from the Apache Gora Project [Kevin Ratnasekera]
• 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]
• -- Baremaps
• -- KIE
• -- Nemo
• -- NLPCraft
• -- OpenDAL
• -- Paimon
• -- SDAP
• -- Uniffle
• -- Wayang
• Report from the Apache IoTDB Project [Xiangdong Huang]
• Report from the Apache Jackrabbit Project [Marcel Reutegger]
• Report from the Apache Karaf Project [Jean-Baptiste Onofré]
• Report from the Apache Kibble Project [Sharan Foga]
• Report from the Apache Kyuubi Project [Kent Yao]
• Report from the Apache Libcloud Project [Tomaž Muraus]
• Report from the Apache Linkis Project [Shuai Di]
• Report from the Apache Lucene Project [Greg Miller]
• Report from the Apache Lucene.Net Project [Shad Storhaug]
• Report from the Apache Mnemonic Project [Yanhui Zhao]
• Report from the Apache MXNet Project [Sheng Zha]
• 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 OpenNLP Project [Jeff Zemerick]
• Report from the Apache OpenWebBeans Project [Mark Struberg]
• Report from the Apache Pig Project [Koji Noguchi]
• Report from the Apache Pivot Project [Roger Lee Whitcomb]
• Report from the Apache PLC4X Project [Christofer Dutz]
• Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
• Report from the Apache Portals Project [Neil Griffin]
• Report from the Apache Pulsar Project [Matteo Merli]
• Report from the Apache Royale Project [Piotr Zarzycki]
• Report from the Apache SeaTunnel Project [Calvin Kirs]
• Report from the Apache Serf Project [Justin Erenkrantz]
• 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 [P. Taylor Goetz]
• Report from the Apache Submarine Project [Liu Xun]
• Report from the Apache Synapse Project [Isuru Udana]
• Report from the Apache Tomcat Project [Mladen Turk]
• Report from the Apache TomEE Project [David Blevins]
• Report from the Apache TVM Project [Tianqi Chen]
• Report from the Apache UIMA Project [Richard Eckart de Castilho]
• Report from the Apache Unomi Project [Serge Huber]
• Report from the Apache VCL Project [Josh Thompson]
• Report from the Apache Velocity Project [Nathan Bubna]
• 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]