@@ -183,6 +183,34 @@ Collaborators might overlook someone with valuable contributions. In that case,
183183the contributor may open an issue or contact a collaborator to request a
184184nomination.
185185
186+ #### How to review a collaborator nomination
187+
188+ A collaborator nomination can be reviewed in the same way one would review a PR
189+ adding a feature:
190+
191+ * If you see the nomination as something positive to the project, say so!
192+ * If you are neutral, or feel you don't know enough to have an informed opinion,
193+ it's certainly OK to not interact with the nomination.
194+ * If you think the nomination was made too soon, or can be detrimental to the
195+ project, share your concerns, ideally before the public nomination is opened,
196+ and avoid sharing those concerns outside of the Collaborator discussion area.
197+ Ideally, list what step(s) the nominee could take that would make you
198+ approve their nomination.
199+ Given that there is no "Request for changes" feature in discussions and issues,
200+ try to be explicit when your comment is expressing a blocking concern.
201+ Similarly, once the blocking concern has been addressed, explicitly say so.
202+
203+ Our goal is to keep gate-keeping at a minimal, but it cannot be zero since being
204+ a collaborator requires trust (collaborators can start CI jobs, use their veto,
205+ push commits, etc.), so what's the minimal amount is subjective, and there will
206+ be cases where collaborators disagree on whether a nomination should move
207+ forward.
208+
209+ When concerns have been raised on the private discussion, refrain from opening
210+ the public issue. If no one has explicitly blocked the nomination and you'd like
211+ it to move forward, comment something like "If I don't hear any objections
212+ before (some time), I will open the public issue".
213+
186214### Onboarding
187215
188216After the nomination passes, a TSC member onboards the new collaborator. See
0 commit comments