On 26/03/26 6:51 pm, Otto Kekäläinen wrote: >> It might be sensible to restrict access to the policy repo to only owners >> to prevent this in the future. > > I'd prefer not to. We can revert changes if needed, but more > importantly we need people to be active - removing permissions from > people who try to be active is the wrong signal and does not help > build a team.
I thought a bit more about it, and so far nobody reverted the changes. Before you call me a holdout again, I did spend _quite some_ time in reviewing new MRs and the merged ones too, on the policy repo, and had many rounds of discussions. I haven't seen comments on those from anyone else (except Nicolas on !15). To be fair, I am extremely uncomfortable for policy changes to be merged and changed so quickly (and for the 42nd time, I don't want to hear that it was open for a few weeks. There really was no team-wide consensus). Realistically, I can't adapt to new workflow(s) that quickly. I still think that access to policy repo (and only this repo) should be restricted. In any case, the current policy changes should probably be reverted **for now**. At the very least https://go-team.pages.debian.net/workflow-changes.html#_2026_03_changes should be renamed to 2026_03_proposed_changes as this right now conveys the wrong message. I'll make a merge request in a week or more if nobody else beats me to it. Thanks! > Actually, the changes that started in 2017 are still not done, and the > main person driving them quit Debian years ago because so many > holdouts was stopping him from doing clearly beneficial work, and > those holdouts didn't do the work either, nor did any of them finalize > the policy changes - neither the policy text itself, nor the tooling > to do it.
