Nominating @jmhbnz as etcd reviewer

[serathius]

Who would you like to nominate?

I would like to propose @jmhbnz for role of reviewer.

@jmhbnz has showed contributions and leadership exceeding expectations for etcd reviewer. He is leading the whole effort for improving etcd continuous integration and ARM64 support.

He was crucial in organizing etcd presense during KubeCon, by proposing work and couching new contributors during ContribFest session and staffing the etcd booth.

He reviewed over 200 PRs and merged over 50.

He is participating both in technical part of the project by being the third most active contributor to etcd and organizational part by participating and helping organise the etcd community meetings.

He authored the etcd triage instructions and are still are actively triaging and helping community.

Requirements

• I have reviewed the community membership guidelines
• The members are actively contributing to 1 or more etcd subprojects
• The members are being sponsored by two current reviewers or a current maintainer.

How do the new members meet the regular active contribution requirements?

• member for at least 3 months. Joined April 7th
• Primary reviewer for at least 5 PRs to the codebase.
  • Add -failfast flag when the mode is fail_fast #15790
  • tests/robustness: Validate all etcd watches opened to etcd #15893
  • tests/robustness: Expect revisions to be unique for Kubernetes Traffic #15909
  • ci: add fix-yamllint rule in Makefile #15966
  • tests/robustness: Extract validation to separate package #16066
  • release-3.5: Tests-arm64 and e2e-arm64 #16097
  • Add e2e-arm64.yaml and Tests-arm64.yaml to release-3.5 #16119
  • build(deps): bump github/codeql-action from 2.20.0 to 2.20.1 #16146
• Reviewed or contributed at least 20 substantial PRs to the codebase.
  • Adjust time resolution to microseconds #15239
  • Add initial .devcontainer for go 1.19 #15383
  • [3.4] Backport tls 1.3 support #15486
  • Remove e2e from coverage calculation #15544
  • tests: Add new test for round robin resolver #15577
  • tests: Ensure healthy cluster before and after robustness failpoint #15604
  • Add issue template for new membership nominations. #15713
  • Initial re-write for contributor issue triage guide #15881
  • Run robustness tests on arm64 #15886
  • Ensure arm64 runners start with a clean checkout #15890
  • [2023-05-16] Bump dependencies identified by dependabot #15904
  • Add example format for initial-cluster in configuration file #15938
  • Strengthen etcd support policy in issue triage docs #15957
  • Promote etcd frequently asked questions in our bug report template and readme #16003
  • Documenting etcd infrastructure and establish basic controls #15998
  • Document new arm64 infra process #16087
  • Document steps for setting up new arm64 self hosted actions runner #16116
  • Templated arm64 integration and e2e workflows for main and release-3.5 #16152
  • Update community meeting frequency to fortnightly #16189
• Knowledgeable about the codebase.
  • @jmhbnz is the go to person for etcd continuous integration infrastructure and ARM64 support
  • @jmhbnz defined the etcd triage policy
• Sponsored by two active maintainers.
  • @serathius, Google
  • @ahrtr, VMware
  • Sponsors must be from multiple member companies to demonstrate integration across community.

[serathius]

cc @ahrtr @ptabor @wenjiaswe @mitake @spzala

[ahrtr]

Thanks @jmhbnz for your great contribution. Also congratulations!

[jmhbnz]

Wow thanks team, this is wonderful news!

Absolutely looking forward to continued contribution and learning, thanks for your support! 🙏🏻

[serathius]

With both sponsors LGTM I'm closing as accepted.

@jmhbnz Can you send PR to add yourself in https://github.com/etcd-io/etcd/blob/main/MAINTAINERS ?

[spzala]

+1 @jmhbnz thanks for your active role and great contributions! Congratulations!

[wenjiaswe]

Woohooo! Well deserved! Congratulations!

[BobyMCbobs]

Woohoo! Great work and congradulations @jmhbnz!