Closed chris-short closed 2 months ago
/assign mfahlandt
/sig contributor-experience
/area contributor-comms
/assign chris-short
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@pnbrown Are we good here or still missing a component?
It looks good to me. I'd have to see what other onboarding has been done or if it's all captured
Currently, we have an automation setup in Zapier to take video from Zoom and dump it into Google Drive. Then, another Zap takes it from Google Drive to YouTube. But there are a few manual steps that need to happen on YouTube after the upload, and right now, @pnbrown is the only one doing that work.
Ideally, using Zapier Code, we can write a Python or JS script to accomplish the metadata tweaks needed on YouTube to eliminate this problem. @mfahlandt has taken the task of writing a JS script to update video metadata on YouTube. This means the above diagram becomes this: