Sorry, maybe "rewrite" is not the proper word. I'm taking on a
documentation reorg/fixup as part of [1] and [2], and I'd like to take
this one on too.

[1] https://issues.apache.org/jira/browse/COUCHDB-2350
[2] https://issues.apache.org/jira/browse/COUCHDB-2368

On Mon, Oct 13, 2014 at 9:00 AM, Javier Candeira <[email protected]> wrote:
> I'm currently taking on a documentation rewrite, I'm happy to tackle
> this one too.
>
> On Mon, Oct 13, 2014 at 1:12 AM, Alexander Shorin (JIRA)
> <[email protected]> wrote:
>>
>>     [ 
>> https://issues.apache.org/jira/browse/COUCHDB-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168660#comment-14168660
>>  ]
>>
>> Alexander Shorin commented on COUCHDB-2383:
>> -------------------------------------------
>>
>> Better say: "Install instructions for 2.0 are missed in docs".
>>
>>> Installation instructions are wrong
>>> -----------------------------------
>>>
>>>                 Key: COUCHDB-2383
>>>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2383
>>>             Project: CouchDB
>>>          Issue Type: Bug
>>>      Security Level: public(Regular issues)
>>>          Components: Documentation
>>>            Reporter: Dale Harvey
>>>
>>> As someone who doesnt build couchdb a lot, when I do it is fustrating
>>> I visited http://couchdb.apache.org/, clicked contribute, there was a huge 
>>> wall of text, I think the calls to action should be clearer. I found "Git 
>>> workflow" but it links to an empty wiki page, I then decided to go back and 
>>> through the documentation, I found 
>>> http://docs.couchdb.org/en/1.6.1/install/mac.html, the dependencies are 
>>> wrong, there is little information on installing from source.
>>> I then took a look at 
>>> https://github.com/apache/couchdb/blob/master/INSTALL.Unix, it also had the 
>>> wrong dependencies and no mention of how to start a dev cluster 
>>> (./configure && make && python2 dev/run)
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)

Reply via email to