How to measure developer love and reach with the orbit model
summary
Shows a concrete system called the Orbit model that turns community activity into numbers: define activities, score them 1–10, and calculate love by max activity in a recent window (example: six months) so ambassadors, fans, users and observers fall into Orbits. Reach is a scored sum of signals like Twitter/GitHub followers, blog traffic, title and company size and the talk demos Airtable templates and Zapier flows used to record activity, send swag, and produce region and ROI reports, with Orbit as an early access product.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 4:28What is the Orbit model
- 5:52Model overview and objectives
- 10:14Measuring love in communities
- 19:45Q&A on love and tracking
- 22:04Measuring reach in communities
- 28:12Q&A on love vs engagement
- 30:22Rewarding community activities
- 34:12Q&A on multi-project communities
- 37:45Q&A on co-founder transition
- 40:22Q&A on identity resolution
related talks
29mThe Value of Community Building. And why you Should Invest in Building One
01h 23mIs there such a thing as Community ROI (and what is it)
45mHacking Communities: ROI of Belonging
45mHacking Communities: ROI of Belonging
50mTurning Users Into Advocates, at Scale
43mPanel Discussion: Marketing is Essential (and Not Sleazy) for Open Source Projects
25mStorytelling with Data
10mOpenDevRel: Tales of Developer Relations in Open Source