[Governance Review]: KServe

[terrytangyuan]

Project Name

KServe

Project Website

https://kserve.github.io/website/latest/

Contact Details 1

@yuzisun

Contact Details 2

@terrytangyuan

Links to communication channels

https://app.slack.com/client/T08PSQ7BQ/C06AH2C3K8B

Reason for governance review request

Other (please specify in the “Additional Notes” input at the end of this form)

Are there any sub-projects, plugins, and related?

Sub-Projects:

• https://github.com/kserve/kserve
• https://github.com/kserve/modelmesh-serving
• https://github.com/kserve/open-inference-protocol
• https://github.com/kserve/models-web-app

Governance model

Technical charter: Project governance doc

We have regular member promotion review cycles every 6 months and have onboarded new reviewers/approvers over the past years.

Process to become a committer: https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/CONTRIBUTING.md#becoming-a-committer

Governance documents

1. Project purpose: https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/KSERVE-TECHICAL-CHARTER.md#1-mission-and-scope-of-the-project
2. Maintainer List (with employer information)

• lizzzcai - SAP
• rachitchauhan43 - Intuit
• sivanantha321 - Idea2IT
• terrytangyuan - Red Hat
• yuzisun - Bloomberg
• andyi2it - Idea2IT
• cmaddalozzo - bloomberg
• Datta0 - Nutanix
• gavrissh - Nutanix
• greenmoon55 - bloomberg
• israel-hdez - Red Hat
• johnugeorge - Nutanix
• Jooho - Red Hat
• spolti - Red Hat

1. How your project is making decisions: https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/KSERVE-TECHICAL-CHARTER.md#3-tsc-voting
2. How and when contributors are moving through the contributor ladder (e.g. becoming a maintainer): https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/CONTRIBUTING.md#becoming-a-committer
3. Maintainer life cycle with information about how and when maintainers are demoted: Currently this is based on discussions and agreement among the maintainers. We are working on improving this process.
4. Code of Conduct: https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/CONTRIBUTING.md#code-of-conduct
5. Contributor Guide: https://github.com/kserve/community/blob/23f78c76d55652a7b86b7237ddb888f092cbc6d1/CONTRIBUTING.md
6. How your community conduct communication and meetings: https://github.com/kserve/community/tree/23f78c76d55652a7b86b7237ddb888f092cbc6d1?tab=readme-ov-file#community-meeting
7. How your community handles security reporting and response: https://github.com/kserve/kserve/blob/070b661b97ad9a9986e7c1b08e7e8da1ee417f44/SECURITY.md
8. Who owns what code and docs: Defined in OWNERS file in each subproject. Example: https://github.com/kserve/kserve/blob/070b661b97ad9a9986e7c1b08e7e8da1ee417f44/OWNERS

Governance Execution Examples

Voting on maintainer promotion: https://cloud-native.slack.com/archives/C06AH2C3K8B/p1725800413961139

PR that adds the promoted maintainers: kserve/kserve#3966

Governance Evolution

No major change yet but we will be working on any gaps identified through this review process.

Any specific aspects of your governance structure are you seeking feedback on?

No response

Do you have any concerns or specific areas where you feel your governance could be improved?

No response

Additional notes and resources

Moving from LF AI & Data Incubating project to CNCF Incubating project.