January 2016 Summaries

Jacob Schatz, the Principal Front End Engineer at GitLab, shares his experience working at the company since December 2015, emphasizing the transparent and collaborative environment that characterizes the workplace. Unlike many other companies with a distinct "upper management divide," GitLab involves all team members in decision-making processes, fostering a culture of openness and skill improvement. Schatz, a JavaScript developer, has expanded his knowledge of Ruby while contributing to the open-source development model at GitLab, which prioritizes both an excellent user experience (UX) and developer experience (DX). He likens this approach to an "open kitchen," where the quality of the internal code must match the external product appearance. GitLab's front end is built using jQuery and CoffeeScript, and the team is looking to hire more skilled JavaScript developers to enhance the front-end architecture and reduce code complexity. Schatz recounts his past experiences with browser compatibility issues, highlighting the importance of well-written, maintainable code at GitLab, which releases updates monthly and requires a balance between addressing small issues and considering broader architectural improvements.

GitLab is actively addressing issues related to maintaining open-source software projects by proposing enhancements to its platform to support better collaboration and communication. Acknowledging challenges such as incomplete issue reports and excessive "+1" comments, GitLab plans to introduce custom fields, mandatory templates, and a first-class voting system to streamline issue reporting and feedback. They are also considering a more visible placement of contribution guidelines to ensure adherence. Additionally, GitLab supports alternative merging strategies to accommodate user preferences and emphasizes its open development process, where community members can participate by commenting, creating issues, voting, and submitting merge requests. These efforts aim to improve the overall user experience and make GitLab a more efficient and welcoming platform for all software projects.

GitLab is celebrating its 50th monthly release with a webcast scheduled for January 28th, where Job van der Voort, the VP of Product, will guide participants through the new features of GitLab 8.4. This release includes enhanced search capabilities, improved importing from GitHub and GitLab, and upgrades to popular features like GitLab CI. Additionally, there are improvements in artifact support, runner auto-queue for enhanced computing power, and upcoming CNAME support for GitLab Pages, particularly for GitLab EE and GitLab.com users. The webcast will also feature a live Q&A session with Job and Dmitriy Zaporozhets, GitLab's project founder and CTO, who will discuss the release process and share insights learned from managing the project. The event promises to offer a comprehensive overview of GitLab's current direction and future plans.

The text discusses the intricacies and challenges of stewarding open-source projects, particularly those supported by commercial entities, using the example of GitLab. It outlines the balance required between maintaining open-source ethos and meeting business needs to ensure sustainability, emphasizing transparency, open communication, and collaboration with the community. The text acknowledges the potential tension between commercial interests and the project's best outcomes, advocating for clear policies and open governance to maintain trust and authenticity. By detailing their commitment and policy, the authors aim to align business practices with open-source principles, allowing community members to hold them accountable and fostering a culture of transparency and collaboration.

At GitLab, the practice of creating Work In Progress (WIP) merge requests is encouraged to manage complex features that require extensive development time. By marking a merge request as WIP, developers can benefit from code review and GitLab CI's code checks without the risk of prematurely merging incomplete work. This approach leverages the open-source community's strength in providing early feedback, allowing developers to catch potential mistakes and receive guidance throughout the development process. GitLab promotes a culture of early sharing and decision-making to foster automatic collaboration and improve project outcomes, exemplified by their use of WIP merge requests for major projects like the Elastic Search implementation.

In early 2015, GitLab participated in Y Combinator's winter batch, an experience that provided the team with mentorship, a focused environment, and invaluable networking opportunities. During the program, GitLab's team, consisting mostly of engineers, moved to the Bay Area and worked collaboratively in a small apartment, fostering a strong team culture and camaraderie. The program emphasized setting clear goals, such as increasing the number of GitLab downloads, which, despite not meeting the ambitious 20% weekly growth target, motivated the team to push themselves further. The access to Y Combinator's vast network and the supportive atmosphere among fellow startups and alumni were significant advantages, offering direct assistance, referrals, and technical help. Even after the program, GitLab maintained the focus and momentum gained, expanding their team and sales significantly, and continued to engage with investors and peers through structured updates. The success and growth experienced since their time at Y Combinator reflect their gratitude and the lasting impact of the program on their development.

GitLab stands out in the software development industry for its unprecedented level of transparency, allowing users and contributors to access detailed information about future features and development progress. Unlike many companies that keep their development roadmaps secret to maintain a competitive edge, GitLab openly shares its plans and objectives through its Direction and What's Coming pages, offering a clear view of priorities and upcoming releases. This openness not only helps users anticipate new features but also enables contributors to align their efforts with the project's goals. GitLab's approach addresses common frustrations with other projects where feature requests seem to vanish without acknowledgment, by making the status of proposals visible and encouraging community input and collaboration. This transparency is not only beneficial for users but also fosters a collaborative environment, enhancing the open-source ethos while balancing customer requests with project sustainability.