Graduation marks the point at which a podling has demonstrated its ability to operate as a healthy, self-governing Apache project. This guide explains the criteria the Incubator PMC (IPMC) uses to evaluate readiness for graduation and outlines the steps to prepare for this review.

About This Guide

This guide is advisory, not a fixed checklist. Each project matures differently, and graduation decisions rely on the judgment of mentors and the IPMC based on the podling’s overall health and sustained practice of The Apache Way. These criteria help podlings self-assess and demonstrate readiness. They are meant to support discussion, not define strict pass/fail requirements.

What Graduation Means

Graduation does not mean the podling’s technology is “finished”. it means the community has learned and practiced The Apache Way.
A graduated project is trusted to manage its own governance, releases, and brand under ASF oversight, without day-to-day IPMC involvement.

Core Graduation Criteria

These criteria are not a one-time checklist but indicators of sustainable community maturity. The IPMC and mentors look for clear, long-term evidence in each area.

1. Community and Diversity

• The community includes multiple independent contributors and committers (no single employer dominates development or decision making).
• The project fosters an open and welcoming culture that encourages new contributors to join and grow.
• At least three active PPMC members from different organizations are required to form a sustainable PMC.
• Mentors are actively involved but not driving all decisions.

2. Governance and Self-Management

• The podling consistently follows The Apache Way - decisions are made publicly on mailing lists, votes are documented, and consensus is respected.
• The PPMC demonstrates its ability to manage its own affairs, including adding new committers and PPMC members.
• The project demonstrates understanding of ASF policies, including releases, trademarks, and licensing.
• Private list traffic is limited to appropriate topics (personnel, security, or sensitive issues).
• The podling uses ASF-provided infrastructure for mailing lists, source control, issue tracking, and websites. All credentials are ASF-managed.

3. Releases and IP Compliance

• The podling has produced ASF-compliant releases approved by the IPMC.
• All source code and dependencies have been reviewed for license compatibility.
• The release includes a correct NOTICE and LICENSE file, and any category-X code has been removed.

4. Branding and Identity

• The project’s website and materials consistently use the “Apache [ProjectName]” name.
• Project name approved by the ASF Brand Management Committee.
• Mentors verify that the project follows the ASF Brand Management Guidelines.
• Third parties, vendors, and related products must also follow the ASF trademark and branding policy, including the correct use of the Apache name and project marks in their materials, documentation, and marketing.

5. Reporting and Oversight

• The podling provides regular quarterly reports to the IPMC, showing responsiveness and transparency.
• Reports demonstrate progress in community building and releases, not just technical milestones.

6. Vendor Neutrality

• No single company or sponsor dominates the project’s direction or decision-making.
• Employment or commercial interests are disclosed, but they do not influence votes.
• Project governance decisions are based on merit and community consensus.

Evidence the IPMC Looks For

• Mailing list archives showing open, inclusive decision-making.
• Documented votes for releases, committers, and PPMC members.
• IP clearance documentation for code imports.
• Project name approved by the ASF Brand Management Committee (VP, Brand Management).
• Mentor sign-off on recent releases and reports.
• Public metrics showing ongoing activity (commits, discussions, contributors).
• Consistent use of ASF infrastructure for all project operations.

Using the ASF Maturity Model (Optional)

Podlings may optionally use the ASF Maturity Model to self-assess their community and governance practices.

The model is not a graduation requirement, but it provides a structured framework for evaluating how well a podling is applying The Apache Way.
It can help identify areas for improvement before proposing graduation, for example, in areas such as diversity, openness, or decision-making processes.

Mentor Role in Graduation Preparation

Mentors play a critical role in helping a podling prepare for graduation.
Their support ensures readiness, consistency with ASF expectations, and a smooth transition to Top-Level Project status.

Mentors should:

• Guide the podling in evaluating each graduation criterion and gathering evidence.
• Verify that ASF infrastructure, branding, and reporting are complete and compliant.
• Encourage the community to document open decision-making on the public dev list.
• Help the PPMC draft the Graduation Resolution and provide historical context when questions arise during the IPMC vote.
• Confirm that community health, contributor diversity, and governance practices are sustainable without the need for mentor involvement.

Mentor endorsement is not a formality, it reflects confidence that the podling can operate as a self-governing Apache community.

Graduation Pathways

1. To a Top-Level Project (TLP)

• The PPMC proposes to form a Project Management Committee.
• Draft Graduation Resolution is reviewed by mentors and the IPMC.
• The IPMC votes to recommend graduation.
• The ASF Board votes to create the TLP and appoint the Chair.

2. To Become a Subproject

• Less common: a podling may join an existing ASF project.
• Requires coordination with that PMC and the IPMC.

Graduation Readiness Checklist

The Graduation Vote

1. The PPMC starts a [DISCUSS] thread on dev@ to assess readiness.
2. After consensus, a [VOTE] thread is held on dev@ and then on general@incubator.apache.org.
3. The IPMC reviews the evidence and votes whether to recommend graduation.
4. Once approved, a Board resolution is submitted for formal approval.

After Graduation

Once the ASF Board resolution passes, the project becomes a Top-Level Project and transitions to normal ASF operations.
For details on post-graduation responsibilities, see Graduation & Beyond.

See Also

• Podling Orientation Guide
• Vendor Neutrality
• How to Use the ASF Maturity Model
• ASF Brand Management Guidelines
• ASF Project Reporting Guide