Jon,
This is considered the start of the problem: https://www.mail-archive.com/dev@cassandra.apache.org/msg09050.html That’s according to this well sourced article called “Fear of Staxit: What next for ASF’s Cassandra as biggest donor cuts back” https://www.theregister.co.uk/2016/11/14/datastax_versus_asf_staxeit/ I am one of the people who didn’t know the history and is now as this article describes, caught between “A Rock and a hard place…: http://www.zdnet.com/article/a-rock-and-a-hard-place-between-scylladb-and-cassandra/ I bet it’s been painful for everyone. It’s really said. Kenneth Brotman From: Jon Haddad [mailto:jonathan.had...@gmail.com] On Behalf Of Jon Haddad Sent: Saturday, February 24, 2018 12:26 PM To: Kenneth Brotman Subject: Re: Gathering / Curating / Organizing Cassandra Best Practices & Patterns I really don’t want to continue this discussion any further on the ML, because I used to work at DataStax and I’d rather not have this turn into a mess. Take a look at the closed JIRAS and git history, they’re mostly pulled out of Apache Cassandra development and ship their own fork. They are done contributing docs as well. https://www.datastax.com/2016/11/serving-customers-serving-the-community Any discussion on the matter is a waste of time, so this is the last email from me on the topic. Jon On Feb 24, 2018, at 12:08 PM, Kenneth Brotman <kenbrot...@yahoo.com.INVALID> wrote: Hey Jon, If that was the issue the whole time, it’s a big nothing to fix. All DataStax and Apache Foundation ever had to do, and it’s really really easy, is execute a property rights sharing agreement that makes everyone comfortable and protects the parties from being controlled by the other party. Super, super easy stuff to work out WHEN you have two parties that want it to work out. If they would just do that we could go back to being one big healthy family. I could work that out with them. I’ve done this type of thing before. I’m not kidding it’s really easy. Just so you know. Just for the record. Just in case the right people are following along. Kenneth Brotman From: Jon Haddad [mailto:jonathan.had...@gmail.com] On Behalf Of Jon Haddad Sent: Saturday, February 24, 2018 10:44 AM To: user@cassandra.apache.org Subject: Re: Gathering / Curating / Organizing Cassandra Best Practices & Patterns DataStax academy is great but no, no work needs to be or should be aligned with it. Datastax is an independent company trying to make a profit, they could yank their docs at any time. There’s a reason why we started doing the docs in-tree, there was too much of a reliance on DS documentation. DataStax isn’t Cassandra. On Feb 24, 2018, at 10:42 AM, Kenneth Brotman < <mailto:kenbrot...@yahoo.com.INVALID> kenbrot...@yahoo.com.INVALID> wrote: Any efforts described below should be aligned with, complement, enhance, fill in the outstanding work of DataStax Academy. Kenneth Brotman From: Kenneth Brotman [ <mailto:kenbrot...@yahoo.com> mailto:kenbrot...@yahoo.com] Sent: Saturday, February 24, 2018 10:16 AM To: ' <mailto:user@cassandra.apache.org> user@cassandra.apache.org' Subject: RE: Gathering / Curating / Organizing Cassandra Best Practices & Patterns To Rahul, This is your official email (just from me as an individual) requesting your assistance to help solve the knowledge management problem. I can appreciate the work you put into the Awesome Cassandra list. It is difficult to keep everything up to date. I’ve been there too. The golden trophy if you want to do the absolute best thing is a full-fledged professional development initiative for Cassandra. From an instructional design view, what you do is create a body of knowledge and exhaustive list of competencies, some call KSA’s: knowledge, skills and abilities; then you do a gap analysis to find the areas in practice where gaps exists between the competencies desired and those of practitioners, then generate a mix of media for difference learning styles in a structured properly sequenced series of easy to work through steps complete with apperception exercises, and everyone will then have a smooth path towards mastery. It’s that easy. So, yes let’s turn it up a few notches. Thank you, Kenneth Brotman -- Rahul Singh <mailto:rahul.si...@anant.us> rahul.si...@anant.us Anant Corporation On Feb 23, 2018, 5:56 PM -0500, Carl Mueller < <mailto:carl.muel...@smartthings.com> carl.muel...@smartthings.com>, wrote: Isn't a github markdown site about the most easiest collaborative platform there is for stuff like this? I'm not saying the end product will knock anyone's socks off. On Thu, Feb 22, 2018 at 10:55 AM, Rahul Singh < <mailto:rahul.xavier.si...@gmail.com> rahul.xavier.si...@gmail.com> wrote: There’s always a reason to complain if you aren’t paying for something. There’s always a reason to complain if you are paying for something. TLDR; If you want to help curate / organize / gather knowledge about Cassandra, send me an email. I’d love to solve at least the knowledge management problem. Complaining itself is not a solution or a step in the right direction. Defining an issue helps by identifying specifically what the pain is and a decision can be made to resolve or not resolve it.
