The user bio should be Markdown enabled with the
``mediagoblin.util.cleaned_markdown_conversion()`` function.

Proposal:


-  Add a field to User (``mediagoblin/db/models.py``) which is
   named ``bio_html`` (see the description\_html field in
   ``MediaEntry`` [same file] for refernce).
-  When the user updates the bio field
   (``mediagoblin/edit/views.py:edit_profile()``), run the
   ``cleaned_markdown_conversion()`` and put the output in the
   ``bio_html`` field.
-  Edit ``mediagoblin/templates/mediagoblin/utils/profile.html`` to
   output ``user.bio_html`` instead of ``user.bio`` and to NOT
   autoescape the output of ``{{ user.bio_html }}`` (see
   @mediagoblin/templates/mediagoblin/user\_pages/media.html for
   reference).

Mongokit's migrations system stuff is complex and way confusing.
Here's something much simpler.


-  migrations are simple functions, iterated by number. You create
   them and register them with a decorator registering what "number"
   they are like so:

   @register\_migration(1) def ponies\_to\_unicorns(database):
   database['quadrapeds'].find( {'animal': 'pony'}).update{ {'$set':
   {'animal': 'unicorn'}})


or whatever else you need to do with that connection. The first and
only argument passed in (database) is a simple pymongo database
connection (**not** mongokit!). Otherwise, it's just a simple
python function. Do what you need to do.


-  current migration status is stored in the ['\_id'] =
   'mediagoblin' document of database['app\_metadata'] in the field
   ['migration\_number']
-  if no migrations have been run yet, migration\_number set to
   current max
-  otherwise all unrun migrations are run, and migration\_number
   updated after each migration finishes.

Currently, there is none;
`http://i.imgur.com/DeucS.png <http://i.imgur.com/DeucS.png>`_