On Thu, 18 Jun 2026 at 05:32, Otto Kekäläinen <[email protected]> wrote: > I would like to improve the situation starting from the Go team, and thus I > want to propose a policy for how team memberships are granted and revoked, > what levels of access exist inside the team, what avenues exist to contribute > without formal access, and how we encourage code reviews as a way to both > onboard new members and keep existing members involved. > > Before I post a draft, I wanted to check if others here think alike and if > having a policy for team membership would be useful? > > Or do people dismiss such things as excess "bureaucracy" and think the > current state of things is just fine, and worrying about potential misuse is > unfounded?
IMO any DD should even be *auto*-accepted into the team -- if they already have access to upload to the archive, we shouldn't give them any barriers to uploading their changes to Git (because that's strictly a net benefit to the team and to the project, even if they do it in a way that isn't exactly in line with our "team preferences"). More generally, it's already hard enough to get folks to contribute at all, and any *extra* barriers we add to doing so only increase the size of that wall. ♥, - Tianon
