At GitLab, Slack is critical to our communication with each other. While it enables real-time communication, we also are careful to remain true to our asynchronous mindset, suggesting that GitLabbers set "do not disturb" and not expect real-time answers from others all the time.
There are groups of channels that can help with various areas of GitLab. This page speaks to a few subsets of those channel groups.
There are a lot of general channels, just to name a few:
#general: General announcements and company-wide broadcasts#questions: Ask all of GitLab for help with any question you have… and then go document it after you find the answer :)#thanks: Where GitLabbers can say thanks to those GitLabbers who did a great job, helped a customer, or helped you!#random: Socialize and share random snippets with your fellow GitLabbers.These channels are for teams and GitLabbers interested in a specific feature that exists in GitLab or is being built today!
Examples
#f_web_ide: Share ideas and feedback about our Web IDE#f_ldap: Talk about our integration with LDAP providers.Group channels (prefixed with a g_) correspond to a DevOps Stage group and other engineering departments and teams.
Example
These channels are used to help GitLabbers who are in the same general region of the world to talk about get-togethers and other location-specific items. They are also instrumental if you're going to be visiting somewhere else in the world - there might be a GitLabber or two nearby! Feel free to join the channel temporarily to chat with GitLabbers who live there, and see if there is an opportunity to leverage the visiting grant to add value to your trip.
Examples
#loc_nashville: Chat with the GitLabbers in Nashville, Tennessee, USA#loc_portugal: A channel for GitLabbers in the entire contry of Portugal!Many customers that require coordination across GitLab teams have dedicated channels in slack to discuss that customer's needs internally. Those channels are all postfixed with -internal