1) Our Meddleware contains a NoOp Meddleware. This seems rather superfluous 2) Our ENABLED_MEDDLEWARE is stored in a tuple rather than a list, so it is not

modifiable.

3) trim_whitespace meddleware plugin

Our HTML output is very verbose (=whitespacy) as our templates are written with an 80 char limit and lots of newlines between blocks, variables etc....

This is a plugin that naively strips of all but the first whitespace from the HTML response. We might want to have an all-fancy html tidy interface here at some point, but it nicely decreases the HTML size about a third on some simple pages.

The formerge/trim_whitespace_plugin branch on ​git://gitorious.org/~spaetz/mediagoblin/spaetz-mediagoblin.git addresses these 3 issues in 3 patches. It would be nice to merge at least no 2 (make ENABLED_MEDDLEWARES modifiable) for this release, so my plugin works and can be distributed separatedly).

What is our policy with regard to plugins? Ship some bundled? Or should I provide them separately?

We will store available (=translated) locales in the form "es_CR". The function get_locale_from_request(request) in tools/translate.py will find the best_match() best on what the webbrowser wants and what we can offer. It will return one of the AVAILABLE_LOCALES items (which we know will be of the form "lc_UP", to there is no need to invoke "locale_to_lower_upper" on every return value. Only invoke that when we parse user input (through the GET/POST parameters to normalize their input).

This is probably not costing too much, but it's one more function that is needlessly called for every request we make.

I found out that the exif-py that GMG use is too old. The new one can read the Nikon EXIF tags without a problem.