developer-meetup-program

Start by writing a one-page charter naming the audience, host model, one primary outcome, format, and rhythm before booking anything. Then pick a repeatable format such as anchor talk plus lightning slots, fix a recurring slot like second Tuesday at 19:00, and plan three editions deep.

Replace monthly open calls with a standing call for proposals linked from every event page, harvest speakers from regional conferences, trade speakers with neighboring groups, and grow lightning speakers into full talks. Keep a visible pipeline board with confirmed, provisional, and prospect speakers two editions ahead.

Plan on roughly 30% no-shows, the figure published by CNCF Community Groups; the often-repeated 40-50% figure has no named organization behind it. After three editions, replace any benchmark with your own trailing median door count, and overbook with an auto-promoting waitlist.

No. DevOpsDays states that no speaker spots can be bought by sponsors and that attendee contact information is never distributed. Sponsors get recognition, a thank-you from the stage, at most 15 minutes of stage time per CNCF guidance, and opt-in badge scans only.

CNCF's ideal cadence is monthly, with more than 90 days between events marking a chapter inactive and at least six meetings per calendar year required. Do not commit to monthly without the organizers and speaker pipeline to hold it, since a missed edition costs more trust than a slower cadence.

Avoid monthly hands-on workshops unless organizers have substantial preparation time, since a week of prep per edition breaks the cadence. Open space only works for rooms that already know each other, so delete it for first editions and new groups.