Maintainers

Subsystem ownership map. Two data sources:

• CODEOWNERS at the repo root — explicit ownership for a small number of subdirectories.
• Recent git history — the most-active human contributors per area in the last year.

Bot identities (A. Unique TensorFlower, TensorFlower Gardener, dependabot[bot]) are excluded from contributor lists — these are automation accounts. See by-the-numbers and fun-facts.

CODEOWNERS-declared owners

From CODEOWNERS:

Subsystem	Official owner(s)
tensorflow/c/eager/	@qqfish
tensorflow/core/common_runtime/eager/	@qqfish
tensorflow/core/debug/ (typo'd tenosrflow)	@caisq
tensorflow/core/kernels/mkl/	@penpornk
tensorflow/core/kernels/sparse/	@penpornk
tensorflow/core/nccl/	@azaks2, @chsigg
tensorflow/python/autograph/	@mdanatg
tensorflow/python/debug/	@caisq
tensorflow/python/eager/	@rohan100jain
tensorflow/tools/docs/	@markdaoust
tensorflow/compiler/mlir/	@aminim
tensorflow/core/ir/	@aminim
tensorflow/core/transforms/	@aminim
third_party/systemlibs/	@perfinion

The CODEOWNERS file is short; many subsystems have no declared owner. For those, fall back to recent contributors below.

Recent contributors by area (git log)

Active human contributors (last ~12 months, top names per area) — derived from git log excluding bot accounts. Names are intended as starting points to find a reviewer; the actual reviewer is often assigned automatically by the PR triage pipeline.

Area	Recent contributors (sample)
tensorflow/compiler/ (XLA bridge / MLIR)	Eugene Zhulenev, Adrian Kuegel, Alexander Belyaev, Henning Becker, Sohaib Iftikhar, Mikhail Goncharov
tensorflow/core/kernels/	Penporn Koanantakool (penpornk), various across kernel families
tensorflow/lite/	Variety; no single dominant author
tensorflow/python/keras/ (legacy)	Largely Copybara'd from internal — Keras 3 is the active project in keras-team/keras
tensorflow/python/autograph/	@mdanatg
tensorflow/python/eager/	@rohan100jain and team
tensorflow/python/distribute/	Various; coordinate with comp:dist-strat triagers
tensorflow/dtensor/	DTensor team (mostly internal)
tensorflow/compiler/tf2tensorrt/	NVIDIA-affiliated contributors
tensorflow/core/distributed_runtime/	Mostly internal; see PRs with comp:dist-runtime

Most external PRs land via Copybara into Google's internal repo and back, so git blame on master will frequently point at A. Unique TensorFlower rather than a person. Open the GitHub PR linked in the commit body to find the human contributor.

How to find a reviewer for a PR

1. Look at the subdirectory of your change.
2. Check CODEOWNERS (the table above is the full content).
3. If no owner: open the PR — the triage bot will apply a comp:* label, and a maintainer for that component will be auto-assigned.
4. Ping @tensorflow/jaxs-people or area teams as referenced in CONTRIBUTING.md if you don't get a response in two weeks.

Why this list is short

The repo is overwhelmingly developed by Google internally. A formal CODEOWNERS for every directory has not been maintained because internal review rules already cover the same ground. For external contributors, the right starting point is the comp:* label system plus the GitHub Issues area. See how-to-contribute/development-workflow.