Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »


Finalize sphinx documentation practice


Justin Deoliveira



Sphinx documentation process

This page represents the current plan; for discussion please check the tracker link above.



This proposal outlines a process for generating and managing project documentation with Sphinx.

Doc Organization

Documentation will be organized into three categories:

#. user guide
#. developer guide
#. web site

And reorganized in svn as follows:

Doc Generation

The maven build will be updated to build documentation. This will involve having maven invoke the sphinx-build utility (through ant). With this building documentation will be no different than building a regular module.

Doc Assembly

The assembly process that produces the bin and src artifacts will be updated. A third assembly will be added for the user guide. And potentially a fourth for the developer guide.

Doc Continuous Build

The hudson server will be updated to build docs continuously in the same manner the rest of the code base is built when changes occur. On successful builds the latest version of the documentation will be published.






no progress






lack mandate/funds/time


volunteer needed

  1. Reorganize docs in svn (tick)
  2. Add doc generation to maven build (tick)
  3. Update assembly to produce doc artifacts (tick)
  4. Add doc build to build server (tick)
  5. Modify doc build to push out new website on updates(tick)
  6. Port wiki content (tick)

API Changes


Documentation Changes

Docs currently living in web will be separated and moved into docs.

  • No labels