We don't seem to have a clear idea how users get access to some sort of "dashboard" of what's going on... both as in terms of how they update their stuff and how they have access to "actions" of things to do. The ideas that have appeared or gone so far in MediaGoblin are:

• The user homepage has a link to settings, and also things like recently updated items appear there. Presumably favorites will appear in the future.
• The user previously had a dropdown menu that you could select actions from. (Easy to use from everywhere, probably had accessibility problems, maybe not obvious that it exists, but more applications seem to have these)
• The user has a "dashboard" on the root now which activities can be added to. However, you can't access these from everywhere... and it might not be clear that you have to go to the root to access them again.
• In Nathan Yergler's branch, more options are being added so you can add actions in settings things with navigation hooks: ​http://mediagoblin.com/tag/nav-hooks/ ​https://gitorious.org/~nyergler/mediagoblin/nyerglers-mediagoblin/commit/fc49daf00a7386bea0ac20c6c2ff77233c3a1d94

It seems to me that a combination of things is probably appropriate: a dropdown menu for tasks that you might want to do everywhere, a homepage that is "customized" for your user, the actual user profile page that contains very you-specific stuff that's both publicly visible and et cetera.

But we need a clear design. I'm not sure where the best place to compile that design is, so for now I'm opening this bug until we have some clear mockups and a plan put in place.

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?

1: Our Lost password function reveals if a user name or

an email address is registered, which can be considered a data leak. Should we simply respond and say: "If you have an account here, we have send you your email"?

2: username and email search is case sensitive. Is that

intended? Should we provide helper functions or how do we deal with that?