Removing the recommendation for Clockwise

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Removing the recommendation for Clockwise similar to the Focus Friday change. Applications like Clockwise can adversely affect customers, team members, and expose GitLab data to an untrusted third-party vendor. Clockwise is being removed as a recommendation for the following reasons:

• Clockwise only accounts for the subscribers availability/timezone and do not give consideration to the meeting invitees. This has led to calendar conflicts which impact multiple team members. As a company operating in 63 countries and many timezones these solutions are unable to accurately account for the needs of our team members.
• Clockwise will automatically decline meetings during focus time and send out emails which could be received by customers. The automatic and abrupt meeting declines can be viewed negatively by customers and prospects.
• Clockwise is unmanaged software with privileged access to read calendars. This presents potential data security risk with potential access to orange and red data.

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
  • 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

---