Rename Category:Pods to Category:Cell

As part of the recent reorganization, Group::Organization was merged with Group::Pods. The term Pods conflicts with Kubernetes Pods and is not descriptive enough of the common goal of the team, which is to find a horizontal scaling solution. Thoughts on the exact reasoning for selecting Cell as a category name are summarised here and here.

TL;DR:

• Group name becomes Tenant Scale (#g_tenant-scale)
• Categories that the team owns are then Category:Organization and Category:Cell

References

• Organization and Pods team and category naming (gitlab-org/gitlab#391930 - closed)

Process

• https://about.gitlab.com/handbook/product/categories/#changes

Examples

• Rename Sharding team/category to Pods (#13367 - closed)
• Rename Manage:Workspace to Manage:Organization (#14254 - closed)

Approvals

• Chief Product Officer: David
• VP of Product: Mike
• Director of Product, Enablement: Josh
• Director of Engineering, Enablement: Chun
• Sr Manager of Product Design, Enablement: Taurie

Informed

• Chief Technology Officer: Joerg
• VP of Development: Christopher
• Director of Quality Engineering:
• Engineering Productivity (by @ mentioning @gl-quality/eng-prod)
• Product Marketing Manager relevant to the stage group(s): Saumya
• Senior Manager, Technical Writing
• Engineering Manager for Quality Engineering

Things to update

No workflow impact

• Handbook pages
  • https://about.gitlab.com/handbook/engineering/development/dev/manage/organization/
  • https://about.gitlab.com/direction/enablement/#data-stores
  • https://about.gitlab.com/direction/enablement/pods/
• Internal handbook pages
  • https://internal-handbook.gitlab.io/handbook/company/performance-indicators/product/enablement-section/
• docs.gitlab.com
  • https://docs.gitlab.com/ee/architecture/blueprints/pods/
• Update marketing material
  • Slide decks

Potential workflow impact

• stages.yml | MR
• categories.yml | MR
• spec/homepage/category_spec.rb: N/A
• Update policies/stages/report/quad-planning-issues.yml
• Tag the group Technical Writer in the merge request to ensure documentation metadata is updated after the category change is merged
• Templates
  • Feature flag issue template
  • Planning issue template
• Epics
• Issues
• Triage ops: Labels
  • category:pods >> category:cell
  • Ensure that GitLab Bot auto-labeling can be updated prior to the change | issue
• Update product_group RSpec metadata for E2E tests located in qa/qa/specs/features | MR
• Update Sisense
• Update CODEOWNERS