Overview:
This guide helps podling communities (PPMCs) understand how to maintain adequate mentor coverage throughout the incubation process. It explains when and how mentors can be replaced, added, or transitioned, and clarifies that PPMCs share responsibility for ensuring continuity. The goal is to support stable oversight and consistent mentoring without unnecessary formality, reflecting the ASF’s principles of community-led governance and transparency.
Each podling in the Apache Incubator should have around two to three active mentors. Mentor changes are expected during incubation as participants’ availability shifts. The focus is to maintain consistent guidance and oversight for the podling.
This guide outlines:
Mentor replacement or addition may be considered when any of the following apply:
| Situation | Typical Indicators | Recommended Action |
|---|---|---|
| Inactivity | No mentor sign-offs or list participation for two or more report cycles | Check in with mentor; if no response, propose replacement |
| Change in availability | Mentor indicates they are stepping back or taking leave | Identify a new mentor before they leave |
| Conflict of interest | Mentor has a business or governance link to the podling’s main sponsor | Usually acceptable if disclosed and managed openly |
| Podling request | Podling feels they need more active or relevant guidance | Podling may directly propose a replacement or addition |
| Reduced coverage | Fewer than two active mentors remain | Encourage podling to invite additional mentors |
Note: Some mentors contribute in other ways, such as reviewing releases, guiding community discussions, or assisting with licensing and policy questions and may not always sign off reports. What matters is regular engagement and visibility on the podling’s mailing lists, not only formal sign-offs.
Mentor participation should be viewed in context. Occasional absences or reduced sign-offs do not automatically indicate disengagement if other forms of support remain visible.
Any PPMC member, mentor, or IPMC member may start the replacement process if coverage or engagement becomes an issue. PPMC members are encouraged to take initiative in maintaining mentor coverage and do not need formal approval from the IPMC to propose replacements. Note, however, that members must be IPMC members.
general@incubator.apache.org:
[DISCUSS] Mentor Replacement for <Podling Name>
podlings.xml entry (any IPMC member may do this)If a mentor is unavailable for a short period (such as travel or personal leave), they can inform the podling and other mentors. No replacement is needed if coverage remains adequate. Temporary partial involvement is acceptable if the mentor continues to provide support when needed and keeps other mentors informed of their availability.
As podlings mature, their needs may shift from technical setup to governance or community focus. Adding mentors with complementary experience can be helpful.
After graduation, mentors may continue as PMC members of the new project. Their continued involvement is welcome but no longer required by the Incubator.
Some podlings remain in incubation for several years due to large codebases, complex governance, or slow community growth. These projects often experience mentor turnover, making it especially important to maintain continuity.
To support stability:
The IPMC may occasionally review such podlings to verify that adequate mentoring and oversight continue.
Mentor changes are a routine part of incubation. Podlings can manage them directly, with light coordination through the IPMC. Timely replacements help maintain guidance and ensure consistent application of ASF principles and policies.
Key takeaway:
Mentor continuity supports podling stability and helps maintain effective oversight without interruption.