-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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 initial CODEOWNERS file #20554
Conversation
could add |
More suggestions:
|
Does this file work with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may also mutually merge this with data from COLLABORATOR_GUIDE.md#who-to-cc-in-the-issue-tracker
.github/CODEOWNERS.txt
Outdated
/deps/npm/ @nodejs/npm | ||
/deps/v8/ @nodejs/v8 | ||
|
||
/benchmark/ @nodejs/performance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+ @nodejs/benchmarking
?
.github/CODEOWNERS.txt
Outdated
*vm* @nodejs/vm | ||
*zlib* @nodejs/zlib | ||
|
||
/src/node.cc @nodejs/process |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+ bootstrap_node.js
?
.github/CODEOWNERS.txt
Outdated
|
||
/deps/libuv/ @nodejs/libuv | ||
/deps/npm/ @nodejs/npm | ||
/deps/v8/ @nodejs/v8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nodejs/v8-update
Updated... fwiw, this is going to require ongoing refinement. It's going to take several tries to get this exactly right. I'd like to get this landed and iterate on it. |
The documentation says "The people you choose as code owners must have write permissions for the repository." so I'm not sure it will work as intended. |
Yep. For most of the groups that holds true. I don't know about groups that may contain a mix. This is a trial run :) |
.github/CODEOWNERS
Outdated
*tls* @nodejs/tls | ||
*dgram* @nodejs/dgram | ||
*domain* @nodejs/domains | ||
*fs* @nodejs/fs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicate?
.github/CODEOWNERS
Outdated
*vm* @nodejs/vm | ||
*zlib* @nodejs/zlib | ||
|
||
/lib/internal/modules/esm/ @nodejs/modules |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it covered by *module* @nodejs/modules
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, the modules team should not be pinged for cjs stuff (in /lib/internal/modules/cjs/
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But will not it be pinged as *module*
glob above matches/lib/internal/modules/cjs/
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that will need to be refined. We don't have a team for the cjs module system. That one might need to be nodejs/tsc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Then COLLABORATOR_GUIDE.md#who-to-cc-in-the-issue-tracker also needs to be refined as for @nodejs/modules
cc)
Also to consider (partly from "Who to cc.."):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on landing this and iterating on it later.
A few suggestions if you want to update before landing:
/src/node_postmortem_metadata.cc @nodejs/diagnostics @nodejs/post-mortem
/src/*.d @nodejs/diagnostics @nodejs/platform-smartos @nodejs/platform-freebsd @nodejs/platform-macos @nodejs/dtrace-mdb
/src/node.stp @nodejs/diagnostics
5c5b823
to
883afb6
Compare
PR-URL: #20554 Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
Landed in c0359f0 |
PR-URL: #20554 Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
First pass at a CODEOWNERS file
This likely needs refinement.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes