Future of HTTP Organization Plan

[Ethan-Arrowood]

Follow up issue from OpenJS World collab summit discussion.

This issue will track the work on planning the organization that will potentially manage http related modules.

[Ethan-Arrowood]

@wesleytodd can you share with us any of the documents Pkgjs used? I'm happy to lead this planning just need some more info 😄

[wesleytodd]

Here is the discussion on having a new Org: nodejs/admin#470
Here is the proposed charter: nodejs/package-maintenance#338

We should be able to just pull from those to refocus the group and charter here if everyone thinks that approach to organizing this effort makes sense.

[Ethan-Arrowood]

Notes from 07/09

• Start with 1 repo in Node.js; called http-next (anyone opposed to this?)
• Holistically covers http in a monorepo style (1,2,3,etc)
• Includes previously discussed submodule ideas such as headers & cookies
• If we'd like to break this into a separate org we can get a charter

[Ethan-Arrowood]

How to create a repo in Node core https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANAGEMENT_POLICY.md#repositories

[Ethan-Arrowood]

✨ nodejs/admin#531

[mcollina]

I highly recommend these new modules/api to be benchmarked.