User Tools

Site Tools


This is an old revision of the document!

The Perfect PerlCon

What would make for a perfect PerlCon?

(Inspired by a mail by PTS organizer Neil Bowers)

Before the event

  • Announce the dates and location at the previous conference, i.e. a year in advanced
  • Website up and running as early as possible (together with announcement?)
  • Weekly or at least monthly updates posted to website / blog / social media
  • Code of Conduct available

General Layout

  • Three days of talks in three tracks
  • One block of lightning talks per day
  • One keynote, maybe more (at most one per day).
  • Not the same old keynote people again and again.
  • A social evening event for all attendees
  • Place for BOFs during the event
  • Paid training sessions before/after the event
  • Hackathon before/after the event

Call for Papers

  • CfP published as soon as possible
  • Accept talks as the come in (eg accept one talk per speaker immediatly, if a speaker submits multiple talks pick the other ones later)
  • Have at least half the schedule filled at least 4 months before the start of the conference


  • Not in school holidays
  • Start at ~9:30, end at ~17:30
  • 2 coffee breaks, 1 lunch break
  • cluster similar talks into tracks
  • don't overlap talks with similar topics
  • ..


theperfectperlcon.1557823594.txt.gz · Last modified: 2019/05/14 08:46 by neilb