KhronosGroup / KhronosGroup/Vulkan-Samples
How to become a collaborator/reviewer/developer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5.4k
- Forks
- 835
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
Hi Vulkan-Samples developer team,
I would like to ask about the process for becoming a collaborator, reviewer, or developer for the Vulkan-Samples project.
I am currently working mainly in the Linux + Mali GPU + Wayland/Weston development environment, and I have already had five commits merged into Vulkan-Samples.
I would like to get more deeply involved in the maintenance of Vulkan-Samples, especially in improving the quality, compatibility, and stability of Vulkan-Samples on the Wayland/Weston window system.
Could you please let me know whether there is a formal process for becoming a collaborator/reviewer/developer, or if there are any specific requirements or next steps I should follow?
Thanks,
Ryan
Contributor guide
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
No files, tests, or entry points are mentioned. Start by finding the project's process for becoming a collaborator, reviewer, or developer; done means the requirements and next steps are clearly stated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100