Skip to content

Deprecate Engineering Allocation Sync Meeting

Alan Richards requested to merge master-patch-335f into master

Why is this change being made?

The Engineering Allocation / Infradev meeting was most recently combined with the past Reliability & Scalability Daily Standup. Prior to that the sync meeting was started to primarily cover active Engineering Allocations and also infradev issues. Currently there are 0 active Engineering Allocations as well as no past-due Infradev issues.

We will not want to lose sight of the status of all that this and other previous meetings have covered, but instead want to ensure that appropriate async methods exist to provide the needed oversight. This is achieved through:

  • For infradev items: The Development PIs and Key Review
  • For engineering allocations: the async EA process, handbook updates, and related infradev issues
  • For availability: the Infrastructure PIs and Key Review
  • For high-severity incidents: The Incident Management process and related escalation methods
  • Error Budgets: the monthly EB report and other process owned by the Infrastructure::Scalability::Projections team

Related to #14494 (closed)

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.

Merge request reports