This ticket exists to track the interaction design of the upload process.

I'll try to start designing this and post iterations to the mailing list to get feedback.

Questions that need to be answered:

• What are the different use cases? What goals do our users have?
• How can we reach these goals in typical awesome GNU MediaGoblin fashion? What steps will the users have to take to upload media?
• What kind of information will they need to provide in the forms? What should be mandatory and what should be optional?
• How do we deal with uploading large amounts of images? How can we provide the best way to upload a single image, several images or a huge number of images?

...etc.

After the design is done we can divide it into smaller parts, check what still needs to be done and report bugs on those issues.

StatusNet has both good writeup of legalcode descriptions of external libraries: https://gitorious.org/statusnet/mainline/blobs/master/README#line90

And also has a good policy for external libraries: https://gitorious.org/statusnet/mainline/blobs/master/extlib/README

Evan has made clear that it's cool (even a good idea) for us to just copy that extlib/README file and adapt it to mediagoblin, and that's what we should do.

We should also find a nice directory to keep these all in, and just use symlinks to move them around to appropriate places (eg, bootstrap.py from zc.buildout can be symlinked to the toplevel of the package, jquery can be symlinked to the mediagoblin static app media directory).