Nominate Tiger Kaovilai as a maintainer

[shubham-pampattiwar]

Tiger (@kaovilai) has made significant contributions to the Velero project by enhancing functionality, improving design, and implementing new features. Some of the key contributions include:

• E2E Usability Updates – Refining end-to-end usability for smoother user experience.
• Status Patching Retry Configuration – Designing a configurable mechanism for status patch retries.
• Descriptive Restore Error on Timeout – Providing better error messages when namespaces remain stuck in terminating state.
• Reduction of Indirect Imports – Cutting down ~140 indirect imports for improved performance and cleaner framework integration.
• Backup Status Update on Finalization – Ensuring Backup.Status.CSIVolumeSnapshotsCompleted is correctly updated.
• Timeout Handling for Download Requests – Cancelling download requests gracefully when no download URL is available.
• New Skip Option for Scheduling CLI/API – Adding --skip-immediately to simplify scheduling commands across the CLI/API.
• Restoration Check for Missing GVKs – Preventing restore attempts for resources with missing GroupVersionKind (GVK) in the cluster.

In addition to the above efforts, he is actively driving the investigation and design for Download server for Velero client (https://github.com/vmware-tanzu/velero/issues/6167)

@vmware-tanzu/velero-maintainers, please cast your votes by adding comments to this issue.

[sseago]

+1

[weshayutin]

I appreciate the "thumbs up" all, according the gov doc, we'll need maintainers to vote w/ +1/-1 in comments please. :)

https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#maintainers

Maintainers New maintainers must be nominated by an existing maintainer and must be elected by a supermajority of existing maintainers. Likewise, maintainers can be removed by a supermajority of the existing maintainers or can resign by notifying one of the maintainers.

Supermajority A supermajority is defined as two-thirds of members in the group. A supermajority of Maintainers is required for certain decisions as outlined above. A supermajority vote is equivalent to the number of votes in favor being at least twice the number of votes against. For example, if you have 5 maintainers, a supermajority vote is 4 votes. Voting on decisions can happen on the mailing list, GitHub, Slack, email, or via a voting service, when appropriate. Maintainers can either vote "agree, yes, +1", "disagree, no, -1", or "abstain". A vote passes when supermajority is met. An abstain vote equals not voting at all.

[blackpiglet]

+1

[reasonerjt]

+1

[ywk253100]

+1

[Lyndon-Li]

+1

[shubham-pampattiwar]

+1