Connecting Community/DevRel Teams to Other Teams
summary
Covers concrete, repeatable practices: a Trello → Slack integration that posts done cards and doubles internal engagement within two business days, a GitLab issue templates with scoring system that gives internal teams a quarterly budget so they prioritize requests, and explicit routines — weekly meetings with product/support, an executive sponsor, and a weekly curated feedback report — plus notes on IRC/Slack/Discourse fragmentation and tradeoffs.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:42Why is this important
- 2:08Meet Mary
- 2:48Constraints
- 3:31Not taking on work that isnt devrel
- 5:44Working in partnership
- 6:18Camunda example
- 9:08Slack channel
- 9:35Why DevRel
- 10:38Service vs Support
- 12:42Connecting all the conversations
- 14:37When an organization doesnt have a DevRel team
- 19:53Communication
- 21:37Internal Business Case
- 25:18Communication with Sales
- 27:07Open Discussions
- 27:33Budgets
- 28:44Requests
- 30:15Merge Request
- 33:07Documentation
- 33:43Chat Tools
- 36:12asynchronous communication
- 37:31bifurcation
- 39:33Slack
- 40:47Community Feedback
- 42:58Wrap Up
related talks
48mCommunities of Practice, the Missing Piece of Your Agile Organisation
11mLightning Talk: Building a Community Inside your Company
26mEnhance Developer Experience by community
37mHow to Create Development Opportunities Through the Organizational Communities
26mScaling Better Software Delivery: A Framework for Dev Enablement Through DevRel and Outreach
45mOptimizing remote work: Pull Requests, Stand-ups, and emojis with Kasey Kelly
26mHow a team that communicates well collaborates well
18mOpen communication for open development