@tduncan / Nvidia-Optimization-Stack-VLLM Mirror · read-only / commits / 5c86a89805
Fork 0

A high-throughput and memory-efficient inference and serving engine for LLMs

Mirrored from https://github.com/tduncan-lum/Nvidia-Optimization-Stack---VLLM.git

Synced Nov 9, 17:06 UTC

[docs] Update governance process links (#32995)

Signed-off-by: esmeetu <jasonailu87@gmail.com> Signed-off-by: Roger Wang <hey@rogerw.io> Co-authored-by: Roger Wang <hey@rogerw.io>

Roy Wang committed Jan 24, 2026 at 15:32 UTC 5c86a89805ad1f078396b3b400918cc753b4f2a9
1 file changed +49 -28
docs/governance/process.md
+49 -28
@@ -25,34 +25,55 @@ Maintainers form a hierarchy based on sustained, high-quality contributions and
25
26 ### Core Maintainers
27
28 -Core Maintainers function like a project planning and decision making committee. In other convention, they might be called a Technical Steering Committee (TSC). In vLLM vocabulary, they are often known as "Project Leads". They meet weekly to coordinate roadmap priorities and allocate engineering resources. Current active leads: @WoosukKwon, @zhuohan123, @simon-mo, @youkaichao, @robertgshaw2-redhat, @tlrmchlsmth, @mgoin, @njhill, @ywang96, @houseroad, @yeqcharlotte, @ApostaC
29 -
30 -The responsibilities of the core maintainers are:
31 -
32 -* Author quarterly roadmap and responsible for each development effort.
33 -* Making major changes to the technical direction or scope of vLLM and vLLM projects.
34 -* Defining the project's release strategy.
35 -* Work with model providers, hardware vendors, and key users of vLLM to ensure the project is on the right track.
28 +Core Maintainers function like a project planning and decision making committee. In other convention, they might be called a Technical Steering Committee (TSC). In vLLM vocabulary, they are often known as "Project Leads". They meet weekly to coordinate roadmap priorities and allocate engineering resources.
29 +
30 +**Project Leads:**
31 +
32 +- Woosuk Kwon ([@WoosukKwon](https://github.com/WoosukKwon))
33 +- Zhuohan Li ([@zhuohan123](https://github.com/zhuohan123))
34 +- Simon Mo ([@simon-mo](https://github.com/simon-mo))
35 +- Kaichao You ([@youkaichao](https://github.com/youkaichao))
36 +- Robert Shaw ([@robertgshaw2-redhat](https://github.com/robertgshaw2-redhat))
37 +- Tyler Michael Smith ([@tlrmchlsmth](https://github.com/tlrmchlsmth))
38 +- Michael Goin ([@mgoin](https://github.com/mgoin))
39 +- Nick Hill ([@njhill](https://github.com/njhill))
40 +- Roger Wang ([@ywang96](https://github.com/ywang96))
41 +- Lu Fang ([@houseroad](https://github.com/houseroad))
42 +- Ye (Charlotte) Qi ([@yeqcharlotte](https://github.com/yeqcharlotte))
43 +- Yihua Cheng ([@ApostaC](https://github.com/ApostaC))
44 +
45 +**Responsibilities:**
46 +
47 +- Author quarterly roadmap and responsible for each development effort.
48 +- Making major changes to the technical direction or scope of vLLM and vLLM projects.
49 +- Defining the project's release strategy.
50 +- Work with model providers, hardware vendors, and key users of vLLM to ensure the project is on the right track.
51
52 ### Lead Maintainers
53
39 -While Core maintainers assume the day-to-day responsibilities of the project, Lead maintainers are responsible for the overall direction and strategy of the project. A committee of @WoosukKwon, @zhuohan123, @simon-mo, @youkaichao, and @robertgshaw2-redhat currently shares this role with divided responsibilities.
54 +While Core maintainers assume the day-to-day responsibilities of the project, Lead maintainers are responsible for the overall direction and strategy of the project. The following committee currently shares this role with divided responsibilities:
55 +
56 +- Woosuk Kwon ([@WoosukKwon](https://github.com/WoosukKwon))
57 +- Zhuohan Li ([@zhuohan123](https://github.com/zhuohan123))
58 +- Simon Mo ([@simon-mo](https://github.com/simon-mo))
59 +- Kaichao You ([@youkaichao](https://github.com/youkaichao))
60 +- Robert Shaw ([@robertgshaw2-redhat](https://github.com/robertgshaw2-redhat))
61
41 -The responsibilities of the lead maintainers are:
62 +**Responsibilities:**
63
43 -* Making decisions where consensus among core maintainers cannot be reached.
44 -* Adopting changes to the project's technical governance.
45 -* Organizing the voting process for new committers.
64 +- Making decisions where consensus among core maintainers cannot be reached.
65 +- Adopting changes to the project's technical governance.
66 +- Organizing the voting process for new committers.
67
68 ### Committers and Area Owners
69
70 Committers have write access and merge rights. They typically have deep expertise in specific areas and help the community.
71
51 -The responsibilities of the committers are:
72 +**Responsibilities:**
73
53 -* Reviewing PRs and providing feedback.
54 -* Addressing issues and questions from the community.
55 -* Own specific areas of the codebase and development efforts: reviewing PRs, addressing issues, answering questions, improving documentation.
74 +- Reviewing PRs and providing feedback.
75 +- Addressing issues and questions from the community.
76 +- Own specific areas of the codebase and development efforts: reviewing PRs, addressing issues, answering questions, improving documentation.
77
78 Specially, committers are almost all area owners. They author subsystems, review PRs, refactor code, monitor tests, and ensure compatibility with other areas. All area owners are committers with deep expertise in that area, but not all committers own areas.
79
@@ -68,23 +89,23 @@ Any committer can nominate candidates via our private mailing list:
89
90 Committership is highly selective and merit based. The selection criteria requires:
91
71 -* **Area expertise**: leading design/implementation of core subsystems, material performance or reliability improvements adopted project‑wide, or accepted RFCs that shape technical direction.
72 -* **Sustained contributions**: high‑quality merged contributions and reviews across releases, responsiveness to feedback, and stewardship of code health.
73 -* **Community leadership**: mentoring contributors, triaging issues, improving docs, and elevating project standards.
92 +- **Area expertise**: leading design/implementation of core subsystems, material performance or reliability improvements adopted project‑wide, or accepted RFCs that shape technical direction.
93 +- **Sustained contributions**: high‑quality merged contributions and reviews across releases, responsiveness to feedback, and stewardship of code health.
94 +- **Community leadership**: mentoring contributors, triaging issues, improving docs, and elevating project standards.
95
96 To further illustrate, a committer typically satisfies at least two of the following accomplishment patterns:
97
77 -* Author of an accepted RFC or design that materially shaped project direction
78 -* Measurable, widely adopted performance or reliability improvement in core paths
79 -* Long‑term ownership of a subsystem with demonstrable quality and stability gains
80 -* Significant cross‑project compatibility or ecosystem enablement work (models, hardware, tooling)
98 +- Author of an accepted RFC or design that materially shaped project direction
99 +- Measurable, widely adopted performance or reliability improvement in core paths
100 +- Long‑term ownership of a subsystem with demonstrable quality and stability gains
101 +- Significant cross‑project compatibility or ecosystem enablement work (models, hardware, tooling)
102
103 While there isn't a quantitative bar, past committers have:
104
84 -* Submitted approximately 30+ PRs of substantial quality and scope
85 -* Provided high-quality reviews of approximately 10+ substantial external contributor PRs
86 -* Addressed multiple issues and questions from the community in issues/forums/Slack
87 -* Led concentrated efforts on RFCs and their implementation, or significant performance or reliability improvements adopted project‑wide
105 +- Submitted approximately 30+ PRs of substantial quality and scope
106 +- Provided high-quality reviews of approximately 10+ substantial external contributor PRs
107 +- Addressed multiple issues and questions from the community in issues/forums/Slack
108 +- Led concentrated efforts on RFCs and their implementation, or significant performance or reliability improvements adopted project‑wide
109
110 ### Working Groups
111