January 2017 Summaries

Two GitLab team members, Douwe and Robert, embarked on a six-month journey across 20 cities and 14 countries to visit and work with 49 colleagues, leveraging GitLab's policy of covering travel costs for employees to meet in person. This initiative highlighted the benefits of remote work by allowing team members to connect deeply beyond virtual interactions, fostering a sense of camaraderie and understanding among colleagues who typically interact online. Despite the challenges of different time zones and remote work dynamics, the trip underscored GitLab's core values of kindness and inclusivity, as team members welcomed the travelers into their homes and cities, reinforcing the notion of GitLab as a cohesive and supportive community. The experience also provided insights into various global work environments and the significance of personal interactions in enhancing remote work relationships, prompting GitLab to encourage more such visits in the future to strengthen its global team culture.

Git Large File Storage (LFS) is an extension designed to efficiently manage large files in Git repositories, addressing the common problem of repository bloat when dealing with large binary files like design assets, movies, and datasets. By using lightweight pointers instead of storing all versions of large files in the local repository, LFS shifts the storage burden to remote servers, allowing local repositories to remain manageable in size. Installation of LFS is necessary as it is not part of the core Git binary, with options available for various operating systems. Once installed, users must explicitly instruct LFS to track specific files or file patterns, ensuring that large files are managed efficiently from the outset. The Tower Git client offers built-in support for LFS, simplifying the process for users by integrating these capabilities into their existing Git workflows, while maintaining standard Git operations like staging, committing, and pushing.

CodePen's transition to GitLab has provided them with increased control, security, and efficiency in their operations. By utilizing a self-managed GitLab instance on AWS, they have gained autonomy over their deployments, enhancing their ability to manage downtime and protect against security breaches. The open-source nature of GitLab, along with its cost-effectiveness, has also been a compelling factor, offering features like Multiple Issue Boards and Continuous Integration without reliance on third-party services. This move has streamlined CodePen's project management by integrating tasks, issue boards, and time tracking within a single platform, replacing previous tools like Trello and GitHub. The transition process included challenges, such as manual data transfers due to the initial oversight of the GitLab Importer tool, but overall, the team finds GitLab's comprehensive features, including its user-friendly pipelines and rollback options, to be a significant improvement, although they still anticipate the addition of features like squash-merge and burndown charts.

GitLab's approach to software delivery focuses on quick, iterative releases, resulting in 12 new versions in 2016, each introducing significant features and enhancements to the platform. Key features from these releases include Issue Boards, Cycle Analytics, GitLab Geo for mirroring instances globally, and the GitLab Container Registry for efficient Docker image management. Other notable additions were Pipelines for better build organization, Confidential Issues for project privacy, and Merge Conflict Resolution within the GitLab interface. The platform also saw improvements like File Locking, Universal Two-Factor Authentication support, and the introduction of Manual Actions for CI, which provided greater control over deployment processes. The year concluded with the release of GitLab 8.15, which finalized the foundation of GitLab's idea-to-production vision, setting the stage for further enhancements in 2017, including Auto Deploy and Web Terminal features to streamline deployment and debugging processes.

GitLab's UX team, led by Allison Whilden and Sarah O'Donnell, addresses the unique challenges of designing for a comprehensive software development lifecycle by using research, testing, and community feedback to make informed design decisions. They emphasize the importance of understanding user needs by using their own product daily, which helps them empathize as both users and technical experts while being mindful of biases. The team works remotely, creating a shared vision documented in their UX Guide, and navigates the relationship with the product team by recognizing that they are both users and builders. Balancing feedback is crucial, with priority given to Enterprise customers, external community input, and internal developers, while developing personas to better understand and predict user behavior to create a cohesive experience for diverse teams.

GitLab 8.16 offers the capability to deploy directly to Google Kubernetes Engine (GKE), enabling users to transition from idea to production in approximately 20 minutes while leveraging features like auto-scaling CI, auto deploy, Mattermost, and a private Docker registry within their Kubernetes cluster. Users can enhance their team's productivity by watching a comprehensive video tutorial, with further instructions available on the project page. An upcoming webcast on January 26 will provide more insights into the latest release, and additional resources for replicating the demo can be accessed on the demo page.

Tower, a popular Git desktop client for Mac, has expanded its services to integrate with GitLab on Windows, enhancing repository management and error correction to boost team efficiency. This new integration, eagerly awaited by users, is celebrated with a 20% discount offer until February 15th. Tower's founder, Tobias Günther, highlights the significance of this feature, while GitLab's VP of Product, Job van der Voort, expresses excitement over the expansion. Key features include a Services Manager for seamless GitLab account management, productivity boosters like automatic fetching and stashing, and tools for error correction such as the "Conflict Wizard." The platform caters to both beginners, with extensive learning resources, and advanced users, offering features like single-line discard and support for Submodules and git-flow.

Operating as a remote-only company necessitates deliberate communication strategies to ensure transparency and keep employees informed. One effective approach employed is the use of functional group updates, as exemplified by the Product team's update, which is shared with the entire company to maintain coherence and transparency across all departments.

Creating effective user personas is crucial for successful product development, as it helps teams understand and empathize with diverse user needs, preventing the creation of products that only cater to a narrow segment. Personas are fictional characters developed using qualitative and quantitative research to represent the motivations, frustrations, and goals of different user types, providing a human face to data and facilitating a unified team focus on user-centered solutions. At GitLab, the development of personas is in its early stages, relying on surveys, user interviews, and web analytics to gather and analyze user data, which helps in defining clear objectives and reducing internal disagreements. By fostering a shared understanding of users, personas guide product managers in validating and prioritizing features, while helping designers determine the product's visual style, ultimately aiming to enhance user experience and ensure that products align with user expectations and goals.

GitLab's vision for monitoring involves integrating Prometheus for system and application observation to enhance user experience and streamline performance tracking. The initial focus is on creating a Minimum Viable Product (MVP) by using Prometheus to monitor GitLab installations and Kubernetes-based applications, emphasizing metrics such as throughput, latency, and error rates. The approach aims to enhance the developer experience by embedding monitoring alerts directly into merge requests, providing immediate feedback on code deployments. Future directions include expanding into comprehensive application performance monitoring, end-user experience evaluation, and deploying monitoring techniques like incremental and blue/green deployments, along with introducing feature flags to decouple deployment from delivery. This strategy is designed to offer a seamless integration of monitoring tools within GitLab, ensuring efficient deployment and feedback mechanisms to aid developers in optimizing and troubleshooting their workflows.

GitLab's development of Review Apps demonstrates a strategic approach to feature implementation, focusing on iterative improvements and user feedback. Initially inspired by similar tools like Heroku Review Apps and informed by internal and external insights, GitLab's team embarked on creating a seamless integration of Review Apps into their platform. Despite the complexity and ambitious goals, they prioritized practicality by breaking down the development into three incremental releases, starting with GitLab 8.12. The first phase introduced dynamic environments through minor but impactful changes to the .gitlab-ci.yml format, followed by enabling app deletion with manual actions in 8.13. The latest release, 8.14, automated app stopping upon branch deletion and organized environment lists to enhance user experience. By emphasizing minimal viable changes, GitLab not only accelerated delivery but also fostered continuous learning and enhancement, with future plans to streamline the .gitlab-ci.yml syntax and potentially reintroduce more advanced features.

GitLab Inc, as it grows to over 150 remote employees, faces challenges in maintaining productivity and remote culture, particularly as management trends towards traditional structures with increased meetings and reviews. The concern is that these practices can hinder efficiency and the unique culture of remote work. The solution proposed is to establish clear expectations for communication and deliverables, emphasizing trust in employees to manage themselves and over-communicate when necessary. This approach aligns with GitLab's policy of hiring self-managing individuals, as the company avoids traditional project management roles to maintain decision-making freedom and accountability among its team members. By doing so, GitLab aims to retain those who thrive in a self-managed environment while acknowledging that this model may not fit everyone. These principles are documented in GitLab's open-source handbook, inviting contributions and transparency.

GitLab's interview process is remote-first, utilizing video calls via platforms like Google Hangouts or Appear.in to connect with candidates and integrate them into the company's virtual culture. To ensure a successful video interview, GitLab advises candidates to select a neutral, quiet, and comfortable environment and to avoid distracting settings such as crowded cafes or cars. It is crucial to test all technical equipment, including Wi-Fi connectivity and microphone functionality, prior to the interview. Candidates are encouraged to review GitLab's handbook and values, as many interview questions can be found in their hiring process documentation. Despite the virtual setting, traditional interview preparation remains important, including dressing appropriately, conducting thorough research, and preparing insightful questions. GitLab emphasizes that a video interview should not be approached casually, and they invite candidates to explore open roles on their jobs page, encouraging engagement via social media or their issue tracker for further inquiries.