Zoom meetings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Hi, over the break it appears that Zoom has added some new security features, including verification by email when someone logs in from a new location.
I looked into it and here's the fix. Instead of having the meeting host log directly into the nodejs-meetings@openjsf.org zoom account, you should instead log in with your own Zoom account. When you're in the meeting, open the participants panel and click "Claim host". It will ask you for the host key, which is a six digit number specific to each zoom account. This should be done by the person who will run the livestream, as only the host can initiate a stream. (As before, you'll still need access to the YouTube account in order to stream, that part is unchanged.)
There are a few advantages to this, one being that we no longer have to use LastPass to share out the credentials. I'll provide the host key to a few community members, or you can email operations@openjsf.org to request it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the administrative documentation for Zoom meetings and livestream setup; no file or entry point is named in the issue. Compare the existing instructions with the proposed personal-account and host-key process, then update the relevant guidance so the new login, host-claim, livestream, and support steps are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100