Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • TPA team TPA team
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 180
    • Issues 180
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

Admin message

GitLab has been upgraded GitLab 16, please report any issues!

  • The Tor Project
  • TPA
  • TPA teamTPA team
  • Issues
  • #29304
Closed
Open
Issue created Feb 01, 2019 by Jens Kubieziel@qbi🤸🏽

Manage the lifecycle of systems

During the sysadmin meeting in Brussels we discussed our infrastructure. Systems are managed by service admins/owners. They sometimes disappear or services become irrelevant. This means we have systems without proper owner which are rotting over time.

To better handle such systems we decided that systems like $host.torproject.org should have an expiration date which is initially one or two years in the future. When the expiration date is near the service owner receives an email informing about the possible shutdown and the means to prevent it (write an email answer to tpa). If the mail is answered the expiration date will be prolonged. If not, the system will be deactivated. The deactivation can easily be revoked. However after some more time without any feedback the host will be decommissioned.

This ticket is to track the several steps for implementing this new policy.

Assignee
Assign to
Time tracking