Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
EVERYTHING OPEN
JOB VAN DER VOORT
VP OF PRODUCT AT GITLAB
@JOBVO
History of GitLab
2011: OPEN SOURCESTARTED BY DMITRIY, WHO DIDN'T HAVE
RUNNING WATER
2013: GITLAB.COMFOUNDED BY SYTSE
(ALREADY HAD RUNNING WATER)
I want to work on GitLab full time
— Dmitriy, still without running water
2014: FOUNDING OF GITLAB BV
5 ENGINEERS, 1 SALES
2015
Y COMBINATOR
SEED + A ROUNDKHOSLA VENTURES; ASHTON KUTCHER;
MICHAEL DELL
> 150,000 ORGANISATIONS
1000 CONTRIBUTORS
~50 EMPLOYEES
PAYING CUSTOMERS
NASA, IBM, SPACEX, AIRBNB,
SONY, ESA, CERN, ALIBABA
OPEN GITLAB
OPEN CORE
COMMUNITY OF HUNDREDS OF
DEVELOPERS WORKS ON
COMMUNITY EDITION
ENTERPRISE EDITION IS FOR
ENTERPRISES
GITLAB INC WORKS ON BOTH
ALL IS GOOD
Dmitriy still doesn't have running water
however
WE REALIZED THAT
EVERYONE STARTS BY USING
THE COMMUNITY EDITION
IT IS NOT ORGANIZATIONS
THAT BECOME OUR
CUSTOMERS
IT'S THE COMMUNITY
what we did
OPENED
EVERYTHING
SUPPORT, DEVELOPMENT, OPERATIONS,
ORGANIZATION, DIRECTION, STRATEGY,
PLANNING
From support to fix
From support to fix
ZENDESK -> GITLAB.COM
From support to fix
- zendesk issue: <link>
A big consumer electronics company reports
that when pressing a button, things ...
From support to fix
From support to fix
Fix is scheduled for a release*
A developer picks up the issue
Logs status and links merge request
The ...
OFTEN, A FIX IS CONTRIBUTED BEFORE WE
CAN START TO WORK ON IT
Feature Requests
Feature Requests
ISSUES ON THE SAME OPEN ISSUE TRACKER
ON GITLAB.COM
Feature Requests
EVERYONE CAN VOTE, COMMENT AND
CONTRIBUTE
Feature Requests
Feature Requests
Feature is scheduled for a release*
A developer works on the feature
Logs status and links merge request
...
Everyone a part of the community
— Employees, customers, hobbyists, organizations
EVERYONE HAS THE SAME
TOOLS
REMOTE-FIRST
How to build a product
from thousands of voices
SCHEDULE ISSUES FOR A RELEASE
E.G. NOTIFICATION CENTER IN 8.5
RELEASE EVERY MONTH ON THE 22ND
SINCE SEPTEMBER 2011
BUILD ITERATIVELYIMPLEMENT THE MINIMALLY VIABLE
FEATURE AND ITERATE BASED ON FEEDBACK
LISTENTHE THOUSANDS OF VOICES HAVE
THOUSANDS OF COOL IDEAS. USE THEM.
PLAN
ABOUT.GITLAB.COM/DIRECTION
How to collaborate within
a community
FOR ALL COOL STUFF
[ ACCEPTING MERGE REQUESTS ]
TO MAKE THE BARRIER OF ENTRY LOW
[ UP-FOR-GRABS ]
What is hard?
SAYING NO
Other things open
OPEN ORGANIZATION
ABOUT.GITLAB.COM/HANDBOOK
OPEN CULTUREABOUT.GITLAB.COM/CULTURE
OPEN STRATEGYABOUT.GITLAB.COM/STRATEGY
OPEN OPERATIONSGITLAB.COM/GITLAB-COM/OPERATIONS
COLLABORATE
BE OPEN
QUESTIONS?@JOBVO
Everything Open
Everything Open
Upcoming SlideShare
Loading in …5
×

Everything Open

185 views

Published on

GitLab works fully in the open. This is how we do it.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Everything Open

  1. 1. EVERYTHING OPEN
  2. 2. JOB VAN DER VOORT VP OF PRODUCT AT GITLAB @JOBVO
  3. 3. History of GitLab
  4. 4. 2011: OPEN SOURCESTARTED BY DMITRIY, WHO DIDN'T HAVE RUNNING WATER
  5. 5. 2013: GITLAB.COMFOUNDED BY SYTSE (ALREADY HAD RUNNING WATER)
  6. 6. I want to work on GitLab full time — Dmitriy, still without running water
  7. 7. 2014: FOUNDING OF GITLAB BV 5 ENGINEERS, 1 SALES
  8. 8. 2015 Y COMBINATOR
  9. 9. SEED + A ROUNDKHOSLA VENTURES; ASHTON KUTCHER; MICHAEL DELL
  10. 10. > 150,000 ORGANISATIONS 1000 CONTRIBUTORS
  11. 11. ~50 EMPLOYEES
  12. 12. PAYING CUSTOMERS NASA, IBM, SPACEX, AIRBNB, SONY, ESA, CERN, ALIBABA
  13. 13. OPEN GITLAB
  14. 14. OPEN CORE
  15. 15. COMMUNITY OF HUNDREDS OF DEVELOPERS WORKS ON COMMUNITY EDITION
  16. 16. ENTERPRISE EDITION IS FOR ENTERPRISES
  17. 17. GITLAB INC WORKS ON BOTH ALL IS GOOD Dmitriy still doesn't have running water
  18. 18. however
  19. 19. WE REALIZED THAT EVERYONE STARTS BY USING THE COMMUNITY EDITION
  20. 20. IT IS NOT ORGANIZATIONS THAT BECOME OUR CUSTOMERS
  21. 21. IT'S THE COMMUNITY
  22. 22. what we did
  23. 23. OPENED EVERYTHING
  24. 24. SUPPORT, DEVELOPMENT, OPERATIONS, ORGANIZATION, DIRECTION, STRATEGY, PLANNING
  25. 25. From support to fix
  26. 26. From support to fix ZENDESK -> GITLAB.COM
  27. 27. From support to fix - zendesk issue: <link> A big consumer electronics company reports that when pressing a button, things break.
  28. 28. From support to fix
  29. 29. 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 senior developer (can be outside of GitLab Inc)
  30. 30. OFTEN, A FIX IS CONTRIBUTED BEFORE WE CAN START TO WORK ON IT
  31. 31. Feature Requests
  32. 32. Feature Requests ISSUES ON THE SAME OPEN ISSUE TRACKER ON GITLAB.COM
  33. 33. Feature Requests EVERYONE CAN VOTE, COMMENT AND CONTRIBUTE
  34. 34. Feature Requests
  35. 35. Feature Requests Feature is scheduled for a release* A developer works on the feature Logs status and links merge request The feature is merged
  36. 36. Everyone a part of the community — Employees, customers, hobbyists, organizations
  37. 37. EVERYONE HAS THE SAME TOOLS
  38. 38. REMOTE-FIRST
  39. 39. How to build a product from thousands of voices
  40. 40. SCHEDULE ISSUES FOR A RELEASE E.G. NOTIFICATION CENTER IN 8.5
  41. 41. RELEASE EVERY MONTH ON THE 22ND SINCE SEPTEMBER 2011
  42. 42. BUILD ITERATIVELYIMPLEMENT THE MINIMALLY VIABLE FEATURE AND ITERATE BASED ON FEEDBACK
  43. 43. LISTENTHE THOUSANDS OF VOICES HAVE THOUSANDS OF COOL IDEAS. USE THEM.
  44. 44. PLAN ABOUT.GITLAB.COM/DIRECTION
  45. 45. How to collaborate within a community
  46. 46. FOR ALL COOL STUFF [ ACCEPTING MERGE REQUESTS ]
  47. 47. TO MAKE THE BARRIER OF ENTRY LOW [ UP-FOR-GRABS ]
  48. 48. What is hard?
  49. 49. SAYING NO
  50. 50. Other things open
  51. 51. OPEN ORGANIZATION ABOUT.GITLAB.COM/HANDBOOK
  52. 52. OPEN CULTUREABOUT.GITLAB.COM/CULTURE
  53. 53. OPEN STRATEGYABOUT.GITLAB.COM/STRATEGY
  54. 54. OPEN OPERATIONSGITLAB.COM/GITLAB-COM/OPERATIONS
  55. 55. COLLABORATE BE OPEN
  56. 56. QUESTIONS?@JOBVO

×