The Apache Software Foundation Board of Directors Meeting Minutes November 16, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:37 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/33ef The meeting was held via teleconference, hosted by Doug Cutting and Cloudera. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Rich Bowen Shane Curcuru Bertrand Delacretaz Isabel Drost-Fromm Marvin Humphrey Jim Jagielski - left at 12:01 Brett Porter Mark Thomas Directors Absent: Chris Mattmann Executive Officers Present: Ross Gardler Sam Ruby Craig L Russell Ulrich Stärk Executive Officers Absent: none Guests: Antoine Toulme Daniel Gruno David Nalley Greg Stein Hadrian Zbarcea Henri Yandell Roman Shaposhnik Sean Kelly Sharan Foga Tom Pappas 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of October 19, 2016 See: board_minutes_2016_10_19.txt Approved by General Consent. B. Action without Meeting See: Attachment BO 4. Executive Officer Reports A. Chairman [Brett] Having been on holidays most of the month, I have nothing to report other than being a long way behind on email. B. President [Sam] Overall ======= We don't have an approved budget; we haven't been routinely reviewing budget vs actuals, expenses (and possibly income) is running ahead of plan, and we have at least two areas where an increase in budget may be warranted. I've been working with the Treasurer and Virtual to improve reporting on actuals. I seek guidance from the board on the overall shape of what the FY 2017 budget should look like; I will then work with owners of individual line items to produce an updated draft budget for the board to approve. I've met (via phone, Skype, and Google Talk) with each of the people who own monthly reports (though not individually with Rich who understandably is busy at this moment); based on these discussions my initial priorities are: budget, brand, fundraising, then EA/TAC. I have a request for the board: my preference is that the primary vehicle for board feedback on operations be via the monthly teleconferences and review of progress on action items. When things come up at other times, I'd prefer that such items be added to the agenda for the next board meeting unless there is a specific reason why it needs to be resolved urgently before that time. For personal reasons, I am not able to travel to Seville this month. I thank Ross for preparing draft slides and Jim for giving the presentation in my absence. I'm maintaining a file for tracking purposes: https://svn.apache.org/repos/private/foundation/President/STATUS Executive Assistant =================== This role was originally envisioned to be responsible for a number of different foundation tasks; at the present time TAC is taking up a large portion of time. I'm not interceding at the current time, but I do plan to revisit what the ideal allocation of time to each task should be with Melissa in the quiet time between conferences. Brand Management ================ This area is considerably running over both the draft budget and last years actuals. I urgently seek guidance from the board as to whether the budget should be revised or brand management should change how it is currently operating. Please see the brand management report for additional information on where money has been sent and on the outlook. Less urgently, but something I would like feedback on in the upcoming months: what is the role the board would like to see brand management perform for the foundation? We clearly have comprehensive brand management procedures. While we have some PMCs that are following these procedures, we have other PMCs that are behaving as if they are unaware of those procedures. We even have PMCs that are clearly aware of the procedures, have provided no actionable feedback on those procedures, but aren't closely following them. A concrete example: this month you proposed that PMCs SHALL restrict their discussions of trademark enforcement actions to private mailing lists. Is this destined to be another requirement that many PMCs will continue to be unaware of and others will chose not to follow? If so, does it make sense to continue to produce such requirements? A second concrete example: Brand Management and PMCs are grappling with what would be a reasonable division of labor with respect to trademark enforcement. This thread with Hadoop is illustrative: https://s.apache.org/yEY6 Accordingly, Shane an Mark have begun exploring how to better track resolutions of potential infringements; being better organized should enable us to move from anecdotal discussions which may ultimately reduced down to internal miscommunication issues to actual data on what steps were or were not taken and how long it takes to resolve an issue. Perhaps the big picture that will emerge is that the Brand Management team will periodically do a scan for egregious violations and hand them off (via JIRA) to the PMCs to resolve by making use of the software wizard/assistants that we produce for this purpose, augmented by Brand Management as a resource to provide advice and as an interface to resources like DLAPiper. Fundraising =========== While income isn't received on any sort of predictable schedule, we seem to be running well above last years income received by this time, and I believe that we have enough months data for that to be representative. As we expect expenditures to continue to grow over the upcoming years, it is prudent to plan for changes that could be made that wouldn't compromise who we are as a foundation. As an example, increased recognition may be possible, but anything that involves control or setting of direction is off the table. This likely will result in Fundraising having a line item in the budget, whether it be for ASF travel to current or potential sponsors (or alternatively to conferences where such are present) or for staff. A concrete example of the latter has been posted to operations@: https://s.apache.org/7Sgf There also is an expectation that charitable foundations that receive donations acknowledge receipt for tax purposes. Marketing and Publicity ======================= Sally and her team handle an amazing amount of absurdity on a continuing basis. This team is also vital to both Brand Management and Fundraising. Despite this, flow of information regarding sponsor changes, incubator activities, branding challenges, and executive officer changes is haphazard. An example of something that should be automatic and routine: https://s.apache.org/OH3o. This needs to be fixed. One item of expense that has come up that is not covered by the current budget: Snoot development costs from Quenda in producing graphics included in our annual report. I intend to include that expense in upcoming draft budget and the board can decide whether or not that is something that the ASF should cover. Meanwhile, Sally has approved one month as a part of the M&P budget. It is coming up on the time to start preparation for the next annual report. Infrastructure ============== David indicated that he would like to continue, and in response I indicated that I have no plans to replace him. As I am aware that he is not fully in control of his availability, and in particular may be unavailable for days without prior notice, I've asked Greg to draft a resolution converting his position to an officer's position so that we have continuous coverage. I trust that Greg and David can work together and adjust dynamically to changes in availability without my involvement. This is also not intended as a net increase in demand on Greg's time. The good news is that the hiring to backfill contractors that were hired away is complete. The bad news is that Infrastructure is another area that is likely to go over budget for FY 2017. It is my recommendation that it be allowed to do so. I've asked the infrastructure team to include two items in their monthly reports: progress on "GitHub as master" until that item reaches conclusion one way or another, and items that will lead to a reduction in the average cost per project over time. The latter is intended to be an ongoing effort, and likely will start with a focus on measurement, proceed to the development of plans, and ultimately a report on progress. This replaces and subsumes a prior direction to focus on "self service", which may turn out to be one of several approaches used to reduce costs. Travel Assistance Committee =========================== At this time, I am changing Melissa's role from acting TAC chair to being the TAC chair. Melissa is transitioning to her new role. At the moment, she is mostly following in the footsteps of her predecessor; the hope is that for Miami she adjusts things to suit what works best for her. As an example, it might be better to move from a UK based travel agent to either a US based travel agent or directly booking flights. The application TAC uses for applications is undocumented and unmaintained; this needs to be corrected. Conference Committee ==================== I've only touched bases briefly with Rich on this item; he is understandably focused on Seville at the moment. I plan to delve more deeply into this in the time between conferences. Rich is developing a playbook for ApacheCon: https://svn.apache.org/repos/private/foundation/ApacheCon/playbook.md Additionally, please see Attachments 1 through 7. DLA Piper is no longer supplying legal resources pro bono, which came as a surprise to some directors. We use them for occasional legal advice and managing our trademark registrations and docket. They charge a discounted hourly rate capped at $5K per month exclusive of trademark registration fees. Other firms would probably charge more. The board is comfortable with continuing to pay DLA Piper for their services at the current rate. C. Treasurer [Ulrich] As requested going forward I will include not only data for the current month but also an overview actuals vs budget both for the current month as well as year-to-date. Since we still don't have a budget for FY2017 the FY17 "budget" is based on the 2016 actuals. In October we have been operating with a small net income vs a projected loss. YTD we have been operating with a significant smaller loss then projected so we still are in a very comfortable financial situation. There is an ongoing effort to get a spending policy for credit card holders in place which has been delayed due to my dayjob duties. Income and Expenses for October 2016 Current Balances: October 2016 FY17 Budget Variance Citizens Checking $498,205 Citizens Money Market $1,203,963 Amazon- ASF Payments $- Paypal - ASF $94,649 Wells Fargo Checking - ASF $- Wells Fargo Savings $- Total Checking/Savings $1,796,818 Income Summary: Public Donations $2,864 $- $2,864 Sponsorship Program $105,000 $39,167 $65,833 Programs Income $- $- $- Other Income $- $- $- Interest Income $510 $- $510 Total Income $108,373 $39,167 $69,207 Expense Summary: Infrastructure $53,326 $47,384 $5,942 Sponsorship Program $- $- $- Programs Expense $- $- $- Publicity $17,518 $(4,556) $22,073 Brand Management $6,960 $1,760 $5,200 Conferences $829 $3,215 $(2,386) Travel Assistance Committee $5,224 $13,646 $(8,422) Tax and Audit $- $- $- Treasury Services $3,100 $3,100 $- General & Administrative $8,421 $8,546 $(126) Total Expense $95,377 $73,096 $22,281 Net Income $12,997 $(33,929) $46,926 YTD 2016 YTD FY17 Budget Variance Income Summary: Public Donations $12,101 $- $12,101 Sponsorship Program $430,795 $119,000 $311,795 Programs Income $- $- $- Other Income $825 $- $825 Interest Income $3,022 $- $3,022 Total Income $446,743 $119,000 $327,743 Expense Summary: Infrastructure $310,177 $290,268 $19,909 Sponsorship Program $- $- $- Programs Expense $- $- $- Publicity $78,103 $77,138 $965 Brand Management $29,292 $2,864 $26,427 Conferences $2,194 $10,778 $(8,585) Travel Assistance Committee $19,864 $32,680 $(12,816) Tax and Audit $6,000 $6,000 $- Treasury Services $18,600 $18,600 $- General & Administrative $53,630 $56,713 $(3,083) Total Expense $517,859 $495,042 $22,818 Net Income $(71,116) $(376,042) $304,926 D. Secretary [Craig] The new Whimsy Secretary Mail tool is working well even in light of the record number of documents received in a single month. In October, 137 iclas, 10 cclas, and one grant were received and filed. E. Executive Vice President [Ross] Truth is I've been enjoying the total freedom from day to day activities. I've assisted a little in the transition to Sam as the new President, but for the most part Sam has simply moved forwards. As agreed with Sam I will pick up the areas that are "just working" and provide oversight there so that Sam can focus on the areas that need attention. Given Sam's indication that he feels the areas needing focus are Brand and Fundraising this means I will be "on call" for Marketing and Publicity, Infrastructure, Conferences and TAC. Each of these areas has paid support and thus the overhead here is expected to be manageable. I will monitor those lists and be available to our officers in those roles should the need arise. F. Vice Chairman [Chris] Nothing to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Isabel] See Attachment 8 B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Bertrand] See Attachment 10 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Abdera [mt] # Chukwa [rb] # DeviceMap [mh] # Gora [bp] # Open Climate Workbench [bp] # Spark [mh] # Stratos [mh] # TomEE [bp] # Xerces [bp] A. Apache Abdera Project [Ant Elder / Mark] No report was submitted. @Mark: pursue a report for Abdera; determine if the Attic is next B. Apache Ambari Project [Yusaku Sako / Marvin] See Attachment B C. Apache Ant Project [Jan Matèrne / Shane] See Attachment C D. Apache BookKeeper Project [Sijie Guo / Chris] See Attachment D E. Apache Brooklyn Project [Richard Downer / Rich] See Attachment E F. Apache Buildr Project [Antoine Toulme / Jim] See Attachment F G. Apache Cassandra Project [Nate McCall / Brett] See Attachment G H. Apache Chukwa Project [Eric Yang / Mark] See Attachment H I. Apache Clerezza Project [Hasan Hasan / Brett] See Attachment I J. Apache Cocoon Project [Thorsten Scherler / Isabel] No report was submitted. K. Apache Community Development Project [Ulrich Stärk / Rich] See Attachment K L. Apache CouchDB Project [Jan Lehnardt / Shane] See Attachment L M. Apache Creadur Project [Brian E Fox / Bertrand] See Attachment M N. Apache DeltaSpike Project [Thomas Andraschko / Jim] See Attachment N O. Apache DeviceMap Project [Radu Cotescu / Marvin] See Attachment O @Marvin: Follow up with possible termination of the project P. Apache Drill Project [Parth Chandra / Chris] See Attachment P Q. Apache Empire-db Project [Rainer Döbele / Jim] See Attachment Q R. Apache Flume Project [Hari Shreedharan / Marvin] See Attachment R S. Apache Forrest Project [David Crossley / Rich] See Attachment S T. Apache Giraph Project [Avery Ching / Isabel] See Attachment T U. Apache Gora Project [Lewis John McGibbney / Mark] No report was submitted. V. Apache Groovy Project [Guillaume Laforge / Brett] See Attachment V W. Apache Hama Project [Edward J. Yoon / Bertrand] See Attachment W X. Apache HTTP Server Project [Eric Covener / Chris] See Attachment X Y. Apache HttpComponents Project [Asankha Perera / Shane] See Attachment Y Z. Apache Ignite Project [Dmitriy Setrakyan / Marvin] See Attachment Z AA. Apache Incubator Project [Ted Dunning / Chris] See Attachment AA AB. Apache jUDDI Project [Alex O'Ree / Rich] See Attachment AB AC. Apache Kafka Project [Jun Rao / Isabel] See Attachment AC AD. Apache Knox Project [Larry McCay / Jim] See Attachment AD AE. Apache Kylin Project [Luke Han / Bertrand] See Attachment AE AF. Apache Lens Project [Amareshwari Sriramadasu / Mark] See Attachment AF AG. Apache Libcloud Project [Tomaž Muraus / Brett] See Attachment AG AH. Apache Logging Services Project [Ralph Goers / Shane] See Attachment AH AI. Apache ManifoldCF Project [Karl Wright / Marvin] See Attachment AI AJ. Apache Marmotta Project [Jakob Frank / Chris] See Attachment AJ AK. Apache MetaModel Project [Kasper Sørensen / Brett] See Attachment AK AL. Apache MINA Project [Jean-François Maury / Rich] See Attachment AL AM. Apache Oltu Project [Antonio Sanso / Shane] See Attachment AM AN. Apache Oozie Project [Robert Kanter / Jim] See Attachment AN AO. Apache Open Climate Workbench Project [Michael James Joyce / Bertrand] No report was submitted. AP. Apache Perl Project [Philippe M. Chiasson / Isabel] No report was submitted. AQ. Apache Phoenix Project [James R. Taylor / Mark] See Attachment AQ AR. Apache POI Project [Dominik Stadler / Marvin] See Attachment AR AS. Apache Qpid Project [Robbie Gemmell / Brett] See Attachment AS AT. Apache REEF Project [Markus Weimer / Shane] See Attachment AT AU. Apache River Project [Patricia Shanahan / Jim] See Attachment AU AV. Apache Roller Project [Dave Johnson / Rich] See Attachment AV AW. Apache Santuario Project [Colm O hEigeartaigh / Bertrand] See Attachment AW AX. Apache Serf Project [Bert Huijben / Chris] See Attachment AX AY. Apache SIS Project [Martin Desruisseaux / Mark] See Attachment AY AZ. Apache Spark Project [Matei Zaharia / Isabel] See Attachment AZ @Shane: Follow up with PMC and legal regarding potential trademark issues with a vendor BA. Apache Stanbol Project [Fabian Christ / Jim] See Attachment BA BB. Apache Stratos Project [Lakmal Warusawithana / Marvin] See Attachment BB @Marvin: Discuss retirement with PMC: need to discuss on dev/user list BC. Apache Subversion Project [Evgeny Kotkov / Mark] See Attachment BC BD. Apache Synapse Project [Hiranya Jayathilaka / Rich] See Attachment BD BE. Apache Syncope Project [Francesco Chicchiriccò / Shane] See Attachment BE BF. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Brett] See Attachment BF BG. Apache TomEE Project [David Blevins / Bertrand] No report was submitted. BH. Apache Turbine Project [Thomas Vandahl / Chris] See Attachment BH BI. Apache Usergrid Project [Todd Nine / Isabel] See Attachment BI BJ. Apache Velocity Project [Nathan Bubna / Mark] See Attachment BJ BK. Apache Whimsy Project [Sam Ruby / Bertrand] See Attachment BK BL. Apache Xalan Project [Steven J. Hathaway / Jim] See Attachment BL BM. Apache Xerces Project [Michael Glavassevich / Isabel] No report was submitted. BN. Apache XML Graphics Project [Glenn Adams / Brett] See Attachment BN Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache APR Project Chair WHEREAS, the Board of Directors heretofore appointed Jeff Trawick (trawick) to the office of Vice President, Apache APR, and WHEREAS, the Board of Directors is in receipt of the resignation of Jeff Trawick from the office of Vice President, Apache APR, and WHEREAS, the Project Management Committee of the Apache APR project has chosen by vote to recommend Nick Kew (niq) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jeff Trawick is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache APR, and BE IT FURTHER RESOLVED, that Nick Kew be and hereby is appointed to the office of Vice President, Apache APR, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache APR Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Synapse Project Chair WHEREAS, the Board of Directors heretofore appointed Hiranya Jayathilaka (hiranya) to the office of Vice President, Apache Synapse, and WHEREAS, the Board of Directors is in receipt of the resignation of Hiranya Jayathilaka from the office of Vice President, Apache Synapse, and WHEREAS, the Project Management Committee of the Apache Synapse project has chosen by vote to recommend Isuru Udana (isudana) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Hiranya Jayathilaka is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Synapse, and BE IT FURTHER RESOLVED, that Isuru Udana be and hereby is appointed to the office of Vice President, Apache Synapse, 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 Synapse Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache Geode 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 data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Geode Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Geode Project be and hereby is responsible for the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. RESOLVED, that the office of "Vice President, Apache Geode" 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 Geode Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Geode 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 Geode Project: * Anilkumar Gingade * Anthony Baker * Ashvin Agrawal * Avinash Dongre * Barrett Oglesby * Bruce Schuchardt * Dan Smith * Darrel Schneider * Dave Barnes * Eric Shu * Greg Chase * Hitesh Khamesra * Jason Huynh * Jens Deppe * Jianxia Chen * Jinmei Liao * John Blum * Karen Miller * Konstantin Boudnik * Kirk Lund * Mark Bretl * Nabarun Nag * Niall Pemberton * Nitin Lamba * Roman Shaposhnik * Sai Boorlagadda * Swapnil Bawaskar * Udo Kohlmeyer * William Markito * Xiaojian Zhou NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl be appointed to the office of Vice President, Apache Geode, 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 Geode 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 Geode Project; and be it further RESOLVED, that the Apache Geode Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Geode podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Geode podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache Geode Project, was approved by Unanimous Vote of the directors present. D. Terminate the Apache DeviceMap Project WHEREAS, the Project Management Committee of the Apache DeviceMap 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 DeviceMap project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache DeviceMap 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 DeviceMap Project; and be it further RESOLVED, that the office of "Vice President, Apache DeviceMap" is hereby terminated; and be it further RESOLVED, that the Apache DeviceMap PMC is hereby terminated. Special Order 7D, Terminate the Apache DeviceMap Project, was tabled. E. Establish Infrastructure Administrator as an Officer WHEREAS, the President has created a position known as Infrastructure Administrator and appointed Greg Stein to fill that position; and WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation to appoint the Infrastructure Administrator as an officer of the Foundation. NOW, THEREFORE, BE IT RESOLVED, that Greg Stein, as Infrastructure Administrator, is hereby an officer of the Foundation, to serve in accordance with and subject to the direction of the President and the Bylaws of the Foundation. Special Order 7E, Establish Infrastructure Administrator as an Officer, was approved by Unanimous Vote of the directors present. F. Change the Apache Samza Project Chair WHEREAS, the Board of Directors heretofore appointed Chris Riccomini (criccomini) to the office of Vice President, Apache Samza, and WHEREAS, the Board of Directors is in receipt of the resignation of Chris Riccomini from the office of Vice President, Apache Samza, and WHEREAS, the Project Management Committee of the Apache Samza project has chosen by vote to recommend Yi Pan (nickpan47) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Chris Riccomini is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Samza, and BE IT FURTHER RESOLVED, that Yi Pan be and hereby is appointed to the office of Vice President, Apache Samza, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7F, Change the Apache Samza Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * Brett: What are the next steps to resolve the issues? [ Chukwa 2016-07-20 ] Status: Chukwa PMC participated to solve released issue, Chukwa 0.8.0 was release on August 2016. Lack of community, seems like irreverisble trend that has looming around Chukwa for years. PMC chair proposed project name change to improve brand name image. * Jim: Discuss new committers discussion with PMC [ Clerezza 2016-08-17 ] Status: PMC contacted. Will follow-up * Greg: follow up to make sure infra understand exactly what will be done and whether we want to use this as an example of services that infra can support [ CloudStack 2016-09-21 ] Status: JIRA tracking this in INFRA * Shane: follow up to see that the PMC is responsive to comments [ Helix 2016-09-21 ] Status: Basic answer supplied; originally they weren't sure how (which list) to reply to board questions. * Marvin: give feedback to PMC regarding bringing on new committers [ Pig 2016-09-21 ] Status: PMC contacted. In progress. * Shane: report back on resolving the hadoop trademark enforcement issues. [ Hadoop 2016-10-19 ] Status: In progress; have some specific plans and looking towards using some new tooling to ensure we can show what's happening going forward. * Shane: pursue a report for Stanbol; check on the status of the new chair discussions [ Stanbol 2016-10-19 ] Status: Report submitted; PMC still hoping to find new chair. * Mark: pursue a report for Synapse and request for a new chair [ Synapse 2016-10-19 ] Status: Complete. We have a report and a resolution for a new chair to consider for the November meeting. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:20 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] Interim VP, TAC Report: • Busy month working on the final details and distributing that information to the TACers • Working on a solution for an online schedule so the TACers can pick the sessions they wish to attend/chair. Having it online is more efficient than working off of paper copies, and by doing so, everyone at any given time knows who is the session host of what session. This is important in the event of schedule clashes/missing session host/etc. so that we can get a new host assigned immediately. • Setup a HipChat channel for onsite communication • In addition to the TAC session host responsibilities, the recipients will also be responsible for setting up the digital audio recordings in each room every morning and retrieving them at the end of the day • Preliminary numbers show we are under budget EA Report: Most of the month was spent on TAC ApacheCon: • Recently discovered that the booth is only up for two days – Tuesday and Wednesday • Travel, hotel, and registration completed for the new Infra hires ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] * ISSUE FOR THE BOARD: Budget overrun. * OTHER OPERATIONS: Very busy; more issues arise than we have volunteers able to provide useful answers. * BUDGET Brand is currently overspending compared to the last board-approved annual budget, both in the short term, and for the foreseeable future given known and likely requests from projects and podlings. There are two factors that have almost completely hidden the true cost of brand from us before quite recently, meaning that most expectations in the past of what we get vs. what we pay were unrealistic: 1- Originally, counsel provided essentially all services pro bono, only passing on actual registration application fees. In mid-2015, counsel move us to a new retainer which charges for services at a discount rate, and generally ensures a flat cap of $5K per month for legal services to limit our budget exposure. Note that this also seems to limit the rate at which some work is accomplished as well. 2- Due to a billing error, 5 months of past bills were never sent until just this month. Thus we have an additional $18k due this month for services rendered in the past; however once this is covered future bills should be much more even. To provide services that projects and podlings are asking for, an estimated monthly run rate is $6K/month. This accounts for $5K of services from primary counsel monthly, plus the occasional registration application fees; plus the rare fees from outside counsel where primary counsel aren't able to directly represent us. * OPERATIONS Along with the extra discussions spilling over about two major projects the board has shown concern over in the recent past, a wide variety of questions continues to come into trademarks@ from both our projects and outside parties. Providing timely, polite, and correct answers or guidance to all requests is no longer something sustainable with volunteers. While some of these questions are mostly answered by existing documentation, it's clear that the documentation isn't widely known. Separately, many of these questions are not covered by documentation, and we don't always have volunteers who can provide consistent, clear, and appropriate answers. Unlike with code checkins, providing an incorrect answer sometimes results in bad results that *cannot* easily be corrected. To ensure at least our "how to deal with an infringement" documentation is usable, we are working on an experiment with the Hadoop PMC to have them use the docs (and ask questions/suggest improvements) to start contacting some of the existing misuses of their brand. * CONFERENCES I will be presenting at ApacheCon Seville on three topics: - Improving your Apache Project's Image and Brand - Practical Trademark Law For FOSS Projects - Successfully Profiting From Apache Projects And Brands All slides will be posted on our resources page after the conference: https://www.apache.org/foundation/marks/resources * LICENSES / REGISTRATIONS Still finalizing conference branding contract, will be signed as soon as it reflects our current v1.3 Event branding policy. Registration applications are in process per request from Hadoop, Hive, Bigtop, and Tez PMCs in the US and Tomcat PMC for international jurisdictions. - Shane ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities are getting back to normal. No issues require the board attention. We continued to get new sponsors at bronze and silver level. On the bronze sponsor topic, I started contacting all current bronze sponsors and inform them of the change in policy. I expect the whole process being completed before the end of November and all links restored to 'nofollow'. As Sam mentioned in his report, with the growth of the Fundation as a whole, there is more work in all operational areas, including Fundraising. While it is way below the levels required by, say, Trademarks, it's still significant and I anticipate the need for some budget to be set aside for Fundraising as well. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: we remain within budget. No payments are due at this time. II. Cross-committee Liaison: Sally Khudairi continues work with Fundraising, Brand Management, and peripherally with the Apache Incubator. She has been working with incoming ASF President Sam Ruby on various Operations-related issues, and has created a detailed call for a new logo for the Apache Incubator (awaiting the PMC to announce as of 7 October). At the request of Rich Bowen, she is also exploring channels/options for internal communications. III. Press Releases: the following formal announcement wa issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 12 October 2016 --The Apache OpenOffice Project Announces Apache® OpenOffice™ v4.1.3 IV. Informal Announcements: 7 items were published on the ASF "Foundation" Blog. 6 Apache News Round-ups were issued, with a total of 121 weekly summaries published to date. 62 items were Tweeted on @TheASF. No new videos have been added to the ASF YouTube channel. Sally continues to tweet for the Apache Incubator account. V. Future Announcements: two announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 11 media queries, plus two dedicated requests for high-res graphics of 23 Apache projects in total for industry-specific reports. The ASF received 1,172 press clips vs. last month's clip count of 1,997. Media coverage of Apache projects yielded 4,553 press hits vs. last month's 4,882. Our clipping service contract has been confirmed through December 2017. VII. Analyst Relations: we responded to 1 analyst query. Apache was mentioned in 39 reports by Gartner (6 Magic Quadrants), 13 reports by Forrester, 22 reports by 451 Research, and 11 reports by IDC. VIII. ApacheCon liaison: Sally is leading media/analyst training at ApacheCon, with Fintan Ryan of RedMonk conducting the analyst briefings. She is also coordinating 5 interviews and was tasked with managing on-site Apache Big Data + ApacheCon press activities by the conference producer's PR team team 2 business days before the event. As this activity is the responsibilty of the conference producer and not the ASF, Sally has addressed this with Rich Bowen. IX. (Non-ASF) Industry Events and Outreach liaison: No formal conference-related activities planned at this time, however, Sally is working with Melissa Warnkin and Sharan Foga on an overall inventory of ASF promotional products that can be used across various events. X. Newswire accounts: we have 30 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] Additions to Infrastructure =========================== Sebastian Bazley (sebb, apmail karma) Freddy Barboza (fbarboza) Chris Thistlethwaite (christ) Christofer Dutz (cdutz) In addition to the above karma grant; our two new staff members are ramping up. (Freddy Barboza and Chris Thistlethwaite) Expect forthcoming blog posts from our three recent hires on the infra blog. Operations Action Items ======================= Short Term Priorities ===================== - Ensuring we have gathered enough information to begin the Gitbox experiments. - Making sure the new wiki instance is running smoothly - Introducing new staffers to the infrastructure - Networking/F2F meetings at ApacheCon Europe - Further work on rebranding our new web site Long Range Priorities ===================== - Stand up a service for mirroring repositories and events from GitHub - 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 decommissioning - Deprecate eos (currently only running mail-archives, wiki was moved) - Work on weaving podlings into LDAP - Further explore identity management proposals General Activity ================ - moin wiki (wiki.apache.org) was moved to a new, faster box and inactive accounts were pruned to greatly increase responsiveness. - More package consolidation and updates on the Jenkins platform - Fixed issues with the buildbot configuration scanner not working as intended. - Stood up buildbot and jenkins setup for publishing web sites via git. - Moved more VMs from vCenter to new cloud locations. - gitbox (stage two of our github experiment) has been stood up as an actual machine, with some services working already. We expect to be able to start mirroring and gathering push logs in the coming month. - In conjunction with gitbox, reworked the overall design of our writeable git repository web interface (and received positive feedback). - Reworked policy for new git repositories so that new repositories are automatically mirrored and have github integrations enabled by default. - Worked on a new web site for infrastructure. Some components can be used for projects wishing to switch to a git-based automated workflow. - Added and fixed a bunch of jenkins build nodes. - Debugged and (hopefully??) fixed some issues with our pubsub systems - Consolidation, general sanity checks and harmonization of Jenkins builds. Ticket Response and Resolution Targets ====================================== Stats for the current reporting cycle can be found at https://status.apache.org/sla/jira/?cycle=2016-11 The tentative goal of having 90% of all tickets fully resolved in time is still being used. We are hoping that the onboarding of new staff will help greatly improve these stats. Uptime Statistics ================= Uptime this month was mostly affected by the moin wiki, which we have now moved. We expect next month to have a much better uptime than this month (99.79%) For detailed statistics, see http://status.apache.org/sla/ Github as Master ================ Sam asked us to report on this process. To date, we've finished our discussion with Legal Affairs to ascertain the framework that things have to operate in. Additionally, we've started discussions on private@ about the ASF-side of that work. You can see the documentation from that discussion: https://pad.apache.org/p/gitbox We have an instance running in AWS (the "gitbox") to run the above. Finally, we've identified an initial project to subject to the experiment. 'Costs per project' Project =========================== Sam has asked to focus on looking at ways to reduce the straight linear expansion of costs for each additional project that we add. To date, this remains a bit of a thought experiment on both how to measure the costs in a more granular way than we do now. Currently the data that we have shows a correlation between increase in requests for service, bandwidth, etc. This correlation has led to our existing planning/staffing models, but there remains much to be done on this front. The goals for next month is to figure out our what specific points we need to be measuring, and ideally looking backwards to validate what the actual rate per project is in terms of consumption. The goal for Q1 is to break that down, and figure out what the constraints of the current onboarding and ongoing operations are. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Rich Bowen] Summary: ApacheCon Seville has a modest turnout, and I've started to turn my attention to making Miami a much more successful event. In particular, we (I) need to do a better job of communicating to our internal audience what's coming, and how to get involved. As we speak, ApacheCon is in process. Several of us are attending the call together here in Seville. We have 550 attendees at the two events, of which 136 registered as committers. This tells me that we are not doing an adequate job of communicating about the event with our project communities -- something I intend to rectify for ApacheCon North America in May. Sponsorship this year has been disappointing, and here, too, I have heard frequently this week from people who said that they would have sponsored if they had known about it earlier. It appears that our internal communication needs a great deal of improvement in the coming six months. ApacheCon North America (And Apache: Big Data) will be held in Miami, May 16-18th, 2017, at the InterContinental Miami. The websites for these events are now up, at http://events.linuxfoundation.org/events/apachecon-north-america and http://events.linuxfoundation.org/events/apache-big-data-north-america respectively. I am working on the Apache Events page, at http://apache.org/events , in an attempt to make it more engaging to the community, and encourage communities to more effectively publicize their events, from the meetup scale all the way up to major conferences. I've refreshed http://apachecon.com/ to make it much clearer what the most important things are, and move distractions to sub-pages. I am working on an ApacheCon playbook - https://svn.apache.org/repos/private/foundation/ApacheCon/playbook.md to ensure that tasks don't get dropped in future events, as well as to make it easier for people to know where they can be of help, without getting in the way of the event producer. It is also hoped that this will assist other events that our project communities put on. This playbook will be forked, so to speak, for each event, to act as a checklist to ensure that everything gets done. We had a meeting with Linux Foundation, the conference produder, on Tuesday morning at ApacheCon in Seville. Present were Sally Khudairi, Sharan Foga, Jillian Hall (LF), Angela Brown (LF), Shane Curcuru, David Nalley, Nick Burch, and myself - Rich Bowen. Many issues were discussed, primarily focused on the events in 2017. ApacheCon and Apache: Big Data will be held overlapping in Miami - that is, both events will run Tuesday through Thursday, May 14-16. This saves money on space, and also increases the event population on any given day, which makes sponsors happier, as well as giving attendees a greater chance of interacting with other members of the community. Attendees who register for one event receive a complimentary pass to the other event. This is done primarily for tracking purposes - to see which event people are primarily interested in. Monday will be available for projects to have developer summits. Information about this will go out to various Foundation-wide mailing lists in the next 2 weeks, once we know how many of these events we have space for. The focus/theme of the event will be innovation. Projects in the incubator, or recently graduated, will be particularly encouraged to bring their content to the event. More established projects will, of course, also be welcomed, but are encouraged to consider the project summit route as a possible alternative. Tighter communication will be established between LF and ASF for the coming six months, so that fewer things are dropped on the marketing side of things. On my side, I'll be attempting to include a broader team into the process. While I will remain the primary point of contact, I will be more proactively delegating tasks out to a wider group. I encourage people who are passionate about ApacheCon to contact me to offer their time to this endeavor. Ideas were pitched including using Foundation funds to help committers or PMC members to attend who might not otherwise be able to do so. These ideas are still very nascent, and will be fleshed out more on the comdev mailing list before being brought as a proposal to the board. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Nick Burch] ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 9: Report from the Apache Legal Affairs Committee [Jim Jagielski] During the last month, 2 items of note were discussed and resolved. First was the categorization of the JSON "Don't Be Evil" license and the other was related to the NetBeans Incubation Proposal. Regarding the former, it was decided that the JSON license, not, by definition, being an "open source license" (since it is not approved by OSI) is, in fact, CatX. Regarding the latter, the difference between hard and soft depedencies were further clarified. No issues requiring board attention. ----------------------------------------- Attachment 10: Report from the Apache Security Team Project [Mark J. Cox] The team is still trying to followup on issues reported via security@ to projects that do not seem to have been dealt with. While in many cases this leads to action (or formally closing an issue), there are still some without action which we will raise to the board in due course. We're hoping to find better automated methods of tracking and reporting on these. Stats for October 2016: 2 CVEs issued to projects (some may not be public yet). e-mails to security@ 15 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to "Apache" mentioned in OSS licenses 1 Security vulnerability question, but not a vulnerability report 2 Support question 1 Direct Vulnerability report to security@apache.org 1 [site] 7 Vulnerabilities reported to projects 1 [zookeeper] 1 [tomcat] 2 [hadoop] 2 [aoo] 1 [cloudstack] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] ----------------------------------------- Attachment B: Report from the Apache Ambari Project [Yusaku Sako] ## Description: - Apache Ambari simplifies provisioning, managing, and monitoring of Apache Hadoop clusters. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last board report in August 2016, the community pushed two releases: 2.4.0 and 2.4.1. 2.4.0 was a significant release involving resolution of more than 2200 JIRAs from 90+ contributors. 2.4.1 was a stability release with a few dozen critical fixes. Jayush Luniya (PMC member/committer) gave a talk titled "Streamline Hadoop DevOps with Apache Ambari" at Hadoop Summit Tokyo on Oct 27, 2016. ## PMC changes: - Currently 42 PMC members. - Bob Nettleton was added to the PMC on Thu Aug 18 2016 ## Committer base changes: - Currently 77 committers. - New commmitters: - Bosco was added as a committer on Fri Aug 26 2016 - Prajwal Rao was added as a committer on Tue Aug 23 2016 - Sangeeta Ravindran was added as a committer on Sun Nov 06 2016 ## Releases: - 2.4.0 was released on Fri Aug 26 2016 - 2.4.1 was released on Sun Sep 11 2016 ## Mailing list activity: - dev@ambari.apache.org: - 259 subscribers (up 18 in the last 3 months): - 101 emails sent to list (132 in previous quarter) - issues@ambari.apache.org: - 37 subscribers (up 6 in the last 3 months): - 7793 emails sent to list (13483 in previous quarter) - reviews@ambari.apache.org: - 40 subscribers (up 2 in the last 3 months): - 2678 emails sent to list (4988 in previous quarter) - user@ambari.apache.org: - 460 subscribers (up 10 in the last 3 months): - 96 emails sent to list (158 in previous quarter) ## JIRA activity: - 758 JIRA tickets created in the last 3 months - 674 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment C: Report from the Apache Ant Project [Jan Matèrne] ## Description: 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 ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The main development activity is on support of Java9 in Ant Core. Actually we focus on and the new Java module system (Jigsaw). Work is ongoing. - Most of the development is done by the actual committer base, so there aren't any new committers on the horizon. - Small changes are coming in over Github. ## Health report: - While gathering the information for the report we had a look at the project health. While discussing the consensus is that we can't support IvyDE and EasyAnt any more and having difficulties in maintaining Ivy. - For Ivy we hope to activate new, reactivate old committers and get a new release manager with git knowledge. - IvyDE is useful for some users but requires more work than we could spent. We tend to move this to the attic, but there wasnt a formal vote yet. - EasyAnt never got that impact and the community. We never got a real release out, so moving that to the attic is maybe the next step. But again: there wasn't a formal vote yet. ## PMC changes: - Currently 21 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Louis Boudart on Thu Dec 12 2013 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Stephen Haberman at Tue Oct 13 2015 ## Releases: - Last releases were - Ant 1.9.7 on Tue Apr 12 2016 - Ivy 2.4.0 on Fri Dec 26 2014 - IvyDE 2.2.0 on Fri Nov 22 2013 - EasyAnt 0.9-incubating Sat Feb 23 2013 ## Mailing list activity: - Mailing list numbers are relatively stable over the last month. Everything is healthy but with low activity. - dev@ant.apache.org: - 291 subscribers (down -8 in the last 3 months): - 126 emails sent to list (58 in previous quarter) - ivy-user@ant.apache.org: - 356 subscribers (down -4 in the last 3 months): - 12 emails sent to list (17 in previous quarter) - notifications@ant.apache.org: - 61 subscribers (down -3 in the last 3 months): - 312 emails sent to list (326 in previous quarter) - user@ant.apache.org: - 700 subscribers (down -9 in the last 3 months): - 14 emails sent to list (22 in previous quarter) ## Bugzilla Statistics: - 17 Bugzilla tickets created in the last 3 months - 8 Bugzilla tickets resolved in the last 3 months ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment D: Report from the Apache BookKeeper Project [Sijie Guo] BookKeeper is a distributed, reliable, and high performance logging service. It has been used as a fundamental service to build high available and replicated services in companies like Twitter, Yahoo and Salesforce. It is also the log segment store for Apache DistributedLog (incubating). ## Issues: There are no issues requiring board attention at this time ## Activity: The mailing list activity has dropped and we attribute it to the split attention between Apache BookKeeper and the incubating project Apache DistributedLog. They are closely related given that DistributedLog uses BookKeeper as a building block for storing logs. Despite the drop of mailing list activity, there has been good discussion around upcoming features and improvements to the project. The community started organizing bi-weekly calls where everyone is invited to join. The goal is not to make decisions outside the mailing list and jira, but instead to have a better understanding of current proposals and problems that users of the project are facing. The community is also organizing a meetup that will happen in November. ## Health report: The community is making good progress. We have been having healthy discussions around issues and features and there are a few contributors on track to become. We haven't had a release in a while and we are targeting one for December 2016. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Matteo Merli on Thu May 26 2016 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was JV Jujjuri at Thu Jun 09 2016 ## Releases: - Last release was 4.4.0 on Mon, 16 May 2016 ## Mailing list activity: The number of subscribers has been going up slightly. The drop in the traffic of the dev list we attribute to the split attention between the two related projects we mention above. - dev@bookkeeper.apache.org: - 77 subscribers (up 4 in the last 3 months): - 276 emails sent to list (512 in previous quarter) - issues@bookkeeper.apache.org: - 6 subscribers (up 0 in the last 3 months) - user@bookkeeper.apache.org: - 96 subscribers (up 4 in the last 3 months): - 12 emails sent to list (19 in previous quarter) ## JIRA activity: - 23 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Brooklyn Project [Richard Downer] ## Description: - Apache Brooklyn Project is a software framework for modeling, monitoring and managing cloud applications through autonomic blueprints. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Development continues with a regular turnover of pull requests submitted and merged. ## Health report: - The project continues with a similar level of activity that we have seen recently. There is a regular turnover of pull requests and commits, and JIRA tickets, showing that development is at a healthy pace and that users are feeding back their problems and feature suggestions. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Baptiste Onofré and Olivier Lamy, who converted their mentor status to committer/PMC member on graduation. ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Potential new committers are being discussed on the private list; a vote is expected to get underway shortly. - Last committer addition was Jean-Baptiste Onofré and Olivier Lamy, who converted their mentor status to committer/PMC member on graduation. ## Releases: - No new releases since last report. - 0.9.0 was released on Mon Apr 18 2016 ## JIRA activity: - 56 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment F: Report from the Apache Buildr Project [Antoine Toulme] ## Description: Apache Buildr is a build system for Java-based applications, including support for Scala, Groovy and a growing number of JVM languages and tools. We wanted something that’s simple and intuitive to use, so we only need to tell it what to do, and it takes care of the rest. But also something we can easily extend for those one-off tasks, with a language that’s a joy to use. And of course, we wanted it to be fast, reliable and have outstanding dependency management. ## Issues: There are no issues requiring board attention at this time. ## Activity: Over the last 6 months, we have resolved most of the open bugs. We have released 1.5 on Friday, September 23rd with better support for Java 8 and Scala 2.11 and are looking to release 1.5.1 by the end of the year. ## Health report: The activity is slow, with 2 active committers. The activity on the mailing lists is better than last quarter, with a few discussions on the user list. We do see that the project is used at large. For example, the latest version has been downloaded over 7000 times, one month after its official release. We have started discussing on the dev list how to improve participation, and have detailed several items for the next release to engage better our users. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Peter Donald on Tue Oct 15 2013 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Tammo van Lessen at Fri Aug 08 2014 ## JIRA activity: - 15 JIRA tickets created in the last 3 months - 29 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment G: Report from the Apache Cassandra Project [Nate McCall] ## Description: The past couple of months have been difficult for us. For posterity, the August [0] and September[1] board agendas provide details of changes affecting the project and subsequent PMC efforts to address board requested action items. We will continue to work constructively with the board on the points therein. With that said, we would like to express not only our optimism (more below) but our thanks to those within the ASF who have spent substantial amounts of time to help us get moving in the right direction. Of particular note have been the ongoing efforts Mark Thomas and Jake Farrell. Without them, it would have been much more difficult to deduce what to do next and how to go about doing it. For everyone else, a large thank you as well. If nothing else, it's clear we all care very deeply about having successful open source software projects. ## Issues: A long-time vendor who has been a large benefactor of the project through contribution of resources, has re-focused said resources to more internal efforts[2]. While many of their staff are still involved in day-to-day activities, it has left something of a hole for the PMC to fill in terms of handling day-to-day resourcing of issues. Discussions are ongoing on how best to do this, but we remain optimistic that the size, diversity and skill of the community are enough that we will find solutions. ## Release Activity: Apache Cassandra has had the following releases: - 2.1.16 was released on Mon Oct 10 2016 - 2.2.8 was released on Wed Sep 28 2016 - 3.8 was released on Thu Sep 29 2016 - 3.9 was released on Thu Sep 29 2016 We have recently moved trunk up to 4.0 and are currently discussing a roadmap for such on the development mailing list. Note: 3.10 and 3.0.10 were scheduled to be released, but were voted down due to a regression bug discovered by the community. ## Health report: From the past several weeks of mailing list and social media activity, one can draw the following conclusions regarding the health of Cassandra: - our large, diverse community of users care deeply about the project and are not afraid to very publicly ask hard questions - the board cares deeply about our project as can be seen by amount of effort expended in handling not only Cassandra but the larger issues brought about by the point above - the PMC wants very much to do the right thing and is doing its best to constructively move forward In short, we do not lack for passion at any level of the project. It is therefore our game to lose and we intend to put our best efforts in over the next quarter. ## PMC changes: - Currently 21 PMC members. - There are two new PMC members: - Sankalp Kohli was added to the PMC on Mon Oct 24 2016 - Michael Shuler was added to the PMC on Thu Sep 22 2016 ## Committer base changes: - Currently 38 committers. - There are three new commmitters: - Dikang Gu was added as a committer on Fri Nov 04 2016 - Sankalp Kohli was added as a committer on Tue Oct 25 2016 - Branimir Lambov was voted in and accepted, we are awaiting ICLA submission ## Mailing list activity: Activity on both dev and user mail lists have increased substantially over last quarter. We have no direct quantitative information as to why, but anecdotally it appears that we have knowledgeable users appearing more often to answer other users's questions. - dev@cassandra.apache.org: - 1582 subscribers (down -3 in the last 3 months): - 709 emails sent to list (452 in previous quarter) - Though not as high and some is resulting to larger political discussions, we still have over 60% growth in traffic. - user@cassandra.apache.org: - 3109 subscribers (down -6 in the last 3 months): - 1597 emails sent to list (901 in previous quarter) - Mail list activity has increased over 50% from the last quarter. ## JIRA activity: As discussed above in Issues we would like the number of resolved issues to be higher, but over 75% is not a bad place to be and we are actively working on getting more community involvement. - 480 JIRA tickets created in the last 3 months - 372 JIRA tickets closed/resolved in the last 3 months ## Trademark Enforcement Three requests were sent out regarding our trademarks, all of which were immediately complied with by the recipients: - Clarified appropriate use of trademark and guidelines for a third party vendor providing backports of Apache Cassandra patches to a custom long term release version [3] - Use of trademark in project name [4] - Use of trademark in project name [5] ## 'dtest' Project Contribution DataStax recently offered to donate the dtest distributed testing suite to the project [6],[7]. This was voted on in the dev mailing list and passed [8]. Filing the appropriate forms with the Incubator folks for review will be done shortly. ## References [0] https://www.apache.org/foundation/records/minutes/2016/board_minutes_2016_08_17.txt [1] https://www.apache.org/foundation/records/minutes/2016/board_minutes_2016_09_21.txt [2] http://www.datastax.com/2016/11/serving-customers-serving-the-community [3] https://lists.apache.org/thread.html/69d87a0d59a23a4ee7578563785581d5daa5cb248987d67a70c44b86@%3Cprivate.cassandra.apache.org%3E [4] https://lists.apache.org/list.html?private@cassandra.apache.org:lte=1M:Apache%20trademark%20and%20Spring%20project%20names [5] https://mesosphere.github.io/cassandra-mesos/ [6] https://github.com/riptano/cassandra-dtest [7] https://lists.apache.org/thread.html/d43300016d3871587c43eea8cd4223221904fddc7916d9d6d858bd29@%3Cprivate.cassandra.apache.org%3E [8] https://lists.apache.org/thread.html/d9e694ba8eaac8e8c70cbfd3f6ee249d43f8c67279882ffc65e56cac@%3Cdev.cassandra.apache.org%3E ----------------------------------------- Attachment H: Report from the Apache Chukwa Project [Eric Yang] ## Description:             Chukwa is an open source data collection system for monitoring         large distributed systems.      ## Activity:   - Updated site navigation - Updated Apache trademark on Chukwa website - Chukwa PMC participated to solve released issue, Chukwa 0.8.0 was release on August 2016. Lack of community, seems like irreverisble trend that has looming around Chukwa for years. PMC chair proposed project name change to improve brand name image or achieve the project. These discussion are put into vote in Chukwa private mailing list.     ## Issues: - No commerical sponsor to build momentum - Not enough people to build a community ## PMC/Committership changes:      - No new PMC members in the last 3 months. - Latest PMC addition: Tue Oct 15 2013 (Alan Cabrera) - 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:  - 0.8.0 was released on Fri Jul 15 2016        ## Mailing list activity:      - dev@chukwa.apache.org: - 90 subscribers (up 0 in the last 3 months): - 14 emails sent to list (46 in previous quarter) - user@chukwa.apache.org: - 159 subscribers (down -1 in the last 3 months): - 5 emails sent to list (0 in previous quarter)     ## JIRA activity:       - 2 JIRA tickets created in the last 3 months   - 3 JIRA tickets closed/resolved in the last 3 months  ----------------------------------------- Attachment I: Report from the Apache Clerezza Project [Hasan Hasan] DESCRIPTION Apache Clerezza is an OSGi-based modular application and a set of components (bundles) for building RESTFul Semantic Web applications and services. ISSUES FOR THE BOARD There are no issues requiring board attention at this time. RELEASE Latest release was partial-release-201604 created on May 13, 2016. ACTIVITY To ease developers in contributing to Clerezza code base, and thus as a step to attract new committers, Clerezza codes are reduced to core components in the master branch while moving the rest to a legacy branch in the git repository. COMMUNITY Latest change was addition of a new committer and PMC member on 16.08.2013. To gain new committers, an email has been sent to dev@clerezza.apache.org. Currently, there are nine PMC members in the project, where four of them are also ASF members. That should be sufficient to be a community. INFRASTRUCTURE To allow easier update of Clerezza Website, the use of Apache CMS has been suggested. ----------------------------------------- Attachment J: Report from the Apache Cocoon Project [Thorsten Scherler] ----------------------------------------- Attachment K: Report from the Apache Community Development Project [Ulrich Stärk] ## Description: The Community Development PMC is responsible for helping people become involved with Apache projects ## Issues: No issues require board attention at the moment. ## Activity: Google Summer of Code 2016 has ended and Google will be invoiced shortly. Although we applied the rules for ranking and accepting students stricter this year we still saw only 35 of the 49 projects succeeding. 6 students failed at midterm evaluation, another 7 failed during the final evaluations. The reasons for failure are numerous with lack of skills, other commitments and students simply disappearing being the most frequent. We will now discuss how to better mitigate the risks of students failing for 2017. We briefly discussed participating in Google Code-In, a project with goals similar to GSoC where high school students would work on small tasks given out by participating organizations. Concerns about the program's organization agreement and the indemnification rules in particular in the end prevented us from applying. Since a similar agreement is being used for GSoC we will submit the agreement to V.P. Legal for advice on whether it is ok to sign for GSoC 2017. Sharan Foga has written an extensive update on the encouraging diversity efforts spearheaded by her which can be found at https://s.apache.org/n097 In the past few months ComDev has operated without a clear strategy with GSoC and pointing random people into the right direction being the main tasks. An effort has been started to get a strategy/roadmap into place. ## PMC changes: The PMC currently features 22 members. The last addition has been Sharan Foga on 2016-11-15. ## Releases: None. ## Mailing list activity: A lot of discussion around guiding newcomers, ApacheCon and general community-related discussions are happening on dev@. Subscriber count is up in the past months, number of messages slightly down which is probably just usual fluctuation. GSoC-related discussions are happening on mentors@ with number of messages fluctuating with GSoC phase. ----------------------------------------- Attachment L: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: - CouchDB is a database with seamless multi-master sync that scales from Big Data to Mobile, with an intuitive HTTP/JSON API, and designed for reliability. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Shipped 2.0, 4 years in the making, 10+ years planning, finally coming together The release was a huge success, adoption, based on mailing list and JIRA traffic, is going well. - New logo (see http://couchdb.apache.org) - New slogan (see “Description” above) - Preparating for 2.0.1 and genereally faster releases (again). - Discussion about 3.0 and beyond scope. Lots of contributions. - Total of six talks at ApacheCon EU and Apache BigData EU. ## Health report: - Project is buzzing as expected. Decent update in activity post 2.0, mostly end-user support and fixing little issues. All well! ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Garren Smith on Mon Oct 19 2015 ## Committer base changes: - Currently 55 committers. - Benjamin Anderson was added as a committer on Mon Oct 31 2016 ## Releases: - 2.0.0 was released on Tue Sep 20 2016 ## JIRA activity: - 129 JIRA tickets created in the last 3 months - 55 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment M: Report from the Apache Creadur Project [Brian E Fox] Apache Creadur creates and maintains a suite of open source software related to the auditing and comprehension of software distributions. Any language and build system are welcomed. Status ------ Since the last report, email and commit activity continues to move along slowly. There has been not much other activity on the release side. Creadur is primarily used by other Apache projects to help check for conformity to ASF standards. This is why the project team is primarily comprised of members and committers from other ASF projects. The risk of the project foundering is therefore very low despite the ongoing lack of progress. If someone has an itch to scratch, it will no doubt get fixed. Community --------- In September 2016 Karl Heinz Marbaise was elected to join as PMC and Commiter. Releases -------- Apache Rat 0.12 was released in June, 2016 Apache Rat 0.11 was released in August, 2014 Apache Rat 0.10 was released in September, 2013. Community Objectives -------------------- Find more committers ----------------------------------------- Attachment N: Report from the Apache DeltaSpike Project [Thomas Andraschko] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans outside of a container. - JSF integration, including backporting of JSF 2.2 features for Java EE 6. - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. - Quartz integration Testing support is also provided, to allow you to do low level unit testing of your CDI enabled projects. ## Issues: There are no issues requiring board attention at this time. ## Activity: We released 1.7.2, which mainly contains bug fixes and documentation improvemets. Currently we improve our configuration API for the upcoming version 1.8. ## Health report: The community and developers activity was average in the last quarter. ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Harald Wellmann on Thu May 19 2016 ## Committer base changes: - Currently 33 committers. - No new committers added in the last 3 months - Last committer addition was Matej Novotny at Fri Jun 03 2016 ## Releases: - 1.7.2 was released on Sun Nov 06 2016 ## Mailing list activity: - users@deltaspike.apache.org: - 179 subscribers (up 4 in the last 3 months): - 70 emails sent to list (137 in previous quarter) - dev@deltaspike.apache.org: - 105 subscribers (down -3 in the last 3 months): - 350 emails sent to list (596 in previous quarter) ## JIRA activity: - 31 JIRA tickets created in the last 3 months - 28 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment O: Report from the Apache DeviceMap Project [Radu Cotescu] Description: Device Data Repository and classification API (established November 2014) Activity: Bertrand Delacretaz resigned from DeviceMap's PMC, leaving the PMC with only two members. Therefore, we request moving the project to Attic [0]. Health report: 2 PMC members left. The project is not viable any more. Terminate the Apache DeviceMap Project WHEREAS, the Project Management Committee of the Apache DeviceMap 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 DeviceMap project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache DeviceMap 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 DeviceMap Project; and be it further RESOLVED, that the office of "Vice President, Apache DeviceMap" is hereby terminated; and be it further RESOLVED, that the Apache DeviceMap PMC is hereby terminated. PMC changes: Currently 2 PMC members, after processing's Bertrand Delacretaz's resignation. Committer base changes: Currently 13 committers. No new committers added in the last 3 months Last committer addition was Volkan Yazici at Thu Apr 23 2015 Releases: Last release was devicemap-client-vbnet 1.0.1 on Thu Oct 01 2015 JIRA activity: 6 JIRA tickets created in the last 3 months 8 JIRA tickets closed/resolved in the last 3 months [0] - https://lists.apache.org/thread.html/4ab7605e3bacb2a180edd9be8b343b300ea1db99b45362b95cd37339@%3Cdev.devicemap.apache.org%3E ----------------------------------------- Attachment P: Report from the Apache Drill Project [Parth Chandra] ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage ## Issues: - There are no issues requiring board attention at this time ## Activity: - Since the last board report, Drill has released version 1.8 - Drill has added many new features reffered to in the last report. Dynamic UDFs, Parquet reader performance improvements, filter pushdown for Parquet, and improved support for Metadata in the clients has been added. - Improved use of statistics, and security enhancements (including support for Kerberos) continue to be in the works. Also in progress is an improvement to the data locality algorithm. ## Health report: - There has been a good increase in the number posts in the dev and jira lists. This reflects the increased activity on the development front. User list activity is down this period, but not a concern at the moment. ## PMC changes: - Currently 18 PMC members. - Sudheesh Katkam was added to the PMC on Wed Oct 05 2016 ## Committer base changes: - Currently 28 committers. - No new committers added in the last 3 months - Last committer addition was Hsuan-Yi Chu at Thu Apr 07 2016 ## Releases: - 1.8.0 was released on Mon Aug 29 2016 ## Mailing list activity: - dev@drill.apache.org: - 436 subscribers (down -10 in the last 3 months): - 1797 emails sent to list (1231 in previous quarter) - issues@drill.apache.org: - 20 subscribers (up 0 in the last 3 months): - 2188 emails sent to list (1550 in previous quarter) - user@drill.apache.org: - 567 subscribers (down -14 in the last 3 months): - 436 emails sent to list (824 in previous quarter) ## JIRA activity: - 173 JIRA tickets created in the last 3 months - 88 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache Empire-db Project [Rainer Döbele] Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project --------------------------- We have completed the work for our upcoming release and are currently voting on a release candidate. Changes in committers or PMC members -------------------------------------------------- There have been no changes in committers or PMC members during the last months. Issues -------- There are no issues that require the board's attention at this time. Releases ----------- Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015. ----------------------------------------- Attachment R: Report from the Apache Flume Project [Hari Shreedharan] DESCRIPTION Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. RELEASES * The last release of Flume was version 1.7.0, released on October 16, 2016. * No other releases are planned at this time. CURRENT ACTIVITY: * Project activity has picked up over the past few months, and a number of new contributors are active contributing code, reviews and responding to user and developer queries on mailing lists. * A total of 52 issues have been filed, and 40 issues have been resolved between the period starting August 8, 2016 and November 6, 2016. * Approximately 978 messages were exchanged on the dev list in the past three months, while a total of 52 were exchanged on the user list in this period. COMMUNITY * Two new committers, Balazs Donat Bessenyei and Jeff Holoman were elected to the project on September 21, 2016. * The last time a new PMC member was elected for the project was on November 4, 2014. * Currently there are: - Total of 292 subscribers to the developer list - Total of 687 subscribers to the user list - Total of 28 committers - Total of 21 PMC members ISSUES * There are no issues requiring board attention at this time. ----------------------------------------- Attachment S: Report from the Apache Forrest Project [David Crossley] Apache Forrest mission is software for generation of aggregated multi-channel documentation maintaining a separation of content and presentation. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2013-04-08 Most recent addition: 2009-06-09 New committers: None. Most recent addition: 2009-06-09 None on the horizon. General status: The most recent release is 0.9 on 2011-02-07. Since then there have been some changes, but it will need someone to initiate the release process. No activity on the user mail list. However it never gets used much anyway. There was some activity on the dev mail list. One PMC member continued development of the new "fleece" skin and related issues, and enquiries about integrating external components. Two other PMC members assisted with suggestions. Four PMC members were present during the quarter. At this report, no other PMC members responded to my draft report. The presence of some during the quarter, indicates that there should be sufficient people hanging around for us to potentially be able to make a decision or encourage new contributors. Project status: Activity: Low 3+ people have indicated presence, so has sufficient oversight. Security issues published: None. Progress of the project: Continued minor development of the "fleece" bootstrap-based skin. ----------------------------------------- Attachment T: Report from the Apache Giraph Project [Avery Ching] Giraph is a Bulk Synchronous Parallel framework for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. Project releases * Sergey and Roman completed the Giraph 1.2.0 release that includes the Blocks & Pieces framework, OOC processing, and Facebook configuration (https://blogs.apache.org/giraph/entry/giraph_1_2_0_release) * No immediate plans for an upcoming new release Overall project activity since the last report * Published a comparison between Giraph/GraphX https://code.facebook.com/posts/319004238457019/a-comparison-of-state-of-the-art-graph-processing-systems/ * Lots of repo clean up in preparation for the 1.2.0 release * Continued bug fixes When were the last committers or PMC members elected? ** Hassan Eslami (Committer) on 7/15/2016 ** Sergey Edunov (PMC) on 8/15/2016 Mailing list members * Our mailing list is stable (not much change from the last report) ** user@ 470 -> 465 ** dev@ 280 → 279 ----------------------------------------- Attachment U: Report from the Apache Gora Project [Lewis John McGibbney] ----------------------------------------- Attachment V: Report from the Apache Groovy Project [Guillaume Laforge] ## Description: Apache Groovy is a multi-faceted programming language for the Java platform. Groovy is a powerful, optionally typed and dynamic language, with static- typing and static compilation capabilities, aimed at multiplying developers’ productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain- Specific Language authoring, runtime and compile-time meta-programming and functional programming. ## Issues: Still on the agenda: further work on the release process, to improve automation while respecting the Apache guidelines. The community is impatient for new releases, so we need to line up our ducks to be able to give a fresh cut to our community, as well as allowing them to try the new features of Groovy 2.5. ## Activity: Thanks to our new committer, there's lots of energy and discussions around the development of the new parser for Groovy, covering the Java 8 syntax features, and discussing additional elements. This quarter, 160 commits were contributed from 26 contributors including 19 non-committer contributers, 13 of which were new. The number of tickets open and closed has significantly augmented, but we are closing at least as many as are being opened. The user mailing-list seems to have slowed down a little, but the dev list has seen a nice increase, likely thanks to the renewed activity around the new parser. On the more social aspects, the @ApacheGroovy Twitter account is close to reach its 2k followers (1995 at the time of this writing). The LinkedIn Groovy user group reaches 4717 members. Groovy is still in the top 20 of the TIOBE index, with rank 18. The previous month, the site indicated both Groovy and Go to have seen the biggest increase the past year. A Slack channel for the Groovy ecosystem has been created by the community and has over 400 members. The Groovy community will gather soon at the G3 Summit conference dedicated to the Groovy ecosystem, in Florida, at the end of the month. ## Health report: The project is healthy, and we're happy to have Daniel Sun join our ranks as new committer to the team. The downloads are still going strong, as we have now surpassed the 2 million downloads per month. From January to October included, we are now at over 18 million downloads for this year (compared to 12.7M in 2015). ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrew Bayer on Wed Nov 18 2015 ## Committer base changes: - Currently 17 committers. - Daniel Sun was added as a committer on Thu Nov 03 2016 ## Releases: - 2.4.7 was released on Tue Jun 07 2016 - 2.4.6 was released on Feb 22 2016 - 2.4.5 was released on Sept 17 2015 - 2.4.4 was released on Jul 09 2015 - 2.4.3 was released on Mar 23 2015 ## Mailing list activity: - users@groovy.apache.org: - 381 subscribers (up 7 in the last 3 months): - 210 emails sent to list (301 in previous quarter) - dev@groovy.apache.org: - 217 subscribers (up 6 in the last 3 months): - 388 emails sent to list (263 in previous quarter) - issues@groovy.apache.org: - 9 subscribers (up 0 in the last 3 months) - notifications@groovy.apache.org: - 31 subscribers (up 3 in the last 3 months): - 1212 emails sent to list (935 in previous quarter) ## JIRA activity: - 94 JIRA tickets created in the last 3 months - 97 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment W: Report from the Apache Hama Project [Edward J. Yoon] ## Description: - Apache Hama is a framework for Big Data analytics which uses the Bulk Synchronous Parallel (BSP) computing model, which was established in 2012 as a Top-Level Project of The Apache Software Foundation. ## Issues: - there are no issues requiring board attention at this time ## Activity: - "Apache Hama: An Emerging BSP Computing Framework for Big Data Applications" has accepted at IEEE ACCESS - We elected new committer JongYoon Lim ## Health report: - The jira and mailing list traffic decreasing. We are continuing effort to making community healthier. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Behroz Sikander on Mon Feb 01 2016 ## Committer base changes: - Currently 17 committers. - JongYoon Lim was added as a committer on Tue Sep 13 2016 ## Releases: - Last release was hama-0.7.1 on Mon Mar 14 2016 ## Mailing list activity: - dev@hama.apache.org: - 114 subscribers (down -1 in the last 3 months): - 36 emails sent to list (69 in previous quarter) - user@hama.apache.org: - 186 subscribers (down -1 in the last 3 months): - 2 emails sent to list (1 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: Report from the Apache HTTP Server Project [Eric Covener] ## Description: The Apache HTTP Server Project develops and maintains an open-source HTTP server for modern operating systems. ## Issues: There are no issues requiring board attention at this time. ## Activity: * Development pace is slow with a few notable exceptions (Strict HTTP compliance, http2, redis socache, security investigations) ## Health report: * Overall things are healthy. Routine tickets/emails are being addressed in a timely manner. * Some security work with backwards-compatibility complications has been proceeding more slowly then we'd normally like. This work and the queue of more straightforward issues blocked behind it has in some sense also delayed new releases. ## PMC changes: * No PMC change this period ** Last PMC addition: Jean-Frederic Clere was added to the PMC on Tue Nov 24 2015 * Currently 44 PMC members. ## Committer base changes: * 1 committer added this period * * Evgeny Kotkov was added on Tue Sep 20 2016 * Currently 116 committers. ## Releases: * No releases this reporting period. ** Last stable release was 2.4.23 on July 05, 2016 ** Last legacy release was 2.2.31 on July 16, 2015 (EOL announced during 2.4.23) ----------------------------------------- Attachment Y: Report from the Apache HttpComponents Project [Asankha Perera] Report from the Apache HttpComponents Project ## Description: - The Apache HttpComponents project is responsible for creating and maintaining a toolset of low-level Java components focused on HTTP and associated protocols ## Issues: - There are no issues requiring board attention at this time ## Activity: - We are currently working on adding support for HTTP/2 protocol to HttpCore and HttpClient. ## Health report: - Overall the project remains active. Although established in late 2007 the project remains stable and active as seen by JIRA and Emails. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Mon Aug 24 2015 ## Committer base changes: - Currently 18 committers. - New commmitters: - Dmitry Potapov was added as a committer on Mon Sep 05 2016 - Julian Sedding was added as a committer on Fri Sep 30 2016 ## Releases: - Last release was HttpAsyncClient 4.1.2 GA on Mon Jun 27 2016 ## JIRA activity: - 37 JIRA tickets created in the last 3 months - 38 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Z: Report from the Apache Ignite Project [Dmitriy Setrakyan] The Apache Ignite (TM) In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash technologies. Apache Ignite (TM) provides many in-memory components to improve performance and scalability of user applications, including in-memory data grid (distributed caching), in-memory compute grid, in-memory streaming, and more. ## Activity: - PMC started discussion on PMC chair rotation - Community started discussions about Ignite 2.0 on the dev list: https://s.apache.org/ignite2.0 - Community is actively planning Ignite 1.8 release: https://s.apache.org/ignite-1.8 main features: - new DML in addition to SQL (insert, update, delete) - ODBC improvements - Community has added more content to Ignite website ## Health report: - Ignite keeps attracting new contributors on the mailing list - Ignite chatroom member list continuously grows ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 monthss - Last PMC addition was Denis Magda on Sun Sep 27 2015 - Community has voted and added Alexey Kuznetsov to PMC However, it turned out that Alexey Kuznetsov was added to PMC by mistake when he was granted committer priveleges, so no LDAP changes were needed. ## Committer base changes: - Currently 32 committers. - New commmitters: - Andrey N. Gura was added as a committer on Tue Sep 13 2016 - Igor Rudyak was added as a committer on Mon Nov 14 2016 - Saikat Maitra was added as a committer on Wed Aug 31 2016 ## Releases: - Last release was 1.7.0 on Fri Aug 05 2016 ## Mailing list activity: - dev@ignite.apache.org: - 212 subscribers (up 13 in the last 3 months): - 1576 emails sent to list (1823 in previous quarter) - issues@ignite.apache.org: - 24 subscribers (down -1 in the last 3 months): - 4313 emails sent to list (4485 in previous quarter) - user@ignite.apache.org: - 366 subscribers (up 53 in the last 3 months): - 1887 emails sent to list (1972 in previous quarter) ## JIRA activity: - 514 JIRA tickets created in the last 3 months - 388 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for November 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 currently 63 podlings incubating - no change from last month. The Geode podling has proposed itself for graduation. There were two new IPMC members added this past month. The IPMC approved 17 releases this month as well. * Community New IPMC members: - Felix Meschberger - Stephan Ewen People who left the IPMC: - None * New Podlings - None * Graduations The board has motions for the following: - Geode * Releases The following releases entered distribution during the month of October: - Apache Unomi 1.1.0-incubating 2016-10-03 - Apache Impala 2.7.0-incubating 2016-10-04 - Apache Fluo 1.0.0-incubating 2016-10-05 - Apache Htrace 4.2.0-incubating 2016-10-07 - Apache PredictionIO 0.10.0-incubating 2016-10-07 - Apache Pirk 0.2.0-incubating 2016-10-09 - Apache HAWQ 2.0.0.0-incubating 2016-10-10 - Apache CarbonData 0.1.1-incubating 2016-10-11 - Apache Metron 0.2.1BETA-incubating 2016-10-13 - Apache Geode 1.0.0-incubating 2016-10-15 - Apache Mnemonic 0.3.0-incubating 2016-10-21 - Apache Juneau 6.0.0-incubating 2016-10-24 - Apache Fineract 0.4.0-incubating 2016-10-25 - Apache Fluo Recipes 1.0.0-incubating 2016-10-27 - Apache Rya 3.2.10-incubating 2016-10-28 - Apache S2Graph 0.1.0-incubating 2016-10-30 - Apache Beam 0.3.0-incubating 2016-10-31 * IP Clearance - None * Legal / Trademarks - Incoming podlings are pushing more for GitHub as master approaches. - In addition, the usage of GitHub Issues continues to be asked. - Better alignment between all impacted parties is needed for both of these. * Infrastructure - While the loss of a server is never convenient, the report manager gives huge kudos to the infra team for replacing the moin-moin wiki server quickly, avoiding much impact on this months report. * Miscellaneous - None * Credits - Report Manager: John D. Ament -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - AriaTosca - Guacamole - Hivemall - iota - NetBeans - Spot - Toree * Not yet ready to graduate Stagnant: - Sirona No release: - Blur - Climate Model Diagnostic Analyzer - DistributedLog - Edgent - Joshua Community growth: - DataFu - Fineract - Fluo - Impala - PredictionIO - S2Graph - Streams - Unomi * Potentially Ready to Graduate - BatchEE - Beam - CarbonData - Eagle - Slider - SystemML - Tamaya * Did not report, expected next month - Annotator ---------------------------------------------------------------------- Table of Contents AriaTosca Beam Blur CarbonData Climate Model Diagnostic Analyzer DataFu DistributedLog Eagle Edgent Fineract Fluo Guacamole Hivemall Impala iota Joshua NetBeans PredictionIO S2Graph Sirona Slider Spot Streams SystemML Tamaya Toree Unomi ---------------------------------------------------------------------- -------------------- AriaTosca ARIA TOSCA project offers an easily consumable Software Development Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and Orchestration Specification of Cloud Applications) based solutions. AriaTosca has been incubating since 2016-08-27. Three most important issues to address in the move towards graduation: 1. Finalize migration of existing ARIA code, including Parser-NG with TOSCA and TOSCA for NFV profiles, and workflow engine to the ASF repo. 2. Create and publish release process for ARIA-TOSCA Project, release process will include Parser, TOSCA profiles, Workflow Engine, CLI. 3. Publish "How To Contribute" guide at ARIA-TOSCA Website. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There's an INFRA jira we created over a month ago which has yet to be addressed - please see here INFRA-12733 - Ability to create a Sprint Board for AriaTosca WAITING FOR USER It is not entirely critical for the project's progress, but it could be helpful if we indeed get a sprint board and the other things requested in that issue. How has the community developed since the last report? Preparing TOSCA DSL training materials Confluence space initialized How has the project developed since the last report? 1. Created master branch 2. CI on travis enabled for the project 3. Initial workflow engine code migrated to ASF repo 4. Preparing migrating Parser code to ASF repo 5. Various task executors have been implemented Date of last release: None When were the last committers or PMC members elected? Project is being established in incubator with the proposed initial set of committers. Signed-off-by: [X](ariatosca) Suneel Marthi [X](ariatosca) John D. Ament [ ](ariatosca) Jakob Homan -------------------- Beam Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the mechanics of large-scale batch and streaming data processing and can run on a number of runtimes such as Apache Flink, Apache Gearpump, Apache Apex, Apache Spark, and Google Cloud Dataflow. Beam also brings SDKs in different languages, allowing users to easily implement their data integration processes. Beam has been incubating since 2016-02-01. The most important issue to address in the move towards graduation: 1. Make it easier for the Beam community to to learn, use, and grow by expanding and improving the Beam documentation, code samples, and the website 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? * 441 closed/merged pull requests * High engagement on dev and user mailing lists (742 / 179 messages) * Several public talks, articles, and videos including: - @Scale San Jose (“No shard left behind: APIs for massive parallel efficiency in Apache Beam”) - Strata + Hadoop World NYC (“Learn stream processing with Apache Beam”) - Paris Spark Meetup (“Introduction to Apache Beam”) - Hadoop Summit Melbourne (“Stream/Batch processing portable across on-prem (Spark, Flink) and Cloud with Apache Beam”) - Hadoop User Group Taipei (“Stream Processing with Beam and Google Cloud Dataflow”) - Data Science Lab London (“Apache Beam: Stream and Batch Processing; Unified and Portable!”) How has the project developed since the last report? Major developments on the project since last report include the following: * Second and third incubating release (0.2.0 and 0.3.0) and a release guide [1] * New DirectRunner support for testing streaming pipelines[2] * Continued improvements to the Flink, Spark, and Dataflow runners * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC with Cassandra, MQTT support pending in pull requests * Addition of the Apache Apex runner on a feature branch, and continued work on the Apache Gearpump runner and Python SDK feature branches. [3] * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing [1]: http://beam.incubator.apache.org/contribute/release-guide/ [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html [3]: http://beam.incubator.apache.org/contribute/work-in-progress/#feature-branches Dates of last releases: * 2016/08/07 - 0.2.0-incubating * 2016/10/31 - 0.3.0-incubating When were the last committers or PMC members elected? The following committers were elected on 2016/10/20: * Thomas Weise * Jesse Anderson * Thomas Groh Signed-off-by: [X](beam) Jean-Baptiste Onofré [ ](beam) Venkatesh Seetharam [ ](beam) Ted Dunning -------------------- Blur Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur has been incubating since 2012-07-24. Three most important issues to address in the move towards graduation: 1. Greater community involvement. 2. Produce releases. 3. 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? Subscriptions: user@ - 62[+1]; dev@ - 78[-1] The community involvement has not really changed over the past few months. How has the project developed since the last report? - Not much has changed, a few bug fixes. Date of last release: 2014-07-29 When were the last committers or PMC members elected? 2014-07-28 Signed-off-by: [ ](blur) Doug Cutting [X](blur) Patrick Hunt [ ](blur) Tim Williams -------------------- CarbonData Apache CarbonData is a new Apache Hadoop native file format for faster interactive query using advanced columnar storage, index, compression and encoding techniques to improve computing efficiency, in turn it will help speedup queries an order of magnitude faster over PetaBytes of data. CarbonData has been incubating since 2016-06-02. Three most important issues to address in the move towards graduation: 1. Prepare a couple of new releases 2. Increase the communities 3. Prepare website Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community activity increased: many new users started to use and test CarbonData, we had more than 300 issues created till Nov; Two new finance enterprises have formally deployed CarbonData to their business system,and the query performance speeded up 10-70 times in comparison to old system (both are bank enterprise in China). We finished 2nd Meetup in Beijing on 29th Oct, and CarbonData has increased 10+ contributors in last month. How has the project developed since the last report? Code donation has been done and all resources have been created by INFRA(git, github mirror, mailing list, Jira, ...). We also created the Jenkins CI jobs, and preparing org website. We did the 2nd release (0.1.1-incubating) in Oct and we are preparing a new one(0.2.0) in Nov. We have finished 2 technical talks in Bay area with Databricks, Alluxio in last month for discussing ecosystem integration with Spark and Alluxio. Date of last release: 2016-10-10 When were the last committers or PMC members elected? We elected a new committer Kumar Vishal on 2016-10-15. Signed-off-by: [X](carbondata) Henry Saputra [X](carbondata) Jean-Baptiste Onofré [X](carbondata) Uma Maheswara Rao G -------------------- Climate Model Diagnostic Analyzer CMDA provides web services for multi-aspect physics-based and phenomenon- oriented climate model performance evaluation and diagnosis through the comprehensive and synergistic use of multiple observational data, reanalysis data, and model outputs. Climate Model Diagnostic Analyzer has been incubating since 2015-05-08. The achievements in October of 2016 are: 1. Drafted the Apache CMDA project web page 2. Developed a mechanism to keep track of user id in each service call 3. Designed a mechanism to define a workflow, to execute a workflow, to collect the result and provenance from the workflow execution. Three most important issues to address in the move towards graduation: 1. To facilitate workflow scenarios in which a scientist can chain two or more services; 2. To develop a suite of science use cases; 3. To demonstrate the use of provenance in recommendation of data, users, and services. 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 climate scientist Frank Lee has joined the project to develop science use cases. The priority has been shifted to helping him in adding new source data files and modifying the software to accommodate these new data files. How has the project developed since the last report? The issues that we found from our 2016 Caltech/JPL climate summer school have been addressed. Examples are: a mechanism to capture and store user id for provenance data collection, and removal of some functionalities that are not meant for users that do not have login accounts on our website. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? Signed-off-by: [ ](climatemodeldiagnosticanalyzer) James W. Carman [X](climatemodeldiagnosticanalyzer) Chris Mattmann [ ](climatemodeldiagnosticanalyzer) Michael James Joyce [ ](climatemodeldiagnosticanalyzer) Kim Whitehall Shepherd/Mentor notes: Chris Mattmann: I'm worried still about this podling. Discussion seemed to still happen offlist and to be summarized to the list, instead of actively involving others in the community. Also, it says the website has been drafted - where is it? Where are the corresponding JIRA issues? Where are the public discussions about the site. The podling is/was on a short leash since the [DISCUSS] Retirement vote. I'd say give it one more month, and would appreciate others chiming in here. The other thing I'd say is that there is definitely mentor attrition here. I don't think we have enough active mentors reinforcing and sending the message (myself included) day to day. It's definitely more reactive now than proactive. The podling could use some help in that area. -------------------- 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. Resolve NOTICE and LICENSE issues for binary distributions 2. Continued releases 3. Increased committer activity 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? * No updates How has the project developed since the last report? * Released 1.3.1. Now using ASF-associated signing key. Feedback from previous release addressed. * Website updated alongside 1.3.1 release. * Cleaned up release instructions. Date of last release: 2016-08-10 When were the last committers or PMC members elected? July 2016 (Eyal Allweil) Signed-off-by: [ ](datafu) Ashutosh Chauhan [X](datafu) Roman Shaposhnik [ ](datafu) Ted Dunning Shepherd/Mentor notes: Roman Shaposhnik: Pushing this community towards graduation is pretty high on my TODO list. I think they are as ready as they are ever going to be. -------------------- DistributedLog DistributedLog is a high-performance replicated log service. It offers durability, replication and strong consistency, which provides a fundamental building block for building reliable distributed systems. DistributedLog has been incubating since 2016-06-24. Three most important issues to address in the move towards graduation: 1.Continue to grow the community, and increase diversity of community. 2.Improve documentation, including documentation of project and processes. 3.Successful 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? 1. Increase in contributions from community. - 8 created and 4 resolved issues in community JIRA in October. 2. Lots of engagement on documentation. - Enhance existing documents, - Setup guides for developers and committers. 3. Increased traffic on the mailing list, in particular, due to committers engaging more actively with contributors. - we have 35 people subscribed mail list. - 125 messages to distributedlog mail list in October. How has the project developed since the last report? 1. Documentation has improved for project build and project deployment. Added more information on community page. New added pages: https://cwiki.apache.org/confluence/display/DL/Developer+Guide https://cwiki.apache.org/confluence/display/DL/Committer+Guide 2. Involved more discussion of new ideas and bring in new features. Include major discussions like 'transaction support', 'batch commit', "EventStore" . etc. 3. First release expected on November, and repackaging of the project under apache namespace are being discussed. - Pull requests for repackaging. - The major blocker is https://issues.apache.org/jira/browse/DL-2. We were expecting to let DL depends on an official bk version. Date of last release: NA When were the last committers or PMC members elected? NA Signed-off-by: [ ](distributedlog) Flavio Junqueira [ ](distributedlog) Chris Nauroth [X](distributedlog) Henry Saputra -------------------- Eagle Eagle is a Monitoring solution for Hadoop to instantly identify access to sensitive data, recognize attacks, malicious activities and take actions in real time. Eagle has been incubating since 2015-10-26. Three most important issues to address in the move towards graduation: 1. Jira, PR are all populated with good description so that people can reference in the future. 2. Massive improvement on unit test, now it becomes stable and build status is closed monitored in README 3. Community has one more discussion about graduation and all are with positive feedback, and we are going through the graduation steps. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Nil How has the community developed since the last report? - Presented in conference: QCon Shanghai - More active contributors from YHD.com participate in large feature development How has the project developed since the last report? - 0.5 version is being in active development. This version will include big improvement in application management and alert engine. - Job monitoring feature is ready including map/reduce and spark job - Standalone alert engine which is highly scalable and user friendly in that user does not need code to configure alerting rules - UI is completely rewritten to expose metadata to end user and user can define data source, stream and policy etc. - Cluster health monitoring is ready, including hdfs health indicator, hbase health indicator etc. Date of last release: 2016-07-19, and 0.5 release is being prepared When were the last committers or PMC members elected? - Jinhu Wu 2016-09-10 Signed-off-by: [ ](eagle) Owen O'Malley [X](eagle) Henry Saputra [x](eagle) Julian Hyde [X](eagle) P. Taylor Goetz [X](eagle) Amareshwari Sriramdasu -------------------- Edgent Edgent is a stream processing programming model and lightweight runtime to execute analytics at devices on the edge or at the gateway. Edgent 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 the Edgent project 2. Create the first Apache release of Edgent 3. Document a repeatable release process. 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? * A well attended meetup in Plano, TX about Apache Edgent was held on September 9th "Sensor Data Analytics Acceleration with Apache Edgent" http://www.meetup.com/DFW-Sensor-Technology/events/233150402/ * A presentation about Apache Edgent was presented on October 21st @ Open Source India 2016. Approximately 400 attendees were present. * A presentation about Apache Edgent, Streaming Analytics and Weather Company Data was presented at World of Watson in Las Vegas on October 26th. * A demo about Apache Edgent was presented at World of Watson in Las Vegas on October 24th. "IoT Device Events to Streaming Analytics in 15 Minutes with Bluemix" * For the months of September and October four new community members either subscribed to the edgent-dev mailing list, or opened JIRAs. How has the project developed since the last report? * A new build system was created using Gradle. The initial contribution for this work came from two community contributors. The follow up work was done by committers. According to JIRA, the project has added the following: * September: 11 new issues; 15 issues resolved. * October: 46 new issues; 23 issues resolved. * October activity was almost exclusively due to readying for the first Edgent release. Date of last release: * We have not created an Apache release, but are working on one to be ready soon. During the September and October time period we made build changes and handled licensing work and are poised to create our first release. When were the last committers or PMC members elected? * In May, we added two new committers and PPMC members, Kathy Saunders and * Queenie Ma. Signed-off-by: [ ](edgent) Daniel Debrunner [x](edgent) Luciano Resende [X](edgent) Katherine Marsden [X](edgent) Justin Mclean -------------------- 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. With the first official incubation release out, we want to work on getting frequent successful incubation releases shipped to the community on a monthly basis. 2. Adding new committers and contributors to the project along with empowering volunteers and support partner organizations in the community to contribute to the codebase while using the project infrastructure. 3. Resolving the questions around introduction of a rework of the original code – in particular repository/infrastructure/release questions which result from the microservice architecture Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? * With the first official incubation release out, we look add several new committers who have worked on modules and features that will soon be merged into the release. * The community is more involved and engaged in asking questions on the developer and user mailing lists. We are working to ensure that all inquiries are actively addressed and more discussions regarding functionality and design occur on the mailing lists. How has the project developed since the last report? * Our first release was made on October 25, 2016. We received 4 binding votes from the community. * Significant work was led by the Mifos core development team to address the licensing issues with a dependency on Hibernate and replacing it with OpenJPA - details on the code changes made and the challenges overcome can be found at https://youtu.be/C4lXtXY-MY4 Date of last release: 2016-10-25 When were the last committers or PMC members elected? 2016-05-05 Signed-off-by: [ ](fineract) Ross Gardler [X](fineract) Greg Stein [X](fineract) Roman Shaposhnik Shepherd/Mentor notes: Roman Shaposhnik: Next item on the immediate TODO list for the community is to master releases of binary convenience artifacts. -------------------- Fluo Fluo is a distributed system for incrementally processing large data sets stored in Accumulo. Fluo has been incubating since 2016-05-17. Three most important issues to address in the move towards graduation: 1. Attract new contributors and users 2. Additional releases 3. 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? * Two talks at the Accumulo Summit mentioned Fluo: * http://accumulosummit.com/program/talks/tips-for-writing-fluo-applications/ * http://accumulosummit.com/program/talks/indexing-strategies-for-searching-semantic-networks/ * Hadoop Weekly Issue #191 mentioned Fluo's release * Website traffic is up after the first release according to Google Analytics * Created Twitter Account : http://twitter.com/apachefluo * Recent release of Rya which uses Fluo How has the project developed since the last report? * Successfully made first release and two more releases : * https://fluo.apache.org/release/fluo-recipes-1.0.0-incubating/ * https://fluo.apache.org/release/fluo-1.0.0-incubating/ * https://lists.apache.org/thread.html/0d02022b544fef972dabcfbbf59381fc811fe3d0843f7052568cd56e@%3Cgeneral.incubator.apache.org%3E * Created Fluo Tour (easy, hands on introduction) : https://fluo.apache.org/tour/ * Completed Podling Namesearch : https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-109 * fluo.io now redirects to fluo.apache.org * The fluo-io GitHub org was renamed to astralway Date of last release: 2016-10-28 When were the last committers or PMC members elected? Never Signed-off-by: [x](fluo) Billie Rinaldi [x](fluo) Drew Farris [x](fluo) Josh Elser Shepherd/Mentor notes: Josh Elser: The podling is definitely finding their legs in creating and releasing software, but very little progress has been made on growing the community (no prospective members). I am also happy with the state of trademarks for the podling. -------------------- Guacamole Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway. Combined with cloud hosting, Guacamole provides an excellent alternative to traditional desktops. Guacamole aims to make cloud-hosted desktop access preferable to traditional, local access. Guacamole has been incubating since 2016-02-10. Three most important issues to address in the move towards graduation: 1. **Making the first Guacamole release under the Apache Incubator** 2. Encouraging community participation and contribution 3. Accepting additional committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? It is clear that the continuing lack of a release is a major obstacle to community development, especially given outstanding pull requests which cannot be merged due to pre-release code freeze. We believe that the source and documentation are finally up-to-date with respect to Apache and the Incubator, and that we are ready to move forward with the procedures surrounding the release. Any assistance in navigating our first release would be greatly appreciated. How has the community developed since the last report? Community participation has remained roughly the same as last report. Mailing list participation is active but unchanged. Since last report, we have received an additional 3 pull requests, and have engaged the contributors for code review. Code looks good, and response to feedback has been professional, but merge is blocked until we can get the first release out of the way. How has the project developed since the last report? All outstanding issues which were aimed at the project's first release (0.9.10-incubating) have been completed, as have all bugs discovered during testing. We have made preparatory changes to the project website with the release in mind. The project's old SourceForge forums have finally been closed, replaced by the mailing lists. The forums have been left in read-only mode for the sake of reference, with a stickied announcement notifying users of the move. Date of last release: 2015-12-18 (0.9.9, prior to Apache Incubator) When were the last committers or PMC members elected? The most recent committer, Frode Langelo, was accepted into the project by VOTE on 2016-04-03, with the required ICLA received on 2016-04-05. Signed-off-by: [X](guacamole) Jean-Baptiste Onofré [ ](guacamole) Daniel Gruno [ ](guacamole) Olivier Lamy [X](guacamole) Jim Jagielski [X](guacamole) Greg Trasuk -------------------- Hivemall Hivemall is a library for machine learning implemented as Hive UDFs/UDAFs/UDTFs. Hivemall has been incubating since 2016-09-13. Three most important issues to address in the move towards graduation: 1. Create the first Apache release 2. Community growth 3. IP clearance 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? * Presented a talk in Hadoop Summit Tokyo on Oct 26. * Still in progress at migrating the repository/community to ASF infra on https://issues.apache.org/jira/browse/HIVEMALL-8 How has the project developed since the last report? * We setup JIRA and managed issues on https://issues.apache.org/jira/browse/HIVEMALL/ * We build the project site on http://hivemall.incubator.apache.org/ * Documentation updates has been made http://hivemall.incubator.apache.org/userguide/ Date of last release: No release yet When were the last committers or PMC members elected? None Signed-off-by: [ ](hivemall) Reynold Xin [X](hivemall) Markus Weimer [ ](hivemall) Xiangrui Meng -------------------- 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. Community growth 2. Transition of user documentation to Apache hosting 3. Migration of pre-commit continuous integration testing to publicly-available infrastructure Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? Our last report was in August. Since then, we have five new contributors who have authored patches, while two relatively recent contributors who were active before August have continued their involvement by authoring new patches. Traffic to our developer mailing list has grown by about 60%. How has the project developed since the last report? There have been 241 commits since the last report. Our status website now has 16 of the 17 listed work items complete. We had our first Apache release and have a wiki page describing how to perform the release in detail. We scrubbed our code using the RAT tool for copyright notices not compliant with the ASF rules. We wrote guidelines for contributors on how to become a committer and added a new committer. All developer documentation has now moved to the Apache-hosted wiki. Date of last release: 2016-10-05 When were the last committers or PMC members elected? 2016-08-18 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. Building the developer community 2. Outreach at events outside the Apache ecosystem to inform and invite participation in the project 3. Getting an alpha release out by the end of this year based on the current 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? Increased user interest with 4 individuals that are contributing in spurts of activity. This needs to become consistent. How has the project developed since the last report? Some improvements in the core engine, performers and the build process Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? None but we are working on a proposal to add a new committer (a contributor that has made significant contributions in the last 6 months) Signed-off-by: [ ](iota) Daniel Gruno [ ](iota) Sterling Hughes [X](iota) Justin Mclean [X](iota) Hadrian Zbarcea Shepherd/Mentor notes: Justin Mclean: I have some concerns re progress of this poddling: - The on list PPMC activity is low and there may be discussions happening off list. - There is little progress towards making an Apache release. - I'm not sure there are 3 active PPMC members. -------------------- 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. Creating our first release. 2. Continue to build the community 3. Identify specific users and use cases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? We have added a few new members. How has the project developed since the last report? A new release is imminent; we just need to pull the trigger. We have put together over sixty "language packs" that will be released in a no-dependency version and a Docker container. Date of last release: Forthcoming. When were the last committers or PMC members elected? John Hewitt (August 13, 2016) Max Thomas (pending) Michael Hedderich (pending) Signed-off-by: [ ](joshua) Paul Ramirez [ ](joshua) Lewis John McGibbney [X](joshua) Chris Mattmann [ ](joshua) Tom Barber [X](joshua) Henri Yandell -------------------- NetBeans NetBeans is a development environment, tooling platform and application framework. NetBeans has been incubating since 2016-10-01. Three most important issues to address in the move towards graduation: 1. Licensing, i.e., identifying and solving GPL-related code. 2. Coming up with a process of contributing code that makes sense to everyone. 3. Working on roadmaps, features, and plans together as a community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Mailing lists and Wiki set up. Discussions about voting, the CCLA/SGA, are taking place in the private mailing list, all other discussions in dev mailing list. We want as many discussions as possible in dev mailing list, i.e., as public as possible. How has the project developed since the last report? Apache NetBeans Proposal has been published and accepted into incubation. Apache Transition plan, listing everything needing to be done, including proposed milestones, is being worked on: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition CCLA and SGA have been provided in draft form by Oracle and have been approved by ASF. Currently they're in the process of being approved and signed by Oracle. Once that's done, experiments with migrating hg.netbeans.org/releases to Apache Git can proceed. Date of last release: No releases yet. When were the last committers or PMC members elected? No one has been elected so far. Signed-off-by: [X](netbeans) Ate Douma [X](netbeans) Bertrand Delacretaz [X](netbeans) Emmanuel Lecharny [ ](netbeans) Daniel Gruno [X](netbeans) Jim Jagielski [x](netbeans) Mark Struberg -------------------- PredictionIO PredictionIO is an open source Machine Learning Server built on top of state-of-the-art open source stack, that enables developers to manage and deploy production-ready predictive services for various kinds of machine learning tasks. PredictionIO has been incubating since 2016-05-26. The initial code for PredictionIO was granted on 2016-06-16. A second grant of PredictionIO templates and SDKs was granted on 2016-09-20. Three most important issues to address in the move towards graduation: 1. Establish a formal release schedule and process, allowing for dependable release cycles in a manner consistent with the Apache way. 2. Grow the community to establish diversity. 3. Migrate the remainder of former PredictionIO users from google-groups to ASF mailing lists. 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. Both user and development mailing list are seeing increased activity. 2. Users requesting features are coming forward with code contributions. There have been discussions regarding future roadmap and development on the mailing lists. 3. The ecosystem around engine templates is slowly gaining traction again on Apache infrastructure. There are discussions around engine templates. How has the project developed since the last report? 1. The first Apache release has been released on 2016-10-17. 2. The second software grant has been issued and recorded by ASF. Seven templates and five SDKs are now transferred to Apache. Date of last release: Apache PredictionIO 0.10.0-incubating on 2016-10-17 When were the last committers or PMC members elected? Paul Li was elected as committer and PMC member on Aug 30, 2016. Signed-off-by: [X](predictionio) Andrew Purtell [ ](predictionio) James Taylor [ ](predictionio) Lars Hofhansl [ ](predictionio) Luciano Resende [ ](predictionio) Xiangrui Meng [X](predictionio) Suneel Marthi Shepherd/Mentor notes: Drew Farris (shepherd): Two Mentors active on the mailing lists. Healthy activity observed on lists. -------------------- S2Graph S2Graph is a distributed and scalable OLTP graph database built on Apache HBase to support fast traversal of extremely large graphs. S2Graph has been incubating since 2015-11-29. Three most important issues to address in the move towards graduation: 1. Make a release 2. Attract users and contributors 3. Foster more and diverse committers 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? * Held two sessions on S2Graph: usecases * Deview: https://deview.kr/2016/schedule#session/160 * TechPlanet: http://techplanet.skplanet.com/eng/speaker_track2.html#spk_trk2_5 * Started to discuss overhauling the website layout and contents How has the project developed since the last report? * The first Apache release has been released on 2016-11-01. * 30 issues are created, 32 issues are resolved. Date of last release: Apache S2Graph 0.1.0-incubating on 2016-11-01. When were the last committers or PMC members elected? No Signed-off-by: [ ](s2graph) Andrew Purtell [ ](s2graph) Seetharam Venkatesh [X](s2graph) Sergio Fernández -------------------- Sirona Monitoring Solution. Sirona has been incubating since 2013-10-15. Three most important issues to address in the move towards graduation: 1. Increase community/visibility 2. Get a bit more dynamic 3. 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? Not much How has the project developed since the last report? Some enhancements around the javaagent for short time living JVM use cases. Date of last release: 2015-11-03 When were the last committers or PMC members elected? Signed-off-by: [ ](sirona) Olivier Lamy [ ](sirona) Henri Gomez [ ](sirona) Jean-Baptiste Onofre [ ](sirona) Tammo van Lessen [x](sirona) Mark Struberg Shepherd/Mentor notes: Mark Struberg: Cool project, but sadly we have a very low activity. -------------------- Slider Slider is a collection of tools and technologies to package, deploy, and manage long running applications on Apache Hadoop YARN clusters. Slider has been incubating since 2014-04-29. Three most important issues to address in the move towards graduation: 1. Apache Slider community/PPMC has voted to move portions of Slider into Apache Hadoop YARN as modules. It is possible that the remaining pieces will be moved at a later point in time or become obsolete or evolve to work closely with YARN. Slider PPMC will decide what makes the most sense as we progress through this exciting time. 2. Getting more external users 3. Growth of a diverse set of developers/committers/PMC members is also crucial towards the final state of Slider Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? The Apache Hadoop YARN community/PMC and Apache Slider community/PPMC had decided to move portions of Slider into YARN, to make fast and significant progress on: YARN-4692 - [Umbrella] Simplified and first-class support for services in YARN. As a result, the Slider Core module (including Application Master, Client and Java unit tests) has been rolled into an Apache Hadoop YARN feature branch as a hadoop-yarn-slider-core module. This effort is being captured in: YARN-5079 : Native YARN framework layer for services. All the migrations are happening in a branch (namely yarn-native-services) created of off Hadoop trunk. As a result of this, we are already seeing interest in the Hadoop committers/PMC, who have started to contribute and submit patches to Slider. In order to support existing users of Slider, and to provide seamless migration, there will be sufficient overlap between the time when a stable state of long running services support is available in some future version of YARN and the time till an independent Slider release is available. The community/PPMC will also determine the future state of Slider as we navigate through these changes. The discussions on the Slider and YARN community DLs can be viewed here - https://s.apache.org/0hoh https://s.apache.org/MncV For the benefit of those who would like to use Slider Core from the Hadoop codebase, but continue to use classic Slider Agent and legacy app-packages, a new branch (yarn-native-services) has been created in classic Slider repo. This branch retains only the Agent (python) code and the App Packages. It adds Slider Core module as a Hadoop dependency. This allows users to consume the latest of Slider Core. Future classic Slider releases can be made purely off of this branch. Additionally an effort is being made to create an agent-less provider for legacy app-packages, which could help users to completely migrate to Hadoop codebase for creating long-running services with Slider. Expectation from app-package owners would be to make minor modification of their packages. Primary changes would be to shed the dependency on python Agent code, effectively making packages much simpler than what they look like today in classic Slider. How has the project developed since the last report? There has been fewer bug fixes on the classic Slider side as most of the focus has been on developing features on native YARN services in the Hadoop codebase. Work continues on support for complex services (assemblies) and agent-less applications in Slider. The efforts on Slider Core will continue in the new services branch created in YARN. Few key features which were merged to classic Slider as well were - SLIDER-875 - Ability to create an Uber application package with capability to deploy and manage as a single business app, and SLIDER-1107 - Generate app configuration files in AM. Several issues identified by Coverity scans were resolved as well. Additionally few patches were contributed by the community fixing functional and performance issues. Slider community plans to ship a release in the next quarter with all these features and bug fixes. Date of last release: 2016-06-28 slider-0.91.0-incubating When were the last committers or PMC members elected? 2015-07-07: Yu (Thomas) Liu Signed-off-by: [ ](slider) Arun C Murthy [ ](slider) Devaraj Das [X](slider) Jean-Baptiste Onofré [X](slider) Mahadev Konar -------------------- Spot Apache Spot is a solution stack that provides the capability to ingest network related telemetry (network flows, domain name service information and proxy server logs) and provide unsupervised machine learning capabilities to identify suspicious activity. The information is organized and presented using operational analytics so that a security analyst can investigate the most suspicious connections. Apache Spot is built on an open data model using Apache Spark and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important issues to address in the move towards graduation: - Move infrastructure and development to ASF (code, issues, mailing list, …) - Build diverse community - Demonstrate ability to create releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We currently have a hard dependency via our LDA implementation that requires a GPL license. A rewrite is in progress to move the code from LDA-C to Spark LDA. How has the community developed since the last report? This is first report after accepting Apache Spot to incubator and we still have not transitioned everything to ASF. We do however see increased interest in the project, primarily on our Slack channel. How has the project developed since the last report? This is first report. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [x](spot) Jarek Jarcec Cecho [ ](spot) Brock Noland [ ](spot) Andrei Savu [X](spot) Uma Maheswara Rao G -------------------- Streams Apache Streams (incubating) unifies a diverse world of digital profiles and online activities into common formats and vocabularies, and makes these datasets accessible across a variety of databases, devices, and platforms for streaming, browsing, search, sharing, and analytics use-cases. Streams has been incubating since 2012-11-20. Three most important issues to address in the move towards graduation: 1. Community growth and PMC maturity. 2. Demonstrate a consistent release schedule. 3. Participation of project community within related standards-bodies and Apache projects. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The project is now on a monthly reporting schedule to monitor effective progress in growing the community and active participation. How has the community developed since the last report? dev@streams.incubator.apache.org 115 emails (up >100%) sent by 16 people (+1), divided into 36 topics (up 400%). http://streams.incubator.apache.org 196 Sessions (up ~60%), 247 Users (up ~35%), 1110 Pageviews (up >100%). How has the project developed since the last report? https://github.com/apache/incubator-streams-master Excluding merges, 4 authors (+3) have pushed 32 commits (up ~375%) to master. On master, 22 files (up 250%) have changed. https://github.com/apache/incubator-streams Excluding merges, 7 authors (+6) have pushed 106 commits (up >1000%) to master. On master, 868 files (up >1000%) have changed. https://github.com/apache/incubator-streams-examples Excluding merges, 3 authors (+2) have pushed 7 commits (+1) to master. On master, 24 files have changed. 52 Issues closed for the upcoming 0.4-incubating release 35 new Issues opened (+28) Date of last release: 2016-10-03 : 0.3-incubating release When were the last committers or PMC members elected? 2016-10-27: Joey Frazee elected as committer / PPMC member 2016-09-28: Suneel Marthi elected as mentor / PPMC member Signed-off-by: [X](streams) Ate Douma [X](streams) Matt Franklin [X](streams) Suneel Marthi Shepherd/Mentor notes: Suneel Marthi: Healthy community activity, following the 0.3 release on Oct 3, 0.4 release is presently in the works and work has been scoped out for the 0.5 release. Ate Douma: The Streams podling is getting back on track, making good progress: * new community participants * good mailing list discussions * elected a new committer and ppmc member (Joey) * a new release candidate 0.4-incubating is in progress -------------------- SystemML SystemML provides declarative large-scale machine learning (ML) that aims at flexible specification of ML algorithms and automatic generation of hybrid runtime plans ranging from single node, in-memory computations, to distributed computations running on Apache Hadoop MapReduce and Apache Spark. SystemML has been incubating since 2015-11-02. Three most important issues to address in the move towards graduation: - Grow SystemML community: increase mailing list activity, increase adoption of SystemML for scalable machine learning, encourage data scientists to adopt DML and PyDML algorithm scripts, respond to user feedback to ensure SystemML meets the requirements of real-world situations, write papers, and present talks about SystemML. - Continue to produce releases. - Increase the diversity of our project's contributors and committers. 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? Our mailing list from August through October had 375 messages on a wide range of topics. We have gained 4 new contributors to the main project since August 1st. Our website has been redesigned with the help of several design engineers and we have commits from 3 new contributors to the website project. On GitHub, the project has been starred 417 times and forked 156 times. Niketan Pansare gave a talk with the title "Apache SystemML - Declarative Machine Learning at Scale" on October 7th in the CS graduate seminar at UC Merced. Matthias Boehm gave a talk on "Compressed Linear Algebra for Large- Scale Machine Learning" at TU Dresden on August 30th. We presented the papers "Compressed Linear Algebra for Large-Scale Machine Learning" (research paper + poster) and "SystemML: Declarative Machine Learning on Spark" (industry paper) at VLDB'16. The "Compressed Linear Algebra for Large-Scale Machine Learning" paper won the VLDB 2016 Best Paper Award. We gave two 90 minute tutorials at the BOSS'16 workshop, co-located with VLDB'16, and our paper "SPOOF: Sum-Product Optimization and Operator Fusion for Large-Scale Machine Learning" has been accepted at CIDR'17. How has the project developed since the last report? The main project has had 213 commits since August 1. The website project has had 51 commits since August 1. Since August 1, 241 issues have been reported on our JIRA site and 137 issues have been resolved or closed. 79 pull requests have been created since August 1, and 72 pull requests have been closed. Date of last release: 2016-06-15 (version 0.10.0-incubating) When were the last committers or PMC members elected? 2016-05-07 Glenn Weidner 2016-05-07 Faraz Makari Manshadi Signed-off-by: [x](systemml) Luciano Resende [ ](systemml) Patrick Wendell [ ](systemml) Reynold Xin [ ](systemml) Rich Bowen -------------------- Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important issues to address in the move towards graduation: 1. Extend Community 2. Improve Documentation and release base components 3. Graduate als TLP in 2017 after next releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? After our next releases and improving our homepage we'd like to graduate as a TLP in 2017. How has the community developed since the last report? We have increasing feedback of use cases to be covered and also a few bug reports, so Tamaya is used by developers and companies. Additionally we are doing regular bi-weekly hangouts and have defined a well defined roadmap to release and restructure our project. Apart from that we gathered feedback from JavaOne 2016: official Configuration JSR proposal and Anatole had a talk there. The conflicts that arose in the past seem to be solved as some of the mentors and early committers have left the project. Since we've established our hangouts we have the feeling of beeing more connect and able to work towards a common goal. How has the project developed since the last report? Apart from the main project we established new repositories to hold extensions and sandbox modules. In order to get rid of the problematic webpage generation we decided to start from scratch. In addition to making the API more smooth, we try to keep the base repository/project as lean as possible and prepare a next release. Due to various technical issues (infrastructure behaves differently from local builds and checkouts) we did not meet our deadline on getting a release out by the end of October. Date of last release: 2016-04-06 When were the last committers or PMC members elected? Phil Ottlinger at 2016-04-24. Signed-off-by: [X](tamaya) John D. Ament [ ](tamaya) David Blevins Shepherd/Mentor notes: John D. Ament: While the podling has had issues in the past around community growth, I am seeing them operate more consistently, with clear open discussions. I believe they're operating well and should be ready to graduate soon, if not already. -------------------- 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. Make a release: The community is working on RC from 0.1.x branch. Master has moved to start support for Spark 2.0. Currently working on RC3. 2. 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) In progress. Project elected new PPMC member. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? NONE, previous issue with LGPL dependency has been RESOLVED as the JeroMQ dependency has now been released as MPL license. How has the community developed since the last report? 1. Active communication in mailing list and gitter with early adopters 2. No worries about transitioning from old Spark Kernel code. 3. More external contributions being made. Mainly focused on master to stabilize Spark 2.0 support How has the project developed since the last report? 1. Working on 1st release. Got an RC3 going on for a vote 2. Addressing issues opened by community 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 Shepherd/Mentor notes: Drew Farris (shepherd): Two Mentors active on the mailing lists. Healthy activity and progress towards release observed on the mailing lists. -------------------- Unomi is a reference implementation of the OASIS Context Server specification currently being worked on by the OASIS Context Server Technical Committee. It provides a high-performance user profile and event tracking server. Unomi has been incubating since 2015-10-05. Three most important issues to address in the move towards graduation: 1. Continued releases, and updated dependencies 2. Grow up user and contributor communities, seeing more contribution/PR Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? We are still targeting the development of the user community. For that, we discussed about improving and polishing the website. Today, it's obvious that it's not easy to understand what Unomi can do and actually does. The purpose is to give more use cases and introduction on the mailing list. Some small improvements have been performed in that way. How has the project developed since the last report? The second Apache Unomi 1.1.0-incubating has been released. We updated key dependencies and provided new features in addition of the bug fixes. We also fixed the LGPL issue in the binary distribution. The Unomi rules and conditions engine has been improved as well. Date of last release: 2016-10-03 When were the last committers or PMC members elected? N/A Signed-off-by: [X](unomi) Jean-Baptiste Onofré [ ](unomi) Bertrand Delacretaz [ ](unomi) Chris Mattmann Shepherd/Mentor notes: Chris Mattmann: I am going to humbly request being removed as a mentor for this podling. I haven't had a chance to send it to the list but I don't have the bandwidth to actively provide oversight here. ----------------------------------------- Attachment AB: Report from the Apache jUDDI Project [Alex O'Ree] jUDDI (pronounced "Judy") is an open source Java implementation of the Universal Description, Discovery, and Integration (UDDI v3) specification for (Web) Services. The jUDDI project includes Scout. Scout is an implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR). jUDDI - All mailing lists have had very Low traffic this quarter. - 3.3.3 Released Sept 12, 2016, maintenance and bug fixes. Scout - No release this period, no development took place. - Very low volume of JAXR related questions on the mailing list. Last PMC addition and new committer April 3, 2013 (Alex O'Ree) Last Release jUDDI-3.3.3, Sept 12, 2016 There are no issues that require the boards attention at this time. Low development activity is a factor for low mailing list volume, but in all likelihood, it's from a general lack of interest in the protocol. ----------------------------------------- Attachment AC: Report from the Apache Kafka Project [Jun Rao] Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We switched to a time-based release model and plan to do a release every 4 months. We released 0.10.1.0 which includes new features such as interactive queries, time-based seek, replication quotas, and quota by user. We plan to do the next release in Feb, 2017. Community =========== Lots of activities in the mailing list. We have 2243 subscribers in the user mailing list, up 48 in the last 3 months. We have 1718 emails in the user mailing list in the last 3 months, slightly down from 1912 in the previous cycle. We have 871 subscribers in the dev mailing list, up 18 in the last 3 months. We have 5355 emails in the dev mailing list in the last 3 months, up from 5318 in the previous cycle. We elected two new committers, Jason Gustafson and Jiangjie Qin, on Sep. 6 and Oct, 31, 2016, respectively. We elected a new PMC member Gwen Shapira on Aug.17, 2016. We had several Kafka meetups in various cities in this quarter. Releases =========== 0.10.1.0 was released on Oct. 20, 2016. ----------------------------------------- Attachment AD: Report from the Apache Knox Project [Larry McCay] # Description The Apache Knox Gateway is a REST API Gateway for interacting with Apache Hadoop clusters. The Knox Gateway provides a single access point for all REST/HTTP interactions with Apache Hadoop clusters. # Issues None # Status The Apache Knox team has just wrapped up the 0.10.0 release with a number of contributions from the community. We missed our target for the release by over a month. This was due to activity in the community, discussion in how to go about testing certain contributions to determine whether goals were actually met, etc. We've begun using wiki as a means to describe Knox Improvement Proposals (KIPs). These are "one-pagers" that capture a particular vision for improvement in certain areas. They should help illustrate the roadmap for the related feature areas and map those visions to JIRAs. This helps give focus to the releases and should also help contributors see how active JIRAs map into the roadmap and vision. # Releases * 0.10.0: 2016-11-07 Added PAM support, LDAP paging, Websocket support and fixed a number of bugs - through ~25 commits. # Development Activity * Community is discussing the planning of the 0.11.0 release which will continue to use the KIPs to drive the release themes * Jira: 776 total, +23 -15 (last 30 days) * Git (Source): 15 commits over last 30 days * SVN (Site & Docs): 8 commits over last 30 days # Community Activity ## Membership Changes * Change PMC chair from Kevin Minder (kminder) to Larry McCay (lmccay). [2] * Zac Blanco was added as a committer on 8/24/2015 [1]. * We have received some more sizable contributions from the community and have a couple contributors that are emerging as candidates to be invited as committers and PMC members. * We also continue to have smaller contributions from the community and remain on the lookout for new committers to emerge. ## Mailing List Activity * user@knox: ~55 messages over last 30 days * dev@knox: ~300 messages over last 30 days (inflated due to jenkins emails) 1. http://mail-archives.apache.org/mod_mbox/knox-dev/201508.mbox/%3CD9C32FB4-CDD5-4DCD-A3D7-3BEEE97734AC%40hortonworks.com%3E 2. http://mail-archives.apache.org/mod_mbox/knox-dev/201608.mbox/%3CCAJWAuamVSN_e%3DQJFDmQaCkdeCuk2TSawXM9Tnj9nD4EViDtr5g%40mail.gmail.com%3E ----------------------------------------- Attachment AE: Report from the Apache Kylin Project [Luke Han] ## Description: =============== Apache Kylin is an open source Distributed Analytics Engine designed to provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop supporting extremely large datasets. ## Issues: ========== - there are no issues requiring board attention at this time ## Activity: ============ - Mailing list, JIRA, and commit activity are at or above average - Apache Kylin Meetup hosted on 2016-10-29 in Shenzhen, China engaged more than 200 participants, with 4 sessions from Liangyi Huang (Kylin User), Jongyoul Li (Zeppelin PMC), WeiShuo Zhen (Tableau Expert) and Yang Li (Kylin PMC) - Yang Li presented Kylin topic at ChinaHadoop live broadcast on 2016-11-3, more than 2200 people joined that session - Luke Han presented Kylin streaming topic at Analysys 10 Summit on 2016-10-28 in Beijing - Luke Han presented Kylin open source topic at QCon Shanghai on 2016-10-22 - Apache Kylin Practices eBook published on 2016-10-27 by InfoQ China ## Community: ============= - Currently 23 PMC members and committers. - No new PMC member & committer added in the last 3 months - Messages on the dev mailing list after last report: 720 - Messages on the user mailing list after last report: 402 - 224 JIRA tickets created after last report - 239 JIRA tickets closed/resolved after last report ## Releases: ============ - The latest release, v1.5.4.1, released on 2016-09-28 - v1.5.4, released on 2016-09-15 ----------------------------------------- Attachment AF: Report from the Apache Lens Project [Amareshwari Sriramadasu] ## Description: Lens provides a Unified Analytics interface. Lens aims to cut the Data Analytics silos by providing a single view of data across multiple tiered data stores and optimal execution environment for the analytical query. It seamlessly integrates Hadoop with traditional data warehouses to appear like one. ## Issues: There are no issues requiring board attention at this time. ## Activity: Community has made Lens 2.6 GA release which works with apache hive 2.1.x, with changes including the following and many more simple improvements and bug fixes. + Druid jdbc rewriter has been added + Capability for scheduling queries added + Server enhancements like http call back on query completion, driver hooks at various stages of query launching, ability to analyze sessions, detecting duplicate queries are added + Lens regression suite is has been made upto date with features coming in. + Client side enhancements : Python client has been added, results get streamed on sync queries, UI enhancements. + OLAP enhancements : Added tags to fields, start/end times for fact columns, optimize dimension filters by conveting them to fact filters ## Health report: We have 13 individual developers and 8 committers active in the quarter, with similar counts in last quarter. And 139 user emails are sent to user list in the quarter (62 in previous quarter). github contributor graph : https://github.com/apache/lens/graphs/contributors?from=2016-06-01&to=2016-11-09&type=c ## PMC changes: - Currently 18 PMC members. - Puneet Gupta was added to the PMC on Tue Sep 20 2016 ## Committer base changes: - Currently 22 committers. - No new committers added in the last 3 months - Last committer addition was Archana H at Sat May 21 2016 ## Releases: - Last release was Lens-2.6.1 on Tue Oct 25 2016 ----------------------------------------- Attachment AG: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description: Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. ## Issues: There are no issues which require board attention at this time. ## Activity: We have received a larger than usual number of contributions in October, a reason for that is our participation in Hacktoberfest (https://hacktoberfest.digitalocean.com/). Special thanks to Anthony Shaw for helping manage and review the influx of contributions. ## PMC changes: - Currently 13 PMC members. - Jeff Dunham was added to the PMC on Sat May 21 2016 ## Committer base changes: - Currently 19 committers. - Jeff Dunham was added as a committer on Sat May 21 2016 ## Releases: - 1.2.0 was released on Sep 15 2016 - 1.2.1 was released on Sep 23 2016 - 1.3.0 was released on Oct 14 2016 ----------------------------------------- Attachment AH: Report from the Apache Logging Services Project [Ralph Goers] The Apache Logging Services Project creates and maintains open- source software related to application logging. Currently there are no issues which require the board's attention. - Community Log4j 2 remains an active project. The overall community is healthy and friendly. Log4cxx is still active in the Incubator. They have been sporadic discussions regarding performing a release but little real progress has been made. In general, all subprojects are still healthy although none has grown since the last report. - Project Branding Requirements All components except Chainsaw meet the branding requirements. We will fix the Chainsaw branding with the next release. - Last three community changes * Mikael Ståldal joined as a PMC Member on June 20 2016 * Ralph Goers was voted to be the next Chair on Nov 01 2015 * Mikael Ståldal joined as a Committer on Sep 17 2015 - Releases * Log4j 2.7 (Oct 1, 2016) - Subproject summaries Log4j 2: Active. Significant work has been done to reduce or eliminate the number of objects Log4j creates and in documenting how to use Log4j in a "garbage free" manner. Quite a few bug fixes in the last 2 releases. Discussions have been held on the developer list regarding how large the Log4j 2 project has gotten, the need to have some of the builds target newer Java versions, and some new components. In support of that new git repositories have been created for log4j-audit, log4j-plugins, log4j-scala, and log4j-tools. The number of emails on the developer mailing list has increased by about 25% in the last 3 months. Log4net: Active with 2 releases within the last year and a significant uptick in activity on the dev and user lists Log4cxx: Prgoress seems to have stalled in the incubator. They have made no progress towards a release. However, the email lists still show some activity. Log4php: No activity this quarter. Chainsaw: No activity this quarter. ----------------------------------------- Attachment AI: Report from the Apache ManifoldCF Project [Karl Wright] Project description ============== ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr, OpenSearchServer or ElasticSearch. ManifoldCF also defines a security model for target repositories that permits them to enforce source repository security policies. Releases ======== ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then, there have been numerous major releases, including a 2.5 release on August 18, 2016. The next major release is scheduled for December 31, 2016. Committers and PMC membership ============================= The last committer we signed up was Furkan Kamaci on September 7, 2016. The last PMC member was Rafa Haro, voted in on August 31, 2015. Mailing list activity ===================== Mailing list activity has been light this quarter. Issues reported have been mainly garden-variety bugs. We've had several feature requests but few contributions. Dev list comments for this period have also been light, with occasional user questions. I am unaware of any mailing list question that has gone unanswered. Outstanding issues ================== No outstanding infrastructure issues are known at this time. Branding ======== We continue to believe we are now compliant with Apache branding guidelines, with the possible exception of (TM) signs in logos from other Apache products that don't have any such marks. We received word that the ManifoldCF trademark application (US TM App No. 86583085 for "MANIFOLDCF" in Cl. 9 | DLA Ref: 393457-900118) has been accepted. ----------------------------------------- Attachment AJ: Report from the Apache Marmotta Project [Jakob Frank] # Marmotta Board Report for August 2016 ## Description: Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013. ## Issues: There are no issues requiring board attention at this time. ## Activity: A very quiet quarter in the project, both in terms of development and mailing lists activity. The project struggles to find new challengues and people to actively work on the project. Issue has been discussed several times, still looking for a sustainable solution. ## Health report: The project was considered feature-complete in 3.3.0. The current release cycle (3.4.0) focused on refining and fixing bug, plus incorporation some non-core new features. The development (issues, commits, emails) has significantly come down in the last months. ## PMC changes: - Currently 11 PMC members. - Mark A. Matienzo was added as a PMC member on Wed Aug 03 2016. ## Committer base changes: - Currently 13 committers. - Mark A. Matienzo was added as a committer on Wed Aug 03 2016. ## Releases: - Last release was 3.3.0 on Fri Dec 05 2014 ## Mailing list activity: - users@marmotta.apache.org: - 114 subscribers (up 2 in the last 3 months) - 44 emails sent to list (18 in previous quarter) - dev@marmotta.apache.org: - 95 subscribers (up 2 in the last 3 months) - 74 emails sent to list (507 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache MetaModel Project [Kasper Sørensen] ## Description: Providing a common interface for discovery, exploration of metadata and querying of different types of data sources. ## Issues: - there are no issues requiring board attention at this time ## Activity: - No major events recently, but bug reports, fixes and minor feature improvements appear steadily. ## Health report: - We see a bit less activity than usual from the "usuals" in the metamodel community. But external JIRA reports etc. seem to have picked up. ## PMC changes: - Currently 11 PMC members. - Dennis Du Krøger was added to the PMC on Mon Sep 05 2016 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Dennis Du Krøger at Thu Oct 15 2015 ## Releases: - Last release was 4.5.4 on Wed Aug 03 2016 ## JIRA activity: - 17 JIRA tickets created in the last 3 months - 13 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AL: Report from the Apache MINA Project [Jean-François Maury] ## Description: Apache MINA is a network application framework which helps users develop high performance and high scalability network applications easily. ## Issues: A security vulnerability (remote command execution with OGNL) has been fixed with release 2.0.14. OGNL commands are now checked against a set of allowed characters. MINA 2.0.15 fixed a critical SSL issue (basically, when the SSL negociation failed, messages were transmtted in clear text). ## Activity: Four releases this quarty, addressing security. Although no releases showed ip this quarter, SSHD project is quite active. ## Health report: Since last report, MINA activity has increased, with 4 releases, one to come, and many fixes. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jeff Genender on Tue Apr 05 2016 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Lyor Goldstein at Thu Apr 30 2015 ## Releases: - Apache FTPServer 1.1.0 was released on Mon Oct 31 2016 - Apache MINA 2.0.15 was released on Tue Sep 27 2016 - Apache MINA 2.0.16 was released on Mon Oct 31 2016 - MINA-2.0.14 was released on Tue Aug 30 2016 ## Mailing list activity: - dev@mina.apache.org: - 365 subscribers (up 5 in the last 3 months): - 570 emails sent to list (268 in previous quarter) ## JIRA activity: - 39 JIRA tickets created in the last 3 months - 44 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AM: Report from the Apache Oltu Project [Antonio Sanso] Oltu is a project to develop a Java library which provides an API specification for, and an unconditionally compliant implementation of the OAuth v2.0 specifications. OAuth is a mechanism that allows users to authenticate and authorise access by another party to resources they control while avoiding the need to share their username and password credentials. MILESTONES Apache Oltu 1.0 was released on March 3rd 2014. Apache Oltu Oauth2 module version 1.0.2 was released June 20th 2016. Apache Oltu Parent v4 was released June 20th 2016. CURRENT ACTIVITY The core part of the project related to 'The OAuth 2.0 Authorization Framework' (RFC 6749) is pretty stable due the fact RFC 6749 is now a standard. A stable version 1.0 was released on March 3rd 2014 and some minor releases are going out regularly for bug fixing. Updated modules contained bug fixing were released June 20th 2016 . At the moment we are working on JSON Web Encryption support ( OLTU-80 - Implement JWE support for JWT IN PROGRESS ). In a recent mail thread in private@ some important things have been pointed out: The last few months it has been awfully quiet (this might also be due the fact the OAuth spec is stable). But not only, since we have some patches laying around for a while The release has not been finished. It seems some of the artifacts are not synched correctly in https://www.apache.org/dist/oltu The builds keep failing One of the outcome was that embracing the Apache way of having new blood from time to time we are going to rotate the VP for the project. COMMUNITY We have voted two new PMC members: Stein Welberg and Jasha Joachimsthal in June 2016 (13/06/2016) ISSUES There are no issues requiring board attention at this time. ----------------------------------------- Attachment AN: Report from the Apache Oozie Project [Robert Kanter] ## Description: - Oozie is a workflow scheduler system to manage Apache Hadoop jobs. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Development activity continues as can be seen from the following JIRA report: https://s.apache.org/oozie_report_nov_16 - The OOZIE-1770 Oozie on Yarn project continues to make good progress in a feature branch - An RC was recently created for a 4.3.0 release, but some issues were found that we're currently working through ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ryota Egashira on Mon Aug 10 2015 ## Committer base changes: - Currently 21 committers. - New commmitters: - Attila Sasvári was added as a branch committer on Wed Oct 05 2016 - Gézapeti was added as a branch committer on Wed Oct 05 2016 - Peter Bacsko was added as a branch committer on Mon Oct 10 2016 ## Releases: - Last release was 4.2.0 on Tue Jun 02 2015 ## Mailing list activity: - dev@oozie.apache.org: - 149 subscribers (up 1 in the last 3 months): - 3167 emails sent to list (2072 in previous quarter) - user@oozie.apache.org: - 501 subscribers (up 7 in the last 3 months): - 69 emails sent to list (108 in previous quarter) ## JIRA activity: - 97 JIRA tickets created in the last 3 months - 100 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: Report from the Apache Open Climate Workbench Project [Michael James Joyce] ----------------------------------------- Attachment AP: Report from the Apache Perl Project [Philippe M. Chiasson] --- mod_perl 2.0 -- mod_perl 2.X is designed to work with all httpd 2.X branches. mod_perl 2.0.10 was released on Wed Oct 26 2016 Most notable change included in this release is support for Perl 5.22.x --- Apache-Test -- Apache-Test provides a framework which allows module writers to write test suites that can query a running mod_perl enabled server. It is used by mod_perl, httpd and several third party applications, and includes support for Apache modules written in C, mod_perl, PHP and Parrot. Apache-Test 1.40 was released on Sep 06, 2016 -- Development -- mod_perl continues to be a healthy development community, though as a mature and stable product development moves at a naturally slower pace than in years past. Bugs are found and discussed and fixes are applied with due consideration for our production userbase. -- Users -- The mod_perl users list is seeing little activity, with a bump in activity following the 2.0.10 RCs and the final release. Patches and bug reports are few, but keep on coming. -- Commiters -- Currently 22 committers. No new changes to the committer base since last report. -- PMC -- Currently 11 PMC members. No new PMC members added in the last 3 months Last PMC addition was Steve Hay on Wed Feb 29 2012 ----------------------------------------- Attachment AQ: Report from the Apache Phoenix Project [James R. Taylor] ## Description: - Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop ## Issues: - There are no issues requiring board attention at this time ## Activity: - Released 4.8 and 4.8.1 in the last three months - Voting underway on a 4.9 and 4.8.2 release - New committer (kliew) has been added - Work progressing on a 5.0 release leveraging Apache Calcite. ## Health report: - The project is healthy and continues to grow as users look for easy ways to gain insight over and manage their ever-increasing Hadoop data through standard SQL and JDBC APIs. ## PMC changes: - Currently 24 PMC members. - Josh Elser was added to the PMC on Tue Aug 09 2016 ## Committer base changes: - Currently 29 committers. - Kevin Liew was added as a committer on Thu Nov 10 2016 ## Releases: - 4.8.0 was released on Tue Aug 09 2016 - 4.8.1 was released on Mon Sep 26 2016 ## Mailing list activity: - Both dev and user lists continue to gain subscribers - dev@phoenix.apache.org: - 219 subscribers (up 7 in the last 3 months): - 3876 emails sent to list (3688 in previous quarter) - user@phoenix.apache.org: - 521 subscribers (up 12 in the last 3 months): - 615 emails sent to list (389 in previous quarter) ## JIRA activity: - 299 JIRA tickets created in the last 3 months - 193 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: Report from the Apache POI Project [Dominik Stadler] Report from the Apache POI committee [Dominik Stadler] ## Description: - Apache POI is a Java library for reading and writing Microsoft Office file formats ## Issues: - there are no issues requiring board attention at this time ## Activity: - The 3.15 release required some time to stabilize, however the additional effort in regression testing hopefully will maninfest in lower numbers of newly introduced bugs in the library. There is constant activity in multiple areas, mostly bugfixes, cryptography enhancements and enhanced support for reading VBA macro contents. Work has begun to add a Gradle based build with a plan to replace the ageing Ant based build in the future. We released version 3.15 and are planning to release 3.16-beta1 soon in order to provide a build for one regression item that made it into 3.15. ## Health report: - activity looks good, all seems healthy, there is a constant stream of user-questions, patches and development related discussions as well as commits by various committers. ## PMC changes: - Currently 28 PMC members. - Greg Woolsey was added to the PMC on Wed Oct 05 2016 ## Committer base changes: - Currently 35 committers. - Greg Woolsey was added as a committer on Tue Oct 04 2016 ## Releases: - 3.15 was released on Wed Sep 21 2016 ## Mailing list activity: - Mainly constant membership numbers. POI is a mature project with a stable user/developer-base. - dev@poi.apache.org: - 243 subscribers (down -5 in the last 3 months): - 1071 emails sent to list (1251 in previous quarter) - general@poi.apache.org: - 130 subscribers (down -2 in the last 3 months): - 4 emails sent to list (2 in previous quarter) - user@poi.apache.org: - 655 subscribers (down -11 in the last 3 months): - 155 emails sent to list (119 in previous quarter) ## Bugzilla Statistics: - 93 Bugzilla tickets created in the last 3 months - 95 Bugzilla tickets resolved in the last 3 months - 432 bugs are open overall - Having 103 enhancements, thus having 329 actual bugs - 101 of these are waiting for feedback - thus having 228 actual workable bugs - 5 of the workable bugs have patches available ----------------------------------------- Attachment AS: Report from the Apache Qpid Project [Robbie Gemmell] Apache Qpid is a project focused on creating software based on the Advanced Message Queuing Protocol (AMQP), currently providing a protocol engine library, message brokers written in C++ and Java, a message router, and client libraries for C++, Java / JMS, .Net, Python, Perl and Ruby. # Releases: - Qpid Dispatch 0.6.1 was released on 15th Aug 2016. - Qpid Proton 0.14.0 was released on 26th Aug 2016. - Qpid Python 1.35.0 was released on 26th Aug 2016. - Qpid CPP 1.35.0 was released on 6th Sept 2016. - Qpid JMS 0.11.0 was released on 8th Sept 2016. - Qpid JMS 0.11.1 was released on 3rd Oct 2016. - Qpid Proton 0.15.0 was released on 13th Oct 2016. - Qpid for Java 6.0.5 was released on 1st Nov 2016. # Community: - The main user and developer mailing lists continue to see good activity, and JIRAs are being raised and addressed, both in line with prior levels. - There were no new committer or PMC member additions in this quarter. The most recent new committer is Ganesh Murthy, added on 29th Feb 2016, with the most recent PMC addition being Lorenz Quack on 7th March 2016. # Development: - Work continues towards a Qpid Dispatch 0.7.0 release incorporating various improvements and bug fixes. An initial candidate was taken to vote, but some blocking issues were found and are being worked through. - Development toward Qpid Proton 0.16.0 is well under way, containing various fixes and further work on improving integration with frameworks. There has been some discussion to clarify direction for Proton going forward and how to progress this, including suggestion to make the C (+bindings) and Java components independently releasable as we have with various other components previously. - Good progress is being made on implementing JMS 2.0 support in the AMQP 1.0 JMS client, with aim to release in the coming weeks. - Development on the broker and AMQP 0-x JMS client continue toward a new Qpid for Java release. An initial 6.1.0 candidate was taken to vote, but testing identified some issues that are currently being resolved ahead of a new vote. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment AT: Report from the Apache REEF Project [Markus Weimer] ## Description: Apache REEF (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. ## Issues: No issues require the board's activity at this time. ## Activity: - REEF 0.15.1 was released during the reporting period. (Pending) - Lots of work towards REEF.NET on Linux - Significant enhacements to the Iterative MapReduce layer to support fault tolerant machine learning algorithms. ## Health report: Overall, the community is healthy: there is a constant flow of bug reports, fixes and discussions. That said, we have not seen new people show up on the dev list during the reporting period. This is something we will have to discuss in the community. ## PMC changes: - Currently 21 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrew Chung on Tue Nov 17 2015 ## Committer base changes: - Currently 33 committers. - No new committers added in the last 3 months - Last committer addition was Carlo Curino at Tue Jun 07 2016 ## Releases: - Last release was 0.15 on Sun May 22 2016 ## Mailing list activity: Mailing list activity is down significantly. At the same time, JIRA activity is about the same as in the last few quarters. Activity seems to have migrated from the dev list to JIRA and GitHub pull request discussions. - dev@reef.apache.org: - 68 subscribers (down -1 in the last 3 months): - 935 emails sent to list (1570 in previous quarter) - user@reef.apache.org: - 7 subscribers (up 7 in the last 3 months) ## JIRA activity: - 147 JIRA tickets created in the last 3 months - 107 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AU: Report from the Apache River Project [Patricia Shanahan] ## Description: - Apache River software provides a standards-compliant JINI service. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Wrapped up River-3.0.0, released this quarter. - Continued discussion of River's future direction. ## Health report: - The ongoing future directions discussion has progressed from high level strategy to discussion of specific features and use-cases. - Two PMC members resigned during the quarter, a concern because at this point there is no stream of incoming developers to provide new committers and PMC members. Attracting new developers will be difficult until the future direction is firmed up and made visible. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bryan Thompson on Sun Aug 30 2015 - Two PMC members resigned (went emeritus) during the quarter, Simon IJskes (2016-10-23), and Tom Hobbs (2016-08-19) ## Committer base changes: - Currently 15 committers. - No new committers added in the last 3 months - Last committer addition was Dan Creswell at Mon Jun 20 2016 ## Releases: - River-3.0.0 was released on Wed Oct 05 2016 ## Mailing list activity: - The increased activity level in the dev@ mailing list is due to the combination of completing a release and the future direction discussion. - dev@river.apache.org: - 94 subscribers (up 0 in the last 3 months): - 128 emails sent to list (74 in previous quarter) - user@river.apache.org: - 95 subscribers (down -2 in the last 3 months): - 3 emails sent to list (3 in previous quarter) ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ============================================================================== = The above report received +1 votes from PMC members Patricia Shanahan, Peter Firmstone, and Bryan Thompson ----------------------------------------- Attachment AV: Report from the Apache Roller Project [Dave Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat and MySQL, and is known to run on other Java servers and relational databases. The ASF blog site at blogs.apache.org runs on Roller 5.0.3 Tomcat and MySQL. ## Issues: - There are no issues requiring board attention at this time ## Activity: - The core Roller community is small and with low activity levels. - Roller website was switched over from Apache CMS to Git PubSub with JBake - There is ongoing work to create a modernized UI using Bootstrap with Struts, but it slowed since our last report. ## Health report: - Community is made-up of part-time volunteers with limited time to devote to Roller. ## PMC changes: - Currently 5 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kohei Nozaki on Sun Dec 06 2015 ## Committer base changes: - Currently 10 committers. - No new committers added in the last 3 months - Last committer addition was Kohei Nozaki at Mon Mar 09 2015 ## Releases: - Last release was 5.1.2 on Tue Mar 24 2015 ## Mailing list activity: Subscriber counts could be taken to mean there is still good interest in Apache Roller. The low email counts reflec the low level of development and user-support activity. - dev@roller.apache.org: - 158 subscribers (up 0 in the last 3 months): - 7 emails sent to list (2 in previous quarter) - user@roller.apache.org: - 287 subscribers (up 1 in the last 3 months): - 5 emails sent to list (1 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AW: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: - Library implementing XML Digital Signature Specification & XML Encryption Specification ## Issues: - There are no issues requiring board attention at this time ## Activity: - The project team discussed the merits of a new major release for the Java project, namely so that we can introduce Java 7/8 features in the code (current release requires JDK 6). A consensus was reached that this would be a good idea, and so the master branch has been updated to 2.1.0-SNAPSHOT. Apart from this, a handful of user bugs were reported, some of which have been fixed at this point. A new minor release of the Java library will probably happen over the next quarter to include these fixes. ## Health report: - Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC. Right now there are no obvious potential new committers for the project. ## PMC changes: - Currently 6 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Marc Giger on Wed Apr 03 2013 ## Committer base changes: - Currently 16 committers. - No new changes to the committer base since last report. - Last committer addition was Marc Giger in July 2012 ## Releases: - Last release was Apache Santuario XML Security for Java 2.0.7 on Fri Jun 17 2016 ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AX: Report from the Apache Serf Project [Bert Huijben] ## Description: The serf library is a high performance C-based HTTP client library built upon the Apache Portable Runtime (APR) library. Serf is the default client library of Apache Subversion and Apache OpenOffice. ## Issues: There are no issues requiring board attention at this time. ## Activity: We released Apache Serf 1.3.9 after testing the release process and scripting on a private release. It was good to see some outside suggestions on how to improve our release process and especially how we should announce releases within the Apache foundation. ## Health report: Activity is at a normal, fairly quiet level. The serf project's activity is quite related to that of Subversion and with that projects recent affairs we slowed more than expected. ## PMC & Committer changes: Currently 11 PMC members and 12 committers. Our last new committer was added on Wed Sep 02 2015. ## Releases: Apache Serf 1.3.9 was released on Thu Sep 01 2016 trunk (1.4.x): Still stabilizing towards a new release. Slow ongoing development. ## Mailing list and Jira activity: Normal activity. A bit more activity around the release of 1.3.9. ----------------------------------------- Attachment AY: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: Apache Spatial Information System (SIS) is a Java library for developing geospatial applications. SIS enables better representation of spatial objects for searching, archiving, or other relevant spatial needs. The SIS metadata module forms the base of the library and enables the creation of metadata objects which comply with the model of international standards. The SIS referencing module enable the construction of geodetic data structures for geospatial referencing such as axis, projection and coordinate reference system definitions, along with the associated operations which enable the mathematical conversion of coordinates between different systems of reference. ## Issues: There are no issues requiring board attention at this time. ## Activity: Review and integration of contributors work: - The Google Summer of Code project has been completed [1]. The student (Hao) worked in collaboration with the Vietnamese space agency, which provided the data. * Her work on LANDSAT and GeoTIFF metadata has been integrated. * Her work on MODIS and the Catalog Services for the Web (CSW) has not yet been integrated (pending review) but this integration is planned [2]. - Rémi Maréchal is continuing Hao's work on GeoTIFF [3]. - Johann Sorel's work on the GPX format [4] (currently in the SIS development branch) is under refactoring for closer integration with the ISO 19115 metadata model and SIS DataStore model. Implementation of standards: - JSR-363 (Units of Measurement API) got its final approbation by the JCP and is now an official standard [5]. This new standard replaces JSR-275. A JSR-363 implementation has been developed in SIS. - Above replacement implies an API change not only in SIS, but also in the GeoAPI 3.0.0 standard on which SIS depends. A GeoAPI 3.0.1-RC1 release candidate has been prepared and is currently submitted for vote in the Open Geospatial Consortium (OGC) [6]. The JSR-363 implementation that we did allowed us to verify that the new GeoAPI standard works before submission to OGC Meetings: - An Open Geospatial Consortium (OGC) meeting happened in September. Reports of previous meetings were used to be posted on the SIS mailing list, but are now posted on geospatial@apache.org instead in an attempt to encourage cross-projects collaboration. - SIS will have a presentation at the ApacheCon in Sevilla. It will be part of the geospatial track, created for the second time (after ApacheCon in Vancouver) with the help of OGC. Presence on the web: - Fixed errors on the Wikipedia page about Well-Known Text (WKT) format and added Apache SIS in the list of libraries that support that format [7]. - Apache SIS is cited in a W3C draft paper about Spatial Data on the Web Best Practices [8]. * The GeoAPI 3.0.1 standard candidate cites Apache SIS as a "proof of concept" implementation. ## Health report: Development continued at an average pace of 45 commits per month. For the last quarter, 97% of those commits were by the same committer. But we saw a slight increase of activity from two other committers (Johann Sorel and Rémi Maréchal) lately, and I expect their contribution to increase slowly as SIS development shifts from low level to higher level topics. Google Summer of Code, ApacheCon and extensive javadoc are some efforts for increasing the developer base; we plan to continue those efforts. JIRA activity is low because of a tendency to write a single ticket for large topic (e.g. a single SIS-334 task for the whole JSR-363 implementation effort): - 5 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months Number of downloads from Maven central repository has been multiplied by 4 in the last 12 months (about 14000 last month). ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Marc Le Bihan on Wed Dec 10 2014 - No new PMC candidate in sight yet ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Johann Sorel at Thu Mar 31 2016 - No new committer candidate in sight for now ## Releases: - Last release was 0.7 on Fri May 27 2016 - Current tendency is about 8 months between releases [1] https://lists.apache.org/thread.html/0d044fffab99f5617e967f9049c75b0c6c91f4725b9da38e42f09e96@%3Cdev.sis.apache.org%3E [2] https://lists.apache.org/thread.html/5ef52dd9af0dbb7868e2ffe1e2fac6a15b8547fa2e1302fbd724362c@%3Cdev.sis.apache.org%3E [3] https://lists.apache.org/thread.html/7fe47cfe609bbf25e219e7bd6cba54374d4348a573d326b1ce497251@%3Cdev.sis.apache.org%3E [4] https://lists.apache.org/thread.html/6a39bb3a1c1107c0c148a5443a553f5cf0c537a7025b6a174a921b64@1460363401@%3Cdev.sis.apache.org%3E [5] https://jcp.org/en/jsr/results?id=5877 [6] https://lists.apache.org/thread.html/844320f744c879ec093f97b58a4ff00f799a53103d824d41525835af@%3Cdev.sis.apache.org%3E [7] https://en.wikipedia.org/wiki/Well-known_text#APIs_that_provide_support [8] https://www.w3.org/TR/sdw-bp/#CRS-background ----------------------------------------- Attachment AZ: Report from the Apache Spark Project [Matei Zaharia] Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python and R as well as a rich set of libraries including stream processing, machine learning, and graph analytics. Project status: - The community released Apache Spark 2.0.1 on October 3rd, 2016 as the first patch release for the 2.x branch. We also released Spark 1.6.3 on November 7th to continue patching the 1.x branch, and started voting on release candidates for Spark 2.0.2 with more patches to 2.x. - The Spark Summit Europe conference ran in Brussels on Oct 25-27 with around 1000 attendees, including presentations on new use cases at Microsoft and Facebook. - There've been several discussions on the dev list about making the development process easier to follow and giving feedback to contributors faster. One concrete thing we'd like to implement is a process to post "improvement proposals" scoping a new feature before detailed design begins, so that developers can solicit feedback from users earlier, and users can easily see the project's high-level roadmap in one place. The most recent writeup on this is at https://s.apache.org/ndAX and seems to be welcomed by contributors who've used a similar process in other ASF projects. Other things that contributors are working on are creating a template for design documents and cleaning up JIRA. Trademarks: - We are continuing engagement with various organizations. Latest releases: Nov 07, 2016: Spark 1.6.3 Oct 03, 2016: Spark 2.0.1 July 26, 2016: Spark 2.0.0 June 25, 2016: Spark 1.6.2 May 26, 2016: Spark 2.0.0-preview Committers and PMC: The last committer was added on Sept 29th, 2016 (Xiao Li). The last PMC members were added on Feb 15th, 2016 (Joseph Bradley, Sean Owen and Yin Huai). ----------------------------------------- Attachment BA: Report from the Apache Stanbol Project [Fabian Christ] Apache Stanbol provides a set of reusable components for semantic content management. The project finally managed to invite two new PMC members. One of these two new members, Rafa Haro, also managed to cut a release after more than two years without a major release. From the technical side the project is doing okay now. The release helps people to use Stanbol in a stable manner. However, the ongoing development is rather slow and no plans were made until now for future releases. The project chair started a discussion about electing a new chair who is much more involved in the daily business of Stanbol. Since the current chair has less time for Stanbol (the missed reports is a clear indication), it may be good to handover to someone else. However, it is not the intention to just drop the job but to drive the discussion for a new chair. Subscribers on the dev list: 227 Last new committer was Cristian Petroaca on May 7th, 2015 Last new PMC member were Cristian Petroaca on July 28th, 2016 Rafa Haro on July 28th, 2016 Last stack release was: Apache Stanbol 1.0.0 on Oct 23rd, 2016 Last component release was: Apache Stanbol Partial Security Release RC2 on June 5th, 2014 org.apache.stanbol.commons.security.reactor-20140602 ----------------------------------------- Attachment BB: Report from the Apache Stratos Project [Lakmal Warusawithana] ## Description: Apache Stratos is a highly-extensible Platform-as-a-Service (PaaS) framework that helps run Apache Tomcat, PHP, and MySQL applications and can be extended to support many more environments on all major cloud infrastructures. ## Issues: - It seems no one active in the project. I started thread in PMC about moving to attic. No one replied. I am not sure what can do for going forward. ## Activity: - No any coding activity - One user query - One user (who were GSOC student) said interesting to contribute to project. But no reply from PMC or Committers - No any other discussions ## Health report: Answers for board auctions raised at last board meeting. Q: How many of the 45 are in that "very few" count? A: 7 Committers Q: How many of the 45 will every commit again, since, iirc, WSO2 has dropped any activity related to Stratos? A: 10 - 15 Committers. All them are WSO2 employees. One suggestion was promoting who ever vote for last release as committers. We have not tried that. But my concern is without current committers support it is very hard new comers to get used to the code base. ## PMC changes: - Currently 45 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Pubudu Gunatilaka on Fri Sep 25 2015 ## Committer base changes: - Currently 46 committers. - No new committers added in the last 3 months - Last committer addition was Pubudu Gunatilaka at Thu Sep 24 2015 ## Releases: - Apache Stratos 4.1.6 was released on Thu Aug 10 2016 ----------------------------------------- Attachment BC: Report from the Apache Subversion Project [Evgeny Kotkov] Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community A hackathon hosted by elego was held in Berlin during October 10th-14th, with approximately 8 developers attending. The discussion was mostly focused around a new developed feature, the interactive tree conflict resolver, and a lot of progress occurred on its development. During this quarter, there is an increase in the dev@ mailing list activity (353 messages, as opposed to 188 in the previous quarter), and a slight increase in the number of commits. Our users@ mailing list is active as well, and receives about 100 messages per month from users and the community members assisting them. There has been a conflict on the ground of inviting a new PMC member, and unfortunately one of the existing PMC members has resigned from the Subversion PMC. The community is now working through several discussions that should help to avoid similar situations in the future. These discussions happen on our private mailing list. Last PMC addition was in December 2015 (James McCoy). Last committer addition was November 2015 (James McCoy). * Releases Our last 1.8.16 and 1.9.4 releases were made on April 28, 2016. The work toward 1.10.x is progressing, with no specific release date planned. ----------------------------------------- Attachment BD: Report from the Apache Synapse Project [Hiranya Jayathilaka] Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. Community ========= The last committer and PMC member was added in May 2016: Ravi Undupitiya (ravi) There is some development work taking place in the project targetting the next release. Albeit slow progress, we are hopeful that the 3.0 release can be finished soon. Releases ======== There have been no new releases since the last report. The last release of Synapse is version 2.1, which was released on January, 2012. Board Issues ============ We have elected a new PMC chair, as per the recommendation made by the board. The corresponding resolution is filed under the special orders section of the November 2016 board meeting agenda. ----------------------------------------- Attachment BE: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: Apache Syncope is an Open Source system for managing digital identities in enterprise environments. ## Issues: There are no issues requiring board attention at this time. ## Activity: This quarter has been busy with final 2.0.0 release and related announcement on the ASF blog. For the occasion, The New Stack published an interview with V.P. Apache Syncope: https://s.apache.org/x18F The new major release 2.0.0 incorporated some relevant contributions received via Github, including SYNCOPE-808 which was successfully completed as part of GSoC 2016. A pull request for SYNCOPE-809, which instead did not complete for GSoC 2016, is currently under work. About the Syncope PoC with infra, we are still on hold waiting for the availability of a "playground zone" - see INFRA-10931 for details. It has been quite a while now without any feedback or ETA, it might be the case to consider retiring the proposal. ## Health report: We have recently invited 2 new PMC members and they both accepted (this also in response to mt comment from our last report). Two talks about new features in 2.0 are scheduled for ApacheCon EU 2016 by two PMC members. ## PMC changes: - Currently 11 PMC members. - New PMC members: - Andrea Patricelli was added to the PMC on Thu Oct 13 2016 - Giacomo Lamonaco was added to the PMC on Thu Oct 13 2016 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Matteo Di Carlo at Sat Jul 09 2016 ## Releases: - 2.0.0.M5 was released on Fri Sep 02 2016 - 2.0.0 was released on Fri Sep 09 2016 - 1.2.9 was released on Fri Oct 07 2016 - 2.0.1 was released on Fri Oct 21 2016 ----------------------------------------- Attachment BF: Report from the Apache Tapestry Project [Thiago H. de Paula Figueiredo] ## Description: - Apache Tapestry is a Java component-based web framework that features high productivity, great code reuse, robust deployment, and terrific performance. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Activity on the user mailing list is slow, and unfortunately getting slower. - Questions are answered with participation of not only the core contributors but also by the community at large. Discussion focuses especially around new features of the 5.4 release. ## Branding requirement progress: - License and Security links added. - We'll try to add the 'tm' to the Apache Tapestry logo ourselves in the near future. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jochen Kemnade on Thu Mar 19 2015 ## Committer base changes: - Currently 25 committers. - No new committers added in the last 3 months - Last committer addition was Jochen Kemnade at Fri Apr 25 2014 ## Releases: - Last release was 5.4.1 on Sat Mar 19 2016 ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 41 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BG: Report from the Apache TomEE Project [David Blevins] ----------------------------------------- Attachment BH: Report from the Apache Turbine Project [Thomas Vandahl] Apache Turbine Project Board Report, November 2016 Apache Turbine is a servlet based framework that allows experienced Java developers to quickly build web applications. Turbine allows you to personalize the web sites and to use user logins to restrict access to parts of your application. Turbine is a matured and well established framework that is used as the base of many other projects. Status The Turbine project has had again some increased activity in the last quarter. We could even resurrect a former committer. In response to the feedback of the board regarding the last report: We don't currently have prospects of new committers or PMC members. However we believe that our small community is healthy enough to provide the necessary oversight. We are striving to attract new users by providing a good example of a Turbine application as a Maven Archetype. The Turbine project has no board-level issues at this time. Community changes No new committers were voted in since the last board report. The last change to the committer base was the addition of Georg Kallidis (2012/09/19). No new PMC members were voted in since the last board report. The last change to the PMC was the addition of Georg Kallidis (2013/09/30). Turbine core project We are in the process of migrating old applications to the new Turbine framework. It turns out that a number of bugs have to be fixed, mostly in supporting Fulcrum components. Also the new security model showed some weaknesses which need to be addressed. The Maven Archetype for a Hello-World-application is being prepared. We found some issues with it, so the vote was cancelled. The last released version was Turbine 4.0-M2 (2015/12/22). Fulcrum component project Some changes to the Fulcrum Intake component to support Java8 The last released component was Fulcrum Yaafi 1.0.7 (2015/10/09). ----------------------------------------- Attachment BI: Report from the Apache Usergrid Project [Todd Nine] ## Description: - Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database (Cassandra), a query engine (Elastic Search), and application layer and client tier with SDKs for developers. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Unique value implementation has been moved to Akka. This has increased stability significantly. We're also in the process of implemented multi-region via Akka, removing the dependency on AWS for a multi region Impl. ## Health report: - Usergrid is healthy and the community is growing at a moderate pace. ## PMC changes: - Currently 25 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Dunker on Mon Jan 18 2016 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was George Reyes at Tue Sep 29 2015 ## Releases: - Last release was 2.1.0 on Wed Feb 17 2016 ## Mailing list activity: - The list has been slow. Our features have stabilized, and our primary concern is on operational stability. As a result, the removal of AWS dependencies has been the primary focus. - dev@usergrid.apache.org: - 97 subscribers (up 1 in the last 3 months): - 126 emails sent to list (337 in previous quarter) - user@usergrid.apache.org: - 128 subscribers (up 5 in the last 3 months): - 24 emails sent to list (77 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BJ: Report from the Apache Velocity Project [Nathan Bubna] ## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Very busy, thanks to one developer, with others testing and discussing changes. Prep and final debugging for Engine 2.0 release. Much work happening on Tools 3.0 also. ## Health report: - Engine 2.0 test builds are coming steadily, release should be soon. - Work is also in progress toward a Tools 3.0 release. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Mike Kienenberger at Mon Jun 01 2015 ## Releases: - velocity-master POM 2 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 30 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BK: Report from the Apache Whimsy Project [Sam Ruby] ## Description: Tools that help automate various administrative tasks or information lookup activities ## Issues: There are no issues requiring board attention at this time ## GitHub experiment: - No issues to report. Commits are pushed to GitHub and mirrored to ASF hardware and push logs are maintained. Net: while the infrastructure is in place to enable pushing to the ASF clone, the Whimsy project is defacto operating with GitHub as master. ## Health report: - While there remains sufficient oversight, and three active committers, there has been no progress this quarter in growing a development community. ## Development: - In order to address board agenda lockups during board meetings, synchronous server sent events were replaced with an asynchronous and event driven websocket implementation. Further improvements were made this month to catch missing updates which required manual refreshes to see. - Replaced secretary workbench with a more maintainable implementation; one that also relieves the infrastructure team from debugging and cleaning up after a mal-formed email or a wedged svn working copy required attention. This change also enabled a number of performance improvements and some minor functionality improvements (e.g. more tailored email messages). ## PMC and committer base: - Currently 9 committers, all on the PMC. - Last addition was Craig L Russell in December of 2015. ----------------------------------------- Attachment BL: Report from the Apache Xalan Project [Steven J. Hathaway] The Apache Xalan Project develops and maintains libraries and programs that transform XML documents using XSLT standard stylesheets. Our subprojects use the Java and C++ programing languages to implement the XSLT libraries. Xalan is a mature project, but we are hoping to acquire more committers who can help with integration builds for a new release that integrates Xerces-C. ISSUES FOR THE BOARD None. CURRENT ACTIVITY Oregon State University Capstone has accepted a project to use Xalan. The project also uses Xerces, the Unicode ICU, and possibly the xml-commons entity resolver. Steve Hathaway is the project mentor. There are three students doing the software integration work. We are currently integrating the Xerces-C parser patch release into a Xerces-C patch release. Most of the communications traffic is via JIRA. Email list activity has been stagnant for 3 months. MEMBERSHIP Changes in the PMC membership: None. Last new committer: May 2014 PROJECT RELEASES Xalan Java 2.7.2 April 15, 2014 Xalan C/C++ 1.11 October 31, 2012 Publishing of project releases was refreshed Oct 30, 2014. OTHER ISSUES We would still appreciate more active persons to build Xalan-C tests. We continue to get requests for Xalan to support XSLT version 2. The Xalan libraries currently support XSLT version 1. Feature ugrades and migration will require more than a few committers. BRANDING ISSUES None. ----------------------------------------- Attachment BM: Report from the Apache Xerces Project [Michael Glavassevich] ----------------------------------------- Attachment BN: Report from the Apache XML Graphics Project [Glenn Adams] ## Description: - The Apache XML Graphics Project is responsible for software intended for the creation & maintenance of the conversion of XML formats to graphical output & related software components. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - During this reporting period, activity on the three sub-projects has remained low. ## Health: - The level of community and developer activity remains at a low level for a relatively mature product, albeit one with a fair number of outstanding unresolved issues. ## PMC: - No new PMC member during this period. - Currently 11 PMC members. - Vincent Hennebert resigned from the PMC on Oct 20 2016 - Last PMC addition was Simon Steiner on Jan 19 2016 ## Committers: - No new committer during this period. - Currently 21 committers. - Last committer addition was Matthias Reischenbacher, May 2015 ## Releases: - No releases during this period. - XMLGraphics Commons 2.1 was released on Wed Jan 13 2016 - XMLGraphics FOP 2.1 was released on Wed Jan 13 2016 ## Mailing Lists: - Slight decrease in number of subscribers. Mail lists show a 32% reduction in message traffic from the previous period, down from 517 to 349. ----------------------------------------- Attachment BO: Written Consent of the Directors of The Apache Software Foundation to action without meeting The undersigned, being all of the directors of The Apache Software Foundation, consent to the following resolutions in accordance with Section 5.12 of the Bylaws of the Foundation. 1. Appoint Vice President, Conferences WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to appoint an officer responsible for Conferences, including but not limited to management of the ASF's relationships with event producers, and as a liaison with project management committees. NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President, Conferences" be and hereby created, the person holding such office to serve at the direction of the President, and to have primary responsibility of managing the ASF's relationships with event producers; and be it further RESOLVED, that Rich Bowen be and hereby is appointed to the office of Vice President, Conferences, to serve in accordance with and subject to the direction of the President and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. 2. Fill Vacancy in Board of Directors WHEREAS, the Board of Directors is in receipt of a resignation as director from Sam Ruby; and WHEREAS, Section 5.7 of the Bylaws of the The Apache Software Foundation provide for the filling of vacancies by the affirmative vote of the majority of the remaining directors; and WHEREAS, an objective analysis of the last election results indicates that Rich Bowen would be an appropriate candidate to fill the vacancy, NOW, THEREFORE, BE IT RESOLVED, that the resignation of Sam Ruby be accepted effective immediately, and BE IT FURTHER RESOLVED, that Rich Bowen be hereby appointed as a director of The Apache Software Foundation, to serve in accordance with and subject to the Bylaws of the Foundation for the remainder of the current term, concluding at the next annual meeting of members, and until his or her successor shall have been elected and qualified or until his or her earlier resignation, removal or death. Directors: Shane Curcuru Bertrand Delacretaz Isabel Drost-Fromm Marvin Humphrey Jim Jagielski Chris Mattmann Brett Porter Mark Thomas ------------------------------------------------------ End of minutes for the November 16, 2016 board meeting.