L10n/HomePage/Status/2008-02-27
From MozillaWiki
< L10n
« previous week | index | next week »
Meeting Details
- 9:00am Pacific, 12:00pm Eastern
- 650-903-0800 x91 Conf# 206 (US/INTL)
- irc.mozilla.org #l10n-drivers for backchannel
Attendees
Seth, Tim, Wil, Mic, Pascal, Chofmann (late)
Notes
*Firefox 3 Beta 4 - issues
- Patch in ship locales bugs with all new locales for Beta 4
- If we get any updates, we can add them after
*FOSDEM follow ups
- Will be doing a survey, using community survey application
- see they're notes for details [mic insert link]
- gather all questions in this document
*QA
- Third Party quality tester (S-) has provided their test dialogue's to us
- Feedback from Fosdem (those localizers we don't usually have challenges with) was that quality of community feedback is higher than outsourced provider
- Advantage of Litmus is see and track results; imagine its a lot of work but the tracking would be worth the one-time up front investment; we just need to be sure that localizers will use them; ACTION build a few tests based on these new dialogue's and then review with both strong and weaker localization team
- Test day: have to be sure we cover time zones with QA people; have bunch of testers around world using their own locales and have same things go on for each test day; special test day for them and introductory session where to grab builds, how the day works, etc.; down road goal is to get engagement with people doing this and bring them into the regular process that we're doing
- narrowing target by having to speak english and coordinating with Mountain View; maybe can do days organized by language like today testing German, that way can handle things by language
- Likely need to do both: channels with German teams and then channels that are more broad
- ACTION: Mic/Pascal - organize these test days to happen - target within 2 to 3 weeks
*Tools
- Hosted a BoF session on Friday
- Alexander from Romania, we'd like to support him in some ways. His tool was well received. His tool provides a capability to store translation strings in a database
- Friedel presented Translation ToolKit Suite from SA, translation software and management
- Would be good ot get Wil to connect directly with Friedel and review his tool from Web Dev perspective
- Jeolen (sp?) from LaunchPad, biggest issue is software is not open
- Gandalf presented a tool he'd built in python
- Outcomes, had great demos and start of lots of good conversation, enabling collaboration, closer to supporting these tool builders, learned a lot about what's really not working
- Seth is working on 3 to 4 page summary from each tool provider with links to online tools; will be posting to blog with this information
- Was a lot of opportunity for knowledge sharing across open source projects for localization tools in general, like translation, QA testing, Community building, etc
*Community Dev
- Serbian team has two additional members; Localizer is working to build team around him; the two new localizers will focused on localizing the mozilla europe site
*Remora/Add-ons
- There appears to be some common issues for localizers of extensions: have problems committing - this is not a known issue
- ACTION: Pascal file a bug and Wil reviews
- AMO is string frozen v3.2
- Surprise for AMO team is Indonesia localized Ramora - Indonesians have been localizing Firefox as well
- Check out: http://remora.stage.mozilla.com/en-US/firefox/