How to become a collaborator/reviewer/developer

[Kkaiwz]

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

[marty-johnson59]

Hi @Kkaiwz, first of all, thank you for your contributions! If you are not currently a Khronos member (or working for a company that is), then I think the way you're currently contributing is probably the best approach. Submitting issues for problems you see definitely gets those on our radar to address...and creating PRs is a great way to have a direct impact. To get more tightly engaged with the Khronos Samples team, you'd need to become a Khronos member which gets you access to our internal resources and ability to join team meetings. See https://www.khronos.org/members/ for the available options. Unfortunately, all these imply an annual fee. There is also a way to become an individual contributor, but there is a pretty high bar for that (including both Vulkan Working Group and Khronos Board-level approvals - not something they take lightly..). It very much helps if you're already working with others who can provide supportive recommendations. Do you have regular engagements with folk working on Vulkan on your Linux/Mali efforts that would be willing to help with recommendations? If so, I can start some internal dialog on exploring that path.

[Kkaiwz]

Hi @marty-johnson59, thanks for your detailed explanation and help. I'm working for NXP which is the contributor member of KHRONOS (https://www.khronos.org/members/list/).
The signed-off-by email of commit which i used is my nxp email: ryan.zhang@nxp.com.

[marty-johnson59]

Excellent. In that case, just subscribe to Vulkan Developer Relations on Causeway to see our meetings in the Causeway calendar. Feel free to join us on alternate Mondays (8am PT) - we'd welcome your participation!