Google Code-in/Making videos

From MusicBrainz Wiki
< Google Code-in
Revision as of 20:58, 18 October 2018 by Rdswift (talk | contribs) (Corrected the point providing the feedabck.)

This page will hold some pointers, tips, and best practices for making videos for the MetaBrainz YouTube channel, esp. in the context of Google Code-in.

General workflow

  1. First off, before you start recording: make a script going over the things you want to talk about, making sure it includes any points you want to make.
    Now you read this over and make sure that it makes sense and preferably get someone else to look it over too. (If you're a GCI student, you should absolutely submit this on your task for your mentor(s) to review it!)
  2. Do a first recording.
  3. Look over the recording, make sure audio levels are okay, that any text is visible/readable, that you're speaking clearly and articulate clearly.
  4. Get someone else to review the video.
  5. Based on feedback from 3. and/or 4., you may need to re-record certain parts (or all!) of the video. Lather, rinse, repeat until there are nothing further to refine.
  6. Add in any effects, background music, credits, etc. (Be sure to keep the original recordings for now!!)
  7. Get someone else to review the edited video.
  8. Based on feedback from 7., you may need to change some of the editing. Lather, rinse, repeat until there are nothing further to refine.
  9. Write up a video description text (see existing video on the YouTube channel for what to include/how to format it).
  10. Once everything has been approved of and a video description text has been supplied, your mentor will upload the video to YouTube. Thank you so much for your contribution to MetaBrainz!!

Licensing and asset use

Open source, open data, and open content are using licenses that give certain rights and freedoms on top of "raw" copyright law. This has a number of implications, but that most important one is that only the one that actually holds the copyright for a given work can declare under what license they want to distribute their work. We (obviously) wish to respect this.

For our own videos, we prefer to use the Creative Commons Attribution-ShareAlike license, which means that any assets (graphics, sound effects, background music, etc.) need to have been released under a compatible license. Please be sure to list the sources for any assets you use in the video.