What Are the Responsibilities of the Apache Incubator?

Updated

The Apache Incubator is the entry path into the Apache Software Foundation (ASF) for projects that want to join. It helps incoming projects, called "podlings," adopt the Apache style of governance and operation and guides them toward becoming top-level ASF projects (TLPs). Its formal responsibilities are welcoming new podlings, guiding their communities under the Apache Way, reporting monthly to the ASF Board, recommending graduation (or retiring podlings when needed), and accepting intellectual property donations. This overview is for anyone evaluating whether the Incubator fits their project or trying to understand how the ASF onboards new work.

The five core responsibilities

The Incubator's own site lists these duties:

Responsibility What it means in practice
Welcoming new podlings Bringing accepted projects into the ASF as podlings
Guiding governance and community growth Helping podlings operate according to the Apache Way, the ASF's philosophy and guidelines for collaborative development
Monthly board reporting Reporting to the ASF Board each month on podling progress
Graduation and retirement Recommending podlings that should graduate to TLPs; retiring podlings when needed
Accepting IP donations Receiving intellectual property donations into the Foundation

How the Incubator carries this out

The Incubator assigns mentors to every podling. Mentors act as liaisons between the podling and ASF teams such as the Incubator PMC and the Infrastructure team, facilitating the podling's operations and ongoing growth. In other words, the responsibilities above are not abstract: a named mentor is the podling's day-to-day connection to the rest of the Foundation.

What this means if you are considering joining

The responsibilities map directly onto what a prospective podling must do:

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

Expect the process to be about community and governance as much as code: the Incubator's job is to see that your project can govern and grow itself the Apache way before it graduates.

Where to go next

The Incubator site also publishes guidance on proposal creation, IP clearance, branding, release management, successful graduation, and retirement, plus a list of current podlings and the Clutch report. If your question is "is the ASF right for us?" start with the cookbook; if it is "what are we signing up for?" the responsibilities table above is the short answer.