Background


This is a back-to-our-roots Pause, which means it's free (donations accepted), short notice, and recording is solely BYOS. So if you want to record your session or a session you're really into, that's cool. But we'd prefer the recordings be more organic so they are the exception in sessions rather than something speakers need to think about. Partly this is because we're realistic about the post production just not getting done, and partly because we think they get in the way.

Here is Matt Navarre's take on this (Matt did most of the recording tech for the last two Pauses)...

"Wow, I love how the recording plan has evolved, and all for the better I think. Recording all the audio and video for the sessions did present a huge challenge for post production. And recording changes the nature of what the presenter might say, and how (or whether) the audience participates."

"In reflection, after all the effort that FMI went to in recording all the sessions at DevCon - do you know how many of those I've watched? None. And I bet that's true for most developers, even though I had and have every intention of watching several of them. They're just not as riveting as TV or iPad games, or sleep, or billable client work, or bike rides, or 3 week ocean kayak trips, etc. Short interviews with speakers and presenters are what is useful to a larger audience."

(Matt will be recording interviews and podcasting from Pause: be sure to speak into the mic.)

Guidelines


So where does that leave us?

  • Record your own session and broadcast it wherever? Cool, but it's polite to tell everyone in the room that you're recording it. (Linking that recording to your session page would be cool as well.)

  • Recording someone else's session? Cool, just be subtle, get the session leader's permission privately ahead of time, and get that of everyone in the room publicly. If someone objects at all, don't record it.

  • Record every session and post it to get attention? Not very cool.