The Apache Software Foundation Board of Directors Meeting Minutes December 21, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:35 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/3420 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 - joined at 11:00 Bertrand Delacretaz Isabel Drost-Fromm Marvin Humphrey Jim Jagielski Chris Mattmann Brett Porter Mark Thomas Directors Absent: none Executive Officers Present: Ross Gardler Kevin A. McGrail Sam Ruby Craig L Russell Executive Officers Absent: Ulrich Stärk Guests: Alan Gates Daniel Gruno Davor Bonaci Greg Stein Hadrian Zbarcea Henri Yandell Jacopo Cappellato Jake Farrell Jean-Baptiste Onofré Mark Bretl P. Taylor Goetz Par Niclas Hedhman Sean Kelly Sharan Foga Tom Pappas Chris Douglas 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of November 16, 2016 See: board_minutes_2016_11_16.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] The majority of discussion over the last month has been around the way in which project's enforce their brand, as covered in the President's report. In the next month, I'll start preparing for the Annual Members Meeting again, looking to set a date in March again. B. President [Sam] Overall ======= My priorities remain: budget, brand, fundraising, then EA/TAC. EVP will be reporting on other areas. Virtual has changed from outsourcing Professional Employer Organization (PEO) services to a third party to bringing this in house. The only immediate change that contactors will see is a modest reduction in the number of days they have to select a health care provider should they be interested in taking advantage of this benefit. The end date remains the same, it is only the start date that is slightly delayed. There is a possibility that there may be some cost reductions that Virtual can pass on to us down the road, but that has yet to be seen. I'm working with the Treasurer to review a policy for ASF issued credit cards which was prepared by Virtual. Budget ====== We now have a draft FY17 budget for review and approval. It's not perfect, but I encourage the board to approve it as is and to provide feedback on what changes should be made for the FY18 budget. The budget reflects direct input from the following officers: Brand Management, Fundraising, Infrastructure Administrator, and Marketing and Publicity. In all other areas, I'm carrying forward the data provided by Virtual as these areas are low risk and are likely to come in on budget. This budget includes a modest amount of funding for Fundraising activities. I see this as experimental: we are going to try things to see what works and what does not. Monthly fundraising reports will identify specifics as to how the money is spent and attempt to relate those expenditures with potential future sponsorships. In my opinion there has been an unwarranted amount of attention on Brand Management budget. While it is true that for the first time Brand Management expenses are expected to exceed TAC, it still remains under both EA and Marketing and Publicity expenses. If funding were tight -- which it most definitely is not -- I personally would recommend looking elsewhere for savings first. To be fair, the pushback to date hasn't been so much on the amount but whether or not alternatives have been explored to see if lower cost options might be viable. I'll merely observe that similar questions could productively be asked of each budget area, and that Brand Management isn't in my opinion a priority in either likelihood of finding savings or in the amount of savings. My top priority for that remains infrastructure; not because I feel that it is poorly run (it is not), but due to the size of that budget item even a small change could produce a substantial savings. Brand Management ================ Prior direction to this area was to decentralize where possible. I'm now seeing signs that this approach will need to be modified. More data is needed, and -- heads up! -- some board guidance and perhaps intervention may be required. I've added a discussion item to the agenda for this purpose. Overall, my feeling is that having EITHER Brand Management OR the PMCs be responsible for marks (as an either/or) is problematic. As PMCs will rarely need to worry about marks, this responsibility can be quickly forgotten. What we need is: 1) a way to track issues (which Mark and Shane are working on), and for both Brand Management and PMCs be jointly responsible for identifying and opening issues. Brand Management's searches will need to be prioritized, and Shane has taken a first pass at doing exactly that. I'd like to see Mark's work to create a private JIRA instance to be in a position where it is ready to be used by the start of the next (January) board meeting, and am willing to task infrastructure with helping make this happen if that is needed. 2) for the expectation to be set that PMCs to be the first line of defense, in terms of contacting outside parties using the documented process; and for there to be some consequences spelled out for PMCs that don't meet these expectations. 3) for Brand Management (and/or the President) being the last line of defence after PMCs have taken every reasonable step to resolve the issue. This does not need to be resolved this month. It may be prudent to wait until the effort to better track issues provides more data. Fundraising =========== Not quite yet fully on my radar, and continues to be well on track to support our increased FY17 expenditures, but preliminary discussions have occurred with a focus on making sure that we plan for a future that may rely more heavily on paid support. The primary idea is to expand beyond the tech focused companies that dominate our platinum sponsors. An example of a company that we want to attract is Capital One. Longer lead times and lower individual company contributions than Platinum sponsors, but the thought is that once we get a toehold in an industry we can get others to follow. This will require more careful tracking and physically being at places where we don't normally show up, so some expenditures for support from Virtual and a travel budget to places like conferences is included in the draft budget. EA/TAC ====== As this month's report again shows, much of the EA's time is still going to TAC related activities. A fundamental rethinking of the role of the EA is overdue. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] @Tom: post the treasurer's report to board minutes @Sam: work with Tom to explore having Tom add raw data to treasurer's report before the board meeting Income and Expenses for November 2016 CASH BASIS "Preliminary" Current Balances: Orig FY17 YTD FY17 Orig November 2016 Budget Variance YTD 2016 Budget Variance Citizens Checking $ 393,623 Citizens Money Market $ 1,204,457 Amazon- ASF Payments $ - Paypal - ASF $ 100,838 Total Checking/Savings $ 1,698,918 Income Summary: Public Donations $ 1,772 - 1,772 13,874 - 13,874 Sponsorship Program $ 45,000 88,667 (43,667) 475,795 207,667 268,128 Programs Income $ 27,200 - 27,200 27,200 - 27,200 Other Income $ - - - 825 - - Interest Income $ 493 - 493 3,515 - 3,515 Total Income $ 74,466 88,667 (14,201) 521,209 207,667 312,717 Expense Summary: Infrastructure $ 54,975 57,929 (2,954) 365,152 348,197 16,955 Sponsorship Program $ - - - - - - Programs Expense $ - - - - - - Publicity $ 7,078 5,455 1,623 85,181 82,593 2,589 Brand Management $ 11,623 1,959 9,664 40,914 4,823 36,091 Conferences $ - - - 2,194 10,778 (8,585) Travel Assistance Committee $ - 1,294 (1,294) 19,864 33,975 (14,111) Tax and Audit $ - - - 6,000 6,000 - Treasury Services $ 3,100 3,100 - 21,700 21,700 - General & Administrative $ 10,412 8,371 2,041 64,042 65,084 (1,042) Total Expense $ 87,188 78,108 9,080 605,047 573,150 31,898 Net Income $ (12,722) 10,559 (23,281) (83,839) (365,483) 281,644 D. Secretary [Craig] Secretary continues to run smoothly. In November, 68 iclas, 4 cclas, and 9 grants were received and filed. E. Executive Vice President [Ross] As previously agreed, my focus is to be on the areas of the foundation that are running well. For the most part, therefore, my reports are expected to be uneventful. That being said, I have not done a good job of as I might in staying abreast of the activities in these areas. Fortunately, we have full reports. For infrastructure all open positions have now been backfilled and new hires are being onboarded. Exploring GitHub as a master continues to be a focus, along with finding ways to reduce the infrastructure costs per project. For conferences the dates for ApacheCon North America 2017 in Miami were released (May 15-19, 2017), at the Intercontinental Miami. Marketing proceeds as expected. Thank you to Sally and all contributors to the FY17 Q2 report which was published on 12/15 (https://s.apache.org/oTOF). A new monthly blog series "Success at Apache" has also been launched to share success stories from the foundation. Sally is seeking content for this blog. TAC has reported final numbers and budget for ApacheCon EU (13 recipients, budget $26,190.04). Two of the TAC recipients have been invited to join the TAC committee. This presents some complication in that only foundation members can participate in some aspects of TAC, specifically where private information is shared by applicants. However, there are many ways in which non-members can assist that do not require access to private information. The TAC report includes some details about how many recent TAC recipients go on to participate more deeply with one or more foundation project. F. Vice Chairman [Chris] Nothing to report this month. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Chris] See Attachment 8 B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Jim] 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 [bp] # Archiva [bp] # Axis [bp] # Bahir [bp] # Bloodhound [bp] # Cocoon [bp] # Felix [bp] # Incubator [bp] # Karaf [rb] # Labs [bp] # SpamAssassin [bp] # Tajo [bp] # TomEE [bp] # VCL [bp] # Wink [bp] A. Apache Abdera Project [Ant Elder / Isabel] No report was submitted. B. Apache Allura Project [Dave Brondsema / Shane] See Attachment B C. Apache Any23 Project [Lewis John McGibbney / Marvin] See Attachment C D. Apache Archiva Project [Olivier Lamy / Bertrand] No report was submitted. E. Apache Aurora Project [Jake Farrell / Mark] See Attachment E F. Apache Axis Project [Deepal Jayasinghe / Brett] See Attachment F G. Apache Bahir Project [Luciano Resende / Rich] See Attachment G @Rich: Follow up with PMC to address previous comments H. Apache Bigtop Project [Olaf Flebbe / Jim] See Attachment H I. Apache Bloodhound Project [Gary Martin / Chris] See Attachment I J. Apache BVal Project [Matt Benson / Shane] See Attachment J K. Apache Camel Project [Christian Mueller / Brett] See Attachment K L. Apache Cayenne Project [Michael Gentry / Rich] See Attachment L M. Apache Chemistry Project [Florian Müller / Isabel] See Attachment M N. Apache CloudStack Project [Will Stevens / Marvin] See Attachment N O. Apache Cocoon Project [Thorsten Scherler / Mark] No report was submitted. @Mark: pursue a report for Cocoon P. Apache Commons Project [Gary D. Gregory / Bertrand] See Attachment P Q. Apache Cordova Project [Shazron Abdullah / Isabel] See Attachment Q R. Apache cTAKES Project [Pei J Chen / Marvin] See Attachment R S. Apache Curator Project [Jordan Zimmerman / Chris] See Attachment S T. Apache Falcon Project [Srikanth Sundarrajan / Jim] See Attachment T U. Apache Felix Project [Carsten Ziegeler / Bertrand] See Attachment U @Bertrand: Work with PMC to get a more complete report V. Apache Flex Project [Alex Harui / Shane] See Attachment V W. Apache Flink Project [Stephan Ewen / Brett] See Attachment W X. Apache Gora Project [Lewis John McGibbney / Rich] See Attachment X Y. Apache Gump Project [Stefan Bodewig / Mark] See Attachment Y Z. Apache Helix Project [Kishore Gopalakrishna / Bertrand] See Attachment Z AA. Apache Hive Project [Ashutosh Chauhan / Marvin] See Attachment AA AB. Apache Incubator Project [Ted Dunning / Jim] See Attachment AB @Jim: Mentor comments are extremely important; please try to include them. @Jim: Many projects have been incubating for years. Please address this. AC. Apache Jackrabbit Project [Michael Dürig / Mark] See Attachment AC AD. Apache Karaf Project [Jean-Baptiste Onofré / Rich] See Attachment AD @Jean-Baptiste: Provide an off-cycle report next month to reply to previous feedback AE. Apache Labs Project [Danny Angus / Isabel] See Attachment AE @Isabel: Work with PMC to see if they plan to change their remit AF. Apache Lucene Project [Tommaso Teofili / Chris] See Attachment AF AG. Apache Lucene.Net Project [Prescott Nasser / Shane] See Attachment AG AH. Apache OFBiz Project [Jacopo Cappellato / Brett] See Attachment AH AI. Apache Olingo Project [Christian Amend / Jim] See Attachment AI AJ. Apache OODT Project [Tom Barber / Shane] See Attachment AJ AK. Apache Open Climate Workbench Project [Michael James Joyce / Isabel] See Attachment AK AL. Apache OpenNLP Project [Jörn Kottmann / Rich] See Attachment AL AM. Apache OpenWebBeans Project [Mark Struberg / Chris] See Attachment AM AN. Apache Pig Project [Daniel Dai / Bertrand] See Attachment AN AO. Apache Pivot Project [Roger Whitcomb / Mark] See Attachment AO AP. Apache Portable Runtime (APR) Project [Nick Kew / Marvin] See Attachment AP AQ. Apache Portals Project [David Sean Taylor / Brett] See Attachment AQ AR. Apache Sentry Project [Sravya Tirukkovalur / Bertrand] See Attachment AR AS. Apache ServiceMix Project [Krzysztof Sobkowiak / Shane] See Attachment AS AT. Apache Shiro Project [Les Hazlewood / Marvin] See Attachment AT AU. Apache Sling Project [Carsten Ziegeler / Jim] See Attachment AU AV. Apache SpamAssassin Project [Sidney Markowitz / Isabel] See Attachment AV AW. Apache Stanbol Project [Fabian Christ / Mark] No report was submitted. AX. Apache Storm Project [P. Taylor Goetz / Chris] See Attachment AX AY. Apache Synapse Project [Isuru Udana / Brett] See Attachment AY AZ. Apache Tajo Project [Hyunsik Choi / Rich] No report was submitted. BA. Apache Tiles Project [Mick Semb Wever / Isabel] See Attachment BA BB. Apache Tomcat Project [Mladen Turk / Shane] See Attachment BB BC. Apache TomEE Project [David Blevins / Jim] No report was submitted. @Jim: pursue a report for TomEE BD. Apache Twill Project [Terence Yim / Bertrand] See Attachment BD BE. Apache UIMA Project [Marshall Schor / Chris] See Attachment BE BF. Apache VCL Project [Andy Kurth / Marvin] See Attachment BF @Marvin: Pursue response to feedback from previous board meeting BG. Apache Wicket Project [Martijn Dashorst / Mark] See Attachment BG BH. Apache Wink Project [Luciano Resende / Rich] See Attachment BH BI. Apache Xerces Project [Michael Glavassevich / Brett] See Attachment BI BJ. Apache Yetus Project [Sean Busbey / Marvin] See Attachment BJ BK. Apache Zest Project [Niclas Hedhman / Isabel] See Attachment BK BL. Apache ZooKeeper Project [Flavio Junqueira / Mark] See Attachment BL BM. Apache Geode Project [Mark Bretl / Brett] See Attachment BM Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache REEF Project Chair WHEREAS, the Board of Directors heretofore appointed Markus Weimer (weimer) to the office of Vice President, Apache REEF, and WHEREAS, the Board of Directors is in receipt of the resignation of Markus Weimer from the office of Vice President, Apache REEF, and WHEREAS, the Project Management Committee of the Apache REEF project has chosen by vote to recommend Byung-Gon Chun (bgchun) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Markus Weimer is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache REEF, and BE IT FURTHER RESOLVED, that Byung-Gon Chun be and hereby is appointed to the office of Vice President, Apache REEF, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache REEF Project Chair, was approved by Unanimous Vote of the directors present. B. Approve the 2017 FY ASF Budget The board is requested to approve the following budget for FY17. Notable increases include Infrastructure, Publicity, Brand Management, Travel Assistance, and a new item for Fundraising. Income Total Public Donations 88,874 Total Sponsorship 968,295 Total Programs 28,025 Interest Income 3,515 ======= Total Income 1,088,709 Expense Infrastructure 723,068 Program Expenses 27,200 Publicity 140,900 Brand Management 84,292 Conferences 12,418 Travel Assistance 61,519 Treasury 47,700 Fundraising 7,750 General & Administrative 113,904 ========= 1,218,751 Special Order 7B, Approve the 2017 FY ASF Budget, was approved by Unanimous Vote of the directors present. C. Establish the Apache Beam 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 unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Beam Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Beam Project be and hereby is responsible for the creation and maintenance of software related to a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities; and be it further RESOLVED, that the office of "Vice President, Apache Beam" 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 Beam Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Beam 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 Beam Project: * Tyler Akidau * Davor Bonaci * Robert Bradshaw * Ben Chambers * Luke Cwik * Stephan Ewen * Dan Halperin * Kenneth Knowles * Aljoscha Krettek * Maximilian Michels * Jean-Baptiste Onofré * Frances Perry * Amit Sela * Josh Wills NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci be appointed to the office of Vice President, Apache Beam, 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 Beam 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 Beam Project; and be it further RESOLVED, that the Apache Beam Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Beam podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Beam podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache Beam 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 approved by Unanimous Vote of the directors present. E. Establish the Apache Eagle 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 distributed monitoring solution for identifying security and performance issues in real time on big data platforms, including Apache Hadoop and Apache Spark. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Eagle Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Eagle Project be and hereby is responsible for the creation and maintenance of software related to a distributed monitoring solution for identifying security and performance issues in real time on big data platforms, including Apache Hadoop and Apache Spark; and be it further RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Eagle 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 Eagle Project: * Hao Chen * Dendukuri Hemanth * P. Taylor Goetz * Gupta Chaitali * Julian Hyde * Jilin Jiang * Kumar Senthil * Manoharan Arun * Libin Sun * Ralph Su * Jinhu Wu * Wu Michael * Edward Zhang * Qingwen Zhao * Daniel Zhou NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang be appointed to the office of Vice President, Apache Eagle, 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 Eagle 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 Eagle Project; and be it further RESOLVED, that the Apache Eagle Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Eagle podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Eagle podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7E, Establish the Apache Eagle Project, was approved by Unanimous Vote of the directors present. F. Change the Apache Zest Project Name WHEREAS, the Project Management Committee of the Apache Zest Project has chosen by vote to recommend a change of name to Apache Polygene without revision of its charges, and WHEREAS, the Board of Directors is receipt of this and deems it to be in the best interests of the Foundation and consistent with the Foundation's purposes; NOW, THEREFORE, BE IT RESOLVED, that the Project Management Committee (PMC), heretofore known as the "Apache Zest Project", shall henceforth be known as the the "Apache Polygene Project". Special Order 7F, Change the Apache Zest Project Name, was approved by Unanimous Vote of the directors present. G. Change the Apache Ignite Project Chair WHEREAS, the Board of Directors heretofore appointed Dmitriy Setrakyan (dsetrakyan) to the office of Vice President, Apache Ignite, and WHEREAS, the Board of Directors is in receipt of the resignation of Dmitriy Setrakyan from the office of Vice President, Apache Ignite, and WHEREAS, the Project Management Committee of the Apache Ignite project has chosen by vote to recommend Denis Magda (dmagda) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Dmitriy Setrakyan is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Ignite, and BE IT FURTHER RESOLVED, that Denis Magda be and hereby is appointed to the office of Vice President, Apache Ignite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7G, Change the Apache Ignite Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Role of Brand Management as it relates to PMCs. Do we empower PMCs to do what is best for their communities, and let a thousand flowers bloom, even to the point where we allow actions that may limit our abilities to enforce our marks? Or do we treat Brand as a core part of our unique Apache model for community, and require consistency in approach across all PMCs and third parties, even if it means denying use of marks to friendly third parties in ways that would benefit communities? Generalities: 1) Is the Trademark Policy a policy or a set of best practices? https://www.apache.org/foundation/marks/ 2) Are PMCs the wrong tool for trademark enforcement? Specifics: 1) Can a PMC decide that it is OK for a third party to make use of an ASF Mark in their product name? 2) Can a PMC decide that it is OK for the only attribution to the ASF for use of a mark to appear in a link in a small font at the bottom of a page? 3) Can a PMC decide that it is Brand Management's job to contact a third party who is making use of the PMC's name; or even to decide that no contact is necessary? Brand Management Discussion Marvin: it’s a policy, but a bit too verbose; can use improvement, but brand owns it Mark: it’s a policy but can have exceptions; enforcement must be delegated to PMCs with advice from VP Brand. Can a PMC unilaterally decide policy on their own? No. Sam: if there is an exception to policy should PMCs have to get approval from VP Brand? Mark: if PMC wants to act outside the policy they need to work with VP Brand. Brett: likes consistency; there's a good example in the way the press PMC handles publicity policy Chris Mattman: in regard to specifics: yes, yes, yes, as long as decisions are documented on archived list the last decision on board was PMCs should take a more active role, so this looks like a change from best practice to policy Sam: this wasn’t a change; there has always been a policy Brett: PMCs should still be very involved but it is a policy; there should be minimal burden on PMCs but the policy gives them teeth against bad actors; think of it as not to be holding PMCs to rules, but helping them Chris Douglas: there was a recent dispute with VP Brand from the October report about Hadoop China conference; VP Brand was dissatisfied with how Hadoop is managing the brand there are still lots of people showing up to work on hadoop, so who is negatively affected the way we are managing? how is hadoop PMC failing the mission? trademark enforcement is not something that engineers will do well; the value of a particular brand is limited Jim: what I see is that the public perception is there is an elite group of vendors who can make use of Hadoop marks but others cannot, and this is not a defensible situation for marks to be valuable they have to be protected; we must remember we are a 501c3 and must abide by our charter. so, we can enforce a tight policy where all vendors are playing on level field (good) or we show favoritism to some vendors, or we could lose the brand (both of which would be a bad outcome) this is potentially a slippery slope so needs to be tightly controlled and defended Bertrand: the web page with Brand policy is IMO too detailed and impossible for us to accept as policy as a whole. my suggestion would be to replace that page with a minimal list of "atomic" numbered items that the board can review to decide which items are policy and which ones are best practices only Sam: would like at least General question 1 answered as soon as possible, preferably today unless more talk might change peoples' minds Brett: leaning toward deferring a vote on whether brand has a policy or not; should come to agreement and have a resolution to vote on next board meeting AI Sam: lead the discussion offline and prepare another resolution to vote on for next meeting B. Appointing an Assistant Treasurer Kevin McGrail had the position of Assistant Treasurer before taking a leave; now that he is back, by acclamation the board reappointed him to the position. 9. Review Outstanding Action Items * Jim: Discuss new committers discussion with PMC [ Clerezza 2016-08-17 ] Status: emailed * Marvin: give feedback to PMC regarding bringing on new committers [ Pig 2016-09-21 ] Status: Complete. There was a bit of a miscommunication in that among the several people working on the Spark branch was at least one person who already had committer rights. Another, whose candidacy had been back-burnered, has now been added. * Shane: report back on resolving the hadoop trademark enforcement issues. [ Hadoop 2016-10-19 ] Status: See president's report for prerequisite questions. * Mark: pursue a report for Abdera; determine if the Attic is next [ Abdera 2016-11-16 ] Status: * Marvin: Follow up with possible termination of the project [ DeviceMap 2016-11-16 ] Status: Complete. * Shane: Follow up with PMC and legal regarding potential trademark issues with a vendor [ Spark 2016-11-16 ] Status: * Marvin: Discuss retirement with PMC: need to discuss on dev/user list [ Stratos 2016-11-16 ] Status: In progress. A discussion is underway on the Stratos dev list. We'll probably receive a retirement resolution next month. * Bertrand: Work with the Incubator PMC to clarify / better document the [ Action Items 2016-11-16 ] Status: not done yet, slipped through the cracks 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:24 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] As usual, this is the slow time of year. I’ve been working with Accounting to obtain the actuals for ACEU (had to wait for the credit card statement to get the currency conversion). All actuals are in, and we came in $4,809.96 under budget (as seen in my VP TAC report). The booth was very busy, as it always is! We had a prime location, and I was able to convince the LF to let us keep the booth up an additional day (ASFers like to use the booth as a common meeting area/mingling spot). Due to the lack of sponsors in the “technology showcase”, the booths were scheduled only for Tuesday and Wednesday – I hope this improves for Miami!? The leftover swag was sent back with Sharan Foga for use at FOSDEM 2017. Merry Christmas, Happy Holidays, and a Happy/Healthy New Year to all!! ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] * ISSUES FOR THE BOARD Please see the president's report. In particular, a clear ratification by the board if the existing policy documents posted on the website are correct or not. While PMCs report to the board, my expectation is that the brand policies are required policies by PMCs, and that the board will take action to work with PMCs repeatedly refusing to follow them. If there are specific policies that the board wishes to change to guidelines, that would be fine. If the board votes to change all brand policies to be non-required, well... I'm not sure what other work there would be for Brand Management to do. https://www.apache.org/foundation/marks/ Also, please see the brand request in the President's submitted budget. * OPERATIONS trademarks@ requests and questions both internally and externally; and discussions from PMCs and Members, continues to grow beyond the capacity of the few regularly participating Brand Management Committee members to respond to. Our current volunteer pool and resources are insufficient to continue to be able to provide sufficient services for projects requesting help or registrations. I do not have a current solution for this, so over the next quarter will work with the President to look for improvements or additional proposals to the board. To address some of the questions from the many discussion threads about brand processes and details of specific issues, I have published some additional information for review by the board and any interested Members or committers. * REGISTRATIONS The IMPALA registrations have been donated to the ASF. Our HADOOP application in India has been published for opposition; this is the last step before the registration will actually issue. Our APACHE registration has finally issued in Brazil. Several requests are still in process at various stages. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities continue normally. After a few conversation with Tom Pappas and Virtual we agreed to request a fundraising budget. There are a few more details in the President report. Assuming the request gets approved the following months reports will provide details about how the funds are spent. As in previous years we created a Holidays greeting card and we are in the process of sending them to all our sponsors. I expect this to be completed by the time of the board meeting. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: we remain within budget with no payments due at this time. II. Cross-committee Liaison: Sally Khudairi continues work with Fundraising, Brand Management, the Apache Incubator, and Events/ApacheCon. She continues working with ASF President Sam Ruby on various Operations-related issues, is preparing the ASF's Q2 Operations Summary, launched "Success at Apache" (a new monthly blog), and has created a detailed call for a new logo for the Apache Incubator which will be announced before the end of the year. In addition, she met face-to-face with Tom Pappas and Shane Curcuru to discuss the budget for the current fiscal year, future planning/tactics across several operational activities, and strategies to manage non-Sponsor level donations. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 21 November 2016 --The Apache Software Foundation Announces Apache® Geode™ as a Top-Level Project - 15 November 2016 --The Apache Software Foundation Announces Apache® jclouds™ v2.0 IV. Informal Announcements: 3 items were published on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 126 weekly summaries published to date. 44 items were Tweeted on @TheASF. Rich Bowen has been uploading audio recordings from ApacheCon onto Feathercast. No new videos have been added to the ASF YouTube channel. Sally continues to tweet for the Apache Incubator account. V. Future Announcements: one announcement is 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 19 media queries. The ASF received 2,210 press clips vs. last month's clip count of 1,172. Media coverage of Apache projects yielded 3,027 press hits vs. last month's 4,553. VII. Analyst Relations: we responded to 3 analyst queries. Apache was mentioned in 13 reports by Gartner, 12 reports by Forrester, 10 reports by 451 Research, and 16 reports by IDC. VIII. ApacheCon liaison: Sally held newly-formatted media/analyst training at ApacheCon, with Fintan Ryan of RedMonk conducting the analyst briefings. The trainings were successful: two participants appeared in the press within 24 hours of taking the course. She also coordinated all on-site media activities and liaised 5 interviews during Apache Big Data + ApacheCon. Sally is currently working on new positioning for ApacheCon and is exploring underwriting options for the event outside of North America. Linux Foundation will be brought in once she has gained traction with candidate underwriters. IX. (Non-ASF) Industry Events and Outreach liaison: Sally is working with Sharan Foga on the ASF presence at FOSDEM 2017. X. Newswire accounts: we have 28 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] Finances ======== This past month has seen lots of activity in reviewing the FY17 "actuals" and projecting our overall FY17 expenditures, within the Infrastructure section of the budget. These numbers have been coordinated with the President and with Virtual, and are presented elsewhere in the December Board agenda. In short, Infrastructure is forecasting increases in staffing costs, cloud services, and a small amount related to a once/year gathering of the team at ApacheCon. On the other side, we're looking at lower hardware costs as we transition from ASF-owned machines towards a more flexible posture using virtual private servers in our cloud providers. Short Term Priorities ===================== - Get one or more projects launched on the Gitbox system - Training of our new staffers, particularly towards VM migration - LDAP changes to support podlings, and to integrate it within our supported services (eg. Sonar and Roller) Long Range Priorities ===================== - Move all services off ASF-owned hardware, including the difficult process of moving our email infrastructure - Finish the use of puppet for all services, then explore to move towards upgrading to Puppet 4, and/or containers for ongoing service management General Activity ================ - Finalizing the (emergency) move of the moin wiki - Continued gitbox work (see separate section) - Ongoing conversation and development plans for integrating podling management into LDAP (and other ASF tooling; particularly, gitbox) - SonarQube puppetized, LDAP-enabled, and brought up. This was a big VM move, and will enable self-service of sonar jobs - Continued work on puppetizing Roller (blogs.a.o) and moving that VM. Testing is now beginning. - Continued puppet work and VM moves - Beginning investigation of launching Fisheye services locally at the ASF to replace the third-party service run by Atlassian. Numerous projects use the service, but it will be shut down in early January. We're costing out a local replacement. - The security-vm is in testing, with a new Jira instance. This Jira will be used (privately) for the Security Team and Brand Mgmt. Uptime Statistics ================= Uptime for this reporting cycle hit 99.9% overall, with critical services staying at an impressive 100.0%. The usual culprits, Jenkins and SonarQube were responsible for dragging down the overall score, and are being replaced/updated to address this. The moin wiki, which has been moved and cleaned up heavily has improved immensely, going from a previous average of 94% uptime to a solid 100% uptime over the past few months. This weekend (Dec 17-18) we were hit by an outage at NERO, causing outages for the services hosted at OSUOSL. While the situation has been resolved, this will reflect negatively on next month's SLA. For more details, please visit: http://status.apache.org/sla/ Github as Master ================ The GitBox project is moving ahead as planned, and is generally considered ready for testing with willing projects. We are in talks with a specific project for the initial tests, and will discuss onboarding more projects as this progresses. The services involved have been set up and fully puppetized, and tests are showing good results here. While this service depends on LDAP (and thus awaits the upcoming LDAP changes for podlings), we have modified the system to work with a hardcoded list of podling members, so we can test with podlings without having to wait for the LDAP changes. We have a list of things either to be done or that have been done, at: https://pad.apache.org/p/gitbox - this outlines what we were thinking, where we are, and what remains to be done before we can consider this service production ready. We invite everyone to visit https://gitbox.apache.org/ and have a look, perhaps even try out the account linking service and provide feedback on this. 'Costs per project' Project =========================== As a long-term project, Infrastructure has been tasked with reducing the "cost per project added into our systems." There has been some work at the margins of our self-servce tools and processes, to reduce the staff/volunteer time to provide service and to reduce resource costs of these services (eg. locating services on more cost-effective providers). However, we have not made any progress on computing current per-project costs, projecting those costs, or planning mitigation strategies. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Rich Bowen] Since our last meeting, I have been primarily focused on getting the recordings from ApacheCon Seville posted to FeatherCast. In this effort, I have been enormously assisted by Felix Schumacher and Sharan Foga. I hope to get the remainder of these recordings uploaded over my Christmas break. The CFP for ApacheCon Miami is still running, and is scheduled to close February 11. December is always a slow time for this, and promotion of that event will start in earnest at the first of the year. As always, if you have suggestions for keynotes, or can make connections for sponsorship, please get in touch with me. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin] ApacheCon Europe ---------------- * 13 TAC recipients * $4,809.96 under budget ($31k budget; $26,190.04 spent) * TACers did a great job with their responsibilities; we added audio recording back in this time due to lack of sponsorship for such – there were a couple of sessions that didn’t get recorded, but the majority of them did. * Online (google) schedule for the purpose of tracking session hosts worked very well (thanks to Sergio for ensuring this was up-to-date at all times!), as did using the HipChat channel for real-time communications (great suggestion, Chris!). * 2 TAC recipients have joined the TAC Team as a result of attending ACEU * Post-conference surveys are being recorded in svn and will be posted on the website Committee – New Members --------- Sergio Fernández Issac Goldstand Darshan Kumar (ACEU2016 recipient) Gaurav Saini (ACEU2016 recipient) Miami (Provided by Nick last month) - I'm so happy to have Nick back!! ----- To try to avoid the SPOF's that affected Seville, committee members have been meeting to try to better document the process, and the pointers to other documentation / steps / resources / storage locations etc. That work so far is on the wiki at https://cwiki.apache.org/confluence/display/TAC/Apache+Travel+Assistance+Process Planning on what to do differently/better in future is also being captured there. Stats (Provided by Nick last month) ----- Of the people helped by TAC at Budapest and Vancouver, 3 have become members since the conference they attended, 2 have joined PMCs and 2 have become committers. Overall, the figures are: * People who weren't members at the conference, and now are: 23 * People who weren't committers at application, now are: 21 * People who weren't on PMCs at application, now are: 37 * People who now help with TAC: 4 (6 now with the addition of the new members after ACEU2016) * People who have never been/become committers: 27 * Unique people helped by TAC: 131 * Total number of TAC awards: 153 Merry Christmas, Happy Holidays, and a Happy/Healthy New Year to all!! ----------------------------------------- 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] Clarification and decision on JSON License, with mandate provided to projects regarding usage of said artifacts. No other 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 November 2016: 5 CVEs issued to projects (some may not be public yet). e-mails to security@ 4 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 9 Direct Vulnerability report to security@apache.org 1 [ambari] 1 [lucene] 1 [httpd] 1 [xmlgraphics] 1 [karaf] no response to reporter, OP disclosed after 7 days 1 [site] rejected 1 [axis] 1 [cxf] 1 [commons] 5 Vulnerabilities reported to projects 1 [hadoop] 1 [struts] 2 [httpd] 1 [tomcat] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] ----------------------------------------- Attachment B: Report from the Apache Allura Project [Dave Brondsema] ## Description: Apache Allura is an open source implementation of a software forge, a web site that manages source code repositories, bug reports, discussions, wiki pages, blogs, and more for any number of individual projects. ## Issues: - No issues needing board attention. ## Activity: - 1.6.0 release is currently in process - Regular development, including two-factor auth added - PMC member attended ApacheCon EU and spoke about Allura with others there - Interview article with Jaxenter published https://jaxenter.com/apache-allura-more-than-just-for-software-129214.html ## Health report: Development pace is still a bit slow, but moving along. One newer contributor is providing some merge requests. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rohan Verma on Tue Jul 26 2016 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Rohan Verma at Sat Jul 30 2016 ## Releases: - 1.6.0 votes occurring, should be released by board meeting time. ----------------------------------------- Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Apache Any23 is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: there are no issues requiring board attention at this time ## Activity: Any23 is very quiet. Very very quiet. We have brought on one new PMC member based upon a documentation contribution which is great. However Any23 remains (as is always has) very quiet. ## Health report: The health report reflects the above activity. We are actually waiting on a critical dependency release which will enable us to stabalize out test suite and push for a 1.2. release. Any23 is very quiet as always. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was William L. Anderson on Sun Aug 28 2016 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Bill Anderson at Tue Aug 30 2016 ## Releases: - Last release was 1.1 on Mon Oct 27 2014 ## Mailing list activity: It would appear that without any release coming out of Any23 our community is not growinf much... if anything it is possibly stagnating and even diminishing. As PMC Chair I am optimistic that if we can stabalize tests and release, then this outcome will change as we typically announce out releases to the W3C and other Web-based forums. - dev@any23.apache.org: - 35 subscribers (down -1 in the last 3 months): - 47 emails sent to list (104 in previous quarter) - user@any23.apache.org: - 51 subscribers (up 0 in the last 3 months): - 2 emails sent to list (6 in previous quarter) ## 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 Archiva Project [Olivier Lamy] ----------------------------------------- Attachment E: Report from the Apache Aurora Project [Jake Farrell] Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks. Project Status --------- The Apache Aurora community has continued to see growth from new users and contributors over the last quarter. There has been a great deal of activity in open code reviews with excellent community involvement. In September we released Apache Aurora 0.16.0 and since have started discussions about our next 0.17.0 release candidate. The next release will focus on a number of bug fixes, stability enhancements as well as some new features outlined in our release notes [1] Community --- Latest Additions: * Committer addition: Stephan Erb, 2.3.2016 * PMC addition: Stephan Erb, 2.3.2016 Issue backlog status since last report: * Created: 86 * Resolved: 57 Mailing list activity since last report: * @dev 169 messages * @user 37 messages * @reviews 1391 messages Releases --- Last release: Apache Aurora 0.16.0 released 09.28.2016 [1]: https://github.com/apache/aurora/blob/master/RELEASE-NOTES.md ----------------------------------------- Attachment F: Report from the Apache Axis Project [Deepal Jayasinghe] ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services frameworks and subsidiary components (both Java and C). ## Issues: - Axis2/C project is becoming inactive and we need to consider moving that to Attic as well. We moved another inactive project (Axis1) to attic on August, 2016 [1]. PMC will discuss the matter in the mailing list and update the board in next board report. ## PMC/Committer changes: - Currently 62 PMC/Commiters members. - No new committers were added in last three month (last addition was in June 2016.). ## Releases: - Axis2 Java 1.7.4 - October, 21 206. This release includes fixes for vulnerabilities affecting the admin console as well as a dependency on an Apache HttpClient version affected by known security vulnerabilities (CVE-2012-6153 and CVE-2014-3577). - Axis2 C Project and Sub-projects - Apr 2009 [1] : https://issues.apache.org/jira/browse/ATTIC-16 ----------------------------------------- Attachment G: Report from the Apache Bahir Project [Luciano Resende] Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Community Activity: Apache Bahir community has been actively working on supporting and enhancing previously available Apache Spark extensions and also creating new ones such as the new structured streaming extension for MQTT. The Apache Flink community has approached the Apache Bahir community and the two are now maintaining Apache Flink extensions in the context of Apache Bahir project. The following extensions have now been migrated to Apache Bahir : ActiveMQ, Flume and Redis connectors, and a couple more are under review as GitHub PRs. The Apache Bahir is finalizing a new 2.0.2 release based on Apache Spark 2.0.2. Issues: * No known issues Releases: 10/28/2016 - Bahir 2.0.1 Committers or PMC changes: 11/30/2016 - Christian Kadner voted as Apache Bahir committer 10/18/2016 - Robert Metzger voted as Apache Bahir committer Trademark/Branding: * No known issues. Legal Issues: * None ----------------------------------------- Attachment H: Report from the Apache Bigtop Project [Olaf Flebbe] ## Description: Apache Bigtop is a software related to a system for integration, packaging, deployment and validation of a big data management software distribution based on Apache Hadoop. ## Issues: None ## Releases: 1.1.0 was released on Fri Jan 29 2016 ## Activitiy Activity has been started again and work for a release 1.2.0 is in progress. We decided to invite two more committers and they accepted. We are monitoring if additional actions are required to drive the project forward. At ApacheCon Big Data Europe in Seville there were several talks with use cases for Apache Bigtop: * Implementing BigPetStore in Spark and Flink - Márton Balassi * Massively Parallel Data Warehousing in the Hadoop Stack (Greenplum) - Gregory Chase & Roman Shaposhnik * Attacking a Big Data Developer - Olaf Flebbe * Performance Tuning tips for Apache Spark Machine Learning workloads - Shreeharsha GN & Amir Sanjar ## PMC changes: Last PMC addition was Nate D'Amico on Fri Jan 22 2016 ## Committer base changes: Last committer additions: * Jonathan Kelly was added as a committer on Thu Dec 08 2016 * Kengo Seki was added as a committer on Tue Dec 06 2016 ----------------------------------------- Attachment I: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== The threat of moving the project to the attic is ongoing but further progress has been acheived in the form of promoting a GSoC student to be a full committer on the project. Releases ======== There have been no releases over the last three months. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 15 PMC members on the project with the last changes in December 2016: Resignations: * Mat Booth (12th December 2016) Additions: * Dammina Sahabandu (13th December 2016) The last new committers were added in May 2014. Community & Development ======================= The relatively small numbers of PMC members who are able to contribute necessary skills for the continuation of the project remains a concern although it has been mitigated by the addition of Dammina to the PMC. Dammina was already one of the most active contributors and so it is hoped that his addition will help drive the project forward. It was also sad to see the resignation of Mat Booth from the PMC but he had not considered himself to be one of the active contributors for a long time. His advice will of course be missed. The details for these PMC changes will be updated shortly. There has been a modest increase in the number of emails to the dev list over the previous quarter. Much of this was driven by Dammina with discussions of what might go into a new release, updates to Trac and new ideas around potential changes to the standard icon provider for the project. In addition there were some queries from users indicating a few problems with installation documentation and multi-product use cases that we could better support. Activity on the user list is negligible. ----------------------------------------- Attachment J: Report from the Apache BVal Project [Matt Benson] ## Apache BVal Report December 2016 ## - The Apache BVal project implements the Java EE Bean Validation specification(s) and related extensions, and became a top-level project of the foundation on February 15, 2012. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The community pulled together to get some improvements out the door for inclusion into Apache TomEE 7.0.2. A parallel effort was made to clean up the JIRA backlog, closing issues that had inadvertently become obsolete, etc. ## Health report: - The BVal project continues on limited manpower. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. ## Releases: - Apache BVal 1.1.2 was released on Wed Nov 02 2016 ## Mailing list activity: - The run-up to the 1.1.2 release is reflected by the mailing list statistics: - dev@bval.apache.org: - 43 subscribers (down -1 in the last 3 months): - 75 emails sent to list (15 in previous quarter) - user@bval.apache.org: - 51 subscribers (up 0 in the last 3 months): - 3 emails sent to list (2 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 22 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: Report from the Apache Camel Project [Christian Mueller] ## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are receiving many contributions from our contributors (via GitHub pull requests). - We are focusing the development of the next minor release Apache Camel 2.19.0. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - With the community, we are looking for a new logo for our project. ## Health report: - The project is super healthy, active and stays at a high level - At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from PMC's, committers and contributers/users. ## PMC changes: - Currently 29 PMC members. - Luca Burgazzoli was added to the PMC on Thu Oct 06 2016 ## Committer base changes: - Currently 54 committers. - No new committers added in the last 3 months - Last committer addition was Nicola Ferraro at Mon Aug 22 2016 ## Releases: - 2.16.4 was released on Sun Sep 25 2016 - 2.17.4 was released on Wed Nov 30 2016 - 2.18.0 was released on Sun Oct 09 2016 - 2.18.1 was released on Fri Dec 02 2016 ## Mailing list activity: - Mailing list activity stays at a high level. ----------------------------------------- Attachment L: Report from the Apache Cayenne Project [Michael Gentry] ## Description: Apache Cayenne is a Java database persistence framework. It takes a distinct approach to object persistence and provides an ORM runtime, remote persistence services, and a GUI mapping/modeling tool. ## Issues: There are no issues requiring board attention at this time. ## Activity: There were no releases on the stable (3.1) or alpha (4.0) branches this past reporting period, however there has been significant activity resolving issues in preparation for a 4.0.M4 release, which is currently being evaluated and voted upon. ## Health report: Cayenne is still under active development and has a stable user and developer community. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months. - Last PMC addition was Savva Kolbachev on Tue Apr 12 2016. - PMC members decided it would be good to rotate the PMC Chair from time-to-time and voted to change PMC Chair from Andrus Adamchik to Michael Gentry (vote closed Mon Oct 17 2016). ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months. - Last committer addition was Savva Kolbachev at Mon Jan 19 2015. We'd also like to note that Nikita Timofeev and Ruslan Ibragimov, while not direct Cayenne committers, have been making many needed and welcomed improvements to Cayenne recently and we appreciate their contributions to the project. ## Releases: - Last release was 4.0.M3 on Thu Feb 11 2016. We hope to have 4.0.M4 released this month. ## Mailing list activity: - dev@cayenne.apache.org: - 125 subscribers (up 1 in the last 3 months). - 85 emails sent to list (43 in previous quarter). - user@cayenne.apache.org: - 248 subscribers (up 2 in the last 3 months). - 94 emails sent to list (177 in previous quarter). ## JIRA activity: - 51 JIRA tickets created in the last 3 months. - 33 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment M: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have released OpenCMIS 1.0.0. - Not much activity except a few bug fixes. ## Health report: - The CMIS standard hasn't changed and the libraries are mature now. There is no major code development expected. ## PMC changes: - Currently 35 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ben Chevallereau on Thu Dec 11 2014 ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Sanija Shabani at Wed Nov 26 2014 ## Releases: - OpenCMIS 1.0.0 was released on Thu Sep 08 2016 ## Mailing list activity: - dev@chemistry.apache.org: - 175 subscribers (down -2 in the last 3 months): - 145 emails sent to list (194 in previous quarter) ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache CloudStack Project [Will Stevens] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage and networking devices. ## Issues: - The outstanding JIRA issue [1] has been closed in favor of a different resolution. Instead of moving `apache/cloudstack` to `apachecloudstack/cloudstack`, we will likely be participating in the Beta of the new Github As Master initiative which Apache is working on. This will give us access to the Github features we are looking for without being an anomaly in what Apache is supporting. - We are working with the ASF Infra team to finally get access to the racked servers which were donated by Citrix to Apache CloudStack for testing. It has been a slow process, but Greg is working with us to finally make these resources available to us. ## Activity: - ACS is continuing its focus on testing and release tooling. Our release cadence has intentionally slowed in favor of improving test coverage and stability of the large number of different deployment scenarios. The developers at ShapeBlue have built and open sourced a tool called Trillian which allows us to automate and more accurately test the ACS features in many different deployment scenarios. We have been integrating this tool into our development workflow to better validate the impact of proposed pull requests and to verify the functionality. - We currently have 3 releases which are in the final RC process; 4.10.0, 4.9.1 and 4.8.2. Since we have slowed the release cycle a bit in order to improve the test coverage and deployment scenarios, these releases are quite large. - The intentional slowdown in the release cycle is not a reflection of inactivity, but instead, more focus on the quality of the releases for all the different deployment scenarios ACS is used in. You will notice that the activity on the dev@ list has actually more than doubled since the previous quarter. - We continue to rely heavily on the features of Github for managing and and merging changes into our source tree. The majority of our communication around the code is actually done inline in the proposed pull requests as well as in the comments of the pull requests. We look forward to being able to use additional Github features such as `Status` and `Labels`, once the new Github As Master program is available, to improve our workflow even more. ## Health report: The ACS project is very healthy. We have a lot of activity and recently we have been able to focus on some of the challenges facing a project of our complexity. The slowing of the release cycle so we could focus on improving the testability and test automation will produce a better experience for our users. ## PMC changes: - Currently 42 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rafael Weingärtner on Sun Apr 24 2016 ## Committer base changes: - Currently 112 committers. - New commmitters: - Nicolás Vázquez was added as a committer on Fri Nov 25 2016 - Sergey Levitskiy was added as a committer on Fri Nov 25 2016 - Syed Ahmed was added as a committer on Fri Oct 07 2016 ## Releases: - Last releases were 4.9.0 and 4.8.1 around Aug 15 2016 ## Mailing list activity: We have had a lot of activity on our mailing lists recently. You will notice that our dev@ list has doubled in activity from our previous quarter. That is partly because the previous quarter was down a bit because of an extended code freeze, but in general, the mailing lists have been very active. - users@cloudstack.apache.org: - 1115 subscribers (down -8 in the last 3 months): - 743 emails sent to list (639 in previous quarter) - dev@cloudstack.apache.org: - 740 subscribers (down -1 in the last 3 months): - 4883 emails sent to list (2342 in previous quarter) - announce@cloudstack.apache.org: - 476 subscribers (down -7 in the last 3 months): - 2 emails sent to list (1 in previous quarter) - issues@cloudstack.apache.org: - 232 subscribers (up 1 in the last 3 months): - 4129 emails sent to list (1334 in previous quarter) - marketing@cloudstack.apache.org: - 235 subscribers (up 2 in the last 3 months): - 41 emails sent to list (84 in previous quarter) - press@cloudstack.apache.org: - 15 subscribers (up 1 in the last 3 months) ## JIRA activity: - 176 JIRA tickets created in the last 3 months - 40 JIRA tickets closed/resolved in the last 3 months [1] https://issues.apache.org/jira/browse/INFRA-12078 ----------------------------------------- Attachment O: Report from the Apache Cocoon Project [Thorsten Scherler] ----------------------------------------- Attachment P: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The Apache Commons project focuses on all aspects of reusable Java components. The Apache Commons components are widely used in many projects, both within Apache and without. Any ASF committer can commit to Apache Commons. The last report was on September 13 2016. ## Issues: - There are no issues that requires the boards attention this quarter. ## Activity: - The project is active with 6 releases this reporting period. - We released one new component: Apache Commons RNG 1.0. Commons RNG provides implementations of pseudo-random numbers generators that are either faster or of higher quality (and sometimes both) than java.util.Random. - Commons RDF is making its way out of the incubator into Commons toward a 1.0 release. ## Health report: - Most components in Commons are mature, but are still actively maintained (6 releases). The dev list is active. JIRA is active. Speed of responses to users is reasonable in most cases. We have 1 new PMC member, and Commons is still open to any Apache Committer. - Commons Math still feels stuck and now depends on Commons RNG in our repository. We are discussing how to evolve this component, which has caused some friction within our community, all of which can be seen on the developer's mailing list. There are several proposals for fostering new communities in place of the dwindling Commons Math one, but that those are in limbo because no consensus has been reached yet. Unedited reporter data follows. ## PMC changes: - Currently 36 PMC members. - Bruno P. Kinoshita was added to the PMC on Wed Oct 26 2016 ## Committer base changes: - Currently 142 committers. - No new committers added in the last 3 months - Last committer addition was Eric Barnhill at Tue Sep 06 2016 ## Releases: - BEANUTILS-1.9.3 was released on Sat Sep 24 2016 - BUILDPLUGIN 1.7 was released on Mon Nov 21 2016 - JCS-2.0-beta-2 was released on Mon Oct 31 2016 - LANG-3.5 was released on Thu Oct 13 2016 - RNG-1.0 was released on Sun Dec 11 2016 - WEAVER-1.3 was released on Mon Oct 17 2016 ## JIRA activity: - 177 JIRA tickets created in the last 3 months - 184 JIRA tickets closed/resolved in the last 3 months Gary Gregory, Your Apache Commons PMC Chair. ----------------------------------------- Attachment Q: Report from the Apache Cordova Project [Shazron Abdullah] ## Description: A platform for building native mobile applications using HTML, CSS and JavaScript. ## Issues: There are no issues requiring Board attention at this time. ## Activity: The iOS platform had one minor and one patch release, and the Android platform had a major and minor release, while the Windows platform only had one patch (bug fix) release. The Android platform major release (6.0.0) includes full support for Android 7.0 Nougat (API 24) while Ice Cream Sandwich (4.0) support was deprecated. The iOS platform minor release (4.3.0) includes support for CocoaPods in plugins, and also support for Xcode 8. The Windows platform patch release (4.4.3) fixes some major issues with application activation, splashscreen and VS project generation. We also had one Tools (CLI 6.4.0 and supporting libraries) release that deprecates node.js 0.x support (we will only support node.js 4.x and above starting next year), and it also includes other new features to config.xml, plus bug fixes. There were two overall plugin releases this quarter. An overall plugin release usually consists of all, if not most, of our 22 plugins. ## Health report: Our status dashboard at http://status.cordova.io is mostly all green. The badges that are red are known issues of the CI environment that we are tracking in various JIRA issues. We are actively trying to improve our testing -- we are trying to automate more manual tests, and streamlining tests across the board since the number of active contributors has dropped off. The drop off (as discussed in the last report) is due to a large number of active contributors from a major vendor being moved off the Apache Cordova project. We still have a huge backlog of Github Pull Request activity. At last estimate we had less than 150 pull requests in total, across our 60+ git repos. We are actively trying to prune the PRs by closing out stale issues or issues that cannot merge cleanly. It is harder to do so since we do not have write access to Github to close or label PRs, due to Github's limited repo access granularity. We can only clean up PRs using specially constructed empty commit messages as suggested by INFRA, but there is no facility to label PRs for organization. Our goal for plugins release is to have one per week as a cadence, and we have failed to do so again this quarter. We are working on streamlining this so it will be easier for release managers to package releases. ## PMC changes: - Currently 84 PMC members. - Darryl Pogue was added to the PMC on Sun Sep 25 2016 ## Committer base changes: - Currently 87 committers. - Darryl Pogue was added as a committer on Fri Sep 23 2016 ## Releases: - cordova-android@6.0.0 was released on Sun Oct 23 2016 - cordova-android@6.1.0 was released on Sun Nov 06 2016 - cordova-app-hello-world@3.11.0 was released on Sat Oct 01 2016 - cordova-common@1.5.0 was released on Sun Oct 09 2016 - cordova-common@1.5.1 was released on Sun Oct 16 2016 - cordova-create@1.0.1 was released on Sat Oct 01 2016 - cordova-ios@4.3.0 was released on Sun Oct 23 2016 - cordova-ios@4.3.1 was released on Thu Dec 01 2016 - cordova-js@4.2.0 was released on Tue Oct 25 2016 - cordova-lib@6.4.0 was released on Tue Oct 25 2016 - cordova-plugin-battery-status@1.2.0 was released on Tue Sep 13 2016 - cordova-plugin-battery-status@1.2.1 was released on Mon Dec 12 2016 - cordova-plugin-camera@2.3.0 was released on Tue Sep 13 2016 - cordova-plugin-camera@2.3.1 was released on Mon Dec 12 2016 - cordova-plugin-compat@1.1.0 was released on Thu Nov 03 2016 - cordova-plugin-console@1.0.4 was released on Tue Sep 13 2016 - cordova-plugin-console@1.0.5 was released on Mon Dec 12 2016 - cordova-plugin-contacts@2.2.0 was released on Tue Sep 13 2016 - cordova-plugin-contacts@2.2.1 was released on Mon Dec 12 2016 - cordova-plugin-device-motion@1.2.2 was released on Tue Sep 13 2016 - cordova-plugin-device-motion@1.2.3 was released on Mon Dec 12 2016 - cordova-plugin-device-orientation@1.0.4 was released on Tue Sep 13 2016 - cordova-plugin-device-orientation@1.0.5 was released on Mon Dec 12 2016 - cordova-plugin-device@1.1.3 was released on Tue Sep 13 2016 - cordova-plugin-device@1.1.4 was released on Mon Dec 12 2016 - cordova-plugin-dialogs@1.3.0 was released on Tue Sep 13 2016 - cordova-plugin-dialogs@1.3.1 was released on Mon Dec 12 2016 - cordova-plugin-file-transfer@1.6.0 was released on Tue Sep 13 2016 - cordova-plugin-file-transfer@1.6.1 was released on Mon Dec 12 2016 - cordova-plugin-file@4.3.0 was released on Tue Sep 13 2016 - cordova-plugin-file@4.3.1 was released on Mon Dec 12 2016 - cordova-plugin-geolocation@2.3.0 was released on Tue Sep 13 2016 - cordova-plugin-geolocation@2.4.0 was released on Thu Sep 29 2016 - cordova-plugin-geolocation@2.4.1 was released on Mon Dec 12 2016 - cordova-plugin-globalization@1.0.4 was released on Tue Sep 13 2016 - cordova-plugin-globalization@1.0.5 was released on Mon Dec 12 2016 - cordova-plugin-inappbrowser@1.5.0 was released on Tue Sep 13 2016 - cordova-plugin-legacy-whitelist@1.1.2 was released on Mon Dec 12 2016 - cordova-plugin-media-capture@1.4.0 was released on Tue Sep 13 2016 - cordova-plugin-media-capture@1.4.1 was released on Mon Dec 12 2016 - cordova-plugin-media@2.4.0 was released on Tue Sep 13 2016 - cordova-plugin-media@2.4.1 was released on Mon Dec 12 2016 - cordova-plugin-network-information@1.3.0 was released on Tue Sep 13 2016 - cordova-plugin-network-information@1.3.1 was released on Mon Dec 12 2016 - cordova-plugin-splashscreen@4.0.0 was released on Tue Sep 13 2016 - cordova-plugin-splashscreen@4.0.1 was released on Mon Dec 12 2016 - cordova-plugin-statusbar@2.2.0 was released on Tue Sep 13 2016 - cordova-plugin-statusbar@2.2.1 was released on Mon Dec 12 2016 - cordova-plugin-test-framework@1.1.3 was released on Tue Sep 13 2016 - cordova-plugin-test-framework@1.1.4 was released on Mon Dec 12 2016 - cordova-plugin-vibration@2.1.2 was released on Tue Sep 13 2016 - cordova-plugin-vibration@2.1.3 was released on Mon Dec 12 2016 - cordova-plugin-whitelist@1.3.0 was released on Tue Sep 13 2016 - cordova-plugin-whitelist@1.3.1 was released on Mon Dec 12 2016 - cordova-plugin-wkwebview-engine@1.1.0 was released on Tue Sep 13 2016 - cordova-plugin-wkwebview-engine@1.1.1 was released on Mon Dec 12 2016 - cordova-windows@4.4.3 was released on Tue Oct 25 2016 - cordova@6.4.0 was released on Tue Oct 25 2016 - plugman@1.4.0 was released on Tue Oct 25 2016 ## JIRA activity: - 399 JIRA tickets created in the last 3 months - 336 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache cTAKES Project [Pei J Chen] ## Description: Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is an open-source natural language processing system for information extraction from electronic medical record clinical free-text. ## Issues: - The majority of the committee has been working very hard to push forward the next release since has been almost 2 years since the last release as pointed out in the last report. There are volunteers and an RM already stepped forward and started the process. However, there is a small group which differs in opinion and prefers to delay/block the critical minor/patch release (https://s.apache.org/Q0iS). Looking forward to a concensus soon. ## Activity: - There was a successful cTAKES hackathon during AMIA's NLP Working Group earlier in Nov at Chicago, IL (https://s.apache.org/IVqy) - There has been continued activity and contributions in new components in sandbox and improvements to current components (Clinical De identification, ctakes-wsd, ctakes-temporal, etc. ) - There is interest from new committers to improve the current codebase such as Java File Resource loading improvements, general code clean up, etc. - Committee continues to work on the next release (see above notes). ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michelle Chen on Mon Feb 02 2015 ## Committer base changes: - Currently 35 committers. - New commmitters: - Azad Dehghan was added as a committer on Fri Jun 03 2016 - Lewis John McGibbney was added as a committer on Fri May 27 2016 - Peter Klügl was added as a committer on Fri May 27 2016 - Richard Eckart de Castilho was added as a committer on Fri May 27 2016 ## Releases: - Last release was 3.2.2 on Sat May 30 2015 - 3.2.1 was released on Dec 10 2014 - 3.2.0 was released on Jul 23 2014 ## Mailing list activity: The mailing lists remain active with discussions and there is steady growth in interest and increase in number of subscribers from various institutions. - dev@ctakes.apache.org: - 211 subscribers (up 8 in the last 3 months): - 85 emails sent to list (60 in previous quarter) - user@ctakes.apache.org: - 189 subscribers (up 4 in the last 3 months): - 75 emails sent to list (46 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment S: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: - The Apache Curator Java libraries make using Apache ZooKeeper much easier and more reliable. ## Issues: - Curator participated in the "help wanted" project. To date, we've not gotten any real help. People don't even bother to subscribe to the mailing list. It appears they are just fishing to see if they can pad their CVs. So, this isn't a Curator "issue" per se, but I thought I'd take this opportunity to report about it. ## Activity: - Curator activity is normal for this period - We continue to produce releases, field questions, etc. - We continue to track releases of Apache ZooKeeper and try to stay current with it ## Health report: - Curator is a healthy, active project. We have consistent, quality input from the community and Curator usage continues to grow. - I've learned that Facebook will be standardizing on Apache Curator as its primary ZooKeeper client - good news! - Curator's health is intimately tied to Apache ZooKeeper and, from our perspective, Apache ZooKeeper is a very healthy project - Curator could use 1 or 2 more active committers. A few individuals have been identified and, assuming they continue to contribute, votes can take place ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Drob on Thu Jul 23 2015 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Mike Drob at Fri Jul 24 2015 ## Releases: - Apache Curator 2.11.1 was released on Mon Nov 14 2016 - Apache Curator 3.2.1 was released on Mon Nov 14 2016 ## Mailing list activity: - dev@curator.apache.org: - 54 subscribers (up 1 in the last 3 months): - 336 emails sent to list (180 in previous quarter) - user@curator.apache.org: - 159 subscribers (up 2 in the last 3 months): - 94 emails sent to list (96 in previous quarter) ## JIRA activity: - 13 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache Falcon Project [Srikanth Sundarrajan] ABOUT Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. ISSUES There are no issues that require board's attention at this time. STATUS Work is currently underway in Falcon to support user space extensions to easily extend various data management operations without requiring changes to the core Falcon code. This, the project team hopes will help encourage developers to contribute repetitive and useful data processing & management functions for reuse. Besides the team is also reviewing work relating to update of Falcon entities with an effective time, essentially supporting use cases where users can go back in time and reprocess data without submitting newer processing entities. Earlier, we had introduced feature in Falcon to visually monitor processing backlog through a monitoring system. The community of developers and their activity has come down compared to the past, however core set of developers continue to make heavy contributions to the project and help move forward. The project team continues to be on the lookout for new committers to maintain sustainable growth of software and usage. PMC CHANGES - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sowmya Ramesh on Mon Jun 06 2016 COMMITTER CHANGES - Currently 24 committers. - Praveen Adlakha was added as a committer on Fri Nov 04 2016 RELEASES - Last release was 0.10 on Mon Aug 08 2016 MAILING LIST ACTIVITY - dev@falcon.apache.org: - 110 subscribers (down -3 in the last 3 months): ----------------------------------------- Attachment U: Report from the Apache Felix Project [Carsten Ziegeler] Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. Community PMC: The last new PMC member was added in Jul. 2016. Committers: The last new committer was added in Jul. 2016. Steady mailing list activity. There are no issues requiring board attention at this time. Software Apache Felix HttpLite 0.1.5 (November 30th, 2016) Apache Felix Resolver 1.10.1 (November 7th, 2016) Apache Felix Config Admin 1.8.12 (October 25th, 2016) Apache Felix Framework 5.6.1 (October 24th, 2016) SCR Tooling: Apache Felix Maven SCR Plugin 1.23.0, Apache Felix SCR Bnd Plugin 1.6.0, Apache Felix SCR Ant Task 1.16.0, Apache Felix SCR Annotations 1.12.0, and Apache Felix SCR Generator 1.15.0 released (October 18th, 2016) Apache Felix Preferences 1.1.0 (October 15th, 2016) Apache Felix Http Jetty 3.4.0, Apache Felix Http Bridge 3.0.16, and Apache Felix Http Base 3.0.16 (October 8th, 2016) Apache Felix Framework 5.6.0, Framework Security 2.6.0, and Resolver 1.10.0 released (September 25th, 2016). ----------------------------------------- Attachment V: Report from the Apache Flex Project [Alex Harui] Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES - Apache Flex FalconJX 0.7.0 was released on 9/7/16. Voting underway for Apache Flex SDK 4.16.0. - Apache Flex SDK 4.15.0 was released on 1/9/16. - Apache Flex BlazeDS 4.7.2 was released on 11/16/15. - Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14. - Apache Flex Tool API 1.0.0 was released on 11/20/14 - Apache Flex Squiggly 1.1 was released on 10/26/14 - Apache Flex Installer 3.2.0 was released on 6/23/15. ACTIVITY The past three months saw a significant increase in committer activity around FlexJS. FlexJS is the next generation of Flex that provides application developers with a highly productive framework and tool chain for developing web apps, mobile apps and desktop apps. Traditional Flex applications require Adobe Flash/AIR runtimes (or tools to pre-compile them to Android/IOS). FlexJS applications output HTML/JS/CSS and can even be used to create Apache Cordova applications. A few new names have appeared, but none are at the point of being committer-candidates yet. But two existing committers have jumped in, making significant contributions to the UI toolkit by creating a library with a Material Design look-and-feel. COMMUNITY - Greg Dove was added as a committer. - No new PMC members this quarter either. - Last PMC addition was Josh Tynjala on Wed Sep 16 2015. Flex has recently attracted committers that show up for 3 months and just as we are thinking they are ready for PMC nomination, they go quiet. But I am encouraging one PMC member to nominate one recent committer so hopefully that will happen before the next report. - Latest analytics include a little less than 1000 hits per day on the website during the work week (less on weekends). - There were more than 14,000 installs of Apache Flex 4.15.0 since its release in January. - Almost 115,000 people have run the Tour De Flex application. Tour De Flex is a set of examples folks use to learn how to develop Flex applications. TRADEMARKS - A company is promoting a software product called Flex that appears to be related to themes/styles for website visuals. Despite several attempts to contact them, they have not responded. The ASF VP Trademarks sent them an email on 11/3/16. I did not see a response and their website is still up. What is the next step? ----------------------------------------- Attachment W: Report from the Apache Flink Project [Stephan Ewen] DESCRIPTION Apache Flink is a distributed data streaming system for batch and streaming data analysis on top of a streaming dataflow engine. Flink's stack contains functional batch and streaming analysis APIs in Java and Scala and libraries for various use cases. Flink interacts and integrates with several Apache projects in the broader ecosystem of data storage and computing, such as Apache Beam (incubating), Hadoop, Kafka, HBase, Cassandra, Bahir, and others. ISSUES - There are no issues that require board attention. STATUS AND ACTIVITY - The Flink community is heading towards the 1.2 release, which is the biggest release so far. The community decided to add backwards compatibility of "application state" from this release on (in addition to API compatibility since version 1.0.0). Releasing version 1.2 is also the blocker for merging a large feature branch on resource management that many contributors have worked on over the last months. - The community is also in the progress of releasing the bug fix release 1.1.4. This release is the result of a major effort with large production users to address robustness issues found in such installations. - There will be 'Flink Forward' conferences in San Francisco (April 2017) and Berlin (September 2017). The PMC will be in touch with the organizers to make sure the event is endorsed by the Flink community and respects the Apache trademark guidelines. - 'data Artisans' conducted a survey among Flink users and contributors, with the goal to share the results with the community. The survey is currently being evaluated, results to be shared soon. - In the previous quarter, the Flink community started working together with the Apache Bahir community. The first connectors are now exclusively managed by the Bahir project, and not part of the Flink project any more. - Several community members have started to voice concerns that the Flink code base is getting very intensive to build and test. Individual discussions in these threads suggested to kick of a proper discussion after the 1.2 release is out. COMMUNITY There was no new PMC addition since the last report. The latest PMC addition was July 2nd, 2015 (Maximilian Michels) No new committers have been added since the last report. The last committer addition was Tzu-Li (Gordon) Tai on August, 26th, 2016. Flink currently has 24 committers and 16 PMC members. RELEASES The following releases were made since the last board report: → 1.1.3 was released on October, 12th, 2016 ACTIVITY ON JIRA / MAILING LISTS Both user@f.a.o and dev@f.a.o lists are quite active, with mails getting answered by a mix of committers and non-committers. JIRA is even more active than in the three month period before (730 JIRA tickets created, 545 JIRA tickets resolved) ----------------------------------------- Attachment X: Report from the Apache Gora Project [Lewis John McGibbney] ## Description: The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key value stores, document stores and RDBMSs, and analyzing the data with extensive Apache Hadoop™ MapReduce support. ## Issues: - there are no issues requiring board attention at this time - A new member is currently being brought into the Gora PMC ## Activity: - Gora has come off the back of a very productive summer. The proect has seen two new modules being committed however they have not been released. The next goal is for the PMC and Commiter base to push the 0.7 release. ## Health report: - A number of Gora modules are slightly behind, however what we support is stable. We had excellent representation... yet again at ApacheCon where one of our GSoC students clearly displayed how flexible as framework Gora truly is. JCache is now supported over any Gora datastore implementation. A huge win for those that want and require object-to-datastore transactions. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Pierre Sutra on Mon Jun 13 2016 ## Committer base changes: - Currently 22 committers. - No new committers added in the last 3 months - Last committer addition was Pierre Sutra at Sat May 21 2016 ## Releases: - Last release was 0.6.1 on Sun Sep 13 2015 ## Mailing list activity: Dev@ is stable... there is nothing more to say. We will have more user@ when we release 0.7. The fact that we have increased subscribers is marginally decent. - dev@gora.apache.org: - 75 subscribers (up 1 in the last 3 months): - 145 emails sent to list (400 in previous quarter) - user@gora.apache.org: - 77 subscribers (up 3 in the last 3 months): - 7 emails sent to list (12 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 10 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Y: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == vmgump has been replaced with a new VM with most of the installation being automated via Puppet. == Releases == Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. == Activity == As indicated in the last report we've freed up the Linux VM named vmgump so its host Eirene can get decommissioned. The new installation vmgump-vm3 is based on a Puppet module for most of it, a few manual steps remain as they require credentials we don't want to store in a repository. == Changes to the Roster == All ASF committers have write access to the metadata that configure the ASF installations. The last changes to the PMC have seen Konstantin Kolinko and Mark Thomas join in November 2014. ----------------------------------------- Attachment Z: Report from the Apache Helix Project [Kishore Gopalakrishna] ## Description: - A cluster management framework for partitioned and replicated distributed resources ## Issues: - None ## Activity: - Activity has been increased in the last quarter with multiple contributions. - 13 pull requests merged in last 3 months. - 43 commits in last 3 months. ## Health report: - Project had a release recently and added a new PMC ## PMC changes: - Currently 17 PMC members. - Lei Xia was added to the PMC on Tue Dec 06 2016 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Lei Xia at Tue May 10 2016 ## Releases: - Last release was 0.6.6 on Oct 31 2016 ## Mailing list activity: - dev@helix.apache.org: - 69 subscribers (up 0 in the last 3 months): - 162 emails sent to list (65 in previous quarter) - user@helix.apache.org: - 100 subscribers (up 2 in the last 3 months): - 35 emails sent to list (10 in previous quarter) ## JIRA activity: - 12 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Hive Project [Ashutosh Chauhan] ## Description: - The Apache Hive (TM) data warehouse software facilitates querying and managing large datasets residing in distributed storage. ## Issues: - No issues needing board attention at this point in time. ## Activity: - Misuse of trademark by Korean company of using Hive in their product name has been resolved. Their website now has no mention of said violation. - Trademark registration request is pending to tm-registeration@ - A bug fix release for 2.1 a.k.a 2.1.1 is released. - Discussion is underway on dev list for doing releases with stability as primary focus. ## Health report: - Project continues to have strong user community which is active on users@. - Project continues to receive strong contributions from various contributors. ## PMC changes: - Currently 31 PMC members. - No new PMC members in the last 3 months. - Last PMC addition: Sat Jul 16 2016 (Jesus Camacho Rodriguez) ## Committer base changes: - Currently 61 committers. - Last committer addition: Tue Dec 13 2016 (Rajesh Balamohan) ## Releases: - 2.1.1 was released on Wed Dec 07 2016 ## Mailing list activity: - dev@hive.apache.org: - 849 subscribers - user@hive.apache.org: - 2176 subscribers ## JIRA activity: - 677 JIRA tickets created in the last 3 months - 436 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for December 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 65 podlings incubating, another record high. There were seven releases published in the month of November. There were seven new IPMC members elected and one member who left. * Community New IPMC members: - Kasper Sørensen - Willem Ning Jiang - Luke Han - Par Niclas Hedhman - Jukka Zitting - Stian Soiland-Reyes - Kasper Sørensen People who left the IPMC: - Sean Busbey * New Podlings - RocketMQ - OpenWhisk - Weex * Graduations The board has motions for the following: - Beam - Eagle The following have already graduated into sub-projects: - CommonsRDF -> Apache Commons RDF * Releases The following releases entered distribution during the month of November: - Apache Ranger 0.6.2-incubating 2016-11-08 - Apache Streams 0.4-incubating 2016-11-10 - Apache SystemML 0.11.0-incubating 2016-11-12 - Apache CommonsRDF 0.3.0-incubating 2016-11-15 - Apache CarbonData 0.2.0-incubating 2016-11-19 - Apache Metron 0.3.0-incubating 2016-11-28 - Apache Gearpump 0.8.2-incubating 2016-11-28 * IP Clearance - None * Legal / Trademarks - None * Infrastructure - None * Miscellaneous - Work has begun on updating Apache Incubator documentation to better align with current infrastructure requirements and provide better guidelines to new podlings on how to get setup. * Credits - Report Manager: John D. Ament -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - Annotator - AriaTosca - NetBeans - OpenWhisk - Spot * Not yet ready to graduate No release: - MRQL - Myriad - Pirk - SAMOA - Trafodion - Wave Community growth: - Atlas - Gearpump - Hivemall - HTrace - Mnemonic - Pony Mail - Quickstep - Singa - Tephra * Ready to graduate - Ranger - Streams - Taverna The Board has motions for the following: - Beam - Eagle * In trouble, further actions required - log4cxx2 - Omid ---------------------------------------------------------------------- Table of Contents Annotator AriaTosca Atlas Gearpump Hivemall HTrace log4cxx2 Mnemonic MRQL Myriad NetBeans Omid OpenWhisk Pirk Pony Mail Quickstep Ranger SAMOA Singa Spot Streams Taverna Tephra Trafodion Wave ---------------------------------------------------------------------- -------------------- Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. Three most important issues to address in the move towards graduation: 1. Achieving active development cadence 2. Attracting new contributors 3. Establishing presence (web, repo, activity) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Beginning work within the ASF has been slow (and rather confusing). Mailing list activity has improved, but still low volume. Development priorities are still being discussed. We do now have repositories for code and the website, but are blocked by needing access to them--the request as been made to the general@incubator list. However, we have successfully gotten Jira and Confluence setup for the project and have a promotional web page ready and waiting once access has been granted. Making the incubation process clearer (and ideally more automated) would have saved a lot of time and confusion. That said, our Champion (Daniel Gruno), has been most helpful in helping us navigate. How has the community developed since the last report? Discussions have begun on development priorities. Infrastructure helped us resolve some outstanding project setup needs (Jira, Confluence, and git for the web site and code). Once the site is online, we intend to promote the community more and make concrete plans out of the proposals made on the mailing list so far. How has the project developed since the last report? Same as above. Mostly discussion and infrastructure/access setup--some still in progress. Date of last release: None. When were the last committers or PMC members elected? None since start of incubation. Signed-off-by: [*](annotator) Nick Kew [ ](annotator) Brian McCallister [ ](annotator) Daniel Gruno [ ](annotator) Jim Jagielski Shepherd/Mentor notes: Drew Farris (shepherd): One mentor active on mailing lists and another's assistance is referenced in the board report. Annotator is still getting off the ground. Observed recent mailing list activity seeking to set a path forward for the project. -------------------- AriaTosca ARIA TOSCA project offers an easily consumable Software Development Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and Orchestration Specification of Cloud Applications) based solutions. AriaTosca has been incubating since 2016-08-27. Three most important issues to address in the move towards graduation: 1. Grow the community and enroll new committers. 2. Have frequent Release cycles to be compliant with the Apache Way. 3. Publish "How To Contribute" guide at ARIA-TOSCA Website. 4. Update ARIA website acording to ASF guideline(Include release process for ARIA-TOSCA Project) 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. Update: the ticket is now in progress. How has the community developed since the last report? * Open-O is in process for consuming the ARIA ASF package * Cloudfiy is in process for consuming the ARIA ASF package as well. * Need to work on building the community and accepting external contributions. How has the project developed since the last report? * TOSCA parser migrated into ASF * CI on Appveyor, Jenkins * Sphinx documentation added to the project * CLIs of workflow engine and parser coalesced * TOSCA CSAR packager added * APIs for workflows, operations * Workflow engine task retry support * Workflow engine execution cancel support Date of last release: No Releases yet When were the last committers or PMC members elected? Project is still functioning with the initial set of committers. Signed-off-by: [X](ariatosca) Suneel Marthi [X](ariatosca) John D. Ament [ ](ariatosca) Jakob Homan Shepherd/Mentor notes: John D. Ament: The podling is still getting its feet wet. Discussions are starting to happen on the mailing lists rather than in physical offices which is good and will help to bring about a more diverse community. I would also strongly encourage the podling to work with their mentors to get infra changes in to avoid confusion. -------------------- Atlas Apache Atlas is a scalable and extensible set of core foundational governance services that enables enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the complete enterprise data ecosystem. Atlas has been incubating since 2015-05-05. Three most important issues to address in the move towards graduation: 1. Podling name search is pending. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No specific issues at this time to report. How has the community developed since the last report? 1. We have added 3 new committers since the last report from different organizations. About 10 new contributors have been added since the last report. The current number of contributors is around 70. 2. The activity on the atlas-dev mailing list stands at around 610 messages per month between September and November [1] 3. People across various organizations are interested in exploring Atlas. We have received comments and suggestions from people who are evaluating Atlas for their governance requirements [5] How has the project developed since the last report? 1. We are working towards a 0.8-incubating release in the next couple of months. This upcoming release would include major features like structured high level REST APIs, entity creation/updation from Atlas UI,DSL Search improvements, Atlas Hook support for Hive2, Knox SSO support for Atlas, addition of user defined and system attributes to entities 2. An abstraction layer has been added to make Atlas agnostic to the underlying graph database version 3. A total of 186 issues were reported between Sep 1st 2016 and Nov 30th 2016. 122 issues have been resolved in the same time [2][3] Date of last release: 2016-07-09: 07-incubating [4] When were the last committers or PMC members elected? 1. The PPMC voted and elected 3 new members as committers to the project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal Sharma. Links [1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/ [2] https://issues.apache.org/jira/browse/ATLAS-1341?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%20%272016-09-01%27%20and%20created%20%3C%3D%20%272016-11-30%27 [3] https://issues.apache.org/jira/browse/ATLAS-1335?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%20%272016-09-01%27%20and%20resolved%20%3C%3D%20%272016-11-30%27 [4] https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3CCAAbv78fuzCv51E4Pn8fg7nwkJyOUQo9z2WNhsiz2EstbTvj1Gw@mail.gmail.com%3E [5] http://www.ibmbigdatahub.com/blog/case-open-metadata Signed-off-by: [ ](atlas) Arun Murthy [x](atlas) Chris Douglas [ ](atlas) Jakob Homan [ ](atlas) Vinod Kumar Vavilapalli -------------------- Gearpump Gearpump is a reactive real-time streaming engine based on the micro-service/Actor model. Gearpump has been incubating since 2016-03-08. Three most important issues to address in the move towards graduation: 1. Make initial Apache branded release and release on a regular schedule. 2. Continue to evolve community interest and support. 3. Integrate within Apache Beam and akka-streams frameworks. - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None - How has the community developed since the last report? Increased community contribution on integration with Apache Cassandra. - How has the project developed since the last report? Two Apache source releases and one binary release - Added Window DSL and Triggers. Continued integration within Apache Beam (Gearpump Runner). Codes have been merged to runner-gearpump branch on Beam and Beam capabilities are being built into Gearpump. - Continued integration within akka-streams (Gearpump Materializer). 4 PRs have been committed to akka and an akka-stream feature branch has been created on Gearpump. - 75 issues created and 55 resolved - Manu presented Gearpump at Strata Beijing 2016 - Kam presented Gearpump Materializer at Reactive Summit 2016 - Huafeng and Karol co-presented Gearpump at ApacheCon Big Data Europe 2016 Date of last release: 2016-11-30 When were the last committers or PMC members elected? No new committers or PMC members elected yet. Signed-off-by: [ ](gearpump) Andrew Purtell [ ](gearpump) Jarek Jarcec Cecho [ ](gearpump) Reynold Xin [ ](gearpump) Todd Lipcon [ ](gearpump) Xuefu Zhang [X](gearpump) Jean-Baptiste Onofré -------------------- Hivemall Hivemall is a library for machine learning implemented as Hive UDFs/UDAFs/UDTFs. Hivemall has been incubating since 2016-09-13. Three most important issues to address in the move towards graduation: 1. Create the first Apache release 2. Community growth (committers and users) 3. Migrate the development community from Github to ASF infra Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * All SGAs and I-CLA has been submitted and recorded * Daniel Dai is elected as a new Mentor on Nov 22 https://lists.apache.org/thread.html/48a61eb44188d3f204e7c41ff7c102128e9325eed029ab41a23ff3a9@%3Cdev.hivemall.apache.org%3E How has the community developed since the last report? * Presented a talk in Cloudera World Tokyo on Nov 8. * Created Twitter Account: @ApacheHivemall How has the project developed since the last report? * Collected and submitted all SGAs and I-CLA required for IP clearance https://issues.apache.org/jira/browse/HIVEMALL-9 * Finished updating License headers and NOTICE https://issues.apache.org/jira/browse/HIVEMALL-12 * Finished the initial code dump on Dec 1 and the development moved to ASF infra https://issues.apache.org/jira/browse/HIVEMALL-6 https://github.com/apache/incubator-hivemall * Created 5 JIRA Issues and resolved 4 issues in the last 30 days https://issues.apache.org/jira/browse/HIVEMALL/ Date of last release: No release yet (planning the first Apache release in Q1, 2017) When were the last committers or PMC members elected? * Daniel Dai (Mentor) on Nov 22 Signed-off-by: [ ](hivemall) Reynold Xin [ ](hivemall) Markus Weimer [ ](hivemall) Xiangrui Meng [X](hivemall) Daniel Dai -------------------- HTrace HTrace is a tracing framework intended for use with distributed systems written in java. HTrace has been incubating since 2014-11-11. Three most important issues to address in the move towards graduation: 1. Continue to grow the Apache HTrace community 2. Continue to explore projects integrating Apache HTrace 3. Continue to develop and release stable Apache HTrace incubating artifacts Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There are no issues requiring board attention at this time. How has the community developed since the last report? Mailing lists have been quiet. Little activity during this period. How has the project developed since the last report? Released htrace-4.2.0 and added a new committer. Date of last release: htrace-4.2.0 October 6th, 2016 When were the last committers or PMC members elected? +Mike Drob (mdrob) October 3rd, 2016 - Committer+PMC Member Signed-off-by: [x](htrace) Jake Farrell [ ](htrace) Todd Lipcon [ ](htrace) Lewis John Mcgibbney [ ](htrace) Andrew Purtell [x](htrace) Billie Rinaldi [x](htrace) Michael Stack -------------------- log4cxx2 Logging for C++. N.B. This is a reboot of the Log4cxx podling which previously graduated. log4cxx2 has been incubating since 2013-12-09. Three most important issues to address in the move towards graduation: 1. Create a release 2. Activate some community 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There was a discussion in the first quarter of the year to move the project to attic unless it is able to release in the next few months. No release happened since then. Currently it seems that there's only one official project member with commit access left and even though some contributor worked on fixing the release process, that project member was unable to invest the necessary time to create a release yet. For that reason, the left member decided to not even care anymore about a release and published this decision on the dev mailing list of the project. While the member is still willing to provide some support and would regret a move of the project to attic, creating a release has no priority nor is seen as strictly necessary and will therefore most likely always prioritize lower than other tasks. How has the community developed since the last report? 3 support questions, no new project members. There was a lengthy discussion about switching to C++ standard smart pointers with possibly breaking the API, the influence of such an approach on a release etc. Some bugs have been created to coordinate that work. Robert Middleton started to move the project to smart pointers using boost or std::shared_ptr in a private GitHub repo. He's actually changing more code than the one left official project member. https://github.com/rm5248/log4cxx-testing/tree/smart_pointers Date of last release: 2008-04-03 was the last official, pre-incubation 0.10.0 When were the last committers or PMC members elected? Signed-off-by: [X](log4cxx2) Ralph Goers Shepherd/Mentor notes: Ralph Goers: The Log4j PMC will need to have a discussion about the state of this project. Since Log4cxx2 was always intended to be a subproject of the Logging project moving it to the attic may or may not be the right move. Instead, it might just become a "dormant" subproject. -------------------- Mnemonic Apache Mnemonic is an advanced hybrid memory storage oriented library, we've proposed a non-volatile/durable Java object model and durable computing service that bring several advantages to significantly improve the performance of massive real-time data processing/analytics. developers are able to use this library to design their cache-less, SerDe-less and native-direct computing high performance applications. Three most important issues to address in the move towards graduation: 1. Apache releases: we have release version 0.3.0-incubating 2. Improved dev. docker to facilitate development. 3. provided information to potential customers e.g. bank user, other project's Apache committers 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 April. Since then * Two more developers are going to join our community. * We need to encourage more discussion on the dev list in the coming months How has the project developed since the last report? * Added durable native sorting service (n-dim linked data) with testcases * Removed the 3rd Maven repository and use Maven central repository only * DOM and DNCS could apply to volatile memory service except fixed k-v store * Added a bench workload to verify the benefits from DNCS with scripts, generator * Added a sys-vmem service that makes it possible to utilize system memory for DNCS in an unified way * Added a script to bundle signed portable artifacts for maven repository submitting * and other bugfixes, features, improvements Date of last release: 2016-10-21 When were the last committers or PMC members elected? None Signed-off-by: [X](mnemonic) Patrick Hunt [ ](mnemonic) Andrew Purtell [ ](mnemonic) James Taylor [X](mnemonic) Henry Saputra -------------------- MRQL MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Hama, Spark, and Flink. MRQL has been incubating since 2013-03-13. Three most important issues to address in the move towards graduation: 1. Increase the number of active committers 2. Increase adoption, expand user community, and increase user list 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? There was one new developer who developed the new evaluation mode for MRQL that runs on top of Apache Storm. There were no new committers since our last report. How has the project developed since the last report? A new evaluation mode for MRQL queries was developed based on Apache Storm (using the Trident API). MRQL can now process stream queries on a single stream using Storm, but will be soon be extended to support multiple streams. Date of last release: 2016-03-02 When were the last committers or PMC members elected? 2014-04-17 Signed-off-by: [X](mrql) Alan Cabrera [ ](mrql) Edward J. Yoon [ ](mrql) Mohammad Nour El-Din Shepherd/Mentor notes: Alan Cabrera: Not a huge amount of activity but at least there's a small consistent trickle. I think that the fact that someone was interested in adding an Apache Storm adapter speaks somewhat to the viability of the project. -------------------- Myriad Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on the same cluster and allows dynamic resource allocations across both Hadoop and other applications running on the same physical data center infrastructure. Myriad has been incubating since 2015-03-01. Three most important issues to address in the move towards graduation: 1. Expand user/contributor/committer community 2. Gather more support from Hadoop and Mesos vendors 3. Release new versions (0.3 in progress), with more enterprise features Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? * dev@ mailing list had 73 messages since the last report. 2 new correspondents. * Bi-weekly dev syncs with 2-3 participants. Some cancelled due to lack of attendance. Minutes at http://s.apache.org/8kF * Myriad presented at HadoopWorld/Strata NYC. How has the project developed since the last report? * Myriad 0.3.0 in progress. * 1 commit/PR merged and 2 JIRAs resolved. * Myriad submitted to DC/OS Universe: https://github.com/mesosphere/universe/pull/841 Date of last release: 2016-06-20 myriad-0.2.0-incubating When were the last committers or PMC members elected? 2016-06-16 Yuliya Feldman Signed-off-by: [ ](myriad) Benjamin Hindman [x](myriad) Danese Cooper - https://lists.apache.org/thread.html/f7635ace681984cacfca6692a35221ede0000bcc70f4fcfc990433e9@%3Cdev.myriad.apache.org%3E [x](myriad) Ted Dunning [ ](myriad) Luciano Resende Shepherd/Mentor notes: John D. Ament: I am concerned about lack of engagement in this podling. Mentors need to be a bit more engaged and repsonsive. -------------------- 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? Discussed CCLA/SGA on the dev mailing list. Discussed existing mailing lists migration plan to Apache: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists+migration How has the project developed since the last report? CCLA and SGA still in the process of being approved and signed by Oracle, which will also apply the copyright headers as instructed on the dev mailing list. Started initial code cleanup analysis https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+NetBeans+Structure Oracle has already agreed to relicense the Graal.js parser under the Apache license. Resolved in LEGAL-279 the nb-javac dependency license. Almost finished new static website for Apache NetBeans. Experimented Mercurial to Git repository migration with a focus on repository size. Solution found, size not an issue anymore. 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 [X](netbeans) Daniel Gruno [ ](netbeans) Jim Jagielski [ ](netbeans) Mark Struberg -------------------- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently integrating/using Omid. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Initiated contact with Apache Phoenix community to integrate Omid. Blog entries published in Yahoo Engineering and Hadoop blogs. Article about Apache Omid incubation published in Datanami. Talk proposal on Omid sent to DataWorks Summit EU 2017 Quarter Stats (from: 2016-09-01 to: 2016-11-30): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 20 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 2 | | Resolved Issues | 1 | | Pull Requests merged | 0 | | Pull Requests proposed | 0 | +---------------------------------------------+ How has the project developed since the last report? In the process of completing its second release under in the Apache incubator. Date of last release: 2016-06-24 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [ ](omid) Alan Gates [ ](omid) Lars Hofhansl [x](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [ ](omid) James Taylor Shepherd/Mentor notes: Alan Gates: I'm concerned about this podling. The last commit was on August 15. Discounting broadcast and reminders, there have been no emails on the dev list since October, and there were only 3 that month. I've sent email on the dev list asking if people are still actively involved. Flavio Junqueira: I second Alan's concern, there has been very little activity in the last period for this podling. -------------------- OpenWhisk OpenWhisk is an open source, distributed Serverless computing platform able to execute application logic (Actions) in response to events (Triggers) from external sources (Feeds) or HTTP requests governed by conditional logic (Rules). It provides a programming environment supported by a REST API-based Command Line Interface (CLI) along with tooling to support packaging and catalog services. OpenWhisk has been incubating since 2016-11-23. Three most important issues to address in the move towards graduation: 1. The project just entered the Incubator and infrastructure is in progress to be setup. 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - How has the community developed since the last report? - How has the project developed since the last report? - Date of last release: None yet. When were the last committers or PMC members elected? - Signed-off-by: [X](openwhisk) Felix Meschberger [X](openwhisk) Isabel Drost-Fromm [X](openwhisk) Sergio Fernández -------------------- Pirk Pirk is a framework for scalable Private Information Retrieval (PIR). Pirk has been incubating since 2016-06-17. The initial code for Pirk was granted on 2016-07-11. Three most important issues to address in the move towards graduation: 1. Grow the community to establish diversity of background and expertise. 2. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process. 3. Add to and improve the Pirk user documentation and examples both on the website and in the codebase 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 attracted a couple of new contributors since the last report. The mailing list activity, pull requests, and page views to the Apache Pirk website (via Google Analytics) have also increased since the last report. An 'Introducing Pirk' talk was presented at ApacheCon Europe on November 15, 2016. How has the project developed since the last report? The project is in the process of completing its second release, 0.2.0-incubating. The project has also undertaken a refactor of some of the packages and drivers and added additional user/developer documentation on the website. Date of last release: August 29, 2016 When were the last committers or PMC members elected? Pirk elected two new committers (Tim Ellison and Suneel Marthi, both mentors) on August 18, 2016. Signed-off-by: [x](pirk) Billie Rinaldi [x](pirk) Joe Witt [x](pirk) Josh Elser [X](pirk) Suneel Marthi [ ](pirk) Tim Ellison Shepherd/Mentor notes: Josh Elser: Dev traffic appears to have slowed down a little in the past month, but nothing really to be concerned about yet, IMO. -------------------- Pony Mail Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms. Pony Mail has been incubating since 2016-05-27. Three most important issues to address in the move towards graduation: 1. Grow the community 2. Grow awareness of the project 3. Master releases and project management Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None that we know of. How has the community developed since the last report? One new committer (Sebastian Bazley) was invited to the project. How has the project developed since the last report? Email traffic has been roughly the same, 75-ish mails per month to the lists. Quite a few bugs have been worked on. Date of last release: 2016-08-02 When were the last committers or PMC members elected? - Sebastian Bazley was elected committer on October 9th, 2016. Signed-off-by: [ ](ponymail) Andrew Bayer [X](ponymail) John D. Ament -------------------- Quickstep Quickstep is a high-performance database engine. Quickstep has been incubating since 2016-03-29. Three most important issues to address in the move towards graduation: 1. Make the first release of the system. 2. Write blogs/papers on the release. 3. Help foster a user community to try out the project. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? The developer community is actively working on having more discussions on line both on code and larger project related work. In other words, embracing the Apache way both mechanistically and philosophically. How has the project developed since the last report? The code continues to make progress and is close to the point where a release can be created. Date of last release: None so far. When were the last committers or PMC members elected? Tarun Bansal was elected as a committer on Oct 27, 2016. Signed-off-by: [ ](quickstep) Konstantin Boudnik [x](quickstep) Julian Hyde [x](quickstep) Roman Shaposhnik -------------------- Ranger The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform. Ranger has been incubating since 2014-07-24. Three most important issues to address in the move towards graduation: 1. Working with Mentors on all action/preparation for Graduation 2. Re-organize documentation for easier access to end-users, new users and contributors. 3. Expanding user/dev 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? 1. Mailing list activity since last report (September-01-2016 to November-30-2016): @dev 648 @user 96 @commit 140 2. Issues (JIRAs) created/resolved since last report (after September-01-2016 before November-30-2016): Created: 71 Resolved: 48 3. Adding more community members to involve in Apache Ranger How has the project developed since the last report? 1. Released one minor release: 0.6.2 released on 11/08/2016 2. Members have been working on a next major release of 0.7.0 a. Working on the roadmap features to be delivered soon. 3. Members are actively involved in Graduation process in the dev community * "Graduation Maturity Assessment" is being discussed in the community * Elected VP/PMC Chair for Ranger: Selvamohan Neethiraj Date of last release: November-08-2016 When were the last committers or PMC members elected? 1. Velmurugan Periasamy has been added as PMC member on September-05-2016 Signed-off-by: [X](ranger) Alan Gates [ ](ranger) Daniel Gruno [ ](ranger) Devaraj Das [ ](ranger) Jakob Homan [ ](ranger) Owen O'Malley Shepherd/Mentor notes: Alan Gates: The community is actively working on graduating. They have been discussing a draft proposal on the dev list and are working out a few final details before taking it to the Incubator PMC. Based on their self assessment against the maturity model, community growth, and several Apache releases I believe they are ready to graduate. -------------------- SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Flink, Apache Storm, Apache Apex and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Grow the developer base 2. Grow the user base 3. Add some more ML techniques Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Mailing list activity (September 2016 - November 2016): * @dev: 87 messages Jira issues backlog (September 2016 - November 2016): * Created: 0 * Resolved: 1 - We manage to resolve the pending issue regarding the integration of Apache Apex with Samoa. - Also, we made some testing progress with Apache Gearpump. - We also had a presentation of Apache Samoa and its integration with Apache Apex in Apache BigData Europe 2016 - We also published a scientific paper using Apache Samoa and one of its machine learning techniques (Vertical Hoeffding Tree) (to be presented in IEEE BigData Conference in December 2016) How has the project developed since the last report? - We have performed a new release with several bug fixes and new features (0.4.0) - We are looking into new ML techniques for development. Date of last release: 2016-09-30 When were the last committers or PMC members elected? None Signed-off-by: [X](samoa) Alan Gates [ ](samoa) Ashutosh Chauhan [ ](samoa) Enis Soztutar [X](samoa) Ted Dunning Shepherd/Mentor notes: Alan Gates: Very low activity on this project over the last few months, with last commit showing as Sept 22 and very few commits since last March. A big need here beyond activity is to grow the community. There is a one individual who made several contributions last spring; I sent an email to the mailing list asking if it made sense to invite him to become a committer. -------------------- Singa Singa is a distributed deep learning platform. Singa has been incubating since 2015-03-17. Three most important issues to address in the move towards graduation: 1. Add more documentations and tutorials, to make the installation and use of SINGA easier. We have done some work as described below in the answer of 'how has the project developed since the last report'. 2. Grow the community. We added one more committer after the last report and are getting more user feedbacks. We want to further grow the community and to graduate in early 2017. 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? There were 68, 125 and 61 emails from dev@ list in September 2016, October 2016 and November 2016 respectively. There are 100 more commits since the last report. One new committer was added into SINGA committer list. How has the project developed since the last report? We released the v1.0 shortly after the last report, which include major changes in terms of the programming model and other aspects: + Tensor abstraction for supporting more machine learning models. + Device abstraction for running on different hardware devices, including CPU, (Nvidia/AMD) GPU and FPGA (to be tested in later versions). + Replace GNU autotool with cmake for compilation. + Support Mac OS. + Improve Python binding, including installation and programming + More deep learning models, including VGG and ResNet + Replace website building tool from maven to Sphinx and updated the documentations. + Integrate Travis-CI We also added python notebooks and windows support, and are working on the model zoo, python whl files and Docker images to make it easier for users to get started with SINGA. We are focusing on our niches, including distributed training at the system level and health-care models at the application level. Date of last release: 2016-09-09 When were the last committers or PMC members elected? 2016-10-21 Signed-off-by: [ ](singa) Daniel Dai [X](singa) Alan Gates [X](singa) Ted Dunning [ ](singa) Thejas Nair -------------------- 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: 1. Move infrastructure and development to ASF (code, issues, mailing list, ...) 2. Build diverse community 3. Demonstrate ability to create releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Please elaborate on the process for code scanning and IP reviews. How has the community developed since the last report? Community interaction has ramped velocity, as new adopters of the project have been posting questions through Twitter and Slack. We have added approximately 20% to our Slack channel and added several contributors through the ICLA. How has the project developed since the last report? We have moved our repo to ASF as of December 8, 2016. We have removed our LDA-C dependencies by switching to Spark LDA, eliminating licensing issues on this particular branch. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [ ](spot) Jarek Jarcec Cecho [ ](spot) Brock Noland [X](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 community has begun an internal assessment using the Apache Maturity Model to identify gaps that should be addressed before graduation. How has the community developed since the last report? Dev List 117 emails sent by 16 people, divided into 32 topics. Web Page 498 Sessions (up ~150%), 341 Users (up ~35%), 1178 Pageviews (up 10%). How has the project developed since the last report? Source Control https://github.com/apache/incubator-streams Excluding merges, 2 authors have pushed 17 commits to master and 17 commits to all branches. On master, 816 files have changed and there have been 36,280 additions and 38,567 deletions. https://github.com/apache/incubator-streams-examples Excluding merges, 2 authors have pushed 2 commits to master and 2 commits to all branches. On master, 8 files have changed and there have been 323 additions and 301 deletions. Steve Blackmon presented Apache Streams at Shark Tank, ApacheCon Europe, Seville, Spain on Nov 18, 2016. Team is presently working on 0.4.1-incubating release scheduled for the week of Dec 5, 2016. Work has been scoped out for an upcoming 0.5-incubating release scheduled for later this year. JIRA 52 issues closed with 0.4-incubating release 12 issues closed after 0.4-incubating release 16 new issues opened in November. Date of last release: 2016-11-11 : 0.4-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) Matt Franklin [X](streams) Ate Douma [X](streams) Suneel Marthi Shepherd/Mentor notes: Suneel Marthi: There's been lot of activity on the project since Sep 2016 and the project has had 2 releases since then. The project's on track for TLP graduation. -------------------- Taverna Taverna is a domain-independent suite of tools used to design and execute data-driven workflows. Taverna has been incubating since 2014-10-20. Three most important issues to address in the move towards graduation: 1. Project maturity evaluation 2. IP/licence review of unreleased repositories 3. Graduate! Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Preparing to graduate. Stian added as new mentor. How has the community developed since the last report? Added 3 new committers who were introduced via the Google Summer of Code. 2 of them did not directly work on Apache Taverna through GSoC but this was where they heard about the project. How has the project developed since the last report? The Taverna Mobile Android application is nearing release standard with all licence checks passed. Most of the codebases under the Taverna banner are also nearing release standard with an extensive licence review currently underway. Preparing maturity report, almost ready for graduation vote. Email stats dev@taverna: 2016-09: 190 emails 2016-10: 69 emails 2016-11: 78 emails Email stats users@taverna: 2016-09: 0 emails 2016-10: 3 emails 2016-11: 16 emails Jira stats: 2016-09 (6 created, 0 resolved) 2016-10 (3 created, 7 resolved) 2016-11 (0 created, 15 resolved) Git stats: 2016-09: 158 commits 2016-10: 165 commits 2016-11: 34 commits Date of last release: 2016-07-01 taverna-engine-3.1.0-incubating 2016-07-01 taverna-common-activities-2.1.0-incubating 2016-07-01 taverna-commandline-3.1.0-incubating When were the last committers or PMC members elected? 2016-10-20 Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Daniel J Debrunner [x](taverna) Stian Soiland-Reyes [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [ ](taverna) Marlon Pierce -------------------- Tephra Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 18 subscribers in dev mailing list - 21 new JIRAs filed since the last report - 4 external contributors submitted patches since the last report How has the project developed since the last report? - Working on 0.10.0 release - Released 0.9.0 Date of the last release: 2016-09-18 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates [ ](tephra) Andrew Purtell [x](tephra) James Taylor [ ](tephra) Lars Hofhansl Shepherd/Mentor notes: Drew Farris (Shepherd): Two mentors active on mailing lists. Project is building towards a healthy community. -------------------- Trafodion Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Trafodion has been incubating since 2015-05-24. Three most important issues to address in the move towards graduation: 1. Develop community and bring in more diverse contributors. 2. Continue the momentum and become more integrated with the rest of the Apache community. 3. Continue to create software releases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * None How has the community developed since the last report? * Participation in public lists has been relatively steady: 715 messages in the codereview forum, 728@commits, 257@dev, 1155@issues and 61@user. * We are working towards our next release, 2.1. * Gunnar Tapper has volunteered to be the Release Manager. * Identified items for the roadmap of our next release: - TRAFODION-2067 Support CDH 5.7 - TRAFODION-1988 Better java exception handling in the java layer of Trafodion - TRAFODION-2117 Add support of SQL extension 'EXCEPT' - TRAFODION-2060 Add support for native tinyint datatype - TRAFODION-1931 ODB tool support on Windows platform - TRAFODION-1861 Support Trafodion running on CentOS 7 - TRAFODION-1673 Implement the WITH clause in Trafodion SQL for simple use cases - TRAFODION-2047 add SQL syntax support to INTERSECT - TRAFODION-2127 enhance Trafodion implementation of WITH clause * The community continues to be active in China, with some communications happening outside the Apache dev lists, we had a discussion on the Incubator general list about that. * Community members speaking at public events: - Liu Ming had a Trafodion open-class for undergraduates at FuDan University, Shanghai on Nov 10. - Jin Jian had a Trafodion open-class for post-graduate students at FuDan University, Shanghai on Nov 24 How has the project developed since the last report? * 253 commits from 27 contributors. * 182 JIRAs filed and 113 resolved Sep 1 - Nov 30. * Many of the roadmap items listed above have been implemented, plus many more enhancements not listed above. Date of last release: 2016-07-07 2.0.1 When were the last committers or PMC members elected? in August Signed-off-by: [ ](trafodion) Devaraj Das [ ](trafodion) Enis Söztutar [x](trafodion) Michael Stack -------------------- Wave A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community has several new/re-activated contributors and participants across different disciplines since last report. The most significant developments for our community have come about since September. After an open community conference call on Sept 28th, a joint effort between Wave and SwellRT development was initiated. SwellRT API has been tried out by some members of the community and a branch containing the SwellRT code is now in the repository. Discussions are still taking place to determine the full extent of the integration as the projects share a common goal but have side plans as well. SwellRT is a fork of Wave resolving some complexity issues of the Wave code that have prevented community growth and adoption issues. How has the project developed since the last report? Some members of Wave community have tried SwellRT API and some common tasks have been performed, such as: - Cleaned up some obsolete dependencies. - New branch created on wave repo containing a mirror of SwellRT code. - Updated major dependencies and fixed minor bugs, some taken from SwellRT. Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [ ](wave) Christian Grobmeier [x](wave) Upayavira Shepherd/Mentor notes: Upayavira: SwellRT appears to be a useful addition to Wave - it was originally a fork of Wave that has been improved/simplified. The Wave community still needs to handle IP Clearance for the SwellRT codebase. ----------------------------------------- Attachment AC: Report from the Apache Jackrabbit Project [Michael Dürig] Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. In reaction of the recent move of the JSON license to Category X the PMC removed usages of respective libraries from all versions of all products released within the Jackrabbit project. See See JCR-4068 and OAK-5171. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component / sub-project. Commit activity is moderate to high in preparation of new major release early next year. The oak-dev list is seeing a broad variety of topics being discussed. ## PMC changes: - Currently 49 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Tomek Rękawek on Mon Mar 21 2016 - On Nov. 30th the PMC offered PMC membership to Andrei Dulceanu, who subsequently accepted. Formally joining the PMC is blocked by account creation being stuck and nobody reacting to my inquiries. See https://issues.apache.org/jira/browse/INFRA-13096. ## Committer base changes: - Currently 49 committers. - No new committers added in the last 3 months - Last committer addition was Tomek Rekawek at Mon Mar 21 2016 - On Nov. 30th the PMC offered committeship to Andrei Dulceanu, who subsequently accepted. Formally joining as committer is blocked by account creation being stuck and nobody reacting to my inquiries. See https://issues.apache.org/jira/browse/INFRA-13096. ## Releases: - jackrabbit-2.12.5 was released on Mon Nov 07 2016 - jackrabbit-2.12.6 was released on Tue Dec 06 2016 - jackrabbit-2.13.4 was released on Mon Oct 10 2016 - jackrabbit-2.13.5 was released on Wed Dec 07 2016 - jackrabbit-2.4.6 was released on Mon Sep 19 2016 - jackrabbit-2.6.6 was released on Sat Sep 17 2016 - jackrabbit-2.6.7 was released on Mon Sep 26 2016 - jackrabbit-2.8.3 was released on Thu Sep 15 2016 - vault-3.1.30 was released on Thu Sep 29 2016 - oak-1.0.34 was released on Mon Oct 03 2016 - oak-1.0.35 was released on Mon Nov 14 2016 - oak-1.2.19 was released on Tue Sep 13 2016 - oak-1.2.20 was released on Wed Oct 12 2016 - oak-1.2.21 was released on Tue Nov 15 2016 - oak-1.2.22 was released on Mon Dec 12 2016 - oak-1.4.10 was released on Thu Nov 10 2016 - oak-1.4.11 was released on Mon Dec 12 2016 - oak-1.4.8 was released on Mon Oct 03 2016 - oak-1.4.9 was released on Fri Oct 21 2016 - oak-1.5.10 was released on Tue Sep 13 2016 - oak-1.5.11 was released on Fri Sep 30 2016 - oak-1.5.12 was released on Tue Oct 11 2016 - oak-1.5.13 was released on Tue Nov 08 2016 - oak-1.5.14 was released on Mon Nov 21 2016 - oak-1.5.15 was released on Thu Dec 08 2016 - oak-Segment Tar 0.0.12 was released on Mon Sep 19 2016 - oak-Segment Tar 0.0.14 was released on Mon Oct 10 2016 - oak-Segment Tar 0.0.16 was released on Mon Oct 24 2016 ## JIRA activity: - 562 JIRA tickets created in the last 3 months - 605 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AD: Report from the Apache Karaf Project [Jean-Baptiste Onofré] Apache Karaf provides a very modern and polymorphic container, multi-purpose (microservices, OSGi, etc) powered by OSGi. Community ========= Last committer addition: October 31, 2016 Last PMC addition: August 22, 2016 Grzegorz Grzybek and Luca Burgazzoli were added as committers on October 31, 2016. Messages on the dev mailing list during last 3 months: 341 (184 subscribers) Messages on the user mailing list during last 3 months: 707 (367 subscribers) Some talks related to Apache Karaf have been given during ApacheCon Europe. Development =========== The following new releases have been voted: - 4.0.7 was released on Sun Sep 25 2016 - cellar 4.0.3 was released on Mon Oct 31 2016 - 185 JIRA tickets created in the last 3 months - 174 JIRA tickets closed/resolved in the last 3 months Issues for board consideration ============================== None so far. ----------------------------------------- Attachment AE: Report from the Apache Labs Project [Danny Angus] ## Description: Apache Labs exists to incubate small and emerging projects from ASF committers. ## Issues: There are no issues requiring board attention at this time. ## Activity: There has been no activity of any kind in the past three months. ## Health report: The project remains healthy but there was an ongoing lack of all activity in Labs in the reporting period. This lack of activity does not imply a lack of health, the PMC and committers include experienced and active members and committers. I note from MT's comments on our last report that "if the lack of activity continues for another reporting period or two then the attic starts to look more likely." I would be interested to hear other board members' opinions on attic vs status quo vs pivot, given that this was a strategic initiative and is an outlier in its nature and purpose. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jan Iversen on Tue Feb 04 2014 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Jan Iversen at Thu Feb 27 2014 ## Releases: - this project does not produce releases ## Mailing list activity: - labs@labs.apache.org: - 177 subscribers (up 3 in the last 3 months): - 0 emails sent to list (0 in previous quarter) ----------------------------------------- Attachment AF: Report from the Apache Lucene Project [Tommaso Teofili] ## Description: - Lucene Core is a search-engine toolkit - Solr is a search server built on top of Lucene Core ## Issues: - There are no new issues requiring board attention at this time ## Activity: - The community is actively working on both Lucene and Solr, with daily commits, towards 6.4.0 (and 7) releases - We pushed out a few releases since last report (see below) - We got reported three security vulnerabilities which we are (slowly) addressing - We included a large contribution which required inspecting legal concerns (Solr Learn to Rank) - A huge Jira maintenance effort has been put in place by some committers in order to close lots of old issues - Discussions are generally flowing in a good shape, except one email thread (subj: "Future of FieldCache in Solr") that got a bit too hot but luckily it didn't "diverge" - A number of meetups / conferences on Lucene / Solr took place around the world: - Lucene4IR in Glasgow, Sept 8-9th - London Lucene Hackday, Oct 7th - NYC Apache Lucene Solr Meetup Oct 10th - Lucene/Solr Revolution in Boston, October 11-14th ## PMC changes: - Currently 39 PMC members. - Varun Thacker was added to the PMC on Mon Dec 12 2016 ## Committer base changes: - Currently 64 committers. - Ishan Chattopadhyaya was added as a committer on Tue Nov 29 2016 ## Releases: - Lucene 6.2.1 released on Sep 20, 2016 - Solr 6.2.1 released on Sep 20, 2016 - Lucene 6.3.0 released on Nov 8th, 2016 - Solr 6.3.0 released on Nov 8th, 2016 - Solr RefereGuide 6.3.0 released on Nov 16th, 2016 ----------------------------------------- Attachment AG: Report from the Apache Lucene.Net Project [Prescott Nasser] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == * Currently have 4.8 in pre-release (http://myget.org/gallery/lucene-net, downloads: 25398) * Strong community involvement to get this over the line == Releases == * Last Release 3.0.3 - Oct 2012 == Statistics == * Last PMC Member Added, Paul Irwin, October 2013 * Last committer added Sept 2016, Shad Storhaug Nuget package downloads: * Lucene.Net 3.0.3: 417,307 (up from 357,422) * Lucene.Net.Contrib 3.0.3: 109,915 (up from 95,087) * Lucene.Net Contrib Spatial: 11,269 (up from 10,574) * Lucene.Net Contrib Spatial.NTS: 2,079 (up from 1,999) ----------------------------------------- Attachment AH: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source enterprise automation software project. ## Issues: There are no issues requiring board attention at this time. ## Activity: - The latest release 16.11.01, published on November, is an important milestone for the project: apart from a large number of features, enhancements and fixes, the release changes the build system (from Ant to Gradle), improves the dependency management configuration, provides some tools to manage integration and extensions; the community has dedicated this important release to the memory of OFBiz Committer and ex PMC member Adrian Crum, who passed away on 1st January 2016 and his loss is strongly felt. - The release has also resolved two security vulnerabilities, CVE-2016-6800 and CVE-2016-4462, that have been announced after the release, completing the security handling workflow; there are no outstanding security vulnerability reports at the moment. - Several new features, improvements and bug fixes have been contributed and integrated into the official code base. - Interesting discussions about possible framework and user interface refactoring are ongoing in the dev list. - ApacheCon EU 2016 @ Seville: the event was a success for the OFBiz project with 5 OFBiz presentations and a series of informal meetups. - The activity in the official blog and Twitter accounts is steady with a monthly blog post and frequent tweets. - The PMC is working at improving the workflow to manage and implement trademark protection (a special thanks to Shane who is providing great advices); in parallel, the PMC is addressing specific trademark violations with good results: please refer to [*] for details. - The PMC is defining a policy to govern and limit marketing messages operated by third parties on the OFBiz lists. ## Health report: This month the OFBiz project is celebrating 10 years at ASF! And after 10 years the project is still in an healthy and active phase characterized by steady traffic in the mailing lists, good and friendly communication and collaboration, several contributions for bug fixes and enhancements committed by different committers and big ideas for the future. ## PMC changes: - Currently 18 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Brohl on Fri Sep 02 2016 ## Committer base changes: - Currently 40 committers. - No new committers added in the last 3 months - Last committer addition was Gregory Draperi at Mon Mar 07 2016 ## Releases: - 16.11.01 was released on Sun Nov 27 2016 ## Mailing list activity: - dev@ofbiz.apache.org: - 571 subscribers (up 21 in the last 3 months): - 1001 emails sent to list (7017 in previous quarter) - notifications@ofbiz.apache.org: - 82 subscribers (up 22 in the last 3 months): - 5210 emails sent to list (1602 in previous quarter) - user@ofbiz.apache.org: - 940 subscribers (up 22 in the last 3 months): - 205 emails sent to list (463 in previous quarter) ## JIRA activity: - 911 JIRA tickets created in the last 3 months - 1002 JIRA tickets closed/resolved in the last 3 months ## References [*] https://svn.apache.org/repos/private/pmc/ofbiz/trademarks.txt ----------------------------------------- Attachment AI: Report from the Apache Olingo Project [Christian Amend] ## Description: Apache Olingo is a Java and JavaScript library that implements the Open Data Protocol (OData). Apache Olingo serves client and server aspects of OData. It currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC. ## Olingo Status Currently Olingo has no issues that would require board attention. The 4.3.0 release was provided to the community on September 19th, 2016. The next release is scheduled at the end of December. Considering that there are no major new features which were developed with the new version a release is unlikely. There have been bug fixes in the Olingo V2 code line. But since no community member asked for a new patch release we have not yet provided one. Traffic on the mailing list and our JIRA has gone down compared to the last report. Same goes for the number of contributions. This does not worry me as the V2 and V4 core libraries are nearly feature complete. Once the new OData 4.01 specification is published at Oasis these numbers should grow again. All in all I still think Olingo is a healthy Apache project. We don`t have as much traffic as other projects but it is mostly constant. In the last report I mentioned a large contribution from an individual to the Olingo V4 code line. It was a JPA extension to the Olingo core libraries. After discussing this contribution on the mailing list it was decided that it will not be accepted. Main reason was the fact that some PMC members thought that the new extension could not be handled with the current Olingo community members. They felt that even if we gave the contributor committing rights the main burden would be on this one committer. If he left the community there would be no other that would take over. As a compromise the contributor was encouraged to create a GitHub repository for the extension first. Once the code has reached a certain maturity and attracted a larger number of committers they could come back and contribute to Olingo again. Initial discussion: http://mail-archives.apache.org/mod_mbox/olingo-dev/201609.mbox/%3CetPan.57e60779.412690d1.c4bd%40apache.org%3E Follow up: http://mail-archives.apache.org/mod_mbox/olingo-dev/201610.mbox/%3C2266c519a9fd470c9a3343e0a07d9a76%40derote13de02.global.corp.sap%3E Questions from last report: idf: Do you have any guess as to why those people filing a JIRA issue tend to not come back? OData as such is not a hype and does not have as much users as other open source projects. So my personal guess is that once their specific issue has been addressed they are satisfied. Thus they don`t have to contribute further and leave. Most of the users that open multiple JIRA issues don`t attach patches. Of course pointing the community towards issues with their code is also an important part in a community. But it does not help speeding up the fixing process. Another reason is the complexity of the protocol. Many don`t want to dive into protocol specifics but rather only use it with as much abstraction as possible to not worry about the details. When providing a fix one must make sure to be specification compliant which can make even simple fixes challenging. === Statistics === ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ramesh Reddy on Thu Oct 08 2015 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Christian Holzer at Thu Feb 26 2015 ## Releases: - (Java) V4 4.3.0 was released on Mon Sep 19 2016 ## Mailing list activity: - dev@olingo.apache.org: - 83 subscribers (up 4 in the last 3 months): - 309 emails sent to list (414 in previous quarter) - user@olingo.apache.org: - 162 subscribers (up 8 in the last 3 months): - 59 emails sent to list (90 in previous quarter) ## JIRA activity: - 37 JIRA tickets created in the last 3 months - 30 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache OODT Project [Tom Barber] DESCRIPTION Apache OODT is a software framework as well as an architectural style for the rapid construction of scientific data systems. It provides components for data capture, curation, metadata extraction, workflow management, resource management, and data processing. RELEASES/DEVELOPMENT - Last release was 1.0 on Wed Jun 29 2016 We resolved 0 issues for this release. We finally reached a point in the platform lifecycle which made sense to release Apache OODT as 1.0. This was done both to signify the stability of what we had but also allow us to prepare for major changes coming in the next major release cycle to modernise the platform and extend what was already in place. These changes will be API breaking and as such we wanted to signify this in the release versioning. It was asked in last months meeting to keep the board updated with regards to driving adoption. To this end this month we have switched our website from Apache CMS to gitsubpub and Jekyll to ease the updating process. Along the website has tried to reduce the science centric focus and add more business use case type content. This will be an ongoing process as we get time to add more content to aid potential users in understanding how OODT can help them. Tom also gave an OODT related talk at Apachecon Europe that had decent attendance and further feedback afterwards. Having spoken to a number of PMC members we feel that reducing the size of the code base and integrating with a number of the other ASF data projects will help bring people on board and as such the roadmap for OODT 2.0 has this aim in mind. COMMUNITY Latest committers and PMC members: - Radu Maonle(radumanole) on 11th Oct 2015 as committer and PMC member Last committer and PMC member added on 6th October 2015. Mailing list activity has been pretty much static in terms of period on period volume and Jira has been quiet. ISSUES There are no issues requiring board attention at this time. HEALTH REPORT The project activity is pretty quiet, but there are still on going efforts in place to help drive wider adoption. ----------------------------------------- Attachment AK: Report from the Apache Open Climate Workbench Project [Michael James Joyce] Apache Open Climate Workbench is a tool for scalable comparisons of remote sensing observations to climate model outputs. Development on the project has been great since the last report. September and especially November have seen very high contributions from a number of our regular contributors. We've also seen occasional interest from external contributors expressing interest in participating, but nothing has come from that yet. The project released v 1.1.0 late in July which provides a number of key features required of the tool in addition to many quality-of-life improvements. The team is currently discussing a 1.2.0 release and features / improvements we would like to see make their way in first. We expect to see a new release in the next reporting cycle. Issues for the Board: None When was the last committer or PMC member elected: - Omkar Reddy - 20 January 2016 - Ibrahim Jarif - 26 April 2016 When was the last release: - 1.0.0 - 22 September 2015 - 1.1.0 - 27 July 2016 ----------------------------------------- Attachment AL: Report from the Apache OpenNLP Project [Jörn Kottmann] The Apache OpenNLP library is a machine learning based toolkit for the processing of natural language text. It supports the most common NLP tasks, such as tokenization, sentence segmentation, part-of-speech tagging, named entity extraction, chunking, parsing, and coreference resolution. These tasks are usually required to build more advanced text processing services. Development ------------------ The development team stayed active over the last three month and the activity in commits increased slightly while working on the next release. Community --------------- The community stayed active with the usual amount of traffic on the user mailing list and contributed a couple of patches to fix bugs and to improve our code. Rodrigo Agerri was added to the PMC on Jul 09 2015 Anastasija Mensikova was added as a committer on Jul 20 2016. Releases ------------ The last release OpenNLP 1.6.0 was released on Jul 09 2015. Issues -------- There are no board-level issues at this time. ----------------------------------------- Attachment AM: Report from the Apache OpenWebBeans Project [Mark Struberg] ## Description: Apache OpenWebBeans is an ALv2-licensed implementations of the "Contexts and Dependency Injection for the Java EE platform" specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1 and CDI-1.2 (MR) specifications (JSR-346). ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity is ok. We started with a new subproject called Meecrowave. It is a mircroprofile server consisting of Tomcat9 + OpenWebBeans + CXF + Johnzon, all in 9MB. https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/ We decided to create an own subproject since we rely on other projects and thus we will see separate release cycles as from OWB core. We will also see a CDI-2.0 implementation effort soon as the spec (JSR-365, available under ALv2) is just about to get finished. ## Health report: Nothing special to report. We did not yet create separate tickets for Meecrowave as we did not yet have any release. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Louis Monteiro on Wed May 28 2014 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Reinhard Sandtner at Fri Sep 26 2014 ## Releases: - Last release was 1.7.0 on Sun Sep 04 2016 ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AN: Report from the Apache Pig Project [Daniel Dai] ## Description: Apache Pig is a platform for analyzing large data sets on Hadoop. It provides a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Pig on Spark development is still under way in the spark branch, merge to trunk is near and target remain for 0.17.0 - Preparing Pig 0.16.1 release ## Health report: - Project activity in the community - mails, commits, jiras, etc is good and is at the same levels as previous few quarters. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Koji Noguchi on Thu Aug 04 2016 ## Committer base changes: - Currently 28 committers. - Liyun Zhang was added on Thu Dec 15 2016 ## Releases: - Last release was 0.16.0 on Tue Jun 07 2016 ## Mailing list activity: - dev@pig.apache.org: - 403 subscribers (up 2 in the last 3 months): - 1122 emails sent to list (876 in previous quarter) - user@pig.apache.org: - 1157 subscribers (down -10 in the last 3 months): - 36 emails sent to list (41 in previous quarter) ## JIRA activity: - 44 JIRA tickets created in the last 3 months - 51 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: Report from the Apache Pivot Project [Roger Whitcomb] Description: Apache Pivot is an open-source platform for building installable Internet applications (IIAs). It combines the enhanced productivity and usability features of a modern user interface toolkit with the robustness of the Java platform. Issues: There are no board-level issues at this time. Activity: Activity has been way down this quarter (see stats below). The long- delayed next release did not happen this past quarter, but we are ready to do it when the chair can get some cycles. Health report: The ongoing issue remains lack of activity on the project. Active development was being done by myself, but my employment has changed technologies, and is no longer interested in Pivot, so it is hard to find the time to do much more. I will push through the 2.0.5 release in the next few months and we will see if that helps any. There are also many changes in "trunk" that could almost warrant a 2.1 release (but there is no "killer" feature yet), but that might produce an uptick as well. When I get time, I will try to reach out some more using any of the available means to try to stimulate some interest. PMC Changes: - Currently 4 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Niclas Hedhman on Wed Jan 13 2016 Committer base changes: - Currently 5 active (that is, not emeritus) committers. - No new changes to the committer base since last report. - No new committers added in the last 3 months. - Last committer addition was more than 2 years ago. Releases: - Last release was 2.0.4 on Mon May 19 2014 Mailing list activity: As you can see from the following statistics there was virtually no activity this last quarter. - dev@pivot.apache.org: - 62 subscribers (no change) - 7 emails sent to list (23 in previous quarter) - user@pivot.apache.org: - 175 subscribers (no change) - 2 emails sent to list (11 in previous quarter) ----------------------------------------- Attachment AP: Report from the Apache Portable Runtime (APR) Project [Nick Kew] ## Short version of report: No releases, modest activity. Some growth of the community, and a new PMC chair. ## Description: The Apache Portable Runtime (APR) project creates and maintains software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. The sub-projects which are released somewhat regularly are APR and APR-util. In addition, the APR-iconv sub-project is commonly used but has not had a release since 2007. ## Issues: - The board may be interested in the FOSSA security report, commissioned by the EU commission into Apache HTTPD core and extending into APR. This was handled by Dirk van Gulik for the ASF. Summary details in Dirk's email at http://mail-archives.apache.org/mod_mbox/apr-dev/201611.mbox/%3C9643AB52-078F-4779-B80C-9CE39A2121AF%40webweaving.org%3E - No issues requiring board attention at this time. ## Activity: - Commit activity remains low. - Mailing list activity remains low. - The number of open issues on Bugzilla is stable. ## Health report: - This is a mature project, and most of its development activity is driven by the needs of established users. In this quarter, a new apr_redis module has been introduced. - There is little impetus to develop the software further to meet the needs of potential new users. - Since a few patches have been languishing committed but unreleased for some time, we have identified a need for a new release and anticipate one within the next quarter. ## Personnel changes: - Jeff Trawick having indicated his desire to step down from the role of PMC chair, Nick Kew has stepped into that role. - Currently 67 committers and 40 PMC members. - Christophe Jaillet was added to the PMC in October. - Ivan Zhakov joined the team as committer in October. ## Releases: - No releases in this quarter - APR 1.5.2, released April 29, 2015 - APR-util 1.5.4, released September 22, 2014 - APR-iconv 1.2.1, released November 26, 2007 ## Mailing list activity: Traffic has been predominantly of a routine nature. The increase on last quarter is partially down to discussion of the new apr_redis. - dev@apr.apache.org: - 349 subscribers (down -9 in the last 3 months): - 66 emails sent to list (43 in previous quarter) - bugs@apr.apache.org: - 21 subscribers (down -1 in the last 3 months): - 39 emails sent to list (62 in previous quarter) ## Bugzilla Statistics: - 2 Bugzilla tickets created in the last 3 months - 2 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment AQ: Report from the Apache Portals Project [David Sean Taylor] ## Description: Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Activity: Apache Portals released 0 releases since the last report. Apache Portals Pluto team has completed implementing Pluto 3.0 to support to the Portlet Spec 3.0 Apache Portals Pluto team has completed implementing the TCK (Test Compatibility Kit) for Portlet Spec 3.0 The Portlet API 3.0 specification has been approved by the JCP (JSR 362 Public Review Ballot), see: https://www.jcp.org/en/jsr/results?id=5896 Apache Portals Pluto team is aiming to release Pluto 3.0 in December 2016. ## Mailing list activity: A little more activity with release preparation. ## Issues: We have no board-level issues at this time. ## PMC/Committership changes: none Last Added PMC Members: 4 May 2015 - Randy Watler Last Added Committers: 05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014 Neil Griffin ## Releases: Jetspeed 2.3.1 on May 9, 2016 ----------------------------------------- Attachment AR: Report from the Apache Sentry Project [Sravya Tirukkovalur] ## Description: Apache Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop Cluster. ## Issues: None ## Activity: Software: - Improvements related to consistency and transactions - Sentry web page and metrics related improvements - Scale test tool - Other bug fixes Community: - Presented Sentry High availability at ApacheCon, Spain ## Health report: - Usual activity on mailing lists but slower activity on jiras. ## PMC changes: - Currently 33 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Colm O hEigeartaigh on Tue Jun 07 2016 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Ashish Singh at Sun Sep 04 2016 ## Releases: - Last release was 1.7.0 on Tue Jun 14 2016 ## Mailing list activity: Mailing list activity is as usual. - dev@sentry.apache.org: - 87 subscribers (up 2 in the last 3 months): - 325 emails sent to list (389 in previous quarter) - issues@sentry.apache.org: - 17 subscribers (up 1 in the last 3 months): - 1090 emails sent to list (1550 in previous quarter) - security@sentry.apache.org: - 14 subscribers (up 1 in the last 3 months) ## JIRA activity: Jira activity is slower than previous quarter - 98 JIRA tickets created in the last 3 months - 49 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AS: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF and Karaf to provide a complete, enterprise-ready ESB powered by OSGi. ## Issues There are no outstanding issues requiring board attention. ## Activity The project focus of Apache ServiceMix is the assembly of the integration container, the actual functionality is being maintained in related projects like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ. During the las period we have provided the users with new maintenance release 6.0.5 and new updates 5.6.2 and 6.1.3 from the development branches. We have decided to transit the 5.5.x branch into EOL, as there is no more development on this branch nor on the proper versions of the related projects. We have also released 2 new OSGi bundle sets. We have also released the last preview release of ServiceMix 7 (7.0.0.M3). We plan to release the final version at the end of this year. In the next period we plan to focus on ServiceMix 7, but we also expect to provide the maintenance releases for ServiceMix 5 and 6, as long new dependencies will be available. ## Health report Activity on the mailing lists and in JIRA is on the same level like in the last period. We had some new contributions. We have lost a lot of our momentum now that major parts of the functionality are being maintained in related projects like Apache Karaf and Apache Camel. ## PMC changes - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Krzysztof Sobkowiak on Sat Jul 05 2014 ## Committer base changes - Currently 50 committers. - No new committers added in the last 3 months - Last committer addition was Andrea Cosentino at Sun Mar 13 2016 ## Releases - Apache ServiceMix Bundles 2016.09 on September 29 2016 - Apache ServiceMix Bundles 2016.10 on November 07 2016 - Apache ServiceMix 5.6.2 on November 23 2016 - Apache ServiceMix 6.0.5 on November 23 2016 - Apache ServiceMix 6.1.3 on November 23 2016 - Apache ServiceMix 7.0.0.M3 on December 03 2016 ## JIRA activity - 78 JIRA tickets created in the last 3 months - 77 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache Shiro Project [Les Hazlewood] Apache Shiro is a powerful and flexible open-source application security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. We have no issues that require Board assistance at this time. Releases: - 1.4.0-RC2 was released on Wed Nov 09 2016 Community & Project: - Mailing list traffic has remained the same. - Most of the 2.x changes have been included in the 1.4.0-RC2 release. 1.4.0 is now on master. Development will continue on master. - Feature development is planned to continue against master. - The 1.4.0 Release has been a step toward modernizing Shiro as well as retain backwards compatibility. Last committer voted in: Andreas Kohn on 15 Jul 2016 Last PMC Member voted in: Andreas Kohn on 26 Jul 2016 ----------------------------------------- Attachment AU: Report from the Apache Sling Project [Carsten Ziegeler] Apache Sling is an OSGI-based scriptable web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. There are no issues which require board attention at the moment. Community Good activity level overall, contributions from different people continue. One new committer (Georg Henzler) (last committers change was in September 2016 with one new committer elected), one new PMC member (Konrad Windszus) (last PMC change was in October 2016 with one new PMC members elected). Releases Apache Sling OSGi Mock 2.2.0, OSGi Mock 1.9.0, Sling Mock 2.2.0, Sling Mock 1.9.0 (December 8th, 2016) Apache Sling API 2.16.0, Apache Sling Resource Resolver 1.5.6, Apache Sling Servlets Resolver 2.4.8, Apache Sling JCR Resource 2.8.4 (December 6th, 2016) Apache Sling Models bnd Plugin 1.0.0, Apache Sling Commons ClassLoader 1.3.6 (November 24th, 2016) Apache Sling JCR Resource 2.8.2, Security 1.1.2, Models Implementation 1.3.4 and Models Jackson Exporter 1.0.4 (November 22th, 2016) Apache Sling Resource Resolver 1.5.4, Apache Sling Discovery Base 1.1.6, Apache Sling Discovery Commons 1.0.18, Apache Sling Discovery Impl 1.2.10 and Apache Sling Discovery Oak 1.2.16 (November 21st, 2016) Apache Sling Auth Core 1.3.22 (November 15th, 2016) Apache Sling JCR Base 2.4.2 (November 14th, 2016) Apache Sling Provisioning Model 1.7.0 and Apache Sling Slingstart Maven Plugin 1.6.0 (November 13th, 2016) Apache Sling JCR Repoinit 1.1.0 and Apache Sling Repoinit Parser 1.1.0 (November 12th, 2016) Apache Sling Slingstart Maven Plugin 1.5.0 (November 11th, 2016) Apache Sling Installer Core 3.8.0, Apache Sling Context-Aware Configuration SPI 1.1.0 and Apache Sling Context-Aware Configuration Impl 1.1.0 (November 10th, 2016) Apache Sling Resource Resolver 1.5.2, Apache Sling Provisioning Model 1.6.0, and Apache Sling HTL Maven Plugin 1.0.2 (November 8th, 2016) Apache Sling Commons Mime 2.1.10 (November 7th, 2016) Apache Sling Web Console Security Provider 1.2.0 (November 6th, 2016) Apache Sling Models API 1.3.0, Models Implementation 1.3.0 and Models Jackson Exporter 1.0.0 (November 3th, 2016) Apache Sling Launchpad Base 2.6.14, Apache Sling Provisioning Model 1.5.0, Apache Sling XSS Protection API 1.0.16 (October 31st, 2016) Apache Sling Commons Scheduler 2.5.2 (October 27th, 2016) Apache Sling API 2.15.0, Apache Sling Resource Resolver 1.5.0, Apache Sling Installer Core 3.7.0 (October 25st, 2016) Apache Sling Scripting HTL Engine 1.0.26, Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0, Apache Sling DataSource Provider 1.0.2 and Apache Sling Log Tracer 1.0.2 (October 24th, 2016) Apache Sling Servlets Resolver 2.4.6 (October 22nd, 2016) Apache Sling Scripting JSP 2.2.0, Apache Sling Engine 2.6.6, Apache Sling Scripting Java 2.1.0, Apache Sling Scripting HTL JS Use Provider 1.0.16 (October 20th, 2016) Apache Sling Context-Aware Configuration API 1.0.0, SPI 1.0.0, Impl 1.0.0, bnd Plugin 1.0.0, Resource Builder 1.0.2, Testing Hamcrest 1.0.0 (October 18th, 2016) Apache Sling Scripting Core 2.0.40, Apache Sling Scripting HTL Java Compiler 1.0.4, Apache Sling Scripting HTL Engine 1.0.24 (October 17th, 2016) Apache Sling Launchpad Base 2.6.12 (October 16th, 2016) Apache Sling Event 3.4.0, Apache Sling Distributed Eventing 1.1.0, and Apache Sling Rewriter 1.2.0 (October 15th, 2016) Apache Sling Pipes 0.0.10 (October 14th, 2016) Apache Sling Scripting HTL Compiler 1.0.2, Apache Sling Scripting HTL Java Compiler 1.0.2, Apache Sling Scripting HTL Engine 1.0.22, Apache Sling Scripting HTL JS Use Provider 1.0.14, Apache Sling Scripting HTL Models Use Provider 1.0.4 (October 13th, 2016) Apache Sling Testing Sling Mock 2.1.2 (October 10th, 2016) Apache Sling i18n 2.5.4 (October 8th, 2016) Apache Sling Oak Restrictions 1.0.0 (October 3rd, 2016) Apache Sling Discovery Commons 1.0.16 and Discovery Oak 1.2.14 (Sep 29th, 2016) Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0, Apache Sling Testing Rules 1.0.0 (Sep 16th, 2016) Apache Sling Auth Core 1.3.20, JUnit Core 1.0.18, JUnit Tests Teleporter 1.0.8, Testing Logging Mock 2.0.0, JCR Mock 1.1.16, OSGi Mock 1.8.0, OSGi Mock 2.1.0, Sling Mock 1.8.0, Sling Mock 2.1.0, Sling Mock Oak 2.0.2, Resource Builder 1.0.0, Servlet Helpers 1.1.0 (Sep 19th, 2016) Apache Sling Scripting HTL Compiler 1.0.0, Apache Sling Scripting HTL Java Compiler 1.0.0, Apache Sling Scripting HTL Engine 1.0.20, Apache Sling Scripting HTL JS Use Provider 1.0.12, Apache Sling Scripting HTL Models Use Provider 1.0.2, Apache Sling Scripting HTL REPL 1.0.4, Apache Sling HTL Maven Plugin 1.0.0 (Sep 8th, 2016) Documentation and infrastructure Nothing to report Project Branding is tracked in SLING-2696. ----------------------------------------- Attachment AV: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to board for December 2016 SpamAssassin is a mail filter to identify spam. The project provides a framework/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Health report: The status of the project is basically unchanged from the last report, a mature project that is not in rapid development. The users mailing list is active with user level questions and responses from people with expertise in SpamAssassin. Traffic on the developers mailing list is much quieter, showing mostly the results of our automated processes and regular bug fix activity by developers on our Bugzilla issues. Much of the ongoing developer level activity is around the maintenance of the rule-generation facility that runs as a service for the users of SpamAssassin. Issues: The problems with the mailing list mentioned last quarter seem to have been successfully resolved by the banning of one person from the list. There are no new issues to mention. Releases: Last quarter’s report stated the intention to produce a 3.4.2 release, as did the previous quarter’s report. We still have not selected a release manager and triggered the release process but have closed a number of our Bugzilla issues that would go into a 3.4.2 release. It would be a good idea to get the release process started in January. Committer/PMC changes: John Hardin (jhardin) joined the PMC two months ago. ----------------------------------------- Attachment AW: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment AX: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: - Apache Storm is a distributed real-time computation system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Progress continues toward making a 1.1.0 release. - Migration of Clojure code to Java is nearing completion. - A significant amount of progress has been made on Storm's SQL interface that leverages Apache Calcite. - An effort is underway to implement an improved API for collecting and reporting system level and user-defined metricts. - An effort is underway to implement an Apache Beam runner on top of Storm. ## Health report: - Overall the project continues to be healthy and we are seeing new faces show up and contribute. ## PMC changes: - Currently 32 PMC members. - Xin Wang was added to the PMC on Mon Nov 28 2016 ## Committer base changes: - Currently 33 committers. - Xin Wang was added as a committer on Tue Nov 29 2016 ## Releases: - Last release was 0.10.2 on Mon Sep 12 2016 ## Mailing list activity: - There has been a significant drop in the number of emails to the dev@ list. This can be attributed to moving JIRA notifications to the issues@ list and modifying GitHub integration (GitHub activity now posts to the JIRA work log instead of comments to reduce the number of duplicate emails). - dev@storm.apache.org: - 548 subscribers (up 6 in the last 3 months): - 1840 emails sent to list (4816 in previous quarter) - issues@storm.apache.org: - 12 subscribers (up 1 in the last 3 months): - 626 emails sent to list (0 in previous quarter) - user@storm.apache.org: - 1417 subscribers (up 4 in the last 3 months): - 594 emails sent to list (664 in previous quarter) ## JIRA activity: - 148 JIRA tickets created in the last 3 months - 103 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AY: Report from the Apache Synapse Project [Isuru Udana] 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) We have completed most of the development work related to the 3.0 release. Since we are doing a major revamp of the http protocol handling transport, this release requires a significant amount of testing. Several committers and no committers are working on testing the release and hopefully we should be able to get the release out by end of the year. 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 ============ None identified. ----------------------------------------- Attachment AZ: Report from the Apache Tajo Project [Hyunsik Choi] ----------------------------------------- Attachment BA: Report from the Apache Tiles Project [Mick Semb Wever] ## Description: Apache Tiles is a free open-sourced templating framework for Java applications. Based upon the Composite pattern it is built to simplify the development of user interfaces. ## Activity: Apache Tiles remains a stable but low traffic project. This quarter there was very little public activity. A couple of small fixes. No releases were cut. The majority of activity still happens on non-apache sites like the StackExchange forums. StackExchange sees a few questions and answers each day or two. Efforts to subscribe these posts back to the user mailing list should be re-investigated. ## Health report: There are currently two responsive PMC, other PMC help out with votes when needed. Everyone is aware of the how little momentum the project has, but it does not feel abandoned by members, nor not in use by the public. ## Issues Further effort is still required to increase health to the project. Previous board report received feedback on what such effort might be. This can be from including the StackExchange traffic, following up on some of the development ideas, to publicity and engagement with other communities that have more momentum in the UI space. ## Memorial On September 30th our previous chair Greg Reddin passed away. A number of members stepped forward to contribute their praise and condolences. What was written up was shared with Greg's wife. http://www.apache.org/memorials/greg_reddin.html ----------------------------------------- Attachment BB: Report from the Apache Tomcat Project [Mladen Turk] ## Description: A Java Servlet, JavaServer Pages, Java WebSocket and Java Unified Expression language specifications implementation. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Continued healthy activity across multiple components and responsiveness on both dev and user lists. ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Felix Schumacher on Mon Oct 26 2015 ## Committer base changes: - Currently 42 committers. - New commmitters: - Coty Sutherland was added as a committer on Fri Aug 26 2016 - Huxing Zhang was added as a committer on Fri Aug 26 2016 ## Releases: - Apache Tomcat 6.0.47 was released on Oct 16 2016 - Apache Tomcat 6.0.48 was released on Nov 15 2016 - Apache Tomcat 7.0.72 was released on Sep 19 2016 - Apache Tomcat 7.0.73 was released on Nov 14 2016 - Apache Tomcat 8.0.38 was released on Oct 10 2016 - Apache Tomcat 8.0.39 was released on Nov 14 2016 - Apache Tomcat 8.5.6 was released on Oct 10 2016 - Apache Tomcat 8.5.8 was released on Nov 11 2016 - Apache Tomcat 8.5.9 was released on Dec 08 2016 - Apache Tomcat 9.0.0.M11 was released on Oct 10 2016 - Apache Tomcat 9.0.0.M13 was released on Nov 11 2016 - Apache Tomcat 9.0.0.M15 was released on Dec 08 2016 - Apache Tomcat Native 1.2.10 was released on Oct 05 2016 - Apache Tomcat Connectors 1.2.42 was released on Oct 05 2016 ## Trademark: Since our last report the Tomcat PMC dealt with the following trademark issues: - A minor issue with a github project that was renamed at our request from "Tomcat XXX" to "XXX for Tomcat". - Some historical documentation for a product previously renamed from "Tomcat XXX" to "XXX for Tomcat" appeared in our regular search using the old name. The historical documentation was updated to use the correct form. In both cases speedy resolution was aided by the fact that Tomcat PMC members were involved in - or had close ties to - the projects concerned. The Tomcat PMC has decided not to pursue further a trademark issue outstanding since 2008 since the project has been dormant for many years. There are currently no outstanding trademark issues that the Tomcat PMC is working on. Detailed history is available at: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt ## Security: - Detailed status: http://tomcat.apache.org/security.html There were some low impact vulnerabilities reported and fixed in Tomcat (6.0.47, 7.0.72): - Low: Timing Attack CVE-2016-0762 The Realm Implementations used different amount of time for authentication requests with or without a password - Low: Security Manager Bypass CVE-2016-5018 The SecurityManager could be bypassed - Low: System Property Disclosure CVE-2016-6794 System Properties could be read, that should have been protected by a SecurityManager - Low: Security Manager Bypass CVE-2016-6796 A configured SecurityManager could be bypassed - Low: Unrestricted Access to Global Resources CVE-2016-6797 Webapps could access global JNDI ressources even when they were not explicitly configured for the Webapp There were some important vulnerabilities reported and fixed in Tomcat (6.0.48, 7.0.73, 8.0.39, 8.5.8, 8.5.9, 9.0.0.M13): - Important: Information Disclosure CVE-2016-6816 HTTP request line was not parsed correctly - Important: Denial of Service CVE-2016-6817 The HTTP/2 header parser could be tricked into an infinite loop - Important: Remote Code Execution CVE-2016-8735 The JmxRemoteLifecycleListener was vulnerable to a remote execution attack - Important: Information Disclosure CVE-2016-8745 When using NIO and sendfile requests could be shared between to concurrent threads, which led to possible information leakage ----------------------------------------- Attachment BC: Report from the Apache TomEE Project [David Blevins] ----------------------------------------- Attachment BD: Report from the Apache Twill Project [Terence Yim] Apache Twill is an abstraction over Apache Hadoop YARN to reduce the complexity of developing distributed applications. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Add a new committer, Ali Anwar (anwar@) ## Health report: - Addition of new committer and have new contributors sending patches - Made two releases since Sep 2016 ## PMC changes: - Currently 6 PMC members - Last PMC addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 7 committers and 23 contributors - One new committer added in the last 3 months - Two new contributor added in the last 3 months - Last committer addition was Ali Anwar on Oct 7, 2016 - Last contributor addition was Chengfeng Mao on November 18, 2016 ## Releases: - Last release was release 0.9.0 on December 16, 2016 ## Mailing list activity: - dev@twill.apache.org: - 67 subscribers - 424 emails sent to the list in past three months (297 in last report) - commits@twill.apache.org: - 17 subscribers - 99 emails sent to the list in past three months (68 in last report) ## JIRA activity: - 2 new JIRA tickets created in the last month - 1 JIRA tickets resolved in the last month ----------------------------------------- Attachment BE: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for December 2016. Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. Dates: 28 Sep 2016 (new) last release - Apache UIMA Ruta 2.5.0 03 May 2016 (no change) last PMC addition 24 Jul 2015 (no change) last Committer addition Releases: 28 Sep 2016 Apache UIMA Ruta 2.5.0 many upgrades, improvements, fixes Other Activity: At infra's request, fixed a test case running as part of Jenkins build for UIMA-AS that opened an RMI port. We fixed the test harness and configured it to not open this port. Infra chat support was very helpful in getting this resolved. Apache UIMA AS subproject in release vote (pending). Community: The community continues to be moderately active. Issues: No Board level issues at this time. ----------------------------------------- Attachment BF: Report from the Apache VCL Project [Andy Kurth] ## Description: VCL is a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources including virtual machines, bare-metal computers, and resources in other cloud platforms. A self-service web portal is used to request resources and for administration. VCL became a TLP on June 20, 2012. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Upon a review of our documentation, we realized that it needed notable improvement and thought it best to put a fair amount of work into it before getting our next release out. Work is in progress to improve it. - There are a few coding issues that still need to be completed for the next release. We plan to focus on the documentation first, and finish up the coding work afterwards. ## Health report: - Overall, the health of the project is fair. Activity and interest seem to be fairly flat. We're working on aspects such as improving documentation to attempt to make it easier for people to adopt the Apache VCL software and also to contribute to the project. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Aaron Coburn on Tue Jun 19 2012 ## Committer base changes: - Currently 8 committers. - No new committers added in the last 3 months - Last committer addition was Young Hyun Oh at Sun Dec 08 2013 ## Releases: - Last release was 2.4.2 on Wed Apr 15 2015 ## Mailing list activity: - List activity is fairly steady. There was a coincidental flurry of activity prior to our previous report which made the September report's email numbers a bit higher than normal. - dev@vcl.apache.org: - 131 subscribers (down -2 in the last 3 months): - 69 emails sent to list (195 in previous quarter) - user@vcl.apache.org: - 168 subscribers (down -1 in the last 3 months): - 15 emails sent to list (53 in previous quarter) ## JIRA activity: - 16 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BG: Report from the Apache Wicket Project [Martijn Dashorst] Report from the Apache Wicket project [Martijn Dashorst] Apache Wicket is an open source Java component oriented server-side web application framework. A bit busy quarter, our dev@ traffic roughly doubled compared to our previous quarter (to 426 messages sent). The increased traffic is mostly caused by our actions pre and post ApacheCon and the JSON.org re-categorization. Due to the re-categorization of the JSON.org library to category-X we had to rework our code, while maintaining API compatibility for our releases that follow semantic versioning. The next releases for 6.x, 7.x and 8.x will feature the re-implementation courtesy of Ted Dunning. ApacheCon EU 2016 in Sevilla featured 2 presentations by two committers (Andrea del Bene and Martijn Dashorst). The turn up was a bit disappointing, but having Andrea and Martijn meet in real life was good. Also the conference enabled some cross project collaboration between Martijn and Directory Fortress. During ApacheCon Martijn and Andrea worked on the documentation of Wicket, converting from the obsolete gdocs format to Asciidoctor. The 191 documents and 10,000 line reference is converted using scripts crafted by high school student Thijs Beltman in the summer of 2015. Documentation for 7.x and 8.x has been converted, 6.x will follow soon. ## Noteworthy items: - Currently 30/29 Committers/PMC members. - Last committer/PMC addition was François Meillet on Mon Jun 29 2015 - Work on Wicket 8 is in progress, we released a milestone release (8.0-M2) - There are no issues requiring board attention at this time ## Releases this quarter We have issued the following releases: 8.0.0-M2, 7.5.0, 6.25.0 and 1.5.17. ## New committers/PMC members We haven't seen many new contributors to the project, we will keep an eye out for new folks to join, but we don't expect a huge influx given the state of server-side Java web frameworks in general. ----------------------------------------- Attachment BH: Report from the Apache Wink Project [Luciano Resende] Apache Wink is a project that enables development and consumption of REST style web services. The core server runtime is based on the JAX-RS (JSR 311) standard. The project also introduces a client runtime which can leverage certain components of the server-side runtime. Apache Wink delivers component technology that can be easily integrated into a variety of environments. There are no issues that require Board attention at the moment. Community: The Wink project is a mature project with a small community which is currently not very active. Although I believe Wink is a mature project with active users. The probe to check how many active PMC members sent to the private PMC list had response from two of the PMC members, with partial support for retirement. https://s.apache.org/pmc-probe-2016 Based on this, I have started a discussion on 'what's next' with the larger wink community: https://s.apache.org/wink-whats-next We have also started discussions on removing the dependency on json.org with a member of the community volunteering to handle the work. After that is completed the community will need to prepare a new release. Releases: * Last release was Apache Wink 1.4.0 which was released on September 15, 2013 Committers or PMC changes: * Voted Gerhard Petracek was added as a Wink committer in August 2013. Trademark/Branding: * No known issues. Legal Issues: * None ----------------------------------------- Attachment BI: Report from the Apache Xerces Project [Michael Glavassevich] # Xerces-J There were only a few commits over the reporting period (to update documentation of the XML Schema 1.1 tests). A Xerces-J committer from long ago recently approached the PMC to have their committer status reinstated. It seems this does not require a new vote, but we are not sure of the next steps and would appreciate advice on what to do here. This particular individual was last active when the ASF was still using CVS and does not have an SVN account. Mailing list traffic has been low; roughly 50+ posts on the j-dev and j-users lists since the beginning of August 2016. No new releases this quarter. The latest release is Xerces-J 2.11.0 (November 30th, 2010). # Xerces-C A vote was recently completed to add a new committer. He has already submitted his CLA and we plan to request a new account for him once the vote result appears in the mailing list archives. Mailing list traffic has been low; roughly 80+ posts on the c-dev and c-users lists since the beginning of August 2016. No new releases this quarter. The latest release is Xerces-C 3.1.4 (June 29th, 2016). # Xerces-P Nothing in particular to report. There was no development activity over the reporting period. # XML Commons No activity over the reporting period. # Committer / PMC Changes The most recent committers were added in February 2015 (Xerces-C) and May 2009 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. One committer has committed changes to SVN since August. # Apache Project Branding Requirements The project logo still needs a "TM" to be added to it. ----------------------------------------- Attachment BJ: Report from the Apache Yetus Project [Sean Busbey] Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ISSUES FOR THE BOARD'S ATTENTION Last report we were asked if we had approached VP Legal about our licensing issue (we had a contribution we had to ultimately reject because of a hard dependency on a GPL project). We never did approach VP Legal because the planned new component was not an internal build tool to our project but something intended to be used by downstream users of our project. While our most visible downstream users are currently other ASF projects, our goal remains the wider public good so the foundation rules around dependency licenses should apply normally. RELEASES None since last report. Last release was version 0.3.0 on May 22nd 2016. The community is currently working through a 0.4.0 release. ACTIVITY Ajay Yadava was added to the PMC during this period (Dec 1st). Andrew Wang and Ajay Yadava were added as committers during this period (Sep 20th). The community had a noticeable plunge in both overall activity and apparent reviewer bandwidth during this report period. This has been most apparent in our protracted effort to complete the 0.4.0 release. The PMC has previously discussed our need to accelerate responsibilities for new contributors, but the topic needs to be reviewed again. Additionally, I'm looking to rotate the PMC chair but none of the other PMC members have sufficient time to step in. I've agreed to try to keep finding the time through our March report. I presume the lack of folks who think they have the extra hour or two per quarter means our community needs to get aggressive on PMC recruitment in addition to our need to expand the committer list. STATS - Currently 8 PMC members - Currently 10 committers - dev list has 41 subscribers (flat from previous period) - 17 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BK: Report from the Apache Zest Project [Niclas Hedhman] ## Description: Apache Zest is a community based effort exploring Composite Oriented Programming for domain centric application development. ## Issues: It has come to the PMC's attention that Eclipse Zest is a well-established subproject, within EMF/GEF/GMF ecosystem at Eclipse Foundation, and that there is some conceptual overlap (both deal with explicit application models). They also started way back in time, and the Zest PMC think that although we could stick to the name, we think we should express some goodwill towards Eclipse and change name. The sooner the better, especially since we have no published releases under the Apache Zest namespace. The new name "Apache Polygene" has been chosen, after quite a lot of discussion back and forth and some dead ends. We have just started the "unusual" process of project name change, and we are trying to capture the work needed in https://issues.apache.org/jira/browse/ZEST-195, a fairly long list of tasks (currently 18). We don't need Board assistance on this issue. ## Activity: Recruitment of new blood is continuing to be our weak spot. Re-positioning, re-branding, better tutorials and lowering the bar to entry are items to be worked on, inspired by other Apache projects, although I suspect too few small projects check what other smaller ASF projects do right. Zest is a small community, and this quarter was very typical, with good progress towards the long overdue 3.0 release, which is all about making the incompatible changes once and for all, both in namespaces as well as leveraging Java 8 features in public APIs and discarding outdated ways for that. Zest is started participating in Oracle's outreach beta testing of Java 9 in CI build, and we are currently reporting "yellow" but expect to go "green" before 3.0 release. ## Health report: Zest is small, but above the threshold for worry. Efforts are being worked on to simplify adoption. Mailing list activity remains moderate and JIRA issues are being both created and worked on. All active committers that are willing, are on the PMC already. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kent Sølvsten on Tue Sep 22 2015 ## Committer base changes: - Currently 18 committers. - No new committers added in the last 3 months - Last committer addition was Georg Ragaller at Thu Jun 16 2016 ## Releases: - Last release was JAVA-2.1 on Fri Jul 31 2015 ## Mailing list activity: Rich Bowen is taking up 100% of the traffic on the users@ list :-) with announcements. Officially, the users@ list is non-active as all queries are directed to the dev@ list. The dev@ activity this month was normal, although the stats shows a substantial increase, but that is probably due to a larger number of CI build reports, some related to Java 9 testing - users@zest.apache.org: - 19 subscribers (up 0 in the last 3 months): - 2 emails sent to list (2 in previous quarter) - dev@zest.apache.org: - 40 subscribers (up 3 in the last 3 months): - 332 emails sent to list (240 in previous quarter) ## JIRA activity: - 38 JIRA tickets created in the last 3 months - 12 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BL: Report from the Apache ZooKeeper Project [Flavio Junqueira] ## Description: Apache ZooKeeper is a system for distributed coordination. It enables distributed systems to implement a variety of primitives and mechanisms that are critical for such systems to function, e.g., distributed locks, master election, group membership, and configuration. ## Issues: There are no issues requiring board attention at this time. ## Activity: The focus of the community has been to lift the alpha label of the 3.5 branch. We have solved the main remaining issue (ZOOKEEPER-2014) and we are now getting ready to release 3.5.3, which is supposed to be the last alpha release of the 3.5 branch. The 3.5 branch has a number of important new features, including reconfiguration, which has been the main culprit for the stabilization of the branch. We have additionally been preparing a new release of our stable branch, 3.4.10. It will include bug fixes and one contribution that improves security for server-to-server communication. Both these releases are very close to coming out. We have organized a meetup at the Facebook HQ back in November. ## Health report: There has been a good amount of activity on all lists, new contributors, and new features proposed. There are potentially new committers currently being discussed on the private list. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Chris Nauroth on Sun Aug 07 2016 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Chris Nauroth at Wed Sep 09 2015 ## Releases: - Last release was 3.4.9 on Sat Sep 03 2016 ## Mailing list activity: The activity on the dev list remained roughly constant while the activity of the user list dropped. This is an artifact of questions now being asked on the dev list mostly because they often involve more than just a clarification over the API. The community has been favoring discussions on the dev list and slowly moving more towards asking questions directly on that dev list. We don’t really make an effort to have a clear separation between the two, although we suggest that API and use case questions are better on the user list. - dev@zookeeper.apache.org: - 500 subscribers (up 2 in the last 3 months): - 3251 emails sent to list (3252 in previous quarter) - user@zookeeper.apache.org: - 1182 subscribers (up 6 in the last 3 months): - 186 emails sent to list (300 in previous quarter) ## JIRA activity: The number of issues created has been greater than the number of issues resolved, creating a backlog. We need more committer cycles to help with the backlog, and we are working on inviting new committers. - 67 JIRA tickets created in the last 3 months - 33 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BM: Report from the Apache Geode Project [Mark Bretl] ## Description: - Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency. ## Issues: - No issues requiring board attention at this time ## Activity: - Graduated from the incubator November 21, 2016! - Released our first non-milestone release, 1.0.0-incubating. - Transitioned project resources from incubator to TLP namespace. - Started discussions about our first release as a TLP. - Jinmei Liao presented a talk at apachecon Europe: "Implementing Security in Apache Geode Using Apache Shiro." ## Health report: - Geode is still seeing active development. With our first non-milestone release we're hoping to settle into a more regular release cadence. We're still working to attract more contributors from outside of Pivotal and since graduation we're seeing more contributions coming in from other sources which is a good sign. ## PMC changes: - Currently 30 PMC members - No PMC changes since the last report to the incubator board. ## Committer base changes: - Currently 76 committers - Ken Howe joined as a committer Nov 15th. ## Releases: - 1.0.0-incubating October 25, 2016 ## Mailing list activity: - dev@geode.apache.org: - 154 subscribers (down -3 in the last 3 months): - 2258 emails sent to list (1529 in previous quarter) - issues@geode.apache.org: - 55 subscribers (up 0 in the last 3 months): - 2977 emails sent to list (2751 in previous quarter) - user@geode.apache.org: - 194 subscribers (up 13 in the last 3 months): - 187 emails sent to list (157 in previous quarter) ## JIRA activity: - 320 JIRA tickets created in the last 3 months - 279 JIRA tickets closed/resolved in the last 3 months ------------------------------------------------------ End of minutes for the December 21, 2016 board meeting.