On 22/04/2026 13:18, Simon Josefsson wrote:
Arnaud Rebillout <[email protected]> writes:
On 26/03/2026 19:54, Nilesh Patra wrote:
It might be sensible to restrict access to the policy repo to only owners
to prevent this in the future.
Agreed, that would be a step forward.
As a contrary position: I think the real problem is that we can't seem
to make any progress on any policy changes, not that there are too many
people with write access to the go team policy git repo. Does anyone
with long experience in the Go team have time to shepherd that various
proposals floating around into changes? I think that would be a great
contribution.
I also agree with the problem statement here: people in position to
drive policy changes -- defined as people who are 1) currently active in
go packaging and 2) have long enough experience -- are also not very
active on this kind of discussions.
But letting anyone change the policy with little oversight doesn't fix
this problem. You still don't have the valuable feedback that you hoped
for before you propose a change. And there's still no consensus. Pushing
the changes through nevertheless just weakens the value of the policy.
This is not a progress.
