Skip to content

Adds experimentation category linked to growth groups

Phil Calder requested to merge pcalder-add-growth-experimentation-category into master

Why is this change being made?

When adding code to GitLab, developers are required to use a feature_category:. Lately we have had multiple cases where the category used has been questioned by the reviewer/maintainer. This introduces an experimentation category to be used when needed for Growth experiments.

More info: gitlab-org/growth/team-tasks#338 (closed)

Checklist: https://about.gitlab.com/handbook/product/product-processes/#adding-a-new-category-to-a-stage

  • add a ~Category:Experimentation label to gitlab-org once this MR is approved.

Review:

  1. Categories: https://pcalder-add-growth-experimentation-category.about.gitlab-review.app/handbook/product/categories/#growth-stage
  2. Features (currently none for this category): https://pcalder-add-growth-experimentation-category.about.gitlab-review.app/handbook/product/categories/features/#growth

@hilaqu, @s_awezec, @mkarampalas I'm looking for at least one approval before merging this change to add an experimentation category to the handbook. Note we have the option of creating more specific categories like onboarding, and growth_marketing and should this consider this in future.

cc @whaber

Note this is not a significant change to categories or stages, so does not warrant the full approvals list https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab/merge_request_templates/Category-Change.md - adding for notification purposes:

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Phil Calder

Merge request reports