You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.
@nodejs/http ... this is a strawman ... feel free to knock it down
This WG would have the following responsibilities:
Addressing http issues on the Node.js issue tracker.
Authoring and editing http documentation within the Node.js project.
Reviewing changes to http subclasses within the Node.js project.
Working with the ecosystem of http related module developers to evolve the http implementation and APIs in core
Assisting in the implementation of http providers within Node.js.
Advising the Core TC on all http related issues and discussions
Messaging about the future of http to give the community advance notice of changes.
The charter should likely include an additional constraint that backwards incompatible changes to the existing HTTP API cannot be made without signoff from Core TC members. The WG can extend that API, or provide alternatives to it, but not breaking the existing ecosystem of developers takes priority over shiny new buttons.
This is a placeholder for now. We'll need to get a charter drafted for consideration by the TC
The text was updated successfully, but these errors were encountered: