L10n/HomePage/Status/2008-04-23
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
- (notetaker: Mic)
Proposed Agenda
- Comm Dev
- Spanish team has agreed to represent us at Open Source conferences there and we will pay expenses
- Tools
- Wil believes that starting with Pootle will be better than starting with Python, summary of file types to support with tool: http://wiki.mozilla.org/User:Clouserw/Verbatim:Development_Planning/Interaction_with_file_types
- Proposal is going forward to steering committee for funding, proposal should produce a higher quality tool with lower barriers to entry
- Fx3
- RC1 status report: approval requests for landing is slowly progressing to zero, stabilizing, code point of view we're in good shape, RTL Mac theme landed (looked at Mac build and we should ship them)
- in-product pages: locales/pages going well, Phishing page no for RC1, not complete yet in English, new locales haven't done any translation work yet, filing QA bugs, status can be ascertained from here: http://l10n.mozilla.org/webdashboard/?localesstatus Note: Some localizers commit all at once vs progressively so it appears in some cases like ja or zh-cn that they are far away but not really case, wait a few days
- QA: Clint still working on Minotaur, testing going well, run time automation still more discussion to come from JODuinn, still unclear on what they want to fix, whouldn't be that complex but more who is assigned to do this, might need Schrep to weigh in on this
- AMO
- Update: Tools - see above, Summit, Students
Roundtable
- I don't think Toni considers the Valencian thing finished although I
haven't talked to him since his last email. I'd like to make a decision on whether we keep the dictionary on AMO or not - and if we need to involve Basil for a policy, let's do it. This has a habit of coming up right after our meetings are over and I don't want to have to delay another week.
- if it's a normal extension on AMO, marking it as extension and putting
- Fx3 post mortem: opportunity for team to review good, bad and ugly from Fx3 and do this before Summit so that we could put things in place before that Summit. Action: forum post and do an all email. sounds like a good idea