Community: Create a recurring zoom meeting for the sig-testing kind subproject

[spiffxp]

ref: https://kubernetes.slack.com/archives/CEKK1KTN2/p1548192461363600

After looking at responses from everyone @munnerz and I are planning to start at project meeting 11AM PST on Mondays, starting next week hopefully.

I'm going to take this opportunity to try setting up sig-testing meetings correctly.

/sig contributor-experience
hey look I'm finally doing the zoom stuff

/sig testing
/kind cleanup
/priority important-soon

[spiffxp]

/assign
ok, trying to setup the kind meeting real quick

[spiffxp]

Meeting settings in zoom (minus the link)

[spiffxp]

To create the calendar invite:

• I let zoom add it to my gmail.com calendar (then removed access because I'm paranoid like that)
• I should not be trusted to own this thing so I sent an ownership change request to @BenTheElder
• I invited kubernetes-sig-testing@

[spiffxp]

/assign @BenTheElder
to confirm ownership of this meeting now

[parispittman]

@spiffxp you should create a shared calendar and then transfer ownership of that invite to the shared calendar. add sig-testing-leads to the shared calendar with change perms and everyone will be able to edit the meeting.

Also, the waiting room is optional these days and only for hosts comfort. not required so take that as you will.

[BenTheElder]

Thanks @spiffxp, I accepted the transfer link and see edit rights on the calendar entry, I believe (?) that confirms.

[spiffxp]

@parispittman that makes sense, is this something I overlooked in the docs?

[parispittman]

@spiffxp i dont see anything in the docs that indicates turning it on although that was the previous recommendation at one point. can you point to where you saw that so I can make the change?

[BenTheElder]

we're having issues with users not being able to see the meeting via link it seems, but I've shared out the zoom link form it for now.

[BenTheElder]

[noting that we need to fix the calendar entry -- seems only I and maybe @spiffxp can see it, also the zoom meeting didn't seem to actually allow join before host :confused: ]

[parispittman]

@BenTheElder - that's because the waiting room was enabled. Needs to be one or the other.

[BenTheElder]

I believe I've just fixed the calendar entry to properly invite [email protected] based on all the auto-decline-rsvp emails in my inbox 😂
I think the zoom meeting still needs fixing and this needs to go in the SIGs metadata. 🙏

[spiffxp]

I disabled the waiting room, meeting worked as expected today

[spiffxp]

Just to close the loop on "did I read the docs", I saw something about the waiting room at https://git.k8s.io/community/communication/zoom-guidelines.md#moderation and assumed that was a thing I needed to enable. The doc shared with kubernetes-sig-leads@ mentions it, but only as an "if you have it enabled"

Why this is still open: I need to actually make a sig-testing shared calendar and put the meeting there

[parispittman]

the doc is currently showing that the waiting room is what happens when you put someone on hold. we told folks to initially to enable that before we had the security under control but have since edited out those instances on all docs.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

I think this is done? :-)

[spiffxp]

/remove-lifecycle stale
/close
Yeah this has been done for a while (I did the shared calendar thing under https://github.com/kubernetes/community/issues/3345)

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/remove-lifecycle stale
/close
Yeah this has been done for a while (I did the shared calendar thing under https://github.com/kubernetes/community/issues/3345)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.