Policies
- If the request is because the project is hosted elsewhere, keeping it creates confusion.
- If the project was created by mistake, there is no problem removing it.
Otherwise
- http://mail.gnu.org/archive/html/savannah-hackers/2002-12/msg00030.html
- Looks like SF had the same policy
Note: because of this policy we can't give complete control over to repository to admins. This is tedious, so I suggest that admins should generally be able to reset their project without our intervention. However, it would be good to back up to previous repository in such cases. We still should not give complete access to project members, nor direct write access when hooks are involved (we do not wish to grant any kind of local shell access).
Doing it
Steps to remove a project:
- Authentify the project administrator (eg. have him/her send a GPG signed confirmation)
- Mark it as deleted in Savane, so nobody change it
- Ask the project admin about deleting the mailing lists
- run infra/maintenance/delete_project.sh projname
- a backup of the project's sources will be put in ~/deleted-projects/
- ??? mailing lists are still present in the database after project deletion, we should remove them as well