You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying for a while to work out how we can help lower the barrier to entry for this WG, and nodejs/TSC#392 and the setup of the nodejs/automation team means now seems like a good time to suggest this.
Proposal
Split the test-access part of Build membership (and access to the secrets repo) into a subteam of build (in the same way we currently do release-access and infra-access). Then we can add people to the Build WG without worrying about who they are.
The text was updated successfully, but these errors were encountered:
I've been trying for a while to work out how we can help lower the barrier to entry for this WG, and nodejs/TSC#392 and the setup of the nodejs/automation team means now seems like a good time to suggest this.
Proposal
Split the test-access part of Build membership (and access to the secrets repo) into a subteam of build (in the same way we currently do release-access and infra-access). Then we can add people to the Build WG without worrying about who they are.
The text was updated successfully, but these errors were encountered: