Add Follow the Sun Coverage outline
Why is this change being made?
As we did in MVC - GitLab WebIDE support - Code Suggestions (gitlab-org&10549 - closed), we should consider keeping a log of how to approach the following sun rotation. This approach is used when Results are not-optional, it takes a level of burden and stress off the DRI group to prevent them from working around the clock.
This change should consist of three parts:
- Create a Page of Follow the Sun Coverage in this MR.
- On that page describe what Follow the Sun Coverage is and add a section about the Follow the sun pairing in this MR.
- Refer to Follow the Sun Coverage under the Bias for Action Sub Value as an example, we will update gitlab-com/content-sites/handbook!184 (closed) to handle that.
See:
- https://master-patch-9b14.about.gitlab-review.app/handbook/engineering/development/#follow-the-sun-coverage
- https://master-patch-9b14.about.gitlab-review.app/handbook/engineering/development/processes/follow-the-sun-coverage.html
Author Checklist
-
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
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by David O'Regan