How to make an internal conference worth our time
summary
Equinor’s internal developer conference grows from community drive from below, plus managerial backing and iterative improvements, and proves it by filling public tickets in 1 minute 4 seconds and getting ~200 sign-ups in the first hour. Organizers run a GitHub repo and Slack for proposals as issues and pull requests with automation, run two workshop days and two conference days (about 12–14 workshop tracks and five conference tracks), use one-hour slots with 15-minute gaps, avoid blanket recordings, and report higher retention and active contributor rates (~one third or more).
AI-written summary · about
chapters (7)
- 0:00Internal conferences intro
- 1:26Three pillars for success
- 3:15Community-driven approach
- 5:26Implementation tips
- 7:11Management commitment
- 9:18Regularity and feedback
- 11:48Iterative improvement
related talks
46mYour developer’s intelligence isn’t artificial
11mLightning Talk: Building a Community Inside your Company
16mOpening remarks
15mGrowing at Work with Community-oriented Development
47mRooting Community Culture in Organizations — Promoters and Successors on the Value of Community and Paths to Sustainability
32mBuild a Better PyCon My Annual Reflection
33mIntroduction
24mHybrid Conferences made by Small Teams