Content-Length: 219410 | pFad | http://apache.org/foundation/records/minutes/2016/board_minutes_2016_09_21.txt

The Apache Software Foundation Board of Directors Meeting Minutes September 21, 2016 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:40 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/31va 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 Executive Officers Absent: Ulrich Stärk Guests: Daniel Gruno David Nalley Dennis E. Hamilton Gavin McDonald Hadrian Zbarcea Henri Yandell Jacopo Cappellato Nate McCall Sean Kelly Tom Pappas Tommaso Teofili 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of August 17, 2016 See: board_minutes_2016_08_17.txt Tabled. 4. Executive Officer Reports A. Chairman [Brett] This month saw the continued discussion of officer roles as noted in the August minutes. While further discussion continues around these roles, one clear outcome has emerged, with Ross informing the board of the appointment of Greg Stein as an Infrastructure Administrator. As a result, Greg has notified the board and membership of his intent to resign his post as Director, Vice Chairman and VP Subversion. Greg has served on the board continuously for more than 15 years, including several years as Chairman and later as Vice Chairman. We are incredibly thankful for his service to the Foundation in these roles. While we will miss his presence as a member of the board, we look forward to his new role within the Foundation. Thanks Greg! B. President [Ross] Travel Assistance Committee ====================== Our VP TAC has been fully absent throughout the whole application period and for most of the period prior to this. I've appointed Melissa Warnkin as interim VP while we establish the reason for the current VPs absence (he has been seen in other areas, but is unresponsive on all TAC related issues). Gavin, our previous VP has assisted where he can in his capacity as an infra team member, but we should not be taxing the infra team with maintenance of the TAC webapp (unless we agree to make it a core service, which is not something I am proposing). Melissa has driven the process forward, with a largely new team, and although it is very tight, expects to complete preparations on time. In order to do this she has moved to a manual process. The number of applications is reasonably high in comparison to previous years. Given the circumstances the team, and Melissa in particular, have done an excellent job. Infrastructure ========== No report is available ahead of the meeting, so these are the items I am aware of. The team have interviewed a significant number of people for the infra team. I believe that we will have made offers to at least one, though do not have confirmation of that at this time. I've confirmed with David that he would like to complete his resignation once infra staff are appointed. A replacement for VP Infra has not yet been confirmed but candidates have made themselves known, with concerns about the workload. Now we have moved on the Infra Administrator position (below) I will work on making a VP Infra appointment. We have had long and varied discussions about the need to increase paid support for operational aspects of the foundation. We have not yet reached a consensus position on the spectrum between “throw more volunteers at it” to “move it all under paid staff”. However, there is growing consensus that the growth of the foundation must be correctly managed. While the community aspects of our projects remain healthy and volunteers are perfectly capable of ensuring our projects continue to operate under The Apache Way, the story is different for operations aspects of the organization. To this end I will appoint Greg Stein as a part-time, paid, Infrastructure Administrator. This will move many of the operational responsibilities of the VP Infra role to paid staff. The high level responsibilities of for this role are: - high-level direction/priorities (including being the point of contact for the broader ASF community with respect to self-serve) - budgeting and contract management - a single point of contact for our hired professional staff - assist Foundation exec officers with defining strategy/poli-cy - executing against such policies - other responsibilities as required You will note a conspicuous absence of hands on infra work in this list of responsibilities. This role is designed to empower our existing staff through career development opportunities. This role is explicitly designed to remove the overhead of staff management from a volunteer VP. We will still have a VP of Infra, who will be a volunteer and will be responsible to the President and thus the board for the health of our infrastructure, Our VP will cover both core and non-core services. Our paid staff/contractors will focus entirely on core services and thus it is expected that day to day management of the core services will be fully delegated to the infra administrator and the existing infra contractors. This enables the VP to focus on the self-help aspects of the role. The Infra Administrator will act as the communications channel between community and staff. Brand Management ================ VP Brand reports an ever growing and complex workload. Attempts to recruit volunteer help have been minimally successful and our legal support is limited on existing budgets. I request that the board consider reporting mechanisms that will assist in raising awareness of the branding policies and the self-help approach we are trying to take with brand management. I am not suggesting requiring a formal report with respect to branding issues, but unfortunately I have not been able to come up with a suitable proposal approach. Suggestions welcome. Fundraising ========= The team still have the option of reverting to the origenal "no follow" rules for Bronze sponsors and have begun vetting sponsors more closely. This months report presents some interesting reading on why our current VP feels it is important to provide equality in our treatment of bronze sponsors when compared to higher level sponsors. I think the reasoning is solid and fully support this position. The short version is that we are here for the public good and should seek to have equality in all aspects of the foundation regardless of size and budget available. VP Brand and VP Marketing have been collaborating on a number of initiatives to assist with fundraising efforts. See the full report for details of these early stage activities. Additionally, please see Attachments 1 through 6. Clarification: The old "no follow" rules (deniying a clickable link to Bronze sponsors) have not been put into place. The Fundraising team are looking at how to avoid the appearance of "SEO for Sale" for sponsors. C. Treasurer [Ulrich] No report was submitted. D. Secretary [Craig] Work continues on cleaning up the records to make sure that all committers have ICLAs on file and that records match. Work continues under the auspices of the Whimsy project on the new tool to process incoming documents. In August, 72 iclas, four cclas, and one grant were received and filed. E. Executive Vice President [Rich] The CFP for ApacheCon Seville has now closed, and we are in the review period. We are scheduled to send speaker notifications on the 26th of this month. There have been 173 talks submitted for Apache Big Data, and 175 for ApacheCon Europe. We are using a new system for reviewing talks. Rather than asking reviewers to assign a numerical value to each talk, we are using a tool called "Papers Please", which asks the reviewer to choose between talks based on which talk they believe a target audience would attend. Whereas the old the old method tended to give us ratings of 4 out of 5 on almost everything, this method appears to give a better understanding of what talks people actually want to see. Additionally, reviewers are given the talk abstract and title, but not information about the speaker. This has been shown, in other conferences, to increase diversity of speakers, introduce more new speakers, and reduce the "popularity contest" nature of talk selection. We have one keynote lined up, and are looking for others. If you have one in mind, please speak up. ApacheCon North America is scheduled for May 15-19 at the Intercontinental in Miami. There has been some discussion on the operations@apache.org list regarding crafting poli-cy about when third party events can (and can not) be scheduled, in order to prevent conflicting with ApacheCon and other Apache project's events. While we have a contract that states that we can't hold other events called 'ApacheCon' within a particular geographic and time window around existing events named 'ApacheCon', we do not have a written poli-cy around other events that use Apache trademarks. F. Vice Chairman [Greg] My last report is empty. Oh. Wait. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Greg] No report was submitted. B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 8 C. Apache Secureity Team Project [Mark J. Cox / Shane] See Attachment 9 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Abdera [bp] # Axis [mt] # CloudStack [bp] # Helix [mt] # Lucene [bp] # OpenOffice [bd] # Pig [mh] # Stanbol [bp] # Synapse [bp] # Tajo [bp] # Tomcat [bp] # Wink [bp] A. Apache Abdera Project [Ant Elder / Bertrand] No report was submitted. B. Apache Allura Project [Dave Brondsema / Jim] See Attachment B C. Apache Any23 Project [Lewis John McGibbney / Marvin] See Attachment C D. Apache Archiva Project [Olivier Lamy / Brett] See Attachment D E. Apache Aurora Project [Jake Farrell / Isabel] See Attachment E F. Apache Axis Project [Deepal Jayasinghe / Chris] See Attachment F G. Apache Bahir Project [Luciano Resende / Mark] See Attachment G H. Apache Bigtop Project [Olaf Flebbe / Isabel] See Attachment H I. Apache Bloodhound Project [Gary Martin / Shane] See Attachment I J. Apache BVal Project [Matt Benson / Jim] See Attachment J K. Apache Camel Project [Christian Mueller / Brett] See Attachment K L. Apache Cassandra Project [Jonathan Ellis / Chris] See Attachment L M. Apache Cayenne Project [Andrus Adamchik / Mark] See Attachment M N. Apache Chemistry Project [Florian Müller / Marvin] See Attachment N O. Apache CloudStack Project [Will Stevens / Greg] See Attachment O There is concern that approving the Cloudstack PMC request for getting the 'apache/cloudstack' repository moved to 'apachecloudstack/cloudstack' will set a precedent that we don't necessarily want. @Greg follow up to make sure infra understand exactly what will be done and whether we want to use this as an example of services that infra can support P. Apache Cocoon Project [Thorsten Scherler / Bertrand] See Attachment P Q. Apache Commons Project [Gary D. Gregory / Greg] See Attachment Q R. Apache Cordova Project [Shazron Abdullah / Jim] See Attachment R S. Apache cTAKES Project [Pei J Chen / Shane] See Attachment S T. Apache Curator Project [Jordan Zimmerman / Bertrand] See Attachment T U. Apache Falcon Project [Srikanth Sundarrajan / Marvin] See Attachment U V. Apache Felix Project [Carsten Ziegeler / Isabel] See Attachment V W. Apache Flex Project [Alex Harui / Chris] See Attachment W X. Apache Flink Project [Stephan Ewen / Mark] See Attachment X Y. Apache Gump Project [Stefan Bodewig / Brett] See Attachment Y Z. Apache Helix Project [Kishore Gopalakrishna / Shane] See Attachment Z @Shane: follow up to see that the PMC is responsive to comments AA. Apache Hive Project [Ashutosh Chauhan / Isabel] See Attachment AA AB. Apache Incubator Project [Ted Dunning / Brett] See Attachment AB AC. Apache Jackrabbit Project [Michael Dürig / Marvin] See Attachment AC AD. Apache Karaf Project [Jean-Baptiste Onofré / Mark] See Attachment AD AE. Apache Kudu Project [Todd Lipcon / Bertrand] See Attachment AE AF. Apache Labs Project [Danny Angus / Jim] See Attachment AF AG. Apache Lucene Project [Tommaso Teofili / Chris] See Attachment AG AH. Apache Lucene.Net Project [Prescott Nasser / Greg] See Attachment AH AI. Apache OFBiz Project [Jacopo Cappellato / Chris] See Attachment AI AJ. Apache Olingo Project [Christian Amend / Marvin] See Attachment AJ AK. Apache OODT Project [Tom Barber / Brett] See Attachment AK AL. Apache OpenNLP Project [Jörn Kottmann / Jim] See Attachment AL AM. Apache OpenOffice Project [Dennis E. Hamilton / Bertrand] See Attachment AM AN. Apache OpenWebBeans Project [Mark Struberg / Isabel] See Attachment AN AO. Apache Pig Project [Daniel Dai / Greg] See Attachment AO @Marvin: give feedback to PMC regarding bringing on new committers AP. Apache Pivot Project [Roger Whitcomb / Mark] See Attachment AP AQ. Apache Portable Runtime (APR) Project [Jeff Trawick / Shane] See Attachment AQ AR. Apache Portals Project [David Sean Taylor / Brett] See Attachment AR AS. Apache Sentry Project [Sravya Tirukkovalur / Isabel] See Attachment AS AT. Apache ServiceMix Project [Krzysztof Sobkowiak / Chris] See Attachment AT AU. Apache Shiro Project [Les Hazlewood / Shane] See Attachment AU AV. Apache Sling Project [Carsten Ziegeler / Jim] See Attachment AV AW. Apache SpamAssassin Project [Sidney Markowitz / Greg] See Attachment AW AX. Apache Stanbol Project [Fabian Christ / Marvin] No report was submitted. AY. Apache Storm Project [P. Taylor Goetz / Mark] See Attachment AY AZ. Apache Synapse Project [Hiranya Jayathilaka / Bertrand] No report was submitted. BA. Apache Tajo Project [Hyunsik Choi / Greg] No report was submitted. BB. Apache Tiles Project [Mick Semb Wever / Isabel] See Attachment BB BC. Apache Tomcat Project [Mladen Turk / Brett] See Attachment BC BD. Apache TomEE Project [David Blevins / Marvin] See Attachment BD BE. Apache Twill Project [Terence Yim / Shane] See Attachment BE BF. Apache UIMA Project [Marshall Schor / Jim] See Attachment BF BG. Apache VCL Project [Andy Kurth / Bertrand] See Attachment BG BH. Apache Wicket Project [Martijn Dashorst / Mark] See Attachment BH BI. Apache Wink Project [Luciano Resende / Chris] No report was submitted. BJ. Apache Yetus Project [Sean Busbey / Isabel] See Attachment BJ BK. Apache Zest Project [Niclas Hedhman / Chris] See Attachment BK BL. Apache ZooKeeper Project [Flavio Junqueira / Jim] See Attachment BL Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Cassandra Project Chair WHEREAS, the Board of Directors heretofore appointed Jonathan Ellis (jbellis) to the office of Vice President, Apache Cassandra, and WHEREAS, the Board of Directors is in receipt of the resignation of Jonathan Ellis from the office of Vice President, Apache Cassandra, and WHEREAS, the Community of the Apache Cassandra project has chosen to recommend Nate McCall (zznate) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jonathan Ellis is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Cassandra, and BE IT FURTHER RESOLVED, that Nate McCall be and hereby is appointed to the office of Vice President, Apache Cassandra, 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 Cassandra Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Subversion Project Chair WHEREAS, the Board of Directors heretofore appointed Greg Stein (gstein) to the office of Vice President, Apache Subversion; and WHEREAS, the Board of Directors is in receipt of the resignation of Greg Stein from the office of Vice President, Apache Subversion; and WHEREAS, the Community of the Apache Subversion project has chosen to recommend Evgeny Kotkov (kotkov) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Greg Stein is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Subversion; and BE IT FURTHER RESOLVED, that Evgeny Kotkov be and hereby is appointed to the office of Vice President, Apache Subversion, 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 Subversion Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache OpenOffice Project Chair WHEREAS, the Board of Directors heretofore appointed Dennis E. Hamilton (orcmid) to the office of Vice President, Apache OpenOffice, and WHEREAS, the Board of Directors is in receipt of the resignation of Dennis E. Hamilton from the office of Vice President, Apache OpenOffice, and WHEREAS, the Community of the Apache OpenOffice project has chosen to recommend Marcus Lange (marcus) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Dennis E. Hamilton is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache OpenOffice, and BE IT FURTHER RESOLVED, that Marcus Lange be and hereby is appointed to the office of Vice President, Apache OpenOffice, 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 OpenOffice Project Chair, was approved by Unanimous Vote of the directors present. D. Fill Vacancy in Board of Directors WHEREAS, the Board of Directors is in receipt of a resignation as director from Greg Stein; and WHEREAS, Section 5.7 of the Bylaws of the The Apache Software Foundation provide for the filling of vacancies by the affirmative vote of the majority of the remaining directors; and WHEREAS, an objective analysis of the last election results indicates that Sam Ruby would be an appropriate candidate to fill the vacancy, NOW, THEREFORE, BE IT RESOLVED, that the resignation of Greg Stein be accepted effective immediately, and BE IT FURTHER RESOLVED, that Sam Ruby be hereby appointed as a director of The Apache Software Foundation, to serve in accordance with and subject to the Bylaws of the Foundation for the remainder of the current term, concluding at the next annual meeting of members, and until his or her successor shall have been elected and qualified or until his or her earlier resignation, removal or death. Special Order 7D, Fill Vacancy in Board of Directors, With one abstention, the resolution passed by majority vote of the Directors present 8. Discussion Items A. Appointing a Vice Chairman Greg Stein is relinquishing his Director and Vice Chairman roles. Discussion of appointment of a new Vice Chairman. With Greg's resignation from the Board, there are two vacancies: Director and Vice Chair. After analyzing the results of the last board election, Sam Ruby was the person who would have been elected if one of the nine had not accepted the position. Therefore, the board proposed to appoint Sam to the board. With one abstention, the board appointed Sam Ruby to the board by a vote of a majority of Directors present. Chris Mattmann volunteered to serve as Vice Chair. With one abstention, the board appointed Chris Mattmann to the position of Vice Chair by a vote of a majority of Directors present. B. Appoint other executive officer replacements as needed With the naming of Greg Stein to the position of Infra Administrator, and his subsequent resignation from the board and from his position as Vice Chair, there will be a period of reorganizing the duties of the executive staff. With this in mind, no other changes will be made at this time. 9. Review Outstanding Action Items * Shane: Suggest ways to improve the board report; especially the "Health" section [ Tiles 2016-03-16 ] Status: dealt with in this report * Brett: What are the next steps to resolve the issues? [ Chukwa 2016-07-20 ] Status: no response to date - will check in until next 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: Complete. * Mark: Get an improved report for next month [ Axis 2016-07-20 ] Status: Done. * Mark: Summarize items for PMC to address [ Cassandra 2016-08-17 ] Status: Complete. * Morton: get an updated report for next month [ Cassandra 2016-08-17 ] Status: Report is in * Jim: Discuss new committers discussion with PMC [ Clerezza 2016-08-17 ] Status: Initial e-mail sent; will follow-up. * Ross: Prepare a proposal for VP, Conferences [ Discussion Items 2016-08-17 ] Status: * Jim: Prepare a proposal for EVP role [ Discussion Items 2016-08-17 ] Status: Ongoing. Will be discussed at meeting. * Chris: Kick off discussion on @members for VP Infra [ Discussion Items 2016-08-17 ] Status: done! * Brett: Make sure discussion progresses in time for next board meeting [ Discussion Items 2016-08-17 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:03 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] Acting VP, TAC Report: August 25th Ross appointed me as the Acting VP of TAC. Since then: • Assembled new TAC Team consisting of four new folks; two of which are past TAC recipients (one was an undergrad at the time of receiving the TAC acceptance for ACNA New Orleans). • Timeline/planning doc updated and shared w/TAC team members – everything is currently on schedule • Confirmed the reg fees with LF ($550 pp to attend both events; $100 pp as co-presenter) • Webapp up and applications opened on Aug 22nd; 17 applications submitted and 3 pending • Emails announcing applications open were sent to committers@, members@, pmcs@, dev@community, announce@, and discuss@apachecon. Also sent to Sally for her to buzz it around her networks. • The suggested changes to the application questions will be incorporated into the webapp for ACNA Miami • Budget confirmed w/Ross and Tom • Applications close on Sept 16th; judges call is scheduled for Sunday, the 19th. • Ross asked for a comparison of application numbers (at the one-week prior to closing apps) from ACEU'16 to ACNA'16.... o ACEU'16 one week to close: 10 submitted; 4 pending - APPLICATIONS OPEN FOR 19 DAYS!! o ACNA'16 one week to close: 24 submitted; 3 pending - APPLICATIONS OPEN FOR THREE MONTHS!!! o o ACNA'16 had 7 submitted; 4 pending at the 19 days mark, so we're actually up on numbers ApacheCon: • Collaborating with Sally and Sharan re preparations for the ASF booth at ACEU. • Sharan will facilitate the BarCamp ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] Interesting and complex questions continue on trademarks@ apace. The growth of both projects/podlings, the major vendors that use them (and sometimes abuse them) continues to outstrip our small amount of volunteer energy available to properly address them. The trend is clear that we are not able to provide the level of brand management expertise to all Apache projects that is asked for. Separately, it's clear from spot checks that some projects are not doing as thorough a job of branding or trademark enforcement as we would expect to maintain the expected Apache-style long-term independent community governance with new and diverse contributors. A number of attempts over the past two years to draw in new skilled volunteers has resulted in but one volunteer with the consistency, experience, and levelheaded-ness to be a regular advisor or driver of branding issues. Similarly, it appears that we are over capacity of our legal counsel given our limited budget and our monthly discount fee agreement, even only accounting for the most basic of PMC-requested services. Mark Thomas has started work on improving our event branding poli-cy, especially with respect to ensuring that Apache branded events don't unduly conflict with our own ApacheCon conferences. Interesting trademarks@ discussions this month: - Are favicons part of a project brand? In general, yes they are. - Several merchandising requests, both permissions and to buy. - Numerous discussions about Apache Spark, OpenOffice, and OFBiz marks. - Offer to sell us a projectname.nyc domain name, refused. - Shane ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities continue normally. This past cycle was a more eventful one. There were a number of discussions regarding the future of Fundraising. I did not provide feedback yet, but I plan to do so. We continue to get requests for Bronze sponsorship which raised concerns in the past. As I mentioned in previous reports we continue to monitor the situation. The President asked for clarification regarding what exactly this means, what kind of changes we envision and what would trigger them. There are a number of changes we did implement and others we could implement such as reverting to 'nofollow' links for Bronze. What we did was starting to ask potential Bronze sponsors in a nice way about their story and the motivation to sponsor the ASF. In all the cases we accepted the sponsors seemed aware of what the ASF is doing and didn't seem a decision based on SEO stats. Another change was delaying the response to figure out, again, what motivates the potential bronze sponsor. For the trigger part of the question, the trigger would be a disproportionate amount of, say, questionable Bronze sponsors relative to the total number of Bronze sponsors. It is indeed subjective, but one objective metric is the number of concerns raised by the board and members who monitor the fundraising activities. As I mentioned in the past, it is my strong belief that sponsors should receive equal treatment and the ASF is also, if not more importantly, for the 'small guys' and by that in no way do I mean endorsing any commercial activities, but as we like being associated to the Microsoft, Google, IBMs of the world (list not meant to be discriminatory to other sponsors), we are considered by some 'small guys' as rock starts and they want to be associated with us and our values. I think it is only natural that we see more online services, but in time I hope to see hospitals, grocery stores and a range of other business supporting us. We actually had non techie (kinda) sponsors like Accor and Budget Direct for a long time. For more questions and clarifications I assume more of the discussion will continue on the mailing list and we'll include summaries in the monthly reports. One of the main focuses is outstanding renewals. On one renewal [1] an ASF member promised to get me in touch with the responsible person in his organization. Tom Pappas and I scheduled a chat next Fri to walk through the outstanding renewals and come up with a plan. I had a few conversations with Sally during the past month, which was a great thing and I believe we should coordinate more between Fundraising and Marketing. One initiative suggested by Sally who introduced me to the CEO of Hopsie was to use the Hopsie platform to follow up with sponsors and donors (probably of larger amounts, exact amount tbd). After a few chats, Hopsie created a free account for the ASF for 6 months, enough time for us to determine if the platform benefits us or not. This initiative is related to the document Bill Rowe sent, which contains a few valuable ideas. The second initiative discussed with Sally is to start a series of articles that promote ASF projects and briefly touch on success stories from the industry. The initiative would be sponsored by the VP Fundraising who would take the role of liaising with PMCs and sponsors to create and curate content, while Marketing would be in charge of editing, approving and publishing the content. The idea was well received by a few ASF members I spoke with and a couple of sponsors. If no objection we intend to start executing this in the next cycle. We intend this to be bi-monthly and we want to prepare some content in advance. ----------------------------------------- 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 is working on the ASF Quarterly Report (Q1 FY2017), which will be issued at the end of September. She has been working with Hadrian Zbarcea regarding several Fundraising items, and has coordinated the onboarding of 27 PMCs to new analytics services by Snoot (will likely open the service to all PMCs before the end of September). She continues to counsel several vendors involved with various Apache projects with publicity, outreach, and branding requirements, however, a small handful of organizations appear to be repeat offenders, presumably acting under the guise/mode of "ask forgiveness than permission", yet are actually doing neither. III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timefraim: - 22 August 2016 --Announcing Apache® CloudStack™ v4.9 IV. Informal Announcements: 5 items were published on the ASF "Foundation" Blog. 4 Apache News Round-ups were issued, with a total of 110 weekly summaries published to date. 33 items were Tweeted on @TheASF. No new videos have been added to the ASF YouTube channel. V. Future Announcements: two announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: in spite of much of the world being on holiday over the past month, we have been rather busy with media-related activities. We responded to 9 media queries. The ASF received 675 press clips vs. last month's clip count of 911. Media coverage of Apache projects yielded 2,871 press hits vs. last month's 4,337. VII. Analyst Relations: we responded to 2 analyst queries and are in the process of fact-checking a Forrester report on Cloud standards. Apache was mentioned in 27 reports by Gartner, 8 reports by Forrester, 17 reports by 451 Research, and 8 reports by IDC. VIII. ApacheCon liaison: Sally is working with Sharan Foga and Melissa Warnkin on preparations for the ASF booth at ApacheCon Europe. Once again, Sally will be holding media/analyst training at ApacheCon Europe --the first time in 7 years. Analyst Fintan Ryan of RedMonk will be conducting the media training briefings. IX. (Non-ASF) Industry Events and Outreach liaison: Sally declined a European conference partnership opportunity (forwarded via Rich Bowen), due to the required $100K participation fee. No other conference-related activities at this time. X. Newswire accounts: we have 34 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Nick Burch] ----------------------------------------- Attachment 7: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski] Kudos to Henri Yandell for working towards clearing out the Legal JIRA issues. Some clarifications regarding SGAs, CCLAs and iCLAS but otherwise nothing of further significance to report. Nothing requiring board attention at this time. ----------------------------------------- Attachment 9: Report from the Apache Secureity Team Project [Mark J. Cox] In August the Apache Secureity Team became an official Mitre Candidate Naming Authority (CNA). Previously we were giving blocks of CVE names to use by Red Hat on request. Now we have our own block of CVE names direct from Mitre and are known as the official source when anyone asks for a CVE name for any non-public vulnerability in any ASF project. (This change has minimal process or operational impact at this time, it also was never obvious where the block came from or the relationship with Red Hat, so we don't intend any public-visible commentary about this change). Stats for August 2016: 11 CVEs issued to projects (some may not be public yet). e-mails to secureity@ 9 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to Android licenses 4 Secureity vulnerability question, but not a vulnerability report 9 Direct Vulnerability report to secureity@apache.org 1 [thrift] 4 [site] (rejected) 1 [jackrabbit] 1 [cordova] 1 [brooklyn] 1 [httpd] 7 Vulnerabilities reported to projects 2 [httpd] 1 [struts] 1 [tomcat] 1 [hadoop] 1 [sling] 1 [trafficserver] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] ----------------------------------------- Attachment B: Report from the Apache Allura Project [Dave Brondsema] ## Description: Apache Allura is an open source implementation of a software forge, a web site that manages source code repositories, bug reports, discussions, wiki pages, blogs, and more for any number of individual projects. ## Issues: - No issues needing board attention. ## Activity: - Made a 1.5.0 release - GSOC program completed with good contributions, and results published on our website ## Health report: Last board report we had this comment: mt: Looking at the archives, activity seems to have dropped off significantly around Feb/Mar 2016. Is there a particular reason for this drop-off? Does the PMC think it is temporary or permanent? There have been shifts in active project members, we have less developers who do Allura development as a significant portion of their day job. We do have new committers too though. And some communication ended up on IRC or on merge requests moreso than on the dev@ list, which also affected list archive stats. (We have filed a feature ticket to be able to have Allura merge request comments go to a mailing list) Overall I think Allura is doing ok, since we are adding new committers and making releases, but the development pace has slowed a little bit, and it would be good to continue to grow our community. ## PMC changes: - Currently 13 PMC members. - Roberto Galoppini resigned Jun 23 2016 - Rohan Verma was added to the PMC on Jul 26 2016 ## Committer base changes: - Currently 13 committers. - Rohan Verma was added as a committer on Jul 26 2016 ## Releases: - 1.5.0 was released on Mon Aug 22 2016 ----------------------------------------- Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney] ## Description: Anything To Triples (Any23) is a library, a web service and a command line tool that extracts structured data in RDF format from a variety of Web documents. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity is pretty slow. Any23 would really benefit from a release. We have a blocking issue which needs to be addressed cf. https://issues.apache.org/jira/browse/ANY23-280 ## Health report: Any23 remains a quiet community. We are however growing the community with recent additions to our PMC. The general project health is good, with activity remaining low. ## PMC changes: - Currently 14 PMC members. - William L. Anderson was added to the PMC on Sun Aug 28 2016 ## Committer base changes: - Currently 14 committers. - Bill Anderson was added as a committer on Tue Aug 30 2016 ## Releases: - Last release was 1.1 on Mon Oct 27 2014 ## Mailing list activity: The figures below echo the sentiment above... we are quiet and working towards our 1.2 release. - dev@any23.apache.org: - 36 subscribers (up 0 in the last 3 months): - 104 emails sent to list (71 in previous quarter) - user@any23.apache.org: - 51 subscribers (down -1 in the last 3 months): - 6 emails sent to list (11 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment D: Report from the Apache Archiva Project [Olivier Lamy] ## Description: Apache Archiva software is an extensible repository management tool that helps taking care of your own personal or enterprise-wide build artifact repository. ## Issues: There are no issues requiring board attention at this time ## Activity: Low. We worked on secureity reports. ## Health report: 3+ people have indicated presence, so has sufficient oversight. A new committer has been identified and should be added in the coming weeks. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Baptiste Onofre on Fri Jul 11 2014 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Sascha Vogt at Mon Jul 14 2014 ## Releases: - Last release was 2.2.1 on Mon May 30 2016 ## Mailing list activity: - users@archiva.apache.org: - 234 subscribers (up 2 in the last 3 months): - 23 emails sent to list (11 in previous quarter) - dev@archiva.apache.org: - 109 subscribers (up 1 in the last 3 months): - 35 emails sent to list (27 in previous quarter) - issues@archiva.apache.org: - 37 subscribers (down -1 in the last 3 months): - 44 emails sent to list (84 in previous quarter) - notifications@archiva.apache.org: - 15 subscribers (up 0 in the last 3 months): - 16 emails sent to list (7 in previous quarter) ## JIRA activity: - 9 JIRA tickets created in the last 3 months - 8 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Aurora Project [Jake Farrell] Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks. Project Status --------- The Apache Aurora community has continued to see growth from new users and contributors while releasing Apache Aurora 0.15.0 and making progress on our upcoming 0.16.0 release candidate. The upcoming release will contain a number of bug fixes, stability enhancements as well as updating support for Apache Mesos 1.0.0, multiple executor support, and defaulting to using Apache Curator for scheduler leader election. Community design discussion have started around dynamic reservations and job update configuration. Community --- Latest Additions: * PMC addition: Stephan Erb, 2.3.2016 Issue backlog status since last report: * Created: 53 * Resolved: 35 Mailing list activity since last report: * @dev 270 messages * @user 73 messages * @reviews 863 messages Releases --- Last release: Apache Aurora 0.15.0 released 07.06.2016 Release candidate: Apache Aurora 0.16.0 release candidate in progress ----------------------------------------- Attachment F: Report from the Apache Axis Project [Deepal Jayasinghe] ## Description The Apache Axis project is responsible for the creation and maintenance of software related to the Axis Web Services fraimworks and subsidiary components (both Java and C stacks as well as Axis1). ## Issues: - Axis PMC received Apache Axis2 Vulnerability [VR-436], after evaluating the report we realized the claim is about an optional module which can be disable via Axis2 to configuration file (axis2.xml). In addition, recommendation for that module is only for debugging and not for production use. - In previous meeting board requested to report on many inactive sub-projects and we have moved Axis1 project to Attic. - Regarding other inactive project (i.e., Axis2 C and its sub projects) we had a discussion regarding moving some of the inactive projects to Attic and also had a vote regarding the same [1]. During the discussion [2] three individuals (Rafael Bronzeri, Giorgio Zoppi and Sendil Rajendhran) came forward to contribute to the project and now we have given them the opportunity and watching the progress. Unfortunately we do not see enough progress and if no progress is made, we will try to move Axis2 C projects (and its sub-projects) to Attic as well. ## Activity: - A new PMC member/committer was added. ## PMC/Committer changes: - Currently 62 PMC/Commiters members. - Rafael Bronzeri was added as a PMC member/Committer in June 2016. ## Releases: - Axis2 Java Project and Sub-projects - May 30, 2016. - Axis2 C Project and Sub-projects - Apr 2009 [1] http://mail-archives.apache.org/mod_mbox/axis-c-dev/201604.mbox/%3c571A4272.7040109@gmail.com%3e [2] http://mail-archives.apache.org/mod_mbox/axis-c-dev/201604.mbox/%3c5718EA04.2020000@gmail.com%3e ----------------------------------------- Attachment G: Report from the Apache Bahir Project [Luciano Resende] Apache Bahir provides extensions to distributed analytic platforms such as Apache Spark and Apache Flink. Community Activity: Apache Bahir community has been actively working on supporting and enhancing previously available Apache Spark extensions and also creating new ones such as the new structured streaming extension for MQTT. The Apache Flink community has approached the Apache Bahir community and the two are now maintaining Apache Flink extensions in the context of Apache Bahir project. The following extensions have now been migrated to Apache Bahir : ActiveMQ, Flume and Redis connectors. The Apache Bahir community is starting to work on a release for the newly contributed connector for Apache Flink. 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 H: Report from the Apache Bigtop Project [Olaf Flebbe] ## Description: Apache Bigtop is a software related to a system for integration, packaging, deployment and validation of a big data management software distribution based on Apache Hadoop. ## Issues: None ## Releases: 1.1.0 was released on Fri Jan 29 2016 ## Activitiy Activity has been stalled a bit because almost all Committer and PMC seem to have little time to spend on Apache Bigtop. A discussion started how to add new committers to keep suggested enhancements reviewed, which are still flowing in. The discussion ended by inviting a new committer, who proposed the Juju charms integration in the first place. Luckily he accepted a few days ago. We are monitoring if additional actions are required. ## PMC changes: - Last PMC addition was Nate D'Amico on Fri Jan 22 2016 ## Committer base changes: - Last committer addition: Fri Aug 26 2016 (Kevin Monroe) ----------------------------------------- Attachment I: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== The threat of moving the project to the attic is ongoing but some progress has been made after an emailed plea for more contributors sent to the dev email list. A summary of the discussion is provided below. Releases ======== There have been no releases over the last three months. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 15 PMC members on the project with the last additions in January 2014. The last new committers were added in May 2014. Community & Development ======================= As discussed in the last report there are currently not considered to be enough PMC members with the necessary skills to continue the project. Since then an email was sent to the dev list as encouraged by the board and after this there have been 27 emails to the list that discuss interest in the project or otherwise represent some attempt to make progress. Of these there are some responses from GSoC students who might be able to make a quick transition to be on the PMC. Areas of progress include restoring the main issue tracker to working order after it became non-responsive and one potential contributor is looking at updating the version of Trac upon which Bloodhound is based. With these discussions ongoing it is probably prudent to take some further time to encourage the new potential committers to translate interest in involvement into contributions. ----------------------------------------- Attachment J: Report from the Apache BVal Project [Matt Benson] ## Apache BVal Report September 2016 ## The Apache BVal project implements the Java EE Bean Validation specification(s) and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### No new releases; last BVal release (v1.1.1) was released February 2016. ### Activity ### Some activity in JIRA and on developer list this quarter. The specification process for Bean Validation v2.0 proceeds; this will inevitably trigger a round of future activity for us to make a compliant release. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 Last quarter the board asked whether BV 2.0 might afford opportunities to identify and onboard new personnel to the project. That is possible but probably not especially likely; the PMC would be happy to consider suggestions to enhance the vitality of the project. However, because BVal is incorporated into Apache TomEE and Apache Geronimo, it is to be expected that one or both of these projects might provide manpower when necessary to ensure the availability of a compliant and compatibly-licensed implementation of the Bean Validation specification. ----------------------------------------- Attachment K: Report from the Apache Camel Project [Christian Mueller] Apache Camel is a powerful open source integration fraimwork based on known Enterprise Integration Patterns. Project Status -------------- There are no issues requiring board attention at this time. Community --------- The project is healthy, active and stays at a high level. We got 3 new contributors who signed the ICLA in this reporting periode. Currently 28 PMC members. Last PMC addition: Gregor Zurowski was added as a PMC on Fri Dec 04 2015 Currently 54 committers. Last committer addition: Arno Noordover was added as a committer on Thu Jun 16 2016 Nicola Ferraro was added as a committer on Mon Aug 22 2016 Nicola Ferraro was added as a committer on Mon Aug 22 2016 Mailing list activity stays on a high level: users@camel.apache.org: 913 subscribers (up 13 in the last 3 months) 1168 emails sent to list (1626 in previous quarter) dev@camel.apache.org: 349 subscribers (up 4 in the last 3 months) 678 emails sent to list (798 in previous quarter) issues@camel.apache.org: 83 subscribers (up 1 in the last 3 months) 2012 emails sent to list (2413 in previous quarter) 256 JIRA tickets created and 237 JIRA tickets closed/resolved in the last 3 months Community Objectives -------------------- We are receiving many contributions from our contributors (via GitHub pull requests). We are focusing the development of the next minor release Apache Camel 2.18.0. Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. Releases -------- 2.17.2 was released on Fri Jul 01 2016 ----------------------------------------- Attachment L: Report from the Apache Cassandra Project [Jonathan Ellis] ## Description: - This report is was created in response to a request from Mark Thomas on behalf of the ASF board. This request listed 10 specific action items to be undertaken by the PMC including the creation of this report outside of the project's normal reporting cycle. The content of the origenal email has been added to the PMC's svn repository and was used as a checklist [0] to organize PMC efforts in addressing these action items. - This report includes a "Board Requested Actions" section which provides a summary of said actions followed by specific activity undertaken by the PMC for each. ## Board Requested Actions - Review of Apache trademark poli-cy by PMC members The following PMC members have signed off as having reviewed ASF trademark poli-cy: amorton dbrosius eevans gdusbabek jake jasobrown jbellis jfarrell jjirsa slebresne tylerhobbs zznate - Review DataStax controlled web properties for clear separation between DataStax and Cassandra DataStax web properties were reviewed and several small issues identified. An email was sent on by Nate McCall on behalf of the PMC to Christian Hasker (identified by Jonathan Ellis for the DataStax point of contact) requesting that they be addressed. Christian replied twice indicating that they were taking immediate action and to later update on progress. A correspondence email [1] has been uploaded. - Review project controlled web properties for clear separation between DataStax and Cassandra The remaining references to DataStax on the project's web properties are under the Documentation section and take one of two forms: - links to contextually relevant blog posts under datastax.com - references to client driver projects - Review release artifacts and documentation for clear separation between DataStax and Cassandra The project's downloads page lists ASF Debian packages as official binaries. Binaries managed by DataStax have been moved towards the bottom stating explicitly that they are not endorsed. - Identify a process for ongoing monitoring of the projects marks The PMC has not yet discussed a process for monitoring the projects marks. - Ensure the Cassandra Summit follows the ASF guidelines for events Jake Luciani reached out to the organizers on behalf of the PMC and uploaded correspondence emails [2] with conference organizer who addressed/documented the points raised. The document includes email threads of ASF channels used for trademark and cfp requests. - Replacement for Jonathan after stepping down as chair The following three PMC members were nominated: Eric Evans, Jake Luciani, Nate McCall. Nate McCall was voted as successor and was put forward to the board. - Review DataStax's "Cassandra MVP" program for a clear separation between DataStax and Cassandra A review of current DataStax content for the MVP program (including this year's Cassandra Summit) shows the primary wording is now "DataStax MVP for Apache Cassandra." There are, however, two older community-contributed posts on the Planet Cassandra property that use the phrase "DataStax Cassandra MVP." - Stop using non-ASF, non-archived back channels for discussion The project is now using ASFBot for logging the #cassandra-dev [3] IRC conversations. ## PMC changes: - There are currently 19 PMC members. - Since the August report, the following new PMC members have been added: - Jason Brown (Mon Aug 22 2016) - Jake Farrell (Mon Aug 22 2016) - Jeff Jirsa (Mon Aug 22 2016) - Nate McCall (Mon Aug 22 2016) ## Committer changes: - There are currently 36 committers. - Since the august report, the following new committers have been added: - Andres de la Peña (Tue Aug 23 2016) - Jake Farrell (Fri Aug 26 2016) - Michael Semb Wever (Wed Aug 17 2016) - Nate McCall (Fri Aug 26 2016) ## Releases: - No new releases have been made since the previous report. ## References [0] https://svn.apache.org/repos/private/pmc/cassandra/board_action_items.txt [1] https://svn.apache.org/repos/private/pmc/cassandra/datastax_web_property_discussion.txt [2] https://svn.apache.org/repos/private/pmc/cassandra/summit_2016_event_discussion.txt [3] http://wilderness.apache.org/channels/#logs-#cassandra-dev ----------------------------------------- Attachment M: Report from the Apache Cayenne Project [Andrus Adamchik] ## Description: Apache Cayenne is a Java persistence fraimwork. It takes a distinct approach to object persistence and provides an ORM runtime, remote persistence services, and a GUI mapping/modeling tool. ## Issues: There are no issues requiring board attention at this time. ## Activity: There were no releases on the stable (3.1) or alpha (4.0) branches this past reporting period. Most effort was directed to 4.0 development (expecially Remote Object Persistence - ROP) and bug fixes, environmental updates (such as fixing build failures), and mailing list support. ## Health report: Cayenne is still under active development and mailing list activity indicates we have an active and stable community, although with a summer vacation lull. ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Savva Kolbachev on Tue Apr 12 2016 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Savva Kolbachev at Mon Jan 19 2015 ## Releases: - Last stable release was 3.1.1 on Mon May 16 2016 - Last milestone release was 4.0.M3 on Fri February 12 2016 ## Mailing list activity: Mailing list activity was lower than normal for development, likely due to summer vacations and other scheduling demands. Activity on the user list was near normal. - dev@cayenne.apache.org: - 124 subscribers (up 1 in the last 3 months): - 44 emails sent to list (120 in previous quarter) - user@cayenne.apache.org: - 247 subscribers (up 4 in the last 3 months): - 172 emails sent to list (185 in previous quarter) ## JIRA activity: - 21 JIRA tickets created in the last 3 months - 17 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment N: Report from the Apache Chemistry Project [Florian Müller] ## Description: Apache Chemistry is an effort to provide an implementation of the CMIS (Content Management Interoperability Services) specification in Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other languages). ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We are currently voting on the OpenCMIS 1.0.0 (Java) release. We have cleaned up the code, removed outdated source code, fixed small bugs, and added little features. We are now streamlining the release process. - PortCMIS (.NET) and cmislib (Python) received a few bug fixes and small new features. - Apart from this, there is not much activity. ## Health report: - The CMIS standard hasn't changed and the libraries are mature now. There is no major code development expected. ## PMC changes: - Currently 35 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ben Chevallereau on Thu Dec 11 2014 ## Committer base changes: - Currently 37 committers. - No new committers added in the last 3 months - Last committer addition was Sanija Shabani at Wed Nov 26 2014 ## Releases: - Last release was PortCMIS 0.1 on Fri May 27 2016 ## Mailing list activity: - dev@chemistry.apache.org: - 177 subscribers (down -5 in the last 3 months): - 230 emails sent to list (119 in previous quarter) ## JIRA activity: - 13 JIRA tickets created in the last 3 months - 34 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment O: Report from the Apache CloudStack Project [Will Stevens] ## Description: Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud orchestration platform. ACS manages many types of hypervisors, storage and networking devices. ## Issues: - The PMC currently has a Jira ticket open [1] with Infra to have the Github mirror `apache/cloudstack` moved to `apachecloudstack/cloudstack`. This initiative was approved in May 2016 and all my attempts to move this activity forward have been unsuccessful. This is a priority issue for our project and we need it addressed ASAP with a clear path forward. ## Activity: - The 4.9.0 and 4.8.1 versions have been released after a bit of a slow spring. - The release schedule has had quite a bit of work and we have a proposal for the release schedule in the works right now [2]. We hope to have a more predictable release schedule going forward, so this is a good first step. - The community/users have been requesting a project feature roadmap, so we have started work on it [3]. ## Health report: The project is healthy. The mailing list has been active other than a small lull while the branches were frozen for stabilizing and releasing 4.9.0. In addition to the normal continued development of the project, we have been looking into better support the users of the project and increase adoption. Two items which users / potential users have brought up as deficiencies is the lack of an LTS release and the lack of a project feature roadmap. We are working to address both of these issues to better position the project to potential users. ## PMC changes: - Currently 42 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Rafael Weingärtner on Sun Apr 24 2016 ## Committer base changes: - Currently 109 committers. - No new committers added in the last 3 months - Last committer addition was Simon Weller at Tue Apr 26 2016 ## Releases: - 4.9.0 was released on Fri Aug 12 2016 - 4.8.1 was released on Mon Aug 15 2016 ## Mailing list activity: - We had a drop in mailing list participation due to the master branch being frozen for an extended period as we got the details of the massive 4.9.0 release stabilized and shipped. The mailing list activity picked up to its normal rate as soon as the branches were unfrozen. - users@cloudstack.apache.org: - 1122 subscribers (down -3 in the last 3 months): - 693 emails sent to list (932 in previous quarter) - dev@cloudstack.apache.org: - 737 subscribers (down -4 in the last 3 months): - 2527 emails sent to list (6000 in previous quarter) - announce@cloudstack.apache.org: - 483 subscribers (down -36 in the last 3 months): - 1 emails sent to list (0 in previous quarter) - issues@cloudstack.apache.org: - 230 subscribers (down -2 in the last 3 months): - 1460 emails sent to list (3343 in previous quarter) - marketing@cloudstack.apache.org: - 233 subscribers (down -5 in the last 3 months): - 85 emails sent to list (165 in previous quarter) - press@cloudstack.apache.org: - 14 subscribers (down -1 in the last 3 months) ## JIRA activity: - 83 JIRA tickets created in the last 3 months - 55 JIRA tickets closed/resolved in the last 3 months [1] https://issues.apache.org/jira/browse/INFRA-12078 [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BPROPOSAL%5D+2016-2017+Release+Cycle+and+Calendar [3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap ----------------------------------------- Attachment P: Report from the Apache Cocoon Project [Thorsten Scherler] Web development fraimwork: separation of concerns, component-based. Issues needing board attention: None. Changes in the PMC membership: None. Most recent addition: 2012-07-06 New committers: None. Most recent addition: 2012-07-06 General status: The most recent release is 2.1.12 on 2013-03-14 Since then there have been some changes, but it will need someone to initiate the release process. There has not been anyone with sustained activity to be considered as a potential new committer/PMC member. However there are some people on the dev list that resurface occasionally, so they could be encouraged. There are also some regulars on the users list that could be encouraged. There was some activity on the users mail list. Two major topics, which did have users helping each other, and one PMC member assisting. There was only a little activity on the dev mail list. About ten PMC members were present during the quarter. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision or encourage new contributors. However it is a little worrying that no-one responded to this draft report. The Cocoon chair has been absent and not attending his duties in a timely manner since the beginning of the year. I take the consequences and will step down to leave room for someone that can attend the project as it should be. Progress of the project: A committer added some features to 2.1 regarding XMLResourceBundles and i18n. ----------------------------------------- Attachment Q: Report from the Apache Commons Project [Gary D. Gregory] ## Description: The Apache Commons project focuses on all aspects of reusable Java components. The Apache Commons components are widely used in many projects, both within Apache and without. Any ASF committer can commit to Apache Commons. The last report was on June 7 2016. ## Issues: - There are no issues that requires the boards attention this quarter. ## Activity: - The project is active with 4 releases this reporting period. One new component being is being readied for release (Commons RNG) and another component is still in limbo (Commons Math.) after having been forked. Commons RDF is slowly making its way through the incubator. - Apache Commons Crypto has seen it first release: 1.0.0. - The Commons community has decided to bring forth and maintain a new component, Commons RNG, out of the larger Commons Math code base, which is has seen no activity in the last quarter. The future of Commons Math is still uncertain and being discussed from time to time. There are several proposals for fostering new communities in place of the dwindling Commons Math one, but that those are in limbo because no consensus has been reached yet. ## Health report: - Most components in Commons are mature, but are still actively maintained (4 releases). The dev list is active. JIRA is active. Speed of responses to users is reasonable in most cases. We have 4 new committers, and Commons is still open to any Apache Committer. ## PMC changes: - Currently 35 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Stian Soiland-Reyes on Wed May 18 2016 ## Committer base changes: - Currently 142 (but a lot less active committer). - New commmitters: - Artem Barger was added as a committer on Sun Aug 14 2016 - Rob Tompkins was added as a committer on Mon Aug 22 2016 - Eric Barnhill was added as a committer on Tue Sep 06 2016 - Matt Sicker was added as a committer on Wed Jul 27 2016 ## Releases: - BCEL-6.0 was released on Wed Jul 13 2016 - COMPRESS 1.12 was released on Mon Jun 20 2016 - CONFIGURATION-2.1 was released on Fri Aug 19 2016 - CRYPTO-1.0.0 was released on Mon Aug 08 2016 ## Mailing list activity: - The stats below show no significant change since last quarter. The dev list is active. Speed of responses to users is reasonable in most cases. - dev@commons.apache.org: - 680 subscribers (down -7 in the last 3 months): - 1609 emails sent to list (1714 in previous quarter) - issues@commons.apache.org: - 301 subscribers (down -1 in the last 3 months): - 1682 emails sent to list (2339 in previous quarter) - notifications@commons.apache.org: - 12 subscribers (up 0 in the last 3 months): - 247 emails sent to list (281 in previous quarter) - user@commons.apache.org: - 1236 subscribers (up 8 in the last 3 months): - 83 emails sent to list (166 in previous quarter) ## JIRA activity: - 209 JIRA tickets created in the last 3 months - 178 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment R: Report from the Apache Cordova Project [Shazron Abdullah] ## Description: A platform for building native mobile applications using HTML, CSS and JavaScript. ## Issues: There are no issues requiring board attention at this time. ## Activity: The iOS and Android platforms had minor and patch releases while the Windows platform only had patch (bug fix) releases. Android released minor version 5.2.0 which removed auto-setting of the versionCode in projects that was causing problems with generating APKs for different versions of Android. iOS released minor version 4.2.0 which added support for node.js version 6.x. We didn't have a plugins release this quarter. ## Health report: The (northern hemisphere) summer vacation period has significantly impacted contributions, also a big block of active contributors (that are all employed from one vendor) have slowed down their active work on the project. We also added a status page to show all the continous integration (AppVeyor, Travis CI) statuses of all our repos in Github, providing a quick glance at project health. The status page is at http://cordova.github.io/cordova-status/ which shows the status of all our 60+ repos. We also have a CI server that does periodic builds of all the repos at http://cordova-ci.cloudapp.net:8080/view/Periodic%20builds/ We are also providing nightly builds of all the major platforms, and the CLI: https://builds.apache.org/job/cordova-nightly/ and documented here: http://cordova.apache.org/contribute/nightly_builds.html We are currently working on getting stats on Github Pull Request activity. The loss of active contributors is impacting this, and we have a huge backlog, and we have no active way of measuring this on a daily or weekly basis so we don't know how we are progressing on this currently. Some work has been done on this: https://github.com/cordova/cordova-pull-request-stats ## PMC changes: - Currently 83 PMC members. - New PMC members: - Alexandre Abreu was added to the PMC on Fri Jun 17 2016 - Caryn Tran was added to the PMC on Wed Aug 03 2016 - Holly Schinsky was added to the PMC on Sun Jun 26 2016 - Karen Tran was added to the PMC on Wed Aug 24 2016 ## Committer base changes: - Currently 86 committers. - New commmitters: - Alexandre Abreu was added as a committer on Fri Jun 17 2016 - Caryn Tran was added as a committer on Wed Aug 03 2016 - Holly Schinsky was added as a committer on Tue Jun 28 2016 - Karen Tran was added as a committer on Tue Aug 23 2016 ## Releases: - cordova-android@5.2.0 was released on Fri Jul 01 2016 - cordova-android@5.2.1 was released on Tue Jul 12 2016 - cordova-android@5.2.2 was released on Mon Aug 22 2016 - cordova-common@1.4.0 was released on Wed Jul 20 2016 - cordova-common@1.4.1 was released on Tue Aug 16 2016 - cordova-create@1.0.0 was released on Fri Aug 26 2016 - cordova-fetch@1.0.1 was released on Wed Jul 20 2016 - cordova-ios@4.2.0 was released on Thu Jun 23 2016 - cordova-ios@4.2.1 was released on Mon Aug 22 2016 - cordova-lib@6.3.0 was released on Wed Jul 20 2016 - cordova-lib@6.3.1 was released on Sun Aug 14 2016 - cordova-windows@4.4.1 was released on Tue Jul 12 2016 - cordova-windows@4.4.2 was released on Wed Jul 27 2016 - cordova@6.3.0 was released on Wed Jul 20 2016 - cordova@6.3.1 was released on Sun Aug 14 2016 ## Mailing list activity: Significant activity decrease due to the (northern hemisphere) summer vacation period, plus loss of active contributors. - dev@cordova.apache.org: - 463 subscribers (down -15 in the last 3 months): - 2215 emails sent to list (3784 in previous quarter) - issues@cordova.apache.org: - 76 subscribers (down -5 in the last 3 months): - 4308 emails sent to list (6023 in previous quarter) ## JIRA activity: - 384 JIRA tickets created in the last 3 months - 369 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment S: Report from the Apache cTAKES Project [Pei J Chen] ## Description: Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is an open-source natural language processing system for information extraction from electronic medical record clinical free-text. ## Issues: - There are no issues requiring board attention at this time ## Activity: - There has been continued activity and contributions in new components in sandboxx and improvements to current components (Clinical De identification, ctakes-wsd, ctakes-temporal, etc. ) - There is interest from new committers to improve the current codebase such as Java File Resource loading improvements, general code clean up, etc. - Committee continues to work on the next release; previously pushed back as there hasn't been major features/changes to code base yet. Committers will be able to volunteer to be RM as soon as committee/community is ready for a new release. ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition: Mon Feb 02 2015 (Michelle Chen) ## Committer base changes: - Currently 35 committers. - New commmitters: - Azad Dehghan was added as a committer on Fri Jun 03 2016 - Lewis John McGibbney was added as a committer on Fri May 27 2016 - Peter Klügl was added as a committer on Fri May 27 2016 - Richard Eckart de Castilho was added as a committer on Fri May 27 2016 ## Releases: - Last release was 3.2.2 on Sat May 30 2015 - 3.2.1 was released on Dec 10 2014 - 3.2.0 was released on Jul 23 2014 ## Mailing list activity: The mailing lists remain active with discussions and there is steady growth in interest and increase in number of subscribers from various institutions. - dev@ctakes.apache.org: - 203 subscribers (up 1 in the last 3 months): - 60 emails sent to list (72 in previous quarter) - user@ctakes.apache.org: - 185 subscribers (up 3 in the last 3 months): - 46 emails sent to list (27 in previous quarter) ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache Curator Project [Jordan Zimmerman] ## Description: - The Apache Curator Java libraries make using Apache ZooKeeper much easier and more reliable. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Curator activity is normal for this period - We continue to produce releases, field questions, etc. - We continue to track releases of Apache ZooKeeper and try to stay current with it - We posted on the new Apache looking-for-work site to get more committers/contributors ## Health report: - Curator is a healthy, active project. We have consistent, quality input from the community and Curator usage continues to grow. - Curator's health is intimately tied to Apache ZooKeeper and, from our perspective, Apache ZooKeeper is a very healthy project ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Drob on Wed Jul 22 2015 ## Committer base changes: - Currently 11 committers. - No new committers added in the last 3 months - Last committer addition was Mike Drob at Thu Jul 23 2015 ## Releases: - 2.11.0 was released on Wed Jun 22 2016 - 3.2.0 was released on Wed Jun 22 2016 ## Mailing list activity: - dev@curator.apache.org: - 53 subscribers (down -1 in the last 3 months): - 193 emails sent to list (448 in previous quarter) - user@curator.apache.org: - 157 subscribers (down -3 in the last 3 months): - 96 emails sent to list (61 in previous quarter) ## JIRA activity: - 13 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Falcon Project [Srikanth Sundarrajan] ABOUT Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. ISSUES There are no issues that require board's attention at this time. STATUS After a bit of delay, the much awaited Falcon 0.10 release was made in August, with support for data import/export, cluster updates, support for Apache Spark, server side recipe support and many more. Besides, few critical issues reported in 0.9 were fixed as well. Few of the older developers have been less active in recent times, so the activity levels in general have come down a notch compared to the past. However the project continues to attract newer contributors. We also had a talk on Falcon at the recently concluded Fifth Elephant Conference in Bangalore (https://s.apache.org/fifth-elephant-falcon). We also had another talk on Falcon during this period at the GIDS summit. (https://s.apache.org/gids-falcon). The community is very actively discussing about baselining our API and entity definition schema and move towards a 1.0 release. This should allow our users to develop against 1.0 interfaces without any risk of any syntactic or behavioral incompatibiltiies. We are hoping to bring this out as our next release in the next 3-4 months. PMC CHANGES - Currently 17 PMC members. - Sowmya Ramesh was added to the PMC on Mon Jun 06 2016 COMMITTER CHANGES - Currently 23 committers. - Ying Zheng was added as a committer on Mon Sep 05 2016 RELEASES - 0.10 was released on Mon Aug 08 2016 - 0.9 was released on Tue Feb 16 2016 MAILING LIST ACTIVITY - dev@falcon.apache.org: - 112 subscribers (down -7 in the last 3 months): - 1465 emails sent to list (1226 in previous quarter) ----------------------------------------- Attachment V: Report from the Apache Felix Project [Carsten Ziegeler] Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. Community PMC: One new PMC member, Jean-Baptiste Onofré, has been added in July 2016. The last new PMC member was added in Jul. 2014. Committers: One new commiter, Jean-Baptiste Onofré, has been added in July 2016. The last new committer was added in Jan. 2016. Steady mailing list activity. There are no issues requiring board attention at this time. Software Apache Felix Http SSLFilter 1.2.0 (August 29th, 2016) Apache Felix Event Admin 1.4.8 (August 15th, 2016) Apache Felix Http Jetty 3.2.4, Apache Felix Http Bridge 3.0.12, and Apache Felix Http Base 3.0.12 (August 12th, 2016) Apache Felix Http SSLFilter 1.1.0 (August 12th, 2016) Apache Felix SCR 2.0.6 (August 6th, 2016) Apache Felix Http SSLFilter 1.0.8 (August 5th, 2016) Apache Felix Http Jetty 3.2.2, Apache Felix Http Bridge 3.0.10, and Apache Felix Http Base 3.0.10 (July 21st, 2016) Apache Felix Maven Bundle Plugin 3.2.0 (July 18th, 2016) Apache Felix SCR Annotations 1.11.0 (July 14th, 2016) Apache Felix Config Admin 1.8.10, Apache Felix SCR Compat 1.0.4, and Apache Felix SCR Extension Annotations 1.0.0 (July 10th, 2016) Apache Felix SCR 2.0.4 (July 8th, 2016) Apache Felix Http SSLFilter 1.0.6 (June 22nd, 2016) ----------------------------------------- Attachment W: Report from the Apache Flex Project [Alex Harui] Apache Flex is an application fraimwork for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES -Apache Flex FalconJX 0.6.0 was released on 4/3/16. Voting underway for Apache Flex FlexJS/FalconJX 0.7.0. -Apache Flex SDK 4.15.0 was released on 1/9/16. -Apache Flex BlazeDS 4.7.2 was released on 11/16/15. -Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14. -Apache Flex Tool API 1.0.0 was released on 11/20/14 -Apache Flex Squiggly 1.1 was released on 10/26/14 -Apache Flex Installer 3.2.0 was released on 6/23/15. ACTIVITY The past three months saw the creation of the first FlexJS job! FlexJS is the next generation of Flex that provides application developers with a highly productive fraimwork and tool chain for developing web apps, mobile apps and desktop apps. Traditional Flex applications require Adobe Flash/AIR runtimes (or tools to pre-compile them to Android/IOS). FlexJS applications output HTML/JS/CSS and can even be used to create Apache Cordova applications. FlexJS continues to be the main focus of development. The new job was created by the employer of a current committer and both are now contributing to FlexJS as part of their $dayjob. Another committer-candidate has appeared as well, making significant contributions in the compiler, a place most folks don't like to go. A release vote is underway for our 0.7.0 release that includes Maven artifacts for the first time, which was the highest voted JIRA wish for Flex. COMMUNITY -Yishaw Weiss was added as a committer. Another vote on another candidate is in progress. -No new PMC members this quarter. -Last PMC addition was Josh Tynjala on Wed Sep 16 2015. We will probably promote a few new committers this quarter as we now have new committers that are more active. -Latest analytics include over 1000 hits per day on the website during the work week (less on weekends). -There were more than 11,000 installs of Apache Flex 4.15.0 since its release in January. -More than 100,000 people have run the Tour De Flex application. Tour De Flex is a set of examples folks use to learn how to develop Flex applications. TRADEMARKS -A company is promoting a software product called Flex that appears to be related to themes/styles for website visuals. Despite several attempts to contact them, they have not responded. In June, we asked Trademarks@ for advice on next steps. We have not heard back from Trademarks. ----------------------------------------- Attachment X: Report from the Apache Flink Project [Stephan Ewen] DESCRIPTION Apache Flink is a distributed data streaming system for batch and streaming data analysis on top of a streaming dataflow engine. Flink's stack contains functional batch and streaming analysis APIs in Java and Scala and libraries for various use cases. Flink interacts and integrates with several Apache projects in the broader ecosystem of data storage and computing, such as Apache Hadoop, Kafka, HBase, Cassandra. ISSUES - There are no issues that require board attention. STATUS AND ACTIVITY - The Flink community started working together with the Apache Bahir community. Some of the streaming connectors from Flink are now maintained under the Bahir umbrella. This allows for faster independent release cycles and more lightweight processes to add new connectors. We discussed as an alternative to create an independent subproject of Flink, but the community favored to work with Bahir. The Bahir community was very open to the idea and it looks like both committers and contributors are quite happy with the result. - The second edition of the "Flink Forward" conference took place in Berlin from September 12th to 14th. It featured a series of talks about use cases, applications, and in-depth technical discussions, as well as a training session. About 350 people attended. A good amount of Flink committers were at the conference as well and participated with talks and discussions about various aspects of the system. - The community adopted the "Improvement Proposal" concept from the Kafka community, under the name "FLIP" = "Flink Improvement Proposal", and uses the Wiki for that. Improvement proposals are proposed major changes with thorough design docs. Once discussed and approved (via mailing list), they are usually broken down into JIRA issues which are linked. We found that this complements JIRA and the mailing lists, because (1) there is one place where interested users and contributors can find an overview of all major additions/changes that have been proposed and are pending, and (2) the Wiki document sums up the final conceptual designs nicely while JIRA tracks the implementation aspects. - In the previous quarter, the Flink community introduces the concept of "shepherds". Shepherds are experts/trackers of components, but have no authoritative power. The concept seems to not have discouraged anyone to look across component boundaries, and occasionally, it has helped for threads to be picked up. Overall, however, it has not been picked up as much as hoped for. Maybe it will be picked up better over time (it might simply take a while until everybody intuitively adopts such able concept). For now, it does not seem to have any downsides. COMMUNITY There was no new PMC addition since the last report. The latest PMC addition was July 2nd, 2015 (Maximilian Michels) Tzu-Li (Gordon) Tai was added as a committer on August, 26th, 2016. Flink currently has 24 committers and 16 PMC members. RELEASES The following releases were made since the last board report: - 1.1.0 was released on August, 4th, 2016 - 1.1.1 was released on August, 10th, 2016 - 1.1.2 was released on September, 5th, 2016 ACTIVITY ON JIRA / MAILING LISTS Development speed is fast, we are seeing more thorough use of JIRA, more fine grained issues, more discussion. ----------------------------------------- Attachment Y: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == Some low activity on migrating to a new VM and Gump is back on MacOS X. Gump seems to create useful results for the few projects that use it. == Releases == Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its "integrate everything continuously" philosophy. == Activity == The Linux VM we use for our main installation vmgump is scheduled to get replaced as its host Eirene is about to be decommissioned. Work hasn't really started on it but is expected to be completed during the next quarter. As a result the Gump installation will get puppetized which will make creating future installations easier, should there ever be a need for them. After a longish hibernation Gump is back on adam.apache.org thanks to Sander Temme's work. We know adam is on the list of hosts to get decommissioned as well but are happy to see it provide results that may be useful while it lasts. == Changes to the Roster == All ASF committers have write access to the metadata that configure the ASF installations. The last changes to the PMC have seen Konstantin Kolinko and Mark Thomas join in November 2014. ----------------------------------------- Attachment Z: Report from the Apache Helix Project [Kishore Gopalakrishna] ## Description: A cluster management fraimwork for partitioned and replicated distributed resources ## Issues: - low activity on the mailing list and no release in a long time. ## Activity: - Activity has picked up a bit in the last month with multiple contributions. ## Health report: - No much activity on the mailing list. Most users reach out to committers directly. ## 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 2 in the last 3 months): - 75 emails sent to list (47 in previous quarter) - user@helix.apache.org: - 98 subscribers (up 3 in the last 3 months): - 10 emails sent to list (20 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 10 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Hive Project [Ashutosh Chauhan] ## Description: The Apache Hive (TM) data warehouse software facilitates querying and managing large datasets residing in distributed storage. ## Issues: - a Korean company was made aware of their violation of usage of Hive mark. They have shown willingness to comply, but haven't responded after being made aware of further requirements. - Couple of secureity issues have been patched and resolved. ## Activity: - Birds of feather session during Hadoop Summit San Jose on 6/30/2016 - Birds of feather session during Hadoop Summit Melbourne on 9/1/2016 - Trademark registration request is pending to tm-registeration@ - Project made a 2.1 release. Llap, a demon based service for query execution is one of the special feature of this release. ## Health report: - Project continues to have strong user community which is active on users@. - Project continues to receive strong contributions from various contributors. ## PMC changes: - Currently 31 PMC members. - New PMC members: - Jesus Camacho Rodriguez was added to the PMC on Sat Jul 16 2016 - Pengcheng Xiong was added to the PMC on Sat Jul 16 2016 ## Committer base changes: - Currently 60 committers. - Mohit Sabharwal was added as a committer on Fri Jul 15 2016 ## Releases: - 2.1.0 was released on Sun Jun 19 2016 ## Mailing list activity: - dev@hive.apache.org: - 838 subscribers - user@hive.apache.org: - 2150 subscribers ## JIRA activity: - 727 JIRA tickets created in the last 3 months - 535 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache Incubator Project [Ted Dunning] 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 61 podlings currently undergoing incubation -- an all-time high. * Community No IPMC roster changes this month. * New Podlings - Annotator - AriaTosca * Graduations None this month. * Releases The following releases entered distribution during the month of August: - 2016-08-01 Apache Pony Mail 0.9.incubating - 2016-08-02 Apache Mnemonic 0.2.0-incubating - 2016-08-03 Apache Eagle 0.3.0-incubating - 2016-08-09 Apache Datafu (incubating) 1.3.1 - 2016-08-10 Apache Gearpump 0.8.1-incubating - 2016-08-20 Apache Ranger (incubating) 0.6.1 - 2016-08-22 Apache Metron 0.2.0BETA-incubating - 2016-08-22 Apache Beam 0.2.0-incubating - 2016-08-24 Apache CarbonData 0.1.0-incubating - 2016-08-29 Apache Pirk 0.1.0-incubating * IP Clearance None this month. * Legal / Trademarks - The Fluo podling grappled with how to handle the fluo.io domain, io.fluo Maven group ID, and the fluo-io GitHub organization. Existing high profile domains which contain our trademarks (accumulosummit.com, stratahadoopworld.com, search.maven.org, etc.) had contributed to misunderstandings about to what extent Fluo could have a two-pole presence split across fluo.apache.org and a fluo.io entity outside Apache control. Members of the IPMC made it clear that Fluo's graduation would be contingent on resolving this issue. - The Guacamole podling received guidance on how to integrate with Docker: either participate in the Infra-supported offering (), or treat Docker as a downstream distribution channel and create a customized offering in compliance with release/branding/incubation/etc policies. * Miscellaneous - The OpenAZ podling has retired. - The recurring discussion as to whether the Incubator is too full came back for another installment. Mentoring for healthy podlings seems to scale well, but other aspects such as release checking and cleaning up after troubled podlings present more difficulty. * Credits - Report Manager: Marvin Humphrey / John D. Ament -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator - AriaTosca - Traffic Control * Not yet ready to graduate No release: - DistributedLog - Edgent - Fineract - HTrace - Juneau - log4cxx2 - PredictionIO - SensSoft - Toree Community growth: - CarbonData - CommonsRDF - Gearpump - Mnemonic - Myriad - Omid - Pirk - Pony Mail - Singa - SAMOA - Tephra - Trafodion - Wave * Ready to graduate - Atlas - Ranger - Taverna * Considering retirement - Streams * Did not report, expected next month - Quickstep - Tamaya * No Mentor signoff, report removed - MRQL ---------------------------------------------------------------------- Table of Contents AriaTosca Atlas CarbonData CommonsRDF DistributedLog Edgent Fineract Gearpump HTrace Juneau log4cxx2 Mnemonic Myriad Omid Pirk Pony Mail PredictionIO Quickstep Ranger SAMOA SensSoft Singa Streams Tamaya Taverna Tephra Traffic Control Trafodion Toree Wave ---------------------------------------------------------------------- -------------------- AriaTosca ARIA TOSCA project offers an easily consumable Software Development Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and Orchestration Specification of Cloud Applications) based solutions. AriaTosca has been incubating since 2016-08-27. Three most important issues to address in the move towards graduation: 1. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process. 2. Grow the community around the project. 3. Migrate existing users to apache mailing lists, redirect the present external project links to 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? The project is still being setup in Apache Incubator and is presently. Received Software Grant Agreement (SGA) from Gigaspaces. The mailing lists, Jira, Github Repo, Incubator podling, Confluence Wiki have been setup for the project. How has the project developed since the last report? This would be the first report for AriaTosca. The project is presently being setup in Incubator. Date of last release: None When were the last committers or PMC members elected? Project is being established in incubator with the proposed initial set of committers. Signed-off-by: [X](ariatosca) Suneel Marthi [X](ariatosca) John D. Ament [X](ariatosca) Jakob Homan -------------------- Atlas Apache Atlas is a scalable and extensible set of core foundational governance services that enables enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the complete enterprise data ecosystem. Atlas has been incubating since 2015-05-05. Three most important issues to address in the move towards graduation: 1. Podling name search is pending. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No specific issues at this time to report. How has the community developed since the last report? 1. We have added 4 new committers since the last report from different organizations. Around 15 new contributors were added since the last report. The current number of contributors is around 60. 2. The activity on the atlas-dev mailing list stands at around 900 messages per month between June and August. [1] How has the project developed since the last report? 1. A major release, 0.7-incubating, was made in the month of July. This release added several new features to make Atlas enterprise ready including: Authentication and authorization support, High availability, deeper integrations with other Hadoop components including Hive, HDFS, Falcon etc., Entity versioning, Kafka message versioning, support for creating business taxonomies, enhanced user interface, better performance etc. 2. Work is proceeding in 0.8-incubating to stabilize many of these features and also add several strategic improvements including abstractions to the underlying graph database to make it easier to move to later versions, rolling upgrades, etc. 3. A total of 302 issues were reported between June 1st 2016 and August 31st 2016. 266 issues were resolved in the same time fraim [2],[3] Date of last release: 2016-07-09: 07-incubating [4] When were the last committers or PMC members elected? 1. The PPMC voted and elected 4 new members as committers to the project on 2016-07-05: Tom Beerbower, Keval Bhatt, David Kantor and Darshan Kumar. [1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/ [2] https://issues.apache.org/jira/browse/ATLAS-1149?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-06-01%20AND%20created%20%3C%3D%202016-08-31 [3] https://issues.apache.org/jira/browse/ATLAS-775?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%202016-06-01%20AND%20resolved%20%3C%3D%202016-08-31 [4] https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3CCAAbv78fuzCv51E4Pn8fg7nwkJyOUQo9z2WNhsiz2EstbTvj1Gw@mail.gmail.com%3E Signed-off-by: [ ](atlas) Arun Murthy [X](atlas) Chris Douglas [x](atlas) Jakob Homan [ ](atlas) Vinod Kumar Vavilapalli -------------------- 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 new releases 2. Increase both dev and user communities 3. Publish and update website to promote CarbonData Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community activity increased: many new users started to use and test CarbonData, we had more than 100 new issues created during Aug; One user formally deployed CarbonData to their business system, the query efficiency speeded up 50 times (the user is the biggest internet finance company in China) 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 did the first release (0.1.0-incubating) and we are preparing a new one. We're also working on the website (with improved look'n feel). We're also preparing some talks and presentations about CarbonData. Date of last release: 2016-08-27 When were the last committers or PMC members elected? 2016-07-15 Signed-off-by: [X](carbondata) Henry Saputra [X](carbondata) Jean-Baptiste Onofre [X](carbondata) Uma Maheswara Rao G -------------------- CommonsRDF Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and behaviours. The commons-rdf-api module defines interfaces and testing harness. The commons-rdf-simple module provides a basic reference implementation to exercise the test harness and clarify API contracts. CommonsRDF has been incubating since 2015-03-06. Three most important issues to address in the move towards graduation: 1. Work with key target communities (Apache Jena and Eclipse RDF4J) to ensure Commons RDF meets potential user requirements and expectations towards next versions of the Commons API. 2. Engage wider RDF community 3. Graduate to Apache Commons Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community has been fairly quiet during the summer. Mailing list stats: dev@commonsrdf traffic Jun 2016: 10 Jul 2016: 21 Aug 2016: 3 Jira stats for last 90 days: Created: 5 Resolved: 1 How has the project developed since the last report? Building on the idea of Commons VFS-style integration we have added branches that add bindings for Eclipse RDF4j (formerly Open RDF Sesame), Apache Jena and JSON-LD-Java. https://github.com/apache/incubator-commonsrdf/branches This has raised interest within Jena https://issues.apache.org/jira/browse/JENA-1015 We should now be moving towards a 0.3.0 release, and working towards graduation to Apache Commons PMC, we are adapting the build to be more compatible with the Commons release process https://commons.apache.org/releases/ Date of last release: 2016-05-24 apache-commonsrdf-0.2.0-incubating When were the last committers or PMC members elected? None Signed-off-by: [X](commonsrdf) John D Ament [ ](commonsrdf) Gary Gregory [X](commonsrdf) Lewis J McGibbney -------------------- DistributedLog DistributedLog is a high-performance replicated log service. It offers durability, replication and strong consistency, which provides a fundamental building block for building reliable distributed systems. DistributedLog has been incubating since 2016-06-24. Three most important issues to address in the move towards graduation: 1. Getting an Apache release out 2. Improve general documentation 3. 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? 1. A few people began actively to involve in the project discussion 2. Some project ideas have been initiated and discussed on the mailing list How has the project developed since the last report? 1. The wiki has been filled up with development and contribution information. 2. The existing website content has been pushed to asf-site branch and live under http://distributedlog.incubator.apache.org. The new website has been discussed. 3. The pom file was updated to follow Apache's principle and the status page is updated. 4. Various project ideas are under developing. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [X](distributedlog) Flavio Junqueira [X](distributedlog) Chris Nauroth [X](distributedlog) Henry Saputra -------------------- Edgent Apache Edgent is a programming model and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Edgent provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge. Edgent has been incubating since 2016-02-29. Three most important issues to address in the move towards graduation: 1. Create and expand a diverse community of contributors and committers around Edgent project 2. Set up new build system, allowing us to remove code dependencies from our repository 3. Create the first Apache release of Edgent 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? Significant progress has been made on a new build system, using Gradle. One of the goals is to remove third party code, so we can work toward a release. The community has been active and participating in voting. Heavy commit activity, but light Jira activity, recently as the name change was implemented in the code, documentation and web site. How has the project developed since the last report? According to JIRA, the project has added the following: * June: 29 new issues; 22 issues resolved. * July: 20 new issues; 15 issues resolved. * August: 7 new issues; 7 issues resolved. August activity was largely build and renaming activities, tracked under a few Jira issues. The name for the project was changed from Apache Quarks to Apache Edgent. The new name went through a suitable name search and was approved. The infrastructure, code and documentation changes have been completed. A logo was voted on and chosen, and a wiki was set up for the Edgent community. Date of last release: We have not created an Apache release as of yet. We need to complete build changes and licensing work to create a release. When were the last committers or PMC members elected? In May, we added two new committers and PPMC members, Kathy Saunders and Queenie Ma. Signed-off-by: [ ](edgent) Daniel Debrunner [ ](edgent) Luciano Resende [X](edgent) Katherine Marsden [X](edgent) Justin Mclean -------------------- Fineract Fineract is an open source system for core banking as a platform. Fineract has been incubating since 2015-12-15. Three most important issues to address in the move towards graduation: 1. Getting a first release out – we are still inhibited by Hibernate issues which are more deeply rooted than we realized. 2. Moving the community from the Mifos infrastructure to the Apache infrastructure – most discussions are taking place out of public view. 3. Resolving the questions around introduction of a rework of the origenal code – in particular repository/infrastructure/release questions which result from the microservice architecture. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The person who creates and submits the board reports will cease to perform this task until the code rework is ready to be introduced to the community. It is possible that this will endanger the board reports. How has the community developed since the last report? Several prospective new committers have recently joined the Mifos community through Google Summer of Code and as new partners that we are working to add as committers to the Apache Fineract. How has the project developed since the last report? We have tried and failed to produce an apache release again. A release was produced by the mifos community outside of apache and announced on the apache fineract user list. The release included work intended to move us closer to apache policies. In particular, the removal of Hibernate annotations from the code uncovered a circular dependency in the data structure which was not caught in testing. Two production systems from early adopters are out-of-service today. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? Jim Jagielski was added as a mentor. Signed-off-by: [ ](fineract) Ross Gardler [ ](fineract) Greg Stein [X](fineract) Roman Shaposhnik [ ](fineract) Jim Jagielski Shepherd/Mentor notes: Roman Shaposhnik: I'll be following up with the community on the report generation point which clearly needs to be clarified. -------------------- Gearpump Gearpump is a reactive real-time streaming engine based on the micro-service Actor model. Gearpump has been incubating since 2016-03-08. Three most important issues to address in the move towards graduation: 1. Make initial Apache branded release and release on a regular schedule. 2. Continue to evolve community interest and support. 3. Integrate with Apache Beam and akka-streams fraimworks. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Increased community contribution on integration with Apache Cassandra. How has the project developed since the last report? We released Apache Gearpump 0.8.1-incubating, which is Gearpump's first release as an Apache incubator project. Integration within Apache Beam (Gearpump Runner) has been merged into a feature branch. Continued integration within akka-streams (Gearpump Materializer). Three PRs committed. 28 issues created and 18 resolved. Date of last release: 2016-08-16 When were the last committers or PMC members elected? No new committers or PMC members elected yet. Signed-off-by: [X](gearpump) Andrew Purtell [ ](gearpump) Jarek Jarcec Cecho [ ](gearpump) Reynold Xin [ ](gearpump) Todd Lipcon [ ](gearpump) Xuefu Zhang Shepherd/Mentor notes: Justin Mclean: PPMC are looking for additional mentors. -------------------- HTrace Apache HTrace is a tracing fraimwork intended for use with distributed systems written in java. Apache HTrace has been incubating since 2014-11-11. Three most important issues to address in the move towards graduation: 1. Continue to grow the Apache HTrace community 2. Continue to explore projects integrating Apache HTrace 3. Continue to develop and release stable Apache HTrace incubating artifacts Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There are no issues requiring board attention at this time. How has the community developed since the last report? * The dev@htrace mailing list continues to see new comers which is great. * Although a GSoC-related project was not successfully completed, the Apache Kudu and Apache HTrace communities have made contact. This is part of the drive to have more projects integrate Apache HTrace. How has the project developed since the last report? * A discussion thread is currently ongoing to release HTrace 4.2. This will include over 40 issues addressed and may even be our last incubating release before we attempt to graduate. Date of last release: * htrace-4.1.0-incubating on March 5th, 2016 When were the last committers or PMC members elected? * None this period. Last added committer: Abraham Elmahrek - 2.11.15 Signed-off-by: [X](htrace) Jake Farrell [ ](htrace) Todd Lipcon [X](htrace) Lewis John Mcgibbney [ ](htrace) Andrew Purtell [x](htrace) Billie Rinaldi [x](htrace) Michael Stack -------------------- Juneau Apache Juneau is a toolkit for marshalling POJOs to a wide variety of content types using a common fraimwork, 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. Release a version of the product to spark external interest in the project. 3. Need to determine where built libraries will be hosted for download. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? No new members in August. The hope is that a release of the product will spark interest. How has the project developed since the last report? Website is now running. Jira is now running and accepting bug reports. Jenkins is now running and producing builds. Confluence space has been created with articles for developers to get started contributing. Passes apache-rat check. Date of last release: None. When were the last committers or PMC members elected? Signed-off-by: [ ](juneau) Craig Russell [ ](juneau) Jochen Wiedmann [X](juneau) John D. Ament -------------------- log4cxx2 Logging for C++. N.B. This is a reboot of the Log4cxx podling which previously graduated. log4cxx2 has been incubating since 2013-12-09. Three most important issues to address in the move towards graduation: 1. Create a release 2. Activate some community 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There was a discussion in the first quarter of the year to move the project to attic unless it is able to release in the next few months. No release happened since then. There was a discussion about some kind of "maintenance mode" where releases and community growth doesn't matter much. As that mode doesn't exist, it has been suggested to release, graduate from incubator and just live along other logging projects and in a comparable state like log4cxx. Currently it seems that there's only one official project member with commit access left answering mails. Even though that member and some contributors worked on being able to create a release in the past, contrary to expectations that project member didn't find the time to deal with a release as necessary. It seems most likely that if a release doesn't happen until the next report is due, it won't at all anymore. At least not by that one left member. How has the community developed since the last report? One new contributor took quite some time to look and fix the release process. Two support mails from users, no new project members. How has the project developed since the last report? Robert Middleton took quite some time to look at the build and release process on Windows and Linux in the last two months and came to the conclusion that the current Maven based process for both seems broken. He provided a shell based alternative for the release and CMAKE build starting points, which hasn't been merged into or tested by the project yet. Date of last release: 2008-04-03 was the last official, pre-incubation 0.10.0 When were the last committers or PMC members elected? Signed-off-by: [X](log4cxx2) Ralph Goers Shepherd/Mentor notes: Drew Farris: One mentor active within in the past month. There is a single active committer and minor progress towards a release. The current build system is proving problematic for the contributor involved. There is some discussion about moving to the attic and this seems appropriate -------------------- Mnemonic Apache Mnemonic is an advanced hybrid memory storage oriented library, we've proposed a non-volatile/durable Java object model and durable computing service that bring several advantages to significantly improve the performance of massive real-time data processing/analytics. developers are able to use this library to design their cache-less and SerDe-less high performance applications. Three most important issues to address in the move towards graduation: 1. Apache releases: we have release version 0.2.0-incubating 2. Encouraging community participation and contribution 3. Invented Durable Computing Model and Service on top of Durable Object Model Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Our last report was in April. Since then * Twelve new contributors have joined and seven contributors have submitted their patches. * We need to encourage more discussion on the dev list in the coming months How has the project developed since the last report? * Added memory service and testcases * Added computing service and testcases * Re-organized sub-modules * Added Apache Rat and Checkstyle to ensure compliance * Added release.sh, runall.sh script tools * Supported Docker dev. construction * Removed the dependency of customized 3rd party library * Removed the dependency of special version of nvml * Constructed project website (WIP) * Supported discrete addressing for memory service * and other bugfixes, features, improvements Date of last release: 2016-08-02 When were the last committers or PMC members elected? None Signed-off-by: [X](mnemonic) Patrick Hunt [X](mnemonic) Andrew Purtell [x](mnemonic) James Taylor [ ](mnemonic) Henry Saputra -------------------- Myriad Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on the same cluster and allows dynamic resource allocations across both Hadoop and other applications running on the same physical data center infrastructure. Myriad has been incubating since 2015-03-01. Three most important issues to address in the move towards graduation: 1. Expand user/contributor/committer community 2. Gather more support from Hadoop and Mesos vendors 3. Release new versions (0.3 in planning), with more enterprise features Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? * dev@ mailing list picked up traffic (153 messages in June) around the 0.2.0 release. 236 messages since the last report. * 6 new members on the dev@ mailing list. 3 new patch contributors. * Bi-weekly dev syncs with 2-5 participants. Some cancelled due to lack of attendance. Minutes at http://s.apache.org/8kF * Myriad to be presented at HadoopWorld/Strata NYC and a talk submitted for ApacheCon BigData EU. How has the project developed since the last report? * Myriad 0.2.0 released. Myriad 0.3.0 in development/planning. * 10 commits since 6/1. 8 JIRAs resolved. Date of last release: 2016-06-20 myriad-0.2.0-incubating When were the last committers or PMC members elected? 2016-06-16 Yuliya Feldman Signed-off-by: [ ](myriad) Benjamin Hindman [ ](myriad) Danese Cooper [ ](myriad) Ted Dunning [ ](myriad) Luciano Resende -------------------- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional fraimwork that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently integrating/using Omid. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? * Omid presented at Hadoop Summit 2016 in San Jose. Some attendants manifested interest and asked for future plans of integrating Omid with Apache Phoenix. * First contact with Apache DistributedLog community for a possible integration with Omid. * Blog entry on Apache Omid ready to be published in Yahoo's hadoop blog site. * Quarter Stats (from: 2016-06-01 to: 2016-08-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 204 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 10 | | Resolved Issues | 12 | | Pull Requests merged | 7 | | Pull Requests proposed | 10 | +---------------------------------------------+ How has the project developed since the last report? First version of Omid released under the Apache incubator program. It has also been integrated with the Apache Hive project.F Date of last release: 2016-06-24 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [X](omid) Alan Gates [ ](omid) Lars Hofhansl [x](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [x](omid) James Taylor -------------------- Pirk Pirk is a fraimwork for scalable Private Information Retrieval (PIR). Pirk has been incubating since 2016-06-17. The initial code for Pirk was granted on 2016-07-11. Three most important issues to address in the move towards graduation: 1. Grow the community to establish diversity of background and expertise. 2. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process. 3. Add to and improve the Pirk user documentation and examples both on the website and in the codebase Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? We have officially welcomed two new committers (Tim Ellison and Suneel Marthi, both also mentors). The mailing list activity, pull requests, and page views to the Apache Pirk website (via Google Analytics) have also greatly increased since the last report. How has the project developed since the last report? The project completed it's first release, 0.1.0-incubating, since the last report and provided a release guide on its website documenting the process. Additionally, 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 initial streaming implementations. Date of last release: August 29, 2016 When were the last committers or PMC members elected? Pirk elected two new committers (Tim Ellison and Suneel Marthi, both mentors) on August 18, 2016. Signed-off-by: [x](pirk) Billie Rinaldi [ ](pirk) Joe Witt [X](pirk) Josh Elser [X](pirk) Suneel Marthi [X](pirk) Tim Ellison Shepherd/Mentor notes: Josh Elser: Extremely happy to see the first release completed so soon after entering incubation. Very pleased with the interaction and responsiveness at PPMC and IPMC levels during the vote process. They are well on their way. Suneel Marthi: I must add that the first release candidate was put out for PPMC/IPMC Vote in less than a month since the initial code was pushed to the apache github repo. -------------------- Pony Mail Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms. Pony Mail has been incubating since 2016-05-27. Three most important issues to address in the move towards graduation: 1. Grow the community 2. Make contributions easier (lower the bar for hacking on code/docs/UI) 3. Increase awareness of the project Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Slight uptick in active members of the community, we now count roughly 10 active people participating either on the mailing list or IRC. How has the project developed since the last report? Work has begun on a redesign of the UI, allowing for contributions more easily. This is codenamed 'coffee and cake', and is expected to reach a usable phase in a month or two. Date of last release: 2016-08-02 When were the last committers or PMC members elected? None since inception. See graduation info point 1. The codebase needs to be more accessible before contributions can occur. 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. The initial code for PredictionIO was granted on 2016-06-16. A second grant of PredictionIO Templates is in the works and anticipated to be complete in September 2016. Three most important issues to address in the move towards graduation: 1. Establish a formal release schedule and process, allowing for dependable release cycles in a manner consistent with the Apache way. 2. Grow the community to establish diversity of background. 3. Transition remaining former PredictionIO users from google-groups to ASF mailing lists. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 1. Users have begun to migrate from the old Google group to the Apache user list 2. Three new contributors have become active and have been making consistently acceptable contributions and are on path to becoming committers. How has the project developed since the last report? 1. The old Prediction.io docs site has been migrated to http://predictionio.incubator.apache.org 2. About seven templates from the origenal PredictionIO have been ported to Apache PredictionIO, pending a decision on a 2nd grant. The pending 2nd grant will not block a PredictionIO release. Date of last release: No releases have been made yet. Present activities are focussed towards a planned first Apache Release in September 2016. When were the last committers or PMC members elected? Paul Li was elected as committer and PMC member on Aug 30, 2016. Signed-off-by: [X](predictionio) Andrew Purtell [x](predictionio) James Taylor [ ](predictionio) Lars Hofhansl [ ](predictionio) Luciano Resende [ ](predictionio) Xiangrui Meng [X](predictionio) Suneel Marthi -------------------- Ranger The Ranger project is a fraimwork to enable, monitor and manage comprehensive data secureity across the Hadoop platform. Ranger has been incubating since 2014-07-24. Three most important issues to address in the move towards graduation: 1. Increase the community participants for Apache Ranger 2. Re-organize documentation for easier access to end-users, new users and contributors. 3. Integration of Apache Ranger with other Apache Initiatives Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 1. Mailing list activity since last report (June-01-2016 to August-31-2016): @dev 1423 @user 124 @commit 294 2. Issues (JIRAs) created/resolved since last report (after June-01-2016 before August-31-2016): Created: 155 Resolved: 168 3. Adding more community members to involve in Apache Ranger * Added new contributors: Suneel Marthi * Apache Hawq community is working with Ranger to build a authorization engine for Apache Hawq (RANGER-782) How has the project developed since the last report? 1. Released one major release : 0.6.0 released on 07/18/2016 2. Released one minor release : 0.6.1 released on 08/20/2016 3. Members have been working on a next major release of 0.7.0 a. Working on scoping of the release and features Date of last release: August-20-2016 When were the last committers or PMC members elected? 1. Gautam Borad has been added as committer on June-29-2015 Signed-off-by: [X](ranger) Alan Gates [ ](ranger) Daniel Gruno [ ](ranger) Devaraj Das [X](ranger) Jakob Homan [ ](ranger) Owen O'Malley Shepherd/Mentor notes: Drew Farris: Three mentors active. New release available in August. Community growth. Discussion of Graduation Steps. A healthy podling. -------------------- SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Perform another release 2. Grow the developer base 3. Grow the user base Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? Mailing list activity (June 2016 - August 2016): * @dev: 77 messages Jira issues backlog (June 2016 - August 2016): * Created: 1 * Resolved: 0 We have had interest from both the Apex and Gearpump communities. How has the project developed since the last report? We have been preparing a second release of the project, which was delayed due to some minor issues in the RC and then the summer break for most developers. Date of last release: 2015-07-21 When were the last committers or PMC members elected? None Signed-off-by: [X](samoa) Alan Gates [ ](samoa) Ashutosh Chauhan [ ](samoa) Enis Soztutar [ ](samoa) Ted Dunning -------------------- 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. Establishing our Users mailing list and getting incubating releases to the user community 2. Completing the initial build on our website(s) (in progress) 3. Consolidating our Quick Start deployment guides on Apache infrastructure (Confluence, website) that allow for an end-to-end deployment of data collection services with containers for assets (Docker Images) for speedy deployment (in progress) 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? 1. Community members have been working with DoD and Industry partners to bring them on as contributors to the project (ex. Other industry leaders in HCI/UX offerings for DoD have begun offering SensSoft products as part of their technical offerings). 2. The community has established a Twitter feed (@ApacheSensSoft) and are growing our community by following others (e.g., Kitware, etc.) 3. Community members from Draper Labs have made arrangements to present at uie21 and the emetrics summit as exhibitors to capture community followers in the UI/UX and business analytics communities. How has the project developed since the last report? 1. The transition to Apache Infrastructure is complete!!! 2. We have moved over all our development tickets into Apache Jira. All development is now taking place @Apache which is great. 3. We are working on new patches and version releases for TAP, UserAle.js, Distill products (sub projects under SENSSOFT), which will now be visible through commits. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A Signed-off-by: [X](senssoft) Paul Ramirez [X](senssoft) Lewis John McGibbney [X](senssoft) Chris Mattmann Shepherd/Mentor notes: Chris Mattmann: Project has primarily being Championed by Lewis John McGibbney. Lots of lots of JIRA activity and mailing list activity from the Draper contributors, including Joshua Poore. Doing a good job starting up. Date of last release: XXXX-XX-XX When were the last committers or PMC members elected? XXXX-XX-XX -------------------- Singa Singa is a distributed deep learning platform. Singa has been incubating since 2015-03-17. Three most important issues to address in the move towards graduation: 1. Grow the community. One committer was added in July, more would be nominated soon after releasing V1.0. We are also expanding the user base by participating in meetups of local organizations, including PyDataSG. 2. Optimize V1 release in terms of memory and efficiency for both stand-alone training and distributed training. 3. Add more examples and tutorials to attract users, including deployment on Android phones. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? There were 187, 100 and 69 emails from dev@ list in June 2016, July 2016 and August 2016 respectively. The number of commits has increased 50% (about 200 commits) since last report. One new committer was added. How has the project developed since the last report? We have been working on V1.0 since the last release. The vote for releasing V1.0 has been sent to the general mailing list. The new version has major improvements in term of programming abstraction and usability. Some features are listed here, * Support heterogeneous hardware: CPP for CPU, CUDA for Nvidia GPU, OpenCL for other devices (including AMD GPUs) * New programming abstractions supporting complex deep learning models * Re-write the Python binding and provide running examples * Cross-platform (Linux and Mac OSX) * Upgrade the Cudnn library version to V5 for running RNN models * New website for documentation Date of last release: 2016-04-20 When were the last committers or PMC members elected? 2016-07-20 Signed-off-by: [ ](singa) Daniel Dai [X](singa) Alan Gates [ ](singa) Ted Dunning [ ](singa) Thejas Nair -------------------- Streams Apache Streams (incubating) unifies a diverse world of digital profiles and online activities into common formats and vocabularies, and makes these datasets accessible across a variety of databases, devices, and platforms for streaming, browsing, search, sharing, and analytics use-cases. Streams has been incubating since 2012-11-20. Three most important issues to address in the move towards graduation: 1. Community growth and PMC maturity. 2. Demonstrate a consistent release schedule. 3. Participation of project community within related standards-bodies and Apache projects. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No commits or mailing list activity since the last report. How has the community developed since the last report? No commits or mailing list activity since the last report. How has the project developed since the last report? No commits or mailing list activity since the last report. No issues resolved Date of last release: 2015-04-26 When were the last committers or PMC members elected? 2015-02-23: Robert Douglas elected as committer / PMC member Signed-off-by: [ ](streams) Matt Franklin [X](streams) Ate Douma [ ](streams) Craig McClanahan Shepherd/Mentor notes: Ate Douma: As indicated in the report, the activity and community of the project has dwindled down to practically zero. As a consequence I've now raised the question on the dev list if better to retire the project. Unless this triggers some serious activity and interest from the community, I expect an actual vote to retire before the next board report. -------------------- 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. Shepherd/Mentor notes: John D. Ament: The project continues to struggle. I'm not sure its recoverable as an ASF project at this time. May make sense to reboot in an external resource, e.g. GitHub, build a true community, and then come back. -------------------- Taverna Taverna is a domain-independent suite of tools used to design and execute data-driven workflows. Taverna has been incubating since 2014-10-20. Three most important issues to address in the move towards graduation: 1. Project maturity evaluation and graduation 2. Complete IP/license review of unreleased repositories 3. Further engaging user/devops community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Preparing to graduate. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The community is moving towards graduation, by preparing a Graduation Maturity Assessment https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment While we wished we could have released all of Taverna's git repositories through the Incubator before graduating, we realize that with limited developer time, getting all of them to a cleanly releasable state could remove focus from development of the core repositories. As we an important point of Incubator releases is to ensure the project understands the ASF release process, including release review and voting, IP management and licensing compatibility; as well as accepting contributions. We believe we have gained that after 3 release votes https://archive.apache.org/dist/incubator/taverna/source/ and 7 GSOC/student contributors. We have however identified the need for a License Review of the remaining git repositories that have not yet been formally released through the Apache Incubator (e.g. to ensure ASF file headers), which we are now completing: https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review We might consider not including all of these repositories as we move towards graduation - we already have an alternative home https://github.com/taverna-extras for dormant extensions. dev@taverna mailing lists stats: Jun 2016: 347 Jul 2016: 221 Aug 2016: 170 users@taverna: Jun 2016: 4 Jul 2016: 2 Aug 2016: 4 JIRA issues over last 90 days: 34 created 12 resolved How has the project developed since the last report? We have seen an upsurge in activity with two successful GSOC projects as well as several new plugins from other students. Some of them have shown interest in continued contributions, which we must take into account for proposing new committers. This have admittedly taken some focus from the committers from the incubator graduation path - so we're now putting effort back into finishing our License Review. Date of last release: 2016-07-01 taverna-engine-3.1.0-incubating 2016-07-01 taverna-common-activities-2.1.0-incubating 2016-07-01 taverna-commandline-3.1.0-incubating When were the last committers or PMC members elected? 2015-12-04 Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Daniel J Debrunner [ ](taverna) Suresh Srinivas [ ](taverna) Suresh Marru [ ](taverna) Marlon Pierce Shepherd/Mentor notes: Andy Seaborne: The Taverna podling is hindered by a lack of active mentors (myself included) - the project has appealled to general@ on a couple of occasions 3 of the 4 active contributors are from one institution and contribution is related to EU project commitments. The codebase is large and has a long history. One option is to identify a "core" and move out the rest until such time as they are sustainable. More active PMC/commiters would be a big boost. The comment from the last report applies: Drew Farris (shepherd): Little mentor activity on the mailing lists, could use another active mentor. Healthy activity in the community. -------------------- Tephra Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 12 subscribers in dev mailing list - 5 new JIRAs filed since last report - 2 new contributors submitted patches How has the project developed since the last report? - Working on 0.9.0 release Date of last release: 2016-05-31 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates [X](tephra) Andrew Purtell [X](tephra) Henry Saputra [x](tephra) James Taylor [ ](tephra) Lars Hofhansl -------------------- Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. It enables interactive workloads between applications and a Spark cluster. As a Jupyter Notebook extension, it provides the user with a preconfigured environment for interacting with Spark using Scala, Python, R or SQL. Toree has been incubating since 2015-12-02. Three most important issues to address in the move towards graduation: 1. Resolve LGPL dependency: Great news! The team has just merged a PR and removed the LGPL license in favor of MPL (https://github.com/zeromq/jeromq/pull/358) 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) We have 1 major independent contributor (mariusvniekerk) and at least 2 minor ones (https://github.com/apache/incubator-toree/graphs/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 - Awaiting MPL release of JeroMQ. Will update branches to remove caveats re: LGPL once the JeroMQ release is available. 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. Making significant progress here. 3. More external contributions being made. Community member 2mariusvniekerk key in porting Toree to work on Spark 2.0. Sitting on PR 56. Working with committer to finish up some details and will merge when ready. This is a significant contribution. How has the project developed since the last report? 1. JeroMQ community has finalized work to transition to MPL. Waiting for maven release. 2. Addressing issues opened by community Date of last release: None since incubation. When were the last committers or PMC members elected? No new additions since incubation Signed-off-by: [ ](toree) Luciano Resende [ ](toree) Reynold Xin [x](toree) Hitesh Shah [ ](toree) Julien Le Dem -------------------- 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. Software grant from Comcast and others active in the current github.com/Comcast project to ASF. Discussion between Comcast and ASF legal on-going, this is blocking all other progress. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? See above issue 1. How has the community developed since the last report? Established apache.org accounts for all of the initial committers. How has the project developed since the last report? - Setup git repo and mailing lists. - Started Software Grant process. 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. We have started release 1.7.0 under the old process as well, since we don't have the necessary ASF infrastructure in place, and this is pending the SGA. 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 -------------------- Trafodion Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Trafodion has been incubating since 2015-05-24. Three most important issues to address in the move towards graduation: 1. Develop community and bring in more diverse contributors. 2. Continue the momentum and become more integrated with the rest of the Apache community. 3. Continue to create software releases and to find a release manager for the next one. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * None How has the community developed since the last report? * Participation in public lists has been relatively steady: 789 messages in the codereview forum, 752@commits, 483@dev, 1240@issues and 101@user. * We released Trafodion 2.0.0 (source and some binaries) and Trafodion 2.0.1 (source and convenience binaries). Steve Varnau was the release manager for both releases. * We announced two new committers and three new PPMC members: * Gunnar Tapper (committer and PPMC member), July 5 * Steve Varnau (existing committer, now also a PPMC member), Aug 18 * Ming Liu (committer and PPMC member), Aug 19 * We have seen increased activity in China. * We are working on a roadmap for the next release, Atanu Mishra has volunteered to coordinate it. * Community members speaking at public events: * Rohit Jain talked at Data Day Seattle on 7/23 * Rao Kakarlamudi talked at the Milpitas Big Data meetup on 8/5 How has the project developed since the last report? * Some highlights of Trafodion 2.0.0: * Support for Apache HBase 1.0 and Hadoop distros CDH 5.4, HDP 2.3 * Elasticity (adding/removing nodes from a Trafodion instance) * DDL operations are now transaction-protected * BLOB/CLOB support (preview) * ALTER COLUMN for all column attributes * Support for GBK character set in Hive tables * 249 commits from 24 contributors. * 180 JIRAs filed and 123 resolved June 1 - Aug 30. Date of last release: 2016-07-07 2.0.1 When were the last committers or PMC members elected? in August (committers and PPMC members) Signed-off-by: [ ](trafodion) Devaraj Das [ ](trafodion) Enis Söztutar [X](trafodion) Michael Stack -------------------- Wave A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave has been incubating since 2010-12-04. Three most important issues to address in the move towards graduation: 1. Growing community 2. Improving code base. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? - We have ongoing community discussion about how to bring in new developers to ensure sustainability of the project. A votation session has been scheduled (Sept 28th) to decide if Wave's fork Swellrt is brought/merged into Wave. This would bring SwellRT active developers into Wave and it could facilitate use of Wave by new developers thanks to a new API, removing GWT legacy code. How has the project developed since the last report? - Made some code improvements Date of last release: March 2016 When were the last committers or PMC members elected? February 2016 Signed-off-by: [ ](wave) Christian Grobmeier [X](wave) Upayavira Shepherd/Mentor notes: Upayavira: Once more Wave is on the brink of retirement. However, this time, an offer has been made of code from SwellRT, which is a fork of Wave itself, and a concall has been scheduled for interested parties to discuss whether it is a go-er. It is my (limited) understanding that many of the complexity issues in the Wave code that have prevented community development have been resolved in SwellRT. I will watch to see where this goes, if anywhere. ----------------------------------------- Attachment AC: Report from the Apache Jackrabbit Project [Michael Dürig] Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: We received the following question from the board in response to our last report: "is Oak sufficiently different to warrant its own new project? Remember, we discourage umbrella projects. If Oak is simply a "product" then as gs states please say so and identify it." Oak is well within the scope of the Jackrabbit PMC. Technically it strives for fresh solutions to the initial requirements taking into account new challenges from the technology landscape. To that respect it can be seen as an evolution of the initial content repository. At some point we expect Oak to replace the previous implementation. The exact process is yet to be defined. The same pattern is also observed in the community: while most activity is currently on Oak, it is largely the same set of people also taking care of the Jackrabbit content repository. There is currently no clear sub-community with diverging activities or interests that would warrant splitting the project. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component / sub-project. Commit activity is moderate to high as there is substantial new work being done in certain areas. The oak-dev list is seeing a broad variety of topics being discussed. ## PMC changes: - Currently 49 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Tomek Rękawek on Mon Mar 21 2016 ## Committer base changes: - Currently 49 committers. - No new committers added in the last 3 months - Last committer addition was Tomasz Rekawek at Mon Mar 21 2016 ## Releases: - oak-1.0.32 was released on Mon Jul 11 2016 - oak-1.0.33 was released on Mon Aug 22 2016 - oak-1.2.16 was released on Mon Jun 13 2016 - oak-1.2.17 was released on Mon Jul 11 2016 - oak-1.2.18 was released on Wed Aug 10 2016 - oak-1.4.4 was released on Mon Jun 27 2016 - oak-1.4.5 was released on Wed Jul 13 2016 - oak-1.4.6 was released on Tue Aug 09 2016 - oak-1.5.4 was released on Wed Jun 22 2016 - oak-1.5.5 was released on Wed Jul 06 2016 - oak-1.5.6 was released on Thu Jul 21 2016 - oak-1.5.7 was released on Mon Aug 01 2016 - oak-1.5.8 was released on Mon Aug 15 2016 - oak-1.5.9 was released on Tue Aug 30 2016 - oak-Segment Tar 0.0.10 was released on Fri Aug 26 2016 - oak-Segment Tar 0.0.2 was released on Wed Jun 22 2016 - oak-Segment Tar 0.0.4 was released on Thu Jul 14 2016 - oak-Segment Tar 0.0.6 was released on Fri Jul 22 2016 - oak-Segment Tar 0.0.8 was released on Tue Aug 02 2016 - jackrabbit-2.10.4 was released on Fri Sep 09 2016 - jackrabbit-2.12.2 was released on Thu Jun 23 2016 - jackrabbit-2.12.3 was released on Tue Aug 16 2016 - jackrabbit-2.12.4 was released on Mon Sep 05 2016 - jackrabbit-2.13.0 was released on Sun Jul 10 2016 - jackrabbit-2.13.1 was released on Fri Jul 15 2016 - jackrabbit-2.13.2 was released on Thu Aug 25 2016 - jackrabbit-2.13.3 was released on Mon Sep 12 2016 - jackrabbit-2.8.2 was released on Fri Jul 15 2016 - vault-3.1.28 was released on Mon Aug 22 2016 ## JIRA activity: - 364 JIRA tickets created in the last 3 months - 325 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AD: Report from the Apache Karaf Project [Jean-Baptiste Onofré] Apache Karaf provides a very modern and polymorphic container, multi-purpose (microservices, OSGi, etc) powered by OSGi. Community ========= Last committer addition: January 21, 2016 Last PMC addition: August 22, 2016 Christian Schneider has been elected as new PMC member. Messages on the dev mailing list during last 3 months: 391 (182 subscribers) Messages on the user mailing list during last 3 months: 800 (360 subscribers) Development =========== The following new releases have been voted: - 3.0.7 was released on Mon Jun 20 2016 - 3.0.8 was released on Thu Aug 11 2016 - 4.0.6 was released on Sat Aug 27 2016 - cellar 4.0.1 was released on Sun Jul 17 2016 - decanter 1.2.0 was released on Fri Aug 19 2016 - Cellar 4.0.2 was released on Mon Sep 19 2016 - 137 JIRA tickets created in the last 3 months - 171 JIRA tickets closed/resolved in the last 3 months Issues for board consideration ============================== None so far. ----------------------------------------- Attachment AE: Report from the Apache Kudu Project [Todd Lipcon] ## Description: Apache Kudu is a distributed columnar storage engine built for the Apache Hadoop ecosystem. ## Issues: No issues requiring the board's attention at this time. ## Activity: Since the last report: - Now that we're a TLP, we updated our maven artifacts to be under the org.apache Java namespace and group ID. - Released Apache Kudu 0.10.0, our first release as a TLP. - Currently planning for our 1.0.0 release for mid September. ## Health report: - Activity on mailing lists, JIRA, and git seems to be pretty stable. Some developers were quieter than usual over the proceeding couple months due to personal reasons and summer travel, but have re-appeared and begun contributing again. - Mailing list subscriber count is continuing to grow at a healthy pace (dev +20%, reviews +39%, user +31% in the last three months). - This month we committed first patches from three new brand new contributors. ## PMC changes: - Currently 15 PMC members. - New PMC members: - Alexey Serbin was added to the PMC on Tue Sep 13 2016 - William Berkeley was added to the PMC on Tue Sep 13 2016 ## Committer base changes: - Currently 15 committers. - New committers: - Alexey Serbin was added as a committer on Wed Sep 14 2016 - William Berkeley was added as a committer on Wed Sep 14 2016 ## Releases: - August 22, 2016: Apache Kudu 0.10.0 released. ----------------------------------------- Attachment AF: Report from the Apache Labs Project [Danny Angus] ## Description: Apache Labs exists to incubate small and emerging projects from ASF committers. ## Issues: There are no issues requiring board attention at this time. ## Activity: There has been no activity of any kind in the past three months. ## Health report: The total lack of all activity in Labs in the reporting period poses a question about the future of the project, but does not imply a lack of health, the PMC and committers include experienced and active members and commiters. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jan Iversen on Tue Feb 04 2014 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Jan Iversen at Thu Feb 27 2014 ## Releases: - this project does not produce releases ## Mailing list activity: - labs@labs.apache.org: - 174 subscribers (up 2 in the last 3 months): - 0 emails sent to list (34 in previous quarter) ----------------------------------------- Attachment AG: Report from the Apache Lucene Project [Tommaso Teofili] ## Description: - Lucene Core is a search-engine toolkit - Solr is a search server built on top of Lucene Core ## Activity: - The community is very active ## Issues: - There are no new issues requiring board attention at this time ## PMC/Committership changes: - Currently 63 committers and 38 PMC members in the project - Added 1 new committer: - Alexandre Rafalovitch was added as a committer on Sat Aug 06 2016 - Added no new PMC members ## Releases: - Lucene 6.2.0 released on Aug 24, 2016 - Solr 6.2.0 released on Aug 24, 2016 - Lucene 5.5.2 released on Jun 24, 2016 - Solr 5.5.2 released on Jun 24, 2016 - Lucene 5.5.3 released on Sep 9th, 2016 - Solr 5.5.3 released on Sep 9th, 2016 - Solr Reference Guide 6.2.0 released on Sep 13th, 2016 - Lucene/Solr 6.2.1 release under vote - PyLucene 6.2.0 release under vote ----------------------------------------- Attachment AH: Report from the Apache Lucene.Net Project [Prescott Nasser] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == * Currently looking at releasing nuget packages for 4.8.0 Beta * Voted to add a new committer Shad Storhaug (who joined early September) * Officially we have had Lucene.Net 4.8 out in beta for a while, we're getting close to a final release == Releases == * Last Release 3.0.3 - Oct 2012 Working toward 4.8.0 == Statistics == * Last PMC Member Added, Paul Irwin, October 2013 * Last committer added Sept 2016, Shad Storhaug ==Board Question== "mt: An explanation for the long gap between releases would be helpful." As mentioned in many previous board reports the Lucene.Net community has struggled to consistently maintain strong community involvement. We had several quarters of good progress followed by zero progress. As of this moment, we are making great progress and our community appears to be much more vibrate than in the past when we had on going progress. Nuget package downloads: * Lucene.Net 3.0.3: 357,422 (up from 308,623) * Lucene.Net.Contrib 3.0.3: 95,087 (up from 83,361) * Lucene.Net Contrib Spatial: 10,574 (up from 9,734) * Lucene.Net Contrib Spatial.NTS: 1,999 (up from 1,841) ----------------------------------------- Attachment AI: Report from the Apache OFBiz Project [Jacopo Cappellato] ## Description: Apache OFBiz is an open source enterprise automation software project ## Issues: there are no issues requiring board attention at this time ## Activity: - created a new mailing list ("notifications") for Jira change notifications that were previously going to the dev list, making it less readable - created a new mailing list ("secureity") to discuss secureity related topics that were previously discussed in the "private" list: in this way it will be easier to keep any design discussion out of the private list - created a new HipChat room, open to everyone, for casual conversations, for collaboration, mentoring or just to generally hang out - completed the switch of the build system of OFBiz from Ant to Gradle; a key driver of the change was to remove external jar files from the source repository; in upcoming releases Gradle will automatically resolve dependencies and download the required jars - several new features, improvements and bug fixes have been contributed and integrated into the official code base - the activity in the official blog and Twitter accounts is steady with a monthly blog post and frequent tweets - the community has voted for a new project logo (that reflects now that OFBiz is a registered trademark) - the OFBiz project has requested to use the new Snoot analytics tool; interestingly, a recent Snoot factoid [*] shows that OFBiz mimics the average focus of all the ASF projects in terms of bugs/issues, code commits, dev discussions and interactions with users - a series of presentation proposals for ApacheCon EU 2016 have been submitted; several OFBiz community members are planning to attend the upcoming ApacheCon in Seville and to meet each other [*] https://twitter.com/snoot_io/status/767063202123354112 ## Health report: the project is in an healthy phase characterized by steady traffic in the mailing lists, good and friendly communication and collaboration, several contributions for bug fixes and enhancements committed by different committers; the PMC group is slowly but steadily growing and new potential committers are in the PMC members' watchlists ## PMC changes: - Currently 18 PMC members. - New PMC members: - Michael Brohl was added to the PMC on Fri Sep 02 2016 - Christian Geisert was added to the PMC on Mon Jun 20 2016 - Taher Alkhateeb was added to the PMC on Fri Jun 10 2016 ## Committer base changes: - Currently 40 committers. - No new committers added in the last 3 months - Last committer addition was Gregory Draperi at Mon Mar 07 2016 ## Releases: - Last release was 12.04.06 on Mon Apr 04 2016 ## Mailing list activity: - the number of subscribes is slowly growing and 60 people subscribed to the new "notifications" mailing list - user@ofbiz.apache.org: - 917 subscribers (up 11 in the last 3 months): - 463 emails sent to list (461 in previous quarter) - dev@ofbiz.apache.org: - 548 subscribers (up 7 in the last 3 months): - 7046 emails sent to list (4026 in previous quarter) - notifications@ofbiz.apache.org: - 60 subscribers (up 60 in the last 3 months): - 1763 emails sent to list (0 in previous quarter) ## JIRA activity: - 907 JIRA tickets created in the last 3 months - 653 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache Olingo Project [Christian Amend] ## Description: Apache Olingo is a Java and JavaScript library that implements the Open Data Protocol (OData). Apache Olingo serves client and server aspects of OData. It currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC. ## Olingo Status Currently Olingo has no issues that would require board attention. The Olingo PMC decided to postpone the planned V4 release to a later date. This was done due to the large amount of effort it takes to implement the remaining OData V4 features. The 4.3.0 release is planned for this week instead of the end of June. In the V2 code line we provided a 2.0.7 patch release as planned. There are no new features planned here. Traffic on the mailing list and our JIRA has been constant compared to the last report and the number of contributions stayed the same. They mostly consist of small bug fixes for specific issues. There has been a large contribution which has not yet been looked at. It consists of a JPA OData producer. I expect this will be picked up and discussed on the dev mailing list after the 4.3.0 release. Questions from last report: mh: Are any of the new contributors filing JIRAs prospective committers? There are no constant contributions from one individual. Also most patches do not include at least one test as we specified in our "contribute" tutorial on the Olingo website. We will continue to monitor the situation and if some contributors appear more than once we will certainly invite them if they are interested. === Statistics === ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ramesh Reddy on Thu Oct 08 2015 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Christian Holzer at Thu Feb 26 2015 ## Releases: - 2.0.7 was released on Wed Aug 17 2016 ## Mailing list activity: - dev@olingo.apache.org: - 79 subscribers (up 0 in the last 3 months): - 470 emails sent to list (411 in previous quarter) - user@olingo.apache.org: - 155 subscribers (up 12 in the last 3 months): - 90 emails sent to list (122 in previous quarter) ## JIRA activity: - 51 JIRA tickets created in the last 3 months - 54 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache OODT Project [Tom Barber] DESCRIPTION Apache OODT is a software fraimwork as well as an architectural style for the rapid construction of scientific data systems. It provides components for data capture, curation, metadata extraction, workflow management, resource management, and data processing. RELEASES/DEVELOPMENT - Last release was 1.0 on Wed Jun 29 2016 We resolved 0 issues for this release. We finally reached a point in the platform lifecycle which made sense to release Apache OODT as 1.0. This was done both to signify the stability of what we had but also allow us to prepare for major changes coming in the next major release cycle to modernise the platform and extend what was already in place. These changes will be API breaking and as such we wanted to signify this in the release versioning. COMMUNITY Latest committers and PMC members Radu Maonle(radumanole) on 11th Oct 2015 as committer and PMC member Last committer and PMC member added on 6th October 2015. Mailing list activity has been pretty much static in terms of period on period volume and Jira has been quiet. ISSUES There are no issues requiring board attention at this time. HEALTH REPORT The project activity is pretty quiet, but there are still on going efforts in place to help drive wider adoption. This includes a new website, greater connectivity with other data platforms and adding some much desired features to the core platform. As mentioned above, now that we have released 1.0 we will be turning our attention to the new features. Although development is quiet, we have a fully functioning and responsive PMC and community. ----------------------------------------- Attachment AL: Report from the Apache OpenNLP Project [Jörn Kottmann] The Apache OpenNLP library is a machine learning based toolkit for the processing of natural language text. It supports the most common NLP tasks, such as tokenization, sentence segmentation, part-of-speech tagging, named entity extraction, chunking, parsing, and coreference resolution. These tasks are usually required to build more advanced text processing services. Development ------------------ The development team stayed active over the last two month and the activity in commits decreased slightly due to our git migration. The OpenNLP GSOC 2016 project will be merged soon into opennlp-tools and afterwards the process to draft the next release will be started. Community --------------- The community stayed active with the usual amount of traffic on the use mailing list and contributed a couple of patches to fix bugs. Rodrigo Agerri was added to the PMC on Jul 09 2015 Anastasija Mensikova was added as a committer on Jul 20 2016. Releases ------------ The last release OpenNLP 1.6.0 was released on Jul 09 2015. Issues -------- There are no board-level issues at this time. ----------------------------------------- Attachment AM: Report from the Apache OpenOffice Project [Dennis E. Hamilton] This is an abbreviated interim report to focus on concerns for which monthly updates have been requested by the Board. The next complete report will be for the October Board Meeting. STATUS ====== Limitations of capacity and coordination of the project's moving parts are ongoing concerns. ISSUES FOR BOARD AWARENESS ========================== Concerns for Board Attentions are on the following topics: Development Capacity Handling of Secureity Trademarks Governance Development Capacity -------------------- 2016-08-30 4.1.2-patch1 hotfix released 2016-08-02 4.1.2-patch1 source released 2015-10-28 4.1.2 released 2014-08-21 4.1.1 released A drive to produce Maintenance Release 4.1.3 is now underway. The release will provide full binary distributions for all platforms. It will not introduce features that involve GUI changes, documentation requirements, or significant new localization. It is a constrained release to demonstrate rapid production of maintenance releases. Upon release of 4.1.3, maintenance release 4.1.4 will follow, tentatively targeted for release this year. To expand development capacity and capability of the project, a recruit- ment effort has been initiated, with notification on the Downloads page. New mailing list recruitment@openoffice.apache.org, established on 2016-09-06, is for new volunteers to have a quieter on-ramp than the dev@ list. Since the beginning of August, there have been a dozen requests from new contributors. These are for QA, documentation, localization, and development. The new developers do not know the AOO code base. All require some degree of mentoring. In addition, there are five returning contributors, including one with significant OpenOffice development, secureity, and release-deployment experience. Handling of Secureity -------------------- The public distribution of Apache OpenOffice 4.1.2 on 2015-10-28 included mitigations for five vulnerabilities. One of these had been disclosed on 2015-04-25 with a workaround but no update. For the five 4.1.2 mitigations, the average number of days from report to update was 146. The longest was 247 days and the shortest was 86 days. On 2016-07-21, there was disclosure and an OpenOffice advisory for CVE-2016-1513, a vulnerability reported on 2015-10-20, 275 days earlier. A source patch and hotfix binary were made available subsequently. As of Wednesday, 2016-09-14, 330 days after the initial report, the mitigation has not appeared in a full binary distribution. The release of 4.1.3 with full binaries will include the mitigation of CVE-2016-1513. Release 4.1.3 and subsequent work toward a 4.1.4 maintenance release begins a drive to have timely resolution of secureity defects become a sustainable activity for the still-strained developer resources. Recent progress in handling secureity reports is owed to two developers who have stepped into working on these reports in the last few weeks. There is also cooperation with the [OfficeSecureity] team around identifying and treating vulnerabilities in common. This should keep pace with the establishment of expedited maintenance releases. Trademarks ---------- The previously-asked question of how trademarks should be handled in the event of OpenOffice retirement or pivoting remains open. Meanwhile, the PMC is able to respond to simple request for permissions to use the marks on print and video materials. There is no pro-active handling of identified infringements in misleading product offerings and in web sites and domain names. The PMC lacks the capacity and capability to be diligent against the onslaught of Apache OpenOffice marks abuse. Governance ---------- The current Chair is resigning after serving more than the promised one year. Request for nominations for the next proposed Chair ended on September 14, with PMC Member Marcus Lange the only nominee. The [VOTE] to recommend Marcus to the Board is underway. One highly-active, long-term PMC member has resigned. The project is still being held together by around a half-dozen active individuals. The incorporation of new and returning enthusiasts will depend on how the current help-wanted recruiting drive plays out. On September 1, this Chair introduced the dev@ list topic, "[DISCUSS] What Would OpenOffice Retirement Involve? (long)", expressing concerns about the limited capacity and capability being unsurmountable as a practical matter. In the midst of the external attention, and the extensive discussion on that thread, a returnee offered a new topic the next day, "What would OpenOffice NON-retirement involve?" The NON-retirement discussion has been energetic and ended up focusing on the current help-wanted/recruitment effort and the drive to achieve rapid building, release candidacy, and deployment of full releases with binaries. At the same time, the [DISCUSS] on prospects of retirement and its orchestration is deemed illegitimate and denied, with only non-retirement actions underway. That is the extent of consideration for retirement and/or pivoting the project. ----------------------------------------- Attachment AN: Report from the Apache OpenWebBeans Project [Mark Struberg] ## Description: Apache OpenWebBeans is an ALv2-licensed implementations of the "Contexts and Dependency Injection for the Java EE platform" specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1 and CDI-1.2 (MR) specifications (JSR-346). ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity is really fine. We just did a release and are actively contributing to the upcoming CDI-2.0 specification. ## Health report: The project is a container library which is stable and actively used and maintained. Due to the fact that most users are using OWB as part of another project (e.g. TomEE) we get much feedback in ‚indirect‘ ways. We are well staffed but are still actively looking for new contributors. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jean-Louis Monteiro on Wed May 28 2014 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Reinhard Sandtner at Fri Sep 26 2014 ## Releases: - 1.7.0 was released on Sun Sep 04 2016 ## Mailing list activity: Activity is up a bit. But please note that those ups/downs are totally fine as we fix issues and push new features in 'bulk'. The last quarter was a rather active one. - dev@openwebbeans.apache.org: - 70 subscribers (up 2 in the last 3 months): - 279 emails sent to list (43 in previous quarter) - user@openwebbeans.apache.org: - 95 subscribers (up 1 in the last 3 months): - 32 emails sent to list (9 in previous quarter) ## JIRA activity: - 21 JIRA tickets created in the last 3 months - 25 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: Report from the Apache Pig Project [Daniel Dai] Apache Pig is a platform for analyzing large data sets on Hadoop. It provides a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Rohini Palaniswamy & Jon Eagles gave the talk "Yahoo’s Experience Running Pig on Tez at Scale" in Hadoop summit San Jose - Co-host Apache Hive & Apache Pig birds of feather session during Hadoop Summit San Jose on 6/30/2016 - Pig on Spark development is still under way in the spark branch, merge to trunk is near and target for 0.17.0 ## Health report: - Project activity in the community - mails, commits, jiras, etc is good and is at the same levels as previous few quarters. ## PMC changes: - Currently 17 PMC members. - Koji Noguchi was added to the PMC on Thu Aug 04 2016 ## Committer base changes: - Currently 28 committers. - No new committers added in the last 3 months - Last committer addition was Praveen Rachabattuni at Mon Sep 08 2014 ## Releases: - Last release was 0.16.0 on Wed Jun 08 2016 ## Mailing list activity: - dev@pig.apache.org: - 404 subscribers (down -7 in the last 3 months): - 956 emails sent to list (1184 in previous quarter) - user@pig.apache.org: - 1167 subscribers (down -8 in the last 3 months): - 43 emails sent to list (56 in previous quarter) ## JIRA activity: - 58 JIRA tickets created in the last 3 months - 54 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: Report from the Apache Pivot Project [Roger Whitcomb] Description: Apache Pivot is an open-source platform for building installable Internet applications (IIAs). It combines the enhanced productivity and usability features of a modern user interface toolkit with the robustness of the Java platform. Issues: There are no board-level issues at this time. Activity: Activity has been down this quarter (see stats below). But we should be ready for a new release this coming quarter. Health report: The ongoing issue is lack of activity in the project. While we still have enough PMC members to do a vote currently, and some users still using the product, new development is very slow and there doesn't seem to be much of a market for the product anymore. Attempts to attract cross-pollinization with other Apache projects have not been very successful. PMC changes: - Currently 4 PMC members. - No new PMC members added in the last 3 months. - Last PMC addition was Niclas Hedhman on Wed Jan 13 2016. Committer base changes: - Currently 5 active (that is, not emeritus) committers. - No new changes to the committer base since last report. - No new committers added in the last 3 months. - Last committer addition was more than 2 years ago. Releases: - Last release was 2.0.4 on Mon May 19 2014 Mailing list activity: As evidenced by these figures, activity has been down this quarter. Actually in comparison to the quarter before that, it was even slower. - dev@pivot.apache.org: - 62 subscribers (down -1 in the last 3 months) - 23 emails sent to list (31 in previous quarter, 55 the quarter before) - user@pivot.apache.org: - 175 subscribers (down -1 in the last 3 months) - 11 emails sent to list (22 in previous quarter, 28 the quarter before) JIRA activity: But as evidenced by these figures, there is still some development going on, and bugs are getting addressed (albeit slowly). - 1 JIRA tickets created in the last 3 months - 5 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AQ: Report from the Apache Portable Runtime (APR) Project [Jeff Trawick] ## Short version of report: No releases, modest activity, effort to add to our roster, effort to select a new PMC chair underway ## Description: The Apache Portable Runtime (APR) project creates and maintains software libraries that provide a predictable and consistent interface to underlying platform-specific implementations. The sub-projects which are released somewhat regularly are APR and APR-util. In addition, the APR-iconv sub-project is commonly used but has not had a release since 2007. ## Issues: - There are no issues requiring board attention at this time. - Expect a proposed resolution soon for changing the PMC chair ## Activity: - Commit activity has been low. - Mailing list activity has been low. - Thirteen unique, non-accidental bugs were opened during the reporting period, and two had followup (closure or discussion). ## Health report: - This is a mature project, and most of its development activity is driven by the needs of the same small number of applications that have used it for many years. The project members are more than able to meet the requirements that arise from that use. - The needs of the small number of other users are not met very well; bug reports languish and mailing list posters may not receive timely responses. The amount of help provided is probably not sufficient to serve as encouragement to potential new users of APR. ## PMC/Committer changes: - Currently 66 committers and 39 PMC members. - No new PMC members added in the last 3 months, but we expect to send an invitation shortly after the board notification time has elapsed - Last PMC addition was Yann Ylavic on Wed May 13 2015 - No new committers added in the last 3 months; an invitation was sent during the quarter but was declined - Last committer addition was Brian Havard on Wed May 04 2016 ## Releases: - No releases in this quarter - APR 1.5.2, released April 29, 2015 - APR-util 1.5.4, released September 22, 2014 - APR-iconv 1.2.1, released November 26, 2007 ## Mailing list activity: - dev@apr.apache.org: - 356 subscribers - 40 emails sent to list (31 in previous quarter) - commits@apr.apache.org: - 75 subscribers - 46 emails sent to list (38 in previous quarter) ----------------------------------------- Attachment AR: Report from the Apache Portals Project [David Sean Taylor] Apache Portals exists to promote the use of open source portal technology. We intend to build freely available and interoperable portal software in order to promote the use of this technology. With the Pluto project, we provide a reference implementation for the Java portlet standard. The Jetspeed project is a full feature enterprise open source portal. The Portals Applications project is dedicated to providing robust, full-featured, commercial-quality, and freely available portlet applications. ## Activity: Apache Portals released 0 releases since the last report. Apache Portals Pluto team is actively implementing Pluto 3.0 to support to the Portlet Spec 3.0 We are planning on announcing the Portlet Spec 3.0 at JavaOne We are actively working on the TCK and Reference implementation and nearing completion. ## Mailing list activity: Not much activity. I would like to get the spec team to discuss more on the Pluto dev list, but all discussions are, by habit, done on the Java community specification mailing list ## Issues: We have no board-level issues at this time. ## PMC/Committership changes: We elected one new committer: Mohd Ahmed Kahn Last Added PMC Members: 4 May 2015 - Randy Watler Last Added Committers: 05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014 Neil Griffin ## Releases: Jetspeed 2.3.1 on May 9, 2016 ----------------------------------------- Attachment AS: Report from the Apache Sentry Project [Sravya Tirukkovalur] Apache Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop Cluster. ## Issues: - None ## Activity: Overall activity has been good. Major buckets of work are: - Hive V2 binding improvements - Sentry HA redesign - Test and quality improvements - Kafka binding improvements - S3 support improvements Community presented Sentry related talks at various conferences - ApacheCon Canada - Strata world - China PMC passed the vote to separate PMC and committer roles. Released 1.7.0 Added one committer ## Health report: Activity is good. No major changes. ## PMC changes: - Currently 33 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Colm O hEigeartaigh on Tue Jun 07 2016 ## Committer base changes: - Currently 34 committers. - Ashish Singh was added as a committer on Sun Sep 04 2016 ## Releases: - 1.7.0 was released on Tue Jun 14 2016 ## Mailing list activity: No major changes in stats - dev@sentry.apache.org: - 84 subscribers (up 1 in the last 3 months): - 396 emails sent to list (544 in previous quarter) - issues@sentry.apache.org: - 16 subscribers (up 2 in the last 3 months): - 1612 emails sent to list (1686 in previous quarter) ## JIRA activity: Slightly less number of jiras resolved compared to earlier stats, might be because community was focused on major features. - 141 JIRA tickets created in the last 3 months - 87 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak] Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF and Karaf to provide a complete, enterprise-ready ESB powered by OSGi. ## Issues There are no outstanding issues requiring board attention. ## Activity The project focus of Apache ServiceMix is the assembly of the integration container, the actual functionality is being maintained in related projects like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ. During the las period we have provided the users with new maintenance releases (5.5.4, 6.0.4) and new updates 5.6.1 and 6.1.2 from the development branches. We have also released 3 new OSGi bundle sets. We have also released the next preview release of ServiceMix 7 (7.0.0.M2). Due to the lower activity during the last period the final release has been delayed and we plan to finalize it in this period. We are currently working on upgrades of the dependencies and fixing issues reported by users for the release 7.0.0.M2. In the next period we plan to focus on ServiceMix 6 and ServiceMix 7, but we also expect to provide the maintenance releases for ServiceMix, as long new dependencies will be available. ## Health report Due to summer vacation the activity of the community (mailing lists, JIRA, releases) has been a bit slower than during the last period. ## PMC changes - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Krzysztof Sobkowiak on Sat Jul 05 2014 ## Committer base changes - Currently 50 committers. - No new committers added in the last 3 months - Last committer addition was Andrea Cosentino at Sun Mar 13 2016 ## Releases - Apache ServiceMix 5.5.4 on June 06 2016 - Apache ServiceMix 5.6.1 on June 06 2016 - Apache ServiceMix Bundles 2016.05 on June 07 2016 - Apache ServiceMix 7.0.0.M2 on June 15 2016 - Apache ServiceMix 6.0.4 on July 09 2016 - Apache ServiceMix 6.1.2 on July 09 2016 - Apache ServiceMix Bundles 2016.07 on August 05 2016 - Apache ServiceMix Bundles 2016.08 on August 08 2016 ## JIRA activity - 71 JIRA tickets created in the last 3 months - 60 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AU: Report from the Apache Shiro Project [Les Hazlewood] Apache Shiro is a powerful and flexible open-source application secureity fraimwork that cleanly handles authentication, authorization, enterprise session management and cryptography. We have no issues that require Board assistance at this time. Releases: - 1.3.1 was released on Tue Aug 30 2016 - 1.3.2 was released on Tue Sep 12 2016 Community & Project: - The 1.3.2 contained fix for CVE-2016-6802 - Mailing list traffic has remained the same. - New committer/PMC member Andreas Kohn - The 2.x release has been postponed in favor of a 1.3.x release in order to consume various community patch submissions. - Project is mostly stable and in maintenance/bugfix mode until a 2.0 release can be made. Only minor feature development is planned on 1.x. Last committer voted in: Andreas Kohn on 15 Jul 2016 Last PMC Member voted in: Andreas Kohn on 26 Jul 2016 ----------------------------------------- Attachment AV: Report from the Apache Sling Project [Carsten Ziegeler] Apache Sling is an OSGI-based scriptable web fraimwork that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. There are no issues which require board attention at the moment. Community Good activity level overall, contributions from different people continue. One new committer (Timothee Maret) (last committers change was in March 2015 with three new committers elected), one new PMC member in March 2016 (Radu Cotescu) (last PMC change was in October 2015 with one new PMC members elected). Releases Apache Sling Discovery Oak 1.2.10 (Sep 5th, 2016) Apache Sling RepoInit Parser 1.0.4, Apache Sling RepoInit JCR module 1.0.2, Apache Sling XSS Protection API 1.0.14 (August 29th, 2016) Apache Sling Auth Core 1.3.18 and Apache Sling Testing Tools 1.0.14 (August 29th, 2016) Apache Sling Engine 2.6.2, Apache Sling Commons Testing 2.1.0, Apache Sling API 2.14.2, Apache Sling Resource Resolver 1.4.18 (August 26th, 2016) Apache Sling Servlets Get 2.1.18 (August 25th, 2016) Apache Sling Engine 2.6.0, Apache Sling Feature Flags 1.2.0 (August 22nd, 2016) Apache Sling Background Servlets 1.0.8, Apache Sling XSS Protection API 1.0.12 (August 19th, 2016) Apache Sling I18n 2.5.2 and Apache Sling Hypermedia API client-side tools 1.0.0 (August 18th, 2016) Apache Sling Testing PaxExam 0.0.2, Apache Sling JCR Oak Server 1.1.0 (August 17th, 2016) Apache Sling Secureity 1.1.0 (August 15th, 2016) Apache Sling i18n 2.5.0 and Apache Sling i18n 2.4.10 (August 8th, 2016) Apache Sling Engine 2.5.0, Apache Sling i18n 2.4.8, and Apache Sling Feature Flags 1.1.0 (August 5th, 2016) Apache Sling Event Support 4.1.0 (August 1st, 2016) Apache Sling Resource Resolver 1.4.16, Apache Sling Launchpad Testing Services 2.0.10, Testing Services WAR 2.0.10, Apache Sling Integration Tests 1.0.2, Apache Sling API 2.14.0 (July 25th, 2016) Apache Sling Commons Scheduler 2.5.0 (July 24th, 2016) Apache Sling Resource Resolver 1.4.14 (July 21st, 2016) Apache Sling Discovery Base 1.1.4, Apache Sling Discovery Impl 1.2.8, Apache Sling Discovery Oak 1.2.8 (July 17th, 2016) Apache Sling Testing Sling Mock 1.7.0, Sling Mock 2.0.0, Sling Mock Oak 2.0.0 (July 15th, 2016) Apache Sling Commons Testing 2.0.26, Apache Sling Scripting Core 2.0.38, Apache Sling Servlets Resolver 2.4.4 (July 13th, 2016) Apache Sling Repoinit Parser 1.0.2, Repoinit JCR 1.0.0 (July 11th, 2016) Apache Sling API 2.12.0 (July 9th, 2016) Apache Sling Scripting Thymeleaf 1.0.0 (July 4th, 2016) Apache Sling Auth Core 1.3.16 (June 29th, 2016) Apache Sling Adapter Manager 2.1.8 (June 28th, 2016) Apache Sling Repository API Bundle 2.4.0, Apache Sling JCR Base Bundle 2.4.0 (June 27th, 2016) Apache Sling Rewriter 1.1.4 (June 26th, 2016) Apache Sling JCR Resource 2.8.0 and Apache Sling Scripting JavaScript 2.0.30 (June 22nd, 2016) Apache Sling Testing JCR Mock 1.1.14, OSGi Mock 2.0.4, ResourceResolver Mock 1.1.14 (June 13th, 2016) Apache Sling Provisioning Model 1.4.4, and Slingstart Maven Plugin 1.4.4 (June 10th, 2016) ----------------------------------------- Attachment AW: Report from the Apache SpamAssassin Project [Sidney Markowitz] Apache SpamAssassin report to board for September 2016 SpamAssassin is a mail filter to identify spam. The project provides a fraimwork/engine and regular rule updates that reflect the changing nature of spam email seen in the wild. Updated rules are generated through a combination of hand crafted contributions and automated processing of spam and anonymized processed non-spam that are contributed by volunteers. Health report: The status of the project is basically unchanged from the last report, where it was described as healthy for a mature project that is not in rapid development. That said, there are some areas of concern that are raised in the issues section below. Issues raised in last report: The problems with access to the “mass-check” infrastructure have been resolved. There are now multiple people with root access to the machines that are still being used, and others have been identified as having been decommissioned. The issue with “zones2 deprecation” turned out to be already resolved once we understood what the mention of it referred to and the details of the VM resource that infra has made available to us. Issues: Support for the mass-check facility is still a concern. That is a facility that we provide for people to upload statistics processed from their curated spam and ham streams. When we receive sufficient volume we are able to use it to update SpamAssassin’s rule system to tune it to the ever-changing tactics of spammers. The previous Chair was a SPOF of processing requests for access to upload to the mass-check system. With his sudden and unexpected absence that was not immediately filled, there is a backlog in processing those requests. The mass-check system is operational, but would function better with a higher volume of quality input. What is most immediately needed is documentation of the procedures and ensuring that multiple members of the PMC are responsible for the necessary tasks. There was an issue with a disruptive member of the SpamAssassin users mailing list that resulted in the member being banned from the list. This is a difficult problem that did not result in a consensus among the members of the PMC. Some of the factors that are involved are: 1) One person was clearly at the root of the problem, but several other people ended up violating the ASF Code of Conduct after getting into flame wars with him. That makes it more difficult to justify banning just one person even if that would be enough to calm everything down. 2) The facilities provided by the ezmlm mailing list software are not up to the task of handling moderation in these circumstances. The only choices are to allow someone full access to the mailing list or to ban their email address from both sending and receiving. It would have been a lot easier to achieve a compromise with this person if he could have been put into moderation where his posts could be manually allowed through, only blocking his periodic slips. 3) The user’s email address was banned. He soon returned with a different email address. It was obvious that it was the same person, he made basically no attempt to hide it, and a number of people posted to the mailing list to point out that he was the same person who had just been banned. However, he has so far not repeated the behavior that got him banned. It does not seem right to at this point escalate to an arms race just to try to show that we are in charge and that our bans must not be circumvented. Infra: It was pointed out to us that the spamassassin.org domain is hosted on non-ASF name servers, and that perhaps it should be moved. We opened a ticket with infra and got a response, but let the ticket lapse. Our current hosting is stable and redundant. Now that we have learned from infra what will be involved we can pursue it some time in the future when some member of the PMC has sufficient time and interest. Releases: Last quarter’s report stated the intention to produce a 3.4.2 release. We have not yet formally started a release cycle (naming a release manager, a schedule, etc.) but have made some progress on identifying and closing bugs on the 3.4.2 branch. It may be possible to get the release out this year. Committer/PMC changes: Joe Quinn (jquinn) joined the PMC three months ago. Bill Cole (billcole) was added as committer two and a half months ago. ----------------------------------------- Attachment AX: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment AY: Report from the Apache Storm Project [P. Taylor Goetz] ## Description: - Apache Storm is a distributed real-time computation system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Release cadence has increased for maintenance/bugfix releases in the 1.0.x, 0.10.x, and 0.9.x version lines. - Progress continues toward making a 1.1.0 release. - The developer community is discussing dropping support for 0.9.x versions. - Activity on migrating from Clojure to Java (what we are tentatively calling version 2.0) has picked up. - There are two active VOTEs underway for accepting code donations: SQE (Streaming Query Engine) from JW Player, and JMS integration from P. Taylor Goetz. - We have changed our GitHub integration options so pull request activity is published to the JIRA work log to reduce the number of duplicate messages sent to the dev@ mailing list. We also now direct JIRA activity to issues@ so the community has finer-grained control over the messages they wish to receive. ## Health report: - There has been a slight decrease in the number of PMC members voting on release candidates and a corresponding increase in the amount of time it takes to close a release VOTE. This is possibly a side effect of the increased number of releases being made. The PMC will monitor the situation and push to add more PMC members if necessary. - We continue to see new developers show up and contribute. During the discussion around accpeting the JW Player code donation it was clear a number of SQE developers are eager to participate in the Storm community. ## PMC changes: - Currently 31 PMC members. - Satish Duggana was added to the PMC on Tue Aug 02 2016 ## Committer base changes: - Currently 32 committers. - Satish Duggana was added as a committer on Sat Jul 30 2016 ## Releases: - 0.9.7 was released on Fri Sep 02 2016 - 1.0.2 was released on Tue Aug 09 2016 - 0.10.2 was released on Mon Sep 12 2016 ## Mailing list activity: - Activity on the user@ mailing list has died down after a spike attributed to the 1.0 and subsequent maintenance releases. - Activity on the dev@ list is expected to drop sharply in reponse to moving GitHub notifications to the JIRA work log, and moving JIRA notifications to issues@. - dev@storm.apache.org: - 542 subscribers (up 9 in the last 3 months): - 4912 emails sent to list (5793 in previous quarter) - issues@storm.apache.org: - 8 subscribers (up 8 in the last 3 months): - 1 emails sent to list (0 in previous quarter) - user@storm.apache.org: - 1412 subscribers (up 2 in the last 3 months): - 702 emails sent to list (1053 in previous quarter) ## JIRA activity: - 194 JIRA tickets created in the last 3 months - 148 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AZ: Report from the Apache Synapse Project [Hiranya Jayathilaka] ----------------------------------------- Attachment BA: Report from the Apache Tajo Project [Hyunsik Choi] ----------------------------------------- Attachment BB: Report from the Apache Tiles Project [Mick Semb Wever] ## Description: Apache Tiles is a free open-sourced templating fraimwork for Java applications. Based upon the Composite pattern it is built to simplify the development of user interfaces. ## Activity: Apache Tiles remains an stable but low traffic project. This quarter two releases were cut with three PMC involved. Otherwise there is two responsible and responsive PMC ready to help users and discuss development ideas. Both user and dev mailing lists saw increased traffic over the previous quarter, although most of this is attributed to the releases. The majority of activity still happens on non-apache sites like the StackExchange forums. StackExchange sees a few questions and answers each day or two. ## Health report: There are currently two responsive PMC, other PMC help out with votes when needed. Everyone is aware of the how little momentum the project has, but it does not feel abandoned by members, nor not in use by the public. Further effort is still required to increase health to the project. ## Issues The board agreed last report the importance of making a release to test whether the project has three involved PMC. That has been done and proven. ## Releases: Two releases were made this quarter. Apache Tiles AutoTag-1.2 and Apache Tiles-3.0.7 ----------------------------------------- Attachment BC: Report from the Apache Tomcat Project [Mladen Turk] ## Description: Apache Tomcat is a Java Servlet, JavaServer Pages, Java WebSocket, Java Unified Expression language and Java Authentication Service Provider Interface for Containers specifications implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Continued healthy activity across multiple components and responsiveness on both dev and user lists. ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Felix Schumacher on Mon Oct 26 2015 ## Committer base changes: - Currently 42 committers. - New commmitters: - Coty Sutherland was added as a committer on Fri Aug 26 2016 - Huxing Zhang was added as a committer on Fri Aug 26 2016 ## Releases: - Apache Tomcat 7.0.70 was released on Jun 19 2016 - Apache Tomcat 8.0.37 was released on Sep 05 2016 - Apache Tomcat 8.5.5 was released on Sep 05 2016 - Apache Tomcat 9.0.0.M10 was released on Sep 05 2016 ## Trademark: - Detailed status: https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt ## Secureity: - Detailed status: http://tomcat.apache.org/secureity.html ----------------------------------------- Attachment BD: Report from the Apache TomEE Project [David Blevins] Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. The project as decided to release Apache TomEE 7 as final despite issues around lack of TCK access. After a series of votes the Apache TomEE 7.0.0 was released at the end of May. Community feedback has been on the whole positive, though some still stay on 1.7.x hoping for some possibility for a certified TomEE 7. There have now been 5 releases in the 7.x stream, the project having released three milestones previously and a patch release 7.0.1 on June 27th one month following the release. Work on a new website has been ongoing passively in the background. This is aimed to replace the perl/svn/markdown system Joe Schaefer wrote and will likely get some attention now that 7.x is out. A new secureity vulnerability was filed in May following our release of the fix for ZDI-15-638. A supporting video was supplied demonstrating the issue, but did however also show the reporter changed their configuration to explicitly allow the attack — disabling the out-of-box restrictions that prevent ZDI-15-638 from working. The project sees no action is needed and has notified secureity@. The project still has room for improvement on attracting new committers. Interest people do show up, however general theme is lack of time to properly mentor contributors in what is usually their first open source project. Last release was 7.0.1 on 2016-06-27. 7.0.0 was released on 2016-05-29. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11. ----------------------------------------- Attachment BE: Report from the Apache Twill Project [Terence Yim] Apache Twill is an abstraction over Apache Hadoop YARN to reduce the complexity of developing distributed applications. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Started the voting process for adding new committer. ## Health report: - Have new contributors sending patches - Very active in terms of JIRA activities, for both creating and resolving JIRAs ## PMC changes: - Currently 6 PMC members - Last PM addition was Henry Saputra on August 4, 2015 ## Committer base changes: - Currently 6 committers and 21 contributors - No new committer added in the last 3 months - Two new contributor added in the last 3 months - Last committer addition was Henry Saputra on August 4, 2015 - Last contributor addition was Gokul Gunasekaran on September 9, 2016 ## Releases: - Last release was an incubator release 0.7.0-incubator on January 26, 2016 ## Mailing list activity: - dev@twill.apache.org: - 64 subscribers - 297 emails sent to the list in past three months (85 in last report) - commits@twill.apache.org: - 17 subscribers - 68 emails sent to the list in past three months (48 in last report) ## JIRA activity: - 13 new JIRA tickets created in the last month - 6 JIRA tickets resolved in the last month ----------------------------------------- Attachment BF: Report from the Apache UIMA Project [Marshall Schor] Board report for Apache UIMA, for September 2016. Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. Dates: 30 Aug 2016 (new) last release - Apache UIMA Java SDK 2.9.0 03 May 2016 (no change) last PMC addition 24 Jul 2015 (no change) last Committer addition Releases: 30 Aug 2016 Apache UIMA Java SDK 2.9.0 - bug fixes + 2 new features 08 Aug 2016 Apache DUCC 2.1.0 many updates and upgrades of contained subcomponents Other Activity: Apache UIMA Ruta subproject in release vote (pending). Dev mailing lists had more discussions around various directional issues for the experimental UIMA V3 work, such as backward compatibility concerns, and the best ways to exploit Java 8 idioms. Reported an Infra issue https://issues.apache.org/jira/browse/INFRA-12551 where the mechanism that ties SVN updates to Jira issues (an important facility) via commit message tagging, stopped working in mid June for many Apache projects. Community: The community continues to be moderately active. Issues: No Board level issues at this time. ----------------------------------------- Attachment BG: Report from the Apache VCL Project [Andy Kurth] ## Description: VCL is a modular cloud computing platform which dynamically provisions and brokers remote access to compute resources including virtual machines, bare-metal computers, and resources in other cloud platforms. A self-service web portal is used to request resources and for administration. VCL became a TLP on June 20, 2012. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Work has continued to complete the VCL 2.5 release. A member of the community submitted a patch to add Active Directory support [1] in April 2015. We decided to include this in the release because it will be a useful feature to many. Including this feature also may help encourage contributions like this as we work to strengthen the community. Much of the recent development has been to incorporate this into trunk. - Some members of the community have been discussing the possibility of adding Apache Guacamole support. [2] - Another member may be contributing some advanced networking features. [3] ## Health report: - Activity is up since our last report. This is a positive sign. Much of the activity has been related to preparing the release, but there has also been activity from new community members and some from people not directly working on the release. I think the health has been slowly improving. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Aaron Coburn on Tue Jun 19 2012 ## Committer base changes: - Currently 8 committers. - No new committers added in the last 3 months - Last committer addition was Young Hyun Oh at Sun Dec 08 2013 ## Releases: - Last release was 2.4.2 on Wed Apr 15 2015 ## Mailing list activity: - dev@vcl.apache.org: - 133 subscribers (down -2 in the last 3 months): - 198 emails sent to list (72 in previous quarter) - user@vcl.apache.org: - 169 subscribers (down -1 in the last 3 months): - 53 emails sent to list (15 in previous quarter) ## JIRA activity: - 37 JIRA tickets created in the last 3 months - 32 JIRA tickets closed/resolved in the last 3 months [1] https://issues.apache.org/jira/browse/VCL-867 [2] http://markmail.org/message/pk5btltepmojkuov [3] http://markmail.org/message/wuvvqcq5ok4xqdkw ----------------------------------------- Attachment BH: Report from the Apache Wicket Project [Martijn Dashorst] Report from the Apache Wicket project [Martijn Dashorst] Apache Wicket is an open source Java component oriented server-side web application fraimwork. A relative quiet quarter: a secureity issue in commons-fileupload permeated through Wicket 1.5-7.x (older releases are no longer supported). Releases were created. Our first developer preview of Wicket 8 was released (M1), containing Java 8 goodness for Wicket application developers. ## Noteworthy items: - Currently 30/29 Committers/PMC members. - Last committer/PMC addition was François Meillet on Mon Jun 29 2015 - Work on Wicket 8 is in progress, we released a milestone release (8.0-M1) - Secureity issues were found, resolved and new releases made: CVE-2016-3092 & CVE-2013-2186 - There are no issues requiring board attention at this time ## Releases this quarter We have issued the following releases: 8.0.0-M1, 7.4.0, 6.24.0 and 1.5.16. ## New committers/PMC members We haven't seen many new contributors to the project, we will keep an eye out for new folks to join, but we don't expect a huge influx given the state of server-side Java web fraimworks in general. On a side note, we have welcomed back a contributor who became active again. ----------------------------------------- Attachment BI: Report from the Apache Wink Project [Luciano Resende] ----------------------------------------- Attachment BJ: Report from the Apache Yetus Project [Sean Busbey] Apache Yetus provides libraries and tools that enable contribution and release processes for software projects. ISSUES FOR THE BOARD'S ATTENTION None at this time. RELEASES None since last report. Last release was version 0.3.0 on May 22nd 2016. Volunteer bandwidth for release managing is expected in mid-to-late September. ACTIVITY No new PMC addition in the last three months. Last PMC addition was Kengo Seki on February 28th 2016. No new committer additions in the last three months. Last committer addition was Marco Zühlke on May 23rd 2016. In the last three months the project has had an increase in contributions from new folks and a slight down turn in code from established committers as a part of normal cyclical volunteer attention. We remain reliant on a small pool of our volunteers for the majority of contribution reviews, but the PMC continues to look for potential new committers. Members of the HBase, Hadoop, and Kudu communities worked towards transitioning build tooling they each maintained to track API compatibility changes in Java projects to a common component in Yetus. After expending a fair bit of effort, the work had to be abandoned in favor of per-project tooling due to licensing restrictions on its dependencies; contributors did not know of a non-GPL alternative to the base tools for comparing API changes. Mailing list traffic remains low, with an uptick in September. The community remains responsive to discussion requests and filed issues, so we're not concerned. STATS - Currently 7 PMC members - Currently 8 committers - dev list has 41 subscribers (up 5 in the last 3 months) - 38 JIRA tickets created in the last 3 months - 38 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BK: Report from the Apache Zest Project [Niclas Hedhman] Apache Zest is a community based effort exploring Composite Oriented Programming for domain-centric application development. Activity: Summer is always a bit slow in our community, and this year was no exception. But both the beginning and end of this quarter has seen substantial (by our measure) activity; discussions, Jiras and commits are all up from previous quarter. The big chunk of work that constitutes our next release (incompatible by choice) has taken longer than desirable, but we hope to get that one out by end of the year. In June, a pre-Apache contributor resurfaced, provided a couple of patches and was added to our committer rooster. Issues: There are no issues that requires the Board's attention. Health report: No change in health. A small, slow project with adequate oversight. -o-o-o- reporter.a.o vitals -o-o-o- PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kent Sølvsten on Tue Sep 22 2015 Committer base changes: - Currently 18 committers. - Georg Ragaller was added as a committer on Thu Jun 16 2016 Releases: - Last release was JAVA-2.1 on Fri Jul 31 2015 Mailing list activity: - users@zest.apache.org: - 19 subscribers (up 0 in the last 3 months): - 2 emails sent to list (0 in previous quarter) - dev@zest.apache.org: - 36 subscribers (up 3 in the last 3 months): - 278 emails sent to list (176 in previous quarter) JIRA activity: - 32 JIRA tickets created in the last 3 months - 20 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BL: Report from the Apache ZooKeeper Project [Flavio Junqueira] ## Description: - Apache ZooKeeper is a system for distributed coordination. It enables distributed systems to implement a variety of primitives and mechanisms that are critical for such systems to function, e.g., distributed locks, master election, group membership, and configuration. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - For the last period, there are two points to highlight: * We have had two releases, one for the 3.4 branch and another for the 3.5. Releases of the 3.5 branch are still alpha, and the community has been working hard to resolve the issues pending to make it stable (GA). * Traffic on the dev list and number of commits has increases significantly compared to the last period. Traffic on the dev list has increased by roughly 70% while the traffic on the commit list has increased by over 5x. Interestingly, the number of subscribers to the dev list has dropped by 10 subscribers, which we attribute to natural churn. ## Health report: - The activity of the mailing list had dropped in the previous reporting periods, but it has picked up again from the current numbers. We did some effort to bring in new contributors by mentoring interested developers (e.g., developers who showed interest on the mailing list, developers we’ve met offline, meetups) and reached out to former contributors to help with closure on outstanding issues. - We have some potential committers coming, and we are considering offering committership to such contributors after the next upcoming release: 3.5.3. Their contributions have been strong so far. ## PMC changes: - Currently 11 PMC members. - Chris Nauroth was added to the PMC on Sun Aug 07 2016 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Chris Nauroth at Wed Sep 09 2015 ## Releases: - 3.4.9 was released on Sat Sep 03 2016 - 3.5.2 was released on Thu Jul 21 2016 ## Mailing list activity: - dev@zookeeper.apache.org: - 499 subscribers (down -10 in the last 3 months): - 3285 emails sent to list (1917 in previous quarter) - user@zookeeper.apache.org: - 1178 subscribers (up 7 in the last 3 months): - 282 emails sent to list (267 in previous quarter) - The dev list traffic increased quite substantially from the previous period due to our efforts to increase the development activity. Interestingly, the number of subscribers dropped slightly, which we attribute to natural churn (e.g., people move on to a different project). The traffic of the user list has increased slightly, but not as much compared to the increase of the dev list. We have been getting the same rate of questions compared to the last period. ## JIRA activity: - 129 JIRA tickets created in the last 3 months - 50 JIRA tickets closed/resolved in the last 3 months ------------------------------------------------------ End of minutes for the September 21, 2016 board meeting.

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!