The Apache Software Foundation Board of Directors Meeting Minutes December 15, 2021 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:01 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/42eb 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: Bertrand Delacretaz Roy T. Fielding Sharan Foga Justin Mclean Sam Ruby Craig L Russell Sander Striker Sheng Wu Directors Absent: Roman Shaposhnik Executive Officers Present: Myrle Krantz David Nalley Matt Sicker Ruth Suehle Executive Officers Absent: none Guests: Daniel Gruno Dave Fisher Greg Stein Joe Brockmeier Sally Khudairi Shane Curcuru 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of November 17, 2021 See: board_minutes_2021_11_17.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander] December is always one of those months. At least my personal experience is that both too much and too little happens. This year is no different. COVID-19 is still with us, and keeps impacting daily life. In short, life remains interesting. With that in mind I remain impressed with the ability of our community to keep providing software for the public good. B. President [David] From an operations perspective, it's been a relatively quite month as we approach the holiday season and end of the calendar year. Though obviously Infrastructure and M&P have been dealing with their respective facets of security response. I spent some time speaking with our Chairman about supporting the Board Agenda Tool. Following some of the discussion around CVE-2021-44228 I've had a brief conversation with VP, Security around the potential for us adding some paid support staff to help handle the administrivia associated with security processes. It's nothing past some very initial conversations that we've agreed to pick back up after the massive amounts of work subside and folks get to rest a bit. I mention it now to highlight one potential issue which is that Security isn't part of operations, but since volunteer leadership is likely to remain in place, I don't suspect that this is a blocker. Additionally, please see Attachments 1 through 8. C. Treasurer [Myrle] We have completed a draft of the Investment Policy Statement and submitted it to the board for comment. We hope it will be passed, so that the Treasury can make progress on two open issues: * CDARS replacement. * Endowment fund establishment with the $500k restricted donation that we've been carrying on our books since 2018. Similar to the Arrow donation managed by Myrle Krantz, and then later the Cordova donation managed by Craig Russell, Craig McClanahan is currently making Ramp Cards available to the Spark community to help them use a restricted donation targeted at helping the Spark community. We've also received a restricted donation targeted to the Apache D&I community efforts. In the context of the increased volume of restricted donations targeted at specific Apache projects we are currently examining our accounting practices and our technology choices to see if we can improve the processes involved. D. Secretary [Matt] In November, the secretary received 60 ICLAs, 3 CCLAs, and 1 software grant. E. Executive Vice President [Ruth] No additional updates. F. Vice Chair [Shane] No activities this month. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Roy] No report was submitted. B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 10 C. Apache Security Team Project [Mark J. Cox / Craig] See Attachment 11 D. VP of Jakarta EE Relations [Rob Tompkins / Sam] No report was submitted. Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # REEF [striker] A. Apache Airflow Project [Bolke de Bruin / Justin] See Attachment A B. Apache Allura Project [David Philip Brondsema / Sheng] See Attachment B C. Apache Ant Project [Jan Materne / Bertrand] See Attachment C D. Apache Any23 Project [Lewis John McGibbney / Roman] See Attachment D E. Apache Archiva Project [Olivier Lamy / Sander] See Attachment E F. Apache Atlas Project [Madhan Neethiraj / Sharan] See Attachment F G. Apache Axis Project [Robert Lazarski / Justin] See Attachment G H. Apache Bahir Project [Luciano Resende / Craig] See Attachment H I. Apache Beam Project [Kenneth Knowles / Roy] See Attachment I J. Apache Bigtop Project [Kengo Seki / Sam] See Attachment J K. Apache Bloodhound Project [Gary Martin / Sander] No report was submitted. L. Apache BVal Project [Matthew Jason Benson / Bertrand] See Attachment L M. Apache Camel Project [Andrea Cosentino / Sharan] See Attachment M N. Apache Cayenne Project [Michael Ray Gentry / Sheng] See Attachment N O. Apache Chemistry Project [Florian Müller / Roman] See Attachment O P. Apache CloudStack Project [Gabriel Beims Bräscher / Roy] See Attachment P Q. Apache Cocoon Project [Cédric Damioli / Sheng] See Attachment Q R. Apache Commons Project [Gary D. Gregory / Sander] See Attachment R S. Apache Cordova Project [Jesse MacFadyen / Roman] See Attachment S T. Apache CouchDB Project [Jan Lehnardt / Craig] See Attachment T U. Apache cTAKES Project [Pei Chen / Sharan] See Attachment U V. Apache Curator Project [Enrico Olivelli / Justin] See Attachment V W. Apache Daffodil Project [Mike Beckerle / Bertrand] See Attachment W X. Apache DeltaSpike Project [Mark Struberg / Sam] See Attachment X Y. Apache Drill Project [Charles Givre / Sharan] See Attachment Y Z. Apache Druid Project [Gian Merlino / Sheng] See Attachment Z AA. Apache ECharts Project [Wenli Zhang / Craig] See Attachment AA AB. Apache Felix Project [Karl Pauls / Roy] See Attachment AB AC. Apache Flex Project [Olaf Krüger / Bertrand] See Attachment AC AD. Apache Flink Project [Stephan Ewen / Sander] See Attachment AD AE. Apache Gobblin Project [Abhishek Tiwari / Roman] See Attachment AE AF. Apache Gora Project [Kevin Ratnasekera / Sam] See Attachment AF AG. Apache Guacamole Project [Mike Jumper / Justin] See Attachment AG AH. Apache Gump Project [Stefan Bodewig / Sam] See Attachment AH AI. Apache Helix Project [Kishore G / Sander] See Attachment AI AJ. Apache Hive Project [Ashutosh Chauhan / Sheng] No report was submitted. AK. Apache Hudi Project [Vinoth Chandar / Bertrand] See Attachment AK AL. Apache Iceberg Project [Ryan Blue / Roman] See Attachment AL AM. Apache Incubator Project [Justin Mclean] See Attachment AM AN. Apache IoTDB Project [Xiangdong Huang / Roy] See Attachment AN AO. Apache Jackrabbit Project [Marcel Reutegger / Sharan] See Attachment AO AP. Apache Karaf Project [Jean-Baptiste Onofré / Craig] See Attachment AP AQ. Apache Lucene Project [Michael Sokolov / Justin] See Attachment AQ AR. Apache Lucene.Net Project [Shad Storhaug / Sam] See Attachment AR AS. Apache Mnemonic Project [Yanhui Zhao / Roman] See Attachment AS AT. Apache Mynewt Project [Szymon Janc / Justin] See Attachment AT AU. Apache NetBeans Project [Geertjan Wielenga / Sharan] See Attachment AU AV. Apache OFBiz Project [Jacopo Cappellato / Sheng] See Attachment AV AW. Apache Olingo Project [Michael Bolz / Craig] See Attachment AW AX. Apache OODT Project [Imesha Sudasingha / Roy] No report was submitted. AY. Apache OpenNLP Project [Jeff Zemerick / Sander] No report was submitted. AZ. Apache OpenWebBeans Project [Mark Struberg / Bertrand] See Attachment AZ BA. Apache Pig Project [Koji Noguchi / Justin] No report was submitted. BC. Apache Pivot Project [Roger Lee Whitcomb / Sheng] No report was submitted. BD. Apache PLC4X Project [Christofer Dutz / Roy] See Attachment BD BE. Apache Portable Runtime (APR) Project [Nick Kew / Sharan] See Attachment BE BF. Apache Portals Project [David Sean Taylor / Sander] See Attachment BF BG. Apache Pulsar Project [Matteo Merli / Justin] See Attachment BG BI. Apache REEF Project [Sergiy Matusevych / Roman] See Attachment BI BJ. Apache Roller Project [David M. Johnson / Bertrand] See Attachment BJ BK. Apache Royale Project [Piotr Zarzycki / Sheng] See Attachment BK BL. Apache Santuario Project [Colm O hEigeartaigh / Justin] See Attachment BL BM. Apache ServiceMix Project [Krzysztof Sobkowiak / Roy] See Attachment BM BN. Apache Shiro Project [Brian Demers / Sam] See Attachment BN BO. Apache SINGA Project [Wang Wei / Sharan] See Attachment BO BP. Apache Sling Project [Robert Munteanu / Roman] See Attachment BP BQ. Apache SpamAssassin Project [Sidney Markowitz / Bertrand] See Attachment BQ BR. Apache Storm Project [Kishor Patil / Craig] See Attachment BR BS. Apache Submarine Project [Liu Xun / Sander] See Attachment BS BT. Apache Synapse Project [Isuru Udana / Sheng] No report was submitted. BU. Apache Tomcat Project [Mladen Turk / Roy] See Attachment BU BV. Apache TomEE Project [David Blevins / Roman] See Attachment BV BW. Apache TVM Project [Tianqi Chen / Bertrand] See Attachment BW BX. Apache UIMA Project [Richard Eckart de Castilho / Craig] See Attachment BX BY. Apache Unomi Project [Serge Huber / Sharan] See Attachment BY BZ. Apache Usergrid Project [Michael Russo / Justin] See Attachment BZ CA. Apache VCL Project [Josh Thompson / Sam] See Attachment CA CB. Apache Velocity Project [Nathan Bubna / Sander] See Attachment CB CC. Apache Wicket Project [Andrea Del Bene / Sam] See Attachment CC CD. Apache Xerces Project [Michael Glavassevich / Bertrand] See Attachment CD CE. Apache Yetus Project [Allen Wittenauer / Roy] See Attachment CE CF. Apache Zeppelin Project [Lee Moon Soo / Sharan] No report was submitted. CG. Apache ZooKeeper Project [Flavio Paiva Junqueira / Roman] See Attachment CG Committee reports approved as submitted by General Consent. 7. Special Orders A. Decision Regarding 401k Matching and Profit Sharing WHEREAS, the 401k plan adopted by the Foundation, provided to its US employees via ADP TotalSource and Voya, requires a formal end of year decision regarding 401k contribution matching and profit sharing; NOW, THEREFORE, BE IT RESOLVED, that no 401k contribution matching, nor profit sharing, will occur during Plan Year 2021. Special Order 7A, Decision Regarding 401k Matching and Profit Sharing, was approved by Unanimous Vote of the directors present. B. Terminate the Apache Usergrid Project WHEREAS, the Project Management Committee of the Apache Usergrid project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Usergrid project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Usergrid project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Usergrid Project; and be it further RESOLVED, that the office of "Vice President, Apache Usergrid" is hereby terminated; and be it further RESOLVED, that the Apache Usergrid PMC is hereby terminated. Special Order 7B, Terminate the Apache Usergrid Project, was approved by Unanimous Vote of the directors present. C. Investment Policy Statement WHEREAS, the Board of Directors desires to facilitate sound governance of the Foundation's financial assets, and WHEREAS, the Board of Directors desires to to establish the financial structures necessary to maintain an endowment NOW, THEREFORE, BE IT RESOLVED, the investment policy statement in Attachment CH be adopted; and be it further RESOLVED that the Treasurer be charged and entrusted with managing the Foundation's investments in line with the investment policy; and be it further RESOLVED, that the Treasurer be charged with regularly reviewing the investment policy and proposing updates. Special Order 7C, Investment Policy Statement, was approved by Unanimous Vote of the directors present. D. Change the Apache Bahir Project Chair WHEREAS, the Board of Directors heretofore appointed Luciano Resende (lresende) to the office of Vice President, Apache Bahir, and WHEREAS, the Board of Directors is in receipt of the resignation of Luciano Resende from the office of Vice President, Apache Bahir, and WHEREAS, the Project Management Committee of the Apache Bahir project has chosen by vote to recommend João Boto (eskabetxe) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Luciano Resende is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Bahir, and BE IT FURTHER RESOLVED, that João Boto be and hereby is appointed to the office of Vice President, Apache Bahir, 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 Bahir Project Chair, was approved by Unanimous Vote of the directors present. E. Establish the Apache Hop Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a platform for data orchestration. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Hop Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Hop be and hereby is responsible for the creation and maintenance of software related to a platform for data orchestration; and be it further RESOLVED, that the office of "Vice President, Apache Hop" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Hop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Hop Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Hop Project: * Nicolas Adment * Hans Van Akelyen * Dave Campen * Matt Casters * Julian Hyde * Brandon Jackson * Bart Maertens * Francois Papon * Sergio Ramazzina * Kevin Ratnasekera NOW, THEREFORE, BE IT FURTHER RESOLVED, that Bart Maertens be appointed to the office of Vice President, Apache Hop, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Establish the Apache Hop Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Executive Session (22:30 UTC) Discuss officer positions Attendees: Directors, Secretary, Treasurer, President No decisions made by the board during this session. 9. Review Outstanding Action Items * Bertrand: Board Agenda Tool transition to ASF Infra [ Unfinished Business 2021-08-18 ] Status: Requirements doc has been started at https://s.apache.org/qh4y9 * Justin: follow up on BT SIG [ Mynewt 2021-09-15 ] Status: In progress * Roman: reach out to ComDev about alternative communication channels for [ President 2021-10-20 ] Status: * Sharan: follow up about copyright issue [ DataSketches 2021-11-17 ] Status: Thanks very much to Dave Fisher for volunteering to follow up on this as he is on the DataSketches PMC. Feedback is that the copyright comment is actually trademarks and the PMC has been advised to approach trademarks if they need support. https://s.apache.org/60g02 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 23:10 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period November 2021 * ISSUES FOR THE BOARD * OPERATIONS Responded to the following queries, liaising with projects as required: - three requests to use project logos on a website - clarified for a KAFKAwhen we require attribution of our marks and when we require a disclaimer - one request to reference project documentation in a university course - rejected a DCMA notice for multiple reasons - not least of which being we neither own nor control the domain in question - one request to use screenshots from project documentation in a book - one request to use project marks on internal company swag - provided advice to OOZIE regarding acceptable names of projects that support the OOZIE community * REGISTRATIONS OPENOFFICE registrations in China have been renewed. Registration has started for DOLPHINSCHEDULER in the US and China. Continued to work with counsel and BEAM PMC to progress the registration of APACHE BEAM. Counsel continue to progress the update of registered address for registrations. * INFRINGEMENTS Continued to work with PINOT PMC to address potential infringements of their mark. Provided advice to FINERACT regarding potential infringements of their marks. Continued to work with OPENOFFICE and counsel regarding infringement of their marks. Continued to work with FLINK and counsel to address infringements in China. Reported additional infringements for Amazon marketplace seller and responded to various follow-up emails that resulted from the report. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: we are entering our end-of-calendar-year busy season for renewals. We are in the process of renewing 9 Sponsors (2 Gold, 2 Silver, 5 Bronze), and pursuing 23 renewals (5 Platinum, 4 Gold, 3 Silver, and 11 Bronze). Three Platinum, 1 Gold, and 2 Bronze Sponsors have committed to renew, and we are waiting for their approval to proceed with the invoicing process. Of note is attrition with a small handful of SEO-focused Bronze Sponsors who have chosen not to renew in the 2022 sponsorship year, a pattern nearly identical to the previous year. We are awaiting payment from 5 Sponsors (2 Gold, 1 Silver, and 2 Bronze), and received payment from one Silver Sponsor and one Silver Targeted Sponsor. 2) Targeted Sponsors: our activities surrounding Targeted Sponsorships continue to grow, and are fine-tuning our sponsorship conditions and policies as a result. We welcomed a new Silver Targeted Sponsor and are onboarding several new Targeted Sponsors who are donating services towards an array of Apache projects. We are also helping facilitate a donation to benefit ASF Diversity & Inclusion, and help with a possible donation towards Infrastructure support. 3) Sponsor Relations: standard outreach continues, and are preparing end-of-year activities. We worked with Marketing & Publicity to publish a Platinum Sponsor "Success at Apache" post and are also discussing options with three additional Platinum Sponsors to promote their support of the ASF. 4) Event Sponsorship: we await final payment from a few remaining event sponsors. 5) Individual Donations and Corporate Giving: we earned $3,700 in November over 78 donations. We promoted Individual Giving and Corporate Giving programs, including the Giving Tuesday global charitable giving program, and will continue to do so through the end of the calendar year. 6) Administrivia: we are working with the Treasury to evaluate possible CRM options. We continue to work with Accounting on some AR/follow-through issues. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Joe Brockmeier] From a planned publicity perspective, it's been relatively quiet since the last report. From a unplanned perspective we've been fielding a lot of press around the Log4j issue. We continue to field press inquiries and coordinate with the PMC to respond to them. Look for a larger summary and debrief on this in January when the issue is (one hopes) in the rearview. Apache Critical Communication Response Plan ============================================ To that end, I've updated and plan to implement in 2022 a critical response playbook. Ideally for any future security issues or major issues, we'd follow this runbook and track response more officially. The idea here is to do the following: 1) Ensure we're speaking with one voice and issuing the correct information. I believe we've done this so far with the Log4j vulnerability. 2) Take as much weight off the PMC and Apache Security team (or other affected teams if it's not a security issue) by having "canned" responses on the ready and letting the PMC avoid distractions. I think we have room to improve here. Each PMC is different, of course, and some may *want* to be very hands on with press while others may prefer to supply information once and be left to preparing patches, etc. Draft here in Google Docs: https://s.apache.org/rkix5 Budget ======= Planning on dropping the Meltwater subscription. It's ~$10K a year and in my opinion a clipping service is not of that much value to the foundation. Most of its results are, effectively, noise. Haven't finalized the GlobeNewswire/West/Intrado/Notified for 2022 yet for press releases but looking to lock in a smaller package of 20 releases -- if we absolutely have to send out a 21st release we'll be able to do so at their normal rate. But generally not seeing sending over the wire as vital for many of our communications. Published ============= The following items were published on blogs.apache.org - Sponsor Success at Apache: Exploration and Practice of the Apache Way in Tencent https://s.apache.org/258az - Apache Month in Review: October 2021 https://s.apache.org/October2021 Press Releases: we issued no formal announcements during this timeframe Informal Announcements: we published 7 items on the ASF "Foundation" Blog, including 5 Apache News Round-ups and 1 monthly overview, totalling 411 news summaries published to date. We tweeted 27 items to 61.1K followers on Twitter, and posted 19 items to 51K followers on LinkedIn. The ASF’s YouTube channel had 18.2K views, and 10.9K subscribers. Future Announcements: we continue to wait on content from select area leads in order to publish the Q1 FY2022 Report. Media Relations ================= We responded to 4 media queries through November. Note that this does *not* include Log4j or anything past 5 December. That will be tallied in the January report. Highlights include: - Microsoft AI with Spark to “Find and Protect Threatened Snow Leopard Population” https://s.apache.org/s/new - Apache Kafka in the Public Sector - Part 3: Government and Citizen Services https://s.apache.org/i27fb - AWS re:Invent - A Roundup Of ML And AI Announcements https://s.apache.org/jsy7h - Cloud-based Object Storage Pros and Cons For Data Management https://s.apache.org/jwwi0 - Researchers warn of increase in attacks against Zoho software https://s.apache.org/1qspz - Why Everyone Needs to Take the Latest CISA Directive Seriously https://s.apache.org/pzwrq Analyst Relations ==================== We responded to one analyst query during this timeframe. Apache was mentioned in a total of 21 reports by Gartner, Forrester, 451 Research, and IDC. Extra ======= Liaison with ASF Fundraising -- - Published “Sponsor Success at Apache” article on blogs.a.o - Coordinated promotional material development with Central Services for Giving Tuesday PMC Communication ===================== - Supported 3 PMCs in promoting their events - working with a PMC regarding recognizing their community’s contributions to the project ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected, and has no current issues requiring escalation to the President or the Board. Highlights ========== - New announce@infra.a.o with auto-subscription (no opt-out) for all PMC members, and opt-in for all Committers. This will be used to announce changes in infrastructure that could be important to the communities' use/operation of our services. - All TLP websites now redirect to TLS (https). There was some content fetched by software that does not follow redirects (eg. DTDs and schemas) that are carved out from the redirect to https. Finances ======== November expenses are well-above normal due to accumulated staffing expenses that were withheld during FY21, per instruction from the Treasurer and President. These values were included within the FY22 budget, so the one-month spike should not throw off FY22 as a whole. Short Term Priorities ===================== - LDAP changeover to new system (scheduled: Dec 18) - Complete onboarding of new-hire Long Range Priorities ===================== - GitBox v2 is starting some initial testing, but needs to be deployed to migrate off 16.04 General Activity ================ - Working with Operations' attorney to create a Confidentiality Agreement for US employees (historically, this was provided by Virtual, Inc.) - End of year 401k review; a Resolution is before the Board. - Standing up a Jenkins cluster of donated s390 nodes. - Lots of Buildbot work (to 3.2, Windows, etc) - Some impact from the AWS outage, but it eventually cleared. - Gitbox v2 beginning to make progress. - Gradle cache deployed. - Beginning a new Jenkins cluster for HBase, to incorporate some donated build nodes. - Some fine-tuning of NodePing, PD, and StatusPage. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] We are still in a quiet period between events. It is my intent to resume discussion of our 2022 events plan first thing next year. As such, I have nothing to report this month. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== No current events Future Events ============= None Currently Short/Medium Term Priorities ===================== In person events are starting to pop up and TAC is keeping an eye out for suitable events. To be discussed starting this month is foss backstage that is a hybrid event in March. A smaller event such as this might be a good test for TAC under these times. Still to be discussed are additional questions that could/should be added around Covid Passports etc. Mailing List Activity ===================== None Membership ========== No changes to the membership this month. ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas] ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 9: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] It's been an uneventful month. Committee members and others have taken good care of responding to and resolving issues. We have fewer open issues than last month (15). There is nothing that requires board attention. There's been some discussions around Javadoc licensing, if 3rd parties need a NOTICE file and some release policy tweaks. ----------------------------------------- Attachment 11: Report from the Apache Security Team Project [Mark J. Cox] Continued work on incoming security issues, keeping projects reminded of outstanding issues, and general oversight and advice. Stats for Nov 2021: 31 [license confusion] 12 [support request/question not security notification] Security reports: 44 (last months: 36, 47, 48) 6 [site] 3 [shenyu] 2 [druid], [dubbo], [httpd], [shardingsphere], [skywalking], [storm], [tomcat], [trafficcontrol] 1 [airflow], [apisix], [cassandra], [guacamole], [heron], [jspwiki], [kafka], [kylin], [linkis], [logging], [lucene], [mxnet], [nifi], [pdfbox], [shiro], [solr], [subversion], [superset], [trafficserver] In total, as of 1st Dec 2021, we're tracking 89 (last month: 90) open issues across 42 projects, median age 90 (last month: 87) days. 46 of those issues have CVE names assigned. 5 (last month: 4) of these issues, across 3 projects, are older than 365 days. ----------------------------------------- Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins] ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: The mission of Apache Airflow is the creation and maintenance of software related to workflow automation and scheduling that can be used to author and manage data pipelines ## Issues: ## Membership Data: Apache Airflow was founded 2018-12-19 (3 years ago) There are currently 45 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Ephraim Anierobi on 2021-08-31. - No new committers. Last addition was Brent Bovenzi on 2021-08-27. ## Project Activity: Recent releases: Provider packages 2021-11-30 was released on 2021-12-06. 2.2.2 was released on 2021-11-15. Provider packages (Amazon) 2021-11-04 was released on 2021-11-11. Airflow Helm Chart Check 1.3.0 was released on 2021-11-08. Provider packages 2021-10-30 was released on 2021-11-04. 2.2.1 was released on 2021-10-29. 2.2.0 was released on 2021-10-11. Provider packages 2021-10-08 was released on 2021-10-11. Provider packages 2021-09-30 was released on 2021-10-05. Apache Airflow Helm Chart 1.2.0 was released on 2021-09-28. 2.1.4 was released on 2021-09-18. Provider Packages 2021-09-04 was released on 2021-09-08. ## Community Health: - There's quite a lot of interesting discussions going on, those include introducing multi-tenancy or redesigning Airflow’s executors as well as possible drop in support for MySQL. All those discussions show that Apache Airflow is actively used and developed and there are still things that can be improved. - To reward some of Airflow users and contributors we are running an end-of-year campaign to send swags to the most active and creative participants in the campaign. - Community voted a crucial Airflow Improvement Proposals that will have huge impact on future of Airflow: [AIP-42 Dynamic Task Mapping][1] ### Events: The Airflow Summit Steering Committee has started planning 2022 summits for the Airflow community. [1]: https://s.apache.org/od4lx ----------------------------------------- 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" ## Issues: - No issues needing board attention. ## Membership Data: Apache Allura was founded 2014-03-18 (8 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: - Guillermo Cruz was added to the PMC on 2021-11-09 - Guillermo Cruz was added as committer on 2021-11-09 ## Project Activity: - Work on upgrading all our dependencies is progressing - A new contribution is pending review - A few small fixes & improvements have landed - Mailing lists have been pretty quiet aside from ticket updates ## Community Health: - Added a new PMC member, as noted above - Not much end-user interactions this quarter ----------------------------------------- Attachment C: Report from the Apache Ant Project [Jan Materne] ## Description: The mission of Apache Ant is the creation and maintenance of the Ant build system and related software components. It consists of 3 main projects: - Ant - core and libraries (AntLibs) - Ivy - Ant based dependency manager - IvyDE - Eclipse plugin to integrate Ivy into Eclipse Additionally Ant provides several extensions to Ant (antlibs). ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Ant was founded 2002-11-18 (19 years ago) There are currently 29 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quarter: - No new PMC members. Last addition was Magesh Umasankar on 2018-07-06. - No new committers. Last addition was Jaikiran Pai on 2017-06-14. ## Project Activity: Recent releases: Ant 1.10.12 was released on 2021-10-19. Ant 1.10.11 was released on 2021-07-13. Ant 1.9.16 was released on 2021-07-13. AntUnit 1.4.1 was released on 2021-07-07. Ivy 2.5.0 was released on 2019-10-24. ## Community Health: For Ant we feel healthy enough to apply patches, and get a release done. But basically we are in "maintenance mode". There isn't much development. For IvyDE we lack the knowledge of building Eclipse plugins on actual Eclipse versions. We hope to get the build running again so we could update that. As most projects moved to Maven or Gradle, the interest in Ant is decreased and also the will to contribute. Ant is still used in several places, as this "swiss army knife" is a sharp one in some areas. But to sum up: we don't expect to get more contributors, but we'll keep the project alive as long as possible and worthful. ----------------------------------------- Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: The mission of Apache Any23 is the creation and maintenance of software related to automatic crawling, parsing, analyzing, producing, validating and converting RDF (Resource Description Framework) data ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Any23 was founded 2012-08-27 (9 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Hans Brende on 2018-02-25. - No new committers. Last addition was Hans Brende on 2018-02-21. ## Project Activity: The project recently activated Dependabot (https://github.com/dependabot) on the codebase. This is really helping to ensure Any23 dependencies are kept up-to-date. The goal is for the project to make more regular releases. A 2.6 release candidate has been available since 2021-11-12 with two +1 PMC VOTE's and one +1 non-PMC VOTE. We are somewhat struggling to get one more PMC vote and this is holding up the 2.6 release. ## Community Health: A VOTE thread has been underway to invite a long-term community member as PMC. This thread is suffering from the same attention as the 2.6 release candidate thread however. We are struggling to get one more PMC +1 VOTE. ----------------------------------------- Attachment E: Report from the Apache Archiva Project [Olivier Lamy] ## Description: The mission of Archiva is the creation and maintenance of software related to Build Artifact Repository Manager ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Archiva was founded 2008-03-19 (14 years ago) There are currently 21 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Martin Stockhammer on 2017-04-10. - No new committers. Last addition was Martin Stockhammer on 2016-09-22. ## Project Activity: Last release 19th June 2020. Low activity the last months. Focus on updating old dependencies ## Community Health: Small developers community but we still get users questions and bug reports. ----------------------------------------- Attachment F: 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 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Atlas was founded 2017-06-20 (4 years ago) There are currently 44 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16. - No new committers. Last addition was Sidharth Mishra on 2021-04-19. ## Project Activity: - enhanced hook messages to capture hook version and message source - updated quick search to support sorting - added metrics persistence to retrieve historical data - UI: updated term details page to add additional attributes - UI: chart representation of metrics data - UI: implemented session timeout - performance improvement in glossary bulk import - fixes in index health monitor - Dependent component version updates: JanusGraph 0.6.0, Apache Strom 2.3.0, Elastic search 6.8.17, Apache Kafka 2.8.1, netty 4.1.69, Junit 4.13.1, jackson 2.11.0, commons-io 2.11.0, Spring Security 5.4.4 ## Community Health: - dev@atlas.apache.org had a 10% decrease in traffic in the past quarter (798 emails compared to 881) - user@atlas.apache.org had a 45% decrease in traffic in the past quarter (10 emails compared to 18) - 87 issues opened in JIRA, past quarter (3% increase) - 56 issues closed in JIRA, past quarter (-43% change) - 111 commits in the past quarter (-5% change) - 15 code contributors in the past quarter (-34% change) - 7 PRs opened on GitHub, past quarter (no change) - 3 PRs closed on GitHub, past quarter (-50% change) ## Most Recent releases: 2.2.0 was released on 2021-08-17 2.1.0 was released on 2020-07-15 0.8.4 was released on 2019-06-21 ----------------------------------------- Attachment G: 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 (20 years ago). 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 Commiters 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.0 was released on August 1, 2021. - Axis 2/Rampart 1.7.1 was released on July 30, 2017. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Health report: Axis2 Java released 1.8.0 this past August, and a follow up release is planned for the next quarter concerning issues AXIS2-6016 and AXIS2-6009. Apache Rampart is a Java implementation of several WS-Sec* standards. Rampart is also scheduled for a release next quarter, so those users can upgrade to the latest Axis2 version. See RAMPART-449 for the status and release discussion. The Axis project lacks committer growth due to that SOAP and XML have been out of fashion for several years now. We continue to promote our JSON support to reverse the trend, which mirrors what is rapidly growing in our day jobs. 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: 5 ## Axis2 java Jira issues closed in the last 90 days: 1 ----------------------------------------- Attachment H: Report from the Apache Bahir Project [Luciano Resende] ## Description: Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Currently, Bahir provides extensions to multiple distributed analytic platforms, extending their reach with a diversity of streaming connectors and SQL data sources. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Bahir was founded 2016-05-17 (6 years ago) There are currently 40 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was João Boto on 2020-07-09. - No new committers. Last addition was Łukasz Antoniak on 2019-01-21. ## Project Activity: Apache Bahir community continues to see a steady medium flow of contributions enhancing the existing extensions for Apache Flink and more towards the low side on the Apache Spark extensions. And although a lot of discussions, the discussed releases have not been completed yet on both Apache Spark or Apache Flink extensions. ## Community Health: This past quarter has seen a great increase in community involvement with healthy engagement on reviewing new issues and prs. dev@bahir.apache.org had a 120% increase in traffic in the past quarter reviews@bahir.apache.org had a 128% increase in traffic in the past quarter ### Releases Apache Bahir for Apache Spark 2.4.0 released on 2019-09-23 Apache Bahir for Apache Spark 2.3.4 released on 2019-09-23 Apache Bahir for Apache Flink 1.0 released on 2017-05-24 ## Trademark/Branding * No known issues. ## Legal Issues * No known issues. ----------------------------------------- Attachment I: 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. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Beam was founded 2016-12-20 (5 years ago) There are currently 80 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:1. Community changes, past quarter: - No new PMC members. Last addition was Chamikara Madhusanka Jayalath on 2021-01-20. - No new committers. Last addition was Emily Ye on 2021-07-22. ## Project Activity: Releases: - 2.34.0 was released on 2021-11-11 Notable technical developments: - The Beam Java API for inserting SQL into a pipeline is no longer "experimental". This has been available for users for many years, but this represents a declaration of confidence to our users. - New support for `pip install apache-beam[dataframe]` to track the pandas versions that we have compatibility with. - Experimental support for the new BigQuery Storage Read API, which should be a simpler and more efficient choice for many use cases. Detailed technical change log at https://github.com/apache/beam/blob/master/CHANGES.md Notable discussions: - There seems to be consensus to migrate from Jira to GitHub Issues, with the primary goal being familiarity for new and/or casual contributors. The technical effort involved is not yet clear. [issues] - An update to schema-aware transforms, to use this system for even more of Beam. These are transforms that have a known schema for their configuration parameters and also have schemas for their input and output (vs just passing blobs of bytes). The increased development and adoption of this should be good for debugging and performance. [schema] [issues] https://lists.apache.org/thread/q5nbwxqvfkzlz664c4kchzkbj26c3r89 [schema] https://lists.apache.org/thread/8yxt3bo5h6xs4vqhvch7mrpln04sjtqj ## Community Health: Community metrics show nothing remarkable. A typical dip in the later part of the year and otherwise largely stable. ----------------------------------------- Attachment J: Report from the Apache Bigtop Project [Kengo Seki] ## Description: Bigtop is a project for the development of packaging and tests of the Apache Hadoop ecosystem. The primary goal of Bigtop is to build a community around the packaging and interoperability testing of Hadoop-related projects. This includes testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. In short we strive to be for Hadoop what Debian is to Linux. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Bigtop was founded 2012-09-19 (9 years ago) There are currently 40 committers and 30 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Masatake Iwasaki on 2021-03-11. - Luca Toscano was added as committer on 2021-12-07 ## Project Activity: - 3.0.0 was finally released on 2021-10-23. In this release we moved to Hadoop, Hive and Spark 3.x, and upgraded many other components for compatibility. Some new distros were also newly supported. - Definition of 3.1.0 BOM is in discussion on BIGTOP-3605. In addition, we are having a brainstorming about adding cutting-edge software and dropping obsolete features in the dev-ml thread (https://lists.apache.org/thread/bryf46kfbomt4zytgscjgvwvs6cy7mv2). ## Community Health: - Community health is good. Several contributors are actively fixing issues and developing the next release. - 8 code contributors in the past quarter (33% increase) - 22 PRs opened on GitHub, past quarter (-24% change) - 21 PRs closed on GitHub, past quarter (-27% change) - 43 commits in the past quarter (30% increase) ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] ----------------------------------------- Attachment L: Report from the Apache BVal Project [Matthew Jason Benson] ## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: Project statistics tool gives us a negative community health score. ## Membership Data: Apache BVal was founded 2012-02-14 (10 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Being an implementation of a Java Community specification, it is not uncommon for Apache BVal to be in a dormant state for relatively long periods of time. With that in mind, we have recently been arguably less active than usual. Admittedly it would be better if we could collectively devote a bit more time to the project as there is at least one recently demonstrated failure in specification compatibility that has as yet gone unaddressed; at the same time we remain confident that we can continue to keep abreast of any sweeping updates to our target specification. ## Community Health: As noted in the "issues" section, statistics-based estimates of community health are not flattering to the team. If (paraphrasing) "bad code yields good communities" we can at least take the metrics as a backhanded compliment (which is by no means intended to imply that our code has no areas that could benefit from improvement). We are more than willing to consider any suggestions for improving community engagement. ----------------------------------------- Attachment M: 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. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 79 committers and 38 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 James Netherton on 2021-04-12. - No new committers. Last addition was Marat Gubaidullin on 2021-07-29. ## Project Activity: - We released Camel 3.7.6 - We released Camel 3.11.2 - We released Camel 3.11.3 - We released Camel 3.11.4 - We released Camel 3.12.0 - We released Camel 3.13.0 - We released 3.11.0 release: this releases train is the LTS release with 3.7.x. We're going to stop releasing 3.7.x releases and going ahead with two LTS 3.11.x and 3.14.x. - We are going to release 3.14.0 in the Middle of December: this release will be the last supporting Java 8, so we're going to support it for 2 years instead of 1. intermediate development releases. - We released Camel K 1.6.1 - We released Camel K 1.7.0 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing more Kameletes to the provided catalog. The amount of Kamelets is increasing in a really impressive way. - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.3.0 - We released Camel-quarkus 2.4.0 - We released Camel-quarkus 2.5.0 - We are continuing working on the Camel-kafka-connector for basing it on Kamelet concept - 0.11.0 on 21 Sep 2021 - We are going to release 1.0 based on 3.14.0 LTS soon, probably in January. - We added two more projects to the ecosystem - https://github.com/apache/camel-kameleon - https://github.com/apache/camel-karavan ## Community Health: - dev@camel.apache.org had a 45% increase in traffic in the past quarter (501 emails compared to 344): This increase is related to 3.14.x LTS release and migration effort and some camel-k discussion. - issues@camel.apache.org had a 58% increase in traffic in the past quarter (2360 emails compared to 1488): We are working a lot on JIRA to clean up and setup everything related to 3.14.0 release, also we have some issues and discussion around the website. - users@camel.apache.org had a 9% increase in traffic in the past quarter (326 emails compared to 299): the situation is more or less the same of the last quarter, the increase is probably related to users moving from Camel 2.x and 3.x - 212 issues opened in JIRA, past quarter (-42% decrease) and 209 issues closed in JIRA, past quarter (-42% decrease): as reported above, the situation is stable. The activity related to Camel 2 is near to zero and we are focusing on old opened issues. We are getting feedback about new LTS releases, but many of them are coming from other channel like the zulip chat. - 3122 commits in the past quarter (7% decrease) and 119 code contributors in the past quarter (4% decrease): the core Camel team is stabilizing the codebase so there is a little decrease in number of commits, contributions related to documentation and website is increasing. We are much more focusing on giving to the community something stable with 3.14.0 and when it will be released we'll restart to innovate with the next dev releases. - 875 PRs opened on GitHub, past quarter (-7% decrease) and 872 PRs closed on GitHub, past quarter (-8% decrease): the code stabilization and less work on the camel kafka connector side explain the decrease in number of PRs open and closed. Camel-kafka-connector still needs to be aligned to the new LTS with Kamelets support, but in the next quarter we'll release it aligned with the latest LTS. - 210 issues opened on GitHub, past quarter (25% decrease) and 211 issues closed on GitHub, past quarter (22% decrease): It's always related to camel-kamelets repository. There were a lot of issues opened there in the last two quarters. ----------------------------------------- Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry] # Apache Cayenne Board Report, December 2021 ## 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. ## Issues On the June Board Report, Justin Mclean commented: > I notice that your latest source release contains compiled code in the form > of jars and class files. There may be a reason why these are included, but > in general a source releases shouldn't contain jar or class files. It > would be good to review this. This issue has been addressed and there are no known issues requiring board attention at this time. ## Membership Data Apache Cayenne was founded 2006-12-19 (15 years ago). There are currently 23 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Nikita Timofeev on 2017-06-25. - No new committers. Last addition was Arseni Bulatski on 2018-12-10. ## Project Activity Development is focused on Cayenne 4.2. Prior versions are maintenance-only. A vote for Cayenne 4.2B1 is currently underway and release of the first beta is expected by mid-December. - Cayenne 4.0 (stable) - Maintenance only. - Cayenne 4.1 (stable) - Maintenance only. - Cayenne 4.2 (development) - Most development work is focused on this version. ### Releases - Cayenne 4.0.2 on 2019-10-14. - Cayenne 4.1 on 2020-07-21. - Cayenne 4.2.M3 on 2021-03-19. ## Community Health Cayenne is healthy. JIRA, Git, and mailing list (user and development) activity was up over the past quarter. Questions on the mailing list are actively addressed. ----------------------------------------- Attachment O: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Chemistry was founded 2011-02-16 (11 years ago) There are currently 38 committers and 36 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 Laurent Mignon on 2017-09-23. - No new committers. Last addition was Laurent Mignon on 2017-09-20. ## Project Activity: There was no activity in the last three months. Last releases were in 2017. ## Community Health: We have a mature code base. No major development is expected. There hasn't been much activity in the last four years and there is no expectation that this is going to change. ----------------------------------------- Attachment P: Report from the Apache CloudStack Project [Gabriel Beims Bräscher] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage, and networking devices. ## Issues: No issues to report. ## Activity: - The Apache CloudStack project is pleased to announce the LTS maintenance release of CloudStack 4.15.2.0 - The Apache CloudStack project is pleased to announce the new LTS release, CloudStack 4.16.0.0 - The Apache CloudStack project is pleased to announce that the first-ever virtual CloudStack Collaboration Conference gathered a broad audience from users and contributors across the world. It happened on 9th - 12th November 2021. A few numbers regarding the event: 48 talks; 40 speakers; average unique views of 43 per talk; average views per talk of 74 (including replays). - The CloudStack PMC is evaluating a few names to be invited to join the committers. - The CloudStack project is pleased to announce that the participation at the Google Summer of Code 2021 resulted in four successful projects [1,2] by the four students: Apurv, Junxuan, Bikram, and Sangwoo. The mentors were: Pearl, David, Suresh, Bobby, Hari, and Nicolas. [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/GSoC+2021 [2] https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+label%3Agsoc2021 ## Health report: Apropos of the activity report; the project is considered healthy. Here follows some highlights based on the ASF Project Statistics for Apache CloudStack. Data was gathered on December 3rd at the ASF Project Statistics [3]. [3] https://reporter.apache.org/wizard/statistics?cloudstack. These statistics combined indicate that the project is healthy. - According to the apache statistics, the project achieved the Community Health Score (Chi): 9.60 (Super Healthy) - More than 4 emails per day to all mailing lists combined in the past quarter. - New members added to the LDAP committee group within the last six months - New committer(s) invited within the last six months - New releases (4.16.0) in the past 6 months. - Github Statistics: -- PR activity: 227 PRs opened on GitHub, past quarter (-12% change) 227 PRs closed on GitHub, past quarter (-24% change) -- Issues: 144 issues opened on GitHub, past quarter (26% increase) 107 issues closed on GitHub, past quarter (-17% change) -- 562 commits in the past quarter (1% increase) -- 39 code contributors in the past quarter (21% increase) - Mailing lists Statistics: -- dev@cloudstack.apache.org had a 9% decrease in traffic in the past quarter (830 emails compared to 911). -- issues@cloudstack.apache.org had a 43% decrease in traffic in the past quarter (8 emails compared to 14). The issues mailing list has been decreasing consistently over time, mostly due to the fact that we are using GitHub "issues" instead of JIRA. Additionally, users that would report issues to the community via the issues@cloudstack.a.o (or users@cloudstack.a.o) now are creating issues in GitHub, which helps developers and the Release Manager(s) to track milestones and bugs/features to be merged in major or maintenance releases; additionally, issues are linked to the Pull Requests and, consequently, the Commits that fixed them. -- marketing@cloudstack.apache.org had a 7% decrease in traffic in the past quarter (45 emails compared to 48). -- users@cloudstack.apache.org had a 2% increase in traffic in the past quarter (758 emails compared to 736). The users mailing list is stable, even with the decreasing of users reporting issues at this ML. ## Project Composition: - There are currently 128 committers and 52 PMC members in this project. - The Committer-to-PMC ratio is roughly 2:1. PMC changes: - No new PMC member was added since the last report. - Most recently added PMC member: Nicolás Vázquez was added to the PMC on 2021-08-01. Committer base changes: - No new committers were added since the last report. - Most recently added committers: David Jumani, Daniel Augusto Veronezi Salvador, and Pearl Dsilva; added on 2021-07-06. ## Releases: Latest: - 4.16.0.0 was released on 15th November 2021 -- EOL 1st May 2023. - 4.15.2.0 was released on 20th September 2021 -- EOL 1st July 2022. - 4.15.1.0 was released on 5th July 2021 -- EOL 1st July 2022. - 4.15.0.0 was released on 22nd January 2021 -- EOL 1st July 2022. - 4.14.1.0 was released on 4th of March 2021 -- EOL 1st January 2022. Reaching EOL: - 4.14.X.0 will reach EOL on 1st January 2022, it was released on 26th May 2020. ----------------------------------------- Attachment Q: Report from the Apache Cocoon Project [Cédric Damioli] ## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (19 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: Still low activity, no commits, but some discussions on lists. ## Community Health: Interestingly, there was a thread on users list mentioning a possible future release of the 2.2 branch ----------------------------------------- Attachment R: 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 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Commons was founded 2007-06-19 (14 years ago) There are currently 148 committers and 42 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. The last addition was Matt Juntunen on 2021-06-25. - No new committers. The last addition was Peter Lee on 2020-03-13. ## Project Activity: We have released the following components during this reporting period: - CLI-1.5.0 was released on 2021-10-27. - RNG-1.4 was released on 2021-09-13. - GEOMETRY-1.0 was released on 2021-08-21. ## Community Health: The community appears moderately healthy with most of the activity coming in from GitHub in the form of pull requests, specifically 446 PRs opened on GitHub, past quarter (3% increase). We are handling this activity fairly well with 431 PRs closed on GitHub, no change from the past quarter. ----------------------------------------- Attachment S: Report from the Apache Cordova Project [Jesse MacFadyen] ## Status report for the Apache Cordova project - December 2021 ## Description: - A platform for building native mobile applications using HTML, CSS and JavaScript. ## Activity Current work has been around keeping up with recent changes to iOS and Android, our most used platforms, and updating plugins. We continue to work towards reducing technical debt, and 'running the business' We have archived translations of our documentation which was very out of date. Similarily we will be archiving outdated documentation for releases more than 3 years old. Several committers have received test devices purchased with donated funds, the remainder should be done shortly. ## Issues: - There are no issues requiring board attention at this time. ## Health report: Our status dashboard at http://status.cordova.io remain mostly all green - failures are usually due to external service issues that do device testing. Our nightly builds have been extremely stable. ASF Project Statistics gives the project a Community Health Score (Chi): 6.3 ( Healthy ) We continue to see contributions from a small group of dedicated individuals. That said, things remain stable and the project continues to see good traffic. The cordova-cli, the base tool used for creating/building/running gets 125k downloads a week on npm, and has been consistent for the last year. Various core plugins see usage in the 50-80k/wk range. Our primary channel for helping, and hearing from users is via our #slack community, which has ~4k users and continues to be fairly active. ## Membership Data: There are currently 103 committers and 100 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. ### Community changes, past quarter: - No new PMC members. Last addition was Pieter Van Poyer on 2021-04-05 - No new committers. Last addition was Pieter Van Poyer on 2021-04-05 ## Releases: - cordova-create@4.0.0 was released on 2021-12-07. - cordova-plugin-statusbar@6.0.0 was released on 2021-12-01. - cordova-app-hello-world@6.0.0 was released on 2021-10-31. - cordova-eslint@4.0.0 was released on 2021-10-31. - cordova-lib@10.1.0 was released on 2021-10-08. - cordova-android@10.1.1 was released on 2021-09-15. ## Dev mailing list: dev@cordova.apache.org had a 17% decrease in traffic in the past quarter (60 emails compared to 72): ## Github activity: issues@cordova.apache.org had a 20% increase in traffic in the past quarter (2400 emails compared to 1985): Issue close rate of 83% - 132 issues opened on GitHub, past quarter (-15% change) - 110 issues closed on GitHub, past quarter (-14% change) PR close rate of 119% - 227 PRs opened on GitHub, past quarter (33% increase) - 271 PRs closed on GitHub, past quarter (60% increase) Commits - 255 commits in the past quarter (39% increase) - 26 code contributors in the past quarter (30% increase) ----------------------------------------- Attachment T: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: Apache CouchDB software is a document-oriented database that can be queried and indexed in a MapReduce fashion using JavaScript. CouchDB also offers incremental replication with bi-directional conflict detection and resolution. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache CouchDB was founded 2008-11-19 (13 years ago) There are currently 68 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. Community changes, past quarter: - No new PMC members. Last addition was Jonathan Hall on 2020-02-12. - No new committers. Last addition was Balázs Donát Bessenyei on 2021-01-14. ## Project Activity: - released 3.2.0 to acclaim as well as 3.2.1. - extended ownership of convenience windows binaries from one individual contributor to a team that includes entirely new contributors (ongoing). - increased visibility of CouchDB sub-components that might be useful for other Erlang-based projects (as a trojan horse to attract new contributors, and initial reactions are promising). ## Community Health: - notable uptake in unofficial Slack support community including more folks helping out with answering questions. - increase in all around project activity as well. ----------------------------------------- Attachment U: 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 ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache cTAKES was founded 2013-03-19 (8 years ago) There are currently 39 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - There is a discussion for a new committer (https://s.apache.org/k9wq2). - No new committers. Last addition was Peter Abramowitsch on 2020-10-15. - No new PMC members. Last addition was Gandhi Rajan on 2018-07-12. ## Project Activity: - Committee continues to work on the future release (4.x.x or 5.x.x) - Last release was 4.0.0.1 patch on Jan 20 2021 - 4.0.0 was released on Apr 27 2017 - 3.2.2 was released on May 30 2015 ## Community Health: There has been a decrease in the email traffic this quarter. email lists have been quiet, but there was at least one new user with question(s) on mailing lists this quarter. dev@ctakes.apache.org had a 64% decrease in traffic in the past quarter ( 12 emails compared to 33) user@ctakes.apache.org had a 50% decrease in traffic in the past quarter (1 email compared to 2) ----------------------------------------- Attachment V: 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 ## Issues: There are no issues for the board. Not much activity but the community is in good shape, when users have problem we help and possibly guide them to contribute a fix. ## Membership Data: Apache Curator was founded 2013-09-18 (8 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Zili Chen on 2020-08-06. - No new committers. Last addition was Zili Chen on 2020-08-06. ## Project Activity: Recent releases: 5.2.0 was released on 2021-07-26. 5.1.0 was released on 2020-07-03. Apache Curator 5.0.0 was released on 2020-05-28. ## Community Health: During the past 3 month there has been not much activity. We fixed a couple of bugs and we will probably cut a release soon, especially in order to recognize the value of the contributions received by users who had problems and contributed solutions. - dev@curator.apache.org had a 62% decrease in traffic in the past quarter (139 emails compared to 362) - user@curator.apache.org had a 65% decrease in traffic in the past quarter (7 emails compared to 20) - 7 issues opened in JIRA, past quarter (-65% change) - 4 issues closed in JIRA, past quarter (-42% change) - 6 commits in the past quarter (-40% change) - 5 code contributors in the past quarter (-28% change) - 4 PRs opened on GitHub, past quarter (-66% change) - 6 PRs closed on GitHub, past quarter (-33% change) ----------------------------------------- Attachment W: 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 ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Daffodil was founded 2021-02-16 (10 months ago) There are currently 13 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Brandon Sloane on 2021-02-16. - No new committers were added. ## Project Activity: Daffodil VSCode Data Debugger - new repository, we brought in new code base to the project following process, first release of this new tool is in preparation. Daffodil primary library - Release v3.2.0 released on 2021-12-06. This is our second post-incubator release. ## Community Health: A big increase in dev activity from new contributors working on the new Daffodil VSCode Data Debugger. Steady contribution on the main daffodil library as well. ----------------------------------------- Attachment X: Report from the Apache DeltaSpike Project [Mark Struberg] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans outside of a container. - JSF integration, including backporting of JSF 2.2 features for Java EE 6. - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. Testing support is also provided, to allow you to do low level unit testing of your CDI enabled projects. ## Issues: There are no issues requiring board attention at this time. ## Activity We had some discussions about the question if and how to address the move from javax to jakartaee. Apart from that we implemented a few new Config features. ## Health Report Not that much going on, but otoh also not much to worry about. Still people around to fix bugs and review. ## Releases - 1.9.5 was released on 2021-03-10. - 1.9.4 was released on 2020-06-12. - 1.9.3 was released on 2020-02-05. ## Project Composition: - There are currently 35 committers and 19 PMC members in this project. - The Committer-to-PMC ratio is roughly 9:5. ## Community changes, past quarter: - No new PMC members. Last addition was Harald Wellmann on 2016-05-19. - No new committers. Last addition was Christian Beikov on 2019-10-21. ----------------------------------------- Attachment Y: Report from the Apache Drill Project [Charles Givre] ## Description: The mission of Drill is the creation and maintenance of software related to Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage ## Issues: No issues requiring board attention. ## Membership Data: Apache Drill was founded 2014-11-18 (7 years ago) There are currently 59 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Bohdan Kazydub on 2020-01-28. - No new committers. Last addition was Cong Luo on 2021-01-19. ## Project Activity: We are gearing up to release Drill 1.20.0 before the end of the calendar year. Some highlights for Drill 1.20.0 include: * Format plugins for Iceberg Tables, SAS files and a fixed width reader. * New Storage Plugin for Apache Phoenix * Writing capability for JDBC data sources * Update to Parquet V2 * Schema provisioning for JSON and Excel readers Numerous other bug fixes and enhancements. Recent releases: 1.19.0 was released on 2021-06-10. 1.18.0 was released on 2020-09-04. 1.17.0 was released on 2019-12-26. ## Community Health: The Drill community hosted our first meetup in a long time. We had attendees from Germany, China, South Africa, Ukraine and various parts of the US. We will be resuming a monthly cadence for these sessions. dev@drill.apache.org had a 83% increase in traffic in the past quarter (1116 emails compared to 608) issues@drill.apache.org had a 74% increase in traffic in the past quarter (964 emails compared to 553) user@drill.apache.org had a 62% increase in traffic in the past quarter (94 emails compared to 58) 75 issues opened in JIRA, past quarter (78% increase) 70 issues closed in JIRA, past quarter (288% increase) 153 commits in the past quarter (-24% change) 15 code contributors in the past quarter (-16% change) 72 PRs opened on GitHub, past quarter (44% increase) 66 PRs closed on GitHub, past quarter (29% increase) 20 issues opened on GitHub, past quarter (100% increase) 13 issues closed on GitHub, past quarter (333% increase) In addition to the metrics above, the Apache Drill slack channel has 309 members. ----------------------------------------- Attachment Z: Report from the Apache Druid Project [Gian Merlino] ## Description Apache Druid is a high performance real-time analytics database. It is designed for workflows where low-latency query and ingest are the main requirements. It implements ingestion, storage, and querying subsystems. Users interface with Druid through built-in SQL and JSON APIs, as well as third-party applications. Druid has an extensive web of connections with other Apache projects: Calcite for SQL planning, Curator and ZooKeeper for coordination, Kafka and Hadoop as data sources, Avro, ORC, or Parquet as supported data input formats, and DataSketches for scalable approximate algorithms. Druid can also be used as a data source by Superset. ## Issues There are no issues requiring board attention at this time. ## Activity Our last major release was Druid 0.22.0, which contained 400 new features, bug fixes, performance enhancements, documentation improvements, and additional test coverage from 73 contributors. Before that release, we had hoped to sort out whether or not we need IP clearance for the Druid Helm chart. It was moved to the Apache Druid repo from the Helm Charts repo after the latter was deprecated: https://github.com/helm/charts#%EF%B8%8F-deprecation-and-archive-notice However, we were not able to complete this work, so we excluded the Helm chart from the 0.22.0 release. We hope to be able to sort this out for the next release. On November 9 and 10, Druid Summit 2021 ran as a two-day virtual event with 34 sessions and roughly 1,100 attendees. Session recordings are available free of charge at https://druidsummit.org/. Since our last board report, there have been 26 community meetups via groups based in Austin, San Francisco, Philadelphia, Toronto, London, Milan, Madrid, Paris, Bern, São Paulo, Canberra, Brisbane, Seoul, and Bangalore. Dev list activity is down from last quarter, while activity on GitHub is up in terms of both commits and the number of unique contributors. Coupled with the fact that the busiest issues/PRs are receiving substantially more comments than the busiest dev list threads, this suggests that development discussion is generally shifting to GitHub. Meanwhile, our ASF Slack channel, #druid, has continued to grow, and has reached over 1,800 members. ## Recent PMC changes - Currently 32 PMC members. - 2 new PMC members this quarter. - Most recently added PMC members: - Atul Mohan (Oct 26, 2021) - Frank Chen (Oct 26, 2021) ## Recent committer changes - Currently 50 committers. - 1 new committer this quarter. - Most recently added committers: - Agustin Gonzalez Tuchmann (Oct 20, 2021) ## Recent releases - 0.22.0, a major release, on 2021-09-22. - 0.21.0, a major release, on 2021-04-26. - 0.20.2, a security patch release, on 2021-03-29. ## Development activity by the numbers In the last quarter: - 527 commits from 59 contributors - 582 pull requests opened - 524 pull requests merged/closed - 176 issues opened - 60 issues closed ----------------------------------------- Attachment AA: 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 ## Issues: No. ## Membership Data: Apache ECharts was founded 2020-12-16 (a year ago) There are currently 26 committers and 14 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 Houjin Huang on 2020-12-16. - Han Minghao was added as committer on 2021-09-21 ## Project Activity: - We have released two versions since last board meeting, the last of which was on 2021.11.01. - We are working towards the next version 5.3.0, which is expected to be released within a month. ## Community Health: There is a notable increase in the number of emails in our mailing list and most of our users can get feedback from the community in time. ----------------------------------------- Attachment AB: 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. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Felix was founded 2007-03-28 (15 years ago) There are currently 68 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Georg Henzler on 2019-06-10. - No new committers. Last addition was Robert Munteanu on 2020-07-20. ## Project Activity: - Existing implementations have been improved/enhanced based on community feedback. - We released a new framework version (minor fixes). - Released 9 components including framework 7.0.3 (mostly bug fixes/minor improvements). ### Releases - felix-logback-1.0.4 was released on 2021-12-07. - org.apache.felix.framework-7.0.3 was released on 2021-12-06. - org.apache.felix.framework.security-2.8.3 was released on 2021-12-06. - org.apache.felix.main-7.0.3 was released on 2021-12-06. - org.apache.felix.main.distribution-7.0.3 was released on 2021-12-06. - log-1.2.6 was released on 2021-12-04. - configadmin.plugin.interpolation-1.2.2 was released on 2021-10-29. - org.apache.felix.fileinstall-3.7.2 was released on 2021-10-24. - SCR 2.1.30 was released on 2021-09-08. ## Community Health: - Overall the project is in ok health. - Very quiet quarter. - 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. - dev@felix.apache.org had a 9% decrease in traffic in the past quarter (416 emails compared to 456) - users@felix.apache.org had a 35% increase in traffic in the past quarter (27 emails compared to 20) - 22 issues opened in JIRA, past quarter (-21% change) - 27 issues closed in JIRA, past quarter (-18% change) - 22 PRs opened on GitHub, past quarter (10% increase) - 21 PRs closed on GitHub, past quarter (no change) ----------------------------------------- Attachment AC: Report from the Apache Flex Project [Olaf Krüger] ## 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) ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Flex was founded 2012-12-19 (9 years ago) There are currently 68 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 Olaf Krüger on 2017-08-28. - No new committers. Last addition was Greg Dove on 2016-09-07. ## Project Activity: No changes have been made to the Flex framework for a long time and it is unlikely that another release will appear. We maybe should think about archiving the project in 2022. ## Community Health: During the last quarter, there was nearly no mailing list activity at users and dev. ----------------------------------------- Attachment AD: Report from the Apache Flink Project [Stephan Ewen] ## Description: Apache Flink is a distributed system for unified batch- and streaming data processing. Flink consists of a scalable high-performance runtime and many APIs and libraries, including SQL, functional DSLs in Java, Scala, Python, and the Stateful Functions library for event-driven applications. Flink interacts and integrates with several Apache projects in the broader ecosystem of data storage and computing, such as Apache Beam, Kafka, Pulsar, Hadoop, HBase, Cassandra, Calcite, Iceberg, Hudi, and various others. ## Issues: ## Membership Data: PMC changes since the previous report: - Igal Shilman was added to the PMC on 2021-09-29 New committers since previous report: - Yangze Guo was added as committer on 2021-11-11 - Jing Zhang was added as committer on 2021-11-11 - Leonard Xu was added as committer on 2021-11-11 - Fabian Paul was added as committer on 2021-11-14 - Yingjie Cao was added as committer on 2021-11-17 - Ingo Bürk was added as committer on 2021-12-07 - Matthias Pohl was added as committer on 2021-12-07 The newest PMC member is Igal Shilman, joined on September 29th, 2021. The newest committer is Ingo Bürk, joined on December 7th, 2021. There are currently 82 committers and 36 PMC members in this project. ## Releases The following releases were made since the last board report: - Flink 1.14.0 was released on 2021-09-29. - Flink 1.13.3 was released on 2021-10-19. ## Project Activity: - After releasing the big 1.14.0 release in September, the community is working on Flink 1.15. We are currently putting (among other things) effort into connectors, managed tables in SQL, support for consistent stateful upgrades for streaming SQL queries, faster savepoints, as well as improvements to job life cycle management and the ops APIs. - Major upcoming changes for existing users are the deprecation of Java 8 support, as well as making Flink independent of Scala versions (so users can use any Scala version against Flink's Java APIs). - The community has started an effort to move connectors from the current big mono-repo to a separate repository. We believe this has multiple advantages, like lowering the contribution barrier, faster and more stable builds on the core repository, as well as enforcing connector API stability. - We did a public retrospective of the previous release cycle, called "Flink Backwards" (a pun referring to the name of the the Flink Forward conference). That was well received and we plan to do this again for the next release. We also want to explore public status syncs meetings. - There is an ongoing effort to re-define and enhance API stability. We observed that many components that are labeled as 'evolving' are in practice heavily used (and are pre-requisites for certain use cases). The community is discussing better ways to classify APIs as well as guidelines when a APIs should move from 'evolving' to 'stable'. - The Flink Forward EU/US conference took place in a virtual format in October. Flink Forward Asia will take place on January 8-9 in a mixed physical/virtual format. ## Community Health: The activity on mailing lists and JIRA is still high, but lower than the spring and summer spikes. - user@f.a.o is at 1602 mails/quarter - user-zh@f.a.o is at 889 mails/quarter - dev@f.a.o is at 1967 mails/quarter - As usual in the first half of a release cycle, there is quite some activity around major change proposals (FLIPs = Flink Improvement Proposals). - 979 JIRA issues opened, 709 JIRA issues closed. - 877 PRs opened, 752 PRs closed. ----------------------------------------- Attachment AE: Report from the Apache Gobblin Project [Abhishek Tiwari] ## Description: The mission of Apache Gobblin is the creation and maintenance of software related to a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems ## Issues: No issues to report. ## Membership Data: Apache Gobblin was founded 2021-01-19 (a year ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19. - Zihan Li was added as committer on 2021-10-13 ## Project Activity: - Completeness watermark support was added for Apache Iceberg tables - GridFS related cleanup and refactoring was done - Improvement in completion watermark checkpointing - Avro-Hive Conversion utils were refactored - Integration with Helix APIs to add or remove tasks was done - Local mode was created for streaming Kafka jobs to help users - Support for RDBMS backed Job catalogs was added - Several minor improvements like enhanced robustness (retries), better logging, bug fixes, performance improvement (lazy loading) and addition of configuration knobs Last release (v0.15.0) was done on: Dec 10, 2020. Current release (v0.16.0) vote passed, and is being published. ## Community Health: - There have been 49 commits since 1st Sep 2021. - 33 commits have been from non-committers. - We constantly look for consistent contributors to vote them in as Committers and PMC. (Zihan was voted in October) - dev@gobblin.apache.org had 1448 new emails last quarter. ----------------------------------------- Attachment AF: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: - The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key-value stores, document stores, distributed in-memory key-value stores, in-memory data grids, in-memory caches, distributed multi-model stores and hybrid in-memory architectures. Gora also enables analysis of data with extensive Apache Hadoop MapReduce, Apache Spark, Apache Flink, and Apache Pig support. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Gora was founded 2012-01-24 (10 years ago) There are currently 31 committers and 31 PMC members in this project. The Committer-to-PMC ratio is 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-28. ## Project Activity: - We were able to complete GSoC 2021 project successfully and these contributions are still under review from community. - Received contributions from several external contributors during last quarter. - We were able to secure a slot from Outreachy Diversity internship programme. - 0.9 was released on 2019-08-15 and we are currently working on our development drive for next release. Compared to the previous quarters, We couldn't make any significant progress from last report. As we heading to towards holidays, hopefully we will be able to allocate more time on next release pending work. ## Community Health: - We observed the usual traffic that we get on both Github and mailing lists for the past quarter. So nothing significant compared to previous quarters. We are hoping to maintain the level of activity with new internship, project and release work. ----------------------------------------- Attachment AG: Report from the Apache Guacamole Project [Mike Jumper] ## Description: The mission of Apache Guacamole is the creation and maintenance of software related to providing performant, browser-based remote access ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Guacamole was founded 2017-11-14 (4 years ago) There are currently 14 committers and 9 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 Carl Harris on 2017-11-19. - No new committers. Last addition was Luke on 2020-02-07. ## Project Activity: Project development is currently focused on completing the 1.4.0 release, which is expected to be ready by the end of the year. Work remaining for the release appears to be mainly documentation and the usual regression testing. Recent releases: - 1.3.0 was released on 2021-01-01. - 1.2.0 was released on 2020-06-28. - 1.1.0 was released on 2020-01-29. ## Community Health: The community is active and healthy. There has been a marked increase in activity on the user@ mailing list (32% relative to last quarter), and a corresponding increase in the number of code contributors (33%). ----------------------------------------- Attachment AH: Report from the Apache Gump Project [Stefan Bodewig] ## Description: Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and OpenSSL. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Gump was founded 2004-02-18 (18 years ago) There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Mark Thomas on 2014-12-03. - No new committers. Last addition was Konstantin Kolinko on 2015-02-11. ## Project Activity: The Tomcat community is the only one still using Gump actively and the only activity in Gump is around keeping the infrastructure alive and tweaking things for the benefit of Tomcat builds. 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. ----------------------------------------- Attachment AI: Report from the Apache Helix Project [Kishore G] ## Description: The mission of Helix is the creation and maintenance of software related to A cluster management framework for partitioned and replicated distributed resources ## Issues: No Issue needs attention. ## Membership Data: Apache Helix was founded 2013-12-17 (8 years ago) There are currently 24 committers and 18 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Junkai Xue on 2017-07-03. - Neal Sun was added as committer on 2021-10-06 ## Project Activity: 1.0.2 was released on 2021-09-02 0.9.9 was released on 2021-11-21 ## Community Health: dev@helix.apache.org had a 100% increase in traffic in the past quarter 7 code contributors in the past quarter (16% increase) 10 issues closed on GitHub, past quarter ----------------------------------------- Attachment AJ: Report from the Apache Hive Project [Ashutosh Chauhan] ----------------------------------------- Attachment AK: Report from the Apache Hudi Project [Vinoth Chandar] ## Description: The mission of Apache Hudi is the creation and maintenance of software related to providing atomic upserts and incremental data streams on Big Data ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Hudi was founded 2020-05-19 (2 years ago) There are currently 26 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Udit Mehrotra was added to the PMC on 2021-11-16 - Sagar Sumit was added as committer on 2021-11-03 - Y Ethan Guo was added as committer on 2021-11-23 ## Project Activity: Community is currently voting on the 0.10.0 release, which adds a new streaming sink for Apache Kafka Connect, simplified config management, and more. For the first time in open source data lake storage, we have added support for multi-dimensional indexing aka space filling curves as well. We focussed a lot on integrations with other open source projects in the data ecosystem - including a Trino connector, redoing our presto Integration. Hudi is also now integrated into the popular dbt framework for authoring ETL pipelines. We revived our monthly community syncs and weekly office hours, post pandemic. Members of the Hudi community continued to give various talks, presentations around their work. ## Community Health: Our github engagement remains strong and growing. As noted in previous reports as well, users tend to prefer reporting issues there over users list. ----------------------------------------- Attachment AL: Report from the Apache Iceberg Project [Ryan Blue] ## Description: Apache Iceberg is a table format for huge analytic datasets that is designed for high performance and ease of use. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Iceberg was founded 2020-05-19 (2 years ago) There are currently 18 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - Jack Ye was added to the PMC on 2021-11-14 - Russell Spitzer was added to the PMC on 2021-11-13 - No new committers. Last addition was Jack Ye on 2021-07-02. ## Project Activity: 0.12.1 was released on 2021-11-08. The community is also working on the next release, 0.13.0. * A spec for table branching and tagging was written and is nearing completion * Iceberg's documentation is being updated so that multiple versions can be easily maintained and updated. * Delete file compaction was added to the rewrite files action and stored procedure. Additional compaction options are planned. * Sort based compaction was added * Flink and Spark plugins have been refactored so that each version is independent and is compiled against the correct engine version. While this duplicates some code, it makes integrating new features easier and reduces the risk of runtime incompatibilities. * Added support for Flink 1.14.x and Spark 3.2.x * A REST catalog API spec is taking shape. This should standardize an interface for providing a table catalog, similar to the thrift metastore interface used by Hive. * Aliyun OSS support was added as an IO module * The community decided on goals for a 1.0 release, targeted for early next year * Python implementation is making progress ## Community Health: Community metrics show healthy growth. Notably, there were 66 unique contributors this quarter, up from 50 last quarter. Total PRs submitted was more than 750, about 50% more than the 500 last quarter. Similarly, PRs closed also increased to 682 from about 400 last quarter, a 64% increase. The most significant stat is the increase in unique contributors, which signals that more people are interested in the project. This quarter, there were talks featuring Iceberg at AWS re:Invent (where Athena announced support), Trino summit, and community events for PrestoDB, lakeFS, and SF Big Analytics. ----------------------------------------- Attachment AM: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for December 2021 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 38 podlings incubating. In November, podlings executed 7 distinct releases. We added two new IPMC members, and none retired. There was one IP clearance. A couple of new podlings are under discussion, and SeaTunnel has joined the Incubator. There were no graduations last month. A couple of podlings are heading towards graduation in the next few months. This month we were missing reports from Hivemall, Livy, PageSpeed, SDAP, Spot and Training, and they will be asked to report next month. All podlings mentioned have had a history of misisng the occasional report, and most have low levels of activity. Training is discussing possible retirement. Spot has very low activity levels and has missed multiple reports. Since the last roll call only attracted 2 PPMC members, I've requested another roll call and asked them if it is time to consider retirement. Multiple projects were asked to use the correct URL for their KEYS files. A few projects have been using the WIP disclaimer a little too widely, and their releases attracted -1 votes. We usually had a top level project ask for a vote on their release and were unable to help them. In recent times some of the incubator reports have been submitted late and board members have not had adequate time to review them. To improve this situation: - Report generation tools have been updated to be able to produce future report templates - One full year (2022) of report templates have been produced - The dates due for all of 2022 Incubator reports have been published - ISC calendar files have been produced for all of these dates in 2022 As usual, most discussions on the mailing list were around graduations, releases, and new project proposals. ## Community ### New IPMC members: - Xiangdong Huang - Guo William ### People who left the IPMC: - None ## New Podlings - SeaTunnel ## Podlings that failed to report, expected next month ## Graduations - none The board has motions for the following: - Hop ## Releases The following releases entered distribution during the month of November: - Age 0.6.0 - Annotator 0.2.0 - Doris 0.15.0 - Inlong 0.11.0 - Nuttx 10.2.0 - Pegasus 2.3.0 - Sedona 1.1.1 ## IP Clearance - Mvndaemon ## Legal / Trademarks N/A ## Infrastructure N/A ## Miscellaneous N/A ## Table of Contents [AGE](#age) [brpc](#brpc) [Crail](#crail) [Hop](#hop) [Kyuubi](#kyuubi) [Marvin-AI](#marvin-ai) [Nemo](#nemo) [StreamPipes](#streampipes) [Toree](#toree) [Wayang](#wayang) -------------------- ## AGE AGE is a multi-model database that enables graph and relational models built on PostgreSQL. AGE has been incubating since 2020-04-29. ### Three most important unfinished issues to address before graduating: 1.Community Vote for TLP graduation is started on the AGE dev mailing list. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? We have a new PPMC member, four new committers, and new contributors. ### How has the project developed since the last report? The project had two new releases. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2021-11-30 ### When were the last committers or PPMC members elected? 2021-11-02 ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes, PPMC is managing the podling's brand / trademarks. ### Signed-off-by: - [ ] (age) Kevin Ratnasekera Comments: - [X] (age) Von Gosling Comments: More voices come from community, we are activly discussing are we ready for graduation. - [ ] (age) Raphael Bircher Comments: - [X] (age) Felix Cheung Comments: - [X] (age) Juan Pan Comments: I can see more guys joining this community, good signal. - [ ] (age) Suneel Marthi Comments: ### IPMC/Shepherd notes: -------------------- ## brpc brpc is an industrial-grade RPC framework for building reliable and high- performance services. brpc has been incubating since 2018-11-13. ### Three most important unfinished issues to address before graduating: 1. Regular apache release 2. Adding more committer 3. Fix Branding issue ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? we added one new committer named wangwei, he is an active contributor from Vivo Mobile. And we have our offline dinner meeting together on 12/3 in beijing, to get to know each other face2face. ### How has the project developed since the last report? we got our 1.0.0 version released, Since then, we will branch 1.0 out for stable release, and accept bigger feature into trunk. ### 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: 2021-11-30 1.0.0 ### When were the last committers or PPMC members elected? 2021-09-14 Wangwei ### Have your mentors been helpful and responsive? Pan Juan is very helpful, she gave us many intructions. ### Is the PPMC managing the podling's brand / trademarks? I will check it out before next pod report. ### Signed-off-by: - [ ] (brpc) Kevin A. McGrail Comments: - [ ] (brpc) Jean-Baptiste Onofré Comments: - [X] (brpc) Von Gosling Comments: - [X] (brpc) Juan Pan Comments: Congrats, our 1.0.0 release. ### IPMC/Shepherd notes: -------------------- ## Crail Crail is a storage platform for sharing performance critical data in distributed data processing jobs at very high speed. Crail has been incubating since 2017-11-01. ### Three most important unfinished issues to address before graduating: 1.More frequent/steady code contributions 2.New release 3.More committers ### 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? No new committer since last report ### How has the project developed since the last report? Some pending issues were closed. The latest elasticity extensions we are aware of are not yet presented as a PR, unfortunately. ### 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: 2021-05-03 ### When were the last committers or PPMC members elected? 2021-05-16 ### Have your mentors been helpful and responsive? Mentors are helpful and always responsive. ### Is the PPMC managing the podling's brand / trademarks? The PPMC took steps to get one non compliant use of the 'Crail' name on a web page corrected. ### Signed-off-by: - [X] (crail) Julian Hyde Comments: Activity is very low. Crail is discussing ways to increase activity. - [ ] (crail) Luciano Resende Comments: - [X] (crail) Felix Cheung Comments: ### IPMC/Shepherd notes: -------------------- ## Hop Hop is short for the Hop Orchestration Platform. Written completely in Java it aims to provide a wide range of data orchestration tools, including a visual development environment, servers, metadata analysis, auditing services and so on. As a platform, Hop also wants to be a reusable library so that it can be easily reused by other software. Hop has been incubating since 2020-09-24. ### Three most important unfinished issues to address before graduating: 1. the community has [voted](https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k) on graduation and will (re)start the discussion on the incubator mailing list. ### 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? The community is active and growing. Hop has hundreds of followers on each of the social media accounts. The PPMC sees an increased traction around Hop. ### How has the project developed since the last report? Hop 1.0 was released in early October. The project is working towards graduation and continues to work towards Hop 1.1. ### How would you assess the podling's maturity? - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation: community vote passed and resolution accepted - [ ] Other: ### Date of last release: 2021-10-05 ### When were the last committers or PPMC members elected? 2021-07-05 (Dave Campen) ### Have your mentors been helpful and responsive? Julian, Kevin and Francois have always been available when the Hop PPMC needed help or advice. ### Is the PPMC managing the podling's brand / trademarks? No known issues. The Hop project name was approved with [PODLINGNAMESEARCH-191](https://issues.apache.org/jira/browse/PODLINGNAMESEA RCH-191) ### Signed-off-by: - [ ] (hop) Tom Barber Comments: - [X] (hop) Julian Hyde Comments: Hop has approved the graduation resolution. Good luck with graduation! - [ ] (hop) Maximilian Michels Comments: - [X] (hop) Francois Papon Comments: - [ ] (hop) Kevin Ratnasekera Comments: ### IPMC/Shepherd notes: -------------------- ## Kyuubi Kyuubi is a distributed multi-tenant Thrift JDBC/ODBC server for large-scale data management, processing, and analytics, built on top of Apache Spark and designed to support more engines. Kyuubi has been incubating since 2021-06-21. ### Three most important unfinished issues to address before graduating: 1.Gain more active contributors/committers to build a diverse community 2.Make Apache releases regularly and keep the quality for all releases 3.Improve project structure and documentation ### 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? 1. 4 new contributors participate in the community since the last one. There are currently 54 contributors and 9 committers. 2. 22 authors have pushed 89 commits to master and 108 commits to all branches. On master, 395 files have changed and there have been 22,900 additions and 3,545 deletions. 3. Several discussions/bug reports on the GitHub Issues/WeChat groups, etc. 4. Participate in 1 online and 1 offline meetup to share kyuubi ### How has the project developed since the last report? 1. v1.4.0-incubating is in the middle of voting process 2. the community is working on implementation of RESTful API 3. Flink engine support in progress 4. Support cloud native service discovery 5. Support execute scala/spark programing code snippet ### 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: 2021-10-25 ### When were the last committers or PPMC members elected? None ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [X] (kyuubi) Willem Ning Jiang Comments: It's good to see the community is growing. - [ ] (kyuubi) Jeff Zhang Comments: - [ ] (kyuubi) Duo Zhang Comments: - [ ] (kyuubi) Akira Ajisaka Comments: ### IPMC/Shepherd notes: -------------------- ## Marvin-AI Marvin-AI is an open-source artificial intelligence (AI) platform that helps data scientists, prototype and productionalize complex solutions with a scalable, low-latency, language-agnostic, and standardized architecture while simplifies the process of exploration and modeling. Marvin-AI has been incubating since 2018-08-21. ### Three most important unfinished issues to address before graduating: 1. Increase activity from current contributors and community. 2. Push packages of next release to repositories. 3. Release a new architecture. ### 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? Community has discussed new approaches to integrate Apache Marvin-AI to new schedulling softwares like Apache Airflow, Kubeflow Pipelines and Tekton. It can simplify the codebase and make Marvin more useful for many more users. ### How has the project developed since the last report? New functionalities (Minor Airflow integration, CLI capabilities) and preparation to release a new version in progress. ### 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: 2019-07-18 ### When were the last committers or PPMC members elected? Wei Chen added as new PPMC member (2019-06-07). New committer Lucas Cardoso (2021-09-17). ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (marvin-ai) Luciano Resende Comments: - [X] (marvin-ai) William Colen Comments: ### 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. Address a few remaining items in the Apache Project Maturity Model 2. Grow the community 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? - Successfully hosted three GSoC students to contribute to Nemo - New committer added: Hwarim Hyun ### How has the project developed since the last report? - Added stream processing metrics - Added stream processing applications - Added hierarchical aggregation - Explored various stream processing scheduling policies ### 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: 2020-12-07 ### When were the last committers or PPMC members elected? September 28, 2021 ### Have your mentors been helpful and responsive? Our mentors have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? The PPMC manages the podling's brand / trademarks. ### Signed-off-by: - [ ] (nemo) Hyunsik Choi Comments: - [X] (nemo) Byung-Gon Chun Comments: - [ ] (nemo) Jean-Baptiste Onofré Comments: - [X] (nemo) Markus Weimer Comments: It might be time for anothe release. ### IPMC/Shepherd notes: -------------------- ## StreamPipes StreamPipes is a self-service (Industrial) IoT toolbox to enable non- technical users to connect, analyze and explore (Industrial) IoT data streams. StreamPipes has been incubating since 2019-11-11. ### Three most important unfinished issues to address before graduating: 1. Make more releases 2. Complete Maturity assessment 3. Prepare graduation process ### Are there any issues that the IPMC or ASF Board need to be aware of? There are no issues right now. ### How has the community developed since the last report? * Multiple of the contributors that we mentioned in the previous report were elected as committers * We've seen increased discussions on the dev mailing list (159 mails in October, 97 mails in November) and have many fruitful discussions * We received an increased amount of bug reports and questions from users, which shows increased adoption * We've seen a few applied research papers where StreamPipes was used as a basis for digital twin management * An article about StreamPipes in the US Linux magazine which was published in March is now also available online: https://www.linuxpromagazine.com/Issues/2021/244/Apache-StreamPipes/(languag e)/eng-US * Community members held two talks in the ApacheCon IoT track * Number of Twitter followers has increased (last report: 199, currently: 208) * Number of Github stars increased (last report: 255, currently: 274) ### How has the project developed since the last report? * During the reporting period multiple large improvements were developed by the community * A completely renewed data explorer to visualise historic time-series data * Advanced user and role management to handle multiple users and define individual data access * A new stateless authentication system * A testing framework for e2e tests to continually improve the software quality * The community decided to merge the three repositories (incubator-streampipes, incubator-streampipes-extensions, and incubator-streampipes-installer) into one to ease the release process which had previously three release artifacts * Currently preparations for the next release 0.69.0 are performed and we are slowly but steadily nearing towards a 1.0 release ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2021-07-22 ### When were the last committers or PPMC members elected? 2021-12-04: Patrick Philipp 2021-11-30: Hrushikesh Rao 2021-10-20: Stefan Obermeier ### Have your mentors been helpful and responsive? Yes, our mentors are helpful and responsive as usual. ### Is the PPMC managing the podling's brand / trademarks? We are actively managing the brand and did not discover any issues related to incorrect brand use. The new logo is now available in the current development version and the full rebranding will take place right after the next release. ### Signed-off-by: - [X] (streampipes) Christofer Dutz Comments: - [ ] (streampipes) Jean-Baptiste Onofré Comments: - [ ] (streampipes) Julian Feinauer Comments: - [S] (streampipes) Justin Mclean Comments: - [ ] (streampipes) Kenneth Knowles Comments: ### IPMC/Shepherd notes: -------------------- ## Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. Toree has been incubating since 2015-12-02. ### Three most important unfinished issues to address before graduating: 1.Increase active contributors 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Not much, the community has been trying to vote a release without much success. I am starting to think that maybe the best solution might be to try to reboot the podling and see if we can inject more new blood to the project and see if it could make a change. I will think more about this and propose something for the next report. ### How has the project developed since the last report? Very minimum discussions towards the release vote. ### 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: 2020-07-31 ### When were the last committers or PPMC members elected? Kevin Bates was added to the PPMC on 2019-08-14 ### Have your mentors been helpful and responsive? There was nothing requiring mentor intervention on the last quarter. ### Is the PPMC managing the podling's brand / trademarks? No Trademark issues ### Signed-off-by: - [X] (toree) Luciano Resende Comments: - [ ] (toree) Julien Le Dem Comments: - [ ] (toree) Ryan Blue 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. Make sure that every PPMC is able to manage a release 2. Release the first version of Apache Wayang under the umbrella of the Apache Software Foundation 3. We have significant growth (stars / forks at GitHub), but we want to gain more popularity and growth the community further ### Are there any issues that the IPMC or ASF Board need to be aware of? Apache Wayang is doing the first release, and it has many iterations; almost all the -1 votes comes from license issues or related. Many members of the community comment about the lack of documentation and examples in the incubator page in a case like: - set up well the license when you bring pieces of code from another project. - what happens when you bring code from another source. - How need to be the headers if you bring the code from the repository that it said is apache but does not contain headers licenses. - How to need to be the license when you bring a code snippet or similar. - and some another cornet cases that could happen. ### How has the community developed since the last report? The community growth is significant (according to Github), the team around Apache Wayang was present at the BOSS conference ’21 and the Apache @home conference. We also signed an LOI with the TU of Berlin to cooperate with “AGORA-EO: Indexing and Querying Earth from Federated Big Data Archives”. The TU Berlin will add federated image processing to Apache Wayang. ### How has the project developed since the last report? As we had to import and rebrand a running project we needed some time to rework the code base for fitting the ASF standards, which resulted in 8 release candidates. The incubator community spottet the issues we weren’t aware of, which allows us now to present the first release of Apache Wayang without a WIP disclaimer. We have chosen this route to make sure that the project will always fit the standards, even when we had different views. At the end all concerns and issues were solved, thanks to the Sheppards. ### 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: Technology wise the Podling is a productive state, which is also reflected by cooperating with the TU Berlin. We see growing adaption in the market, especially from companies with large data processing pipelines. ### Date of last release: No Release yet. At the moment of this report, the RC9 is under votes. ### When were the last committers or PPMC members elected? 2021-03-05 : Committer ### Have your mentors been helpful and responsive? Yes, the mentors are very responsive and helpful ### Is the PPMC managing the podling's brand / trademarks? No Answer ### Signed-off-by: - [X] (cdutz) Christofer Dutz Comments: The team has done a great amount of work ruling out all issues before the first release. They didn't want to go with the WIP and wanted to get things right ... I liked that. - [ ] (wayang) Lars George Comments: - [ ] (wayang) Bernd Fondermann Comments: - [ ] (wayang) Jean-Baptiste Onofré Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AN: Report from the Apache IoTDB Project [Xiangdong Huang] ## Description: The mission of Apache IoTDB is the creation and maintenance of software related to an IoT native database with high performance for data management and analysis ## Issues: No ## Membership Data: Apache IoTDB was founded 2020-09-16 (a year ago) There are currently 41 committers and 24 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Chao Wang on 2021-06-02. - No new committers. Last addition was Chao Wang on 2021-07-03. ## Project Activity: - IoTDB-0.12.3 was released on 2021-11-18. - The community is discussing about the new architecture of IoTDB's cluster architecture. - v0.13 is in development, and we will introduce new aligned timeseries feature. - the project is introduced in China Open Source conference. - more new contributors are developing IoTDB's ecosystem softwares, and we are trying to discuss with them whether they will donate to the project. - a subproject (iotdb-quality) is voted and approved by IoTDB PMC. ## Community Health: We can see more new contributors joining the community, and the dev@ mailing list traffic increases. However, the Chi of the project decrease, and we will investigate why. ----------------------------------------- Attachment AO: Report from the Apache Jackrabbit Project [Marcel Reutegger] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites 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. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Miroslav Smiljanic on 2020-10-27. - No new committers. Last addition was Miroslav Smiljanic on 2020-10-27. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular maintenance releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.6.22 made available on November 19th. According to planned release schedule of the project, the next feature release for Jackrabbit Oak is long overdue. The majority of Jackrabbit Oak users and committers seems to be using maintenance releases or 3rd party builds created from trunk, reducing the need for new feature releases. The PMC decided to retire the Jackrabbit Oak 1.4 maintenance branch. There will be no more releases from this branch. Users of 1.4.x are encouraged to use 1.40.0 or 1.22.8 instead. 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. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the 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-filevault-3.5.4 was released on 2021-10-05 - jackrabbit-2.21.8 was released on 2021-10-08 - jackrabbit-oak-1.22.9 was released on 2021-10-11 - jackrabbit-filevault-maven-plugin-1.2.2 was released on 2021-10-18 - jackrabbit-2.20.4 was released on 2021-11-06 - jackrabbit-oak-1.8.25 was released on 2021-11-08 - jackrabbit-oak-1.6.22 was released on 2021-11-19 - jackrabbit-filevault-3.5.6 was released on 2021-11-25 ## JIRA activity: - 101 JIRA tickets created in the last 3 months - 89 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: The mission of the Apache Karaf project is the creation and maintenance of open-source software related to a generic platform providing higher level features and services specifically designed for creating OSGi-based servers for distribution at no charge to the public. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Karaf was founded 2010-06-16 (11 years ago) There are currently 31 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2018-11-29. - No new committers. Last addition was Francois Papon on 2018-05-19. ## Project Activity: Karaf runtime 4.2.12 has been released on 2021-09-16. Karaf Decanter 2.8.0 has been released on 2021-09-16. Karaf main branch is now 4.4.x version with OSGi R8 update done. We are now working on Karaf runtime 4.4.0.RC1 and 4.3.4 releases. Vote for 4.3.4 should start very soon. We also did good progress on Karaf 5 PoC, it will be discussed on the mailing list soon. ## Community Health: Karaf runtime 5 has been presented during ApacheCon. We got very positive feedback and interested into Karaf 5. ----------------------------------------- Attachment AQ: Report from the Apache Lucene Project [Michael Sokolov] ## Description: The mission of Lucene is the creation and maintenance of software related to Search engine library ## Issues: There are no issues requiring the board's attention. ## Membership Data: Apache Lucene was founded 2005-01-18 (17 years ago) There are currently 91 committers and 61 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - One new PMC member, Julie Tibshirani, was added on 2021-11-30 - Michael Gibney was added as committer on 2021-10-06 ## Project Activity: Recent releases: * 9.0.0 was released on 2021-12-07, * 8.11.0 was released on 2021-11-16. * 8.10.1 was released on 2021-10-18. * 8.10.0 was released on 2021-09-27. Lucene 9.0 is our first major release in over two years, and the first release since Solr was separated into its own top-level project. ### About the 9.0 release * The 9.0 release will require JDK 11. * The build system has been completely rewritten and modernized for this release. * 9.0 adheres to a more stringent backwards compatibility policy than prior releases, and will be able to read indexes created using 7.x and 8.x. * This marks the end of the 8.x series of feature releases. ### Highlights of new features and optimizations * Support for indexing and searching high-dimensionality numeric vectors * Improvements to language-specific text analysis including three new languages as well as improved stemming, normalization and suggester for several others * Improvements to indexing, sorting and faceting speed for important use cases. * Please see the [Release Notes](https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.0) for more information ## Community Health: We see a healthy trend in metrics indicating volume of participation. There is a slight drop-off (-7%) in number of code contributors, which is most likely due to random variation, but we will want to keep an eye on that to see if it persists since it could indicate a loss of diversity, ----------------------------------------- Attachment AR: Report from the Apache Lucene.Net Project [Shad Storhaug] ## Description: Apache Lucene.NET is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. ## Issues: There are no Board-level issues at this time. ## Membership Data: Apache Lucene.Net was founded 2012-08-15 (9 years ago) There are currently 17 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 9:7. Community changes, past quarter: - No new PMC members. Last addition was Laimonas Simutis on 2020-09-08. - No new committers. Last addition was Ron Clabo on 2021-06-03. ## Project Activity: We are continuing to track down bugs and/or mistranslations from Java, and are uncovering new issues every month. We fixed the randomized seed functionality in the test framework so we can now repeat failures. Although the feature is still experimental, this has resulted in a much quicker resolution time for bugs. The primary development focus has been on migrating to the new J2N APIs that were introduced earlier this year and to track down issues related to test failures and hangs/crashes in the test environment. Recent releases: Apache-Lucene.Net-4.8.0-beta00015 was released on 2021-10-29. Apache-Lucene.Net-4.8.0-beta00014 was released on 2021-03-28. Apache-Lucene.Net-4.8.0-beta00013 was released on 2020-11-16. ## Community Health: We have a large increase in commit and PR activity this quarter, primarily in preparation for our 4.8.0-beta00015 release. We have seen a drop in bug reports for 4.8.0, many of the issues that are being opened by the community are inquiries and not actual bug reports. We have also completed work on some old issues that were first reported as early as 2017. 4 code contributors in the past quarter (no change) GitHub PR activity: 42 PRs opened on GitHub, past quarter (82% increase) 44 PRs closed on GitHub, past quarter (109% increase) GitHub issues: 10 issues opened on GitHub, past quarter (42% increase) 20 issues closed on GitHub, past quarter (566% increase) (previous quarter stats available directly via https://reporter.apache.org/wizard/statistics?lucenenet#githubissues) ----------------------------------------- Attachment AS: Report from the Apache Mnemonic Project [Yanhui Zhao] ## Description: Apache Mnemonic is an open-source Java library for durable object-oriented programming on hybrid storage-class memory(e.g. NVM) space. It comes up with durable object model (DOM) and durable computing model(DCM) and takes full advantages of storage-class memory to simplify the code complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing next generation computing platforms. Mnemonic makes the storing and transmitting of massive linked objects graphs simpler and more efficient. The performance tuning could also be mostly converged to a single point of tuning place if based on Mnemonic to process and analyze linked objects. The programmer is able to focus on the durable object oriented business logic instead of worrying about how to normalize/join, SerDe(un)marshal, cache and store their linked business objects with arbitrary complexity. ## Issues: No issue during this report period ## Membership Data: Apache Mnemonic was founded 2020-11-30 (a year ago) There are currently 21 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Chenyang Li on 2020-11-04. - Chunyong was added as committer on 2021-10-05 We have one new developer starting contributing the project ## Project Activity: We had our 0.16.0 release at Oct 22nd, covering the following achievements 1. Fixing failing test cases and resolving issues related to JDK upgrade. 2. Continuing to remove third-party dependency 3. Proposing and planning for new features With 28 JIRA tickets created, 33 JIRA tickets resolved, and 25 PR merged. Our next release 0.17.0 will be majorly focusing on new feature developments after past releases of bug fixes and stabilities improvement. We planned three new feature candidates (Redis and Apache Flink integration, mnemonic-site migrations) for our 0.17.0 release, design, discussion, and development activities are currently ongoing ## Community Health: The contribution flow has been stable, from issue open, to pr request, to developer activities since our last release. According to the community health report, we had 24 issues opened and 15 PR requestfor the past quarter. New tasks and tickets have been created for 0.17.0 release, with discussions on JIRA regarding implementation details. Our community meetings have has been focusing on ticket reviewing, and discussion on new feature implementation plans. ----------------------------------------- Attachment AT: Report from the Apache Mynewt Project [Szymon Janc] ## Description: Mynewt is a real-time operating system for constrained embedded systems like wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS architectures. The mission of Apache Mynewt is the creation and maintenance of software related to an embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android ## Issues: Bluetooth SIG manufacturer ID for ASF issue is stil not resolved. ## Membership Data: Apache Mynewt was founded 2017-06-21 (4 years ago) There are currently 36 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24. - No new committers. Last addition was Krzysztof Kopyściński on 2021-01-26. ## Project Activity: No new release was made in past quarter. Next release is tentatively planned on early Q1 2022. Community work in several areas including: - improvements in MCU and BSP support - security improvement (ARM TrustZone support) - USB support improvements - BLE stack refactoring for future Bluetooth LE Audio support - Bluetooth Mesh improvements - bug fixes ## Community Health: Mailing list traffic dropped as people tend to discuss more on github or slack. Code wise (commits, PRs, issues) project is back on usual level after summer drop. ----------------------------------------- Attachment AU: 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 ## Issues: Nothing to report at this time. ## Membership Data: Apache NetBeans was founded 2019-04-17 (3 years ago). There are currently 77 committers and 63 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 Sarvesh Kesharwani on 2019-06-06. - No new committers. Last addition was José Contreras on 2021-05-24. ## Project Activity: - Apache NetBeans 12.6 vote result succeeded November 29, 2021. - nb-javac getting closer to being directly included in Apache NetBeans releases. - From next release onwards, whole numbers will be used for release numbers, starting with 13 for the next release. - Many thanks to release manager Neil C. Smith who has brought stability to the recent Apache NetBeans releases by his leadership from start to end of the process. ## Community Health: Activity on dev mailing list has increased while on users mailing list has decreased, reflecting the healthy development that more and more activity is taking place on the dev mailing list since users of Apache projects are by default contributors. - dev@netbeans.apache.org had a 100% increase in traffic in the past quarter (706 emails compared to 353) - users@netbeans.apache.org had a 32% decrease in traffic in the past quarter (303 emails compared to 442) - 284 issues opened in JIRA, past quarter (29% increase) - 136 issues closed in JIRA, past quarter (41% increase) - 74 commits in the past quarter (37% increase) - 222 PRs opened on GitHub, past quarter (19% increase) - 214 PRs closed on GitHub, past quarter (15% increase) ----------------------------------------- Attachment AV: 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. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OFBiz was founded 2006-12-20 (15 years ago) There are currently 55 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Akash Jain on 2021-01-28. - Wiebke Pätzold was added as committer on 2021-10-20 ## Project Activity: In the last quarter the project published the first and the second release from the 18.12 branch: - 18.12.01 was released on 2021-10-28 - 18.12.02 was released on 2021-11-22 With these releases, the 18.12 branch is now the active stable branch and the 17.12 branch is obsolete. In addition to the continued work on the 18.12 line, various bug fixes, refactoring, code cleanups and enhancements have been contributed to the project. The community has planned to create a new stabilization branch in the beginning of 2022; the branch will be named 22.01. ## Community Health: Community health is good and community activity over the last quarter has been on average for our project (the metrics show an increase of activity on all the channels over the past quarter but this is simply because we had a slow quarter during the summer). We have added a new committer and we have some good candidates in our watchlist for committers and PMC members. ----------------------------------------- Attachment AW: Report from the Apache Olingo Project [Michael Bolz] ## Description: The Apache Olingo Project provides server and client implementations of the OASIS OData (Open Data Protocol) specifications. It currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Olingo was founded 2014-03-19 (8 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: [Insert your Recent releases: - 4.8.0 was released on 2020-12-27. - 4.7.1 was released on 2019-12-25. - 4.7.0 was released on 2019-12-04. With release 4.8.0 we continued to have at least one maintenance release per year. The for December planed maintenance releases (2.0.12 and 4.9.0) will be very likely postponed to January (or released in December). ## Community Health: Overall community health is good and activity on the mailing lists in last quarter has increased. The V4 code line is on development also reflected in some discussions on mailing list which results in 9 new JIRA items. Six JIRA item and six PRs could be solved and some commits where done, but with planed release preparation this will increase. Release of V4 version 4.9.0 is planned to be done in December/January containing the latest updates, fixes and improvements. The V2 code line has some resolved JIRA items hence version 2.0.12 release is planned and should be done in December/January too. ----------------------------------------- Attachment AX: Report from the Apache OODT Project [Imesha Sudasingha] ----------------------------------------- Attachment AY: Report from the Apache OpenNLP Project [Jeff Zemerick] ----------------------------------------- Attachment AZ: Report from the Apache OpenWebBeans Project [Mark Struberg] ## Description: Apache OpenWebBeans is an ALv2-licensed implementations of the "Contexts and Dependency Injection for the Java EE platform" specifications which are defined as JSR-299 (CDI-1.0), JSR-346 (CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0). The OWB community also maintains a small server as Apache Meecrowave subproject. Meecrowave bundles latest releases of the ASF projects Tomcat9 + OpenWebBeans + CXF + Johnzon + log4j2. ## Issues: There are no issues requiring board attention at this time. ## Activity: We shipped OWB-2.0.24 and are right now preparing to release 2.0.25. This contains some performance and scanning improvements. There have also been some discussions about how to handle jakartaee CDI-4.0 changes which seem to rather heavily break backward compatibility (which we do not like at all). ## Health All fine, bunch of active people around. ## PMC changes: - Currently 13 PMC members, 20 committers - Last PMC addition was Reinhard Sandtner on 2017-10-09. - Last committer addition was John D. Ament on 2017-10-09. ## Recent Releases - 2.0.24 was released on 2021-12-08. - meecrowave-1.2.12 was released on 2021-08-05. - 2.0.23 was released on 2021-06-06. ## Project Statistics: - 154 mails on the list - 10 issues opened in JIRA - 12 issues closed in JIRA ----------------------------------------- Attachment BA: Report from the Apache Pig Project [Koji Noguchi] ----------------------------------------- Attachment BC: Report from the Apache Pivot Project [Roger Lee Whitcomb] ----------------------------------------- Attachment BD: Report from the Apache PLC4X Project [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. ## Issues: There are currently no issues requiring board attention. I do see a bit of an absence of PMC coverage however regarding things cominig up on the mailinglists (dev and private) ## Membership Data: Apache PLC4X was founded 2019-04-17 (3 years ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - César García was added to the PMC on 2021-10-01 - No new committers. Last addition was Thomas Frost on 2021-05-07. ## Project Activity: After finishing the work for the next release some members of the community have invested a lot of time into a complete refactoring of our codebase for the code-generation. This was needed in order to be able to support more situations needed for new drivers, but also for cleaning up stuff to make it more easily understandable for others. Others have been working on adding very cool new features to the S7 driver as well as working on the CAN-drivers. We had talks at 4 conferences: - ApacheCon @Home (2 Talks) - LF OSS-Summit (1 Talk) - Eclipse Con (1 Talk) - IoT Conference (1 Talk) ## Community Health: We are getting more and more reports of people using plc4x and getting bug reports. That's great. However contributions have been coming in from 11% less individuals compared to the previous quarter. Hopefully, in 2022 we will be able to do in-person events again, to strengthen the sense of community again. I am feeling as we are loosing grip of each other after 2 years of absolutely no in-person events. In the past especially these events have been helping with building the commnunity. ----------------------------------------- Attachment BE: Report from the Apache Portable Runtime (APR) Project [Nick Kew] ## 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. ## Issues: No issues requiring board attention. ## Membership Data: Apache Portable Runtime (APR) was founded 2000-12-01 (21 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 Michael Osipov on 2020-08-29. - No new committers. Last addition was Michael Osipov on 2020-08-29. ## Project Activity: As ever, activity has been low, though there have been several fixes dealing largely with changes to the operating systems supported. It has recently been proposed that remaining vestiges of support for operating systems long-abandoned by their erstwhile vendors (specifically OS/2 and Netware) be cleanly removed, and that is now likely to happen. A new release was mooted in September, but progress on that is currently stalled. ## Community Health: The community remains broadly healthy, but lack of momentum towards a proposed release may raise a question over its vigor. Your humble reporter hopes to push the release if noone else steps up. ----------------------------------------- Attachment BF: Report from the Apache Portals Project [David Sean Taylor] ## Description: Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Issues: ## Membership Data: Apache Portals was founded 2004-02-17 (18 years ago) There are currently 41 committers and 18 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 Neil Griffin on 2017-02-11. - No new committers. Last addition was Ahmed on 2016-08-06. ## Project Activity: A security related release for Apache Pluto is scheduled for next week (the week of December 13th, 2021). A security related release for Apache Jetspeed is scheduled for the December/January/February timeframe. ## Community Health: With two releases in progress, there is a little more activity. The mailing lists are very quiet. ----------------------------------------- Attachment BG: Report from the Apache Pulsar Project [Matteo Merli] ## Description: Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. ## Issues: - There are no issues requiring board attention at this time. ## Project Activity: - 2.8.1 was released on September 10th 2021 - Pulsar Client Go 0.7.0 was released on November 15th 2021 - Pulsar Client Node 1.4.1 was released on October 8th 2021 - We have added a more formal process and guidelines for contributors for adding new features and signficant changes. There were several improvement proposals discussed this quarter, * PIP-111: Add messages produced by Protocol Handler When checking maxMessagePublishBufferSizeInMB * PIP 110: Topic metadata * PIP 108: Add method to help user judge if consumer queue has message PIP * PIP 107: Introduce the chunk message ID PIP * PIP 106: Broker extensions to provide operators of enterprise-wide clusters better control and flexibility * PIP 105: Support pluggable entry filter in Dispatcher - Pulsar has reached 472 contributors on the main Github repo (It was 452 contributors in September 2021) - The first edition on Pulsar Summit EU was on October 6th, and the 2nd edition of Pulsar Summit Asia will be on January 15. - Next release 2.9.0 has went through 4 release candidates and has been finally approved. Release notes and website updates are ongoing, before the official announcement. ## Health report: - There is healthy grow in the community, several users are starting to become contributors to the project and engaging more and more with the community. In this quarter 8 contributors were invited as committers to the project. ## Membership Data: Apache Pulsar was founded 2018-09-18 (3 years ago) There are currently 49 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: Community changes, past quarter: - David Kjerrumgaard was added as committer on 2021-09-30 - Liu Yu was added to the PMC on 2021-11-30 - Michael Marshall was added as committer on 2021-12-02 - Guo Jiwei was added as committer on 2021-10-28 - Marvin Cai was added as committer on 2021-11-14 ## Community Health: - Activity on the mailing lists remains high with a mixture of new users, contributors, and deeper more experienced users and contributors sparking discussion and questions and filing bugs or new features. - users@pulsar.apache.org: - 28% decrease in traffic in the past quarter (67 emails compared to 92) - dev@pulsar.apache.org: - 1% increase in traffic in the past quarter (876 emails compared to 863) ## Slack activity: - 5510 Members (4393 in September 2021) - 223 Active weekly users (252 in September 2021) ## GitHub activity: - 1256 commits in the past quarter (no change) - 113 code contributors in the past quarter (-22% change) - 929 PRs opened on GitHub, past quarter (14% increase) - 865 PRs closed on GitHub, past quarter (13% increase) - 380 issues opened on GitHub, past quarter (-19% change) - 182 issues closed on GitHub, past quarter (-25% change) ----------------------------------------- Attachment BI: Report from the Apache REEF Project [Sergiy Matusevych] ## Description: Apache REEF, or Retainable Evaluator Execution Framework, is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. For example, Microsoft Azure Stream Analytics is built on REEF and Hadoop. ## Issues: All new development of the project has been stopped and we have decided to sunset the project. I am in the process of signing and publishing a farewell release 0.16.1 now. After that we will start the process of moving the project to the attic. ## Membership Data: Apache REEF was founded 2015-11-17 (6 years ago) There are currently 35 committers and 22 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 Doug Service on 2017-09-28. - No new committers. Last addition was Scott Inglis on 2018-09-27. ## Project Activity: There is no new development on the project this quarter, with 0 new issues and PRs opened or closed. I am finishing the process of signing the last release of Apache REEF 0.16.1, and will move the project to the attic. ## Community Health: We have a great network of REEF alumni, but none of us has been working on REEF in the past year. ----------------------------------------- Attachment BJ: Report from the Apache Roller Project [David M. Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat and MySQL, and is known to run on other Java servers and relational databases. The ASF blog site at blogs.apache.org runs on Roller 6.0.1 Tomcat and MySQL. ## Issues: No issues require board attention. ## Membership Data: Apache Roller was founded 2007-02-20 (15 years ago) There are currently 12 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Michael Bien on 2021-05-24. - No new committers. Last addition was Yash Maheshwari on 2021-09-01. ## Project Activity: Our last release was May of 2020 and we have recently discussed a new release to get out some of the many small improvements we have made over the past year. ## Community Health: Roller is a fairly quiet community made up of unsalaried volunteers who have limited time to devote to the project, but we are making progress and are always on the lookout for new committers. ----------------------------------------- Attachment BK: Report from the Apache Royale Project [Piotr Zarzycki] ## Description: Apache Royale implements the principles of Apache Flex to support development of applications designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale improves developer productivity in creating applications to run wherever JavaScript runs, including on browsers, in Apache Cordova applications, on Node, and on other platforms. ## Issues: Concerns were raised over a committer failing to communicate on public lists regarding issues that were created by commits she had made. Said committer did not respond to attempts at private communication either. After some discussion on what this means for the community, the issue was eventually resolved technically by a commit made by a PMC member. There have been no further attempts to address the communication issues, as the consensus was that the impact made by this specific committer was not significant enough to warrant the effort. ## Membership Data: Apache Royale was founded 2017-09-20 (4 years ago) There are currently 20 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Apache Royale 0.9.8 was released on September 2 2021 Community changes, past quarter: - No new PMC members. Last addition was Greg Dove on 2019-10-29. - María José Esteve was added as committer on 2021-11-23 ## Project Activity: We have increased activity of current active committers who provided many fixes for the compiler and UI parts of the Royale framework. One of the committers introduced and ActionScript code formatter. Activity on social media: Our Twitter account has 719 (previously 715) followers. Our Facebook page has 208 (previously 169) likes. Our LinkedIn Group has 159 (previously 156) people. Our StackOVerFlow "apache-royale" tag currently has 62 (previously 62) questions. ## Community Health: We are seeing increased activity on the Royale users@ mailing list with questions regarding some features in Royale. These activities and pull requests leads with adding one of the user as our new committer. ----------------------------------------- Attachment BL: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: The mission of Santuario is the creation and maintenance of software related to XML Security in Java and C++ ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Santuario was founded 2006-06-27 (15 years ago) There are currently 17 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Daniel Kulp on 2018-10-01. - No new committers. Last addition was Daniel Kulp on 2018-10-01. ## Project Activity: It was a busy quarter for the project in terms of releases. Versions 2.2.3 and 2.1.7 of the Java library were released in September, which contained a fix for a CVE (CVE-2021-40690). A new major version of the Java library (2.3.0) was released in November containing some enhancements as well as making some of the settings more secure by default. There was some discussion on the mailing list about getting a 2.4.0 release out early next year, due to the demand for switching to the Jakarta JAXB package names. Versions 2.0.3 and 2.0.4 of the C++ library were also released, which added support for OpenSSL 3.0.0. ## Community Health: Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC. ----------------------------------------- Attachment 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 (14 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: We did monthly bundles releases (for other projects like Camel or Karaf): * bundles-2021.09 * bundles-2021.10 ## Community Health: ServiceMix is still maintained, waiting the "move" to Karaf. Our main focus is on specs and bundles (the runtime is really on Karaf side for now). We will move forward on Karaf "move" on Q1/Q2 2022. ----------------------------------------- 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 ## Issues: We have no issues that require Board assistance at this time. ## Membership Data: Apache Shiro was founded 2010-09-22 (11 years ago) There are currently 13 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Benjamin Marwell on 2020-12-14. - No new committers. Last addition was Benjamin Marwell on 2020-04-23. ## Project Activity: - Shiro released v1.8.0 last quarter (2021-08-26), no release this quarter. - Work is close to finished moving the project's site to an OSS static site generator. - Recent changes include generating more secure hashes as required by the infra team. We had interesting discussions started in slack, e.g. if Apache Shiro should support the Jakarta Security API. Since only little interest was shown by Jakarta core committers and there has not been any user demand, the topic was not brought up on the mailing list. ## Community Health: The overall community health is steady. We observed less issues, probably due to a mature codebase. This resulted in less emails on the dev and user lists. There were also no urgent security issues to solve. Issue notifications had been moved to their own mailing list, which is why we see a further decrease on the dev mailing list. There were occasional questions on the user list which were answered by the PMC members. ----------------------------------------- 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 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache SINGA was founded 2019-10-16 (a year ago) There are currently 22 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 Zhang Zhaoqi on 2020-07-01. ## Project Activity: In the past quarter, the community is fixing some bugs and issues of V3.2, as well as working on the following features/changes: * Adding more example models, e.g., cnn, resnet and datasets, e.g., cifar100 for cifar_distributed_cnn example * Debugging and adding assertion for input tensor data types in opt.py * Adding key information printing/logging, e.g., throughput and communication time, for distributed training * Optimizing printing and logging modules for faster distributed training * Adding singa-easy implementation * Reconstructing the singa webpage page to include project features * Updating the Git web site by deploying it via .asf.yaml * Updating Vietnamese documentations Updating Chinese documentations ## Community Health: According to the statistic, there are increases of email traffic, JIRA activities, Commit activities and Github PR activities, which indicate 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. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Sling was founded 2009-06-17 (12 years ago) There are currently 49 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Angela Schreiber on 2021-03-16. - No new committers. Last addition was Joerg Hoh on 2021-03-03. ## Project Activity: Work continues on various individual modules, with 31 releases for this reporting period. Our sample application, the Sling Starter, was last released on October 23rd 2018 with version 11. Work has resumed for version 12 with the aim to finish the migration to the feature model. ## Community Health: There is a decrease in contributions across the board, from Jira activity (down ~40%) to pull requests (down ~20%). The trend needs to be tracked across a larger interval to see whether this is seasonal or not. ----------------------------------------- Attachment BQ: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for December 2021 SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Status and health report: The project activities, including running our rule update infrastructure and our dev and user mailing lists, are continuing smoothly. Primary focus for development is now targeting version 4.0.0 Releases: The last release was Apache SpamAssassin version 3.4.6 on 12 April 2021. Note that we maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. Committer/PMC changes: Most recent new committer: Paul Stead (pds) 12 September 2018 Most recent new PMC members: Paul Stead (pds) 23 March 2021 ----------------------------------------- Attachment BR: Report from the Apache Storm Project [Kishor Patil] ## Description: The mission of Storm is the creation and maintenance of software related to Distributed, real-time computation system ## Issues: Nothing to report here. ## Membership Data: Apache Storm was founded 2014-09-16 (7 years ago) There are currently 42 committers and 41 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 Bipin Prasad on 2020-11-15. - No new committers. Last addition was Bipin Prasad on 2020-11-16. ## Project Activity: - Apache Storm 2.1.1 Released on 14 Oct 2021. - Apache Storm 2.2.1 Released on 11 Oct 2021. - Apache Storm 1.2.4 Released on 11 Oct 2021. - Apache Storm 2.3.0 Released on 27 Sep 2021. ## Community Health: During last quarter, 2 CVEs were reported and addressed across 4 different versions for the project. With major change to include OCI/docker support included in the 2.3 release. ----------------------------------------- Attachment BS: Report from the Apache Submarine Project [Liu Xun] ## Description: The mission of Apache Submarine is the creation and maintenance of software related to allowing infrastructure engineers and data scientists to build deep learning applications (TensorFlow, PyTorch, etc.) end to end on cluster management platforms (like YARN/K8s) ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Submarine was founded 2019-10-16 (2 years ago) There are currently 29 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Kai-Hsun Chen on 2021-07-27. - Kuan-Hsun Li was added as committer on 2021-11-18 ## Project Activity: Software development activity: - We plan released the release 0.7 on 2021-12-31. - We have added support for Model Serving in our master branch. - We have added support for Model Management in our master branch. - We have added support for k8s operator in our master branch. Meetups and Conferences: - We created the submarine project channel on youtube. - Technical exchange meetings are held twice a week. In the past six months, it has mainly focused on the model online services and K8s operator. ## Community Health: Submission activities have dropped significantly this quarter (-63%). The main reason is that there are many college students among the contributors of the project, and many students went out to participate in off-campus internships or graduations this quarter. The number of contributors has also remained unchanged. There are 21 contributors active this quarter, which is a good number for this project. We are cultivating newly enrolled students to participate in the development of the community, and we are also attracting corporate users to participate in the development of the community. The traffic of the development mailing list increased slightly. The main reason was that we posted the minutes of each meeting to the mail, which attracted many users to participate in the slack channel of the project. The submarine project is now in China, and two large Internet companies and industrial manufacturing companies have begun to use it. We strive to bring the submarine project into the production environment. ----------------------------------------- Attachment BT: Report from the Apache Synapse Project [Isuru Udana] ----------------------------------------- Attachment BU: 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. ## Issues: - There are no issues requiring board attention at this time ## Membership Data: - There are currently 28 PMC members. Igal Sapir was added to the PMC on Mar 18 2019 - There are currently 47 committers. Raymond Augé was added as committer on 2020-07-02 ## Project Activity: Apache Tomcat 10.1.0-M7 is a milestone release and is targeted at Jakarta EE 10. - Apache Tomcat 10.1.0-M7 (alpha) was released on 2021-11-07 - Apache Tomcat 10.0.13 was released on 2021-11-15 - Apache Tomcat 10.0.12 was released on 2021-10-01 - Apache Tomcat 10.0.11 was released on 2021-09-10 - Apache Tomcat 9.0.55 was released on 2021-11-15 - Apache Tomcat 9.0.54 was released on 2021-10-01 - Apache Tomcat 9.0.53 was released on 2021-09-10 - Apache Tomcat 8.5.73 was released on 2021-11-17 - Apache Tomcat 8.5.72 was released on 2021-10-06 - Apache Tomcat 8.5.71 was released on 2021-09-13 ## Community Health: - Continued healthy activity across multiple components and responsiveness on both dev and user lists. - We had a one-full-day Tomcat track at ApacheCon @ Home 2021 and attendance was one of the highest of all the tracks that day (and for the whole conference). There were 7 presentations, 2 presented by non-Tomcat-committers. ## Security: - Detailed status: http://tomcat.apache.org/security.html ## Trademark: - No new trademark issues in the last 2 months and there are currently no outstanding trademark issues that the Apache Tomcat PMC is working on. - Detailed history is available at: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt ----------------------------------------- Attachment BV: 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 List traffic and commits have been somewhat lower in the last quarter compared to the previous quarters which saw large spikes due to Jakarta EE 9.1 certification efforts and build stabilization in TomEE 8. We're expecting to see the predictable uptick in activity in January after the holiday lul. ## Activity Primary points of discussion over the last quarter has been how to move TomEE 9 to final and if our bytecode modification approach is sustainable. Apache TomEE 9.0 M7 was released as certified in May of 2021. This implements the javax to jakarta namespace switch through the use of bytecode modification tools: Eclipse Transformer & TomEE Patch Plugin. While this did help us work on pursuing Jakarta EE compliance in both TomEE 8 and TomEE 9 in parallel, it does have limitations we'd like to resolve before moving TomEE 9.0 to final release. The bytecode modification approach is good for transforming a single zip or a jar with no maven dependencies. However, in situations where Maven is used to resolve dependencies transitively, the simply aren't good tools or attractive techniques that can upgrade the old javax dependencies in all the poms across a large codebase. The compromise the project is considering is to move the main branch of TomEE from 8 to 9, do the javax-to-jakarta transformation in java source and Maven pom.xml files, then only use bytecode modification for external dependencies. The cost of this approach is now not only will updates to TomEE 8 not also be reflected in 9 automatically, but merging code changes between 8 and 9 largely impossible due to the breaking namespace change. It does, however, appear to be the least costly approach given the bytecode modification restrictions and impact on the developer experience. A separate discussion was started on forming some clear policy similar to Tomcat's on which branches are maintained and will receive CVE patches. This is likely to be influenced by the pending decision to branch TomEE 9 and do the breaking javax-to-jakarta namespace change in source as backporting will often be impossible, increasing the cost of maintaining older branches. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE Patch Plugin 0.7 on October 20th, 2021 ----------------------------------------- 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 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache TVM was founded 2020-11-17 (a year ago) There are currently 47 committers and 20 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Andrew Reusch was added to the PMC on 2021-11-21 - Chris Sidebottom was added as committer on 2021-11-23 There are also ongoing nominations. ## Project Activity: Last release: 0.8.0 was released on 2021-11-25. The community works very hard to complete the 0.8.0 release. There are a lot of active development activities over the past quarter. Including, but not limited to: - Better TE, TIR, TVMScript support - More frontends (Paddle paddle) - Stablizing AutoScheduler - Stablizing Target system - TensorIR and meta-schedule support - TVMC and microTVM improvements - Improved Vulkan backend ## Community Health: The community has been receiving healthy contributions. Monthly about 70 authors contributing 150 commits. The community RFC process also starts to pick momentum, receiving RFCs from various contributors. We will hold the annual community conference TVMCon next week. This year we have one day tutorial and two days of talks with broad participation from both industry and academia. ----------------------------------------- Attachment BX: Report from the Apache UIMA Project [Richard Eckart de Castilho] ## Description: Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. The software provides frameworks, tools and annotators, facilitating the analysis of unstructured content such as text, audio and video. ## Issues: No Board level issues at this time. ## Membership Data: Apache UIMA was founded 2010-03-17 (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 Viorel Morari on 2019-11-19. - No new committers. Last addition was Viorel Morari on 2018-09-20. ## Project Activity: No releases in this reporting period. A uimaFIT 2.6.0 RC1 was already up for voting but cancelled due to a bug having been discovered. Releases of uimaFIT 2.6.0 and UIMA Java SDK 3.2.1 expected for the next reporting period. Inclusion of the new JSON format hinted at in the last report scheduled for UIMA Java SDK 3.3.0. ## Community Health: The community continues to be moderately active. Activity is shifting from the users mailing list more towards GitHub PRs and StackOverflow though. ----------------------------------------- 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 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Unomi was founded 2019-02-20 (3 years ago) There are currently 14 committers and 7 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Taybou on 2021-03-19. - No new committers. Last addition was Anatol Sialitski on 2021-01-29. ## Project Activity: The project just had it's first meetup (online) and it was quite a success, with over 50 registrations and over 30 participants. Not only did the project update the community on its status but users also presented their work with the project and we received very good feedback on both the project and the event. Unomi is also working hard on the next release (1.6.0) that will feature bug fixes, security improvements and improvements such as the support for Groovy actions. The next major version (2.0) is also on an aggressive schedule and is targeted for early 2022. ## Community Health: Activity is a bit lower on Slack but it is still quite regular and there are still a lot of people in the channel (151). Community contributions are however quite active and a lot of PRs are being merged into both active branches. Traffic on the mailing lists is still low, but I think this is simply because people prefer using Slack. Of course, all major decisions and discussions only happen on mailing lists as they should :) Here are some metrics: - Number of members in #unomi slack channel: 151 - dev@unomi.apache.org had a 40% increase in traffic in the past quarter (448 emails compared to 318) - 28 issues opened in JIRA, past quarter (75% increase) - 25 issues closed in JIRA, past quarter (25% increase) - 104 commits in the past quarter (28% increase) - 10 code contributors in the past quarter (25% increase) - 32 PRs opened on GitHub, past quarter (33% increase) - 39 PRs closed on GitHub, past quarter (50% increase) ----------------------------------------- Attachment BZ: Report from the Apache Usergrid Project [Michael Russo] ## Description: Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database (Cassandra), a query engine (ElasticSearch), and application layer and client tier with SDKs for developers. ## Issues: The PMC has voted to move Usergrid to the Attic. https://lists.apache.org/thread/v2ovg7tv5g6pbzm1g0j89w6bsy8b3n8q ## Membership Data: Apache Usergrid was founded 2015-08-18 (6 years ago) There are currently 27 committers and 24 PMC members in this project. The Committer-to-PMC ratio is 9:8. Community changes, past quarter: - No new PMC members. Last addition was Mike Dunker on 2016-01-18. - No new committers. Last addition was Keyur Karnik on 2019-03-18. ## Project Activity: The PMC has voted to move Usergrid to the Attic. https://lists.apache.org/thread/v2ovg7tv5g6pbzm1g0j89w6bsy8b3n8q ## Community Health: The PMC has voted to move Usergrid to the Attic. https://lists.apache.org/thread/v2ovg7tv5g6pbzm1g0j89w6bsy8b3n8q ----------------------------------------- Attachment CA: Report from the Apache VCL Project [Josh Thompson] ## Description: The mission of the Apache VCL project is to create and maintain of software related to a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache VCL was founded 2012-06-19 (9 years ago) There are currently 10 committers and 8 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Mike Jennings on 2020-08-24. - No new committers. Last addition was Mike Jennings on 2019-01-04. ## Project Activity: - Last release: 2019-07-25 - Since the last board report, there has been some activity on the user list to provide support for users of VCL. ## Community Health: Nothing has changed here - VCL continues to be a small but functioning community. We still have committers, PMC members, and users. I can't speak for other community members, but the PMC members have all been pretty heavily loaded supporting remote computing (VCL's primary purpose) during the pandemic to the point that it has been difficult to make time to work toward a new release. ----------------------------------------- Attachment CB: Report from the Apache Velocity Project [Nathan Bubna] ## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: One of the developers has been doing some work on Tools. There's a contributor PR for Engine under consideration, a few other Engine fixes have been accepted. Another contributor created a Prettier formatter. ## Community Health: Things are slow, and we have a limited number of active committers, but it's enough to keep things moving and respond to contributors and issues (albeit slowly). ----------------------------------------- Attachment CC: Report from the Apache Wicket Project [Andrea Del Bene] ## Description: The mission of Wicket is the creation and maintenance of software related to Component-based Java Web Application Framework. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Wicket was founded 2007-06-20 (14 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: We had three new releases for our stable branch 9.x: 9.5.0, 9.6.0 and 9.7.0. No release for branch 8.x (based on Java 1.8) has been released this quarter, but this comes as no surprise as more and more users and projects have moved to newer Java LTS version (mainly Java 11). In the meantime we started to test our main branch with the early access release of Java 18 as part of our effort for the OpenJDK Quality Outreach program: https://wiki.openjdk.java.net/display/quality/Quality+Outreach ## Community Health: Community is healthy and stable, much like download statistics. Nothing in particular to report this quarter. ----------------------------------------- Attachment CD: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J There was a bit of an uptick of activity, mostly around XML Schema 1.1 compliance and maintenance of a dependency (XPath 2.0 processor) that is currently being hosted outside of the ASF. Some minor fixes and improvements were also committed. The potential security issue mentioned in the previous report still requires verification on whether it affects Apache Xerces. Mailing list traffic has been low; roughly 40+ posts on the j-dev and j-users lists since the beginning of August 2021. No new releases since the previous report. The latest release is Xerces-J 2.12.1 (January 11th, 2020). Xerces-C Multiple JIRA issues were addressed and resolved with pull requests merged into the GitHub repository. Many of the fixes were contributed by the same individual from the community; potentially someone who should be considered to become a committer. There was a brief discussion on the development mailing list about having a Xerces-C 3.2.4 to roll up recent fixes. Mailing list traffic has been increasing; roughly 140+ posts on the c-dev and c-users lists since the beginning of August 2021. No new releases since the previous report. The latest release is Xerces-C 3.2.3 (April 10th, 2020). Xerces-P Nothing in particular to report. There was no development activity over the reporting period. XML Commons Other than cleaning up spam comments/isuses in JIRA there was no other activity. Committer / PMC Changes The most recent committers were added in April 2017 (Xerces-C) and May 2017 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. Two committers have committed changes to SVN and GitHub since August 2021. ----------------------------------------- Attachment CE: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Yetus was founded 2015-09-15 (6 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: Quite a bit of work has been done to prepare for the next release. Barring anything showing up in some internal tests that aw@ is doing and one open doc issue, will likely start the process in the next week or so. One of the biggest changes in this upcoming release may be of interest to other projects. We have moved to GitHub Container Registry for the convience container infrastructure. This change was necessitated to allow us to build both amd64 and arm64 with a minimal of fuss using the multiplatform feature of docker's buildx. This means that with the next release, our containers are now native on Apple M1 and other ARM platforms. The 'docker pull' command knows which platform to pull automatically so user experience is great. Still lingering questions about how to handle the eventual JDK 8 EOL but privately one contributor has mentioned wanting to look at reworking the parts that won't work with JDK9+. For now, keeping those bits in and will need to be reconsidered in a few months. Recent releases: * 0.13.0 was released on 2020-11-27. * 0.12.0 was released on 2020-04-13. * 0.11.1 was released on 2019-11-05. ## Community Health: * 30 issues opened in JIRA, past quarter (328% increase) * 43 issues closed in JIRA, past quarter (4200% increase) * 47 commits in the past quarter (4600% increase) * 3 code contributors in the past quarter (200% increase) * 29 PRs opened on GitHub, past quarter (1350% increase) * 30 PRs closed on GitHub, past quarter (2900% increase) ----------------------------------------- Attachment CF: Report from the Apache Zeppelin Project [Lee Moon Soo] ----------------------------------------- Attachment CG: 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. ## Issues: No issue requires board attention. ## Membership Data: Apache ZooKeeper was founded 2010-11-17 (11 years ago) There are currently 30 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Enrico Olivelli on 2020-01-15. - No new committers. Last addition was Ling Mao on 2021-01-16. ## Project Activity: There has been no new release in the last period. It is clear that the community activity has dropped and the PMC will discuss how to proceed about it. ## Community Health: - dev@zookeeper.apache.org had a 24% decrease in traffic in the past quarter (74 emails compared to 97) - notifications@zookeeper.apache.org had a 32% decrease in traffic in the past quarter (284 emails compared to 417) - 45 issues opened in JIRA, past quarter (-26% change) - 14 issues closed in JIRA, past quarter (-60% change) - 31 commits in the past quarter (-36% change) - 16 code contributors in the past quarter (-20% change) - 30 PRs opened on GitHub, past quarter (-28% change) - 29 PRs closed on GitHub, past quarter (-30% change) ----------------------------------------- Attachment CH: Investment Policy Statement ORGANIZATION Established in 1999, The Apache Software Foundation ("ASF") is a United States 501(c)(3) charitable organization, funded by individual donations and corporate sponsors. Organizational affairs of the ASF are managed following the bylaws (https://www.apache.org/foundation/bylaws.html). PURPOSE This statement establishes policies, guidelines, and procedures related to all investable assets held by The ASF. In doing so the policy: * defines the duties and responsibilities of all parties involved in the management of investable funds * identifies the objectives, risk profiles, and benchmarks for each purpose-driven investment pool * outlines policies and procedures relative to the expenditure of institutional funds * serves to assist the Board in effectively supervising, monitoring, and evaluating the investment of The ASF's management of the organizations’ investments. ROLES AND RESPONSIBILITIES Board of Directors: The Board of Directors has a direct oversight role regarding all decisions that impact The Apache Software Foundation’s investable assets. The Board must ensure that appropriate policies governing the management of the portfolio(s) are in place and that these policies are being effectively implemented. In doing so, the Board sets and approves the Investment Policy Statement and delegates responsibility for the management of these funds to the Treasurer. Based on the advice and recommendations of the Treasurer, the Board shall: * adopt an investment strategy that addresses the organization's operating needs while reflecting the long-term risk-adjusted return objectives of the endowment. Treasurer: The Treasurer shall not be held accountable for portfolio performance. Instead, the Treasurer is responsible for the development, recommendation, implementation and maintenance of all policies relative to The ASF's investable funds and shall: * present investment strategy recommendations to the Board. These recommendations should address short and long-term objectives, liquidity needs and diversification * recommend the retention and/or dismissal of an Investment Advisor and/or other outside professionals * meet with the Investment Advisor on a regular basis (quarterly / semi-annually) to evaluate and assess compliance with investment guidelines, performance, outlook and investment strategies; monitor asset allocation and rebalance assets * on an annual basis, evaluate whether this policy, investment activities, risk management controls and processes remain consistent with set goals and objectives The Treasurer and Assistant Treasurers shall also be responsible for the day-to-day administration and implementation of policies established by the Board and/or the Treasurer concerning the management of investable assets. Specifically, the Treasurer shall: * serve as the primary liaison between the Investment Advisor and/or other outside professionals that may be retained to assist in the management of such funds * oversee the day-to-day operational activities subject to policies established by the Board * contract with any necessary outside service providers, such as: Investment Advisors, investment managers, banks and/or trust companies etc. * ensure that service providers adhere to the terms and conditions of their contracts; have no material conflicts of interest with the interests of The ASF; and ensure that performance monitoring is sufficient to provide the Treasurer with timely, accurate and useful information * comply with official accounting and auditing guidelines regarding due diligence and ongoing monitoring of investments * prepare and issue periodic status reports to the Board Investment Advisor: The Investment Advisor is responsible for all aspects of managing and overseeing the portfolio. On an ongoing basis the Investment Advisor will: * monitor the asset allocation to promote diversification in the portfolio * implement an unbiased, open-architecture approach to manager/security selection * provide the Treasurer with quarterly performance reports * assist the Treasurer with periodic reviews of this Investment Policy including an assessment of the current asset allocation and investment objectives * supply the Treasurer with other reports or information as requested * attend meetings with the Treasurer and/or Board concerning performance results, economic outlook, efficacy of investment strategy, organization changes (if any), and any other pertinent matters identified by the Board, and/or the Investment Advisor. Custodian: The Custodian will be responsible for the safekeeping of securities held by The ASF. Additional responsibilities include the collection of dividend and interest payments, redemption of maturing securities, and receipt of delivery following purchases or sales. The Custodian will provide accounting of all assets owned, purchased, or sold, and the movement of assets into or out of The ASF's account(s). Additional specialists, such as attorneys, auditors, actuaries, and others may be employed by the Board to assist in meeting its responsibilities and obligations to administer portfolio assets prudently. FIDUCIARY RESPONSIBILITY In seeking to attain the investment objectives set forth in this IPS, members of the Board, the Treasurer, Assistant Treasurer, the Investment Advisor, and all other persons acting as fiduciaries, shall exercise prudence and appropriate care in accordance with the Uniform Prudent Management of Institutional Funds Act (UPMIFA). All investment actions and decisions must be made solely in the interest of The ASF and fiduciaries must provide full and fair disclosure to the Board regarding all material facts pertaining to any potential conflicts of interest. When making any decision relative to the expenditure of donated funds, each of the following factors must be considered, and properly documented, in the minutes or other records of the applicable decision-making body: * general economic conditions; * possible effect of inflation or deflation; * expected tax consequences, if any, of investment decisions or strategies; * the role that each investment or course of action plays within the overall investment portfolio of the fund; * expected total return from the income and appreciation of investments; * other resources of the organization; * the needs of the organization and the fund to make distributions and preserve capital; * an asset’s special relationship or special value, if any, to the organization’s purposes. PROHIBITED INVESTMENTS The following investments and investment activities are prohibited: * Private placements * Letter stock * Derivatives (excluding mutual funds which may buy or sell derivatives for the purposes of managing portfolio risk) * Commodity contracts * Short sales * Margin transactions OPERATING ACCOUNT The ASF has established a demand deposit account to support its day-to-day operating needs. The ASF will seek to maintain a target balance of 50%-75% of the yearly expenses contained in the most recent board-approved budget in this account to accommodate operating and other expenses. OPERATING RESERVE The ASF has additional reserves set aside to serve as a separate Operating Reserve. This portfolio is meant to meet the expenses occurring as a result of unanticipated fundraising shortfalls or unanticipated board-approved expenses, and to improve the return on funds held in the operating account. The objectives of this portfolio are in order of priority: 1.) Preservation of Principal 2.) Liquidity 3.) Rate of Return The portfolio must be well diversified and consist of fixed-income securities rated "A" or better. ENDOWMENT The ASF's Endowment is meant to support the organization in perpetuity and thus has a longer time horizon and a substantially different risk profile than the Operating Reserve. In all instances, donor intent shall be respected when decisions are rendered concerning the investment or expenditure of donor restricted funds. If a donor, in the gift instrument, has directed that appreciation not be spent, The Apache Software Foundation shall comply with that directive and consider it when making decisions regarding the management and investment of the fund. Any attempt to lift restrictions on any fund shall be conducted in full compliance with the law. Time Horizon: The Treasurer seeks to achieve the investment objectives over a full market cycle. The Treasurer does not expect that all investment objectives will be attained each year and recognizes that over various time periods the portfolio may produce significant over or under performance relative to broad markets. For this reason, long-term investment returns will be measured net of fees over a five-year moving average. Spending Policy: Distributions from the corpus, income and/or appreciation of The ASF's Endowment is prohibited unless approved by the Board in advance. The Board will keep a record of its deliberations and address the factors considered when making its decisions. Strategy: The Board and Committee agree that the benefit of investing in securities with higher return expectations outweighs the short-term volatility risk. * Equity and equity-like strategies will be used for capital appreciation. * Fixed income and diversifying strategies will be used to lower short-term volatility and provide stability, especially during periods of deflation and negative equity markets. * Cash is not a strategic asset of the portfolio but is a residual to the investment process and will be used to meet short-term liquidity needs. Asset Class Guidelines: Asset allocation will likely be the key determinant of the portfolio's total return over the long-term. Thus, diversification of investment across multiple markets that are not similarly affected by economic, political, or social developments is highly desirable. A globally diversified portfolio with uncorrelated returns from various assets should reduce the variability of returns over time. Asset classes are not to be considered individually, rather, the inclusion or exclusion of any particular asset class shall be determined by its potential impact to the total portfolio. The target asset allocation should provide an expected total return equal to or greater than the primary objective of the portfolio while avoiding undue risk concentrations presented by any single asset class or category. The Treasurer has adopted a long-term asset allocation policy that identifies the strategic target weights for each of the major asset classes. The table below highlights these asset classes and identifies strategic target weights and allowable ranges. Asset Allocation: Target Low High Equity 60% 40% 75% Fixed Income 40% 20% 55% Cash / Cash Equivalents 2% 1% 10% Rebalancing: The Investment Advisor is expected to continually monitor the portfolio mix and provide quarterly reports to the Treasurer. Neither the upper nor lower limits of the asset allocations are intended to require portfolio activity for the sole purpose of complying with the guidelines; however, deviations from these guidelines will be treated as discussion topics at portfolio review meetings with the Investment Advisor. Rebalancing should be considered at least annually. It is recommended that the target allocation be maintained so that the portfolio will be able to achieve its long-term goals. Manager Selection: The Investment Advisor's selection of Investment Manager(s) must be based on prudent due diligence procedures. A qualifying Investment Manager must be a registered investment advisor under the Investment Advisers Act of 1940, or a bank or insurance company. Active Versus Passive Management: Asset allocation will be implemented using both active and passive investment managers. Highly efficient areas of the capital markets may be managed using lower cost index or exchange traded funds while other asset classes may be managed using active managers and strategies that the Advisor believes have the ability to outperform. Investment Advisor Performance Review and Evaluation: Performance reports generated by the Investment Advisor shall be compiled at least quarterly and communicated to the Treasurer for review. The investment performance of the total portfolio, as well as asset class components, will be measured against commonly accepted performance benchmarks and relevant indices. Consideration shall be given to the extent to which the investment results are consistent with the investment objectives, goals, and guidelines as set forth in this IPS. The Treasurer intends to evaluate the portfolio(s) over at least a three-year period but reserves the right to terminate an Investment Advisor for any reason. Benchmarks: The primary investment objective is to achieve a total return exceeding that of the target weighted benchmark established by the Treasurer over a full market cycle. This target benchmark will be each asset category benchmark (or appropriate substitute) weighted by its target allocation. The relevant benchmarks for each asset class are as follows: Asset Class Benchmark Domestic Equity S&P 500 International Equity MSCI World Equity Ex US NR USD Fixed Income Barclays Capital U.S. Aggregate Bond INVESTMENT POLICY REVIEW The Treasurer will review this IPS at least annually to determine whether the stated investment objectives remain relevant. It is not expected that the IPS will change frequently. In particular, short-term changes in the financial markets should not require adjustments to the IPS. ------------------------------------------------------ End of minutes for the December 15, 2021 board meeting.