campadrenalin / contentgremlin Goto Github PK

Create a 'task' abstraction that allows us to track file creation processes. Start with just upload. Should have progress reporting.

We should do the right thing when:

• Task continues running after grem has died
• Task finished while grem was offline
• Task completely does not exist (hard reboot, for example - needs to not fail even when a random new process obtains the old PID)

This might be tricky to test, but I'm sure we can mock our way to victory.

Should be fairly placeholder, include an 'upload' button, etc.

This is quite cosmetic, but will be important someday. Sooner for some users than others.

Store all images in a lossless format, but with a max resolution.

Allow owners to store and edit metadata, like description, title, license, etc.

We'll want to support Persona login for anyone with an email address, even if they don't already have an account. We'll want to think how to expose auth plugins to the UI, since they need to be able to create new accounts, not just authenticate existing ones.

We want to be able to upload files via forms. AJAX will be a separate ticket.

We're competing (in a friendly way) with Mediagoblin, which means that on mascot turf, we have to compete with Gavroche. Tough act to follow, especially since we're already walking the line of derivative concepts. I do have some skills with Inkscape, we really just need some good concept art, and a little time investment on my part to vectorize the new mascot/logo.

Should contain 'db.sqlite' and 'contents' dir.

Allow people to comment on media.

Create a tasks AJAX call that can be used to track all uploads and transcodes from any tab. Transcodes themselves may not be available yet.

Use go-bindata to host static files, using the standard production/debug dichotomy. This allows quick development, but makes it easier/more self-contained to revert versions of the static filesystem in a production rollback.

Include iframes fallback stuff, using the same stack as photo uploads at Inspire.

Include transcode progress via ffmpeg

Support locking the old process into read-only mode, cloning and upgrading the DB, shutting down the old process, moving the old db to a backup location, moving the new db in, and starting up from the old process.

Will handle task persistence in another ticket.

Should use 3 tables: users, display_names, and authenticators. In most cases, authenticators will be scrypt-hashed passwords.

Yes, we also need auth plugins.

Support uploading images. This will require creating the plugin infrastructure, which recognizes image types, and rejects unknown types. Do not attempt any transcoding yet.

Much more complex than Persona, so much less of a priority.

Media plugins should also provide a UI, which we can use to see the media.