@@ -110,36 +110,6 @@ the team membership shares an employer, then the situation must be
110
110
immediately remedied by the resignation or removal of one or more team
111
111
members affiliated with the over-represented employer(s).
112
112
113
- ## Team Meetings
114
-
115
- The team meets weekly on a Zoom On Air. A designated moderator
116
- approved by the team runs the meeting. Each meeting should be
117
- published to [ YouTube] ( https://www.youtube.com/c/nodejs-foundation/streams ) .
118
-
119
- Items are added to the team agenda that are considered contentious or
120
- are modifications of governance, contribution policy, team membership,
121
- or release process.
122
-
123
- The intention of the agenda is not to approve or review all patches;
124
- that should happen continuously on GitHub and be handled by the larger
125
- group of Collaborators.
126
-
127
- Any community member or contributor can ask that something be added to
128
- the next meeting's agenda by logging a GitHub Issue. Any Collaborator,
129
- team member or the moderator can add the item to the agenda by adding
130
- the *** performance-agenda*** tag to the issue.
131
-
132
- Prior to each team meeting the moderator will share the Agenda with
133
- members of the team. Team members can add any items they like to the
134
- agenda at the beginning of each meeting. The moderator and the team
135
- cannot veto or remove items.
136
-
137
- The team may invite persons or representatives from certain projects to
138
- participate in a non-voting capacity.
139
-
140
- The moderator is responsible for summarizing the discussion of each
141
- agenda item and sends it as a pull request after the meeting.
142
-
143
113
## Consensus Seeking Process
144
114
145
115
The Performance Team follows a [ Consensus Seeking] [ ] decision-making model.
0 commit comments