The Apache Software Foundation Board of Directors Meeting Minutes March 18, 2020 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:32 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/4298 The meeting was held via teleconference, hosted by the Secretary via Zoom. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Danny Angus - joined 11:27 PT Rich Bowen Shane Curcuru Ted Dunning Dave Fisher Myrle Krantz Daniel Ruggeri Craig L Russell Roman Shaposhnik Directors Absent: none Executive Officers Present: Sally Khudairi David Nalley Tom Pappas Sam Ruby Matt Sicker Executive Officers Absent: none Guests: Carl Marcum Daniel Gruno Dirk-Willem van Gulik Greg Stein Joe Brockmeier Justin Mclean Mike Jumper Pierre Smits Sander Striker 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of February 19, 2020 See: board_minutes_2020_02_19.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Craig] The COVID-19 pandemic has had several effects on the operation of the Foundation. Many face-to-face conferences and meetings have been postponed or canceled, including Apache conferences and other open source and vendor conferences. More cancellations are expected before the situation is resolved. Considering that most of Apache's work communication happens via email, the functioning of the individual projects seems to continue with minimum disruption. If any member of the Apache community needs help dealing with the pandemic, they should let us know. The annual Members Meeting is on track and is expected to be conducted as normal. A reminder will be sent for everyone to submit a proxy if they are not sure they can attend the first part of the meeting via IRC. The membership will be asked to vote on recommending that the board update the Bylaws to change gender-specific terms to gender-neutral terms. Thanks to Patricia Shanahan for leading the effort to adopt a formal Conflict of Interest policy, which will be voted on shortly. B. President [Sam] As a reminder, I would like David Nalley to be considered the acting President at this time. I've forwarded on the rare emails I have received as President to David, and have not noted any problems that have occurred due to my deferring to David. To the contrary, I've been very pleased with the changes he has already instituted, in particular the monthly operations calls and the more rigorous checking that expenses that are incurred are actually charged against the right line items in the budget. At the present time, I'm assuming that the official changes in positions will be done by the new board. I don't foresee that being a problem. I contributed to the COI policy that is being drafted and am supportive of its adoption. Additionally, please see Attachments 1 through 9. C. Treasurer [Myrle] Operating Cash on February 29th, 2020 was $2,107.4K, which is down $30.4K from last month’s ending balance (Jan 20) of $2,137.8 K. Total Cash as of February 29th, 2020 is $3,501.3K (includes the Pineapple, Restricted Donation) as compared to $4,052.8K on January 31st, 2019, (a decrease of $551.5K year over year). The February 29th 2020 ending Operating cash balance of $2,107.4K represents an Operating cash reserve of 9.7 months based on the “Estimated” FY20 Cash forecast average monthly spending of $249.9K/month. The ASF actual Operating reserve of 9.7 months at the end of February 2020 is a bit ahead the budgeted 8.7 months of reserve for YTD February 29th, 2020. The estimated YE Operating reserve of 10.5 months is ahead of the Budgeted YE reserve of 7.6 months. The ASF Operating reserve is above the ASAE standard average of 6 months of reserve for Non-Profits. Reviewing the YTD Cash P&L, total Revenue is behind budget at this point in the Fiscal year by $288.6K (this is partly due to timing of sponsor payments and Conference and Donations lagging a bit behind budget at this point in the Fiscal) The open Accounts Receivable is very healthy at $448K, which as of the February 20 Financial Close is enough, if it all arrives in the bank, before 4.30.20, to achieve the FY20 Foundation Sponsorship Budget. As compared to FY19, FY20 YTD revenue is ahead by $131.6K primarily due to FY20 Events exceeding Revenue as compared to FY19, YTD. YTD expenses through February 29th, 2020 are under budget by $237.8K, spread across all depts except Conferences, Infra and D&I, which are minor amounts, comparatively speaking. The updated Cash forecast expects this underage in expenses to continue through the end of the Fiscal year. Regarding Net Income (NI), YTD FY20 the ASF finished with a negative <$288.9K> NI vs a budgeted negative <$238K> NI or $50.9K behind the Budgeted NI for FY20 at this point in the Fiscal year. The cash forecast has been updated, with the information we have at hand, and at this point with about 2 months left in the Fiscal year, we are still on pace to, if everything goes according to the Forecast, exceed our FY20 budgeted NI. I want to thank the Dept heads for their review of the FY20 actual activity which has allowed us to move some expenses to the correct accounts and departments, which has made the cash forecast a much more valuable management tool as we move forward and close out FY21. With regard to FY19, we are ahead in revenue, by $131.6K as noted above, but we are also ahead on expenses by $989.1K (due to ACNA19, ACEU19, the Lease web payment which should have taken place in FY19, but did not, as well as other expenses that occurred in FY20 and not in FY19); thus, year over year NI FY20 is behind FY19 by $857.5K. It is estimated that this will even out, to a degree, as the FY20 progresses. Current Balances: Boston Private CDARS Account 2,278,368.45 Citizens Money Market 715,009.35 Citizens Checking 505,788.54 Paypal - ASF 2,143.00 Total Checking/Savings 3,501,309.34 Feb-20 Budget Variance Income Summary: Public Donations 3,363.27 2,455.29 907.98 Sponsorship Program 150,000.00 162,000.00 -12,000.00 Programs Income 0.00 0.00 0.00 Conference/Event Income 0.00 0.00 0.00 Other Income 0.00 Interest Income 11,752.52 400.00 11,352.52 Total Income 165,115.79 164,855.29 260.50 Expense Summary Infrastructure 88,951.27 85,733.09 3,218.18 Programs Expense 4,166.00 3,333.33 832.67 Publicity 46,863.34 29,308.32 17,555.02 Brand Management 0.00 8,166.66 -8,166.66 Conferences 2,750.00 12,250.00 -9,500.00 Travel Assistance Committee 4,302.87 10,000.00 -5,697.13 Fundraising 12,020.01 16,080.00 -4,059.99 Treasury Services 5,659.00 5,850.00 -191.00 General & Administrative 780.84 1,915.00 -1,134.16 Diversity and Inclusion 30,000.00 5,833.33 24,166.67 Total Expense 195,493.33 178,469.73 17,023.60 Net Income -30,377.54 -13,614.44 -16,763.10 YTD FY20 Budget Variance Income Summary: Public Donations 95,228.64 127,311.35 -32,082.71 Sponsorship Program 1,206,600.00 1,390,000.00 -183,400.00 Programs Income 14,900.00 14,000.00 900.00 Conference/Event Income 610,161.06 700,000.00 -89,838.94 Other Income 0.00 0.00 Interest Income 20,040.50 4,250.00 15,790.50 Total Income 1,946,930.20 2,235,561.35 -288,631.15 Expense Summary Infrastructure 918,547.10 911,830.82 6,716.28 Programs Expense 16,586.31 33,333.32 -16,747.01 Publicity 295,977.82 360,488.36 -64,510.54 Brand Management 35,958.09 81,666.68 -45,708.59 Conferences 681,886.78 645,500.00 36,386.78 Travel Assistance Committee 50,361.68 155,000.00 -104,638.32 Fundraising 123,895.60 160,800.00 -36,904.40 Treasury Services 35,809.00 36,000.00 -191.00 General & Administrative 16,843.19 30,670.00 -13,826.81 Diversity and Inclusion 60,000.00 58,333.32 1,666.68 Total Expense 2,235,865.57 2,473,622.50 -237,756.93 Net Income -288,935.37 -238,061.15 -50,874.22 D. Secretary [Matt] In February, the secretary received 74 ICLAs, 2 CCLAs, 4 SGAs, and 3 emeritus requests. Note that these emeritus requests are from the past three months are were not all sent in February; they were officially filed in February. E. Executive Vice President [David] This month has been a busy one for the Operations side of the ASF. The COVID-19 pandemic has generated a lot of work for Conferences, Marketing & Publicity, Fundraising, Travel Assistance, and Infrastructure. FY21 Budget =========== A good deal of work has been done by those officers with budgets, both in vetting the items charged against them, as well as preparing plans for the coming year. The current proposed budget shows a loss of roughly 176k. Just to begin preparing folks and start the discussion you can view my budget worksheet here: https://s.apache.org/FY21-Draft-Budget We still have some account rejiggering to do, but I suspect we're close to final form. I am still missing a few smaller numbers and I've highlighted those cells in yellow, and that will change as we move forward. Fundraising =========== Despite all of the extra work from the pandemic, and the normal good work; I do want to call out what I see as an incredible victory from the Fundraising team in a multi-year commitment from one our Platinum sponsors. Marketing and Publicity ======================= Working smoothly despite the increased workload. Travel Assistance ================= TAC was ramping up to support roadshows, but that's no longer needed. TAC has also realized that they keep standing up web apps for collection of information about applicants. With the need to support ever more of these, they are looking for something that demands less volunteer time. They're working on creating a requirements list as well as discussing what others who do similar work in our space are doing. D&I === Survey hasn't materially moved but should have progress to report by next month. I highly recommend that all Directors read the friction logs from the first Outreachy session. There's very valuable insight there. Because of the small number and privacy concerns, members and Directors can read those on the D&I private list. The upcoming Outreachy term has three projects teed up. Privacy ======= A GDPR request has been handled. Work remains to be done on a repeatable process and governance. Conferences =========== Conferences has cancelled or postponed 3 Roadshows thus far. Work continues forward with ApacheCon. F. Vice Chairman [Shane] Assisted with preparing files and communications for our Annual Member's Meeting this month. As an all-online organization, the recent COVID-19 disruptions are not a direct issue for most of our operations. However, as an all-volunteer organization, many development activities may take longer than expected, as our volunteer committers spend time keeping their families safe. A big thank you to all of our communities for their help in this turbulent time. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Daniel] No report was submitted. B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 11 C. Apache Security Team Project [Mark J. Cox / Danny] See Attachment 12 D. VP of Jakarta EE Relations [Mark Struberg / Shane] No report was submitted. Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Cordova [df] # Flume [rb] # Hama [rs] # Karaf [rb] # Olingo [myrle] # Portals [da] # SINGA [da] A. Apache Airflow Project [Bolke de Bruin / Roman] See Attachment A B. Apache Allura Project [David Philip Brondsema / Ted] See Attachment B C. Apache Ambari Project [Jayush Luniya / Craig] See Attachment C D. Apache Any23 Project [Lewis John McGibbney / Myrle] See Attachment D E. Apache Archiva Project [Olivier Lamy / Dave] See Attachment E F. Apache Atlas Project [Madhan Neethiraj / Rich] See Attachment F G. Apache Axis Project [Robert Lazarski / Ted] See Attachment G H. Apache Bahir Project [Luciano Resende / Myrle] See Attachment H I. Apache Beam Project [Kenneth Knowles / Rich] No report was submitted. @Rich: pursue a report for Beam J. Apache Bigtop Project [Jun He / Danny] See Attachment J K. Apache Bloodhound Project [Gary Martin / Daniel] No report was submitted. @Daniel: pursue a report for Bloodhound L. Apache BVal Project [Matthew Jason Benson / Dave] No report was submitted. @Dave: pursue a report for BVal M. Apache Camel Project [Andrea Cosentino / Shane] See Attachment M N. Apache Cayenne Project [Michael Ray Gentry / Craig] See Attachment N O. Apache Chemistry Project [Florian Müller / Roman] See Attachment O P. Apache CloudStack Project [Paul Angus / Roman] See Attachment P Q. Apache Cocoon Project [Cédric Damioli / Ted] See Attachment Q R. Apache Commons Project [Gary D. Gregory / Daniel] See Attachment R S. Apache Cordova Project [Jesse MacFadyen / Craig] See Attachment S @Daniel: continue tracking targeted donation T. Apache cTAKES Project [Pei Chen / Shane] See Attachment T U. Apache Curator Project [Jordan Zimmerman / Danny] See Attachment U V. Apache DRAT Project [Tom Barber / Dave] See Attachment V W. Apache Druid Project [Gian Merlino / Myrle] See Attachment W X. Apache Eagle Project [Edward Zhang / Rich] See Attachment X Y. Apache Felix Project [Karl Pauls / Shane] See Attachment Y Z. Apache Flex Project [Olaf Krüger / Myrle] See Attachment Z AA. Apache Flink Project [Stephan Ewen / Danny] See Attachment AA AB. Apache Flume Project [Ferenc Szabo / Rich] See Attachment AB AC. Apache Gora Project [Kevin Ratnasekera / Ted] See Attachment AC AD. Apache Guacamole Project [Mike Jumper / Dave] See Attachment AD AE. Apache Gump Project [Stefan Bodewig / Craig] See Attachment AE AF. Apache Hama Project [Chia-Hung Lin / Roman] No report was submitted. @Dave: inform Hama about next steps for Attic resolution AG. Apache Helix Project [Kishore G / Daniel] See Attachment AG AH. Apache Hive Project [Ashutosh Chauhan / Myrle] See Attachment AH AI. Apache Incubator Project [Justin Mclean / Shane] See Attachment AI AJ. Apache Jackrabbit Project [Marcel Reutegger / Danny] See Attachment AJ AK. Apache Joshua Project [Tommaso Teofili / Roman] No report was submitted. AL. Apache Karaf Project [Jean-Baptiste Onofré / Dave] See Attachment AL AM. Apache Labs Project [Danny Angus] See Attachment AM AN. Apache Lucene Project [Anshum Gupta / Daniel] See Attachment AN AO. Apache Lucene.Net Project [Shad Storhaug / Craig] See Attachment AO AP. Apache Marmotta Project [Jakob Frank / Ted] No report was submitted. AQ. Apache Mnemonic Project [Gang Wang / Rich] No report was submitted. AR. Apache Mynewt Project [Justin Mclean / Craig] See Attachment AR AS. Apache NetBeans Project [Geertjan Wielenga / Danny] See Attachment AS AT. Apache OFBiz Project [Jacopo Cappellato / Rich] See Attachment AT AU. Apache Olingo Project [Michael Bolz / Daniel] See Attachment AU AV. Apache OODT Project [Imesha Sudasingha / Dave] No report was submitted. @Dave: pursue a report for OODT AW. Apache OpenNLP Project [Jeffrey T. Zemerick / Shane] See Attachment AW AX. Apache OpenWebBeans Project [Mark Struberg / Roman] No report was submitted. @Roman: pursue a report for OpenWebBeans AY. Apache Pig Project [Koji Noguchi / Myrle] See Attachment AY AZ. Apache Pivot Project [Roger Lee Whitcomb / Ted] No report was submitted. @Ted: pursue a report for Pivot BA. Apache PLC4X Project [Christofer Dutz / Ted] See Attachment BA BB. Apache Portable Runtime (APR) Project [Nick Kew / Roman] See Attachment BB BC. Apache Portals Project [David Sean Taylor / Shane] See Attachment BC @Danny: follow up on project viability to handle security issues BD. Apache PredictionIO Project [Donald Szeto / Myrle] See Attachment BD BE. Apache Pulsar Project [Matteo Merli / Daniel] See Attachment BE BF. Apache River Project [Peter Firmstone / Rich] See Attachment BF BG. Apache Royale Project [Piotr Zarzycki / Dave] See Attachment BG BH. Apache Sentry Project [Kalyan Kalvagadda / Danny] No report was submitted. @Danny: pursue a report for Sentry BI. Apache Serf Project [Branko Čibej / Craig] No report was submitted. @Danny: see if project needs additional help or ready for Attic BJ. Apache ServiceMix Project [Krzysztof Sobkowiak / Roman] See Attachment BJ BK. Apache Shiro Project [Les Hazlewood / Daniel] See Attachment BK BL. Apache SINGA Project [Wang Wei / Danny] See Attachment BL BM. Apache Sling Project [Robert Munteanu / Craig] See Attachment BM BN. Apache SpamAssassin Project [Sidney Markowitz / Myrle] See Attachment BN BO. Apache Stanbol Project [Rafa Haro / Ted] No report was submitted. BP. Apache Storm Project [Kishor Patil / Rich] See Attachment BP BQ. Apache Submarine Project [Wangda Tan / Dave] See Attachment BQ BR. Apache Synapse Project [Isuru Udana / Shane] See Attachment BR BS. Apache Tajo Project [Hyunsik Choi / Daniel] See Attachment BS BT. Apache Tomcat Project [Mladen Turk / Shane] See Attachment BT BU. Apache Trafodion Project [Pierre Smits / Ted] See Attachment BU BV. Apache Twill Project [Terence Yim / Craig] No report was submitted. @Ted: pursue possibility of Attic resolution BW. Apache UIMA Project [Marshall Schor / Rich] See Attachment BW BX. Apache Unomi Project [Serge Huber / Myrle] See Attachment BX BY. Apache VCL Project [Josh Thompson / Roman] See Attachment BY BZ. Apache Wicket Project [Andrea Del Bene / Danny] See Attachment BZ CA. Apache Xerces Project [Michael Glavassevich / Dave] See Attachment CA CB. Apache Yetus Project [Allen Wittenauer / Rich] See Attachment CB CC. Apache ZooKeeper Project [Flavio Paiva Junqueira / Roman] See Attachment CC Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache CloudStack Project Chair WHEREAS, the Board of Directors heretofore appointed Paul Angus (paul_a) to the office of Vice President, Apache CloudStack, and WHEREAS, the Board of Directors is in receipt of the resignation of Paul Angus from the office of Vice President, Apache CloudStack, and WHEREAS, the Project Management Committee of the Apache CloudStack project has chosen by vote to recommend Sven Vogel (svogel) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Paul Angus is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache CloudStack, and BE IT FURTHER RESOLVED, that Sven Vogel be and hereby is appointed to the office of Vice President, Apache CloudStack, 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 CloudStack Project Chair, was approved by Unanimous Vote of the directors present. B. Adopt a COI policy WHEREAS, the Board of Directors desires to increase clarity around correct handling of conflicts of interest, and WHEREAS, the Board of Directors desires to hold our organization to the highest standards of transparency NOW, THEREFORE, BE IT RESOLVED, the following conflict of interest policy, be adopted, and that the Secretary be charged and entrusted with the record keeping which results from Articles IV and VI, and that the Chairman of the Board be charged and entrusted with the ensuring the performance of periodic reviews as described in Article VII. Article I - Purpose The purpose of the conflict of interest policy is to protect the Apache Software Foundation's (ASF's) interest when it is contemplating entering into a transaction or arrangement that might benefit the private interest of an officer or director of the ASF or might result in a possible excess benefit transaction. This policy is intended to supplement but not replace any applicable state and federal laws governing conflict of interest applicable to nonprofit and charitable organizations. Article II - Definitions 1. Principal Officer: A principal officer is an officer other than a PMC chair who holds no other office. 2. Interested Person: Any director or principal officer who has a direct or indirect financial interest, as defined below, is an interested person. 3. Financial Interest: A person has a financial interest if the person has, directly or indirectly, through business, investment, or family: a. An ownership or investment interest in any entity with which the ASF has a transaction or arrangement, b. A compensation arrangement with the ASF or with any entity or individual with which the ASF has a transaction or arrangement, or c. A potential ownership or investment interest in, or compensation arrangement with, any entity or individual with which the ASF is negotiating a transaction or arrangement. Compensation includes direct and indirect remuneration as well as gifts or favors that aren’t insubstantial. For purposes of this policy, an ownership or investment interest that is insubstantial need not be disclosed. A financial interest isn’t necessarily a conflict of interest. Under Article III, Section 2, a person who has a financial interest may have a conflict of interest only if they declare a possible conflict of interest or the appropriate board decides that a conflict of interest exists. Article III - Procedures 1. Duty to Disclose In connection with any actual or possible conflict of interest, an interested person must choose one of two paths: a. They can disclose the existence of a possible conflict of interest, and recuse themselves from the affected decisions, without giving any more information. b. If the interested person believes the financial interest does not constitute a conflict of interest they must disclose the existence of the financial interest and be given the opportunity to disclose all material facts to the directors and members of committees with governing board delegated powers considering the proposed transaction or arrangement. 2. Determining Whether a Conflict of Interest Exists In case of voluntary declaration of a possible conflict of interest and recusal, the conflict is presumed to exist. If the interested person declares a financial interest without voluntary recusal then after disclosure of the financial interest and all material facts, and after any discussion with the interested person, the remaining board or committee members shall decide if a conflict of interest exists. 3. Procedures for Addressing the Conflict of Interest a. An interested person may make a presentation to the board or relevant committee, but shall not cast a vote on the transaction or arrangement involving the possible conflict of interest. b. The chairperson of the governing board or committee shall, if appropriate, appoint a disinterested person or committee to investigate alternatives to the proposed transaction or arrangement. c. After exercising due diligence, the governing board or committee shall determine whether the ASF can obtain with reasonable efforts a more advantageous transaction or arrangement from a person or entity that would not give rise to a conflict of interest. d. If a more advantageous transaction or arrangement isn’t reasonably possible under circumstances not producing a conflict of interest, the governing board or committee shall determine by a majority vote of the disinterested directors whether the transaction or arrangement is in the ASF's best interest, for its own benefit, and whether it is fair and reasonable. In conformity with the above determination it shall make its decision as to whether to enter into the transaction or arrangement. 4. Violations of the Conflicts of Interest Policy a. If the governing board or committee has reasonable cause to believe a member has failed to disclose actual or possible conflicts of interest, it shall inform the member of the basis for such belief and afford the member an opportunity to explain the alleged failure to disclose. b. If, after hearing the member's response and after making further investigation as warranted by the circumstances, the governing board or committee determines the member has failed to disclose an actual or possible conflict of interest, it shall take appropriate disciplinary and corrective action. Article IV - Records of Proceedings The minutes of the governing board and all committees with board delegated powers shall contain: a. The names of the persons who disclosed or otherwise were found to have a financial interest in connection with an actual or possible conflict of interest. If the interested person did not choose voluntary recusal, the nature of the financial interest, any action taken to determine whether a conflict of interest was present, and the governing board's or committee's decision as to whether a conflict of interest in fact existed. b. The names of the persons who were present for discussions and votes relating to the transaction or arrangement, the content of the discussion, including any alternatives to the proposed transaction or arrangement, and a record of any votes taken in connection with the proceedings. Article V - Compensation a. A voting member of the governing board who receives compensation, directly or indirectly, from the ASF for services is precluded from voting on matters pertaining to that member's compensation. b. A voting member of any committee whose jurisdiction includes compensation matters and who receives compensation, directly or indirectly, from the ASF for services is precluded from voting on matters pertaining to that member's compensation. c. No voting member of the governing board or any committee whose jurisdiction includes compensation matters and who receives compensation, directly or indirectly, from the ASF, either individually or collectively, is prohibited from providing information to any committee regarding compensation. Article VI - Annual Statements Each director, principal officer and member of a committee with governing board delegated powers shall annually sign a statement which affirms such person: a. Has received a copy of the conflicts of interest policy, b. Has read and understands the policy, c. Has agreed to comply with the policy, and d. Understands the ASF is charitable and in order to maintain its federal tax exemption it must engage primarily in activities which accomplish one or more of its tax-exempt purposes. For purposes of this article, a Project Management Committee (PMC) having only the normal powers of a PMC is not a committee with governing board delegated powers. Article VII - Periodic Reviews To ensure the ASF operates in a manner consistent with charitable purposes and doesn't engage in activities that could jeopardize its tax-exempt status, periodic reviews shall be conducted. The periodic reviews shall, at a minimum, include the following subjects: a. Whether compensation arrangements and benefits are reasonable, based on competent survey information, and the result of arm's length bargaining. b. Whether partnerships, joint ventures, and arrangements with management organizations conform to the ASF's written policies, are properly recorded, reflect reasonable investment or payments for goods and services, further charitable purposes and don't result in inurement, impermissible private benefit, or in an excess benefit transaction. Article VIII - Use of Outside Experts When conducting the periodic reviews as provided for in Article VII, the ASF may, but need not, use outside advisers. If outside experts are used, their use shall not relieve the governing board of its responsibility for ensuring periodic reviews are conducted. Special Order 7B, Adopt a COI policy, was approved by Unanimous Vote of the directors present. C. Change the Apache Flume Project Chair WHEREAS, the Board of Directors heretofore appointed Ferenc Szabo (szaboferee) to the office of Vice President, Apache Flume, and WHEREAS, Ferenc Szabo is no longer performing the duties of Vice President, Apache Flume and is not responding to emails and WHEREAS, the Project Management Committee of the Apache Flume project has chosen by vote to recommend Balázs Donát Bessenyei (bessbd) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ferenc Szabo is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Flume, and BE IT FURTHER RESOLVED, that Balázs Donát Bessenyei be and hereby is appointed to the office of Vice President, Apache Flume, 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 Flume Project Chair, was approved by Unanimous Vote of the directors present. D. Change the Apache OpenOffice Project Chair WHEREAS, the Board of Directors heretofore appointed Jim Jagielski (jim) to the office of Vice President, Apache OpenOffice, and WHEREAS, the Board of Directors is in receipt of the resignation of Jim Jagielski from the office of Vice President, Apache OpenOffice, and WHEREAS, the Project Management Committee of the Apache OpenOffice project has chosen by vote to recommend Carl B. Marcum (cmarcum) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jim Jagielski is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache OpenOffice, and BE IT FURTHER RESOLVED, that Carl B. Marcum be and hereby is appointed to the office of Vice President, Apache OpenOffice, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache OpenOffice Project Chair, was approved by Unanimous Vote of the directors present. E. Change the Jakarta EE Relations VP WHEREAS, the Board of Directors heretofore appointed Mark Struberg (struberg) to the office of Vice President, Apache Jakarta EE Relations, and WHEREAS, the Board of Directors is in receipt of the resignation of Mark Struberg from the office of Vice President, Apache Jakarta EE Relations, and WHEREAS, the Board of Directors has found Henri Yandell (bayard) to be a qualified successor to the post of Vice President, Apache Jakarta EE Relations; NOW, THEREFORE, BE IT RESOLVED, that Mark Struberg is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Jakarta EE Relations, and BE IT FURTHER RESOLVED, that Henri Yandell be and hereby is appointed to the office of Vice President, Apache Jakarta EE Relations, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Change the Jakarta EE Relations VP, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * David: close the loop with Arrow and other communities with needs for CI [ Arrow 2019-10-16 ] Status: * Rich: pursue a roll call for PredictionIO [ PredictionIO 2019-12-18 ] Status: Roll call was completed, with more than adequate response. * Dave: find a volunteer for this position [ Jakarta EE Relations 2020-01-15 ] Status: Done. We have a volunteer - Henri Yandell * Myrle: follow up on security issue [ Aries 2020-01-15 ] Status: * Daniel: follow up on outstanding questions to PMC [ AsterixDB 2020-01-15 ] Status: Done 2020/01/26 * Danny: pursue a roll call [ Helix 2020-01-15 ] Status: Done (Not needed) Helix release was voted by three PMC members. * DanielGruno: start graduation talks with Pony Mail [ Incubator 2020-01-15 ] Status: * Dave: push for Attic discussion with PMC and community [ Stanbol 2020-01-15 ] Status: Done. There have been two +1 to go to the Attic the dev@stanbol mailing list. Next step is to add the resolution. * David: determine top ten CI issues affecting projects [ President 2020-02-19 ] Status: * Rich: pursue report for next month [ Cocoon 2020-02-19 ] Status: Done * Roman: pursue a report for Flume [ Flume 2020-02-19 ] Status: done. * Daniel: pursue a report for Gora [ Gora 2020-02-19 ] Status: Done * Ted: begin Attic process with Hama [ Hama 2020-02-19 ] Status: * Craig: pursue a report for Helix [ Helix 2020-02-19 ] Status: done. report submitted for March 2020 meeting * Ted: pursue a report for Joshua [ Joshua 2020-02-19 ] Status: * Daniel: follow up about log4net security fix [ Logging Services 2020-02-19 ] Status: Pending response (email sent 2020-03-17) * Shane: pursue a report for Marmotta [ Marmotta 2020-02-19 ] Status: * Danny: find out about fork details [ Open Climate Workbench 2020-02-19 ] Status: * Ted: pursue a report for River [ River 2020-02-19 ] Status: done. * Danny: pursue a report for Serf [ Serf 2020-02-19 ] Status: emailed 3/12 and emailed again 3/16 * Daniel: follow up with questions from comments [ SIS 2020-02-19 ] Status: Done - PMC responded on list * Craig: fill in unfinished business section for next board meeting [ Long Running Topics of Board Interest 2020-02-19 ] Status: done. * Myrle: pursue a report for DRAT [ DRAT 2020-02-19 ] Status: done. 10. Unfinished Business Clarify guidelines for PMCs to publish binary artifacts Clarify guidelines for PMCs to request Continuous Integration resources Determine how to accept Restricted Donations 11. New Business 12. Announcements 13. Adjournment Adjourned at 11:58 a.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] * ISSUES FOR THE BOARD None. * OPERATIONS Covering the period January 2020 Responded to the following queries, liaising with projects as required: - Approved three podling name searches - Continued to work on the downstream distribution policy - Approved one use of our logos to identify our products within third-party products / websites - Provided advice on naming an external product to avoid infringement - Approved one use of logos on t-shirts - Approved one external event - Provided advice regarding correct attribution of ASF marks in an external white paper - The Brand Management Google account (formerly used for web site analytics has been deleted) * REGISTRATIONS - Started the process to register FLINK in China and the EU - The process to transfer the SERVICECOMB marks continues * INFRINGEMENTS Provided advice to BEAM regarding a potential infringement. KAFKA has resolved an issue related to external product naming. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] Fundraising continues operating smoothly with renewals and business-as-usual work. We are pursuing renewals for one Gold, two Silver, and two Bronze sponsors. One sponsor has deepened their commitment to The ASF by upgrading to Platinum and signing a multi-year sponsorship agreement. We are waiting for purchase orders to invoice renewals for one Platinum and one Gold sponsor. One Gold and one Silver sponsor have been acquired and are sorting out their future budgets/strategy. We have been seeking a new point-of-contact for one Silver and one Bronze sponsors. One Gold sponsor is in arrears. We had no new Sponsors this month. We are finalizing our outreach to our Targeted Sponsors to confirm their commitment to renew their benefits to The ASF through 2020. We will continue to work on developing a new Targeted fund specifically earmarked for TAC recipients to ASF events in collaboration with the TAC team, but will hold off on its launch until travel bans and coronavirus-related issues ease. We also received a new Targeted donation to benefit Apache Tomcat. We have reached out to all Sponsors regarding their renewals, per their usual sponsorship cycle. We also pre-pitched sponsorship opportunities for ASF Conferences in 2020. We will be following up to share the Q3 Operations Summary as well as the ASF Statement on the COVID-19 coronavirus Outbreak and an update on ASF conferences. Support for ASF Conferences in 2020 continues as usual, comprising 3 Roadshows in North America and 1 in Europe, as well as ApacheCon North America. We have ceased sales for those Roadshows that were cancelled or postponed due to the coronavirus. We earned $2,215 over the past month from individual donations and corporate giving. We have been experiencing a high volume of repeat fraudulent donation attempts over the past few months, and have successfully worked with Hopsie and ASF Infrastructure to resolve the issue. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: we are sorting out some budget anomalies, such as charges from other ASF operations areas mistakenly applied against the M&P budget, as well as reconciling a small handful of bills that continue to be presented by a vendor that has already been paid. We intend to resolve the outstanding issues during March to avoid a scramble at the end of the fiscal year. II. Cross-committee Liaison: Sally Khudairi continues to support ASF Fundraising with Sponsor Relations outreach, Sponsorship renewals, Targeted Sponsor commitments, pursuing outstanding sponsorship fee payments. We have successfully secured commitment for a multi-year Platinum sponsorship which will commence towards the end of FY2020. We are also making arrangements for a one-off corporate donation valued between ASF Platinum and Gold levels to be received before the end of FY2020. We are also developing a specific Targeted fund towards TAC sponsorship for Apache events, but will be holding off on launching due to widespread corporate travel bans and serious health risks by travelling to events. Our work with ASF 2020 Conferences has shifted towards assisting with status notifications for those events impacted by the coronavirus. We also published The Apache Software Foundation Statement on the COVID-19 Coronavirus Outbreak https://s.apache.org/COVID-19 , as well as sent messages of support and encouragement to ASF Sponsors and Committers during this difficult time; the FY2020 Q3 Report/Operations Summary https://s.apache.org/r6s5u , "Success at Apache: Google Summer of Code Mentorship --inside the GSoC 2019 Mentor Summit" https://s.apache.org/ejj5q , and the February edition of the Apache Month in Review (a new monthly overview of events that have taken place within the Apache community) https://s.apache.org/Feb2020 . Post-production continues on the ASF documentary, "Trillions and Trillions Served". III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe. 3 March - The Apache Software Foundation Announces Apache® Brooklyn(TM) v1.0 27 February - The Apache Software Foundation Announces 20th Anniversary of Apache® Subversion® IV. Informal Announcements: we published 14 items on the ASF "Foundation" Blog. 5 Apache News Round-ups and 2 monthly overviews were issued, with a total of 299 news summaries published to date. We tweeted 28 items to 56.3K followers on Twitter, and posted 21 items on LinkedIn that garnered more than 73K organic impressions. V. Future Announcements: 2 announcements are on hold. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones, "Did You Know?" success stories, "Have You Met?" highlights, and "Project Perspectives" profiles are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to five media queries. The ASF received 1,276 press clips vs. last month's clip count of 1,213. Media coverage of Apache projects yielded 1,622 press hits vs. last month's 1,180. ApacheCon received 3 press hits. VII. Analyst Relations: we received two briefing requests and one extended fact-check. Apache was mentioned in 2 reports by Gartner; 8 reports by Forrester; 6 reports by 451 Research; and 5 reports by IDC. VIII. Central Services: the Creative team have been updating the Apache project logo page and updating all "Powered By Apache" badges where possible. Our work on a new home page for Central Services requests (both Creative and Editorial) continues. We continue to grapple with gaps in editorial production due to volunteers' limited availability. IX. Events liaison: we have been assisting a member of the "executive team" with their keynote presentation at a Sponsor-run event, which has since become an online event due to the coronavirus. We received offers to hold an ASF booth at two Apache project events, and are seeking local volunteers from ComDev to participate, providing that they are still taking place. We have also been providing supporting communications regarding the coronavirus impact on ASF Conferences, including Apache Roadshows and ApacheCon. X. Newswire and press clip accounts: all accounts are auto-renewing through 2020 to ensure we have constant service and access without interruption. We have been experiencing some accounts issues with one of our vendors following their acquisition and double-rebranding: it appears that their systems are still not fully integrated, as we continue to simultaneously receive confirmation of payment and overdue bill notifications. In addition, their online press release distribution management system mis-assigned a HALO-originating, non-ASF project to the ASF account. HALO will be reimbursing the ASF for the amount and paid in error. # # # ----------------------------------------- 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 ========== - The Infrastructure F2F in Nashville has been canceled. Our accomodations have been fully refunded. It is unclear whether flights will be refunded; we have spent about US$3250. - One of our staff departed the Foundation on March 13, 2020. We will begin the hiring process to backfill this position. - The Board requested specific reporting upon our CI/CD services. We have pulled together a page to gather insights: https://infra-reports.apache.org/cistats/ We will continue to refine this page, specifically to delineate projects using their own build nodes vs those of shared nodes. Finances ======== We submitted a revised budget to the President, incorporating a new line item for the service which runs lists.a.o. This expense had historically not appeared within Infra cost accounts, so we missed carrying this forward into the FY21 budget. Short Term Priorities ===================== - TravisCI renewal contract. Long Range Priorities ===================== - Continued CI/CD capacity growth. General Activity ================ - blogs.a.o was migrated to 1804/p6, in coordination with M&PR. - Groundwork for switching to AWS Route53 for DNS management. - CI/CD statistics gathering and reporting. - Working with our mirror provides to move them to https: if possible, in light of Chrome eventually disabling downloads from http: sites. - Continued work on new Jenkins masters for project-specific groups of build nodes. - Stood up pubsub.a.o as a new service to coordinate various actions across the Foundation. It is intended to replace the ad-hoc systems in use today, under a single cover. This will incorporate git/svn commit notifications, website publishing, PR/issue updates from GitHub, and more. Future work will incorporate better resiliency, replay, monitoring, and insights which are missing from today's variant systems. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] In light of the World Health Organization raising the threat level about the COVID-19 coronavirus outbreak, we have decided, after much consideration, to cancel or postpone the three Apache Roadshows that were scheduled to occur in the next few months. Details have been posted to the blog: https://blogs.apache.org/foundation/entry/notice-on-apache-2020-conferences Apache Roadshow, DC, scheduled for 25 March has been canceled. Apache Roadshow, Chicago, scheduled for May 18-19, has been canceled. Apache Roadshow, Seattle, scheduled for June 10-12, has been postponed until further notice. ApacheCon North America, New Orleans, scheduled for September 28 - October 1 is still planned to occur. Two more events are being planned, but we have no published details on them at this time. * Apache Roadshow, Europe * Apache Roadshow, China Individual event reports follow: Apache Roadshow, DC Apache Roadshow DC 2020 is canceled. Attempts were made to switch to a virtual event but we were unable to get enough speakers interested. Otherwise everything to shut it down is now complete: All checks have been returned, all tickets refunded, all vendors notified, all swag canceled, all food cancelled, and all speakers notified. Apache Roadshow, Chicago Website updated. Tickets refunded. Speaker notified of cancellation. Venues cancelled. Will file expense reimbursement for $30 fee at one venue (only explicit cost for ARS-Chicago). Apache Roadshow, Seattle Seattle roadshow has been postponed. No new date has been selected as of this time. ApacheCon North America, New Orleans We continue to move forward with this event. The Call for Presentation is still open, and we have received 52 proposals so far. This is about on track with what we usually see, with most of the proposals arriving in the last 2 weeks before the deadline, so we have no cause for concern here. We are receiving queries about sponsorship, and many sponsorship opportunities still remain open. Apache Roadshow Berlin Eu Roadshow Berlin is currently in preparation to go public (Homepage is in preparation). The date although is not fixed and we will wait for more details until we will fix a date but currently it looks like it will be August. We will try to prepare everything (without signing contracts) to be ready to announce a date as soon as we are confident with one. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== No current events Future Events ============= TAC has an events Calendar that it shares with other Committees for the purposes of cross-committee planning and collaboration. Currently filled our up until October. Due to the cancellation of many events, currently the next supported event will be ApacheCon New Orleans. Any ASF Project putting on a Hackathon and/or Meetup should also talk to TAC about supporting them getting folks there (Committers and Non Committers) Short Term Priorities ===================== We are looking into creating a new webapp, one that is independent on the reliance of one or two volunteers, that can be maintained and serve TACs needs for the next few years. The webapp would need to be ready and tested before applications open for the next event. Long Term Priorities ==================== Be ready for applications open for ApacheCon NA, applications should be open by early June. Mailing List Activity ===================== No list activity since the previous report. Membership ========== No changes to the TAC membership since the last report. ----------------------------------------- Attachment 7: Report from the VP of Finance [Tom Pappas] VP Finance Feb 2020 report Continue to work and assist Fundraising Worked and assisted the DC Roadshow with logistics and insurance Worked with the Seattle Roadshow on logistics Continued to work with EVP on FY 21 Budget ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Gris Cuevas] [Outreachy activity report missing, will update once it's in] ## 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: *** Project: Survey revamp*** Work on the report was completely paused this month due to V.P.'s bandwidth, looking to resume next week. *** Project: User Experience Research on new contributors *** Work was completely paused this month due to V.P.'s bandwidth, looking to resume next week. *** Project: Internships for underrepresented groups (Outreachy) *** There's 1 new edit on your page page icon Diversity & Inclusion - Board Reports Katia Rojas edited this page Here's what changed: ... *** Project: Internships for underrepresented groups (Outreachy) *** The first Outreachy program round has been concluded. The friction log has been sent to the intern and two co-mentors. We set a reminder to get the friction log from intern and mentors. Friction log templates have been filled up by mentors and mentee. We are going to analyze the information of the friction log to improve the current process and experience in the Outreachy program. We've got 3 projects for the second round of the Outreachy program: May-August 2020: - Extend & Improve Apache Airflow REST API 2020 May to 2020 August round - - Improve Apache Camel website 2020 May to 2020 August round - Improve the UI of Apache Airflow 2.0 Contribution period is open: March 5,2020 to April 7, 2020 We are working to create a FAQ page for the Outreachy program. [2] ## Health report: The dev@ and diversity@ mailing lists continue to be slow, not too much activity outside the work done for each ongoing project. The discussions have been focused on topics that pertain to the projects we are running. ## Committee members changes: None. ## References [1] https://www.outreachy.org/communities/cfp/apache/ [2] Outreachy FAQ ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Dirk-Willem van Gulik] Operational: First genuine GDPR request (removal) handled; but actual governance & long term recording not yet sorted properly (e.g. making sure that the details of this request are automatically purged when they hit delaware record law limits, etc). Strategic: Not made as much progress as I wanted - largely due to the chair (personally) being swamped & not enough delegation. The latter should become unstuck as we start creating deliverables. Next: Define these deliverables/plan; find 3-6 volunteers for the operational part & write down SOPs; talk to infra to figure out what is practically possible around retention. ----------------------------------------- Attachment 10: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 11: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] For the past months we've had a regular amount of usual requests flowing through LEGAL JIRA and legal-discuss. Hen and the rest of the volunteers took a good care of resolving most of these in time. We're down 2 (to 20), unresolved issues this month. Henri Yandell has indicated that he may want to step in to replace Mark Struberg as VP Jakarta EE Relations. With renewed involvement, hopefully we can finalize discussions with the Eclipse Foundation. Due to recent global events, progress on various binary distribution channels that ASF controls is slow, but it is still on my radar. DLA Piper started to review our by-laws. We reviewed (and approved with modifications) an Associated Partner contract text from the KNX Association (LEGAL-509) and also Bylaws of the OPC Foundation (LEGAL-508). ----------------------------------------- Attachment 12: 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. This month saw an issue in Tomcat CVE-2020-1938 which gained press interest when it was given branding and a name and was disclosed by a third-party co-ordination centre before Tomcat released an advisory (although after the issue was fixed in new releases of Tomcat). Although serious if exploited, it only affected Tomcat installations which exposed an unprotected AJP Connector to untrusted networks (which is already not a good thing to do even without this issue). That limits the number of affected installations. Stats for Feb 2020: 20 [license confusion] 26 [support request/question not security notification] Security reports: 23 (last months: 40, 23, 31, 29) 6 [dubbo] 5 [site] 2 [tika] 1 [asterixdb], [cloudstack], [guacamole], [httpd], [iotdb], 1 [logging], [openwhisk], [sling], [spamassassin], [tomcat] In total, as of 1st March 2020, we're tracking 52 (last month: 53) open issues across 30 projects, median age 81 (last month: 69) days. 37 of those issues have CVE names assigned. 6 (last month: 4) of these issues, across 3 projects, are older than 365 days. None require escalation. ----------------------------------------- Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg] ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: The mission of Apache Airflow is the creation and maintenance of software related to workflow automation and scheduling that can be used to author and manage data pipelines ## Issues: Due to Corona virus concerns the first ever Airflow Summit was delayed until further notice. ## Membership Data: Apache Airflow was founded 2018-12-19 (a year ago) There are currently 30 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Kengo Seki on 2019-12-01. - Tomasz Urbaszek was added as committer on 2019-12-20 ## Project Activity: 1.10.9 was released on 2020-02-07 (quick fix release). 1.10.8 was released on 2020-02-07. 1.10.7 was released on 2019-12-24. ## Community Health: We have a very healthy community with lots of activity. Apache Airflow jobs rank 4 for data engineering jobs. Airflow's Slack channels are active. dev@airflow.apache.org had a 12% increase in traffic in the past quarter (823 emails compared to 733) users@airflow.apache.org had a 115% increase in traffic in the past quarter (198 emails compared to 92) 801 issues opened in JIRA, past quarter (6% increase) 654 issues closed in JIRA, past quarter (35% increase) 1607 commits in the past quarter (36% increase) 199 code contributors in the past quarter (11% increase) 910 PRs opened on GitHub, past quarter (7% increase) 944 PRs closed on GitHub, past quarter (12% increase) ----------------------------------------- Attachment B: Report from the Apache Allura Project [David Philip Brondsema] ## Description: Apache Allura is an open source implementation of a software forge, a web site that manages source code repositories, bug reports, discussions, wiki pages, blogs, and more for any number of individual projects. ## Issues: - No issues needing board attention. ## Project Activity: - A new contributor's large merge request has been merged. It adds a new tool for project ratings. - Another new contributor has been working on forum imports and making good progress - Getting to the final steps for supporting Python 3 ## Community Health: - Development has been a bit better than previous quarters, due to activity noted above. - A few questions from from end-users/admins on mailing list ## Membership Data: - Last PMC addition: Sun Oct 28 2018 (Shalitha Suranga) - Currently 15 PMC members. - Last committer addition: Mon Oct 29 2018 (Shalitha Suranga) - Currently 15 committers. ## Releases: - 1.12.0 was released on 2019-10-04 ----------------------------------------- Attachment C: Report from the Apache Ambari Project [Jayush Luniya] ## Description: The mission of Apache Ambari is the creation and maintenance of software related to Hadoop cluster management ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: - Apache Ambari was founded 2013-11-19 (6 years ago) - There are currently 106 committers and 48 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 Ishan Bhatt on 2018-10-25. - No new committers. Last addition was Masahiro Tanaka on 2019-11-07. ## Project Activity: Recent releases: - 2.7.5 was released on 2019-12-16. - 2.7.4 was released on 2019-09-13. - 2.7.3 was released on 2018-11-17. ## Community Health: - Many committers and PMC members have moved to other projects. We plan to add 3 new PMC members and 2 new committers soon to take ownership and drive the project forward. - 45 issues opened in JIRA, past quarter. - 61 issues closed in JIRA, past quarter. - 15 commits in the past quarter. - 10 code contributors in the past quarter. - 28 PRs opened on GitHub, past quarter. - 17 PRs closed on GitHub, past quarter. ----------------------------------------- Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Any23 was founded 2012-08-27 (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 Hans Brende on 2018-02-25. - No new committers. Last addition was Hans Brende on 2018-02-21. ## Project Activity: Project activity has actually been very low indeed! No dev@ work has been logged in JIRA since 2019-10-17. Put simply, the project is going through a very quiet period indeed. In October of 2019 the PMC was actually working on a release... this stalled as there were several Spotbugs issues which were being worked on. That work did not finished so the release was never finished. The next steps are for that work to resume and for the project to make a formal release. Right now, no plan is in place for when that will be! ## Community Health: Although the community is not growing, as of Oct 2019, the small community was responsive and quite eager to see a release. Once work is completed on the Spotbugs issues and we make a release we will hopefully see a bit of community activity as we roll out application upgrades. ----------------------------------------- Attachment E: Report from the Apache Archiva Project [Olivier Lamy] ## Description: The mission of Archiva is the creation and maintenance of software related to Build Artifact Repository Manager ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Archiva was founded 2008-03-19 (12 years ago) There are currently 21 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - No new PMC members. Last addition was Martin Stockhammer on 2017-04-10. - No new committers. Last addition was Martin Stockhammer on 2016-09-22. ## Project Activity: Activity was very low focused on some refactoring and fixing issues with Windows environment ## Community Health: * dev@archiva.apache.org had a 20% increase in traffic in the past quarter (18 emails compared to 15) * issues@archiva.apache.org had a 42% decrease in traffic in the past quarter (24 emails compared to 41) * 4 issues opened in JIRA, past quarter (-42% decrease) * 2 issues closed in JIRA, past quarter (-66% decrease) * 131 commits in the past quarter (-12% decrease) * 5 code contributors in the past quarter (25% increase) * 7 PRs opened on GitHub, past quarter (16% increase) * 8 PRs closed on GitHub, past quarter (300% increase) ----------------------------------------- Attachment F: Report from the Apache Atlas Project [Madhan Neethiraj] ## Description: Apache Atlas is a scalable and extensible set of core foundational governance services that enables enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the complete enterprise data ecosystem ## Issues: There are no issues requiring board attention at this time. ## Activity: - performance improvements in lineage, tag-propagation - new feature to support business metadata - updated authorization model to support operations on labels, business-metadata - performance improvements in import functionality - updated JanusGraph version to 0.4.1, and Tinkerpop version to 3.4.4 - added updated entity models for AWS S3 - added entity models for ADLS-Gen2 - search enhancements to support system-attributes, business-attributes - working towards release of Apache Atlas 2.1, by end of March-2020 ## Health report: - 2 new contributors added in last 3 months: Pinal Shah, Sourav Banerjee ## PMC changes: - Currently 34 PMC members - Last addition to PMC role was on 5/13/2019 ## Committer base changes: - Currently 38 committers - No new committers added in last 3 months - Last addition to committer role was on 10/15/2018 ## Releases: 0.8.4 was released on 06/21/2019 1.2.0 was released on 06/12/2019 2.0.0 was released on 05/14/2019 0.8.3 was released on 10/31/2018 1.1.0 was released on 09/17/2018 1.0.0 was released on 06/02/2018 0.8.2 was released on 02/05/2018 1.0.0-alpha was released on 01/25/2018 0.8.1 was released on 08/29/2017 0.8-incubating was released on 03/16/2017 0.7.1-incubating was released on 01/26/2017 0.7-incubating was released on 07/09/2016 0.6-incubating was released on 12/31/2015 0.5-incubating was released on 07/11/2015 ----------------------------------------- Attachment G: Report from the Apache Axis Project [Robert Lazarski] # Apache Axis Board Report ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues There are no issues requiring board attention at this time. ## Membership Data: Axis was created on 2001-01-19 (19 years ago). There are currently 63 committers and PMC members in this project, a vote in 2010 made all committers automatically PMC members. Community changes, past quarter: - Currently 63 PMC/Commiters members. - No new committers were added in the last 90 days, last committer added was Bill Blough on December 7th 2017 who also was added to the PMC on May 9th 2018. ## Project Activity: Recent releases: - Axis 2/Java 1.7.9 was released on November 16, 2018. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## Health report: We have enough PMC to cut releases. Axis2 is a mature project, but still actively maintained. There continued to be light but consistent traffic of new users this past quarter on the Axis2 Java users mailing list. While best known for SOAP, the future of Axis2 Java is with JSON and REST. AXIS2-5943 applied some JSON message related bug fixes and fixes for the JSON samples. Also, docs were added on how to send JSON via Curl as an HTTP client for REST based web services. The goals for the next Axis2 Java release continue to be JDK 11 support, by removing the remaining deprecated com.sun dependencies from the code base. Time was spent this past quarter on trying to get the nightly builds via Travis working again - which depend on github syncing with our svn repo but that stopped working. Discussions about our Github future (with 3+ PMC members) are currently occurring on java-dev@axis.apache.org. Axis2 C PMC member Bill Blough was "in the middle of making some bugfixes/improvements to the build system" this past quarter. The communication continues to be good. ## JIRA Activity for Axis2 java - 3 JIRA tickets created in the last 90 days. - 3 JIRA tickets closed/resolved in the last 90 days. ----------------------------------------- Attachment H: Report from the Apache Bahir Project [Luciano Resende] ## Description: Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Currently, Bahir provides extensions to multiple distributed analytic platforms, extending their reach with a diversity of streaming connectors and SQL data sources. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Bahir was founded 2016-05-17 (4 years ago) There are currently 40 committers and 11 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 Prashant Sharma on 2018-10-19. - No new committers. Last addition was Łukasz Antoniak on 2019-01-21. ## Project Activity: Apache Bahir community continues to see a steady medium flow of contributions enhancing the existing extensions for both Apache Spark and Apache Flink. There is a need to produce a new release of the Flink extensions but work has not started by the community. There is also a need to catch up on Spark extensions release. ## Community Health: ### JIRA activity: 6 issues opened in JIRA, past quarter (100% increase) 3 issues closed in JIRA, past quarter (200% increase) ### Committs activity: 15 commits in the past quarter (114% increase) 6 code contributors in the past quarter (100% increase) ## Trademark/Branding * No known issues. ## Legal Issues * None ----------------------------------------- Attachment I: Report from the Apache Beam Project [Kenneth Knowles] ----------------------------------------- Attachment J: Report from the Apache Bigtop Project [Jun He] ## Description: Bigtop is a project for the development of packaging and tests of the Apache Hadoop ecosystem. The primary goal of Bigtop is to build a community around the packaging and interoperability testing of Hadoop-related projects. This includes testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. In short we strive to be for Hadoop what Debian is to Linux. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Bigtop was founded 2012-09-19 (7 years ago) There are currently 37 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Jun He on 2018-11-25. - No new committers. Last addition was Jun He on 2018-02-23. ## Recent releases - 1.4.0 was released on 2019-06-15. ## Project Activity: - Bigtop community is actively working on v1.5.0 release. Kengo Seki volunteered as release manager. This release includes components bumping up and new Linux distros support. It is in good progress. - Several new contributors (a few from Wikimedia) get involved and are driving the dev momentum. - Jun He was elected as the new PMC chair. ## Community Health: - Community health is good. Discussions and commits have increased along with v1.5 release in progress: - dev@bigtop.apache.org had a 83% increase in traffic in the past quarter (342 emails compared to 186) - issues@bigtop.apache.org had a 36% increase in traffic in the past quarter (329 emails compared to 241) - 41 PRs opened on GitHub, past quarter (24% increase) - 29 PRs closed on GitHub, past quarter (11% increase) - Regularly recived bug reports/feature requests/PRs from user and community members ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] ----------------------------------------- Attachment L: Report from the Apache BVal Project [Matthew Jason Benson] ----------------------------------------- Attachment M: Report from the Apache Camel Project [Andrea Cosentino] ## Description: Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (11 years ago) There are currently 70 committers and 35 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Volodin on 2019-05-08. - Gazda was added as committer on 2020-03-02 ## Project Activity: - We released Apache Camel 3.0.1 on 16 Jan 2020 - We released Apache Camel 3.1.0 on 27 Feb 2020 - We are already working on a patch release for 3.1.x and we'll release 3.1.1 in the next quarter - We are working already on the 3.2.0 version too. - Actually we are doing a big effort on stabilizing the codebase for 3.x branch, there is an ongoing effort and a lot of activity and contributions from old and new contributors - We released a new 2.x version, the 2.24.3 on 26 Dec 2019. - We released also the 2.25.0 version, on 23 Jan 2020, which will be the last major release supported on Camel 2.x - We are preparing for the next minor release Apache Camel 2.24.4 and the first patch release for 2.25.x - We released Camel-K-Runtime 1.0.9 and 1.1.0 respectively on 19 Dec 2019 and 24 Feb 2020 - We released Camel-K 1.0.0-RC1 and Camel-K 1.0.0-RC2 respectively on 24 Dec 2019 and 28 Feb 2020 - We are continuing our work on Camel-K by improving the support for Camel 3 and we plan to release a GA soon after the RC candidates will have more feedback. - We are continuing supporting Camel-Quarkus by releasing multiple versions in this quarter - We released the following Camel-Quarkus versions: - 1.0.0-M2 on 17 Dec 2019 - 1.0.0-M3 on 24 Jan 2020 - 1.0.0-M4 on 06 Mar 2020 - We are continuing working on the Camel-kafka-connector project to be able to release a first version in the coming months - This is the complete releases list - 3.0.1 was released on 2020-16-01 - 3.1.0 was released on 2020-27-02 - 2.25.0 released on 2020-23-01 - 2.24.3 released on 2019-26-12 - Camel-K 1.0.0-RC1 released on 2019-12-24 - Camel-K 1.0.0-RC2 released on 2020-02-245 - Camel-Quarkus 1.0.0-M2 released on 2019-12-17 - Camel-Quarkus 1.0.0-M3 released on 2020-01-24 - Camel-Quarkus 1.0.0-M4 released on 2020-03-06 - This year Apache Camel will participate to Google Summer Of Code: we have already some student proposals we are evaluating and we are giving feedback to them. Actually we have 5 students interested. - This year Apache Camel will participate to Outreachy program: We have already a lot of requests for contributing and getting started. Really nice. More info: https://camel.apache.org/blog/Outreachy-May2020/ ## Community Health: - dev@camel.apache.org had a 56% decrease in traffic in the past quarter (663 emails compared to 1505) This is related to the first Camel 3 GA release - users@camel.apache.org had a 15% increase in traffic in the past quarter (514 emails compared to 445) This is related to the questions coming in about migration from camel 2 to 3 - 388 issues opened in JIRA, past quarter (+21% increase) This is because we created new issues for improvements and new stuff on Camel 3 branch - 329 issues closed in JIRA, past quarter (+4% decrease) This is because we were focusing on existing issues too - 3450 commits in the past quarter (+28% decrease) This is for the new features and some refactoring done in 3.1.0 - 545 PRs opened on GitHub, past quarter (-12% decrease) This is for the stabilization, so feature contributor are continuing to work on them - 556 PRs closed on GitHub, past quarter (-10% decrease) This is for the stabilization, so feature contributor are continuing to work on them - 284 issues opened on GitHub, past quarter (9% increase) This is for the new projects in the ecosystem, we are noticing more contributors and obviously more issue - 195 issues closed on GitHub, past quarter (-13% decrease) This is because there are ongoing issue still to resolve ----------------------------------------- Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry] # Apache Cayenne Board Report, March 2020 ## Description Apache Cayenne is a Java database persistence framework. It takes a distinct approach to object persistence and provides an ORM runtime, remote persistence services, and a cross-platform GUI database mapping/modeling tool. ## Issues There are no issues requiring board attention at this time. ## Membership Data Apache Cayenne was founded 2006-12-19 (13 years ago). There are currently 23 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Nikita Timofeev on 2017-06-25. - No new committers. Last addition was Arseni Bulatski on 2018-12-10. ## Project Activity Development is focused on Cayenne 4.1 and 4.2. Prior versions are maintenance-only. - Cayenne 3.1.3 (aging) - Maintenance only. - Cayenne 4.0.2 (stable) - Maintenance only. - Cayenne 4.1.RC2 (beta) - Expecting to release Cayenne 4.1 as soon as final bugs are fixed and tested. - Cayenne 4.2M1 (development) - Most development work is focused on this version. ### Releases - Cayenne 3.1.3 on 2018-07-25. - Cayenne 4.0.2 on 2019-10-14. - Cayenne 4.1.RC2 on 2019-10-29. ## Community Health Cayenne is healthy. Development activity is stable and and we have a stable user and developer community. ### Mailing List Activity - dev@cayenne.apache.org had a 70% decrease in traffic in the past quarter (18 emails compared to 60). - user@cayenne.apache.org had a 65% decrease in traffic in the past quarter (34 emails compared to 96). Mailing list traffic decrease is hopefully due to fewer issues being discovered with the 4.1 RC release. ### JIRA and GitHub Activity - 8 issues opened in JIRA, past quarter (-68% decrease). - 7 issues closed in JIRA, past quarter (-50% decrease). - 37 commits in the past quarter (-76% decrease). - 2 code contributors in the past quarter (-33% decrease). - 7 PRs opened on GitHub, past quarter (75% increase). - 4 PRs closed on GitHub, past quarter (400% increase). JIRA and GitHub activity likely reflects the mailing list activity with fewer issues arising from the 4.1 RC release. ----------------------------------------- Attachment O: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Chemistry was founded 2011-02-16 (9 years ago) There are currently 38 committers and 36 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Laurent Mignon on 2017-09-23. - No new committers. Last addition was Laurent Mignon on 2017-09-20. ## Project Activity: There was little activity in the last three months. We got requests make a new release of OpenCMIS with basically no code change but updated dependancies. We are looking into it. Last releases were in 2017. ## Community Health: We have a mature code base. No major development is expected. ----------------------------------------- Attachment P: Report from the Apache CloudStack Project [Paul Angus] ## Description: The mission of CloudStack is the creation and maintenance of software related to Infrastructure as a Service solution ## Issues: No issues to report. ## Membership Data: Apache CloudStack was founded 2013-03-20 (7 years ago) There are currently 121 committers and 51 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 Nathan Johnson on 2019-07-17. - No new committers. Last addition was Dennis Konrad on 2019-03-19. ## Project Activity: - A large cross-community project to create a new UI for CloudStack is nearing completion. - The next new release of CloudStack (4.14) should reach code freeze on 13th March. This has been delayed due to the number of major new features that will come with it. - The PMC has voted for their next Chair (Sven Vogel), a resolution to this effect has been put forward to the board for the next meeting. - Work has begun on updating the CloudStack Collaboration Conference website to reflect its presence at this year's ApacheCon NA in new orleans. ## Community Health: Community health is good (some new committers would be nice). There is a lot of development activity wrt new features as well as closing issues and PRs. Taking into account reduced user activity over the winter break, stats look good (to me). - dev@cloudstack.apache.org had a 68% increase in traffic in the past quarter (1177 emails compared to 699) - issues@cloudstack.apache.org had a 66% increase in traffic in the past quarter (10 emails compared to 6) - marketing@cloudstack.apache.org had a 65% decrease in traffic in the past quarter (15 emails compared to 42) - users@cloudstack.apache.org had a 36% decrease in traffic in the past quarter (247 emails compared to 383) - users-cn@cloudstack.apache.org had a 30% decrease in traffic in the past quarter (7 emails compared to 10) - 2 issues opened in JIRA, past quarter (no change) 163 commits in the past quarter (36% increase) - 32 code contributors in the past quarter (45% increase) - 134 PRs opened on GitHub, past quarter (8% increase) - 192 PRs closed on GitHub, past quarter (106% increase) - 70 issues opened on GitHub, past quarter (-13% decrease) - 80 issues closed on GitHub, past quarter (321% increase) ----------------------------------------- Attachment Q: Report from the Apache Cocoon Project [Cédric Damioli] ## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (17 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: I don't really understand why the report last month was flagged as 'minimal' and 'last-minute report'. The report was approved by the PMC and IMHO there was nothing more to say. Project's activity is obviously low, but answers are given quickly when required. The most recent release is 2.1.12 on 2013-03-14 The project is mainly in maintenance mode. ## Community Health: Still very few activity on the project. Still active PMC members around here. There was some activity on users list showing that the branch 2.2 is still in use, while all activity was previously mainly on branch 2.1 ----------------------------------------- Attachment R: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The mission of Apache Commons is the creation and maintenance of Java focused reusable libraries and components ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Commons was founded 2007-06-19 (13 years ago) There are currently 149 committers and 38 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 Alex Herbert on 2019-05-09. - Matt Juntunen was added as committer on 2020-03-09 ## Project Activity: We have released the following Apache Commons Components: - CONFIGURATION-2.7 was released on 2020-03-11. - COMPRESS-1.20 was released on 2020-02-08. - CSV-1.8 was released on 2020-02-06. - VFS-2.6.0 was released on 2020-01-09. - CODEC-1.14 was released on 2020-01-03. - VFS-2.5.0 was released on 2019-12-28. - PARENT-50 was released on 2019-12-17. ## Community Health: The community is active despite a drop in mailing list statistics. The number of Jira tickets open is up though. ----------------------------------------- Attachment S: Report from the Apache Cordova Project [Jesse MacFadyen] ## Status report for the Apache Cordova project - March 2020 ## Description: - A platform for building native mobile applications using HTML, CSS and JavaScript. ## Activity - We are still working out the details for how to use last years donation to hire someone to update our documentation and author some getting started guides. We have started an issue thread: https://github.com/apache/cordova-docs/issues/1057 and welcome input/guidance from Apache. ## Issues: - There are no issues requiring board attention at this time. ## Health report: Our status dashboard at http://status.cordova.io is mostly all green - failures are usually due to external service issues that do device testing. Our nightly builds have been extremely stable. We are still working to resolve all existing issues in JIRA while also maintaining all the new issues and pull requests in Github. ## PMC changes: - Currently 99 PMC members. - Niklas Merz was added to the PMC on 2019-12-26 ## Committer base changes: - Currently 102 committers - Niklas Merz was added to committers on 2019-12-26 ## Releases: - cordova-plugin-inappbrowser@3.2.0 was released on 2020-01-08. - cordova-windows@7.0.1 was released on 2020-01-06. - cordova-node-xcode@2.1.0 was released on 2019-12-24. ## JIRA activity: - 0 JIRA tickets created in the last quarter (JIRA has been shut down) - 11 JIRA tickets closed/resolved in the last quarter ## Github activity: Issue close rate of 57%: - 233 issues opened on GitHub, past quarter - 134 issues closed on GitHub, past quarter PR close rate of 95%: - 136 PRs opened on GitHub, past quarter - 130 PRs closed on GitHub, past quarter ----------------------------------------- Attachment T: Report from the Apache cTAKES Project [Pei Chen] ## Description: Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is an open-source natural language processing system for information extraction from electronic medical record clinical free-text. ## Issues: There are no issues requiring board attention at this time. ## Project Activity: - Committee continues to work on the future release (4.0.1) - Committee continues to work on bug fixes and improvements documented in Jira ## Health report: - The community continues to be moderately active. - There are new questions/suggestions from new users on the mailing lists - There is steady increase in interest and growth in the community based on the activity on the mailing lists ## Membership Data: - Currently 31 PMC members. - Last PMC addition was Gandhi Rajan on Thu Jul 12 2018 ## Committer base changes: - Currently 38 committers. - Last committer addition was Gandhi Rajan at Tue Nov 14 2017 ## Releases: - Last release was 4.0.0 on Thu Apr 27 2017 - 3.2.2 was released on May 30 2015 - 3.2.1 was released on Dec 10 2014 ## Community Health: Overall community health is good. dev@ctakes.apache.org had a 28% increase in traffic in the past quarter (58 emails compared to 45) ----------------------------------------- Attachment U: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: The mission of Curator is the creation and maintenance of software related to Java libraries that make using Apache ZooKeeper easier ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Curator was founded 2013-09-17 (6 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 Shay Shimony on 2019-04-17. - No new committers. Last addition was Shay Shimony on 2019-04-18. ## Project Activity: - Interest in Curator has increased recently matching the increased activity from new committers in ZooKeeper. - We have two new releases planned: - 4.3.0 is a bug fix release being voted on right now and will hopefully be released soon - A possible 5.0.0 is being worked on to make Curator compatible with the upcoming 3.6.0 release of ZooKeeper - The Curator team is working on a number of things: - Some important bug fixes were merged from the community for 4.3.0 - Refactoring and removing a bunch of cruft/tech debt for upcoming 5.0.0 - Added new features to support corresponding ZooKeeper 3.6.0 features ## Recent Releases - Apache Curator 4.2.0 was released on 2019-03-06. - Apache Curator 4.3.0 is being voted on right now and will be released as soon as the community accepts this version - We have plans for Curator 5.0.0 sometime in 2020 ## Community Health: Curator is healthier than it has been in a while. We now have 3 active committers who are engaged. We also get regular input from community members with bug reports, PRs, etc. We still need more active engagement from the community, however. Given how widely used Curator is it can be frustrating that there aren't more people active in the project. We continue to reach out in various forums: Apache Slack, email, Stackoverflow, etc. ----------------------------------------- Attachment V: Report from the Apache DRAT Project [Tom Barber] ## Description: The mission of Apache Distributed Release Audit Tool is the creation and maintenance of software related to large scale code license analysis, auditing and reporting. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache DRAT was founded 2017-09-19 (2 years ago) There are currently 14 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Ahmed Ifhaam on 2018-08-30. - No new committers. Last addition was Ahmed Ifhaam on 2018-08-28. ## Project Activity: There’s not much going on since we were stalled a bit on the 1.0 release since it was complicated and involved some bits and pieces from OODT. There are still at least 3 active folks (Mattmann, Tom Barber, and Imesha, for one), so I think we’re just slowly moving along. ## Community Health: The project is a slow project, and intrinsically tied to OODT in many ways. 1.0 is basically done, we were just trying to pin it to a version of OODT that didn't rely on Avro and still used XML-RPC (for now) and then upgrade to Avro later. There is sufficient oversight and still enough people that care we just move slow. ----------------------------------------- Attachment W: 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 hard at work preparing to create a branch for our 2nd post-graduation release, 0.18.0, expected to be done within the next week, targeting a release by the end of the month. 0.18.0 is currently weighing in at over 200 commits from 41 contributors since our last release on Jan 26 2020. In-person meetups and events have always been an important part of the Druid community, but given the current global COVID-19 situation, they have become untenable. Druid Summit, a larger event, was originally planned for April 13-15 and has recently been postponed to November 2-4. We are also investigating alternatives to the smaller local meetups (typically 20-50 people) that we had been planning for New York City, Orange County, and San Diego over the next two months. ## Recent PMC changes - Currently 27 PMC members. - No recent changes to PMC. ## Recent committer changes - Currently 35 committers. - No recent changes to committers. ## Recent releases - 0.17.0, our first release post graduation was released on Jan 26 2020 ## Development activity by the numbers In the last month: - 69 pull requests opened - 67 pull requests merged/closed - 56 issues opened - 30 issues closed - 275 comments on pull requests - 147 comments on issues ----------------------------------------- Attachment X: Report from the Apache Eagle Project [Edward Zhang] ## Description: The mission of Apache Eagle is the creation and maintenance of software related to a distributed monitoring solution for identifying security and performance issues in real time on big data platforms, including Apache Hadoop and Apache Spark. ## Issues: There are no issues requiring board attention ## Membership Data: Apache Eagle was founded 2016-12-20 (3 years ago) There are currently 18 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 9:8. Community changes, past quarter: - No new PMC members. Last addition was Deng Lingang on 2017-05-08. - No new committers. Last addition was Jay Sen on 2017-03-16. ## Project Activity: Project refactoring has not started since PMCs discussed the new design a few months back. Hopefully we can come up with some jira stories for the project refactoring in coming months. The idea is still to remove hbase dependency, and remove hadoop specific monitoring and make the monitoring framework more generic. ## Community Health: There is no much activity from community in last 3 months. Hopefully after we started development of the new design, community would have more feedback and interactions. ----------------------------------------- Attachment Y: Report from the Apache Felix Project [Karl Pauls] ## Description: Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Felix was founded 2007-03-28 (13 years ago) There are currently 68 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Georg Henzler on 2019-06-10. - Stefan Bischof was added as committer on 2020-03-02 ## Project Activity: - Existing implementations have been improved/enhanced based on community feedback. - We did migrate from svn to git(box) and started reorganising around git repositories (including a rework of our website to reflect the changes). - We are discussing breaking out some of our bigger subproject into additional git repositories. - We accepted and integrated the "Atomos" contribution by Thomas Watson and attracted a new committer in the process (Stefan Bischof). - Released 3 components (mostly bug fixes overall). ## Releases: - org.apache.felix.configadmin.plugin.interpolation-1.1.0 was released on 2020-03-02. - maven-scr-plugin-1.26.2 was released on 2019-12-07. - org.apache.felix.scr.bnd-1.9.6 was released on 2019-12-07. - org.apache.felix.scr.bnd-1.9.4 was released on 2019-12-07. ## Community Health: - Overall the project is in ok health. - Questions on the user list are answered, development concerns are either discussed on the mailing list or directly in the JIRA issues. - The project as well as the OSGi community in general is still in the process of adapting to JPMS and Graal/substrate - however, we hope that Atomos and the new OSGi Connect RFC will help in that area. - We need to be on the lookout for new committers. Atomos and the move to github hopefully will help in attracting more people. - We had no issues voting on releases and JIRA issues are generally addressed. - dev@felix.apache.org had a 30% decrease in traffic in the past quarter (292 emails compared to 415) - We had relatively (for us) few releases this quarter. At least in parts, that accounts for some of the decrease in traffic on the dev list. - users@felix.apache.org had a 166% increase in traffic in the past quarter (8 emails compared to 3) - 30 issues opened in JIRA, past quarter (11% increase) - 24 issues closed in JIRA, past quarter (33% increase) - 19 commits in the past quarter (-47% decrease) - 4 code contributors in the past quarter (-42% decrease) - 9 PRs opened on GitHub, past quarter (-30% decrease) - 14 PRs closed on GitHub, past quarter (133% increase) ----------------------------------------- Attachment Z: Report from the Apache Flex Project [Olaf Krüger] ## Description: Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. Because the FlashPlayer reaches its EOL at the end of 2020, we won't be able to target the browser with Flex after 2020. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Flex was founded 2012-12-19 (7 years ago) There are currently 69 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Olaf Krüger on 2017-08-28. - No new committers. Last addition was Greg Dove on 2016-09-07. ## Project Activity: The latest AIR update breaks Flex. The community is discussing how to fix this issue. ## Community Health: Even the daily mailing list activity is decreasing, users still come back when issues needs to be resolved. ----------------------------------------- Attachment AA: Report from the Apache Flink Project [Stephan Ewen] ## Description: Apache Flink is a distributed data streaming system for batch and streaming data analysis on top of a streaming dataflow engine. Flink's stack contains functional batch and streaming analysis APIs in Java, Scala, Python, and libraries for various use cases. Flink interacts and integrates with several Apache projects in the broader ecosystem of data storage and computing, such as Apache Beam, Calcite, Hadoop, Mesos, Kafka, HBase, Cassandra, and various others. ## Issues: - There are no community issues that require board attention. ## Membership Data: No new PMC members were added since the last report. Committers added since the last board report: - Yu Li was added as committer on January 7th, 2020 - Dian Fu was added as committer on January 17th, 2020 - Jingsong Lee was added as committer on February 2nd, 2020 The newest PMC member is Jark Wu, joined on November 8th, 2019. The newest committer is Jingsong Lee, joined on February 2nd, 2020. There are currently 55 committers and 26 PMC members in this project. ## Releases The following releases were made since the last board report: - Flink 1.9.2 was released on January 31st, 2020. - Flink 1.10.0 was released on February 11th, 2020. - Flink Shaded 10.0 (vendored libraries) was released on February 17th, 2020 ## Project Activity: - The community has released Flink 1.10, a big release with many features, notably easier memory configuration, Python functions, an active Kubernetes integration, integration with Hive and fulls TPC-DS coverage in SQL. - The ASF has registered Flink as a trademark for the EU and China regions now. Flink was already registered as a trademark in the US. - The contributed Stateful Functions project is on its way to its first release under its new home in the Flink community. Code and documentation has been successfully migrated, discussions are ongoing about updating the presentation of the website to better reflect the Flink project's evolution. - The Flink Forward community conference has been canceled due to the Covid-19 outbreak, and the organizers are exploring options to have an online event instead. - Discussions about the 1.11 release have been started by the designated release managers. - The community is exploring a "developer blog" to better exchange information about internals of the system and project between contributors, that might not be very relevant or interesting to most users. ## Community Health: The mailing list activity remains stable on a high level. - user@f.a.o (2027 mails/quarter) - user-zh@f.a.o (706 mails/quarter) - dev@f.a.o (2997 mails/quarter) JIRA continues to be very active as well, 1315 JIRA tickets created, 843 JIRA tickets closed in the last 3 months. ----------------------------------------- Attachment AB: Report from the Apache Flume Project [Ferenc Szabo] ## Description: The mission of Flume is the creation and maintenance of software related to a reliable service for efficiently collecting, aggregating, and moving large amounts of log data ## Issues: The Flume PMC Chair is no longer responding to emails. It has been confirmed that he left his employer several months ago where he was employed to maintain Flume. The PMC has confirmed that there are at least 6 people monitoring the mailing lists, ## Membership Data: Apache Flume was founded 2012-06-19 (8 years ago) There are currently 32 committers and 24 PMC members in this project. However at most 18 people are subscribed to the private list. As noted above, 6 of the 18 responded to a query to determine how many were still participating. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Ferenc Szabo on 2019-01-27. - Tristan Stevens was added as committer on 2020-01-06 ## Project Activity: The project has a slow but steady activity. Jira issues and Pull Request are being creating and addressed. ## Community Health: The last Flume release was January 2, 2019. The PMC needs to elect a new PMC chair but a vote has not yet begun. ----------------------------------------- Attachment AC: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: - The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key-value stores, document stores, distributed in-memory key-value stores, in-memory data grids, in-memory caches, distributed multi-model stores and hybrid in-memory architectures. Gora also enables analysis of data with extensive Apache Hadoop MapReduce, Apache Spark, Apache Flink, and Apache Pig support. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Gora was founded 2012-01-24 (8 years ago) There are currently 30 committers and 30 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Sheriffo Ceesay on 2019-10-01. - No new committers. Last addition was Sheriffo Ceesay on 2019-10-01. ## Project Activity: - Except for several bug fixes, improvements and a security fix while considering development work, it has been a fairly quiet quarter for us. - Several members of Gora PMC have volunteered to be mentors for this years GSoC to increase community participation. - There were several contributions from external people and we are also in process of inviting one potential contributor for Gora PMC / Committership once his major contributions are merged. ## Community Health: - Our main communication medium gora development mailing lists were mostly quiet for past quarter. We believe this is mainly due to holidays period. We are hoping to bring some energy with GSoC and new development drive work for the next release. However we could also observe some level of JIRA and Github related activity for past quarter. ----------------------------------------- Attachment AD: Report from the Apache Guacamole Project [Mike Jumper] ## Description: The mission of Apache Guacamole is the creation and maintenance of software related to providing performant, browser-based remote access ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Guacamole was founded 2017-11-14 (2 years ago) There are currently 14 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Carl Harris on 2017-11-19. - Luke was added as committer on 2020-02-07 - Sean Reid was added as committer on 2020-02-07 ## Project Activity: With 1.1.0 having been released, focus has shifted to the next release (1.2.0) and to producing more frequent releases in general. Scope of the 1.2.0 release has been settled, though flexibility in scope is being allowed for regressions related to the two major migrations that were part of 1.1.0 (FreeRDP 2.0.0 and the Apache Directory API). Recent releases: - 1.1.0 was released on 2020-01-29. - 1.0.0 was released on 2019-01-08. - 0.9.14 was released on 2018-01-18. ## Community Health: The community is active and healthy. The decrease in community activity noted last quarter has vanished, with all metrics now showing major increases. ----------------------------------------- Attachment AE: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and OpenSSL. # Summary The Tomcat community seems to be the only one still using Gump actively. With a new branch of Tomcat getting built the average build time of a full run has gone beyond nine hours so that the number of runs has been reduced to two runs per day. # Releases Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. # Changes to the Roster All ASF committers have write access to the metadata that configure the ASF installations. The last changes to the PMC have seen Konstantin Kolinko and Mark Thomas join in November 2014. Brett Porter has left the PMC in December 2019. ----------------------------------------- Attachment AF: Report from the Apache Hama Project [Chia-Hung Lin] ----------------------------------------- Attachment AG: Report from the Apache Helix Project [Kishore G] ## Description: The mission of Helix is the creation and maintenance of software related to A cluster management framework for partitioned and replicated distributed resources ## Issues: No major issues for project. ## Membership Data: Apache Helix was founded 2013-12-17 (6 years ago) There are currently 20 committers and 18 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 Junkai Xue on 2017-07-03. - No new committers. Last addition was Hunter Lee on 2019-03-12. ## Project Activity: Active projects still ongoing: ZkCient module separation. Cloud support for Helix. Distributed lock WAGED rebalancer ## Community Health: We do have user requests and questions increased. More discussion in the dev channel. 105 PRs opened on GitHub, past quarter (3% increase) 101 PRs closed on GitHub, past quarter (3% increase) ----------------------------------------- Attachment AH: 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: There are no issues currently which need Board's attention at this time. ## Membership Data: We currently have 89 committers and 49 PMC members. Membership changes past quarter: - Anishek Agarwal was added to the PMC on 2020-02-10 - Mahesh Behera was added to the PMC on 2020-02-10 - Denys Kuzmenko was added as committer on 2020-02-14 - László Pintér was added as committer on 2020-02-07 ## Project Activity: Last release we had was in December 2019. There is no RC under discussion. But since community is very active, we expect to have a release in coming months. ## Community Health: This quarter we had email volume go up on dev list. At the same time jira activity, code commits and github PRs were down. Nothing unusual, we had a quieter quarter in terms of development activity. We still closed 250 jiras indicating a good pace of development. ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for March 2020 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. This monthly report is in markdown so that it's easier to read. If you are not viewing this in that format, it can be seen here: https://cwiki.apache.org/confluence/display/INCUBATOR/March2020 There are presently 45 podlings incubating. In February, podlings executed 9 distinct releases. We added no new IPMC members, but two will be added shortly, and 2 IPMC members retired, a further 72 were removed by a board resolution. There was four requested IP clearance, some issue around previous IP clearances have been resolved. We have one new podling this month NLPCraft; another three are under discussion AgensGraph, HBlock and Rainbow. No projects graduated last month. Taverna has retired from the Incubator and Tamaya is discussing retirement. At least one podling is heading towards graduation in the next few months. PageSpeed which didn't report last month reported this month. Hivemall did not report and have indicated they will report next month. Most podlings have sorted out their private mailing lists. Three podlings MXNet, SDAP and Spot are still working on it. The board proposal to remove inactive IPMC members was passed, and they have been removed; everything went smoothly. When they were removed, a few projects found themselves with fewer mentors, and a couple of people have put their hand up to help mentor them. A discussion about the announce email format turned into a discussion about release pages. Several podling that have made releases were discovered not to have download pages, they have been asked to fix this. A script found several other podlings with incorrect download links on download pages and those podling are working on fixing those. ## Community ### New IPMC members: - None ### People who left the IPMC: - 72 IPMC members in board proposal - Jacopo Cappellato - Naomi Slater ## New Podlings - NLPCraft ## Podlings that failed to report, expected next month - Hivemall ## Graduations - None The board has motions for the following: - None ## Releases The following releases entered distribution during the month of February: - APISIX 1.1 - APISIX dashboard 1.0 - BRPC 0.9.7 - Dolphin Scheduler 1.2.1 - Livy 0.7.0 - MXNet 1.6.0 - Milagro Crypto-C v2.0.1 - PageSpeed 1.14.36.1 - Ratis 0.5.0 ## IP Clearance - Pulsar - DotPulsar - OpenWhisk - wskdebug - Atomos Codebase - Maven Wrapper ## Legal / Trademarks - N/A ## Infrastructure - Changes to /dist link has an impact on podling download pages. ## Miscellaneous - We also had a privacy request for the removal of personal information that was passed on to the privacy committee. Table of Contents [brpc](#brpc) [Crail](#Crail) [Daffodil](#Daffodil) [DolphinScheduler](#DolphinScheduler) [Hivemall](#Hivemall) [IoTDB](#IoTDB) [Marvin-AI](#Marvin-AI) [Nemo](#Nemo) [NuttX](#NuttX) [PageSpeed](#PageSpeed) [SAMOA](#SAMOA) [ShardingSphere](#ShardingSphere) [Spot](#Spot) [StreamPipes](#StreamPipes) [Superset](#Superset) [TubeMQ](#TubeMQ) [Warble](#Warble) [YuniKorn](#YuniKorn) -------------------- ## brpc brpc is an industrial-grade RPC framework for building reliable and high- performance services. brpc has been incubating since 2018-11-13. ### Three most important unfinished issues to address before graduating: 1. release apache standard release regularly 2. attract more contributors and committers 3. clean branding issue ### Are there any issues that the IPMC or ASF Board need to be aware of? No big issues ### How has the community developed since the last report? We added three new committers, they are helei, cai Daojin, mu gaidong. they are all from iqiyi company , using brpc for their business, and contributing a lot to brpc projects, including bugfix/feature/code review/evangelism. ### How has the project developed since the last report? 1. vote for release 0.97 rc2 failed due to some license issue 2. vote for release 0.97 rc3 is still ongoing, with WIP disclaimer, hopefully will be done 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 - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2020-01-16 ### When were the last committers or PPMC members elected? 2019-12-24 ### Have your mentors been helpful and responsive? von helped a lot with the release discussion, and JB/kevin also help to vote for new committers. ### Is the PPMC managing the podling's brand / trademarks? Not ready for the branding issue, will check it next time. ### Signed-off-by: - [X] (brpc) Kevin A. McGrail Comments: Nicely done this quarter. - [X] (brpc) Jean-Baptiste Onofré Comments: - [x] (brpc) Von Gosling Comments: As we get closer to the first apache release, the community needs to further strengthen the building and increase developer activity. ### IPMC/Shepherd notes: Justin Mclean: It seems your release has not been placed in the offical release area. Please do so. -------------------- ## Crail Crail is a storage platform for sharing performance critical data in distributed data processing jobs at very high speed. Crail has been incubating since 2017-11-01. ### Three most important unfinished issues to address before graduating: 1. Community building: Increase on number of active contributors and users. 2. Establish new use cases in the community ### Are there any issues that the IPMC or ASF Board need to be aware of? With Patrick currently unavailable for the project, we lost our main contributor. We need help from new active contributors to drive things forward. ### How has the community developed since the last report? Interest from the community in native C++ client for Crail integration with ML frameworks such as TensorFlow. New users from academia. ### How has the project developed since the last report? - Release 1.2 is out. - Working towards releasing new elasticity extensions of Crail. ### 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-01-14 ### When were the last committers or PPMC members elected? December 4th, 2018 ### Have your mentors been helpful and responsive? Our mentors are very helpful. ### Is the PPMC managing the podling's brand / trademarks? Yes, others are using the podling's name correctly (e.g. Samsung Research, Stanford University) ### Signed-off-by: - [x] (crail) Julian Hyde Comments: Glad to hear about the new release. Sorry to hear of Patrick's departure. - [x] (crail) Luciano Resende Comments: We should make sure all development, including prototypes, happen at Apache repositories. New repos can be created when necessary. - [x] (crail) Felix Cheung Comments: Steady progress, would be great to get more community growth ### IPMC/Shepherd notes: -------------------- ## Daffodil Apache Daffodil is an implementation of the Data Format Description Language (DFDL) used to convert between fixed format data and XML/JSON. Daffodil has been incubating since 2017-08-27. ### Three most important unfinished issues to address before graduating: 1. Increase community growth and participation beyond Tresys (main priority) 2. Work with other Apache projects where Daffodil could provide extra functionality (NiFi and Drill are current priorities) 3. Continue frequent release schedule ### 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? - Continued mailing lists discussions, with a handful of new faces asking questions on the users@ mailing list, hopefully some of these can be converted to developers - Struggling to get active involvement outside of Tresys. We are actively working with known users of Daffodil to encourage contributions, including virtual meetings and making time to help spin up with the codebase - An outside developer has shown interest in contributing to the code-generation runtime. Hoping to spin up that user shortly and start getting contributions. ### How has the project developed since the last report? - Released Daffodil 2.5.0 - 29 commits merged from 5 different contributors - 44 issues created, 29 issues resolved, focus was primarily on large features rather than bug burn down. - Significant improvement to DFDL schema compilation time - Incorporated SonarCloud static analysis to help verify code quality - Lots of refactoring to improve code quality and type safety - Created a container to streamline a repeatable release process - Looking like next release will be sometime in March ### 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-01-12 ### When were the last committers or PPMC members elected? - 2019-11-26 - Olabusayo Kilo (Committer) - 2019-06-20 - Brandon Sloane (PPMC) ### Have your mentors been helpful and responsive? - Yes ### Is the PPMC managing the podling's brand / trademarks? - No known cases of a 3rd party incorrectly using the Daffodil name/brand. - Podling name search has been completed and approved by Brand Management Committee: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-147 ### Signed-off-by: - [X] (daffodil) Dave Fisher Comments: Community growth is the main issue blocking graduation. Other than that the podling is in good shape following the Apache Way. - [X] (daffodil) Christofer Dutz Comments: ### IPMC/Shepherd notes: -------------------- ## DolphinScheduler Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow scheduling system dedicated to solving the complex dependencies in data processing, making the scheduling system out of the box for data processing. Dolphin Scheduler has been incubating since 2019-8-29. ### Three most important unfinished issues to address before graduating: 1. Develop more committers and contributors. 2. Make development document more easily to read. 3. make E-mail as an official discussion tool in our communities. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? 1. New committers is active in answer Jira issue and other contributions. 2. More articles were written by users and contributors initiatively. ### How has the project developed since the last report? 1. Apache 1.2.1 without WIP has been released. 2. Restructure the Master/Worker model for easily to expand. 3. Refine CI/CD process for more contributors easily to join. ### 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-2-24 ### When were the last committers or PPMC members elected? 2020-1-24 ### Have your mentors been helpful and responsive? Yes, our mentors help a lot on our progress on restruction. ### Is the PPMC managing the podling's brand / trademarks? Yes, We keep tracking podling's brand / trademarks. ### Signed-off-by: - [x] (dolphinscheduler) Sheng Wu Comments: - [ ] (dolphinscheduler) ShaoFeng Shi Comments: - [x] (dolphinscheduler) Liang Chen Comments: - [X] (dolphinscheduler) Furkan KAMACI Comments: - [x] (dolphinscheduler) Kevin Ratnasekera Comments: ### IPMC/Shepherd notes: -------------------- ## IoTDB IoTDB is a data store for managing large amounts of time series data such as timestamped data from IoT sensors in industrial applications. IoTDB has been incubating since 2018-11-18. ### Three most important unfinished issues to address before graduating: 1. Get more user feedbacks to the community 2. More committers should know how to release a version. And more PPMC should join to vote. 3. make sure the private mailing list is consistent with the PPMC list. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? 1. According to the statistics of https://lists.apache.org/, there are 1079 emails sent by 87 people, divided into 564 topics in these 3 months. 2. 6 new committers are added into the community. 3. 6 GSoC2020 ideas are published. ### How has the project developed since the last report? 1. IoTDB v0.9.1, which contains 11 bug-fix, was released on 11 Jan 2020. It is finished by the 4th RM in the community. 2. 124 Pull requests are merged 3. Now IoTDB docker images and Python client lib are available on dockerHub and pipy.org. ### 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-01-11 (v0.9.1) ### When were the last committers or PPMC members elected? 2020-02-01 ### Have your mentors been helpful and responsive? Very helpful. ### Is the PPMC managing the podling's brand / trademarks? Required Name Search is done. A google search didn’t show any major branding issues that the PPMC needs to deal with. ### Signed-off-by: - [X] (iotdb) Justin Mclean Comments: - [x] (iotdb) Christofer Dutz Comments: By far most email traffic generated by jira (hard to follow especially when trying to keep up to date while commuting) - [ ] (iotdb) Willem Ning Jiang Comments: - [X] (iotdb) Kevin A. McGrail Comments: Discussing what's needed to graduate and the checklist. ### IPMC/Shepherd notes: Dave Fisher: There are a few small issues I noticed. I fixed one and sent an email to the dev@ list with a list. -------------------- ## Marvin-AI Marvin-AI is an open-source artificial intelligence (AI) platform that helps data scientists, prototype and productionalize complex solutions with a scalable, low-latency, language-agnostic, and standardized architecture while simplifies the process of exploration and modeling. Marvin-AI has been incubating since 2018-08-21. ### Three most important unfinished issues to address before graduating: 1. Increase activity from current contributors and community. 2. Build compatibility with all the mainstream storages for artifact persistence. 3. Finish the new version of Toolbox. ### Are there any issues that the IPMC or ASF Board need to be aware of? * A lot of conversations about the project in last few months happened in private channel, because of some contributing groups known to each other. We have already warned everyone about the importance of discussing on open lists. ### How has the community developed since the last report? * in the last few months we have focused on development of university communities, we set up "Marvin-lab" at the university we have the partnership, and several postgraduate students in the artificial intelligence field started using marvin as their main tool for their research. ### How has the project developed since the last report? * Minor bug fixes. * Compatibility with MS Azure Blob for artifact persistence. * New contents and structure improvements in project documentation. * AutoML module and integration with Apache Spark MLib in construction. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2019-07-18 ### When were the last committers or PPMC members elected? * Wei Chen added as new PPMC member (2019-06-07) ### Have your mentors been helpful and responsive? * At least two of the mentors are sometimes active. ### Is the PPMC managing the podling's brand / trademarks? * yes ### Signed-off-by: - [X] (marvin-ai) Luciano Resende Comments: Technical discussions need to happen on the dev list. Please ensure contributors submit their individual contributions. - [X] (marvin-ai) William Colen Comments: ### IPMC/Shepherd notes: Justin Mclean: There has been no traffic to your mailing list for the last 3 -4 months. Why is this the case? And why was it not mentioned in this report? -------------------- ## Nemo Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Nemo has been incubating since 2018-02-04. ### Three most important unfinished issues to address before graduating: 1. Grow the community (committers, contributors, users) 2. Create releases 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? * New committer added: Haeyoon Cho * Committers actively involved in improving code quality * Committers started to work on interesing features such as dynamic task scheduling and offheap computation ### How has the project developed since the last report? * Release 0.2 PPMC vote passed on March 3, 2020 * Developing a job simulator that estimates stage execution time * Started to work on dynamic task scheduling (DTS) that changes task sizes to choose parallelism better * Developing offheap computation that executes UDF functions with offheap data natively * Supported Java 1.11 * Fixed code smells throughout the code base ### 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: Release 0.1 on Dec. 31, 2018 ### When were the last committers or PPMC members elected? February 27, 2020 ### Have your mentors been helpful and responsive? Our mentors have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? The PPMC manages the podling's brand / trademarks. ### Signed-off-by: - [ ] (nemo) Hyunsik Choi Comments: - [X] (nemo) Byung-Gon Chun Comments: - [X] (nemo) Jean-Baptiste Onofre Comments: - [X] (nemo) Markus Weimer Comments: Great work on the release! ### IPMC/Shepherd notes: Justin Mclean: It seems your release was placed in the release area before the vote was complete. This can only be done after the vote has finished. -------------------- ## 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. Determine the form and location of NuttX releases 3. Make the first release under Apache ### 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 128 subscribers and is the home of all development discussions and users questions. * Github's PRs and Issues also have their own discussions. * Some new names are contributing to the project through Github. ### How has the project developed since the last report? * Contributions are flowing regularly as PRs in GitHub and as patches in the dev list. * A bunch of improvements, bug fixes and new architectures were collaborated. * The nightly build is up and running: https://s.apache.org/wnv2u This will improve our review process and push us forward towards making our first Apache release. ### 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: Still working towards making the first Apache release. ### When were the last committers or PPMC members elected? Last elected PPMC: 2020-01-10 ### Have your mentors been helpful and responsive? Mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Some concerns and actions regarding podling's brand were noted in the past reports, however, trademarks issues will be dealt with when graduation draws near. ### Signed-off-by: - [ ] (nuttx) Junping Du Comments: - [X] (nuttx) Justin Mclean Comments: I suggest you look at trademark issues before nearing graduation. - [ ] (nuttx) Mohammad Asif Siddiqui Comments: - [ ] (nuttx) Flavio Paiva Junqueira Comments: ### IPMC/Shepherd notes: -------------------- ## PageSpeed PageSpeed represents a series of open source technologies to help make the web faster by rewriting web pages to reduce latency and bandwidth. PageSpeed has been incubating since 2017-09-30. ### Three most important unfinished issues to address before graduating: 1. Produce a release 2. Increase the number of active developers 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? After a series of release candidates, a first incubator release was approved by both the developer group and the IPMC. However, while doing the final release preparation a blocking issue was observed: the scripts that package the product would still point to dl.google.com as a repo source. This is being addressed. ### How has the community developed since the last report? Mailing lists and git issues are active. The number of active developers is steady. ### How has the project developed since the last report? A first WIP incubator release made it through the voting rounds, but needs some small changes to address a blocking issue observed during finalization. Those have been made, and another vote is in progress. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? May 27 2019 (Longinos Ferrando, elected as both committer and PMC member) ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? As far as we know the brand is respected by third parties It's not known if the VP, brand has explicitly approved, so that is something we need to make sure about and resolve. ### Signed-off-by: - [ ] (pagespeed) Jukka Zitting Comments: - [ ] (pagespeed) Leif Hedstrom Comments: - [x] (pagespeed) Nick Kew Comments: ### IPMC/Shepherd notes: Justin Mclean: It seems your release has not been placed in the offical release area. Please do so. -------------------- ## SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza. SAMOA has been incubating since 2014-12-15. ### Three most important unfinished issues to address before graduating: 1. Revitalize the project by resuming development 2. Enlarge the user base and contributing community ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? - Mailing list activity: - @dev: 31 messages ### How has the project developed since the last report? With the help of the new commiter Corey Sterling, we prepared a new release of Apache SAMOA, that is already being discussed and voted (RC3). ### 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: 2016-09-30 ### When were the last committers or PPMC members elected? August 2019 ### Have your mentors been helpful and responsive? Yes, the mentors have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Yes. There are no 3rd parties incorrectly using the podling‘s name and brand for now. ### Signed-off-by: - [X] (samoa) Alan Gates Comments: With the election of the new committer it looks like the project is slowly making some progress. I'm happy to see it start moving forward. ### IPMC/Shepherd notes: -------------------- ## ShardingSphere ShardingSphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. ShardingSphere has been incubating since 2018-11-10. ### Three most important unfinished issues to address before graduating: 1. Doing podling name search now, the JIRA ticket here[1] 2. Clear issues which indicate by incubator status page[2] 3. Finished discussion about graduation and start to vote to TLP[3] [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-178 [2] https://incubator.apache.org/clutch/shardingsphere.html [3] https://lists.apache.org/thread.html/r2272e5fb70044e07f8ff21e282d84ab88a 30eac6709a9d0981f6b2c1%40%3Cdev.shardingsphere.apache.org%3E ### Are there any issues that the IPMC or ASF Board need to be aware of? There is a user wall page[4] to show all user lists. The URL of page may generate confusion with apache powered by policy. We have already change the page url to [5]. [4] https://shardingsphere.apache.org/community/en/poweredby/ [5] https://shardingsphere.apache.org/community/en/users/ ### How has the community developed since the last report? Wen Ouyang, ZongLei Dong, Xiaofeng Jiang have been voted and joined as committer. There are 115 people to contribute codes to the main repo, there are 26 new contributors during last report. We are happy to see the community are growing up. Prepare for graduation, finished discussion mail list is [6]. The main resolved issues are: 1. Major contributors sign ICLA 2. Confirm PMC and committer list 3. IP Clearance for OpenSharding GitHub repo[7] 4. Remove author information in java code 5. Update incubator status site[8] [6] https://lists.apache.org/thread.html/r885653f36d76c9d842b52f0ba2576dd962 efd2e9a24acc03515c9e24%40%3Cdev.shardingsphere.apache.org%3E [7] https://github.com/OpenSharding [8] https://incubator.apache.org/clutch/shardingsphere.html ### How has the project developed since the last report? Release 4.0.0 last month, it is the stable version of 4.0.0-RC1, 4.0.0-RC2 and 4.0.0-RC3. Releasing and voting version 4.0.1 now. ### 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-01-13 ### When were the last committers or PPMC members elected? 2020-01-08 ### Have your mentors been helpful and responsive? Yes, the mentors have been helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Yes. There are no 3rd parties incorrectly using the podling‘s name and brand for now. ### Signed-off-by: - [X] (shardingsphere) Craig L Russell Comments: Graduation vote is underway on the dev list. I believe the project is ready to graduate. - [x] (shardingsphere) Willem Ning Jiang Comments: It's good to see the project is ready to graduate. - [x] (shardingsphere) Von Gosling Comments: Glad to see all necessary graducation affairs have been resolved. ### IPMC/Shepherd notes: Dave Fisher: The VP, Brand approved your name search on February 20. -------------------- ## StreamPipes StreamPipes is a self-service (Industrial) IoT toolbox to enable non- technical users to connect, analyze and explore (Industrial) IoT data streams. StreamPipes has been incubating since 2019-11-11. ### Three most important unfinished issues to address before graduating: 1. Make a first Apache release 2. Grow the community 3. Diversify PPMC members & committers ### Are there any issues that the IPMC or ASF Board need to be aware of? There are no issues right now. ### How has the community developed since the last report? * We gave a talk about StreamPipes at Bosch Connected World 2020 (~100 participants in the talk) * We gave several IIoT demos involving Apache StreamPipes at FZI Open House (~300 participants) * There was a lot more communication on the mailing list concerning the discussion on upcoming features and improvements * An external company mentioned their usage of StreamPipes in one of their upcoming products * Some new contributions/pull requests from external contributors * The number of Twitter followers has increased (currently at 113) * The number of Github stars has increased (currently at 117) ### How has the project developed since the last report? * The community is currently working on the final steps concerned with the preparation of the first ASF release * We performed an upgrade of the UI components to Angular 9, which improves performance * We implemented a new live dashboard * We refactored the code base and removed/rewrote components which relied on non-ASF conformant licenses, e.g., kafka-rest * LICENSE and NOTICE files have been created for the incubator-streampipes project The first release is planned within the next few weeks. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] 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? No new committers have been added so far. ### Have your mentors been helpful and responsive? Our mentors are very responsive and provide good feedback. ### Is the PPMC managing the podling's brand / trademarks? * Currently, no issues are known related to brand misuse, but there are still some open issues concerning the transition to the ASF infrastructure (e.g., shutting down the old streampipes organization on Github to avoid confusion) * We started to contact external websites who provided links to the old streampipes.org website and asked them (or created pull requests) to change this to the new streampipes.apache.org domain. ### Signed-off-by: - [X] (streampipes) Christofer Dutz Comments: Perhaps it would help assigning streampipes.org domain to apache and have auto-redirect? - [X] (streampipes) Jean-Baptiste Onofré Comments: The highest priority is a first release and it's planned in few weeks. - [ ] (streampipes) Julian Feinauer Comments: - [X] (streampipes) Justin Mclean Comments: - [ ] (streampipes) Kenneth Knowles Comments: ### IPMC/Shepherd notes: -------------------- ## Spot Apache Spot is a platform for network telemetry built on an open data model and Apache Hadoop. Spot has been incubating since 2016-09-23. ### Three most important unfinished issues to address before graduating: - Revive community activity (Discussion in mailing lists, increase frequency of commits) - Create a new roadmap and release plan that will improve adoption. - Make it easier to contribute to the project (e.g. documentation, framework). ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? The number of active committers has increased over the past quarter, and we also have several new potential community members looking to become committers. We will work with our mentors to go through the process to onboard them. Much of the activity from the community has been focused on stabilizing the codebase and fixing known issues in the documentation and Spot website. This will greatly benefit new users and reduce confusion when standing up the Spot different modules. ### How has the project developed since the last report? Several projects have been proposed, discussed, and completed during the past quarter. We're also working to close the remaining open PRs as soon once the community finishes its review. Additionally there were some Podling Website check failures in the Whimsy report that we began to look into and resolve. These should be mostly resolved by the next Podling report update. We've also begun discussions on the second version of the Open Data Model (ODM v2). There were several problems seen in the implementation with ODM v1 that need to be resolved before substantial adoption of Apache Spot can take place. Its our goal to come to a decision on the design of ODM v2 this next quarter. Once a data model redesign is agreed upon this will serve as a catalyst to modernizing other Spot modules so everything is properly integrated. ### 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: - 2017-09-08 ### When were the last committers or PPMC members elected? - 2019-09-02 - Mark Schoeni ### Have your mentors been helpful and responsive? Yes our mentors have been helpful. We will be engaging them more soon for guidance on on-boarding new committers, as well as a few other items related to the Whimsy and Clutch reports and also updating the Apache Spot Podling website as this is missing a number of updates. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (spot) Uma Maheswara Rao G Comments: There is some improvement on mailing lists recently. IMO, Still needs improvement in community development. ### IPMC/Shepherd notes: -------------------- ## Superset Apache Superset (incubating) is a modern, enterprise-ready business intelligence web application. ### Three most important unfinished issues to address before graduating: - Keep producing a steady stream of approved Apache releases - Produce a project charter - Seek a positive recommendation from the IPMC ### 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? - Suitable name search was [approved](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-173) by Apache legal! - The first Superset Meetup took place, hosted by Preset, on 2020-02-11, with talks by Maxime Beauchemin, Beto Dealmeida, and Evan Rusackas - Organic growth of our Github Contributors: -- Stars (27,034 → 27,885) -- Forks (5,400 → 5636) -- Watchers (1245 → 1,241) - Added 225 commits (Dec 1, 2019 to Feb 24, 2020) - Grew Superset slack users to (1,023→ 1,309) ### How has the project developed since the last report? - Release 0.35.1 - Release 0.35.2 ### 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-01-06 ### When were the last committers or PPMC members elected? - 2020-02-24 - Evan Rusackas - 2020-01-30 - Ville Brofeldt - 2019-12-06 - Craig Rueda ### Have your mentors been helpful and responsive? Alan Gates and Jakob Homan approved the prior Podling report ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [X] (superset) Alan Gates Comments: - [X] (superset) Jakob Homan Comments: - [ ] (superset) Ashutosh Chauhan 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.Launch the first Apache release. 2.Make development document more easily to read. 3.Grow the community to involve more contributors and increase the diversity. ### 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? At this stage, no community activities were initiated, but we internally initiated a vote for the project committer and selected the first committer of the project. I believe this will promote the subsequent development of the project community. ### How has the project developed since the last report? The project is nearing completion of the migration to the Apache incubator: at this stage, we have completed the change of the project's package name, the standardization of file's LICENSE, and the launch of the project home page but the documentation and project home page content relatively lacking, this part needs to be improved in the next stage. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: None ### When were the last committers or PPMC members elected? 2020-02-20 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [X] (tubemq) Junping Du Comments: I saw there are new committers get voted, good move! - [X] (tubemq) Justin Mclean Comments: Showing better progress than before. - [ ] (tubemq) Sijie Guo Comments: - [ ] (tubemq) Zhijie Shen Comments: - [X] (tubemq) Jean-Baptiste Onofre Comments: Podling is still in bootstrap phase but moving forward. ### IPMC/Shepherd notes: -------------------- ## YuniKorn Apache YuniKorn (incubating) 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: - Gain more contributors and active committers. - Launch the first Apache release. - Improve documentation and provide a roadmap. ### Are there any issues that the IPMC or ASF Board need to be aware of? - No critical issues at this point in time ### How has the community developed since the last report? This is the first report for YuniKorn. Migration and setup is not fully finialised. ### How has the project developed since the last report? - source code repository moved to apache - JIRA setup and configured - community design for a new feature started ### 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: N.A. ### When were the last committers or PPMC members elected? No new committers or PPMC members have been added since starting incubation. ### Have your mentors been helpful and responsive? Yes, helped setup project page (Holden) and questions (Junping) ### Is the PPMC managing the podling's brand / trademarks? No issues that we are aware of ### Signed-off-by: - [X] (yunikorn) Junping Du Comments: - [x] (yunikorn) Felix Cheung Comments: - [X] (yunikorn) Jason Lowe Comments: - [ ] (yunikorn) Holden Karau Comments: Comments: Some projects choose to prepare a new release soon after becoming Apache incubator project. See if YuniKorn would like to follow. ### IPMC/Shepherd notes: ----------------------------------------- Attachment AJ: Report from the Apache Jackrabbit Project [Marcel Reutegger] Apache Jackrabbit: Board Report March 2020 ========================================== ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.24.0 that was made available on January 28th. The upcoming Jackrabbit Oak 1.26.0 release will finally remove usage of java.security.acl.Group, a deprecated interface that will be removed in Java 14. A security issue was reported on January 22nd on the private list. The issue was very well handled by Angela Schreiber and Julian Reschke and within a week new releases were made available that contained a fix. The security issue was initially discovered by Andrew Khoury and Russ Wright of Adobe. Details on the security issue are available in https://issues.apache.org/jira/browse/OAK-8870 and https://nvd.nist.gov/vuln/detail/CVE-2020-1940 Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. Jukka Zitting contacted the PMC and expressed his desire to go emeritus. His resignation from the PMC and committer base became effective after a 72 hour wait period on March 6th. ## PMC changes: - Currently 55 PMC members. - Jukka Zitting resigned on 2020-03-06 - No new PMC members. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Committer base changes: - Currently 55 committers. - Jukka Zitting resigned on 2020-03-06 - No new committers. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Releases: - jackrabbit-oak-1.10.7 was released on 2019-12-12 - jackrabbit-2.20.0 was released on 2020-01-07 - jackrabbit-oak-1.6.19 was released on 2020-01-13 - jackrabbit-oak-1.22.0 was released on 2020-01-16 - jackrabbit-oak-1.4.25 was released on 2020-01-20 - jackrabbit-oak-1.8.19 was released on 2020-01-23 - jackrabbit-oak-1.24.0 was released on 2020-01-28 - jackrabbit-oak-1.10.8 was released on 2020-01-28 - jackrabbit-oak-1.8.20 was released on 2020-01-31 - jackrabbit-oak-1.6.20 was released on 2020-02-05 - jackrabbit-oak-1.22.1 was released on 2020-02-13 - jackrabbit-2.21.0 was released on 2020-02-14 - jackrabbit-oak-1.4.26 was released on 2020-02-19 ## JIRA activity: - 157 JIRA tickets created in the last 3 months - 130 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AL: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: Apache Karaf provides a modern and polymorphic applications runtime, multi-purpose (micro services, cloud, integration, IoT, OSGi, etc). ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Karaf was founded 2010-06-16 (10 years ago) There are currently 31 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Francois Papon on 2018-11-29. - No new committers. Last addition was Francois Papon on 2018-05-19. ## Project Activity: We prepared and plan first Apache Karaf European Meetup in Germany in April 30th. The formal communication (with CFP) will be sent soon (this week) and we will plan to ask "support" to ASF com. In term of releases and "pure" project activity, we released Apache Karaf 4.3.0.RC1 with a almost full support for OSGi R7. It's an important milestone for the project as it heads to the next major release (4.3.0). We also released 4.2.8 and 3.0.10 maintenance releases to sustain our release cycle. Karaf 4.2.9 will be submitted to vote soon as well. We also started a redesign of the Karaf tooling (maven plugins, etc) to propose a much better developer experience. We had several feedbacks saying that Apache Karaf is great once running, but the developer ramp up and developer experience could be much better. That's why we started to work on this area. About the subprojects, Apache Karaf Cave 4.2.1 has been released, containing a complete refactoring of Cave, now more multipurpose repository focused. We are also preparing Apache Karaf Decanter 2.3.0 as maintenance release with lot of improvements and bug fixes. Finally, a complete Apache Karaf Cellar refactoring has started, heading to new major Cellar release. Here's a quick summary about recent releases: - 4.3.0.RC1 was released on 2020-01-31. - 4.2.8 was released on 2020-01-23. - 3.0.10 was released on 2020-01-11. - Cave 4.2.1 was released on 2019-12-02. * The meetup was changed from an in-person meeting to a virtual meetup as a result of the current COVID19 pandemic concerns. ## Community Health: We are happy to see a growing interest around Apache Karaf, with new users and potential contributors on Slack and mailing lists. We can see about 25% more traffic on mailing lists proving this interest about Apache Karaf. We think that first Apache Karaf Meetup will be a great opportunity for Karaf communities to meet and discuss about the project. There are also discussions with Apache ServiceMix and OPS4J communities to move some projects into Apache Karaf. It's also a tremendous sign about Karaf community and branding. With these new subprojects, Apache Karaf will be first citizen project in the runtime ecosystem. ----------------------------------------- Attachment AM: Report from the Apache Labs Project [Danny Angus] ## Description: Labs is a place for innovation where committers of the foundation can experiment with new ideas. ## Issues: Labs underwent a roll-call in January called by wave@ There were four responses. ## Membership Data: Apache Labs was founded 2006-11-15 (13 years ago) There are currently 31 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Simone Tripodi on 2011-06-14. - No new committers. Last addition was Juan P. Gilaberte on 2018-05-30. ## Project Activity: Labs is largely inactive but as it is a facility offered to committers for their use, lack of activity on its own is not a symptom of disfunction. ## Community Health: Labs' community is all committers. Demand for labs is currently non-existent but this may change. ----------------------------------------- Attachment AN: Report from the Apache Lucene Project [Anshum Gupta] ## Description: - Lucene Core is a search-engine toolkit - Solr is a search server built on top of Lucene Core ## Issues: The community is currently working on reducing the tech debt that Solr currently carries, as mentioned in the previous board report. Several committers are actively working on a much improved 9.0 release. The PMC feels that the situation is now under control. ## Membership Data: Apache Lucene was founded 2005-01-18 (15 years ago) There are currently 82 committers and 54 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Nhat Nguyen was added to the PMC on 2020-03-02 - No new committers. Last addition was Bruno Roustant on 2019-11-22. ## Project Activity:We released Lucene and Solr 8.4.0 and 8.4.1 since the last report. With 8.4.0, we added numerous optimizations in Lucene. LatLonShape now supports the "CONTAINS" relation, which enables to find all indexed shapes that contain the query shape. Solr added a new package management system and improved security out of the box. Solr 8.4.0 release also announced CVE-2019-17558. An 8.4.1 release was done to fix SSL support in Solr along with security improvements in the newly added package manager. Overseer serialization was also fixed to support rolling upgrades. We are still working to change our entire build system from Ant to Gradle. A lot has already been ported, and this task is very close to completion. The Lucene and Solr websites were revamped and ported from SVN to Git and published as HTTPS only. ## Community Health: Community health is very strong. Our two main user lists, java-user and solr-user, continue to be widely used. Our Jira issue activity and code contributions are also very strong. 450 issues were opened and 315 closed in JIRA in the past quarter. Our GitHub activity has also been on an upward trend and more contributors are using GitHub PRs as compared to patches now. A Lucene/Solr track has been reintroduced to ApacheCon NA 2020. We are actively asking possible speakers to submit talks and hope to see a good lineup of talks by users and developers. ----------------------------------------- Attachment AO: Report from the Apache Lucene.Net Project [Shad Storhaug] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == This quarter has seen some progress, mostly with addressing performance issues: * NIOFSDirectory was modified to move buffered data in batches, rather than one byte at a time. * FSDirectory.FSIndexOutput was modified so it doesn't utilize the buffer in BufferedIndexOutput, since FileStream already has its own buffer. * TokenStream had Reflection code that ran at runtime, which has been replaced with a dotnet Code Analyzer and Fix which runs at design time. * Replaced Lucene's WeakIdentityMap with .NET's ConditionalWeakTable. * The scaffolding known as the Lucene.Net.Support namespace has been either moved to the J2N library or marked internal. Several types were optimized and consolidated in the process. * The caches in ICU4N were replaced with the cache from Microsoft.Extensions.Caching.Memory. * The API documentation has been cleaned up a lot and work is being done to set it up so each release has its own version. Lucene.NET 4.8.0-beta00007 was released this quarter. A few bugs were reported on JIRA, but the mailing lists have been mostly inactive. == Remaining Work on 4.8.0 == We updated the itemized list of remaining issues for both Lucene.NET and ICU4N and have arrived at the following estimates to production release: Lucene.NET 4.8.0 * Hours Completed: ~4000 * Hours Remaining: ~450 ICU4N 60.x * Hours Completed: ~540 * Hours Remaining: ~260 (assuming we don't port any more of it) * Hours Remaining: ~725 (ported to feature completion) Lucene.NET 8.x Upgrade * Hours Completed: 0 * Hours Remaining: ~1700 The primary items left to complete for the 4.8.0 release are identifying and addressing performance issues, reviews of tests and usage of IDisposable, the API docs, and ICU4N. == Releases == * Last Release 3.0.3 - Oct 2012 * Working toward 4.8.0 - Currently beta0007, released 2019-12-29 == People == * Last PMC Member added May 2017, Shad Storhaug (nightowl888) * Last committer added Oct 2019, Shannon Deminick (shazwazza) * PMC Chair rotated 20 June 2018 to Shad Storhaug (nightowl888) ----------------------------------------- Attachment AP: Report from the Apache Marmotta Project [Jakob Frank] ----------------------------------------- Attachment AQ: Report from the Apache Mnemonic Project [Gang Wang] ----------------------------------------- Attachment AR: Report from the Apache Mynewt Project [Justin Mclean] ## Description: The mission of Apache Mynewt is the creation and maintenance of software related to an embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android ## Issues: ASF membership in Bluetooth SIG (for NimBLE stack being able to use manufacturer ID of ASF) was raised on private@. Creating account requires "Company's formation document" and "signing authority" and this matter seems to be stuck and is not moving forward since January. ## Membership Data: Community changes, past quarter: - No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24. - No new committers. Last addition was Hauke Petersen on 2019-11-13. ## Project Activity: - Work on release 1.8.0 in March 2020 - NimBLE 1.3 stack release at same time - Community work in several areas including: - CI and test facilities, - Bluetooth 5.1 and 5.2 features - Improvements to internal components like console, sensors drivers etc - More BSP supported - tooling improvements (newt and newtmgr) Release is overdue initial plans due to mcumgr component decoupling (completed now). ## Community Health: - Mailing list activity seeing new users - Mailing list exchanges are mostly around BLE, tooling and Windows support - Mailing list activity has dropped compared to last quarter - Some mailing list messages remain unanswered - Slack remains active and is primary place for development discussions and user support ----------------------------------------- Attachment AS: Report from the Apache NetBeans Project [Geertjan Wielenga] ## Description: The mission of Apache NetBeans is the creation and maintenance of software related to a Java-based development environment, tooling platform, and application framework. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache NetBeans was founded 2019-04-17 (a year ago) There are currently 69 committers and 63 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - Currently working on two or three new committers to join the project. - No new PMC members. Last addition was Sarvesh Kesharwani on 2019-06-06. - No new committers. Last addition was Gaurav Gupta on 2019-11-15. ## Project Activity: - Apache NetBeans 11.3 was released on 2020-02-24, with thanks to Eric Barboni for managing the process awesomely. - Work started on first LTS release, i.e., 12.0, outside Apache Incubator. - 5th Oracle donation, focused on code related to C/C++ features, completed. - Archive of historic Oracle NetBeans bugs now available read-only in Apache: https://bz.apache.org/netbeans. - Strong Apache NetBeans presence at FOSDEM in Brussels in February: https://fosdem.org/2020/schedule/track/free_tools_and_editors/ ## Community Health: - dev@netbeans.apache.org had a 28% decrease in traffic in the past quarter (1079 emails compared to 1484) - netcat@netbeans.apache.org had a 381% increase in traffic in the past quarter (77 emails compared to 16) - 387 issues opened in JIRA, past quarter (-22% decrease) - 176 issues closed in JIRA, past quarter (-10% decrease) - 496 commits in the past quarter (-28% decrease) - 55 code contributors in the past quarter (12% increase) - 281 PRs opened on GitHub, past quarter (-13% decrease) - 293 PRs closed on GitHub, past quarter (-5% decrease) ----------------------------------------- Attachment AT: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source product for the automation of enterprise processes that includes framework components and business applications for ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset Management). Apache OFBiz provides a foundation and starting point for reliable, secure and scalable enterprise solutions. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OFBiz was founded 2006-12-20 (13 years ago). There are currently 49 committers and 21 PMC members in this project. The Committer-to-PMC ratio is 7:3. Community changes, past quarter: - Mathieu Lirzin was added to the PMC on 2019-11-12 but then resigned on 2020-02-24 - Second last addition was Gil Portenseigne on 2019-11-08. - Yoav Shapira resigned from the PMC on 2020-03-04 - Olivier Heintz was added as committer on 2020-01-16 ## Project Activity: - the main focus, after the switch from SVN to Git in the last quarter, has been that of streamlining the contribution workflow, documenting best practices, leveraging the new tools available, maintaining a clean repository history; this is still a work in progress but good progress is made on the dev list on all these topics - The community worked together on bug fixes, improvements and documentation during the OFBiz Community Days event [1] for Q1 of 2020, that was held from 21st to 25th of February. - new releases: Apache OFBiz 16.11.07 was released on February, 2020; it is the 7th bug-fix release of the 16.11 series and probably the last one in the series; Apache OFBiz 17.12.01 was released on March, 2020; it is the first release of the 17.12 series, that is now the active release branch - Vulnerability reports: since our last report, with the publication of the two new releases, we have resolved two CVEs: CVE-2019-12426 and CVE-2020-1943; - Various bug fixes and enhancements have been contributed and committed to the trunk and backported to the various release branches - More details about the community activities are published in the official blog [2], on Twitter [3] and other social media [4]. - Trademarks: we do not have trademark related concerns at the moment and our backlog of non-compliant parties is mostly empty [1] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days [2] https://blogs.apache.org/ofbiz/ [3] https://twitter.com/ApacheOfbiz [4] https://www.facebook.com/Apache-OFBiz-1478219232210477/ ## Community Health: We are currently considering for PMC and committers membership a group of candidates from our watchlist; the community is actively involved in finalizing the migration to Git and as usual in improving the trunk, fixing vulnerabilities, stabilizing the release branches, publishing new releases and in various discussions and support requests posted mostly in the mailing list and in our issue tracker. ----------------------------------------- Attachment AU: Report from the Apache Olingo Project [Michael Bolz] ## Description: The Apache Olingo Project be and hereby is responsible for the creation and maintenance of software related to providing an implementation of the OASIS OData (Open Data Protocol) specifications, in server and client form; It currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Olingo was founded 2014-03-19 (6 years ago) There are currently 25 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Ramya Vasanth on 2019-04-15. - No new committers. Last addition was Archana Rai on 2017-05-26. ## Project Activity: Recent releases: - 4.7.1 was released on 2019-12-25. - 4.7.0 was released on 2019-12-04. - 4.6.0 was released on 2019-05-05. ## Community Health: Overall community health is good. The V4 code line is on steady development also reflected in related discussions on mailing list and new created JIRA items. Release of V4 version 4.7.1 was done in December last year. The V2 code line has still open and new created JIRA items. Over the last months there were less new JIRA issues created then in the past quarter (-20% created). We closed less JIRA issues then in the past quarter (-37% closed). On GitHub only 3 PRs were created and one PR closed which is for an decrease to past quarter. ----------------------------------------- Attachment AV: Report from the Apache OODT Project [Imesha Sudasingha] ----------------------------------------- Attachment AW: Report from the Apache OpenNLP Project [Jeffrey T. Zemerick] ## Description: The mission of OpenNLP is the creation and maintenance of software related to Machine learning based toolkit for the processing of natural language text ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OpenNLP was founded 2012-02-14 (8 years ago) There are currently 22 committers and 15 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 Koji Sekiguchi on 2017-10-09. - Tim Allison was added as committer on 2020-01-28 ## Project Activity: The project has 7 JIRA issues closed and marked as fix for the next release (1.9.3) and is in the planning process for a 1.9.3 release with the goal of having the release done by the end of March 2020. ## Community Health: Commit activity and developer mailing list activity had an increase likely due to the working of pending pull requests. We were able to successfully merge and close many pull requests and are continuing to work on the remaining ones. Faster resolution of pull requests may encourage more contributions from the community. ----------------------------------------- Attachment AX: Report from the Apache OpenWebBeans Project [Mark Struberg] ----------------------------------------- Attachment AY: Report from the Apache Pig Project [Koji Noguchi] ## Description: Apache Pig is a platform for analyzing large data sets on Hadoop. It provides a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. ## Issues: We still haven't released 0.18 with Hadoop version 3 support but we are making progress now. We are working on updating owasp known vulnerabilities and also dealing with conflicts moving to newer dependencies and supporting newer versions of dependent stacks. Also, working on fixing unstable pig-on-spark unit&e2e test failures. ## Membership Data: Apache Pig was founded 2010-09-21 (9 years ago) There are currently 31 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Koji Noguchi on 2016-08-04. - No new committers. Last addition was Nándor Kollár on 2018-09-06. ## Project Activity: Still low activities but now having other committers/PMC helping. (Last 0.17.0 release was on 2017/06/16. ) ## Community Health: Overall activity is low as project is mostly stable and contributions are mainly bug fixes. ----------------------------------------- Attachment AZ: Report from the Apache Pivot Project [Roger Lee Whitcomb] ----------------------------------------- Attachment BA: Report from the Apache PLC4X Project [Christofer Dutz] ## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Issues: Currently nothing would require board attention ## Membership Data: Apache PLC4X was founded 2019-04-17 (a year ago) There are currently 14 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Łukasz Dywicki on 2019-07-28. - Alvaro del Castillo was added as committer on 2020-01-29 - César García was added as committer on 2020-02-03 - Niklas Merz was added as committer on 2020-01-29 - Lukas Ott was added as committer on 2020-01-03 - Dominik Riemer was added as committer on 2020-02-04 ## Project Activity: - 0.6.0 was released on 2020-03-01 In December we had a 3 day code retreat, where a large portion of the core-team meet and worked on addressing some of the most important architectural challenges in preparation to porting all of our drivers to the new generated codebase. In general we have started to maintain and fix a lot of reported issues in the 0.6 branch which we now consider a LTS release branch. The version 0.7.0 is a huge refactoring as we completely rewrote the core of PLC4X and are currently deleting all existing drivers, replacing them with new version which we generate from our new code-generation tool. Still 1-2 drivers to port, but most of the others are already finished. We completely relaunched our website, giving it a way more appealing look and feel as we think the old website was preventing people from giving PLC4X a chance. We are currently in the process of preparing the ASF to become member of a list of 4-5 industry foundation in order to allow us to legally be able to provide some drivers and or mention them on our website and other public information material. We have had Meetups/Conference-Talks/Workshops: - PLC4X full day workshop: Building IoT (02-03-2020) - Talks: Building IoT - Essen (03-03-2020, 04-03-2020) - Talk: Stuttgarter Innovationstage (03-03-2020) - Talk: OOP - Munich (05-02-2020) Perhaps worth mentioning: In December Christofer applied for European research funds via NLnet Foundation and was recently informed that his application was granted. So if this really will happen, then these funds will be used 100% for driving the C-type drivers for PLC4X as well as an Apache MyNewt integration. ## Community Health: This year the number of contributors has grown quite a bit. Also the number of people showing up from different companies has increased significantly. Also starting this year we started to invite people as committer first and stopped instantly inviting them as PMC in one go, as we noticed some people became less active after becoming PMCs. At the same time we lowered the bar for committership a little and redefined how we interpret the term "committer". We treat committers as people who are committed to PLC4X and PMCs who have proven to be so for a prolonged period of time (not too long) - dev@plc4x.apache.org had a 59% increase in traffic in the past quarter (494 emails compared to 309) - issues@plc4x.apache.org had a 444% increase in traffic in the past quarter (305 emails compared to 56) - 23 issues opened in JIRA, past quarter (21% increase) - 20 issues closed in JIRA, past quarter (42% increase) - 490 commits in the past quarter (62% increase) - 17 code contributors in the past quarter (13% increase) - 28 PRs opened on GitHub, past quarter (21% increase) - 27 PRs closed on GitHub, past quarter (28% increase) - 172 Github Stars (up by 18 since last report) (up by 30) - 305 @ApachePLC4X Twitter account followers (up by 33) ----------------------------------------- Attachment BB: Report from the Apache Portable Runtime (APR) Project [Nick Kew] ## Description: The mission of the Apache Portable Runtime (APR) project is to create and maintain software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. APR provides an API to which software developers may code and be assured of predictable if not identical behaviour regardless of the platform on which their software is built, relieving them of the need to code special-case conditions to work around or take advantage of platform-specific deficiencies or features. Consistent abstractions are provided both for host platforms and for utilities such as databases. In addition, APR provides a range of general-purpose utilities. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Portable Runtime (APR) was founded 2000-12-01 (19 years ago) There are currently 67 committers and 42 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 Ivan Zhakov on 2019-11-05. - No new committers. Last addition was Evgeny Kotkov on 2017-09-13. ## Project Activity The project has been very quiet in the quarter. Nothing of note to report. ## Community Health: The community remains broadly healthy. Although there is no significant development on the horizon, there is capacity to act if a new need is identified, or to react to a security report. ----------------------------------------- Attachment BC: Report from the Apache Portals Project [David Sean Taylor] Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Activity: No new releases since April 25 2019 (Pluto 3.1.0) No additional members since last report 12 Feb 2017 - Two new PMC members added 27 April 2017 - Apache Portals Pluto team released Pluto Maven Archetypes 3.0 to support to developing new portlets to the new 3.0 spec ## Mailing list activity: Low to zero activity on all lists ## Issues: We have no board-level issues at this time. ## PMC/Committership changes: Last Added PMC Members: 12 Feb 2017 - Scott Martin Nicklaus 12 Feb 2017 - Neil Griffin Last Added Committers: 05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014 Neil Griffin ## Releases: Pluto 3.1.0 - 25 April 2019 Pluto 3.0.1 - 21 June 2018 Pluto Maven Portlet Archetype 3.0.1 - 21 June 2018 Pluto Maven Generic Archetype 3.0.1 - 21 June 2018 Pluto Maven Archetype 3.0.0 - 27 April 2017 Pluto 3.0.0 - 18 January 2017 Jetspeed 2.3.1- 09 May 2016 ----------------------------------------- Attachment BD: Report from the Apache PredictionIO Project [Donald Szeto] ## Description: The mission of Apache Predictionio is the creation and maintenance of software related to a machine learning server built on top of state-of-the-art open source stack, that enables developers to manage and deploy production-ready predictive services for various kinds of machine learning tasks ## Issues: Update: A community member, who's a committer and PMC of another Apache project, has expressed interest in helping. The member has been engaged and we are waiting for actions from that member. Last report: No PMC chair nominee was nominated a week after the PMC chair expressed intention to resign from the chair on the PMC mailing list. ## Membership Data: Apache PredictionIO was founded 2017-10-17 (2 years ago) There are currently 29 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. Community changes, past quarter: - No new PMC members. Last addition was Andrew Kyle Purtell on 2017-10-17. - No new committers were added. ## Project Activity: Sparse activities only on mailing list. Recent releases: 0.14.0 was released on 2019-03-11. 0.13.0 was released on 2018-09-20. 0.12.1 was released on 2018-03-11. ## Community Health: Update: A community member, who's a committer and PMC of another Apache project, has expressed interest in helping. The member has been engaged and we are waiting for actions from that member to see if a nomination to PMC and chair would be appropriate. Last report: We are seeking new leadership for the project at the moment to bring it out of maintenance mode. Moving to the attic would be the last option. ----------------------------------------- Attachment BE: Report from the Apache Pulsar Project [Matteo Merli] Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. ## Issues: - There are no issues requiring board attention at this time. ## Project Activity: - The project has released 2.5.0 in December that included Highlights include: * [PIP-41] Introduce Protocol Handler API * [PIP-45] Pluggable metadata interface * [PIP-44] Separate schema compatibility checker for producer and consumer * [PIP-43] Producer send messages with different schema * [PIP-51] Introduce sticky consumer * [PIP-38] Support batch receive in java client. * [PIP-52] Add support of dispatch throttling relative to publish-rate * Upgraded to ZooKeeper 3.5 * Upgraded to BookKeeper 4.10.0 * HDFS offloader for Pulsar tiered storage - Work is underway for next release 2.6.0 - Pulsar NodeJS client library 1.1.0 was released on Feb 18th. - Several improvement proposals have been submitted: * PIP 59: gPRC Protocol Handler * PIP 58: Support Consumers Set Custom Retry Delay * PIP 57: Improve Broker's Zookeeper Session Timeout Handling * PIP 56: Python3 Migration * PIP 55: Refresh Authentication Credentials * PIP 54: Support acknowledgement at batch index level * PIP 53: Contribute DotPulsar to Apache Pulsar * PIP 52: Message dispatch throttling relative to publish rate - Several talk on Pulsar were presented at conferences and meetups, in US, Europe and China, both by Pulsar committer/PMC members as well as other members of the community. Non-exhaustive list: * A Pulsar meetup was held on Jan 15 in Toronto. Cory Darby gave a talk about "RIP Apache Kafka, long live Apache Pulsar" and Tamer A shared about "Pulsar in Action, getting your hands dirty with Pulsar". * Apache IoTDB X Apache Pulsar meetup was held on Jan 4 in Beijing. Jia Zhai from StreamNative shared about "Apache Pulsar: from messaging system to event streaming platform". Besides, Guangning E from StreamNative gave a talk about "How to connect Apache Pulsar to IoTDB with Pulsar IO". * Pulsar Summit SF was initially scheduled for Apr 28th though due to current situation it has been postponed to a TBD date after summer. - Work is ongoing for next release (2.6.0) and for to reach the first release for the native Go client library. ## Community Health: - There is healthy growth in the community, several users are starting to become contributors to the project and engaging more and more with the community. ## Membership Data: - There are currently 30 committers and 24 PMC members in this project. - The Committer-to-PMC ratio is 5:4. - Community changes, past quarter: * No new PMC members. Last addition was Penghui Li on 2019-09-16. * No new committers. Last addition was Liu Yu on 2019-11-28. ## Releases: - 2.5.0 was released on Dec. 6th 2019 - Pulsar-client-node 1.1.0 was released on Feb. 18th 2020 ## Mailing list activity: - Activity on the mailing lists remains high with a mixture of new users, contributors, and deeper more experienced users and contributors sparking discussion and questions and filing bugs or new features. - users@pulsar.apache.org: - 140 subscribers (+10 from Dec 2019) - 137 emails sent to list in last 3 months - dev@pulsar.apache.org: - 174 subscribers (+21 from Dec 2019) - 425 emails sent to list in last 3 months ## Slack activity: * 1673 Members (1311 in Dec 2019) * 234 Active weekly users (160 in Dec 2019) ## GitHub activity: - 438 PRs from 88 contributors (+11) were merged in the last 3 months - 278 Issues were created and 165 closed in the last 3 months - 5218 Stars (up from 4608 in Dec 2019) ----------------------------------------- Attachment BF: Report from the Apache River Project [Peter Firmstone] ## Description: - Apache River provides a platform for dynamic discovery and lookup search of network services. Services may be implemented in a number of languages, while clients are required to be jvm based (presently at least), to allow proxy jvm byte code to be provisioned dynamically. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Minimal activity at present, initial work on the modular build structure has commenced. The current monolithic build is complex, with it's own build tool classdepandjar, it adds complexity for new developers. In recent months I have had work committments that have limited my ability to integrate the modular build. The other committers are waiting for the modular build and I have done a lot of work on this locally, this work has been a significant undertaking integrating the works of Dennis Reedy, Dan Rollo and myself. This is also a mature codebase, having been in development since the late 1990's. - The monolithic code has been svn moved into modules into an initial maven build structure, next step is to move junit tests to each module. - Until the monolithic build has been broken up into maven modules, we are likely to have difficulty attracting new contributors due to the appearance of complexity. Release roadmap: - River 3.1 - Modular build restructure (& binary release) - River 3.2 - Input validation 4 Serialization, delayed unmarshalling & safe ServiceRegistrar lookup service. - River 3.3 - OSGi support ## Health report: - River is a mature codebase with existing deployments, it was primarily designed for dynamic discovery of services on private networks. IPv4 NAT limitations historically prevented the use of River on public networks, however the use of IPv6 on public networks removes these limitations. Web services evolved with the publish subscribe model of todays internet, River has the potential to dynamically discover services on IPv6 networks, peer to peer, blurring current destinctions between client and server, it has the potential to address many of the security issues currently experienced with IoT and avoid any dependency on the proprietary cloud for "things". - Future Direction: * Target IOT space with support for OSGi and IPv6 (security fixes required prior to announcement) * Input validation for java deserialization - prevents DOS and Gadget attacks. * IPv6 Multicast Service Discovery (River currently only supports IPv4 multicast discovery). * Delayed unmarshalling for Service Lookup and Discovery (includes SafeServiceRegistrar mentioned in release roadmap), so authentication can occur prior to downloading service proxy's, this addresses a long standing security issue with service lookup while significantly improving performance under some use cases. * Security fixes for SSL endpoints, updated to TLS v1.2 with removal of support for insecure cyphers. * Secure TLS SocketFactory's for RMI Registry, uses the currently logged in Subject for authentication. The RMI Registry still plays a minor role in service activation, this allows those who still use the Registry to secure it. * Maven build to replace existing ant built that uses classdepandjar, a bytecode dependency analysis build tool. * Updating the Jini specifications. ## Project Composition: There are currently 16 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 4:3. ## Community changes, past quarter: No new PMC members. Last addition was Dan Rollo on 2017-12-01. No new committers. Last addition was Dan Rollo on 2017-11-02. ## Project Release Activity: - Recent releases: * River-3.0.0 was released on 2016-10-06. * River-jtsk-2.2.3 was released on 2016-02-21. * River-examples-1.0 was released on 2015-08-10. ----------------------------------------- Attachment BG: Report from the Apache Royale Project [Piotr Zarzycki] ## Description: Apache Royale is a new implementation of the principles of Apache Flex, designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale improves developer productivity in creating applications to run wherever JavaScript runs, including on browsers as well as in Apache Cordova applications, Node, etc. ## Issues: There are no issues requiring board attention at this time. ## Releases: - Apache Royale 0.9.2 was released on March 16 2018. - Apache Royale 0.9.4 was released on November 14 2018. - Apache Royale 0.9.6 was released on October 1 2019 ## Membership Data: - Greg Dove was added as a new PMC member on October, 2019. ## Project Activity: - We are still investing a lot of time in supporting users who wanted to port their applications from Flex to Apache Royale. - Emulation of Flex components has been significantly improved. Developers can use emulation with success for porting most of their existing MX components and some Spark components. - We have made significant refactoring towards better modularization of item renderers. - Filled a gap in the Jewel UI set by adding ButtonBar and DataGrid. - Added Jewel VirtualList and VirtualComboBox to improve performance managing large collections of data. - Jewel Button got new "Outlined" and "Unboxed" styles. - Jewel got theme switch feature, implemented in Tour De Jewel example, to change themes at runtime. - Lots of improvements in Jewel UI Set (including resizing, themes, and disabling) - Added Routing infrastructure classes to allow "routing" or "deep linking" on SPA applications. - Added AMFLocalStorage to allow storing data on the user's machine with AMF encoding, removing the need to encode/decode to/from JSON. - Royale compiler gets an improvement in data binding area. - Royale Docs continues to be improved as the project develops. - Royale Docs for Crux were added. - We created two TodoMVC examples (from (todomvc.com)[http://www.todomvc.com] website), one using Jewel UI set and the other adding the Crux IoC framework). This example shows MVC good practices in Royale and many features like IoC, DI, Event Handling, Data Binding, Jewel Theme Customization, Routing and LocalStorage (with AMF). ## Community Health: We think it is important to do this so people outside the project and not following it on a daily basis can get a notion of how we are doing. The numbers are: - Our Twitter account has 643 (previously 610) followers. - Our Facebook page has 147 (previously 144) likes. - Our LinkedIn Group has 131 (previously 129) people. - Our StackOVerFlow "apache-royale" tag currently has 44 (previously 43) questions. - We recently added a Slack channel, "royale", in the-asf.slack.com workspace as an experiment to support real-time collaboration. - users@royale.apache.org: - 79 subscribers (up 1 in the last 3 months) - 1% increase in traffic in the past quarter (358 emails compared to 351) - dev@royale.apache.org: - 79 subscribers (no increase in the last 3 months) - 11% increase in traffic in the past quarter (1603 emails compared to 1444) ----------------------------------------- Attachment BH: Report from the Apache Sentry Project [Kalyan Kalvagadda] ----------------------------------------- Attachment BI: Report from the Apache Serf Project [Branko Čibej] ----------------------------------------- Attachment BJ: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ## Description: Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF and Karaf to provide a complete, enterprise-ready ESB powered by OSGi. ## Issues: There are no outstanding issues requiring board attention. ## Membership Data: Apache ServiceMix was founded 2007-09-19 (12 years ago) There are currently 50 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Andrea Cosentino on 2017-03-15. - No new committers. Last addition was Andrea Cosentino on 2016-03-13. ## Project Activity: - During the last period we have released 3 sets of OSGi bundles and Specs - Apache ServiceMix Specs (jaxb-api, jaxws-api, saaj-api) on January 08 2020 - Apache ServiceMix Bundles 2019.12 on January 08 2020 - Apache ServiceMix Bundles 2020.01 on February 03 2020 - During the next period we are going to provide - the next Bundles and Specs releases ## Community Health: Due to a low activity in the project and low interest to provide further releases of ServiceMix Assembly we are currently discussing about the future of the ServiceMix project. Our draft plan is to: - move the Bundles and Specs to Apache Karaf or provide in Apache Karaf a descriptor mechanism which lets us to avoid to provide a bundle for each Java library - provide a documentation explaining how to "migrate" from ServiceMix to Karaf "ecosystem". The purpose is to provide smooth path to ServiceMix users. - maybe provide an Integration distribution of Apache Karaf - provide in Apache Camel or Apache Karaf project a documentation about running integration in the Karaf "ecosystem" - move the ServiceMix project to attic ----------------------------------------- Attachment BK: Report from the Apache Shiro Project [Les Hazlewood] ## Description: Apache Shiro is a powerful and flexible open-source application security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. ## Issues: We have no issues that require Board assistance at this time. ## Membership Data: Apache Shiro was founded 2010-09-21 (9 years ago) There are currently 13 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Colm O hEigeartaigh on 2019-10-08. - No new committers. Last addition was Colm O hEigeartaigh on 2019-10-09. ## Project Activity: - As of the 1.5, Shiro requires Java 8+ - Feature development on master is going strong and helping modernize the project. ## Community Health: dev and user list activity has gone up this quarter Our latest committers / PMC members have been helping bring some new life to the project ----------------------------------------- Attachment BL: Report from the Apache SINGA Project [Wang Wei] According to [1], SINGA is supposed to submit the report in April because we reported monthly for the first 3 months, namely Nov., Dec., and Jan. Hence, we didn't prepare to report in March. Instead, we are going to report in April. [1] https://www.apache.org/foundation/board/reporting#when ----------------------------------------- Attachment BM: Report from the Apache Sling Project [Robert Munteanu] ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Sling was founded 2009-06-17 (11 years ago) There are currently 45 committers and 27 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Timothée Maret on 2019-06-21. - No new committers. Last addition was Angela Schreiber on 2019-10-30. ## Project Activity: Individual module releases continue at a good pace, 41 since the last board report. Efforts are ongoing for the release of the next release of our demo/sample app - the Sling Starter. ## Community Health: We have seen a recent uptick in community metrics. - dev@sling.apache.org had a 77% increase in traffic in the past quarter (3285 emails compared to 1853) - users@sling.apache.org had a 182% increase in traffic in the past quarter (48 emails compared to 17) - 263 issues opened in JIRA, past quarter (17% increase) - 237 issues closed in JIRA, past quarter (26% increase) - 881 commits in the past quarter (32% increase) ----------------------------------------- Attachment BN: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for March 2020 SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Status and health report: The project activities, including running our rule update infrastructure and our dev and user mailing lists, are continuing smoothly. SpamAssassin 3.4.4 was released on 28 January, 2020. It was primarily a security release, fixing two CVEs, all then known outstanding open security issues on the project. Release of SpamAssassin 3.4.5 is imminent, fixing a subsequently reported CVE level security issue. We intend to return our primary focus to development of version 4.0.0. Releases: The last release was Apache SpamAssassin version 3.4.4 on 28 January 2020. Note that we maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. Committer/PMC changes: Most recent new committer: Paul Stead (pds) 12 September 2018 Most recent new PMC members: Giovanni Bechis (gbechis) 24 Sep 2018 Henrik Krohns (hege) 25 Sep 2018 ----------------------------------------- Attachment BO: Report from the Apache Stanbol Project [Rafa Haro] ----------------------------------------- Attachment BP: Report from the Apache Storm Project [Kishor Patil] ## Description: The mission of Storm is the creation and maintenance of software related to Distributed, real-time computation system ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Storm was founded 2014-09-16 (5 years ago) There are currently 40 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members added in the last 3 months - No new committers added in the last 3 months ## Project Activity: - The team is currently working on fixing some bugs. - We may have a release next quarter to release all these fixes. - This is my first report to the board as PMC Chair for Storm. ## Community Health: - New contributors continue to engage and that engagement tends to keep up activity levels, even as some contributors move on. ----------------------------------------- Attachment BQ: Report from the Apache Submarine Project [Wangda Tan] # Submarine - Mar 2020 ## Description The Apache Submarine is a project which allows infra engineer/data scientist to run machine learning unmodified Tensorflow or PyTorch programs on YARN or Kubernetes. ## Issues There are no problematic issues requiring board attention. ## General ### Feature development of Submarine: The community is busy working on following features, continue efforts since last report. - Submarine Server and K8s Support for PyTorch and Tensorflow. - Submarine workbench for note book service. - Submarine workflow for ML applications. Overall the development from the community is good, we're talking to some contributors to see if we can get some of them to run the Submarine project management to help community move ahead. ## Membership Data: Apache Submarine was founded on 2019-10 There are currently 29 committers and 7 PMC members in this project. ### PMC changes, past quarter: - No new PMC member since last report. ### Committer base changes, past quarter: - Kevin Su (pingsutw) added since last report ## Project Activity: ### Releases - Community is actively working on 0.3.0 since last report, and 0.3.0 is released on Feb 1st, 2020. - 0.4.0 release is in planning stage, we're looking at sometime around May 2020 to release 0.4.0, which include a whole bunch of new features like notebook service, cloud deployment, etc. Roadmap for 0.4.0: https://cwiki.apache.org/confluence/display/SUBMARINE/Roadmap. ## Community Health: ### JIRA Activity Significantly up compared to last quarter - 112 JIRA tickets created since the past quarter [ 107 in ("Apache Submarine") AND createdDate >= 2019-12-11 ] - 131 JIRA tickets resolved since the past quarter [ pproject in ("Apache Submarine") AND resolutiondate >= 2019-12-11 ] - 40 JIRA tickets created since the past month [ project in ("Apache Submarine") AND createdDate >= 2020-02-11 ] - 48 JIRA tickets resolved since the past month [ project in ("Apache Submarine") AND resolutiondate >= 2020-02-11 ] ### Mailing list, slack channel, Github activities: - dev@submarine: 635 emails since Feb 11, 2020. There're 27 accounts participated the discussion, which up 22% comparing to last report. - Community sync up: Similar to last report. Submarine community sync up is very active now, weekly sync up has 10+ participants in the last several months. - There're close to 50 emails sent to users@submarine, we will encourage more users go to users list instead of sending emails to dev@submarine. - There're 204 stars of apache/submarine Github, which up from 182 since last report. ----------------------------------------- Attachment BR: 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 (12 years ago) There are currently 34 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 Prabath Ariyarathna on 2017-02-10. ## Project Activity: Project activity has increased in this quarter compared to the previous one. Even though there is no major activity from the existing committers, two new contributors are giving a new life to the project. They are active in making code contributions, fixing build failures, configuring Jenkins build, etc. So we are looking forward to moving the project in the right direction with the help of new contributors. ## Community Health: dev@synapse.apache.org had a 27% increase in traffic in the past quarter (46 emails compared to 36) 4 issues opened in JIRA, past quarter (100% increase) 1 issue closed in JIRA, past quarter 7 commits in the past quarter (600% increase) 3 code contributors in the past quarter (200% increase) 5 PRs opened on GitHub, past quarter (400% increase) 5 PRs closed on GitHub, past quarter (25% increase) Numbers have increased compared to last quarter mainly due to the contributions from new contributors. ----------------------------------------- Attachment BS: Report from the Apache Tajo Project [Hyunsik Choi] ## Description: The mission of Tajo is the creation and maintenance of software related to Big data warehouse system on Apache Hadoop ## Issues: - According to the attic process, we opened a discussion moving into the attic in dev/user mailing list. ## Membership Data: Apache Tajo was founded 2014-03-19 (6 years ago) There are currently 18 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 9:7. Community changes, past quarter: - No new PMC members. Last addition was Hyoung Jun Kim on 2014-12-07. - No new committers. Last addition was Jong-young Park on 2016-05-29. ## Project Activity: - 0.11.3 was released on 2016-05-18. - 0.11.2 was released on 2016-04-06. ## Community Health: - Very low activity in mailing list and Github PRs - 1 PR opened during the last quarter ----------------------------------------- Attachment BT: Report from the Apache Tomcat Project [Mladen Turk] ## Description: - A Java Servlet, JavaServer Pages, Java WebSocket and Java Unified Expression language specifications implementation. ## Issues: - There are no issues requiring board attention at this time ## Membership Data: - There are currently 28 PMC members. Igal Sapir was added to the PMC on Mar 18 2019 - There are currently 46 committers. Woonsan Ko was added as a committer on Dec 19 2018 ## Community Health: - Continued healthy activity across multiple components and responsiveness on both dev and user lists. ## Project Activity: - The Tomcat project has been awarded a Patch Reward from Google of $5,000 which we are working with fundraising and accounting to accept. The intention is to use it to subsidise a security focused committer meetup/ hackathon / BarCamp once the risks associated with COVID-19 subside. - Apache Tomcat 10.x is the current focus of development. It builds on Tomcat 9.0.x and implements the Servlet 5.0, JSP 3.0, EL 4.0, WebSocket 2.0 and Authentication 2.04 specifications (the versions required by Jakarta EE 9 platform). - Apache Tomcat 10.0.0-M1 was released on 2020-02-20 - Apache Tomcat 9.0.31 was released on 2020-02-11 - Apache Tomcat 9.0.30 was released on 2019-12-12 - Apache Tomcat 8.5.51 was released on 2020-02-11 - Apache Tomcat 8.5.50 was released on 2019-12-12 - Apache Tomcat 7.0.100 was released on 2020-02-14. - Apache Tomcat Connectors 1.2.48 wa released on 2020-03-06 ## Security: - Detailed status: http://tomcat.apache.org/security.html ## Trademark: - No new trademark issues in the last 3 months and there are currently no outstanding trademark issues that the Apache Tomcat PMC is working on. - Detailed history is available at: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt ----------------------------------------- Attachment BU: Report from the Apache Trafodion Project [Pierre Smits] ## Description: The mission of Apache Trafodion is the creation and maintenance of software related to webscale SQL-on-Hadoop solution enabling transactional or operational workloads. ## Issues: There are no issues requiring board attention at this time. ## Project Activity: - In the last month of the quarter a new suggestion to consider a contributor for privileges was brought before the PMC. The PMC has started a vote on that suggestion in the last days of the quarter. - No security issues were reported. ## Community Health: - Subscriptions to the (public) mailing lists showed stable numbers compared to previous quarter (for details see section Mailing List activity below). - Compared to previous quarter, the community involvement showed a stable participation on the dev and user mailing list. - The PMC regards the project as healthy (Community Health Score: 2.25). ## Membership Data: Apache Trafodion was founded 2017-12-20 (2 years ago) There are currently 24 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Anoop Sharma on 2018-12-06. - No new committers. Last addition was Prashanth Vasudev on 2018-11-13. ## Releases: - Last release was 2.3.0 on Wed Feb 27 2019 ## Other project statistics Mailing Lists: - dev@trafodion.apache.org: - 88 subscribers (down -4 in the last 3 months): - no accurate insight can be provided through ComDev-reporter services - codereview@trafodion.apache.org: - 24 subscribers (up 0 in the last 3 months): - no accurate insight can be provided through ComDev-reporter services - issues@trafodion.apache.org: - 31 subscribers (down 2 in the last 3 months): - no accurate insight can be provided through ComDev-reporter services - user@trafodion.apache.org: - 102 subscribers (down 0 in the last 3 months): - no accurate insight can be provided through ComDev-reporter services - security@trafodion.apache.org: - 3 subscribers (down 3 in the last 3 months): - Currently no automated insights in number of ml postings provided by ComDev-reporter services. - private@trafodion.apache.org: - 17 subscribers (down 3 in the last 3 months): - Currently no automated insights in number of ml postings provided by ComDev-reporter services. - JIRA activity - 3 issues created in the reporting period (Down 57%) - 3 issues closed/resolved in the reporting period (Up 50%) - GitHub Actviities: - PR opened: 7 (Down 25%) - PR closed: 8 (Down 20%) - Commit activities: - commits: 18 (Down 5%) - active contributors: 4 (Up 25%) ----------------------------------------- Attachment BV: Report from the Apache Twill Project [Terence Yim] ----------------------------------------- Attachment BW: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for March 2020. ## Description: Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. The software provides frameworks, tools and annotators, facilitating the analysis of unstructured content such as text, audio and video. ## Membership Data: Apache UIMA was founded 2010-03-16 (10 years ago) There are currently 25 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Viorel Morari on 2019-11-18. - No new committers. Last addition was Viorel Morari on 2018-09-20. ## Project Activity: ### Releases: No releases in last quarter ## Activity: Major work continues on getting the uima-cpp (the C++ support) working on modern versions of Linux. UIMA Issues at a slow/moderate pace are continuing to be reported and fixed in core UIMA, uimaFIT, Ruta, uima-as, and uima-ducc. A request to INFRA to move the uima-as project to GIT from SVN was made January 20, and we're awaiting INFRA action on this. ( https://issues.apache.org/jira/browse/INFRA-19750 ) ## Community Health: The community continues to be moderately active. ## Issues: No Board level issues at this time. ----------------------------------------- Attachment BX: Report from the Apache Unomi Project [Serge Huber] ## Description: The mission of Apache Unomi is the creation and maintenance of software related to providing a reference implementation of the OASIS Customer Data Platform specification currently being worked on by the OASIS Context Server Technical Committee ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Unomi was founded 2019-02-20 (a year ago) There are currently 12 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was David Griffon on 2019-02-20. - No new committers. Last addition was Taybou on 2019-04-01. ## Project Activity: The project has seen some great progress towards the next upcoming releases, notably: - new contributors that are working on the implementation of the CDP GraphQL specification (slated for 2.0) - new extensive documentation of the data model - updates to the latest version of Apache Karaf. - improvements in the back-end, notably new ways to query CDP objects - JDK 11 support Recent releases: 1.4.0 was released on 2019-05-24. 1.3.0-incubating was released on 2018-08-23. 1.2.0-incubating was released on 2017-09-28. ## Community Health: The community is really growing now, we have seen a lot of new (unknown) people get interested in the project, and what is even more interesting is the fact that they are quick to contribute. A few new companies have been integrating the technology and their engineers are contributing back to the project which is really encouraging to see, it seems like the efforts around communication and onboarding have helped. It is a focus of the PMC to get people involved quickly and easily, and a high priority is put on answering PRs or any requests. A lot of activity is also happening on the Slack channel, where people prefer to go for short/quick questions. It would be great to be able to reflect this somehow in the reports. - dev@unomi.apache.org had a 1% decrease in traffic in the past quarter (302 emails compared to 305) - users@unomi.apache.org had a 52% increase in traffic in the past quarter (32 emails compared to 21) - 13 issues opened in JIRA, past quarter (18% increase) - 5 issues closed in JIRA, past quarter (-50% decrease) - 69 commits in the past quarter (-46% decrease) - 9 code contributors in the past quarter (-10% decrease) - 18 PRs opened on GitHub, past quarter (no change) - 17 PRs closed on GitHub, past quarter (-5% decrease) ----------------------------------------- Attachment BY: Report from the Apache VCL Project [Josh Thompson] ## Description: The mission of the Apache VCL project is to create and maintain software related to a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache VCL was founded 2012-06-19 (8 years ago) There are currently 10 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2012-06-19. - No new committers. Last addition was Mike Jennings on 2019-01-04. ## Project Activity: Project activity has been pretty light over the last quarter. Committers seem to mostly have been busy with day job tasks. ## Community Health: The VCL community is somewhat small and quiet, but still healthy. We will be having a discussion and vote on adding our newest committer to the PMC within the next month or so. ----------------------------------------- Attachment BZ: Report from the Apache Wicket Project [Andrea Del Bene] ## Description: Apache Wicket is an open source Java component oriented web application framework. ## Issues: No issues require board attention. ## Membership Data: Apache Wicket was founded 2007-06-20 (13 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: - No new PMC members. Last addition was Ernesto Reinaldo Barreiro on 2019-08-14. - No new committers. Last addition was Ernesto Reinaldo Barreiro on 2019-08-13. ## Project Activity: On January we had a new release cycle involving version 7.x, 8.x and 9.x (this last is in development). As result on the same month we reached a new downloads record touching 480k downloads via Maven repositories. As of the writing we are preparing to release a new Milestone (the fifth) before the finally releasing Wicket 9. In this Milestone we have introduced the last major feature which is CSP (Content Security Policy) support. The development of this feature has been lead by Emond Papegaaij. The release of Wicket 9 should shortly (a couple of months) follow this last Milestone. ## Community Health: The community is stable and healthy. Questions to the user list and dev list are answered, resolved and discussed. In the last quarter we have also seen some very interesting Wicket-related activities and projects outside the Apache community: -On Udemy Ansgar Schulte created a German-based course on Apache Wicket: https://www.udemy.com/course/apache-wicket-kompakt/ -Robin Shen presented OneDev, an open source, Wicket-based, all-in-one devops platform that is rapidly gaining a notable interest on GitHub: https://github.com/theonedev/onedev -Roman Sery has started his new blog almost entirely dedicated to Apache Wicket: https://www.coderdreams.com/ -Martin Grigorov has successfully tested Wicket with Apache tomcat 10 M1: https://twitter.com/mtgrigorov/status/1225359299570028546 -Bruno Borges has run some interesting experiments with Wicket and Quarkus https://github.com/brunoborges/wicket-with-quarkus ----------------------------------------- Attachment CA: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J Xerces-J 2.12.1 was released a the beginning of January. This is a bug fix release which makes it possible to compile the source with Java 9+ and mostly addresses issues in Xerces' XML Schema processor. As usual, the community has been helping with publishing the binaries to Maven central. Since the release there's been a couple updates to the documentation but no other activity to report. Mailing list traffic has been low; roughly 80+ posts on the j-dev and j-users lists since the beginning of December 2019. The latest release is Xerces-J 2.12.1 (January 11th, 2020). Xerces-C Xerces-C has finally completed its migration to Git. The project has been using it since the beginning of January. The community has already been submitting pull requests with enhancement and bug fix suggestions. A few of them have been reviewed. While doing that, the developers have been debating what the threshold is for requiring a contributor to sign the Apache CLA (trivial one-line fixes vs. substantial work) before accepting their pull request. Since the beginning of March there's been discussion about the creation of a branch for Xerces-C 3.3 to allow for some necessary changes to the API. It was recently decided that master would be used for this purpose. Xerces-C 3.2 was pushed to a branch. Mailing list traffic has been high; roughly 240+ posts on the c-dev and c-users lists since the beginning of December 2019. No new releases since the previous report. The latest release is Xerces-C 3.2.2 (September 19th, 2018). Xerces-P Nothing in particular to report. There was no development activity over the reporting period. XML Commons No activity over the reporting period. Committer / PMC Changes The most recent committers were added in April 2017 (Xerces-C) and May 2017 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. Four committers have committed changes to SVN and Git since December 2019. ----------------------------------------- Attachment CB: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: The mission of Yetus is the creation and maintenance of software related to Collection of libraries and tools that enable contribution and release processes for software projects ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Yetus was founded 2015-09-15 (4 years ago) There are currently 12 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Akira Ajisaka on 2018-12-17. - No new committers. Last addition was Akira Ajisaka on 2018-02-06. ## Project Activity: Patches are trickling in for an eventual 0.12.0 release! It looks like we have folks using Apache Yetus in new and interesting ways and hitting bugs and/or missing features or usability problems. Frankly, it is quite exciting and hope it leads to more community growth which will lead to more contributions which will lead to more committers which will lead to more PMC members. That said, given some of the critical issues that have been filed, a 0.12.0 will come sooner rather than later . . . ## Community Health: As usual, a new year == more activity. But to me the interesting thing is how much our workflows are moving to GitHub vs. JIRA+mailing lists: While both have had interesting discussions just in the past month, there is no denying where stuff is happening: * dev@yetus.apache.org had a 8% increase in traffic in the past quarter (39 emails compared to 36) * gitbox@yetus.apache.org had a 280% increase in traffic in the past quarter (133 emails compared to 35) Our workflow is basically open a JIRA, then either open a GitHub PR with your change or attach a patch file to JIRA. It's obvious what is the preferred path: * 25 issues opened in JIRA, past quarter (56% increase) * 18 issues closed in JIRA, past quarter (125% increase) * 14 PRs opened on GitHub, past quarter (40% increase) * 13 PRs closed on GitHub, past quarter (30% increase) ----------------------------------------- Attachment CC: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables the implementation of a variety of primitives and mechanisms that are critical for safety and liveness in distributed settings, e.g., distributed locks, master election, group membership, and configuration. ## Issues: There are no issues requiring board attention ## Membership Data: Apache ZooKeeper was founded 2010-11-17 (9 years ago) There are currently 27 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 9:5. Community changes, past quarter: - Enrico Olivelli was added to the PMC on 2020-01-15 - No new committers. Last addition was Brian Nixon on 2019-09-24. ## Project Activity: - Recent releases: * 3.6.0 was released on 2020-03-03. * 3.5.7 was released on 2020-02-14. * 3.5.6 was released on 2019-10-18. - No new security vulnerability reported ## Community Health: The community has worked on three releases in this period: two bug-fix releases and one major release. The activity increase observed across the dev list, issues opened/closed, commits and code contributions reflects all the effort from the community to cut all these releases. It was certainly a good quarter for the project. Health indicators: - dev@zookeeper.apache.org had a 13% increase in traffic in the past quarter (1170 emails compared to 1034) - issues@zookeeper.apache.org had a 27% decrease in traffic in the past quarter (788 emails compared to 1065) - 106 issues opened in JIRA, past quarter (no change) - 65 issues closed in JIRA, past quarter (30% increase) - 166 commits in the past quarter (107% increase) - 30 code contributors in the past quarter (20% increase) - 103 PRs opened on GitHub, past quarter (10% increase) - 80 PRs closed on GitHub, past quarter (1% increase) ------------------------------------------------------ End of minutes for the March 18, 2020 board meeting.