dask / dask/community

gpuCI admin team for Dask and Dask-contrib orgs

Open
#184 13 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
25
Forks
3
PR merge metrics
No merged PRs in 30d

Description

As [pointed out](https://github.com/dask/distributed/issues/5154#issuecomment-921818168) on dask/distributed#5154, it is not immediately obvious to Dask contributors who the gpuCI admins are; currently, the admin list is:

```
charlesbluca
quasiben
pentschev
jacobtomlinson
jrbourbeau
jsignell
martindurant
jcrist
jakirkham
mrocklin
TomAugspurger
```

Which doesn't match up with the [`dask/gpu`](https://github.com/orgs/dask/teams/gpu) team that is typically pinged on PRs that need gpuCI approval. @jakirkham suggested that we might improve transparency here by creating a org team that coincides with the admin list; I generally think this a good idea, though I am not sure if everyone on the current admin list would want to get pinged whenever PR approval is needed. I think a sensible solution for now would be to add all the missing members of the `dask/gpu` team to the current admin list, and then we can have a follow-up discussion on if there's anyone we should remove from the admin list in advance before making a new team.

@jakirkham also [suggested](https://github.com/dask-contrib/dask-sql/issues/239#issuecomment-921882344) doing the same for dask-contrib in preparation for setting up gpuCI on dask-sql. Not sure how folks feel about that, since dask-contrib only has one member currently.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.