Tianon Gravi <[email protected]> writes: > 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
+1 I see no reason to deny if a DD wants to help, and think we should even encode this in the policy, something like: "If you are a DD you should consider yourself already part of the Go team and feel welcome to contribute considering normal Debian policies in general and Go team policies in particular". Beyond that, I don't have a strong opinion, beyond a belief based on my own experience with Debian package maintainer teams is that they their presence (with typical unclear membership and contribution rules) is that they acts as a way to exclude people wanting to help. I'd like to see welcoming contributor guidelines that encourage and helps new contributors, rather than membership/accesscontrol rules that exclude people. I think/hope this is what Otto has in mind, though, but framing it as "access control rules" may lead people in the wrong way of thinking. /Simon
signature.asc
Description: PGP signature
