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
The Node.js Foundation Technical Steering Committee is the technical governing body of the Node.js Foundation. It admits and oversees all top-level Projects in the Node.js Foundation. It also elects a representative to the Node.js Foundation Board of Directors.
3
+
The Node.js Foundation Technical Steering Committee is the technical governing
4
+
body of the Node.js Foundation. It admits and oversees all top-level Projects
5
+
in the Node.js Foundation. It also elects a representative to the Node.js
6
+
Foundation Board of Directors.
4
7
5
-
For more details read the [TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md) adopted by the Node.js Foundation Board of Directors on June 17th 2015.
8
+
For more details read the [TSC Charter][] adopted by the Node.js Foundation
9
+
Board of Directors on June 17th 2015.
6
10
7
-
If your project is interested in joining the Node.js Foundation please read the [Project Lifecycle.md](./Project-Lifecycle.md) documentation.
11
+
If your project is interested in joining the Node.js Foundation please read
12
+
the [Project Lifecycle.md](./Project-Lifecycle.md) documentation.
8
13
9
14
## TSC Scope
10
15
11
-
**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.**
16
+
**The TSC is responsible for Node.js Core project, a number of projects
17
+
depended upon by Node.js Core, and a number of projects adjacent to Node.js
18
+
Core.**
12
19
13
-
The TSC exercises autonomy in managing its responsibilities and seeks agreement from the Node.js Foundation Board on any change to the scope of those responsibilities as defined below.
20
+
The TSC exercises autonomy in managing its responsibilities and seeks agreement
21
+
from the Node.js Foundation Board on any change to the scope of those
22
+
responsibilities as defined below.
14
23
15
24
### Node.js Core
16
25
17
-
Node.js Core is defined as the code project existing in the repository located at <https://github.com/nodejs/node> which the `node` executable and associated packages are built from, _minus_ the vendored projects included in the codebase, specifically those located in the [deps](https://github.com/nodejs/node/tree/master/deps) and [tools](https://github.com/nodejs/node/tree/master/tools) directories that are copied in from externally maintained repositories.
26
+
*Node.js Core* is defined as the contents of the repository located at
27
+
<https://github.com/nodejs/node> from which the `node` executable and associated
28
+
packages are built excluding the vendored projects included in the codebase
29
+
located in the [deps][] and [tools][] directories that are copied in from
30
+
externally maintained repositories.
18
31
19
32
### Dependent Projects
20
33
21
-
Additional projects fall within the TSC's scope of responsibility which are dependencies of Node.js Core in that they are **required** to plan, test, build, document and ship Node.js releases.
34
+
Additional projects fall within the TSC's scope of responsibility which are
35
+
dependencies of Node.js Core in that they are **required** to plan, test, build,
36
+
document and ship Node.js releases.
22
37
23
38
These projects are located in the following repositories:
*https://github.com/nodejs/build — administration delegated to the Build Working Group
27
42
*https://github.com/nodejs/citgm — administration delegated to the Core Technical Committee, managed by the Smoke Testing Team
28
-
*https://github.com/nodejs/CTC — administration delegated to the Core Technical Committee
29
43
*https://github.com/nodejs/docker-node — administration delegated to the Docker Working Group
30
44
*https://github.com/nodejs/http-parser — administration delegated to the Core Technical Committee
31
45
*https://github.com/nodejs/LTS — administration delegated to the Core Technical Committee, managed by the LTS Team
@@ -39,13 +53,22 @@ These projects are located in the following repositories:
39
53
40
54
### Adjacent Projects
41
55
42
-
The TSC is responsible for a number of projects that are not strictly required to plan, test, build, document and ship Node.js releases. Projects that are _adjacent_ are either created from within the technical organization managed by the TSC or are adopted into that organization from outside.
56
+
The TSC is responsible for a number of projects that are not strictly required
57
+
to plan, test, build, document and ship Node.js releases. Projects that are
58
+
_adjacent_ are either created from within the technical organization managed by
59
+
the TSC or are adopted into that organization from outside.
43
60
44
-
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.
61
+
In the case of adopting existing projects, once the TSC has decided that
62
+
adoption appropriate, it should seek agreement from the Node.js Foundation Board
63
+
for such adoption as it impacts on the scope of technical activities of the
64
+
Foundation.
45
65
46
-
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.
66
+
If the Node.js Foundation Board wishes to adopt an existing project, it must
67
+
seek agreement from the TSC that such adoption is appropriate and that any
68
+
changes to scope that it entails are acceptable.
47
69
48
-
Current adjacent projects that are within the TSC's scope of responsibility can be found at the following locations:
70
+
Current adjacent projects that are within the TSC's scope of responsibility can
71
+
be found at the following locations:
49
72
50
73
*https://github.com/nodejs/abi-stable-node — administration delegated to the API Working Group
51
74
*https://github.com/nodejs/abi-stable-node-addon-examples — administration delegated to the API Working Group
@@ -80,66 +103,115 @@ Current adjacent projects that are within the TSC's scope of responsibility can
80
103
81
104
### List of TSC Responsibilities
82
105
83
-
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.
106
+
The TSC exercises autonomy in setting up and maintaining procedures, policies,
107
+
and management and administrative structures as it deems appropriate for the
108
+
maintenance and operation of these projects and resources.
84
109
85
110
Included in the responsibilities of the TSC are:
86
111
87
-
* Managing code and documentation creation and changes for the listed projects and resources
88
-
* Setting and maintaining standards covering contributions of code, documentation and other materials
* Making decisions regarding dependencies of the Node.js Core project, including what those dependencies are and how they are bundled with source code and releases
91
-
* Creating new repositories and projects under the _nodejs_ GitHub organization as required
92
-
* Setting overall technical direction for the Node.js Core project, including high-level goals and low-level specifics regarding features and functionality
93
-
* Setting and maintaining appropriate standards for community discourse via the various mediums under TSC control
94
-
* 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
95
-
96
-
Many of these responsibilities will be delegated by the TSC to appropriate bodies such as the CTC and Working Groups.
112
+
* Managing code and documentation creation and changes for the listed projects
113
+
and resources
114
+
* Setting and maintaining standards covering contributions of code,
115
+
documentation and other materials
116
+
* Managing code and binary releases: types, schedules, frequency, delivery
117
+
mechanisms
118
+
* Making decisions regarding dependencies of the Node.js Core project,
119
+
including what those dependencies are and how they are bundled with source
120
+
code and releases
121
+
* Creating new repositories and projects under the _nodejs_ GitHub organization
122
+
as required
123
+
* Setting overall technical direction for the Node.js Core project, including
124
+
high-level goals and low-level specifics regarding features and functionality
125
+
* Setting and maintaining appropriate standards for community discourse via the
126
+
various mediums under TSC control
127
+
* Setting and maintaining governance rules for the conduct and make-up of the
128
+
TSC, Working Groups and other bodies within the TSC's domain
129
+
130
+
Many of these responsibilities will be delegated by the TSC to appropriate
131
+
bodies such as the Working Groups.
97
132
98
133
## TSC Members
99
134
100
-
TSC members are responsible for top level technical community concerns. The role is
101
-
mostly administrative and is responsible for admitting new Top Level Projects, Top Level
102
-
Working Groups, and advocating for any needs in the technical side of the foundation to
103
-
the Node.js Foundation Board of Directors.
104
-
105
-
TSC members can nominate new members at any time. Candidates for membership tend to be people
106
-
who have a competancy for community management and a high tolerance and patience for process
107
-
minutiae as the TSC delegates most of its responsibilities to other projects and working groups.
135
+
TSC members are responsible for top level technical community concerns. The role
136
+
is mostly administrative and is responsible for admitting new Top Level
137
+
Projects, Top Level Working Groups, and advocating for any needs in the
138
+
technical side of the foundation to the Node.js Foundation Board of Directors.
108
139
109
-
Every Top Level Project not currently incubating can appoint someone to the TSC who they elect
110
-
at their own discretion.
140
+
Every Top Level Project not currently incubating can appoint someone to the TSC
Copy file name to clipboardExpand all lines: Streaming/Streaming-To-Youtube.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -62,5 +62,5 @@ However, it may turn yellow and issue a warning in a "stream health" section bel
62
62
63
63
Moderation follows the [Moderation Policy](../Moderation-Policy.md). Messages can be moderated right-clicking and selecting the necessary action, such as `remove`.
64
64
65
-
During TSC and CTC meetings, there is a section of public Q&A at the end.
65
+
During TSC meetings, there is a section of public Q&A at the end.
66
66
It is important to solicit for questions **well in advance** of public Q&A sections so that people have time to think of and type questions.
0 commit comments