[status page idea] Sharing common ecosystem infra outage observations via status.infra.aio-libs.org

[webknjaz]

Earlier today https://status.python.org/incidents/0jzvfb9tnqmv / python/cpython#158554 happened. And it cascaded into many Sphinx builds in CIs (GHA and others) and RTD failing when they used intersphinx (and strict nitpicky mode with failures on warnings).

Many people are exposed to 1-2 projects and end up having to research causes of such failures individually on their own. Meanwhile, I have often known the answer, having seen it across dozens of projects. So I've sometimes shared such infra-related insights via announcements: https://github.com/orgs/aio-libs/discussions/categories/announcements?discussions_q=break+category%3AAnnouncements (some are lost from pre in-settings times).

It occurred to me that it might be a good idea to have a status page for exposing such things that the maintainers and triagers could consult or add information to. I figured, I'd rather not maintain a full web server but a static web site on gh-pages, so this is what a simple search returned:

• https://github.com/jayfk/statuspage / https://jayfk.github.io/statuspage-demo/
• https://github.com/statsig-io/statuspage / https://status.statsig.com

Thoughts?

cc @achimnol @bdraco @Dreamsorcerer @jakob-keller @jettify @Nothing4You @mjpieters @aio-libs/admins @aio-libs/sprinters @aio-libs/triagers

[Dreamsorcerer]

Might be useful. I'll leave it to you if you want to try something out.

[wbarnha]

I'm in favor of it! I think a status page could have helped me during https://www.reddit.com/r/Python/comments/1jiy2sm/setuptools_7801_breaks_the_internet/, when a bad setuptools update made everyone come to me and ask, "hey why is this broken?"
"I dunno, I just work here." (paraphrase/embellishment)

[webknjaz]

Oh yeah, I had to educate people in the issue: pypa/setuptools#4910 (comment)