At least UI Language should be transferred to the website, by menu 'Tools -> Extensions Manager -> Get more Extensions online ...' the link should not simply be <http://extensions.libreoffice.org/>, but
and so on.
It should be easy (with Rob Snelders' help) to gain required info, we already have that in mine 'Help -> Feedback', what creates links like <https://www.libreoffice.org/get-help/bug/?LOversion=188.8.131.52.alpha0&LOlocale=en-US&LOmodule=StartModule>
May be this option should be splitted from this report as an extra Enhancement request.
Also LOversion-info can be useful in a second step to create links like
<http://templates.libreoffice.org/template-center?getCategories=&getCompatibility=LibreOffice+4.0&sort_on=positive_ratings&path=%2FLibreOffice-Templates%2Ftemplate-center&portal_type=PSCProject&SearchableText=>, so that only Templates compatible with LO version will be offered (before User amends query if necessary).
Transfer of UI language should be an EasyHack because most research already has been done for BSA.
I already tested for ar (Arabic) to gl (Galician), it seems that the Extension website always uses English version if a not existing localization (like <http://extensions.libreoffice.org/?set_language=zz>) has been selected.
So we can trail a localized "?set_language=" with the localization after the "=" to all links in 'Tools -> Extensions Manager -> Get more Extensions online ...'
Currently this one has a very low priority because localization is rudimentary on the extensions website, but AFAIK Andreas is working on an improvement.
I separated the Version info enhancement to "Bug 59012 - Transfer LibO Version info to EXTENSIONSWEBSITE"
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyInteresting SkillCpp TopicUI)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
A polite ping, still working on this bug
(In reply to jani from comment #6)
> A polite ping, still working on this bug
Reverting status to NEW, due to other engagement.