Governance: deprecate Owner role and align Maintainer membership requirements

[Copilot]

The membership policy still required “owners” for maintainer promotion, but Owner was never operationalized in this community. This update removes Owner from governance membership definitions and makes Maintainer eligibility fully maintainer-driven.

• Governance model update

  • Removed the Owner role from community-membership.md (summary table + dedicated section).
  • Keeps role hierarchy aligned with the community’s de facto top-level governance (maintainers).

• Maintainer requirement rewrite

  • Updated Maintainer requirements to:
    • Sponsor from 2 maintainers
    • Nominated by a project maintainer
    • Technical judgment focused on architecture and evolution of Volcano
  • Preserved existing tenure requirement (Approver for at least 2 months).

• Doc quality cleanup

  • Corrected role label typo in the summary table: Reivewer → Reviewer.

• Example (policy diff)

  ### Requirements (Maintainer)
  
  - Sponsor from 2 maintainers
  - Approver for at least 2 months
  - Nominated by a project maintainer
  - Good technical judgement in architecture and evolution of Volcano

• • Updated policy view: https://github.com/user-attachments/assets/b8fb61f3-2155-48e7-ba96-699ce4911402

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Governance] Update community membership requirements</issue_title>
<issue_description>
From the document https://github.com/volcano-sh/community/blob/master/community-membership.md

We can see

Role	Requirements	Responsibilities	Privileges
Member	Sponsor from 2 approvers, active in community, contributed to Volcano	Welcome and guide new contributors	Volcano GitHub organization Member
Reivewer	Sponsor from 2 maintainers, has basic experience and knowledge of domain, actively contributed to code and review	Review contributions from community members	Write access to specific packages in relevant repository
Approver	Sponsor from 2 maintainers, has good experience and knowledge of domain, actively contributed to code and review	Review and approve contributions from community members	Write access to specific packages in relevant repository
Maintainer	Sponsor from 2 owners, shown good technical judgement in feature design/development and PR review	Participate in release planning and feature development/maintenance	Top level write access to relevant repository. Name entry in Maintainers file of the repository
Owner	Sponsor from 3 owners, helps drive the overall Volcano project	Drive the overall technical roadmap of the project and set priorities of activities in release planning	Volcano GitHub organization Admin access

There is a owner role, which can not correctly reflect volcano's operation. We donot see owners' activity, and also can not know who are owners.

So if one want to apply to become maintainer, this current requirement can not be satisfied

Requirements
Sponsor from 2 owners
Approver for at least 2 months
Nominated by a project owner
Good technical judgement in feature design/development

I would suggest we deprecate owner role and update maintainer requirement to

Requirements
Sponsor from 2 maintainers
Approver for at least 2 months
Nominated by a project maintainer
Good technical judgement in architecture and evolution of volcano

</issue_description>

Comments on the Issue (you are @copilot in this section)

@hzxuzhonghu @volcano-sh/volcano-maintainer please take a look, and click 👍 or 👎 @kevin-wangzefeng +1, this document is out of date, we need to fix it.

Maintainers are the de facto top governing body of our community. We never really implemented the "owner" role, and I don't think we really need it.</comment_new>
<comment_new>@william-wang
+1, agree with it.</comment_new>

• Fixes [Governance] Update community membership requirements #112

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from hzxuzhonghu. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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