You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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 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.
The text was updated successfully, but these errors were encountered: