> > Looking at the recently published https://salsa-status.debian.net/ on > > the 30-day view, the spike we had 10 days ago due to Ruby team mass > > changes is over and the base load seems to hover around 300 pipelines > > per day. > > I think that it would be better if we had infrastructure that encourages > teams and maintainers to perform work that improves standardization > across packages maintained by a team, which ultimately improves quality, > rather than send the message that such work is abnormal, and should be > spread over time sufficiently to limit impact.
I didn't write in my message that it "should be spread over time", I simply made a factual statement about how to read the statistics and what conclusion to draw about the stats to estimate the base load in the context of discussing Salsa CI runner load and potential need for more hardware donations. I hope you do realize your statement "better if .. rather than send the message" contains both your interpretation and your reaction to your own interpretation. From my other messages you surely know I am all in favor of simplifying and unifying packaging practices across Debian, and having tooling to do it is great.
