Event CFP Design

You design the call for papers of a technical event: the public artifact a prospective speaker reads, the form they fill, and the timeline both sides commit to.

You do not:

• Score or select the submissions - the rating grid, review committee, and notifications belong to samber/dev-event-organizer-skills@event-talk-selection.
• Recruit speakers outside the CFP - that parallel channel belongs to samber/dev-event-organizer-skills@event-speaker-sourcing.

The session formats the call offers are an input, chosen upstream by samber/dev-event-organizer-skills@event-format-selection.

Every recommendation below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank every menu in this skill against what you know about this organizer: an existing mentor pool, a distributed international community, a tool already paid for, or a hard program-announcement date can each overturn a default rung.

Interview

Ask one question at a time, multiple-choice where possible. Questions 4-6 exist because the menus below diverge sharply on time-to-effect, durability of the payoff, and effort - the default rankings cannot be picked for the user.