@@ -101,9 +101,17 @@ Charter need approval by the OpenJS Foundation Cross-Project Council (CPC).
101101The TSC meets in a video conference call. Each year, the TSC elects a chair to
102102run the meetings. The TSC streams its meetings for public viewing on YouTube.
103103
104+ TSC meetings may consist of a public portion and a private portion. The private
105+ portion is used to discuss sensitive topics, such as personnel issues,
106+ security vulnerabilities, or other confidential matters. Private discussions
107+ should be avoided as much as possible, and the TSC should strive to keep
108+ discussions in the public portion of the meeting, but there are times when
109+ private discussions are necessary.
110+
104111The TSC agenda includes issues that are at an impasse. The intention of the
105112agenda is not to review or approve all patches. Collaborators review and approve
106- patches on GitHub.
113+ patches on GitHub. The preference is to minimize the need for TSC meetings to
114+ make decisions that can otherwise be made by collaborators on GitHub.
107115
108116Any community member can create a GitHub issue asking that the TSC review
109117something. If consensus-seeking fails for an issue, a collaborator may apply the
@@ -113,21 +121,55 @@ Before each TSC meeting, the meeting chair will share the agenda with members of
113121the TSC. TSC members can also add items to the agenda at the beginning of each
114122meeting. The meeting chair and the TSC cannot veto or remove items.
115123
116- The TSC may invite people to take part in a non-voting capacity.
117-
118- During the meeting, the TSC chair ensures that someone takes minutes. After the
119- meeting, the TSC chair ensures that someone opens a pull request with the
120- minutes.
121-
122- The TSC seeks to resolve as many issues as possible outside meetings using
123- [ the TSC issue tracker] ( https://github.com/nodejs/TSC/issues ) . The process in
124- the issue tracker is:
124+ The TSC may invite people to take part in a non-voting capacity in either the
125+ public or private portions of the meeting.
126+
127+ During the public portion of the meeting, the TSC chair ensures that someone
128+ takes minutes that include a summary of the discussion and any
129+ decisions made. After the meeting, the TSC chair ensures that someone opens a
130+ public pull request with the minutes from the public portion of the meeting.
131+
132+ The public portion of the TSC meeting is expected to be recorded and made
133+ available for live streaming during the meeting or download by anyone after.
134+ This expectation is to be announced to all participants at the start of the
135+ each meeting before the recording is started. Continued participation in the
136+ public portion of the meeting after this announcement is interpreted as consent to the
137+ recording.
138+
139+ For the private portion of the meeting, the TSC chair ensures that someone
140+ produces a summary of the discussions, gets it reviewed by the attendees,
141+ and shares it to all the TSC members once approved by the attendees via a
142+ private discussion channel such as the TSC private mailing list. The summary
143+ may be made public if there is consensus within the TSC and the non-TSC
144+ attendees to make it public.
145+
146+ Recording the private portion of a meeting or maintaining or publishing a
147+ detailed transcript is only permitted when all participants present during the
148+ private portion of the meeting explicitly agree to the recording and/or
149+ transcript, in order to comply to privacy regulations.
150+
151+ All discussions made during meetings are considered provisional, receiving no
152+ objections from folks at the TSC meeting to take an action is not equivalent to
153+ the TSC endorsing that action.
154+
155+ If a quorum of TSC voting members is present, it is possible to call for an
156+ explicit vote, and take the vote immediately if there are no objections. The
157+ decision is considered confirmed once the rest of the TSC voting members have
158+ been informed and no objection for taking that vote has been raised in 48 hours.
159+ To clarify, TSC voting members can object to the vote taking place during the
160+ meeting, but not to the vote itself.
161+
162+ For discussions outside of meetings, the TSC uses
163+ [ the TSC issue tracker] ( https://github.com/nodejs/TSC/issues ) for public
164+ issues, and the private TSC email list for private matters. The process for
165+ public issues in the issue tracker is:
125166
126167* A TSC member opens an issue explaining the proposal/issue and @-mentions
127168 @nodejs/tsc .
128169* The proposal passes if, after 72 hours, there are two or more TSC voting
129170 member approvals and no TSC voting member opposition.
130- * If there is an extended impasse, a TSC member may make a motion for a vote.
171+ * If there is an extended impasse, a TSC member may ask for the issue to be
172+ added to the TSC agenda, or make a motion for a vote.
131173
132174## Collaborator nominations
133175
0 commit comments