Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 28 Jan 2015 22:32:35 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12770813.1422482969000.199047.1422484354990@Atlassian.JIRA>
In-Reply-To: <JIRA.12770813.1422482969000@Atlassian.JIRA>
References: <JIRA.12770813.1422482969000@Atlassian.JIRA>
 <JIRA.12770813.1422482969907@arcas>
Subject: [jira] [Commented] (CASSANDRA-8700) replace the wiki with docs in
 the git repo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295971#comment-14295971 ] 

Brandon Williams commented on CASSANDRA-8700:
---------------------------------------------

bq. instead of using the wiki, the doc directory in the cassandra repo be used for docs 

The problem with this is, only committers can contribute. If you look at the [contributors group|https://wiki.apache.org/cassandra/ContributorsGroup] on the wiki, it's a pretty long list and regularly people request contributor access (I know because I do the bulk of the adding.)

bq. If the wiki were kept even remotely up to date

I can put you in the contributors group :)  Really though, some of it is, some of it isn't. http://wiki.apache.org/cassandra/ArchitectureGossip for instance is quite accurate.

> replace the wiki with docs in the git repo
> ------------------------------------------
>
>                 Key: CASSANDRA-8700
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8700
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation & website
>            Reporter: Jon Haddad
>            Priority: Minor
>
> The wiki as it stands is pretty terrible.  It takes several minutes to apply a single update, and as a result, it's almost never updated.  The information there has very little context as to what version it applies to.  Most people I've talked to that try to use the information they find there find it is more confusing than helpful.
> I'd like to propose that instead of using the wiki, the doc directory in the cassandra repo be used for docs (already used for CQL3 spec) in a format that can be built to a variety of output formats like HTML / epub / etc.  I won't start the bikeshedding on which markup format is preferable - but there are several options that can work perfectly fine.  I've personally use sphinx w/ restructured text, and markdown.  Both can build easily and as an added bonus be pushed to readthedocs (or something similar) automatically.  For an example, see cqlengine's documentation, which I think is already significantly better than the wiki: http://cqlengine.readthedocs.org/en/latest/
> In addition to being overall easier to maintain, putting the documentation in the git repo adds context, since it evolves with the versions of Cassandra.
> If the wiki were kept even remotely up to date, I wouldn't bother with this, but not having at least some basic documentation in the repo, or anywhere associated with the project, is frustrating.
> For reference, the last 3 updates were:
> 1/15/15 - updating committers list
> 1/08/15 - updating contributers and how to contribute
> 12/16/14 - added a link to CQL docs from wiki frontpage (by me)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)