Add Meetings Page Auto Closer extension to Other apps > Productivity

Why is this change being made?

In #whats-happening-at-gitlab, team members reported that https://about.gitlab.com/whats-new/ was opening in their browser roughly once a day with no apparent action on their part. The cause is the Zoom join page, which redirects to the What's new page a few minutes after a meeting is joined, so a day of meetings leaves behind several tabs nobody opened.

In that thread, a team member shared the Meetings Page Auto Closer Chrome extension as a pre-approved way to handle it, and several others found it useful. Another team member noted in the same thread that we need to do a better job of documenting this. This MR adds the extension to the Productivity section of the Other apps page so the fix is discoverable outside of a Slack thread.

Selected excerpts from the thread:

I'm finding that https://about.gitlab.com/whats-new/ gets opened automatically in my browser around once a day, every day, through no apparent action I've taken... Anyone know what might be doing that?

It got changed a few months back - but each time you open a zoom, the 'join now' page redirects to the whats new after about 5 mins

https://chromewebstore.google.com/detail/meetings-page-auto-closer/pbgidoglkjhfgjhalbbiiahdlokjcplb is the way I handle it - auto closes the zoom join pages; pre-approved extension.

Got it. So we need to do a better job of sharing that this is a thing. We'll confirm if this is still something that's necessary (I assume it is) and make sure it's clearly documented somewhere

Affected page: Other apps > Productivity

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
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• 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

---