Skip to content

NYCrb/organizing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 

Repository files navigation

In-between Meetup tasks

  • 2 months prior to a future Meetup, create a new event on http://nycrb-cfpapp.herokuapp.com. Copy-paste guidelines/description from previous Event. Announce the new, open CFP (be sure to mark event status as "OPEN") on the NYC.rb mailing list ([email protected]). Set the proposal deadline to 1 week prior to the future meetup. EXAMPLE: For the March 2016 meetup, we opened proposals at the January meetup (January 12), and proposals were due three weeks later (Feb 2nd), 1 week before the next meetup (Feb 9).
  • 1 week prior to proposal deadline, send a reminder email to [email protected]. EXAMPLE: For the march 2016 meetup, we sent this email on 1/26. Remind people to submit talks. We suggest automating this email with a tool like Boomerang for Gmail or similar.
  • 1 day prior to proposal deadline, send a reminder email to [email protected]. EXAMPLE: Sent on 2/1. Remind people to submit talks. We suggest automating this email with a tool like Boomerang for Gmail or similar.
  • The day after the proposal deadline, all organizers independently rate each proposal on a 1-5 scale (done in the app). The best 2-3 talks get selected for the meetup. Organizers have a 15-minute phone call to discuss the selection, making sure time and subject matter concerns are met. One organizer is delegated to update the meetup description with the talks that were selected.
  • At each Meetup, we announce talks for the next Meetup. EXAMPLE: At the February meetup, we announce the talks for March.

Running a Meetup

6:30 - Arrive

  • Set up microphones
    • Hold pwr button to turn on and off
    • Ask each speaker if they will be live-coding. If they will, be sure they are given a lavalier style microphone (the kind that clips to your shirt).
    • We usually have a helpful A/V person from Pivotal helping us. They usually sit in the back, next to the microphones. Introduce yourself!
  • Get each speaker to plug in and test display setup. This is important for making sure their display works properly and the projectors are warmed up.
  • If you haven't already, tell speakers what order they will be presenting in.
    • We usually let them decide it between themselves.

7:00 - Announce starting soon

  • feel the room, start either immediately (if full) or within 10 minutes (if people still filtering in)

7:05 - Begin

  • What you should say:
    • Welcome to NYC.rb!
    • Thank you to Pivotal Labs!
    • Pizza and drinks in the back. Remind people that food is for here, not for the road (don't take snacks that you arent gonna eat here! Pivotal is not your pantry!)
    • Point out bathrooms (ladies is furthest from the podium)
    • Ask audience for announcements - hiring, events interesting to Rubyists (sometimes we delay this until the end).
    • Any NYC.rb announcements - ask for proposals for next month, etc
  • Run talks in order - I usually don't introduce each person extensively, just say name and title of talk.
    • Leave 5 minutes for questions, try to keep stuff on time
    • Watch time for each speaker.

Wrap-up

  • Stack chairs.
  • Stack pizza boxes.

9:00 Hard stop

  • Everyone has to be out by 9 - this is to respect Pivotal's time

About

Documents describing how NYCrb is run/organized

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published