It'd be nice if maketarball built the docs and put them in the right place to automate generating release tarballs.

Something like this:

1. add support for a -r flag indicating this is a release tarball
2. write the -r code which builds the html and texinfo docs and puts them in the right place in the tarball

Assigning to me and putting in the 0.0.4 target.

This covers some research and also some tweaks to our process. GNU requires that we push tarballs to their ftp server.

http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html

So we need to figure out the following:

1. how do we get set up with that?
2. how do we add it to our release process?

Grabbing this one and putting it in the 0.0.5 target.

We have three separate audiences that we need to write documentation for:

• contributors (developers, hackers, themers, translators, ...)
• site admin (someone who installs MediaGoblin on his/her server to use)
• users (someone who sets up a MediaGoblin account, uploads photos, ...)

Currently, we have documentation in a few different places. We want to migrate to the following:

1. contributor and project infrastructure documentation goes in the wiki.
2. site admin documentation goes in docs/ where it's built in HTML and Texinfo formats for release tarballs; site admin documentation is also available on http://docs.mediagoblin.org/
3. user documentation will be part of the MediaGoblin code probably as Jinja2 templates available through /help/ url or something like that

We want to do this for 0.0.5, but the most important stuff initially is straightening out the contributor docs, then straightening out the site admin docs, then writing user docs.