So updating with Sebb's response: Can be done by Attic:
- Create page on Attic site - Inform users - Delete from committee-info.txt (members) - Remove from www.apache.org navigation - Announce on announce at apache.org Needs permissions from Infra for Attic: - Update website with Attic notice - Update HEADER.html in downloads - Update the project DOAP file - 6 months+: strip dist/project and add a .htaccess redirect Needs to be done by Infra: - Point SVN mails to general at attic - Make SVN + JIRA/Bugzilla read-only - Turn off automated builds - Close down infrastructure resources - 6 months+: Consider deleting the user list With sites on the CMS, updating the website with an Attic notice is likely to be a challenge. Typically I did a search and replace on every .html page and inserted a <div> at the top of the page. Any thoughts from anyone CMS-knowledgable about whether it's best to try and do that in the CMS somehow, or perhaps to have a more programmatic notion that marks a site as retired and inserts a header? Hen
