doc: revise TSC Meetings material in GOVERNANCE.md · nodejs/node@82e6c33 (original) (raw)

`@@ -75,46 +75,37 @@ Charter need approval by the Node.js Board of Directors.

`

75

75

``

76

76

`### TSC Meetings

`

77

77

``

78

``

`-

The TSC meets regularly in a voice conference call. The meeting is run by a

`

79

``

`-

designated meeting chair approved by the TSC. Each meeting is streamed on

`

80

``

`-

YouTube.

`

``

78

`+

The TSC meets in a voice conference call. Each year, the TSC elects a chair to

`

``

79

`+

run the meetings. The TSC streams its meetings for public viewing on YouTube or

`

``

80

`+

a similar service.

`

81

81

``

82

``

`-

Items are added to the TSC agenda which are considered contentious or

`

83

``

`-

are modifications of governance, contribution policy, TSC membership,

`

84

``

`-

or release process.

`

``

82

`+

The TSC agenda includes issues that are at an impasse. The intention of the

`

``

83

`+

agenda is not to review or approve all patches. Collaborators review and approve

`

``

84

`+

patches on GitHub.

`

85

85

``

86

``

`-

The intention of the agenda is not to approve or review all patches.

`

87

``

`-

That should happen continuously on GitHub and be handled by the larger

`

88

``

`-

group of Collaborators.

`

``

86

`+

Any community member can create a GitHub issue asking that the TSC review

`

``

87

`+

something. If consensus-seeking fails for an issue, a Collaborator may apply the

`

``

88

`` +

tsc-agenda label. That will add it to the TSC meeting agenda.

``

89

89

``

90

``

`-

Any community member or contributor can ask that something be reviewed by the

`

91

``

`-

TSC by logging a GitHub issue. If consensus-seeking among TSC members fails for

`

92

``

`-

a particular issue, it may be added to the TSC meeting agenda by adding the

`

93

``

`` -

tsc-agenda label.

``

``

90

`+

Before each TSC meeting, the meeting chair will share the agenda with members of

`

``

91

`+

the TSC. TSC members can also add items to the agenda at the beginning of each

`

``

92

`+

meeting. The meeting chair and the TSC cannot veto or remove items.

`

94

93

``

95

``

`-

Prior to each TSC meeting, the meeting chair will share the agenda with

`

96

``

`-

members of the TSC. TSC members can also add items to the agenda at the

`

97

``

`-

beginning of each meeting. The meeting chair and the TSC cannot veto or remove

`

98

``

`-

items.

`

``

94

`+

The TSC may invite people to take part in a non-voting capacity.

`

99

95

``

100

``

`-

The TSC may invite additional persons to participate in a non-voting capacity.

`

``

96

`+

During the meeting, the TSC chair ensures that someone takes minutes. After the

`

``

97

`+

meeting, the TSC chair ensures that someone opens a pull request with the

`

``

98

`+

minutes.

`

101

99

``

102

``

`-

The meeting chair is responsible for ensuring that minutes are taken and that a

`

103

``

`-

pull request with the minutes is submitted after the meeting.

`

104

``

-

105

``

`-

Due to the challenges of scheduling a global meeting with participants in

`

106

``

`-

several time zones, the TSC will seek to resolve as many agenda items as

`

107

``

`-

possible outside of meetings using

`

``

100

`+

The TSC seeks to resolve as many issues as possible outside meetings using

`

108

101

`the TSC issue tracker. The process in

`

109

102

`the issue tracker is:

`

110

103

``

111

104

`* A TSC member opens an issue explaining the proposal/issue and @-mentions

`

112

105

`@nodejs/tsc.

`

113

``

`` -

``

114

``

`-

explicit opposition from other TSC members, then the proposal is approved.

`

115

``

`-

`

116

``

`-

either the proposal is dropped or the objecting members are persuaded. If

`

117

``

`-

there is an extended impasse, a motion for a vote may be made.

`

``

106

`+

`

``

107

`+

and no TSC opposition.

`

``

108

`+

`

118

109

``

119

110

`## Collaborator Nominations

`

120

111

``