[ci]: update issue template & security & license

[KMSorSMS]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @KMSorSMS, 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 focuses on enhancing the project's community interaction and legal clarity. It introduces updated and consolidated issue templates for bug reports and feature requests, aiming to streamline the information gathering process. Additionally, it establishes a formal security reporting policy and explicitly includes the Apache License 2.0, providing essential governance and legal documentation. A minor adjustment was also made to the Chinese README to reflect changes in community engagement platforms.

Highlights

• Updated Issue Templates: The English bug report and feature request issue templates have been significantly revamped to include more structured fields, bilingual descriptions, and clearer guidance for users, including links to FAQs and reminders to search existing issues.
• Consolidated Issue Templates: The separate Chinese bug report and feature request templates (-bug2-.yaml and -feature2-.yaml) have been removed, indicating a consolidation into the updated English templates which now feature bilingual content.
• New Security Policy: A new SECURITY.md file has been added, providing clear instructions on how to report security vulnerabilities, directing users to the GitHub Security Advisory feature.
• Added Project License: The project now explicitly includes the Apache License, Version 2.0, in a new LICENSE file, clarifying the terms under which the software can be used and distributed.
• README Update: The Chinese README_ZH.md file has been updated to remove references and links to GitHub Discussions.

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 overhauls the issue templates by merging the English and Chinese versions into unified, more structured forms, and removes the now-redundant separate Chinese templates. Additionally, it introduces a SECURITY.md file to guide users on reporting vulnerabilities and adds an Apache 2.0 LICENSE file. The changes to the issue templates are a great improvement, making the process clearer for users. I've provided a couple of suggestions to re-introduce default title prefixes for better issue tracking and to fix a minor formatting issue in the bug report template.

[gemini-code-assist]

For consistency and easier filtering of issues, it's helpful to have a default title prefix for bug reports. Consider adding the title field back.

labels: ["bug", "pending"]
title: "[Bug] "

[gemini-code-assist]

There are extra spaces around nvidia-smi within the asterisks, which will prevent it from being rendered as bold text. Please remove the spaces for correct Markdown formatting.

        Please share your system info with us. You can run the command **lscpu**, **nvidia-smi** etc. and copy-paste its output below.

[gemini-code-assist]

To maintain consistency across issue types and make them easier to triage, it would be beneficial to add a default title prefix for feature requests. Please consider adding the title field back.

labels: ["enhancement", "pending"]
title: "[Feature] "