On Thu, 2025-01-23 at 17:24 -0800, Otto Kekäläinen wrote: > Can we agree to update the Go team policy to follow this and default > to 'debian/latest' going forward? I'll prefix this with a disclaimer that I haven't fully followed the discussion on proposed workflow changes the past several months across different email threads, due largely to wanting to spend my "Debian time" on other tasks and a general willingness to follow group consensus on changes to team workflows. But I was tagged on a MR & PR today, and I wanted to respond here rather than across github/salsa. I think it's pretty clear that there is strong disagreement with changing the default git branch name, both among this team as well as the broader Debian community. There's also disagreement about the other changes, and I support reverting things, at least for the moment. From most of what I've seen Otto propose, it seems that he's wanting to push for use of more modern software engineering practices like you might find at a good software engineering company. I think that's a commendable goal, but a single person can't force such changes in Debian. When working as a paid employee, a manager can dictate how MRs are reviewed, repo layout, etc are handled, and if I refuse to follow I can expect to be fired. In Debian, most of us are working as volunteers, on our own time. Making changes to workflows require group buy-in, as there's really no other way to get people to follow along. Attempting to force the issue will either cause people to retreat and do less team-packaging work, or dig in their heels and refuse to consider any changes. Mathias
Attachment:
signature.asc
Description: This is a digitally signed message part