Point Growth group Slack channels at #s_growth

Serhii Yarynovskyirequested to merge
growth-consolidate-group-slack-channels into master

Describe the change and rationale here.

Sets slack.channel to s_growth for the three Growth groups — acquisition, activation, and engagement. They previously pointed at g_acquisition, g_activation, and g_engagement.

Why: Growth is consolidating its three per-group Slack channels into the stage channel #s_growth. With the team operating in a pooled model the per-group channels fragment discussion without a current need, so they are being de-referenced and then archived. The change is reversible — if per-group channels are needed again, they can be recreated and this reverted.

Scope: channels only. The three groups remain distinct groups with their own GitLab groups, group::* labels, and error budgets. Nothing else in this file changes, and the stage-level growth.slack.channel was already s_growth.

Downstream effect: the handbook syncs this file at build time via scripts/sync-data.sh, so these pages pick up the change with no handbook MR:

  • /handbook/product/categories/#growth-stage (and the #acquisition-group, #activation-group, #engagement-group anchors)
  • /handbook/product/categories/features/
  • /handbook/product/categories/lookup/

The two hand-written handbook pages that name these channels (the Growth engineering page and the marketing growth page) are handled in a separate handbook MR.

Change classification

Per Section, Stage, and Group changes, this is a Group-level informational change (updating a link), which requires approval from either the relevant Product or Engineering lead. The broader notification list below applies to structural section/stage/group changes and is left unticked deliberately — no group is being added, removed, renamed, or re-scoped here.

Verification

Run locally against this branch:

  • bundle exec rake lint:stages_yml — SUCCESS: stages.yml links are valid, no invalid resources found.
  • bundle exec rspec spec/stages/stages_yml_checker_spec.rb spec/homepage/stage_spec.rb spec/homepage/group_spec.rb — 107 examples, 0 failures.
  • yamllint data/stages.yml — clean.
  • Checked lib/stages/stages_yml_checker.rb: slack is a required-field check only, with no uniqueness constraint, so three groups sharing one channel is valid.

Approvals

All Section, Stage, Group, Feature, and Category changes require approval. Please see the handbook section on making changes to see which approvals are required depending on the changes you are making.

The following people need to be mentioned on the merge request so they stay informed:

  • Relevant Product lead(s) for affected section(s), if not already an approver
  • PLT Leader relevant to the affected Section(s), if not already an approver
  • Relevant Engineering lead(s), plus the Engineering lead(s) "above" - For example, a Group-level change, mention the Engineering lead for the Group and the Stage the Group is in.
  • Engineering lead(s) for the affected Section(s)
  • The relevant Product Marketing Manager(s)
  • Technical Writing counterpart(s)
  • Director of Technical Writing
  • UX Research Leader
  • Sr Director of Product Design
  • Chief of Design
  • Chief Product and Marketing Officer
  • VP, (Infrastructure) Platforms Engineering
  • Chief Technology Officer

References

Merge request reports