DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
- how governance is occurring on public lists;
- progress in participation from additional individuals or organizations;
- how
How release processes follow ASF infrastructure;
- steps taken to improve transparency or independence;
- any risks or concerns being addressed.
...
- using public mailing lists for governance and decisions;
- maintaining ASF-compliant branding;
- encouraging participation from multiple individuals and organizations;
- declaring affiliations in votes and discussions;
- supporting independent contributors as they take responsibility.
16. Responsibility for Monitoring Neutrality
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:
- trademarks@apache.org when reviewing branding
- infra@apache.org when reviewing websites or build processes
- IPMC reviewers when reading podling reports
Anyone may raise a potential issue, but the PPMC is accountable for understanding it and ensuring that project governance remains open and independent.
17. Raising, Escalating, and Resolving Neutrality Concerns
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:
- provide context if available
- review whether project processes, tooling, or communication patterns require adjustment
- agree on necessary changes and document the outcome on the list
If further assistance is needed, escalation paths include:
- mentors, if they are not already involved
- the IPMC, for broader guidance on incubation expectations
- trademarks@apache.org for branding issues
- infra@apache.org for infrastructure or release-process issues
Escalation is intended to support the podling and clarify expectations.
18. Cultural Considerations
Organizational or regional norms may influence contributor behaviour. Podlings should reinforce that ASF projects value individual participation, open discussion, and public collaboration.
...
19. Branding Requirements
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.
...
20. Graduation Requirements
To graduate, a podling must demonstrate:
- community-led, publicly documented governance
- participation from more than one individual or organization, or a clear progress toward this
- ASF-controlled, repeatable release processes
- branding aligned with ASF policy
...
21. Graduation Concerns
Graduation may be delayed if:
- governance is dominated by a single individual or organization without evidence of change
- independent contributors do not participate meaningfully
- project direction follows external priorities rather than community discussion
- branding conflicts with ASF policy
...
22. Consequences of Stagnation
Lack of progress toward neutrality may lead to extended incubation, additional Board scrutiny, declining participation, or, in rare cases, retirement from the Incubator.
...
23. Summary
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.
...