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

Clean up outside collaborators #318

Closed
mrbobbytables opened this issue Oct 29, 2019 · 7 comments
Closed

Clean up outside collaborators #318

mrbobbytables opened this issue Oct 29, 2019 · 7 comments
Assignees
Labels
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.

Comments

@mrbobbytables
Copy link

Hey there @kubernetes-client/csharp-admins ,

One of the github-admins here. -- We have a longstanding issue on cleaning up outside collaborators, and are now actively planning on removing them on December 1st.

At this point, people that are actively contributing to the Kubernetes project should be promoted to org members, and any repo specific permissions should be managed through their associated configuration in kubernetes/org.

With that in mind, the following people are listed as outside collaborators:

Both @itowlson and @tg123 are active and I'd encourage applying for membership to kubernetes-client org. 😄

If you have any questions or comments, please don't hesitate to ask in here or feel free to poke me in slack 👍

Thanks!

assigning csharp-admins:
/assign @brendanburns @krabhishek8260

/sig contributor-experience
/priority important-soon

@k8s-ci-robot k8s-ci-robot added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 29, 2019
@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: GitHub didn't allow me to assign the following users: brendanburns.

Note that only kubernetes-client members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Hey there @kubernetes-client/csharp-admins ,

One of the github-admins here. -- We have a longstanding issue on cleaning up outside collaborators, and are now actively planning on removing them on December 1st.

At this point, people that are actively contributing to the Kubernetes project should be promoted to org members, and any repo specific permissions should be managed through their associated configuration in kubernetes/org.

With that in mind, the following people are listed as outside collaborators:

Both @itowlson and @tg123 are active and I'd encourage applying for membership to kubernetes-client org. 😄

If you have any questions or comments, please don't hesitate to ask in here or feel free to poke me in slack 👍

Thanks!

assigning csharp-admins:
/assign @brendanburns @krabhishek8260

/sig contributor-experience
/priority important-soon

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.

@mrbobbytables
Copy link
Author

woops...attempted to assign to wrong brendan burns
/assign @brendandburns

@tg123
Copy link
Member

tg123 commented Oct 29, 2019

Thanks for inviting.
I am happy to join the org

kubernetes/org#1351

@krabhishek8260
Copy link
Contributor

I have replied on the above open issue.

@mrbobbytables
Copy link
Author

Thanks!

@mrbobbytables
Copy link
Author

Permissions have been cleaned up.

@itowlson -- Please go ahead and file for org membership and we can pursue adding you the appropriate groups for repo permissions 👍

If you have any questions, please don't hesitate to reopen or ping me on slack.

Thanks!
/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

Permissions have been cleaned up.

@itowlson -- Please go ahead and file for org membership and we can pursue adding you the appropriate groups for repo permissions 👍

If you have any questions, please don't hesitate to reopen or ping me on slack.

Thanks!
/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
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.
Projects
None yet
Development

No branches or pull requests

5 participants