[SBIN] Define code-owners for cuvs_c headers
Open
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Determine an initial set of developers trusted to be cuvs_c abi code-owners. They will be responsible for the review, and approval of changes to all header files within the cuvs_c component.
- Create cuvs_c_header code owner group with ops
- Setup the github codeowner logic to be public C header
- Ensure the developers have read the ABI documentation we have generated
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
Start by locating the cuvs_c public C headers and the repository's GitHub code-owner configuration, then review the generated ABI documentation. Done means the cuvs_c_header group exists with ops, the relevant public C headers have code-owner rules, and the selected developers have read the ABI documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100