Skip to content

WIP: Refactor incubation SEG stages

Daniel Croft requested to merge dcroft-refactor-incubation-segs into master

Why is this change being made?

So far, Single Engineer Groups (SEG) from DepartmentIncubation Engineering have been added to stages.yml as though they were stages. There are currently 3 examples of this in this: mobile_devops, deploy, and no_code. Since an SEG is actually a group this MR is attempting to reflect a structure that more accurately represents the team and groups within it. Additionally, since the introduction of this rubocop rule, categories (and by association) stages are required.

What's the change?

I've added an incubation stage with appropriate fields, used To Be Decided (TBD) where appropriate, and copied the group entries for the 3 existing SEGs to this incubation stage.

What action is needed

The incubation engineers working on the 3 SEGs already here should make sure the groups within the incubation stage have the correct information entered. Please suggest in a comment or add another commit updating the incubation.groups.your_group_name as appropriate. Once you're happy with it, feel free to check the box below and unassign yourself.

The template for fields is described in the handbook but for convenience, the first group should be the name of the SEG like 5-min-app, the format is below:

  group:
    name:
    label:
    focus:
    pm:
    pmm:
    cm:
    backend_engineering_manager:
    frontend_engineering_manager:
    support:
    pdm:
    ux:
    uxr:
    sets:
    tech_writer:
    appsec_engineer:
    be_team_tag:
    fe_team_tag:
    cs_team_tag:
    internal_customers:
    internal_customers.department:
    internal_customers.dri:
    usage_driver_score:
    asp_driver_score:
    sam_driver_score:
    pi_gmau:
    pi_pgmau:
    analyst_reports:
    comp_comparison:
    categories:

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Sri Rang

Merge request reports