Let me start off my comments with setting the general context: Pootle is
a volunteer-driven project. What the volunteers contributing to it can
do, and want to do is really up to that team.
It's also open-source, so you can contribute patches, if you want to
scratch an itch.
> <1> Test the working of mozilla locamotion on all different available
> browsers to avoid 500 internal server error.
Quite frankly, that's a non-goal for the mozilla-focused installation.
If you're a firefox localizer, you should be using Firefox (actually,
Aurora) in your language. If the browser you work on doesn't work for
you, why would it work for anybody else?
For the pootle project in general, it's of course useful to work good in
many browsers, but I guess it's OK to limit this to current versions.
> <2> Show language code against the language name.
What's the exact use-case? The reason I'm asking is that the language
name shows up often, and adding the locale code everywhere would likely
add a good deal of noise to the UI.
> <3> creation of help desk to solve problem quickly if any problem occured
> during hackathon.
There's an irc channel on freenode, #pootle. That's not a help desk,
though. Again, pootle is a volunteer driven effort, if you want
assistance from the pootle guys for your sprint, you'll have to motivate
one of them to get out of bed early, given your timezone. Not
impossible, as they're mostly around UTC natively.
> <4> Sometimes the pootle translation page does not responds- it needs to be
> fixed.
Dwayne and I met at
djangocon.eu (awesome!) this weekend, and there's
some low-hanging fruit to improve responsiveness of the
mozilla.locamotion.org site.
I also overheard a conversation between Arky and Dwayne about UI
feedback on things that happen in ajax. No UI feedback plus interesting
network connections make that problem probably look worse than it might
be. This is harder to fix, of course.
> <5> porting all translations of mozilla projects to locamotion for easy
> translation.
This is blocked on pootle being able to participate in a distributed
effort. That's really far out, and not a high-priority issue, I guess. I
can't see this happening without ripping out significant pieces of the
software toolchain, and replacing them with a different chain. I.e.,
you'd replace A-B-C-D with A-XY-D. That's tough.
>
> And lastly , the event was successful to some extent as we have expected. I
> would like to thanks all people who have directly or indirectly supported
> us in successful completion of the hackathon.A special thanks to Mozilla
> Locamotion and Transifex Developers.
Great to hear. Thanks for the effort and the feedback.
Axel