How-To: Build a local Python community
summary
Concrete claims and actionable steps: started with two people and found 30 then 150 shows small beginnings scale; a first conference can fail if it’s too big (forgot invoices) so start tiny from meetups not a full conference. One committed organizer is sufficient, aim to make that role replaceable, use partners for venues and sponsors for coffee, no budget needed — meet in pubs libraries or parks, consider a nonprofit once money flows, adopt a code of conduct, and PSF reimburses meetup.com.
AI-written summary · about
chapters (20)
- 0:00Building a Python Community How To
- 0:35Why build a community? How to manage expectations when setting it up? What resources do you need? How do you grow the community?
- 2:24A hard question.
- 4:08Why do I do this?
- 5:04No matter what reason, go for it
- 5:16Managing the expectations
- 6:01There is someone else.
- 6:29Don't over-commit
- 7:47People & Resources
- 8:38Other organisers
- 10:27Speakers, trainers etc.
- 10:57Two currencies: Time & Money
- 13:24Partners / Sponsors
- 14:29How to tell people about the community?
- 14:51Existing usergroups
- 15:55Internal mailing lists of companies
- 17:35Do you want to?
- 18:11You need other people
- 19:08Don't be afraid to reach out to experienced people.
- 19:48Be proud of yourself 3
related talks
25m"How (Not) to Start a Python User Group"
30mSetting Up Your Python Community for Success: Lessons from the Melbourne Python User Group
46mCommunity BOF
07mCreate and Attend Meetups
56mFounding C++ User Groups
29m"Scaling a Rust Community: Lessons from the Frontlines"
29mHow To Run A Successful Local User Group
36mHandcrafting Community