L10n:Meetings/BrusselsQ12013: Difference between revisions

(Sandstone design for Elmo, Define proper way of pushing to HG from tools)
Line 20: Line 20:
* Tracking and rewarding l10n contributions
* Tracking and rewarding l10n contributions
* Gaia l10n and l12y
* Gaia l10n and l12y
** Gaia testing: current status and future plans
* Sandstone design for Elmo [Bug 791685]
* Sandstone design for Elmo [Bug 791685]
* Define proper way of pushing to HG from tools
* Define proper way of pushing to HG from tools
* String and reviews. Can l10n's involvement improve the current situation and spot errors before they land and spread confusion on several branches? How can we do that? Maybe it's already covered by the 1st point (e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=831372 or https://bugzilla.mozilla.org/show_bug.cgi?id=809094#c55)
* Can we build a string-only repository that replicates mozilla-central's history?  Possible pros: save time when localizers clone or update, easier/quicker to track the bug responsible for a change. Cons: is it worth it? Is it too complex to create or maintain?
* l10n-web bugs: inconsistent choices (file format, 1 bug per locale vs multilocale bug), who can provide a localization?, etc. (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=822663)


===Logistics===
===Logistics===
Account confirmers, canmove, Confirmed users
2,357

edits