This guide was generated from real graduation vote discussions on the Apache Incubator mailing list and reflects the issues that were actually raised during graduation votes.

Who This Guide Is For

This guide is intended for:

• Podling PPMCs
• Incubator mentors
• IPMC members

It is designed to support practical decision-making when a podling is being considered for graduation.

Unifying Principle

Graduation is assessed as a governance and operational readiness outcome.

Purpose

This guide documents the specific themes that surfaced during graduation votes: what voters questioned, what they objected to, and what they treated as readiness signals.

Guidance in this document complements, but does not replace, ASF policy and legal guidance.

1. Dissent Can Appear and Must Be Addressed

It is unusual for graduation votes to include dissent (-1), as most concerns are typically discussed and resolved before the vote is called.

When dissent does appear, it is framed as a readiness concern that requires an explicit response and resolution before a graduation recommendation can proceed.

2. Canonical Communication and Accessibility Are Treated as Readiness Signals

Graduation votes can raise concerns about region-specific or non-universally accessible chat platforms.

The readiness concern is that decisions and consensus must remain in the canonical public record, and that alternate channels must not become the place where governance occurs.

3. Branding and Apache Identity Signals Are Reviewed

Graduation votes can raise branding and identity concerns.

These concerns centre on how the project presents itself as an Apache project and whether the public-facing identity creates confusion about what is “Apache” versus something else.

4. Operational Closure Items Can Be Part of Graduation Readiness

Graduation votes can raise operational follow-through topics.

These included practical transition items such as:

• website and DNS handling
• downloads and related public release surfaces

These are treated as readiness and completion signals, not as product features.

5. IP Clearance Topics Can Surface as Readiness Concerns

Graduation votes can include readiness discussion connected to IP clearance.

6. Security Responsiveness Can Be Treated as a Maturity Signal

At least one graduation vote treated security responsiveness and vulnerability handling as a maturity signal relevant to readiness.

7. Key Takeaways for Mentors, PPMCs, and the IPMC

• Treat any -1 as a readiness blocker until it’s explicitly answered and resolved

• Graduation assumes governance happens in the canonical public record (and remains accessible)

• Expect reviewers to check Apache identity signals and whether public messaging creates confusion

• Close off obvious operational loose ends (site/DNS/download surfaces) before calling the vote

• Be ready to explain the podling’s IP clearance posture as part of readiness

• Demonstrated security responsiveness can count as a maturity signal during the vote