Third Quarter, Fiscal Year 2018 (November 2017 - January 2018)
"The unbroken success of Apache still has important lessons to teach us... The Apache community has succeeded not just in developing great code, it has managed to distil the essence of the development process and ethos in such a way that other cognate projects can adopt and adapt it." --Glyn Moody, "Learning from The Apache Way"
> Conferences and Events: In the report period, the ASF did not conduct any events, and thus we have nothing to report. During this period, we investigated options for ApacheCon events in the 2018 calendar year. You can find details about those events at http://apachecon.com/ and in our upcoming Annual Report. At the close of this quarter, we were finalizing our plans for participation in FOSDEM http://fosdem.org/ .
> Community Development: During this quarter our main focus was participation in several existing Open Source related events. Our involvement was not only represented by talks and presentations but also by having a booth so that we could talk directly with conference attendees. In November, we participated at the FOSS Backstage Micro Summit, a new conference that focuses on Open Source communities, governance and legal aspects. These areas are very relevant to the community development effort and several Apache speakers were selected to be part of the program. Feedback was positive and we would like to continue being involved in this event in the future.
Following our participation last year at the OpenExpo in Madrid, we have been invited to participate again at the conference in 2018. This time we have been allocated a keynote and other presentation slots that will help us promote Apache within Spain and the Spanish speaking community. During early December, we participated at the Open Source Summit in Paris. This included a keynote and also a half day Apache track featuring a range of technical presentations for various projects. We also provided some additional talks as part of the community track.
Community Development also ran the Apache booth which attracted a lot of visitors. As this was a predominantly French speaking event, the French version of the ASF brochure was very useful in explaining to people what the foundation does and how it works. Feedback received from attendees was extremely positive and many wanted become involved with various projects. A key focus during January were tasks around the ASF involvement in for Google Summer of Code(GSoC). The Community Development team is a main contact for co-ordinating and managing the ASF involvement as a mentoring organisation. Many ASF projects have already created a list of ideas that prospective students could work on.
Following on from our last update, we have facilitated the introduction of Apache business cards that anyone involved with Apache projects can use when they are promoting their Apache project at an event or representing their Apache project. Two formats have been agreed, one that is a formal ASF role card that is based card n the existing ASF business cards, and another less formal community business card any contributor to an Apache project can use. A wiki page has been setup with information and FAQs to help with the introduction.
Our mailing list traffic remains stable this quarter with the the main focus being discussions related to the Apache events announced for 2018.
> Committers and Contributions: Over the past quarter, 1,715 contributors committed 51,157 changes that amount to 17,995,945 lines of code across Apache projects. The top 5 contributors during this timeframe were: Michał Narajowski (673 commits); Daniel Sun (666 commits); Mark Thomas (592 commits); Andrea Cosentino (514 commits); Junkai Xue (513 commits).
All individuals who are granted write access to the Apache repositories must submit an Individual Contributor License Agreement (ICLA). Corporations that have assigned employees to work on Apache projects as part of an employment agreement may sign a Corporate CLA (CCLA) for contributing intellectual property via the corporation. Individuals or corporations donating a body of existing software or documentation to one of the Apache projects need to execute a formal Software Grant Agreement (SGA) with the ASF.
During Q3 FY2018, the ASF Secretary processed 203 ICLAs, 13 CCLAs, and 4 Software Grants. Apache committer activity can be seen at http://status.apache.org/#commits
> Brand Management: This quarter has seen the usual stream of questions, potential infringements, permission requests and registration activities to the Brand Management team. Our policies and answers to common questions may be found on online at https://www.apache.org/foundation/marks/resources and we would encourage everyone with a brand related question to review those pages in the first instance.
One of the challenges for the Brand Management team has been finding a way to track open issues without imposing an unnecessary burden on those raising the issue, the Apache project communities the issue relates to or the Brand Management team. Like all communities at Apache, our communication is based on a mailing list --albeit a private one in this case as many of the issues we handle require a degree of confidentiality. It has been clear for some time that the mailing list alone is not sufficient for tracking open issues. Having experimented with various schemes without success over the last six months, we believe we have found a solution. The Brand Management team is now utilizing a shared mailbox and associated labeling system to allow all team members to see, broken down by project, which issues are resolved, which are waiting on other parties and which require action from us. It is still early in the adoption of this new system, but the initial results are promising.
In this quarter the US trademark registration has completed for Tez® and CouchDB® along with a number of renewals of existing marks. Some of these renewals have been for communities that came to the ASF with registrations in a large number of jurisdictions. Given the costs associated with renewing marks in some jurisdictions, we have started to discuss with those communities whether renewal is a cost-effective use of our funds.
Looking forward to the next quarter, we hope that the new issue tracking process fulfills its early promise and we'll be doing detailed planning for the next financial year.
As always, if you do have any comments or questions for the Brand Management team, please do get in touch: https://www.apache.org/foundation/marks/contact
> Legal Affairs: The Apache Software Foundation (ASF) Legal Affairs team works diligently with our pro-bono legal counsel and answers legal questions, and addresses policy issues regarding license compatibility for The Apache Software Foundation. In the last quarter, the Legal Affairs team worked on providing guidance on how to update two of our Export Control Classification Number (ECCN) numbers for ASF projects. In addition the following specific questions were answered and the following work was performed:
- How to deal with commercial attribution and use of ASF software.
- How to properly deal with NOTICE and LICENSE files in ASF projects.
- The inclusion of Apache license short headers in source code files.
- Answering whether or not Unified Modeling Language (UML) files could be licensed using the Apache License version 2.0 (ALv2).
- Use of a dependency licensed under the JSON lib license and also a community with a question about the BSD 3 clause (“nuclear”) license.
- The Eclipse Public License version 2.0 was added to Category-B license list on the legal resolved page.
- The inclusion of public work files in ASF projects.
- Whether design files commercially licensed could be used to build ASF project websites.
- Discussions surrounding the replacement of our CLA with the DCO+ALv2 agreement were undertaken but did not reach any conclusions.
- The use of metrics data collection surrounding the use of ASF projects was discussed.
The committee is a Board committee and reports directly Apache Board of Directors. We are eager to meet and serve the needs of our projects, in collaboration with our pro-bono counsel.
> Infrastructure: The Infrastructure team and its volunteers have been hard at work over the past quarter working on our mail systems, LDAP, cost reduction, build system improvements, and continued migration off of ASF-owned machines to more flexible cloud-based provisioning.
The mail system at the Foundation is a complex system that has evolved over the twenty years of our existence. It serves tens of thousands of users, millions of daily messages, and resides at the very core of how our communities operate under the Apache Way. Yet, this long history and evolution comes with a lot of historical baggage and technical debt that we have been working against for quite a while. We have made great strides this quarter in crafting new archival and access systems, which also assists with our goals for migration and using Puppet for management. We are still testing and qualifying these systems for deployment, next quarter.
The Foundation has been on a long trajectory to consolidating our authentication and authorization mechanisms around a central LDAP-based system. Our initial deployment did not quite serve our needs properly, so we have simplified, upgraded, and applied Puppet to better provide LDAP services across the Foundation's infrastructure.
This process is near completion, and has served to reduce, remove, and simplify much of our historical tooling.
One of our cost reduction efforts has been focused around our domain and certificate management. We have consolidated several providers to just one, and are looking at about a 40% reduction in future costs. At the same time, using the domain registrar's APIs, we've been able to bring more consistent management to our set of domains (we manage about 40, for the Foundation and its projects).
The holiday season was a great time to upgrade our Jenkins build cluster to their latest LTS release, while people were away spending time with family instead of queuing more build jobs. In addition, one of our sponsors helped out by donating many more build machines. Our projects have an ever-increasing need for more builds, so this has been a great quarter to satisfy those needs.
Lastly, we have made some great progress on our movement away from Foundation-owned hardware towards third-party provisioning of hardware and virtual machines. This long-term project is finally seeing the light at the end of the tunnel, and should be finalized during calendar year 2018.
> Financial Statement:
> Fundraising: Over this past quarter we have been launching our Targeted Sponsorship program. Targeted sponsorships give our sponsors greater recognition and more flexibility in how they can help our Top-Level Projects. Take a look at http://www.apache.org/foundation/thanks2.html
We are also proud to be working on three Apache events for 2018: ApacheCon 2018 North America in Montreal in September, the Apache 2018 EU Roadshow in Berlin in June and the Apache 2018 US Roadshow in Washington, DC in October.
Interested in sponsoring? Please email email@example.com for more details.
Finally, the Foundation relies on our sponsors to exist. We are not a trade organization but a 100% volunteer-led charity. Donations are tax-deductible to the extent permitted by law.
# # #
Report prepared by Sally Khudairi, Vice President Marketing & Publicity, with contributions by Sam Ruby, ASF President; Rich Bowen, Vice President Conferences; Sharan Foga, Vice President Community Development; Chris Mattmann, Vice President Legal Affairs; Mark Thomas, Vice President Brand Management; Greg Stein, ASF Infrastructure Administrator; Tom Pappas, ASF Member and Vice President, Finance & Accounting at Virtual, Inc.; and Kevin McGrail, Vice President Fundraising.
For more information, subscribe to the firstname.lastname@example.org mailing list and visit http://www.apache.org/, the ASF Blog at http://blogs.apache.org/, the @TheASF on Twitter, and https://www.linkedin.com/company/the-apache-software-foundation.
(c) The Apache Software Foundation 2018.