Skip to content

Standardize Fulfillment team yml

Jerome Z Ng requested to merge standardize-fulfillment-team-yml into master

Why is this change being made?

This MR is part of Restructure Fulfillment Handbook Pages https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/321

This MR standardizes the role title, department, and specialties for all Fulfillment team members. Having team yml standardized makes for easier reporting and display in the handbook.

Changes made

The following changes were made:

Role changes

Department changes:

  • Added the relevant departments for each team member
Product:
- Product Management
- Fulfillment Section
- Fulfillment PM Team
- Fulfillment:License Team / Fulfillment:Purchase Team / Fulfillment:Utilization Team

Development:
- Engineering Function
- Development Department
- Fulfillment Section
- Fulfillment Sub-department
- Fulfillment:Purchase Team / Fulfillment:License Team / Fulfillment:Utilization Team / Fulfillment:InfraDev Team
- Fulfillment:Purchase BE Team / Fulfillment:Purchase FE Team / Fulfillment:License BE Team / Fulfillment:License FE Team / Fulfillment:Utilization BE Team / Fulfillment:Utilization FE Team
- Frontend / Backend

Quality:
- Engineering Function
- Quality Department
- Fulfillment Section
- Fulfillment & Growth QE Team
- Fulfillment:License Team / Fulfillment:Purchase Team / Fulfillment:Utilization Team

Design:
- Engineering Function
- UX Department
- Fulfillment Section
- Fulfillment UX Team
- Fulfillment:License Team / Fulfillment:Purchase Team / Fulfillment:Utilization Team

Specialty changes

  • Added the relevant specialties for each team member
- 'Fulfillment'
- 'Fulfillment: Purchase'
- 'Fulfillment: License'
- 'Fulfillment: Utilization'

Reports to changes

  • Renamed be-mgr-fulfillment-purchase to chrisbaus

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
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 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 Jerome Z Ng

Merge request reports