OWNERS: Auto Sync OWNERS files from community membership (#67717)

[ti-chi-bot]

This is an automated cherry-pick of #67717

Check List

Tests

• No need to test

  • I checked and no code files have been changed.

Summary by CodeRabbit

• Chores
  • Updated project governance and ownership documentation structure.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 92c51836-f1ea-40b5-8534-8925b45111e0

📥 Commits

Reviewing files that changed from the base of the PR and between adc727d and 8347090.

📒 Files selected for processing (2)

• OWNERS
• OWNERS_ALIASES

---

📝 Walkthrough

Walkthrough

OWNERS and OWNERS_ALIASES governance metadata files are updated with refreshed documentation references, reorganized approver and reviewer rosters with user additions and removals, and consolidated comment formatting across alias entries.

Changes

Governance metadata

Layer / File(s)	Summary
OWNERS approvers and reviewers OWNERS	OWNERS documentation URL updated with sig-community-* sync note. Approvers list reordered and expanded with new usernames (joechenrh, nolouch, rleungx, terry1purcell, wlwilliamx). Reviewers list adjusted with additions (Tristan1900, gengliqi, henrybw, wddevries) and removals (JmPotato, nolouch, rleungx, terry1purcell, TszKitLo40).
OWNERS_ALIASES documentation and aliases OWNERS_ALIASES	Header comment updated to reference OWNERS documentation and note sig-community-* synchronization. Inline module comments removed from sig-approvers-* alias keys while preserving member lists and key structure.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• pingcap/tidb#67717: Both PRs update the same OWNERS/OWNERS_ALIASES metadata files with overlapping approver and reviewer username changes including joechenrh, nolouch, rleungx, terry1purcell, wlwilliamx, Tristan1900, gengliqi, henrybw, and wddevries.

Suggested labels

cherry-pick-approved, release-note-none, skip-issue-check

Poem

🐰 The governance grows and evolves with care,
Approvers shuffled here and there,
Comments trimmed to keep it clean,
Community sync—a well-oiled machine!
Metadata dancing in perfect array,
Code review blessed on this fine day. 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description omits critical required sections including problem statement, issue number, change explanation, and release notes despite the template requiring them.	Add the missing required sections: a problem statement with issue number, detailed explanation of changes, and release notes if applicable. Reference the PR description template for required format.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change as an automated sync of OWNERS files from community membership, which matches the PR's primary objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[windtalker]

lgtm

[windtalker]

/release-note-none

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: windtalker, wshwsh12

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [windtalker,wshwsh12]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-05-28 07:40:40.933802583 +0000 UTC m=+510710.903967646: ☑️ agreed by windtalker.
• 2026-05-28 07:43:36.637828205 +0000 UTC m=+510886.607993262: ☑️ agreed by wshwsh12.