Collect Infrastructure/Development communication points
We have a number of different processes, mechanisms and meetings where we communicate across department. There are some efforts that are duplicated and others that rely on a key-person in order for them to be successful.
The purpose of this issue is to collect details about each of these processes to see if we need to consolidate, simplify, automate or rotate responsibility.
Item | Detail (what happens) | Purpose (why do we do this) | DRI | Recommendations | Links |
---|---|---|---|---|---|
Error Budget Monthly Report | List stage groups and their budget spend. Example: https://gitlab.com/gitlab-org/error-budget-reports/-/issues/4 |
Highlight spend on a monthly basis to remind stage groups of their commitment to reliability/availability. | Scalability (Rachel) | Increase visibility of open issues that contribute to Error Budget improvements #1506 (comment 858894412) | GitLab project |
Infradev Status Report | Weekly report of open Infradev issues, traffic share, error budget spend, corrective actions and incidents. Example: https://gitlab.com/gitlab-org/infradev-reports/-/issues/29 |
Generating project | |||
Infradev Issue Process | |||||
Corrective Action Issues | Issue list | ||||
Engineering Allocation Meeting | Meeting doc | ||||
Capacity Planning | Tamland | ||||
Incident Reviews | Meeting doc |
Edited by Liam McAndrew