The Apache Software Foundation Board of Directors Meeting Minutes April 20, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:33 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/2zkh 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: Shane Curcuru Bertrand Delacretaz Isabel Drost-Fromm Marvin Humphrey Jim Jagielski Chris Mattmann Brett Porter Greg Stein Mark Thomas Directors Absent: none Executive Officers Present: Rich Bowen Ross Gardler Craig L Russell Executive Officers Absent: Kevin A. McGrail Guests: Bruce Snyder Daniel Gruno Dennis E. Hamilton Gavin McDonald Hadrian Zbarcea Henri Yandell John D. Ament Sam Ruby Sean Kelly - left at 11:17 Sravya Tirukkovalur 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of March 16, 2016 See: board_minutes_2016_03_16.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] Welcome to the new board, elected by the members last month! I’d like to particularly welcome Isabel, Marvin and Mark, each serving as a director for the first time. Our gratitude goes to the outgoing directors Rich, David and Sam for all that they did during their term. Everything went well during the meeting. We elected 58 new members, and will announce them next month after the final paperwork has been received. We also passed a resolution to convert a number of inactive members to emeritus status, but would certainly welcome them back again in the future! Thanks to the STeVe project for their work on a new voting front-end that was used at the meeting. I’ve included my report from the Annual Members Meeting below. ----- It has been another outstanding year for the Apache Software Foundation, marked by continued growth and success of our top-level project communities, and the steady addition of new top-level projects. Since the 2015 Annual Members Meeting, we have added 15 new projects: Parquet, Orc, Whimsy, NiFi, Lens, Ignite, Usergrid, Serf, Yetus, Brooklyn, Calcite, Kylin, Groovy, REEF and Arrow; while 6 existing projects have retired to the Attic: Lenya, DirectMemory, Deltacloud, Shindig, Onami and Rave. Overall we find ourselves with 171 top-level projects, with 45 additional projects under incubation. At the last meeting, we easily met quorum after the challenges the prior year. This is something we will continue to monitor and address through encouraging proxies, and reaching out to inactive members who may be considering emeritus status. Nevertheless, with over 200 members joining it is extremely encouraging to to have such a large number of our members participating in the governance of the Foundation. In 2015, we elected 108 new Members, expanding our representation across the various project communities to a total of 603 members as of February 20. We also elected a new board, with Shane Curcuru returning to the board, and David Nalley joining for the first time. I thank all the directors for their service to the Foundation over the last 12 months! The board has functioned well, bringing diverse opinions but making clear decisions. The board has balanced discussion of Foundation issues with a focus on projects and their reports. We’ve continued to improve tooling in several areas, and formed the Whimsy PMC, in addition to the existing Steve PMC, to build tools that help the Foundation run smoothly. We have seen continued success from our operations, as detailed in the President’s report, and inline with budget. We have made a transition to new staffing arrangements that have increased costs, which will need to be addressed in the budget over the next couple of years. For the first time, the ASF released an Annual Report, a significant effort that helped share specific details of the ASF’s impact with our sponsors and the public. Thank you to the President, EVP, VPs and the committees they work with, many of which expended significant time as volunteers, to keep the Foundation ticking day to day. We also thank Chris Mattmann for his service as Treasurer, as he prepares to transition the role to a new volunteer in the next board year. Through these Foundation-level developments, we support the communities that make up our top-level projects. I can report that the Apache Way continues to show the benefit of community-led development throughout our existing projects, and an attractive reason for other projects to join through the Incubator. I’m pleased that in the last year we have managed to initiate some changes that have a potentially significant cultural impact, while carefully ensuring that we retain the unique Apache DNA. We have had additional projects take advantage of proposing TLPs directly to the board where incubation was not deemed necessary. We have also expanded support for GitHub use by ASF projects, and began experiments through the Whimsy project to assess some of the technical (and later cultural) impact. One of the Foundation’s strengths is that by building communities, we not only build software but also build relationships that extend beyond that development. Therefore, we acutely feel the loss of valued members of the community. It is with great sadness that we saw the passing of Ian Lynch, Nóirín Plunkett, and Adrian Crum in the last year. Their memory, and their contributions, will carry on through our communities, and our thoughts remain with their families and friends. Thank you to the entire ASF community for making it such a wonderful place to contribute, and for the privilege it has been to serve as Chairman. B. President [Ross] Executive Assistant continues to keep critical activities moving in support of our volunteers. Primary focus in the last month has been TAC and ApacheCon. Trademarks has seen a few complex issues in the last month. Shane is working on documentation to assist PMCs seeking to "self-serve". See http://www.apache.org/foundation/marks/templates/ and http://www.apache.org/foundation/marks/guide. Shane is explicitly calling for member feedback, in addition to assistance on clarifying key point sin the existing policy docs (specifically domain name and event branding policies). Fundraising, for the last few months we've been reporting that fundraising was lagging behind budget, but that this was a result of last years budget being averaged across the year, rather than showing actual renewal dates. This month we are ahead of budget since a number of renewals have now been completed. Moving into next year the budget reflects renewal dates rather than an averaged income. The fundraising team will be meeting at ApacheCon to discuss additional improvements to the overall fundraising activities. Marketing and Publicity: Contract renewed with Halo (no increase in fees). Infrastructure: We remain understaffed and it seems that the search committee has made insufficient progress on advertising for a new lead role. I submitted an outline proposal for discussion on 4/1. This involves a significant spend on a lead role for infrastructure. One member of the committee supported the idea in principle (the current VP Infra), one opposed it for lack of detail. Others did not comment, awaiting more detail. This was provided on 4/3, resulting in one more member of the committee explicitly supporting the proposal. We do not yet have consensus and therefore further discussion is required. There are two candidates for backfilling the existing team. I've reached out to David to ask if we ought to seek to back-fill while we look to a longer term plan as a search committee. The board approved the inclusion of 2 new projects in the GitHub enablement experiment. This work is ongoing with Sam Ruby stepping up to help ensure self-service is addressed within the project. Traffic Server has been onboarded and, at the time of writing, no incidents have been raised. Budget: Budget is behind schedule. First lets roll up the previous budget, the forecasted net loss for 2016 was $-160K, with March numbers in the estimated deficit is now $-1.1K. For the forthcoming year I provided proposed budget to all VPs on 4/1 and have received feedback from Marketing, Brand Management, Infrastructure and TAC. There are some outstanding items I need to address, but we are in good shape except that I've been holding off on the final budget while the Infra Lead search committee discuss the proposed budget for this role. However, as noted above this is not moving as quickly as I would like. Therefore, I have submitted a proposed budget without the infrastructure staffing changes included. I ask that the board consider this and approve it (with necessary modifications), by email, ahead of the next board meeting. I will answer questions both in the meeting and by email. Additionally, please see Attachments 1 through 6. Marvin: Are we up against a deadline for replacing VP Infra? Ross: No concerns presently. C. Treasurer [Chris] Wells Fargo is officially closed and the money has been moved to our new account at Citizens. In doing so, we have went through the following checklist of items to shut down: 1. Corporate Credit Cards 2. Direct Pay 3. Wire Transfer 4. Lockbox 5. Safebox This has been a lengthy process and to our knowledge the only remaining service is a corporate credit card of a former Treasurer that is only still open as we are transferring the hefty amount of rewards points off of it into some tangible form before shutting it down. Virtual is assisting with the process. The Treasurer is working with ASF infra to make sure treasurer@ and accounting@ are archived, web-accessible (via mail-search) archives. Chris Mattmann remains the Treasurer until a new Treasurer can be appointed by the Board during Executive Session. Income and Expenses for March 2016 CASH BASIS Current Balances: Mar 2016 Citizens Checking $562,270 Citizens Money Market $1,200,450 Amazon- ASF Payments $- Paypal - ASF $81,913 Wells Fargo Checking - ASF $- Wells Fargo Savings $- Total Checking/Savings $1,844,632 Income Summary: Inkind Revenue $7,167 Public Donations $3,370 Sponsorship Program $308,000 Programs Income $- Interest Income $313 Total Income $318,850 Expense Summary: In Kind Expense $7,167 Infrastructure $48,714 Sponsorship Program $- Programs Expense $- Publicity $5,455 Brand Management $- Conferences $2,009 Travel Assistance Committee $199 Tax and Audit $4,500 Treasury Services $3,100 General & Administrative $8,530 Total Expense $79,674 Net Income $239,176 D. Secretary [Craig] The project to replace missing ICLAs is progressing. 27 entries in iclas.txt with no active account and no ICLA on file were removed. There were two responses to the request to file replacement ICLAs for existing committers, included in the numbers below. In March, 84 iclas, five cclas, 4 grants, and 40 membership applications were received and filed. As of April 20, all invited members from the March member meeting have been accepted as new members. E. Executive Vice President [Rich] With ApacheCon 3 weeks out, I have been spending all of my ASF time promoting that event. This has included a series of podcasts on feathercast.org promoting our speakers, their talks, their projects, and ApacheCon itself. Registration numbers follow (as of Monday, April 18): Apache: Big Data 336 ApacheCon 2016: 265 BarCampApache: 40 Last month I promised an update on ApacheCon Europe. The update is that we're going to have one, but that it will be as lean as possible. This means things like not providing an on-site lunch, not having an off-site reception, and not doing recordings of talks. This is a great opportunity for sponsors to step up to cover these things, if desired. However, I have opted to have an event under these conditions rather than to not have an event at all. We should have some idea of venue soon, and will hopefully be able to announce this at ApacheCon in Vancouver. F. Vice Chairman [Greg] Nothing to report this month. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Isabel] See Attachment 7 B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 8 C. Apache Security Team Project [Mark J. Cox / Brett] See Attachment 9 @Jim: follow up with APR Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # ACE [bp] # ActiveMQ [mh] # Archiva [mt] # Axis [bp] # Celix [bp] # Continuum [bp] # Geronimo [bp] # MINA [mh] # OpenMeetings [mt] # SpamAssassin [bp] # Struts [mt] # Synapse [bp] # Tuscany [bp] # Web Services [mt] A. Apache Accumulo Project [Billie Rinaldi / Shane] See Attachment A B. Apache ACE Project [Marcel Offermans / Chris] No report was submitted. C. Apache ActiveMQ Project [Bruce Snyder / Bertrand] See Attachment C @Bruce: Prepare new report for next month with more information on the health of the project. D. Apache Airavata Project [Suresh Marru / Mark] See Attachment D E. Apache Ant Project [Conor MacNeill / Marvin] See Attachment E F. Apache Archiva Project [Olivier Lamy / Jim] See Attachment F @Jim: Resubmit next month G. Apache Aries Project [Jeremy Hughes / Greg] See Attachment G H. Apache Arrow Project [Jacques Nadeau / Shane] See Attachment H I. Apache Attic Project [Henri Yandell / Brett] See Attachment I J. Apache Avro Project [Ryan Blue / Mark] See Attachment J K. Apache Axis Project [Deepal Jayasinghe / Marvin] No report was submitted. L. Apache Bloodhound Project [Gary Martin / Chris] See Attachment L M. Apache Calcite Project [Julian Hyde / Isabel] See Attachment M N. Apache Celix Project [Alexander Broekhuis / Bertrand] See Attachment N @Bertrand: (Lack of) activity on dev list is a concern. O. Apache Chukwa Project [Eric Yang / Jim] See Attachment O P. Apache Continuum Project [Brent Atkinson / Greg] No report was submitted. @Brett: Put an Attic resolution on next month's agenda. Q. Apache Crunch Project [Micah Whitacre / Greg] See Attachment Q R. Apache CXF Project [Daniel Kulp / Isabel] See Attachment R S. Apache DB Project [Bryan Pendleton / Chris] See Attachment S T. Apache Directory Project [Kiran Ayyagari / Bertrand] See Attachment T U. Apache Geronimo Project [Alan Cabrera / Brett] No report was submitted. @Brett: pursue a report for Geronimo for next month. Is the project still viable, or is another chair needed? V. Apache Hadoop Project [Christopher Douglas / Marvin] See Attachment V W. Apache HBase Project [Andrew Purtell / Mark] See Attachment W X. Apache Helix Project [Kishore Gopalakrishna / Jim] See Attachment X Y. Apache Incubator Project [Ted Dunning / Shane] See Attachment Y Z. Apache Isis Project [Dan Haywood / Chris] See Attachment Z AA. Apache James Project [Eric Charles / Brett] See Attachment AA AB. Apache jclouds Project [Ignasi Barrera / Greg] See Attachment AB AC. Apache Jena Project [Andy Seaborne / Isabel] See Attachment AC AD. Apache JMeter Project [Sebastian Bazley / Jim] See Attachment AD AE. Apache JSPWiki Project [Juan Pablo Santos / Marvin] See Attachment AE AF. Apache Lucene.Net Project [Prescott Nasser / Mark] See Attachment AF AG. Apache Lucy Project [Marvin Humphrey] See Attachment AG AH. Apache Mahout Project [Suneel Marthi / Shane] See Attachment AH AI. Apache Maven Project [Hervé Boutemy / Bertrand] See Attachment AI AJ. Apache Mesos Project [Benjamin Hindman / Shane] See Attachment AJ AK. Apache MINA Project [Jean-François Maury / Mark] See Attachment AK AL. Apache MRUnit Project [Brock Noland / Jim] No report was submitted. AM. Apache MyFaces Project [Mike Kienenberger / Isabel] See Attachment AM AN. Apache NiFi Project [Joe Witt / Chris] See Attachment AN AO. Apache Nutch Project [Sebastian Nagel / Brett] See Attachment AO AP. Apache ODE Project [Tammo van Lessen / Greg] See Attachment AP AQ. Apache OpenJPA Project [Pinaki Poddar / Bertrand] See Attachment AQ AR. Apache OpenMeetings Project [Maxim Solodovnik / Marvin] See Attachment AR AS. Apache OpenOffice Project [Dennis E. Hamilton / Jim] See Attachment AS AT. Apache ORC Project [Owen O'Malley / Greg] See Attachment AT AU. Apache Parquet Project [Julien Le Dem / Bertrand] See Attachment AU AV. Apache PDFBox Project [Andreas Lehmkühler / Marvin] See Attachment AV AW. Apache Samza Project [Chris Riccomini / Brett] See Attachment AW AX. Apache Sentry Project [Sravya Tirukkovalur / Isabel] See Attachment AX AY. Apache SpamAssassin Project [Kevin A. McGrail / Mark] No report was submitted. @Mark: pursue a report for SpamAssassin AZ. Apache Sqoop Project [Jarek Jarcec Cecho / Chris] See Attachment AZ BA. Apache Steve Project [Daniel Gruno / Shane] See Attachment BA BB. Apache Struts Project [René Gielen / Shane] See Attachment BB BC. Apache Synapse Project [Hiranya Jayathilaka / Brett] No report was submitted. @Brett: help Synapse in its move to the Attic. BD. Apache Tajo Project [Hyunsik Choi / Jim] See Attachment BD BE. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Marvin] See Attachment BE BF. Apache Tcl Project [Massimo Manghi / Greg] See Attachment BF BG. Apache Tez Project [Siddharth Seth / Isabel] See Attachment BG BH. Apache Thrift Project [Jake Farrell / Mark] See Attachment BH BI. Apache Tika Project [Dave Meikle / Chris] See Attachment BI BJ. Apache TomEE Project [David Blevins / Bertrand] See Attachment BJ BK. Apache Traffic Server Project [Leif Hedstrom / Bertrand] See Attachment BK BL. Apache Tuscany Project [Jean-Sebastien Delfino / Shane] No report was submitted. @Shane: help Tuscany in its move to the Attic BM. Apache VXQuery Project [Till Westmann / Brett] See Attachment BM BN. Apache Web Services Project [Sagara Gunathunga / Greg] See Attachment BN @Greg: The report continues to be unacceptable. Time for a new chair? BO. Apache Whimsy Project [Sam Ruby / Isabel] See Attachment BO Committee reports approved as submitted by General Consent. 7. Special Orders A. Terminate the Apache MRUnit Project WHEREAS, the Project Management Committee of the Apache MRUnit project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache MRUnit project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache MRUnit project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache MRUnit Project; and be it further RESOLVED, that the office of "Vice President, Apache MRUnit" is hereby terminated; and be it further RESOLVED, that the Apache MRUnit PMC is hereby terminated. Special Order 7A, Terminate the Apache MRUnit Project, was approved by Unanimous Vote of the directors present. B. Change the Apache Labs Project Chair WHEREAS, the Board of Directors heretofore appointed Jan Iversen (jani) to the office of Vice President, Apache Labs, and WHEREAS, the Board of Directors is in receipt of the resignation of Jan Iversen from the office of Vice President, Apache Labs, and WHEREAS, the Project Management Committee of the Apache Labs project has chosen by vote to recommend Danny Angus (danny) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jan Iversen is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Labs, and BE IT FURTHER RESOLVED, that Danny Angus be and hereby is appointed to the office of Vice President, Apache Labs, 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 Labs Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache TinkerPop 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 graph computing framework for graph databases and graph analytic systems NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache TinkerPop Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache TinkerPop Project be and hereby is responsible for the creation and maintenance of software related to a graph computing framework for graph databases and graph analytic systems; and be it further RESOLVED, that the office of "Vice President, Apache TinkerPop" 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 TinkerPop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache TinkerPop 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 TinkerPop Project Management Committee: * Daniel Gruno * Daniel Kuppitz * James Thornton * Hadrian Zbarcea * Marko Rodriguez * Stephen Mallette * Ted Wilmes NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen Mallette (spmallette) be appointed to the office of Vice President, Apache TinkerPop, 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 TinkerPop 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 TinkerPop Project; and be it further RESOLVED, that the Apache TinkerPop Project be and hereby is tasked with the migration and rationalization of the Apache Incubator TinkerPop podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator TinkerPop podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache TinkerPop Project, tabled @Jim: discuss board's concerns with the TinkerPop community. D. Establish the Apache Apex 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 distributed, large-scale, high throughput, low-latency, fault tolerant, unified stream and batch processing platform for Apache Hadoop. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Apex Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Apex Project be and hereby is responsible for the creation and maintenance of software related to distributed, large-scale, high throughput, low-latency, fault tolerant, unified stream and batch processing platform for Apache Hadoop; and be it further RESOLVED, that the office of "Vice President, Apache Apex" 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 Apex Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Apex 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 Apex Project: * Ilya Ganelin * P. Taylor Goetz * Gaurav Gupta * Pramod Immaneni * Amol Kekre * Justin Mclean * Chetan Narsude * Chris Nauroth * Vlad Rozov * Hitesh Shah * Thomas Weise * David Yan * Brennon York NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise (thw) be appointed to the office of Vice President, Apache Apex, 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 Apex 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 Apex Project; and be it further RESOLVED, that the Apache Apex Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Apex podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Apex podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7D, Establish the Apache Apex Project, was approved by Unanimous Vote of the directors present. E. Establish the Apache Johnzon 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 JSR-353 compliant JSON parsing and a set of useful modules to help with the usage of JSR-353 as well as JSR successors (like JSR-374) or related JSRs (like JSR-367). NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Johnzon Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Johnzon Project be and hereby is responsible for the creation and maintenance of software related to JSR-353 compliant JSON parsing and a set of useful modules to help with the usage of JSR-353 as well as JSR successors (like JSR-374) or related JSRs (like JSR-367); and be it further RESOLVED, that the office of "Vice President, Apache Johnzon" 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 Johnzon Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Johnzon 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 Johnzon Project: * Justin Mclean * Romain Manni-Bucau * Jean-Louis Monteiro * Mark Struberg * Hendrik Saly NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hendrik Saly (salyh) be appointed to the office of Vice President, Apache Johnzon, 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 Johnzon 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 Johnzon Project; and be it further RESOLVED, that the Apache Johnzon Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Johnzon podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Johnzon podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7E, Establish the Apache Johnzon Project, was approved by Unanimous Vote of the directors present. F. Establish AsterixDB 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 parallel distributed data management technologies for semi-structured data, NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache AsterixDB Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache AsterixDB Project be and hereby is responsible for the creation and maintenance of software related to parallel distributed data management technologies for semi-structured data; and be it further RESOLVED, that the office of "Vice President, Apache AsterixDB" 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 AsterixDB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache AsterixDB 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 AsterixDB Project: * Abdullah Alamoudi * Ate Douma * Cameron Samak * Chen Li * Chris Hillery * Chris Mattmann * Heri Ramampiaro * Ian Maxon * Ildar Absalyamov * Jianfeng Jia * Jochen Wiedmann * Keren Ouaknine * Michael Blow * Michael J. Carey * Murtadha Hubail * Pouria Pirzadeh * Preston Carman * Raman Grover * Sattam Alsubaiee * Steven Jacobs * Taewoo Kim * Ted Dunning * Till Westmann * Vassilis Tsotras * Vinayak Borkar * Yingyi Bu * Young-Seok Kim * Zach Heilbron NOW, THEREFORE, BE IT FURTHER RESOLVED, that Till Westmann (tillw) be appointed to the office of Vice President, Apache AsterixDB, 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 AsterixDB 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 AsterixDB Project; and be it further RESOLVED, that the Apache AsterixDB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator AsterixDB podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator AsterixDB podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7F, Establish AsterixDB, was approved by Unanimous Vote of the directors present. G. Change the Apache OpenJPA Project Chair WHEREAS, the Board of Directors heretofore appointed Pinaki Poddar (ppoddar) to the office of Vice President, Apache OpenJPA, and WHEREAS, the Board of Directors is in receipt of the resignation of Pinaki Poddar from the office of Vice President, Apache OpenJPA, and WHEREAS, the Project Management Committee of the Apache OpenJPA project has chosen by vote to recommend Mark Struberg (struberg) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Pinaki Poddar is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache OpenJPA, and BE IT FURTHER RESOLVED, that Mark Struberg be and hereby is appointed to the office of Vice President, Apache OpenJPA, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7G, Change the Apache OpenJPA Project Chair, was approved by Unanimous Vote of the directors present. H. Change the Apache Mahout Project Chair WHEREAS, the Board of Directors heretofore appointed Suneel Marthi (smarthi) to the office of Vice President, Apache Mahout, and WHEREAS, the Board of Directors is in receipt of the resignation of Suneel Marthi from the office of Vice President, Apache Mahout, and WHEREAS, the Project Management Committee of the Apache Mahout project has chosen by vote to recommend Andrew Palumbo (apalumbo) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Suneel Marthi is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Mahout, and BE IT FURTHER RESOLVED, that Andrew Palumbo be and hereby is appointed to the office of Vice President, Apache Mahout, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7H, Change the Apache Mahout Project Chair, was approved by Unanimous Vote of the directors present. I. Change the Apache Crunch Project Chair WHEREAS, the Board of Directors heretofore appointed Micah Whitacre (mkwhit) to the office of Vice President, Apache Crunch, and WHEREAS, the Board of Directors is in receipt of the resignation of Micah Whitacre from the office of Vice President, Apache Crunch, and WHEREAS, the Project Management Committee of the Apache Crunch project has chosen by vote to recommend Josh Wills (jwills) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Micah Whitacre is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Crunch, and BE IT FURTHER RESOLVED, that Josh Wills be and hereby is appointed to the office of Vice President, Apache Crunch, 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 7I, Change the Apache Crunch Project Chair, was approved by Unanimous Vote of the directors present. J. Change the Apache Bigtop Project Chair WHEREAS, the Board of Directors heretofore appointed Andrew Purtell (apurtell) to the office of Vice President, Apache Bigtop, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrew Purtell from the office of Vice President, Apache Bigtop, and WHEREAS, the Project Management Committee of the Apache Bigtop project has chosen by vote to recommend Olaf Flebbe (oflebbe) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrew Purtell is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Bigtop, and BE IT FURTHER RESOLVED, that Olaf Flebbe be and hereby is appointed to the office of Vice President, Apache Bigtop, 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 7J, Change the Apache Bigtop Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Timing of Executive Officer Appointments 9. Review Outstanding Action Items * David: follow up with last PMC and committer additions. [ Santuario 2015-05-20 ] Status: * David: Finalise move to the Attic [ Tuscany 2015-06-17 ] Status: No emails on private@, dev@, user@ even after announcement they were likely moving to Attic. +1 to move to Attic -sc * Brett: pursue a report for Continuum [ Continuum 2015-12-16 ] Status: didn't get to this last month - will propose the Attic for May * Ross: Notify PMC that tools are available to aid in the Apache Extras [ Pivot 2015-12-16 ] Status: * Shane: Contact PMC to get a better report next month; make sure to read the guidelines [ Web Services 2016-02-17 ] Status: Email sent; private@ list shows slight activity (voted in new PMC member recently); dev@ lists are definitely active. -sc * Brett: Add another reminder to tardy projects the Monday before the meeting [ Discussion Items 2016-02-17 ] Status: will send again, but didn't get a chance to add to Whimsy * Brett: pursue a report for Ant [ Ant 2016-03-16 ] Status: present this month * Shane: pursue a report for Bloodhound [ Bloodhound 2016-03-16 ] Status: Bloodhound will submit a report saying they're likely to vote for Attic for May board meeting. -sc * Bertrand: Work with PMC to get a better report for next quarter [ Groovy 2016-03-16 ] Status: * Rich: Work with PMC to get a better report next quarter [ Hive 2016-03-16 ] Status: * Rich: Communicate to the PMC that the competitive analysis vs. vs. hazelcast is inappropriate [ Ignite 2016-03-16 ] Status: complete per RB * Sam: Get more (actionable) information on github fork [ CloudStack 2016-03-16 ] Status: I saw no evidence of an intent to fork externally; this was confirmed retroactively with a vote thread. What I did see was an intent to find a solution to an infrastructure issue (auth granularity) which affects their ability to set up, configure, and maintain travis. * Shane: Suggest ways to improve the board report; especially the the "Health" section [ Tiles 2016-03-16 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:26 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] ApacheCon and TAC: TAC: * After receiving a record-breaking number of applications (48), 19 were accepted (this includes the folks that were accepted after the Board agreed to increase the budget, as well as the LF-funded folks [3]). One applicant dropped out of the LF-funding due to indecision; we’ve advised the LF re this since he is a speaker. * All flights have been secured and sent to the applicants * All rooms have been secured and confirmation numbers sent to the applicants * All visa invitation letters have been sent to the applicants * I continue to field and respond to the applicants’ queries * Hotel invoice and flights reimbursement have been submitted to svn and accounting@ is doing an out-of-cycle payment for this and the flights – thank you, Accounting Team!! ApacheCon: * Made hotel reservations, conference registrations, and in one case, made flight arrangements for the Infra folks * Collaborating with the LF personnel re booth logistics, shipping logistics, etc. * Order placed for the giveaways Fundraising: * Hope to meet up with the VPs of Fundraising at ACNA’16 to discuss the problems w/in the fundraising system Trademarks: * Due to my time commitment to TAC, Trademarks have fallen behind on my end, but luckily, Shane has been staying on top of the issues. ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] Several significant brand issues reported this month which unfortunately show that PMC awareness and capability to deal with trademark problems varies widely. In particular, the lack of timely response and thoughtful analysis in two situations is disappointing, where issues that should have either been dealt with, or at least attracted attention from the PMC still aren't resolved. One of these involved a third party showing clear confusion as to the source of our software product; instead of contacting the Apache project directly, they had been contacting another software vendor with questions about our software. This specific case is not the real issue; the real issue is ensuring that PMCs as a whole can consistently and fairly act to police their brands, especially when PMC members work for the vendors potentially causing issues. To help ensure guidelines are sufficiently clear, I'm working on much more detailed explanations as well as asking for reviews and feedback on documentation on trademarks@. In the spirit of self-service, proposed template(s) for contacting third parties and guidelines for how to properly refer to Apache project names are now published: http://www.apache.org/foundation/marks/templates/ http://www.apache.org/foundation/marks/guide (draft) I would love to see more Member feedback on these over on trademarks@, as well as thoughtful and specific suggestions for clarifying the Domain Name and Event Name branding policies to ensure that PMCs can apply them more easily and consistently. To help test these guidelines, I will be using them to contact a number of companies misusing our Hadoop brand in their software products shortly. Met with DLAPiper counsel to ensure they are addressing a number of outstanding applications and legal questions, including a review of the OpenOffice PMC's proposed repackaging license Submitted formal trademark complaints to the Microsoft store in relation to third party software using our OpenOffice registered trademarks. At the request of PMCs: Renewed OPENOFFICE.ORG US registration; TOMCAT US application was finalized; provided responses to USPTO office actions for FLINK and PDFBOX applications. Several US and international registrations are preparing for applications. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising continues with no significant issues or challenges. As I mentioned in the past reports and shown in Tom's (Virtual) report, most of the sponsorships get renewed in the spring. As of now we beat the street estimates and are ahead of the plan in the last month of the fiscal year. This is due as mentioned in the other report to one payment ahead of a Platinum sponsor, but is also in spite of loosing a few sponsors this year. I am now working on being more persistent with companies that indicated that are considering becoming sponsors so that we avoid loosing some ground next year. For that Melissa planned to meet with me and Jim in Vancouver next month. I hope to have a few conversations with Ross as well. I also have a call scheduled with Tom and Lynsey (Virtual) for Wednesday (after the Board meeting) to go over the process and see what works well and what would need improvement. All in all, this was a good fiscal year for Fundraising and I would like to thank the many ASF members who helped out. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: as we close out the fiscal year, we remain within budget, with no outstanding invoices due at this time. The FY2017 Marketing & Publicity budget was submitted to President Ross Gardler, who has authorized the contract renewal with HALO Worldwide for ASF's communication services. II. Fundraising/Branding/Marketing/ComDev liaison: Sally Khudairi is beginning to plan the second ASF Annual Report, which will be issued the last week of May. The tasklist for the ongoing rollout of the new ASF logo continues to grow; the aim is to complete as much as possible in time for the upcoming ApacheCon. Sally is also working on fulfillment of a corporate order for various Apache project stickers, which will be paid for by the requesting organization. III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 21 March 2016 --The Apache® Software Foundation announces Apache PDFBox™ v2.0 IV. Informal Announcements: 9 items were published on the ASF "Foundation" Blog, including a post co-authored by Sally and ASF Chairman Brett Porter in celebration of the ASF's 17th Anniversary. 22 items were Tweeted on @TheASF. 5 Apache News Round-ups were issued, with a total of 85 weekly summaries published to date. No new videos have been added to the ASF YouTube channel; we will see if the will be the opportunity to showcase anything from next month's Apache: Big Data and ApacheCon events. V. Future Announcements: one announcement is actively in development, with two on hold as their respective PMCs are preparing for new version releases. 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 welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: Sally continues to counsel several vendors regarding their involvement with various Apache projects. She has invited ASF Members, Apache Committers, and PMCs to attend the media/analyst trainings that will be offered free-of-charge during ApacheCon. Stephen O'Grady of RedMonk will serve as our analyst during the trainings. As of this writing, the sessions are close to reaching capacity. Over the past month, the ASF received 662 press clips vs. last month's clip count of 1,095. VII. Analyst Relations: Apache was mentioned in 20 reports by Gartner, 13 reports by Forrester, 11 reports by 451 Research, and 17 reports by IDC. VIII. ApacheCon liaison: Sally continues to help promote ApacheCon and Apache: Big Data in partnership with the Linux Foundation, and is working with Melissa Warnkin regarding orders for promotional items. IX. (Non-ASF) Industry Events and Outreach liaison: aside from advising projects and organizations on providing the proper ASF attribution, no formal activities are taking place at this time. X. Newswire accounts: we have 45 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] Short Term Priorities: ====================== - Ensuring/monitoring that the dual git repository setup works as intended. - Provision an isolated test environment (including isolated LDAP) for developing/testing services faster than is currently possible, under a separate domain (asfplayground.org). We believe this separation will also help projects and volunteers work on their ideas, such as the Syncope trial, as they can then develop and test without interfering with production systems. - Looking at deploying Apache Traffic Server to help alleviate the troubled BugZilla instances and possibly JIRA. Long Range Priorities: ====================== - Mailing list system switchover is expected to happen in the coming months. We are aware of a few outstanding mail-search requests that we have concluded could be solved out-of-the-box by this. - VMs on Eirene, Nyx and Erebus to be moved in readiness for their decommission - Further explore identity management proposals General Activity: ================= - git-dual has been fully puppetized and is ready for more extensive testing. - Traffic Server has joined the git-dual experiment, so far without incident. - Due to severe abuse, we had to take our European archive server offline and make extensive restrictions on our US archive. We also had to put the US archive in maintenance mode for a few days in order to relocate it to a new machine that can better handle the load (and isn't 5 years old). - Following concerns raised on infrastructure@ about the loss of history due to the migration of people.a.o to a new host not including the contents of committer's public_html directories, an infrastructure volunteer stepped forward to automate the copying of this data. Of the original ~500GB, around 80% was inappropriate (RCs, Maven repos, nightly builds) and was filtered out. There have been no further concerns raised since the copy of the remaining ~110GB was completed. Ticket Response and Resolution Targets: ======================================= Stats for the current reporting cycle can be found at https://status.apache.org/sla/jira/?cycle=2016-04 The tentative goal of having 90% of all tickets fully resolved in time is still being used. Compared to March, we have had slightly more tickets opened, and the percentage of tickets that hit our SLA is lower, as we are essentially 2 full time staffers fewer than we were in March. Quick April reporting cycle summary: - 230 tickets opened - 228 tickets resolved - 248 tickets applied towards our SLA - Average time till first response: 13 hours (up from 6h in Feb-Mar) - Average time till resolution: 44 hours (up from 23h in Feb-Mar) - Tickets fully handled in time: 90% (204/227) Uptime Statistics: ================== Uptime is not pretty this month, but this is primarily an aesthetic issue. The biggest failure here has been keeping LDAP servers in sync, as we have a specific LDAP server in PNAP that keeps going 10 minutes out of sync with the rest. We are looking into why this happens, but so far we have not been able to determine the true cause. Nonetheless, this does not mean LDAP has been down or unresponsive, merely out of sync on one node. As mentioned earlier, we also had to pull the EU archive due to massive abuse, primarily from some EC2 instances and other external datacenters. We are working with the data centers in question to resolve the issue, and have also imposed a new 5GB daily download limit per IP on the new archive machine. Preliminary data suggests this new limit has reduced the traffic from archive.apache.org by as much as 65% (going from around 3TB/day to 1.1TB/day), further suggesting that the bulk of traffic from that service is to poorly configured VMs or other CI systems that should never have been using the archive in the first place. As the machine that hosted the archive also hosts the moin wiki and mail archives, we believe that these services will now perform better, in lieu of archives.a.o moving. For detailed statistics, see http://status.apache.org/sla/ ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Nick Burch] ----------------------------------------- Attachment 7: Report from the VP of W3C Relations [Andy Seaborne] Noting to report for this month or last month. ----------------------------------------- Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski] JIRA issues continue to be addressed with support from the entire team. I have had some emails related to questions about our iCLAs and CCLAs regarding clarification of intent. Have had issues related to scheduling for one specific entity to address their questions and concerns. No issues requiring board attention. ----------------------------------------- Attachment 9: Report from the Apache Security Team Project [Mark J. Cox] A little progress has been made reviewing historical reports. We have now gone back as far as mid-March 2015. The current intention is to continue back into 2014 but how far back will be determined by the rate at which overlooked issues are uncovered. The security team has been evaluating https://srcclr.com/. While it is an improvement on similar tools and has enabled a handful of projects to indentify vulnerable dependencies, it currently lacks the features required for it to be useful without being overly burdensome at the ASF. These features are expected to be made available shortly at which point the security team will re-evaluate. The security team is currently tracking 72 open issues. Not all of these have been confirmed as valid and it is likely some will be rejected. Some TLPs have failed to respond to vulnerability reports and/or requests from the security team for updates. Stats for Mar 2016: 15 CVEs issued to projects (some may not be public yet). Just over 1000 e-mails to security@ 2 Support questions 6 Questions about published security vulnerabilities 3 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to Android licenses 11 Direct Vulnerability report to security@apache.org 1 [activemq] 1 [cocoon] 1 [commons] 1 [httpd] 1 [jspwiki] 1 [mina] 1 [openmeetings] 1 [qpid] 1 [shiro] 1 [tomcat] 1 [tomee] 14 Vulnerabilities reported to projects 1 [apex] 1 [cloudstack] 1 [hadoop] 5 [httpd] 5 [struts] 1 [trafficserver] ----------------------------------------- Attachment A: Report from the Apache Accumulo Project [Billie Rinaldi] The Apache Accumulo sorted, distributed key/value store is a robust, scalable, high performance data storage system that features cell-based access control and customizable server-side processing. It is based on Google's BigTable design and is built on top of Apache Hadoop, Zookeeper, and Thrift. Summary The project is active and there are no Board-level issues at this time. We have added one new committer / PMC member and made two new releases since the previous report. We have had some discussion about whether the community is stagnating and how we could attract the interest of new developers. Releases Version 1.7.1 was released on 2/26/2016. Version 1.6.5 was released on 2/17/2016. Activity The number of subscribers to the user and dev lists have both increased slightly and mailing lists remain active. In the past 3 months, there have been 155 commits to the master branch from 12 authors, 5 of whom are not yet committers. Versions 1.7.1 and 1.6.5 have been released and we have not yet begun planning for the next major release. The PMC has approved the use of the Apache Accumulo mark for the next Accumulo Summit, to be held in October 2016. Community Michael Wall was added as a committer and PMC member on 4/11/2016. ----------------------------------------- Attachment B: Report from the Apache ACE Project [Marcel Offermans] ----------------------------------------- Attachment C: Report from the Apache ActiveMQ Project [Bruce Snyder] ## Description: - Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0. ## Issues: - No issues ## Activity: - Apache ActiveMQ Artemis has been working towards adding ActiveMQ 5.x equivalent features and client compatibility improvements: - The OpenWire protocol module has been completely refactored, improvements include: - Improved message encoding support with increased performance - Cluster connections can now be configured using ActiveMQ 5.x style URI - Equivalent implementations of all ActiveMQ 5.x JAAS modules are now available in Artemis - Artemis has initial support for database backed Journal. - Various improvements and bug fixes to: - HA Replication, STOMP protocol module, File Journal Storage ## Health report: - No issues ## PMC changes: - Currently 22 PMC members. - New PMC members: - Christopher Shannon was added to the PMC on Sun Jan 24 2016 - Jeff Genender was added to the PMC on Sun Jan 24 2016 ## Committer base changes: - Currently 56 committers. - New commmitters: - Matt Richard Hogstrom was added as a committer on Thu Jan 28 2016 - John Robert Sisson was added as a committer on Thu Jan 28 2016 ## Releases: - 5.13.1 was released on Thu Feb 04 2016 - 5.13.2 was released on Thu Mar 03 2016 - ActiveMQ-CPP v3.9.3 was released on Wed Mar 30 2016 - Activemq-CPP v3.9.2 was released on Sun Feb 07 2016 - Apache.NMS.ActiveMQ v1.7.2 was released on Wed Apr 06 2016 ## Mailing list activity: - users@activemq.apache.org: - 727 subscribers (up 12 in the last 3 months): - 930 emails sent to list (770 in previous quarter) - dev@activemq.apache.org: - 352 subscribers (up 11 in the last 3 months): - 666 emails sent to list (717 in previous quarter) - announce@activemq.apache.org: - 9 subscribers (up 0 in the last 3 months) - issues@activemq.apache.org: - 37 subscribers (up 6 in the last 3 months): - 1910 emails sent to list (1780 in previous quarter) ## JIRA activity: - 276 JIRA tickets created in the last 3 months - 240 JIRA tickets closed/resolved in the last 3 months @Marvin: Please elaborate about the health of the community, particularly with regards to the direction taken after the architectural debates. @Bruce: No significant turmoil over the last year after settling the architecural issues. No recent departures of any community members. ----------------------------------------- Attachment D: Report from the Apache Airavata Project [Suresh Marru] Apache Airavata is a distributed system software framework to manage simple to composite applications with complex execution and workflow patterns on diverse computational resources. ## Issues: There are no issues requiring board attention at this time ## Activity: The community has been active. There are designed floating around for a face lift of the website and logo to align with new ASF logo. We hope to roll this out by the time of ApacheCon. ## Health report: As with previous years Airavata has attracted around 10 GSoC applications. We had enough mentors to mentor all these projects but tried to restrict to 3 or 4 to pave way for other PMC’s to take advantage of new contributors. Following previous years students, we are hoping a fraction of the contributors will stick around beyond GSOC and eventually become part of the PMC. ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Supun Nakandala on Mon May 18 2015 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Hasini Gunasinghe at Mon Aug 10 2015 ## Releases: The last release of Apache Airavata 0.15 was made in previous quarter. We prepared for Airavata 0.16 release this quarter and expecting it to be out in the next few weeks. - 0.15 was released on Fri Dec 04 2015 ## Mailing list activity: The communication on the mailing lists remain high. The high increase in dev list communication is largely attributed to GSOC student applications. - users@airavata.apache.org: - 101 subscribers (down -4 in the last 3 months): - 50 emails sent to list (80 in previous quarter) - dev@airavata.apache.org: - 143 subscribers (up 1 in the last 3 months): - 366 emails sent to list (106 in previous quarter) - architecture@airavata.apache.org: - 72 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@airavata.apache.org: - 18 subscribers (up 0 in the last 3 months): - 482 emails sent to list (201 in previous quarter) ## JIRA activity: - 64 JIRA tickets created in the last 3 months - 73 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment E: Report from the Apache Ant Project [Conor MacNeill] My apologies for missing the regular reporting schedule. Apache Ant is a Java based build tool along with associated tools. It consists of 4 main projects: - Ant core and libraries (Antlibs) - Ivy - Ant based dependency manager - IvyDE - Eclipse plugin to integrate Ivy into Eclipse - EasyAnt - Ant and Ivy toolbox to support build processes o Release Status - Ant 1.9.6 followed on July 3, 2015 and is the current release - Ivy 2.4.0 was released on December 26, 2014 - Ivy-DE 2.2.0 was released on November 22, 2013 - EasyAnt The current release is still from the Incubator 0.9-Incubating. o Committers and PMC Jean-Louis Boudart was added to the PMC on Dec 6th, 2013 Stephen Haberman was made a committer on October 12th, 2015 o Community We have decided to have future Ant releases require Java 8. Ant 1.10.0 will be the first such release. Any further Ant 1.9.x releases will continue to require Java 5. An Ant 1.9.7 is being discussed presently. I would expect an Ant 1.10.0 tofollow, albeit after some time. Our addition of a new committer, Stephen Haberman, for improved Ivy response has not been that effective. Some of that is due to some difficulties in getting Stephen’s existing Apache account reactivated as all his old email addresses are no longer active. For now, we will continue to monitor the Ivy situation. Jan Materne ran the reporter tool which I have not used to date but I thought the mailing list stats were interesting  - dev@ant.apache.org:     - 300 subscribers (down -1 in the last 3 months):     - 90 emails sent to list (51 in previous quarter)  - ivy-user@ant.apache.org:     - 365 subscribers (down -2 in the last 3 months):     - 14 emails sent to list (23 in previous quarter)  - notifications@ant.apache.org:     - 63 subscribers (down -3 in the last 3 months):     - 179 emails sent to list (132 in previous quarter)  - user@ant.apache.org:     - 718 subscribers (down -4 in the last 3 months):     - 30 emails sent to list (17 in previous quarter) I will have a look at this in future reports to see if there are any obvious trends which are noteworthy. The project is obviously quiet. reporter.a.o suggested that maybe hedgehogs took over the project which I couldn’t discount. ----------------------------------------- Attachment F: 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: - Small number of bug fixed ## Health report: - Low activity at the moment ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Baptiste Onofre on Fri Jul 11 2014 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Sascha Vogt at Mon Jul 14 2014 ## Releases: - Last release was 2.2.0 on Mon Mar 02 2015 ## Mailing list activity: - users@archiva.apache.org: - 233 subscribers (up 1 in the last 3 months): - 18 emails sent to list (18 in previous quarter) - dev@archiva.apache.org: - 104 subscribers (up 1 in the last 3 months): - 10 emails sent to list (36 in previous quarter) - issues@archiva.apache.org: - 36 subscribers (down -1 in the last 3 months): - 108 emails sent to list (27 in previous quarter) - notifications@archiva.apache.org: - 13 subscribers (up 0 in the last 3 months): - 8 emails sent to list (15 in previous quarter) ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 61 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment G: Report from the Apache Aries Project [Jeremy Hughes] # Description: Apache Aries delivers a set of pluggable Java components enabling an enterprise OSGi application programming model. ## Issues: - There are no issues requiring board attention at this time ## Activity: - New module: Aries Remote Service Admin seeded from Apache CXF DOSGi for providing an implementation of the OSGi Remote Service Admin specification with pluggable transports. http://aries.apache.org/modules/rsa.html - New module: Aries Transaction Control Service. An implementation of the in development RFC221 at the OSGi Alliance. - 8 releases since the last report in January ## Health report: - Mailing list discussion and project contributions continue to be healthy. ## PMC changes: - Currently 37 PMC members. - No new PMC members added in the last 3 months Last PMC addition was Christian Schneider on Fri Apr 10 2015 ## Committer base changes: - Currently 49 committers. - No new committers added in the last 3 months - Last committer addition was Sam Bratton at Mon Dec 21 2015 ## Releases: - Aries JPA container (jpa-container) 1.0.4 2016-03-08 - Apache Aries Proxy Service (proxy-impl) 1.0.5 2016-03-25 - Apache Aries JMX Core (jmx-core) 1.1.6 2016-03-25 - Aries Blueprint Core (blueprint-core) 1.6.0 2016-03-25 - Aries Blueprint Spring Support (blueprint-spring) 0.2.0 2016-03-25 - Aries Blueprint Spring Extender Support (blueprint-spring-extender) 0.2.0 2016-03-25 - Aries Blueprint no-OSGI (blueprint-noosgi) 1.1.2 2016-03-25 - Aries Blueprint CM (blueprint-cm) 1.0.8 2016-03-25 ## Mailing list activity: - dev@aries.apache.org: - 131 subscribers (down -4 in the last 3 months): - 488 emails sent to list (527 in previous quarter) - user@aries.apache.org: - 236 subscribers (up 0 in the last 3 months): - 37 emails sent to list (37 in previous quarter) ## JIRA activity: - 44 JIRA tickets created in the last 3 months - 50 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment H: Report from the Apache Arrow Project [Jacques Nadeau] ## Description: Arrow is a columnar in-memory analytics layer designed to accelerate big data. It houses a set of canonical in-memory representations of flat and hierarchical data along with multiple language-bindings for structure manipulation. It also provides IPC and common algorithm implementations. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - A number of public presentations have been done about Arrow including at Strata SJ, Hadoop Summit Europe and various meetups. Response at each was strong and we saw subsequent increased interaction on the mailing list. - We've seen a great new project Feather, a collaboration between the Python and R communities build on top of Arrow to provide an ephemeral cross system format that performs faster and has better typing than the traditionally used CSV format. - A number of interested organizations have posted blogs about their interest in and support for Arrow. ## Health report: - We continue to see new community members engage. - Public discussions and contributions from both committers and casual contributors continue to improve the Arrow specification. - We're working with the incubating Mnemonic community to support alternatives to ephemeral memory for storing Arrow vectors. This will likely first appear as an optional extension module of the Java api. - We're still negotiating the final Arrow switch over in the Drill community. The goal is to do it as part of the 2.0 branch to avoid any disruption to the active stable branch (master). ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 20 committers. - Most recently added committers: - Ippokratis Pandis was added as a committer on Thu Feb 18 2016 - David Alves was added as a committer on Wed Feb 17 2016 - Wes McKinney was added as a committer on Mon Feb 01 2016 ## Releases: - No releases yet. ## JIRA activity: - 100 JIRA tickets created in the last 3 months - 67 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment I: Report from the Apache Attic Project [Henri Yandell] ## Description: - The Attic is where projects slumber when their communities fade away. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Onami, Rave and Wookie were all moved to the Attic in this quarter, along with some website fixes. There are no open issues to retire projects currently. ## Health report: - We're retiring what needs retiring with little on the backlog. The project is as healthy as needed. ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Herve Boutemy on Sat Jul 18 2015 ## Committer base changes: - Currently 24 committers. - New commmitters: - Herve Boutemy was added as a committer on Wed Jan 27 2016 - Henk P. Penning was added as a committer on Wed Jan 27 2016 - Sebastian Bazley was added as a committer on Wed Jan 27 2016 ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment J: Report from the Apache Avro Project [Ryan Blue] ## Description: - Avro is a cross-language data serialization system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - 1.8.0 released on 29 January 2016. - The latest release brings the project's licensing documentation up-to-date, which was a major blocker. - 1.8.0 includes a new JavaScript implementation ## Health report: - Avro's last release, 1.7.7, was 23 July 2014. More than a year between releases is not a healthy cadence. - Avro needs to increase engagement with potential contributors. - Some bug reports, reviews are not getting attention. - Some language implementations are unmaintained. ## PMC changes: - Currently 16 PMC members. - New PMC members: - Sean Busbey was added to the PMC on Sun Feb 14 2016 - Martin Kleppmann was added to the PMC on Sun Feb 14 2016 ## Committer base changes: - Currently 23 committers. - Matthieu Monsch was added as a committer on Mon Jan 18 2016 ## Releases: - Last release: 1.8.0 on 29 January 2016 ## Mailing list activity: - dev@avro.apache.org: - 273 subscribers (up 2 in the last 3 months): - 635 emails sent to list (541 in previous quarter) - user@avro.apache.org: - 605 subscribers (up 7 in the last 3 months): - 107 emails sent to list (70 in previous quarter) ## JIRA activity: - 45 JIRA tickets created in the last 3 months - 26 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: Report from the Apache Axis Project [Deepal Jayasinghe] ----------------------------------------- Attachment L: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== The board should be aware that the Bloodhound PMC is discussing moving the project to the attic as discussed below. Releases ======== There have been no releases over the last three months. The last release was in fact towards the end of last year: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 15 PMC members on the project with the last additions in January 2014. The last new committers were added in May 2014. Community & Development ======================= Committer activity has remained stubbornly low with very little activity on the development mailing list. The continued lack of activity led the PMC to discuss whether there are enough active members of the PMC who have the time, interest and necessary skills to keep the project going. At this point, only one member of the PMC has stated that they would be prepared to continue. Three others have indicated that they are in favour of moving to the attic. An alternative suggestion for further development to continue by moving away from Trac as the basis for the project was raised. This was suggested to be a radical departure from the work of Bloodhound that, if there was interest in that direction, it could be done outside of the ASF. Discussion having died down on the above topic, there will shortly be a formal vote on the motion to move to the attic which will take place on the private mailing list. ----------------------------------------- Attachment M: Report from the Apache Calcite Project [Julian Hyde] ## Description Apache Calcite is a highly customizable engine for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. Calcite graduated from the Apache Incubator on October 21, 2015. Avatica is a sub-module within Calcite, and provides a framework for building local and remote JDBC and ODBC database drivers. Since March 2016, Avatica has an independent release schedule. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Avatica split Avatica became an independently released module. Previously the 4 Avatica artifacts were released as part of Calcite, but now releases and release numbers are decoupled from Calcite releases. Avatica has its own section of the web site, http://calcite.apache.org/avatica/. Our motivation is that other projects (e.g. Apache Phoenix's Query Server) depend only on Avatica, and are likely to require maintenance releases. Also, Avatica does not depend on Calcite, and the perception that it has few dependencies will improve adoption. Avatica is still governed by the Calcite PMC, and developed using the same git repo and dev list. Communities are diverging slightly, but there is still significant overlap. - A new adapter for Apache Cassandra - Talks * Julian Hyde spoke about Streaming SQL & Calcite at an Apache Samza meetup (Mountain View) on Feb 17. * Julian Hyde and James Taylor presented a Developer Showcase at Strata conference (San Jose) on Mar 30. * Upcoming talks at ApacheCon BigData (Vancouver), Hadoop Summit (Dublin), Kafka Summit (San Francisco), XLDB (Palo Alto), Hortonworks User Group (Herndon, VA). ## Health report: - Mailing lists are a little above typical levels (585 emails on dev) - JIRA at typical levels (141 created, 116 closed) - The community wants to try to keep the volume on the dev list at reasonable levels. During this quarter, we decided to post each created JIRA case to the dev list in the hope that this would drive discussions from dev onto JIRA cases, and thereby reduce dev volume. ## PMC changes: - Currently 14 PMC members. - Josh Elser was added to the PMC on Wed Feb 17 2016 ## Committer base changes: - Currently 15 committers. - Wei (Maryann) Xue was added as a committer on Sun Nov 08 2015 ## Releases: - 1.6.0 was released on Fri Jan 22 2016 - 1.7.0 was released on Tue Mar 22 2016 - avatica-1.7.0 was released on Sun Mar 13 2016 - avatica-1.7.1 was released on Wed Mar 16 2016 ----------------------------------------- Attachment N: Report from the Apache Celix Project [Alexander Broekhuis] ## Description: - OSGi framework implementation in C. ## Issues: - there are no issues requiring board attention at this time ## Activity: - The activity for Celix is low at the moment. - A considerable amount of work has been done on the project, but not much communication in the mailing list. ## Health report: - Number of commits on the project is healty considering it's size. - The project needs to make a new release. This is long overdue. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Alexander Broekhuis on Wed Jul 16 2014 ## Committer base changes: - Currently 7 committers. - No new committers added in the last 3 months - Last committer addition was Bjoern Petri at Fri Jul 18 2014 ## Releases: - Last release was 1.0.0-incubating on Tue Feb 25 2014 ## Mailing list activity: - dev@celix.apache.org: - 55 subscribers (up 0 in the last 3 months): - 18 emails sent to list (41 in previous quarter) ## JIRA activity: - 14 JIRA tickets created in the last 3 months - 13 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment O: Report from the Apache Chukwa Project [Eric Yang] Report from the Apache Chukwa project [Eric Yang] ## Description:             Chukwa is an open source data collection system for monitoring         large distributed systems.            ## Activity:   - Jsoup dependency security vulnerability reported to Chukwa community  - Community reported compatibility problem in Hadoop + HBase  - Some bug fix activities - Getting ready for 0.8.0 release as a minor patch release     ## Issues:  - There are no issues requiring board attention at this time. ## PMC/Committership changes:      - No new PMC members in the last 3 months. - Latest PMC addition: Sun Dec 01 2013 (Grace Huang) - No new committers in the last 3 months. - Latest committer addition: Mon Mar 16 2015 (Sreepathi Prasanna) - Currently 16 committers and 12 PMC members.     ## Releases:       - Latest Chukwa 0.7.0 released on Dec 21 2015     ## Mailing list activity:       - dev@chukwa.apache.org:       - 94 subscribers (down 0 in the last 3 months):      - 69 emails sent to list (135 in previous quarter)       - user@chukwa.apache.org:       - 160 subscribers (0 emails sent in the last 3 months):      - 15 emails sent to list (2 in previous quarter)          ## JIRA activity:       - 6 JIRA tickets created in the last 3 months   - 6 JIRA tickets closed/resolved in the last 3 months  ----------------------------------------- Attachment P: Report from the Apache Continuum Project [Brent Atkinson] ----------------------------------------- Attachment Q: Report from the Apache Crunch Project [Micah Whitacre] Apache Crunch is a Java library for writing, testing, and running MapReduce and Spark pipelines on Apache Hadoop. Project Status -------------- The project has been moving at a slightly slower pace to the previous quarter, with13 new JIRAs being created since the previous board report with 11 (10 new + 1 old) issues being resolved in that time. The majority of the work on the project continues to focus on maintenance such as bug fixes but improvements to the Java 8 Lambda support and HBase efficiencies. There are no board-level issues at this time. Community --------- Community activity slowed but remained steady. The user mailing list activity has reduced to a question (1 every 3 days). Over the last reporting period the activity on the developer mailing list has remained steady (2 per day). David Whiting was added as a committer on Dec 2nd, 2015. Josh Wills was re-elected to the PMC Chair on April 10, 2016 and resolution sent to the board. Releases -------- * Apache Crunch 0.13.0 was released August 5, 2015 ----------------------------------------- Attachment R: Report from the Apache CXF Project [Daniel Kulp] ## Description: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. There are also two sub-projects that leverage CXF: Fediz - Fediz helps you to secure your web applications via the standard WS-Federation Passive Requestor Profile. DOSGi - is the reference implementation of the Distribution Provider component of the OSGi Remote Services Specification ## Issues: There are no issues requiring board attention at this time ##Releases - 3.0.8 was released on Sun Feb 07 2016 - 3.0.9 was released on Sun Mar 27 2016 - 3.1.5 was released on Sun Feb 07 2016 - 3.1.6 was released on Sun Mar 27 2016 - Apache CXF Fediz 1.2.2 was released on Mon Feb 15 2016 - Apache CXF Fediz 1.3.0 was released on Tue Mar 29 2016 - Apache CXF DOSGi 1.8.0 was released on Mon Apr 4 2016 ## Activity: This quarter was a busy quarter creating a bunch of releases. In the CXF core code, there were a lot of bug fixes and enhancements, many to support the releases of Fediz and DOSGi. Fediz 1.3.0 adds a new OpenId Connect based IdP, support for bridging between the WS-Federation and OpenId Connect protocols, and support for SAML SSO in the Fediz IdP. DOSGi 1.8.0 is a result of splitting the DOSGi 1.7.0 release into two parts: a) The OSGi specific and implementation independent interfaces and objects. These were split out of DOSGi and moved to a new sub-project in Apache Aries. b) The CXF specific implementation of the above interfaces which is now the CXF DOSGi sub-project. While helping the Security team evaluate the SRCCLR tool, we did find a few minor dependency updates that were also incorporated in the releases. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andriy Redko on Tue Sep 09 2014 ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Francesco Chicchiricco at Mon Nov 30 2015 ----------------------------------------- Attachment S: Report from the Apache DB Project [Bryan Pendleton] ## Description: The Apache DB TLP consists of the following subprojects: o DdlUtils : a small, easy-to-use component for working with Database Definition (DDL) files. o Derby : a relational database implemented entirely in Java. o JDO : focused on building the API and the TCK for compatibility testing of Java Data Object implementations providing data persistence. o Torque : an object-relational mapper for Java. ## Issues: There are no issues requiring board attention at this time. ## Activity: Two students have submitted applications for the Google Summer of Code 2016 opening in the Derby project. Nominated and seconded by Apache DB community members, I am now a Member of the Apache Software Foundation. Thanks! ## Health report: Activity in the Apache DB community remains low, but steady. ## PMC changes: - Currently 43 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Matthew Adams on Sun Jan 19 2014 ## Committer base changes: - Currently 42 committers. - No new changes to the committer base since last report. ## Releases: - Last release was Derby-10.12.1.1 on Sun Oct 11 2015 ----------------------------------------- Attachment T: Report from the Apache Directory Project [Kiran Ayyagari] Current Activity and Status --------------------------- In the last quarter two new committers were added and new versions of two sub-projects were released. A major refactoring work is happening in the ApacheDS project at the moment and Fortress sub-project is being prepared for a general release. There is very little activity in the remaining sub-projects. ------------------------- Detailed Information ------------------ -- Community -- * Two new committers (last addition: Aug 2015) * Chris Pike * Jan Sindberg * No new PMC members (last addition: November 2015) * Mailing lists: * Users mailing list: 302 subscribers (+1) * Development mailing list: 175 subscribers (+2) * API mailing list: 73 subscribers (+2) * Fortress mailing list: 28 subscribers (+1) * Kerby mailing list: 25 subscribers (+2) -- Current activity -- * Apache Directory LDAP API: * No new releases. * Low activity * Mainly bug fixes. * Apache Mavibot: * No new releases. * Low activity * ApacheDS: * No new release. * High activity. * Apache Directory Studio: * One new release. * Low activity. * Apache eSCIMo: * Nil activity. * No releases yet. * Fortress: * One new releases. * Good activity. * Apache Kerby: * One new releases. * Good activity. -- Releases -- * One new releases for Apache Directory Fortress * 1.0-RC42 (March 24th, 2016) * One new releases for Apache Kerby * 1.0.0-RC2 (March 13th, 2016) * No releases for Apache Directory LDAP API, Server, Studio, Mavibot and eSCIMo ----------------------------------------- Attachment U: Report from the Apache Geronimo Project [Alan Cabrera] ----------------------------------------- Attachment V: Report from the Apache Hadoop Project [Christopher Douglas] Hadoop is a set of related tools and frameworks for creating and managing distributed applications running on clusters of commodity computers. YARN development yielded improvements in preemption, hardening of the timeline server, and a new web UI. Designs for resource-aware scheduling and long-running services are being shaped in JIRA. HDFS erasure coding, native client, object store (Ozone), and intra-datanode rebalancing are significant areas under development. MapReduce continues to receive bug fixes, but even maintenance has slowed. Trademark enforcement continues to be a challenge. While most vendors have engaged quickly and positively, slow (non-)compliance falls off the radar. We are working with trademarks@ to amortize the costs of engagement with templates and will track these incidents in the BRAND JIRA as appropriate, to track followup. RELEASES - 2.6.4 was released on Feb 10 2016 - 2.7.2 was released on Jan 26 2016 COMMUNITY (+ PMC Yongjun Zhang 2016-02-18) (+ PMC Sangjin Lee 2016-04-12) (+ committer Masatake Iwasaki 2016-01-20) (+ committer Eric Payne 2016-02-08) (+ committer Li Lu 2016-02-21) (+ committer Naganarasimha Garla 2016-03-29) (+ committer Kai Zheng 2016-04-07) (+ committer Larry McCay 2016-04-08) (+ branch-HDFS-1312 Anu Engineer 2016-03-03) (+ branch-HDFS-8707 Bob Hansen 2016-01-13) (+ branch-YARN-1011 Iñigo Goiri 2016-01-29) auth: 138 committers (including branch), 66 PMC members ----------------------------------------- Attachment W: Report from the Apache HBase Project [Andrew Purtell] HBase is a distributed column-oriented database built on top of Hadoop Common and Hadoop HDFS. ISSUES FOR THE BOARD’S ATTENTION None at this time. RELEASES We made two releases from our 0.98 code line: 0.98.17 was released on January 21 2016 and 0.98.18 was released on March 25 2016. We made one release from our 1.0 code line, expected to be the last one: 1.0.3 was released on January 27 2016. We made two releases from our 1.1 code line: 1.1.3 was released on January 24 2016 and 1.1.4 was released on March 26 2016. We made the first release from our new 1.2 code line: 1.2.0 was released on February 21 2016. ACTIVITY The last PMC addition was Sean Busbey (busbey) on March 24, 2015. We added three committers in this reporting period. Yu Li was added on March 16 2016. Francis Liu was added on March 21 2016. Ashish Singhi was added on March 29 2016. HBaseCon, the yearly conference for the HBase community, will happen again in 2016, and has been scheduled for Tuesday May 24 2016 at The Village on Market St. in San Francisco. STATS We have seen a notable increase in subscriptions to our user mailing list. 50 committers 27 PMC 1059 subscribers to the dev list (no change in the last 3 months) 2327 subscribers to the user list (up 23 in the last 3 months) 514 JIRA tickets created in the last 3 months 374 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: Report from the Apache Helix Project [Kishore Gopalakrishna] ## Description: - A cluster management framework for partitioned and replicated distributed resources  ## Issues: - None ## Activity: - Low. ## Health report: - Project is stable and mature. We continue to see increase in adoption but no new feature requests from users. There is a plan to re-write the api's but there is no pressing need for that. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Terence Yim on Tue Dec 17 2013 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Greg Brandt at Mon Jul 06 2015 ## Releases: - Last release was 0.6.5 on Tue Mar 24 2015 ## Mailing list activity: - dev@helix.apache.org: - 63 subscribers (up 3 in the last 3 months): - 73 emails sent to list (53 in previous quarter) - user@helix.apache.org: - 92 subscribers (up 8 in the last 3 months): - 39 emails sent to list (18 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Y: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for April 2016 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are 56 podlings currently undergoing incubation. We have four podlings planning to graduate this month and added six podlings to the roster. As is typical in the months following the annual members meeting, we have seen a jump in the number of IPMC members join. * Community New IPMC members: - Marvin Humphrey - Suneel Marthi - Uma Gangumalla - Henri Yandell People who left the IPMC: - Jukka Zitting * New Podlings - Airflow - Gearpump - Mnemonic - Omid - Tephra - Quickstep * Graduations The board has motions for the following: - Apex - Johnzon - TinkerPop - AsterixDB * Releases The following releases entered distribution during the month of March: 2016-03-02 Apache MRQL 0.9.6-incubating 2016-03-03 Apache Apex Malhar 3.3.1-incubating 2016-03-03 Apache Htrace 4.1.0-incubating 2016-03-04 Apache Mynewt-0.8.0-b1-incubating 2016-03-09 Apache Kudu 0.7.1-incubating 2016-03-10 Apache Ranger 0.5.2-incubating 2016-03-11 Apache Taverna-language 0.15.1-incubating 2016-03-11 Apache Taverna-osgi 0.2.1-incubating 2016-03-14 Apache MADlib v1.9alpha-rc2-incubating 2016-03-21 Apache Unomi 1.0.0-incubating 2016-03-25 Apache Mynewt 0.8.0-b2-incubating 2016-03-27 Apache FreeMarker 2.3.24-incubating * IP Clearance - Apache Sling Dynamic Includes * Infrastructure We continue to struggle with podling report reminders. A suite of manual reminders were sent, some were received by the podlings and some were not. * Miscellaneous Based on group understanding, it appears that the Concerted podling will retire soon. Same is likely for OpenAz. * Credits - Report Manager: John D. Ament ------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - Gearpump - iota - Joshua - Metron - Milagro - Mnemonic - Quarks * Not yet ready to graduate No release: - Hawq - Horn - Impala - Rya - Toree Community growth: - Fineract - Geode - MADlib - Ranger - Wave * Ready to graduate The Board has motions for the following: - Apex - Johnzon - TinkerPop - AsterixDB * Did not report, expected next month - Concerted - OpenAz (missed 4 months) - Tephra ---------------------------------------------------------------------- Table of Contents Apex BatchEE Concerted DataFu Fineract FreeMarker Gearpump Geode HAWQ HORN HTrace Impala iota Johnzon Joshua MADlib Metron Milagro Mnemonic Mynewt ODF Toolkit Quarks Ranger Rya Sirona Toree ---------------------------------------------------------------------- -------------------- Apex Apex is an enterprise grade native YARN big data-in-motion platform that unifies stream processing and batch processing. Apex has been incubating since 2015-08-17. Three most important issues to address in the move towards graduation: None. Incubator graduation VOTE passed: https://s.apache.org/qhTf Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Resolution to establish Apache Apex as TLP submitted to board. How has the community developed since the last report? The community is very engaged with the development of the project. We see continious uptick in mailing list participaton (2180 messages on dev@ for March, 122+ subscribers). The community discussed graduation, addressed outstanding issues and completed VOTE. The community has been active building additional meetup groups: http://s.apache.org/jKT Many presentations and uptick in engagement. How has the project developed since the last report? Release 3.3.1-icubating of Malhar on 2016-03-02 Various metrics for March are as follows: +---------------------------------------------------+ | Metric | Core | Malhar | +---------------------------------------------------+ | Non Merge Commits | 52 | 22 | | Contributors | 10 | 11 | | Jira New Issues | 40 | 31 | | Resolved Issues | 43 | 20 | | Pull Requests merged | 33 | 12 | | Pull Requests proposed | 2 | 11 | +---------------------------------------------------+ We are anticipating patch release 3.2.1 in April. Date of last release: 2016-03-02 Apex (Malhar) 3.3.1-incubating When were the last committers or PMC members elected? 2 PPMC members and 1 committer were added since December. PPMC and committer list was updated on the status page. Signed-off-by: [X](apex) Chris Nauroth [ ](apex) Alan Gates [X](apex) Hitesh Shah [X](apex) Justin Mclean [ ](apex) P. Taylor Goetz [X](apex) Ted Dunning -------------------- BatchEE Apache BatchEE aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification. BatchEE has been incubating since 2013-10-03. Three most important issues to address in the move towards graduation: The PPMC feels that the project is ready to graduate soon. 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? Bugfixing continues in BatchEE and we are actively working with the JBatch community towards a new JBatch specification How has the project developed since the last report? BatchEE contributes to the JBatch specification to make the project moving forward in the right direction. Date of last release: 2015-12-08 When were the last committers or PMC members elected? 2015-12-11 Signed-off-by: [ ](batchee) Jean-Baptiste Onofré [ ](batchee) Olivier Lamy [X](batchee) Mark Struberg Shepherd/Mentor notes: John D. Ament (johndament): It seems that the community posted one report, but then a mentor posted a largely reworded report. No evidence of a discussion seems to have been done on public mailing lists for either report. -------------------- Concerted Apache Concerted is a Do-It-Yourself toolkit for building in-memory data engines. Concerted has been incubating since 2015-10-14. Shepherd/Mentor notes: Julian Hyde (jhyde): No report, despite prodding from Chris, and no activity on lists. I think this one's dead. Jake Farrell (jfarrell): No activity so far in 2016. Chris Nauroth (cnauroth): There has been no activity on the project for several months, and we don't see a viable way to salvage it. We are discussing closing it down. -------------------- DataFu DataFu provides a collection of Hadoop MapReduce jobs and functions in higher level languages based on it to perform data analysis. It provides functions for common statistics tasks (e.g. quantiles, sampling), PageRank, stream sessionization, and set and bag operations. DataFu also provides Hadoop jobs for incremental data processing in MapReduce. DataFu has been incubating since 2014-01-05. Three most important issues to address in the move towards graduation: 1. Grow user and contributor base 2. Increased committer activity 3. Continued 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? * A new contributor opened several JIRAs regarding improvements and contributed patches. Two have been committed so far. How has the project developed since the last report? * Improved instructions on loading projects in Eclipse based on discussion in JIRA. * Added checks in build system to catch issues using wrong JDK version. * Some UDFs were improved to be more efficient. * A new UDF is pending review. Date of last release: 2015-11-14 When were the last committers or PMC members elected November 2014 Signed-off-by: [ ](datafu) Ashutosh Chauhan [X](datafu) Roman Shaposhnik [X](datafu) Ted Dunning -------------------- Fineract Fineract is an open source system for core banking as a platform. Fineract has been incubating since 2015-12-15. Three most important issues to address in the move towards graduation: 1. Finalising the initial release 2. Improve the communication around the differences between the previous MifosX project and the new Fineract project, especially in the MifosX community, website etc. 3. With the first initial release, encourage the community to use the proper infastructure (mailing lists, issue tracker) for the ongoing collaboration within the community. 4. Change management towards less 'key-man' dependency on previous tech/community leaders from MifosX, more towards community driven consensus. 5. Reduce clutter on mailinglist from JIRA updates etc. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? On the mailinglist there have been discussions around the lack of traffic on it. This is part of the switchover from the current MifosX community and mailinglists towards the new Fineract lists. At the same time the recent meet-up of Mifosx and Fineract devs and people interested in it (see community development), has also triggered a lot of offline interaction. How has the community developed since the last report? While activity on the mailinglist has been pretty low, we've had a great meet-up in Amsterdam where a nice mix of existing MifosX community members and a group of new interested people was present. This has boosted interest in Fineract. We have a high level of interest from new contributors throughout Africa - we are working to properly engage them and guide them to the correct collaboration channels in our Fineract community. How has the project developed since the last report? Individual members of the leading partner organizations building solutions using the Fineract platform have begun to effectively use the Fineract issue tracker to communicate and track the requirements and enhancements they're building and contributing to Fineract. These individuals are setting a good example that other individuals from our partner community should follow. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [ ](fineract) Ross Gardler [ ](fineract) Greg Stein [X](fineract) Roman Shaposhnik -------------------- FreeMarker FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. FreeMarker is implemented in Java as a class library for programmers. FreeMarker has been incubating since 2015-07-01. Three most important issues to address in the move towards graduation: 1. Finding more active contributors 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 changes How has the project developed since the last report? FreeMarker had two public releases: A Release Candidate (so that users can test it), and one final release. Apart from the new features and fixes, we have adjusted the source code and build process to follow Apache best practices more closely, and to be more appealing for contributors (switching to Java 5, fixing formatting where it didn't fit the modern Java conventions). The legal/policy issue with the web site domain (INFRA-10787) was settled, and we are using our historical domain again (freemarker.org) until graduation. Date of last release: 2016-03-28 When were the last committers or PMC members elected? 2015-10-21 Nan Lei, committer (non-PMC) Signed-off-by: [X](freemarker) Jacopo Cappellato [ ](freemarker) Jean-Frederic Clere [X](freemarker) David E. Jones [X](freemarker) Ralph Goers [X](freemarker) Sergio Fernández -------------------- 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. Make initial Apache branded release 2. Initial community process definition and practice enforcement by following Apache policies 3. Build the first Apache branded informative website to make Gearpump contributor and end-user friendly. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The rights holder of the Gearpump copyright filed a CCLA including a Schedule B granting the Gearpump codebase to the Foundation. We are awaiting assistance from Infrastructure on INFRA-11435 to perform the import. How has the community developed since the last report? All of the initial committers/PPMC have set up with Apache accounts and Apache JIRA accounts. Discussion among developers has started on dev@gearpump.incubator.apache.org How has the project developed since the last report? The JIRA for the podling is active at https://issues.apache.org/jira/browse/GEARPUMP and seeing activity. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members elected yet. Signed-off-by: [X](gearpump) Andrew Purtell [ ](gearpump) Jarek Jarcec Cecho [ ](gearpump) Reynold Xin [ ](gearpump) Todd Lipcon [ ](gearpump) Xuefu Zhang -------------------- Geode Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. Geode has been incubating since 2015-04-27. Three most important issues to address in the move towards graduation: 1. Rename packages to org.apache 2. Expanding the community to include contributors and committers outside of Pivotal. 3. Establish a release cadence. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? - We have been able to address the “Three most important issues to move towards graduation” from the previous report 1. We had our first public release 2. We Added 4 new committers, one of which is outside Pivotal 3. We are about to have a second release, establishing a regular release cadence - We had a GeodeSummit http://geodesummit.com/ - 22 sessions (including Keynote) - Sessions included current use cases as well as integrations with other Apache projects - Over 100 attendees - Received project proposal after the summit. - The Geode Clubhouse hosted a meeting covering a walk through the different approaches for caching data in a Spring based application with Apache Geode by Luke Shannon - The breakdown of JIRA tickets is the following: Q3 / 2015 - 65 created, 19 resolved. Q4 / 2015 - 342 created, 227 resolved. Q1 / 2016 - 438 created, 362 resolved. Q2 / 2016 - 8 created, 12 resolved (As of Apr 4th) - There was a total of 123 pull requests on GitHub with 6 still open. - The breakdown of the mailing lists messages for January, Feb, March of 2016: org.apache.geode.issues 4300 org.apache.geode.commits 3731 org.apache.geode.dev 2154 org.apache.geode.user 294 - There are now 153 subscribers on the dev and 145 on the user mailing lists. - Community events: - January 2016: - FOSDEM 2016 in Brussels: - Taxi trip analysis (DEBS grand-challenge) with Apache Geode (incubating) - Big Data meets Fast Data: an scalable hybrid real-time transactional and analytics solution - February 2016: - Seattle Java User’s Group (Talk about Introduction to Apache Geode) - March 2016: - Geode Summit in Palo Alto, California - Geode meetup in Palo Alto (http://www.meetup.com/Pivotal-Open-Source-Hub/events/228983898/) - Apache Apex (incubating) meetup featuring Geode integration (http://www.meetup.com/Apex-Bay-Area-Chapter/events/228593080/) How has the project developed since the last report? - Had first release, close to the second release (with 134 out of 138 issues resolved) - We elected a release manager for the first release and have rotated that responsibility for the second release - Had a discussion about how to number the releases - Voted on the Release candidates, rejected the first but the second release candidate was voted as the final release - The community discussed the criteria for becoming a committer and learned the correct way of nominating new committers. - JIRA components were refined after a discussion on the mailing list. - Consensus was achieved for the scope for the releases on the mailing list. - Decision was made not to rename the command line tool on the mailing list. - Each commit and pull request is run through CI using Travis CI - Removed @author tags - First release published to maven central - Javadocs hosted on the project website. Date of last release: 2016-02-06 When were the last committers or PMC members elected? - Jinmei Liao (2016-01-26) - Sai Boorlagadda (2016-02-19) - Nitin Lamba (2016-03-08) - Dave Barnes (2016-03-30) Signed-off-by: [ ](geode) Konstantin Boudnik [ ](geode) Chip Childers [ ](geode) Justin Erenkrantz [ ](geode) Jan Iversen [ ](geode) Chris Mattmann [ ](geode) William A. Rowe Jr. [X](geode) Roman Shaposhnik -------------------- HAWQ Apache HAWQ is a Hadoop native SQL query engine that combines the key technological advantages of MPP database with the scalability and convenience of Hadoop. HAWQ reads data from and writes data to HDFS natively. HAWQ delivers industry-leading performance and linear scalability. It provides users the tools to confidently and successfully interact with petabyte range data sets. HAWQ provides users with a complete, standards compliant SQL interface. HAWQ has been incubating since 2015-09-04. Three most important issues to address in the move towards graduation: 1. Produce our first Apache Release 2. Expand the community, by adding new contributors and focusing on making sure that there's a much more robust level of conversations and discussions happening around roadmaps and feature development on the public dev mailing list 3. Infrastructure migration: create Jenkins projects that build HAWQ binary, source tarballs, and run feature tests including at least installcheck-good tests for each commit (HAWQ-127). Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Everything seems to be smooth, nothing urgent at this time. How has the community developed since the last report? 1. One HAWQ Nest community meeting (topic: GPORCA: Query Optimization as a Service) Video: http://bit.ly/HAWQNest0223yt 2. The community shows pretty high activities. In Dev, there have been 816 messages on dev@/user@ in March 2016. 3. Got around 29 pull requests from contributors that are not in the initial committer team. 4. GSoC 2016: 6 topics created for it. 5. FOSDEM 2016 event: https://fosdem.org/2016/schedule/event/hpc_bigdata_hadoopsql/ https://s.apache.org/BYMR How has the project developed since the last report? 1. Main features/improvements added include: a) Hawq-473 Add fault reason and history into hawq catalog b) HAWQ-404 Add sort during INSERT of append only row oriented partition tables c) HAWQ-558 Improve performance of truncate on small tables d) HAWQ-532 HAWQ-580 HAWQ-587 Enhance the virtual segment number selection method e) HAWQ-551 Enhance explain analyze with more information on data locality and resource manager f) HAWQ-546 Enhance \d for HCatalog tables g) HAWQ-144 Support HAWQ build on MAC h) HAWQ-597 Add Travis CI(OSX) for MAC i) Critical bug fixes. 2. 135 new JIRAs filed, 116 resolved (In Mar 2016) 3. 134 code commits (In Mar 2016) Date of last release: We have not had a release yet. When were the last committers or PMC members elected? No new committers/members from initial. Signed-off-by: [](hawq) Alan Gates [](hawq) Konstantin Boudnik [](hawq) Justin Erenkrantz [](hawq) Thejas Nair [X](hawq) Roman Shaposhnik Shepherd/Mentor notes: Justin Mclean (jmclean): A couple on minor issues around communication on list and releases but mentors are on top on it. -------------------- HORN HORN is a neuron-centric programming APIs and execution framework for large- scale deep learning, built on top of Apache Hama. HORN has been incubating since 2015-09-04. Three most important issues to address in the move towards graduation: 1. Increase development velocity 2. Make a 0.1 release 3. Refocus the direction we want to take this project. 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? Number of subscribers has increased slightly, development has however been slow. How has the project developed since the last report? We have decided that we need to refocus on what we want HORN to look like Date of last release: None yet. When were the last committers or PMC members elected? October Signed-off-by: [ ](horn) Luciano Resende [ ](horn) Robin Anil [x](horn) Edward J. Yoon -------------------- 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 HTrace community 2. Continue to explore projects integratiing HTrace 3. Continue to develop and release stable HTrace incubating artifacts 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? * YCSB community are working on integrating HTrace. * Google Summer of Code 2016 projects for Apache HTrace are being planned. There are proposals such as * distributed tracing for s3 and other alternative Hadoop FS * Kudu span receiver * integrating HTrace into Hadoop YARN * HTrace'ing in Apache Nutch How has the project developed since the last report? * +70 issues were fixed and released as part of 4.1.0-incubating. * Improved htraced a lot in Web-UI, robustness, metrics and logging * Added Docker support for development * Added Documentation for developers Date of last release: * htrace-4.1.0-incubating on March 5th, 2016 When were the last committers or PMC members elected? * None this period. Last added committer: Abraham Elmahrek - 2.11.15 Signed-off-by: [X](htrace) Jake Farrell [ ](htrace) Todd Lipcon [X](htrace) Lewis John Mcgibbney [ ](htrace) Andrew Purtell [X](htrace) Billie Rinaldi [ ](htrace) Michael Stack Shepherd/Mentor notes: John D. Ament (johndament): This podling's come pretty far. Maybe time to graduate soon? -------------------- Impala Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. Impala has been incubating since 2015-12-03. Three most important issues to address in the move towards graduation: 1. Transition of development workflows to ASF (see https://issues.cloudera.org/browse/IMPALA-3221) 2. Initial release as incubating project. 3. Community growth 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 have been no additions to the committer or PMC lists since incubation began. We continue to see an uptick in external contributions, with two patches from new contributors this month. One contributor pleasingly reported it was "great to work closely with Impala community". How has the project developed since the last report? We have put together a list of tasks required to move development of Impala from Cloudera's infrastructure to the ASF. Since Impala was already a well-established project before the Incubator proposal, there is perhaps more decoupling required than for more nascent projects. The list is at https://issues.cloudera.org/browse/IMPALA-3221, and is being actively worked on. Note that this doesn't cover the standard podling tasks (like name search, etc). Date of last release: None since entering incubation. When were the last committers or PMC members elected? None since entering incubation. Signed-off-by: [X](impala) Tom White [ ](impala) Todd Lipcon [ ](impala) Carl Steinbach [ ](impala) Brock Noland -------------------- 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. Overcome current technical difficulties. You might be asking what is happening with Apache iota. The initial architecture that we wanted to upload was not as scalable as we required it to be. Rather than upload an architecture that we wanted to fundamentally change we have been developing a new backend architecture and code based that implements a significantly more scalable solution using Apache, Spark, Spark Streaming and Cassandra. We are still using Python and Django for our APIs and authentication (session and token based). Consequently, you haven’t seen any activity on the Apache iota site and repository. This will be changing soon. Litbit (the contributing company whose business runs on iota) has been working around the clock to remake the backend using additional Apache components that makes the solution far more scalable. 2. Set up web site and import code. We will be setting up the Apache iota website to reflect the new architecture and uploading the initial source code as quickly as we can. 3. Promote Iota to a wider user base / grow the community. We are planning to promoting iota at an upcoming keynote being given by Scott Noteboom (Litbit's CEO). In addition we will be presenting iota at Apache Con in May 2016. Our goal in promoting iota will be to start building a community that will contribute to moving iota to it’s first release as an Apache incubator project 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? * This is the first submitted report How has the project developed since the last report? * This is the first submitted report Date of last release: * None When were the last committers or PMC members elected? None yet, just getting started. Signed-off-by: [ ](iota) Daniel Gruno [ ](iota) Sterling Hughes [X](iota) Justin Mclean [X](iota) Hadrian Zbarcea Shepherd/Mentor notes: John D. Ament (johndament); Its a bit concerning to see that the project is starting off in a non-ASF way. Even if the code isn't quite right for donation, may be better to start off writing new code in the ASF repos. Justin Mclean (jmclean): I too have concerns about why they are developing outside of the ASF. I've contacted them a few times with a please explain and have assurances that this will be fixed. I'd suggest placing the podling on monthly reports for a few more months. Drew Farris (drew): 2 mentors active on the mailing list this month, but little activity as the team has not moved development to ASF. Concur with keeping podling on monthly reports. -------------------- Johnzon Implementation of JSR-353 JavaTM API for JSON Processing. Johnzon has been incubating since 2014-06-09. Three most important issues to address in the move towards graduation: 1. Currently graduation, so nothing but issues necessary for graduation Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * Currently graduating to a TLP How has the community developed since the last report? There are new people on the dev list and the project got contributions from non-committers. On the dev list there are approx. 20 msgs (on average) messages per month. How has the project developed since the last report? The project did its 10th incubator release. During the last three month 9 jira issues were reported and 6 of them fixed. Project has also started to implement the upcoming JSR-374 and JSR-367 specification. The project has also voted for a logo. Date of last release: 2016-FEB-17 (0.9.3-incubating) When were the last committers or PMC members elected? Last committer was elected 2014-08-23, last PMC member was elected 2015-04-09 (Hendrik Saly) Signed-off-by: [X](johnzon) Justin Mclean [ ](johnzon) Daniel Kulp Shepherd/Mentor notes: John D. Ament (johndament): Podling is planning to graduate, but sign off received from only one mentor. -------------------- 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. Migration of the entire project over to Apache infrastructure (nearly complete) 2. Building up community and attracting developers 3. Putting out regular Joshua releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None that come to mind. We are occupied with the issues above, and things are proceeding nicely. How has the community developed since the last report? We have voted in two new committers and invitations have been extended to them. How has the project developed since the last report? A large pull request was accepted reporting large speed increases due to caching, and increasing the usability of Joshua as a library. Date of last release: 2015-11-05 (prior to incubation) When were the last committers or PMC members elected? - Felix Hieber (2016-04-01) - Kellen Sunderland (2016-04-01) Signed-off-by: [ ](joshua) Paul Ramirez [X](joshua) Lewis John McGibbney [ ](joshua) Chris Mattmann [ ](joshua) Tom Barber [ ](joshua) Henri Yandell -------------------- MADlib Big Data Machine Learning in SQL for Data Scientists. MADlib has been incubating since 2015-09-15. Three most important issues to address in the move towards graduation: 1. Continue to produce regular Apache (incubating) releases. 2. Expand the community, increase dev list activity and add new contributors. 3. Execute and manage the project according to governance model required by the "Apache Way”. 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. Held three community calls in Q1 2016. Each call featured a different member of the Apache MADlib community presenting on a topic of interest to them: * Jan 15th - Bayesian Analysis of Binomial Response Models on MPP Databases (Gautam Muralidhar) * Feb 16th - An Overview of GWR Analysis of Spatial Data (Chenliang Wang) * Mar 16th - MADlib on PostgreSQL and PGXN (AJ Welch) 2. One new committer has been added to the project (Xiaocheng Tang) 3. Presentation of Apache MADlib at FOSDEM’16 in Brussels (Frank McQuillan) 4. Material technical conversations on dev mailing lists and in the appropriate JIRAs (e.g., 111 emails on dev@ mailing list in Feb) 5. Several Google Summer of Code (GSoC) candidates have expressed interest in working on MADlib projects via dev@ mailing list. How has the project developed since the last report? 1. 1st ASF release MADlib v1.9alpha on 3/11/16 which was intended to clear all potential IP issues in the code base and make it legally ready to be adopted by the community. 2. 2nd ASF release MADlib v1.9 is currently in IPMC voting as of this writing on 4/6/16. The goal of this 2nd release is general availability of MADlib v1.9 for community use. 3. Some features in the latest release: path functions, support vector machines, advanced matrix operations, covariance matrix, proportion of variance for PCA, support for Apache HAWQ (incubating) 2.0. 4. 15 JIRAs created and 27 resolved in last 30 days. Date of last release: Apache MADlib (incubating) v1.9alpha on 3/11/16. When were the last committers or PMC members elected? Xiaocheng Tang on 1/14/16. Signed-off-by: [ ](madlib) Konstantin Boudnik [X](madlib) Ted Dunning [X](madlib) Roman Shaposhnik -------------------- Metron 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. Metron has been incubating since 2015-12-06. Three most important issues to address in the move towards Graduation. - Building a diverse community of developers for Metron - Getting security practitioners to provide feedback on requirements - Make an Apache release Any issues that the Incubator PMC or ASF Board might wish/need to be aware of - We are currently trying to produce the first Apache release of Metron * How has the community developed since the last report - We added one additional committer, David Lyle - We accepted 2 separate contributions from non-committers interested in Metron - We saw an uptick in interest from the community on the dev boards which corresponds to people trying the product prior to an official release, which is a good sign. * How has the project developed since the last report - We closed 20 more Jiras and are in the latest stages of releasing an Apache release. - We added deployment automation for EC2 so trying out Metron in a multi-node environment is even easier - We integrated the CI environment that infra set up for us at our request so that unit tests and apache rat license checks are run on every pull request submitted - We added support for indexing enriched sensor capture data into Apache Solr indexing as well as Elasticsearch Date of last release: -- When were the last committers or PMC members elected? David Lyle on 22 March 2016 Signed-off-by: [X](metron) Billie Rinaldi [ ](metron) Chris Mattmann [X](metron) Owen O'Malley [ ](metron) P. Taylor Goetz [ ](metron) Vinod Kumar Vavilapalli -------------------- Milagro Distributed Cryptography; M-Pin and other pairing protocols for Identity and Trust Milagro has been incubating since 2015-12-21. Three most important issues to address in the move towards graduation: 1. Import the software: The source code is already prepared and placed in repositories on GitHub – soon to be imported to Apache repositories. This includes a full Milagro MFA implementation. 2. Awareness among developers: Milagro announcement – during ApacheCon North America – May 2016 3. General Awareness 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? No substantial developments to report. The project is targeting community development following Apachecon presentations. How has the project developed since the last report? Project members are preparing to present the project at ApacheCon with a view to connecting with the wider Apache community and finding synergies with other projects. Date of last release: n/a When were the last committers or PMC members elected? February, as reported. Signed-off-by: [ ](milagro) Sterling Hughes [ ](milagro) Jan Willem Janssen [x](milagro) Nick Kew -------------------- Mnemonic Mnemonic is a Java based non-volatile memory library for in-place structured data processing and computing. Mnemonic has been incubating since 2016-03-03. Mnemonic code was moved into ASF on 3/24 Various metrics for March are as follows: +--------------------------------------------+ | Metric | counts | +--------------------------------------------+ | Non Merge Commits | 82 | | Contributors | 10 | | Jira New Issues | 13 | | Resolved Issues | 4 | | Pull Requests merged | 8 | | Pull Requests proposed | 8 | +--------------------------------------------+ Three most important issues to address in the move towards graduation: 1. Apache releases: we are preparing 0.1.0 release 2. Expand and build strong community, keep active dev list discussions, adding new contributors 3. Develop new features Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Everything is on track, nothing urgent at this time. How has the community developed since the last report? The project is in early stage in setting up the infra. In addition to contributors listed in Mnemonic proposal, we had one new contributor joined us. We are actively discuss with Arrow community in dev list for the idea on integration. Apache Arrow community is very interested in Mnemonic integration for extending Arrow into persistent memory and storage. How has the project developed since the last report? We ported source code in Apache on 3/24 after SGA was filed on 3/23. We are doing several refactorings and defining coding guidelines to fit Apache project standard. We are working on enabling Apache Arrow to use Mnemonic as underlying pooling mechanism. We are designing the native computing infrastructure, built native computing interface code. Bug tracking JIRA setup was done, 13 issues were filed. 4 issues were solved. Mailing list discussions are happening actively related to infrastructure, code standard, features for the project. Date of last release: No release yet, working on 0.1.0 release When were the last committers or PMC members elected? No election, since the project is just starting. As part of incubation process, initial committers and contributors were proposed and added. Signed-off-by: [X](mnemonic) Patrick Hunt [X](mnemonic) Andrew Purtell [X](mnemonic) James Taylor [X](mnemonic) Henry Saputra -------------------- Mynewt Mynewt is a real-time operating system for constrained embedded systems like wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures. Mynewt has been incubating since 2015-10-20. Three most important issues to address in the move towards graduation: 1. Make further releases capable of producing a downloadable RTOS image with support for multiple peripherals and network connectivity. Do subsequent releases to indicate thorough understanding, repeatability, and maturity of process. 2. Continue to develop and execute policies that enable project contributors to achieve self-governance 3. Expand community - attract new project contributors and users, grow committer base 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. Healthy, active mailing lists with increasing numbers of subscribers 2. Continual outside interest by 3rd parties. Outreach via conferences, exhibits, one on one meetings, beta testers, GSoC participation. 3. Vigorous discussions and implementation decisions via proposals and voting on @dev mailing list. How has the project developed since the last report? 1. Releases: Two releases so far - first on 22nd Feb, next on 18th March - Identified and fixed license issues, regular process established to check for license issues esp. with third party software - Tagging process and release candidate naming process tested and used - Voting process and timelines established and used 2. Documentation support: Several committers added documentation either through direct git pushes or pull requests on github mirror. 3. Effort towards self governance: - Two releases completed successfully. - Two committer candidates going through voting for committer status after meeting threshold of patch submissions. Date of last release: 2016-03-18 When were the last committers or PMC members elected? At the start Signed-off-by: [ ](mynewt) Sterling Hughes [X](mynewt) Jim Jagielski [X](mynewt) Justin Mclean [ ](mynewt) Greg Stein [ ](mynewt) P. Taylor Goetz -------------------- ODF Toolkit Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents ODF Toolkit has been incubating since 2011-08-01. Three most important issues to address in the move towards graduation: 1. Attract more developers 2. Have frequent releases 3. Decide on possible ways to graduate Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Not many developers are active currently. How has the community developed since the last report? Several patches have been added to JIRA by community members. Issues have been reported. How has the project developed since the last report? Several patches have been applied, a new release is planned. Date of last release: 2014-06-02 When were the last committers or PMC members elected? 2012-10-29 Signed-off-by: [ ](odftoolkit) Sam Ruby [X](odftoolkit) Nick Burch [ ](odftoolkit) Yegor Kozlov Shepherd/Mentor notes: Nick Burch (nick): Hopefully the new release will generate a little more interest. I'd suggest we wait a few more months to see the effect of that, before deciding on what to do with the podling (staying in the incubator for ever isn't an option!) -------------------- Quarks Apache Quarks is a programming model and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Quarks provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge. Quarks has been incubating since 2016-02-29. Three most important issues to address in the move towards graduation: 1. Create and expand a diverse community of contributors and committers around Quarks project 2. Create the first Apache release of Quarks 3. Complete migration of website to host all content at Apache (javadoc is still on Github). Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Nothing jumps to mind. How has the community developed since the last report? The Quarks community is keeping dev-related conversations on the mailing list. Because of this, it's allowed for the participation of independent contributors in mailing list discussions. Although our list of independent contributors is small, Quarks is still very new as an Apache project and we aim to actively grow our list in the near future. How has the project developed since the last report? * The project has successfully migrated from Github-based development to using the Apache git repo, Jira, and the mailing lists. Date of last release: Quarks is still new, so we haven't created an Apache release as of yet. When were the last committers or PMC members elected? No changes from the initial committers. Signed-off-by: [ ](quarks) Daniel Debrunner [ ](quarks) Luciano Resende [X](quarks) Katherine Marsden [X](quarks) Justin Mclean -------------------- Ranger The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform. Ranger has been incubating since 2014-07-24. Three most important issues to address in the move towards graduation: 1. Increase the community participants for Apache Ranger 2. Re-organize documentation for easier access to end-users, new users and contributors. 3. Integration of Apache Ranger with other Apache Security Initiatives 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. Added new contributors: (Bolke de Bruin,Deepak Sharma,Colm O hEigeartaigh,Tushar Dudhatra,mugdha.varadkar,pradeep.agrawal,mehul,ankita.sinha) Total Contributor Count: 23 2. Mailing list activity since last report (Dec-01-2015 to Mar-31-2016): @dev 1534 @user 153 @commit 345 3. Issues (JIRAs) created/resolved since last report (after Dec-01-2015 before Mar-31-2016): Created: 153 Resolved: 140 How has the project developed since the last report? 1. Released two minor releases : 0.5.1 release on 01/26/2016 0.5.2 release on 02/29/2016 2. Members have been working on a next major release of 0.6.0 a. Working with new contributors to add HSM support for Apache Ranger KMS. b. Working to provide both Column-level-masking and Row-level-filtering support for data security c. Working to add Tag-Based authorization policies Date of last release: Feb-29-2016 When were the last committers or PMC members elected? 1. Gautam Borad has been added as committer on June-29-2015 Signed-off-by: [ ](ranger) Alan Gates [ ](ranger) Daniel Gruno [ ](ranger) Devaraj Das [X](ranger) Jakob Homan [X](ranger) Owen O'Malley -------------------- Rya Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Accumulo. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data. Rya has been incubating since 2015-09-18. Three most important issues to address in the move towards graduation: 1. Become familiar with the release process and have a first release as part of the Apache Foundation 2. Expand the "how to" document to explain the ways new contributors can become involved in the project, so we increase the size of the community. 3. Add new committers to the project. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? * We have a Rya "office hour" teleconference every other week. We had some technical difficulties with screen sharing, but we had a working solution for the last meeting. Users and developers can ask questions, receive answers, discuss ideas for future developments. The minutes are sent to the dev@ list. * We have more PRs from non-committers which are integrated into the repository. We expect some of these non-committers to continue to submit PRs and become committers. * There were several ideas from Rya for Google Summer of Code, and a few students expressed interest; one of them submitted a proposal How has the project developed since the last report? * Created a quick-start VM for users to try out Rya. * Created a website for the project. * Resolved a handful of issues that users have encountered. * Committed features: incremental update for precomputed join indices, extensions to query planning to support more complex precomputed join indices, free text search support for MongoDB, additional Geo indexing for MongoDB, extensions of examples for both Accumulo and MongoDB backed Rya Date of last release: Not applicable When were the last committers or PMC members elected? Not applicable Signed-off-by: [x](rya) Josh Elser [x](rya) Edward J. Yoon [x](rya) Sean Busbey [x](rya) Venkatesh Seetharam Shepherd/Mentor notes: Sean Busbey (busbey): Project activity was a little slow, due to other time commitments for the dev community, but folks had a great discussion around next steps when it came time for a draft report. -------------------- Sirona Monitoring Solution. Sirona has been incubating since 2013-10-15. Three most important issues to address in the move towards graduation: 1. increase the community 2. do more releases 3. make the community more active 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? No change but some more user feedbacks. How has the project developed since the last report? Several fixes have been done and enhancements in instrumentation side. Date of last release: 2015-11-18 When were the last committers or PMC members elected? Signed-off-by: [X](sirona) Olivier Lamy [ ](sirona) Henri Gomez [ ](sirona) Jean-Baptiste Onofre [ ](sirona) Tammo van Lessen [ ](sirona) Mark Struberg [X](sirona) Romain Manni-Bucau -------------------- Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. It enables interactive workloads between applications and a Spark cluster. As a Jupyter Notebook extension, it provides the user with a preconfigured environment for interacting with Spark using Scala, Python, R or SQL. Toree has been incubating since 2015-12-02. Three most important issues to address in the move towards graduation: 1. Resolve LGPL dependency: This is in progress, and hopefully we will have the dependency license changed to a license that is compatible with AL2. 2. Make a release: nearing completion 3. Grow a diverse community: We should put some emphasis on growing the community and making it diverse (the rule is at least three independent contributors) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? TOREE-262 - Progress on removal of LGPL dependency How has the community developed since the last report? 1. Active communication in mailing list and gitter with early adopters 2. Still working on transitioning users from Spark Kernel project into Toree. 3. First external contribution made by user @dongjoon-hyun 4. Apache Toree was featured at SF Data Science meetup https://github.com/asimjalis/apache-toree-quickstart Date of last release: None since incubation. When were the last committers or PMC members elected? No new additions since incubation Signed-off-by: [ ](toree) Luciano Resende [ ](toree) Reynold Xin [X](toree) Hitesh Shah [ ](toree) Julien Le Dem -------------------- 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. Growing community 2. Improving code base. 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 made our first release. - Elected new committer. - Previously private fork (wiab.pro) opened the source code that includes many improvements that can be integrated back into main project. - Also, there's an active development in additional open source fork (swellrt) that potentially allows us to integrate back important features. How has the project developed since the last report? - Replaced the old ANT build system with a new Gradle one. - Fixed a few bugs - Made a few code improvements Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [x](wave) Upayavira ----------------------------------------- Attachment Z: Report from the Apache Isis Project [Dan Haywood] ## Description: Apache Isis is a framework for rapidly developing domain-driven apps in Java. ## Issues: There are no issues requiring board attention at this time ## Activity: Since the last report we have made two releases, a bug fix v1.11.1 [1] and a much larger release 1.12.0 with some substantial new features [2]. One technical talk and two conference sessions have been accepted (on the topic of Apache Isis); all are in June and in the UK (London, Cambridge and London again). ## Health report: Project activity (#mails, tickets, commits etc) are healthy, with the v1.12.0 release incorporating substantial new features. Documentation has been improved; we now generate PDFs of all our user guides (previously only HTML was available). In addition a whole new slew of screencasts have been recorded [3], hopefully will attract new users to the framework. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Martin Grigorov on Tue Dec 23 2014 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Martin Tzvetanov Grigorov at Thu Dec 11 2014 ## Releases: - 1.11.1 was released on Sun Jan 17 2016 - 1.12.0 was released on Tue Mar 29 2016 ## Mailing list activity: The mailing list activity has declined somewhat, but we continue to see new voices asking questions. In previous quarters we have always seen a handful of new subscribers; this is the first one where there has been no substantive change. We are not unduly worried about this at this time. - users@isis.apache.org: - 155 subscribers (up 1 in the last 3 months): - 286 emails sent to list (532 in previous quarter) - dev@isis.apache.org: - 74 subscribers (down -1 in the last 3 months): - 791 emails sent to list (836 in previous quarter) ## JIRA activity: - 68 JIRA tickets created in the last 3 months - 58 JIRA tickets closed/resolved in the last 3 months [1] http://isis.apache.org/release-notes.html#r1.11.1 [2] http://isis.apache.org/release-notes.html#r1.12.0 [3] http://isis.apache.org/screencasts.html ----------------------------------------- Attachment AA: Report from the Apache James Project [Eric Charles] ## Description: - The Apache James Project delivers a rich set of open source modules and libraries, written in Java, related to Internet mail which build into an advanced enterprise mail server. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Focus has been on updating and enrolling jsieve (server side mail filtering) into the server code base. - Mailbox API as Elasticsearch and Cassandra implementations ## Health report: - Due to the unavailibity of a final james server 3 release, users tend to fallback to version 2. Discussions will be started to have a plan for this first final version 3. ## PMC changes: - Currently 16 PMC members. - New PMC members: - Antoine Duprat was added to the PMC on Fri Mar 11 2016 - Benoit Tellier was added to the PMC on Fri Mar 11 2016 - Matthieu Baechler was added to the PMC on Fri Mar 11 2016 ## Committer base changes: - Currently 36