The Apache Software Foundation (ASF) is a charitable organization dedicated to the development of open source software, and has been praised by the community for its wide range of projects and open governance model. As one of the largest open source foundations in the world, how ASF chooses open source projects has become the focus of attention. In this article, we explore the ASF's process, criteria, and values for selecting open source projects, and the implications of those decisions for the open source community and industry.
As a long-time ASF volunteer, mentor, and board member, I am extremely proud to share unique insights into ASF's operating processes and values. ASF is based on the open source Apache license and operates in an open and practical way. Unlike many other foundations, ASF is a charitable organization established for the public interest. This article will further explore how ASF selects projects, the current situation of open source licenses, and the outlook for the future of ASF.
Within the ASF, the process of selecting projects begins with the Apache Incubator, where potential projects receive help and mentorship with the hope of eventually becoming a top-level Apache project. Anyone can submit a project proposal to the incubator and seek support from ASF internal staff. When reviewing potential projects, the ASF prefers to see a diversity of individuals and entities involved rather than just a single body corporate. We've found that this wide diversity leads to wider usage and longevity of projects.
The main goal of the incubator is to help projects learn and operate in what we call The Apache Way. This is a set of values that provide best practices for community-led development. Central to the Apache Way is strict vendor neutrality, prioritizing the community even above the project code itself. Open and transparent communication is also critical: ASF requires that all project communications be publicly accessible and permanently archived to support asynchronous collaboration. Additionally, all accepted projects come with the open source Apache license, ensuring that all source code is publicly available.
In the incubator, we first check the project's alignment with Apache values, although it doesn't need to be completely aligned, the project needs to be willing to adapt to these values. In addition, we also discuss from a license point of view to ensure that the project is fully compatible with Apache, and in some cases we may remove or replace dependencies. The goal of the Apache Way is to move in the direction of building self-sustaining communities. However, building a community can be difficult for some projects, and some projects fail to make it past the incubator stage.
Consensus decision-making is another key element of a thriving community in the Apache Way. In their experience, it is important to open up discussions and avoid a single project leader dominating the process. We have had projects with strong individuals trying to maintain control where they have not been successful for this reason. Open source projects come in many forms. However, using an open source license does not automatically make the project open source. The community is the key to unlocking the value of open source, promoting greater openness and transparency.
Through strict incubator processes and adhering to the values of "Apache Way", ASF not only selects many successful open source projects, but also helps create a supplier-neutral, open and transparent environment in the technical field.