Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

[TODO] Draft the Charter #4

Open
jasnell opened this issue Oct 22, 2015 · 3 comments
Open

[TODO] Draft the Charter #4

jasnell opened this issue Oct 22, 2015 · 3 comments

Comments

@jasnell
Copy link
Member

jasnell commented Oct 22, 2015

This is a placeholder for now. We'll need to get a charter drafted for consideration by the TC

@jasnell jasnell added the meta label Oct 22, 2015
@jasnell
Copy link
Member Author

jasnell commented Oct 27, 2015

@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.

@dougwilson
Copy link
Member

I don't see any glaring issues with this charter.

@williamkapke
Copy link

Per nodejs/node#3919 this group appears to have completed chartering steps.

This issue can be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants