Skip to content

Expand on CODEOWNERS file #363

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

Merged
merged 13 commits into from
Aug 25, 2022
Merged

Expand on CODEOWNERS file #363

merged 13 commits into from
Aug 25, 2022

Conversation

ianpittwood
Copy link
Collaborator

Added ownership assignments for Connect and Workbench.

@ianpittwood ianpittwood linked an issue Aug 1, 2022 that may be closed by this pull request
@ianpittwood
Copy link
Collaborator Author

@colearendt I saw you already added the file so I just expanded on it. My main goal is to close #306 so just let me know if you think the version in main is good as is and I can close both this PR and the issue.

@colearendt
Copy link
Contributor

Howdy @ianpittwood ! This looks great - I think I would probably consider #306 closed FWIW (I just forgot to close it when I merged the previous PR).

The only hesitation I have here is that it will be pretty noisy and potentially disruptive to the RSC / IDE teams, and they have not been briefed on / agreed to be party to all of the PRs in this repo 😅 As such, I would definitely hold this PR open, but it's probably worth sanity checking that this number of notifications is acceptable to the teams. (The RSPM team specifically agreed to be a CODE_OWNER).

@kfeinauer
Copy link
Contributor

@ianpittwood @colearendt Agree this could be spammy. I think we should reach out to the teams to see who wants to be included here.

@MariaSemple
@aronatkins

Could you two comment on who should be added to the CODEOWNERS file for the RSW and RSC Docker images?

@MariaSemple
Copy link
Contributor

I've put this on the agenda to be discussed at our next team meeting, and will update here with the result of the discussion.

Copy link
Contributor

@aronatkins aronatkins left a comment

Choose a reason for hiding this comment

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

The @rstudio/connect team may eventually prove to be too broad, but is probably the best option we have available. Let's start with this and adjust later.

@ianpittwood
Copy link
Collaborator Author

@MariaSemple did your team discuss yet?

@MariaSemple
Copy link
Contributor

Not yet - next Thursday.

@MariaSemple
Copy link
Contributor

MariaSemple commented Aug 18, 2022

For the Workbench team, could you set @melissa-barca and @cm421 as our code-owners instead of @rstudio/ide-team?

@ianpittwood
Copy link
Collaborator Author

Thanks, @MariaSemple! Everything should be updated and ready for review @atheriel @colearendt!

Copy link
Contributor

@MariaSemple MariaSemple left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@colearendt colearendt left a comment

Choose a reason for hiding this comment

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

LGTM! The only additional thought I had is maybe to add the RSW team to the r-session-complete images?

@ianpittwood
Copy link
Collaborator Author

@MariaSemple thoughts?

@zfouts zfouts mentioned this pull request Aug 19, 2022
@ianpittwood
Copy link
Collaborator Author

Maria approved of adding the same owners for workbench to r-session-complete. I updated the CODEOWNERS file and will merge once checks finish.

@ianpittwood ianpittwood merged commit a06f2d0 into main Aug 25, 2022
@ianpittwood ianpittwood deleted the 306-set-up-code_owners branch August 25, 2022 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set up CODE_OWNERS
5 participants