July 2016 Summaries

Koding and GitLab aim to streamline the development process by eliminating the time-consuming task of creating development environments, enabling developers to contribute code faster through a one-click setup for projects, issues, and merge requests within a complete IDE. This integration allows teams to work collaboratively and seamlessly across various cloud platforms, enhancing efficiency by making every GitLab repository buildable on any cloud. The vision is to simplify the transition from idea to production using a unified set of tools, facilitating everything from issue creation and code writing to testing and deployment, and providing feedback on project health and development time. The upcoming integration, expected to debut on August 22nd, seeks to foster collaboration and streamline workflows, allowing developers to focus more on writing code and improving their products.

Captain Train's transition from Jenkins to GitLab CI for building their web-app has significantly improved their development process, enhancing speed, reliability, and control. While Jenkins was a robust solution, it suffered from slow and unreliable builds due to resource constraints, leading to issues like random crashes of PhantomJS during tests. By migrating to GitLab CI, Captain Train benefits from dockerized builds that prevent process interference and facilitate easy scaling across different architectures. The configuration is now managed through a simple .gitlab-ci.yml file, allowing for seamless integration with the git workflow and increased accessibility for project maintainers. This change has not only reduced build times but also improved engineering quality and developer satisfaction by making continuous integration more approachable and efficient. Additionally, the GitLab CI interface offers a comprehensive overview of build jobs, providing clear insights into build statuses and facilitating smoother testing processes for merge requests.

In recent years, the software development landscape has shifted from traditional waterfall and agile methodologies to a model emphasizing frequent, smaller deployments, moving away from large biannual releases that can create bottlenecks and coordination issues. This trend toward early-and-often releases focuses on delivering smaller slices of customer value iteratively, allowing for easier bug identification and quicker fixes, without needing to wait for all features to be complete. Time-based releases, adopted by companies like GitLab, Docker, and Ubuntu, decouple features from release schedules, ensuring that only ready features are deployed, while patches can be issued as needed. This approach reduces the time between releases, enhances usability, and improves overall development efficiency, highlighting that the quest for a perfect software release is outdated due to the rapid pace of technological advancement.

GitLab, led by its CEO, embraces an open core business model by offering both open source (GitLab CE) and closed source (GitLab EE) software, while striving to maintain transparency and open collaboration in its development process. Despite the common misconception, the hosted service GitHub.com is not open source; it is free for open source projects but based on closed source software. This distinction often leads to confusion between open source hosting services and the actual open source software. GitHub, although closed source, significantly contributes to the open source community by supporting projects like Git and Ruby on Rails and releasing various libraries and applications. GitLab utilizes open source software that GitHub has released, highlighting the interconnected nature of software development.

The post discusses the use of the Kramdown markdown engine for creating and styling content on GitLab's website, highlighting its advantages over the previously used RDiscount engine. Kramdown allows users to apply CSS classes, custom IDs, and attributes directly within markdown files, enabling enhanced customization such as colored text and specific styling for headings and paragraphs. It supports the inclusion of HTML blocks, making it possible to embed multimedia content like videos and interactive elements such as CodePens. The post emphasizes the engine's ability to generate automatic tables of contents and integrate Font Awesome icons, showcasing its versatility for web content creation. It invites users to explore more features through the GitLab Markdown Guide and encourages contributions to the open-source project, fostering a collaborative environment for continuous improvement and innovation in markdown use.

GitLab began as a part-time open-source project by Dmitriy Zaporozhets and Valery Sizov in 2011, later joined by Sid Sijbrandij, who helped create GitLab.com, the company's first SaaS offering. The company markets both an open-source Community Edition and a proprietary Enterprise Edition, striking a balance between open-source sustainability and monetization. GitLab is renowned for its transparent development process, encouraging user feedback to enhance product offerings. It has grown into a major player in the software industry, used by over 100,000 organizations, and has adapted its business model to serve large organizations with single-tenant installations. GitLab’s pricing strategy has evolved through trial and error, and the company is now focusing on expanding its sales and marketing efforts to compete with proprietary solutions. Despite the cloud's growing influence, GitLab's success with on-premises installations challenges the conventional wisdom of a full shift to the cloud, as many companies prefer control over their source control solutions due to security and legal reasons. The company has embraced venture funding to accelerate growth and aims to become a dominant player in the git hosting space, capitalizing on its open-source roots and comprehensive developer collaboration tools.

GitLab is a versatile, self-managed Git repository system available in both a free Community Edition and a subscription-based Enterprise Edition, suitable for those seeking full control over their source control systems. The text outlines the process of deploying a GitLab instance using Microsoft Azure, which offers a pre-configured GitLab virtual machine (VM) through its Marketplace. This setup allows users to quickly and efficiently explore GitLab's features without significant time investment or administrative overhead. It details the steps to create an Azure account, configure a GitLab VM, and manage resources, emphasizing the ease of using Azure's interface and the benefits of utilizing Azure credits for trials. Additionally, the text covers maintaining the GitLab instance, including updating procedures, and highlights Azure as a secure, scalable platform for those who find GitLab an optimal solution for source code management.

GitLab, a remote-only company that has grown from 10 to over 90 employees across 26 countries, emphasizes the importance of effective communication and transparency through its open source Handbook. By making this Handbook publicly available under a Creative Commons license, GitLab allows others to learn from their practices, ensuring that company policies remain up-to-date and accessible to all employees regardless of location. This transparency not only streamlines onboarding and hiring by providing potential employees with a clear view of company culture and processes but also ensures that all team members are aligned with current practices. The Handbook's open-source nature encourages collaboration and continuous updates, reflecting the dynamic needs of the organization. GitLab advocates for other companies to adopt similar practices, advising them to focus on universal processes such as values and communication first, and to start by building a shared document that evolves over time.

Open sourcing components of a company's infrastructure can provide significant benefits, but there are common misconceptions that often deter businesses from adopting this practice. Contrary to popular belief, open sourcing does not equate to giving away a business for free or losing control over the code. Companies can still maintain ownership and manage contributions by choosing appropriate open source licenses. Moreover, the presence of open source in widely used platforms like Windows, macOS, and Linux, as well as in modern web hosting stacks and mobile devices, highlights its inherent value. Open sourcing does not necessarily lead to financial loss or business failure; instead, many successful companies like Red Hat and Comcast have thrived by fostering ecosystems around their projects. Concerns about competitors stealing ideas or features may be mitigated by the fact that the business ecosystem, including product management and marketing, plays a crucial role in differentiating a company. While the process can be daunting, open source remains a viable path for innovation and collaboration.