Please refrain from public sharing of Zoom links and add moderation of Zoom Meetings

[bbu...@microsoft.com]

Folks,

We have unfortunately seen a couple of incidents of in-appropriate conduct in SIG meetings. Anonymous users have joined the meetings and behaved in ways that are unprofessional, in-appropriate and violate the code of conduct.

I would like to apologize to anyone impacted by this, and strongly condemn this sort of behavior. It is literally the dumbest, worst part of the internet.

At this time, we believe that the people doing this are from outside the kubernetes community and as such, we would like to encourage everyone in the community to take steps to ensure the integrity of our online meetings.

The first request is that people stop sharing public Zoom links on freely available/searchable mediums. Please do not share links on Twitter, Google Groups or Github. If you have existing links, please consider generating new links and sharing them in a more limited setting such as Slack. If you have Zoom links on github, please either remove them, or move them to a private repository.

Additionally, I'm re-posting the recommendations Paris posted recently for increasing the moderation of our zoom channels:

Here are some changes that we suggest:

1) Co-host; allow host to have the same in meeting controls as host 

2) Allow host to put attendees on hold - This allows hosts to temporarily remove an attendee from the meeting.

3) All new persons joining a meeting will be muted by default. 

There is a control that is in beta from Zoom to identify guest participants in the meeting. This is a beta feature and we will be asking the CNCF/LF to ask Zoom about this since we are paying customers. 

Additionally we have published some general and Zoom-specific moderator guidelines:

- https://github.com/kubernetes/community/blob/master/communication/moderation.md

- https://github.com/kubernetes/community/blob/master/communication/zoom-guidelines.md

And lastly the steering committee will be approaching the CNCF about how to best tie in our org structures to Zoom via their API so we can tighten up some of the permissions on our meetings. 

If you are a SIG lead, please take the time to learn how the moderation tools in Zoom work and the policies that need to be applied. A good technique is for you to log in with a colleague and practice how to put people on hold, etc. 

We will also be investigating if there is more we can do with the Zoom API to make our meetings less of an easy target.

Thanks in advance for your help in protecting the values of our community.

--brendan

[Dan Kohn]

Thanks for raising these concerns. This is a priority for CNCF to help resolve. 

There is a setting available to require participants to sign into a meeting: https://support.zoom.us/hc/en-us/articles/115002542483-Restrict-Access-to-Join-a-Meeting

The downside is that it would require those dialing in from their phones to first connect via the Zoom app. CNCF will work with Paris and ContribEx to investigate this and the beta option you mention.

--

Dan Kohn <d...@linuxfoundation.org>

Executive Director, Cloud Native Computing Foundation https://www.cncf.io

+1-415-233-1000 https://www.dankohn.com

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/e1cca941-6b44-4a41-9e96-6ed85b2512ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.