Page History

...

By analysing where the IPMC acted early, responded late, or could have recognised signals sooner, the Incubator aims to continuously improve its role in supporting healthy communities and upholding ASF governance standards.

...

Purpose

The guide supports the IPMC’s continuous improvement by identifying patterns of oversight that have influenced podling outcomes. It draws on verified public information to help mentors and reviewers recognise early signs of strength or risk in community development.

...

The goal is to reinforce timely, transparent, and practical support across all stages of incubation.

...

How to Use This Guide

Use these patterns as reference points when reviewing reports, mentoring podlings, or participating in graduation discussions. They are not checklists or rules but conversation starters for recognising early signals, supporting timely engagement, and maintaining ASF’s governance standards.

...

1. Acting Early

Projects in this group benefited from early mentor engagement and active guidance from the IPMC. They demonstrate that incubation is often most effective when ASF processes and communication norms are established from the outset.

...

Lesson: Early and consistent mentoring strengthens ASF culture, accelerates graduation, and builds durable community habits.

...

2. Recognised but Delayed Action

In these examples, the IPMC or mentors identified issues but responded or sustained intervention more slowly than ideal. Delays allowed stagnation or weak engagement to persist beyond the point of easy recovery.

...

Lesson: Awareness must lead to visible and timely engagement. Prompt, supportive action prevents repeated cycles of low activity or uncertainty.

...

3. Missing Early Signals

These cases illustrate instances where cultural or governance misalignment was not addressed early in the incubation process. Strong technical output sometimes masked deeper structural challenges that limited long-term sustainability.
These examples describe past stages of incubation and do not reflect the current state of the projects. They illustrate common patterns rather than project-specific causes.

Examples: MXNet, Zipkin, Trafodion.

MXNet

Originally developed at the University of Washington and later supported heavily by AWS.
The IPMC noted the concentration of contributors within one organisation and encouraged broader participation.
Although the project achieved technical success and multiple releases, diversity remained limited throughout graduation, and activity later declined, ultimately leading to its retirement.

IPMC reflection: Sustained concentration within a single organisation can appear stable in the short-term but signals long-term fragility. Diversification and cross-company participation are most effective when reinforced from an early stage.

Zipkin

Entered the Incubator with an existing ecosystem under the OpenZipkin GitHub organisation.
While the community produced releases, most development and discussion continued on external infrastructure and instant messaging channels rather than ASF mailing lists.

...

IPMC reflection: When communication and infrastructure remain outside ASF norms, it indicates limited governance alignment. Early evaluation of cultural fit helps prevent prolonged incubation without integration.

Trafodion

Donated by HP as an SQL on HBase database. The project met the release and process requirements and graduated successfully; however, contributor diversity remained limited, and activity later declined, ultimately leading to retirement.

IPMC reflection: Graduation criteria should include signs of ongoing contributor renewal and independence, not only procedural completion.

...

4. Outcome

By turning historical cases into structured learning, the IPMC develops institutional awareness of the characteristics of effective oversight. This strengthens mentoring, improves the quality of graduation, and ensures the consistent application of ASF values: transparency, collaboration, and self-governance. In doing so, the Incubator not only supports individual podlings but also contributes to the ASF’s broader ability to sustain healthy, self-directed communities across generations of projects.

...

5. Mentor Actions and Early Signals

(Practical Application for Mentors)

...

The following practices translate oversight lessons into everyday mentoring habits.

Acting Early: Positive Mentor Habits

• Model ASF communication: Ensure all substantive decisions and technical discussions happen on the dev@ list rather than in private or external channels.
• Encourage shared responsibility: Help rotate release managers, reviewers, and vote initiators early to build resilience.
• Promote transparency: Ensure outcomes from GitHub or chat discussions are summarised on the public mailing list.
• Acknowledge progress: Recognise ASF-compliant releases and new contributors publicly to reinforce community engagement.

Recognising but Delaying Action: Correcting the Pattern

• Raise patterns, not people: Focus discussion on recurring issues rather than individuals (for example, reliance on one company or slow releases).
• Document concerns: Use quarterly reports to record observed risks or progress; this helps the IPMC identify broader trends.
• Ask for help early: If mentor consensus or capacity is limited, open a short incubator-general thread for guidance rather than waiting.

Missing Early Signals: Avoiding Oversight Gaps

• Check communication scope: Are major discussions or decisions occurring off ASF infrastructure (for example, Slack, private messaging, or corporate tools)?
• Watch community balance: Is one company or individual driving most releases, decisions, or branding?
• Support contributor growth: Identify and encourage new committers or PPMC members to participate in votes and discussions.
• Escalate thoughtfully: When alignment with the ASF process or culture remains unclear after guidance, raise the issue on incubator-general for wider IPMC visibility.

Takeaway for mentors:
Timely communication, visible documentation, and early, transparent discussion are the most effective ways to prevent small issues from becoming long-term risks.
Proactive mentoring helps podlings internalise ASF culture and reduces the need for later IPMC intervention.

...

7. Reflecting on Oversight Challenges

Occasionally, the IPMC or mentors have faced situations where issues were detected too late or not fully understood during the incubation process.
These examples highlight how trust, communication, and verification must work in tandem for effective oversight.

...

Lesson:
Reflecting on these challenges helps the IPMC strengthen its oversight and mentor support practices. By treating occasional missteps as opportunities for improvement, the Incubator reinforces transparency, accountability, and trust throughout the ASF.

...

8. Graduation Deferrals and Lessons

While most podlings graduate on their first proposal, several have had their graduation discussions deferred or repeated. These cases illustrate how the IPMC balances encouragement with due diligence and help define what "readiness" truly means within the ASF culture.

...

Thoughtful deferrals demonstrate that oversight is working as intended, ensuring that new TLPs embody the transparency and self-governance at the heart of the Apache Way.

...

9. Graduation Handoff and Transition

Graduation marks a transition to full project autonomy. Once a podling becomes a TLP, IPMC oversight ends. In many cases, one or more former mentors also join the new PMC and continue helping as PMC participants. This ensures a smooth transition while clearly indicating that responsibility rests entirely with the new PMC.

...