Update docs

[merrymercy]

• Introduce SGLang Code Maintenance Model
• Fix other minor details

[gemini-code-assist]

Summary of Changes

Hello @merrymercy, 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 primarily focuses on updating and improving the project's documentation and internal governance. It introduces a new, more structured code maintenance model to clarify roles and responsibilities, aiming for a more efficient development workflow. Additionally, it refines user-facing documentation, updating information on supported models, community growth, installation procedures, and troubleshooting, while also enhancing issue submission templates for better user experience.

Highlights

• New Code Maintenance Model: A comprehensive SGLang Code Maintenance Model has been introduced, outlining roles such as Area Maintainer, Codeowner, Write, and CI Maintainer, along with their permissions and responsibilities. This model aims to ensure a responsive review process and faster iteration.
• Updated Project Governance: The project's governance structure has been refined by adding a dedicated MAINTAINER.md document and updating the CODEOWNERS file to reflect new responsibilities and streamline the PR merge process. The previous REVIEWERS.md file has been removed, as its functionality is now covered by the new model.
• Improved Issue Templates: The bug report and feature request issue templates have been updated with clearer, more concise descriptions and checklist items to improve the quality and efficiency of issue submissions.
• Documentation Enhancements: Various documentation files have been updated to reflect the latest project status, including expanded model support (e.g., diffusion models), an increased community GPU count (now over 400,000), and updated links to blog posts and social media channels. A new index for popular model usage has also been added.
• Platform and Feature Updates: Installation documentation now includes support for Intel XPU and updated links for NVIDIA DGX Spark. The observability documentation has been expanded to include production request tracing, and the FAQ section has been refined for clarity on deterministic inference.

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 primarily focuses on updating and reorganizing documentation. It introduces a new MAINTAINER.md file that defines the code maintenance model, removes the old REVIEWERS.md, and refactors the documentation structure for popular models. Additionally, issue templates have been streamlined for better usability, and various other documents have been updated to reflect the latest project status. My review includes a suggestion regarding a change in the CODEOWNERS file to ensure new code is always reviewed, and some minor wording improvements for the new maintenance documentation.

[gemini-code-assist]

Removing the wildcard rule /python/sglang/* could be risky. While there are many specific rules for subdirectories, any new file or directory created directly under /python/sglang/ that doesn't match an existing pattern will now have no code owner. This could lead to unreviewed changes slipping through. Consider re-adding a general rule for /python/sglang/* with a default set of owners to act as a fallback.

[gemini-code-assist]

This is a great document explaining the maintenance model! I have a few minor suggestions to improve clarity and grammar:

• Line 24: "...who actively try to help..." could be rephrased to "...who is responsible for helping..." for better clarity on the role's duty.
• Line 26: "Area Maintainer" and "Codeowner" should be pluralized to "Area Maintainers" and "Codeowners" for grammatical correctness.
• Line 30: "@ them" is a bit informal. Consider using "@-mentions them". Also, "auto-request" could be "automatically requests".
• Line 34: The sentence could be rephrased for better flow, for example: "In cases where it is difficult to meet all requirements due to flaky CI or slow responses, an Area Maintainer can bypass branch protection to merge the PR."