KhronosGroup / KhronosGroup/openvx-samples
Please post OpenVX feedback here
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 113
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
The OpenVX working group would like to ask the community for feedback and contributions to make OpenVX more accessible to developers. If you have any requests or suggestions on topics to cover or resources to be developed, please ask them here. If you have a resource to suggest please add an issue or pull request here. We look forward to hearing from you!
The OpenVX Working Group
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
Read the issue and the linked api/openvx/resources.md file first to understand the requested resource topics. Done means proposing concrete OpenVX accessibility feedback or resources through this issue, or submitting a focused issue or pull request for a resource.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100