-
Notifications
You must be signed in to change notification settings - Fork 134
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
Objection Override -> [#33879](https://github.com/nodejs/node/pull/33879) #928
Comments
If there are more than one codeowner for a PR, will one approval from each team be require, or only from one of the teams? |
I was under the impression it was one member from one of the teams, although I think this does beg the question of in what circumstance there will be more than one codeowner, and how those specific teams feel about it |
A PR touching two subsystems would be one case where more than one team is pinged. Another question: the approval still has to be from a collaborator (since codeowners can be working group teams and not all members will be collaborators), right? |
As for audit, how far do we want to go with the strictness of it? I think we could have an Action in this repository that runs periodically and dumps membership of all teams in the org into files, and opens a PR if anything changes. This way we get notified of any membership changes. It's not super robust since the Action would need to run periodically instead of on an event (there are no Actions for Org events yet), but better than nothing I guess? Or is this more than necessary, and just a sweep of teams every once in a while is enough? |
Plus, should we aim for 100% codeownership on nodejs/node? |
(I'm plus one on this proposal, just want to make sure we remove some ambiguity or unclarity from it) |
Linking to nodejs/node#33879 |
Also related discussion in #921 |
@mmarchini I was looking to see if we have consensus as the target we set for objections has passed. I'm not sure if you think we should change the proposal to be put into nodejs/node#33879 or if the details of the audit can be finalised agreed afterwards? |
Audit can be done afterwards IMO |
There were no objections, so I'll assume this is approved. I'll leave a comment in the PR and remove from the agenda. |
We discussed this in the TSC meeting this week.
Proposal is to override the objection after the PR having been updated to reflect this suggested compromise:
Along with a planned audit of the current members of the CODEOWNERS for each area.
@nodejs/tsc unless there are objections by Wed Sep 23rd, the assumption will be that TSC consensus on this as the direction has been reached.
The text was updated successfully, but these errors were encountered: