launchpad-dev team mailing list archive

[Matthew Revell <matthew.revell@xxxxxxxxxxxxx>]

Howdy,

I want us to have one place where anyone in the Canonical LP team, and
related people such as the sys admins (LOSAs), can announce
service-affecting issues.

The most important thing, for me, is that someone should be able to
check one source and, if there's nothing there, be reasonably sure
that the issue they've experienced is neither planned nor known about
by Canonical people. So, we need a place to do that and also a
process.

I think the easiest way to do this is to set up an identi.ca account
as that give us:

* A single page where you can find the latest status info
(identi.ca/launchpadstatus)
* Forwarding to a Twitter account (twitter.com/launchpadstatus)
* An RSS feed (https://identi.ca/api/statuses/user_timeline/launchpadstatus.rss)
* No reliance on Launchpad in order to function.

As a bonus, we don't have to spend ages discussing how an automated
status page would work ;)

Right now, we have a page on the blog (/maintenance), a
"notifications" category on the blog, the general Launchpad
Twitter/identi.ca accounts, the launchpad-announce list.

Anything that requires more explanation could still be posted to the
notifications of the blog and anything that pretty much every LP user
needs to know about should go out to the -announce list. I'm not sure
what to do with the maintenance page, other than move it to the dev
wiki; I think we could use it to list planned maintenance times, as we
do now, but the identi.ca page should do that. The only advantage, I
see, of retaining the maintenance page is that it allows us to show
fairly far off into the future what's planned, whereas the identi.ca
account would be a moving target.

The process side would be fairly simple; I'll work something out if
people feel this idea is a go-er.

Any thoughts?

-- 
Matthew Revell - Launchpad.net - free software collaboration and project hosting