Document how to use dependency groups in developer/contributor guides
Open
Nobody has claimed this yet.
cuda.bindings
documentation
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
It would be nice to document how this works for internal/external developers as well as QA.
Originally posted by @leofang in https://github.com/NVIDIA/cuda-python/issues/995#issuecomment-3383750653
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
Locate the developer and contributor guides and find the existing dependency-group configuration. Read how dependency groups are currently defined, then document their use for internal and external developers and QA; done means each audience can follow the guides without needing undocumented context.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100