Skip to content

Conversation

jdm
Copy link
Member

@jdm jdm commented Sep 6, 2025

The Contributor role has lower stakes than a Maintainer role, and nominations often receive lots of support very quickly. We should set a threshold for a nomination having enough support that we don't need to wait the full week.

### Nomination

A **Maintainer** requests the addition of a new **Contributor** in the private *Maintainers* channel in Zulip, listing the number of nontrival contributions by that person. A person may also request that a **Maintainer** nominates them and vouch for them. If no objections are raised within one week, the person is added to the **Contributors** team.
A **Maintainer** requests the addition of a new **Contributor** in the private *Maintainers* channel in Zulip, listing the number of nontrival contributions by that person. A person may also request that a **Maintainer** nominates them and vouch for them. If no objections are raised within one week, the person is added to the **Contributors** team. Additionally, if four other maintainers express support before the week has elapsed then there is no need to wait out the remaining time.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have discussed about this in the TSC call today, it seems it'd be nice to add a minimum of 1 or 2 days of waiting time before we can make someone a contributor, in case someone has any concern to raise. Otherwise a new contributor could be approved in a few hours, without allowing any chance for someone to say anything about that person.

Would you be fine adding something like that to the new proposed text?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants