And the simplest and easiest thing to do is simply email this list when you see
something wrong or missing in the DataStax Cassandra doc, or for anything that
is not adequately anywhere. I work with the doc people there, so I can make
sure they see corrections and improvements. And simply sharing knowledge on
this list is always a big step forward.
-- Jack Krupansky
From: spa...@gmail.com
Sent: Wednesday, July 23, 2014 4:25 AM
To: user@cassandra.apache.org
Subject: Re: Why is the cassandra documentation such poor quality?
I would like to help out with the documentation of C*. How do I start?
On Wed, Jul 23, 2014 at 12:46 PM, Robert Stupp <sn...@snazy.de> wrote:
Just a note:
If you have suggestions how to improve documentation on the datastax website,
write them an email to d...@datastax.com. They appreciate proposals :)
Am 23.07.2014 um 09:10 schrieb Mark Reddy <mark.re...@boxever.com>:
Hi Kevin,
The difference here is that the Apache Cassandra site is maintained by the
community whereas the DataStax site is maintained by paid employees with a
vested interest in producing documentation.
With DataStax having some comprehensive docs, I guess the desire for people
to maintain the Apache site has dwindled. However, if you are interested in
contributing to it and bringing it back up to standard you can, thus is the
freedom of open source.
Mark
On Wed, Jul 23, 2014 at 2:54 AM, Kevin Burton <bur...@spinn3r.com> wrote:
This document:
https://wiki.apache.org/cassandra/Operations
… for example. Is extremely out dated… does NOT reflect 2.x releases
certainly. Mentions commands that are long since removed/deprecated.
Instead of giving bad documentation, maybe remove this and mark it as
obsolete.
The datastax documentation… is … acceptable I guess. My main criticism
there is that a lot of it it is in their blog.
Kevin
--
Founder/CEO Spinn3r.com
Location: San Francisco, CA
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
--
http://spawgi.wordpress.com
We can do it and do it better.
