The Apache Software Foundation Board of Directors Meeting Minutes December 17, 2014 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:33 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: http://timeanddate.com/s/2rt6 The meeting was held via teleconference, hosted by Doug Cutting and Cloudera. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Rich Bowen Doug Cutting Bertrand Delacretaz Ross Gardler Jim Jagielski Chris Mattmann Brett Porter Sam Ruby Greg Stein Directors Absent: none Executive Officers Present: Craig L Russell Executive Officers Absent: none Guests: Jake Farrell Daniel Gruno Sean Kelly Shane Curcuru Hadrian Zbarcea David Nalley Henri Yandell Tom Pappas (Virtual) Marvin Humphrey 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of November 19, 2014 See: board_minutes_2014_11_19.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Brett] Nothing specific to report this month. B. President [Ross] A very busy month, on many fronts. Apologies for the late filing. I'm trying to catch up. Here's the High and Low lights. EA has been chugging along ensuring we keep things moving. In her report Melissa indicates getting the Credit Cards has proven problematic. This morning I have had notification from her that Tom (Virtual) has indicated we should expect the cards in 7-10 days. TAC is wrapping up the EU activities and ramping up on the US activities. All is well. Trademarks has been busy evaluating the need to protect the ApacheCon conference from conflicting events organized by third parties. After some long (and often repetitive) debates an agreeable solution was found. Shane has now encoded the details in our event policy. However, I note the whole exercise will be have been pointless if we don't actually enforce it Relating to this the lack of any clarity around what a "blackout date" period is could cause problems should we ever wish to enforce those blackouts. While there is a little more clarity the current policy and MOU is still unclear. The trademark report also indicates there is a new trademark request relating to a training certification program. I am unaware of the details but note that Shane invites input on the trademarks list (and draw attention to the phrase "charging fees" in this context). Upayavira has finally hung up his hat over at Fundraising (though he's still helping with the transition). Jim and Hadrian have been in office for a month and the renewed (and doubled) energy is bearing fruit. See below for a little more on fundraising. Marketing has completed the usual activities (see report). In addition Sally is putting together the initial quarterly report. The first version of which will be retroactive in nature, but see below for further discussion. Sally is also working with Hadrian to send out "thank you" messages during the holiday season. Finally, I have asked Sally to work with me in crafting media campaign focusing on the ASF as a place for "Innovation and Collaboration" this will run prior to ApacheCon US and will be crafted to focus on a track I am chairing at the event. Note, this will not be an ApacheCon marketing campaign, it is an Apache Software Foundation campaign but will be designed to both ride-on and add-to the ApacheCon wave. It is early days (with only a handful of email exchanges at this point) so early feedback is on the high level messaging is welcome. Infrastructure, oh Infrastructure. Last month I took great pleasure in reporting that the team had had lots of opportunity to pay off significant technical debt. Not so this month (although progress is still being made). I want to recognize that the infrastructure team responded extremely well to three significant outages. Whilst it would be good to have no outages (see technical debt) it is pleasing to see the team increasingly working as a team in the face of these outages. Full details of the outages are in the infra report all that we need here is for me to thank the team for "going the extra mile" to minimize impact on our projects. Greg has made some progress on the "contractors vs employees" solution, though as I understand it he has nothing significant to report at this point. I'll leave any fuller report to Greg. Lastly, as previously reported, VP Infra is keen to have a longer term view of where the ASF is heading so that he can make appropriate planning decisions. EVP arranged a two hour meeting involving VP Infra, VPs Fundraising, EVP, myself and the Chair in order to have an initial discussion about this. This was largely a brainstorming meeting. We focused mostly on how to properly plan for the consistent growth the ASF has been seen for a number of years (1.5 new projects per month with increasingly varied infra requirements) and how to ensure fundraising can provide income to support those plans. There were also some discussions about how to manage community growth and health across ASF projects, however given that those in the meeting were wearing their Presidents Committee hats these topics were not discussed in detail. Extensive notes were taken and will be shared in the raw form upon request. However, I would suggest that what is really important at this point is the immediate action items. The most important at this time (from a board perspective) is a suggestion to implement the budget planning adjustment suggested by some directors last year. That is to move out the budget planning so that our budget cycle falls six months after the board elections. If the board are agreeable this will mean that the next budget for approval (May 1st) will be for eighteen months with the incoming board reviewing and potentially revising after the first six months. Subsequent budget cycles will be 12 months and will be set in the middle of the board term. I invite early feedback on this suggestion. If implemented this means the budget planning cycle will be: - Jan 2015 - Categorization of Infra services according to level of importance to our projects - Feb 2015 - Call to all committees for budget requests - March 2015 - Draft budget for board feedback - April 2015 - Approval of budget by the board - September 2015 - Revision of budget if necessary In parallel to this I propose to deliver, in partnership with VP Infra and VPs Fundraising a longer term (5 years), though less detailed, plan. The goal here will be to provide VP Infra with enough clarity to prioritize effectively whilst also giving the board an opportunity to review regularly. I propose that this longer term plan be approved alongside the budget as outlined above. I invite the board to provide initial feedback during the meeting but intend to raise this on the board@ mailing list shortly after the meeting. Additionally, please see Attachments 1 through 6. Shane: We need the concept of "blackout dates" in the contracts even without being explicit. Still in process. C. Treasurer [Chris] The Treasurer’s office continues to work with Virtual to get the corporate credit cards up and running. A few more forms needed to be filled out and signed and we are awaiting the cards from Citizen’s Bank at this point. Chris and Tom Pappas from Virtual had a call to go over some outstanding loose ends and information to get the 990 process shored up. We are on track to get it filed on time with Virtual and the CPA. The President also assisted in this process by signing the engagement forms for the 990 to be completed by the CPA and Virtual. Income and Expenses for November 2014 CASH BASIS Current Balances: Citizens Checking $195,676 Amazon- ASF Payments $16,359 Paypal - ASF $40,976 Wells Fargo Checking - ASF $907,279 Wells Fargo Savings $288,103 Total Checking/Savings $1,448,392 Income Summary: Public Donations $2,160 Amazon and Paypal Sponsorship Program $80,000 Interest Income $24 Total Income $82,183 Expense Summary: Infrastructure $29,200 Sponsorship Program $- Programs Expense $- Publicity $13,137 Brand Management $279 Conferences $- Travel Assistance Committee $- Treasury Services $2,850 General & Administrative $10,221 Total Expense $55,688 Net Income $26,495 D. Secretary [Craig] The errors in the computer program that prepares incoming documents for processing by the secretary continued to impact timely receipt and acknowledgement of documents. The problem appears to have been resolved. In November, 85 iclas, 11 cclas, and four grants were received and acknowledged. E. Executive Vice President [Rich] We are in the ramp-up phase for ApacheCon North America, and I'm trying to gather a group of track chairs to shepherd content based on topic rather than specific project, as this makes it a lot easier to get people to attend. We are also trying to identify possible keynote speakers. Brian Behlendorf has confirmed that he will be keynoting. I'm also trying to contact as many of the early httpd crowd as possible to come celebrate httpd's 20th birthday. Brian is being very helpful with this. There has been discussion (as you will see in other reports) on the Trademarks list about event MOUs and blackout windows, and, for my part, I've been working with LF to encourage earlier planning, so that the blackout window becomes less of a big deal. Specifically, we're going to do our best to announce 2016 locations and dates at ApacheCon Austin. I don't yet know if this is actually feasible. F. Vice Chairman [Greg] I have started work on the contractor issue, but have nothing to report at this time. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Chris] See Attachment 7 B. Apache Legal Affairs Committee [Jim Jagielski] See Attachment 8 C. Apache Security Team Project [Mark Cox / Rich] See Attachment 9 Additional officer reports approved as submitted by General Consent. 6. Committee Reports A. Apache Abdera Project [Ant Elder / Greg] No report was submitted. B. Apache Allura Project [Dave Brondsema / Jim] See Attachment B C. Apache Ant Project [Conor MacNeill / Bertrand] No report was submitted. D. Apache Any23 Project [Lewis John McGibbney / Ross] See Attachment D E. Apache APR Project [Jeff Trawick / Doug] See Attachment E F. Apache Archiva Project [Olivier Lamy / Sam] See Attachment F G. Apache Axis Project [Deepal Jayasinghe / Brett] No report was submitted. @Brett: pursue a report for Axis H. Apache Bigtop Project [Konstantin Boudnik / Brett] See Attachment H I. Apache Bloodhound Project [Gary Martin / Chris] See Attachment I J. Apache BookKeeper Project [Ivan Kelly / Greg] See Attachment J K. Apache BVal Project [Matt Benson / Sam] See Attachment K L. Apache Camel Project [Christian Mueller / Rich] See Attachment L M. Apache Cayenne Project [Andrus Adamchik / Ross] See Attachment M N. Apache Chemistry Project [Florian Müller / Bertrand] See Attachment N O. Apache CloudStack Project [Hugo Trippaers / Doug] See Attachment O P. Apache Commons Project [Gary Gregory / Jim] See Attachment P Q. Apache Cordova Project [Shazron Abdullah / Chris] See Attachment Q R. Apache cTAKES Project [Pei J Chen / Greg] See Attachment R S. Apache Curator Project [Jordan Zimmerman / Rich] No report was submitted. T. Apache DeviceMap Project [Reza Naghibi / Ross] See Attachment T U. Apache DirectMemory Project [Raffaele P. Guidi / Sam] See Attachment U @Sam: Follow up with a more complete report next month V. Apache Drill Project [Jacques Nadeau / Bertrand] See Attachment V W. Apache Felix Project [Carsten Ziegeler / Brett] See Attachment W X. Apache Flex Project [Alex Harui / Jim] See Attachment X Y. Apache Giraph Project [Avery Ching / Doug] See Attachment Y Z. Apache Gump Project [Stefan Bodewig / Brett] See Attachment Z AA. Apache Helix Project [Kishore Gopalakrishna / Rich] See Attachment AA AB. Apache Hive Project [Carl Steinbach / Jim] See Attachment AB AC. Apache Incubator Project [Roman Shaposhnik / Chris] See Attachment AC A number of podlings have mentors who appear not to be actively monitoring. There are many podlings whose mentors have not signed off on their reports. @Rich: Discuss these concerns with Incubator chair AD. Apache Jackrabbit Project [Michael Dürig / Doug] See Attachment AD AE. Apache Karaf Project [Jean-Baptiste Onofré / Sam] See Attachment AE AF. Apache Labs Project [Tim Williams / Greg] No report was submitted. AG. Apache Lucene Project [Mark Miller / Ross] See Attachment AG AH. Apache Lucene.Net Project [Prescott Nasser / Bertrand] See Attachment AH @Ross: Discuss with comdev how to get projects to engage with them more AI. Apache MetaModel Project [Kasper Sørensen / Sam] See Attachment AI AJ. Apache MRUnit Project [Brock Noland / Greg] No report was submitted. @Greg: pursue a report for MRUnit AK. Apache OFBiz Project [Jacopo Cappellato / Jim] See Attachment AK AL. Apache Olingo Project [Christian Amend / Rich] See Attachment AL AM. Apache OODT Project [Sean Kelly / Ross] See Attachment AM @Ross: Bring statistics in line with reporting period AN. Apache OpenJPA Project [Pinaki Poddar / Brett] See Attachment AN AO. Apache OpenNLP Project [Joern Kottmann / Chris] See Attachment AO @Chris: Discuss leaving out individual names from reports AP. Apache OpenWebBeans Project [Mark Struberg / Doug] See Attachment AP AQ. Apache Perl Project [Philippe M. Chiasson / Bertrand] See Attachment AQ AR. Apache Pig Project [Cheolsoo Park / Sam] See Attachment AR AS. Apache Pivot Project [Roger Whitcomb / Ross] See Attachment AS AT. Apache POI Project [Yegor Kozlov / Brett] See Attachment AT AU. Apache Portals Project [David Sean Taylor / Jim] See Attachment AU AV. Apache ServiceMix Project [Gert Vanthienen / Greg] See Attachment AV AW. Apache Shiro Project [Les Hazlewood / Bertrand] See Attachment AW AX. Apache Sling Project [Carsten Ziegeler / Chris] See Attachment AX AY. Apache SpamAssassin Project [Kevin A. McGrail / Rich] See Attachment AY AZ. Apache Stanbol Project [Fabian Christ / Doug] See Attachment AZ BA. Apache Storm Project [P. Taylor Goetz / Brett] See Attachment BA BB. Apache Synapse Project [Hiranya Jayathilaka / Doug] See Attachment BB @Brett: Discuss how to work with Axis to make a release BC. Apache Tajo Project [Hyunsik Choi / Jim] See Attachment BC BD. Apache Tiles Project [Greg Reddin / Sam] No report was submitted. BE. Apache Tomcat Project [Mladen Turk / Greg] No report was submitted. BF. Apache Tuscany Project [Jean-Sebastien Delfino / Rich] No report was submitted. BG. Apache UIMA Project [Marshall Schor / Ross] See Attachment BG BH. Apache VCL Project [Andy Kurth / Bertrand] See Attachment BH BI. Apache Whirr Project [Andrew Bayer / Chris] No report was submitted. BJ. Apache Wicket Project [Martijn Dashorst / Ross] See Attachment BJ @Ross: Discuss the "fork me" banner issue with the project after discussion with members BK. Apache Wink Project [Luciano Resende / Jim] No report was submitted. @Jim: pursue a report for Wink BL. Apache ZooKeeper Project [Flavio Junqueira / Chris] See Attachment BL Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache Falcon Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a Big Data management platform covering data pipelines, data motion, data lifecycle management, data discovery & governance. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Falcon Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Falcon Project be and hereby is responsible for the creation and maintenance of software related to a Big Data management platform covering data pipelines, data motion, data lifecycle management, data discovery & governance; and be it further RESOLVED, that the office of "Vice President, Apache Falcon" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Falcon Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Falcon Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Falcon Project: * Amareshwari Sriramadasu * Arpit Gupta * Jean-Baptiste Onofre * Raghav Kumar Gautam * Rishu Mehrotra * Ruslan Ostafiychuk * Samarth Gupta * Sanjay Radia * Shaik Idris * Sharad Agarwal * Shwetha GS * Srikanth Sundarrajan * Suhas Vasu * Venkatesh Seetharam NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be appointed to the office of Vice President, Apache Falcon, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Falcon PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Falcon Project; and be it further RESOLVED, that the Apache Falcon Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Falcon podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Falcon podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7A, Establish the Apache Falcon Project, was approved by Unanimous Vote of the directors present. B. Establish the Apache Flink Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to fast and reliable large-scale data analysis with focus on programmability, optimizability, efficiency, and combination of batch and streaming data processing. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Flink Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Flink Project be and hereby is responsible for the creation and maintenance of software related to fast and reliable large-scale data analysis with focus on programmability, optimizability, efficiency, and combination of batch and streaming data processing; and be it further RESOLVED, that the office of "Vice President, Apache Flink" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Flink Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Flink Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Flink Project: * Márton Balassi * Ufuk Celebi * Stephan Ewen * Gyula Fora * Alan Gates * Fabian Hueske * Vasiliki Kalavri * Aljoscha Krettek * Robert Metzger * Till Rohrmann * Henry Saputra * Sebastian Schelter * Kostas Tzoumas * Timo Walther * Daniel Warneke NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Ewen be appointed to the office of Vice President, Apache Flink, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Flink PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Flink Project; and be it further RESOLVED, that the Apache Flink Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Flink podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Flink podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7B, Establish the Apache Flink Project , was approved by Unanimous Vote of the directors present. C. Change the Apache Nutch Project Chair WHEREAS, the Board of Directors heretofore appointed Julien Nioche to the office of Vice President, Apache Nutch, and WHEREAS, the Board of Directors is in receipt of the resignation of Julien Nioche from the office of Vice President, Apache Nutch, and WHEREAS, the Project Management Committee of the Apache Nutch project has chosen by vote to recommend Sebastian Nagel as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Julien Nioche is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Nutch, and BE IT FURTHER RESOLVED, that Sebastian Nagel be and hereby is appointed to the office of Vice President, Apache Nutch, 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 Nutch Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * Brett: Remind PMCs to report on dates Status: still to reach out based on updated guidelines * Greg: Any info about the community? [ ACE ] Status: * Chris: The report identifies a problem with no resolution... [ Deltacloud ] Status: * Chris: Please clarify what "voted on" means [ James ] Status: * Chris: Is PMC member discussion still ongoing? [ JMeter ] Status: * Chris: Clarify volunteer comment. [ Tcl ] Status: * Jim: send message to all PMCs re: health of projects, new committers, new PMC members Status: Ready to go out. * Rich: work with PMC to help resolve conflicts [ Flex ] Status: * Chris: does the project have enough committers to make releases? [ BVal ] Status: * Greg: the report states a problem but no plan to address it [ Deltacloud ] Status: * Sam: follow up with PMC for clarification on the relationship between the addons and the project [ Isis ] Status: * Greg: find out if TCK is holding up progress [ MyFaces ] Status: * Chris: need more detail in the report; seems like a cut/paste from previous reports [ OpenJPA ] Status: * Sam: pursue a report for Abdera Status: * Chris: pursue a report for DirectMemory Status: * Chris: Summarize comments and follow on the dev list. [ Lenya ] Status: * Bertrand: follow up on the WeNeedYou page issues. [ OpenMeetings ] Status: done - the http://openmeetings.apache.org/WeNeedYou.html page was gone before I contacted the PMC, removed in http://svn.apache.org/viewvc?view=revision&revision=1642041 * Jim: pursue a report for Perl Status: * Rich: Ping them to make sure they've got enough people active. [ Velocity ] Status: * Rich: pursue a report for Giraph Status: * Doug: pursue a report for Tuscany Status: I sent them a note last month but heard nothing back. Rich sent them another note yesterday. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 11:34 a.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] Daily monitoring of all email activity (ea@, fundraising@, trademarks@, treasurer@, comdev@, tm-registrations@, and board@) and following-up with appropriate personnel Fundraising/Virtual: • Work still continues with Virtual re credit cards. Citizens requested additional paperwork/ID from Chris two weeks ago, which was provided. Virtual is doing their part – Citizens needs to step up and get the cards issued! • Spoke with Tom and Lynsey on 12.11 re the cc situation. Tom will be on the board call and will answer any questions. • The credit card situation has gone on WAY TOO LONG, and we need a resolution – we need credit cards in hand. No more excuses, let’s get it done. • As of this writing, the sponsorship payments received since the last Board Report are: $20k WANdisco (re-instated sponsorship); $50k Comcast; and $10k Cerner – final installment (upgraded from Bronze and paid six months early!). • CRM for Fundraising – should have a proposal within a week from Hot Wax Media with their recommendation (they’ve been busy with traveling to/from India, Thanksgiving, etc.). • Fundraising up-to-date at the moment; Jim and Hadrian transitioning into their roles like pros! ApacheCon Europe: • TAC: Final hotel bill (436,48 EUR) received on 12.2 – sent to Accounting for payment • ACEU was a huge success – thanks to Rich for all of his hard work!! As always, I had a lot of traffic at the booth! Everyone that I spoke with thoroughly enjoyed the conference and the giveaways! ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] Updated large scale event MOU with feedback from counsel and many trademark perspectives. Renewed existing Hadoop-related MOU with updated terms. Updated the event policy with clarifications for blackout dates and trademark attributions. A third party is requesting trademark permissions to use an Apache project logo for their training certification program. Starting the process of working with counsel to come up with a workable way to grant permissions. Feedback on our approach - charging fees, other requirements - appreciated on trademarks@. Several projects and members commented on the Corporate Recognition Best Practices, which is helpful both to better explain the practices as well as get feedback on more real-world applications of these type of guidelines for Apache projects. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Upayavira] The transition from Upayavira to Hadrian and Jim is progressing. Already we have reached out to present (and potential) sponsors about the change. There were some hiccups during the transition, but nothing of importance. Hadrian is looking at ways to attract new sponsors and how we could run fundraising campaigns. Hadrian reviewed the fundraising@ threads for the past year and there are some good proposals we need to act on. Cleaning up our "Thanks" page is an example. Sally and Hadrian worked on a Holiday Thanks card project. We expect to send a digital Thank You cards to all sponsors this week. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] I. Budget: there are no payments due at this time. Sally Khudairi is reviewing the mid-year budget to ensure that we are on track for the second half of the Fiscal Year. II. Fundraising/Branding/Marketing liaison: Sally is working with Fundraising on developing quarterly reports, as well as holiday communications. She continues to liaise with Trademarks & Brand Management with usage requests. III. Press Releases: the following formal announcements were issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 09 December 2014 --The Apache Software Foundation Announces Apache™ MetaModel™ as a Top-Level Project - 02 December 2014 --The Apache Software Foundation Announces Apache™ Drill™ as a Top-Level Project - 19 November 2014 --The Apache Software Foundation Celebrates 15 Years of Open Source Innovation and Community Leadership - 17 November 2014 --Apache CouchDB™ Adds Clustering and Big Data Capabilities With 2.0 Developer Preview Release of Its Popular NoSQL Database - 12 November 2014 --The ASF @ 15 -- Community Over Code IV. Informal Announcements: 11 items were tweeted on @TheASF. Sally continues to publish a weekly "News Roundup" of news items sent to announce@apache.org, announce@apachecon.com, and items of interest to the Apache community. 12 weekly summaries have been issued thus far. V. Future Announcements: no official announcements are in development. Those PMCs wishing to announce major project news, as well as podlings ready to graduate from the Incubator, are welcome to contact Sally at for more information. Kindly provide at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 4 media requests, and proactively reached out to 13 journalists regarding misinformation communicated about a new podling that entered the Apache Incubator. Sally met with the heads of communications of the organization behind the podling submission, as well as a company based on an Apache project regarding their communications plan for their upcoming IPO this month. We have established an editorial framework and publishing process for Apache blog contributions to OpenSource.com. The ASF received 2,271 press clips over this time period, vs. last month's clip count of 2,799. VII. Analyst Relations: we responded to 3 analyst queries. Apache was mentioned in 2 write-ups by Gartner, 2 reports by Forrester, 9 write-up by GigaOM, 6 reports by 451 Research/Yankee Group, and 5 reports by IDC. Forrester issued their vendor report on private Cloud software, with Apache CloudStack correctly represented. VIII. ApacheCon liaison: Sally is working with Ross on creating an ASF-wide marketing campaign that can be mapped against the tracks at ApacheCon. IX. (Non-ASF) Industry Events and Outreach liaison: none at this time. X. Newswire accounts: we have 31 pre-paid press releases with NASDAQ GlobeNewswire through the end of 2016, and continue to receive gratis news release distribution in the UK by Pressat. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] New Karma: ========== Andrew Bayer was added to root@ Finances: ========== $758.48 Windows License $761.27 Replacement Harddrives $1607.78 Service contracts $1247.95 AWS Operations Action Items: ======================== n/a Short Term Priorities: ====================== Codesigning: ------------ A number of projects inquired about codesigning at ApacheCon with intent to sign up and request access to codesigning. In the last 30 days no releases have been signed. Machine deprecation: -------------------- The failure of the machine underlying the SVN master has caused some reprioritization of work and evaluating our older physical machines for the important services that run there. There is ongoing work to relocate the writable git service as well as the Bugzilla machines off of the rapidly aging hardware. Long Range Priorities: ====================== Monitoring ---------- Work continues on monitoring, with several advances being made The first is work with collectd that is being deployed to all of our puppetized-machines. This gives us insight into performance metrics of the machine. Additionally, we've managed to get Dell's OMSA platform for monitoring the underlying hardware deployed to a number of physical hosts. This information is being utilized to monitor for things like failed disks, failed power supplies, and see other overall health information like ambient and internal temperatures. We've gotten a platform that integrates PagerDuty, Hipchat, and email alerts for our Dell physical hardware that has OMSA installed. You can see the code here: https://github.com/humbedooh/dsnmp We are also expanding the radius of hardware notifications from root@ to infrastructure-private. All of this while reducing that down to a single email per day. Automation ---------- We continue to make large steps forward in our automation efforts. The following services are now in configuration management. Several other are currently in progress. rsync.apache.org Git mirrors Subversion master status.a.o website Additionally, some of our work from last months' work around getting the webserver into configuration management has been adopted upstream. https://github.com/puppetlabs/puppetlabs-apache/pull/939 Resilience --------- We now have a second critical service that we have the ability to easily replicate and redeploy. Technical Debt -------------- We are encountering lots of touchpoints that are tied to specific machine names, specific file locations on specific machines and a large chunk of our time is spent in having to decouple this. General Activity: ================= This month has been extraordinarily taxing on Infrastructure, with three large outages or service degradations occurring following ApacheCon. Several volunteers and contractors traveled to Budapest to attend ApacheConEU. In addition to a dedicated track around Infrastructure, an Infra hackfest table was manned where folks could come and ask questions or get help. Many folks took advantage of this. While at ApacheConEU, a number of volunteers and contractors met with folks from OpenOffice to talk about existing and future needs. Details of this meeting can be seen in Andrea Pescetti's notes: http://s.apache.org/aooinframeetingreport Git mirroring (including git mirroring to github) suffered some disruption immediately following ApacheConEU. The 6+ year old machine that the service was running on was shared with 3 project zones, and as the number of git mirrors has increased over time, service delays began increasing to the point that the service was non-functional. Initial attempts to restore service on machine were not successful over the long term and we ended up moving the service off of the affected host and into AWS. The underlying machine that the service was running on has been deprecated. We have sent the projects with zones there notice that we plan to shut down the machine in the not too distant future. We have begun organizing replacement resources in lieu of the Solaris zones. The machine that ran the Foundation's SVN master suffered an outage caused by a failure of the root filesystem array. The initial public reporting is at: https://blogs.apache.org/infra/entry/subversion_master_undergoing_emergency_maintenance The post-mortem report from this event is at: https://blogs.apache.org/infra/entry/svn_service_outage_postmortem We were able to resurrect the service on new hardware with the configuration residing completely in configuration management. This should minimize the time to recovery for future issues. The recovery took approximately 2 days to complete. We suffered a loss of all network connectivity to services in our colo facility at Oregon State University Open Source Lab on 10 December. The outage lasted almost 2 hours. We are still working with OSUOSL, OSU, and NERO to figure out what happened. A redundant (but disabled) network link was activated to bring us back online. While monitoring the newly provisioned webserver, we discovered that Cassandra is pointing users to a .deb package repository on the main webservers instead of utilizing the mirrors, as package repositories won't function with our current mirror offering. After some analysis we found that this package repository was the source of 15% of all traffic hitting our webservers. Our initial thought was to block that traffic. Doing so would have had a large impact on folks. We are currently researching options to provide package repositories so as to remove that load from our main webservers. Uptime Statistics: ================== Unfortunately, uptime for critical services this month saw a sharp decline due to the subversion outage. Also affecting uptime was the brief network outage on December 10/11, as well as the migration of the git mirrors to a new location. Overall, due to all other services behaving exemplary, we did experience a slight increase in overall uptime by 0.03% compared to previous months. Thus, the total recorded uptime for 2014 (weeks 27 through 50) is as follows: Type: Target: Reality: Target Met: --------------------------------------------------------- Critical services: 99.50% 99.84% Yes Core services: 99.00% 99.77% Yes Standard services: 95.00% 98.38% Yes --------------------------------------------------------- Overall: 98.00% 99.39% Yes --------------------------------------------------------- For details on each service as well as average response times, see http://s.apache.org/uptime Contractor Details: =================== Geoffrey Corey: - Resolved 37 JIRA tickets - Worked on completing the steps to graduate 4 projects to TLPs - First round of On-Call duties - Rename argus podling to ranger - Coordinate with OSUOSL to replace disk in Tethys - Coordinate with Henk P. to migrate rsync.apache.org us host off eos and onto the AWS TLP server - clean TLP off eos to help recover disk space - Clean up lingering details with TLP/dist and rsync being migrated off eos - Helped in various ways to restore svn master after the failure of eris Daniel Gruno: - Helped to restore the subversion master after the failure had occurred - Worked on implementing more extensive SNMP monitoring of capable (mostly puppetized) hosts - Moved git.apache.org off the aging Solaris box and onto a new puppetized VM - Tweaked svn/git-to-github syncing process to cut down execution time from 2 hours to 8 minutes - Helped clean up some TLP snafus in relation to bringing svn templates to git. - Various on-call duties - Resolved 35 JIRA tickets since last report - Fixed various rendering issues with status.apache.org by using asynchronous calls Chris Lambertus: - Resolved 9 Jira tickets - Helped to restore the subversion master after the failure had occurred - On-call duties - fixed FUB VPN and rebuilt oceanus as cloudstack testbed - resolved ongoing issues with secmail.py - resolved major outage due to eirene vmware network failure - resolved nightly backup problems with several hosts - ongoing prototyping and evaluation of "enterprise" backup solutions - troubleshooting assistance with TLP/git/svn puppet migrations and service configs - documented nexus project creation process - ongoing addition of hardware to Dell OME, acquisition of windows license to make this a complete service Tony Stevenson: - Worked on the restoration of SVN master, including moving to Ubuntu and puppet - Started work on moving the git-wip-us service off of again baldr onto a Ubuntu VM. - Various on call activities - Attended Apachecon, where we had several infra sessions and an Infra meetup on the Sunday following the conf. - Worked on several JIRA issues and some longer term background activities like host patching. - Conducted the SVN master post-mortem exercise - Writing and updates of puppet modules to continue to make them platform agnostic Gavin McDonald: - Worked on 75 Jira Tickets, closing 57. - Infra commits SVN - 33 - On Call duties. - Work with new contractors on various issues. - Updating non puppet VMs/Machines for security updates. - More work on reducing cron mails - Work started on archive logging for HipChat - Restored SVN to Buildbot Hooks mechanism after the move. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] The Apache Travel Assistance Committee assisted 12 people in attending ApacheCon Europe 2014 in Budapest. These were drawn from 9 different countries, predominantly Europe, but with a few coming in from further afield where their project(s) are strongly Europe focused and there was lots for their project at the conference. Questionnaires have been sent out to all attendees, and responses have now been received from all. General feedback was positive, and Jan has kindly agreed to sumarise them, hopefully for next month's report. We'll also try to pull out some quotes for Sally. Feedback on the process is being fed into the Austin planning. We're still awaiting Virtual sending out the remaining wires for Budapest costs. Once those have gone, we can finalise the Budapest costs in USD (remaining costs are fixed in other currencies), and report. It's expected to be slightly higher than originally planned, in large part because we planned with hotel costs we thought was VAT inclusive but which turned out to be ex-VAT. Still in budget though! We've learnt lessons on this for Austin. Applications for Austin have opened, and we've worked with Sally and PMCs to get the word out. We have plans for additional publicity during the applications period. Following some progress improvements agreed after Budapest, we've been able to shorten the normal time period to fit with the later-than-normal CPF close. We have enough committee members signed up to cover all roles for Austin, with a little slack. One person resigned from the committee after Budapest. We're very glad for all Tony's hard work for TAC! ----------------------------------------- Attachment 7: Report from the VP of W3C Relations [Andy Seaborne] There is an election for participation (by individuals) in the W3C Technical Architecture Group. Voting closes end 2015-01-08. ----------------------------------------- Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski] I presented at the Practicing Law Institute (PLI) last week during their "Open Source" training session; my topic was related to open source communities. There were also other topics regarding patents, ethics, etc that were useful and interesting. Nothing at this time for board action. ----------------------------------------- Attachment 9: Report from the Apache Security Team Project [Mark Cox] There continues to be a steady stream of reports of various kinds arriving at security@. These continue to be dealt with by the security team. November 2014 1 Security vulnerability question, but not a vulnerability report 6 Vulnerability reports to security@apache.org 2 [httpd] 1 [site] rejected 1 [xerces] 1 [trafficserver] 1 [tomcat] 7 Vulnerability reports to projects own security lists 2 [struts] 2 [oo] 1 [couchdb] 1 [cloudstack] 1 [spamassassin] ----------------------------------------- Attachment A: Report from the Apache Abdera Project [Ant Elder] ----------------------------------------- Attachment B: Report from the Apache Allura Project [Dave Brondsema] 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. Project Status -------------- No issues needing board attention. We would like to attract more contributors, and we're working on getting into a more frequent release cycle which may help. Community --------- * Latest committer & PMC member added in Oct 2014 * Ongoing tickets & commits from the active developers. * A few email discussions with Allura users / deployers. Community Objectives -------------------- We completed the move of tickets from SourceForge to the Allura self-hosted site. We would like to find and encourage new contributors to Allura. We also want to explore if other Apache projects would be interested in using Allura. Releases -------- Last release was Feb 2014. We are working on one blocker and then will proceed with a new release. ----------------------------------------- Attachment C: Report from the Apache Ant Project [Conor MacNeill] ----------------------------------------- Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney] 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. Project Releases The last release of Any23 (1.1) was on 16-Oct-2014. Overall Project Activity since last report Project activity has been reasonably slow however this is nothing new for Any23 generally. Work is nearly complete on the Any23 plugin for Apache Nutch trunk codebase https://issues.apache.org/jira/browse/NUTCH-1129 Additionally Any23 has featured in a number of recent presentations at NASA Jet Propulsion Laboratory where the software is being evaluated for use within the Systems Engineering domain. How has the community developed since the last report? Since the Any23 1.0 release the release management process has included emailing the announcement to a number of very active W3C lists. The intention here is to interest other developers and build the Any23 community further. This strategy is gathering traction, usually with activity immediately after the last two Any23 releases. http://any23.apache.org/release-howto.html#Announce_the_Release Any23 received contributions in the form of the donation of both any23.org and any23.com domain names. We thank Richard Cyganiak for the contributions and also Infra for accepting them. Changes to PMC & Committers Stephane Corlosquet (scor) was added to the Any23 PMC on Tue, 19 Aug 2014 04:28:51 GMT. ----------------------------------------- Attachment E: Report from the Apache APR Project [Jeff Trawick] 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. Releases ======== The project has not produced any releases this quarter. APR 1.5.1 was released on April 21, 2014. APR-util 1.5.3 was released on November 18, 2013. A maintenance release of APR is needed, and should be anticipated in early 2015. Community ========= New PMC members: none The last new PMC member was added in November of 2013. New committers: none The last two committers were added in June of 2014. Six bugs were opened during the reporting period, with some sort of developer followup (closure or discussion) on four bugs. Mailing list activity has been the lightest in this quarter (thus far) as in any quarter in the history of the project. Development =========== Nothing to report Issues ====== There are no board-level issues at this time. ----------------------------------------- Attachment F: Report from the Apache Archiva Project [Olivier Lamy] Apache Archiva is an extensible repository management software that helps taking care of your own personal or enterprise-wide build artifact repository. It is the perfect companion for build tools such as Maven, Continuum, and ANT. Releases -------- None since last report Community --------- We added a new committer: Sascha Voigt (17 July 2014) We added a new PMC member: Jean-Baptiste Onofre (28 July 2014) The new 2.x series releases tends to generate a bit more traffic mailing lists. Development ----------- On-going development is now geared towards the release of 2.2.x with particular enhancements to LDAP support and fixing issues. Issues ------ As some projects at Apache, Archiva was dependant on rsync services from people.a.o to synchronize their Maven artifacts to Maven Central after a vote period based on artifacts deployed to the Apache Archiva instance. It looks to be now mandatory to use an external product call Nexus whereas Sonatype still support this rsync synchronization. Obviously the Archiva team will be happy to continue using his own dog food. The issue has been reported here: https://issues.apache.org/jira/browse/INFRA-8762 ----------------------------------------- Attachment G: Report from the Apache Axis Project [Deepal Jayasinghe] ----------------------------------------- Attachment H: Report from the Apache Bigtop Project [Konstantin Boudnik] 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. RELEASES * The last release of Apache Bigtop was version 0.8.0, released on Oct 5, 2014 * Bigtop 0.9.0 is the next release scheduled for Q1 of 2015, based on Hadoop 2.6 CURRENT ACTIVITY * Development activity for 0.9.0 release continues as can be seen from the following list: https://issues.apache.org/jira/issues/?filter=12329840 (since last board report, Sep 2014) * Community is working on next release, build system usability and product testability * The project has fully migrated away from make to Gradle build infrastructure * Two new software components were added since last release: GridGain Hadoop Accelerator, and Tachyon FS cache * The project has presented a talk at ApacheCon Europe 2014 * We are working to put together Bigtop workshop at Scale 13x conference COMMUNITY * Project has grown with a few new contributors since last report * No other changes in the community in this period * Currently there are: - Total of 118 subscribers to the developer list - Total of 149 subscribers to the user list - Total of 25 subscribers to the announce list - Total of 26 committers - Total of 21 PMC members ISSUES * There are no issues requiring board attention at this time. ----------------------------------------- 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 ====== It is worth the board noting that there have been concerns raised about the rate of development and the inability to create a release. While there has since been a release, this is discussed below. Releases ======== There has been one release over the last three months. The last releases were: * apache-bloodhound-0.6 (16th July 2013) * apache-bloodhound-0.7 (23rd August 2013) * apache-bloodhound-0.8 (11th December 2014) Community & Development ======================= No new committee members have been added this quarter. The last new committee members to be added joined in January 2014. The last new committers were added in May 2014 for the GSoC scheme. Concerns have been raised on the private list about the rate of development to the extent of a suggestion of moving the project to the attic. This has not resulted in any great response but the reasons for this are not clear. However, one outcome from this suggestion was that a release was finally created and the vote passed smoothly. It was also good to see demonstrations of continued interest from some of the GSoC students. It is clear that the rate of development has to increase again. Given the recent progress, the situation will hopefully become clearer over the next three to six months. ----------------------------------------- Attachment J: Report from the Apache BookKeeper Project [Ivan Kelly] Bookkeeper is a distributed, reliable, and high performance logging service. The project also includes Hedwig which is a highly scalable Pub/Sub service built on top of ZooKeeper and Bookkeeper with strong durability guarantees. = Project Status = Since becoming TLP (2014-11-19), focus has been on getting our new infrastructure set up. There were some delays in getting the mailing list up and running, but it's all resolved now. Subsequently, everything that depended on the mailing lists was delayed. We are current voting on a set of bylaws. Development work has been low over the last month, but a lot of work has been done to improve the documentation and accessibility of the project (new website, new client tutorial, etc). = Releases = Our last release was 4.3.0, released on 2014-10-14. We are currently in the process of voting for a release plan for 4.3.1 and 4.2.4. = Community Status = There have been no committers added since we became TLP (2014-11-19). The last committer added, when we were a subproject, was Rakesh Radhakrishnan on 24th July 2014. 50 subscribers in dev@bookkeeper.apache.org 66 subscribers in user@bookkeeper.apache.org 811 issues opened to date, 34 since 2014-10-01 556 issues resolved to date, 14 since 2014-10-01 50 people have reported issues, 9 since 2014-10-01 24 people have contributed patches, 6 since 2014-10-01 ----------------------------------------- Attachment K: Report from the Apache BVal Project [Matt Benson] 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 release was v0.5 in September 2012. ### Activity ### The Commons Weaver quasi-dependency bottleneck has as long last been resolved and BVal development has resumed. We continue to work with the Apache TomEE PMC, who bundle our project and thereby provide a clear barometer for ease of integration. I note the question on the agenda of whether we have enough committers to make releases... I assume this refers to BVal, though it could have referred to Commons as we did spend an unfortunate amount of time blocked there. While the developer energy of most of the PMC is being expended elsewhere, I believe we have strong enough representation amongst the wider "ApachEE" (i.e. JEE at Apache) community to be handily able to garner the votes for a release once we are satisfied with the state of the codebase. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment. ----------------------------------------- Attachment L: Report from the Apache Camel Project [Christian Mueller] Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 5 new contributors who signed the ICLA. * The community stays at a high level (321 subscribers at dev@; 800 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 552 mails per month on the users mailing list in September 2014 - November 2014 * Avg. 183 mails per month on the dev mailing list in September 2014 - November 2014 * Avg. 647 commits per month in September 2014 - November 2014 Community Objectives -------------------- * We are planning to release Apache Camel 2.14.1 in the next weeks. * Adding new features and improvements to Apache Camel in version 2.15.0. Project Composition ------------------- * One new committer was added in this reporting period * Colm O hEigeartaigh 11/06/2014 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.12.5 (10/27/2014) * 2.13.3 (10/31/2014) ----------------------------------------- Attachment M: Report from the Apache Cayenne Project [Andrus Adamchik] Apache Cayenne is a Java persistence framework. It takes a distinct approach to object persistence and provides an ORM runtime, remote persistence services, and a GUI mapping/modeling tool. Project Status * Cayenne 3.1 Final was released on September 29. * Active 3.2 release branch was renamed to 4.0 to reflect a significant scope of changes. * 4.0 development has been very active. We added a new fluent query APIs, and a new automated way to synchronize the ORM model with DB-schema and Java classes, made significant CayenneModeler UI improvements. More new features are likely to happen in the coming months. * We are in preparations to release 4.0.M2. Community * dev@ list activity is higher than before, due to the active discussions of the new 4.0 features. * There seems to be a trend of declining activity on the user@ list though. Not specifically in this quarter, more like a long-term trend, partially explained by good support provided on stackoverflow, partially perhaps by the project maturity. * We receive steady contributions from two new developers. * The last PMC member was added in December 2012. * The last committer was added in May 2012. ----------------------------------------- Attachment N: Report from the Apache Chemistry Project [Florian Müller] 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). The project has graduated in February 2011. == Project status == We added a new subproject called "Chemistry Parts". It provides a CMIS library for JavaScript and Web Parts for SharePoint, using the JavaScript library. The "Chemistry Parts" contributors became committers. The OpenCMIS subproject frequently receives bug fixes and smaller improvements. The other subprojects are not very active at the moment. There are no board-level issues at this time. == Community == We added six new committers who look after the "Chemistry Parts" subproject. == Releases == Last releases: OpenCMIS 0.12.0 2014-08-21 ObjectiveCMIS 0.4 2014-07-25 DotCMIS 0.6 2014-03-17 cmislib 0.5.1 2012-12-19 ----------------------------------------- Attachment O: Report from the Apache CloudStack Project [Hugo Trippaers] DESCRIPTION Apache CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. ISSUES CVE-2014-7807: Apache CloudStack unauthenticated LDAP binds, Dec 8 2014 CURRENT ACTIVITY * The community is working on the next major release (4.5.0) of Apache CloudStack. The first release candidate is available already. * Ongoing efforts in fixing bugs and findings from static code analysis resulted in a number of bug fixes to existing branches. * Apache CloudStack CloudMonkey 5.3.0 was released on Nov 11 2014. Apache CloudStack CloudMonkey is a CLI tool for interacting with Apache CloudStack and is distributed separate from Apache CloudStack * Apache CloudStack 4.4.1 was released Oct 23 2014. This maintenance release is followed by a second maintenance release numbered 4.4.2 at Dec 10 2014. Release 4.4.2 fixes the vulnerability reported in CVE-2014-7807 * The community enjoyed a very successful European CloudStack Collaboration Conference (CCCEU). CCCEU in Budapest. The new format including a full day single room track and poster sessions seemed to work out well. * The community is still struggling with way to improve quality and prevent master from breaking. Multiple efforts including improved automated testing and work flow enhancements are being executed and/or proposed. There is no clear consensus other than the generic agreement that the current situation leaves ample room for improvement. RELEASES Apache CloudStack 4.4.1 was released on Oct 23, 2014. Apache CloudStack 4.4.2 was released on Dec 10, 2014. Apache CloudStack CloudMonkey 5.3.0 was released on Nov 11, 2014 COMMUNITY Including the following additions, CloudStack has 96 committers and 32 (+3) PMC members. New Committers: - New PMC Members: Ian Duffy (duffy) - Sep 29 Pierre-Luc Dion (pdion891) - Sep 29 Rajani Kuruturi (rajani) - Oct 16 The Apache CloudStack project remains a high volume community: dev@ msgs = Nov: 1322, Oct: 1054, Sep: 1421 users@ msgs = Nov: 670, Oct: 557, Sep: 481 issues@ msgs = Nov: 1933, Oct: 1011, Sep: 1671 commits@ msgs = Nov: 1039, Oct: 696, Sep: 826 marketing@ msgs = Nov: 70, Oct: 60, Sep:69 users-cn@ msgs = Nov: 120, Oct: 46, Sep: 61 ----------------------------------------- Attachment P: Report from the Apache Commons Project [Gary Gregory] 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. The last report was September 9 2014. No issues require board attention at this time. Overall project health is good with six releases this period. Releases: 2014-09-25: Apache Commons Configuration 2.0-alpha1 2014-09-30: Apache Commons Weaver 1.1 2014-10-10: Apache Commons Compress 1.9 2014-11-06: Apache Commons Exec 1.3 2014-11-09: Apache Commons Codec 1.10 2014-11-16: Apache Commons CSV 1.1 New committers None News 2014-11-07: Proposal to create Apache Commons Text as a sandbox component. 2014-12-08: VOTE passed to allow all Apache committers to commit to Apache Commons. ----------------------------------------- Attachment Q: Report from the Apache Cordova Project [Shazron Abdullah] Apache Cordova is a platform for building native mobile applications using HTML, CSS and JavaScript. # Status Current releases have been voted on according to the Apache vote policy. We have released Cordova CLI 4.0 which is the beginning of the independence of platform versions from the cli version. For example, with the Cordova CLI 4.0 release, it includes the pinned platform versions at version 3.6.4 (except for cordova-browser, at 3.6.0). Each new platform release will correspond with a tools release to update the pinned versions. Since the last board report, Apache Cordova has had: - over 2100 commits in its 52 Git repositories - over 2800 emails in its dev mailing list - over 4500 issues/comments on issues in JIRA - 8 new contributors filed iCLAs specifically for contributing to Apache Cordova - over 436,000 downloads of cordova from https://www.npmjs.org/package/cordova Since the last board report, Apache Cordova has had 60 different releases. We also released a new platform, cordova-browser. # Community Cordova welcomed the following new committers and PMC members: - Maxim Ermilov (zaspire) - Staci Cooper (stacic) # Board Issues There are no Board-level issues at this time. # Releases (60) - http://archive.apache.org/dist/cordova/ ## Platforms (15) Released Nov 6th, 2014 - cordova-ios@3.7.0 ............. http://s.apache.org/hzL - cordova-windows@3.7.0 ......... http://s.apache.org/WBa - cordova-wp8@3.7.0 ............. http://s.apache.org/WBa Released Sep 15th, 2014 - cordova-amazon-fireos@3.6.0 ... http://s.apache.org/RjF - cordova-android@3.6.3 ......... http://s.apache.org/RjF - cordova-blackberry@3.6.3 ...... http://s.apache.org/RjF - cordova-firefoxos@3.6.3 ....... http://s.apache.org/RjF - cordova-ios@3.6.3 ............. http://s.apache.org/RjF - cordova-ubuntu@3.6.3 .......... http://s.apache.org/RjF - cordova-windows@3.6.3 ......... http://s.apache.org/RjF - cordova-wp8@3.6.3 ............. http://s.apache.org/RjF Released Oct 3rd, 2014 - cordova-android@3.6.4 ......... http://s.apache.org/L7i Released Oct 8th, 2014 - cordova-wp8@3.6.4 ............. http://s.apache.org/jqz - cordova-windows@3.6.4 ......... http://s.apache.org/SSo - cordova-browser@3.6.0 ......... http://s.apache.org/0KI ## Libs (2) Released Sep 15th, 2014 - cordova-app-hello-world@3.6.3 ...... http://s.apache.org/RjF - cordova-mobile-spec@3.6.3 .......... http://s.apache.org/RjF ## Tools (15) Released Nov 13th, 2014 - cordova-js@3.7.2 ............. http://s.apache.org/V7c - cordova-cordova-lib@4.1.2 .... http://s.apache.org/V7c - cordova-cordova@4.1.2 ........ http://s.apache.org/V7c - cordova-plugman@0.22.16 ...... http://s.apache.org/V7c Released Sep 15th, 2014 - cordova-cordova-lib@0.21.11 ........ http://s.apache.org/RjF - cordova-cordova@3.6.3-0.2.11 ....... http://s.apache.org/RjF - cordova-plugman@0.22.8 ............. http://s.apache.org/RjF Released Sep 22nd, 2014 - cordova-js@3.6.4 .................... http://s.apache.org/vLq - cordova-cordova-lib@0.21.13 ......... http://s.apache.org/vLq - cordova-cordova@3.6.3-0.2.13 ........ http://s.apache.org/vLq - cordova-plugman@0.22.10 ............. http://s.apache.org/vLq Released Oct 15th, 2014 - cordova-js@3.7.1 .......... http://s.apache.org/esw - cordova-lib@4.0.0 ......... http://s.apache.org/esw - cordova-cli@4.0.0 ......... http://s.apache.org/esw - cordova-plugman@0.22.12 ... http://s.apache.org/esw ## Plugins (28) Released Sep 22nd, 2014 - cordova-plugin-battery-status@0.2.11 ........ http://s.apache.org/DK5 - cordova-plugin-camera@0.3.2 ................. http://s.apache.org/DK5 - cordova-plugin-console@0.2.11 ............... http://s.apache.org/DK5 - cordova-plugin-contacts@0.2.13 .............. http://s.apache.org/DK5 - cordova-plugin-device@0.2.12 ................ http://s.apache.org/DK5 - cordova-plugin-device-motion@0.2.10 ......... http://s.apache.org/DK5 - cordova-plugin-device-orientation@0.3.9 ..... http://s.apache.org/DK5 - cordova-plugin-dialogs@0.2.10 ............... http://s.apache.org/DK5 - cordova-plugin-file@1.3.1 ................... http://s.apache.org/DK5 - cordova-plugin-file-transfer@0.4.6 .......... http://s.apache.org/DK5 - cordova-plugin-geolocation@0.3.10 ........... http://s.apache.org/DK5 - cordova-plugin-globalization@0.3.1 .......... http://s.apache.org/DK5 - cordova-plugin-inappbrowser@0.5.2 ........... http://s.apache.org/DK5 - cordova-plugin-media@0.2.13 ................. http://s.apache.org/DK5 - cordova-plugin-media-capture@0.3.3 .......... http://s.apache.org/DK5 - cordova-plugin-network-information@0.2.12 ... http://s.apache.org/DK5 - cordova-plugin-splashscreen@0.3.3 ........... http://s.apache.org/DK5 - cordova-plugin-statusbar@0.1.8 .............. http://s.apache.org/DK5 - cordova-plugin-vibration@0.3.11 ............. http://s.apache.org/DK5 Released Oct 15th, 2014 - cordova-plugin-camera@0.3.3 ................. http://s.apache.org/hq - cordova-plugin-contacts@0.2.14 .............. http://s.apache.org/hq - cordova-plugin-file-transfer@0.4.7 .......... http://s.apache.org/hq - cordova-plugin-globalization@0.3.2 .......... http://s.apache.org/hq - cordova-plugin-inappbrowser@0.5.3 ........... http://s.apache.org/hq - cordova-plugin-media@0.2.14 ................. http://s.apache.org/hq - cordova-plugin-media-capture@0.3.4 .......... http://s.apache.org/hq - cordova-plugin-network-information@0.2.13 ... http://s.apache.org/hq - cordova-plugin-splashscreen@0.3.4 ........... http://s.apache.org/hq ----------------------------------------- Attachment R: Report from the Apache cTAKES Project [Pei J Chen] Apache cTAKES (clinical Text Analysis and Knowledge Extraction System) is a natural language processing (NLP) tool for information extraction from electronic medical record clinical free-text. Issues: There are no issues requiring board attention at this time. Releases: - ctakes-3.1.1 on 2013-12-05 - ctakes-3.2.0 on 2014-07-23 - ctakes-3.2.1 on 2014-12-10 Development: The committee is actively working on a future release. Some of the planned code changes for upcoming release includes: - Hadoop/Spark Integration (example) - Various big fixes in Jira Community: Last Committers/PMC: Murali Nagendranath (2013-10-21) Vijay Garla (2013-11-16) Jay Vyas (2014-11-04) There was a local cTAKES meetup hosted by the local Boston group in Oct (http://s.apache.org/ctakesmeetupoct2014). There is an ongoing collaborative work with integrating cTAKES with other Apache Projects such as BigTop, Spark, etc. for Big Data processing. he community seems to be active and continues to be growing steadily. dev mailing list subscribers count: 135 (+4 since last report) user mailing list subscribers count: 115 (+2 since last report) ----------------------------------------- Attachment S: Report from the Apache Curator Project [Jordan Zimmerman] ----------------------------------------- Attachment T: Report from the Apache DeviceMap Project [Reza Naghibi] Apache Devicemap is a data repository containing devices attributes, and their related browsers, and operating systems. The project also maintains an api to classify these attributes. CURRENT ACTIVITY * DeviceMap recently graduated to a TLP at the last board meeting. * Resource migration from the incubator has been completed. * Many new devices have been added to our JIRA for inclusion on our next data release. RELEASES * There have been no releases since the 1.0.1 data release on October 15th. A new Java client release has been staged and work is in progress on our next data release. COMMUNITY * There were no new additions to the PMC since the last report. ISSUES * There are no issues requiring board attention at this time. ----------------------------------------- Attachment U: Report from the Apache DirectMemory Project [Raffaele P. Guidi] Apache DirectMemory is an off-heap cache implementation for the JVM * General Information Development and mailing lists traffic are mostly quiet * Issues No known issues at the time * Committers or PMC members change Last added PMC member was Noctarius (Cristoph Engelbert) on 2013-09-25 * Releases Release 0.2 has seen the light on 2013-09-17 ----------------------------------------- Attachment V: Report from the Apache Drill Project [Jacques Nadeau] Description: Apache Drill is a distributed query layer that supports querying JSON, NoSQL and Hadoop using SQL. Current Activity: Drill graduated to a TLP at the last board meeting. Since then, Drill has migrated mailing lists, the website and the git repository to top-level resources. Traffic is good on the user and dev mailing lists within many new user and contributor engagements. Releases: * The 0.6 release of Drill was on 10/26/2014 * The 0.7 release is targeted for a release vote in the next couple weeks. This will be the first release as a top-level project. Community: * 335 emails on the dev mailing list in November * 204 emails on the user mailing list in November * The PMC has 16 members * No new committers or PMC members added since graduation Issues: * There are no issues requiring board attention at this time. ----------------------------------------- Attachment W: Report from the Apache Felix Project [Carsten Ziegeler] Apache Felix is a project aimed at implementing specifications from the OSGi Alliance as well as implementing other supporting tools and technologies aligned with OSGi technology. Community PMC: No new PMC members have been added in this report period. The last new PMC member was added in Dec. 2013 Committers: One new committer: Bob Paulin. Steady mailing list activity. There are no issues requiring board attention at this time. Software Apache Felix HTTP 2.3.2 (November 11, 2014) Apache Felix Event Admin 1.4.2 (September 14, 2014) Project Branding TM missing from all Logos Licensing and other issues None ----------------------------------------- Attachment X: Report from the Apache Flex Project [Alex Harui] Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES - Apache Flex 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 Tour De Flex Component Explorer 1.1 was released on 9/24/14. - Apache Flex Squiggly 1.0 was released on 9/3/14 - Apache Flex Installer 3.1.0 was released on 7/14/14. - Apache Flex SDK 4.13.0 was released on 7/16/14. - Apache Flex FlexUnit 4.2.0 was released on 4/13/14. - Apache FlexJS 0.0.2 was released on 7/17/14. - Apache Flex FalconJX 0.0.2 was released on 7/17/14. ACTIVITY Activity in Apache Flex is becoming more diverse. While there is still work going on fixing bugs in the existing Adobe Flash Platform-dependent code base, and on FlexJS, a version of Flex that is independent from the Adobe Flash Platform, there has been more tangible activity working on Maven support for the various releases, contributions to the Installer, Tour De Flex, the Squiggly Spell Checking library, Text Layout Framework, Android and IOS skins, and more. In the past three months we've continued to see: - Continued JIRA activity (more bugs raised than resolved however) - New committers and potential committers. Code Donation Update - Swiz donation is still pending. The donor has not filed the paperwork. - Mahmoud Ali and Bruno Pacola donated the FlatSpark theme. COMMUNITY - Mahmoud Ali, Bruno Pacola, Curtis Aube, Neil Madsen and Jorge Yabra were added as committers. - Tom Chiverton, Piotr Zarzycki, Chris Martin and Mihai Chira were promoted from committer to PMC member. - Latest analytics include around 2000 hits per day on the website during the work week (less on weekends). That’s about the same as previous report. - There were more than 10,000 installs of 4.13.0 since its release. - More than 20,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. ----------------------------------------- Attachment Y: Report from the Apache Giraph Project [Avery Ching] Giraph is a Bulk Synchronous Parallel framework for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. Project releases 1.1.0 - This was finally released by Roman on 11/26. Thanks Roman! Overall project activity since the last report Mostly bug fixes for the 1.1.0 release. When were the last committers or PMC members elected? We have a new committer - Sergey Edunov on 11/24! New community development Maja presented in Boston@Scale on 11/12 on how she used Giraph as the foundation for scalable collaborative filtering at Facebook (http://dataatscaleboston.splashthat.com/). Mailing list members We continue to see steady mailing list growth. user@ 429 -> 437 dev@ 250 -> 260 ----------------------------------------- Attachment Z: Report from the Apache Gump Project [Stefan Bodewig] Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == During this quarter we've added two new PMC members. Gump seems to create useful results for the few projects that use it. The FOP community has decided they no longer need the service provided by Gump. == 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 Gump builds have been updated to run on Java8 which causes a few builds to break (like the one of Google Guava) and forced us to replace dependencies with pre-packaged binaries in two cases. == Changes to the Roster == All ASF committers have write access to the metadata that configure the ASF installations. Konstantin Kolinko and Mark Thomas joined the Gump PMC. ----------------------------------------- Attachment AA: Report from the Apache Helix Project [Kishore Gopalakrishna] Project Description =================== Apache Helix is a generic cluster management framework used for the automatic management of partitioned, replicated and distributed resources hosted on a cluster of nodes. Helix automates reassignment of resources in the face of node failure and recovery, cluster expansion, and reconfiguration Development =========== - Task framework integrated with a product service - REST API for task framework - Python Helix admin library contributed by the community - 41 new JIRAS since last report - 22 issues resolved Community ========= - 200+ emails on the dev list - 50+ emails on the user list - Community effort in building Python Helix admin library - Community effort in evaluating Helix controller performance ----------------------------------------- Attachment AB: Report from the Apache Hive Project [Carl Steinbach] DESCRIPTION Apache Hive is a data warehouse written on top of Apache Hadoop. It provides SQL to query and manage data (in the form of tables and partitions stored in HDFS or external systems) and provides a metastore containing metadata information about the stored data. RELEASES * The last release of Apache Hive was version 0.14.0, released on November 12, 2014. COMMUNITY * A Hive User Group meeting was held on December 3rd at LinkedIn's offices in Mountain View. 110 people placed their names on the RSVP list. * Eugene Koifman and John Pullokkaran were voted in as committers. The most recent addition was made on October 1st. * Alan Gates and Prasad Mujumdar were voted in as new PMC members. The most recent addition was made on December 9th. * Currently there are: - 713 subscribers to the developer list - 1860 subscribers to the user list - 15 committers - 19 PMC members - 6 Emeritus PMC members BRANDING CHECKLIST Since the last report all remaining branding sub-tasks have been completed. Please refer to HIVE-2432 for the complete list. * Project Website Basics: [DONE] * Project Naming And Descriptions: [DONE] * Website Navigation Links: [DONE] * Trademark Attributions: [DONE] * Logos and Graphics: [DONE] * Project Metadata: [DONE] ----------------------------------------- Attachment AC: Report from the Apache Incubator Project [Roman Shaposhnik] The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are currently 36 podlings undergoing incubation. Two podlings joined us this month, NiFi and Tamaya. Five new IPMC members and two new Shepherds joined our ranks as well. * Community New IPMC members: Andrew L. Farris Thejas Nair Brock Noland Daniel Dai Adam Estrada New Incubator Shepherds: Timothy Chen Andrew L. Farris People who left the IPMC: None * New Podlings Nifi Tamaya * Graduations The board has motions for the following: Falcon The IPMC is currently voting on graduations for: Flink * Releases The following releases were made since the last Incubator report: apache-calcite-0.9.2-incubating apache-twill-0.4.0-incubating apache-parquet-format-2.2.0-incubating apache-johnzon-0.2-incubating apache-slider-0.60.0-incubating metamodel-4.3.0-incubating apache-aurora-0.6.0-incubating * IP Clearance Sling Sightly and XSS modules * Legal / Trademarks There are many on going Podling Name Search requests, with few being closed. Droids still has an open name search. Falcon is processing a name search currently. Tamaya successfully cleared Podling Name Search. Two podlings (BatchEE and Johnzon) are currently waiting on the result of a new licensing agreement w/ Oracle to gain access to the TCKs for new EE related JSRs. Until this is done they could not be considered compliant implementations * Infrastructure SVN outage caused minor inconvenience to some podlings. Argus/Ranger is facing some struggles with their rename. * Miscellaneous The Kalumet podling is currently thinking about throwing around a retirement vote. The Samza community is voting on a draft graduation resolution. There is a vote underway to recommend retiring for the NPanday. Hadoop Development Tools community has voted to retire from the Incubator. -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator Ignite Lens Nifi Tamaya Taverna * Not yet ready to graduate No release: Brooklyn Wave Community growth: Johnzon Sentry Streams * Ready to graduate The Board has motions for the following: Falcon * Did not report, expected next month Ranger (formerly Argus) Kalumet NPanday * Not signed off by mentors Brooklyn MRQL ---------------------------------------------------------------------- Table of Contents Brooklyn Falcon Ignite Johnzon Lens log4cxx2 MRQL NiFi Ripple Sentry Streams Tamaya Taverna Wave ---------------------------------------------------------------------- -------------------- Brooklyn Brooklyn is a framework for modelling, monitoring, and managing applications through autonomic blueprints. Brooklyn has been incubating since 2014-05-01. Three most important issues to address in the move towards graduation: 1. Completing our first release under Apache 2. Grow the community 3. More diversity of the committers/PPMC (currently biased towards employees of a single organization) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? Our community continues to grow slowly but surely, and has received interest and contributions from new community members. We had the opportunity to talk about our project at ApacheCon Europe last week, which has introduced Brooklyn to a wider audience within Apache. How has the project developed since the last report? Code continues to be proposed and merged at a high rate. We are satisfied with our technical velocity. We are currently in the process of making our first release. As is common with incubating project's first releases, this involves several iterations and ongoing discussions with mentors and IPMC. Date of last release: No release yet, but we have begun the process for our first release and aim to release as soon as we possibly can. When were the last committers or PMC members elected? No change since 2014-07-02. Signed-off-by: [ ](brooklyn) Matt Hogstrom [ ](brooklyn) Alex Karasulu [ ](brooklyn) David Nalley [ ](brooklyn) Marcel Offermans [ ](brooklyn) Jean-Baptiste Onofré [ ](brooklyn) Olivier Lamy [ ](brooklyn) Chip Childers [ ](brooklyn) Andrei Savu [ ](brooklyn) Joe Brockmeier [ ](brooklyn) Jim Jagielski -------------------- Falcon 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. Falcon has been incubating since 2013-03-27. Three most important issues to address in the move towards graduation: Graduation resolution was presented to the board in Nov 2014 and the board has asked the project team to address the following issues before it can be considered * Podling name search pending (PODLINGNAMESEARCH-61) * Discrepancy in status report with respect to committer ids. 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? * More users & contributors have joined the falcon project and the community continues to grow How has the project developed since the last report? * Development activity has been very hectic more than 240 JIRAs have been created and about 200 resolved since the last report * There are more than 100 users subscribed on the dev mailing list Date of last release: 2014-12-03 (0.6-incubating) 2014-09-20 (0.5-incubating) When were the last committers or PMC members elected? Aug 28, 2014 Signed-off-by: [ ](falcon) Arun Murthy [X](falcon) Chris Douglas [ ](falcon) Owen O'Malley [ ](falcon) Devaraj Das [ ](falcon) Alan Gates -------------------- Ignite A unified In-Memory Data Fabric providing high-performance, distributed in- memory data management software layer between various data sources and user applications. Ignite has been incubating since 2014-10-01. Three most important issues to address in the move towards graduation: 1. Finish migration to Apache process. 2. Grow active and healthy community around Apache Ignite product. 3. Get on a stable release schedule and have 3 successful product releases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at the moment. How has the community developed since the last report? No new committers/PPMC members were added. Several new contributors have joined. How has the project developed since the last report? - Project planning for the 1st sprint started with over 30 tickets filed in Ignite Jira. - Landing web page was set. - Website design was chosen in Jira, IGNITE-7. Initial version will be pushed early in the week of 12/9. - Ignite code was pushed into Apache GIT repository. The code is fully maven-enabled and buildable. Date of last release: No releases yet: the code is still in the development phase When were the last committers or PMC members elected? 10/01/2014 Initial committers were added. Signed-off-by: [X](ignite) Branko Čibej [X](ignite) Konstantin Boudnik [ ](ignite) Henry Saputra [X](ignite) Roman Shaposhnik [ ](ignite) Michael Stack -------------------- Johnzon Implementation of JSR-353 JavaTM API for JSON Processing (Renamed from Fleece) Johnzon has been incubating since 2014-06-09. Three most important issues to address in the move towards graduation: 1. Expanding the community, increase dev list activity and adding new committers/pmc members. 2. Complete the status page 3. Add and improve documentation Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * Nothing How has the community developed since the last report? There are new people on the dev list and the project got contributions from non-committers. On the dev list there are approx. 70 msgs (on average) messages per month. Christian Grobmeier quits as mentor. How has the project developed since the last report? The project did its first and second incubator release. During the last three month nine jira issues were reported and fixed. Date of last release: 2014-11-22 When were the last committers or PMC members elected? Last committer was elected 2014-08-23, no new PMC members since incubation. Signed-off-by: [X](johnzon) Justin Mclean [ ](johnzon) Daniel Kulp -------------------- Lens Lens is a platform that enables multi-dimensional queries in a unified way over datasets stored in multiple warehouses. Lens integrates Apache Hive with other data warehouses by tiering them together to form logical data cubes. Lens has been incubating since 2014-10-10. Three most important issues to address in the move towards graduation: 1. Make the first release from apache 2. Make project website available on apache 3. Reach out to people through presentations and blogs Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We are still waiting for project website creation via https://issues.apache.org/jira/browse/INFRA-8549 How has the community developed since the last report? * We are near of proposing a new committer * We are actively working on logo for the project * We have presented above Apache Lens in Hadoop meetup at Bangalore, India * Proposed talks on upcoming ApacheCon and HadoopSummit conferences * Mailing list subscription (as on 29th November): ** Dev list : 25 members ** Commits list : 11 members ** User list : 19 members How has the project developed since the last report? * Main activities include ** Podling setup wrt jira, reviewboard, jenkins, confluence space ** Standardizing branching and versioning in project code base ** Improving documentation ** Stabilizing the code for first stable release * Mailing list activity : ** Dev via http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/ *** November - 512 messages ** Commits via http://s.apache.org/yGX is missing *** Missing archive -https://issues.apache.org/jira/browse/INFRA-8744 *** November - 74 messages (counted thru subscription) ** User mailing list activity - None * Issues 82 created and 25 resolved via http://s.apache.org/WOu Date of last release: NONE When were the last committers or PMC members elected? NONE Signed-off-by: [X](lens) Christopher Douglas [X](lens) Jakob Homan [ ](lens) Jean-Baptiste Onofre [ ](lens) Vinod Kumar Vavilapalli -------------------- log4cxx2 Logging for C++ log4cxx2 has been incubating since 2013-12-09. Three most important issues to address in the move towards graduation: 1. Create a release 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None yet. How has the community developed since the last report? Not grown. However the project aims to become a sub project of Apache Logging again. Community growth is not much a matter for this podling, as long as there are a few active contributors. How has the project developed since the last report? Not much: some mails were sent, but in general it was not much development. Date of last release: None. When were the last committers or PMC members elected? Signed-off-by: [X](log4cxx2) Christian Grobmeier [ ](log4cxx2) Scott Deboy Shepherd/Mentor notes: Podling reported late. It doesn't look like the marvin alerts went out. Could be a moderation issue. Mailing list activity is very light. -------------------- MRQL MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Hama, Spark, and Flink. MRQL has been incubating since 2013-03-13. Three most important issues to address in the move towards graduation: 1. increase the number of active committers 2. increase adoption, expand user community, and increase user list activity Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? none How has the community developed since the last report? There were no new developers or new committers since our last reports. How has the project developed since the last report? During the last three month, 12 jira issues were reported, from which 10 were fixed. Most of these issues were related to MRQL query evaluation in Flink mode. Finally, we have set up MRQL on ASF Jenkins, which is a CI server that continuously checks the integrity of our builds and validates our tests. Date of last release: 2014-06-26 When were the last committers or PMC members elected? 2014-04-17 Signed-off-by: [ ](mrql) Alan Cabrera [ ](mrql) Anthony Elder [ ](mrql) Alex Karasulu [ ](mrql) Mohammad Nour El-Din Shepherd/Mentor notes: Podling looks very healthy. -------------------- NiFi NiFi is a dataflow system based on the concepts of flow-based programming. NiFi has been incubating since 2014-11-24. Three most important issues to address in the move towards graduation: 1. Establishment of Apache Infrastructure. Git establishment is outstanding with INFRA-8707 2. Produce an initial release. 3. Grow the community beyond those involved in the incubator proposal. 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? Since podling initiation our dev mailing list has 42 subscribers and the commits mailing list has 19. How has the project developed since the last report? Since podling initiation the team has mailing lists, website, and Jira setup. Awaiting INFRA action for Git. We should then be able to better communicate and grow. We fully understand though that Infra has been very busy addressing the SVN server issues. Date of last release: N/A When were the last committers or PMC members elected? Entered incubation 2014-11-24. There have been comments/messages/ subscriptions on the mailing lists from folks not on the initial contributors list. We believe there is a good opportunity to bring on more folks from a more diverse base fairly quickly. Signed-off-by: [X](nifi) Billie Rinaldi [X](nifi) Arvind Prabhakar [X](nifi) Sergio Fernández [X](nifi) Benson Margulies [X](nifi) Drew Farris [ ](nifi) Brock Noland [X](nifi) Andrew Purtell -------------------- Ripple Ripple is a browser based mobile phone emulator designed to aid in the development of HTML5 based mobile applications. Ripple is a cross platform and cross runtime testing/debugging tool. It currently supports such runtimes as Cordova, WebWorks and the Mobile Web. Ripple has been incubating since 2012-10-16. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The community recently discussed the lack of growth in the project. Some members felt that retirement of the podling was appropriate. Others have stepped up to take over essential tasks and attempt to build a community. We have agreed with mentors to review this situation in 6 months. It is possible that Ripple is no longer important as its functionality is potential being replaced by Cordova-browser. Our original champion, Ross Gardler has also up to help evaluate the situation. For Cordova-browser idea, there was also a discussion on the mailing list. How has the community developed since the last report? No new committers since last June 2014. How has the project developed since the last report? Minor user contributions. Date of last release: No release made as yet, this will be the first item to receive attention. When were the last committers or PMC members elected? June, 2014. Signed-off-by: [ ](ripple) Jukka Zitting [X](ripple) Christian Grobmeier [ ](ripple) Andrew Savory Shepherd/Mentor notes: Report is past due already, and no releases has been made since incubation. Email/Code both not quite active, has concerns about inactivement and retirement for few months already. -------------------- Sentry Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop cluster. Sentry has been incubating since 2013-08-08. Three most important issues to address in the move towards graduation: 1. Continue to grow the Sentry community 2. Initiate graduation discussion with community and address any potential concerns raised 3. Update project status page, website etc 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 is growing. Several new members have started actively contributing to the project. New contributors made a significant contribution in patches as well as release activity. The user group meetup at NYC was well attended. Community members presented Apache Sentry at various community meetups around the world, include Hadoop group meetup in Hydrabad, India and ApacheCon Europe in Budapest, Hungary How has the project developed since the last report? A number of new features implemented in the master codeline. The sentry community is working towards removing some of the non Apache dependencies in order to avoid any potential concerns for the graduation processes. Date of last release: 2014-08-19 When were the last committers or PMC members elected? Arun Suresh and Tuong Truong have been added as a committer as announced on 9/1/2014. No new PPMC members have been added since the project has entered the incubator. Signed-off-by: [ ](sentry) Arvind Prabhakar [ ](sentry) Joe Brockmeier [ ](sentry) David Nalley [ ](sentry) Olivier Lamy [X](sentry) Patrick Hunt [ ](sentry) Thomas White -------------------- Streams Apache Streams (incubating) is a lightweight (yet scalable) framework for ActivityStreams. Streams has been incubating since 2012-11-20. The project provides a framework for abstracting away individual data schemas and API protocols from solutions built to collect, publish, process, and analyze digital activity data, as well as a community- driven process for determining best practice usage of the ActivityStreams specification with real-world datasets - valuing working, tested, adaptable, useful code over strict adherence to existing specs. Importantly, the project does not impose one execution framework - modules built to Apache Streams interfaces and coding standards may be instantiated within multiple JVM-based runtime containers, including popular ‘big-data' frameworks. Three most important issues to address in the move towards graduation: 1. Establish and maintain a consistent release process. 2. Improve quality of code, tests, documentation, and examples. 3. PPMC must relieve project mentors of all responsibility for the project's adherence to the Apache Way and long-term viability. 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? Ryan Ebanks was voted in as committer and PPMC member on 10-17-2014. How has the project developed since the last report? Since the last report, 50 pull requests were submitted and merged to master, 43 issues were marked resolved, and 78 issues were created. Date of last release: streams-master:0.1-incubating Jan-2013 incubator-streams:0.1-incubating in progress, ETC Dec-2014 When were the last committers or PMC members elected? Ryan Ebanks, committer and PPMC, 10-17-2014 Signed-off-by: [ ](streams) Matt Franklin [X](streams) Ate Douma [ ](streams) Craig McClanahan -------------------- Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important issues to address in the move towards graduation: 1. Project web site must be setup (ongoing). 2. Establish a collaboration model within the community and ensure a common view on the main focus points. 3. Improve code base for being ready for a first release around Q1 2015. 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? Many of the committers have successfully filed the ICLA and also started to contribute, some of them already by doing first patches. Feedback in the community was overwhelming. We could also successfully place the topic at conferences as well as in the German Java Magazin and other events. Also interest of people during the Zurich Hackergarten in November was great and will definitely lead to additional committers early 2015. How has the project developed since the last report? The project setup is going quite well. Initial committers are onboarding, the initial code donation was successfully moved and other preconditions like the project name, IP clearance, Jenkins etc. were successfully done. Thanks to INFRA for their incredible support! Date of last release: Still getting started. When were the last committers or PMC members elected? Still getting started. Signed-off-by: [x](tamaya) John D. Ament [ ](tamaya) David Blevins [ ](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek Shepherd/Mentor notes: Justin Mclean - Off to a good start. Email list and mentors active. -------------------- 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. IP clearance to be signed by Univ of Manchester 2. Move source code, wiki, issues to apache.org. Restructure git repos. 3. Invite contributors who volunteered at October workshop Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Infrastructure bootstrapping takes a long time and requires a series of requests. E.g. Taverna incubator has been approved, but does not get a web-site without explicitly asking for it. Documentation for apache.org infrastructure assumes you are already a long-term committer. How has the community developed since the last report? Transition of mailing list successful (? - can we get some numbers?). Most of the proposed initial committers have sorted CLAs https://wiki.apache.org/incubator/TavernaProposal#Initial_Committers and received apache.org account - see https://people.apache.org/committers-by-project.html#taverna Many of the remaining initial committers have not been active in the recent years. We're following up these (and others) through private conversations. There's been some confusion with regards to the term "committer" - some were scared and thought it meant they had to make a commitment to work on the source code! Not much further development - worried that dev@taverna are scared away by the long-dragged bootstrapping which dominates the list. How has the project developed since the last report? Source code is being restructured at https://github.com/taverna-incubator before being staged to import into git.apache.org Normal development continues at https://github.com/taverna/ - due to prepare the final 2.5.1 non-Apache release. Stian Soiland-Reyes was at ApacheCon in Budapest, fruitful discussions with mentor Andy Seaborne and Gavin McDonald from INFRA with regards to the transitioning of Taverna's existing source code repository, wiki and issue tracker (luckily git->git, confluence->confluence and jira->jira). Date of last release: No release since incubation. When were the last committers or PMC members elected? No new committers or PMC members elected since incubation. Signed-off-by: [x](taverna) Andy Seaborne [ ](taverna) Chris Mattmann [ ](taverna) Suresh Srinivas [x](taverna) Suresh Marru [x](taverna) Marlon Pierce Shepherd/Mentor notes: As noted the email list just been migrated and code repo setup, but already show good signs of activity on the email list. Code activity seems good so far although it's still on it's own github repo. -------------------- 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. Making release. 2. Growing community. 3. Source fixes/improvements. 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? After some spike in activity we had a slowdown. How has the project developed since the last report? Some improvements were committed like full text search with Solr and some more need to be reviewed/merged. We are working on making an updated RC and plan to hold review/voting soon. Date of last release: not yet. When were the last committers or PMC members elected? No Signed-off-by: [X](wave) Christian Grobmeier [ ](wave) Upayavira ----------------------------------------- Attachment AD: Report from the Apache Jackrabbit Project [Michael Dürig] 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 Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following maintenance releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 1.0.6 on September 25th * Apache Jackrabbit Oak 1.0.7 on October 14th * Apache Jackrabbit Oak 1.0.8 on November 4th We made the following unstable release from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 1.1.0 on October 6th * Apache Jackrabbit Oak 1.1.1 on October 13th * Apache Jackrabbit Oak 1.1.2 on November 10th We made the following release from the Jackrabbit FileVault sub project: * Apache Jackrabbit FileVault 3.1.8 on October 27th o Community / Development * No new committers or PMC members joined the Jackrabbit team since June 2014. * .adaptTo() Berlin in September and ApacheCon EU Budapest in November featured sessions on Jackrabbit Oak. ----------------------------------------- Attachment AE: Report from the Apache Karaf Project [Jean-Baptiste Onofré] Apache Karaf provides higher level features and services specifically designed for creating OSGi-based servers. Community ========= Three talks have been given during ApacheCon EU: - Enterprise Development with Apache Karaf - Best Practices for Design and Development of OSGi Applications in Apache Karaf and a tutorial - Application Integration in OSGi on Apache Karaf A talk and workshop has been given during latest JUG Barcelona. Last committer addition: October 21, 2013 Last PMC addition: September 05, 2012 Development =========== A plan to have a periodically release cycle has been proposed and we move forward to follow this plan. The following new releases have been voted: - Apache Karaf Cellar 2.3.3 (maintenance release) (November 17, 2014) - Apache Karaf 2.3.9 (maintenance release) (November 9, 2014) - Apache Karaf 4.0.0.M1 (technical preview release) (October 14, 2014) - Apache Karaf 3.0.2 (maintenance release) (October 13, 2014) - Apache Karaf 2.4.0 (maintenance release) (September 20, 2014) - Apache Karaf 2.3.8 (maintenance release) (September 19, 2014) - Apache Karaf 2.3.7 (maintenance release) (September 6, 2014) Issues for board consideration ============================== None so far. ----------------------------------------- Attachment AF: Report from the Apache Labs Project [Tim Williams] ----------------------------------------- Attachment AG: Report from the Apache Lucene Project [Mark Miller] The Apache Lucene project develops open-source search software. TLP --- We added one new committer in the last quarter: Gregory Chanan Lucene Core and Solr -------------------- Lucene Core is a search-engine toolkit. Solr is a search server built on top of Lucene Core. In the last quarter we made two releases of both Lucene Core and Solr: - 4.10.1 on 29 Sept 2014 - 4.10.2 on 31 Oct 2014 We have also started the process for a 4.10.3 release. The community is very active. Security: There was one security issue reported: - An XXS vulnerability was reported against Apache Solr (CVE-2014-3628). An attacker could inject javascript that is executed via the admin ui because stored queries are not escaped / sanitized. This will be addressed in the upcoming 4.10.3 release that is currently being voted on. PyLucene -------- PyLucene is a Python integration of Lucene Java. Development is almost entirely an automated port, so this project will never require a lot of developers. The user community is active. In the last quarter we made one release of PyLucene: - 4.10.1-1 on 6 Oct 2014 ----------------------------------------- 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 == The PMC has recognized we have become stagnant and have not had a release in two years. We are actively working towards rebuilding and re-invigorating the community. Cleaning up our PMC processes: - We realized several PMC members were not on the private mailing list - There was a typo in the moderation account for the mailing list that wasn't realized - We had a roll call and all PMC members are now present and accounted for - Last PMC Member Added, Paul Irwin, October 2013 Working on our community / tooling: - We're actively brainstorming how to create better documentation around getting started with Lucene.Net as a developer, and getting invovled as a committer - With the help of our community members and some free licensing, we are in the process of setting up a CI system for our tests - We're looking at possibly pulling in questions from stackoverflow to the mailing list to expand visibility of those questions to the mailing list and hopefully spur conversation (SO questions look like 1 per 1-2 days or so at most) - Looking at a website refresh to go along with the documentation Pushing hard on 4.8.0. - We were provided a contribution from MSFT over the summer of a significant code port of the 4.8.0 Java code. We have been working to clean that up. Currently we have 300 failing tests to fix, as well as some additional libraries that help users make the most of Lucene.Net (encoding codecs and contrib extensions) We could use any advice or assistance on the above to help us build / rebuild our community. == Releases == Last Release 3.0.3 - Oct 2012 Working toward 4.8.0 == Statistics == Nuget package downloads: Lucene.Net 3.0.3: 106720 Lucene.Net Contrib 3.0.3: 29343 Lucene.Net Contrib Spatial: 3987 Lucene.Net Contrib Spatial.NTS: 980 ----------------------------------------- Attachment AI: Report from the Apache MetaModel Project [Kasper Sørensen] Apache MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Releases: * November 24th, 2014: MetaModel 4.3.0-incubating Statistics: * Last committers added: 2014-10-14 (Alberto Rodriguez) * Last PMC members added: 2014-11-20 (When the project graduated) * Mailing list activity for last 3 months: 426 messages * Mailing list subscribers: 55 * Commits the last 3 months: 51 Activity: * October and November was active months with increased commits, a release and graduation from Apache Incubator. * We are finishing the process of migrating from Incubator infrastructure to TLP infrastructure. * Website, Mailing List, Git repository has been migrated to TLP namespace. * The website was updated with a "news" section and an updated splash image. * Working with Apache press team to make press release about our graduation. * There is an experimental module/connector for Neo4j in the works, initiated by Tomasz Guzialek. ----------------------------------------- Attachment AJ: Report from the Apache MRUnit Project [Brock Noland] ----------------------------------------- Attachment AK: Report from the Apache OFBiz Project [Jacopo Cappellato] Apache OFBiz is an open source product for the automation of enterprise processes that includes framework components and business applications for Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), E-Business / E-Commerce, Supply Chain Management (SCM), Manufacturing Resource Planning (MRP). We have no issues that require Board assistance at this time. *Releases* * Apache OFBiz 11.04.06 has been released in September 2014; this is the last release of the 11.04 series * Apache OFBiz 12.04.05 has been released in September 2014 * Apache OFBiz 13.07.01 has been released in October 2014 *Community and Project* * new committers: Nicolas Malin (nmalin) is a new committer since September 2014 * new PMC members: Sharan Foga (sharan), has been elected in the PMC in September 2014 * mailing list traffic and commit rates are steady with significant activity in the enhancement of documentation * ApacheCon EU Budapest has been a successful event for the OFBiz project; six sessions have been presented covering a range of business and technical topics: ** "What Business Users See and Want" by Sharan Foga, PMC (Czech Republic) ** "Brewing with Apache OFBiz - A Case Study" by Pierre Smits, contributor (The Netherlands) ** "Introduction To A Groovy Based DSL For Apache OFBiz" by Jacopo Cappellato, PMC (Italy) ** "Gui Unit Test For Apache OFBiz" by Olivier Heintz, contributor (France) ** "Apache OFBiz Infra Task Automation For Deployment And Hosting" by Nicolas Malin, committer and Gil Portenseigne, contributor (France) ** "Introduction To A Recommender System For Apache OFBiz" by Anahita Goljahani, contributor (Italy) *Infra/Legal* We have no issues that require Board assistance. ----------------------------------------- Attachment AL: Report from the Apache Olingo Project [Christian Amend] Apache Olingo is an effort to provide an implementation of the OASIS OData (Open Data) specification in Java, and JavaScript (and possibly other languages). The project has graduated in April 2014. Releases: The latest OData V2 compliant Java release is version 2.0.1 and was built on 2014-11-06. The latest OData V4 compliant Java release is version 4.0.0-beta-01 and was built on 2014-09-23. The latest OData V4 JavaScript release is version 4.0.0-beta-01 and was built on 2014-09-19. Overall Activity: The main focus of the Olingo community right now is the OASIS OData 4.0 standard. There have been beta releases for Java and JavaScript. The maintenance for the OData V2 standard is still ongoing and resulted in a first patch release. The mailing lists and Jira show a strong increase in traffic after the first beta releases for OData V4. We hope this increase in interest will help the Olingo community to grow. Community: Stephan Klevenz resigned as the VP of Olingo and the Olingo community elected Christian Amend as the new VP on 2014-10-06. The Olingo community elected Sven Kobler-Morris as a new PMC member on 2014-10-06. The Olingo community elected Ramesh Reddy as a new committer on 2014-11-07. ----------------------------------------- Attachment AM: Report from the Apache OODT Project [Sean Kelly] DESCRIPTION Apache OODT is a software framework as well as an architectural style for the rapid construction of scientific data systems. It provides components for data capture, curation, metadata extraction, workflow management, resource management, and data processing. RELEASES/DEVELOPMENT • OODT-0.7 on 2014-09-19 • OODT-0.6 on 2013-07-17 • OODT-0.5 on 2012-12-25 We resolved 26 issues in JIRA [1] since the release of OODT-0.7 and look forward to including these in OODT-0.8. Our development mailing lists remain popular, while the user list shows less activity. The table below lists the number of postings by list, by month, in Q4 2014: List Oct Nov Dec ---- --- --- --- dev 177 348 7 user 2 14 0 COMMUNITY Latest committers and PMC members: • Angela Wang (angela_wang) on 2014-11-07 as committer and PMC member • Valerie Mallder (vmallder) on 2014-11-25 as committer and PMC member PRESS OODT PMC Member Michael Starch (starchmd) spoke at NASA JPL's "Spark Day" event where he presented a concept that integrates Apache OODT with Apache Spark, Apache Mesos, Apache Hadoop, and Apache Kafka. Materials presented are available at the OODT wiki [2]. [1] https://issues.apache.org/jira/browse/OODT [2] https://cwiki.apache.org/confluence/display/OODT/Streaming+OODT ----------------------------------------- Attachment AN: Report from the Apache OpenJPA Project [Pinaki Poddar] == Summary == Apache OpenJPA is a persistent object management kernel for relational and non-relational databases. For relational database, OpenJPA provides persistence for Plain Old Java Object (POJO). OpenJPA is compliant to industry-standard Java Persistence Architecture (JPA) version 2.0 version and runs in stand-alone JSE as well as JEE containers and many other lightweight frameworks, such as Tomcat, TomEE, Spring or OSGi. == Community == OpenJPA developers had, over past several years, not only developed a general-purpose, stable software for complex Object-Relational Mapping but also ensured its stability across many released versions. OpenJPA has a solid user base and many have migrated their persistence provider to OpenJPA from more well-known provider in the past. Current OpenJPA developer/committers actively maintain the code base as well as support via the mailing list users and the code service streams. However, developer resource is shrinking as many senior committers are not active and new volunteers are hard to come by as new development opportunities are rare and hard to incorporate. Also lack of strong corporate interest/sponsorship is affecting future growth/expansion of the community. PMC members are exploring how to invigorate the project. We hope that the Board members may be able to share their experience on how to re-energize a matured project in its maintenance phase of life. == Recent Work == OpenJPA development team member Jody Grassel has upgraded Serp bytecode library to version 1.15 for Java 8 language features (e.g. lambda expression) and integrated OpenJPA with the upgrade. As OpenJPA natively uses bytecode enhancement, supporting Java 8 has more than usual impact on OpenJPA. Many requests have been received for upgrade to JPA 2.1 compliance. Prototype work for supporting JPA 2.1 features such as Store Procedure support has started. == Issues == One of the nightly builds (2.3.1) artifact is missing [1] in the repository. The issue is likely to be an infrastructure issue and is being tracked by [2] [1] https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.3.1-SNAPSHOT/ [2] https://issues.apache.org/jira/browse/OPENJPA-2537 ----------------------------------------- Attachment AO: Report from the Apache OpenNLP Project [Joern 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 stayed active over the last 3 month and the release is finally prepared. William Colen was elected as Release Manager and published the first release candidate for testing. Community --------------- The community stayed active with the usual amount of traffic on the user mailing list. There are no new PMC members. Mark Giaconia was added as a committer in October 2013 and is active since then. Releases ------------ The last release OpenNLP 1.5.3 was released on 15.4.2013. Issues -------- There are no board-level issues at this time. ----------------------------------------- Attachment AP: Report from the Apache OpenWebBeans Project [Mark Struberg] Apache OpenWebBeans 1.x is an ALv2-licensed implementation of the "Contexts and Dependency Injection for the Java EE platform" specification which is defined as JSR-299 (CDI-1.0). OpenWebBeans 1.5.x also implements the CDI-1.1 and CDI-1.2 (MR) specifications(JSR-346) We will later also also implement CDI-2.0 (JSR-365) as OpenWebBeans-2.0.x. Board Issues There are no issues requiring board attention this time. Development Development continues in trunk to implement CDI 1.2 as OpenWebBeans-1.5.x. We are finished with the SE parts and fully pass this TCK. We continue working with the Apache TomEE team to also pass the EE part of the CDI-1.2 TCK. Members of the community also actively contribute to the CDI-2.0 JavaEE specification (ALv2 licensed) which has been filed as JSR-365. New Releases OpenWebBeans-1.2.7 on 2014-12-09 We still have to upload to our dist after the SVN outage. We are also preparing to release owb-1.5.0-alpha-1 this month. Discussions. Nothing which requires board attention. Community Community activity is fine. Last Committer: Reinhard Sandtner on Sept 23th, 2014 Last PMC addition: Thomas Andraschko and Jean-Louis Monteiro on 2014-05-28 ----------------------------------------- Attachment AQ: Report from the Apache Perl Project [Philippe M. Chiasson] -- mod_perl 1.0 -- The mod_perl 1.x is a maintenance track designed to work with httpd 1.3.x. No new mod_perl 1.x releases since 2014-07 --- mod_perl 2.0 -- mod_perl 2.X is designed to work with all httpd 2.X branches. The work to support the 2.4 branch has finally been fully merged back on trunk, with the remaining few little issues mostly ironed out. 2 PMC members have already volunteered to be release managers for the next release. With the holiday period coming fast, I expect to see the first RCs coming out in early January. --- Apache-Test -- Apache-Test provides a framework which allows module writers to write test suites than can query a running mod_perl enabled server. It is used by mod_perl, httpd and several third party applications, and includes support for Apache modules written in C, mod_perl, PHP and Parrot. No new Apache-Test releases since 2014-07. --- Apache-SizeLimit -- Apache-SizeLimit is a popular component in most mod_perl production environments. It is used to kill off large httpd child processes based on various environmental triggers. Apache-SizeLimit 0.97 was released on Apr 02, 2012 No new Apache-SizeLimit releases since 2014-07. --- Apache-Bootstrap -- Apache-Bootstrap is a framework to make it easier to build perl module distributions for different mod_perl versions. It encapsulates code developed over the years by mod_perl developers to make maintaining Apache::* and Apache2::* modules in the same distribution easy. Apache-Bootstrap 0.07 was released on Jul 13, 2009 No new Apache-Bootstrap releases since 2014-07. --- Apache-Reload -- Apache-Reload is a popular component in most mod_perl development environments, used to refresh compiled code in the perl interpreter without completely restarting httpd. Apache-Reload 0.12 was released on March 31st, 2012 No new Apache-Reload releases since 2014-07. -- Apache-DBI -- Apache-DBI is a popular component in many mod_perl deployments. It is used to provide transparent database connection pooling to clients using DBI. Apache-DBI 1.12 was released on June 12th, 2013 No new Apache-DBI releases since 2014-07. -- Development -- mod_perl continues to be a healthy development community, though as a mature and stable product development moves at a naturally slower pace than in years past. Bugs are found and discussed and applied with due consideration for our production userbase. Work on the httpd-2.4 branch has come to a standstill, as all work on that branch completed and was merged into the trunk. -- Users -- The mod_perl users list is seeing little activity, except for the occasional obscure bug report, or general user questions. Patches and bug reports are few, but keep on coming. -- PMC -- No noteworthy PMC events happened since the last report. ----------------------------------------- Attachment AR: Report from the Apache Pig Project [Cheolsoo Park] Description: Pig is a platform for analyzing large data sets that consists of a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. The salient property of Pig programs is that their structure is amenable to substantial parallelization, which in turns enables them to handle very large data sets. Releases: * 0.14.0: released in Nov 2014 that includes several new features as follows: ** Pig on Tez ** OrcStorage ** Loader predicate push down ** Constant calculation optimization Community: * 424 subscribers to the dev mailing list (420 in the last report) * 1159 subscribers to the user mailing list (1163 in the last report) * The PMC has 15 members and the project counts 6 additional committers ** No new committer ----------------------------------------- Attachment AS: Report from the Apache Pivot Project [Roger Whitcomb] Apache Pivot is a 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. Status: Project activity has been very slow this quarter -- very little user mailing list (only 6 postings). Some development activity, and discussions about the next (2.0.5) release, which we expect sometime in the next quarter. There are some questions about Pivot on StackOverflow lately, which show some interest. There were 5 issues created in JIRA, and 7 resolved during the quarter. Board Issues: None that I know of. Releases: Last release was 2.0.4, published 19-May-2014. Branding/Naming issues: None. Legal issues: None. Infrastructure Issues/Needs: The migration of Apache-Extras has gotten some attention again, which I have been following. Community: Last Committer Piotr Kolaczkowski (pkolaczk) was created 09 May 2012. Latest PMC Changes: Greg Brown (gbrown) went Emeritus on 10 Sept 2013, Martijn Dashorst (dashorst) went Emeritus in July 2012. ----------------------------------------- Attachment AT: Report from the Apache POI Project [Yegor Kozlov] Apache POI is a Java library for reading and writing Microsoft Office file formats. Releases -------- There were two releases in the last quarter: POI 3.10.1 on 18 August 2014 POI 3.11-beta3 on 11 November 2014 The release vote on 3.11 final is in progress and we are hoping to push it on the mirrors within a week. Community --------- No new committers/PMC members added in the last quarter. Last committer and PMC was added in December, 2013 (kiwiwings) Project Status --------- Apache POI continues to be an active project, both in terms of community and development. Traffic on the mailing lists has been steady in the last 3 months. Most patches are applied without much delay. General Comments ---------------- There are no issues that require Board attention. ----------------------------------------- Attachment AU: Report from the Apache Portals Project [David Sean Taylor] Apache Portals is a project for building freely available and interoperable portal software. 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. Releases: Delayed releasing Jetspeed 2.3.0, 2.2.3, and APA WebContent-2 until next quarter March 6, 2013 - Portals Apps Web Content 1.3 October 10, 2011 - Portals Jetspeed 2.2.2 26 September 2011 - Portals Pluto 2.0.3 Committer/PMC: None Security updates: None Community update: Pluto team has implementing Portlet 3.0 TCK (Test Compatibility Kit and Portlet 3.0 RI Pluto team is now actively working on Portlet API 3.0 Implementation and Portlet Hub Apache Portals Web Content has been rewritten and should be released next quarter ----------------------------------------- Attachment AV: Report from the Apache ServiceMix Project [Gert Vanthienen] 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. Project Status: 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 and Apache Camel. Activity on the mailing lists and in JIRA has been a bit slow, but we did manage to stick to a steady release schedule and get a few new releases out. Apart from the maintenance releases on the 5.0.x and 5.1.x branches, we also released a new 5.3.0 version. There are no outstanding issues requiring board attention. Community: No changes since the last board report. Last committer (Wim Verreydt) and PMC member (Krzysztof Sobkowiak) additions were in July 2014. Community Objectives: We're not expecting any more dependency updates to become available for the 5.0.x branch, but we do plan to keep our release schedule going with the 5.1.x and 5.3.x releases. We're also working towards further 5.x releases and a 6.0.0 release to provide our users with major version upgrades of Karaf, Camel, CXF, ... Releases: - A set of 128 bundles in September - Apache ServiceMix 5.0.4 in September - Apache ServiceMix 5.1.2 in September - Apache ServiceMix 5.0.5 in October - Apache ServiceMix 5.1.3 in October - Apache ServiceMix 5.3.0 in October - A set of 65 bundles in October - Apache ServiceMix 5.0.6 in November - Apache ServiceMix 5.1.4 in November - A set of 282 bundles in November ----------------------------------------- Attachment AW: Report from the Apache Shiro Project [Les Hazlewood] Apache Shiro is a powerful and flexible open-source application security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. We have no issues that require Board assistance at this time. Releases: - No new releases since our previous 1.2.3 bugfix release on 25 February 2014. A 1.3 release may be possible as an interim before 2.0, but development work last quarter has targeted the 2.0 branch. Community & Project: - Mailing list traffic remains steady compared to last quarter. - Efforts towards a 2.0 distribution remain active on a separate dev branch. Changes are ongoing, and we hope to make a 2.0 release Q1 2015. Last PMC Member voted in: Brian Demers on 20 May 2013 Last committer voted in: Jared Bunting on 29 Jul 2012 ----------------------------------------- Attachment AX: Report from the Apache Sling Project [Carsten Ziegeler] Apache Sling is an OSGI-based scriptable web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. There are no issues which require board attention at the moment. Community Good activity level overall, contributions from different people continue. Three new committers: Marius Petria, Konrad Windszus and Julian Sedding, no new PMC members. Last PMC change was in June 2014 with six new PMC members elected. Releases - Apache Sling Auth Core 1.3.4 (December 2nd, 2014) - Apache Sling Resource Merger 1.2.0 (November 29th, 2014) - Apache Sling Resource Resolver 1.1.8 (November 27th, 2014) - Apache Sling Servlets Resolver 2.3.6, and Apache Sling Engine 2.3.10 (November 18th, 2014) - Apache Sling Servlets Resolver 2.3.4 (November 14th, 2014) - Apache Sling Eventing 3.4.4 (November 7th, 2014) - Apache Sling Scripting JSP 2.1.6 (November 6th, 2014) - Apache Sling Slingstart Maven Plugin 1.0.2 (November 5th, 2014) - Apache Sling Event 3.4.2 (November 1st, 2014) - Apache Sling Engine 2.3.8, Apache Sling Provisioning Model 1.0.0, and Apache Slingstart Maven Plugin 1.0.0 (October 27th, 2014) - Apache Sling JCR Resource Resolver 2.3.12 (October 26th, 2014) - Apache Sling Eventing 3.4.0, and Apache Sling Distributed Event Admin 1.0.0 (October 24th, 2014) - Apache Sling JCR Resource Resolver 2.3.10 (October 22nd, 2014) - Apache Sling Auth Core 1.3.2, Resource Resolver Mock 1.0.0, JCR Mock 1.0.0, OSGi Mock 1.0.0, Sling Mock 1.0.0, Sling Mock Jackrabbit 0.1.0 (October 21st, 2014) - Apache Sling IDE Tooling 1.0.4 ( October 18th, 2014) - Apache Sling Settings 1.3.4, Apache Sling Discovery API 1.0.2, and Apache Sling Discovery Impl 1.0.12 (October 10th, 2014) - Apache Sling Resource Resolver 1.1.6 (October 4th, 2014) - Apache Sling Superimposing Resource Provider 0.2.0, and Apache Sling 7 (October 3rd, 2014) - Apache Sling Scripting Java 2.0.12 (September 30th, 2014) - Apache Sling Resource Resolver Mock 0.3.0 (September 29th, 2014) - Apache Sling Resource Resolver 1.1.4 (September 26, 2014) - Apache Sling JSP Taglib 2.2.4 (September 25, 2014) - Apache Sling DavEx Access to repositories 1.2.2, and Apache Sling Adapter Manager Implementation 2.1.2, - Apache Sling Scripting Core implementation 2.0.28 (September 22nd, 2014) - Apache Sling JCR ContentLoader 2.1.0, and Apache Sling Web Console Security Provider 1.1.4 (September 21st, 2014) - Apache Sling Resource Access Security 1.0.0, and Apache Sling Auth Core 1.3.0 (September 20th, 2014) - Apache Sling Engine 2.3.6, Apache Sling JCR ClassLoader 3.2.2, - Apache Sling JCR Jackrabbit Access Manager 2.1.2, and Apache Sling JCR Jackrabbit Server 2.2.0, - Apache Sling JCR Jackrabbit User Manager 2.2.2, and Apache Sling JCR Registration 1.0.2, - Apache Sling JCR Web Console 1.0.2 (September 19th, 2014) - Apache Sling Scripting Thymeleaf 0.0.4 (September 17th, 2014) - Apache Sling Resource Resolver 1.1.2 (September 16th, 2014) - Apache Sling Maven Launchpad Plugin 2.3.2 (September 15th, 2014) - Apache Sling Filesystem Resource Provider 1.1.4, and Apache Sling Launchpad Content 2.0.8, - Apache Sling JSP Tag Library 2.2.2, and Apache Sling Scripting Groovy Support 1.0.0 (September 12th, 2014) Documentation and infrastructure Nothing to report Project Branding is tracked in SLING-2696. ----------------------------------------- Attachment AY: Report from the Apache SpamAssassin Project [Kevin A. McGrail] Description ----------- SpamAssassin is a mail filter to identify spam. It is an intelligent email filter which uses a diverse range of tests to identify unsolicited bulk email, more commonly known as Spam. These tests are applied to email headers and content to classify email using advanced statistical methods. In addition, SpamAssassin has a modular architecture that allows other technologies to be quickly wielded against spam and is designed for easy integration into virtually any email system. Releases -------- 3.4.0 was released on 2014-02-11. Our rules releases have continued and with 73 rule sets published since the last quarterly report. The first release candidate for 3.4.1 was created today on Dec 16th. Community & Development ----------------------- The most recent addition to our PMC is Adam Katz added on 2013-01-30. The most recent addition to the committers is Joe Quinn added on 2014-02-27. The community has started the process to revive the SOUGHT rules project However, we do not have any new people moving moving towards committer but do have commits and rules being discussed and passed through to current committers to vet and apply showing good community development health. Our RuleQA dev list has been active and community support is good. The project users' list is active; questions get asked and answered. The project dev list has been active with both committers and community members contributing. We still need to get our Jenkins build slave working under FreeBSD instead of Solaris1 (Bug 6887). https://builds.apache.org/job/SpamAssassin-trunk/ is offline and not working. We are preparing to deprecate the zones2 server. Thanks to Infra for the work on the SVN recovery! Project Branding Requirements ----------------------------- IN PROCESS - Logos and Graphics : include TM, use consistent product logo on your site NOTE: Will announce the new logo along with the powered by logo. Planned with 3.4.1 release. Committee Record Review ----------------------- We compared http://svn.apache.org/repos/asf/spamassassin/trunk/CREDITS to https://svn.apache.org/repos/private/committers/board/committee-info.txt and no discrepancies were found. Issues ------ No further issues. ----------------------------------------- Attachment AZ: Report from the Apache Stanbol Project [Fabian Christ] Apache Stanbol provides a set of reusable components for semantic content management. There are no issues which require board attention at the moment. The project is performing well and the development is going towards version 1.0. Some minor tasks are still to do. In the meantime the project is preparing a 0.12.1 maintenance release. The Stanbol project has participated at the ApacheCon EU with a talk by Rupert Westenthaler about a possible new annotation model for Apache Stanbol [1, 2 (slides)]. In this context Stanbol was offered the possibility to send a member to the W3C group working on Open Annotation. [1] http://s.apache.org/AwS [2] http://s.apache.org/CUX Subscribers on the dev list: 217 No new committers or PMC members were elected. Last new committer was Antonio David Perez Morales on Jan 14th, 2014 No new PMC member was elected since the graduation of Apache Stanbol on Sep 19th, 2012. Last stack release was: Apache Stanbol 0.12 on Mar 2nd, 2014 Last component release was: Apache Stanbol Partial Security Release RC2 on June 5th, 2014 org.apache.stanbol.commons.security.reactor-20140602 ----------------------------------------- Attachment BA: Report from the Apache Storm Project [P. Taylor Goetz] DESCRIPTION APACHE Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. CURRENT ACTIVITY * Version 0.9.3 has been released. This was the first release as a top-level project. The Storm incubator distribution area has been cleaned up as required. * The developer and user lists continue to be active, and JIRAs are being created and addressed. * Development activity continues on version 0.10 which will be the next major release (AKA the “security” release). RELEASES * The last release of Apache Storm was version 0.9.3, released on November 25, 2014. This was the first release as a TLP. COMMUNITY * Storm added 4 PMC/Committer members on September 27, 2014 (Note: These members were voted in during incubation, and added as PMC members post- graduation via board NOTICE). * There were no new additions to the PMC since the last report. ISSUES * There are no issues requiring board attention at this time. ----------------------------------------- Attachment BB: Report from the Apache Synapse Project [Hiranya Jayathilaka] Apache Synapse is a high performance, flexible, lightweight Enterprise Service Bus (ESB) and a mediation framework. Community ========= No new committers or PMC members were nominated this quarter. Latest Synapse committer was elected on December, 2013. Latest Synapse PMC member was elected on December, 2013. Releases ======== There have been no new releases during this period. The last release of Synapse is version 2.1, which was released on January, 2012. Our release process is still blocked by the absence of a compatible Apache Axis2 release. After our last board report, it was suggested that we consider the option of contributing our time and effort into Axis2, so we can get it released. This proposal was sent to our mailing list for discussion but it hasn't garnered a positive response from the Synapse community. I believe that the above proposal is based on the premise that at some point in the past, both Axis2 and Synapse projects were maintained by more or less the same people. But to my understanding these committers are no longer active in either project. Currently active Synapse committers were all voted in within the last three years, and they are not Axis2 experts. And so far they haven't shown any interest in actively working on the Axis2 project. As it stands now, we prefer to treat Axis2 as yet another external dependency on which we can develop Synapse code. To get around this hurdle, we have been looking into the possibility of branching the current Axis2 trunk and doing a Synapse-specific release (current Axis2 trunk is stable enough for our purposes). But this option also poses some challenges due to the long dependency chain of Synapse and Axis2. As it turns out we also need releases from several other projects such as Axiom, WSS4J and XmlSchema. However, so far this is the only option that has succeeded in gathering any kind of momentum in the Synapse dev community. Therefore, we will continue to explore this idea. Board issues ============ None identified, although any feedback on how to handle the above mentioned release problem will be much appreciated. ----------------------------------------- Attachment BC: Report from the Apache Tajo Project [Hyunsik Choi] Apache Tajo is a robust big data relational and distributed data warehouse system for Apache Hadoop. Tajo is designed for low-latency and scalable ad-hoc queries, online aggregation, and ETL (extract-transform-load process) on large-data sets stored on HDFS (Hadoop Distributed File System) and other data sources. By supporting SQL standards and leveraging advanced database techniques, Tajo allows direct control of distributed execution and data flow across a variety of query evaluation strategies and optimization opportunities. Board Issues ============= There are no outstanding issues requiring board attention. Current Activity ================ Recently, we are discussing 0.9.1 release (incremental release), including bug fixes and new features, such as HBase storage support, recap of timezone, and Hadoop dependency removal from TajoClient. For 0.9.1 release, we have resolved about 80 issues since last release in Oct 2014. Releases =============== - Apache Tajo 0.9.0 (major release) (October 21, 2014) - Apache Tajo 0.8.0 (major release) (May 1, 2014) The last committers or PMC members elected =========================================== Last new PMC member: Hyoung Jun Kim on 2014/12/08 Last new committer: Hyoung Jun Kim on 2014/08/06 ----------------------------------------- Attachment BD: Report from the Apache Tiles Project [Greg Reddin] ----------------------------------------- Attachment BE: Report from the Apache Tomcat Project [Mladen Turk] ----------------------------------------- Attachment BF: Report from the Apache Tuscany Project [Jean-Sebastien Delfino] ----------------------------------------- Attachment BG: Report from the Apache UIMA Project [Marshall Schor] 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: 23 Oct 2014 last release 12 Mar 2013 last PMC addition 24 Dec 2013 last Committer addition 2 Releases: 23 Oct 2014 UIMA-DUCC (Distributed UIMA Cluster Controller) 1.1.0 released http://uima.apache.org/news.html#23 October 2014 23 Sept 2014 UIMA Ruta (rule based scripting w/ Eclipse workbench) 2.2.1 released http://uima.apache.org/news.html#23 September 2014 Other Activity: A Youtube channel for UIMA was started, to post tutorials; you can see it here: https://www.youtube.com/channel/UC1YKyoL1W-xNHs9cv4U1V9g There are many other previous tutorials about UIMA on youtube, posted by various individuals, as well. Core UIMA is quite active, working towards a next release, which will include JSON serialization, in support of the trend toward Cloud deployments. The mailing lists are fairly active, and normal bug finding/fixing work continues. Community: The community continues to be active, with some new contributions coming in, including some video tutorials which were posted on Youtube. UIMA-DUCC is starting to get traffic on the email lists as users start using it. Issues: No Board level issues at this time. ----------------------------------------- Attachment BH: 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. CURRENT ACTIVITY * The next release of VCL was pushed back due to an underestimate of the amount of work remaining. We plan to create a release candidate next week. * Almost all of the development work is complete. Work is wrapping up to add NAT support and a few minor improvements. * After this release, we will work to improve how the project handles release planning and management. It has been a very long time since our last release (12/12). Some discussion has started in the thread referenced as [1]. RELEASES None COMMUNITY Subscribers to the user list: 162 Posts to user list, 9/14-11/14: 97 Subscribers to the dev list: 130 Posts to dev list, 9/14-11/14: 440 Committers: 8 PMC members: 7 ISSUES There are no issues requiring board attention at this time [1] http://vcl.markmail.org/thread/ejanbxnvtm2476mc ----------------------------------------- Attachment BI: Report from the Apache Whirr Project [Andrew Bayer] ----------------------------------------- Attachment BJ: Report from the Apache Wicket Project [Martijn Dashorst] Apache Wicket is a Java framework for creating highly dynamic, component oriented web applications. Things worthy of note: - 7.0.0-M4, 6.18.0 - Nutch Google Summer of Code delivered admin interface using Wicket - ApacheCon EU 2014 had 2 Wicket presentations and 1 isis presentation - Jesse Long was added as a committer and PMC member - New site discussions Date last committer/PMC member added: 28 September 2014 ApacheCon EU Martijn Dashorst presented 2 sessions at ApacheCon EU in Budapest: - Wicket and Java EE Sitting in a Tree - Apache Wicket: 10 Years and Beyond In the aftermath good discussions with committers of other projects arose, including Deltaspike and Isis. New website In the quest for a more 2014+ design for our current aging web site a lot of activity arose to craft a new site. The new site will be compliant with the branding guidelines. A preview can be found at http://dashorst.github.io/wicket-site One of the discussions focused on the addition of the "Fork me on Github" banner in the top right corner of every page. Community members want a prominent link to github because they claim it attracts contributions and because the tooling available at github is more aligned with current open source contributors. As Chair I voiced my concerns about linking to a non-sponsor, commercial entity in such a prominent place (even the foundation doesn't have such prominence). I find it rather difficult to convince my community members of why this is wrong. Somehow it does not compute that "Fork me on Github" is not a good message to send out and is in fact a big banner ad for github. In a discussion on board@ it seemed that some folks share my concerns whereas others rather give projects leeway in how they approach such links. The fact that both Project Thanks Pages and Product Support Pages specifically mention that such links should not (including added emphasis on the not) be (prominent) on the homepage, doesn't seem to hold much if any weight. Ultimately I removed the banner from the site. Having such a link on every page is (according to me) against ASF policy if not in writing at least in spirit (i.e. mark/linking policies). ----------------------------------------- Attachment BK: Report from the Apache Wink Project [Luciano Resende] ----------------------------------------- Attachment BL: Report from the Apache ZooKeeper Project [Flavio Junqueira] ZooKeeper is a reliable coordination service for distributed systems. We have released an alpha version of the 3.5 branch on Aug. 06, 2014. This release includes important features such as reconfiguration. It fixes a significant number of bugs and includes smaller improvements both in the server and client. The community is now focusing on the stability of the branch. There is also ongoing work to introduce SSL support. This is a feature that has been long awaited. No infrastructure issues: Community: * Mailing list activity hasn’t changed significantly. * 11 active committers representing 10 unique organizations. No change to the list of committers. *  9 active PMC members representing 8 unique organizations. No change to the list of PMC members. * 437 subscribers on dev (up from 435 last quarter). * 988 subscribers on user (up from 974 last quarter). * 2093 jira issues have been created to date (38 more since last quarter) ------------------------------------------------------ End of minutes for the December 17, 2014 board meeting.