...

• Clarify on the mailing list that mentors provide advice, not final approval, and that decisions belong to the PPMC.
• Encourage mentors to frame their guidance as “recommendations” or “ASF expectations,” rather than directives.
• Use moments like this as learning opportunities, reaffirming that mentoring supports independence, not control.

...

Scenario: The Conflicted PPMC

Several active PPMC members work for the same company that initially proposed the podling. As the project matures, company goals begin to align with community priorities, such as marketing deadlines, roadmap direction, or product integration timelines. Decisions on the dev@ list often mirror internal discussions, and other contributors hesitate to question them. When a mentor raises this concern, the PPMC insists that “everyone agrees internally,” but little discussion happens in public.

Reflection questions

• How can PPMC members recognize when company interests are influencing project decisions?
• What safeguards ensure that ASF projects remain independent of corporate agendas?
• What role should mentors and the IPMC play in helping a community maintain neutral, consensus-based governance?

Possible path forward

• Encourage all technical and strategic discussions to take place publicly on the mailing list, regardless of any prior internal agreements.
• When posting on behalf of an employer, clarify whose view you represent and invite others to comment openly.
• Rotate release managers, vote initiators, and report drafters to ensure shared ownership beyond a single organization.
• Mentors can remind the community that ASF projects operate by public consensus, not by company alignment—corporate support is welcome, but direction comes from the community.
• If necessary, the PPMC or IPMC can invite new contributors from outside the company to broaden participation and strengthen neutrality.

...

Scenario: The Unreliable Narrator

During several community discussions, a mentor and two PPMC members consistently argue for a particular technical direction. Later, it is discovered that all three work for the same company, which plans to integrate the feature into its product. Their affiliation wasn’t hidden, but it was never clearly stated in the relevant threads or votes. New contributors assumed the support was broad and independent. When this is raised, the individuals insist they were “just speaking as community members.” The incident damages trust and prompts a wider discussion about disclosure and transparency.

Reflection questions

• Why is it important to disclose company or organizational affiliations in ASF communities?
• How can mentors model transparent communication when their employer also has a stake in the project?
• What happens when affiliations aren’t clear and influence perceptions of consensus or neutrality?

Possible path forward

• Encourage contributors to disclose their affiliations when relevant, especially in discussions where corporate interests may overlap with community decisions.
• Remind everyone that consensus depends on clarity. The ASF expects decisions to be community-driven, not company-directed.
• If confusion arises, clarify on-list to restore trust and reaffirm that votes and discussions represent individual opinions, not those of employers.
• Use moments like this to reinforce vendor neutrality as part of the ASF’s governance culture.

...

Scenario: The Glossed-Over Report

A podling submits its quarterly report, describing the community as “active and healthy,” which highlights several releases and broad participation. Mentors and IPMC members, however, are aware that mailing list traffic has decreased, and contributor engagement has been inconsistent. When asked, the PPMC explains that they “didn’t want to sound negative” in a public report. Mentors remind the community that reports are not public relations statements, they are a core part of the ASF’s oversight and learning process.

Reflection questions

• Why must podling reports reflect reality, not just optimism?
• What responsibilities do mentors and the PPMC share for ensuring accurate reporting?
• How can mentors help communities be open about problems without fear of criticism?

Possible path forward

• Reiterate that reports are for transparency, not promotion, and accurate information allows the IPMC to provide timely help.
• Mentors should review draft reports and confirm they represent the full picture, including challenges.
• If a report omits serious issues, mentors can follow up on the mailing list and suggest a correction or clarification.
• Encourage the PPMC to discuss concerns openly before each report, so potential problems are recognized and documented early.
• Treat report preparation as a shared learning exercise, not a compliance task.

...

Conflict Resolution and Communication

...