-
Notifications
You must be signed in to change notification settings - Fork 790
Request: New membership for @ajaysundark #5603
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 @ajaysundark #5603
Conversation
|
Keywords which can automatically close issues and at(@) mentions are not allowed in the title of a Pull Request. You can edit the title by writing /retitle in a comment.
When GitHub merges a Pull Request, the title is included in the merge commit. To avoid invalid keywords in the merge commit, please edit the title of the PR.
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-sigs/prow repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ajaysundark The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @ajaysundark! |
|
Hi @ajaysundark. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
|
/close Please create a github issue instead of PR. Thanks! |
|
@Priyankasaggu11929: Closed this PR. In response to this:
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-sigs/prow repository. |
GitHub Username
@ajaysundark
Organization you are requesting membership in
kubernetes, kubernetes-sigs
Requirements
I have reviewed the community membership guidelines
I have enabled 2FA on my GitHub account
I have subscribed to the kubernetes dev e-mail list
I am actively contributing to 1 or more Kubernetes subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
I have verified that my sponsors are from different member companies
I have verified that my sponsors are a reviewer or an approver in at least one OWNERS file within one of the Kubernetes GitHub organizations (excluding the contributor-playground)
SUGGESTED: Ensure your affiliation in gitdm is up to date (gitdm is used by devstats to track affiliation)
SUGGESTED: Ensure your affiliation in openprofile.dev is up to date (used by LFX Insights to track affiliation, will replace gitdm in the future)
SUGGESTED: I have taken the Inclusive Open Source Community Orientation course
Sponsor 1
@yujuhong
Sponsor 2
@haircommander
List of contributions to the Kubernetes project
KEP:
kubernetes/enhancements#5233
Issues:
kubernetes-sigs/cloud-provider-azure#6342
kubernetes/kubernetes#130960
kubernetes/kubernetes#131169
kubernetes/kubernetes#131208
PR's:
kubernetes/kubernetes#130831
Reviews:
kubernetes/kubernetes#130523
kubernetes/kubernetes#129578