Connecting Community/DevRel Teams to Other Teams
summary
Argues that DevRel succeeds on concrete processes not platitudes: use Trello→Slack integration so every card moved to Done posts to a public channel and engagement rises within days; require request templates and a stakeholder budget scoring system in GitLab issues to force prioritization; treat cross-team help as mentoring not doing so teammates learn to own tasks; publish a weekly curated feedback report that aggregates multi-channel bugs and feature asks into prioritized items for Product.
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
29mLightning Talk: OpenDevRel: Tales of Developer Relations in Open Source
05mIgnite: Learning to Share
24mBuilding a Foundation for Open Collaboration
40mPanel Discussion: Build a Community, Not a Framework
24mHow To Contribute to a Project without Coding
21mLeading and Growing an Open Source Comunity
17mScaling Community, Code, Contributors
19mLet's Talk Community - How to Grow, Nurture, Engage, & Measure