The Apache Software Foundation Board of Directors Meeting Minutes January 15, 2025 1. Call to order The meeting was scheduled for 21:00 UTC and began at 21:01 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/44h5 The meeting was held via teleconference, hosted by the Secretary via Zoom. The #asfboard channel on the-asf.slack.com was used for backup. 2. Roll Call Directors Present: Rich Bowen Shane Curcuru Willem Ning Jiang Justin Mclean Jean-Baptiste Onofré Craig L Russell Sander Striker Kanchana Pradeepika Welagedara - joined :02 Directors Absent: Jeff Jirsa Executive Officers Present: Craig R. McClanahan Matt Sicker Ruth Suehle Executive Officers Absent: David Nalley Guests: Alin Jerpelea Brian E Fox Chris Lambertus Christopher Schultz Daniel Gruno Drew Foulks Gavin McDonald Greg Stein Herve Boutemy Jacob Wujciak Julien Le Dem Melissa Logan Paul King - joined :02 Sally Khudairi Zili Chen 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of December 18, 2024 See: board_minutes_2024_12_18.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Shane Curcuru] While our contributors continue work on ASF projects, our volunteer officers and Members continue the work of our corporate being: corporate filings, budget planning, and maintaining our infrastructure and operations that provide support to all our communities. Last month the board appointed a VP of ECMA Relations, and we will be applying as a non-profit member there, giving ASF projects a way to work on the Technical Committees of some key standards. Our VP, Public Affairs and a team of volunteers have also submitted commentary on a recent US DOD proposed rule for federal vendors that would require onerous reporting duties. Our comments [1] make clear the need for explicit carve-outs for open source software, and clarity around the rule's definition of "open source" itself. [1] https://www.regulations.gov/comment/DARS-2024-0034-0003 B. President [Ruth Suehle] Everyone has really started the new year on a roll, which is fantastic. We should have a Community Over Code venue secured by the end of the month, are working on interviewing tooling candidates, and some officers have been getting requests from folks who would like to shadow them. At the ops officers most recent meeting, a few things were discussed, including: - Solidifying a rotation of officer reports to the board. We started this but got out of the cycle. Ideally we plan them out for the year so that nobody's surprised by a "can you come next week" kind of request. - Rich Bowen was in attendance and volunteered to create a set of questions for all board nominees to answer in the coming cycle for members to review in considering their votes. We've also begun the budget planning process for the coming fiscal year. Officers will be making their requests by the next ops meeting, which means I should have something for the board to discuss by the February meeting. Because we won't have an EU event in early summer for a board F2F, we'll need to consider the additional cost of that in budget planning. Additionally, please see Attachments 1 through 10. C. Treasurer [Craig R. McClanahan] Normal operations continue, including working with Fundraising and Infra to set up a couple of new targeted donation sponsorships. D. Secretary [Matt Sicker] In December 2024, the secretary received 30 ICLAs, one CCLA, and one CoI affirmation. E. Executive Vice President [David Nalley] No report was submitted. F. Vice Chair [Justin Mclean] nothing of note to mention Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / JB] See Attachment 11 B. Apache Legal Affairs Committee [Roman Shaposhnik / Willem] See Attachment 12 C. Apache Security Team Project [Mark J. Cox / Shane] See Attachment 13 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Aries [striker, rbowen, jbo] # CarbonData [Kanchana] # DataFu [Kanchana] # Fineract [jmclean] # Griffin [striker] # Hadoop [jmclean] # Maven [jjirsa] # Mesos [rbowen] # Mnemonic [Kanchana] # Pivot [striker] # Web Services [Kanchana] A. Apache Accumulo Project [Ed Coleman / Rich] See Attachment A B. Apache ActiveMQ Project [Bruce Snyder / Sander] See Attachment B C. Apache Airavata Project [Suresh Marru / Jeff] See Attachment C D. Apache Answer Project [Ning Qi / Craig] See Attachment D E. Apache APISIX Project [Ming Wen / Kanchana] See Attachment E F. Apache Aries Project [Christian Schneider / Justin] See Attachment F @Jean-Baptiste: follow up regarding Attic G. Apache Arrow Project [Neal Richardson / JB] See Attachment G H. Apache AsterixDB Project [Till Westmann / Craig] See Attachment H I. Apache Attic Project [Herve Boutemy / Justin] See Attachment I J. Apache Avro Project [Ryan Skraba / Sander] See Attachment J K. Apache bRPC Project [James Ge / Willem] See Attachment K L. Apache Calcite Project [Ruben Q L / Jeff] See Attachment L M. Apache CarbonData Project [Liang Chen / Kanchana] No report was submitted. N. Apache Causeway Project [Jörg Rade / Kanchana] See Attachment N O. Apache Celix Project [Pepijn Noltes / Rich] See Attachment O P. Apache CXF Project [Andriy Redko / Shane] See Attachment P Q. Apache DataFu Project [Eyal Allweil / Kanchana] No report was submitted. @Kanchana: pursue a roll call for DataFu R. Apache DB Project [Bryan Pendleton / Shane] See Attachment R S. Apache Directory Project [Shawn McKinney / Willem] See Attachment S T. Apache DolphinScheduler Project [Lidong Dai / Justin] See Attachment T U. Apache Druid Project [Gian Merlino / Rich] No report was submitted. V. Apache Dubbo Project [Jun Liu / Sander] No report was submitted. W. Apache Fineract Project [James Dailey / Rich] See Attachment W @Kanchana: follow up with PMC Chair and PMC regarding community health X. Apache Flagon Project [Joshua C. Poore / JB] See Attachment X Y. Apache Fluo Project [Keith Turner / Jeff] No report was submitted. Z. Apache Geronimo Project [Jean-Louis Monteiro / Craig] See Attachment Z AA. Apache Griffin Project [William Guo / Sander] See Attachment AA @Sander: pursue a roll call of PMC AB. Apache Hadoop Project [Xiaoqiao He / Rich] See Attachment AB AC. Apache HBase Project [Duo Zhang / Kanchana] See Attachment AC AD. Apache Incubator Project [Justin Mclean] No report was submitted. @Rich: ensure IPMC is helping with board reports AE. Apache InLong Project [Charles Zhang / Willem] See Attachment AE AF. Apache James Project [Benoit Tellier / Justin] No report was submitted. AG. Apache jclouds Project [Andrew Gaul / Willem] See Attachment AG AH. Apache Jena Project [Andy Seaborne / Jeff] See Attachment AH AI. Apache JMeter Project [Bruno Demion / JB] See Attachment AI AJ. Apache Johnzon Project [Jean-Louis Monteiro / Shane] See Attachment AJ AK. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Craig] See Attachment AK AL. Apache Kudu Project [Andrew Wong / Sander] See Attachment AL AM. Apache Libcloud Project [Tomaž Muraus / Justin] No report was submitted. AN. Apache Logo Development Project [Daniel Gruno / Willem] See Attachment AN AO. Apache MADlib Project [Ed Espino / JB] See Attachment AO AP. Apache Mahout Project [Andrew Musselman / Kanchana] See Attachment AP AQ. Apache Maven Project [Karl Heinz Marbaise / Jeff] See Attachment AQ @Jean-Baptiste: follow up regarding Maven Central discussion AR. Apache Mesos Project [Qian Zhang / Craig] See Attachment AR @Rich: follow up with roll call for Mesos PMC AS. Apache MINA Project [Guillaume Nodet / Rich] See Attachment AS AT. Apache Mnemonic Project [Gordon King / Kanchana] No report was submitted. AU. Apache MyFaces Project [Bernd Bohmann / Shane] See Attachment AU AV. Apache NiFi Project [Joe Witt / Justin] See Attachment AV AW. Apache Nutch Project [Sebastian Nagel / Kanchana] See Attachment AW AX. Apache NuttX Project [Alin Jerpelea / Rich] See Attachment AX AY. Apache OpenJPA Project [Mark Struberg / Shane] See Attachment AY AZ. Apache OpenMeetings Project [Maxim Solodovnik / Jeff] See Attachment AZ BA. Apache OpenOffice Project [Dave Fisher / Rich] No report was submitted. BB. Apache OpenWebBeans Project [Mark Struberg / JB] See Attachment BB BC. Apache ORC Project [William Hyun / Sander] See Attachment BC BD. Apache Parquet Project [Julien Le Dem / Willem] See Attachment BD BE. Apache PDFBox Project [Andreas Lehmkühler / Justin] See Attachment BE BF. Apache Petri Project [Dave Fisher / Craig] See Attachment BF BG. Apache Pig Project [Koji Noguchi / Rich] No report was submitted. BH. Apache Pivot Project [Roger Lee Whitcomb / Sander] No report was submitted. BI. Apache Ranger Project [Selvamohan Neethiraj / JB] No report was submitted. BJ. Apache Ratis Project [Tsz-wo Sze / Craig] See Attachment BJ BK. Apache Rya Project [Adina Crainiceanu / Justin] See Attachment BK BL. Apache Samza Project [Jagadish Venkatraman / Willem] No report was submitted. BM. Apache SeaTunnel Project [Jun Gao / Shane] No report was submitted. BN. Apache SkyWalking Project [Sheng Wu / Kanchana] See Attachment BN BO. Apache Steve Project [Daniel Gruno / Jeff] No report was submitted. BP. Apache Struts Project [René Gielen / Rich] See Attachment BP BQ. Apache Synapse Project [Isuru Udana / Sander] See Attachment BQ BR. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Willem] See Attachment BR BS. Apache Tcl Project [Georgios Petasis / Craig] See Attachment BS BT. Apache Tez Project [László Bodor / Justin] No report was submitted. BU. Apache Thrift Project [Jens Geyer / Shane] See Attachment BU BV. Apache Tika Project [Tim Allison / Kanchana] See Attachment BV BW. Apache TinkerPop Project [Kelvin Lawrence / Jeff] See Attachment BW BX. Apache Traffic Server Project [Bryan Call / JB] No report was submitted. BY. Apache Web Services Project [Daniel Kulp / Kanchana] No report was submitted. BZ. Apache Zeppelin Project [Jongyoul Lee / Shane] See Attachment BZ Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache StreamPark 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 Make stream processing easier! Easy-to-use streaming application development framework and operation platform. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache StreamPark Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache StreamPark be and hereby is responsible for the creation and maintenance of software related to Make stream processing easier! Easy-to-use streaming application development framework and operation platform; and be it further RESOLVED, that the office of "Vice President, Apache StreamPark" 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 StreamPark Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache StreamPark 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 StreamPark Project: * Al-assad * ZhouYu Chen * Zili Chen * Ning Guo * Willem Ning Jiang * Shaokang Lv * Chunjin Mu * Huajie Wang * Qingrong wang * Sizhu Wang * Duo Zhang * Yang Zhou NOW, THEREFORE, BE IT FURTHER RESOLVED, that Huajie Wang be appointed to the office of Vice President, Apache StreamPark, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. RESOLVED, that the Apache StreamPark Project be and hereby is tasked with the migration and rationalization of the Apache Incubator StreamPark podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator StreamPark podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7A, Establish the Apache StreamPark Project, was approved by Unanimous Vote of the directors present. B. Terminate the Apache Cocoon Project WHEREAS, the Project Management Committee of the Apache Cocoon 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 Cocoon project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Cocoon 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 Cocoon Project; and be it further RESOLVED, that the office of "Vice President, Apache Cocoon" is hereby terminated; and be it further RESOLVED, that the Apache Cocoon PMC is hereby terminated. Special Order 7B, Terminate the Apache Cocoon Project, was approved by Unanimous Vote of the directors present. C. Change the Apache Petri Project Chair WHEREAS, the Board of Directors heretofore appointed Dave Fisher (wave) to the office of Vice President, Apache Petri, and WHEREAS, the Board of Directors is in receipt of the resignation of Dave Fisher from the office of Vice President, Apache Petri, and WHEREAS, the Project Management Committee of the Apache Petri project has chosen by vote to recommend Greg Stein (gstein) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Dave Fisher is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Petri, and BE IT FURTHER RESOLVED, that Greg Stein be and hereby is appointed to the office of Vice President, Apache Petri, 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 Petri Project Chair, was approved by Unanimous Vote of the directors present. D. Terminate the Apache Pivot Project WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Pivot project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Pivot 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 Pivot Project; and be it further RESOLVED, that the office of "Vice President, Apache Pivot" is hereby terminated; and be it further RESOLVED, that the Apache Pivot PMC is hereby terminated. Special Order 7D, Terminate the Apache Pivot Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Soliciting strategic officer feedback Brief discussion of improving ways to gather strategic feedback from operations officers, both in terms of goals as well as resources needed to meet goals. 9. Review Outstanding Action Items * Justin: follow up with PMC about board report sections [ TomEE 2024-06-19 ] Status: Done * David: follow up with report about shadow infrastructure budget [ President 2024-06-19 ] Status: * Shane: follow up about enforcement for privacy policies [ Data Privacy 2024-07-17 ] Status: Done, conversation about enforcement started: https://lists.apache.org/thread/qfrrhkbonzo335stbrn44f5vg3zszxtw * Shane: update Incubation guidelines to include trademark grant [ Trademark management status briefing VP, Brand Management 2024-07-17 ] Status: * Justin: follow up on issue for board [ Kafka 2024-08-21 ] Status: Done (Infra resolved) * Justin: follow up with trademarks [ RocketMQ 2024-08-21 ] Status: Done * Justin: Discuss reporter tooling requirements [ Shiro 2024-09-18 ] Status: Done (no need for action) * Greg: Write up a proposed resolution to require tooling to validate email [ Discuss list subscription tools 2024-09-18 ] Status: I no longer wish to help the current Board with this. * Jeff: Start discussion of communications on board@ specifically the use of [ New Business 2024-09-18 ] Status: * Kanchana: pursue a roll call for PMC [ CarbonData 2024-10-16 ] Status: Conducted in Nov . used email-template ---> Two responses +1 and -1 : Individual PMC who is active on the project voted +1. AI : Board needs to make the decision if we need to move this project to attic. * Justin: pursue a roll call for PMC [ Libcloud 2024-10-16 ] Status: Roll call sent * Rich: talk with PMC about certification request [ NuttX 2024-10-16 ] Status: Done: https://lists.apache.org/thread/h9tjhbn9x35mvff3rbs3hp89mklj366c -- no response. Closing AI. * Craig McClanahan: pursue an audit on ramp cards [ Review expense accounting categories 2024-10-16 ] Status: * Rich: follow up with updates to reporting tool template regarding statistics [ Druid 2024-11-20 ] Status: Done: The Reporter tool contains the following phrasing: PLEASE DON'T COPY THESE METRICS INTO THE REPORT ALONE! While these metrics might offer insights into the wellbeing of the project, what the board of directors wants to see is the story behind these metrics. Please take some time to explain why these metrics are the way they are, and what this means for the project. If you are unsure how to do this, please take a look at some of the examples provided above (click the button!). * Kanchana: pursue a roll call for Mnemonic [ Mnemonic 2024-11-20 ] Status: Wasn't in the meeting due to power outage , will get to this today. * Rich: follow up with details regarding AI tooling [ Superset 2024-11-20 ] Status: Done: As I understand it, VP Privacy has resolved this conversation with Superset, and it's no longer a Board issue. * Willem: pursue a roll call for PMC [ Portals 2024-12-18 ] Status: Sent out the roll call email https://lists.apache.org/thread/y599spzqom1vxdc83v9tr460rkckpjbw * Craig: follow up with Infra about outstanding issue [ Storm 2024-12-18 ] Status: Done. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 21:38 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period December 2024 * ISSUES FOR THE BOARD None. * OPERATIONS - Rejected HUNTER as a podling name - Provided advice to a vendor regarding use of project and/or foundation logos on their website - Approved UNIFFLE as a podling name - The DORIS PMC addressed some vendor independence issues on the project website - Answered one question about the status of our NIFI trademark - Reviewed two events for ICEBERG - Provided feedback on the OTAVA name search * REGISTRATIONS The GUACAMOLE registration in the US is now complete. The APACHE registration in India is now complete. * INFRINGEMENTS Worked with the LOG4J PMC to resolve an infringing domain name. Worked with the HBASE PMC to try and progress a minor issue. Worked with the GUACAMOLE PMC towards addressing an infringing website. Continue to chase a downstream vendor regarding multiple infringements of ASF marks. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: no new Sponsors were onboarded during this timeframe. b —Renewals: we successfully secured renewal commitments from two Platinum, one Gold, three Silver, and three Bronze Sponsors, and are discussing a possible upgraded renewal with a second Sponsor. c —Payments: 1 —New: we received no new Sponsor payments during this timeframe. 2a —Renewing: we received payment from one renewing Gold, and two renewing Bronze Sponsors. 2b —Incoming: we await payment from two renewing Platinum, two renewing Gold, three renewing Silver, and two renewing Bronze Sponsors. 2) Targeted Sponsors: we are starting up three Targeted Sponsorship renewals. We are also working with a beneficiary PMC on deploying a corporate contribution as a Targeted Sponsorship. 3) Sponsor Relations: we continue communicating regularly with our Sponsors, with a considerable spike in activity to accommodate end-of-year renewals and corporate contributions. We issued the monthly Sponsor update, promoted End-of-Year giving, and also announced new event sponsorship benefits available . 4) Event Sponsorship: we promoted the new additional benefits to ASF Platinum and Gold Sponsors that bridge sponsorship benefits for Community Over Code North America 2025, and liaised interested ASF Sponsors with the ASF Conferences committee. 5) Individual Donations and Corporate Giving: we received $9,480 in online donations via https://donate.apache.org/ , and also received several end-of-year corporate contributions that included volunteer hours donations, matching gifts, and one-time donations (several of which were made by repeat donors). 6) Administrivia: we have been working successfully with the Accounting and Treasury teams towards resolving outstanding invoicing issues and recovering missing payments. We collaborated with Marketing & Publicity on the ASF's End-of-Year giving campaigns, as well as with promoting new ASF Initiative Targeted Sponsorships. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] Foundation Comms * Issued December edition of the Plus One Newsletter which featured a letter from President Ruth Suehle Project Comms * Published project spotlight for Apache CloudStack and promoted across social media channels and featured in Plus One newsletter Foundation Content * Published “CISA Tabletop Exercise Tests Open Source Security Response Procedures” on ASF blog and promoted across social channels * Published blog recapping Community Over Code Keynotes including embedded video links. * Published blog detailing ASF member and former Director Isabel Drost-Fromm speaking before the German Bundestag’s Committee on Digital Affairs Website * Began work to create redirects to old Press pages * Made updates to 25th Anniversary webpage as well as M&P wiki (updating email address to reflect markpub@) Social Media Overview In total, 55 posts were published: 43 Tweets + 12 LinkedIn. Social Highlights (X + LinkedIn) * Total Audience: 141,254# * New Followers in December: 350 * Total Impressions: 88,484 (11.4% increase MoM) * Total Engagements: 3,240 (2.6% decrease MoM) * Post Link Clicks: 1,619 (18.7% decrease MoM) #ASF follower growth is 100% attributed to LinkedIn; ASF growth on Twitter in December was -8 followers. Website Analytics * 678,614 visits, 678,560 unique visitors -24.2% * 2 min 51s average visit duration +7.5% * 49% visits have bounced (left the website after one page) +6.7% * 5.8 actions (page views, downloads, outlinks, internal site searches) per visit -39.6% * 10,003 max actions in one visit (level) * 3,084,018 pageviews, 856,132 unique pageviews -60% * 8 total searches on your website, 3 unique keywords -20% * 276,743 downloads, 197,719 unique downloads -41.6% * 543,134 outlinks, 183,702 unique outlinks +50.3% ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Myrle Krantz] General ======= Infrastructure is operating at reduced staffing, and support gaps are becoming apparent. Hiring is due to commence at the start of Q1 2025, in parallel with the ongoing Tooling hire process. Finances ======== - Infra continues to expect a targeted donation to support replacement of some Cassandra build nodes, but this has not yet occurred. - The HBase targeted donation has expired and those nodes have been decommissioned. - 2024 Personnel-related expenses were under budget due to staffing changes. - Infra sysadmin hiring Q1/2025 will bring staffing budget back to near-baseline. - No decision to backfill the Infra Admin position has been made yet and is not expected in the near term. Hiring ====== - Infra staff developing an updated job description for the open sysadmin position, to hire during Q1 2025. - Tooling hire process is underway by VP Tooling, with candidates being interviewed. Travel ====== - Infra Team F2F likely to happen in April/May 2025. Major Projects ============== - Work is ongoing on the Jira -> GitHub Issues migration tool to fix a number of showstopper problems and improve the process. - In cooperation with a number of volunteers within our Builds/CI community, a process to streamline and democratize the approval of GitHub Actions is in the initial phases of rollout. - Infra continues to work with our partners at Gradle to improve the functionality and performance of our donated Gradle Develocity stack, with a large upgrade scheduled mid-January. - An organization-wide CSP (Content-Security-Policy) is slated to be rolled out on February 1st (brownout), going into full effect on March 1st, 2025. This will effectively block _unapproved_ external sources (such as trackers, font/js CDNs, etc) from our websites until such a point where they have been validated by the Privacy team, whether through DPAs or sufficient anonymization of data. (ref: INFRA-26115) - Next iteration of our .asf.yaml control file for git repositories is to be enabled on January 19th (opt-in for a week, full rollout on Jan 26th). A roundtable session was held on January 8th to inform projects about how they can write or improve features in .asf.yaml themselves going forward. ----------------------------------------- Attachment 5: Report from the VP of Tooling [Dave Fisher] General ====== Tooling began the interview process for a contractor position - Senior Engineer, Tooling. We had over 200 applications and despite the holidays we narrowed our short list to five. We are likely to contract two engineers as combined with existing Budget plus an expected sponsorship our costs will be easily covered for at least 2025. Bootstrap ======= - Tooling mailing lists are created: dev@tooling.apache.org and private@tooling.apache.org - There is a slack channel: #tooling-discuss - An existing discussion infra slack channel is open and renamed #apache-trusted-releases January Goals ========== 1. Begin on boarding of contractor(s) and start organizing requirements. 2. Work on the web presence for https://tooling.apache.org ----------------------------------------- Attachment 6: Report from the VP of Conferences [Brian Proffitt] The Community Over Code Asia 2025 has set their dates for July 25-27, 2025 in Beijing. The call for tracks is underway until January 28, with the CFP scheduled to begin in February. Site visits for Community Over Code NA will be happening January 25-27, so we expect to announce dates and venue soon after, in early February. Call for tracks will go out immediately after, and expect call for presentations to start in late February. There have been some inquiries about Community Over Code EU for 2025. Regretfully, this event will not be happening this coming year. There are many factors contributing to this; primarily, a clear splitting of audience and sponsorship funds across the two 2024 events, which contributed to the loss of revenue for both events last year. To avoid that, and to give each region the full attention they deserve, Community Over Code will alternate continents, switching each year. Thus, in 2026, there will be a Community Over Code EU, but not a Community Over Code NA. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald] Sorry, a nothing to report month, nothing happened. ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [David Nalley] ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik] USA US seems to be in a bit of a transition phase - with key people a bit distracted; so nothing to report here. Comments were submitted for DARS-2024-0034-0001 https://www.regulations.gov/document/DARS-2024-0034-0001 with compliments to Henri and everyone else that worked on that. The short of it is that we tried to help explain/define open source better. EU CRA, PLD, DSA, NIS2, DORA, etc; the impact/actual creation of regulatory bodies & its funding seems a bit delayed (with [1] often referenced). For NIS2 (which is ahead of the CRA) - there is now the first guidance open for suggestions[2]. We will see the same for the CRA next year. Main item this month will be the CRA expert meeting (of which the ASF, with its peers Eclipse and LF) is part. There is some talk about the software liability v.s AI liability directive; with the move to the right of the parliament possibly narrowing scope down further. ORWGC Open Regulatory Working Group at Eclipse -- actual useful work is starting there; with sufficient (IETF/Apache style) openness/accessibility to anyone. While at the same time having enough structure/goverance to keep this useful/suitable to inform policy & PAS processes. My hope is that we can get enough of a decent FAQ[4] or 1-half pager by the time of FOSDEM to allay the first order concerns of open source developers. And as a minor tidbit - the FSFE has been given the right to intervene in the Apple court case at the EU court of justice. 1: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14168-White-Paper-How-to-master-Europes-digital-infrastructure-needs?_en 2: https://www.enisa.europa.eu/news/asking-for-your-feedback-enisa-technical-guidance-for-the-cybersecurity-measures-of-the-nis2-implementing-act 3: https://edri.org/our-work/free-software-foundation-europe-intervenes-in-landmark-apple-vs-european-commission-case/ 4: https://github.com/orcwg/cra-hub/blob/main/faq.md -- but look at the PRs/branches ----------------------------------------- Attachment 11: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 12: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] Past month has been pretty calm. Committee members took good care of resolving most issues on time. After resolving a handful of LEGAL issues, we are flat at 30 issues compared to the last month. We're working with DLAPiper on two subpoenas -- no action required from the board at this time -- since we're handling everything in a timely fashion. Tika PMCs was threaten with a DMCA takedown notice for a small amount of allegedly copyrighted material that they hosted as part of their testing artifacts. The PMC promptly complied with the removal (we didn't engage in figuring out whether the allegations were true or not) and there's no issue with this at the time. ----------------------------------------- Attachment 13: Report from the Apache Security Team Project [Mark J. Cox] December * Several disclosures (Struts' CVE-2024-53677, Tomcat's CVE-2024-56337, Mina's CVE-2024-52046) were mentioned in various press outlets. These issues had in common that they were serious, but only affected a very specific set of use cases, and in some cases needed more than just a version bump to resolved. Coverage was mostly well-balanced and helped users understand whether they were affected and what to do in that case. We helped several outlets to give accurate and complete information * We continue to encourage projects to describe their project-specific security model, recently HertzBeat, Jackrabbit * We continue to help projects secure their GitHub Actions workflows and build out resources for future reference * We continue to improve the population and deployment of https://sbom.security.apache.org/ * We participated in the 2024 LF Europe and OpenSSF Stewards and Manufacturers Workshop Stats for December 2024: 35 [license confusion] 11 [support request/question not security notification] 10 [report/question relating to dependencies] Security reports: 67 (last months: 84, 76) 14 ['website or other infrastructure'] 4 ['hugegraph'] 3 ['activemq', 'superset', 'tomcat', 'trafficserver'] 2 ['airflow', 'hertzbeat', 'huntr', 'jspwiki', 'kylin', 'openoffice', 'seata', 'seatunnel', 'struts'] 1 ['apisix', 'cassandra', 'cocoon', 'commons', 'datafusion', 'directory', 'doris', 'eventmesh', 'flink', 'geronimo', 'guacamole', 'httpd', 'ignite','nifi', 'roller', 'spamassassin', 'subversion', 'trafficcontrol', 'velocity'] In total, as of 1st January 2025, we're tracking 179 (last months: 168, 175) open issues across 59 projects, median age 86 days (last months: 117, 107). 59 of those issues have CVE names assigned. 15 (last month: 17) of these issues, across 10 projects, are older than 365 days. Updates for projects with 'red' status: * oozie: not making releases (Health red): Project is dormant. Oozie are unable to respond to security reports, with one outstanding, and another one which has been fixed for more than 6 months but not released. We are at the second step of our formal escalation process and it looks like oozie will be moving to the attic soon. (Last update: 2025-01-06) Updates for projects with 'amber' status: * fineract (Health amber): the PMC has been attempting to engage more of the wider Fineract ecosystem to help triage, fix and release security issues, but with limited effect so far. (Last update: 2024-11-01) * geode (Health amber): Four issues in Geode over 365 days old. The project has voted to move to the Attic, but there might be a chance of revisiting that decision if relevant stakeholders successfully join the effort. (Last update: 2025-01-06) * openoffice (Health amber): Three issues in OpenOffice over 365 days old and a number of other open issues not fully triaged. (Last update: 2024-11-21) * zeppelin (Health amber): has a history of not dealing with security issues (Last update: 2024-11-28) ----------------------------------------- Attachment A: Report from the Apache Accumulo Project [Ed Coleman] ## Description: The mission of Apache Accumulo is the creation and maintenance of software related to a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Project Status: Current project status: Ongoing with high activity. Issues for the board: None ## Membership Data: Apache Accumulo was founded 2012-03-20 (13 years ago) There are currently 43 committers and 39 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 Kevin Rathbun on 2024-07-24. - No new committers. Last addition was Kevin Rathbun on 2024-07-25. ## Project Activity: ### Releases: - accumulo-1.10.4 (legacy) was released on 2023-11-16. - accumulo-2.1.3 (LTM) was released on 2024-08-12. - accumulo-3.0.0 was released on 2023-08-21. - accumulo-access-1.0.0-beta was released on 2024-02-17. ### Planned Release Activity: Accumulo is currently working on some significant development efforts. With the release of 2.1.3, we have begun formalizing future release plans: - Continue with critical bug fixes of the 2.1.x line. - Work continues on 3.1 branch to prepare for a feature-freeze and a release preparation. No traget date has been set. - We continue to work towards a 4.0.0-alpha release. These changes are the evolution of the processing model to support dynamic scaling and provide elasticity for improved cost and performance management. These changes are outlined in [1] ### Notable Work: - Metrics improvements - Monitor rework to support new processing model - Stability and scaling improvements to support elasticity ## Community Health: Overall community health is good and GitHub activity remains consistent. The email traffic reflects the community preference of using GitHub projects and issues for PRs discussions. We also use our slack channel for day-to-day communications. We continue to use the mailing list for official Apache business and it remains a channel for users to contact us. ## Links: [1] https://accumulo.apache.org/blog/2024/10/07/accumulo4-preview.html ----------------------------------------- Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder] ## Description: The mission of Apache ActiveMQ is the creation and maintenance of software implementing a distributed messaging system ## Project Status: Current project status: On going Issues for the board: None ## Membership Data: Apache ActiveMQ was founded 2007-01-16 (18 years ago) There are currently 64 committers and 30 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 Matt Pavlovich on 2023-12-06. - No new committers. Last addition was Anton Roskvist on 2024-02-09. ## Project Activity: ### ActiveMQ Classic - 6.1.4 was released on 2024-11-12 - 6.1.5 is also in preparation and will submit to vote soon - 6.2.0 is being worked on with new JMS 2/3 operations support. ### ActiveMQ Artemis - 2.38.0 released. Highlights include support for WebSocket compression plus management, configuration, and utility improvements. - 2.39.0 released. Java 17 is now required plus new management for federation and broker connections as well as numerous dependency upgrades and a 15% smaller binary distribution. - Work is progressing toward 2.40.0 & 3.0! ## Community Health: A proposal for design documentation has been discussed and will be experimented with soon. Aside from simplifying collaboration this should provide some additional visibility of the roadmap which will hopefully encourage new contributors. ----------------------------------------- Attachment C: Report from the Apache Airavata Project [Suresh Marru] ## Description: The mission of Apache Airavata is the creation and maintenance of software related to executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds. ## Project Status: Current project status: The Project is active, and the community is healthy. Issues for the board: No issues to report. ## Membership Data: Apache Airavata was founded 2012-09-18 (12 years ago) There are currently 44 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Lahiru Jayathilake on 2024-04-07. - No new committers. Last addition was Praneeth Chityala on 2024-04-25. ## Project Activity: Apache Airavata's last release was in December 2024. We are planning to continue the momentum and actively release in 2025. ## Community Health: Community activity is still spread across GitHub issues and PR's. Currently these discussions get notified in issues mailing lists, we will attempt to bring all communications to dev mailing lists to encourage more community activity and participation. ----------------------------------------- Attachment D: Report from the Apache Answer Project [Ning Qi] ## Description: The mission of Apache Answer is the creation and maintenance of software related to A Q-and-A platform software for teams at any scales ## Project Status: Current project status: New Issues for the board: None ## Membership Data: Apache Answer was founded 2024-12-18 (16 days ago) There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: On Nov 22, 2024, Apache Answer v1.4.1 was released. The new version includes a new linking question feature and several improvements, optimizing the display of personal pages and adding related questions and hot questions sections to the SEO template. Apache Answer is preparing to release version 1.4.2, which includes some new features and bug fixes. Additionally, we are preparing to update the name and documentation post-graduation. The new features in this version include: - Attachment-upload feature - Addition of key metrics to the dashboard - Introduction of a "Frequent" tab to filter the most linked questions We are planning to release v1.4.2 as the first version after graduation. There are also some new features under development and testing, which are expected to be released in the future versions: - Permanent user deletion - Scheduled cleanup of unused uploaded files - Addition of privacy policy and terms of service at the bottom ## Community Health: The development mailing list saw a slight decrease in traffic (-4%), with 52 emails compared to 54 last quarter. Overall, community health is stable. In the next quarter, we plan to focus on outreach efforts to attract new contributors and develop more committers to strengthen the project. ----------------------------------------- Attachment E: Report from the Apache APISIX Project [Ming Wen] ## Description: The mission of Apache APISIX is the creation and maintenance of software related to a cloud-native microservices API gateway ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache APISIX was founded 2020-07-15 (4 years ago) There are currently 64 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Ashish Tiwari was added to the PMC on 2024-10-16 - Abhishek Choudhary was added to the PMC on 2024-10-16 - No new committers. Last addition was Wanxing Zheng on 2024-09-07. ## Project Activity: 3.11.0 was released on 2024-10-17. 3.10.0 was released on 2024-08-13. 3.9.0 was released on 2024-03-29. ## Community Health: dev@apisix.apache.org had a 36% increase in traffic in the past quarter (60 emails compared to 44) notifications@apisix.apache.org had a 34% decrease in traffic in the past quarter (1566 emails compared to 2348) 102 commits in the past quarter (-19% change) 20 code contributors in the past quarter (-42% change) 119 PRs opened on GitHub, past quarter (-14% change) 100 PRs closed on GitHub, past quarter (-25% change) 196 issues opened on GitHub, past quarter (2% increase) 113 issues closed on GitHub, past quarter (-15% change) ----------------------------------------- Attachment F: Report from the Apache Aries Project [Christian Schneider] ## Description: Apache Aries software is a set of pluggable Java components enabling an enterprise OSGi application programming model. ## Project Status: Current project status: Mainly maintenance activity Roll call result was 4 +0, 1 -1. Issues for the board: No issues besides low activity ## Membership Data: Apache Aries was founded 2010-12-15 (14 years ago) There are currently 56 committers and 40 PMC members in this project. The Committer-to-PMC ratio is 7:5. Community changes, past quarter: - No new PMC members. Last addition was Carlos Sierra Andrés on 2018-07-03. - No new committers. Last addition was Romain Manni-Bucau on 2020-01-29. ## Project Activity: Very low activity before December. Since December we see some increased activity. 3 Maintenance releases. ## Community Health: No activity on user list since June 2024. We had one request for a new jira account. Robert initiated a small new sub project to register platform mbean server as OSGi service. ----------------------------------------- Attachment G: Report from the Apache Arrow Project [Neal Richardson] ## Description: The mission of Apache Arrow is the creation and maintenance of software related to columnar in-memory processing and data interchange. More information can be found at https://arrow.apache.org/overview/. ## Project Status: Current project status: Ongoing (high activity) Issues for the board: none ## Membership Data: Apache Arrow was founded 2016-01-19 (9 years ago) There are currently 112 committers and 53 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Curt Hagenlocher was added to the PMC on 2024-10-29 - Gang Wu was added to the PMC on 2024-12-02 - Adam Reeve was added as committer on 2024-11-18 - Laurent Goujon was added as committer on 2024-11-25 - Rossi Sun was added as committer on 2024-10-22 ## Project Activity: ### Recent releases: * RS-OS-0.11.2 was released on 2024-12-24. * RS-54.0.0 was released on 2024-12-23. * JULIA-2.8.0 was released on 2024-12-06. * 18.1.0 was released on 2024-11-21. * RS-53.3.0 was released on 2024-11-20. * ADBC-15 was released on 2024-11-13. * JULIA-2.7.4 was released on 2024-10-30. * 18.0.0 was released on 2024-10-28. * RS-53.2.0 was released on 2024-10-24. * GO-18.0.0 was released on 2024-10-22. * RS-OS-0.11.1 was released on 2024-10-20. * NANOARROW-0.6.0 was released on 2024-10-13. Selected sub-project activity: ### Arrow C Data Interface The proposed asynchronous version of the C Data Interface was merged: https://github.com/apache/arrow/pull/43632 ### Format We’ve added a new experimental standard for statistics: https://arrow.apache.org/docs/dev/format/StatisticsSchema.html ### Go We’ve released a new version from the split repository (apache/arrow-go). We’ll be able to maintain the Go implementation in this development style. ### Java Like Go, the Java implementation has been moved to its repository to make independent releases. This will not require users to make any changes, but (like Go) will need work to set up independent CI and release processes. ### MATLAB Initial support for reading and writing the Arrow IPC Stream Format was added. This work was done in part to enable [Arrow-over-HTTP](https://github.com/apache/arrow-experiments/tree/main/http/get_simple) workflows. ### nanoarrow Version 0.6.0 was added, which included an IPC writer, CMake and meson configuration improvements, and DLPack/non-CPU device support in the Python bindings. ### R A CVE was filed for arbitrary code execution when loading a malicious data file: https://www.cve.org/CVERecord?id=CVE-2024-52338 ### Rust The Rust implementation continues monthly releases, with breaking API changes restricted to every 3 months. This process seems to be working well and we have had less community pushback due to breaking changes. We continue to encourage additional community help maintaining / reviewing PRs, though PRs are still bottlenecked by reviewer bandwidth. Overall the focus has been on filling out DataType support in kernels, and interoperability with other implementations (Dictionary handling, ListArray field naming, etc.) Most work for the Rust object store has been related to incremental features, and small bug fixes. We are prioritizing stability. ## Community Health: GitHub statistics show a 20-30% drop in activity this quarter: * github@arrow.apache.org had a 30% decrease in traffic in the past quarter (10460 emails compared to 14773) * 1878 commits in the past quarter (-21% change) * 1616 PRs opened on GitHub, past quarter (-27% change) * 1666 PRs closed on GitHub, past quarter (-22% change) * 1034 issues opened on GitHub, past quarter (-31% change) * 899 issues closed on GitHub, past quarter (-23% change) Given that the number of commits is down less than the traffic on the github@ mailing list, we can infer that this means that PR review activity was more significantly reduced: there were fewer issues, PRs, and commits, and those that did occur got less discussion. Dev mailing list traffic is stable/slightly increased, as is the number of unique code contributors. This is all consistent with the effects of the major layoffs of paid Arrow contributors mentioned in the previous board update. If that is in fact the cause, we should expect that decrease to stabilize in the next quarter. Moreover, some of those affected by the layoffs have found Arrow-related positions in other companies (with at least one open source company stepping up to provide maintenance for Arrow), so we may see these numbers recover in the future. ----------------------------------------- Attachment H: Report from the Apache AsterixDB Project [Till Westmann] ## Description: Apache AsterixDB is a scalable big data management system (BDMS) that provides storage, management, and query capabilities for large collections of semi-structured data. ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache AsterixDB was founded 2016-04-19 (8 years ago) There are currently 40 committers and 27 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 Wail Y. Alkowaileet on 2023-11-21. - Ritik Raj was added as a committer on 2024-09-17. ## Project Activity: Apache AsterixDB JDBC Driver 0.9.8.3 was released on 2024-04-03. apache-asterixdb-0.9.8.2 was released on 2024-03-04. apache-asterixdb-0.9.9 was released on 2024-03-04. apache-hyracks-0.3.8.2 was released on 2024-03-04. apache-hyracks-0.3.9 was released on 2024-03-04. Activity: Release 0.9.8.3 is awaiting some features before it is released. ## Community Health: The APE (AsterixDB Proposed Enhancements) process has started to gain some traction. Previously some APEs were retroactive or sparse, but this is changing. For example, APE 9 (UPDATE statement) had some good discussion around the design of the syntax. Since the last board report we're up to APE 17 now. The weekly meeting is going on as usual, there are at least a few new voices every quarter but none from the dev list yet. The newer contributors to the project are doing great work and many of them are the principal authors behind the newest set of APEs, we hope some of them can become committers soon. ----------------------------------------- Attachment I: Report from the Apache Attic Project [Herve Boutemy] ## Description: The mission of Attic is the creation and maintenance of a home for dormant projects. ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Attic was founded 2008-11-19 (16 years ago) There are currently 19 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Herve Boutemy on 2015-07-19. - No new committers. Last addition was Herve Boutemy on 2016-01-27. ## Project Activity: Attic retired 1 project this quarter: Streams. Discussion is starting on updating retired projects websites to adapt to recent regulation. ## Community Health: Last retirements went well with our tools and documented process: looking for areas of improvement, like the recent ask for websites updates. ----------------------------------------- Attachment J: Report from the Apache Avro Project [Ryan Skraba] ## Description: Apache Avro is a data serialization system with a compact binary format. It is used for storing and transporting schema-driven serialized data. The unique features of Avro include automatic schema resolution: when the reader's expected schema is different from the actual schema with which the data was serialized the data is automatically adapted to meet reader's requirements. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Avro was founded 2010-04-21 (15 years ago) There are currently 39 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Oscar Westra van Holthe - Kind was added to the PMC on 2024-08-27 - No new committers. Last addition was Christophe Le Saec on 2023-08-12. ## Project Activity: There was no release this quarter. The last releases were 1.12.0 and 1.11.4 in August 2024. Notably, we announced the CVE-2024-47561 that these releases fixed in this quarter. As planned, the Rust SDK was separated from the main avro git repository into its own repo, the first of the languages to do so. It seems like a good fit and is receiving PRs and commits from the community. We are in a good place to release new minor versions if necessary. ## Community Health: Mailing Lists: - dev@avro.apache.org had 305 emails (-44% change) - issues@avro.apache.org (mostly notifications) had 476 emails (-42% change) - user@avro.apache.org continues to have very little traffic, 7 total JIRA: - 36 issues opened (-52% change) - 18 issues closed (-67% change) Code Repository: - 46 commits in the past quarter (-76% change) - 16 code contributors in the past quarter (-42% change) GitHub: - 84 PRs opened on GitHub, past quarter (-58% change) - 76 PRs closed on GitHub, past quarter (-56% change) All of the measures of project activity have decreased this quarter, likely due to the releases in the last quarter and the winter holidays. ----------------------------------------- Attachment K: Report from the Apache bRPC Project [James Ge] ## Description: The mission of Apache bRPC is the creation and maintenance of software related to an industrial-grade RPC framework for building reliable and high-performance services ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache bRPC was founded 2022-12-21 (2 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: - Guangming Chen, who contributed 120 commits and 16k LOC, was added as a new PMC member on 2025-01-06. - No new committers. Last addition was Yang Liming on 2024-03-24. ## Project Activity: bRPC v1.11.0 was released on October 27th with the following new features: - Support pthread mutex deadlock detection - Support bzlmod - Support multiple RPCs parsing in wireshark dissector for baidu_std - Support jemalloc profiler and stats print - Support rpc protobuf message factory interface - Support arena rpc pb message factory - Support backup request policy - Support semaphore and rwlock for bthread - Support batch create and accept stream - Support timedlock of fast/hook pthread and bthread::Mutex ## Community Health: Committers take turns responding user emails and issues on a weekly basis. During the past quarter, about 55 new emails were received and answered weekly. 103 commits were made in the past quarter by 22 code contributors. ----------------------------------------- Attachment L: Report from the Apache Calcite Project [Ruben Q L] ## Description: Apache Calcite is a highly customizable framework for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. Avatica is a sub-project within Calcite and provides a framework for building local and remote JDBC and ODBC database drivers. Avatica has an independent release schedule and its own repository. ## Project Status: Current project status: ongoing (high activity) Issues for the board: none ## Membership Data: Apache Calcite was founded 2015-10-22 (9 years ago) There are currently 75 committers and 29 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 Mihai Budiu on 2024-07-26. - No new committers. Last addition was Norman Jordan on 2024-08-13. ## Project Activity: Apache Calcite 1.38.0 was released on 2024-10-15. It contained contributions from 39 contributors, and resolved 165 issues. The main features of this release were the AS MEASURE clause to define measures and use them in simple queries, ASOF join, the EXCLUDE clause in window aggregates, Postgres-compatible implementations of the TO_DATE, TO_TIMESTAMP and TO_CHAR functions, and the extension of the type system to allow types with negative scale. There was no release for Apache Avatica in the last quarter, but discussions have started to release the next version (1.26.0) soon. Following our traditional yearly rotation, a new PMC Chair (Ruben Quesada Lopez) was chosen for 2025. ## Community Health: The community continues on a "Super healthy" status. Looking at the metrics, we have seen an increase on the commit activity (10% increase on commits, 42% increase on code contributors). Other metrics show a slight decrease, e.g. 9% decrease in traffic on the dev meailing list, or 16% / 10% decrease on opened / closed PRs, which is understandable considering the holiday period at the end of the year. The number of non-committer (contributor) commits per month: +------+-------+---------------------+ | year | month | contributor_commits | +------+-------+---------------------+ | 2024 | 10 | 16 | | 2024 | 11 | 19 | | 2024 | 12 | 19 | +------+-------+---------------------+ The number of active reviewers per month: +------+-------+------------------+ | year | month | active_reviewers | +------+-------+------------------+ | 2024 | 10 | 3 | | 2024 | 11 | 2 | | 2024 | 12 | 5 | +------+-------+------------------+ Top reviewers in the last 3 months: +-------------+---------+ | committer | reviews | +-------------+---------+ | Mihai Budiu | 39 | | ILuffZhe | 5 | | NobiGo | 4 | +-------------+---------+ We have seen a decrease in the number of reviewers compared to previous quarters, with one particular reviewer (Mihai Budiu) being the most active one and taking care of most of this job. The situation with PR reviewing and the lack of reviewers, especially in a non-release period (usually right before a release more reviewers tend to get involved), is a known issue within the community, which has been discussed several times on the mailing list with several proposals to try to mitigate it. ----------------------------------------- Attachment M: Report from the Apache CarbonData Project [Liang Chen] ----------------------------------------- Attachment N: Report from the Apache Causeway Project [Jörg Rade] ## Description: The mission of Causeway is to enable the rapid development of maintainable domain-driven apps in Java. ## Project Status: ### Current project status: This is a mature project and the framework is generally stable. ### Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache Causeway was founded 2012-10-17 (12 years ago) There are currently 16 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Martin Hesse on 2023-07-05. - No new committers. Last addition was Martin Hesse on 2023-07-04. ## Project Activity: * In this quarter we released Causeway 3.2.0 (based on Spring Boot 3.4) [1]. This added a couple of significant new features (QueryDSL support, invoke actions from collection). * We've now ceased to release the v2.x branch as there was no demand from the community. * We are continuing to promote the framework to extend our user base. Dan Haywood has presented at meetups in both London [2] and Dublin [3,4], and was a recent guest on Josh Long's Bootiful Podcast [5]. An article on TheNewStack [6] is also in the works. ## Community Health: We continue to see engagement on our slack channel, which the community seems to much prefer over the users mailing list. Nevertheless, we continue to ensure that all relevant information are cross-posted to users@ and dev@ where necessary. ## References (links) [1] https://causeway.apache.org/relnotes/latest/about.html [2] https://www.meetup.com/londonjavacommunity/events/304374863 [3] https://ti.to/dublin-java-user-group/2024-apache-causeway [4] https://www.youtube.com/watch?v=wLEtrpfpAmA&t=298s&ab_channel=TechMeetup.Space [5] https://www.youtube.com/watch?v=F15iqJfFy5Y [6] https://thenewstack.io ----------------------------------------- Attachment O: Report from the Apache Celix Project [Pepijn Noltes] ## Description: The mission of Celix is the creation and maintenance of software related to Implementation of the OSGi specification adapted to C ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Celix was founded 2014-07-16 (10 years ago) There are currently 17 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Peng Zheng on 2022-10-16. - No new committers. Last addition was Zhenbao on 2022-10-19. ## Project Activity: - Remove event admin MQTT was added - Refactoring of bundle manifest file format to JSON - Several ci build fixes - The project is still working towards a major (breaking) release and this will (still) take a while. ## Community Health: Overall activity is slow but steady. No changes in the active developers. The number of closed PRs has increased, but not significantly. ----------------------------------------- Attachment P: Report from the Apache CXF Project [Andriy Redko] ## Description: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. There is also a sub-project that leverages CXF: Fediz - Fediz helps you to secure your web applications via the standard WS-Federation Passive Requestor Profile. ## Project Status: Current project status: Ongoing, moderate activity Issues for the board: none ## Membership Data: Apache CXF was founded 2008-04-15 (17 years ago) There are currently 44 committers and 26 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 Andy McCright on 2019-02-24. - No new committers. Last addition was Jamie Mark Goodyear on 2024-07-19. ## Project Activity: Most of the activity for this period was directed towards 4.1.0 release, compatible with Jakarta EE 10 platform (it has been constant ask from the community). The mitigation for one of the long-standing issues have been committed (and released) as well, the CVE allocation for it is in progress. The discussion has been started on the mailing list to resurrect OSGi support, driven by the Apache Karaf team. It may result into new joint repository since OSGi ecosystem is not level up on Jakarta and the integrations are not straightforward. Recent releases: 4.1.0 was released on 2024-12-13. 3.5.10 was released on 2024-12-09. 3.6.5 was released on 2024-12-09. 4.0.6 was released on 2024-12-09. Apache CXF Fediz 1.7.0 was released on 2024-11-14. ## Community Health: For the most part, the project is making steady, but not stellar, progress. Many of the protocols and specs that CXF implements are mature specs and don't really change much. Thus, steady progress and regular releases are a good thing. We are responding to bug reports, reviewing and merging pull requests, and hopefully getting patch releases out soon. We are looking to address all failing Jakarta EE 10 TCK tests that we haven't had time to fix before 4.1.0 release. After that, the focus will be shifted towards upcoming Jakarta EE 11 support. ----------------------------------------- Attachment Q: Report from the Apache DataFu Project [Eyal Allweil] ----------------------------------------- Attachment R: Report from the Apache DB Project [Bryan Pendleton] ## Description: The mission of the Apache DB project is to create and maintain commercial-quality, open-source, database solutions based on software licensed to the Foundation, for distribution at no charge to the public. The Apache DB TLP consists of the following subprojects: o Derby : a relational database implemented entirely in Java. o JDO : focused on building the API and the TCK for compatibility testing of Java Data Object implementations providing data persistence. o Torque : an object-relational mapper for Java. ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: none ## Membership Data: Apache DB was founded 2002-07-16 (22 years ago) There are currently 48 committers and 46 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Max Philipp Wriedt on 2024-07-03. - No new committers. Last addition was Max Philipp Wriedt on 2023-04-14. ## Project Activity: Recent releases: Torque 6.0 was released on 2024-05-22. Derby-10.17.1.0 was released on 2023-11-14. Derby-10.16.1.1 was released on 2022-06-15. This fall, all the Apache DB communities continued their normal development work. The Torque community incorporated some fixes in code (e.g TORQUE-368) and an ongoing discussion for a new illustrative use case (TORQUE-369). In the JDO community, work continued on adapting the release process to incorporate the SBOM files for improved security transparency. The community also continue to work on moving to JDK 11 as the lowest supported version. The Derby community is working on verifying compatibility with Open JDK 24 in DERBY-7171. This release of Java removes several long-deprecated features from the Java platform. There was some discussion about the challenges of updating older releases to incorporate security fixes. ## Community Health: Community health across all three Apache DB communities was low, but was typical for these stable, mature projects. ----------------------------------------- Attachment S: Report from the Apache Directory Project [Shawn McKinney] ## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Project Status: The core team continues to maintain the various subprojects. In response to question from the board last month: "Regarding the reported low activities in the subproject, have you assessed their value for the community for the future? are at least 3 PMCs responsive in each sub project. I have not observed at that." Answer: 'Yes', but, there aren't 3 for each. There are four members who are consistently active: Emmanuel Lecharny (ApacheDS, API, Studio, Mavibot), Colm O hEigeartaigh (Kerby), Brian Demers (Scimple) and myself (Fortress). We'll vote on all releases and respond to security incidents and project-wide business. This setup works because our projects are all related, and dependent on one another. For example, Fortress uses API, ApacheDS and Studio. So, by testing it, I'm testing the others. The same can be said for the others. Our tech stacks are closely related and so the overall project essentially functions as a single unit. We're not stating everything's great. It'd be easy to walk away. In doing we'd be abandoning an important project to the security ecosystem. My hunch's this is a common problem. As projects mature, they become less compelling for developers to work on. They'd rather work on more exciting tech rather than "boring" infrastructure components. We're open to / requesting suggestions from the board on how to attract and maintain help. We have a low bar to being a committer/PMC member. We're inviting and aren't controlled by a single entity. Folks come and work on a few issues. Once those are done they'll drift away and we'll rarely hear from them again. Perhaps, I'm overstating this last part a bit. We do have those who regularly submit patches and bug reports. Certainly, we're appreciative of their contributions and no disrespect is meant to any perceived lack of commitment. Our roster of contributors rotates, isn't consistent and can't be relied upon to cast votes, work on releases or to help with critical project-wide activities. ## Membership Data: Apache Directory was founded 2005-02-22 (20 years ago) There are currently 57 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Brian Demers on 2023-10-23. - No new committers. Last addition was Fredrik Roubert on 2023-07-10. ## Project Activity: Per sub-project: - ApacheDS: low activity. Release in the works. - LDAP API: low activity. Release in the works. - Studio: low activity. - Fortress: low activity. Release in the works. - Kerby: low activity. - Mavibot: low activity. Release in the works. - SCIMple: low activity. Work being done to get Scimple tests going with LDAP backend. ## Community Health: As stated earlier, the project activity is low with most of it realized via pull requests and to a lesser extent Jira tickets. Nonetheless, the PMC remains responsive. ----------------------------------------- Attachment T: Report from the Apache DolphinScheduler Project [Lidong Dai] ## Description: Apache DolphinScheduler is a cloud-native workflow orchestration platform with powerful user interface, dedicated to solving complex task dependencies in the data pipeline and providing various types of jobs available `out of the box` ## Project Status: Current project status:Health issues for the board: There are no issues for the board at this time ## Membership Data: Apache DolphinScheduler was founded 2021-03-17 (3 years ago) There are currently 59 committee members and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Xin Cheng was added to the PMC on 2024-06-18 - Hengliang Tan was added as committee on 2024-07-02 ## Project Activity: - 3.2.2 was released on Jul 18. - the top 2 active issues are as follows: dolphinscheduler/issues/16728[DSIP-78][Data Quality] Suggest remove data quality module(25 comments) dolphinscheduler/issues/16747[Bug] org.apache.dolphinscheduler.server.master.event.TaskEventHandleError: Handle task running event error, update taskInstance to db failed(11 comments) ## Community Health: - We have held two community online Meetups in last quarter. - 5 code contributors in the past quarter - 199 commits in the past quarter (38% increase) - 200 PRs closed on GitHub, past quarter (-20% change) - 167 PRs opened on GitHub, past quarter (-30% change) ----------------------------------------- Attachment U: Report from the Apache Druid Project [Gian Merlino] ----------------------------------------- Attachment V: Report from the Apache Dubbo Project [Jun Liu] ----------------------------------------- Attachment W: Report from the Apache Fineract Project [James Dailey] ## Description: The mission of Apache Fineract is the creation and maintenance of software related to a core banking platform that provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world's underbanked and unbanked. ## Project Status: Current project status: Stable. Issues for the board: Nothing urgent to highlight. ## Membership Data: Apache Fineract was founded 2017-04-18 (8 years ago) There are currently 54 committers and 24 PMC members in this project. The Committer-to-PMC ratio ~ 2:1 if the math is right. Community changes, past quarter: - No new PMC members. Last addition was Adam Saghy on 2023-07-10. - Marta Jankovics was added as committer on 2024-10-14 ## Project Activity: 1.10.1 was released on 2024-12-31. (pending issue with website) 1.9.0 was released on 2024-01-12. ## Community Health: A drop in listserv traffic is probably indicative of better help available from outside resources, including the newly launched Fineract-Academy.com by PMC member Adam Saggy. This was approved by the PMC. Message from PMC chair Dec 31st, 2-24: https://lists.apache.org/thread/1799o3xx9n6f9nmxfqkryjcf2cdqslb7 Today, our software is in use in organizations large and small around the world, reaching - according to some vendors - at least 65 million end users, and by dozens of vendors and maybe hundreds of direct providers. I suspect this under-counts our use...and impact. Some highlights and things to do: In 2024, we reworked the docker hub target and got that working again. We continue to see a lot of downloads there. We released 1.9.0 in January 2024, version 1.10.1 on Dec 31st, 2024. In 2025, we intend to make the release process easier such that this can happen more frequently. As part of this we may decide (after discussion) to do away with back porting of security patches and only have one official current release. If you want to earn karma by back porting recent security fixes or have an issue to report, send to security @ Fineract .apache.org In 2025, I'd also like to propose the following: * Readme and asciidoc documentation is improved and versioned with each release, with wiki content streamlined to project management. * Builds improvements as discussed in this dev thread https://lists.apache.org/thread/9l46b7p6bxt7c475o94wrg3k2wc54zdv * Progress on each of the FSIPs as outlined at https://cwiki.apach e.org/confluence/display/FINERACT/Fineract+Significant+Improvement+Proposals In a virtuous cycle of innovation, we continue to need the "roadmap" of items like those on the FSIPs as well as a set of "anti-roadmap" items, aka much later priority roadmap items. The roadmap is defined by the community not by any one Vendor, but contributions drive that roadmap. We have to ask “what is being planned?” Or “what would you like to add?” And discuss. Our assumed anti-roadmap currently includes "we will not embed complex reporting" and "we will not build the front end", as it is useful in defining where outside users and vendors can develop additional value-adds with some predictability. The philosophy of commercial open source requires companies ("vendors") making money such that they can contribute to the core code, and always exist upstream on the codebase because it is strategic for them. "You get what you develop, you get what they develop, you get what everyone develops." In terms of patterns, as has been pointed out recently, we need to push back on "Endless feature expansion". We don't do a good job of pruning features, which makes the process of development more complex than it needs to be. We may need a more frank discussion in 2025 about backwards compatibility and feature limitations. +1 on "look left and right" when touching the code. We should make sure that we develop cleanly and with sufficient documentation and consistency. More eyeballs are needed on the reviews. Subscribe to the feed and start following. In 2025, we should clear out old jira tickets and focus on the real needs and errors of today. Is this something you can help with? ----------------------------------------- Attachment X: 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: Current project status: Ongoing with low activity Issues for the board: None at this time Note : (no official Apache Releases have any dependencies on ElasticSearch--it remains a worked example in the repos only, but not distributed through releases). ## Membership Data: Apache Flagon was founded 2023-03-21 (2 years ago) There are currently 18 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Evan Jones on 2024-07-10. - No new committers. Last addition was Evan Jones on 2024-02-13. ## Project Activity: The project documentation and website has seen major improvements. There is always more to document, but a lot of stale information has been removed or updated. On the product side, we’ve seen some minor development. Most notably adding support for web sockets and improving test coverage. ## Community Health: Community growth was slow in the current period, however, it is growing nonetheless. Recently, we have had some members cross pollinate with the CNCF’s Open telemetry project. Open telemetry offers widely adopted standards that apply to a lot of our core functions. The PMC is currently exploring how integrating with the Open telemetry ecosystem can foster better community health. We are also aware that some community members have discussed OpenSearch integrations. We have struggled this period to get community members to converse on lists. ----------------------------------------- Attachment Y: Report from the Apache Fluo Project [Keith Turner] ----------------------------------------- Attachment Z: Report from the Apache Geronimo Project [Jean-Louis Monteiro] ## Description: The mission of Geronimo is the creation and maintenance of software related to Java2, Enterprise Edition (J2EE) container ## Project Status: Current project status: no major work or development but regular maintenance on the various libraries and implementations. Issues for the board: none ## Membership Data: Apache Geronimo was founded 2004-05-26 (21 years ago) There are currently 72 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2021-03-09. - No new committers. Last addition was Richard Zowalla on 2024-04-15. ## Project Activity: A few maintenance releases happened. No major development quite yet. Jakarta has been itself delayed so only maintenance is required. ## Community Health: No new committer joined the project. The current group handles the workload without much issue. It is composed of people from other projects like ActiveMQ, TomEE, OpenWebBeans and others. ----------------------------------------- Attachment AA: Report from the Apache Griffin Project [William Guo] ## Description: The mission of Apache Griffin is the creation and maintenance of software related to a data quality solution for big data, including both streaming and batch mode. It offers an unified process to measure data quality from different perspectives. ## Project Status: Current project status: Ongoing, moderate activity on branch griffin-2.0.0-dev Issues for the board: None ## Membership Data: Apache Griffin was founded 2018-11-21 (6 years ago) There are currently 21 committers and 19 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 Chitral Verma on 2020-05-06. - No new committers. Last addition was Chitral Verma on 2020-05-05. ## Project Activity: - basically the core module of griffin 2.0.0 is almost done - need more resources for ui and integration parts ## Community Health: - Normal, metrics should increase when 2.0.0 is released. - Will call for commits from community, since 2.0.0 is almost ready. ----------------------------------------- Attachment AB: Report from the Apache Hadoop Project [Xiaoqiao He] ## Description: The mission of Hadoop is the creation and maintenance of software related to Distributed computing platform ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Hadoop was founded 2008-01-16 (17 years ago) There are currently 248 committers and 125 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 Shilun Fan on 2023-10-31. - Anuj Modi was added as committer on 2024-10-19 ## Project Activity: 3.4.1 was released on 2024-10-18. 3.4.0 was released on 2024-03-17. hadoop-thirdparty-1.2.0 was released on 2024-02-07. 3.3.6 was released on 2023-06-25. ## Community Health: - Hadoop has made some progress on JDK17 compatibility[1]. Currently, JDK17 can compile Hadoop successfully. The PR we submitted mainly addresses issues with unit tests that were incompatible with JDK17, and now over 90% of the unit tests pass on JDK17. Compatibility issues with unit tests in the ResourceManager module (HADOOP-15984) are still being resolved and are expected to take some more time to fully address. - HDFS new feature "Asynchronous Router RPC"[2][3] which will improve performance of Router RPC dispatch is near to be ready, The core works has been completed and we will launch discuss to merge as early as next month. - HDFS new feature "NameNode Fine-Grained locking Based on Directory Tree" [4][5] which improve the performance of NameNode, The phase one developed works has been completed too, is discussing to merge via mailing list[6] and waiting for some ack, then propose an official merge request vote. - The core functionality of YARN Cgroup V2[7] is still under active development. While the features are currently being actively worked on, the overall development is expected to take some more time to complete. - Some functionality of the YARN Capacity Scheduler has been optimized, with valuable improvements provided by the participants, making the relevant features more robust. - The Project shows healthy engagement based on Mailing list/Jira/Github traffic. [1] https://issues.apache.org/jira/browse/HADOOP-17177 [2] https://issues.apache.org/jira/browse/HDFS-17531 [3] https://lists.apache.org/thread/k930cmlvo1z2zox9qhfx9797gk561nnc [4] https://issues.apache.org/jira/browse/HDFS-17366 [5] https://lists.apache.org/thread/6wlwx4jbpsfn4xs3617ltgqqxs69prlt [6] https://lists.apache.org/thread/36bowf8rwskt7gb5yzhyzjcjoyz80znz [7] https://issues.apache.org/jira/browse/YARN-11669 ----------------------------------------- Attachment AC: Report from the Apache HBase Project [Duo Zhang] ## Description: Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. hbase-thirdparty is a set of internal artifacts used by the project to mitigate the impact of our dependency choices on the wider ecosystem. hbase-connectors is a collection of integration points with other projects. The initial release includes artifacts for use with Apache Kafka and Apache Spark. hbase-filesystem contains HBase project-specific implementations of the Apache Hadoop FileSystem API. It is currently experimental and internal to the project. hbase-operator-tools is a collection of tools for HBase operators. Now it is mainly for hosting HBCK2. hbase-native-client is a client library in C/C++, in its early days. hbase-kustomize is for deploying HBase on kubernetes, still under development. ## Project Status: Current project status: Ongoing Issues for the board: The trademark team found out that https://6sense.com/tech/nosql-databases uses 'Hbase' instead of 'Apache HBase'. But we haven't found the contact info on the website. Mark Thomas has reached out them via Linkedin but there is no response yet. ## Membership Data: Apache HBase was founded 2010-04-21 (15 years ago) There are currently 107 committers and 61 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Istvan Toth was added to the PMC on 2024-11-28 - No new committers. Last addition was Ray Mattingly on 2024-09-10. ## Project Activity: 2.6.1 was released on 2024-10-18. We finally moved up to hadoop 3.4.x as our default hadoop 3 dependency version. https://lists.apache.org/thread/orc62x0v2ktvj26ltvrqpfgzr94ncswn https://issues.apache.org/jira/browse/HBASE-28846 We have finished the first round of alignment between git commit and jira issue for 3.0.0 release. This means we have made a big progress on the final 3,0.0 release. https://issues.apache.org/jira/browse/HBASE-28844 https://lists.apache.org/thread/zwb2y5vz7jfdnvvo9z8k8z9j8frp938m ## Community Health: - dev@hbase.apache.org: 964 subscribers(966 in the previous quarter) 419 emails sent to list(527 in the previous quarter) - user@hbase.apache.org: 1980 subscribers(1985 in the previous quarter) 27 emails sent to list(36 in the previous quarter) - user-zh@hbase.apache.org 81 subscribers(81 in the previous quarter) 8 emails sent to list(17 in the previous quarter) - Commit activity: 263 commits in the past quarter (-63% decrease) 31 code contributors in the past quarter (-32% change) - GitHub PR activity: 204 PRs opened on GitHub, past quarter (-34% change) 174 PRs closed on GitHub, past quarter (-40% change) The project was not very active because there were not many releases this quartar. We plan to make new 2.6.x and 2.5.x releases soon. And we have made big progresses on the final 3.0.0 release, hope we could make it soon. ----------------------------------------- Attachment AD: Report from the Apache Incubator Project [Justin Mclean] ----------------------------------------- Attachment AE: Report from the Apache InLong Project [Charles Zhang] ## Description: The mission of Apache InLong is the creation and maintenance of software related to a one-stop data integration framework that provides automatic, secure, and reliable data transmission capabilities. InLong supports both batch and stream data processing at the same time, which offers great power to build data analysis, modeling, and other real-time applications based on streaming data ## Project Status: Current project status: Ongoing, with moderate activity. Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache InLong was founded 2022-06-15 (3 years ago) There are currently 53 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. - ShuoMing Qiu was added as committer on 2024-12-12 - Xiangming Zhou was added as committer on 2024-12-16 - Yifei Gao was added as committer on 2024-12-16 ## Project Activity: In the past quarter, InLong has successfully released 2.0.0, and the project is working on 2.1.0, which will be released next month. For the newly released 2.0.0, it closed about 315+ issues, including 6+ major features and 96+ optimizations, for example: - New Transform Capabilities - Community Documentation Restructuring - Support for OceanBase Data Source - Dynamic Resource Calculation for Sort Tasks - SortStandalone Supports HTTP Sink - Full-Link Management of Offline Synchronization There were no meetups during the past quarter. ## Community Health: The community health looks good overall. - dev@inlong.apache.org had a 35% decrease in traffic in the past quarter (430 emails compared to 661) - 249 commits in the past quarter (-38% change) - 24 code contributors in the past quarter (-40% change) - 189 PRs opened on GitHub, past quarter (-51% change) - 236 PRs closed on GitHub, past quarter (-28% change) - 195 issues opened on GitHub, past quarter (-52% change) - 259 issues closed on GitHub, past quarter (-24% change) The developing data experienced some decline, but it's within expectations, and the project is still undergoing normal iteration and evolution. ----------------------------------------- Attachment AF: Report from the Apache James Project [Benoit Tellier] ----------------------------------------- Attachment AG: Report from the Apache jclouds Project [Andrew Gaul] There are no issues requiring board attention A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == During the last few years, we initiated discussions to move the project to the Attic, given the low activity and the concerns shared in previous reports. The discussion started in October 2022 (https://s.apache.org/jclouds-attic) and the Brooklyn and Karaf communities expressed interest in keeping the project alive and helping the project. Despite the very welcomed good intentions, however, nothing actually happened in the form of actual contributions, further engagement with the project, etc, and for months we have been just waiting for something to happen beyond the will to keep the project alive. The Attic discussion is a perfect example of the current status of the jclouds community: there are people interested in keeping the project alive, but no one has the time and/or energy to actually do it, and in this scenario, it has been discussed that we would probably better serve the community by moving the project to the Attic and set clear expectations for our users, instead of keeping it in the current limbo of inactivity. Revisiting this thread in March 2024 shows no new interest: https://lists.apache.org/thread/ql50d2v7s3ccywm2frkmqsqwdzj402fb == Community == Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Run final 2.6.1 release in 1Q2025 Initiate attic process in October and write post-mortem == Releases == The last major jclouds release, 2.6.0, took place on 2024-03-09. The last bugfix release, 2.2.1, took place on 2020-05-14. ----------------------------------------- Attachment AH: Report from the Apache Jena Project [Andy Seaborne] ## Description: The mission of Jena is the creation and maintenance of software related to a Java framework for building Semantic Web applications ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Jena was founded 2012-04-18 (13 years ago) There are currently 20 committers and 14 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 Arne Bernhardt on 2024-04-05. - No new committers. Last addition was Sergei Zuev on 2024-08-01. ## Project Activity: Jena 5.2.0 was released on 2024-10-15 with a significant contribution from AWSlabs. It is an experimental implementation of an extension the SPARQL query language as part of a proposal to the wider SPARQL and RDF community, . The "experimental" label is used by the project to indicate areas that may be subject to between versions. As a project with many components, synchronizing semantic version management is not always practical for specific new features not considered main stream yet. ## Community Health: The 5.3.0 release is in-progress and will incorporate several contributions from outside the project committers. It will also have replacement of old code. There is no significant change in the community activity. Jena development tends to happen in branches on cloned repos. Some of the drop in commits will be due to the replacements being squashed to a few commits. ----------------------------------------- Attachment AI: Report from the Apache JMeter Project [Bruno Demion] ## Description: The mission of JMeter is the creation and maintenance of software related to Java performance and functional testing ## Project Status: Current project status: Ongoing, with low activity Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache JMeter was founded 2011-10-26 (13 years ago) Jakarta JMeter, first version was released 1998-12-15 (26 years ago) There are currently 13 committers and 8 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 Vladimir Sitnikov on 2018-06-08. - No new committers. Last addition was Maxime Chassagneux on 2017-02-15. ## Project Activity: - Current (low) objective is to move the code base of JMeter to Java 17+ (from Java 8) for next major release (6.0) - Recent releases: 5.6.3 final was released on 2024-01-07. ## Community Health: - The project has a low activity during last quarter. ----------------------------------------- Attachment AJ: Report from the Apache Johnzon Project [Jean-Louis Monteiro] ## Description: The mission of Johnzon is the creation and maintenance of software related to JSR-353 compliant JSON parsing; modules to help with JSR-353 as well as JSR-374 and JSR-367 ## Project Status: Current project status: nothing happening at the minute. Jakarta has been delayed. Issues for the board: none ## Membership Data: Apache Johnzon was founded 2016-04-20 (9 years ago) There are currently 9 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Reinhard Sandtner on 2016-08-30. - No new committers. Last addition was Markus Jung on 2024-02-05. ## Project Activity: Jakarta has been delayed so there is no new JSON-B or JSON-P work to do. And the current code based is stable so no new release or maintenance done. ## Community Health: Hard to say for the moment if project is at risk or not considering there is nothing to do. The active committers all are also committers on others top level projects. They are active there so whenever there is work, there has been always committers to work on Johnzon. ----------------------------------------- Attachment AK: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez] ## Description: The mission of JSPWiki is the creation and maintenance of software related to Leading open source WikiWiki engine, feature-rich and built around standard JEE components (Java, servlets, JSP). ## Project Status: Current project status: Ongoing, with low activity. Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache JSPWiki was founded 2013-07-17 (11 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: - Arturo Bernal was added to the PMC on 2023-06-21 - Arturo Bernal was added as committer on 2023-06-21 ## Project Activity: Activity this quarter has been mostly around reviewing and working on the switch to Jakarta 10. Initially on a contributor's fork, the migrated code is now living on the jakarta branch of the main git repo. The main stopper in that branch is that we have to decide what to do with some xmlrpc code, which has no upgrade path. Current options are 1) rewrite it using the metaweblog API (sort of xmlrpc successor), 2) remove it all together or 3) replace it with a proper REST API. Or perhaps 2) and then later on 3). We've received a couple of vulnerability reports that are still under study, but they will probably require to release 2.12.3 before switching to 3.0.0. ## Community Health: Work on latest master shows commits from 1 commiter, which contains 1 pull request from one contributor and some dependency upgrades. Also, the jakarta branch landed on december. No questions unanswered on MLs, although they continue to have little traffic. ----------------------------------------- Attachment AL: Report from the Apache Kudu Project [Andrew Wong] ## Description: The mission of Apache Kudu is the creation and maintenance of software related to a distributed columnar storage engine built for the Apache Hadoop ecosystem. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kudu was founded 2016-07-19 (8 years ago) There are currently 32 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Ke Deng on 2024-09-13. - No new committers. Last addition was Xixu Wang on 2024-09-14. ## Project Activity: - 1.17.1 was released on 2024-11-15. - 1.17.0 was released on 2023-09-01. - 1.16.0 was released on 2022-04-11. ## Community Health: - Development activity measured in the number of commits has increased by 11%. Development measured in the number of unique developers reached back to 13. - Traffic to the dev mailing list decreased by 40%. This is mainly due to release planning and other discussions about the project in the previous quarter. - The number of issues opened has decreased (15 issues opened, -64%) due to the holiday season. - Community activity measured in community Slack is steady (the number of weekly active users -6%, and public posters +8%). ----------------------------------------- Attachment AM: Report from the Apache Libcloud Project [Tomaž Muraus] ----------------------------------------- Attachment AN: Report from the Apache Logo Development Project [Daniel Gruno] ## Description: The mission of Apache Logo Development is the creation and maintenance of software related to Creation and development of a brand and logo for the Foundation ## Project Status: Current project status: Ongoing Issues for the board: No issues for the board. ## Membership Data: Apache Logo Development was founded 2024-08-21 (5 months ago) There are currently 17 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Melissa Logan on 2024-08-28. - No new committers were added. ## Project Activity: Work is underway to set up the voting mechanisms for conducting test voting, ensuring our tooling works with the voting platform and can be deployed when we get closer to the official vote. There are some technical issues to coordinate with infrastructure, but we have no concerns at present that this would present any form of blocker. Once we have conducted the tests to satisfaction, we will begin discussing the official vote and the messaging around it. It is my personal expectation that the committee will be able to reach this point in the coming month. ## Community Health: No updates of note. The roster has remained the same since last report, and we are slowly getting back into the groove after the holidays. ----------------------------------------- Attachment AO: Report from the Apache MADlib Project [Ed Espino] ## Description: The mission of Apache MADlib is the creation and maintenance of software related to a scalable, Big Data, SQL-driven machine learning framework for Data Scientists ## Project Status: Current project status: The project is essentially in a stalled state. Issues for the board: We will be taking forward the discussion to formalize moving Apache MADlib closer to an active community (i.e. Apache Cloudberry (Incubating)) project. Two PMC members Roman Shaposhnik (rvs) and Greg Chase are in support of this initiative. I (Ed Espino) am on the Apache Cloudberry PPMC. I will formalize the discussion the potential move under the Apache Cloudberry umbrella of components (see Plan forward (proposal) below). ## Membership Data: Community changes, past quarter: - No new PMC members. Last addition was Ed Espino on 2023-03-22. - No new committers. Last addition was Ed Espino on 2023-03-23. ## Project Activity: - No releases have taken place. - No releases are planned. ## Community Health: The only communication has been on the PMC level to discuss the project's options moving forward. For reference, this is what was sent with only Roman Shaposhnik and Greg Chase responding: ## Plan forward (proposal) As I have conversations with both projects and communities, I could use some guidance on what process to follow. I have not observed any movement of one project into another. Any guidance would be greatly appreciated. Here is a proposal. Initial Discussion and Consensus Building - First, formalize discussions within both communities through their respective dev mailing lists - Get clear confirmation from the MADlib PMC about their willingness to move under Cloudberry - Document support from both communities' members - Create a written proposal outlining the benefits and technical synergies Technical Assessment - Create an inventory of MADlib's current assets (codebase, documentation, infrastructure) - Identify potential integration points with Cloudberry - Draft a technical migration plan - Consider any naming/branding implications Community Alignment - Share merger details with communities - Address any concerns from either community - Establish how the existing MADlib committers and PMC members would transition - Define the governance model post-merger Apache Infrastructure & Legal - Consult with ASF Legal regarding any IP or licensing considerations - Plan repository migration strategy - Document infrastructure needs (CI/CD, websites, mailing lists) Formal Proposal - Draft a formal proposal for the ASF Board - Current state of both projects - Rationale for the merger - Community support evidence - Technical migration plan - Timeline - Post-merger governance structure Implementation - Get board approval - Execute technical migration - Update documentation and websites - Announce to broader Apache community ----------------------------------------- Attachment AP: Report from the Apache Mahout Project [Andrew Musselman] ## Description: Mahout is a distributed linear algebra framework and mathematically expressive DSL designed to let mathematicians, statisticians, and data scientists quickly implement their own algorithms. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Mahout was founded 2010-04-20 (15 years ago) There are currently 29 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Shannon Quinn on 2023-02-12. - No new committers. Last addition was Tommy Naugle on 2024-04-18. ## Project Activity: Latest work efforts are toward quantum-based machine learning, including supporting measurement, testing, and post-processing per new business in https://mahout.apache.org/minutes/2024/12/06/Meeting-Minutes.html ## Community Health: * Ongoing community meeting minutes found at (https://mahout.apache.org) * “Introducing Qumat! (An Apache Mahout Joint)” at FOSDEM in February 2025 ----------------------------------------- Attachment AQ: Report from the Apache Maven Project [Karl Heinz Marbaise] ## Description: The mission of Maven is the creation and maintenance of software related to Java project management and comprehension tools ## Project Status: Current project status: ongoing with high activity. Issues for the board: none ## Membership Data: Apache Maven was founded 2003-03-01 (22 years ago) There are currently 70 committers and 31 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 Romain Manni-Bucau on 2023-10-16. - No new committers. Last addition was Zhongming Hua on 2024-01-28. ## Project Activity Recent releases: Apache Maven Changelog Plugin 3.0.0-M1 was released on 2024-12-30. Apache Maven Changes Plugin 3.0.0-M2 was released on 2024-12-30. Apache Maven Remote Resources Plugin 3.3.0 was released on 2024-12-30. Apache Maven Shared JAR 3.2.0 was released on 2024-12-30. Apache Maven 4.0.0-rc-2 was released on 2024-12-17. Maven Resolver 2.0.5 was released on 2024-12-16. Maven Javadoc Plugin 3.11.2 was released on 2024-12-14. Maven Fluido Skin 2.0.1 was released on 2024-12-11. Apache Maven Patch Plugin 1.3 was released on 2024-12-10. Apache Maven Invoker Plugin 3.9.0 was released on 2024-12-09. Apache Maven Changes Plugin 3.0.0-M1 was released on 2024-12-07. Apache Maven Archiver 4.0.0-beta-3 was released on 2024-12-02. Apache Maven Daemon 2.0.0-rc-1 was released on 2024-12-02. Apache Maven 4.0.0-rc-1 was released on 2024-11-28. Maven Resolver 2.0.4 was released on 2024-11-18. Apache Maven Plugin Testing 4.0.0-beta-2 was released on 2024-11-13. Maven Fluido Skin 2.0.0 was released on 2024-11-02. Maven Resolver 2.0.3 was released on 2024-11-01. Maven Artifact Plugin 3.5.3 was released on 2024-10-30. Maven Javadoc Plugin 3.11.1 was released on 2024-10-30. Maven Surefire 3.5.2 was released on 2024-10-30. Maven Archetype Plugin 3.3.1 was released on 2024-10-25. Maven PMD Plugin 3.26.0 was released on 2024-10-25. Apache Maven 4.0.0-beta-5 was released on 2024-10-22. Maven Archiver 3.6.3 was released on 2024-10-22. Maven Checkstyle Plugin 3.6.0 was released on 2024-10-22. Maven Dependency Analyzer 1.15.1 was released on 2024-10-22. Maven JXR 3.6.0 was released on 2024-10-22. Maven Plugin Tools 3.15.1 was released on 2024-10-22. Maven Artifact Plugin 3.5.2 was released on 2024-10-19. Maven Dependency Plugin 3.8.1 was released on 2024-10-18. Maven Help Plugin 3.5.1 was released on 2024-10-18. Maven Invoker Plugin 3.8.1 was released on 2024-10-18. Maven Project Info Reports Plugin 3.8.0 was released on 2024-10-18. Maven Site Plugin 3.21.0 released was released on 2024-10-18. Maven Resolver 2.0.2 was released on 2024-10-17. Maven Reporting Exec 2.0.0 was released on 2024-10-15. Maven Reporting Impl 4.0.0 was released on 2024-10-12. ## Maven Central Sustainability & Continuity We're having discussions about Maven Central copy, its evolution, successes, challenges, and future plans. ## Community Health: * Some increases on the dev-mailing list; means a bit more communication there. Not so much as lost since the last report. * Some of the communication is done via Slack channels which explains the descreasing emails on the mailing lists. * Issue mailing list traffic has increased, also users-mailing list, but I expect the issue-mailing list to decrease over the next quarter based on the usage of Github issues. * A larger number of GitHub PR's and closed PR's also shows a bigger move to GitHub (Issues/PR's) by the community also by the committers. A going down at the end of year as expected. * The usage of github issues is the way the community wants to go, because it's easier for the community in comparison to JIRA. That will also bring more changes into that direction for the next quarter. General observation is that people hesitate to use mailing lists and prefer more other things like slack or alike. High activity currently focusing on Maven 4.0.0 line. Getting some feedback from the community based on increasing number downloads of the newer Maven 4.X versions. ----------------------------------------- Attachment AR: Report from the Apache Mesos Project [Qian Zhang] ## Description: The mission of Mesos is the creation and maintenance of software related to a cluster manager that provides efficient resource isolation and sharing across distributed applications ## Project Status: Current project status: [No new PRs created, the community was a bit quiet.] Issues for the board: [None] ## Membership Data: Apache Mesos was founded 2013-06-19 (12 years ago) There are currently 50 committers and 50 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Charles-François Natali on 2021-08-08. - No new committers. Last addition was Charles-François Natali on 2021-08-07. ## Project Activity: [No much activities besides one PR created last quarter received some review comments.] ## Community Health: [Just one PR got some review comments, no bugs created, overall the community was a bit quiet.] ----------------------------------------- Attachment AS: Report from the Apache MINA Project [Guillaume Nodet] ## Description: The mission of MINA is the creation and maintenance of software related to Multipurpose Infrastructure for Network Application ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache MINA was founded 2006-10-25 (18 years ago) There are currently 29 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Gary D. Gregory on 2023-09-13. - No new committers. Last addition was Gary D. Gregory on 2022-03-24. ## Project Activity: Apache MINA 2.0.26 was released on 2024-10-15. Apache MINA 2.1.9 was released on 2024-10-15. Apache MINA SSHD 2.12.1 was released on 2024-02-14. Apache MINA 2.0.27 was released on 2024-12-25. Apache MINA 2.1.10 was released on 2024-12-25. Apache MINA 2.2.4 was released on 2024-12-25. Those 3 last releases are fixing CVE-2024-52046. ## Community Health: Activity is low but the community is healthy. We receive external contributions through PRs and we released a few bug fix releases. ----------------------------------------- Attachment AT: Report from the Apache Mnemonic Project [Gordon King] ----------------------------------------- Attachment AU: Report from the Apache MyFaces Project [Bernd Bohmann] ## Description: The mission of MyFaces is the creation and maintenance of software related to JavaServer(tm) Faces implementation and components ## Project Status: Current project status: Ongoing, with moderate activity Issues for the board: None ## Membership Data: Apache MyFaces was founded 2005-02-23 (20 years ago) There are currently 81 committers and 47 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 Melloware on 2024-01-25. - No new committers. Last addition was Milan Siebenbürger on 2024-01-24. ## Project Activity: - Apache MyFaces Core is working on a 2.3.11 release - Apache Tobago community is working on 6.7.0 and 5.15.0. - Recent Releases: myfaces-core-4.1.0 was released on 2024-12-07. myfaces-core-4.1.0-RC3 was released on 2024-11-02. tobago-5.14.0 was released on 2024-10-19. tobago-6.6.0 was released on 2024-10-19. ## Community Health: - Apache MyFaces Core is healthy. UI-Component Sets: - Apache Tobago is healthy. - Apache Trinidad is in maintenance mode. Last developer commit was Sept 2017. - Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016. Last commit on behalf of a contributor was May 2016. Add-ons and Extensions: - Apache MyFaces Portlet Bridge is in maintenance mode. Last developer commit was Jan 2014. Last commit on behalf of a contributor was May 2015. - Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache DeltaSpike so new development happens there. Last commit March 2014. - Apache MyFaces Orchestra is in maintenance mode. New projects use CDI and DeltaSpike instead. Last commit on behalf of a contributor was August 2016. - Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014. - Apache MyFaces Commons is in maintenance mode. Last commit August 2012. - Apache MyFaces Ext-Scripting is in maintenance mode. Last commit Sept 2017. - Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last commit May 2017. ----------------------------------------- Attachment AV: Report from the Apache NiFi Project [Joe Witt] ## Description: The mission of NiFi is the creation and maintenance of software related to providing an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi MiNiFi is an edge data collection agent built to seamlessly integrate with and leverage the command and control of NiFi. There are both Java and C++ implementations. Apache NiFi Registry is a centralized registry for key configuration items including flow versions, assets, and extensions for Apache NiFi and Apache MiNiFi. Apache NiFi Nar Maven Plugin is a release artifact used for supporting the NiFi classloader isolation model. Apache NiFi Flow Design System is a theme-able set of high quality UI components and utilities for use across the various Apache NiFi web applications in order to provide a more consistent user experience. ## Project Status: Current project status: Ongoing. High. Issues for the board: None. ## Membership Data: Apache NiFi was founded 2015-07-14 (9 years ago) There are currently 68 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - Ferenc Kis was added to the PMC on 2024-12-31 - Lucas Ottersbach was added as committer on 2024-11-12 ## Project Activity: After a concerted multi-year effort Apache NiFi 2.0 has been released! Apache NiFi 2.0 is the first major release for the NiFi community in more than 8 years. It brings a host of important improvements including a completely rebuilt user interface, moves to Java 21 as a minimum, removes many deprecated components, introduces new extensions, and now supports Python extensions as a first class concept running in true Python rather than via Jython. All of this helps provide a strong future for NiFi in the many use cases it has been used for but also increasingly in the emerging unstructured data use cases becoming popular with Generative AI. We've since released Apache NiFi 2.1.0 in late December 2024 as well showcasing our continued momentum on frequent releases and focus on security and staying up to date with dependencies. ## Community Health: JIRA and Mailing list activity remains consistent. The slack community continues to grow and be highly active reaching 3,534 members in the general channel. We continue to produce frequent and substantive releases in the NiFi community and benefit from substantial release vote participation. Mailing list and PR creation, review and closure are all very active. Notably this quarter a venture backed startup claiming support for Apache NiFi was acquired by Snowflake and social media and marketing information from Cloudera continues to describe support for Apache NiFi including the latest 2.x release line. ----------------------------------------- Attachment AW: Report from the Apache Nutch Project [Sebastian Nagel] ## Description: Apache Nutch is a highly extensible and scalable open source web crawler software project based on Apache Hadoop® data structures and the MapReduce data processing framework. ## Project Status: Current project status: ongoing with medium to low activity Issues for the board: none ## Membership Data: Apache Nutch was founded 2010-04-21 (14 years ago) There are currently 23 committers and 23 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Joe Gilvary was added as committer and PMC member on 2024-08-07 ## Project Activity: 1.20 was released on 2024-04-24. The work on Nutch 1.21 is ongoing with bug fixes, dependency upgrades, improvements to the build system. ## Community Health: The number of contributions (Jira issues, commits, activity on the mailing lists) is on steady level, showing a slight increase in the last quarter. ----------------------------------------- Attachment AX: Report from the Apache NuttX Project [Alin Jerpelea] ## Description: The mission of Apache NuttX is the creation and maintenance of software related to a mature, real-time embedded operating system (RTOS) ## Project Status: Current project status: On going with high activity Issues for the board: The project has no issues. ## Membership Data: Apache NuttX was founded 2022-11-16 (2 years ago) There are currently 32 committers and 24 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Yanfeng Liu on 2024-08-15. - Ville Juven was added as committer on 2024-10-25 ## Project Activity: - 12.8.0 released on 06.01.2025(with SPDX headers) - The project has completed the SPDX header implementation. - SBOM implementation planned for next release - aims for Open Chain self certification while looking for other certifications that can be obtained ## Community Health: The community is active on the dev mailing list which saw a 12% traffic increase There are 191 code contributors (12% increase) from various companies There were inquiries if NuttX is certified or used for medical devices Most reported issues were fixed and closed in a timely manner 179 issues opened on GitHub, past quarter (-2% change) 151 issues closed on GitHub, past quarter (5% increase) ----------------------------------------- Attachment AY: Report from the Apache OpenJPA Project [Mark Struberg] ## Description: The mission of OpenJPA is the creation and maintenance of software related to JPA: Object Relational Mapping for Java ## Issues: There are no issues requiring board attention. ## Project Activity: We right now have some implementation discussions in a few tickets and on the list. Apart from that the last quarter war rather silent. ## Membership Data: Apache OpenJPA was founded 2007-05-16 (18 years ago) There are currently 35 committers and 18 PMC members in this project. ## Community changes, past quarter: - No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13. - No new committers. Last addition was Matt Pavlovich on 2019-05-22. ## Recent releases: 4.0.1 was released on 2024-09-27. 4.0.0 was released on 2024-02-14. 3.2.2 was released on 2022-03-16. ----------------------------------------- Attachment AZ: Report from the Apache OpenMeetings Project [Maxim Solodovnik] ## Description: The mission of OpenMeetings is the creation and maintenance of software related to OpenMeetings: Web-Conferencing and real-time collaboration ## Project Status: Current project status: Dormant Issues for the board: none. ## Membership Data: Apache OpenMeetings was founded 2013-01-25 (12 years ago) There are currently 30 committers and 28 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 Ali Alhaidary on 2021-03-22. - No new committers. Last addition was Ali Alhaidary on 2021-04-07. ## Project Activity: We were able to release long waited version 8.0.0 (One CVE has been addressed) I still hope we can add some new features to attract new users :) Recent releases: - 8.0.0 was released on 2025-01-02. - 7.2.0 was released on 2023-12-23. - 7.1.0 was released on 2023-05-09. ## Community Health: We are answering emails, and addressing issues (security issues are addressed in timely manner). Email flow seems to be at constant low level, I'm afraid the only way to increase it is to add new features (maybe perform one more redesign, not sure). ----------------------------------------- Attachment BA: Report from the Apache OpenOffice Project [Dave Fisher] ----------------------------------------- Attachment BB: 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), JSR-365 (CDI-2.0) and Jakarta CDI (CDI-4.0). The OWB community also maintains a small server as Apache Meecrowave subproject. Meecrowave bundles latest releases of the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2. ## Issues: There are no issues requiring board attention at this time. ## Activity: We've improved portability and fixed a few bugs requested by downstream projects. We've also updated/fixed our site setup. Mailing list activity and committs was quite ok. The reporter commit stats might not be correct though as we switched from 'master' to 'main'. We've also shipped an OWB-4.0.3 bugfix release. We are right now preparing a new Meecrowave release. ## Community Health All fine. We got quite some feedback for the release. ## 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 - 4.0.3 was released on 2024-12-14 - 4.0.2 was released on 2024-02-14. - meecrowave-1.2.14 was released on 2022-05-11. ----------------------------------------- Attachment BC: Report from the Apache ORC Project [William Hyun] ## Description: The mission of ORC is the creation and maintenance of software related to the smallest, fastest columnar storage for Hadoop workloads. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache ORC was founded 2015-04-21 (9 years ago) There are currently 49 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. - No new PMC members. Last addition was Pavan Lanka on 2023-03-30. - No new committers. Last addition was Yuanping Wu on 2024-05-14. ## Project Activity: According to our release cadence, we released three maintenance releases in this quarter and helped other Apache communities use them. - 1.8.8 was released on 2024-11-11. - 1.9.5 was released on 2024-11-14. - 2.0.3 was released on 2024-11-14. In addition, we are preparing the following milestones for the next quarter. - 2.1.0 (January) - 2.0.4 (March) - 1.9.6 (May) ## Community Health: In this quarter, we have seen an overall increase in activities with an increase of 80% and 150% for GitHub PRs and issues closed respectively. With a 20% increase in traffic for the dev mailing list, which is a good sign for community growth. ----------------------------------------- Attachment BD: Report from the Apache Parquet Project [Julien Le Dem] Parquet Report Jan 2025 ## Description: A column-oriented data file format designed for efficient data storage and retrieval. It provides high performance compression and encoding schemes to handle complex data in bulk and is supported in many programming languages and analytics tools. Parquet consists of a format specification (the Parquet format) and several implementations, one of which (Parquet Java) is developed directly under the umbrella of the Apache Parquet project. Non-Apache implementations also exist, some of them closed source. ## Project Status: Current project status: Ongoing - improve Parquet footer metadata using Flatbuffers. - Define a Variant type based on the work from the Spark project - Add Geometry types ## Issues for the board: none ## Membership Data: Apache Parquet was founded 2015-04-21 (10 years ago) There are currently 39 committers and 30 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 Antoine Pitrou on 2024-07-17. - No new committers. Last addition was Xuwei Fu on 2024-07-11. ## Project Activity: Recent Parquet Java releases: 1.14.3 was released on 2024-10-05. 1.14.2 was released on 2024-08-28. 1.14.1 was released on 2024-06-16. Other Parquet open source implementations are released on their own basis by their respective Apache projects (notably Arrow C++, Arrow Rust, Arrow Go). - The Variant type spec is fairly close to being complete and the shredding spec is being finalized. Outstanding discussion related to whether we should have undefined behavior or not in the presence of incorrect shredding. We need an owner for driving the implementation of a second implementation of the spec besides parquet-java. The two main candidates are either C++ (in Arrow/cpp) or Rust (in arrow-rs). https://github.com/apache/arrow-rs/issues/6736 - Parquet footer improvement experimentations to be further discussed. The POC for the new footer is in progress. Some of the metadata removed for compactness is needed by some readers. We need to iterate to solve this. https://github.com/apache/arrow/pull/43793 - Geometry type: The main discussion is happening in the Iceberg ticket. Follow up work in Parquet is expected to come from the conclusions of that discussion. Iceberg Geometry/Geography type PR: https://github.com/apache/iceberg/pull/10981 Parquet Geometry type PR: https://github.com/apache/parquet-format/pull/240 ## Community Health: Healthy community. Regular discussions are held: - on the mailing list and github - in a recurring bi-weekly online meeting open to all and notes are posted on the mailing list. ----------------------------------------- Attachment BE: Report from the Apache PDFBox Project [Andreas Lehmkühler] ## Description: The mission of PDFBox is the creation and maintenance of software related to Java library for working with PDF documents ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: none ## Membership Data: Apache PDFBox was founded 2009-10-21 (15 years ago) There are currently 21 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Matthäus Mayer on 2017-10-16. - No new committers. Last addition was Joerg O. Henne on 2017-10-09. ## Project Activity: Recent releases: 3.0.3 was released on 2024-08-08. 2.0.32 was released on 2024-07-24. 2.0.31 was released on 2024-03-24. ## Community Health: - there is a steady stream of contributions, bug reports and questions on the mailing lists - we start to prepare the 2.0.33 release. Our pre release text extraction test revealed some issues. some of them are already solved - once 2.0.33 is out, we are going to cut the 3.0.4 release - Tilman started to clean up some of our old tickets ----------------------------------------- Attachment BF: Report from the Apache Petri Project [Dave Fisher] ## Description: The mission of Apache Petri is the creation and maintenance of software related to assessment of, education in, and adoption of the Foundation's policies and procedures for collaborative development and the pros and cons of joining the Foundation ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache Petri was founded 2019-11-19 (5 years ago) There are currently 8 committers and 5 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Daniel Shahaf on 2019-11-19. - No new committers. Last addition was Justin Erenkrantz on 2020-04-23. ## Project Activity: There will be a PMC Chair change resolution for this meeting. ## Community Health: We are willing to discuss adjustments to our mission. For example expanding to provide guidance about ways a PMC can adjust to better follow our Way. ----------------------------------------- Attachment BG: Report from the Apache Pig Project [Koji Noguchi] ----------------------------------------- Attachment BH: Report from the Apache Pivot Project [Roger Lee Whitcomb] ----------------------------------------- Attachment BI: Report from the Apache Ranger Project [Selvamohan Neethiraj] ----------------------------------------- Attachment BJ: Report from the Apache Ratis Project [Tsz-wo Sze] ## Description: The mission of Apache Ratis is the creation and maintenance of software related to a highly customizable Raft protocol implementation in Java ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Ratis was founded 2021-02-16 (4 years ago) There are currently 31 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was William Song on 2024-01-18. - No new committers. Last addition was Xinyu Tan on 2024-08-27. ## Project Activity: We released Ratis 3.1.2 on 2024-11-13. It is a maintenance release with improvements and bug fixes. We also released Ratis-Thirdparty 1.0.7 and 1.0.8 respectively on 2024-11-27 and 2024-12-27. They mainly update the third party library versions. We are currently discussing the next Ratis 3.1.3 maintenance release. The previous Ratis 3.1.1 and Ratis Thirdparty 1.0.6 respectively on 2024-09-26 and 2024-05-14. ## Community Health: The project is healthy. In this quarter, we have less email traffic (23% decrease in dev@, 89% decrease in user@), less commits (25% decrease) and less contributors (14% decrease). On the other hand, we have more pull requests opened (30% increase) and closed (60% increase). One of the major focuses in the development is the gRPC zero-copy feature. ----------------------------------------- Attachment BK: Report from the Apache Rya Project [Adina Crainiceanu] ## Description: The mission of Apache Rya is the creation and maintenance of software related to scalable storage, retrieval, and analysis of RDF data ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache Rya was founded 2019-09-17 (5 years ago) There are currently 12 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members since project became a top-level project. Last addition was David Lotts on 2016-11-17. - No new committers were added. ## Project Activity: No new activity. Last release 4.0.1 was on 2020-12-22 ## Community Health: There is no current activity in the project. The software is used in production by users. The project is in "dormant" state: not much happening on the code, but at least 3 PMC members ready to engage if needed dev@rya.apache.org had a 0% decrease in traffic in the past quarter (1 emails compared to 1) 0 commits in the past quarter (no change) 0 code contributors in the past quarter (no change) ----------------------------------------- Attachment BL: Report from the Apache Samza Project [Jagadish Venkatraman] ----------------------------------------- Attachment BM: Report from the Apache SeaTunnel Project [Jun Gao] ----------------------------------------- Attachment BN: Report from the Apache SkyWalking Project [Sheng Wu] ## Description: The mission of Apache SkyWalking is the creation and maintenance of software related to application performance management and monitoring (APM) ## Project Status: Current project status: Ongoing Issues for the board: No issue ## Membership Data: Apache SkyWalking was founded 2019-04-17 (6 years ago) There are currently 62 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - Zixin Zhou was added to the PMC on 2024-12-30 - No new committers. Last addition was Claire Chen on 2024-05-27. ## Project Activity: 3 new released are launched - php-0.8.0 was released on 2024-12-06. - 10.1.0 was released on 2024-10-01. - nginx-lua-1.0.1 was released on 2024-09-30. SkyWalking community decided to remove H2 storage option. BanyanDB subporject is moving forward to GA. ## Community Health: 199 PRs opened on GitHub, past quarter (93% increase) 207 PRs closed on GitHub, past quarter (130% increase) 67 issues opened on GitHub, past quarter (157% increase) 70 issues closed on GitHub, past quarter (400% increase) The community goes well. Hundreds of discussions happened on GH Discussion. We are preparing the 10.2 with BanyanDB 0.8. This would be a product ready version for the new database. ----------------------------------------- Attachment BO: Report from the Apache Steve Project [Daniel Gruno] ----------------------------------------- Attachment BP: Report from the Apache Struts Project [René Gielen] ## Description: The Apache Struts MVC framework is a solution stack for creating modern and elegant action-based Java web applications. It favours convention over configuration, is extensible using a plugin architecture, and ships with plugins to support patterns and technologies such as REST, AJAX and JSON. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Struts was founded 2004-03-17 (21 years ago) There are currently 60 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Kusal Kithul-Godage on 2024-02-24. - No new committers. Last addition was Kusal Kithul-Godage on 2023-08-03. ## Project Activity: The Struts team made three releases in the reporting period: - Struts 6.6.1 - Bug Fix Release (2024-10-18) [1] - Struts 6.7.0 - Feature and Bug Fix Release (2024-11-17) [2] - Struts 7.0.0 - Major Feature Release (2024-12-19) [3] The last Struts releases besides the core framework were - Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06) - Struts Annotations 1.0.8 - Enhancements in preparation for the next framework release (2022-11-05) The last quarter was an exceptionally busy one for the Struts community. The team released Struts 6.6.1 in October [1], followed by Struts 6.7.0 in November [2]. On December 12, the team released security bulletin S2-067 [4][5]. The announced vulnerability CVE-2024-53677 is of maximum severity and was complicated to fix, since the whole file upload mechanism had to be redesigned to address and fix the issue. Thanks to the whole team for their hard work, as well as the Apache Security Team for their continuous and comprehensive support. Later in December, we had more positive news to announce: The long awaited new major Struts version 7.0.0 was released on December 20 [3]. Among other things it features Jakarta EE support and requires Java 17 as a minimum. We have no issues that require board assistance at this time. ## Community Health ### Development activity in the reporting period We had 101 PRs opened and 97 closed in the main project. This is again more activity than in the preceding quarter. ### Mailing list activity: - dev@struts.apache.org had a 159% increase in traffic in the past quarter (161 emails compared to 62) - issues@struts.apache.org had a 116% increase in traffic in the past quarter (694 emails compared to 321) - notifications@struts.apache.org had a 80% increase in traffic in the past quarter (730 emails compared to 404) [1] https://struts.apache.org/announce-2024#a20241018 [2] https://struts.apache.org/announce-2024#a20241117 [3] https://struts.apache.org/announce-2024#a20241219 [4] https://struts.apache.org/announce-2024#a20241210 [5] https://cwiki.apache.org/confluence/display/WW/S2-067 ----------------------------------------- Attachment BQ: 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: Current project status: Active Issues for the board: None ## Membership Data: Apache Synapse was founded on 2007-12-19 (18 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: Project activity has increased significantly. A suggestion was made to rewrite Synapse in GO lang, leading to the creation of a new GitHub repository named Synapse-Go to facilitate this initiative. The repository has already received the initial code contribution via a pull request. Active discussions are ongoing on the developer list regarding this development. ## Community Health: The dev@synapse.apache.org mailing list experienced an 1800% increase in traffic this past quarter (19 emails compared to 1 in the previous quarter), indicating revived community engagement and interest in the project's future. ----------------------------------------- Attachment BR: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo] ## Description: The mission of Tapestry is to provide a comprehensive component-oriented framework for building dynamic and scalable web applications in Java, with a focus on developer productivity and extensibility. ## Project Status: Current project status: ongoing (moderate/low) Issues for the board: none ## Membership Data: Apache Tapestry was founded 2006-02-15 (19 years ago) There are currently 30 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-03. - No new committers. Last addition was Christian Köberl on 2024-05-02. ## Project Activity: Testing for the second 5.9.0 preview released with Jakarta EE support is ongoing, with positive internal and community feedback and few issues. The next release is expected to be the final version. Efforts continue to address community-raised issues in a more timely manner, and cleaning up the backlog by identifying and closing stale issues/PRs to better reflect the current state of the project and enhance contributor experience. Work on updating the project website is progressing to improve support for Jakarta EE and javax, making documentation more straightforward and more accessible. We're trying to identify key third-party dependencies and explore how to work closer with the authors and eventually bring them under a more community-driven umbrella for the long-term stability without increasing the number of sub-projects. No additional releases were done, as work is still mostly focused on feedback from 5.9.0 preview 2 (released 2024-09-19) and improvements for the upcoming final 5.9.0 release. ## Community Health: December was slower due to the holiday season, as expected. Overall, it was a good quarter, with similar activity and mailing list traffic as usual: +6% activity on dev@tapestry.apache.org (31 vs 29) -18% activity on users@tapestry.apache.org (19 vs 23) There were 24 commits last quarter on the primary development branch and there's one outstanding PR related to current development. Three PRs were merged of the 15 closed, as the latter were either stale or no longer applicable. The upcoming Jakarta EE support has been well received by the community, leading to engagement and discussions. JIRA activity stats for the last quarter: 7 open and actively discussed issues 17 closed/resolved ----------------------------------------- Attachment BS: Report from the Apache Tcl Project [Georgios Petasis] ## Description: The mission of Tcl is the creation and maintenance of software related to Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration efforts. The purpose of our project is to combine the power of the Apache web server with the capabilities of the mature, robust and flexible Tcl scripting language. Currently only the Apache Rivet project is actively maintained. ## Project Status: Current project status: Ongoing Issues for the board: Delays in board reporting, due to a series of personal events. ## Membership Data: Apache Tcl was founded 2000-07-24 (24 years ago) There are currently 12 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Brice Hamon De Crevecoer on 2014-11-25. - No new committers. Last addition was Brice B. Hamon on 2014-11-25. ## Project Activity: During this reporting period, rivet 3.2.6 (released on 2024-11-12) has been released. Rivet 3.2.6 improves DIO, an Itcl based DBMS access abstraction layer, with a new connector that supports the TDBC series of connectors (all these relate to connecting to relational DBs). There is a discussion whether the whole infrastructure should be ported to TclOO, as it is better supported in Tcl 9.0. ## Community Health: The traffic of the mailing lists has increased in comparison to the previous reporting period, which is normal for the project (as most traffic in the list happens after new releases). ----------------------------------------- Attachment BT: Report from the Apache Tez Project [László Bodor] ----------------------------------------- Attachment BU: Report from the Apache Thrift Project [Jens Geyer] ## Description: Apache Thrift is a high performance cross platform RPC and serialization solution. ## Project Status: Current project status: Ongoing moderate Issues for the board: none ## Membership Data: Apache Thrift was founded 2010-10-20 (14 years ago) There are currently 41 committers and 21 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 Mario Emmenlauer on 2022-04-13. - No new committers. Last addition was Liu Jiayu on 2022-06-25. ## Project Activity: Working towards next release scheduled for Feb 2025. Last release 0.21.0 on 2024-09-21. ## Community Health: Misc. activities on moderate levels on all channels (Jira, mailing lists, Github). Steady flow of incoming contributions from current and new contributors. ----------------------------------------- Attachment BV: Report from the Apache Tika Project [Tim Allison] ## Description: Apache Tika is a dynamic toolkit for content detection, analysis, and extraction. It allows a user to understand, and leverage information from, a growing a list of over 1200 different file types including most of the major types in existence (MS Office, PDF, Text, Images, Video, Code, and science data) as recognized by IANA and other standards bodies. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Tika was founded 2010-04-20 (15 years ago) There are currently 32 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05. - No new committers. Last addition was Nicholas DiPiazza on 2021-06-03. ## Project Activity: We released 3.0.0 (minimum JRE 11) in October 2024, and started a 4.x branch (minimum JRE 17). We announced an EOL for 2.x (JRE 8) in April 2025. We have plans for some significant refactorings of the tika-pipes modules in 4.x, but most of the rest of the project will remain the same. ## Community Health: Chi is 4.70. Email traffic is lower this quarter, possibly driven by the holidays. We continue to be on the lookout for new committers/PMC members. ----------------------------------------- Attachment BW: Report from the Apache TinkerPop Project [Kelvin Lawrence] ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). ## Project Status: Project state: The project is ongoing with moderate activities this past quarter. Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache TinkerPop was founded 2016-05-17 (9 years ago) There are currently 30 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Yang Xia on 2023-03-14. - Norio Akagi was added as committer on 2024-10-31 ## Project Activity: We released 3.6.8 and 3.7.3 on 2024-10-23, which contained a number of security updates, bug fixes in the core functionality, as well as updates to improve implementation extensibility for providers. This was also the last release of the 3.6.x line [1], as future development will be focused on new features for TinkerPop 4.0 and maintenance for 3.7.x. The community continues to be active in development for the next major release of TinkerPop 4.0, aimed at increasing maintainability, usability, extensibility, and security of the project. Implementation of the Gremlin Server, as well as the Java and Python drivers has been wrapping up as the community prepares for a milestone preview of TinkerPop 4.0.0, for early user preview, testing and feedback on the current implementation. Out of abundance of caution, the milestone release was held off for additional testing, with new dates in discussion [2]. ### Releases: 3.6.8 was released on 2024-10-23. 3.7.3 was released on 2024-10-23. ## Community Health: The TinkerPop Community continues to have a steady flow of activity from core committers, and occasional contributions from outside sources are in line with previous quarters. Several TinkerPop providers have also released new updates. G.V(), an all-in-one client for Gremlin graph database recently released 3.9.32 [3], offering new free-tier access and improved result visualization. Gremify [4], a cloud-based platform providing Gremlin query execution and visualization for Gremlin users of all levels, recently released support for TinkerPop 3.7.3. We hosted another exciting live event on Twitch [5], where we invited an external contributor to discuss his work on a GQL to Gremlin transpiler, a prototype optimizer and discuss how the GQL standard [6] could help further develop TinkerPop. All the recordings are available on our YouTube channel [7]: * TinkerPop Wide: GQL to Gremlin [8] Presenter: William Saffery ## Report Links [1]: https://lists.apache.org/thread/ysc1ov4l3x3v3nyjr3b7z05tml7s7o46 [2]: https://lists.apache.org/thread/hh58k28qy49lb9k7b9j4mnqvpxj0xf85 [3]: https://gdotv.com/blog/g-v-3-9-32-release-notes/ [4]: https://gremlify.com/ [5]: https://www.twitch.tv/apachetinkerpop [6]: https://www.gqlstandards.org/ [7]: https://www.youtube.com/@apachetinkerpop [8]: https://www.youtube.com/watch?v=Kd0i-ieni6M ----------------------------------------- Attachment BX: Report from the Apache Traffic Server Project [Bryan Call] ----------------------------------------- Attachment BY: Report from the Apache Web Services Project [Daniel Kulp] ----------------------------------------- Attachment BZ: Report from the Apache Zeppelin Project [Jongyoul Lee] ## Description: The mission of Zeppelin is the creation and maintenance of software related to A web-based notebook that enables interactive data analytics ## Project Status: Current project status: Dormant. There are at least 3 PMC members can participate in some urgent situation and are contributing to the project regularly. Issues for the board: We have 4-5 security issues which are not published yet. The community is voting a new release including security fixes. ## Membership Data: Apache Zeppelin was founded 2016-05-18 (9 years ago) There are currently 25 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Cheng Pan on 2024-08-25. - No new committers. Last addition was Cheng Pan on 2024-08-25. ## Project Activity: The community tried to improve existing features. It changed the default web UI to a new version of Angular and prepared to release it with a new version. For interpreters, the comunity upgraded some interpreters with newer versions. The community discussed a new version of Apache Zeppelin and it concluded that it wouldn't be enough to get 1.0.0 yet. After stabilizing a new UI and compoenents, it will release 1.0.0. ## Community Health: In the this reporting period, some contributors focused on their efforts to contribute code, implemented features, and fixed some bugs and inefficient code. In the year-end season, there's not much contributions. ------------------------------------------------------ End of minutes for the January 15, 2025 board meeting.