search

operate-first / community

GNU General Public License v3.0
11 stars 6 forks source link

YouTube permissions for multiple people to upload #173

Closed quaid closed 1 year ago

quaid commented 2 years ago

For meeting notes, etc.

aakankshaduggal commented 2 years ago

Hey @quaid, could you please let us know the email associated for the people who'd want to upload on youtube.

quaid commented 2 years ago

Hey @quaid, could you please let us know the email associated for the people who'd want to upload on youtube.

Thanks, that would be a great solution to get us going today. We also need to know the process that one of us would follow to get posted live.

But we can also look from the beginning at how this can scale with our GItOps processes, e.g. what if we started with a YAML file with GitHub handles for each of the people who need to upload to YT? Even if the YAML isn't driving anything yet, we get the data out of an issue and into a repo?

(Feel free to tell me I'm silly or offer a better approach for what I'm trying to do, thanks!)

aakankshaduggal commented 2 years ago

@quaid We will have to grant access to your existing Google account on youtube to be able to post and interact with the operate first youtube channel. Yes, a YAML or a document that stores every authorized user's email address because we probably need that to link to the youtube account instead of a Github handle.

cc- @oindrillac please correct me if I am wrong. Is this the right set of action items we would require to add a user to operate first youtube account?

sesheta commented 2 years ago

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.

/lifecycle stale

sesheta commented 2 years ago

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.

/lifecycle stale

sesheta commented 1 year ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

sesheta commented 1 year ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 1 year ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/community/issues/173#issuecomment-1386270590): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.