[doc] clarify windows support

[youkaichao]

closes #14981

[houseroad]

Looks good. Btw, separate question, do we want to have some bar to promote to a vllm host repo?

[youkaichao]

do we want to have some bar to promote to a vllm host repo?

this is not a vllm hosted repo, it's a fork outside vllm. we just give them some exposure

[houseroad]

Right, I mean do we want to set some bar for the repo owner to get the repo promoted if the repo owner would like to do so.

[youkaichao]

do we want to set some bar for the repo owner to get the repo promoted if the repo owner would like to do so.

We don't have this process right now. if the owner wants to do this, we need to discuss case by case.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀