To be very concrete: I think my proposal is just to exercise a bit of empathy towards other work and when you are asked "let's discuss it on a devlist" because it's a complex case, with huge impact (and effort needed) and potentially disruptive and where many people will like have opinion, let's just do it. Especially if the previous incarnation of it has already been discussed and actions taken.
To the "bike shed color argument" of Ash. Yes, maybe choosing a color seems like bike-shed discussion, but when you want to repaint your whole house in a different colour while there are about a 100 people at the same time in your flat moving the furniture, polishing the floor, changing the windows and replacing door-knobs. You painted half of the flat and you prepared it carefully and planned around all the other work so that the places you already painted can be safely used by those 100s of people while you are painting the rest of the house. You agreed the color with every stakeholder and you found a good one you paint it with, and it took weeks to paint half of the house and the rest is planned. Then you have one of the tenants come and say "I do not like the green, let's make it red altogether". Surely you do not want to jump on it, and do it straight away or even discuss the new colour on the corridor with that one stakeholder. And certainly you do not want to repaint it all over again while splashing the paint on all the people that are at the same time in the rooms that you already painted. Likely you want to gather those stakeholders afterwards and agree on a new colour - but possibly in a bit calmer way, after all the frenzy is done. And maybe even start discussing on the new colour, and whether it makes sense at all, or maybe the current green colour is really acceptable, and only one of the tenants has a different opinion and the rest prefers green? It would seem so from the previous discussions, let's check it on devlist. That is my proposal. J. On Wed, Mar 26, 2025 at 6:07 PM Daniel Standish <daniel.stand...@astronomer.io.invalid> wrote: > BUT LET ME ADD > > Can anyone sort of try to focus the discussion here a bit? > > Is there anything specific being proposed? > > On Wed, Mar 26, 2025 at 9:58 AM Daniel Standish < > daniel.stand...@astronomer.io> wrote: > > > I think that many times, you only bring things to list after they reach a > > certain level of maturity. Sometimes on slack etc you are just working > out > > how you feel about something, trying to understand something. I think it > > is perfectly fine to have such conversations on slack. > > > > Perhaps you find that there is consensus but you want to inform folks on > > dev list. Then you can make a lazy consensus thread. > > > > Perhaps you find that there is disagreement and you need community input > > to help resolve. Then you can make a discuss thread. > > > > Or perhaps you realize that there is more or less agreement (or > > disagreement but acceptance) and there is no need to bring it to list. > > > > All such outcomes are possible. > > >
