Merge Category:Subgroups and Category:Projects to Category:Groups & Projects

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.

This issues handles merging the categories Category:Subgroups and Category:Projects into a single Category:Groups & Projects. This is intended to help support the consolidation of categories across Enablement as part of the recent move of Group::Organization to Group::Pods.

Why is this change needed?

  • Projects are not a marketing category and do not have a direction page
  • Groups and projects are strongly linked together. It is almost impossible to talk about one without talking about the other.

References

Process

Examples

Approvals

  • Chief Product Officer: David
  • VP of Product: Mike
  • Director of Product, Enablement: Josh
  • Director of Engineering, Enablement: Chun
  • Director 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 | MR
  • Update marketing material
    • Slide decks

Potential workflow impact

Edited by Christina Lohr