|Workflow||How may we be of service?||GitLab.com Status|| |
|Issue Trackers||Infrastructure: Milestones, OnCall||Production: Incidents, Changes, Deltas||Delivery|
|Slack Channels||#sre-lounge, #database||#alerts, #production||#g_delivery|
|Operations||Runbooks (please contribute!)||On-call: Handover Document, Reports|
GitLab is a widely distributed company, and we aim to work asynchronously most of the time. There are times, however, when we must get together to discuss a topic in real time, and thus, we do have some meetings schedule.
The Infrastructure Call is one of many channels to share and distribute Infrastructure-related information relevant to the entire company and beyond. The meeting is organized by the Director of Infrastructure.
The InfraCall agenda is divided into the following sections:
Infrastructure managers and ICs update relevant sections before the meeting. Other attendees are welcome to add agenda items as necessary.
Design and Automation (DNA) is a purely technical meeting for Infrastructure ICs to discuss technical topics. Managers also attend this meeting, but they take off their manager hat as soon as they join the meeting. The meeting is organized by the Director of Infrastructure.
The DNA agenda is driven by blueprints and designs; open discussions are also welcome as long as they are technically relevant. Project status discussions are strictly out of bounds in this (the only exception being the resolution of technical dependencies).
While open discussions are welcome, it is strongly recommended blueprints and designs are used as the source of agenda items. This allows everyone to have the appropriate context for the conversation before the meeting.
During discussions, it is obviously ok to point shortcomings for a given design. This is one way in which we expand our angle of vision and learn. In general, however, make it a point to provide alternatives.
Each team in Infrastructure has a weekly Staff meeting, where relevant team issues are discussed. These meetinfs are organized by Infrastructure Managers for their respective teams.
The weekly mStaff brings together Infrastructure's management team for a weekly sync early in the week to prepare for the week and address issues that require attention. The meeing is organized by the Director of Infrastructure.