The Apache Software Foundation Board of Directors Meeting Minutes March 20, 2019 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:30 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/3t0g 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 Bertrand Delacretaz Isabel Drost-Fromm Ted Dunning Brett Porter Roman Shaposhnik Phil Steitz Mark Thomas Directors Absent: none Executive Officers Present: Ross Gardler Tom Pappas Sam Ruby Craig L Russell Matt Sicker Executive Officers Absent: Daniel Ruggeri Ulrich Stärk Guests: Benoit Tellier Greg Stein Henri Yandell Jim Jagielski Myrle Krantz P. Taylor Goetz Sally Khudairi Serge Huber 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of February 20, 2019 See: board_minutes_2019_02_20.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Phil] This month, we will celebrate our 20th anniversary on the same date as the annual members meeting. We also published an important blog post this month [1], elucidating the core concepts underlying the Apache Way. This statement represents the collaborative work of quite a few ASF members and represents a big step forward in getting better clarity for ASF volunteers and others interested in understanding the Foundation. Many thanks to those who contributed and for the overall positive and productive discussion around the post. [1] https://s.apache.org/GhnI B. President [Sam] Items requiring board attention ------------------------------- Marketing & Publicity has a two proposals for substantial, one time investments in recognition of the ASF's 20th anniversary. If there aren't objections, these items will be included in the upcoming FY20 budget where they will receive final approval at that time. Financials ---------- Overall, we are continuing our pattern of under-running expenses and over-producing on income. The under-running will slow down a bit with the hiring of new system administrators. Our finances are in such good shape that I approved of the pulling forward of 75% down payment on ACEU19 (which was approved by the board last month) into this fiscal year. The net effect of this will be to reduce the amount by which we overachieved this year in terms of budget and will reduce the amount requested in the FY20 budget. Summary ------- All areas operating normally. * Brand management responding to queries, working with council on registration and privately with third parties on infringements. * Fundraising have established a division of labor for working with existing sponsors, outreach, and events. This is resulting in timely renewals, invoicing, and sponsor contacts. Notably, there are two new sponsors. * Marketing and Publicity in addition to the normal media contacts, M&P is completing development of promotional materials, and working closely with event planners. As mentioned previously, there is a proposal for the board to evaluate. * Infrastructure completed hiring of two new system administrators. Otherwise operating normally with the exception of a bit of downtime on our TLP servers which has been resolved. * Conferences now has 4 events in flight; each with a dedicated volunteer event chair overseeing the report. * Travel assistance no report posted as of yet; I've sent an email reminding Gavin of this responsibility, and will follow up before the next meeting. * Finance there was an uptick of activity with respect to filings, fundraising, events, and meeting with banks. Most notably, there was a conversation with a possible wealth management firm. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] Here is a summary of the Foundation’s Financial performance for the first ten months of FY19; Operating Cash on February 28, 2019 was $2,658.9K, which is up $59.7K from last month’s ending balance (Jan 19) of $2,599.2K. Total Cash as of Feb 28, 2019 is $4,052.8K ( includes the Pineapple and restricted Donation) as compared to $2,500.2K on Feb 28th 2018 (an increase of $1,552.6K year over year). The Feb 2019 ending Operating cash balance of $2,658.9K represents an Operating cash reserve of 20 months based on the FY19 conservative Cash forecast average monthly spending of $132.8K/month ( this will most change for FY 20, 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 20 months at the end of Feb 2019 is ahead of the budgeted 10.6 month reserve for YTD through Feb 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 Income is ahead of FY18 at this point in the Fiscal year by $501.7K . As compared to the FY19 Budgeted Income, YTD, we are ahead by $630.5K. YTD expenses, through Feb 28, 2019 are under budget by $382.1K. All depts. are under budget, at the end of Feb 2019. There are still a couple items worth mentioning, one being Infra, as noted in the Board summary is $227K under budget due to the timing of hiring of staff ( though this will change in Mar19 as they have hired two new staff members, Congrats) and not having to pay any Lease web invoices YTD. The other being TAC at $45K under budget YTD for FY19. The Expenses vs Budget will also change in Mar 19 as we just put a 75% down payment on ACEU19 of $229.6K as well. So with both of these for the Mar 19 close we will be closer to our FY19 Expense Budget. Regarding Net Income (NI), YTD FY19 the ASF finished with a positive $607.2K NI vs a budgeted negative <$405.4K> NI or $1,012.6K ahead of Budget, NI, for FY19 at this point in the Fiscal year. This is attributable to timing of some Sponsor payments as well as more Donations than were budgeted as well as underspending in all depts YTD, vs the FY19 Budget. At this point in the FY we are doing very well, ahead in Revenue and well under budget in Expenses, even taking timing variances into account. We will continue to monitor this as we finish out FY19. With regard to FY18, we are outpacing revenue, by $501.7K as noted above, but we are also out pacing expenses by $180.8K. However, year over year NI for FY19 exceeds FY18 by $320.9K, another good yard stick of the Foundation’s financial health at this point in time. Current Balances: Boston Private CDARS Account 2,250,000.00 Citizens Money Market 1,068,066.39 Citizens Checking 727,720.86 Paypal - ASF 7,011.37 Total Checking/Savings 4,052,798.62 Feb-19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 2,344.90 77,774.15 -75,429.25 Sponsorship Program 162,000.00 18,000.00 144,000.00 Programs Income 0.00 0.00 0.00 Conference/Event Income 2,000.00 0.00 2,000.00 Other Income 310.85 1,655.23 -1,344.38 Interest Income 466.38 974.45 -508.07 Total Income 167,122.13 98,403.83 68,718.30 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 47,454.80 78,128.36 -30,673.56 Programs Expense 0.00 0.00 0.00 Publicity 16,701.34 13,729.53 2,971.81 Brand Management 13,108.32 8,166.66 4,941.66 Conferences 7,623.35 10,000.00 -2,376.65 Travel Assistance Committee 0.00 0.00 0.00 Fundraising 8,560.50 17,333.32 -8,772.82 Treasury Services 3,350.00 5,825.00 -2,475.00 General & Administrative 2,938.01 2,117.69 820.32 Total Expense 99,736.32 135,300.56 -35,564.24 Net Income 67,385.81 -36,896.73 104,282.54 YTD FY19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 129,218.61 116,663.92 12,554.69 Sponsorship Program 1,383,371.47 839,000.00 544,371.47 Programs Income 17,200.00 14,400.00 2,800.00 Conference/Event Income 250,227.95 184,000.00 66,227.95 Other Income 29,868.52 18,191.18 11,677.34 Interest Income 5,416.22 12,590.87 -7,174.65 Total Income 1,815,302.77 1,184,845.97 630,456.80 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 582,263.03 809,283.28 -227,020.25 Programs Expense 0.00 4,400.00 -4,400.00 Publicity 194,322.95 205,090.92 -10,767.97 Brand Management 53,290.31 81,666.68 -28,376.37 Conferences 204,635.42 210,000.00 -5,364.58 Travel Assistance Committee 0.00 45,000.00 -45,000.00 Fundraising 122,513.77 173,333.36 -50,819.59 Treasury Services 36,135.00 39,250.00 -3,115.00 General & Administrative 14,901.53 22,179.85 -7,278.32 Total Expense 1,208,062.01 1,590,204.09 -382,142.08 Net Income 607,240.76 -405,358.12 1,012,598.88 D. Secretary [Craig] Internal procedures were updated for emeritus members who wish to be reinstated. External documentation of the process is pending. Several discrepancies in the records have been fixed (missing and duplicate ICLAs). In February, 56 ICLAs, three CCLAs, and one grant were received and filed. E. Executive Vice President [Ross] Infrastructure ============== Two new Sys Admins started on March 18th. Welcome to Drew Foulks and John Andrunas MoinMoin Wiki will be deprecated in favour of either Confluence or GitHub Wiki Assisting M&PR to stage the 20th Anniversary website design. Eclipse IDE caused a problem with a rapid rise in requests for a plugin that had been removed from dist.apache.org. This resulted in a large scale repeated fetch operations from across the globe. That had a knock on effect that led the team to revamp Blocky, our tool for automated ban/blocking. We are now better equipped to handle such events. Marketing and PR ================ Lots of work for the 20th Anniversary. The Quarterly Report for Q3 FY2019 is live at https://s.apache.org/nUxz Fundraising re-alignment of responsibilities continues to bring results. Conferences =========== 4 events "in flight" so the team are very busy. Of note is that we have a lengthy report with contributions from each of the event leads. This is very encouraging to see. Real teamwork but also with real leadership to keep things moving. Rich appears to finally have reached his goal - congrats to all. ApacheCon North America 2019 - CFP is open. There are a number of community led tracks (details in full report). ApacheCon Europe 2019 progressing well. DC Roadshow - in the black financially. Focus is on attracting attendees at this time. Chicago Roadshow is putting the schedule together. Travel Assistance Committee =========================== No report at time of writing. What I know is... Accepted sponsorship to assist attendance for specific minority groups. This is being administered within the existing process. Ramping up to run TAC for the multiple events on the horizon. F. Vice Chairman [Shane] Not much to report other than some Whimsy and documentation work trying to make our annual Member's meetings even easier to understand, attend, and manage. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Isabel] See Attachment 8 B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Shane] See Attachment 10 D. VP of Data Privacy [Chris Mattmann / Rich] No report was submitted. @Phil pursue a report for Data Privacy Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Hama [rb] # Incubator [ps] # Stanbol [rs] # Storm [rs] A. Apache Airflow Project [Bolke de Bruin / Brett] See Attachment A B. Apache Allura Project [David Philip Brondsema / Bertrand] See Attachment B C. Apache Any23 Project [Lewis John McGibbney / Phil] See Attachment C D. Apache Archiva Project [Olivier Lamy / Mark] No report was submitted. E. Apache Atlas Project [Madhan Neethiraj / Ted] See Attachment E F. Apache Aurora Project [Jake Farrell / Roman] See Attachment F G. Apache Axis Project [Robert Lazarski / Mark] See Attachment G H. Apache Bahir Project [Luciano Resende / Phil] No report was submitted. @Phil: pursue a report for Bahir I. Apache Beam Project [Kenneth Knowles / Shane] See Attachment I J. Apache Bigtop Project [Youngwoo Kim / Roman] See Attachment J K. Apache Bloodhound Project [Gary Martin / Rich] See Attachment K L. Apache BVal Project [Matthew Jason Benson / Isabel] See Attachment L M. Apache Camel Project [Andrea Cosentino / Brett] See Attachment M N. Apache Cayenne Project [Michael Ray Gentry / Bertrand] See Attachment N O. Apache Chemistry Project [Florian Müller / Ted] See Attachment O P. Apache CloudStack Project [Mike Tutkowski / Bertrand] See Attachment P Q. Apache Commons Project [Gary D. Gregory / Phil] See Attachment Q R. Apache Cordova Project [Jesse MacFadyen / Mark] See Attachment R S. Apache cTAKES Project [Pei Chen / Roman] See Attachment S T. Apache Curator Project [Jordan Zimmerman / Isabel] See Attachment T U. Apache Eagle Project [Edward Zhang / Shane] See Attachment U V. Apache Falcon Project [Pallavi Rao / Brett] See Attachment V W. Apache Felix Project [Karl Pauls / Rich] See Attachment W X. Apache Flex Project [Olaf Krüger / Ted] See Attachment X Y. Apache Flink Project [Stephan Ewen / Brett] See Attachment Y Z. Apache Guacamole Project [Mike Jumper / Mark] See Attachment Z AA. Apache Gump Project [Stefan Bodewig / Ted] See Attachment AA AB. Apache Hama Project [Chia-Hung Lin / Roman] See Attachment AB @Shane: write up a proposal for PMC to show that they are exercising oversight AC. Apache Helix Project [Kishore G / Isabel] See Attachment AC AD. Apache Hive Project [Ashutosh Chauhan / Bertrand] See Attachment AD AE. Apache Incubator Project [Justin Mclean / Shane] See Attachment AE AF. Apache Jackrabbit Project [Michael Dürig / Rich] See Attachment AF AG. Apache Joshua Project [Tommaso Teofili / Phil] No report was submitted. @Phil: pursue a report for Joshua AH. Apache Karaf Project [Jean-Baptiste Onofré / Mark] See Attachment AH AI. Apache Kylin Project [Luke Han / Phil] See Attachment AI AJ. Apache Labs Project [Danny Angus / Brett] See Attachment AJ AK. Apache Lucene Project [Cassandra Targett / Isabel] See Attachment AK AL. Apache Lucene.Net Project [Shad Storhaug / Ted] See Attachment AL AM. Apache Mesos Project [Benjamin Hindman / Shane] See Attachment AM AN. Apache Mnemonic Project [Gang Wang / Rich] See Attachment AN AO. Apache Mynewt Project [Justin Mclean / Roman] See Attachment AO AP. Apache OFBiz Project [Jacopo Cappellato / Bertrand] See Attachment AP AQ. Apache Olingo Project [Michael Bolz / Rich] See Attachment AQ AR. Apache OODT Project [Imesha Sudasingha / Bertrand] See Attachment AR AS. Apache OpenNLP Project [Jörn Kottmann / Isabel] See Attachment AS AT. Apache OpenWebBeans Project [Mark Struberg / Mark] See Attachment AT AU. Apache Perl Project [Philippe Chiasson / Ted] No report was submitted. AV. Apache Pig Project [Koji Noguchi / Brett] See Attachment AV AW. Apache Pivot Project [Roger Lee Whitcomb / Shane] See Attachment AW AX. Apache Portable Runtime (APR) Project [Nick Kew / Phil] See Attachment AX AY. Apache Portals Project [David Sean Taylor / Roman] See Attachment AY AZ. Apache PredictionIO Project [Donald Szeto / Ted] See Attachment AZ BA. Apache Pulsar Project [Matteo Merli / Brett] See Attachment BA BB. Apache River Project [Peter Firmstone / Phil] See Attachment BB BC. Apache RocketMQ Project [Xiaorui Wang / Mark] See Attachment BC BD. Apache Royale Project [Harbs / Isabel] See Attachment BD BE. Apache Sentry Project [Alex Kolbasov / Shane] See Attachment BE BF. Apache ServiceMix Project [Krzysztof Sobkowiak / Bertrand] See Attachment BF BG. Apache Shiro Project [Les Hazlewood / Roman] See Attachment BG BH. Apache Sling Project [Robert Munteanu / Rich] See Attachment BH BI. Apache SpamAssassin Project [Sidney Markowitz / Bertrand] See Attachment BI BJ. Apache Stanbol Project [Fabian Christ / Phil] No report was submitted. BK. Apache Storm Project [P. Taylor Goetz / Mark] See Attachment BK BL. Apache Synapse Project [Isuru Udana / Roman] See Attachment BL BM. Apache Tajo Project [Hyunsik Choi / Shane] See Attachment BM BN. Apache Tomcat Project [Mladen Turk / Isabel] See Attachment BN BO. Apache Trafodion Project [Pierre Smits / Ted] See Attachment BO BP. Apache Twill Project [Terence Yim / Brett] No report was submitted. BQ. Apache UIMA Project [Marshall Schor / Rich] See Attachment BQ BR. Apache Unomi Project [Serge Huber / Rich] See Attachment BR BS. Apache VCL Project [Josh Thompson / Phil] See Attachment BS BT. Apache Wicket Project [Andrea Del Bene / Roman] See Attachment BT BU. Apache Xalan Project [Steven J. Hathaway / Shane] No report was submitted. @Roman: pursue a report for Xalan BV. Apache Xerces Project [Michael Glavassevich / Brett] See Attachment BV BW. Apache Yetus Project [Allen Wittenauer / Mark] See Attachment BW BX. Apache ZooKeeper Project [Flavio Paiva Junqueira / Ted] See Attachment BX Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache REEF Project Chair WHEREAS, the Board of Directors heretofore appointed Byung-Gon Chun (bgchun) to the office of Vice President, Apache REEF, and WHEREAS, the Board of Directors is in receipt of the resignation of Byung-Gon Chun from the office of Vice President, Apache REEF, and WHEREAS, the Project Management Committee of the Apache REEF project has chosen by vote to recommend Sergiy Matusevych (motus) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Byung-Gon Chun is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache REEF, and BE IT FURTHER RESOLVED, that Sergiy Matusevych be and hereby is appointed to the office of Vice President, Apache REEF, 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. The vote result can be found at https://s.apache.org/c9qL. Special Order 7A, Change the Apache REEF Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Flume Project Chair WHEREAS, the Board of Directors heretofore appointed Mike Percy (mpercy) to the office of Vice President, Apache Flume, and WHEREAS, the Board of Directors is in receipt of the resignation of Mike Percy from the office of Vice President, Apache Flume, and WHEREAS, the Project Management Committee of the Apache Flume project has chosen by vote to recommend Ferenc Szabo (szaboferee) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Mike Percy is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Flume, and BE IT FURTHER RESOLVED, that Ferenc Szabo be and hereby is appointed to the office of Vice President, Apache Flume, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. The PMC discuss thread can be found at https://s.apache.org/Dvvf Special Order 7B, Change the Apache Flume Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache CloudStack Project Chair WHEREAS, the Board of Directors heretofore appointed Mike Tutkowski (mtutkowski) to the office of Vice President, Apache CloudStack, and WHEREAS, the Board of Directors is in receipt of the resignation of Mike Tutkowski from the office of Vice President, Apache CloudStack, and WHEREAS, the Project Management Committee of the Apache CloudStack project has chosen by vote to recommend Paul Angus (paul_a) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Mike Tutkowski is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache CloudStack, and BE IT FURTHER RESOLVED, that Paul Angus be and hereby is appointed to the office of Vice President, Apache CloudStack, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7C, Change the Apache CloudStack Project Chair, was approved by Unanimous Vote of the directors present. D. Change the Apache Royale Project Chair WHEREAS, the Board of Directors heretofore appointed Harbs (harbs) to the office of Vice President, Apache Royale, and WHEREAS, the Board of Directors is in receipt of the resignation of Harbs from the office of Vice President, Apache Royale, and WHEREAS, the Project Management Committee of the Apache Royale project has chosen by vote to recommend Piotr Zarzycki (piotrz) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Harbs is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Royale, and BE IT FURTHER RESOLVED, that Piotr Zarzycki be and hereby is appointed to the office of Vice President, Apache Royale, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache Royale Project Chair, was approved by Unanimous Vote of the directors present. E. Change the Apache Sentry Project Chair WHEREAS, the Board of Directors heretofore appointed Alex Kolbasov (akolb) to the office of Vice President, Apache Sentry, and WHEREAS, the Board of Directors is in receipt of the resignation of Alex Kolbasov from the office of Vice President, Apache Sentry, and WHEREAS, the Project Management Committee of the Apache Sentry project has chosen by vote to recommend Kalyan Kalvagadda (kalyan) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Alex Kolbasov is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Sentry, and BE IT FURTHER RESOLVED, that Kalyan Kalvagadda be and hereby is appointed to the office of Vice President, Apache Sentry, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Change the Apache Sentry Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * Roman: is this project still viable? [ Stanbol 2018-09-19 ] Status: * Roman: help the project with their request to add new pmc/committers [ Xalan 2018-09-19 ] Status: * Isabel: follow up -- are there enough PMC members? [ Hama 2019-01-16 ] Status: * Phil: reach out to PPMC to see about improving the governance of the project. [ Incubator 2019-01-16 ] Status: Ongoing * Rich: follow up regarding communications with security team [ Isis 2019-01-16 ] Status: Complete: I am unable to figure out what this action item is about. The ISIS report from that month does not mention security, nor does the security report mention ISIS. * Isabel: pursue a report for Thrift [ Thrift 2019-01-16 ] Status: * Phil: discuss on board-chat exact process involving email to secretary@ to [ Process for restoring emeritus members 2019-01-16 ] Status: Complete * Phil: pursue a report for Hama [ Hama 2019-02-20 ] Status: Complete (report was submitted) * Ted: pursue a report or new chair for Kylin [ Kylin 2019-02-20 ] Status: Complete * Roman: ping community about activity [ Marmotta 2019-02-20 ] Status: * Isabel: pursue a report for Mesos [ Mesos 2019-02-20 ] Status: Complete * Phil: pursue a report for River [ River 2019-02-20 ] Status: Complete * Shane: pursue a report for RocketMQ [ RocketMQ 2019-02-20 ] Status: Done: report submitted. * Rich: follow up with web issue for mod_pagespeed [ Serf 2019-02-20 ] Status: The PPMC responded that they plan to redirect pagespeed.incubator.apache.org to modpagespeed.com, which also does not seem like the right thing to do. I have encouraged them to consult with their mentors, and I'll check back on this in a few weeks. Update: http://pagespeed.incubator.apache.org/ continues to be 404 as of March 14th. Discussion on the pagespeed mlist indicates that someone is going to work on this. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 11:46 a.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] * ISSUES FOR THE BOARD None. * OPERATIONS Covering the period February 2019 Responded to the following queries, liaising with projects as required: - Provided advice on the process to transfer the HUDI mark - Agreed a way forward for DRUID with the podling. We will continue to seek a coexistence agreement but it won't block graduation - Use of project logos to represent projects - Approved 3 podling name (ICEBERG, FLAGON, ALEMBIC) - Declined 1 podling name (RAINBOW) - Approved use of project logo on stickers - Provided advice to GROOVY on draft crowdfunding page - Provided advice to the ZIPKIN podling on naming referring to other brands * REGISTRATIONS In line with the approach agreed with the Apache OpenOffice project, directed counsel to allow our OPENOFFICE.ORG registrations to lapse in Taiwan, Norway and South Korea. Worked with counsel to progress our APACHE registration. Worked with counsel to progress our IGNITE registration. Working with counsel and IBM to transfer OPENWHISK marks. Working with counsel and Huawei to transfer SERVICECOMB marks. * INFRINGEMENTS ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] Fundraising is doing well with timely renewals, invoicing and sponsor contacts. Our Sponsor Ambassadors have completed outreach/check-in with ASF Sponsors and Targeted Sponsors. Big thanks to our Sponsor Ambassadors for their effort. We are also in the process of welcoming two new sponsors and are happy to report this month that more than $500 USD has been donated by individual donors. We also continue working with Platinum and Gold sponsors for promotional opportunities. Three Platinum sponsors have recently taken advantage of the benefit and we will soon be releasing a Sponsor case study. We're also working with sponsors for our 20th Anniversary. Work with ASF events has continued picking up. We've partnered with the Conferences team to help finalize event prospectuses for Apache Roadshow Chicago, ApacheCon NA Las Vegas and ApacheCon EU Berlin. Sponsorship support for the events is going well. We are also engaged with the event producers to establish processes. We continue our ongoing records maintenance and accounts reconciliation on the backend of our processes and published our FY2019 Q3 report. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity - March 2019 I. Budget: we remain on budget and on schedule. We are exploring additional promotional opportunities possible for the ASF 20th Anniversary, and will be submitting an addendum to our proposed budget for FY2020. II. Cross-committee Liaison: Sally Khudairi continues to work closely with VP Fundraising Daniel Rugger in restructuring ASF Fundraising. She continues to secure sponsorship renewals and is working with Virtual to ensure timely invoicing. We have signed a new Platinum Targeted Sponsor who will be announced later this month, and has been following up on numerous incoming sponsorship queries. The newly-established Central Services sub-group of ASF Marketing & Publicity has kicked off with three creative projects, namely the site refresh of apache.org, creating logo assets for the ASF's upcoming 20th Anniversary, and launching supporting graphics for Apache Conferences. Sally has been working closely with ASF Conferences across planning, sponsorships, marketing, and related tactics, and has successfully completed content and creative direction on the prospectuses for the upcoming Apache Roadshow/Chicago, ApacheCon/Las Vegas, and ApacheCon/Berlin, as well as launched a digital ad campaign for the Apache Roadshow/DC. The latest "Success at Apache" post, "Growing with the ASF", was published at https://s.apache.org/NoXH . The Quarterly Report for Q3 FY2019 is live at https://s.apache.org/nUxz . We are finalizing the next ASF Sponsor case study (offered exclusively to Gold and Platinum sponsors), which will be published in the coming days. Promotional planning and tactics continue for the upcoming ASF 20th Anniversary, which will be formally rolling out on 26 March and continue through the calendar year. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 4 March - MEDIA ALERT: The Apache Software Foundation to present on Apache software projects in government, cybersecurity, and more at Roadshow and Open Source Job Fair at George Mason University - 19 February - The Apache® Software Foundation Announces Apache Arrow™ Momentum IV. Informal Announcements: 7 items were published on the ASF "Foundation" Blog. 4 Apache News Round-ups were issued, with a total of 242 weekly summaries published to date. We tweeted 31 items to 52.1K followers on Twitter. We posted 11 items on LinkedIn, which garnered more than 38.2K organic impressions. V. Future Announcements: 3 announcements are 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 3 media queries, and are working on several placed articles by invitation. The ASF received 1,235 press clips vs. last month's clip count of 1,053. Media coverage of Apache projects yielded 2,461 press hits vs. last month's 2,062. ApacheCon received 120 press hits. We continue to work with several corporates that are involved with several Apache projects on externally-focused communications and publicity. VII. Analyst Relations: we received one analyst queries during this time. Apache was mentioned in 11 reports by Gartner; 2 reports by Forrester; 2 reports by 451 Research; and 6 reports by IDC. VIII. Graphics: we are completing development of promotional materials, assets, and Website refresh for the ASF's 20th Anniversary. Members of the new Central Services sub-group of ASF Marketing & Publicity have been collaborating successfully on the apache.org refresh, reviewing, judging, and optimizing the selected entry for the 20th Anniversary logo, and developing digital assets for Apache events. We plan to expand this group to include possible outside contributors and will be working on a strategy to promote involvement with new communities. IX. Events liaison: we continue to work closely with Virtual regarding the Apache Roadshow/Chicago and ApacheCon/Las Vegas, as well as preparing ApacheCon/Berlin for initial publicity. In addition, we are working with ASF Conferences and ComDev on new opportunities to promote Apache projects and exploring opportunities for ApacheCon in 2020. X. Newswire accounts: we have renewed our pre-paid press release contract with GlobeNewswire, which will run through December 2020. # # # ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected, and has no current issues to bring to the attention of the President or the Board. Hiring ====== We completed our hiring process, and brought aboard two new system administrators: Drew Foulks and John Andrunas. They started the week of March 18, 2019. Short Term Priorities ===================== - Onboard the new employees. - Deprecation of the MoinMoin wiki, and the associated moves of projects over to Confluence or the GitHub wiki system. - Evaluate hosted solutions for Reviewboard and Sonarqube. Long Range Priorities ===================== - Complete puppetization and migration off the old hardware, then begin a mass migration to Ubuntu 18.04 LTS, and Puppet v6. General Activity ================ - Upgraded Confluence, and its various plugins. We have now configured Confluence to use standard/simplified Apache LDAP sign-in, while retaining the ability for the public to create accounts and contribute to wiki pages. - Working with M&PR to stage a new website design. - Our automated ban/blocking system called "Blocky" was completely revamped, as a result of the Eclipse fallout (described below). The new Blocky better handles bans, limited-time bans, whitelists, and limited-time whitelists. The user interface has been rebuilt to simplify the discovery, ban repeal, manual ban/whitelist, and other functions. - Jira plugins were upgraded. - Our install of Crowd (an SSO solution for Atlassian products) has been upgraded, and we're rolling it out across our ecosystem. Uptime Statistics ================= We experienced some downtime on our TLP servers due to a bug in the Eclipse IDE plugin loading system. The Apache Geronimo project removed an obsolete plugin (that was erroneously hosted or referenced to our dist.apache.org server), and Eclipse did not recognize the 404 response from our server. Eclipse retried endlessly/immediately. This appeared to coincide with some Eclipse-related event, as the removal occurred long ago. Whatever instigated the fetch from our servers, it ramped up quickly and arrived from thousands of source addresses all around the planet. The team worked on various remediation efforts and blocks, but the final answer was to simply reinstate a file that Eclipse could retrieve. This stopped the traffic load, and our systems have returned to normal. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] Overall, things seem to be going well. We have 4 events "in flight" right now, so it's a lot to keep track of. I'm very grateful for the independence and self motivation of each of the event chairs, so that I haven't had to do much for those other events. Each event chair will provide a sub-report below. ## ApacheCon North America 2019 The Call for Presentations is now open, and registration should be open in time for the DC Roadshow and the 20th anniversary announcements. ### CCC The Cloudstack Collaboration Conference has launched their own website, at http://us.cloudstackcollab.org/ to promote their event. We anticipate that several of the other tracks/summits will do the same in the coming weeks. ### ACNA-IoT Track We haven't emailed specific projects bc I thought there was an all-user all-dev blast going out soon and didn't want to back-to-back spam, however I have seen one-off announcements going out from other tracks so please let me know. ### Integration track The Integration track of ApacheCon NA is scheduled for Thursday 12th of September in the Laughlin 1 room with the capacity of 100 persons. Zoran Regvart is the chair of the track. He engaged his colleagues at Red Hat to submit talks and sent an e-mail to dev@ ActiveMQ, Airflow, Arrow, Beam, CXF, Falcon, Flume, Ignite, Kafka, Karaf, Lens, MetaModel, NiFi, Pulser, RocketMQ, Spark and Storm projects highlighting the Integration track and encouraging submissions. Additional invitation was extended to Camel dev@ and users@ with the offer to help with topics and submissions. ## ApacheCon Europe 2019 Myrle: ApacheCon Berlin is humming along. Sharan got our website up, we've finalized the sponsor prospectus, and gotten the registration system up and running. Once the prospectus was finalized, Sally needed only 90 minutes to sell the first Platinum sponsorship. The first ticket sale (with a 40 euro donation to the ASF!) was also quite fast. The first pubic announcement for ApacheCon Berlin has gone out on the coattails of the DC Roadshow. We are coordinating with ApacheCon Las Vegas as tightly as possible including on sponsorship prices and on keynote speakers. Paul of NewThinking and Myrle have a weekly meeting for Monday morning (CET) where we will coordinate whatever comes up. And Sharan, as the event sponsor ambassador has been coordinating with Nina of NewThinking as well. Still on our todo list: get the CfP system up, get an announcement out that focuses on Berlin, get our keynotes lined up, coordinate with TAC, and get more track chairs on board. ## DC Roadshow KAM: The DC Roadshow is going well. We are in the black financially. The biggest concern is putting butts in seats. Lots of work is ongoing to do that. Otherwise, I expect the event to be a big success and look forward to repeating it. ## Chicago Roadshow Trevor: CFP is Closed- except for "Apache in Adtech" and "Apache in Startups" track, still waiting on a few proposals to fill those out. I've created a gdoc on which-track-which-day. Next step is to email selected talks (a correctly filled out abstract was selected, but they all look good except one maybe-questionable-maybe-just-a-bad-abstract). After all of that, will post schedule and start promoting the event. So far we've sold 4 tickets. Will be updating website soon wrt GCP sponsorship (once I get green light that its been signed?). ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] ----------------------------------------- Attachment 7: Report from the VP of Finance [Tom Pappas] VP Finance activities for Feb 2019: 1) Coordinated and made sure submission of the ASF 990 and Annual report were filed on time to meet the March 2019 deadlines 2) Worked closely with Fundraising with regards to the DC Roadshow (procuring Insurance for the event), Chicago Road show (working on event insurance) and ACNA19 3) Participated in a phone call with the Event organizer's for ACEU19 to help coordinate finances 4) Met with a bank that also participates in the CDARs program that has better rates than the current CDARs bank Boston Private offers, exploring possible move due to better rates 5) Had further conversations with possible Wealth management firm, to address ASF cash position ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- 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 a good care of resolving most of these in time. (we're down 4, from 28 to 24, open issues this month). Kudos to Hen for leading a few cleanup/clarifications efforts, most notably in private/foundation/legal SVN and web properties of legal committee available under https://www.apache.org/legal Also, Hen contributed quite a bit to the 5 year plan with details available at: https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-422 Discussions around evolving our binary release policies continued on legal-discuss and general@incubator with several data points for a potential proposal emerging, but with no clear indication for how and when the process will converge. This may require a board level feedback on how important it is for us to spend significant resources on pursuing this. Discussion around clarifying the scope and purpose of legal mailing lists and also creating a privileged mailing list re-surfaced again. This time we have much more consensus at least around how to proceed with privileged one. We finalizing publishing of our IRS filings for the 2016/2017 as per request of Martin Michlmayr. It is now available under: https://www.apache.org/foundation/records/ ----------------------------------------- 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 up to 2 weeks to update the CVE database. Stats for February 2019: 8 [license confusion] 21 [support request/question not security notification] Security reports: 35 (last months: 38, 16, 34) 3 [httpd], [incubator/superset] 2 [activemq], [airflow], [hadoop], [openoffice], [site], [thrift] 1 [archiva], [commons], [cordova], [groovy], [hbase], [hc], [incubator/ponymail], [infrastructure], [jspwiki], [mesos], [nifi], [roller], [storm], [struts], [subversion], [tomcat], [zookeeper] In total, as of 1st March 2019, we're tracking 85 (last month: 78) open issues across 43 projects, median age 77 (last month: 75) days. 61 of those issues have CVE names assigned. 7 (last month: 8) of these issues, across 6 projects, are older than 365 days. ----------------------------------------- Attachment 11: Report from the VP of Data Privacy [Chris Mattmann] ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: - Apache Airflow (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows. When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative. Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed. ## Issues: - there are no issues requiring board attention at this time ## Activity: - New committer added: Xiaodong Deng - Healthy discussions on the mailinglist around DAG serialization ## Health report: - We have grown from 712 to 743 contributors since our last report. We do monitor for potential committers, but we also see a lot of "hit and run" contributors that particularly add to the 'periphery' of our code. - Since latest release 1058 commits have been made ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 19 committers. - Xiaodong Deng was added as a committer on Sat Mar 09 2019 ## Releases: - 1.10.2 was released on Tue Jan 22 2019 ## Mailing list activity: - dev@airflow.apache.org: - 578 subscribers (up 0 in the last 3 months): - 665 emails sent to list (757 in previous quarter) ## JIRA activity: - 578 JIRA tickets created in the last 3 months - 420 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment B: Report from the Apache Allura Project [David Philip Brondsema] ## Description: Apache Allura is an open source implementation of a software forge, a web site that manages source code repositories, bug reports, discussions, wiki pages, blogs, and more for any number of individual projects. ## Issues: - No issues needing board attention. ## Activity: - Several students interested in Google Summer of Code are getting involved and making some contributions - Various improvements and fixes continue - Some discussions on our list & tickets. ## Health report: - GSoC is already providing more activity, and hopefully can produce some long-term contributions - Otherwise slow but steady ## PMC changes: → Jim Jagielski resigned (he hadn't been active since podling mentorship time) → Last PMC addition: Sun Oct 28 2018 (Shalitha Suranga) → Currently 15 PMC members. ## Committer base changes: → Last committer addition: Mon Oct 29 2018 (Shalitha Suranga) → Currently 15 committers. ## Releases: → Last release was 1.10.0 on Mon Oct 29 2018 ----------------------------------------- Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (Any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity has been good. The project received good community review and an uptake in activity which resulted in the recent 2.3 release. ## Health report: Any23 continues to operate as a small but healthy project with stable development. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Hans Brende on Sun Feb 25 2018 ## Committer base changes: - Currently 15 committers. - No new committers added in the last 3 months - Last committer addition was Hans Brende at Wed Feb 21 2018 ## Releases: - 2.3 was released on Sun Mar 03 2019 ## Mailing list activity: Not much shift in the typical mailing list statistics. - dev@any23.apache.org: - 37 subscribers (up 0 in the last 3 months): - 86 emails sent to list (400 in previous quarter) - user@any23.apache.org: - 49 subscribers (down -1 in the last 3 months): - 6 emails sent to list (1 in previous quarter) ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 8 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment D: Report from the Apache Archiva Project [Olivier Lamy] ----------------------------------------- Attachment E: Report from the Apache Atlas Project [Madhan Neethiraj] ## Description: Apache Atlas is a scalable and extensible set of core foundational governance services that enables enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the complete enterprise data ecosystem ## Issues: There are no issues requiring board attention at this time. ## Activity: - significant updates to lineage UI - faster rendering, searchability, option to hide entities, highlight selected entity path, .. - added option to ignore/prune metadata for temporary/staging Hive tables - support for custom icons per entity-type - significant performance improvements during create/update of entities - added support for notifications on relationship changes - model updates to remove use of ownedRef/inverseRef constraints - enhancements to enable Atlas to be a reference implementation for Egeria - working on 2.0.0 release, to support Hadoop 3, HBase 2, Solr 7, Kafka 2, Hive 3 ## Health report: - 5 new contributors added in last 3 months: Aadarsh, Binit, Le Ma, Sridhar K, Sridhar S ## PMC changes: - Currently 33 PMC members - No new PMC members added in last 3 months - Last PMC member addition was on 6/21/2017 ## Committer base changes: - Currently 38 committers - No new committers added in last 3 months - Last addition to committer role was on 10/15/2018 ## Releases: 2.0.0 plan to release by 03/31/2019 0.8.3 was released on 10/31/2018 1.1.0 was released on 09/17/2018 1.0.0 was released on 06/02/2018 0.8.2 was released on 02/05/2018 1.0.0-alpha was released on 01/25/2018 0.8.1 was released on 08/29/2017 0.8-incubating was released on 03/16/2017 0.7.1-incubating was released on 01/26/2017 0.7-incubating was released on 07/09/2016 0.6-incubating was released on 12/31/2015 0.5-incubating was released on 07/11/2015 Responses to questions on earlier report: - 2018-12-19, 2018-09-19: clarification on what a contributor role is. A contributors has ability to assign JIRAs and attach patches. They don't have the ability to commit patches. Atlas PMC reviews contributors engagement with the project periodically and offer committer role to folks with sustained contributions over a period of time. - 2018-06-20, 2018-03-21: on contributor->committer pipeline. As stated above, Atlas PMC offers committer role to folks with sustained contributions over a period of time. Recently Ramesh Mani was offered committer role on 10/15/2018. PMC will continue to monitor the contributions and offer committer role. ----------------------------------------- Attachment F: Report from the Apache Aurora Project [Jake Farrell] ## Description: Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks. ## Issues The project might be heading towards the Apache Attic in the future, unless the community interest increases again. We will need advice on when and how we should make this transition. ## Health report The Apache Aurora project has seen a significant slowdown of user and contributor activity over the most recent months. This can partially be attributed to the overall stability and maturity of the project, but more importantly this is due to other external projects that managed to win the developer mindshare within the container orchestration field (e.g., general purpose cloud providers, Kubernetes, ...). ## PMC changes: - Currently 21 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jordan Ly on Wed May 02 2018 ## Committer base changes: - Currently 22 committers. - No new committers added in the last 3 months - Last committer addition was Renan DelValle at Fri Jan 26 2018 Issue backlog status since last report: * 0 JIRA tickets created in the last 3 months * 0 JIRA tickets closed/resolved in the last 3 months Mailing list activity since last report: * @dev 9 messages (127 in previous quarter) * @user 2 messages (13 in previous quarter) * @reviews 22 messages (181 in previous quarter) * @issues 8 messages (15 in previous quarter) ## Releases: - Last release was 0.21.0 on Sun Sep 09 2018 ## Mailing list activity: Activity for this project is on a downward trajectory. As noted above, this project may be headed for the Attic if this trend continues. - dev@aurora.apache.org: - 152 subscribers (down -1 in the last 3 months): - 19 emails sent to list (90 in previous quarter) - announcements@aurora.apache.org: - 47 subscribers (up 1 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@aurora.apache.org: - 36 subscribers (down -1 in the last 3 months): - 0 emails sent to list (17 in previous quarter) - reviews@aurora.apache.org: - 31 subscribers (up 0 in the last 3 months): - 8 emails sent to list (146 in previous quarter) - user@aurora.apache.org: - 87 subscribers (up 1 in the last 3 months): - 1 emails sent to list (9 in previous quarter) ----------------------------------------- Attachment G: Report from the Apache Axis Project [Robert Lazarski] # Apache Axis2 Board Report ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues There are no issues requiring board attention at this time. ## Activity - Axis2 Java 1.7.9 (stable) - Maintenance only. - Axis2 Java 1.8 (development) - Axis2 C 1.7 (development) ## Health report: We have enough PMC to cut releases. Axis2 is a mature project, but still actively maintained. Most of our users are using legacy SOAP services so we are lacking new committers. A committer offer was made this past quarter to an individual who declined. As our day jobs move more into REST and JSON, we will continue to use Axis2 for this and expect to grow our community by better docs and examples in that area. Axis2 C added a new committer, Bill Blough, this past December 2017 and so far that is helping the project pick up speed. There was more progress via commits and Jira issues this past quarter. Bill has indicated he expects his activity to increase this next quarter. ## PMC/Committer changes: - Currently 63 PMC/Commiters members. - No new committers were added in the last 90 days, last committer added was Bill Blough on December 7th 2017 who also was added to the PMC on May 9th 2018. ## Releases: - Axis 2/Java 1.7.9 was released on November 16, 2018. - Axis 2/C 1.6 was released on April 20, 2009. - Axis 1.4 was last released in 2006. ## JIRA Activity - 7 JIRA tickets created in the last 90 days. - 3 JIRA tickets closed/resolved in the last 90 days. ----------------------------------------- Attachment H: Report from the Apache Bahir Project [Luciano Resende] ----------------------------------------- Attachment I: Report from the Apache Beam Project [Kenneth Knowles] ## Description: Apache Beam is a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Beam has a number of major technical endeavors maturing. As usual for Beam, these include many integrations with other projects / communities: - Beam Python can be executed on Flink and is reported to be used in production - Beam Java on Samza is reported to be used in production, and some success reported running Beam Python on Samza - Our first release with partial Python 3 support - Beam's IO connector ecosystem is healthy, with additions or upgrades to connectivity to RabbitMQ, Redis, Spanner, Parquet, Hadoop, MongoDb, Kafka, BigQuery, Cassandra, JDBC. And Beam SQL has added Hive Metastore support. This reflects the growing diversity of users and use cases represented in the Beam community. Community event activity has seen good developments and cross-community building too: - A San Francisco-based Beam meetup group started and seems self-sustaining - Beam Python on Flink has gained interest and was presented at a Seattle Flink Meetup - Kettle on Beam was presented at a London Pentaho Meetup Beam Summit Europe 2019 is approved, to occur June 19-20 in Berlin (convenient to Berlin Buzzwords). There have been three Beam Newsletters [1, 2, 3] since the last report was authored. There are collaboratively authored - anyone can suggest content about technical achievements, what they are working on, events, blog posts, etc. Much of the above and other details can be found in the newsletter. A nice community touch is that the newsletter also gathers information from threads where people introduce themselves, so it is a place to learn/reflect on new members of the community. The community has recently discussed moving finalized newsletter to the blog or creating a "News" section on the website to boost visibility of the information and clarity around the newsletter's publication date. [1] https://s.apache.org/beam-newsletter-2018-12 [2] https://s.apache.org/beam-newsletter-2019-01 [3] https://s.apache.org/beam-newsletter-2019-02 ## Health report: Dev and user list subscription is slightly up, while traffic is slightly down. There's no indication of major health changes. The content of both lists remains qualitatively about the same. Each release tends to include commits from 60-100 contributors. ## PMC changes: - Currently 20 PMC members. - Etienne Chauchot was added to the PMC on Thu Jan 24 2019 ## Committer base changes: - Currently 50 committers. - New commmitters: - Gleb Kanterov was added as a committer on Thu Jan 24 2019 - Mark Liu was added as a committer on Fri Mar 08 2019 - Michael Luckey was added as a committer on Fri Feb 22 2019 - Raghu Angadi was added as a committer on Thu Mar 07 2019 ## Releases: - 2.9.0 was released on Thu Dec 13 2018 - 2.10.0 was released on Sun Feb 10 2019 - 2.11.0 was released on Thu Feb 28 2019 ## Mailing list activity: - dev@beam.apache.org: - 613 subscribers (up 28 in the last 3 months): - 1464 emails sent to list (1941 in previous quarter) - user@beam.apache.org: - 627 subscribers (up 28 in the last 3 months): - 391 emails sent to list (465 in previous quarter) ## JIRA activity: - 607 JIRA tickets created in the last 3 months - 462 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment J: Report from the Apache Bigtop Project [Youngwoo Kim] ## Description: - Apache Bigtop is a software related to a system for integration, packaging, deployment and validation of a big data management software distribution based on Apache Hadoop. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Bigtop community is working on 1.4.0 release. Evans Ye volunteered as release manager for the release. - Jun He, Evans Ye and Ganesh Raju will co-present Apache Bigtop and the support of big data on Aarch64 on Linaro Connect Bangkok 2019 ## PMC changes: - Currently 27 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jun He on Sun Nov 25 2018 ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Jun He at Fri Feb 23 2018 ## Releases: - Last release was 1.3.0 on Sat Nov 17 2018 ## Mailing list activity: - dev@bigtop.apache.org: - 149 subscribers (down -1 in the last 3 months): - 225 emails sent to list (277 in previous quarter) - announce@bigtop.apache.org: - 54 subscribers (up 2 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - ci@bigtop.apache.org: - 15 subscribers (down -2 in the last 3 months): - 249 emails sent to list (169 in previous quarter) - issues@bigtop.apache.org: - 41 subscribers (up 1 in the last 3 months): - 393 emails sent to list (316 in previous quarter) - user@bigtop.apache.org: - 177 subscribers (down -3 in the last 3 months): - 15 emails sent to list (17 in previous quarter) ## JIRA activity: - 77 JIRA tickets created in the last 3 months - 80 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== Releases ======== There have been no releases over the last three months. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Ryan Ollos resigned from the PMC in April 2017. Community & Development ======================= In the month since the last report, there is not much further progress to report. As mentioned in previous reports, the chair is arranging sprint days to get PMC members and potentially other interested parties together to give some dedicated time to work on the project. One sprint has been announced for the last Saturday of March. ----------------------------------------- Attachment L: Report from the Apache BVal Project [Matthew Jason Benson] ## Apache BVal Report March 2019 ## - The Apache BVal project implements the Java EE Bean Validation specification(s) and related extensions, and became a top-level project of the foundation on February 15, 2012. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have lately been working to support our 2.0.0 release from last fall. Most notably this release, which rewrote a large portion of the codebase, is quite slow compared to the reference implementation of the Java Bean Validation (BV) specification so our near-term efforts will revolve around making improvements in that regard. - The 2.0.1 release described in last quarter's report as being in planning has not yet occurred. To remind the reader, one of the main purposes of the release would be to enable the proper tooling to certify Apache BVal as an implementation of the 2.0 BV specification. ## Health report: - We retain a small core of developers with the desire to keep this project afloat. It must be admitted that the available time for this project among this pool of resources is suboptimal; we continue to do what we can. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. ## Releases: - Last release was 2.0.0 on Sat Oct 27 2018 ## Mailing list activity: - dev@bval.apache.org: - 42 subscribers (up 0 in the last 3 months): - 49 emails sent to list (118 in previous quarter) - user@bval.apache.org: - 54 subscribers (up 0 in the last 3 months): - 1 emails sent to list (5 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment M: Report from the Apache Camel Project [Andrea Cosentino] ## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are continuing our work towards Apache Camel 3.0.0: we released the Milestone 1 on 17 February 2019. - We are working on the Milestone 2 and we are focusing on new features, improvements and bug fixes. - We are continuing our work on a new website and on adding more new documentation in the repository. - We are working on a new 2.x release (2.24.0) but we still need to define a timeline for that. - We are preparing for the next minor release Apache Camel 2.23.2 expected for the end of April: we are working on bug fixes mainly. - We released Camel-K-Runtime 0.2.1 and 0.3.0 - We released Camel-K 0.2.1 and 0.3.0 - We are continuing our work on Camel-K by supporting both Camel 2.x and Camel-3.x - We held a Camel BoF at FOSDEM 2019 with two PMCs, one contributor and two community members - We're receiving signups for tasks we marked for Google Summer of Code 2019, so far two students have applied ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 33 PMC members. - Alex Dettinger is the last new PMC Member added since the last report - Last PMC was added on Mon Dec 17 2018 ## Committer base changes: - Currently 66 committers. - 3 additions since the last report - Ramu K was added as a committer on Fri Feb 22 2019 - Tadayoshi Sato was added as a committer on Mon Dec 10 2018 - Andrea Tarocchi was added as a committer on Sat Feb 23 2019 ## Releases: - Camel 2.21.4 was released on Thu Jan 10 2019 - Camel 2.21.5 was released on Sat Feb 09 2019 - Camel 2.22.3 was released on Fri Jan 25 2019 - Camel 2.23.1 was released on Fri Jan 18 2019 - Camel 3.0.0-M1 was released on Fri Feb 22 2019 - Camel-K 0.2.1 was released on Fri 22 2019 - Camel-K 0.3.0 was released on Mon Mar 04 2019 ## Mailing list activity: - users@camel.apache.org: - 1010 subscribers (up 19 in the last 3 months) - 358 emails sent to list (295 in previous quarter) - dev@camel.apache.org: - 349 subscribers (up 8 in the last 3 months) - 1450 emails sent to list (1104 in previous quarter) - issues@camel.apache.org: - 83 subscribers (down -1 in the last 3 months): - 2317 emails sent to list (1610 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 311 JIRA tickets created in the last 3 months - 247 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry] # Apache Cayenne Board Report, March 2019 ## Description Apache Cayenne is a Java database persistence framework. It takes a distinct approach to object persistence and provides an ORM runtime, remote persistence services, and a cross-platform GUI mapping/modeling tool. ## Issues There are no issues requiring board attention at this time. ## Activity New development is focused on Cayenne 4.1. Prior versions are maintenance-only. - Cayenne 3.1.3 (aging) - Maintenance only. - Cayenne 4.0 (stable) - Maintenance only. - Cayenne 4.1.B1 (development/beta) - Development continues on Cayenne 4.1. Milestone 3 was dropped in favor of Beta 1, which will be released soon. ## Health Report Cayenne is healthy. Development activity is stable and and we have a stable user and developer community. ## PMC Changes - Currently 9 PMC members. - No new PMC members added in the last 3 months. - Last PMC addition is Nikita Timofeev on Sun Jun 25 2017. ## Committer Base Changes - Currently 23 committers. - Last committer addition is Arseni Bulatski on Mon Dec 10 2018. ## Releases - Cayenne 3.1.3 on Wed Jul 25 2018. - Cayenne 4.0 on Mon Aug 20 2018. - Cayenne 4.1.M2 on Wed Jul 25 2018. Cayenne 4.1.B1 is being prepared for release. ## JIRA Activity - 51 JIRA tickets created in the last 3 months. - 36 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment O: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: - There are no issues requiring board attention at this time. ## Activity: There was basically no activity in the last three months. ## Health report: - We have a mature code base. No major development is expected. ## PMC changes: - Currently 36 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Laurent Mignon on Sat Sep 23 2017 ## Committer base changes: - Currently 38 committers. - No new committers added in the last 3 months - Last committer addition was Laurent Mignon at Wed Sep 20 2017 ## Releases: - Last release was cmislib 0.6.0 on Thu Aug 31 2017 ## Mailing list activity: - dev@chemistry.apache.org: - 162 subscribers (up 0 in the last 3 months): - 33 emails sent to list (38 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 P: Report from the Apache CloudStack Project [Mike Tutkowski] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage and networking devices. ## Issues: ## Activity: - The community is currently working on RC testing 4.12. We have also organized a CloudStack Collab Conf for Brazil on Friday, April 26th (co-hosted with The Developers Conference (http://www.thedevelopersconference.com.br)). ## Health report: - Version 4.12.0 is in the process of RC testing. - Planning is underway for a CloudStack Collaboration Conference co-located with ApacheCon in Las Vegas (September). ## PMC changes: - Currently 46 PMC members (one removed since last report per his request) - Most recently added PMC member was Syed Ahmed on Sun Oct 08 2017 ## Committer base changes (no change since last report): - Currently 119 committers - Most recently added committer was Boris Stoyanov on Wed Dec 12 2018 ## Releases: - Release 4.11.2.0 on Nov 13 2018 ----------------------------------------- Attachment Q: Report from the Apache Commons Project [Gary D. Gregory] ## Description: - Apache Commons is an Apache project focused on all aspects of reusable Java components. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Activity is good with the release of 9 components. ## Health report: - We migrated all active components that remained in Subversion to GitBox. - The project is healthy and has welcomed two new committers. - We are continuing to improve the release process by updating our Maven plugins. - Mailing activity is good and JIRAs are addressed in a timely manner for most components. ## PMC changes: - Currently 38 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rob Tompkins on Fri Jun 30 2017 ## Committer base changes: - Currently 147 committers. - Maxim Solodovnik was added as a committer on Tue Dec 18 2018 - Alex Herbert was added as a committer. ## Releases: - BCEL-6.3 was released on Sun Jan 27 2019 - CODEC-1.12 was released on Tue Feb 12 2019 - COLLECTIONS-4.3 was released on Mon Feb 04 2019 - DBCP-2.6.0 was released on Tue Feb 19 2019 - FILEUPLOAD-1.4 was released on Thu Dec 27 2018 - POOL-2.6.1 was released on Tue Feb 12 2019 - RELEASE-PLUGIN-1.5 was released on Tue Jan 29 2019 - RNG-1.2 was released on Tue Dec 11 2018 - VFS-2.3 was released on Sun Feb 03 2019 ## JIRA activity: - 138 JIRA tickets created in the last 3 months - 100 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache Cordova Project [Jesse MacFadyen] Status report for the Apache Cordova project - March 2019 Description: A platform for building native mobile applications using HTML, CSS and JavaScript. Issues: There are no issues requiring board attention at this time. Activity: We made 6 platform releases (Android@8, Browser@6, Electron@1, iOS@5, OSX@5, Windows@7), and 1 patch release (Electron@1.0.1). Electron is a new platform, and the 2 releases were the first. We also made 8 tools/libraries releases. Health report: Our status dashboard at http://status.cordova.io is mostly all green - failures are usually due to external service issues that do device testing. Our nightly builds remain extremely stable. We are still actively working to resolve all existing issues in JIRA while also maintaining all the new issues and pull requests in Github. PMC changes: - Currently 94 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bryan Ellis on Wed Jul 25 2018 Committer base changes: - Currently 97 committers. - No new committers added in the last 3 months - Last committer addition was Bryan Ellis at Thu Jul 26 2018 Releases: Platforms - cordova-android@8.0.0 was released on Fri Feb 15 2019 - cordova-browser@6.0.0 was released on Sun Feb 03 2019 - cordova-electron@1.0.0 was released on Wed Feb 27 2019 - cordova-electron@1.0.1 was released on Tue Mar 05 2019 - cordova-ios@5.0.0 was released on Fri Feb 08 2019 - cordova-osx@5.0.0 was released on Sun Feb 03 2019 - cordova-windows@7.0.0 was released on Thu Mar 07 2019 Libraries - cordova-app-hello-world@4.0.0 was released on Mon Dec 24 2018 - cordova-common@3.1.0 was released on Wed Jan 02 2019 - cordova-create@2.0.0 was released on Wed Jan 09 2019 - cordova-fetch@2.0.0 was released on Mon Dec 24 2018 - cordova-js@5.0.0 was released on Mon Dec 24 2018 - cordova-node-xcode@1.1.0 was released on Thu Dec 20 2018 - cordova-node-xcode@2.0.0 was released on Wed Jan 16 2019 - cordova-serve@3.0.0 was released on Mon Dec 24 2018 JIRA activity: - 0 JIRA tickets created in the last 3 months (JIRA has been shut down) - 10 JIRA tickets closed/resolved in the last 3 months Github activity: Issue close rate of 43%: - 423 Github Issues created in the last 3 months - 182 Github Issues closed in the last 3 months PR close rate of 96%: - 216 Github Pull Requests created in the last 3 months - 207 Github Pull Requests closed/merged in the last 3 months ----------------------------------------- Attachment S: Report from the Apache cTAKES Project [Pei Chen] ## Description: Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is an open-source natural language processing system for information extraction from electronic medical record clinical free-text. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Committee continues to work on the future release (4.0.1) - Committee continues to work on bug fixes and improvements documented in Jira ## Health report: - The community continues to be moderately active. - There are new questions/suggestions from new users on the mailing lists - There is steady increase in interest and growth in the community based on the activity on the mailing lists ## PMC changes: - Currently 31 PMC members. - Last PMC addition was Gandhi Rajan on Thu Jul 12 2018 ## Committer base changes: - Currently 38 committers. - Last committer addition was Gandhi Rajan at Tue Nov 14 2017 ## Releases: - Last release was 4.0.0 on Thu Apr 27 2017 - 3.2.2 was released on May 30 2015 - 3.2.1 was released on Dec 10 2014 ## Mailing list activity: There was an increase in number of emails/discussions sent to the dev and user @ mailing lists with less subscribers. - dev@ctakes.apache.org: - 257 subscribers (down -5 in the last 3 months): - 97 emails sent to list (32 in previous quarter) - user@ctakes.apache.org: - 269 subscribers (down -2 in the last 3 months): - 60 emails sent to list (17 in previous quarter) ----------------------------------------- Attachment T: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: - Apache Curator is a Java/JVM client library for Apache ZooKeeper, a distributed coordination service. It includes a highlevel API framework and utilities to make using Apache ZooKeeper much easier and more reliable. It also includes recipes for common use cases and extensions such as service discovery and a Java 8 asynchronous DSL. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Good community involvement since last report - Important bugs are being reported and feature suggestions ## Health report: - For whatever reason, things seem healthier at this juncture - As always we'd love more committers. We came close to a new one but there was pushback internally. We continue to scout for new committers. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Fangmin Lv on Mon Mar 27 2017 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Fangmin Lv at Tue Mar 28 2017 ## Releases: - Apache Curator 4.1.0 was released on Tue Dec 18 2018 - Apache Curator 4.2.0 was released on Tue Mar 05 2019 ## Mailing list activity: - dev@curator.apache.org: - 55 subscribers (down -1 in the last 3 months): - 632 emails sent to list (172 in previous quarter) - user@curator.apache.org: - 164 subscribers (up 0 in the last 3 months): - 23 emails sent to list (11 in previous quarter) ## JIRA activity: - 20 JIRA tickets created in the last 3 months - 25 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Eagle Project [Edward Zhang] ## Description: - Apache Eagle is an open source analytics solution for identifying security and performance issues instantly on big data platforms. ## Issues: - There are no issues requiring board attention at this time ## Activity: - In Eagle dev mail list, architecture improvement is still on-going, committers were discussing pros and cons for different options. - Communities raised some questions about using Eagle ## Health report: - Seen continuous interests on Eagle adoption from community, really need committers to answer the questions quickly. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Deng Lingang on Mon May 08 2017 ## Committer base changes: - Currently 18 committers. - No new committers added in the last 3 months - Last committer addition was Jay Sen at Thu Mar 16 2017 ## Releases: - Last release was 0.5.0 on Sat Sep 09 2017 ## Mailing list activity: - dev@eagle.apache.org: - 72 subscribers (down 4 in the last 3 months): - 31 emails sent to list (11 in previous quarter) - issues@eagle.apache.org: - 19 subscribers (up 0 in the last 3 months): - 2 emails sent to list (15 previous quarter) - user@eagle.apache.org: - 57 subscribers (up 1 in the last 3 months): - 1 emails sent to list (1 in previous quarter) ----------------------------------------- Attachment V: Report from the Apache Falcon Project [Pallavi Rao] ABOUT Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. ISSUES The project is not seeing much traction in the past few months and seems to have run its course. Have initiated a discussion asking for suggestion from the community and so far there hasn't been much forthcoming. Wish to keep the email thread open a little longer before we decide to move the project to attic, just to give the community a little more time to think about it. STATUS After 0.11 release there have been no new feature asks from the community. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sowmya Ramesh on Mon Jun 06 2016 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Sandeep Samudrala at Thu Mar 09 2017 ## Releases: - Last release was 0.11 on Tue Mar 13 2018 ## Mailing list activity: - dev@falcon.apache.org: - 106 subscribers (down -4 in the last 3 months): - 19 emails sent to list (8 in previous quarter) - user@falcon.apache.org: - 31 subscribers (up 0 in the last 3 months): - 1 emails sent to list (1 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 W: Report from the Apache Felix Project [Karl Pauls] ## Description: Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Existing implementations have been improved/enhanced based on community feedback. - Released 15 components (mostly bug fixes and a new healthcheck subproject). - Accepted and integrated the "Health Check Framework" contribution from the Apache Sling project. ## Health report: - Overall the project is in good health. - Questions on the user list are answered, development concerns are either discussed on the mailing list or directly in the JIRA issues. - The project as well as the OSGi community in general is still in the process of adapting to JPMS and its long term impact. - We added 3 committer by attracting a contribution from the Apache Sling project. The contribution (called healthchecks) has been integrated and released. - Turning some of the committers we gained recently into PMC members needs to be a focus for the upcoming quarter. - We had no issues voting on releases and JIRA issues are generally addressed promptly. ## PMC changes: - Currently 26 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Raymond Augé on Thu May 03 2018 ## Committer base changes: - Currently 67 committers. - New commmitters: - Bertrand Delacretaz was added as a committer on Tue Dec 18 2018 - Georg Henzler was added as a committer on Tue Dec 18 2018 - Oliver Lietz was added as a committer on Tue Dec 18 2018 ## Releases: - felix-logback-1.0.2 was released on Mon Jan 21 2019 - org.apache.felix.converter-1.0.4 was released on Thu Mar 07 2019 - org.apache.felix.dependencymanager-r15 was released on Sun Dec 23 2018 - org.apache.felix.framework-5.6.12 was released on Mon Feb 04 2019 - org.apache.felix.framework-6.0.2 was released on Thu Jan 31 2019 - org.apache.felix.gogo.jline-1.1.4 was released on Mon Jan 28 2019 - org.apache.felix.healthcheck.annotation-2.0.0 was released on Mon Feb 25 2019 - org.apache.felix.healthcheck.api-2.0.0 was released on Mon Feb 25 2019 - org.apache.felix.healthcheck.core-2.0.0 was released on Mon Feb 25 2019 - org.apache.felix.healthcheck.generalchecks-2.0.0 was released on Mon Feb 25 2019 - org.apache.felix.healthcheck.webconsoleplugin-2.0.0 was released on Mon Feb 25 2019 - org.apache.felix.main-6.0.2 was released on Thu Jan 31 2019 - org.apache.felix.main.distribution-6.0.2 was released on Thu Jan 31 2019 - org.apache.felix.scr-2.1.12 was released on Tue Feb 26 2019 - org.apache.felix.scr.bnd-1.9.2 was released on Mon Jan 28 2019 ## Mailing list activity: - users@felix.apache.org: - 564 subscribers (down -2 in the last 3 months): - 75 emails sent to list (134 in previous quarter) - dev@felix.apache.org: - 320 subscribers (down -4 in the last 3 months): - 876 emails sent to list (844 in previous quarter) ## JIRA activity: - 84 JIRA tickets created in the last 3 months - 72 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: Report from the Apache Flex Project [Olaf Krüger] ## Description: Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity on the mailing list among the users stayed the same as in the previous three months. We are responding when users have problems with downloading the SDK due to changes related to the MD5 signature on the Adobe side. Repositories of the project were migrated to gitbox. A vote on the move to the github wiki and github issues has received no majority [1]. There is an ongoing trademark issue that the PMC and trademarks are dealing with: The Xeptor issue is resolved, the MagicMotorsprot issue remains to be resolved. ## PMC changes: - Currently 45 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Olaf Krüger on Mon Aug 28 2017 - Dave Fisher resigned from PMC - Carol Frampton resigned from PMC - Olaf Krüger was approved as the new chair in January 2019 ## Committer base changes: - Currently 69 committers. - No new committers added in the last 3 months - Last committer addition was Greg Dove at Wed Sep 07 2016 ## Releases: - Apache Flex SDK 4.16.1 on 2017-11-22 - Apache Flex Installer 3.3.2 on 2018-07-09. ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months [1] http://apache-flex-development.2333347.n4. nabble.com/Vote-Moving-JIRA-issues-and-Confluence-Wiki-to-GitHub-td65616.html ----------------------------------------- Attachment Y: Report from the Apache Flink Project [Stephan Ewen] DESCRIPTION Apache Flink is a distributed data streaming system for batch and streaming data analysis on top of a streaming dataflow engine. Flink's stack contains functional batch and streaming analysis APIs in Java and Scala and libraries for various use cases. Flink interacts and integrates with several Apache projects in the broader ecosystem of data storage and computing, such as Apache Beam, Calcite, Hadoop, Mesos, Kafka, HBase, Cassandra, and various others. ISSUES - There are no issues that require board attention. STATUS AND ACTIVITY - The Flink community is trying to improve many community aspects in the last months, resulting in a lot of discussions and efforts. - Inspired by the effort from the Apache Beam project, the Flink PMC is looking to have a monthly discussion on promising candidates for committers and PMC and actively reach out. There are already healthy discussions about PMC and committer growth. - The community added a Chinese language user@flink mailing list for user-to-user questions and support. Since its creation six weeks ago, the list has already gathered 300 subscribers. Design discussions and decisions still happen on the dev mailing list. - The trademark issue with the https://flink-china.org website (mainly a translation of the official Flink website) was resolved by convincing the maintainers to contribute the contents to the Apache website. The Flink website is now dual-language (Chinese version under https://flink.apache.org/zh/). The https://flink-china.org is currently online, with a disclaimer that it is being contributed and to the official Flink website and will then be shut down. - Alibaba has contributed the code of their internal Flink fork 'Blink' back to the open source project. The code is available in a separate branch, the community is working on merging selected parts into the mainline. - The community published a roadmap for the project, which sums up the active Flink Improvement Proposals (FLIPs) and JIRA issues to give users and contributors an easily digestible overview of all the ongoing efforts. - There are several discussion threads on how to improve the experience of contributing to Flink and keeping up with a large number of contributions. Current efforts include a better organization of JIRA components, a more transparent review process, and some automation through a pull request bot. In addition, we are thinking about component-specific guides and test frameworks, for example for connectors. - The community is in the process of releasing Flink 1.8. The release contains some new user-facing features plus a lot of internal cleanup and refactoring, fixing some long term issues, and preparing the work on a deeper integration of batch and stream processing in the runtime. - Program for Flink Forward San Francisco is online: https://sf-2019.flink-forward.org/conference-program Flink committers can get a free pass, and there are a discount codes for other Apache committers. COMMUNITY PMC members added since the last board report: - Thomas Weise joined the PMC on February 12th, 2019 No new committers were added since the last board report. The newest PMC member is Thomas Weise, joined on February 12th, 2019. The newest committer is Jamie Grier, joined on December 17th, 2018. Flink currently has 43 committers and 20 PMC members. RELEASES The following releases were made since the last board report: - 1.6.3 was released on December 21st, 2018 - 1.6.4 was released on February 22nd, 2019 - 1.7.1 was released on December 20th, 2018 - 1.7.2 was released on February 14th, 2019 - shaded-6.0 was released on February 12th, 2019 ACTIVITY ON JIRA / MAILING LISTS Mailing lists continue to be very active: - user@f.a.o (1737 mails/quarter) - dev@f.a.o (1963 mails/quarter) JIRA continues to be active as well, 767 JIRA tickets created, 836 JIRA tickets resolved in the last 3 months. ----------------------------------------- Attachment Z: Report from the Apache Guacamole Project [Mike Jumper] ## Description: - Apache Guacamole is a clientless remote desktop gateway which supports standard protocols like VNC, RDP, and SSH. We call it "clientless" because no plugins or client software are required. Once Guacamole is installed on a server, all you need to access your desktops is a web browser. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Noticeable increase in activity and community involvement following release of 1.0.0, particularly on the dev@ and user@ mailing lists. - Current development is focused on the 1.1.0 release whose scope was settled shortly after the release of 1.0.0. ## Health report: - The project is healthy. Development and community involvement continue to be active. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Carl Harris on Sun Nov 19 2017 ## Committer base changes: - Currently 12 committers. - Joel Best was added as a committer on Wed Jan 30 2019 ## Releases: - 1.0.0 was released on Mon Jan 07 2019 ## Mailing list activity: - dev@guacamole.apache.org: - 91 subscribers (up 2 in the last 3 months): - 552 emails sent to list (380 in previous quarter) - announce@guacamole.apache.org: - 6 subscribers (up 6 in the last 3 months): - 3 emails sent to list (0 in previous quarter) - issues@guacamole.apache.org: - 7 subscribers (up 7 in the last 3 months): - 388 emails sent to list (0 in previous quarter) - user@guacamole.apache.org: - 334 subscribers (up 15 in the last 3 months): - 713 emails sent to list (352 in previous quarter) ## JIRA activity: - 75 JIRA tickets created in the last 3 months - 58 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == Very light activity, but really no changes compared to the last quarter. == Releases == Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. == Activity == The Maven Repository Proxy used by Gump in order to inject freshly built artifacts into dependent builds was changed to only listen to the local network address. The Tomcat and Forrest communities are still using Gump actively. We will need to migrate from our Moin Wiki instance. Work hasn't started, yet, but we'll do so during the next quarter. == Changes to the Roster == All ASF committers have write access to the metadata that configure the ASF installations. The last changes to the PMC have seen Konstantin Kolinko and Mark Thomas join in November 2014. ----------------------------------------- Attachment AB: 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: - Start discussion future roadmap - Move from git-wp to gitbox ## Health report: - In spite of low activities, this might be enough at this point. A few tasks had been initiated, and discussion with respect to the future development. ## 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 AC: Report from the Apache Helix Project [Kishore G] ## Description: - A cluster management framework for partitioned and replicated distributed resources. ## Issues: - There are no issues requiring board attention at this time ## Health report: - Release 0.8.4 was out in Mar. 6 2019. - There is regular level of activities on commits, pull requests and releases.- Dev mail list activities was normal, user email activities dropped. We have moved the discussion into Slack channels.- - One new committer added. Many of current committers are not quite active in terms of daily developments and pull request review, need to look for potential new committers from the community. ## PMC changes: - Currently 18 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Junkai Xue on Mon Jul 03 2017 ## Committer base changes: - Currently 20 committers. - Hunter Lee was added as a committer on Tue Mar 12 2019 ## Releases: - Last release was 0.6.9 on Sat Oct 14 2017 ## Mailing list activity: - dev@helix.apache.org: - 68 subscribers (down -2 in the last 3 months): - 172 emails sent to list (246 in previous quarter) - user@helix.apache.org: - 106 subscribers (up 2 in the last 3 months): - 5 emails sent to list (54 in previous quarter) ## JIRA activity: - 24 JIRA tickets created in the last 3 months - 17 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AD: Report from the Apache Hive Project [Ashutosh Chauhan] ## Description: The Apache Hive (TM) data warehouse software facilitates querying and managing large datasets residing in distributed storage. ## Issues: No issues requiring board attention at this time. ## Activity: Although good all-around activity was little lower compared to previous quarter. We attribute that to holiday season of last year. Activity on jira is again picking up in recent weeks. ## PMC changes: - No changes this quarter to existing roster of 47 PMC members. - Last addition Zoltan Haindrich (Oct 29 2018) ## Committer changes: - No changes this quarter to existing roster of 83 committers - Last addition Bharath Krishna (Nov 30 2018) ## Releases: - No new release this quarter ## JIRA activity: - 411 JIRA tickets created in the last 3 months - 238 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AE: Report from the Apache Incubator Project [Justin Mclean] Incubator PMC report for March 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 51 podlings incubating. During the month of February, podlings executed 8 distinct releases. We added one new IPMC member (and new candidates are being considered) and we've had one IPMC member retire. We have two new podlings this month, Apache Training and Apache Cava (name will change). Unomi graduated last month and several podlings are heading towards graduation in the next few months. There are currently a conversation on accepting another new podling into the incubator. BatchEE took a vote to go to Apache Geronimo or TLP and decided on TLP they have given themselves until June to graduate. Both of the podlings that failed to report this last month submitted a report this month. Three podlings have not submitted reports and will be asked to report them next month. They are: - Spot - Taverna - Warble Warble is mostly inactive but has plans to address this. OpenWhisk failed to get sign off by any mentors and will be asked to report next month. There was one IP clearance. As reported last month we have a problem with unapproved releases. Checking other podlings showed several that are making unapproved releases or have branding and trademark issues. Several where contacted and have fixed the issue. ECharts has several issues that are still outstanding but their mentors and their PPMC are dealing with it. A podling (Zipkin) went straight to the board with a complaint that the incubator is unfriendly. (Their first release had a -1 IPMC vote for including compiled code in a source release and was muddied by further comments that were not pertinent to the -1 vote) Since then there has been number of conversations on private and public lists about this (and other issues) and it's brought up some old "the incubator is broken" threads. The IPMC has been given many suggestions for improvement. Some of the suggestions for incubator change are positive and are likely to show benefits, some ignore recent improvements in the incubator and refer to how the incubator was in the past, and a couple seem to have little basis in fact. Several come from people who are not IPMC members or are not currently actively involved in the IPMC. The IPMC is reviewing all these suggestions and will evaluate them and other ideas to see what is possible to implement in the near future without having a detrimental impact on all current podlings and mentors. Some of these discussion about IPMC interference have already had a cooling effect of voting on releases and a couple of podlings needed to request help on release voting. One release that was put up for IPMC vote, seemingly without mentor input, and it contained several significant ASF policy issues. There were several discussions about podlings releasing software outside the ASF (mostly on docker and GitHub) and ways of providing guidance to them to comply with ASF's legal, release, distribution and trademark policy that got a little derailed because of the above. It was noticed that GitHub is publishing release candidates (and in fact any tag) as a release. I believe Infra has reached out to GitHub to see what can be done to improve this. * Community New IPMC members: Jan Piotrowski People who left the IPMC: Hyrum Kurt * New Podlings Training Cava * Podlings that failed to report, expected next month are listed above * Graduations The board has motions for the following: - None * Releases The following releases entered distribution during the month of February: - MXNet 1.4.0 - OpenWhisk Composer 0.10.0 - Zipkin Brave for Apache Karaf 0.1.2 - Daffodil 2.3.0 - Dubbo OPS 0.1 - Doris 0.9.0 - Dubbo Spring Boot Project 2.7.0 - PLC4X 0.3.0 * IP Clearance Apache Arrow Rust DataFusion * Legal / Trademarks N/A * Infrastructure N/A * Miscellaneous A couple of mentors were found for podlings with less than 3 mentors. A few old unused incubator mailing lists were shut down. A discussion come up about short non-ASF domain names and hosting copies of ASF sites in China. ---------------------------------------------------------------------- Table of Contents BRPC Crail Daffodil DLab Druid Dubbo Hivemall Hudi Iceberg IoTDB Marvin-AI Myriad Nemo Omid OpenWhisk Pinot Pony Mail SAMOA ShardingSphere SINGA SkyWalking Superset Tamaya Tephra Training Zipkin ---------------------------------------------------------------------- -------------------- 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. Repo has been just moved to apache org,thanks for apache infra‘s help 2. Begin to prepare an apache release 3. Community buidling is going on Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Community is a little shy, some more activities could be occurred in the mail list. How has the community developed since the last report? Added one PPMC member How has the project developed since the last report? The repo has been moved to apache git hosted on github, committers are working on remaining commit permission issues How would you assess the podling's maturity? Very beginning of the podling Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: No Apache release When were the last committers or PPMC members elected? Added one PPMC member-JerryTan 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 is very helpful to push apache infra to work on repo transfer, and added jerrytan as new PPMC member. Von Gosling is also trying his best to encourage ppmc members to be more active and make discussion about the feature development in the community. Signed-off-by: [X](brpc) Kevin A. McGrail Comments: I'll try and be more helpful. I've subscribed to dev and private. [ ](brpc) Jean-Baptiste Onofré Comments: [x](brpc) Von Gosling Comments: IPMC/Shepherd notes: Dave Fisher: now the the git repository has finally been transferred and the correct membership is on the PPMC the podling can finally get some community traction. I plan to keep a close eye and will ask to officially mentor if needed. Von Gosling: community should be encouraged to make more discussion in the mail list. -------------------- Crail Crail is a storage platform for sharing performance critical data in distributed data processing jobs at very high speed. Crail has been incubating since 2017-11-01. Three most important issues to address in the move towards graduation: 1. Community building: Increase on number of contributors and users. 2. Further increase project visibility 3. Make Crail better consumable / cooperate with other projects on Crail integration. 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 OSDI'18 paper on Elastic Ephemeral Storage for Serverless Analytics (based on Apache Crail) increased projects visibility noticeable. * We added two blog posts to the projects Apache home page. One blog covers the performance of the Crail Python API, another efficient shuffle data dis-aggregation via Crail. * The @ApacheCrail twitter account has 155 followers. We use it to regularly tweet the availability of new blog posts, code releases etc. How has the project developed since the last report? * Bug fixes for current release. * Started evaluation of options for adding fault tolerance/robustness to Crail service. * Started native C++ implementation of Crail tailored to Machine Learning framework integration (such as TensorFlow, PyTorch, etc.) 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: Nov-26-2018 When were the last committers or PPMC members elected? December 4th, 2018 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 mentors are very helpful. We are very happy we got Felix Cheung offering help as a third mentor. Signed-off-by: [x](crail) Felix Cheung Comments: Good work on external community; would love to see more traffic on dev@ [x](crail) Julian Hyde Comments: I enjoyed the blog post. Crail seem to be doing the right things to attract community, hoping that we see new contributors soon. [x](crail) Luciano Resende Comments: IPMC/Shepherd notes: -------------------- Daffodil Apache Daffodil is an implementation of the Data Format Description Language (DFDL) used to convert between fixed format data and XML/JSON. Daffodil has been incubating since 2017-08-27. Three most important issues to address in the move towards graduation: 1. Increase community growth and participation 2. Establish a frequent release schedule 3. Work with other Apache projects where Daffodil could provide extra functionality 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? - A user is developing a DFDL/Daffodil class, leading to many good discussions on the users@ mailing list - Apache PLC4X has developed a DFDL schema and used Daffodil as a means to parse Industrial IoT data - Continued discussions and investigations to integrate Daffodil with Apache NiFi - Mike Beckerle gave a talk at a local Meetup in December, leading to some discussions on the users@ list - Steve Lawrence is scheduled to give a talk at the Apache Roadshow in DC, March 25 - Contributions made from two first time Daffodil contributors How has the project developed since the last report? - 44 commits from 5 different developers - 62 issues created, 57 issues resolved 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-02-26 When were the last committers or PPMC members elected? - None, same as project incubation 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. - We have one inactive mentor, but the addition of a new mentor should help with that Signed-off-by: [X](daffodil) John D. Ament Comments: [X](daffodil) David Fisher Comments: The project is doing well with the code and helping users. Focus on community growth is now required. Thank you CDutz for mentoring! [X](daffodil) Christofer Dutz Comments: Just started out being a mentor for Daffodil a week ago ... IPMC/Shepherd notes: -------------------- DLab DLab is a platform for creating self-service, exploratory data science environments in the cloud using best-of-breed data science tools. DLab has been incubating since 2018-08-20. Three most important issues to address in the move towards graduation: 1. Execute the SGA between EPAM and the ASF so code can be imported 2. Complete on-boarding of initial committers 3. Work toward an initial Apache releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Not this time How has the community developed since the last report? All initial committers have completed on-boarding. Also we've seen addition of 3 more contributors: Anna Orlovska, Oleksandr Isniuk and Demyan Mysakovets How has the project developed since the last report? The team fully switched our work to Apache Infrastructure: JIRA, Git. Also we've been working hardly towards first Apache release. Release branch has been created and is waiting for further acceptance by means of voting in apache general mailing list. We've already reviewed and fixed couple of enhancements proposed by our mentors in regards to the release. We've added bunch of new features, all of them described in release notes: https://github.com/apache/incubator-dlab/releases/tag/2.1 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: N/A When were the last committers or PPMC members elected? Oleksandr Isniuk added as new PPMC 2/26/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. We would highly appreciate if following page could start being populated: https://incubator.apache.org/projects/dlab.html, currently there are many empty pages, not all sections are filled in. The team can provide all needed information, but unfortunately we don't ability to Edit this page. Signed-off-by: [ ](dlab) P. Taylor Goetz Comments: [X](dlab) Henry Saputra Comments: Working on first release under Apache [ ](dlab) Konstantin I Boudnik Comments: IPMC/Shepherd notes: Dave Fisher: DLAB is yet another podling that does not understand that the top 3 items to address question is forward looking. The IPMC needs to refine the question - English language tenses can be subtle. Since MOIN Wiki is going away there is an opportunity to do this. -------------------- Druid Druid is a high-performance, column-oriented, distributed data store. Druid has been incubating since 2018-02-28. Three most important issues to address in the move towards graduation: 1. Complete more Apache releases 2. Move the website to Apache infrastructure 3. Continue to grow the community 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? - We see growth in the number of downloads for Druid, with a ~11% compound weekly rate since the last podling report. - We see a good rate of new PRs opened (between 10-30 opened weekly) since the last report. - The project has been receiving ~25 Github stars added per week since the last report. - The next Druid meetup has been scheduled for April 2, 2019. How has the project developed since the last report? - Since the last report, we have had a total of 151 commits from 23 contributors - We have released 0.13.0-incubating, our first incubator release - We have code frozen the branch for our second release, 0.14.0-incubating, and we are currently preparing the release candidate. - We have updated our LICENSE and NOTICE files which were issues in our first release - We are continuing to work on moving the project pages from druid.io to druid.apache.org How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: - Druid 0.13.0-incubating was released on Dec 12, 2018. When were the last committers or PPMC members elected? The Druid PPMC elected 10 new committers to the project on November 20, 2018. 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. They have been very helpful. Signed-off-by: [x](druid) Julian Hyde Comments: Druid are indeed close to graduation. We should start discussion on the dev list about what is left to do. [ ](druid) P. Taylor Goetz Comments: [ ](druid) Jun Rao Comments: IPMC/Shepherd notes: -------------------- Dubbo Dubbo is a high-performance, lightweight, java based RPC framework. Dubbo has been incubating since 2018-02-16. Three most important issues to address in the move towards graduation: 1. Ensure PPMC is involved in organizing meetup. 2. Self-correcting things that are not done in Apache way. 3. Ensure more decision are happening on list. 4. Add more committers/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? * New committer: (12 in total, 25% are from Alibaba) * Taosheng Wei(tswstarplanet) has been voted as committer on 2019-01-23 * Xianjun Ke(kexianjun) has been voted as committer on 2019-1-25 * Kun Song(satansk) has been voted as committer on 2019-1-30 * Xiaojie Li(lixiaojiee) has been voted as committer on 2019-1-31 * Yuhao Bi(biyuhao) has been voted as committer on 2019-2-2 * Zhongming Hua(crazyhzm) has been voted as committer on 2019-2-18 * New PMC member: (19 in total, excluding mentors, 52% are from Alibaba) * Yuhang Xiu(carryxyh) has been voted as pmc member on 2018-12-20 * Yunkun Huang(htynkn) has been voted as pmc member on 2019-2-25 * New users: (136 in total) * 18 new companies reported their using of Dubbo since last report * Meetup * Guangzhou Meetup was held on 2019-01-19, with online registration ~400, and on-site registration: 200+ * Nanjing Meetup: CFP is closed, topics selection is ongoing. The ppmc is involved in all the way, including discussing scheduling, call for participation, topic selection and etc. * Ecosystem project(under http://github.com/dubbo, non-Apache repositories) * Future steps of how to deal with ecosystem projects has been discussed on the list, most of them will be brought to ASF * dubbo-samples has been transferred into ASF * dubbo-registry-nacos has been merged into 2.6.x branch * dubbo-configcenter-archaius has been deleted * dubbo-spring-cloud-project has been deleted * dubbo-metrics has been added, to avoid potential branding issue, a discussion on renaming to metrics is ongoing These projects are being watched by Apache Dubbo PPMC and are planning be moved to Apache once they meet the quality requirement. * Branding: * The branding issues for start.dubbo.io has been identified and the solution is being discussed * Non ASF maven binary snapshot distribution has been identified for module dubbo-registry-etcd3 and dubbo-rpc-native-thrift, the code will be merge into incubator-dubbo repository. * Unapproved maven binary distribution spring-boot-starter 0.1.2.RELEASE and 0.2.1.RELEASE are identified. * All the non Apache release in GitHub has been renamed to be clearly different with Apache releases. How has the project developed since the last report? * Dubbo spring boot starter 0.2.1 and 0.1.2 is released on 2019-01-27 * Dubbo 2.7.0 is released on 2019-01-29 * Dubbo spring boot starter 2.7.0 is released on 2019-02-14 * Dubbo Ops 0.1 is release on 2019-02-15 * Dubbo 2.6.6 is under release vote * Dubbo 2.7.1 is under development * A dramatic increase of mailing list discussion is observed: * 2018-12-01~2019-02-28: 1135 emails, 96 participants, 203 topics * 2018-09-01~2018-11-31: 663 emails, 68 participants, 118 topics * 2018-06-01~2018-08-31 : 680 emails, 85 participants, 128 topics * Github stats: (With the increase of community, more collaboration are happening) * 2018-12-01~2019-02-02: 332 issues closed, 382 pr closed * 2018-09-01~2018-11-31: 182 issues closed, 190 pr closed * 2018-06-01~2018-08-31 : 200 issues closed, 287 pr closed * number of stars has grown from 22796 to 24735. * contributors has been grown from 144 to 179. * number of forks has grown from 15761 to 16603. * Community effort project: * With the help from community, the code coverage has been increase to 64% How would you assess the podling’s maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [x] Nearing graduation [ ] Other: I think Dubbo is in a good shape towards graduation. Date of last release: 2019-02-15 When were the last committers or PPMC members elected? 2019-02-25 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 are very responsive and have provided many useful feedback. Signed-off-by: [X](dubbo) Justin Mclean Comments: Agree with the points Mark and ave raise. PPMC is being more proactive in fixing any issues. [X](dubbo) Mark Thomas Comments: I agree the podling is nearing graduation. Another month or two to consolidate their understanding of how Apache projects operates and I think they'll be ready to graduate. [X](dubbo) David Fisher Comments: Podling is doing well. There is an ecosystem around Dubbo where IP issues are murky. PPMC is appropriately evaluating the status of related "Dubbo" projects. The correct questions are being asked. IPMC/Shepherd notes: -------------------- Hivemall Hivemall is a library for machine learning implemented as Hive UDFs/UDAFs/UDTFs. Hivemall has been incubating since 2016-09-13. Three most important issues to address in the move towards graduation: 1. Community growth (committers and users) 2. One or more Apache Releases as an Incubator project 3. Documentation improvements 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? * Github watchers/stars are gradually increasing: 199 stars as of Mar 1 (was 181 on Nov 27) * Twitter account @ApacheHivemall followers are gradually increasing: 189 followers as of Mar 1 (was 175 on Nov 27) How has the project developed since the last report? * Released the second Apache release v0.5.2 on Dec 3, 2018. Since the last report, we have * In the last 3 months, we opened 13 JIRA issues and closed 17 JIRA issues as seen in https://goo.gl/QFQEF5 (as of Mar 1) Created Resolved Dec 2018 1 2 Jan 2019 6 6 Feb 2019 6 3 * Created 10 Pull Requests and closed 10 Pull Requests between Nov 28th and Feb 28th. https://github.com/apache/incubator-hivemall/pulls?utf8=%E2%9C%93&q=is%3Apr+ created%3A2018-11-28..2019-02-28 https://github.com/apache/incubator-hivemall/pulls?utf8=%E2%9C%93&q=is%3Apr+ closed%3A2018-11-28..2019-02-28 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: 2018-12-03 When were the last committers or PPMC members elected? - Elected Jerome Banks as a committer on April 2, 2018. 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. - Koji is active at mentoring. Signed-off-by: [ ](hivemall) Xiangrui Meng Comments: [ ](hivemall) Daniel Dai Comments: [x](hivemall) Koji Sekiguchi Comments: We've released 0.5.2 in December. We've moved repository to gitbox smoothly in January. As the lead PPMC, Makoto handles the community nicely and other PMC members are cooperative team players. IPMC/Shepherd notes: -------------------- Hudi Hudi provides atomic upserts and incremental data streams on Big Data Hudi has been incubating since 2019-01-17. Three most important issues to address in the move towards graduation: 1. Make frequent releases as per Apache guidelines 2. Grow community 3. Complete SGA, transfer code to ASF infra Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * PODLINGNAMESEARCH-162 has been completed, but is not reflected on Whimsy How has the community developed since the last report? Project's still being setup. Few new user inquiries, 10+ signups on dev@ ML How has the project developed since the last report? 1. Podling name search has been completed (PODLINGNAMESEARCH-162) 2. hudi.apache.org site has been published with community guidelines 3. Hudi Improvement Plan (based off Apache Kafka KIP) under review 4. Agreement over code migration method, JIRA vs Github Issues 5. Submitted a Hudi talk abstract for upcoming Berlin Buzzwords in June 2019 6. Issues migrated to Apache JIRA from github. 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: Project still being established When were the last committers or PPMC members elected? No new committers since incubation. 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 are actively following up on ML questions and pointing out gaps Signed-off-by: [X](hudi) Thomas Weise Comments: Nice uptick on mailing list activity and collaboration thinking. [x](hudi) Luciano Resende Comments: A formal improvement process such based on Kafka KIP might be overkill for a podling that is actively looking for growing the community. Usually these processes are implemented on big communitites that want to have some control over stability or backward compatibility of the code. [ ](hudi) Kishore Gopalakrishnan Comments: [X](hudi) Suneel Marthi Comments: Good adaption of the Apache Way by PPMC. IPMC/Shepherd notes: -------------------- Iceberg Iceberg is a table format for large, slow-moving tabular data. Iceberg has been incubating since 2018-11-16. Three most important issues to address in the move towards graduation: 1. Update build for Apache release, add LICENSE/NOTICE to Jars. 2. Make the first Apache release. (https://github.com/apache/incubator-iceberg/milestone/1) 3. Grow the Iceberg community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * No issues that require attention. How has the community developed since the last report? * The community has continued to receive new contributors * Several contributors are reliable helping review pull requests. Because of these review contributions and the small number of committers, the community voted to relax the RTC requirements and allow committers to push their own changes if the community has reviewed the PR. This helps develop reviewers and gets changes in faster. The vote also set reasonable limits for this practice: PRs must be up for at least 2 days and this is only for the first year, while we are working with a small set of committers. How has the project developed since the last report? * Podling name search concluded that Iceberg is a suitable name. (See PODLINGNAMESEARCH-163) * The community voted to accept a large PR with a Python implementation. * Contributors are fixing important predicate push-down issues, including case sensitivity, filtering on nested types, missing file metrics, etc. * Contributors added support for plugging in file stream encryption. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup (name clearance approval pending) [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: None yet When were the last committers or PPMC members elected? None yet Have your mentors been helpful and responsive 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](iceberg) Ryan Blue Comments: I wrote the first pass of the report. [ ](iceberg) Julien Le Dem Comments: [X](iceberg) Owen O'Malley Comments: (Approval copied from +1 on dev list) [ ](iceberg) James Taylor Comments: [ ](iceberg) Carl Steinbach Comments: -------------------- IoTDB IoTDB is a data store for managing large amounts of time series data such as timestamped data from IoT sensors in industrial applications. IoTDB has been incubating since 2018-11-18. Three most important issues to address in the move towards graduation: 1. Release the first version; 2. refactor codes which are hard to understand for new developers, and supply more design documents to help new developers. 3. Attract more contributors; 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? - 4 new contributors joined the community: review and modify the English documents, add Apache Calcite adaptor demo, and discuss in the mailing list. - Mailing list: -- dev@mailing list: 59 emails are sent, and can be divided into 18 threads (Apache Jenkins Pipeline notifications are exclude) -- reviews@mailing list: more than 420 mails are sent, for code review and new branch creation notifications. How has the project developed since the last report? - 48 PR are proposed totally, and 42 PR are merged. - 16 authors have pushed 50 commits to master and 110 commits to all branches. - 31 issues (bugs, and feature requests) are logged on JIRA, 15 of them are resolved. - Dockerfile is created, which can attract more users to try IoTDB. How would you assess the podling's maturity? - The project is growing. Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: - N/A When were the last committers or PPMC members elected? - 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. - very Helpful. Signed-off-by: [X](iotdb) Justin Mclean Comments: More effort needs to be made to have conversations on list. [X](iotdb) Christofer Dutz Comments: [](iotdb) Willem Ning Jiang Comments: [X](iotdb) Kevin McGrail Comments: IPMC/Shepherd notes: Christofer Dutz: Allmost no discussions on list, requested the podling to move discussions to the dev list. Dave Fisher: It looks like Christofer's request is successful so far. No discussion yet if any contributors are looking like good committers/PPMC members. -------------------- Marvin-AI Marvin-AI is an open-source artificial intelligence (AI) platform that helps data scientists, prototype and productionalize complex solutions with a scalable, low-latency, language-agnostic, and standardized architecture while simplifies the process of exploration and modeling. Marvin-AI has been incubating since 2018-08-21. Three most important issues to address in the move towards graduation: 1.Move development infrastructure to Apache 2.Build Community 3.Build Releases 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? * The project began to receive help from community members. * The community started discussing new releases. How has the project developed since the last report? * New improvements in documentation and official website * Some improvements for a new release 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. * At least two of the mentors are sometimes active. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? * N/A Signed-off-by: [ ](marvin-ai) Jim Jagielski Comments: [x](marvin-ai) Luciano Resende Comments: What are the missing items around `1.Move development infrastructure to Apache` [ ](marvin-ai) William Colen Comments: IPMC/Shepherd notes: -------------------- Myriad Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on the same cluster and allows dynamic resource allocations across both Hadoop and other applications running on the same physical data center infrastructure. Myriad has been incubating since 2015-03-01. Three most important issues to address in the move towards graduation: 1. MYRIAD-283: Prepare for 0.3.0 release (Voting right now) 2. MYRIAD-280: Improve overall stability 3. MYRIAD-279: Reworking a new UI design Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We need new mentors, we have only one active mentor right now. We have to increase the community and we have to increase the number of mentors too. The PPMC number is a problem too, we are only two PPMCs/committers, so we have problems with the minimum number of votes for consensus. https://www.mail-archive.com/dev@myriad.incubator.apache.org/msg02661.html How has the community developed since the last report? An increment of activity and newcomers with a desire to contribute, in particular in the scope of the user interface, and at least three new users ready for contributing. How has the project developed since the last report? After a few years of inactivity the project is slowly getting activity, as a matter of fact we are right now in the voting process of a new release apache-myriad-0.3.0-incubating-rc1. 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 [X] Other: Almost ready for a new release, vote pending right now. Date of last release: The 0.2.0 release was issued on Jun 29, 2016. The .3 release is planned for the next days, if we have any help for unlocking the release. When were the last committers or PPMC members elected? 2018-05-22 New committer/PMC member Juan P. Gilaberte. 2018-03-28 New committer/PMC member Javi Roman. 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. We have only one active mentor, so we have new mentors as soon as possible, this is one of the our main issues, we need help. Signed-off-by: [ ](myriad) Benjamin Hindman Comments: [X](myriad) Ted Dunning Comments: IPMC/Shepherd notes: -------------------- Nemo Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Nemo has been incubating since 2018-02-04. Three most important issues to address in the move towards graduation: 1. Grow the community (committers, contributors, users) 2. More releases 3. Add and improve features 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? * Committers actively involved in sending PRs and doing code reviews * Engaged with the Beam community to register Nemo as an official Beam runner * Started to attract new contributors * Ran a Nemo tutorial in an open-source project venue How has the project developed since the last report? * Donated code to ASF * Released 0.1 (the first release!) * Committer’s guide added * Added Nemo Web UI * Created an official Beam runner * Improved metric collection and storage * Improved skew handling pass * Refactored runtime pass and IR DAG * Fixed skew handling bugs 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: 2018-12-31 release 0.1 When were the last committers or PPMC members elected? None yet. 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. The community has been receiving much help from our mentors! Signed-off-by: [X](nemo) Davor Bonaci Comments: Good progress; nothing to add. Focus on community building needed going forward. [X](nemo) Hyunsik Choi Comments: [X](nemo) Byung-Gon Chun Comments: [ ](nemo) Jean-Baptiste Onofre Comments: [X](nemo) Markus Weimer Comments: IPMC/Shepherd notes: -------------------- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Optimise Omid for the integration with Apache Phoenix. 2. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 3. Get positive feedback from other projects currently in Apache. 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? Integration with Apache Phoenix was over, we are currently working on optimisation. How has the project developed since the last report? 1. Release 1.0.0 was published and includes all the Phoenix required features. 2. The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. 3. We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-12-24 When were the last committers or PPMC members elected? 2018-09-25 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 mentors are extremely responsive and helpful. Signed-off-by: [X](omid) Alan Gates Comments: I don't see any of the issues listed under "Three most important issues to address in the move towards graduation" as blockers for graduation. The community has done multiple releases and added one committer. Development is slow but consistent. I do not believe the community has done a name search yet to make sure Omid is acceptable. AFAIK that is the only blocker for graduation. I've given this feedback to the community. [X](omid) James Taylor Comments: IPMC/Shepherd notes: -------------------- OpenWhisk OpenWhisk is an open source, distributed Serverless computing platform able to execute application logic (Actions) in response to events (Triggers) from external sources (Feeds) or HTTP requests governed by conditional logic (Rules). It provides a programming environment supported by a REST API-based Command Line Interface (CLI) along with tooling to support packaging and catalog services. The OpenWhisk platform components are packaged as Docker containers and can be deployed directly to Docker or deployed using Container Frameworks such as Mesos, Kubernetes, Compose, and YARN. OpenWhisk has been incubating since 2016-11-23. Three most important issues to address in the move towards graduation: 1. Close legal transfer of trademark on "OpenWhisk" name and logo to ASF from IBM. 2. Complete project maturity model assessment and formal graduation process. 3. Improve release automation. A comprehensive OpenWhisk release includes over 20 sub-components, each drawn from its own github repo and each packaged as a separately downloadable source release. a. Release process/automation/documentation are here https://github.com/apache/incubator-openwhisk-release. b. During incubation, we have made over a dozen conforming Apache releases of sub-components. We have developed reasonable automation for releasing a group of sub-components, but there is a need to further define and automate the process of making a unified release of a coherent set of released sub-components. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; hopefully this will happen at the March ASF Board meeting. 2. The podling was down to one active mentor for several months, which has made getting the required minimum of 3 positive IPMC votes for each released component a significant challenge. This had a negative effect on project velocity and PPMC morale. At the time of this report, the IPMC is taking action by soliciting additional mentors to help the project finish out its incubation. How has the community developed since the last report? + dev mailing list activity: + We have implemented an automated process to post a daily archive of the OpenWhisk Team Slack to our dev mailing list. + Increased use of the dev list for technical discussion, especially around releasing sub-components and ensuring awareness of significant PRs before merging. + incubator-openwhisk Github stars: 3,825 (+168 since last report) + incubator-openwhisk GitHub forks: 738 (+46 since last report) + Slack community: + 1,159 members (+87 from last report). Very active in most channels from both end users or the project and contributors + To-date: 141,783 messages sent across all channels (+15,501 since last report) + Analytics: https://openwhisk-team.slack.com/admin/stats + The bi-weekly Zoom "Technical Interchange" continues to be well received and attended. Complete videos posted to OW YouTube channel and detailed notes to our CWIKI. + New Contributors + 13 new ICLAs received (including some that were missed in the previous two status reports): 1. Sam Baxter 6/11/18 2. Emanuel Russo 8/6/18 3. Prabhash Rathnayake 10/2/18 4. Shawn Black 10/2/18 5. Moritz Raho 10/4/18 6. Duy Nguyen 10/4/18 7. Sam Hjelmfelt 11/21/18 8. Marc Schwind 1/28/19 9. Avi Weit 2/5/19 10. Lars Andersson 2/8/19 11. Maciej Małecki 2/26/19 12. Somaya Jamil 2/27/19 13. Erez Hadad 3/1/19 + 5 new people Joined Community Technical Interchange calls and introduced themselves: 1. Thomas Peikert: grad. student using OW, looking to make contributions in future 2. Erez Hadad (IBM Research), working on Serverless, incl. OW and knative, etc. 3. Rahul (Adobe) - working on some depl. strat. starting a CWIKI post... 4. Lavanya (Adobe) 5. Manoj (Adobe) - SW quality engineer How has the project developed since the last report? 1. There has been a focus on clearing the backlog of PRs and issues across all our github repos, motivated by a desire to make a unified release of all the OpenWhisk system sub-components. There is still significant work needed to clear out stale issues in the core repository, but the PR backlog mentioned in multiple previous reports has been rectified. 2. Project technical highlights include (a) the addition of a .NET runtime component, (b) merged support for concurrent activation processing, (c) merged support for a "lean" system configuration suited for resource-limited hosts, (d) added the capability of deploying OpenWhisk on Apache YARN, (e) the unification of the `wskdeploy` and `wsk` CLIs into a single `wsk` cli. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: Apache OpenWhisk Composer v0.10.0-incubating (2/27/19) Links to latest releases of all components can be found here: https://openwhisk.apache.org/downloads.html When were the last committers or PPMC members elected? New Committers+PPMC: 1. Olivier Tardieu (2/27/19) New Committers: 1. Michele Sciabarra (1/8/19) 2. Rob Allen (1/8/19) 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 sole remaining mentor has been helpful and responsive, but release voting has been challenging. The recent efforts of the IPMC to identify projects needing additional mentors and should allow us to regain our desired release velocity. Signed-off-by: [ ] (openwhisk) Bertrand Delacretaz 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 issues to address in the move towards graduation: 1. Improving documentation 2. Cutting a release 3. Building community contribution 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 added some new features and improved documentations. - Adding parquet record reader https://github.com/apache/incubator-pinot/pull/3852 - Adding an aggregation function for population standard variance https://github.com/apache/incubator-pinot/pull/3850 - Improving documentation https://github.com/apache/incubator-pinot/pull/3826 How has the project developed since the last report? - We finished to update LICENSE/NOTICE files for both source and binary releases. (this item was ongoing for the last report) - We have updated pom files for release preparation. (adding rat, maven-release-plugin, maven-checksum-plugin...etc) - We are currently in the voting process for the first Apache release candidate. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [X] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: N/A When were the last committers or PPMC members elected? We haven't had a change in committers or PPMC since our incubation. 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 very helpful and have responded in a timely manner. They also helped us on release verification for a community vote. Signed-off-by: [X](pinot) Kishore Gopalakrishna Comments: [ ](pinot) Jim Jagielski Comments: [ ](pinot) Roman Shaposhnik Comments: [X](pinot) Olivier Lamy Comments: [X](pinot) Felix Cheung Comments: Congrats on vote passing on your first release IPMC/Shepherd notes: -------------------- Pony Mail Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms. Pony Mail has been incubating since 2016-05-27. Three most important issues to address in the move towards graduation: 1. Grow community 2. Lower bar for participation 3. Get some more releases out 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? - No noteworthy development. How has the project developed since the last report? - Nothing noteworthy here either 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: 2018-02-5 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. Signed-off-by: [X](ponymail) John D. Ament Comments: Project is looking to start picking up traction again which is good. Hopefully it can sustain. [ ](ponymail) Sharan Foga Comments: IPMC/Shepherd notes: -------------------- SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Revitalize the project by resuming development 2. Enlarge the user base and contributing community 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? * Mailing list activity (September 2018 - November 2018): * @dev: 8 messages How has the project developed since the last report? * 1 new PRs created * Working on code for supporting Apache Heron How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2016-09-30 When were the last committers or PPMC members elected? January 2018 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, the mentors have been helpful and responsive. Signed-off-by: [X](samoa) Alan Gates Comments: [ ](samoa) Ashutosh Chauhan Comments: IPMC/Shepherd notes: -------------------- ShardingSphere Sharding-Sphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. ShardingSphere has been incubating since 2018-11-10. Three most important issues to address in the move towards graduation: 1. Prepare for the first ASF release. 2. Fix bugs and develop new features. 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? Not bad. Two committers and PPMC members have been officially invited to the project. The community participation has been active, with multiple problems brought out and solved. How has the project developed since the last report? Two members have been officially invited to the PPMC. We are closer to the first Apache release. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [X] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: Not finished for the 1st apache release yet. When were the last committers or PPMC members elected? 28 Jan 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. Signed-off-by: [x](shardingsphere) Craig L Russell Comments: [ ](shardingsphere) Benjamin Hindman Comments: [X](shardingsphere) Willem Ning Jiang Comments: ShardingSphere already made a first step to get new committer onboard, it's now working its first Apache release. [X](shardingsphere) Von Gosling Comments: IPMC/Shepherd notes: -------------------- SINGA SINGA is a distributed deep learning platform. SINGA has been incubating since 2015-03-17. Three most important issues to address in the move towards graduation: 1. Release version 2.0 which was scheduled in Dec 2018 but has been delayed 2. Start the graduation process in about 2-3 month 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? We have a new PPMC member, Moaz, who was a committer. We have a new committer, Wanqi Xue. Number of emails from Sep to Dec. 56 Dec 2018 22 Jan 2019 22 Feb 2019 15 Mar 2019 How has the project developed since the last report? We have done the name search for "Apache Singa" We enhanced Singa's performance on Intel CPU by calling Intel's MKLDNN library. We have updated the website and documentation to include the instructions for "How to prepare a release". How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-06-06 When were the last committers or PPMC members elected? 2018-12-21 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](singa) Alan Gates Comments: [X](singa) Ted Dunning Comments: [ ](singa) Thejas Nair Comments: IPMC/Shepherd notes: Alan Gates: One key question for the project is to determine how dependent the project is on a single group of contributors. This is a key community resilience factor and should be addressed by the project. This isn't a graduation preventer ... it is, however, very important to solve. -------------------- SkyWalking Skywalking is an APM (application performance monitor), especially for microservice, Cloud Native and container-based architecture systems. Also known as a distributed tracing system. It provides an automatic way to instrument applications: no need to change any of the source code of the target application; and an collector with an very high efficiency streaming module. SkyWalking has been incubating since 2017-12-08. Three most important issues to address in the move towards graduation: 1. IP clearance. [RESOLVED] 3. First ASF release. (SkyWalking 5.0) [RESOLVED] 3. Further ASF culture and processes. [RESOLVED] 4. 5.x releases are stable for product, and have 5 open end users, at least. [RESOLVED] 5. Support multiple languages agents/SDKs. [RESOLVED] 6. Integration with other pupolar OSS systems. Zipkin data format supported. [RESOLVED] 7. Clear Brand issues with other ecosystem projects. [RESOLVED] Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Have six Apache releases already. 5.0.0-alpha, 5.0.0-beta, 5.0.0-beta2, 5.0.0-RC2, 5.0.0-GA, 6.0.0-alpha, 6.0.0-beta, 6.0.0-GA There are several related projects and GitHub org in SkyWalking ecosystem, before or during project joined the ASF incubator, such as .net, node.js and php agents, they were using skywalking-* prefix in project name and releases, which may cause brand issue. We have fixed these. All skywalking-* have been renamed to skyapm-*, old releases with skywalking- removed(maybe not necessary). Old existing GitHub orgs, including OpenSkywalking, OpenSkywalkingTest, SkywalkingContrib, have been renamed to SkyAPM, SkyAPMTest or removed(SkywalkingContrib). Another brand related issue is `skywalking` in DockerHub, including some binary releases, which have been removed and moved to ASF Infra - https://hub.docker.com/r/apache/skywalking-base - https://hub.docker.com/r/apache/skywalking-oap-server - https://hub.docker.com/r/apache/skywalking-ui All of these are only including the approved releases. All known brand issues have been addressed and solved. Be good for the graduation. How has the community developed since the last report? 1. SkyWalking is working with Envoy community, trying to contribute a new service mesh probe. 2. Lang Li, Yixiong and Jinlin Fu Cao have been voted and joined as committer. 3. Yao Wang and Jian Tan have been voted and joined as PPMC 4. There are 92 people to contribute codes to our main repo. 18 more than the last report. 5 Over 60 companies have confirmed they are using SkyWalking through issue report, our powered-by page or through our ecosystem pages. How has the project developed since the last report? There has been over 100 commits by more than 27 contributors in the three months. In 6.1.0(in developing) release milestones, there are 81 issues and pull requests solved. SkyWalking 6.0.0-GA is suitable for production. In 6.0.0-GA release milestones, there are 134 issues and pull requests solved. In 6.0.0-beta release milestones, there are 153 issues and pull requests solved. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release [x] Community building [x] Nearing graduation [ ] Other: Date of last release: Jan 29th, 2019 6.0.0-GA When were the last committers or PPMC members elected? Jan 29th, 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. Signed-off-by: [ ](skywalking) Luke Han Comments: [X](skywalking) Willem Ning Jiang Comments: I think skywalking is in a good sharp of graduation by getting more and more developer involved. [X](skywalking) Mick Semb Wever Comments: Updated the "Three most important issues to address in the move towards graduation" section, as it had been misread, and the list had become an accumulation of resolved items. [X](skywalking) Ignasi Barrera Comments: IPMC/Shepherd notes: -------------------- Superset Superset is an enterprise-ready web application for data exploration, data visualization and dashboarding. Superset has been incubating since 2017-05-21. Three most important issues to address in the move towards graduation: 1. Plan and execute our first Apache release. Since the last report, we have removed all questionable third party code from the repo, which was a major blocker for the source code release, and are ready to begin the work on the first code release. 2. Address remaining project operations issues. See below. Any issues that the Incubator PMC (IPMS) or ASF Board wish/need to be aware of? For project operations, we have made the following progress and need the following support: * Held a meeting on December 13 with Mentors, PMC, and Committers to learn more about the Apache way and clarified ways of contributing and collaborating that would uphold the principles. The notes from this meeting were shared on the dev list. * No more unapproved releases. We are working towards our first official release; see above. * Trademark: We continue to have challenges here. Our attempts to complete this task has been unsuccessful and we would appreciate more specific guidance. How has the community developed since the last report? * Organic growth of our Github contributors (306->343), forks (3974->4300), watchers (1157->1170) and stars (22,097->23,326) How has the project developed since the last report? * Added Christine Chambers as a new committer * In general, there has been a healthy, constant flow of bug fixes, quality improvements and new features. Please see project’s commit log on Github for more details. Some highlights: New features * Refined layout of SQL Lab. * Added back-end for tagging system, for organization and discovery of content. * Added support for customization of deployments: feature flags, custom logo. * Decoupled visualizations as plugins that can be added/removed. * Omnibar on dashboard page, to enable users to easily switch between dashboards. * New deck.gl polygon visualization type that accommodates aggregated spatial types (zip, geohash, etc.) Bug fixes, code quality and housekeeping * All files now include ASF header. * A lighter, more accurate events logger for user interactivities with timing. * More translations were added. * Sped up build time and tests on Travis CI. * Fixed vulnerabilities from dependencies. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [X] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: No official release yet since being voted into Apache Incubation. (Planning for the first Apache release in Q2, 2019) When were the last committers or PPMC members elected? * Christine Chambers - Committer (2019-01-06) Signed-off-by: [ ](superset) Ashutosh Chauhan Comments: [ ](superset) Luke Han Comments: [X](superset) Alan Gates Comments: Sent email to dev list following up on the request for help with trademark issues. I have been impressed over the last 3 months with the renewed effort this community is putting into learning and adopting the Apache Way. 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 issues to address in the move towards graduation: 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? * elected 2 new committers and onboarded them * discussions/we benefited from the Gitbox migration as it makes contribution much easier How has the project developed since the last report? * frequent bugreports and discussions via Jira/mailing list * new external contributions (code improvements, Jira issues, OSGi bugfixes) * homepage overhaul 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. * As the project needs a wider audience, maybe mentors with interest in Tamaya would be welcome. * Current mentors did not sign-off the report in February and did not react on mails :-( Signed-off-by: [X](tamaya) John D. Ament Comments: Podling is continuing to struggle. I strongly disagree with the notion that this project is ready to graduate or nearing readiness. It has not executed a release in 2 years, Development activity has definitely increased in the past few months, and with the addition of 2 new committers may see more sustained progress, but we need to ensure that this vitality continues on. [ ](tamaya) David Blevins Comments: IPMC/Shepherd notes: -------------------- Tephra Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Two most important issues to address in the move towards graduation: 1. Improve community engagement 2. Increase adoption 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? - 1 new JIRA filed since the last report - 1 new bug created since the last report How has the project developed since the last report? - Working on 0.16.0-incubating release How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-09-04 When were the last committers or PPMC members elected? - None since coming to incubation 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 helpful and responsive Signed-off-by: [X](tephra) Alan Gates Comments: [X](tephra) James Taylor 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. Total number of posts in February were 112 and in March so far (5 March) already 50. Total number of subscribers is 25. How has the project developed since the last report? - This is our first report - The scope of the project deliverables, core procedures, details regarding website, and code management are under discussion. 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: Off to a good start. [x](training) Craig Russell Comments: [X](training) Christofer Dutz Comments: [X](training) Lars Francke Comments: IPMC/Shepherd notes: -------------------- Zipkin Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. Zipkin has been incubating since 2018-08-29. Three most important issues to address in the move towards graduation: 1. Finalize the first release of the Apache Zipkin (incubating) for Apache Karaf 2. Migrate other repositories to ASF Github organization 3. Work towards releasing more Apache Zipkin (incubating) components once migration is completed Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The first release was very challenging. The Zipkin community found The Apache Incubator established practices to be somewhat hostile and unwelcoming for the newcomers. The community felt frustration and demotivation to the the point that the issues had been raised for the attention of the board. How has the community developed since the last report? A lot of work has been done to get the first release out, by all means a great achievement. The team and community is looking forward to see the positive changes within Apache Incubator with respect to the feedback provided. How has the project developed since the last report? The team has mastered the Apache CI/CD infrastructure and was able to quickly do the switch over for the first migrated repository. Also, the team better understands how the incubation process works and what to watch for. 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-26 When were the last committers or PPMC members elected? 2019-02-26 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](zipkin) Michael Semb Wever Comments: [X](zipkin) John D. Ament Comments: [X](zipkin) Willem Ning Jiang Comments: [X](zipkin) Andriy Redko Comments: [x](zipkin) Sheng Wu Comments: IPMC/Shepherd notes: -------------------- ----------------------------------------- Attachment AF: Report from the Apache Jackrabbit Project [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. We made our 5th major release of Oak (1.10) in January. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. We are currently discussing a new release strategy for Oak. The aim is to facilitate managing our many branches, releasing of tools and aligning with Oracle's changes in their release and support model for Java. See https://s.apache.org/oM0w, https://s.apache.org/0UKO and https://s.apache.org/tk9u on oak-dev for details. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring the features in for Oak 1.10. ## PMC changes: - Currently 52 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Woonsan Ko on Tue Sep 25 2018 ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months - Last committer addition was Woonsan Ko at Tue Sep 25 2018 ## Releases: - 1.10.0 was released on Fri Jan 11 2019 - 1.10.1 was released on Mon Feb 25 2019 - 1.4.24 was released on Tue Jan 08 2019 - 1.6.16 was released on Fri Jan 11 2019 - 1.8.10 was released on Mon Dec 17 2018 - 1.8.11 was released on Mon Jan 14 2019 - 1.9.13 was released on Mon Dec 10 2018 - 2.10.9 was released on Mon Jan 07 2019 - 2.19.0 was released on Fri Dec 07 2018 - 2.19.1 was released on Mon Feb 04 2019 - 2.8.10 was released on Thu Feb 28 2019 ## JIRA activity: - 193 JIRA tickets created in the last 3 months - 183 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AG: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AH: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: - Apache Karaf provides a modern and polymorphic applications runtime, multi-purpose (microservices, cloud, IoT, OSGi, etc). ## Issues: - There are no issues requiring board attention at this time ## Activity: - The kloud (karaf for the cloud) initiative has been launched. The first goal is to improve the tooling to easily start with Karaf for both developers and devops. - Karaf Vineyard moved forward but not as fast as planned. The donation proposal should happen soon. - Karaf 4.3.x branch has started, starting to upgrade to OSGi R7 specification and implement the "kloud initiative" features and improvements. ## Health report: - More interaction with other projects have been built. Especially, we are helping the jclouds community to upgrade to latest Karaf release. - We started an effort to have regular cadence in Karaf releases. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Francois Papon on Thu Nov 29 2018 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Francois Papon at Sat May 19 2018 ## Releases: - 4.2.2 was released on Thu Dec 20 2018 - 4.2.3 was released on Mon Feb 11 2019 - Cellar 4.1.3 was released on Wed Feb 27 2019 ## Mailing list activity: - We can see an increase on the dev mailing list related to the kloud initiative mostly. The user mailing list activity is stable. - dev@karaf.apache.org: - 182 subscribers (down -4 in the last 3 months): - 301 emails sent to list (146 in previous quarter) - issues@karaf.apache.org: - 42 subscribers (down -1 in the last 3 months): - 1492 emails sent to list (1138 in previous quarter) - user@karaf.apache.org: - 363 subscribers (up 2 in the last 3 months): - 506 emails sent to list (561 in previous quarter) ## JIRA activity: - 149 JIRA tickets created in the last 3 months - 153 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AI: 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: - 2018/12/20 Chunen Ni presented Apache Kylin on Flink Forward 2018 at Beijing - 2019/2/23 Apache Kylin meetup @ Shanghai, Gang Ma, Dong Li, and two users (China Unionpay and Ctrip) presented Kylin new features and use cases. ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Zhong Yanghong on Thu Aug 02 2018 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Chunen Ni at Sat Dec 01 2018 ## Releases: - 2.6.0 was released on Sat Jan 12 2019 - 2.6.1 was released on Fri Mar 08 2019 ## Mailing list activity: Due to Chinese New Year holiday, there's impact for the mailing list activity. It's coming back to normal after the CNY. - dev@kylin.apache.org: - 467 subscribers (up 16 in the last 3 months): - 539 emails sent to list (965 in previous quarter) - issues@kylin.apache.org: - 104 subscribers (up 11 in the last 3 months): - 2373 emails sent to list (2708 in previous quarter) - user@kylin.apache.org: - 422 subscribers (up 18 in the last 3 months): - 194 emails sent to list (447 in previous quarter) ## JIRA activity: - 152 JIRA tickets created in the last 3 months - 123 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache Labs Project [Danny Angus] ### Description Apache Labs exists to incubate small and emerging projects from ASF committers. ## Issues: There are no issues requiring board attention at this time. ## Activity: One active lab Turbulence. ## Health report: Labs remains quiet, but not inactive. Lack of volunteer energy limits progress. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Simone Tripodi on Tue Jun 14 2011 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Juan P. Gilaberte at Wed May 30 2018 ## Releases: - Per charter Labs does not make releases ----------------------------------------- Attachment AK: Report from the Apache Lucene Project [Cassandra Targett] ## Description: - Lucene Core is a search-engine toolkit - Solr is a search server built on top of Lucene Core ## Issues: - There are no new issues requiring board attention at this time. ## Activity: We are actively voting to release Lucene and Solr 8.0. PyLucene 7.7.1 is also being voted on for release. Since our last report, we released Lucene and Solr 7.6, 7.7 and 7.7.1, and PyLucene 7.6.0. 7.7 was released as the final minor release of the 7.x line, in preparation for releasing 8.0. Lucene 7.7 had some speed improvements for merging segments with points and support for Unicode 9.0, while Solr 7.7 added a login screen for the Admin UI (when auth is configured) and the ability to configure a whitelist for distributed queries. 7.7.1 was a patch release to fix two bugs in Solr deemed critical: one that impacted 7.6 and 7.7 and another that impacted 7.7 only. No changes were made in the 7.7.1 release for Lucene. ## PMC changes: - Jason Gerlowski added on February 20, 2019 - Ignacio Vera added on March 3, 2019 - We invited another committer to join the PMC, but he declined our invitation for personal reasons. - Currently 52 PMC members. ## Committer base changes: - No new Committers since last report - Currently 75 committers. ## Releases: - Lucene/Solr 7.6.0 was released December 14, 2018 - Lucene/Solr 7.7.0 was released February 11, 2019 - Lucene/Solr 7.7.1 was released February 28, 2019 - PyLucene 7.6.0 was released on January 11, 2019 ----------------------------------------- Attachment AL: Report from the Apache Lucene.Net Project [Shad Storhaug] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == We had stalled in the second half of 2018, with several board members attempting to reach out to figure out status, and several board reports missing, there were several calls and questions regarding moving to the attic. In January 2019 an email to the dev mailing list generated activity, after the private pmc mailing list seemed to have gone radio silent. There has been vocal support (reported last month), and we have continued to make some progress: * New Website went live: http://lucenenet.apache.org/ * The team is re-looking at our CI options (previously TeamCity, may continue with that) * We're looking at stabiling the current 4.8.0-beta0005 and cutting it as a release, and then moving on. Issues: * PMC Still seems a little stalled as there isn't much activity at that level * As previously mentioned we needed a PMC roll call, that was not yet done. == Releases == * Last Release 3.0.3 - Oct 2012 * Working toward 4.8.0 - Currently beta0005, which has been out for some time == People == * Last PMC Member Added, Paul Irwin, October 2013 * Last committer added Sept 2016, Shad Storhaug (nightowl888) * PMC Chair rotated 20 June 2018 to Shad Storhaug (nightowl888) == Statistics == As of 2019.02.01 Metric are as follows: Release 3.0.3 * Lucene.Net 3.0.3: 1,894,662 (Feb 2019: 1,757,023) * Lucene.Net.Contrib 3.0.3: 403,432 (Feb 2019: 370229) * Lucene.Net Contrib Spatial: 27,623 (Feb 2019: 26483) * Lucene.Net Contrib Spatial.NTS: 5,836 (Feb 2019: 5697) Beta 4.8.0-beta00005 (Published 10/24/2017) * Lucene.Net: 83132 * Lucene.Net.Analysis.Common: 74917 * Lucene.Net.Analysis.Kuromoji: 2939 * Lucene.Net.Analysis.Phonetic: 757 * Lucene.Net.Analysis.SmartCn: 268 * Lucene.Net.Analysis.Stempel: 561 * Lucene.Net.Benchmark: 201 * Lucene.Net.Classification: 490 * Lucene.Net.Codecs: 1502 * Lucene.Net.Expressions: 3338 * Lucene.Net.Facet: 3768 * Lucene.Net.Grouping: 4388 * Lucene.Net.Highlighter: 2545 * Lucene.Net.ICU: 373 * Lucene.Net.Join: 3980 * Lucene.Net.Memory: 3865 * Lucene.Net.Misc: 3281 * Lucene.Net.Queries: 64592 * Lucene.Net.QueryParser: 60334 * Lucene.Net.Replicator: 212 * Lucene.Net.Sandbox: 66705 * Lucene.Net.Spatial: 1620 * Lucene.Net.Suggest: 2654 ----------------------------------------- Attachment AM: 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: The project relies on ReviewBoard almost exclusively for doing reviews. We've recently learnt that contributors cannot signup to ReviewBoard anymore because of LDAP integration (which only committers have access to). This is a big problem for us and we would like to request that contributors to the project be given access to signup and use ReviewBoard. We've already engaged ASF Infra to figure out a solution but would also ask for help from the Board to resolve it expediently. Activity: * MesosCon 2018 was held at SF (Nov 5th-7th) and was a success. * Project migrated to the gitbox.apache. repository. * We simplified the process for a contributor to become a committer on the project. We are optimistic this will reduce the burden of new contributors. * 3 new committers were added to the project and several minor and patch releases have been cut since the last board report.orgnew * The project continues to see new bug reports, bug fixes, features, reviews and releases. The mailing lists, slack and IRC channels are also very much active with healthy discussions. Multiple active working groups (containerization, performance, API, community). New committers: Meng Zhu (2018-10-20), Andrei Budnik (2019-02-26) and Benno Evers (2019-01-31) have been voted in as new committers / PMC members. Releases (recent): 1.4.3 was released on Fri Feb 22 2019 1.5.2 was released on Thu Jan 24 2019 1.6.2 was released on Mon Feb 25 2019 1.7.2 was released on Fri Feb 22 2019 JIRA Activity (last 3 months): 177 Issues Created 212 Issues Resolved ----------------------------------------- Attachment AN: Report from the Apache Mnemonic Project [Gang Wang] Description: Apache Mnemonic is an open-source Java library for durable object-oriented programming on hybrid storage-class memory(e.g. NVM) space. it comes up with durable object model (DOM) and durable computing model(DCM) and takes full advantages of storage-class memory to simplify the code complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing next generation computing platform. Mnemonic makes the storing and transmitting of massive linked objects graphs simpler and more efficient. The performance tuning could also be mostly converged to a single point of tuning place if based on Mnemonic to process and analyze linked objects. The programmer is able to focus on the durable object oriented business logic instead of worrying about how to normalize/join, serDe(un)marshal, cache and storing their linked business objects with arbitrary complexity. Issues: There are no board-level issues at the moment. Activity: In this period of reporting, 18 of tickets has been created and resolved, basically, we have improved our project, completed the documenting, upgraded the dependencies, added more test cases and proceeded to support new PMDK memory service. Our community has welcomed gsoc2019 participant to join our project, we guided gsoc2019 participant to get insiged into our project structure, memory service to refer to for their ticket and which knowledges need to learn to fulfill the ticket. Our contributor has completed a test case for old API of Hadoop to verify the functionalities durable object model also works on that API Recently, There are no new version Mnemonic released, we continue to work on v0.13 that might be released before next report. We are also voting a new committer to join our project. Health Report: Basically unchanged since the last report. Users are generally quiet in public but development continues. PMC Changes: - Currently 12 PMC members. - no new PMC member added since Jun. 2018. Committer Base Changes: - Currently 13 committers. - No new committer added since Jun. 2018. Releases: - Last release was v0.12.0 on Sep. 04 2018 - Still active development on next major version (0.13) JIRA Activity (Since Sep. 2018): - 18 JIRA tickets created since the last report - Also 13 JIRA tickets closed/resolved this period ----------------------------------------- Attachment AO: Report from the Apache Mynewt Project [Justin Mclean] ## Description: Mynewt is a real-time operating system for constrained embedded systems like wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS architectures. ## Issues: None. ## Activity: - Ongoing preparation for upcoming Release 1.6.0 around mid-March 2019 - Testing and bug fixes completed to pass Bluetooth SIG qualification of the NimBLE controller stack, paperwork started - Community work in serval areas including test utilities, low power support in LoRa, Cortex M33 support, Power management support for bus devices, log level manipulation flexibility, porting of NimBLE stack to Linux and more. ## Health report: - PMC and committers are active - Users questions and contributor's pull requests are quickly dealt with - Promotion of Apache Mynewt at Embedded World Nuremberg, Feb 2019 ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Aditi Hilbert on Wed Jun 21 2017 ## Committer base changes: - Currently 30 committers - Two new committers added or voted on since last report - Last committer addition was on 1/16/2019 - Martin Turon and Ben McCrea ## Releases: - 1.6.0 slated for release mid-March, 2019 - Last release was 1.5.0 on Nov 5, 2018 ## Mailing list activity: - Mailing list activity seeing new users and responders to questions asked (esp. questions from newcomers) - Mailing list exchanges are mostly around test facilities, LoRa, BLE, hardware support and performance - Mailing list average activity (# of topics, messages, people responding) dropped by about 20% compared to previous quarter. - Slack activity up significantly and weekly/daily active users up 10% from last period (from 415 to 458 active users) ## GitHub Issues activity: - Issue types seen include change/feature requests, bug reports, contributions/PR, Q&A ----------------------------------------- Attachment AP: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source enterprise automation software project ## Issues: There are no issues requiring board attention at this time ## Highlights: - Trademarks: we do not have trademark related concerns at the moment and our backlog of non-compliant parties is mostly empty [1] - Releases: no new releases have been published in the last quarter but we will probably release 16.11.06 in the next few weeks; the stabilization of the new release branches is ongoing but we do not have a publication date, yet; however the 17.12 branch is quite stable and the community may release 17.12.01 sometime soon; we have also created, at the end of December, the new stabilization branch, named 18.12 - source code repository: recently, in the dev list, it was proposed [3] to switch the project's repository from SVN to Git; the proposal has triggered a lot of community feedback, mostly everyone in favor of moving to Git; we expect this switch is something the community will work upon the next months - Various bug fixes and enhancements have been contributed and committed to the trunk: a summary of the main changes is available as usual in the project's blog [4] - More details about the community activities are published in the official blog [4], on Twitter [5] and other social media [6]. ## Health report: a new committer has joined the project in the last quarter and we have other candidates in our watchlist; as usual the community is actively involved in improving the trunk, fixing vulnerabilities, stabilizing the release branches and in various discussions and support requests posted mostly in the mailing list and in our issue tracker ## PMC changes: - No new PMC members added in the last 3 months - Last PMC addition was Paul Foxworthy on Mon Mar 19 2018 - Currently 20 PMC members. ## Committer base changes: - Mathieu Lirzin was added as a committer on Fri Feb 22 2019 - Currently 47 committers. ## Releases: - No new releases published in the last 3 months - Last release was 16.11.05 on Tue Oct 02 2018 ## Mailing list activity: There is nothing significant to report in the mailing list activity and statistics. ## JIRA activity: - 161 JIRA tickets created in the last 3 months - 179 JIRA tickets closed/resolved in the last 3 months ## References [1] https://svn.apache.org/repos/private/pmc/ofbiz/trademarks/trademarks.txt [2] https://svn.apache.org/repos/private/pmc/ofbiz/security/vulnerabilities.txt [3] https://s.apache.org/kgja [4] https://blogs.apache.org/ofbiz/ [5] https://twitter.com/ApacheOfbiz [6] https://www.facebook.com/Apache-OFBiz-1478219232210477/ ----------------------------------------- Attachment AQ: Report from the Apache Olingo Project [Michael Bolz] ## Description: Apache Olingo is a Java and JavaScript library that implements the Open Data Protocol (OData). Apache Olingo serves client and server aspects of OData. It currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC. ## Issues: There are no issues requiring board attention at this time ## Activity: - Discussion started about current (not anymore) active and possible new members which will result in invitations to the Olingo PMC (latest mid of 2019). ## Health report: - The Olingo project is still healthy and has no issues that require board involvement (beside already mentioned activity). - The V4 code line is on steady development also reflected in related discussions on mailing list and new created JIRA items. It is planned to do a release latest by mid of 2019 or earlier if requested. - The V2 code line was released as 2.0.11 and contains the latest contributions. But there are still open and new created JIRA items. Based on work on those there might be a further minor maintenance release during this year. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ramesh Reddy on Thu Oct 08 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Archana Rai at Fri May 26 2017 ## Releases: - V2 2.0.11 was released on Sat Feb 16 2019 ## Mailing list activity: - dev@olingo.apache.org: - 87 subscribers (down -1 in the last 3 months): - 131 emails sent to list (147 in previous quarter) - user@olingo.apache.org: - 201 subscribers (down -2 in the last 3 months): - 5 emails sent to list (6 in previous quarter) ## JIRA activity: - 23 JIRA tickets created in the last 3 months - 12 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: Report from the Apache OODT Project [Imesha Sudasingha] ## Description: - Apache OODT is a software framework as well as an architectural style for the rapid construction of scientific data systems. It provides components for data capture, curation, metadata extraction, workflow management, resource management, and data processing. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Last release was 1.2.5 released on Thu Sep 13 2018 - This has been a very quiet period since no major developments were carried out. The 1.9 release is yet to be made, but is on hold due to committers being busy to verify the changes made. ## Health report: - 1.9 release is yet to be made (though it is 100% ready from dev point of view, not verified yet). We hope we will be able to release this in the coming period with the new found energy due to GSoC 2019. - We are planning to offer 2/3 GSoC projects to attract new contributors to the community. These projects are focused on improving OODT UI (named OPSUI) and making OODT deployment easy. - We believe that OODT will be more active with GSoC students applying for projects and the introduction of above mentioned features from users' point of view. ## PMC changes: - Currently 45 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Imesha Sudasingha on Mon Aug 28 2017 ## Committer base changes: - Currently 46 committers. - No new committers added in the last 3 months - Last committer addition was Imesha Sudasingha at Tue Aug 29 2017 ## Releases: - Last release was 1.2.5 on Thu Sep 13 2018 ## Mailing list activity: - As mentioned earlier, this has been a quiet period and no reasonable development activity took place. - dev@oodt.apache.org: - 96 subscribers (up 1 in the last 3 months): - 57 emails sent to list (135 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AS: Report from the Apache OpenNLP Project [Jörn Kottmann] ## Description: - Apache OpenNLP is a machine learning based toolkit for the processing of natural language text. ## Issues: - No issues to report. ## Activity: - Suneel Marthi and Jörn Kottmann had a talk at FOSDEM 2019 which utilized OpenNLP, "Streaming Pipelines for Neural Machine Translation" - Suneel Marthi and Jörn Kottmann had a talk at Big Data Warsaw 2019, which used OpenNLP, "Streaming topic model training and inference with Apache Flink" ## Health report: - The project has an active committer base and there’s healthy activity on mailing lists. - The PMC is not tracking any prospects right now, all active committers are already in the PMC. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Koji Sekiguchi on Tue Oct 10 2017 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Jeffrey T. Zemerick at Wed Apr 26 2017 ## Releases: - 1.9.1 was released on Mon Dec 31 2018 ## Mailing list activity: - We received the usual amount of traffic on the dev and users lists. - users@opennlp.apache.org: - 455 subscribers (up 7 in the last 3 months): - 11 emails sent to list (24 in previous quarter) - dev@opennlp.apache.org: - 239 subscribers (up 2 in the last 3 months): - 14 emails sent to list (8 in previous quarter) - issues@opennlp.apache.org: - 52 subscribers (up 1 in the last 3 months): - 62 emails sent to list (82 in previous quarter) ## JIRA activity: - 11 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache OpenWebBeans Project [Mark Struberg] ## Description: Apache OpenWebBeans is an ALv2-licensed implementations of the "Contexts and Dependency Injection for the Java EE platform" specifications which are defined as JSR-299 (CDI-1.0), JSR-346 (CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0). The OWB community also maintains a small server as Apache Meecrowave subproject. Meecrowave bundles latest releases of the ASF projects Tocmat9 + OpenWebBeans + CXF + Johnzon + log4j2. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity is fine. We fixed a few Java11 related issues. Next up is again looking a bit into performance. We are still fine, but probably could be even better. ## Health report: We got some contribution to our Meecrowave samples. Currently we are mostly in maintenance mode. Activity is fluctuating as most our contributors are involved in multiple ASF projects. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Reinhard Sandtner on Mon Oct 09 2017 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was John D. Ament at Mon Oct 09 2017 ## Releases: - 1.2.5 was released on Sun Jan 13 2019 - 1.2.6 was released on Wed Jan 30 2019 - 2.0.10 was released on Sun Jan 13 2019 - 2.0.9 was released on Thu Dec 20 2018 - meecrowave-1.2.5 was released on Sun Jan 13 2019 - meecrowave-1.2.6 was released on Sat Feb 02 2019 - meecrowave-1.2.7 was released on Thu Feb 28 2019 ## JIRA activity: - 28 JIRA tickets created in the last 3 months - 31 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AU: Report from the Apache Perl Project [Philippe Chiasson] --- mod_perl -- No new mod_perl 2.x releases since 2016-10. -- Activity -- This report doesn't have much more to offer than last time around. I am not sure how to describe the health of this project, it's not unhealthy in my opinion. Just dormant, missing developers willing to spend time on it. The project isn't done by any stretch of the imagination, there are still a lot of things to be implemented, especially since httpd-2.4. I am aware it's not an ideal situation for an ASF project, but for the time being, I am not sure what could be concretely be done to address this. As for specific comments from the board: The concert about sufficient PMC members available to step in, for instance in the case of a security issue, I can't be 100% certain here, but I can say that myself, for one, would make the necessary time and I do read the mailing-lists daily. The suggestion to possible join the httpd project, I am not sure what that would achieve. I think the most difficult issue with finding development resources is that not only it requires a very good understanding of httpd's internals *and* Perl's internals. I wouldn't necessarily be against it, but I am just not convinced it would achieve much. As for the overall issue of oversight, I've reached directly to the PMC to see if folks want to speak for themselves and I'll include their responses either in this report or the next. Most certainly open to all and any suggestions. -- Users -- The mod_perl users list is seeing little activity, as usual. There was some growing interest in seeing some form of support for the event mpm, but that would be very tricky to implement robustly. Patches and bug reports are few, but keep on coming. -- Commiters -- Currently 22 committers. No new changes to the committer base since last report. Last Commiter addition was Jan Kaluza in April 2013 -- PMC -- Currently 11 PMC members. No new PMC members added in the last 3 months Last PMC addition was Steve Hay on Wed Feb 29 2012 ----------------------------------------- Attachment AV: Report from the Apache Pig Project [Koji Noguchi] ## Description: - Apache Pig is a platform for analyzing large data sets on Hadoop. It provides a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. ## Issues: - There are no issues requiring board attention at this time ## Activity: - We are behind on the next major release of 0.18. Last release 2017/06. We were hoping to get bytecode generation(PIG-5256) committed but depending on the availability of other contributors, we may need to release one before that. ## Health report: - Overall activity is low as project is mostly stable and contributions are mainly bug fixes. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Koji Noguchi on Thu Aug 04 2016 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Nándor Kollár at Thu Sep 06 2018 ## Releases: - Last release was 0.17.0 on Thu Jun 15 2017 ## Mailing list activity: - dev@pig.apache.org: - 363 subscribers (down -1 in the last 3 months): - 191 emails sent to list (326 in previous quarter) - user@pig.apache.org: - 1062 subscribers (down -8 in the last 3 months): - 16 emails sent to list (3 in previous quarter) ## JIRA activity: - 12 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AW: Report from the Apache Pivot Project [Roger Lee Whitcomb] Description: Apache Pivot is an open-source platform for building installable Internet applications (IIAs). It combines the enhanced productivity and usability features of a modern user interface toolkit with the robustness of the Java platform. Issues: There are no board-level issues at this time. Activity: Again, very little (almost no) development activity this quarter; combination of work pressures and ongoing personal challenges. A tiny uptick in dev and user emails, which still shows some interest. Otherwise no change from previous quarters. Deprecations in the latest Java versions (esp. Applet and Nashorn engine) will require serious development efforts to address, thus some suggestions for different backends. Health report: Basically unchanged for several years: development is ongoing, but users are quiet. PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Niclas Hedhman on Wed Jan 13 2016 Committer base changes: - Currently 9 committers. - No new changes to the committer base since last report. - No new committers added in the last 3 months - Last committer addition was more than 2 years ago Releases: - Last release was 2.0.5 on Mon Jul 03 2017 - Still some development on next major version (2.1.0). Mailing list activity: - dev@pivot.apache.org: - 62 subscribers (up one in the last 3 months) - 10 emails sent to list (20 in previous quarter) - user@pivot.apache.org: - 169 subscribers (unchanged over the last 3 months) - 1 email sent to list (1 in previous quarter) JIRA activity: - No JIRA tickets created in the last 3 months - One JIRA ticket closed/resolved in the last 3 months ----------------------------------------- Attachment AX: Report from the Apache Portable Runtime (APR) Project [Nick Kew] ## Description: - The Apache Portable Runtime (APR) project creates and maintains software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. There are three sub-projects: APR, APR-UTIL and APR-ICONV, of which the first two are the main focus of developer interest. ## Issues: There are no issues requiring board attention at this time. ## Activity: The project is broadly stable, and there has been little activity. Towards the end of the period, it was proposed we push for an APR-1.7 release. This may be hoped for with APR within the next reporting period. An APR-UTIL 1.7 release is likely to be further away, as there is more work to be done including some substantial backports from trunk. ## Health report: - The project remains quiet but healthy. ## PMC changes: - Currently 41 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Evgeny Kotkov on Wed Sep 13 2017 ## Committer base changes: - Currently 67 committers. - No new committers added in the last 3 months - Last committer addition was Evgeny Kotkov at Wed Sep 13 2017 ## Releases: - No new releases in the reporting period. The last release was a bugfix (APR-1.6.5) in September 2018. ## Mailing list activity (from reporter.apache.org): - The subscriber base remains stable. - dev@apr.apache.org: - 330 subscribers (up 1 in the last 3 months): - 64 emails sent to list (91 in previous quarter) - bugs@apr.apache.org: - 20 subscribers (up 0 in the last 3 months): - 43 emails sent to list (22 in previous quarter) ## Bugzilla Statistics: - 4 Bugzilla tickets created in the last 3 months - 2 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment AY: Report from the Apache Portals Project [David Sean Taylor] ## Description: Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Activity: Apache Portals has released 0 releases since the last report. Pluto: Here are some new utility JAR modules I hope to release at that time as well: - portlet-servlet-adapter - thymeleaf-mvc-portlet-api - thymeleaf-mvc-portlet-cdi - thymeleaf-mvc-portlet-spring - thymeleaf-portlet-api No additional members since last report 12 Feb 2017 - Two new PMC members added 27 April 2017 - Apache Portals Pluto team released Pluto Maven Archetypes 3.0 to support to developing new portlets to the new 3.0 spec ## Mailing list activity: Not much activity. Some discussions around the Jetspeed Maven plugins on the Jetspeed list. Low volume activity on all lists. ## Issues: We have no board-level issues at this time. ## PMC/Committership changes: Last Added PMC Members: 12 Feb 2017 - Scott Martin Nicklaus 12 Feb 2017 - Neil Griffin Last Added Committers: 05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014 Neil Griffin ## Releases: Pluto 3.0.1 - 21 June 2018 Pluto Maven Portlet Archetype 3.0.1 - 21 June 2018 Pluto Maven Generic Archetype 3.0.1 - 21 June 2018 Pluto Maven Archetype 3.0.0 - 27 April 2017 Pluto 3.0.0 - 18 January 2017 Jetspeed 2.3.1- 09 May 2016 ----------------------------------------- Attachment AZ: Report from the Apache PredictionIO Project [Donald Szeto] ## Description: - PredictionIO is an open source Machine Learning Server built on top of state-of-the-art open source stack, that enables developers to manage and deploy production-ready predictive services for various kinds of machine learning tasks. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Released version 0.14.0 - Version 1.0 design in progress - Tracking the community for new committer candidates - Continued community support and driving for contributions ## PMC changes: - Currently 28 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mars Hall on Fri Jul 28 2017 ## Committer base changes: - Currently 29 committers. - No new changes to the committer base since last report. - Last committer addition was Mars Hall on Fri Jul 28 2017 ## Releases: - 0.14.0 was released on Mon Mar 11 2019 ----------------------------------------- Attachment BA: Report from the Apache Pulsar Project [Matteo Merli] ## Description: Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The project has released 2.3.0 in February. This was a very big release that included many new features and improvements. Highlights include: * Kubernetes support in Pulsar functions * New Pulsar IO connectors: Change data capture with Debezium, MongoDB, Elastic Search, HBase and local files source and sink. * Token based authentication * Schema support in Python client library * Function state API in Python - Several meetup and conferences talk on Pulsar * Two talks are scheduled for Strata SF in March: - How Zhaopin.com built its enterprise event bus using Apache Pulsar from Sijie and Penghui - Reducing stream processing complexity using Apache Pulsar Functions from Jowanza Joseph and Karthik Ramasamy - A patch release (2.3.1) is being prepared to address all the issues reported in 2.3.0 release - Work is ongoing for next release (2.4.0), scheduled for end of March for which we plan to include: * NodeJS client library * Negative acknowledgments * Replicated subscription state * Kerberos authentication plugin - Since last report several PIPs (Pulsar improvement proposals) were submitted: * PIP 32: Go Function API, Instance and LocalRun * PIP 31: Transaction Support * PIP 30: change authentication provider API to support mutual authentication * PIP 28: Pulsar Proxy Gateway Improvement * PIP 29: One package for both pulsar-client and pulsar-admin * PIP 26: Delayed Message Delivery ## Health report: - There is healthy grow in the community - Activity on the Slack channel is still high, many first time users come to ask questions while getting started. There are 103 weekly active users on the channel, up from 92 in November. ## PMC changes: - Currently 23 PMC members - No new PMC added since last report ## Committer base changes: - Currently 24 committers - Last committer added: Penghui Li - Dec 7th ## Releases: - 2.2.1 was released on Dec. 31st 2018 - 2.3.0 was released on Feb. 20th 2019 ## Mailing list activity: - Activity on the mailing lists remains high with a mixture of new users, contributors, and deeper more experienced users and contributors sparking discussion and questions and filing bugs or new features. - users@pulsar.apache.org: - 94 subscribers (+10 from Dec 2018) - 103 emails sent to list in last 3 months - dev@pulsar.apache.org: - 97 subscribers (+17 from Dec 2018) - 241 emails sent to list in last 3 months ## GitHub activity: - 386 PR from 47 contributors were merged in the last 3 months (up from 131) - 197 Issues were created and 125 closed in the last 3 months ----------------------------------------- Attachment BB: Report from the Apache River Project [Peter Firmstone] ## Description: - Apache River provides a platform for dynamic discovery and lookup search of network services. Services may be implemented in a number of languages, while clients are required to be jvm based (presently at least), to allow proxy jvm byte code to be provisioned dynamically. ## Issues: - Answers to board questions: idf: It's been a year since the last committer addition. Are there a new prospects? - Not at present, due to low activity and the complexity of the unique monolithic build system. We are working to resolve this with a Maven modular build structure. rs: given 12 vs 16 members of PMC and committership roster, is there anything preventing the remaining 4 committers to consider joining the PMC? - There are no blockers, I will ask them to join the PMC. ## Activity: - Minimal activity at present, initial work on the modular build structure has commenced. The current monolithic build is complex, with it's own build tool classdepandjar, it adds complexity for new developers. In recent months I have had work committments that have limited my ability to integrate the modular build. The other committers are waiting for the modular build and I have done a lot of work on this locally, this work has been a significant undertaking integrating the works of Dennis Reedy, Dan Rollo and myself. This is also a mature codebase, having been in development since the late 1990's. Release roadmap: River 3.1 - Modular build restructure (& binary release) River 3.2 - Input validation 4 Serialization, delayed unmarshalling& safe ServiceRegistrar lookup service.River 3.3 - OSGi support ## Health report: - River is a mature codebase with existing deployments, it was primarily designed for dynamic discovery of services on private networks. IPv4 NAT limitations historically prevented the use of River on public networks, however the use of IPv6 on public networks removes these limitations. Web services evolved with the publish subscribe model of todays internet, River has the potential to dynamically discover services on IPv6 networks, peer to peer, blurring current destinctions between client and server, it has the potential to address many of the security issues currently experienced with IoT and avoid any dependency on the proprietary cloud for "things". - Future Direction: * Target IOT space with support for OSGi and IPv6 (security fixes required prior to announcement) * Input validation for java deserialization - prevents DOS and Gadget attacks. * IPv6 Multicast Service Discovery (River currently only supports IPv4 multicast discovery). * Delayed unmarshalling for Service Lookup and Discovery (includes SafeServiceRegistrar mentioned in release roadmap), so authentication can occur prior to downloading service proxy's, this addresses a long standing security issue with service lookup while significantly improving performance under some use cases. * Security fixes for SSL endpoints, updated to TLS v1.2 with removal of support for insecure cyphers. * Secure TLS SocketFactory's for RMI Registry, uses the currently logged in Subject for authentication. The RMI Registry still plays a minor role in service activation, this allows those who still use the Registry to secure it. * Maven build to replace existing ant built that uses classdepandjar, a bytecode dependency analysis build tool. * Updating the Jini specifications. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dan Rollo on Fri Dec 01 2017 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Dan Rollo at Thu Nov 02 2017 ## Releases: - Last release was River-3.0.0 on Thu Oct 06 2016 ## /dist/ errors: 4 - TODO - Developer certificates expired, investigate solution. I created new certificates, prior to the expiry of my old certificates, should I resign the release artifacts with the new certificates? ## Mailing list activity: - Relatively quiet - dev@river.apache.org: - 89 subscribers (down -1 in the last 3 months): - 5 emails sent to list (9 in previous quarter) - user@river.apache.org: - 92 subscribers (up 0 in the last 3 months): - 1 emails sent to list (0 in previous quarter) ----------------------------------------- Attachment BC: Report from the Apache RocketMQ Project [Xiaorui Wang] ## Description: - Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Apache RocketMQ Meetup Hangzhou, China ended on Sat Nov 24 2019, 200+ spectators attended. - Apache RocketMQ Meetup Shanghai, China ended on Sat Jan 12 2019, 200+ spectators attended. - Community are calling for proposal for Apache RocketMQ Meetup Chengdu, China. - Some hobbyists from the community are planning to organize City Meetup in China. PMCs are keeping eyes on the discussion of the activity. - Von Gosling presented Exploring lightweight streaming platform with Apache RocketMQ at Flink Forward China 2018. ## Health report: Within the past three months (since 2018-12-01 ): - 57 GitHub issues were opened and 43 were closed - 51 GitHub pull requests were opened and 78 were closed ## PMC changes: - Currently 11 PMC members. - Du Heng was added to the PMC on Mon Dec 24 2018 - Last PMC addition: Mon Dec 24 2018 (Du Heng) ## Committer base changes: - Currently 18 committers. - ShannonDing was added as a committer on Sat Dec 22 2018 - Last committer addition: Sat Dec 22 2018 (ShannonDing) - At least 3 active contributors have a chance to be committers, pmc members are keeping eyes on them ## Releases: - ROCKETMQ-4.4.0 was released on Wed Jan 23 2019 ## Mailing list activity: We have disabled the JIRA system so the issues mailing list has no activity. In this quarter, Some hobbyists from the community have organized a number of online events that have greatly motivated people to get to know about the community. In the next few months, more city meetups will be launched, and this proposal will be encouraged to be discussed in the dev and user mailing list. - users@rocketmq.apache.org: - 240 subscribers (up 54 in the last 3 months): - 193 emails sent to list (61 in the previous cycle) - dev@rocketmq.apache.org: - 213 subscribers (up 56 in the last 3 months): - 2194 emails sent to list (744 in previous cycle) - commits@rocketmq.apache.org: - 74 subscribers (up 6 in the last 3 months): - 538 emails sent to list (139 in previous cycle) ----------------------------------------- Attachment BD: Report from the Apache Royale Project [Harbs] ## DESCRIPTION Apache Royale is a new implementation of the principles of Apache Flex, designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale improves developer productivity in creating applications to run wherever JavaScript runs, including on browsers as well as in Apache Cordova applications, Node, etc. ## ISSUES There are no issues requiring board attention at this time. ## RELEASES - Apache Royale 0.9.2 was released on March 16 2018. - Apache Royale 0.9.4 was released on November 14 2018. ## ACTIVITY - No releases this quarter; however, we have started discuss about next release. We would like to make the whole process less complex, so there is a discussion on the dev list about making one central point where most of the steps happen automatically. - Lots of improvements in one of the core parts of Royale responsible for communications with server sites (AMF). - Lots of progress on a new default look (component set) for Royale apps. - Lots of progress on migrating large Flex apps to Royale. A new "Flex Emulation" component set is being worked on to ease migrations. - The owner of an ActionScript code base that doesn't use Flex is attempting to use the Royale compiler to cross-compile his code to JavaScript. - There have been a number of blog posts on using Royale. They seem to be well-received. - We are using Disqus for blog comments. It seems to help engagement. We were not able to figure out how to get comments sent to the @dev list. - We had a lot of activity on social networks, sharing what is happening in Apache Royale as we progress in the project. We think it is important to do this so people outside the project and not following in a daily basis can get a notion of how we are doing. The numbers are: - Our Twitter account has gained 507 followers since we opened it, and we are getting around 30 likes and 10 to 20 retweets when we post something, showing interest in what we're doing. - Our Facebook page has 116 likes, and we get 10-15 interactions (likes) and some comments on each post, showing interest in Apache Royale. - We started a LinkedIn Group that 122 people joined almost immediately. Groups in LinkedIn tend to be watched by many people who remain silent most of the time. - A contributor was able to migrate an Apache Flex application with success. The application, part of a suite is in the process of validation and testing and should be put in production for a client in about a month. The current version is the app's first iteration since the Flex version, a huge app developed over several years. The plan is to continue to migrate other parts of the suite in phases as the client requires them. ## COMMUNITY - Greg Dove was added as committer on October 28, 2018. - No new PMC Members yet - Two new contributors are candidates to become committers. ## Mailing list activity: User-lists continue to grow. Fewer emails to read, but still a lot of emails. - users@royale.apache.org: - 72 subscribers (up 1 in the last 3 months): - 366 emails sent in the past 3 months (528 in the previous quarter) - dev@royale.apache.org: - 77 subscribers (up 1 in the last 3 months): - 1389 emails sent in the past 3 months (1974 in the previous quarter) ----------------------------------------- Attachment BE: Report from the Apache Sentry Project [Alex Kolbasov] ## Description: Apache Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop Cluster. ## Issues: Sentry PMC voted to propose a new PMC Chair - Kalyan Kalvagadda but the change didn't go through the process yet. ## Activity: - Work on 2.2.0 release - HDFS sync performance and usability enhancements ## Health report: - Development activity seems pretty consistent; - New developers starting contributing to the project; ## PMC changes: - Currently 38 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Na Li on Mon Dec 10 2018 ## Committer base changes: - Currently 40 committers. - No new committers added in the last 3 months - Last committer addition was Arjun Mishra at Fri Jul 06 2018 ## Releases: - Last release was 2.1.0 on Sun Sep 30 2018 ----------------------------------------- Attachment BF: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] Description =========== Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF and Karaf to provide a complete, enterprise-ready ESB powered by OSGi. Issues ====== There are no outstanding issues requiring board attention. Activity ======== The project focus of Apache ServiceMix is the assembly of the integration container, the actual functionality is being maintained in related projects like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ. - We have released 2 sets of OSGi bundles and the next set is on vote. - We have migrated our repositories to gitbox. - The work on ServiceMix Assembly and documentation was outstanding last months. I'd like to start discussion in the community about the next steps to provide a new assembly (probably new ServiceMix 8.x line), how can we focus more on cloud capabilities and how can we make the community more attractive for new people. Health report ============= - The activity of the community (mailing lists, JIRA, releases) has been a bit slower than during the last period. PMC changes =========== - Currently 21 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrea Cosentino on Wed Mar 15 2017 Committer base changes ====================== - Currently 50 committers. - No new committers added in the last 3 months - Last committer addition was Andrea Cosentino at Sun Mar 13 2016 Releases ======== - Apache ServiceMix Bundles 2018.12 on December 30 2018 - Apache ServiceMix Bundles 2019.01 on February 05 2019 JIRA activity ============= - 111 JIRA tickets created in the last 3 months - 91 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BG: Report from the Apache Shiro Project [Les Hazlewood] 2019 March - Board report for Apache Shiro Apache Shiro is a powerful and flexible open-source application security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. We have no issues that require Board assistance at this time. Releases: - Last release was 1.4.0 on 05-May-2017 Community & Project: - Our latest committer / PMC member has been helping bring some new life to the project - Project commits and message on the dev list has gone up since the start of the year - Feature development is planned to continue against master. - The 1.4.0 Release has been a step toward modernizing Shiro as well as retain backwards compatibility Last committer voted in: Francois Papon on 10 Dec 2018 Last PMC Member voted in: Francois Papon on 10 Dec 2018 ----------------------------------------- Attachment BH: Report from the Apache Sling Project [Robert Munteanu] ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Issues: Business continues as usual with individual module releases. ## Activity: Good activity level overall, contributions from different people continue. ## Health report: We have also made a good number of module releases. ## PMC changes: - Currently 26 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrei Dulvac on Mon Jul 30 2018 ## Committer base changes: - Currently 43 committers. - No new committers added in the last 3 months - Last committer addition was A. J. David Bosschaert at Fri Mar 09 2018 ## Releases: - Apache Sling API 2.20.0 was released on Tue Dec 18 2018 - Apache Sling Capabilities 0.2.0 was released on Mon Dec 17 2018 - Apache Sling Capabilities JCR 0.2.0 was released on Mon Dec 17 2018 - Apache Sling DataSource Provider version 1.0.4 was released on Tue Feb 26 2019 - Apache Sling Engine 2.6.18 was released on Fri Jan 11 2019 - Apache Sling Feature 1.0.0 was released on Fri Feb 01 2019 - Apache Sling Feature IO 1.0.0 was released on Fri Feb 01 2019 - Apache Sling HTL Maven Plugin 1.2.4-1.4.0 was released on Mon Jan 28 2019 - Apache Sling JCR Jackrabbit Access Manager 3.0.4, Apache Sling JCR ContentLoader 2.3.0 was released on Thu Dec 20 2018 - Apache Sling JCR Resource Resolver version 3.0.18 was released on Tue Feb 26 2019 - Apache Sling Maven Plugin 2.4.0 was released on Mon Jan 14 2019 - Apache Sling Resource Collection API version 1.0.2 was released on Tue Feb 26 2019 - Apache Sling Scripting HTL Compiler 1.1.2-1.4.0 was released on Mon Jan 28 2019 - Apache Sling Scripting HTL Engine 1.1.2-1.4.0 was released on Mon Jan 28 2019 - Apache Sling Scripting HTL Java Compiler 1.1.2-1.4.0 was released on Mon Jan 28 2019 - Apache Sling Scripting HTL Runtime 1.1.0-1.4.0 was released on Mon Jan 28 2019 - Apache Sling Scripting JSP Tag Library (Compat) 1.0.0 was released on Mon Feb 18 2019 - Apache Sling Scripting JSP Tag Library 2.4.0 was released on Mon Feb 18 2019 - Apache Sling Servlets Annotations 1.2.4 was released on Tue Dec 18 2018 - Apache Sling Servlets Get 2.1.40 was released on Tue Dec 11 2018 - Apache Sling Servlets Post 2.3.28 was released on Mon Jan 14 2019 - Apache Sling Servlets Resolver 2.5.2 was released on Tue Dec 18 2018 - Apache Sling Tenant 1.1.4 was released on Wed Jan 16 2019 - Apache Sling Testing OSGi Mock 2.4.6 was released on Thu Feb 14 2019 - Apache Sling Testing Sling Mock Jackrabbit Oak-based Resource Resolver 2.1.2 was released on Tue Dec 11 2018 - Apache Sling XSS Protection API 2.0.14 was released on Thu Jan 24 2019 - Apache Sling XSS Protection API 2.1.0 was released on Tue Jan 29 2019 ## JIRA activity: - 141 JIRA tickets created in the last 3 months - 121 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BI: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for March 2019 SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Status and health report: The project activities, including running of our rule update infrastructure and our dev and user mailing lists, are continuing smoothly. We are close to releasing SpamAssassin version 3.4.3, although we missed releasing it in the last quarter. We have one mentored project for GSOC 2019, and are still soliciting proposals. Releases: The last release was Apache SpamAssassin version 3.4.2 on 16 September 2018. We are close to releasing version 3.4.3 to address some issues that were deferred, in part so we could quickly release security fixes in 3.4.2. After we release 3.4.3 we expect to resume development in our main branch for 4.0. Note that we maintain online rule updates that are continuously updated through a combination of developer contributions and automated processing via our mass-check facility. Committer/PMC changes: Most recent new committer: Paul Stead (pds) 12 September 2018 Most recent new PMC members: Giovanni Bechis (gbechis) 24 Sep 2018 Henrik Krohns (hege) 25 Sep 2018 ----------------------------------------- Attachment BJ: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment BK: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: - Apache Storm is a distributed real-time computation system. ## Issues: - See update in the private section below. ## Activity: - Project activity has been relatively quiet this quarter. ## Health report: - New contributors continue to engage and that engagement tends to keep up activity levels, even as some contributors move on. ## PMC changes: - Currently 38 PMC members. - Govind Menon was added to the PMC on Thu Jan 24 2019 ## Committer base changes: - Currently 39 committers. - Govind Menon was added as a committer on Fri Jan 04 2019 ## Releases: - Last release was 1.1.3 on Mon Jun 04 2018 ## JIRA activity: - 53 JIRA tickets created in the last 3 months - 44 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BL: Report from the Apache Synapse Project [Isuru Udana] ## Description: Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. ## Issues: None identified. ## Activity: There was no major activity in the project in the last quarter. ## Health report: PMC members and contributors who were active in the project for doing the last release had a meeting to see how we can bring back project into life. So as the starting point, we decided to flush the pending Jira tickets by reviewing issues, reviewing and committing patches, etc. When we get into a good state we will plan for the next release. ## PMC changes: - Currently 27 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Prabath Ariyarathna on Thu May 04 2017 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Prabath Ariyarathna at Fri Feb 10 2017 ## Releases: - Last release was 3.0.1 on Sat Dec 09 2017 ## Mailing list activity: - dev@synapse.apache.org: - 184 subscribers (down -1 in the last 3 months): - 16 emails sent to list (17 in previous quarter) - user@synapse.apache.org: - 177 subscribers (up 0 in the last 3 months): - 1 emails sent to list (1 in previous quarter) ----------------------------------------- Attachment BM: Report from the Apache Tajo Project [Hyunsik Choi] ## Description: - Tajo is an open source big data warehouse system in Hadoop for processing web-scale data sets. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Tajo 0.11.3 was released on May 18, 2016 - We already moved Tajo git repository to Gitbox before the mandatory migration. ## Health report: - The activity of this project is still low. However, PMC members can answer immediately any issue. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Hyoung Jun Kim on Sun Dec 07 2014 ## Committer base changes: - Currently 18 committers. - No new committers added in the last 3 months - Last committer addition was Jong-young Park at Sun May 29 2016 ## Releases: - Last release was 0.11.3 on Wed May 18 2016 ## Mailing list activity: - dev@tajo.apache.org: - 93 subscribers (down -2 in the last 3 months): - 6 emails sent to list (1 in previous quarter) - issues@tajo.apache.org: - 23 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - user@tajo.apache.org: - 47 subscribers (up 0 in the last 3 months): - 1 emails sent to list (0 in previous quarter) ----------------------------------------- Attachment BN: Report from the Apache Tomcat Project [Mladen Turk] ## Description: - A Java Servlet, JavaServer Pages, Java WebSocket and Java Unified Expression language specifications implementation. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Continued healthy activity across multiple components and responsiveness on both dev and user lists. - The EU FOSSA program has offered the project a 2 day hackathon on 4th/5th May 2019 and the project has accepted. The EU is starting the necessary organisation and we expect to hear from them shortly regarding the next steps. - We have made transition from svn to git. ## PMC changes: - Currently 27 PMC members. - Last addition May 2018 ## Committer base changes: - Currently 46 committers. - Woonsan Ko was added as a committer on Wed Dec 19 2018 ## Releases: - Apache Tomcat 7.0.93 was released on Thu Feb 21 2019 - Apache Tomcat 8.5.37 was released on Tue Dec 18 2018 - Apache Tomcat 8.5.38 was released on Fri Feb 08 2019 - Apache Tomcat 9.0.16 was released on Fri Feb 08 2019 ## Trademark: - No new trademark issues in the last 3 months and there are currently no outstanding trademark issues that the Apache Tomcat PMC is working on. - Detailed history is available at: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt ## Security: - Detailed status: http://tomcat.apache.org/security.html ----------------------------------------- Attachment BO: Report from the Apache Trafodion Project [Pierre Smits] ## Description: - Apache Trafodion extends the Apache Hadoop ecosystem to guarantee transactional integrity and operational workloads for new kinds of Big Data applications. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - In the last quarter the community worked to get a new release out. - The community continued working on tickets and participating on the Project's mailing list in line with previous months. - Repositories of the project were migrated to gitbox. - The PMC onboard two new members in this quarter, and one new com- mitter was added. ## Health report: - Subscriptions to the (public) mailing lists showed stable numbers compared to previous quarter (for details see section Mailing List activity below). - Compared to previous quarter, the community involvement showed a stable participation on the dev and user mailing list, while sharp increases were noticed for the notifications for code review and ticket creation, comment and resolution (for details see section Mailing List activity below). This sharp increase was partly the result of migration of repositories to gitbox. - The PMC regards the project as healthy. ## PMC changes: - Currently 15 PMC members. - New PMC members: - Anoop Sharma was added to the PMC on Thu Dec 06 2018 - Hans Zeller was added to the PMC on Thu Dec 06 2018 ## Committer base changes: - Currently 24 committers. - No new committers added in the last 3 months - Last committer addition was Prashanth Vasudev at Tue Nov 13 2018 ## Releases: - 2.3.0 was released on Wed Feb 27 2019 ## Mailing list activity: - dev@trafodion.apache.org: - 96 subscribers (down -2 in the last 3 months): - 241 emails sent to list (233 in previous quarter) - codereview@trafodion.apache.org: - 24 subscribers (down -1 in the last 3 months): - 416 emails sent to list (205 in previous quarter) - issues@trafodion.apache.org: - 33 subscribers (down -1 in the last 3 months): - 489 emails sent to list (343 in previous quarter) - user@trafodion.apache.org: - 104 subscribers (down -1 in the last 3 months): - 1 emails sent to list (4 in previous quarter) - security@trafodion.apache.org: - 6 subscribers (up 0 in the last 3 months): - Currently no automated insights in number of ml postings provided by ComDev-reporter services. - private@trafodion.apache.org: - 20 subscribers (up 0 in the last 3 months): - Currently no automated insights in number of ml postings provided by ComDev-reporter services. ## JIRA activity: - 39 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ## Social media activity: - Followers: 275 (+8) - Tweets: 93 (+0) - Likes: 73 (+0) ----------------------------------------- Attachment BP: Report from the Apache Twill Project [Terence Yim] ----------------------------------------- Attachment BQ: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for March 2019. Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Lou DeGenaro on Mon May 02 2016 ## Committer base changes: - Currently 25 committers. - Last new committer: Viorel Morari was added as a committer on Thu Sep 20 2018 ## Releases: 1 releases of UIMA Ruta - Ruta 2.7.0 was released on 24 February 2019 Activity: UIMA DUCC project has been working on a release, with several release candidates. The core UIMA Java SDK version 3.0.2 is recently posted for voting. Community: The community continues to be moderately active. Issues: No Board level issues at this time. -Marshall Schor ----------------------------------------- Attachment BR: 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 customers experiences while also offering features to respect visitor privacy rules (such as GDPR). It is also the reference implementation of a ongoing standard specification being developed at OASIS Open. ## Issues: - there are no issues requiring board attention at this time ## Activity: - The focus has been on graduation, which was just been successful. - We are working on post graduation migration tasks (repository renaming, website update) - An Apache PR is in the works, we are working with the Apache press team to coordinate the announcements. ## Health report: - Development activity is a little slower than usual because a lot of focus was put on the graduation, but will probably return to normal soon - Committers & PMC members will soon be added as we asked some to wait until graduation is completed. ## PMC changes: - Currently 6 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 11 committers. - No changes (the PMC was established in the last 3 months) ## Releases: - 2018-09-10 Released version 1.3.0-incubating - 2017-09-28 Released version 1.2.0-incubating - 2016-10-04 Released version 1.1.0-incubating - 2016-05-22 Released version 1.0.0-incubating ## Mailing list activity: - users@unomi.apache.org: - 17 subscribers (up 5 in the last 3 months) - dev@unomi.apache.org: - 32 subscribers (up 0 in the last 3 months) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BS: Report from the Apache VCL Project [Josh Thompson] ## Description: - VCL is a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources including virtual machines, bare-metal computers, and resources in other cloud platforms. A self-service web portal is used to request resources and for administration. VCL became a TLP on June 20, 2012. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Votes for extending committer invitations to the two individuals previously mentioned passed. Invitations were sent, and both individuals accepted. ## Health report: - We continue to slowly creep forward toward our next release. There are only a few items remaining. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Aaron Coburn on Tue Jun 19 2012 ## Committer base changes: - Currently 10 committers. - New commmitters: - Mike Jennings was added as a committer on Fri Jan 04 2019 - Junaid Ali was added as a committer on Fri Dec 21 2018 ## Releases: - Last release was 2.5 on Thu Aug 17 2017 ## Mailing list activity: - dev@vcl.apache.org: - 117 subscribers (down -1 in the last 3 months): - 66 emails sent to list (34 in previous quarter) - user@vcl.apache.org: - 157 subscribers (up 2 in the last 3 months): - 11 emails sent to list (29 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BT: Report from the Apache Wicket Project [Andrea Del Bene] ## Description: Apache Wicket is an open source Java component oriented web application framework. ## Issues: - No issues require board attention. ## Activity: - After serving for 11 years as VP for Apache Wicket, Martijn Dashorst has stepped down from his role. Andrea Del Bene has been elected as new VP. He will be in charge for the current year (2019) as we have also decided to rotate our chair each year, just like many Apache project already do. We'd like to thank Martijn for his long and valuable service and we are happy knowing that he will continue to contribute to the project both as committer and PMC member. ## Health report: - The community is stable as is to be expected from a mature server side Java web framework. We don't anticipate a sudden large growth or large decline. - Questions to the user list and dev list are answered, resolved and discussed. - We keep on the look out for new committers and PMC members. The PMC is aware that to keep the project healthy new blood is necessary, but are realistic that server side Java web frameworks are not the newest and hottest technologies at this time. -We still working on Wicket 9. We started to collect some features and improvments we'd like to implement in the next main version (see http://apache-wicke t.1842946.n4.nabble.com/Future-releases-and-random-thoughts-td4681465.html). A first RC should see the light in two or three months. ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Maxim Solodovnik on Thu Apr 13 2017 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Maxim Solodovnik at Thu Apr 13 2017 ## Releases: - 6.30.0 was released on Mon Dec 10 2018 - 7.12.0 was released on Wed Feb 06 2019 - 8.3.0 was released on Fri Feb 01 2019 ## Mailing list activity: - Despite a slight decrease of subscribers, we can see an increase in activity not only in downloads, but also on mailinglist activity as well. So usage of Wicket seems steady and healthy. - users@wicket.apache.org: - 827 subscribers (down -20 in the last 3 months): - 258 emails sent to list (157 in previous quarter) - dev@wicket.apache.org: - 341 subscribers (down -8 in the last 3 months): - 207 emails sent to list (237 in previous quarter) - announce@wicket.apache.org: - 339 subscribers (down -8 in the last 3 months): - 8 emails sent to list (5 in previous quarter) ## JIRA activity: - 23 JIRA tickets created in the last 3 months - 23 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BU: Report from the Apache Xalan Project [Steven J. Hathaway] ----------------------------------------- Attachment BV: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J A couple minor improvements were recently made to the XML Schema 1.1 support, but otherwise it's been quiet. Mailing list traffic has been low; roughly 55+ posts on the j-dev and j-users lists since the beginning of December 2018. No new releases since the previous report. The latest release is Xerces-J 2.12.0 (April 30th, 2018). Xerces-C There's been discussion on several JIRA issues since December, but otherwise no development activity. Mailing list traffic has been low; roughly 35+ posts on the c-dev and c-users lists since the beginning of December 2018. 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 There was a recent question about whether we should have a new XML Commons release (to be consumed by Xerces-J). There may have been some bug fixes made that would benefit users, but this needs some investigation. 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 December 2018. ----------------------------------------- Attachment BW: Report from the Apache Yetus Project [Allen Wittenauer] ## Description: Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ## Issues: There are no issues requiring board attention at this time. ## Activity: We released 0.9.0 and are working towards a 0.10.0 release to fix some outstanding issues as well as add a few features. ## Health Report: Since the last board report, the switch to lazy consensus has moved the needle for the project as far as speed of commits. No contributions have been rejected. To answer the board's question from the last report: there has been no practical difference between RTC w/lazy consensus and CTR as yet. However, we have not done a release yet that compromised mostly LC commits since that was put in place. Adoption of/upgrades to 0.9.0 in the ASF remain lower than expected. This likely has to do with most of the contribution work being geared towards non-ASF deployments. Since the upgrade of the build infrastructure off of builds.apache.org in the past few months, there has been an uptick of build jobs failing. Some of us have been getting queries from Yetus-based ASF projects. No real cycles have been spent investigating why. Some thinking that the systemd defaults are out of whack again. With our own (relatively tiny) jobs, rerunning on a different, much less busy host usually succeeds. ## PMC changes: - Currently 9 PMC members. - Akira Ajisaka was added to the PMC on Mon Dec 17 2018 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Akira Ajisaka at Tue Feb 06 2018 ## Releases: - 0.9.0 was released on Thu Jan 17, 2019 ## Mailing list activity: INFRA made an unannounced change after we had been on Gitbox for a month causing all Github traffic to head to dev@. Attempting to get this changed such that Gitbox emails go to the gitbox@ mailing list instead has been a bit of a struggle. - dev@yetus.apache.org: - 44 subscribers (down -1 in the last 3 months): - 179 emails sent to list (49 in previous quarter) - gitbox@yetus.apache.org: - 5 subscribers (up 5 in the last 3 months) - notifications@yetus.apache.org: - 16 subscribers (up 0 in the last 3 months): - 805 emails sent to list (448 in previous quarter) ## JIRA activity: 0.9.0 closed a lot of long-standing issues, thus getting us a net positive for this quarter! - 84 JIRA tickets created in the last 3 months - 99 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BX: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables the implementation of a variety of primitives and mechanisms that are critical for safety and liveness in distributed settings, e.g., distributed locks, master election, group membership, and configuration. ## Issues: No issues requiring board attention. ## Activity: No new releases, only development work during the period. ## Health report: There has been no new release during the period, but we have bootstrapped the release process of 3.4.14, and it is currently being voted. The email activity has dropped compared to the last period, but the Jira activity has increased slightly. It has been a quiet period overall. The PMC continues to mentor contributors to eventually offer committership to the ones that show a strong commitment to the community. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Han on Wed Jun 21 2017 ## Committer base changes: - Currently 24 committers. - No new committers added in the last 3 months - Last committer addition was Fangmin Lv at Wed Oct 24 2018 ## Releases: - Last release was 3.4.13 on Mon Jul 16 2018 ## Mailing list activity: - dev@zookeeper.apache.org: - 495 subscribers (down -8 in the last 3 months): - 2691 emails sent to list (3691 in previous quarter) - user@zookeeper.apache.org: - 1205 subscribers (down -12 in the last 3 months): - 82 emails sent to list (136 in previous quarter) ## JIRA activity: - 97 JIRA tickets created in the last 3 months - 81 JIRA tickets closed/resolved in the last 3 months ------------------------------------------------------ End of minutes for the March 20, 2019 board meeting.