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 @harshanarayana #3683

Closed
9 tasks done
harshanarayana opened this issue Sep 13, 2022 · 5 comments · Fixed by #3684
Closed
9 tasks done

REQUEST: New membership for @harshanarayana #3683

harshanarayana opened this issue Sep 13, 2022 · 5 comments · Fixed by #3684
Labels
area/github-membership Requesting membership in a Kubernetes GitHub Organization or Team

Comments

@harshanarayana
Copy link
Contributor

harshanarayana commented Sep 13, 2022

GitHub Username

@harshanarayana

Organization you are requesting membership in

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)
  • OPTIONAL: I have taken the Inclusive Open Source Community Orientation course

Sponsor 1

@ramrodo

Sponsor 2

@leonardpahlke

List of contributions to the Kubernetes project

Part of Kubernetes Release team v1.26 (Release Notes Shadow)

PRs reviewed/authored

  1. multi-cluster workflow: add example of multi cluster test workflow kubernetes-sigs/e2e-framework#157
  2. client-go: Modify FakeEvents to Work Event Sink started with "" namespace kubernetes#110649
  3. GIT-110239: fix activeDeadlineSeconds enforcement bug kubernetes#110294
  4. job_controller: refactor job controller to be able to inject FakeClock for UTs kubernetes#110710
  5. 🌱 GIT-2731: enable TokenRequest for ServiceAccount token generation kubernetes-sigs/kubebuilder#2733
  6. multi-cluster workflow: add example of multi cluster test workflow kubernetes-sigs/e2e-framework#157
  7. GIT-141: enable panic handlers for ensuring Finish Steps kubernetes-sigs/e2e-framework#143
  8. GIT-119: handle scoping for parallel tests kubernetes-sigs/e2e-framework#120
  9. GIT-112: enable framework specific fail-fast mode kubernetes-sigs/e2e-framework#118
  10. GIT-60: enable helper function for conditional waits kubernetes-sigs/e2e-framework#73

Sig projects I'm involved in

@harshanarayana harshanarayana added the area/github-membership Requesting membership in a Kubernetes GitHub Organization or Team label Sep 13, 2022
@leonardpahlke
Copy link
Member

+1, I think you don't need to create this issue to join K8s-sigs if you are already K8s member - you can just add yourself :)

@leonardpahlke
Copy link
Member

@leonardpahlke
Copy link
Member

leonardpahlke commented Sep 13, 2022

@mrbobbytables perhaps we could update the documentation to highlight that being a K8s member does not require sponsorship to join other K8s organizations? I could add a note to the issue template - WDYT?

@mrbobbytables Does this apply the other way around, if you are a K8s-sigs member, you don't need sponsorship for the K8s organization?

@harshanarayana
Copy link
Contributor Author

Thanks @leonardpahlke I've opened a PR to do the same.

@palnabarun
Copy link
Member

@leonardpahlke -- Membership of any orgs grants implicit rights to be part of the other orgs. So, both cases that you enumerate hold true.

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.

3 participants