The goal is to support the members of these groups in connecting at a personal level, not to check in on people's progress or replace any existing processes to communicate status or ask for help, and the questions are written with that in mind:
Each week, the Engineering Manager (EM) creates a short video communicating both GitLab and Team information. The Weekly Update is accompanied by a presentation and a Google Document to capture asynchronous questions.
To maintain our service level for GitLab.com customers, GitLab team members serve as On-call Engineers. In general, Engineers select shifts that are convenient for them. Each shift spans four hours.
Each week, the Product Manager, the Create:Editor Frontend and Create:Editor Backend Teams conduct a synchronous meeting to share progress and discuss issues. These meetings are recorded and can be viewed asynchronously. A Google Doc is also available to ask questions or comment synchronous or asynchronously. Conducting meetings using this format allows all team members to participate in knowledge sharing.
Calendars are used to communicate important events:
The PTO Ninja communicates your Out of Office events.
Communicate as much as possible and as early as possible through the issue. Here are a few examples of communicating via the issue:
The groups in the Create stage organize regular Deep Dive sessions to share our domain specific knowledge with others in the stage, the organization, and the wider community. All existing Deep Dives can be found on GitLab Unfiltered with slides and recordings in the descriptions. For Create specific Deep Dives, there is a different playlist. To find more information on upcoming sessions, or to propose a new topic, please see the epic.