-
Notifications
You must be signed in to change notification settings - Fork 143
move undici to the nodejs org #541
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
Comments
Only thing I would want to ensure is that the code is properly licensed which it appears to be. LGTM |
SGTM. I'm transfering the issue to
Request is approved if there are no objections in 72h. |
cc @nodejs/community-committee @nodejs/tsc |
SGTM |
See: nodejs/admin#541 Fixes #312.
See: nodejs/admin#541 Fixes #312.
@nodejs/tsc @nodejs/community-committee please review nodejs/undici#346. |
LGTM once nodejs/undici#346 lands (made one suggested change there) |
* Add Node.js meta documents See: nodejs/admin#541 Fixes #312. * Update CODE_OF_CONDUCT.md Co-authored-by: Michael Dawson <[email protected]> Co-authored-by: Michael Dawson <[email protected]>
Done. I've also created a team with @ronag and myself in it with |
A long time ago, I started developing https://github.com/mcollina/undici which is a replacement for Node.js core
http.request
andhttp.Agent
. I think it has a reached a point of maturity where it would benefit to be in the Node.js organization instead.wdyt?
cc nodejs/undici#312
The text was updated successfully, but these errors were encountered: