The Apache Software Foundation Board of Directors Meeting Minutes June 19, 2024 1. Call to order The meeting was scheduled for 21:00 UTC and began at 21:02 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/43ft 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 Christofer Dutz Willem Ning Jiang - joined :05 Jeff Jirsa Justin Mclean Jean-Baptiste Onofré Sander Striker - joined :04 Directors Absent: Craig L Russell Executive Officers Present: Craig R. McClanahan David Nalley Matt Sicker Ruth Suehle Executive Officers Absent: none Guests: Bob Paulin - parted :29 Brian Proffitt Daniel Augusto Veronezi Salvador Daniel Gruno Dave Fisher - joined :06 Gavin McDonald Greg Stein Kanchana Pradeepika Welagedara Kim McMahon Paul King Philipp Ottlinger Sally Khudairi 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of May 15, 2024 See: board_minutes_2024_05_15.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Shane Curcuru] Our board face to face strategy meeting was a success, and enabled the board as a whole to gel together and build consensus on some of the strategic issues facing the ASF. Directors, officers, and guests attending all collaborated incredibly well to get us through the whole agenda on time, and got us to some sort of consensus as to next steps on all items. Our VP, Public Affairs and President provided key F2F briefings on legislative changes coming to open source, from CRA, AI Act, CIRCIA, and more. These legal changes to how software can be built and released to the market will force far-reaching changes one processes for all of our project communities. The board is committed to building the operational infrastructure and tooling needed to ensure complying with the CRA will be as simple as we can make it for ASF projects. VP. Marketing & Publicity also briefed the board on various branding activities happening around our #ASF25Years anniversary, and is ensuring we have ample plans and messaging to smoothly capitalize on this campaign through the year. Having plenty of in person time in our F2F meeting allowed the board to dig deeply into questions around our strategy, where the ASF is heading, and how we can truly be a better home with improved services for our project communities. I look towards all our volunteers to find the time this summer to refine and implement some of the process and tooling improvements we're exploring, so we can make it easier for all projects to ship more software. B. President [David Nalley] I had the pleasure of attending Community over Code in Bratislava and immensely enjoyed meeting with newcomers to the ASF as well old friends. I also attended the Board face to face which felt like a very useful expenditure of time. Separately from that, I've been invited in my role as President to speak on a panel at the United Nations on July 10, 2024. After consulting with Dirk-Willem van Gulik I have accepted that speaking slot and plan to be present. As I said at the Board offsite, I do think that we are entering upon an era when legislative and regulatory pressures are going to change some of the underlying methods of operation of the foundation. We have a small opportunity at this juncture to both influence the standards that are being created, as well as establish the ASF as a leader in how open source is done well. I think the work that Myrle Krantz and Greg Stein have done in charting a path for future tooling is a big part of whether we'll be seen as a leader or not, and look forward to the board discussing that. Finally - I have submitted a proposed budget for the board's review, which was long overdue. The majority of the credit is due to Ruth Suehle for assembling it. Additionally, please see Attachments 1 through 9. @David: follow up with report about shadow infrastructure budget C. Treasurer [Craig R. McClanahan] More typical work, things operating normally. We also coordinated with sponsors for the CoC EU and CoC NA conferences as needed. D. Secretary [Matt Sicker] In May, the secretary received 69 ICLAs, 1 CCLA, 1 software grant, and 1 CoI affirmation. E. Executive Vice President [Ruth Suehle] Bratislava conversations were productive. It was great to see folks in person. I've submitted RFPs to four potential cities for Community Over Code NA 2025 in hopes of announcing the dates and location during the 2024 Denver event. Planning out the new brand launch timing to be sure that we have updated swag for CoC Denver! F. Vice Chair [Justin Mclean] Nothing that needed help with this month. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Justin] See Attachment 10 B. Apache Legal Affairs Committee [Roman Shaposhnik / Jeff] See Attachment 11 C. Apache Security Team Project [Mark J. Cox / JB] See Attachment 12 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Iceberg [jbo] # TomEE [jmclean] A. Apache Airflow Project [Bolke de Bruin / Rich] See Attachment A B. Apache Allura Project [David Philip Brondsema / Sander] See Attachment B C. Apache Aries Project [Christian Schneider / Christofer] No report was submitted. D. Apache Atlas Project [Madhan Neethiraj / Craig] See Attachment D E. Apache Attic Project [Herve Boutemy / Shane] No report was submitted. F. Apache Axis Project [Robert Lazarski / Willem] See Attachment F G. Apache Beam Project [Kenneth Knowles / JB] See Attachment G H. Apache Bigtop Project [Masatake Iwasaki / Craig] No report was submitted. I. Apache Bloodhound Project [Gary Martin / Shane] See Attachment I J. Apache BVal Project [Matthew Jason Benson / Sander] No report was submitted. K. Apache Camel Project [Andrea Cosentino / Willem] See Attachment K L. Apache Cayenne Project [Michael Ray Gentry / Shane] See Attachment L M. Apache Celeborn Project [Keyong Zhou / Jeff] See Attachment M N. Apache CloudStack Project [Daniel Augusto Veronezi Salvador / Rich] See Attachment N O. Apache Commons Project [Gary D. Gregory / Christofer] See Attachment O P. Apache Cordova Project [Bryan Ellis / Justin] See Attachment P Q. Apache cTAKES Project [Pei Chen / Christofer] See Attachment Q R. Apache Curator Project [Enrico Olivelli / Craig] See Attachment R S. Apache Daffodil Project [Mike Beckerle / Rich] See Attachment S T. Apache DataFusion Project [Andrew Lamb / Sander] See Attachment T U. Apache ECharts Project [Wenli Zhang / Jeff] See Attachment U V. Apache Felix Project [Karl Pauls / Justin] See Attachment V W. Apache Flex Project [Harbs / JB] See Attachment W X. Apache Flink Project [Robert Metzger / Shane] See Attachment X Y. Apache Gora Project [Kevin Ratnasekera / Shane] See Attachment Y Z. Apache Gobblin Project [Abhishek Tiwari / Sander] See Attachment Z AA. Apache Guacamole Project [Mike Jumper / Justin] See Attachment AA AB. Apache Gump Project [Stefan Bodewig / Shane] See Attachment AB AC. Apache Helix Project [Junkai Xue / Craig] See Attachment AC AD. Apache Hive Project [Naveen Gangam / Jeff] No report was submitted. AE. Apache Hudi Project [Vinoth Chandar / Rich] See Attachment AE AF. Apache Iceberg Project [Ryan Blue / Christofer] See Attachment AF AG. Apache Incubator Project [Justin Mclean] See Attachment AG AH. Apache IoTDB Project [Xiangdong Huang / JB] See Attachment AH AI. Apache Jackrabbit Project [Marcel Reutegger / Willem] See Attachment AI AJ. Apache Johnzon Project [Jean-Louis Monteiro / Justin] No report was submitted. AK. Apache Karaf Project [Jean-Baptiste Onofré] See Attachment AK AL. Apache Kudu Project [Andrew Wong / JB] See Attachment AL AM. Apache Kvrocks Project [Hulk Lin / Willem] See Attachment AM AN. Apache Kyuubi Project [Kent Yao / Shane] See Attachment AN AO. Apache Linkis Project [Shuai Di / Jeff] See Attachment AO AP. Apache Lucene Project [Chris Hegarty / Sander] See Attachment AP AQ. Apache Lucene.Net Project [Shad Storhaug / Rich] No report was submitted. AR. Apache Mnemonic Project [Gordon King / Sander] No report was submitted. AS. Apache Mynewt Project [Szymon Janc / Craig] No report was submitted. AT. Apache NetBeans Project [Geertjan Wielenga / Christofer] See Attachment AT AU. Apache OFBiz Project [Jacopo Cappellato / Justin] See Attachment AU AV. Apache Olingo Project [Michael Bolz / Rich] See Attachment AV AW. Apache OpenDAL Project [Hao Ding / Willem] See Attachment AW AX. Apache OpenJPA Project [Mark Struberg / Sander] No report was submitted. AY. Apache OpenNLP Project [Jeff Zemerick / JB] See Attachment AY AZ. Apache OpenWebBeans Project [Mark Struberg / Shane] No report was submitted. BA. Apache Paimon Project [Jingsong Lee / Sander] See Attachment BA BB. Apache Pekko Project [PJ Fanning / Christofer] See Attachment BB BC. Apache Pig Project [Koji Noguchi / Christofer] No report was submitted. BD. Apache Pivot Project [Roger Lee Whitcomb / Craig] No report was submitted. BE. Apache PLC4X Project [Christofer Dutz] See Attachment BE BF. Apache Portable Runtime (APR) Project [Yann Ylavic / Jeff] See Attachment BF BG. Apache Portals Project [Neil Griffin / Craig] See Attachment BG BH. Apache Pulsar Project [Matteo Merli / JB] No report was submitted. BI. Apache Ranger Project [Selvamohan Neethiraj / Justin] See Attachment BI BJ. Apache Royale Project [Yishay Weiss / Rich] See Attachment BJ BK. Apache SDAP Project [Nga Thien Chung / Willem] See Attachment BK BL. Apache SeaTunnel Project [Jun Gao / Jeff] See Attachment BL BM. Apache ServiceMix Project [Krzysztof Sobkowiak / Christofer] See Attachment BM BN. Apache Shiro Project [Brian Demers / Shane] See Attachment BN BO. Apache SINGA Project [Wang Wei / Sander] See Attachment BO BP. Apache Sling Project [Robert Munteanu / JB] See Attachment BP BQ. Apache SpamAssassin Project [Sidney Markowitz / Shane] See Attachment BQ BR. Apache Storm Project [Richard Zowalla / Willem] See Attachment BR BS. Apache Streams Project [Steve Blackmon / Craig] No report was submitted. BT. Apache TomEE Project [David Blevins / Shane] See Attachment BT @Justin: follow up with PMC about board report sections BU. Apache Synapse Project [Isuru Udana / Christofer] No report was submitted. BV. Apache Tomcat Project [Mladen Turk / Jeff] See Attachment BV BW. Apache TVM Project [Tianqi Chen / Justin] See Attachment BW BX. Apache UIMA Project [Richard Eckart de Castilho / Rich] No report was submitted. BY. Apache Unomi Project [Serge Huber / Sander] See Attachment BY BZ. Apache VCL Project [Josh Thompson / Craig] See Attachment BZ CA. Apache Wicket Project [Andrea Del Bene / Sander] See Attachment CA CB. Apache Yetus Project [Allen Wittenauer / Rich] See Attachment CB CC. Apache ZooKeeper Project [Flavio Paiva Junqueira / Jeff] See Attachment CC Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Impala Project Chair WHEREAS, the Board of Directors heretofore appointed Jim Apple (jbapple) to the office of Vice President, Apache Impala, and WHEREAS, the Board of Directors is in receipt of the resignation of Jim Apple from the office of Vice President, Apache Impala, and WHEREAS, the Project Management Committee of the Apache Impala project has chosen by vote to recommend Zoltán Borók-Nagy (boroknagyz) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jim Apple is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Impala, and BE IT FURTHER RESOLVED, that Zoltán Borók-Nagy be and hereby is appointed to the office of Vice President, Apache Impala, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Impala Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Logging Services Project Chair WHEREAS, the Board of Directors heretofore appointed Volkan Yazici (vy) to the office of Vice President, Apache Logging Services, and WHEREAS, the Board of Directors is in receipt of the resignation of Volkan Yazici from the office of Vice President, Apache Logging Services, and WHEREAS, the Project Management Committee of the Apache Logging Services project has chosen by vote to recommend Piotr Karwasz (pkarwasz) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Volkan Yazici is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Logging Services, and BE IT FURTHER RESOLVED, that Piotr Karwasz be and hereby is appointed to the office of Vice President, Apache Logging Services, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache Logging Services Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache Cassandra Project Chair WHEREAS, the Board of Directors heretofore appointed Josh McKenzie (jmckenzie) to the office of Vice President, Apache Cassandra, and WHEREAS, the Board of Directors is in receipt of the resignation of Josh McKenzie from the office of Vice President, Apache Cassandra, and WHEREAS, the Project Management Committee of the Apache Cassandra project has chosen by vote to recommend Dinesh Joshi (djoshi) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Josh McKenzie is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Cassandra, and BE IT FURTHER RESOLVED, that Dinesh Joshi be and hereby is appointed to the office of Vice President, Apache Cassandra, 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 Cassandra Project Chair, was approved by Unanimous Vote of the directors present. D. Change the Apache Kvrocks Project Chair WHEREAS, the Board of Directors heretofore appointed Hulk Lin (hulk) to the office of Vice President, Apache Kvrocks, and WHEREAS, the Board of Directors is in receipt of the resignation of Hulk Lin from the office of Vice President, Apache Kvrocks, and WHEREAS, the Project Management Committee of the Apache Kvrocks project has chosen by vote to recommend Mingyang Liu (twice) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Hulk Lin is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Kvrocks, and BE IT FURTHER RESOLVED, that Mingyang Liu be and hereby is appointed to the office of Vice President, Apache Kvrocks, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache Kvrocks Project Chair, was approved by Unanimous Vote of the directors present. E. Establish Position of VP, Tooling WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to appoint an officer responsible for developing software tooling to support Foundation operations, governance, and communities, for purposes including but not limited to supporting software releases, and support tools for board meetings. NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President, Tooling" be and hereby is created, the person holding such office to serve at the direction of the President, and to have responsibility for hiring and managing one or more paid staff who will develop tooling to support Foundation operations, governance, and communities. BE IT FURTHER RESOLVED, that Myrle Krantz be and hereby is appointed to the office of Vice President, Tooling, to serve in accordance with and subject to the direction of the President until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Establish Position of VP, Tooling, was approved by Unanimous Vote of the directors present. F. Change the Apache Parquet Project Chair WHEREAS, the Board of Directors heretofore appointed Xinli Shang (shangxinli) to the office of Vice President, Apache Parquet, and WHEREAS, the Board of Directors is in receipt of the resignation of Xinli Shang from the office of Vice President, Apache Parquet, and WHEREAS, the Project Management Committee of the Apache Parquet project has chosen by vote to recommend Julien Le Dem (julien) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Xinli Shang is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Parquet, and BE IT FURTHER RESOLVED, that Julien Le Dem be and hereby is appointed to the office of Vice President, Apache Parquet, 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 7F, Change the Apache Parquet Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Fundraising Strategy And Future Needs Brief presentation and discussion with VP, Fundraising on current fundraising strategy, and needs/asks going forward. A key focus will be how we can grow our fundraising capability to meet the significant funding needs we'll have to meet CRA and other legislative requirements in the next 1-5 years. Discussed at start of meeting before PMC reports. B. FY2025 Budget Process Discussion around the in-progress FY2025 budget proposal from President/operations; including any increases related to CRA or other legislative compliance, or around VP, Tooling and other operational improvement proposals. C. Project Reporting Improvement Pilots At our recent F2F meeting, the board discussed ideas around improving our project reporting process, both to ensure the board gets accurate and useful data from PMC reports, and especially ways to make reporting easier and more valuable for our project communities. Discussion around refining those ideas and planning pilot program(s). Tabled for later discussion. D. Proposed FY2025 Budget Income Total Public Donations $150,000 Total Sponsorship $2,600,000 Total Programs $0 Interest Income $0 Conference $250,000 Total Income $3,000,000 Expense General & Administrative $125,000 Brand Management $80,000 ComDev $10,000 Conferences $200,000 Fundraising $108,000 Infrastructure $1,900,000 Privacy $5,000 Publicity $222,750 Travel Assistance $60,000 Treasury $50,000 Security $6,000 Governmental Affairs $100,000 Legal Affairs $25,000 Total Expense $2,760,750 Net $239,250 The board approved the budget by unanimous vote. 9. Review Outstanding Action Items * Sander: follow up on project pivot status [ Mnemonic 2024-03-20 ] Status: https://lists.apache.org/thread/w7gq5vrj7t74dkpdvt9y5j4qrok6ok4d, https://lists.apache.org/thread/mb7xmcfo8smlv8wqft35yrcnxvhk35ky. * David: reach out on list about strategy for D&I position [ Diversity and Inclusion 2024-04-17 ] Status: * Christofer: pursue a roll call vote [ Griffin 2024-04-17 ] Status: Sent roll-call email with a deadline set to the 27th of June 18.07.2024: Not a single response within the last 5 days. Will send another reminder in 2 days. * Sander: follow up on trademark question [ HBase 2024-04-17 ] Status: Issue is resolved: https://lists.apache.org/thread/3rw93c92r3lrcd98l0zk1s1q7g8q4frd * Christofer: pursue a roll call vote [ MADlib 2024-04-17 ] Status: Got contacted by Ed from the Madlib project asking us to help with doing a roll call. It From the discussions on the list, it seems as if the company providing a large percentage of the active PMC members has shifted to a closed-source model for their products, they have stopped contributing. Sent roll-call email with a deadline set to the 27th of June. 18.06.2024: Got two responses so far ... will send reminders in 2 days. * Shane: figure out username policy [ MyFaces 2024-04-17 ] Status: * Christofer: look into development activity [ Pig 2024-04-17 ] Status: * Christofer: pursue a roll call vote [ Synapse 2024-04-17 ] Status: Sent roll-call email with a deadline set to the 27th of June 18.06.2024: Got two replies saying there would be enough people hanging around. Left a message, that it then should not be a problem to get a third one to respond. Will send another reminder in 2 days. * Rich: continue conversing with PMC around tooling and oversight [ Tcl 2024-04-17 ] Status: Done. Our message has been delivered, and they can do with it as they see fit. * Sander: follow up on trademark issue [ Tez 2024-04-17 ] Status: Asked to confirm assumption that there were no issues. * Rich: follow up about metrics tooling [ Traffic Server 2024-04-17 ] Status: Require further board discussion here, TBH. Are we going to ask Infra or Tooling to provide project metrics? Is this, possibly, part of our Project Reporting changes? * Justin: follow up with AGE PMC about corporate branding issue [ AGE 2024-05-15 ] Status: Done * Justin: follow up with Docker distribution [ AGE 2024-05-15 ] Status: Done * Rich: follow up about lack of BuildStream.a.o website and related policy [ BuildStream 2024-05-15 ] Status: * Rich: pursue a roll call for Empire-db PMC [ Empire-db 2024-05-15 ] Status: Roll call requested: https://lists.apache.org/thread/msvmgwmmw4txrjz97pfygf0gs036jn81 Project has adequate oversight. Done * Shane: follow up on Attic [ Bloodhound 2024-05-15 ] Status: * Sander: follow up about including releases in board reports [ EventMesh 2024-05-15 ] Status: Set reminder for myself to remind the project for the August report. * Rich: follow up about potential Attic resolution [ Geode 2024-05-15 ] Status: Done: Shane posted a thoughtful "here's stuff to think about and do before going to the Attic" message on June 4th. * Sander: pursue a roll call for OpenJPA [ OpenJPA 2024-05-15 ] Status: Initiated. * Rich: follow up on trademark issue raised by Superset [ Superset 2024-05-15 ] Status: Encouraged them to ask trademarks@ first, as I'm unable to find a thread there in the last six months about this issue. * Justin: follow up on Kapa.ai usage [ Superset 2024-05-15 ] Status: Done * Christofer: pursue a roll call for Velocity PMC [ Velocity 2024-05-15 ] Status: Sent roll-call email with a deadline set to the 27th of June Got more than enough responses within a few hours ... project claims to be "hyper-stable" and just not needing any work being done on it ... so not worried at all. * Brian: follow up with board about F2F status with Slovakia situation [ Board F2F Agenda Planning 2024-05-15 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:05 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period May 2024 * ISSUES FOR THE BOARD If board members (or anybody else but it is board members that triggered this request) reach out to projects and/or external companies regarding trademark issues I strongly request (I'd say require but I can't require the board to do anything) that they CC trademarks@a.o so that trademarks@a.o can track requests and trends over time as well as ensure consistent messaging. If there is a concern that CC'ing trademarks would be viewed as overly aggressive, then please use BCC. * OPERATIONS Responded to the following queries, liaising with projects as required: - one request to use various project logos on a website - no progress on the draft policy for service naming - redirected a question about using derivations of the ASF logo to the marketing team - provided advice to AGE regarding use of R vs TM - reviewed list of domain names containing ASF marks for possible transfer to the ASF - reviewed text for rbowen's proposed instructional video - approved one external event for DRUID - approved one request to use the AIRFLOW logo within a commercial product - OPENOFFICE approved one request to use project marks within a textbook - PULSAR updated the project website to include a trademark attribution - Directed a request to buy a domain we neither own nor control to whois to correctly identify the owner * REGISTRATIONS The renewal process for the following registrations has completed: - FLEX in the EU - MADLIB in the US and the EU - NUTTX in the US Directed counsel to allow the UK registration for PREDICTIONIO to lapse. Counsel continue to monitor the trademarks that we anticipate will transfer to the ASF when the KIE podling graduates as several are due for renewal soon. Worked with counsel to renew OPENWHISK registrations in class 9. * INFRINGEMENTS Provided advice to FINERACT regarding potential infringements. KAFKA PMC addressed a potential minor infringement. They are also working to resolve a number of additional, unrelated issues. Reviewed EU registration for potential conflict with OPENOFFICE - no concerns at this time. The PULSAR PMC are working to resolve an issue with a commercial product name. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: we have welcomed one new Gold Sponsor. b —Renewals: one Platinum and one Gold Sponsor have confirmed their renewal. c —Payments: 1 —New: we received one new Sponsor payment this month. 2a —Renewing: we received renewal payments from one Platinum and two Gold Sponsors. 2b —Incoming: we await payment from one renewing Platinum, two renewing Gold, and one new Silver Sponsor. 2) Targeted Sponsors: we are working with a current ASF Sponsor regarding a new Targeted opportunity, as well as discussing Targeted Sponsorship options with a PMC who have been approached by a potential donor. 3) Sponsor Relations: we are preparing to kick off a new quarterly call series with Gold and Platinum Sponsors to augment our standing Sponsor outreach. 4) Event Sponsorship: we continue to support Community Over Code sponsorships, and liaise with Conferences, Accounting, and local production teams. 5) Individual Donations and Corporate Giving: we received $1.3K in online donations via https://donate.apache.org/ 6) Administrivia: we continue to work closely with the Treasury and Accounting teams with Sponsor invoicing and payment platform onboarding requirements. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] Foundation Comms * Fielded two incoming inquiries from projects (Apache Answer and Apache DataFusion) for M&P support for a TLP release and Project Spotlight blog * Announced one new TLP - Apache Pekko - via press release and social media promotions * Coordinated with the Apache Causeway PMC to develop and issue an announcement touting the projects two major releases * Continued coordination with ASF officers for FY2024 Annual report * Secured ASF quote in two articles: in Security Blvd[1] and The New Stack[2] on future of open source 25th Anniversary Project * Published a new project spotlight blog feature Apache NuttX * Promoted the ASF’s “Public Good Campaign” garnering 11 new responses to vet for social promotion and website features Branding Project * Developed slides for June board meeting to introduce logo/messaging * Drafted timeline for website redesign and began homepage review * Developed + updated website rebranding dashboard to track all needed updates and corresponding pages 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 Posts In total, 69 posts were published: 44 Tweets + 25 LinkedIn. LinkedIn continues to be the largest source of engagement and garners the greatest reach for social posts. Decline in key metrics can largely be attributed to a decrease in ASF-issued project announcements (TLPs + major releases) from the previous month and an increase in event-related posts as Community Over Code neared. Social Engagement Stats (X + LinkedIn) * Total Audience: 138,048 * New Followers in March: 606 * Total Impressions: 176,590 (16.9% decrease MoM) * Total Engagements: 6,677 (28.1% decrease MoM) * Post Link Clicks: 4,125 (33.6% decrease MoM) Website Analytics * 972,084 visits, 972,033 unique visitors +5.6% * 2 min 42s average visit duration -0.6% * 49% visits have bounced (left the website after one page) +2.1% * 8.8 actions (page views, downloads, outlinks, internal site searches) per visit -17.8% * 10,004 max actions in one visit (level) * 6,824,103 pageviews, 1,190,500 unique pageviews -0.6% * 19 total searches on your website, 14 unique keywords +90.0% * 492,169 downloads, 341,336 unique downloads -0.4% * 1,154,609 outlinks, 279,390 unique outlinks +351.9% [1] https://securityboulevard.com/2024/05/key-areas-where-open-source-security-needs-to-evolve/ [2] https://thenewstack.io/open-source-is-at-a-crossroads/ ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Myrle Krantz] General ======= Infrastructure is operating as expected, and has no current issues requiring escalation to the President or the Board. Short Term Priorities ===================== - Mark Ubuntu 24.04 as production-ready, and being migration of boxes there, particuarly the 18.04 boxes as they are EOL'd - Deploy Kopia broadly, pending showstopper. Long Range Priorities ===================== - Build out the platform for making artifacts available to the public, particularly with eyes on requirements from the CRA. General Activity ================ - Continued work on the asfquart package for the Infra server apps. - Agenda Tool has been ported to asfquart. - Kopia is being rolled out for backups across our boxes. Incremental testing is being performed before complete rollout. Working through some issues, but nothing blocking. - We are continuing some tests for VPN handling across our boxes, particularly as a method to close SSH ports to the general internet, and relying on internal "bastion" servers to SSH to boxes. - Slow work continues on svn's mailer.py to add features necessary for the ASF to roll it out on a new svn server. - We are deprecating our old BuildBot-based Pelican workflow for constructing websites. This has been switched to a new GitHub Action that invokes Pelican to produce the websites. We will roll this out to project websites, and when stable to www.a.o itself. - selfserve.a.o has been converted to the asfquart package. The Agenda Tool and ADP have, too. - Discussion has begun on a new sqlite layer for the asfpy package used by many tools across the ASF. - Working with VP Infra and Board to offer a new "Tooling" department idea, resolution, and further discussion. - Testing and prepation for using Ubuntu 24.04 on our systems. We have some Puppet configs, testing, and verification to do. - Held an Infra Roundtable on Wednesday, June 5th. - Testing the move to Atlassian Cloud products progresses, and we've seen much progress with our user-count issue. - Certificate moves (to mod_md / LetsEncrypt) were put on hold pending the validation of 24.04 for production use. We were moving boxes to 22.04 to switch to mod_md, but now we plan on 24.04 instead. - Infra had several people at CoC EU in Bratislava. Lots of interactions with the community and Foundation officers, along with attending the Board's F2F meeting. - MFA implementation is ongoing. We are basing this on keycloak, and working on integrating/testing it with various systems. The hard problem is defining the best workflow for key recovery. - Infra has begun monitoring the use of GitHub Actions (GHA) in our multitude of projects. As a single organization, we have a *single* quota for usage of GHA. The Tragedy of the Commons affects us, but with our new tools, we've been able to identify projects that have been using a disportionate amount of GHA. We've worked with them on ways to trim their usage, to great success. - The Artifact Distribution Platform has been moving forwards on different ways for communities/PMCs to vote on releases. Several data schemas and supporting concepts are moving forward. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Brian Proffitt] The Community Over Code EU was held with very good success in Bratislava, Slovakia June 3-5. The organizers should be pleased with the outcome of their efforts. Reported numbers: 259 registrations, printed 252 badges, of which 122 were free tickets for speakers, volunteers and organizers. A post-mortem session will be held on June 17 to go over the highlights and problems that may have occurred. CFP for Community Over Code NA 2024 notifications have gone out, and to date only five speakers have responded with a negative. I am working on building the registration site, to launch before the end of June. We are also expecting a bid for av equipment for Denver this week. As referenced in the EVP report, Ruth has submitted RFPs to four potential cities for Community Over Code NA 2025 in hopes of announcing the dates and location during the 2024 Denver event. Community Over Code Asia CFP The results of the CFP have been sent out gradually since May 14th. We first notified the accepted proposals, followed by the rejected proposals, and there were also a small number of proposals (17) still on the waitlist where we have not provided notification yet. As of now, several speakers from outside of China have given up their speaking opportunities due to issues with travel sponsorship. After making substitutions, there are a total of 144 sessions. We have also begun inviting Keynote Speakers, the final invitation list will also take the funding situation into consideration when deciding. CFP for Stands The CFP for Stands has already closed. We received a total of 36 applications, of which 24 were accepted. The majority were Apache projects, as well as the most influential general developer communities or technical media in China, plus open source projects that have deep partnerships with the Apache community. Sponsorship Confirmed - 490,000 CNY, with 7 sponsors We are still waiting for confirmation from other 4 sponsors. Thanks, Willem Jiang On behalf of CoC Asia conference committee ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Previous Events =============== Community Over Code EU 2024 ---------------------------- Bratislava was a great success. Beginning on the Sunday before the event with meeting the Organizers and going through the next days ahead, followed by an evening meal with invited guests, which is always a highlight of the week. Helping the organizers throughout the event looking after speakers and other attendees. Overall they were a great set of people from all backgrounds. Post event surveys are expected to be sent out soon and we look forward to posting stories on the TAC website. Some were also interviewed for Current Events ============== Community Over Code Asia 2024 ---------------------------- Applications closed on the 8th of May. From a total of 20 applications, the judges call on the 19th May narrowed that down and accepted 13 applicants to attend in China. Visa applications are under way and flights etc are to be booked soon. Community Over Code NA 2024 ---------------------------- Applications closed on the 7th June after being extended from an initial 6th May. We ended up with 24 applications. After the judges call Sunday 16th June we have accepted at total of 16 applicants to attend Denver with us. Visa applications have begun. Budget ======= TAC submitted its budget request last month. Monthly Meetings ================ For at least the run up to events, we continue to hold monthly meetings on the second Tuesday. With multiple events to support at the same time and different people running each event we thought a monthly live call would compliment our mailing list and Slack Channels. Any interested members or other Operations folks are welcome to attend these. TAC App ======= TAC App is closed currently Future Events ============= Looking into a few other events as always. With 3 Community Over Code events happening we may not have enough volunteer time to take on anything else concurrent. Short/Medium Term Priorities ============================ Keeping an eye out for other smaller events to support. Mailing List Activity ===================== Not much activity this month Membership ========== No changes to the membership this month. ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [David Nalley] ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] # General There are no issues that need urgent attention. Currently, 50 tracking codes were requested (+1). 10 Matomo sites don't receive traffic at this point (not yet implemented). We signed a DPA with AUTOMATTIC for the WordPress hosting. Multiple questions about embedding resources were handled. # Open tasks - Create a list of WordPress sites - Create a list of domains that are allowed to connect because a DPA is covering it (improved Whimsy support) - Better documentation about DPAs - Add "canned responses" and instructions on how to run the privacy office to the website - Investigate TAC for data privacy and develop a targeted version for the committee - Clarify responsibility for the Matomo VM https://lists.apache.org/thread/6c7dn3ot494pxdlfxfn1pngbcpzj5g08 https://issues.apache.org/jira/browse/INFRA-25432 ----------------------------------------- Attachment 9: Report from the VP of Public Affairs [Dirk-Willem van Gulik] First - was lovely to meet so many people in Bratislava & hear so many well considered, varied and valuable thoughts from people over how we as the ASF need to deal with regulation (or how we should ignore it). Most valuable. 1)CRA and open standards. Good and bad news. The good news is that he joint effort of the open source community at Eclipse (Known as the Open Regulatory Compliance Working Group mailto:open-regulatory-compliance@eclipse.org — fully open) is (finally!) off to a good start. With broad participation. And we saw an EU representative present at the last meeting - with the offer of EU to sort of act as an AMA when needed. The bad news is that despite a lot of push-pull - there is no movement on the CENELEC side. 2) The followup on the 2023 Geneva 'open source congress' is being planned in China, with Open Atom as the local organizer. After consulting with various people - the ASF is going to keep some distance for this year. The main two reasons both relate to trust and control. The first issue here is that when we prepared for the 2023 event, we got the very strong personal assurances from LF their SVP Research that was organising it — that any concerns of this being the start of a congress in the sense of a (chartered) UN style/treaty organisation were unwarranted. And that we should not read anything symbolic into the fact that it was in Geneva. That was laughable even. And we got strong assurances that there would not really be any closing statement or meaningful reports, other than a simple writeup for the participants. We since know that this is not quite how this played out - the report (https://www.linuxfoundation.org/research/2023-open-source-congress - in Chinese and English) was externally focused & exactly positions this event to become eactly such an organisation. Stressing the symbolism of Geneva, etc. etc. The second issue is that the set-up appears to give us both insufficient control over the reporting from the event and insufficient control on who we can have attend this event. Which is important - as, like in Geneva, the majority of those present are not open source organisations. But organisations that want to tell/control what open source should do. So we are going to keep a bit of distance here for now. 3) Of all the big pieces of legislation - the AI act is still not finished/stable. PLD and the others - no changes. 4) With regard to 1025 (the rules for how the industry & open source can (or cannot as it is right now) are required to be involved in industry standards that are being rewritten) — OFE is taking a lead there. But on the ASF side we’re having a lack of Human Resources to follow this. Which is a shame - but not fatal; as OSI and OFE are doing the right things here. I have some leads from Bratislava that I need to follow up on. Finally - much more longer term - I am hoping to start working with Willem Ning Jiang and the Chinese community to see if we can get our community there prepared for much the same conversations that we are now having in Europe and with CISA in the USA. ----------------------------------------- Attachment 10: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 11: 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 slightly up at 21 issues (from 19). We had a tip about potential Infringement of the Apache Free Software License by a company selling medical devices. The person was routed to an appropriate ASF community (httpd) for the next steps. We haven't heard from the httpd PMC on the matter since. U.S. Federal Trade Commission reached out to us regarding an anti-trust investigation. After explaining the basics of how ASF works they proceeded to have a conversation with PMC members of Apache Airflow. After a bit of delay (and frankly prodding) Annual Report FY2024 Legal section was submitted. ----------------------------------------- Attachment 12: Report from the Apache Security Team Project [Mark J. Cox] May: - An older Flink CVE, CVE-2020-17519, has been added to CISA's Known Exploited Vulnerabilities (KEV) catalog. - We continue working with projects to publish 'security model' information on their websites, this month Ignite. - We have cross-referenced our CVEs with the advisories in GitHub's advisory database (used for tools such as dependabot), and added additional metadata in some cases. - Further refined our internal 'reminders, actions and escalations' workflow/guidelines, with the intent to make some of the advanced escalations more formal and public. - Work on OpenSSF Scorecards and Best Practices Badges - Preparations for advisories for remaining Submarine security reports, as this project is moving to the Attic. - Experimented with Guac for giving projects more incentive to produce SBOMs - Provided further feedback on the report for the audit of three Commons components coordinated through OSTIF. - Worked with the Zeppelin project to try and involve more people in their security process, to avoid falling behind again. Stats for May 2024: 25 [license confusion] 11 [support request/question not security notification] 6 [report/question relating to dependencies] Security reports: 51 (last months: 61, 108, 78, 86) 7 ['zeppelin'] 6 ['httpd'] 5 ['tomcat'] 4 ['airflow'] 3 ['activemq', 'hc', 'logging', 'website or other infrastructure'] 2 ['cxf', 'fineract', 'hertzbeat', 'qpid', 'solr'] 1 ['allura', 'ambari', 'commons', 'commons-ostif', 'dubbo', 'eventmesh', 'flink', 'fury', 'maven', 'ofbiz', 'pulsar', 'ranger', 'royale', 'struts', 'superset', 'vince', 'wicket'] In total, as of 1st June 2024, we're tracking 185 (last months: 191, 197) open issues across 67 projects, median age 91 days (last months: 75, 73, 82). 62 of those issues have CVE names assigned. 13 (last month: 12) of these issues, across 8 projects, are older than 365 days. ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: The mission of Apache Airflow is the creation and maintenance of software related to workflow automation and scheduling that can be used to author and manage data pipelines ## Project Status: Current project status: ongoing, high activity Issues for the board: none ## Membership Data: Apache Airflow was founded 2018-12-19 (5 years ago) There are currently 62 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Andrey Anshin on 2024-01-15. - Wei Lee was added as committer on 2024-04-04 ## Project Activity: The Airflow project has kicked off a project to plan and release the next major version, v3.0[1] and is currently having frequent "dev calls" to organize and align the community. Minutes are available in our Confluence Space[2]. Release activity shows our regular cadence of minor and bug fix releases, and regular "provider" packages": Apache Airflow 2.9.2 was released on 2024-06-10. Provider packages 2024-06-07 was released on 2024-06-09. Provider packages 2024-05-30 was released on 2024-06-03. Provider packages 2024-05-26 was released on 2024-05-30. Provider packages 2024-05-12 was released on 2024-05-17. Apache Airflow 2.9.1 was released on 2024-05-06. Provider packages 2024-05-01 was released on 2024-05-06. Apache Airflow Python Client 2.9.0 was released on 2024-05-02. Provider packages 2024-04-16 was released on 2024-04-21. Provider packages 2024-04-13 was released on 2024-04-16. Provider packages 2024-04-10 was released on 2024-04-13. Apache Airflow 2.9.0 was released on 2024-04-08. Provider packages 2024-03-25 was released on 2024-04-03. Apache Airflow 2.8.4 was released on 2024-03-25. Apache Airflow Helm Chart 1.13.1 was released on 2024-03-25. [1]: https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.0 [2]: https://cwiki.apache.org/confluence/x/8ApeEg ## Community Health: Activity on mailing lists and issues is down slightly over the last quarter but there is a lot of engagement in the first two Airflow 3 Dev/planning calls with around 30 participants in each call so far. The second in-person Airflow Summit is happening in San Francisco in September and had 200 submissions from 190 unique speakers and 78 talks accepted/scheduled. There were five talks about Apache Airflow in to CoC EU summit (3 in the Data Engineering track, 2 elsewhere), and only one was given by a PMC member. ----------------------------------------- Attachment B: Report from the Apache Allura Project [David Philip Brondsema] ## Description: The mission of Apache Allura is the creation and maintenance of software related to a software development infrastructure platform commonly known as a "forge" ## Project Status: Current project status: Ongoing (moderate activity) Issues for the board: none ## Membership Data: Apache Allura was founded 2014-03-18 (10 years ago) There are currently 17 committers and 17 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Guillermo Cruz on 2021-11-09. - No new committers. Last addition was Guillermo Cruz on 2021-11-09. ## Project Activity: - a security issue reported and fixed - release 1.17.0 published - OAuth2 supported added, primarily by a new contributor - a few small email exchanges with new people ## Community Health: - Last release was 1.17.0 on 2024-06-10 - Good to see some new contributions and interest - Besides that, general maintenance and support continues ----------------------------------------- Attachment C: Report from the Apache Aries Project [Christian Schneider] ----------------------------------------- Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj] ## Description: The mission of Apache Atlas is the creation and maintenance of software related to a scalable and extensible set of core foundational governance services - enabling enterprises to effectively and efficiently meet their compliance requirements ## Project Status: Current project status: Ongoing, with low activity Issues for the board: there are no issues requiring board attention ## Membership Data: Apache Atlas was founded 2017-06-20 (7 years ago) There are currently 48 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16. - No new committers. Last addition was Umesh Padashetty on 2023-06-14. ## Project Activity: - improvements in Export/Import functionality - updates to support ignore patterns in all Atlas hooks - added support for Chinese characters in Atlas entity attributes - Docker setup update to address HBase failures - updated versions of dependent libraries JanusGraph and Tinkerpop ## Community Health: - dev@atlas.apache.org had a 166% increase in traffic in the past quarter (312 emails compared to 117) - 23 commits in the past quarter (64% increase) - 7 code contributors in the past quarter (40% increase) - 4 PRs opened on GitHub, past quarter (100% increase) - 2 PRs closed on GitHub, past quarter (100% increase) ## Recent releases: - Apache Atlas 2.3.0 was released on 2022-12-06 - Apache Atlas 2.2.0 was released on 2021-08-17 - Apache Atlas 2.1.0 was released on 2020-07-15 ----------------------------------------- Attachment E: Report from the Apache Attic Project [Herve Boutemy] ----------------------------------------- Attachment F: Report from the Apache Axis Project [Robert Lazarski] # Apache Axis Board Report ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues There are no issues requiring board attention at this time. ## Membership Data: Axis was created on 2001-01-19 (23 years ago). It is listed as established in 2009-12 but really the first Apache commit was in 2001. There are currently 63 committers and 62 PMC members in this project, a vote in 2010 made all committers automatically PMC members. One PMC member resigned. Community changes, past quarter: - Currently 62 PMC/ 63 Committers members. - No new committers were added in the last 90 days, last committer added was Bill Blough on December 7th 2017 who also was added to the PMC on May 9th 2018. ## Project Activity: Recent releases: - Axis 2/Java 1.8.2 was released on July 14, 2022. - Axis 2/Rampart 1.7.1 was released on July 30, 2017. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Project state: Ongoing, with moderate activity ## Health report: Development for the upcoming Axis2 1.8.3 release finally has completed in our long transition to jakarta and also from httpclient4 to httpclient5 - the latter took months longer than expected as Axis2 uses the httpclient5 API for functionality and testing that goes deep into their architecture. We still have an outstanding OSGI issue that currently is triaged out of the next Axis2 release because we lack volunteers who use it, while being difficult to support. The next preliminary step for an Axis2 release is an Apache Axiom release from the Apache Web Services project, in which several Axis committers are also committers in that project. A large amount of work in Axiom to support the Axis2 move to jakarta recently completed. A major refactoring has also completed of our sub project Apache Rampart - an implementation of WS-Security standards - that was required from commits upgrading OpenSAML from 2.x to 4.3.0, and Apache WS-WSS4J from 1.6 to 3.0.0. Rampart currently has no active committers that uses it in their own projects. However, we did receive a very significant set of pull requests from a contributor, See RAMPART-449. The schedule for this upcoming quarter is: Rampart release off of Axis2 1.8.2--> Axiom release --> Axis2 1.8.3 --> Rampart release off of Axis2 1.8.3. We continue to lack committer growth. We had a big contribution to Axis2 this past quarter - see https://github.com/apache/axis-axis2-java-core/pull/589 . Rampart as mentioned in RAMPART-449 received help but that individual turned down a committer role. Another individual reached out to help Axis2 this past quarter, but never responded after given the 'new committer' link. Our continued progress to make Axis2 a contemporary and relevant JSON engine as demanded by our day jobs - some of us moved off of SOAP years ago - is the best chance Axis has for committer growth going forward. Axis2 C PMC member Bill Blough continues to help users on the mailing list and he also participates in release votes. ## Axis2 java Jira issues opened in the last 90 days: 3 ## Axis2 java Jira issues closed in the last 90 days: 1 ----------------------------------------- Attachment G: Report from the Apache Beam Project [Kenneth Knowles] ## Description: The mission of Apache Beam is the creation and maintenance of software related to a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. ## Project Status: Current project status: Ongoing Issues for the board: none. ## Membership Data: Apache Beam was founded 2016-12-20 (7 years ago) There are currently 95 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 3:1. Community changes, past quarter: - No new PMC members. Last addition was Alex Van Boxel on 2023-10-01. - No new committers. Last addition was Svetak Sundhar on 2024-02-09. ## Project Activity: Recent releases: - 2.56.0 was released on 2024-05-02. - 2.55.1 was released on 2024-04-08. Notably, Beam's first point release! Our release automation has gotten much better so this was finally worthwhile to do. - 2.55.0 was released on 2024-03-25. Technical development notes: - Added a new API for "Managed" transforms that represents an innovative direction for Beam: these transforms are explicitly constructed from a machine-readable config rather than just code, with the intention that OSS runners and/or Cloud providers can use the config to manage them more effectively. Up to this point, with a few exceptions, Beam transforms have been "guest" code managed by the user, with runners treating them as black boxes. With this API, we hope to enable even smoother user experience than Beam's portability APIs enabled, for example transparently applying upgrades to address CVEs, etc. - New Ordered Processing PTransform added for encapsulating a common pattern for processing order-sensitive stateful data. - Added bad record handling for BigQueryIO and PubsubIO connectors. - Added Vertex AI Feature Store handler for the Enrichment transform (a best-effort pseudo-join for when just grabbing data from an auxiliary store is good enough). Dependency/related project updates: - Arrow version was bumped to 15.0.0 from 5.0.0 (a breaking change that we determined was justified) - Go SDK base container image moved to distroless/base-nossl-debian12, reducing vulnerable container surface to kernel and glibc (also potentially breaking change per Hyrum's Pitfall [1] since container surface reduced) - First release with Flink 1.17 support. - Added Flink 1.18 support [1] https://www.hyrumslaw.com/ ## Community Health: Community health is steady. Traffic on dev@ list has settled in to a new activity level that isn't changing too much. The same is true for code contributions, bug reports, and code review. ----------------------------------------- Attachment H: Report from the Apache Bigtop Project [Masatake Iwasaki] ----------------------------------------- Attachment I: Report from the Apache Bloodhound Project [Gary Martin] Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== The PMC has been discussing whether it is time to retire the project to the attic. This is further discussed in the Community & Development section below. Releases ======== There have been no releases since the last report. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Community & Development ======================= The PMC has been prompted to discuss moving Apache Bloodhound to the Attic. A number of the PMC members are supporting this move, pointing out that energy levels have remained stubbornly low. At this point there is more support for retirement. The chair has held off from casting a vote on the proposal if it was deemed appropriate to try again to get the attention of the dev list and get new people involved. The activity generated by the previous call was not sustained and so it would not be surprising if this happened again. Further input from the board on these issues will be welcomed. ----------------------------------------- Attachment J: Report from the Apache BVal Project [Matthew Jason Benson] ----------------------------------------- Attachment K: Report from the Apache Camel Project [Andrea Cosentino] ## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Project Status: Current project status: Ongoing with high activity Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (15 years ago) There are currently 93 committers and 47 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Colm O hEigeartaigh was added to the PMC on 2024-03-11 - Marat Gubaidullin was added to the PMC on 2024-03-11 - Gaelle Fournier was added as committer on 2024-03-06 - Ivan Kulaga was added as committer on 2024-03-12 ## Project Activity: Apache Camel: - We released Camel 3.22.2 - We released Camel 4.0.5 - We released Camel 4.4.1 - We released Camel 4.4.2 - We released Camel 4.5.0 - We released Camel 4.6.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - The 4.4.x release is our LTS release train and we are already release two patch releases 4.4.1 and 4.4.2 - We are working torward our next LTS release 4.8.0, we released two development releases 4.5.0 and 4.6.0 - We continued the release train for 3.22.x LTS - The 3.22.x release train is the LTS for 3.x - The situation is really healthy and the community is super. We are introducing many new features and working on engaging the community more. Apache Camel K: - For Camel K we released a 2.3.0, 2.3.1 and 2.3.2 (on vote) with a lot of good stuff. - For Camel-K-runtime we released 3.8.0, for 2.3.x work. - Camel K is in good shape and the community is expading with new contributors and many new good idea. Apache Camel Kamelets: - We released Camel Kamelets 4.4.1 - We released Camel Kamelets 4.4.2 - We released Camel Kamelets 4.5.0 - We released Camel Kamelets 4.6.0 - The 4.4.x release train is matching the LTS release from Camel core and it's an important building block for starting with routes - We introduced a lot of new Kamelets and we are improving the documentation by focusing on much more examples Apache Camel Quarkus: - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 3.8.1 - We released Camel-quarkus 3.8.2 - We released Camel-quarkus 3.9.0 - We released Camel-quarkus 3.10.0 - We released Camel-quarkus 3.11.0 - The 3.8.x release train is matching the 4.4.x release from Camel core and it will be an LTS - A lot of work has been done on testing side and we are working on supporting more extensions for vector databases and AI Apache Camel-Karavan: - Camel-Karavan is improving and the community around the project is increasing in number of features and new issues reporting - We released the 4.4.0 - We released the 4.4.1 - We released the 4.5.0 - We released the 4.6.0 - We released also the 4.4.x patch releases matching the LTS version from Camel core Camel-Kafka-Connector: - We plan to release a 4.4.2 to match the LTS release from camel core, the release process is on-going - The community is active and we receive a lot of feedback and requests Apache Camel-Karaf: - Camel-karaf main branch has been updated andnow works with Camel 4.6.0 and Karaf 4.4.6+.We are working on new good features, heading to the first camel-karaf 4.x release. Many new contributors are helping on this. Overall: - The Camel project and all the subprojects are in a really good shape and all of them are growing in terms of community involvement and contributions. ## Community Health: - 339 issues opened on GitHub, past quarter (11% increase) and 339 issues closed on GitHub, past quarter (12% increase): Some of the subproject are using github issues, but Camel core is still on JIRA. We are seeing increase in Camel K and Camel Quarkus. - 4248 commits in the past quarter (17% decrease) and 115 code contributors in the past quarter (10% increase): We are consolidating the codebase and that explains the decrease in commits and we are seeing increase in terms of contributors - 1706 PRs opened on GitHub, past quarter (5% decrease) and 1699 PRs closed on GitHub, past quarter (6% decrease): Here we are more or less in line with the last quarter. The situation is really good and we are observing more engagement in open PRs. - dev@camel.apache.org had a 10% increase in traffic in the past quarter (363 emails compared to 328): The discussion are moving much more on Zulip but still there was an increase. - issues@camel.apache.org had a 10% increase in traffic in the past quarter (2122 emails compared to 1915): We are opening more new issues related to possible improvements and developments - users@camel.apache.org had a 17% increase in traffic in the past quarter (218 emails compared to 185): Users are starting to move and ask questions on Zulip, like the discussion for development, but we have some more discussions related to Karaf and to release scheduling. - Jira Activity: 133 issues opened in JIRA, past quarter (-60% change) and 164 issues closed in JIRA, past quarter (-46% change). Those numbers seems innacurate, but only Camel and Camel-Spring-Boot are still using JIRA instead of gh issues, so it is somewhat justified. ----------------------------------------- Attachment L: Report from the Apache Cayenne Project [Michael Ray Gentry] # Apache Cayenne Board Report, June 2024 ## Description Apache Cayenne is a Java database persistence framework. It takes a distinct approach to object graph persistence and provides an ORM runtime, remote persistence services, and a cross-platform GUI database mapping/modeling/development tool. ## Project Status ### Project State Ongoing ### Issues for Board None ## Membership Data Apache Cayenne was founded 2006-12-19 (17 years ago). There are currently 23 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Nikita Timofeev on 2017-06-25. - No new committers. Last addition was Arseni Bulatski on 2018-12-10. There was recent discussion (on the private mailing list) about adding a new committer who has been active finding bugs and submitting patches. We will make an invitation soon to become an official committer. ## Project Activity After the release of 4.2, most development has shifted to 5.0 (unreleased). Prior versions are maintenance-only. - Cayenne 4.0.x (stable) - Maintenance only. - Cayenne 4.1.x (stable) - Maintenance only. - Cayenne 4.2.x (stable) - Maintenance only. - Cayenne 5.0 (unreleased) - Features are being defined and development has started. Cayenne 4.2.1 is being prepared for a maintenance release. A regression was found which halted the release vote, but it should be released soon. ### Releases - Cayenne 4.0.3 on 2023-03-02. - Cayenne 4.1.1 on 2021-12-24. - Cayenne 4.2 on 2023-05-25. ## Community Health Cayenne is healthy, but the past quarter has generally been slower than before. After the 4.2.1 maintenance release, 5.0 will get more attention. ----------------------------------------- Attachment M: Report from the Apache Celeborn Project [Keyong Zhou] ## Description: The mission of Apache Celeborn is the creation and maintenance of software related to an intermediate data service for big data computing engines to boost performance, stability, and flexibility ## Project Status: Current project status: New Issues for the board: None ## Membership Data: Apache Celeborn was founded 2024-03-20 (3 months ago) There are currently 21 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - Chandni Singh was added as committer on 2024-03-21 - Mridul Muralidharan was added as committer on 2024-04-29 ## Project Activity: Software development activity: - We released 0.4.1 on May 28th. - We are in the process of releasing 0.5.0. - Memory file storage is merged to main. - An optimized AQE support is under review. Meetups and Conferences: - A talk was given in Apache Local Conference Hangzhou on May 28th. Recent releases: - 0.4.1 was released on May 22th, 2024. - 0.4.0-incubating was released on February 6th, 2024. ## Community Health: Overall community health is good. In the past quarter, user mail list had a 450% increase in traffic, dev mail list had a 6% decrease in traffic, the PMCs treat it as normal fluctuation. We have been performing extensive outreach for our users, and encouraging them to contribute back to the project. Also, we are active in making a voice in various conferences to attract more users. ----------------------------------------- Attachment N: Report from the Apache CloudStack Project [Daniel Augusto Veronezi Salvador] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage, and networking devices. ## Project Status: Current project status: Ongoing, with high activity. Issues for the board: None. ## Membership Data: Apache CloudStack was founded on 2013-03-20 (11 years ago) There are currently 138 committers and 56 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - Slavka Peleva was added to the PMC on 2024-04-08 - Kiran Chavala was added as committer on 2024-04-09 - Rene Peinthor was added as committer on 2024-04-05 ## Project Activity: Software development/management activity: - The current version of Apache CloudStack is 4.19.0.1; - The community is planning to release Apache CloudStack 4.20.0.0 in August. - The schedule changed from the last report because the community is also working towards releasing an update for 4.19 at the end of June, which affects the 4.20 schedule. - The version 4.18.2.0 was released on April 25, 2024. - We released two security patches (4.18.1.1 and 4.19.0.1) to solvce 3 vulnerabilities. - A new version (v2.16.1) of the Go SDK for CloudStack was released on May 20, 2024. - The CloudStack Kubernetes provider does not have a new version since 2021. However, the community is planning to release version 1.1.0 later this month. - A new version (v0.5.0) of the Go SDK for CloudStack was released on April 9, 2024. - A new version (v6.4.0) of the CloudStack CLI was released on March 21, 2024. Meetups and Conferences: - Some PMC members, committers, and contributors attended and presented talks at CloudStack's track on the Community Over Code EU 2024. - Although we missed the call for tracks for Community Over Code NA 2024, which finished in December 2023, we engaged with the conference planners and joined the track "Cloud and runtime". Then, the track was renamed to "CloudStack, cloud, and runtime" due to the expressivity of the CloudStack community on the submitted talks. There are 7 talks related to CloudStack approved for the Community Over Code NA 2024. - CloudStack European User Group is scheduled for September 12, 2024, in Frankfurt, Germany: https://cloudstack.apache.org/blog/cseug-2024/ - CloudStack Collaboration Conference 2024 is planned for November 20-22, 2024, in Madrid, Spain: https://www.cloudstackcollab.org/. Call for presentation is open: https://docs.google.com /forms/d/e/1FAIpQLSdzhEy-v68wyVQcBY3AnQT7OeDVs4xnfvlt3wIlLxV50dP11w/viewform ## Community Health: Statistics: - According to the reporter tool, the Community Health Score (Chi) is 10.00 (Super Healthy). Following are the past quarter's statistics: - dev@cloudstack.apache.org had a 25% decrease in traffic in the past quarter (628 emails compared to 828) - issues@cloudstack.apache.org had a 43% decrease in traffic in the past quarter (92 emails compared to 159) - marketing@cloudstack.apache.org had a 24% decrease in traffic in the past quarter (13 emails compared to 17) - users@cloudstack.apache.org had a 6% decrease in traffic in the past quarter (994 emails compared to 1057) - 419 commits in the past quarter (-44% change) - 40 code contributors in the past quarter (-9% change) - 315 PRs opened on GitHub, past quarter (-6% change) - 234 PRs closed on GitHub, past quarter (-20% change) - 165 issues opened on GitHub, past quarter (-24% change) - 183 issues closed on GitHub, past quarter (28% increase) Although we see a general decrease in the interactions in the past quarter, there are no current concerns regarding that, as some quarters are busier than others. Also, we expect that some interactions decrease while the project matures. - There are new PMC members and committers added since the previous report. - The community is discussing improving its policies regarding cadence of releases, policies for introducing disruptive features, and removing deprecated methods, technologies, and designs. The discussion is being held on GitHub: https://github.com/apache/cloudstack/discussions/8970 (the messages are also sent by email by GitHub Discussion). ----------------------------------------- Attachment O: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The mission of Apache Commons is the creation and maintenance of Java focused reusable libraries and components ## Project Status: Current project status: Ongoing with moderate activity. Issues for the board: none. ## Membership Data: Apache Commons was founded 2007-06-19 (17 years ago) There are currently 149 committers and 44 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - Claude Warren was added to the PMC on 2024-03-22 - No new committers. Last addition was Claude Warren on 2022-02-01. ## Project Activity: Many releases of our components: CONFIGURATION-2.11.0 was released on 2024-06-10. NET-3.11.1 was released on 2024-06-10. PARENT-71 was released on 2024-06-10. JEXL-3.4.0 was released on 2024-06-06. NET-3.11.0 was released on 2024-05-31. VALIDATOR-1.9.0 was released on 2024-05-28. JCS-3.2.1 was released on 2024-05-27. DAEMON-1.4.0 was released on 2024-05-24. CLI-1.8.0 was released on 2024-05-23. COMPRESS-1.26.2 was released on 2024-05-23. LOGGING-1.3.2 was released on 2024-05-15. PARENT-70 was released on 2024-05-15. CSV-1.11.0 was released on 2024-05-02. RELEASE-PLUGIN-1.8.2 was released on 2024-04-19. CLI-1.7.0 was released on 2024-04-18. IMAGING-1.0.0-alpha5 was released on 2024-04-18. TEXT-1.12.0 was released on 2024-04-16. BUILD-PLUGIN-1.14.0 was released on 2024-04-15. IO-2.16.1 was released on 2024-04-08. COLLECTIONS-4.5.0-M1 was released on 2024-04-02. IMAGING-1.0.0-alpha4 was released on 2024-04-02. PARENT-69 was released on 2024-04-01. IO-2.16.0 was released on 2024-03-28. LOGGING-1.3.1 was released on 2024-03-24. PARENT-68 was released on 2024-03-23. CONFIGURATION-2.10.1 was released on 2024-03-20. CONFIGURATION-2.10.0 was released on 2024-03-13. ## Community Health: We welcomed Claude Warren as our latest PMC member. Mailing list activity has increased mostly due to GitHub automated emails. Most if not all of our growth in contributions are coming in through GitHub pull requests. GitHub PRs with our use of GitHub continuous integration builds provide validation of PRs and the existing code base. The flip side is that the increase in GitHub usage is matched by a decrease in Jira usage. ----------------------------------------- Attachment P: Report from the Apache Cordova Project [Bryan Ellis] ## Status report for the Apache Cordova project - June 2024 ## Description A platform for building native mobile applications using HTML, CSS and JavaScript. ## Project Status **Current project status:** Our current work continues on staying updated with changes to iOS and Android, our most utilized platforms, alongside ensuring regular updates to plugins. Our status dashboard at http://status.cordova.io remains mostly all green and our nightly builds are still extremely stable. Committers made a major release to update the cordova-android platform to update dependencies. cordova-ios minor and cordova-plugin-file releases were published to comply with Apple's new privacy requirements. Niklas Merz, one of our PMC members gave a talk at Community Over Code EU 2024 (June 2024 Bratislava, Slovakia) about maintainer personas and our community survey. The talk discussed some ideas and results of the survey and hopefully inspires other projects to have a look at their community. **Issues for the board:** There are no issues requiring board attention at this time. ## Membership Data There are currently 99 committers and 96 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. **Community changes, past quarter:** - No new PMC members. Last addition was Pieter Van Poyer on 2021-04-06. - No new committers. Last addition was Pieter Van Poyer on 2021-04-06. ## Project Activity Our project made releases this quarter for our core platforms to keep up with current requirements. **Releases:** - cordova-plugin-file@8.1.0 was released on 2024-06-05. - cordova-android@13.0.0 was released on 2024-05-23. - cordova-ios@7.1.0 was released on 2024-04-03. - cordova-eslint@5.1.0 was released on 2024-03-27. ## Community Health ASF Project Statistics gives the project a Community Health Score (Chi): 4.70 (Healthy) We continue to see contributions from a small group of dedicated individuals. Things remain stable and the project continues to see good traffic. Github discussions have become how our community supports each other. Our discussion area is live at https://github.com/apache/cordova/discussions and activity is forwarded to the 'issues' list. ## Mailing List Activity - dev@cordova.apache.org had a 211% increase in traffic in the past quarter (56 emails compared to 18) - issues@cordova.apache.org had a 67% increase in traffic in the past quarter (895 emails compared to 533) ## Github Activity **Issues:** Issue close rate of 94% - 54 issues opened on GitHub, past quarter (8% increase) - 51 issues closed on GitHub, past quarter (6% increase) **PRs:** PR close rate of 112% - 97 PRs opened on GitHub, past quarter (185% increase) - 109 PRs closed on GitHub, past quarter (172% increase) **Commits:** - 103 commits in the past quarter (145% increase) - 9 code contributors in the past quarter (12% increase) ----------------------------------------- Attachment Q: Report from the Apache cTAKES Project [Pei Chen] ## Description: The mission of cTAKES is the creation and maintenance of software related to Natural language processing (NLP) tool for information extraction from electronic medical record clinical free-text ## Project Status: Current project status: Ongoing with moderate/low activity. Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache cTAKES was founded 2013-03-19 (11 years ago) There are currently 40 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Gandhi Rajan on 2018-07-12. - No new committers. Last addition was Dennis Johns on 2023-01-06. ## Project Activity: - Committee continues to work on the future release (6.x.x) - 5.1.0 was released on May 10 2024 - 4.0.0.1 was released on Jan 20 2021 - 4.0.0 was released on Apr 27 2017 - 3.2.2 was released on May 30 2015 ## Community Health: dev@ctakes.apache.org had a 77% increase in traffic in the past quarter (55 emails compared to 31) most related to the new 5.1.0 release. ----------------------------------------- Attachment R: Report from the Apache Curator Project [Enrico Olivelli] ## Description: The mission of Curator is the creation and maintenance of software related to Java libraries that make using Apache ZooKeeper easier ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Curator was founded 2013-09-18 (11 years ago) There are currently 16 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Kezhu Wang on 2023-03-25. - No new committers. Last addition was Kezhu Wang on 2023-03-24. ## Project Activity: This week we are cutting a release (5.7.0), following the usual steady pace of the community. 5.6.0 was released on 2024-01-08. 5.5.0 was released on 2023-04-28. 5.4.0 was released on 2022-10-28. ## Community Health: There is not much traffic on the mailing list but we are receiving feedback from users (bug reports) and fixing the problems. Unfortunately we don't have any good candidates as new committers, almost all of the contributions this quarter came from existing committers. Some stats: - dev@curator.apache.org had a 32% increase in traffic in the past quarter (57 emails compared to 43) - user@curator.apache.org had a 85% decrease in traffic in the past quarter (2 emails compared to 13) - 4 code contributors in the past quarter (33% increase) - 5 PRs opened on GitHub, past quarter (no change) - 7 PRs closed on GitHub, past quarter (75% increase) ----------------------------------------- Attachment S: Report from the Apache Daffodil Project [Mike Beckerle] ## Description: The mission of Apache Daffodil is the creation and maintenance of software related to an implementation of the Data Format Description Language (DFDL) used to convert between fixed format data and more readily processed forms such as XML or JSON ## Project Status: Current project status: The project is healthy based on ongoing activity and releases. The DFDL Standard is now ISO/IEC 23415, and is available from ISO and national-standards web-sites worldwide. It also remains an open-standard available from its existing source at the Open Grid Forum. Daffodil 3.7.0 was released on 2024-04-10. Daffodil 3.8.0 is underway and will be released in 3Q2024. The next release of Daffodil (3.8.0) is in RC1 voting state. The next release of the VSCode extension for Daffodil, which will be v1.4.0 is in discussion for release. Issues for the board: none. ## Membership Data: Apache Daffodil was founded 2021-02-16 (3 years ago) There are currently 20 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - Peter Katlic was added to the PMC on 2024-03-17 - Peter Katlic was added as committer on 2024-03-17 John Interrante is retiring from his job at GE, and we congratulate him on his lifetime achievement. We expect him to be less active on Daffodil going forward, but he will remain a PMC member on the project and we hope to continue to receive his valued guidance. ## Project Activity: Collaboration on the Drill connector to Daffodil has resumed and is close to an initial release. The features in Daffodil 3.7.0 appear to enable the completion of this work. The level of activity on the project as a whole is robust. ## Community Health: Activity level is acceptable and our metrics reflect that with recent increases in email and commit frequency. ----------------------------------------- Attachment T: Report from the Apache DataFusion Project [Andrew Lamb] ## Description: The mission of Apache DataFusion is the creation and maintenance of software related to an extensible query engine ## Project Status: Current project status: New + Ongoing (high activity) Issues for the board: None ## Membership Data: Apache DataFusion was founded 2024-04-16 (2 months ago) There are currently 32 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Ruihang Xia was added to the PMC on 2024-06-13 - Mehmet Ozan Kabak was added to the PMC on 2024-06-13 - Mustafa Akur was added to the PMC on 2024-05-09 - Oleks V. was added to the PMC on 2024-05-09 ## Project Activity: The project continues to be quite active with many PRs and issues opened and closed per day. We have mostly completed tasks related to becoming a new top level project including an ASF press release[0] the new top level project and document ing more thoroughly the process of inviting new committers and PMC members[1]. We also began discussing adopting the sql parser into the DataFusion ASF governance process[2]. There are also several regional meetups planned: in San Francisco in June and in China in July. [0]: https://news.apache.org/foundation/entry/ apache-software-foundation-announces-new-top-level-project-apache-datafusion [1]: https://github.com/apache/datafusion/pull/10778 [2]: https://github.com/sqlparser-rs/sqlparser-rs/issues/1294 ### DataFusion core https://github.com/apache/datafusion We made our first successful release as a new project, version 38.0.0 In addition to the work related to moving to a top-level project, the community continues to work on making logical planning faster, making function packages (i.e. UDFs) modular and easier to mix/match, and “de-parsing” logical plan expressions back to SQL, and improve type coercion. Recently there has been renewed interest in reading parquet files and creating secondary indexes. ### Sub project: DataFusion Python https://github.com/apache/datafusion-python The DataFusion Python subproject has become more active since the last board report with contributions from several contributors. Version 37 was released, and version 38 is in the process of being released ### Sub project: DataFusion Comet https://github.com/apache/datafusion-comet The Comet subproject has had face to face sync meetings which are recorded[1]. [1] https://lists.apache.org/thread/9kqxkpwxf4oxonfboyfh8j6ko7r3fb3z The Comet subproject is very active and is receiving significant contributions from new contributors. There is some initial documentation published at https://datafusion.apache.org/comet/. ### Sub project: DataFusion Ballista https://github.com/apache/datafusion-ballista https://github.com/apache/datafusion-ballista-python The Ballista subproject is not currently actively maintained. ### Recent Releases * PYTHON-38.0.1 was released on 2024-05-30. * PYTHON-37.1.0 was released on 2024-05-13. * 38.0.0 was released on 2024-05-10. ## Community Health: We have added several new committers and PMC members (see above) in the last month, and we expect to continue to do so regularly. While it would always be nice to have more bandwidth to devote to PMC activities, we are currently doing well. While most communications still happen through github, the mailing lists are now fully active, as reflected in their metrics: * dev@datafusion.apache.org had a big increase in traffic in the past quarter (71 emails compared to 0) * github@datafusion.apache.org had a big increase in traffic in the past quarter (7685 emails compared to 0) ----------------------------------------- Attachment U: Report from the Apache ECharts Project [Wenli Zhang] ## Description: The mission of Apache ECharts is the creation and maintenance of software related to a charting and data visualization library written in JavaScript ## Project Status: Current project status: Ongoing: We are currently focusing on the development of the next major release, Apache ECharts 6.0. Consequently, updates to the 5.x version will primarily consist of bug fixes. Issues for the board: NA ## Membership Data: Apache ECharts was founded 2020-12-16 (3 years ago) There are currently 29 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was He Hao on 2022-07-06. - No new committers. Last addition was Linghao Su on 2023-08-01. ## Project Activity: We are currently focusing on the development of the next major release, Apache ECharts 6.0, which is expected to be available early next year. Key features of this release include: - A new matrix layout that can be utilized with various chart types such as scatter plots, heatmaps, graphs, and more. - Axis breaks, which allow for the representation of discontinuities in axes. - Enhanced candlestick series, designed to improve usability in real-world stock market scenarios. - Violin plots, to better illustrate data distribution. - Scatter plot jittering, which helps depict data density and prevent overlap. - And additional features. By the end of this month, we plan to release a candidate for the next minor update, version 5.5.1, which will primarily address bug fixes and introduce a few new features. ## Community Health: The decline in commit activity can be attributed to our primary focus on the upcoming major release. Consequently, pull requests are not being merged into the master branch as frequently, and the larger size of these PRs means they require more time for both submission and review. Additionally, we should be aware of the declining number of contributors and take proactive measures to address this. Many of our existing committers have new priorities in their lives, resulting in reduced contribution time. Furthermore, we are experiencing a shortage of new, continuous contributions that could lead to new committers. It is crucial that we concentrate on reviewing current PRs and providing feedback more consistently to encourage community participation. While the number of releases on npm is increasing, the decline in email activity and the number of open issues on GitHub should not cause much concern. This trend may indicate that the software is becoming more stable. Therefore, we should aim to introduce exciting new features and enhancements in the next major release to generate enthusiasm within the community. By doing so, we can reinvigorate interest and engagement among our contributors and users. ----------------------------------------- Attachment V: Report from the Apache Felix Project [Karl Pauls] ## Description: Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. ## Project Status: Current project status: Ongoing, with low activity. Issues for the board: none. ## Membership Data: Apache Felix was founded 2007-03-28 (17 years ago) There are currently 67 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Georg Henzler on 2019-06-10. - No new committers. Last addition was Robert Munteanu on 2020-07-20. ## Project Activity: - Existing implementations have been improved/enhanced based on community feedback. - Released 10 components. Mostly bug fixes/minor improvements related to jetty updates. ### Releases - org.apache.felix.http.jetty-5.1.16 was released on 2024-06-10. - org.apache.felix.http.jetty12-1.0.8 was released on 2024-06-10. - org.apache.felix.http.jetty-5.1.14 was released on 2024-05-27. - org.apache.felix.http.jetty12-1.0.6 was released on 2024-05-27. - org.apache.felix.http.base-5.1.8 was released on 2024-05-05. - org.apache.felix.http.bridge-5.1.8 was released on 2024-05-05. - org.apache.felix.http.jetty-5.1.12 was released on 2024-05-05. - org.apache.felix.http.jetty12-1.0.4 was released on 2024-05-05. - org.apache.felix.webconsole-4.9.8 was released on 2024-04-14. - org.apache.felix.webconsole-5.0.2 was released on 2024-04-14. ## Community Health: - Overall the project is in ok health with little ongoing activity. - There is a decline in community activity and in general, we don't see a lot of new development right now. We are at the lookout for new topics and contributors. - Questions on the user list are answered, development concerns are either discussed on the mailing list or directly in the JIRA issues. - We had no issues voting on releases and JIRA issues are generally addressed. ----------------------------------------- Attachment W: Report from the Apache Flex Project [Harbs] ## Description: The mission of the Apache Flex project is to create and maintain software related to the development of expressive web applications that deploy to all major browsers, desktops and devices (including smartphones, tablets and tv) ## Project Status: Current project status: Project is stable Issues for the board: None ## Membership Data: Apache Flex was founded 2012-12-19 (11 years ago) There are currently 67 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Greg Dove on 2023-03-03. - No new committers. Last addition was Greg Dove on 2016-09-07. ## Project Activity: There was an issue with spam going undetected to the commits list. Apparently noone on the PMC was subscribed to that list and spam protection was not turned on. Infra turned on spam protection and at least one PMC member is now subscribed to that list. ## Community Health: Email activity has been very light. There has been little change for a long time. ----------------------------------------- Attachment X: Report from the Apache Flink Project [Robert Metzger] ## Description: The mission of Flink is the creation and maintenance of software related to platform for scalable batch and stream data processing ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Flink was founded 2014-12-17 (9 years ago) There are currently 112 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Jing Ge was added to the PMC on 2024-04-12 - Lincoln Lee was added to the PMC on 2024-04-12 - Alexander Fedulov was added as committer on 2024-04-18 - Zakelly Lan was added as committer on 2024-04-26 - Weijie Guo was added to the PMC on 2024-06-04 - Rui Fan was added to the PMC on 2024-06-04 ## Project Activity: Recent Releases: * cdc-3.1.0 was released on 2024-05-17. * kubernetes-operator-1.8.0 was released on 2024-03-21. * 1.19.0 was released on 2024-03-18. The Flink CDC connectors have been successfully donated from Ververica to the ASF, with the sub-project successfully creating its first release (3.1.0). Flink 1.19 has been released -- with major improvements across the board, in particular Flink SQL. ## Community Health: The Flink community is healthy and active. The dev@ list keeps increasing in activity (with increases of 14% in the December 23 report, 6% in the March report and now a 22% increase). However, there are a few messages on dev@ which remain unanswered. The user@ list had a 58% increase (last report it was down 37%) -- we hope that the list activity stays at the higher level going forward. Code-related metrics are pointing downwards this quarter (JIRA issues, commits, contributors, PRs) .. but we anticipate the number to go up again closer to the 1.20 release feature freeze. We have some delays in releasing new Flink connector versions due to the lack of PMC votes. ----------------------------------------- Attachment Y: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: The mission of Gora is the creation and maintenance of software related to ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop ## Project Status: Current project status: Ongoing project with low activity Issues for the board: None ## Membership Data: Apache Gora was founded 2012-01-24 (12 years ago) There are currently 31 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Lahiru Jayasekara on 2020-04-30. - No new committers. Last addition was Lahiru Jayasekara on 2020-04-27. ## Project Activity: - Several PMC members volunteered in mentoring GSoC for this year, we were granted a single slot for this year's GSoC programme. - There were discussions around rolling out the next release. - Except for work carried out related to GSoC project past quarters, we have not been able to make significant progress on our next major release, 0.9 was released on 2019-08-15 and it has been quite a while since the last release. ## Community Health: - While we observed the usual low activity level on Github and there were some level of increase in mailing lists activity due to release and GSoC project work discussions. However compared to previous reports activity level mostly remains the same. We are hoping to increase the level of activity in the project with GSoC and next release work. ----------------------------------------- Attachment Z: Report from the Apache Gobblin Project [Abhishek Tiwari] ## Description: The mission of Apache Gobblin is the creation and maintenance of software related to a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems ## Project Status: Current project status: Ongoing. Issues for the board: None. ## Membership Data: Apache Gobblin was founded 2021-01-19 (3 years ago) There are currently 20 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19. - No new committers. Last addition was Arjun Singh Bora on 2023-10-09. ## Project Activity: * Feature added to disable DAG manager when DAG proc engine is enabled. * Retry logic added to Iceberg replication. * Support to delete triggers whenever deadline enforcement DAG actions are deleted. * Increased ExecuteGobblinWorkflow & WorkFulfillmentWorker execution concurrency. * Optimize max connections to DB through Docker. * Support for long execution ids. * Changed permissions setup before commit for consistent ACLs. * Capability to handle multiple job runs in DAG procs. * Enforcement to not run DAG prod code when DAG prog engine is not enabled. * Clean-up of config ambiguity. * Support for connection timeout option in Couchbase writer. * Fix in JobSpec so that properties are fully reflected from Job configs. * Fix of permission issues with chid directories in CopyDataPublisher. * Addition of DAG action store within DAGManagementStateStore. * Addition of execution start timer to Temporal. * Support for previous event time for lease arbitration of reminder DAG actions. * Addition of eventTimeMillis to leaseAttemptStatus for adhoc flows where flowExecutionId is different than the event time of the lease. * Implementation of DAG proces to enforce job start deadline and DAG completion deadline. * Support to make offset range in Gobblin Metadata pipeline configurable. * Improvement to not prematurely initialize DAGManagementStateStore. * Improvement to ensure Orchestrator cleans up FlowSpec even when orchestration fails. * Addition of GaaSObservabilityEvent for better insights into GaaS operations. * Support for resuming DAG proc. * Support to release containers which are running Helix tasks and stuck in any state. * Addition of settings to allow for fully cleanup in GobblinYarnAppLauncher. * Addition of config to fail Gobblin Distcp writer if setting permissions fails. * Integration of AutomaticTroubleShooter with Gobblin on Temporal. * Generalization of ProcessWorkUnit beyond CopyEntity in Gobblin on Temporal. * Addition of loggin exceptions in HighLevelConsumer queue consumption. * Support to set execute bit only for new folders in manifest Distcp. * Support to handle multiple failure scenarios in multi-leader compilation startup. * Improvement to start DAGActionMonitor only after its dependencies are ready. * Other misc fixes and improvement in DAGProcessingEngine, Telemetry, ComparableWatermark, CommitActivity, FlowLaunchHandler, DAGActionStore, FlowGraph validation, CopySource, SchedulerLeaseArbiter, Icerberg file metrics. * Last Release date: 30th August, 2023 ## Community Health: - There have been 60 commits since March 2024. - 22 commits have been from non-committers. - Arjun Singh Bora was voted in October, 2023 as a committer. We constantly look for consistent contributors to vote them in as Committers. ----------------------------------------- Attachment AA: Report from the Apache Guacamole Project [Mike Jumper] ## Description: The mission of Apache Guacamole is the creation and maintenance of software related to providing performant, browser-based remote access ## Project Status: Current project status: Ongoing, with moderate activity. Issues for the board: none. ## Membership Data: Apache Guacamole was founded 2017-11-14 (7 years ago) There are currently 15 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Luke on 2023-02-22. - No new committers. Last addition was Alexander Leitner on 2023-11-13. ## Project Activity: The project has completed its 1.5.5 release and moved on to progressing 1.6.0, with an eye toward larger changes like the migration away from AngularJS in 2.0.0. Recent releases: - 1.5.5 was released on 2024-04-05. - 1.5.4 was released on 2023-12-07. - 1.5.3 was released on 2023-07-31. ## Community Health: The community continues to be active and healthy. The user mailing list is seeing a steady level of activity, with a routinely decent number of threads and community participants. ----------------------------------------- Attachment AB: Report from the Apache Gump Project [Stefan Bodewig] ## Description Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and OpenSSL. ## Project Status Current Status: dormant - when things need to be done, they get done Issues: There are no issues requiring board attention. ## Membership Data Apache Gump was founded 2004-02-18. There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: No new PMC members. Last addition was Mark Thomas on 2014-12-03. No new committers. Last addition was Konstantin Kolinko on 2015-02-11. ## Project Activity Mark Thomas switched the vmgump builds to use OpenJDK 22 for Java projects, many thanks! The Tomcat community is the only one still using Gump actively and the only activity in Gump is around keeping the infrastructure alive and tweaking things for the benefit of Tomcat builds. We will certainly support any other project that wants to get the benefit of the early warning system for backwards incompatible changes Gump provides, but we are not actively recruiting projects. ### Releases Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. ## Community Health There isn't much happening but help is there when anybody needs it. Apart from foundation wide announcements or infrastructure team messages nobody has posted any message to the Gump mailing list or asked for a change who is not a member of the Gump PMC already for the last five years. ----------------------------------------- Attachment AC: Report from the Apache Helix Project [Junkai Xue] ## Description: The mission of Helix is the creation and maintenance of software related to A cluster management framework for partitioned and replicated distributed resources ## Project Status: Current project status: ongoing, moderate Issues for the board: no major issue. ## Membership Data: Apache Helix was founded 2013-12-17 (10 years ago) There are currently 28 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Jiajun Wang on 2022-11-02. - No new committers. Last addition was Molly Gao on 2023-06-06. ## Project Activity: - 1.4.0 is in progress and plan to release on June - 1.3.1 was released on 2023-09-18 - 1.3.0 was released on 2023-07-25 - 1.2.0 was released on 2023-05-02 - 1.1.0 was released on 2023-01-04 ## Community Health: - One discussion still in the dev channel is deprecating helix-front, which is the UI support. As Helix has limited UI expert and CVE usually comes from this component. - Recent dev work focus on container based support such as redefining instance operation types. - Helix 2.0 topic will be raised up for boarder discussion. High level direction is to 1) simplify Helix APIs for usage 2) multi language support and 3) better flexibility and data model for better performance. ----------------------------------------- Attachment AD: Report from the Apache Hive Project [Naveen Gangam] ----------------------------------------- Attachment AE: Report from the Apache Hudi Project [Vinoth Chandar] ## Description: The mission of Apache Hudi is the creation and maintenance of software related to providing atomic upserts and incremental data streams on Big Data ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Hudi was founded 2020-05-19 (4 years ago) There are currently 38 committers and 19 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Sagar Sumit on 2023-11-05. - No new committers. Last addition was Jonathan Vexler on 2024-02-13. ## Project Activity: The community has released 0.15.0 as a stable release version for 0.x release line. In parallel, active PRs are worked upon on master branch towards a 1.0.0-beta2 release, while taking feedback from 1.0.0-beta1 that was released late last year. A new repo apache/hudi-rs is setup and under development towards its first official release 0.1.0. Community continues to be active with community syncs (monthly) where we present major developments, showcase user talks. New blogs written by Hudi users have been added to the Hudi website's blog page. ## Community Health: We continue to see more active developer engagement on the project in terms of code contributions, and a jump in dev emails. These can be attributed to commits for release items, release email threads, and the new repo's automated email triggered by GH activities (have been moved to commits email list). Overall, the community has been working on stabilizing the branch for 0.15.0 (landing fixes and certifying the artifacts), and expanding to Rust/Python ecosystem. ----------------------------------------- Attachment AF: Report from the Apache Iceberg Project [Ryan Blue] ## Description: Apache Iceberg is a table format for huge analytic datasets that is designed for high performance and ease of use. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Iceberg was founded 2020-05-19 (4 years ago) There are currently 27 committers and 16 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 Szehon Ho on 2023-04-20. - No new committers. Last addition was Renjie Liu on 2024-03-06. ## Project Activity: Releases: - 1.5.1 was released on 2024-04-25 - 1.5.2 was released on 2024-05-09 - PyIceberg 0.6.1 was released on 2024-04-30 PyIceberg: - Contributors are working to release more often - Improved retries for Hive catalog locking - Added register table support for Glue catalogs - Adding metadata table support (snapshots, manifests, etc.) - Working toward 0.7.0 release with partitioned writes and staged table creation Rust: - Implemented projection to support partition-based file pruning - Implemented the inclusive metrics evaluator and predicate pushdown to Parquet - Added Hive catalog support - Improved REST catalog with OAuth2 and custom headers - Added integration with DataFusion Go: - Working toward full expression support; added literals Iceberg Java: - The next Java release, 1.6.0, is targeted for release in June - Specs: - Discussions about standardizing metadata for materialized views have made good progress. The community decided to use existing objects rather than creating a new combined table/view object and is working on metadata details. - An extension to the REST protocol for privilege GRANT and REVOKE operations was proposed. - Many discussions for extending the REST protocol are ongoing, including adding routes to plan scans, adding auth decisions, and appending data files - There are also discussions for v3 features, like additional types (variant, timestampns, and others) ## Community Health: The Iceberg community continues to be healthy, with a large number of commits and individual contributors over the past quarter. Although overall commits decreased, the change corresponds with the number of opened PRs so the change is not a concern for health; PRs are getting reviewed. The community is formalizing design discussions and has added github labels and documented a process for making changes to community specs. The community also held the first Iceberg Summit this quarter, with 32 sessions that are now available on the YouTube (https://tinyurl.com/iceberg-summit). Community members also spoke at CoC EU. A company that employs 3 PMC members and 2 committers was acquired. The PMC members (2 of whom are ASF members) have been reminded to act as individuals, not as representatives of their employer, when interacting in the community. Concentrations of PMC members is a risk that the community is aware of and will note in future board reports. Other projects and announcements: - Trino added support for Iceberg views - Beam has added an Iceberg sink - Confluent, Terradata, and Oracle announced Iceberg support - Snowflake announced a new open source REST catalog project, Polaris - Databricks released its Unity catalog that implements the REST protocol - Nessie added support for the Iceberg REST catalog protocol - Gravino, which supports the REST protocol, was added to the incubator ----------------------------------------- Attachment AG: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for June 2024 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are currently 28 podlings incubating. In May, podlings executed 5 distinct releases and no IP clearances occurred. Several incubating proposals have been discussed on the mailing list. At least one new podling will be joining the incubator - OpenServerless. No podling graduated or retired last month. One person retired from the IPMC. Two podlings, Liminal and Toree, failed to report and will be asked to report next month, and a roll call will be performed. Liminal should probably retire at this point. There was a discussion about the requirements of project download pages and why they are needed, most of the other discussions were on releases. ## Community ### New IPMC members: - None ### People who left the IPMC: - Rich Bowen ## New Podlings - Gravitino ## Podlings that failed to report, expected next month - Liminal - Three ## Graduations - None The board has motions for the following: - None ## Releases The following releases entered distribution during the month of May: - Answer 1.3.1 - Fury 0.5.0 - Fury 0.5.1 - Stormcrawler 3.0 - Streampark 2.1.4 ## IP Clearance - None ## Legal / Trademarks N/A ## Infrastructure N/A ## Miscellaneous N/A ## Table of Contents [Amoro](#amoro) [Annotator](#annotator) [Baremaps](#baremaps) [GraphAr](#graphar) [HertzBeat](#hertzbeat) [KIE](#kie) [Nemo](#nemo) [StormCrawler](#stormcrawler) [Teaclave](#teaclave) [Training](#training) [Uniffle](#uniffle) [Wayang](#wayang) -------------------- ## Amoro Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon. Amoro has been incubating since 2024-03-11. ### Three most important unfinished issues to address before graduating: 1. Release our first Apache release. 2. Build and grow a diverse community. ### Are there any issues that the IPMC or ASF Board need to be aware of? Currently no. ### How has the community developed since the last report? * Attend an offline meetup hosted by StarRocks community, one of our PPMC Member (id: jinsongzhou) gave a presentation named <>. * 3 new contributors joined the Amoro community. ### How has the project developed since the last report? * Started the first Apache release discussion in the dev mailing list and the release manager is working towards it. * Merged 47 PRs in last month. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? 2024-03-11, when the project was accepted into the incubator. ### Have your mentors been helpful and responsive? Yes, Amoro's mentors actively participate in the project, contribute insights, and help advance the project towards graduation. ### Is the PPMC managing the podling's brand / trademarks? Yes, everything is fine. ### Signed-off-by: - [ ] (amoro) Justn Mclean Comments: - [ ] (amoro) Zhongyi Tan Comments: - [X] (amoro) Yu Li Comments: Good to see new contributors joining and look forward to the ASF release. - [ ] (amoro) Xinyu Zhou Comments: - [ ] (amoro) Kent Yao Comments: ### IPMC/Shepherd notes: -------------------- ## Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. ### Three most important unfinished issues to address before graduating: 1. Apache Annotator is unable to produce releases due to low activity 2. PMC is largely inactive 3. Motivation to contribute is low due to inability of producing enough release votes ### Are there any issues that the IPMC or ASF Board need to be aware of? See above. Unless there is interest by new people to join the project and help getting out releases, IMHO it would make more sense to retire the podling, fork it and release it without the three-vote hurdle. ### How has the community developed since the last report? The community has not grown. ### How has the project developed since the last report? Yarn has been dropped from the project in favor of npm. Since then, a number of dependabot issues have piled up. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: it is so stable that it is probably ready for retirement ;) ### Date of last release: 2021-07-14 (0.2.0) We tried to get out a 0.3.0 in May 2022, but it got stuck in the vote. ### When were the last committers or PPMC members elected? @reckart was the last one to join in August 2022 (waving the flag). ### Have your mentors been helpful and responsive? @BigBlueHat has prepared the previous incubator report for this project and has provided some guidance. ### Is the PPMC managing the podling's brand / trademarks? I don't know. ### Signed-off-by: - [ ] (annotator) Nick Kew Comments: - [ ] (annotator) Tommaso Teofili Comments: - [X] (annotator) Benjamin Young Comments: ### IPMC/Shepherd notes: -------------------- ## Baremaps Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps. Baremaps has been incubating since 2022-10-10. ### Three most important unfinished issues to address before graduating: 1. Reviewing the changes made to make the code and documentation website compliant with Apache standards 2. Growing the community 3. Making releases ### Are there any issues that the IPMC or ASF Board need to be aware of? We believe that most of the issues related to licensing have now been addressed. The next step is to remove the DISCLAIMER-WIP in future releases. ### How has the community developed since the last report? No new committer joined the project, but a few issues, documentation improvements, and pull requests were submitted by external contributors. ### How has the project developed since the last report? We released a new version of Baremaps and the process went relatively smoothly. A nice collaborative effort also started to implement a GeoParquet reader and to support OvertureMaps files. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2024-04-27 ### When were the last committers or PPMC members elected? 2023-08-31 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [X] (baremaps) Julian Hyde Comments: - [X] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: -------------------- ## GraphAr GraphAr is an open-source and language-independent data file format designed for efficient graph data storage and retrieval. GraphAr has been incubating since 2024-03-25. ### Three most important unfinished issues to address before graduating: 1. Release our first Apache release. 2. Growing the community(attracting more committers, contributors and users) ### Are there any issues that the IPMC or ASF Board need to be aware of? Currently no ### How has the community developed since the last report? 1. We were selected for OSPP (China's GSoC) 2024. 2. 2 new contributors joined the GraphAr community. ### How has the project developed since the last report? 1. Create 26 PRs in last month. 2. Discuss and draw up road map. 3. Implement the definition of format with Protobuf. 4. Improve the release and verify document. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: We are working towards our first release ### When were the last committers or PPMC members elected? GraphAr has been in incubation since March 25th, 2024. As of yet, no new committers have been elected for the project. ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-221) ### Signed-off-by: - [X] (graphar) Calvin Kirs Comments: - [X] (graphar) tison Comments: - [X] (graphar) Xiaoqiao He Comments: LGTM. +1 for looking forward to seeing the first release. - [X] (graphar) Yu Li Comments: Good to see new contributor joining the community and look forward to the first ASF release. ### IPMC/Shepherd notes: -------------------- ## HertzBeat HertzBeat is an easy-to-use, open source, real-time monitoring system. It features an agentless architecture, high-performance clustering, Prometheus compatibility, and powerful custom monitoring and status page building capabilities. HertzBeat has been incubating since 2024-04-05. ### Three most important unfinished issues to address before graduating: 1. Publish 1st Apache release. 2. Grow the community and attract more users. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? Over the past month, the project has successfully attracted 4 new contributors, some of whom has shown great promise and potential to be considered for committer status in the future. Excluding merges, 26 authors have pushed 105 commits to master and 156 commits to all branches. On master, 792 files have changed and there have been 22,365 additions and 5,961 deletions. ### How has the project developed since the last report? During the past month, HertzBeat has fixed the incompatible protocol LGPL license package, has used Apache Jexl and EclipseLink to replace Hibernate and Avaitor. It has added support for custom pulgin, support hugegraph, openai, Apache Yarn, Hdfs monitoring, support redfish protocol to monitoring server and more. These updates are expected to be included in the upcoming Apache release. And we have conducted three rounds of version release voting. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: We haven't published Apache release. ### When were the last committers or PPMC members elected? HertzBeat has been in incubation since April 05th, 2024. As of yet, no committers have been elected for the project. ### Have your mentors been helpful and responsive? Yes, they are very nice. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues. ### Signed-off-by: - [X] (hertzbeat) Yonglun Zhang Comments: We've started the first release. The team responded quickly, and all issues were handled promptly. - [ ] (hertzbeat) Yu Xiao Comments: - [ ] (hertzbeat) Justn Mclean Comments: - [X] (hertzbeat) Francis Chuang Comments: ### IPMC/Shepherd notes: -------------------- ## KIE KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows. KIE has been incubating since 2023-01-13. ### Three most important unfinished issues to address before graduating: 1. Release 2. Better website 3. Community building (always ongoing) ### Are there any issues that the IPMC or ASF Board need to be aware of? Nope. ### How has the community developed since the last report? We've really been going steady. There hasn't been a big up-tick in new members or anything else. ### How has the project developed since the last report? We are pushing hard for a release. We're working on getting all of the 't's crossed and 'i's dotted. We were hoping to have a vote already, but we have found some issues in our pipelines and some missing headers in files. We're pushing for all of that. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: Haven't had one yet, but we are very close. ### When were the last committers or PPMC members elected? About three months ago. ### Have your mentors been helpful and responsive? No, I don't believe anything is falling through the cracks. We've been pretty constant communication with Infra, the wider Incubator community, and speaking with our mentors as needed. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [X] (kie) Brian Proffitt Comments: Are there any concerns around the recent media coverage about the fate of OptaPlanner? It might be something to detail, just to ease any concerns. - [X] (kie) Claus Ibsen Comments: - [X] (kie) Andrea Cosentino Comments: All looks good and the project is in good shape ### IPMC/Shepherd notes: -------------------- ## Nemo Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Nemo has been incubating since 2018-02-04. ### Three most important unfinished issues to address before graduating: 1. Motivate growth in the community 2. Address remaining items before graduation ### Are there any issues that the IPMC or ASF Board need to be aware of? The issue raised in our previous podling report (Mar. 2024) still exists. This is a project initiated from academia, and many of the committers have graduated with their degree and moved on to something else. The project itself is very promising, known that many outstanding academic papers have been developed on top of Apache Nemo [1-5], so it would be ideal if it finds its purpose, however it seems quite challenging at this particular moment. It is quite disappointing to see the project lose its momentum during the covid-19 pandemics, which made it extremely challenging for us to build the community. Nevertheless, the project itself, I believe, deserved to be in the TLP, but it seems like if there is no breakpoint for the project regarding the project community, I think we could start discussing about sending it to the attic. Any suggestions or opinions are welcome! [1] https://www.usenix.org/conference/atc19/presentation/yang-youngseok [2] https://dl.acm.org/doi/10.1145/3468144 [3] https://dl.acm.org/doi/10.1145/3064176.3064181 [4] https://dl.acm.org/doi/10.1145/3546591.3547524 [5] https://www.usenix.org/conference/atc23/presentation/song ### How has the community developed since the last report? Trying to have a discussion towards the issue raised above ### How has the project developed since the last report? Trying to have a discussion towards the issue raised above ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2022-09-02 ### When were the last committers or PPMC members elected? September 28, 2021 ### Have your mentors been helpful and responsive? Please refer to the issue raised above. ### Is the PPMC managing the podling's brand / trademarks? The PPMC manages the polling's brand / trademarks. ### Signed-off-by: - [ ] (nemo) Hyunsik Choi Comments: - [ ] (nemo) Byung-Gon Chun Comments: - [ ] (nemo) Jean-Baptiste Onofré Comments: - [ ] (nemo) Markus Weimer Comments: ### IPMC/Shepherd notes: -------------------- ## StormCrawler StormCrawler is a collection of resources for building low-latency, customisable and scalable web crawlers on Apache Storm. StormCrawler has been incubating since 2024-03-19. ### Three most important unfinished issues to address before graduating: 1. Community building 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? Nothing yet. ### How has the community developed since the last report? We got some involvement (issues, simple PRs) from outside the usual suspects. We need to increase our outreach to attract more users / developers to foster a healthy community development. ### How has the project developed since the last report? We have published our first release (3.0). We are currently working on adding the feedback received for 3.0. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2024-05-16 ### When were the last committers or PPMC members elected? No new committers yet. ### Have your mentors been helpful and responsive? Nothing to note. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [ ] (stormcrawler) Dave Fisher Comments: - [ ] (stormcrawler) Lewis John McGibbney Comments: - [ ] (stormcrawler) Ayush Saxena Comments: - [ ] (stormcrawler) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## Teaclave Teaclave is a universal secure computing platform. Teaclave has been incubating since 2019-08-20. ### Three most important unfinished issues to address before graduating: 1.Improve project structure and documentation. 2.Grow the community (attracting more committers, contributors, users). 3.Publish Apache releases (resolving logistics on Apache release). ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Since the last report, we have organized three monthly virtual meetups. For each meetup, we have write-ups published on the Teaclave blog . - Teaclave Meetup #13: - Teaclave Meetup #14: - Teaclave Meetup #15: Additionally, we introduced a new project Teaclave Java TEE SDK to our community: ### How has the project developed since the last report? Here are the summaries of recent progress: #### Teaclave Faas Platform - New release 0.6.0: - Merged PRs: #### Teaclave TrustZone SDK - New 'no-std' branch (set as recommended): - Merged PRs: #### Teaclave SGX SDK - Preparing release v2.0.0: - Merged PRs: #### [NEW] Teaclave Java TEE SDK - The first release v0.1.0: https://github.com/apache/incubator-teaclave-java-tee-sdk/releases/tag/v0.1. 0 ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2023-06-26: Apache Teaclave (incubating) FaaS Platfrom 0.6.0 ### When were the last committers or PPMC members elected? 2023-05-04: He Sun (Apache ID: hsun), PPMC ### Have your mentors been helpful and responsive? Yes, our mentors work responsively to help us with electing new mentors, developing new features, fixing bugs, and expanding the community. ### Is the PPMC managing the podling's brand / trademarks? We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175) ### Signed-off-by: - [ ] (teaclave) Felix Cheung Comments: - [ ] (teaclave) Furkan Kamaci Comments: - [ ] (teaclave) Jianyong Dai Comments: - [ ] (teaclave) Matt Sicker Comments: - [ ] (teaclave) Zhijie Shen Comments: - [ ] (teaclave) Gordon King Comments: ### IPMC/Shepherd notes: -------------------- ## Training The Training project aims to collect, and share training resources, and develop tools to support training resource creation (templates, etc.). The resulting tools and curated training artefacts can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects. Training has been incubating since 2019-02-21. ### Three most important unfinished issues to address before graduating: 1. Review and eventually simplify the release process for training artefacts - or at least confirm finally, that we use the existing flow as it is to go on 2. Establish a sharing culture with other projects - Apache Training needs a link to other projects so that the training artefacts can be owned but contributed by the creators of the project, but share via Apache Training 3. Grow the community so that non-tech contributors can find a home inside the ASF, by joining Apache Training as tech-writer, translator, or educator who helps us to spread the words. ### Are there any issues that the IPMC or ASF Board need to be aware of? - nothing critical right now ### How has the community developed since the last report? - the last report was delayed, to access issues but now it works. - the collaboration between Apache Wayang and Apache Training has been established - the joint presentation at the CoC 2024 in Bratislava is a result - one non-tech contributor (from CISO domain) has been interviewed and we work on his onboarding ### How has the project developed since the last report? - I did multiple attempts to release the tools-subproject, but due to permission issues I am not able to to go through the full procedure. - I still need support to sort out this access permission issues. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [OK] Initial setup - [OK] Working towards first release - [W.I.P.] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2024-04-XX (last attempt to release the tools subproject) ### When were the last committers or PPMC members elected? August 2024 ### Have your mentors been helpful and responsive? - access rights for the release manager, who is blocked in the middle of the release process ### Is the PPMC managing the podling's brand / trademarks? - no activities on this yet ### Signed-off-by: - [ ] (training) Craig Russell Comments: - [X] (training) Christofer Dutz Comments: - [X] (training) Justin Mclean Comments: - [ ] (training) Lars Francke Comments: ### IPMC/Shepherd notes: -------------------- ## Uniffle Uniffle is an unified Remote Shuffle Service Uniffle has been incubating since 2022-06-06. ### Three most important unfinished issues to address before graduating: We're starting to discuss the graduation. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? 112 pull requests are created and 69 pull requests are merged. 75 issues are created and 61 issues are closed. ### How has the project developed since the last report? We developed many exciting features. First, Netty data transportation is production available. Second, the we polish the feature stage recomputation. Third, we supported K8S operator for new K8S version. Fourth, we break origin limitation of blockId to support long run time job. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2023-12-13. We released 0.8.0. We are preparing to release 0.9.0 now. ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? Yes, they are helpful. ### Is the PPMC managing the podling's brand / trademarks? No. ### Signed-off-by: - [ ] (uniffle) Felix Cheung Comments: - [ ] (uniffle) Junping Du Comments: - [ ] (uniffle) Liu Xun Comments: - [X] (uniffle) Weiwei Yang Comments: - [ ] (uniffle) Zhankun Tang Comments: ### IPMC/Shepherd notes: -------------------- ## Wayang Wayang is a cross-platform data processing system that aims at decoupling the business logic of data analytics applications from concrete data processing platforms, such as Apache Flink or Apache Spark. Hence, it tames the complexity that arises from the "Cambrian explosion" of novel data processing platforms that we currently witness. Wayang has been incubating since 2020-12-16. ### Three most important unfinished issues to address before graduating: 1. Growing community 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? New PPMC member ### How has the project developed since the last report? New PPMC member and many new features, such as Python API, Tensorflow integration, and initial support for federated data processing ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2024-02-05 ### When were the last committers or PPMC members elected? 2024-05-13 ### Have your mentors been helpful and responsive? Everything good. ### Is the PPMC managing the podling's brand / trademarks? Everything good ### Signed-off-by: - [X] (wayang) Christofer Dutz Comments: - [ ] (wayang) Lars George Comments: - [ ] (wayang) Bernd Fondermann Comments: - [ ] (wayang) Jean-Baptiste Onofré Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AH: Report from the Apache IoTDB Project [Xiangdong Huang] ## Description: The mission of Apache IoTDB is the creation and maintenance of software related to an IoT native database with high performance for data management and analysis ## Project Status: Current project status: Ongoing with high activity. Issues for the board: - there are some trademark issues and the community has resolved them. ## Membership Data: Apache IoTDB was founded 2020-09-16 (4 years ago) There are currently 63 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Steve Yurong Su on 2023-09-28. - William Song was added as committer on 2024-03-22 - Caiyin Yang was added as committer on 2024-06-12 ## Project Activity: - Recent releases: IOTDB-1.3.2 is on the way. IOTDB-1.3.1 was released on 2024-04-22. IOTDB-1.3.0 was released on 2024-01-01. IOTDB-1.2.2 was released on 2023-10-15. - Main work of project: * We are working on the table model providing data to users in a table view in the same way as relational databases which will greatly reduce the learning curve of IoTDB. * Collaborate with the Apache StreamPipes community to improve the IoTDB plugin and explore other means on integration. * New query optimization rules are added to greatly improve the query performance of IoTDB, like PredicatePushDown and AggregatePushDown. * Explain Analyze tool which can be used to analyze specific query performance better and is a good tool for troubleshooting performance problems ## Community Health: Overall community health is good. - on 2024-04-09, IoTDB was presented at the JavaLand Summit in Germany. The talk was given by Christofer Dutz. - on 2024-06-03, IoTDB was presented in 2 talks at CommunityOverCode EU. The talks were given by Christofer Dutz and Julian Feinauer. - Joined "Digital Economy-Urban Open Source Tour" meetup in Shanghai. - the mailing list traffic increases (226 emails compared to 76) ----------------------------------------- Attachment AI: Report from the Apache Jackrabbit Project [Marcel Reutegger] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Project Status: The project is ongoing with moderate activity. There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (18 years ago). There are currently 59 committers and 59 PMC members in this project. The Committer-to-PMC ratio is 1:1, because all committers automatically become PMC members. Community changes, past quarter: - No new PMC members. Last addition was Nuno Santos on 2023-11-14. - No new committers. Last addition was Nuno Santos on 2023-11-13. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. Steffen Van suggested introducing a code formatter for the Jackrabbit Oak code base. The proposal sparked a discussion on the mailing list and a corresponding pull request. Jackrabbit committers voiced concerns about the impact on git diff readability and backporting of changes to maintenance branches. No decision has been made yet. A new revision garbage collection feature was added to Jackrabbit Oak. The feature is disabled by default and can be enabled with a feature toggle. Additional work is in progress to control the type of garbage that is collected. After some confusion about the Jackrabbit even/odd minor version scheme, the team decided to add a -beta suffix to releases with an odd minor version number. The first release with the new versioning scheme was Jackrabbit 2.21.26-beta on March 28th. ## Community Health: The project is generally healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.15 was released on 2024-03-11 - jackrabbit-oak-1.22.19 was released on 2024-03-14 - jackrabbit-2.21.26-beta was released on 2024-03-28 - jackrabbit-oak-1.62.0 was released on 2024-04-09 - jackrabbit-2.20.16 was released on 2024-05-13 - jackrabbit-oak-1.22.20 was released on 2024-05-13 - jackrabbit-oak-1.64.0 was released on 2024-05-27 ## JIRA activity: - 207 JIRA tickets created in the last 3 months - 179 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache Johnzon Project [Jean-Louis Monteiro] ----------------------------------------- Attachment AK: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: The mission of the Apache Karaf project is the creation and maintenance of open-source software related to a generic platform providing higher level features and services specifically designed for creating OSGi-based servers for distribution at no charge to the public. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Karaf was founded 2010-06-16 (14 years ago) There are currently 32 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2018-11-29. - No new committers. Last addition was Robert Varga on 2023-10-31. ## Project Activity: We released: * Karaf runtime 4.4.6 was released on 2024-04-12. We are already preparing Karaf 4.4.7 with several improvements on top of 4.4.6 like Spring 5/6 features, dependency updates. ## Community Health: The karaf-integration distribution is planned for Karaf 4.5.0 (see KARAF-7792). We are happy to help on camel-karaf. The main branch has now been updated: https://github.com/apache/camel-karaf Apache Karaf 4.4.6 and Camel 4.6.0 are now working fine thanks to camel-karaf, including the camel:* shell commands. camel-karaf also includes components very useful on the karaf runtime (especially camel-direct-vm and camel-vm). ----------------------------------------- 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 30 committers and 30 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Marton Greber on 2023-11-09. - No new committers. Last addition was Marton Greber on 2023-11-09. ## Project Activity: - 1.17.0 was released on 2023-09-01. - 1.16.0 was released on 2022-04-11. - 1.15.0 was released on 2021-06-22. ## Community Health: - Development activity measured in the number of commits has increased (+31%). Development measured in the number of unique developers increased slightly (11 to 14). The previous quarter had a dip in activity on account of developers being out and a Jenkins upgrade taking some bandwidth. - The number of issues opened has decreased (4 issues opened, -85%), while the number of issues closed has increased slightly (7 issues closed, +40%). - Traffic across all mailing lists is up (dev@ +42%, issues@ +26%, reviews@ +62%). - Community activity measured in community Slack is steady (the number of weekly active users -5%, and public posters +9%). ----------------------------------------- Attachment AM: Report from the Apache Kvrocks Project [Hulk Lin] ## Description: The mission of Apache Kvrocks is the creation and maintenance of software related to a distributed key-value NoSQL database, supporting the rich data structure ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kvrocks was founded 2023-06-21 (a year ago) There are currently 24 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Pengbo Cai was added to the PMC on 2024-03-18 - Xuwei Fu was added to the PMC on 2024-03-22 - No new committers. Last addition was Ji Huayu on 2024-01-23. ## Project Activity: Apache Kvrocks has released 2.8.0 in the past quarter. The community is planning the next release, as well as the first release of its subproject: kvrocks-controller. For the Kvrocks part, the notable feature is that Kvrocks now supports RedisSearch basic commands, the most popular module in the Redis stack. I believe this feature will make a lot of users happy. Apart from new features, we're active in resolving bugs and security issues found by the community. And for its sub-project: kvrocks-controller, we're mainly focused on refactoring to make it production-ready, and it's ready now. The community also actively participates in GSoC and OSPP(Open Source Promotion Plan) to attract more contributors. ## Community Health: The issues/PRs have decreased (-26% / -8%) in the past quarter because we're focused on developing the RedisJSON module which involves many new commands and contributors. I believe the community is steady and healthy. And from the user side, we're proud to know that the open-source project: CVAT has adapted Apache Kvrocks to replace Redis. Also, the famous development tool: wakatime uses Apache Kvrocks as its cache. Besides, Kvrocks got much more attention as an alternative replacement for Redis. ----------------------------------------- Attachment AN: Report from the Apache Kyuubi Project [Kent Yao] ## Description: The mission of Apache Kyuubi is the creation and maintenance of software related to a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses ## Project Status: Current project status: Ongoing: With moderate activity Issues for the board: None ## Membership Data: Apache Kyuubi was founded 2022-12-21 (a year ago) There are currently 27 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 9:5. Community changes, past quarter: - No new PMC members. Last addition was Zhen Wang on 2023-11-07. - Zhou Yifan was added as committer on 2024-03-24 ## Project Activity: Software development activity: - We released the bug fix release 1.9.1 for Apache Kyuubi on 2024 Jun 3. - We released the minor feature release 1.9.0 for Apache Kyuubi on 2024 Mar 19. - We released the bug fix release 1.8.2 for Apache Kyuubi on 2024 Apr 26. - The donation of PyHive project is resolved and the IP Clearance is approved by IPMC. - Integrated JDBC Engine with Apache Hadoop Yarn scheduler Meetups and Conferences: - One of our PMC submited a subject and got accepted by CoC Asia 2024, it's a good opportunity to help other podling grow wit Kyuubi. 'Accelerating Queries on Apache Kyuubi with Apache Gluten(Incubating) and Velox Engine at NetEase' ## Community Health: By reviewing the statistics of Q2, the Github issues, commits and the traffic of mailing lists are in line with Q1 ----------------------------------------- Attachment AO: Report from the Apache Linkis Project [Shuai Di] ## Description: The mission of Apache Linkis is the creation and maintenance of software related to a distributed computation middleware to facilitate connection, governance and orchestration between the upper applications and the underlying data engines. ## Project Status: Current project status: New Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache Linkis was founded 2022-12-21 (a year ago) There are currently 37 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC. Last addition was Jie Cheng on 2024-01-28. - No new committers. Last addition was GuoHua Liu on 2023-12-06. ## Project Activity: Apache Linkis V1.6.0 version is under testing and is expected to be released in June. Mainly includes the following features: - Spring cloud version upgrade fixes security issues - Flink supports UDF function - Support doris engineconn - Result set storage supports switching to orc and Parquet formats - Orchestator supports substitution - Apache Spark etl supports Apache Doris In addition, the requirements for Linkis V1.7.0 are being collected and will enter development in July. Meetups and Conferences: - No ## Community Health: Overall community health is good. - 22 PRs closed on GitHub, past quarter - 37 issues closed on GitHub, past quarter ----------------------------------------- Attachment AP: Report from the Apache Lucene Project [Chris Hegarty] ## Description: The mission of Lucene is the creation and maintenance of software related to Search engine library ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Lucene was founded 2005-01-19 (19 years ago) There are currently 100 committers and 68 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Ben Trent on 2024-02-22. - No new committers. Last addition was Chao Zhang on 2024-02-20. While not a problem in and of itself, this is a good opportunity to remind PMC members to keep an eye on activity so as to identify new potential committers and PMC members, where appropriate. ## Project Activity: - 9.11.0 was released on 2024-06-06 - Support for posix_madvise, allowing to advise the system of the type of memory access being performed. For example, random access for vector data, or sequential access for docvalues. - Expand support for new scalar bit levels for HNSW vectors. including 4-bit vectors and an option to compress them to gain a 50% reduction in memory usage. - Speed up vector comparisions ~2x by scoring byte vectors off-heap. - Recursive graph bisection is now supported on indexes that have blocks - Release notes: https://lucene.apache.org/core/9_11_0/changes/Changes.html - Working towards Lucene 10.0 - It's been ~2.5 years since Lucene 9.0 (December 2021) - Tentative release date of October 1st - Gathering requirements and making necessary preparations Additional, let's see how we can celebrate the upcoming milestone of the new major release, Lucene 10, later this year. ## Community Health: Community interactions remain very healthy, with good activity in all areas (discussions, PRs, etc). - The dev@ mailing list had a 50% decrease in traffic compared to the last quarter (147 emails compared to 294). There were no particularly contentious topics, but rather a healthy amount of discussion on a breath of subjects. Much of the technical discussion happens in GitHub issues and PRs, rather than the mailing list. - Development remains very active. In this quarter: - 423 commits across all branches - 202 PRs opened - 165 PRs closed - This is down a little from the previous quarter, but still very healthy. - PR volume remains healthy, with open PRs trending in a steady state while closed PRs remain steady (https://home.apache.org/~mikemccand/lucenebench/github_pr_counts.html). ----------------------------------------- Attachment AQ: Report from the Apache Lucene.Net Project [Shad Storhaug] ----------------------------------------- Attachment AR: Report from the Apache Mnemonic Project [Gordon King] ----------------------------------------- Attachment AS: Report from the Apache Mynewt Project [Szymon Janc] ----------------------------------------- Attachment AT: Report from the Apache NetBeans Project [Geertjan Wielenga] ## Description: The mission of Apache NetBeans is the creation and maintenance of software related to development environments, tooling platforms, and application frameworks. ## Project Status: Current project status: Ongoing with steady activity. Issues for the board: Issues for the board: none. ## Membership Data: Apache NetBeans was founded 2019-04-17 (5 years ago) There are currently 82 committers and 65 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - No new PMC members. Last addition was Michael Bien on 2022-05-01. - No new committers. Last addition was Tomas Hurka on 2023-05-24. ## Project Activity: Apache NetBeans 22 was released on 2024-05-29. 21.9.9 NetBeans VSCode Extension was released on 2024-04-13. Apache NetBeans 21 was released on 2024-02-20. ## Community Health: - The release of Apache NetBeans 22 was done more as a community and less driven by one or two people, which was a good development for the project. - Apache NetBeans 22 was released thanks to 25 contributors, including 3 who have contributed for the first time. - dev@netbeans.apache.org had a 4% increase in traffic in the past quarter (121 emails compared to 116). ----------------------------------------- Attachment AU: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source product for the automation of enterprise processes that includes framework components and business applications for ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset Management). Apache OFBiz provides a foundation and starting point for reliable, secure and scalable enterprise solutions. ## Project Status: Current project status: Ongoing Issues for the board: none. ## Membership Data: Apache OFBiz was founded 2006-12-20 (17 years ago) There are currently 58 committers and 36 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 Giulio Speri on 2023-12-21. - No new committers. Last addition was Mekika Leila on 2022-09-28. ## Project Activity: * New releases: ** 18.12.13 was released on 2024-05-07 ** 18.12.14 was released on 2024-05-31. * Security: we have disclosed and fixed two vulnerabilities that have been addressed by the latest releases: CVE-2024-32113 and CVE-2024-36104. * Based on the conversations in our dev list, we may soon create a new release branch that, once stabilized, will supersede the 18.12 release branch. * Trademarks: there are no trademark related concerns at the moment. ## Community Health: No new PMC members have been invited during the last quarter (but, after a rather long time, we had three new members in the previous quarter). No new committers have been invited during the last quarter but there are some candidates in our radar. Community activity over the last quarter has been on average. A nice group of members of the OFBiz community met in Bratislava at Community Over Code EU 2024 to follow the sessions, learn more about each other, chat about the project and have fun together. ----------------------------------------- Attachment AV: Report from the Apache Olingo Project [Michael Bolz] ## Description: The Apache Olingo Project is responsible for the creation and maintenance of software related to providing an implemention of the OASIS OData (Open Data Protocol) specifications, in server and client form; ## Project Status: Current project status: Dormant Issues for the board: No issues requiring board attention at this time. ## Membership Data: Apache Olingo was founded 2014-03-19 (10 years ago) There are currently 25 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Ramya Vasanth on 2019-04-15. - No new committers. Last addition was Archana Rai on 2017-05-26. ## Project Activity: Recent releases: - V4 5.0.0 was released on 2023-12-18. - 4.10.0 was released on 2023-10-22. - V2 2.0.13 was released on 2023-10-22. For V2 a feature release (version 3.0.0) is in progress, however it is delayed and will not come before July/August. For V4 the next release is a maintenance release planned in December. ## Community Health: Overall community health is somewhat okayish. Activity on the mailing lists decreased and there are no contributions, but new JIRA items. Roadmap for feature release was discussed and decided, resulting in the plan mentioned in project activity. ----------------------------------------- Attachment AW: Report from the Apache OpenDAL Project [Hao Ding] ## Description: Apache OpenDAL is a data access layer that allows users to easily and efficiently retrieve data from various storage services in a unified way. Its vision centers on enabling **access data freely**, with the goal of empowering ALL users to freely access ANY storage service in ANY way they choose. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: - There are currently 23 committers and 16 PMC members in this project. - The Committer-to-PMC ratio is roughly 3:2. #### Community changes, past quarter: - Yang Shuai was added to the PMC on 2024-03-18 - Runjie Yu was added as committer on 2024-06-10 ## Project Activity: ### New Release OpenDAL released version 0.47.0 this week. Now, OpenDAL integrates seamlessly with the developing Apache Iceberg Rust and Apache Arrow Rust. Additionally, the community is interested in collaborating with more open source communities. ### Events The two student-related events, GSoC and OSPP, were successful. Six students were selected to work on various projects, ranging from additional storage service support (monofs, opfs) to enhanced protocol support (fuse fs, virtio fs, ftp), among others. One student has been nominated as a committer, and two others are strong candidates for the new committer role. The OpenDAL PMC expect most students at this event to become OpenDAL committers. ## Community Health: ### Mailing List - dev@opendal.apache.org had a 50% decrease in traffic in the past quarter (106 emails compared to 209) This is the first time the OpenDAL PMC has performed quarterly reports. Our data are compared with our graduation discussion, which is quite extensive and active. However, the OpenDAL PMC acknowledges that most discussions occur on Discord and GitHub, which are not sufficiently public. We plan to shift more formal discussions to a mailing list to ensure the entire community is informed about our progress, rather than just those who follow GitHub events or have joined our Discord. ### Contributors Since our last update, the OpenDAL community has integrated 219 pull requests across 757 files, thanks to the efforts of 41 contributors. Our total number of contributors has now reached 204, an increase of 16 from our previous report. The OpenDAL PMC has completed the internal refactor, establishing a strong foundation to attract more contributors and users. We will pay closer attention to our integrations (such as arrow_rs object_store, webdav, ftp) and binaries (including opendal command line, opendal gateway, opendal fs). We aim to broaden the use cases for OpenDAL and ultimately increase our contributor base. ----------------------------------------- Attachment AX: Report from the Apache OpenJPA Project [Mark Struberg] ----------------------------------------- Attachment AY: Report from the Apache OpenNLP Project [Jeff Zemerick] ## Description: The mission of OpenNLP is the creation and maintenance of software related to Machine learning based toolkit for the processing of natural language text ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache OpenNLP was founded 2012-02-14 (12 years ago) There are currently 25 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Martin Wiesner on 2023-06-24. - No new committers. Last addition was Atita Arora on 2023-02-28. ## Project Activity: We released minor revisions in the past quarter which is more often than we used to release which is good. The project is working on releasing trained NLP models as Maven dependencies. This may help lower the barrier of entry to using OpenNLP. We raised LEGAL-676 regarding older trained models. ## Community Health: Outside contributor activity is low but the project remains healthy. OpenNLP will be represented at Apache Community over Code NA. ----------------------------------------- Attachment AZ: Report from the Apache OpenWebBeans Project [Mark Struberg] ----------------------------------------- Attachment BA: Report from the Apache Paimon Project [Jingsong Lee] ## Description: The mission of Apache Paimon is the creation and maintenance of software related to a unified lake storage to build dynamic tables for both stream and batch processing with big data compute engines, supporting high-speed data ingestion and real-time data query ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Paimon was founded 2024-03-20 (2 months 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 (project graduated recently). - No new committers were added. ## Project Activity: Software development activity: - We released the first release 0.8.0 on 2024-05-10. - We are preparing to making release candidates for 0.8.1 in the coming week. - We are developing Deletion Vectors supports for non-primary-key table. ## Community Health: The Paimon community is healthy and active. dev@paimon.apache.org had a 60% increase in traffic in the past quarter (186 emails compared to 116) issues@paimon.apache.org had a 14% increase in traffic in the past quarter (2648 emails compared to 2314) user@paimon.apache.org had a 39% decrease in traffic in the past quarter (37 emails compared to 60) ----------------------------------------- Attachment BB: Report from the Apache Pekko Project [PJ Fanning] ## Description: The mission of Apache Pekko is the creation and maintenance of software related to a toolkit and an ecosystem for building highly concurrent, distributed, reactive and resilient applications for Java and Scala. ## Project Status: Current project status: Ongoing with moderate activity. Issues for the board: Nothing ## Membership Data: Apache Pekko was founded 2024-03-20 (3 months ago) There are currently 27 committers and 20 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - JingZhang Chen was added to the PMC on 2024-05-29 - A new committer, Jiafu Tang, has accepted an invite. - We are still setting up his Apache ID ## Project Activity: We are working through the various Pekko modules to do v1.1.0-M1 releases. 4 are complete. More modules still need v1.1.0-M1 RCs. ## Community Health: Mailing list and GitHub Issues/PRs/Discussions remain reasonably active. There is evidence from Apache Nexus and elsewhere of good uptake of the v1.0.x releases. ----------------------------------------- Attachment BC: Report from the Apache Pig Project [Koji Noguchi] ----------------------------------------- Attachment BD: Report from the Apache Pivot Project [Roger Lee Whitcomb] ----------------------------------------- Attachment BE: Report from the Apache PLC4X Project [Christofer Dutz] ## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: None ## Membership Data: Apache PLC4X was founded 2019-04-16 (5 years ago) There are currently 21 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was César García on 2021-09-30. - No new committers. Last addition was Jinlin Hong on 2022-11-02. ## Project Activity: - Version 0.12.0 was released on 2024-02-19. - On 03/23/2024 the team held a work meeting in Franfurk with the purpose of defining the work path towards version 1.0.0, the main focus being the implementation of the management of the real or emulated subscription concept as applicable for the specific device. - The "plc4x" repository was separated between "plc4x" (core) and "plc4x-extras", the latter containing the examples and integration projects with other Apache projects. - The support of libraries with python "plc4xpy" was moved to top level, its incorporation to The Python Package Index is being planned. ## Community Health: There has been no invitation to a new committer for a while. The user base based on statistical reports (individuals and other institutions) is increasing. Although the level of commits has decreased in this period, the community is working on the objectives established for version 1.0.0. . dev@plc4x.apache.org had a 29% decrease in traffic in the past quarter (437 emails compared to 608) . issues@plc4x.apache.org had a 67% increase in traffic in the past quarter (248 emails compared to 148) . 61 commits in the past quarter (-83% decrease) . 7 code contributors in the past quarter (-53% change) ----------------------------------------- Attachment BF: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic] ## Description: The mission of the Apache Portable Runtime (APR) project is to create and maintain software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. The primary goal is to provide an API to which software developers may code and be assured of predictable if not identical behaviour regardless of the platform on which their software is built, relieving them of the need to code special-case conditions to work around or take advantage of platform-specific deficiencies or features. ## Project Status: Current project status: ongoing Issues for the board: no issues requiring board attention ## Membership Data: Apache Portable Runtime (APR) was founded 2000-12-01 (24 years ago) There are currently 68 committers and 43 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Steffen Land on 2023-03-02. - No new committers. Last addition was Steffen Land on 2023-02-27. ## Project Activity: The quarter activity was moderate, nothing unusual. Great work from ivan to improve the cmake/vcpkg build system and running the tests suite on windows. With more contributions comes more code review which shows up on dev@ activity too. No new release this quarter. ## Community Health: Some discussions started about how APR-2 (trunk) could be (re)modularized, not like APR-1 and APR1-util with different repositories, but rather how the build from a single code base could produce separate libraries for each non-core feature (DB, crypto, xml, ldap, ...) which apps/distros could link to as needed without depending on the rest. ----------------------------------------- Attachment BG: Report from the Apache Portals Project [Neil Griffin] ## Description: The mission of Portals is the creation and maintenance of software related to Portal technology ## Project Status: Current project status: Apache Pluto is a stable implementation of a JCP standard and is currently in a maintenance mode. Issues under consideration at this point largely (if not entirely) consist of 3rd party dependency upgrades. ## Membership Data: Apache Portals was founded 2004-02-17 (20 years ago) There are currently 40 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Neil Griffin on 2017-02-11. - No new committers. Last addition was Ahmed on 2016-08-06. ## Project Activity: No new activity since the last report, which mentioned the release of Apache Portals Pluto 3.1.2 on December 20, 2023. ## Community Health: There is no recent activity on the dev lists, and no recent community contributions. Again, the project is in a maintenance mode. ----------------------------------------- Attachment BH: Report from the Apache Pulsar Project [Matteo Merli] ----------------------------------------- Attachment BI: Report from the Apache Ranger Project [Selvamohan Neethiraj] ## Description: Apache Ranger is a framework to enable, monitor and manage comprehensive data security - consistently across various data processing services. ## Issues: There are no issues requiring board attention at this time ## Membership Data: - Apache Ranger was founded 2017-01-17 (6 years ago). - There are 33 committers and 16 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 Sailaja Polavarapu on 2019-09-18. - Last addition to Committer was Dhaval Rajpara, added on 2024-04-25 ## Project Activity: - Still working on Ranger 3.0.0 version with more than 66 jira(s) in unresolved status. - Key features addressed in 3.0.0 release in the past quarter: -- Improvement in GDS (Governed Data Sharing) to support filter by object identifier -- Enhancement of Hive masking expression -- Upgrade of react-bootstrap library version -- Support Ranger KMS integration with AWS KMS -- Improved memory management of plugins -- Configurable GraalVM features -- Upgrade of Spring Security (5.7.12) and Spring Framework (5.3.33) versions -- Improved re-use of code by moving getResourceACL() to RangerPolicyEvaluator ## Community Health: No Significant changes to mailing list traffic. - 587 emails in dev@ranger.apache.org in this quarter (- 49% change from past quarter) - 42 emails in user@ranger.apache.org in this quarter (+133% change from past quarter) - 23 issues opened in JIRA in this quarter (- 85% change from past quarter) - 12 issues closed in JIRA in this quarter (- 87% change from past quarter) - 20 commits in this quarter (- 81% change from past quarter) - 12 code contributors in this quarter (- 36% change from past quarter) - 6 PRs opened on GitHub in this quarter (+ 50% change from past quarter) - 10 PRs closed on GitHub in this quarter (+150% change from past quarter) ## Most Recent releases: - Apache Ranger 2.4.0 was released on 2023-03-30 - Apache Ranger 2.3.0 was released on 2022-07-06 - Apache Ranger 2.2.0 was released on 2021-11-01 ----------------------------------------- Attachment BJ: Report from the Apache Royale Project [Yishay Weiss] ## Description: The mission of Apache Royale is the creation and maintenance of software related to improving developer productivity in creating applications for wherever JavaScript runs (and other runtimes). ## Project Status: ## Membership Data: Apache Royale was founded 2017-09-20 (7 years ago) There are currently 20 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Hugo Ferreira on 2022-10-27. - No new committers. Last addition was María José Esteve on 2021-11-23. ## Project Activity: Discussions about the next release were started. We hope to have a change in RM for this release. Latest release is 0.9.10. Release date: May 31, 2023. ## Community Health: There has been an increase in user activity due to new users showing an interest or actually starting to use the product. Commits to Apache repos have shown a decrease but there have been commits made to other repos (e.g. the Spectrum component set). New developers have trained to use Royale, which indicates a healthy eco-system. ----------------------------------------- Attachment BK: Report from the Apache SDAP Project [Nga Thien Chung] ## Description: The mission of Apache SDAP is the creation and maintenance of software related to an integrated data analytic center for Big Science problems ## Project Status: Current project status: New Issues for the board: none ## Membership Data: Apache SDAP was founded 2024-04-17 (2 months ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past month: - No new PMC members (project graduated recently). - No new committers were added. - Invitations were sent out to 2 potential additions to PMC membership/committership. ## Project Activity: SDAP community has not yet made a release after TLP was established. Most recent SDAP release was 1.2.0 on 2024-03-15 VOTE for SDAP release 1.3.0 was started on 2024-06-10. ## Community Health: ### Mailing List Since last month, dev@sdap.apache.org had 3 new threads. ### Contributors Since last month, the SDAP community has merged 7 PRs and created/updated 10 Jira issues. ----------------------------------------- Attachment BL: Report from the Apache SeaTunnel Project [Jun Gao] ## Description: The mission of Apache SeaTunnel is the creation and maintenance of software related to a very easy-to-use ultra-high-performance distributed data integration platform that supports real-time synchronization of massive data ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache SeaTunnel was founded 2023-05-17 (a year ago) There are currently 30 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - Guangdong Liu was added to the PMC on 2024-05-15 - No new committers. Last addition was Yao Zhou on 2023-11-14. ## Project Activity: SeaTunnel version 2.3.5 was released on 2024-05-07. ## Community Health: At present, the activity of the community is declining, the most important reason is that the transformation of the connector has involved more in-depth technical details, and we need more technical experienced contributors. We're working on it. ----------------------------------------- Attachment BM: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ## Description: The mission of Apache ServiceMix project is to create and maintain a flexible, open-source integration container, powered by OSGi, that unifies the features and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful runtime platform you can use to build your own integrations solutions. ## Issues: No issue requiring board attention. ## Membership Data: Apache ServiceMix was founded 2007-09-19 (15 years ago) There are currently 50 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Andrea Cosentino on 2017-03-15. - No new committers. Last addition was Andrea Cosentino on 2016-03-13. ## Project Activity: Recent Releases: - bundles-2024.03 - bundles-2024.05 ## Community Health: Still in maintenance mode. The ServiceMix community is working on camel-karaf to support camel 4.x. Karaf 4.5.0 will provide the kataf-integration distribution as alternative for SMX. Karaf 4.5.x will wrap the bundles on the fly and the further maintenance of ServiceMix Bundles will be no more required. We will be able to move the project to attic soon. ----------------------------------------- Attachment BN: Report from the Apache Shiro Project [Brian Demers] ## Description: The mission of Shiro is the creation and maintenance of software related to Powerful and easy-to-use application security framework ## Project Status: Current project status: Ongoing with low activity Issues for the board: We have no issues that require Board assistance at this time. ## Membership Data: Apache Shiro was founded 2010-09-21 (14 years ago) There are currently 14 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:6. Community changes, past quarter: - No new PMC members. Last addition was Lenny Primak on 2022-12-04. - No new committers. Last addition was Lenny Primak on 2022-11-02. ## Project Activity: The Shiro team is actively working on 2.0, and 1.x is in maintenance mode. 2.0 is now GA and we are in the process of figuring out a End-of-life plan for 1.x - 2.0.1: 2024-05-25 ## Community Health: Mailing list traffic is up a bit in general as issues and questions about the major release are raised. ----------------------------------------- Attachment BO: Report from the Apache SINGA Project [Wang Wei] ## Description: The mission of Apache SINGA is the creation and maintenance of software related to a distributed deep learning platform ## Project Status: Current project status: Ongoing Issues for the board: N.A. ## Membership Data: Apache SINGA was founded 2019-10-16 (3 years ago) There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Chris Yeung on 2020-04-17. - No new committers. Last addition was Naili Xing on 2022-11-19. ## Project Activity: The team has released SINGA 4.2.0 on 15 March 2024. In the past quarter, the community is fixing some bugs of V4.2, as well as working on the following features/changes: 1. Update the dockerfile for RDBMS such as polarDB and postgresql. 2. Add more traninig datasets for structured data analytics. 3. Update the online documentations and example illustrations for the structured data analytics. 4. Update the deployment configurations and environments for the model selection example. 5. Update the SINGA installation wheel files and the corresponding docker file. 6. Update the HFL example. ## Community Health: According to the statistics, there are increase of email traffic, code contributors, and resolved GitHub issues which shows that the community is active in the development. ----------------------------------------- Attachment BP: Report from the Apache Sling Project [Robert Munteanu] ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Project Status: Current project status: Ongoing, with moderate activity. Issues for the board: none. ## Membership Data: Apache Sling was founded 2009-06-17 (15 years ago) There are currently 51 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Joerg Hoh on 2022-06-13. - No new committers. Last addition was Henry Kuijpers on 2023-10-19. ## Project Activity: We released version 12 of our sample application, the Sling Starter, on March 18th, 2022. We have not yet made plans for version 13, but individual modules are being developed and released, with 21 releases for this reporting period. Work is ongoing for migrating individual modules to the Jakarta JSON specification. ## Community Health: Community health is pretty good and contributions from various individuals continue. ----------------------------------------- Attachment BQ: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for June 2024 ## Description: SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. ## Project Status: Project state: Ongoing with low to moderate activity Primary focus for development is now ongoing maintenance bug fixes to the recently released 4.0.1. Issues for the board: None ## Membership Data: Apache SpamAssassin was founded 2004-06-01 (20 years ago) There are currently 33 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Paul Stead on 2021-03-23. - Kent Oyer was added as committer on 2024-03-29. ## Project Activity: New release this quarter: Apache SpamAssassin version 4.0.1 on 29 March 2024. We maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. ## Community Health: Maintenance of our rule update infrastructure, developer community submissions for rule update testing, and our dev and user mailing lists, are continuing smoothly. ----------------------------------------- Attachment BR: Report from the Apache Storm Project [Richard Zowalla] ## Description: The mission of Storm is the creation and maintenance of software related to Distributed, real-time computation system ## Project Status: Current project status: Ongoing (reactivated) Issues for the board: None ## Membership Data: Apache Storm was founded 2014-09-17 (9 years ago) There are currently 47 committers and 46 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Nikhil Singh on 2023-10-23. - No new committers. Last addition was Nikhil Singh on 2023-10-23. ## Project Activity: Project activity has slowed down over the past few years. Storm is essentially in maintenance mode. We have upgraded many third-party libraries to newer versions in order to reduce technical debt, and did a maintenance release in May. We hope to maintain this release cadence and release patches at a similar frequency. We are still working on reducing third-party dependencies in Storm. Storm depends on many third-party party libraries. It remains a huge task to to reduce this technical debt in order to have a controlled set of third-party dependencies. On another technical note, the Storm UI has a lot of legacy and outdated Javascript libraries in the Git repository. Sadly, we do not have any dedicated and skilled frontend developers among the active committership. The project has decided to migrate issues from Jira to GitHub, but we did not make any progress. We want to migrate our old issues towards GitHub but the ticket on INFRA side is stalled. We might start a discussion to just switch Jira into „read only“ mode and start over again. This step may may require some technical changes to our release tools and documentation. We are are confident that this move will attract new users and contributors by lowering the barrier to entry for issues. In addition, we are receiving issues and questions on the user list from time to time, which is a good sign, that Storm is still in use. Recent releases - 2.6.2 was released on 2024-04-05. ## Community Health: Community engagement is currently healthy, but could benefit from new contributors or users. However, active contributions from outside remain sparse. ----------------------------------------- Attachment BS: Report from the Apache Streams Project [Steve Blackmon] ----------------------------------------- Attachment BT: Report from the Apache TomEE Project [David Blevins] ## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Activity on the project over the last quarter is 94 commits from 4 individuals, with 84 of those commits from one individual. The project voted in new contributor, Thomas Andraschko, at the end of March. Thomas has been active in helping the project with library upgrades, partuclarly, pertaining to MyFaces. Thomas' last contribution was February 5th this year. ## Activity Work on Jakarta EE 10 is still the main focus. The first milestone of TomEE 10 was released in early April. Primary areas of work over the last quarter have been in setting up more TCKs and getting the corresponding tests running in the build. Two of the most notable are the JAX-RS and Jakarta Security TCKs. A PR for the JAX-RS TCK was started some months ago from a new contributor. The PR required significant rework before it could be merged and the original author was a good sport with allowing changes. It was a brave first contribution and we hope the author will continue contributing. A PR for OpenID support from Jakarta Security 3.0 was recently merged. This PR had significant changes with 44 files changed and represents a pretty significant contribution. This PR comes from a new contributor and gives the project some hope. This kind of contribution is extremely rare and exactly what we need. Overall there are still TCKs not yet setup and we are still a long way from being compliant with Jakarta EE 10 and MicroProfile 6. Discussion has started on rolling a second milestone of TomEE 10. This will be the first release with Java 17 as the base JVM requirement. A requirement for such a release would be a new milestone or beta release of CXF 4.1.0-SNAPSHOT. Should the CXF community not want to do an interim build of some kind for us, we would need to opt to do such a milestone release of CXF 4.1.0-SNAPSHOT under the org.apache.tomee Maven group id, something we prefer not to do, but have done a handful of times as often our desires for a milestone are not perfectly timed with other communities. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 34 committers. - Last committer added was Thomas Andraschko on March 25th, 2024 ## Releases: - Apache TomEE 10.0.0-M1 on April 2nd, 2024 - Apache TomEE 9.1.3 on April 15th, 2024 ----------------------------------------- Attachment BU: Report from the Apache Synapse Project [Isuru Udana] ----------------------------------------- Attachment BV: Report from the Apache Tomcat Project [Mladen Turk] ## Description: - A Java Servlet, JavaServer Pages, Java WebSocket and Java Unified Expression language specifications implementation and Jakarta EE equivalents. ## Project Status: - There are no issues requiring board attention at this time ## Membership Data: - Apache Tomcat was founded 2005-05-18 (18 years ago) - There are currently 48 committers and 29 PMC members in this project. - Han Li was added to the PMC on 2023-03-06. - No new committers. Last addition was Han Li on 2022-08-23. - The currently active committers are drawn from a diverse range of companies. ## Project Activity: - Apache Tomcat 11.0.0-M20 (alpha) was released on 2024-05-08. - Apache Tomcat 11.0.0-M19 (alpha) was released on 2024-04-16. - Apache Tomcat 11.0.0-M18 (alpha) was released on 2024-03-14. - Apache Tomcat 10.1.24 was released on 2024-05-13. - Apache Tomcat 10.1.20 was released on 2024-03-25. - Apache Tomcat 9.0.89 was released on 2024-05-07. - Apache Tomcat 9.0.88 was released on 2024-04-16. - Apache Tomcat 9.0.87 was released on 2024-03-14. - Apache Tomcat 8.5.100 was released on 2024-03-25. ## Community Health: - Continued healthy activity across multiple components and responsiveness on both dev and user lists. - Participated in the ApacheCon/Community Over Code in Bratislava in June 2024. - We have organized Security Day EU 2024 on June 6th. The event was by invitation only, and attended by 7 Apache Tomcat PMC members, and five additional guests. The purpose of the meeting was how to improve Apache Tomcat security. More info can be found at https://cwiki.apache.org/confluence/display/TOMCAT/Security+Day+EU+2024 This event used about 1/3 of the security funding Google provided so we intend to run similar events in the future supported with the remaining funding. - We are starting to see discussions on list to follow up on the various topics that were discussed on the Security Day EU 2024. ----------------------------------------- Attachment BW: Report from the Apache TVM Project [Tianqi Chen] ## Description: The mission of Apache TVM is the creation and maintenance of software related to compilation of machine learning models to run on a wide range of hardware platforms ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache TVM was founded 2020-11-17 (4 years ago) There are currently 76 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - Balint Cristian was added as committer on 2024-05-20 - Park Sunghyun was added as committer on 2024-05-30 - Tong Meng was added as committer on 2024-04-09 ## Project Activity: Recent releases: 0.16.0 was released on 2024-06-12. 0.15.0 was released on 2024-03-10. 0.14.0 was released on 2023-11-03. The project continues to bring in new features; highlights include: - Better multiGPU support - Improvements for LLM applications and KV cache management - Better backend support for WebGPU and other emerging platforms. - Supporting latest H100 GPU and FP8 We start to see a lot of developments now centering around new LLM workloads and applications start to arise for deploying these latest models. ## Community Health: The community get contributions from 64 contributors in past quarter, with 200 commit smonthly. We are entering a period of steady state development after the TVM unity transition. Most activities are around stabilizing the new features and existing ones. We also started to see interest in areas like WebGPU and H100 FP8 support. As the field of machine learning and related user community shifts to generative AI workloads, the community also starts to adapt to the latest set of interests and keep up with the changes in the overall landscape of AI/ML. ----------------------------------------- Attachment BX: Report from the Apache UIMA Project [Richard Eckart de Castilho] ----------------------------------------- Attachment BY: Report from the Apache Unomi Project [Serge Huber] ## Description: The mission of Apache Unomi is the creation and maintenance of software related to providing a reference implementation of the OASIS Customer Data Platform specification currently being worked on by the OASIS Context Server Technical Committee ## Project Status: Current project status: Ongoing, low-activity Issues for the board: none ## Membership Data: Apache Unomi was founded 2019-02-20 (5 years ago) There are currently 16 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Taybou on 2021-03-19. - No new committers. Last addition was Francois Gerthoffert on 2022-09-15. ## Project Activity: The activity was rather low recently, it is expected to pickup as the latest work to perform some cleanups and library upgrades is coming to completion. There is also work planned on the support of OpenSearch that is currently starting. ## Community Health: As reflected in the project activity, the community has been less active recently, but as mentioned it is expected to pickup hopefully soon. A proposal for a regular monthly meeting was also proposed which should help activate the community members on a more regular basis. ----------------------------------------- Attachment BZ: Report from the Apache VCL Project [Josh Thompson] ## Description: The mission of the Apache VCL project is to create and maintain of software related to a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources. ## Project Status: Current project status: Ongoing Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache VCL was founded 2012-06-19 (12 years ago) There are currently 10 committers and 8 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Mike Jennings on 2020-08-24. - No new committers. Last addition was Mike Jennings on 2019-01-04. ## Project Activity: We are still working toward our next release. However, things have slowed down somewhat due to one of our core developers taking another job that doesn't utilize VCL. The developer has mostly stepped away from the project, though not to the point of resigning. Other developers have picked up the parts he was working on, but it's caused progress to slow down. ## Community Health: Having progress toward the next release slow down has been somewhat discouraging, but the community is still healthy. ----------------------------------------- Attachment CA: Report from the Apache Wicket Project [Andrea Del Bene] ## Description: The mission of Wicket is the creation and maintenance of software related to Component-based Java Web Application Framework. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Wicket was founded 2007-06-20 (17 years ago) There are currently 33 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Thomas Heigl on 2020-08-14. - No new committers. Last addition was Thomas Heigl on 2020-05-18. ## Project Activity: On the last quarter we released versions 9.18.0 and 10.1.0, this last is the maintenance release for the 10.x branch. Both versions contains a patch for ‘CVE-2024-36522 - Remote code execution via XSLT injection’ which was brought to our attention by the security team. We expect to release a version also for branch 8.x as we still support security fixes for this branch. ## Community Health: Our community is stable and healthy. We are about to vote to invite a long time contributor of Wicket and satellite project WicketStuff, who is already member of Apache Uima. We think he should be a good addition for the team. ----------------------------------------- Attachment CB: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ## Project Status: Current project status: Ongoing/low Issues for the board: None ## Membership Data: Apache Yetus was founded 2015-09-15 (8 years ago) There are currently 12 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Akira Ajisaka on 2018-12-17. - No new committers. Last addition was Akira Ajisaka on 2018-02-06. ## Project Activity: Not much to speak of, other than some discussions on the mailing list. Typical post-release lull that matches the project's cyclic nature. Most of the discussion lately has been about switching from Ubuntu to something else. ## Community Health: dev@yetus.apache.org had a 80% increase in traffic in the past quarter (9 emails compared to 5) ----------------------------------------- Attachment CC: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables the implementation of a variety of primitives and mechanisms that are critical for safety and liveness in distributed settings, e.g., distributed locks, master election, group membership, and configuration. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache ZooKeeper was founded 2010-11-17 (14 years ago) There are currently 32 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - Damien Diederen was added to the PMC on 2024-04-16 - Zili Chen was added to the PMC on 2024-04-16 - No new committers. Last addition was Li Wang on 2023-03-17. ## Project Activity: The most recent releases from March 2024 have been reported already, I'm repeating them here for convenience: - 3.9.2 was released on 2024-03-12. - 3.8.4 was released on 2024-03-05. ## Community Health: It has not been a quarter with a lot of community activity. We intend to assess interest on the next major release 3.10.0 and minor releases of the 3.8 and 3.9 branches, and drive the development accordingly. - dev@zookeeper.apache.org had a 22% decrease in traffic in the past quarter (75 emails compared to 95) - user@zookeeper.apache.org had a 83% increase in traffic in the past quarter (11 emails compared to 6) - 6 issues opened in JIRA, past quarter (-84% change) - 4 issues closed in JIRA, past quarter (-78% change) - 3 commits in the past quarter (-95% change) - 4 code contributors in the past quarter (-78% change) ------------------------------------------------------ End of minutes for the June 19, 2024 board meeting.