Functional Group Updates

  1. You are here:
  2. Team Handbook
  3. People Operations
  4. Functional Group Updates

Format

Functional Group Updates are regular updates from a group at GitLab.

  1. We'll use Zoom for now, will switch to YouTube Live later.
  2. Presentations are optional, if you use them please ensure everyone with the url can access (inside and outside GitLab).
  3. Use this slide deck as template to your presentation.
  4. Make sure to add the link of the presentation to the GitLab Availability Calendar invite before the call takes pace. This allows people to see if they want to see the presentation, it allows them to click links, it allows random access during the presentation and it allows people to quickly scan the presentation if they missed it. To do this, go to the GitLab availability calendar, find the event, click on more details and edit the description.
  5. Reduce distractions for yourself and the attendees by:
    • having the presentation open in its own new browser window, and only sharing that window in Zoom.
    • switching off notifications (from Slack, email, etc.). On Mac, in the notification center in the upper right hand corner, click on Notifications, select Do Not Disturb (sometimes you need to scroll up to see the option).
  6. All calls except sales, partnerships, and finance are public unless mentioned otherwise, in the future all calls will be public.
  7. Right now everyone at GitLab the company is invited to each call, we'll invite the wider community later.
  8. Attendance is optional.
  9. The update is also announced on and the recording linked from our team call agenda.
  10. Tone should be informal, like explain to a friend what happened in the group last month, it shouldn't require a lot of presentation.
  11. You can invite someone in the team to give the update, it doesn't need to be the team lead, but the team lead is responsible that it is given.
  12. Calls are 4 times a week 30 minutes before the team call, 8:00 to 8:25am Pacific.
  13. Calls do not go over time, if there are more questions invite them via chat, if there are no more questions feel free to end the call after 5 minutes.
  14. Calls are scheduled by an EA who can also switch team based on availability of the presenter.
  15. Every group with 5 people or more presents.
  16. The call is recorded automatically, and all calls are transferred every hour to a Google Drive folder called "GitLab Videos", which is accessible to all users with a GitLab.com e-mail account.
  17. Video recordings will be published on our blog so contributors, users, and customers can see it. We're aiming to publish a blog post once a week of that weeks' recordings with the matching slides in one go.

Template for the blog post

For instructions on how to create a blog post, please see our Blog Handbook.

Please copy the code block below and paste it into a blog post with the file name yyyy-mm-dd-functional-group-updates.html.md.

---
title: "GitLab's Functional Group Updates - MMM DD-DD" # replace "MMM" with the current month, and "DD-DD" with the date range
author: Name Surname
author_gitlab: gitlab.com-username
author_twitter: twitter-username
categories: Functional Group Updates
image_title: '/images/blogimages/functional-group-update-blog-cover.jpg'
description: "The Functional Groups at GitLab give an update on what they've been working on"
---

<!-- beginning of the intro - leave it as is -->

Every day from Monday to Thursday, right before our [GitLab Team call](https://about.gitlab.com/handbook/#team-call), a different Functional Group gives an [update](https://about.gitlab.com/handbook/people-operations/functional-group-updates/) to our team.

The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.

<!-- more -->

## Recordings

All of the updates are recorded using [Zoom](https://zoom.us) at the time of the call. All the recordings will be uploaded to our YouTube account and made public, with the exception of the Sales and Finance updates.

<!-- end of the intro -->

<!-- beginning of the FG block - repeat as many times as necessary (copy and paste the entire block) -->

----

### XXX Team

[Presentation slides](link-to-slides-deck)

<figure class="video_container">
  <iframe src="https://www.youtube.com/embed/8vJBc8MJihE" frameborder="0" allowfullscreen="true"> </iframe>
</figure>

<!-- end of the FG block -->

<!-- beginning of the FG block - repeat as many times as necessary (copy and paste the entire block) -->

----

### XXX Team

[Presentation slides](link-to-slides-deck)

<figure class="video_container">
  <iframe src="https://www.youtube.com/embed/8vJBc8MJihE" frameborder="0" allowfullscreen="true"> </iframe>
</figure>

<!-- end of the FG block -->

----

Questions? Leave a comment below or tweet [@GitLab](https://twitter.com/gitlab)! Would you like to join us? Check out our [job openings](https://about.gitlab.com/jobs/)!

Uploading and Editing the Videos

Functional Group Update XXX-Team Date

Try GitLab EE FREE for 30 days, no credit card required - https://goo.gl/JdznoY

Want to know more about our free GitLab.com? https://goo.gl/Uol8bl

GitLab License FAQ - https://goo.gl/hZAsYF

Questions?? - https://goo.gl/i7KzQ8

Schedule

There is a rotating schedule:

Week 1:

Week 2:

Week 3:

Week 4:

Week 5:

Agenda

A possible agenda for the call is:

  1. Accomplishments
  2. Concerns
  3. Stalled/need help
  4. Plans
  5. Questions in chat
This page is generated from a public file on GitLab.com — merge requests with improvements are very welcome. Creative Commons License