The Apache Software Foundation Board of Directors Meeting Minutes June 21, 2017 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:38 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/39p6 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 Brett Porter Phil Steitz Mark Thomas Directors Absent: Jim Jagielski Chris Mattmann Executive Officers Present: Kevin A. McGrail Sam Ruby Craig L Russell Executive Officers Absent: Ross Gardler Ulrich Stärk Guests: Daniel Gruno Greg Stein John D. Ament P. Taylor Goetz Tom Pappas 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of May 17, 2017 See: board_minutes_2017_05_17.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] We had a productive face to face meeting in McLean last week, covering topics about the next 5 years of the Foundation, how we might best support the growth of healthy project communities and our own membership in line with the mission of the Foundation, and some key operational considerations. I will work with Craig over the next week to publish the formal minutes and a summary of the work done, as well as starting to track the action items that resulted from the meeting. I'd like to thank the board, officers and members who took the time out of their schedules to attend, including the support many received from their employers. In particular, our thanks to Capital One for hosting us at their McLean facilities and for sponsoring our pre-meeting dinner. Thank you to Craig also for driving the changes in the board list discussed at the previous meeting. I hope these will serve to allow more focused discussion on board-level items among the board, officers and interested members. I have indicated to the board that I intend to step down from the role as Chairman, and at the face to face we discussed a succession plan. I will transition the role over the following months. It has been fun, and I'm privileged to have had the opportunity over the last 4 years. B. President [Sam] My current priorities: Fundraising, EA/TAC, then Brand Management. Items requiring board attention: None. - - - Financially, we started off the FY strong. I caution everybody that much of this is due to revenue that we should have received last year hitting the books this year. And we have a one time revenue windfall due to converting bitcoins to cash. That being said, all things considered, in one month we made up for the larger than expected full year deficit in FY17 and then some by over $20K. The Fundraising president's committee has updated its roster and divided up the list of sponsors and is making great progress in re-establishing connections. In particular, Sally has stepped up and is leading this charge. Virtual's role in fundraising has been expanded, and the additional expense should be containable in the current budget. Fundraising has a new nofollow policy, rewarding Bronze level sponsors who have a sustained committment. An audit of ASF sites shows that many foundation requirements for links to such things as sponsorship and conferences are being ignored. Each of the operations areas are going to work together to determine a way to resolve this in a centralzed way. See https://whimsy.apache.org/site/. Brand Management continues normally, including working through legal issues related to registrations for two projects. EA's focus has remained primarily on conferences. In the upcoming months, I plan to get with Rich, Melissa, and others to revisit this. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] Summary from Virtual: Here is a brief summary of the Foundation’s performance for the first month of FY18. Cash at May 31st 2017 was $1,639.9K, which is up $124.6K from last month’s ending balance (Apr 17) of $1,515.3K, due to the timing of some Sponsor payments. The May 2017 cash balance is down $134.8K from the May 2016 month end balance of $1,774.7K, however AR is up $100K from May of 2016. The May 2017 ending cash balance of $1,639.9K represents a cash reserve of 14.2 months at the end of May 2017 based on the FY18 Cash forecast average monthly spending of $115.2K/month. The ASF reserve continues to be very healthy for an organization of ASF’s size, with an FY18 YE estimate of 12 months cash reserve. Regarding the Cash P&L, for May 2017, we are starting out very well right out of the gate due to some timing issues. Revenue was $241.8K vs a budget of $116.6K. This was due to the Platinum Sponsor payment for Pivotal Labs which had been forecasted to arrive in April but actually hit the bank in May as well as $21.5K of Coinbase ( Kevin did a fantastic job cashing out the bitcoin donation) and $2.7K from Hopsie. This left us $125.2K ahead of bud through May 2017. The open AR at this point is over $406K, again $100K more than last year at this time and with the increased Sponsorship effort and follow through we are well on our way to making our numbers for FY18. In addition to this I would also like to point out that year over year for May we were $163K ahead in revenue, while only $16K ahead in expense for a NI for May 2017 that $147K better than May of 2016 again a very good way to start off FY 18. In May 2017 expenses were in total under Budget by $5.6K. There were a few variances, which I will circle back with the respective budget stake holders to make sure it was just timing and will factor that into an updated forecast, which will include an updated revenue forecast based on the updated fundraising efforts over the past couple of weeks. With regard to Net Income (NI), for May 2017 the ASF finished with a positive $124.7K NI vs a budgeted negative $6.2K NI or $130.9K ahead of Budget for the first month of FY18, as compared to the Negative $131K NI for April 2017 again starting off FY18 on a great note. Report from Assistant Treasurer: Bitcoins - We received and have effectively cashed in on all the bitcoins Donated to-date excepting 0.02965575 BTC which I transfered to Coinbase on 6/16 to zero out our multibit wallet. Corporate Service Company - Service and Annual Report - Virtual will be looking to switch/handle the annual report. We are currently paying just under $700 annually to CSC which is exorbitant in comparison to the work required. Thanks to Roy Fielding, the Safety Deposit box was closed and old checks shredded. Executed contract addendum for a $250/mo increase in fees with Virtual. This was already known and encompassed in the budget. We are discussing an Audit and vendors to perform the work with Virtual. The ASF has never undergone an audit which is helpful for Guidestar and similar fundraising requirements. We have had a successful financial review. Items Still Tracking: - Contribution Language for Car Donations - Payment Privacy changes to move away from Dropbox, etc. - CDARS - Virtual is working towards a method to FDIC insure our entire balance and is researching CDARS - Network for Good - Missing a $125 check - Credit Card with a lower foreign transaction fee still being researched Things should be slower for Treasurer role as I believe many of the tasks I’ve been working on for the past many months have been coming to completion. Other than that, Uli is quite busy with a new child (Congrats!) so if there are time-sensitive issues for the treasurer, please ping me. Board Summary Financials: Current Balances: Citizens Money Market 1,465,786.77 Citizens Checking 171,131.62 Paypal - ASF 2,983.86 Total Checking/Savings 1,639,902.25 May-17 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 24,177.42 1,302.98 22,874.44 Sponsorship Program 215,000.00 115,000.00 100,000.00 Programs Income 0.00 0.00 0.00 Other Income 2,660.10 0.00 2,660.10 Interest Income 0.00 292.92 -292.92 Total Income 241,837.52 116,595.90 125,241.62 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 76,677.78 74,956.17 1,721.61 Sponsorship Program 2,341.90 3,250.00 -908.10 Programs Expense 0.00 0.00 0.00 Publicity 24,687.76 16,000.00 8,687.76 Brand Management 1,697.02 7,416.67 -5,719.65 Conferences 460.03 4,000.00 -3,539.97 Travel Assistance Committee 0.00 5,000.00 -5,000.00 Tax and Audit 0.00 0.00 0.00 Treasury Services 3,100.00 3,100.00 0.00 General & Administrative 8,228.19 9,077.86 -849.67 Total Expense 117,192.68 122,800.70 -5,608.02 Net Income 124,644.84 -6,204.80 130,849.64 YTD 2017 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 24,177.42 1,302.98 22,874.44 Sponsorship Program 215,000.00 115,000.00 100,000.00 Programs Income 0.00 0.00 0.00 Other Income 2,660.10 0.00 Interest Income 0.00 292.92 -292.92 Total Income 241,837.52 116,595.90 122,581.52 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 76,677.78 74,956.17 1,721.61 Sponsorship Program 2,341.90 3,250.00 -908.10 Programs Expense 0.00 0.00 0.00 Publicity 24,687.76 16,000.00 8,687.76 Brand Management 1,697.02 7,416.67 -5,719.65 Conferences 460.03 4,000.00 -3,539.97 Travel Assistance Committee 0.00 5,000.00 -5,000.00 Tax and Audit 0.00 0.00 0.00 Treasury Services 3,100.00 3,100.00 0.00 General & Administrative 8,228.19 9,077.86 -849.67 Total Expense 117,192.68 122,800.70 -5,608.02 Net Income 124,644.84 -6,204.80 130,849.64 D. Secretary [Craig] Secretary has completed the process of identifying committers with no ICLA on file and requesting infra to disable these accounts. In May, 67 iclas, five cclas, and one grant were received and filed. One member requested to transition to Emeritus status. E. Executive Vice President [Ross] No report was submitted. F. Vice Chairman [Chris] I have resigned as Vice Chairman and the board will appoint a new VC at the meeting. Thanks for the confidence of the Board in appointing me originally into the position. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Mark] See Attachment 8 B. Apache Legal Affairs Committee [Chris Mattmann] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Shane] See Attachment 10 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Axis [bp] # BVal [rb] # Bahir [bp] # Bloodhound [bp] # Camel [bp] # Eagle [bp] # Flex [rb] # Giraph [bp] # Hama [bp] # Helix [bp] # Incubator [rb] # Labs [bp] # Oltu [bp] # Pig [bp] # Sentry [bd] # Stanbol [bp] # Tajo [mt] # VCL [bp] # Yetus [bp] A. Apache ACE Project [Marcel Offermans / Brett] See Attachment A B. Apache Allura Project [Dave Brondsema / Rich] See Attachment B C. Apache Any23 Project [Lewis John McGibbney / Chris] See Attachment C D. Apache Archiva Project [Olivier Lamy / Bertrand] See Attachment D E. Apache Aurora Project [Jake Farrell / Phil] See Attachment E F. Apache Axis Project [Deepal Jayasinghe / Jim] No report was submitted. G. Apache Bahir Project [Luciano Resende / Ted] No report was submitted. H. Apache Beam Project [Davor Bonaci / Chris] See Attachment H I. Apache Bigtop Project [Evans Ye / Phil] See Attachment I J. Apache Bloodhound Project [Gary Martin / Brett] No report was submitted. K. Apache BVal Project [Matt Benson / Rich] See Attachment K L. Apache Camel Project [Christian Mueller / Ted] No report was submitted. M. Apache CarbonData Project [Liang Chen / Mark] See Attachment M N. Apache Cayenne Project [Michael Gentry / Bertrand] See Attachment N O. Apache Chemistry Project [Florian Müller / Jim] See Attachment O P. Apache CloudStack Project [Wido den Hollander / Shane] See Attachment P Q. Apache Commons Project [Gary D. Gregory / Ted] See Attachment Q R. Apache Cordova Project [Shazron Abdullah / Brett] See Attachment R S. Apache cTAKES Project [Pei J Chen / Mark] See Attachment S T. Apache Curator Project [Jordan Zimmerman / Bertrand] See Attachment T U. Apache Eagle Project [Edward Zhang / Phil] No report was submitted. V. Apache Falcon Project [Srikanth Sundarrajan / Shane] See Attachment V W. Apache Felix Project [Carsten Ziegeler / Jim] See Attachment W X. Apache Fineract Project [Myrle Krantz / Chris] See Attachment X Y. Apache Flex Project [Alex Harui / Rich] See Attachment Y @Mark: Take suggestions for improving communication back to the project Z. Apache Flink Project [Stephan Ewen / Chris] See Attachment Z AA. Apache Giraph Project [Avery Ching / Shane] No report was submitted. AB. Apache Gump Project [Stefan Bodewig / Rich] See Attachment AB AC. Apache Hama Project [Edward J. Yoon / Mark] No report was submitted. AD. Apache Helix Project [Kishore Gopalakrishna / Jim] No report was submitted. AE. Apache Hive Project [Ashutosh Chauhan / Bertrand] See Attachment AE AF. Apache Incubator Project [Ted Dunning] See Attachment AF AG. Apache Jackrabbit Project [Michael Dürig / Ted] See Attachment AG AH. Apache Karaf Project [Jean-Baptiste Onofré / Phil] See Attachment AH AI. Apache Labs Project [Danny Angus / Brett] No report was submitted. AJ. Apache Lucene Project [Tommaso Teofili / Phil] See Attachment AJ AK. Apache Lucene.Net Project [Prescott Nasser / Jim] See Attachment AK AL. Apache Metron Project [Casey Stella / Ted] See Attachment AL AM. Apache OFBiz Project [Jacopo Cappellato / Rich] See Attachment AM AN. Apache Olingo Project [Christian Amend / Shane] See Attachment AN AO. Apache Oltu Project [Antonio Sanso / Bertrand] No report was submitted. AP. Apache OODT Project [Tom Barber / Brett] See Attachment AP AQ. Apache OpenNLP Project [Jörn Kottmann / Chris] See Attachment AQ AR. Apache OpenWebBeans Project [Mark Struberg / Mark] See Attachment AR AS. Apache Pig Project [Daniel Dai / Chris] No report was submitted. AT. Apache Pivot Project [Roger Whitcomb / Shane] See Attachment AT AU. Apache Polygene Project [Paul Merlin / Jim] See Attachment AU AV. Apache Portable Runtime (APR) Project [Nick Kew / Mark] See Attachment AV AW. Apache Portals Project [David Sean Taylor / Phil] See Attachment AW AX. Apache Sentry Project [Alex Kolbasov / Bertrand] See Attachment AX @Bertrand: Help PMC chair to provide a better report; next month please AY. Apache ServiceMix Project [Krzysztof Sobkowiak / Rich] See Attachment AY AZ. Apache Shiro Project [Les Hazlewood / Ted] See Attachment AZ BA. Apache Sling Project [Carsten Ziegeler / Brett] See Attachment BA BB. Apache SpamAssassin Project [Sidney Markowitz / Mark] See Attachment BB BC. Apache Stanbol Project [Fabian Christ / Rich] No report was submitted. BD. Apache Storm Project [P. Taylor Goetz / Phil] See Attachment BD BE. Apache Synapse Project [Isuru Udana / Jim] See Attachment BE BF. Apache SystemML Project [Deron Eriksson / Chris] See Attachment BF BG. Apache Tajo Project [Hyunsik Choi / Bertrand] See Attachment BG @Ted: Discuss state of development with PMC; encourage on-list development BH. Apache Tiles Project [Mick Semb Wever / Ted] See Attachment BH BI. Apache Tomcat Project [Mladen Turk / Brett] See Attachment BI BJ. Apache Twill Project [Terence Yim / Shane] See Attachment BJ BK. Apache UIMA Project [Marshall Schor / Bertrand] See Attachment BK BL. Apache VCL Project [Andy Kurth / Phil] No report was submitted. BM. Apache Wicket Project [Martijn Dashorst / Rich] See Attachment BM BN. Apache Yetus Project [Sean Busbey / Mark] No report was submitted. BO. Apache ZooKeeper Project [Flavio Junqueira / Brett] See Attachment BO Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Incubator Project Chair WHEREAS, the Board of Directors heretofore appointed Ted Dunning (tdunning) to the office of Vice President, Apache Incubator, and WHEREAS, the Board of Directors is in receipt of the resignation of Ted Dunning from the office of Vice President, Apache Incubator, and WHEREAS, the Project Management Committee of the Apache Incubator project has chosen by vote to recommend John D. Ament (johndament) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ted Dunning is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Incubator, and BE IT FURTHER RESOLVED, that John D. Ament be and hereby is appointed to the office of Vice President, Apache Incubator, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Incubator Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Drill Project Chair WHEREAS, the Board of Directors heretofore appointed Parth Chandra (parthc) to the office of Vice President, Apache Drill, and WHEREAS, the Board of Directors is in receipt of the resignation of Parth Chandra from the office of Vice President, Apache Drill, and WHEREAS, the Project Management Committee of the Apache Drill project has chosen by vote to recommend Aman Sinha (amansinha) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Parth Chandra is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Drill, and BE IT FURTHER RESOLVED, that Aman Sinha be and hereby is appointed to the office of Vice President, Apache Drill, 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 Drill Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache Atlas 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 scalable and extensible set of core foundational governance services - enabling enterprises to effectively and efficiently meet their compliance requirements. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Atlas Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Atlas Project be and hereby is responsible for the creation and maintenance of software related to a scalable and extensible set of core foundational governance services - enabling enterprises to effectively and efficiently meet their compliance requirements; and be it further RESOLVED, that the office of "Vice President, Apache Atlas" 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 Atlas Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Atlas 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 Atlas Project: * Aaron Dossett * Andrew Ahn * Arun C. Murthy * Apoorv Naik * Ayub Pathan * Barbara Stortz * Chris Hyzer * Daniel Markwat * Darshan Kumar * Dave Kantor * Dennis Fusaro * Greg Senia * Harish Butani * Hemanth Yamijala * Jeffrey Hagelberg * Jitendra Pandey * Jon Maron * Kalyani Kashikar * Keval Bhatt kbhatt * Madhan Neethiraj * Mitch Schussler * Neeru Gupta * Nixon Rodrigues * Sarath Subramanian * Shwetha GS * Srikanth Sundarrajan * Suma Shivaprasad * Suresh Srinivas * Tom Beerbower * Venkat Ranganathan * Venkatesh Seetharam * Vimal Sharma * Vinod Kumar Vavilapalli NOW, THEREFORE, BE IT FURTHER RESOLVED, that Madhan Neethiraj be appointed to the office of Vice President, Apache Atlas, 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 Atlas 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 Atlas Project; and be it further RESOLVED, that the Apache Atlas Project be and hereby is tasked with the migration of the Apache Incubator Atlas podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Atlas polling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache Atlas Project, was approved by Unanimous Vote of the directors present. D. Establish the Apache MADlib 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 scalable, Big Data, SQL-driven machine learning framework for Data Scientists. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache MADlib Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache MADlib Project be and hereby is responsible for the creation and maintenance of software related to a scalable, Big Data, SQL-driven machine learning framework for Data Scientists. RESOLVED, that the office of "Vice President, Apache MADlib" 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 MADlib Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache MADlib 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 MADlib Project: Sarah Aerni Greg Chase Aaron Feng Rahul Iyer Jim Jagielski Nandish Jayaram Anirudh Kondaveeti Orhan Kislal Frank McQuillan Srivatsan R Rashmi Raghu Roman Shaposhnik Atri Sharma NOW, THEREFORE, BE IT FURTHER RESOLVED, that Aaron Feng be appointed to the office of Vice President, Apache MADlib, 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 MADlib 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 MADlib Project; and be it further RESOLVED, that the Apache MADlib Project be and hereby is tasked with the migration and rationalization of the Apache Incubator MADlib podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator MADlib podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7D, Establish the Apache MADlib Project, was tabled. E. Change the Apache Turbine Project Chair WHEREAS, the Board of Directors heretofore appointed Thomas Vandahl (tv) to the office of Vice President, Apache Turbine, and WHEREAS, the Board of Directors is in receipt of the resignation of Thomas Vandahl from the office of Vice President, Apache Turbine, and WHEREAS, the members of the Apache Turbine Project Management Committee have chosen by vote to recommend Georg Kallidis (gk) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Thomas Vandahl is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Turbine, and BE IT FURTHER RESOLVED, that Georg Kallidis be and hereby is appointed to the office of Vice President, Apache Turbine, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7E, Change the Apache Turbine Project Chair, was approved by Unanimous Vote of the directors present. F. Establish the Apache Mynewt 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 embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Mynewt Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mynewt Project be and hereby is responsible for the creation and maintenance of software related to an embedded OS optimized for networking and built for remote management of constrained devices that are incapable of running either Linux or Android. RESOLVED, that the office of "Vice President, Apache Mynewt" 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 Mynewt Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mynewt 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 Mynewt Project: Justin Mclean P. Taylor Goetz Greg Stein Jim Jagielski Sterling Hughes Marko Kiiskila Will Sanfilippo Christopher Collins Vipul Rahane Fabio Utzig Andrzej Kaczmarek Michał Narajowski Szymon Janc Łukasz Rymanowski Neel Natu Peter Snyder Paul Dietrich Julian Ingram Aditi Hilbert NOW, THEREFORE, BE IT FURTHER RESOLVED, that Justin Mclean be appointed to the office of Vice President, Apache Mynewt, 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 Mynewt 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 Mynewt Project; and be it further RESOLVED, that the Apache Mynewt Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Mynewt podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Mynewt podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7F, Establish the Apache Mynewt Project, was approved by Unanimous Vote of the directors present. G. Motion for Licensing for a Closely Related Company NOTE: There is nothing in the ASF charter that prevents this concept from being done underneath our current 501(c)(3) umbrella; and Nothing that stops an external party from doing most everything here with the exception of using our brands and marks in compliance with our established policies. The mechanism of using a related company is chosen for political reasons, not technical or legal. However, it should be noted that the motion has been discussed both from an internal execution and external licensing perspective for the purposes of documenting this information for the next 3-5 years. WHEREAS, the Apache Software Foundation wishes to ensure the longevity and success of the foundation; and WHEREAS, the Board of Directors agrees that the licensing assets of the organization can provide a useful and beneficial source of subsistence; and WHEREAS, the Board of Directors agrees that the foundation exists to provide free, open-source software for the public good; and WHEREAS, the Board of Directors agrees that foundation is a volunteer-driven charity that provides products as-is, without warranty or guarantee of fitness for use; and WHEREAS, the Board of Directors agrees that the foundation does not wish to obligate itself to provide additional, related services and products; and WHEREAS, the Board of Directors wishes to facilitate the provision of these related services and products; and WHEREAS, the Board of Directors recognizes the value of these related services and products but does not wish to assume the costs and legal liability to do so; and WHEREAS, the Board of Directors agrees that the foundation wishes to license certain assets specified herein to a corporation yet to be formed that but shall be referred to for the purposes of this motion as the APACHE MEDIA CORPORATION, or AMC. NOW, THEREFORE, BE IT RESOLVED, that the Apache Software Foundation shall license the following: 1) The perpetual license to create a derivative mark and corporate name based on the foundation name and logos. 2) The exclusive outside vendor rights for 2 years beginning October 1, 2017 to certify Apache products, vendors, training, exams, certifications and services in North America, Europe and Asia as well as to claim association and support. Such rights shall specifically exclude electronic or physical books; and conferences attended by more than 75 persons. However, this license shall not impede the foundation itself from performing any actions in any manner internally without the use of outside parties. 3) The rights in paragraph 2 shall automatically renew under the same terms herein unless notification from either party is received thirty days prior to the renewal date. BE IT FURTHER RESOLVED that in return for these valuable licenses, the following conditions shall be met: 1) A foundation member and executive officer shall found the AMC in his personal capacity; and 2) The AMC shall donate 15% of all net income with a minimum floor of $10,000 USD per quarter beginning on October 1, 2017 with the first payment necessary to fully ratify this agreement; and 3) The founding member shall personally guarantee the minimum floor payments up to $80,000 USD owed; and 4) The AMC shall be vendor neutral using processes with equivalent terms for all applicants; and 5) The President & Chair of the foundation shall automatically be two of the five initial AMC Board of Director members to ensure that it best exemplifies the Apache Way. However, should the President and/or Chair decline the automatic membership, the foundation shall have the right to appoint their replacement(s); and 6) The foundation shall have the right to appoint an additional board of director member for every three additional AMC board members added; and 7) The foundation shall maintain the right to replace their representatives to the board at any time for any reason as they see fit; and 8) The AMC is solely responsible to define, ensure and defend materials, products, services and vendors certifications are sufficient to the purpose and intent of the foundation and further remove all liability and responsibility from the foundation; and 9) Oversight of AMC contracts and dealings shall be provided through the AMC board membership granted to the foundation which shall be expressly permitted for discussed on the board-private@apache.org mailing list; and 10) The AMC shall enact a strict COID policy that is incumbent on employees, consultants, contractors and other parties alike to require full conflict of interest disclosures when involved with matters of the foundation. Said disclosure shall specifically NOT require abstention or recusal as it is expected that people may serve roles on behalf of the AMC and the foundation; and 11) The AMC is solely responsible for expenses incurred in the execution of this contract up to a maximum of $2,000 USD for the foundation’s legal review; and 12) The AMC shall indemnify the foundation from any responsibility for damages or other liabilities arising from this agreement; and 13) In recognizing the goal of Open Source Software and the Apache Way, materials that are generated and in use externally such as coursework, books, training videos and exams shall AT A MINIMUM be released as “open source” materials under the Apache Software License v2 or greater within a period not to exceed two years from the time of first external use; and 14) The AMC will be solely responsible for all contractual obligations in these matters and shall not be licensed to obligate the foundation in any way. 15) The AMC exists to help buoy the success of the foundation and to ensure monies are not siphoned away, shall use requirements for major contracts in excess of $25,000 USD annually that stipulate being an ASF Sponsor in good standing maintained at the same current sponsorship level for existing sponsors or becoming a sponsor as applicable. Special Order 7G, Motion for Licensing for a Closely Related Company, was disapproved by Unanimous Vote of the directors present. H. Update Legal Affairs Committee Membership WHEREAS, the Legal Affairs Committee of The Apache Software Foundation (ASF) expects to better serve its purpose through the periodic update of its membership; and WHEREAS, the Legal Affairs Committee is an Executive Committee whose membership must be approved by Board resolution. NOW, THEREFORE, BE IT RESOLVED, that the following contributor be added as a Legal Affairs Committee member: Roman Shaposhnik Special Order 7H, Update Legal Affairs Committee Membership, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Vice Chairman role Phil Steitz has been proposed to replace Brett as chair, and would like to have a transition, starting by taking the role of Vice Chair. The board appointed Phil Steitz to the role of Vice Chair. 9. Review Outstanding Action Items * Shane: please explain the comment regarding external org [ Cassandra 2017-02-27 ] Status: Complete: Explained earlier, it was the expected issue with a well known vendor changing their direction. * Chris: follow up on reported meeting between external parties not brought back [ Eagle 2017-02-27 ] Status: Email sent to the project RE: slack conversations https://s.apache.org/fgtb * Shane: follow up on brand action item [ Spark 2017-02-27 ] Status: Complete for board purposes; awaiting feedback from contact with the vendor, tracking in brand. * Mark: work on reminder to the PMC that decisions need to be made in public [ Mesos 2017-04-19 ] Status: Onoing. * Shane: where has the work been done on 0.12? [ Tajo 2017-04-19 ] Status: * Brett: take the discussion to the board@ list (!) and recommend a solution. [ Discussion Items 2017-05-17 ] Status: Split board into three lists: Done and done. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:20 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] *Monitoring of all email and following up with appropriate personnel when needed *Handled booth logistics for ACNA’17, ordered banners (as per Sally’s request), shipped the existing inventory of swag for giveaways *Set up and tore down booth – shipped banners and some swag back to my house – Sharan took the majority to have on-hand for the Europe events. *Staffed the booth at ACNA’17 – attendance was great, as always! We had lots of traffic stopping by every day! *Attended the ApacheCon Planner’s Meeting at ACNA’17 ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] * ISSUES FOR THE BOARD None. * OPERATIONS Presented the popular Practical Trademark Law for FOSS Projects at ApacheCon Miami which drew some great questions; similarly the curated Apache Way track by a number of different speakers went amazingly well and got lots of questions throughout the day. http://shaneslides.com/2017/05/Practical-Trademark-Law/ Using automation from Whimsy, published a comprehensive list of both registered and unregistered trademarks claimed by the ASF, including all software releases that projects have created DOAP files from: https://www.apache.org/foundation/marks/list/ Implemented Analytics with a vp-brand@ account for the /foundation/marks/* portion of the apache.org website, so we can better focus improvement efforts on how users are actually reading the documentation. Thanks to Mark Thomas for continuing to provide great answers to a variety of questions and for doing an excellent job with all issues around the Tomcat brand. * REGISTRATIONS & CONTRACTS Finalized registration paperwork relating to the incoming IMPALA and BROOKLYN trademarks, both donated during incubation. Continuing to work through legal issues related to registrations for two projects. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Kevin A. McGrail] Tobi.com did not renew as a bronze sponsor and has been removed from the sponsorship thank you page upon expiration. New Bronze Sponsors: HostPapa and Emirio have agreed to come on board. We are working on small but high fraud issues where the consensus is that bad actors are using our site to pre-test stolen creditcards and the billing address. Using a new Sponsor Onboard Questionnaire: https://docs.google.com/document/d/16CpuFD6aQNs41CXSGwKUOhQRSNkCgk4Fv-Uwa-QaXd k/edit Well liked by Virtual and it’s had minor revisions. Will continue refining and move towards likely something like an automa form. I have implemented this as our Official Bronze NoFollow Policy: The thank you link for Bronze level sponsors will contain a “NoFollow” tag. However, to reward sponsors committed to the long-term success of the ASF and free, open source software, we remove this attribute on links for repeat Bronze sponsors or for sponsors who pay for a three year Bronze sponsorship in advance. With this new policy, I’ve shelved the Bronze+ concept as OBE (Overcome by Events, no longer needed) Ambassador program has been going well. Thanks to Sally for leading the charge. Working to get foundational issues done like contracts, audits of sponsors, etc. Making headway. Executed contract with Virtual to increase their assistance with sponsorship at a cost increase of $750/mo as of May 1. This was already planned and encompassed in the budget. Will be listing Hopsie and Atlassian as in-kind sponsors. ApacheCon NorthAmerica was advertised on ~15 project sites. It was missing from our own www.apache.org as well as people.a.o, reporter.a.o, whimsical.a.o (not sure whimsy.a.o counts as it's more of an app) & reference.a.o The whimsy team coded up a quick script to check https://whimsy.apache.org/site/ Therefore, I request board approval to Update the Navigation links http://www.apache.org/foundation/marks/pmcs.html#navigation to make it a requirement to include an Apache overlay div to avoid design or dependency concerns on all ASF web properties include www.apache.rg that is centrally located/updated The update of this data will fall to VP Fundraising, VP Conferences & VP Marketing jointly. ----------------------------------------- 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: after a 7-year hiatus, Sally Khudairi has officially returned to work with ASF Fundraising, and has relaunched the ASF Sponsor outreach program with “ambassadorial” support from Rich Bowen, Jim Jagielski, Tom Pappas, Mark Thomas, and Hadrian Zbarcea. She published the seventh "Success at Apache" post https://s.apache.org/x9Be , and has confirmed authors through October 2017. Sally held Media & Analyst Training at ApacheCon, and is working on the the ASF Annual Report for FY2017, with the aim of publishing by the end of June. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 31 May 2017 - The Apache Software Foundation Announces Apache® SystemML™ as a Top-Level Project - 17 May 2017 - The Apache Software Foundation Announces Apache® Beam™ v2.0.0 - 15 May 2017 - The Apache Software Foundation Announces Apache® Samza™ v0.13 IV. Informal Announcements: 6 items were published on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 152 weekly summaries published to date. We actively promoted numerous ApacheCon presentations and activities during the event. We secured professional post-production editing services for 111 ApacheCon presentations that were successfully published onto Feathercast within 12 days of the conference close. We posted 16 items on LinkedIn, which garnered more than 108K collective organic impressions over the past month. 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 8 media queries, plus a handful of press interviews during ApacheCon. During ApacheCon, the tone of the State of the Feather presentation triggered some misunderstandings that led to negative press coverage. We addressed the issue directly during Media & Analyst Training and executed a comprehensive crisis communications plan that included publishing On The State of the Feather https://s.apache.org/Lz3t . Our efforts successfully blocked further media coverage, and our internal speaking points were also used by members of the greater Apache community to address various queries. The statement also resulted in 5x more impressions than our usual postings on LinkedIn. The ASF received 1,223 press clips vs. last month's clip count of 1,053. Media coverage of Apache projects yielded 3,144 press hits vs. last month's 4,560. Sally has worked with a small handful of organizations (including some ASF Sponsors) on correcting misleading information in press/marketing/social media documents and promotions. VII. Analyst Relations: we received no analyst queries during this timeframe. Apache was mentioned in 27 reports by Gartner, 2 reports by Forrester, 14 reports by 451 Research, and 10 reports by IDC. VIII. Graphics: the ASF Identity Style Guide (graphics/visual/branding) has been uploaded to http://apache.org/foundation/press/kit/ . Sally is also designing templates for ASF business cards in response to requests by several ASF representatives/spokespeople. IX. ApacheCon liaison: Sally will continue to support ApacheCon as the event evolves. X. (Non-ASF) Industry Events and Outreach liaison: we had a presence at OpenExpo in Madrid, with booth coverage by Sharan Foga, Jan Iverson, and Ignasi Barrera, who will be following up with those who attended the booth, as well as a potential ASF Sponsor. Ignasi also worked with Sally on developing localized collateral for the event, which can be utilized by the ASF Community Development (ComDev) team for future events. XI. Newswire accounts: we have 13 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017; any overflow needs will link to our new contract signed 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. The Infra team was able to meet last month during and after the ApacheCon in Miami. This was a chance for the entire team to get together to discuss work and for team bonding. Short Term Priorities ===================== - Discuss and possibly perform an additional Confluence upgrade to a more recent version - LDAP changes to better support project membership management, and to support Atlassian Crowd (a single sign-on system for their products) Long Range Priorities ===================== - Continue retiring ASF-owned hardware, reduce technical debt, and update documentation/runbooks Uptime Statistics ================= - Confluence was taken down to perform an emergency upgrade after we learned of a critical CVE in the version that we are running. - Jira was taken down for about two hours to perform a planned upgrade - We maintained our SLA requirements, even with the upgrades ----------------------------------------- Attachment 6: Report from the VP of Conferences [Rich Bowen] A month ago we ran ApacheCon North America in Miami. We had just over 500 in attendance. Feedback so far has been overwhelmingly positive. All audio from the event has been published to http://feathercast.org/ already. Thank you Sally for arranging a contractor to handle this editing and posting. We also have all raw audio if anybody wants to repurpose any of it. Various interviews with speakers and sponsors are still going on on FeatherCast at this time. All video from the event (keynotes and three additional tracks, sponsored by Comcast) are up on YouTube at https://s.apache.org/miamivideo and we are in the process of obtaining all of the raw video so that we can use that for other purposes if we wish. We will be further promoting these videos and podcasts on both @apachecon and @ApacheCommunity in the coming days and weeks. While at the event, we held a meeting discussing what ApacheCon will look like in the coming years. The full notes from that meeting were sent to the planners@apachecon.com mailing list, and may be seen here: https://s.apache.org/kpgw (Members only.) While you are encouraged to join that list if you are interested in the progress of this conversation, please understand that this is a working list, and extended philosophical discussions are discouraged. In the vein, the meeting at ApacheCon was very focused on actual objectives, and how to reach them, and was very productive. An enormous thank you to everyone who attended, and who were able to keep this away from the traditional complaint session we have seen in past years. We agreed to pursue three tracks: 1) Participate more actively in third-party events, providing both standalone "Apache Way" talks, as well as Apache tracks focusing primarily on The Apache Way ("Community > Code") and the Incubator ("Tomorrow's Software Today"). 2) Run ApacheCon as a convention of project events, but attempt to do so at much lower cost venues, focusing on University and Government facilities, rather than fancy hotels. 3) More inward-facing events, centered around F2F board meetings and Infra gatherings - which we will be holding anyway - and then making the space available for project summits and, possibly, sponsor meetings. Capture high-quality content (video, audio) for later use. I will leave the deeper details for the planners list, and encourage you to read the meeting notes (linked above) for many of the details that are omitted from this report. In the last few weeks, Apache participated in Open Expo Madrid - http://www.openexpo.es/en/ - spearheaded by Sharan Foga. We have also been approached by several events requesting Apache content, in line with point 1 above. And, pursuant to point 2, we have asked the Virtual events management team to provide a bid for such an event. Tom Pappas has notified us that, were they to take on such a task, it would involve an up-front retainer, which would involve Conferences making a request for budget to cover this. This would be a change from what Conferences has ever done in the past at the ASF, and so will no doubt involve more discussion. At this time, we do not have any plans to run an ApacheCon event in Europe. If you are asked about it, please stick to three points: 1) We will not be doing an official ApacheCon event in Europe in 2017. 2) We will be participating more actively in other conferences - please see http://apache.org/events and @apachecon for more details as we have them. 3) Please contact Rich Bowen for more details. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin] * 22 applications submitted; 12 accepted; 2 (later) declined the offer (1 couldn’t get the time off from work; the other was supported by his company); TAC supported a total of 10 recipients for ACNA’17 * Post-ApacheCon surveys sent to all TACers and dropped in svn * TAC Interview Requests sent to those who agreed to answering the interview questions. They will also be dropped in svn and included on the website under the “travel stories” once received. * Reimbursement request of $1,260 submitted for subsistence payment, which Melissa paid out-of-pocket (9*$125; 1*$120 (Dammina); 4*$3.75 (ATM service fees)). The reason I chose to do it this way was because there were several folks that weren’t due to hear back from the visa office until it would’ve been way too late to submit for a payment request, and I didn’t want to submit it early and have the numbers be off. Michelle and I spoke about this ahead of time. * $9,200 under budget! This is primarily due to the fact that two of the accepted (and included in the original budget) recipients declined the offer. * TACers did a fantastic job at their duties Stats that were sent to Sally for the Annual Report, which were provided by Nick and do not include ACNA’17 Miami: Of the people helped by TAC at Budapest and Vancouver, 3 have become members since the conference they attended, 2 have joined PMCs and 2 have become committers. Overall, the figures are: * People who weren't members at the conference, and now are: 23 * People who weren't committers at application, now are: 21 * People who weren't on PMCs at application, now are: 37 * People who now help with TAC: 4 (6 now with the addition of the new members after ACEU2016) * People who have never been/become committers: 27 * Unique people helped by TAC: 131 * Total number of TAC awards: 153 ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 9: Report from the Apache Legal Affairs Committee [Chris Mattmann] There have been a variety of license related questions, some policy related questions that added a license to Category-X on our resolved page, an issue related to a separate project on Github using a license it dubbed "Modified Apache 2.0 License", and an issue related to whether or not a project is able to use training data licensed under various licenses to produce new ALv2 NLP models trained on that data. There were also questions regarding if an ASF project could build code generation tools that were used to generate non ALv2 and/or permissively licensed code (e.g., GPL). And finally there was a question regarding using sample data licensed under CC0 / Public Domain as unit testing/acceptance testing data in one of our projects. In addition, there was a request from the IPMC to absolve it from the requirement of performing/managing IP clearances for projects. Legal has decided that the IPMC is the correct place for these clearances to continue. In the past month, the grace period for removing software using the JSON license from Apache products has expired, and Legal notified PMCs of this expiration. A PMC was found to be rerouting release oriented user data to an external third party site. The ASF Infra Admin and infra stepped in, along with others to rectify this situation by the ASF taking control of the third party site domain, and working with the PMC to make sure everything is happening on ASF servers. Legal has no concerns with this resolution. Legal is proposing the addition of a new member to its committee via resolution. More information on relevant tickets to this report is provided below. * LEGAL-303 RocksDB Integrations * LEGAL-313 Use of CC0: Public Domain License data * LEGAL-310 Handling of IP Clearance for non-incubating projects * Re: JRuby bundling LGPL prior to version 9.1.9.0 ----------------------------------------- Attachment 10: Report from the Apache Security Team Project [Mark J. Cox] Stats for May 2017: 16 CVEs issued to projects (some may not be public yet). e-mails to security@ 7 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to "Apache" mentioned in OSS licenses 7 Direct Vulnerability report to security@apache.org 2 [site] rejected 1 [cordova] 2 [solr] 2 [httpd] (1 rejected) 8 Vulnerabilities reported to projects 6 [openmeetings] 1 [trafficserver] 1 [trafficcontrol] ----------------------------------------- Attachment A: Report from the Apache ACE Project [Marcel Offermans] ## Description: - Apache ACE is a software distribution framework that allows you to centrally manage and distribute modular software components, configuration data and other artifacts to OSGi based and related target systems. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - There has not been much activity in the last four months. ## Health report: - There are still enough PMC members around, but activity is low. ## PMC changes: - Currently 11 PMC members. - No new PMC members added since the last report. - Last PMC addition was Bram de Kruijff on Mon Jul 08 2013 ## Committer base changes: - Currently 12 committers. - No new committers added since the last report. - Last committer addition was Bram Pouwelse at Thu Feb 25 2016 ## Releases: - February 9th, 2016: ACE 2.1.0 release. ## Mailing list activity: - users@ace.apache.org: - 74 subscribers (up 0 in the last 3 months): - 1 emails sent to list (2 in previous quarter) - dev@ace.apache.org: - 70 subscribers (up 0 in the last 3 months): - 0 emails sent to list (7 in previous quarter) ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment B: 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: - Two new contributors: students interested in GSOC made several contributions - Other development has continued to be mostly quiet, but still proceeding with bugfixes mostly ## Health report: As mentioned, development is a bit slower, but was good to see students interested in GSOC. Unfortunately they weren't accepted but it still was a good experience for them & us for the time they were learning about Allura, writing proposals, and making some contributions. We should make our next release soon. ## 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: - Last release was 1.6.0 on Tue Dec 13 2016 ----------------------------------------- Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (Any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity has been pretty stable. We are pretty quiet mailing list-wise. ## Health report: We recently extended an invitation to a new prospective PMC and Committer with the invite being rejected (by the contributor) at this point in time. Otherwise, there is not a great deal to report on for the period. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was William L. Anderson on Sun Aug 28 2016 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Bill Anderson at Tue Aug 30 2016 ## Releases: - Last release was 2.0 on Thu Feb 16 2017 ## Mailing list activity: It is positive to see the user@ emails up from last quarter. dev@ remains our most popular list with mostly JIRA messages. - dev@any23.apache.org: - 34 subscribers (down -1 in the last 3 months): - 108 emails sent to list (151 in previous quarter) - user@any23.apache.org: - 51 subscribers (up 0 in the last 3 months): - 13 emails sent to list (6 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 D: 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: Low. We worked on security reports. And cut a new release with security fixes ## Health report: We have enough PMC to cut release. ## PMC changes: - Currently 9 PMC members. - Martin Stockhammer was added to the PMC 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: - 2.2.3 was released on Tue May 16 2017 ## Mailing list activity: - users@archiva.apache.org: - 232 subscribers (down -1 in the last 3 months): - 11 emails sent to list (6 in previous quarter) - dev@archiva.apache.org: - 106 subscribers (down -1 in the last 3 months): - 56 emails sent to list (17 in previous quarter) - issues@archiva.apache.org: - 35 subscribers (up 0 in the last 3 months): - 153 emails sent to list (4 in previous quarter) - notifications@archiva.apache.org: - 14 subscribers (up 0 in the last 3 months): - 112 emails sent to list (2 in previous quarter) ## JIRA activity: - 19 JIRA tickets created in the last 3 months - 14 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: 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 been discussing different architecture updates to allow for dynamic reservations, rolling restarts, and performance updates to our storage engine while making progress on our 0.18.0 release candidate. Our newest committer, Santhosh Shanmugham, has been shepherding the release candidate through the process. 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: 30 * Resolved: 24 Mailing list activity since last report: * @dev 57 messages * @user 8 messages * @reviews 646 messages Releases --- Last release: Apache Aurora 0.17.0 released 02.06.2017 Vote is currently in progress for Apache Aurora 0.18.0-RC0 ----------------------------------------- Attachment F: Report from the Apache Axis Project [Deepal Jayasinghe] ----------------------------------------- Attachment G: Report from the Apache Bahir Project [Luciano Resende] ----------------------------------------- Attachment H: 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: We have achieved a major milestone for the project -- the completion of the first stable release, version 2.0.0. It signifies 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. Additionally, version 2.0.0 improves user experience across the project, focusing on seamless portability across execution environments, including engines, operating systems, on-premise clusters, cloud providers, and data storage systems. Beam continues to interconnect additional execution engines and data storage/messaging systems, and serves as a glue in the ecosystem. On the execution side, the work continues on the Apache Gearpump (incubating) runner, and a new effort on the JStorm runner has started. On the IO connector side, connectors for Apache Cassandra and Apache Hive’s HCatalog have been contributed, and additional connectors for Redis, Apache DistributedLog (incubating), Apache Solr, Apache Parquet, RabbitMQ, and Advanced Message Queuing Protocol (AMQP) are in progress. Finally, we have started a major effort to create a SQL extension, based on Apache Calcite. We have published a press release and a blog post regarding the first stable release: - https://blogs.apache.org/foundation/entry/the-apache-software-foundation- announces12 - https://beam.apache.org/blog/2017/05/17/beam-first-stable-release.html We have also refreshed the design of our website. Beam was covered at seven major industry conferences over the past quarter, including the "Apache: Big Data" conference in Miami, FL, where we have had 4 talks, a birds-of-a-feather session and a social event. Additionally, we organized the first meetup in the Bay Area, hosted by Hortonworks and Future of Data. 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 Python SDK to all Beam runners. ## Health report: The community continues to grow steadily, as follows: - The number of contributors continues to increase. We are now at 179 unique code contributors, with 76 individuals contributing to the latest release alone (which spanned less than 2 months). - Releases continue at a regular pace of 1-2 months per release. - The activity on the user@ mailing list more than doubled. ## PMC changes: Currently 14 PMC members. No new PMC members have been added since graduation six months ago. We are watching for potential new PMC members. ## Committer base changes: Currently 24 committers. Four new committers have been added since the last report: - Aviem Zur was added as a committer on Fri Mar 17 2017. - Chamikara Jayalath was added as a committer on Fri Mar 17 2017. - Ismaël Mejía was added as a committer on Fri Mar 17 2017. - Eugene Kirpichov was added as a committer on Fri Mar 17 2017. ## Releases: Since the last report, Apache Beam has published two releases: - 0.6.0 was released on Mon Mar 13 2017. - 2.0.0 was released on Mon May 15 2017. Version 2.0.0 is 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 activity continues to increase across all metrics, with the number of user@ emails more than doubling compared to the previous quarter. - dev@beam.apache.org - 424 subscribers (up 63 in the last 3 months). - 1162 emails sent to list (1094 in previous quarter). - user@beam.apache.org - 384 subscribers (up 73 in the last 3 months). - 547 emails sent to list (250 in previous quarter). ## JIRA activity: JIRA activity continues to increase across all metrics, with the number of resolved issues nearly doubling. - 725 JIRA tickets created in the last 3 months (542 in the previous quarter). - 650 JIRA tickets closed/resolved in the last 3 months (347 in the previous quarter). ----------------------------------------- Attachment I: 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: PMC spots that a company[1] is using name/trademark similar to Bigtop. We'll get this to Apache legal team to find out our next move. ## Activity: The community has released 1.2.0 on April 4th, 2017. The community is working on 1.2.1 release expected to be out at the end of June, which will mainly be a bug fixing release with minor upgrades for certain components. Folks had a meetup during DataWorks Summit San Jose 2017, laying down details of what need to be included in 1.2.1 release and what's our future directions. We'll bring that back on mailing list to reach consensus. There was a talk about Apache Bigtop at Apache: Big Data Miami: Leveraging Docker for Hadoop Build Automation and Big Data Provisioning, Evans Ye ## 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 ----------------------------------------- Attachment J: Report from the Apache Bloodhound Project [Gary Martin] ----------------------------------------- Attachment K: Report from the Apache BVal Project [Matt Benson] ## Apache BVal Report June 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: - We have begun work on the necessary changes to implement the forthcoming 2.0 version of the Java Bean Validation specification. We should have quite heightened activity over the next cycle or two while this work proceeds. ## Health report: - BVal continues to be maintained by obligation; this remains tenable. ## 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. - Last committer addition was Romain Manni-Bucau on Sun Jun 23 2013 ## Releases: - Last release was 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment L: Report from the Apache Camel Project [Christian Mueller] ----------------------------------------- Attachment M: Report from the Apache CarbonData Project [Liang Chen] ## Description: - The Apache CarbonData is an indexed columnar store file format for fast analytics on Big Data platforms (including Apache Hadoop, Apache Spark, among others) to help speed up queries an order of magnitude faster over petabytes of data, with the aim of using a unified file format to satisfy all kinds of data analysis cases. ## Board comment in the last month report: - For future reports, please include the date of the last PMC addition (as well as the last committer addition) Re: this month report already added these information. ## Issues: - There are no new issues requiring board attention at this time. ## Activity: - we finished 1st release as top level project, the apache carbondata 1.1.0 is a milestone release with V3 format to improve 50% performance for aggregation cases. - Liang Chen gave a talk to introduce Apache CarbonData during ApacheCon in Miami. - Jackylk present "CarbonData with SparkSQL" practices at China Spark summit on 2017-05-19. - We are prepare apache carbondata 1.1.1 and apache carbondata 1.2.0 - An important work is in progress of providing index framework for users to extend more index, for example : integrate with Apache Lucene for search data. ## Health Report: - The project is healthy, community keep active in all the various categories(dev mailing list, JIRAs, and pull requests). ## Releases: - Apache CarbonData 1.1.0 released on 2017-05-16 ## PMC changes: - Currently 9 PMC members. ## Committer base changes: Currently 13 committers, two new committers added in the past quarter: - hexiaoqiao was added as a committer on 2017-02-21. - qiangcai was added as a committer on 2017-05-09. ## Mailing list activity: dev@carbondata.apache.org: - 152 subscribers (up 34 in the last 3 months). - 862 emails sent in the past 3 months, 758 in the previous cycle issues@carbondata.apache.org: - 7 subscribers (up 1 in the last 3 months). - 4951 emails sent in the past 3 months, 4266 in the previous cycle user@carbondata.apache.org: - 35 subscribers (up 29 in the last 3 months) (27 emails sent in the past 3 months, 0 in the previous cycle) ## JIRA activity: - 393 JIRA tickets created in the last 3 months - 266 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache Cayenne Project [Michael Gentry] ## 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 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) - Current development efforts are geared toward the 4.0 release. Artifacts for our first beta (4.0.B1) were just produced and approved for release, which is a significant milestone for the project. - 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. We just released 4.0 Beta 1 which should be a feature/API freeze for the 4.0 release. We are starting to discuss what finishing touches (documentation, etc) need to be finished and what features to target after this release. We have a stable user and developer community. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months. - Last PMC addition was Savva Kolbachev on Tue Apr 12 2016. ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months. - Last committer addition was Nikita Timofeev at Fri Dec 23 2016. ## Releases: - Cayenne 4.0.B1 on Mon Jun 12 2017. - Cayenne 4.0.M5 on Mon Mar 6 2017. ## Mailing list activity: - dev@cayenne.apache.org: - 127 subscribers (down -1 in the last 3 months). - 104 emails sent to list (164 in previous quarter). - user@cayenne.apache.org: - 252 subscribers (up 3 in the last 3 months). - 151 emails sent to list (208 in previous quarter). ## JIRA activity: - 65 JIRA tickets created in the last 3 months. - 86 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment O: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: - There are no issues requiring board attention at this time. ## Activity: - OpenCMIS 1.1.0 (Java) and PortCMIS 0.2 (C#) have been released. - cmislib (Python) and ObjectiveCMIS (Objective-C) received bug fixes and enhancements. ## Health report: - The CMIS Technical Committee at OASIS has been closed. There will be no further CMIS specification version, errata, or official extension. This will affect Apache Chemistry in the long run. - Our last two releases got both 5+1 votes, but not from exactly the same group of people. Out of the 35 PMC members, there are probably 10 members left that watch the project and vote for releases. Due to the different subprojects and programming languages, not everyone is interested in every release. ## 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 ## 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: - OpenCMIS 1.1.0 was released on Wed Apr 05 2017 - PortCMIS 0.2 was released on Fri Mar 17 2017 ## Mailing list activity: - dev@chemistry.apache.org: - 172 subscribers (down -6 in the last 3 months): - 176 emails sent to list (98 in previous quarter) ## JIRA activity: - 19 JIRA tickets created in the last 3 months - 52 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment P: 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: - CloudStack is now using Apache Gitbox to host the Git repositories on Github. Committers seem very happy with easier merging of PRs and the ability to add milestones and labels to PRs ## Health report: - Release 4.10 is currently in RC5 which has one blocker. Project is working hard on releasing 4.10 since there are a lot of open PRs for 4.11 which are waiting to be merged. - Apache Con / CloudStack Conference took place in Miami in May and was a succes. Lot's of committers showed up and participated in discussions and presented talks ## PMC changes: - Currently 46 PMC members. - New PMC members: - Rene Moser was added to the PMC on Mon Mar 27 2017 - Wei Zhou was added to the PMC 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: - Last release was 4.9.2.0 on Thu Jan 05 2017 - Last release was 4.8.1 on Mon Aug 15 2016 ## Mailing list activity: - TODO Please explain what the following statistics mean for the project. If there is nothing significant in the figures, omit this section. - users@cloudstack.apache.org: - 1112 subscribers (down -3 in the last 3 months): - 482 emails sent to list (523 in previous quarter) - dev@cloudstack.apache.org: - 740 subscribers (down -1 in the last 3 months): - 2094 emails sent to list (4186 in previous quarter) - announce@cloudstack.apache.org: - 500 subscribers (up 10 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@cloudstack.apache.org: - 234 subscribers (up 1 in the last 3 months): - 1800 emails sent to list (4038 in previous quarter) - marketing@cloudstack.apache.org: - 235 subscribers (down -2 in the last 3 months): - 10 emails sent to list (51 in previous quarter) - press@cloudstack.apache.org: - 13 subscribers (up 0 in the last 3 months) ## JIRA activity: - 125 JIRA tickets created in the last 3 months - 102 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: 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 on April 4, 2016. ## Issues: - There are no issues that requires the board's attention this quarter. ## Activity: - The project is active with four (4) releases this reporting period. - We are working on a new component: Apache Commons Numbers, providing implementations of extended number types such as complex, quaternion, and fraction. - We migrated Commons CLI, Commons FileUpload, and Commons Imaging from Subversion to Git. - We are starting to add testing with IBM Java 8 to Travis-CI builds. ## 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 no new PMC member, and Commons is still open to any Apache Committer. - Some of the energy spent toward Commons Math 4 is being redirected on building a new component out of Commons Math: Apache Commons Number. ## PMC changes: - Currently 36 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bruno P. Kinoshita on Wed Oct 26 2016 ## Committer base changes: - Currently 144 committers. - No new committers added in the last 3 months - Last committer addition was Bernd Porr at Tue Jan 31 2017 ## Releases: - Apache Commons Compress 1.14 was released on Sat May 13 2017 - Apache Commons FileUpload 1.3.3 was released on Tue June 13 2017 - Apache Commons JEXL 3.1 was released on Thu Apr 13 2017 - Apache Commons Lang 3.6 was released on Wed Jun 07 2017 - Apache Commons Text 1.1 was released on Mon May 22 2017 ## JIRA activity: - 199 JIRA tickets created in the last 3 months - 179 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: 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: There was one overall plugin release this quarter. An overall plugin release usually consists of all, if not most, of our 23 plugins. This number was one less than last quarter. We had two platform releases - one minor plus three patch releases for Android (6.2.0, 6.2.1, 6.2.2, 6.2.3) and one minor release for iOS (4.4.0). Android releases were to fix two consecutive major breaks in Android tools releases (deprecation of certain Android SDK tools). The minor iOS release was to support Carthage, breakage while using Xcode 8.3.2, and also dynamic frameworks. We had a major tools release of the CLI version 7.0.0 with support for custom platforms, increased package.json support, and dropping of support for older platform versions. We had a new plugin release - cordova-plugin-screen-orientation 2.0.0, as well as a new developer tool release, cordova-coho 1.0.0. ## Health report: Our status dashboard at http://status.cordova.io is mostly all green. Travis CI pull request times have been vastly improved versus last quarter due to INFRA enabling certain beta changes for Travis. Previously pull requests may have taken 24 hours but now it happens within 15 minutes. Our plugin device testing has been put on hold since a major contributor has decided to not support the server we have been testing on, resulting in a lot of "broken" build status badges on the status page. To resolve this, we are moving the testing to AppVeyor and Travis CI, and have filed an INFRA issue for help: https://issues.apache.org/jira/browse/INFRA-14273 We still have a huge backlog of Github Pull Request activity, again, same as last quarter -- but it has improved. We would have liked to have direct access to Github to manage these issues better and we have requested Gitbox access but there hasn't been a response so far: https://issues.apache.org/jira/browse/INFRA-14347 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. ## PMC changes: - Currently 86 PMC members. - Matrosov Nikita was added to the PMC on Wed Jun 14 2017 ## Committer base changes: - Currently 89 committers. - Matrosov Nikita was added as a committer on Tue Jun 13 2017 ## Releases: - cordova-android@6.2.0 was released on Thu Mar 30 2017 - cordova-android@6.2.1 was released on Tue Apr 04 2017 - cordova-android@6.2.2 was released on Thu Apr 27 2017 - cordova-android@6.2.3 was released on Thu May 04 2017 - cordova-app-hello-world@3.12.0 was released on Wed May 03 2017 - cordova-coho@1.0.0 was released on Sat May 13 2017 - cordova-common@2.0.2 was released on Sun Apr 16 2017 - cordova-common@2.0.3 was released on Wed May 03 2017 - cordova-create@1.1.0 was released on Wed May 03 2017 - cordova-create@1.1.1 was released on Thu May 11 2017 - cordova-fetch@1.1.0 was released on Wed May 03 2017 - cordova-ios@4.4.0 was released on Fri Apr 21 2017 - cordova-lib@7.0.0 was released on Wed May 03 2017 - cordova-lib@7.0.1 was released on Thu May 11 2017 - cordova-plugin-battery-status@1.2.4 was released on Sun Apr 30 2017 - cordova-plugin-camera@2.4.1 was released on Sun Apr 30 2017 - cordova-plugin-console@1.0.7 was released on Sun Apr 30 2017 - cordova-plugin-contacts@2.3.1 was released on Sun Apr 30 2017 - cordova-plugin-device-motion@1.2.5 was released on Sun Apr 30 2017 - cordova-plugin-device-orientation@1.0.7 was released on Sun Apr 30 2017 - cordova-plugin-device@1.1.6 was released on Sun Apr 30 2017 - cordova-plugin-dialogs@1.3.3 was released on Sun Apr 30 2017 - cordova-plugin-file-transfer@1.6.3 was released on Sun Apr 30 2017 - cordova-plugin-file@4.3.3 was released on Sun Apr 30 2017 - cordova-plugin-geolocation@2.4.3 was released on Sun Apr 30 2017 - cordova-plugin-globalization@1.0.7 was released on Sun Apr 30 2017 - cordova-plugin-inappbrowser@1.7.1 was released on Sun Apr 30 2017 - cordova-plugin-media-capture@1.4.3 was released on Sun Apr 30 2017 - cordova-plugin-media@3.0.1 was released on Sun Apr 30 2017 - cordova-plugin-network-information@1.3.3 was released on Sun Apr 30 2017 - cordova-plugin-screen-orientation@2.0.0 was released on Mon Mar 20 2017 - cordova-plugin-screen-orientation@2.0.1 was released on Sun Apr 30 2017 - cordova-plugin-splashscreen@4.0.3 was released on Sun Apr 30 2017 - cordova-plugin-statusbar@2.2.3 was released on Sun Apr 30 2017 - cordova-plugin-vibration@2.1.5 was released on Sun Apr 30 2017 - cordova-plugin-wkwebview-engine@1.1.3 was released on Sun Apr 30 2017 - cordova-plugman@1.5.0 was released on Wed May 03 2017 - cordova@7.0.0 was released on Wed May 03 2017 - cordova@7.0.1 was released on Thu May 11 2017 ## JIRA activity: - 342 JIRA tickets created in the last 3 months - 295 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment S: 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 released a major release 4.0.0 recently in April 2017. - Committee continues to work on the future release (4.0.1). - Committee is actively working on updating the cTAKES Confluence website for improved documentation ## Health report: - The community continues to be moderately active. There are a fair number of new users/questions interest in the dev and user mailing lists. ## 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 users mailing list(s) over the last quarter with the recent 4.0.0 release. - dev@ctakes.apache.org: - 221 subscribers (up 2 in the last 3 months): - 289 emails sent to list (280 in previous quarter) - user@ctakes.apache.org: - 211 subscribers (up 8 in the last 3 months): - 77 emails sent to list (23 in previous quarter) ## JIRA activity: - 26 JIRA tickets created in the last 3 months - 42 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: - Apache Curator is a Java/JVM client library for Apache ZooKeeper, a distributed coordination service. It includes a highlevel API framework and utilities to make using Apache ZooKeeper much easier and more reliable. It also includes recipes for common use cases and extensions such as service discovery and a Java 8 asynchronous DSL. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We added a new committer, Fangmin Lv - Development and user activity continues ## Health report: - Apache Curator is very healthy - Adding a new committer was a long term goal now accomplished - we could probably use 1 or 2 more ## PMC changes: - Currently 12 PMC members. - Fangmin Lv was added to the PMC on Tue Mar 28 2017 ## Committer base changes: - Currently 12 committers. - Fangmin Lv was added as a committer on Wed Mar 29 2017 ## Releases: - Apache Curator 2.12.0 was released on Mon Mar 06 2017 - Apache Curator 3.3.0 was released on Mon Mar 06 2017 ## Mailing list activity: - dev@curator.apache.org: - 55 subscribers (down -1 in the last 3 months): - 682 emails sent to list (499 in previous quarter) - user@curator.apache.org: - 159 subscribers (up 3 in the last 3 months): - 40 emails sent to list (59 in previous quarter) ## JIRA activity: - 28 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Eagle Project [Edward Zhang] ----------------------------------------- Attachment V: Report from the Apache Falcon Project [Srikanth Sundarrajan] 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 has been QA certified and is ready for release. Release should happen this month. 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: - 115 subscribers (up 1 in the last 3 months): - 210 emails sent to list (558 in previous quarter) JIRA ACTIVITY: - 6 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment W: 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 Framework 5.6.4 and Resolver 1.14.0 released (May 24th, 2017) Apache Felix Web Console 4.3.4 (May 12th, 2017) Apache Felix Web Console 4.3.2, Apache Felix WebConsole OBR Plugin 1.0.4 (May 9th, 2017) Apache Felix Utils 1.10.0, Apache Felix FileInstall 3.6.0 (May 9th, 2017) Apache Felix Gogo Runtime 1.0.6, Apache Felix Gogo JLine 1.0.6 (May 9th, 2017) Apache Felix SCR 2.0.8 (April 28th, 2017) Apache Felix Maven Bundle Plugin 3.3.0 (March 13th, 2017) ----------------------------------------- Attachment X: Report from the Apache Fineract Project [Myrle Krantz] ## Description: - Apache Fineract (\’fīn-,ә-,rakt\) is an open source system for core banking as a platform. Fineract provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world’s 2 billion underbanked and unbanked. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Released version 1.0.0. - Mentoring GSOC interns ## Health report: - The project remains healthy. Activity levels on mailing lists, git and JIRA remain mostly constant. Release voting was a little slow. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jim Jagielski on November 3rd, 2016. ## Committer base changes: - Currently 14 committers. - No changes (the PMC was established in the last 3 months) - Last committer additions were Zayyad Said and Robert Ippez on March 13th, 2017. ## Releases: - Released version 1.0.0 https://dist.apache.org/repos/dist/release/fineract/1.0.0/ on June 1. ## Mailing list activity: Requests for help on the user list continue to be answered in a prompt and friendly manner. - dev@fineract.apache.org: - 144 subscribers (up 21 in the last 3 months): - 938 emails sent to list (1138 in previous quarter) - issues@fineract.apache.org: - 8 subscribers (up 0 in the last 3 months): - 212 emails sent to list (180 in previous quarter) - user@fineract.apache.org: - 123 subscribers (up 19 in the last 3 months): - 39 emails sent to list (102 in previous quarter) ## JIRA activity: Tickets created and tickets closed are holding parity. - 60 JIRA tickets created in the last 3 months - 59 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Y: 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 Flex SDK 4.16.0 was released on 3/10/17. -Apache Flex BlazeDS 4.7.3 was released on 3/31/17. -Preparing to vote on Apache FlexJS 0.8.0. -Apache FlexJS 0.7.0 was released on 9/7/16. -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 Flex SDK 4.16.0 and Apache Flex BlazeDS 4.7.3, the latter addressing CVE-2017-5641. Apache Flex SDK 4.16.0 contained a fix for FLEX-35123, an XSS issue reported in prior board reports. It is only exploitable in really old versions of Safari. We did not get a CVE for it. Maybe we should? It seems almost more academic than actual. Christofer Dutz organized the FlexJS Summit at ApacheCon. Several committers met for the first time and reportedly had a great time. A list of priorities for FlexJS and other products we release also came out of the summit. An attempt was made to get the Apache FlexJS 0.8.0 release out by the end of April in order to meet the org.json deadline, but many major bugs were found after feature freeze started on April 21 (known as "Last Call" on our dev@ list). We next tried to get the release out for ApacheCon, but as of May 31 we are still fixing bugs. There is something inefficient about the release process for Apache Flex releases. As the release manager for Apache FlexJS 0.8.0, it doesn't feel like the community focuses on trying to get the release out, but rather, reasons to put off the release. The Apache Flex SDK 4.16.0 only had 3 voters. And after it went out, we found out that the installer didn't work in some common scenarios. We are unable to reach quality in a timely manner. There have been no new volunteers to be Release Manager for several years now. Being RM is one of the things I dread doing. As I (Alex Harui, PMC Chair) file this report, we still won't have a release out since a couple of PMC members did not bother to examine the artifacts during "Last Call", waited for the RC to be posted, and now want major restructuring of the release artifacts. Mailing list activity on dev@ dropped by 30% around the end of March and remains down. Commit activity from folks who were active in the prior quarter is down as well. I am hopeful that this is because one committer ran out of time to contribute recently and the others finished most of the work on the libraries they were working on and are now building apps for their employers on top of those libraries. COMMUNITY -Last committer as added on 9/5/16. A discussion has started about a new candidate. -Yishay Weiss was added to the PMC on 1/20/17. -Latest analytics include a little less than 500 hits per day on the Website during the work week (less on weekends). It used to be closer to 1000 hits per day. -There were more than 2700 installs Apache Flex 4.16.0 since its release in March 2017. -More than 130,000 people have run the Tour De Flex application. Tour De Flex is a set of examples folks use to learn how to develop Flex applications. 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? -Trademarks@ notified us that a company in Europe is applying to register the word FLEX for a software product that runs gas stations, but still might cause confusion. The recommendation from trademarks@ and consensus from the Flex PMC is to have Apache counsel write them a nice letter asking them to limit the scope of their application to their industry. ----------------------------------------- Attachment Z: 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 - Flink is in a healthy phase of growing the committer base to handle the increased activity in various components. Since the beginning of the year, eight new committers were added. - The first time-based release happened with 1.3.0, and the feedback from users and committers was positive. - The discussion about modularization and possible changes to the build and testing setups continues, to address the very long build/test times. No conclusion has been reached so far. A significant build-time reduction would require big changes to the build setups (like organizing Flink into various sub-repositories) and there are concerns about the added complexity for users and contributors that such a setup brings. - There will be another instance of the Flink Forward conference in Berlin in September this year: http://berlin.flink-forward.org The program committee consists of a mix of Flink community members and stream processing experts from other stream and event-processing communities. The call for participation is currently happening. - The Flink Forward San Francisco conference happened in April, with Apache Flink training, user talks, committer talks, and a "how to participate in the community" tutorial. In addition, there were presentations about Flink at Apache Con, Kafka Summit, Dataworks Summit, Strata, Mesos Con, J on the Beach, and several other conferences. - Voting on bugfix release 1.3.1 is in progress at the time of writing this report. COMMUNITY PMC members added since last report: - Greg Hogan was added as a PMC member on March 13th, 2017. Committers added since the last board report: - Theodore Vasiloudis was added as a committer on March 21st, 2017 - Xiaogang Shi was added as a committer on May 21st, 2017 - Dawid Wysakowicz was added as a committer on June 14th, 2017 - Shaoxuan Wang was voted in as a committer on June 15th, 2017 Flink currently has 32 committers and 17 PMC members. RELEASES The following releases were made since the last board report: - 1.1.5 was released on March, 22nd, 2017 - 1.2.1 was released on April 25th, 2017 - 1.3.0 was released on May 31st, 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 (824 JIRA tickets created, 622 JIRA tickets over last 3 months) ----------------------------------------- Attachment AA: Report from the Apache Giraph Project [Avery Ching] ----------------------------------------- Attachment AB: 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 == No changes compared to the last quarter, the service is 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 AC: Report from the Apache Hama Project [Edward J. Yoon] ----------------------------------------- Attachment AD: Report from the Apache Helix Project [Kishore Gopalakrishna] ----------------------------------------- Attachment AE: 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: - Sustained discussion with Apache Spark PMC on issues concerning compatibility claims, trademark and published maven artifacts with potential to cause confusion. - Consensus has been reached on compatibility claimed between Spark sql and Hive with Spark PMC agreeing to remove some language from their website. - Consensus has been reached that there is no trademark issue. - Consensus has been reached that published maven artifacts will be removed once proper jars are available from Hive project. That is pending on some technical issues which needs to be resolved. ## Activity: - Community is working on 2.2 and 2.3 releases. - PMC requested a vendor to clarify documentation on their website w.r.t configurations supported in their distribution. Vendor complied and made edits as requested. ## PMC changes: - Currently 40 PMC members. - New PMC members: - Aihua Xu was added to the PMC on Wed May 24 2017 - Chaoyu Tang was added to the PMC on Wed May 24 2017 - Daniel Dai was added to the PMC on Wed May 24 2017 - Jimmy Xiang was added to the PMC on Wed May 24 2017 - Rui Li was added to the PMC on Wed May 24 2017 - Sergio Pena was added to the PMC on Wed May 24 2017 - Vaibhav Gumashta was added to the PMC on Wed May 24 2017 - Yongzhi Chen was added to the PMC on Wed May 24 2017 ## Committer base changes: - Currently 64 committers. - Vineet Garg was added as a committer on Mon May 08 2017 ## Releases: - 1.2.2 was released on Thu Apr 06 2017 - hive-storage-2.3.0 was released on Tue May 02 2017 - hive-storage-2.3.1 was released on Mon May 29 2017 ## Mailing list activity: - dev@hive.apache.org: - 864 subscribers (down -1 in the last 3 months) - user@hive.apache.org: - 2218 subscribers (up 2 in the last 3 months) ## JIRA activity: - 662 JIRA tickets created in the last 3 months - 499 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AF: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for June 2017 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. At the end of May, there were 60 podlings incubating. Podlings executed six releases this month. The incubator brought in one new podling, and the board has motions to graduate three podlings from the incubator. One IPMC member stepped down while two new IPMC members joined. Many reports below were signed off by a single mentor. The Incubator PMC shall begin to plan for a way to address this. * Community New IPMC members: - Bikas Saha - Bob Paulin People who left the IPMC: - Par Niclas Hedhman * New Podlings - Superset * Podlings that failed to report, expected next month - HORN - No on list discussions recently. - MRQL - No on list discussion in past 3 months, limited discussions prior to that. - Myriad - Discussing retirement - Sirona - Likely to be retired or moved as a sub-project by next report * Graduations The board has motions for the following: - Atlas - MADlib - Mynewt * Releases The following releases entered distribution during the month of May: - 2017-05-01 Apache Trafodion 2.1.0 - 2017-05-04 Apache Mnemonic 0.7.0-incubating - 2017-05-09 Apache Airflow 1.8.1 - 2017-05-09 Apache MADlib 1.11 - 2017-05-17 Apache Ratis 0.1.0-alpha - 2017-05-30 Apache Tephra 0.12.0 * Infrastructure - The Incubator has begun to migrate podling maintenance into Whimsy * Miscellaneous - The IPMC has elected a new chair, hopefully accepted at this month's board meeting. ---------------------------------------------------------------------- Table of Contents AriaTosca Atlas Gearpump Gobblin Griffin Hivemall HTrace iota Joshua Mnemonic Omid OpenWhisk Pony Mail Quickstep SAMOA Singa Slider Spot Streams Superset Tamaya Taverna Tephra Toree 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. Have frequent Release cycles to be compliant with the Apache Way. 3. Move the website to apache.org Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The project is ready for its first release as far as the code is concerned; We're working on updating the README and ensuring compatibility with ASF's regulations regarding creating releases. On the latter issue, we've come across a few possible problems, that are being discussed on the project's mailing list. For more information, see the threads "ARIA dependencies License issues" and "A few questions about creating a release" on the mailing list archive. How has the community developed since the last report? * All project communication takes now place on either the mailing list or ASF's Slack, and is open for everybody. * Increased chatter on the mailing list including new subscribers who ask questions, make suggestions and are likely to become contributors themselves in the near future. How has the project developed since the last report? 1. ARIA now has a CLI, making it usable as a stand alone tool as well as a library. 2. Usage examples have been added 3. End-to-End tests now run on a daily basis (as well as on CIs for every commit) 4. 93 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. [X] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: No release yet. 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 continues to struggle in adopting the Apache Way. It's clear most of them want to do it, but need to work on getting focused to make it happen. [ ](ariatosca) Jakob Homan Comments: -------------------- Atlas 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 Atlas has been incubating since 2015-05-05. Three most important issues to address in the move towards graduation: We do not see any issues in moving towards graduation. The dev community feel that we are ready for graduation as discussed in this mail thread: https://s.apache.org/94xI. We have intimated the IPMC about this and are working towards answering some queries raised in the Incubator mailing list regarding the same. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None that we are aware of. How has the community developed since the last report? * Madhan Neethiraj was voted in to the Apache Atlas PPMC. * The following new committers were added: * Ayub Khan Pathan * Apoorv Naik * Kalyani Kashikar * Neeru Gupta * Nixon Rodriguez * Sarath Subramanian * Following contributors have been added to JIRA. * Jan Hentschel * Qinglin Xia * Laxmikanth Malladi * Shi Wang * Christopher Grote * Graham Wallis How has the project developed since the last report? * Apache Atlas community released version 0.8 of the software on March 31 2017. [1] * Several new features are in progress or have finished development including enhanced metadata and governance capabilities through typesystem improvements (modeling relationships, glossary), a Virtual Data Connector project, improvements to search capabilities, Export/Import of Atlas graph metadata etc. * 239 new issues were filed between March 1st 2017 and May 29th [2]. 189 issues were resolved in the same time [3] 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-03-31 When were the last committers or PPMC members elected? * PPMC Members - Madhan Neetiraj (March 5 2017) * Committer - Ayub Pathan (March 20 2017) [1] https://lists.apache.org/thread.html/739d520597ea0bf93e9b5649044bc6a92c4660bbc 44ffdd94f5bcb21@%3Cdev.atlas.apache.org%3E [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20creat ed%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29 [3] https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20resol utiondate%20%3E%3D%202017-03-01%20AND%20resolutiondate%20%3C%3D%202017-05-29%2 0ORDER%20BY%20resolutiondate%2C%20createdDate%20DESC Signed-off-by: [ ](atlas) Arun Murthy Comments: [X](atlas) Chris Douglas Comments: [ ](atlas) Jakob Homan Comments: [ ](atlas) Vinod Kumar Vavilapalli Comments: -------------------- 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? - Increased community contribution on rabbitmq connector and state management. How has the project developed since the last report? - 27 issues created and 24 issues resolved. - Continued integration within Apache Beam (Gearpump Runner). - Joined in GSoC 2017 project. 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-04-19 When were the last committers or PPMC members elected? No new committers or PMC members elected yet. Signed-off-by: [X](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. Few first steps has been made: * mailing list setup * jira setup * few Apache account creation for new committers. Three most important issues to address in the move towards graduation: 1. Code import. Still need agreement from LinkedIn/Microsoft 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 very first steps of the project How has the project developed since the last report? Not much. We are waiting code donation before start building the community. 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](gobblin) Olivier Lamy Comments: [ ](gobblin) Jean-Baptiste Onofre Comments: [X](gobblin) Jim Jagielski Comments: -------------------- Griffin Griffin is an 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. Make the first release. 2. Enhance data quality algorithms to let contributors to expand artifacts to meet more data quality dimensions. 3. Onboard more use cases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 1.We were invited to Database Technology conference China 2017( http://dtcc.it168.com/yicheng.html ) to introduce Apache Griffin in May, lots of open source audience would like to try Apache Griffin as their data quality solution. 2.We were invited to Opensource Innovation Meetup( https://www.oschina.net/news/84136/2017-5-yue-yuanchuanghui ) to introduce Apache Griffin in May, some of them will contribute to our development. 3.Discussed with Angular expert damoqiongqiu (https://github.com/damoqiongqiu) for UI enhance. How has the project developed since the last report? - Active development started in the community. 38 commits since last report. - Core services are done, users can go through our data quality process easily. - Setup online demo on AWS.[will attach here soon] How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Signed-off-by: [ ](griffin) Kasper Sørensen Comments: [X](griffin) Uma Maheswara Rao Gangumalla Comments: [ ](griffin) Luciano Resende Comments: -------------------- 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? * We invited Takuya KItazawa to PPMC on April 24th but his is not yet getting an invitation from IPMC. Could you take a look? Vote thread is at: msgid: CAGJoAUnmnsDBVHD+V_ix3gGzKTjNNwco8szxJ71rmU0cCbAjbg@mail.gmail.com How has the community developed since the last report? * We invited a PPMC member (Takuya Kitazawa) * Had a presentation at Apache BigData, Miami https://goo.gl/7JZ59O http://events.linuxfoundation.org/sites/events/files/slides/apachebigdata20 17.pdf (slide) * Had a BoF session at Apache BigData, Miami * Github watchers/stars are gradually increasing: 79 stars as of May 31 (was 52 on Feb 28) * Twitter account @ApacheHivemall followers are gradually increasing: 70 followers as of May 31 (was 52 on Feb 28) How has the project developed since the last report? * approaching the first Apache release in Q2 - Blocking issues are decreased https://issues.apache.org/jira/browse/HIVEMALL-21 * 4 committers are active at development https://github.com/apache/incubator-hivemall/pulse/monthly Since the last report (March 2017), we have * Opened 24 JIRA issues and closed 19 JIRA issues as seen in https://goo.gl/88Qr11 Created Resolved March 2017 9 10 April 2017 7 6 May 2017 8 3 * Created 27 Pull Requests https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A 2017-03-01..2017-05-31 * Merged 27 Pull Requests https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2 017-03-01..2017-05-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 Q2, 2017) When were the last committers or PPMC members elected? * Inviting Takuya Kitazawa to PPMC Signed-off-by: [ ](hivemall) Reynold Xin Comments: [ ](hivemall) Markus Weimer Comments: [ ](hivemall) Xiangrui Meng Comments: [x](hivemall) Daniel Dai Comments: You can invite Takuya Kitazawa to PPMC now. -------------------- 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? There are no issues requiring board attention at this time. How has the community developed since the last report? Mailing lists have been quiet. How has the project developed since the last report? We are on track to make an HTrace 4.3 release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2016-10-06 When were the last committers or PPMC members elected? 2016-10-03 Signed-off-by: [x](htrace) Jake Farrell Comments: [ ](htrace) Todd Lipcon Comments: [ ](htrace) Lewis John Mcgibbney Comments: [ ](htrace) Andrew Purtell Comments: [x](htrace) Billie Rinaldi Comments: [x](htrace) Michael Stack Comments: -------------------- iota Open source system that enables the orchestration of IoT devices. iota has been incubating since 2016-01-20. Three most important issues to address in the move towards graduation: 1. An initial release of iota 2. Building a more active community 3. Consistency in the discussions on mailing lists/ steady flow of source code contributions 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? Presentation give at ApacheCon Miami with a focus on developing downloading iota and developing iota performers. Several individuals became interested in using iota and have begun contributing to the iota user and dev threads. How has the project developed since the last report? Two new contributors are proposing the addition of Akka dependency injection into iota to facilitate the integration with the Spring Framework. This coming next month there will be an initial release of iota. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Yes - Barbara Gomes was added as a committer on 12/02/2016 Signed-off-by: [ ](iota) Daniel Gruno Comments: [ ](iota) Sterling Hughes Comments: [X](iota) Justin Mclean Comments: Currently I'm not sure if Apache is the right place for this project as they seem unable to keep discussion on list, develop in the open or make a release. Little has changed since these emails [1][2]. This pull request has been outstanding since February. [3] On the plus side a talk at ApacheCon has generated more interest. 1. https://lists.apache.org/thread.html/5fabdad2f6d32e9248f207010f59b7547 7098dddd43ee2b1ff4510ad@%3Cdev.iota.apache.org%3E 2. https://lists.apache.org/thread.html/f995bc2a9bc4b8df84feff2b979516a60 7e9841319ab68f7209346b0@%3Cdev.iota.apache.org%3E 3. https://github.com/apache/incubator-iota/pull/32 [ ](iota) Hadrian Zbarcea Comments: -------------------- Joshua Joshua is a statistical machine translation toolkit Joshua has been incubating since 2016-02-13. Three most important issues to address in the move towards graduation: 1. Release Apache Joshua incubating 6.1 (rc4) and then begin development on 7.X branch. 2. Identifying specific use cases that we might excel at. 3. Attracting active developers and users. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There is currently an ongoing VOTE thread over on general@incubator regarding the proposed release of Apache Joshua incubating 6.1 (rc4). If this goes through it will be a significant achievement for the podling. How has the community developed since the last report? There are ongoing discussion threads on user@ regarding integration of Joshua with Mailman. There are no new community members. Some members of the Joshua PPMC became Apache members post this years annual meeting. Henry Yandell is now emeritus mentor. How has the project developed since the last report? The community has been iterating on Apache Joshua incubating 6.1 RC's as well as refining the release process. We have pretty much addressed all concerns now so subsequent releases should be easier. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup DONE [X] Working towards first release VERY CLOSE [ ] Community building Joshua was not represented at ApacheCon this year but hopefully we can get involved in future events. [ ] Nearing graduation possibly one or two more releases... possibly of the 7.X branch before we graduate. [ ] Other: Date of last release: N/A When were the last committers or PPMC members elected? - 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC + Committership. - 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership. - 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership. Signed-off-by: [ ](joshua) Paul Ramirez Comments: [X](joshua) Lewis John McGibbney Comments: The community will benefit significantly from a 6.1 release if the current VOTE on general@incubator passes. [ ](joshua) Chris Mattmann Comments: [X](joshua) Tom Barber Comments: There has been a slight bottleneck with committers bandwidth and the ability to ship a release, along with getting other people familiar with the release process and happy to ship new versions. I'm sure this bottleneck will reduce when have iterated through a few more releases to iron out the kinks. -------------------- Mnemonic Apache Mnemonic is an advanced hybrid memory storage oriented library, we've proposed a non-volatile/durable Java object model and durable computing service 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 native-direct computing high performance applications. Mnemonic has been incubating since 2016-03-03. Three most important issues to address in the move towards graduation: 1. Have elected new PPMC and committers 2. Integrated with Apache Spark and released v0.7.0 3. Presented Mnemonic models on ApacheCon 17' Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? Our last report was in Mar. Since then * discussed the gaps from graduation * elected new release manager How has the project developed since the last report? * Added Durable Tree as new durable collection * Added DurableRDD for Apache spark integration * Improved the persistence and transaction APIs for durable objects * and other bugfixes, features, improvements 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-05-04 When were the last committers or PPMC members elected? Debo Dutta (PPMC and Committer 2017-04-19) Johnu George (Committer 2017-04-28) Signed-off-by: [X](mnemonic) Patrick Hunt Comments: [ ](mnemonic) Andrew Purtell Comments: [X](mnemonic) James Taylor Comments: [ ](mnemonic) Henry Saputra Comments: -------------------- 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 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? 2 new contributors Omid presented in the Apache Conf US in comparison to other Apache TMs for HBase. It will be presented also in HBase conf in mid June. Meeting with Apache Tephra contributors How has the project developed since the last report? Several bugs discovered and working on fixes. Continue working on next release. Testing in prod env. Quarter Stats (from: 2017-03-01 to: 2017-05-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 60 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 8 | | Resolved Issues | 2 | | Pull Requests merged | 1 | | 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: In the past I have made comments on the lack of activity on this podling. While activity is still low it has definitely picked up with several JIRAs being filed and fixed and user queries appearing on the mailing list and being answered. It's good to see this pickup in activity. [ ](omid) Lars Hofhansl Comments: [X](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. OpenWhisk has been incubating since 2016-11-23. Three most important issues to address in the move towards graduation: 1. Moving last remaining (project website) github repo. : i.e., https://github.com/openwhisk/openwhisk.github.io under the Apache Github org. i.e. http://openwhisk.incubator.apache.org/ and automatic Jenkins build to compile the static website (using current Jekyll) build and automate publishing to our incubator site. looking at using the “GitPubSub” tool: https://blogs.apache.org/infra/entry/git_based_websites_available 2. Complete updating all source files with approved ASF header (incl. JS) 3. Credentials sharing process for social media sites (e.g., Twitter, YouTube, Medium, etc.) to provide access to PPMC members. Continue working through project incubation checklists on CWIKI Compliance Checklist for OpenWhisk.org website. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - Travis is still taking much longer under the Apache org. within GitHub then it did under the previous openwhisk.org and experiencing build time-outs. Developers are looking to reduce build dependencies to shorten build times by using pre-built Docker images, as well as optimizing CI tests. How has the community developed since the last report? - Successful sessions / Shark Tank / BoF at ApacheCon NA 2017. - OpenWhisk booth presence very active with great interest in architecture. - GitHub project “Stars” = 1511 (up from 1395 last month) with 310 forks. - a couple new contributors in devtools/kube repos. - new ICLA from Vadim Raskin - “dev", “private” email list traffic continues to be healthy; positive discussion of a few new code feature/change topics. - requested/created new “issues” list to provide separate destination for GitHub issues emails / separate from “commits” and allow better “searchability" - Increased traffic on Slack “general” channel. Install/deployment questions - setup/config/local build questions/errors being addressed. - Under our public Slack Team (openwhisk-team.slack.com). - Added a new channel named “kubernetes” for discussion of our new Kubernetes deployment (project/repo.) - Moving all GitHub issue emails to new “issues” list - Exploring forwarding “dev” Slack threads to “dev” email list How has the project developed since the last report? - 29/30 Repositories moved from “openwhisk” to “apache” org. under GitHub successfully. - Addressing Travis (URL) changes repo-by-repo, fixing GitHub event/emails being sent to “dev” lists incorrectly, - Repo. topic/description changes/updates being done as encountered with INFRA. - Created the incubator-openwhisk-deploy-kube repo. to host a brand new deployment (still experimental) to Kubernetes. - Created the incubator-openwhisk-utilities repo. to host cross-project utilities; moved code scanning tool there and working through repos. to reference the tool in Travis. - Confluence WIKI (https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wi ki) adds/udaptes pages for: - Improved new Committer process / instructions - Incubator status site: http://incubator.apache.org/projects/openwhisk.html - updated all sections to be up-to-date as of 2017-05-15. - Active “dev” discussions on: - DockerContainer implementation with a MesosTask - Performance testing (new repo.?) - Potential use of PassportJS as a new “package” for OAuth integration - New features: - Progress on splitting out CLI from main project and making it “pluggable” (i.e., incubator-openwhisk-cli and incubator-openwhisk-client-go) - HA enabling of - improve monitoring (especially of containers) to elasticsearch. Date of last release: - No release yet When were the last committers or PPMC members elected? - Matt Hamann, new committer 2017-05-27 Signed-off-by: [X](openwhisk) Felix Meschberger Comments: Happy to see progress on infrastructure consolidation [ ](openwhisk) Isabel Drost-Fromm Comments: [ ](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. Finding and recognizing new contributors to the project 2. Explore options to better increase visibility and welcomeness of the project 3. Get the next release out Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? The committer list has not changed. We have received some contributions from new people, however, and will evaluate and explore further means of growing the community. How has the project developed since the last report? A new release has been discussed, and should be under way shortly. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2016-08-20 When were the last committers or PPMC members elected? Sebastian Bazley was elected PPMC on 2016-09-10. No new committers since last report. Signed-off-by: [ ](ponymail) Andrew Bayer Comments: [X](ponymail) John D. Ament 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. Give talks on the technology. 2. Work on adoption of the Quickstep technology by getting committers outside the current group. 3. Write more blog posts, papers, demos on the technology. 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 have a new committer, Tianrun Li. How has the project developed since the last report? We have made a first release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-03-27 When were the last committers or PPMC members elected? May 2017 Signed-off-by: [ ](quickstep) Konstantin Boudnik Comments: [x](quickstep) Julian Hyde Comments: Getting the first release out this quarter was a big milestone for the project. Their next challenge is to build a community outside of Madison. They are giving papers and talks at academic conferences but I have been encouraging them to find ways to connect with industry and the open source community. [x](quickstep) Roman Shaposhnik Comments: what Julian said ;-) -------------------- 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 Flink, Apache Storm, Apache Apex and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Grow the developer base 2. Grow the user base 3. Add some more ML techniques 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 (March 2017 - May 2017): * @dev: 38 messages Jira issues backlog (March 2017 - May 2017): * Created: 6 * Resolved: 1 - We organized a 2-day internal workshop on SAMOA at Telefonica I+D with researchers of Orange Labs, Telecom Paris and QCRI. Various have been discussed to improve SAMOA's ML and other interfaces with systems like Kafka, etc. - We submitted a proposal for funding which will help the development of new features on Samoa. - We have been working on a new release 0.5.0, probably coming up in one month. This release will have support for Kafka, a more well-rounded support for Avro and Json formats, as well as support to store predictions outputted from the model. - There was also significant work done to integrate correctly the instances between MOA and SAMOA, as there was a deviation of how they were defined and hindered the portability of new methods from MOA to SAMOA. - Early discussions to increase the committers / developers team by inviting new contributors to the panel. How has the project developed since the last report? - We are looking into new ML techniques for development. - Worked on the integration of Samoa-MOA instances - Engaging interactions with new parties (Orange Labs) and potential collaborations 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 PMC members elected? None Signed-off-by: [X](samoa) Alan Gates Comments: [ ](samoa) Ashutosh Chauhan Comments: [ ](samoa) Enis Soztutar Comments: [ ](samoa) Ted Dunning Comments: IPMC/Shepherd notes: Drew Farris (shepherd): One mentor active. Light activity on the project in general. -------------------- 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. Finish the distributed version 2. Nominate some candidate contributors as committers 3. Update the documentation and test all examples 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? There are 38 commits and 70 dev@ emails since the last report. We have reached 28 github contributors in total. How has the project developed since the last report? 1. We added more documentation including Jupyter notebooks and Chinese translation. 2. Debian package is improved with CPack 3. Memory optimization is added 4. We fixed some bugs and added several new features, e.g. image augmentation methods, L2 normalization layer and SigmoidCrossEntropy loss. How would you assess the podling's maturity? We will start the graduating process after the next release with the above issues fixed. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-02-12 When were the last committers or PPMC members elected? 2017-02-26 Signed-off-by: [ ](singa) Daniel Dai Comments: [X](singa) Alan Gates Comments: [ ](singa) Ted Dunning Comments: [ ](singa) Thejas Nair Comments: -------------------- Slider Slider is a collection of tools and technologies to package, deploy, and manage long running applications on Apache Hadoop YARN clusters. Slider has been incubating since 2014-04-29. Three most important issues to address in the move towards graduation: 1. Apache Slider community/PPMC has voted to move portions of Slider into Apache Hadoop YARN as modules. It is possible that the remaining pieces will be moved at a later point in time or become obsolete or evolve to work closely with YARN. Slider PPMC will decide what makes the most sense as we progress through this exciting time. 2. Getting more external users 3. Growth of a diverse set of developers/committers/PMC members is also crucial towards the final state of Slider Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Mailing list activity has been lower due to the bulk of the development moving to an Apache Hadoop branch. Questions on usage and issues encountered by end users keep coming at regular intervals, keeping the DL fairly active. How has the project developed since the last report? Work continues in parallel on the Apache Hadoop yarn-native-services branch and on the Slider podling. The bulk of the work has been in yarn-native-services, while a few Slider patches (related to critical issues or agent-only issues) have been committed as well. 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-23 slider-0.92.0-incubating When were the last committers or PPMC members elected? 2015-07-07: Yu (Thomas) Liu Signed-off-by: [ ](slider) Arun C Murthy Comments: [ ](slider) Devaraj Das Comments: [ ](slider) Jean-Baptiste Onofré Comments: [ ](slider) Mahadev Konar Comments: [X](slider) Vinod Kumar Vavilapalli Comments: Joined as a new mentor while the transition of Slider to Apache Hadoop project as a sub-module continues. Per feedback on general@, the community shall work on a concrete plan on how the project's journey in incubator comes to a close. IPMC/Shepherd notes: johndament: The IPMC still is looking for clarification on Slider/Hadoop's relationship. Will follow up. -------------------- Spot Apache Spot is a solution stack that provides the capability to ingest IT related telemetry (network flows, domain name service DNS, and proxy server logs) and provide unsupervised machine learning capabilities to identify suspicious activity. The information is organized and presented using operational analytics so that a security analyst can investigate the most suspicious connections. Apache Spot is built on an open data model using Apache Spark and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important issues to address in the move towards graduation: 1. Move infrastructure and development to ASF (code, issues, mailing list, ...) 2. Build diverse community 3. Demonstrate ability to create releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Two out of the four mentors are the ones showing the most active participation and involvement on the project so we need to discuss with IPMC our options to get the other two replaced. How has the community developed since the last report? By remaking the Community section on the Project webpage and driving users on Slack to limit the usage of the same tool just for quick interactions, the traffic over Mail Lists has increased, we still need to continue driving usage questions to USER list. A group of Developers from Brazil is coming with a proposal for UX and UI, based on the merits of the proposal, and the potential that the same has we have invited them to become Committers on the projects. The initial purpose of the Project on Network & Security needs to expand the scope to IT Analytics to cover other uses cases and/or enrich content with User and Endpoint data. While a normalization framework has been drafted to what we call Open Data Model we still need more work and contributions on technical delivery to make it a reality. Contributions to improve the concept of Ingestion Pipeline & Data Lake are delivered with more cadence, there is a recognition from Community to normalize data to open the space for other sources of Ingestion How has the project developed since the last report? The team has created the epic on ASF JIRA towards the first Apache release, we’re working now including the user stories that will be part of release, and doing checks to what can be delivered before we do the the formal announcement on DEV for the code freeze. Integrations for context enrichment are critical, however also the need of bringing a plugin manager where does can be handled, the Spec was drafted, and the team now is finalizing the last Pull requests to begin merging functionality onto project code. Documentation is an area of focus so from May to July committers we’ll continue improving & detailing more, architecture definitions, deployment options, and UI usage sections. As the whole delivery is concluded we’ll vote for a FAQ section which can be a point of reference for common issues/situations. Being part of ASF is important Community requests that project enables integration/consumption of other Apache projects, one of our DEVOPS committers, for that reason having an API framework now will open the door for more smooth integrations. Date of last release: N/A When were the last committers or PMC members elected? Last committer was elected on 06/02 How does the podling rate their own maturity? By know we’re almost ready to do our first Apache Release which is good, but we still need to mature Community, the ramping of other Contributors has been slow, we have a strong base of Consumer positive aspect as it probed consumption, however more Commits from other interested parties will accelerate functionality delivery. Signed-off-by: [X](spot) Jarek Jarcec Cecho Comments: [ ](spot) Brock Noland Comments: [ ](spot) Andrei Savu Comments: [X](spot) Uma Maheswara Rao G Comments: -------------------- Streams Apache Streams (incubating) 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. Streams has been incubating since 2012-11-20. Three most important issues to address in the move towards graduation: 1. Community growth and PMC maturity. 2. Demonstrate a consistent release schedule. 3. Participation of project community within related standards-bodies and Apache projects. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The community has completed an internal assessment using the Apache Maturity Model to identify gaps that should be addressed before graduation. The community is working against a task list of graduation TODOs: https://cwiki.apache.org/confluence/display/STREAMS/Graduation+TODOs It is likely that Streams will pursue graduation to TLP during the coming quarter. How has the community developed since the last report? Dev List 57 emails sent by 12 people, divided into 20 topics Web Page 820 Sessions (up ~75%), 508 Users (up ~50%), 1507 Pageviews (up ~30%). Public Slack: apachestreams.slack.com 1202 Messages, 11 Files Committers Slack: the-asf.slack.com #dev-streams 157 Messages, 3 Files How has the project developed since the last report? Source Control https://github.com/apache/incubator-streams Excluding merges, 4 authors have pushed 29 commits to master. On master, 165 files have changed and there have been 5,891 additions and 1,647 deletions. https://github.com/apache/incubator-streams-examples Excluding merges, 3 authors have pushed 4 commits to master. On master, 10 files have changed and there have been 18 additions and 72 deletions. JIRA 24 issues closed with 0.5-incubating release 7 issues closed after 0.5-incubating release 18 new issues opened this period Date of last release: 2017-03-20 : 0.5-incubating release When were the last committers or PMC members elected? 2017-04-14: Trevor Grant elected as committer / PPMC member Signed-off-by: [X](streams) Matt Franklin Comments: The community is small, but diverse and dedicated. I look forward to seeing them move past the incubator and hopefully continuing to add new contributors. [X](streams) Ate Douma Comments: [X](streams) Suneel Marthi Comments: -------------------- Superset Superset is business intelligence (BI) software that helps modern organizations visualize and interact with their data. Superset enables users explore data from a variety of databases, assemble beautiful dashboards and share their findings. Superset works neatly with all modern SQL-speaking databases, and integrates with Druid.io to provide real-time, interactive, blazing fast data access to large datasets. Superset has been incubating since 2017-05-02. Three most important issues to address in the move towards graduation: 1. Grow the community and enroll new committers. 2. Setup our Git repository and transition our codebase there now that our contributor CLAs and Airbnb SGA is complete 3. Move the website to apache.org Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? The team is working on finishing up all the items on the Incubation Checklist. We’re working on finding a way to link Jira Issues to GitHub Issues as the team has a preference for using GitHub Issues for tracking. How has the community developed since the last report? * The mailing lists have been created (dev@superset.incubator.apache.org & private@superset.incubator.apache.org) and all project communication now takes place on the mailing list and is open for everyone. * Organic growth of our Github contributors (140), forks (1981), watchers (707) and stars (14 331) * Recent talk were given by Maxime Beauchemin at DataEngConf and PlotCon How has the project developed since the last report? * The team has filed an executed SGA from Airbnb allowing the team to move forward with migrating the code base to a Git repository on ASF * A JIRA project has been setup for issue tracking * 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 does the podling rate their own maturity. [X] Initial setup [ ] 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 Q3, 2017) When were the last committers or PPMC members elected? Project is still functioning with the initial set of committers Signed-off-by: [X](superset) Ashutosh Chauhan Comments: [X](superset) Luke Han Comments: [X](superset) Jim Jagielski Comments: IPMC/Shepherd notes: Drew Farris (shepherd): Three mentors active on the mailing lists. Incubation is just getting started. Discussion of SGA, infrastructure setup and migration of git repo observed. -------------------- Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important issues to address in the move towards graduation: 1. finally release 0.3 - RC vote already took place 2. Release next artifacts after core/API 0.3-incubating is out 3. graduate Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We would like to graduate after our new release is out. How has the community developed since the last report? Many discussions and bug reports were filed in order to see how microprofile.io discussions match the Tamaya roadmap. In order to prepare for the new release some people (inactive for quite a while) were moved to the emeritus section. How has the project developed since the last report? New homepage is live, release candidates for 0.3-incubating are out. Waiting to continue with extensions and further development on sandbox modules. 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: 2016-04-06 When were the last committers or PPMC members elected? P. Ottlinger at 2016-04-24. Signed-off-by: [X](tamaya) John D. Ament Comments: It's a small and diverse community. They have a little bit to go before graduation, and need to figure out how to get communicating more on list. [ ](tamaya) David Blevins 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. Project maturity evaluation 2. IP/Licence Review 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? New contributor showing interest (some pull requests and Jira issues). Need to get them engaged also on mailing list. Project activity still slow overall - need more day-to-day encouragement and follow-up? Suggested weekly telcons How has the project developed since the last report? Taverna Mobile Android app (initially a GSOC contribution) has matured and is ready for its first release. Some bugs raised on the Taverna Server, lacking contributors - need more code insight from original author? 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: From the recent graduation/IP review it was agreed to skip some of the auxiliary git repositories from the graduation process (move to GitHub) - but this has not yet happened. Although the community is ready, we are lacking initiative on the bureaucratic side and need to push ourselves harder. Date of last release: 2016-07-01 When were the last committers or PPMC members elected? 2016-10-20 Committer 2015-12-09 PPMC member Signed-off-by: [x](taverna) Andy Seaborne Comments: Taverna has been quiet for 6 months with low activity on the dev@ list. More community building would be valuable for the long-term success of the project. [x](taverna) Stian Soiland-Reyes Comments: Project needs to find a daily/weekly rhythm to engage the community more. This is a general task for the podling PMC, it should not have to rely on any one particular person. [ ](taverna) Daniel J Debrunner Comments: [ ](taverna) Marlon Pierce Comments: [ ](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? - Andreas Neumann talked about Apache Tephra as part of his talk on "Transactions in Hadoop" at ApacheCon BigData North America 2017 in Miami, Florida, USA - 2 new subscribers in dev mailing list since the last report - 4 new JIRAs filed since the last report - 0 external contributors submitted patches since the last report - 1 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 - Released 0.12.0-incubating 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-05-23 When were the last committers or PPMC 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: -------------------- Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. Toree has been incubating since 2015-12-02. Three most important issues to address in the move towards graduation: 1. More discussion and engagement on the dev list 2. Community growth 3. Continue to make releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * No issues require attention at this time. How has the community developed since the last report? * Toree's 0.1.0-incubating release is a good step forward. The first Apache release is the most difficult, so clearing that hurdle should make further releases easier. * The community has also added a new PPMC member and mentor. How has the project developed since the last report? * Apache Toree 0.1.0-incubating release on 2017-02-21 * Apache Toree website updated 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-02-21 When were the last committers or PPMC members elected? * Ryan Blue was added to the PMC on 2017-04-03 Signed-off-by: [ ](toree) Luciano Resende Comments: [ ](toree) Reynold Xin Comments: [X](toree) Hitesh Shah Comments: [ ](toree) Julien Le Dem Comments: [X](toree) Ryan Blue 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? * None How has the community developed since the last report? * Participation in the project remains healthy: - ML subscriptions public lists: 93 user, 100 dev, 26 code rev, 39 issues, 32 commits - ML postings: 81 user (+161%), 349 dev (+27%), 480 coderev (-7%), 801 issues (-7%), 735 commits (+24%) - Twitter: 218 (followers), 72 tweets, 67 likes * We released version 2.1 * Release 2.1 triggered the attention of a Gartner analyst * Sandhya Sundaresan stepped down as the Release Manager on 2017-05-08 * Ming Liu volunteered on on 2017-05-08 to be the Release Manager for our next release * We are working towards our next release, 2.2. * Sean Broeder gave a talk on Trafodion at the HBase meet up in San Francisco, hosted by Splice Machine, on 2016-12-08 * Peng-Xiang Liu gave a talk on BigData architecture and solution design with Trafodion at DevEco (www.deveco.io) at the China- Singapore Suzhou Industrial Park, Suzhou, China on 2016-12-10 * Discussion regarding Readiness to Graduate continues. Diversity continues to grow. How has the project developed since the last report? * 191 commits from 23 contributors. * 117 JIRAs filed and 42 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? * New PPMC member(s): Arvind Narain (2017-03-08) Pierre Smits (2017-03-08) * New Committer(s): Yi Zhang (Eason) (2017-03-10) Signed-off-by: [ ](trafodion) Devaraj Das Comments: [ ](trafodion) Enis Söztutar Comments: [X](trafodion) Michael Stack Comments: IPMC/Shepherd notes: johndament: The podling has confirmed that there is only one active mentor on the project, needs to be addressed. -------------------- 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? A ToDo list of tasks to reach graduation has been set, and some members are working on it. 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) Upayavira Comments: Wave continues as a very small scale project. It hovers just under the threshold of sufficient participation for graduation, whilst is too active to argue for retirement. IPMC/Shepherd notes: johndament: Considering your comments, are there additional contributors who you think may make sense to start to invite? upayavira: perhaps a new mentor might bring something new, but repeated efforts to draw in new contributors have not brought the kind of interest the project needs. It remains one active PPMC member below the minimum for graduation. Any help warmly accepted, even if short term. ----------------------------------------- Attachment AG: Report from the Apache Jackrabbit Project [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. 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. The PMC resolved the impact of the recently published SHA-1 collisions in the development branch. Back ports to maintenance branches are under consideration. The last quarter saw a much needed and anticipated refactoring of the Oak code base leading to an overall improved and simplified module structure. While some of this work is still ongoing we expect it to have a positive effect on the overall evolvability and maintainability of the code base. We will be holding an Oak Hackathon August 21st to 25th in Basel, Switzerland (https://wiki.apache.org/jackrabbit/Oakathon%20August%202017). Attendance is open and free to everybody wanting to hack Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues. ## PMC changes: - Currently 51 PMC members. - Robert Munteanu was added to the PMC on Mon May 22 2017 ## Committer base changes: - Currently 51 committers. - Robert Munteanu was added as a committer on Mon May 22 2017 ## Releases: - jackrabbit-2.12.7 was released on Mon Apr 03 2017 - jackrabbit-2.14.1 was released on Mon May 29 2017 - jackrabbit-2.15.2 was released on Mon May 01 2017 - jackrabbit-2.15.3 was released on Fri Jun 09 2017 - oak-1.0.38 was released on Tue Mar 28 2017 - oak-1.2.25 was released on Tue Apr 11 2017 - oak-1.2.26 was released on Mon Jun 05 2017 - oak-1.4.15 was released on Mon Apr 03 2017 - oak-1.4.16 was released on Mon Jun 05 2017 - oak-1.6.2 was released on Mon Jun 12 2017 - oak-1.7.0 was released on Wed May 24 2017 - oak-1.7.1 was released on Tue Jun 06 2017 - vault-3.1.38 was released on Mon Mar 27 2017 ## JIRA activity: - 451 JIRA tickets created in the last 3 months - 397 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AH: Report from the Apache Karaf Project [Jean-Baptiste Onofré] ## Description: - Apache Karaf provides a very modern and polymorphic container, multi-purpose (microservices, OSGi, etc) powered by OSGi. ## Issues: - There are no issues requiring board attention at this time ## Activity: - We did 4 releases in the last 3 months. 3 are maintenance release, and Cellar 4.1.0 is the first release in the Cellar 4.1.x series bringing lot of new features, improvements and fully compliant with Karaf 4.1.x - "Large Apache Karaf cluster with Karaf Cellar and Mesos" talk has been given during ApacheCon NA '17 Miami. We noticed important interest during the talk and we got lot of questions and feedbacks from users. - We are preparing Karaf 4.1.2, Cellar 4.1.1 and Decanter 1.4.0 releases. - An important work is in progress on the documentation (mostly dev guide with samples). It's longer than we expected, but we did good progress and hopefully it should be available on our website soon. ## Health report: - Our user community is still growing up, and ApacheCon was a great way to meet users in person. We had several discussions and demos in the hacking area during ApacheCon. - We addressed the trademark issue mentioned in the previous report. - As usual, we are watching potential new PMC members and committers. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Christian Schneider on Mon Aug 22 2016 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Grzegorz Grzybek at Mon Oct 31 2016 ## Releases: - 4.0.9 was released on Mon Apr 10 2017 - 4.1.1 was released on Fri Mar 31 2017 - Cellar 4.0.4 was released on Mon May 15 2017 - Cellar 4.1.0 was released on Mon May 15 2017 ## Mailing list activity: - dev@karaf.apache.org: - 190 subscribers (up 4 in the last 3 months): - 236 emails sent to list (335 in previous quarter) - user@karaf.apache.org: - 395 subscribers (up 22 in the last 3 months): - 565 emails sent to list (559 in previous quarter) ## JIRA activity: - 145 JIRA tickets created in the last 3 months - 126 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AI: Report from the Apache Labs Project [Danny Angus] ----------------------------------------- Attachment AJ: 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 is actively working on both Lucene and Solr, with daily commits, towards Lucene and Solr 7 releases - We pushed out 5 releases since last report - Discussions are generally flowing in a good shape - Meetups / conferences around Lucene / Solr: - Berlin Buzzwords (12-14 June 2017): not Lucene/Solr related but lots of Lucene / Solr related talks were presented ## PMC changes: - Christian Moen was added to the PMC on Thu May 18 2017 - Shawn Heisey was added to the PMC on Thu May 18 2017 - Currently 43 PMC members ## Committer base changes: - Mike Drob was added as a committer on Thu May 04 2017 - Currently 68 committers and 43 PMC members. ## Releases: - Apache Lucene 6.6.0 released on 6 June 2017 - Apache Solr 6.6.0 released on 6 June 2017 - Apache Lucene 6.5.1 released on 27 April 2017 - Apache Solr 6.5.1 released on 27 April 2017 - pylucene 6.5.0 released on Thu Apr 06 2017 ----------------------------------------- Attachment AK: Report from the Apache Lucene.Net Project [Prescott Nasser] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == * As of last board report we had finally shipped beta 1 of Lucene 4.8.0. We are currently at 4.8.0-beta00004 * Strong community involvement to get this over the line, and lots of people are jumping in to give feedback on the release. == Releases == * Release 4.8.0 Beta4 - May 21st, 2017 * Release 4.8.0 Beta1 - May 9th, 2017 * Release 3.0.3 - Oct 2012 == Statistics == * Last PMC Member added May 2017, Shad Storhaug * Last committer added Sept 2016, Shad Storhaug Nuget package downloads: As we will have 17 packages for 4.8.0 release, I'll work on a new way to present these metrics. Currently we have just over 900 downloads of the core beta package and 50 for the various libraries that add additional features ----------------------------------------- Attachment AL: Report from the Apache Metron Project [Casey Stella] ## Description: Metron integrates a variety of open source big data technologies in order to offer a centralized tool for security monitoring and analysis. Metron provides capabilities for log aggregation, full packet capture indexing, storage, advanced behavioral analytics and data enrichment, while applying the most current threat-intelligence information to security telemetry within a single platform. ## Issues: There are no issues requiring board attention at this time ## Activity: - We are unincubated - We are in the middle of voting for a release, our first as an top level - Given some performance work that happened late last month motivated the community to hold the release for that. ## Health report: Project activity is broadly the same as in prior months. There was some renewed interest after graduation in user@ and it's evident that more people are trying the product. Also, there were a number of talks associated with Metron in Hadoop Summit San Jose this month. I think we will see increased interest and traffic. ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - A new PMC member is being discussed presently in private@ ## Committer base changes: - Currently 35 committers. - New commmitters: - Billie Rinaldi was added as a committer on Tue May 23 2017 - Jim Baker was added as a committer on Tue May 23 2017 - JJ Meyer was added as a committer on Tue May 23 2017 - Jon Zeolla was added as a committer on Tue May 23 2017 - Kyle Richardson was added as a committer on Tue May 23 2017 - Justin Leet was added as a committer on Tue May 23 2017 - Matthew Foley was added as a committer on Tue May 23 2017 - Chris Mattmann was added as a committer on Tue May 23 2017 - Michael Miklavcic was added as a committer on Tue May 23 2017 - Owen O'Malley was added as a committer on Tue May 23 2017 - Otto Fowler was added as a committer on Tue May 23 2017 ## Releases: - No release data could be found [FIX!] ## Mailing list activity: - dev@metron.apache.org: - 181 subscribers (up 16 in the last 3 months): - 2725 emails sent to list (2598 in previous quarter) - issues@metron.apache.org: - 22 subscribers (up 0 in the last 3 months): - 2192 emails sent to list (1966 in previous quarter) - user@metron.apache.org: - 207 subscribers (up 20 in the last 3 months): - 417 emails sent to list (170 in previous quarter) ## JIRA activity: - 231 JIRA tickets created in the last 3 months - 146 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AM: 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 has endorsed the "Support Apache" initiative by publishing a news item in the landing page of the website - refactoring and stabilization of source code is slowly progressing - new features, improvements and bug fixes have been contributed and integrated into the official code base: 147 tickets created and 121 tickets resolved in the last quarter - there are new and ongoing initiatives to improve the documentation for developers and users - mailing list activity have been on average for number of messages exchanged and for the number of subscriptions - the activity in the official blog [1] and Twitter account [2] is steady with monthly blog posts and tweets; we have a rather low activity in our public HipChat room [3] - the project has now an official Facebook page [4] and Vimeo account [5] - we are still actively tracking and following up on trademark violations ## Health report: - the last quarter have been a normal one in the life of the project; the community is supportive and active; no new committer or PMC members have been invited in this quarter; we have published a new release ## Answers to comments made by Board members to our last report Mark Thomas: "I'd be interested in hearing in your next report what impact the architectural changes have had on the community - particularly levels of involvement and activity." - The main architectural changes have been the switch from Ant to Gradle as the project's build system and the split of the codebase into two repositories: one for the core framework and one for the extensions/plugins. However the latter is still a work in progress with active discussions [7] as infrastructure and code are still being developed to serve plugins to users [8]. Impact can be measured after publishing plugins which is expected with the next major release of OFBiz. On the other hand the switch to Gradle, introduced in the 16.11 series, has been already published since we have 2 releases in the series: 16.11.01 and the new 16.11.02. So far the impact has not been huge: we are getting a few questions in the mailing list and in Stackoverflow about how to perform traditional Ant tasks in the new way; the questions are promptly answered and documentation has been produced to assist the users [6]. ## 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 42 committers. - No new committers added in the last 3 months - Last committer addition was James Yong at Fri Mar 03 2017 ## Releases: - 16.11.02 was released on Mon May 22 2017 ## References [1] https://blogs.apache.org/ofbiz/ [2] https://twitter.com/ApacheOfbiz [3] https://apache.hipchat.com/chat/room/2814115 [4] https://www.facebook.com/Apache-OFBiz-1478219232210477/ [5] https://vimeo.com/ofbiz [6] https://github.com/apache/ofbiz/blob/trunk/README.md [7] https://s.apache.org/DVj8 [8] https://issues.apache.org/jira/browse/INFRA-13924 ----------------------------------------- Attachment AN: 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. Since the last report no new releases were done. As of last week we got few request regarding new releases in the 4.x code line and the 2.x code line. As of now no release candidate has been produced but we are working on that. The project should pick up a more steady release schedule again once the 4.01 specification is released. This specification is currently in public review at Oasis. Last report I said that there are individuals that contribute a lot to Olingo. I am pleased to say that that this resulted in invites to become Olingo committers for Archana Rai and Ramya Vasanth. Both accepted and have been contributing since then. === 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. - New commmitters: - Archana Rai was added as a committer on Fri May 26 2017 - Ramya Vasanth was added as a committer on Fri May 26 2017 ## Releases: - Last release was (Java) V4 4.3.0 on Mon Sep 19 2016 ## Mailing list activity: - dev@olingo.apache.org: - 87 subscribers (up 0 in the last 3 months): - 324 emails sent to list (212 in previous quarter) - user@olingo.apache.org: - 178 subscribers (up 4 in the last 3 months): - 19 emails sent to list (50 in previous quarter) ## JIRA activity: - 42 JIRA tickets created in the last 3 months - 36 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: Report from the Apache Oltu Project [Antonio Sanso] ----------------------------------------- Attachment AP: 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.0 on Wed Jun 29 2016 We resolved 0 issues for this release. Whilst development remains quiet we have a number of OODT 2.0 features under active development, these include integration of a new curation module and the development of the new zookeeper configuration engine by our GSOC student. We will start rolling out new test builds for both of these features in the near future with the aim of moving towards a 1.1 release for the curator and 2.0 alpha for the new zookeeper components. COMMUNITY Latest committers and PMC members Sujen Shah(sujen) on 5th April 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 was good turn out and discussion at ApacheCon Miami for our last minute OODT 2.0 talk along with ongoing development for new releases and website content. ----------------------------------------- Attachment AQ: 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 guidance from Infra for performing daily updates to the website via Jenkins CI ## Activity: 1. Project had a major 1.8.0 release in May 2017. 2. The team’s presently working on 1.8.1 release planned for June 2017. 3. The project now has a new logo - courtesy of Bruno Kinoshita with contributions by Koji Sekiguchi . 4. The project website was completely redone with JBake by Bruno Kinoshita and William Colen. 5. An Irish Sentence Detector component was contributed by Jim Regan. 6. New Language Detector Module from William Colen will be part of the next release. ### Conferences/Public Speaking: Tommaso Teofili and Suneel Marthi presented a talk using Apache OpenNLP Language detector titled ‘Embracing Diversity: Searching over Multiple Languages’ at Berlin Buzzwords, June 12, 2017, Berlin, Germany Suneel Marthi presented a talk ‘Large Scale Analysis of Structured Text’ using Apache OpenNLP and Apache Flink at Dataworks Summit, San Jose on June 15, 2017. Daniel Russ will be presenting some of his work using Apache OpenNLP at Data Science Maryland meetup on June 19, 2017 - https://www.meetup.com/Data-Science-MD/events/240470935/?gj=co2&rv=co2 3 of the PMC members - Jorn Kottmann, Tommaso Teofili, Suneel Marthi were at Berlin Buzzwords 2017, Berlin, Germany. ## Health report: - Project has healthy activity levels and dedicated committers. Four new committers were added in the past quarter and one committer was promoted to PMC. ## PMC changes: - Currently 11 PMC members. - Daniel Russ was added to the PMC on Tue Apr 18 2017 ## Committer base changes: - Currently 21 committers. - New committers: - Jeffrey T. Zemerick was added as a committer on Wed Apr 26 2017 - Bruno P. Kinoshita was added as a committer on Fri Apr 21 2017 - Koji Sekiguchi was added as a committer on Wed Apr 12 2017 - Peter Thygesen was added as a committer on Sat Mar 25 2017 ## Releases: - 1.8.0 was released on Wed May 17 2017 ## Mailing list activity: - users@opennlp.apache.org: - 431 subscribers (up 10 in the last 3 months): - 37 emails sent to list (123 in previous quarter) - dev@opennlp.apache.org: - 223 subscribers (up 1 in the last 3 months): - 391 emails sent to list (466 in previous quarter) ## JIRA activity: - 84 JIRA tickets created in the last 3 months - 80 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: 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" specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1 and CDI-1.2 (MR) specifications (JSR-346). The OWB community also maintains a small server based as Apache Meecrowave subproject. Meecrowave consists of Tocmat9 + OpenWebBeans + CXF + Johnzon. ## Issues: There are no issues requiring board attention at this time. ## Activity: We have finished implementing the CDI-2.0 (JSR-365) specification. The spec and TCK are available under ALv2 thanks to JBoss. We are now successfully passing the TCK and expect to ship an OWB-2.0.0 release this month. Apache Meecrowave (an OWB subproject) is also progressing fine. We will likely ship a new version this month as well. After OWB-2.0 is out we will also upgrade Meecrowvave to CDI-2.0. ## Health report: The community is small but quite healthy. We are always keeping our eyes open for new committers. New people keep popping up on our lists and ticket system but there is a rather big gap between using OWB and providing deep patches it seems. ## 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: - 1.7.3 was released on Wed Apr 19 2017 - meecrowave-0.3.1 was released on Tue May 02 2017 ## Mailing list activity: - dev@openwebbeans.apache.org: - 71 subscribers (up 0 in the last 3 months): - 261 emails sent to list (177 in previous quarter) - user@openwebbeans.apache.org: - 98 subscribers (up 1 in the last 3 months): - 12 emails sent to list (18 in previous quarter) ## JIRA activity: - 44 JIRA tickets created in the last 3 months - 31 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AS: Report from the Apache Pig Project [Daniel Dai] ----------------------------------------- Attachment AT: 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: There has been a lot of activity (relatively-speaking) this quarter: a "show-stopper" issue showed up with the release of Java 8u131 that required an immediate fix, which was done within a few days; much work is being done in "trunk" on implement Input Method Editor support for text controls; and the next maintenance release is just about to happen. Health report: With the "show-stopper" issue a number of people who had been quietly using Pivot in the background "resurfaced" to weigh in, which indicated that there are more people interested in the project than is reflected in the mailing list statistics. This is heartening. The upcoming maintenance release should help as well, hopefully, to revive some interest. 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.4 on Sun May 18 2014 - Next release (2.0.5) is in process. Mailing list activity: The developer list activity is way up due to the increased coding in "trunk" and fixing the "show-stopper" issue in the maintenance branch. Incidentally the change in mailing list subscribers was actually due to a user changing his email address, and he contacted us for help. - dev@pivot.apache.org: - 62 subscribers (down -1 in the last 3 months): - 131 emails sent to list (21 in previous quarter) - user@pivot.apache.org: - 174 subscribers (down -1 in the last 3 months): - 5 emails sent to list (6 in previous quarter) JIRA activity: - 7 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months - About 5 tickets were also changed to move them out from 2.0.5 to 2.1 in order to expedite the 2.0.5 release. ----------------------------------------- Attachment AU: 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: No issues that requires Board attention at this point in time. Activity This has been a quarter much more busy than normal. We tried to make a release in April, but had to pull it due to missing a couple of incompatibility changes desired, as well as one feature not working as advertised. A new attempt at a release is planned for July. We want to change the logo, have a basic idea, but not gotten to actually do it. Last outstanding issue regarding the name change. Health report Stanislav has been voted into the PMC. Before we came to Apache, he was very active, and ended up creating a C# fork/clone and been working on that since. During this quarter he has assisted in some design decisions, by comparing what he has in the C# version. Discussion is also on-going whether that C# version should be brought to Polygene as well. Other than that, community growth is not what we wished it to be. PMC changes - Currently 12 PMC members. - Stanislav Muhametsin was added to the PMC 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 more than 2 years ago Releases: - Last release was in August 2015 Mailing list activity: I suspect that the drop of 2 subscribers this quarter may be due to the amount of email sent, both discussing the release as well as the many Jenkins reports of broken builds. - users@polygene.apache.org: - 19 subscribers (up 0 in the last 3 months): - 1 emails sent to list (2 in previous quarter) - dev@polygene.apache.org: - 37 subscribers (down -2 in the last 3 months): - 718 emails sent to list (231 in previous quarter) JIRA activity: - 22 JIRA tickets created in the last 3 months - 53 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AV: Report from the Apache Portable Runtime (APR) Project [Nick Kew] 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: - Activity has been substantially above average as we have worked towards a new release 1.6 of APR and APR-UTIL. Release candidates APR-1.6.0 and APR-UTIL-1.6.0 were tagged on April 15th. After identifying problems with the APR candidate, further work led to tagging APR-1.6.1 on May 31st, but that too had a problem. Since the end of the period, APR-1.6.2 has been tagged, and voted for release along with APR-UTIL-1.6.0. ## Health report: - The release process has highlighted the difficulty (of which we have long been aware) of supporting platforms outside those regularly used by the core team. A proposal to help deal with this problem is being floated. ## 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: - Last releases were APR-1.5.2 on Wed Apr 29 2015 and APR-UTIL-1.5.4 on Sept 22 2014. ## Mailing list activity: - Increased activity due primarily to release drive. Fewer subscribers: we can only speculate that the increased activity has prompted people who are no longer interested to unsubscribe. - dev@apr.apache.org: - 329 subscribers (down -10 in the last 3 months): - 365 emails sent to list (194 in previous quarter) - bugs@apr.apache.org: - 22 subscribers (up 0 in the last 3 months): - 33 emails sent to list (29 in previous quarter) ## Bugzilla Statistics: - 4 Bugzilla tickets created in the last 3 months - 3 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment AW: Report from the Apache Portals Project [David Sean Taylor] Please find the Apache Portals board report for June 2017 ## 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 1 release since the last report. 12 Feb 2017 - Two new PMC members added 27 April 2017 - Apache Portals Pluto team released Pluto Maven Archetypes 3.0 to support to developing new portlets to the new 3.0 spec ## Mailing list activity: Not much activity. Some discussions around 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 AX: 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: - TODO - list any issues that require board attention, there are no issues requiring board attention at this time ## Activity: - Active development for Sentry high-availability - Started discussion of the release strategy ## Health report: Development activity seems pretty consistent. ## PMC changes: - Currently 34 PMC members. - Alex Kolbasov was added to the PMC on Mon May 08 2017 ## Committer base changes: - Currently 36 committers. - Vadim Spector was added as a committer on Fri Jun 02 2017 ## Releases: - Last release was 1.7.0 on Tue Jun 14 2016 ## Mailing list activity: - TODO Please explain what the following statistics mean for the project. If there is nothing significant in the figures, omit this section. - dev@sentry.apache.org: - 93 subscribers (up 5 in the last 3 months): - 1011 emails sent to list (546 in previous quarter) - issues@sentry.apache.org: - 18 subscribers (up 2 in the last 3 months): - 2529 emails sent to list (1342 in previous quarter) ## JIRA activity: - 146 JIRA tickets created in the last 3 months - 125 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AY: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] ## Description Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF and Karaf to provide a complete, enterprise-ready ESB powered by OSGi. ## Issues There are no outstanding issues requiring board attention. ## Activity The project focus of Apache ServiceMix is the assembly of the integration container, the actual functionality is being maintained in related projects like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ. - We have prepared 2 releases of Apache ServiceMix: maintenance release 6.1.4 and next development release 7.0.1. We don't expect too much activity on ServceMix 6 and we plan to transit in into EOL soon. In the new period we are going to focus on the further development, stability and maintenance of ServiceMix 7. We are working on new releases of ServiceMix 7 upgraded to the new dependency versions, especially Apache Karaf 4.1.x and new Apache Camel versions. - We have also released 2 sets of OSGi bundles and a new release of ServiceMix Specs. We are currently working on new Bundles and Specs releases. - Thanks to a contribution we did a big step in documentation improvement. The documentation has been migrated into Asciidoc format and updated with the actual state of ServiceMix. It should be integrated soon in our website. - 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. - Jean-Baptiste Onofré has submitted a new feature proposal. The new feature should extend ServiceMix with ability to manage APIs. We are going to accept the initial contribution and work on the new feature to provide it in one of the next releases. ## Health report - Activity on the mailing lists and in JIRA is on the same level like in the last period. We had some contributions. - We have invited Andrea Cosentino to become a new PMC member - We are still watching potential new PMC members and committers ## 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.8.0 on Mar 24 2016 - Apache ServiceMix Bundles 2017.03 on April 06 2017 - Apache ServiceMix Bundles 2017.04 on May 07 2017 - Apache ServiceMix 6.1.4 on May 27 2017 - Apache ServiceMix 7.0.1 on May 27 2017 ## JIRA activity - 105 JIRA tickets created in the last 3 months - 107 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AZ: Report from the Apache Shiro Project [Les Hazlewood] Apache Shiro is a powerful and flexible open-source application security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. We have no issues that require Board assistance at this time. Releases: - Last release was 1.4.0 on 05-May-2017 Community & Project: - Mailing list traffic has remained the same. - 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 BA: 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. Good activity level overall, contributions from different people continue. Major release Sling 9 is just around the corner. No new committer (last committers change was in September 2016 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 JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, and Tooling Support Source 1.0.4 (June 6th, 2017) - Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, and Commons Metrics 1.2.2 (June 6th, 2017) - Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0 (June 2nd, 2017) - Apache Sling SLF4J Implementation (Logback) 5.0.2 (June 1st, 2017) - Apache Sling JCR Resource 3.0.2 (May 31st, 2017) - Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2, Context-Aware Configuration SPI 1.3.2, Context-Aware Configuration Impl 1.4.2, Context-Aware Configuration Mock Plugin 1.3.0, Launchpad Content 2.0.12 (May 29th, 2017) - Apache Sling Servlet Post 2.3.20, JCR Contentloader 2.2.2, Launchpad Base 5.6.4-2.6.18 (May 28th, 2017) - Apache Sling Service User Mapper 1.3.2, Apache Sling JCR Base Bundle 3.0.2, Apache Sling Web Console Branding 1.0.2 and Apache Sling Engine Implementation 2.6.8 (May 22nd, 2017) - Apache Sling Servlets Get 2.1.26 and Apache Sling Servlets Post 2.3.18 (May 19th, 2017) - Apache Sling Commons Scheduler 2.6.2 and Apache Sling Installer Core 3.8.10 (May 18th, 2017) - Apache Sling Models Impl 1.4.2, Testing OSGi Mock 2.3.2, OSGi Mock 1.9.6, Sling Mock 2.2.10, Sling Mock 1.9.8, Apache Sling Auth Core 1.3.24 (May 15th, 2017) - Apache Sling JUnit Scriptable Tests Provider 1.0.12 (May 12th, 2017) - Apache Sling XSS Protection Compat Bundle 1.1.0 (May 11th, 2017) - Apache Sling Scripting JavaScript 3.0.0 (May 11th, 2017) - Apache Sling Junit Core 1.0.24, Junit Teleporter 1.0.14, and Testing Tools 1.0.16 (May 11th, 2017) - Apache Sling Adapter 2.1.10 (May 11th, 2017) - Apache Sling Servlets Get 2.1.24, Servlets Post 2.3.16, and JCR Jackrabbit Access Manager 3.0.0 (May 11th, 2017) - Apache Sling Healthcheck API 1.0.0 and Core 1.2.8 (May 11th, 2017) - Apache Sling Discovery Commons 1.0.20, Base 2.0.0, Impl 1.2.12, and Oak 1.2.18 (May 11th, 2017) - Apache Sling Scripting HTL Java Compiler 1.0.10, Apache Sling Scripting HTL Engine 1.0.34, Apache Sling Scripting HTL JS Use Provider 1.0.22 , Apache Sling Servlets Resolver 2.4.12 (May 9th, 2017) - Apache Sling Installer Core 3.8.8 (May 8th, 2017) - Apache Sling JCR ContentLoader 2.2.0, Pax Exam Utilities 1.0.4, Apache Sling File System Resource Provider 2.1.0, File System Resource Provider 1.4.0, JCR Content Parser 1.1.0 (May 8th, 2017) - Apache Sling XSS Protection Bundle 2.0.0, XSS Protection Compat Bundle 1.0.0, Sling Resource Resolver 1.5.24, Context-Aware Configuration Impl 1.4.0, Context-Aware Configuration Mock Plugin 1.2.0, Testing JCR Mock 1.3.0, OSGi Mock 2.3.0, Sling Mock 2.2.8 (May 5th, 2017) - Apache Sling Models API 1.3.4 and Models Implementation 1.4.0 (May 1st, 2017) - Apache Sling JCR Installer Provider 3.1.26 (May 1st, 2017) - Apache Sling JCR Resource 3.0.0 (May 1st, 2017) - Apache Sling Sling Slingstart Maven Plugin 1.7.4, Apache Sling Service User Mapper 1.3.0, Apache Sling Scripting API 2.2.0 and Tooling Support Source 1.0.2 (May 1th, 2017) - Apache Sling Commons Johnzon 1.0.0 (April 29th, 2017) - Apache Sling Event API 1.0.0 (April 19th, 2017) - Apache Sling Validation API and Core 1.0.0 (April 12th, 2017) - Apache Sling Testing ResourceResolver Mock 1.1.18 (April 4th, 2017) - Apache Sling JCR Jackrabbit User Manager 2.2.6 (April 3rd, 2017) - Apache Sling Resource Resolver 1.5.22 and Apache Sling Service User Mapper 1.2.6, Apache Sling Testing Sling Mock 2.2.6, Sling Mock 1.9.6, Sling Mock Oak 1.0.2, Context-Aware Configuration Implementation 1.3.2, File System Resource Provider 2.0.0, File System Resource Provider 1.3.0 (March 30th, 2017) - Apache Sling CAConfig SPI 1.3.0, CAConfig Impl 1.3.0, CAConfig Mock Plugin 1.1.0, Apache Sling Maven Sling Plugin 2.2.0 (March 24th, 2017) - Apache Sling JCR Content Parser 1.0.0, Testing OSGi Mock 2.2.4, Testing OSGi Mock 1.9.4 (March 23th, 2017) - Apache Sling Commons JSON 2.0.20, Apache Sling Karaf repoinit 0.2.0, Apache Sling Scripting JSP API Wrapper 1.0.0, Apache Sling Scripting JSP EL Wrapper 1.0.0, Apache Sling Scripting JSP 2.3.0, Apache Sling Testing PaxExam 0.0.4, Apache Sling JCR Oak Server 1.1.4, Apache Sling Scripting Thymeleaf 1.1.0, Apache Sling Resource Presence 0.0.2 (March 20th, 2017) - Apache Sling Resource Resolver 1.5.20, Apache Sling JCR Repoinit 1.1.4 (March 13th, 2017) ----------------------------------------- Attachment BB: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to Board for June 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: Project activity has picked up quite a bit in the past quarter with work proceeding on a new release and the addition of two new committers who are working on our sysadmin/infrastructure needs to resurrect the mass check facility on a new machine. We have set up a new public mailing list sysadmins@ for the latter activity, 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: The board feedback to the last report brought to our attention a private key that was stored on a shared server. There is no reason to believe that anything has been compromised. The key was encrypted and on a private directory. We asked to have the file deleted. We will generate a new signing key for our next release and make sure that we follow best practices in how we secure it. Our old VM was decommissioned before the new machine was running, but we restored essential services fairly quickly and without it being a crisis situation. Most importantly we now have better documentation and an active sysadmin team as a subset of our committer/PMC team. 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. Work has been steadily proceeding this year, and at a faster pace this quarter, on the upcoming 3.4.2 release, however most work has been on completing the migration of the ruleqa/mass-check facility to the new infrastructure. We have completed a triage of issues and port of commits from trunk to the 3.4.2 branch. We expect the release to follow soon after the infrastructure work is completed. Committer/PMC changes: New Committers this quarter: Dave Jones (davej) 26 April 2017 Bryan Vest (bvest) 7 May, 2017 PMC, most recent new member: John Hardin (jhardin) 18 October 2016 ----------------------------------------- Attachment BC: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment BD: 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: - The community is nearing a 1.1.1 maintenance release - Discussions and plans are underway for both the 1.2.0 release as well as what is tentatively being called the 2.0 release - The PMC recently voted to invite an individual as a Committer/PMC Member. Though that individual declined, they have been told the offer stands should they change their mind in the future. That person continues to be very active in the community. - The DataWorks Summit conference this month included 9 sessions featuring Apache Storm - The community is currently discussing adopting a Storm Improvement Proposal (SIP) process similar to the one used by projects such as Kafka and Flink ## Health report: - The community continues to be healthy. There continues to be a steady influx of new faces in both the dev and user communities. ## PMC changes: - Currently 33 PMC members. - No new PMC members added in the last 3 months (1 invited, but declined) - Last PMC addition was Hugo da Cruz Louro on Wed Mar 08 2017 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months (1 invited, but declined) - Last committer addition was Hugo da Cruz Louro at Fri Feb 24 2017 ## Releases: - 1.1.0 was released on Wed Mar 29 2017 ## JIRA activity: - 137 JIRA tickets created in the last 3 months - 92 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BE: Report from the Apache Synapse Project [Isuru Udana] [REPORT] Synapse - June 2017 ## Description: Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. ## Issues: None identified. ## Activity: After the synapse 3.0 major release, there was no major activity happened in the project. Two of the committers were added to the PMC. Now we are planning to do a patch release by fixing some of the identified bugs in the 3.0 release. ## PMC changes: - Currently 27 PMC members. - New PMC members: - Prabath Ariyarathna was added to the PMC on Thu May 04 2017 - Vanjikumaran Sivajothy was added to the PMC on Thu May 04 2017 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Prabath Ariyarathna at Fri Feb 10 2017 ## Releases: - Last release was 3.0.0 on Wed Jan 04 2017 ----------------------------------------- Attachment BF: 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. - We are working towards our first release as a top-level project. ## Health report: - Code contribution is at a healthy level with 342 commits in the last 3 months. - Community growth looks healthy. 1 new PMC member and 4 new contributors in the last 3 months. - Communication at a healthy level. ## 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. ## Mailing list activity: - dev@systemml.apache.org: - 110 subscribers (up 6 in the last 3 months) - 334 emails sent to list (315 in previous quarter) - issues@systemml.apache.org: - 10 subscribers (up 1 in the last 3 months) - 1439 emails sent to list (1077 in previous quarter) ## JIRA activity: - 282 JIRA tickets created in the last 3 months - 217 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BG: 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: - There were some user QnAs, and Tajo PMC responded quickly. ## Health report: - Currently, we are in 'maintain' mode, and there isn't much development. ## PMC changes: - Currently 15 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: - 102 subscribers (up 1 in the last 3 months): - 0 emails sent to list (3 in previous quarter) - issues@tajo.apache.org: - 26 subscribers (up 0 in the last 3 months): - 4 emails sent to list (0 in previous quarter) - user@tajo.apache.org: - 49 subscribers (up 2 in the last 3 months): - 7 emails sent to list (2 in previous quarter) ----------------------------------------- Attachment BH: 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 a little extra traffic project this quarter. A few small fixes. And more community involvement, new contributors and new people offering answers on MLs. No releases were cut, but one remains warranted, and is planned this month. Responsiveness on the ML increased a little this quarter. ## Health report: There are currently two responsive PMC, other PMC help out with votes when needed. There is room to add another committer to the project. ## Issues Further effort is still required to increase health to the project. A past ideas: including the StackExchange traffic digests to dev ML; is being experimented. ----------------------------------------- Attachment BI: 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. ## 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 6.0.51 was released on Thu Mar 16 2017 - Apache Tomcat 6.0.53 was released on Fri Apr 07 2017 - Apache Tomcat 7.0.76 was released on Thu Mar 16 2017 - Apache Tomcat 7.0.77 was released on Sun Apr 02 2017 - Apache Tomcat 7.0.78 was released on Tue May 16 2017 - Apache Tomcat 8.0.42 was released on Tue Mar 14 2017 - Apache Tomcat 8.0.43 was released on Sun Apr 02 2017 - Apache Tomcat 8.0.44 was released on Tue May 16 2017 - Apache Tomcat 8.5.13 was released on Thu Mar 30 2017 - Apache Tomcat 8.5.14 was released on Tue Apr 18 2017 - Apache Tomcat 8.5.15 was released on Wed May 10 2017 - Apache Tomcat 9.0.0.M19 was released on Thu Mar 30 2017 - Apache Tomcat 9.0.0.M20 was released on Tue Apr 18 2017 - Apache Tomcat 9.0.0.M21 was released on Wed May 10 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-5664 The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page. This means that the request is presented to the error page with the original HTTP method. Affects: 9.0.0.M1 to 9.0.0.M20, 8.0.0.RC1 to 8.0.43, 8.5.0 to 8.5.14, 7.0.0 to 7.0.77 - Important: Information Disclosure CVE-2017-5651 The refactoring of the HTTP connectors for 8.5.x onwards, introduced a regression in the send file processing. If the send file processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This could result in the same Processor being used for multiple requests which in turn could lead to unexpected errors and/or response mix-up. Affects: 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12 - Important: Denial of Service CVE-2017-5650 The handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all available processing threads. Affects: 9.0.0.M1 to 9.0.0.M18 - Important: Information Disclosure CVE-2017-5647 A bug in the handling of the pipelined requests when send file was used resulted in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C. Affects: 9.0.0.M1 to 9.0.0.M18, 8.0.0.RC1 to 8.0.42, 8.5.0 to 8.5.12, 7.0.0 to 7.0.76 - Low: Information Disclosure CVE-2017-5648 While investigating bug 60718, it was noticed that some calls to application listeners did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application. Affects: 9.0.0.M1 to 9.0.0.M17, 8.0.0.RC1 to 8.0.41, 8.5.0 to 8.5.11, 7.0.0 to 7.0.75 ----------------------------------------- Attachment BJ: 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 better documentations to attracts more users and contributors to the community ## Health report: - Made one release since Mar 2017 ## PMC changes: - Currently 6 PMC members - Last PMC addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 8 committers and 22 contributors - No new committer added in the last 3 months - No new contributor added in the last 3 months - Last committer addition was Martin Serrano on Feb 24, 2017 - Last contributor addition was Chengfeng Mao on November 18, 2016 ## Releases: - Last release was release 0.11.0 on April 7, 2016 ## Mailing list activity: - dev@twill.apache.org: - 68 subscribers - 360 emails sent to the list in past three months (601 in last report) - commits@twill.apache.org: - 18 subscribers - 125 emails sent to the list in past three months (134 in last report) ## JIRA activity: - 5 new JIRA tickets created in the last month - 1 JIRA tickets resolved in the last month ----------------------------------------- Attachment BK: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for June 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: 04 Apr 2017 (new) last release - Apache UIMA Java SDK 2.10.0 03 May 2016 (no change) last PMC addition 18 Apr 2017 (new) last Committer addition Releases: 04 Apr 2017 Apache UIMA Java SDK 2.10.0 29 Mar 2017 Apache uimaFIT 2.3.0 19 Mar 2017 Apache UIMA Java SDK 3.0.0-alpha02 10 Mar 2017 Apache UIMA Ruta 2.6.0 Activity: All major projects (Java SDK, DUCC, uimaFIT, RUTA, C++) are actively being worked on. The Java SDK version 3 is progressing towards a beta version (after 2 alpha releases). Mailing list activity remains moderate, with people from the extended community helping out by answering questions. Community: The community continues to be moderately active. We added a new committer, who has started work on a release candidate for the C++ version of UIMA. Issues: No Board level issues at this time. ----------------------------------------- Attachment BL: Report from the Apache VCL Project [Andy Kurth] ----------------------------------------- Attachment BM: 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: - We are very pleased to welcome Maxim Solodovnik to our team - 3 releases have been issued - It is 10 years since the Wicket project joined the ASF ## Issues: - there are no issues requiring board attention at the moment ## Activity: - Work is progressing, Wicket 8 should be final soon - Maintenance releases for our supported branches keep coming out - Andrea del Bene has been performing the releases for a while now ## Health report: - As with most web frameworks from 2004 that are still active, the community remains stable - Mailinglist traffic is stable, new team members are found to keep the project fresh and ongoing, JIRA issues are reported and solved. ## PMC changes: - Currently 30 PMC members. - Maxim Solodovnik was added to the PMC on Thu Apr 13 2017 ## Committer base changes: - Currently 31 committers. - Maxim Solodovnik was added as a committer on Thu Apr 13 2017 ## Releases: - 7.7.0 was released on Thu May 18 2017 - 8.0.0-M5 was released on Wed Mar 29 2017 - 8.0.0-M6 was released on Fri May 19 2017 ----------------------------------------- Attachment BN: Report from the Apache Yetus Project [Sean Busbey] ----------------------------------------- Attachment BO: 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: We have completed two releases since March and the community is now working towards the first stable release of the 3.5 branch. There isn’t much to report other than the fact that there is work going on in the community, see for example, mailing list and lira numbers below. ## Health report: Number of subscribers and emails sent to the user/dev lists have grown only slightly. The size of the community has been roughly stable, although the slight growth is an indication of health: we still occasionally get new joiners and the overall numbers aren’t dropping. We are also working with various contributors in the community to get them to a stage that we can offer them committership. We also have just voted a new PMC member, but this PMC Chair hasn’t processed the new member yet. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rakesh Radhakrishnan on Fri Mar 03 2017 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Mohammad Arshad at Tue Jan 24 2017 ## Releases: - 3.4.10 was released on Thu Mar 30 2017 - 3.5.3 was released on Mon Apr 17 2017 ## Mailing list activity: Number of dev subscribers has grown by 2%, while the number of user subscribers has grown by less than 1%. As I have explained in a previous report, typically questions on ZooKeeper are asked in the dev list. In fact, the number of messages sent to the user list is small compared to the dev list. - dev@zookeeper.apache.org: - 517 subscribers (up 10 in the last 3 months): - 3774 emails sent to list (3741 in previous quarter) - user@zookeeper.apache.org: - 1200 subscribers (up 7 in the last 3 months): - 131 emails sent to list (168 in previous quarter) ## JIRA activity: - 86 JIRA tickets created in the last 3 months - 53 JIRA tickets closed/resolved in the last 3 months ------------------------------------------------------ End of minutes for the June 21, 2017 board meeting.