At some point a PMC may want to join the Attic. The following defines a process to move that PMC into the Attic and gently close it down.
retire.py
, with other generated parts to move the project to the Attic.infrajiratext.py
.The following are useful svn/https locations:
xdocs
, generated html in docs
Check previous Board minutes to confirm the "terminate" resolution passed. The minutes are available from the following sources:
However note that the most recent meeting minutes are not published until the following meeting at the earliest
Check that Secretary removed the PMC from https://svn.apache.org/repos/private/committers/board/committee-info.txt
This automatically removes VP entry on https://www.apache.org/foundation/ and project from https://www.apache.org/#projects-list navigation
Let the users know that the PMC is moving into the Attic. Use the following template:
A heads up for the ${project} user community that the ${project} PMC 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 https://attic.apache.org. You can follow this process in JIRA: https://issues.apache.org/jira/browse/ATTIC-${#} Thanks, ${Name} on behalf of ${project} + the Attic.
Remember to subscribe to the user list: use Whimsy Mailing List Self-subscription to avoid moderation (if the project hasn't been removed yet).
Also bear in mind that the user mailing list may already know and you can skip this stage, or you can get help from project having asked to move to the Attic. Make sure you read that thread if it does exist.
The Attic website is built using Anakia. Anakia is an old site technology built on top of Apache Velocity. You can get the source for the site from Subversion:
svn co https://svn.apache.org/repos/asf/attic/site
You can generate the required changes using the Python3 retire.py
script as follows:
./retire.py id1 [id2...]
This should generate the following files for each ID, as well as updating xdocs/stylesheets/project.xml:
ID.jira.tmp
xdocs/flagged/ID
xdocs/projects/ID.xml
cwiki_retired/WIKI_ID.txt
N.B. The code does not (yet) allow for wiki aliases. For example, eagle used EAG as the wiki name.
Review the changes in xdocs/
, then commit to svn.
The ID.jira.tmp
file is text that can be copy-pasted into a JIRA description. It should be deleted after use, and not committed to SVN
The buildbot job will build the site and commit the result which will be published soon after
The files referenced are in https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk, which every Apache committer can update.
Identify whether the project has a DOAP file (see the <comdev repo>/projects.apache.org/data/projects.xml file if update the rdf file with PMC to the Attic and add a category of retired:
pmc change: <asfext:pmc rdf:resource="http://attic.apache.org" /> new category: <category rdf:resource="http://projects.apache.org/category/retired" />
You can use script/project2attic.py
to prepare the update that you'll just need to review and commit
Announce that the project is now retired. Consider the following template.
Sometimes, the user mailing list will not be shut down. If that is the case, it should be mentioned in the announce. e.g. add "The user mailing list remains open." after "change in url." below.
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 efforts. You can read more about ${project}'s retirement at: https://attic.apache.org/projects/${project}.html The project's resources will continue to be available in a read-only state - website, mailing lists, wikis, git, 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: https://attic.apache.org/ Thanks, ${NAME} 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.