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 to be:

"responsible for the oversight of projects which otherwise would not have oversight; and be it further ... is not authorized to actively develop and release the projects under its oversight"

It is intended to:

  • Be non-impacting to users
  • Provide restricted oversight for these codebases
  • Provide oversight for active user lists with no Project Management Committee (PMC)

It is not intended to:

  • Rebuild community
  • Make bugfixes
  • Make releases

Getting into the Attic

There 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.

In either case, the following may be useful: Template Board Resolution.

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 Attic

This is defined in the separate process document.

Process of leaving the Attic again

Options are:

  • Forking the project - we'll link to any forks which have been created so please let us know
  • Restarting the community in the Apache Incubator
  • Recreating a PMC for the project

Contacting the Attic PMC

The Attic is managed by a Project Management Committee (PMC). Discussions are found on the general@ mailing list and you are welcome to subscribe.

Attic FAQ

Please ask away on the list and we'll grow this FAQ.