Skip to content

[no-ci] Update the contributor guide #3292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leofang merged 2 commits into from
Nov 2, 2026
Merged

[no-ci] Update the contributor guide #3292

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0d9f262
stress the need of assignment, no exception
leofang Oct 30, 2026
dd5fa7a
fix linter
leofang Oct 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 15 additions & 10 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,21 +37,26 @@ reproducers, documentation improvements, and code changes are welcome.

## Coordinate before implementing

Review capacity is limited. If you are contributing from outside NVIDIA:
Our review and CI capacities are limited. If you are contributing from outside NVIDIA:

- **Existing issue:** comment and wait for a maintainer to assign it to you or
- **Existing issues:** comment and wait for a maintainer to assign it to you or
explicitly ask you to implement it. Check existing assignments and requests
to take the issue.
- **New features, design changes, or CI/release infrastructure:** open an issue
and agree on scope and validation before implementing.
- **Small standalone bug or documentation fixes without an existing issue:**
a direct PR is welcome. Explain the problem and how you checked the fix.
- **New features, bug/documentation fixes, RFCs, or code updates/enhancements:** open an
issue, agree on scope and validation, and wait for the assignment before implementing.

NVIDIA contributors may use normal team planning and self-assignment.
For obvious issues, opening a one-liner issue for tracking and assignment purposes is
completely fine.

For bug reports, please include a reproducer with a clear description for the expected
versus observed behavior. Also include the CUDA driver version and the Python environment
information (ex: `pip list`, `conda list`, ..., depending on how the environment was
created).

Feel free to report a bug or send reproducers, measurements, and suggestions
without an assignment. Include relevant versions and expected versus observed
behavior in bug reports.
Please do not send unsolicited (i.e. without prior discussion and assignment) PRs, which
could be closed without notice subject to the team's triage.

NVIDIA contributors may use normal team planning and self-assignment.

Keep changes focused, understand the complete diff, and report which checks
ran and any validation gaps.
Expand Down
Loading