How we designed an inclusivity-first conference on a shoestring budget and short timeline
summary
North Bay Python builds an inclusivity‑first conference from scratch in under six months on a shoestring budget, proving specific choices matter: a downtown no-catering venue to convert per‑person costs into fixed costs, an anonymized first‑round review plus curated reattachment to hit representation targets, and paid consulting plus accessibility spending (live captioning, travel assistance) funded largely by sponsorship so tickets stay affordable. Expect concrete budgets ($20k minimum viable, ~$61k revenue) and surprising timing (25% register in final 48 hours).
AI-written summary · about
chapters (14)
- 0:00Start
- 3:44How do you build an inclusive community?
- 5:33Conversion Funnel
- 6:15Start with your team. Shore up what's missing.
- 7:02Recruit advisors and advocates.
- 7:26Prioritize your outreach. Seriously.
- 10:52Hire a professional.
- 11:43Build an inclusive team. Prioritize difficult outreach Communicate with care.
- 14:31Code of Conduct Expected audience Financial aid
- 16:46Review panel
- 17:14Anonymized review
- 21:20Conferences cost money
- 21:51Cost is an inclusivity issue.
- 28:18Live Captioning Travel Assistance Lunch Guides
related talks
23mThe Labors of Inclusivity
45mInclusion and Community in the face of crisis
36mDiversity and Inclusion Panel: The Work Still Matters: Inclusion, Access, and Community in 2025
35mHow to Build a Magical Living Room
31mHow to amplify diversity inside a Python community?
34mDiversity and Inclusion Panel
42mPractical Strategies for Centering DEI in Your Open Source Event
30mOrganizing conferences for learners: How we made it work in Namibia