Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add one more

...

  • Mentors should inform the IPMC early when a podling shows sustained inactivity, release delays, or governance problems.
  • Use private@incubator for sensitive concerns and general@incubator for public awareness and guidance.
  • Encourage the PPMC to document challenges transparently in reports so the IPMC can assist before issues become critical.
  • Treat escalation as part of responsible mentorship, not as failure — timely communication helps protect both the podling and the wider community.

...

Scenario: Conflicting Mentor Advice

In one podling, mentors gave different guidance on key incubation steps. One mentor told the community to proceed with a release candidate, while another advised waiting for additional license review. The podling, unsure which direction to follow, paused work and sought clarification on the incubator mailing list. The inconsistent advice created confusion and slowed progress until the mentors and IPMC clarified expectations together.

Reflection questions

  1. How can mentors coordinate to ensure their guidance is consistent and aligned with ASF policy?
  2. What should a podling do when mentors provide conflicting or unclear instructions?
  3. How can the IPMC help maintain a shared understanding of policies and mentor responsibilities?

Possible path forward

  • Mentors should communicate regularly with each other and with the IPMC to stay aligned on ASF practices.
  • When uncertain, mentors should confirm their interpretation on the incubator list before advising the podling.
  • Podlings should feel free to ask for clarification on general@incubator when advice appears inconsistent.
  • Consistent, transparent communication between mentors prevents confusion and helps the podling learn The Apache Way more effectively.

...

Conflict Resolution and Communication

...