Add AI notetaker guidance to Zoom meeting guidelines

[TineoC]

Fixes #9030

Adds a new section to communication/zoom-guidelines.md recommending hosts:

• Enforce authentication (only authenticated users)
• Enable CAPTCHA for guest users
• Use waiting room

This avoids maintaining a domain block list or marketplace app block list — authentication is the primary defense since bots join as anonymous guests.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: TineoC
Once this PR has been reviewed and has the lgtm label, please assign priyankasaggu11929 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• communication/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Champbreed]

Thanks for the PR! Left one review.

[Champbreed]

There are two ways to use the waiting room — reactive and proactive. The Moderation section above covers the reactive use: sending a participant to the waiting room during a live meeting via Host Tools. But since bots join the moment a meeting opens, the in-meeting toggle might be too late.
Per waiting room documentation, hosts can enable the waiting room as a standing setting before the meeting starts via zoom.us → Settings → Meeting → Security → Waiting Room. It would be worth adding the setup path or linking the documentation here so hosts configure it before going live rather than trying to manage it mid-meeting.

[chris-short]

/hold

Per my comment on the issue:

None of these options are great, but I think we should update the guidance to clearly state we don't allow notetakers. Perhaps enforcement mechanisms should be discussed separately.

Instead of focusing on remediation techniques, we need to create language stating that AI notetakers are not allowed at community meetings. The remediation methods are still up for debate; none of them are great options and all of them create work/processes for someone else. The language and the remediation suggestions need to both be done thoughtfully.

Let's focus on the language that AI notetakers are not allowed; then we can work with Zoom Admins, SIGs, and Steering on remediation methods. It's vitally important that we don't turn off potential new contributors because of hastily implemented remediations meant to fix what is a mild inconvenience at the beginning of community meetings.

[TineoC]

@chris-short do you want to remove everything after this line?

[chris-short]

Yes, keep the part about removing notetakers if they're in the meeting, though.

[TineoC]

/unhold