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

meta: add N-API to codeowners coverage #34039

Closed
wants to merge 4 commits into from

Conversation

mhdawson
Copy link
Member

We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>
@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Jun 24, 2020
@richardlau
Copy link
Member

It makes sense to have one of the N-API team sign off on commits
that changes N-API

The team may have to be made a sub team of collaborators for this to work, see discussion in #33895.

# N-API

# ./src/node_api* @nodejs/n-api
# ./src/js_native_api* @nodejs/n-api
Copy link
Member

Choose a reason for hiding this comment

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

Should the relevant doc pages also require sign off?

Copy link
Member Author

Choose a reason for hiding this comment

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

@richardlau makes sense added.


# N-API

# ./src/node_api* @nodejs/n-api
Copy link
Member

Choose a reason for hiding this comment

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

are these supposed to be commented out

Copy link
Member Author

Choose a reason for hiding this comment

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

@devsnek that is a good question. I saw most of them were commented out so followed the same pattern. @jasnell since you left many of the them commented out for now is it ok to turn it on for N-API now or do you think we should let the initial set bake for a while? Either way I'd like to add N-API now (either active or commented out) so that we don't forget.

Copy link
Contributor

Choose a reason for hiding this comment

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

The ones commented out are for teams which does not have write permission on this repository (teams which are not subteams of collaborators), as per discussions in #33895.

I'm working on an alternative to codeowners using the github-bot to work around GitHub's constraint on only teams with write permissions being valid owners. IMO it's best to keep these commented out for now, then we can uncomment when we move to the github-bot-based owners. Note that this PR is essentially a no-op this way though.

@mmarchini
Copy link
Contributor

@nodejs/tsc (since according to CODEOWNERS changes to CODEOWNERS should add tsc for review, but apparently it didn't work)

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@Trott
Copy link
Member

Trott commented Jul 2, 2020

It makes sense to have one of the N-API team sign off on commits
that changes N-API

The team may have to be made a sub team of collaborators for this to work, see discussion in #33895.

So someone can get write permissions to the repo by accident. We don't have any real auditing or oversight of these teams. It also means that right now, we'd have to boot a bunch of people off the team.

@mhdawson
Copy link
Member Author

mhdawson commented Jul 2, 2020

@Trott sounds like the same issue applies to the other commented out teams as well.

At this point I mostly want to make sure we don't forget applying to the N-API team once we figure how to make it work in general (and since its commented out like the others there would be no harm).

@mmarchini
Copy link
Contributor

I'm working on an alternative to code owners that should work for us. PRs opened here and on github-bot

.github/CODEOWNERS Outdated Show resolved Hide resolved
Co-authored-by: Richard Lau <riclau@uk.ibm.com>
@Trott
Copy link
Member

Trott commented Jul 2, 2020

@Trott sounds like the same issue applies to the other commented out teams as well.

At this point I mostly want to make sure we don't forget applying to the N-API team once we figure how to make it work in general (and since its commented out like the others there would be no harm).

Oh, uh yeah, commented out is no problem. Sorry I missed that!

@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 2, 2020
.github/CODEOWNERS Outdated Show resolved Hide resolved
jasnell
jasnell previously requested changes Jul 3, 2020
Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

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

Marking this 'Request changes' so it doesn't land without the suggested fixes

@jasnell jasnell removed the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 3, 2020
@mhdawson
Copy link
Member Author

mhdawson commented Jul 3, 2020

@james I think the suggestion was to leave commented out for now. I'll remove the dot but leave comment out until we figure out the issues that apply to all of the sections.

Co-authored-by: James M Snell <jasnell@gmail.com>
@jasnell
Copy link
Member

jasnell commented Jul 3, 2020

Ok... in general, now that the paths are correct, the CODEOWNERS file is working perfectly for the QUIC files. Zero issues thus far.

@mhdawson
Copy link
Member Author

mhdawson commented Jul 3, 2020

Equivalent to a doc change and linters are ok so landing.

@jasnell jasnell dismissed their stale review July 3, 2020 22:07

Resolved

@mhdawson
Copy link
Member Author

mhdawson commented Jul 3, 2020

@james just noticed you are still "changes requests" are you ok with it landing?

@jasnell
Copy link
Member

jasnell commented Jul 3, 2020

Heh... our timing is perfect today... just resolved that :-)

mhdawson added a commit that referenced this pull request Jul 3, 2020
We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

PR-URL: #34039
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@mhdawson
Copy link
Member Author

mhdawson commented Jul 3, 2020

Landed as bff7de3

@Trott Trott closed this Jul 4, 2020
MylesBorins pushed a commit that referenced this pull request Jul 14, 2020
We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

PR-URL: #34039
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Jul 14, 2020
MylesBorins pushed a commit that referenced this pull request Jul 16, 2020
We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

PR-URL: #34039
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@mmarchini
Copy link
Contributor

Just FYI, the team is not being added as reviewer because it is not a subteam of collaborators (as an example: #34344)

addaleax pushed a commit that referenced this pull request Sep 22, 2020
We have this guidance for contributing to N-API:
https://github.com/nodejs/node/blob/master/doc/guides/adding-new-napi-api.md

It makes sense to have one of the N-API team sign off on commits
that changes N-API

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

PR-URL: #34039
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@codebytere codebytere mentioned this pull request Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants