The Wayback Machine - https://web.archive.org/web/20201214103117/https://github.com/nodejs/admin/issues/531
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

New Repo Request: http-next #531

Closed
Ethan-Arrowood opened this issue Jul 9, 2020 · 8 comments
Closed

New Repo Request: http-next #531

Ethan-Arrowood opened this issue Jul 9, 2020 · 8 comments

Comments

@Ethan-Arrowood
Copy link

@Ethan-Arrowood Ethan-Arrowood commented Jul 9, 2020

The NodeJS Web Server Framework Working Group requests a new repo in the NodeJS org titled http-next. We will be using this repo to develop a ground-up rewrite of the http core modules. This plan was discussed during the OpenJS World collaboration summit and continued during our routine working group meetings.

Here are some relevant issues for more information:

Reminder: requests like this are automatically approved after 72 hours. If you object to this new repo or would like to propose a different name please do so promptly so we can discuss. Thank you!

@mhdawson
Copy link
Member

@mhdawson mhdawson commented Jul 9, 2020

+1

@mcollina
Copy link
Member

@mcollina mcollina commented Jul 10, 2020

LGTM.

Is this going to be a node core fork?

@Ethan-Arrowood
Copy link
Author

@Ethan-Arrowood Ethan-Arrowood commented Jul 10, 2020

Great question @mcollina

@jasnell do you think a fork would be best or would you like to build it in another way?

@wesleytodd
Copy link
Member

@wesleytodd wesleytodd commented Sep 4, 2020

I don't think this will be a node core fork. My understanding was that this would house the mid and top tier apis, and @jasnell was working on the lowest level apis in node core now. So, this repo would house the http1/2/3 apis and whatever abstraction we build on top of that to make the compatibility story better.

If anyone from the @nodejs/web-server-frameworks team disagrees with my understanding please chime in.

@Trott
Copy link
Member

@Trott Trott commented Sep 6, 2020

According to https://github.com/nodejs/admin/blob/1ac8f19c14c22683c8f8271ca8f205a6580b3be6/GITHUB_ORG_MANAGEMENT_POLICY.md#repositories, this is effectively approved. Looking at the web-server-frameworks folks, I see at least four people that should be able to add the repo (Matteo, James, Michael, and Gireesh). Happy to do it if they'd prefer that for any reason, but probably best for one of them to just set it up.

@mhdawson
Copy link
Member

@mhdawson mhdawson commented Oct 26, 2020

Repo created, https://github.com/nodejs/http-next. @Ethan-Arrowood can you push, licence, readme.md and code of conduct files before anything else goes in?

@Ethan-Arrowood
Copy link
Author

@Ethan-Arrowood Ethan-Arrowood commented Oct 27, 2020

Pushed! Let me know if anything needs to be changed

@Trott
Copy link
Member

@Trott Trott commented Oct 27, 2020

I think this can be closed now? Re-open if I'm wrong, of course.

@Trott Trott closed this Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
You can’t perform that action at this time.