The Apache Attic
The Apache Attic was created in November 2008 to provide process and solutions to make it clear when an Apache project has reached its end of life. Specifically:
It is intended to:
It is not intended to:
Getting into the AtticThere are two expected mechanisms by which a project may enter the Attic. Either the managing Project Management Committee (PMC) decides it would like to move the project, or The Apache Software Foundation’s board dissolves the PMC and chooses to move the project. First step is to add a suitable resolution to the next board agenda: see the Template Board Resolution. Once the submitted resolution has been approved during a board meeting, the Attic project starts executing the move. When should a project move to the Attic?Projects whose PMC are unable to muster 3 votes for a release, who have no active committers or are unable to fulfill their reporting duties to the board are all good candidates for the Attic. Process of moving into the AtticThis is defined in greater details in the separate process document. Process of leaving the Attic againOptions are:
A receiving PMC must be willing to assume all responsibilities that come
with running a project: maintain code, answer questions, fix bugs,
publish releases etc. Contacting the Attic ProjectThe Attic is a project as any other:
Retired Incubator ProjectsThe Apache Incubator project is the entry path into The Apache Software Foundation for projects and codebases wishing to become part of the Foundation’s efforts. Not all projects ‘graduate’ out of the Incubator; some are retired instead. Those retired projects remain under Incubator oversight: the list may be found on the Incubator’s Projects page. |