Skip to content
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.

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

Update CODEOWNERS #3331

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update CODEOWNERS #3331

wants to merge 1 commit into from

Conversation

jrhemstad
Copy link
Collaborator

Update the CODEOWNERS in preparation for enabling 2 required reviews.

I've changed the strategy from how it was set up before where it would assign reviewers from a general pool as well as a specific pool. This was more relevant when the team was smaller. Now that we have more people, I think we can just require 2 reviewers from the specific codeowner team.

For reference, here is the current group membership: https://github.com/orgs/NVIDIA/teams/cccl-codeowners/teams
This should be updated as well.
image

Copy link

copy-pr-bot bot commented Jan 10, 2025

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

libcudacxx/ @nvidia/cccl-libcudacxx-codeowners @nvidia/cccl-codeowners
thrust/ @nvidia/cccl-thrust-codeowners
cub/ @nvidia/cccl-cub-codeowners
libcudacxx/ @nvidia/cccl-libcudacxx-codeowners
cudax/ @nvidia/cccl-cudax-codeowners
c/ @nvidia/cccl-c-codeowners
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think Python team should be a stakeholder here

Suggested change
c/ @nvidia/cccl-c-codeowners
c/ @nvidia/cccl-c-codeowners @nvidia/cccl-python-codeowners

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(alternatively, we could just nuke cccl-c-codeowners...)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree there's a lot of overlap, but I've just encoded that in the membership of the two different groups. Putting two teams listed as codeowners would end up requiring 4 total reviews which is probably too many.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought the threshold is set independently in the repo setting, not based on the number of teams? (I could be wrong.)

libcudacxx/ @nvidia/cccl-libcudacxx-codeowners @nvidia/cccl-codeowners
thrust/ @nvidia/cccl-thrust-codeowners
cub/ @nvidia/cccl-cub-codeowners
libcudacxx/ @nvidia/cccl-libcudacxx-codeowners
cudax/ @nvidia/cccl-cudax-codeowners
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: by the time we start integrating some components from cudax with cuda.core, we might need Python team here. For now it's OK since I keep an eye on it already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants