|
| 1 | +# Streaming Meetings to Youtube |
| 2 | + |
| 3 | +We publicly live stream our meetings to YouTube using [Zoom](https://zoom.us/). |
| 4 | + |
| 5 | +## Getting Access |
| 6 | + |
| 7 | +You need the Foundation login credentials for Zoom in order to host the meeting. |
| 8 | +The userid and password is shared through 1password. |
| 9 | + |
| 10 | +Your YouTube Account must be a manager of the |
| 11 | +[Node.js YouTube account](https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ). |
| 12 | + |
| 13 | +To request access open an issue in the Node.js |
| 14 | +[admin](https://github.com/nodejs/admin) repository with the title being |
| 15 | +`Zoom and Youtube access for X` where X is the GitHub id and |
| 16 | +the YouTube ID of the person for which access is being requested. |
| 17 | +Include a short reason why access is needed(for example streaming |
| 18 | +a team meeting etc.). |
| 19 | + |
| 20 | +Unless there are objections the request is considered approved after 48 hours. |
| 21 | + |
| 22 | +## Managing access |
| 23 | + |
| 24 | +### Youtube |
| 25 | + |
| 26 | +To add managers or verify an account is a manager: |
| 27 | + |
| 28 | +1. Go to <https://youtube.com> |
| 29 | +2. Click on the Node.js icon on the right top. |
| 30 | +3. Select settings, select "Add or remove managers", select "Manage permissions" |
| 31 | +4. On that page you can use the +people at the top right of the popup to add |
| 32 | + people. It also lists all current managers. |
| 33 | + |
| 34 | +### Zoom |
| 35 | + |
| 36 | +To share the Zoom password log into 1password, select the settings gear for |
| 37 | +the`zoom-creds` vault and then use `Share Vault` to share the vault with the |
| 38 | +new user. Use the gear to set the permissions to include only `View Items` and |
| 39 | +`View and Copy passwords`. |
| 40 | + |
| 41 | +When adding access for a user also ask them to create a PR adding themselves |
| 42 | +to the `zoom-nodejs` group in the |
| 43 | +[iojs.org/aliases.json](https://github.com/nodejs/email/blob/main/iojs.org/aliases.json) |
| 44 | +file [nodejs/email](https://github.com/nodejs/email/) |
| 45 | + |
| 46 | +## Live streaming a meeting |
| 47 | + |
| 48 | +### Start and Stop the stream |
| 49 | + |
| 50 | +1. Login to <https://zoom.us> using the Foundation credentials. |
| 51 | +2. Go to <https://zoom.us/webinar/list>, find the meeting. |
| 52 | +3. Press "Start", it should open the meeting in the Zoom application. |
| 53 | +4. Go to "Participants" panel, check Attendees, promote them to panelists. |
| 54 | +5. Go to "... More" in toolbar, choose "Live on YouTube", it will open in |
| 55 | + browser. |
| 56 | +6. Choose to login to <https://youtube.com> with Node.js account, accept |
| 57 | + Zoom usage agreement (on first use) |
| 58 | +7. On the Streaming page, edit the webinar title to include the meeting date, |
| 59 | + then press the red "Go Live!" button. Troubleshooting note: at least one |
| 60 | + person has found that "Go Live!" errored with a message "Please grant |
| 61 | + necessary privilege for live streaming". Copying the link from the default |
| 62 | + browser to a different browser may work around this issue. |
| 63 | + |
| 64 | +Every participant can choose whether to participate with or without video. |
| 65 | + |
| 66 | +YouTube records the live stream. Recordings are made available on the |
| 67 | +[Node.js channel](https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ/videos). |
| 68 | + |
| 69 | +The stream title is set automatically from the information in Zoom. We usually |
| 70 | +set it to `YYYY-MM-DD - Meeting Name` for example |
| 71 | +`2022-11-02 - Technical Steering Community Meeting`. |
| 72 | + |
| 73 | +The description should be a link to the meeting issue. |
| 74 | + |
| 75 | +You can edit title and description on YouTube at a later time if needed. |
| 76 | + |
| 77 | + |
| 78 | + |
| 79 | +### Share the meeting once you've gone live |
| 80 | + |
| 81 | +The meeting link should be `http://www.youtube.com/c/nodejs-foundation/live`. |
| 82 | + |
| 83 | +Send it in a tweet such as: |
| 84 | + |
| 85 | +```text |
| 86 | +.@nodejs Technical Steering Committee meeting live now: |
| 87 | +http://www.youtube.com/c/nodejs-foundation/live |
| 88 | +``` |
| 89 | + |
| 90 | +Adjust the `Technical Steering Committee` part as necessary and remove the |
| 91 | +`.@nodejs` if tweeting from the official twitter account. |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | +## Check stream status |
| 96 | + |
| 97 | +This should say online when you are streaming, and usually be green. |
| 98 | + |
| 99 | +However, it may turn yellow and issue a warning in a "stream health" |
| 100 | +section below. Since we usually stream with static images for the |
| 101 | +video, there will often be warnings that the video bitrate is low. |
| 102 | +This is a not a problem and should almost always be ignored. |
| 103 | + |
| 104 | + |
| 105 | + |
| 106 | +## Check how many people are watching |
| 107 | + |
| 108 | + |
| 109 | + |
| 110 | +## Moderate the chat and solicit questions |
| 111 | + |
| 112 | +Moderation follows the [Moderation Policy](https://github.com/nodejs/admin/blob/main/Moderation-Policy.md). |
| 113 | +Messages can be moderated right-clicking and selecting the necessary action, |
| 114 | +such as `remove`. |
| 115 | + |
| 116 | +If you participate in the chat while logged in as Node.js, it's good |
| 117 | +practice to append your initials to your messages. |
0 commit comments