Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StatusPage: What is an Incident? #2303

Closed
MattIPv4 opened this issue Apr 22, 2020 · 1 comment
Closed

StatusPage: What is an Incident? #2303

MattIPv4 opened this issue Apr 22, 2020 · 1 comment
Labels

Comments

@MattIPv4
Copy link
Member

Main issue: #2265

Creating a dedicated issue to house discussion around what exactly an incident is going to be defined as, and the more general policy that needs to be put in place for use of the status page.

Ref: #2265 (comment) & #2299 (comment)

As a starting point for defining this, I gave the following:

I think a lot of that comes down to human judgement of each situation, but I guess rather vaguely, I'd probably define an incident as a public-facing issue (optionally, that people are going to notice or is going to affect a lot of people).

So, for example, a CI machine crashing wouldn't really be an incident that requires posting on the status page and sending notifications out to the community, but downloads failing (which started this thread) would be something that should have an incident made for and notifications sent out.

I welcome all thoughts and feedback on what exactly an incident should be defined as and how the status page should be used with this in mind.

@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant