Moving a PMC to the Attic
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.
1. A PMC decides to move to the Attic
- Conduct a discussion on the public developer list whether to dissolve the PMC. 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.
- Consider whether any contributors might be candidates for promotion to committers or PMC members.
- Conduct a PMC vote on the public dev list.
- If the PMC votes to dissolve the PMC and move to the Attic, inform the board of the successful vote on board@ mailing list (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 to the Attic. They should inform the board as above, noting that the vote failed to get enough votes.
2. If the board approves the resolution
The Attic team will open an Attic JIRA item - Move ${project} to the Attic.
Issue content typically contains following steps:
- # Confirm Board Resolution
- # Create project page on Attic site: https://attic.apache.org/projects/${project}.html
- # Inform users of the move to the Attic
- # Update the project DOAP files (if any) or copy to projects-override
- # Get infra lock down project’s resources
- # Announce on announce at apache.org
See Attic Process - How To for a description of each step that the Attic team will follow.
Getting help from terminating project is welcome, particularly on informing users step or any other useful action at project’s level like modifying DOAP file. Don’t hesitate to discuss through the Jira issue.
