Skip to content

2015 Registration Planning

Nathen Harvey edited this page Dec 21, 2015 · 1 revision

Also see Registration

#Rough Timeline

  • May 21: 50% of registration volunteers (pick registration captain)
  • May 28: Draft of registration day of timeline
  • June 2 (or so): registration volunteers call
  • June 2: Registration FAQ for volunteers; Volunteer assignments
  • June 2: Finalize registration day of timeline
  • June 9: Print out badges
  • June 11: Event

#Questions

  • tables and tablecloths - yes tablecloths
  • power and network
  • computer at table? - yes
  • Probably no printer - agreed, no printer
  • We think nice badges - yes
  • separate card with event information
  • swag bags? - no swag bags

#Tasks

  • Select registration provider.
    • Eventbrite
    • nvite
    • BusyConf
      • Also handles speaker and abstract management.
      • Nathan used this for ChefConf2013.
      • MoDev also uses this.
    • Jeff to get bench resources to [evaluate](Registration Provider Evaluation Factors).
    • Needs to be done and setup by 3/16.
    • DECISION (2/17): we're using BusyConf.
  • Meet w/ Excella MarComm to get playbook from DCBADD event.
  • Setup event in registration provider.
  • Create onsite registration procedures.
    • Use DODDC GitHub wiki.
    • Who could we ask to get a starting point?
      • Excella MarComm.
      • DevOpsDays organizers.
      • Jeff’s networking group (cadre) — they host a lot of awesome events.
      • Nathen Harvey — ChefConf 2013.
      • Pete Erickson - MoDev.
    • ACTION (2/17): Jeff will reach out to collect playbooks.
  • Identify onsite registration team.
    • ACTION (2/17): Greg will reach out to Mike DelNegro about onsite registration volunteers.

Ideas

  • Lottery tickets for prizes
    • Could be sponsorship opportunity
  • During registration, ask people about doing open talks
  • Little labels you can put on your badge to identify you (dev, ops, management, fed, speaker, sponsor, DevOpsDays veteran, *)
  • FAQ in advance (what to bring, food, logistics, building pictures)
  • Is there a theme for our registration?
  • Could we integrate Twilio?
  • Computing resources and services from sponsors
    • Pre-integrated DevOps environment

Questions

  • How do we handle USPTO registrations (30 tickets)?
  • How do we integrate registration into devopsdays.org website?
  • Could we handle sponsorship registrations through this, too?
  • How do we handle 25% .gov registrations (50 tickets)?
    • USPTO already has 30 tickets.
    • Would be nice if .gov block were handled by registration provider. Make this a use case in evaluation.
  • What are we handing out to attendees when they show up onsite?
    • Coordination with sponsors for swag.
  • What kind of badges? Sticky? Lanyard?
  • How do we prepare people for handling the unknown?

Other Stuff

  • Setting up registration station onsite the day before.
    • Tables, chairs, power, wifi.
    • Registration equipment.
    • Attendee materials.
  • Badge printing and holders.
    • How do we handle this onsite for changes?
      • Re-printing.
      • “Here’s your pen."
      • “I guess your name is Joe today and tomorrow."
  • “How to convince your boss you need to go” content.
  • Emails to registered attendees leading up to and following event.
  • Financials.
    • Excella can handle back-end AR/AP, if needed.
    • Talk w/ Ramez Mourad (DODDC Treasurer).
Clone this wiki locally