L10n/HomePage/Status/2007-06-13

From MozillaWiki
< L10n
Revision as of 20:21, 17 June 2007 by Mic (talk | contribs)
Jump to navigation Jump to search

« 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

Proposed agenda

  • Buffet - progress and specific action plans
  • Triaging bug list for new locales
  • Content handling/Micro-Formats
  • Gregorian update
  • AMO and language packs - john's feedback
  • QA news

Attendees

SethB, Mic, Axel, TimR, WilC (Pascal at conference; Choffman on vacation)

DRAFT meeting minutes

buffet proposed to community giving program, making resources available to teams who want to hoste domains, it was approved. Mongolians were fist to receive funds, contacted them through IRC. use Mongolian example to formalize who we can support localizers to help them build community and take away organizational challenges (as it's been a big burden to localizers). this has become a funding description that we'll include in Buffet, will be about 300Euro's. serving s test case for what we can do

Gregorian historical - update on buglist

Gerv; triage the bug list triggered Simon to get into changes to Calendar, creating traffic to specific bugs including Gregorian localizer who branched what he had without review and (accidentally we think) unbranched his complete localization so every tinder box went red (we rebranched his lcoalization but not with original) there are some changes on branch. problems (remembered what happened last time, security drills). confident didn't break any other localizations

Content handling micro-formats has same l10n impacts - same as content handling

QA clint is close to completing minutes verfiication for minotour tool - partner first then L10n, running within 2.5 weeks/end of quarter; test partner/locale builds next week resched post thursday

AMO and language packs - john's feedback category called "language support and translation" could use all.html page - in same way we do with partners poorly maintained localizations on all.html page isn't a decent quality statement - end user experience may be bad works: can put language packs on AMO, security updates don't work on this (bug assigned to Benjamin) do localizers know how to update lanugage packs budnling is a better user experience but it's more expensive on resources (partner build people) project: can have it reviewed well in AMO/sandbox sandbox is for new add-ons or language packs, gets reviewed and provide feedback and then nominated for public if realize that should be reasonable language packs difficult; hard time to encourge people to review stuff in Sandbox; might need guildelines or rules to move things to public side earlier queston: how know quality of lead translators; part of point is to have community around that person to have a review (not like modules where have module lead already established in community) - effectieve way to advertise them withou conflicting with current ones have to balance benefit/risk benefit - expose lcoalization work early; short technical review of it and publish it put different use cases in different boxes use case of release early and often - alpha testers people that have small community and stable localization -