Welcome to the Apache Incubator

An introduction to joining the Apache Software Foundation through the Incubator

What Is a Podling?

A podling is a project accepted into the Apache Incubator on its journey to becoming an Apache Top-Level Project (TLP).

Before entering, a proposal is submitted with a Champion, a Sponsor, and at least one ASF Member mentor.

Incubation is not only about technology it’s about learning and practicing The Apache Way.

Goals of Incubation

  • Adopt ASF values: transparency, consensus, meritocracy, community over code, vendor neutrality.

  • Build a diverse and sustainable community.

  • Demonstrate ASF-compliant releases.

  • Ensure legal and policy compliance.

  • Graduate as an independent Apache project.

First Steps

  • Subscribe to project mailing lists (dev@, commits@, private@).

  • Introduce the community and mentors on dev@.

  • Set up ASF infrastructure (Git, website, issue tracker, lists).

  • Review code import with mentor and IPMC guidance.

  • Begin practicing open, list-based decision making.

Role of Mentors

  • Guide the podling in applying ASF policies and culture.

  • Help interpret ASF rules and avoid common pitfalls.

  • Review and sign off on reports and releases.

  • Provide continuity between the podling and the IPMC.

Podling Project Management Committee (PPMC)

  • Composed of initial committers, mentors, and voted-in PPMC.

  • Oversees the podling’s growth and governance.

  • Votes on releases and community decisions under IPMC oversight.

  • Uses ASF infrastructure, which remains managed by the Foundation during incubation.

The Apache Way in Practice

  • Transparency: discussions and decisions on public lists.

  • Consensus: seek agreement; hold formal votes when needed.

  • Meritocracy: influence earned through contribution.

  • Community over Code: people and collaboration come first.

  • Vendor Neutrality: avoid single-company dominance.

Releases

  • Each release involves two votes:

    • 1️⃣ Podling (PPMC) vote on dev@ (72-hour minimum).

    • 2️⃣ IPMC vote on general@incubator.apache.org.

  • Must receive at least 3 +1 votes and more +1s than -1s.

  • A -1 vote is not a veto, but signals a concern to resolve.

  • Include the incubating name and ASF disclaimer.

  • Source releases must be staged under dist/dev/incubator/<podling>.

  • Choose the appropriate disclaimer: standard or work-in-progress.

Reporting

  • File monthly reports for the first 3 months, then quarterly.

  • Summarize community growth, releases, and challenges.

  • Include mentor comments where appropriate.

  • Reports are reviewed by the IPMC and aggregated for the ASF Board.

Common Pitfalls

  • Making decisions in private chats or company channels.

  • Delaying the first release too long.

  • Expecting mentors to handle process work.

  • Ignoring reports or feedback.

  • Not taking care of project branding and trademarks.

Graduation

Podlings are ready to graduate when they:

  • Have a diverse and active community.

  • Operate independently using ASF practices.

  • Have made multiple compliant releases.

  • No longer rely on mentor oversight.

Graduation requires an IPMC vote and ASF Board approval.

Working in a Global Community

  • Apache is global — account for time zones, languages, and norms.

  • Be inclusive and avoid culture-specific references.

  • Respect volunteer time and differing availability.

Key Takeaways

  • Incubation is about community as much as code.

  • The Apache Way guides all decisions.

  • Mentors and the IPMC are here to help.

  • Graduation is the destination — openness is the path.

Getting Help

  • Ask mentors on the dev@ list — they’re your first contact.

  • Use general@incubator.apache.org for Incubator-wide questions.

  • Browse lists.apache.org for archived examples.

  • Check the Incubator Wiki for templates, FAQs, and checklists.

Resources

Next Steps

  • Read the Podling Orientation Guide.

  • Watch the PPMC Onboarding presentation.

  • Explore ASF Values to understand ASF culture.

  • Stay active on dev@ — transparency builds trust and trust builds community.

  • Reach out to your mentors early and often — collaboration is the Apache Way.