Draft: Update paid-time-off

Why is this change being made?

Suggests updates to PTO to make it more objective (less of a pitch of why to take vacation as this doesn't seem like an issue at GitLab). Also, removes blanket guidance. Not every team member needs a 2 week block.

Most material change is an update to the expected notification period for planned PTO. Instead of twice as many days notice as time away (for ex, 4 business days notice for 2 days away), it updates to as many weeks away notice as days away (for ex, 2 weeks notice for 2 day away or 5 weeks notice for 5 days away). This assists managers as they consider coverage and helps teams to better understand and address dependencies. Since we are talking about planned time off, it should be possible and not overly onerous for team members to meet this timeline in most instances.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file paid-time-off.md

---