Hi Matt, I suggested the resources keeping in mind the ease with which one can learn. My idea was not to disrespect Apache or community in any form, it was just to facilitate learning of a Newbie. While having a good wiki would be amazing and I believe we all agree on this Thread that current Documentation has a lot of scope for improvement. And I'm completely willing to contribute in whatever way possible to the docs and getting it reviewed.
Best Regards, Bhuvan On Mon, Jun 13, 2016 at 8:17 PM, Eric Evans <john.eric.ev...@gmail.com> wrote: > On Mon, Jun 13, 2016 at 8:05 AM, Mattmann, Chris A (3980) > <chris.a.mattm...@jpl.nasa.gov> wrote: > > However also see that besides the current documentation, there needs to > be > > a roadmap for making Apache Cassandra and *its* documentation (not > *DataStax’s*) > > up to par for a basic user to build, deploy and run Cassandra. I don’t > think that’s > > the current case, is it? > > There is CASSANDRA-8700 > (https://issues.apache.org/jira/browse/CASSANDRA-8700), which is a > step in this direction I hope. > > One concern I do have though is that changing the tech used to > author/publish documentation won't in itself be enough to get good > docs. In fact, moving the docs in-tree raises the barrier to > contribution in the sense that instead of mashing 'Edit', you have to > put together a patch and have it reviewed. > > That said, I also think that we've historically set the bar way too > high to committer/PMC, and that this may be an opportunity to change > that; There ought to be a path to the PMC for documentation authors > and translators (and this is typical in other projects). So, I will > personally do my best to set aside some time each week to review and > merge documentation changes, and to champion regular doc contributors > for committership. Hopefully there are others willing to do the same! > > > -- > Eric Evans > john.eric.ev...@gmail.com >
