A high-throughput and memory-efficient inference and serving engine for LLMs
Mirrored from https://github.com/tduncan-lum/Nvidia-Optimization-Stack---VLLM.git
Synced Nov 16, 00:45 UTC
[Doc] Deprecate Discord (#12668)
Zhuohan Li committed
Feb 2, 2025 at 19:19 UTC
326fcc8b9f1d75a9f194581c98a7994d220c5255
2 files changed
+3
-4
CODE_OF_CONDUCT.md
+1
-1
@@ -61,7 +61,7 @@ representative at an online or offline/IRL event.
61
62
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63
reported to the community leaders responsible for enforcement in the #code-of-conduct
64
-channel in the [vLLM Discord](https://discord.com/invite/jz7wjKhh6g).
64
+channel in the [vLLM Slack](https://slack.vllm.ai).
65
All complaints will be reviewed and investigated promptly and fairly.
66
67
All community leaders are obligated to respect the privacy and security of the
README.md
+2
-3
@@ -10,7 +10,7 @@ Easy, fast, and cheap LLM serving for everyone
10
</h3>
11
12
<p align="center">
13
-| <a href="https://docs.vllm.ai"><b>Documentation</b></a> | <a href="https://vllm.ai"><b>Blog</b></a> | <a href="https://arxiv.org/abs/2309.06180"><b>Paper</b></a> | <a href="https://discord.gg/jz7wjKhh6g"><b>Discord</b></a> | <a href="https://x.com/vllm_project"><b>Twitter/X</b></a> | <a href="https://slack.vllm.ai"><b>Developer Slack</b></a> |
13
+| <a href="https://docs.vllm.ai"><b>Documentation</b></a> | <a href="https://vllm.ai"><b>Blog</b></a> | <a href="https://arxiv.org/abs/2309.06180"><b>Paper</b></a> | <a href="https://x.com/vllm_project"><b>Twitter/X</b></a> | <a href="https://slack.vllm.ai"><b>Developer Slack</b></a> |
14
</p>
15
16
---
@@ -139,8 +139,7 @@ If you use vLLM for your research, please cite our [paper](https://arxiv.org/abs
139
## Contact Us
140
141
* For technical questions and feature requests, please use Github issues or discussions.
142
-* For discussing with fellow users, please use Discord.
143
-* For coordinating contributions and development, please use Slack.
142
+* For discussing with fellow users and coordinating contributions and development, please use Slack.
143
* For security disclosures, please use Github's security advisory feature.
144
* For collaborations and partnerships, please contact us at vllm-questions AT lists.berkeley.edu.
145