db/migrations.py has this:

from mediagoblin.db.models import (MediaEntry, Collection, MediaComment, User,
        Privilege)

This is a big NO! Those are the current variansts of those tables. Not the versions needed in any old migration. Those current tables could have changed in a completely unexpected way and break old migrations.

If there are migration docs, please add a note about this.

The current main use of the above imports is code like this:

creator = Column(Integer, ForeignKey(User.id), nullable=False)

This can be easily fixed:

creator = Column(Integer, ForeignKey('core__users.id'), nullable=False)

When this is done, please take a look at add_new_notification_tables():

    user_table = inspect_table(metadata, 'core__users')
    mediaentry_table = inspect_table(metadata, 'core__media_entries')
    mediacomment_table = inspect_table(metadata, 'core__media_comments')

This code might be useless.

After fixing all of this, please make sure the migrations still work.

Add a collection option to 'addmedia' command line uploading functionnality. Specify the collection with its slug.

Use like this:

gmg addmedia user file.jpg -c collection-slug

​Here's the patch

This is my first contribution, please tell me what I did wrong :-)

jpope has implemented an excellent "sandy 70s speedboat" theme: ​http://whird.jpope.org/sandy-seventies-speedboat-mediagoblin-theme/

We should try to incorporate this in MediaGoblin proper for the next release. It looks pretty awesome!