This guide was generated from real graduation-related discussion threads on the Apache Incubator mailing list and reflects identity, branding, and communication issues raised while assessing graduation readiness.

Who This Guide Is For

This guide is intended for:

  • Podling PPMCs
  • Incubator mentors
  • IPMC members

It is designed to support practical decision-making as a podling prepares for graduation and questions arise about public-facing identity and communication practices.

Unifying Principle

At graduation time, the project must present a clear, community-owned Apache identity and operate with accessible, transparent communication anchored in the canonical public record.

Purpose

This guide documents the identity and communication themes that surfaced during graduation-related discussions.

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

1. Graduation Readiness Includes Public-Facing Identity

The graduation discussion included a review of how the project presents itself publicly.

Branding and identity concerns are treated as readiness signals because they affect:

  • user understanding of what the Apache project is
  • long-term independence perception
  • trust in the project’s governance and stewardship

2. Confusion Between “Apache” and Non-Apache Variants Is a Readiness Concern

Concerns are raised when public-facing material could be confused with:

  • the Apache podling/project
    and
  • a vendor product, distribution, hosted offering, or similarly named non-Apache variant

Perception and clarity are needed in graduation readiness.

3. Project Naming and Brand Signals Must Support Independence

Identity questions are raised where the project name or branding could be read as:

  • primarily controlled by a single company
  • part of a vendor ecosystem
  • a rebrand of an existing vendor product

These concerns are framed as governance and neutrality signals rather than as marketing preferences.

4. Public Channels, Websites, and Domains Are Part of the Identity Surface

Graduation-related discussion treated public surfaces as part of the “identity” of the project, including:

  • the website and where it points
  • domains and redirects
  • prominent download entry points

When these surfaces did not clearly represent the Apache project as the primary source of truth, questions will be raised.

5. Graduation Is a Correction Gate for Identity Issues

The discussion framed graduation as a point at which identity issues should be corrected rather than carried forward.

The readiness expectation are that:

  • identity confusion should not persist into TLP stage
  • public-facing identity should be stable and project-led
  • users should not have to guess which site, domain, or brand is authoritative

6. Canonical Communication and Accessibility Are Treated as Readiness Signals

Concerns are raised when project communication relies heavily on platforms that are not universally accessible.

The readiness concern is that:

  • decisions and consensus must be discoverable in the public record
  • contributors and users should not be excluded by geography, platform availability, or language barriers

Mailing lists are treated as the authoritative record for governance and decision-making.

7. Region-Specific Chat Platforms Can Create Perception Risk

A graduation discussion highlighted risks where region-specific or proprietary chat platforms are used extensively.

The concern is not the existence of chat platforms, but that they could:

  • become the primary venue for decision-making
  • create the perception of a closed or region-bound community
  • limit participation by contributors outside a specific geography

These risks are framed as governance and inclusivity concerns.

8. Chat Platforms May Be Used for Coordination, Not Governance

A distinction is drawn between:

  • chat platforms used for informal coordination or support
    and
  • mailing lists used for decisions, consensus, and record-keeping

Graduation readiness is assessed on whether this distinction is clearly maintained in practice.

9. Visibility of Decisions Is a Graduation Readiness Signal

Concerns are raised when:

  • important discussions were difficult to find on the mailing list
  • decisions appeared to be made elsewhere and summarized late or incompletely

Clear, timely reflection of decisions on the list is treated as an indicator of readiness.

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

  • Identity and communication practices are treated as graduation readiness signals
  • Confusion between Apache and non-Apache variants is a governance concern
  • Names and public-facing signals should support independence and neutrality
  • Websites, domains, and download entry points contribute to project identity
  • Mailing lists are treated as the canonical record for decisions
  • Region-specific chat platforms can create accessibility and perception risks
  • Chat platforms may support coordination but should not replace on-list governance
  • Visibility and accessibility of decisions are treated as maturity signals
  • No labels