October 2016 Summaries

In the two months since joining GitLab, the author has experienced rapid team integration and productivity through the company's strong emphasis on communication, focus, and iteration. GitLab's remote-only structure necessitates meticulous documentation, encapsulated in their comprehensive public handbook, and the organizational policy that each employee reports to only one manager to streamline responsibilities. Regular meetings, including one-on-ones, team standups, and casual coffee breaks, foster a deep sense of community and collaboration across departments. GitLab prioritizes small, actionable changes over extensive planning, allowing for quick decision-making and implementation. This focus on iteration is exemplified by their commitment to releasing a new version on the 22nd of every month, supported by Cycle Analytics, which measures the efficiency of moving from idea to production. The company's agile approach and continuous development suggest its increasing prominence in the market, potentially positioning GitLab as a comprehensive project management tool.

The text discusses the decision-making process behind selecting a JavaScript framework, using GitLab's adoption of Vue.js as a case study. It highlights the common inclination to follow major companies' practices due to their success, cautioning against blindly adopting frameworks without understanding their benefits. Vue.js was chosen by GitLab for its simplicity, ease of use, and minimalistic nature, which allows developers to write straightforward JavaScript without the need for excessive external libraries or plugins. The framework's balance between providing structure and allowing developer control is praised, contrasting it with other frameworks that can become complex quickly. The author emphasizes that Vue.js allows GitLab to solve complex problems efficiently, reducing code length and complexity compared to using jQuery. The success of Vue.js is attributed not only to its quality code but also to its excellent documentation, community support, and adaptability through user feedback, making it a comprehensive solution for JavaScript development.

GitLab's UX Team is unveiling a preview of their ongoing design efforts, which include enhancements for both the upcoming 8.13 release and future updates. Key initiatives include improving empty states to make them more informative and celebratory, streamlining filtering and searching functionalities to create a more powerful and cohesive search experience, and facilitating time tracking on issues with slash commands. The team is also advancing Cycle Analytics by breaking down stages into events for better data transparency and refining the Review Apps experience for better usability. Future plans involve standardizing settings pages, introducing visuals like burndown charts, and refining GitLab's overall personality, with feedback from users being actively sought to shape these developments. Acknowledgement is given to the design team members for their contributions.

OOHLALA Mobile, an education technology company, implemented GitLab CI as their CI/CD solution to manage the deployment of their increasingly complex fabfile system, which is primarily executed through Fabric. They favored GitLab CI for its simplicity, speed, and cost-effectiveness, especially given their small development team and need for tailored solutions on dedicated hardware. Unlike other CI solutions such as Jenkins, Travis CI, and CircleCI, GitLab CI's shell executor was ideal for executing fabfiles quickly, without the overhead of Docker dependency setups. The flexibility of installing GitLab runners on their own macOS and Windows machines for mobile app CI/CD was a significant advantage, allowing them to maintain control over their infrastructure and keep SSH keys secure. Ultimately, the seamless integration with GitLab CI influenced their decision to host their code on GitLab.com, as other hosting services like GitHub and Gogs did not offer significant feature advantages for their needs.

Willem de Groot attempted to publish a list of web stores containing malware, initially hosting it on GitHub and then on GitLab, but both platforms deleted it, with GitLab citing the exposure of vulnerable systems as the reason. Although GitLab emphasizes responsible disclosure, which involves notifying system owners before publicizing vulnerabilities, this case was complex as the victims included both the store owners and their users. While the responsible disclosure policy typically prioritizes notifying system owners first, GitLab decided to reinstate the list due to the greater interest in protecting users, acknowledging that web store owners have a duty to safeguard their customers. GitLab expressed appreciation for Willem's efforts to protect users and committed to contributing to a more secure internet, while also apologizing to Willem for the initial deletion.

Raising funds for a startup in a challenging economic climate requires strategic planning and engagement with the right investors who can provide not only capital but also valuable expertise and connections. GitLab's experience highlights several key strategies: the optimal timing for fundraising is when an organization has eight quarters of runway, allowing for thorough preparation and negotiation without pressure. Efficient organization and teamwork are crucial, as the fundraising process can be intensive and time-consuming, with a typical duration ranging from a few weeks to several months. Crafting a compelling slidedeck is essential, focusing on clear design and relevant content that evolves with investor feedback. Meetings and follow-ups require punctuality, preparedness, and effective communication, ensuring that all investor queries are addressed. Understanding financial terms like prorata rights is important for negotiating investment terms, particularly as they impact ownership percentages across funding rounds. Finding the right investor or board member is critical, as their industry connections and strategic insights can significantly influence a startup's trajectory. Ultimately, the focus should be on demonstrating innovation and potential to disrupt the market, which can attract investors beyond just favorable valuation metrics.

Adfinis SyGroup has implemented an automated system using GitLab CI to build Debian packages, specifically illustrated with the GoAccess log analysis tool. By utilizing a generic Docker container, which houses essential package-building tools, GitLab CI triggers tasks based on Git tags to streamline package creation. The Docker container setup, based on Debian Wheezy, allows for easy updates and includes scripts to prepare the build environment. The process involves creating necessary Debian control files, configuring a Dockerfile, and registering the container with the GitLab project. Within GitLab CI, a .gitlab-ci.yml file specifies the build stages, ensuring that dependencies are installed and the build is executed correctly, resulting in a Debian package that can be downloaded from GitLab's web interface. This workflow facilitates continuous integration and delivery, and there is an outlook towards employing a bot for further automation, enabling the deployment of packages to Aptly repositories for seamless publication.

The debate over whether to use line breaks in GitLab documents centers on balancing readability with editing ease, as the style guide suggests breaking lines after 80-100 characters to facilitate review. While some team members advocate for wrapping text to prevent endless horizontal scrolling and ease inline commenting, others argue against it, citing the challenges of realigning text during edits and the lack of necessary rewrapping features in some editors. The official stance favors wrapped text for its readability benefits, although this can complicate writing and editing processes. To address these issues, suggestions include setting a max-width for comment boxes and editors to ensure usability irrespective of line length. The broader consensus leans towards wrapped text due to the preferences of guest writers and reviewers, highlighting the need for a balance that accommodates both writing and reviewing workflows.

GitPitch is an innovative slideshow presentation service integrated with GitLab, designed specifically for developers. It allows users to create, share, and present both online and offline slide presentations using Markdown files directly from their GitLab repositories, eliminating the need for traditional presentation tools like Keynote or PowerPoint. By simply adding a PITCHME.md file to a project, developers can instantly generate a slideshow that reflects their project's style, image, or brand, with options for customization through themes, background images, and custom CSS. GitPitch also supports features essential for developers, such as code blocks, GitHub GIST, and math formulas, while ensuring presentations are easily accessible via a public URL linked to the GitLab project. This integration enhances the GitLab workflow by allowing for the use of feature branches to tailor presentations for different audiences and making it easy to share slides post-presentation. Created by David Russell, GitPitch is an open-source project that aligns with GitLab's ethos of fostering collaboration and rapid idea-to-production processes.

Sid, the CEO, offered personal assistance to founders applying to Y Combinator by conducting office hours and one-on-one meetings to review and improve their application forms, following a blog post that gained traction on HackerNews. The initiative aimed to ensure candidates' responses were clear and concise, as recommended in the blog. Recordings of Sid's calls with founders from companies like Color Search and TrueJob were shared on YouTube, providing a resource for other applicants to refine their submissions. These sessions highlighted practical advice and encouraged collaborative improvement among aspiring entrepreneurs.