At some point a project will vote to join the Attic. The following defines a process to move that project into the Attic and gently close it down.

  1. A Project PMC decides to move to the Attic.
    • Conduct a discussion on whether to dissolve the PMC and move the project to the Attic on the public dev list. Do not conduct it on the private PMC list.
    • Consider an appeal to the user list for interested users to provide their interest in helping out more.
    • Conduct a PMC vote on the public dev list.
    • If the PMC votes to dissolve the PMC and move the project to the Attic, inform the board of the successful vote (linking or forwarding the 'successful' vote) and add a resolution to dissolve the PMC to the next board meeting agenda.
    • If the PMC can't get enough people to vote to dissolve the PMC (and there are not three -1 votes), then that is grounds for moving the project to the Attic. They should inform the board as above, noting that the vote failed to get enough votes.
  2. If the board approve the resolution, open a JIRA item - 'Move ${project} to the Attic'.
    Add the following items to the details:
  3. Open an Infrastructure JIRA issue identifying the resources that need turning off/making read only. Typically:
    • Remove files from and add a .htaccess containing:
      RedirectMatch permanent .*${project}.html
    • Closing down of dev@, commits@ and private@ mailing lists
    • Close down the user mailing list (unless still active - in which case propose a moderator to Infra)
    • Make JIRA|Bugzilla read-only
    • Make the wiki (Confluence|Moinmoin) read-only
    • Delete unix/ldap group
    • Turn off automated builds

How To: Confirm Board Resolution (if TLP)

Check previous Board minutes (in SVN or to committers@) to confirm project was retired.

How To: Delete from committee-info.txt

Someone needs to remove the PMC from the committee-info file.

If the outgoing PMC chair is not chair of any other PMCs, then ask infra to adjust the 'pmc-chairs' LDAP group accordingly.

Remove VP entry on

Access the CMS here and update the text.

How To: Inform users of the move to the Attic

You should let the users know that the project is moving into the Attic. Consider the following template:

A heads up for the ${project} user community that the ${project} project has 
been 'moved to the Attic'. This means that the ${project} developers (more 
formally its Project Management Committee) have voted to retire ${project} 
and move the responsibility for its oversight over to the Attic project.

Loosely speaking this means that the projects resources will be moved to a 
read-only state.

You can read more about the Apache Attic and the process of moving to the 
Attic at

You can follow this process in JIRA:${#}


${Name} on behalf of ${project} + the Attic.

Bear in mind to subscribe to the user list to avoid moderation. Also bear in mind that the user mailing list may already know and you can skip this stage. Make sure you read that thread if it does exist.

How To: Create page on Attic site

A simple page should be created on the Attic site. Use existing pages as templates and make sure you link to the Apache Archives to get the software. While you are here, add the user mailing list to the list of sites under the Attic's oversight.

How To: Obtain SVN karma

Change asf-authorization-template so that the attic-pmc has karma instead of the defunct project.

How To: Point SVN mails to general at attic

Change asf-mailer.conf so that SVN notification emails go to the Attic general list.

How To: Adding an Attic notice to the website

A banner needs to be added to the website indicating that it is now in the Attic. This needs to be done in a lightweight way without having to learn how the project manage their site. One way is to (carefully!) search and replace for a common tag such as the body tag. Another is to edit the CSS.

Site may be published through websites svn or other means: need investigation on each case.

How To: Update the project DOAP file

Identify whether the project has a DOAP file (see the projects.xml file and old files.xml file) and if it does, update the PMC to the Attic and add a category of retired:

pmc change:    <asfext:pmc rdf:resource="" />
new category:  <category rdf:resource="" />

How To: Move committee's PMC data file to retired

If committee appears in committees list, moving data to retired will remove it from the list. Notice that this task is being automated, then not necessary to track any more in the future...

Comment PMC data files index entry (see the committees.xml file and old pmc_list.xml file) and move PMC data file from committees/ directory to committees-retired/.

How To: Remove from navigation

As a retired project, a link on the front page of Apache site is no longer necessary. Remove the link and regenerate the main Apache site. This is done via the trunk/templates/blocks/projects.mdtext of the CMS.

It's also worth checking that the VP link from has been removed.

How To: Announce on

Announce that the project is now retired. Consider the following template.

Announcing that the Apache ${project} committers have voted to retire
the project due to inactivity. ${project} was {boilerplate}.

Retiring a project is not as simple as turning everything off, as
existing users need to both know that the project is retiring and
retain access to the necessary information for their own development

You can read more about ${project}'s retirement at:${project}.html

The user mailing list remains open, while the rest of the project's
resources will continue to be available in a read-only state -
website, wikis, svn, downloads and bug tracker with no change in url.

Providing process and solutions to make it clear when an Apache
project has reached its end of life is the role of the Apache Attic,
and you can read more about that at:


on behalf of the Apache Attic and the now retired Apache ${project} project

It's important to include the boilerplate from the project's site so people know what we're talking about.