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

Commit

Permalink
doc: address Working Groups
Browse files Browse the repository at this point in the history
So far, there hasn't been anything formal that covers the
formation and transition of working groups. This makes a
first attempt.

/cc: @mikeal
  • Loading branch information
jasnell committed Apr 15, 2015
1 parent 67332ae commit 625c63d
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,22 @@ When dependencies introduce additional functionality that does not break backwar

While the `npm` utility is shipped as part of Node.js, it is not a functional dependency in the same way as V8, OpenSSL or libuv. Specifically, `npm` is not considered part of the Node.js API. As a general rule, *semver-patch* and *semver-minor* updates in `npm` may be introduced into Node.js with only a *semver-patch* version increase. If there is a *semver-major* update in `npm`, such as when `npm` rolls over to version 3.0.0, then a *semver-major* version increase should occur in Node.js. However, the TSC may alter this policy in the future depending on the nature and scope of changes expected in newer versions of `npm`.

## Working Groups

Working Groups are autonomous groups of Collaborators chartered by the TSC to oversee specific aspects of the Project. Working groups can be formed at any time but must be ratified by the TSC.

Every Working Group has a charter that details it's area of responsibility. Once approved by the TSC, the Working Group becomes solely responsible for items detailed in that charter.

The charter must also indicate the conditions under which the Working Group's activity can be considered to be complete and the WG can be dissolved. A Working Group can, at any time, request that the TSC dissolve the Working Group by opening an issue requesting dissolution with the *tsc-agenda* tag.

The TSC may revoke the Working Groups charter at any time following the decision making process defined in the TSC Charter.

Proposals to create a new Working Group should be made either by opening an issue or submitting a PR with the draft charter for the new Working Group, then putting that on the TSC agenda using the *tsc-agenda* tag.

### Transition of io.js Working Groups

The io.js project currently has a number of Working Groups already chartered as detailed here: https://github.com/iojs/io.js/blob/v1.x/WORKING_GROUPS.md. Upon the launch of the Foundation and approval of the Foundation TSC charter, these existing Working Groups (and their existing membership) would be absorbed into the project. However, the TSC should perform a one-time review the existing WG charters and determine if rechartering is required. It is expected that most (if not all) the existing Working Groups will be transitioned without requiring recharter.

## Developer's Certificate of Origin 1.0

By making a contribution to this project, I certify that:
Expand Down

3 comments on commit 625c63d

@mikeal
Copy link

@mikeal mikeal commented on 625c63d Apr 15, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought this was covered in the Lifecycle document rather than the dev policy?

@jasnell
Copy link
Member Author

@jasnell jasnell commented on 625c63d Apr 15, 2015 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mikeal
Copy link

@mikeal mikeal commented on 625c63d Apr 15, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, because it's still an open PR :) joyent/nodejs-advisory-board#33

I even address how they move over and get merged in to the new ladder https://github.com/mikeal/nodejs-advisory-board/blob/lifecycle/governance-proposal/WG-Merger.md

Please sign in to comment.