[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VOTE] Development Approach for Apache Cassandra Management process

I am hoping all the folks who are saying we should not vote will drive the
other thread.  Also note that there is consensus about doing a side car but
no consensus on which approach to take. I hope not deciding which approach
is not a poison pill for side car!!

On Wed, Sep 12, 2018 at 4:11 PM Mick Semb Wever <mck@xxxxxxxxxx> wrote:

> > But I'd like to see a serious investigation of the options -- feature
> set,
> > maturity, maintainer availability, etc -- before making a decision.  This
> > will take some time, but this is a place where "measure twice, cut once"
> > seems like the right approach.
> This^ 100%.
> I dislike the idea of a vote altogether:
> Discussion should resolve things, accepting something into the community
> that divides (isn't built on consensus) seems an unhealthy thing to do to
> the community. Jonathan's suggestion gives us something productive to do to
> get to consensus.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx