Hi, > > If there is a true emergency then sure, go ahead an upload a package > > without coordination. But this wasn't so urgent, Santiago could have > > easily waited one or two days instead of the 2h he did now. Just > > waiting a bit longer isn't that much extra work, it is just a matter > > of taking a break and context switching back a couple of days later. > > I understand your point, but there are a few considerations here. There > aren't many active uploaders in the Go team, as you may have noticed > from the activity on the mailing list. Many of us are contributing in > our free time, which can be unpredictable. For example, if I know that I > won't have availability in the next few days, I might choose to complete > the task now while I have the chance.
To me the paragraph above reads that you don't understand my point about coordination, but instead you are suggesting that if I choose to give less of my own volunteer time to Go team, I can skimp on coordinating work with others and spend that lesser amount of time purely on committing changes and uploading them? > Even if the upload had been delayed, I’m not sure it would have been > picked up by anyone else much sooner. As you may have observed from the > response times on your own threads, it often takes longer to get a > reply, especially when people are working on different schedules. I will reply to this in 30 days from now. > Granted this is holiday season and a CVE reported, I felt it was OK to > upload. The commit picked up in question is an upstream patch here, so I > don't see a need for a second review unless we don't trust upstream to > do their job properly. Holiday season does not really have to do anything here. Some people might do more Debian work, others less. Regardless you should at least wait until the next day, nobody is going to reply to messages within hours regardless of season. > Your point does make a lot of sense in teams where there's a very high > amount of activity (like python for instance) but this is not one of those. Go team is big enough to not use team size as an excuse. This very email thread proves that multiple people replied within 12 hours of the first message. Go team has 301 members, and there have been 3058 MRs posted (https://salsa.debian.org/groups/go-team/-/merge_requests). Python has 507 members and 2235 MRs (https://salsa.debian.org/groups/python-team/packages/-/merge_requests). Also the team size does not really matter. The Developers Reference I mentioned earlier and the process of NMUs there have the same suggested wait times regardless of what is the team size. Also when you think about it, the team size does not really affect how quickly or slowly for example Anthony (the maintainer of the GH package) replies and what is socially a sensible time to wait after sending an email to be able to conclude if that person is nowadays active in Debian or not.
