Automation: Use the Zapier Code tool to eliminate manual labor on YouTube when uploading SIG videos

Question

Automation: Use the Zapier Code tool to eliminate manual labor on YouTube when uploading SIG videos

chris-short opened this issue 7 months ago · comments

Chris "Not So" Short commented 7 months ago

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.

graph LR
    RS1("SIG-ContribEx Zoom") --> Zapier
    RS2("SIG-Docs Zoom") --> Zapier
    RS3("SIG-K8s-Infra Zoom") --> Zapier
    RS4("WG-LTS Zoom") --> Zapier
    Zapier --> |$TOPIC for $TIME| D("Google Drive")
    D --> E("YouTube")
    E --> F("Nigel")
    F --> E

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:

graph LR
    RS1("SIG-ContribEx Zoom") --> Zapier
    RS2("SIG-Docs Zoom") --> Zapier
    RS3("SIG-K8s-Infra Zoom") --> Zapier
    RS4("WG-LTS Zoom") --> Zapier
    Zapier --> |$TOPIC for $TIME| D("Google Drive")
    D --> E("YouTube")
    E --> F("Zapier Code")
    F --> E

Mario · Answer 1 · Sat Jan 20 2024 00:20:06 GMT+0800 (China Standard Time)

/assign mfahlandt

Chris "Not So" Short · Answer 2 · Sat Jan 27 2024 00:59:53 GMT+0800 (China Standard Time)

/sig contributor-experience

/area contributor-comms

Chris "Not So" Short · Answer 3 · Sat Jan 27 2024 01:02:04 GMT+0800 (China Standard Time)

/assign chris-short

Kubernetes Triage Robot · Answer 4 · Fri Apr 26 2024 01:14:45 GMT+0800 (China Standard Time)

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Kubernetes Triage Robot · Answer 5 · Sun May 26 2024 01:22:16 GMT+0800 (China Standard Time)

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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Chris "Not So" Short · Answer 6 · Fri Jun 21 2024 23:24:46 GMT+0800 (China Standard Time)

@pnbrown Are we good here or still missing a component?

Nigel Brown · Answer 7 · Fri Jun 21 2024 23:42:55 GMT+0800 (China Standard Time)

It looks good to me. I'd have to see what other onboarding has been done or if it's all captured