support file

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at love@v2ray.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/SUPPORT.md

@@ -0,0 +1,66 @@
+# V2Ray 用户支持 (User Support)
+
+**English reader please skip to the English section below**
+
+## 获得帮助信息的途径
+
+您可以从以下渠道获取帮助：
+
+1. 官方网站：[v2ray.com](https://www.v2ray.com)
+1. Github：[Issues](https://github.com/v2ray/v2ray-core/issues)
+1. Telegram：[主群](https://t.me/projectv2ray)
+
+## Github Issue 规则
+
+1. 请按模板填写 issue；
+1. 配置文件内容使用格式化代码段进行修饰（见下面的解释）；
+1. 在提交 issue 前尝试减化配置文件（如下）：
+  * 删除不必要 inbound / outbound 模块；
+  * 删除不必要的路由项；
+1. 在提交 issue 前尝试确定问题所在，比如：
+  * 将 socks 代理换成 http 再次观察问题是否能重现；
+  * 更改加密方式再次观察问题是否能重现；
+1. 配置文件必须结构完整，即除了必要的隐私信息之外，配置文件可以直接拿来运行。
+
+**不按模板填写的 issue 将直接被关闭**
+
+## 格式化代码段
+
+在配置文件上下加入 Markdown 特定的修饰符，如下：
+
+\`\`\`javascript
+{
+  // 配置文件内容
+}
+\`\`\`
+
+## Way to Get Support
+
+You may get help in the following ways:
+
+1. Office Site: [v2ray.com](https://www.v2ray.com)
+1. Github: [Issues](https://github.com/v2ray/v2ray-core/issues)
+1. Telegram: [Main Group](https://t.me/projectv2ray)
+
+## Github Issue Rules
+
+1. Please fill in the issue template.
+1. Decorate config file with Markdown formatter (See below).
+1. Try to simplify config file before submitting the issue, such as:
+  * Removing unnecessary inbound / outbound blocks.
+  * Removing unnecessary routing rules.
+1. Try to determine the cause of the issue, for example:
+  * Replacing socks inbound with http inbound to see if the issue still exists.
+  * Changing encryption methods to see if the issue still exists.
+
+**Any issue not following the issue template will be closed immediately.**
+
+## Code formatter
+
+Add the following Markdown decorator to config file content:
+
+\`\`\`javascript
+{
+  // config file
+}
+\`\`\`