Skip to content

Updating DRIs, Cadence, Dates for Security, Infra & Quality, Support

Marisa Carlson requested to merge MarisaCarlson-main-patch-6ea1 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

I have made a handful of updates to this page, listed below:

  1. Updated DRI for Development from Schedule and DRI section of page (from Christopher Lefelhocz to Tim Zallmann, because Christopher left GitLab in Oct. 2023)
  2. Deleted UX Group Conversation with DRI Christie Lenneville from Schedule and DRI section of page (Christie also left GitLab in 2023,UX Key Reviews have not happened in some time (Summer of 2022))
  3. Updated DRI for Support Group Conversations from Schedule and DRI section of page (it was previously Lyle Kozloff and Lee Matos, but since Johnny Scarborough joined in late 2023, we needed to update and former Sr. EBA to Engineering did not make these updates previously).
  4. Updated cadence for Security, Support, and Infrastructure & Quality to Quarterly (had previously been listed as 2x/quarter or 'every other month')
  5. Listed dates for Security Group Conversations based on Security's scheduled Key Reviews for FY25. (these had previously been entered in on a recent MR, but were not reflected on the page for some reason)
  6. Listed dates for Infrastructure & Quality and Support based on their Key Review dates. Since former Sr. EBA to Engineering did not update this page at the beginning of FY25, and since we have a new Sr. EBA to Engineering that is only just starting today and will be focused on onboarding for the time being, I took the bias for action and added their dates in, these can always be updated on a future MR if the new Sr. EBA to Engineering deems it necessary. =)
  • Update file group-conversations.md

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

Merge request reports