Add jschintag to kubevirt members

[jschintag]

GitHub Username

@jschintag

Requirements

• I have reviewed the community code of conduct (https://github.com/kubevirt/kubevirt/blob/master/CODE_OF_CONDUCT.md)
  
• I have enabled 2FA on my GitHub account (https://github.com/settings/security)
  
• I have subscribed to the kubevirt-dev e-mail list (https://groups.google.com/forum/#!forum/kubevirt-dev)
  
• I am actively contributing to KubeVirt
  
• 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 publicly introduced myself to the community through one of the community communication channels
  

(https://github.com/kubevirt/community#socializing)

Sponsors

• @brianmcarey
• @dhiller

List of contributions to the KubeVirt project

• PRs reviewed and/or authored

• Enable building and running kubevirt on s390x kubevirt#10490
• hack/build-go.sh: Use race flag when running go test for individual packages kubevirt#10836
• virt-handler: Fix panic when listing devices on host without USB devices kubevirt#11047
• virt-api: Fix race condition on streamer unit-test kubevirt#11493
• virt-launcher: Refactor/Simplify is<ARCH> functions kubevirt#11602
• add s390x support for kubevirt builder. kubevirt#11097

• Issues responded to

• race detected during execution of test kubevirt#8765

Reason for joining

I am currently working on enabling kubevirt to run on the s390x architecture. For that reason i would like to join the kubevirt org to be able to better maintain the s390x support, as well as general multi-arch support.

Important

After this pull request has been merged, an invitation to the KubeVirt GitHub organization will be automatically sent to the new member. The new member needs to accept the invitation to receive member status.

[kubevirt-bot]

Hi @jschintag. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

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/test-infra repository.

[brianmcarey]

/cc

[dhiller]

/cc

Would happily sponsor you @jschintag

FYI @fabiand

[dhiller]

/approve

/hold for some others to chime in

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dhiller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jschintag]

@dhiller Thank you for sponsoring me, i have added you as a sponsor. I hope you have (had when you read this) a nice vacation.

[victortoso]

+1

[brianmcarey]

/lgtm

[dhiller]

/unhold

@jschintag welcome to the KubeVirt community! 🎉

[jschintag]

/retest

[kubevirt-bot]

@jschintag: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[dhiller]

/retest

You will be allowed to execute this (and other) prow commands after you've accepted the invitation joining the KubeVirt org :)