osdir.com

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

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


On Wed, Sep 12, 2018 at 10:19 AM sankalp kohli <kohlisankalp@xxxxxxxxx> wrote:
>
> Hi,
>     Community has been discussing about Apache Cassandra Management process
> since April and we had lot of discussion about which approach to take to
> get started. Several contributors have been interested in doing this and we
> need to make a decision of which approach to take.
>
> The current approaches being evaluated are
> a. Donate an existing project to Apache Cassandra like Reaper. If this
> option is selected, we will evaluate various projects and see which one
> fits best.
> b. Take a piecemeal approach and use the features from different OSS
> projects and build a new project.
>
> Available options to vote
> a. +1 to use existing project.
> b. +1 to take piecemeal approach
> c  -1 to both
> d +0 I dont mind either option

As others have pointed out, I think we're placing too much of an
emphasis on voting; What we need is consensus, not a majority ruling.
Obtaining consensus can be difficult, frustrating, and time-consuming,
but IMO always worth it.

My interpretation of the discussion is that there was at least
consensus on the value of a project-supported management stack, as
well as (I think) the notion that it should be kept loosely coupled to
the database, beyond that things seem contentious.

Assuming I'm not wrong, and there is consensus on a loosely-coupled
project, why do we need to rush a decision on inclusion?  What
prevents those who are vested in one approach (or existing project) or
another from working on what they think best?  I suspect developing
consensus here would be a lot easier if we were talking about
something a bit more concrete.

-- 
Eric Evans
john.eric.evans@xxxxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx