Summary
Artifacts
- streaming destinations selected, after reviewing terms-of-service, privacy rules, etc
- guidelines re what can be streamed, where (e.g. no simulcast to Facebook live?)
- conferencing provider selected and accounts created
- decide if video conferences are going to be simultaneously streamed to eg YouTube. If yes, determine if conferencing service provides this service, and if we will use it.
- simulcast provider selected and accounts created (possibly optional if conferencing provider is used to simulcast to YouTube, etc.)
- guidelines re fair use/copyright created
- guide for finding licensable/public domain audio, backgrounds, etc found
- Optional: local library of usable assets
- guidelines for demarcating live (audio and video, audio only) and ‘safe’ areas when public streaming is happening
- privacy policy and waiver templates
Workbook
Google spreadsheet containing notes, estimates, etc. -> here
Potential Suppliers
- Live stream/recording repositories: YouTube, Twitch, Facebook Live
- Video conferencing services: zoom, bluejeans, jitsi. See the Big summary of conferencing providers
Key Observations
From streaming providers:
- Key streaming providers need to be identified and their terms of service carefully reviewed
- These requirements need to be clearly communicated to users of the system
- If simulcasting is to be done, consideration has to be given as to if this is to be done by a separate service (eg ReStream) or via options provided by the video conferencing providers. For example Zoom can simulcast conference calls directly to YouTube.
- Clear privacy policies and declarations need to be developed, both for presenters and also audience members
- Protocols need to be developed to communicate privacy protocols- e.g. areas enclosed in red tape will be on camera. Surrounding areas may be picked up by microphones
- Clear policies and training needs to be developed with regard to fair use and legal licensing of images/videos/music/video game play throughs, etc