August 2018 Summaries

Following GitLab's transition to Google Cloud Platform (GCP) on August 11, 2018, GitLab.com traffic is now managed through GCP infrastructure, with a temporary proxy in Azure maintained for GitLab Pages users who had not yet updated their DNS records. During the transition, users were advised to change their DNS records to the new GCP IP address, 35.185.44.232, from the old Azure IP address, 52.167.214.135. However, a recent cleanup of the Azure infrastructure inadvertently affected the Azure load balancer associated with the old IP address, leading to potential service disruptions for users who hadn't updated their DNS settings. GitLab has communicated this change to inform affected users about updating their DNS records to ensure continued service without interruptions.

GitLab team members have shared their recent reading experiences, highlighting various topics relevant to their work in technology and development. Nick Thomas, a Staff Developer, found an article on Rust's standard library vulnerabilities insightful from a security perspective. Kristie McGoldrick, a Solutions Architect, praised "Designing Delivery" for its applicability to GitLab's operations. Lin Jen-Shin, a Developer, enjoyed a CircleCI blog post discussing the challenges of adopting future technology, noting GitLab's efforts with Kubernetes in collaboration with Google. Rebecca Dodd, a Content Editor, mentioned "The Phoenix Project," a staple read among her colleagues about IT and DevOps. Mike Miranda, a Sales Development Representative, is exploring "The DevOps Handbook" to better grasp IT leaders' needs.

The text outlines the role of a Merge Request Coach at GitLab, emphasizing the importance of making contributors comfortable with the contribution process. It highlights common issues in merge requests (MRs), such as contributors not adding tests, and offers guidance on best practices, including setting up the GitLab Development Kit (GDK) locally and addressing continuous integration (CI) issues promptly. The introduction of the Web IDE is mentioned as a beneficial tool for quick edits and resolving conflicts directly from the web interface. The text encourages contributors not to strive for perfection in their initial MRs and to learn through collaboration and reviewing others' work. It also invites experienced contributors to join the core team or pursue full-time positions and suggests looking at issues labeled for community contributions for those unsure of where to start. The overall message is one of support and encouragement, with an open invitation for contributions and an emphasis on collaboration and learning.

Epics and roadmaps are new features in GitLab Ultimate and GitLab.com Gold, designed to facilitate planning and tracking of larger initiatives within teams. An epic represents a larger scope of work compared to an issue and operates at the group level, allowing for a broader discussion and linkage of multiple issues under its umbrella. The roadmap offers a timeline-based visualization of these epics, aiding in both long-term, top-down planning and short-term, bottom-up planning. Top-down planning involves creating strategic initiatives with fixed dates and high-level collaboration, whereas bottom-up planning focuses on actionable tasks and detailed designs with dynamic dates derived from milestones. The integration of these features enables seamless transitions between planning approaches, automatically updating the roadmap to reflect the current status and timeline of all epics.

Freedesktop.org (fd.o), founded in 2000 by Havoc Pennington, is an open-source, neutral platform aimed at fostering collaboration among various desktop environments like GNOME, KDE, and others. Initially created to support the development of shared standards for open-source desktops, fd.o has evolved to host a wide array of projects such as GStreamer, LibreOffice, and the X.Org Foundation, which oversees the development of the graphics stack used in Linux. Despite its success, fd.o faced challenges with outdated infrastructure and has decided to migrate to GitLab to streamline its services, which include repository management, issue tracking, and CI/CD pipelines, thereby allowing developers to work more autonomously. This move is expected to enhance workflow efficiency, improve security through modern identity management, and better handle targeted threats and spam. The migration to GitLab is anticipated to significantly reduce administrative overhead and improve the site's capability to offer cohesive, integrated services to its diverse family of projects.

Markdown is a widely used lightweight markup language created by John Gruber in 2004 that allows users to add formatting elements to plain text documents, making it popular for its simplicity and versatility across platforms and applications. GitLab, for instance, employs a variant known as GitLab Flavored Markdown (GFM) that offers additional functionalities like referencing project items, autolinking URLs, creating diagrams, and executing quick actions directly from the keyboard. The persistence and universal readability of Markdown-formatted text make it a reliable choice for various digital content, ensuring that documents remain accessible even if specific applications become obsolete. Users can begin learning Markdown through online tutorials, editors like StackEdit and Dillinger, or by experimenting with any text editor, emphasizing the language's adaptability and ease of use in numerous contexts.

Designers face the intricate task of crafting solutions that empower users, particularly developers, to excel in their work, as discussed by UX Manager Sarrah Vesselov. The evolving complexity of designing for developers stems from their use of multifaceted tools, requiring designers to continuously adapt and iterate based on direct user feedback, such as that from Hacker News, which allows for quick improvements in products like GitLab. A crucial aspect of creating positive UX experiences involves understanding developers' goals and motivations, while the greatest challenge lies in managing the increasing complexity of developers' needs. Vesselov advises designers to collaborate closely with developers to gain insights and effectively cater to their audience, emphasizing the importance of building relationships with the developers they work with. The UX team is actively seeking new members who are eager to design for a developer audience and contribute to their dynamic environment.

GitLab has been recognized as the 4th fastest-growing private software company in the U.S., achieving a revenue growth of 6,213 percent over the past three years and marking its debut on the Inc. 5000 list. Originally a simple Git repository manager, GitLab has evolved into a comprehensive application for the software development and operations lifecycle, facilitating collaboration among various teams by eliminating handoffs and bottlenecks. This growth and innovation are driven by GitLab's extensive open-source community, with over 2,000 contributors and more than 100,000 organizations, including notable names like NASA and NASDAQ, engaging with its open issue tracker. By enabling companies to focus on revenue-generating code rather than redundant tasks, GitLab positions itself not only as a robust product for today but also as a strategic partner for the future, continuing to expand its DevOps capabilities.

The author shares insights into managing remote internships at GitLab, highlighting both challenges and effective strategies for success. Initially, the lack of a clear transition path from intern to junior positions was a hurdle, illustrated by the experience with the first intern, Collen. This led to the realization of the importance of defining success and setting clear expectations, especially in the remote work environment where communication can be less direct. The author emphasizes the need for interns to take initiative, avoid busywork, and engage in meaningful tasks, while also being provided with a supportive environment to build skills and confidence. Through structured guidance and regular feedback, the second intern, Chenje, was able to focus on significant projects, demonstrating the effectiveness of these improved practices. These experiences underscore the value of thoughtful internship management, particularly in remote settings, to foster capable and motivated future team members.

Drupal, a pioneering open-source content management system launched over 17 years ago, is widely used for creating diverse digital experiences across platforms like web, mobile, and augmented reality. It powers significant governmental, commercial, healthcare, and educational systems globally, with a substantial community of contributors. Drupal is migrating its code collaboration tools to GitLab to modernize its developer practices, moving from a patch workflow to a more contemporary merge request workflow. This transition aims to boost developer efficiency, attract new talent, and maintain the collaborative practices that have driven Drupal's success. The move is expected to provide contributors with improved tools for code review and inline editing, ultimately enhancing the Drupal building experience. The Drupal community encourages participation through a comprehensive guide and events like DrupalCon, fostering a strong community ethos alongside its technical endeavors.

GitLab is actively seeking to expand its community of over 2,000 code contributors by implementing various initiatives aimed at fostering engagement and support among both new and experienced members. Efforts include improving onboarding documentation to facilitate easier participation, recognizing and mentoring first-time contributors, and launching a blog series to highlight experienced contributors like Core Team member Vitaliy Klachkov. Additionally, regular Core Team meetings have been initiated to discuss community topics, with these meetings being open for broader participation through the use of GitLab's Service Desk. These steps are designed to create a more inclusive and supportive environment for contributors, encouraging collaboration across the global GitLab community.

The author expresses enthusiasm for working at GitLab, highlighting the company's 100 percent remote workforce and dynamic team culture. The focus on enhancing security through policy as code is emphasized, with particular interest in the developments presented at Google Next 2018, such as Forseti 2.0 and Istio 1.0. The author describes engaging with Google engineers and security experts like Tom Salmon during Forseti Hack Day, which provided valuable insights into best security practices in Google Cloud Platform (GCP). The post encourages readers to explore the various sessions available from the conference on YouTube and invites feedback and discussions about using these technologies, fostering a collaborative environment for continuous improvement.

GitLab Auto DevOps is a comprehensive tool designed to streamline the DevOps lifecycle, enabling IT leaders and engineers to achieve faster and better production of cutting-edge software. As the only application covering the entire DevOps process, it provides development teams with the necessary tools to deliver high-quality, secure software at unprecedented speeds by automating the integration and pipeline setup. Auto DevOps enhances efficiency by automatically testing code for quality, scanning for security vulnerabilities and licensing issues, packaging, and preparing for monitoring and deployment, allowing engineers to focus on product enhancement. The platform's effectiveness is likened to the value of visual aids, encouraging users to explore its functionalities through documentation and product vision pages.

GitLab Inc., a comprehensive DevOps platform, was recognized as a Strong Performer in Forrester's Q3 2018 New Wave report for Value Stream Management (VSM) tools, highlighting its capability to meet the broad, integrated solution needs of companies. GitLab's platform offers an end-to-end suite of DevOps tools, ensuring streamlined software development processes with enhanced visibility and control across the entire lifecycle. This recognition underscores GitLab's commitment to providing a single application solution for the DevOps lifecycle, enabling enterprise teams to accelerate software delivery efficiently. With a user base of over 30 million, including major enterprises like Comcast, Siemens, and NASA, GitLab continues to deliver innovations built on open-source principles, enhancing collaboration and productivity. As an all-remote company since 2015, GitLab's global team spans over 65 countries, further driving its mission to empower organizations to maximize returns on software development.

Kathy Wang, Director of Security at GitLab, has extensive experience in building security teams from the ground up, and she emphasizes the unique challenges and opportunities presented by GitLab's all-remote, transparent work environment. With a focus on securing GitLab's products and infrastructure, her team is small yet dynamic, collaborating across departments to enhance security features and address evolving threats. Wang highlights the importance of critical thinking and problem-solving skills for aspiring security practitioners, encouraging engagement in local security communities and open-source projects as pathways into the field. The security team at GitLab actively contributes to the development of new security dashboards and features, integrating actionable metrics into the company's product roadmap to benefit customers. As GitLab continues to grow, the security team plans to expand, seeking passionate individuals who value collaboration and transparency to join their efforts in promoting secure practices company-wide.

In recent years, GitLab's frontend team has embraced the integration of DevOps and Continuous Integration/Continuous Deployment (CI/CD) workflows to enhance code consistency, delivery speed, and automation, ultimately improving both developer efficiency and customer satisfaction. The team transitioned from default Rails framework conventions to using webpack for better performance and maintainability, while implementing linters and Prettier to maintain code style. This shift included adopting tools like Sitespeed for performance analysis, which has provided valuable insights into areas needing improvement. By automating many aspects of the development process, GitLab has minimized disruptions from unreliable connections and streamlined code deployment, benefiting projects such as GitLab SVG libraries and Trello Power-Up. The incorporation of CI/CD has not only facilitated problem detection and resolution but also inspired a cultural shift towards viewing performance issues from a developer's perspective, emphasizing the importance of consistent scenarios and CI-compatible tools. As a result, the team endorses the use of CI/CD for teams of all sizes, encouraging the addition of features like performance testing and code documentation generation to further enhance the development workflow.

The GitLab.com Support Team emphasizes the importance of account security and provides practical tips to prevent losing access due to common issues. Users are encouraged to set up two-factor authentication (2FA) and securely store recovery codes, either by printing them or using a password manager, to avoid being locked out if their phone is lost or stolen. An SSH key can be added to accounts to generate new recovery codes if needed, while a backup email from a well-known provider is suggested to mitigate issues with custom or company domains. Using a real name or recognizable online identities on account profiles can facilitate identity verification in cases where account recovery is necessary. These measures are recommended to ensure users maintain access, as the Support Team must adhere to strict policies for security and privacy when assisting with account recovery.

Git, a free and open-source version control system created by Linus Torvalds in 2005, is crucial for distributed code management, particularly in collaborative software development. It offers superior performance, distributed workflow support, and security features, making it ideal for large-scale projects like the Linux kernel. The text provides practical solutions to common Git mistakes, such as amending commit messages, handling unwanted files, and managing branches. It also offers recommendations for maintaining secure and efficient Git repositories by avoiding the inclusion of sensitive information and unnecessary files, and by utilizing key commands like `git clone`, `git branch`, and `git checkout`. Additionally, the text underscores the importance of repository security in web projects and suggests using commands like `git reflog` and `git reset` for undoing mistakes, while promoting community engagement through shared tips.

GitLab's blog series highlights contributions from its community, featuring Vitaliy "blackst0ne" Klachkov as the first profiled contributor. Klachkov began contributing in 2016 after discovering GitLab through a news article and was impressed by the swift feedback on his merge requests. As one of the top 50 contributors with 227 merged requests, he has significantly impacted GitLab's backend and frontend, introducing popular features and addressing technical debts. Professionally, Klachkov is a full-stack web developer at GEOPHYSTECH LLC, and he enjoys various sports and UX-related activities in his free time. He encourages others to join the GitLab community, offering assistance via Twitter, and suggests starting with the "Contributing to GitLab" page.

Meltano is an open-source tool designed to help data teams manage version control for everything from raw data to visualizations, aiming to provide a cohesive solution where many teams currently face fragmented processes. The tool has received substantial interest and feedback, particularly from data professionals who find existing solutions either too costly or cumbersome due to licensing issues. Meltano's development is guided by the vision of offering a convention over configuration framework, allowing users to easily integrate and visualize data from sources like Salesforce without extensive setup. The team's efforts include building core extractors for common platforms and exploring machine learning applications to enhance the tool's capabilities. Meltano's architecture is structured around a monorepo and Docker images to facilitate customization and collaboration within the open-source community. While currently integrated with GitLab CI for orchestration, the project's ambition is to expand its feature set to potentially rival leading data integration tools, emphasizing the importance of community contributions for its success.

Managing access to resources within Kubernetes infrastructure is crucial for ensuring reliability, security, and efficiency, with role-based access control (RBAC) offering a more manageable solution compared to attribute-based access control (ABAC). While RBAC simplifies permission management using kubectl and the Kubernetes API, ABAC requires SSH and root access, making it more complex. RBAC, which became generally available in Kubernetes 1.8, allows for permissions to be defined as Roles or ClusterRoles, with the former being namespace-specific and the latter cluster-wide. The process involves assigning permissions to users through RoleBinding or ClusterRoleBinding, emphasizing the principle of least privilege for security. Best practices include specifying exact resources and actions, using Roles instead of ClusterRoles when possible, and creating service accounts for processes that require permissions. Although GitLab currently does not support RBAC in its integration with Kubernetes, future updates are expected to address this limitation, highlighting the ongoing evolution of access management in Kubernetes environments.

Cloud adoption continues to grow rapidly, with Gartner predicting that by 2025, 80% of companies will have closed their traditional data centers. As cloud infrastructure spending increases, public cloud use is becoming a priority for many enterprises, particularly in industries like discrete manufacturing, professional services, and banking. Multi-cloud strategies are prevalent, and Kubernetes has emerged as the dominant container orchestration system. Azure is narrowing the gap with AWS in the infrastructure-as-a-service market, showing significant growth outpacing its competitors, while Google Cloud also sees substantial gains. Despite this growth, security remains a top concern for organizations using cloud services, prompting expectations that security will become increasingly integrated into cloud platforms.

GitLab has developed a streamlined approach to project and portfolio management by focusing on creating fewer but more versatile tools, exemplified by its Issues Board. This tool simplifies the complex nature of managing software and projects by using GitLab's existing issue-tracking functionality and leveraging issue labels as lists on a Kanban board. The flexibility of the Issues Board allows users to track workflows, plan cross-functionally, and maintain team visibility through customizable boards that can be tailored by labels, milestones, and assignees. The approach enhances workflow visibility and simplifies the management of multiple projects, people, or products, making it easier for users to maintain oversight. Additionally, the tool supports Agile workflows by allowing easy movement of issues between milestones, providing a high-level view of what teams are working on, and ensuring consistency throughout the development lifecycle.

The guide provides a comprehensive tutorial on using Git and GitLab Pipelines to streamline and automate the management of Home Assistant configurations for smart home enthusiasts. By addressing common frustrations like SSH access and configuration backups, the guide explains how to set up a CI/CD pipeline that automates configuration testing and deployment. It enables users to make changes remotely and securely, leveraging GitLab's Web IDE and Git's version control for easy configuration management. The tutorial covers essential steps, such as setting up a Git repository, creating a GitLab project, configuring SSH access, and defining CI/CD pipeline stages for testing, deploying, and sending notifications. This setup ensures that users can confidently update their Home Assistant settings from anywhere, with automatic testing and notification systems in place to handle configuration changes efficiently.

GitLab faces challenges in leveraging its extensive data for business operations, prompting the creation of Meltano, a comprehensive open-source tool designed to enhance data analytics across various teams such as Customer Success and Sales. Meltano, distinct from GitLab, aims to streamline the data science lifecycle by offering tools for data extraction, transformation, analysis, and orchestration, thereby integrating best practices from software development into data analytics. It seeks to democratize access to data analytics, especially for small and medium-sized companies lacking in-house data engineers, by addressing integration challenges and enabling cross-functional data insights. Meltano is currently focused on supporting Postgres, with plans to expand to other databases like Snowflake, and invites contributions from the community to enhance its capabilities. It emphasizes open collaboration, encouraging feedback and contributions to refine its analytics processes, and maintains active communication through published team calls and updates on social platforms.