Skip to content

Latest commit

 

History

History
109 lines (89 loc) · 3.57 KB

format.md

File metadata and controls

109 lines (89 loc) · 3.57 KB

FoodFightShow

The main foodfightshow is a panel show modeled after the ruby rogues. More than 5 participants is difficult to handle, or at least each individual participant has much less opportunity to talk.

Purpose

  1. To summarize important development in Chef community on ML, chat, conferences for busy people who can't necessarily be there or read the ML everyday
  2. For fun!
  3. Discuss w/ really smart people about subjects that are of interest operations professionals
  4. Help people in community feel like they “know” prominent community members
  5. Introduce Chef to new users

Not the Purpose

  1. To talk about religion, sex or politics
  2. discuss consumer technology, other shows do that better
  3. To hate on Microsoft or other proprietary technology
  4. To promote desktop linux

Recording an episode

In general, you should try to minimize the time you spend planning an episode. Time spent episode planning takes away from time spent recording.

  1. Round up some prospective guests, tell each of them to wear a headset during recording and mute their built-in audio
  2. If you have multiple participants, use doodle.com to find a suitable time.
  3. Use Foodfightshow calendar to send an invite w/ the recording date we have a good invitation template to which you'll need to add a link to show notes.
  4. Notify participants w/ the url for the google hangout about 10 mins beforehand, remind them to use a headset and mute built-in audio
  5. Send a tweet notifying our fans of the episode
  6. log on to irc #foodfightshow ahead of the episode. We get a lot of questions from there.
  7. Warn participants that the show will be recorded live and we can't edit the video on youtube.
  8. Tell everyone when u go on air
  9. Keep the main discussion to 1 hour, but picks section can go over one hour
  10. Tell everyone when you go off air
  11. Post-production
  12. create stub of show notes w/link to youtube video and publish
  13. download the video from youtube
  14. strip the audio using screenflow or ffmpeg
  15. put together show notes using the foodfight/foodfightshow.github.com repo
  16. Put the first 15 seconds of the foodfight theme song at the beginning of the show and again at the end
  17. remove blank spots and curse words from audio
  18. upload to libsyn.com
  19. grab the url to the mp3 download
  20. add mp3 download url to show notes and push
  21. tweet that show now available

Sections

  1. Chef news - less than 5 mins about recent events in chef community
  2. Guest intros
  3. Topic Discussion
  4. Picks
  5. Goodbye
    1. send in cookbook news
    2. subscribe to newsletter
    3. thank guests

Notes for Guests

  1. Use a USB headset, not one w/ analog connector, you'll thank me later
  2. Mute the internal audio and microphone on your laptop
  3. Please move to a quiet room for the show recording
  4. Don't be shy. This is an amateur operation, share your dumb jokes
  5. Be opinionated, that's why we invite you on the show

Rules

  1. Family-friendly, keep it G-rated
  2. Don't talk about politics, religion, your sexual exploits. 50% will disagree w/ you and the other 50% won't care.
  3. Don't trash other open-source projects
  4. Don't trash Microsoft

Show License: CC-BY 3.0

DevOps Delicacy

This is a much shorter, focused show. Typically it will only have two participants. It is intended to focus on specific tools and practices. Anyone can produce a DevOps delicacy. These shows will typically run 30 minutes.