*bump*
Mick - could you enumerate the list of tools you mentioned earlier?
Dinesh
On Sunday, September 23, 2018, 6:22:48 PM PDT, Dinesh Joshi
<dinesh.jo...@yahoo.com.INVALID> wrote:
Hi Mick,
Thanks for the feedback. Please find my clarifications inline.
> There's also been suggestions to take a step away from any focus on code and
> go back to documentation and brainstorming. I appreciate the work already
> done in the gdoc, but there's a lot left to the imagination (or just not
> properly summarised in one place).
As I mentioned in my previous emails, the gdoc was just a starting point for a
discussion / brainstorming.
> So could we take a step back from even designing and go to brainstorming.
> Examples questions i can think of are running through the different scenarios
> we're thinking of improving/solving, surveying the different C* tooling out
> there and what they solve, need or could benefit from, ("feature set,
> maturity, maintainer availability, etc"). I can think of a number of tools
> already that provide the ability for cluster-wide commands. Such a page
> listing all the tools and what they offer would be of benefit to the
> community.
Great point, I would appreciate enumerating the list of tools you know. This is
the kind of feedback we would've liked on the gdoc. We can look at all the
features they provide. However, I am curious other than looking at the feature
set, what is the motivation for surveying these tools?
> But I also thought we agreed to take a piecemeal approach between solutions,
> rather than jumping in and developing the one and only defined sub-task from
> scratch.
Yes I think we have a consensus on the piecemeal approach (if something doesn't
agree, please speak up!).
> And I can't say I'm a huge fan of google doc. Any chance we could be
> collaborating in the Cassandra wiki instead?
> https://cwiki.apache.org/confluence/display/CASSANDRA
Sure, I don't think I have a particular preference for gdoc. It's easier to
collaborate. I am not sure if everyone has write access to the apache wiki. It
also requires a separate account.
I also haven't seen a process to propose & discuss larger changes to Cassandra.
The Cassandra contribution[1] guide possibly needs to be updated. Some
communities have a process which facilitate things. See Kafka Improvement
Process[2], Spark Improvement Process[3].
Thanks,
Dinesh
[1] http://cassandra.apache.org/doc/latest/development/index.html
[2]
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
[3] http://spark.apache.org/improvement-proposals.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
