Community: Improve process for requesting Zoom -> YouTube automation

[mrbobbytables]

As we've had multiple groups recently come forward regarding setting up the splain -> Youtube bridge, we should do 2 things:
1) Create a generic YouTube/Zoom GitHub issue request to handle things like automation (splain), as well as new playlist requests etc.
2) improve instructions / record keeping as each additional zoom account that has splain integrated requires an additional license.

/sig contributor-experience
/area community-management
/milestone next

[k8s-ci-robot]

@mrbobbytables: The provided milestone is not valid for this repository. Milestones in this repository: [August, Next]

Use /milestone clear to clear the milestone.

In response to this:

As we've had multiple groups recently come forward regarding setting up the splain -> Youtube bridge, we should do 2 things:
1) Create a generic YouTube/Zoom GitHub issue request to handle things like automation (splain), as well as new playlist requests etc.
2) improve instructions / record keeping as each additional zoom account that has splain integrated requires an additional license.

/sig contributor-experience
/area community-management
/milestone next

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.

[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

[mrbobbytables]

/remove-lifecycle stale

[onlydole]

/assign @onlydole

[onlydole]

I'd love to tackle this with you, @mrbobbytables and @castrojo (if you're down!)

[mrbobbytables]

There is an open issue regarding adding another sig for the splain automation. This would be a great time to go through the process and improve the docs / add the issue template 👍

[mrbobbytables]

@onlydole friendly ping. Is something you're still interested in taking on?

[onlydole]

I am indeed! I need to take a look at what's currently in place and then I can get started. I’ll have time this coming week to take a peek.

[onlydole]

I'm still looking into this one...do you know the best place I can come up to speed with Splain, @mrbobbytables?

[mrbobbytables]

We have some docs here: https://github.com/kubernetes/community/blob/master/communication/youtube/youtube-guidelines.md#automation

But they should be cleaned up... and a GH template for requesting it assigning the youtube admins would be useful here too.

1. We have to request an additional splain license by sending an email to [email protected] with the email address of the zoom account requesting the integration ([email protected] should be cc'ed on this)
2. A youtube admin has to login as the zoom account holder to setup the ouath app. Once it's connected and the flagging vids to be private by default it's pretty much setup.
   
   
   
   • The requesting SIG should NOT have auto-record enabled for their meetings
   
   
   • If they have multiple SIG meetings e.g. for multiple subprojects, each one should be scheduled via zoom independently to be given a unique zoom name ID. Otherwise they will all go into youtube as a same name.
   
   

After that it should pretty much be good to go.

[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

[onlydole]

/remove-lifecycle stale

[mrbobbytables]

We can hold off on doing this until splain is reliable again :(

[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-contributor-experience at kubernetes/community.
/lifecycle stale