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 ju
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 leve
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 th
IMO having the discussion on Github has very helpful for me. That's just
the first place we look for.
And if been asked on why was "*this particular change*" was made, I
can answer it brought up a discussion on the dev list and the
community voted on it.
In a gist, I don't have a problem with the
> So I’m not sure what you are actually proposing, since we already do make
important decisions on the list, and that discussing the minutia of every
decision isn’t practical.
I think it's really a question of the impact it has. In this case changing
the layout of the repo (as I tried to explain h
> On 23 Mar 2025, at 03:44, Jarek Potiuk wrote:
>
> The thread here was sparked with a slack discussion where TP
> commented essentially "we should change our layout of folder, I do not like
> the lack of consistency" - in a random slack conversation, that many of us
> could have missed. And I
OK. Let me clarify then,
1) First of all - yes - i completely missed cadwyn and API versioning we
agreed to in the AIP. We had so many of those AIPs that I simply forgot
this tiny-little detail. Totally my fault and sorry for calling that one
out. Sorry Ash for that if you felt you've been called
I completely agree regarding transparency, having options expressed in
writing, and tracking decisions.
I also support the ASF philosophy that voting should only happen on the dev
list.
However, treating the dev list as the only acceptable mechanism for
discussion feels overly burdensome, in my h
+1, I fully agree with the mechanism - it is open, transparent, gives
everyone an opportunity to participate, and keeps track of how the
decisions are made.
On Sat, Mar 22, 2025 at 5:34 PM Shahar Epstein wrote:
> Overall I agree that decisions should be made in the devlist.
> One improvement tha
Overall I agree that decisions should be made in the devlist.
One improvement that I'd like to suggest, though, is to have a dedicated
page on cwiki that summarizes all recent and upcoming decisions (votes +
lazy consensus) in a table, including links to their respective devlist
threads. We could h
I also would like to start another thread regarding decision making in our
projects. We had some discussions about decision making in our project.
As an ASF project we are supposed to make important decisions on the
devlist. Full stop. "If it did not happen at the devlist, it did not
happen" is so
11 matches
Mail list logo
