Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

youtube channel needs a new owner #3985

Closed
parispittman opened this issue Aug 8, 2019 · 9 comments
Closed

youtube channel needs a new owner #3985

parispittman opened this issue Aug 8, 2019 · 9 comments
Assignees
Labels
area/community-management priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Milestone

Comments

@parispittman
Copy link
Contributor

parispittman commented Aug 8, 2019

I'm the current owner on the community channel for youtube. I'd like to pass the torch to another youtube admin.

A) how should someone be selected for this role?
B) let's document it.
C) can contributors@kubernetes.io own it and then multiple people have access? unsure. need to investigate. [update: yes, this address can be the primary owner. i will remove myself as the primary owner and add this account.]
D) if not contributors@, who? [update: see 'C']

@parispittman parispittman added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. area/community-management labels Aug 8, 2019
@parispittman parispittman added this to the August milestone Aug 8, 2019
@parispittman parispittman self-assigned this Aug 8, 2019
@parispittman parispittman added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 8, 2019
@mrbobbytables
Copy link
Member

At least for C, it should be possible for contributors@kubernetes.io to own it. A shared owner account will certainly help with the current bus-factor aspect. 😬

Better management (ref: #3938) of the credentials shouldn't necessarily be a blocker for changing ownership...but we should probably pursue sorting that out sooner rather than later.

@xiexiaojing
Copy link

A shared owner account is an excellent idea.😀

@castrojo
Copy link
Member

Feel free to move primary ownership to me, I can at at least assign a new moderator and start documenting the process.

@parispittman
Copy link
Contributor Author

update - contributors@ will be the primary. next step is figuring out who should get access to contributors@. i think it should be everyone in the owners file at the root for the community-management subproject. thoughts? we need to update docs, too.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 19, 2019
@cblecker
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 19, 2019
@cblecker
Copy link
Member

/assign castrojo
I think this is done, isn't it?

@mrbobbytables
Copy link
Member

It is done \o/
/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

It is done \o/
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community-management priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Development

No branches or pull requests

7 participants