Comments on a photo should appear above the new comment form

[Karen Rustad]

Right now, comments only appear after the new comment form on the
photo page. This makes them really easy to miss, so far down the
page.

Let's put the comments ahead of the new comment form -- so you
(hopefully) read what other people have written before writing
something new!

[Christopher Allan Webber]

There's an opposite potential problem here that hasn't been raised.
If you have 30 comments to a page, you might never reach the
comment form, and we want people to talk.

Then again, that doesn't seem to be a problem here:
`http://creativecommons.org/weblog/entry/28403#comments <http://creativecommons.org/weblog/entry/28403#comments>`_

Curious what others think.

[Christopher Allan Webber]

I guess we should do this after all :)

Robin, not sure if you're still around to do it..

[Christopher Allan Webber]

(Adding Jef to see if he has commentary though)

[Robin Holler]

Still around here, still willing to help (definitely), but damn, my
bachelor thesis is detaining me ... have to move through the whole
of germany as well. So sorry, there will be more helpful times
soon! =)

[Christopher Allan Webber]

Ok, thanks for the update Robin!

[Aaron Williamson]

Patch:
`https://gitorious.org/mediagoblin/mediagoblin/merge\_requests/27 <https://gitorious.org/mediagoblin/mediagoblin/merge_requests/27>`_

I also added a link at the top of the comments allowing the user to
jump below the comments to the comment form.

[Elrond]

Hi. I only took a quick look! Generally looks fine.

Could you wrap the trans tag just around the string, not including
the html? It's not wrong the current way, but it would certainly
make translators' life easier.

[Aaron Williamson]

Corrected trans tag issue, updated merge request.

[Elrond]

Merged into my "reviewed" branch, which Chris Webber will hopefully
merge soon.

I've set the version to 0.1.1, as I think, this will go into 0.1.1,
especially, as it's not vital to 0.1.0.

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/469 .