Skip to content

Add definition of impact for Scalability

Sean McGivern requested to merge scalability-impact into master

Why is this change being made?

This came out of !63198 (merged).

Because we don't work on direct user-facing features, it can be easy to lose site of our actual 'users', which are:

  1. The infrastructure itself.
  2. SREs in Infrastructure.
  3. Engineers in Development.

Unless one of those notices what we've done, we effectively haven't done anything.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Merge request reports