Maintainers

The official ownership model is defined in OWNERS files scattered throughout the repo. Each OWNERS references shared SIG (Special Interest Group) approver/reviewer lists synchronised from the pingcap/community repository, so the in-tree files don't list individuals directly. The root OWNERS is:

filters:
  go\.mod$:
    approvers:
      - sig-critical-approvers-dep
  .*:
    approvers:
      - sig-community-approvers
    reviewers:
      - sig-community-reviewers

Subsystem-specific approver groups (e.g., sig-planner, sig-storage) are referenced from deeper OWNERS files such as pkg/planner/OWNERS, pkg/parser/OWNERS, pkg/ddl/OWNERS, etc. Membership is managed at https://github.com/pingcap/community.

For day-to-day "who has been touching this code lately" the most useful lens is git history. Below is a snapshot from git log --since="90 days ago" against master, filtered to non-bot accounts.

Recent active human contributors (last 90 days)

Author	Commits (90d)
Weizhen Wang	65
D3Hunter	53
Dongpo Liu	27
tpp	24
Yuanjia Zhang	22
Arenatlx	17
Yiding Cui	16
Rossi Sun	16
guo-shaoge	12
GMHDBJD	12
wjHuang	11

Around 75 humans committed to master in the last 90 days (raw count after filtering out the visible bots Ti Chi Robot, ti-srebot, pingcap-github-bot, and flaky-claw).

All-time top committers (raw, includes bots)

Author	Commits (all)
Ti Chi Robot	4,089
ti-srebot	2,020
Weizhen Wang	1,819
tiancaiamao	1,663
Ewan Chou	1,097
Yuanjia Zhang	1,084
crazycs	849
pingcap-github-bot	808
Lynn	701
tangenta	662

Ti Chi Robot, ti-srebot, and pingcap-github-bot are project bots that handle cherry-picks, mergebot autolands, and auto-generated cleanup commits. flaky-claw is the flaky-test triage bot. They are intentionally not contact points; if you need a human, look at the recent-90-day list above or run git log --no-merges --pretty=format:"%aN" -- <path> for the file you're touching.

How to find owners for a specific path

# nearest OWNERS file
find . -name OWNERS -path "*<path>*" 2>/dev/null
# recent committers on a path
git log origin/master --since="6 months ago" --pretty=format:"%aN" -- <path> | sort | uniq -c | sort -rn | head

The wiki skill recommends querying origin/master (or origin/dev) when deriving contributors so feature-branch noise doesn't skew the result.

Communication channels

Documented in the project README:

• Discord — https://discord.gg/KVRZBR2DrG.
• Slack (English) — https://slack.tidb.io/invite?team=tidb-community&channel=everyone.
• Slack (Japanese) — https://slack.tidb.io/invite?team=tidb-community&channel=tidb-japan.
• Stack Overflow — https://stackoverflow.com/questions/tagged/tidb.
• Chinese forum — https://asktug.com.
• X — @PingCAP.

Bug reports and feature requests go through GitHub Issues at https://github.com/pingcap/tidb/issues.