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. Open a JIRA item - 'Move ${project} to the Attic'.
  2. Open a subtask: Board resolution successful.
  3. Ensure a Board resolution is on the next Board agenda. Once this is successful, continue.
  4. Open a ticket with Infra to have website and downloads chgrp'd to attic
  5. Open the following subtasks if needed, or just do them without an issue (see below for more information):
    • Inform users
    • Update website with Attic notice
    • Update HEADER.html in downloads
    • Update the project DOAP file
    • Point SVN mails to general at attic
    • Make SVN + JIRA/Bugzilla read-only
    • Delete from committee-info.txt
    • Create page on Attic site
    • Turn off automated builds
    • Remove from navigation
    • Close down infrastructure resources
    • Announce on announce at
  6. Open a new ticket with a due date 6 months in the future:
    • to consider deleting the user list
    • to strip dist/project and add a .htaccess containing:
      RedirectMatch permanent .*${project}.html

Informing users of the vote

Your first task is to 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.

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. The simplest way is to (carefully!) search and replace for a common tag such as the body tag.

Update HEADER.html in downloads

Another area to take note of the move to the Attic is the download section. Add or update a HEADER.html file that says something like:

<h1>Project Retired</h1>

<p>yyyy/mm/dd - Apache ${project} has been retired.</p>

<p>For more information, please explore the Attic at</p>

Update the project DOAP file

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

Point SVN mails to general at attic

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

Make SVN + JIRA/Bugzilla read-only

Someone with SVN karma karma should edit the asf-authorization file. The project's karma should be moved to read-only and the commit notification should be pointed to

Someone with JIRA or Bugzilla administrative rights should modify the project to be read-only. In JIRA this means moving it to the Retired category and applying the Read-Only Permissions. You should also note that the project is retired and read-only in the JIRA description:


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.

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.

Turn off automated builds

Research to find out if an automated build exists and get it turned off.

Remove from navigation

As a retired project, a link on the front page of Apache is no longer necessary. Remove the link and regenerate the main Apache site.

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

Close down infrastructure resources

Open a ticket with Infrastructure asking for resources to be closed down. This includes:

  • JIRA, Bugzilla + SVN if no one has karma
  • Closing down of dev@, commits@ and private@ mailing lists
  • Read-only in wiki (be it Confluence or Moinmoin)
  • Delete unix/ldap group
  • New moderator for user@ list

Bear in mind you will need to identify who is volunteering as the new moderator for the user@ list will be.

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.