Handbook Update - Developer Relations meeting recordings
Why is this change being made?
Questions about the process of recording the team meeting and sharing the link come up in Slack every few weeks. Starting this MR to discuss and update the handbook. https://gitlab.slack.com/archives/C0R04UMT9/p1690931594332239
Proposed solution/next steps:
- Figure out who has access to the recordings for the Developer Relations meeting when anyone clicks "Record to Cloud" - maybe the meeting organizer @esalvadorp - Emilio, could you verify if you see recordings under "Cloud Recordings" https://gitlab.zoom.us/recording/ - for example, one for 2023/08/02?
- Determine if it's possible to give everyone access to the Recordings by adding co-host or other permissions to the meeting so anyone can take the link and share in the meeting doc.
- If not possible, come up with an alternative solution.
cc @gitlab-com/marketing/developer-relations
Author Checklist
-
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.