So you want a PGDay in your city
summary
Organizing a PGDay requires an advocate from PGUS to get approval, a secured budget (expect weeks of back-and-forth), and about six months minimum of elapsed planning time; a one-track vs two-track decision changes venue, AV and recording costs, and sponsorship needs; recruit many helpers—never too many volunteers—and assign clear roles so CFP, ops and sponsor teams don’t overlap; use a venue with good transit and reliable catering, list nearby hotels for speakers, and watch Convene’s three-day shipping window for merchandise.
AI-written summary · about
chapters (19)
- 0:00Introduction and motivations
- 4:04Getting started
- 9:07Planning checklist
- 11:09Finding volunteers
- 13:35Resources for organizers
- 15:03Strategic planning lessons
- 17:46Budget and cost management
- 20:03Venue selection and logistics
- 24:04Catering and attendee comfort
- 25:04Role definition
- 26:15Talk selection and timing
- 28:14Structural organization
- 30:58Volunteer management
- 33:21Consensus and communication
- 35:07Managing stakeholder expectations
- 36:15Execution and promotion
- 39:28Handling day-of surprises
- 42:05Gratitude and closing
- 44:27Final call to action
related talks
46mRunning a Community Conference
01h 04mGrowing the PostgreSQL Community...
01mClosing Remarks
15mWelcome to just product 2023
27mSetting max_connection: Building PostgreSQL user groups that bring people together
06mopening talk (Day 3)
28mHow to Conference A User Guide
10mWhy Your Community Needs a Python Pizza Event