This guide explains vendor and other neutrality requirements for Apache Incubator podlings. It describes why neutrality matters, what the Incubator looks for during incubation, and how podlings and participating individuals or organizations can support community-led governance. The goal is to provide clear and practical guidance consistent with ASF principles and Incubator expectations. Additional background is available in the Incubation Policy, and a general overview of The Apache Way is also helpful.
Neutrality means that no single individual, company, or other organization controls or directs an Apache project. Individuals contribute in their own capacity, decisions are made publicly, and the project’s identity, processes, and governance belong to the community. Participation from organizations or vendors is welcome, provided governance and releases remain community-based and independent.
Neutrality ensures:
These expectations reflect ASF governance norms and IPMC evaluation criteria.
Many podlings begin with most contributors associated with a single entity. This may be a company or a group around an individual founder. This is normal in early incubation. Over time, podlings are expected to broaden participation, move governance to the public lists, and build processes that are not tied to any one person or organization. The focus is on visible progress toward independence.
Strong involvement from one entity, whether a company, individual maintainer, or other group, is not inherently a neutrality problem. Common early-stage patterns include:
Neutrality issues arise only when these patterns constrain participation or obscure community governance.
Neutrality does not require:
Neutrality is based on transparency, governance structure, and independence, not numerical representation.
Neutrality concerns often come from inherited habits rather than deliberate behaviour. These include:
Indicators that neutrality may require attention include:
These indicators warrant review, but they are not problems in themselves.
Some neutrality issues may be less visible:
Addressing these issues fosters stronger community trust and increased participation.
The following must be resolved for graduation:
Relevant ASF policies include the ASF Release Policy and the ASF Trademark Policy.
A neutral project demonstrates:
What matters is that the project is open, transparent, and not dependent on a single entity.
Design, planning, roadmap decisions, and elections must take place on ASF mailing lists. Private tools (e.g., Slack, Teams, WeChat, Discord) may be used for informal coordination, but not for governance or decision-making. See ASF mailing list guidance and Communication in ASF projects.
Official releases must be produced using ASF infrastructure and follow the ASF Release Policy. Internal or private infrastructure may assist development, but must not produce release candidates.
PPMC membership should reflect sustained participation in the project. Over time, podlings should show:
There is no numeric requirement, only evidence of progress and openness.
Some podlings involve contributors from several organizations but still rely heavily on one organization or one individual. This is acceptable early in incubation. Over time, the project must show that others can participate in governance, discussion, and release activities. The key question is whether contributors outside the dominant entity can influence the project’s direction.
Organizations and individuals participating in a podling should:
These expectations apply equally when the dominant influence comes from an individual acting alone.
If neutrality concerns arise, useful adjustments include:
Proposals should include context, be raised early, and avoid referencing private discussions. Discussion should occur on the lists to allow broad participation.
Internal or private tools can be used for convenience, but require transparency:
Contributors may need to explain ASF expectations to managers or organizational leadership. Key points:
See the ASF overview.
Work should proceed publicly and allow time for input. Decisions should be recorded clearly on the lists.
Openness may be shown through:
The IPMC evaluates:
Podling reports should briefly describe:
Reports should focus on clarity and progress rather than numerical summaries.
Mentors help identify neutrality issues early, reinforce public governance, onboard new contributors, and provide informed assessments to the IPMC regarding progress and risks.
Podlings are responsible for:
Neutrality is a PPMC responsibility. All PPMC members are expected to notice and draw attention to anything that may limit participation or indicate private decision-making. This responsibility applies throughout incubation. Mentors also help identify neutrality risks, particularly early in incubation when outside perspectives can highlight issues that are less visible to project participants.
Other groups may surface related signals, including:
Anyone may raise a potential issue, but the PPMC is accountable for understanding it and ensuring that project governance remains open and independent.
Neutrality concerns should be raised on the public lists with enough detail for the PPMC and mentors to understand the issue. The purpose is to clarify the situation, review the relevant processes, and ensure that governance remains public and accessible.
When a concern is raised, the PPMC should:
If further assistance is needed, escalation paths include:
Escalation is intended to support the podling and clarify expectations.
Organizational or regional norms may influence contributor behaviour. Podlings should reinforce that ASF projects value individual participation, open discussion, and public collaboration.
Podlings must comply with ASF trademark and branding policies. Project names, documentation, and communication must not imply ownership by any individual or organization. See the ASF Trademark Policy.
To graduate, a podling must demonstrate:
Graduation may be delayed if:
Lack of progress toward neutrality may lead to extended incubation, additional Board scrutiny, declining participation, or, in rare cases, retirement from the Incubator.
Vendor neutrality is a core ASF governance principle. Podlings do not need equal representation among all contributors or organizations. They must, however, demonstrate public decision-making, independence from any single individual or organization, and consistent progress toward a sustainable community-led model.