GammaLib

FYI: with this one I screwed up a bit, because I ran pandoc without replacing the \newcommand first.
So there might be a few “GammaLib” words simply missing from the text.
Probably still easier to read it through once (I did that, but quickly) than to start the conversion from scratch.

Right, I left it “In Progress” for this reason. I guess we need to scan the .rst files to improve this.

I also see that the entire User Manual is a single flat file (here index.rst). I guess it would be nice if it were structured, so that pages are much shorter. What do you think?

Yes. Definitely break up into smaller chunks.
Same with the coding conventions.

It might be better to work out a structure for the documentation first and then refactor existing parts into that.
I think e.g. astropy has a good webpage and well-structured documentation and could serve as an example:

http://www.astropy.org
http://docs.astropy.org

I’m happy to contribute after the HESS collaboration meeting next week.
I’m not familiar enough with the Gammalib codebase to make good contributions, but e.g. rewriting existing examples into tutorials is something I can do.

Some more examples of documentation I like:

http://scikit-image.org/
http://scikit-learn.org/
http://pandas.pydata.org/pandas-docs/stable/

We should also find a way to link to Doxygen API docs from Sphinx.
This is not quite what we want I think, but might be worth a look:
http://michaeljones.github.io/breathe/