What Is the Apache Incubator?

Updated

The Apache Incubator is the entry point into the Apache Software Foundation (ASF) for projects that want to join it. It provides services to incoming projects, called "podlings," helping them adopt the Apache style of governance and operation and guiding them to the resources they need to become top-level ASF projects (TLPs). Each podling is assigned mentors who act as liaisons between the podling and ASF teams such as the Incubator PMC and the Infrastructure team.

What the Incubator actually does

The Incubator's stated responsibilities are:

  • Welcoming new podlings into the ASF.
  • Guiding podlings to govern and grow their communities according to the Apache Way, the ASF's philosophy and guidelines for collaborative development.
  • Reporting monthly to the board on podling progress.
  • Recommending to the ASF Board which podlings should graduate and become top-level projects.
  • Retiring podlings when needed.
  • Accepting intellectual property (IP) donations.

In short, it is both a gatekeeper and a coach: it evaluates incoming projects and IP, and it actively develops the community practices a project needs to operate as an ASF project.

Podlings, mentors, and TLPs

Three roles explain most of how the Incubator works:

Term What it means
Podling An incoming project under Incubation
Mentor A delegate assigned to a podling, acting as liaison to ASF teams (Incubator PMC, Infrastructure, etc.)
TLP A top-level ASF project — the graduation target for a podling

The mentor relationship is the practical core of the model. Rather than leaving a new community to figure out ASF processes alone, the Incubator connects it to people who can route questions and requests to the right ASF teams.

How a project gets started

The site lays out three starting steps:

  1. Read the cookbook. It helps potential podlings decide whether the ASF is a good fit and walks through the steps required to become a podling.
  2. Review the Incubation Policy. This outlines the rules for participation.
  3. Submit a proposal for your project to join the Incubator.

The site also points to presentations offering advice on applying to — and ultimately graduating from — the Incubator.

Who this is for

The Incubator is relevant if you maintain a project that wants to join the ASF and operate under the Apache Way, or if you are donating IP to the ASF. If you are simply looking to use Apache software, you don't need the Incubator — it serves projects and their communities, not end users. A useful first check is the cookbook's fit assessment: it is designed to help you decide whether the ASF is the right home before you invest in a proposal.

Where to go next

The site organizes its material into policies (including the Incubation Policy and IP clearance), proposal guidance, podling guides (community building, branding, publicity, code import, name search, websites, source control, release management, graduation, retirement, and transferring resources out of the Incubator), a current podling list, and role-specific guides for mentors, the Incubator chair, and PMCs. Start with the cookbook and policy; use the podling guides once your proposal is accepted.