We have a new wiki. The migration is not 100% complete. You can help out by moving pages across. This wiki will exist for as long as there are pages left.
The official documentation has moved to http://docs.couchdb.org — The transition is not 100% complete, but http://docs.couchdb.org should be seen as having the latest info. In some cases, the wiki still has some more or older info on certain topics inside CouchDB.
Please follow these steps if you have questions, think you have found a bug or have any other comments about CouchDB.
Has it happened before or already been answered?
Search the mailing lists. Enter search terms at http://couchdb.markmail.org
Search the bug tracking system at https://issues.apache.org/jira/browse/COUCHDB
The wiki also has many useful guides and can also be searched (look in top right)
Preparing your question
In order for people to help you, please prepare your question. Your goal is for the people who can answer to understand what you are doing with CouchDB, what you see and what you expected to see. You should also include platform information (eg Windows or Linux), version information (which version of Couchdb), libraries and tools in use (eg are you talking directly to CouchDB using curl or a library such as python-couchdb). These two links are helpful guides:
Asking the question
The best place to get help, ask questions and receive answers is the CouchDB users mailing list. Please post your question in only one place. (If you post it in multiple places then answerers won't see each others responses, people will be discouraged from answering suspecting they will be duplicating answers elsewhere, followups are fragmented etc.)
Make sure you will be able to see answers before posting. For example you may want to subscribe to the mailing list, or bookmark the GMane page. Ensure you keep checking back. You should see answers or there may be more questions asking for further information in order to provide a better answer. It is appreciated if you respond in a timely manner.
Once the issue or question is resolved it may be appropriate to post a followup summary. Imagine that someone else in the future had the same thoughts as you so make the post easy to find via searches and for them to understand the resolution. For example it may have been a bug in your code so you can say how to test for it or prevent it in the future, or it may be a bug in CouchDB in which case point to the ticket, or a wiki page may have been updated or created.