mattl: is there any chance you could make users for the movable
type instance for willkg, freedeb, myself? If you'd like to have a
phone call about this soonish, maybe we can figure out how this is
going to happen website-wise

I'm putting this in the Support tracker... though I'm not entirely
sure whether that's right.

Assigning this to Matt.

Add / adjust copyright headers on all files.


-  Python files already have appropriate AGPL header, except need
   adjustment to provide exception for HTML (maybe also CSS for the
   sake of clarity?) files. See:
   `http://www.gnu.org/licenses/gpl-faq.html#WMS <http://www.gnu.org/licenses/gpl-faq.html#WMS>`_
   though we will probably need to make some adjustments to that.
-  HTML templates should contain CC0 header. See:
   `http://wiki.creativecommons.org/CC0\_FAQ#May\_I\_apply\_CC0\_to\_computer\_software.3F\_If\_so.2C\_is\_there\_a\_recommended\_implementation.3F <http://wiki.creativecommons.org/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F>`_
-  Move COPYING to AGPLv3.txt
-  Download
   CC0\_1.0.txt:http://creativecommons.org/publicdomain/zero/1.0/legalcode.txt
-  Create a new COPYING which describes that python code is under
   AGPLv3 (AGPLv3.txt) w/ exception for HTML templates, Javascript
   under AGPLv3 w/ exception for HTML, and HTML templates / images /
   CSS of base theme all under CC0 (CC0\_1.0.txt)

If we end up having CSS files by the time this is written we should
also add headers to these, but do this in the style listed at the
bottom of this post:
`https://creativecommons.org/weblog/entry/27094 <https://creativecommons.org/weblog/entry/27094>`_

This one specifically assigned to cwebber :)

Continue / finish writing workflow.rst in the docs directory of
mediagoblin (refactoring these into different files is fine, but
that's what it is at the moment).

Describe:


-  (WSGI) Application structure
-  Media submission process
-  Media conversion/processing process
-  Multiple media type handling for display/submission/processing
   and what writing extensions for this will look like
-  Maybe a bit about plugins vision but that's not currently
   critical

And optionally other things that seem appropriate.