Request to be an Reviewer of Volcano community

[JesseStutler]

I'm requesting to be an reviewer of Volcano community. My major contributions include scheduling feature development, core issue fixing, CI project maintenance, feature research, and performance testing/analysis. I have opened 20 PRs, 14 issues and reviewed 27 PRs. The detailed contributions are as follows:
Features:

• done:
  • feature:add preemptionpolicy in preempt and reclaim volcano#3739
  • feature: Add podgroups statistics volcano#3751
  • feature: add approve workflows action volcano#3758
  • Move GetAncestors as HyperNodeInfoMap method and provide GetLCAHyperNode volcano#3969
  • Add hypernodes validation webhook configuration yaml volcano#3974
  • Add PULL_REQUEST_TEMPLATE.md volcano#3942
• ongoing:
  • feature: Add dynamic resource allocation(DRA) plugin volcano#3799
  • [WIP]feature: Create hyperNode cr by node label volcano#3890

BugFix:

• fix: not remove podgroup uid will cause topology annotation to be useless volcano#3711
• fix: volumeZone and podTopologySpread don't work if nodeVolumeLimits is enabled volcano#3727
• fix ci and add event logging to help debug ci volcano#3817
• fix: if the capability cpu or memory is not specified in the hierarchical queue, it will be set to the corresponding value of the parent queue volcano#3917
• fix: hierarchical queue webhook validation use listing podgroups instead volcano#3913
• reclaim: When choosing a preemptor, choose a starving one rather than one with pending tasks. volcano#3951

Now I am confident to become a reviewer of volcano and look forward to contributing more to Volcano! Thanks!

[JesseStutler]

PTAL, thank you @Monokaix @wangyang0616 @archlitchi @hwdef @lowang-bh @william-wang @kevin-wangzefeng

[Monokaix]

+1
Thanks for your great contribution!

[hwdef]

+1
Strongly support

[kevin-wangzefeng]

+1 to adding @JesseStutler as reviewer

[Monokaix]

/close

[volcano-sh-bot]

@Monokaix: Closing this issue.

In response to this:

/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.