OWNERS: Auto Sync OWNERS files from community membership

[ti-chi-bot]

Check List

Tests

• No need to test

  • I checked and no code files have been changed.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[gemini-code-assist]

Summary of Changes

Hello @ti-chi-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the management of repository ownership by transitioning from explicit user lists in OWNERS files to a more dynamic, alias-based system. It centralizes the definition of approvers and reviewers by referencing community membership, ensuring that ownership information is consistent and automatically updated.

Highlights

• OWNERS File Refactoring: The OWNERS file has been refactored to remove direct listings of individual approvers and reviewers. Instead, it now uses a filters section to dynamically assign sig-community-approvers and sig-community-reviewers aliases for all paths.
• Introduction of Community Aliases: New aliases, sig-community-approvers and sig-community-reviewers, have been introduced in the OWNERS_ALIASES file. These aliases encapsulate the individual members who were previously listed directly in the OWNERS file.
• Centralized Membership Syncing: The ownership definitions are now explicitly noted as being synced from the pingcap/community repository, centralizing and automating the management of approver and reviewer lists.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the OWNERS and OWNERS_ALIASES files to centralize community membership management. By replacing hardcoded lists of approvers and reviewers with aliases synced from the community repository, this change significantly improves maintainability. The changes are clear and well-implemented. I've added a couple of minor suggestions to sort the new alias lists alphabetically to further enhance readability.

[gemini-code-assist]

For better readability and easier maintenance, it's a good practice to keep lists of usernames sorted alphabetically. Please consider sorting this list.

    - 3pointer
    - amyangfei
    - anotherrachel
    - aylei
    - crazycs520
    - dveeden
    - ericsyh
    - glkappe
    - GMHDBJD
    - Joyinqin
    - junlan-zhang
    - KanShiori
    - lucklove
    - lysu
    - ngaut
    - superlzs0476
    - tiancaiamao
    - weekface
    - Yisaer
    - zimulala

[gemini-code-assist]

For better readability and easier maintenance, it's a good practice to keep lists of usernames sorted alphabetically. Please consider sorting this list.

    - breezewish
    - csuzhangxc
    - hfxsd
    - Icemap
    - jackysp
    - kissmydb
    - lance6716
    - lilin90
    - Oreoxmt
    - overvenus
    - qiancai
    - tangenta

[ti-chi-bot]

/release-note-none