Refactors the incubation engineering job families
Why is this change being made?
Please see: https://gitlab.com/gitlab-org/incubation-engineering/meta/-/issues/23
Currently, the job roles for incubation engineering are within the engineering
folder, from an ownership and availability perspective, this doesn't accurately reflect the organisation structure. This MR is intended to provide ownership of incubation engineering job families to the incubation engineering team as well as identify that these roles are specific to this department.
No changes to role requirements are being made in this MR.
What changes are being made here?
-
Creates an incubation-engineering
folder under theengineering
folder -
Moves incubation-engineer
folder into this folder -
Moves VP Incubation Engineering
to this folder
Adds CODEOWNER entries for this subfolder
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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 Daniel Croft