Crayons, Glue, and Stickers
summary
A concrete playbook emerges: pick a daily-relevant GitLab seed, host a public Slack forum that supports threading and notifications, and write self-service docs so teams can teach to fish. The payoff is measurable: more subject-matter experts, fewer single points of failure, and mean time to resolve drops as crowd-sourced support answers routine ops questions. Outcomes also include skinnier central teams, an internal open source flow of reusable tools, and scalable leadership practice.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:52Problem Space
- 3:00Communication
- 6:26Building a Community
- 9:16Building a Platform
- 12:22Guiding Principles
- 16:27Keep it Public
- 20:07Be Engaging
- 23:17Outcomes
- 30:13Questions
related talks
20mJourney Of Devops Teams in a Corporate Environment
21mDriving Cultural Change to Improve Software Development and CI/CD
25mLightning Talks Part 2
37mCollaborative Development: The Only CD That Matters
29mScaling Across the Enterprise
54mFrom Code to Customer
48mLightning Talks
25mHow we create and leverage Data Services in GitLab.com