Loading content/handbook/engineering/development/sec/software-supply-chain-security/oncall/coverage-and-scheduling.md +3 −3 Original line number Diff line number Diff line Loading @@ -34,9 +34,9 @@ A typical schedule shows: The SSCS rotation provides coverage Monday-Friday, 24 hours each day. Coverage is split into three 8-hour regional blocks: - **APAC Team**: Best effort basis - Coverage: UTC 23:00 - 07:00 - **EMEA Team**: Coverage: UTC 07:00 - 15:00 - **AMER Team**: Coverage: UTC 15:00 - 23:00 - **APAC** (Best effort basis): UTC 23:00 - 07:00 - **EMEA**: UTC 07:00 - 15:00 - **AMER**: UTC 15:00 - 23:00 You're expected to respond during your assigned 8-hour block, which should align closely with your normal work hours. Based on your residence (APAC, EMEA or AMER), you'll be assigned to the region that matches your timezone. Loading content/handbook/engineering/development/sec/software-supply-chain-security/oncall/joining-and-leaving-rotation.md +3 −3 Original line number Diff line number Diff line Loading @@ -62,21 +62,21 @@ The frequency depends on your region and team size. Here's the current distribut **APAC (Asia-Pacific)** - Coverage: 02:00-10:00 UTC - Coverage: UTC 23:00 - 07:00 (Best effort basis) - Approximately 6-7 weeks per person per year - Team size: 7 engineers (Authentication: 2, Authorization: 3, Pipeline Security: 2) - Higher frequency due to smallest regional team size **EMEA (Europe/Middle East/Africa)** - Coverage: 10:00-18:00 UTC - Coverage: UTC 07:00 - 15:00 - Approximately 5-6 weeks per person per year - Team size: 10 engineers (Authentication: 6, Authorization: 1, Pipeline Security: 3) - Medium frequency **AMER (Americas)** - Coverage: 18:00-02:00 UTC - Coverage: UTC 15:00 - 23:00 - Approximately 4-5 weeks per person per year - Team size: 12 engineers (Authentication: 3, Authorization: 5, Pipeline Security: 4) - Lower frequency due to largest regional team size Loading content/handbook/engineering/development/sec/software-supply-chain-security/oncall/rotation-leader.md +3 −3 Original line number Diff line number Diff line Loading @@ -44,21 +44,21 @@ Coverage is Monday-Friday only (no weekends in the initial iteration). Your rotation targets specific frequency based on team size and regional coverage needs: **APAC Team (Asia-Pacific)** **APAC (Asia-Pacific)** - Coverage: UTC 23:00 - 07:00 (Best effort basis) - Approximately 6-7 weeks per person per year - Current team size: 7 engineers - Higher frequency due to smallest team size **EMEA Team (Europe/Middle East/Africa)** **EMEA (Europe/Middle East/Africa)** - Coverage: UTC 07:00 - 15:00 - Approximately 5-6 weeks per person per year - Current team size: 10 engineers - Medium frequency **AMER Team (Americas)** **AMER (Americas)** - Coverage: UTC 15:00 - 23:00 - Approximately 4-5 weeks per person per year Loading Loading
content/handbook/engineering/development/sec/software-supply-chain-security/oncall/coverage-and-scheduling.md +3 −3 Original line number Diff line number Diff line Loading @@ -34,9 +34,9 @@ A typical schedule shows: The SSCS rotation provides coverage Monday-Friday, 24 hours each day. Coverage is split into three 8-hour regional blocks: - **APAC Team**: Best effort basis - Coverage: UTC 23:00 - 07:00 - **EMEA Team**: Coverage: UTC 07:00 - 15:00 - **AMER Team**: Coverage: UTC 15:00 - 23:00 - **APAC** (Best effort basis): UTC 23:00 - 07:00 - **EMEA**: UTC 07:00 - 15:00 - **AMER**: UTC 15:00 - 23:00 You're expected to respond during your assigned 8-hour block, which should align closely with your normal work hours. Based on your residence (APAC, EMEA or AMER), you'll be assigned to the region that matches your timezone. Loading
content/handbook/engineering/development/sec/software-supply-chain-security/oncall/joining-and-leaving-rotation.md +3 −3 Original line number Diff line number Diff line Loading @@ -62,21 +62,21 @@ The frequency depends on your region and team size. Here's the current distribut **APAC (Asia-Pacific)** - Coverage: 02:00-10:00 UTC - Coverage: UTC 23:00 - 07:00 (Best effort basis) - Approximately 6-7 weeks per person per year - Team size: 7 engineers (Authentication: 2, Authorization: 3, Pipeline Security: 2) - Higher frequency due to smallest regional team size **EMEA (Europe/Middle East/Africa)** - Coverage: 10:00-18:00 UTC - Coverage: UTC 07:00 - 15:00 - Approximately 5-6 weeks per person per year - Team size: 10 engineers (Authentication: 6, Authorization: 1, Pipeline Security: 3) - Medium frequency **AMER (Americas)** - Coverage: 18:00-02:00 UTC - Coverage: UTC 15:00 - 23:00 - Approximately 4-5 weeks per person per year - Team size: 12 engineers (Authentication: 3, Authorization: 5, Pipeline Security: 4) - Lower frequency due to largest regional team size Loading
content/handbook/engineering/development/sec/software-supply-chain-security/oncall/rotation-leader.md +3 −3 Original line number Diff line number Diff line Loading @@ -44,21 +44,21 @@ Coverage is Monday-Friday only (no weekends in the initial iteration). Your rotation targets specific frequency based on team size and regional coverage needs: **APAC Team (Asia-Pacific)** **APAC (Asia-Pacific)** - Coverage: UTC 23:00 - 07:00 (Best effort basis) - Approximately 6-7 weeks per person per year - Current team size: 7 engineers - Higher frequency due to smallest team size **EMEA Team (Europe/Middle East/Africa)** **EMEA (Europe/Middle East/Africa)** - Coverage: UTC 07:00 - 15:00 - Approximately 5-6 weeks per person per year - Current team size: 10 engineers - Medium frequency **AMER Team (Americas)** **AMER (Americas)** - Coverage: UTC 15:00 - 23:00 - Approximately 4-5 weeks per person per year Loading
