Difference between revisions of "Projects/OWASP Media Project/Help"

Revision as of 07:25, 19 October 2018

Help for Google Hangouts, YouTube Channel management and social media tips will be here.

Guidelines and standards for YouTube

Access management is currently given to OWASP Media Project leaders and OWASP Global Staff. Make sure you:

• Send an email to the project mailing list when adding or removing access
• Move back to communication manager any manager that are not posting video content actively
• Periodically audit and clean up the accesses given to people
• You can access the manage permissions page while logged in with the correct Google account on Brand Account details

In order to achieve an acceptable level of quality and consistence trought the videos upload on the channel, each uploaded videos must meet theses requirements :

• Comply with YouTube Copyright regulations http://youtube.com/yt/copyright/what-is-copyright.html
  • Fun introduction https://www.youtube.com/copyright_school
  • Basically, do not upload any content or partial content that are from another source, that includes music, TV show captures, clips from movies/TV.
  • If we get Copyright strikes, after 3 we are out and will be ban from YouTube. We are at one strike before the writing of the current requirements and lost some advantages of our partnership with Google. Current resolution of status is due April 2013.
  • Deleting an infringement strike trigger (it's automated) videos won't help removing the strike.
• Respect basic quality standards for uploaded videos.
  • 720p minimum, upload in 1080p Full HD if available (YouTube will create lesser resolutions versions automatically)
    • Use recommended YouTube mp4/aac/H.264 encoding if possible (no conversion will be done, upload will be faster) https://support.google.com/youtube/answer/1722171?hl=en&ref_topic=2888648
    • Use recommended 16:9 ratio if possible
  • Slides must be readable in 480p (for mobile usage and default web view).
  • Sound must be clear and with no electronic noise or with minimal white noise.
  • Google Hangout are relaxed from theses quality standards as long as the slides are full screen and we can hear fine the speaker.
  • Editing must be professional level or very minimal with YouTube tools or absent.
• Upload videos only with consent from the source even if it's OWASP (like a chapter or a conference).
• For meta data information:
  • Put the subject and the speaker name in the title
    • If the subject is too long, the speaker name can be omitted
  • Link to the source on owasp.org Wiki and then any links you want
  • Put the abstract if available and speaker BIO in the description
  • Leave the OWASP Media Project signature
  • Use the default tags (currently #owasp and #appsec) and optionally add some if desired
• If videos are from a logical batch, associate it with a playlist (Example: AppSecEU2013 playlist)

YouTube uploading procedure

Prerequisites

• Have a Google account, preferably an @owasp.org one, that is added as a manager of OWASPGLOBAL YouTube channel
• If you plan to upload content regularly, you must be subscribed to our OWASP Media Project mailing list
• Read the "Guidelines and standards for YouTube" especially about copyright

Warnings

• Use another browser or profile than your normal browser in order to upload to YouTube. If you browse YouTube as "OWASP", all history, likes and favorites will be shared with the channel.
• Take special care of your account because it is now having all access to a front-facing OWASP asset

Procedure

• Login as OWASP on YouTube with the top right account change widget
• As OWASP, Create a playlist with the name of your contribution
  • For a conference, use the full name and the year
  • Examples: AppSecUSA 2014, Projects Summit 2014, OWASP Global Chapter Meetings, https://www.youtube.com/view_all_playlists
• Upload the video using https://www.youtube.com/upload
  • In Privacy settings, make it "Unlisted" or "Private" if you don't want it to be shown right away
  • As it upload and process, set the correct title and description (please leave the Media Project signature)
  • Add tags related to the subject or the contribution. These are like keywords.
  • You can use the Video Manager in order to tag many videos at once
  • Save and wait until it is completely uploaded
• View the video and add it to your playlist
  • Change the Privacy settings to Public if it was Private or Unlisted
  • Review title and description
• Share the video as you wish on Twitter, LinkedIn, Facebook, etc.
  • Use embed code to share it in HTML
  • Use wiki code #ev:youtube|VIDEO-ID or #ev:youtubeplaylist|PLAYLIST-ID between {{}} for owasp.org wiki

YouTube + Hangout streaming procedure

This is partially oudated as of 2018

Hardware and other software

In order to get the best "bang for the bucks" hardware possible, we have used and tested many devices. We apologize to direct you to specific products but some people needed direct suggestions.

Microphone

If the presenter is in front of a presentation laptop, use the microphone on that laptop. If it happens to be a MacBook Pro, you'll get great sound. If not, any USB microphone that is around the 100$USD mark will do the job. The H1 Zoom has been reported as worked on Mac, Windows and Ubuntu is a plug-n-play manner. It can also used as an stand-alone offline recorder (event with a pro lapel mic).

Note that any phone devices (dials in, Bluetooth) will reduce the sound quality and that might be problematic if you are aiming for the better quality.

Also, wireless is great, but costly. If you have a budget between 500-1000$USD for sound and operating staff, go for it, if not you're better with wired equipment.

Video capture

For low budget recording, we strongly recommend using software screen recorder and no hardware. You can use Open Broadcaster Software to stream and locally records any content. It's free and open source and for Win/Linux/Mac but we have tested only the Windows version. It also supports captures cards and webcams.

If you want an hardware soluion, you can input from a dedicated capture card. Many of them are branded for gaming recording purpose and will do real fine. The main advantage of the capture card is that you don't need to install any stand-alone software or plugins on the presenter's laptop. You'll quicker results and quality won't be touched much, except if you are still using VGA instead of HDMI. Some cards can "wiretap" by offering a bypass between the projector and the computer.

OWASP has in stock a few X-CAPTURE-1 to capture from HDMI and VGA, all with bypass features. It's biggest limitation is that it is Windows (DirectX) compatible only but they capture the greatest range of outputs for that price (around 350$USD). For official big OWASP events those cards are available for lending. However, in 2018, many cheaper and better solutions are available. Some of them even have on-board recording without the need for a computer. Just make sure you are recording in HDMI.

Conference Guidelines

OWASP Media Project used to provide on site recording for talks during major OWASP conferences (20+ speakers), but this is now a thing of the past. In order to achieve a respectable results in quality of content, dealing with an experienced professional vendor is now a must.

Note that OWASP Media Project will still provide support on uploading, publishing and marketing of the video content as of 2018. Vendor could still be required to upload to YouTube, this is particularly useful if they don't deliver on physical media by the end of the event.

In order to assure painless success some hard requirements are to be followed:

• Use HDMI for screen capture
• Do not record the slides using a video camera and use that as final publishing
• Require the vendor to have experience with recording presentations

And some somewhat flexible requirements (downplaying them will jeopardize quality):

• Require the vendor to have experience with online publications
  • Have the vendor send a prior sample of their work
• Coordinate the recording vendor with the audio vendor
  • Some hotels will enforce their own audio vendor, fight them or make sure that they have a SLA in the contract
  • Most of the problems you'll have at this point will be audio, be prepared, but don't go as silly as have dual microphones, unless it's a huge keynote.
• Have the vendor do live post-production. That means that talks are ready at the end of the conference, not 2-4 weeks after
• If they do post-production with music, make sure it has been tested on YouTube to not generate copyright strikes.
• If recording of the speaker is done, make sure it's with professional grade camera
• Prioritize keynotes on budget for recording and additional marketing efforts

What to NOT do:

• Do not use your own laptop for presentations with software recording
  • We actually suggest software recording for smaller or single talk event, but in a big conference that's a guaranteed headache
• Do not publish all content at once
• Do not expect 100% quality from any vendor
  • A 5% failure rate is to be expected; you'll loose some recordings, sound will be bad on some, aspect ratio might be weird, HDCP might ruin everything.
  • Some talks will be beyond salvage. We published them in the past but with 700+ videos online now, we think it's unnecessary unless there's a direct demand from the community to see the talk anyways.
• Do not wait to publish talks more than ~3 months after the event.
  • With global events overlapping, you also don't want to publish one event over the other.

Last but not least, be ready to pay the price. We suggest that you look for sponsors in order to cover the costs. Be aware that you might break YouTube EULA by adding ads inside the videos, especially when using permanent logos. You can however add a comment bellow in text, or do sponsored content in a stand alone video or inside the content.

If you are lucky, you might find a local enthusiast that will do it for free. In this case, we suggest to have professional recording of the keynotes, and make sure you handle the risk you are taking by having exceptional communication between them and the conference team.