Rename Sharding team/category to Pods

Summary

As we look beyond the CI decomposition rollout, the Sharding team will begin exploring a pods architecture for continuing to scale GitLab.com. To reflect that this will be the team's focus, as opposed to further sharding (which the team may still end up working on), we will rename the product category and team accordingly.

In the most recent Pods/CEO sync, several name options were proposed and "Pods" was selected with support from the CEO.

Process and Examples

• https://about.gitlab.com/handbook/product/product-categories/#changes
• Rename Telemetry to Product Analytics
• Rename Product Analytics to Product Intelligence

Approvals

• CEO (Sid) - Note: Sid provided his approval and support for the new team name in the Pods/CEO sync on 2022-04-26 (recording).

Informed

• CTO (Eric)
• VP Product (David)
• VP Development (Christopher)
• VP Infrastructure (Steve)
• VP Quality (Mek)
• Engineering Productivity
• Product Marketing Manager

Things to update

No Workflow Impact

• Handbook pages
  • /handbook/engineering/development/enablement/sharding/ and /handbook/engineering/development/enablement [!104745 (merged)]
  • /direction/enablement/sharding [!105532 (merged)]
• docs.gitlab.com
• Greenhouse Job Description and Title

Potential Workflow Impact

• stages.yml and category.yml [!105685 (merged)]
• GitLab projects
  • gl-retrospectives and async-retrospectives
  • https://gitlab.com/gitlab-org/sharding-group
    • Access Request
  • https://gitlab.com/gitlab-org/sharding-group/group-tasks
    • Access Request
  • https://gitlab.com/gitlab-org/sharding-group/group-tasks
• Gitlab Groups
  • https://gitlab.com/gitlab-org/sharding-group
  • https://gitlab.com/gitlab-org/sharding-group/group-tasks
• labels - Issue: gitlab-org/quality/triage-ops#1065 (closed)
  • group::sharding label
  • sharding::active
• Slack channel names
  • Change Slack channel references in stages.yml (!108351 (merged))
  • Geekbot
• Triage ops
  • Issue: gitlab-org/quality/triage-ops#1065 (closed)
• Update team.yml for relevant team members (!108151 (merged))
• Update Ally.io
  • Requested access.
• Update CODEOWNERS - No changes needed.
  • gitlab-comwww-gitlab-com
  • gitlab-org/gitlab
• Update BambooHR
  • Couldn't find any references to Sharding
• Update Workday
  • Slack Message to #people-connect
• YouTube Unfiltered Playlist.
  • Create a new playlist
• Create Pods: Build board
• Team Page
  • Create MR when changes being referenced are completed.
  • https://about.gitlab.com/handbook/engineering/development/enablement/data_stores/pods

Added after closing

• @sharing-group Slack Group

Communications

• Announce in:
  • Slack: #s_enablement, #whats-happening-at-gitlab, #g_sharding, #development, #vp-development, #cto
    • Proceeding Announcement
    • Finished Announcement
  • Engineering Week in Review

Proceeding Announcement

Over the next few days I will be going through the process of renaming the Sharding Group to the Pods Group (#13367 (closed)). As you can see from the Issue this includes changes to Groups and Projects as well as 3rd party systems. I will keep the Issue updated on the progress of the different tasks and will update here again once they are all complete. If you have any questions, feel free to ask me.

Finished Announcement
Regarding renaming the Sharding Group to Pods (#13367 (closed)). All the tasks on the Issue are complete. Please let me know if there are any problems as a result of the work done here or you see anything that has been missed.