Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B blog
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Web
  • blog
  • Issues
  • #23007
Closed
Open
Created Jul 22, 2017 by Roger Dingledine@armaMaintainer

Get a second blog maintainer

We try to have two maintainers for every service: https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure

I think only hiro knows how to log in to the blog and fix stuff? Or worse, there is no such thing as logging into the blog (i.e. there is only the web interface), and fixing things requires filing tickets with the current hosting provider? And in that case the right answer is to document how to file those tickets, who our contacts are, etc, so somebody else can do this process if needed?

Is Mike this person?

Assignee
Assign to
Time tracking