I'm definitely in favour of building up the docs/ effort to replace the wiki as *the* place to find out how couchdb works. I can't quite picture what will be left of the wiki when that's achieved. I guess the pages where we list contributors and couchdb-based projects, but not too much else.
I'm -0.9 (see http://www.apache.org/foundation/voting.html) on switching to Confluence. The choice of wiki technology is a tiny factor, in my opinion. No wiki is useful without active maintenance. Unless there's a horde of editors just waiting for the switch before they'll help out, I think it's a distraction from the real issue. B. On 9 May 2013 11:46, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: >> Anyway, I'm really excited about CouchDB and I really want to contribute to >> the global documentation out there, but MoinMoin ain't making it easy. I >> really think that a move to a better documentation tool could be a huge >> push to CouchDB's adoption. Thanks for listening. > > Have you seen the new Sphinx-based docs? I think they're a huge > improvement over both the wiki and the book drafts. Personally, I > think it would make a lot of sense to invest more time in those, > rather than moving wiki content around. We could port wiki content > that's missing from the docs to reST so it gets included in every > CouchDB release (where it's easily accessible through Futon). > > I think the biggest problem with the wiki is that wikis require a lot > of what I tend to think of as "gardening" to make them easy to > navigate. I don't think MoinMoin is the larger problem here (though I > tend to agree that it's pretty unattractive). > > If we want to go one step further with reST, it would even be possible > to have similar handling for the blog. I use Pelican for my personal > blog and it uses reST as well. We could have a directory "blog" in the > tree somewhere where people can collaborate on blog entries which > subsequently get published to the interwebz. > > Cheers, > > Dirkjan
