In October 2002 the Board of Directors of the Apache Software Foundation passed a resolution to establish the Apache Incubator PMC. Quoting the October 16th, 2002 Board Minutes:
…establish a Project Management Committee charged with accepting new products into the Foundation, providing guidance and support to help each new product engender their own collaborative community, educating new developers in the philosophy and guidelines for collaborative development as defined by the members of the Foundation, and proposing to the board the promotion of such products to independent PMC status once their community has reached maturity.
See the October 2002 link:https://www.apache.org/foundation/board/calendar-1999-2004.html#2002 [Board report] for the resolution.
The Incubator has the following responsibilities:
Welcoming new Podlings to become part of the Apache Software Foundation (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 the progress of Podlings.
Graduating Podlings to top level Apache Software Foundation projects.
Retiring Podlings when needed.
Accepting IP donations.
This document is the reference for the policies and procedures put in place by the Incubator PMC for the incubation process.
The document makes use of the terms MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL. Where these are capitalized, we use these terms as defined in RFC 2119.
Like many policy documents, this is not the most fun thing to read. Our Cookbook provides more concrete information on the incubation process.
This document contains the minimum requirements and processes that Podlings undergoing incubation MUST meet.
This document does not apply outside the process of incubation.
This document is the set of requirements for incubation. Where other documents say something different, this document is correct.
The Incubator PMC MUST approve changes to the content of this document.
Each Podling in Incubation MUST report to the Incubator PMC. Podlings SHALL report monthly for their first three months, after that quarterly. The Incubator PMC MAY, at their discretion, ask a Podling to report more frequently. The PPMC, with the mentor or mentors' help, MUST produce a report for the Incubator PMC detailing overall progress toward graduation and any issues the Podling has encountered.
While in Incubation, Podlings are constrained in the actions they can undertake.
There are restrictions on where Podlings can host their websites and what branding they can use on them.
Consult the Podling Websites Guide for the current policies on Podling websites.
There are restrictions about how Podlings can use their own and other ASF brands and names.
Consult the Podling Branding Guide for details.
There are restrictions about how Podlings can advertise themselves, especially in press releases related to Podlings.
Consult the Podling Publicity Guide for details.
Podlings MUST include a clear disclaimer on their website and in all documentation, releases and release announcements stating that they are in incubation.
A Podling has a choice of two disclaimers: a standard disclaimer or a work-in-progress disclaimer.
Podlings wishing to use a different disclaimer message MUST have the Incubator PMC approve it before use.
Podlings wanting to follow all ASF policy on releases SHOULD use the following text for all disclaimers (replace the underlined text as appropriate):
Apache Podling-Name is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
For releases, the text SHOULD be included in a separate DISCLAIMER file stored alongside the NOTICE and LICENSE files.
A Podling wishing to make releases that may not follow all ASF policy SHOULD use the following disclaimer (replace the underlined text where needed):
Apache Podling-Name is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision-making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Some of the incubating project’s releases may not be fully compliant with ASF policy. For example, releases may have incomplete or un-reviewed licensing conditions. What follows is a list of issues the project is currently aware of (this list is likely to be incomplete): List of known issues goes here
If you are planning to incorporate this work into your product/project, please be aware that you will need to conduct a thorough licensing review to determine the overall implications of including this work. For the current status of this project through the Apache Incubator, visit: https://incubator.apache.org/projects/Apache Podling-Name.html
For releases, the text SHOULD be included in a separate DISCLAIMER-WIP file stored alongside the NOTICE and LICENSE files.
Podlings are not yet fully accepted as official projects within the Apache Software Foundation. Podlings MUST NOT perform any ASF releases of software without the approval of the Incubator PMC. When a Podling decides it wants to make an ASF release, the Podling MUST hold a vote on their public dev list. At least three +1 PPMC votes are required (see the Apache Voting Process page) and more +1 votes than -1 votes. If the vote passes, the Podling MUST send a summary of that vote to the Incubator’s general list and request that the Incubator PMC approve the release. Three +1 Incubator PMC votes are required to approve a release. Below is an example showing how an incubating project managed this process:
Should the Incubator PMC vote to approve a release, the Podling MAY make that release available to the public under these conditions:
The release archive(s) MUST include the word "incubating" in the filename.
The release archive(s) MUST contain a disclaimer (see above), which SHOULD be placed in a DISCLAIMER or DISCLAIMER-WIP file.
Releases for the Podling MUST be distributed through http://www.apache.org/dist/incubator/Podling The Podling MAY choose to distribute approved releases through other channels by following the guidelines here.
After voting someone into the PPMC on the PPMC private list, the Podling MUST send a NOTICE email to the private@incubator list. Only after the NOTICE has been sent can the PPMC invite the new PPMC member to join the PPMC. See Voting in a new PPMC member.
As with all PMCs, the IPMC votes on proposed members on the private@incubator list. After a vote has finished, the IPMC MUST send a NOTICE email to the board before inviting the proposed member. Any ASF member can ask to be an IPMC member, without a vote, but the IPMC MUST still give notice to the board.
The Incubator PMC SHOULD notify a Podling of any policy violations. It MAY consider termination of a Podling that does not correct such violations.