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

Add scope of responsibility for TSC ("Define Node Core" cont.) #144

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 13 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ For more details read the [TSC Charter](https://github.com/nodejs/TSC/blob/maste

If your project is interested in joining the Node.js Foundation please read the [Project Lifecycle.md](./Project-Lifecycle.md) documentation.

## TSC Scope of Responsibility
## TSC Scope

**The TSC is responsible for Node.js Core project, a number of projects depended upon by Node.js Core, and a number of projects adjacent to Node.js Core.**

Expand All @@ -24,10 +24,10 @@ These projects are located in the following repositories:

* https://github.com/nodejs/build — administration delegated to the Build Working Group
* https://github.com/nodejs/citgm — administration delegated to the Core Technical Committee
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm probably wrong here- but I thought this was delegated to the Build Working Group

Copy link
Member Author

Choose a reason for hiding this comment

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

Ambiguous so I said CTC, could be Build, could be Testing, could even be LTS or it a whole new Smoke Testing group!

@thealphanerd what say you?

* https://github.com/nodejs/CTC — administration delegated to the Core Technical Committee
* https://github.com/nodejs/CTC — administration delegated to the Core Technical Committee, managed by the Smoke Testing Team
Copy link
Contributor

@williamkapke williamkapke Jan 12, 2017

Choose a reason for hiding this comment

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

Maybe this change was supposed to be 1 line up (on CitGM)?

Yeah- I see the prior comment now. This needs to move up to CitGM.

* https://github.com/nodejs/docker-node — administration delegated to the Docker Working Group
* https://github.com/nodejs/http-parser — administration delegated to the Core Technical Committee
* https://github.com/nodejs/LTS — administration delegated to the LTS Working Group
* https://github.com/nodejs/LTS — administration delegated to the Core Technical Committee, managed by the LTS Team
* https://github.com/nodejs/node-eps — administration delegated to the Core Technical Committee
* https://github.com/nodejs/nodejs-dist-indexer — administration delegated to the Build Working Group
* https://github.com/nodejs/nodejs-latest-linker — administration delegated to the Build Working Group
Expand All @@ -42,8 +42,12 @@ The TSC is responsible for a number of projects that are not strictly required t

In the case of adopting existing projects, once the TSC has decided that adoption appropriate, it should seek agreement from the Node.js Foundation Board for such adoption as it impacts on the scope of technical activities of the Foundation.

Copy link
Member

Choose a reason for hiding this comment

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

Where do repositories such as node-chakracore and http2 fit in? I'm thinking they should be handled as dependent projects.

Copy link
Member Author

Choose a reason for hiding this comment

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

done, tried to be pretty exhaustive in latest version

If the Node.js Foundation Board wishes to adopt an existing project, it must seek agreement from the TSC that such adoption is appropriate and that any changes to scope that it entails are acceptable.

Current adjacent projects that are within the TSC's scope of responsibility can be found at the following locations:

* https://github.com/nodejs/abi-stable-node - administration delegated to the API Working Group
* https://github.com/nodejs/abi-stable-node-addon-examples - administration delegated to the API Working Group
* https://github.com/nodejs/api — administration delegated to the API Working Group
* https://github.com/nodejs/benchmarking — administration delegated to the Benchmarking Working Group
* https://github.com/nodejs/code-and-learn
Expand All @@ -52,16 +56,16 @@ Current adjacent projects that are within the TSC's scope of responsibility can
* https://github.com/nodejs/education
* https://github.com/nodejs/email — administration delegated to the Build Working Group
* https://github.com/nodejs/evangelism — administration delegated to the Evangelism Working Group
* https://github.com/nodejs/github-bot — administration delegated to the Core Technical Committee
* https://github.com/nodejs/help — administration delegated to the Core Technical Committee
* https://github.com/nodejs/github-bot — administration delegated to the Core Technical Committee, managed by the GitHub Bot Team
* https://github.com/nodejs/help — administration delegated to the Evangelism Working Group
* https://github.com/nodejs/http — administration delegated to the HTTP Working Group
Copy link
Member

Choose a reason for hiding this comment

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

HTTP WG has been dechartered. This should fall back to CTC

* https://github.com/nodejs/http2 — administration delegated to the Core Technical Committee
* https://github.com/nodejs/iojs.org — administration delegated to the Website Working Group
* https://github.com/nodejs/installer — administration delegated to the Core Technical Committee
* https://github.com/nodejs/Intl — administration delegated to the Intl Working Group
* https://github.com/nodejs/llnode — administration delegated to the Core Technical Committee
* https://github.com/nodejs/llnode — administration delegated to the Post Mortem Working Group
* https://github.com/nodejs/nan — administration delegated to the Addon API Working Group
* https://github.com/nodejs/node-addon-examples — administration delegated to the Addon API WorkingGroup)
* https://github.com/nodejs/node-addon-examples — administration delegated to the Addon API Working Group)
* https://github.com/nodejs/node-chakracore — administration delegated to the Core Technical Committee
* https://github.com/nodejs/node-gyp — administration delegated to the Core Technical Committee
* https://github.com/nodejs/nodereport — administration delegated to the Post Mortem Working Group
Expand All @@ -72,7 +76,7 @@ Current adjacent projects that are within the TSC's scope of responsibility can
* https://github.com/nodejs/testing — administration delegated to the Testing Working Group
Copy link
Member

Choose a reason for hiding this comment

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

probably need to add

https://github.com/nodejs/abi-stable-node - administration delegated to the API Working Group
https://github.com/nodejs/abi-stable-node-addon-examples - administration delegated to the API Working Group

* _And_ various language and resource translation groups under https://github.com/nodejs/

### Responsibilities
### List of TSC Responsibilities

The TSC exercises autonomy in setting up and maintaining procedures, policies, and management and administrative structures as it deems appropriate for the maintenance and operation of these projects and resources.

Expand All @@ -85,7 +89,7 @@ Included in the responsibilities of the TSC are:
* Creating new repositories and projects under the _nodejs_ GitHub organization as required
* Setting overall technical direction for the Node.js Core project, including high-level goals and low-level specifics regarding features and functionality
* Setting and maintaining appropriate standards for community discourse via the various mediums under TSC control
* Setting and maintaining governance rules for the conduct and make-up of the TSC, CTC, Working Groups and other bodies under the TSC
* Setting and maintaining governance rules for the conduct and make-up of the TSC, CTC, Working Groups and other bodies within the TSC's domain

Many of these responsibilities will be delegated by the TSC to appropriate bodies such as the CTC and Working Groups.

Expand Down