Skip to content

Standardize on the use of SLA abbreviation in Engineering Handbook

Vladimir Dzalbo (GitLab) requested to merge master-patch-dcb3 into master

Why is this change being made?

SLA abbreviation is used interchangeably in our handbook as short for either Service Level Agreement or Service Level Availability.

Some examples:

This MR attempts to make the use of SLA as a term MECEFU. Taking into account existing SLI, SLO, SLA definitions as well as the fact that SLA is an industry-agreed term for Service Level Agreement (with availability usually being a critical part of it), I suggest to refrain from using SLA when talking about Service Level Availability.

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.
Edited by Vladimir Dzalbo (GitLab)

Merge request reports