What is the problem?
SRE has launched a public-facing, high-level site status page at www.wikimediastatus.net.
We'd like to communicate this with on-wiki communities, while also setting expectations about its purpose.
It is primarily intended to serve the general public and the news media, although we expect community members to also use it as a resource -- but we certainly don't mean to replace, for example, on-wiki technical village pumps. The focus is on very visible/widespread outages, and not on issues that we expect to affect only sophisticated editors.
There's more background information, and process information on how we intend to use it, linked below:
https://wikitech.wikimedia.org/wiki/Wikimediastatus.net
https://office.wikimedia.org/wiki/SRE/Status_page
T202061: Implement an accurate and easy to understand status page for all wikis
How can we help you?
Provide guidance on how to best communicate the status page appropriately, and if any adaptations or adjustments should be made to how we implemented it.
What does success look like?
Community members know to check www.wikimediastatus.net to help answer concerns like "is Wikipedia down for everyone or just me?"
Community members know that "power user" functionality questions like "is automated citation generation broken" or "is mathematical formula rendering slow" or "are there problems with Job Queue" -- or questions about things that are not WMF-supported like "is there an issue with X bot or Y tool on Toolforge" -- won't be answered by the status page.
Community members are reasonably happy with the third-party service we selected and its inclusion of some other third-party services (like Google ReCAPTCHA, for one feature we disabled). Some background on why we chose Atlassian Statuspage are here on wikitech.
What is your deadline?
No firm deadline, although sooner would be better. Perhaps I'll suggest between two weeks and one month?