Skip to content

Adding thoughts on how to document & communicate PTO for other team members

Manuel Kraft requested to merge manuel.kraft-master-patch-89178 into master

Why is this change being made?

What: Going on PTO and being sure that everything is known to the rest of the team is very important for each team member and managers. Documenting the most relevant parts is key for other team members which will act as a backup / covering team member.

Why: To make it easier for team members to document their work/topics before going on PTO, i added thoughts / practices which worked well in the past after a longer PTOs (1-3 weeks).

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 one of the people listed in the "Maintained by" section in 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.
    • 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. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports