2009/10/5 Martin Pool <[email protected]>: >> 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. > > I think that's a great idea ;-) > > We seem to already own @launchpad so I think we should just put it > there rather than fragmenting into a separate channel. I don't think > it's worth fragmenting them: people who want to know about Launchpad > generally should be interested in outages, and people who're wondering > "is it down or is it just me" won't mind also seeing feature news on > that page.
I've been wondering about that. In some respects I think it's useful to have a dedicated status feed -- for example, if someone wants to subscribe (either via identi.ca or the RSS feed) and see *only* status information. On the other hand, we do already post some status updates to our general Twitter and identi.ca accounts. On balance, I think there's a lot to be said for offering people the choice of tittle-tattle about Launchpad and a pure feed of status information. > It would be good to have links to there from the top of > help.launchpad.net and possibly even from the footer of every page. > (Why? Because tweets are a good way to communicate about stuff > generally, and because if it's failing and help.l.n can't be reached, > people may still have a page showing the footer.) Yeah, I like Kiko's suggestion of redirecting launchpad.net/status to the identi.ca or Twitter page (there's a political choice to be made, heh...) >> The process side would be fairly simple; I'll work something out if >> people feel this idea is a go-er. > > The only other thing to mention is that it's important that access to > this account be widely distributed to responsible people. I've > tweeted about lp being down or back up, but only in my personal > account. Yes, How about Canonical Launchpad team leads, yourself and the LOSAs? > The best process would be that someone check with LOSAs/etc what the > actual status is, but that tweeting the status is not a burden on the > people working to fix the problem. It should actually save them from > repeated questions. That makes sense. Thanks. -- Matthew Revell - Launchpad.net - free software collaboration and project hosting _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
