The Apache Software Foundation Board of Directors Meeting Minutes June 15, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:33 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/30d7 The meeting was held via teleconference, hosted by Doug Cutting and Cloudera. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Shane Curcuru Bertrand Delacretaz Isabel Drost-Fromm Marvin Humphrey Jim Jagielski Chris Mattmann Brett Porter Greg Stein Mark Thomas Directors Absent: none Executive Officers Present: Rich Bowen Ross Gardler Craig L Russell Ulrich Stärk - dropped at 11:01 Executive Officers Absent: none Guests: Andrew Palumbo Daniel Gruno Hadrian Zbarcea Jake Farrell Robert Metzger Sam Ruby Sean Kelly Sidney Markowitz Tom Pappas Will Stevens 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of May 18, 2016 See: board_minutes_2016_05_18.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] The main topic of discussion for the board this month has been the possible need for additional staffing, and what that role should look like. This has considered everything from an infrastructure lead to a "general manager" role, and continues from the topics raised in Ross' report last month, as well as the Infrastructure Lead discussion item in February. At this point, no action has been taken. Thanks to everyone involved in publishing our second annual report earlier in the month. It looks great, and did pick up some positive attention. B. President [Ross] Once again I must apologize for the very late posting of this report. I will provide a full verbal report as it is unlikely all Directors will have had the time to absorb the contents here. The good news is that the personal issues keeping me from work like this are very definitely subsiding. Expect me back up to speed in the coming weeks. Executive Assistance Business as usual. No unexpected activities. Brand Management VP Brand reports an increase in the number of PMC members actively monitoring trademark usage. This has resulted in an increase in the number of concerns raised, in most cases only when they are significant issues rather than early diversions from policy. This highlights what is needed next in terms of the education of our PMCs in managing brand: "Since branding issues are not as clear cut as compiler errors, this often results in an imprecise call to action that is sometimes taken in the wrong spirit by the receiving PMC, resulting in a lot of unfortunate noise and anger." This months report from VP Brand contains a number of specific recommendations for our communities. I encourage everyone to read them and communicate them within their projects. Fundraising Hadrian has raised some concerns about a small increase in the number of Bronze sponsors that he is uncomfortable with, he is of the opinion that they are seeking advertising rather than supporting the foundation. He attributes this to a relaxing of the "no-follow" policy. This was relaxed some time ago but only recently documented on the fundraising website website. The timing makes it unclear if the removal of no-follow is related to these two new sponsors and since both sponsors likely depend on ASF technologies and are (it appears) legitimate businesses I am taking no position on this other than to remind VPs Fundraising that they are free to define policy as they see fit. Another area that needs clarification is "in-kind" donations, in particular for infra. This conversation is on-going. Marketing and Publicity Our annual report was published on time. A big thank you to Sally for coordinating and to all contributors. I am pleased to say I only wrote one report this time around (my own) and thus the whole process was much more enjoyable for myself. I have reminded VPs Fundraising to ensure that this needs to be sent out to sponsors, but I can report my own employer was pleased to see the details laid out clearly. I am confident that this will make renewal conversations easier over the coming year. Sally's report contains the usual "business as usual" facts and figures about our ongoing M&P work. Infrastructure The search continues to find new staff. Unfortunately the only candidates found so far are cost prohibitive (that I know of wither David or I have spoken to 7 potential candidates). Infra continue to raise concerns, with justification. We are broadening the search through broader job advertising sites and would welcome any referrals from the broader community. I can provide a job description on request. There is also a concern about the growth of the foundation and what it means to infra resourcing. For example: "Given our current rate of growth, addressing tickets alone will require 5.5 full time staff members by years end, and if we continue at our current pace we'll need to add 1 to 1.5 staff members every 2 years just to deal with continued growth." This does not include "big ticket items" such as Git support. The infra report includes more details and data. This issue will have my full attention over the coming year. We are not at risk today, but financial this model breaks in 4-5 years if we do not either increase fundraising or decrease demands on infra. The solution is to do both increase fundraising and reduce demand (both through removal of unnecessary work and enabling more self-service). There have been some outages around Nexus. There is a medium term plan to move this to a more reliable and maintainable infrastructure. In the meantime the team continue to use sticky plasters where necessary. David has started renegotiating contracts with existing employees/contractors as per my 1:1 with each at ApacheCon. As a result of understaffing we did not meet this months SLA for repository.a.o (see above). Overall we met SLA on the three categories of critical, core and standard services. Given the staffing circumstances this is understandable and I support the teams prioritization efforts. Travel Assistance Committee No report submitted at the time of writing. However, EA has reported that the TAC recipient surveys are complete with responses being prepared for publication. We are close to closing out the budget for TAC this time around. With the recent announcement of the opening of EU CFP TAC are now planning their timetable to support that event. Additionally, please see Attachments 1 through 6. @Ross: Post the infra job description for members to review C. Treasurer [Ulrich] Uli has been on-boarded is currently learning the ropes. Virtual and Tom have been very helpful on this front. Access to the BitCoin wallet that Rich set up some time ago has been transferred to the Treasurer office Income and Expenses for May 2016 CASH BASIS Current Balances: May 2016 Citizens Checking $490.110 Citizens Money Market $1.201.450 Amazon- ASF Payments $- Paypal - ASF $83.126 Wells Fargo Checking - ASF $- Wells Fargo Savings $- Total Checking/Savings $1.774.686 Income Summary: Inkind Revenue $7.167 Public Donations $752 Sponsorship Program $69.545 Programs Income $- Other Income $825 Interest Income $509 Total Income $78.797 Expense Summary: In Kind Expense $7.167 Infrastructure $38.868 Sponsorship Program $- Programs Expense $- Publicity $35.200 Brand Management $- Conferences $1.071 Travel Assistance Committee $1.623 Tax and Audit $6.000 Treasury Services $3.100 General & Administrative $8.737 Total Expense $101.767 Net Income $(22.970) D. Secretary [Craig] In May, 71 iclas, four cclas, and three grants were received and filed. E. Executive Vice President [Rich] Registration and CFPs are up for ApacheCon Seville, and Apache Big Data Seville, at http://apachecon.com/ but this hasn't been widely announced. We'll be starting to promote that in the coming week or two, as soon I have some time. Meanwhile, LF is promoting the events via their websites. Audio from ApacheCon Vancouver is slowly making it up to Feathercast.org. I think at this point all of the audio has been processed and uploaded. I just need to do the actual podcast posts via Wordpress to publish them. F. Vice Chairman [Greg] Nothing to report this month. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Chris] See Attachment 7 B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 8 C. Apache Security Team Project [Mark J. Cox / Mark] See Attachment 9 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Abdera [bp] # Axis [mt] # Helix [bp] # OpenNLP [bp] # Shiro [bp] # Spark [mh] # Synapse [mt] # Tajo [bp] A. Apache Abdera Project [Ant Elder / Marvin] See Attachment A B. Apache Allura Project [Dave Brondsema / Greg] See Attachment B C. Apache Any23 Project [Lewis John McGibbney / Shane] See Attachment C D. Apache Apex Project [Thomas Weise / Bertrand] See Attachment D E. Apache Archiva Project [Olivier Lamy / Brett] See Attachment E F. Apache AsterixDB Project [Till Westmann / Jim] See Attachment F G. Apache Aurora Project [Bill Farner / Isabel] See Attachment G H. Apache Axis Project [Deepal Jayasinghe / Brett] See Attachment H @Mark: follow up with PMC and get an improved report for next month I. Apache Bahir Project [Luciano Resende / Bertrand] See Attachment I J. Apache Bigtop Project [Olaf Flebbe / Shane] See Attachment J K. Apache Bloodhound Project [Gary Martin / Jim] See Attachment K L. Apache BVal Project [Matt Benson / Marvin] See Attachment L M. Apache Camel Project [Christian Mueller / Mark] See Attachment M N. Apache Cayenne Project [Andrus Adamchik / Isabel] See Attachment N O. Apache Chemistry Project [Florian Müller / Chris] See Attachment O P. Apache CloudStack Project [Will Stevens / Greg] See Attachment P Q. Apache Commons Project [Gary D. Gregory / Mark] See Attachment Q R. Apache Cordova Project [Shazron Abdullah / Marvin] See Attachment R S. Apache cTAKES Project [Pei J Chen / Chris] See Attachment S T. Apache Curator Project [Jordan Zimmerman / Jim] See Attachment T U. Apache Etch Project [Martin Veith / Greg] See Attachment U V. Apache Falcon Project [Srikanth Sundarrajan / Shane] See Attachment V W. Apache Felix Project [Carsten Ziegeler / Isabel] See Attachment W X. Apache Flex Project [Alex Harui / Brett] See Attachment X Y. Apache Flink Project [Stephan Ewen / Bertrand] See Attachment Y Z. Apache Gump Project [Stefan Bodewig / Mark] See Attachment Z AA. Apache Helix Project [Kishore Gopalakrishna / Bertrand] No report was submitted. AB. Apache Hive Project [Ashutosh Chauhan / Jim] See Attachment AB AC. Apache Ignite Project [Dmitriy Setrakyan / Shane] See Attachment AC AD. Apache Incubator Project [Ted Dunning / Brett] See Attachment AD AE. Apache Jackrabbit Project [Michael Dürig / Marvin] See Attachment AE AF. Apache Johnzon Project [Hendrik Saly / Isabel] See Attachment AF AG. Apache Karaf Project [Jean-Baptiste Onofré / Chris] See Attachment AG AH. Apache Labs Project [Danny Angus / Greg] See Attachment AH AI. Apache Lucene Project [Michael McCandless / Greg] See Attachment AI AJ. Apache Lucene.Net Project [Prescott Nasser / Brett] See Attachment AJ AK. Apache OFBiz Project [Jacopo Cappellato / Chris] See Attachment AK AL. Apache Olingo Project [Christian Amend / Shane] See Attachment AL AM. Apache OODT Project [Tom Barber / Bertrand] See Attachment AM AN. Apache OpenNLP Project [Jörn Kottmann / Marvin] No report was submitted. AO. Apache OpenWebBeans Project [Mark Struberg / Jim] See Attachment AO AP. Apache Perl Project [Philippe M. Chiasson / Isabel] See Attachment AP AQ. Apache Pig Project [Daniel Dai / Mark] See Attachment AQ AR. Apache Pivot Project [Roger Whitcomb / Brett] See Attachment AR AS. Apache Portable Runtime (APR) Project [Jeff Trawick / Marvin] See Attachment AS AT. Apache Portals Project [David Sean Taylor / Isabel] See Attachment AT AU. Apache Sentry Project [Sravya Tirukkovalur / Mark] See Attachment AU AV. Apache ServiceMix Project [Krzysztof Sobkowiak / Chris] See Attachment AV AW. Apache Shiro Project [Les Hazlewood / Jim] No report was submitted. AX. Apache Sling Project [Carsten Ziegeler / Greg] See Attachment AX AY. Apache SpamAssassin Project [Kevin A. McGrail / Bertrand] See Attachment AY AZ. Apache Spark Project [Matei Zaharia / Shane] See Attachment AZ BA. Apache Stanbol Project [Fabian Christ / Jim] See Attachment BA BB. Apache Storm Project [P. Taylor Goetz / Shane] See Attachment BB BC. Apache Synapse Project [Hiranya Jayathilaka / Greg] See Attachment BC BD. Apache Tajo Project [Hyunsik Choi / Mark] No report was submitted. BE. Apache Tiles Project [Mick Semb Wever / Bertrand] See Attachment BE BF. Apache TinkerPop Project [Stephen Mallette / Brett] See Attachment BF BG. Apache Tomcat Project [Mladen Turk / Isabel] See Attachment BG BH. Apache UIMA Project [Marshall Schor / Chris] See Attachment BH BI. Apache VCL Project [Andy Kurth / Marvin] See Attachment BI BJ. Apache Web Services Project [Sagara Gunathunga / Greg] See Attachment BJ BK. Apache Wicket Project [Martijn Dashorst / Shane] See Attachment BK BL. Apache Wink Project [Luciano Resende / Brett] See Attachment BL BM. Apache Xerces Project [Michael Glavassevich / Jim] See Attachment BM BN. Apache Yetus Project [Sean Busbey / Mark] See Attachment BN BO. Apache Zeppelin Project [Lee Moon Soo / Bertrand] See Attachment BO BP. Apache Zest Project [Niclas Hedhman / Marvin] See Attachment BP BQ. Apache ZooKeeper Project [Flavio Junqueira / Chris] See Attachment BQ Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Lucene Project Chair WHEREAS, the Board of Directors heretofore appointed Mike McCandless (mikemccand) to the office of Vice President, Apache Lucene, and WHEREAS, the Board of Directors is in receipt of the resignation of Mike McCandless from the office of Vice President, Apache Lucene, and WHEREAS, the Project Management Committee of the Apache Lucene project has chosen by vote to recommend Tommaso Teofili (tommaso) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Mike McCandless is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Lucene, and BE IT FURTHER RESOLVED, that Tommaso Teofili be and hereby is appointed to the office of Vice President, Apache Lucene, 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. Thread: https://s.apache.org/X3vi Special Order 7A, Change the Apache Lucene Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache SpamAssassin Project Chair WHEREAS, the Board of Directors heretofore appointed Kevin A. McGrail (kmcgrail) to the office of Vice President, Apache SpamAssassin, and WHEREAS, the Board of Directors has been notified that Kevin A. McGrail is not able to fulfill the duties and responsibilities of the office of Vice President, Apache SpamAssassin, and WHEREAS, the Project Management Committee of the Apache SpamAssassin project has chosen by vote to recommend Sidney Markowitz (sidney) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Kevin A. McGrail is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache SpamAssassin, and BE IT FURTHER RESOLVED, that Sidney Markowitz be and hereby is appointed to the office of Vice President, Apache SpamAssassin, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache SpamAssassin Project Chair, was approved by Unanimous Vote of the directors present. C. Terminate the Apache Etch Project WHEREAS, the Project Management Committee of the Apache Etch 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 Etch project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Etch 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 Etch Project; and be it further RESOLVED, that the office of "Vice President, Apache Etch" is hereby terminated; and be it further RESOLVED, that the Apache Etch PMC is hereby terminated. Special Order 7C, Terminate the Apache Etch Project, was approved by Unanimous Vote of the directors present. D. Terminate the Apache Bloodhound Project WHEREAS, the Project Management Committee of the Apache Bloodhound 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 Bloodhound project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Bloodhound 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 Bloodhound Project; and be it further RESOLVED, that the office of "Vice President, Apache Bloodhound" is hereby terminated; and be it further RESOLVED, that the Apache Bloodhound PMC is hereby terminated. Special Order 7D, Terminate the Apache Bloodhound Project, was tabled. E. Establish the Apache Twill 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 providing a set of libraries as abstraction to develop distributed applications, with a programming model that is similar to running threads, inside compute cluster such as Apache Hadoop YARN NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Twill Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Twill Project be and hereby is responsible for the creation and maintenance of software related to providing a set of libraries as abstraction to develop distributed applications, with a programming model that is similar to running threads, inside compute cluster such as Apache Hadoop YARN and be it further RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Twill 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 Twill Project: * Terence Yim * Andreas Neumann * Gary Helmling * Albert Shau * Poorna Chandra * Henry Saputra NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further RESOLVED, that the Apache Twill Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Twill podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Twill podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7E, Establish the Apache Twill Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Craig proposes that the board appoint Sam Ruby to the position of Assistant Secretary. The board appoints Sam Ruby to the office of Assistant Secretary. B. Jim wishes to discuss the OSI Affiliate program Jim: a few years back, Jim was on the OSI board; ASF thought it might make sense to join OSI but didn't match OSI who were trying to establish themselves. OSI is now trying to refocus on community aspects and now sees affiliates as helping. Jim volunteers to continue discussion with OSI. Chris: ok Marvin: will we have to opt out or opt in to OSI decisions? Jim: OSI will notify affiliates before taking action affecting them. In fact, ASF can help redefine affiliate interaction Mark: will OSI expect affiliates to pay dues? Jim: no dues for affiliates. Mark: what are benefits to ASF? Jim: gives ASF more opportunity to promote The Apache Way; up to now projects might not be steered to ASF @Jim: continue to work with OSI and report to the board next month 9. Review Outstanding Action Items * Ross: Notify PMC that tools are available to aid in the Apache Extras [ Pivot 2015-12-16 ] Status: * Brett: Add another reminder to tardy projects the Monday before the meeting [ Discussion Items 2016-02-17 ] Status: * Shane: pursue a report for Bloodhound [ Bloodhound 2016-03-16 ] Status: Thanks to Bloodhound for providing a detailed report including their vote to go to the Attic. * Rich: Work with PMC to get a better report next quarter [ Hive 2016-03-16 ] Status: present this month and approved * Shane: Suggest ways to improve the board report; especially the the "Health" section [ Tiles 2016-03-16 ] Status: Working separately on clarifying updates to PMC requirements and board reporting guidelines documents, will send to Tiles when done. * Jim: Resubmit next month [ Archiva 2016-04-20 ] Status: Complete * Brett: pursue a report for Geronimo for next month. Is the project still viable, or is another chair needed? [ Geronimo 2016-04-20 ] Status: done last month * Mark: pursue a report for SpamAssassin [ SpamAssassin 2016-04-20 ] Status: Done. A resolution to change the chair and a report have been provided by the PMC for the 2016-06-15 meeting. * Brett: help Synapse in its move to the Attic. [ Synapse 2016-04-20 ] Status: back in action * Greg: The report continues to be unacceptable. Time for a new chair? [ Web Services 2016-04-20 ] Status: on hold, pending Jim's inquiry * Brett: pursue a report for Abdera [ Abdera 2016-05-18 ] Status: (sc) A minimal report was filed before the board meeting. * Mark: explain to Axis PMC what the board is looking for in a report [ Axis 2016-05-18 ] Status: E-mail sent 2016-05-31. Looking at the most recent report, it appears it was ignored. * Jim: prepare an attic resolution [ Etch 2016-05-18 ] Status: Complete * Brett: ensure that committer dates are present in the next scheduled report [ HttpComponents 2016-05-18 ] Status: pinged * Marvin: pursue a report for Perl [ Perl 2016-05-18 ] Status: Complete. * Greg: pursue a report for Xerces [ Xerces 2016-05-18 ] Status: they will report in June 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 11:42 a.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] TAC: * Post-conference surveys were sent to the TACers. Some of the stories will be included on the website. * Final expenses will be provided by Nick when finalized. In the process of reconciling with the Linux Foundation (they owe the ASF for reimbursement on the speakers they agreed to fund, but we paid for upfront for convenience; and we owe them for the TACers registration fees). Fundraising * Handled the requests for new bronze sponsorship ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] # Operations A number of project-related discussions spilled across trademarks@ this past month, with complaints about either vendor use of project brands or PMC handling of the situations; Spark and Cassandra both were major sources of discussion and action by members, the PMCs, and the board. The good news is that this shows a wider variety of individuals are looking at and raising issues that affect how our project brands and the Apache brand are used (or mis-used). We've long needed to have more Members and project contributors looking for and bringing up these issues. The not as good news is the way that these issues have been raised, as well as in some cases how the PMC has responded. The trouble with branding mis-uses is that many project participants don't pay attention until they happen to see something that REALLY UPSETS THEM! Thus we historically have plenty of times with no reports, and then suddenly a project contributor or ASF Member RAISES THIS HUGE ISSUE THAT MUST BE DEALT WITH. Since branding issues are not as clear cut as compiler errors, this often results in an imprecise call to action that is sometimes taken in the wrong spirit by the receiving PMC, resulting in a lot of unfortunate noise and anger. Separately, one PMC did not appear to take recent complaints seriously enough, to the point where the board required a new project report and discussed some very serious potential future consequences. This not as good news calls for better behavior in three kinds of situations: 1- If you see an Apache project branding mis-use, say something - in a polite, specific, and actionable way. We have guides for this. Branding issues need to be as specific as possible, to ensure we can request concrete steps by the mis-user to correct them. In particular, assuming ignorance rather than malice, and raising issues in a positive way really help to reduce miscommunications and arguments about details. http://www.apache.org/foundation/marks/reporting 2- It's clear that not all PMCs fully understand and/or regularly pay attention to their project's branding issues. Detailed procedures exist, but ensuring that PMCs are truly taking things like Project Independence to heart in their day to day actions - as well as in the public uses of their brand by vendors in the ecosystem - is something we still need to work on. Branding issues are far easier to solve the earlier they are reported, and PMCs need to fully ensure the appearance of independent governance for their projects: http://community.apache.org/projectIndependence 3- While we are a volunteer-led organization that allows individual project participants broad responsibility and ability to direct their own project's affairs, we are still a single Foundation with documented governance and required policies. It should not take a director bringing up serious consequences to a PMC to have the PMC take credible reports of brand mis-uses seriously, and to take positive action on specific issues immediately. # Registrations After some great progress on a few legal related issues, several new issues have come up and some past ones seem stalled. It's clear I'll need to work on more time as VP to keep the legal & application process side of the house on track. This needs more investigation to see if it's related to our current counsel billing process and budget. OFBIZ is now our registered trademark in the US. We have applied for US registrations for TEZ and FLINK. Several other projects have expressed interest in US registrations, including one or two logo registrations. # Organizational Note For the record, I have been laid off from my employer, and am now formally unaffiliated. This does not change my view on the VP, Brand Management position, which has always been that the good of the Foundation as a whole comes first. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities continue normally. During the past few weeks we got a number of Bronze sponsors that, while I am sure rely on ASF technologies for their operations, seem to be not very well aligned with ASF's mission (this is not an allegation, just my personal opinion). The concern, expressed on the mailing list is that such sponsors seem more interested in marketing related benefits. Another item that generated a bit of a debate on the Fundraising@ mailing list is related to a discussion I had with a cloud provider to offer an in-kind sponsorship that seems to be not very well received by infra@. While I will have to clarify with infra@ and its VP what exactly is we do and do not need, I started a more general thread on Fundraising@ to gather ideas and opinions about the type of services we would need as in-kind sponsorship. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: we remain within budget, with no outstanding invoices due at this time. II. Fundraising/Branding/Marketing/ComDev liaison: Sally Khudairi issued the second ASF Annual Report; thanks to Brett Porter, Ross Gardler, Rich Bowen, Chris Mattmann, Tom Pappas, Hadrian Zbarcea, David Nalley, Shane Curcuru, Jim Jagielski, and Daniel Gruno for their contributions. Whilst post-ApacheCon liaison has quieted down somewhat, Sally continues to counsel a handful of vendors involved with various Apache projects. III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 6 June 2016 --The Apache® Software Foundation Announces Annual Report for 2015-2016 Fiscal Year - 25 May 2016 --The Apache Software Foundation Announces Apache® Zeppelin™ as a Top-Level Project - The Apache Software Foundation Announces Apache® TinkerPop™ as a Top-Level Project IV. Informal Announcements: 8 items were published on the ASF "Foundation" Blog. 6 Apache News Round-ups were issued, with a total of 96 weekly summaries published to date. 39 items were Tweeted on @TheASF. No new videos have been added to the ASF YouTube channel. V. Future Announcements: two announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 11 media queries. Over the past month, the ASF received 1,923 press clips vs. last month's clip count of 1,074. VII. Analyst Relations: we responded to 3 analyst queries. Apache was mentioned in 46 reports by Gartner (including 14 “Cool Vendor” reports), 14 reports by Forrester, 22 reports by 451 Research, and 7 reports by IDC. VIII. ApacheCon liaison: Sally will resume work with Melissa Warnkin next month regarding promotional items needed for ApacheCon Europe. IX. (Non-ASF) Industry Events and Outreach liaison: no formal activities are taking place at this time. X. Newswire accounts: we have 41 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] Operations Action Items: ======================== Hiring -------- We've published a job description and are working with the President and Virtual to publish this widely in efforts to solicit more candidates. Demand for Infra services ----------------------------------- The number of projects that the Foundation is responsible for continues to grow, and that is placing an ever increasing burden on demands for infrastructure resources. Today, our largest constraint is staff members to do the work. Historically, we've had an average of 33 tickets per month per full time staff member, and as that average grows we typically add staff. Today we have 3.5 full time staff members - working, though statically, we really should be at 5 just to be able to handle the ticket load. (This does not include any time to focus on larger scale projects) Given our current rate of growth, addressing tickets alone will require 5.5 full time staff members by years end, and if we continue at our current pace we'll need to add 1 to 1.5 staff members every 2 years just to deal with continued growth. Take a look at a graph demonstrating the growrth rates, demand for services based on tickets, and staff members: https://i.imgur.com/72V0DFN.png Short Term Priorities: ====================== TLP Some of the automation behind the mechanics of transforming a graduated podling into a TLP fell into disrepair over the past few months. This led to many exaggerated timelines for TLP graduation. Infra held a TLP work day and while it largely remains a manual operation there is now a runbook that is current for dealing with graduations. And all of the pending graduations were processed. There is ongoing work to automate large swaths of that, but for now it should only take ~30 minutes to process a newly-graduated TLP. Long Range Priorities: ====================== Because of staffing shortage, precious little work has occurred on our long range priorities. Instead we've moved back to what can largely be described as firefighting and attempting to keep up with incoming work as best as can be managed. General Activity: ================= Outages: ------------ We suffered a somewhat longterm outage of the Nexus repository. We temporarily restored the service, but a service move off of the ailing VMW infrastructure is planned for the short term future. More recently, we suffered both a database and VMware-related outage on the same day. Our VMware infrastructure is on increasingly brittle hardware. We have been concerted efforts for some months on moving VMs off of this infrastructure, and continue to do so. New Contracts -------------------- Following up on discussions that occurred at ApacheCon NA, we are beginning the process of renegotiating contracts for our non-employee staff members. Uptime Statistics: ================== Overall we met the service uptime, though on an individual service basis we did not meet the uptime expectations for repository.a.o. Please see: http://status.apache.org/sla/ ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Nick Burch] ACNA 16 ------- Surveys have gone out, and most feedback received. Generally very positive, a few small suggestions for improvements for next time (especially around tooling and on-the-ground communications). Interviews for the Past Recipients site in progress We still need to finalise costs with the LF before we can be sure on exactly how much the event cost. (We owe them for some registration fees, they owe us for some other bits!) ACEU 16 ------- Disucussions have started on when to close applications based on the CFP dates No progress yet on questions, promotion or the extra/tweaked tooling needed Future ------ Notes from Vancouver meetings still need to finish being written up and circulated ----------------------------------------- Attachment 7: Report from the VP of W3C Relations [Andy Seaborne] No changes to W3C participation by ASF. An open letter from the EFF to the W3C Advisory Committee regarding EME (Encypted Media Extension) generated a lot of discussion. This included resubmiting the proposal for a covenant to protect implementers and to make it an exit condition for the EME work proceeding. The outome so far is a propsal for an advisory "Technology and Policy Interest Group" (TechPolig). Proceedings will be W3C-member-only. The initial areas for TechPolig are Deep Linking, DMCA-like challenges and Surveillance. W3C background: https://www.w3.org/2016/03/EME-factsheet ----------------------------------------- Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski] Some discussions regarding license compatibility, specifically related to OpenSSL dependency, and the official release process. No issues requiring board attention. ----------------------------------------- Attachment 9: Report from the Apache Security Team Project [Mark J. Cox] Following from the discussion from Mark Thomas at last board mtg we discussed a plan for handling of security issues that are repeatedly ignored by a PMC (determined by history of dealing with the PMC/issue severity/issue history). We will draft a mail ready to be sent to the issue reporter which outlines the steps we made to contact the PMC and our suggested next action (usually that the reporter posts the details of the issue public in some forum such as the oss-security list). That draft will be sent to the PMC as our final attempt to get the PMC to respond and work with the reporter, and after some further period of inactivity will be sent to the reporter and recorded in the next board report. Stats for May 2016: 10 CVEs issued to projects (some may not be public yet). e-mails to security@ 3 Support questions 2 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to Android licenses 12 Direct Vulnerability report to security@apache.org 1 [juddi] 1 [comdev] 2 [site] rejected 1 [ranger] 1 [qpid] 1 [axis] 1 [wicket] 1 [flex] 1 [openmeetings] 1 [oozie] 1 [archiva] 1 Vulnerabilities reported to projects 1 [commons] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] Apache Abdera provides Java implementations of the IETF Atom Syndication Format and Publishing Protocol specifications. Abdera is in maintenance mode with minimal development activity. I believe there are at least three PMC members providing oversight still. Not much at all going on in Abdera the last few months other than misfiled JIRA. The last release was over two years ago, the last commiter / PMC member addition was Nov 2011. No board issues. ----------------------------------------- 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: - Made a 1.4.0 release - One GSOC student being mentored - IRC being used more among some new contributors/users - Decreased activity from core committers ## Health report: - Frequent committers are not as frequent or present any more. - New contributors/users/committers are engaged and making contributions though. ## PMC changes: - Currently 13 PMC members. - Pranav Sharma was added to the PMC on Sun Feb 07 2016 ## Committer base changes: - Currently 13 committers. - Pranav Sharma was added as a committer on Mon Feb 08 2016 ## Releases: - 1.4.0 was released on Mon Apr 11 2016 ----------------------------------------- Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (Any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention at this time ## Activity: Unfortunately the proposed GSoC project did not go ahead. Lessons have been learned from the application period and next year we will better engage with target communities. Activity has been pretty low as usual with at least one blocking issue which needs t be addressed before we can make our next release. ## Health report: Any23 continues to be a quiet but useful project for its user base. The main issue which will increase project health is for us to make a 1.2 release. We also need to grow the community and hopefully add a new committer or PMC member. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Stephane Corlosquet on Sun Sep 07 2014 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Stephane Corlosquet at Mon Aug 18 2014 ## Releases: - Last release was 1.1 on Tue Oct 28 2014 ## Mailing list activity: Both dev@ and user@ have increased which is excellent. - dev@any23.apache.org: - 36 subscribers (up 1 in the last 3 months): - 89 emails sent to list (65 in previous quarter) - user@any23.apache.org: - 52 subscribers (up 4 in the last 3 months): - 14 emails sent to list (5 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment D: Report from the Apache Apex Project [Thomas Weise] Apache Apex is a distributed, large-scale, high throughput, low-latency, fault tolerant, unified stream and batch processing platform for Apache Hadoop. ## Issues: There are no issues that require the Board's attention. ## Status/Activity: Top level project migration tasks were completed with LDAP groups now properly setup and repositories renamed. Last month saw releases 3.4.0 of Apex Core and Malhar. Community is now focused on road map items for the next Malhar release, especially in the higher level API area, integrations with other ecosystem projects and improving usability of operators. Continued presentations at meetups with several events during next weeks: http://www.meetup.com/pro/apacheapex/ There will be presentations about Apache Apex at Hadoop Summit in San Jose. ## Community: - Currently 14 PMC members. - Last PMC addition was Siyuan Hua 2016-06-07 - Currently 39 committers. - Last committer addition was Ashish Tadose on 2016-03-11 https://projects.apache.org/committee.html?apex - 54 contributors all time ## Releases: Following are the most recent releases: - Malhar 3.4.0 released 2016-05-25 - Core 3.4.0 released 2016-05-12 - Core 3.2.1 released 2016-04-20 ----------------------------------------- Attachment E: Report from the Apache Archiva Project [Olivier Lamy] ## Description: Apache Archiva software is an extensible repository management tool that helps taking care of your own personal or enterprise-wide build artifact repository. ## Issues: There are no issues requiring board attention at this time ## Activity: Low. 3+ people have indicated presence, so has sufficient oversight. ## Health report: Despite low activity we were able to release a new version. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Baptiste Onofre on Fri Jul 11 2014 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Sascha Vogt at Mon Jul 14 2014 ## Releases: - 2.2.1 was released on Mon May 30 2016 ## Mailing list activity: - users@archiva.apache.org: - 234 subscribers (up 0 in the last 3 months): - 15 emails sent to list (12 in previous quarter) - dev@archiva.apache.org: - 108 subscribers (up 4 in the last 3 months): - 27 emails sent to list (11 in previous quarter) - issues@archiva.apache.org: - 38 subscribers (up 2 in the last 3 months): - 87 emails sent to list (38 in previous quarter) - notifications@archiva.apache.org: - 15 subscribers (up 2 in the last 3 months): - 7 emails sent to list (11 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 61 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment F: Report from the Apache AsterixDB Project [Till Westmann] Description: Apache AsterixDB is a scalable big data management system (BDMS) that provides storage, management, and query capabilities for large collections of semi-structured data. Activity: - The general state of the project - and the report - are largely unchanged from last month. Development and discussions are active, the community is healthy and engaged. The move of infra sources has been started (the mailing lists were moved), but the migration ticket in JIRA is still "waiting for infra". - Kaveen Rodrigo has started working with the AsterixDB community on a GSoC project. Issues: - TLP migration JIRA tasks not started yet: https://issues.apache.org/jira/browse/INFRA-11789 PMC/Committership changes: There have been no changes since graduation. The last committer/PPMC member added was Michael Blow on 2016-03-28. Releases: AsterixDB graduated from the Incubator on April 20, 2016. The last releases were on February 26, 2016: AsterixDB 0.8.8-incubating and Hyracks 0.2.17-incubating. ----------------------------------------- Attachment G: Report from the Apache Aurora Project [Bill Farner] 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 while working towards our upcoming 0.14.0 release. The upcoming release will contain a number of bug fixes, stability enhancements and new experimental features added such as Mesos GPU resource support, external webhook support, launching tasks using filesystem image with the new Apache Mesos unified containerizer. Bill Farner has indicated that he would like to step down as the Apache Aurora PMC chair, discussion and vote thread for a new chair will be started soon. Community --- Latest Additions: * PMC addition: Stephan Erb, 2.3.2016 Issue backlog status since last report: * Created: 62 * Resolved: 80 Mailing list activity since last report: * @dev 329 messages * @user 103 messages Releases --- Last release: Apache Aurora 0.13.0 released 4.13.2016 Release candidate: Apache Aurora 0.14.0 release candidate vote is currently in progress ----------------------------------------- Attachment H: 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 stacks). ## Issues: - There are no issues requiring board attention at this time. However, we had a discussion regarding moving some of the inactive projects to Attic and also had a vote regarding the same [1]. During the discussion [2] three individuals (Rafael Bronzeri, Giorgio Zoppi and Sendil Rajendhran) came forward to contribute to the project and now we have given them the opportunity and watching the progress. If no progress is made we will move the projects to Attic. ## Activity: - Received Security Disclosure - Persistent Cross-Site Scripting in Apache Axis2 ( CVE-2010-3981). We addressed it and released the fixed code. Kudos to Andreas for quick fix and the release. - Axis PMC was able to release the most waited Axis2 1.7.3 release.. ## PMC/Committer changes: - Currently 61 PMC/Commiters members. - No new PMC members added in the last 3 months - Last PMC addition was on July 7 2015 ## Releases: - Apache Axis2 1.7.3 (May 30, 2016) ## Community activities - User list - 16 emails. - Dev list - 554 emails ( 157 - Apr, 209-May, 188-June) - Commits - 188 commits. [1] - http://mail-archives.apache.org/mod_mbox/axis-c-dev/201604.mbox/%3c571A4272.7040109@gmail.com%3e [2] - http://mail-archives.apache.org/mod_mbox/axis-c-dev/201604.mbox/%3c5718EA04.2020000@gmail.com%3e ----------------------------------------- Attachment I: Report from the Apache Bahir Project [Luciano Resende] Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark. Community Activity: Apache Bahir was created on on 18/05/2016 and has just finished up setting up the project infrastructure. Seeding code has been imported from Apache Spark hash 8301fadd8 and we are discussing/start working on a release based on Apache Spark 2.0.0-preview release. Issues: There were two questions related to PMC/Committership related to inclusion in the project initial roster which were discussed on the private mailing list and seems to be ok now. Releases: * None Committers or PMC changes: * None Trademark/Branding: * No known issues. Legal Issues: * None ----------------------------------------- Attachment J: 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: Issues regarding ODPi's vs. Apache Bigtop position have been resolved on the private@ mailing list. ## Releases: 1.1.0 was released on Fri Jan 29 2016 ## Activitiy We see a 10% new members increase on the dev mailing list in the last three months and important new contributions to the project: An AARCH64 ARM Machine has been provided by Linaro via ODPi to the project. A major new feature contributed by ubuntu is in the queue: Juju charms for apache bigtop. [1] From the last uptick of patches for inclusion of additional big data components into the Bigtop Stack these have been processed: Apache Flink, Apache Apex (incubating) and Quanta File System (QFS) packaging has been included into the master branch now. Work is still continuing on further support, especially on Flink deployment. There have been a couple of talks around Apache Bigtop at ApacheCon Big Data NA: Konstantin Boudnik & Roman Shaposhnik: - How ODPi Leveraged Apache Bigtop to Get to Market Faster (and You Can Too!) Antonio Rosales & Konstantin Boudnik: - Apache BigTop Hadoop Dev Test Benchmark on Your Favorite Cloud or Laptop Konstantin Boudnik: - Apache Bigtop: Overview and 2016 Community Update Amir Sanjar & Evans Ye: - Dockerized Hadoop Platform and Recent Updates in Apache Bigtop Evans Ye: - Using the SDACK Architecture to Build a Big Data Product ## PMC changes: - Last PMC addition was Nate D'Amico on Fri Jan 22 2016 ## Committer base changes: - Amir Sanjar was added as a committer on Fri Jun 03 2016 ## Links: 1. https://issues.apache.org/jira/browse/BIGTOP-2435 ----------------------------------------- Attachment K: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== The board should be aware that the Bloodhound PMC has voted on moving the project to the attic as discussed below. 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 additions in January 2014. The last new committers were added in May 2014. Community & Development ======================= As discussed in the last report, due to there not being enough active PMC members with the necessary skills to keep the project going, there has been discussion of moving the project to the Attic. As such a vote has been undertaken to make an official decision on this, which was passed with the following results: +1: (7) brane, chambej, gjm, matevz, mbooth, rjollos, saintgermain 0: (0) -1: (0) A link to the summary email for this is here: https://s.apache.org/qqj0 The resolution to terminate the Apache Bloodhound project has therefore been added as item D of the Special Orders section of the board agenda for this month. ----------------------------------------- Attachment L: Report from the Apache BVal Project [Matt Benson] ## Apache BVal Report June 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. ### Releases ### No new releases; last BVal release (v1.1.1) was released February 2016. ### Activity ### No activity to speak of this quarter. The specification process for Bean Validation v2.0 is beginning to get underway which will inevitably trigger a round of activity for Apache BVal to make a compliant release. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment. ----------------------------------------- Attachment M: 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 resolved a trademark issue on GitHub with a project called Camel.Net. - We are focusing the development of the next minor release Apache Camel 2.18.0. ## Health report: - The project is healthy, active and stays at a high level. - We got 10 new contributors who signed the ICLA in this reporting periode. ## PMC changes: - Currently 28 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Gregor Zurowski on Fri Dec 04 2015 ## Committer base changes: - Currently 52 committers. - New commmitters: - Luca Burgazzoli was added as a committer on Thu Apr 07 2016 - Stephan Siano was added as a committer on Tue Apr 26 2016 ## Releases: - 2.15.6 was released on Thu Mar 31 2016 - 2.16.3 was released on Sat Apr 09 2016 - 2.17.0 was released on Sat Mar 26 2016 - 2.17.1 was released on Sun May 08 2016 ## Mailing list activity: - users@camel.apache.org: - 903 subscribers (up 14 in the last 3 months): - 1704 emails sent in the past 3 months (1349 in the previous cycle) - dev@camel.apache.org: - 346 subscribers (up 9 in the last 3 months): - 842 emails sent in the past 3 months (634 in the previous cycle) - commits@camel.apache.org: - Currently: 63 subscribers (up 4 in the last 3 months): - 2574 emails sent in the past 3 months (1938 in the previous cycle) - issues@camel.apache.org: - 82 subscribers (up 7 in the last 3 months): - 2526 emails sent in the past 3 months (2088 in the previous cycle) - notifications@camel.apache.org: - 8 subscribers (up 1 in the last 3 months) ## JIRA activity: - 346 JIRA tickets created in the last 3 months - 411 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache Cayenne Project [Andrus Adamchik] ## Description: Apache Cayenne is a Java 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: The project released version 3.1.1 (stable branch) to fix bugs, while continuing development on 4.0 (alpha branch). Many changes were made to 4.0 the past quarter for the Remote Object Persistence (ROP) layer of Cayenne to make it more modular and allow swapping serialization protocols. These changes will continue as ROP and other features are fleshed out for the 4.0 release. ## Health report: Cayenne is still under active development and mailing list activity indicates we have an active and stable community. ## PMC changes: - Currently 8 PMC members. - Savva Kolbachev was added to the PMC on Tue Apr 12 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. ## Releases: - Last release was 3.1.1, a maintenance release, on May 16, 2016. ## Mailing list activity: User and Developer mailing list activity has been healthy. There were many interesting and useful conversations on the User list, including many helpful responses from non-PMC/Committer members which indicates broad community interest in the project and assisting others. The Developer list hosted many robust conversations over the ROP changes and future features/changes for Cayenne Modeler. - dev@cayenne.apache.org: - 122 subscribers (up 1 in the last 3 months). - 120 emails sent to list (165 in previous quarter). - user@cayenne.apache.org: - 241 subscribers (up 0 in the last 3 months). - 189 emails sent to list (145 in previous quarter). ## JIRA activity: - 23 JIRA tickets created in the last 3 months. - 14 JIRA tickets closed/resolved in the last 3 months. ----------------------------------------- Attachment O: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have released OpenCMIS 0.14.0 (Java), which adds full Java 8 support (by switching to Apache CXF), adds a few small features, and fixes a few bugs. - We have released PortCMIS 0.1 (.NET), the successor of DotCMIS. - Apart from this, there is not much activity. ## 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 0.14.0 was released on Mon May 23 2016 - PortCMIS 0.1 was released on Fri May 27 2016 ## Mailing list activity: - dev@chemistry.apache.org: - 181 subscribers (down -1 in the last 3 months): - 126 emails sent to list (134 in previous quarter) ## JIRA activity: - 13 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment P: 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 PMC currently has a Jira ticket open with Infra to have the Github mirror `apache/cloudstack` moved to `apachecloudstack/cloudstack`. - Once the move described by the above Jira ticket is done, the ACS project will be able to better manage the implementation of our CI initiative. ## Activity: - We had a slow down in releases in the first half of this year due to not having a Release Manager. We have resolved this and we are actively working to get back to a consistent release schedule. - A CloudStack Collaboration Conference was held in Montreal from June 1-3. The event went very well and the community was engaged and supportive. Videos from the event will be published soon so the broader community who where not able to attend are able to take advantage of the content. - A CloudStack Collaboration Conference is scheduled to be hosted in Brazil on Sept 29-30, we are not aware of any ASF conflicts at this time. - We are actively reviewing some community contributed artwork for "powered by apache cloudstack". The current "powered by apache" trademark templates do not represent our brand very well, so we are reviewing some alternatives. The artwork in question is currently available here: [http://poweredbycloudstack.bitcloud.cloud/](http://poweredbycloudstack.bitcloud.cloud/) - It still remains to be seen if the Accelerite purchase of CloudPlatform from Citrix will impact the ACS community in any way. We are hopeful that the change will enable the CloudPlatform developers to more actively collaborate with the ACS project. We will remain diligent to make sure there are no conflicts of interest for the ACS project. - The Schuberg Philis fork of Apache CloudStack does not seem to be negatively affecting the ACS project in a substantial way. Their developers were very active in our community and the development process, so we definitely miss their direct contribution. They have remained relatively active in the community and have been periodically backporting bug fixes for our project. - We continue to focus on improving the CI workflow and tools available for testing the ACS software. This activity is expected to continue getting a lot of focus over the remainder of the year. - We are working to make the release cycle less dependant on a single person as release manager and are working to add more structure around the release process. - We are in the early stages of introducing an LTS release of the ACS software every 6 months to better address the enterprise use case for our software. - We are in the early stages of working out how to best publish a roadmap for the project and who is working on what. The lack of a roadmap and inconsistency in our release schedule have been hightlighted as a potential barriers for adoption of our software, so we are actively working to address these areas. ## Health report: - Committee Health score: 10.00 (Super Healthy) from reporter.apache.org - The community, in general, seems to be in concensus on the different topics we need to be focusing on as a project. Primarily testability and CI workflows, and consistency in our release schedule. The move of our `apache/cloudstack` github repository to the `apachecloudstack` github org will help us better address these areas, so we are eager for that to take place. ## PMC changes: - Currently 42 PMC members. - Rafael Weingärtner was added to the PMC on Sun Apr 24 2016 ## Committer base changes: - Currently 109 committers. - Simon Weller was added as a committer on Tue Apr 26 2016 ## Releases: - The 4.9 release is in final preparation for release - Security releases 4.5.2.1, 4.6.2.1, 4.7.1.1, 4.8.0.1 on Fri Jun 10 2016 - Latest release was 4.8.0 on Tue Jan 26 2016 - Update release was 4.7.1 on Mon Jan 25 2016 ## Mailing list activity: - The mailing list activity is stable and reflects the healthy project status. ## JIRA activity: - 103 JIRA tickets created in the last 3 months - 89 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The Apache Commons project focuses on all aspects of reusable Java components. The Apache Commons components are widely used in many projects, both within Apache and without. Any ASF committer can commit to Apache Commons. The last report was on March 16 2016. ## Issues: The Apache Commons private mailing list [1] and development list [7] have been notified that a number of Commons Math developers have forked the Commons Math component as a new project called Hipparchus [2] instead of continuing with establishing a new Apache Math TLP. Many members of the Commons project feel that the Commons PMC should make the board aware of this fact. The PMC does not request board action at this time but we welcome board input. ## Activity: - The project is active with 10 releases this reporting period, one new component being readied for release through the incubator (Commons Crypto) and one component loosing developers (Commons Math.) and having been forked (See "Issues.") ## Health report: - Most components in Commons are mature, but are still actively maintained (10 releases). We've welcomed many new committers through a new components: Apache Commons Crypto. The dev list is active. JIRA is active. Speed of responses to users is reasonable in most cases. ## PMC changes: - Currently 35 PMC members. - Stian Soiland-Reyes was added to the PMC on Wed May 18 2016 ## Committer base changes: - Currently 138 committers. - New commmitters: - Aaron Myers was added as a committer on Sat Apr 09 2016 - Benson Margulies was added as a committer on Tue Apr 12 2016 - Chris Nauroth was added as a committer on Sat Apr 09 2016 - Dian Fu was added as a committer on Sat Apr 09 2016 - Dong Chen was added as a committer on Sat Apr 09 2016 - Josh Elser was added as a committer on Fri Apr 29 2016 - Haifeng Chen was added as a committer on Sat Apr 09 2016 - Dapeng Sun was added as a committer on Sat Apr 09 2016 - Stian Soiland-Reyes was added as a committer on Fri May 20 2016 - Uma Maheswara Rao G was added as a committer on Sat Apr 09 2016 - Marcelo Masiero Vanzin was added as a committer on Sat Apr 09 2016 - Andrew Wang was added as a committer on Sat Apr 09 2016 - Ferdinand Xu was added as a committer on Sat Apr 09 2016 - Yi Liu was added as a committer on Sat Apr 09 2016 The majority of new committers have been welcomed through the Commons Crypto component. ## Releases: - COMPRESS 1.11 was released on Tue Apr 05 2016 - CONFIGURATION-2.0 was released on Wed Mar 23 2016 - CSV-1.3 was released on Sun May 08 2016 - CSV-1.4 was released on Sat May 28 2016 - FILEUPLOAD-1.3.2 was released on Wed May 25 2016 - IO 2.5 was released on Wed Apr 20 2016 - MATH-3.6.1 was released on Sun Mar 20 2016 - NET-3.5 was released on Wed May 04 2016 - VALIDATOR 1.5.1 was released on Fri Apr 29 2016 - VFS-2.1 was released on Tue May 17 2016 ## JIRA activity: - 276 JIRA tickets created in the last 3 months - 263 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache Cordova Project [Shazron Abdullah] Report from the Apache Cordova committee [Shazron Abdullah] ## Description: A platform for building native mobile applications using HTML, CSS and JavaScript. ## Issues: There are no issues requiring board attention at this time. ## Activity: We had three patch platform releases: iOS, Ubuntu and Windows. Windows had one minor platform release, version 4.4.0, which included significant improvements and features. There were also 27 plugin releases, and minor cordova-cli releases (6.1.0 and 6.2.0), which includes an improvement that allows for plugin developers to give a mapping of plugin releases to project requirements, greatly enhancing plugin compatibility for platform and cli versions. We also released an improved documentation search update on http://cordova.apache.org ## Health report: For this period, we managed two overall plugins releases (same as last quarter) when our goal was to have one plugins release per week, although we had individual plugin releases as well. We had a slight decrease (27 vs 34) of plugins that were released this quarter versus last quarter. ## PMC changes: - Currently 79 PMC members. - New PMC members: - Kerri Shotts was added to the PMC on Thu Jun 02 2016 - Sarangan Rajamanickam was added to the PMC on Sat May 28 2016 ## Committer base changes: - Currently 82 committers. - New commmitters: - Kerri Shotts was added as a committer on Fri Jun 03 2016 - Sarangan Rajamanickam was added as a committer on Sun May 29 2016 ## Releases: - cordova-common@1.1.1 was released on Wed Mar 23 2016 - cordova-common@1.2.0 was released on Wed Apr 20 2016 - cordova-common@1.3.0 was released on Mon May 23 2016 - cordova-fetch@1.0.0 was released on Mon May 23 2016 - cordova-ios@4.1.1 was released on Wed Apr 06 2016 - cordova-js@4.1.4 was released on Wed Mar 23 2016 - cordova-lib@6.1.0 was released on Wed Mar 23 2016 - cordova-lib@6.1.1 was released on Mon Apr 04 2016 - cordova-lib@6.2.0 was released on Mon May 23 2016 - cordova-plugin-battery-status@1.1.2 was released on Wed Apr 20 2016 - cordova-plugin-camera@2.1.1 was released on Fri Mar 11 2016 - cordova-plugin-camera@2.2.0 was released on Wed Apr 20 2016 - cordova-plugin-console@1.0.3 was released on Wed Apr 20 2016 - cordova-plugin-globalization@1.0.3 was released on Fri Mar 11 2016 - cordova-plugin-splashscreen@3.2.1 was released on Fri Mar 11 2016 - cordova-plugin-statusbar@2.1.2 was released on Fri Mar 11 2016 - cordova-plugman@1.2.0 was released on Wed Mar 23 2016 - cordova-ubuntu@4.3.4 was released on Tue Jun 07 2016 - cordova-windows@4.3.2 was released on Wed Apr 06 2016 - cordova-windows@4.4.0 was released on Sun Jun 05 2016 - cordova@6.1.0 was released on Wed Mar 23 2016 - cordova@6.1.1 was released on Mon Apr 04 2016 - cordova@6.2.0 was released on Mon May 23 2016 - plugman@1.2.1 was released on Mon Apr 04 2016 - plugman@1.3.0 was released on Mon May 23 2016 - cordova-plugin-contacts@2.1.0 was released on Wed Apr 20 2016 - cordova-plugin-device@1.1.2 was released on Wed Apr 20 2016 - cordova-plugin-device-motion@1.2.1 was released on Wed Apr 20 2016 - cordova-plugin-device-orientation@1.0.3 was released on Wed Apr 20 2016 - cordova-plugin-dialogs@1.2.1 was released on Wed Apr 20 2016 - cordova-plugin-file@4.2.0 was released on Wed Apr 20 2016 - cordova-plugin-file-transfer@1.5.1 was released on Wed Apr 20 2016 - cordova-plugin-geolocation@2.2.0 was released on Wed Apr 20 2016 - cordova-plugin-inappbrowser@1.4.0 was released on Wed Apr 20 2016 - cordova-plugin-media@2.3.0 was released on Wed Apr 20 2016 - cordova-plugin-media-capture@1.3.0 was released on Wed Apr 20 2016 - cordova-plugin-network-information@1.2.1 was released on Wed Apr 20 2016 - cordova-plugin-splashscreen@3.2.2 was released on Wed Apr 20 2016 - cordova-plugin-statusbar@2.1.3 was released on Wed Apr 20 2016 - cordova-plugin-test-framework@1.1.2 was released on Wed Apr 20 2016 - cordova-plugin-vibration@2.1.1 was released on Wed Apr 20 2016 - cordova-plugin-whitelist@1.2.2 was released on Wed Apr 20 2016 - cordova-plugin-wkwebview-engine@1.0.3 was released on Wed Apr 20 2016 - cordova-plugin-compat@1.0.0 was released on Wed Apr 20 2016 ## JIRA activity: - 574 JIRA tickets created in the last 3 months - 439 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment S: Report from the Apache cTAKES Project [Pei J Chen] ## Description: Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is an open-source natural language processing system for information extraction from electronic medical record clinical free-text. ## Issues: - There are no issues requiring board attention at this time ## Activity: - We have added 4 new committers this quarter. - There hasn't been as much activity for a new release yet. However, there has been a lot of 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. ## 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 on the dev and user lists. - dev@ctakes.apache.org: - 202 subscribers (up 5 in the last 3 months): - 73 emails sent to list (145 in previous quarter) - user@ctakes.apache.org: - 178 subscribers (up 6 in the last 3 months): - 38 emails sent to list (14 in previous quarter) ----------------------------------------- Attachment T: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: - The Apache Curator Java libraries make using Apache ZooKeeper much easier and more reliable. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Curator activity is normal for this period - We continue to produce releases, field questions, etc. - We are working on a new major release at this time - 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. - Curator's health is intimately tied to Apache ZooKeeper and, from our perspective, Apache ZooKeeper is a very healthy project ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Drob on Wed Jul 22 2015 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Mike Drob at Thu Jul 23 2015 ## Releases: - Last release was 2.10.0 on Sun Feb 14 2016 ## Mailing list activity: - dev@curator.apache.org: - 54 subscribers (up 4 in the last 3 months): - 472 emails sent to list (522 in previous quarter) - user@curator.apache.org: - 160 subscribers (up 5 in the last 3 months): - 55 emails sent to list (26 in previous quarter) ## JIRA activity: - 28 JIRA tickets created in the last 3 months - 21 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Etch Project [Martin Veith] Apache Etch is a cross-platform, language- and transport-independent RPC-like framework for building and consuming network services. BOARD ISSUES Proposal to move Apache Etch to attic. Awaiting boards resolution to this. RELEASES * Apache Etch 1.4.0 was released on August, 06 2014. ACTIVITY * No activity since more then one year in the SVN repository and on the user and developer mailing lists. * Started conversation on private@etch.a.o if there is an opinion against moving Etch to attic. COMMITTERS OR PMC MEMBERS CHANGE * No changes regarding PMC or committers composition since graduation in January 2013. * No changes in our committer and user base. We were able to get exactly three binding PMC votes for the last release. ----------------------------------------- Attachment V: Report from the Apache Falcon Project [Srikanth Sundarrajan] ABOUT Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. ISSUES There are no issues that require board's attention at this time. STATUS There has been active development of new features and bug fixes since the last report. Notable features include 1) Cluster updates, 2) Support for safe mode, 3) Server side extension for falcon recipes, 3) Snapshot based mirroring of HDFS 4) Instance search, 5) Hbase support for Graph, 6) Support for encrypted dirs in Mirroring. These features are part of 0.10 release, which is in the progress currently. We also moved documentation from svn to git to simplify the process of keeping documentation on site uptodate. PMC CHANGES - Currently 17 PMC members. - New PMC members: - Pallavi Rao was added to the PMC on Tue May 10 2016 - Sowmya Ramesh was added to the PMC on Mon Jun 06 2016 COMMITTER CHANGES - Currently 22 committers. - No new committers added in the last 3 months - Last committer addition was Pavan Kumar at Tue Jan 26 2016 RELEASES - 0.9 was released on Tue Feb 16 2016 - 0.8 was released on Sun Nov 15 2015 MAILING LIST ACTIVITY - dev@falcon.apache.org: - 121 subscribers (up 2 in the last 3 months): - 1431 emails sent to list (3249 in previous quarter) - issues@falcon.apache.org: - 7 subscribers (up 1 in the last 3 months) - user@falcon.apache.org: - 28 subscribers (up 2 in the last 3 months): - 0 emails sent to list (8 in previous quarter) JIRA ACTIVITY - 168 JIRA tickets created in the last 3 months - 127 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment W: Report from the Apache Felix Project [Carsten Ziegeler] Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. Community PMC: No new PMC members have been added in this report period. The last new PMC member was added in Jul. 2014. Committers: No new committers have been added in this report period. The last new committer was added in Jan. 2016. Steady mailing list activity. There are no issues requiring board attention at this time. Software Apache Felix Web Console 4.2.16 (June 3rd, 2016) SCR Tooling: Apache Felix SCR Bnd Plugin 1.5.0 released (May 28, 2016) SCR Tooling: Apache Felix Maven SCR Plugin 1.22.0, Apache Felix SCR Ant Task 1.15.0, Apache Felix SCR Annotations 1.10.0, and Apache Felix SCR Generator 1.14.0 released (May 18, 2016) Apache Felix Bundle Repository 2.0.8 and Apache Felix File Install 3.5.4 (April 4, 2016) Apache Felix Http Jetty 3.2.0, Apache Felix Http Bridge 3.0.8, Apache Felix Http Proxy 3.0.2, and Apache Felix Http Base 3.0.8 (April 1, 2016) Apache Felix Dependency Manager r8 (March 06, 2016) ----------------------------------------- Attachment X: 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.6.0 was released on 4/3/16. -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 the first of what we hope are many "Apache FlexJS World Tour" events. In early April we invited people to attend a one- day orientation and hackathon on FlexJS, a version of Flex that is independent from the Adobe Flash Platform. Many folks attended on-line as well. Some potential committers are hopefully among them. In addition, 2 PMC members attended ApacheCon NA and reported larger than expected attendance. Most activity seems to be centered around FlexJS, with the main focus being on Maven Integration, plus efforts to show that FlexJS is a more efficient way to build applications with other JS frameworks and even for building Apache Cordova apps. New capabilities like XML support and source maps have also been added. COMMUNITY -Olaf Krüger was added as a committer. -No new PMC members this quarter. -Last PMC addition was Josh Tynjala on Wed Sep 16 2015. Committers not on the PMC haven't been highly active, so we have not discussed promoting any of them to the PMC at this time. -Latest analytics include over 1000 hits per day on the website during the work week (less on weekends). -There were more than 7000 installs of Apache Flex 4.15.0 since its release in January. -There were more than 200 installs of Apache FlexJS 0.6.0 since its release in April. -Over 71,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. We have asked Trademarks@ for advice on next steps. ----------------------------------------- Attachment Y: 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 technology around Apache Hadoop and Apache Kafka. ISSUES - There are no issues that require board attention. STATUS AND ACTIVITY - Shane informed us that the "Apache Flink" trademark has been approved, but still needs to be officially issued. - Since the 1.0 release, the community growth seems to have accelerated. - As a response, the community decided to promote a "shepherd" concept within the community. Every component (like API, distributed runtime, library, ...) has one or more shepherds, which are experts of that component, and act as people to contact for issues and questions that cannot be answered by the broad community. We decided to go with the name "shepherd", rather than "maintainer", because it is a non-authoritative role, but a guiding role. Shepherds are mostly committers, but also some non-committers volunteered. This looks like a nice way to identify prospects for future committers. The shepherds should also feel responsible for driving/moderating (not deciding) the resolution of community contributions. We are still in the phase of trying this out, hope to be able to report results in the next board report. - There will be a conference on Apache Flink and Stream Processing in September called "Flink Forward" (http://flink-forward.org/). The organizers are in touch with the PMC. The program committee will be five people from the Apache stream processing ecosystem. - Flink has been integrated with more Apache projects, like BigTop (done by the Flink and BigTop community) and Mahout (mostly done by the Mahout community). - Since the 1.0 release, the community brought measures in place to check binary backwards compatibility. - So far, the Flink community has accepted the majority of contributions, such as for connectors for integration with external systems. We have, however, seen quite a few times the contributors were not interested in following up and maintaining the contribution, and a tough maintenance job was imposed on the community for barely used and unfamiliar code. As a results, there are discussions about encouraging contributors to create individual independent projects for such connectors, if there are no additional people in the community that would back the contribution. COMMUNITY There was no new PMC addition since the last report. The latest PMC addition was July 2nd, 2015 (Maximilian Michels) The latest committer addition was on March, 8th, 2016 (Greg Hogan) Flink currently has 23 committers and 16 PMC members. RELEASES The following releases were made since the last board report: - 1.0.1 was released on Tue Apr 05 2016 - 1.0.2 was released on Fri Apr 22 2016 - 1.0.3 was released on Wed May 11 2016 ACTIVITY ON JIRA / MAILING LISTS Development speed continues to be healthy. - 439 JIRA tickets created in the last 3 months - 318 JIRA tickets closed/resolved in the last 3 months Compared to previous quarters, dev mailing list activity is increasing a bit, but user mailing list activity is increasing a lot. - dev@flink.apache.org: - 381 subscribers (up 58 in the last 3 months): - 1396 emails sent to list (1176 in previous quarter) - user@flink.apache.org: - 533 subscribers (up 119 in the last 3 months): - 2211 emails sent to list (1368 in previous quarter) ----------------------------------------- Attachment Z: 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 == Some development activity fixing a git problem, Gump seems to create useful results for the few projects that use it. == 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 == We had some back and forth tweaking the git integration as we tried to make Gump pick up changes to file attributes and realized some builds had become stale. Other than that the projects that use Gump have occasionally modified their respective configuration files. === Mailing-List Statistics === general@gump.apache.org: 49 subscribers (up 2 in the last 3 months) (87 emails sent in the past 3 months, 94 in the previous cycle) commits@gump.apache.org: 22 subscribers (up 1 in the last 3 months) (41 emails sent in the past 3 months, 25 in the previous cycle) == 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 AA: Report from the Apache Helix Project [Kishore Gopalakrishna] ----------------------------------------- Attachment AB: 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: - Misuse of Apache Hive trademark by a Korean company was brought to the attention of PMC. PMC communicated to the company. They responded with their willingness to comply. PMC has conveyed further requirements for Nexr to comply with. Waiting for their response. ## Activity: - Project has raised a trademark registered request to tm-registeration@ - Project passed a resolution to change bylaw so that to commit minor patches its no longer required to get a +1 from another committer. - Project is preparing to make a 2.1 release. An RC is currently under vote. - After discussion on dev@ list, project decided to primarily support jdk8 environment. Discussion on completely dropping support for jdk7 is underway on dev@ list. - Project moved back to apache jenkins infra to trigger our unit test runs. ## Health report: - Project continues to have strong user community which is active on users@ - Project continues to receive strong contributions from various contributors. Most of the dev activity is happening in llap area. ## PMC changes: - Currently 29 PMC members. No new PMC members added in the last 3 months ## Committer base changes: - Currently 59 committers. Wei Zheng was added as a committer on Wed Mar 09 2016 ## Releases: - 2.0.1 was released on Wed May 25 2016 ## Mailing list activity: - dev@hive.apache.org: - 837 subscribers (up 18 in the last 3 months): - 1591 emails sent to list (1334 in previous quarter) - user@hive.apache.org: - 2153 subscribers (up 36 in the last 3 months): - 884 emails sent to list (1004 in previous quarter) ## JIRA activity: - 728 JIRA tickets created in the last 3 months - 558 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AC: Report from the Apache Ignite Project [Dmitriy Setrakyan] The Apache Ignite (TM) In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash technologies. Apache Ignite (TM) provides many in-memory components to improve performance and scalability of user applications, including in-memory data grid (distributed caching), in-memory compute grid, in-memory streaming, and more. ## Activity: - On 2016/05/23 the community released Ignite 1.6.0 with a big number of improvements, including ODBC support, deadlock detention, new C++ features, web console improvements, and more. - As suggested by the board, the comparison matrixes and benchmarks were removed from the Ignite website. ## Health report: - Ignite keeps attracting new contributors on the mailing list - Ignite chatroom member list continuously grows - Community added new committer, Vladisav Jelisavcic - Based on user feedback, the community has recognized the need to release more often and is currently discussing a possibility of monthly or quarterly releases ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Denis Magda on Sun Sep 27 2015 ## Committer base changes: - Currently 28 committers. - Vladisav Jelisavcic was added as a committer on Fri Jun 03 2016 ## Releases: - 1.6.0 was released on Mon May 23 2016 ## Mailing list activity: - Mailing list activity keeps growing quarter to quarter - dev@ignite.apache.org: - 187 subscribers (up 36 in the last 3 months): - 1573 emails sent in the past 3 months, 2131 in the previous cycle - issues@ignite.apache.org: - 23 subscribers (up 5 in the last 3 months): - 3769 emails sent in the past 3 months, 4799 in the previous cycle - user@ignite.apache.org: - 280 subscribers (up 59 in the last 3 months): - 2080 emails sent in the past 3 months, 1126 in the previous cycle ## JIRA activity: - 482 JIRA tickets created in the last 3 months - 352 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AD: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for June 2016 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are 56 podlings currently undergoing incubation. We have one podling planning to graduate this month and added two podlings to the roster. May was a generally quiet month, adding a single IPMC member, and completing four releases. * Community New IPMC members: - Joe Witt * New Podlings - Pony Mail - Fluo * Graduations The board has motions for the following: - Twill * Releases The following releases entered distribution during the month of May: - 2016-05-05 Apache Mynewt 0.8.0 - 2016-05-24 Apache Tephra 0.8.0 - 2016-05-24 Apache CommonsRDF 0.2.0 - 2016-05-24 Apache Mnemonic 0.1.2 * Legal / Trademarks - A comment on a recent Podling Name Search indicated that there was a desire to have PNS's come later on during incubation. Many IPMC members seem to believe that they should happen earlier. An email requesting clarification has been sent. * Infrastructure - Multiple former podlings are reporting delays in being converted to TLPs. * Miscellaneous - The CMDA podling is now 2 months behind. In response to the lack of activity, a mentor has begun retirement discussions with the podling. * Credits - Report Manager: John D. Ament -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - Fluo - Gossip - Pony Mail * Not yet ready to graduate No release: - Airflow - Gearpump - iota - log4cxx2 - Quarks - Quickstep - Streams - Toree Community growth: - Atlas - CommonsRDF - HTrace - Mnemonic - MRQL - Myriad - Omid - OpenAz - Ranger - SAMOA - Singa - Taverna - Tephra - Trafodion - Wave * Ready to graduate The Board has motions for the following: - Twill * Did not report, expected next month - Climate Model Diagnostic Analyzer (2 months) ---------------------------------------------------------------------- Table of Contents Airflow Atlas CommonsRDF Fluo Gearpump Gossip HTrace iota log4cxx2 Mnemonic MRQL Myriad Omid OpenAz Pony Mail Quarks Quickstep Ranger SAMOA Singa Streams Taverna Tephra Toree Trafodion Wave ---------------------------------------------------------------------- -------------------- Airflow Airflow is a workflow automation and scheduling system that can be used to author and manage data pipelines. Airflow has been incubating since 2016-03-31. Three most important issues to address in the move towards graduation: 1. Releases 2. Grow up user and contributor communities 3. Improve and extend documentation and samples on the website Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? * Since our last podling report 1 month ago, we grew our contributors from 137 to 148 * Since our last podling report 1 month ago, we accepted/merged 51 PRs * We voted on the following matters according to Apache guidelines: * We voted to make all current and future committers part of the PPMC * We voted in a new committer and PPMC member : Steven Yvinec-Kruyk and he accepted * We voted in a commit policy of "RTC with a +1 vote from a committer other than the author (assuming no vetos)" How has the project developed since the last report? * All resources have been created and all migrations are complete - code donation included * The website is in progress Date of last release: N/A - we are still working out releases as we are new to Apache. When were the last committers or PMC members elected? On May 20, 1 committer/PPMC member(Steven Yvinec-Kruyk) was elected and he accepted. Signed-off-by: [X](airflow) Chris Nauroth [x](airflow) Hitesh Shah [x](airflow) Jakob Homan -------------------- 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. 2. Expand the community and add more committers. 3. The upcoming release for Atlas (0.7-incubating) will be nearly 6 months since the last one. We would like to improve on this by making more frequent releases, and also encourage the community to discuss in release roadmaps etc. 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. The user/dev community show increasing interests. In the last two months, the average number of messages has increased to more than 900 messages per month, from an average of 400 per month in the last report. 2. Around 7 contributors were added, number of contributors is at 49 currently. Community is more widespread with more organizations participating in the project. How has the project developed since the last report? 1. We are working towards a 0.7-incubating release around the next month. This release will include several new features to make Atlas enterprise ready including: Authentication and authorization support, High availability, deeper integrations with other Hadoop components including Hive, HDFS, Falcon etc., Entity versioning, support for rolling upgrade, support for creating business taxonomies, enhanced user interface, better performance etc. 2. There are more strategic contributions coming in to make the system agnostic to the underlying graph database version, and improve horizontal scalability. 3. A total of 216 issues were reported between April 1st 2016 and May 30th 2016. 84 have been resolved in the same time. Date of last release: 2015-12-31 - 0.6-incubating When were the last committers or PMC members elected? 1. Suma Shivaprasad was added as a PPMC member on 2016-05-03. 2. Hemanth Yamijala was added as a committer on 2016-04-14 and PPMC member on 2016-04-29. Signed-off-by: [ ](atlas) Arun Murthy [x](atlas) Chris Douglas [x](atlas) Jakob Homan [ ](atlas) Vinod Kumar Vavilapalli -------------------- CommonsRDF Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and behaviours. The commons-rdf-api module defines interfaces and testing harness. The commons-rdf-simple module provides a basic reference implementation to exercise the test harness and clarify API contracts. CommonsRDF has been incubating since 2015-03-06. Three most important issues to address in the move towards graduation: 1. Find concrete target goals that could make the project viable as a Commons component. 2. Work with key target communities (Apache Jena and Eclipse RDF4J) to ensure Commons RDF meets potential user requirements and expectations towards next versions of the Commons API. 3. Re-engage and grow the Commons RDF community base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? More key people (Andy Seaborne this time) has left the podling due lack of time. Mentor Rob Vesse has also resigned for the same reason. How has the community developed since the last report? Community have been compacted with the lost of some key people. We still aim to attract a more broader RDF community, both in and out of ASF. Mailing list stats: dev@commonsrdf traffic Mar 2016: 45 Apr 2016: 75 May 2016: 18 Jira stats for last 90 days: Created: 7 Resolved: 6 How has the project developed since the last report? Project's development has resumed the work in the last weeks, being able to cast a 0.2.0-incubating release https://s.apache.org/rd0E Achieving such milestone has reactivated the discussion about the future of the project. All options have been put on the table, even retiring the podling; but currently the most likely option looks to be graduating as a Apache Commons component. Rather than the original plan of aiming for each RDF frameworks to adapt Commons RDF, the project is now experimenting with its own integration bindings in the style of Commons VFS. Discussions will continue in the next weeks. Date of last release: 2016-05-24 apache-commonsrdf-0.2.0-incubating When were the last committers or PMC members elected? None Signed-off-by: [X](commonsrdf) John D Ament [X](commonsrdf) Gary Gregory -------------------- Fluo Fluo is a distributed system for incrementally processing large data sets stored in Accumulo. Fluo has been incubating since 2016-05-17. Three most important issues to address in the move towards graduation: 1. Attract new contributors. 2. Establish an Apache website for Fluo that makes it easy for new users and contributors to get started. 3. Do a release. We should be able to start working on our first release as soon as we are fully established on Apache infrastructure Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? The community is the same as when it started incubation a few weeks ago. How has the project developed since the last report? This is the first Fluo report. We are trying to get established within Apache infrastructure. Mailing lists are setup. Need to import code. We are working with INFRA to explore using Github for issue tracking. See INFRA-11900. Date of last release: Never When were the last committers or PMC members elected? Never Signed-off-by: [X](fluo) Billie Rinaldi [X](fluo) Drew Farris [X](fluo) Josh Elser Shepherd/Mentor notes: John Elser: Not much to report here. Podling members are working with INFRA to get the existing codebase+issue tracker content ported. Still spinning up. -------------------- 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 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? - Good discussion on dev mailing list related to features, bugs and logo - Increased participation and interest from developers to provide new sources and examples How has the project developed since the last report? - Package renaming completed. - New logos submitted - reasonable number to finally vote on. - Continued integration within Apache Beam (Gearpump Runner). PR submitted. - Continued integration within akka-streams (Gearpump Materializer). PR submitted. - Release pending this month. Over a dozen JIRA's fixed. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members elected yet. Signed-off-by: [X](gearpump) Andrew Purtell [ ](gearpump) Jarek Jarcec Cecho [ ](gearpump) Reynold Xin [ ](gearpump) Todd Lipcon [ ](gearpump) Xuefu Zhang Shepherd/Mentor notes: Drew Farris (shepherd): One mentor active on the user/dev lists. Healthy activity on mailing lists commits, moving toward first apache release. -------------------- Gossip Gossip is a system to form peer-to-peer networks using the gossip protocol Gossip has been incubating since 2016-05. Three most important issues to address in the move towards graduation: 1. Establish an Apache website for Gossip that makes it easy for new users and contributors to get started. 2. Facilitate discussions and build the protocol specification and implementation 3. Produce a usable release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? The community is the same as when it started incubation a few weeks ago. How has the project developed since the last report? This is our first report. We have imported the code from github. We are online. We have had good discussions on the dev list that have spawned a couple of tickets. One is in the review stage now. Taylor has been an enormous help. Date of last release: Never When were the last committers or PMC members elected? Never Signed-off-by: [X](gossip) P. Taylor Goetz [x](gossip) Josh Elser [X](gossip) Sean Busbey Shepherd/Mentor notes: Sean Busbey: Community def still bootstrapping, but has done a good job of making progress once infra was in place. -------------------- HTrace HTrace is a tracing framework intended for use with distributed systems written in java. HTrace has been incubating since 2014-11-11. Three most important issues to address in the move towards graduation: 1. Continue to grow the HTrace community 2. Continue to explore projects integrating HTrace 3. Continue to develop and release stable HTrace incubating artifacts Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There are no issues requiring board attention at this time. How has the community developed since the last report? * GSoC student, Nisala Mendis, mentored by Colin McCabe working on making an Apache Kudu (incubating) SpanReceiver How has the project developed since the last report? * 18 issues resolved since last report * YCSB integrated HTrace Date of last release: * htrace-4.1.0-incubating on March 5th, 2016 When were the last committers or PMC members elected? * None this period. Last added committer: Abraham Elmahrek - 2.11.15 Signed-off-by: [X](htrace) Jake Farrell [ ](htrace) Todd Lipcon [ ](htrace) Lewis John Mcgibbney [ ](htrace) Andrew Purtell [X](htrace) Billie Rinaldi [x](htrace) Michael Stack -------------------- iota Open source system that enables the orchestration of IoT devices. iota has been incubating since 2016-01-20. Three most important issues to address in the move towards graduation: 1. Complete code upload 2. Continue discussion on requirements started by Anatole Tresch 3. Need to add additional committer (Barbara Gomes) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Presentation at ApacheCon 2016 - good suggestions from Anatole Tresch in moving iota forward. Have additional potential committer How has the project developed since the last report? Code is now being uploaded as well as requirements documents Date of last release: None When were the last committers or PMC members elected? None Signed-off-by: [ ](iota) Daniel Gruno [ ](iota) Sterling Hughes [X](iota) Justin Mclean [ ](iota) Hadrian Zbarcea Shepherd/Mentor notes: Justin Mclean (jmclean): Slow start and still low activity on mailing list. Web site now has content and there is some code in git. IMO keep on monthly reports until that changes. -------------------- log4cxx2 Logging for C++ 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. The project would like to have some kind of maintenance mode within Apache, where things like community growth and releases are not that important, as long there's a bit of support provided and "anyone" is still alive. The problem with attic is the read-only state of the repo, which makes it impossible to do anything (even if it's rare). How has the community developed since the last report? Not grown and only a few mails on the dev list in the last two months. No support requests the last two months. Bill Rowe stepped in as a mentor. How has the project developed since the last report? The build process using autotools on Linux has been fixed and there was a discussion about supported build tools, because currently the project heavily relies on the unsupported cpptasks framework. While there was no actual result, the common focus was on dropping cpptasks and ANT for the build of the software and use autoconf and/or cmake instead. Additionally, one project member was willing to make himself more familiar with the release process, but there was no progress reported in the last month. 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: I have explained that there is no "maintenance mode" for a standalone project. However, if the project can demonstrate that it can produce a release and has enough people to maintain the project then it can rejoin the logging project where it can essentially exist in maintenance mode much like log4php is. The project moved to the incubator because there were people who said they wanted to get involved with the project and were willing to get involved. To date, one person has been actively involved but not enough to produce a release. One other person was involve in a discussion on the release process. -------------------- Mnemonic Mnemonic is a Java based non-volatile memory library for in-place structured data processing and computing. Mnemonic has been incubating since 2016-03-03. On 05/24/2016, we released our first official build at https://dist.apache.org/repos/dist/release/incubator/mnemonic/0.1.2-incubating/ Various metrics for May are as follows: (5/3-5/31/2016) +------------------------------------------+ | Metric | counts | +------------------------------------------+ | Non Merge Commits | 23 | | Contributors | 3 | | Jira New Issues | 18 | | Resolved Issues | 18 | | Pull Requests merged | 0 | | Pull Requests proposed | 0 | +------------------------------------------+ Three most important issues to address in the move towards graduation: 1. Apache releases: Community voted and released Mnemonic-0.1.2-incubating 2. Expand and build strong community, keep active dev list discussions 3. Develop new features: We are working in Native computing layer design 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? Yanping and Gary presented Mnemonic project at ApacheCon Big Data Conference. Yanping presented at In-Memory Computing Summit. Both talks were well received. Several developers approached us to ask additional details on how Mnemonic worked for Spark. They are interested to see if we are able to successfully integrate Mnemonic into other projects. While we are focusing on develop new features, we will try to contact other projects' communities to explore integration opportunities. As the official release is done this month, for the next 3 months we expect integration activities will be increased. How has the project developed since the last report? We have been focusing the first Apache release over the past weeks. We also explored ideas on design native computing layer which will further enhance durable Java object model on large non-volatile memory. Date of last release: 2016-05-24 When were the last committers or PMC members elected? No election, the project is still in early stage of developing. Signed-off-by: [X](mnemonic) Patrick Hunt [X](mnemonic) Andrew Purtell [ ](mnemonic) James Taylor [ ](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 were no new developers or new committers since our last report. How has the project developed since the last report? We had a new release on March 2nd. It included various bug fixes and performance improvements. The most important new feature in the new release is support for incremental query processing in MRQL streaming, called Incremental MRQL. There was very little activity on JIRA after the release (only 4 JIRA issues were reported and fixed). Date of last release: 2016-03-02 When were the last committers or PMC members elected? 2014-04-17 Signed-off-by: [ ](mrql) Alan Cabrera [x](mrql) Edward J. Yoon [ ](mrql) Mohammad Nour El-Din -------------------- 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. Develop project roadmap for longer term community/user engagement. 2. Release frequently - 0.2.0 is underway, but has taken ~6 months since last release. 3. Expand community - users/contributors/committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? * dev@ mailing list experienced a low in March, but picked up traffic leading up to 0.2.0 release. 141 messages since the last report. * 5 new members on the dev@ mailing list. 2 new contributors. * Myriad was presented at ApacheCon Vancouver and at couple of other meetups. Talks submitted at various conferences. * Bi-weekly dev syncs happening steadily. Approx. 4-7 members participate. Minutes at http://s.apache.org/8kF How has the project developed since the last report? * Myriad 0.2.0 out for PPMC voting. DarinJ is driving the release. * 12 commits since 4/1. * 13 JIRAs fixed/resolved. Date of last release: 2015-12-09 myriad-0.1.0-incubating released When were the last committers or PMC members elected? 2015-10-05 Darin J 2015-10-14 Swapnil Daingade Signed-off-by: [ ](myriad) Benjamin Hindman [ ](myriad) Danese Cooper [X](myriad) Ted Dunning [x](myriad) Luciano Resende Shepherd/Mentor notes: Ted Dunning: Seems kind of low activity, but with dedicated cadre. -------------------- 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. Code and documentation successfully moved into the Apache infrastructure (See https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git & http://omid.incubator.apache.org/) 2. Prepared release guide (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+process), first release (0.8.2) under Apache (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+0.8.2.0) and upload binaries to Maven Central 3. Active collaboration started with another Apache community: Apache Hive 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? * Talk submitted to Hadoop Summit. It was accepted and will be presented on 2016-06-29 * The Hive community is using Omid to integrate with HBase for their metastore requirements * First contact with the Apache Phoenix community for a possible integration of Omid as a transaction manager for the SQL layer Phoenix provides * Quarter Stats (from: 2016-05-17 -project moved into Apache- to: 2016-06-03): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 303 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 27 | | Resolved Issues | 31 | | Pull Requests merged | 9 | | Pull Requests proposed | 12 | +---------------------------------------------+ How has the project developed since the last report? N/A, this is the first report since joining the Apache Incubation program Date of last release: 2016-06-06 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [x](omid) Daniel Dai (Champion) [X](omid) Alan Gates [ ](omid) Lars Hofhansl [X](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [ ](omid) James Taylor -------------------- OpenAz OpenAz OpenAz is a project to create tools and libraries to enable the development of Attribute-based Access Control (ABAC) Systems in a variety of languages. In general the work is at least consistent with or actually conforming to the OASIS XACML Standard. OpenAZ has been incubating since 01-2015. Three most important issues to address in the move towards graduation: 1. Increasing community involvement: We are focusing on getting information published on the website to aid the acquisition and orientation of new contributors, as well increasing the number of committers, in order to reduce individual member workload, reduce reliance on any particular member, and to increase project velocity. David Ash was voted in as a committer last month. There are several other committers that may be added in the near future. 2. Merging the source code from AT&T, JP Morgan and Oracle and creating POMs. AT&T and JP Morgan source code has been merged and POMs created, it needs uploading into the Apache repository. AT&T and JP Morgan ICLAs were received, but Oracle is taking more time. The IP clearance is on it's way. 3. Get our first release done. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. The efforts to revive the project seem to be paying off and discussions are gaining traction. How has the community developed since the last report? Pam Dragosh, David Ash and Ajith Nair are the active committers at this point. The project intends to reboot the PPMC which may include removing some of the initial commiters who are no longer active. There are, however, several contributors who could be potentially added as committers in the future. How has the project developed since the last report? 1. Ongoing collective effort to improve project documentation, marketing material for better visbility and adoption. 2. A pending contribution towards PEP implementation is being reviewed and we plan to merge in these changes soon. 3. We are looking into design feedback/comments from Nextlabs - a XACML service provider. We hope to incorporate many of these in the coming weeks. Date of last release: N/A When were the last committers or PMC members elected? One new committer, David Ash, was elected Tuesday, May 3rd. Signed-off-by: [x](openaz) Emmanuel Lecharny [x](openaz) Colm O Heigeartaigh [ ](openaz) Hadrian Zbarcea Shepherd/Mentor notes: Emmanuel Lecharny: This is encouraging ! I'm very pleased with what happened in the past last weeks, with some new committer voted in, and some increasing activity going on. -------------------- 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. Teach newcomers the Apache Way 3. Build towards the first release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at present. How has the community developed since the last report? Just getting started with bootstrapping the podling. Mailing lists have been set up, temporary web site and code repositories ditto. We are working on onboarding the new non-Apache committers in the community and having people familiarize themselves with the project. How has the project developed since the last report? N/A Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? No new committers have been elected just yet, as we just got started. Signed-off-by: [ ](ponymail) Andrew Bayer [X](ponymail) John D Ament -------------------- Quarks Apache Quarks is a programming model and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Quarks provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge. Quarks has been incubating since 2016-02-29. Three most important issues to address in the move towards graduation: 1. Create and expand a diverse community of contributors and committers around Quarks project 2. Create the first Apache release of Quarks 3. Complete the product name search and select a suitable name Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Due to trademark concerns with "Quarks", the Quarks PPMC voted to change the project's name. A renaming discussion and public vote was held on the dev mailing list. The voting results are being discussed privately by the PPMC. How has the community developed since the last report? We have added two new committers and PPMC members, Kathy Saunders and Queenie Ma. Kathy has taken the lead on the name search process for Quarks, and her positive attitude and helpfulness are an incredible asset for the Quarks community. Queenie has contributed content to the website and is a frequent participant in community discussions. The Quarks community is still small, as Quarks has just recently incubated, therefore we aim to continue growing our list in the near future. How has the project developed since the last report? * According to JIRA, the project has added 27 new issues in May, and 22 issues have been resolved. * On May 12, several Quarks contributors hosted an "Apache Quarks on Raspberry Pi" webcast where they showed how to use Quarks to work with real sensor data on a Raspberry Pi, and demonstrated a smart sprinkler application using Quarks. Date of last release: Quarks is still new, so we haven't created an Apache release as of yet. When were the last committers or PMC members elected? In May, we added two new committers and PPMC members, Kathy Saunders and Queenie Ma. Signed-off-by: [ ](quarks) Daniel Debrunner [x](quarks) Luciano Resende [X](quarks) Katherine Marsden [X](quarks) Justin Mclean -------------------- Quickstep Quickstep is a high-performance data processing platform that aims to fully exploit the vast and increasing amount of parallelism that is packed in individual nodes. The project’s initial target is interactive in-memory data warehousing workloads, and early results indicate that Quickstep is over an order-of-magnitude faster than existing platforms including Spark 2.0 and PostgreSQL 9.6 Beta1. Quickstep has been incubating since 2016-03-29. Three most important issues to address in the move towards graduation: 1. Acquire early adopters 2. Build a community. 3. Create an ASF release. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? We were incubated into Apache recently, and the developers are actively learning about the Apache way from our mentors. How has the project developed since the last report? We have fully transitioned to the ASF for all development work. Date of last release: No release yet. When were the last committers or PMC members elected? N/A Signed-off-by: [ ](quickstep) Konstantin Boudnik [x](quickstep) Julian Hyde [x](quickstep) Roman Shaposhnik Shepherd/Mentor notes: Julian Hyde (jhyde): Getting development onto ASF git took a while, but I think we're there. I'll work with the project to refine the "Acquire early adopters" goal into more concrete outreach steps. Roman Shaposhnik (rvs): Really, at least goal #2 should be "make a first ASF release". Hopefully we can work with the community to get a sense how important it is in addition to growing a community (all 3 goals in this report). -------------------- Ranger The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform. Ranger has been incubating since 2014-07-24. Three most important issues to address in the move towards graduation: 1. Increase the community participants for Apache Ranger 2. Re-organize documentation for easier access to end-users, new users and contributors. 3. Integration of Apache Ranger with other Apache Initiatives Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 1. Mailing list activity since last report (April-01-2016 to May-31-2016): @dev 1090 @user 118 @commit 174 2. Issues (JIRAs) created/resolved since last report (after April-01-2016 before Mar-31-2016): Created: 94 Resolved: 92 How has the project developed since the last report? 1. Released one minor releases : 0.5.3 released on 05/31/2016 2. Members have been working on a next major release of 0.6.0 a. Working on fixing bugs in the current 0.6.0 features Date of last release: May-31-2016 When were the last committers or PMC members elected? 1. Colm O hEigeartaigh has been added as committer on April 19, 2016 Signed-off-by: [X](ranger) Alan Gates [ ](ranger) Daniel Gruno [ ](ranger) Devaraj Das [x](ranger) Jakob Homan [ ](ranger) Owen O'Malley -------------------- SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache Flink, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Grow the community 2. Elect new PMC members 3. Release more often Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Mailing list activity (March 2016 - May 2016): * @dev: 202 messages Jira issues backlog (March 2016 - May 2016): * Created: 3 * Resolved: 9 We have a number of new users showing up on the mailing list, which is encouraging. How has the project developed since the last report? After the decision taken by the community to drop support for S4, we removed the support for S4. We fixed automatic build issues, we simplified input from HDFS, and we worked on adding support for Apache Gearpump. Two talks were given to advertise Apache SAMOA, one at ApacheCon NA Big Data by Nicolas Kourtellis, and another one at the "J on the beach" conference by Albert Bifet. Date of last release: 2015-07-21 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: I sent a mail to the community poking on the long wait since the last release and whether they think there will be a release soon. I also expressed my concern on not having added any committers and asked if there were any contributors who looked like they might be a good candidate for committership. -------------------- 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. Grow the community. We anticipate stronger growth of the community when the upcoming, major release (v1.0) is available. SINGA v1.0 will have new programming abstractions and be able to run on heterogeneous hardware (e.g., using Cuda and OpenCL). It will also have improved usability in terms of installation and training new models, etc (see details below). 2. Clean and improve existing documentations. We plan to replace the website template with a better one. 3. Focus on Rafiki --- SINGA-based deep learning as a service. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? The Github repository has scored 602 stars and 205 forks. There were 107, 73 and 37 emails from dev@ list in March 2016, April 2016 and May 2016 respectively. There were 9, 35, and 30 commits in March 2016, April 2016 and May 2016. How has the project developed since the last report? In April 2016, we released our third version, i.e. v0.3.0, with the following major features: * Training on GPU cluster * Python wrapper improvements * New SGD updaters * Remove several dependencies for single node training. * Heterogeneous training with CPU and GPU. * Support cuDNNv4. In May, we started working on the first major release (v1.0) with the following notable features(http://singa.apache.org/develop/schedule.html): * Cross-platform * Support heterogeneous hardware: CUDA, OpenCL * Enhance programming abstraction, focusing on Tensor as core abstraction. * Python binding, cloud integration (Spark, Hadoop, etc.) * Runtime optimization. We are working on a system called Rafiki which uses SINGA to provide deep learning as a service and has the following features: * Sharing of pre-training models * Visualizing training progress * Configuring model via GUI (web browsers) Date of last release: 2016-04-20 When were the last committers or PMC members elected? N/A Signed-off-by: [ ](singa) Daniel Dai [X](singa) Alan Gates [X](singa) Ted Dunning [ ](singa) Thejas Nair Shepherd/Mentor notes: Alan Gates: I sent an email to the community sharing my concerns about the slow progress of adding new committers and asking if they had any contributors that looked like they might be ready for committership. Ted Dunning: The trend in dev mailing list traffic is worrisome as well. The opposite trend in JIRA volume is curious. -------------------- 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? # of contributors submitting and reviewing pull requests and participating in discussions is still too low. Getting the attention of developers who work with social datasets and highlighting the ways that adopting and contributing to streams could provide value for their projects remains our biggest challenge and opportunity in community growth. How has the community developed since the last report? Several recently in-active project contributors participated again this quarter. How has the project developed since the last report? http://streams.incubator.apache.org has been completely overhauled, and following several talks given at ApacheCon NA 2016, a new blog post, and a renewed focus on marketing we’re beginning to see a payoff in the form of a consistent level of unique visitors, according to google analytics. 25 Issues resolved + 4 Issues resolved by open pull requests Date of last release: 2015-04-26 When were the last committers or PMC members elected? 2015-02-23: Robert Douglas elected as committer / PMC member Signed-off-by: [ ](streams) Matt Franklin [X](streams) Ate Douma [ ](streams) Craig McClanahan -------------------- 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. Releasing main code base (RC under vote) 3. Engaging user/devops community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? ASF guidance on US export ECCN cryptography registration https://www.apache.org/dev/crypto.html has not yet been updated for the 2010 rule changes, confusion around this classification caused Taverna delays. Lack of active mentors - would appreciate another volunteer. How has the community developed since the last report? Two new GSOC students now active. 2-3 other new potential contributors discussing new work. A total of 4 ICLAs registered - however these folks need further encouragement and guidance to submit regular pull requests. dev@taverna mailing lists stats: Mar 2016: 312 Apr 2016: 102 May 2015: 184 users@taverna: Mar 2016: 12 Apr 2016: 6 May 2015: 1 JIRA issues over last 90 days: 49 created 25 resolved How has the project developed since the last report? Preparations for release of the main workflow engine has had focus, including build stability across platforms, documentation update and US Export classifications of encryption items (which caused some delays). Taverna Engine/Command Line Release candidate now under vote. https://lists.apache.org/thread.html/Zpt11soyc7qf2so Traffic on users@ show interest mainly on Taverna Server, so this component should probably be the development focus after GSOC. Date of last release: 2016-03-11 taverna-osgi-0.2.1-incubating 2016-03-11 taverna-language-0.15.1-incubating Currently in [VOTE]: taverna-engine, taverna-common-activities, taverna-commandline https://lists.apache.org/thread.html/Zpt11soyc7qf2so When were the last committers or PMC members elected? 2015-12-04 Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Daniel J Debrunner [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne: There is still a lack of active mentors. I'm dipping in when I can. Drew Farris (shepherd): Little mentor activity on the mailing lists, could use another active mentor. Healthy activity in the community. -------------------- 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. Complete project setup 2. Regular releases 3. Improve community engagement 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? 1) Apache Tephra now powers ACID transactions in Apache Phoenix (since v4.7.0). 2) We presented Apache Tephra as a part of the Apache Phoenix talk at HBaseCon 2016. 3) We also presented a more elaborate version of the above talk at PhoenixCon 2016. 4) We are making progress towards setting up of Project page. How has the project developed since the last report? 1) We had our first release (0.8.0-incubating) since incubation. 2) We have added support for Apache HBase v1.2 in the latest release (0.8.0-incubating). Date of last release: 2016-05-31 When were the last committers or PMC members elected? None since the May 2016 report Signed-off-by: [X](tephra) Alan Gates [X](tephra) Andrew Purtell [ ](tephra) Henry Saputra [X](tephra) James Taylor [ ](tephra) Lars Hofhansl -------------------- Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. It enables interactive workloads between applications and a Spark cluster. As a Jupyter Notebook extension, it provides the user with a preconfigured environment for interacting with Spark using Scala, Python, R or SQL. Toree has been incubating since 2015-12-02. Three most important issues to address in the move towards graduation: 1. Resolve LGPL dependency: This is in progress, and hopefully we will have the dependency license changed to a license that is compatible with AL2. 2. Make a release: nearing completion 3. Grow a diverse community: We should put some emphasis on growing the community and making it diverse (the rule is at least three independent contributors) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? TOREE-262 - Progress on removal of LGPL dependency How has the community developed since the last report? 1. Active communication in mailing list and gitter with early adopters 2. Still working on transitioning users from Spark Kernel project into Toree. 3. More external contributions being made How has the project developed since the last report? 1. Contrinue working with JeroMQ community to further their transition into MPL v2 and away from LGPL. 3 committers to go. 2. Substantial effort in our build system to make Apache compliant releases. 3. Addressing issues opened by community Date of last release: None since incubation. When were the last committers or PMC members elected? No new additions since incubation Signed-off-by: [x](toree) Luciano Resende [ ](toree) Reynold Xin [x](toree) Hitesh Shah [ ](toree) Julien Le Dem -------------------- 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. Finish our second release, including convenience binaries and support for Apache HBase 1.x without a commercial distribution. 3. Continue the momentum and become more integrated with the rest of the Apache 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? * Participation in public lists has been steady: 722 messages in the codereview forum, 1045@commits, 689@dev, 1294@issues and 240@user. * Upcoming release 2.0 was verified by several new users. * Release 2.0 is being actively discussed in the dev forum. How has the project developed since the last report? * For our second release in incubation, Trafodion 2.0 release candidate 3 has passed an internal vote. It was submitted for a vote in the incubator PMC on May 31. Many thanks go to Steve Varnau, the release manager! * Added documentation in form of HTML and PDF manuals. * 314 commits from 28 contributors. * 171 JIRAs filed and 165 resolved in the last three months. Date of last release: 2016-01-11 1.3.0 When were the last committers or PMC members elected? RuoYu Zuo was announced as a new committer in February. The last PMC members were announced in November 2015. We expect to add an additional committer soon. 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? - We had a few discussions regarding technical developments. How has the project developed since the last report? - Made some code improvements - Introduced GitHub based pull requests as accepted way for change submissions. 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: Wave is a slow moving, but functioning, project. It needs to attract additional developers to focus on attracting new developers in order to be able to exit the incubator. ----------------------------------------- Attachment AE: Report from the Apache Jackrabbit Project [Michael Dürig] Report from the Apache Jackrabbit committee [Michael Dürig] June 2016 ## 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 Oak sub-project is an effort to implement a scalable and performant hierarchical content repository for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to the initial implementation Oak does not implement all optional features from the JSRs and 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 high activity. This quarter saw the third major release of Oak (1.4). Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. A XSS vulnerability was discoverd and fixed. See * https://issues.apache.org/jira/browse/JCR-3950 * https://mail-search.apache.org/pmc/private-arch/jackrabbit-private/ 201602.mbox/%3C56C8B688.3000703@apache.org%3E * ## 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 high as we just entered a new release cycle. The oak-dev list is seeing some interesting and controversial discussions. ## PMC changes: - Currently 49 PMC members. - Tomek Rękawek was added to the PMC on Mon Mar 21 2016 ## Committer base changes: - Currently 49 committers. - Tomasz Rekawek was added as a committer on Mon Mar 21 2016 ## Releases: - oak-1.0.29 was released on Tue Mar 22 2016 - oak-1.0.30 was released on Thu Apr 21 2016 - oak-1.0.31 was released on Wed Jun 01 2016 - oak-1.2.13 was released on Wed Mar 23 2016 - oak-1.2.14 was released on Wed Apr 20 2016 - oak-1.2.15 was released on Mon May 16 2016 - oak-1.4.1 was released on Thu Mar 24 2016 - oak-1.4.2 was released on Tue May 03 2016 - oak-1.4.3 was released on Tue May 31 2016 - oak-1.5.0 was released on Tue Mar 29 2016 - oak-1.5.1 was released on Mon Apr 11 2016 - oak-1.5.2 was released on Fri May 13 2016 - jackrabbit-2.10.2 was released on Wed Mar 23 2016 - jackrabbit-2.10.3 was released on Mon May 09 2016 ## JIRA activity: - 376 JIRA tickets created in the last 3 months - 301 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AF: Report from the Apache Johnzon Project [Hendrik Saly] ## Project description Apache Johnzon is an implementation of JSR-353 (JavaTM API for JSON Processing) and a set of useful extension for this specification like an Object mapper, some JAX-RS providers and websocket (JSR-356) integration. ## Issues There is one outstanding infrastructure INFRA-11764 which covers the cleanup and the transition from the incubator to a TPL: https://issues.apache.org/jira/browse/INFRA-11758 No one cares about it so I would kindly ask the Board to take action here. This ticket is also blocking us from the next release. ## Status Currently in the process of performing the graduation out of the incubator. There is ongoing work to make Johnzon JSR-367 (JSON-B) compliant. Its also planned to implement JSR-374 (JSON-P 1.1), the successor of JSR-353. ## Releases Johnzon graduated from the Apache Incubator on April 20, 2016. Last release was on Feb. 17, 2016 (0.9.3-incubating). No new release since then. Next planned release: 0.9.5 in June 2016. ## Committers and PMC membership The last committer we signed up was Reinhard Sandtner on April 12, 2016. The last PMC member was Hendrik Saly, voted in on April 9, 2015. ## Project activity Since the last report (submitted last month) there was middle activity. We had 8 new Jira issues and fixed 5 of them. On the mailing list there are no unanswered questions left. On the dev list we have 28 subscribers currently and 10 msg sent per week last month in average. Since last report we saw mailing list activity from two new people and also Jira issues from new contributors. ----------------------------------------- Attachment AG: 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: January 21, 2016 Last PMC addition: September 05, 2012 Talks related to Karaf have been given during ApacheCon NA Vancouver: - Tutorial: Apache Karaf and OSGi Basics - Tom Barber - Messaging for the cloud with ActiveMQ and Karaf - Hadrian Zbarcea & Jamie Goodyear - Focus on business code with Apache Karaf Boot - Jean-Baptiste Onofré - Monitoring and alerting with Apache Karaf Decanter - Jean-Baptiste Onofré Messages on the dev mailing list during last 3 months: 374 Messages on the user mailing list during last 3 months: 694 Development =========== The following new releases have been voted: - 4.0.5 was released on Sat Apr 16 2016 - decanter 1.1.0 was released on Tue Apr 26 2016 We are preparing new releases and the new karaf-boot subproject. - 152 JIRA tickets created in the last 3 months - 114 JIRA tickets closed/resolved in the last 3 months Issues for board consideration ============================== None so far. ----------------------------------------- Attachment AH: Report from the Apache Labs Project [Danny Angus] ## Description Apache Labs hosts small and emerging projects from ASF committers. ## Activity Labs activity is virtually nonexistent. Since being elected as PMC chair I have had to handle more spam email to the lists than actual correspondence of any kind. I'm not aware of any commits, there are no new proposals, and I don't know how to find the mailing list subscriber stats, but I would be surprised if it had changed. ## Issues I have put some questions to the community about the future of the project and had a handful of responses, it seems from that small sample that there is some consensus around the idea that labs no longer fills a valuable purpose at the ASF. There are then options as to how we proceed, basically we can vote to shut labs down, we can accept the status quo or we can attempt to pivot labs until it becomes relevant. During the next reporting period we will work on determining a way ahead, in the meantime we would be grateful for any guidance the board may wish to provide. (N.B. I'm afriad I will be travelling at the time of this meeting and will be unable to attend.) ## PMC/Committership changes: New PMC Chair (danny) since the last board report. ## Releases The project does not make releases per definition. ----------------------------------------- Attachment AI: Report from the Apache Lucene Project [Michael McCandless] ## Description: - Lucene Core is a search-engine toolkit - Solr is a search server built on top of Lucene Core ## Activity: - The community is very active - We have submitted a resolution to change the PMC Chair from Mike McCandless to Tommaso Teofili ## Issues: - There are no new issues requiring board attention at this time ## PMC/Committership changes: - Currently 62 committers and 38 PMC members in the project - Added 3 new committers: - Kevin Risden was added as a committer on Tue Mar 15 2016 - Karl Wright was added as a committer on Mon Apr 04 2016 - Scott Blum was added as a committer on Wed Apr 20 2016 - Added no new PMC members ## Releases: - 6.0.0 was released on April 8, 2016 - 5.5.1 was released on May 5, 2016 - 6.0.1 was released on May 28, 2016 - 6.1.0 release will get started (release branch) around June 8 ## Mailing list activity: - Mailing lists remain active and healthy ## JIRA activity: - Jira activity remains active and healthy ----------------------------------------- Attachment AJ: 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 looking at releasing nuget packages for 4.8.0 Beta * We continue to see strong community support - looking at adding new committers soon * Efforts are under way to make Lucene.Net into a Portal Common Library (PCL), to work across all devices that support .NET == Releases == * Last Release 3.0.3 - Oct 2012 Working toward 4.8.0 == Statistics == * Last PMC Member Added, Paul Irwin, October 2013 * Two committers added Jan '15 -Laimonas, Feb '15 - Wyatt Nuget package downloads: * Lucene.Net 3.0.3: 308,623 (up from 278,843) * Lucene.Net.Contrib 3.0.3: 83,361 (up from 75,128) * Lucene.Net Contrib Spatial: 9,734 (up from 9,221) * Lucene.Net Contrib Spatial.NTS: 1,841 (up from 1,749) ----------------------------------------- Attachment AK: 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: - a Community Day (days in which contributors virtually meet and work together at resolving as many tickets as possible) was held on Saturday 19th March 2016: 15 Jira issues were worked on and 6 were closed - the next Community Day is planned for Saturday 18th June 2016 - new features, improvements and bug fixes have been contributed and integrated into the official code base - we are working at a new version of our logo and at our website where we are planning to refactor most of the content and the layout - a committers survey was held; the results are published in (*) - some good progress has been made in the refactoring of the framework following an evolutionary step-by-step approach (**) - the activity in the official blog and Twitter accounts is steady - ApacheCon NA 2016: the OFBiz project has been represented by Sharan Foga, PMC member, that presented two talks, one about community consensus and one about OFBiz configuration - we have resolved all the CVEs that have been created in the last months and we have issued bug fix releases to address the vulnerabilities ## Health report: The project is in an healthy phase: the community is active and friendly, communication is happening in the mailing lists, in Jira, Confluence and on ad-hoc Skype groups. The committers group is growing; we are working at growing the PMC group as well ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Nicolas Malin on Mon Mar 23 2015 ## Committer base changes: - Currently 40 committers. - Gregory Draperi was added as a committer on Mon Mar 07 2016 ## Releases: - 12.04.06 was released on Mon Apr 04 2016 - 13.07.03 was released on Mon Apr 04 2016 ## Mailing list activity: mailing list activity has been steady (in terms of number of subscribers and number of emails) and similar to the ones in previous quarters ## JIRA activity: Jira activity is steady (with spikes during our community days) ## References: (*) https://cwiki.apache.org/confluence/display/OFBIZ/May+2016+-+Committers+Survey (**) https://cwiki.apache.org/confluence/display/OFBIZ/Re-Factor+To-Do+List ----------------------------------------- Attachment AL: Report from the Apache Olingo Project [Christian Amend] === General === ## 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 Olingo project released the latest 4.2.0 version in march as planned. The next release is planned for the end of June. There is also a vote open on a new patch release for the OData V2 code line. The focus is still on OData V4. Most OData features have been implemented. The remaining features are of a larger scope and thus take longer to implement. This lead to fewer but bigger commits by the PMC members. Overall we see fewer requests on the users mailing list. Interestingly we see more JIRA tickets with patches from users. Mostly for the V2 code line. So overall I would describe the health of the Olingo community as stable compared to the last report. The last report also mentioned a GitHub repository which was intended as a first easy starting point for a JPA extensions. There have been no commits or any further requests either on the user mailing list or the dev mailing list. I would consider this a failed experiment. If a JPA extension for the V4 code line is implemented it will most likely happen within the Apache repository. Although some users have asked for such an extension in the past there haven´t been any contributions which would speed up development. === 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.2.0 was released on Tue Apr 05 2016 ## Mailing list activity: - dev@olingo.apache.org: - 78 subscribers (up 0 in the last 3 months): - 423 emails sent to list (490 in previous quarter) - user@olingo.apache.org: - 141 subscribers (up 7 in the last 3 months): - 128 emails sent to list (172 in previous quarter) ## JIRA activity: - 64 JIRA tickets created in the last 3 months - 54 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AM: 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 0.12 on Feb 19th 2016 We resolved 4 issues for this release. The last few months have been quiet in development but there has been movement to start merging some pretty large changes that were developed in the last GSOC into our main development branch and release an OODT 1.0 release. COMMUNITY Latest committers and PMC members: Radu Maonle (radumanole) on 28 Oct 2015 as committer and PMC member. 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. This includes a new website, greater connectivity with other data platforms and adding some much desired features to the core platform. ----------------------------------------- Attachment AN: Report from the Apache OpenNLP Project [Jörn Kottmann] ----------------------------------------- Attachment AO: 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 are atm mostly fixing and enhancing the existing mainline. A few OWB committers are actively contributing to the ALv2 licensed CDI-2.0 specification. ## Health report: The project is a container library which is stable and actively used and maintained. Due to the fact that most users are using OWB as part of another project (e.g. TomEE) we get much feedback in ‚indirect‘ ways. Note that the recent GoogVsOrcl case doesn’t affect OWB as the CDI specification and TCK are both ALv2 licensed. ## 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.6.3 on Sat Feb 20 2016 ## Mailing list activity: Mailing list traffic is fine. ## JIRA activity: - 7 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: Report from the Apache Perl Project [Philippe M. Chiasson] -- mod_perl 1.0 -- mod_perl 1.x is a maintenance track designed to work with httpd 1.3.x. There have been no new mod_perl 1.x releases since our last report. --- mod_perl 2.0 -- mod_perl 2.X is designed to work with all httpd 2.X branches. The most recent release on this branch was mod_perl 2.0.9 on June 18, 2015. --- Apache-Test -- Apache-Test provides a framework which allows module writers to write test suites that can query a running mod_perl enabled server. It is used by mod_perl, httpd and several third party applications, and includes support for Apache modules written in C, mod_perl, PHP and Parrot. Apache-Test 1.39 was last released on Apr 21, 2015 --- Apache-SizeLimit -- Apache-SizeLimit is a popular component in most mod_perl production environments. It is used to kill off large httpd child processes based on various environmental triggers. Apache-SizeLimit 0.97 was released on Apr 02, 2012 --- Apache-Bootstrap -- Apache-Bootstrap is a framework to make it easier to build perl module distributions for different mod_perl versions. It encapsulates code developed over the years by mod_perl developers to make maintaining Apache::* and Apache2::* modules in the same distribution easy. Apache-Bootstrap 0.07 was released on Jul 13, 2009 --- Apache-Reload -- Apache-Reload is a popular component in most mod_perl development environments, used to refresh compiled code in the perl interpreter without completely restarting httpd. Apache-Reload 0.13 was released on May 09, 2015 -- Apache-DBI -- Apache-DBI is a popular component in many mod_perl deployments. It is used to provide transparent database connection pooling to clients using DBI. Apache-DBI 1.12 was released on June 12nd, 2013 -- Development -- mod_perl continues to be a healthy development community, though as a mature and stable product development moves at a naturally slower pace than in years past. Bugs are found and discussed and fixes are applied with due consideration for our production userbase. -- Users -- Support for users through the mailing list is ongoing. Patches and bug reports are few, but keep on coming. -- PMC -- No noteworthy PMC events happened since the last report. The PMC has currently 11 members ----------------------------------------- Attachment AQ: Report from the Apache Pig Project [Daniel Dai] 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 0.16.0 is released - Pig on Spark development is still under way in the spark branch, merge to trunk is near and target for 0.17.0 ## 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 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Xuefu Zhang on Tue Feb 23 2016 ## Committer base changes: - Currently 28 committers. - No new committers added in the last 3 months - Last committer addition was Praveen Rachabattuni at Mon Sep 08 2014 ## Releases: - 0.16.0 was released on Wed Jun 08 2016 ## Mailing list activity: - dev@pig.apache.org: - 411 subscribers (down -10 in the last 3 months): - 1148 emails sent to list (891 in previous quarter) - user@pig.apache.org: - 1175 subscribers (up 1 in the last 3 months): - 53 emails sent to list (103 in previous quarter) ## JIRA activity: - 83 JIRA tickets created in the last 3 months - 74 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: 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: I see the information about migration of Pivot-Extras, but haven't had time to pursue it since the last report. Would appreciate a bit of help digging into the process. Otherwise, there are no board-level issues this time around. Activity: Activity has been up a bit from last quarter with the new users still working and asking (a few) questions. There has been some bug fix activity. We should be able to do a new release (2.0.5) after one more bug is resolved (a Java 8 issue). Health report: The new users we got recently and continued development by me has kept things going this quarter. Long-term prospects are still uncertain as the market moves away from these kinds of platforms. We still have three PMC members for votes. 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: A couple more users started asking development questions, which is good. But it was a slow quarter as far as actual development goes. The new users contributed some good questions, which were all resolved (I think). Not quite as slow as some quarters go, so actually not bad. - dev@pivot.apache.org: - 63 subscribers (up 2 in the last 3 months): - 33 emails sent to list (55 in previous quarter) - user@pivot.apache.org: - 176 subscribers (up 2 in the last 3 months): - 22 emails sent to list (28 in previous quarter) JIRA activity: - 2 JIRA tickets created in the last 3 months. - 2 JIRA tickets closed/resolved in the last 3 months. - Activity has picked up just this last week (that is, after the reporting period). ----------------------------------------- Attachment AS: Report from the Apache Portable Runtime (APR) Project [Jeff Trawick] ## Short version of report: No releases, no committee/committer changes, modest other activity (Same summary as for the March 2016 report) ## Description: The Apache Portable Runtime (APR) project creates and maintains software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. The sub-projects which are released somewhat regularly are APR and APR-util. In addition, the APR-iconv sub-project is commonly used but has not had a release since 2007. ## Issues: - There are no issues requiring board attention at this time. - APR provided an interim report in May 2016 to address a security response issue. ## Activity: - Commit activity has been low. - Mailing list activity has been very low. - Five unique, non-SPAM bugs were opened during the reporting period, and four had followup (closure or discussion). ## Health report: - This is a mature project, and most of its development activity is driven by the needs of the same small number of applications that have used it for many years. The project members are more than able to meet the requirements that arise from that use. - The needs of the small number of other users are not met very well; bug reports languish and mailing list posters may not receive timely responses. The amount of help provided is probably not sufficient to serve as encouragement to potential new users of APR. ## PMC/Committer changes: - Currently 66 committers and 39 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Yann Ylavic on Wed May 13 2015 - One committer added in the last 3 months - Last committer addition was Brian Havard on Wed May 04 2016 ## 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: - dev@apr.apache.org: - 360 subscribers - 30 emails sent to list (86 in previous quarter) - commits@apr.apache.org: - 75 subscribers - 34 emails sent to list (59 in previous quarter) ----------------------------------------- Attachment AT: Report from the Apache Portals Project [David Sean Taylor] Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Activity: Apache Portals released 1 release since the last report. Apache Portals Jetspeed released version 2.3.1 on May 9, 2016. Version 2.3.1 introduces important Security patches provided by the Apache Security team. New features include a new Search UI, improved Session Preferences, Detached Portlets, updates to the tutorial, and improved Responsive Decorators. Apache Portals Pluto team is actively implementing Pluto 3.0 to support to the Portlet Spec 3.0 We are planning on releasing the Portlet Spec 3.0 by September 2016 ## Issues: We have no board-level issues at this time. ## PMC/Committership changes: We are in the process of proposing one new PMC member from the Pluto team, Martin Scott Nicklaus, the Portlet API Spec lead. The Pluto team nominated Mohd Ahmed Kahn, who was elected by the Pluto team on the dev list. However, a PMC member requested that the vote be held in private by the PMC. The PMC decided to not elect Mohd until he provided more documented contributions. We plan to revote within a month or two. Last Added PMC Members: 4 May 2015 - Randy Watler Last Added Committers: 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014 Neil Griffin ## Releases: Jetspeed 2.3.1 on May 9, 2016 ----------------------------------------- Attachment AU: 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: There are no issues requiring board attention at this time ## Activity: Post graduation tasks have been completed. There has been good development activity in the following areas: - Solr, Kafka and Hive binding improvements and bug fixes - Sentry service improvements and bug fixes - Improved test coverage - Performance improvements of the Sentry client - High availability ## Health report: Activity is good. No major changes. ## PMC changes: - Currently 31 PMC members. - Two new PMC members have been added recently: Li Li and Colm O hEigeartaigh ## Committer base changes: - Currently 33 committers. - New commmitters: - Colm O hEigeartaigh was added as a committer on Tue May 10 2016 - Li Li was added as a committer on Tue May 10 2016 ## Releases: - Community voting on 1.7.0 release ## Mailing list activity: - Increase in subscribers to the dev list. 5 as compared to 1 the previous month. - dev@sentry.apache.org: - 85 subscribers (up 5 in the last 3 months): - 595 emails sent to list (538 in previous quarter) - issues@sentry.apache.org: - 14 subscribers (up 14 in the last 3 months): - 1679 emails sent to list (0 in previous quarter) ## JIRA activity: - 66 JIRA tickets created in the last 1 month - 54 JIRA tickets closed/resolved in the last 1 month ----------------------------------------- Attachment AV: 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 releases (5.5.4, 6.0.3) and new updates 5.6.1 and 6.1.1 from the development branches. We have also released new OSGi bundle sets and ServiceMix Specs. We can observe decreasing activity on dependency version used by the 5.5.x and 5.6.x versions, so we expect decreasing activity on ServiceMix 5 next months and transiting it in 'end of life' state soon. We plan to focus on ServiceMix 6 and ServiceMix 7 instead, to provide users with latest and greatest technology and upgrades of Apache Karaf, ActiveMQ, Camel and CXF versions. We plan to release new versions of ServiceMix 6 next weeks. We are working on the new ServiceMix 7.0.0.M2 which should be released next days. During the next period we plan to release the final version of ServiceMix 7 and return to the work on migration of the documentation. ## Health report Activity on the mailing lists and in JIRA has been a bit slow during the last period, but is picking up again now. Since our last board report, we voted in 1 new committer, Andrea Cosentino. ## 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. - Andrea Cosentino was added as a committer on Sun Mar 13 2016 ## Releases - Apache ServiceMix 6.0.3 on March 23 2016 - Apache ServiceMix 6.1.1 on March 23 2016 - Apache ServiceMix Bundles 2016.03 on March 30 2016 - Apache ServiceMix Specs 2.7.0 on April 17 2016 - Apache ServiceMix Bundles 2016.04 on May 03 2016 - Apache ServiceMix 5.5.4 on June 06 2016 - Apache ServiceMix 5.6.1 on June 06 2016 - Apache ServiceMix Bundles 2016.05 on June 07 2016 ## Mailing list activity - users@servicemix.apache.org: - 420 subscribers (up 1 in the last 3 months): - 88 emails sent to list (54 in previous quarter) - dev@servicemix.apache.org: - 207 subscribers (up 0 in the last 3 months): - 149 emails sent to list (215 in previous quarter) - issues@servicemix.apache.org: - 9 subscribers (up 1 in the last 3 months): - 615 emails sent to list (699 in previous quarter) - commits@servicemix.apache.org: - 57 subscribers (up 1 in the last 3 months): - 790 emails sent to list (830 in previous period) ## JIRA activity - 119 JIRA tickets created in the last 3 months - 122 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AW: Report from the Apache Shiro Project [Les Hazlewood] ----------------------------------------- Attachment AX: 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. No new committers (last committers change was in March 2015 with three new committers elected), one new PMC member in March 2016 (Radu Cotescu) (last PMC change was in October 2015 with one new PMC members elected). Releases: Apache Sling Servlets Post 2.3.12 (June 1st, 2016) Apache Sling JSON Library 2.0.16 (May 27th, 2016) Apache Sling Discovery API 1.0.4 (April 29th, 2016) Apache Sling Log Tracer version 1.0.0, Apache Sling Resource Resolver 1.4.12 (April 25th, 2016) Apache Sling Scripting JSP-Taglib version 2.2.6 (April 21st, 2016) Apache Sling Auth Core 1.3.14 (April 12th, 2016) Apache Sling Servlets Post (April 10th, 2016) Apache Sling Resource Resolver (April 7th, 2016) Apache Sling Event 4.0.2 (April 4th, 2016) Apache Sling Discovery Commons 1.0.12 (March 29th, 2016) Apache Sling Scripting Sightly Engine 1.0.18 (March 18th, 2016) Apache Maven Sling Plugin 2.1.8 (March 16th, 2016) Apache Sling IDE Tooling for Eclipse 1.1.0 (March 14th, 2016) Apache Sling Resource Resolver 1.4.8, Apache Sling JCR Resource 2.7.4, and Apache Sling Installer Core 3.6.8 (March 11th, 2016) Apache Sling Health Check Core 1.2.4, Apache Sling Health Checks Annotations 1.0.4, Apache Sling JCR Davex 1.3.2, and Apache Sling JCR Webdav 2.3.4 (March 8th, 2016) Apache Sling Scripting Sightly Engine 1.0.16 (March 5th, 2016) Apache Sling Tooling Support Source 1.0.0 (March 3rd, 2016) Documentation and infrastructure: Nothing to report Project Branding is tracked in SLING-2696. ----------------------------------------- Attachment AY: Report from the Apache SpamAssassin Project [Kevin A. McGrail] 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 project is mature in that it has not seen rapid development of its software component. SpamAssassin is widely used, and users do make use of the regular updates of the rules. There has not been much new development of the code. Bug reports are being looked at and handled. There is active discussion on the user list. Rule updates happen regularly. Issues: The project chair became unexpectedly unavailable last March. The PMC did not determine the full circumstances until recently. The PMC has voted to nominate Sidney Markowitz as the new chair. One issue with the sudden transition is that the chair had set up the infrastructure for our “mass-check” that accepts submissions of spam and non-spam email and drives our automated rule update system. We are still trying to determine if anyone else knows the details or at least has access to the infrastructure. The mass-check system itself has been running smoothly, but lack of access for moving, changing, or fixing it is a major concern. Infra: The last report that was submitted stated that Zones2 deprecation was stalled due to disk space requirements. Now the status is that it is stalled until the new chair can find out what that means and finish the task. Releases: The last release was version 3.4.1 on April 30, 2015. Last November the project agreed that there are sufficient bug fixes in the 3.4 branch and it is sufficiently stable to justify releasing 3.4.2 “soon”. There has been development in the main (4.0) branch, but no discussion of a release schedule for it. We need to close some remaining issues for 3.4.2 and sweep through issues in the 4.0 branch to check for any fixed ones that should be ported or open ones that really ought to be fixed in 3.4.2, then get the 3.4.2 release out the door. Committer/PMC changes: The last new committer was added over two years ago. The last new member of the PMC was three and a half years ago. The new chair has stated concern over the stagnation that implies and will see if there is anything we can do about it. ----------------------------------------- Attachment AZ: Report from the Apache Spark Project [Matei Zaharia] Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python and R as well as a rich set of libraries including stream processing, machine learning, and graph analytics. Project status: - The community is in the QA phase for Spark 2.0, our second major version since joining Apache. There are a large number of additions in 2.0, including a higher-level streaming API, improved runtime code generation for SQL, and improved export for machine learning models. We are also using this release to clean up some experimental APIs, remove some dependencies, add support for Scala 2.12. The full list of changes is available at http://s.apache.org/spark-2.0-features. We also released a 2.0.0-preview package to let users broadly participate in testing the new APIs. - We released Spark 1.6.1 in March, with bug fixes for the 1.6 branch. - For Apache Spark 2.0, the community decided to move some of the less used data source connectors for Spark Streaming to a separate project, Apache Bahir (http://bahir.apache.org). We proposed a new project in order to maintain ASF governance of these components. - The project removed the role of "maintainers" for reviewing changes to specific components (originally added 1.5 years ago) in response to concerns from some ASF members that it makes the project appear less welcoming, as well as the conclusion that it did not have a noticeable impact in practice (https://s.apache.org/DUTB, https://s.apache.org/AgCt). Trademarks: In the past few weeks, there have been several discussions asking for more attention to trademark use from the PMC. Some of the main issues were: - A vendor offering a "technical preview" package of Apache Spark 2.0 before there was any official PMC release. - A vendor claiming to offer "early access" to the project's roadmap. - Various corporate and open source products whose name includes "Spark". - Corporate pages were the most prominent mention says "Spark" instead of "Apache Spark". The PMC is addressing these issues in several ways: - Reaching out to the organizations involved. - To make the project's association with the ASF clearer in news articles and corporate materials, we are working to update the logo to include "Apache": https://s.apache.org/Jf7J. We also added a FAQ entry about using the logo that links to the ASF trademarks page. - Continuing to review news articles, product announcements, etc. - Starting with this board report, we will have a section on trademarks in our reports to track brand activity. - Question for the board: Would it be helpful to put a summary of the trademark policy on spark.apache.org? It would be nice to have this more visible (e.g. in the site's navigation menu), but either way is fine. We can draft a version and sent it to trademarks@. Events: - The Spark Summit community conference in San Francisco ran June 6-8. There were close to 100 talks from at least 50 organizations. Latest releases: - May 26, 2016: Spark 2.0.0-preview - Mar 9, 2016: Spark 1.6.1 - Jan 4, 2016: Spark 1.6.0 - Nov 09, 2015: Spark 1.5.2 - Oct 02, 2015: Spark 1.5.1 Committers and PMC: - The last committer was added on May 23, 2016 (Yanbo Liang). - The last PMC members were added Feb 15, 2016 (Joseph Bradley, Sean Owen and Yin Huai) ----------------------------------------- Attachment BA: Report from the Apache Stanbol Project [Fabian Christ] Apache Stanbol provides a set of reusable components for semantic content management. The project is doing fine on a low level. The major blocker is still the stocked release process. People do not find the time to cut new releases or to hand over the process to other PMC members. The project is focused on easing the use of Stanbol and use resources like Docker images. The project also received contributions in terms of improved documentation which will be included in the near futur. In combination with an improved release process Stanbol should become more easy to use to end users. The project voted for two new PMC members. The board has been notified but we need to wait for the 72 hours period to end until we invite them officially. The vote for new PMC members is a first step to hand over the planned improvements and the release process to a new generation of people. Subscribers on the dev list: 231 Last new committer was Cristian Petroaca on May 7th, 2015 Last stack release was: Apache Stanbol 0.12 on Mar 2nd, 2014 Last component release was: Apache Stanbol Partial Security Release RC2 on June 5th, 2014 org.apache.stanbol.commons.security.reactor-20140602 ----------------------------------------- Attachment BB: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: - Apache Storm is a distributed real-time computation system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The community released verion 1.0, which was a major milestone. - Since the 1.0 release, we have accellerated our release rate in order to address bugs/issues in a timely manner. - Preparations for 1.0.2 and 1.1.0 releases are underway, with a release expected soon. - We had one trademark issue raised. It was addressed quickly and easily. - The PMC has been reminded of the importance of policing our trademark. ## Health report: - There has been a slight decrease in committer activity. This can likely be attributed to a "sigh of relief" after the 1.0 release, as well as a shift in priorities among some committers' day jobs. - We continue to regularly add new committers/PMC members at a rate of 2-3 per quarter. ## PMC changes: - Currently 30 PMC members. - New PMC members: - Abhishek Agarwal was added to the PMC on Thu Jun 02 2016 - John Fang was added to the PMC on Thu May 12 2016 ## Committer base changes: - Currently 31 committers. - New commmitters: - Abhishek Agarwal was added as a committer on Fri Jun 03 2016 - John Fang was added as a committer on Tue May 10 2016 ## Releases: - 0.10.1 was released on Wed May 04 2016 - 1.0.0 was released on Sun Apr 10 2016 - 1.0.1 was released on Wed May 04 2016 ## Mailing list activity: - There has been a slight decrease in dev@ list activity as mentioned in the health report. - Activity on the user@ list has increased over the last quarter, most likely in response to the 1.0 release. - dev@storm.apache.org: - 530 subscribers (up 17 in the last 3 months): - 6503 emails sent to list (8827 in previous quarter) - user@storm.apache.org: - 1413 subscribers (up 47 in the last 3 months): - 1102 emails sent to list (645 in previous quarter) ----------------------------------------- Attachment BC: Report from the Apache Synapse Project [Hiranya Jayathilaka] Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. Community ========= The last committer and PMC member was added in May 2016: Ravi Undupitiya (ravi) Last month Brett Porter informed our community about the process for moving the project into the attic. Interestingly, this email has had a significant rejuvenating effect on the project. Since the email went out at least 4 volunteers have come forward who have expressed strong interest in contributing to the project and keeping it alive. One of them also volunteered to drive the next Synapse release as the release manager. We have voted him in as a committer and a PMC member, and he is currently working on fixing open issues to get the release out. Other volunteers have also been highly active in the project over the past few weeks. As a result we have had more development activity in Synapse over the last 3 weeks, than we have had in 3 years. Given the current level of participation, our chances of getting a release out soon is very good at the moment. We intend to vote in rest of these new volunteers as committers in the near future. 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. Work is successfully underway for a 3.0 release. Board Issues ============ In light of the new contributors who have come forward to resurrect the project, we will not be pursing a move to attic at this point in time. I (hiranya) will continue to serve and oversee the project as the PMC chair until a replacement is found. ----------------------------------------- Attachment BD: Report from the Apache Tajo Project [Hyunsik Choi] ----------------------------------------- Attachment BE: 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 an stable but low traffic project. There remains two responsible and responsive PMC ready to help users and discuss development ideas. Other PMC come out to help when needed. Currently no members are active in development, and no contributions have come in. The majority of activity happens on non-apache sites like the StackExchange forums. StackExchange sees a few questions and answers each day or two. This quarter saw input from an emeritus member Antonio, who had contributed much of the rewrite to Apache Tiles-3. While Antonio looks not to actively contribute again, but is using Tiles-3 again and will offer related contributions and ideas when appropriate. ## Health report: Apache Tiles is a stable project seeing little new momentum. There are currently two responsive PMC, other PMC help out with votes when needed. An initial effort was made to subscribe the StackExchange traffic into the users mailing list, without luck. Since this is the best representation of active traffic that we have this effort should be retried. Current members need to be reaching out to other forums to show that the Apache community is still there for them. 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. The pending patch release really should be made the next quarter so to verify the presence of 3+ PMC, as described above. ## Issues The board requested last report that less emphasis on the output of the health reporter be used, and a more direct statement used to describe the low health status that the project holds. Hopefully this has been addressed this report. ## Releases: No releases were made this quarter. There is still a patch release pending, no action has been taken so far. ----------------------------------------- Attachment BF: Report from the Apache TinkerPop Project [Stephen Mallette] ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). This is TinkerPop's first month outside of incubation. We are still awaiting resource transfer changes related to graduation to take place as there are issues preventing the infrastructure team from completing that process. Project development has been building up to two new releases which are expected to be released in July. A key area of focus in this last month has been related to opening TinkerPop to non-JVM programming languages through the concept of Gremlin Language Variants[1]. In taking this direction, TinkerPop becomes more accessible to non-JVM developer communities. ## Issues: There are no issues requiring board attention at this time. ## Releases: - 3.1.2 (April 8, 2016) - 3.2.0 (April 8, 2016) ## PMC/Committer: - Last PMC addition was Dylan Millikin - May 2016 - Last committer addition was Michael Pollmeier - April 2016 ## Links [1] http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/tutorials/gremlin-language-variants/ ----------------------------------------- Attachment BG: Report from the Apache Tomcat Project [Mladen Turk] Apache Tomcat is a Java Servlet, JavaServer Pages, Java WebSocket, Java Unified Expression language and Java Authentication Service Provider Interface for Containers 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. - Three presentations on Tomcat were given at ApacheCon NA and a meetup one evening was held with about ten participants. - A spate of Bugzilla spam was succcessfully blocked by the infra team. - Currently five branches are actively maintained. This will be reduced to three sometime later this year as 8.0.x reaches EOL (replaced by 8.5.x) and 6.0.x will be reach EOL at the end of this year. - A roughly monthly release cycle is held up for 9.0.x, 8.5.x, 8.0.x and 7.0.x and a roughly six monthly release cycle for 6.0.x. - Open bugs (excluding enhancement requests and those where furthe information is required from the OP) are fixed before each release. - There are three components where there is less activity. taglibs is dormant and it needs to be discussed whether it should be placed into Tomcat's attic. The Tomcat Maven Plugin needs committers. Currently it is only compatible with 7.0.x and lower, only. The connectors component is fairly mature will still sees bugs reports and needs committers in order to address them. - Discussion about inviting a new committer has started with no conclusion yet. Tomcat 9 has a dependency on the Servlet 4 specification which is part of Java EE 8. There has been much public discussion about the (lack of) progress [1] of Java EE 8. We do not intend to let this slow down Tomcat development. We continue to review the situation and take action as necessary. For example, Tomcat 8.5.x was introduced to make HTTP/2 (and other new features) available in a production quality release so users weren't waiting for Tomcat 9. PMC changes: - Currently 24 PMC members. - Last PMC addition was Felix Schumacher on Mon Oct 26 2015 Committer base changes: - Currently 40 committers. - Last committer addition was Martin Tzvetanov Grigorov at Tue Oct 27 2015 Releases: - Apache Tomcat 6.0.45 was released on Feb 10 2016 - Apache Tomcat 7.0.69 was released on Apr 15 2016 - Apache Tomcat 8.0.33 was released on Mar 24 2016 - Apache Tomcat 8.0.35 was released on May 16 2016 - Apache Tomcat 8.0.36 was released on Jun 13 2016 - Apache Tomcat 8.5.0 (beta) was released on Mar 24 2016 - Apache Tomcat 8.5.2 (beta) was released on May 16 2016 - Apache Tomcat 8.5.3 was released on Jun 13 2016 - Apache Tomcat 9.0.0.M4 was released on Mar 16 2016 - Apache Tomcat 9.0.0.M6 was released on May 16 2016 - Apache Tomcat 9.0.0.M8 was released on Jun 13 2016 - Apache Tomcat Native 1.2.6 was released on Apr 26 2016 - Apache Tomcat Native 1.2.7 was released on May 8 2016 Trademark: - Detailed status: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt Security: - Detailed status: http://tomcat.apache.org/security.html ----------------------------------------- Attachment BH: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for June 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: 20 May 2016 (new) last release - Apache UIMA-AS 2.8.1 (UIMA Asynchronous Scalout) 03 May 2016 (new) last PMC addition 24 Jul 2015 (no change) last Committer addition Releases: 06 Apr 2016 Apache uimaFIT 2.2.0 this had many bug fixes and improvements, and upgrades to dependencies 20 May 2016 Apache UIMA-AS 2.8.1 this was an upgrade of many dependencies to later release levels. Other Activity: Work on the experimental UIMA Version 3 core is focused on getting a migration path that is easy for the user community. UIMA Ruta (Rules Text Language and workbench) and DUCC continue to be very active. Community: The community continues to be moderately active. Issues: No Board level issues at this time. ----------------------------------------- Attachment BI: 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: - The community had a fairly lengthy and productive discussion regarding the health of the project. [1][2] Some good ideas were expressed for how to maintain and improve the health. It is now up to us to actually implement these ideas. We will try to work on this over the upcoming months. - Work is underway to clear out the few remaining open Jira issues for the next release, VCL 2.5. This is mostly janitorial work. No significant code needs to be worked on. We hope to begin the release process this month. ## Health report: - Mailing list traffic is up a bit since the last report. I expect dev traffic to increase as we release a new version and user traffic to increase afterwards. - It has now been over a year since our last release. We will be releasing a new version soon. ## 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 Thu Apr 16 2015 ## Mailing list activity: - dev@vcl.apache.org: - 135 subscribers (up 1 in the last 3 months): - 77 emails sent to list (68 in previous quarter) - user@vcl.apache.org: - 170 subscribers (up 0 in the last 3 months): - 29 emails sent to list (8 in previous quarter) ## JIRA activity: - 14 JIRA tickets created in the last 3 months - 15 JIRA tickets closed/resolved in the last 3 months [1] http://vcl.markmail.org/thread/yaqxxfxf7drh4yj5 [2] http://vcl.markmail.org/thread/h33ag3bmrhgkezge ----------------------------------------- Attachment BJ: Report from the Apache Web Services Project [Sagara Gunathunga] Web Services Report for June 2016 Apache Web Services is a collection of shared technologies related to SOAP/XML based Web Services that can be shared by different implementations. Spring-WS, Axis2, CXF, and others use parts of the technology created within Apache Web Services. Community: WebServices is a mature project based on standards that are also quite mature. As such, there is not a significant amount of activity required. However, user questions are being answered promptly, bugs are being fixes, and there are at least 3 independent PMC members around making sure the project can continue to produce releases as needed. Since SOAP/XML based Web Services is no longer considered state of the art, we don’t expect a major uptick in new development efforts, new committers, etc... Last committer addition: Sun Sep 14 2014 (Alessio Soldano) Last PMC addition: Tue May 17 2016 (Alessio Soldano) Releases this period: Axiom - StAX-based, XML Infoset compliant object model * 1.2.19 - Apr 30, 2016 WSS4J - implementation of WS-Security and related technologies * 2.0.7 - March 22, 2016 * 2.1.5 - March 22, 2016 Last releases for other technologies: * XmlSchema 2.2.1 : Feb 2015 (XML Schema model) * Neethi 3.0.3 : Jan 2014 (WS-Policy implementation) * Woden 1.0M10 : Sept 2015 (WSDL 2.0 implementation) * WSS4J 2.0.7/2.15 : March 2016 (WS-Security implementation ) ----------------------------------------- Attachment BK: 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. ## Noteworthy items: - Currently 30/29 Committers/PMC members. - Last committer/PMC addition was François Meillet on Mon Jun 29 2015 - There are no issues requiring board attention at this time - Mailinglist traffic is stable without significant changes - An academic paper about architectural debt reviewed 7 Apache projects, including Wicket. - Work on Wicket 8 is in progress, a milestone release is imminent ## Releases this quarter We have issued the following releases: 7.3.0 and 6.23.0. ## Academic paper about architectural debt This article [1] references an academic paper about architectural debt that has researched 7 large-scale open source projects from Apache: Camel, Cassandra, CXF, Hadoop, HBase, PDFBox, and Wicket. Though we don't have access to the ACM's library, the linked summary provides some nice points about technical/architectural debt. ## State of the project The outlook for the project's long term future hasn't changed since the previous report. That said, there's interest in writing a new Wicket book. Several PMC members have been queried by publishers and authors about this effort. If such a book could appear is still not clear. Development for Wicket 8 is slow, albeit ongoing. A first milestone release is imminent, will be available for consumption later this month. Releases have not followed a fixed schedule lately, but we intend to start on a monthly or bi-monthly release schedule for the supported branches. [1] https://blog.acolyer.org/2016/06/13/identifying-and-quantifying-architectural-debt/ ----------------------------------------- Attachment BL: 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 has a mature project with small community which is currently not very active. Although I believe Wink is a mature project with active users, the overall PMC has been alive but not active. The user community continue to help each other in couple of questions we have received and they also contributing patches which is currently under review. Last svn activity (March 2016) was a security fix provided by a user. 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 BM: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J A couple minor updates were recently committed, otherwise it's been quiet on the development front over the last four months. There was another user query on the mailing list about having a new release. We still need volunteers to help drive one. Mailing list traffic continues to be very low; only 20+ posts on the j-dev and j-users lists since the beginning of March 2016. No new releases this quarter. The latest release is Xerces-J 2.11.0 (November 30th, 2010). Xerces-C Xerces-C has had a fair bit of activity as of late. Several JIRA issues that were opened by the community have been investigated and resolved since the beginning of June. Mailing list traffic has been low; roughly 65+ posts on the c-dev and c-users lists since the beginning of March 2016. No new releases this quarter. The latest release is Xerces-C 3.1.3 (February 17th, 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). One new PMC member (Scott Cantor) was added to the PMC this month (June 2016). The previous two additions to the PMC were in May 2010. Three committers have committed changes to SVN since March. Apache Project Branding Requirements The project logo still needs a "TM" to be added to it. ----------------------------------------- Attachment BN: 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 None at this time. RELEASES - Version 0.2.1 was released on April 7th 2016. - Version 0.3.0 was released on May 22nd 2016. ACTIVITY No new PMC addition in the last three months. Last PMC addition was Kengo Seki on February 28th 2016. Marco Zühlke was added as a committer on May 23rd 2016. Since our last report the community has worked on adding some new features for our existing downstream users, including a new tool for measuring code base health according to the rules defined in the precommit patch test tool. We've also been discussing easing getting started with the project through a combination of additional documentation and making use of the new Apache Help Wanted tool from comdev. As planned, our Allen Wittenauer presented the project at ApacheCon BigData and ApacheCon Core. Additionally he also gave a precommit patch test tool specific overview to the Apache HBase community at a meetup in San Francisco. Mailing list traffic remains low, as in prior reports, but less bursty. The community is still responsive to incoming requests, so we're not concerned. STATS - Currently 7 PMC members - Currently 8 committers - dev list has 36 subscribers (up 5 in the last 3 months) - 88 JIRA tickets created in the last 3 months - 71 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BO: Report from the Apache Zeppelin Project [Lee Moon Soo] ## Description: Apache Zeppelin is a collaborative data analytics and visualization tool for general-purpose data processing systems. ## Issues: There are no issues requiring board attention at this time. ## Activity: - After the graduation TLP migration is in progress with infra migration INFRA-11963. - Release discussion and preparation is started ZEPPELIN-889. - Team is hard at work fix flaky test on CI build. - Many code contribution is focused on multi-tenancy support. - There has been a couple of talks around Apache Zeppelin at ApacheCon Big Data NA. - Everyone Plays: Collaborative Data Science with Zeppelin - Trevor Grant - Apache Zeppelin and It’s Pluggable Architecture for Your Data Science Environment - Moon Soo Lee - Mining Public Datasets Using Apache Zeppelin (incubating) and Spark - Alexander Bezzubov - Interactive Data Science from Scratch with Apache Zeppelin and Apache Spark - Felix Cheung ## Health report: - We see lots of user demands for the release. And dev community is trying to respond to it/them. - Steady increment of number of code contributors. +5 last month, 120 total - There're up and down in mailing list traffic every months. But no significant increment since last Novmber. ## PMC changes: - Apache Zeppelin established on May 18 2016 with 9 PMC members. - Last (P)PMC addition was Prabhjyot Singh on Mar 29 2016, under incubation ## Committer base changes - Currently all Committers are PMC ## Release - 0.5.6-incubating was released on Jan 22 2016 - 0.5.5-incubating was released on Nov 18 2015 - 0.5.0-incubating was released on Jul 23 2015 ## Mailing list activity - users@zeppelin.apache.org - 538 subscribers (up 64 in the last 3 months) - 176 emails sent to the list (377 in previous quarter) - dev@zeppelin.apache.org - 267 subscribers (up 39 in last 3 months) - 922 emails sent to the list (1087 in previous quarter) ## JIRA activity: - 223 JIRA tickets created in the last 3 months - 91 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BP: 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. Activity: The activity during this last quarter has been (as usual) slow, but slightly higher than previous quarter. We have seen a handful of responses coming in via help.apache.org, but not managed to convert any into contributions, and we think that is the nature of that page (easy to click, even if no commitment is intended). Issues: There are no issues that requires the Board's attention. Health report: Attracting new blood is constantly on our mind, but we have no good answers. One new user surfaced and have been helped to get going. We hope to convert that to some more activity. 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 17 committers. - No new committers added in the last 3 months - Last committer addition was Kent Sølvsten at Sun Jun 14 2015 Releases: - Last release was Zest JAVA-2.1 on Fri Jul 31 2015 Mailing list activity: We should probably shut down, or at least stop listing the users@ mailing list, as all traffic has been (and will be for the foreseeable future) on the dev@ list. - users@zest.apache.org: - 19 subscribers (up 1 in the last 3 months): - 0 emails sent to list (1 in previous quarter) - dev@zest.apache.org: - 33 subscribers (up 4 in the last 3 months): - 185 emails sent to list (140 in previous quarter) JIRA activity: - 10 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BQ: 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: - Release 3.4.7 contains a number of bug fixes,   including:     - ZOOKEEPER-1506: Retry DNS resolution on connection failures.     - ZOOKEEPER-1833: Improve the quality of Windows build.     - ZOOKEEPER-1907: Improve thread handling. - Release 3.4.8 mainly fixes a deadlock introduced in 3.4.7: - ZOOKEEPER-2347: Deadlock shutting down zookeeper - Chris Nauroth is the release manager for the next alpha release 3.5.2. The community is currently working towards releasing 3.5.2 and stabilizing the 3.5 branch which is currently alpha. - Rakesh Radhakrishnan has been driving the effort to add server-to-server   authentication (ZOOKEEPER-1045). ## Health report The mailing list activity remains comparable to the one of the previous period with a slight increase on the number of subscribers. The number of commits has dropped significantly compared to the previous period based on the number of messages for commits@zookeeper.apache.org. The PMC is actively looking into inviting contributors to become committers. ## PMC changes: - Currently 10 PMC members. - The last PMC member added was Raúl Gutierrez Gonzales on Feb. 2, 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: - 3.4.7 released on Wed Dec 02 2015 has been withdrawn due to a serious deadlock bug. - 3.4.8 was released on Feb. 20, 2016. ## Mailing list activity: The number of subscriptions has increased both for the user and the dev lists. The number of messages on the user list has dropped slightly (roughly 5%). The number of commits has dropped significantly. - commits@zookeeper.apache.org - 110 subscribers (up 6 in the last 3 months) - 70 emails sent in the past 3 months (317 in the previous cycle) - dev@zookeeper.apache.org: - 507 subscribers (up 19 in the last 3 months): - 2161 emails sent to list (1148 in previous quarter) - user@zookeeper.apache.org: - 1170 subscribers (up 27 in the last 3 months): - 296 emails sent to list (314 in previous quarter) ## JIRA activity: - 55 JIRA tickets created in the last 3 months - 32 JIRA tickets closed/resolved in the last 3 months ------------------------------------------------------ End of minutes for the June 15, 2016 board meeting.