Tier 2 on call slack channels

Context

With the rollout of Tier 2 oncall, we have many different rotations to keep track of. It's important that people that need to find and communicate with members of a given rotation have a well defined and discoverable place to do so. We will thus create slack channels for each rotation. These slack channels also allow space for rotation members to swap shifts, talk about future coverage, and coordinate changes to the schedules.

Proposal

We standardize on the usage of slack channels and include a naming convention to make these channels easy to find if you know the rotation you are seeking. The process for onboarding a new rotation will include steps to add these slack channels.

Tasks

• Add a section to https://handbook.gitlab.com/handbook/engineering/infrastructure/incident-management/tier2-oncall/#expectations-for-rotation-owners regarding slack channel creation/maintenance.
• Update any other tier 2 onboarding material to ensure slack channels are made by rotation owners for any future rotations.
• Create Slack channels for:
  • DevOps Rails rotation #oc-rails
  • AI Rotation #oc-ai
  • Gitaly Rotation #oc-gitaly
  • DBO Rotation #oc-database-operations
  • Tier 2 general
• If appropriate, rename these rotation channels to match the new convention:
  • #eoc-general => oc-sre (not sure what the best name is here to match convention since oc-eoc is repetitive)
  • #im-general => oc-im