The Apache Software Foundation Board of Directors Meeting Minutes August 17, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:35 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/3199 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 Sam Ruby Craig L Russell Ulrich Stärk - left at 12:15 Executive Officers Absent: none Guests: Aaron Morton Daniel Gruno David Nalley Dennis E. Hamilton Henri Yandell - joined at 10:51 Jake Farrell Jonathan Ellis Sean Kelly Tom Pappas 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of July 20, 2016 See: board_minutes_2016_07_20.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] The focus of the board over August have been the issues Ross highlights in the President's report, and covered in the discussion items. Other than that, several directors have been assisting a small number of projects working through community issues. B. President [Ross] For personal reasons I have mostly been absent from my role for a few months now. As a result I have asked the board to consider whether it is the best thing for the ASF to have me continue as President. I have reassured the board that I am ramping back up, and indeed during the last couple of weeks I feel I have almost fully returned, however, my absence has led me to consider the role in some detail. Below is the edited text of a couple of emails I sent privately to the board a week before this meeting. It prompted some discussion and has resulted in a discussion item on this months agenda. I have had to take personal time recently. I’ve found it impossible to get motivated to come back until now. During my personal time I’ve done a great deal of thinking and I’ve come to the conclusion that things here need to change. Either me or the foundation. The foundation is growing faster than our operations abilities to manage the foundation. I’ve proposed many different models to address this and taken many positive steps towards fixing individual pieces (as have many VPs that have come and gone over the years). My focus, as a fully committed ASF Member, has always been to preserve the independence of the foundation. Unfortunately, I have been knocked back at every step. Sometimes because the proposal is seen as too broad (i.e. hire someone), sometimes because volunteers are burned out by the overhead of change management. The argument against radical change is usually that we will not crash and burn if things just tick along with the occasional blip. This is true, but it is a very short sighted view. What will happen is that we will slowly rot if we don’t address these things. Volunteers will continue to burn out. The foundation will continue to grow. We will become increasingly unbalanced and our ability to manage the operations of the foundation will eventually be crushed. I’ve failed to come up with an acceptable solution for the board, therefore the board, with me, needs to come up with an alternative. I realize that the best alternative may be a new Prez. Perhaps my lack of motivation is now part of the problem (this is certainly true for the last few months). I want to be clear that I am happy to tender my resignation at an agreed time, I'm also happy to stay on, but with the understanding that radical change, in some form, is needed. I’m not laying down an ultimatum, nor am I threatening. I want to work with the board to ensure the ASF remains healthy in the long term. My recommendation remains that we must hire someone, or some org, to take responsibility for the operations of the foundation, under the leadership of volunteer VPs and a Prez. That being said, I know there is no consensus around this. I know there is significant objection. But when we try to discuss this it focuses more about "the title" than "the role and responsibilities", or more about "what might happen if we do" than "what might happen if we don't". That is discussion often feels more about restating history than looking at the future. I'm not saying I'm right. I'm saying I don't feel the open discussion has been had. This report is intended to provoke that discussion. I stand by those words and now make them public. I undertake to work with the current directors to find the best solution. This is not an easy thing to do. If there were a quick fix we would have implemented it already. Fortunately, the foundation is in good shape and my concern is about ensuring the foundation can maintain this good shape for many years to come. At this time our financial situation is extremely solid. Our communities grow yearly. Our operations are, though creaking, mostly effective. However, whilst well managed our budget deficit is growing year on year and, unless we see significant increases in income, that deficit will continue to grow - especially as we look to further invest in infrastructure. There is no need for alarm. We have many years of reserve, but we cannot operate long term on a plan that depends on a reserve. As the current President I feel we need to take the long view and we are now at a point where my long term recommendations may not be sufficiently aligned with that of the board. EA == EA has recently, at my request, taken over full responsibility for the coordination of the TAC process for ApacheCon. This is because our VP TAC appears to be otherwise engaged. The good news is that since taking on this responsibility TAC has mostly come back on track with plenty of ne volunteers. One area of difficulty is in updating the website and questions app. Melissa has reached out to Infra for help on this. Though with the arrival of new volunteer it is hoped that someone will take on this responsibility. Melissa is working with Sharan to organize our ApacheCon EU booth activities. Sharan covered for Melissa in NA last time around and has since stepped up to help more broadly. As a resident of the EU this reduces travel time and expense. Brand Management =============== A busy time recently. VP Brand Management is struggling to stay on top, though the decentralization of brand management to PMCs continues to pay dividends. I will observe, however, that this decentralization, can only be harmed when community concerns are brought to the trademark list (an element of operations) and used to influence a trademark registration request, coupled with voluntary donations to cover costs. These two things should be kept separate. Having trademarks assigned to the ASF gives the foundation more influence over community players who are not yet managing trademarks as effectively as we would like. VP Brands report contains similar comments. Fundraising ========= Thanks to Jim who has resigned as one of our two VPs. At this time I do not intend to replace Jim, but again invite all directors to help with both finding new sponsors and engaging with existing sponsors The usual activity around fundraising with the difficulty in contacting one sponsor due for renewal clearly illustrating the need for an ongoing engagement with our sponsors. VP Fundraising again raises concerns about the potential for sponsors at the Bronze level seeing sponsorship as "buying a link" rather than sponsoring the foundation. On this occasion a new sponsor raised some concerns. I continue to defer to VP Fundraising to set policy, but I have enquired as to what needs to happen before this is considered a problem. My concern is that one sponsor expressing a concern may be many more not taking the time to make the observation. Marketing and Publicity ================== Business as usual with the normal press and analyst engagements. Sally has also been working with Melissa and Sharan to explore community partnerships at ApacheCon. Infrastructure ========== We are finally moving on our search for infrastructure team members. Our continued "in the loop" search continued to only attract applicants that were outside of our price range. However, with a new and very broad outreach we are now being "flooded" with applications. My thanks go to David who is working with the Infra team to work through these proposals. The team have hit a major milestone with the puppetization of the Jenkins and BuildBot services. The next major project is to migrate Jira from aging hardware. The Git experiment has little to report, which is a "good thing" as it means it is working reasonably well. The team continue to expand the work. This is an item I want to push forward once our team is fully resourced. As previously asserted I believe allowing projects to use the GitHub as a canonical repository (with appropriate safeguards as discussed) is an important part of the reduction of operations overhead. TAC === Around 10 months ago we discussed reviewing the TAC questions to ensure they met the goals of the foundation with respect to community development. While there have been some tweaks to the questions this work has not yet been carried out. Mostly due to a lack of volunteer energy to drive this difficult task. Additionally, please see Attachments 1 through 6. There will be a discussion on many of these points in the Discussion section of the board meeting. C. Treasurer [Ulrich] Operations continue as normal. We are operating with a slight deficit but our cash reserves are still healthy. Treasurer still needs to find out a suitable way to make use of our bitcoin wallet, no progress has been made there. Income and Expenses for July 2016 CASH BASIS Current Balances: July 2016 Citizens Checking $464,797 Citizens Money Market $1,202,452 Amazon- ASF Payments $- Paypal - ASF $86,444 Wells Fargo Checking - ASF $- Wells Fargo Savings $- Total Checking/Savings $1,753,692 Income Summary: Inkind Revenue $6,163 Public Donations $2,106 Sponsorship Program $71,003 Programs Income $- Other Income $- Interest Income $509 Total Income $79,782 Expense Summary: In Kind Expense $7,167 Infrastructure $49,198 Sponsorship Program $- Programs Expense $- Publicity $5,455 Brand Management $12,365 Conferences $- Travel Assistance Committee $- Tax and Audit $- Treasury Services $3,100 General & Administrative $9,011 Total Expense $86,295 Net Income $(6,513) D. Secretary [Craig] In July, 66 iclas, two cclas, and two grants were received and filed. E. Executive Vice President [Rich] We are entering the last month of the CFP for ApacheCon Europe, so this is when we expect to see some talks actually coming in. Once we have a schedule, we will start promoting the event more. However, we have already seem significantly more Twitter/Facebook/G+ activity around the event than we have seen around the last few events, which is a good early sign. Registration ApacheCon Europe 14 Apache: Big Data Europe 15 CFPs ApacheCon Europe 48 Apache: Big Data Europe 51 Please watch the dev@community.apache.org mailing list for ways that you can help get the word out about this event, as we get closer. 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 / Bertrand] 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 [bp] # Cassandra [cm] # Clerezza [cm] # Cocoon [bp] # TomEE [bp] A. Apache Abdera Project [Ant Elder / Jim] No report was submitted. B. Apache ACE Project [Marcel Offermans / Marvin] See Attachment B C. Apache Airavata Project [Suresh Marru / Isabel] See Attachment C D. Apache Ambari Project [Yusaku Sako / Brett] See Attachment D E. Apache Ant Project [Conor MacNeill / Greg] See Attachment E F. Apache Attic Project [Henri Yandell / Mark] See Attachment F G. Apache Axis Project [Deepal Jayasinghe / Shane] No report was submitted. Mark: also concerned about holding retirement votes on private list H. Apache Bahir Project [Luciano Resende / Mark] See Attachment H I. Apache BookKeeper Project [Sijie Guo / Chris] See Attachment I J. Apache Brooklyn Project [Richard Downer / Brett] See Attachment J K. Apache Buildr Project [Alex Boisvert / Shane] See Attachment K L. Apache Cassandra Project [Jonathan Ellis / Greg] See Attachment L The Board expressed continuing concern that the PMC was not acting independently and that one company had undue influence over the project. PMC representatives acknowleged the Board's concerns and asked for clarity from the Board in the form of explicit actions that the PMC should be taking to improve the situation. It was suggested that a representative from the board could meet with senior company management to relate the board's concerns directly. It was agreed that the project should report again next month. @Mark: Summarize items for PMC to address @Jim: Arrange a meeting to relate the Board's concerns with senior company management. M. Apache Clerezza Project [Hasan Hasan / Jim] See Attachment M @Jim: Discuss new committers discussion with PMC N. Apache Cocoon Project [Thorsten Scherler / Bertrand] No report was submitted. O. Apache Community Development Project [Ulrich Stärk / Isabel] See Attachment O P. Apache CouchDB Project [Jan Lehnardt / Marvin] See Attachment P Q. Apache Creadur Project [Brian E Fox / Marvin] See Attachment Q R. Apache CXF Project [Daniel Kulp / Shane] See Attachment R S. Apache DeltaSpike Project [Thomas Andraschko / Bertrand] See Attachment S T. Apache DeviceMap Project [Radu Cotescu / Isabel] See Attachment T U. Apache Drill Project [Parth Chandra / Brett] See Attachment U V. Apache Empire-db Project [Rainer Döbele / Chris] See Attachment V W. Apache Flume Project [Hari Shreedharan / Jim] See Attachment W X. Apache Forrest Project [David Crossley / Greg] See Attachment X Y. Apache Giraph Project [Avery Ching / Mark] See Attachment Y Z. Apache Gora Project [Lewis John McGibbney / Shane] See Attachment Z AA. Apache Groovy Project [Guillaume Laforge / Bertrand] See Attachment AA AB. Apache Hama Project [Edward J. Yoon / Isabel] See Attachment AB AC. Apache Helix Project [Kishore Gopalakrishna / Jim] See Attachment AC AD. Apache HTTP Server Project [Eric Covener / Greg] See Attachment AD AE. Apache HttpComponents Project [Asankha Perera / Mark] See Attachment AE AF. Apache Ignite Project [Dmitriy Setrakyan / Marvin] See Attachment AF AG. Apache Incubator Project [Ted Dunning / Brett] See Attachment AG AH. Apache jUDDI Project [Alex O'Ree / Chris] See Attachment AH AI. Apache Kafka Project [Jun Rao / Isabel] See Attachment AI AJ. Apache Knox Project [Kevin Minder / Chris] See Attachment AJ AK. Apache Kudu Project [Todd Lipcon / Jim] See Attachment AK AL. Apache Kylin Project [Luke Han / Brett] See Attachment AL AM. Apache Lens Project [Amareshwari Sriramadasu / Greg] See Attachment AM AN. Apache Libcloud Project [Tomaž Muraus / Shane] See Attachment AN AO. Apache Logging Services Project [Ralph Goers / Marvin] See Attachment AO AP. Apache ManifoldCF Project [Karl Wright / Bertrand] See Attachment AP AQ. Apache Marmotta Project [Jakob Frank / Mark] See Attachment AQ AR. Apache MetaModel Project [Kasper Sørensen / Jim] See Attachment AR AS. Apache MINA Project [Jean-François Maury / Isabel] See Attachment AS AT. Apache Oltu Project [Antonio Sanso / Chris] See Attachment AT AU. Apache Oozie Project [Robert Kanter / Marvin] See Attachment AU AV. Apache Open Climate Workbench Project [Michael James Joyce / Greg] See Attachment AV AW. Apache Perl Project [Philippe M. Chiasson / Shane] See Attachment AW AX. Apache Phoenix Project [James R. Taylor / Bertrand] See Attachment AX AY. Apache POI Project [Dominik Stadler / Mark] See Attachment AY AZ. Apache Qpid Project [Robbie Gemmell / Brett] See Attachment AZ BA. Apache REEF Project [Markus Weimer / Jim] See Attachment BA BB. Apache River Project [Patricia Shanahan / Greg] See Attachment BB BC. Apache Roller Project [Dave Johnson / Brett] See Attachment BC BD. Apache Santuario Project [Colm O hEigeartaigh / Marvin] See Attachment BD BE. Apache Serf Project [Bert Huijben / Isabel] See Attachment BE BF. Apache SIS Project [Martin Desruisseaux / Bertrand] See Attachment BF BG. Apache Spark Project [Matei Zaharia / Chris] See Attachment BG BH. Apache Stratos Project [Lakmal Warusawithana / Mark] See Attachment BH BI. Apache Subversion Project [Greg Stein] See Attachment BI BJ. Apache Syncope Project [Francesco Chicchiriccò / Shane] See Attachment BJ BK. Apache TinkerPop Project [Stephen Mallette / Bertrand] See Attachment BK BL. Apache TomEE Project [David Blevins / Marvin] No report was submitted. BM. Apache Turbine Project [Thomas Vandahl / Brett] See Attachment BM BN. Apache Twill Project [Terence Yim / Mark] See Attachment BN BO. Apache Usergrid Project [Todd Nine / Greg] See Attachment BO BP. Apache Velocity Project [Nathan Bubna / Isabel] See Attachment BP BQ. Apache Whimsy Project [Sam Ruby / Chris] See Attachment BQ BR. Apache Xalan Project [Steven J. Hathaway / Jim] See Attachment BR BS. Apache Xerces Project [Michael Glavassevich / Shane] See Attachment BS BT. Apache XML Graphics Project [Glenn Adams / Brett] See Attachment BT BU. Apache Zeppelin Project [Lee Moon Soo / Jim] See Attachment BU BV. Apache OpenOffice Project [Dennis Hamilton] A special report was presented verbally by Dennis Hamilton during the board concall. Below are notes on that report: Dennis: lots of activity on security and developer lists issued an advisory on a security issue will release a hot fix early next week general ability to respond: taking too long and no solution for quick releases for all platforms binaries there is pushback on releasing patch releases for stable platforms don’t know if there can be consensus on releasing security patches steep learning curve for new volunteers down to about 6 people who are experts in the code base Jim: Board feedback was given to PMC Discussion morphed into a build platform issue Will continue to monitor and stimulate discussion over the long term plan for the project Dennis: Some discussion has spilled over to the dev list. Mark: Currently lurking on private list Response to security issues is not adequate Dennis: It is useful to be reminded of security obligations Wants to step down as chair, hopefully for October board meeting @Dennis change to monthly board reporting @Dennis send email with verbal summary After the meeting, Dennis provided a written summary of the verbal discussion (above) and expanded some particular points into a larger report, which is in Attachment BV. Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Knox Project Chair WHEREAS, the Board of Directors heretofore appointed Kevin Minder (kminder) to the office of Vice President, Apache Knox, and WHEREAS, the Board of Directors is in receipt of the resignation of Kevin Minder from the office of Vice President, Apache Knox, and WHEREAS, the Project Management Committee of the Apache Knox project has chosen by vote to recommend Larry McCay (lmccay) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Kevin Minder is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Knox, and BE IT FURTHER RESOLVED, that Larry McCay be and hereby is appointed to the office of Vice President, Apache Knox, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Knox Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Ant Project Chair WHEREAS, the Board of Directors heretofore appointed Conor MacNeill (conor) to the office of Vice President, Apache Ant, and WHEREAS, the Board of Directors is in receipt of the resignation of Conor MacNeill from the office of Vice President, Apache Ant, and WHEREAS, the Project Management Committee of the Apache Ant project has chosen by vote to recommend Jan Matèrne (jhm) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Conor MacNeill is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Ant, and BE IT FURTHER RESOLVED, that Jan Matèrne be and hereby is appointed to the office of Vice President, Apache Ant, 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 Ant Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache Buildr Project Chair WHEREAS, the Board of Directors heretofore appointed Alex Boisvert (boisvert) to the office of Vice President, Apache Buildr, and WHEREAS, the Board of Directors is in receipt of the resignation of Alex Boisvert from the office of Vice President, Apache Buildr, and WHEREAS, the Project Management Committee of the Apache Buildr project has chosen by vote to recommend Antoine Toulme (toulmean) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Alex Boisvert is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Buildr, and BE IT FURTHER RESOLVED, that Antoine Toulme be and hereby is appointed to the office of Vice President, Apache Buildr, 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 7C, Change the Apache Buildr Project Chair, was approved by Unanimous Vote of the directors present. D. Change the Apache ODE Project Chair WHEREAS, the Board of Directors heretofore appointed Tammo van Lessen (vanto) to the office of Vice President, Apache ODE, and WHEREAS, the Board of Directors is in receipt of the resignation of Tammo van Lessen from the office of Vice President, Apache ODE, and WHEREAS, the Project Management Committee of the Apache ODE project has chosen to recommend Sathwik Bantwal Premakumar (sathwik) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Tammo van Lessen is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache ODE, and BE IT FURTHER RESOLVED, that Sathwik Bantwal Premakumar be and hereby is appointed to the office of Vice President, Apache ODE, 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 7D, Change the Apache ODE Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Executive VP responsibilities B. Status of Infrastructure Lead C. Paid support for other areas and impact on fundraising Please refer to this month's President's report for background information for this discussion. A. Executive VP responsibilities Can we increase responsibilities of EVP role? Jim: seems Rich’s heart is in ApacheCon so it makes more sense to have someone to take more of Ross’s responsibilities and have Rich focus on conferences Ross: While Rich is focused on conferences, he has been very involved in other issues. Biggest concern is workload, and need people who can step up. Chris: Maybe it’s time to create a VP, Conferences role Ross: But we want to move away from the ApacheCon model to project-focused conferences Rich: One concern is the relationship between conferences and brands Marvin: Is there an issue with reporting relationships for contractors? Ross: There should not be confusion. The buck stops at the VP; the President (or EVP) is only there to unblock issues Jim: Foresees EVP getting more involved in sponsors and fundraising, hiring infra @Ross: Prepare a proposal for VP, Conferences @Jim: Prepare a proposal for EVP role B. Status of Infrastructure Lead Ross: Operations vs. Infra: should not have both paid management positions Tom: focus now is on back filling staff that we have lost Brett: What does infra look like going forward? Chris: What happened to the Infra Lead Search Committee? Didn’t go anywhere. Ross: The Infra Lead didn’t get much traction. We’re looking now at Infra Lead as specifically technical. We need to hire senior technical infrastructure staff Chris: Adding more infrastructure doesn’t make sense without strategy for solving the VP Infra position Ross: We are backfilling contractors but still intend to hire technical infra lead. Still have a problem with liaison between infra and projects Marvin: Pleased with efforts to staff infra Chris: Also pleased with backfilling progress @Chris: Kick off discussion on @members for VP Infra @Brett: Make sure discussion progresses in time for next board meeting C. Paid support for other areas and impact on fundraising Brett: Do we have a model for infra going forward? Chris: I just don't feel that as an ASF member or community member that I know exactly what the direction is for infra, and strategy, etc. Ross: There are proposals on the table that are being discussed. But they are not formal enough to vote on at the moment. Jim: Maybe we can prioritize based on immediate need (e.g. TAC is time sensitive) 9. Review Outstanding Action Items * Ross: Notify PMC that tools are available to aid in the Apache Extras [ Pivot 2015-12-16 ] Status: Complete * Brett: Add another reminder to tardy projects the Monday before the meeting [ Discussion Items 2016-02-17 ] Status: This hasn't been an issue over recent months, closing the action item but will always follow up if there's a major issue on a given month. * Shane: Suggest ways to improve the board report; especially the the "Health" section [ Tiles 2016-03-16 ] Status: * Mark: explain to Axis PMC what the board is looking for in a report [ Axis 2016-05-18 ] Status: Complete. Remaining issues bening handled under other Axis action. * Ross: Post the infra job description for members to review [ President 2016-06-15 ] Status: Complete * Brett: What are the next steps to resolve the issues? [ Chukwa 2016-07-20 ] Status: follow up sent 15 Aug * Greg: Work with PMC to elect a new chair [ ODE 2016-07-20 ] Status: done * Tom: Virtual will help with recruiting infra staff. [ Discussion Items 2016-07-20 ] Status: update was provided in the President's report * Jim: Work with PMC to plan next steps for the project [ OpenOffice 2016-07-20 ] Status: Ongoing * Marvin: Links to unreleased source code must be removed from the Arrow home page. [ Arrow 2016-07-20 ] Status: * Mark: Get an improved report for next month [ Axis 2016-07-20 ] Status: Ongoing. No report provided this month. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:29 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] TAC: Despite repeated emails to VP, TAC over the past month and a half, I am not receiving responses. I spoke w/Ross about this in July; Ross sent an email to Nick on July 14th – no response. Meanwhile: • I created a DRAFT timeline for ACEU16 and sent to the TAC team (~July 14th) to review/edit/modify/etc. – no response. • TAC has received a few emails advising of tac applications submitted (they’re not full applications – just a name and answer to the first question). Again, despite several emails to Nick inquiring about this, I still have not received a response. • TAC was supposed to be reviewing/revising the application questions based on feedback received from past participants and with speaking with folks at ACNA16 and OSCON. – Despite repeated emails re this and if it’s being done, I have heard nothing. • Main page on http://apache.org/travel/ still reflects all the info for ApacheCon Vancouver – despite my emails re this. • There is no obvious info on the website for ACEU 16 (since it still has info for ACNA16)…the only way to get any info on ACEU 16 is to click on the “online application” – from there, it pulls up info for Seville. Which, oddly enough, I see the dates have now changed… “Time is very tight for this event, so applications will open on Aug. 14, 2016 and will end on Sept. 30, 2016 - to give enough time for travel arrangements to be made. Notifications will be sent out by Oct. 5, 2016.” …. Last I knew, the applications were due to open on July 23rd??!! But then again, what do I know since no one has responded to my (repeated) inquiries.?!!? ApacheCon: * Collaborating with Sally and Sharan re preparations for the ASF booth at ACEU. Operations: * Following up on the past-due invoice received for the Directors and Officers insurance (payment already sent – advised CSC of this). Fundraising and Trademarks: *Continuous monitoring of both Misc: *Handled misc requests for Apache stickers ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] Complex questions and heated discussion threads continue to pour through trademarks@ from a variety of PMCs and outside parties alike. Even accounting for the slowdown of responses during many recent summer vacations, the trend of notable issues requiring thoughtful and knowledgeable responses continues to grow faster than the number of volunteers providing regular and productive assistance. A PMC with a popular project is requesting international registrations in European Union, Japan, and India for their project name, and have supplied a detailed and well-thought-out rationale for the expense and effort for the additional registrations (a US application is in process already). Notably, a company working in this space has volunteered to help cover the legal costs of the registration in a way that properly respects our fundraising policies. While there are outstanding issues relating to the PMC's work on policing third party uses of their brand, I support the additional registrations and hope to work with operations@ on an appropriate way to secure greater rights for the ASF while minimizing our actual expenses. Unfortunately the discussion on the PMC's progress became more heated and widespread than I thought would be productive. Several trademark policy improvements are being proposed to better clarify allowable third party uses, in response to both existing projects as well as an incubating project's questions about ability to allow the project donor to continue using the brand. The policy for incoming names will be clarified to ensure it's clear that when donating a software product brand or trademark, it must be fully donated to the ASF, and the original donor does not retain any special rights. For cases where the original donor still has questions, the best advice will be for the podling to choose a new, unique name that the ASF can fully own. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities continue normally. The main focus this month was closing two sponsor renewals [1]. Jim resigned as VP fundraising and that led to discussions about the role of VP Fundraising. I suspect the discussions will continue as there were a few proposals in the past about how to structure the fundraising work. Another discussion thread was triggeres by a new sponsor. After an initial offer to sponsor he came back with a comment regarding concerns of their board of being associated with questionable businesses via our Thanks page, due to a few, let's say atypical, new bronze sponsors. After answering his concerns he decided to move forward and become an ASF sponsor. I am convinced such discussions will continue to pop up, as I said in previous reports, we continue to monitor the situation. Like Jim mentioned, it is a frustrating situation that was completely avoidable. For now it's not getting worse so there is no decision or recommendation for change yet. Hadrian is in vacation with spotty access to email and won't attend this month's board meeting. ----------------------------------------- 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 has secured Sharan Foga to officially assist with the ASF booth at select events, particularly those in Europe. Sally continues to counsel an increasing number of vendors involved with various Apache projects (both incubating and TLPs) with outreach and branding requirements. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 27 July 2016 --The Apache Software Foundation Announces Apache® Mesos™ v1.0 - 27 July 2016 --The Apache Software Foundation Announces Apache® Twill™ as a Top-Level Project - 26 July 2016 --The Apache Software Foundation Announces Apache® Kudu™ as a Top-Level Project IV. Informal Announcements: 7 items were published on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 106 weekly summaries published to date. 17 items were Tweeted on @TheASF. No new videos have been added to the ASF YouTube channel. V. Future Announcements: one announcement is in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 11 media queries. Over the past month, the ASF received 911 press clips vs. last month's clip count of 1,318. Our new reporting on media coverage of Apache projects yielded 4,337 press hits vs. last month's 4,813. VII. Analyst Relations: we responded to 2 analyst queries. Apache was mentioned in 48 reports by Gartner, 4 reports by Forrester, 18 reports by 451 Research, and 6 reports by IDC. VIII. ApacheCon liaison: through Sharan's ComDev contacts, Sally has been acting as introductory liaison to ApacheCon + Apache: Big Data producers, the Linux Foundation, for possible community partnerships. Sally has also connected Sharan with Melissa Warnkin on preparations for the ASF booth at ApacheCon Europe. IX. (Non-ASF) Industry Events and Outreach liaison: Sally is following up on a possible partnership for a conference in Europe, via Rich Bowen. X. Newswire accounts: we have 35 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] Short (and tardy) report this month. Hiring --------- We saw the blog post announcing the open position get reposted to several remote working job boards and have had a decent response in terms of resumes showing up. We made a first pass over approximately 1/3 of the incoming resumes as of this writing and hope to finish that first pass by end of week. We've seen a number of promising resumes show up and hope to be able to move forward with them. Hopefully we'll have material updates to provide to this in the coming week. General activity ------------------- Ongoing work on Jenkins and Buildbot slaves has finally coalesced into being completely managed via puppet. This is a huge milestone as these are relatively complex configurations and because of the number of machines it involves. It's also gotten some critical acclaim[1]. This should make it much easier for folks to get additional build dependencies installed in a more self-service manner (simple pull request against the repo compared to filing a ticket and having that done by infra) Work is in preparation for migrating our Jira instance off of our existing hardware. The current hardware is approximately 6 years old, and our instance has grown so much that the underlying database infrastructure on separate machines is starting to become a constraint. Growing on our blocky (infrastructure-wide IP bans for violation of rules against one or many hosts) we've added a dashboard to both manage the rules and blocked IPs. Github experiment ----------------------- Nothing material to report. Things seem to be largely 'just working' We are working on adding an incubator project to the github experiment - we expect this will push the limits of the project as there are literally thousands of incubator committers, so it should be an interesting threshold to pass and gauge our ability to cover them. [1] https://s.apache.org/A9oF ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Nick Burch] ----------------------------------------- Attachment 7: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report. ----------------------------------------- Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski] Nothing requiring board attention at this time. ----------------------------------------- Attachment 9: Report from the Apache Security Team Project [Mark J. Cox] Stats for July 2016: 10 CVEs issued to projects (some may not be public yet). e-mails to security@ 7 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to Android licenses 12 Direct Vulnerability report to security@apache.org 1 [httpd] (httpoxy) 1 [ofbiz] 1 [wicket] 1 [tika] 1 [axis] 1 [myfaces] 3 [site] (comments.apache.org valid issue addressed, 1 rejected, 1 open) 1 [ranger] 1 [blazeds] 13 Vulnerabilities reported to projects 3 [httpd] 3 [tomcat] 3 [openoffice] 1 [struts] 1 [hadoop] 1 [sling] 1 [hadoop] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] ----------------------------------------- Attachment B: Report from the Apache ACE Project [Marcel Offermans] ## Description: - Apache ACE is a software distribution framework that allows you to centrally manage and distribute modular software components, configuration data and other artifacts to OSGi based and related target systems. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Following our last release we are answering some questions and fixing bugs. Progress was slow over the summer holidays. ## Health report: - The current release seems pretty stable. There are some ongoing discussions about extending ACE. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bram de Kruijff on Mon Jul 08 2013 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Bram Pouwelse at Thu Feb 25 2016 ## Releases: - February 9th, 2016: ACE 2.1.0 release. ## Mailing list activity: - users@ace.apache.org: - 75 subscribers (up 0 in the last 3 months): - 32 emails sent to list (3 in previous quarter) - dev@ace.apache.org: - 73 subscribers (up 3 in the last 3 months): - 6 emails sent to list (12 in previous quarter) ## JIRA activity: - 9 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment C: Report from the Apache Airavata Project [Suresh Marru] ## Description: Apache Airavata is a distributed system software framework to manage simple to composite applications with complex execution and workflow patterns on diverse computational resources. ## Issues: There are no issues requiring board attention at this time. ## Activity: The community has been active. The GSOC projects are wrapping up. The project has a new website and logo, both to align with new ASF logo and demonstrate the project is indeed active :). A new release was made during this reporting period. ## Health report: - The community remained stable, no substantial changes either up or down. The GSoC students has been less productive than previous years. While we can nit-pick on students, we as mentors have not been pro-active relatively. We will hope to put more efforts in “recruiting”. - Two of the PMC members (Marlon Pierce, Suresh Marru) are teaching a graduate level class related to Apache Airavata, we hope some of the students will stir up new directions for the project. ## PMC changes: - Currently 20 PMC members. - Last PMC addition was Supun Nakandala on Mon May 18 2015. - A new PMC member is voted in and is in 72 hour board notice embargo until August 19th. ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Hasini Gunasinghe at Mon Aug 10 2015 ## Releases: - Last release was 0.16 on July 25th 2016 ## Mailing list activity: - The mailing list traffic remained constant. During the last report feedback, it was suggested to shutdown the architecture list if it is not being used. We will take the discussion up on dev list. - users@airavata.apache.org: - 107 subscribers (up 1 in the last 3 months): - 16 emails sent to list (16 in previous quarter) - dev@airavata.apache.org: - 152 subscribers (up 3 in the last 3 months): - 265 emails sent to list (469 in previous quarter) - architecture@airavata.apache.org: - 75 subscribers (up 1 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@airavata.apache.org: - 21 subscribers (up 0 in the last 3 months): - 356 emails sent to list (413 in previous quarter) ## JIRA activity: - 63 JIRA tickets created in the last 3 months - 35 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment D: Report from the Apache Ambari Project [Yusaku Sako] ## Description: - Apache Ambari simplifies provisioning, managing, and monitoring of Apache Hadoop clusters. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last board report in May 2016, the Apache Ambari community has been focused on making progress towards the upcoming release 2.4.0 on branch-2.4. This release includes many new features, bug fixes, and performance improvements with more than 2100 JIRAs resolved to date. Apache Ambari Meetup took place on June 27, 2016, with talks by Alejandro Fernandez (PMC/committer), Jayush Luniya (PMC/committer), Juanjo Marron (committer), Mithun Mathew (committer), Bhuvnesh Chaudhary (committer), Alexander Denissov (committer), Aravindan Vijayan (committer), Swapan Shridhar (committer), and Prajwal Rao (contributor). Alejandro Fernandez and Jayush Luniya also gave a talk on the activity and feature of Apache Ambari at Hadoop Summit 2016 - San Jose. ## PMC changes: - Currently 41 PMC members. - Robert Levas was added to the PMC on Sun Jun 19 2016 ## Committer base changes: - Currently 74 committers. - New commmitters: - Juanjo Marron was added as a committer on Sat Jun 25 2016 - Nitiraj Rathore was added as a committer on Wed Jul 06 2016 - Gaurav Nagar was added as a committer on Wed Jul 06 2016 - Lav Jain was added as a committer on Sun Jul 24 2016 - Mugdha Varadkar was added as a committer on Fri Jul 29 2016 - Tim Thorpe was added as a committer on Fri Jul 29 2016 ## Releases: - Last release was 2.2.2 on Fri May 06 2016 ## Mailing list activity: - As mentioned in the last board report, dev mailing list has been split into "dev" (developer discussions), "reviews" (code review requests), and "issues" (JIRA notifications). This split has been positive; it cut down unnecessary noise coming from automated notifications on "dev" so that developers can easily find emails pertaining to actual development-related questions/discussions. - dev@ambari.apache.org: - 241 subscribers (up 14 in the last 3 months): - 134 emails sent to list (5475 in previous quarter) - issues@ambari.apache.org: - 30 subscribers (up 7 in the last 3 months): - 13633 emails sent to list (8670 in previous quarter) - reviews@ambari.apache.org: - 37 subscribers (up 4 in the last 3 months): - 5022 emails sent to list (3022 in previous quarter) - user@ambari.apache.org: - 449 subscribers (up 14 in the last 3 months): - 158 emails sent to list (325 in previous quarter) ## JIRA activity: - 1487 JIRA tickets created in the last 3 months - 1363 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Ant Project [Conor MacNeill] Apache Ant Status Report - August 2016 Apache Ant is a Java based build tool along with associated tools. It consists of 4 main projects: - Ant - core and libraries (Antlibs) - Ivy - Ant based dependency manager - IvyDE - Eclipse plugin to integrate Ivy into Eclipse - EasyAnt - Ant and Ivy toolbox to support build processes The main development activity is on support of Java9 in Ant Core. This includes support of Java modules in . While working on Java9 support we had several discussions with the Java development team because of discovered bugs/changes in the JDK (e.g. changed behaviour of DateFormat.SHORT used in or invisibility of tool classes Ant uses for , and ). Work is ongoing. o Release Status Core Ant 1.9.7 was release on April 12th, 2016 Ivy Ivy 2.4.0 was released on December 26, 2014 Ivy-DE 2.2.0 was released on November 22, 2013 EasyAnt The current release is still from the Incubator 0.9-Incubating. o Committers and PMC No new committers or PMC members this year. Jean-Louis Boudart was added to the PMC on Dec 6th, 2013 Stephen Haberman was made a committer on October 12th, 2015 o Community Mailing list numbers are relatively stable over the last month. Everything is healthy but with low activity. Stats from reporter.a.o: - Currently 29 committers and 21 PMC members - dev@ant.apache.org: - 299 subscribers (down -3 in the last 3 months): - 69 emails sent to list (119 in previous quarter) - ivy-user@ant.apache.org: - 359 subscribers (down -7 in the last 3 months): - 20 emails sent to list (6 in previous quarter) - notifications@ant.apache.org: - 64 subscribers (down -1 in the last 3 months): - 384 emails sent to list (258 in previous quarter) - user@ant.apache.org: - 710 subscribers (down -4 in the last 3 months): - 22 emails sent to list (41 in previous quarter) Please note that this report was largely prepared by Jan Materne whom we will be recommending to the board be appointed as the next chairman of the Apache Ant PMC ----------------------------------------- Attachment F: Report from the Apache Attic Project [Henri Yandell] The Attic is where projects slumber when their communities fade away. Continuum has moved to the Attic. Bloodhound and Etch are in the process of moving to the Attic. The Axis PMC have asked for assistance in moving Axis v1 to the Attic. Activity is low. The Attic could use some energy towards generating advice on how to keep out of the Attic, some more energy on the mundane clean up work, and energy on encouraging energy. ## PMC changes: - Currently there are 20 PMC members. - Last PMC addition was Herve Boutemy on Sat Jul 18 2015 ## Mailing list activity: - general@attic.apache.org: - 35 subscribers (up 0 in the last 3 months): - 107 emails sent to list (168 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 G: Report from the Apache Axis Project [Deepal Jayasinghe] ----------------------------------------- Attachment H: Report from the Apache Bahir Project [Luciano Resende] Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark. Community Activity: Apache Bahir community has been actively working on supporting and enhancing previously available Apache Spark extensions and also creating new ones. The community has recently contributed a new structured streaming extension for MQTT. The Apache Flink project has reached out to the Bahir mailing list and discussions are under way to have Flink extensions being developed at Bahir. The Apache Bahir 2.0.0 release has just been approved and it provides support for Apache Spark 2.0.0. Issues: * No known issues Releases: 08/11/2016 - Bahir 2.0.0 07/02/2016 - Bahir 2.0.0-preview Committers or PMC changes: * None Trademark/Branding: * No known issues. Legal Issues: * None ----------------------------------------- Attachment I: Report from the Apache BookKeeper Project [Sijie Guo] BookKeeper is a distributed, reliable, and high performance logging service. It has been used as a fundamental service to build high available and replicated services in large companies like Twitter, Yahoo and Salesforce. It is also the log segment store for Apache DistributedLog (incubating). ## Issues: - there are no issues requiring board attention at this time ## Activity: - The 4.4.0 has been release on May 16th 2016. - The community is working on releasing 4.5.0. The 4.5.0 release is targeted on merging major changes from different companies, including Twitter, Yahoo and Salesforce. - Salesforce hosted the last bookkeeper meetup on the 28th Jun 2016 ## Health report: - The community has been stable. ## PMC changes: - Currently 8 PMC members. - Matteo Merli was added to the PMC on Wed May 25 2016 ## Committer base changes: - Currently 11 committers. - New commmitters: - JV Jujjuri was added as a committer on Wed Jun 08 2016 - Jia Zhai was added as a committer on Sat Jun 04 2016 ## Releases: - Last release was 4.4.0 on May 16th 2016 ## Mailing list activity: - dev@bookkeeper.apache.org: - 73 subscribers (up 2 in the last 3 months): - 526 emails sent to list (765 in previous quarter) - issues@bookkeeper.apache.org: - 6 subscribers (up 0 in the last 3 months) - user@bookkeeper.apache.org: - 93 subscribers (up 6 in the last 3 months): - 17 emails sent to list (5 in previous quarter) ## JIRA activity: - 15 JIRA tickets created in the last 3 months - 14 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment J: Report from the Apache Brooklyn Project [Richard Downer] ## Description: - Apache Brooklyn Project is a software framework for modeling, monitoring and managing cloud applications through autonomic blueprints. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Development continues with a regular turnover of pull requests submitted and merged. - Our GSoC student Jose Carrasco is working on adding PaaS support to Apache Brooklyn. Mentor Andrea Turli reports that he is doing very well, and Jose also comments that he is learning a great deal from Andrea. ## Health report: - The project continues with a similar level of activity that we have seen recently. There is a regular turnover of pull requests and commits, and JIRA tickets, showing that development is at a healthy pace and that users are feeding back their problems and feature suggestions. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Baptiste Onofré and Olivier Lamy, who converted their mentor status to committer/PMC member on graduation. ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Jean-Baptiste Onofré and Olivier Lamy, who converted their mentor status to committer/PMC member on graduation. ## Releases: - No new releases since last report. - 0.9.0 was released on Mon Apr 18 2016 ## JIRA activity: - 57 JIRA tickets created in the last 3 months - 25 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: Report from the Apache Buildr Project [Alex Boisvert] Apache Buildr is a Ruby-based build system for Java-based applications, including support for Scala, Groovy and a growing number of JVM languages and tools. Our last release (v1.4.25) happened on April 4th, 2016. Development and community activity remains low, with only a handful of emails and Jira updates on average every month (due to low activity, activity tend to be "bursty" around releases). Our last committer/PMC change happened in October 2013. As reported previously, I (Alex Boisvert) have decided to step down as PMC Chair for the Buildr project. Following the recent vote (https://lists.apache.org/thread.html/5b3b645bd4bda001c4b9f749efea7e18aa41efa4342e0bfad45416fc@%3Cprivate.buildr.apache.org%3E), Antoine Toulme should become our next PMC Chair. I will send a resolution for the Board to approve/reject. Otherwise, we have no issues that require board attention ----------------------------------------- Attachment L: Report from the Apache Cassandra Project [Jonathan Ellis] Releases -------- 2.1.15 (7 Jul 2016) 2.2.6 (6 Jul 2016) 3.7 (14 Jun 2016) 3.0.7 (14 Jun 2016) Community --------- NGCC (Next Generation Cassandra Conference) took place in Austin, TX. Sixty committers and contributors attended. Day 1 saw presentations from engineers from Apple, DataStax, Eriksson, Instagram, The Last Pickle, Protectwise, Stratio, and Yahoo Japan. These presentations were followed on Day 2 by an unconference discussion. My notes are here [1] and videos are here [2]. O’Reilly’s Cassandra: The Definitive Guide 2nd Edition [3] is out. This is the first book to cover Cassandra 3.0. PMC & Committers ---------------- Jeff Jirsa was added as committer on 15 Jun 2016. Dave Brosius, Tyler Hobbs, and Aaron Morton were added as PMC members on 10 Jun 2016. 1 committer and 5 PMC member votes are currently in progress. [1] https://docs.google.com/document/d/1rYyJWDsiwGmc3IUNCV_AKhzUJghLwA_iWDzog-eDSSE [2] https://www.youtube.com/user/PlanetCassandra/videos [3] http://shop.oreilly.com/product/0636920043041.do ----------------------------------------- Attachment M: Report from the Apache Clerezza Project [Hasan Hasan] DESCRIPTION Apache Clerezza is an OSGi-based modular application and a set of components (bundles) for building RESTFul Semantic Web applications and services. ISSUES FOR THE BOARD There are no issues requiring board attention at this time. However, the activities in the past few months are very low. I will discuss this internally. RELEASE - Latest release was partial-release-201604 created on May 13, 2015. ACTIVITY - Fixed a bug in rdf.core COMMUNITY Latest change was addition of a new committer and PMC member on 16.08.2013 ----------------------------------------- Attachment N: Report from the Apache Cocoon Project [Thorsten Scherler] ----------------------------------------- Attachment O: Report from the Apache Community Development Project [Ulrich Stärk] ## Description: The Community Development PMC is responsible for helping people become involved with Apache projects ## Issues: No issues require board attention at the moment. ## Activity: Google Summer of Code is approaching final evaluations. 43 of our initial 49 students made it through the midterm evaluations. We will shortly start discussion about who to send to the mentor summit in October. Sharan Foga is heading our diversity efforts and succesfully held a webinar on the ASF for Hackbright Academy's students on the 28th of July. ## PMC changes: The PMC currently features 21 members. There were no additions in the past 3 months. The last addition has been Roman Shaposhnik on 2015-08-26. We expect to report some changes for the next report. ## Releases: None. ## Mailing list activity: A lot of discussion around guiding newcomers, ApacheCon and general community-related discussions are happening on dev@. Subscriber count is up in the past months, number of messages slightly down (~ 8%) which is probably just usual fluctuation. GSoC-related discussions are happening on mentors@ with number of messages fluctuating with GSoC phase. ----------------------------------------- Attachment P: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: - NoSQL document database using HTTP, JSON, and MapReduce ## Issues: - there are no issues requiring board attention at this time ## Activity: - Final, final stretches for major 2.0 release (see last report for more details) - We are currently making release candidates available on a weekly basis for larger community feedback. - We are also running a blog-post series on various 2.0-related topics, two posts a week until end of August. ## Health report: - 2.0 release preparation buzz is envigorating, the whole team is coming together coding, testing, wrapping up lose ends, finishing docs, and the wider community is reporting back their experiences with the 2.0 release candidates. Despite the usual (northern hemisphere-) summer-lull, things feel very active and exciting. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Garren Smith on Mon Oct 19 2015 ## Committer base changes: - Currently 54 committers. - Nick Vatamaniuc was added as a committer on Thu Jun 16 2016 ## Releases: - Last release was 1.6.1 on Wed Sep 03 2014 ## Mailing Lists - Business as usual ## JIRA activity: - 81 JIRA tickets created in the last 3 months - 39 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache Creadur Project [Brian E Fox] Apache Creadur creates and maintains a suite of open source software related to the auditing and comprehension of software distributions. Any language and build system are welcomed. Status ------ Since the last report, email and commit activity continues to move along slowly. There has been not much other activity. The .12 release was finally done in June Creadur is primarily used by other Apache projects to help check for conformity to ASF standards. This is why the project team is primarily comprised of members and committers from other ASF projects. The risk of the project foundering is therefore very low despite the ongoing lack of progress. If someone has an itch to scratch, it will no doubt get fixed. Community --------- The last committer was elected in August, 2012. In September 2013 Phil Ottlinger was elected to join the PMC. There was recently a discussion about adding a new committer/pmc member. The vote just needs to be started. Releases -------- Apache Rat 0.12 was released in June, 2016 Apache Rat 0.11 was released in August, 2014 Apache Rat 0.10 was released in September, 2013. Community Objectives -------------------- Find more committers ----------------------------------------- Attachment R: Report from the Apache CXF Project [Daniel Kulp] ## Description: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. There are also two sub-projects that leverage CXF: - Fediz - Fediz helps you to secure your web applications via the standard WS-Federation Passive Requestor Profile. - DOSGi - is the reference implementation of the Distribution Provider component of the OSGi Remote Services Specification ## Issues: There are no issues requiring board attention at this time ##Releases - 3.0.10 was released on August 8, 2016 - 3.1.7 was released on August 8, 2016 ## Activity: This quarter was primarily spent fixing bugs for 3.1.7 and getting that stabilized. 3.1.7 also introduced better spring-boot support which has been asked for by several users. We received several contributions toward that goal and we are hoping the contributions from those individuals will continue in hopes of getting a new committer or two from it. Fediz 1.3.1 is under vote now with some minor fixes as well as upgrading to CXF 3.1.7. 1.2.3 should be released soon as well. DOSGi 2.0 is being worked on with hopes of releasing it by the end of the quarter. The major change here is the split with the "abstract API's" moving to Apache Aries and the CXF DOSGi being an implementation of the API's based on CXF. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andriy Redko on Tue Sep 09 2014 ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Francesco Chicchiricco at Mon Nov 30 2015 It has been a while since the last committer addition. We're hoping some of the new spring-boot contributions can lead to a new committer. In general, however, CXF is a mature project implementing mature specs. ----------------------------------------- Attachment S: Report from the Apache DeltaSpike Project [Thomas Andraschko] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans outside of a container. - JSF integration, including backporting of JSF 2.2 features for Java EE 6. - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. - Quartz integration Testing support is also provided, to allow you to do low level unit testing of your CDI enabled projects. ## Issues: There are no issues requiring board attention at this time. ## Activity: We receive contributions from the community on a regular basis. For 1.7.0 we did a lot of improvements in the Data-Module like performance enhancements and support of Java8 features like Streams and Optional. We also did a some minor improvements and bugfixes in other modules. For 1.7.1 we also applied a lot of PullRequests from non-committers at GitHub. ## Health report: The community and developers activity was average in the last quarter. ## PMC changes: - Currently 19 PMC members. - Harald Wellmann was added to the PMC on Thu May 19 2016 ## Committer base changes: - Currently 33 committers. - Matej Novotny was added as a committer on Fri Jun 03 2016 ## Releases: - 1.7.0 was released on Sun Jun 19 2016 - 1.7.1 was released on Wed Jul 20 2016 ## Mailing list activity: - users@deltaspike.apache.org: - 174 subscribers (up 1 in the last 3 months): - 137 emails sent to list (114 in previous quarter) - dev@deltaspike.apache.org: - 108 subscribers (up 0 in the last 3 months): - 627 emails sent to list (523 in previous quarter) ## JIRA activity: - 49 JIRA tickets created in the last 3 months - 52 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache DeviceMap Project [Radu Cotescu] ## Description: - Device Data Repository and classification API (established November 2014) ## Issues: - There are no issues requiring board attention at this time ## Activity: - The project's activity decreased drastically after the PMC had reached the minimal viable number of PMC members. ## Health report: - The project is still minimally viable, with 3 active PMC members, but at risk if anyone leaves without new PMC members being elected. ## PMC changes: - Currently 3 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bertrand Delacretaz on Wed Nov 19 2014 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Volkan Yazici at Thu Apr 23 2015 ## Releases: - No releases in the past 3 months ## Mailing list activity: - dev@devicemap.apache.org: - 58 subscribers (up 0 in the last 3 months): - 24 emails sent to list (21 in previous quarter) ## JIRA activity: - 0 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Drill Project [Parth Chandra] ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last board report, Drill has released version 1.7 - The focus of the releases continues to be on stability and performance. - We've seen a nice trend in design discussions with developers writing detailed design documents that is leading to good feedback. - Work is in progress on multiple features including dynamic loading of UDF's, resource management with YARN, enhanced security, improved use of statistics, and performance of reading parquet files. A large part of these are being done by new contributors. ## Health report: - We are continuing to add new users at a steady pace with a healthy number of emails being posted by new users. - The developer community has seen a small growth in the number of people providing new contributions both in code and in the discussions. As indicated above, we hope to see larger contributions from some of the new contributors. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Hanifi Gunes on Thu Feb 11 2016 ## Committer base changes: - Currently 28 committers. - No new committers added in the last 3 months - Last committer addition was Hsuan-Yi Chu at Thu Apr 07 2016 ## Releases: - 1.7.0 was released on Mon Jun 27 2016 ----------------------------------------- Attachment V: Report from the Apache Empire-db Project [Rainer Döbele] Empire-db board report August 2016 Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. # Progress of the project Over the last months we have collected various improvements and some new features that will justify the publication of a new release. # Changes in committers or PMC members This quarter we have promoted 3 committers who have not been pmc members to become members of our pmc. # Issues There are no issues that require the board's attention at this time. # Releases Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015. ----------------------------------------- Attachment W: Report from the Apache Flume Project [Jarek Jarcec Cecho on behalf of Hari Shreedharan] DESCRIPTION Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. RELEASES * The last release of Flume was version 1.6.0, released on May 20, 2015. * Next release 1.7.0 has been discussed in the community but precise date has not been set yet. CURRENT ACTIVITY: * A total of 59 issues have been filed, and 67 issues have been resolved in last three months. * Approximately 1164 messages were exchanged on the dev list in the past three months, while a total of 124 were exchanged on the user list in this period. COMMUNITY * The last time a new committer was added to the project was on June 19, 2015. * The last time a new PMC member was elected for the project was on November 4, 2014. * Currently there are: - Total of 285 subscribers to the developer list - Total of 680 subscribers to the user list - Total of 26 committers - Total of 21 PMC members ISSUES * There are no issues requiring board attention at this time. ----------------------------------------- Attachment X: Report from the Apache Forrest Project [David Crossley] Apache Forrest mission is software for generation of aggregated multi-channel documentation maintaining a separation of content and presentation. Issues needing board attention: None. Changes in the PMC membership: None. Last modified: 2013-04-08 Most recent addition: 2009-06-09 New committers: None. Most recent addition: 2009-06-09 None on the horizon. General status: The most recent release is 0.9 on 2011-02-07. Since then there have been some changes, but it will need someone to initiate the release process. No activity on the user mail list. However it never gets used much anyway. There was some activity on the dev mail list, with two PMC members participating: One committer commenced an additional skin based on the Bootstrap framework. Another committer assisted a little. I am surprised that there was not any other comment. Two PMC members were present during the quarter. At this report, four other PMC members responded to my draft report. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision or encourage new contributors. Project status: Activity: Low 3+ people have indicated presence, so has sufficient oversight. Security issues published: None. Progress of the project: Initial Bootstrap-based skin. Improved documentation to link to the new lists.apache.org interface. ----------------------------------------- Attachment Y: Report from the Apache Giraph Project [Avery Ching] Giraph is a Bulk Synchronous Parallel framework for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. Project releases * Sergey and Roman are working on the new 1.2 release in the later part of 2016 that includes the Blocks & Pieces framework and OOC processing. This is the first release since Nov 2014 (1.1.0) so we are working out the issues and hope to made more frequent releases after we iron out the process. Overall project activity since the last report * Redesigned out-of-core mechanism, made it more performant and automated. It is running in production at Facebook. * Made it possible to store all partition data in a serialized form, to allow scaling to larger number of vertices (10s of billions) * Added FacebookConfiguration with all the recommended Giraph settings, to make it easier to get great performance * Moved partition exchange off of Zookeeper, making it possible to use arbitrarly large number of partitions * Continued bug fixes When were the last committers or PMC members elected? * We recently added a new committer and PMC member! ** Hassan Eslami on 7/15/2016 ** Sergey Edunov on 8/15/2016 Mailing list members * Our mailing list is stable (not much change from the last report) ** user@ 473 → 470 ** dev@ 280 → 280 ----------------------------------------- Attachment Z: Report from the Apache Gora Project [Lewis John McGibbney] The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key value stores, document stores and RDBMSs, and analyzing the data with extensive Apache Hadoop MapReduce support. ## Issues: There are no issues requiring board attention at this time. ## Activity: Gora development has mainly involved GSoC efforts with two projects this year. This is the fourth or fifth year Gora has participated in GSoC and the work is going very well. Othe aspects of the community have been reasonably quiet however we are very close to a release now. In recent months we have added a number of modules to the codebase from external contributors. ## Health report: There are ideas to present some of the community work at the forthcoming ApacheCon EU. An update on Gora was presented a while back at the NASA JPL Open Developer Meetup in Pasadena, CA, U.S.A ## PMC changes: - Currently 22 PMC members. - Pierre Sutra was added to the PMC on Mon Jun 13 2016 ## Committer base changes: - Currently 22 committers. - Pierre Sutra was added as a committer on Sat May 21 2016 ## Releases: - Last release was 0.6.1 on Mon Sep 14 2015 ## Mailing list activity: dev@ continues to see the overwhelming majority of the community traffic. This is a continuing trend with user@ seeing very low amounts of traffic. - dev@gora.apache.org: - 74 subscribers (up 0 in the last 3 months): - 267 emails sent to list (188 in previous quarter) - user@gora.apache.org: - 75 subscribers (up 1 in the last 3 months): - 11 emails sent to list (25 in previous quarter) ## JIRA activity: - 7 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Groovy Project [Guillaume Laforge] ## Description: Apache Groovy is a multi-faceted programming language for the Java platform. Groovy is a powerful, optionally typed and dynamic language, with static- typing and static compilation capabilities, aimed at multiplying developers’ productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain- Specific Language authoring, runtime and compile-time meta-programming and functional programming. ## Issues: The groovy-lang.org has been transferred to the Apache Software Foundation. We still have the dichotomy between the groovy-lang.org website, and groovy.apache.org which is still pointing at groovy-lang.org. ## Activity: We made a new release on June 7th, with version 2.4.7. We're still investigating how to make more automatic releases, some experiments have started in this area, during the Gradle Summit conference. This quarter, we got 22 contributors to the codebase, including 15 non-committers, 6 of which were new. ## Health report: Compared to last year's 12.7M downloads, up until July, we are already at 12M downloads for the first 7 months of the year (across both Maven Central and Bintray JCenter). We have a bit more users (7% increase) on the users list, but the number of posts has decreased. The summer period is often a bit less busy, so probably not worrying. However we have a bit more trafic on the dev list, indicating more discussions going on, which is good. Less tickets opened compared to last quarter, but more tickets closed. In terms of social presence, Groovy is 16th in the TIOBE language index. The @ApacheGroovy twitter account reached 1758 followers, compared to last quarter's 1475 (19% increase) The GR8Conf Europe & US 2016 conferences have taken place, and the next dedicated event will be the G3 Summit in December. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrew Bayer on Wed Nov 18 2015 ## Committer base changes: - Currently 16 committers. - No new changes to the committer base since last report. ## Releases: - 2.4.7 was released on Tue Jun 07 2016 - 2.4.6 was released on Feb 22 2016 - 2.4.5 was released on Sept 17 2015 - 2.4.4 was released on Jul 09 2015 - 2.4.3 was released on Mar 23 2015 ## Mailing list activity: - users@groovy.apache.org: - 374 subscribers (up 26 in the last 3 months): - 319 emails sent to list (404 in previous quarter) - dev@groovy.apache.org: - 209 subscribers (up 3 in the last 3 months): - 269 emails sent to list (208 in previous quarter) - issues@groovy.apache.org: - 9 subscribers (up 0 in the last 3 months) - notifications@groovy.apache.org: - 28 subscribers (up 1 in the last 3 months): - 954 emails sent to list (836 in previous quarter) ## JIRA activity: - 66 JIRA tickets created in the last 3 months - 74 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache Hama Project [Edward J. Yoon] ## Description: - Apache Hama is a framework for Big Data analytics which uses the Bulk Synchronous Parallel (BSP) computing model, which was established in 2012 as a Top-Level Project of The Apache Software Foundation. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Added float 32/16 writable - Migrated Hama streaming github project ## Health report: - The community has been somewhat inactive recently (maybe effect of state-of-the-art cheap clouds?), but I'm (edward) working on neural networks, streaming analytics using Hama on real products, and expect we'll grow again. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Behroz Sikander on Mon Feb 01 2016 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Behroz Sikander at Wed Feb 03 2016 ## Releases: - Last release was hama-0.7.1 on Mon Mar 14 2016 ## Mailing list activity: The mailing list is inactive at the moment, but will reopen as soon as something exciting happens. - dev@hama.apache.org: - 115 subscribers (up 1 in the last 3 months): - 75 emails sent to list (116 in previous quarter) - user@hama.apache.org: - 187 subscribers (up 1 in the last 3 months): - 1 emails sent to list (13 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AC: Report from the Apache Helix Project [Kishore Gopalakrishna] A cluster management framework for partitioned and replicated distributed resources ## Issues: - No feature requests from users stalling the project development. ## Activity: - low. ## Health report: - No active development in the project but members are active and respond to questions. LinkedIn has modified the task framework and plan to contribute it back to the project. We plan to create a new release in next 2 months. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Terence Yim on Tue Dec 17 2013 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Lei Xia at Tue May 10 2016 ## Releases: - Last release was 0.6.5 on Tue Mar 24 2015 ## Mailing list activity: - dev@helix.apache.org: - 69 subscribers (up 3 in the last 3 months): - 40 emails sent to list (35 in previous quarter) - user@helix.apache.org: - 97 subscribers (up 5 in the last 3 months): - 9 emails sent to list (34 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AD: Report from the Apache HTTP Server Project [Eric Covener] ## Description: The Apache HTTP Server Project develops and maintains an open-source HTTP server for modern operating systems. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Recent focus has been on the backlog of security reports. ## Health report: - Relatively quiet summer, but there is activity from several committers and releases are on the horizon. - EOL timeline for 2.2.x series was announced during 2.4.23 release. ## PMC changes: - Currently 44 PMC members. - No PMC changes. Jean-Frederic Clere was added to the PMC on Tue Nov 24 2015 (last PMC addition) ## Committer base changes: - Currently 116 committers. - Jacob Champion was added on Thu Jul 07 2016 ## Releases: - 2.4.23 was released on July 05, 2016 - 2.2.x: no releases Last Release: 2.2.31 was released July 16, 2015 (EOL announced during 2.4.23) ----------------------------------------- Attachment AE: Report from the Apache HttpComponents Project [Asankha Perera] ## Description: - The Apache HttpComponents project is responsible for creating and maintaining a toolset of low-level Java components focused on HTTP and associated protocols ## Issues: - There are no issues requiring board attention at this time ## Activity: - We are currently working on adding support for HTTP/2 protocol to HttpCore and HttpClient. ## Health report: - Overall the project remains active. Although established in late 2007 the project remains stable and active as seen by JIRA and Emails. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Mon Aug 24 2015 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Wed Oct 22 2014 ## Releases: - HttpAsyncClient 4.1.2 GA was released on Mon Jun 27 2016 - HttpCore 4.4.5 GA was released on Tue Jun 14 2016 ## Mailing list activity: - dev@hc.apache.org: - 190 subscribers (up 1 in the last 3 months): - 378 emails sent to list (312 in previous quarter) - httpclient-users@hc.apache.org: - 574 subscribers (up 8 in the last 3 months): - 89 emails sent to list (176 in previous quarter) ## JIRA activity: - 29 JIRA tickets created in the last 3 months - 26 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AF: 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/08/05 the community released Ignite 1.7.0 with a big number of improvements, including non-collocated distributed SQL joins - Community started discussions about Ignite 2.0 on the dev list: https://s.apache.org/ignite2.0 ## Health report: - Ignite keeps attracting new contributors on the mailing list - Ignite chatroom member list continuously grows ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 monthss - Last PMC addition was Denis Magda on Sun Sep 27 2015 ## Committer base changes: ## Committer base changes: - Currently 29 committers. - New commmitters: - Pavel Tupitsyn was added as a committer on Thu Jun 16 2016 - Vladisav Jelisavcic was added as a committer on Thu Jun 02 2016 ## Releases: - 1.6.0 was released on Mon May 23 2016 - 1.7.0 was released on Fri Aug 05 2016 ## Mailing list activity: - Mailing list activity keeps growing quarter to quarter - dev@ignite.apache.org: - 201 subscribers (up 17 in the last 3 months): - 1873 emails sent to list (1539 in previous quarter) - issues@ignite.apache.org: - 25 subscribers (up 4 in the last 3 months): - 4619 emails sent to list (3771 in previous quarter) - user@ignite.apache.org: - 312 subscribers (up 52 in the last 3 months): - 2078 emails sent to list (1797 in previous quarter) ## JIRA activity: - 546 JIRA tickets created in the last 3 months - 367 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AG: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for August 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 59 podlings currently undergoing incubation. We added two podlings to the roster and have no graduations this month. July was a quiet month, completing four releases and no other major activities. * Community New IPMC members: - None People who left the IPMC: - None * New Podlings - SensSoft - Traffic Control * Graduations The board has motions for the following: - None * Releases The following releases entered distribution during the month of July: - Apache Trafodion 2.0.1-incubating - Apache Atlas 0.7-incubating - Apache Ranger 0.6.0-incubating - Apache Eagle 0.4.0-incubating * Legal / Trademarks - See also: Fluo's report * Credits - Report Manager: John D. Ament -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - CarbonData - DistributedLog - Juneau - Pirk - Pony Mail - SensSoft - Trafic Control * Not yet ready to graduate No release: - Blur - CMDA - Guacamole - Impala - iota - PredictionIO - Quickstep - S2Graph Community growth: - Beam - Eagle - Fluo - Joshua - Slider - SystemML * Did not report, expected next month - Fineract - Quarks ---------------------------------------------------------------------- Table of Contents BatchEE Beam Blur CarbonData Climate Model Diagnostic Analyzer DistributedLog Eagle Fluo Guacamole Impala iota Joshua Juneau OpenAz Pirk Pony Mail PredictionIO Quickstep S2Graph SensSoft Sirona Slider SystemML Tamaya Toree Traffic Control Unomi ---------------------------------------------------------------------- -------------------- BatchEE BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification. BatchEE has been incubating since 2013-10-03. Three most important issues to address in the move towards graduation: None, as the PPMC feels the project is ready to graduate 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 got several new users and interest in advanced integration (in particular our GUI). How has the project developed since the last report? Not much but it is quite stable and no new spec was out since last report so it behaves as expected. BatchEE is used in TomEE and many industry projects. So we also get feedback in indirect ways via TomEE, Geronimo, etc. Date of last release: 2015-12-08 batchee-0.3-incubating When were the last committers or PMC members elected? * Reinhard Sandtner on 2015-12-01 Signed-off-by: [ ](batchee) Jean-Baptiste Onofré [ ](batchee) Olivier Lamy [X](batchee) Mark Struberg Shepherd/Mentor notes: struberg: I think this podling is ready to graduate. -------------------- Beam Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the mechanics of large-scale batch and streaming data processing and can run on a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in different languages, allowing users to easily implement their data integration processes. Beam has been incubating since 2016-02-01. Three most important issues to address in the move towards graduation: 1. Additional and continued Beam releases 2. Grow the community of Beam users and contributors 3. Add to and improve upon documentation, code samples, and project 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? * 425 closed/merged pull requests * High engagement on dev and user mailing lists (590 / 455 messages) * Several public talks, articles, and videos including: * Hadoop Summit San Jose ("Apache Beam: A Unified Model for Batch and Streaming Data Processing" & "The Next Generation of Data Processing & OSS") * O’Reilly & The New Stack ("Future-proof and scale-proof your code") * QCon NY ("Apache Beam: The Case for Unifying Streaming API's") * JBCN Barcelona ("Introduction to Apache Beam") How has the project developed since the last report? Major developments on the project since last report include the following: * First incubating release (0.1.0-incubating) * Second incubating release (0.2.0-incubating) * Addition of Apache Beam Python SDK * Addition of the Apache Gearpump runner * Added support for writing to Apache Kafka clusters * Added support for reading from and writing to Java Message Services, including Apache ActiveMQ, GeronimoJMS, and RabbitMQ * Ratified new Beam model APIs to improve efficiency and failure handling: DoFn setup, teardown, and reuse * Optimized key components such as data serialization and shuffle * Continued improvements to the Flink, Spark, and Dataflow runners * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing Date of last release: * 2016/06/15 - 0.1.0-incubating * 2016/08/08 - 0.2.0-incubating) When were the last committers or PMC members elected? N/A - no changes since last report. Signed-off-by: [X](beam) Jean-Baptiste Onofre [ ](beam) Venkatesh Seetharam [X](beam) Bertrand Delacretaz [X](beam) Ted Dunning -------------------- Blur Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur has been incubating since 2012-07-24. Three most important issues to address in the move towards graduation: 1. Greater community involvement. 2. Produce releases. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? Subscriptions: user@ - 61[0]; dev@ - 79[+1] The community involvement has not really changed over the past few months. How has the project developed since the last report? - Not much has changed, a few bug fixes. Date of last release: 2014-07-29 When were the last committers or PMC members elected? 2014-07-28 Signed-off-by: [ ](blur) Doug Cutting [X](blur) Patrick Hunt [x](blur) Tim Williams -------------------- CarbonData Apache CarbonData is a new Apache Hadoop native file format for faster interactive query using advanced columnar storage, index, compression and encoding techniques to improve computing efficiency, in turn it will help speedup queries an order of magnitude faster over PetaBytes of data. CarbonData has been incubating since 2016-06-02. Three most important issues to address in the move towards graduation: 1. Prepare first CarbonData release 2. Prepare first CarbonData website 3. Promote the project and grow user and dev community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? We voted two new committers: Venkata Ramana and Ravindra Pesala. We are preparing the CarbonData website, blog posts and talks to promote CarbonData and grow the user and dev communities. The community activity increased: many new users started to use and test CarbonData, we had more than 100 new issues created during July. On the other hand, presentation material has been created and a first talk has been given: http://www.slideshare.net/liangchen18/apache-carbondatanew-high-performance-d ata-format-for-faster-data-analysis How has the project developed since the last report? Code donation has been done and all resources have been created by INFRA (git, github mirror, mailing list, Jira, ...). We also created the Jenkins CI jobs. We are now in the process of cleanup and polishing the build and legal to prepare the first release. Date of last release: Not yet available When were the last committers or PMC members elected? 2016-07-15 Signed-off-by: [ ](carbondata) Henry Saputra [X](carbondata) Jean-Baptiste Onofre [X](carbondata) Uma Maheswara Rao G -------------------- Climate Model Diagnostic Analyzer CMDA provides web services for multi-aspect physics-based and phenomenon- oriented climate model performance evaluation and diagnosis through the comprehensive and synergistic use of multiple observational data, reanalysis data, and model outputs. Climate Model Diagnostic Analyzer has been incubating since 2015-05-08. Three most important issues to address in the move towards graduation: 1. Enlarge the CMDA community; 2. Develop stable platform to allow broad contributors to turn in code; 3. Develop a streamline procedure to allow the entire community to develop the CMDA project Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? In this month, the CMDA community focuses on developing the summer school program, in order to advocate and distribute CMDA 2.0, to educate more students on our latest product, and to attract more people to join our community. So far, we have received about 25 graduate students who show interest and will come to our summer school to learn CMDA 2.0 product and the platform. Meanwhile, with the great guidance from our mentors, the CMDA community has learned to run the project from various aspects in an Apache way. Many community meetings were held to streamline and develop our operation regulations. Here we just name a few strategies. Weekly community meetings are arranged with pre-distributed meeting agenda. Meeting invites are sent to all community members with open access to the weekly meetings. After each community meeting, various contributors/groups summarize their to-do items on the community mailing list, to welcome all community members' input. Community communication always adopts the community mailing list as carrier. More committers join the voting group. More committers are recommended based on their active performance in the community. How has the project developed since the last report? We have successfully encapsulated and deployed CMDA 2.0 onto Amazon cloud environment, leveraging docker technology to ensure scalability. Provenance engine is also deployed onto Amazon cloud to ensure that we gather all provenance during the summer school for further study and development of our project after the summer school. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? Signed-off-by: [ ](climatemodeldiagnosticanalyzer) James W. Carman [X](climatemodeldiagnosticanalyzer) Chris Mattmann [ ](climatemodeldiagnosticanalyzer) Michael James Joyce [ ](climatemodeldiagnosticanalyzer) Kim Whitehall [ ](climatemodeldiagnosticanalyzer) Gregory D. Reddin Shepherd/Mentor notes: * Chris Mattmann - The community has shown progress in addressing a near vote to terminate the podling. There were and still are concerns that need to be tended to and watched but as a mentor I am pleased by the efforts of Jia, Seungwon, and Lei whom I have seen contribute to the discussion. I think we should continue to closely evaluate the progress, but I am happy with this month. * Drew Farris - Three mentors active on the mailing lists. Kudos to Chris to the amount of engagement here. After choosing to avoid retirement the community is taking concrete steps to increase its engagement with ASF by establishing a web presence at Apache, creating committer accounts, preparing code for contribution and moving processes to the mailing lists. This podling is moving to a monthly reporting cycle for the next three months progress can be monitored closely. -------------------- DistributedLog DistributedLog is a high-performance replicated log service. It offers durability, replication and strong consistency, which provides a fundamental building block for building reliable distributed systems. DistributedLog has been incubating since 2016-06-24. Three most important issues to address in the move towards graduation: * Getting an Apache release out * Improve general documentation * Grow user base Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There is currently no issue. How has the community developed since the last report? * A few people have started to report issues * Some conversations have been initiated on the mailing list * Sijie will be present at Strata in China to present the project How has the project developed since the last report? * The wiki has been set up (cwiki.apache.org/confluence/display/DL/) * A few contributions were made to the repository on GitHub and are in the process of being merged * Various mailing lists have been set up * SGA from Twitter has been completed * Status page is up and we have started filling it out * Most accounts of initial committers have been created * Jira queue has been created (https://issues.apache.org/jira/browse/DL) * Repository has been created (and mirrored on GitHub) Signed-off-by: [x](distributedlog) Flavio Junqueira [x](distributedlog) Chris Nauroth [ ](distributedlog) Henry Saputra Shepherd/Mentor notes: Flavio Junqueira: Project has been progressing well. All three mentors have been actively participating in bringing the project up to speed and helping out with issues. Several contributors have expressed interest in the project and there is some initial discussion around issues, improvements, and new features. I'm personally happy with the progress. -------------------- Eagle Apache Eagle (incubating) is an open source analytics solution for identifying security and performance issues instantly on big data platforms, e.g. Apache Hadoop, Apache Spark etc. It analyzes data activities, Yarn application, Hadoop JMX metrics and daemon logs etc., provides state-of-the-art alert engine to identify security breach, performance issues and shows insights. Eagle has been incubating since 2015-10-26. Three most important issues to address in the move towards graduation: 1. Eagle community is discussing graduation and use Apache maturity assessment to measure the gap to graduation. That should be completed, see https://cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Ass essment 2. Complete one requirement from self assessment which is to provide a well-documented channel to report security issues, along with a documented way of responding to them. 3. Identify other housekeeping before graduation, for example agreement on bylaws, PMC composition etc. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? NIL How has the community developed since the last report? - Presented in Apache Con, May 2016 - Presented in London Stratus + Hadoop, May 2016 - Presented in San Jose Hadoop Summit, June 2016 - Presented in DTCC2016 Beijing, China, May 2016 - Presented in JavaCon, China, May 2016 - Presented in Hadoop Summit, San Jose, China, June 2016 - Presented in Data Asset Management Summit, Shanghai, China, July 2016 Communities showed continuous interest in Apache Eagle project. Some company tried to integrate Eagle as part of whole solution and some contributed different use case to Eagle platform, for example MapR support, Oozie monitoring support etc. How has the project developed since the last report? Technically we added more documents for user to easily use Eagle Besides Hadoop security monitoring, we have started working on performance monitoring design and development based on the requests from community. As we may have multiple different use cases running on top of Eagle, a design discussion and prototype is conducted to make sure Eagle is a framework to host multiple use cases and user will use Eagle to manage those use cases. Alert engine is going to be decoupled from data processing so that alert engine will be multi-tenant and easy to be used by multiple use cases by incorporating well-designed metadata. Date of last release: 2016-07-19 When were the last committers or PMC members elected? - Daniel Zhou, 2016-06-15 - Michael Wu, 2016-06-17 Signed-off-by: [ ](eagle) Owen O'Malley [ ](eagle) Henry Saputra [x](eagle) Julian Hyde [x](eagle) P. Taylor Goetz [x](eagle) Amareshwari Sriramdasu -------------------- 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. Do a release 3. Conduct a podling name search Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? We have a new contributor to Fluo since the last report. How has the project developed since the last report? We completed refactoring of code to use Apache names. We attempted our first release of a parent pom (for both Fluo projects) and it failed on the incubator list. A parent pom is a way to share build configuration among multiple projects. We plan for Fluo and Fluo Recipes to both inherit the same parent pom and obtain common config for code formatting, findbugs, checkstyle rules, etc. For this to work the parent pom needs to be released before the projects. The reason it failed is because members of the IPMC identified the following issues : * Improper linking to pre-Apache releases of Fluo from website. * Branding and linking issues with fluo.io domain, fluo-io GitHub org and projects. The domain name and github org were used by the project before moving to Apache. This was really good feedback. We want to remedy the issues identified and eliminate possible confusion around the Apache Fluo brand. The following link identifies discussion of a possible way forward. https://lists.apache.org/thread.html/b478645815bf7b1fee8342a21924162decc173d9 1c22eaf5f708a435@%3Cdev.fluo.apache.org%3E 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: JE: There was a very heavy discussion on branding spurred from the attempted VOTE thread. In the end, I believe this was a very positive discussion and resulted in fixing many branding issues. I believe most of them were due to the transition from an independent Github community to Apache (which included bringing the website). The PPMC has been extremely responsive to incubator feedback and I am very happy with the level of response they spearheaded (without mentor prodding/coaxing). -------------------- Guacamole Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway. Combined with cloud hosting, Guacamole provides an excellent alternative to traditional desktops. Guacamole aims to make cloud-hosted desktop access preferable to traditional, local access. Guacamole has been incubating since 2016-02-10. Three most important issues to address in the move towards graduation: 1. Making the first Guacamole release under the Apache Incubator 2. Encouraging community participation and contribution 3. Accepting additional committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Activity on the mailing lists has increased now that the new project website is up. At the time of the last report, the @user list was unused. Since then, the number of emails has increased each month, with 52 in May, 95 in June, and 123 in July. Users do still occasionally post to the old SourceForge forums, but are then gently redirected to the mailing lists. Excluding project committers, the community has opened 5 pull requests, 2 of which have been merged. How has the project developed since the last report? The project has finished migrating to Apache infrastructure, including the project website. There is one major outstanding task, screen sharing, which has been blocking the release but is finally nearing completion. Since last report, the project has had roughly 250 commits, about 60% of which were directly related to the outstanding task mentioned above. Date of last release: 2015-12-18 (0.9.9, prior to Apache Incubator) When were the last committers or PMC members elected? The most recent committer, Frode Langelo, was accepted into the project by VOTE on 2016-04-03, with the required ICLA received on 2016-04-05. Signed-off-by: [x](guacamole) Jean-Baptiste Onofre [ ](guacamole) Daniel Gruno [ ](guacamole) Olivier Lamy [X](guacamole) Jim Jagielski [X](guacamole) Greg Trasuk -------------------- Impala Impala is a high-performance C++ and Java SQL query engine for data stored in Apache Hadoop-based clusters. Three most important issues to address in the move towards graduation: 1. Transition of development workflows to ASF (see https://issues.cloudera.org/browse/IMPALA-3221) 2. Initial release as incubating project. 3. Community growth Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? No. How has the community developed since the last report? Our last report was in April. Since then * Six new contributors have submitted patches for review, and two contributors new to the project since incubation have continued to send patches. * Mailing list activity more than doubled in the four months since our last report compared to the four months before that, from 31 threads to 75 threads (excluding patch review comments) How has the project developed since the last report? * The podling name search was completed: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-96 * Trademark handoff was completed * Impala's git repository is now hosted on ASF infrastructure * Impala's website's source is hosted on ASF’s git infrastructure and the website is now available on https://impala.apache.org * Project bylaws have been ratified: https://impala.apache.org/bylaws.html * Developer documentation has started to move to the ASF-hosted wiki: https://cwiki.apache.org/confluence/collector/pages.action?key=IMPALA * Work has begun in migrating to ASF-hosted JIRA * A patch changing the copyright headers is in review Date of last release: No releases have been made yet. When were the last committers or PMC members elected? No committers or PMC members have been added since incubation began. Signed-off-by: [X](impala) Tom White [ ](impala) Todd Lipcon [ ](impala) Carl Steinbach [ ](impala) Brock Noland -------------------- iota Open source system that enables the orchestration of IoT devices. iota has been incubating since 2016-01-20. Three most important issues to address in the move towards graduation: 1. Building a community now that we have completed source code upload of one for the main components of the system. 2. Moving towards an initial release before the end of the year 3. Working on IP clearance for the release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? A number of individuals have made contributions some of which have been incorporated. We need to encourage more discussion on the dev list in the coming months. How has the project developed since the last report? We continue to improve (the Fey engine) we have added tests for the core engine and documentation for the engine and the component set. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? At the start of the project. Signed-off-by: [ ](iota) Daniel Gruno [ ](iota) Sterling Hughes [X](iota) Justin Mclean [ ](iota) Hadrian Zbarcea Shepherd/Mentor notes: Justin Mclean: Probably time to come off the extended monthly reporting? -------------------- Joshua Joshua is a statistical machine translation toolkit Joshua has been incubating since 2016-02-13. Three most important issues to address in the move towards graduation: 1. Ensure first release of Joshua Incubating artifacts (6.1) 2. Continue to build the Joshua PPMC and user community 3. Investigate targeted user communities within Apache Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? We have gained a new contributor, and have continued developing and updating the web page to increase interest. We have not made any real advertising or publicity pushes, but hope to around the time of our first formal release under the Apache banner (targeted for September). How has the project developed since the last report? We have been steadily pushing up stability and design improvements, including a move from an ant+ivy to a maven build system. We have made some changes to our build process, including enabling Travis-CI for continual integration testing. We are in discussion about deeper architectural changes that will facilitate an API. Date of last release: N/A When were the last committers or PMC members elected? Kellen Sunderland and Felix Hieber (April 11, 2016) Thamme Gowda (May 26, 2016) Signed-off-by: [ ](joshua) Paul Ramirez [ ](joshua) Lewis John McGibbney [X](joshua) Chris Mattmann [ ](joshua) Tom Barber [X](joshua) Henri Yandell -------------------- Juneau Apache Juneau is a toolkit for marshalling POJOs to a wide variety of content types using a common framework, and for creating sophisticated self- documenting REST interfaces and microservices using VERY little code. Juneau has been incubating since 2016-06-24. Three most important issues to address in the move towards graduation: 1. Build up community with non-IBM and non-Salesforce contributors. 2. Finish creating website. 3. Finish populating Git repo. 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? Currently only two of the original proposers have gone through the process of getting commit approval. Some of the Salesforce proposers have been busy with their release schedule. Others need to be bugged to finish up the paperwork. How has the project developed since the last report? Grant from IBM Corporation for Juno (Apache Juneau) has been received by the ASF. The Juno codebase has been uploaded to the Git repository. We're still in the process of cleaning it up and converting to using Maven for builds. Work has been done on the website, although build issues appear to be preventing it from being fully deployed. Date of last release: N/A When were the last committers or PMC members elected? Signed-off-by: [x](juneau) Craig Russell [ ](juneau) Jochen Wiedmann [X](juneau) John D. Ament -------------------- OpenAz Tools and libraries for developing Attribute-based Access Control (ABAC) Systems in a variety of languages. OpenAz has been incubating since 2015-01-20. Shepherd/Mentor notes: johndament: The community is currently voting to retire. -------------------- Pirk Pirk is a framework for scalable Private Information Retrieval (PIR). Pirk has been incubating since 2016-06-17. The initial code for Pirk was granted on 2016-07-11. Three most important issues to address in the move towards graduation: 1. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process. 2. Establish a process which allows different release cycles for the core framework, extensions/adaptors, and additional algorithms. 3. Grow the community to establish diversity of background and expertise. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? The mailing list activity, pull requests, and page views to the Apache Pirk website (via Google Analytics) have greatly increased since the last report. How has the project developed since the last report? The project has ensured that all dependencies are compliant with the Apache License version 2.0 and that all code and documentation artifacts have the correct Apache licensing markings and notice. The project has also undertaken a refactor of some of the initial packages and provided more robust support for user interaction. Date of last release: No releases have been made yet. When were the last committers or PMC members elected? Pirk is operating with its initial committers and PMC and has not yet elected new committers or PMC members. Signed-off-by: [X](pirk) Billie Rinaldi [X](pirk) Joe Witt [X](pirk) Josh Elser [X](pirk) Suneel Marthi [X](pirk) Tim Ellison -------------------- 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 base 2. Ensure that releases and processes adhere to ASF standards 3. Spread the word, get more developers onboard. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? The community is growing, albeit at a very slow pace, possibly due to summer vacations (and some newborns). We intend to ramp up our recruitment drive in the coming months. How has the project developed since the last report? We have managed to vote on and release Pony Mail 0.9. Trademark issues have been discussed, mostly done but perhaps with a few lose ends to tie up. Date of last release: 2016-08-02 When were the last committers or PMC members elected? 2016-05-27 Signed-off-by: [ ](ponymail) Andrew Bayer [X](ponymail) John D. Ament -------------------- PredictionIO PredictionIO is an open source Machine Learning Server built on top of state- of-the-art open source stack, that enables developers to manage and deploy production-ready predictive services for various kinds of machine learning tasks. PredictionIO has been incubating since 2016-05-26. Three most important issues to address in the move towards graduation: 1. Establish a formal release schedule and process, allowing for dependable release cycles consistent with the Apache way. 2. Grow the community to establish diversity 3. Transition of present PredictionIO users from google-groups to ASF mailing lists. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The mailing list activity, pull requests and page views to the PredictionIO website (per google analytics) have greatly increased since the last report. We have announced our new mailing lists on ASF infra on the old Google Groups and have made those groups read only. Since then, we have seen previous joining the new ASF-based community, and some new contributors actively making proposals and patches. How has the project developed since the last report? The project has ensured that all dependencies are Apache License 2.0 compliant, and all code. Working to ensure that all code and documentation markings have the correct apache license 2.0 attributions. We have seen contributors who used to submit patches pre-donation are now actively submitting patches to the migrated codebase. There are also new contributors who have submitted proposals about migrating the template gallery to be based on ASF, which we have happily merged. New integration tests have also been proposed and being actively developed by new contributors. Date of last release: No releases yet. When were the last committers or PMC members elected? PredictionIO is still operating with the initial committers and PMC and has not yet elected new committers or PMC members. Signed-off-by: [X](predictionio) Andrew Purtell [ ](predictionio) James Taylor [ ](predictionio) Lars Hofhansl [x](predictionio) Luciano Resende [ ](predictionio) Xiangrui Meng [X](predictionio) Suneel Marthi -------------------- Quickstep Quickstep is a high-performance database engine. Quickstep has been incubating since 2016-03-29. Three most important issues to address in the move towards graduation: 1. Acquire early adopters. 2. Continue to build the developer community. 3. Create an ASF release. 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? 1. Added two new members to the (core) Committers group. 2. Added one new member to the Contributor group. 3. Started discussions for a community and governance structure. Initial proposal has been circulated the project developer list. How has the project developed since the last report? 1. We have closed over 40 pull requests. 2. Created a website. 3. Created a getting started guide. 4. Started work on cleaning up the entire repository to have licensing and copyrights in line with ASF projects. 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 [ ](quickstep) Roman Shaposhnik -------------------- S2Graph S2Graph is a distributed and scalable OLTP graph database built on Apache HBase to support fast traversal of extremely large graphs. S2Graph has been incubating since 2015-11-29. Three most important issues to address in the move towards graduation: 1. Make a release 2. Attract users and contributors 3. Foster more and diverse committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? * Held a session on S2Graph: Internal at Apache Big Data NA * Made various networking efforts at Apache Big Data NA, Vancouver and Druid Meet-up, Seoul * Made plans to integrate with Apache TinkerPop in order to reach a wider audience (S2GRAPH-72) * Discussion with Apache Zepplin regarding joint meet-ups at Seoul * 3 inquiries from user mailing list * Submit paper to INFOCOM 2017 How has the project developed since the last report? * We decided project logo. * Project website is up. * Working on issues on providing package for distribution. * 20 issues are created, 18 issues are resolved. * Working on first release(S2GRAPH-86) Date of last release: No yet When were the last committers or PMC members elected? No Signed-off-by: [X](s2graph) Andrew Purtell [ ](s2graph) Venkatesh Seetharam [X](s2graph) Sergio Fernández -------------------- SensSoft SensSoft is a software tool usability testing platform SensSoft has been incubating since 2016-07-13. Three most important issues to address in the move towards graduation: 1. Ensure that Software grant/CCLA are submitted to secretary@ 2. Port all infrastructure and community over to the ASF Incubator infrastructure. 3. Grow the Senssoft community and work towards incubating releases. 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? Senssoft has only literally arrived in the Incubator. Podling bootstrapping is currently underway. CCLA was received by secretary@ and all CLAs have been submitted and received as well. We are ready to begin incubating. How has the project developed since the last report? Project repos have been established at the ASF and the community are undertaking QA in order to have them writable. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [ ](senssoft) Paul Ramirez [X](senssoft) Lewis John McGibbney [X](senssoft) Chris Mattmann -------------------- Sirona Monitoring Solution. Sirona has been incubating since 2013-10-15. Three most important issues to address in the move towards graduation: 1. Extend the community 2. Release a bit more often 3. - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? User community increased a bit but not much the core project community. How has the project developed since the last report? We tried to release but have few fixes to do. Date of last release: 2015-11-03 When were the last committers or PMC members elected? Signed-off-by: [ ](sirona) Olivier Lamy [ ](sirona) Henri Gomez [ ](sirona) Jean-Baptiste Onofre [ ](sirona) Tammo van Lessen [X](sirona) Mark Struberg -------------------- Slider Slider is a collection of tools and technologies to package, deploy, and manage long running applications on Apache Hadoop YARN clusters. Slider has been incubating since 2014-04-29. Three most important issues to address in the move towards graduation: 1. Apache Slider community/PPMC has voted to move portions of Slider into Apache Hadoop YARN as modules. It is possible that the remaining pieces will be moved at a later point in time or become obsolete or evolve to work closely with YARN. Slider PPMC will decide what makes the most sense as we progress through this exciting time. 2. Getting more external users 3. Growth of a diverse set of developers/committers/PMC members is also crucial towards the final state of Slider Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? The Apache Hadoop YARN community/PMC and Apache Slider community/PPMC has decided to move portions of Slider into YARN, to make fast and significant progress on: YARN-4692 - [Umbrella] Simplified and first-class support for services in YARN. As a result, portions like Slider Core, Application Master, Client and Tests will roll into Apache Hadoop YARN as module(s). This effort is being captured in: YARN-5079 : Native YARN framework layer for services. At this point, a branch has been created in the Hadoop codebase, and Slider has been selectively migrated. As a result of this, we are already seeing interest in the Hadoop committers/PMC, who have started to contribute and submit patches to Slider. In order to support existing users of Slider, and to provide seamless migration, there will be sufficient overlap between the time when a stable state of long running services support is available in some future version of YARN and the time till an independent Slider release is available. The community/PPMC will also determine the future state of Slider as we navigate through these changes. The discussions on the Slider and YARN community DLs can be viewed here - https://s.apache.org/0hoh https://s.apache.org/MncV How has the project developed since the last report? We released version 0.91.0-incubating in June, 2016 with significant work done on token management, unique component support, SLIDER-906 (Support for Docker based application packaging with first class YARN support) and several bug fixes. Work continues on support for complex services (assemblies) and agent-less applications in Slider. The efforts on the Core will continue in the new services branch created in YARN. Date of last release: 2016-06-28 slider-0.91.0-incubating When were the last committers or PMC members elected? 2015-07-07: Yu (Thomas) Liu Signed-off-by: [ ](slider) Arun C Murthy [X](slider) Devaraj Das [ ](slider) Jean-Baptiste Onofré [ ](slider) Mahadev Konar -------------------- SystemML SystemML provides declarative large-scale machine learning (ML) that aims at flexible specification of ML algorithms and automatic generation of hybrid runtime plans ranging from single node, in-memory computations, to distributed computations running on Apache Hadoop MapReduce and Apache Spark. SystemML has been incubating since 2015-11-02. Three most important issues to address in the move towards graduation: - Grow SystemML community: increase mailing list activity, increase adoption of SystemML for scalable machine learning, encourage data scientists to adopt DML and PyDML algorithm scripts, respond to user feedback to ensure SystemML meets the requirements of real-world situations, write papers, and present talks about SystemML. - Continue to produce releases. - Increase the diversity of our project's contributors and committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? NONE. How has the community developed since the last report? Our mailing list from May through July had 237 messages including a wide range of topics. We have gained 6 new contributors since May 1st. On GitHub, the project has been starred 365 times and forked 129 times. Fred Reiss spoke at Spark Summit West on June 7 about building custom machine learning algorithms with SystemML. Mike Dusenberry presented about SystemML on May 19 at Datapalooza Denver. Elgohary, Boehm, Haas, Reiss, and Reinwald published Compressed Linear Algebra for Large-Scale Machine Learning. How has the project developed since the last report? We produced our second Apache release, version 0.10.0-incubating. The project has had 205 commits since May 1. 187 issues have been reported on our JIRA site and 127 issues have been resolved. 70 pull requests have been created since May 1, and 63 of these have been closed. Date of last release: 2016-06-15 (version 0.10.0-incubating) When were the last committers or PMC members elected? 2016-05-07 Glenn Weidner 2016-05-07 Faraz Makari Manshadi Signed-off-by: [x](systemml) Luciano Resende [ ](systemml) Patrick Wendell [ ](systemml) Reynold Xin [ ](systemml) Rich Bowen -------------------- Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important issues to address in the move towards graduation: 1. Allow community to build consensus in APIs. 2. Get new contributors. 3. Understand and work through end user use-cases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The community recently had a bit of a falling out between this project and some changes proposed to go into the Geronimo project. Its generally believed that what was being proposed was not malicious. It does however represent some of the core issues around this project's ability create consensus and grow. The project has already been incubating for two years, with very few releases and very little contributor growth. How has the community developed since the last report? - See issues section. How has the project developed since the last report? - Releases are still in progress, and work is being done to refactor the Tamaya APIs based on some input from Mark Struberg and others. Date of last release: 2016-04-06 (0.2-incubating) When were the last committers or PMC members elected? Philipp Ottlinger has been elected on 2016-04-22 as new committer. Signed-off-by: [X](tamaya) John D. Ament [X](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: johndament: Discussions are beginning to talk through the future of the podling. Going to request an extra report next month since this was created by mentors. -------------------- 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: 0.1.x branch should be ready for release. Master has moved to start support for Spark 2.0 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. Community member 2mariusvniekerk key in porting Toree to work on Spark 2.0. Sitting on PR 56. 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. 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 -------------------- Traffic Control Traffic Control allows you to build a large scale content delivery network using open source. Traffic Control has been incubating since 2016-07-12. Three most important issues to address in the move towards graduation: 1. Get set up with all resources (git / mailing lists / JIRA / irc / etc) 2. Name search / name sign off 3. Prepare for next release under apache process Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? This is the first report, we are just getting started. How has the project developed since the last report? This is the first report, we are just getting started. ICLAs are done. Date of last release: We released 1.6.0 on 2016-07-29 under the old process, because the release process (candidates and votes) had already started before our official entry in the incubator. Our next release will be the first release where we will follow the Apache incubator process. When were the last committers or PMC members elected? 2016-07-12 - initial committer list. Signed-off-by: [x](trafficcontrol) Phil Sorber [x](trafficcontrol) Eric Covener [ ](trafficcontrol) Daniel Gruno [ ](trafficcontrol) J. Aaron Farr -------------------- Unomi Unomi is a reference implementation of the OASIS Context Server specification currently being worked on by the OASIS Context Server Technical Committee. It provides a high-performance user profile and event tracking server. Unomi has been incubating since 2015-10-05. Three most important issues to address in the move towards graduation: 1. Continued releases, and updated dependencies 2. Grow up user and contributor communities, seeing more contribution/PR Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The activity of the dev mailing list smoothly increased, discussing key enhancements in the project. We are now targeting the development of the user community. For that, we discussed about improving and polishing the website. Today, it's obvious that it's not easy to understand what Unomi can do and actually does. The purpose is to give more use cases and introduction on the mailing list. How has the project developed since the last report? The first Apache Unomi 1.0.0-incubating has been released. We updated key dependencies and implemented couple of new releases in addition of the bug fixes. The purpose is to cut off a new release asap. Date of last release: 2016-03-09 When were the last committers or PMC members elected? N/A Signed-off-by: [X](unomi) Jean-Baptiste Onofré [X](unomi) Bertrand Delacretaz [X](unomi) Chris Mattmann ----------------------------------------- Attachment AH: Report from the Apache jUDDI Project [Alex O'Ree] August 2016 Report for the jUDDI project jUDDI (pronounced "Judy") is an open source Java implementation of the Universal Description, Discovery, and Integration (UDDI v3) specification for (Web) Services. The jUDDI project includes Scout. Scout is an implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR). jUDDI - Very Low traffic on the mailing lists this quarter. - 3.3.2 Released November 10, 2015 Scout - No release this period, no development took place. - Very low volume of JAXR related questions on the mailing list. Last PMC addition and new committer April 3, 2013 (Alex O'Ree) Last Release jUDDI-3.3.2, November 10, 2015 There are no issues that require the boards attention at this time. ----------------------------------------- Attachment AI: Report from the Apache Kafka Project [Jun Rao] Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released 0.10.0.0 which includes new features such as Kafka stream, rack-awareness support, and native support of timestamp in the message. We also did a bug fix release 0.10.0.1 which fixed 53 issues in 0.10.0.0. We are actively working on new features such as admin apis, queryable state in Kafka stream, replication throttling, etc. Community =========== Lots of activities in the mailing list. We have 2187 subscribers in the user mailing list, up 129 in the last 3 months. We have 2043 emails in the user mailing list in the last 3 months, up from 1839 in the previous cycle. We have 852 subscribers in the dev mailing list, up 72 in the last 3 months. We have 5631 emails in the dev mailing list in the last 3 months, down from 6291 in the previous cycle, mostly because 0.10.0.0 has been released. We last elected a new committer Ismael Juma on Apr. 26, 2016. We are voting on a new PMC member right now. We had several Kafka meetups in various cities in this quarter. Releases =========== 0.10.0.0 and 0.10.0.1 were released on May. 24 and Aug. 10, 2016, respectively. ----------------------------------------- Attachment AJ: Report from the Apache Knox Project [Kevin Minder] # Description The Apache Knox Gateway is a REST API Gateway for interacting with Apache Hadoop clusters. The Knox Gateway provides a single access point for all REST/HTTP interactions with Apache Hadoop clusters. # Issues None # Status Actively working on maintaining a release cadence to deliver bug fixes as well as new features in as timely a manner as possible. Most recent release missed our target of middle June due to community testing efforts and filed JIRAs which was great to see. Three new contributors provided patches, testing and JIRAs. We have a number of new JIRAs already targeted for the 0.10.0 release around LDAP improvements which will likely be a central theme to that release. The community has voted to change PMC chair as has been communicated separately via email of the resolution. # Releases * 0.9.1: 2016-08-04 Fixed numerous issues related to proxying of UIs, SAML, replay buffer size, etc - through ~25 commits. # Development Activity * Community is discussing the creation of 0.10.0 as a possible candidate for 1.0.0 release * Jira: 729 total, +11 -6 (last 30 days) * Git (Source): 16 commits over last 30 days * SVN (Site & Docs): 3 commits over last 30 days # Community Activity ## Membership Changes * Board notified of request to change PMC chair from Kevin Minder (kminder) to Larry McCay (lmccay). [2] * Zac Blanco was added as a committer on 8/24/2015 [1]. * We continue to have smaller contributions from the community but are still on the lookout for new committers to emerge. ## Mailing List Activity * user@knox: 10 messages over last 30 days * dev@knox: 170 messages over last 30 days 1. http://mail-archives.apache.org/mod_mbox/knox-dev/201508.mbox/%3CD9C32FB4-CDD5-4DCD-A3D7-3BEEE97734AC%40hortonworks.com%3E 2. http://mail-archives.apache.org/mod_mbox/knox-dev/201608.mbox/%3CCAJWAuamVSN_e%3DQJFDmQaCkdeCuk2TSawXM9Tnj9nD4EViDtr5g%40mail.gmail.com%3E ----------------------------------------- Attachment AK: Report from the Apache Kudu Project [Todd Lipcon] ## Description: Apache Kudu is a distributed columnar storage engine built for the Apache Hadoop ecosystem. ## Activity: * Graduated from the Incubator in July, 7.20.2016. * Press and blog post went out announcing Apache Kudu as TLP * Discussing started regarding our first release out of incubation targeting 0.10.0 release candidate sometime in August ## Issues No major issues at this time ## Community Latest Additions: * PMC addition: Established as a TLP 7.20.2016 * Contributor addition: Binglin Chang, 4.4.2016 ### Issue backlog status since last report: * Created: 115 * Resolved: 76 ### Mailing list activity since last report: * @dev 1369 messages * @user 237 messages ## Releases Last release: 0.9.1-incubating, Release Date: 6.30.2016 ----------------------------------------- Attachment AL: Report from the Apache Kylin Project [Luke Han] ## Description: =============== Apache Kylin is an open source Distributed Analytics Engine designed to provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop supporting extremely large datasets. ## Issues: ========== - there are no issues requiring board attention at this time ## Activity: ============ - Mailing list, JIRA, and commit activity are at or above average - Yang Li presented Kylin streaming function topic at Strata+Hadoop World Beijing on 2016-08-06 - Shaofeng Shi presented Kylin general topic at Strata+Hadoop World Beijing on 2016-08-06 ## Community: ============= - no committer has been appointed after last report. - Messages on the dev mailing list after last report: 1147 - Messages on the user mailing list after last report: 489 - 304 JIRA tickets created after last report - 273 JIRA tickets closed/resolved after last report ## Releases: ============ - The latest release, v1.5.3, released on 2016-07-28 ----------------------------------------- Attachment AM: Report from the Apache Lens Project [Amareshwari Sriramadasu] ## Description: Lens provides a Unified Analytics interface. Lens aims to cut the Data Analytics silos by providing a single view of data across multiple tiered data stores and optimal execution environment for the analytical query. It seamlessly integrates Hadoop with traditional data warehouses to appear like one. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Hive dependency moved to apache release dependency. Lots of work is done in Apache Hive as well to fix bugs and add improvements. - Many more regression tests added in Lens regression module. - Saved query service has been stabilized. - Scheduling capability added. The feature is experimental right now. - Python client has been added as one more client for Lens. - node.js based UI has been improved and made the default UI for Lens - Added limit for active sessions per user. - Added capability to stream results directly when queries finish faster and output is smaller. - Server now has a launcher pool to launch queries in parallel. - Outer join queries are optimized to pull filters as subqueries. - Branching done for Release 2.6 and verification is in progress. ## PMC changes: - Currently 17 PMC members. - Deepak Barr was added to the PMC on Mon May 23 2016 ## Committer base changes: - Currently 22 committers. - Archana H was added as a committer on Sat May 21 2016 ## Releases: - Last release was Lens-2.5.0-beta on Mon Mar 28 2016 ----------------------------------------- Attachment AN: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description: Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. ## Issues: There are no issues which require board attention at this time. ## Activity: We had a good amount of activity and user contributions in the past couple of months. ## PMC changes: - Currently 13 PMC members. - Jeff Dunham was added to the PMC on Sat May 21 2016 ## Committer base changes: - Currently 19 committers. - Jeff Dunham was added as a committer on Sat May 21 2016 ## Releases: - 1.0.0 was released on Mon Jun 20 2016 - 1.1.0 was released on Thu Jul 07 2016 ## Community - Jeff Dunham has join us as a committer and a PMC member in May. - v1.0 release had received a decent reception and coverage around the internet. Special thanks to Anthony and Sally for working on the PR. ----------------------------------------- Attachment AO: Report from the Apache Logging Services Project [Ralph Goers] The Apache Logging Services Project creates and maintains open- source software related to application logging. Currently there are no issues which require the board's attention. - Community Log4j 2 remains an active project. The overall community is healthy and friendly. Log4cxx is still active in the Incubator. They have been sporadic discussions regarding performing a release but little real progress has been made. In general, all subprojects are still healthy although none has grown since the last report. - Project Branding Requirements All components except Chainsaw meet the branding requirements. We will fix the Chainsaw branding with the next release. - Last three community changes * Mikael Ståldal joined as a PMC Member on June 20 2016 * Ralph Goers was voted to be the next Chair on Nov 01 2015 * Mikael Ståldal joined as a Committer on Sep 17 2015 - Releases * Log4j 2.6.2 (Jul 5, 2016) * Log4j 2.6.1 (Jun 8, 2016) * Log4j 2.6 (May 28, 2016) - Subproject summaries Log4j 2: Active. Significant work has been done to reduce or eliminate the number of objects Log4j creates and in documenting how to use Log4j in a "garbage free" manner. Quite a few bug fixes in the last 2 releases. The number of emails on the developer mailing list has increased again in the last 3 months. Log4net: Active with 2 recent releases. Log4cxx: Active in the Incubator. Discussions on how to perform a release are still in progress. Log4php: Almost no activity this quarter. Chainsaw: No activity this quarter. ----------------------------------------- Attachment AP: Report from the Apache ManifoldCF Project [Karl Wright] Project description ============== ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr, OpenSearchServer or ElasticSearch. ManifoldCF also defines a security model for target repositories that permits them to enforce source repository security policies. Releases ======== ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then, there have been numerous major releases, including a 2.4 release on April 23, 2016. The next major release is scheduled for August 30, 2016. Committers and PMC membership ============================= The last committer we signed up was Tugba Dogan on September 7, 2015. The last PMC member was Rafa Haro, voted in on August 31, 2015. Mailing list activity ===================== Mailing list activity has been moderate this quarter. Issues reported have been mainly garden-variety bugs. We've had several feature requests but few contributions. Dev list comments for this period have also been light, with occasional user questions. I am unaware of any mailing list question that has gone unanswered. Outstanding issues ================== No outstanding infrastructure issues are known at this time. Branding ======== We continue to believe we are now compliant with Apache branding guidelines, with the possible exception of (TM) signs in logos from other Apache products that don't have any such marks. We received word that the ManifoldCF trademark application (US TM App No. 86583085 for "MANIFOLDCF" in Cl. 9 | DLA Ref: 393457-900118) has been accepted. ----------------------------------------- Attachment AQ: Report from the Apache Marmotta Project [Jakob Frank] # Marmotta Board Report for August 2016 ## Description: Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013. ## Issues: There are no issues requiring board attention at this time. ## Activity: As the previous, this has not been a very active period either. Most of the issues we targeted for 3.4.0 still remain open. So we are discussing how to move forward with the release in the next few weeks (https://s.apache.org/pzef). The reduction of frequent contributions from many of the core members is affecting the project development and support. Therefore we have started to look for solutions to grow the community and help in the future development. Mark A. Matienzo has been recently added as Committer and PMC member (https://s.apache.org/ztE6). W3C has kicked-off a relevant Community Group for evolving LDP (https://www.w3.org/community/ldpnext/). The new recent member (Mark) could represent the project, although goals has not yet been discussed. ## Health report: The project was considered feature-complete in 3.3.0. The current release cicle (3.4.0) focused on refining and fixing bug, plus incorporation some non-core new features. The development (issues, commits, emails) has significantly come down in the last months. ## PMC changes: - Currently 11 PMC members. - Mark A. Matienzo was added as a PMC member on Wed Aug 03 2016. ## Committer base changes: - Currently 13 committers. - Mark A. Matienzo was added as a committer on Wed Aug 03 2016. ## Releases: - Last release was 3.3.0 on Fri Dec 05 2014 ## Mailing list activity: - users@marmotta.apache.org: - 112 subscribers (up 0 in the last 3 months): - 18 emails sent to list (79 in previous quarter) - dev@marmotta.apache.org: - 93 subscribers (up 0 in the last 3 months): - 507 emails sent to list (241 in previous quarter) ## JIRA activity: - 12 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AR: Report from the Apache MetaModel Project [Kasper Sørensen] ## Description: Providing a common interface for discovery, exploration of metadata and querying of different types of data sources. ## Issues: - there are no issues requiring board attention at this time ## Activity: - A new (confluence) wiki is being set up to replace the current MoinMoin wiki. - A new SPI-based API have been added to MetaModel, making it possible to dynamically add new modules. We believe this approach makes integration with other projects such as Apache Calcite (and thereby also e.g. Apache Drill) much easier (see CALCITE-1304). ## Health report: - The 4.x releases occur at a steady pace, growing maturity. - The community does not seem to grow very much, but supporters are loyal. It is my impression that we lag behind on “marketing” activities to make the project more known. - The future 5.x release is ambitious in trying to broaden MetaModel’s scope by adding a RESTful HTTP API on top of the existing Java API. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ankit Kumar on Tue Nov 18 2014 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Dennis Du Krøger at Thu Oct 15 2015 ## Releases: - 4.5.3 was released on Thu May 19 2016 - 4.5.4 was released on Fri Aug 04 2016 ## Mailing list activity: - We have added new mailing lists @issues and @user, but these have not yet been taken into good use. - dev@metamodel.apache.org: - 77 subscribers (up 3 in the last 3 months): - 1368 emails sent to list, a lot of which was SPAM from the JIRA SPAM incidents (226 in previous quarter) - issues@metamodel.apache.org: - 5 subscribers (up 5 in the last 3 months) - user@metamodel.apache.org: - 10 subscribers (up 10 in the last 3 months) ## JIRA activity: - 27 JIRA tickets created in the last 3 months - 16 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AS: Report from the Apache MINA Project [Jean-François Maury] Apache MINA is a network application framework which helps users develop high performance and high scalability network applications easily. ## Activity: No new release this quarter. ## Health report: Project activitity has declined expect for the SSHD project, in all the various categories (commits, JIRA tickets, mails). ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jeff Genender on Tue Apr 05 2016 ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months - Last committer addition was Lyor Goldstein at Thu Apr 30 2015 ## Releases: - Last release was Apache MINA 2.0.13 on Tue Feb 16 2016 ## Mailing list activity: - users@mina.apache.org: - 507 subscribers (up 5 in the last 3 months): - 56 emails sent to list (80 in previous quarter) - dev@mina.apache.org: - 361 subscribers (up 1 in the last 3 months): - 240 emails sent to list (561 in previous quarter) - ftpserver-users@mina.apache.org: - 133 subscribers (down -3 in the last 3 months): - 0 emails sent to list (2 in previous quarter) ## JIRA activity: - 30 JIRA tickets created in the last 3 months - 21 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache Oltu Project [Antonio Sanso] Oltu is a project to develop a Java library which provides an API specification for, and an unconditionally compliant implementation of the OAuth v2.0 specifications. OAuth is a mechanism that allows users to authenticate and authorise access by another party to resources they control while avoiding the need to share their username and password credentials. MILESTONES Apache Oltu 1.0 was released on March 3rd 2014. Apache Oltu Oauth2 module version 1.0.2 was released June 20th 2016. Apache Oltu Parent v4 was released June 20th 2016. CURRENT ACTIVITY The core part of the project related to 'The OAuth 2.0 Authorization Framework' (RFC 6749) is pretty stable due the fact RFC 6749 is now a standard. A stable version 1.0 was released on March 3rd 2014 and some minor releases are going out regularly for bug fixing. Updated modules contained bug fixing were released June 20th 2016 . At the moment we are working on JSON Web Encryption support ( OLTU-80 - Implement JWE support for JWT In Progress ). Users activity is growing slowly but steadily (the user@ mailing list has got new messages from new users). Lately we have been fixing a bunch of users reported issues hence the new release. COMMUNITY We have voted two new PMC members: Stein Welberg and Jasha Joachimsthal in June 2016 (13/06/2016) ISSUES There are no issues requiring board attention at this time. ----------------------------------------- Attachment AU: Report from the Apache Oozie Project [Robert Kanter] ## Description: - Oozie is a workflow scheduler system to manage Apache Hadoop jobs. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Development activity continues as can be seen from the following JIRA report: https://s.apache.org/oozie_report_aug_16 - We've recently started work on a big project to change the execution framework from Hadoop MapReduce to Hadoop Yarn (OOZIE-1770). - We're currently working on scoping out and reviewing JIRAs for a 4.3.0 release. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ryota Egashira on Mon Aug 10 2015 ## Committer base changes: - Currently 18 committers. - No new committers added in the last 3 months - Last committer addition was Jaydeep Vishwakarma at Mon Apr 11 2016 ## Releases: - Last release was 4.2.0 on Wed Jun 03 2015 ## Mailing list activity: - dev@oozie.apache.org: - 149 subscribers (up 3 in the last 3 months): - 2205 emails sent to list (1001 in previous quarter) - user@oozie.apache.org: - 494 subscribers (down -6 in the last 3 months): - 139 emails sent to list (143 in previous quarter) ## JIRA activity: - 102 JIRA tickets created in the last 3 months - 77 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AV: Report from the Apache Open Climate Workbench Project [Michael James Joyce] Apache Open Climate Workbench is a tool for scalable comparisons of remote sensing observations to climate model outputs. Development on the project has been great since the last report. July and especially early August have seen very high contributions from a number of our regular contributors. We haven't seen an increase in new contributors, but Google Summer of Code brought a good amount of activity to the project with both Omkar and Ibrahim making great contributions to the project. The project released v 1.1.0 late in July which provides a number of key features required of the tool in addition to many quality-of-life improvements. The team is working hard towards 1.2 and a number of new features. Issues for the Board: None When was the last committer or PMC member elected: - Omkar Reddy - 20 January 2016 - Ibrahim Jarif - 26 April 2016 When was the last release: - 1.0.0 - 22 September 2015 - 1.1.0 - 27 July 2016 ----------------------------------------- Attachment AW: Report from the Apache Perl Project [Philippe M. Chiasson] -- mod_perl 1.0 -- The mod_perl 1.x is a maintenance track designed to work with httpd 1.3.x. No new mod_perl 1.x releases since 2014-12. --- mod_perl 2.0 -- mod_perl 2.X is designed to work with all httpd 2.X branches. mod_perl 2.0.9 was released 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 released on Apr 21, 2015 No new Apache-Test releases since 2015-11. --- 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 No new Apache-SizeLimit releases since 2015-11. --- 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 No new Apache-Bootstrap releases since 2015-11. --- 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 No new Apache-Reloase releases since 2015-11. -- 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 No new Apache-DBI releases since 2015-11. -- 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. The 2.0.9 release has caused some more healthy activity, and development is continuing. -- Users -- The mod_perl users list is seeing little activity, with a bump in activity following the 2.0.9 RCs and the final release. 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 AX: Report from the Apache Phoenix Project [James R. Taylor] ## Description: - Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop ## Issues: - There are no issues requiring board attention at this time ## Activity: - The first inaugural PhoenixCon, a dual track Meetup, was hosted by Salesforce.com on Wed May 25th with attendance of ~100 people. - Three Phoenix talks were given at Hadoop Summit on June 28-30. - One Phoenix talk was given at HBaseCon on Tue May 24. - Support for Phoenix 4.7 was added to Amazon EMR on Thu June 2. - Cloudera Labs version of Phoenix was updated to 4.7 on Mon June 27. ## Health report: - The project is healthy and continues to grow as users look for easy ways to gain insight over and manage their ever-increasing Hadoop data through standard SQL and JDBC APIs. ## PMC changes: - Currently 24 PMC members. - Josh Elser was added to the PMC on Wed August 10 2016 ## Committer base changes: - Currently 28 committers. - Sergey Soldatov was added as a committer on Wed May 18 2016 ## Releases: - Phoenix 4.8.0 was released on Wed August 10 2016 ## Mailing list activity: - Both dev and user lists continue to gain subscribers - dev@phoenix.apache.org: - 211 subscribers (up 11 in the last 3 months): - 3807 emails sent to list (3124 in previous quarter) - user@phoenix.apache.org: - 509 subscribers (up 32 in the last 3 months): - 398 emails sent to list (729 in previous quarter) ## JIRA activity: - 275 JIRA tickets created in the last 3 months - 190 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AY: Report from the Apache POI Project [Dominik Stadler] Report from the Apache POI committee [Dominik Stadler] ## Description: - Apache POI is a Java library for reading and writing Microsoft Office file formats ## Issues: - there are no issues requiring board attention at this time ## Activity: - There was a constant stream of work from a number of committers, work went into bugfixes, streamlining the API in respect to enums instead of ints and supporting more cryptography options of the file formats. Discussion around replacing XMLBeans is continuing, some legal issues related to possible replacements are discussed at LEGAL-264. On further release automation there was discussion of setting up a machine to automatically publish generated documentation. There was one security related topic in a code-sample (not the core libraries), which was published as CVE-2016-5000 "XXE in XLS2CSV", see http://www.openwall.com/lists/oss-security/2016/07/22/2 Some work was done to prepare for JDK 9, although there are still bugs in the JDK itself that prevent a successful CI run. We released version 3.15-beta2 and are in the final stages for 3.15-beta3, which should be mostly what we release as 3.15 final shortly. Some preparation is underway for celebrating 15 years of POI. ## Health report: - activity looks good, all seems healthy, there is a constant stream of user-questions and development related discussions. ## PMC changes: - Currently 27 PMC members. - Mark Murphy was added to the PMC on Sat Jul 09 2016 ## Committer base changes: - Currently 34 committers. - Mark Murphy was added as a committer on Sat Jul 09 2016 ## Releases: - 3.15-beta2 was released on Sat Jul 02 2016 ## Mailing list activity: - Mainly constant membership numbers. POI is a mature project with a stable user/developer-base. - dev@poi.apache.org: - 248 subscribers (down -7 in the last 3 months): - 1267 emails sent to list (979 in previous quarter) - general@poi.apache.org: - 133 subscribers (up 1 in the last 3 months): - 2 emails sent to list (3 in previous quarter) - user@poi.apache.org: - 666 subscribers (down -1 in the last 3 months): - 124 emails sent to list (123 in previous quarter) ## Bugzilla Statistics: - 110 Bugzilla tickets created in the last 3 months - 142 Bugzilla tickets resolved in the last 3 months - 430 bugs are open overall - Having 103 enhancements, thus having 327 actual bugs - 101 of these are waiting for feedback - thus having 226 actual workable bugs - 5 of the workable bugs have patches available ----------------------------------------- Attachment AZ: Report from the Apache Qpid Project [Robbie Gemmell] Apache Qpid is a project focused on creating software based on the Advanced Message Queuing Protocol (AMQP), currently providing a protocol engine library, message brokers written in C++ and Java, a message router, and client libraries for C++, Java / JMS, .Net, Python, Perl and Ruby. # Releases: - Qpid Java 6.0.3 was released on 25th May 2016 [1]. - Qpid Dispatch 0.6.0 was released on 13th June 2016. - Qpid Proton 0.13.0 was released on 15th June 2016. - Qpid JMS 0.10.0 was released on 1st July 2016 [2]. - Qpid Java 6.0.4 was released on 1st July 2016 [2]. - Qpid Proton 0.13.1 was released on 11th July 2016 [3]. [1] Addressed CVE-2016-3094 and CVE-2016-4432 along with other updates. [2] Addressed CVE-2016-4974 along with other updates. [3] Addressed CVE-2016-4467 along with other updates. # Community: - There have been no new committer or PMC member changes in the previous quarter. Ganesh Murthy was added as a committer on 29th February 2016, and Lorenz Quack was added to the PMC on 7th March 2016. - The main user and developer mailing lists continue to see good activity, and JIRAs are being raised and addressed, in line with previous levels. # Development: - Work continues towards the Qpid Dispatch 0.7.0 release incorporating various improvements and bug fixes. A 0.6.1 patch release has passed vote and will be announced soon. - The release process for Qpid Proton 0.14.0 is getting under way, containing various fixes and further work on the C++ reactive API bindings, aiming for a release in the next couple of weeks. - A 0.11.0 release of the AMQP 1.0 JMS client with various bug fixes and improvements is aimed for the next few weeks. Work is also getting started on updating the client to suppport JMS 2.0 for later releases. - Craig Russell raised a concern with the Qpid Java naming used on more recent independent releases of some Qpid components written in Java. After discussion looping in trademarks@ and legal-internal@, updates have been made to transition the website and future releases to reference "Apache Qpid for Java", "Qpid for Java" etc going forward. - Development on the broker and AMQP 0-x JMS client continue toward new Qpid for Java releases, with both a larger 6.1.0 release and smaller 6.0.5 patch release planned. - The components written in C++ and Python have been reorganised and their code migrated to Git repositories, with work progressing toward new releases for these. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment BA: Report from the Apache REEF Project [Markus Weimer] ## Description: Apache REEF (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. ## Issues: No issues require the board's activity at this time. ## Activity: - REEF 0.15 was released in the report period. It contains significant improvements to REEF.NET - We've seen a significant uptick in the interest in and work towards a fully functional REEF.NET on Linux - Twitter released their new streaming platform Heron in version 0.14. In this version, it can be run on Apache Hadoop YARN via a scheduler implemented in REEF. ## Health report: Overall, the community is healthy: We've seen several new people introduce themselves on the dev list, and many of them have started contributing already. Activity has been down a little bit, which seems to be due to the summer vacation schedule of our community. This also caused us to slip on the post- graduation cleanup of our PMC membership we asked about in the last report. ## PMC changes: - Currently 21 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andrew Chung on Tue Nov 17 2015 ## Committer base changes: - Currently 33 committers. - Carlo Curino was added as a committer on Tue Jun 07 2016 ## Releases: - 0.15 was released on Sun May 22 2016 ## Mailing list activity: - dev@reef.apache.org: - 69 subscribers (up 18 in the last 3 months): - 1558 emails sent to list (2150 in previous quarter) ## JIRA activity: - 135 JIRA tickets created in the last 3 months - 103 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BB: Report from the Apache River Project [Patricia Shanahan] ## Description: - Apache River software provides a standards-compliant JINI service. ## Issues: - There are no issues requiring board attention at this time. Although the troubles discussed last quarter persist, there is on-going discussion of possible future directions. ## Activity: - There has been little activity. ## Health report: - The technical and people problems discussed last quarter have not yet been solved, but neither have they killed the project. In the last two months there have been threads on dev@river.apache.org, involving a total of 6 people, discussing how to support languages other than Java and how to take River in an IoT direction. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bryan Thompson on Sun Aug 30 2015 ## Committer base changes: - Currently 15 committers. - Dan Creswell was added as a committer on Mon Jun 20 2016 ## Releases: - Last release was river-jtsk-2.2.3 on Sat Feb 20 2016 The above report received +1 votes from PMC members Simon IJskes, Peter Firmstone, Bryan Thompson, Tom Hobbs, and Patricia Shanahan ----------------------------------------- Attachment BC: Report from the Apache Roller Project [Dave Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat and MySQL, and is known to run on other Java servers and relational databases. The ASF blog site at blogs.apache.org runs on Roller 5.0.3 Tomcat and MySQL. ## Issues: - There are no issues requiring board attention at this time ## Activity: - The core Roller community is small and with low activity levels. - There is ongoing work to create a modernized UI using Bootstrap with Struts ## Health report: - Community is made-up of part-time volunteers with limited time to devote to Roller. ## PMC changes: - Currently 5 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kohei Nozaki on Sun Dec 06 2015 ## Committer base changes: - Currently 10 committers. - No new committers added in the last 3 months - Last committer addition was Kohei Nozaki at Mon Mar 09 2015 ## Releases: - Last release was 5.1.2 on Tue Mar 24 2015 ## Mailing list activity: Based on the low volume of activity and email, I'm surprised we have as many subscribers as we do. - dev@roller.apache.org: - 158 subscribers (down -2 in the last 3 months): - 2 emails sent to list (5 in previous quarter) - user@roller.apache.org: - 286 subscribers (up 0 in the last 3 months): - 1 emails sent to list (1 in previous quarter) ## JIRA activity: - 0 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BD: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: - Library implementing XML Digital Signature Specification & XML Encryption Specification ## Issues: - There are no issues requiring board attention at this time ## Activity: - There was one release of the Java library over the last quarter. It fixed some backwards compatiblity regressions, a BASE-64 encoding issue as well as another couple of minor issues. No other issues have cropped up since then, so no release is expected in the next quarter. ## Health report: - Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC. Right now there are no obvious potential new committers for the project. ## PMC changes: - Currently 6 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Marc Giger on Wed Apr 03 2013 ## Committer base changes: - Currently 16 committers. - No new changes to the committer base since last report. - Last committer addition was Marc Giger in July 2012 ## Releases: - Apache Santuario XML Security for Java 2.0.7 was released on Fri Jun 17 2016. ## JIRA activity: - 9 JIRA tickets created in the last 3 months - 9 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BE: Report from the Apache Serf Project [Bert Huijben] ## Description: The serf library is a high performance C-based HTTP client library built upon the Apache Portable Runtime (APR) library. Serf is the default client library of Apache Subversion and Apache OpenOffice. ## Issues: There are no issues requiring board attention at this time. ## Activity: The project had another three very quiet months. Some time was spent on testing the recently added features, and looking at some user reported issues around OpenSSL and Kerberos. ## Health report: Activity is at a normal, fairly quiet level. The serf project's activity is quite related to that of Subversion and with that projects recent affairs we slowed more than expected. ## PMC & Committer changes: Currently 11 PMC members and 12 committers. Our last new committer was added on Wed Sep 02 2015. ## Releases: No ASF releases yet. Last pre-ASF release 2014-10-20. We are trying to get both the 1.3.x stable branch and trunk back in a fully releasable state. 1.3.x: This branch was released pre-ASF and making it a full ASF release is a bit destabilizing for a release branch, and by that needs more review than any previous release. I hope that the delay on 1.4 (=trunk), will make us release a new 1.3.x within the next few weeks. Branko has some OpenSSL work in progress for better OS/X build support trunk (1.4.x): This branch had quite a bit of new development before switching to the ASF and then later on when we added full HTTP/2 support. This code needed some time for testing, which it now had. I think we need to review which parts need to be visible in the public api and which not. Generating proper doxygen docs from this branch would be nice, but I think we should do the comment fixups for that before branching. ## Mailing list and Jira activity: Normal activity. ----------------------------------------- Attachment BF: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: Apache Spatial Information System (SIS) is a Java library for developing geospatial applications. SIS enables better representation of spatial objects for searching, archiving, or other relevant spatial needs. The SIS metadata module forms the base of the library and enables the creation of metadata objects which comply with the model of international standards. The SIS referencing module enable the construction of geodetic data structures for geospatial referencing such as axis, projection and coordinate reference system definitions, along with the associated operations which enable the mathematical conversion of coordinates between different systems of reference. ## Issues: There are no issues requiring board attention at this time. ## Activity: Released Apache SIS 0.7 in May. This is the first release that depends on the EPSG geodetic dataset, which can be redistributed but not under terms compatible with Apache 2 license. As suggested in LEGAL-183 [1] and after discussion on the SIS mailing list [2], we deployed the EPSG geodetic dataset on Maven Central in an "org.apache.sis.non-free" groupId. This non-free artifact is not included in Apache releases and users who need its functionalities have to declare the Maven dependency themselves. Prepared an Apache SIS 0.7.1 bug-fix release in July [3], but the call for vote got no reply from someone else than the poster. Acknowledging that there is apparently no strong demand for a 0.7.1 bug-fix release, the new proposal [4] is to wait for 0.8 release. We did some progress on the Apache SIS developer guide [5], especially in the section about spatial reference systems. Helping the ncWMS project [6] to migrate their spatial referencing framework from Geotk to Apache SIS. I hope to do the same for an Open Geospatial Consortium (OGC) toolkit [7] later this year. Google Summer of Code project is continuing. We hope to start merging some parts of the work into Apache SIS this week. ## Health report: The project is reported as healthy by the report helper, but the commits are still mostly from one person. Another committer (Johann Sorel) became more active recently and his activity is expected to increase as future SIS development shifts more toward various storage formats, but he is from the same company. The Google Summer of Code student is committing in a repository clone on GitHub. ## PMC changes: * Currently 19 PMC members. * No new PMC members added in the last 3 months. * Last PMC addition was Marc Le Bihan on Wed Dec 10 2014. * Two PMC members asked to go emeritus. ## Committer base changes: * Currently 21 committers. * No new committers added in the last 3 months. * Johann Sorel was added as a committer on Thu Mar 31 2016. ## Releases: * Apache SIS 0.7 has been released in May 2016. [1] https://issues.apache.org/jira/browse/LEGAL-183 [2] https://lists.apache.org/thread.html/6b8dda7f7c59de46ff6c8571dcc211110eb2c542c8f385336b8fcd3d@1463694072@%3Cdev.sis.apache.org%3E [3] https://lists.apache.org/thread.html/ef831ab1e2483e37d6cd63d982415a02bf72ed9fec3d187a8e4497cc@%3Cdev.sis.apache.org%3E [4] https://lists.apache.org/thread.html/c9758edf4c28c0db1f4fbf5e4a24e23925ba2ceea77f65b437158688@%3Cdev.sis.apache.org%3E [5] http://sis.staging.apache.org/book/en/developer-guide.html [6] http://www.resc.rdg.ac.uk/trac/ncWMS/ [7] https://github.com/opengeospatial/geomatics-geotk ----------------------------------------- Attachment BG: Report from the Apache Spark Project [Matei Zaharia] Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python and R as well as a rich set of libraries including stream processing, machine learning, and graph analytics. Project status: - The community released Apache Spark 2.0 on July 26, 2016. This was a big release after nearly 6 months of effort that puts in a strong foundation for the 2.x line and multiple new components while remaining highly compatible with 1.x. Full release notes are available at http://spark.apache.org/releases/spark-release-2-0-0.html. Trademarks: - We posted a trademarks summary page on our website after discussions with trademarks@ to let users easily find out about the trademark policy: https://spark.apache.org/trademarks.html - We are continuing engagement with the organizations discussed earlier. Latest releases: - July 26, 2016: Spark 2.0.0 - June 25, 2016: Spark 1.6.2 - May 26, 2016: Spark 2.0.0-preview - Mar 9, 2016: Spark 1.6.1 - Jan 4, 2016: Spark 1.6.0 Committers and PMC: The last committer was added on August 6th, 2016 (Felix Cheung). The last PMC members were added Feb 15th, 2016 (Joseph Bradley, Sean Owen and Yin Huai) ----------------------------------------- Attachment BH: Report from the Apache Stratos Project [Lakmal Warusawithana] ## Description: Apache Stratos is a highly-extensible Platform-as-a-Service (PaaS) framework that helps run Apache Tomcat, PHP, and MySQL applications and can be extended to support many more environments on all major cloud infrastructures. ## Issues: - No issue for last quarter ## Activity: - No coding or discussions happened in Stratos 5.0.0 new architecture. - Did a bug fixing release 4.1.6 against the 4.x branch which is currently active. - Mainly target on existing customers. - Few mailing list user quires and answer by PMC members. ## Health report: - Very few PMC members and committers were active in bug fixing release. - Unfortunately if we can’t start Stratos 5 architecture, people may loose interest. - Two non committers voted to the bug fixing release. Thats some good sign ## PMC changes: - Currently 45 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Pubudu Gunatilaka on Fri Sep 25 2015 ## Committer base changes: - Currently 46 committers. - No new committers added in the last 3 months - Last committer addition was Pubudu Gunatilaka at Thu Sep 24 2015 ## Releases: - Apache Stratos 4.1.6 was released on Thu Aug 10 2016 ----------------------------------------- Attachment BI: Report from the Apache Subversion Project [Greg Stein] Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community continues to operate in a healthy fashion, with continued activity on the dev@ and user@ mailing lists. As a mature project, we are not attracting new developers like we did a decade ago (heh) ... but we continue to accomodate all newcomers and make it easy for them to contribute and to become part of the larger community. Last PMC addition: December 2015. Last committer addition: November 2015. * Releases Last releases were made on April 28, 2016: 1.9.4 and 1.8.16. The community continues to work on a 1.10.x release, with no specific release date planned. ----------------------------------------- Attachment BJ: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: Apache Syncope is an Open Source system for managing digital identities in enterprise environments. ## Issues: There are no issues requiring board attention at this time. ## Activity: The activity level on user@ is still slowly growing, especially with new users asking directions for milestone releases in preparation of 2.0.0. The work towards 2.0.0 seems to be fruitful: we are finalizing the new documentation and improving our Apache Camel-based provisioning features. There is also an ongoing effort to provide Apache Syncope with identity recertification capabilities. The experience with Google Summer of Code is evolving: the Eclipse plugin (SYNCOPE-809) is doing fine, is expected to be completed according to the original schedule and is going to be part of the 2.0.0 release; the Netbeans plugin (SYNCOPE-808), instead, failed the mid-term review but was submitted anyway as incomplete pull request on GitHub. About the Syncope PoC with infra, we are currently on hold waiting for the availability of a "playground zone" - see INFRA-10931 for details. ## Health report: The overall activity is consistently at good level: discussion on project features and improvements are coordinated on dev@, contributions are regularly accepted as pull requests on GitHub. We have reported a new contributor in the team list website page and elected a new committer (Matteo Di Carlo), who accepted. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Guido Wimmel on Sat Apr 05 2014 ## Committer base changes: - Currently 20 committers. - Matteo Di Carlo was added as a committer on Sat Jul 09 2016 ## Releases: - 1.2.8 was released on Fri Jun 03 2016 - 2.0.0-M3 was released on Fri Jun 03 2016 - 2.0.0-M4 was released on Fri Jun 24 2016 ----------------------------------------- Attachment BK: 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). ## Activity: As discussed in the previous report, TinkerPop was preparing for the first releases outside of incubation. Those releases were voted on positively by the community and released the week of July 18th. We released 3.1.3 which was largely a maintenance packaging with some minor features and 3.2.1 which is the recommended version to be on. Going forward, we expect to continue to maintain the 3.1.x line of code providing bug fixes when needed. New development continues on the 3.2.x line and we expect our initial release of Gremlin Language Variants[1] for Python to be part of that line, likely 3.2.2. ## Issues: There are no issues requiring board attention at this time. ## Releases: - 3.1.3 (July 18, 2016) - 3.2.1 (July 18, 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 BL: Report from the Apache TomEE Project [David Blevins] ----------------------------------------- Attachment BM: Report from the Apache Turbine Project [Thomas Vandahl] Apache Turbine Project Board Report, August 2016 Apache Turbine is a servlet based framework that allows experienced Java developers to quickly build web applications. Turbine allows you to personalize the web sites and to use user logins to restrict access to parts of your application. Turbine is a matured and well established framework that is used as the base of many other projects. Status The Turbine project has again some increased activity in the last quarter. The Turbine project has no board-level issues at this time. Community changes No new committers were voted in since the last board report. The last change to the committer base was the addition of Georg Kallidis (2012/09/19). No new PMC members were voted in since the last board report. The last change to the PMC was the addition of Georg Kallidis (2013/09/30). Turbine core project We are in the process of migrating old applications to the new Turbine framework. It turns out that a number of bugs have to be fixed, mostly in supporting Fulcrum components. Also the new security model showed some weaknesses which need to be addressed. The last released version was Turbine 4.0-M2 (2015/12/22). Fulcrum component project Some bigger changes to the Fulcrum Security component. A few bugfixes to others. A new release of Fulcrum Security Torque will probably require a Torque 4.1 release first. The last released component was Fulcrum Yaafi 1.0.7 (2015/10/09). ----------------------------------------- Attachment BN: Report from the Apache Twill Project [Terence Yim] ## Description: Apache Twill is an abstraction over Apache Hadoop YARN to reduce the complexity of developing distributed applications. ## Issues: There are no issues requiring board attention at this time. ## Activity: - All post graduation Infra migration (INFRA-12146) tasks completed - Worked with ASF Press on announcing Twill as TLP (https://s.apache.org/Rzsf) ## Health report: - Have new contributors sending patches - Looking to convert two contributors to committers in next month - Seeing more discussions in the mailing list about new use cases/improvements ## PMC changes: - Currently 6 PMC members - Last PM addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 6 committers and 20 contributors - No new committer added in the last 3 months - One new contributor added in the last 3 months - Last committer addition was Henry Saputra on August 4, 2015 - Last contributor addition was Martin Serrano on August 9, 2016 ## Releases: - Last release was an incubator release 0.7.0-incubator on January 26, 2016 ## Mailing list activity: - dev@twill.apache.org: - 68 subscribers - 85 emails sent to the list in past three months (91 in last report) - commits@twill.apache.org: - 17 subscribers - 48 emails sent to the list in past three months (38 in last report) ## JIRA activity: - 6 new JIRA tickets created in the last month - No JIRA tickets resolved in the last month ----------------------------------------- Attachment BO: Report from the Apache Usergrid Project [Todd Nine] ## Description: Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database (Cassandra), a query engine (Elastic Search), and application layer and client tier with SDKs for developers. ## Issues: There are no issues requiring board attention at this time ## Activity: The Usergrid team is working to improve performance of Usergrid 2.x Work includes: - Completion of unique indexing to use Akka - Team has begun the migration from Thrift to CQL - Bug fix and stability improvements ## Health report: Usergrid is healthy and the community is growing at a moderate pace. ## PMC changes: - Currently 25 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Dunker on Mon Jan 18 2016 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was George Reyes at Tue Sep 29 2015 ## Releases: - 2.1.0 was released on Thu Feb 18 2016 ## Mailing list activity: Numbers reflect very active but slowly growing community. - dev@usergrid.apache.org: - 96 subscribers (down 1 in the last 3 months): - 368 emails sent in the past 3 months (442 in the previous cycle) - user@usergrid.apache.org: -123 subscribers (up 2 in the last 3 months) - 77 emails sent in the past 3 months(56 in the previous cycle) ----------------------------------------- Attachment BP: Report from the Apache Velocity Project [Nathan Bubna] ## Description: - Java-based template engine ## Issues: - No issues requiring board attention at this time. ## Activity: - Very busy, thanks to one developer mostly. Many old patches applied. Much new work toward a 2.0 release. ## Health report: - Moved much closer to a 2.0 release, thanks to hard work of one PMC member. Others chimed in on questions, everyone eager to see a 2.0 release happen. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Mike Kienenberger at Mon Jun 01 2015 ## Releases: - No releases in the last quarter. Last release of consequence was Nov 2010. ## Mailing list activity: - This shows the big bump in dev activity. Pretty sure those unsubscribing weren't interested in being on an active list. - dev@velocity.apache.org: - 124 subscribers (down -2 in the last 3 months): - 151 emails sent to list (6 in previous quarter) - general@velocity.apache.org: - 85 subscribers (down -4 in the last 3 months): - 9 emails sent to list (0 in previous quarter) - user@velocity.apache.org: - 307 subscribers (down -1 in the last 3 months): - 1 emails sent to list (1 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 44 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BQ: Report from the Apache Whimsy Project [Sam Ruby] ## Description: Tools that help automate various administrative tasks or information lookup activities ## Issues: There are no issues requiring board attention at this time ## GitHub experiment: - No issues to report ## Activity: - Whimsy moved to a new VM to avoid SVN, LDAP, and proxy issues thought to be related to the server network; SVN and LDAP problems remain though proxy issues have been resolved due to the fact that whimsy-vm3 is no longer behind a proxy. - 3 minor patches were integrated during this month from ASF members who are not on the PMC. ## Health report: - While there remains sufficient oversight, there has been little progress this quarter in growing a development community. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - One PMC member left last month. - Last PMC addition was Craig L Russell on Sun Dec 13 2015 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Craig L Russell at Mon Dec 14 2015 ## Releases: - Code development is operating under a continuous deployment model ## Mailing list activity: email volume continues to drop. - dev@whimsical.apache.org: - 20 subscribers (up 1 in the last 3 months): - 299 emails sent to list (602 in previous quarter) - notifications@whimsical.apache.org: - 6 subscribers (up 0 in the last 3 months): - 8039 emails sent to list (404 in previous quarter) ----------------------------------------- Attachment BR: Report from the Apache Xalan Project [Steven J. Hathaway] The Apache Xalan Project develops and maintains libraries and programs that transform XML documents using XSLT standard stylesheets. Our subprojects use the Java and C++ programing languages to implement the XSLT libraries. Xalan is a mature project, but we are hoping to acquire more committers who can help with integration builds for a new release that integrates Xerces-C. ISSUES FOR THE BOARD None. CURRENT ACTIVITY Xalan is a mature product. There is little development activity other than patch maintenance. Most of the activity is in the Xalan-J subproject. There are some participants reporting on their build and deployment issues. We are still trying to get more participants to report on their integration build attempts. Work is continuing to perform integration builds using Microsoft Visual Studio 2003 through 2015. Some builds were recently performed for Solaris against the development SVN tree. Some build environment patches have yet to be committed to the code base, but are documented in JIRA. We are currently integrating the Xerces-C parser patch release into a Xerces-C patch release. Most of the communications traffic is via JIRA. Email list activity has been stagnant for 3 months. MEMBERSHIP Changes in the PMC membership: None. Last new committer: May 2014 PROJECT RELEASES Xalan Java 2.7.2 April 15, 2014 Xalan C/C++ 1.11 October 31, 2012 Publishing of project releases was refreshed Oct 30, 2014. OTHER ISSUES We would still appreciate more active persons to build Xalan-C tests. We continue to get requests for Xalan to support XSLT version 2. The Xalan libraries currently support XSLT version 1. Feature ugrades and migration will require more than a few committers. BRANDING ISSUES None. ----------------------------------------- Attachment BS: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J We have been making slow progress towards a Xerces-J 2.12.0 release. A new contributor and one of the committers have been scrubbing through JIRA to help build the release notes. Mailing list traffic has been low; roughly 100+ posts on the j-dev and j-users lists since the beginning of June 2016. No new releases this quarter. The latest release is Xerces-J 2.11.0 (November 30th, 2010). Xerces-C Xerces-C 3.1.4 was released on June 29th to address a security vulnerability. We have a potential new committer who has been contributing several patches since the beginning of July. Mailing list traffic has been low; roughly 85+ posts on the c-dev and c-users lists since the beginning of June 2016. The latest release is Xerces-C 3.1.4 (June 29th, 2016). Xerces-P Nothing in particular to report. There was no development activity over the reporting period. XML Commons There are some broken links on the website that were recently reported. We plan to fix those. Nothing else to report. Committer / PMC Changes The most recent committers were added in February 2015 (Xerces-C) and May 2009 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. One committer has committed changes to SVN since June. Apache Project Branding Requirements The project logo still needs a "TM" to be added to it. ----------------------------------------- Attachment BT: Report from the Apache XML Graphics Project [Glenn Adams] ## Description: - The Apache XML Graphics Project is responsible for software intended for the creation & maintenance of the conversion of XML formats to graphical output & related software components. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - During this reporting period, activity on the three sub-projects has been less than in prior periods. The recent conversion to a Maven based build project continues to be popularized in the community and its use (as opposed to Ant) appears to be increasing. - The second of two security related reports created against the Batik sub-project was resolved, with the first resolved last period. ## Health: - The level of community and developer activity remains at a fairly low level for a relatively mature product, albeit one with a fair number of outstanding unresolved issues. A challenge faced by the project is recruiting more committers to assist in resolving the backlog of issues. At present, there are a total of 839 open, reopened, and in progress JIRA issues in the three sub-projects, distributed as follows: XMLGraphicsCommons 18 Batik 341 FOP 480 There are 3058 previously Resolved and closed issues. So current non-resolved, non-closed issues account for a total of 21% of all issues ever opened against these sub-projects. - The PMC Chair recommends that the PMC undertake an effort to recruit more committers. A discussion has been initiated in the PMC on the subject of increasing the project's activity level, including attracting new committers, improving the outstanding issue count, and other activities. ## PMC: - No new PMC member during this period. - Currently 12 PMC members. - Simon Steiner was added to the PMC on Tue Jan 19 2016 ## Committers: - No new committer during this period. - Currently 21 committers. - Last committer addition was Matthias Reischenbacher, May 2015 ## Releases: - No releases during this period. - XMLGraphics Commons 2.1 was released on Wed Jan 13 2016 - XMLGraphics FOP 2.1 was released on Wed Jan 13 2016 ## Mailing Lists: - Slight decrease in number of subscribers. Mail lists show a 26% reduction in message traffic from the previous period, down from 701 to 517. ----------------------------------------- Attachment BU: 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: - Community discussed about http://zeppelin-project.org (discussion: https://s.apache.org/iAwl). And created issue ZEPPELIN-1117 to address it. Migration of contents from zeppelin-project.org to zeppelin.apache.org is in progress. - https://www.zeppelinhub.com is owned by NFLabs. NFLabs contacted trademark@ about using 'zeppelinhub' brand name and in discussion about branding issue. Continuing engagement with NFLabs. ## Activity: - Planned 0.6.1 release to support Spark 2.0 and scala 2.11 as user request - 0.6.1 release is currently in vote - Community is asking and contributing many features around multi-tenancy support ## Health report: - Steady increment of number of code contributors. +7 last month, 135 total - 3 (code) contributors are currently in vote for the committer. ## PMC changes: - Last (P)PMC addition was Prabhjyot Singh on Mar 29 2016, under incubation ## Committer base changes: - Currently all Committers are PMC ## Releases: - 0.6.0 was released on Jul 02 2016 - 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: - 566 subscribers (up 24 in the last 3 months): - 840 emails sent to list (835 in previous quarter) - dev@zeppelin.apache.org: - 277 subscribers (up 12 in the last 3 months): - 4938 emails sent to list (2813 in previous quarter) ## JIRA activity: - 469 JIRA tickets created in the last 3 months - 301 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BV: Special Report from the Apache OpenOffice Project [Dennis Hamilton] Although the Board relates its comments to the PMC and asks about the PMC, I pointed out that recently, most conversations have been on the AOO security list and now the developer (and QA) lists. In particular, conversations about how the project proceeds, what resources it needs/has, and the handling of now-disclosed security vulnerabilities are on dev@. With regard to senior ASF members watching the PMC list and being silent, I requested that there be more visibility, if only to have the PMC reminded that we are being observed for how we are dealing with matters of importance that have been conveyed from the Board. It is important for the PMC and the project to understand that the Board is not forgetful. 1. Monthly Reporting. Apache OpenOffice will report monthly from now on, although the non-quarterly reports will not be comprehensive. I propose that focus be on the key issues where on-going visibility is called for. I have committed to that as the Chair, and my successor would be expected to follow suit. Key observations. Today, there was no opportunity to consult with the PMC, so these are clearly my personal observations. My verbal report was not so comprehensive. 2. Handling of Security In the past 60 days there have been imminent disclosure of an unexploited vulnerability (with proof-of-concept), working out of a hotfix approach that avoids full-up binary releases, response to disclosure with an advisory and a source patch, and, now, readiness of tested hotfixes with end-user procedure for general availability. The project has now taught itself, after much to-and-fro, how to accomplish this. Were there another vulnerability that could be remedied in this way, it could be done in much less time. It remains problematic how to provide emergency releases that put new installs into the hands of users. There is no consensus on the need for doing so separate from crunching toward feature releases instead. There is push-back against even going through what might be essentially fire drills (with real patches) to confirm controlled ways of doing this. This despite there being some pent-up issues that would qualify and could grow to emergencies. There is also significant effort to upgrade the OpenOffice dependencies on external resources to use the latest versions for their vulnerability repairs, lest the vulnerabilities be exposures to OpenOffice. No source release nor binary distributions reflect these updates. There are insufficient resources to attend to security analysis and preparation of emergency patch/maintenance releases concurrent with focused progress toward a feature release. There is ongoing investigation and discussion on this topic. 3. Trademarks At the July Board meeting, there was concern about what to do about branding and trademarks if it is concluded that the Apache OpenOffice project must retire or pivot away from providing end-user distributions. My recommendation, today, is that this question cannot be addressed up front. It is necessary to first determine what the stages of any retirement would be and how soft-landing of user-facing resources would be accomplished. Given a practicable scenario, it would be appropriate to determine how branding and trademarks can best be handled. 4. Existential Questions and the OpenOffice Contingent Future In partial response to the July Board feedback, there has been a renewed effort to seek additional volunteers for work on Apache OpenOffice development. This is done in the face of an aging and disappearing population of developers with ready-to-hand subject-matter knowledge of OpenOffice, its code base, and the development/deployment methodologies on which it rests. The learning curve for additions to that population is challenging. There are not resources and skills for mentoring and cultivating interested beginners who have the necessary persistence. While worthwhile, and the project is pouring its heart into this, this is not a short-term remedy to immediate concerns. The fundamental reality is that, from a development perspective, the project is being held together by about a half-dozen part-time volunteers. ------------------------------------------------------ End of minutes for the August 17, 2016 board meeting.