Dinesh,
> Most of the discussion and work was done off the mailing list - there's a
> big risk involved when folks disappear for months at a time and resurface
> with big pile of code plus an agenda that you failed to loop everyone in
> on.
Given all the discussions that have been had offline at this year's DD
conference, I hope that we don't repeat the same mistake and fail to put a
summary (more than just Sankalp's words below) out so that we're all on the
same page and others have a chance to agree/disagree. "If it didn't happen on
the mailing list it didn't happen."
> In addition, by your own words the design document didn't accurately
> describe what was being built.
There's been confusion over the different cassandra tickets and what they cover
and how they overlap.
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).
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. 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.
It would be nice to see some horizon on this, to thrash out the landscape, and
better understand where we're first choosing to head and why. Making it a more
inclusive approach will also help get consensus, and hopefully post-freeze get
more people involved. ("measure twice, cut once")
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
regards,
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
