> I think we need to have a meta discussion about the goal for
> introducing a new process.
Indeed, and these were only two brief examples that came to me. Another, using
the sidecar proposal as an example, is simply to ensure a little patience is
taken during the initial brainstorming and navigation phase, to give more open
collaboration a better chance. What's in the landscape, where's the value, who
might be interested in getting involved in this, etc etc. I think the C*
community has typically been pretty amazing at this, but it would be nice to
see it formalised a bit better.
> By not mandating it, we do not need to define where it is necessary;
> the larger and more impactful the change, the greater the incentive to
> the author.
This is what Scott highlighted well.
Sure, a CEP could be opened with nothing but a title to begin with. And where
it goes from there is up to the working group that materialises. Just to have a
landing space for new features that's not Jira, I believe would be of value.
And in no way should the CEP be a return to waterfall. As you say, late
discoveries and feedback (as annoying as it can be) is all part of the agile
game.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
