<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[GitLab Magazine - Medium]]></title>
        <description><![CDATA[GitLab is a single application for the entire DevOps lifecycle. - Medium]]></description>
        <link>https://medium.com/gitlab-magazine?source=rss----2d8b29d6db33---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>GitLab Magazine - Medium</title>
            <link>https://medium.com/gitlab-magazine?source=rss----2d8b29d6db33---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:55:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/gitlab-magazine" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 things we learned from you in recent UX research]]></title>
            <link>https://medium.com/gitlab-magazine/5-things-we-learned-from-you-in-recent-ux-research-711214e20068?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/711214e20068</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Emily von Hoffmann]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 01:46:32 GMT</pubDate>
            <atom:updated>2019-11-05T01:46:07.380Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rjgyUo4OxkfQzOaV" /><figcaption>Photo by <a href="https://unsplash.com/@mike_meyers?utm_source=medium&amp;utm_medium=referral">Mike Meyers</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>How you use Snippets, whether to rename Auto DevOps, how to improve our billing process, and more.</h4><p>This past quarter, the GitLab UX research team was charged with supporting some big <a href="https://about.gitlab.com/company/okrs/">OKRs</a>:</p><ul><li><a href="https://gitlab.com/gitlab-com/www-gitlab-com/issues/4932">Create</a> products and experiences that users love and value.</li><li>Complete at least 5 qualitative interviews per Product Manager — part of scaling UX research across the org, which we’ll <a href="https://gitlab.com/gitlab-org/gitlab-design/issues/665">continue</a> next quarter.</li><li><a href="https://gitlab.com/gitlab-org/ux-research/issues/362">Implement</a> a pilot of customer satisfaction surveys.</li></ul><p>Throughout all of it, researchers continued working to learn more about each <a href="https://about.gitlab.com/handbook/product/categories/">stage group</a>. Here are some of the highlights.</p><h3>1. Snippets can be an extremely useful knowledge base</h3><p><a href="https://gitlab.com/gitlab-org/ux-research/issues/339">Using Snippets</a> to share commonly used code throughout an organization (fixes, install scripts, social icons, etc) can be beneficial for consistency, saving time on searching for solutions, and onboarding new or junior team members.</p><p><a href="https://gitlab.com/gitlab-org/gitlab/issues/15958">Group-level Snippets</a>, <a href="https://gitlab.com/gitlab-org/gitlab/issues/14340">Multi-file Snippets</a>, and <a href="https://gitlab.com/gitlab-org/gitlab/issues/14228">Version control for Snippets</a> are highly upvoted issues in GitLab’s issue tracker.</p><p>Check out the <a href="https://gitlab.com/groups/gitlab-org/-/epics/2030">full results</a>.</p><h3>2. After considering other options, you prefer the name “Auto DevOps”</h3><p>We surveyed nearly 200 developers to evaluate 4 terms: ‘Auto Config’, ‘Auto Pipelines’, ‘NoOps’, and ‘Auto DevOps’ (our existing name). The term that did best both in terms of 1) allowing users to accurately predict what the feature does and 2) was considered appropriate for the feature’s definition (i.e. a feature that automatically detects, builds, tests, deploys, and monitors you applications) was Auto DevOps, with Auto Pipelines as a very close second. Consequently, it was decided to stick with Auto DevOps.</p><p><a href="https://gitlab.com/gitlab-org/ux-research/issues/243#note_224667453">Full results</a></p><h3>3. You wanted a new flow for enabling security checks</h3><p>Based on insights gathered in a previous usability study around users’ mental model, the Secure team created a new flow for enabling security checks, which allows users to configure security checks from the UI itself. We then tested the new flow and saw significant improvement — all participants were able to complete the task, as opposed to only 1 out of 5 before the new design was created. Yay for evidence-based design!</p><p><a href="https://docs.google.com/presentation/d/1blpG78sBTNYcFyP1DH4gNjmJSB8SGm4xMgVtOe9UXLo/edit">Full results</a></p><h3>4. Logs contain rich data, and you need a better way to manage it</h3><p>Logs are captured for a number of reasons: audit/compliance, security (to monitor against abuse/attacks), and for troubleshooting when things go wrong. Logs are able to capture more information than metrics, but because they capture so much more information, users need a way of managing them, searching through them, and surfacing insights.</p><p>Another interesting finding: You use tracing when things aren’t running as expected and you want to find out what’s going on “under the hood.” It’s underutilized compared to logging.</p><p><a href="https://gitlab.com/gitlab-org/ux-research/issues/276">Full results</a></p><h3>5. Our billing processes just aren’t cutting it</h3><p>Our billing processes are optimized for large orgs, but don’t support the needs of small businesses as effectively or efficiently. Additionally, our true-up policy is not transparent. We saw customers mistakenly expect adding users to be automatically prorated, often leading to surprise charges at renewal time.</p><p>Finally, we have an opportunity to help more customers self-serve. Self-hosted customers must contact GitLab every time they want to add users to their license, creating friction for customers and taking up valuable support/sales time.</p><p><a href="https://gitlab.com/groups/gitlab-org/-/epics/1963">Full results</a></p><h3>Join GitLab First Look</h3><p>Did you recognize some of the above as your own needs and wants? Or did you disagree with everything completely?! Either way, we want to hear from you.</p><p>You can participate in interviews, surveys, beta tests, and more from the comfort of your own computer 💻✨Your feedback is incredibly important to us, and we hope you consider joining our research program, <a href="https://about.gitlab.com/community/gitlab-first-look/">GitLab First Look</a>.</p><p><em>This round-up was compiled using </em><a href="https://docs.google.com/presentation/d/1nDFgGQpr6gLQ6wp8UC0WIdb_ZNWGSDCk1Dt8-dliduw/edit#slide=id.g651551733c_6_0"><em>research and analysis</em></a><em> by Katherine Okpara, Tali Lavi, Amelia Bauerly, Iain Camacho, Eileen Ruberto, Lorie Whitaker, and Jeff Crow.</em></p><p><em>Originally published at </em><a href="https://about.gitlab.com/blog/2019/10/21/five-things-we-learned-from-you-in-recent-ux-research/"><em>https://about.gitlab.com</em></a><em> on October 21, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=711214e20068" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/5-things-we-learned-from-you-in-recent-ux-research-711214e20068">5 things we learned from you in recent UX research</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab Meetups: August 2019]]></title>
            <link>https://medium.com/gitlab-magazine/gitlab-meetups-august-2019-9b25beb4427b?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/9b25beb4427b</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[meetup]]></category>
            <dc:creator><![CDATA[John Coghlan]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 22:15:06 GMT</pubDate>
            <atom:updated>2019-08-08T13:53:55.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SC0Ko07fybuT5XM58thlIw.jpeg" /></figure><h4>Come see us this month in a city near you!</h4><p>We have another packed month of community events leading into our inaugural GitLab Commit user conferences in <a href="https://about.gitlab.com/events/commit/?utm_medium=other&amp;utm_source=communityoutreach&amp;utm_campaign=gitlabcommit&amp;utm_content=brooklyn">Brooklyn</a> and <a href="https://about.gitlab.com/events/commit/?utm_medium=other&amp;utm_source=communityoutreach&amp;utm_campaign=gitlabcommit&amp;utm_content=london">London</a> this fall. Here is where you can find the GitLab community in August.</p><h4>Orange County GitLab Users Group</h4><p>Join the OC GitLab Users Group in Irvine on Thursday, August 1. RSVP and Details on <a href="https://www.meetup.com/Orange-County-GitLab-Users-Group/events/263201035/">Meetup</a>.</p><h4>GitLab Perú</h4><p>On August 2, the GitLab Perú community will be gathering to learn about GitLab at Crack the Code in Lima. Details and RSVP on <a href="https://www.meetup.com/GitLab-Peru/events/263472004/">Meetup</a>.</p><h4>GitLab Philadelphia</h4><p>Interested in Open Source? Don’t miss this meetup in Philly on August 13. Details and RSVP on <a href="https://www.meetup.com/Gitlab-Philadelphia/events/263482668/">Meetup</a>.</p><h4>GitLab Austin User Community</h4><p>Join the GitLab Austin User Community to talk about remote work at Proof on August 14. Details and RSVP on <a href="https://www.meetup.com/GitLab-Austin-User-Community/events/262738328/">Meetup</a>.</p><h4>Austin Vue.js Meetup</h4><p>If you’re a front-end engineer, you probably know about GitLab’s love for Vue. Now you can learn about how to use Cypress to test while you code at the Vue Meetup in Austin on August 20. Details and RSVP on <a href="https://www.meetup.com/The-Austin-Vue-js-Meetup/events/mdfcdryzlbbc/">Meetup</a>.</p><h4>GitLab Guatemala</h4><p>Join the first GitLab Guatemala meetup on August 20. Details and RSVP on <a href="https://www.meetup.com/Gitlab-Guatemala/events/263588261/">Meetup</a>.</p><h4>Philly Vue</h4><p>Ben Hong, Senior Frontend Engineer on the Meltano team at GitLab &amp; Vue community partner, will be giving a talk on Vuepress in Philadelphia on August 21. Details and RSVP on <a href="http://Ben Hong - Senior Frontend Engineer on the Meltano team at GitLab &amp; Vue community partner - Vuepress">Meetup</a>.</p><h4>Cloud Native and Kubernetes Minneapolis</h4><p>Get an introduction to CI/CD and Pipelines at this CNCF-hosted meetup in Minneapolis on August 22. Details and RSVP on <a href="https://www.meetup.com/Cloud-Native-Minneapolis/events/gtwkhqyzlbdc/">Meetup</a>.</p><h4>Greater Atlanta GitLab Meetup</h4><p>Don’t miss a great demo on how GitLab can help you go from idea to production at the first GitLab meetup in Atlanta (and first to be hosted at an airport) on August 22. Details and RSVP on <a href="https://www.meetup.com/Greater-Atlanta-Gitlab-Meetup/events/263534663/">Meetup</a>.</p><h4>GitLab Moscow User Community</h4><p>The first GitLab Meetup in Moscow is scheduled for August 22. Hear 3 talks about GitLab from local GitLab team members. Details and RSVP on <a href="https://www.meetup.com/GitLab-Moscow-User-Community/events/263772294/">Meetup</a>.</p><p>The most exciting part of the calendar for August is the number of new groups that are starting this month. Atlanta, Austin, Guatemala, Moscow, Orange County, Peru, and Philadelphia are all new groups.</p><p>Ready to bring the GitLab community together in your part of the world? Let <a href="https://twitter.com/john_cogs/">me</a> <a href="/service/mailto:evangelists@gitlab.com">know</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b25beb4427b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/gitlab-meetups-august-2019-9b25beb4427b">GitLab Meetups: August 2019</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we use automation to scale-up security at GitLab]]></title>
            <link>https://medium.com/gitlab-magazine/how-we-use-automation-to-scale-up-security-at-gitlab-f8440574e0e4?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/f8440574e0e4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Heather Simpson ]]></dc:creator>
            <pubDate>Thu, 18 Jul 2019 17:35:15 GMT</pubDate>
            <atom:updated>2019-07-18T17:35:15.746Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pJbwJYw-pr2NAP0A" /><figcaption>Photo by <a href="https://unsplash.com/@shotinraww?utm_source=medium&amp;utm_medium=referral">shotinraww</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong><em>We sat down with GitLab senior security engineer Alex Groleau to talk about the opportunities for automation in security, what he’s currently focusing on in his role, and where he sees the industry moving.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*5PuJvSoBvGCMVAzg6R7PNQ.jpeg" /></figure><p><strong>Name: </strong>Alex Groleau</p><p><strong>Title: </strong>Senior security engineer, automation</p><p><strong>Alex on: </strong><a href="https://gitlab.com/agroleau">GitLab</a> | <a href="https://www.linkedin.com/in/awgneo">LinkedIn</a> | <a href="https://twitter.com/awgneo">Twitter</a></p><p><strong>In 50 words or less, tell us what you do at GitLab:</strong></p><p>I am a senior security engineer specializing in security automation. This involves constructing efficient security systems that prevent or detect intrusions to GitLab.com and the organization while assisting and scaling other teams proactively with their security needs.</p><p><strong>What’s the most challenging or rewarding aspect of your role?</strong></p><p>The nascent GitLab security team has grown fast over the last year to meet the needs of the rest of the burgeoning organization. We have very specific goals in mind with a unique set of constraints, such as the company’s warranted obsession with <a href="https://about.gitlab.com/handbook/values/#dogfooding">dogfooding</a> the GitLab product as much as possible, that make our path very interesting. It often feels like we are solving more problems than just our own, but then again, that is exactly what the GitLab product is.</p><p><strong>What are the top two or three initiatives you’re currently focused on?</strong></p><p>The security team is holistically focused on <a href="https://gitlab.com/gitlab-com/gl-security/engineering/issues/466">zero trust architecture</a>. But like anything at GitLab, this initiative extends beyond corporate boundaries and into the features our team members and customers use everyday. On the internal side, I am helping to ingest audit logs from all of the third party services we use internally for threat detection. On the customer side, I am enhancing the security of our CI/CD runner environment to prevent bad behaviors that violate our terms of service and harm other customers on the GitLab.com platform. As a side effect, this will also allow customers to <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/58921">view various performance metric information associated with each pipeline job run</a>.</p><p><strong>How did you get into security?</strong></p><p>With the vast and changing landscape of knowledge that is computer science, I never once envisioned myself working directly on security projects. In my younger years, I would hack and break into things, but this passion for breaking things quickly turned into a passion for creating things before and during college. Working on features that you can put right in front of a user to make their day easier stole my interests away from the thought that these features could one day be hacked by nefarious actors.</p><p>Customer features and automations are synonymous terms. After college, I gravitated towards roles that involved automating significant portions of business processes for a better user experience. From point-of-sale manufacturing and servicing automation software to radio automation software, to mass-digital marketing automation software, the process of removing steps and waste within any organization in any industry can easily be a lifetime career. The Japanese have a term for this form of corporate waste, “Muda,” and its eradication is pivotal to <a href="https://en.wikipedia.org/wiki/Kaizen">Kaizen</a> and lean process thinking.</p><blockquote>From point-of-sale manufacturing and servicing automation software to radio automation software, to mass-digital marketing automation software, the process of removing steps and waste within any organization in any industry can easily be a lifetime career.</blockquote><p>With every industry ripe for automation, you have to decide what industries you want to support and what skills you want to learn that are unique to that industry or a product within the industry. GitLab is my first professional foray into security for security’s sake, and I could not be happier with my decision. This is a skill set I needed to solidify; having kept best security practices on my radar — but very much on the sidelines, as I automated elsewhere. Having these practices in mind and a humble understanding of the critical role security engineers play in any organization is the reason why I am currently in security.</p><p><strong>What is the most important emerging trend you see in security or technology?</strong></p><p>The decentralization of everything and the emergence of more user friendly peer-to-peer technologies. From BitTorrent to Bitcoin, from Holochain to Ethereum, new P2P technologies are taking over the world and removing the need for traditional, centralized organizations. Users will soon have the technology to truly own their own credentials and personal information online with self-sovereign identity. In parallel, cloud applications will no longer require data centers that sift through their user’s information on the regular and give it to the highest bidders. The original sin of the Internet (advertising as a business model) is finally being reversed and security will shift from central authority to the hands of users.</p><p><strong>From the perspective of your role, what’s GitLab doing better than anyone else in terms of security?</strong></p><p>GitLab has a product division called “<a href="https://about.gitlab.com/handbook/engineering/ops/secure/">Secure</a>” , that is separate from the security team; which works to protect the corporation. There are incentives to secure both GitLab.com and GitLab the product and these teams working together internally will generate compound incentives and solutions that can be shared on both sides. Two recent internal security initiatives on the security automation team are likely to both end up as customer facing features for the GitLab product. One being an <a href="https://gitlab.com/gitlab-com/gl-security/engineering/issues/446">escalation engine</a> for security alerts and the other being the pipeline job metrics collection system mentioned above.</p><p><strong>What is the most significant piece of Security advice you could provide to a colleague or friend?</strong></p><p>Use a different password, preferably a completely random one, and two-factor authentication, for every website you visit. Use whatever form of password manager to keep them all straight. I have used 1Password for years. Websites are hacked daily and there is a high chance that one of the websites you have an account at was hacked within the last year. If your passwords are all the same, you are likely compromised as you read this sentence.</p><p><strong>GitLab is very unique in that we strive to be incredibly transparent…about everything. What sort of challenges does that present to you as a security professional? What opportunities?</strong></p><p>Having seen the way transparency has been of great benefit to the rest of GitLab, I don’t see any challenges specific to the field of security. If we truly believe in full transparency, it should not end at the security team. The only transparency concern I have company-wide is the timing of information release. No matter what kind of information you are releasing, you want to ensure you are not going to cause others harm. The timing of our security releases is <a href="https://about.gitlab.com/handbook/engineering/infrastructure/blueprint/release/security/#what-are-the-slas-for-releasing-the-fixes-to-public-for-each-of-the-severitypriority-labels">well documented</a> in the GitLab Handbook, but I am not sure I have seen “transparency SLAs” defined for other forms of information, such as features that might have some sort of competitive advantage associated with them. Perhaps we should have that.</p><h3>And, now, for the questions you really want to have answered:</h3><p><strong>If you could automate any one thing, what would it be?</strong></p><p>The entire health insurance industry.</p><p><strong>Favorite Linux distro?</strong></p><p>Arch Linux. Giant point release distributions never last for me. Incremental daily updates are far more manageable.</p><p><strong>When traveling, packing cubes or no packing cubes?</strong></p><p>Packing cubes for anything larger than a carry-on so that shift does not occur.</p><p><strong>Who is your favorite superhero and why?</strong></p><p>The world does not and has never needed superheroes. In my opinion, it is awful to convince anyone that there is some Earthly being that is watching out for us and has our best interests at heart. We all have to have the skills and knowledge to watch out for each other and not place any human on a such an extreme pedestal.</p><p><em>Have a question to ask our security team? Leave a comment below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8440574e0e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/how-we-use-automation-to-scale-up-security-at-gitlab-f8440574e0e4">How we use automation to scale-up security at GitLab</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab Meetups: July 2019]]></title>
            <link>https://medium.com/gitlab-magazine/gitlab-meetups-july-2019-e0e3a8fbd781?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0e3a8fbd781</guid>
            <category><![CDATA[tech-events]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[John Coghlan]]></dc:creator>
            <pubDate>Fri, 28 Jun 2019 18:13:07 GMT</pubDate>
            <atom:updated>2019-06-28T18:13:07.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JihFOzGB9jpwik3IvJat_A.jpeg" /><figcaption>GitLab Korea Meetup — June 2019</figcaption></figure><h4>Check out some of the GitLab meetups around the world this month</h4><p>The growth of our community over the last few months has been amazing. In 2019, our community organizers have hosted more than 50 events across Asia, Australia, Africa, Europe, South America, and North America.</p><p>We’re excited to keep the momentum going. We are excited to connect with new organizers who are ready to lead meetups in their area. If you’re interested in learning more about our Meetups program, take a look at our <a href="https://about.gitlab.com/community/meetups/">GitLab Meetups</a> page or contact <a href="/service/mailto:evangelists@gitlab.com">me</a> and we can set up time to chat.</p><p>If you’re just here to see what’s happening in July, wait no more. 😃</p><h4>GitLab Nigeria Community</h4><p>This meetup on July 6 in Warri, Nigeria is targeted to beginner and intermediate developers who want to learn more about how and why to use GitLab to improve their skills and productivity. Details and RSVP on <a href="https://www.meetup.com/GitLab-Nigeria-Community/events/261974443/">Meetup</a>.</p><h4>GitLab France Meetup</h4><p>On July 9, the GitLab community with gather to learn about the value of using a single tool for your entire DevOps workflow with a focus on GitLab’s CI/CD tool. Details and RSVP on <a href="https://www.meetup.com/GitLab-Meetup-France/events/262502632/">Meetup</a>.</p><h4>DC Spring Framework Meetup</h4><p>Learn the cool ways that Gitlab supports the full life cycle of Spring Boot development and how you can use Gitlab to deploy your application to Cloud Foundry on July 11 in Washington, DC. Details and RSVP on <a href="https://www.meetup.com/DC-Spring-Framework/events/261860829/">Meetup</a>.</p><h4>GitLab Nigeria Community</h4><p>A second meetup aimed to help beginner and intermediate developers who want to learn more about how and why to use GitLab to improve their skills and productivity will take place in Nigeria on July 13 in Effrun. Details and RSVP on <a href="https://www.meetup.com/GitLab-Nigeria-Community/events/261975292/">Meetup</a>.</p><h4>GitLab Tokyo Meetup</h4><p>Join the GitLab Tokyo community on July 19 for a meetup in conjunction with Open Source Summit Japan. Details and RSVP on <a href="https://gitlab-jp.connpass.com/event/132776/">Connpass</a>.</p><h4>Frontend London</h4><p>Learn about GitLab’s journey to becoming a PWA at Frontend London on July 25. Details and tickets (available after July 16) on <a href="https://www.frontendlondon.co.uk/">Frontend London</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0e3a8fbd781" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/gitlab-meetups-july-2019-e0e3a8fbd781">GitLab Meetups: July 2019</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab 12.0 Release Parties]]></title>
            <link>https://medium.com/gitlab-magazine/gitlab-12-0-release-parties-c641476f4f39?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/c641476f4f39</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[tech-events]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[gitlab]]></category>
            <dc:creator><![CDATA[John Coghlan]]></dc:creator>
            <pubDate>Wed, 12 Jun 2019 21:45:36 GMT</pubDate>
            <atom:updated>2019-06-12T21:45:35.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBzda8mMK64zlRFponGQMg.jpeg" /><figcaption>Who is excited for 12.0? Photo by <a href="https://medium.com/u/cc862325bbcd">Philippe Charrière</a></figcaption></figure><h3>Join us for a GitLab 12.0 release party near you!</h3><h4>We’d love to help you organize or find an event in your local area.</h4><p>Later this month, we’re releasing <a href="https://about.gitlab.com/upcoming-releases/">GitLab 12.0</a>. While maintaining a <a href="https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release-dates-at-gitlab/">monthly release cadence</a> is always cause for celebration, this time is different. We’re encouraging everyone in the wider GitLab community to take a moment to step back and enjoy the growth and success our community has experienced this year. Since <a href="https://about.gitlab.com/releases/">11.0</a>, we’ve hosted more than 160 meetups and our Meetup community has grown by more than 3,200 members. Amazing! We have release parties scheduled in <a href="https://www.meetup.com/GitLab-Meetup-Hamburg/events/262026723/">Germany</a>, <a href="https://www.meetup.com/GitLab-Meetup-Jalandhar/events/261729281/">India</a>, and <a href="https://www.meetup.com/GitLabANZ/events/261819148/">Australia</a> and we want to get even more people involved.</p><h3>How to get involved</h3><p>We would love to help you organize an event in your local area. Reach out to GitLab’s <a href="/service/mailto:evangelists@gitlab.com">Evangelist Program Manager</a> to get started. We’ll send swag, cover the costs of food and drinks, and help you prepare to present a talk about the success of the GitLab community over the last 12 releases and what we’re looking forward to in the future.</p><p>Not ready to organize an event? Check out our <a href="https://www.meetup.com/pro/gitlab">Meetup Pro</a> page to see the complete list of upcoming GitLab meetups near you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c641476f4f39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/gitlab-12-0-release-parties-c641476f4f39">GitLab 12.0 Release Parties</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab Meetups: June 2019]]></title>
            <link>https://medium.com/gitlab-magazine/gitlab-meetups-june-2019-274ae8aee6d0?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/274ae8aee6d0</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[John Coghlan]]></dc:creator>
            <pubDate>Fri, 31 May 2019 17:44:30 GMT</pubDate>
            <atom:updated>2019-05-31T17:44:29.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6bb4IbcFV2RYWpFlPFf2UQ.jpeg" /><figcaption>GitLab Nigeria Community Meetup in Warri</figcaption></figure><h4>Here are some of the GitLab meetups happening around the globe this month 🌏</h4><h4><strong>GitLab Nigeria Community</strong></h4><p>Following a successful launch in Warri in May, the GitLab Nigeria Community will be meeting again! Join them in <a href="https://www.meetup.com/GitLab-Nigeria-Community/events/261068115">Otuoke</a> on June 1 and <a href="https://www.meetup.com/GitLab-Nigeria-Community/events/261640785/">Benin</a> on June 22.</p><h4>VMware {code}</h4><p>GitLab and VMware are partnering to show you how to be budget conscious in an automated world in Palo Alto on June 5. Can’t make it to Palo Alto? This one will be livestreamed. Details and RSVP on <a href="https://www.meetup.com/VMware-code/events/261490345/">Meetup</a>.</p><h4>Cloud Security Alliance — Atlanta</h4><p>GitLab will be joining a Cloud Security panel discussion on June 6 in Atlanta at the Cloud Security Alliance meetup. Details and RSVP on <a href="https://www.meetup.com/Cloud-Security-Alliance-Atlanta-Chapter-Meetup/events/260801796">Meetup</a>.</p><h4>GitLab Tokyo Meetup</h4><p>Get an update about <a href="https://www.youtube.com/watch?v=V2Z1h_2gLNU">GitLab Contribute</a> from people who were there on June 6 at the monthly GitLab Tokyo Meetup. Details and RSVP on <a href="https://gitlab-jp.connpass.com/event/129245/">Connpass</a>.</p><h4>CDS Lyon</h4><p>Fall in love with GitLab Runners at the CDS Lyon meetup on June 6. Details and RSVP on <a href="https://www.meetup.com/Econocom-Digital-Application-Services-CDS-Lyon/events/261013613/">Meetup</a>.</p><h4>GitLab Polska — Wroclaw</h4><p>CI, AutoDevOps, and Serverless will be covered at this first event for the GitLab Polska group in Wroclaw on June 12. Details and RSVP on <a href="https://www.meetup.com/GitLab-Polska/events/261826648/">Meetup</a>.</p><h4>GitLab ANZ — Sydney</h4><p>On June 25, the GitLab community will gather in Sydney to learn about Auto DevOps from the engineering manager who leads the Auto DevOps team. Details and RSVP on <a href="https://www.meetup.com/GitLabANZ/events/261819148/">Meetup</a>.</p><h4><strong>GitLab Meetup Jalandhar</strong></h4><p>Learn all about GitLab’s 12.0 Release with the GitLab community in Jalandhar on June 27. Details and RSVP on <a href="https://www.meetup.com/GitLab-Meetup-Jalandhar/events/261729281/?_xtd=gqFyqTE5MDM1NzA1M6Fwo3dlYg&amp;from=ref">Meetup</a>.</p><h4>Cloud Native and Kubernetes Minneapolis</h4><p>Learn about the architecture of the GitLab CI/CD system and the basic parts of a pipeline definition including a sample pipeline on June 27. Details and RSVP on <a href="https://www.meetup.com/Cloud-Native-Minneapolis/events/gtwkhqyzjbkc/">Meetup</a>.</p><h3>What’s next</h3><p>Are you ready to join a local community but don’t see an event near you? Take a look at the <a href="https://about.gitlab.com/community/meetups/">GitLab Meetups page</a> or reach out to <a href="https://twitter.com/john_cogs">me</a> to learn how GitLab can help you start a meetup in your area.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=274ae8aee6d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/gitlab-meetups-june-2019-274ae8aee6d0">GitLab Meetups: June 2019</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Following the GitLab model: How to build a profitable, open core, remote-working startup]]></title>
            <link>https://medium.com/gitlab-magazine/following-the-gitlab-model-how-to-build-a-profitable-open-core-remote-working-startup-1f313423d1d3?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f313423d1d3</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[David Beesley]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:30:02 GMT</pubDate>
            <atom:updated>2019-05-16T16:30:02.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eG2MFl0sGRKFmd_USgA_8Q.jpeg" /></figure><p>GitLab is similar to a lot of startups, born out of frustration with existing tools to founders who know the community they serve well. But, the similarities end there. GitLab does not occupy floors of office space in the usual tech hubs but rather has a completely remote workforce. GitLab CEO, <a href="https://about.gitlab.com/company/team/#sytses">Sid Sijbrandi</a>, told me how this decision was initially driven by the original makeup of the founding team who were spread over Europe, and has become ingrained in his company’s DNA. Talking to Sid, you can tell he’s proud of what he’s built and this shows by the effort GitLab has given to promote remote work in startups, something a lot of venture capitalists (VCs) will tell you is “not ideal.”</p><h3>Getting investors on board</h3><p>I asked Sid what the reaction was when he told investors they were a remote team. As I’ve experienced with my own startup, remote work is viewed as a negative which required justification to get investment. VCs, Sid explained, are focused on reducing risk; why invest in a startup which is following a different model to the one you are used to and know works? Recently, in a video chat with a potential investor my cofounder and I laid out our rationale for remote work. He responded that he felt everyone had to be in the same place to effectively communicate. I asked if we were not all effectively communicating in our chat this very second. Times are changing as investors realize talent is global, but long-held views die hard.</p><h3>Deciding on an open core business model</h3><p>GitLab’s unique approach extends beyond remote work; it has secured investment from some of the best VCs in the world with what it terms an <a href="https://about.gitlab.com/2018/11/09/monetizing-and-being-open-source/">‘open core’ business model</a>. This is a smart compromise between being completely open source and holding back enough features that enterprises and startups will pay you enough to keep the internet connection flowing in GitLab’s 500 employees’ home offices (GitLab pays for its employees’ internet). The open source model usually involves charging for support, but GitLab found this did not work for them. As they grew more stable and became more intuitive customers were seldom in need of support so they stopped paying. This is great from a product perspective but not an economic one.</p><p>So, here comes the million dollar question. How do you decide which features to charge for and which to give for free in your open core? While, at the same time, ensuring you get the benefits of working with the wider development community, who can contribute massively when properly engaged. GitLab’s answer is beautifully simple: look at who is asking for what and follow the budget. If a C-level exec asks for a feature, they probably need it to work across an entire organisation and will be willing to pay for productivity gains. A startup founder has a different set of requirements (and budget) for managing small teams efficiently, so maybe this goes in a middle tier. While a single developer only needs the open core free tier for hobby projects. Sid explained you can generate value for all these segments by separating out the feature and ensuring fair pricing.</p><h3>Hiring an all-remote team</h3><p>Once you’ve got a killer business model, an actively engaged community and you’ve raised enough money to build out your product, how do you hire a remote team? Well, it turns out it’s not much different to how most companies hire. Sid explained that potential hires are aware of how remote work operates and how, from an engineering standpoint, it makes relatively little difference where someone is working from as long as they stick to regular office hours. Perhaps remote work will eventually lead to a more diverse workforce and provide a better family-work balance. After all, forcing talented people to undertake ~3-hour daily commutes hardly shows how much you value them. Remote work may not be a magic bullet to automatically improve inclusion and diversity, but perhaps it’s a good starting point.</p><p>As our conversation drew to a close, it became clear why GitLab is the poster child for remote work and open core development. But what’s on the horizon? There is increasing disquiet about how cloud vendors have built business models around taking open source software and delivering it ‘as-a-service.’ The mood from investors seems to be to create more restrictive licenses which prevent this. GitLab is published under the open MIT license and Sid hopes they will never be forced to change this. I hope he is right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f313423d1d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/following-the-gitlab-model-how-to-build-a-profitable-open-core-remote-working-startup-1f313423d1d3">Following the GitLab model: How to build a profitable, open core, remote-working startup</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab Meetups: May 2019]]></title>
            <link>https://medium.com/gitlab-magazine/gitlab-meetups-may-2019-7713e946732?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/7713e946732</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[meetup]]></category>
            <dc:creator><![CDATA[John Coghlan]]></dc:creator>
            <pubDate>Wed, 01 May 2019 15:26:41 GMT</pubDate>
            <atom:updated>2019-05-02T13:41:01.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1b4_97h59bNJrTva_MaJvQ.jpeg" /><figcaption>Tokyo Women Who Code Meetup</figcaption></figure><h4>Here’s a list of all the irl places you can find the GitLab Community this month</h4><h4>Warri GitLab Meetup</h4><p>The first GitLab Meetup in Nigeria is coming up on May 18 in Warri. The event will feature talks from the local GitLab community, GitLab team members, and plenty of time for conversation. Details and RSVP on <a href="https://www.meetup.com/GitLab-Nigeria-Community/events/260843221/">Meetup</a>.</p><h4>Barcelona Free Software</h4><p>Heading to KubeCon + CloudNativeCon Europe? If you’re in Barcelona on May 20, join us for this meetup with the Barcelona Free Software community. Their will be talks on working in the open, Kubic, and more. Details and RSVP on <a href="https://www.meetup.com/Barcelona-Free-Software/events/260656266/">Meetup</a>.</p><h4>Bay Area GitLab Meetup</h4><p>Join us for the reboot of our Bay Area Meetup group on May 23 at Pure Storage in Mountain View. The Pure Storage team will share their story about deploying GitLab on Kubernetes. There will also be a GitLab + GKE demo. Details and RSVP on <a href="https://www.meetup.com/GitLab-Meetup-Group/events/260731202/">Meetup</a>.</p><h4>GitLab Meetup Hamburg</h4><p>The GitLab Meetup in Hamburg will be getting together for their second meetup on May 23. Details and RSVP on <a href="https://www.meetup.com/GitLab-Meetup-Hamburg/events/261099126/">Meetup</a>. Interested in giving a talk? I’m happy to introduce you to the organizer.</p><h3>What’s next</h3><p>Are you ready to join a local community but don’t see an event near you? Take a look at the <a href="https://about.gitlab.com/community/meetups/">GitLab Meetups page</a> or reach out to <a href="https://twitter.com/john_cogs">me</a> to learn how GitLab can help you start a meetup in your area.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7713e946732" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/gitlab-meetups-may-2019-7713e946732">GitLab Meetups: May 2019</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Acquisitions, growth curves, and IPO strategies: A day at Khosla Ventures]]></title>
            <link>https://medium.com/gitlab-magazine/acquisitions-growth-curves-and-ipo-strategies-a-day-at-khosla-ventures-2762eb02c83a?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/2762eb02c83a</guid>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Erica Lindberg]]></dc:creator>
            <pubDate>Tue, 09 Apr 2019 17:42:27 GMT</pubDate>
            <atom:updated>2019-04-09T17:42:27.108Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kfuun0zLk8Y_EUYawYGppQ.jpeg" /></figure><h4>A CEO Shadow’s take on GitLab’s annual investor meeting with Khosla Ventures.</h4><p>When I accepted the opportunity to participate in GitLab’s <a href="https://about.gitlab.com/handbook/ceo/shadow/">CEO Shadow program</a>, I knew exactly what to expect. In typical GitLab fashion, there was already a handbook page detailing the goal, the format, and the expectations of the program. Our co-founder and CEO, <a href="https://twitter.com/sytses">Sid Sijbrandij</a>, keeps his calendar <a href="https://about.gitlab.com/handbook/values/#public-by-default">public by default</a> to GitLab team members, so I was able to get a good understanding of the meetings I’d be attending, who’d be present, and what would be discussed. What I couldn’t have predicted is how an annual meeting between Sid and venture capitalist <a href="https://en.wikipedia.org/wiki/Vinod_Khosla">Vinod Khosla</a> would turn out.</p><h3>Skeptical about in-person meetings</h3><p>GitLab is an <a href="https://about.gitlab.com/company/culture/all-remote/">all-remote</a> company. We don’t have any offices, and we communicate and collaborate via Zoom, Slack, Google docs, and GitLab. To me, this is normal, and, as an introvert, my biggest concern with participating in the CEO program was the energy drain I knew I would experience living in downtown San Francisco for three weeks and meeting with people in person. Luckily, even our CEO conducts most of his business remotely.</p><p>However, many of our investors and board members are still, what I call, remote shy, and tend to default to in-person meetings. This is how I found myself traveling an hour and a half south to Menlo Park to meet with one of our investor groups, Khosla Ventures, for their annual meeting with Sid.</p><blockquote>“I’m not sure what we’re going to get out of this. Khosla is the only investor that can get me to travel an hour and a half to meet in person, every year, without an agenda.”</blockquote><p>Khosla Ventures (KV) is a venture capitalist firm founded by Vinod Khosla, co-founder of Sun Microsystems. KV and GitLab have a long history: They invested in our seed round, led our Series A, and has been a part of every fundraising round since. You could say Khosla Ventures is a big fan of GitLab, and the feeling is mutual.</p><p>“I’m not sure what we’re going to get out of this. Khosla is the only investor that can get me to travel an hour and a half to meet in person, every year, without an agenda,” Sid told me. While I sincerely appreciate Sid’s dedication to all-remote, to <a href="https://about.gitlab.com/handbook/values/#efficiency">efficiency</a>, and to keeping things simple, I found his sentiment surprising. To me, this was a big deal. We were going to spend the day with some of the industry’s brightest minds in Silicon Valley. However, I equally appreciated his emphasis on the lack of agenda. At GitLab, <a href="https://about.gitlab.com/handbook/communication/">we work asynchronously</a> and agendas allow people to prepare ahead of time so meetings can be interactive, discussion-oriented, and productive. A meeting without an agenda is unpredictable and can be a waste of time.</p><h3>Khosla Ventures</h3><p>Pulling up to Khosla Ventures in Menlo Park was a refreshing change of scenery from downtown San Francisco where I’d been staying. The mid-century modern style building is tucked behind lush greenery, and as soon as you enter you are unexpectedly greeted by quirky grape purple walls. Inside Khosla Ventures feels more like a creative incubator than an investor firm.</p><p>We first met with Bruce Armstrong, operating partner at Khosla Ventures and a GitLab board member. Top of mind for everyone was the board. With our plans to go public, we needed to hire new board members with public company experience. Earlier that week, I had the opportunity to sit in on a few conversations with potential board members and now I was getting the chance to hear how they were evaluating the candidates. Across the candidates, a pattern was emerging: They all had experience firing CEOs. For some CEOs this would be worrisome. For Sid, it appeared to be a point of pride: He wanted to hire the best people that were going to make the best decisions for the company in the long run. Period.</p><h3>The brainstorm</h3><p>Next we met with Vinod, Bruce, and investment partners Brian Byun and Sven Strohband for a company brief and brainstorm session. Sid began with an update on the financials, and detailed our massive growth and expansion both in terms of people and product. There were no slides presented. Instead, Sid used our website as a visual aid. Nearly every question or discussion point was first addressed with a Google search to pull up the appropriate GitLab web page to reference. When discussing the progress of the product, he defaulted to our <a href="https://about.gitlab.com/">homepage</a>, where our product team has meticulously detailed our current and future feature set. During a discussion about competitors and potential partners, our <a href="https://about.gitlab.com/devops-tools/">DevOps tools page</a> was referenced for a single page view of all our competitors in context of exactly how we compete.</p><p>I’ve been working at GitLab for two and a half years as a content writer on our marketing team and at times have been extremely frustrated with our marketing website — the content on it, how it’s organized, what we’re presenting, etc. It doesn’t look or operate in a way I’m familiar with so my instinct was to not trust it. But nothing we do at GitLab is “normal,” and witnessing our CEO use the website as a single source of public truth to inform our investors is just one example of what it means to be a radically <a href="https://about.gitlab.com/handbook/values/#transparency">transparent company</a>. We don’t hide behind “marketing speak” on our public facing website or develop behind closed walls. We tell the same story and share the same information with the company, the customers, the community, and yes, even the investors.</p><p>While our website doesn’t have the same flashy graphics and pithy marketing copy I’m used to, it speaks the truth even when the truth makes people a little nervous about how we’re going to pull this off. We have an incredibly ambitious product roadmap to be built by an all remote team in a short amount of time.</p><blockquote>“I see what you’re trying to do, but realistically, which categories are you really able to compete in?” And, unfalteringly Sid answers: all of them.</blockquote><h4>Acquisition strategy</h4><p>Something I’ve found surprising throughout my entire CEO Shadow experience is how external people underestimate GitLab’s ability to deliver on ambitious plans. The conversation often defaults to, “I see what you’re trying to do, but <em>realistically</em>, which categories are you really able to compete in?” And, unfalteringly Sid answers: all of them. There are some awkward laughs, and the question is reframed to “What part of the product are most of your customers using today?” We move on.</p><p>The conversation with Vinod Khosla was similar but different in tone. Vinod and the rest of the team were skeptical of our ambition but perhaps more attuned to Sid’s commitment to the direction and vision and thus more willing to dig into how we get there instead of why we won’t.</p><p>Potential partnerships to help fill some of our missing functionality were discussed, but it was apparent that our plan was quickly encroaching into competitive territory among the leading contenders.</p><p>Instead, there’s an acquisition strategy. To achieve our goal to deliver a single application for the entire DevOps lifecycle that is best-of-breed in every category, we are going to need some help and make some acquisitions. We already acquired <a href="https://about.gitlab.com/2017/03/15/gitter-acquisition/">Gitter</a> and <a href="https://about.gitlab.com/2018/01/30/gemnasium-acquired-by-gitlab/">Gemnasium</a> in order to enter into the ChatOps and security space more quickly than if we tried to build it all from scratch.</p><p>Naturally, our acquisition strategy and offer was <a href="https://about.gitlab.com/handbook/alliances/acquisition-offer/">already drafted and public in our handbook</a>. This enabled the conversation to focus on thinking through potential companies and specific areas of our product where we may want to augment the productivity of our soon-to-be 500 internal developers with an acquisition.</p><h4>The IPO date</h4><p>GitLab <a href="https://about.gitlab.com/company/strategy/#sequence">plans to go public on November 18, 2020</a> and prefers to remain an independent company with no plans of being acquired. While Vinod made it clear it’s strange to pick and make public an IPO date, at GitLab, we are driven by results and deadlines and even an IPO is no exception to the rule. The route we chose to go — traditional or direct listing — was another topic.</p><p>Direct listings are historically uncommon. It wasn’t until <a href="https://techcrunch.com/2018/02/28/spotify-has-filed-to-go-public/">Spotify went public via a direct listing</a> in 2018 that there was even a precedent for tech companies. Now, Slack and potentially Airbnb are rumored to be next, officially <a href="https://www.bloomberg.com/opinion/articles/2019-01-11/direct-listings-are-a-thing-now">making direct listings <em>a thing</em></a>. As for GitLab, like everything else, it will come down to what’s right for us. I can report in good faith all options are being examined carefully and closely. The takeaway here is that while some might think it’s crazy of GitLab to set this ambitious goal, and Vinod might think it’s crazy to set a specific date, one thing is for sure: As a company, we’re ready and already thinking about what’s next.</p><blockquote>“Where is GitLab five years from now? This is where you are now, what comes next?”</blockquote><h4>Growth curves</h4><p>You know you’re at a successful company when the VCs aren’t focused on how you’re going to meet your short-term goals or current <a href="https://about.gitlab.com/direction/#vision">product vision</a> but are excited about the long-term vision.</p><p>“Where is GitLab five years from now?” Vinod asked the room, as he stood up and drew a chart with three staggered S curves on it. He pointed to the first one, “This is where you are now.” Pointing to the other two he asked, “what comes next?”</p><p>He explained how Square started as a payment device, then to a point-of-sale system, found success, and instead of stagnating, entered into a new market via their Square Capital and Cash App offerings. You see similar trajectory with Facebook entering into the devices space with their newest Portal system. What was it going to be for GitLab? It seemed like an outrageous question to ask considering we still have this huge vision to complete but, unsurprisingly, Sid had thought about this and some things are already in the making.</p><p><strong>Growth curve #1: Meltano</strong></p><p><a href="https://about.gitlab.com/2018/08/01/hey-data-teams-we-are-working-on-a-tool-just-for-you/">Meltano</a> (model, extract, load, transform, analyze, notebook, orchestrate) is a start-up within GitLab aimed at becoming a complete solution for data teams. Similar in concept to GitLab, the goal is to create a single application for the entire data science lifecycle. The mission is similar as well: Make analytics accessible to everyone. If successful, Meltano will begin to bridge the gap between systems and data and bring the GitLab vision of everyone can contribute to even more people.</p><p><strong>Growth curve #2: Product assisted digital transformation</strong></p><p>The next idea was a real show stopper: product assisted digital transformation. Think code review as a service but expanded to culture, infrastructure, management, pipelines, process, and integrated directly into the product instead of being an outside service. Imagine if you could bootstrap and up-level your engineering teams’ skills with a product that comes with engineering best practices and support out-of-the-box.</p><h3>Safe for another year</h3><p>As it turns out, agenda-less meetings at Khosla Ventures can provide a ton of value. We walked out of Khosla’s office with a healthy dose of validation and criticism, and our brains buzzing with new horizons of potential to explore. I was already convinced GitLab is a great company to work for, but my experience at Khosla opened my eyes to just how unique our opportunity is. And, the on-site, half day, agenda-less meeting is good for another year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2762eb02c83a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/acquisitions-growth-curves-and-ipo-strategies-a-day-at-khosla-ventures-2762eb02c83a">Acquisitions, growth curves, and IPO strategies: A day at Khosla Ventures</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring a remote employee in Canada: Lessons from our chat with GitLab CEO Sid Sijbrandij]]></title>
            <link>https://medium.com/gitlab-magazine/hiring-a-remote-employee-in-canada-lessons-from-our-chat-with-gitlab-ceo-sid-sijbrandij-e85517ee6123?source=rss----2d8b29d6db33---4</link>
            <guid isPermaLink="false">https://medium.com/p/e85517ee6123</guid>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Daniel Aisen]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 16:44:27 GMT</pubDate>
            <atom:updated>2019-03-29T16:44:27.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vo2d1vBQAbhmcsYq" /><figcaption>Photo by <a href="https://unsplash.com/@andrewtneel?utm_source=medium&amp;utm_medium=referral">Andrew Neel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Over the course of last month, my co-founder Allison and I spent a good deal of our time evaluating whether it would be possible to bring on a remote employee based in Canada to join our team at Proof Trading. For context, the two of us are based in New York and our company is a Delaware C-Corp.</p><p>We’re still in the early days of our operation, but GitLab’s distributed team model has been an inspiration to us. GitLab has team members in over 50 countries around the world, so if anyone could provide advice, we figured it would be them. One of the first places we looked in tackling this challenge was their <a href="https://about.gitlab.com/handbook/">Employee Handbook</a>, which is densely packed with helpful information.</p><p>Of note, we found these pages extremely useful as they detail GitLab’s approach to bringing on remote team members:</p><ul><li><a href="https://about.gitlab.com/handbook/contracts/#canada">Hiring Process in Canada</a></li><li><a href="https://about.gitlab.com/company/culture/all-remote/">All Remote</a></li></ul><p>It turns out GitLab hires remote employees through a variety of different mechanisms around the world. Sometimes they set up a local subsidiary, sometimes they use a local staffing agency, and other times they hire the individual as an independent contractor. In Canada specifically, they use a staffing agency called CXC Global. We were curious to learn how they made this decision, so we reached out through a mutual contact to see if someone at GitLab could provide more insight. To our surprise and delight, their <a href="https://about.gitlab.com/handbook/ea/#pick-your-brain-meetings">CEO Sid Sijbrandij offered to have a video call with me to go through my questions</a>! As such, I decided to also take the opportunity to ask some additional questions about distributed teams in general. Here’s the recording of our call:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYr2do8A38r0&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYr2do8A38r0&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FYr2do8A38r0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad50532f67e0d16fd1d8854a1d300d2e/href">https://medium.com/media/ad50532f67e0d16fd1d8854a1d300d2e/href</a></iframe><p>Here were my questions and the takeaways from Sid’s responses:</p><p><strong>Logistics of hiring remote team members around the world</strong></p><p>Our old company did not particularly embrace remote work, but we want Proof to be extremely amenable to it. In particular, right now we’re exploring bringing on an employee based in Canada, and we’re bumping up again logistical questions like how to approach the employment arrangement. As such, we’d love to hear more from your perspective.</p><ul><li>What issues did you face bringing on team members all around the world, particularly in the early days?</li></ul><p>GitLab still faces logistical issues bringing on team members around the world, but as its got bigger, it now has the opportunity to incorporate in more countries and have a traditional employer relationship in those. In countries where that’s still hard, they sometimes hire a professional employment organization (PEO) to be the employer of record (EOR). In other cases, the team members are contractors. There’s no one-size-fits-all approach, and they continually monitor where there are high numbers of team members and which places are a nexus of business to determine when to incorporate in a new country.</p><ul><li>When hiring an employee in a new country, how did you choose between the various options for onboarding them? (e.g. creating a local subsidiary vs. using a staffing firm vs. independent contractor). In particular, why did you choose to use CXC Global in Canada?</li></ul><p>“We have a firm that advises us on which option to use. They take into account how many people we have there, how much business we do there, and the legal requirements in that country, and then they run a risk assessment.”</p><p>In the early days, they didn’t use an advisory firm for making these choices, but since they had so few people, incorporating locally was rarely the best option, so they would mainly hire individuals as contractors or through an EOR.</p><p>In Canada specifically, because GitLab does not have a large number of employees there and because CXC Global is a good PEO option, they chose to go down that route.</p><ul><li>Have you faced any complications related to issuing equity or options to team members in different countries?</li></ul><p>GitLab has run into remarkably few issues with issuing equity. They recently did an audit on the 40+ countries in which they’ve issued options, and there were basically no issues. The one country that does pose more challenges is China.</p><ul><li>Is there any other advice you would offer to a new company trying to bring on remote international team members?</li></ul><p>Sid is extremely proud of the fact that they issue options to all their team members around the world. Most companies take the approach of only issuing options to employees in the U.S., but this runs the risk of unfairness in the case that the options become valuable. They are very glad they took the harder path of issuing options everywhere.</p><p><strong>Remote productivity</strong></p><p>We’ve just gone from a 100-person open floor plan, loud, constant interruption work environment to now starting a two-person, remote-friendly company, so all of this is very new to us.</p><ul><li>Could you describe your remote collaboration tools and which tools are preferred in different scenarios? (e.g. Issues, Email, Chat, Video Chat, Docs, etc.)</li></ul><p>“We use a lot of GitLab (issues, merge requests). We use Slack extensively, but it’s never the system of record, so if there’s a meaty issue we make an issue. We still have meetings but they’re much more focused. Every meeting has a Google Doc with an agenda and people put their questions in there during the meeting and they’re answered there as well.</p><p>“The solution to most issues is either an update to the code base or an update to the Employee Handbook which are the company processes. To figure out high-level things with a lot of back and forth, employees are encouraged to hop on a video call. Meetings, either regular meetings or one-offs, have this Google Doc attached.</p><p>“Every single meeting at GitLab is optional. People can judge their use of time, and if you don’t feel the meeting is useful to you, you can skip it. Or even once you join, if you find it’s not relevant, you’re encouraged to jump off.”</p><ul><li>Do you have a process for encouraging team members to try out new productivity tools and/or for introducing new tools company-wide?</li></ul><p>“We don’t have a process, but we do have a <a href="https://about.gitlab.com/handbook/tools-and-tips/">Tools and Tips</a> section in the handbook where people can see what others use and add their own. People at GitLab tend to be curious and try new things on their own. There are lots of additions to the Handbook every single day.”</p><ul><li>One of my biggest worries going from an intensely social and in-person work environment to a distributed team was loneliness — how does GitLab combat employee loneliness?</li></ul><p>“We do chit-chat — we call them Coffee Chats. There doesn’t need to be an agenda, and you don’t need to talk about work, and they’re encouraged. When a new person joins, we ask them to do 10 Coffee Chats to get them used to the idea.</p><p>“We also encourage people to meet up in real life. There’s a travel budget, and we pay for employees to travel to meet up with each other or to organize local meetups. I have a house back in the Netherlands and team members are welcome to stay there too. Every 9 months, we fly everyone together into one location for a company-wide retreat, most recently in Cape Town. It’s very important to interact with other people — I’m perfectly comfortable doing that remotely, but some team members choose to work from a co-working space to be around others (not necessarily co-workers), and we pay for that as well.”</p><p>The call with Sid gave us a great deal of confidence that we could hire the employee and that using a staffing firm was an excellent approach. Afterwards, I reached out to CXC Global, the EOR that GitLab uses, but for our particular use case CXC actually recommended we use a different firm: Globalization Partners. CXC is primarily a contractor staffing firm, whereas Globalization Partners is a more full-service PEO firm. Since we were hoping to bring on the individual as an employee with benefits, Globalization Partners seemed to be a perfect option for what we wanted to do.</p><p>We’re thrilled to report that we were able to <a href="https://medium.com/prooftrading/hiring-a-remote-employee-in-canada-1f9dd02e91c4">onboard the employee</a> on March 1st, and everything has gone off without a hitch. A huge thank you to Sid and GitLab for being such a wonderful resource!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e85517ee6123" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitlab-magazine/hiring-a-remote-employee-in-canada-lessons-from-our-chat-with-gitlab-ceo-sid-sijbrandij-e85517ee6123">Hiring a remote employee in Canada: Lessons from our chat with GitLab CEO Sid Sijbrandij</a> was originally published in <a href="https://medium.com/gitlab-magazine">GitLab Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>