couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: Docs, second try
Date Wed, 01 Aug 2012 12:00:17 GMT

Texinfo is important because we are using Autotools, and it expects texinfo
so it can install info pages. Autotools comes with a toolchain which will
convert texinfo into other formats for you, for free. The user doesn't need
anything installed locally on their machine. This is why I listed it as a
requirement for the docs solution we pick. Fortunately, Sphinx satisfies
this, which is why I am pleased.

What is Pytohn nirvana? Is that related to the Sphinx effort I checked out
towards the end of this thread?

I think once the docs are converted to RST and the Sphinx work looks okay,
we should merge this into master, and I am offering to take over from
there. I will happily integrate this into the build system, hook it up with
Futon, update the README files, etc.

What is standing between here and there?

What is there left to do before we can get the Sphinx work into master for
further iteration?

On Wed, Aug 1, 2012 at 12:28 PM, Dirkjan Ochtman <> wrote:

> On Wed, Aug 1, 2012 at 1:11 PM, Dave Cottlehuber <> wrote:
> > Do we have a concensus now to go for RST & python nirvana?
> If we do, a proposed plan forward, with Dave and Robert N.:
> - Keep the docs branch as it is, with DocBook docs
> - Iterate on the Sphinx docs in the docs branch (for example based on my
> csets)
> - When everything has properly been converted to Sphinx, remove DocBook
> files
> - At this point, merge docs into master and do further improvement
> This means the DocBook version is safely in repository history for
> archival purposes. Sphinx building can easily be integrated into
> Makefiles, we'll also need to update some READMEs etc to document
> Sphinx dependencies. We should probably not wait until the docs are
> perfect before merging into master, but make sure everything from the
> DocBook version is in there.
> I'll note that I think the pace of movement around the Sphinx stuff
> indicates that this significantly helps contribution to the docs, so I
> think this would be a great way to move forward.
> Cheers,
> Dirkjan


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message