Opened 13 months ago

Last modified 12 months ago

#23007 needs_review defect

Get a second blog maintainer

Reported by: arma Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Blog Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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?

Child Tickets

Change History (4)

comment:1 Changed 13 months ago by isabela

I will try emailing the hosting people, I think I have access to the hosting page. Mike could help too, I think.

comment:2 Changed 13 months ago by hiro

Hi,

I will get in touch with them now. Sorry for being late about this.

comment:3 Changed 13 months ago by hiro

Following up with pantheon and the cron issue they mention. More updates soon.

comment:4 Changed 12 months ago by hiro

Status: newneeds_review

The issue was solved on pantheon side. It was some chron process hanging in there. I am ok on having a second blog maintainer. Although in this case pantheon people can do most of the things as we can't even access the machine where the blog lives.

Another discussion would be if we actually like this setup in which we have a bit less control on the infrastructure we use, but also a server less to maintain. There are pro and cons.

Note: See TracTickets for help on using tickets.