From MozillaWiki
Jump to: navigation, 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
  • (notetaker: clouserw)


TimR, Chofmann, Axel, Mic, Seth, (Wil and Pascal)

Proposed Agenda

  • Community Dev
    • Community Pack: he and Seth will split up 16 different focus areas, write a middle layer and next layer of what it means and links to next stuff
  • Evangelism style blog posts about launch of Firefox 3: Abdulkadir (Technical and process oriented), Ankit (Emerging Market), Friedel (Tools perspective); who I am, success, pain, how a localizer does this
    • 100 blog posts about what went into creation of Firefox and piece of post went into localization
    • Distribute half of grant to Dwayne, testing machine (MacMini type thing)
  • Firefox
    • which webstatus is blocking what
    • web pages, go up and down, need some help to determine what to block if anything
    • hebrew in better shape now
  • Summit
    • Mic proposed sessions on Summit, look for duplicates
    • Asa collect items in themes and organize accordingly
    • How many localizers?
    • Mic double check with Asa about posts for sessions
  • AMO
    • blog post about localiztion plan @ summit
    • emailed dev.l10n list to get feedback
  • RoundTable
    • Mobile, want to release in as many languages as possible, need some further detailed planning; figure out which platforms then when UI will become stable; we can do some prior notification teams; at Summit lay out plan for what it might take for localizations to happen and lay out some requirements and set out some dates for things like UI stability
    • Communication challenges for L10n
      • Suggestions: All hands meeting (good one) report on what L10n community is doing, Lists dev l10n is listed (good) no description available: the place where localization issues are discussed and release schedules are discussed, check to be sure teams list is complete and put descriptions where missing; l10n drivers is to coordinate releases and all results should be going into dev.l10n group; at the director's l10n is represented when needed between Tim and Chofmann

e.g., making process more agile, reviewing fx3 process to make it easier so that not sending new lcoales down same path, community pack good to talk about this in internal meeting, also good to recognize new localizations and conributions -- mostly about heads up on this is coming next week or reminder of what happened in preiovus week