Page History

...

1. Early alignment matters
Projects that thrive (e.g.for example, Flink, Iceberg, and Airflow) had mentors who clarified ASF expectations early, especially around releases, mailing-list use, and decision-making. Early reinforcement prevents years of off-list or GitHub-only habits that are hard to undo later.

2. Balance guidance with independence
Over-involvement can mask weak community ownership. Mentors succeed when they teach why ASF practices exist, then step back and let the PPMC lead, intervening only when culture or process drifts.

3. Watch for silent warning signs
Long gaps between releases, single-company commit patterns, or mailing lists that go quiet are all early indicators of risk. Mentors should surface these gently before they become structural problems.

4. Coordinate among mentors
Consistent messaging avoids confusion. Podlings that received mixed advice (e.g., on release timing or voting scope) often stalled until mentors and the IPMC clarified expectations together.5. Model transparent communication
When mentors consistently reply on-list, summarize outcomes, and reference policy links, podlings mirror that behavior. Mentor silence or private side-chats often lead to slower culture adoption.

65. Recognize when withdrawal or retirement is healthy
As seen with Zipkin or Mesos, not every project needs to remain at Apache forever. Helping a community make that decision transparently can be as valuable as guiding one to graduation.to graduation.

6. Keep mentorship time-bounded
Effective mentors plan their exit. Ensuring the PPMC can self-govern before graduation and remains functional without external prompting.

7. Time in incubation is a signal, not a goal
Incubation length varies from months to years. Fast graduation can show strong existing maturity (as with Flink) but may hide dependence if mentors push too soon. Longer incubation can simply reflect complex IP clearance (NetBeans) or gradual culture-building (Superset). Mentors should judge progress by ASF maturity, including steady releases, independent decisions, and visible community growth, not by time alone.

8. Mentorship style should adapt to the podling’s phase
Early phases need hands-on clarification of ASF basics such as releases, voting, and mailing lists. Later stages benefit more from coaching and accountability than instruction. Mentors who shift from directing to advising help the PPMC gain true independence before graduation.

9. Maintain context after graduation
Graduation isn't the end of learning. A short transition period where mentors remain subscribed or available helps the new TLP stabilize and handle first-year governance and reporting challenges confidently.

10. Reflect and share lessons back to the IPMC
Each incubation reveals new edge cases in culture, licensing, or governance. Mentors strengthen the whole Incubator when they share anonymized insights that inform future guidance and policy updates7. Keep mentorship time-bounded
Effective mentors plan their exit. Ensuring the PPMC can self-govern before graduation and remains functional without external prompting.

...

Case Study 1: Apache Pinot - Strong Community Growth and Graduation

...

• Releases: Began producing incubating releases in 2016; later established a steady cadence.
• Community growth: Quickly broadened participation beyond Airbnb — - contributors from Google, Polidea, and independents became committers.
• Governance: Shifted all decision-making onto dev@ mailing lists.
• Ecosystem impact: Widely adopted in data-engineering ecosystems; integrations accelerated growth.
• Mentorship: Mentors emphasized neutrality and rotating release managers.

...

• Community context: An established ecosystem already existed under the OpenZipkin GitHub organization.
• Challenges: Development and issue tracking remained primarily in the external GitHub organization; ASF mailing lists were under-utilized.
• Releases: No incubating ASF releases were produced.
• Mentorship: Concerns were raised about lack of ASF alignment (releases, infrastructure, governance).

...

NetBeans shows that incubation isn’t just for new projects — - even mature, widely used codebases must:

...

Kafka is often cited as a strong multi-company community; as its commercial ecosystem expanded, the community continued to discuss how to preserve vendor-neutral governance.

...

Case Study 16: Apache Pulsar

...

- Modern Distributed Messaging with Transparent Governance

Entry

• Originally developed at Yahoo! for cloud messaging.
• Entered the Apache Incubator in June 2017.

...

Arrow shows that ASF governance can successfully coordinate long-term, cross-language data standards serving a broad ecosystem.

...

Case Study 25: Apache NiFi

...

- From Government Research to Open Collaboration

Entry

• Originated within the U.S. National Security Agency (NSA) as “NiagaraFiles.”
• Donated to the ASF through a U.S. government release process.
• Entered the Apache Incubator in November 2014.

...