The Apache Software Foundation Board of Directors Meeting Minutes January 20, 2021 1. Call to order The meeting was scheduled for 20:00 UTC and began at 20:03 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/42aa 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: Shane Curcuru Bertrand Delacretaz Roy T. Fielding Niclas Hedhman Justin Mclean Sam Ruby Craig L Russell Patricia Shanahan Sander Striker Directors Absent: none Executive Officers Present: Myrle Krantz David Nalley Matt Sicker Ruth Suehle Executive Officers Absent: none Guests: Daniel Gruno Gavin McDonald Greg Stein Rich Bowen Sally Khudairi Sven Vogel 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of December 16, 2020 See: board_minutes_2020_12_16.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Roy] I had a nice discussion with Ian Buck, VP at NVIDIA, and we resolved the longstanding issue impacting MXNet regarding our distribution of binaries compiled by NVIDIA's CUDA SDK. Other than that, my free time has been consumed by the HTTP specifications which are now in working group last call at the IETF. I hope to get more Apache work done this month. B. President [David] As we close out CY2020 and open CY2021 the Fundraising folks pulled together an impressive month taking advantage of the end of fiscal year for a number of our sponsors. I've spent some time this past month working with the Treasurer on the initiation of our TD Bank account and services. We have an ongoing Code of Conduct issue that's being worked and a fresh complaint that arrived shortly before drafting this report. We've filed the 2021 Annual Report with the state of Delaware as required to keep our corporation status active. I'm just starting work on the budget, and more coming on that as we enter February. Additionally, please see Attachments 1 through 8. C. Treasurer [Myrle] While reading this and future reports, please keep in mind that reducing manual labor and increasing automatically accessible insights for volunteers and paid staff alike has been the major theme behind the changes we have made and will continue to make in the Treasurer’s office. Transition to TDBank: We have opened a new bank account with TDBank. Currently we are depositing all donor checks to TDBank and directing payments from Stripe and PayPal to TDBank. We are not currently requesting that sponsors remit to the TDBank account, and we also are not currently paying expenses out of it. Our evaluation of virtualizing our credit card expenditures is still lower priority, but opening the TD Bank account helps us towards this goal, because it allows us to provide the virtual credit card provider with read-only access to our bank account. TDBank also syncs automatically with QuickBooks Online, which reduces our manual work in accounting reconciliation. In the process of transitioning Boston Private, I requested that Trevor Grant be added to the signatories. We’ve been asked to sign an agreement very similar to the Citizen’s agreement that recently required board action. We should discuss how we wish to handle this. Support of Fundraising: Our new treasurer/accounting team spent a lot of extra cycles supporting fundraising/sponsor relations in December to help bring in last minute, end-of-year sponsorships, including a rather exciting double Platinum sponsorship invoice created and submitted to the Microsoft purchase order system by the Treasurer herself on the morning of the January 1st (European time) with extensive support from Greg Stein and Sally Khudairi. IgniteSpot was very responsive, sometimes even during their vacation. Accounting transition: The transition to the new accountant is mostly complete. Still outstanding are: * Complete the tax and audit of our books from the last fiscal year, which are still held by our previous accounting firm. Progress has been made, but this is not yet complete. * Recovering access to two last donation channel accounts. Of the outstanding items from the accounting transition mentioned in our previous report, we’ve been able to complete: * Transition our bank account out from under the previous accounting firm’s relationship with our bank, and provide the new accounting firm with read access to our banking data. * Complete the integration between bill.com and QuickBooks online, in order to automatically sync payment data. * Migrate the PayPal account, and the Boston Private account. Other items we have accomplished: * Our current accountant, with support from our previous accountant, was also able to complete the 1099’s for the year and is sending them out. * We have agreed on a notification schedule and format for incoming payments for fundraising. And finally, a reminder: for *all* email communications with our accounting team, please include team@treasurer.apache.org. D. Secretary [Matt] In December, the secretary team filed 48 ICLAs and four software grants. E. Executive Vice President [Ruth] [no additional updates] F. Vice Chairman [Shane] Big thanks go out to the many staff and volunteers who led the successful and smooth transition of many back office services to the ASF. We always thank our many project volunteers for their work; let's also take the time to thank myriad organizational volunteers who keep our corporate being healthy too! 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 / Patricia] No report was submitted. C. Apache Security Team Project [Mark J. Cox / Justin] See Attachment 11 D. VP of Jakarta EE Relations [Rob Tompkins / Shane] See Attachment 12 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: A. Apache Accumulo Project [Ed Coleman / Craig] See Attachment A B. Apache ActiveMQ Project [Bruce Snyder / Bertrand] See Attachment B C. Apache Airavata Project [Suresh Marru / Niclas] See Attachment C D. Apache APISIX Project [Ming Wen / Sam] See Attachment D E. Apache Aries Project [Christian Schneider / Roy] See Attachment E F. Apache Arrow Project [Wes McKinney / Niclas] See Attachment F G. Apache AsterixDB Project [Till Westmann / Sander] See Attachment G H. Apache Attic Project [Mads Toftum / Craig] No report was submitted. I. Apache Avro Project [Ismaël Mejía / Bertrand] See Attachment I J. Apache Beam Project [Kenneth Knowles / Roy] See Attachment J K. Apache Bloodhound Project [Gary Martin / Justin] See Attachment K L. Apache Calcite Project [Haisheng Yuan / Patricia] See Attachment L M. Apache CarbonData Project [Liang Chen / Shane] See Attachment M N. Apache Celix Project [Pepijn Noltes / Sam] No report was submitted. O. Apache CXF Project [Daniel Kulp / Roy] See Attachment O P. Apache DataFu Project [Matthew Hayes / Bertrand] See Attachment P Q. Apache DataSketches Project [Lee Rhodes / Justin] See Attachment Q R. Apache DB Project [Bryan Pendleton / Shane] No report was submitted. S. Apache Directory Project [Shawn McKinney / Craig] See Attachment S T. Apache Druid Project [Gian Merlino / Sam] See Attachment T U. Apache Dubbo Project [Ian Luo / Patricia] See Attachment U V. Apache ECharts Project [Wenli Zhang / Sander] See Attachment V W. Apache Fineract Project [Awasum Yannick / Niclas] See Attachment W X. Apache Fluo Project [Keith Turner / Bertrand] See Attachment X Y. Apache Geronimo Project [Romain Manni-Bucau / Justin] See Attachment Y Z. Apache Griffin Project [William Guo / Shane] See Attachment Z AA. Apache Hadoop Project [Wei-Chiu Chuang / Roy] See Attachment AA AB. Apache HAWQ Project [Lei Chang / Niclas] See Attachment AB AC. Apache HBase Project [Duo Zhang / Sam] See Attachment AC AD. Apache Hive Project [Ashutosh Chauhan / Sander] See Attachment AD AE. Apache Incubator Project [Justin Mclean] See Attachment AE AF. Apache Isis Project [Johan Doornenbal / Patricia] See Attachment AF AG. Apache James Project [Benoit Tellier / Craig] See Attachment AG AH. Apache jclouds Project [Ignasi Barrera / Craig] See Attachment AH AI. Apache Jena Project [Andy Seaborne / Roy] See Attachment AI AJ. Apache JMeter Project [Bruno Demion / Shane] See Attachment AJ AK. Apache Johnzon Project [Romain Manni-Bucau / Sam] See Attachment AK AL. Apache Joshua Project [Tommaso Teofili / Niclas] No report was submitted. AM. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Patricia] See Attachment AM AN. Apache Kudu Project [Adar Dembo / Bertrand] See Attachment AN AO. Apache MADlib Project [Aaron Feng / Justin] See Attachment AO AP. Apache Mahout Project [Trevor Grant / Sander] See Attachment AP AQ. Apache Maven Project [Robert Scholte / Roy] See Attachment AQ AR. Apache Mesos Project [Vinod Kone / Craig] See Attachment AR AS. Apache MINA Project [Guillaume Nodet / Sam] See Attachment AS AT. Apache Mnemonic Project [Gordon King / Bertrand] See Attachment AT AU. Apache MyFaces Project [Bernd Bohmann / Justin] See Attachment AU AV. Apache NiFi Project [Joe Witt / Shane] See Attachment AV AW. Apache Nutch Project [Sebastian Nagel / Niclas] See Attachment AW AX. Apache OpenJPA Project [Mark Struberg / Patricia] See Attachment AX AY. Apache OpenMeetings Project [Maxim Solodovnik / Sander] See Attachment AY AZ. Apache OpenOffice Project [Carl B. Marcum / Craig] See Attachment AZ BA. Apache ORC Project [Owen O'Malley / Justin] See Attachment BA BB. Apache Ozone Project [Sammi Chen / Shane] See Attachment BB BC. Apache Parquet Project [Julien Le Dem / Sander] See Attachment BC BD. Apache PDFBox Project [Andreas Lehmkühler / Roy] See Attachment BD BE. Apache Perl Project [Philippe Chiasson / Patricia] No report was submitted. BF. Apache Petri Project [Dave Fisher / Bertrand] See Attachment BF BG. Apache Ranger Project [Selvamohan Neethiraj / Sam] No report was submitted. BH. Apache Rya Project [Adina Crainiceanu / Niclas] See Attachment BH BI. Apache Samza Project [Yi Pan / Patricia] See Attachment BI BJ. Apache SkyWalking Project [Sheng Wu / Sander] See Attachment BJ BK. Apache Sqoop Project [Venkat Ranganathan / Sam] See Attachment BK BL. Apache Steve Project [Daniel Gruno / Shane] See Attachment BL BM. Apache Streams Project [Steve Blackmon / Niclas] See Attachment BM BN. Apache Struts Project [René Gielen / Justin] See Attachment BN BO. Apache Superset Project [Maxime Beauchemin / Craig] See Attachment BO BP. Apache Synapse Project [Isuru Udana / Roy] See Attachment BP BQ. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Bertrand] See Attachment BQ BR. Apache Tcl Project [Georgios Petasis / Shane] See Attachment BR BS. Apache Tez Project [Jonathan Turner Eagles / Roy] See Attachment BS BT. Apache Thrift Project [Jens Geyer / Justin] See Attachment BT BU. Apache Tika Project [Tim Allison / Bertrand] See Attachment BU BV. Apache TinkerPop Project [Stephen Mallette / Niclas] See Attachment BV BW. Apache Traffic Server Project [Bryan Call / Craig] See Attachment BW BX. Apache Trafodion Project [Pierre Smits / Sander] No report was submitted. BY. Apache TVM Project [Tianqi Chen / Patricia] See Attachment BY BZ. Apache Web Services Project [Daniel Kulp / Sam] See Attachment BZ CA. Apache Zeppelin Project [Lee Moon Soo / Shane] No report was submitted. Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache jclouds Project Chair WHEREAS, the Board of Directors heretofore appointed Ignasi Barrera (nacx) to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Ignasi Barrera from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Andrew Gaul (gaul) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ignasi Barrera is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Andrew Gaul be and hereby is appointed to the office of Vice President, Apache jclouds, 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 jclouds Project Chair, was approved by Unanimous Vote of the directors present. B. Establish the Apache Gobblin Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Gobblin Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Gobblin be and hereby is responsible for the creation and maintenance of software related to a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems; and be it further RESOLVED, that the office of "Vice President, Apache Gobblin" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Gobblin Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Gobblin Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Gobblin Project: * Lorand Bendig * Issac Buenrostro * Shirshanka Das * Kishore G * Olivier Lamy * Yinan Li * Tamás Németh * Owen O'Malley * Jean-Baptiste Onofré * Sahil Takiar * Abhishek Tiwari * Hung Tran * Sudarshan Vasudevan NOW, THEREFORE, BE IT FURTHER RESOLVED, that Abhishek Tiwari be appointed to the office of Vice President, Apache Gobblin, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Gobblin Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Gobblin podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Gobblin podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7B, Establish the Apache Gobblin Project, was approved by Unanimous Vote of the directors present. C. Change the Apache Mnemonic Project Chair WHEREAS, the Board of Directors heretofore appointed Gordon King (garyw) to the office of Vice President, Apache Mnemonic, and WHEREAS, the Board of Directors is in receipt of the resignation of Gordon King from the office of Vice President, Apache Mnemonic, and WHEREAS, the Project Management Committee of the Apache Mnemonic project has chosen by vote to recommend Yanhui Zhao (yzhao) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Gordon King is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Mnemonic, and BE IT FURTHER RESOLVED, that Yanhui Zhao be and hereby is appointed to the office of Vice President, Apache Mnemonic, 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 Mnemonic Project Chair, was approved by Unanimous Vote of the directors present. D. General Deposit Resolution WHEREAS, The Apache Software Foundation (the "Corporation") wishes to maintain accounts at Boston Private (the “Bank”). RESOLVED: 1. That Boston Private (the “Bank”) is designated a depository of the funds of this Corporation (“Corporation”), and: Myrle Krantz Treasurer Trevor Grant Assistant Treasurer David Nalley President Ruth Suehle Exec. V.P is/are hereby authorized: a. To open deposit accounts at Bank; b. To contract for any services offered by Bank, including (without limitation) electronic account access and management services; c. To submit for deposit and/or collection for the account of this Corporation all checks, drafts, notes or other instruments for the payment of money; and the bank is authorized to accept such instruments, whether or not endorsed by any person or by stamp or other impression in the name of the Corporation, without inquiry as to the circumstances of the endorsement or lack of endorsement or the disposition of the proceeds. d. To make deposits of currency for the account of this Corporation; e. To sign checks, drafts or other orders with respect to any funds to the credit of this Corporation, including checks, drafts or orders in favor of any individual designated above, and to issue stop payment instructions with reference to any of the above; f. To make withdrawals or transfers of funds from accounts in the name of this Corporation, and to transfer funds between such accounts, by any means authorized by Bank. g. To conduct any and all other lawful business with Bank. 2. That any and all withdrawals of money and/or other transactions heretofore had on behalf of this Corporation with the Bank are hereby ratified, confirmed and approved, and that the Bank may rely upon the authority conferred by this entire resolution unless, and except to the extent that, this resolution shall be revoked or modified by any subsequent resolution. 3. That the designated authorized person(s) in this Resolution are individually empowered to delegate to other persons the authority to perform transactions with respect to the accounts of this Corporation and to change and revoke such delegations from time to time; the Bank is entitled to rely upon such delegations of authority and to accept instructions from such other persons as being fully authorized by this Corporation 4. That this Corporation acknowledges and agrees that all accounts are subject to the rules, regulations, charges and fees of Bank contained in the Bank’s Business Deposit Agreement and Schedule of Fees and Charges and any other account agreements it receives, and any modification(s) or amendment(s) of same, with the same effect as if each and every term thereof were set forth in full herein. 5. That this Corporation certifies that the provisions in this Resolution are in conformity with the statutes applicable to, or organizational documents of the Corporation. Any provision hereof which may prove unenforceable under any law shall not affect the validity of any other provision hereof. 6. That the signatures and/or facsimile signatures appearing above and on the Bank’s signature card are those of the authorized signers designated and that each said individual is legally empowered, in accordance with the charter or bylaws of the Corporation, to exercise the authority provided for in this Resolution. 7. That if not a single stockholder corporation, the Secretary or/and Assistant Secretary of this Corporation be/are and hereby is/are authorized and directed to certify to the Bank the names of the present officers of this Corporation and other persons authorized to sign for it, and the offices respectively held by them, together with specimens of their signatures and from time to time as changes in such personnel are made, immediately to certify such changes to the Bank, and the Bank shall be fully protected in relying on such certifications and shall be indemnified and held harmless from any claims, demands, expenses (including reasonable attorneys' fees), losses or damages resulting from refusing to honor any signature not so certified. That the Secretary or an Assistant Secretary of this Corporation be and hereby is authorized and directed to certify to the Bank that this resolution has been duly adopted, is in full force and effect and is in accordance with the provisions of the charter. a. To open deposit accounts at Bank; b. To contract for any services offered by Bank, including (without limitation) electronic account access and management services; c. To submit for deposit and/or collection for the account of this Corporation all checks, drafts, notes or other instruments for the payment of money; and the bank is authorized to accept such instruments, whether or not endorsed by any person or by stamp or other impression in the name of the Corporation, without inquiry as to the circumstances of the endorsement or lack of endorsement or the disposition of the proceeds. d. To make deposits of currency for the account of this Corporation; e. To sign checks, drafts or other orders with respect to any funds to the credit of this Corporation, including checks, drafts or orders in favor of any individual designated above, and to issue stop payment instructions with reference to any of the above; f. To make withdrawals or transfers of funds from accounts in the name of this Corporation, and to transfer funds between such accounts, by any means authorized by Bank. g. To conduct any and all other lawful business with Bank. 2. That any and all withdrawals of money and/or other transactions heretofore had on behalf of this Corporation with the Bank are hereby ratified, confirmed and approved, and that the Bank may rely upon the authority conferred by this entire resolution unless, and except to the extent that, this resolution shall be revoked or modified by any subsequent resolution. 3. That the designated authorized person(s) in this Resolution are individually empowered to delegate to other persons the authority to perform transactions with respect to the accounts of this Corporation and to change and revoke such delegations from time to time; the Bank is entitled to rely upon such delegations of authority and to accept instructions from such other persons as being fully authorized by this Corporation 4. That this Corporation acknowledges and agrees that all accounts are subject to the rules, regulations, charges and fees of Bank contained in the Bank’s Business Deposit Agreement and Schedule of Fees and Charges and any other account agreements it receives, and any modification(s) or amendment(s) of same, with the same effect as if each and every term thereof were set forth in full herein. 5. That this Corporation certifies that the provisions in this Resolution are in conformity with the statutes applicable to, or organizational documents of the Corporation. Any provision hereof which may prove unenforceable under any law shall not affect the validity of any other provision hereof. 6. That the signatures and/or facsimile signatures appearing above and on the Bank’s signature card are those of the authorized signers designated and that each said individual is legally empowered, in accordance with the charter or bylaws of the Corporation, to exercise the authority provided for in this Resolution. 7. That if not a single stockholder corporation, the Secretary or/and Assistant Secretary of this Corporation be/are and hereby is/are authorized and directed to certify to the Bank the names of the present officers of this Corporation and other persons authorized to sign for it, and the offices respectively held by them, together with specimens of their signatures and from time to time as changes in such personnel are made, immediately to certify such changes to the Bank, and the Bank shall be fully protected in relying on such certifications and shall be indemnified and held harmless from any claims, demands, expenses (including reasonable attorneys' fees), losses or damages resulting from refusing to honor any signature not so certified. That the Secretary or an Assistant Secretary of this Corporation be and hereby is authorized and directed to certify to the Bank that this resolution has been duly adopted, is in full force and effect and is in accordance with the provisions of the charter. Special Order 7D, General Deposit Resolution, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Schedule the annual members meeting We should plan a date for the annual members meeting. For the past six years it has been held around the last week of March, which drops a new board into the end of budgeting for the coming year. Roy thinks it would be better to have a meeting on the first or second week of March [March 2-4 or 9-11]. Would it be possible/desirable to use our virtual conferences platform to host the first part of our annual meeting? RESOLVED, the next annual members meeting shall be March 9-11, 2021, was approved by General Consent. 9. Review Outstanding Action Items * Roy: work on binary release policy [ Unfinished Business 2020-05-20 ] Status: Not done. * Roy: notify members about bylaw updates [ Unfinished Business 2020-11-18 ] Status: Not done. See Bertrand's link below. * Sander: pursue a report for Perl [ Perl 2020-12-16 ] Status: Carrying forward. Will action EOW. * Justin: pursue a roll call for Trafodion [ Trafodion 2020-12-16 ] Status: Done * Bertrand: take over the GitHub repo ASF docs repo initiative [ Unfinished Business 2020-12-16 ] Status: Created https://github.com/apache/members-info/issues/1 to work on the Bylaws as per our September 2020 Resolution 7D. Let's see if that matches people's expectations on how to work on those changes. 10. Unfinished Business A. Prepare a notice for the members regarding the bylaws amendment approved in October so that the formal approval clock can commence. B. Find a way to make use of our github repo to assist with collaborative writing of ASF documentation and provide a place for meaningful tracking of board issues. C. Work on a binary release policy. @Matt: find out about updating bylaws for a DE corp 11. New Business 12. Announcements 13. Adjournment Adjourned at 20:29 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period December 2020 * ISSUES FOR THE BOARD - None * OPERATIONS Responded to the following queries, liaising with projects as required: - provided advice to AIRFLOW regarding external entities providing swag for committers - approved name search for GOBBLIN - approved external events for PULSAR - approved a request to create stickers using the SHIRO logo - provided quarterly report content to Press & marketing - approved a request to use LOGGING logos in a book - approved a request to use the ASF logo when referring to the ASF in a webinar and blog post - started the process of changing our registered address for our trademark registrations - requested advice from counsel for KAFKA regarding their wish to adopt a more relaxed naming policy for a limited set of extensions * REGISTRATIONS Worked with counsel to progress the registrations for: - BROOKLYN in the US - APACHE FLINK in China - APACHE in China Received notification the the APACHE IGNITE registration has completed in China. * INFRINGEMENTS Provided advice on how to handle a potential minor infringement in a dormant GitHub project. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] 1) ASF Sponsors: we are working on $68K in renewals (one Gold, and three Bronze Sponsors). We have $537K in invoicing (new Sponsorships or renewals in place, with monies due to the ASF: this is for three Platinum; three Gold; two Bronze Sponsors). We received $420K in Sponsor payments (two Platinum, two Gold, three Silver, and two Corporate Charitable Contributions). We welcomed (signed on) one new Platinum, one Gold, one Silver, and one Bronze Sponsor. We are now administering/maintaining all Sponsor accounting records. 2) Targeted Sponsors: we are working on securing Targeted renewals for the New Year, and completed end-of-year outreach with existing Targeted Sponsors. 3) Sponsor Relations: we have completed our end-of-year outreach to all Sponsors. We are working with three organizations considering ASF Sponsor promotional offerings as part of their sponsorship. 4) Event Sponsorship: no activity (there are no Apache events being planned at this time). 5) Individual Donations and Corporate Giving: we successfully closed our end-of-year Individual and Corporate Giving campaigns. We earned $7,602 during December over 103 donations through donate.apache.org. Select Sponsors also use our online donation platform to process payment of their Sponsorship renewals. 6) The work of ensuring our sponsor recognition (thanks page) matches our internal records is receiving a boost thanks to automation. Tooling now exists that identifies deltas between the two locations and will continue to be enhanced with the goal of full, automated synchronization. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity — January 2021 I. Budget: we are on-budget and processing standing vendor payments as scheduled. II. Cross-committee Liaison: Sally Khudairi continues to support day-to-day activities within ASF Fundraising, focusing on end-of-year Sponsor renewals, invoicing, and giving campaigns. We issued the December Month In Review https://s.apache.org/Dec2020 , published Apache in 2020 - By The Digits https://s.apache.org/Apache2020Digits and accompanying video highlights https://s.apache.org/Apache2020Digits-vid , the Second Quarter FY 2021 Operations Summary https://s.apache.org/Q2FY2021 , and published Part II of the "Inside Infra" interview with Andrew Wetmore https://s.apache.org/InsideInfra-Andrew2 and are preparing to publish the final interview of the series. We helped coordinate response to an ASF Code-of-Conduct violation, helped an Apache project community with planning an upcoming event, worked with three Sponsors with promoting their support of the ASF, secured a Board member spokesperson and wrote their presentation for a Sponsor conference, and handled an Apache project logo re-publishing request and another for social media promotion with Brand Management. III. Press Releases: no formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe. IV. Informal Announcements: we published 8 items on the ASF "Foundation" Blog, including 4 Apache News Round-ups and 1 monthly overview, totalling 354 news summaries published to date. We tweeted 18 items to 59K followers on Twitter, and posted 19 items to 45.6K followers on LinkedIn. The ASF's YouTube channel had 14,232 views this month, with 8,421 subscribers to date. V. Future Announcements: 6 announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 7 media queries. We received a total of 2,156 press hits vs. last month's 3,441, inclusive of coverage on the ASF, Apache Projects, and initiatives such as ApacheCon. VII. Analyst Relations: we received two analyst queries, provided background to a EU analyst researching AI Service Clouds for an upcoming industry report, and followed up on last month's Serverless Computing research query on behalf of an Apache project PMC. Apache was mentioned in a total of 28 reports by Gartner, Forrester, 451 Research, and IDC. VIII. Central Services: Kenneth Paskett (Creative team) continues to make updates and adjustments to apache.org related sub-pages. We are preparing for the migration to the new CMS. Swapnil Mane (Editorial team) continues with drafting and publishing Weekly News Round-ups and Month-in-Review summaries, and has launched the new ASF news video highlight promotions, which we are planning to produce on a regular basis. IX. Events liaison: we are working with an Apache project community that is partnering with other industry foundations on an upcoming event. We will also be assisting with creative aspects of the ASF's virtual booth at FOSDEM once we receive specifications. We continue to advise several Apache projects with promoting their events. X. Newswire and press clip accounts: We completed the transition of billing pass-throughs from HALO Worldwide to the ASF. We confirmed the clipping service through 2021. XI. Miscellany: we are working with a vendor seeking to promote an Apache project's milestones, are working with a Targeted Sponsor seeking additional marketing exposure, helped a corporate contributor make an end-of-year donation, advised two podlings on how to work with Infra to migrate their repositories, addressed a request regarding announce@a.o posting policy, responded to two subscription-related requests with the committers' master email list, addressed a request for ASF to sponsor a Chaos developer event, helped a PMC Chair help a non-coding/non-technical individual seeking to contribute to the ASF, reviewed and edited a corporate's press release that references their product's dependency on an Apache project, responded to a query regarding Apache Project activity and release cadence during the pandemic, and reviewed and edited a researcher report that featured the ASF. # # # ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected, and has no current issues requiring escalation to the President or the Board. Highlights ========== - Staff is now completely on our new PEO, three payrolls have been run successfully, and our benefits plan started on January 1. The 401k plan should start on March 1. - A potential security gap in GitHub Actions led to our disabling of "untrusted" third-party Actions until we could investigate. We are on-track with security recommendations and a scanner to enforce that policy, as people adjust workflows [which use Actions]. Finances ======== - Budget planning will start very soon. Staffing represents over 85% of the Infra budget, and that was completed during our PEO transition. The remaining portion of our budget will be very straightforward. - Overall, the Infra budget is doing well for FY21, as we did not backfill our open position (and had budgeted for a half-year). Short Term Priorities ===================== - Finish the FY22 budget. - Gitbox v2 launch, for a few private repositories. Long Range Priorities ===================== - Finish the mail system upgrade. It is in testing right now. - Extract permalinks from our PonEE snapshot, and validate them to ensure we have a disaster recovery plan that includes permalinks. General Activity ================ - Helpful edits for community.a.o and incubator.a.o - Continued migration from old ubuntu/puppet. - Gavin led another "Builds Meeting", with two people from GitHub in attendance to answer questions, and to take concerns, around the use of GitHub Actions (per the highlight above). - Beginning to explore Okta as an identity platform. It will be used for when we migrate to the Atlassian cloud products. We may be able to use Okta in other areas of the Foundation. - Ported the Buildstream repository (and other supporting data, and metadata) from Gitlab over to GitHub. - Some volunteers are assisting with Jira administration, and JDK support via bintray. - Beginning testing of GitHub's Container Registry, as their old package repository is deprecated and causing some issues. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Apologies for my tardiness. I will provide a full report next month. Only thing to note is I have received a Phase 1 proof of concept for the new TAC App, of which I am still evaluating before responding ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [Gris Cuevas] ## Description: - The Diversity and Inclusion VP works in collaboration with a team who 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: None ## Activity: *** Operations Preparing budget for 2021 FY Finalizing project wrap up with Bitergia *** Project: User Experience Research on new contributors *** Final report is underway Wrote and submitted an academic paper for CSCW (Computer-Supported Cooperative Work and Social Computing)[1]. CSCW is the premier venue for research in the design and use of technologies that affect groups, organizations, communities, and networks. Bringing together top researchers and practitioners, CSCW explores the technical, social, material, and theoretical challenges of designing technology to support collaborative work and life activities. The conference accepts novel, innovative and original work and typically has a 20-25% acceptance rate – which means it’s a very competitive conference. The conference had 900 participants in 2020. We have submitted our work for CSCW 2021 and we will know about how our paper did in April 2021, when we receive the review comments. We hopefully get an Accept or a Major Revision. This will make the research validated by a cross functional team of academics, helping us complete our first short term goal of providing scientific validates data on the state of D&I in the foundation. *** Project: Internships for underrepresented groups (Outreachy) *** 6 interns on 6 different projects. All projects proceeding as normal. You can check the working group notes here [2] ## Committee members changes: None. ## References [1] https://cscw.acm.org/2020/ [2]https://cwiki.apache.org/confluence/display/EDI/Outreachy+Working+Group+-+Meeting+notes ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 9: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] ----------------------------------------- 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. In December the ASF became the first organisation to get a live CVE name using the new CVE project automation API. Instead of the security team holding a pool of names requested in advance we now allocate them on demand, with the service taking care of emails to the PMC and other previously manual parts of the process. We expect more automation available over the coming year allowing us to streamline the CVE process for projects even further. Special thanks go to Accumulo, Airflow, CXF, NuttX, Tomcat, and Unomi who all used the new portal to handle vulnerabilities. Stats for Dec 2020: 18 [license confusion] 11 [support request/question not security notification] Security reports: 45 (last months: 45, 41, 32) 9 [site] 4 [servicecomb] 3 [httpd], [shardingsphere], [struts] 2 [activemq], [dubbo], [hadoop], [hbase], [openoffice], [tomcat] 1 [accumulo], [cordova], [flink], [gobblin], [infrastructure], [kafka], [kylin], [maven], [myfaces], [shiro], [skywalking], [wicket] In total, as of 30th December 2020, we're tracking 68 (last month: 64) open issues across 33 projects, median age 80 (last month: 90) days. 29 of those issues have CVE names assigned. 7 (unchanged since last month) of these issues, across 4 projects, are older than 365 days. None require escalation. ----------------------------------------- Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins] I've submitted the paperwork for the membership application. I'm now sorting out what membership at the $0 level affords us. Apparently to have any stake in things we may have to chip in more than $0 ($6075.25 approx. annually). That said, I'm not sure what the appetite here is for that level of involvement. I plan to further correspond via email to the board to ask if there is any such appetite. ----------------------------------------- Attachment A: Report from the Apache Accumulo Project [Ed Coleman] ## Description: The mission of Apache Accumulo is the creation and maintenance of software related to a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. It is based on Google's BigTable design and is built on top of Apache Hadoop, Zookeeper, and Thrift. ## Issues: Trademark issue with http://www.accumulodata.com: The owner of no longer has access to the email used to register the domain, and the registrar will not accept communications from alternate accounts. Currently, the domain is set to expire on 2021-06-28, and without access by the owner, should automatically expire. The Accumulo PMC is currently trying to determine if other actions are required. Initial emails are at [1] and follow-up discussions at [4]. Advice received Brand Management VP suggested that allowing the domain to expire in 6 months is a viable option and allows volunteer efforts to be put towards better uses. ## Membership Data: Apache Accumulo was founded 2012-03-20 (9 years ago) There are currently 38 committers and 38 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Ed Coleman approved on 2020-11-18 as PMC Chair and Vice President of Apache Accumulo. - Jeffrey Manno was added to the PMC on 2020-11-01 - Jeffrey Manno was added as committer on 2020-11-02 ## Project Release Activity: - accumulo-1.10.1 was released on 2020-12-22 [2] - accumulo-2.0.1 was released on 2020-12-24. [3] ## Project Activity: - CVE-2020-17533 [5] was reported on 2020-12-09 and resolved within 14 days. The CVE concerned allowed authenticated users to perform certain administrative operations without having the appropriate permissions. - Project activity on the next release remains active with significant improvements to the current baseline. The remaining issues are being actively worked. - There is community interest in improving support for cloud computing platforms (AWS, Azure) and alternate files systems. ## Community Health: - Mailing list participation and GitHub issues are consistent. - The large JIRA activity increase reflects migration or closing old JIRA issues in favor of using GitHub for issue tracking. - 3 new contributors, each from different organizations showing continued interest from a diverse community: - Szabolcs Bukros [Cloudera](https://www.cloudera.com/) - Seth Falco [Elypia](https://elypia.org/en-US/) - Dominic Garguilo [Arctic Slope Regional Corp](https://www.asrc.com/) ## Links [2]:https://lists.apache.org/thread.html/r947a56c98d0a8e009fa93df3b19e93761bfea8b236f30fb0c21b1992%40%3Cuser.accumulo.apache.org%3E [3]:https://lists.apache.org/thread.html/r38b0920499c9c88de282ca783debb9fbb8dc8ed88f5fc0ad9981bf97%40%3Cuser.accumulo.apache.org%3E [5]:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17533 ----------------------------------------- Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder] * Description ** Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST. * Activity ** ActiveMQ *** Apache ActiveMQ 5.15.14 has been released on 2020-12-10 *** We are already preparing 5.16.1 and 5.15.15 to address fixes, dependency updates (including CVE), and minor improvements *** ActiveMQ 5.17.0 is in preparation with full JDK11 build, leveldb and scala removal, preparation for new features (distributed store, cloud friendly features, ...) *** We will provide a dedicated landing page (subsite) to update the documentation, and give better visibility ** ActiveMQ Artemis *** Apache ActiveMQ Artemis 2.16.0 has been released on 2020-11-6 *** As part of the 2.16.0 we introduced a new DR asynchronous solution supporting multiple replicas. *** As part of the 2.16.0 we also introduced a major improvement on the Web Console. With a real nice new look & feel and pleasant for users. *** Performance has been significantly improved on the main path. AMQP is considered a main protocol in Artemis at this point. ** ActiveMQ NMS (.NET Clients) *** Apache ActiveMQ NMS OpenWire Client 1.8.0 has been released on 2020-12-28 **** This updated the OpenWire client to support .net core, work that has been slowly contributed over the past year, finally finished and released. *** Ongoing work with upgrading NMS to support JMS 2.0 features in .NET, initially API will be updated and first implemented in NMS AMQP Client. ** ActiveMQ CMS (C++ Clients) *** Whilst there has been no code activity, there has been some discussions in the dev mailing lists from the community about possibly re-igniting this and updating it. * Releases ** ActiveMQ 5.15.14 was released on 2020-12-10 ** ActiveMQ Artemis 2.16.0 released on 2020-11-6 ** Apache ActiveMQ NMS Openwire Client 1.8.0 has been released on 2020-12-28 * Committer/PMC Changes ** No new PMC members. Last addition was Jean-Baptiste Onofré on 2019-12-17 ** No new committers. Last addition was Domenico Francesco Bruscino on 2020-06-29 ----------------------------------------- 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 2012-09-18 (8 years ago) There are currently 41 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. The last addition was Sudhakar Pamidighantam on 2019-12-19. - No new committers. The last addition was Aarushi Bisht on 2019-12-19. ## Project Activity: The technical activity of the project is going as planned. We are refactoring the complex code into manageable chunks and started the release management documentation to make quick three releases in January. ## Community Health: The community is doing well, we are striving for attracting new contributions by lowering the barrier of entry through simplification of complex components. We plan to participate in GSoC to spur further community engagement. ----------------------------------------- Attachment D: 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: No issue. ## Membership Data: Apache APISIX was founded 2020-07-15 (6 months ago) There are currently 32 committers and 21 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 Xin Xu on 2020-09-18. - Guosheng Yang was added as committer on 2020-11-29 - Chao Zhang was added as committer on 2020-11-17 - acmly was added as committer on 2021-01-09 ## Project Activity: We released following versions. apisix-ingress-controller-0.1.0-rc2 was released on 2020-12-24. apisix-dashboard-2.2 was released on 2020-12-16. 2.1 was released on 2020-12-01. apisix-dashboard-2.1 was released on 2020-11-23. dashboard-2.0 was released on 2020-11-20. 2.0 was released on 2020-10-27. Several representations are made by our PMC member at COSCon2020, Apache Skywalking DevCon 2020, Apache APISIX DevCon 2020. ## Community Health: The community is healthy. People are active around the APISIX project. we reached 140+ code contributors for a single one repo(APISIX). dev@apisix.apache.org had a 14% increase in traffic in the past quarter (469 emails compared to 409) 876 commits in the past quarter (114% increase) 62 code contributors in the past quarter (21% increase) 736 PRs opened on GitHub, past quarter (72% increase) 749 PRs closed on GitHub, past quarter (87% increase) 850 issues opened on GitHub, past quarter (88% increase) 782 issues closed on GitHub, past quarter (101% increase) ----------------------------------------- Attachment E: 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: The only issue is not very signification and relates to the migration away from ASF CMS toward an Antora based site. While progress is slow, a recent report from the member working on this indicated that progress was being made. Since this is a volunteer, best effort, that's to be expected. ## Membership Data: Apache Aries was founded 2010-12-14 (10 years ago) There are currently 58 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-02. - No new committers. Last addition was Romain Manni-Bucau on 2020-01-29. ## Project Activity: Most activity has taken place in 3 projects, cdi, spifly over the last quarter, and most recently in jax-rs-whiteboard. There are more plans for even further activity on jax-rs-whiteboard and a couple of new integrations with it are being conceived. Of course the site migration away from AFS CMS is still in progress and we recently got an update that, while slowly, this is progressing. It should be noted that Aries does contain many widely used and highly stable components that, while they do not provide much activity, issues for them are important and are most often immediately addressed; Aries Blueprint, Aries Proxy, Aries SPI Fly to name just a few. ## Community Health: Community engagement seems to at least be stable while trending toward a slight improvement. However participation is still rather low. Hoping that new releases and a new site can inspire a little more activity. ----------------------------------------- Attachment F: Report from the Apache Arrow Project [Wes McKinney] ## Description: The mission of Apache Arrow is the creation and maintenance of software related to columnar in-memory processing and data interchange ## Issues: * After our past issues around scarce CI resources, we had managed to stabilize our CI setup around the relatively generous execution facilities provided by Github Actions, and a bunch of additional builds on other platforms (mostly for nightly builds). That equilibrium was unfortunately shattered after INFRA suddenly disallowed most third-party Github Actions helpers in response to security concerns. Our remaining Github Actions builds also seem to be queued longer. This has now been resolved (https://issues.apache.org/jira/browse/INFRA-21239) but it was hugely disruptive to our community. Concurrently, Travis-CI also started to be much stricter with resource consumption, which is currently affecting several of our nightly builds until we manage to migrate them to other CI services. These factors compounded mean we'll finally need to provide and set up our own CI resources. We hope to be able to migrate a significant number of builds to Buildkite, using execution resources paid by our sponsors. We also hope that INFRA rules around repository access and configuration won't stifle that endeavour. ## Membership Data: Apache Arrow was founded 2016-01-19 (5 years ago) There are currently 54 committers and 30 PMC members in this project. The Committer-to-PMC ratio is 9:5. Community changes, past quarter: - No new PMC members. Last addition was Francois Saint-Jacques on 2020-03-04. - Andrew Lamb was added as committer on 2020-11-06 ## Project Activity: - We'd like to release Arrow 3.0 around mid-January. The issues discussed above (diminished CI coverage due to disallowed third-party Github Actions, blocked nightly builds on Travis-CI, complex release procedure) make it more difficult than we'd like. - There seems to be growing interest in zero-copy zero-dependency cross-runtime interoperability using our "C data interface". It is now concretely possible to share data in-process between R, Python and Rust, without any shared code and without going through IPC mechanisms (the latter still possible, of course, using the Arrow IPC format). Other projects such as DuckDB have started using this interface. - The Arrow in-memory format is regularly being adopted and/or adapted to in other projects, especially in the dataframe and database communities. ## Community Health: * The project is overall very active. The Rust implementation is especially thriving, with numerous pull requests being submitted and merged in due time. The C++ implementation is advancing at similar speed as in previous reports. A Julia implementation was recently contributed. * Our pull request backlog has also grown slightly as a result of increased activity, but it does not seem to be posing a real problem for now. * The weight of our release procedure puts a burden on our capacity to release often. The "weight" is a function of the project complexity but also limitations in our CI/CD resources and feedback cycles (e.g. builds that run only once a day overnight often fail and we end up blocked on releasing until those failures are resolved). Our goal is to cut a new feature release roughly once every two months, which often ends up challenging. This situation also makes us reluctant to put out bugfix releases in-between, except for critical fixes. Improved CI/CD along with improvements to streamline the release process itself (for example, addressing procedural issues with preparing the Java project to release) would help a great deal. We also need more PMC members to step up and help with release management. Most of the release management over the lifetime of the project has fallen on the shoulders of only 4 out of our 30 PMCs. ----------------------------------------- Attachment G: 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 is healthy and engaged. Issues: There are no issues that require the board's attention at this time. PMC/Committership changes: - Rui Guo was added as a committer on 2021-01-12. - The last committer added was Rui Guo on 2021-01-12. - The last PMC member added was Xikui Wang on 2018-02-02. Releases: - Apache AsterixDB 0.9.6 was released on 2020-10-13. - Apache Hyracks 0.3.6 was released on 2020-10-13. ----------------------------------------- Attachment H: Report from the Apache Attic Project [Mads Toftum] ----------------------------------------- Attachment I: Report from the Apache Avro Project [Ismaël Mejía] ## 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-20 (10 years ago) There are currently 34 committers and 24 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Ryan Skraba on 2020-09-14. - No new committers. Last addition was Kengo Seki on 2020-07-08. ## Project Activity: Apache Avro 1.10.1 was released on 2020-12-03. This release keeps the expected pace of releases every six months discussed by the community. It updated many dependencies and fixed issues across the several languages supported. One particular issue fixes a regression that was blocking downstream projects (Apache Hive and Apache Spark) from upgrading to Avro 1.10.x. For more details see the announcement: https://s.apache.org/avro-1.10.1-announce The community decided to move its Continuous Integration jobs from Travis to Github Actions for stability reasons. The migration process is ongoing. For those who prefer metrics: Mailing Lists: - dev@avro.apache.org had 645 emails (34% decrease) - user@avro.apache.org had 32 emails (35% decrease) - issues@avro.apache.org had 232 emails (105% increase) JIRA: - 83 issues opened (76% increase) - 33 issues closed (26% increase) GitHub: - 81 PRs open (138% increase) - 46 PRs closed (70% increase) Code Repository: - 106 commits in the past quarter (211% increase) - 14 code contributors in the past quarter (-12% decrease) ## Community Health: Community health is doing well at drawing in contributions. The pace was higher during this quarter due to the release, however the number of contributors was smaller. The PMC keeps the ongoing track of recognizing contributors through committership. We have improved the release cadence in the last two years having in average a release every two quarters which is a good pace for a ‘mature’ project like Avro. We are also updating some of the technical infrastructure to make contributors experience better. ----------------------------------------- Attachment J: Report from the Apache Beam Project [Kenneth Knowles] ## Description: The mission of Apache Beam is the creation and maintenance of software related to a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Beam was founded 2016-12-20 (4 years ago) There are currently 75 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - No new PMC members. Last addition was Alexey Romanenko on 2020-06-11. - No new committers. Last addition was Heejong Lee on 2020-09-03. The cause of the stall is simply lowered PMC activity. It has been noted by the PMC and we are getting it moving again. ## Project Activity: In the core model there is big news: "Splittable DoFn" is now the default recommended way to write new data connectors. In simple terms: data sources are now dynamic. Previously, data connectors were a root of the computation graph (no inputs) and you said what you wanted to read before you started your job. Now data connectors take their input specification at runtime. This opens up a whole new realm of data processing, as you can take a "big data" number of Kafka topics or HDFS paths on input and read from all of them, and the rest of the Beam model "just works" with this (including unification of bounded and unbounded data and watermarks, etc). In the Python realm: - Python 2 and Python 3.5 support dropped! - Performance-driven type checking added (opt-in) [pytypes]. - An exciting new avenue for users is a Pandas compatible API. The goal is exact compatibility. To that end, we are running Pandas own test suite against the Beam module. - Beam's cross-language capabilities continue to expand: Java-based KinesisIO, SnowflakeIO, are available for Beam Python users In the Java realm: - Java 11 is officially supported and tested. Users are invited to use Java 11. - We have started to develop BOMs that simplify dependency management for users who have committed to a particular ecosystem (where "ecosystem" is deliberately undefined and user demand can drive new BOMs being made). - Our Hadoop connectors are now tested against Hadoop 3. In the SQL realm: a bunch more connector capabilities: - Avro, JSON, and Protobuf over Kafka - Avro over Pubsub - Bigtable connector - Thrift format support For the Flink runner there is a major change in the works: it was cloning every item of data needlessly. This was noticed, diagnosed, and fixed, reducing some pipeline runtimes by 80%. For the Dataflow runner there is a major migration happening: "Dataflow V2" is going more "all in" on Beam. Rather than translating Beam's pipeline model to the Dataflow API it is using Beam's model directly. This also enables cross-language pipelines and users to have simplified custom containers for their UDFs. FlinkRunner and SparkRunner already had "portable" variants, and this is the "portable" variant of Dataflow. (the term "portable" refers to using Beam's new "portability" APIs that allow all the language-agnostic goodness). Recent releases (we have a target cadence of 6 weeks): - 2.27.0 was released on 2021-01-08. - 2.26.0 was released on 2020-12-11. - 2.25.0 was released on 2020-10-23. ([pytypes](https://beam.apache.org/blog/python-performance-runtime-type-checking/) ## Community Health: There is an overall trend of reduced activity. The variance in usual quarters is pretty high, but I would guess the pandemic has had a significant effect. Verbatim stats, for reference: - dev@beam.apache.org had a 21% decrease in traffic in the past quarter (811 emails compared to 1017) - github@beam.apache.org had a 37% decrease in traffic in the past quarter (7584 emails compared to 11968) - issues@beam.apache.org had a 39% decrease in traffic in the past quarter (13471 emails compared to 21750) - 565 issues opened in JIRA, past quarter (3% increase) - 697 commits in the past quarter (-37% decrease) - 120 code contributors in the past quarter (-27% decrease) - 610 PRs opened on GitHub, past quarter (-27% decrease) - 586 PRs closed on GitHub, past quarter (-30% decrease) - 114 issues closed in JIRA, past quarter (570% increase) ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== There are no issues to raise to the Board at this time. Releases ======== There have been no releases since the last report. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Community & Development ======================= As noted in the last report to the board in September, discussions around the idea of migrating the project to the attic on the dev list appeared to demonstrate enough ongoing interest to continue the project. The PMC roll call email confirmed that there were 4 PMC members willing to provide the required oversight for the project. Development progress remains slow but it was agreed that the project would move to using git for new work. ----------------------------------------- Attachment L: Report from the Apache Calcite Project [Haisheng Yuan] ## 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: There are currently 51 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. No new committers or PMC members were added in the last 3 months. Calcite community has the tradition of annual rotation for PMC chair, Haisheng Yuan is selected as the new PMC chair. ## Project Activity: Calcite 1.26.0 was released on 2020-10-06, with important features such as supporting SEARCH operator and Sarg literal, adding PIVOT operator in SQL, adding support for JDK 15 and Guava version 29.0-jre. On Jan 20th, there will be online meetup for Calcite community with presentations covering Calcite concepts, recent work on streams, spatial query implementation. ## Community Health: The overall activity in the community has slightly decreased in the past few months without this being worrisome. 121 issues opened in JIRA and 79 issues closed in the past quarter (40% decrease). The fewer number of design discussions and JIRA activities can be explained by the holiday season and low number of active committers. commits by non-committers +--------------+------------+----------------+---------------------+ | quarter_date | committers | non_committers | total | +--------------+------------+----------------+---------------------+ | 2020-10-01 | 118 | 36 | 154 | top-5 reviewers +---------------------+-----------+ | reviews | committer | +---------------------+-----------+ | 7 | Julian Hyde | | 7 | Stamatis Zampetakis | | 6 | Chunwei Lei | | 6 | Ruben Quesada Lopez | | 4 | Danny Chan | | 4 | Wang Yanlin | ----------------------------------------- Attachment M: Report from the Apache CarbonData Project [Liang Chen] ## Description: - The Apache CarbonData is an indexed columnar 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: - Apache CarbonData has finished integration with Apache spark, Apache Flink, Apache Kafka, Presto etc. - The community released 2.1.0 , Some key features and improvements as belows: - Support Float and Decimal in the Merge Flow - Implement delete and update feature in carbondata SDK. - Support array with SI - Support IndexServer with Presto Engine - Insert from stage command support partition table. - Implementing a new Reindex command to repair the missing SI Segments - Support Change Column Comment - Presto complex type read support - SI global sort support - We organized two online discussion for planing 2021 feature list. ## Health Report: - Commit activity: - 75 commits in the past quarter (-31% decrease) - 17 code contributors in the past quarter (-19% decrease) - GitHub PR activity: - 98 PRs opened on GitHub, past quarter (-28% decrease) - 103 PRs closed on GitHub, past quarter (-25% decrease) ## Releases: - 2.1.0 was released on 2020-11-12. - 2.0.1 was released on 2020-06-01. - 2.0.0 was released on 2020-05-20. - 1.6.1 was released on 2019-10-25. ## Project Composition: - There are currently 26 committers and 15 PMC members in this project. - The Committer-to-PMC ratio is roughly 7:4. ## Community changes, past quarter: - Ajantha Bhat U was added to the PMC on 2020-11-15 - Indhumathi was added as committer on 2020-10-02 - Kunal Kapoor was added to the PMC on 2020-03-29 - Tao Li was added as committer on 2020-02-04 - Zhi Liu was added as committer on 2020-02-27 ## Notable mailing list trends:Mailing list activity stays at a high level - dev@carbondata.apache.org: - 178 subscribers (reduce 6): - dev@carbondata.apache.org had a 35% increase in traffic in the past quarter (104 emails compared to 113) - issues@carbondata.apache.org: - issues@carbondata.apache.org had a 15% decrease in traffic in the past quarter (3746 emails compared to 4400) - user@carbondata.apache.org: - 76 subscribers (no change): ## JIRA activity: - 76 issues opened in JIRA, past quarter (-41% decrease) - 85 issues closed in JIRA, past quarter (-26% decrease) ----------------------------------------- Attachment N: Report from the Apache Celix Project [Pepijn Noltes] ----------------------------------------- Attachment O: Report from the Apache CXF Project [Daniel Kulp] ## Description: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. There are also two sub-projects that leverage CXF: Fediz - Fediz helps you to secure your web applications via the standard WS-Federation Passive Requestor Profile. DOSGi - is the reference implementation of the Distribution Provider component of the OSGi Remote Services Specification ## Issues: There are no issues requiring board attention. ## Membership Data: Apache CXF was founded 2008-04-15 (13 years ago) There are currently 43 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Andy McCright on 2019-02-24. - No new committers. Last addition was Alexey Markevich on 2017-12-29. We have a few patches from various people, but nothing strong enough for consideration as a committer. We've tried to encourage some additional involvement from various people, but many people more or less disappeared over the holidays. ## Project Activity: The primary focus this period was bug fixes for a patch release for 3.4 that was released last period. There were several important regressions and bugs in 3.4 that were fixed as part of 3.4.2. Traffic on both the dev and users lists was up a bit this quarter as people started migrating to 3.4. Recent releases: 3.3.9 was released on 2020-12-28. 3.4.2 was released on 2020-12-28. Apache CXF Fediz 1.5.1 was released on 2020-11-30. ## Community Health: For the most part, the project is making steady, but not stellar, progress. Many of the protocols and specs that CXF implements are mature specs and don't really change much (other than the above mentioned package change from javax->jakarta). Thus, steady progress and regular releases are a good thing. We are responding to bug reports and security issues and getting patch releases out. ----------------------------------------- Attachment P: Report from the Apache DataFu Project [Matthew Hayes] ## Description: The mission of Apache DataFu is the creation and maintenance of software related to well-tested libraries that help developers solve common data problems in Hadoop and similar distributed systems. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache DataFu was founded 2018-02-20 (2 years ago) There are currently 19 committers and 11 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 Casey Stella on 2018-02-20. - No new committers. Last addition was Ohad Raviv on 2019-07-26. ## Project Activity: * Spark explode array method added. ## Community Health: * Eyal opened a discussion about whether to deprecate DataFu Pig and Hourglass libraries. ----------------------------------------- Attachment Q: Report from the Apache DataSketches Project [Lee Rhodes] ## Description: The mission of Apache DataSketches is the creation and maintenance of software related to an open source, high-performance library of streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods ## Issues: There are no issues requiring board attention. ## Membership Data: Apache DataSketches was founded 2020-12-15 (a month ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members (project graduated recently). - Charlie Dickens was added as committer on 2020-12-18 ## Project Activity: Over the past month (since graduation) we have been busy with the transition. With the holidays, we have had only two weeks to work on the transition, nonetheless, as of this writing, we are about 95% complete. We have a number of releases to do, which will be a strong test that we have all the pieces in the right place. Our last release was our C++, Python Core on Sep 22, 2020. We plan for a new release of Java Memory this month with a new release of our Java core shortly thereafter. ## Community Health: We suspect that some of the decrease in traffic on dev@ and users@ may be due to the holidays. Also, much of our code has been very stable in its quality, which is a good thing. We will be introducing some new sketches soon, which will indubitably have concomitant traffic. ----------------------------------------- Attachment R: Report from the Apache DB Project [Bryan Pendleton] ----------------------------------------- Attachment S: Report from the Apache Directory Project [Shawn McKinney] ## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - 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 (16 years ago) There are currently 58 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. - new committer Jiayi Liu on 2021-01-11 ## Project Activity: Overall: As first reported last quarter we are using the new CMS and the project website migration (using it) was successful, made possible by a large effort from a few members of our project team. Per sub-project: - ApacheDS: low activitity: security, bug fixes and work migrating to Junit 5. - LDAP API: very low activity. - Studio: low activity: being maintained, with latest eclipse compatibility (its framework) and move beyond Java 8 is required. - Fortress: low activity: security, bug fixes and enhancements. Planning for next release, late spring early summer. - Kerby: low activity: security and bug fixes. - Mavibot: low activity. It was heavily modified during 2Q 2020. At that time transactions across B-trees were added. Next is to add old revisions removal. This is quite a bit more work but the developer, Emmanuel Lecharny has made it clear that it will be done. It's considered important to the future of the directory server sub-project due to its promise of a stable database. - SCIMple: no activity. ## Community Health: No problems to report. 4Q activity continues to be low but steady across most of the sub-projects. ----------------------------------------- Attachment T: 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 We are currently starting the release process for our fifth major post-graduation release, 0.21.0, which we expect to have ready within the coming weeks. Additionally, we made our fourth major post-graduation release 0.20.0 on October 16, 2020. Since our last board report we have had 7 community virtual meetups in various "locations" across the globe (San Francisco, Bucharest, London, Bangalore), with 2 more scheduled in January (San Francisco, London). "Virtual Druid Summit IV", took place on 11/18, featuring talks from Druid adopters showcasing a variety of different use cases, with 402 registrations and 118 live attendees. Recordings of all talks so far can be viewed at the Druid summit website, https://druidsummit.org/. In-person events are still on hold due to COVID-19 related concerns around nonessential gatherings. Mailing list activity is a bit lower over the past quarter, but seems relatively typical for the holiday season (commit and PR activity show a similar decrease), with 76 emails on the dev list (dev@druid.apache.org) over the last quarter. Our ASF Slack channel, #druid, has continued to grow, and has reached over 1300 members, with daily activity of users asking questions and offering support to each other. ## Recent PMC changes - Currently 27 PMC members. - No new PMC members since graduation. ## Recent committer changes - Currently 41 committers. - No new committers this quarter. - Most recently added committer: - Atul Mohan (Aug 28 2020) ## Recent releases - 0.20.0, a major release, was released on October 16, 2020 ## Development activity by the numbers In the last quarter: - 330 pull requests opened - 344 pull requests merged/closed - 182 issues opened - 132 issues closed - 46 contributors ----------------------------------------- Attachment U: Report from the Apache Dubbo Project [Ian Luo] ## Description: The mission of Apache Dubbo is the creation and maintenance of software related to a high-performance, lightweight, java based RPC framework. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Dubbo was founded 2019-05-15 (2 years ago) There are currently 59 committers and 20 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - Yincheng Fang was added to the PMC on 2020-10-13 - Joe Zou was added to the PMC on 2020-10-26 - Hao Hongfan was added as committer on 2020-12-30 ## Project Activity: - dubbo-go has 3 releases in total in this quarter, including 1.5.3, 1.5.4, 1.5.5, and 1.5.6 is still under development. The community starts to work on dubbo-go 3.0 to align with dubbo java but the progress is slow. - dubbo don't have any release in this quarter, 2.7.8 is still under development. We are focusing on dubbo 3.0 development, and security issues reported against 2.7.8. In order to improve regression, we are building dubbo-samples as dubbo's integration test. - dubbo 3.0 is under development and is expected to have a preview release in late of this month. - dubbo-website is rebuilt based on docsy in order to enhance user experience. ## Community Health: - dev@dubbo.apache.org had a 53% decrease in traffic in the past quarter (91 emails compared to 192) - 815 commits in the past quarter (11% increase) - 103 code contributors in the past quarter (37% increase) - 416 PRs opened on GitHub, past quarter (46% increase) - 357 PRs closed on GitHub, past quarter (45% increase) - 312 issues opened on GitHub, past quarter (-5% decrease) - 126 issues closed on GitHub, past quarter (-62% decrease) From the stats in this quarter, it appears the community needs to focus on issue and pull request, and release more frequently on the branch of 2.7 in the next quarter. ----------------------------------------- Attachment V: Report from the Apache ECharts Project [Wenli Zhang] ## Description: Apache ECharts is a powerful, interactive charting and data visualization library for browser. ## Issues: We have completed the new TLP tasks at jira https://issues.apache.org/jira/browse/INFRA-21290 . ## Membership Data: Apache ECharts was founded 2020-12-16 (23 days ago) There are currently 22 committers and 14 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. No new PMC member or committers added this quarter because we are mainly working for the graduation and the major release. But we do find some qualified candidates and should take further look next quarter. ## Project Activity: We released a major version 5.0.0 on 2020/12/02. In this version, we provide more than 15 new features. The overall consideration is to make it easier for developers to tell a better story with Apache ECharts. Features include: - Story-telling: We improved the ability to provide an easier way to show the changes of data overtime. - Visual Design: We optimized design based on visualization theory to allow readers to have a better understanding of the data. - Interaction: Multi-state design allows readers to participate in the interaction, the richness and fluency of the interaction makes the users understand the association between data more deeply. - Developer Experience: More powerful and better to use by default, so that developers do not need to worry about data processing, i18n and other issues, so that they can focus on telling a better story of the data. - Accessibility: With a more accessible default theme and using decal patterns to distinguish data, ECharts 5 make it easier for developers to enable accessibility design for their charts and let more people understand the story behind the data. We are also working on more tutorial posts and videos to help the users learn about this major release. These promoting jobs should be done before the end of Jan 2020. We are currently testing our next release and hopefully should start voting next week. ## Community Health: We are working with Sally Khudairi on the graduation announcement. Thanks to Sally's help, it's almost finished now. We plan to announce the graduation in Jan 2021 soon. Commit activity: 473 commits in the past quarter (-29% decrease) 17 code contributors in the past quarter (-22% decrease) GitHub PR activity: 128 PRs opened on GitHub, past quarter (18% increase) 136 PRs closed on GitHub, past quarter (17% increase) GitHub issues: 458 issues opened on GitHub, past quarter (20% increase) 330 issues closed on GitHub, past quarter (-13% decrease) ----------------------------------------- Attachment W: Report from the Apache Fineract Project [Awasum Yannick] ## Description: The mission of Apache Fineract is the creation and maintenance of software related to a core banking platform that provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world's underbanked and unbanked. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Fineract was founded 2017-04-19 (4 years ago) There are currently 41 committers and 20 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 Aleksandar Vidakovic on 2020-10-11. - No new committers. Last addition was Percy Enoabane on 2020-10-02. ## Project Activity: We have had a lot of end user questions around Fineract 1.x probably due to people deploying the latest 1.4 release we did in late September. Customer support questions now account for more than 50% of the emails we get on our Dev list. These issues or questions are being addressed in a timely fashion and those that cannot be fixed immediately are logged on JIRA for volunteer developers to pick up and fix. We are beginning to have conversations around reorganizing the mailing lists: adding back the dedicated users list which we disabled back in 2018. This discussion is ongoing and we have not yet come to a consensus. Alek, Mike and Petri worked a lot on expanding the swagger documentation and create sample SDK clients for Fineract over the past few months. Fineract 1.5.0 has been planned for the first quarter of 2021. Given the moderate rate of contributions, we think it makes sense to release a new version once every 3 months. Rahul Pawar, one of our GSoC 2020 intern kept working on his Credit Bureau Integration into Fineract projecct by adding more features which enables Financial Institutions to check credit histories of customers before processing loan applications Fineract CN:- We currently have 1 Outreachy intern working to improve Fineract CN. Audrey Ndum under the supervision of Committer Kaze Nasser is working to upgrade the deprecated dependencies in Fineract CN. So far she has update a few microservices left over when the project started. We think she will be done with all this by February. ## Community Health: Both Fineract 1.x and Fineract CN remain healthy as we see traction the the Dev list and JIRA. There is a sharp decrease (above 50%) in email traffic on our Dev List probably due to holiday seasons in December. Number of issues reported have also dropped sharply probably as a result of the recently released Fineract 1.4 which may have fixed some issues for end users. Code Contributors, PRs opened and commits made have drops by more than 40% as the solution gets more stable and vacation in December. We need to do better to get more people engaged with the community. ----------------------------------------- Attachment X: Report from the Apache Fluo Project [Keith Turner] ## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (3 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: * All issues outstanding for a 2.0.0 release were resolved. An assessment was conducted to determine if Fluo is ready for a release and shared on the mailing list for discussion. The assessment determined there is more that could be done before release, but nothing that would block a release. There was agreement with this finding on the mailing list. * Nice improvements were made to the way Uno downloads dependencies. * Uno was updated to support running multiple Accumulo tablet servers. * Updates were made to Uno and Muchos subproject to work w/ latest Accumulo and Fluo dependencies. * Noticed the checksum on an InfluxDB rpm used by Muchos changed. Reached out to the influxdb team and they were not sure why it changed. Researched this and found it was resigned. ## Community Health: Activity on the project was very low this quarter. No large changes were made, mostly smaller maintenance fixes were made. Any hurdles blocking a release were cleared and we are ready to do a release. There were 19 commits from 5 committers and 3 contributors. One of the contributors was completely new to Fluo. ----------------------------------------- Attachment Y: Report from the Apache Geronimo Project [Romain Manni-Bucau] ## 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 (17 years ago) There are currently 70 committers and 40 PMC members in this project. The Committer-to-PMC ratio is 7:4. Community changes, past quarter: - No new PMC members. Last addition was Jean-Baptiste Onofré on 2020-10-05. - Jean-Baptiste Onofré was added as committer on 2020-10-05 ## Project Activity: Recent releases: - batchee-0.6 was released on 2020-11-15. - jcache-simple-1.0.5 was released on 2020-11-15. - jwt-auth-1.0.4 was released on 2020-11-15. - javamail_1.6-1.0.0 was released on 2020-10-19. - javamail_1.6_spec-1.0.0 was released on 2020-10-19. We also got some activity around Geronimo Arthur (GraalVM wrapper) with the OpenWebbeans support addition which can trigger a release soon. ## Community Health: User list seems kind of abandonned but we have some very good activity on dev list and commit metrics. The main activity was to push a new specification implementation (javamail 1.6) and some maintenance of other specification implementations. We are expecting more activity to come around Arthur probably and new Java versions requiring some our tool releases for ASF projects. ----------------------------------------- Attachment Z: 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 (2 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: - 0.6.0 was released on 2020-11-09, this release broaden griffin scenarios. - We are considering to enhance our data quality DSL. - We are considering update griffin to support apache spark 3.0.1 ## Community Health: - dev had a 50% decrease(100 emails) in traffic in the past quarter. - 8 issues opened in JIRA, past quarter (-33% decrease). - 25 commits in the past quarter (733% increase). ----------------------------------------- Attachment AA: 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: The Ozone sub project completed split from the Hadoop project. The transition went well. ## Membership Data: Apache Hadoop was founded 2008-01-15 (13 years ago) There are currently 228 committers and 119 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Eric Badger was added to the PMC on 2020-11-17 - Takanobu Asanuma was added to the PMC on 2020-11-08 - No new committers. Last addition was Lisheng Sun on 2020-10-01. ## Project Activity: No new release was announced in this quarter. However, several RCs for 3.2.2 was cut and voted on several times in this quarter. 3.2.2 later passed vote in January 2021. One CVE was announced: CVE-2018-11764 Apache Hadoop Privilege escalation in web endpoint Web endpoint authentication check is broken. Authenticated users may impersonate any user even if no proxy user is configured. Versions affected: 3.0.0-alpha4, 3.0.0-beta1, 3.0.0 Fixed versions: 3.0.1 Impact: privilege escalation Reporter: Daryn Sharp Reported Date: 2018/03/17 Issue Announced: 2020/10/21 Hadoop Common: The object store work is keeping people busy. * There's now a storage connector for HuaweiCloud Object Storage, so Hadoop and other applications using the FileSystem APIs can work with data stored in Huawei's cloud. * A new IOStatistics API has gone in to allow applications to query input classes (filesystems, streams, iterators) for IO performance details. This should allow tests and applications to identify performance issues during profiling and hopefully production * AWS S3 is now consistent. This enables the maintainers of the S3A connector to remove all the S3Guard code, which relied on DynamoDB for a consistent view of the data. They are looking forward to this. * The guava update is becoming a major friction for downstream applications to adopt new Hadoop releases. The community is working to shade guava as the solution. (HADOOP-16924) * The native compression libraries for Snappy and LZ4 are now shipped with Hadoop binary, no longer requiring manual installation of the native libraries on the host machines, making them easier to use. (HADOOP-17125 and HADOOP-17292) HDFS: * A new encryption codec "SM4/CTR/NoPadding" was added (HDFS-15098). * HDFS Router Based Federation received a number of new improvements, including balancer (HDFS-15294), isolation (HDFS-14090). Rename support is being worked on, starting this quarter. (HDFS-15747) * The new View FS implementation is near completion. (HDFS-15289) * The community is working to add dynamic mount support for both read and write for HDFS Provided Storage. (HDFS-15714) * Dynamic disk-level tiering (HDFS-15547) continued from last quarter. YARN: * The consolidation of FairScheduler and CapacityScheduler started in Q3 and is near completion. (YARN-10370) * Capacity scheduler is being enhanced to support auto queue creation. (YARN-10496) ## Community Health: Overall, the community participation appears relatively healthy despite Ozone's recent move to TLP. We had a steady supply of new contributors and new features this quarter. Erasure Coding appears to get traction in the last two quarters. Numerous EC bug fixes and improvements were raised this quarter. It looks like Hadoop 3 is getting adopted. Code development and mailing list traffic were both down significantly quarter over quarter, possibly due to the holiday season. Traffic in ozone-dev and ozone-issues mailing lists were down because of the Ozone TLP. dev@hadoop.apache.org had a 75% decrease in traffic in the past quarter (10 emails compared to 39) general@hadoop.apache.org had a 67% decrease in traffic in the past quarter (15 emails compared to 45) mapreduce-issues@hadoop.apache.org had a 39% increase in traffic in the past quarter (237 emails compared to 170) ozone-dev@hadoop.apache.org had a 93% decrease in traffic in the past quarter (13 emails compared to 174) ozone-issues@hadoop.apache.org had a 80% decrease in traffic in the past quarter (1180 emails compared to 5804) user@hadoop.apache.org had a 30% decrease in traffic in the past quarter (56 emails compared to 80) user-zh@hadoop.apache.org had a 45% decrease in traffic in the past quarter (5 emails compared to 9) 322 issues opened in JIRA, past quarter (-31% decrease) 242 issues closed in JIRA, past quarter (-34% decrease) 591 commits in the past quarter (-3% decrease) 82 code contributors in the past quarter (-16% decrease) 214 PRs opened on GitHub, past quarter (-13% decrease) 185 PRs closed on GitHub, past quarter (-20% decrease) In addition to mailing lists, JIRA and GitHub PR, we are seeing more traffic in the official ASF slack hdfs (113 users), hadoop (119 users) and yarn (39 users) channels over the last quarter. They are being used to communicate community online meetup events and troubleshooting issues. ----------------------------------------- Attachment AB: Report from the Apache HAWQ Project [Lei Chang] ## Description: HAWQ is a SQL query engine that combines the key technological advantages of MPP database with the scalability and convenience of Hadoop and Cloud. HAWQ delivers industry-leading performance and linear scalability. It provides users the tools to confidently and successfully interact with petabyte range data sets. HAWQ provides users with a complete, standards compliant SQL interface. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache HAWQ was founded 2018-08-15 (2 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 Amy Bai on 2018-08-15. - No new committers. Last addition was Stephen Tuyu on 2019-08-23. ## Project Activity: - Recent release: 2.4.0.0 was released on 2018-09-21 - Activity: 2020 PostgreSQL Conference China ## Community Health: Overall community health is action required. The development of Apache HAWQ is pretty good in the past quarter, with 213% increase in the issue traffic, 200% increase in the opened JIRA, and 400% increase in the closed JIRA. The reason is that we focused on the new features and facilities which were added to the project recently. However, we need to be more active in the community. Such as discuss and draft the roadmap, plan the new releases, have more interaction in the dev@hawq.apache.org, make more more committers and PMC members in the project. ----------------------------------------- Attachment AC: Report from the Apache HBase Project [Duo Zhang] ## Description: Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. hbase-thirdparty is a set of internal artifacts used by the project to mitigate the impact of our dependency choices on the wider ecosystem. hbase-connectors is a collection of integration points with other projects. The initial release includes artifacts for use with Apache Kafka and Apache Spark. hbase-filesystem contains HBase project-specific implementations of the Apache Hadoop FileSystem API. It is currently experimental and internal to the project. hbase-operator-tools is a collection of tools for HBase operators. Now it is mainly for hosting HBCK2. hbase-native-client is a client library in C/C++, in its early days. ## Issues: ## Membership Data: Apache HBase was founded 2010-04-21 (11 years ago) There are currently 92 committers and 54 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 Viraj Jasani on 2020-10-03. - Yulin Niu was added as committer on 2020-12-03 - Xin Sun was added as committer on 2020-12-03 ## Project Activity: Recent releases: 2.4.0 was released on 2020-12-15. hbase-thirdparty-3.4.1 was released on 2020-11-27. 2.3.3 was released on 2020-11-02. A new minor release line 2.4.x has been established, which is the fifth minor release line for 2.x. We discussed whether to purge the hbase-backup module because it has not been included in any releases and now lack maintenance and there was a user in the community who wanted to maintain it. https://s.apache.org/k5b9i We discussed how to better make use of 'Signed-off-by' in the commit message. There is no consensus so far, mainly because whether to use 'Reviewed-by' instead of 'Signed-off-by' for non committer reviewers. https://s.apache.org/tgjup We decided to move the stable pointer to 2.3.x and EOL the 2.2.x release line. The final release for 2.2.x will be 2.2.7. https://s.apache.org/7rqow We switched from OpenTracing to OpenTelemetry for implementing our tracing system. https://issues.apache.org/jira/browse/HBASE-22120 ## Community Health: - Mailing list activity: dev@hbase.apache.org: 985 subscribers(989 in the previous quarter) 1014 emails sent to list(1167 in the previous quarter) user@hbase.apache.org: 2080 subscribers(2085 in the previous quarter) 85 emails sent to list(87 in the previous quarter) user-zh@hbase.apache.org 71 subscribers(69 in the previous quarter) 35 emails sent to list(41 in the previous quarter) - JIRA activity: 296 issues opened in JIRA, past quarter (-35% decrease) 226 issues closed in JIRA, past quarter (-46% decrease) - Commit activity: 809 commits in the past quarter (-30% decrease) 73 code contributors in the past quarter (1% increase) - GitHub PR activity: 337 PRs opened on GitHub, past quarter (-34% decrease) 313 PRs closed on GitHub, past quarter (-38% decrease) We had a new minor release this quarter but still not too many new commits. This means 2.x is getting more and more stable and no big new features for 2.x. This is a sign that we may need to kick the 3.0.0 release. A good news is that the number of contributors remained at the same level. ----------------------------------------- Attachment AD: Report from the Apache Hive Project [Ashutosh Chauhan] ## Description: The mission of Hive is the creation and maintenance of software related to Data warehouse infrastructure using the Apache Hadoop Database ## Issues: No issues requiring board's attention at this time. ## Membership Data: Apache Hive was founded 2010-09-21 (10 years ago) There are currently 94 committers and 49 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 Anishek Agarwal on 2020-02-10. - Aasha Medhi was added as committer on 2021-01-08 - Mustafa İman was added as committer on 2020-11-11 - Pravin Sinha was added as committer on 2020-12-18 ## Project Activity: Community is in progress of making release on 2.3 line. Encouraging to see maintenance release being driven by multiple community members. ## Community Health: Last quarter saw bit of decrease of activity across jira and mailing list. We attribute that to end of year holiday season slowdown. Nothing concerning. ----------------------------------------- Attachment AE: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for January 2021 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 40 podlings incubating. In December, podlings executed 9 distinct releases. We added three new IPMC members, and none retired. There was one IP clearance in December. We have one new project Wayang. ECharts and DataSketches graduated last month, and Ratis and Flagon should graduate next month. Annotator and Liminal, which failed to report last month, have reported this month. BRPC did not report again, and a role-call will be carried out to see if there is still an active PMC. This month we were missing reports from BRPC, Livy, PonyMail and Weex. BlueMarlin still seems to be having some difficulty communicating on their mailing lists. They have submitted a report this month which is a good start. Liminal has corrected the issue with its unapproved releases. S2Graph will be retired shortly. Weex, who was considering retirement, has managed to get the needed 3 +1 PPMC votes for a release and their release is now up for IPMC vote. SAMOA currently has no mentors but given there's little, or no activity on the mailing list and no commits for 9 months that's not a big issue. The project will be encouraged to retire. Andrew Wetmore went though and simplified the language on many incubator site pages, including the policy page. There's a couple of missing links that still need to be corrected. The major licensing issue with MXNet has been resolved with permission given to distribute it under the Apache 2.0 license. There are still several trademark and branding issues that need to be resolved. The project states it's nearing graduation, but IMO some work still needs to be done before that can happen. Their last release failed to get the required number of IPMC votes due to the difficultly in reviewing it. The previous releases containing Category X code still have not been removed (see INFRA-20442). Most discussions on the mailing list were around releases and graduations. There were graduation discussions around ECharts, Flagon, Ratis and Goblin. ## Community ### New IPMC members: - Ming Wen - Maximilian Michels - Francois Papon ### People who left the IPMC: - None ## New Podlings - Wayang ## Podlings that failed to report, expected next month - BRPC - Livy - PonyMail - Weex ## Graduations - ECharts - DataSketches The board has motions for the following: - Gobblin ## Releases The following releases entered distribution during the month of December: - DolphinScheduler 1.3.4 - ECharts 5.0.0 - Gobblin 0.15.0 - NLPcraft java-client 0.7.2 - Nemo 0.3 - NuttX 10.0.0 - NuttX 10.0.1 - NuttX 9.1.1 - TubeMQ 0.7.0 ## IP Clearance - OpenWhisk IDE plugins ## Legal / Trademarks - MXNet license issue resolved - Trademark issues seem to be coming a more common issue with graduating projects ## Infrastructure - ASF's GitHub actions limits are causing some projects issues but this is being looked into by Infra. ## Miscellaneous - N/A ## Table of Contents [Annotator](#annotator) [BlueMarlin](#bluemarlin) [DataLab](#datalab) [Flagon](#flagon) [Gobblin](#gobblin) [Hop](#hop) [Liminal](#liminal) [Milagro](#milagro) [MXNet](#mxnet) [NuttX](#nuttx) [Pegasus](#pegasus) [Teaclave](#teaclave) [TubeMQ](#tubemq) [Wayang](#wayang) [YuniKorn](#yunikorn) -------------------- ## 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. Communicate clear roadmap 2. Add active contributors 3. Demonstrate good governance through voting on process improvements. ### 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? Community calls continue. A few new developers have reached out with interest in using and contributing to the project. ### How has the project developed since the last report? Significant code reorganisation has been undertaken to generalise the selector algorithms such that they could be applied to other document types/representations than the DOM. A performance issue has been resolved after feedback from early adopters. ### How would you assess the podling's maturity? - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2020-07-11 ### When were the last committers or PPMC members elected? 2018-09-04 ### Have your mentors been helpful and responsive? As for a while only one mentor was active and responsive, Benjamin Young has been added as mentor to facilitate processes. ### Is the PPMC managing the podling's brand / trademarks? No issues at this time. ### Signed-off-by: - [X] (annotator) Nick Kew Comments: Apologies for recent reporting hiatus. The project feels like it could be picking up momentum, though that has yet to translate into community growth. - [ ] (annotator) Tommaso Teofili Comments: - [X] (annotator) Benjamin Young Comments: ### IPMC/Shepherd notes: -------------------- ## BlueMarlin BlueMarlin will develop a web service to add intelligence functionality to a plain ad system. BlueMarlin has been incubating since 2020-06-09. ### Three most important unfinished issues to address before graduating: 1. Bootstrap the project (code donation, legal files) 2. Cut the first incubating release 3. Grow up community ### Are there any issues that the IPMC or ASF Board need to be aware of? No issue ### How has the community developed since the last report? We are in the bootstrapping phase (take longer than expected) ### How has the project developed since the last report? This is the first report, bootstrapping in progress ### 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: No release for now ### When were the last committers or PPMC members elected? N/A ### Have your mentors been helpful and responsive? JB proposed to help. ### Is the PPMC managing the podling's brand / trademarks? Yes, we are in the check phase. ### Signed-off-by: - [ ] (bluemarlin) Craig Russell Comments: - [X] (bluemarlin) Jean-Baptiste Onofré Comments: We don't have lot of interaction with BlueMarlin team. I will ping them a new time. Update: I have been pinged by BlueMarling guys, I will move forward with them. - [ ] (bluemarlin) Von Gosling Comments: I couldn't receive the team any feedback which was a little disappointing. I have ping team again and like to see does the team still needs help? - [ ] (bluemarlin) Junping Du Comments: - [ ] (bluemarlin) Uma Maheswara Rao G Comments: ### 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: Finish preparing all artifacts necessary for graduation ### Are there any issues that the IPMC or ASF Board need to be aware of? No issues ### How has the community developed since the last report? We have a new committer (java-developer) - Yurii Kinash. ### How has the project developed since the last report? - We are working towards the release 2.5.0 - Migration to Py3 (in progress) - Edge node recreation capability (in progress) - Support of Spark v.3.x.x (open) - Localization (done) - Switch to modular architecture (in progress) - Augment an administrative page (in progress) - Bug fixing ### 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 - [X] Other: working towards next release ### Date of last release: 2020-17-09 ### When were the last committers or PPMC members elected? The last committer was elected on December 10, 2020. ### Have your mentors been helpful and responsive? Yes, our mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues. New name was approved and our team changed all references to DLab that are publicly accessible to DataLab, including code base, presentations, documentation, etc. ### Signed-off-by: - [ ] (datalab) P. Taylor Goetz Comments: - [ ] (datalab) Henry Saputra Comments: - [ ] (datalab) Konstantin I Boudnik Comments: - [X] (datalab) Furkan Kamaci Comments: ### IPMC/Shepherd notes: -------------------- ## 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. Work with IPMC to approve draft graduation resolution 2. Add DISCLAIMER and make read-only subprojects to be retired (TAP, STOUT, etc.) 3. Add logo to appropriate Apache outlet (logos.apache.org) ### Are there any issues that the IPMC or ASF Board need to be aware of? No issues at this time. ### How has the community developed since the last report? Not significantly. ### How has the project developed since the last report? - We are working towards UserALE release 2.1.1 - We have been actively engaged with an expanding user base - Core product source code is well maintained - Preparing to complete outstanding graduation actions ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-03-27 ### When were the last committers or PPMC members elected? - Furkan (Mentor) 2019-07-24 - Tim Allison (Mentor) 2019-07-17 - Arthi Vezhavendan (PPMC) 2017-01-24 ### Have your mentors been helpful and responsive? - Our mentors have been very supportive and responsive - Our mentors have urged us to create a Graduation resolution ### Is the PPMC managing the podling's brand / trademarks? - To date, there are no known issues of 3rd Party misuse of brand - 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow. - 'Flagon' branded graphics will conform to Apache's Trademark and Branding policies. ### Signed-off-by: - [X] (flagon) Lewis John McGibbney Comments: Flagon was to do degree blokced from graduating within the last ~3 months. I personally felt that the IMPC review of the DRAFT graduation resolution could have been better handled by the IPMC. There were a number of non-blocking items which were raised and which eventually impacted the motivation to graduate. It would be nice if Flagon could graduate as ther podling has shown excellent underatanding of the Apache Way and it's patience to mature as a podling. I will work with the Flagon PPMC on the next steps as highlightes in the above report. - [ ] (flagon) David Meikle Comments: - [ ] (flagon) Tim Allison Comments: - [X] (flagon) Furkan Kamaci Comments: ### IPMC/Shepherd notes: Justin Mclean: Looking at the email discussion I can't see how it was blocked, a few minor things were raised that were easily fixed. All of the proposed PMC members have still not signed up the the private list. -------------------- ## Gobblin Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. Gobblin has been incubating since 2017-02-23. ### Three most important unfinished issues to address before graduating: 1. Discuss and Vote in progress in general@incubator mailing list for graduation to TLP. ### 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? - Email stats since last report: dev@gobblin.incubator.apache.org : 505 (Oct), 324 (Nov), 313 (Dec) - There have been 63 Commits since last report: git log --format='%ci' | grep -cE '((2020-1(0|1|2)))' - 29 ie. 46% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '(2020-1(0|1|2))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n ### How has the project developed since the last report? 1. Vote within community for graduation to TLP was passed after a discussion. Discuss and vote was started in general@incubator. 2. Roster, project page, documentation, website, and wiki were reviewed and updated. 3. Evaluation under Apache maturity model for graduation was done. 4. Podling name search was done. 5. New version (0.15.0) was approved and released. On technical side, the following was added: 1. Support for Kafka 1.1. 2. Decimal type support in GobblinORCWriter. 4. LDAP based group ownership support. 5. New Groups ownership service. 6. Azkaban OAuth token support. 7. Gradle version was upgraded. 8. Auto-tune of ORC writer params. 9. Support for multiple DFS tokens fetch for HDFS federation. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-12-10 ### When were the last committers or PPMC members elected? Tamás Németh and Sudarshan Vasudevan for PPMC in June, 2020. ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [X] (gobblin) Jean-Baptiste Onofre Comments: - [ ] (gobblin) Olivier Lamy Comments: - [X] (gobblin) Owen O'Malley Comments: ### IPMC/Shepherd notes: -------------------- ## Hop Hop is short for the Hop Orchestration Platform. Written completely in Java it aims to provide a wide range of data orchestration tools, including a visual development environment, servers, metadata analysis, auditing services and so on. As a platform, Hop also wants to be a reusable library so that it can be easily reused by other software. Hop has been incubating since 2020-09-24. ### Three most important unfinished issues to address before graduating: 1. identify and resolve the last remaining incompatibly licensed dependencies (if any) 2. create a first release 3. grow the community ### Are there any issues that the IPMC or ASF Board need to be aware of? No known significant issues at this moment ### How has the community developed since the last report? - 3 additional committers, lots of committer and community activity in the last month - 14 new registered chat members (108->122) - 1 new subscriber to dev (21->22), 0 to users mailing lists (11) - significant follower growth on LinkedIn (309->321), Twitter (233->253) and YouTube (40->50) ### How has the project developed since the last report? Two releases candidates (0.50-rc1, 0.50-rc2) were created but failed to get enough positive votes. Hop will take the feedback and lessons learned from 0.50-rc1 and 0.50-rc2 to build a new 0.60-rc1. Summary of the 2 RCs: https://s.apache.org/06hws December was a very active month, with continued activity over the holiday period: - metadata perspective - look and feel updates - new transform plugins (UDJC, Token Replacement) - partitioned stream lookup - docker included, community activity on kubernetes - jandex-based plugins - integration testing - community activity on Hop Web - documentation updates Full details are available in the December monthly roundup: https://hop.apache.org/blog/2021/01/roundup-2021-01/ ### 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: XXXX-XX-XX ### When were the last committers or PPMC members elected? 2020-12-2 ### Have your mentors been helpful and responsive? Julian Hyde and François Papon regularly check in and provide valuable input. We're sure our other mentors will step in for RCs after the holiday period. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues. The PPMC only uses "Apache Hop (Incubating)" as the official project name and has explicitly called "Project Hop" deprecated as of the moment of acceptance in the Incubator. ### Signed-off-by: - [X] (hop) Tom Barber Comments: I agree with Julian. The community is great, obviously a lot came from knowledge of the previous life and interest in seeing it progress which is good. The chat vs mailing list stuff is true, I don't follow the chat too much, just lurk but there is a lot going on there, not necessarily decision making but communication that could be missed for those who choose not to use it. Conversely I would say that a lot of the folk on the chat room are users as opposed to developers, and as such don't have to be treated in the same manner. Might be worth checking committers vs chat vs dev list? I suspect its probably pretty much up to date. Great progress on the software front, good to see it coming together. - [X] (hop) Julian Hyde Comments: Good report! I'd say you are through 'initial setup' and can uncheck that box next time. The community is going great, and I'm sure that the first release will happen very soon. One concern: the difference in the number of people on chat vs the dev list (122 vs 22). The traffic on chat is benign (e.g. no major decisions being made) but I am concerned that with so few of the regulars on the dev list, chat will become the de facto place to make decisions. Also I couldn't find a public archive of chat. I'll raise this issue on the dev list. - [X] (hop) Maximilian Michels Comments: I'm continuing to be amazed by the progress of the Hop project. There is a constant flow of incoming pull requests and the first release is nearing completion. It might not be clear to all community members but I've tried to only step in when necessary, e.g. give feedback to unblock the release process. - [X] (hop) Francois Papon Comments: The community is still very active and starting to learn the release process. For now, the only issue in the release is the license part and the team is focused on it to prepare a new vote. - [X] (hop) Kevin Ratnasekera Comments: ### 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. First release (due next week) 2. Build a community 3. Define 2021 roadmap ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? We had a successful meetup and a presentation on Data & AI summit Europe. Discussing with few companies to join the effort. ### How has the project developed since the last report? The first release candidate is ready and verified, planning to have a formal release next week. ### 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: The first release candidate is ready and verified, planning to have a formal release next week. ### When were the last committers or PPMC members elected? NA ### Have your mentors been helpful and responsive? JB & Davor have been helpful. ### Is the PPMC managing the podling's brand / trademarks? No. ### Signed-off-by: - [X] (liminal) Jean-Baptiste Onofre Comments: First release has been done. - [ ] (liminal) Henry Saputra Comments: - [ ] (liminal) Uma Maheswara Rao G Comments: - [X] (liminal) Davor Bonaci Comments: Looking forward to the community review of the first release! - [ ] (liminal) Liang Chen Comments: ### IPMC/Shepherd notes: Justin Mclean: Individuals contribute to ASF projects not companies. I'm sure you know that, you just might want to be more careful with your language in future reports. -------------------- ## 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. 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. 2. Continue to improve compliance with the Apache Way. In particular to update the Milagro website and other project sites (e.g. Whimsy) in accordance with Apache policies. 3. Further releases to increase the scope of the Milagro project, extend the capability of existing releases and to demonstrate improved compliance with the Apache Way. ### Are there any issues that the IPMC or ASF Board need to be aware of? No significant issues, however some administrative tasks around the project are still outstanding but are being addressed. In particular, a PPMC meeting has been proposed for 3rd February to discuss outstanding issue with a follow on meeting for the entire Milagro community to discuss the project's roadmap. ### How has the community developed since the last report? No change. ### How has the project developed since the last report? Work continues on the C and Rust versions of the core cryptographic library and on preparing the Multi Party Computation library for its first official Apache release. ### 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: 2020-02-10 ### When were the last committers or PPMC members elected? February 2020 ### Have your mentors been helpful and responsive? No issues. ### Is the PPMC managing the podling's brand / trademarks? No known issues, but further investigation is still required by the Milagro community. ### Signed-off-by: - [X] (milagro) Nick Kew Comments: - [X] (milagro) Jean-Frederic Clere Comments: ### IPMC/Shepherd notes: Justin Mclean: What administrative tasks are still outstanding? -------------------- ## MXNet A Flexible and Efficient Library for Deep Learning MXNet has been incubating since 2017-01-23. ### Three most important unfinished issues to address before graduating: 1. Address licensing and trademark issues for the binary releases in the community. - ONGOING. Close to completion. See update in the next section. 2. Address release issues, improve automation for license checks, and make it easier for auditing. Successfully and smoothly make releases without WIP disclaimer. - ONGOING. 3. Improve brand management. - ONGOING. ### Are there any issues that the IPMC or ASF Board need to be aware of? 1. The community is fixing the remaining releases that have license issues. See summary below. 2. MXNet 2.0 first public beta, interoperable with NumPy, is on the way: https://github.com/apache/incubator-mxnet/projects/18 RFC: https://github.com/apache/incubator-mxnet/issues/16167 3. The community is including brand usage reviews as part of the quarterly report process to proactively manage our brand going forward. #### Status on license and branding issues Most of the issues from last update hinged on the resolution of LEGAL-516. We are very glad that LEGAL-516 concluded that ASF projects compiled using NVIDIA’s CUDA compiler may be distributed under the Apache License 2.0, which unblocks many of the distribution practices that are essential to the wide adoption of software that utilizes GPU. We would like to thank for the help, the patience, and the leniency and flexibility that the incubator and legal granted us, and the numerous helps we received along the way from the ASF members and our community members from NVIDIA. Especially, I would like to thank Michael O’Conner and Triston Cao from NVIDIA for pushing this through within their organization. Based on the conclusion of LEGAL-516, binary distribution of CUDA-compiled Apache projects can be properly licensed as ALv2. In addition, the branding issues from distribution pages from Amazon, NVIDIA, and Intel have all been acted on. As a result, among the 9 pending issues from last update, 5 can be resolved. We are following up on the remaining items to resolve all issues in INCUBATOR-253. As part of our improvement in brand management, we are including third-party brand usage review in our quarterly reports and we will keep it as part of our regular practice beyond graduation. Status on open issues since last update: 1. Source and convenance binary releases containing Category X licensed code. (pending item 5) * Source code releases by the PPMC do not contain Category X code.
 Takedown and backfill of compliant binary releases by the PPMC on repository.apache.org is in progress, see item 5.
 PyPI releases are made by third-party. See item 8. 5. Maven releases containing Category X licensed code. (pending) * Takedown of binary releases on repository.apache.org initiated (i.e. INFRA-20442). Based on the resolution of LEGAL-516, the takedown (and backfill) includes those that include GPL licensed components. We are working on this in the infra issue. 6. PyPI releases containing Category X licensed code. (Resolved) * The third-party releases are compliant with branding guidelines since the releases are from official source code releases and are properly licensed with ALv2. 7. Docker releases containing Category X licensed code. (Resolved) * The third-party releases are compliant with branding guidelines since the releases are from official source code releases and are properly licensed with ALv2. 9. Trademark and branding issues with PyPI and Docker releases. (Resolved) * These release are compliant with trademark and branding requirements since they don’t contain Category X licensed code and are licensed with ALv2 based on item 6 and 7. 10. Trademark and brand issues with naming of releases. (Resolved) * There are no binary releases by the PPMC besides the repository.apache.org releases in item 5. 14, 22, 23. Branding and release of 3rd parties containing unreleased code. Known pages with issues: * +https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20- 03.html+ (item 14, Resolved)
 NVIDIA switched to "NVIDIA Optimized Deep Learning Framework, powered by Apache MXNet” for naming. +https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&r ef_=srh_res_product_title+ (item 22, pending) PPMC reached out to Bitnami directly regarding this listing. Bitnami responded but the page still needs update. We followed up again with Bitnami this week. +https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MX Net+ (item 23, pending) PPMC reached out to AWS through internal channel to fix branding issue. Amazon intends to use AWS MX powered by Apache MXNet naming convention. The naming change is in progress. After last update, for item 15, SourceForge further added a disclaimer that the page is an automatic mirror of MXNet’s GitHub tags: +https://sourceforge.net/projects/apache-mxnet.mirror/+. In addition, MXNet PPMC identified several more listings that require correction according to the branding guideline on AWS marketplace that are related to AWS Deep Learning Container/DLAMI, and they have all been resolved. From recent brand usage review for MXNet third-party distributions, we found several listings on AWS marketplace that need update. The PPMC is reaching out to the publishers of these listings for correction. https://aws.amazon.com/marketplace/pp/B079225XXC?qid=1609989161134&sr=0-14&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B07MP6Y8XT?qid=1609989161134&sr=0-17&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B073SHB43M?qid=1609989286506&sr=0-21&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B01JJ31R8C?qid=1609989286506&sr=0-22&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B07F3YBMT9?qid=1609989286506&sr=0-23&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B084FXK9XH?qid=1609989286506&sr=0-24&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B08L8H9NWD?qid=1609989286506&sr=0-28&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B08G8VXC1Q?qid=1609989286506&sr=0-29&r ef_=srh_res_product_title https://aws.amazon.com/marketplace/pp/B07C49CVC1?qid=1609989286506&sr=0-30&r ef_=srh_res_product_title ### How has the community developed since the last report? * The number of GitHub contributors increased to currently 948 (2019-10-08; +13% since last report) * Active blogs and social media presence * Medium (https://medium.com/apache-mxnet) w/ 2k followers (+3%) * Active video channels * YouTube channel (https://www.youtube.com/apachemxnet) w/ 1.33k subscriber (+4.7% since last report) * Chinese YouTube channel (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.43k subscribers (+2.3%) * (in China) bilibili space (https://space.bilibili.com/209599371) w/ 26k subscriber (+4% since last report) * Highlights in MXNet ecosystem * Dive into Deep Learning has 50K 28-day active users, and has attracted 28.0K stars & 333 contributors on GitHub. It has been adopted as a textbook or reference book by 170+ universities from 40 countries, such as Stanford, MIT, UC Berkeley, CMU, UCambridge. * GluonCV v0.9.0 release (https://github.com/dmlc/gluon-cv/releases/tag/v0.9.0) * GluonNLP MX2 NumPy version (https://github.com/dmlc/gluon-nlp/tree/master) * GluonTS v0.6.4 release (https://github.com/awslabs/gluon-ts/releases/tag/v0.6.4) * DeepInsight (https://github.com/deepinsight/insightface) * Sockeye 2.3.2 release (https://github.com/awslabs/sockeye) * MXNet community held the "Apache MXNet Day" community meet-up on 12/14 with NVIDIA and AWS as sponsors and Apache as community sponsor. At the meet-up, community members shared the latest progress in MXNet, and discussed topics such as array API standardization across frameworks, and the history and future of MXNet. ### How has the project developed since the last report? 1) 1.8.0 release is in progress: https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc2 with 100+ patches of new features, improvements, and fixes. 2) 2.0 alpha release: https://github.com/apache/incubator-mxnet/projects/18 3) Github statistics of last month: * Dec 5, 2020 – Jan 5, 2021: Excluding merges, 28 authors have pushed 31 commits to master and 60 commits to all branches. On master, 175 files have changed and there have been 7,192 additions and 1,628 deletions. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-08-24 ### When were the last committers or PPMC members elected? 2020-11-30 ### Have your mentors been helpful and responsive? Yes. Michael stepped down as a mentor and we are grateful for his helps for our project. Markus also expressed desire to step down as a mentor if we find more mentors. Because of the large scope of the project and the several issues we faced so far, we definitely wish to have more mentors to help. ### Is the PPMC managing the podling's brand / trademarks? Yes. The PPMC conducted more extensive branding and trademarks review, identified some violations and acted on resolving them with offenders, as described in "Status on license and branding issues" section. In addition, The community is including brand usage reviews as part of the quarterly report process to proactively manage our brand going forward. ### Signed-off-by: - [ ] (mxnet) Markus Weimer Comments: - [ ] (mxnet) Bob Paulin Comments: - [ ] (mxnet) Jason Dai Comments: - [X] (mxnet) Furkan Kamaci Comments: ### IPMC/Shepherd notes: -------------------- ## NuttX NuttX is a mature, real-time embedded operating system (RTOS). NuttX has been incubating since 2019-12-09. ### Three most important unfinished issues to address before graduating: 1. Clear any potential infringing use of the NuttX trademark 2. Make more releases under Apache 3. Continue to grow the community with people from different background ### 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? * Most communications have moved from old venues to dev@nuttx.apache.org. The dev list contains 210 subscribers, an increase of 6% since our previous report, and is the home of all 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. * One new committer has been added since the last report. ### How has the project developed since the last report? * We have made significant steps toward license clearing, needed for graduation: In this quarter, we have secured 34 ICLAs and 7 SGAs, the most of any quarter so far, from past and present contributors. * We have successfully made our third, fourth, and fifth releases under the ASF umbrella: NuttX-10.0 followed by security fix releases NuttX-9.1.1 and NuttX-10.0.1. * Contributions are flowing regularly as PRs in GitHub with occasional patches in the dev list. * Many technical improvements, bug fixes, and new architectures have been collaborated and work continues with an average of 6 and sometimes as many as a dozen pull requests merged per day. * We have listened to the valuable feedback received during our previous releases and continue to improve our documentation. This can be found at https://nuttx.apache.org/docs/latest/. * We've implemented additional automatic checks on PRs. This has helped us to improve our review process. ### 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: NuttX-10.0.1 and NuttX-9.1.1 were released on 2020-12-08. ### When were the last committers or PPMC members elected? Last elected PPMC: 2020-01-10 Last committer added: 2020-12-30 ### Have your mentors been helpful and responsive? Mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Podling name was approved on May 17th 2020: https://s.apache.org/4hfzx ### Signed-off-by: - [X] (nuttx) Duo Zhang Comments: Glad to see that we have made good progress on license clearing. - [ ] (nuttx) Junping Du Comments: - [X] (nuttx) Justin Mclean Comments: - [ ] (nuttx) Mohammad Asif Siddiqui Comments: - [ ] (nuttx) Flavio Paiva Junqueira 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. Attract more contributors and committers. 2. Make more releases in ASF policy regularly. 3. Resolve the license problems. ### 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? We have recently attracted a new contributor empiredan, who have merged 2 PRs until now. ### How has the project developed since the last report? We are still actively working towards the next big release, which may be called 2.2.0. We have open-sourced 3 subprojects that were temporarily maintained outside the Apache orgnization: - https://github.com/pegasus-kv/admin-cli - https://github.com/pegasus-kv/pegic - https://github.com/pegasus-kv/meta-proxy Those are tiny tools but also considered as very important complement to the Pegasus ecosystem. `pegic` and `meta-proxy` are still in the initial stage. Developing under the "pegasus-kv" orgnization gets us full control of the Github settings so that we can move faster. `admin-cli` is nearly completed and license-cleared and will soon be migrated to Apache. The three projects will all eventually be moved to Apache. ### 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: 2020-11-30 ### When were the last committers or PPMC members elected? N/A ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (pegasus) Kevin A. McGrail Comments: Short report but accurate. - [X] (pegasus) Duo zhang Comments: - [X] (pegasus) Liang Chen Comments: - [X] (pegasus) Von Gosling Comments: ### IPMC/Shepherd notes: Justin Mclean: I like to see some explanation on why the sub-projects are being maintained outside of the project. There are branding and trademark issues and it may be best to consider moving them in-house. Also please list 3 unfinished issues that you still need to do to graduate. Justin Mclean: Thanks for the explanation, if might be better if you you worked with Infra on the GitHub settings, developing code outside the ASF is likely to cause a number of issues in the future when the code is moved. -------------------- ## Teaclave Teaclave is a universal secure computing platform. Teaclave has been incubating since 2019-08-20. ### Three most important unfinished issues to address before graduating: 1. Improve project structure and documentation 2. Grow the community (attracting more committers, contributors, users) 3. Publish more Apache releases ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? - We received contributions from a new external contributor. - We found a new project using Teaclave SGX SDK called Veracruz, which is a framework for defining and deploying collaborative, privacy-preserving computations amongst a group of mutually mistrusting individuals. - We summarized the community and projects powered by Teaclave and published a blog on our homepage. - Rust TrustZone SDK will be accepted in Teaclave as a subproject. The community is discussing and voting the acceptance. - The community has accepted a new committer. ### How has the project developed since the last report? - Add PCA function in the builtin executor. - Add exposed password checking function in the builtin executor. - Add the attestation subcommand to display attestation reports form the Intel attestation service. - Add document to support deploying on Azure confidential computing VM. ### 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: 2020-10-09 (version 0.1.0) ### When were the last committers or PPMC members elected? 2020-10-22 (Ran Duan, commiter, rduan@apache) ### Have your mentors been helpful and responsive? Yes, our mentors are very helpful and responsive on our discussion about security reporting and new projects acceptance voting. ### 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: - [x] (teaclave) Felix Cheung Comments: - [X] (teaclave) Furkan Kamaci Comments: - [ ] (teaclave) Jianyong Dai Comments: - [ ] (teaclave) Matt Sicker Comments: - [ ] (teaclave) Zhijie Shen Comments: ### IPMC/Shepherd notes: -------------------- ## TubeMQ TubeMQ is a distributed messaging queue (MQ) system. TubeMQ has been incubating since 2019-11-03. ### Three most important unfinished issues to address before graduating: 1.Adjust project goal && project name 2.Keep growing the community, attract more contributors and committers 3.Release Apache standard releases regularly ### Are there any issues that the IPMC or ASF Board need to be aware of? We hope more IPMCs will pay attention to our project and give more suggestions. ### How has the community developed since the last report? Since the last report, the TubeMQ community has continued to improve its functions as well as external publicity and communication; at the same time, we PPMCs conducted a discussion on adjusting project objectives and project names. We hope to provide a complete one-stop streaming data service platform: the system integrates a series of components in the form of plug-ins for collection, aggregation, storage and forwarding to build a complete data reporting service; based on this platform, users only need to publish and subscribe to data, and they can easily build analysis and applications based on streaming data; and TubeMQ will continue to develop in this project. ### How has the project developed since the last report? At this stage, we released the SDK of the Python language and the tubemq-manager module for cluster management. The tubemq-manager module is used for cross-cluster control to make the project more usable; we have also made a number of improvements in the function of the project, for details information, please refer to our project issues: https://issues.apache.org/jira/projects/TUBEMQ/issues. ### 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: 2020-12-04 ### When were the last committers or PPMC members elected? 1. yuanboliu was added as committer on 2020-12-10 2. dockerzhang was added as PPMC on 2020-12-15 ### Have your mentors been helpful and responsive? In the recent period, the mentors have given us a lot of help and guidance; We hope that the mentors can continue to pay attention to the development of our project and continue to provide more help and suggestions to the project. ### Is the PPMC managing the podling's brand / trademarks? Yes, all good here. ### Signed-off-by: - [ ] (tubemq) Junping Du Comments: - [X] (tubemq) Justin Mclean Comments: Don't forget you can reach out to your mentors if you need help. Keeping discussions on the mailing list also helps. - [ ] (tubemq) Sijie Guo Comments: - [ ] (tubemq) Zhijie Shen Comments: - [X] (tubemq) Jean-Baptiste Onofre Comments: ### IPMC/Shepherd notes: -------------------- ## Wayang Wayang is a cross-platform data processing system that aims at decoupling the business logic of data analytics applications from concrete data processing platforms, such as Apache Flink or Apache Spark. Hence, it tames the complexity that arises from the "Cambrian explosion" of novel data processing platforms that we currently witness. Wayang has been incubating since 2020-12-16. ### Three most important unfinished issues to address: 1. Finishing the Software Grant paperwork 2. Onboarding of the existing team at Apache 3. Getting Wayang setup on Apache infrastructure ### Are there any issues that the IPMC or ASF Board need to be aware of? There are no issues present at the moment ### How has the community developed since the last report? We are in the onboarding process, but got new developer requests which we process when the project is fully onboarded ### How has the project developed since the last report? We are in process to sort the software grant, getting the team on board and started code rebranding to fit the ASF regulatory framework ### 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 yet ### Have your mentors been helpful and responsive? Yes, the mentors are very responsive and helpful ### Is the PPMC managing the podling's brand / trademarks? We are managing the brand, to avoid conflict we renamed rheem into Wayang, the process is still ongoing ### Signed-off-by: - [X] (wayang) Christofer Dutz Comments: Seems getting the paperwork done takes a bit longer for universities and institues than for "normal" companies, but I'm hopeful that we'll sort out the remaining issues till the next report. - [X] (wayang) Lars George Comments: - [X] (wayang) Bernd Fondermann Comments: cdutz signed off the report as Bernd had problems logging in (signoff on file in dev-list mail archive) - [X] (wayang) Jean-Baptiste Onofré Comments: Initial phase, but it moves forward anyway. ### IPMC/Shepherd notes: -------------------- ## YuniKorn YuniKorn is a standalone resource scheduler responsible for scheduling batch jobs and long-running services on large scale distributed systems running in on-premises environments as well as different public clouds. YuniKorn has been incubating since 2020-01-21. ### Three most important unfinished issues to address before graduating: 1. Gain more contributors and active committers. 2. Establish a release cadence based on roadmap. 3. Improve the ease of deployment and documentation quality. ### Are there any issues that the IPMC or ASF Board need to be aware of? No issues at this point in time. ### How has the community developed since the last report? New committer vote is in progress (delayed due to Christmas break). Two new large features started. Driven by different parts of the community: gang scheduling and open tracing. New release planned for the end of January 2021 and the search for a new release manager has started. ### How has the project developed since the last report? Major scheduler core code update rewrite committed. Upgrades to build tools to the latest supported tool versions. Testing matrix updated to support latest versions of Kubernetes. Some statistics for the report period (2020-10-01 till 2021-12-31) JIRA: 67 created, 56 resolved PRs: 55 opened, 58 resolved 10 unique active code contributors (cumulative for all repos) ### 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: 2020-08-26 ### When were the last committers or PPMC members elected? New committer vote is in progress (delayed due to Christmas break). ### Have your mentors been helpful and responsive? Yes, review of PRs and part of the community syncs ### Is the PPMC managing the podling's brand / trademarks? No issues that we are aware of. ### Signed-off-by: - [ ] (yunikorn) Junping Du Comments: - [x] (yunikorn) Felix Cheung Comments: - [X] (yunikorn) Jason Lowe Comments: - [X] (yunikorn) Holden Karau Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AF: 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 (8 years ago). There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jörg Rade on 2020-04-12. - No new committers. Last addition was Jörg Rade on 2020-03-23. ## Project Activity: There continues to be substantial development work on v2.0, with the framework being "re-platformed" to run on top of Spring Boot. The main focus during the last quarter has been the persistence layer, with the aim of supporting both JDO and also JPA. This is still ongoing, and has allowed the existing JDO implementation to be massively simplified. There has also been work to automatically generate docs from sources [1], and the demo/tutorial app continues to be extended, now available online [2]. The last release was 2.0.0-M4 on Oct 17 2020. We hope to finally release v2.0 in Q1 this year. ## Community Health: This is a mature project. The framework is generally stable. While there is little activity on the mailing lists, there is general activity on the Slack channel. ## References [1] https://apache-isis-committers.github.io/isis-nightly/system/latest/generated/system-overview.html [2] https://demo-wicket.isis.incode.work/ ----------------------------------------- Attachment AG: 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 (18 years ago) There are currently 39 committers and 16 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 Antoine Duprat on 2016-03-11. - No new committers. Last addition was David Leangen on 2020-07-06. ## Project Activity: The project saw interests on the JMAP protocol, raising discussions on project mailing list and start being used. JMAP protocol had been used with a tier app (LTT.RS) proving interoperability. Development efforts are now oriented toward JMAP PUSH specifications, enabling efficient mail client re-synchronization. The project saw active contributions around setting up an Apache CI, as well as bug-fixes and build stability improvements related to it. ## Community Health: Linked to the build improvement activities, the number of pull requests had significantly increased: - 32 PRs opened on GitHub, past quarter (77% increase) - 27 PRs closed on GitHub, past quarter (12% increase) ----------------------------------------- Attachment AH: Report from the Apache jclouds Project [Ignasi Barrera] A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have upgraded our Guava and Guice dependencies, addressing several user issues. However, these changes introduced some incompatibilities in OSGi environments, and we're looking at addressing those and relaxing the constraints on the core dependencies of the project to minimize the impact on the jclouds ecosystem. We are looking forward to releasing 2.3.0 once the fixes are in place. == Community == There have been contributions from people in the community, especially around our OSGi integration. This is an ongoing effort mainly driven by a fairly new contributor that is being really helpful and unblocked several issues that prevented jclouds from upgrading to newer Java versions. Apart from this, the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Release 2.3.0 in Q1 2021. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.2.1, took place on 2020-05-14. ----------------------------------------- Attachment AI: 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 (9 years ago) There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. - No new committers. Last addition was Greg Albiston on 2019-07-08. ## Project Activity: Jena release version 3.17.0 in December. This incorporated many dependency updates promoted by enabling the github dependency bot on the project codebase. Jena usually does a release every 3-4 months. This release was at just over the 4 month mark from the previous release. The project is engaged in moving from a Java8 to Java11 as a prerequisite. We see some dependencies and potential interesting dependencies requiring Java11. ## Community Health: The project channels remain at normal level; there was a burst of process email connected with the upgrade of dependencies. Last report activity level were down, which as noted, coincided with northern hemisphere summer. ----------------------------------------- Attachment AJ: Report from the Apache JMeter Project [Bruno Demion] ## Description: The mission of JMeter is the creation and maintenance of software related to Java performance and functional testing ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache JMeter was founded 2011-10-26 (9 years ago) There are currently 13 committers and 8 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Vladimir Sitnikov on 2018-06-08. - No new committers. Last addition was Maxime Chassagneux on 2017-02-15. ## Project Activity: - The project working to release the next (minor) version (5.4.1). The vote is in progress. ## Community Health: - The project has a normal activity during last quarter. ## Project Release Activity: Recent releases: 5.4 final was released on 2020-12-03. ----------------------------------------- Attachment AK: Report from the Apache Johnzon Project [Romain Manni-Bucau] ## 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: We need to maybe find more contributors but since the project is crazy stable and implements a specification it is not that trivial by nature. ## Membership Data: Apache Johnzon was founded 2016-04-20 (5 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: Project got some maintenance related to TomEE TCK work but also some new features (JSON logic related). Recent releases: - 1.2.8 was released on 2020-07-06. - 1.2.7 was released on 2020-06-04. - 1.2.6 was released on 2020-05-13. Project is also working to get Johnzon to be listed as a compatible implementation for JSON-B and JSON-P on the Jakarta EE Website. ## Community Health: Due to the activity we got some more jira and mail exchanges than usual. The exchanges about the related topics were positively moving forward but still between the same prople (likely due to the same issue mentionned in "issues" part). ----------------------------------------- Attachment AL: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AM: 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 (7 years ago) There are currently 14 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 7:5. Community changes, past quarter: - No new PMC members. Last addition was Dave Koelmeyer on 2016-04-06. Murray Altheim requested (Jan 5, 2021) to step down as PMC member due to being inactive for a long time. - No new committers. Last addition was Dave Koelmeyer on 2016-04-06. Murray Altheim requested (Jan 5, 2021) to step down as committer due to being inactive for a long time. ## Project Activity: 2.11.0.M8 was released on 2020-12-13, which featured fixes for problems on Searches and Workflows' persistence on disk, introduced on 2.11.0.M7. This release also contained features provided by community members: completed translations for french and german, and another patch reworking a previous fix in one of the plugins bundled with JSPWiki. After 2.11.0.M8, activity has been focused on attending several PRs created by the dependabot (dependabot configuration was provided by another contributor). We also got a contribution regarding the official documentation, where the Docker page got a big rework. 2.11.0 should be the next planned release. ## Community Health: There's enough project oversight, although project activity is low. We are looking for some continuity on previously noted contributors, as they may end up becoming potential PMC members / committers. ----------------------------------------- Attachment AN: Report from the Apache Kudu Project [Adar Dembo] ## 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 (4 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: Recent releases: - Discussions have started regarding a 1.14.0 release. The release management process is expected to commence in the coming week or two. - 1.13.0 was released on 2020-09-17. - 1.12.0 was released on 2020-05-11. - 1.10.1 was released on 2019-11-20. - 1.11.1 was released on 2019-11-20. ## Community Health: - Traffic to the dev and user mailing lists decreased significantly (-84% and -53% respectively), with more questions popping up on the community Slack. - Public IM activity over the community Slack channel is up, with the average daily and weekly active members remaining steady (under 3% difference for each), but average daily number of posts in public channels having increased +60%. - Website traffic decreased slightly, with around -7% measured number of users and sessions in the last 90 days, according to Google Analytics. - Development activity measured in the number of commits is down (-16%). Contributions were authored by 11 unique contributors (-15%), one of which was a first-time contributor to the project. - Development activity measured by opened and closed issues has decreased (-20% opened tickets, -71% closed tickets), partially due to the coarse granularity of tasks being worked on. ----------------------------------------- Attachment AO: Report from the Apache MADlib Project [Aaron Feng] ## Description: - Apache MADlib is a scalable, big data, SQL-driven machine learning framework for data scientists. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Release 1.17.0 occurred on Apr 9, 2020 which was the 7th release as an Apache TLP project. - Community is working on the 1.18.0 release with JIRAs related to deep learning and other ML methods: * deep learning - improve GPU efficiency * deep learning - support custom loss functions and custom metrics * deep learning - add autoML methods Hyperband and Hyperopt * DBSCAN clustering algorithm - Recent blog post mentioning Apache MADlib: https://tanzu.vmware.com/content/blog/analytic-workloads-bi-ai-vmware-tanzu-greenplum ## Health report: The community is relatively small but very engaged with robust mailing list traffic, interest in doing frequent releases and new functionality being developed by contributors. The number of developers actively contributing to the code/documentation is approximately 5 in the 4th quarter of calendar year 2021. We will constantly be on a lookout for new community members to be invited either as committers or PMC. ## PMC changes: - No changes in the last quarter. Currently stands at 14 PMC members. ## Committer base changes: - Currently 17 committers, no new committers since last report. - The most recent committers added were: Ekta Khanna (2019-07-27) Himanshu Pandey (2019-07-27) Domino Valdano (2019-07-27) ## Releases: - Next release: v1.18.0 planned for 1H 2021 - v1.17.0 released on 2020-04-09 - v1.16.0 released on 2019-07-08 - v1.15.1 released on 2018-10-15 ## Mailing list activity: Mailing list activity was 32 posts to dev@ and 2 posts to user@ for the last 3 months Oct-Dec 2020. ## JIRA Statistics: - 8 JIRA tickets created in the 3 months - 5 JIRA tickets resolved in the 3 months ----------------------------------------- Attachment AP: Report from the Apache Mahout Project [Trevor Grant] ## Description: The mission of Mahout is the creation and maintenance of software related to Scalable machine learning library ## Issues: Nothing requiring board attention at this time. ## Membership Data: Apache Mahout was founded 2010-04-20 (11 years ago) There are currently 28 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Trevor Grant on 2017-02-03. - No new committers. Last addition was Christofer Dutz on 2020-06-08. ## Project Activity: Since last board report Trevor Grant has taken over as PMC Chair and initiated weekly status call meetings, with minutes posted to mahout.apache.org and posted back to the mailing list. Also- the community has taken up an initiative to begin releasing Python bindings, and hope to include this in the next release. ## Community Health: We are MUCH healthier than we have been for some time, due alone to our ability to execute builds. This isn't really reflected in the statistics, but is a huge boon for the project. Secondly, after Trevor Grant took over as project chair and began hosting weekly meetings this has negatively impacted mailing list activity as often interested parties will discuss their plans and get feedback on a weekly call whose minutes are reported back- however the entire thread is not archived on the list (decreased mailing list chatter). We are starting to see more action in meaningful PRs and large initiatives, such as Python bindings, Zeppelin+Mahout Getting Started Docker containers, and others are of course still discussed on the list as well as at community meetings. An interesting bit- is that the opened and closed JIRA tickets are greater than open and closed PRs. This is due to some JIRA pruning and deleting old spammy JIRA tickets (from over the prior quarter- one of the first topics of the weekly community call meetings). Issues mailing list was also up due to this. We have resumed a focus on the hunt to bring in fresh committers to our community and have promising leads from ApacheCon and other sources. We have also as a project begun to re-envsion ourselves from just anotherML lib to distributed statistics, a niche exploitation strategy that we hope will help us attract more interest. In this vein- Apache Mahout was used in an example in a new O'Reilly book and we hope that will also help us with this rebranding (using DS-SVD to decompose COVID lung scans). Finally, after a big push to release, and with holidays and other life events of some of the main committers, we all just took a breather. And still the project has healthy statistics. We look forward to some great progression in 2021. - dev@mahout.apache.org had a 48% decrease in traffic in the past quarter (64 emails compared to 123) - issues@mahout.apache.org had a 76% increase in traffic in the past quarter (92 emails compared to 52) - user@mahout.apache.org had a 70% decrease in traffic in the past quarter (4 emails compared to 13) - 8 issues opened in JIRA, past quarter (-50% decrease) - 9 issues closed in JIRA, past quarter (125% increase) - 15 commits in the past quarter (-63% decrease) - 3 code contributors in the past quarter (-40% decrease) - 5 PRs opened on GitHub, past quarter (-16% decrease) - 6 PRs closed on GitHub, past quarter (100% increase) ----------------------------------------- Attachment AQ: Report from the Apache Maven Project [Robert Scholte] ## Description: The mission of Maven is the creation and maintenance of software related to Java project management and comprehension tools ## Issues: Unsure if this is only related to Covid19, but in general most PMC members don't show involvement on the project. We were already seeing that the 3 required +1 PMC votes for releases were done by alomost the same group of people. We clearly see a decrease of motivation here. ## Membership Data: Apache Maven was founded 2003-03-01 (18 years ago) There are currently 63 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Mark Struberg on 2019-12-27. - Benjamin Marwell was added as committer on 2020-12-05 ## Project Activity: Last Maven Release: 3.6.3 (2019-11-25) Plugins (ordered by date) Maven JLink Plugin 3.0.0 was released on 2020-11-23. Maven PMD Plugin 3.14.0 was released on 2020-11-24. Maven SCM Publish Plugin 3.1.0 was released on 2020-12-26. Maven JLink Plugin 3.1.0 was released on 2020-12-27. Maven EAR Plugin 3.2.0 was released on 2021-01-03. Other (ordered by date) Maven Script Interpreter 1.3 was released on 2020-11-14. Maven Resolver Ant Tasks 1.3.0 was released on 2020-11-21. Maven Wagon 3.4.2 was released on 2020-11-25. Maven Artifact Transfer 0.13.1 was released on 2020-12-22. ## Community Health: DevNexus has approach the Maven Project to become a OSSRRRJAM 2021 Partner (free of charge). We've accepted it. Under normal circumstances, the next release of Maven will be 4.0.0-alpha-1. We've added a lot of new features that justify a 4 release. Due to changes in the architecture we need a lot of alpha testers to verify this release. ----------------------------------------- Attachment AR: Report from the Apache Mesos Project [Vinod Kone] ## Description: The mission of Mesos is the creation and maintenance of software related to a cluster manager that provides efficient resource isolation and sharing across distributed applications ## Issues: D2iQ (formerly Mesosphere) has decided to EOL their DC/OS product (based on Apache Mesos) https://d2iq.com/blog/d2iq-takes-the-next-step-forward. Given D2iQ employs almost all of the active committers to the Apache Mesos project, this will likely have a big impact. ## Membership Data: Apache Mesos was founded 2013-06-18 (8 years ago) There are currently 49 committers and 49 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Andrei Sekretenko on 2020-01-20. - No new committers. Last addition was Andrei Sekretenko on 2020-01-21. ## Project Activity: 1.11.0 was released on 2020-11-24. No further releases are planned at this point given the situation described in the Issues section. ## Community Health: We anticipate development activity to significantly reduce over the coming months. See the Issues section. ----------------------------------------- Attachment AS: Report from the Apache MINA Project [Guillaume Nodet] ## Description: The mission of MINA is the creation and maintenance of software related to Multipurpose Infrastructure for Network Application. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache MINA was founded 2006-10-25 (14 years ago) There are currently 28 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Jonathan Valliere on 2018-08-27. - No new committers. Last addition was Thomas Wolf on 2020-09-23. ## Project Activity: - Apache MINA SSHD 2.6.0 was released on 2021-01-04. - Apache MINA 2.1.4 was released on 2020-08-24. - Apache Mina SSHD 2.5.1 was released on 2020-07-01. ## Community Health: No real changes: both Mina SSHD and Mina Core subprojects have a few active committers while the FtpServer and Vysper subprojects have almost no activity. ----------------------------------------- Attachment AT: Report from the Apache Mnemonic Project [Gordon King] Description: Apache Mnemonic is an open-source Java library for durable object-oriented programming on hybrid storage-class memory(e.g. NVM) space. It comes up with durable object model (DOM) and durable computing model(DCM) and takes full advantages of storage-class memory to simplify the code complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing next generation computing platforms. Mnemonic makes the storing and transmitting of massive linked objects graphs simpler and more efficient. The performance tuning could also be mostly converged to a single point of tuning place if based on Mnemonic to process and analyze linked objects. The programmer is able to focus on the durable object oriented business logic instead of worrying about how to normalize/join, SerDe(un)marshal, cache and store their linked business objects with arbitrary complexity. Issues: Activity: In this period of reporting (since Dec. 06, 2020) , 31 of tickets have been created and 29 resolved, basically, we were working on migrating Maven build to Gradle for efficiency and flexibility. A new version has been released. Our community has held several regular meetings every 2 weeks, the agenda mainly covered the following topics - Gradle migration - Preparing new release - Releasing workflow - Issues evaluation - New features and improvement Health Report: Our community and PMCs are working together on Gradle migration and released a new version of Mnemonic, we are closely tracking the progress of project and community activities. New PMCs and contributors are actively contributing and participating in the project. The release plan got closely tracked and fulfilled, Yanhui and other PMCs contributed lot of efforts on community growth and project development. PMC Changes: - Currently 14 PMC members. - 3 PMC joined in Oct. 2020. Committer Base Changes: - Currently 19 committers (corrected according to whimsy). - 3 same committers joined in Oct. 2020. Releases: - Last release was v0.13.0 on Jan. 11 2020 - Active development on next major version (0.14) ----------------------------------------- Attachment AU: Report from the Apache MyFaces Project [Bernd Bohmann] ## Description: The mission of MyFaces is the creation and maintenance of software related to JavaServer(tm) Faces implementation and components ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache MyFaces was founded 2005-02-23 (16 years ago) There are currently 79 committers and 44 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 Eduardo Breijo-Baullosa on 2018-01-30. - No new committers. Last addition was Volodymyr Siedlecki on 2020-05-18. ## Project Activity: - Apache MyFaces Core the community is working on a 3.0 release. There is a vulnerability report about predicting the viewState token. The generation of this token is configurable and we are discussing to change the default from random to secureRandom. - Apache Tobago the community is working on release 5.0.0 and 2.x. - Recent releases: myfaces-core-2.3.7 was released on 2020-11-09. tobago-4.5.1 was released on 2020-11-03. myfaces-core-2.3-next-M4 was released on 2020-09-04. ## Community Health: - Apache MyFaces Core is healthy. UI-Component Sets: - Apache Tobago is healthy. - Apache Trinidad is in maintenance mode. Last developer commit was Sept 2017. - Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016. Last commit on behalf of a contributor was May 2016. Add-ons and Extensions: - Apache MyFaces Portlet Bridge is in maintenance mode. Last developer commit was Jan 2014. Last commit on behalf of a contributor was May 2015. - Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache DeltaSpike so new development happens there. Last commit March 2014. - Apache MyFaces Orchestra is in maintenance mode. New projects use CDI and DeltaSpike instead. Last commit on behalf of a contributor was August 2016. - Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014. - Apache MyFaces Commons is in maintenance mode. Last commit August 2012. - Apache MyFaces Ext-Scripting is in maintenance mode. Last commit Sept 2017. - Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last commit May 2017. ----------------------------------------- Attachment AV: Report from the Apache NiFi Project [Joe Witt] ## Description: The mission of NiFi is the creation and maintenance of software related to providing an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi MiNiFi is an edge data collection agent built to seamlessly integrate with and leverage the command and control of NiFi. There are both Java and C++ implementations. Apache NiFi Registry is a centralized registry for key configuration items including flow versions, assets, and extensions for Apache NiFi and Apache MiNiFi. Apache NiFi Nar Maven Plugin is a release artifact used for supporting the NiFi classloader isolation model. Apache NiFi Flow Design System is a theme-able set of high quality UI components and utilities for use across the various Apache NiFi web applications in order to provide a more consistent user experience. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache NiFi was founded 2015-07-14 (5 years ago) There are currently 48 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Arpad Boda on 2020-05-24. - Marton Szasz was added as a committer on 2020-07-13 The PMC is discussion committer and PMC candidates right now. Three candidates are likely to be voted upon within the coming days and the pipeline remains strong. ## Project Activity: The last release of Apache NiFi was 1.12.1 on Sep 29, 2020. We're now in the release candidate creation phase of Apache NiFI 1.13.0 which is a full feature bearing release including over 200 JIRAs. With respect to Apache NiFi MiNiFi Java the work is still progressing for https://issues.apache.org/jira/browse/MINIFI-422 which will merge MiNiFi Java back into NiFi as a headless form of NiFi supporting both broad use case patterns well and reduce the release/codebase burden. Apache NiFi MiNiFi CPP 0.8.0 is still in progress with over 180 JIRAs with the 0.9.0 release already begun as well including nearly 20 JIRAs and an initial framing of a 1.0 (major) release in progress as well. ## Community Health: We observed a decline in mailing list activity as well as JIRAs and commits this quarter but this is largely due to what appeared to be a solid couple of weeks of limited engagement likely due to the holidays. However, there are many vibrant and engaging threads related to release activities or feature work and contribution reviews so health remains quite strong. The Apache NiFi slack channel activity continues its impressive growth in viewership and engagement growing another 200 users in the past quarter which seems to be consistent. It does seem like a lot of mailing list activities have moved there but we still encourage people to take anything lasting or for which they dont get prompt responses back to the mailing list. Activity on twitter, stackoverflow, youtube, blogs remains interesting and much of it happens by people not engaged in the Apache NiFi community at all. Stale PRs remains an area of concern as we've noted in previous reports though we are still not specifically addressing that problem. We've done some research into how other communities handle it (or dont) but do not yet have a specific plan. ----------------------------------------- Attachment AW: Report from the Apache Nutch Project [Sebastian Nagel] ## Description: Apache Nutch is a highly extensible and scalable open source web crawler software project based on Apache Hadoop® data structures and the MapReduce data processing framework. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Nutch was founded 2010-04-21 (11 years ago) There are currently 21 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 1:1. The last committer and PMC addition was Shashanka Balakuntala Srinivasa on 2020-08-01. ## Project Activity: Work on Nutch 1.18 continues with 13 JIRA issues opened and 12 resolved since the last report. The migration away from the Apache CMS has not made any progress during the last 3 months. We started to work to run Nutch on Apache Tez alternatively to MapReduce resp. Hadoop YARN. ## Community Health: Traffic on mailing lists and development activity are on a low but steady level. ----------------------------------------- Attachment AX: Report from the Apache OpenJPA Project [Mark Struberg] ## Description: Apache OpenJPA is a persistent object management kernel for databases, relational as well as non-relational. For relational databases, OpenJPA is compliant to the Java Persistence Architecture (JPA) version 2.2. OpenJPA runs in stand-alone Java SE as well as containers e.g Java EE, Tomcat, Spring or OSGi. ## Issues: There are no issues requiring board attention at this time ## Activity: The last quarter has been rather silent. We are preparing to release a version which works with the upcoming Java16 and fixed a few bugs. ## Health report: People are still around if needed, code is very functional and stable. ## PMC changes: - No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13. - No new committers. Last addition was Matt Pavlovich on 2019-05-22. ## Releases: - 3.1.2 was released on 2020-07-14. - 3.1.1 was released on 2020-02-14. - 3.1.0 was released on 2019-04-14. ## Activity stats: - 110 emails on dev - 13 tickets opened, 8 closed ----------------------------------------- Attachment AY: 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 (8 years ago) There are currently 29 committers and 27 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 Stefan Kühl on 2019-09-10. - No new committers. Last addition was Stefan Kühl on 2019-09-10. ## Project Activity: We were able to release version 5.1.0, now are working at 6.0.0. Hopefully next release will happen in a month or so ## Community Health: Mail lists activity is more or less the same (small decrease is caused by winter holidays). User questions are being answered :) ----------------------------------------- Attachment AZ: Report from the Apache OpenOffice Project [Carl B. Marcum] ## DESCRIPTION Apache OpenOffice is an open-source office-document productivity suite. There are six productivity applications based around the OpenDocument Format (ODF) that are Writer, Calc, Impress, Draw, Math, Base. With limited support for other file formats, OpenOffice ships for Windows, macOS, Linux 64-bit, Linux 32-bit and in 41 languages. ### History 2012-10-17 - Apache OpenOffice was established as Top Level Project (TLP) 2011-06-13 - OpenOffice.org was accepted as Incubator project in the ASF with the new name Apache OpenOffice ## SUMMARY Latest Release (4.1.8) was in November 2020. The community activity in general is on a low but sustainable level. A major obstacle is the complex code and build system. Therefore it is not easy for new people to gain a foothold into the code when the first build is hard to be done. There is recent activity to update the building guides to make it easier to get builds working. ## ISSUES FOR BOARD AWARENESS No issues ## RELEASES We are working in parallel on 2 release lines: 1) 4.2.0 is the next minor release, planned to be released into a beta phase. We have missed our goal on going into the beta in 2019. We managed only to solve the biggest blockers. Currently a new dev test version is released to be more widely tested. An alpha and/or beta release is planned for the next quarter. For that release we are improving the translation process. We are now able to sync our translation server Pootle with the code. Together with ASF Infra we were able to set up a new (updated) translate VM. At the moment we support 65 languages in Pootle. We plan to add some new languages to the 4.2.0 release. 2) Due to a problem with the recently published macOS version 11 (Big Sur) it is necessary to fix a bug (cannot open any Microsoft Office .docx, .xlsx, .pptx document) and therefore to release a new version 4.1.9. This is planned to be in January. The motivation in still maintaining the 4.1.x release line is not very high. Therefore we will shut it down as soon as we have a stable release of 4.2.x. ## LATEST RELEASE HISTORY 2020-11-10 4.1.8 2019-09-21 4.1.7 2018-11-18 4.1.6 ## COMMITTER & PMC DATA There are currently 143 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 5:1. Community changes, past quarter: - No new PMC members Last PMC member addition was on 2017-Dec-20 Keith N. McKenna (knmc). Last PMC member withdrawal was on 2019-Sep-24 Roberto Galoppini (galoppini). - 1 new committer has been accepted, we welcome Arrigo Marchiori (ardovm) Last committer addition was on 2020-12-24 Arrigo Marchiori (ardovm). Last committer withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid). ## COMMUNITY HEALTH AND DEVELOPMENT Community overall health is improving. With Arrigo Marchiori a new developer on the code has been accepted by the community. With the finished migration we see first steps on website and documentation updates. The community looks forward into 2021 with a positive spirit. ### FOSDEM 2021 Conference The conference is online this year and talks are pre-recorded. OpenOffice has a developer room and we have had some talks accepted and volunteers are preparing them. The scheduled conference dates are February 6th and 7th. ## WEBSITES & INFRASTRUCTURE We have completed the migration from the old Apache CMS to a Jbake site for "www.openoffice.org". The repository is now in GitBox and GitHub. Jenkins is used. The Infrastructure team has been very helpful. We have converted the "openoffice.apache.org" site to use .asf.yaml and Pelican. Our Windows and Linux build bots are functional again. Work still needs to be done on the RAT builds. We are working on a Mac build bot in order to enhance our changes. The machine is sponsored by MacStadium. We have been able to fix a problem with our MWiki wiki.oo.o due to a tag extension used to write URLs to our API documentation during the previous server migration. The issue resulted in hundreds of blank pages throughout the developer guides. Additional work has been done to update the skin as well. These customizations have been placed in Git repos now. We are now planning a new migration of this wiki to a new VM. ### Google Analytics Apache OpenOffice uses Google Analytics. We are aware this is a controversial topic within the ASF. Current setup is to collect as few data points as possible. We do not use Google Analytics for advertisement. Disclaimers are placed. We use the Data to evaluate the speed we can apply to renew the code and raise the minimal requirements of OpenOffice. The general controversy has reached the project. We are evaluating alternatives that will meet our requirements. A log file does not meet our requirements, since nobody can read statistics from a bare text file. ## MARKETING Due to corona all live action marketing has been currently postponed. We have reorganized the flyer activity. Currently we are preparing material for the next year. ### Facebook We have one Volunteer representing Apache OpenOffice on Facebook. The activity is irregular. Most engagement is helping users with issues. Articles reach about 2.2K People. ### Twitter Our Twitter account is maintained by one person. ## DEVELOPMENT ### Apple Code Signing We have done one signed test build and the AOO 4.1.8 macOS DMG images are also signed. However since Apple has changed the standards, users may still see a Gatekeeper warning (this is due to the AOO 4.1.x builds requiring an older SDK). Signing is done manually but via scripting and follows Apple's preferred process: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow ### Windows Code Signing We sign all Windows installer beginning with the 4.1.8 release. There is some discussion to switch from the current Installer to a MSI installer. But there are technical hurdles to be solved. Windows code signing is currently a manual process. ### Unmaintained Python 2 code Python 2 is unmaintained. We have in the development tree the external python3 support. Internal python 3 support is difficult. We are checking alternatives. Planned for the next major release. ### New ODF Version Our default file format, the Open Document Format, has received a new Standard update. We plan to support this format. ----------------------------------------- Attachment BA: Report from the Apache ORC Project [Owen O'Malley] ## 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-22 (6 years ago) There are currently 42 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:2. Community changes, past quarter: - No new PMC members. Last addition was Jesús Camacho Rodríguez on 2019-12-27. - Panagiotis Garefalakis was added as committer on 2020-11-16 ## Project Activity: Recent releases: - 1.6.6 was released on 2020-12-10. - 1.6.5 was released on 2020-10-01. - 1.5.12 was released on 2020-09-30. Most of 1.6.6 resolves backwards compatibility problems that blocked Spark from moving to 1.6. Blog post: - FastIngest: Low-latency Gobblin with Apache Iceberg and ORC format https://engineering.linkedin.com/blog/2021/fastingest-low-latency-gobblin? ## Community Health: Development has substantially picked up in the project with both increased email traffic and pull requests. - dev@orc.apache.org had a 40% increase in traffic in the past quarter (442 emails compared to 314) - issues@orc.apache.org had a 35% increase in traffic in the past quarter (196 emails compared to 145) - 61 PRs opened on GitHub, past quarter (90% increase) - 59 PRs closed on GitHub, past quarter (55% increase) ----------------------------------------- Attachment BB: Report from the Apache Ozone Project [Sammi Chen] ## Description Apache Ozone is a scalable, redundant, and distributed object and file store, designed to scale to billions of objects/files and run on clusters of thousands of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop Compatible File System implementation. ## Issues None. ## Membership Data - Apache Ozone was founded 2020-10-21. - There are currently 45 comitters and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 1.8:1. ## Project Activity: - Trash support feature development is moving fast. - FS Namesystem optimization is moving fast too. - SCM HA has finished Phase 1.5 and entered Phase 2.0 development, targeting for code ready by end of next month. - Community is also actively working on other features development and bug fix, such as S3 ACL, namespace Quota, security related issues, etc. - Community plans to release 1.1.0 in Q1 and already has a volunteer as Release Manager. ## Releases: - 1.0.0 was released on 2020-09-02. - 1.1.0 is planned, depending on Apache Ratis release. ## Community Health: Last board report sent one month ago. Due to the holiday season, some indicators have slightly dropped. In the past 4 weeks, - dev@ozone.apache.org had 35 new emails(Last report is 45). - issues@ozone.apache.org had 1378 new emails(Last report is 1619). - 99 issues resolved in JIRA (Last report is 91). - 92 issues opened in JIRA (Last report is 105). - There are 4 new contributors joined the community this month. And now we have a total of 97 contributors. ----------------------------------------- Attachment BC: Report from the Apache Parquet Project [Julien Le Dem] ## Description: Parquet is a standard and interoperable columnar file format for efficient analytics. Parquet has 3 sub-projects: - parquet-format: format reference doc along with thrift based metadata definition (used by both sub-projects bellow) - parquet-mr: java apis and implementation of the format along with integrations to various projects (thrift, pig, protobuf, avro, ...) - parquet-cpp: C++ apis and implementation of the format along with Python bindings and arrow integration. (Now as part of apache arrow) ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Parquet was founded 2015-04-21 (6 years ago) There are currently 36 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 9:7. Community changes, past quarter: - Xinli Shang was added to the PMC on 2020-11-09 - No new committers. Last addition was Antoine Pitrou on 2020-05-21. ## Project Activity: - bug fixes - improvements related to encryption feature - dependency maintenance updates ## Community Health: Regain of activity after the pandemic slow down, in particular on the mailing list and contributors on github. ----------------------------------------- Attachment BD: 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 issue requiring board attention at this time. ## Membership Data: Apache PDFBox was founded 2009-10-21 (11 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.22 was released on 2020-12-19. 2.0.21 was released on 2020-08-20. 2.0.20 was released on 2020-05-07. ## Community Health: - there is a steady stream of contributions, bug reports and questions on the mailing lists - there are a lot of refactorings, improvements and bugfixes - we started finalizing the next major release 3.0.0. We expect to prepare a first release candidate soon ----------------------------------------- Attachment BE: Report from the Apache Perl Project [Philippe Chiasson] ----------------------------------------- Attachment BF: Report from the Apache Petri Project [Dave Fisher] ## Description: The mission of Apache Petri is the creation and maintenance of software related to assessment of, education in, and adoption of the Foundation's policies and procedures for collaborative development and the pros and cons of joining the Foundation ## Issues: No issues ## Membership Data: Apache Petri was founded 2019-11-19 (a year 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: The BuildStream culture continues its migration with moving their GitLab repository over to Apache GitBox/GitHub with Infrastructure's fine assistance. The community continues to discuss their development efforts well on their dev@buildstrem.apache.org mailing list. ## Community Health: discuss@petri.apache.org had a big increase in traffic in the past quarter (26 emails compared to 0) Petri has a low level of activity. We have the attitude that the next culture we foster will come to us on their own. That may change in the next quarter. The plan to grow Petri PMC membership is to consider the Mentors from cultures once they have become TLPs. Culture mentors are Petri committers. ----------------------------------------- Attachment BG: Report from the Apache Ranger Project [Selvamohan Neethiraj] ----------------------------------------- Attachment BH: 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 ## Membership Data: Apache Rya was founded 2019-09-17 (a year 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: The first release as a TLP is now out. Apache Rya 4.0.1 was released on 2020-12-22. For the next release we are targeting updating the versions of Accumulo and other major dependencies. ## Community Health: There was a lot of activity this quarter related to work on the 4.0.1 release. Several PRs by new contributors were merged and are part of the release. There are several more PRs by new contributors to be reviewed. -dev@rya.apache.org had a 100% increase in traffic in the past quarter (54 emails compared to 27) -2 issues opened in JIRA, past quarter (100% increase) -10 issues closed in JIRA, past quarter (900% increase) -30 commits in the past quarter (3000% increase) -7 code contributors in the past quarter (700% increase) -12 PRs opened on GitHub, past quarter (200% increase) -16 PRs closed on GitHub, past quarter (700% increase) ----------------------------------------- Attachment BI: Report from the Apache Samza Project [Yi Pan] ## Description Apache Samza is a distributed stream processing engine that is highly configurable to process events from various data sources, including real-time messaging system (e.g. Kafka) and distributed file systems (e.g. HDFS). ## Issues: - There are no issues requiring board attention. ## Membership Data: Apache Samza was founded 2015-01-22 (6 years ago) There are currently 26 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 Bharath Kumarasubramanian on 2020-02-13. No new committers. Last addition was Rayman Preet Singh on 2019-07-08. ## Project Activity: - Added AM-HA to allow continuation of job when AM restarts - Preparing for release 1.6.0 ## Community Health: - We held another virtual meetup for Stream Processing on 12/16 - We have another Samza podcast on Software Engineering Radio channel on 11/24 - JIRA Activity: - 22 issues opened in JIRA, past quarter (-37% decrease) - 13 issues closed in JIRA, past quarter (85% increase) - Commit Activity: - 34 commits in the past quarter (-17% decrease) - 9 code contributors in the past quarter (-55% decrease) - 21 PRs opened on GitHub, past quarter (-41% decrease) - 20 PRs closed on GitHub, past quarter (-47% decrease) ----------------------------------------- Attachment BJ: 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 (2 years ago) There are currently 44 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Han Liu on 2020-08-10. - Junxu Chen was added as committer on 2020-11-01 - Wei Jin was added as committer on 2020-11-01 - Liu Jiapeng was added as committer on 2020-11-04 - Chao Chen was added as committer on 2020-11-04 - Juntao Zhang was added as committer on 2020-11-07 - Ke Zhang was added as committer on 2020-12-19 - Gui Cao was added as committer on 2020-12-09 ## Project Activity: We released following versions. python-0.5.0 was released on 2021-01-01. nodejs-0.1.0 was released on 2021-01-01. 8.3.0 was released on 2020-12-02 python-0.4.0 was released on 2020-11-23. client-js-0.2.0 was released on 2020-11-18. nginx-lua-0.3.0 was released on 2020-11-06 8.2.0 was released on 2020-10-27 Several representations are made by our PMC member at COSCon20, PyCon China 20, OpenAtom Foundation Conference. ## Community Health: The community is healthy. New contributors keep showing up, we reached 300+ code contributor for a single one repo, and near 400 code contributors of all repositories. dev@skywalking.apache.org had a 65% increase in traffic in the past quarter (268 emails compared to 162) 764 commits in the past quarter (47% increase) 83 code contributors in the past quarter (23% increase) Releases are more stable, the number of issues reduced a little. 284 issues opened on GitHub, past quarter (-17% decrease) 282 issues closed on GitHub, past quarter (-28% decrease) ----------------------------------------- Attachment BK: Report from the Apache Sqoop Project [Venkat Ranganathan] ## Description: The mission of Sqoop is the creation and maintenance of software related to Bulk Data Transfer for Apache Hadoop and Structured Datastores ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Sqoop was founded 2012-03-20 (9 years ago) There are currently 32 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Vasas Szabolcs on 2018-11-05. - No new committers. Last addition was Fero Szabo on 2018-11-08. ## Project Activity: Recent releases: 1.4.7 was released on 2018-01-24. 1.99.7 was released on 2016-08-08. 1.99.6 was released on 2015-05-04. ## Community Health: dev@sqoop.apache.org had a 75% increase in traffic in the past quarter (7 emails compared to 25) 1 issues opened in JIRA, past quarter (-75% decrease) 0 commits in the past quarter (no change) 0 code contributors in the past quarter (no change) 1 PR opened on GitHub, past quarter (100% decrease) ----------------------------------------- Attachment BL: 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 (8 years ago) There are currently 9 committers and 4 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - No new PMC members. Last addition was Rich Bowen on 2015-04-20. - No new committers. Last addition was Pierre Smits on 2015-12-15. ## Project Activity: Virtually no activity in this quarter, the project remains in "development hibernation" but with people around, should an issue or vulnerability be reported. The project is currently not aware of any outstanding time-sensitive issues, and thus are perfectly content with being in maintenance mode for now. ## Community Health: Community health remains the same. Still enough oversight on the PMC, but other than that there is not a lot going on at present. We do not consider this problematic (as of yet), but would of course love to see new people getting involved with the project. ----------------------------------------- Attachment BM: Report from the Apache Streams Project [Steve Blackmon] ## Description: Apache Streams unifies a diverse world of digital profiles and online activities into common formats and vocabularies, and makes these datasets accessible across a variety of databases, devices, and platforms for streaming, browsing, search, sharing, and analytics use-cases. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Streams was founded 2017-07-18 (3 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. ## Community changes: - Brian Hodge joined PMC on 2020-04-26 - Brian Hodge became a committer on 2020-04-26 ## Project Activity: - Apache Streams 0.6.1 was released in March 2020. - Apache Streams 0.7.0 will be the first compatible with JDK11. - 6 pull requests merged since Q4 board report. - Necessary work to enable Apache Streams 0.7.0 binary/bytecode release is in progress: curation of a NOTICE file. ## Community Health: - Adding committers and growing the PMC will remain a focus. - We need to identify and execute strategies to reach out to likely interested users and developers. - We need to conduct more regular roadmap planning, create and deliver based on a release schedule. ----------------------------------------- Attachment BN: 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 2.5.26 - Bug fix release (2020-12-06) 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 increased activity again. This goes both for development related mailing list traffic and development activity, with 58 opened and 55 closed pull requests in the reporting period compared to 17/18 in the previous quarter. The user mailing stays low on traffic. Users are seemingly looking for help mostly on Stack Overflow, rather than the project mailing list. We released one new security bulletins in the last quarter: [1] * S2-061 - Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution - similar to S2-059. (CVE-2020-17530) [2] We have no issues that require board assistance at this time. ## PMC changes: - Currently 22 PMC members. - 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: - dev@struts.apache.org: - 212 emails sent to list (129 in previous quarter) - issues@struts.apache.org: - 563 emails sent to list (361 in previous quarter) - user@struts.apache.org: - 30 emails sent to list (43 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months [1] https://struts.apache.org/announce.html#a20201208 [2] https://cwiki.apache.org/confluence/display/WW/S2-061 ----------------------------------------- Attachment BO: Report from the Apache Superset Project [Maxime Beauchemin] ## Description: Apache Superset is a Data Visualization and Data Exploration Platform ## Issues: No major issues to report ## Membership Data: Apache Superset was founded 2020-11-17 (2 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: - Lily Kuang was added to the PMC on 2020-12-06 - Rob DiCiuccio was added to the PMC on 2020-11-29 - Yongjie Zhao was added to the PMC on 2020-11-29 - Bence Orlai was added as committer on 2020-11-20 - Junlin Chen was added as committer on 2020-12-02 - Lily Kuang was added as committer on 2020-11-30 - Rob DiCiuccio was added as committer on 2020-11-20 - Srini Kadamati was added as committer on 2020-11-23 - Yongjie Zhao was added as committer on 2020-11-20 - Zuzana Vejrazkova was added as committer on 2020-12-08 ## Project Activity: We're scheduled to announce the graduation as well as the Superset 1.0.0 release on January 19th, coordinating with sally@apache.org ## Community Health: GitHub issues, PRs, discussions and Slack continues to be the place where a lot of the community interacts over the mailing lists. - dev@superset.apache.org had a 26% decrease in traffic in the past quarter (175 emails compared to 234) - notifications@superset.apache.org had a 144% increase in traffic in the past quarter (19154 emails compared to 7833) that's reflective of the high activity taking place on GitHub in - 1237 commits in the past quarter (60% increase) - 58 code contributors in the past quarter (1% increase) - 650 PRs opened on GitHub, past quarter (-1% decrease) - 626 PRs closed on GitHub, past quarter (no change) - 383 issues opened on GitHub, past quarter (24% increase) - 247 issues closed on GitHub, past quarter (-19% decrease) ----------------------------------------- Attachment BP: 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 2007-12-19 (13 years ago) There are currently 35 committers and 26 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 Prabath Ariyarathna on 2017-05-04. - No new committers. Last addition was Shafreen on 2020-07-14. ## Project Activity: We have initiated a new release to include the recent contributions we received from the newly elected committer Shafreen. He has volunteered to play the role of the release manager. We have included project ideas to Apache's Google summer of code project proposals to see whether we could attract new contributors through that program. ## Community Health: dev@synapse.apache.org had a 38% increase in traffic in the past quarter (29 emails compared to 21) 1 issue opened in JIRA, past quarter (100% increase) 3 commits in the past quarter (-25% decrease) 1 code contributor in the past quarter (-50% decrease) 2 PRs opened on GitHub, past quarter (-33% decrease) 2 PRs closed on GitHub, past quarter (-50% decrease) We expect these numbers to get increased singnificantly with the release work we are doing in the near future. ----------------------------------------- Attachment BQ: 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: A couple months ago I tried to remove the Tapestry private mailing list subscribers which aren't in the PMC using the tool at https://whimsy.apache.org/committers/moderationhelper.cgi and now I noticed it hasn't worked. I tried again today. ## Membership Data: Apache Tapestry was founded 2006-02-14 (15 years ago) There are currently 28 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - Ben Weidig was added as committer on 2020-12-30 ## Project Activity: We've had a quarter with more commit and ticket activity than average due to our new upcoming major version, 5.7.0, which we expect be released at most next month. We've added a new committer to our team last December. ## Community Health: dev@tapestry.apache.org had a 26% increase in traffic in the past quarter (120 emails compared to 95) users@tapestry.apache.org had a 75% decrease in traffic in the past quarter (13 emails compared to 51) 14 issues opened in JIRA, past quarter (7% increase) 15 issues closed in JIRA, past quarter (114% increase) 78 commits in the past quarter (32% increase) ----------------------------------------- Attachment BR: 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 (20 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: Building upon the work that has been done in preparing the 3.2 release (two artefacts have been released, Rivet 3.2.0rc1 and Rivet 3.2.0rcr), rivet-3.2.0 was released on 2020-11-07. ## Community Health: There has been an increase in the traffic of the mailing lists. rivet-dev@tcl.apache.org had a 520% increase in traffic in the past quarter (31 emails compared to 5) ----------------------------------------- Attachment BS: Report from the Apache Tez Project [Jonathan Turner Eagles] ## 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: Comments clr: Please keep the board informed regarding almost half of the PMC not being subscribed to the private mail list. It should be easy enough to ask if these folks really are still interested in providing oversight. - Sent request to 14 Tez PMC members to understand to understand interest in taking active role in providing oversight for the project and to present options of signing up to the private list, going emeritus, or resigning. Received 4 responses: 1 private list sign-up, 1 emeritus, 2 resignations. Leaving 11 PMC unsubscribed to private list. Will follow up again this quarter to address remaining 11 accounts. ## Membership Data: Apache Tez was founded 2014-07-15 (6 years ago) There are currently 38 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - László Bodor was added to the PMC on 2020-11-23 - No new committers. Last addition was László Bodor on 2020-01-22. ## Project Activity: New PMC member created release 0.10.0 was released on 2020-10-15. This release has future jdk release support and works with Apache Hadoop 3+. Ongoing github integration made great progress, by reaching out to yetus project and receive patches that will enable full support. Likely this quarter full yetus, github integration will be working. ## Community Health: - many github PRs were closed this quarter to prepare for this being a more active way to contribute to the project. -interest from apache nutch led to more user discussion that usual this month. -holiday vacation led to decreased activity overall on the user lists and active jira. ----------------------------------------- Attachment BT: Report from the Apache Thrift Project [Jens Geyer] ## Description: The mission of Thrift is the creation and maintenance of software related to Framework for scalable cross-language services development ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Thrift was founded 2010-10-20 (10 years ago) There are currently 39 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Duru Can Celasun on 2019-11-11. - Mario Emmenlauer was added as committer on 2020-12-04 ## Project Activity: * 0.13.0 was released on 2019-10-16. * Still working on release 0.14.0. The initial idea was to have the release ready end of 2020. This has not been achieved, but we now push again to prepare the planned release to be ready in the next few weeks. ## Community Health: Despite the numeric decrease in most areas there have been certain valuable contributions to the code base. We also finally managed to switch the Apache Thrift web site away from the deprecated CMS, last not least thanks to some support we got from INFRA. Key bottleneck is still the review pipeline. ----------------------------------------- Attachment BU: 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 over 1200 different file types including most of the major types in existence (MS Office, Adobe, 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 (11 years ago) There are currently 32 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - Peter Lee was added to the PMC on 2020-11-24 - Peter Lee was added as committer on 2020-11-25 ## Project Activity: We released 1.25 on 2020-11-40. This version included numerous dependency upgrades, a critical license issue with Adobe's xmpcore, and several new parsers. We are on the cusp of a release of Tika 2.0.0-ALPHA. On our file corpus development side project, we gathered "stressful" attachments from 35 parser issue trackers. This includes more than a million files (551GB). These are critical for stress testing our own parsers, and we're making the corpus available to other open source and commercial projects: https://corpora.tika.apache.org/base/docs/bug_trackers/. See, for example: https://www.pdfa.org/a-new-stressful-pdf-corpus/ and https://www.pdfa.org/stressful-pdf-corpus-grows/ ## Community Health: As noted above, we've added Peter Lee as a committer/PMC. A number of our JIRA and GitHub health metrics were down slightly in the last quarter. We attribute this to the holidays/new year. However, we saw an uptick in user@ traffic and a slight increase in commits. ----------------------------------------- Attachment BV: Report from the Apache TinkerPop Project [Stephen Mallette] ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). ## Activity: TinkerPop released version 3.4.9 during this reporting period. This version was the largest release of the year in terms of the number of JIRA issues completed, almost matching the total number closed in all the previous releases of 2020 combined. Much of this activity was driven by existing committers who were re-focused on the project in the last quarter of the year. We'd alluded to this re-focus in our last report, as well as the notion of new contributors, but new contributor activity trailed off a bit as we passed through October. Hopefully, some of those folks will return with the start of this new year. We've decided to put a stake in the ground for release of 3.5.0, which has been in development for over a year now, and release it in the March/April timeframe. While it is not everything we had expected it to be, it does contain a lot of necessary dependency and runtime upgrades. We will therefore refer to it as a "heavy maintenance release" and push off some major features to a future version of 3.6.0.[1] In our last report, we'd also noted that we had started the process for bringing gremlint.com[2] into the project as the official Gremlin language formatter. At this point, the owners of gremlint are still settling paperwork on their end. The most recent update from the author of gremlint can be found here[3]. In addition to gremlint, a second code contribution proposal has been made recently to provide an ANTLR grammar for Gremlin along with related code[4]. This source code would also go through the IP Clearance process. This proposal is still in an early stage, but would hopefully be completed in time for release of 3.5.0. In the wider TinkerPop ecosystem, we've recognized HugeGraph[5] as a graph database provider. HugeGraph is high-speed, distributed and scalable OLTP and OLAP graph database with visualized analytics platform. The addition of HugeGraph further solidifies TinkerPop and the Gremlin graph query language as a critical component of the graph processing space, with support for over two dozen graph systems. ## Issues: There are no issues requiring board attention at this time. ## Releases: - 3.4.9 (December 7, 2020) ## PMC/Committer: - Last PMC addition was Jorge Bay-Gondra - October 2018 - Last committer addition was Divij Vaidya - November 2019 ## Links [1] https://s.apache.org/rq6y1 [2] https://gremlint.com/ [3] https://s.apache.org/cjmw3 [4] https://s.apache.org/ol56j [5] https://github.com/hugegraph/hugegraph ----------------------------------------- Attachment BW: 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 (11 years ago) There are currently 64 committers and 53 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. Community changes, past quarter: - Brian Neradt was added to the PMC on 2020-10-23 - No new committers. Last addition was Brian Neradt on 2020-08-31. ## Project Activity: We released ATS 9.0.0, our next major release of ATS. We also made two additional security and bug fix releases for the 7.1.x and 8.1.x branches. With the 9.0.0 release we are ending support for the 7.1.x branch. ATS 8.1.x is now our LTS release branch. ## Community Health: We held our Fall summit remote in October of last year. The summit was well attended and we had people join and present from countries around the world. Our Spring and Fall summit this year will be remote. We are continuing to have monthly meetups during the pandemic to help keep the community socializing and communicating about current projects and corrdinate releases. In general statistics for the mailing lists and GitHub are down last quarter and this is normal for the time of year. The activity on GitHub and the mailing lists should increase this quarter. ----------------------------------------- Attachment BX: Report from the Apache Trafodion Project [Pierre Smits] ----------------------------------------- Attachment BY: Report from the Apache TVM Project [Tianqi Chen] ## Description: Apache TVM’s extensible full-stack framework enables deep learning applications to efficiently deploy across an array of hardware modules, platforms, and systems, including mobile phones, wearables, specialized chips, and embedded devices. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache TVM was founded 2020-11-17 (2 months ago) There are currently 38 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past month: - The community is discussing and voting new PMC members. - Chenfan was added as committer on 2020-12-18 ## Project Activity: Software development activity: - We land the first complete version of the automatic scheduling code generation. - The community has been working on improving the robustness of the internals (better logging and error messaging). - Improvements to uTVM (micro-controller compilation support). - Last project release was v0.7.0 (2020-10-02), the community is working hard to push for the v0.8 release cycle. Meetups and Conferences: - Annual developer conference(see the community health) ## Community Health: Overall community health is good. The amount of PRs drop to 100 (was 150) monthly. But this is expected due to the holiday season. Followed by a successful announcement of the TLP. The community successfully held a three day virtual developer conference (https://tvmconf.org/) on Dec 2-4. Nearly 1000 people registered. The conference attracted talks from major industry users, such as AMD, ARM, AWS, Qualcomm, OctoML, Xilinx, Alibaba, Huawei, and academic contributors from UW, UC Berkeley, Cornell, UCLA, Beihang University. During the conference, the community celebrated the apache way and talked about their applications and contributions to the Apache TVM. ----------------------------------------- Attachment BZ: Report from the Apache Web Services Project [Daniel Kulp] ## Description: Apache Web Services is a collection of shared technologies related to SOAP/XML based Web Services that can be shared by different implementations. Spring-WS, Axis2, CXF, and others use parts of the technology created within Apache Web Services. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Web Services was founded 2003-01-22 (18 years ago) There are currently 223 committers and 42 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - No new PMC members. Last addition was Alessio Soldano on 2016-05-17. - No new committers. Last addition was Alessio Soldano on 2014-09-14. ## Project Activity: WebServices is a mature project based on standards that are also quite mature. As such, there is not a significant amount of activity required. However, user questions are being answered promptly, bugs are being fixed, and there are at least 3 independent PMC members around making sure the project can continue to produce releases as needed. Since SOAP/XML based Web Services is no longer considered state of the art, we don't expect a major uptick in new development efforts, new committers, etc... There was very little work done this quarter. There were a few fixes in wss4j that we released as they were needed for CXF. There was also a bunch of activity in Axiom to upgrade to newer versions of various dependencies as well as be able to build/test with Java 11+. Past Releases: WSS4J-2.3.1: 2020-12-15 WSS4J-2.2.6: 2020-12-15 XmlSchema-2.2.5: 2020-01 Neethi-3.1.1: 2018-01 Axiom-1.2.21: 2018-11 Woden-1.0M10: 2015-09 ## Community Health: As mentioned, SOAP/WebServices is not considered state-of-the-art anymore and we are getting very little contribution from anyone other than the 2 or 3 regulars" that are driving features and changes needed for CXF (which is being driven by their employers). Thus, we are not seeing any possibilities for future new committers or PMC members. However, there are plenty of people around that can do releases and answer questions and respond to security issues. It's a mature project. ----------------------------------------- Attachment CA: Report from the Apache Zeppelin Project [Lee Moon Soo] ------------------------------------------------------ End of minutes for the January 20, 2021 board meeting.