• Created by Unknown User (jmclean) on Nov 12, 2025 7 minute read

Note: This guide is based on historical analysis of ASF Incubator podling reports from 2019–2025.
It summarises patterns and trends using text analysis and Python-based data processing, assisted by AI tools for efficiency. The findings are for mentoring insight and training purposes.

Purpose

This guide helps mentors recognise and respond to common issues that appear in podling monthly reports and understand how those issues have evolved over the last five years. It combines per-podling analysis of five years of incubating project reports to support data-driven mentoring.
The intent is to help mentors and IPMC members identify effective patterns of oversight and apply lessons from past experience to improve mentoring and podling support.
It is not used for compliance or evaluation; it supports mentors and podlings in understanding common growth patterns and improving collaboration.

1. Common Podling Issues and How to Respond

1.1 Release and Licensing Issues

Common signals

  • Still working toward a first release after 6 months
  • Votes not passed or delayed
  • Missing or incorrect content in LICENSE or NOTICE files

Mentor focus

  • Verify the podling understands what constitutes an ASF release and how to follow the ASF Release Policy
  • Encourage use of the Incubator Release Management Guide or the Incubator Release Checklist, or a project-specific equivalent
  • Ensure at least one mentor participates in each release vote and confirms license and notice correctness
  • Remind the PPMC that releases must be made under ASF infrastructure and approved by the Incubator

Useful resources

1.2 Community and Growth Issues

Common signals

  • Inactive or few committers
  • Waiting for mentor input before acting
  • Repeated mentions of contributors without committer growth
  • Low or declining commit and discussion activity

Mentor focus

  • Determine whether the issue is general inactivity or over-reliance on a single sponsor or employer
  • Encourage discussion and decision-making on the mailing list rather than in private channels
  • Suggest small, well-scoped starter tasks to help new contributors gain confidence
  • Review committer diversity and onboarding practices
  • Encourage a healthy, transparent process for adding new committers and PPMC members

Useful resources

1.3 Governance and Decision-Making

Common signals

  • Need to hold votes or uncertainty about consensus
  • Few or no visible decisions recorded on the mailing list
  • Decisions appear to happen off-list or are led by one or two individuals

Mentor focus

  • Ensure project decisions are made publicly on the mailing list and documented for transparency
  • Reinforce consensus-based decision-making, using lazy consensus where appropriate
  • Encourage discussion summaries and a clear recording of outcomes for each decision
  • If leadership is concentrated in a few individuals, guide the PPMC toward broader participation and shared responsibility
  • Encourage documentation: Help podlings record decisions, votes, and lessons in public project spaces so future contributors can understand context and process

Useful resources

1.4 Vendor or Affiliation Dominance

Common signals

  • References to “our company,” “internal team,” or “employees”
  • Lack of visible discussion from unaffiliated contributors
  • No public roadmap or development plan
  • Deadlines or release timing driven by external business goals

Mentor focus

  • Remind the PPMC that participants act as individuals, not company representatives
  • Encourage contributors to use non-corporate email addresses for ASF work when possible
  • Look for visible participation and decision-making from multiple affiliations
  • Reinforce that ASF projects set their own pace and priorities based on community consensus, not external timelines
  • Escalate persistent single-vendor control to the IPMC if community independence does not improve

Useful resources

1.5 Branding and Naming

Common signals

  • Mentions of logo, website, or trademark issues
  • Use of old, company-specific, or non-Apache names
  • Incorrect or inconsistent use of “Apache (incubating)”
  • Artifacts or documentation missing ASF attribution

Mentor focus

  • Verify that the podling follows ASF branding and naming requirements
  • Check that the website, README, and artifact names use the correct “Apache (incubating)” format
  • Ensure the podling understands the ASF trademark process before graduation
  • Encourage early review of logo, website, and naming consistency to avoid delays near graduation

Useful resources

1.6 Reporting and Process

Common signals

  • Report not submitted or repeatedly late
  • Minimal, copied, or outdated content in submitted reports
  • Confusion about reporting frequency or expectations

Mentor focus

  • If a podling misses two consecutive reports, expect the IPMC roll call process to begin and coordinate with the Incubator PMC Chair as needed
  • Remind the PPMC that reports are an opportunity to reflect on progress, identify community challenges, and ask for help where needed
  • Emphasise that reports are a tool for communication and shared accountability, not a bureaucratic requirement, and should include both community progress and technical updates
  • Encourage concise, factual updates covering releases, community activity, and governance progress
  • Verify that reports are written by the podling itself, not mentors, and reflect the community’s own perspective

Useful resources

2. Five-Year Trends Summary (2019–2025)

Analysis of five years of podling reports reveals several encouraging long-term shifts and a few persistent challenges. All values are normalised per active podling per year, showing the average frequency of issue mentions in submitted reports.

Release and licensing issues have declined sharply since 2020.
This suggests that clearer release documentation, mentor training, and automation around release checks have been effective. Most podlings now complete a compliant first release with less intervention than in previous years.

Community-related topics have remained steady across the entire period.
Each podling continues to report similar levels of community growth or stagnation concerns. This suggests that while technical processes have improved, engagement and diversity among contributors remain consistent, with ongoing mentoring needs. Community building, onboarding, and balancing company participation are still the most common themes in reports.

Governance visibility has increased gradually.
More reports now reference discussions, lazy consensus, or formal votes, showing a better understanding of ASF decision-making norms. This improvement aligns with the rollout of governance-focused mentor training and clearer PPMC guidance introduced from 2021 onward.

Branding and trademark issues rose notably after 2023.
This likely reflects increased awareness and earlier attention to ASF branding and trademark compliance rather than a higher number of graduations. Mentors and podlings appear to be raising these topics earlier in the incubation process, which is a positive sign of better awareness. An early understanding of ASF naming and trademark requirements remains important to avoid last-minute blockers during graduation review.

Vendor dominance appears intermittently rather than as a persistent trend.
These cases often involve podlings with development concentrated within one company or sponsor. While uncommon, they underscore the continued importance of monitoring affiliation balance and ensuring that decisions reflect the broader community's interests, not corporate priorities. Mentors should raise concerns early if participation or decision-making appears limited to a single organisation.

Reporting discipline fluctuates year to year.
Missed or minimal reports cluster around the first quarter, likely reflecting renewal cycles and volunteer availability. Mentors should watch for podlings that miss consecutive reports as an early indicator of disengagement.

Overall, the data shows a healthy shift toward fewer procedural issues and more mature self-reporting. The Incubator’s focus has moved from release mechanics toward sustaining governance maturity, community independence, and mentor capacity.

3. Overview of Aggregate Trends

Across the five-year dataset, no strong seasonality was detected. Most issues appear at a steady rate throughout the year. This consistency suggests that podling challenges are shaped more by project maturity and community factors than by timing.

Analysis of report data across all active podlings shows how themes evolve and interact over time.

  • Release-related mentions declined after 2020, with only a small late-period uptick. This suggests release processes are maturing and require less mentor intervention.
  • Community and Reporting issues are strongly correlated (≈0.63), showing that as podlings prepare releases, they also engage more in reporting and community updates.
  • Governance visibility has increased steadily, and it co-occurs moderately with both Release (≈0.48) and Reporting (≈0.38), indicating that decisions are more visible during active development periods.
  • Branding references increased after 2023, reflecting the increased attention given to naming and trademark checks as part of maturity assessments.
  • Vendor mentions remain low and isolated (<0.2 correlation), confirming that affiliation concentration is not a systemic issue but requires early mentor attention when it appears.

Overall, these patterns indicate a gradual shift from procedural and compliance issues to a sustained focus on community and governance maturity.

4. Methodology

This analysis combines manual review with text processing of ASF Incubator podling reports from 2019–2025. Python scripts were used to detect common themes, normalise results, and visualise trends, with AI tools assisting for efficiency and summarisation.

Data sources: Podling monthly reports from the public archive and podlings.xml for project metadata.

Processing: Reports were tokenised and scanned for six recurring issue types - release/licensing, community, governance, vendor, branding, and reporting. Mentions were normalised per podling per month to offset changes in active projects, and correlations between issue types were calculated to identify co-occurring themes.

AI use and validation: AI tools assisted in generating analysis scripts and summarising results. Outputs were reviewed and verified by a human for accuracy and context, with random samples and outliers checked manually.

Limitations: The dataset focuses on written podling reports and excludes other communication channels such as mailing lists or issue trackers. Keyword analysis may overlook nuanced or implicit issues, and higher mention rates can reflect improved awareness rather than the emergence of new problems. AI helps with pattern detection and summarisation, but does not replace human interpretation or judgment.

Note: This guide summarises historical ASF Incubator report data for mentoring reflection and training. It supports learning and continuous improvement, not evaluation or audit of individual projects. Through shared reflection, mentors and IPMC members help sustain ASF culture and the long-term health of its communities.

  • No labels