Welcome to the Apache Incubator. This page introduces new podlings to the incubation process and the expectations of becoming an Apache project.

What Is a Podling?

  • A podling is a project in the Incubator, on its way to becoming an Apache Top-Level Project (TLP).
  • Incubation is not only about technology but 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 a self-governing 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 mentors and IPMC guidance.
  • Begin practicing open, list-based decision making.

Podling Project Management Committee (PPMC)

  • Includes committers, mentors, and other invited members.
  • Oversees the podling’s growth and governance.
  • Votes on releases and community decisions.
  • Works under oversight of the Incubator PMC (IPMC) until graduation.

The Apache Way in Practice

  • Transparency: discussions and decisions on public lists.
  • Consensus: seek agreement; formal votes when needed.
  • Meritocracy: influence earned through contributions.
  • Community over Code: long-term sustainability comes first.
  • Vendor Neutrality: no single company dominance.

Releases

  • Podlings must make ASF-compliant releases during incubation.
  • Require 3 +1 IPMC votes for approval.
  • Must include the (incubating) disclaimer.
  • First release expected within ~6 months of entry.

Reporting

  • Podlings file monthly reports for the first 3 months, then quarterly.
  • Reports cover community growth, releases, challenges, and mentor feedback.

Graduation

Podlings are ready to graduate when they:

  • Have a diverse and active community.
  • Operate independently under ASF practices.
  • Have made multiple compliant releases.
  • No longer rely on mentor oversight.

Graduation requires an IPMC vote and ASF Board approval.

Legal & Policy Requirements

  • Licensing: provenance and correct license headers.
  • CLAs: individual and corporate contributor agreements as needed.
  • Trademarks: project name and branding must align with ASF rules.
  • Cryptography: follow ASF export and distribution requirements.

Cultural Awareness

  • Apache is global: account for time zones, languages, and different work norms.
  • Be inclusive and avoid culture-specific or local references.
  • Respect different levels of availability (volunteers vs. paid contributors).

Key Takeaways

  • Incubation is about community building as much as code.
  • The Apache Way should guide daily practice.
  • Mentors and the IPMC are here to help.
  • Every podling’s journey is unique, but graduation is the goal.

Resources

  • No labels