Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Everything Open (and Remote)

Everything Open (and Remote)

At GitLab we work completely in the open and all from the comfort of our homes. In this talk, I discuss how and what we opened and how we benefitted from that.

Find me on Twitter @jobvo

Presented at Continuous Lifecycle London on May 3rd, 2016.

Job van der Voort

May 03, 2016


  1. Open Job van der Voort - @jobvo

  2. Open core

  3. None
  4. None
  5. > 150,000 organisa)ons 1000 contributors

  6. ~80 employees

  7. Opened (almost) everything

  8. The secret?

  9. None
  10. Website about.gitlab.com

  11. GitLab's repos gitlab.com/gitlab-org gitlab.com/gitlab-com

  12. A concrete example From support to fix

  13. From support to fix Zendesk => GitLab.com

  14. From support to fix - zendesk issue: <link> A big

    consumer electronics company reports that when pressing a button, things break.
  15. From support to fix

  16. From support to fix Fix is scheduled for a release*

    A developer picks up the issue Logs status and links merge request The fix is merged by a merge request endboss (can be outside of GitLab Inc)
  17. o"en, a fix is contributed before we can start to

    work on it
  18. Feature Requests

  19. Feature Requests Issues on the same open issue tracker on

  20. Feature Requests Everyone can vote, comment and contribute

  21. Feature Requests

  22. Everything in the same place No hidden informa-on

  23. A community truly works together on building be5er so6ware when

    it's open Customers, single developers, open source users, our employees all have the same goal
  24. How to be produc-ve as an open company


  26. None
  27. None
  28. None
  29. Work asynchronously

  30. write everything down

  31. + have a single source of truth

  32. Discuss something important in Slack? Create an issue.

  33. Confused about something? Figure it out and document it.

  34. Create an open handbook about.gitlab.com/handbook

  35. None
  36. Open source

  37. By wri'ng everything down and making it open, everyone had

    the same tools
  38. Working asynchronously enabled collabora3on within the community

  39. Community members started to contribute to the handbook

  40. None
  41. Open Direc*on about.gitlab.com/direc0on

  42. Open Culture about.gitlab.com/culture

  43. Open Strategy about.gitlab.com/strategy

  44. Open Opera(ons gitlab.com/gitlab-com/opera0ons

  45. Open Marke*ng gitlab.com/gitlab-com/marke0ng

  46. Open Team about.gitlab.com/team

  47. Open People Ops (HR) gitlab.com/gitlab-com/peopleops

  48. How to work in the open 1. Work async

  49. How to work in the open 1. Work async 2.

    Open everything
  50. 3. Give everyone the same tools

  51. By opening up everything, including all resources our developers are

    using, everyone essen5ally has the same tools
  52. Except for CI

  53. No one wants to wait for CI builds to complete

  54. 1. Built Autoscaling CI higher demand? More Runners up within

    a minute or less
  55. 2. Free CI for everyone (On GitLab.com or your own

  56. Gitlab developers have no leg-up on community contribu7ons

  57. Why?

  58. We are part of a larger community

  59. Millions of GitLab users all over the world

  60. Major features, fixes built by the community

  61. Brings great people together

  62. None
  63. Collaborate Be open

  64. Ques%ons? find me @jobvo