Rename group name from Enablement::Pods to Data Stores::Tenant Scale

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 Cells as a team name are summarised here and here.

TL;DR:

  • Group name becomes Cells (#g_cells) which is coherent with current group name of Pods: plural, we are meant to deliver many Cells, each Cell having many Organizations
  • Group name is after a key feature that we are meant to deliver
  • Categories that the team owns are then Category:Organization and Category:Cell

References

Process

Examples

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

Potential workflow impact

Communications

Announce in:

  • Slack: #s_enablement, #whats-happening-at-gitlab, #g_sharding, #development, #vp-development, #cto, #product
    • Proceeding Announcement
    • Finished Announcement
  • Engineering Week in Review
Edited by Arturo Herrero