BEER: Not Just for Your Devs
summary
Look for concrete answers: what budget and time commitments exist, whether a paid organizer or volunteers run it and who does the outreach and who gets paid, exact logistics offered (space, projector, chairs, snacks) and how many attendees and repeat rate; ask for measures of inclusion (percent diverse speakers last 12 months) and tracking (GitHub‑style portal or spreadsheets recording impact); watch for examples where company support scaled a chapter, reduced volunteer burnout, or paid staff actually improved sustainability.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:25Who benefits
- 2:51Enabling community growth
- 4:15Personal journey
- 5:43Key questions
- 8:15Healthy partnerships
- 10:20Diversity and inclusion
- 12:47Logistical support
- 14:33Long-term strategies
- 17:47Employee participation
- 20:16Benefits of community work
- 23:12Balancing involvement
- 24:36Closing thoughts
related talks
07mInterviews with sponsors
32mBen and Shane's Fireside Chat
26mOh no Your project became really popular
47mRooting Community Culture in Organizations — Promoters and Successors on the Value of Community and Paths to Sustainability
01h 04mThe Minimum Viable Conference
32mBuild a Better PyCon My Annual Reflection
39mScaling an Open Source Sponsorship Program
46mRunning a Community Conference