update-gvisor-maintainers
Update the gVisor maintainer roster in governance/maintainers.yaml or the specialization areas in governance/areas.yaml, and regenerate the files derived from them (MAINTAINERS.md and CODEOWNERS). Use when a maintainer goes on hiatus, returns from hiatus, is added, steps down to emeritus, changes employer or specialization, or when MAINTAINERS.md / CODEOWNERS are out of sync.
- License 许可
- Apache-2.0
- 所属仓库
- google/gvisor
- 最近更新
- 2026-11-15
- Stars
- ★ 2.0w
- Forks
- 2.1k
01 前言 Front Matter
- name
- update-gvisor-maintainers
- description
- Update the gVisor maintainer roster in governance/maintainers.yaml or the specialization areas in governance/areas.yaml, and regenerate the files derived from them (MAINTAINERS.md and CODEOWNERS). Use when a maintainer goes on hiatus, returns from hiatus, is added, steps down to emeritus, changes employer or specialization, or when MAINTAINERS.md / CODEOWNERS are out of sync.
03 SKILL.md 正文
Update the gVisor maintainer roster
governance/maintainers.yaml (the roster) and governance/areas.yaml
(specialization areas) are the sources of truth. Reviewer assignment and the Go
generator read the same area data. The generator produces MAINTAINERS.md and
CODEOWNERS. Edit the source data, regenerate, and run the comparison tests. Do
not hand-edit generated files.
Schema
Each entry under maintainers::
- name: Gee Vaïzaur # Full name or nickname.
github: gvaizaur # GitHub username.
github_id: 123456789 # GitHub user ID.
affiliation: Independent # Current employer, or "Independent".
past_affiliation: # Optional.
- affiliation: Arasaka Corporation
until: 2025-03-01
started: 2018-05-08 # First contribution. The list is sorted by this.
status: HIATUS_SINCE:2026-07-17
areas: [gpu, networking] # Optional. Sorted area names from areas.yaml;
# grants CODEOWNERS ownership of the paths of
# areas with enforced_review. Not for emeritus.
Each entry under areas: in areas.yaml:
- name: gpu # Sorted by name.
enforced_review: false # Required. `true` generates a CODEOWNERS
# section for the area, making
# specialized-maintainer review mandatory.
# Needs at least one non-emeritus maintainer
# with the area.
paths: # Repo-root-relative dirs (/like/this), no
- /images/gpu # trailing slash. Each path in one area only.
status is one of three, and it drives everything downstream:
| Status | Reviews | Merge permissions | MAINTAINERS.md |
|---|---|---|---|
ACTIVE |
yes | yes | main table |
HIATUS_SINCE:YYYY-MM-DD |
no | yes | main table |
EMERITUS_SINCE:YYYY-MM-DD |
no | no | emeritus table |
The review-assignment workflow reads the roster directly and selects only active maintainers. Hiatus affects review assignment, not merge permissions or membership in the main maintainer table.
Common changes
Most of these are a one-line status: edit on an existing entry:
- Goes on hiatus:
status: HIATUS_SINCE:<today>. - Comes back from hiatus:
status: ACTIVE. Drop the date;ACTIVEnever carries one. - Steps down, or hits 12 months of inactivity:
status: EMERITUS_SINCE:<date>. - Comes back from emeritus:
status: ACTIVE, but only through the normal nomination process. See "Becoming a maintainer" inGOVERNANCE.md.
The two that are not:
- New maintainer: insert the entry in
startedorder, not at the end of the file. Look upgithub_idrather than guessing it. - Changed employer: update
affiliation, and move the old one topast_affiliationwith the date it ended asuntil.
Dates are real calendar dates, so go look up today's date rather than guessing at one. If the user gave you a date, use theirs.
After any change, regenerate.
Regenerate
make governance-regen
This regenerates both files in place.
Then:
make governance-check
This fails if the source data changed and you forgot to regenerate, or if someone edited a generated file by hand.
Before handing back
Show the user the diff across all changed files (governance/maintainers.yaml,
governance/areas.yaml, MAINTAINERS.md, CODEOWNERS) and let them confirm
the roster reads the way they meant it to.
If a generated file contains something the generator does not emit, that content is drift, and regenerating is what removes it. Do not teach the generator to reproduce it without asking first: the generator decides what those files contain, not whatever happened to be committed.
04 同仓库更多 Skills
gvisor-performance
Use when modifying gVisor in ways with potential performance implications; as a kernel, gVisor's performance matters almost as much as its security. Load imperatively when editing this performance-sensitive code: * Syscall hot path: `pkg/sentry/kernel` (`task_run.go`, `task_syscall.go`), `pkg/sentry/syscalls/linux`, and app-memory copy layers (`pkg/usermem`, `pkg/safemem`, `pkg/safecopy`, `pkg/marshal`). * Platform: `pkg/sentry/platform`, `pkg/ring0`. * Sandbox startup: `runsc/boot`, `runsc/container`, `runsc/sandbox`. * Serialization and checkpoint/restore: `pkg/state`, `pkg/sentry/state`. * Netstack: `pkg/tcpip`. * File I/O: `pkg/sentry/vfs`, `pkg/sentry/fsimpl`. * Memory management: `pkg/sentry/mm`, `pkg/sentry/pgalloc`. * Gofer IPC: `pkg/lisafs`, `runsc/fsgofer`. * Go `init()` functions, which run on every binary startup. Also load for any change with potential performance impact, even outside these paths.
gvisor-kernel-development
Use when modifying gVisor application kernel behavior: adding a new system call, adding new flags to an existing system call, editing the syscall tests in `//test/syscalls`.