From 4f826841989ba9251ae7236fa49e78d80af2cafb Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Tue, 12 Sep 2023 14:18:01 -0500 Subject: [PATCH] Update oncall rotation documentation (#13888) --- handbook/engineering/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 5005e0d1ca..81f2ad3fb3 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -299,6 +299,10 @@ See [the internal Google Doc](https://docs.google.com/document/d/1FNQdu23wc1S9Yo Fleet team members can also subscribe to the [shared calendar](https://calendar.google.com/calendar/u/0?cid=Y181MzVkYThiNzMxMGQwN2QzOWEwMzU0MWRkYzc5ZmVhYjk4MmU0NzQ1ZTFjNzkzNmIwMTAxOTllOWRmOTUxZWJhQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) for calendar events. +New engineers are added to the oncall rotation by their manager after they have completed onboarding and at least one full release cycle. We aim to alternate the rotation between product groups when possible. + +> The oncall rotation may be adjusted with approval from the EMs of any product groups affected. Any changes should be made before the start of the sprint so that capacity can be planned accordingly. + ### Responsibilities - [Second-line response](#second-line-response)