Blogs›GitLab›Remote Work Culture and Operations

Remote Work Culture and Operations

posts

2015

GitLab has established and refined its fully remote work culture, emphasizing asynchronous communication, flexible work hours, and robust social connection mechanisms. This includes daily morning meetings for coordination and team bonding, a preference for GitLab issues and Slack for communication, and regular individual check-ins with leadership to ensure employee happiness. The company also fosters in-person meetups and virtual social events, particularly around releases, to maintain team cohesion. This post details their lightweight, self-organizing workflow for incoming issues, working and prioritizing, and managing overflow, all while adhering to Agile principles and fostering openness, independence, and responsibility.

2015

GitLab Mattermost, an open source on-premises Slack alternative

8/18/2015

This post announces the integration of GitLab Mattermost, an open-source, on-premises messaging app (similar to Slack), into GitLab Omnibus packages starting with version 7.14. This addresses the need for on-premises communication solutions for organizations that cannot use cloud-based services like Slack. The integration leverages GitLab's existing OAuth provider and Omnibus packaging for easy setup. The post also details the historical context of GitLab's internal communication tools, including the deprecated 'wall' feature, and the rationale for choosing Mattermost.