November 2016 Summaries

GitLab is likened to a collaborative workflow process, akin to how a team of newspaper journalists might work together to produce a story. In this analogy, GitLab facilitates the collaboration of developers by allowing them to break down a project into manageable tasks, akin to journalists dividing a story into sections. Each developer works on a separate copy of the main project, known as a branch, to prevent overwriting others' contributions. As tasks are completed, they are reviewed for quality and integrated into the main project through a process called Continuous Integration, similar to how a journalist's draft is fact-checked and edited. Finally, once all components are approved, the project is deployed into production, akin to sending the final newspaper to print, and user feedback is continuously incorporated to improve future iterations, much like updating an online article based on reader responses.

GitLab is hosting an Issue Bash event on December 3-4, offering participants the chance to win prizes like a Pocket CHIP, Raspberry Pis, and GitLab T-shirts by contributing to the management of over 5000 open issues on GitLab CE. Open to anyone in the GitLab community, including non-technical members, the event aims to streamline the issue tracker by eliminating duplicate issues, labeling unclassified ones, and addressing bugs. Participants can contribute by identifying duplicates, investigating and fixing bugs, and categorizing existing issues, with a requirement of having at least one accepted contribution by the time of the GitLab 8.15 release on December 22 to qualify for a randomly drawn prize. GitLab team members will be available to assist and answer questions throughout the event.

Warren Postma, a team lead at RamSoft, has become an advocate for GitLab, both in his personal projects and professional endeavors. Having transitioned his team from Subversion to Git and GitLab, he emphasizes the platform's advantages in a distributed work environment, particularly its decentralized nature, which supports his multicultural and geographically diverse team. Warren highlights the importance of overcoming ingrained habits when switching to GitLab CI and praises its integrated toolset that combines version control, issue tracking, and CI/CD capabilities. He prefers GitLab over alternatives like Bitbucket due to its open-source nature and robust community, and he sees significant potential in GitLab providing support for smaller companies. Warren's experiences include facilitating the setup and maintenance of private GitLab instances and advocating for its use among peers, while he also expresses interest in developing educational resources to aid teams transitioning from Subversion to Git.

GitLab developer advocate Amanda Folson discusses the nuanced role of developer advocacy with Jasmine Anteunis of Recast.ai, emphasizing the importance of genuine community-building over sales tactics. Folson highlights that developer advocates should focus on enhancing developers' experiences and education, rather than pushing products directly. While public speaking is a notable aspect of advocacy, nurturing communities through engaging content and responsive interactions is crucial, and the effectiveness of these efforts can be gauged through "fuzzy metrics" like event attendance and traffic analysis. Folson outlines that developer relations should complement, not replace, traditional sales efforts, and stresses the importance of balancing both online and in-person engagements to reach diverse audiences. Additionally, recognizing and supporting community influencers, staying abreast of industry trends, and maintaining coding skills are vital for sustaining credible and effective developer relations.

CERN, the European Organization for Nuclear Research, is renowned for being the world's largest particle physics laboratory and the creator of the first website. It utilizes GitLab for hosting software projects and code management, with around 2500 active developers, mostly in France and Switzerland, though its community extends across various member states. GitLab supports key projects such as the Gaudi framework for high-energy physics experiments and is increasingly used for continuous integration tasks. Alexandre Lossent, CERN's Service Manager for version control systems, highlights the organization's preference for open-source options like GitLab, which is also cost-effective and user-friendly, leading to rapid adoption and internal spread. CERN's proactive engagement with GitLab includes contributing the SAML code, earning them recognition and enabling GitLab to function as a SAML 2.0 Service Provider since release 7.12.

Deploying an application from development to production involves various strategies, and one effective approach is using Review Apps, as implemented in GitLab. Initially, developers may deploy directly to production due to low user risk, but as projects grow, the need for separate environments like staging and development arises. Review Apps simplify this process by creating ephemeral environments for each branch, allowing developers, product managers, and QA testers to test features without interfering with others' work. This dynamic system enhances collaboration and accelerates the development cycle by eliminating the need for traditional staging environments. Developers can script the creation and deployment of these apps using GitLab CI, ensuring flexibility whether hosted on private infrastructure or in the cloud. This approach not only aids large teams but also benefits solo developers by streamlining the review process, identifying issues earlier, and facilitating a smoother transition from development to production.

Cognitive Logic is a data analytics startup focused on connecting large datasets while maintaining customer privacy, utilizing technologies like Docker, Golang microservices, and a React/Node.js frontend. The company switched from GitHub to GitLab to leverage features such as validated merge requests, easily configurable CI, and straightforward migration tools, which have enhanced their development workflow. Engineer Johan Brandhorst highlights the challenges of orchestrating CI between repositories and the benefits of GitLab's Docker registry for storing build outputs. The team, composed of 10 developers, emphasizes a flexible work environment with significant control over project priorities, fostering a startup culture that includes recreational activities. Their transition to GitLab has been smooth, aided by features like Google or GitHub account sign-ups, although they anticipate improvements in chaining testing across repositories.

The challenges of scaling GitLab's infrastructure have led to a shift from using cloud-based CephFS storage to dedicated hardware. Initially, CephFS was chosen for its scalability and capacity, but its performance on cloud infrastructure was hindered by shared resources and IO latency, resulting in system bottlenecks and high costs as performance demands increased. This prompted a move to bare metal solutions, which, despite upfront costs, offer more reliable and economical performance for GitLab's needs. To better understand and address these challenges, GitLab has invested in building an observable system that uses Prometheus for gathering and visualizing system metrics, enabling the team to proactively identify and resolve infrastructure issues. This approach is part of a broader strategy to enhance monitoring capabilities, including the development of a gitlab-monitor Prometheus exporter, to provide deeper insights into system performance and trends.

After completing the first month at GitLab, the author reflects on the company's remarkable efficiency and the talented team that fosters a highly productive environment, enabling rapid development of new features. Despite the initial surprise at the streamlined onboarding process and collaborative culture, the author acknowledges the challenges of maintaining work-life balance in such a fast-paced setting, noting the temptation to work beyond regular hours due to personal enjoyment and commitment to the company's mission. To address this, the author has implemented strategies like scheduling lunch breaks to ensure discipline and balance, while appreciating GitLab's support for employee well-being, evidenced by policies such as mandatory vacation time. The overall experience is described as exhilarating, with the opportunity to contribute to impactful software development, and an invitation is extended to those interested in joining the GitLab team.

GitLab's 8.14 release introduces Time Tracking as a feature in its Enterprise Edition, aimed at allowing teams to compare project estimates with actual time spent, thus integrating more of the software development lifecycle into one platform. This feature provides a more seamless, cohesive experience by eliminating the need for external time-tracking tools, aligning with GitLab's mission of streamlining collaboration. It utilizes two new slash commands: /spend for logging hours spent on tasks and /estimate for setting time estimates, with the latter's latest entry overriding previous ones. These commands can be used independently, offering flexibility in whether or not teams choose to estimate time before tracking it. Initially available for free in its beta phase, the Time Tracking feature will benefit both GitLab Enterprise Edition customers and users on GitLab.com.

GitLab emphasizes the importance of contributions and the extensive use of automated testing to facilitate code changes, which are common in software projects. Code coverage is a key metric used to enhance testing, development, and software quality by mapping application execution to source code during automated tests, helping identify untested code areas. Tools like SimpleCov, particularly for Ruby projects, generate detailed HTML coverage reports that can be published via GitLab Pages, making it easier to spot areas needing improvement. GitLab's CI/CD pipeline allows for the execution of these tests, storing results as artifacts, and publishing them when the code is committed to the master branch, with options for running tests in parallel to reduce execution time. The coverage report can be linked in documentation through badges, offering an accessible overview of test coverage, though GitLab acknowledges that while code coverage improves visibility into untested code, it doesn't necessarily reflect test quality.

During the first month at GitLab, the author experienced a dynamic blend of remote collaboration and rapid adaptation to the company's culture and workflows, highlighted by a meet-up on the NYC World Tour. The concept of "Minimum Viable Change" (MVC), central to GitLab's product team, was adopted by the marketing team to enhance efficiency and autonomy, allowing them to make improvements quickly without needing extensive consensus. The transparent and feedback-rich environment, despite the challenges of remote communication across 34 countries, fosters a culture of continuous improvement and open dialogue. The author also overcame initial intimidation with Git basics, finding that learning these functions was easier than anticipated and recognizing the value of gamification in mastering new skills. This supportive and innovative atmosphere encourages new employees to engage confidently, posing questions and contributing to the company's ongoing evolution.

Rapid technological advancements and the pressure for businesses to evolve have led to a shift in software development practices, with developers increasingly favoring open source tools and distributed version control systems like Git to accelerate production. A recent survey highlights that 98% of developers use open source tools, with 92% preferring Git, emphasizing the need for managers to embrace modern development workflows that prioritize collaboration and agility. Despite the overwhelming reliance on outdated systems, there is a significant alignment between developer desires and business needs, with developers advocating for more iterative and conversational development processes to enhance speed and efficiency. The emergence of Conversational Development (ConvDev) is transforming the software development landscape by integrating ongoing communication throughout the development lifecycle, thereby reducing cycle time and enabling teams to deliver faster, smaller changes. This approach is redefining Agile methodologies, underscoring the importance of real-time collaboration tools and the integration of communication at every stage of development to stay competitive in the fast-paced technology industry.