Add guidelines for meeting naming

Why is this change being made?

In a recent round of Product all team members meetings, we were surprised to see so few people attend one of the meetings. Despite overlap with west coast AMER, only APAC members showed up. This happens quite often, where the "APAC" meetings have much lower attendance despite AMER overlap.

When looking at the meeting titles themselves, we saw that they were named:

• Product All-Team Meeting [AMER]
• Product All-Team Meeting [APAC]

This makes it seem like AMER team members must attend the AMER meeting only. This causes the APAC team meetings to have lower attendance than might be possible if people better understood that other options are also fine, which ends up giving the impression that APAC timezone meetings are not as popular or important.

In other cases, people in certain regions are often on the "edges" of meeting times and can feel left out. Folks in New Zealand invited to an EMEA/APAC "friendly" meeting may not feel that the meeting time is particularly friendly, as it's almost certain to be out of their working hours. Or an AMER/APAC "friendly" meeting which is almost certainly going to happen while team members in India are still sleeping.

This MR updates the guidelines for meeting to give more inclusive neutral names to make sure everyone understands that everyone is welcome to attend whichever meeting works for them. We can see in the invite and on our calendar whether or not a meeting matches our working hours, there is no need to prescribe a meeting as dedicated to team members in any particular region.

An example of a set of real upcoming meetings that already follows a similar style:

• Option 1: FY24-Q3 GitLab Assembly all-company meeting
• Option 2: FY24-Q3 GitLab Assembly all-company meeting

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

---