Refactors and removes reliability/ handbook pages
Why is this change being made?
Implements the changes discussed in https://docs.google.com/document/d/1dpicmRIBkTMD1pELAwItArCF-A4RHhYdiaisFtiIyro/edit
This is a first pass of a major refactor because we have moved teams in what was previously called Reliability. Summary of changes:
- All content in https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/ is removed
-
https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/foundations and https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/general are now under
team/foundations
andteam/ops
respectively. - Sub-pages under /reliabilty, https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/issues/ and https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/sre-onboarding/ are moved under
team/ops
. - Updated links in https://handbook.gitlab.com/handbook/engineering/infrastructure/#organization-structure
TODO:
-
Decide what we want to do for dead links to /team/reliability
, and whether we want to make those updates part of this MR. We created a redirect for all paths under.../reliability/*
to a deprecation page -
Create followup issues to update the content of /team/ops
and/team/foundations
gitlab-com/gl-infra/mstaff#299 gitlab-com/gl-infra/mstaff#300 (closed) -
Decide whether to keep https://handbook.gitlab.com/handbook/engineering/infrastructure/team/ or make that change in a separate MR. The index page now is a pointer to the team chart -
Decide whether we are ok to remove https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/practices/ entirely and start from scratch. will remove -
Decide whether we are ok to remove https://handbook.gitlab.com/handbook/engineering/infrastructure/team/reliability/observability/ entirely and start from scratch. will remove
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.
CHANGEME - add the details saying why, not just what.
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Edited by John Jarvis