vllm-project / vllm-project/vllm-project.github.io
Inbound Licence
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 69
- Forks
- 142
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Hi,
Could you clarify what the inbound license for contributing Blogs via this repo?
https://github.com/vllm-project projects appear to be Apache 2.0, including the recipes etc, but I don't see a licence file here. Would you be an able to clarify?
...I'm asking to help with the Arm process for OS contributions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Check this repository for the licence file the issue says is missing, then compare the stated licensing of related vllm-project repositories. Clarify which inbound licence applies to blog contributions and record the answer in the issue or repository documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100