Engineering Key Review Meeting Agenda page in Handbook
Why is this change being made?
We'd like to keep the key meetings handbook-first, and avoid having to cut/paste or screenshot metrics into a deck to allow stakeholders to prepare.
Since the [K]PIs are in YML, this MR generates a single page that can be reviewed prior to the meeting.
One thing that will be difficult to handle is confidential (e.g. financial) [K]PIs.
CC @clefelhocz1 @meks @JohnathanHunt @clenneville
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.
For help with failing pipelines reach out in #mr-buddies in Slack
Edited by Eric Johnson