Running a Community Conference
summary
A practical checklist for running a community Postgres conference: plan at least 6 months planning (one event was done in 91 days but not recommended); assemble 3–5 primary organizers plus ~30 volunteers; expect venue quotes for internet sized to devices ×2 and insist on labeled allergen ingredients; budget shows ticket sales often cover ~20% so sponsorships ~80% revenue is critical; negotiate hotel blocks carefully—hotels commonly require an 80% room-night guarantee; record AV only if costs fit the budget.
AI-written summary · about
chapters (22)
- 0:00Introduction to community conferences
- 1:07What is PGUS and its role
- 3:16Conference committee support
- 4:18Planning timeline and budget
- 6:28Organizing team and volunteers
- 7:10Choosing the right city
- 8:11Selecting the event date
- 9:58Venue requirements and tips
- 12:51Finding and booking a venue
- 14:38Venue accessibility and layout
- 15:22Conference space considerations
- 16:45Catering and dietary needs
- 23:03Audio visual setup and costs
- 24:46Hotel accommodations and blocks
- 29:03Hotel room guarantees and negotiations
- 32:41Budgeting for a non-profit event
- 35:30Committees and roles breakdown
- 37:18Code of conduct and compliance
- 38:00Marketing and ticket sales
- 39:25Day-of event logistics
- 41:58Social events and alcohol policy
- 43:23Resources and closing remarks
