Skip to content

What to expect when you interact with the DRI of Foundations for navigation approvals

Christen Dybenko requested to merge cdybenko-master-patch-0c87 into master

Why is this change being made?

Goal of the MR

  • There is lack of clarity on what to expect going into a navigation approval.
  • The goal of this MR is to prepare the product manager and their team to know what this coming and what is expected so they can make a successful proposal.
  • Note, timelines could also a part of this confusion and were added in another MR.

Reference to feedback

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Christen Dybenko

Merge request reports