The Apache Software Foundation Board of Directors Meeting Minutes January 18, 2023 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:07 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/42zn The meeting was held via teleconference, hosted by the Secretary via Zoom. The #asfboard channel on the-asf.slack.com was used for backup. 2. Roll Call Directors Present: Rich Bowen Bertrand Delacretaz Christofer Dutz Roy T. Fielding Sharan Foga Willem Ning Jiang Roman Shaposhnik Sander Striker Directors Absent: Sam Ruby Executive Officers Present: Craig R. McClanahan David Nalley Craig L Russell Matt Sicker Ruth Suehle Executive Officers Absent: none Guests: Brian Behlendorf Brian Proffitt Christian Grobmeier Claude Warren Coty Sutherland - joined :33 Daniel Gruno Daniel Takamori - joined :23 Dave Fisher - joined :46 Ed Coleman Gavin McDonald Greg Stein Jarek Potiuk Joe Brockmeier Justin Mclean Katia Rojas Mark Thomas Niall Pemberton Ryan Skraba Sally Khudairi Shane Curcuru Torsten Curdt 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of December 21, 2022 See: board_minutes_2022_12_21.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander Striker] We're currently two weeks into the new year. Every year tends to bring its own unique challenges and opportunities. This year will be no different. I'm confident the ASF will continue to remain true and focused on its mission to deliver software for the public good, as it has for the past decades. Every year our members elect a new board of directors and nominate new members to the foundation. I've started preparation for the annual members meeting in March. This is the first annual meeting following a new process with different timings and steps. I'm going to solicit some assistance to get the tools we use for the meeting to align. This being the first meeting of the year shows once more how reminders have become relied on in part of the reporting process. I believe this to be a natural consequence of the reminders having been sent for quite a while on a quarterly basis to each project. As reminders didn't go out at the usual time due to errors on my part, I think we have a record number of reports not yet submitted less than a week before the meeting. This may lead to some additional review load in February. I've taken additional steps to prevent this for the remainder of the year. B. President [David Nalley] If not obvious elsewhere, there was a public post regarding our name. I received a number of requests from reporters to engage on the subject, but referred them all. Joe, Brian, Ruth, and the folks from Constantia drafted a message for us to use in immediate response. Finally, after a request from Joe to step down as VP, Marketing & Publicity, I've appointed Brian Proffitt to the role. Additionally, please see Attachments 1 through 8. C. Treasurer [Craig R. McClanahan] Unfortunately I suffered much of the month with a nasty flu bug, so was not able to accomplish a lot. Fortunately, our assistant treasurers were able to pick up some of the pieces, so we continued making progress on the tasks previously described. D. Secretary [Matt Sicker] In January, the secretary received 51 ICLAs and 2 CCLAs. We're working with Infra and Whimsy to update our use of LDAP with their updated authentication requirements. E. Executive Vice President [Ruth Suehle] ApacheCon things covered in Conferences and Fundraising reports. Should the board conclude in the latter part of this agenda to support a committee to consider our naming concerns, I am happy to work on bringing together the folks who have volunteered in various discussions over the last week and others to create a set of recommended next steps (or to simply participate). F. Vice Chair [Shane Curcuru] Nothing to report! Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Sander] See Attachment 9 B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 10 C. Apache Security Team Project [Mark J. Cox / Willem] See Attachment 11 D. VP of Jakarta EE Relations [Rob Tompkins / Bertrand] 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: # Any23 [ningjiang] # Dubbo [rbowen] # Flex [rbowen] # Mahout [rvs] A. Apache Accumulo Project [Ed Coleman / Sharan] See Attachment A B. Apache ActiveMQ Project [Bruce Snyder / Roy] No report was submitted. C. Apache Airavata Project [Suresh Marru / Sam] See Attachment C D. Apache Airflow Project [Bolke de Bruin / Roman] See Attachment D E. Apache Any23 Project [Lewis John McGibbney / Willem] No report was submitted. F. Apache APISIX Project [Ming Wen / Rich] See Attachment F G. Apache Aries Project [Christian Schneider / Christofer] See Attachment G H. Apache Arrow Project [Andrew Lamb / Bertrand] See Attachment H I. Apache AsterixDB Project [Till Westmann / Christofer] See Attachment I J. Apache Attic Project [Herve Boutemy / Willem] No report was submitted. K. Apache Avro Project [Ryan Skraba / Sharan] See Attachment K L. Apache Beam Project [Kenneth Knowles / Roman] See Attachment L M. Apache bRPC Project [James Ge / Roy] See Attachment M N. Apache Calcite Project [Ruben Q L / Sam] See Attachment N O. Apache CarbonData Project [Liang Chen / Rich] See Attachment O P. Apache Celix Project [Pepijn Noltes / Sander] No report was submitted. Q. Apache CXF Project [Daniel Kulp / Rich] No report was submitted. R. Apache DataFu Project [Eyal Allweil / Christofer] No report was submitted. S. Apache DB Project [Bryan Pendleton / Roy] See Attachment S T. Apache Directory Project [Shawn McKinney / Sam] See Attachment T U. Apache DolphinScheduler Project [Lidong Dai / Sander] See Attachment U V. Apache Druid Project [Gian Merlino / Roman] See Attachment V W. Apache Dubbo Project [Jun Liu / Roman] See Attachment W @Rich: follow up on PMC clarification X. Apache Fineract Project [James Dailey / Willem] See Attachment X Y. Apache Flex Project [Olaf Krüger / Bertrand] See Attachment Y Z. Apache Fluo Project [Keith Turner / Sharan] No report was submitted. AA. Apache Geronimo Project [Jean-Louis Monteiro / Sharan] See Attachment AA AB. Apache Griffin Project [William Guo / Roman] See Attachment AB AC. Apache Guacamole Project [Mike Jumper / Bertrand] See Attachment AC AD. Apache Hadoop Project [Wei-Chiu Chuang / Sander] See Attachment AD AE. Apache HAWQ Project [Lei Chang / Willem] See Attachment AE AF. Apache HBase Project [Duo Zhang / Rich] See Attachment AF AG. Apache Helix Project [Junkai Xue / Roy] No report was submitted. AH. Apache Iceberg Project [Ryan Blue / Christofer] No report was submitted. AI. Apache Incubator Project [Justin Mclean / Sam] See Attachment AI AJ. Apache InLong Project [Charles Zhang / Willem] See Attachment AJ AK. Apache Isis Project [Johan Doornenbal / Sander] See Attachment AK AL. Apache James Project [Benoit Tellier / Rich] See Attachment AL AM. Apache jclouds Project [Andrew Gaul / Roman] See Attachment AM AN. Apache Jena Project [Andy Seaborne / Bertrand] See Attachment AN AO. Apache JMeter Project [Bruno Demion / Sharan] No report was submitted. AP. Apache Johnzon Project [Jean-Louis Monteiro / Christofer] See Attachment AP AQ. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Roy] See Attachment AQ AR. Apache Kudu Project [Andrew Wong / Sam] See Attachment AR AS. Apache Kyuubi Project [Kent Yao / Rich] See Attachment AS AT. Apache Libcloud Project [Tomaž Muraus / Roy] See Attachment AT AU. Apache Linkis Project [Shuai Di / Christofer] See Attachment AU AV. Apache Lucene.Net Project [Shad Storhaug / Sam] No report was submitted. AW. Apache MADlib Project [Aaron Feng / Sharan] No report was submitted. AX. Apache Mahout Project [Andrew Musselman / Roman] No report was submitted. @Roman: pursue a PMC roll call for Mahout AY. Apache Maven Project [Karl Heinz Marbaise / Sander] No report was submitted. AZ. Apache Mesos Project [Qian Zhang / Willem] No report was submitted. BA. Apache MINA Project [Guillaume Nodet / Bertrand] No report was submitted. BB. Apache MXNet Project [Sheng Zha / Willem] No report was submitted. BC. Apache MyFaces Project [Bernd Bohmann / Sam] See Attachment BC BD. Apache Mynewt Project [Szymon Janc / Sharan] See Attachment BD BE. Apache NiFi Project [Joe Witt / Rich] See Attachment BE BF. Apache Nutch Project [Sebastian Nagel / Bertrand] See Attachment BF BG. Apache NuttX Project [Alin Jerpelea / Christofer] See Attachment BG BH. Apache OODT Project [Imesha Sudasingha / Sander] No report was submitted. BI. Apache OpenJPA Project [Mark Struberg / Roy] No report was submitted. BJ. Apache OpenMeetings Project [Maxim Solodovnik / Roman] See Attachment BJ BK. Apache OpenOffice Project [Jim Jagielski / Sam] No report was submitted. BL. Apache OpenWebBeans Project [Mark Struberg / Christofer] No report was submitted. BM. Apache ORC Project [William Hyun / Bertrand] See Attachment BM BN. Apache Parquet Project [Xinli Shang / Willem] See Attachment BN BO. Apache PDFBox Project [Andreas Lehmkühler / Roman] See Attachment BO BP. Apache Petri Project [Dave Fisher / Christofer] See Attachment BP BQ. Apache Pig Project [Koji Noguchi / Rich] See Attachment BQ BR. Apache Pivot Project [Roger Lee Whitcomb / Roy] See Attachment BR BS. Apache Portable Runtime (APR) Project [Nick Kew / Sharan] No report was submitted. BT. Apache Portals Project [David Sean Taylor / Sander] See Attachment BT BU. Apache Ranger Project [Selvamohan Neethiraj / Roy] No report was submitted. BV. Apache Ratis Project [Tsz-wo Sze / Bertrand] See Attachment BV BW. Apache Royale Project [Piotr Zarzycki / Roman] See Attachment BW BX. Apache Rya Project [Adina Crainiceanu / Sam] See Attachment BX BY. Apache Samza Project [Yi Pan / Sander] No report was submitted. BZ. Apache Sedona Project [Jia Yu / Willem] No report was submitted. CA. Apache Serf Project [Justin Erenkrantz / Rich] No report was submitted. CB. Apache SkyWalking Project [Sheng Wu / Christofer] See Attachment CB CC. Apache Steve Project [Daniel Gruno / Sharan] See Attachment CC CD. Apache Storm Project [Kishor Patil / Bertrand] No report was submitted. CE. Apache StreamPipes Project [Philipp Zehnder / Sam] See Attachment CE CF. Apache Streams Project [Steve Blackmon / Christofer] No report was submitted. CG. Apache Struts Project [René Gielen / Willem] See Attachment CG CH. Apache Synapse Project [Isuru Udana / Roy] See Attachment CH CI. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Sharan] See Attachment CI CJ. Apache Tcl Project [Georgios Petasis / Sander] See Attachment CJ CK. Apache Tez Project [László Bodor / Rich] See Attachment CK CL. Apache Thrift Project [Jens Geyer / Roman] See Attachment CL CM. Apache Tika Project [Tim Allison / Roy] See Attachment CM CN. Apache TinkerPop Project [Florian Hockmann / Bertrand] See Attachment CN CO. Apache Traffic Server Project [Bryan Call / Roman] See Attachment CO CP. Apache UIMA Project [Richard Eckart de Castilho / Christofer] See Attachment CP CQ. Apache Web Services Project [Daniel Kulp / Willem] No report was submitted. CR. Apache Zeppelin Project [Lee Moon Soo / Sander] No report was submitted. Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Calcite Project Chair WHEREAS, the Board of Directors heretofore appointed Ruben Q L (rubenql) to the office of Vice President, Apache Calcite, and WHEREAS, the Board of Directors is in receipt of the resignation of Ruben Q L from the office of Vice President, Apache Calcite, and WHEREAS, the Project Management Committee of the Apache Calcite project has chosen by vote to recommend Stamatis Zampetakis (zabetak) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ruben Q L is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Calcite, and BE IT FURTHER RESOLVED, that Stamatis Zampetakis be and hereby is appointed to the office of Vice President, Apache Calcite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Calcite Project Chair, was approved by Unanimous Vote of the directors present. B. Standardise privacy policy for foundation websites WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to standardise privacy policy across all public facing Foundation web sites; and WHEREAS the Board of Directors has previously delegated responsibility for establishing privacy policy to VP, Privacy; NOW, THEREFORE, BE IT RESOLVED, that the Apache Software Foundation Privacy Policy is the new standard for all websites hosted by the Foundation." The full text of the public facing foundation websites can be found here: https://privacy.apache.org/policies/privacy-policy-public.html The full text of the policy: This Privacy Policy clarifies the nature, scope and purpose of the processing of personal data (hereinafter referred to as “Data”) within our online offering and the related websites, features and content, as well as external online presence, e.g. our social media profiles on Twitter, Facebook, YouTube and similar sites (collectively referred to as “online presence”). With regard to the terminology we use, e.g. “Processing” or “Responsible”, we refer to the definitions in Article 4 of the General Data Protection Regulation (GDPR). 1. Name and contact details of the controller and the company data protection officer This privacy policy applies to data processing by: Responsible: The Apache Software Foundation V. P. Data Privacy 1000 N West Street, Suite 1200 Wilmington, DE 19801 U.S.A. E-Mail: vp-privacy@apache.org 2. Collection and storage of personal data and the nature and purpose of their use a) When visiting the website Log files When you visit our websites (full list of domains) or one of our subdomains, the browser on your device automatically sends information to the server of our website. This information is temporarily stored in a log file. The following information is being collected without your intervention and stored until automated deletion: The IP address of the requesting computer The date and time of access The name and URL of the retrieved file The website from which access is made (referrer URL) Geo information of the location from which access is made The browser used and, if applicable, the operating system of your computer and the name of your access provider The data mentioned are processed by us for the following purposes: Ensuring connectivity of our website Ensuring a use of our website, of which we think is comfortable for you Evaluation of system security and stability Other administrative purposes The retention time for this data is 90 days. The legal basis for data processing is Art. 6 para. 1 p. 1 lit. f GDPR. Our legitimate interest follows from the data collection purposes listed above. In no case do we use the collected data for the purpose of drawing conclusions about you. In addition, we use cookies and analysis services when you visit our website. Further details can be found under no. 4 and 5 of this privacy policy. Matomo In addition to log files, some of our websites use Matomo to understand what parts of the website are important to our users, what features are most frequently accessed, where users get lost in the documentation, etc. This data allows us to better understand how users use the system, the website, and the docs and where to focus improvements next. The collected information consists of the following: The IP address from which you access the website The type of browser and operating system you use to access our site The date and time you access our site The pages you visit If you click on any of the file download links on our website The addresses of pages from where you followed a link to our site The addresses of pages you go to from our site The search terms you use on the website This information is gathered and stored using the open source software Matomo. We don’t use any cookies to collect this information. An IP address is anonymized by removing the last two octets from the IP address. That means that if your IP is 192.168.100.50, we store it as 192.168.0.0. Matomo is self-hosted on a virtual machine provided by the Apache Software Foundation. It can only be accessed by members of the Apache Privacy committee. The data can be viewed by anyone by visiting https://analytics.apache.org/. Matomo respects any Do Not Track setting in your browser. You can also opt-out from all Matomo tracking below. b) When registering for our newsletter and mailing lists If, pursuant to Art. 6 para. 1 sentence 1 lit. a GDPR, you have expressly consented, we use your e-mail address to periodically send you our newsletter. For the receipt of the newsletter the indication of an e-mail address is sufficient. We inform our visitors at regular intervals through newsletters about news and offers from The Apache Software Foundation. The newsletter of our Foundation can only be received if (1) the data subject has a valid e-mail address and (2) the person concerned registers for the newsletter. For legal reasons, a confirmation e-mail will be sent to the e-mail address entered by an affected person before the first time of sending the newsletter, using the double-opt-in procedure. This confirmation email is used to check whether the owner of the e-mail address is the person who authorized the receipt of the newsletter. When you subscribe to the newsletter, we store the date and time of registration and the email address. The collection of this data is necessary for us to understand the (possible) misuse of an affected person’s e-mail address at a later date and therefore serves as legal safeguards for the controller. The personal data collected in the context of registering for the newsletter is used exclusively to send our newsletter. Subscribers may also be notified by e-mail if this is necessary for the operation of the newsletter service or registration, as might be the case in the event of changes to the newsletter/mailing list or technical changes. There will be no transfer to third parties of the personal data collected as part of the newsletter service. Subscription to our newsletter may be terminated by the person concerned at any time. Consent to the storage of personal data that the person has given us for the newsletter dispatch can be revoked at any time. For the purpose of revoking the consent, instructions are given by the end of each newsletter email. c) When registering for our mailing lists If, pursuant to Art. 6 para. 1 sentence 1 lit. a GDPR, you have expressly consented, we use your e-mail address to send you messages arriving at our mailing lists. For the receipt of the mailing list message the indication of an e-mail address is sufficient. Visitors may communicate with us through our mailing lists. The mailing list messages of our organisation can only be received if (1) the person concerned has a valid e-mail address and (2) the person concerned registers for the mailing list. For legal reasons, a confirmation e-mail will be sent to the e-mail address entered by an affected person for the first time using the double-opt-in procedure. This confirmation email is used to check whether the owner of the e-mail address authorized the receipt of the mailing list messages. When you subscribe to a mailing list, we store the date and time of registration and the email address. The collection of this data is necessary for us to understand the (possible) misuse of an affected person’s e-mail address at a later date and therefore serves as legal safeguards for the controller. When a mailing list is archived, the log file will be deleted. The personal data collected in the context of registering for a mailing list will be used exclusively to send messages arriving at that mailing list. Subscribers may also be notified by e-mail if this is necessary for the operation of the mailing list service or registration, as might be the case in the event of changes to the mailing list or other technical changes. We will not actively transfer to third parties any personal data as part of the mailing list service. However, almost all of our mailing lists are of a public nature. This means, your name and email may be exposed to the public. Also, all information you send to a mailing list will be exposed to the public. Third parties may collect this information and process it separately. The sender of messages is responsible if they expose their personal data to the public. All content sent to mailing lists is archived indefinitely. By using our mailing list service, you agree that any content is archived in that way. Subscription to our mailing lists may be terminated by the person concerned at any time. The consent to the storage of personal data that a person has given us for the mailing list dispatch can be revoked at any time. For the purpose of revoking the consent, instructions are given by the end of every email. 3. Disclosure of data Transfer of your personal data to third parties for purposes other than those listed below does not take place. We only share your personal information with third parties if: You, in accordance with Art. 6 para. 1 p. 1 lit. a GDPR, have given express consent to this. Disclosure pursuant to Art. 6 para. 1 sentence 1 lit. f GDPR is required to assert, exercise or defend legal claims and there is no reason to assume that you have a predominantly legitimate interest in not disclosing your data. Disclosure pursuant to Art. 6 para. 1 sentence 1 lit. c GDPR is a legal obligation. As permitted by law and according to Art. 6 para. 1 sentence 1 lit. b GDPR, disclosure is required for the settlement of contractual relationships with you. 4. External service providers The Apache Software Foundation uses the following external service providers who help to optimize its services. Insofar as these service providers process data on behalf of The Apache Software Foundation, agreements have been concluded with them which set the European data protection standards as binding and, in particular, prohibit the use of the data for other purposes. If we commission third parties to process data on the basis of a so-called “contract processing contract”, this is done on the basis of Art. 28 GDPR. The full list of providers is located in the full privacy policy page at https://privacy.apache.org/policies/privacy-policy-public.html 5. Social Media Plug-ins We rely on our website on the basis of Art. 6 para. 1 sentence 1 lit. f GDPR social plug-ins from the social networks Facebook, Twitter and Instagram to make our company better known. The underlying commercial purpose is to be regarded as a legitimate interest within the meaning of the GDPR. Responsibility for operation compliant with data protection is to be guaranteed by the respective providers. The integration of these plug-ins by us is done by means of the so-called two-click method to protect visitors to our website in the best possible way. a) YouTube On our website we have integrated components from YouTube. YouTube is an internet video portal that allows video publishers to freely watch video clips provided by other users for free viewing, rating and commenting. YouTube allows the publication of all types of videos, so that both complete film and television broadcasts, music videos, trailers and user-made videos uploaded via the YouTube internet portal are available. YouTube’s operating company is YouTube, LLC, 901 Cherry Ave., San Bruno, CA 94066, USA. YouTube, LLC is a subsidiary of Google Inc., 1600 Amphitheater Pkwy, Mountain View, CA 94043-1351, USA. Each visit to one of the pages of this site operated by the controller and incorporating a YouTube component (YouTube video) will automatically cause the Internet browser on the subject’s information technology system to download an illustration of the corresponding YouTube component from YouTube. More information about YouTube can be found at https://www.youtube.com/yt/about/en/. As part of this technical process, YouTube and Google are aware of the specific location of our site visited by the person concerned. If the person visiting our site is logged in to YouTube at the same time, YouTube calls a sub-page containing a YouTube video for the person visiting our site. This information is collected by YouTube and Google and associated with the individual YouTube account. YouTube and Google will always receive information through the YouTube component that a person has visited our website if the person is logged into YouTube at the time of access to our website; this happens regardless of whether the person clicks on a YouTube video or not. If such transmission of this information to YouTube and Google is not wanted by the person visiting our site, they can prevent the transmission by logging out of their YouTube account before visiting our website. YouTube’s privacy policy, available at https://www.google.com/intl/en/policies/privacy/, identifies the collection, processing, and use of personally identifiable information by YouTube and Google. 7. Affected rights You have the right: in accordance with Art. 15 GDPR, to request information about your personal data processed by us. In particular, you can request information on the processing purposes, the category of personal data, the categories of recipients to whom your data has been disclosed, the planned retention period, the right to rectification, deletion, limitation of processing or opposition, the existence of a right to complain, the source of your data, if not collected from us, and the existence of automated decision-making including profiling and, where appropriate, meaningful information about your data. in accordance with Art. 16 GDPR, to demand the immediate correction of incorrect or complete personal data stored with us. in accordance with Art. 17 GDPR, to demand the deletion of your personal data stored by us, unless the processing is required for the exercise of the right to freedom of expression and information, for the fulfillment of a legal obligation, for reasons of public interest or for the assertion, exercise or defense of Legal claims. to demand the restriction of the processing of your personal data according to Art. 18 GDPR, as far as the accuracy of the data is disputed by you, the processing is unlawful, but you reject its deletion and we no longer need the data, but you assert this, in the exercise or defense of legal claims or you have objected to the processing in accordance with Art. 21 GDPR. in accordance with Art. 20 GDPR, to receive your personal data provided to us in a structured, standard and machine-readable format or to request transmission to another person. according to Art. 7 para. 3 GDPR, to revoke your once-given consent to us at any time. As a result, we are not allowed to continue processing of data based on this consent for the future. to complain to a supervisory authority pursuant to Art. 77 GDPR. As a rule, you can contact the supervisory authority of your usual place of residence or work or our office. 8. Right to object If our retention of your personal data is based on legitimate interests in accordance with Art. 6 para. 1 sentence 1 lit. f GDPR, you have the right to file an objection against the processing of your personal data in accordance with Art. 21 GDPR, provided that there are reasons for this arising from your particular situation or the objection is directed against direct mail. In the latter case, you have a general right of objection, which is implemented by us without specifying any particular situation. If you would like to exercise your right of revocation or objection, please send an e-mail to vp-privacy@apache.org. 9. Data security We use the popular SSL (Secure Socket Layer) method during your site visit, in conjunction with the highest level of encryption supported by your browser. In general, this is a 256-bit encryption. If your browser does not support 256-bit encryption, we use 128-bit v3 technology instead. Whether a single page of our website is encrypted is shown by the closed representation of the key or lock icon in the lower status bar of your browser. We also take appropriate technical and organizational security measures to protect your data against accidental or intentional manipulation, partial or total loss, destruction or unauthorized access by third parties. Our security measures are continuously improved in line with technological developments. 10. Updating and changing this privacy policy This privacy policy is currently valid and is valid as of 2022-04-21. As a result of the further development of our website and offers thereof, or due to changed legal or official requirements, it may be necessary to change this privacy policy. The current privacy policy can be viewed and printed by you at any time on the website at https://privacy.apache.org/policies/privacy-policy-public.html. Some impacts of it can be found here: https://privacy.apache.org/faq/committers.html Special Order 7B, Standardise privacy policy for foundation websites, was approved by Unanimous Vote of the directors present. C. Change the Apache Portals Project Chair WHEREAS, the Board of Directors heretofore appointed David Sean Taylor (taylor) to the office of Vice President, Apache Portals, and WHEREAS, the Board of Directors is in receipt of the resignation of David Sean Taylor from the office of Vice President, Apache Portals, and WHEREAS, the Project Management Committee of the Apache Portals project has chosen by vote to recommend Neil Griffin (asfgriff) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that David Sean Taylor is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Portals, and BE IT FURTHER RESOLVED, that Neil Griffin be and hereby is appointed to the office of Vice President, Apache Portals, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7C, Change the Apache Portals Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Discussion of a name change Discuss possible action with regard to https://blog.nativesintech.org/apache-appropriation/ and https://www.endasfmascotry.com/ The board supports the president in creating a committee to explore updating naming options for the ASF. 9. Review Outstanding Action Items * Christian: pursue a resolution for ratifying data privacy policy [ Data Privacy 2022-06-15 ] Status: Resolution is on the agenda as 7B. * Willem: pursue a report for Any23 [ Any23 2022-12-21 ] Status: I sent three reminder emails to the private@any23 list. There have been no discussions in the private list for more than half a year. We need a PMC roll call for it. * Roman: pursue a report for Druid [ Druid 2022-12-21 ] Status: done 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:59 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period December 2022 * ISSUES FOR THE BOARD None. * OPERATIONS Responded to the following queries, liaising with projects as required: - reviewed FINERACT's mark usage policy and had no concerns - approved an external event for CASSANDRA - approved PNS for CELEBORN * REGISTRATIONS Worked with counsel to maintain the FLINK, PDFBOX, KAFKA and CASSANDRA registrations in the US. Worked with counsel to progress the FINERACT application. The BEAM and DOLPHINSCHEDULER registrations in the US completed. Worked with counsel and the NUTTX PMC to transfer the NUTTX mark to the ASF. * INFRINGEMENTS Contacted Namecheap regarding a phishing site using a copy of the HADOOP website and the site was promptly taken down. Provided advice to FINERACT regarding an infringement that has now been resolved. Directed counsel not to oppose a 3rd party registration that counsel thought might conflict with one of our existing registrations. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a --New: we welcomed one new Bronze Sponsor during this timeframe. b --Renewals: we received renewal confirmations from one Platinum Sponsor. One Gold Sponsor will be renewing at the Silver level. c --Payments: 1 --New: we received payment from one Platinum and one new Bronze Sponsor 1a --Incoming: we await payment from one Bronze Sponsor. We also await purchase a order to formally invoice one new Silver Sponsor. 2 --Renewing: we received payment from one renewing Platinum, one Gold, and one Bronze Sponsor 2a --Incoming: we await payment from one Platinum, five Gold, two Silver, and one Bronze Sponsor. We await purchase orders to formally invoice one Platinum, one Gold, and one Silver Sponsor. 2) Targeted Sponsors: we met with a Targeted Sponsor to review their contributions and provided a summary of their activities to date, as they enter their 7th year of supporting the ASF. We will be performing our annual Targeted Sponsor audit in January. 3) Sponsor Relations: ongoing outreach continues, including working with those Sponsors who needed to close out their budgets prior to the end of the calendar year. We rectified contacts with one Platinum and two Bronze Sponsors. We are also working with some China-based Sponsors regarding blocked emails as well as concerns/risks with Sponsorship renewal. 4) Event Sponsorship: no new events are taking place. A few ApacheCon NA sponsorship payments remain outstanding. 5) Individual Donations and Corporate Giving: we received $41.8K in individual and one-time corporate donations during December, which included renewal payments for one Silver and one Bronze Sponsor. We received contributions of $1K and higher from several repeat donors. 6) Administrivia: we continue to have an outstanding invoicing/payment issue with a Silver Sponsor. We are working with the Treasurer and Accounting teams to resolve. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Joe Brockmeier] General ======= The board is no doubt aware of the discussions around the name of the foundation. M&P received numerous inquiries in the past two weeks (through 18 January 2023) and supplied a statement on behalf of the foundation. We’ll continue to provide support with the press as needed and look forward to the board discussion to inform next steps. VP transition ========== As noted in the President’s report, Brian Proffitt will be taking over the office of VP effective this week. This transition has been in the works for some time, as it was a goal of mine to ensure that the “bus factor” of M&P was reduced (or is that increased?) and there is a deeper bench of people to work on marketing for the foundation. I appreciate David’s support and trust in appointing me to the role and expect that Brian will do a fantastic job going forward. I will continue to be available to help with the transition. Announcements ============= Uptick in TLP announcements lately, we have several announcements queued up for this week and next week. The Apache Software Foundation Announced Apache® NuttX™12.0 https://s.apache.org/tcabm The Apache Software Foundation Announces Apache® Linkis™ as a Top-Level Project https://s.apache.org/lncpq Social Media Note ============== Per last month's report, we continue to monitor the situation around Twitter + Mastodon and will act if / when necessary. ----------------------------------------- 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. Short Term Priorities ===================== - Prepare for the March Annual Members Meeting, possibly with new irc bot and voting tech. - LDAP constraints. - Shift away from TravisCI Long Range Priorities ===================== - Artifact Distribution Platform General Activity ================ - Continued progress on the new Infra-supported Agenda Tool. It is nearing v1.0 release of a readonly display. (v2 will be interactive) - Lots of JDK work for consistency across the build nodes. - Implementation of Gradle Enterprise. Several projects are currently testing our deployment. - Some early testing of Ansible, for future config management. - MFA work and planning. - Started work on Hugo for projects to use for website builds. - Roundtable held on January 11th. - Artifact distribution work continues, with some help from the Security Team for design requirements. - Auto-reboot script looking great for our build nodes, and getting manual for manual reboots of other nodes. We're now tracking a reboot per quarter for every box to pick up (kernel) security upgrades. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] Nothing to report this month. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== None Post ACNA22 event Surveys are complete, looks like we will not be receiving any more, but will push out one last reminder before publishing the stories we have. Travel Policy ========== Submitted Policy awaiting approval by President and/or EVP TAC Sub Domain ============== This has been implemented. we now have changed our primary email to private@tac.apache.org (from travel-assistance@apache.org) With this new domain, we look forward to creating our own website at tac.apache.org. TAC App ======= TAC app is closed. We still need to submit our suggestions for improvements. Future Events ============= None Currently. Due to lack of volunteer time to support and open applications for Fosdem, we will not be supporting this event this time around. Next event to support is likely to be Berlin Buzzwords. Short/Medium Term Priorities ===================== Still keeping an eye out for other smaller events to support. We are keen to hear about projects events. We got an unofficial inquiry from a project member about supporting a weekend project hackathon style event, I asked them to submit a proposal for review, but indicated this is something we support. Mailing List Activity ===================== No email activity this month. Membership ========== No changes to the membership this month ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas] ## Description: - The Diversity and Inclusion VP works in collaboration with a team that contributes towards generating a current description of the D&I landscape in the industry and for the foundation. The team also focuses on developing resources the projects can leverage to increase diversity and inclusion in their communities. ## Issues: ## Activity: *** Project: Internships for underrepresented groups (Outreachy) *** Outreachy December 2022 - March 2023 in progress. You can find the details of our Outreachy inter here [1]. Project: "SOLR-11872 Refactor test infra to work with a managed SolrClient; ditch TestHarness" [2] May-August 2023 round is open. Outreachy is calling for open source communities and mentors. Feb. 6, 2023 at 4pm UTC is the deadline for submitting an initial application. Applicants will be notified of their initial application status on March 6, 2023. *** Project: User Experience Research on new contributors *** Bitergia submitted draft of the user experience research report based on the data collected with the D&I survey. It is currently under internal review before sharing it with the community to confirm the approach is correct and avoid misunderstandings. Bitergia and Kenn (Apache Beam) continue working on the dashboard. *** Operations no news. ## Committee members' changes: no news. ## References [1] https://www.outreachy.org/alums/2022-12/ [2] https://www.outreachy.org/outreachy-december-2022-internship-round/communities/asf/solr-11872-refactor-test-infra-to-work-with-a-mana/cfp/ ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] Privacy Policy: We have submitted a new try for getting the privacy policy for public websites ratified. Some projects expressed to only apply those privacy policy if approved from the board. As there always might be a language barrier, here is the intent of what I am trying to achieve: to have a common, generic privacy policy all projects follow. This of course has some impact. In example, Google Analytics cannot be used anymore. Instead, the policy provides an alternative in terms of Matomo. Question: Updates to this policy may be necessary, when new data processors are added or services are altered. I would like to send updates to the board so they can be vetoed in a lazy way. Is this process acceptable for you? Operations: I have added Scarf and DinoSource ApS to the list of vendors. Scarf is a new service asked by some project to track their download statistics. The service supports the GDPR and also was cooperative when working with them. DinoSource is providing PonyMail and was known as Quenda before. The DPA was filed earlier, but without signature and adding DinoSource was just a formality. We had some removal requests. Automated requests where rejected. One person request was rejected as well since it implied mailinglist removals. So far, no rejections received any follow ups. Next goals: The privacy office will work harder on the committer privacy once the public privacy policy was ratified. Also, I'd like to find a system to help projects migrate to the new policy. ----------------------------------------- Attachment 9: Report from the VP of W3C Relations [Andy Seaborne] W3C Inc. has now started, taking over the staff and services that were previously hosted by MIT. ----------------------------------------- Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] Past month has been pretty calm. Committee members took good care of resolving most issues on time. After resolving a handful of LEGAL issues, we are flat at 19 outstanding issues compared to last month. I was able to reach the folks at DLAPiper. Scheduling by-laws review for next week. ----------------------------------------- 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. - The https://cveprocess.apache.org/ tool was given a major overhaul in order to support version 5 of the CVE JSON format. The security team can now publish a CVE direct to cve.org instantly via the tool and we'll work on rolling that out to projects over time. - We have further explored SBOM and VEX, and have started an experiment publishing (non)exploitability information in a VEX format for the Solr project, https://github.com/apache/solr-site/pull/86 - We have improved the accuracy of the reports we send to projects with open security issues, and made them more easily actionable. Stats for December 2022: 27 [license confusion] 21 [support request/question not security notification] 5 [report/question relating to dependencies] Security reports: 62 (last months: 84, 69, 55) 7 [web site/other infrastructure] 5 ['commons', 'sling'] 4 ['tomcat'] 3 ['airflow', 'jena', 'solr'] 2 ['fineract', 'guacamole', 'hadoop', 'shiro'] 1 ['ambari', 'any23', 'camel', 'cassandra', 'cloudstack', 'dolphinscheduler', 'druid', 'dubbo', 'helix', 'httpd', 'iotdb', 'jspwiki', 'karaf', 'mxnet', 'ofbiz', 'openoffice', 'ozone', 'pivot', 'santuario', 'servicecomb', 'streampark', 'submarine', 'wicket', 'xalan'] In total, as of 2 January 2023, we're tracking 160 (last months: 154, 137) open issues across 65 projects, median age 59 days (last months: 45, 53 days). 52 of those issues have CVE names assigned. 6 (last months: 9, 10) of these issues, across 5 projects, are older than 365 days. ----------------------------------------- Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins] ----------------------------------------- Attachment A: Report from the Apache Accumulo Project [Ed Coleman] ## Description: The Apache Accumulo is a robust, scalable, distributed key/value store that provides robust, scalable data storage and retrieval. With Apache Accumulo, users can store and manage large data sets across a cluster. Accumulo uses Apache Hadoop's HDFS to store its data and Apache ZooKeeper for consensus. ## Issues: There are no new issues requiring board attention. ## Membership Data: Apache Accumulo was founded 2012-03-20 (11 years ago) There are currently 41 committers and 41 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Christopher L. Shannon on 2022-09-26. - No new committers. Last addition was Christopher L. Shannon on 2022-09-27. ## Project Activity: Apache Accumulo 2.1 was released on Nov 1, 2022 as a Long-Term Maintenance (LTM) release. The release contains numerous features and improvements with over 1200 contributions from over 50 contributors. [1] Work on version 3.0 is in progress [2]. The 3.0 release plan release is to provide a quick turn-around release to remove deprecated code that was maintained in 2.1, in compliance with semver requirements. This will complete the removal of terms that have been identified as being potentially offensive. ## Community Health: Overall community health is good and GitHub activity remains consistent. - Community activity remains healthy and centers on GitHub. The decline in GitHub activity this quarter reflects a return to normal activity after increased activity in the prior quarter due to the 2.1 release. This reporting quarter also includes reduced activity during the US Thanksgiving and Christmas holiday periods. - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira activity reflects closing obsolete issues. ## Links [1] https://accumulo.apache.org/release/accumulo-2.1.0/ [2] https://github.com/apache/accumulo/projects/11 ----------------------------------------- Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder] ----------------------------------------- Attachment C: Report from the Apache Airavata Project [Suresh Marru] ## Description: The mission of Apache Airavata is the creation and maintenance of software related to executing and managing computational jobs on distributed computing resources, including local clusters, supercomputers, national grids, academic and commercial clouds. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Airavata was founded on 2012-09-18 (10 years ago) There are currently 42 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 Isuru Ranawaka on 2022-03-06. - No new committers. The last addition was Dinuka DeSilva on 2021-07-22. ## Project Activity: Project activity is consistent, but we dipped the momentum toward releases. The last release was still on March 24th, 2019. As the new calendar year brings in new energy, we will speed towards breaking the codebase into sub-systems and releasing the individual artifacts. ## Community Health: The community activity tapered down towards the end of the year and picked back again post-holidays. As a community, we are trying to lower the barrier to entry by making the READMEs more descriptive, simplifying the build steps, and making it easy to get hello world style capabilities working. We will put these simplifications to the test as GSoC contributors start exploring the projects. ----------------------------------------- Attachment D: 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: There are no issues requiring board attention. ## Membership Data: Apache Airflow was founded 2018-12-19 (4 years ago) There are currently 51 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Daniel Standish on 2022-09-22. - Niko Oliveira was added as committer on 2022-12-19 - Andrey Anshin was added as committer on 2022-11-28 ## Project Activity: We are on a pretty steady release cadence. Next release (2.5.1) is being voted upon as we are submitting this report. - Provider packages 2023-01-02 was released on 2023-01-05. - Provider packages apache-hive, microsoft-azure 2022-12-14 was released on 2022-12-19. - Apache Airflow 2.5.0 was released on 2022-12-02. ## Community Health: We are a very lively community with lots of activity. Work is underway for another Airflow Summit that for the first time will be in-person. - dev@airflow.apache.org had a 8% increase in traffic in the past quarter (390 emails compared to 358) - users@airflow.apache.org had a 31% decrease in traffic in the past quarter (53 emails compared to 76) - 1499 commits in the past quarter (8% increase) 223 code contributors in the past quarter (3% increase) - 1075 PRs opened on GitHub, past quarter (-6% change) - 1073 PRs closed on GitHub, past quarter (-5% change) - 422 issues opened on GitHub, past quarter (-7% change) - 418 issues closed on GitHub, past quarter (-6% change) ----------------------------------------- Attachment E: Report from the Apache Any23 Project [Lewis John McGibbney] ----------------------------------------- Attachment F: Report from the Apache APISIX Project [Ming Wen] ## Description: The mission of Apache APISIX is the creation and maintenance of software related to a cloud-native microservices API gateway ## Issues: There is no issue ## Membership Data: Apache APISIX was founded 2020-07-15 (2 years ago) There are currently 53 committers and 27 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 ZhengSong Tu on 2022-06-06. - Tao Yang was added as committer on 2022-11-19 ## Project Activity: APISIX has released version 3.0. The participation of many contributors in the community has added a lot of features to this version. 3.1.0 was released on 2022-12-29. apisix-dashboard-2.15.0 was released on 2022-12-12. apisix-dashboard-2.14.0 was released on 2022-12-05. apisix-dashboard-2.13.1 was released on 2022-11-18. 2.15.1 was released on 2022-11-17. apisix-java-plugin-runner-0.4.0 was released on 2022-11-11. 3.0.0 was released on 2022-11-02. ## Community Health: APISIX holds a community meeting every month, inviting developers and users to share. Development activity was somewhat down this quarter due to the Christmas and New Year holidays. dev@apisix.apache.org had a 35% increase in traffic in the past quarter (574 emails compared to 424) 470 commits in the past quarter (-19% change) 76 code contributors in the past quarter (-1% change) 379 PRs opened on GitHub, past quarter (-24% change) 364 PRs closed on GitHub, past quarter (-24% change) 392 issues opened on GitHub, past quarter (2% increase) 270 issues closed on GitHub, past quarter (-1% change) ----------------------------------------- Attachment G: Report from the Apache Aries Project [Christian Schneider] ## Description: Apache Aries software is a set of pluggable Java components enabling an enterprise OSGi application programming model. ## Issues: No current issues. ## Membership Data: Apache Aries was founded 2010-12-15 (12 years ago) There are currently 57 committers and 41 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 Carlos Sierra Andrés on 2018-07-03. - No new committers. Last addition was Romain Manni-Bucau on 2020-01-29. ## Project Activity: Recent releases: jax-rs-whiteboard-2.0.2 was released on 2023-01-02. spifly-1.3.6 was released on 2022-12-16. proxy-impl-1.1.13 was released on 2022-10-12. ## Community Health: We got a bit more activity than last quarter but still very low. Especially the user list is very calm. ----------------------------------------- Attachment H: Report from the Apache Arrow Project [Andrew Lamb] ## Description: The mission of Apache Arrow is the creation and maintenance of software related to columnar in-memory processing and data interchange ## Issues: Lack of ASF sponsored invite-free chat service is a minor source of friction for community building. Most subprojects now use github for tickets to lower the barrier to entry for new / casual contributors, but we still have fragmented stories for group chat. ASF Slack requires an invite and some sub communities use other chat-like services. ## Membership Data: Apache Arrow was founded 2016-01-20 (7 years ago) There are currently 89 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Kun Liu was added to the PMC on 2022-11-13 - Jacob Quinn was added to the PMC on 2022-10-25 - Nicola Crane was added to the PMC on 2022-10-25 - Jacob Wujciak was added as committer on 2022-12-19 - Ben Baumgold was added as committer on 2022-10-26 - Bogumił Kamiński was added as committer on 2022-10-24 - Eric Hanson was added as committer on 2022-10-26 - Jie Wen was added as committer on 2023-01-08 - Jarrett Revels was added as committer on 2022-11-02 - Curtis Vogt was added as committer on 2022-11-02 - Raúl Cumplido was added as committer on 2022-12-05 - Will Jones was added as committer on 2022-10-28 - Yang Jiang was added as committer on 2022-11-02 ## Project Activity: * Switching from JIRA to github issues in order to keep the overhead for new contributors low (no need to register for an ASF JIRA account) * [ADBC] (Arrow Database Connectivity) first release: * Community voted to add RLE to the specification * Additional subproject updates are below * We continue to release several different products and releases per quarter [ADBC]: https://arrow.apache.org/blog/2023/01/05/introducing-arrow-adbc/ Recent releases: ADBC-0.1.0 was released on 2023-01-10. RS-30.0.1 was released on 2023-01-08. RS-OS-0.5.3 was released on 2023-01-08. RS-30.0.0 was released on 2023-01-03. RS-29.0.0 was released on 2022-12-12. RS-OS-0.5.2 was released on 2022-12-07. RS-DATAFUSION-15.0.0 was released on 2022-12-05. DATAFUSION-PYTHON-0.7.0 was released on 2022-11-29. RS-28.0.0 was released on 2022-11-28. 10.0.1 was released on 2022-11-22. RS-BALLISTA-0.10.0 was released on 2022-11-21. JULIA-2.4.1 was released on 2022-11-18. RS-27.0.0 was released on 2022-11-15. RS-DATAFUSION-14.0.0 was released on 2022-11-07. RS-26.0.0 was released on 2022-11-03. 10.0.0 was released on 2022-10-26. JULIA-2.4.0 was released on 2022-10-26. RS-BALLISTA-0.9.0 was released on 2022-10-26. RS-25.0.0 was released on 2022-10-17. ## Community Health: The community health appears good, discussions on the mailing lists and github are productive. We recently had a nice discussion on the State of the Project: https://lists.apache.org/thread/r8gl3wvjgy9k8n2t194r0bbdbxx6ksqc and discussed various ways to keep encouraging the community. ## Language Area Updates Arrow has at least 12 different language bindings, as explained in https://arrow.apache.org/overview/ Arrow 10.0.0 release: https://arrow.apache.org/blog/2022/10/31/10.0.0-release/ ### C++ ### C# ### Go We’re seeing significant increases in interest and usage of the Arrow Go library. From startups like Spice.AI to being incorporated and used in Google BigQuery’s quickstart example and more. 2022 was a big year of updates, fixes, and drumming up interest for the Go module that we hope to continue for increased adoption and usage. The Go module, along with C++, is used as the initial implementation for the Run-End Encoding array implementation. Future development plans are to continue to expand the compute capabilities of the Go module and extend integration with Substrait. ### Java ### JavaScript ### Julia We’ve worked again on simplifying and streamlining the administrative side for the Julia implementation; adding additional committers, simplifying the release process, etc. This has increased the rate of contributions, as expected. There’s interest in finishing the C data/stream interfaces for the Julia implementation soon. ### Rust Rust has several projects: arrow-rs (arrow, parquet, arrow-flight object_store implementations) arrow-datafusion: rust query engine arrow-ballista: distributed query engine We are working to incorporate substrait into DataFusion Working on external communication with several blog posts about technology on sorting Fast and Memory Efficient Multi-Column Sorts in Apache Arrow Rust, Part 1 and Querying Parquet with Millisecond Latency We also continue calendar based release train with good results. ### C (GLib) We’ve added support for 16-bit float type. ### MATLAB 1. We have been focusing development efforts on implementing an "object dispatch layer" that uses MEX to "connect" MATLAB objects with corresponding C++ objects. This code is being actively developed at github.com/mathworks/libmexclass. See the following Arrow mailing list discussion for more context. We hope to upstream the changes needed to make the MATLAB Interface to Arrow use libmexclass under the hood in the coming months. This should enable the MATLAB interface to wrap relevant Arrow C++ objects (e.g. arrow::Array, arrow::Table) and expose them to MATLAB. 2. We have been continuing to investigate Windows CI support for the MATLAB interface. Currently, only Linux and macOS are supported. ### Python ### R ### Ruby We’ve added support for 16-bit float type. There is a new contributor who develops a new data frame library based on the Ruby bindings. The new contributor upstreamed some improvements implemented in the downstream data frame library. ----------------------------------------- Attachment I: Report from the Apache AsterixDB Project [Till Westmann] Description: Apache AsterixDB is a scalable big data management system (BDMS) that provides storage, management, and query capabilities for large collections of semi-structured data. Activity: - Development and discussions are active, the community continues to be healthy and engaged. - A number of new features, improvements and fixes have been merged into the master branch and are set to be in the next release. Issues: There are no issues that require the board's attention at this time. PMC/Committership changes: - Vijay Sarathy was added as a committer on 2022-10-13. - The last committer added was Vijay Sarathy on 2022-10-13. - The last PMC member added was Xikui Wang on 2018-02-02. Releases: - Apache AsterixDB JDBC Connector 0.9.7.1 was released on 2022-03-01 - Apache AsterixDB 0.9.7.1 was released on 2021-12-13. - Apache Hyracks 0.3.7. was released on 2021-12-13. ----------------------------------------- Attachment J: Report from the Apache Attic Project [Herve Boutemy] ----------------------------------------- Attachment K: Report from the Apache Avro Project [Ryan Skraba] ## Description: Apache Avro is a data serialization system with a compact binary format. It is used for storing and transporting schema driven serialized data. The unique features of Avro include automatic schema resolution - when the reader's expected schema is different from the actual schema with which the data was serialized the data is automatically adapted to meet reader's requirements. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Avro was founded 2010-04-21 (13 years ago) There are currently 37 committers and 25 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 Martin Tzvetanov Grigorov on 2022-09-08. - No new committers. Last addition was Zoltan Csizmadia on 2022-03-28. ## Project Activity: The last release of Apache Avro 1.11.1 was 2022-07-31. The time is right to do another minor release with bug and security fixes in this quarter, and we are on track to do a major release (1.12.0) if necessary. ## Community Health Our last three board reports have had inaccurate mailing list numbers; we've been reporting the same numbers for every report since Q4 2021. We have COMDEV-482 to track and fix this. Here are the the actual numbers calculated from lists.apache.org over the last from Q4 2021 to Q4 2022. Mailing Lists: - dev@avro.apache.org had 1087, 3554, 1520, 1306 and 412 emails - user@avro.apache.org had 34, 30, 17, 10 and 5 emails - issues@avro.apache.org had 253, 1242, 280, 604, 873 emails These numbers explain why we reported an increase in dev@ list activity in Q3 despite turning off many automatic notifications in August. This is evident in the last quarter. The dev@ mailing list has fewer messages but also better signal-to-noise since making the change. We noted but couldn't explain the bump of contributions in Q2. The other community health indicators remain accurate: JIRA: - 63 issues opened (3% increase) - 41 issues closed (-6% change) Code Repository: - 359 commits in the past quarter (8% increase) - 31 code contributors in the past quarter (55% increase) GitHub: - 140 PRs opened (-2% change) - 129 PRs closed (3% increase) Even if we have been releasing more regularly over the last few years, there is quite a bit of interest on the mailing list for codifying and improving the releases and versioning lifecycle. Some notable changes are on the table are adopting semantic versioning, supporting more than one major release, and especially releasing language SDKs as separate artifacts. ----------------------------------------- Attachment L: 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 (6 years ago) There are currently 90 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. Community changes, past quarter: - No new PMC members. Last addition was Chamikara Madhusanka Jayalath on 2021-01-20. - Ritesh Ghorse was added as committer on 2022-11-02 - Yi Hu was added as committer on 2022-11-05 ## Project Activity: Highlights of community activities: - We started planning the Beam Summit for June 13-15th, 2023 in NYC. - New webpage on ML/RunInference - Java Multi-language pipelines support including support for using Python RunInference from Java SDK. - We have been using GitHub Issues for a while now, and community response is overall positive. - There is a trend of many IO connectors being made into "schema transforms" which means they have a cross-language schema and become more language-SDK agnostic. It signals the continued trend of Beam as a language-independent framework to be used with any big data processin gengine. Recent releases: - 2.44.0 was released on 2023-01-13. - 2.43.0 was released on 2022-11-17. - 2.42.0 was released on 2022-10-16. ## Community Health: The community on the mailing list and in code seems to be holding steady. We have had departures of very active committers but also addition of new ones. If you aren't growing you are shrinking! Change is the only constant! :-) ----------------------------------------- Attachment M: Report from the Apache bRPC Project [James Ge] bRPC quarterly report(Q4 2022) ●Brief description of bRPC. bRPC is an industrial-grade RPC framework for building reliable and high- performance services. ●The overall status and health of bRPC and the community. Apache bRPC is just graduated as Top Level Project in December. 129 developers from 20 more companies and organizations have contributed to the bRPC project, including 10 PMC members and another 6 committers. Committers take turns responding user emails and issues on a weekly basis. Due to efforts of the whole community, the mailing list (and issue board) of Apache bRPC stays active. We released v1.3.0 in last october and plans to make the next release this month including several new features and bug fixes. ●Are there any issues for the Board to act on? There are no Board-level issues at this time. ●When did the project last make any releases? * bRPC v1.3.0 was released on Oct. 25th with several bug fixes and new features such as gcc support on Linux arm64. ●The overall activity in the project over the past quarter. We got 25 +1, and no -1 during the Vote to graduation of bRPC in the IPMC community in December 2022. On Dec. 22th, the ASF board comfirmed the graduation of bRPC to TLP. bRPC v1.3.0 was released on Oct. 25th with several bug fixes and new features such as gcc support on Linux arm64. One new committer was added in Novemeber. During the past quarter, about 100 new emails were received and answered weekly. ●The current plans of bRPC. The release work for bRPC v1.4.0 is in progress, in which several improtant features will be included such as the RDMA support and bazel third_party support. Meanwhile, we are arranging PR announcement for the graduation to TLP and developing new committers as always. ●When were the newest committers or PMC members elected? * On November 1st, 2022 we elected the newest committer Chen Guangming. On June 22th, 2022 we added three new PMC members: Cai Daojin, Helei and Lilei. ●PMC and committer diversity. 16 PMC members and committers are from 9 unique organizations (including one freelancer): Baidu, ByteDance, Google, 4Paradigm, Momemta. AI, Shopee, Tecent, JOYY. ●Project branding or naming issues, either in the project or externally. There are no known branding or naming issues. ●Legal issues or questions. There are no known legal issues or questions. ●Infrastructure issues or strategic needs. There are no infrastructure issues or strategic needs at this time. ----------------------------------------- Attachment N: Report from the Apache Calcite Project [Ruben Q L] ## Description: Apache Calcite is a highly customizable framework for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. Avatica is a sub-project within Calcite and provides a framework for building local and remote JDBC and ODBC database drivers. Avatica has an independent release schedule and its own repository. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Calcite was founded 2015-10-22 (7 years ago) There are currently 60 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 Andrei Sereda on 2022-08-08. - Bertil Chapuis was added as committer on 2022-10-14 - Dmitry Sysolyatin was added as committer on 2022-11-07 Following our yearly rotation tradition, the PMC has elected a new chair: Stamatis Zampetakis. This is the first time that a previous chair has been re-elected. ## Project Activity: There has been no Apache Calcite releases in this quarter. The next one (1.33.0) is currently being discussed and its scope is being finalized, so it should be released soon. Apache Calcite Avatica Go 5.2.0 was released on 2022-10-13. This is a maintenance release of Avatica Go with some dependency updates, bug fixes and a new minor feature. This release supports Go 1.18 and 1.19, which are currently the versions supported and maintained by the Go team. ## Community Health: The community maintains a healthy status. There has been a generalized increment in all the metrics regarding the project activity (137% increase in traffic in the dev mailing list, 55% increase in opened issues in Jira, 78% increase in closed issues, 62% increase in commits, 50% increase in code contributors, 36% increase in opened PRs in GitHub, 69% increase in closed PRs). This is somehow expected after the slight decrease in the previous quarter due to the summer vacation, but nevertheless it confirms the positive trend on Calcite community health and project contributions. The number of non-committer (contributor) commits per month: +---------------------+---------------------+---------------------+ | year | month | contributor_commits | +---------------------+---------------------+---------------------+ | 2022 | 10 | 10 | | 2022 | 11 | 11 | | 2022 | 12 | 11 | +---------------------+---------------------+---------------------+ The number of active reviewers per month: +---------------------+---------------------+---------------------+ | year | month | active_reviewers | +---------------------+---------------------+---------------------+ | 2022 | 10 | 4 | | 2022 | 11 | 6 | | 2022 | 12 | 4 | +---------------------+---------------------+---------------------+ Top reviewers in the last 3 months: +-----------------------------------------------------------+---------+ | committer | reviews | +-----------------------------------------------------------+---------+ | Benchao Li | 13 | | Julian Hyde | 6 | | rubenada | 4 | | Alessandro Solimando | 4 | | Jess Balint | 2 | | Dmitry Sysolyatin | 1 | | Volodymyr Vysotskyi | 1 | | Stamatis Zampetakis | 1 | +-----------------------------------------------------------+---------+ ----------------------------------------- Attachment O: Report from the Apache CarbonData Project [Liang Chen] ## Description: - The Apache CarbonData is data store solution for fast analytics on Big Data platforms (including Apache Hadoop, Apache Spark, Apache Flink among others) to help speed up queries an order of magnitude faster over petabytes of data, with the aim of using a unified file format to satisfy all kinds of data analysis cases. ## Issues: - There are no new issues requiring board attention at this time. ## Activity: - Last 3 months, we focused on fixing issues, some key issues as below: - Operations failed when index loaded - [CARBONDATA-4338] Moving dropped partition data to trash - Remove list files while query and invalid cache. - Fix Wrong Projection name displayed if MV create query has alias. - Fix Show Schema Issue. ## Health Report: - Commit activity: - 23 commits in the past quarter (10 increase) - 11 code contributors in the past quarter ( 10% change) ## Releases: - we are preparing 2.3.1 for fixing some issues - 2.3.0 was released on 2022-01-24 ## Project Composition: - There are currently 28 committers and 18 PMC members in this project. - The Committer-to-PMC ratio is roughly 7:5. ## Community changes, past quarter: - New PMC members Brijoo Bopanna added on 2022-09-24 ## Notable mailing list trends:Mailing list activity stays at a high level - dev@carbondata.apache.org: - 165 subscribers (change 13): - dev@carbondata.apache.org had a 36% decrease in traffic in the past quarter (1012 emails compared to 1566): - issues@carbondata.apache.org: - issues@carbondata.apache.org had a 80% decrease in traffic in the past quarter (67 emails compared to 324): - user@carbondata.apache.org: - 76 subscribers (no change): ## Busiest GitHub issues/PRs: - carbondata/pull/4291Bump jackson-databind from 2.10.0 to 2.13.4.1 in /integration/presto(4 comments) - carbondata/pull/4292Bump solr-core from 6.3.0 to 8.8.2 in /index/lucene(3 comments) - carbondata/pull/4293Bump jackson-databind from 2.10.0 to 2.12.7.1 in /integration/presto(0 comments) ----------------------------------------- Attachment P: Report from the Apache Celix Project [Pepijn Noltes] ----------------------------------------- Attachment Q: Report from the Apache CXF Project [Daniel Kulp] ----------------------------------------- Attachment R: Report from the Apache DataFu Project [Eyal Allweil] ----------------------------------------- Attachment S: Report from the Apache DB Project [Bryan Pendleton] ## Description: The mission of the Apache DB project is to create and maintain commercial-quality, open-source, database solutions based on software licensed to the Foundation, for distribution at no charge to the public. The Apache DB TLP consists of the following subprojects: o Derby : a relational database implemented entirely in Java. o JDO : focused on building the API and the TCK for compatibility testing of Java Data Object implementations providing data persistence. o Torque : an object-relational mapper for Java. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache DB was founded 2002-07-16 (20 years ago) There are currently 47 committers and 44 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 Georg Kallidis on 2020-08-26. - No new committers. Last addition was Tobias Bouschen on 2021-01-19. ## Project Activity: Recent releases: - Derby-10.16.1.1 was released on 2022-06-15. - JDO 3.2.1 was released on 2022-05-25. - JDO 3.2 was released on 2022-02-01. - Torque 5.1 was released on 2022-01-31. - The Derby community received a security vulnerability report and have addressed it; it is tracked as CVE-2022-46337. The fix in already in the source tree and will be delivered with Derby's next release, which is not yet scheduled. - The Derby community have also been testing with new builds of the upcoming JDK 20; Derby's testing processes may have found a bug in one of the JDK 20 features as a result which is good. - The JDO community evaluated the Derby vulnerability report to see if it applied to JDO's use of Derby; no JDO vulnerability was found as a result. - The JDO community are working on moving from JDK 8 to JDK 11, which will be a significant change and require a new 3.3 release, which is not yet scheduled. - The JDO community are working on improving code quality via feedback solicited from a code analysis tool called SonarCloud. SonarCloud itself is not open source but is free to analyze open source projects. A number of issues reported by the tool have been merged to the main branch and several others are currently being worked. - The Torque community have completed source modifications to move from JDK 8 to JDK 11. The changes are anticipated to be delivered as a new release 5.2, which is not yet scheduled. ## Community Health: Community health seems good across the project. All the mailing lists were at typical levels, and source contributions and fixes have been proceeding at a normal pace. All the project repositories are in a development stage trying to work toward future releases. ----------------------------------------- Attachment T: Report from the Apache Directory Project [Shawn McKinney] ## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (18 years ago) There are currently 59 committers and 19 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 Radovan Semancik on 2018-09-28. - No new committers. Last addition was Brian Demers on 2022-04-14. ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. Per sub-project: - ApacheDS: low activity. - LDAP API: low activity. - Studio: low activity. - Fortress: low activity. - Kerby: low activity. Security vulnerability reported. Fix has been merged into the repo. There were some delays which have introduced concerns that will be monitored closely. - Mavibot: low activity. - SCIMple: good activity. Brian Demers continues work on Scimple. Still no release is scheduled which is an ongoing concern as the project has yet to be released. ## Community Health: No problems to report. 4Q activity low but PMC has active members and the project continues to be adequately maintained. ----------------------------------------- Attachment U: Report from the Apache DolphinScheduler Project [Lidong Dai] ## Description: Apache DolphinScheduler is a cloud-native workflow orchestration platform with powerful user interface, dedicated to solving complex task dependencies in the data pipeline and providing various types of jobs available `out of the box` ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache DolphinScheduler was founded 2021-03-17 (2 years ago) There are currently 53 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Chufeng Gao was added to the PMC on 2022-11-24 - Hui Zeng was added as committer on 2022-11-08 ## Project Activity: Software development activity: - We released the bug fix release 2.0.7 on 2022-10. - We released 3.0.2 and 3.1.1 on 2022-11. - We released 3.0.3, 3.0.4 and 3.1.2 on 2022-12. - We released 3.1.3 on 2023-01. Meetups and Conferences: We hosted 4 online meetups in the community. There are DolphinScheduler India Meetup, DolphinScheduler on Azure Meetup, Spark X DolphinScheduler co-Meetup and DolphinScheduler China Meetup ## Community Health: dev@dolphinscheduler.apache.org had a 64% increase in traffic in the past quarter (297 emails compared to 181) 513 commits in the past quarter (-51% decrease) 540 PRs opened on GitHub, past quarter (-20% change) ----------------------------------------- Attachment V: 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 25.0.0, which contained 300 new features, bug fixes, performance enhancements, documentation improvements, and additional test coverage from 51 contributors. Druid Summit 2022 (https://druidsummit.org/) was held on December 6-7 2022. It was a fully-remote conference with 34 sessions including speakers from a variety of organizations. In the past three months (Oct-Dec 2022), mailing list traffic is down 28% relative to the prior three months (Jul-Sep 2022). GitHub activity, depending on how you look at it, is flat (PRs), down 11% (commits), or down 30% (number of issues opened). However, despite this dip from Q3 to Q4, quarterly GitHub PR and issue activity are both up about 30% since our previous report was filed in July 2022. Together, these statistics represent a pattern of migration of activity from mailing lists to GitHub, which has been happening for some time, as well as an indication that contributions to the project are healthy. On January 27 2022, we set up a community Slack workspace at https://apachedruidworkspace.slack.com/. The new workspace currently has 990 members, an increase of 475 members since our last report. A Helm chart for Druid was contributed after the helm/charts repository on GitHub was deprecated. However, we have not included this in any release since then, due to uncertainty about whether or not we need to perform formal IP clearance for this contribution, and a lack of volunteers willing to spend the time to sort this out. We hope to be able to sort this out for a subsequent release. ## Recent PMC changes - Currently 33 PMC members. - 1 new PMC member since the last report: - Abhishek Agarwal (2022-06-06) ## Recent committer changes - Currently 56 committers. - 4 new committers since the last report: - Rohan Garg (2022-07-26) - Amatya Avadhanula (2022-09-29) - Paul Rogers (2022-09-30) - Karan Kumar (2022-11-03) ## Recent releases - 25.0.0, a major release, on 2023-01-04. - 24.0.2, a patch release, on 2022-12-21. - 24.0.1, a patch release, on 2022-11-12. - 24.0.0, a major release, on 2022-09-21. ## Development activity by the numbers In the last quarter: - 719 commits from 44 contributors - 784 pull requests opened - 719 pull requests merged/closed - 137 issues opened - 106 issues closed ----------------------------------------- Attachment W: Report from the Apache Dubbo Project [Jun Liu] ## Description: Apache Dubbo is an easy-to-use Web and RPC framework that provides different language implementations, service discovery, traffic management, observability, security, tools, and best practices for building enterprise-ready microservices. ## Issues: No issues need board attention in this reporting cycle. ## Membership Data: Apache Dubbo was founded on 2019-05-15 (4 years ago) There are currently 90 committers and 27 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 YunXing Zhao on 2022-07-29. - Wang Xiaoxiong was added as committer on 2022-12-15 - Peng Jiaxin was added as committer on 2022-11-03 - Ma Zhihui was added as committer on 2022-12-03 - Yang Yang was added as committer on 2022-11-08 Same as in the last quarter, all the newly added committers are from side projects. No new PMCs are added because the community has decided to tighten the issuance of PMC membership. ## Project Activity: The community has been focusing on building a better ecosystem around Dubbo, so many of the activities in the past quarter happened on some side projects like dubbo-rust, dubbo-admin, dubbo-website, dubbo-go, etc. Release or activities classified by project: - apache/dubbo, 11 releases of 3 active branches with 3 still under voting. - apache/dubbo-go, integrated with other opensource projects like Apache RocketMQ and Polaris - apache/dubbo-rust, v0.2.0 released, v0.3.0 is almost ready - apache/dubbo-node, we are still working with the first official Dubbo3 release, this has been delayed for a while for the complexity of the Triple protocol implementation. - apache/dubbo-website, a brand new website and documentation version is about ready to release at the beginning of the next quarter. - apache/dubbo-admin, the refactoring of this project with Go language is undergoing, we expect Admin to be more active and rich in cloud-native features by migrating to a more cloud-native programming language. Dubbo has won awards from some open-source or media organizations in China, including The 2022 Most Popular Open-source Project from CSDN, 2022 Healthy Community Case from OSC, etc, proving Dubbo is a popular and well-recognized open-source project and community. ## Community Health: In the past quarter, Dubbo's Github activity, including commit, issue and pull request, has increased significantly, because we have published some features in our Roadmap (including observability, proxyless mesh, http/rest, etc.) to Github and encouraged developers to contribute, which has received good returns. We will continue to promote this model in the near future. Some language projects are not very active this quarter. Some are due to the lack of users, and some are due to the lack of new feature plans at a certain stage. We should consider devoting more efforts to these projects in the next quarter to bring them back on the right track. ----------------------------------------- Attachment X: Report from the Apache Fineract Project [James Dailey] ## Description: At Apache Fineract, our mission is to build, maintain and enhance a cloud-ready core banking system for robust, scalable, and secure operations of financial institutions. We believe in financial services for everyone, including and especially for the unbanked and underbanked. ## Issues: Trademark: The project has been working to ensure that the Trademark policy is clear and to address potential issues. RESOLVED Old releases/upgrade paths: OPEN We are working to encourage users to migrate to more recent versions. Based on queries and other information, we are certain that a number of users are remaining on older versions or heavily forked code bases. Upgrade paths have become problematic. We adopted a policy that only the last two releases will be listed on the main page and supported. All users should migrate to those. This is especially for bug or security fixes, of which there are a few. We may revise to include a "stable long term release version" and more upgrade path scripts. ## Membership Data: Apache Fineract was founded 2017-04-19 (6 years ago, contributed by Mifos.org) There are currently 51 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 2 : 1. ~300 emails on list in Q4 2022. Community changes, past quarter: New Committer: Bharath Gowda New PMC Members: Bharath Gowda, Javier Borkenztain, Victor Romero. ## Project Activity: The project added a Patch Release Process. The project released 1.8.2 and 1.7.2 on 28-November-2022, for a relatively minor issue and partly to further test the patch release process. We released 1.8.1 and 1.7.1 as patch releases on 25-November-2022 - covering the CVE below - which was a first test of our patch release process. On August 22nd, the project released Fineract 1.8.0. as covered in our last Board report. There is active development, and a new release (1.9) is anticipated in Q1 2023. Most of the contributions are coming in from commercial motivated interests. The project got a critical security vulnerability report. It was able to deliver a patch following the Apache process and issue the CVE-2022-44635 for the supported versions, and the community also got involved in creating patches for earlier versions. A more explicit Trademark policy was adopted: Fineract Trademarks Usage and Policy. [https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Trademarks+Usage+and+Policy]. We communicated out the trademark policy on dev. Fineract (along with Mifos) was deemed a Digital Public Good in 2022, leading to more scrutiny. [https://www.un.org/techenvoy/content/digital-public-goods] [https://digitalpubli cgoods.net//blog/accelerating-financial-inclusion-during-covid-19-and-beyond/] ## Community Health: In November we conducted a Survey of the community. We had 22 responses, which was probably not a sufficiently diverse sample, but nonetheless, we found useful insights. The project continues to enjoy a generally positive impression, mostly unchanged from surveys in 2019 and 2021. There are a larger number of people responding who found the project on the internet versus the connection to Mifos.org. The domains covered by the production users covered digital wallets (70%), online lending (64%), payment accounts (60%), traditional banking accounts (58%). --> Survey Results 2022 November. "https://cwiki.apache.org/confluence/display/FINERACT/Survey+Results+2022+November" In October we conducted an effort to close older issues. The decision was made by vote to close all issues that were older than 26 months and had no activity on them. We ended up closing about 300 tickets but we still have a lot of stale issues. 2022-October-21: Jira Clean Up. This remains an area of constructive dialog with some arguing to keep stale tickets visible. We began work on additional roadmap thinking in 2022, but have not completed this effort: Roadmap Q4 2022 (PROPOSED) "https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Trademarks+Usage+and+Policy" ApacheCON track PMC Chair James Dailey ----------------------------------------- Attachment Y: 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: BlazeDS Log4J dependencies ## Membership Data: Apache Flex was founded 2012-12-19 (10 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: Some guys are working on a BlazeDS release in order to fix the Log4J issues. https://lists.apache.org/thread/5mjwoc6tt1wcq24hkwlfv18y99f92ppr ## Community Health: There is nearly no mailing list activity at the Flex lists. Some Flex related discussions are held at the Apache Royale lists. Olaf Krüger has resigned as chairman, Harbs is the only one who has offered to take on the task so far: https://lists.apache.org/thread/s70fn0fjopr5s7sx096wcfmvvx7j3ccz Note from Olaf: I am totally inactive on the Flex project since a very long time. It looks like the remaining community still wants to keep the project alive instead of retiring it. I have done my best to prepare this and previous reports. ----------------------------------------- Attachment Z: Report from the Apache Fluo Project [Keith Turner] ----------------------------------------- Attachment AA: Report from the Apache Geronimo Project [Jean-Louis Monteiro] ## Description: The mission of Geronimo is the creation and maintenance of software related to Java2, Enterprise Edition (J2EE) container ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Geronimo was founded 2004-05-26 (19 years ago) There are currently 71 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2021-03-09. - No new committers. Last addition was Francois Papon on 2021-03-09. ## Project Activity: There are many sub projects and artifacts created under the Apache Geronimo umbrella. The community did have a discussion on the mailing list regarding Geronimo and its future. The discussion was around moving some projects to other Apache projects such as Karaf, TomEE to name a few. In the end, the community decided to refocus on shared projects and libraries and discontinue other development were there is no more traction. For instance, it looks like all MicroProfile implementations were pretty outdated and not used anymore. Apache TomEE was the last one using them, but it switched to SmallRye implementations because they were up to date. With the move to Jakarta, most of the specification artifacts we were creating under the groupId org.apache.geronimo.specs do not make sense anymore. We can use the artifact produced by the Eclipse foundation. On the other hand, some projects like the Jakarta Transaction implementation (Apache Geronimo Transaction Manager), or the Jakarta Mail implementation are still used by other Apache projects. The community is starting to embrace the jakarta namespace change and implement the latest Jakarta EE 10 versions. ## Community Health: The large increase of activity on the mailing list and on the codebase is related to the jakarta namespace migration and the development to support new Jakarta EE 10 specifications. ----------------------------------------- Attachment AB: Report from the Apache Griffin Project [William Guo] ## Description: The mission of Apache Griffin is the creation and maintenance of software related to a data quality solution for big data, including both streaming and batch mode. It offers an unified process to measure data quality from different perspectives. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Griffin was founded 2018-11-21 (4 years ago) There are currently 21 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - No new PMC members. Last addition was Chitral Verma on 2020-05-06. - No new committers. Last addition was Chitral Verma on 2020-05-05. ## Project Activity: - According to our release cadence, We will release next generation griffin-1.0.0 in H1 2023. ## Community Health: - Some contributors are working on our next generation griffin, maybe they will become our committer, after we merge it into our master branch. ----------------------------------------- Attachment AC: 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 (5 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: The project has a good rhythm with respect to 1.5.0 and has completed nearly all code changes relevant to the release, with the remaining work being mainly documentation updates. Recent releases: - 1.4.0 was released on 2022-01-01. - 1.3.0 was released on 2021-01-01. - 1.2.0 was released on 2020-06-28. ## Community Health: The community is active and healthy. user@ and dev@ mailing lists show typical levels of activity and engagement, with particular interest in the status of the 1.5.0 release and in a future migration away from AngularJS. JIRA activity has understandably dipped after public account signups were disabled. ----------------------------------------- Attachment AD: Report from the Apache Hadoop Project [Wei-Chiu Chuang] ## Description: The mission of Hadoop is the creation and maintenance of software related to Distributed computing platform ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Hadoop was founded 2008-01-15 (15 years ago) There are currently 242 committers and 123 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 Stephen O'Donnell on 2022-07-25. - Shilun Fan was added as committer on 2022-11-21 ## Project Activity: No new release was GA in this quarter. However, 3.3.5 is pending release. ## Community Health: Overall community activities seem to be getting lower, partly due to the holiday season. * dev@hadoop.apache.org had a 100% decrease in traffic in the past quarter (0 emails compared to 6) * mapreduce-issues@hadoop.apache.org had a 59% decrease in traffic in the past quarter (87 emails compared to 208) * user@hadoop.apache.org had a 50% decrease in traffic in the past quarter (26 emails compared to 51) * user-zh@hadoop.apache.org had a 100% increase in traffic in the past quarter (6 emails compared to 3) * yarn-dev@hadoop.apache.org had a 26% decrease in traffic in the past quarter (349 emails compared to 466) * yarn-issues@hadoop.apache.org had a 39% decrease in traffic in the past quarter (751 emails compared to 1227) * 236 issues opened in JIRA, past quarter (-50% change) * 191 issues closed in JIRA, past quarter (-41% change) * 310 commits in the past quarter (-21% change) * 73 code contributors in the past quarter (32% increase) * 254 PRs opened on GitHub, past quarter (-46% change) * 238 PRs closed on GitHub, past quarter (-36% change) ----------------------------------------- Attachment AE: Report from the Apache HAWQ Project [Lei Chang] ## Description: The mission of Apache HAWQ is the creation and maintenance of software related to a cloud native SQL query engine that combines the key technological advantages of an MPP database with the scalability and convenience of Hadoop ## Issues: There are no outstanding issues requiring board attention. Except that almost 50% of all PMCs not being subscribed to the private list. ## Membership Data: Apache HAWQ was founded 2018-08-15 (4 years ago) There are currently 69 committers and 46 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Wan Chiyang on 2022-01-25. - No new committers. Last addition was Wan Chiyang on 2021-02-20. ## Project Activity: 3.0.0.0 was released on 2021-08-18. Below are recent features and fixes: 1) HAWQ-1853. aarch64 port changes 2) HAWQ-1852. Fix find_udf 3) HAWQ-1851. Fix early free on savedSeqServerHost 4) HAWQ-1850. Fix life cycle of PlannedStmt and its resource 5) HAWQ-1847. change default value of gp_max_plan_slice to 36 6) HAWQ-1849. tag gpfdist --version as SQL version() ## Community Health: Overall community health is good. We have been performing extensive outreach to related projects, in order to attract new contributors. We'd like to take this opportunity to ask the board or others reading this report for guidance on how to make the PMCs subscribe to the private list. ----------------------------------------- Attachment AF: Report from the Apache HBase Project [Duo Zhang] ## Description: Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. hbase-thirdparty is a set of internal artifacts used by the project to mitigate the impact of our dependency choices on the wider ecosystem. hbase-connectors is a collection of integration points with other projects. The initial release includes artifacts for use with Apache Kafka and Apache Spark. hbase-filesystem contains HBase project-specific implementations of the Apache Hadoop FileSystem API. It is currently experimental and internal to the project. hbase-operator-tools is a collection of tools for HBase operators. Now it is mainly for hosting HBCK2. hbase-native-client is a client library in C/C++, in its early days. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache HBase was founded 2010-04-21 (13 years ago) There are currently 101 committers and 57 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 Xiaolin Ha on 2022-04-06. - Liangjun He was added as committer on 2022-11-29 - Rushabh Shah was added as committer on 2022-12-06 ## Project Activity: Recent releases: 2.5.2 was released on 2022-12-03. hbase-thirdparty-4.1.3 was released on 2022-11-15. 2.4.15 was released on 2022-10-28. 2.5.1 was released on 2022-10-28. hbase-thirdparty-4.1.2 was released on 2022-10-10. We finally find a way to publish binaries and artifacts compiled with hadoop3. The guys from the Phoenix community confirmed that the solution worked perfectly. And the Hudi project could also be benefited. https://lists.apache.org/thread/y05gspk4mnxsz6nk7hc5ots8wt50366b https://issues.apache.org/jira/browse/HBASE-27434 https://issues.apache.org/jira/browse/HBASE-27442 https://github.com/apache/hbase/pull/4917 The self registration of jira.a.o had been closed by infra team due to spam, unfortunately HBase uses jira for issuing track. After discussion, we decided to let users send a request email to private@hbase and let PMC members to request a jira account for the contributor. We also changed our readme page to mention this change. https://lists.apache.org/thread/vgy1n8brdoxqg9qs7752hg8otjcnhyoz https://issues.apache.org/jira/browse/HBASE-27513 ## Community Health: - Mailing list activity: dev@hbase.apache.org: 956 subscribers(952 in the previous quarter) user@hbase.apache.org: 1987 subscribers(1994 in the previous quarter) user-zh@hbase.apache.org 78 subscribers(77 in the previous quarter) - JIRA activity: 128 issues opened in JIRA, past quarter (-46% change) 120 issues closed in JIRA, past quarter (-42% change) - Commit activity: 413 commits in the past quarter (-28% change) 42 code contributors in the past quarter (-14% change) - GitHub PR activity: 132 PRs opened on GitHub, past quarter (-42% change) 126 PRs closed on GitHub, past quarter (-48% change) We now have more than 400 invididual contributors(401 till now) on the github statistic page! The development activity was still decreased. This is partly because we are still waiting for the final features to be landed on master and branch-2, i.e, the replication improvements and backup support, so we can cut branch-3 and branch-2.6 and start to making 3.0.0 and 2.6.0 release. Hope we can cut these two branches in the next quarter and make more releases. ----------------------------------------- Attachment AG: Report from the Apache Helix Project [Junkai Xue] ----------------------------------------- Attachment AH: Report from the Apache Iceberg Project [Ryan Blue] ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for January 2023 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 30 podlings incubating. Podlings made 4 distinct releases. This month we were missing reports from Annotator, Marvin-AI and PonyMail. There will be asked to report next month. Marvin-AI has not responded to the PPMC roll call, there has been little activity on the mailing list, and the IPMC has initiated discussions to retire. There are also discussions on retiring Heron. Annotator may need new mentors and has been advised to seek help from the incubator. We have three new volunteers as incubator shepherds, and it's looking good so far. Kyuubi, bRPC, Sedona, and Linkis graduated last month, and more podlings may graduate in the next few months, including Flagon. Tuweni has started graduation discussions, but because the community is highly dependent on a single contributor, IPMC expressed concerns about the diversity of the community. KIE has started a vote to join the incubator. ## Community ### New IPMC members: - None ### People who left the IPMC: - None ## New Podlings - None ## Podlings that failed to report, expected next month - Annoator - Marvin-AI - PonyMail ## Graduations - bRPC - Kyuubi - Linkis - Sedona The board has motions for the following: - none ## Releases The following releases entered distribution during the month of December: - SeaTunnel 2.3.0 - Sedona 1.3.1 - EventMesh 1.7.0 - Uniffle 0.6.1 ## IP Clearance - None ## Legal / Trademarks - None ## Infrastructure ## Miscellaneous ## Credits ## Table of Contents [Baremaps](#baremaps) [Celeborn](#celeborn) [DataLab](#datalab) [EventMesh](#eventmesh) [Flagon](#flagon) [HugeGraph](#hugegraph) [Liminal](#liminal) [Livy](#livy) [Milagro](#milagro) [Pegasus](#pegasus) [Pekko](#pekko) [SeaTunnel](#seatunnel) [StreamPark](#streampark) [Teaclave](#teaclave) [Uniffle](#uniffle) -------------------- ## Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. ### Three most important unfinished issues to address before graduating: 1. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? ### How has the community developed since the last report? ### How has the project developed since the last report? ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other ### Date of last release: XXXX-XX-XX ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? ### Is the PPMC managing the podling's brand / trademarks? ### Signed-off-by: - [ ] (annotator) Nick Kew Comments: - [ ] (annotator) Tommaso Teofili Comments: - [ ] (annotator) Benjamin Young Comments: ### IPMC/Shepherd notes: PJF: In October podling report, it was suggested that maybe Annotator team should email general@incubator.apache.org to see if anyone is interested in joining as a mentor. Likewise, you might consider using the Annotator mailing lists and/or Social Media to see if you can expand the contributor community (to ultimately expand the PPMC). -------------------- ## Baremaps Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps. Baremaps has been incubating since 2022-10-10. ### Three most important unfinished issues to address before graduating: 1. Getting the code in compliance with Apache standards 2. Making releases 3. Growing the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? The community has stayed steady. ### How has the project developed since the last report? - We progressed on some critical licensing issues and made upstream contributions to Proj4J - We improved the web site - We made small steps toward a first release - We experimented with support for the 3D tiles next format ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? When the project entered incubation. ### Have your mentors been helpful and responsive? Yes, the mentors have been very helpful on several topics (community building, licensing, etc.) ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (baremaps) Bertrand Delacretaz Comments: - [ ] (baremaps) Martin Desruisseaux Comments: - [X] (baremaps) Julian Hyde Comments: Baremaps is progressing well. - [X] (baremaps) Calvin Kirs Comments: - [ ] (baremaps) George Percivall Comments: - [ ] (baremaps) Martin Desruisseaux Comments: ### IPMC/Shepherd notes: -------------------- ## Celeborn Celeborn is an intermediate data service for big data computing engines to boost performance, stability, and flexibility. Celeborn has been incubating since 2022-10-18. ### Three most important unfinished issues to address before graduating: 1. Publish our first release 2. Grow the community 3. Improve our website ### Are there any issues that the IPMC or ASF Board need to be aware of? * N/A ### How has the community developed since the last report? 1. Committed our LOGO 2. Resolved the suitable name search for "Apache Celeborn" 3. Improved our website ### How has the project developed since the last report? 1. Prepare and start voting for our first apache release 2. Support rolling upgrade 3. Support load-aware slot allocation ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: XXXX-XX-XX ### When were the last committers or PPMC members elected? * 2022-11-21, nafiyaix was added as new committer. ### Have your mentors been helpful and responsive? * Our memtors have been very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? * The VP, Brand has approved the project name. ### Signed-off-by: - [ ] (celeborn) Becket Qin Comments: - [X] (celeborn) Lidong Dai Comments: - [X] (celeborn) Willem Ning Jiang Comments: Podling is Working on the first release of ASF. - [X] (celeborn) Duo Zhang Comments: - [X] (celeborn) Yu Li Comments: From the dev mailing list discussion I could see the community is working actively towards the first apache release, and I believe the team could work it out in the next report cycle. ### IPMC/Shepherd notes: -------------------- ## DataLab DataLab is a platform for creating self-service, exploratory data science environments in the cloud using best-of-breed data science tools. DataLab has been incubating since 2018-08-20. ### Three most important unfinished issues to address before graduating: 1. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? No, there aren't any issues. ### How has the community developed since the last report? New committers or PPMCs have not been added since the last report. ### How has the project developed since the last report? -We’ve released DataLab version 2.6.0 -The graduation process is started ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: Started graduation process ### Date of last release: 2022-11-30 ### When were the last committers or PPMC members elected? The last committer was added on July 22, 2022. ### Have your mentors been helpful and responsive? Yes, our mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Brand and naming issues are absent. ### Signed-off-by: - [ ] (datalab) P. Taylor Goetz Comments: - [ ] (datalab) Henry Saputra Comments: - [X] (datalab) Furkan Kamaci Comments: DataLab has started the graduation process. Currently, there is no issue against it; the project is mature, and the community is healthy. ### IPMC/Shepherd notes: -------------------- ## EventMesh EventMesh is a dynamic cloud-native basic service runtime used to decouple the application and middleware layer. EventMesh has been incubating since 2021-02-18. ### Three most important unfinished issues to address before graduating: 1. More frequent code contributions 2. A steady release proces 3. Growing the community: more committers, more use cases ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? more than 120 new contributors joined. 10 new committers and 2 new PPMC member were added. ### How has the project developed since the last report? apache-eventmesh(incubating)-1.7.0 released ### 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: 2022-12-5 ### When were the last committers or PPMC members elected? 2022-12-4 ### Have your mentors been helpful and responsive? Mentors were all very nice and helpful. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (eventmesh) Francois Papon Comments: - [ ] (eventmesh) Junping Du Comments: - [X] (eventmesh) Jean-Baptiste Onofré Comments: I think eventmesh is close to graduation. The focus should be on the community build, so far so good. - [X] (eventmesh) Justin Mclean Comments: - [ ] (eventmesh) Von Gosling Comments: ### IPMC/Shepherd notes: Yeah, I agree with JB, let's have maturity model evaluation first. -------------------- ## Flagon Flagon is a software tool usability testing platform Flagon has been incubating since 2016-07-13. ### Three most important unfinished issues to address before graduating: 1. None 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? Apache Flagon passed a VOTE at IPMC to Graduate Flagon as a TLP. Awaiting Board action. Link to Thread: https://lists.apache.org/thread/9fvnpbpwfrvm23zljjlnfmqvq4n4nss9 ### How has the community developed since the last report? Flagon has continued to interface with new users and contributors through PRs, etc. ### How has the project developed since the last report? The community has added a number of new features supporting maintenance/modernization, as well as additional use-case examples. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: Awaiting Board action on IPMC Passed Graduation Resolution ### Date of last release: 2022-05-19 Apache Flagon UserALE.js 2.3.0 ### When were the last committers or PPMC members elected? - Kelsey Rassmann (6/2022) - Kymani Brown (6/2022) - Amir Ghaemi (6/2022) - Austin Bennett (5/2022) ### Have your mentors been helpful and responsive? Mentors were very helpful throughout graduation ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (flagon) Lewis John McGibbney Comments: - [ ] (flagon) David Meikle Comments: - [ ] (flagon) Tim Allison Comments: - [X] (flagon) Furkan Kamaci Comments: ### IPMC/Shepherd notes: -------------------- ## HugeGraph A large-scale and easy-to-use graph database HugeGraph has been incubating since 2022-01-23. ### Three most important unfinished issues to address before graduating: 1. Increase diversity contributors 2. Enhance core product functionality as mentioned in the initial goals 3. Stable release and planning ### 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? 13 new contributors since the last report ### How has the project developed since the last report? 1. Prepare and start voting for the first apache version 1.0.0 2. Support graph computing in stand-alone & k8s mode (OLAP) 3. Support a string of graph algorithms in OLTP mode 4. Using github projects & WIKI to manage and show the schedule ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2022-12-31 (start voting), 2023-01-xx (the final release) ### When were the last committers or PPMC members elected? None, but soon (after the release) ### Have your mentors been helpful and responsive? Yep, they remind us the release progress and we'll communicate more in the 2023 ### Is the PPMC managing the podling's brand / trademarks? None ### Signed-off-by: - [X] (hugegraph) Lidong Dai Comments: - [X] (hugegraph) Trista Pan Comments: Look forward to our first Apache release. It sounds great that we invovled more contributors. - [X] (hugegraph) Xiangdong Huang Comments: 22.12.31 should be the vote date of releasing the first version, not the final date. - [X] (hugegraph) Yu Li Comments: Suggest to have more public discussions in the mailing lists, and hopefully voting of the first apache release is a good start. - [X] (hugegraph) Willem Ning Jiang Comments: Podling is working on the first release. ### IPMC/Shepherd notes: -------------------- ## Liminal Apache Liminal is an end-to-end platform for data engineers and scientists, allowing them to build, train and deploy machine learning models in a robust and agile way. Liminal has been incubating since 2020-05-23. ### Three most important unfinished issues to address before graduating: 1. Grow developers community. 2. Adoption of the project by a few companies. 3. Integrations with eco-system projects. ### Are there any issues that the IPMC or ASF Board need to be aware of? NA ### Are there any issues that the IPMC or ASF Board need to be aware of? NA ### How has the community developed since the last report? NA ### How has the project developed since the last report? We have completed the SageMaker integration and next version is ready to be released. ### 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: 2022-03-10 ### When were the last committers or PPMC members elected? 2022-04-06 ### Have your mentors been helpful and responsive? They have been very responsive and helpful. ### Is the PPMC managing the podling's brand / trademarks? NA ### Signed-off-by: - [X] (liminal) Jean-Baptiste Onofré Comments: Community build is the main target right now. - [ ] (liminal) Henry Saputra Comments: - [ ] (liminal) Uma Maheswara Rao G Comments: - [X] (liminal) Davor Bonaci Comments: - [ ] (liminal) Liang Chen Comments: ### IPMC/Shepherd notes: It's has been a while since the last relase. -------------------- ## Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. ### Three most important unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Focus on Contributors rather than primarily on Users (Docs for processes) ### 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? A proposal to revitalize the PPMC and committers was accepted and execution has begun. A number of new mentors and committers have been added to the Livy podling. ### How has the project developed since the last report? An initial strategic direction was part of the proposal and details the steps toward the iniital from the new community and the migration of innovations from the external forks back into the project. A set of JIRAs have been identified for the next release (0.8.0) which consist of low hanging fruit from previously stranded pull requests, meta tasks for empowering contributors and CVE remediation process and tasks. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: Nearing graduation in code stability but without a dev community supporting it, the devs have moved to working on forks due to lack of PPMC availability. Dev community is emerging and working toward an 0.8.0 release. ### Date of last release: 2021-02-02 ### When were the last committers or PPMC members elected? December 2022 ### Have your mentors been helpful and responsive? No issues with mentors to report. ### Is the PPMC managing the podling's brand / trademarks? No issues to report. ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: The activity has restarted, mostly maintenance. I think we can have new features and improvements soon, helping to extend the community. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [ ] (livy) Sunil Govindan Comments: ### IPMC/Shepherd notes: -------------------- ## Milagro Milagro is core security infrastructure and crypto libraries for decentralized networks and distributed systems. Milagro has been incubating since 2015-12-21. ### Three most important unfinished issues to address before graduating: 1. Introduce policies for correct corporate involvement (see https://github.com/orgs/apache/projects/171/views/1) 2. Continue to build relevant and useful crypto libraries and applications for decentralized networks in order to grow the ecosystem of users and contributors to the project. 3. Improve automated quality pipelines, improve existing releases and demonstrate improved compliance with the Apache Way. ### Are there any issues that the IPMC or ASF Board need to be aware of? Last month issues were resolved. No issues are known as of now. ### How has the community developed since the last report? - Riccardo Iaconelli has been chosen by the community as new committer and PPMC member. - The efforts of the community are concentrated on project graduation ### How has the project developed since the last report? - The first release of a new component (libmpc 0.1) happened successfully - The project has a new, modern website! The website is deployed directly from git using a Continuous Delivery pipeline - The path to graduation has been mapped [in a GitHub project](https://github.com/orgs/apache/projects/171/views/1) ### 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: 2022-11-11 ### When were the last committers or PPMC members elected? December 2022 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No third party are using the brand's name incorrectly ### Signed-off-by: - [ ] (milagro) Nick Kew Comments: - [X] (milagro) Jean-Frederic Clere Comments: ### IPMC/Shepherd notes: -------------------- ## Pegasus Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance. Pegasus has been incubating since 2020-06-28. ### Three most important unfinished issues to address before graduating: 1. Grow the community(attracting more committers, contributors, users). 2. Make more releases in ASF policy regularly. 3. Improve the Pegasus project performance, stability, and usage scenarios. ### 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? An offline meetup in Beijing has been held on Nov 5th, 2022. ### How has the project developed since the last report? 2.4.0 has been released on Nov 1st, 2022. ### 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: 2022-11-05 ### When were the last committers or PPMC members elected? 2022-12-31, PPMC member: Dan Wang(GitHub ID: empiredan) ### Have your mentors been helpful and responsive? Yes, our mentors gave us a lot of help, including IP clearance, version release, and etc. ### Is the PPMC managing the podling's brand / trademarks? No issues that we are aware of. ### Signed-off-by: - [X] (pegasus) Duo zhang Comments: - [ ] (pegasus) Liang Chen Comments: - [ ] (pegasus) Von Gosling Comments: - [ ] (pegasus) Liu Xun Comments: ### IPMC/Shepherd notes: -------------------- ## Pekko Pekko is a toolkit and an ecosystem for building highly concurrent, distributed, reactive and resilient applications for Java and Scala. Pekko has been incubating since 2022-10-24. ### Three most important unfinished issues to address before graduating: 1. Complete the work on updating the file headers and docs to reflect the new branding and licensing. 2. Get the core web site and documentation up. 3. Get a milestone release done - at least for the core modules. This would facilitate the wider OSS community. We would hope that other OSS projects that currently support Akka would look to also support Apache Pekko. ### Are there any issues that the IPMC or ASF Board need to be aware of? * Nothing of note. ### How has the community developed since the last report? * There are 24 PPMC members. There are no extra committers (i.e. 24 committers too). A good proportion of these are active. ### How has the project developed since the last report? * Very early days. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: * None yet. ### When were the last committers or PPMC members elected? * None added since we started the PPMC. ### Have your mentors been helpful and responsive? * There were some knotty issues to discuss about how to manage the license headers and similar issues but the conversations were very constructive. ### Is the PPMC managing the podling's brand / trademarks? * The Pekko project has been widely discussed in Social Media and blogs. No issues to report. * Pekko project did an initial Trademark search to verify the name availability for software products * VP, Brand has approved the name (https://s.apache.org/h2cwg) ### Signed-off-by: - [X] (pekko) PJ Fanning Comments: Might be worth laying out a high level set of tasks and seeing if we can get volunteers to take on specific tasks. - [X] (pekko) Justin McLean Comments: - [ ] (pekko) Roman Shaposhnik Comments: - [ ] (pekko) Wu Sheng Comments: - [X] (pekko) Ryan Skraba Comments: Good starting momentum. - [X] (pekko) JB Onofré Comments: Podling is ramping up. - [X] (pekko) Claude Warren Comments: Community is beginning to coalesce. The main issues facing the development of the community is the ability to progress with development, we have a number of people asking what they can do, but many actions blocked by lack of consensus around specific topics. Now that the outstanding legal questions have been answered I think the project will begin to progress more rapidly. ### IPMC/Shepherd notes: -------------------- ## SeaTunnel SeaTunnel is a very easy-to-use ultra-high-performance distributed data integration platform that supports real-time synchronization of massive data. SeaTunnel has been incubating since 2021-12-09. ### Three most important unfinished issues to address before graduating: None, we plan to graduate. ### 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 ushers in 33 new contributors, bringing the total number to 157 now,300+ pull requests have been merged since SeaTunnel entered the last report. We participated in the meetup held by ALC India and gained some new contributors and users. ### How has the project developed since the last report? We released SeaTunnel Zeta, which is the result of six months of hard work by the community and an engine specially developed for data synchronization. ### 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: Dec 29, 2022 ### When were the last committers or PPMC members elected? - We elected Guangdong and Liu Li as a committer. - We elected Chao Tian and Jun Gao as a PPMC. ### Have your mentors been helpful and responsive? Yes, always responsive and helpful. They gave a lot of great suggestions on community building. ### Is the PPMC managing the podling's brand / trademarks? No known issues, but further investigation is still required by the SeaTunnel community. ### Signed-off-by: - [X] (seatunnel) Zhenxu Ke Comments: - [X] (seatunnel) William-GuoWei Comments: - [X] (seatunnel) Lidong Dai Comments: - [ ] (seatunnel) Ted Liu Comments: - [ ] (seatunnel) Kevin Ratnasekera Comments: - [ ] (seatunnel) JB Onofré Comments: - [ ] (seatunnel) Willem Ning Jiang Comments: ### IPMC/Shepherd notes: -------------------- ## StreamPark StreamPark is a streaming application development platform. StreamPark has been incubating since 2022-09-01. ### Three most important unfinished issues to address before graduating: 1. cleanup dependencies Licenses and Make first StreamPark release at Apache 2. Establish better development specifications and improve official website documentation 3. Attract more active contributors and committers to build a diverse community. ### 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. Added 1 new contributors, the total contributors is 88 now 2. Preparing for the next round of first releases vote 3. Good communication and collaboration, development progressing normally ### How has the project developed since the last report? We are preparing for the release of the first apache version, cleanup licenses of project, and learning the release process ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: No release yet ### When were the last committers or PPMC members elected? 2022-11-29 we elected Chunjin Mu as a StreamPark committer ### Have your mentors been helpful and responsive? Yes, always responsive and helpful. ### Is the PPMC managing the podling's brand / trademarks? The Brand VP has approved the project name. see it at https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-203 ### Signed-off-by: - [X] (streampark) tison Comments: - [ ] (streampark) Willem Ning Jiang Comments: - [ ] (streampark) Stephan Ewen Comments: - [ ] (streampark) Thomas Weise Comments: - [X] (streampark) Duo Zhang Comments: ### IPMC/Shepherd notes: -------------------- ## Teaclave Teaclave is a universal secure computing platform. Teaclave has been incubating since 2019-08-20. ### Three most important unfinished issues to address before graduating: - Improve project structure and documentation - Grow the community (attracting more committers, contributors, users) - Publish Apache releases (resolving logistics on Apache release) ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? Since the last report, we have organized two virtual meetups. For each meetup, we have write-ups published on the Teaclave blog. - Teaclave Meetup #14: https://teaclave.apache.org/blog/2022-12-14-teaclave-meetup-14/ - Teaclave Meetup #15: https://teaclave.apache.org/blog/2022-12-21-teaclave-meetup-15/ We have accepted JavaEnclave to Apache Teaclave (incubating) Proposal. The new project name is Teaclave Java TEE SDK. Its repository is https://github.com/apache/incubator-teaclave-java-tee-sdk. Refer [link](https://teaclave.apache.org/blog/2022-10-18-accepting-java-enclave-pr oposal/) for more information. ### How has the project developed since the last report? Teaclave Faas Platform - Merged PRs: https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-10-01..2023-01-11+base%3Amaster+ Teaclave TrustZone SDK - Merged PRs: https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-10-01..2023-01-11+base%3Amaster+ Teaclave SGX SDK - Merged PRs in master branch: https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-10-01..2023-01-11+base%3Amaster+ - Merged PRs in v2.0.0-preview branch: https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-10-01..2023-01-11+base%3Av2.0.0-preview Teaclave Java TEE SDK New github repository apache/incubator-teaclave-java-tee-sdk is created. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2023-01-06: Apache Teaclave (incubating) Java TEE SDK v0.1.0-rc.1 ### When were the last committers or PPMC members elected? - 2023-01-04: He Sun (Apache ID: hsun), Committer ### Have your mentors been helpful and responsive? Yes, our mentors work responsively to help us with electing new mentors, developing new features, fixing bugs, and expanding the community.. ### Is the PPMC managing the podling's brand / trademarks? We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175) ### Signed-off-by: - [ ] (teaclave) Felix Cheung Comments: - [X] (teaclave) Furkan Kamaci Comments: - [ ] (teaclave) Jianyong Dai Comments: - [ ] (teaclave) Matt Sicker Comments: - [ ] (teaclave) Zhijie Shen Comments: - [ ] (teaclave) Gordon King Comments: ### IPMC/Shepherd notes: -------------------- ## Uniffle Uniffle is an unified Remote Shuffle Service Uniffle has been incubating since 2022-06-06. ### Three most important unfinished issues to address before graduating: Promote the project and grow the user and dev community ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? 1. 9 contributors from different affiliations contributed to Uniffle project. 2. 104 issues have beed created, among this 58 were discussed and resolved. 3. 7 discussions were occurred. ### How has the project developed since the last report? 1. 104 issues has been created, among this 58 issues were closed. 131 PRs has been created, among this 121 PRs were merged. 2. We have released version 0.6.0 and 0.6.1 3. We have a share on 2022 Shanghai Hadoop Meetup to let more people know Uniffle ### 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: 2022-12-09 ### When were the last committers or PPMC members elected? Kaijie Chen ### Have your mentors been helpful and responsive? Yes, they're very helpful in guiding the podling project. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (uniffle) Felix Cheung Comments: - [ ] (uniffle) Junping Du Comments: - [X] (uniffle) Liu Xun Comments: - [ ] (uniffle) Weiwei Yang Comments: - [ ] (uniffle) Zhankun Tang Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AJ: Report from the Apache InLong Project [Charles Zhang] ## Description: The mission of Apache InLong is the creation and maintenance of software related to a one-stop data integration framework that provides automatic, secure, and reliable data transmission capabilities. InLong supports both batch and stream data processing at the same time, which offers great power to build data analysis, modeling, and other real-time applications based on streaming data ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache InLong was founded on 2022-06-15 (7 months ago) There are currently 40 committers and 25 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. The last addition was Junjie Chen on 2022-07-10. - There is a candidate PMC member who is in the voting process. - Cisco Zhou was added as a committer on 2022-10-25 - Xin Gong was added as a committer on 2022-11-08 - Fan Deng was added as a committer on 2022-12-20 - Zixuan Zhao was added as a committer on 2022-12-20 ## Project Activity: In the past quarter, InLong has successively released two versions, 1.4.0 and 1.5.0. The just-released version 1.5.0 mainly completes the following things, including: - Added new load data node for StarRocks, Hudi, Doris, Elasticsearch, etc. - Optimize Dashboard experience. - Refactoring the MQ management model. - Add dirty data processing. - Full link Apache Kafka support. - TubeMQ C++/Python SDK supports production. Meetups and Conferences in the past month: - Attend Doris Summit 2022 and share the topic — "Integration of Apache InLong and Apache Doris, sharing of the whole database migration proposal". - Attend the Hudi Community meetup and share the topic - "The new paradigm for InLong supports of data lake Hudi". - The community summaries year-end review and 2023 planning. ## Community Health: The community health looks good overall. In the latest month, - 9 new code contributors contributed to the project (127 in total). - 178 commits to master (+35% increase). - 35 active contributors (+16% increase). - 186 PRs opened on GitHub (+30% increase). - 188 issues closed on GitHub (+10% increase). ----------------------------------------- Attachment AK: Report from the Apache Isis Project [Johan Doornenbal] ## Description: The mission of Isis is the creation and maintenance of software related to Framework for rapidly developing domain-driven apps in Java ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Isis was founded 2012-10-17 (10 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 Jörg Rade on 2020-04-12. - No new committers. Last addition was Jörg Rade on 2020-03-23. ## Project Activity: In the last quarter we released one further milestone M9 [1], which followed on quickly from M8 to address two security CVEs. The development work continues to be focussed towards v2.0, which is to "re-platform" the framework to run on top of Spring Boot. Development work for this is now pretty much completed, and we are now working on some of the supporting materials for our first RC1, in particular the "demo app" which acts as both a training material and for regression testing [2], [3]. We hope to release RC1 in the coming quarter. RC1 will also be the first release under the new name, Apache Causeway. [4] We have tackled some of the larger changes for this, in particular the internal code changes so that all code now resides under org.apache.causeway rather than org.apache.isis. In the coming quarter we will aiming to address many of the remaining tasks as identified in our umbrella "rename" issue [5]. To assist developers make the change to the new name, we are now providing informal nightly builds [6]. We are also maintaining a branch and providing informal builds for what will eventually be v3.0 of the framework, based on Spring Boot 6 and JDK 17. ## Community Health: This is a mature project and the framework is generally stable. We are continuing to see good engagement on and new sign-ups to our slack channel, which the community seems to much prefer over the users mailing list. Nevertheless, we continue to ensure that all relevant information are cross-posted to users@ and dev@ where necessary. ## References (links) [1] https://isis.apache.org/relnotes/2.0.0-M9/2022/2.0.0-M9/relnotes.html [2] https://github.com/apache/isis/tree/master/examples/demo [3] https://demo-wicket-jpa-snapshot.apps.causeway.dev/ [4] https://whimsy.apache.org/board/agenda/2022-09-21/Change-Isis-Name [5] https://issues.apache.org/jira/browse/ISIS-3130 [6] https://github.com/apache-causeway-committers/causeway-nightly ----------------------------------------- Attachment AL: Report from the Apache James Project [Benoit Tellier] ## Description: The Apache James Project delivers a rich set of open source modules and libraries, written in Java, related to Internet mail which build into an advanced extensible mail server running on the JVM. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache James was founded 2003-01-22 (20 years ago) There are currently 42 committers and 17 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 Karsten Otto on 2022-09-20. - No new committers. Last addition was Jean Helou on 2022-06-17. ## Project Activity: Recent releases: JSIEVE-0.8 was released on 2022-11-04. JSPF-1.0.2 was released on 2022-11-04. MIME4J-0.8.8 was released on 2022-11-04. JDKIM-0.3 was released on 2022-10-17. JAMES-3.7.2 was released on 2022-10-14. The project also devoted time to implement numerous IMAP extensions and make it's design modular. ## Community Health: server-user@james.apache.org had a 59% increase in traffic in the past quarter (67 emails compared to 42) 454 commits in the past quarter (29% increase) server-dev@james.apache.org had a 50% decrease in traffic in the past quarter (318 emails compared to 636) 44 issues opened in JIRA, past quarter (no change) 60 issues closed in JIRA, past quarter (106% increase) Overall the community numbers are stables. We notice that contributors tends to more discuss on Github or JIRA than on the mailing lists. ----------------------------------------- Attachment AM: Report from the Apache jclouds Project [Andrew Gaul] There are no issues requiring board attention A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We continue to discuss the low activity of the project and the impending lack of quorum for releases. Several individuals proposed joining the jclouds team, including members from the Brooklyn and Karaf projects, but subsequent discussion suggested insufficient bandwidth to contribute and they have not filed any issues, submitted any PRs, or otherwise participated in the project. As such, moving the project to the attic soon seems the most likely next step. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.6.0 in 2Q2023 which may be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14. ----------------------------------------- Attachment AN: Report from the Apache Jena Project [Andy Seaborne] ## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Jena was founded 2012-04-18 (11 years ago) There are currently 18 committers and 13 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 Aaron Coburn on 2019-01-22. - No new committers. Last addition was Greg Albiston on 2019-07-08. ## Project Activity: Jena released 4.7.0. The release included feature contributions from 6 people who are not PMC members or project committers. The web site has also seen pull-requests from external contributors. This was a significant release with two major features. LATERAL is a addition to the SPARQL query language being developed by the semantic web community. RDF Patch is a file format for recording changes to RDF data and it can be used recording changes, incremental backup and also as part of high availability replication of Jena Fuseki triplestore instances. The project deal with one security issue in a component that was retired from Jena sometime ago. CVE-2022-45136 ## Community Health: The significant change in email on dev@ is in part due to the release because the project needed to address a random test instability. Otherwise, the quarter has been the usual situation of more user requests than can be addressed within the resources of the project. ----------------------------------------- Attachment AO: Report from the Apache JMeter Project [Bruno Demion] ----------------------------------------- Attachment AP: Report from the Apache Johnzon Project [Jean-Louis Monteiro] ## Description: The mission of Johnzon is the creation and maintenance of software related to JSR-353 compliant JSON parsing; modules to help with JSR-353 as well as JSR-374 and JSR-367 ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Johnzon was founded 2016-04-20 (7 years ago) There are currently 8 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Reinhard Sandtner on 2016-08-30. - No new committers. Last addition was Jonathan Gallimore on 2018-05-09. ## Project Activity: Apache Johnzon was pretty stable so only few maintenance releases happened to fix minor bugs. The community is moving 1.x code base to maintenance and is switching the main development branch to 2.x. Jakarta EE 10 just got released and both JSON-B 3.0.0 and JSON-P 2.1.1 received new features and API changes. So it's time to implement the new version. This is also the opportunity to get the code base migrated to the jakarta namespace and get away from the shade approach. The community is also willing to make Apache Johnzon an official Jakarta compatible implementation. So there will be some investment to pass the TCK for both JSON-P and JSON-B. ## Community Health: Based on the jakarta namespace switch and the new Jakarta EE 10 release, the community seems to be a bit more active, so are the committers. ----------------------------------------- Attachment AQ: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez] ## Description: The mission of JSPWiki is the creation and maintenance of software related to Leading open source WikiWiki engine, feature-rich and built around standard JEE components (Java, servlets, JSP). ## Issues: There are no issues requiring board attention. ## Membership Data: Apache JSPWiki was founded 2013-07-17 (9 years ago) There are currently 14 committers and 8 PMC members in this project. The Committer-to-PMC ratio is 7:4. Community changes, past quarter: - No new PMC members. Last addition was Dave Koelmeyer on 2016-04-06. - No new committers. Last addition was Dave Koelmeyer on 2016-04-06. ## Project Activity: Again, quiet period, as noted on the previous report, we have switched to 2.12.0, which requires JDK-11, upgraded some libraries, and we have fixed several XSS vulnerabilities present on some JSPWiki plugins, which will warrant a CVE. We got another vulnerability report, which was rejected. Last release was 2.11.3 on 2022-08-02. ## Community Health: Traffic on both MLs had an increase compared with last quarter, most due to last quarter being an almost no activity quarter. There is enough people to provide project oversight. ----------------------------------------- Attachment AR: Report from the Apache Kudu Project [Andrew Wong] ## Description: The mission of Apache Kudu is the creation and maintenance of software related to a distributed columnar storage engine built for the Apache Hadoop ecosystem. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Kudu was founded 2016-07-19 (6 years ago) There are currently 27 committers and 27 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Bankim Bhavsar on 2020-04-17. - No new committers. Last addition was Bankim Bhavsar on 2020-04-17. ## Project Activity: 1.16.0 was released on 2022-04-11. 1.15.0 was released on 2021-06-22. 1.14.0 was released on 2021-01-27. ## Community Health: - Traffic to dev@kudu.apache.org had a 66% increase this past quarter, with an upcoming release being proposed. - Public IM activity over the community Slack channel is down, measured by daily active users (-15%) and weekly active users (-13%). - Development activity measured in the number of commits was steady (+4%). Activity measured in open and closed issues was mixed (+22% opened, -12% closed). - Development activity measured in number of contributors was steady (no change). ----------------------------------------- Attachment AS: Report from the Apache Kyuubi Project [Kent Yao] ## Description: Apache Kyuubi™ is a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Kyuubi was founded on 2022-12-21. There are currently 17 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: - Project graduated as a TLP on 2022-12-21 - [SUBPROJECT] Create kyuubi-client repo for our java-based client libaries - [RELEASE] Released 1.6.1-incubating on 2022-11-16 - [FEATURE] Introduce Trino Frontend ## Community Health: - Users and developers like to report issues/features and ask questions on github, the team takes a active response on issue resolution. Average issue resolution time keeps lower than 1d. We use dev maliing list for both dev and user discussions. We didn‘t see much traffic for use questions compared to the discussions on github. But important decisions are made there. - Commit activity has held pretty steady about 90~110/month in the past quarter. - 40 code contributors in the past quarter. ----------------------------------------- Attachment AT: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description: The mission of Libcloud is the creation and maintenance of software related to Unified interface to the cloud ## Issues: There are no issues which require board attention at this time. ## Membership Data: Apache Libcloud was founded 2011-05-19 (10 years ago) There are currently 24 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Dimitris Moraitis on 2021-05-07. - No new committers. Last addition was Dimitris Moraitis on 2021-05-02. ## Project Activity: Activity on Github continues to be OK. Libcloud v3.6.1 has been released in October 2022 and Libcloud v3.7.0 on January 8th, 2023. As part of the last few major releases (v3.6.0, v3.7.0) we have tried to align ourselves better with other popular Python projects so we have dropped support for Python versions which have been EOL for a year or more now (Python 3.6, Python 3.7). We also continue to update our code and packaging metadata to support latest Python versions. We now have a CI running against Python 3.11 which has been released recently and offers nice performance improvements in a lot of situations. Very likely Libcloud users should also benefit from some of those optimizations since the library is pure Python. ## Community Health: Most of the activity happens on Github. Since the last report (August 2022), we have received 15 pull requests and (https://github.com/apache/libcloud/pulls) 18 issues have been opened (https://github.com/apache/libcloud/issues). In early January 2023, a voting thread has been started for a new committer and a PMC member. We are hoping we will have a new person join our project in the near future once the vote closes. As part of the recent Twitter related developments, we are also looking into moving project updates and news from Twitter to another network such as Mastodon. P.S. I apologize for missing reporting in December, 2022 - I was on the road traveling. ----------------------------------------- Attachment AU: Report from the Apache Linkis Project [Shuai Di] ## Description: Linkis builds a computation middleware layer to facilitate connection, governance and orchestration between the upper applications and the underlying data engines. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Linkis was founded 2022-12-21 (21 days ago) There are currently 33 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: Apache Linkis is preparing to release 1.3.1. This version have 35+ contributors participated, 11 new contributors added (currently:127) and 10+ new features included. Software development activity: - We are preparing to release 1.3.1 in the coming week. At this time, we are focusing on trying to develop 1.3.2, and 1.3.2 looks to achieve these goals: - Supports spark submission of jar tasks. - Supports automatic addition of tenant tags. - Supports User Creator IP task interception and other features. Meetups and Conferences: - The community meetings is discussing the roadmap for the 2023. ## Community Health: Overall community health is good, the status is "no change" because it's the first report(2023-01-10). - 66 PRs opened on GitHub in the past month (no change). - 58 issues closed on GitHub in the past month (no change). ----------------------------------------- Attachment AV: Report from the Apache Lucene.Net Project [Shad Storhaug] ----------------------------------------- Attachment AW: Report from the Apache MADlib Project [Aaron Feng] ----------------------------------------- Attachment AX: Report from the Apache Mahout Project [Andrew Musselman] ----------------------------------------- Attachment AY: Report from the Apache Maven Project [Karl Heinz Marbaise] ----------------------------------------- Attachment AZ: Report from the Apache Mesos Project [Qian Zhang] ----------------------------------------- Attachment BA: Report from the Apache MINA Project [Guillaume Nodet] ----------------------------------------- Attachment BB: Report from the Apache MXNet Project [Sheng Zha] ----------------------------------------- Attachment BC: Report from the Apache MyFaces Project [Bernd Bohmann] ## Description: The mission of MyFaces is the creation and maintenance of software related to JavaServer(tm) Faces implementation and components ## Issues: There are no issues. ## Membership Data: Apache MyFaces was founded 2005-02-23 (18 years ago) There are currently 80 committers and 46 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 Henning Nöth on 2021-06-01. - No new committers. Last addition was Melloware on 2021-05-11. ## Project Activity: - Apache MyFaces Core the community is still heavily working on Faces 4.0. Next Release Candidate will include the quarkus extension. - Apache Tobago the community is working for 5.x. and and Jakarta migration(tobago-6.x). - Recent releases: myfaces-core-4.0.0-RC3 was released on 2023-01-03. tobago-5.4.0 was released on 2022-12-12. tobago-4.6.0 was released on 2022-11-06. myfaces-core-4.0.0-RC2 was released on 2022-10-24. tobago-5.3.0 was released on 2022-10-10. ## Community Health: - Apache MyFaces Core is healthy. UI-Component Sets: - Apache Tobago is healthy. - Apache Trinidad is in maintenance mode. Last developer commit was Sept 2017. - Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016. Last commit on behalf of a contributor was May 2016. Add-ons and Extensions: - Apache MyFaces Portlet Bridge is in maintenance mode. Last developer commit was Jan 2014. Last commit on behalf of a contributor was May 2015. - Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache DeltaSpike so new development happens there. Last commit March 2014. - Apache MyFaces Orchestra is in maintenance mode. New projects use CDI and DeltaSpike instead. Last commit on behalf of a contributor was August 2016. - Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014. - Apache MyFaces Commons is in maintenance mode. Last commit August 2012. - Apache MyFaces Ext-Scripting is in maintenance mode. Last commit Sept 2017. - Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last commit May 2017. ----------------------------------------- Attachment BD: Report from the Apache Mynewt Project [Szymon Janc] ## Description: The mission of Apache Mynewt is the creation and maintenance of software related to an embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android ## Issues: None ## Membership Data: Apache Mynewt was founded 2017-06-21 (6 years ago) There are currently 36 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24. - No new committers. Last addition was Krzysztof Kopyściński on 2021-01-26. ## Project Activity: Project is preparing for next release in Q1 2023. Mostly working on improving support Nordic nRF5340 chip and tooling. ## Community Health: We see drop in activity on github and mailinglist, although "core" developers are active. ----------------------------------------- Attachment BE: Report from the Apache NiFi Project [Joe Witt] ## Description: The mission of NiFi is the creation and maintenance of software related to providing an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi MiNiFi is an edge data collection agent built to seamlessly integrate with and leverage the command and control of NiFi. There are both Java and C++ implementations. Apache NiFi Registry is a centralized registry for key configuration items including flow versions, assets, and extensions for Apache NiFi and Apache MiNiFi. Apache NiFi Nar Maven Plugin is a release artifact used for supporting the NiFi classloader isolation model. Apache NiFi Flow Design System is a theme-able set of high quality UI components and utilities for use across the various Apache NiFi web applications in order to provide a more consistent user experience. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache NiFi was founded 2015-07-14 (7 years ago) There are currently 61 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Nathan Gough on 2022-09-06. - No new committers. Last addition was Peter Gyori on 2022-09-22. ## Project Activity: The NiFi community released NiFi 1.19.0 in November 2022 and NiFi 1.19.1 in December 2022 as well as NiFi MiNiFi CPP 0.13.0 in December. The community also discussed and voted up release goals for Apache NiFi 2.0. We are now in the process of executing on converting our main line to be the go forward NiFi 2.0 line while branching to continue to support the 1.x line. NiFi 2.0 will provide a necessary technical debt reduction while still heavily focusing on ensuring existing flows and setups are easily migrated. We will also move away from Java 8 to at least Java 11 consistent with what we're seeing with important dependencies. ## Community Health: Health of the community remains strong. We did not add any committers or PMC members this quarter though we did have a brief discussion on it. We simply didn't pursue it over the break. Despite the usual slowdown we see over the December Holidays and New Years times activity remains strong across the mailing lists, slack, JIRA, and Github. We have already nearly 100 JIRAs and commits for what will be NiFi 1.20.0 and we're conducting appropriate security work. Our general slack channel has just under 2500 people in at the time of this writing and remains an active and responsive channel. Growth of 100 to 200 users per quarter seems steady for nearly a year now. ----------------------------------------- Attachment BF: Report from the Apache Nutch Project [Sebastian Nagel] ## Description: Apache Nutch is a highly extensible and scalable open source web crawler software project based on Apache Hadoop® data structures and the MapReduce data processing framework. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Nutch was founded 2010-04-21 (12 years ago) There are currently 21 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new committers and PMC members. Last addition was Shashanka Balakuntala Srinivasa on 2020-08-01. ## Project Activity: Nutch 1.19 was released on 2022-08-22. Work on the next Nutch release continues. One focus was on resolving dependency conflicts around logging libraries (slf4j2 and reload4j) to finally remove Log4j 1.x from all Nutch plugins. ## Community Health: The number of contributions (Jira issues, commits, activity on the mailing lists) is on a low but steady level. ----------------------------------------- Attachment BG: Report from the Apache NuttX Project [Alin Jerpelea] ## Description: The mission of Apache NuttX is the creation and maintenance of software related to a mature, real-time embedded operating system (RTOS) ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache NuttX was founded 2022-11-16 (2 months ago) There are currently 26 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - 1 PMC added to the project since the last report (Guiding Li) - No new committers were added. ## Project Activity: ### Next release NuttX-12.0.0-rc1 is currently submitted for community vote and release. ### Date of last release: NuttX-11.0.0 was released on 2022-10-12. ## Community Health: - The NuttX community is healthy. The project sees on average 10-20 commits per day from numerous contributors. - Virtually all communications have moved from old venues to dev@nuttx.apache.org. The dev list contains 262 subscribers and is the home of most development discussions and user questions. - GitHub's PRs and Issues also have their own discussions. - We are seeing new contributors to the project through GitHub.s. Commit activity: 1461 commits in the past quarter (25% increase) 106 code contributors in the past quarter (6% increase) GitHub PR activity: 887 PRs opened on GitHub, past quarter (13% increase) 885 PRs closed on GitHub, past quarter (14% increase) GitHub issues: 38 issues opened on GitHub, past quarter (-28% change) 40 issues closed on GitHub, past quarter (25% increase) ----------------------------------------- Attachment BH: Report from the Apache OODT Project [Imesha Sudasingha] ----------------------------------------- Attachment BI: Report from the Apache OpenJPA Project [Mark Struberg] ----------------------------------------- Attachment BJ: Report from the Apache OpenMeetings Project [Maxim Solodovnik] ## Description: The mission of OpenMeetings is the creation and maintenance of software related to OpenMeetings: Web-Conferencing and real-time collaboration ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OpenMeetings was founded 2013-01-25 (10 years ago) There are currently 30 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. Community changes, past quarter: - No new PMC members. Last addition was Ali Alhaidary on 2021-03-22. - No new committers. Last addition was Ali Alhaidary on 2021-04-07. ## Project Activity: Some vulnerable dependencies were updated, some JIRAs were addressed ... I guess, it's time to prepare release :) Recent releases: 6.3.0 was released on 2022-05-16. 6.2.0 was released on 2021-10-24. 6.1.0 was released on 2021-07-20. ## Community Health: There is no much activity in mailing lists, hopefully there will be more email after new release will be announced :) ----------------------------------------- Attachment BK: Report from the Apache OpenOffice Project [Jim Jagielski] ----------------------------------------- Attachment BL: Report from the Apache OpenWebBeans Project [Mark Struberg] ----------------------------------------- Attachment BM: Report from the Apache ORC Project [William Hyun] ## Description: The mission of ORC is the creation and maintenance of software related to the smallest, fastest columnar storage for Hadoop workloads. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache ORC was founded 2015-04-21 (8 years ago) There are currently 46 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 3:1. The PMC has been focusing on the community's growth to be a healthier community by helping candidates. - No new PMC members. Last addition was Yiqun Zhang on 2022-05-06. - No new committers. Last addition was Pavan Lanka on 2022-05-23. ## Project Activity: According to our release cadence, we released one feature release and one maintenance release in this quarter. - 1.8.1 was released on 2022-12-02. - 1.7.7 was released on 2022-11-17. We have prepared an SBOM (Software Bill of Materials). - https://cwiki.apache.org/confluence/display/COMDEV/SBOM We are looking to release the following versions soon in order to get user feedback on the SBOM. We have adjusted the release date to this month. - 1.7.8 (January) - 1.8.2 (January) ## Community Health: In this quarter, the number of code contributors increased by 20%, and closed GitHub issues increased by 27%. Activities have slowed down due to the Holiday season, but we are looking to return back to normal soon. ----------------------------------------- Attachment BN: Report from the Apache Parquet Project [Xinli Shang] ## Description: The mission of Parquet is the creation and maintenance of software related to columnar storage format available to any project in the Apache Hadoop ecosystem ## Issues: No issues found ## Membership Data: Apache Parquet was founded 2015-04-21 (8 years ago) There are currently 37 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Gidon Gershinsky on 2021-11-23. - No new committers. Last addition was Gidon Gershinsky on 2021-04-05. ## Project Activity: Recent releases: MR-1.11.2 was released on 2021-10-06. MR-1.12.2 was released on 2021-10-06. MR-1.12.0 was released on 2021-03-25. ## Community Health: dev@parquet.apache.org had a 65% decrease in traffic in the past quarter 28 issues opened in JIRA, past quarter (-22% change) 14 issues closed in JIRA, past quarter (40% increase) 16 commits in the past quarter (-27% change) 12 code contributors in the past quarter (-33% change) 25 PRs opened on GitHub, past quarter (-24% change) 22 PRs closed on GitHub, past quarter (-8% change ----------------------------------------- Attachment BO: Report from the Apache PDFBox Project [Andreas Lehmkühler] ## Description: The mission of PDFBox is the creation and maintenance of software related to Java library for working with PDF documents ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache PDFBox was founded 2009-10-21 (13 years ago) There are currently 21 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Matthäus Mayer on 2017-10-16. - No new committers. Last addition was Joerg O. Henne on 2017-10-09. ## Project Activity: Recent releases: 2.0.27 was released on 2022-09-29. 1.8.17 was released on 2022-09-15. 2.0.26 was released on 2022-04-21. ## Community Health: - there is a steady stream of contributions, bug reports and questions on the mailing lists - due to the holiday season the last quarter was a little bit quiter than usual - we are going to cut the first beta release of our next major version 3.0.0 this quarter - we are working on the 3.0 migration guide ----------------------------------------- Attachment BP: Report from the Apache Petri Project [Dave Fisher] ## Description: The mission of Apache Petri is the creation and maintenance of software related to assessment of, education in, and adoption of the Foundation's policies and procedures for collaborative development and the pros and cons of joining the Foundation ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Petri was founded 2019-11-19 (3 years ago) There are currently 8 committers and 5 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Daniel Shahaf on 2019-11-19. - No new committers. Last addition was Justin Erenkrantz on 2020-04-23. ## Project Activity: Project is waiting for the next culture. If you know of any open source communities interested in exploring if the ASF is where they want to be then please connect at discuss@petri.apache.org ## Community Health: No current activity, but plan to make updates to the website and then discuss with M&P some publicity. ----------------------------------------- Attachment BQ: Report from the Apache Pig Project [Koji Noguchi] ## Description: Apache Pig is a platform for analyzing large data sets on Hadoop. It provides a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Pig was founded 2010-09-21 (12 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 Koji Noguchi on 2016-08-04. - No new committers. Last addition was Nándor Kollár on 2018-09-06. ## Project Activity: Branch for 0.18 release is cut. We are in the process of running tests and verification for multiple hadoop/hbase/hive/spark versions on the release candidate. ## Community Health: Overall activity is low as the project is mostly stable and contributions are mainly bug fixes. ----------------------------------------- Attachment BR: Report from the Apache Pivot Project [Roger Lee Whitcomb] ## Description: The mission of Pivot is the creation and maintenance of software related to Rich Internet applications in Java ## Issues: No issues requiring Board attention at this time. ## Membership Data: Apache Pivot was founded 2009-12-15 (13 years ago) There are currently 10 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past year: - No new PMC members. Last addition was Gavin McDonald on 2022-04-13. - No new committers. Last addition was Gavin McDonald on 2022-04-14. ## Project Activity: No commit activity this last quarter, and only a minuscule number of emails. Recent releases: * 2.0.5 was released on 2017-07-04. * 2.0.4 was released on 2014-05-19. ## Community Health: No new development activity this quarter. Still anticipating a final release followed by moving to the Attic, unless some totally unexpected community begins to develop again. ----------------------------------------- Attachment BS: Report from the Apache Portable Runtime (APR) Project [Nick Kew] ----------------------------------------- Attachment BT: Report from the Apache Portals Project [David Sean Taylor] ## Description: The mission of Portals is the creation and maintenance of software related to Portal technology ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Portals was founded 2004-02-17 (19 years ago) There are currently 40 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Neil Griffin on 2017-02-11. - No new committers. Last addition was Ahmed on 2016-08-06. ## Project Activity: Neil Griffin was elected as the new PMC Chairman, a 5 votes for and 0 against. David Taylor (the former chairman) will soon be retiring from serving at Apache. ## Community Health: The community is largely inactive. Pluto is the only project that is still actively maintained. Pluto releases are planned to take place annually, mainly to update 3rd party dependencies that may have security vulnerabilities. ----------------------------------------- Attachment BU: Report from the Apache Ranger Project [Selvamohan Neethiraj] ----------------------------------------- Attachment BV: Report from the Apache Ratis Project [Tsz-wo Sze] ## Description: The mission of Apache Ratis is the creation and maintenance of software related to a highly customizable Raft protocol implementation in Java. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ratis was founded 2021-02-17 (2 years ago) There are currently 29 committers and 18 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 Attila Doroszlai on 2022-04-26. - William Song was added as committer on 2022-12-29 ## Project Activity: We released Ratis 2.4.0 and 2.4.1 on 2022-10-18 and 2022-11-28, respectively. Ratis 2.4.0 has the following features/improvements: - Server improvement: separated heartbeat channel, safe async flush, configurable ThreadGroup, configurable first election timeout and startup address binding - SetConfiguration features: ADD mode and CAS mode - Raft snapshot improvement - ratis-shell packaging - Better documentation - Upgraded Ratis Thirdparty to 1.0.2. Ratis 2.4.1 has the following features/improvements: - Support unordered async read. - Allow StateMachine to decide snapshot installation paths. - Performance improvement: buffer small sized packets in streaming. - Performance improvement: share buffer and avoid locking in segmented raft log. - Upgraded Ratis Thirdparty to 1.0.3. We also released Ratis Thirdparty 1.0.3 on 2022-11-8. It was mainly to upgrade protobuf-java to avoid CVEs. The previous Ratis 2.3.0 release was released on 2022-05-19. ## Community Health: The project is healthy. All the mailing lists had a significant increase in traffic. We did have less issues opened/closed and less pull requests/commits in this quarter compared to the previous quarter. ----------------------------------------- Attachment BW: Report from the Apache Royale Project [Piotr Zarzycki] ## Description: The mission of Apache Royale is the creation and maintenance of software related to improving developer productivity in creating applications for wherever Javascript runs (and other runtimes) ## Issues: No issues to report ## Membership Data: Apache Royale was founded 2017-09-20 (5 years ago) There are currently 20 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - Hugo Ferreira was added to the PMC on 2022-10-27 - No new committers. Last addition was María José Esteve on 2021-11-23. ## Project Activity: PMC members and the community after release has started working on new features and more general fixes. One PMC member has started preparations for the next release. Activity related to emulation components is still quite high, making more improvements available in that area. One committer was invited to become a PMC member based on activities and improvements provided. ## Community Health Our Twitter account has 707 (previously 718) followers. Our Facebook page has 184 (previously 185) likes. Our LinkedIn Group has 158 (previously 158) people. Our StackOverFlow "apache-royale" tag currently has 63 (previously 76) questions. Our Slack channel, "royale", in the-asf.slack.com workspace, makes quick team consultations more convenient. ----------------------------------------- Attachment BX: Report from the Apache Rya Project [Adina Crainiceanu] ## Description: The mission of Apache Rya is the creation and maintenance of software related to scalable storage, retrieval, and analysis of RDF data ## Issues: There are no issues requiring board attention. Several PMC members expect to be able to dedicate more time to the project in the near future and increase the viability of the project. ## Membership Data: Apache Rya was founded 2019-09-17 (3 years ago) There are currently 12 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Adina Crainiceanu on 2019-09-17. - No new committers were added. ## Project Activity: Apache Rya 4.0.1 was released on 2020-12-22. There was a discussion for a new release, but not much progress has been made yet. ## Community Health: The activity level in the project is low, but at least one committer plans on spending more time on the project in the next few months. dev@rya.apache.org had a 200% increase in traffic in the past quarter (3 emails compared to 1) 6 commits in the past quarter (600% increase) 1 code contributor in the past quarter (100% increase) 6 PRs opened on GitHub, past quarter (200% increase) 2 PRs closed on GitHub, past quarter (200% increase) ----------------------------------------- Attachment BY: Report from the Apache Samza Project [Yi Pan] ----------------------------------------- Attachment BZ: Report from the Apache Sedona Project [Jia Yu] ----------------------------------------- Attachment CA: Report from the Apache Serf Project [Justin Erenkrantz] ----------------------------------------- Attachment CB: Report from the Apache SkyWalking Project [Sheng Wu] ## Description: The mission of Apache SkyWalking is the creation and maintenance of software related to application performance management and monitoring (APM) ## Issues: No issue. ## Membership Data: Apache SkyWalking was founded 2019-04-17 (4 years ago) There are currently 56 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 7:4. Community changes, past quarter: - No new PMC members. Last addition was Jiemin Xia on 2022-10-04. - Puguang Yang was added as committer on 2022-11-08 - Yueqin Zhang was added as committer on 2022-10-12 ## Project Activity: The following releases are out in this quarter. rust-0.5.0 was released on 2023-01-09. satellite-1.1.0 was released on 2023-01-06. skywalking-banyandb-java-client-0.3.0-rc0 was released on 2023-01-06. skywalking-banyandb-java-client-0.3.0-rc1 was released on 2023-01-06. rover-0.4.0 was released on 2022-12-20. nodejs-0.6.0 was released on 2022-12-05. 9.3.0 was released on 2022-12-03. helm-4.4.0 was released on 2022-11-29. php-0.2.0 was released on 2022-11-28. banyandb-0.2.0 was released on 2022-11-09. banyandb-java-client-0.2.0 was released on 2022-11-09. java-8.13.0 was released on 2022-11-09. client-js-0.9.0 was released on 2022-10-13. SkyWalking 9.3.0 is out, and 8.x is end-of-life(EOL) officially. ## Community Health: Activities of mail list, GitHub issues, GitHub pull request are close to the last quarter. The community is still active. The increases are from new 9.3.0 release, bug fixes and new iteration for 9.4.0. 552 commits in the past quarter (21% increase) 47 code contributors in the past quarter (2% increase) 294 PRs opened on GitHub, past quarter (6% increase) 295 PRs closed on GitHub, past quarter (7% increase) 147 issues opened on GitHub, past quarter (9% increase) 149 issues closed on GitHub, past quarter (20% increase) ----------------------------------------- Attachment CC: Report from the Apache Steve Project [Daniel Gruno] ## Description: The mission of Steve is the creation and maintenance of software related to Apache's Python based single transferable vote software system ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Steve was founded 2012-07-25 (10 years ago) There are currently 10 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Jim Jagielski on 2022-04-16. - No new committers. Last addition was Sean Palmer on 2022-03-04. ## Project Activity: No noteworthy activity in this quarter. It is likely that we will see the usual uptick in activity in the weeks leading up to the next annual members meeting, albeit at a slower pace than usual. There are (still) no official releases of the STeVe software, though we do have the v2 master running on the foundation's vote site. ## Community Health: Community health remains the same as it has been in the past year. We have sufficient oversight (just about), but have not seen any noteworthy changes in the community make-up. ----------------------------------------- Attachment CD: Report from the Apache Storm Project [Kishor Patil] ----------------------------------------- Attachment CE: Report from the Apache StreamPipes Project [Philipp Zehnder] ## Description: The mission of Apache StreamPipes is the creation and maintenance of software related to a self-service Industrial IoT toolbox which enables non-technical users to connect, analyze and explore IoT data streams ## Issues: No Issues ## Membership Data: Apache StreamPipes was founded 2022-11-16 (2 months ago) There are currently 24 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Zike Yang was added to the PMC on 2022-11-26 - Cedric Kulbach was added as committer on 2022-12-15 - Sven Oehler was added as committer on 2022-12-15 - Xin Wang was added as committer on 2022-11-25 ## Project Activity: - Improve the setup of GitHub to make it more friendly for new developers - e.g. mark more issues with the tag 'good first issue' - The project is currently in the release process for version 0.90.0 - Last release (0.70.0) October 13, 2022 - Code improvement, dependency update and code base cleanup ## Community Health: - Constantly growing traffic on the mailing list (November: 399, December: 468). - Several PRs were submitted by new developers - Organization of the first community call for the end of January ----------------------------------------- Attachment CF: Report from the Apache Streams Project [Steve Blackmon] ----------------------------------------- Attachment CG: Report from the Apache Struts Project [René Gielen] The Apache Struts MVC framework is a solution stack for creating elegant and modern action-based Java web applications. It favours convention over configuration, is extensible using a plugin architecture, and ships with plugins to support patterns and technologies such as REST, AJAX and JSON. The Struts team made one release in the last quarter: * Struts 6.1.1 - Feature and bugfix release (2022-11-28) [1] The last Struts releases besides the core framework were * Struts Master 14 - Apply Apache Parent POM and plugin upgrades (2020-02-05) * Struts Annotations 1.0.7 - Enhancements in preparation for the next framework release (2020-02-23) Within the last quarter we saw rather vivid development and community activity, given that activity usually calms down during the Christmas holiday season. This is also reflected in the number of active pull requests, with 65 (61) opened and 64 (70) closed in the main project. These numbers are only slightly lower compared to the last quarter, but significantly higher than in the respective quarter one year ago. The same tendency can be derived from the number of 187 (167) commits by 6 (15) contributors. We released no security bulletin in the last quarter. We have no issues that require board assistance at this time. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - James Chaplin (jchaplin) was added to the PMC on 2020-11-16 ## Committer base changes: - Currently 60 committers. - No new committers added in the last 3 months - James Chaplin (jchaplin) was added as committer on 2020-01-08 ## Mailing list activity: Mailing list activity remained rather high, which is most probably an effect of the introduction of the major revision 6 of the Apache Struts Framework earlier this year. ## JIRA activity: - 32 JIRA tickets created in the last 3 months (36) - 50 JIRA tickets closed/resolved in the last 3 months (172) [1] https://struts.apache.org/announce-2022#a20220915 ----------------------------------------- Attachment CH: Report from the Apache Synapse Project [Isuru Udana] ## Description: Apache Synapse is a high-performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. ## Issues: None identified. ## Membership Data: Apache Synapse was founded on 2007-12-19 (15 years ago) There are currently 36 committers and 27 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. The last addition was Shafreen on 2021-05-09. - Nuwan Jayawardene was added as committer on 2022-11-19 ## Project Activity: The PMC voted to onboard the new contributor (Nuwan) as a committer during the last quarter. He is continuously working on providing fixes related to his GSoC project. However, we couldn't get the release done yet. The release manager (Shafreen) met with an accident and was away for some time. Hopefully, we should be able to continue with the long waited release after he comes back. ## Community Health: dev@synapse.apache.org had a 66% decrease in traffic in the past quarter (10 emails compared to 29) 1 commit in the past quarter (-92% change) 1 code contributor in the past quarter (no change) 3 PRs opened on GitHub, past quarter (300% increase) 2 PRs closed on GitHub, past quarter (no change No improvement to the project in the quarter as well. If we cannot get enough community activities even after doing the next release, we need to decide whether to move the project into the attic. ----------------------------------------- Attachment CI: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo] ## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (17 years ago) There are currently 29 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Ben Weidig on 2021-12-02. - No new committers. Last addition was Volker Lamp on 2022-04-14. ## Project Activity: We've been working on better cache invalidation when not in production mode, something that should improve developer productivity, at least for larger projects. We've also had a couple bugfixes. We should definitely have a new release next quarter. ## Community Health: We had an increase in activity this quarter compared to the previous one: dev@tapestry.apache.org had a 120% increase in traffic in the past quarter (55 emails compared to 25) 6 issues opened in JIRA, past quarter (100% increase) 29 commits in the past quarter (625% increase) ----------------------------------------- Attachment CJ: Report from the Apache Tcl Project [Georgios Petasis] ## Description: The mission of Tcl is the creation and maintenance of software related to Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration efforts. The purpose of our project is to combine the power of the Apache web server with the capabilities of the mature, robust and flexible Tcl scripting language. Currently only the Apache Rivet project is actively maintained. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Tcl was founded 2000-07-24 (22 years ago) There are currently 12 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Brice Hamon De Crevecoer on 2014-11-25. - No new committers. Last addition was Brice B. Hamon on 2014-11-25. ## Project Activity: No release has been made during the reporting period. The new release made on the previous reporting period (rivet-3.2.2 was released on 2022-06-21) has received positive feedback, and no problems have been identified so far. ## Community Health: The traffic of the mailing lists has remained at similar levels to the previous reporting period, which is normal for the project (as most traffic in the list happens after new releases). Thus, the increase in traffic is related to the release of rivet 3.2.2, which was released on 2022-06-21. ----------------------------------------- Attachment CK: Report from the Apache Tez Project [László Bodor] ## Description: Apache Tez is an effort to develop a generic application framework which can be used to process arbitrarily complex DAGs of data-processing tasks and also a re-usable set of data-processing primitives which can be used by other projects. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tez was founded 2014-07-16 (9 years ago) There are currently 35 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 László Bodor on 2020-11-24. - No new committers. Last addition was László Bodor on 2020-01-23. ## Project Activity: Latest release was 0.10.2, and we're already fixing issues that have been discovered there. ## Community Health: There is still not a huge committer/PMC activity. We get random contributions from people, that are reviewed as quickly as possible. ----------------------------------------- Attachment CL: Report from the Apache Thrift Project [Jens Geyer] ## Description: Apache Thrift is a high performance cross platform RPC and serialization solution. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Thrift was founded 2010-10-20 (12 years ago) There are currently 41 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Mario Emmenlauer on 2022-04-13. - No new committers. Last addition was Liu Jiayu on 2022-06-25. ## Project Activity: Working towards next release which is planned for February. ## Community Health: Despite reduced activity on all channels in the last quarter, we still receive contributions and work on adding features/improvements. ----------------------------------------- Attachment CM: Report from the Apache Tika Project [Tim Allison] ## Description: Apache Tika is a dynamic toolkit for content detection, analysis, and extraction. It allows a user to understand, and leverage information from, a growing a list of over 1200 different file types including most of the major types in existence (MS Office, PDF, Text, Images, Video, Code, and science data) as recognized by IANA and other standards bodies. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tika was founded 2010-04-20 (13 years ago) There are currently 32 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05. - No new committers. Last addition was Nicholas DiPiazza on 2021-06-03. ## Project Activity: We had a minor release of 2.6.0 in November. We are starting to discuss goals for a 3.x release, although we have no planned release date. ## Community Health: The project's Chi is unchanged from last quarter -- 4.7, healthy. We've seen decreases in email, JIRA and commits. We suspect this is because of the stabilization and adoption of the 2.x branch. There's a trivial increase in GitHub PRs likely driven by dependabot. ----------------------------------------- Attachment CN: Report from the Apache TinkerPop Project [Florian Hockmann] ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). ## Issues: There are no issues requiring board attention. ## Membership Data: Community changes, past quarter: - No new PMC members. Last addition was Divij Vaidya on 2022-04-25. - No new committers. Last additions were Rithin Kumar, Valentyn Kahamlyk, and Yang Xia on 2022-09-01. ## Project Activity: We have started the preparations for the release of versions 3.5.5 and 3.6.2. These releases are mostly maintenance releases which include a lot of bug fixes, various improvements, and dependency updates. We have decided that we postpone the next major release, 3.7.0, which we initially wanted to release together with 3.5.5 and 3.6.2. The reasons for postponing the release are mostly that some of the changes that we have planned for this version are not implemented yet and also that most graph providers also have not updated to 3.6 yet. Releasing 3.7.0 early would therefore not provide much benefit to most of our users as they have to wait for their graph provider to update to that version. In the wider TinkerPop ecosystem, we've learned about three new systems that are TinkerPop enabled: - ByteGraph, a graph database developed internally at ByteDance, the company behind e.g., TikTok [1] - GraphScope, a large-scale graph computing system from Alibaba [2] - Graph Explorer, a web application to visualize graph data, created by Amazon Neptune that is also compatible with other TinkerPop-enabled graph databases and Apache 2.0 licensed [3] ### Releases: 3.5.4 was released on 2022-07-18. 3.6.1 was released on 2022-07-18. ## Community Health: Since we had a lot of live events already on Discord, we have decided to create a YouTube channel for TinkerPop where we want to make recordings of such events available in the future so that interested users and contributors can watch them even if they could not attend the live event.[4] (The channel is still empty right now as we did not host any event recently and because we unfortunately did not record past events.) ## Links [1] https://www.vldb.org/pvldb/vol15/p3306-li.pdf [2] https://graphscope.io/ [3] https://aws.amazon.com/de/about-aws/whats-new/2023/01/neptune-graph-explorer-open-source-visual-exploration-tool-low-code-users/ [4] https://www.youtube.com/@apachetinkerpop ----------------------------------------- Attachment CO: Report from the Apache Traffic Server Project [Bryan Call] ## Description: The mission of Traffic Server is the creation and maintenance of software related to a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Traffic Server was founded 2010-04-20 (13 years ago) There are currently 70 committers and 57 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - Damian Meden was added to the PMC on 2022-12-14 - No new committers. Last addition was Chris McFarlen on 2022-10-11. ## Project Activity: We released 8.1.6 and 9.1.3 this quarter fixing security issues and bugs. We are working on the 9.2.0 release, which is our next feature release and that will be completed in Q1 of 2023. We are also preparing for our next major release, 10.0.0, and we are planning to release that in Q2 of 2023. Companies will start testing 10.0.0 in production in Q1 of this year. It will have features: HTTP/3, HTTP/2 to the origin, JSON RPC, and many more features. ## Community Health: We had our first in person event since the fall of 2019 (before COVID). Linkedin generously hosted the event. There were 62 people that signed up for the summit and 36 signed up in person. This is much lower than our pre-COVID numbers of 82 people signed up to attend in person. Hopefully attendance will pick up for our fall summit this year. We are planning on having a developer focused summit this spring. We are looking at the possibility of having it in Ireland. We are continuing to have our weekly PR and issue scrub meetings every Monday. Commits and unique committers were down in Q4 of 2022, 21% and 16% respectively. This normally happens around the holidays and picks up Q1. ----------------------------------------- Attachment CP: Report from the Apache UIMA Project [Richard Eckart de Castilho] ## Description: Apache UIMA (*) software provides frameworks, tools and annotators, facilitating the analysis of unstructured content such as text, audio and video. (*) Unstructured Information Management Architecture. ## Issues: There are no board-level issues at this time. ## Membership Data: Apache UIMA was founded 2010-03-17 (13 years ago) There are currently 25 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Viorel Morari on 2019-11-19. - No new committers. Last addition was Viorel Morari on 2018-09-20. ## Project Activity: - uima-uimaj-3.1.1 was released on 2022-10-31 - focus is currently to improve compatibility of the UIMA Java SDK and uimaFIT with multi-classloader such as OSGI - voting for retirement of the UIMA DUCC subproject is ongoing - voting for retirement of all v2.x versions of UIMA subprojects is ongoing. This would also affect e.g. the UIMA-AS subproject, sandbox components, etc. of which currently no v3 versions exist. - voting for retirement of the UIMA C++ SDK is ongoing. One community member has suggested to take over maintenance of the subproject and asked for a month of time to consider. - the UIMA Java SDK, uimaFIT and UIMA Ruta subprojects continue being active. New releases are tentatively scheduled for Q1 2023. ## Community Health: The community remains moderately active. Eventually, I was able to work on upgrading the non-ASF ClearTK OSS project to UIMAv3 myself. A release will probably follow in Q1 2023 and that may pave the way for e.g. Apache cTAKES to also finally upgrade to UIMAv3. ----------------------------------------- Attachment CQ: Report from the Apache Web Services Project [Daniel Kulp] ----------------------------------------- Attachment CR: Report from the Apache Zeppelin Project [Lee Moon Soo] ------------------------------------------------------ End of minutes for the January 18, 2023 board meeting.