Difference between revisions of "Community"
m (Carry the site-wide About message) |
m (Fix repository links to the cgit tree/repo URLs) |
||
| Line 4: | Line 4: | ||
'''Chat:''' [https://discord.gg/Rb9K9DYxKK Open-IOV Discord] | '''Chat:''' [https://discord.gg/Rb9K9DYxKK Open-IOV Discord] | ||
'''Source code and issues:''' [https://git.vgpu.io/open-iov git.vgpu.io/open-iov] | '''Source code and issues:''' [https://git.vgpu.io/open-iov.git/ git.vgpu.io/open-iov] | ||
== Contributing == | == Contributing == | ||
Latest revision as of 04:40, 12 October 2026
An absence of critical technical documentation has historically slowed growth and adoption of developer ecosystems for GPU virtualization.
This CC-BY-4.0 licensed content can either be used with attribution, or used as inspiration for new documentation, created by GPU vendors for public commercial distribution as developer documentation.
Where possible, this documentation will clearly label dates and versions of observed-but-not-guaranteed behaviour vs. vendor-documented stable interfaces/behaviour with guarantees of forward or backward compatibility.
Community
Chat: Open-IOV Discord
Source code and issues: git.vgpu.io/open-iov
Contributing
The project welcomes contributors of every kind. The most valuable contribution is evidence: a new hardware or software combination tested with the project's methodology, with the captures listed in the repository's debugging document.
- Start from Hardware and Software Matrix to see which combinations are Reference, Target or Experimental.
- The repository's developer onboarding document describes the environment, the coding standards and how a change is landed.
- For the firmware side, risc-v-gsp-rm-debugger is the host-side workbench; the tool documentation is in the repository.
Editorial policy for this wiki: account creation and editing are closed to prevent spam. The wiki is maintained from the project's tracked documentation by the project's publishing bot; corrections and additions are made through the repository.