Re: Proposing an Apache Cassandra Management process

2018-08-18 Thread Sankalp Kohli
That’s a good point. Let’s review the patch and when it is ready to commit, we can create the repo then. > On Aug 18, 2018, at 14:04, Stefan Podkowinski wrote: > > I think we do have some consensus that 1) we should give it a try to > have one or many side-car processes for non-essential

Re: Proposing an Apache Cassandra Management process

2018-08-18 Thread Stefan Podkowinski
I think we do have some consensus that 1) we should give it a try to have one or many side-car processes for non-essential features, and that 2) they should be developed in a separate repo. I'm also open to the idea of accepting the proposed implementation as a possible side-car solution and

Re: Proposing an Apache Cassandra Management process

2018-08-18 Thread Sankalp Kohli
The thread for side car is months old and no one has opposed to it and hence someone developed it. I am not sure how else you get consensus. Regarding separate repo, how do we get consensus? > On Aug 18, 2018, at 05:19, Stefan Podkowinski wrote: > > I don't see that we have reached

Re: Proposing an Apache Cassandra Management process

2018-08-18 Thread Stefan Podkowinski
I don't see that we have reached sufficient consensus on this yet. We've had a brief discussion about the pros and cons of in-tree cassandra vs separate ASF repo here, but let's not frame it like it's either or. From my perspective, there hasn't been any final decision yet whether the proposed