[docs]: add maintainers list

[chenht2022]

What does this PR do?

Add maintainers list

Fixes # (issue)

Before submitting

• Did you read the contributor guideline?
• Did you write any new necessary tests?

[gemini-code-assist]

Summary of Changes

Hello @chenht2022, 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 introduces a new MAINTAINERS.md file to enhance project governance and transparency. It clearly defines who the project maintainers are, what their duties entail, and the process for new contributors to join the maintainer team, thereby improving structure for project stewardship.

Highlights

• New MAINTAINERS.md file: A new MAINTAINERS.md file has been added to the repository, establishing formal documentation for project stewardship.
• Maintainer Listing: The document includes a comprehensive list of current project maintainers, detailing their names, GitHub profiles, roles, affiliations, and contact emails.
• Defined Responsibilities: Clear responsibilities for maintainers are outlined, covering areas such as pull request reviews, issue triage, upholding the code of conduct, maintaining CI reliability, overseeing releases, and protecting project security.
• Path to Becoming a Maintainer: Guidelines are provided for contributors interested in becoming maintainers, emphasizing sustained, high-quality contributions and collaborative behavior.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• MAINTAINERS.md
  • Initial creation of the MAINTAINERS.md file.
  • Added a table enumerating current maintainers with their details (Name, GitHub, Role, Affiliation, Email).
  • Documented the key responsibilities of project maintainers.
  • Included a section on the process for becoming a maintainer.

Activity

• The author included a 'Before submitting' checklist in the PR description, indicating initial self-review steps.

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 adds a MAINTAINERS.md file, which is a valuable addition for clarifying project governance and recognizing key contributors. The file is well-structured. My review includes one suggestion to protect the maintainers' email addresses from spam bots, offering a couple of ways to address this potential privacy concern.

[gemini-code-assist]

Publishing raw email addresses in a public repository can expose maintainers to spam from web crawlers. To protect their privacy, I'd suggest one of two options:

1. Obfuscate the email addresses: For example, you could replace @ with [at] and . with [dot] (e.g., xwy21 [at] mails.tsinghua.edu.cn).
2. Remove the email column: You could remove the email column entirely and update the 'Becoming a Maintainer' section to direct interested contributors to open a GitHub issue or use another official communication channel.

[Copilot]

Pull request overview

This PR adds a new MAINTAINERS.md file to document the project's maintainers and their responsibilities. The file provides transparency about project governance and creates a clear path for contributors to become maintainers.

Changes:

• Adds MAINTAINERS.md with a table listing 10 maintainers from MADSys Lab @ Tsinghua University and Approaching.AI
• Documents maintainer responsibilities including PR review, issue triage, CI maintenance, and security oversight
• Provides guidance on how contributors can become maintainers

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.