The Apache Software Foundation Board of Directors Meeting Minutes May 15, 2019 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:33 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/3uqu The meeting was held via teleconference, hosted by Doug Cutting and Cloudera. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Rich Bowen Shane Curcuru Myrle Krantz Daniel Ruggeri Craig L Russell Roman Shaposhnik Joan Touzet Directors Absent: Jim Jagielski Phil Steitz Executive Officers Present: Tom Pappas Sam Ruby Matt Sicker Executive Officers Absent: Ross Gardler Ulrich Stärk Guests: Brian Fitzpatrick Daniel Gruno Danny Angus David Nalley Geoff Macartney Greg Stein Gris Cuevas - joined 12:50 Henri Yandell Kevin A. McGrail Robin Anil Sally Khudairi 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of April 17, 2019 See: board_minutes_2019_04_17.txt Approved by General Consent. 4. Executive Officer Reports A. Acting Chairman [Shane] The board and executive officers are gathered this week for our F2F meeting to plan strategy and improve our decision-making and communications for internal operations. Along with our 20th anniversary, growth in our projects, and many ApacheCon and Roadshow events planned for the year, we have a lot of positive things going on. The board extends an *immense* thank you to Phil Steitz (who recently stepped down as Chairman) and Ross Gardler (recently stepped down as EVP), and recognize the years of thoughtful service they have performed in those and prior roles. Shane Curcuru, as Vice Chairman, will Chair this week's meetings as per our bylaws #6.2. B. President [Sam] I've posted a draft budget as a discussion item. I don't think it is fair or appropriate to ask for it to be approved at this time. My ideal is that we should do the budget in two passes: one a rough cut where we identify priorities, and then a second pass where we commit to expenses. That is the basis for the 5 year projection and 1 year budget rhythm. This failed for a number of reasons, all of which point back to me needing to make the process more clear. The key failure was where in previous years we had projected significant deficits and that suggested fiscal conservationism in what we attempted to do, this time we projected basically a balanced budget and large bank balance. So I requested that people come forward with their wish lists, which took longer than expected. Unfortunately, once it arrived the 1 year projection did not line up with the 5 year plan: it once again showed a significant deficit. Another complicating factor is that my instructions were unclear. Some broke out wish list items. Others included them in their FY20 budget requests. This needs to be sorted out. The good news is that we continue to be acting fiscally responsibly, and we continue to have a substantial bank balance. There is no need to rush a budget. - - - Brand management is seeking review of a downstream distribution policy. Sponsor Ambassadors are current in Fundraising; working with Virtual on business development/growth As always, Marketing and Publicity is not only chugging along, but providing invaluable assistance in fundraising and conferences No issues in infrastructure Conferences are doing well Travel Assistance has gotten to a late start, but I've chatted with Gavin and there should be progress by the board meeting. - - - Much of the effort this month has surrounded supporting the proposal for a Diversity and Inclusion President's committee. I'm sad to see that this contributed to Ross's need to step down. I'm recommending David Nalley as his replacement. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] Operating Cash on April 30, 2019 was $2,409.0K, which is down $92.5K from last month's ending balance (Mar 19) of $2,501.5K. Total Cash as of April 30, 2019 is $3,802.8K (includes the Pineapple and restricted Donation) as compared to $2,964.4K on April 30th 2018 (an increase of $838.4K year over year). The April 2019 ending Operating cash balance of $2,409.0K represents an Operating cash reserve of 16.7 months based on the FY19 Cash forecast average monthly spending of $144.5K/month (this will most change for FY20, as there was a fair amount of budgeted spend in FY19 that has not occurred but may in FY20 as we continue to work on the budget). The ASF actual Operating reserve of 16.7 months at the end of April 2019 is ahead of the budgeted 11.6 month reserve for YTD through April 2019. The ASF Operating reserve continues to be very healthy for an organization of the ASF's size and Operating activity. Reviewing the YTD Cash P&L, total Revenue is ahead of FY18 by $256.2K. As compared to the FY19 Budgeted revenue, we are ahead by $413.4K. YTD expenses, through April 30, 2019 are under budget by $162.2K. All departments, except for Total Conferences, are under budget, at the end of April 2019. Total Conferences is over budget because we put a 75% down payment on ACEU19 of $229.6K plus VAT of $43.3K. With regards to the areas that are under budget, one being Infra, as noted in the Board summary is $263.2K under budget due to the timing of hiring of staff (though this did change in April 19 as they have hired two new staff members, Congrats) and not having to pay any Lease web invoices YTD, thank you Fundraising. The other being TAC at $50K under budget for FY19. Regarding Net Income (NI), YTD FY19 the ASF finished with a positive $331.0K NI vs a budgeted negative <$244.5K> NI or $575.5K ahead of Budget, NI, for FY19. This is attributable to timing of some Sponsor payments as well as more Donations than were budgeted as well as underspending in most depts YTD vs the FY19 Budget. In comparison to last year, FY19 revenue exceeds FY18's by $256.2K as noted above; similarly, expenses exceed last year's by $483.1K. Thus, year over year NI for FY19 is behind FY18 by $226.9K. Current Balances: Boston Private CDARS Account 2,250,000.00 Citizens Money Market 1,078,065.15 Citizens Checking 473,525.77 Paypal - ASF 1,248.97 Total Checking/Savings 3,802,839.89 Apr-19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 4,084.24 1,817.30 2,266.94 Sponsorship Program 32,000.00 210,000.00 -178,000.00 Programs Income 0.00 0.00 0.00 Conference/Event Income 140.00 0.00 140.00 Other Income 701.85 512.27 189.58 Interest Income 546.63 875.61 -328.98 Total Income 37,472.72 213,205.18 -175,732.46 Expense Summary In Kind Expense 0.00 0.00 0.00 Infrastructure 70,889.49 78,128.36 -7,238.87 Programs Expense 0.00 0.00 0.00 Publicity 23,903.23 16,479.54 7,423.69 Brand Management 1,582.09 8,166.66 -6,584.57 Conferences 13,704.73 20,500.00 -6,795.27 Travel Assistance Committee 54.50 10,000.00 -9,945.50 Fundraising 11,250.00 17,333.32 -6,083.32 Treasury Services 3,350.00 3,475.00 -125.00 General & Administrative 5,657.93 2,179.56 3,478.37 Total Expense 130,391.97 156,262.44 -25,870.47 Net Income -92,919.25 56,942.74 -149,861.99 YTD FY19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 135,583.80 120,699.59 14,884.21 Sponsorship Program 1,617,371.47 1,299,000.00 318,371.47 Programs Income 17,200.00 14,400.00 2,800.00 Conference/Event Income 257,466.49 184,000.00 73,466.49 Other Income 31,001.54 19,300.41 11,701.13 Interest Income 6,557.70 14,400.00 -7,842.30 Total Income 2,065,181.00 1,651,800.00 413,381.00 Expense Summary In Kind Expense 0.00 0.00 0.00 Infrastructure 702,347.35 965,540.00 -263,192.65 Programs Expense 0.00 4,400.00 -4,400.00 Publicity 232,702.58 238,300.00 -5,597.42 Brand Management 59,749.66 98,000.00 -38,250.34 Conferences 513,273.00 244,500.00 268,773.00 Travel Assistance Committee 15,054.50 65,000.00 -49,945.50 Fundraising 145,268.64 208,000.00 -62,731.36 Treasury Services 45,170.00 46,200.00 -1,030.00 General & Administrative 20,610.04 26,399.98 -5,789.94 Total Expense 1,734,175.77 1,896,339.98 -162,164.21 Net Income 331,005.23 -244,539.98 575,545.21 D. Secretary [Matt] This is the first month that Matt has been Secretary while Craig has continued knowledge transfer and guidance on the position. The office of Secretary continues to run well with continued improvements in Whimsy tooling. In April, 77 ICLAs, two CCLAs, two software grants, three emeritus requests, and ten membership applications were filed. E. Executive Vice President [Ross] For personal reasons I have tendered my resignation. F. Vice Chairman [Shane] Assisted with organizing agenda for upcoming Board F2F; this meeting will be a great opportunity to welcome new faces to the board and make progress on strategic planning for the ASF's future. Thanks in advance to our hosts and all our officer attendees. Kicked off an informal New Member Mentoring program, to help newly elected Members find their way around our corporate operations and governance. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Joan] See Attachment 8 B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Craig] See Attachment 10 D. VP of Data Privacy [John Kinsella / Roman] See Attachment 11 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Cocoon [rs] # Crunch [druggeri] # Forrest [rb] # Hama [mk] # Impala [mk] # Joshua [clr] # Kylin [rb] # Lens [mk] # Mesos [wohali] # Open Climate Workbench [rb] # Perl [mk, druggeri] # TomEE [jj] # Twill [wohali] A. Apache Ambari Project [Jayush Luniya / Shane] See Attachment A B. Apache Ant Project [Jan Materne / Jim] See Attachment B C. Apache BookKeeper Project [Sijie Guo / Phil] See Attachment C D. Apache Brooklyn Project [Geoff Macartney / Daniel] See Attachment D E. Apache Buildr Project [Antoine Toulme / Rich] See Attachment E F. Apache Cassandra Project [Nate McCall / Myrle] See Attachment F G. Apache Clerezza Project [Hasan Hasan / Phil] See Attachment G H. Apache Cocoon Project [Cédric Damioli / Roman] See Attachment H @Roman: Follow up with PMC about activity I. Apache Community Development Project [Sharan Foga / Joan] See Attachment I J. Apache CouchDB Project [Jan Lehnardt / Daniel] See Attachment J K. Apache Creadur Project [Brian E Fox / Jim] No report was submitted. @Shane: pursue a report for Creadur L. Apache Crunch Project [Josh Wills / Rich] See Attachment L M. Apache DeltaSpike Project [Mark Struberg / Shane] See Attachment M N. Apache DRAT Project [Tom Barber / Myrle] See Attachment N O. Apache Drill Project [Arina Ielchiieva / Craig] See Attachment O P. Apache Empire-db Project [Rainer Döbele / Jim] See Attachment P Q. Apache Flume Project [Ferenc Szabo / Joan] See Attachment Q R. Apache Forrest Project [David Crossley / Roman] See Attachment R @Rich: open up attic discussions to dev list S. Apache FreeMarker Project [Dániel Dékány / Phil] See Attachment S T. Apache Geode Project [Karen Miller / Myrle] See Attachment T U. Apache Giraph Project [Dionysios Logothetis / Rich] See Attachment U V. Apache Gora Project [Kevin Ratnasekera / Daniel] See Attachment V W. Apache Groovy Project [Paul King / Craig] See Attachment W X. Apache Hama Project [Chia-Hung Lin / Shane] See Attachment X @Myrle: follow up about report Y. Apache HTTP Server Project [Daniel Gruno / Joan] See Attachment Y Z. Apache HttpComponents Project [Asankha Chamath Perera / Jim] See Attachment Z AA. Apache Ignite Project [Denis A. Magda / Phil] See Attachment AA AB. Apache Impala Project [Jim Apple / Myrle] See Attachment AB @Myrle: follow up about trademark issue AC. Apache Incubator Project [Justin Mclean / Rich] See Attachment AC @Joan: follow up about reporting improvements for Incubator AD. Apache Joshua Project [Tommaso Teofili / Craig] No report was submitted. @Craig: pursue a report for Joshua AE. Apache jUDDI Project [Alex O'Ree / Daniel] See Attachment AE AF. Apache Juneau Project [James Bognar / Roman] See Attachment AF AG. Apache Kafka Project [Jun Rao / Shane] See Attachment AG AH. Apache Kibble Project [Rich Bowen] See Attachment AH AI. Apache Knox Project [Larry McCay / Shane] See Attachment AI AJ. Apache Kylin Project [Luke Han / Myrle] See Attachment AJ AK. Apache Lens Project [Amareshwari Sriramadasu / Rich] See Attachment AK @Rich: pursue a PMC roll call AL. Apache Libcloud Project [Tomaž Muraus / Phil] See Attachment AL AM. Apache Logging Services Project [Matt Sicker / Craig] See Attachment AM AN. Apache ManifoldCF Project [Karl Wright / Roman] See Attachment AN AO. Apache Marmotta Project [Jakob Frank / Jim] See Attachment AO AP. Apache Mesos Project [Benjamin Hindman / Joan] See Attachment AP @Joan: follow up with project AQ. Apache MetaModel Project [Kasper Sørensen / Daniel] See Attachment AQ AR. Apache NetBeans Project [Geertjan Wielenga / Daniel] See Attachment AR AS. Apache Oozie Project [Gézapeti / Joan] See Attachment AS AT. Apache Open Climate Workbench Project [Huikyo Lee / Shane] See Attachment AT @Rich: find out what the sentence in Issues means AU. Apache Perl Project [Philippe Chiasson / Myrle] No report was submitted. @Roman: pursue a PMC roll call @Daniel: also pursue the PMC roll call AV. Apache Phoenix Project [Josh Elser / Phil] See Attachment AV AW. Apache PLC4X Project [Christofer Dutz / Roman] See Attachment AW AX. Apache POI Project [Dominik Stadler / Craig] See Attachment AX AY. Apache Qpid Project [Robert Gemmell / Rich] See Attachment AY AZ. Apache REEF Project [Sergiy Matusevych / Jim] See Attachment AZ BA. Apache River Project [Peter Firmstone / Shane] No report was submitted. @Shane: pursue a report for River BB. Apache RocketMQ Project [Xiaorui Wang / Craig] See Attachment BB BC. Apache Roller Project [David M. Johnson / Myrle] See Attachment BC BD. Apache Santuario Project [Colm O hEigeartaigh / Rich] See Attachment BD BE. Apache Serf Project [Branko Čibej / Jim] See Attachment BE BF. Apache ServiceComb Project [Willem Ning Jiang / Phil] No report was submitted. @Roman: pursue a report for ServiceComb BG. Apache SIS Project [Martin Desruisseaux / Daniel] See Attachment BG BH. Apache SkyWalking Project [Sheng Wu / Joan] See Attachment BH BI. Apache Spark Project [Matei Alexandru Zaharia / Roman] See Attachment BI BJ. Apache Subversion Project [Stefan Sperling / Roman] See Attachment BJ BK. Apache Syncope Project [Francesco Chicchiriccò / Daniel] See Attachment BK BL. Apache SystemML Project [Jon Deron Eriksson / Myrle] See Attachment BL BM. Apache TomEE Project [David Blevins / Jim] See Attachment BM @Craig: start thread on changing reporting deadline @Rich: propose new PMC chair due to consistently late reports BN. Apache Traffic Control Project [David Neuman / Craig] See Attachment BN BO. Apache Turbine Project [Georg Kallidis / Shane] See Attachment BO BP. Apache Twill Project [Terence Yim / Joan] See Attachment BP @Joan: pursue a PMC roll call and project activity status BQ. Apache Unomi Project [Serge Huber / Phil] See Attachment BQ BR. Apache Usergrid Project [Michael Russo / Rich] See Attachment BR BS. Apache Velocity Project [Nathan Bubna / Shane] See Attachment BS BT. Apache Whimsy Project [Sam Ruby / Myrle] See Attachment BT BU. Apache Xalan Project [Gary D. Gregory / Daniel] See Attachment BU BV. Apache Xerces Project [Michael Glavassevich / Phil] See Attachment BV BW. Apache XML Graphics Project [Clay Leeds / Roman] See Attachment BW Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache the Apache Diversity and Inclusion Committee WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to appoint a Committee responsible for diversity and inclusion matters, including but not limited to strategic planning, providing a framework and tools to support diversity and inclusion initiatives, and advising communities on matters related to diversity and inclusion. NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President, Diversity and Inclusion" be and hereby is created, the person holding such office to serve at the direction of the President, and to have primary responsibility of managing the ASF's diversity and inclusion strategy; and be it further RESOLVED, that the responsibilities of the Vice President of Diversity and Inclusion shall henceforth include management of the Diversity and Inclusion Committee as its chair; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Diversity and Inclusion Committee: * Rich Bowen * Griselda Cuevas Zambrano * Shane Curcuru * Ross Gardler * Daniel Gruno * Dinesh Joshi * Kenneth Knowles * Myrle Krantz * Justin Mclean * Sam Ruby * Craig L Russell * Naomi Slater * Joan Touzet * Kevin A. McGrail * Bertrand Delacretaz * Austin Bennett * Aizhamal Nurmamat kyzy * Shawn McKinney NOW, THEREFORE, BE IT FURTHER RESOLVED, that Griselda Cuevas Zambrano be appointed to the office of Vice President, Apache Diversity and Inclusion, to serve in accordance with and subject to the direction of the President and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Establish the Apache the Apache Diversity and Inclusion Committee, was approved by Unanimous Vote of the directors present. B. Establish the Apache Dubbo Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a high-performance, lightweight, java based RPC framework. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Dubbo Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Dubbo Project be and hereby is responsible for the creation and maintenance of software related to a high-performance, lightweight, java based RPC framework; and be it further RESOLVED, that the office of "Vice President, Apache Dubbo" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Dubbo Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Dubbo Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Dubbo Project: * Huxing Zhang * Ian Luo * Jun Liu * Justin Mclean * Kimm King * Liang Zhang * Liujie Qin * Mercy Ma * Minxuan Zhuang * Shang Zonghai * Von Gosling * Xin Wang * Yong Zhu * Yuhang Xiu * YunKun Huang NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ian Luo be appointed to the office of Vice President, Apache Dubbo, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Dubbo Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Dubbo podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Dubbo podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7B, Establish the Apache Dubbo Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. ComDev supports formation of D&I committee The ComDev PMC hereby requests that the board create a President's committee tasked with supporting our communities in their efforts to be diverse and welcoming places, and tasked with helping the ASF formulate a strategy to improve our diversity and inclusiveness. The ComDev PMC likewise formally requests that the new committee look for ways in which ComDev can support our progress in these areas. B. FY 20 Budget FY20 budget FY19 FY24 FY20 Income Total Public Donations 140 190 150 Total Sponsorship 1,299 2,149 1,309 Total Programs 14 31 171 ? Conference Sponsorships 184 184 184 Interest Income 14 2 11 ? ---- ---- ---- Total Income 1,651 2,556 1,825 Expense Infrastructure 966 1,082 1,053 Program Expenses 4 32 9 ? Publicity 238 388 403 Brand Management 98 143 98 Conferences 245 245 175 Travel Assistance 65 65 65 ? Treasury 46 64 49 ? Fundraising 208 234 193 General & Administrative 16 12 15 ? Board face-to-face 10 10 10 ---- ---- ---- Total Expense 1,896 2,275 2,070 Net -245 281 -245 Cash 3,657 2,142 3,412 Notes: * Units are in thousands of dollars US. * FY19 income/expense represents budget authorization, not actuals FY19 Cash, however, represents current (conservative) projections and DOES include the Pineapple fund. * FY24 column is for informational purposes only Wishlist: Technical writer: 40 ASF Travel Fund 50 Small Event Funding 125 Information Architect Unsized Expense tracking tool Unsized C. Appoint new EVP With Ross's recent resignation, we have a vacancy to fill. Ross has recommended Bertrand Delacretaz for the role, and Sam has recommended David Nalley. David Nalley was appointed to EVP by general consent. D. Statement of Expectation of Conduct of Board Members Discuss, adopt and publish text akin to the following: Board members are held to a much higher standard than regular ASF members or VPs. This includes strict hat wearing, equitable decision making, and exemplary conduct. People look to the Board of Directors for cues about how to behave, especially on mailing lists and in public. It is important that all Directors understand the responsibility that they bear, and that they are individually committed to improving themselves and the Foundation. This could be considered to be extended to the Officers of the Foundation as well. @Tom: research what other nonprofits do for CoCs for boards This discussion item was tabled. E. Publishing of vote records Discuss whether the full voting record (of who votes Yes/Abstain/No) on each Board vote should or needs to be published publicly. If not, discuss whether the full voting record (of who votes Yes/Abstain/No) on each Board vote should be published internally, confidentially, for any Member to review. @Daniel: begin a discussion on the lists about this F. Convention of semantics of Board votes Discuss the semantics of a Director voting Yes, Abstain or No on any given item. Attempt to reach consensus on what these votes mean, with specific reference as to whether or not the expectation is that all Board votes should be unanimous or not. @Roman: create a framework of vote meanings Topic was tabled. G. Address board-level public communications In the past few weeks we have had a series of discussions at the board and membership level that have been viewed as non-productive and potentially harmful to the effectiveness of how ASF conducts its daily business. While, when viewed in historic context, this may not be a new pattern it seems it has reached the severity that requires us to have an active discussion at the board level. This item captures this need for discussion in the hopes that we can map out a plan for a plan and present it at the next board meeting. 9. Review Outstanding Action Items * Phil: reach out to PPMC to see about improving the governance of the project. [ Incubator 2019-01-16 ] Status: * Roman: ping community about activity [ Marmotta 2019-02-20 ] Status: * Rich: follow up with web issue for mod_pagespeed [ Serf 2019-02-20 ] Status: Still open. I sent another message to the Incubator list this week. We'll see if anything comes of that. * Phil: pursue a report for Data Privacy [ Data Privacy 2019-03-20 ] Status: * Phil: pursue a report for Joshua [ Joshua 2019-03-20 ] Status: * Jim: Work with Roman to close out VP Jakarta action item [ Legal Affairs 2019-04-17 ] Status: ongoing * Rich: Look into activity and assess state of project [ Apex 2019-04-17 ] Status: There is a discussion on the pmc list - https://lists.apache.org/thread.html/ceb508142bb1d970bcb82bd9926f835afc17914edc771c4925c367e0@%3Cprivate.apex.apache.org%3E - in which the Chair wants to step down, and someone has volunteered to step up. At the same time, the thread is going into Attic territory. Meanwhile there was no response to the "Board feedback" email. I'll ask the question more directly, Update: The PMC plans to hold a vote on replacing their chair with Pramod Immaneni * Jim: Follow up with ODE PMC about options regarding rebooting the project in [ ODE 2019-04-17 ] Status: ongoing 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 11:42 a.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] * ISSUES FOR THE BOARD Feedback on the draft downstream distribution policy welcome. It is essentially trying to document the status quo rather than set new policy. * OPERATIONS Covering the period April 2019 Responded to the following queries, liaising with projects as required: - 3 enquiries about using logos (APACHE,CASSANDRA, KAFKA) - 1 enquiry about using a derivative logo (HADOOP/SPARK) - approved 1 podling name (DATASKETCHES) - 1 enquiry about merchandise (BIG DATA) - 2 enquiries about screenshots (NETBEANS, HTTPD) - approved 2 3rd party events (HBaseCon Asia, BEAM summits) - 1 enquiry about a non-ASF product - 1 enquiry about use of an ASF mark in a unrelated, non-software use (SPARK) Pinged several PMCs regarding outstanding issues. A draft policy was produced for use of our marks by downstream distributions: http://www.apache.org/foundation/marks/downstream.html * REGISTRATIONS - BROOKLYN have made the website changes and provided the information necessary for their registration to proceed - APACHE IGNITE has been provisionally refused in China due to a little known usage of "apache". We are working with counsel to appeal this. - We have received the paperwork to transfer the OPENWHISK marks. This needs to be completed and sent to counsel. * INFRINGEMENTS ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] Fundraising continues securing sponsorship renewals and are working with Virtual closely on invoicing and following through with sponsor payment. We were also able to renew AND upgrade a Sponsor whose account was in arrears for 6 months. As with our prior report, our Sponsor Ambassadors are "current" on communications and check-ins. We continue working to consolidate terms of combined (ASF + Targeted) Platinum sponsorship; steady progress has been made over the past quarter. As with the prior report, onboarding of a Targeted Platinum Sponsor remains on hold pending legal clearance. A potentially worrisome situation continues to present itself where we have problems with email deliverability when reaching a sponsor in China. We have had to resort to using our private emails to send messages (copying @apache.org lists) until the issue is resolved. Infra is aware of the situation. We have closed 22 event sponsor opportunities (with 12 organizations) and 2 media partnerships across Apache Roadshow/Chicago (1), ApacheCon/Las Vegas (19), and ApacheCon/Berlin (2). Sponsor agreements have successfully been signed using our new Docusign account; we are waiting for final confirmation from 5 additional companies to enter contracts. To that end, the digital sponsorship agreement process investment has helped simplify the acts of creating/sending/signing/gathering completed event agreements. Through this process change, we've witnessed a decrease in volunteer time spent doing such clerical work. Although we've had a slow start, we are working closely with Virtual’s business development/growth team on targeting, qualifying, and pitching candidate sponsors for both events and the foundation. We're pleased to report that we received $4,927+ from individual donors via Hopsie (PLUS additional payments received from PayPal and Amazon independently) this past month. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity - May 2019 I. Budget: we have kicked off the new fiscal year with no vendor issues (all payments are on schedule), and are standing by to answer any questions related to the proposed FY2020 budget and projections through FY2024. II. Cross-committee Liaison: Sally Khudairi continues to support ASF Fundraising with engaging existing sponsors, securing sponsorship renewals, and signing on new sponsors; the team at Virtual have been very responsive in ensuring timely invoicing and follow through. Assistance to ASF Conferences is ongoing, through planning, sponsorships, marketing and creative, PR and promotion, and a variety of supporting tactics for Apache Roadshow/Chicago, ApacheCon/Las Vegas, and ApacheCon/Berlin. Sally closed 20 of 22 event sponsor opportunities, and has secured a second media partnership to help promote all three events. We are editing two "Success at Apache" posts, as well as a new "Project Perspectives" post (highlighting how The Apache Way helps Apache projects and their communities). Sally will attend the ASF Board face-to-face meeting in May. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 29 April - The Apache® Software Foundation Expands Infrastructure with GitHub Integration - 24 April - The Apache Software Foundation Announces Apache® NetBeans™ as a Top-Level Project - 24 April - The Apache Software Foundation Announces Apache® SkyWalking™ as a Top-Level Project - 23 April - The Apache Software Foundation Announces Apache® PLC4X™ as a Top-Level Project IV. Informal Announcements: 11 items were published on the ASF "Foundation" Blog, and 1 item was published on the ApacheCon Blog. 5 Apache News Round-ups were issued, with a total of 251 weekly summaries published to date. We tweeted 90 items to 53.3K followers on Twitter. We posted 26 items on LinkedIn, which garnered more than 129.5K organic impressions. V. Future Announcements: 1 announcement is in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 7 media queries. The ASF received 1,854 press clips vs. last month's clip count of 1,891. Media coverage of Apache projects yielded 3,130 press hits vs. last month's 3,510. ApacheCon received 8 press hits. VII. Analyst Relations: we received 2 analyst queries. Apache was mentioned in 3 reports by Gartner; 2 report by Forrester; 3 reports by 451 Research; and 6 reports by IDC. VIII. Graphics: whilst no new programs are planned, Sally continues to create all promotional graphics for use in social media to promote the ASF and ApacheCon. IX. Events liaison: we have been providing considerable support to all Apache events, most actively the Apache Roadshow/Chicago, from marketing/promotion to sponsorship sales to badges/lanyard production. Work continues with Virtual and newthinking/Plain Schwarz on various advisory and tactical support across ApacheCon/Las Vegas and Berlin. We posted 8 items on the ASF Events and Apache Roadshow/Chicago pages on LinkedIn, tweeted 73 items on the ApacheCon Twitter account, and created all promotional graphics, animations, and digital ad campagins. Sally continues to work closely with ASF VP Conferences Rich Bowen, and will be meeting during the face-to-face Board Meeting to discuss plans and goals through FY2020. She is also planning the redesign of the apachecon.com site. X. Newswire accounts: we have 7 pre-paid press releases with GlobeNewswire through December 2020. # # # ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected. No issues that currently need escalation to the President or Board. Finances ======== Infrastructure closed out well within budget for FY19 Proposed budget has been submitted to the office of President for review at the upcoming Board meeting. CDN Evaluation ============== As our communities grow, particularly beyond North America and Western Europe, we're seeing more calls to have greater geographic diversity in a number of our services, simply to reduce wait time. Following our team meeting in New Orleans, we've been working on evaluating several different CDN options. Two projects, both with significant Asian participation have been assisting us in this evaluation, with their project websites being moved to a CDN, and thus far the feedback has been positive. Much more testing and evaluation will happen before we arrive at a decision on whether to proceed or in what direction. Long Range Priorities ===================== - Test and migrate to the new email setup ("hermes-vm2"). - Turn off mail-archives.a.o and mail-private.a.o, in favor of lists.a.o, leaving behind a redirect system for permalinks. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] ApacheCon North America The CFP has closed. However, due to the inevitable outpouring of "You closed it too soon" emails, I have silently extended the CFP by 48 hours, since I simply do not have time to handle the influx of people sending me their proposals via email. As of this writing, we have 313 proposals, plus 6 spam submissions which I have already rejected. Additionally, several of the project/community/topic tracks are actively soliciting and curating content for their tracks. We expect to announce the schedule by June 3rd, if all the stars align and the review process goes smoothly. ApacheCon Europe ApacheCon EU has had a quiet month. The CfP is going well, we currently have 45 submissions even though we're well ahead of the deadline. If that is a good indicator we will have plenty of ticket sales. Ticket sales are within normal parameters. We've begun working out details of the Friday conference extension in Berlin. We have one workshop already offered for the extension. Chicago Roadshow As of this writing, the roashow is currently underway. By the time of the meeting it will be complete. We expect to have more to report on the day of the meeting. LATE ADDITION: Attendance was around 100. Talks were great. Look for a more thorough report next month. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Events --------- This monrh sees us opening up of applications for ApacheCon NA. Next month applications will also open for ApacheCon EU for NA , we should be open within 24 hours of writing. Also for NA we have an extra $5K targeted pot of money to get a couple or 3 folks from a specific background, which requires us to ask a couple of extra questions on our application form to gather the required info. The questions are personal but will be 'optional' to answer. Budget ---------- A budget request for FY20 has been submitted. Committee --------------- There have been no additions to the Committee Mailing List ---------------- The mailing list has been in its quiet off season period but is starting to discuss the upcoming events. We have 19 subscribers. ----------------------------------------- Attachment 7: Report from the VP of Finance [Tom Pappas] VP of Finance April 2019 report Assisted Conferences with Insurance resolutions for Chi Road Show Assisted Fundraising with work on event sponsorships Assisting Treasurer with research and review of possible new Expense reporting platform ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] Aaron Coburn (acoburn@) has moved his individual account to affiliation ASF and joined as ASF: SPARQL 1.2 Community Group Solid Community Group LDP Next Community Group RDF JavaScript Libraries Community Group No new CG agreements for ASF were necessary. ----------------------------------------- Attachment 9: 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 good care of resolving most of these in time. (we're down 4, from 24 to 20, open issues this month). Thanks to Hen we're closing the loop on rationalizing our mailing lists infrastructure and are about to create our P&C list. We're at the final stretch with reviewing JetBrains sponsorship agreement and should have a final signoff from DLA Piper by the end of this week. Jakarta VP discussion is going on and when the VP Jakarta role is created whoever ends up in that role will be signing the agreement with Eclipse Foundation. We started to evaluate additional options for counsel to augment the work of DLA Piper. We expect to have an update on this in a month or two. Mishi Choudhary from SFLC is looking into refreshing the relationship with us. We had Facebook and Uber reach out to us for help with detailed understanding of our licensing practices. The meetings are being set up and we will report back on the result. ----------------------------------------- Attachment 10: 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. There are continuing issues with Mitre taking several weeks to update the CVE database for some issues. The Zeppelin project continued to not deal with outstanding security issues despite numerous contact attempts and even a board escalation. The issues had already been fixed in their code base for some time, but the process to notify users via a security advisory and publish the CVE names had not been completed. After a final warning, the Security Team Project therefore took the unfortunate step of publishing the details on their behalf: https://www.openwall.com/lists/oss-security/2019/04/23/1 Stats for April 2019: 8 [license confusion] 15 [support request/question not security notification] Security reports: 29 (last months: 39, 35, 38) 6 [httpd] 4 [lucene] 3 [site] 2 [pdfbox], [shiro], [tomcat] 1 [atlas], [commons], [fineract], [hadoop], [hive], [jspwiki], [kafka], [ofbiz], [struts], [trafficserver] In total, as of 1st May 2019, we're tracking 65 (last month: 84) open issues across 35 projects, median age 82 (last month: 66) days. 44 of those issues have CVE names assigned. 8 (last month: 12) of these issues, across 5 projects, are older than 365 days. ----------------------------------------- Attachment 11: Report from the VP of Data Privacy [John Kinsella] Working on setting up structure for data-privacy. Modified personnel-duties/vp-data-privacy.txt, will update further once mailing lists are set up. Stalled on setting up mailing lists as I was going to start conversation on legal ML first, but just going to create lists and run with it. Working on syncing up with others who have worked on data-privacy matters over the last year and talked to counsel. Once that's accomplished, will stat work to review data privacy policy and engage with projects looking for assistance. Stats for April, 2019: * 2 open Jira tickets * 0 closed issues ----------------------------------------- Attachment A: Report from the Apache Ambari Project [Jayush Luniya] ## Description: - Apache Ambari simplifies provisioning, managing, and monitoring of Apache Hadoop clusters. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The community is working on an Apache Ambari 2.7.4 maintenance release. ## Health report: - The development community and engagement remains strong, however few committers and PMC members have moved to other projects. We have 105 committers and 48 PMC members on the project; 3 new committers were added in the past 3 months. ## PMC changes: - Currently 48 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ishan Bhatt on Thu Oct 25 2018 ## Committer base changes: - Currently 105 committers. - New commmitters: - Amarnathreddy Pappu was added as a committer on Sat Apr 13 2019 - Akhil Naik was added as a committer on Mon Mar 25 2019 - Jay SenSharma was added as a committer on Mon Mar 25 2019 ## Releases: - Last release was 2.7.3 on Fri Nov 16 2018 ## Mailing list activity: - Apache Ambari has moved from ReviewBoard to GitBox for code reviews and hence there is no activity on reviews@ambari.apache.org - dev@ambari.apache.org: - 304 subscribers (up 3 in the last 3 months): - 1 emails sent to list (21 in previous quarter) - issues@ambari.apache.org: - 48 subscribers (down -1 in the last 3 months): - 941 emails sent to list (1751 in previous quarter) - reviews@ambari.apache.org: - 61 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - user@ambari.apache.org: - 473 subscribers (down -4 in the last 3 months): - 5 emails sent to list (17 in previous quarter) ## JIRA activity: - 133 JIRA tickets created in the last 3 months - 106 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment B: Report from the Apache Ant Project [Jan Materne] ## Description: Apache Ant is a Java based build tool along with associated tools. It consists of 3 main projects: - Ant - core and libraries (AntLibs) - Ivy - Ant based dependency manager - IvyDE - Eclipse plugin to integrate Ivy into Eclipse Additionally Ant provides several extensions to Ant (antlibs). ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Stefan accepted an invitation by Canonical to the Snapshat Summit Montreal in June 2019 (https://snapcraft.io/blog/snapcraft-summit-montreal) for integrating Ant into Ubuntu Snap. - Ant 1.9.14 was the first release another release manager had cut. Thanks to Jaikiran. He also prepared 1.10.6 which is still in the voting stage. ## Health report: For Ant we feel healthy enough to apply patches, and get a release done. But basically we are in "maintenance mode". There isn't much development. ## PMC changes: - Currently 23 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Magesh Umasankar on Fri Jul 06 2018 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Jaikiran Pai at Wed Jun 14 2017 ## Releases: - Ant 1.9.14 was released on Sun Mar 17 2019 - (Ant 1.10.6 in the voting stage) ----------------------------------------- Attachment C: Report from the Apache BookKeeper Project [Sijie Guo] ## Description: BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for append-only workloads. It has been used as a fundamental service to build high available and replicated services in companies like Twitter, Yahoo and Salesforce. It is also the log segment store for Apache DistributedLog and message store for Apache Pulsar. Apache DistributedLog is a high-level API and service layer for Apache BookKeeper, providing easier access to the BookKeeper primitives. It is a subproject of Apache BookKeeper. ## Issues: There are no issues requiring board attention at this time. ## Activity: - 4.9.0 was released on January 31 2019 - 4.8.2 was released on March 19 2019 - 4.9.1 was released on April 7 2019 - 4.9.2 is under release voting - The growth of Apache Pulsar community also help grow the adoption of BookKeeper. This helps building the ecosystem around BookKeeper. ## Health report: - Development continues at a steady pace. We are merging multiple PRs per week on average. - Mailing list and slack discussions are brisk, in particularly around the active projects. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Enrico Olivelli on Fri Feb 23 2018 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Andrey Yegorov at Sat Feb 10 2018 ## Releases: - 4.9.0 was released on January 31 2019 - 4.8.2 was released on March 19 2019 - 4.9.1 was released on April 7 2019 ## Mailing list activity: - dev@bookkeeper.apache.org: - 104 subscribers (down -1 in the last 3 months): - 67 emails sent to list (112 in previous quarter) - distributedlog-commits@bookkeeper.apache.org: - 12 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - distributedlog-dev@bookkeeper.apache.org: - 41 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - distributedlog-issues@bookkeeper.apache.org: - 9 subscribers (up 0 in the last 3 months): - 6 emails sent to list (2 in previous quarter) - distributedlog-user@bookkeeper.apache.org: - 26 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@bookkeeper.apache.org: - 8 subscribers (up 0 in the last 3 months): - 1825 emails sent to list (1867 in previous quarter) - user@bookkeeper.apache.org: - 117 subscribers (up 0 in the last 3 months): - 8 emails sent to list (11 in previous quarter) ----------------------------------------- Attachment D: Report from the Apache Brooklyn Project [Geoff Macartney] ## Description: - Apache Brooklyn is a software framework for modelling, monitoring and managing cloud applications through autonomic blueprints. ## Issues: - there are no issues requiring board attention at this time ## Activity: - It has been a quiet quarter, with continued development activity at a low level, and some discussions on the mailing list. - We updated the Apache Brooklyn website at the request of Mark Thomas, to correctly comply with the foundation naming guidelines, in order to progress our trademark application. ## Health report: - The project continues with a regular turnover of pull requests and commits. - We continue to monitor our community for potential new committers and PMC members with the aim of regularly adding individuals (see "PMC Changes"). - It has been nearly six months since our M1 release. While preparing for this report I have mailed the dev list to canvass opinion about releasing Brooklyn 1.0.0, and responses have been positive. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Duncan Grant on Thu Aug 30 2018 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Duncan Grant at Wed Jun 13 2018 ## Releases: - Last release was 1.0.0-M1 on Mon Sep 17 2018 ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Buildr Project [Antoine Toulme] ## Description: Apache Buildr is a build system for Java-based applications, including support for Scala, Groovy and a growing number of JVM languages and tools. We wanted something that’s simple and intuitive to use, so we only need to tell it what to do, and it takes care of the rest. But also something we can easily extend for those one-off tasks, with a language that’s a joy to use. And of course, we wanted it to be fast, reliable and have outstanding dependency management. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have released 1.5.7 in February. The project is otherwise very quiet. ## Health report: - We still have a small PMC presence of 3 active members still able to vote releases. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Peter Donald on Tue Oct 15 2013 ## Committer base changes: - Currently 10 committers. - Olle Jonsson was added as a committer on Wed Dec 12 2018 ## Releases: - Last release was 1.5.7 on February 16th 2019 ----------------------------------------- Attachment F: Report from the Apache Cassandra Project [Nate McCall] ## Description: The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance. Linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure make it the perfect platform for mission-critical data. Cassandra's support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages. ## Issues: ## Activity: We were accepted as Google Season of Docs participants. We have already received four inbounds from potential documentation writers even though the program has not officially begun. Additionally, we have expanded our ApacheCon request to a two day track. The first day will be our developer centric conference known as Next Generation Cassandra Conference (NGCC). The second day will be a general-purpose sponsorship. We have already attracted a pair of sponsors and received some high-quality submissions from some of our largest users for both days of the conference. ## Health report: We are continue to track and prioritize issues as we approach 4.0: https://cwiki.apache.org/confluence/display/CASSANDRA/4.0%3A+Open+Issues+by+Component ## PMC changes: Alex Petrov was added to the PMC on Tue Apr 09 2019. There are currently 32 PMC members. ## Committer base changes: Three new committers were added this quarter, bringing our total to 54: - Dinesh Joshi was added as a committer on Tue Mar 05 2019 - Joey Lynch was added as a committer on Thu Feb 28 2019 - Vinay Chella was added as a committer on Sat Feb 23 2019 ## Releases: The project made the following releases this quarter: - 2.1.21 was released on Mon Feb 11 2019 - 2.2.14 was released on Mon Feb 11 2019 - 3.0.18 was released on Mon Feb 11 2019 - 3.11.4 was released on Mon Feb 11 2019 ## Mailing list activity: We had a marginal fall off of mail list activity this quarter, but the overall traffic to both dev and user lists is still healthy. dev@cassandra.apache.org: - 1554 subscribers (down -43 in the last 3 months): - 279 emails sent to list (273 in previous quarter) user@cassandra.apache.org: - 2945 subscribers (down -45 in the last 3 months): - 660 emails sent to list (436 in previous quarter) ## JIRA activity: - 112 JIRA tickets created in the last 3 months - 65 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment G: Report from the Apache Clerezza Project [Hasan Hasan] DESCRIPTION Apache Clerezza models the RDF abstract syntax in Java and provides supports for serializing, parsing, managing and querying triple collections (graphs). Apache Clerezza modules aim at supporting the development of Semantic Web applications and services. ISSUES FOR THE BOARD There are no issues requiring board attention at this time. RELEASE Latest release was created on May 13, 2016. A new release is targeted in Q3 2019. ACTIVITY Some improvements in the jaxrs.rdf.providers module. Updated all artifact versions in the reunited branch to be merged to master. A pull request has been created and being reviewed which refactors Apache Clerezza and integrates the clerezza-rdf-core and as a preparation for the next release. COMMUNITY Latest change was addition of a new committer and PMC member on 27.12.2018 INFRASTRUCTURE Latest update of the Apache Clerezza Website was in February 2018. ----------------------------------------- Attachment H: Report from the Apache Cocoon Project [Cédric Damioli] ## Description: Web development framework: separation of concerns, component-based. ## Issues: There are no issues requiring board attention at this time ## Activity: Last quarter report and board's heads up from the previous one gave us the opportunity to work on a few issues. All pending activity seems now to have been resolved. Following recent discussions on private list, we now have to decide what to do with our several branches. The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report, but more than previous quarters. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06 ----------------------------------------- Attachment I: Report from the Apache Community Development Project [Sharan Foga] ## Description: - The Community Development PMC is responsible for helping people become involved with Apache Projects ## Issues: - No issues require board attention at the moment ## Activity: - GSoC: The ASF was selected to be a mentor organisation for GSoC. As usual the co-ordintation and mentor registration is being managed by ComDev. We have received a lot of ideas and are currently in the final stages of finalising the list of projects and students. - Season of Docs: After some discussion on the mailing list we applied on behalf of some of our projects to be a mentoring organisation for the new Season of Docs program but unfortunately were not selected. Two other ASF projects Apache Cassandra and Apache Airflow were successful in being accepted and allocated a technical writer. - Events:- We have requested feedback on the events that the community would like us to participate in for 2019. The next step is to finalise it, and then plan our participation. - Diversity:- Diversity and inclusion has been a key topic this quarter with several discussions being raised on several aspects. One suggestion is to separate out these efforts into a focussed group that can co-ordinate activities. - Community Tracks at Apachecon :-We are hoping to fill three days of community related content at ApacheCon NA, Las Vegas and two days of community related content at ApacheCon EU, Berlin. Several reminders have been sent to the community highlighting the range of areas that we would be keen to see covered. We have also requested volunteers from the community to help review the CFP proposals that have been submitted. ## Health report: - We have a very active mailing this yet may be missing out of ways to promote and communicate all the things that are happening. This is the third quarter where our monthly blog has slipped. ## PMC changes: - Currently 30 PMC members. - Gris Cuevas was added to the PMC on Mon Apr 22 2019 ## Committer base changes: - Currently 32 committers. - New commmitters: - Paul Berschick was added as a committer on Thu Apr 04 2019 - Gris Cuevas was added as a committer on Mon Apr 22 2019 ## Mailing list activity: - Mailing list traffic has increased this quarter with a lot of active discussions around potential diversity initiatives and also ways to improve understanding of meritocracy and the Apache Way. - dev@community.apache.org: - 890 subscribers (up 4 in the last 3 months): - 799 emails sent to list (404 in previous quarter) ## JIRA activity: - 9 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment J: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: - Seamless multi-master sync, that scales from Big Data to Mobile, with an Intuitive HTTP/JSON API and designed for Reliability. ## Issues: - there are no issues requiring board attention at this time. ## Activity: - Technical discussion for the move to FoundationDB outlined in the last report is ongoing and fruitful. - At the same time new features are added and bugs are fixed for existing release lines. - We are getting close to fully supporting arm64, specifically with pre-built binaries and CI coverage. ## Health report: - Discussion levels are normal and focussed on the tasks at hand. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Nick Vatamaniuc on Tue Nov 07 2017 ## Committer base changes: - Currently 64 committers. - No new committers added in the last 3 months - Last committer addition was Jay Doane at Sat Jan 05 2019 ## Releases: - 2.3.1 was released on Mon Mar 11 2019 ----------------------------------------- Attachment K: Report from the Apache Creadur Project [Brian E Fox] ----------------------------------------- Attachment L: Report from the Apache Crunch Project [Josh Wills] ## Description: - Apache Crunch is a JVM library for writing, testing, and running MapReduce and Apache Spark pipelines on Apache Hadoop. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Most of the work this quarter focused on integrations with Hadoop's FileSystem extensions to better support reading/writing pipeline data from/to various object stores (mainly S3.) ## Health report: - The project's current work is focused on the needs of community members who are moving MapReduce-based pipelines that ran in legacy clusters to various cloud-based Hadoop clusters, and makes sense given Hadoop's general focus on this area as well. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Micah Whitacre on Wed Apr 02 2014 ## Committer base changes: - Currently 15 committers. - No new committers added in the last 3 months - Last committer addition was Stephen Durfey at Fri Feb 09 2018 ## Releases: - Last release was 0.15.0 on Sat Feb 25 2017 ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment M: Report from the Apache DeltaSpike Project [Mark Struberg] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans outside of a container. - JSF integration, including backporting of JSF 2.2 features for Java EE 6. - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. - Quartz integration Testing support is also provided, to allow you to do low level unit testing of your CDI enabled projects. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity was still rather low. DeltaSpike is mature and an important building block for many enterprise projects. But nothing to worry ## Health report: Since jakartaEE must not evolve the javax.* namespace we will probably ship a jakarta.* version of DeltaSpike in parallel rather soonish. ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Harald Wellmann on Thu May 19 2016 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Alexander Falb at Wed Aug 01 2018 ## Releases: - Last release was 1.9.0 on Mon Sep 10 2018 ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache DRAT Project [Tom Barber] ## Description: - Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around Apache RAT™ and other code auditing tools to allow it to complete on large code repositories of multiple file types. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - More ongoing work was done in this period to ready DRAT for a 1.0 release this includes bug fixes in the UI and rendering logic to make it more usable. ## Health report: - Slow pace of development, but functioning PMC and look to get 1.0 released. ## PMC changes: - Currently 14 PMC members. - Ahmed Ifhaam was added to the PMC on Thu Aug 30 2018 ## Committer base changes: - Currently 14 committers. - Ahmed Ifhaam was added as a committer on Tue Aug 28 2018 ## Releases: - Work is ongoing to ready a 1.0 release ## Mailing list activity: - Mailing list activity was pretty flat, but expected - dev@drat.apache.org: - 16 subscribers (down -1 in the last 3 months): - 50 emails sent to list (4 in previous quarter) - issues@drat.apache.org: - 10 subscribers (up 0 in the last 3 months) ----------------------------------------- Attachment O: Report from the Apache Drill Project [Arina Ielchiieva] ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last board report, Drill has released version 1.16.0, including the following enhancements: - CREATE OR REPLACE SCHEMA command to define a schema for text files - REFRESH TABLE METADATA command can generate metadata cache files for specific columns - ANALYZE TABLE statement to computes statistics on Parquet data - SYSLOG (RFC-5424) Format Plugin - NEAREST DATE function to facilitate time series analysis - Format plugin for LTSV files - Ability to query Hive views - Upgrade to SQLLine 1.7 - Apache Calcite upgrade to 1.18.0 - Several Drill Web UI improvements, including: - Storage plugin management improvements - Query progress indicators and warnings - Ability to limit the result size for better UI response - Ability to sort the list of profiles in the Drill Web UI - Display query state in query result page - Button to reset the options filter - Drill User Meetup will be held on May 22, 2019. Two talks are planned: - Alibaba's Usage of Apache Drill for querying a Time Series Database - What’s new with Apache Drill 1.16 & a demo of Schema Provisioning ## Health report: - The project is healthy. Development activity as reflected in the pull requests and JIRAs is good. - Activity on the dev and user mailing lists are stable. - One PMC member was added in the last period. ## PMC changes: - Currently 24 PMC members. - Sorabh Hamirwasia was added to the PMC on Fri Apr 05 2019 ## Committer base changes: - Currently 51 committers. - No new committers added in the last 3 months - Last committer addition was Salim Achouche at Mon Dec 17 2018 ## Releases: - 1.16.0 was released on Thu May 02 2019 ## Mailing list activity: - dev@drill.apache.org: - 406 subscribers (down -10 in the last 3 months): - 2299 emails sent to list (1903 in previous quarter) - issues@drill.apache.org: - 17 subscribers (down -1 in the last 3 months): - 2373 emails sent to list (2233 in previous quarter) - user@drill.apache.org: - 582 subscribers (down -15 in the last 3 months): - 235 emails sent to list (227 in previous quarter) ## JIRA activity: - 214 JIRA tickets created in the last 3 months - 212 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment P: Report from the Apache Empire-db Project [Rainer Döbele] ## Description: - Apache Empire-db is a relational database access engine that takes an SQL-centric approach in contrast to object-relational-mapping like with JPA It encapsulates the functionality of a RDBMS in a powerful, vendor independent, intuitive and maintenance friendly API providing a maximum of compile-time-safety. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Frankly there has been no activity during the last quarter. Due to its maturity, no bugs were reported. However the PMC is aware, that there is work to do to improve the project visibitly and popularity. ## Health report: - The project remains healthy. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jan Glaubitz on Sun Jul 10 2016 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Jan Glaubitz at Mon Oct 05 2015 ## Releases: - Last release was empire-db-2.4.7 on Wed Oct 31 2018 ## Mailing list activity: - dev@empire-db.apache.org: - 33 subscribers (down -1 in the last 3 months): - 1 emails sent to list (16 in previous quarter) - user@empire-db.apache.org: - 51 subscribers (down -3 in the last 3 months): - 1 emails sent to list (0 in previous quarter) ----------------------------------------- Attachment Q: Report from the Apache Flume Project [Ferenc Szabo] ## Description: Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. ## Issues: There are no issues requiring board attention at this time. ## Activity: - a few minor contributions were merged this month such as bug fixes and doc improvements - discussion started about modernizing the description of what Flume is, to place emphasis on its capabilities outside of the Hadoop ecosystem. - Ralph Goers is working on a centralized configuration provider - Ferenc Szabo started working on Java 11 support - discussion started about the next release content and 3rd party library upgrade ## Health report: - The last quarter had low commit activity, likely due to people busy with other things ## Regarding board comments from the last report: idf: It's been a while since the last committer was added. Are there any candidates that could benefit from a bit of mentorship? - there are a few candidates we are already working with - there is a plan to contact new people with more contributions to ask if they are interested in becoming committers ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ferenc Szabo on Mon Jan 28 2019 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Attila Simon at Sat Nov 04 2017 ## Releases: - Last release was 1.9.0 on Wed Jan 02 2019 ## JIRA activity: - 16 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache Forrest Project [David Crossley] Apache Forrest mission is software for generation of aggregated multi-channel documentation maintaining a separation of content and presentation. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2013-04-08 Most recent addition: 2009-06-09 New committers: None. Most recent addition: 2009-06-09 None on the horizon. General status: The most recent release is 0.9 on 2011-02-07. At this report, three other PMC members responded to my draft report. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision. Project status: Activity: Idle 4 people indicated presence: potential for sufficient oversight. None of the remaining project members have yet found time to raise the topic on the dev list about moving to the Apache Attic. Security issues published: None. Progress of the project: None. ----------------------------------------- Attachment S: Report from the Apache FreeMarker Project [Dániel Dékány] ## Description: Apache FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. Apache FreeMarker is implemented in Java as a class library for programmers. FreeMarker 2 (the current stable line) produces releases since 2002. The FreeMarker project has joined the ASF in 2015, and graduated from the Incubator in early 2018. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity was very low in the last 3 months. As a consequence, the release of the micro version (2.3.29), initially planned for February, has been delayed. ## Health report: Activity is low but steady, as it's usual for this project. User questions (mostly on StackOverflow) and new Jira issues are being answered promptly. The short term goal is to release the next micro version (2.3.29) as soon as possible. The long term goal is continuing the ongoing development on the 3.0 branch, so that the project can innovate and the code base can become much cleaner and more attractive for new committers. ## PMC changes: - Currently 7 PMC members. - No changes since the graduation on 2018-03-21 ## Committer base changes: - Currently 7 committers. - No changes since the graduation on 2018-03-21 ## Releases: - 2.3.28 was released on Wed Apr 04 2018 ----------------------------------------- Attachment T: Report from the Apache Geode Project [Karen Miller] ## Description: Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing. ## Issues: There are no issues requiring board attention at this time. ## Activity: - We released v1.9.0, containing 82 improvements and new features, resolving 163 bugs and a total of 297 JIRA tickets. - The v1.9.0 release included some notable performance improvements, as well as improvements in the areas of logging, security, and recovery following unexpected network disconnections. - Work is continuing to improve management REST interface, observability, performance, native client, and stability under heavy load. - Several PMC members are reviewing submissions for the Geode session track at the SpringOne Platform 2019 conference. ## Health report: - Mailing lists remain active and productive. - JIRA tickets show that issues continue to be identified and resolved. - We’re continuing to work on attracting new contributors and making it easier to participate in the community. ## PMC changes: - Currently 51 PMC members. - New PMC members: - Helena Bales was added to the PMC on Tue Feb 12 2019 - Ryan McMahon was added to the PMC on Tue Feb 12 2019 - Owen Nichols was added to the PMC on Mon Feb 18 2019 - Juan Ramos was added to the PMC on Wed Feb 20 2019 - Robert Houghton was added to the PMC on Wed Feb 20 2019 ## Committer base changes: - Currently 100 committers. - New commmitters: - Owen Nichols was added as a committer on Mon Feb 18 2019 - Masaki Yamakawa was added as a committer on Mon Mar 25 2019 ## Releases: - 1.9.0 was released on Tue Apr 23 2019 ## Mailing list activity: Mailing lists have remained active and have maintained consistent usage levels. - dev@geode.apache.org: - 192 subscribers (down -1 in the last 3 months): - 435 emails sent to list (497 in previous quarter) - issues@geode.apache.org: - 51 subscribers (down -4 in the last 3 months): - 3097 emails sent to list (3417 in previous quarter) - notifications@geode.apache.org: - 7 subscribers (no change in the last 3 months): - 1748 emails sent to list (2714 in previous quarter) - user@geode.apache.org: - 242 subscribers (down -7 in the last 3 months): - 110 emails sent to list (81 in previous quarter) ## JIRA activity: - 385 JIRA tickets created in the last 3 months - 362 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Giraph Project [Dionysios Logothetis] ## Description: - Giraph is a Bulk Synchronous Parallel framework for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Only two minor fixes since last report ## Health report: - While I've been working with a contributor that is developing a new algorithm, due to increased workload, we haven't find the time to review the code. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dionysios Logothetis on Sun Apr 22 2018 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Dionysios Logothetis at Mon Apr 23 2018 ## Releases: - Last release was 1.2.0 on Thu Oct 20 2016 ## Mailing list activity: - There's some small but constant activity on small issues - dev@giraph.apache.org: - 268 subscribers (down -1 in the last 3 months): - 30 emails sent to list (69 in previous quarter) - user@giraph.apache.org: - 442 subscribers (up 1 in the last 3 months): - 5 emails sent to list (5 in previous quarter) ----------------------------------------- Attachment V: 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 and Apache Spark support ## Issues: - There are no issues requiring board attention at this time ## Activity: - During the last quarter Gora community has worked mainly on our 0.9 next release. First release candidate of 0.9 version is now available and community is now voting on it for past few days. This release consists of 4 major integrations to other Apache projects such as Apache Flink, Apache Pig, Apache Ignite and Apache Lucene. This is a long awaited release for us and 0.9 release will be available very soon - We have 4 Google summer of code projects accepted for this year. ( 2019 ) 7 PMC members from Apache Gora have volunteered for mentoring efforts. We are very positive on all four projects and we look forward to expand our committer base after GSoC the period - There were several discussions on the past regarding the roadmap for Apache Gora. We will reignite these discussions again once the entire 0.9 release process and activities are completed ## Health report: - Apache Gora project is in very good health. There were lot of development, release process and community based activities - Majority of Apache Gora PMC is very active and helped to drive release efforts as well as GSoC mentoring efforts ## PMC changes: - Currently 27 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Carlos Muñoz on Wed Dec 05 2018 ## Committer base changes: - Currently 27 committers. - No new committers added in the last 3 months - Last committer addition was Carlos Muñoz at Tue Nov 13 2018 ## Releases: - Last release was 0.8 on Tue Sep 19 2017 ## Mailing list activity: - There is huge rise in dev@gora.apache.org list email traffic, mainly due to the release work - dev@gora.apache.org: - 74 subscribers (up 3 in the last 3 months): - 427 emails sent to list (77 in previous quarter) - user@gora.apache.org: - 74 subscribers (up 1 in the last 3 months): - 3 emails sent to list (1 in previous quarter) ## JIRA activity: - 20 JIRA tickets created in the last 3 months - 26 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment W: Report from the Apache Groovy Project [Paul King] ## Description: - Apache Groovy is a multi-faceted programming language for the Java platform. Groovy is a powerful, optionally typed and dynamic language, with static-typing and static compilation capabilities, aimed at multiplying developers’ productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain-Specific Language authoring, first class functional programming support and runtime and compile-time meta-programming. ## Issues: - Outstanding issue: Website: some more progress has been made in the last quarter but this task is not quite finished - work will continue. - Update on open collective: the open collective crowd funding site[1] mentioned in the previous report has now been set up. So far all is operating well. We received positive feedback from within The ASF on how it was set up. The open collective has also received good support within the broader Groovy community. We will continue to monitor the collective to ensure branding guidelines etc. are maintained. [1] https://opencollective.com/friends-of-groovy ## Activity: - This quarter, 1196 commits were contributed from 59 contributors including 47 non-committer contributors (10 new). ## Health report: - Committee Health score: Healthy - Apache Groovy was downloaded 40 million times during the last quarter (across Maven Central and JFrog Bintray). That's about 1/4 of a billion downloads that we have recorded since the project's inception (includes pre-Apache numbers but excludes numbers from Apache servers/mirrors and other repositories). ## PMC changes: - Currently 10 PMC members - Cédric Champeau resigned from the PMC during the quarter - Daniel Sun joined the PMC in the last few days ## Committer base changes: - Currently 17 committers - No new committers added in the last 3 months - Last committer addition was Remko Popma at Sat Jul 07 2018 ## Releases: - Last release was 2.5.6 on Mon Feb 04 2019 ## Mailing list activity: - Mailing list activity has remained steady - users@groovy.apache.org: - 421 subscribers (up 3 in the last 3 months): - 92 emails sent to list (98 in previous quarter) - dev@groovy.apache.org: - 235 subscribers (up 0 in the last 3 months): - 187 emails sent to list (236 in previous quarter) ## JIRA activity: - 127 JIRA tickets created in the last 3 months - 91 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: Report from the Apache Hama Project [Chia-Hung Lin] ## Description: - Apache Hama is a framework for Big Data analytics based on the Bulk Synchronous Parallel paradigm ## Issues: - There are no issues requiring board attention at this time ## Activity: - Wiki was moved from MoinMoin to Confluence - Some development related to the new features were committed ## Health report: - At this stage it looks ok as some tasks are underway, though the traffic is not very high ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Behroz Sikander on Mon Feb 01 2016 ## Committer base changes: - Currently 18 committers. - Last committer addition was YoungWoo Kim at Sun May 20 2018 ## Releases: - Last release was hama-0.7.1 on Sun Mar 13 2016 ----------------------------------------- Attachment Y: Report from the Apache HTTP Server Project [Daniel Gruno] ## Description: The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards. ## Issues: There are no issues requiring board attention at this time ## Activity: - The Apache HTTP Server 2.4.39 was released in March, including four important and three low severity CVEs. I would like to thank the security team for handling this in a diligent manner. A lot of work has also been done on various sub-modules of the project, including but not limited to; http2, ssl and proxying. - A thorough discussion on keep-alives in 304 responses was also started, and is still ongoing[1]. - Members of the project have expressed an interest in revisiting the older parts of our BugZilla backlog for the purpose of cleaning up issues that are either stale or have been fixed/mitigated, as well as improving the overall state of tickets, so as to attract new people and ideas. [1] https://s.apache.org/2uyB ## Health report: This quarter saw activity from 23 different committers, a very good number, 43% higher than last quarter, as well as a substantial increase in commits (258, up 45%) and changes. While no-one was elected in as new committers in this quarter, it is safe to say that we have a healthy and diverse community that produces changes, fixes and enhancements on a very stable basis. Retention-wise, we have had seven people (re)join the project this past quarter, which is a very good number - we need to go back to 2014 to see a higher quarterly uptick on that front. That no-one new joined the committer base obviously means these people were previously engaged in httpd, which is just as much a delight. We welcome them back with open arms. Bus/Pony/Elephant-wise, we remain at a Pony Factor[1] of 5, meaning around five people make up half of the new commits around here. For a project of our size, age and pace, this is a pretty good number, considering this tracks committers and not necessarily authors of commits. For reference, the Pony Factor of httpd has been 5 or 6 for the past 8 years, so nothing has really changed there. On a slightly more "extra-curricular" note, I did a little research in relation to some enhancements I developed for the Apache Kibble project, and plotted httpd's "punch cards" (commits across the hours of the week) for the past 18 years[2]. Touching on the diversity aspect of community health, we have seen a clear move from a US-centric project community to a more wide-spread committer base, now favoring the European and African continents (if we assume that we can roughly correlate a commit timestamp with a timezone through basic knowledge about when people are awake and asleep - this isn't always true of committers!). While not an exact science, as we do not store a whole lot of information about our committers, it is nice to see that the neutrality and governance of the ASF may have caused a natural shift towards a new group of core committers that help keep the httpd project alive and vibrant. Looking at the larger community, things have also been pretty steady, with a stable trend on the development mailing list, and a slight uptick in traffic on our users list (20% more topics discussed than in previous quarter). Numerical stats to follow in the mailing list paragraph. It should also be noted, that we have more than plenty of oversight in the PMC, with around 20 active PMC members involved in the project discussions over the past quarter. [1] https://ke4qqq.wordpress.com/2015/02/08/pony-factor-math/ [2] https://imgur.com/HolcMtQ ## PMC changes: - Currently 53 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Stefan Sperling on Wed Jan 23 2019 ## Committer base changes: - Currently 122 committers. - No new committers added in the last 3 months - Last committer addition was Sebastian Bazley at Fri Jul 13 2018 ## Releases: - 2.4.39 was released on Sat Mar 30 2019 ## Mailing list activity: As stated before, pretty much the same. Slightly fewer emails, but more topics on the lists. - users@httpd.apache.org: - 2461 subscribers (down -31 in the last 3 months): - 193 emails sent to list (272 in previous quarter) - dev@httpd.apache.org: - 820 subscribers (down -5 in the last 3 months): - 148 emails sent to list (222 in previous quarter) ## Bugzilla Statistics: There are currently 1075 open tickets, many of which - as stated in the previous activity paragraph - are either stale or no longer an issue. In our last cleanup session, we removed 700 tickets from the queue, and could likely halve our backlog if we did another cleanup session or hackathon, perhaps at an ApacheCon. - 59 Bugzilla tickets created in the last 3 months - 35 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment Z: Report from the Apache HttpComponents Project [Asankha Chamath Perera] ## Description: - The Apache HttpComponents project is responsible for creating and maintaining a toolset of low-level Java components focused on HTTP and associated protocols. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The team is still working toward completing HttpCore 5.0 and HttpClient 5.0 BETA development phase and reaching GA milestone. Formal release votes can be expected in Q3 2019. ## Health report: - Overall the project remains active. With 5.0 development phase almost complete we expect the main focus to shift from development to maintenance and user support. There are no immediate goals for 5.1 development phase. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Mon Aug 24 2015 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Ryan Schmitt at Tue Nov 13 2018 ## Releases: - HttpClient 4.5.8 GA was released on Sun Mar 31 2019 - HttpClient 5.0-beta4 was released on Mon Apr 08 2019 - HttpCore 5.0-beta7 was released on Mon Mar 04 2019 ## Mailing list activity: - The activity on mailing lists continues to decline. However more development related discussions now tend to take place on Github and user support questions tend to get asked on StackOverflow. Often people subscribe and post quesstions to the user list only if their questions fail to get enough attention on StackOverflow. - dev@hc.apache.org: - 173 subscribers (down -7 in the last 3 months): - 632 emails sent to list (640 in previous quarter) - httpclient-users@hc.apache.org: - 520 subscribers (down -5 in the last 3 months): - 30 emails sent to list (73 in previous quarter) ## JIRA activity: - 29 JIRA tickets created in the last 3 months - 37 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Ignite Project [Denis A. Magda] ## Description: - Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Ignite community has been preparing a maintenance release 2.7.5 that comes with much better JDK 9+ support and bug fixes. - Some community members have been designing a next-gen metrics and monitoring framework as well as driving Ignite 3.0 discussion. ## Health report: - The community embraces more and more contributors as well as committers that keeps the project healthy. ## PMC changes: - Currently 28 PMC members. - Roman Shtykh was added to the PMC on Sun Feb 24 2019 ## Committer base changes: - Currently 47 committers. - New commmitters: - Andrey Mashenkov was added as a committer on Fri Feb 08 2019 - Vyacheslav Daradur was added as a committer on Mon Apr 01 2019 - Ilya Lantukh was added as a committer on Wed Feb 13 2019 - Ivan Pavlukhin was added as a committer on Thu Apr 18 2019 - Alexey Zinoviev was added as a committer on Mon Feb 25 2019 ## Releases: - Last release was 2.7.0 on Wed Dec 05 2018 ## Mailing list activity: - dev@ignite.apache.org: - 430 subscribers (up 9 in the last 3 months): - 1485 emails sent to list (3153 in previous quarter) - ci@ignite.apache.org: - 5 subscribers (up 0 in the last 3 months) - issues@ignite.apache.org: - 33 subscribers (up 0 in the last 3 months): - 5991 emails sent to list (9452 in previous quarter) - notifications@ignite.apache.org: - 8 subscribers (up 0 in the last 3 months): - 2132 emails sent to list (1099 in previous quarter) - services@ignite.apache.org: - 7 subscribers (up 0 in the last 3 months) - user@ignite.apache.org: - 779 subscribers (up 12 in the last 3 months): - 1248 emails sent to list (1839 in previous quarter) ## JIRA activity: - 646 JIRA tickets created in the last 3 months - 706 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache Impala Project [Jim Apple] ## Description: Impala is a high-performance distributed SQL engine. ## Issues: There are no issues requiring board attention at this time. ## Activity and health report: The previous three months had 237 patches to the master branch, while this three-month period had 286. This is likely the recovery from the usual seasonal dip around the end of each calendar year. Prominent work in the last three months includes: - An admission controller debugging page - Thousands of lines of new planner tests - A number of improvements to the shell scripts used to build and to start the various daemons - A few patches that reduced the disk space needed for development by tens of gigabytes - Support for development on Ubuntu 18.04. - Support for Apache Ranger and decoupling Apache Sentry - Support for complex types in ORC files - Better hardware detection - Compatibility with Hive 3.x for data loading and the Metastore - Numerous improvements to metrics and counters - Continued work on supporting Docker in development environments and in production - Initial support for a timeless DATE type Health is a subjective metric, but the increased compatibility with other open source and Apache projects is a good sign, as is the nine new patch authors. ## PMC changes: - Currently 29 PMC members. - Quanlong Huang was added to the PMC on Sun Mar 10 2019 ## Committer base changes: - Currently 46 committers. - New committers: - Pooja Nilangekar was added as a committer on Tue Apr 09 2019 - Paul Rogers was added as a committer on Mon Feb 04 2019 ## Releases: - 3.2.0 was released on Wed Mar 27 2019 ## JIRA activity: - 326 JIRA tickets created in the last 3 months - 296 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AC: Report from the Apache Incubator Project [Justin Mclean] Incubator PMC report for May 2019 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 50 podlings incubating. During the month of April, podlings executed 10 distinct releases. We added two new IPMC members and no IPMC members retired. We have no new podlings this month. Three projects graduated last month namely PLC4X, SkyWalking and Netbeans and several other podlings are heading towards graduation in the next few months. One of the podlings that failed to report last month, Milagro failed to report again this month and the IPMC will discuss what to do. This is the not first time this project has failed to report and it may not have a working PPMC. Two podlings Milagro and Toree have not submitted reports and will be asked to report next month. There were two IP clearances. The new Podling clutch page is working well and documentation has been created clearly explains what information is collected from where. The incubator is providing a new service to podlings to provide feedback on releases. So far no podlings have taken up this service. Mentors are being actively encouraged to vote on their podling releases so that the VOTEs show up on the general@ list with 3 +1 IPMC votes. While a couple of podlings have managed to do this, most still need extra votes by IPMC members outside their projects. The IPMC will need to look further into this. In a couple of cases, podlings canceled vote too early and were encouraged to continue voting. Incubator wiki is being deprecated, and it's been migrated to confluence. Some of the pages were missed in the transfer and infra are looking into why. The new wiki space has been reorganised and the pages categorised for easier navigation. A few minor issues have been encountered e.g. confluence ignoring formatting but have been addressed. A few people have had permission issues and because of this move mentor sign-off is a little lower than normal. The reorganisation and cleanup of incubator web pages started last month continues on. * Community New IPMC members: - Arpit Agarwal - Kevin Ratnasekera People who left the IPMC: None * New Podlings None * Podlings that failed to report, expected next month - Milagro - Toree * Graduations - Netbeans - PLC4X - SkyWalking The board has motions for the following: - Dubbo * Releases The following releases entered distribution during the month of April: - DLab 2.1 - Druid 0.14.0 - Dubbo Spring Boot 2.7.1 - Livy 0.6.0 - NetBeans 11.0 - OpenWhisk Client JS 3.19.0 - OpenWhisk Composer 0.11.0 - Ratis 0.3.0 - ShardingSphere 4.0.0 - Singa 2.0.0 * IP Clearance - Sling Journal-based Content Distribution - IP clearance for SkyWalking RocketBot UI * Legal / Trademarks None * Infrastructure None, although it still unknown if infrastructure will allow distribution of artefacts with IP or other serious issues. * Miscellaneous - Discussion of use of stack overflow |---------------------------------------------------------------------- Table of Contents brpc DataSketches Doris ECharts Edgent Heron MXNet PageSpeed Pinot Ratis S2Graph SDAP Tamaya Training Tuweni TVM |---------------------------------------------------------------------- -------------------- 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 issues to address in the move towards graduation: 1. We begin to prepare an apache release, including prepare for unified License/Copyright, clean dependencies. 2. We depend on npsr’ time, it is MPL/LGPL license, we need to find another lib for it. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? Added two potential committers, they are huwenwei and wangweibing , they will participate in the work of first apache release , and take some tasks already. . How has the project developed since the last report? There are many bugfix into the trunk. How would you assess the podling's maturity? Still in early stage 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: Still working on the first release When were the last committers or PPMC members elected? 2019/2. Jerrytan became a new member of PPMC Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [X](brpc) Kevin A. McGrail Comments: Improving steadily. [ ](brpc) Jean-Baptiste Onofré Comments: [X](brpc) Von Gosling Comments: IPMC/Shepherd notes: Von Gosling: brpc community should pay more warm in the community building except the first release. -------------------- DataSketches DataSketches is an open source, high-performance library of stochastic streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods. DataSketches has been incubating since 2019-03-30. Three most important unfinished issues to address before graduating: 1. Finish IP Assignments 2. Code Migration 3. Perform a Release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? We have the key committers signed up. We are all learning how to navigate in the Apache environment and how to find things. How has the project developed since the last report? This is our first report. 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: Our DataSketches.GitHub.io site is quite active as we are very active with new code and releases from this site. For example, our latest release of sketches-core was yesterday, 25 April 2019. We are a long way from being able to release from the migrated Apache code base as it doesn't yet exist. XXXX-XX-XX When were the last committers or PPMC members elected? We have just signed up are initial list of committers. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Kenneth Knowles has been extremely helpful! Thank you! Signed-off-by: [X](datasketches) Liang Chen Comments: [X](datasketches) Kenneth Knowles Comments: Initial set up has been a bit slow; that's on me [X](datasketches) Furkan Kamaci Comments: IPMC/Shepherd notes: -------------------- Doris Doris is a MPP-based interactive SQL data warehousing for reporting and analysis. Doris has been incubating since 2018-07-18. Three most important unfinished issues to address before graduating: 1. Hold a Meetup to communicate with developers and users. 2. Prepare for the second Apache Release. 3. Grow the community encouraging patches and recognizing sustained contributions by adding as Committers and PPMC members. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? There are 29 contributors now. How has the project developed since the last report? Excluding merges, 12 authors have pushed 75 commits to master and 233 commits to all branches. On master, 253 files have changed and there have been 14,050 additions and 3,027 deletions. 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: 2019-02-21 When were the last committers or PPMC members elected? N/A. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, our mentors have been helpful and responsive. Signed-off-by: [X](doris) Dave Fisher Comments: Will need to start discussions about possible new committers. [ ](doris) Willem Ning Jiang Comments: [ ](doris) Shao Feng Shi Comments: IPMC/Shepherd notes: -------------------- ECharts ECharts is a charting and data visualization library written in JavaScript. ECharts has been incubating since 2018-01-18. Three most important unfinished issues to address before graduating: 1. Apache domain name should be used for the Website. echartsjs.com and echarts.baidu.com should redirect to echarts.apache.org. Currently they are not redirecting due to slow loading time in China. We are working on with a CDN to improve the loading time in China. 2. Website Analytics information should be accessed by PPMC members. We are going to create an Analytics account that can be accessed by PPMC members. 3. Develop more committers from the community. Currently there are some contributors in the community that have contributed continuously and should be considered as new committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We haven't come to a conclusion whether we could use Baidu Tongji in the Website, which is a product quiet similar to Google Analytics. We've consulted John Kinsella as our mentor suggested, but got no reply. See https://lists.apache.org/thread.html/efa62d1ace0cc27f7ee4e47df94c346e863b6419f1d1e3ea6fe32c10@%3Cdev.echarts.apache.org%3E My suggestion is to use both Baidu Tongji and Google Analytics. The reason is that Baitu Tongji has only Chinese UI, while Google Analytics may have the potential of losing some data in China since many Google products are not accessible in China. If IPMC and ASF Board are OK with it, we will start a vote for the plan. How has the community developed since the last report? We have announced our first new committer from the community. More people come to contribute in the community, in the forms of code changes, document mending, and so on. How has the project developed since the last report? We released v4.2.1. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2019-03-21 When were the last committers or PPMC members elected? 2019-04-03 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes. Signed-off-by: [X](echarts) John D. Ament Comments: Glad to see issues getting unblocked as well as semi-recent release. [X](echarts) Kevin A. McGrail Comments: Nice to see things getting unblocked. I think a Terms & Conditions will be needed for my signoff on using Baidu's analytics but I'm not against it. [X](echarts) Dave Fisher Comments: Thanks to Infra the issues blocking a full move to apache.org domains are being addressed. The change is to build a one off CDN in China. [ ](echarts) Ted Liu Comments: Justin Mclean: Is Baidu analytics compliant with the GDPR (EU General Data Protection Regulation)? You might also want to see MXNet's report about needing an ICP filing when setting up CDN in China. I assume infra is handling this? IPMC/Shepherd notes: -------------------- Edgent Apache Edgent is a programming SDK and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Edgent provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge. Edgent has been incubating since 2016-02-29. Three most important issues to address in the move towards graduation: 1. Re-creating a working community 2. Re-populating the PPMC 3. Replenishing the group of mentors Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? For the past months, there has been very few activity in the project There have been a hand full of Emails from external peoples in the last 3 months but the activity in the project has been solely by me (Julian) and Christofer Dutz writing emails without getting any form of response from the rest of the committers, PPMCs or mentors Julian held a Talk on the conference buildingiot 2019 with very positive response and we have an Edgent Meetup on May, 6. Where we hope to see some new faces. The main problem we have is that the only active people in the project came in Late and are not that firm with the codebase. Currently, we have a codebase for which we have a detailed understanding of the build, but almost none of the code itself. Furthermore, there has been a lot of activity in other projects and generally edge processing has developed further in the recent years. Thus, there is some discussion going on about the core or the aim of the project to keep its significance and uniqueness. How has the community developed since the last report? * Total, we have 82 subscribers to our mailing list, an increase of 5 since the last report. * There has been one questions asked by users and little discussions about these issues on the list * On April, 4th, Julian Feinauer has Talked about Edgent on the building iot 2019 * On May, 6th, a Edgent Meetup is planned in Frankfurt How has the project developed since the last report? * According to JIRA, 0 new issue were added and none were resolved in the last 90 days How would you assess the podling's maturity? After the withdrawal of most of the active committers and PPCM members currently a new committer, PPMC and mentor-base has to be built. Currently we try to re-gain the focus of edgent to Start to rebuild the community and resume development. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-12-14 Apache Edgent 1.2.0 When were the last committers or PPMC members elected? In August 2017, we added Christofer Dutz as a new committer and PPMC member. In November 2018, we added Julian Feinauer as a new committer and PPMC member. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. I just double checked, but it seems our mentors are not existent there had been one or two issues where feedback was explicitly asked for, but both the PPMC as well as all mentors remained silent. Except Justin mentioning the absence of mentors. Christofer Dutz joined as new Mentor and is active in the project. Signed-off-by: [ ](edgent) Luciano Resende Comments: [X](edgent) Justin Mclean Comments: [X](edgent) Christofer Dutz Comments: IPMC/Shepherd notes: -------------------- Heron A real-time, distributed, fault-tolerant stream processing engine. Heron has been incubating since 2017-06-23. Three most important unfinished issues to address before graduating: 1. Making a new release with artifacts (more review required). 2. Making several Releases. 3. Continuing to grow the community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. How has the community developed since the last report? The community has been growing. Monthly meetups have been regularly and successfully organized. The April meetup was back in Twitter office and it was very successful. Many discussions and works have been done by the community. How has the project developed since the last report? There have been bug fixes and feature improvements. Some to note are: Set up new sub-project for Heron spouts by community Bazel upgrade Bug fixes in scripts of building artifacts Review and improve packing algorithms Fix memory leaks in binary components and add static/dynamic checks 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? 4 new committers were elected and invited in Feb 2019. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Dave has been helpful on answering questions and voting for releases. Signed-off-by: [ ](heron) Jake Farrell Comments: [ ](heron) Julien Le Dem Comments: [X](heron) P. Taylor Goetz Comments: Moving slowly but making progress. I would like to see more email activity and less slack. [X](heron) Dave Fisher Comments: IPMC/Shepherd notes: -------------------- MXNet A Flexible and Efficient Library for Deep Learning MXNet has been incubating since 2017-01-23. Three most important unfinished issues to address before graduating: 1. Increase diversity in contributors, committers, and PMC members — NEAR COMPLETION. 2. Identify remaining ICLAs or SGAs that need signing – NEAR COMPLETION. 3. Revisit Apache Maturity Model Assessment — TODO Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. Community reached consensus on Gluon branding. In the context of the Gluon API in MXNet, it would be mentioned as MXNet Gluon. https://lists.apache.org/thread.html/af7dcb430e2cedf23d1531e79877e8bf2b40ec392e40853a2d7015da@%3Cdev.mxnet.apache.org%3E 2. Community addressed the IP/licensing issues discovered during previous releases. Updated status can be found here: https://cwiki.apache.org/confluence/display/MXNET/MXNet+Source+Licenses 3. MXNet has significant user presence in China that are worth optimizing for in terms of infrastructure. Setting up CDN in China requires ICP filing. How has the community developed since the last report? * The number of GitHub contributors increased to currently 682 (2019-04-22; +4.4% since last report) * Active discussions on user forums https://discuss.mxnet.io/ (English, 1.6K registered users and 5.6K posts) https://discuss.gluon.ai/ (Chinese, 6K registered users and 19.2K posts) * Active blogs and social media presence Medium (https://medium.com/apache-mxnet) w/ 1.3k followers (+30% since last report). Twitter account (https://twitter.com/ApacheMXNet) w/ 2k followers on (+16% since last report) Meetup group (https://www.meetup.com/pro/deep-learning-with-apache-mxnet/) w/ 10 groups in 8 countries, 1998 members (+65% since last report) (in China) Zhihu w/ 7.5k followers, WeChat official account w/ 3k followers. (reported for the first time) * Active video channels YouTube channel (https://www.youtube.com/apachemxnet) w/ 627 subscriber (+29% since last report) Chinese YouTube channel (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 4.1k subscribers (reported for the first time) (in China) bilibili space (https://space.bilibili.com/209599371) w/ 13k subscriber (reported for the first time) * Highlights in MXNet ecosystem MXNet Gluon book (www.d2l.ai, Dive into Deep Learning/D2L) released v1.0.0-rc0 (https://github.com/d2l-ai/d2l-zh/releases/tag/v1.0.0-rc0) in Chinese and v0.6.0 (https://github.com/d2l-ai/d2l-en/releases/tag/v0.6.0) in English. Dive into Deep Learning has 47.5K 28-day active users, and has attracted 9.3K stars & 200+ contributors on GitHub. It has been adopted as a textbook or reference book by 15+ universities in U.S., China, Spain, and Australia, such as UC Berkeley. GluonCV v0.4.0 release (https://github.com/dmlc/gluon-cv/releases/tag/v0.4.0) GluonNLP v0.6.0 release (https://github.com/dmlc/gluon-nlp/releases/tag/v0.6.0) MXNet Model Server v1.0.2 release (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.0.2) GluonFace (https://github.com/THUFutureLab/gluon-face) DeepInsight (https://github.com/deepinsight/insightface) How has the project developed since the last report? 1) Released v1.4.0: https://github.com/apache/incubator-mxnet/releases/tag/1.4.0; https://blogs.apache.org/mxnet/entry/apache-mxnet-1-4-is1 2) Started v1.4.1 patch release https://lists.apache.org/thread.html/3bb49a1016fafd0840d14f099ce47c7a1822da45f7ca2187c0f03c64@%3Cdev.mxnet.apache.org%3E; Started roadmap discussion on short-term 1.5.0 release https://github.com/apache/incubator-mxnet/issues/14619; Started roadmap discussion on long-term 2.0 plan https://github.com/apache/incubator-mxnet/issues/9686; 3) Code donation from dmlc/mshadow. Community expressed the desire to assimilate dmlc/mshadow code base into mxnet. https://lists.apache.org/thread.html/c1ba34330b0eb52ef3a3a30da6d34964a35a01c 320e93067e94ed306@%3Cdev.mxnet.apache.org%3E. After discussion, DMLC reached agreement to donate dmlc/mshadow code to mxnet, which is its sole consumer. 4) Many ongoing projects: numpy-compatbile deep learning: https://github.com/apache/incubator-mxnet/projects/14; CPU performance and quantization: https://github.com/apache/incubator-mxnet/projects/15; Mixed precision GPU training (AMP): https://github.com/apache/incubator-mxnet/pull/14173, etc. 5) Github statistics of last month: * March 24, 2019 – April 24, 2019: Excluding merges, 53 authors have pushed 102 commits to master and 137 commits to all branches. On master, 495 files have changed and there have been 14,977 additions and 5,391 deletions. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release [x] Community building [x] Nearing graduation Date of last release: 2019-03-04 MXNet 1.4.0 When were the last committers or PPMC members elected? As recent as 2019-04-12. New committer since last report (+12): Iblis Lin, Da Zheng, Steffen Rochel, Lin Yuan, Nicolas Modrzyk, Jackie Wu, Aston Zhang, Ding Kuo, Patric Zhao, Kevin Qin, Jiajun Wu, Jeremie Desgagne-Bouchard New PPMC member (+1): Qing Lan Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors continue providing guidance and support. Signed-off-by: [x](mxnet) Henri Yandell Comments: Noting that Gluon is a trademark of Microsoft + Amazon's. [ ](mxnet) Markus Weimer Comments: [x](mxnet) Michael Wall Comments: [ ](mxnet) Bob Paulin Comments: [ ](mxnet) Jason Dai Comments: IPMC/Shepherd notes: Justin Mclean: You might want to talk to eCharts as they are also setting up a CDN with infra's help. -------------------- 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. Get the project site in order 2. Start releasing 3. Engage more active developers, expanding the community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? The number of active developers is low, we are still working to follow up on the recommendation to create a release. How has the project developed since the last report? - A first draft-release is being manually checked for policy compliance. We expect to be able to raise a thread on general soon to discuss/vote. - There has been some discussion how to get the project site in-order, and there's a plan for that now (transfer modpagespeed.com to the AFS, duplicate contents to pagespeed.incubator.apache.org). 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? Feb 2 2018 (Huibao Lin, elected as both committer and PMC member) Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors have been helpful. Signed-off-by: [ ](pagespeed) Jukka Zitting Comments: [ ](pagespeed) Leif Hedstrom Comments: [X](pagespeed) Nick Kew Comments: [ ](pagespeed) Phil Sorber Comments: IPMC/Shepherd notes: -------------------- Pinot Pinot is a distributed columnar storage engine that can ingest data in real- time and serve analytical queries at low latency. Pinot has been incubating since 2018-10-17. Three most important unfinished issues to address before graduating: 1. Building community contribution 2. Establish a successful release cadence Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? External contributors have made improvements to real-time segment split-commit algorithm to minimize controller access to segment store during segment commit phase. In addition they have also contributed towards other bug fixes, especially in the real-time area. How has the project developed since the last report? - We made our first release Apache Pinot 0.1.0 - We have added and improved a lot more documentation 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-03-07 When were the last committers or PPMC members elected? Committer Xiang Fu, who was already in the incubator proposal, was added. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes mentors have been helpful and responsive Signed-off-by: [ ](pinot) Kishore Gopalakrishna Comments: [x](pinot) Jim Jagielski Comments: [ ](pinot) Roman Shaposhnik Comments: [ ](pinot) Olivier Lamy Comments: [x](pinot) Felix Cheung Comments: great! IPMC/Shepherd notes: Drew Farris (shepherd): Looking great. At least 3 mentors active, observed development activity and interaction on the mailing lists. -------------------- Ratis Ratis is a java implementation for RAFT consensus protocol Ratis has been incubating since 2017-01-03. Three most important unfinished issues to address before graduating: 1. Establish a release cadence. 2. Podling name search. 3. Complete graduation template Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 1 new contributor has been added. Total 59 contributors currently. 20 committers (non-PPMC) and 19 PPMC members. How has the project developed since the last report? 32 commits, Released 0.3.0 version. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [X] Working towards first release [X] Community building [X] Nearing graduation [ ] Establish a release cadence Date of last release: 2019-04-26 When were the last committers or PPMC members elected? 2018-12-05 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes Signed-off-by: [ ](ratis) Jakob Homan Comments: [X](ratis) Uma Maheswara Rao G Comments: [ ](ratis) Devaraj Das Comments: IPMC/Shepherd notes: -------------------- S2Graph S2Graph is a distributed and scalable OLTP graph database built on Apache HBase to support fast traversal of extremely large graphs. S2Graph has been incubating since 2015-11-29. Three most important unfinished issues to address before graduating: 1. Make the third release. 2. Attract more users and contributors. 3. Build the developer community in both size and diversity. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? * There were some discussions on the documentation of the project. * There were some questions and answers from the community about the migration tool. How has the project developed since the last report? * Working on providing OpenAPI documentation for REST API. 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: 2017-08-26 When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. * Our mentor is very helpful and responsive. Signed-off-by: [ ](s2graph) Sergio Fernández Comments: [X](s2graph) Woonsan Ko Comments: IPMC/Shepherd notes: -------------------- SDAP SDAP is an integrated data analytic framework for Big Science problems. SDAP has been incubating since 2017-10-22. Three most important issues to address in the move towards graduation: 1. Make official SDAP (Incubating) Release 2. Improve/create user guide documentation 3. Improve committer participation Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Committership has been accepted by a community member. SDAP was presented at a Data Science Workshop @ JPL How has the project developed since the last report? SDAP is still working towards its first release. Mentors have provided some suggestions that will be taken into consideration for the Java parts of the project, but the python release process also needs to be better understood. A new tool has been published that helps with reading the output produced from the Matchup algorithm. 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 Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Maya Debellis was elected as a committer on 2019-02-08 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, mentors have been helpful and responsive. Signed-off-by: [ ](sdap) Jörn Rottmann Comments: [X](sdap) Trevor Grant Comments: IPMC/Shepherd notes: -------------------- Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important unfinished issues to address before graduating: 1. Grow the PPMC from the existing community. 2. Make another Release 3. Blog about Tamaya Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We'd like to graduate soon. How has the community developed since the last report? No new committers or contributors added, but some interaction via Github pull requests - thanks for the new possibilities. How has the project developed since the last report? Minor changes and SonarCloud integration, homepage improvements. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [X] Nearing graduation [ ] Other: Date of last release: 2017-05-28 0.3-incubating When were the last committers or PPMC members elected? * 2018-12: Aaron Coburn * 2018-12: William Lieurance Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. A new mentor was introduced but did not yet send anything to mailing lists. Signed-off-by: [X](tamaya) John D. Ament Comments: The podling is likely in need of more mentors who can pay closer attention if they want to survive (an additional mentor was added but has yet to participate in the podling). I'm not sure how much of a community is here to be honest, while development works well (slow, but well) not seeing much consumer interaction. [ ](tamaya) David Blevins Comments: [ ](tamaya) Kanchana Pradeepika Welagedara Comments: IPMC/Shepherd notes: -------------------- Training The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects. Training has been incubating since 2019-02-21. Three most important issues to address in the move towards graduation: 1. Agree upon underlying technology stack and architecture for training content 2. Develop first training topic contents 3. Set up our contribution process Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - no critical issues at this point in time How has the community developed since the last report? - The project has been set up recently, so there is an initial activation/development towards a community. - The dev mailing list is active. The total number of posts in March was 160 and in April 140 - Total number of subscribers is 32 (25 in March) How has the project developed since the last report? - The scope of the project deliverables and core procedures are still under discussion (e.g. what makes a release?) - We have had our first few commits. They were for infrastructure (e.g. website) and repository structure - We have been approached by a few more people wanting to donate content and we hope to be able to accept it soon - We actually have the first issue for an actual content donation (Apache Way, ZooKeeper and Git) and hope to have it included soon, the first ones will probably be slow while we work on processes and best practices 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? n.a. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [X](training) Justin Mclean Comments: [x](training) Craig Russell Comments: [X](training) Christofer Dutz Comments: [x](training) Lars Francke Comments: Excited to finally discuss actual content! IPMC/Shepherd notes: -------------------- Tuweni Apache Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralised software in Java and other JVM languages. Apache Tuweni has been incubating since 2019-03-25. Three most important unfinished issues to address before graduating: 1. Grow the community; 2. Have the works of the project comply with legal requirements of the ASF; 3. Consistently releasing products; Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Currently there are no issues that require the involvement of either the Incubator PMC or the ASF board. How has the community developed since the last report? As this is the first full month of the project incubating the development of the community has been low. The project started out with onboarding all parties showing interest at the pre-incubation discussions in general@incubator.a.o. The project consists of a healthy number of mentors and committers/PPMC Members. How has the project developed since the last report? All required INFRA services have been put in play to have the community collaborate. The project is working on getting more body to the whole set of information pages (website, wiki, etc.) The project is working on getting its first release product vetted and released, and is also working on getting the Incubator clutch details up to date. How would you assess the podling's maturity? [X] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: Nothing has been released yet. When were the last committers or PPMC members elected? No new committers and or PPMC members have been elected since bootstrapping the project. Have your mentors been helpful and responsive or are things falling through the cracks? Our participating mentors have been very helpful sharing their insights in a timely manner. Kudos to them! Signed-off-by: [x](tuweni) Jim Jagielski Comments: [X](tuweni) Dave Fisher Comments: Good start! Already reviewing release candidates [ ](tuweni) Kenneth Knowles Comments: [ ](tuweni) Jean-Baptiste Onofré Comments: [x](tuweni) Michael Wall Comments: [X](tuweni) Furkan Kamaci Comments: IPMC/Shepherd notes: -------------------- TVM TVM is a full stack open deep learning compiler stack for CPUs, GPUs, and specialized accelerators. It aims to close the gap between the productivity- focused deep learning frameworks, and the performance- or efficiency-oriented hardware backends. TVM has been incubating since 2019-03-06. Three most important unfinished issues to address before graduating: 1. Source code and website migration to ASF infra 2. Make the first Apache release 3. Continue to grow the community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? TVM community has welcomed one new committer in the past month How has the project developed since the last report? In the past month, 51 contributors have pushed 109 commits to master and 109 commits to all branches. On master, 1,763 files have changed and there have been 44,070 additions and 13,852 deletions. See detailed monthly report - Mar: https://discuss.tvm.ai/t/tvm-monthly-march-2019/2083 - April: https://discuss.tvm.ai/t/tvm-monthly-april-2019/2426 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: not yet When were the last committers or PPMC members elected? 2019 April 22 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors are very helpful in helping to set up the podling and provide helpful guidance. Signed-off-by: [X] (tvm) Markus Weimer Comments: [ ](tvm) Byung-Gon Chun Comments: [ ](tvm) Sebastian Schelter Comments: [X](tvm) Henry Saputra Comments: [ ](tvm) Timothy Chen Comments: [X](tvm) Furkan Kamaci Comments: IPMC/Shepherd notes: ----------------------------------------- Attachment AD: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AE: Report from the Apache jUDDI Project [Alex O'Ree] ## Description: - jUDDI (pronounced "Judy") is an open source Java implementation of the Universal Description, Discovery, and Integration (UDDI v3) specification for (Web) Services. The jUDDI project includes Scout. Scout is an implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR). ## Issues: - There are no issues that require the board's attention at this time. ## Activity: - jUDDI - last release was 04 DEC 2018. Resolved several requisite bugs for updating SCOUT. - SCOUT - last release 10 DEC 2018. Resolved several bugs and dependencies. ## Health report: - Low development activity is a factor for low mailing list volume, but in all likelihood, it's from a general lack of interest in the protocol. - There are enough active PMC members to approve releases and respond to potential security issues. There were no issues raised since the last report. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Alex O'Ree on Sun Mar 17 2013 ## Committer base changes: - Currently 7 committers. - No new changes to the committer base since last report. ## Releases: - 3.3.6 was released on Tue Dec 04 2018 - SCOUT-1.2.8 was released on Mon Dec 10 2018 ## Mailing list activity: - dev@juddi.apache.org: - 68 subscribers (up 0 in the last 3 months): - 7 emails sent to list (106 in previous quarter) - user@juddi.apache.org: - 108 subscribers (up 0 in the last 3 months): - 4 emails sent to list (4 in previous quarter) ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AF: Report from the Apache Juneau Project [James Bognar] ## Description: - A universal toolkit for marshalling POJOs to a wide variety of content types using a common framework. - A universal REST server API for creating REST interfaces using POJOs simply deployed in any Servlet 3.1.0+ container. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We're actively working on release 8.0.1. ## Health report: - We had a burst of interest and activity in December that has tapered off somewhat. However we expect activity to pick up again once 8.0.1 is released. There are a couple of developers that have recently expressed interest in joining the project. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ayeshmantha Perera on Wed Jan 02 2019 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Ayeshmantha Perera at Wed Jan 02 2019 ## Releases: - Last release was 8.0.0 on Sat Dec 22 2018 ## Mailing list activity: - December of last year was a busy month due to the 8.0.0 release. Activity has expectedly slowed since. - dev@juneau.apache.org: - 29 subscribers (up 0 in the last 3 months): - 52 emails sent to list (461 in previous quarter) ## JIRA activity: - 12 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AG: Report from the Apache Kafka Project [Jun Rao] Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development We released 2.2.0 which includes new features such as separate control and data planes, re-authentication in SASL, better fencing with broker epoch, more functionalities in KStreams, etc. We also released 2.1.1, which fixes more than 30 issues. We are actively working on new features such as incremental client rebalancing, MirrorMaker 2.0, improvements in KStreams and AdminClient, etc. Community Lots of activities in the mailing list. We have 2806 subscribers in the user mailing list, about the same as in the last 3 months. We have 624 emails in the user mailing list in the last 3 months, about the same as in the previous cycle. We have 1305 subscribers in the dev mailing list, about the same as in the last 3 months. We have 2152 emails in the dev mailing list in the last 3 months, more than the 1947 in the previous cycle. We added one new committer Randall Hauch on Feb. 14, 2019. We added two new PMC members Sriharsh Chintalapan and Matthias J. Sax on Apr. 18, 2019. We also elected a third new PMC member. Unfortunately, that person declined the invitation due to shifted focus. Kafka Summit New York completed on Apr. 2, 2019, with more than 700 participants. Confluent published two public guidelines on respecting ASF policies. https://www.confluent.io/apache-guidelines https://www.confluent.io/apache-engineering-guidelines Releases =========== 2.2.0 was released on Mar. 26, 2019. 2.1.1 was released on Feb. 19, 2019. ----------------------------------------- Attachment AH: Report from the Apache Kibble Project [Rich Bowen] Apache Kibble is a suite of tools for collecting, aggregating and visualizing activity in software projects. http://kibble.apache.org/ ## Issues: There are no issues requiring board attention at this time. ## Activity and Health The was an uptick in traffic on the issues list - 16 emails sent to list (0 in previous quarter) - reflecting new activity from new contributors. However, we still remain in a situation where almost all code is from one contributor, which is a continuing source of concern. We continue to engage with other metrics agencies, with CHAOSS being at the top of that list. But this has not yet, so far, mapped into much actual new activity. We have had requests to add new sources to Kibble, which shows that new users from within Apache are becoming interested in understanding and using the stats that we provide. Most recently, we added Tuweni. And we have engaged with the dev lists of these projects to let them know that they've been added, in the hopes of receiving further feedback from those communities. To answer questions from last report: On the "finding more people interested in the project" and "research on the topic" part - are you aware of the work being done at https://osr.cs.fau.de/people/ (I just recently came across several publications by Maximilian Capraro and Michael Dorner on open source and inner source activity metrics.) I am not specifically familiar with these people and their work. Others on the project may be. I will start a discussion of those individuals on our lists, and attempt to reach out to them. Thank you. Another question to think about when trying to recruit more volunteers: How easy is it to setup Kibble without any prior experience? How easy is it to extend it? The process for getting Kibble running - https://apache-kibble.readthedocs.io/en/latest/setup.html - is indeed a little intimidating. There has been discussion in the past about how to simplify, or package, so that getting started isn't quite so onerous, but here, too, we suffer from lacking the volunteer effort to make this happen. As for ease of extending - we believe it to be fairly easy, but the proof is in people actually trying and reporting their success - something that we have so far mostly lacked. Another question one could think about: Who are potential users and where do you find them (inside and outside the ASF)? Potential users include any organization with some kind of Open Source Programs Office, who wants to analyze their company's participation in open source. And any university which is doing research in open source in general. It may indeed be worthwhile trying to reach out to those groups specifically. We get good responses from both of those groups to our demos at FOSDEM, but followup is weak. Thank you for your questions, as they indicate useful directions where we might do more active outreach. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rafael Weingärtner on Fri Dec 08 2017 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Rafael Weingärtner at Sat Dec 09 2017 ## Releases: We have not yet made a release. ## Mailing list activity: List activity was flat from previous months, with the exception of the increased traffic on the issues@ list, as mentioned above. We hope that this is a trend that will continue. Issues, and associated pull requests, were responded to swiftly, and the individuals involved appear to have remained engaged. Time will tell. ----------------------------------------- Attachment AI: Report from the Apache Knox Project [Larry McCay] ## Description: - The Apache Knox Gateway is an HTTP/REST API Gateway for interacting with Apache Hadoop clusters. The Knox Gateway provides a single access point for all REST/HTTP interactions with Apache Hadoop clusters. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Knox continues to leverage the KIP approach to communicate designs and proposals but has also integrated Github Pull Requests. The 1.3.0 release was proposed as mid April and we will start the close down in the next week or so. - There are a number of new contributors that are emerging as possible committer/PMC candidates and we will consider invitations over the next quarter or so. ## Health report: - Mail and commits continue to be at a good level. There were previously inflated email counts due to jenkins job failures as indicated in previous reports. These seem to be fewer - presumably due to the use of PRs instead of patches on JIRA. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kevin Risden on Mon Apr 02 2018 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Kevin Risden at Tue Apr 03 2018 ## Releases: - Last release was 1.2.0 on Mon Dec 17 2018 ## Mailing list activity: - dev@knox.apache.org: - 92 subscribers (down -2 in the last 3 months): - 1966 emails sent to list (2448 in previous quarter) - user@knox.apache.org: - 129 subscribers (down -4 in the last 3 months): - 83 emails sent to list (53 in previous quarter) ## JIRA activity: - 100 JIRA tickets created in the last 3 months - 100 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache Kylin Project [Luke Han] ## Description: Apache Kylin is an open source Distributed Analytics Engine designed to provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop supporting extremely large datasets. ## Issues: - There are no issues requiring board attention at this time ## Activity: - 2019/04/13 Apache Kylin Meetup at Beijing ## PMC changes: - Currently 21 PMC members. - Kaisen Kang was added to the PMC on Sun Apr 14 2019 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Chunen Ni at Fri Nov 30 2018 ## Releases: - 2.6.1 was released on Fri Mar 08 2019 - 3.0.0-alpha was released on Fri Apr 12 2019 ## Mailing list activity: - dev@kylin.apache.org: - 460 subscribers (down -3 in the last 3 months): - 520 emails sent to list (535 in previous quarter) - issues@kylin.apache.org: - 103 subscribers (up 1 in the last 3 months): - 2621 emails sent to list (2496 in previous quarter) - user@kylin.apache.org: - 426 subscribers (up 14 in the last 3 months): - 248 emails sent to list (274 in previous quarter) ## JIRA activity: - 189 JIRA tickets created in the last 3 months - 142 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache Lens Project [Amareshwari Sriramadasu] ## Description: - Lens provides an Unified Analytics interface. Lens aims to cut the Data Analytics silos by providing a single view of data across multiple tiered data stores and optimal execution environment for the analytical query. It seamlessly integrates Hadoop with traditional data warehouses to appear like one ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Code reviews have been moved to github pull requests - There is no other development work that happened in this quarter ## PMC changes: - Currently 18 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Puneet Gupta on Tue Sep 20 2016 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Rajitha R at Fri Feb 09 2018 ## Releases: - Last release was 2.7 on Tue Feb 06 2018 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AL: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description: Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. ## Issues: There are no issues which require board attention at this time. ## Activity: We still receive a good amount of contributions on Github and JIRA, but overall the activity has dropped. That's mostly due to lack of active committers / PMC who would have time to review contributions and guide and help contributors. We are trying to recruit more committers / reviewers, but it's not easy due to the nature of the project (driver / plugin model where most people only care about a very small part of a project - e.g. either a single driver or a particular change in the driver they are interested in). ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 21 committers. - Rick van de Loo was added as a committer on Tue Jun 26 2018 ## Releases: - 2.4.0 was released on Thu Nov 08 2018 - 2.3.0 was released on March 03, 2018 - 2.2.1 was released on September 21, 2017 ----------------------------------------- Attachment AM: Report from the Apache Logging Services Project [Matt Sicker] ## Description: - The Apache Logging Services Project creates and maintains open-source software related to the logging of application behavior and released at no charge to the public. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Andrei Ivanov was added as a committer with a particular interest on Log4j Audit. - Log4j 2.11.2 was released with new database appender improvements, many bugfixes, a new internal build system for detecting API changes between releases, and some performance improvements. - Early discussions on a new Groovy configuration DSL have begun. - Small activity around log4cxx on mailing lists. - Early discussions on releasing log4net. Due to the lack of contributors and expertise in .NET in the Logging PMC, forming a release has been challenging. However, we are planning to work on some knowledge transfers during this next release to help keep this project component viable. ## Health report: - The project overall remains active and healthy. Overall activity was less this quarter than previous. - The log4net component has been struggling lately due to lack of contributors. Based on mailing list and jira interest, the project itself continues to have many users, though attracting new committers hasn't materialized. - Similarly, log4cxx has very little activity, and log4php has almost none. These concerns appear to date back several years at this point. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Carter Kozak on Sun Jul 29 2018 ## Committer base changes: - Currently 35 committers. - Andrei Ivanov was added as a committer on Thu Apr 18 2019 ## Releases: - LOG4J-2.11.2 was released on Tue Feb 05 2019 ----------------------------------------- Attachment AN: Report from the Apache ManifoldCF Project [Karl Wright] Project description ============== ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr, OpenSearchServer or ElasticSearch. ManifoldCF also defines a security model for target repositories that permits them to enforce source repository security policies. Releases ======== ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then, there have been numerous major releases, including a 2.12 release on December 20, 2018. The next major release is currently undergoing voting. Committers and PMC membership ============================= We nominated and approved Markus Schuch as a PMC member on 12/29/2017. We did not sign up any new committers this quarter. We continue to be on the lookout for new PMC members and committers. There are several candidates at this time but we have not yet held a vote for committership. We have seen a noted change in the willingness of users of this project to get involved in its maintenance and development. This could be interpreted as fewer active developers using the product and more inexperienced integrators. We have no solution for this development. Mailing list activity ===================== Mailing list activity has been fairly active this quarter, and requests for development have been high. Unfortunately the requests have exceeded the capacity of the team to carry them out, with some notable exceptions. Requests to redevelop connectors due to the end-of-life of many repository APIs is the most concerning development, since the team has neither the time resources nor the software access to perform these without significant assistance from the requestors. Still, we managed to upgrade one connector this cycle, and another rework is underway. I am unaware of any mailing list question that has gone unanswered. ----------------------------------------- Attachment AO: Report from the Apache Marmotta Project [Jakob Frank] ## Description: Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013. ## Issues: There are no major issues requiring board attention at this time. ## Activity: Another quiet quarter to report without significant development activities. After the last report a small discussion about the project status started on users@m.a.o. No actual conclusion was reached, but at least it shows that there still is a community present. ## Health report: The project was considered feature-complete since 3.3.0 and has recently published version 3.4.0. Currently there are no active development activities. ## PMC changes: - Currently 11 PMC members. - Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016 ## Committer base changes: - Currently 13 committers. - Xavier Sumba was added as a committer on Mon Mar 27 2017 ## Releases: - Last release was 3.4.0 on Tue Jun 12 2018 ## Mailing list activity: - users@marmotta.apache.org: - 118 subscribers (up 0 since last report): - 24 emails sent to list (2 in previous report) - dev@marmotta.apache.org: - 95 subscribers (up 0 since last report): - 10 emails sent to list (18 in previous report) ## JIRA activity: - 0 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: Report from the Apache Mesos Project [Benjamin Hindman] ## Description: - Apache Mesos abstracts CPU, memory, storage, and other compute resources away from machines (physical or virtual), enabling fault-tolerant and elastic distributed systems to easily be built and run effectively. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - 1.8.0 release is underway. ## Health report: - The project continues to see new bug reports, bug fixes, features, reviews and releases. The mailing lists, slack and IRC channels are also active with healthy discussions. Multiple active working groups (containerization, performance, API, community). ## Committer base changes: - Currently 48 committers. - New commmitters: - Andrei Budnik was added as a committer on Wed Mar 06 2019 - Benno Evers was added as a committer on Mon Feb 18 2019 ## Releases: - 1.4.3 was released on Thu Feb 21 2019 - 1.5.3 was released on Mon Mar 18 2019 - 1.6.2 was released on Sun Feb 24 2019 - 1.7.2 was released on Thu Feb 21 2019 ## JIRA activity: - 208 JIRA tickets created in the last 3 months - 288 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AQ: Report from the Apache MetaModel Project [Kasper Sørensen] ## Description: Providing a common interface for discovery, exploration of metadata and querying of different types of data sources. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Version 5.3.0 was released in early April. ## Health report: - The project is continuing the "slow but steady" modus. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dennis Du Krøger on Mon Sep 05 2016 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Jörg Unbehauen at Thu May 03 2018 ## Releases: - 5.2.1 was released on Thu Mar 07 2019 - 5.3.0 was released on Wed Apr 03 2019 ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: Report from the Apache NetBeans Project [Geertjan Wielenga] Apache NetBeans is a development environment, tooling platform, and application framework. The project entered the incubator in October 2016 and in April 2019 graduated to become a top level Apache project. Three releases have been completed in the incubator, the most recent release having been at the end of March 2019, and the first release outside the incubator is aimed to be released in June 2019. The current aim is to attempt to release 4 times per year, as time-based rather than feature-based releases. The Apache top level infrastructure has been set up with thanks to the Apache Infra team: https://issues.apache.org/jira/browse/INFRA-18261 The last committers and PMC members have been voted in during April 2019, Vikas Prabhakar and Sarvesh Kesharwani. In the incubator, everyone voted on was automatically both a committer and committee member; now that we're a top level project we are going to separate those two, as guided by our mentors, so that we'll first vote on committers and then in time evaluate whether they are suitable as PMC members. Currently, 691 are signed up to the user mailing list, and 452 to the developer mailing list, both of which is a slight increase over the numbers in the last incubator report of April 2019. A main task coming up is the rerouting of netbeans.org to netbeans.apache.org, a first attempt was made, there were several unexpected side effects, and we rolled back, hoping to try again soon. Another task in progress is the completion of the donation of NetBeans from Oracle to Apache, which will still take some time: though the main features have been donated, several ancillary features, in particular support for C/C++ development, is still in progress, being audited, scrubbed, etc. A rough estimate is that it should take at least another year before all the source code of NetBeans at Oracle is donated to Apache. ----------------------------------------- Attachment AS: Report from the Apache Oozie Project [Gézapeti] ## Description: - Oozie is a workflow scheduler system to manage Apache Hadoop jobs. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Most development is related to dependency-cleanups, security and stability. ## Health report: - Project is healthy with ongoing development - Development activity slowed down, we're planning on enabling pull request support to make contribution easier ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andras Piros on Thu Jun 21 2018 ## Committer base changes: - Currently 25 committers. - Andras Salamon was added as a committer on Thu Feb 14 2019 ## Releases: - Last release was 5.1.0 on Wed Dec 19 2018 ## JIRA activity: - 52 JIRA tickets created in the last 3 months - 54 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache Open Climate Workbench Project [Huikyo Lee] ## Description: - The OCW includes a Python open-source library for common climate model evaluation tasks as well as a set of user-friendly interfaces for quickly configuring a model evaluation task. OCW also allows users to build their own climate data analysis tools, such as the statistical downscaling toolkit. ## Issues: - Our major updates are pending and subject to approval from the PMC members' organization. ## Activity: - We are refactoring and testing OCW by using xarray and pandas. ## Health report: - There are no issues. ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ibrahim Jarif on Mon Apr 25 2016 ## Committer base changes: - Currently 30 committers. - No new committers added in the last 3 months - Last committer addition was Christopher Douglas at Tue Apr 26 2016 ## Releases: - Last release was 1.3.0 on Mon Apr 23 2018 - dev@climate.apache.org: - 63 subscribers - 0 emails sent to list ## JIRA activity: - 0 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AU: Report from the Apache Perl Project [Philippe Chiasson] ----------------------------------------- Attachment AV: Report from the Apache Phoenix Project [Josh Elser] ## Description: - Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop ## Issues: - There are no issues requiring board attention at this time ## Activity: - Continuing an excellent stream of new committers and PMC members (details below). Two more committers have been confirmed via a VOTE but are pending acceptance and clerical tasks to complete the addition. - 4.14.2 is nearing completion. RC0 was voted on, but did not pass. - 5.0.1 is getting close to an initial vote, but has some stabilization/cleanup work yet to do. Appears to be naturally queueing up after 4.14.2 nicely. - A community event ("NoSQL Day"), focusing on Accumulo, HBase, and Phoenix is scheduled for May 21st in Washington, D.C. We have half a dozen Phoenix specific talks accepted on the agenda for the event. ## Health report: - Nothing notable to report. Trends are continuing per normal. Influx of "new blood" is a boon to the community, reflected in a good number of commits and reviews by "old" community members. ## PMC changes: - Currently 30 PMC members. - New PMC members: - Chenglei (2019/04/09) - Geoffrey Jacoby (2019/04/09) ## Committer base changes: - Currently 42 committers. - New committers: - Mihir Monani (2019/04/27) - Abhishek Singh Chouhan (2019/04/05) ## Releases: - 4.14.1 was released on 2018/11/14 - 5.0.0 was released on 2018/07/14 ## Mailing list activity: - Activity is largely in-line with history. No significant changes to trends to be identified. ----------------------------------------- Attachment AW: Report from the Apache PLC4X Project [Christofer Dutz] Apache PLC4X is a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. # Project Status: We are currently in the post graduation phase. All post-graduation tasks have been performed and project activity is picking up again after finishing the pre- and post-graduation work. Also did we invest a lot of effort in preparing the project (especially the build) for upcoming activity with additional languages such as C# and Python. The graduation media coverage was quite extensive and did bring a lot of inquiries from outside entities which we are currently processing. There is a lot of potential for new contributors as well as cooperation with other open source initiatives. # Issues, the board needs to be aware of or act on: none # Activity since last report: This is our first report as TLP, so this answer will refer to the time since the last podling report, which was last month. Mostly pre- and post-graduation work. Handling inquiries from external entities as a result of the graduation media attention. A lot of discussions about other languages and driver generation have been has on the mailing list and the build was prepared for the challenges of the near future. # Plans for the near future: A delegation of 3 PMCs and 2 non-PMCs will be attending the European Union EU-FOSSA2 Hackathon in Brussels with the goal to grow the public awareness as well as the community. We are currently working on setting up a Python API where we will be testing providing an intermediate solution to the unavailability of native drivers in other languages by bundling a Java server with Python client. In parallel there are currently two initiatives for defining a way to formally specify industrial protocols and to generate native code in multiple languages from these definitions. These efforts will be an ongoing effort for the next months. We will be having a first PLC4X Meetup in the next month or two where we will also be doing a little graduation party. # Numbers: Mailing List Subscriptions: 45 (up by 2) Twitter Followers: 160 (up by 30) GitHub Stars: 62 (up by 10) Last release: 2019-03-13: PLC4X (incubating) 0.3.1 (Last release from the incubator) # Last election of Committers/PMCs: 2019-02-04: Tim Mitsch (PPMC and committer) # PMC and Committer diversity: no issues # Project branding or naming issues: none # Legal issues or questions: none # Infrastructure issues or strategic needs: none ----------------------------------------- Attachment AX: Report from the Apache POI Project [Dominik Stadler] Report from the Apache POI committee [Dominik Stadler] ## Description: - Apache POI is a Java library for reading and writing Microsoft Office file formats The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans is a tool that allows you to map XML files to generated Java classes via XML Schema definitions. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Apache POI 4.1.0 was released, it features a new EMF renderer and support for SVG images in XSLF, improvements to Java 9+ support, a handful of new formula function implementations and numerous bug fixes. Early testing of JDK 12 and 13 builds continued. ### XMLBeans - In this period we released XMLBeans 3.1.0 with some important stability fixes. Work is ongoing to refresh the buildsystem to remove some unnecessary complexity and make it easier for developers to build and use modern IDEs for development. Also some work on better support for Java 9+ is planned. ## Health report: - There was some discussions of how to perform some non-standard effects with Microsoft document formats and other discussions which indicate that the popularity of Apache POI is still very good. Questions via email or on Stackoverflow usually get answers quickly. Bug influx was moderate this quarter, bug-numbers stayed mostly constant, some bug influx and some bugs could be fixed, also some bugs were closed as WON'TFIX after being dormant for a long time. Bug influx for XMLBeans is very low because it is a stable project in maintenance-mode. ## PMC changes: - Currently 31 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Vladislav Galas on Sun Dec 30 2018 ## Committer base changes: - Currently 38 committers. - No new committers added in the last 3 months - Last committer addition was Vladislav Galas at Wed Dec 26 2018 ## Releases: - 4.1.0 was released on Mon Apr 08 2019 - XMLBeans-3.1.0 was released on Tue Mar 26 2019 ## Mailing list activity: - Some unsubscribtions, no apparent reason, user base still fairly large and active - dev@poi.apache.org: - 221 subscribers (down -2 in the last 3 months): - 535 emails sent to list (609 in previous quarter) - general@poi.apache.org: - 124 subscribers (up 0 in the last 3 months): - 6 emails sent to list (4 in previous quarter) - user@poi.apache.org: - 569 subscribers (down -14 in the last 3 months): - 58 emails sent to list (116 in previous quarter) ## Bugzilla Statistics: ### Apache POI - 55 Bugzilla tickets created in the last 3 months - 54 Bugzilla tickets resolved in the last 3 months - 528 bugs are open overall (+2) - Having 147 enhancements (+6) - Thus having 381 actual bugs (-4) - 88 of these are waiting for feedback (-11) - Thus having 293 actual workable bugs (+7) - 4 of the workable bugs have patches available (+-0) - Distribution of workable bugs across components: {HSSF=81, XSSF=77, SS Common=39, HWPF=37, XWPF=19, SXSSF=11, XSLF=7, POI Overall=6, POIFS=4, HPSF=3, OPC=3, HSLF=2, HPBF=1, HSMF=1, SL Common=1, XDDF=1} ### Apache XMLBeans - 172 open issues (-3) - Bug 128 (+-0) - Improvement 22 (-1) - New Feature 18 (-1) - Wish 4 (-1) ----------------------------------------- Attachment AY: Report from the Apache Qpid Project [Robert Gemmell] Apache Qpid is a project focused on creating software based on the Advanced Message Queuing Protocol (AMQP), currently providing a protocol engine library, message brokers written in C++ and Java, a message router, and client libraries for C, C++, Go, Java/JMS, Python, and Ruby. # Releases: - Qpid Proton 0.27.0 was released on 9th February 2019. - Qpid Broker-J 7.0.7 was released on 28th February 2019. [1] - Qpid Broker-J 7.1.1 was released on 28th February 2019. [1] - Qpid Dispatch 1.6.0 was released on 28th March 2019. - Qpid Proton-J 0.32.0 was released on 1st April 2019. - Qpid Broker-J 7.1.2 was released on 4th April 2019. - Qpid JMS 0.41.0 was released on 8th April 2018. - Qpid Dispatch 1.7.0 was released on 16th April 2019. - Qpid Proton 0.27.1 was released on 22nd April 2019. [2] - Qpid Proton-J 0.33.0 was released on 4th May 2019. [1] Broker-J 7.0.7 and 7.1.1 addressed CVE-2019-0200. [2] Proton 0.27.1 addressed CVE-2019-0223. # Community: - The main user and developer mailing lists continue to be active and JIRAs are being raised and addressed, in line with prior activity levels. - Jiri Danek was added as a committer on 23rd February 2019. - There were no new PMC additions in this quarter. The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017. # Development: - Proton-C and its language bindings had their 0.27.0 and 0.27.1 releases, incorporating various bug fixes and improvements. A candidate for a 0.28.0 release is currently under vote. - The AMQP 1.0 JMS client had its 0.41.0 release with various bug fixes and improvements. Work continues on more, with a candidate 0.42.0 release currently under vote. - Dispatch router had its 1.6.0 and 1.7.0 releases, and work is under way toward a 1.8.0 with various improvements and bug fixes. - Broker-J 7.0.7 and 7.1.1 + 7.1.2 were released, adding various improvements and bug fixes. Work continues on more toward 8.0.0, with backports to the 7.1.x line as appropriate. - Proton-J had its 0.32.0 and 0.33.0 releases with various fixes and improvements for its dependent components. Work continues on more. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment AZ: Report from the Apache REEF Project [Sergiy Matusevych] ## Description: - Apache REEF (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Finishing work on .Net elastic broadcast. Planning a new release this year. ## Health report: - The engagement from the community has been declining perhaps because the codebase has been stable. - All work is currently in the elastic broadcast pull request (600+ comments/fixes). - We plan to issue a new release as soon as we merge the elastic group communication into master. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Doug Service on Thu Sep 28 2017 ## Committer base changes: - Currently 35 committers. - No new committers added in the last 3 months - Last committer addition was Scott Inglis at Thu Sep 27 2018 ## Releases: - Last release was 0.16 on Wed Aug 09 2017 ## Mailing list activity: - dev@reef.apache.org: - 86 subscribers (up 0 in the last 3 months): - 9 emails sent to list (16 in previous quarter) - user@reef.apache.org: - 20 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BA: Report from the Apache River Project [Peter Firmstone] ----------------------------------------- Attachment BB: Report from the Apache RocketMQ Project [Xiaorui Wang] ## Description: The Apache RocketMQ 4.5.0 version released, provided the multi-replicas storage based on raft algorithm. ## Issues: There are no issues requiring board attention at this time ## Activity: (1)Apache RocketMQ is continuing to improve the surrounding ecological construction, especially the Connect ecosystem, and will build a number of Connect based on the full discussion of the community, such as MySQL Connect, MongoDB Connect, etc. (2)Continuously improve multi-language client,guaranteed consistency with the JAVA client. ## Health report: (1)The continuous development of community projects ensures community activity (2)Community participants are becoming more familiar with Apache way, community users have gradually developed the habit of using mailing lists. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Du Heng on Mon Dec 24 2018 ## Committer base changes: - Currently 20 committers. - New commmitters: - Zong Tang Hu was added as a committer on Thu Mar 07 2019 - Qipeng Li was added as a committer on Thu Mar 07 2019 ## Releases: - 4.5.0 was released on Thu Apr 04 2019 ## Mailing list activity: - users@rocketmq.apache.org: - 252 subscribers (up 14 in the last 3 months): - 95 emails sent to list (211 in previous quarter) - dev@rocketmq.apache.org: - 191 subscribers (down -20 in the last 3 months): - 2434 emails sent to list (2395 in previous quarter) - issues@rocketmq.apache.org: - 97 subscribers (up 11 in the last 3 months): - 0 emails sent to list (0 in previous quarter) ----------------------------------------- Attachment BC: Report from the Apache Roller Project [David M. Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat and MySQL, and is known to run on other Java servers and relational databases. Latest release is 5.2.2 and the ASF blog site at blogs.apache.org runs on Roller 5.1.2 Tomcat and MySQL. ## Issues: - There are no other issues requiring board attention at this time ## Activity: - Currently preparing a Roller 5.2.3 release to address some bugs - Currently working with Infra to get a blogs-test server setup to test Roller 6 for blogs.apache.org ## Health report: - Community is made-up of part-time volunteers with limited time to devote to Roller. Currently only one committer is actively working on developing Roller and making release. For the most part other committers only have time to review and test release. - Vote underway for a new committer, and initiated discussion with another possible candidate. ## PMC changes: - Currently 5 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kohei Nozaki on Sun Dec 06 2015 ## Committer base changes: - Currently 8 committers. - No new committers added in the last 3 months - Last committer addition was Kohei Nozaki at Mon Mar 09 2015 ## Releases: - Last release was 5.2.2 on Wed Jan 09 2019 ## Mailing list activity: Subscriber counts could be taken to mean there is still some interest in Apache Roller. The low email counts reflec the low level of development and user-support activity. - dev@roller.apache.org: - 151 subscribers (up 1 in the last 3 months): - 16 emails sent to list (30 in previous quarter) - user@roller.apache.org: - 273 subscribers (up 0 in the last 3 months): - 12 emails sent to list (5 in previous quarter) ## JIRA activity: - 7 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BD: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: - Library implementing XML Digital Signature Specification & XML Encryption Specification. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - There was one new release over the last quarter - Apache Santuario XML Security for Java 2.1.3. This was our first Java release in 9 months, and so it contained a number of bug fixes. ## Health report: - Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Daniel Kulp on Mon Oct 01 2018 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Daniel Kulp at Mon Oct 01 2018 ## Releases: - Apache Santuario - XML Security for Java 2.1.3 was released on Fri Mar 29 2019 ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BE: Report from the Apache Serf Project [Branko Čibej] Report from the Apache Serf Project [Branko Čibej] ## Description: The serf library is a high performance C-based HTTP client library built upon the Apache Portable Runtime (APR) library. Serf is the default client library of Apache Subversion, Apache OpenOffice and mod_pagespeed. ## Issues: Activity on the project seems to have come to a halt in the last 6 months. Since the last report, there were a couple discussions with users (mostly on the #serf IRC channel on Freenode). Otherwise, there was no significant increase in activity on the project. ## Activity: There has been no move towards getting Serf 1.4.0 released in the last six months. A release candidate for internal testing was produced, but never released. The last Serf release is now 2.5 years old. The only active user of Serf seems to be Apache Subversion. mod_pagespeed is still listed as incubating but doesn't even have a podling web site (either that, or the link on the incubator page is wrong). Some of the PMC members chatted informally (on IRC) about pushing forward the next release (1.4.0). ## Health report: The last commit in the public repository was made on 2nd November. ## PMC & Committer changes: Currently 13 PMC members and 13 committers. - No new committers added in the last 3 months. - Last new committer added in April 2017 (Evgeny Kotkov). - Last new PMC member added in September 2018 (Branko Čibej). ## Releases: Apache Serf 1.3.9 was released on Thu Sep 01 2016 ## Mailing list and Jira activity: The last message on the dev@ mailing list a week old. It's a follow-up from a discussion with a user on IRC who had trouble building our sources.. ----------------------------------------- Attachment BF: Report from the Apache ServiceComb Project [Willem Ning Jiang] ----------------------------------------- Attachment BG: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: Apache Spatial Information System (SIS) is a Java library for developing geospatial applications. SIS enables better representation of spatial objects for searching, archiving, or other relevant spatial needs. The base of the SIS library is modeled according international standards published jointly by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). ## Issues: In last report (February) we wrote that we have difficulty to make a release, because of lack of time. We wrote that we were hoping to work on a release in March, but it did not happened yet. More discussion in the health section below. ## Activity and health report: Exceptionally, I merge those two sections together for this report since they are closely related. Last release (0.8) was in November 2017. About 30,000 lines of code (ignoring comments) have been added since that release (~8600 in last 3 months). We rushed in the development of features required by a contract focused on better support of Earth Observation data such as JAXA's Global Change Observation Mission. Despite the rush, the quality of the code has not been compromised: Apache SIS still have a high comment/code ratio (1.16 : 1). An example of comment documenting algebraic transformations together with a link to OpenOffice document providing more details can be viewed at [1]. However this rush has been done at the sacrifice of community activity (messages on dev@sis.apache.org dropped to 3 emails in this quarter; we did not had the time to make proposals for GSoC this year; we may miss the geospatial track at ApacheCon this year for the first time; we did not wrote summary of latest Open Geospatial Consortium meetings), and at the sacrifice of preparing a release for more than one year. We reported those issues in February. In reaction, the board requested us to confirm by email that there is at least 3 PMC members providing active oversight of the project [2]. The call received responses from 4 PMC members, two of them being myself and a coworker. In the last report, we wrote that we may have time to work on SIS release in March. Unfortunately it did not happen, because of urgent work not yet finished. Work on the SIS release started only last week (May 1st), with one regression fixed [3]. I'm just starting to have weekends and holidays available for working on SIS release. The plan is to ensure that SIS compiles with Java 11 and to verify compliance of new features with OGC/ISO standards; the remaining would be delayed to a future release. A user already sent a pull request about the Java 11 compatibility issue [4] (disclaimer: he is a coworker). Apache Jena is starting to use SIS for GeoSPARQL support [5]. It is the second Apache project to my knowledge, after Apache Tika, to use SIS. ## PMC changes: * Currently 20 PMC members. * No new PMC members added in the last 3 months. * Last PMC addition was Johann Sorel on September 2017. ## Committer base changes: * Currently 21 committers. * No new committers added in the last 3 months. * Last committer addition was Johann Sorel on March 2016. The user who sent above-cited pull request [4] could be a candidate for new committer since he already provided other patches before. We are waiting for the next opportunity, when he will need to work again on SIS. ## Releases: * 0.8 was released on November 24, 2017. * Work on 1.0 release started May 1st, but can continue only during weekends for now. ## Mailing list activity: dev@sis.apache.org: * 69 subscribers (down -2 in the last 3 months) * 3 emails sent to list (8 in previous quarter) Those numbers are down compared to previous quarter, which were already down compared to the quarter before. user@sis.apache.org: * 47 subscribers (up 0 in the last 3 months) * 13 emails sent to list (0 in previous quarter) * Other discussions happened on GitHub issues like [5]. ## JIRA activity: * 9 JIRA tickets created in the last 3 months * 8 JIRA tickets closed/resolved in the last 3 months [1] https://github.com/apache/sis/blob/8ca9f9abb7d87f748e73d5fddb62eb056c98c7e6/core/sis-referencing/src/main/java/org/apache/sis/referencing/operation/projection/MeridianArcBased.java#L74 [2] https://lists.apache.org/thread.html/baeb067f9b0c71de0dfab4c326930046be20cf984a3ac37036d5e161@%3Cprivate.sis.apache.org%3E [3] https://issues.apache.org/jira/browse/SIS-402 [4] https://github.com/apache/sis/pull/16 [5] https://github.com/apache/jena/pull/557 ----------------------------------------- Attachment BH: Report from the Apache SkyWalking Project [Sheng Wu] ## Description: Apache Skywalking is an APM (application performance monitor), especially for microservice, Cloud Native and container-based architecture systems. Support observing and monitoring system from different sources, such as distributed tracing agents/SDKs, through Service Mesh telemetry data. ## Issues: there are no issues requiring board attention at this time. ## Activity: The community has just graduated from incubator last month. The community is working on a UI project(SkyWalking RocketBot) donation and IP Clearance. Release the 6.1 release, as the first release version as TLP. SkyWalking DevCon 2019 has been approved by PMC, will hold in 11th May, Shanghai, China. ## Health report: The project is health. We have over 10 contributors, commit over 5k lines of codes in last month. Mail lists are active. ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 23 committers. - Yuguang Zhao was added as a committer on Fri Apr 19 2019 ## Releases: Working on the first TLP release. ## Mailing list activity: The discussions have been made in the mail list. We have more people subscribe out dev mail list. - dev@skywalking.apache.org: - 60 subscribers (up 14 in the last 3 months): - 171 emails sent to list (168 in previous quarter) - notifications@skywalking.apache.org: - 11 subscribers (up 0 in the last 3 months): - 3398 emails sent to list (3811 in previous quarter) ----------------------------------------- Attachment BI: Report from the Apache Spark Project [Matei Alexandru Zaharia] Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python and R as well as a rich set of libraries including stream processing, machine learning, and graph analytics. Project status: - We released Apache Spark 2.4.1, 2.4.2, 2.4.3 and 2.3.3 in the past three months to fix issues in the 2.3 and 2.4 branches. - Discussions are under way about the next feature release, which will likely be Spark 3.0, on our dev and user mailing lists. Some key questions include whether to remove various deprecated APIs, and which minimum versions of Java, Python, Scala, etc to support. There are also a number of new features targeting this release. We encourage everyone in the community to give feedback on these discussions through our mailing lists or issue tracker. - Several Spark Project Improvement Proposals (SPIPs) for major additions to Spark were discussed on the dev list in the past three months. These include support for passing columnar data efficiently into external engines (e.g. GPU based libraries), accelerator-aware scheduling, new data source APIs, and .NET support. Some of these have been accepted (e.g. table metadata and accelerator aware scheduling proposals) while others are still being discussed. Trademarks: - We are continuing engagement with various organizations. Latest releases: - May 8th, 2018: Spark 2.4.3 - April 23rd, 2019: Spark 2.4.2 - March 31st, 2019: Spark 2.4.1 - Feb 15th, 2019: Spark 2.3.3 Committers and PMC: - The latest committer was added on Jan 29th, 2019 (Jose Torres). - The latest PMC member was added on Jan 12th, 2018 (Xiao Li). ----------------------------------------- Attachment BJ: Report from the Apache Subversion Project [Stefan Sperling] Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. Our user support forums (Email and IRC) receive questions and answers regularly. No new committers were added since the one reported in February. * Releases Subversion 1.12.0 was released on April 24 2019. This is a regular release which will receive 6 months of support. Subversion 1.11, the previous regular release, is no longer supported. Subversion 1.9 and 1.10 are our current long-term-support (LTS) releases and will receive support until August 2019 and April 2022, respectively. * Delayed patching of known security issues There are currently two pending private security issues, the one mentioned in the last report which was reported to us in August 2018, and a newer one which was reported to us in February 2019. In the past, there were usually enough volunteers willing to address security issues. A PMC member with commercial funding (Julian Foad) has recently been assigned some work time to address one or both of these. ----------------------------------------- Attachment BK: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: Apache Syncope is an Open Source system for managing digital identities in enterprise environments. ## Issues: There are no issues requiring board attention at this time. ## Activity: While maintenance for 2_0_X and 2_1_X branches is continuing (2.1.4 and 2.0.13 were released recently), we have finally started the work on the master branch around the new 3.0.0, with new components and features. ## Health report: Discussions about new features and improvements keep appearing and being followed up in dev@. Users keep asking for basic and advanced features and customizations in user@ and are eventually getting supported by the community. Someone is offering help on dev@ and was addressed to docs and tasks addressable as starting points, we'll see if anything concrete is going to happen. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Matteo Alessandroni on Fri Dec 22 2017 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Dima Ayash at Mon Jul 09 2018 ## Releases: - 2.0.13 was released on Fri Apr 19 2019 - 2.1.4 was released on Fri Apr 19 2019 ----------------------------------------- Attachment BL: Report from the Apache SystemML Project [Jon Deron Eriksson] ## Description: - SystemML provides declarative large-scale machine learning (ML) that aims at flexible specification of ML algorithms and automatic generation of hybrid runtime plans ranging from single node, in-memory computations, to distributed computations such as Apache Hadoop MapReduce and Apache Spark. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The latest release, 1.2.0, was approved on August 24th, 2018. - No new committers were added this quarter. ## Health report: - Code activity is healthy with 27 commits in the last 3 months. - Community growth is healthy with our last new committer approved in August. - Communication on the dev mailing list is significantly up. 126 emails were sent to the dev list this quarter. ## PMC changes: - Currently 23 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Arvind Surve on Tue May 16 2017 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Guobao Li at Tue Aug 28 2018 ## Releases: - Last release was 1.2.0, released on Fri Aug 24 2018 ## Mailing list activity: - We observed significantly higher email traffic to dev and issues. - dev@systemml.apache.org: - 109 subscribers (down -4 in the last 3 months): - 126 emails sent to list (6 in previous quarter) - issues@systemml.apache.org: - 14 subscribers (down -1 in the last 3 months): - 60 emails sent to list (23 in previous quarter) ## JIRA activity: - 20 JIRA tickets created in the last 3 months - 12 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BM: Report from the Apache TomEE Project [David Blevins] ## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The community did a concentrated push over the holidays to attract and get new contributors engaged. The most active window was mid November to February and in that time the project shattered every measurable record set in the near 20 years of project history. - highest contributors in a 3-month period: 43 (average was 8 in Oct/Nov) - highest spike in commits (previous 2012) - highest sustained volume (previous 2011) - highest dev list: 1326 messages (previous 520 in Sept 2007) Overall result is from mid November till now the project doubled in total contributors, from 32 to 83. Discussions in the PMC in adding some of them as committers are in progress now, including one vote. ## Activity Four major jumps and areas of focus have taken place in the last few months. The first has been to bring TomEE up from MicroProfile 1.2 support to MicroProfile 2.0 compliance. This work is complete and passing all MicroProfile 2.0 TCK tests. The second area has been a push to add more examples to the project, 26 new examples in total, 15 of those for MicroProfile specifications. The third focus was on the website itself, code that generates the site and basic documentation. The project had been maintaining one set of documentation applicable to all versions. We now have a Tomcat-like system with documentation root per version. The fourth area has been to translate the examples to other languages. 11 translated in total, 6 in Portuguese and 5 in Spanish. The result is the project has experienced a dramatic change, with many new contributors and work that can be done at all levels from any skillset. At this moment there are still 29 PRs in the queue and more showing up regularly. We are very thrilled and proud of everyone. It took 19 years to get 32 contributors and with a major focused effort by everyone simultaneously, we were able to smash 19 years of "new contributor" work in 3 months. It is difficult to sustain and contributions in the last 2 months are lower, but still far greater than the three month period before November. The lesson learned is there is a massive difference in outcome if one or two people push for years vs everyone pushing at once, even if briefly. We hope to do this again in December 2019 on the 20th anniversary of the project, with more committers able to help and hopefully smash some records again. Work on a TomEE 8.0.0-M3 release is in progress. The community would like to get that codebase to run cleanly on Java 11 and then go for a final TomEE 8.0.0 release. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added Roberto Cortez on Thu Sep 6 2018 ## Releases: - Apache TomEE 8.0.0-M2 on Jan 29, 2018 ----------------------------------------- Attachment BN: Report from the Apache Traffic Control Project [David Neuman] ## Description: - Apache Traffic Control can be used to build, monitor, configure, and provision a large-scale content delivery network (CDN). ## Issues: - There are no issues requiring board attention at this time ## Activity: - Released 3.0 and 3.0.1 - Added 2 new PMC members and 1 new committer - There was a lengthy debate in the community around API versioning, I think we have finally come to a consensus. - Spent time working on rounding up presentations for the Content Delivery Track at Apachecon NA ## Health report: - The project is healthy. We have had some challenges with mailing list discussions going on too long and some cases of comments getting personal on PRs. These have been addressed via face to face conversations. ## PMC changes: - Currently 15 PMC members. - New PMC members: - Derek Gelinas was added to the PMC on Sun Mar 17 2019 - Rawlin Peters was added to the PMC on Mon Feb 25 2019 ## Committer base changes: - Currently 22 committers. - Shihta Kuan was added as a committer on Mon Mar 25 2019 ## Releases: - apache-trafficcontrol-3.0.0 was released on Tue Mar 05 2019 - apache-trafficcontrol-3.0.1 was released on Tue Apr 16 2019 ## Mailing list activity: - users@trafficcontrol.apache.org: - 102 subscribers (down -2 in the last 3 months): - 11 emails sent to list (19 in previous quarter) - dev@trafficcontrol.apache.org: - 94 subscribers (up 0 in the last 3 months): - 196 emails sent to list (197 in previous quarter) ## Github Activity - 117 Pull requests submitted in the last quarter - 108 Pull Requests merged/closed in the last quarter - 112 issues created in quarter - 40 issues closed in the quarter ----------------------------------------- Attachment BO: Report from the Apache Turbine Project [Georg Kallidis] ## Description: - Apache Turbine is a servlet based framework that allows experienced Java developers to quickly build web applications. Turbine allows you to personalize the web sites and to use user logins to restrict access to parts of your application. - Turbine is a matured and well established framework that is used as the base of many other projects. ## Issues: - No board-level issues at this time. ## Activity: - Finalizing component upgrades/releases before Turbine 5.0 release and site updates - Migrated MoinWiki to Confluence ## Health report: - The Turbine project's quarter activity mainly referred to release / organizational / community collaboration issues in the dev mailing list and ongoing code changes across many components on low/medium level. - Turbine characterizes as a light-weight and robust, but not very easy to use framework, especially for newcomers. Providing a ready-to-use development environment is still highly desired and already in preparation. Yet, the upcoming main release and accompanying site updates will be of still higher demand. ## PMC changes: - Currently 9 PMC members. - Last PMC addition was Jeffery Painter on Sun Nov 12 2017. ## Committer base changes: - Currently 11 committers. - No new changes to the committer base since last report. - Last committer addition was more than 2 years ago. ## Releases: Turbine core project - No beta or final releases were made since the last board report. - Last main project release was Turbine 4.0.1 on Mon Mar 05 2018. Fulcrum component project - Fulcrum Security 1.1.3 was released on Thu Apr 11 2019 - Fulcrum Intake 2.0.0 was released on Mon Mar 25 2019 - Fulcrum Parser 2.0.0 was released on Mon Mar 18 2019 - Fulcrum Quartz 1.1.1 was released on Tue Feb 26 2019. ----------------------------------------- Attachment BP: Report from the Apache Twill Project [Terence Yim] Apache Twill is an abstraction over Apache Hadoop YARN to reduce the complexity of developing distributed applications. ## Issues: - The community is relatively quiet in the past couple months. - Need to start discussion among PMC on how to bring more activities to the project again. ## Activity: - None ## Health report: - Made one release since July 2018 ## PMC changes: - Currently 6 PMC members - Last PMC addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 9 committers and 25 contributors - No new committer added in the last 3 months - No new contributor added in the last 3 months - Last committer addition was Yuliya Feldman on Mar 6, 2018 - Last contributor addition was Hongyuan Li on Dec 12, 2018 ## Releases: - Last release was release 0.13.0 on July 17, 2018 ## Mailing list activity: - dev@twill.apache.org: - 67 subscribers - 1 emails sent to the list in past three months (17 in last report) - commits@twill.apache.org: - 16 subscribers - No emails sent to the list in past three months (4 in last report) ## JIRA activity: - 0 new JIRA tickets created in the last month - 0 JIRA tickets resolved in the last month ----------------------------------------- Attachment BQ: Report from the Apache Unomi Project [Serge Huber] ## Description: - Apache Unomi is a Java Open Source customer data platform, a Java server designed to manage customers, leads and visitors data and help personalize customer experiences while also offering features to respect visitor privacy rules (such as GDPR). It is also the reference implementation of an ongoing standard specification being developed at OASIS Open. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Removed all references to incubation in the source code - Work has restarted on improving the project now that the post-graduation work has completed - Hoping to release the next version (1.4.0) soon ## Health report: - We are seeing more initiative being taken from recent committers which is very encouraging. - Apache Unomi is getting some interesting press coverage (see https://www.cbronline.com/news/apache-unomi and https://www.cmswire.com/digital-experience/why-the-apache-unomi-open-source-customer-data-platform-is-worth-a-look/) ## PMC changes: - Currently 6 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 12 committers. - Taybou was added as a committer on Mon Apr 01 2019 ## Releases: - Last release was 1.3.0-incubating on Thu Aug 23 2018 ## Mailing list activity: - users@unomi.apache.org: - 20 subscribers (up 4 in the last 3 months): - 13 emails sent to list (50 in previous quarter) - dev@unomi.apache.org: - 30 subscribers (down -2 in the last 3 months): - 176 emails sent to list (271 in previous quarter) ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BR: Report from the Apache Usergrid Project [Michael Russo] ## Description: - Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database (Cassandra), a query engine (ElasticSearch), and application layer and client tier with SDKs for developers. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - CI setup with ASF Jenkins in progress. - Various Bugfixes around index querying and maintenance. - Improved test stability. - Experimentation with using newer versions(5.x) of Elasticsearch vs. supported older version (1.7). ## Health report: Growth has been flat over the past year or so. Some of the historical core contributors have not been active with the project recently. However, there is a new committer and additional interest for modernizing Usergrid -- upgrading Cassandra to the latest version and containerizing Usergrid. Getting the project to a healthier state will continue to be a focus. This includes more discussion on the mailing lists, better use of JIRA, and planning of a new release -- master branch is currently stable and contains many stability fixes over the last release in 2016. ## PMC changes: - Currently 25 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Dunker on Mon Jan 18 2016 ## Committer base changes: - Currently 28 committers. - New committers: - Keyur Karnik was added as a committer on Mon Mar 18 2019 ## Releases: - Last release was 2.1.0 on Wed Feb 17 2016 ## /dist/ errors: 1 - This is still outstanding, there is 1 unsigned package. We will either remove it or ensure it gets signed. ## Mailing list activity: - dev@usergrid.apache.org: - 104 subscribers (down -2 in the last 3 months): - 43 emails sent to list (38 in previous quarter) - user@usergrid.apache.org: - 144 subscribers (up 1 in the last 3 months): - 1 emails sent to list (0 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BS: Report from the Apache Velocity Project [Nathan Bubna] ## Description: - Java-based template engine ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Moderate. One developer actively adding features, fixing bugs, and proposing a possible major new sub-project and/or feature for VelocityTools. ## Health report: - Project is maintained and pushing forward, but the dev community is minimal. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Thu Jul 27 2017 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Mon Jan 30 2017 ## Releases: - velocity-engine-2.1 was released on Sat Mar 30 2019 ## Mailing list activity: - Mostly actual work by Claude and discussion thereof. - dev@velocity.apache.org: - 119 subscribers (down -1 in the last 3 months): - 106 emails sent to list (24 in previous quarter) - general@velocity.apache.org: - 72 subscribers (up 0 in the last 3 months): - 2 emails sent to list (2 in previous quarter) - user@velocity.apache.org: - 278 subscribers (down -6 in the last 3 months): - 6 emails sent to list (2 in previous quarter) ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BT: Report from the Apache Whimsy Project [Sam Ruby] ## Description: Tools that help automate various administrative tasks or information lookup activities ## Issues: None ## Health report: Sebb has clearly become the most active developer on the project. Shane has become more active. The times when this was mostly a one person project with occasional patches from others are long over. A number of individuals have expressed an interest in contributing, and have begun to do so. I am hopeful that there will be new committers in the next quarter or two. We continue to have more than adequate oversight, with two to three active committers, and a few occasional committers. ## Development: - Some new tools are being developed, mostly in branches. Nothing ready to be announced. - Numerous fixes. ## PMC and committer base: - Currently 10 committers, all on the PMC. - Last addition: Jun 2017 (John D. Ament) ----------------------------------------- Attachment BU: Report from the Apache Xalan Project [Gary D. Gregory] ## Description: - The Apache Xalan Project develops and maintains libraries and programs that transform XML documents using XSLT standard stylesheets. Our subprojects use the Java and C++ programing languages to implement the XSLT libraries. ## Issues: - The project does not need board attention at this time. ## Activity: - The project has rebooted its PMC. - We migrated from Subversion to GitBox. - The rebooted PMC is: * Bill Blough (billblough) * Roger Leigh (rleigh) * Mukul Gandhi (mukulg) * Gary D. Gregory (ggregory), Chair. * Michael Glavassevich (mrglavas) ## Health report: - The project has rebooted its PMC. Gary Gregory has taken over from Steven Hathaway as PMC Chair. Thank you Steven for your service these past few years! - We are looking forward to releasing 2.7.3 as a 'warm-up' to moving the project along again. - Discussions have started on what it would take to support XSLT 2 and 3. - There are a moderate amount of JIRA tickets that need attention since they include candidate patches. ## PMC changes: - Currently 5 PMC members. - New PMC members: - Bill Blough was added to the PMC on Tue Feb 19 2019 - Gary D. Gregory was added to the PMC on Tue Feb 19 2019 - Michael Glavassevich was added to the PMC on Tue Feb 19 2019 - Mukul Gandhi was added to the PMC on Tue Feb 19 2019 - Roger Leigh was added to the PMC on Tue Feb 19 2019 ## Committer base changes: - Currently 57 committers. - New commmitters: - Bill Blough was added as a committer on Wed Mar 20 2019 - Mukul Gandhi was added as a committer on Wed Mar 20 2019 - Roger Leigh was added as a committer on Wed Mar 20 2019 ## Releases: - No release data could be found [FIX!] ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months Gary Gregory, Apache Xalan PMC Chair. ----------------------------------------- Attachment BV: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J Xerces-J is considering migrating the source to Git, but no decision has been made yet. Other than a few updates to the documentation it's been otherwise quiet since March. Mailing list traffic has been low; roughly 20+ posts on the j-dev and j-users lists since the beginning of March 2019. No new releases since the previous report. The latest release is Xerces-J 2.12.0 (April 30th, 2018). Xerces-C The PMC / Xerces-C committers recently voted to migrate the source to Git. Follow-up discussion on the migration plan is currently happening on the c-dev mailing list. Mailing list traffic has been low; roughly 40+ posts on the c-dev and c-users lists since the beginning of March 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. One committer has committed changes to SVN since March 2019. ----------------------------------------- Attachment BW: Report from the Apache XML Graphics Project [Clay Leeds] Apache XML Graphics Project Board Report ================================== The Apache XML Graphics Project is responsible for software intended for the creation & maintenance of the conversion of XML formats to graphical output & related software components. ISSUES FOR THE BOARD ===================== No issues at present. ACTIVITY ======== * Apache Batik 1.11 * Apache FOP 2.3 * Apache XML Graphics Commons 2.3 PROJECT HEALTH REPORT ======================= The level of community and developer activity remains at a consistent, moderate, level with respect to the previous reporting period. RECENT PMC CHANGES ================== Currently 11 PMC members. * Simon Steiner was added to the PMC on Tue Jan 19 2016 * Clay Leeds was approved for XML Graphics PMC Chair position on March 26, 2018. Committers ========== Currently 21 committers. * No new committers added in the last 3 months * Last committer added was Matthias Reischenbacher at Wed May 13 2015 Most Recent Releases ==================== There were no releases in the last quarter. * Apache XML Graphics Commons 2.3 was released on Mon May 14, 2018 * Apache XML Graphics FOP 2.3 was released on Mon May 14, 2018 * Apache XML Graphics Apache Batik 1.11 was released on Wed Feb 13, 2019. = SUB PROJECTS = ================ XML GRAPHICS COMMONS ==================== Community activity was light, although there were a few bugs resolved. New Release? ------------ There were no releases this quarter. Latest Release -------------- XML Graphics Commons 2.3 was released on Mon May 14, 2018 FOP === A number of patches have been processed into TRUNK and several bugs fixed. New Release? ------------ * There were no releases this quarter. * Bug Fix for FOP 2.3 to remove Avalon committed to TRUNK (since Avalon is no longer maintained & doesn't compile under Java 9) Latest Release -------------- XML Graphics FOP 2.3 was released on Mon May 14, 2018 BATIK ===== Apache Batik 1.11 was released on Wed Feb 13, 2019. New Release? ------------ Apache Batik 1.11 was released on Wed Feb 13, 2019. Latest Release -------------- Apache Batik 1.11 was released on Wed Feb 13, 2019. ------------------------------------------------------ End of minutes for the May 15, 2019 board meeting.