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

REQUEST: New membership for serbrech #640

Closed
6 tasks done
serbrech opened this issue Mar 21, 2019 · 6 comments · Fixed by #645
Closed
6 tasks done

REQUEST: New membership for serbrech #640

serbrech opened this issue Mar 21, 2019 · 6 comments · Fixed by #645
Assignees
Labels
area/github-membership Requesting membership in a Kubernetes GitHub Organization or Team

Comments

@serbrech
Copy link
Member

GitHub Username

@serbrech

Organization you are requesting membership in

kubernetes
kubernetes-sigs

Requirements

Sponsors

List of contributions to the Kubernetes project

PR reviewed/authored

Issues responded to

SIG projects I am involved with

@serbrech serbrech added the area/github-membership Requesting membership in a Kubernetes GitHub Organization or Team label Mar 21, 2019
@justaugustus
Copy link
Member

+1!

@tariq1890
Copy link
Contributor

+100! Stéphane is a colleague and I can definitely vouch for him. He has been closely involved with cluster-api and cluster-api-provider-azure

@tariq1890
Copy link
Contributor

@mrbobbytables Following up on this :)

@mrbobbytables
Copy link
Member

@tariq1890 I'll get a PR out the door later today :)

@tariq1890
Copy link
Contributor

Thanks!

@mrbobbytables
Copy link
Member

@serbrech thanks for helping out azure cluster api :)
I've created PR #645 to add you to both the @kubernetes and @kubernetes-sigs orgs. Once that gets merged, you should get a membership invite notification.

Welcome to @kubernetes! 🎉

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-membership Requesting membership in a Kubernetes GitHub Organization or Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants