The Apache Software Foundation Board of Directors Meeting Minutes September 20, 2017 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:33 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/3bfz 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 Ted Dunning Jim Jagielski Chris Mattmann Brett Porter Phil Steitz Mark Thomas Directors Absent: none Executive Officers Present: Ross Gardler Sam Ruby Craig L Russell Kevin A. mcGrail - left at 11:17 Executive Officers Absent: Ulrich Stärk Guests: Alex Harui Christofer Dutz Daniel Gruno Daniel Takamori David Fisher Greg Stein P. Taylor Goetz Piotr Zarzycki Sally Khudairi Sharan Foga Tom Pappas Upayavira 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of August 16, 2017 See: board_minutes_2017_08_16.txt Approved by General Consent. B. The meeting of June 15, 2017 See: board_minutes_2017_06_15.txt Tabled. 4. Executive Officer Reports A. Chairman [Phil] First, I would like to thank Brett for his 4+ years of service as ASF Chairman. I am both inspired and challenged by the example that he set. I am also very grateful to him and Sam for automating a lot of administrative tasks, making that aspect of the role a lot easier. Despite careful instruction from Brett, I nonetheless made a few administrative errors this month, which were resolved thanks to help from Sam, Craig and Brett. Thanks to all for your help and patience as I learn the ropes. On September 11, I spoke at the Linux Foundation’s OSS Summit in Los Angeles, CA. The title of my talk was “Scaling OSS, Lessons Learned at the Apache Software Foundation." I talked about historical social, financial and operational challenges and how we had met them. I ended with some personal thoughts about the future - basically a statement of confidence in the resiliency of the ASF. Many thanks to Sally for her help and counsel preparing the talk. More thanks go to Sally, Chris, Rene Gielen and other members of the Struts PMC for marshaling a clear and effective response to press inquiries associated with the Equifax breach. B. President [Sam] My current priorities: EA/TAC/Conferences, Brand Management Items requiring board attention: * Brand Management continues to face scalability issues. See Brand Management reports for details. No immediate action required, options and alternatives will be brought back to the board in upcoming months. * Unless directed otherwise, the ASF infrastructure leadership team will continue to work with the ASF Treasury team in setting up a location to secure and track personnel related documents, balancing oversight and privacy. See January minutes for context. * We are still relatively early in the fiscal year, so projections will vary widely month to month, but for the first time this year we are not projected to make up for last year's underrun; which was attributed to timing of sponsor payments. No cause for concern about this year, but does suggest that we should revisit our five year forecast this fall. Input on whether this should be done bottoms up again, or should be done top down would be appreciated. * Fundraising Would like to give Fundraising Ambassadors VP Titles. Possible idea: VP Sponsor Relations. This is yet another example of a common theme where ASF titles are important externally. While amply reported elsewhere, I would like to also commend the organization's coordinated and professional response to the Equifax breach. Early reports from others on the cause of the breach were incorrect, and our initial response stated the known facts and enumerated the possibilities. As additional facts became known, we provided updates. As others have reported, this was a total team effort, with Sally as usual shouldering the bulk of the load. Not called out by others but Mark Cox played a crucial role in framing the initial message. While I have stayed on top of mailing list traffic, much of my time this month has been spent on converting various Whimsy tools from React.js to Vue.js. Three of the four tools have been converted, and work has begun on the remaining tool: the board agenda. I'll post on board@ with the implications of these change before they are deployed. Meanwhile, I will note that this would be an ideal time to look at any additional requirements (e.g., automating chair activities?) that people may have for this tool. Seeing if we can utilize our EA better remains on my todo list. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] - Virtual Report Here is a summary of the Foundation’s performance for the first four months of FY18. Cash on Aug 31th 2017 was $1,684.5K, which is down $104.5K from last month’s ending balance (Jul 17) of $1,789K, due to the timing of some Sponsor payments. The Aug 2017 cash balance is down $69.8K from the Aug 2016 month end balance of $1,754.3K. The Aug 2017 ending cash balance of $1,684.5K represents a cash reserve of 14.4 months based on the FY18 Cash forecast average monthly spending of $117.1K/month. The ASF reserve continues to be very healthy for an organization of ASF’s size, with an FY18 YE estimate of 11.7 month’s cash reserve. Regarding the YTD Cash P&L, we continue to have a very strong showing against our FY18 Budget four months in however as you can see the effect of the timing of Sponsor payments, which for Aug we had budgeted a few but had none, leaves us with our first down month of FY18. Now we need to continue to focus not only on the new but the existing sponsors as that was how the FY18 budget was constructed. This has us for revenue, $244.6K ahead of bud through Aug 2017. So, with the $607.7K of Sponsor revenue received so far in the first four months of FY18 we are more than 56% to our budgeted Sponsor revenue goal of $1,084K for FY18. We are remaining conservative in our forecasting and showing a slight increase in Net income for FY18, which is predicated on achieving our budgeted revenue figure of $1.084 million in Sponsor revenue and expenses staying relatively flat (currently YTD they are under budget) then the reserve would be 11.7 months which is one month below our budget of 12.7 months, which is still an extremely healthy reserve. YTD expenses are under by $12.7K. Infra, YTD, is over by $16.3K and the other depts. combined are under by $29K. I will be doing a more thorough review and will connect with Greg as there could be some items that are possibly miscoded. I would caution that we are only four months into the current fiscal year so it is very early yet. That said now that we are four months into the fiscal year I will be reaching out to the VP’s and Dept. heads to see if there have any information that could change our FY 18 forecast, for our Oct close. With regard to Net Income (NI), YTD for FY18 the ASF finished with a positive $169.2K NI vs a budgeted negative $88.1K NI or $257.3K ahead of Budget for the first four months of FY18. With the forecasted revenue, ahead of budget due to the Pivotal and Microsoft FY 17 payments as well as the Coinbase funds coming in FY18 and expenses close to Budget at this point we are estimating a $-148.9K negative NI for FY18 vs a budgeted NI loss of $167.8K. I want to congratulate the entire Organization on this very positive start to FY 18, it is still a bit early in the FY at this point, so we do need to continue to keep these efforts up as we move farther into FY 18 and continue to give Fundraising all the support we can as we move forward, while keeping an eye on our expenses at the same time. One last note is we will be getting the Cash Basis Audit underway in Q4 of 2017 for FY 17. I will keep everyone updated as to its progress once it starts. Current Balances: Citizens Money Market 1,470,260.79 Citizens Checking 210,983.97 Paypal - ASF 3,214.32 Total Checking/Savings 1,684,459.08 Aug-17 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 2,315.81 2,593.33 -277.52 Sponsorship Program 0.00 120,000.00 -120,000.00 Programs Income 0.00 0.00 0.00 Other Income 284.87 0.00 284.87 Interest Income 624.09 292.92 331.17 Total Income 3,224.77 122,886.25 -119,661.48 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 66,860.33 62,956.17 3,904.16 Sponsorship Program 2,084.73 2,000.00 84.73 Programs Expense 0.00 0.00 0.00 Publicity 6,700.00 10,000.00 -3,300.00 Brand Management 6,552.46 7,416.67 -864.21 Conferences 0.00 0.00 0.00 Travel Assistance Committee 0.00 0.00 0.00 Tax and Audit 0.00 0.00 0.00 Treasury Services 3,350.00 3,500.00 -150.00 General & Administrative 13,418.73 10,414.87 3,003.86 Total Expense 98,966.25 96,287.71 2,678.54 Net Income -95,741.48 26,598.54 -122,340.02 Cash Proof 1,780,200.56 1,684,459.08 YTD 2018 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 30,646.31 10,618.57 20,027.74 Sponsorship Program 569,612.08 351,250.00 218,362.08 Programs Income 0.00 0.00 0.00 Other Income 4,919.04 0.00 4,919.04 Interest Income 2,474.02 1,171.68 1,302.34 Total Income 607,651.45 363,040.25 244,611.20 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 297,544.44 281,106.95 16,437.49 Sponsorship Program 8,831.96 12,250.00 -3,418.04 Programs Expense 0.00 0.00 0.00 Publicity 56,535.61 64,625.00 -8,089.39 Brand Management 14,031.51 29,666.68 -15,635.17 Conferences 4,987.62 4,000.00 987.62 Travel Assistance Committee 2,191.81 5,000.00 -2,808.19 Tax and Audit 0.00 0.00 0.00 Treasury Services 13,150.00 13,450.00 -300.00 General & Administrative 41,176.83 41,070.99 105.84 Total Expense 438,449.78 451,169.62 -12,719.84 Net Income 169,201.67 -88,129.37 257,331.04 - Assistant Treasurer's Report CDARS discussion ongoing to confirm an appropriate amount to leave in the operational checking and the amounts to tie up in CDARS. Emirio tax issue for payment being actively worked and almost completed. GSOC Payment received Engagement letter received 9/15 for “FY 17 Engagement letter noting the capped fees of $9,500 for the Cash Basis audit and $1,500 for the FY 17 990 prep as outlined in their proposal”. Under review but expected to sign if it matches the proposed numbers. D. Secretary [Craig] To help resolve questions about IP Clearance I updated the Licenses page to include discussion about Provenance and the requirements on projects and incubator podlings for IP Clearance. This should help projects clarify when a separate IP Clearance process is needed. In August, 77 iclas, five cclas, and two grants were received and filed. E. Executive Vice President [Ross] Infrastructure No major items requiring board attention. No significant downtime during the last month. Some unexpected numbers in this infra related financials this month. Most likely misapplied cost centers. The team are investigating and will fix the errors and / or report next month as necessary. Good progress with respect to moving away from ASF owned hardware, though it has become necessary to replace some disks which were reporting a predictive failure ahead of the scheduled decommission date. Marketing and Publicity An Apache project was associated with a recent data breach at Equifax. Thanks to prompt action from the PMC and our VP Marketing and Publicity the foundation was able to respond constructively and to help identify the cause of the problem (failure to install patches addressing a previously identified exploit). We thank those involved for their prompt and efficient handling of the situation, the guidance provided to the Apache user community as a result should be considered good practice. Other than this item it's business as usual, where "usual" now includes sponsor communications. Conferences Nothing to report. TAC Nothing to report. F. Vice Chairman [Jim] In keeping with long-standing tradition, nothing to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Chris] See Attachment 8 B. Apache Legal Affairs Committee [Chris Mattmann] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Phil] See Attachment 10 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Bloodhound [cm] # Incubator [sc] # Oltu [mt] # Tajo [ps, mt] A. Apache ACE Project [Marcel Offermans / Ted] No report was submitted. B. Apache Airavata Project [Suresh Marru / Mark] No report was submitted. @Mark: pursue a report for Airavata; get dev involved for chronic missed reports C. Apache Allura Project [Dave Brondsema / Brett] See Attachment C D. Apache Any23 Project [Lewis John McGibbney / Shane] See Attachment D E. Apache Archiva Project [Olivier Lamy / Jim] See Attachment E F. Apache Atlas Project [Madhan Neethiraj / Bertrand] See Attachment F G. Apache Aurora Project [Jake Farrell / Rich] See Attachment G H. Apache Axis Project [Deepal Jayasinghe / Brett] No report was submitted. I. Apache Bahir Project [Luciano Resende / Mark] See Attachment I J. Apache Beam Project [Davor Bonaci / Phil] See Attachment J K. Apache Bigtop Project [Evans Ye / Chris] See Attachment K L. Apache Bloodhound Project [Gary Martin / Rich] No report was submitted. M. Apache BVal Project [Matt Benson / Bertrand] See Attachment M N. Apache Camel Project [Christian Mueller / Shane] See Attachment N O. Apache Cayenne Project [Michael Gentry / Ted] See Attachment O P. Apache Chemistry Project [Florian Müller / Jim] See Attachment P Q. Apache CloudStack Project [Wido den Hollander / Brett] See Attachment Q R. Apache Commons Project [Gary D. Gregory / Chris] See Attachment R S. Apache Cordova Project [Shazron Abdullah / Shane] See Attachment S T. Apache cTAKES Project [Pei J Chen / Mark] See Attachment T U. Apache Curator Project [Jordan Zimmerman / Bertrand] See Attachment U V. Apache Ambari Project [Yusaku Sako / Rich] See Attachment V W. Apache Eagle Project [Edward Zhang / Jim] See Attachment W X. Apache Falcon Project [Pallavi Rao / Phil] See Attachment X Y. Apache Felix Project [Carsten Ziegeler / Ted] See Attachment Y AA. Apache Flex Project [Alex Harui / Mark] See Attachment AA AB. Apache Flink Project [Stephan Ewen / Rich] See Attachment AB AC. Apache Fluo Project [Keith Turner / Brett] See Attachment AC AD. Apache Giraph Project [Avery Ching / Chris] No report was submitted. AE. Apache Gump Project [Stefan Bodewig / Jim] See Attachment AE AF. Apache Hama Project [Edward J. Yoon / Shane] No report was submitted. AG. Apache Helix Project [Kishore Gopalakrishna / Phil] No report was submitted. AH. Apache Hive Project [Ashutosh Chauhan / Bertrand] See Attachment AH AI. Apache Incubator Project [John D. Ament / Phil] See Attachment AI AJ. Apache Jackrabbit Project [Michael Dürig / Chris] See Attachment AJ AK. Apache Karaf Project [Jean-Baptiste Onofré / Ted] No report was submitted. AL. Apache Labs Project [Danny Angus / Bertrand] See Attachment AL AM. Apache Lucene Project [Tommaso Teofili / Shane] See Attachment AM AN. Apache Lucene.Net Project [Prescott Nasser / Jim] No report was submitted. AO. Apache MADlib Project [Aaron Feng / Brett] See Attachment AO AP. Apache MINA Project [Jean-François Maury / Mark] See Attachment AP AQ. Apache Mynewt Project [Justin Mclean / Rich] See Attachment AQ AR. Apache OFBiz Project [Jacopo Cappellato / Mark] See Attachment AR AS. Apache Olingo Project [Christian Amend / Rich] See Attachment AS AT. Apache OODT Project [Tom Barber / Shane] See Attachment AT AU. Apache OpenNLP Project [Jörn Kottmann / Brett] See Attachment AU AV. Apache OpenWebBeans Project [Mark Struberg / Chris] See Attachment AV AW. Apache Pig Project [Daniel Dai / Jim] See Attachment AW AX. Apache Pivot Project [Roger Whitcomb / Bertrand] See Attachment AX AY. Apache Polygene Project [Paul Merlin / Ted] See Attachment AY AZ. Apache Portable Runtime (APR) Project [Nick Kew / Phil] See Attachment AZ BA. Apache Portals Project [David Sean Taylor / Mark] See Attachment BA BB. Apache Sentry Project [Alex Kolbasov / Bertrand] See Attachment BB BC. Apache ServiceMix Project [Krzysztof Sobkowiak / Shane] See Attachment BC BD. Apache Shiro Project [Les Hazlewood / Rich] See Attachment BD BE. Apache Sling Project [Carsten Ziegeler / Ted] See Attachment BE BF. Apache SpamAssassin Project [Sidney Markowitz / Jim] See Attachment BF BG. Apache Stanbol Project [Fabian Christ / Brett] No report was submitted. BH. Apache Storm Project [P. Taylor Goetz / Chris] See Attachment BH BI. Apache Streams Project [Steve Blackmon / Phil] See Attachment BI BJ. Apache Synapse Project [Isuru Udana / Mark] See Attachment BJ BK. Apache SystemML Project [Deron Eriksson / Jim] See Attachment BK BL. Apache Tajo Project [Hyunsik Choi / Phil] See Attachment BL @Phil: engage with PMC to see what is going on BM. Apache Thrift Project [Jake Farrell / Bertrand] See Attachment BM BN. Apache Tiles Project [Mick Semb Wever / Chris] See Attachment BN BO. Apache Tomcat Project [Mladen Turk / Brett] See Attachment BO BP. Apache Twill Project [Terence Yim / Ted] See Attachment BP BQ. Apache UIMA Project [Marshall Schor / Rich] See Attachment BQ BR. Apache VCL Project [Andy Kurth / Shane] See Attachment BR BS. Apache Wicket Project [Martijn Dashorst / Ted] See Attachment BS BT. Apache Yetus Project [Sean Busbey / Phil] See Attachment BT BU. Apache ZooKeeper Project [Flavio Junqueira / Mark] See Attachment BU BV. Apache Marmotta Project [Jakob Frank / Phil] See Attachment BV BW. Apache Oltu Project [Antonio Sanso / Phil] No report was submitted. BX. Apache Serf Project [Bert Huijben / Phil] See Attachment BX BY. Apache Usergrid Project [Todd Nine / Phil] No report was submitted. BZ. Apache Xalan Project [Steven J. Hathaway / Phil] See Attachment BZ CA. Apache Xerces Project [Michael Glavassevich / Phil] No report was submitted. Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache Distributed Release Audit Tool (DRAT) Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of opensource software, for distribution at no charge to the public, related to large scale code license analysis, auditing and reporting. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Distributed Release Audit Tool (DRAT) Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Apache Distributed Release Audit Tool (DRAT) be and hereby is responsible for the creation and maintenance of software related to large scale code license analysis, auditing and reporting; and be it further RESOLVED, that the office of "Vice President, Apache Distributed Release Audit Tool (DRAT) " be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Distributed Release Audit Tool (DRAT) Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Distributed Release Audit Tool (DRAT) Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Distributed Release Audit Tool (DRAT) Project: * Tom Barber * Wayne Burke * Brian Fox * Chris Mattmann * Lewis John McGibbney * Tyler Palsulich * Paul Ramirez * Karanjeet Singh * Michael James Joyce * Steven Francus NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris Mattmann be appointed to the office of Vice President, Apache Distributed Release Audit Tool (DRAT) , to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed Special Order 7A, Establish the Apache Distributed Release Audit Tool (DRAT) Project, was approved by Unanimous Vote of the directors present. B. Change the Apache HBase Project Chair WHEREAS, the Board of Directors heretofore appointed Andrew Purtell to the office of Vice President, Apache HBase, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrew Purtell from the office of Vice President, Apache HBase, and WHEREAS, the Project Management Committee of the Apache HBase project has chosen by vote to recommend Misty Stanley-Jones as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrew Purtell is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache HBase, and BE IT FURTHER RESOLVED, that Misty Stanley-Jones be and hereby is appointed to the office of Vice President, Apache HBase, 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 7B, Change the Apache HBase Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache Yetus Project Chair WHEREAS, the Board of Directors heretofore appointed Sean Busbey to the office of Vice President, Apache Yetus, and WHEREAS, the Board of Directors is in receipt of the resignation of Sean Busbey from the office of Vice President, Apache Yetus, and WHEREAS, the Project Management Committee of the Apache Yetus project has chosen by vote to recommend Allen Wittenauer as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Sean Busbey is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Yetus, and BE IT FURTHER RESOLVED, that Allen Wittenauer be and hereby is appointed to the office of Vice President, Apache Yetus, 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 Yetus Project Chair, was approved by Unanimous Vote of the directors present. D. Change the Apache Community Development Project Chair WHEREAS, the Board of Directors heretofore appointed Ulrich Stärk (uli) to the office of Vice President, Apache Community Development, and WHEREAS, the Board of Directors is in receipt of the resignation of Ulrich Stärk from the office of Vice President, Apache Community Development, and WHEREAS, the Project Management Committee of the Apache Community Development project has chosen by vote to recommend Sharan Foga (sharan) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ulrich Stärk is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Community Development, and BE IT FURTHER RESOLVED, that Sharan Foga be and hereby is appointed to the office of Vice President, Apache Community Development, 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 Community Development Project Chair, was approved by Unanimous Vote of the directors present. E. Establish the Apache RocketMQ Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache RocketMQ Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache RocketMQ Project be and hereby is responsible for the creation and maintenance of software related to a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data; and be it further RESOLVED, that the office of "Vice President, Apache RocketMQ" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache RocketMQ Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache RocketMQ Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache RocketMQ Project: * Bruce Snyder * Justin Mclean * Jim Jagielski * Willem Ning Jiang * Von Gosling * Xiaorui Wang * Xinyu Zhou * Zhanhui Li * Jixiang Jin * Zhendong Liu NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiaorui Wang be appointed to the office of Vice President, Apache RocketMQ, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache RocketMQ PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache RocketMQ Project; and be it further RESOLVED, that the Apache RocketMQ Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RocketMQ podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RocketMQ podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7E, Establish the Apache RocketMQ Project, was approved by Unanimous Vote of the directors present. F. Change the Apache Flex Project Chair WHEREAS, the Board of Directors heretofore appointed Alex Harui (aharui) to the office of Vice President, Apache Flex, and WHEREAS, the Board of Directors is in receipt of the resignation of Alex Harui from the office of Vice President, Apache Flex, and WHEREAS, the Project Management Committee of the Apache Flex project has chosen by vote to recommend Tom Chiverton (tomc) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Alex Harui is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Flex, and BE IT FURTHER RESOLVED, that Tom Chiverton be and hereby is appointed to the office of Vice President, Apache Flex, 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 7F, Change the Apache Flex Project Chair, was approved by Unanimous Vote of the directors present. G. Change the Apache Pig Project Chair WHEREAS, the Board of Directors heretofore appointed Daniel Dai to the office of Vice President, Apache Pig, and WHEREAS, the Board of Directors is in receipt of the resignation of Daniel Dai from the office of Vice President, Apache Pig, and WHEREAS, the Project Management Committee of the Apache Pig project has chosen by vote to recommend Koji Noguchi as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Daniel Dai is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Pig, and BE IT FURTHER RESOLVED, that Koji Noguchi be and hereby is appointed to the office of Vice President, Apache Pig, 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 7G, Change the Apache Pig Project Chair, was approved by Unanimous Vote of the directors present. H. Change the Apache River Project Chair WHEREAS, the Board of Directors heretofore appointed Patricia Shanahan to the office of Vice President, Apache River, and WHEREAS, the Board of Directors is in receipt of the resignation of Patricia Shanahan from the office of Vice President, Apache River, and WHEREAS, the Project Management Committee of the Apache River project has chosen by vote to recommend Peter Firmstone as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Patricia Shanahan is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache River, and BE IT FURTHER RESOLVED, that Peter Firmstone be and hereby is appointed to the office of Vice President, Apache River, 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 7H, Change the Apache River Project Chair, was approved by Unanimous Vote of the directors present. I. Establish the Apache Royale Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to improving developer productivity in creating applications for wherever Javascript runs (and other runtimes). NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Royale Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Royale Project be and hereby is responsible for the creation and maintenance of software related to improving developer productivity in creating applications for wherever Javascript runs (and other runtimes); and be it further RESOLVED, that the office of "Vice President, Apache Royale" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Royale Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Royale Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Royale Project: * Harbs * Yishay Weiss * Alex Harui * Peter Ent * Josh Tynjala * Piotr Zarzycki * Carlos Rovira * Erik de Bruin * Omprakash Muppirala * Frédéric Thomas * Olaf Krüger * Michael Schmalle * David Fisher NOW, THEREFORE, BE IT FURTHER RESOLVED, that Harbs be 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; and be it further RESOLVED, that the Apache Royale Project be and hereby is tasked with the migration and rationalization of the Apache Flex resources pertaining to FlexJS; and be it further RESOLVED, that all responsibilities pertaining to Apache FlexJS encumbered upon the Apache Flex Project are hereafter discharged. Special Order 7I, Establish the Apache Royale Project, unanimous, with Bertrand abstaining J. Establish the Apache Kibble Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an interactive project activity analyzer and aggregator NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Kibble Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Kibble Project be and hereby is responsible for the creation and maintenance of software related to an interactive project activity analyzer and aggregator; RESOLVED, that the office of "Vice President, Apache Kibble" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Kibble Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Kibble Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Kibble Project: * Daniel Gruno * Ulises Beresi * Daniel Takamori * Sean Palmer * David Nalley * Rich Bowen * Sally Khudairi * Christofer Dutz * Sharan Foga * Herve Boutemy * Larry McCay NOW, THEREFORE, BE IT FURTHER RESOLVED, that Rich Bowen be appointed to the office of Vice President, Apache Kibble, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Kibble PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Kibble Project. Special Order 7J, Establish the Apache Kibble Project, was tabled. 8. Discussion Items 9. Review Outstanding Action Items * Mark: Take suggestions for improving communication back to the project [ Flex 2017-06-21 ] Status: Complete * Ted: Discuss state of development with PMC; encourage on-list development [ Tajo 2017-06-21 ] Status: * Shane: contact the project and strongly encourage them to propose a new chair and report next month [ Axis 2017-07-19 ] Status: * Chris: pursue a report for Hama; is a new chair needed? [ Hama 2017-07-19 ] Status: * Shane: work with the Axis community to help with governance issues [ Axis 2017-08-16 ] Status: In (slow) progress but I'm not sure the prognosis is good. * Ted: pursue a report for Community Development; look at previous examples of [ Community Development 2017-08-16 ] Status: * Chris: follow up with PMC: critical bugs fixes need release [ Giraph 2017-08-16 ] Status: * Rich: follow up to see if the project is still viable [ Hama 2017-08-16 ] Status: Two PMC members responded with a suggestion that they'd move to the Attic. Shane sent another followup last week, but there's been no response to that yet. * Brett: pursue a better report for next time [ Helix 2017-08-16 ] Status: * Jim: follow up to document the resolution of ignite.run issue next board [ Ignite 2017-08-16 ] Status: Reminder sent * Brett: discuss board comments with incubator pmc [ Incubator 2017-08-16 ] Status: * Brett: follow up on board comments for next report [ Libcloud 2017-08-16 ] Status: * Jim: follow up with trademark assignment issue [ MADlib 2017-08-16 ] Status: * Brett: pursue a report for MINA [ MINA 2017-08-16 ] Status: present * Mark: pursue a report for Oltu [ Oltu 2017-08-16 ] Status: In progress. * Shane: follow up with PMC: why no new PMC members [ REEF 2017-08-16 ] Status: Reef replied (finally) on board@, and is adding a new PMC member now. * Rich: pursue a better report for Serf [ Serf 2017-08-16 ] Status: Complete * Ted: pursue a report for Xalan [ Xalan 2017-08-16 ] Status: * Jim: follow up with the PMC to get a public statement out [ Discussion Items 2017-08-16 ] Status: On-going 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:27 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] * Working with JimJag re shipping of swag to All Things Open * Coordinated w/Sally and Sharan re booth equipment (banners and table cloth) for European events. ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] * ISSUES FOR THE BOARD Long term, the current model for providing trademark support to our projects is not working. The number of questions that are either already answered by documentation (meaning PMCs aren't aware of it) or that require trademark expertise (meaning Shane or counsel) continues to grow, as do the number of tasks requiring officer signature or interaction. Will be working over the next several months to propose potential alternatives; this is just a heads up that major improvements are needed over the next year. * OPERATIONS A busy month as various PMCs and companies (who ask us questions) return from summer holidays. A scam email about .cn domain registrations brings up a good point we should consider (additional volunteer energy willing): should we consider additional defensive domain registrations at common top level domains? We have cases of domain squatters using our brands to direct users elsewhere, and likely have more cases than are reported to us. Website Analytics still show the majority of users come to a direct link, are from Android or Windows (curious!), and start on the home page or /list page, and tend not to click through to many pages. I gave a new "Who Owns That Open Source Brand" talk at OSSummit, which was very well received and I think opened some eyes about the importance of trademarks. I've been invited to co-present "Trademarks in Open Source" at PLI's Open Source Software legal training conference again in December. * REGISTRATIONS & CONTRACTS A large number of renewals of existing registrations as well as several other assignments (MADLib, HAWQ) or legal agreements are still in process with counsel. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Kevin A. McGrail] Meetings semi-monthly with Virtual continue between KAM and Lynsey Good progress continues on cleaning up the sponsor records. Before the next board meeting, we’re planning to remove unpaid sponsors off the thanks page. G Suite instance is up and running - gsuite.cloud.apache.org If there are concerns about where fundraising is storing data, who needs access, etc. please let me know. https://blogs.apache.org/foundation/entry/success-at-apache-meritocracy wristbands very successful and very well received. Also posted re: Equifax with official hat on at https://www.linkedin.com/pulse/act-ii-equifax-tries-fails-throw-apache-struts- under-bus-mcgrail/ Shipments to people who requested bracelets is complete with two exceptions and my firm is donating the labor to process everything. Slide deck at the 99% good to go mark. Many thanks to Sally. Received the ASF Credit Card for KAM. Directed sponsorship to unify with inkind sponsors is coming along with discussions ongoing with numerous players. I expect to unify this and have a policy before the November board meeting. Attending All Things Open on ASF Behalf Attending FOSDEM on ASF Behalf Likely to attend Berlin Buzzwords & FOSS Backstage on ASF Behalf Thanks again to Sally and Hadrian for helping pin down sponsors as well as continued work from Virtual. We’ve got renewals coming, invoices going and some bronze sponsors adding as well. We lost some sponsors, gained some and renewed some we thought we had lost. Sponsor onboarding process is getting smoother with notes about sponsor agreement and automating the process more in the works Huawei talking to John D Ament re:incubation and potentially bringing some projects under our umbrella. Multi-year commit from sponsors is being well received and helping with getting Bronze sponsors who are committed to the foundation’s long-term success. Passed the $10K mark in donations from Hopsie (started in March) Would like to give Ambassadors a VP Titles like VP Sponsor Relations Draft of Who can Sponsor the ASF? policy in Google Docs for comments: https://drive.google.com/open?id=18xDS-IO1TG15ZsI26Wk5aXvsRhrNLMozrHYXjyvqaVA ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: we are on budget and on schedule with no vendor payments due at this time. II. Cross-committee Liaison: work with ASF Fundraising continues. Sally Khudairi completed the new pitch deck has provided a master document containing speaking points relevant to Sponsor solicitation/education. She continues to lead Sponsor engagement and outreach with the "ambassador" program, and has helped secure a renewal at the Gold level (downgraded from Platinum), and continues to hold budgeting/renewal/outreach meetings with existing Sponsors. Work continues on individual giving and donor outreach. In addition, Sally continues to work with a handful of Sponsors that are actively involved with some projects in the Apache Incubator, mostly in the realm of project promotions and marketing. The ASF Quarterly Operations Summary for Q1FY2018 (May-July 2017) was published with thanks to Rich Bowen, Shane Curcuru, Sharan Foga, Chris Mattmann, Kevin McGrail, Sam Ruby, Greg Stein, and Tom Pappas for their contributions. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 14 September 2017 - MEDIA ALERT: The Apache Software Foundation Confirms Equifax Data Breach Due to Failure to Install Patches Provided for Apache® Struts™ Exploit - 9 September 2017 - The Apache® Software Foundation Issues Statement on Equifax Security Breach - 22 August 2017 - The Apache Software Foundation Announces Apache® MADlib™ as a Top-Level Project - 17 August 2017 - The Apache Software Foundation Welcomes Phil Steitz as Chairman IV. Informal Announcements: 11 items were published on the ASF "Foundation" Blog. 2 "Success at Apache" blog posts were published. 5 Apache News Round-ups were issued, with a total of 165 weekly summaries published to date. We tweeted 35 items, and have 43.6K followers on Twitter. We posted 11 items on LinkedIn, which garnered more than 170K organic impressions in total. V. Future Announcements: three 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 13 media queries. The ASF received 3,239 press clips vs. last month's clip count of 1,599. Media coverage of Apache projects yielded 7,634 press hits vs. last month's 1,302. We've had another instance of a project requiring crisis communications, which, given our all-volunteer community, has proven challenging with identifying and securing appropriate, prepared, and available spokespeople in a very short timeframe. Having said that, we successfully worked with the Apache Struts PMC and ASF Security team on responding to dozens of media queries and issuing two official statements in response to the Equifax security breach. Special thanks to everyone who helped with escalating the issue internally, and to René Gielen, Lucasz Lenart, Mark Cox, and Mark Thomas for their editorial contributions and collaboration with preparing interview responses, as well as to Chris Mattmann, who participated in same-day broadcast media interviews. VII. Analyst Relations: we received 3 analyst queries during this timeframe. Apache was mentioned in 10 reports and 2 Big Data Webinars by Gartner, 2 reports by Forrester, 8 reports by 451 Research, and 1 report by IDC. VIII. Graphics: Sally created new graphics and coordinated with Sharan Foga and Melissa Warnkin on the production of several signage and promotional items to be used at various conferences. IX. Events liaison: we will continue to support VP Conferences as ApacheCon evolves. We have been working with ComDev to meet their promotional needs at numerous events, and have been liaising with several Sponsors on events they are backing or participating in, as well as external community partner opportunities. X. Newswire accounts: we have 8 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017; unused announcements will be applied towards our new contract that ends in December 2019. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] General ======= Infra continues to operate as expected, and there are no issues for the President or the Board at this time. Finances ======== There appears to be some strange numbers in this month's financials, so some further analysis will be done over the next couple weeks. This is likely a simple matter of misapplied cost centers. Will provide an update next month. Short Term Priorities ===================== - Upgrade Confluence, Jira, and Jenkins. We will schedule these for weekends, as several hours of downtime will be required for each. Long Range Priorities ===================== - First priority: shift towards puppet-managed cloud-based services. - Various automation, which likely will involve working with the Whimsy folks to loop this into their product. General Activity ================ - Seven machines de-racked at OSU/OSL, as part of our mission to move from ASF-owned hardware to cloud-based infrastructure - Several disks at OSL were reporting a predictive failure, so we ordered a few more and are working with OSL to get them installed and looped back into the RAID system. Even though these systems are on a path to decommission, a disk failure would have been much more expensive, than the cost of the replacement. - Towards our goal to decommission minotaur, mbox-vm has been created to function as our official archive of all mail content/archives. Minotaur is serving this function today, with mail-search.a.o and mail-archive.a.o slaving their content from minotaur. mbox-vm is still a work in progress. Uptime Statistics ================= The Infra team has continued its excellent uptime record. We had no significant downtime on any system this past month. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Rich Bowen] Nothing to report this month. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin] No issues to report at this time ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] The appeal vote on Director's decision to pubish the EME standard has run. Within ASF there was more discussion on board@. Combining that with the earlier members@ discussions, I formaly abstained, with comments wishing to see better protection for independent developers and security researchers. ----------------------------------------- Attachment 9: Report from the Apache Legal Affairs Committee [Chris Mattmann] Facebook decided against changing the license of the React.js framework [1] and as such React.js is not useable in any Apache projects per Legal's original guidance and transition period. Projects should have no dependencies on React.js. Questions should be directed to legal-discuss@ and/or to the LEGAL JIRA system [2]. Eclipse released the Eclipse Public License v2.0, and a discussion thread was raised wondering whether Apache legal had any comment. At this point in time, there are no comments, and there has not be a classification of EPLv2.0 in the Apache legal/resolved.html classification system. There was some confusion regarding a software grant from an external company regarding an explicit list of third party dependencies identified in the regular grant form. Confusion about the grant, and information about the project is described in LEGAL-327 [3]. The resolution to this issue was that Legal told the project to go ahead and accept the software grant and then in the future to work with the upstream donating entity to remove such information from future grants. Additional conversation surrounding LEGAL-327 and Legal's role in Incubator software grants, etc., led to the development and addition of information on the Whimsy Roster Chart for VP, Legal [4]. The additional information describes the process for interacting with VP Legal, our Pro Bono Counsel and the mailing lists surrounding them. Other traditional legal questions (about whether License X can be included in project Y, etc.) are being answered slowly and usually in the order received. [1] https://s.apache.org/k3Aj [2] https://issues.apache.org/jira/browse/LEGAL [3] https://issues.apache.org/jira/browse/LEGAL-327 [4] https://whimsy.apache.org/roster/orgchart/vp-legal ----------------------------------------- Attachment 10: Report from the Apache Security Team Project [Mark J. Cox] We've started an audit of the various security@[tlp] lists to ensure that only active project members and PMC members are subscribed. Stats for August 2017: 7 CVEs issued to projects (some may not be public yet). e-mails to security@ 5 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to "Apache" mentioned in OSS licenses 4 Support Questions 13 Direct Vulnerability report to security@apache.org 1 [httpd] 1 [zepplin] 2 [mesos] 1 [apr/subversion] 1 [batik] 2 [airflow] 2 [site] rejected 1 [opennlp] 1 [xerces] 1 [drill] 7 Vulnerabilities reported to projects 1 [httpd] 2 [kafka] 1 [cloudstack] 1 [zookeeper] 1 [nifi] 1 [hadoop] ----------------------------------------- Attachment A: Report from the Apache ACE Project [Marcel Offermans] ----------------------------------------- Attachment B: Report from the Apache Airavata Project [Suresh Marru] ----------------------------------------- Attachment C: Report from the Apache Allura Project [Dave 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: - Made a release. - Working on moving forge-allura.a.o to new hardware, nearly done. https://issues.apache.org/jira/browse/INFRA-13262 - Facebook BSD+patents license of React.js affects us, but hopefully won't be too much work to replace it before our next release. - Bugfixes and small improvements continue ## Health report: Development is slow but steady. Moving forge-allura.a.o to new hardware has forced us to re-do some configuration, but will give us a nice example to share of how to setup & configure Allura for production. ## PMC changes: - No changes. - Currently 14 PMC members. - Kenton Taylor was added to the PMC on Sun Jan 22 2017 ## Committer base changes: - No changes. - Currently 14 committers. - Kenton Taylor was added as a committer on Thu Jan 19 2017 ## Releases: - 1.7.0 was released on Mon Jun 26 2017 ----------------------------------------- Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (Any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity has been pretty stable. We are pretty quiet mailinglist-wise. ## Health report: We are very happy to have persistent contributor Jacek Grzebyta join the PMC and Committership base. William L. Anderson recently turned emeritus. ## PMC changes: - Currently 14 PMC members. - 1 new PMC member added in the last 3 months - 1 PMC member turned emeritus in the last 3 months - Last PMC addition was Jacek Grzebyta on Thu Jul 27 2017 ## Committer base changes: - Currently 14 committers. - Jacek Grzebyta was added as a committer on Thu Jul 27 2017 ## Releases: - Last release was 2.0 on Thu Feb 16 2017 ## Mailing list activity: It is positive to see the dev@ emails up from last quarter. dev@ remains our most popular list with mostly JIRA messages. - dev@any23.apache.org: - 35 subscribers (up 1 in the last 3 months): - 213 emails sent to list (89 in previous quarter) - user@any23.apache.org: - 50 subscribers (down -1 in the last 3 months): - 3 emails sent to list (7 in previous quarter) ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Archiva Project [Olivier Lamy] ## Description: Apache Archiva software is an extensible repository management tool that helps taking care of your own personal or enterprise-wide build artifact repository. ## Issues: there are no issues requiring board attention at this time ## Activity: We have started some refactoring. Moving from Jackrabbit to Oak. And now discussing even more changes. ## Health report: We have enough PMC to cut release. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Martin Stockhammer on Mon Apr 10 2017 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Martin Stockhammer at Thu Sep 22 2016 ## Releases: - Last release was 2.2.3 on Tue May 16 2017 ## Mailing list activity: - users@archiva.apache.org: - 231 subscribers (down -2 in the last 3 months): - 9 emails sent to list (12 in previous quarter) - dev@archiva.apache.org: - 107 subscribers (up 1 in the last 3 months): - 45 emails sent to list (56 in previous quarter) - issues@archiva.apache.org: - 36 subscribers (up 1 in the last 3 months): - 31 emails sent to list (154 in previous quarter) - notifications@archiva.apache.org: - 15 subscribers (up 1 in the last 3 months): - 73 emails sent to list (113 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment F: Report from the Apache Atlas Project [Madhan Neethiraj] ## Description: Apache Atlas is a scalable and extensible set of core foundational governance services that enables enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the complete enterprise data ecosystem ## Issues: There are no issues requiring board attention at this time. ## Activity: - Released 0.8.1, the first release after graduation - Completed backend work on relationships as first class type - Working on new features like tag-propagation, business catalog, Open Metadata & Governance, Virtual Data Connector, Automated Discovery ## Health report: - Added 1 new committer in last month - No new contributors added in last month ## PMC changes: - Currently 33 PMC members - No new PMC members added in last month - Last PMC member addition was on 6/21/2017 ## Committer base changes: - Currently 36 committers - 1 new committer added in last month, on 8/15/2017 - Last addition to committer role was Mandy Chessell ## Releases: 0.8.1 was released on 08/29/2017 0.8-incubating was released on 03/16/2017 0.7.1-incubating was released on 01/26/2017 0.7-incubating was released on 07/09/2016 0.6-incubating was released on 12/31/2015 0.5-incubating was released on 07/11/2015 ----------------------------------------- Attachment G: Report from the Apache Aurora Project [Jake Farrell] 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. Project Status --------- The Apache Aurora community has continued to see growth from new contributors over the last quarter while working on our latest 0.18.0 release, which was successfully released on June 19th, 2017. There has been a great open discussions occurring on the mailing lists surrounding hot standby in replicas to reduce failover time and a design doc has been proposed. Community --- Latest Additions: * Committer addition: Santhosh Kumar Shanmugham, 2.9.2017 * PMC addition: Mehrdad Nurolahzade, 2.24.2017 Issue backlog status since last report: * Created: 11 * Resolved: 14 Mailing list activity since last report: * @dev 114 messages * @user 3 messages * @reviews 317 messages Releases --- Last release: Apache Aurora 0.18.0 released 06.19.2017 ----------------------------------------- Attachment H: Report from the Apache Axis Project [Deepal Jayasinghe] ----------------------------------------- Attachment I: Report from the Apache Bahir Project [Luciano Resende] Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Currently, Bahir provides extensions to multiple distributed analytic platforms, extending their reach with a diversity of streaming connectors and SQL data sources. Community Activity: Apache Bahir community has been actively working on supporting and enhancing previously available Apache Spark extensions and new extensions continue to be proposed to the project. The community continues to actively keep up with the Apache Spark release cadence, having recently released the extensions based on Apache Spark 2.2.0. Apache Bahir has also integrated various extensions for Apache Flink analytical platform. Currently, the following extensions are available in Apache Bahir for Flink: ActiveMQ, Akka, Flume, Netty, and Redis; there has been some discussion about performing a release but the community seems to have decided to wait for the next Flink release that should be coming next month. Issues: * No known issues Releases: 08/22/2017 - Bahir for Spark 2.2.0 07/11/2017 - Bahir for Spark 2.1.1 05/24/2017 - Bahir for Flink 1.0 03/05/2017 - Bahir for Spark 2.1.0 01/28/2017 - Bahir for Spark 2.0.2 10/28/2016 - Bahir for Spark 2.0.1 Committers or PMC changes (Currently 9 PMC / 37 committers) 09/14/2017 - Esteban Laver becomes Apache Bahir committer 04/05/2017 - Robert Metzger becomes Apache Bahir PMC 03/13/2017 - Christian Kadner becomes Apache Bahir PMC 11/30/2016 - Christian Kadner voted as Apache Bahir committer 10/18/2016 - Robert Metzger voted as Apache Bahir committer Trademark/Branding: * No known issues. Legal Issues: * None ----------------------------------------- Attachment J: Report from the Apache Beam Project [Davor Bonaci] ## 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 that require the Board's attention at this time. ## Activity: In the previous quarter, we had achieved a major milestone for the project -- the completion of the first stable release, version 2.0.0. It signified a statement from the community that it intends to maintain API stability with all releases for the foreseeable future, and making Beam suitable for enterprise deployment. In this quarter, we continued to build on that momentum and kept interconnecting additional execution engines and data storage/messaging systems, and serve as a glue in the ecosystem. On the execution side, the Apache Gearpump (incubating) runner effort has merged into the master branch as a new component, and will be included in the next release. JStorm, Apache Hadoop MapReduce, and Apache Tez runners are making further progress. The Spark runner migration from Apache Spark 1.6 to 2.x is nearing completion. A major effort to create an SQL extension, based on Apache Calcite, got merged into the master branch as a new component, and is slated for the next release. On the IO connector side, a connector for Apache Solr has been contributed, and additional connectors for Redis, Apache DistributedLog (incubating), Apache Parquet, RabbitMQ, and Advanced Message Queuing Protocol (AMQP) are in progress. Major improvements to file-based connectors have been contributed, making them capable of handling dynamic source and sink locations. We have published two technical blog posts regarding the recent innovation in the project: - Powerful and modular IO connectors with Splittable DoFn in Apache Beam - Timely (and Stateful) Processing with Apache Beam Beam was covered at several industry conferences over the past quarter, including the DataWorks Summit Sydney 2017, Kafka Summit San Francisco 2017, YOW! Data Sydney 2017, and Flink Forward Berlin 2017. Going forward, the main focus continues to be on the user growth, with outreach continuing across conferences and meetups. On the technical side, the next major milestone is the completion of the portability framework across all components of the project, which would, among other benefits, extend the Python SDK to all Beam runners. ## Health report: The community continues to grow steadily, as follows: - For the first time since the top-level project was established, we have added new PMC members, and have added a record of five new committers in the quarter. - The number of contributors continues to increase. We are now at 196 unique code contributors, up from 176 in the last report. - Releases continue at a regular pace of 1-2 months per release. - The mailing list subscribers continue to increase. ## PMC changes: Currently 16 PMC members. Two new PMC members have been added since the last report: - Ahmet Altay was added to the PMC on Thu Aug 10 2017. - Aviem Zur was added to the PMC on Thu Aug 10 2017. ## Committer base changes: Currently 29 committers. Five new committers have been added since the last report: - Jingsong Lee was added as a committer on Thu Jun 22 2017. - Reuven Lax was added as a committer on Fri Aug 11 2017. - James Xu was added as a committer on Fri Aug 11 2017. - Mingmin Xu was added as a committer on Fri Aug 11 2017. - Manu Zhang was added as a committer on Fri Aug 11 2017. ## Releases: Since the last report, Apache Beam has published one release with another one currently being worked on: - 2.1.0 was released on Mon Aug 21 2017. - 2.2.0 is being prepared, with an expected publication in September 2017. Version 2.0.0 was the first release that comes with API stability guarantees. Going forward, we expect to publish a release every 1-2 months. ## Mailing list activity: Mailing list subscriptions continues to increase. The small decrease in the email volume is the effect of comparison with the previous quarter, which included the major effort of publishing the first stable release. - dev@beam.apache.org - 451 subscribers (up 26 in the last 3 months). - 1024 emails sent to list (1139 in previous quarter). - user@beam.apache.org - 445 subscribers (up 56 in the last 3 months). - 413 emails sent to list (512 in previous quarter). ## JIRA activity: JIRA activity continues to be healthy. The small decrease is the effect of comparison with the previous quarter, which included the major effort of publishing the first stable release. - 505 JIRA tickets created in the last 3 months (725 in the previous quarter). - 278 JIRA tickets closed/resolved in the last 3 months (650 in the previous quarter). ----------------------------------------- Attachment K: Report from the Apache Bigtop Project [Evans Ye] ## 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: None. ## Activity: The PMC has done a scan for all Bigtop upstream projects to identify whether Facebook's BSD+Patents license effects Apache Bigtop[1]. Turns out only Apache Kafka uses RocksDB. The Kafka artifacts are removed from Bigtop's S3 repository on 8/31 with an announcement prior to the deletion. The next bug fixing release 1.2.1 is delayed due to above license issue. The RM plan to roll out the release at the end of Sept. ## PMC changes: Last PMC addition was Amir Sanjar on Mon May 08 2017 Currently 25 PMC members. ## Committer base changes: Last committer addition was Jonathan Kelly on Thu Dec 08 2016 Currently 35 committers. ## Releases: Last release was 1.2.0 on Tue Apr 04 2017 ## Links [1]. https://issues.apache.org/jira/browse/LEGAL-322 ----------------------------------------- Attachment L: Report from the Apache Bloodhound Project [Gary Martin] ----------------------------------------- Attachment M: Report from the Apache BVal Project [Matt Benson] ## Apache BVal Report September 2017 ## - 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: - Version 2.0 of the Java Bean Validation specification was finalized during the past quarter; work progresses on the corresponding Apache BVal version 2.0 as resources are available. ## Health report: - BVal continues to be maintained by obligation; this remains tenable as not a great many issues have arisen requiring urgent attention. ## PMC changes: - Currently 14 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 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache Camel Project [Christian Mueller] ## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - The spam mails we are receiving on Nabble and also on the moderate mail accounts are painful. - We are focusing the development of the next minor release Apache Camel 2.20.0 expected to be released at the end of September 2017. - Finalizing Camel 2.18.5, which will be our last planned 2.18.x maintenance release. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - We have started to deprecate APIs and components that will be dropped for Camel 3.0 - No progress so far on carrying out the logo changet. ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 30 PMC members. - No addition since the last report. - Last PMC was added on Sun Jul 02 2017 ## Committer base changes: - Currently 58 committers. - no addition since the last report - Last committer was added on Thu Jun 08 2017 ## Releases: - 2.19.3 was released on Sep 14 2017 ## Mailing list activity: - Mailing list activity stays at a high level. ----------------------------------------- Attachment O: Report from the Apache Cayenne Project [Michael Gentry] # Apache Cayenne Board Report, September 2017 ## 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 - Cayenne 3.1 (stable) - Maintenance only. - Cayenne 4.0 (development) - The release of our first 4.0 beta (4.0.B1) marked a significant milestone for Cayenne as the API is frozen, barring any major issues, and development effort is only for bug fixes and documentation for 4.0.B2 leading up to the final release of 4.0. - Cayenne 4.1 (development) - With the release of 4.0.B1, development efforts have begun on the next release, 4.1, which already include compelling updates, such as vastly improved memory utilization, progress towards eliminating dependencies on external frameworks, an updated Cayenne Modeler cross-platform GUI mapping/modeling tool, and Java 8 support. - Website - Started working on an updated website with the goal to make it cleaner, more modern, and mobile-friendly. ## Health Report Cayenne is healthy. The framework is under active development. The finishing touches (bug fixes and documentation) are being put on 4.0 beta in order to release 4.0 final. Active development of new features has begun for 4.1. We have a stable user and developer community. ## PMC Changes - Currently 9 PMC members. - Nikita Timofeev was added to the PMC on Sun Jun 25 2017. ## Committer Base Changes - Currently 22 committers. - Hugi Thordarson was added as a committer on Mon Jun 19 2017. ## Releases - Cayenne 4.0.B1 on Mon Jun 12 2017. ## JIRA Activity - 34 JIRA tickets created in the last 3 months. - 29 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment P: 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: - New versions of ObjectiveCMIS, PortCMIS, and cmislib have been released with bug fixes and enhancements. ## Health report: - We have a mature code base. There is no major development expected. ## PMC changes: - Currently 35 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ben Chevallereau on Thu Dec 11 2014 - We are currently voting on a new PMC member, who contributed significantly to the cmislib project. ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Sanija Shabani at Wed Nov 26 2014 ## Releases: - ObjectiveCMIS 0.6 was released on Mon Jul 31 2017 - PortCMIS 0.3 was released on Tue Jul 25 2017 - cmislib 0.6.0 was released on Thu Aug 31 2017 ## Mailing list activity: - dev@chemistry.apache.org: - 172 subscribers (down -1 in the last 3 months): - 107 emails sent to list (187 in previous quarter) ## JIRA activity: - 9 JIRA tickets created in the last 3 months - 11 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache CloudStack Project [Wido den Hollander] ## 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: there are no issues requiring board attention at this time ## Activity: With project has released version 4.9.3 (LTS) and 4.10 since the last report. At 12th September 2017: - The CloudStack Twitter (@cloudstack) account has 34,100 followers - The Github mirror of CloudStack repository has 486 stars and 590 forks ## Health report: Inside the project a discussion is going on if and how the project needs to attract additional committers. Is more diversity needed? Can you nominate or vote for a person working at the same company? These are questions we are trying to answer. ## PMC changes: - Currently 46 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rene Moser on Mon Mar 27 2017 ## Committer base changes: - Currently 112 committers. - No new committers added in the last 3 months - Last committer addition was Nicolás Vázquez at Fri Nov 25 2016 ## Releases: - Release 4.10.0 on Fri Sep 1 2017 - Release 4.9.3.0 on Tue Sep 12 2017 ## Mailing list activity: - users@cloudstack.apache.org: - 1109 subscribers (down -3 in the last 3 months): - 555 emails sent to list (471 in previous quarter) - dev@cloudstack.apache.org: - 738 subscribers (down -2 in the last 3 months): - 495 emails sent to list (2067 in previous quarter) - announce@cloudstack.apache.org: - 514 subscribers (up 14 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@cloudstack.apache.org: - 239 subscribers (up 5 in the last 3 months): - 687 emails sent to list (1767 in previous quarter) - marketing@cloudstack.apache.org: - 237 subscribers (up 2 in the last 3 months): - 21 emails sent to list (10 in previous quarter) - press@cloudstack.apache.org: - 14 subscribers (up 1 in the last 3 months) ## JIRA activity: - 117 JIRA tickets created in the last 3 months - 55 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache Commons Project [Gary D. Gregory] ## Description: - The Apache Commons project focuses on all aspects of reusable Java components. - The Apache Commons components are widely used in many projects, both within Apache and without. Any ASF committer can commit to Apache Commons. - The last report was for the meeting of June 21, 2017. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The project is active with four (4) releases this reporting period. ## Health report: - Most components in Commons are mature, but are still actively maintained (4 releases). The dev list is active. JIRA is active. Speed of responses to users is reasonable in most cases. We have 2 new PMC member, 2 new committer, and Commons is still open to any Apache Committer. - We are still experiencing some growing pains toward Commons Math 4. There is a backlog of issues in JIRA (not unlike other components) but no clear concensus in the community. Do-ocracy is likely to prevail. There is a proposal on how to move the code base forward, either as a multi-module project or multiple components within Commons. All of which can be read on the developer's mailing list. ## PMC changes: - Currently 38 PMC members. - New PMC members: - Rob Tompkins was added to the PMC on Fri Jun 30 2017 - Pascal Schumacher was added to the PMC on Fri Jun 30 2017 ## Committer base changes: - Currently 146 committers. - New commmitters: - Pascal Schumacher was added as a committer on Sat Jul 01 2017 - Carl Franklin Hall was added as a committer on Wed Jul 05 2017 ## Releases: - Apache Commons CSV-1.5 was released on Sat Sep 02 2017 - Apache Commons EMAIL 1.5 was released on Mon Jul 31 2017 - Apache Commons FILEUPLOAD 1.3.3 was released on Mon Jun 12 2017 - Apache Commons JCS-2.2 was released on Tue Aug 01 2017 ## JIRA activity: - 161 JIRA tickets created in the last 3 months - 120 JIRA tickets closed/resolved in the last 3 months Gary Gregory Apache Commons Chair ----------------------------------------- Attachment S: Report from the Apache Cordova Project [Shazron Abdullah] ## 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 had two platform releases - one minor release for iOS (4.5.0) and one major release for Browser (5.0.0). The iOS release integrated the console plugin and has updated some dependencies. The Browser release has implemented our standard platform API and now includes basic support for progressive web apps. We had a major release for our cordova serve tool (2.0.0) which now serves the web content and launches the default browser on the system. We have also had a minor release of our cordova-common library which adds the ability to include variables in the framework tag. ## Health report: Our status dashboard at http://status.cordova.io is mostly all green. We have finished moving our plugin testing to AppVeyor and Travis CI. This is the reason for all of the green badges on our status page! We still have a huge backlog of GitHub Pull Request activity, again, same as last quarter -- but it has improved. We now have direct access to GitHub for platform repos. We are waiting for Infra to move over the rest of our repos to GitBox. https://issues.apache.org/jira/browse/INFRA-14994. Once all of our repos are moved over, we plan on discussing the option of migrating our issues from Jira to GitHub and what that would look like. We are in the process of deprecating a few of our plugins which can be replaced by official W3C specs which have been implemented in the browsers of the platforms we support. We are also in the process of integrating a couple of plugins back into platforms and deprecating the plugins. This will help ease the maintenance load on the team. Again, our goal for plugins release is to have one per week as a cadence, and we have failed to do so again this quarter. We have done work on streamlining this so it will improve in the future. We have recently removed react from our plugins serach at https://plugins.cordova.io. We replaced it with preact. We aren't using react anywhere else. We have attempted to contact Cocoon.io folks multiple times about using the cordova trademark incorrectly. We haven't received a response yet. It appears their top executives have left the company. The company may have folded. ## PMC changes: - Currently 86 PMC members. - No new PMC members added ## Committer base changes: - Currently 89 committers. - No new committers added ## Releases: - cordova-browser@5.0.0 was released on Tue Aug 29 2017 - cordova-common@2.1.0 was released on Thu Aug 31 2017 - cordova-ios@4.5.0 was released on Thu Sep 07 2017 - cordova-serve@2.0.0 was released on Tue Aug 29 2017 ## JIRA activity: - 357 JIRA tickets created in the last 3 months - 278 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache cTAKES Project [Pei J 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 - Committee is actively working on updating the cTAKES Confluence website for improved documentation ## Health report: - The community continues to be moderately active. There have been an increase in new users/questions interest in the dev and user mailing lists. There is still a steep learning curve with the codebase. However, there are patches from various new users/contributors recently. ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michelle Chen on Mon Feb 02 2015 ## Committer base changes: - Currently 35 committers. - No new committers added in the last 3 months - Azad Dehghan was added as a committer on Fri Jun 03 2016 - Lewis John McGibbney was added as a committer on Fri May 27 2016 - Peter Klügl was added as a committer on Fri May 27 2016 - Richard Eckart de Castilho was added as a committer on Fri May 27 2016 ## Releases: - Last release was 4.0.0 on Apr 24 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 the subscribers in the mailing list(s) over the last quarter with the recent 4.0.0 release. - dev@ctakes.apache.org: - 234 subscribers (up 14 in the last 3 months): - 159 emails sent to list (280 in previous quarter) - user@ctakes.apache.org: - 226 subscribers (up 15 in the last 3 months): - 51 emails sent to list (77 in previous quarter) ----------------------------------------- Attachment U: 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: - A major release was accomplished since the last report ## Health report: - Apache Curator is very healthy - We'd like to see more engagement from 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.0.0 was released on Fri Jul 28 2017 ## Mailing list activity: - dev@curator.apache.org: - 52 subscribers (down -2 in the last 3 months): - 403 emails sent to list (697 in previous quarter) - user@curator.apache.org: - 161 subscribers (up 2 in the last 3 months): - 14 emails sent to list (38 in previous quarter) ## JIRA activity: - 14 JIRA tickets created in the last 3 months - 20 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment V: Report from the Apache Ambari Project [Yusaku Sako] ## Description: - Apache Ambari simplifies provisioning, managing, and monitoring of Apache Hadoop clusters. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The community managed to release Ambari 2.5.1 (261 JIRAs resolved) and 2.5.2 (286 JIRAs resolved) for stabilization on the 2.5 line. In addition to the maintenance releases, the community has been working on 2.6.0 as well as 3.0.0 for new feature / re-architecture work. Development cadence and activity remains high. We now have 90 committers and just closed a vote for 6 new committers. On June 12, 2017, an Apache Ambari meetup was held in San Jose, CA, USA, which featured the following speakers to discuss and share various aspects of Ambari: - Alejandro Fernandez (Ambari PMC/committer) - Sunitha Velpulta (Ambari contributor) - Siddharth Wagle (Ambari PMC/commiter) - Swapan Shridhar (Ambari PMC/committer) - Jayush Luniya (Ambari PMC/committer) ## PMC changes: - Currently 44 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Aravindan Vijayan on Sun Jun 04 2017 ## Committer base changes: - Currently 90 committers. - New commmitters: - Attila Magyar was added as a committer on Tue Jun 27 2017 - Balazs Bence Sari was added as a committer on Fri Jun 23 2017 ## Releases: - 2.5.2 was released on Mon Aug 28 2017 - 2.5.1 was released on Thu May 25 2017 ## Mailing list activity: - dev@ambari.apache.org: - 287 subscribers (up 11 in the last 3 months): - 41 emails sent to list (96 in previous quarter) - issues@ambari.apache.org: - 42 subscribers (up 2 in the last 3 months): - 6338 emails sent to list (7421 in previous quarter) - reviews@ambari.apache.org: - 46 subscribers (up 2 in the last 3 months): - 2086 emails sent to list (2812 in previous quarter) - user@ambari.apache.org: - 482 subscribers (up 9 in the last 3 months): - 52 emails sent to list (38 in previous quarter) ## JIRA activity: - 699 JIRA tickets created in the last 3 months - 644 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment W: 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: ## Health report: - Apache Eagle 0.5.0 is released ## PMC changes: - No new PMC members in the last 3 months - Currently 16 PMC members - Last PMC addition: Mon May 08 2017 (Deng Lingang) ## Committer base changes: - No new committers in the last 3 months - Currently 18 committers - Last committer addition was Jay Sen at Thu Mar 16 2017 ## Releases: - 0.5.0 was released on Wed Sep 06 2017 ## Mailing list activity: - dev@eagle.apache.org: - 75 subscribers (up 1 in the last 3 months): - 99 emails sent to list (192 in previous quarter) - issues@eagle.apache.org: - 19 subscribers (up 2 in the last 3 months): - 384 emails sent to list (944 in previous quarter) - user@eagle.apache.org: - 55 subscribers (up 5 in the last 3 months): - 19 emails sent to list (33 in previous quarter) ## JIRA activity: - 23 JIRA tickets created in the last 3 months - 25 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: 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 There are no issues that require board's attention at this time. STATUS Falcon 0.11 is pending release. Major features include: User space extensions or recipe feature. Publishing backlog metrics to Graphite. 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 CHANGES - Currently 25 committers. - No new committers added in the last 3 months - Sandeep Samudrala was added as a committer on Thu Mar 09 2017 RELEASES - Last release was 0.10 on Mon Aug 08 2016 MAILING LIST ACTIVITY - dev@falcon.apache.org: - 112 subscribers (down -3 in the last 3 months): - 230 emails sent to list (63 in previous quarter) JIRA ACTIVITY - 10 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Y: Report from the Apache Felix Project [Carsten Ziegeler] 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. Community The project is in good health. Questions on the user list are frequently answered, development concerns are either discussed in the mailing list or directly in the JIRA issues. Existing implementations are improved/enhanced based on community feedback. Other activities are covering implementing the new OSGi R7 specifications. PMC: The last new PMC member was added in Jul. 2016. Committers: The last new committer was added in February 2017. There are no issues requiring board attention at this time. Software Apache Felix Eventadmin 1.4.10 and Apache Felix Metatype 1.1.4 (September 1st, 2017) Apache Felix Framework 5.6.8 released (August 25th, 2017) Apache Felix Config Admin 1.8.16 (August 7th, 2017) Apache Felix Framework 5.6.6 released (July 31st, 2017) Apache Felix Http Jetty 3.4.4 (July 14th, 2017) Apache Felix Http SSLFilter 1.2.2 (July 10th, 2017) Apache Felix Dependency Manager r11 (July 1, 2017) Apache Felix SCR 2.0.12 (June 26th, 2017) ----------------------------------------- Attachment AA: Report from the Apache Flex Project [Alex Harui] Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES -Apache FlexJS 0.8.0 was released on 6/25/17. -Apache Flex SDK 4.16.0 was released on 3/10/17. -Apache Flex BlazeDS 4.7.3 was released on 3/31/17. -Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14. -Apache Flex Tool API 1.0.0 was released on 11/20/14 -Apache Flex Squiggly 1.1 was released on 10/26/14 -Apache Flex Installer 3.2.0 was released on 6/23/15. ACTIVITY The past three months saw the release of Apache FlexJS 0.8.0. This belatedly fulfilled our obligation to remove org.json dependencies from our releases. On 7/25, Adobe announced the end-of-life for Flash Player in browsers in 2020. This eliminates a significant runtime environment for Apache Flex. This news resulted in a slight increase in interest in FlexJS and some new features were developed in response to user requests. The drop in mailing list and commit activity reported in the prior quarter seems to have been temporary. The Apache Flex Installer assists users in the downloading and expanding of the runtime prerequisites such as the Adobe AIR SDK and is having running out of memory dealing with increasingly large artifacts from Adobe. As such, there is a good chance that fewer successful installs are being tracked by the Apache Flex Installer as more folks may be opting for alternative ways to install our releases. COMMUNITY -Last committer as added on 9/5/16. A discussion started last quarter about a new candidate but that candidate has not been very active lately so the discussion seems to have been suspended. -Olaf Krüger was added to the PMC on 8/28/17. -A resolution to make Tom Chiverton the next Apache Flex chair has been presented to the board. -A proposal to create a new top-level project called Apache Royale has been presented to the board. Apache Royale will take responsibility for what is now Apache FlexJS and related repos. -Latest analytics include around 800 hits per day on the Website during the work week (less on weekends). It used to be closer to 1000 hits per day but better than the 500 hits per day reported last quarter. -There were more than 2700 installs of Apache Flex 4.16.0 since its release in March 2017. TRADEMARKS -A company is promoting a software product called Flex that appears to be related to themes/styles for website visuals. Despite several attempts to contact them, they have not responded. The ASF VP Trademarks sent them an email on 11/3/16. I did not see a response and their website is still up. What is the next step? SECURITY Nothing to report (finally). ----------------------------------------- Attachment AB: 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, Hadoop, Mesos, Kafka, HBase, Cassandra, and various others. ISSUES - There are no issues that require board attention. STATUS AND ACTIVITY - The Flink community is heading towards the 1.4 release. Big threads in the current development are for example a major improvement to the deployment interoperability and elasticity, connectors, dependency management, Stream SQL. - The Flink community is reorganizing the project repository and dependencies, to make the life of users easier with respect to dependency conflicts. We created the "flink-shaded" repository in which we create shaded versions of several dependencies, relocated to a different namespace. That repository contains at this point no code, only build files. - The Flink Forward Berlin conference took place on September 11-13 with about 350 participants, representing a mixture of committers, contributors, production users, exploring users, stream processing enthusiasts, and researchers from academia. - Data Artisans announced that they plan to organise two more Flink Forward conferences next year, similar to this year: One in San Francisco in April, one in Berlin in September. - Since the last board report, two companies publicly annouced hosted managed Flink services: Eventador (http://eventador.io/) and Huawei (http://www.hwclouds.com/product/stream.html). We are in touch with the later one to update their mentioning of "Flink" to "Apache Flink". COMMUNITY PMC members added since last report: - Tzu-Li Tai was added as a PMC member on July 6th, 2017 - Chesnay Schepler was added as a PMC member on July 26th, 2017 Committers added since the last board report: - Jincheng Sun was added as a committer on July 10th, 2017 Flink currently has 33 committers and 19 PMC members. RELEASES The following releases were made since the last board report: - 1.3.1 was released on June 22nd, 2017 - 1.3.2 was released on August 5th, 2017 - shaded-1.0 was released on July 27th, 2017 ACTIVITY ON JIRA / MAILING LISTS Both user@f.a.o and dev@f.a.o lists are very active, with mails getting answered by a mix of committers and non-committers. JIRA continues to be very active (699 JIRA tickets created, 538 JIRA tickets resolved over last 3 months) ----------------------------------------- Attachment AC: Report from the Apache Fluo Project [Keith Turner] ## Description: - Apache Fluo is a distributed processing system built on Apache Accumulo. Fluo users can easily setup workflows that execute cross node transactions when data changes. These workflows enable users to continuously join new data into large existing data sets with low latency while avoiding reprocessing all data. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Work on supporting Mesos and Kubernetes is well underway and nearing completion. Completing this work will likely motivate the next release. - Posted an issue on ASF helpwanted site and had a student start working on it. ## Health report: - Since Aug 8 - 11 GitHub issues were opened and 20 closed - 16 GitHub pull request were opened and 25 were closed - 24 commits were made by 4 authors (all commiters) - One new non-committer started working a issue, but did not complete ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last month ## Committer base changes: - Currently 8 committers. - No changes in last month ## Releases: - No new releases in last month - fluo-1.1.0-incubating was released on Mon Jun 12 2017 - fluo-recipes-1.1.0-incubating was released on Thu Jun 22 2017 ## Answer to question - Craig Russell asked : "This PMC is getting very small. What can be done to make sure that the project stays viable?" - Answer : We need to grow the community and that should lead to more PMC members. To do this we plan to continue with a few releases a year and promote them. Continue to write up starter issues and promote them. Continue to speak at conferences. Continue to be a welcoming community. Continue to engage with other communities. ----------------------------------------- Attachment AD: Report from the Apache Giraph Project [Avery Ching] ----------------------------------------- Attachment AE: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == Just before the report was prepared we noticed vmgump-vm3 to not be available, we are looking into it and will ask infra for help when needed. Other than that there are no changes compared to the last quarter, no real activity by the community, the service seemed to be humming along. == 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 == This has again been a very quiet quarter for Gump. Gump seems to remain useful for the projects using it. == 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 AF: Report from the Apache Hama Project [Edward J. Yoon] ----------------------------------------- Attachment AG: Report from the Apache Helix Project [Kishore Gopalakrishna] ----------------------------------------- Attachment AH: 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: - Issue concerning compatibility claims by Apache Spark has been resolved with Spark PMC making changes as requested by Hive PMC. ## Activity: - A proposal has been made on dev@ list to split out Hive metastore into its own project. Discussion has led to the conclusion of doing exercise of separation first inside Hive and proceed with full separation after that. - Project made two releases in this quarter. - Continued development of features and bug fixes across whole project. ## PMC changes: -- Currently 41 PMC members. -- Matt McCline was added to the PMC on Wed Jul 05 2017 ## Committer base changes: - Currently 69 committers. - New commmitters: - Deepesh Khandelwal was added as a committer on Fri Jun 30 2017 - Peter Vary was added as a committer on Mon Jul 24 2017 - Sahil Takiar was added as a committer on Mon Jul 03 2017 - Teddy Choi was added as a committer on Wed Jul 12 2017 - Vihang Karajgaonkar was added as a committer on Fri Jul 07 2017 ##Releases: - 2.2.0 was released on Mon Jul 24 2017 - 2.3.0 was released on Tue Jul 18 2017 - hive-storage-2.4.0 was released on Sun Jul 16 2017 ## Mailing list activity: - dev@hive.apache.org: - 883 subscribers (up 19 in the last 3 months) - user@hive.apache.org: - 2237 subscribers (up 20 in the last 3 months) ## JIRA activity: - 622 JIRA tickets created in the last 3 months - 375 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [John D. Ament] Incubator PMC report for September 2017 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 currently 54 podlings incubating. We executed nine podling releases and have one podling planning to graduate this month. No changes to the PMC structure this month. * Community New IPMC members: - None People who left the IPMC: - None * New Podlings - Amaterasu - Daffodil * Podlings that Retired - MRQL * Podlings that failed to report, expected next month - Myriad - Spot * Graduations The board has motions for the following: - RocketMQ - Mnemonic (may be next month) * Releases The following releases entered distribution during the month of August: - 2017-08-01 Apache Juneau 6.3.1 - 2017-08-01 Apache Tamaya 0.3.0 - 2017-08-05 Apache Tamaya Extensions 0.3.0 - 2017-08-08 Apache Pulsar 1.19.0 - 2017-08-16 Apache HTrace 4.3.0 - 2017-08-16 Apache Spot 1.0 - 2017-08-17 Apache Fluo 1.0.0 - 2017-08-23 Apache S2Graph 0.2.0 - 2017-08-29 Apache Livy 0.4.0 * Legal / Trademarks - Thanks to hard work on both the Oracle and ASF side, the Netbeans team was able to get the first three repositories populated from a software grant. ---------------------------------------------------------------------- Table of Contents AriaTosca Daffodil Gearpump Gobblin Griffin Heron Hivemall HTrace Livy Mnemonic MRQL Myriad Omid OpenWhisk Pony Mail Pulsar Quickstep SAMOA SINGA Spot Superset Taverna Tephra Trafodion Wave ---------------------------------------------------------------------- -------------------- AriaTosca ARIA TOSCA project offers an easily consumable Software Development Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and Orchestration Specification of Cloud Applications) based solutions. AriaTosca has been incubating since 2016-08-27. Three most important issues to address in the move towards graduation: 1. Grow the community and enroll new committers. 2. Rotate Release Managers for future releases. 3. 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? Seeing some contributions now from independent developers. Active discussions on mailing lists with potential users and contributors. How has the project developed since the last report? The project has had its first two releases in July 2017 - 0.1 and 0.1.1 Important new features have been added: - Resumable workflows - Scaling nodes during service creation - AWS plugin support - Additional work towards being more TOSCA-compliant (e.g. interface inputs support) - Additional usage examples have been added, including ones that use IaaS plugins (Openstack, AWS), as well as one covering a real-life NFV use-case (Clearwater example) - More comprehensive tests, including for documentation generation, and parallelization of test suites - Standardized the release process with automatic shell scripts, allowing anyone to easily create additional releases for the project - 64 JIRA issues have been resolved since the last report How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: July 17, 2017 When were the last committers or PPMC members elected? Project is still functioning with the initial set of committers. Signed-off-by: [X](ariatosca) Suneel Marthi Comments: [X](ariatosca) John D. Ament Comments: The project has started to see more community interest. Need to figure out how to drive development more on list to get more outside contributions. [ ](ariatosca) Jakob Homan Comments: -------------------- 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. Initial setup (finalize infrastructure setup, get SGAs in place, move code/documentation/bugs/etc. over to Apache infrastructure, modify licenses) 2. Establish guidelines regarding release cycles, code reviews, bug management, etc. 3. Work to grow the community to establish a diversity of backgrounds and expertise 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? N/A How has the project developed since the last report? N/A 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 Signed-off-by: [X](daffodil) John D. Ament Comments: [X](daffodil) David Fisher Comments: Just starting off. -------------------- Gearpump Gearpump is a reactive real-time streaming engine based on the micro-service Actor model. Gearpump has been incubating since 2016-03-08. Three most important issues to address in the move towards graduation: 1. Have frequent release cycles. 2. Continue to evolve community interest and support. 3. Increase user adoption. 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? - Gearpump took part in Google Summer of Code 2017 project and it has been succeffully accompolished by student, Buddhi Ayesha, who is interested in making more contributions beyond the project. How has the project developed since the last report? - 32 issues created and 20 issues resolved. - Gearpump Runner has been merged into Apache Beam trunk. - An experimental SQL support has been added and state management is under development. How would you assess the podling's maturity? [ ] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-07-17 When were the last committers or PMC members elected? No new committers or PMC members elected yet. Signed-off-by: [X](gearpump) Jean-Baptiste Onofré Comments: [ ](gearpump) Andrew Purtell Comments: [ ](gearpump) Jarek Jarcec Cecho Comments: [ ](gearpump) Reynold Xin Comments: [ ](gearpump) Todd Lipcon Comments: [ ](gearpump) Xuefu Zhang Comments: -------------------- Gobblin Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. Gobblin has been incubating since 2017-02-23. Three most important issues to address in the move towards graduation: 1. Cut our first release 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 are working towards our first release. * Email stats for last month: user@gobblin.incubator.apache.org : 14 dev@gobblin.incubator.apache.org : 259 * There have been 54 Commits in last month: git log --format='%ci' | grep -cE '2017-0(8)' * 30 of those commits were by non-committers: git log --format='%ae %ci' | grep -E '2017-0(8)' | cut -d ' ' -f 1 | sort | uniq -c | sort -n * A video conference based meetup happened last month. How has the project developed since the last report? * Site has been setup. * Apache wiki has been populated with relevant content. * Code development is actively being tracked via JIRA / Sprint dashboard. How would you assess the podling's maturity? The podling is working towards its first release. Like last time, continued progress and activity on all fronts. [ ] 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 Signed-off-by: [ ](gobblin) Jean-Baptiste Onofré Comments: Waiting the board report. I will help/ping. [X](gobblin) Olivier Lamy Comments: [ ](gobblin) Jim Jagielski Comments: -------------------- Griffin Griffin is a open source Data Quality solution for distributed data systems at any scale in both streaming or batch data context Griffin has been incubating since 2016-12-05. Three most important issues to address in the move towards graduation: 1. Continuous development of more dq dimensions for batch and streaming mode. 2. Make the next release. 3. 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? - Three new contributors on-board, some users had contacted us for use cases. How has the project developed since the last report? - Active development is moving on well, 83 commits in last three months. - The first release of Griffin has been published. - Accuracy measure for streaming mode has been developed. - Griffin DSL has been optimized, to support accuracy and profiling cases well. - Service module refined API, UI module upgrade to Angular 2. - Work toward for next release version (general enough) to support streaming dq measure end to end. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-07-17 When were the last committers or PPMC members elected? - Initial set of committers / PPMC. Signed-off-by: [ ](griffin) Kasper Sørensen Comments: [X](griffin) Uma Maheswara Rao Gangumalla Comments: [ ](griffin) Luciano Resende Comments: [ ](griffin) Henry Saputra Comments: -------------------- Heron A real-time, distributed, fault-tolerant stream processing engine. Heron has been incubating since 2017-06-23. Three most important issues to address in the move towards graduation: 1. Finish bootstrapping project, IP clearance, initial website 2. Expanding the community and adding new committers 3. 1st ASF release 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? * Some issues encountered with new mailing list signups have been resolved. * All initial committers have submitted ICLAs and have gotten their ASF accounts setup. How has the project developed since the last report? * The project has made 3 non-Apache releases. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: No Apache releases as of yet. Working on code import. When were the last committers or PPMC members elected? N/A, still bootstrapping the project. Signed-off-by: [X](heron) Jake Farrell Comments: [ ](heron) Jacques Nadeau Comments: [ ](heron) Julien Le Dem Comments: [x](heron) P. Taylor Goetz Comments: Currently waiting on SGA (pinged for status, but no response yet). Little activity on mailing lists so far. Decision making seems to be taking place off-list (3 non-Apache releases). I concur with Dave Fisher that monthly reporting should be considered (although this is report #2 in their initial monthly reporting cycle). IPMC/Shepherd notes: Dave Fisher: It seems that with 3 non-apache releases while there is not even ay use of Apache resources that Heron ought to focus on migration. I think that they should be monthly until the code is moved. -------------------- 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. Create the first Apache release 2. Community growth (committers and users) 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? * Got contributions from new external contributors https://github.com/apache/incubator-hivemall/pull/91 https://github.com/apache/incubator-hivemall/pull/93 https://github.com/apache/incubator-hivemall/pull/111 https://issues.apache.org/jira/browse/HIVEMALL-124 * Udemy course featuring Hivemal was opened by someone outside PPMC https://www.udemy.com/new-in-big-data-apache-hivemall-machine-learning-with-sql/ * Github watchers/stars are gradually increasing: 99 stars as of Sept 6 (was 79 on May 31) * Twitter account @ApacheHivemall followers are gradually increasing: 87 followers as of Sept 6 (was 70 on May 31) How has the project developed since the last report? * Approaching the first Apache release while the released delayed from Q2 to Q3 due to delay in merging large patches. - Waiting for incoming pull requests to review and merge https://github.com/apache/incubator-hivemall/pulls - Merging HIVEMALL-24 takes time more than expected https://github.com/apache/incubator-hivemall/pull/105 - Blocking issues are decreased https://issues.apache.org/jira/browse/HIVEMALL-21 Since the last report, we have * In the last 90 days, we opened 29 JIRA issues and closed 21 JIRA issues as seen in https://goo.gl/88Qr11 (as of Sept 6) Created Resolved June 2017 7 8 July 2017 15 12 Aug 2017 5 0 Sept 2017 2 1 * Created 30 Pull Requests and merged 24 Pull Requests between June 01 and Aug 31. https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A2017-06-01..2017-08-31 https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2017-06-01..2017-08-31 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: No release yet (planning the first Apache release in Q3, 2017) When were the last committers or PPMC members elected? * June 5: Invited Takuya Kitazawa to PPMC Signed-off-by: [ ](hivemall) Reynold Xin Comments: [X](hivemall) Markus Weimer Comments: [ ](hivemall) Xiangrui Meng Comments: [ ](hivemall) Daniel Dai Comments: -------------------- HTrace HTrace is a tracing framework intended for use with distributed systems written in java. HTrace has been incubating since 2014-11-11. Three most important issues to address in the move towards graduation: 1. Continue to grow the Apache HTrace community 2. Continue to explore projects integrating Apache HTrace 3. Continue to develop and release stable Apache HTrace incubating artifacts Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? In a DISCUSSION thread on our dev list [1], one of us suggested moving the podling htrace to the attic because of inactivity. A healthy back and forth suggested that we are not dead yet, that we cut back our scope radically, and that we give it another try before calling it quits. 1. https://s.apache.org/9ybr How has the community developed since the last report? Mailing lists continue quiet (bar the above noted thread). How has the project developed since the last report? No development. 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-10-06 When were the last committers or PPMC members elected? 2016-10-03 Signed-off-by: [ ](htrace) Jake Farrell Comments: [ ](htrace) Todd Lipcon Comments: [x](htrace) Lewis John Mcgibbney Comments: I think the following comment resonates on the mailing list "...A healthy back and forth suggested that we are not dead yet, that we cut back our scope radically, and that we give it another try before calling it quits." I think HTrace may have a good opportunity to come back to life if the above cut backs are implemented. [ ](htrace) Andrew Purtell Comments: [x](htrace) Billie Rinaldi Comments: [X](htrace) Michael Stack Comments: -------------------- Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. Three most important issues to address in the move towards graduation: 1. Grow more committers to maintain the community 2. Expand the community, be more open to the newcomers 3. Have a regular release cadence 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 are seeing nascent activity on the new ASF mailing lists for users. How has the project developed since the last report? We released the first Apache release of Livy, and migrated all the assets including JIRA, website to ASF. One big feature about support shared session across languages was merged. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-09-01 When were the last committers or PPMC members elected? N/A Signed-off-by: [X](livy) Bikas Saha Comments: [ ](livy) Brock Noland Comments: [ ](livy) Luciano Resende Comments: [X](livy) Jean-Baptiste Onofré Comments: -------------------- Mnemonic Apache Mnemonic is a transparent NVM hybrid memory oriented library that has created Durable Object Model (DOM), Durable Computing Model (DCM) and Durable Query Model (DQM) that bring many advantages to significantly improve the performance of massive real-time data processing/analytics. developers are able to use this library to design their cache-less, SerDe-less and direct-native high-performance applications or frameworks. Mnemonic has been incubating since 2016-03-03. Three most important issues to address in the move towards graduation: 1. Have elected new PPMC, Release Manager and committers 2. Have proposed Durable Query Model (DQM) based on DOM and DCM 3. Have prepared Apache maturity assessment checklist for review Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Not yet How has the community developed since the last report? Our last report was in Jun. Since then * fulfilled the gaps from graduation * elected new release manager * elected new committers * introduce owner of CQEngine to our community * some contributors have started to vote for graduation How has the project developed since the last report? * improved Apache mnemonic official website * implemented durable query in memory service level * implemented pure Java volatile memory service * improved the documentation of project specific release process * released mnemonic-0.8.0-incubating * started to vote mnemonic-0.9.0-incubating 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: 2017-06-23 When were the last committers or PPMC members elected? Johnu George (PPMC on Aug. 04 2017) PeiLi Shen (Committer on Aug. 13 2017) Signed-off-by: [X](mnemonic) Patrick Hunt Comments: afaict ready to graduate (there is an active DISCUSS thread going on now) [ ](mnemonic) Andrew Purtell Comments: [X](mnemonic) James Taylor Comments: [ ](mnemonic) Henry Saputra Comments: -------------------- Myriad IPMC/Shepherd notes: johndament: No report from podling. Discussion back in July indicated the podling did not want to retire and had enough active members to stay alive. No on list activity since then. -------------------- 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. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 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? N/A How has the community developed since the last report? Started integration with Apache Phoenix How has the project developed since the last report? Several bugs discovered and fixed. Continue testing prod environment at Yahoo. Branch 0.9.0.0 started for next release Quarter Stats (from: 2017-03-01 to: 2017-05-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 108 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 6 | | Resolved Issues | 6 | | Pull Requests merged | 3 | | Pull Requests proposed | 3 | +---------------------------------------------+ 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-06-24 When were the last committers or PPMC members elected? Signed-off-by: [X](omid) Alan Gates Comments: Activity continues to be low but there has been a noticeable uptick since the last report, and there is now a consistent if low level of activity on the project. The big challenge now for Omid is to attract new contributors to the project. [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [X](omid) James Taylor Comments: -------------------- 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. Additionslly, it now provides options to host the platform components as Docker containers on various Container Frameworks such as Mesos, Kunernetes, and Compose. OpenWhisk has been incubating since 2016-11-23. Three most important issues to address in the move towards graduation: 1. Est. release process for ZIP of source code 2. Est. release process for Docker and other platform binaries 3. Increase additional company and individual Contributors to maintain all project repos. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - It had been our intent to have Apache host our staging (and move it out of disparate private builds within various companies). However, INFRA indicates they only typically allocate 1 VM per project for use with demos and minor things. They indicated that typically a donation is in order (ala. Spark). -- Note: the desire for this staging capability was expressed in the Incubator submission where we anticipated needing ~12 VMs to host each platform component and be able to load balance/schedule Functional code as part of the OpenWhisk Serverless (across multiple supported language runtimes). This would also be needed to effectively test auto-scaling/load balancing and container pools and to get accurate performance test measures. - Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; need to identify process for this. How has the community developed since the last report? - First substantive design changes allowing for Service Provider Interfaces (SPIs) developed within Apache community (dev list, WIki, etc.). - Established bi-weekly Zoom "Technical Interchange" calls that have been well received. Complete videos posted to OW YouTube channel and detailed notes to our CWIKI. - Kubernetes on OpenWhisk work hosted a few ad-hoc to continue design discussions (CWIKI has designs and comments) for how best to move away from Ansible deployments to self-configuring, autoscalable containers (for use in Kube, Mesos, Compose, etc.). - Increased interest/list/Slack traffic in general due to experiment Kube work, as it is applicable to Mesos, etc. - Increased community discussions (design topics, features) of substance moved to dev list. How has the project developed since the last report? - incubator-openwhisk Github stars: 1928 - incubator-openwhisk GitHub forks: 417 - Movement to become more "pluggable" via Service Provider Interfaces (SPI), several PRs that are ongoing. - So far there are now interfaces for MessagingProvider.scala, ArtifactStoreProvider.scala and proposals for others such as LogStore, ContainerFactory, LoadBalancer, Sig. PRs: - initial work on no root ansible #2669 This allows to deploy with no sudo/root access. Significant to enable Kube/Mesos deployments. - Simplify Spi implementations. #2663 Service Provider Interfaces (SPI) become more mature as patterns emerge. Healthy discussion/growth area for project to allow most components to become (eventually) pluggable (e.g., Log, Trace, Container build, Load Balancing, Scheduler, Routing, Message Queue, etc.) - Apply standard scala formatting #2650 Coding/linting standards debated/agreed to by community (and CI automated enforcement encoded) - Allow multiple controllers and invokers in local environments #2633 implement a ContainerPool which is completely independent of the underlying container driver to facilitate testing and extensibility. More improvements to allow different pooling of invoker containers based upon different application use case (new ideas generated in community) including requirements for diff. scheduling/co-tenanting,/user responsiveness (http), etc. needs. Sig. discussions (dev list): - Release for OpenWhisk - Releases and SPI plans - OpenWhisk shell tool - authentication models for openwhisk - Performance tests for OpenWhisk - Adaption of hosts-files - Default handling for HTTP web actions 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: Comments: Need greater variety of contributors and contributing companies Date of last release: N/A When were the last committers or PPMC members elected? - Tyson Norris, Committer, 08/31/2017 - James Dubee, PPMC, Committer, 09/05/2017 Signed-off-by: [ ](openwhisk) Felix Meschberger Comments: [ ](openwhisk) Isabel Drost-Fromm Comments: [X](openwhisk) Sergio Fernández Comments: -------------------- 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. Work on the next release (0.10) 2. Work on expanding the community, be more open to newcomers 3. Resolve design strategies Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None that I am aware of. How has the community developed since the last report? No major development. A few more bug reports from outside contributors have been filed. How has the project developed since the last report? Work continues towards the next release, 0.10, which should be ready for a vote soon. How would you assess the podling's maturity? The podling is somewhat mature, but it is my assessment that more people are needed for it to be a fully viable community. 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: 2016-08-02 When were the last committers or PPMC members elected? sebb as PMC, 2017-04-17. No new committers as of late. Signed-off-by: [ ](ponymail) Andrew Bayer Comments: [X](ponymail) John D. Ament Comments: -------------------- Pulsar 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. Pulsar has been incubating since 2017-06-01. Three most important issues to address in the move towards graduation: 1. Grow the community with new Committers/PPMC members. 2. Set up a test cluster to be able to run system tests 3. Improve release process by having more committers taking part in releases 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? The community added 2 contributors. There is a healthy discuss on issues related to development, tools and processes among the community members. How has the project developed since the last report? 8 authors have pushed 69 commits to master in the last 30 days. The project has made the first release from the Apache Incubator on August 9th. The next release is planned for mid-September. Several design documents with improvement proposals have been submitted to the wiki and discussed in the mailing list. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-08-09, 1.19.0-incubating When were the last committers or PPMC members elected? Signed-off-by: [X](pulsar) Dave Fisher Comments: Project is moving towards a second release [ ](pulsar) Jim Jagielski Comments: [x](pulsar) P. Taylor Goetz Comments: Pulsar seems to be doing well. [ ](pulsar) Francis Liu Comments: -------------------- Quickstep Quickstep is a high-performance database engine. Quickstep has been incubating since 2016-03-29. Three most important issues to address in the move towards graduation: 1. Building a Quickstep community 2. More adoption of the Quickstep technology 3. More releases 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? In the summer of 2017, we took efforts to spread awareness about the Quickstep project and technology. We had many talks, particularly in the San Francisco Bay Area. The talks/venues are listed here: 1. SRI International in Menlo Park 2. A meetup hosted by H2O.ai in Mountain View 3. Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for hosting) We had also applied for a talk at BigDataWisconsin meetup but the proposal was not selected. How has the project developed since the last report? During the summer, the development activity was slow. There are ongoing efforts to build a distributed version of Quickstep. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-03-25 When were the last committers or PPMC members elected? 2017-05-12 Tianrun Lee (committer) Signed-off-by: [ ](quickstep) Konstantin Boudnik Comments: [x](quickstep) Julian Hyde Comments: Community building remains the project's biggest challenge. The project has been putting considerable effort into talks and I hope this effort starts to pay off. [ ](quickstep) Roman Shaposhnik Comments: -------------------- 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 Flink, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Elect new PPMC members 2. Enlarge the community 3. 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 (June 2017 - August 2017): * @dev: 120 messages Jira issues backlog (June 2017 - August 2017): * Created: 4 * Resolved: 5 We saw the engagement of new contributors, who are plausible candidates for the PPMC. How has the project developed since the last report? * Planning a new release in the next month. Work on the release was delayed due to summer holidays for most of the contributors. * Integrated Apache Kafka support and support for JSON and Avro. * Developed a new Boosting algorithm that will be integrated shortly. * Integrated new version of the SAMOA instances. * Integrated ability to store predictions on disk. 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? None Signed-off-by: [X](samoa) Alan Gates Comments: [ ](samoa) Ashutosh Chauhan Comments: [ ](samoa) Enis Soztutar Comments: [ ](samoa) Ted Dunning Comments: -------------------- 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. Prepare all documentations and go through the graduation voting process. 2. 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? A new committer (moaz) has been added into SINGA. How has the project developed since the last report? 1. We extended SINGA Python support from Py2 to Py3. 2. We added CPack to generate debian packages for SINGA 3. Several example models (VGG and InceptionV3/V4) were added. 4. A couple of bugs were fixed and the documentation was updated. 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: 2017-12-02 When were the last committers or PPMC members elected? 2017-29-08 Signed-off-by: [ ](singa) Daniel Dai Comments: [X](singa) Alan Gates Comments: [ ](singa) Ted Dunning Comments: [ ](singa) Thejas Nair Comments: IPMC/Shepherd notes: Dave Fisher - Graduation looks close. -------------------- Spot IPMC/Shepherd notes: - Drew Farris (shepherd): No mentor activity apparent from the mailing lists, ongoing project activity observed. - John D. Ament: Podling needed some reminding about the board report, I suspect next report will be in and of high quality. -------------------- 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. Address the challenge that React is no longer allowed in Apache projects 2. Grow the community and enroll new committers. 3. Plan and execute our first Apache release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * Superset is heavily reliant upon React, but React is no longer allowed in ASF projects (https://code.facebook.com/posts/112130496157735/explaining-react-s-license/). We are currently evaluating Preact as an alternative. (https://github.com/apache/incubator-superset/pull/3355) How has the community developed since the last report? * Grace Guo and Riccardo Magliocchetti have been elected as Superset Committers * Organic growth of our Github contributors (160), forks (2,338), watchers (829) and stars (15,807) How has the project developed since the last report? * We have completed all of the items on the Apache Incubation Checklist * We have a healthy, constant flow of bug fixes, quality improvements and new features. Take a look at the project’s Pulse on Github for more details 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 Q4, 2017) When were the last committers or PPMC members elected? Grace Guo and Riccardo Magliocchetti were both elected on August 17, 2017 Signed-off-by: [X](superset) Ashutosh Chauhan Comments: [X](superset) Luke Han Comments: [ ](superset) Jim Jagielski Comments: -------------------- Taverna Taverna is a domain-independent suite of tools used to design and execute data-driven workflows. Taverna has been incubating since 2014-10-20. Three most important issues to address in the move towards graduation: 1. Complete the remaining IP review (by retiring irrelevant git repositories) 2. Re-engage PMC to encourage regular activity 3. Graduate! 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? Fairly quiet over the summer. Lack of progress towards graduation. Need more active drive. Email stats since 2017-07-01: dev@taverna: 74 emails users@taverna: 4 emails How has the project developed since the last report? Progress towards release of the Taverna Mobile Android App. Been in contact with legal/infra to figure out how to do code signing for Google Play store. 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: 2016-07-01 When were the last committers or PPMC members elected? 2016-10-20 Signed-off-by: [ ](taverna) Andy Seaborne Comments: [ ](taverna) Daniel J Debrunner Comments: [ ](taverna) Marlon Pierce Comments: [x](taverna) Stian Soiland-Reyes Comments: Mailing list has gone very quiet [ ](taverna) Suresh Marru Comments: [ ](taverna) Suresh Srinivas Comments: -------------------- 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 subscriber in dev mailing list since the last report - 16 new JIRAs filed since the last report - 2 external contributors submitted patches since the last report - 4 external contributor created a ticket in JIRA since the last report How has the project developed since the last report? - Working on 0.13.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 the last release: 2017-05-30 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates Comments: [ ](tephra) Andrew Purtell Comments: [X](tephra) James Taylor Comments: [ ](tephra) Lars Hofhansl Comments: -------------------- Trafodion Apache Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Trafodion has been incubating since 2015-05-24. Three most important issues to address in the move towards graduation: 1. Develop the community and continue to grow the diversity. 2. Continue the momentum and become more integrated with the rest of the Apache community. 3. Continue to create software releases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * Two of our three remaining mentors, Devaraj Das and Enis Söztutar, resigned on July 21. How has the community developed since the last report? * Participation in the project remains healthy, with the usual small dip due to the summer vacation season: - ML postings: 106 user, 273 dev, 389 coderev, 734 issues, 341 commits - Twitter: 221 followers, 72 tweets, 67 likes * We are working towards our next release, 2.2. Ming Liu is the Release Manager. * Discussion regarding readiness to graduate continues. Diversity continues to grow. How has the project developed since the last report? * 162 commits from 18 contributors. * 100 JIRAs filed and 63 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 [X] Nearing graduation [ ] Other: Date of last release: 2017-05-01 2.1 When were the last committers or PMC members elected? 2017-03-10 Signed-off-by: [x](trafodion) Michael Stack Comments: -------------------- Wave A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Appoint members of the PMC 2. Update release procedure 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? There were no relevant events regarding the community in this period. How has the project developed since the last report? Some members of community work on side projects - like UI improvements, but overall we had a low level of activity. 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: March 2016 When were the last committers or PPMC members elected? March 2017 Signed-off-by: [X](wave) John D. Ament Comments: Reached out to get the dates fixed up. In order to graduate, we have to figure out how to get more activity. [ ](wave) Upayavira Comments: IPMC/Shepherd notes: Drew Farris (shepherd): Two mentors active. Light activity on the project in general, some discussion towards graduation a couple months back. ----------------------------------------- Attachment AJ: Report from the Apache Jackrabbit Project [Michael Dürig] Report from the Apache Jackrabbit committee ## 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. 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. Adobe donated the content-package-maven-plugin to us: a Maven plugin that simplifies the creation of content package maven artifacts. The content packages can later be used to install content into a JCR repository using the Apache Jackrabbit FileVault packaging runtime. Filevault was contributed 4 years ago, but we never had a tool to create the packaged during runtime. Adobe's plugin is publicly available, but only in binary form. This contribution brings the source and development closer to the filevault core. Retirement of Apache Jackrabbit 2.4: the Apache Jackrabbit PMC decided that since the 2.4 branch of the project looks like not being used any more to drop support and deprecate this version. Previous branch, tags and releases will still be available for future references, but will not show up on the download page any more. Users are encouraged to upgrade to the latest stable versions (2.14 for Java 7, 2.12 for Java 6). We held an Oak Hackathon August 21st to 25th in Basel - Switzerland, which was free and open to everyone. See https://wiki.apache.org/jackrabbit/Oakathon%20August%202017. There are various talks around Jackrabbit at this year's AdaptTo conference in Berlin Sept. 25th to 27th. ## 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. ## PMC changes: - Currently 51 PMC members. - No new PMC members added in the last 3 months. Prospects being discussed on the private list. - Last PMC addition was Robert Munteanu on Mon May 22 2017 ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months. Prospects being discussed on the private list. - Last committer addition was Robert Munteanu on Mon May 22 2017 ## Releases: - jackrabbit-2.10.6 was released on Mon Jul 03 2017 - jackrabbit-2.14.2 was released on Sat Jul 08 2017 - jackrabbit-2.15.4 was released on Fri Jun 23 2017 - jackrabbit-2.15.5 was released on Mon Jul 31 2017 - jackrabbit-2.15.6 was released on Thu Sep 07 2017 - jackrabbit-2.4.8 was released on Mon Jul 17 2017 - jackrabbit-2.6.9 was released on Mon Sep 04 2017 - vault-3.1.40 was released on Mon Jun 26 2017 - oak-1.0.39 was released on Tue Aug 15 2017 - oak-1.2.27 was released on Wed Aug 02 2017 - oak-1.4.17 was released on Mon Jul 17 2017 - oak-1.4.18 was released on Wed Aug 30 2017 - oak-1.6.2 was released on Mon Jun 12 2017 - oak-1.6.3 was released on Wed Jul 12 2017 - oak-1.6.4 was released on Wed Aug 16 2017 - oak-1.6.5 was released on Mon Sep 04 2017 - oak-1.7.2 was released on Mon Jun 19 2017 - oak-1.7.3 was released on Mon Jul 03 2017 - oak-1.7.4 was released on Wed Jul 19 2017 - oak-1.7.5 was released on Mon Jul 31 2017 - oak-1.7.6 was released on Tue Aug 22 2017 ## JIRA activity: - 364 JIRA tickets created in the last 3 months - 325 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ----------------------------------------- Attachment AL: 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: - Another quiet period for Labs, with essentially zero activity. ## Health report: - Having managed to ascertain that there is volunteer energy amongst the wider community, the next step will be to identify a real use case to act as a test of any proposed changes, and to articulate a revised labs offering to the PMC, the members and the board. - Given that I believe that ASF<->Github integration is critical to the future of this project I would be pleased to have advice from board members about how I can engage with infrastructure without generating disproportionate workload on that critical project. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jan Iversen on Tue Feb 04 2014 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Jan Iversen at Thu Feb 27 2014 ## Releases: - Labs does not make releases ## Mailing list activity: - labs@labs.apache.org: - 209 subscribers (down -1 in the last 3 months): - 3 emails sent to list (55 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 AM: Report from the Apache Lucene Project [Tommaso Teofili] ## 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: - The community has worked a lot on both Lucene and Solr, with daily commits, towards Lucene and Solr 7 releases - We are still working on resolving a security vulnerability and a new one got reported and fix is being addressed - Discussions are generally flowing in a good shape - Meetups / conferences around Lucene / Solr: - LueneSolrRevolution on September 12-15, 2017 Las Vegas, NV - Lucene for Information Access and Retrieval Research (LIARR) Workshop on August 11th at SIGIR 2017 conference in Tokio, Japan ## PMC changes: - No new PMC members in the last 3 months, but a vote to add a new one is ongoing. - Currently 43 PMC members ## Committer base changes: - No new committers in the last 3 months. - Currently 68 committers and 43 PMC members. ## Releases: - The vote on the release of Apache Lucene and Solr 7.0.0 has passed, so the release should go out shortly ----------------------------------------- Attachment AN: Report from the Apache Lucene.Net Project [Prescott Nasser] ----------------------------------------- Attachment AO: Report from the Apache MADlib Project [Aaron Feng] ## Description: - Apache MADlib is a scalable, Big Data, SQL-driven machine learning framework for Data Scientists. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Community activity focused on post-graduation tasks related to MADlib's promotion to ASF TLP status. This included working on the code base, website, wiki, and ASF infrastructure. - Trademark transfer from Pivotal to ASF was completed in the month of August, 2017. - The first TLP release of MADlib 1.12 happened on Aug 29, 2017. - A MADlib community call on the topic of the 1.12 release happened on Sept 7, 2017. - A set of 2.0 JIRAs has been proposed to review by the community. ## Health report: The community is relatively small but very engaged with robust mailing list traffic, interest in doing frequent releases and a bunch of new functionality being developed by contributors. Work has begun in earnest on the next release 2.0 planned in the fall. The number of committers actively contributing to the code/documentation has been steady and remains at a level of half a dozen active committers each month. We will constantly be on a lookout for new community members to be invited either as committers or PMC. ## PMC changes: - No changes in PMC, currently 13 PMC members. ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Nandish Jayaram on 2016-09-08 ## Releases: - v1.12.0 released on 2017-08-29 - v1.11.0-incubating released on 2017-05-17 - v1.10.0-incubating released on 2017-03-10 ## Mailing list activity: Mailing activity has remained relatively stable with 324 posts to dev@ and 19 posts to user@ during the month of Aug. ## JIRA Statistics: - 9 JIRA tickets created in the last month - 13 JIRA tickets resolved in the last month ----------------------------------------- Attachment AP: Report from the Apache MINA Project [Jean-François Maury] ## Description: Apache MINA is a network application framework which helps users develop high performance and high scalability network applications easily. ## Issues: - SSHD 1.6.0 has been released with bug fixes and new PROXY support. MINA 2.0.17 about to be released. ## Activity: SSHD is still the most active project. ## Health report: Core project have bug reported by users, trying to encourage patches to identify future commiters, without success yet. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Lyor Goldstein on Mon Feb 13 2017 - Vote for changing the chair will take place next quarter ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Lyor Goldstein at Thu Apr 30 2015 ## Releases: - SSHD-1.6.0 was released on Wed Jul 05 2017 ## Mailing list activity: - users@mina.apache.org: - 506 subscribers (down -2 in the last 3 months): - 20 emails sent to list (34 in previous quarter) - dev@mina.apache.org: - 358 subscribers (up 2 in the last 3 months): - 302 emails sent to list (295 in previous quarter) - ftpserver-users@mina.apache.org: - 131 subscribers (up 2 in the last 3 months): - 0 emails sent to list (2 in previous quarter) ## JIRA activity: - 24 JIRA tickets created in the last 3 months - 22 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AQ: Report from the Apache Mynewt Project [Justin Mclean] 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: There are no issues requiring board attention at this time. ## Activity: - Talks about Mynewt were given at a couple of conferences to improve project visibility in the community - Community work in serval areas including support for Bluetooth Mesh, Bluetooth 5, LoRa and new boards support - Coverity scan is now run periodically on Mynewt codebase to improve overall code quality and reduce bugs ## Health report: - PMC and committers are active - Users questions and contributor's pull requests are dealt with in a timely manner ## PMC changes: - Currently 19 PMC members - Last PMC addition was everyone on 21st June ## Committer base changes: - Currently 23 committers - One new committer voted on and added since last report - Miguel Arevedo on September 11th 2017 ## Releases: - 1.2 was released on September 12th 2017 ## Mailing list activity: - Mailing list activity is mainly around new feature descriptions and request for comments, voting for releases, questions that would be of general interest (e.g. code size increase/trimming) - Mailing list activity (number of emails, participant count, topics started) increased compared to previous month. - Lots of usage Q&A and error clarification on Slack channel - up to 96 users on Slack channel ## JIRA activity: - Activity similar to last month with similar number of JIRAs raised and closed. The average number of days taken to resolve issues dropped by a week from July to August. ----------------------------------------- Attachment AR: 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 ## Activity: - OFBiz fully redesigned and released its website. The new website is designed with bootstrap and other libraries making it modern and responsive thus working on all devices. In addition to the facelift, the website is also redesigned in terms of navigation and menu structure to make it easy to locate resources. The new design is also more SEO friendly - Refactoring work continues on all areas of the project with more focus on the core components - A redesign of the user interface is underway in which all web artifacts are removed from the framework into a separate directory called the "common" theme. The purpose of this initiative is to decouple any web-artifacts from the framework for better and cleaner implementations. We expect this change to improve the ability to update the user interface by reducing the amount of artifacts altered with each change - A decision was made by the community to centralize the data loading process in one component to ease development and data review [1] - The project discontinued support for the unreleased branches 14.12 and 15.12 - An initiative is underway to improve the code and detect bugs using code analysis tools available through the build system. - the activity in the official blog [2] is steady with monthly blog posts that highlight the main activities in the project; we have been also active on Twitter [3] and other social media [4]; we have had a medium activity in our public HipChat room [5] - vulnerability reports: two reports have been received by the OFBiz security list but after investigating we realized they do not apply to any active release branches and do not qualify as vulnerabilities; the security team still needs to provide an official answer to the reporters ## Health report: This has been another active quarter for the project, despite Jun-Jul-Aug being a traditionally slow period: one new release issued, two new committers, increased number of subscribers and email messages, a steady number of tickets filed and resolved; the community is slowly growing. ## PMC changes: - Currently 19 PMC members - No new PMC members added in the last 3 months - Last PMC addition was Deepak Dixit on Fri Feb 24 2017 ## Committer base changes: - Currently 44 committers. - New commmitters: - Akash Jain was added as a committer on Wed Aug 09 2017 - Rishi Solanki was added as a committer on Wed Aug 09 2017 ## Releases: - 16.11.03 was released on Thu Jun 29 2017 ## Mailing list activity: - dev@ofbiz.apache.org: - 573 subscribers (up 4 in the last 3 months): - 1050 emails sent to list (922 in previous quarter) - notifications@ofbiz.apache.org: - 79 subscribers (up 0 in the last 3 months): - 2493 emails sent to list (1459 in previous quarter) - user@ofbiz.apache.org: - 947 subscribers (up 7 in the last 3 months): - 871 emails sent to list (523 in previous quarter) ## JIRA activity: - 287 JIRA tickets created in the last 3 months - 205 JIRA tickets closed/resolved in the last 3 months ## References [1] https://issues.apache.org/jira/browse/OFBIZ-9501 [2] https://blogs.apache.org/ofbiz/ [3] https://twitter.com/ApacheOfbiz [4] https://www.facebook.com/Apache-OFBiz-1478219232210477/ [5] https://apache.hipchat.com/chat/room/2814115 ----------------------------------------- Attachment AS: Report from the Apache Olingo Project [Christian Amend] ## 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. ## Olingo Status Olingo has no issues that would require board attention. As of last week we released a new minor version of the OData V4 code line. The OData V4.01 specification is still in the public review at Oasis so there has been no progress on that end. The traffic on the mailing lists and in our JIRA is on a stable rate. Most issues that are created revolve around bugs with very little feature requests. Issues with contributions come in more regular now and are picked up by the community. === Statistics === ## 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.9 was released on Sat Jul 08 2017 - 4.4.0 was released on Fri Sep 01 2017 ## Mailing list activity: - dev@olingo.apache.org: - 85 subscribers (down -1 in the last 3 months): - 267 emails sent to list (310 in previous quarter) - user@olingo.apache.org: - 186 subscribers (up 8 in the last 3 months): - 43 emails sent to list (14 in previous quarter) ## JIRA activity: - 41 JIRA tickets created in the last 3 months - 28 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache OODT Project [Tom Barber] 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. RELEASES/DEVELOPMENT - Last release was 1.1 on Wed Jul 27 2017 - Last release was 1.2 on Wed Aug 28 2017 We resolved 21 issues for these releases. Improved activity this reporting period, with 2 releases, a number of fixed bugs, cleaned up Jira and a great new set of features from the GSOC project. We have new features coming into the code base for the 2.0 development drive and a positive outlook for the future. COMMUNITY Latest committers and PMC members Imesha Sudasingha(imesha) on 28th Aug 2017 as committer and PMC member ISSUES There are no issues requiring board attention at this time. HEALTH REPORT The project activity is pretty quiet, but there has been a positive uplift this quarter with the GSOC project and 2 new releases. ----------------------------------------- Attachment AU: Report from the Apache OpenNLP Project [Jörn Kottmann] ## Description: - The Apache OpenNLP library is a machine learning based toolkit for the processing of natural language text. ## Issues: - Need help from infra to setup a repository to store large training data files ## Activity: 1. Project had a minor 1.8.2 release this month. 2. The team’s presently working on 1.8.3 release cycle and on releasing pre-trained statistical models 3. A model for the new language detector component will be released soon. 4. Daniel Russ presented ‘“Its takes a Village to solve a Problem in Data Science” at Data Science Maryland Meetup, June 19 2017, Laurel Maryland - https://www.slideshare.net/DataScienceMD/it-takes-a-village-to-solve-a-problem-in-data-science 5. Suneel Marthi will be presenting ‘Deriving Actionable Insights from High Volume Media Streams” at Machine Learning Conference, San Francisco on Nov 10 2017 - http://mlconf.com/mlconf-2017-san-francisco/#Suneel 6. Suneel Marthi and Jorn Kottmann will be presenting ‘Deriving Actionable Insights from High Volume Media Streams” at Big Data Spain, Madrid in Nov 2017. 7. Apache OpenNLP was cited in paper “An Automatic Approach for Discovering and Geocoding Locations in Domain-Specific Web Data” by Chris Mattmann, Madhav Sharan - https://memex.jpl.nasa.gov/IRI16-Gazetteer.pdf ## Health report: - Project has healthy activity levels and dedicated committers. ## PMC changes: - Currently 14 PMC members. - New PMC members: - Jeffrey T. Zemerick was added to the PMC on Wed Jul 26 2017 - Bruno P. Kinoshita was added to the PMC on Wed Jul 05 2017 - Peter Thygesen was added to the PMC on Mon Aug 07 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.8.1 was released on Sat Jul 08 2017 - 1.8.2 was released on Fri Sep 15 2017 ## Mailing list activity: - users@opennlp.apache.org: - 441 subscribers (up 10 in the last 3 months): - 75 emails sent to list (38 in previous quarter) - dev@opennlp.apache.org: - 225 subscribers (up 3 in the last 3 months): - 331 emails sent to list (364 in previous quarter) - issues@opennlp.apache.org: - 48 subscribers (up 1 in the last 3 months): - 340 emails sent to list (552 in previous quarter) ## JIRA activity: - 37 JIRA tickets created in the last 3 months - 32 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AV: 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 consists of the ASF projects Tocmat9 + OpenWebBeans + CXF + Johnzon + log4j2. ## Issues: There are no issues requiring board attention at this time. ## Activity: We finished the CDI-2.0 work and shipped our first OWB-2.0.x releases. We also upgraded Meecrowave to OWB-2.0.x and shipped another maintenance release. ## Health report: Community is doing fine. We are currently observing a possible new committer. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Louis Monteiro on Wed May 28 2014 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Reinhard Sandtner at Fri Sep 26 2014 ## Releases: - Meecrowave-1.0.0 was released on Tue Jul 11 2017 - Meecrowave-1.1.0 was released on Tue Sep 05 2017 - OWB-1.7.4 was released on Tue Jul 11 2017 - OWB-2.0.0 was released on Fri Jul 14 2017 - OWB-2.0.1 was released on Sun Sep 03 2017 ## Mailing list activity: - dev@openwebbeans.apache.org: - 71 subscribers (up 0 in the last 3 months): - 417 emails sent to list (264 in previous quarter) - user@openwebbeans.apache.org: - 100 subscribers (up 2 in the last 3 months): - 57 emails sent to list (12 in previous quarter) ## JIRA activity: - 45 JIRA tickets created in the last 3 months - 53 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AW: Report from the Apache Pig Project [Daniel Dai] Report from the Apache Pig committee [Daniel Dai] ## 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: - PMC chair change request was missed in the last board meeting. Added to the board agenda again for September. ## Activity: - Stabilization of Pig on Spark, support for Spark 2.0 and development of features like bytecode generation is being worked on in the trunk ## Health report: - Project activity in the community - mails, commits, jiras, etc is good and is at the same levels as previous few quarters. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition: Thu Aug 04 2016 (Koji Noguchi) ## Committer base changes: - Currently 30 committers. - No new committers in the last 3 months. - Last committer addition: Sat May 20 2017 (Ádám Szita) ## Releases: - 0.17.0 was released on Thu Jun 15 2017 ## Mailing list activity: - dev@pig.apache.org: - 402 subscribers (up 4 in the last 3 months) - 673 emails sent in the past 3 months, 1508 in the previous cycle - user@pig.apache.org: - 1136 subscribers (down -1 in the last 3 months) - 17 emails sent in the past 3 months, 19 in the previous cycle ## JIRA activity: - 45 JIRA tickets created in the last 3 months - 24 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AX: Report from the Apache Pivot Project [Roger 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 the moment. Activity: We finally have released the long-awaited 2.0.5 maintenance version, with no new problems reported against it so far. Development has continued (albeit more slowly than last quarter) on the 2.1.0 version. We have started discussion about removing applet support entirely but have not come to any firm conclusions yet. Health Report: Unchanged from last report -- although the new release has not resulted in any net gain in interest that we can see. There are still at least three PMC members listening for votes, etc. PMC Changes: - Currently 4 PMC members. - No new PMC members added in the last 3 months. - Last PMC re-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 3 2017 - Still active development on next major version (2.1.0) Mailing List Activity: - Steady, overall roughly the same as previous quarter. - dev@pivot.apache.org - 61 subscribers (actually down -1 from last report) - 100 emails sent to list (131 from last report) - user@pivot.apache.org - 172 subscribers (down -2 from last report) - 12 emails this quarter (vs. 5 last time) - commits@pivot.apache.org - 21 subscribers (up +1 from last time) - 71 emails this time (vs. 78 in last quarter) - private@pivot.apache.org - 13 subscribers (up +1 for the first time in a long time) - No mails sent JIRA Activity: - 6 JIRA tickets created this quarter - Also 6 JIRA tickets closed/resolved this period ----------------------------------------- Attachment AY: Report from the Apache Polygene Project [Paul Merlin] Description: Apache Polygene is a community based effort exploring Composite Oriented Programming for domain centric application development. Issues: - there are no issues requiring board attention at this time Activity: - The quarter was a flurry of activity leading up to the long overdue release 3.0.0, which involved a massive refactoring where all our own functional and streaming was replaced with those available in Java 8. - Following the release, people have taken a well-deserved rest, but we are probably ready for one more release this year. - The JDK 9 Outreach program is nothing new other than that the release are compatible with "legacy mode" and "jigsaw mode" has not yet been attended to. Health report: - This remains a small project, but it is active and we have enough active PMC members to continue. We have not been able to attract new blood, one feedback seen on blog post complained that it was too difficult to understand what it is all about. Perhaps re-working the Introduction and Tutorial sections will help. PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Stanislav Muhametsin on Mon Jun 12 2017 Committer base changes: - Currently 18 committers. - No new changes to the committer base since last report. - No new committers added in the last 3 months - Last committer addition was Kent Sølvsten at Sun Jun 14 2015 Releases: - Apache Polygene 3.0.0 was released on Wed Jul 26 2017 Mailing list activity: - The drop in mail activity was due to last quarter's much higher traffic in the build up to finalizing the 3.0.0 release. It has now dropped down to more ordinary levels, except the last month or so, when the most active people have been taking vacation. - users@polygene.apache.org: - 20 subscribers (up 1 in the last 3 months): - 0 emails sent to list (1 in previous quarter) - dev@polygene.apache.org: - 37 subscribers (up 0 in the last 3 months): - 276 emails sent to list (690 in previous quarter) JIRA activity: - 15 JIRA tickets created in the last 3 months - 10 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AZ: 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. The sub-projects which are released somewhat regularly are APR and APR-util. In addition, the APR-iconv sub-project is commonly used but has not had a release since 2007. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Following the release of APR-1.6.2 and APR-UTIL 1.6.0 at the beginning of the period, activity has reverted to a low level typical of recent years. ## Health report: - The project remains broadly healthy, though quiet. ## PMC changes: - Currently 40 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Christophe Jaillet on Sun Oct 30 2016 ## Committer base changes: - Currently 66 committers. - No new committers added in the last 3 months - Last committer addition was Ivan Zhakov at Fri Oct 28 2016 ## Releases: - APR 1.6.2 and APR-UTIL 1.6.0 were released jointly on June 14th 2017. ## Mailing list activity: Activity dropped after the release in mid-June. Note: these figures are from reporter.apache.org, and differ from numbers at mail-archives.apache.org. They also differ from reporter.apache.org's own figures regarding the previous quarter. Differences are small. - dev@apr.apache.org: - 331 subscribers (up 1 in the last 3 months): - 118 emails sent to list (333 in previous quarter) - bugs@apr.apache.org: - 22 subscribers (up 0 in the last 3 months): - 47 emails sent to list (32 in previous quarter) ## Bugzilla Statistics: - 7 Bugzilla tickets created in the last 3 months - 4 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment BA: 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 released 0 releases since the last report. Developers are working daily with the Portlet 3.0 TCK as we implement Portlet 3.0 support for our portal products. We have challenged the validity of some TCK tests and also fixed some TCK bugs. But since the TCK is not a releasable artifact, we don't have any plans to release it in the future. 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. Several support questions with 3.0 release. Some discussions around release procedures when we released the 3.0 Maven Archetypes. ## 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 Maven Archetype 3.0.0 - 27 April 2017 Pluto 3.0.0 - 18 January 2017 Jetspeed 2.3.1- 09 May 2016 ----------------------------------------- Attachment BB: 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: There are no issues requiring board attention at this time ## Activity: - Version 1.8 released - Preparation for releasing version 2.0 based on Hive 2 and including HA support ## Health report: Development activity seems pretty consistent; No new developers since last time ## PMC changes: - Currently 35 PMC members. - Vadim Spector was added to the PMC on Sun Jun 11 2017 ## Committer base changes: - Currently 38 committers. - New commmitters: - Kalyan Kalvagadda was added as a committer on Wed Jun 21 2017 - Sergio Peña was added as a committer on Mon Aug 28 2017 - Vadim Spector was added as a committer on Fri Jun 02 2017 ## Releases: - 1.8.0 was released on Sun Aug 06 2017 - 1.7.0 was released on Tue Jun 14 2016 ## Mailing list activity: Most of the activity was about 1.8/2.0 releases and about finishing up HA work. ## JIRA activity: - 119 JIRA tickets created in the last 3 months - 125 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BC: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] 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 don't expect any new releases in for dependencies of ServiceMix 6 and we have transited it in EOL. - We want currently focus on ServiceMix 7 and upgrading preparing the new release containing the newest versions of Apache Karaf and Apache Camel. - We have released 4 sets of OSGi bundles and a new release of ServiceMix Specs. - We are going to make a small refactoring of ServiceMix features to give them a separate lifecycle (as ServiceMix Features) and provide better modularity and maintainability of ServiceMix. - We are going to focus more on improvement of the documentation (which was migrated lately into the Asciidoc format) and improvement of the examples to give people easier start into integration with ServiceMix. ## Health report - Due to summer vacation the activity of the community (mailing lists, JIRA, releases) has been a bit slower than during the last period. ## PMC changes - Currently 23 PMC members. - Andrea Cosentino was added to the PMC 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 Specs 2.9.0 on June 06 2016 - Apache ServiceMix Bundles 2017.05 on June 06 2017 - Apache ServiceMix Bundles 2017.06 on July 09 2017 - Apache ServiceMix Bundles 2017.07 on August 01 2017 - Apache ServiceMix Bundles 2017.08 on September 07 2017 ## JIRA activity - 106 JIRA tickets created in the last 3 months - 105 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BD: Report from the Apache Shiro Project [Les Hazlewood] 2017 September - 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 - We encountered a few permission issues during post release tasks. A different team member lead the release (which is great), we are working on fixing this for the next release. Community & Project: - Mailing list traffic has dipped a little, Stack Overflow has been becoming the preferred place to ask questions. - Community pull requests to the Shiro doc site continue to roll in, now that pages includes an 'Edit in Github' link. - 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: Andreas Kohn on 15 Jul 2016 Last PMC Member voted in: Andreas Kohn on 26 Jul 2016 ----------------------------------------- Attachment BE: Report from the Apache Sling Project [Carsten Ziegeler] Apache Sling is an OSGI-based scriptable web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. There are no issues which require board attention at the moment. Community Good activity level overall, contributions from different people continue. Finally released Sling 9. Working on getting Sling 10 with Java 9 support out. One new committer elected: Nicolas Peltier (June) (last committers change was in June 2017 with one new committer elected), no new PMC member (last PMC change was in October 2016 with one new PMC members elected). Releases Apache Sling Scripting HTL Compiler 1.0.12, Apache Sling Scripting HTL Java Compiler 1.0.12, Apache Sling Scripting HTL Engine 1.0.38 (September 1st, 2017) Apache Sling Launchpad Base 5.6.8-2.6.24 (August 31st, 2017) Apache Sling Provisioning Model 1.8.4, Apache Sling Slingstart Maven Plugin 1.7.8 (August 28th, 2017) Apache Sling Servlets Resolver 2.4.14 (August 28th, 2017) Apache Sling Commons Scheduler 2.7.0 (August 25th, 2017) Apache Sling Scripting JSP 2.3.2 (August 24th, 2017) Apache Sling Rewriter 1.2.2, Apache Sling Launchpad Base 5.6.6-2.6.22 (August 17th, 2017) Apache Sling Event 4.2.6 (August 16th, 2017) Apache Sling Default POST Servlets 2.3.22 (August 14th, 2017) Apache Sling Parent 31 (August 8th, 2017) Apache Sling Security 1.1.6, Apache Sling Scripting HTL Engine 1.0.38, Apache Sling Scripting HTL Compiler 1.0.10, Apache Sling HTL Maven Plugin 1.0.8 (August 7th, 2017) Apache Sling Launchpad Base 5.6.6-2.6.20 (August 3rd, 2017) Apache Sling Resource Resolver 1.5.30 (July 27th, 2017) Apache Sling Service User Mapper 1.3.4, Resource Resolver 1.5.28, JCR Base 3.0.4, JCR Resource 3.0.4 (July 21th, 2017) Apache Sling File System Resource Provider 2.1.8, File System Resource Provider 1.4.8 (July 18th, 2017) Apache Sling Commons Johnzon 1.1.0 (July 17th, 2017) Apache Sling Discovery Base 2.0.4 and Discovery Oak 1.2.20 (July 10th, 2017) Apache Sling Resource Resolver 1.5.26 (July 10th, 2017) Apache Sling Auth Core 1.4.0 (June 29th, 2017) Apache Sling Event 4.2.4, JCR Content Parser 1.2.4, File System Resource Provider 2.1.6, File System Resource Provider 1.4.6 (June 26th, 2017) Apache Sling Security 1.1.4 (June 21st, 2017) Apache Sling Testing Clients 1.1.4, Apache Sling Testing Email 1.0.0, Apache Sling Resource Merger 1.3.4 (June 20th, 2017) Apache Sling Slingstart Archetype (June 15th, 2017) Apache Sling JSPC Maven Plugin 2.1.0 Apache Sling Slingstart Archetype 1.0.2 (June 15th, 2017) Apache Sling 9, Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.12, Apache Sling Launchpad Testing Services 2.0.12, Apache Sling Launchpad Test Bundles 0.0.2, Apache Sling Launchpad Testing Services WAR 2.0.12, Apache Sling Integration Tests 1.0.4 (June 12th, 2017) ----------------------------------------- Attachment BF: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for September 2017 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. Health report: There has been little change from the previous quarter. Bug reports have been at a steady slow pace, with responses and fixes keeping up. Most technical activity has been on the mass-check/rule update infrastructure. The users list has been quite active and fairly technical for a user oriented list. There is a regular presence of some committers/PMC answering questions and participation in the discussions. Issues: Our mass-check system / rule update services have been migrated to its new VM. We have been dealing with instability problems including hangs. Infra has been responsive, increasing the RAM and number of cores in the VM. We have enabled additional logging to better track root causes of problems if they persist even with the increase in resources. The mass-check seems to be operational again, leaving problems with the output of rule update still to be resolved. Much thanks to Infra for their assistance. We continue to debug rule updates. Releases: The last release was Apache SpamAssassin version 3.4.1 on 30 April 2015. 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. Our new 3.4.2 release is close to ready for a release candidate but that will be held until the the resurrection of the mass-check / rule update system on the new platform is successful. Committer/PMC changes: Most recent new committers: Dave Jones (davej) 26 April 2017 Bryan Vest (bvest) 7 May, 2017 Most recent new PMC member: John Hardin (jhardin) 18 October 2016 ----------------------------------------- Attachment BG: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment BH: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: - Apache Storm is a distributed real-time computation system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - A security vulnerability (CVE-2017-9799) affecting the 1.1.x and 1.0.x release lines was was discovered by the Apache Storm PMC. The issue was discussed privately by the PMC and patched. Versions 1.0.4 and 1.1.1 were released to address the vulnerability prior to public announcement. - Version lines 1.1.x and 1.0.x are currently in maintenance mode with new feature development focusing on upcoming releases of versions 1.2 and 2.0. - Progress continues on the 2.0 release, which includes replacing Storm's Clojure code with pure Java implementations. - Anecdotal evidence seems to suggest that the move from Clojure to Java has increased contributor activity to the 2.0 release (which was one of the stated goals behind the decision). - An ongoing discussion is taking place around implementing a "Storm Improvement Proposal (SIP)" process for major changes/efforts. Concensus has yet to emerge, with some worrying the process may add too much overhead and suggesting a lightweight experiment before adopting it as policy. - We have moved from a manual changelog/release notes management to a scripted report generation tool that pulls data from JIRA. ## Health report: - Project activity continues to be fairly consistent, with periodic lulls and bursts in activity. - New contributors continue to engage and that engagement tends to keep up activity levels, even as some contributors move on. - The upcoming 2.0 release seems to have spurred activity, and the move from Clojure to Java appears to have attracted additional contributors. ## PMC changes: - Currently 34 PMC members. - Stig Rohde Døssing was added to the PMC on Wed Jul 12 2017 ## Committer base changes: - Currently 35 committers. - Stig Rohde Døssing was added as a committer on Fri Jul 14 2017 ## Releases: - 1.1.1 was released on Mon Jul 31 2017 - 1.0.4 was released on Thu Jul 27 2017 - 1.0.5 was released on Wed Sep 13 2017 ## Mailing list activity: - Activity on dev@ has picked up in response to the 2.0 release efforts. A number of new developers have begun contributing to the project. Activity on user@ is consistent with historical ebbs and flows. - dev@storm.apache.org: - 540 subscribers (down -2 in the last 3 months): - 2384 emails sent to list (1551 in previous quarter) - issues@storm.apache.org: - 16 subscribers (up 3 in the last 3 months): - 971 emails sent to list (611 in previous quarter) - user@storm.apache.org: - 1392 subscribers (down -12 in the last 3 months): - 481 emails sent to list (307 in previous quarter) ## JIRA activity: - 186 JIRA tickets created in the last 3 months - 160 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BI: Report from the Apache Streams Project [Steve Blackmon] ## Description: - Apache Streams unifies a diverse world of digital profiles and online activities into common formats and vocabularies, and makes these datasets accessible across a variety of databases, devices, and platforms for streaming, browsing, search, sharing, and analytics use-cases. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have completed almost all known PMC setup, infra, code, and website refactoring work due to graduation. - The final task remaining is to stop hosting the website from the incubator svn. - We now have our pull requests under continuous integration via jenkins. ## Health report: Streams graduated to TLP on July 19 2017.  Eight PPMC members have joined the new PMC.  Enthusiasm is strong and there is a lot of important work ahead.  ## PMC changes: - None. There are currently 8 PMC members.   ## Committer base changes: - None. There are currently 8 committers. ## Releases: - Prior release was 0.5-incubating on March 20, 2017 - Next release will be 0.6.0 - discussion on list has started. ## Mailing list activity: (3 month) 50 emails sent by 15 people, down 1 (-1%) compared to previous 92 days. 9 topics started during these 92 days, down 15 (-62%) compared to previous 92 days. 16 Participants during these 92 days, up 2 (14%) compared to previous 92 days. https://s.apache.org/QNOh ## JIRA Statistics: (3 month) 14 new, 15 resolved https://s.apache.org/Bm5T ## Website activity: (3 month) 800 sessions, up 9.44% compared to previous 3 months. 728 users, up 46.5% compared to previous 3 months. https://s.apache.org/XGBW ## Upcoming Project Initiatives: - Reduce disparities between normalized activities and objects of like type collected from various data sources.  - Reduce disparities between the configuration objects that initialize similar providers from various data sources. - Improve the interfaces by which components are created, configured, activated, and executed via SDK and CLI. - Drop remaining maven dependencies on java SDKs for accessing third-party HTTP APIs in favor of interfaces powered by Apache Juneau (incubating) Remoteable Annotations. - Add official support for Schema.org and Activity Streams 2.0 data types. - More tweets and blog posts of zeppelin notebooks demonstrating data pipelines and analyses based on Apache Streams. - More official examples in source tree demonstrating integration of Apache Streams with complementary technologies. ----------------------------------------- Attachment BJ: Report from the Apache Synapse Project [Isuru Udana] Synapse - September 2017 ## Description:  Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework.     ## Issues:  None identified.     ## Activity:  We are working on the next synapse feature release at the moment. We got some attraction from few new developers, one of them submitted a new feature. Newly elected PMC members are actively contributing to the project.     ## PMC changes:       - Currently 27 PMC members - No new PMC members added in the last 3 months   ## 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.0 on Wed Jan 04 2017  ----------------------------------------- Attachment BK: Report from the Apache SystemML Project [Deron Eriksson] ## Description: SystemML provides declarative large-scale machine learning (ML) that aims at flexible specification of ML algorithms and automatic generation of hybrid runtime plans ranging from single node, in-memory computations, to distributed computations such as Apache Hadoop MapReduce and Apache Spark. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We graduated as an Apache top-level project on May 18, 2017. - Third phase of GSoC project completed to automate performance testing. - We are currently voting on our first top-level project release (0.15.0). ## Health report: - Code activity is healthy with 285 commits in the last 3 months. - Community growth is healthy with 4 new contributors in the last 3 months. - Communication at a healthy level on mailing list, JIRAs, and pull requests. ## PMC changes: - Currently 23 PMC members. - Felix Schüler was elected as PMC member on April 19, 2017. ## Committer base changes: - Currently 23 committers. - Felix Schüler was elected as committer on April 19, 2017. ## Releases: - Version 0.14.0-incubating was released on May 8, 2017. ----------------------------------------- Attachment BL: 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: - No major updates and few discussions in Jira ## Health report: - This project is under 'maintain' mode. ## 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 20 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: - 104 subscribers (up 2 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@tajo.apache.org: - 28 subscribers (up 2 in the last 3 months): - 4 emails sent to list (1 in previous quarter) - user@tajo.apache.org: - 50 subscribers (up 1 in the last 3 months): - 0 emails sent to list (7 in previous quarter) ## JIRA activity: - 0 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BM: Report from the Apache Thrift Project [Jake Farrell] Apache Thrift is a framework for providing cross-platform RPC and serialization. Project Status --------- The Apache Thrift community is currently working on our 0.11.0 release candidate which will include a number of stability and performance enhancements to our Go, Node and Python client libraries [1]. We are targeting the availability of the 0.11.0 release candidate by end of September. Community --- Latest Additions: * PMC addition: Nobuaki Sukegawa, 1.25.2016 * Committer addition: James King, 10.18.2016 Issue backlog status since last report: * Created: 99 * Resolved: 70 Mailing list activity since last report: * @dev 1302 messages * @user 34 messages Releases --- Last release: 0.10.0, Release Date: 1.3.2017 Cut 0.11.0 branch, release candidate creation and testing in progress [1]: https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=tree;h=refs/heads/0.11.0;hb=refs/heads/0.11.0 ----------------------------------------- Attachment BN: Report from the Apache Tiles Project [Mick Semb Wever] ## Description: Apache Tiles is a free open-sourced templating framework for Java applications. Based upon the Composite pattern it is built to simplify the development of user interfaces. ## Activity: Apache Tiles saw more traffic project this quarter. An higher number of commits and traffic on the dev ML than normal. One meta release has passed and a public release is in progress. This will be followed by one more release. It looks like there will also be four more releases following this. There has been a few small fixes around the website. ## Health report: There are currently two responsive PMC, other PMC help out with votes when needed. A recent ML discussion showed there's still a small community of people that care. There remains a need to add another committer to the project. ----------------------------------------- Attachment BO: 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 Tomcat PMC is organising a small 1 day conference to be held in London later this month. At the time of writing just under two thirds of the twenty available places have been sold and we have contingency plans in place to double capacity should a last minute rush take us over twenty. Thanks to the combination of generous sponsorship and ticket sales we are on track to have a sufficient surplus of funds after this event to provide seed money (e.g. to book venues, subsidize speaker travel) for the next event. The aim is to be able to hold a handful of small events a year - based nearish committers to reduce speaker travel costs - that are self-financing so they can survive without ongoing sponsorship or subsidy / financial guarantees from either the ASF or individual PMC members. If we are fortunate enough to obtain sponsorship then that will open up the possibility of bringing in more speakers and/or more frequent events. We intend to publish 'accounts' after each event so the community has visibility of how the events are being financed. If, for any reason, we decide to discontinue these events, any remaining funds will be transferred to the ASF. ## PMC changes: - Currently 26 PMC members. - New PMC members: - Coty Sutherland was added to the PMC on Thu May 18 2017 - Huxing Zhang was added to the PMC on Thu May 18 2017 ## Committer base changes: - Currently 44 committers. - Michael Osipov was added as a committer on Mon May 08 2017 ## Releases: - Apache Tomcat 7.0.79 was released on Sat Jul 01 2017 - Apache Tomcat 7.0.81 was released on Wed Aug 16 2017 - Apache Tomcat 8.0.45 was released on Sat Jul 01 2017 - Apache Tomcat 8.0.46 was released on Fri Aug 18 2017 - Apache Tomcat 8.5.16 was released on Mon Jun 26 2017 - Apache Tomcat 8.5.20 was released on Tue Aug 08 2017 - Apache Tomcat 9.0.0.M22 was released on Mon Jun 26 2017 - Apache Tomcat 9.0.0.M26 was released on Tue Aug 08 2017 ## 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 - Important: Security Constraint Bypass CVE-2017-7675 The HTTP/2 implementation bypassed a number of security checks that prevented directory traversal attacks. It was therefore possible to bypass security constraints using an specially crafted URL. Affects: 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15 - Moderate: Cache Poisoning CVE-2017-7674 The CORS Filter did not add an HTTP Vary header indicating that the response varies depending on Origin. This permitted client and server side cache poisoning in some circumstances. Affects: 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15, 7.0.0 to 7.0.77 ----------------------------------------- Attachment BP: Report from the Apache Twill Project [Terence Yim] Apache Twill is an abstraction over Apache Hadoop YARN to reduce the complexity of developing distributed applications. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Working on more regular release interval. ## Health report: - Made one release since Jun 2017 ## PMC changes: - Currently 6 PMC members - Last PMC addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 8 committers and 23 contributors - No new committer added in the last 3 months - One new contributor added in the last 3 months - Last committer addition was Martin Serrano on Feb 24, 2017 - Last contributor addition was Yuliya Feldman on June 24, 2017 ## Releases: - Last release was release 0.12.0 on August 24, 2017 ## Mailing list activity: - dev@twill.apache.org: - 72 subscribers - 252 emails sent to the list in past three months (360 in last report) - commits@twill.apache.org: - 19 subscribers - 82 emails sent to the list in past three months (125 in last report) ## JIRA activity: - 7 new JIRA tickets created in the last month - 3 JIRA tickets resolved in the last month ----------------------------------------- Attachment BQ: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for September 2017. 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. Dates: 30 Aug 2017 (new) last release - Apache UIMA DUCC 2.2.1 03 May 2016 (no change) last PMC addition 18 Apr 2017 (no change) last Committer addition Releases: 30 Aug 2017 Apache UIMA DUCC 2.2.1 29 Aug 2017 Apache Java SDK 2.10.1 24 Jul 2017 Apache UIMA Ruta 2.6.1 Activity: Most major projects (Java SDK, DUCC, uimaFIT, RUTA) are actively being worked on. The Java SDK version 3 had another release candidate for a beta version. Testing of version 3 with other parts of UIMA is being done, as part of the beta version release candidate. Mailing list activity remains moderate, with people from the extended community helping out by answering questions. Community: The community continues to be moderately active. Issues: No Board level issues at this time. ----------------------------------------- Attachment BR: Report from the Apache VCL Project [Andy Kurth] ## 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: - Development of the remaining issues regarding VCL 2.5 was finished. - VCL 2.5 was released on August 22nd. - Prior to the release, the steps listed on the ASF's crypto page were completed. [1] Apache VCL is now listed on the exports page. [2] - Development has obviously slowed since the push to get the release out. Some work is being done to update documentation. ## Health report: - Health continues to be a concern. Only 3 committers/PMC members voted in the VCL 2.5 release thread. [3] - We have recently seen involvement from new community members interested in contributing some features which could significantly help modernize the codebase. [4][5] ## 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 8 committers. - No new committers added in the last 3 months - Last committer addition was Young Hyun Oh at Sun Dec 08 2013 ## Releases: - Last release was 2.4.2 on Wed Apr 15 2015 (Note: I'll work to figure out why the most recent release isn't being detected by the report generation tool) ## Mailing list activity: - Dev list traffic continued to be heavy relative to what VCL's dev list usually sees. This is surely due to the flurry of activity related to the release. - User list traffic has been pretty light. I hope to see an uptick as people and organizations (hopefully) upgrade to VCL 2.5. - dev@vcl.apache.org: - 124 subscribers (up 2 in the last 3 months): - 202 emails sent to list (302 in previous quarter) - user@vcl.apache.org: - 167 subscribers (up 5 in the last 3 months): - 14 emails sent to list (42 in previous quarter) ## JIRA activity: - 25 JIRA tickets created in the last 3 months - 25 JIRA tickets closed/resolved in the last 3 months [1] https://www.apache.org/dev/crypto.html [2] http://www.apache.org/licenses/exports/ [3] http://markmail.org/thread/hpwlzijtxtxu4xl5 [4] http://apache.markmail.org/thread/h5koov2mzrarwrhw [5] http://apache.markmail.org/thread/vr2vlxin4fxmwcmz ----------------------------------------- Attachment BS: Report from the Apache Wicket Project [Martijn Dashorst] Report from the Apache Wicket project [Martijn Dashorst] Apache Wicket is an open source Java component oriented web application framework. ## Noteworthy items: - 3 releases, 1 attempt at emergency fix (7.8.1, cancelled) were performed - Wicket 8 is around the corner ## Issues: - No issues require board attention. ## Activity: - The free ride we got from OpenShift for hosting our examples projects (we have 3 actively maintained branches with each an examples project) is over, so we are pursuing an ASF hosted VM for our examples. Infra and the PMC are working together to get this completed. - A major issue was discovered in 7.8.0, where upon a user logging out, the corresponding storage for its session was not cleaned up in Wildfly. The fix we implemented for a 7.8.1 release created problems for Tomcat, so 7.8.1 was not released. A more proper fix has now been applied and is under test. A 7.9.0 release will be forth coming. This was a nice example of the community working together to fix the issue again and again. - We are on the cusp of releasing Wicket 8, so we'll be working with Sally for the corresponding press coverage. ## 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. ## 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.27.0 was released on Thu Jul 06 2017 - 7.8.0 was released on Wed Jul 12 2017 - 8.0.0-M7 was released on Sat Aug 12 2017 ----------------------------------------- Attachment BT: Report from the Apache Yetus Project [Sean Busbey] ## 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: No new PMC additions in this period; our last PMC addition was Ajay Yadava on Dec 1st, 2016. There are currently 8 PMC members. No new committer additions in this period; our last committer additions were Andrew Wang and Ajay Yadava on Sep 20th, 2016. There are currently 10 committers. Community is working on 0.5.1, an emergency release to fix a critical, non-security bug on some platforms. ## Health report: Apache Yetus is now two years old! "A rising tide lifts all boats." Contributions remain low but fairly consistent. Most contributions are related to other Apache projects investigating or migrating to using Apache Yetus in their workflows. The project is healthy given our goal of a common shared space for exactly these kinds of common tasks, despite the appearance low activity level. Our challenge remains to keep these new contributors engaged enough beyond getting their project up and running. ## Releases: - 0.5.0 was released on Mon Jul 10 2017 ## Mailing list activity: - dev@yetus.apache.org: - 42 subscribers (up 1 in the last 3 months): - 123 emails sent to list (124 in previous quarter) - notifications@yetus.apache.org: - 18 subscribers (up 2 in the last 3 months): - 267 emails sent to list (289 in previous quarter) ## JIRA activity: - 25 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BU: Report from the Apache ZooKeeper Project [Flavio Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables distributed systems to implement a variety of primitives and mechanisms that are critical for them to function, e.g., distributed locks, master election, group membership, and configuration. ## Issues: There are no issues requiring board attention at this time. ## Activity: There has been no significant change to the project status since the last report. There has been no addition to the set of committers or PMC. The traffic of mailing lists has not changed significantly, although the number of subscribers has increased slightly and the overall number of messages to the dev list has dropped. ## Health report: The PMC has been working with contributors and committers to get them to the point that both committership and PMC membership, respectively, can be offered. ## PMC changes: - Currently 13 PMC members. - Michael Han was added to the PMC on Wed Jun 21 2017 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Mohammad Arshad at Mon Jan 23 2017 ## Releases: - Last release was 3.5.3 on Mon Apr 17 2017 ## Mailing list activity: Dev list traffic has dropped by ~10%. User list traffic has increases by 15%. The traffic drop of the mailing lists is very likely due to the summer vacation period, which is typically a bit slower. - dev@zookeeper.apache.org: - 520 subscribers (up 4 in the last 3 months): - 3257 emails sent to list (3622 in previous quarter) - user@zookeeper.apache.org: - 1216 subscribers (up 17 in the last 3 months): - 150 emails sent to list (131 in previous quarter) ## JIRA activity: - 90 JIRA tickets created in the last 3 months - 44 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BV: Report from the Apache Marmotta Project [Jakob Frank] ## Description: Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013. ## Issues: There are no major issues requiring board attention at this time. ## Activity: Another period of low activity, also caused by an extra summer-low. We're still struggling to ensure the midterm viability of the project. Google Summer of Code brought us an engaged student working on the task of upgrading from Sesame to Eclipse RDF4J. The codebase shows good progress, but was not finished due to open issues within the codebase and third-party libraries. More details in our wiki (https://s.apache.org/tVx6) and the related PR (https://s.apache.org/o38k) ## Health report: The project was considered feature-complete in 3.3.0. The current release cycle (3.4.0) focuses on refining and fixing bug, plus incorporation some non-core new features. The development activities (issues, commits, emails) have significantly come down in the last year. ## PMC changes: - Currently 11 PMC members. - Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016 ## Committer base changes: - Currently 13 committers. - Xavier Sumba was added as a committer on Mon Mar 27 2017 ## Releases: - Last release was 3.3.0 on Fri Dec 05 2014 ## Mailing list activity: - users@marmotta.apache.org: - 116 subscribers (up 4 since last report) - 4 emails sent to list (7 in previous report) - dev@marmotta.apache.org: - 101 subscribers (up 1 since last report) - 183 emails sent to list (101 in previous report) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BW: Report from the Apache Oltu Project [Antonio Sanso] ----------------------------------------- Attachment BX: Report from the Apache Serf Project [Bert Huijben] ## Description: The serf library is a high performance C-based HTTP client library built upon the Apache Portable Runtime (APR) library. Serf is the default client library of Apache Subversion, Apache OpenOffice and mod_pagespeed. ## Issues: There are no issues requiring board attention at this time. ## Activity: There hasn't been much activity over the last few months, but in the last few weeks a number of network test scenarios were run for Subversion, which found a few minor issues in older versions. The patches for these issues are already backported to the maintenance branches. We expect that we will put out a new release with these fixes within a few weeks. ## Health report: Activity is at a normal, fairly quiet level. The serf project's activity is quite related to that of Subversion and with that projects recent affairs we slowed more than expected. ## PMC & Committer changes: Currently 12 PMC members and 13 committers. We added Evgeny Kotkov as Committer and PMC member this April. ## Releases: Apache Serf 1.3.9 was released on Thu Sep 01 2016 ## Mailing list and Jira activity: Normal slow activity. ----------------------------------------- Attachment BY: Report from the Apache Usergrid Project [Todd Nine] ----------------------------------------- Attachment BZ: Report from the Apache Xalan Project [Steven J. Hathaway] The Apache Xalan Project develops and maintains libraries and programs that transform XML documents using XSLT standard stylesheets. Our subprojects use the Java and C++ programing languages to implement the XSLT libraries. Xalan is a mature project, but we are hoping to acquire more committers who can help with integration builds for a new release that integrates Xerces-C. ISSUES FOR THE BOARD This report should have been submitted last month (August 2017). CURRENT ACTIVITY Most activity has been through JIRA issue tracking. The email lists have seen little activity. We are reviewing the background of a committer of another Apache project that may be willing to participate with Xalan-C activities. MEMBERSHIP Changes in the PMC membership: None. Last new committer: May 2014 PROJECT RELEASES Xalan Java 2.7.2 April 15, 2014 Xalan C/C++ 1.11 October 31, 2012 Publishing of project releases was refreshed Oct 30, 2014. OTHER ISSUES We would still appreciate more active persons to build Xalan-C tests. We continue to get requests for Xalan to support XSLT version 2. The Xalan libraries currently support XSLT version 1. Feature ugrades and migration will require more than a few committers. BRANDING ISSUES None. ----------------------------------------- Attachment CA: Report from the Apache Xerces Project [Michael Glavassevich] ------------------------------------------------------ End of minutes for the September 20, 2017 board meeting.