« 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

Agenda

• Content handling/Micro-Formats (Mic)
• Documentation: major work has been done to http://wiki.mozilla.org/L10n:Localization_Process in support of triaging bug list and generally, there are some significant implications to our build process in the way we've proposed to handle new builds, check it out
• AMO and language packs - (WilC)
  • Promotion and Building - Mic has update from PKim, John's sent around a note, and WilC has talked with Madhava
• Other?

Attendees

WilC, Axel, Pascal, Mic

DRAFT NOTES

I'm trying a new format this week to speed up the time it takes to get notes out. That is to type the notes while on the call and in this post directly. It means that notes will be pretty ugly/rough at first but will improve over the day and this "draft notes" tag will disappear once the notes are finalized. Thanks for your patience if you're hitting this page mid-edit :-) /mic

Content handling/Micro-Formats

There are two types of content handlers, those that sit within the operating system and are treated as defaults to handle e.g., images, video, etc. And, web service based content handlers like Google Docs, Gmail, RSS readers, etc. The L10n impact is in the web service based content handler, as these are the ones that Localizers will be able to provide specific to their language/locale. They will use the same infrastructure as what we currently do for RSS readers, meaning we'll need to list specifications by locale and there will be a server side impact for the local provider to be incorporated into Firefox. The product lead is Jason Douglas and you can check out the latest status on his Content Hanlder product page. Pascal asked if we'd need to worry about content not currently handled by o/s; thinking about linux piece; Axel beleives there won't be a localization piece form a process perspective but this will be treated like any typical operating system interaction. ACTION: Mic to double check that the statement about this functioning like RSS readers is accurate

Documentation

We (Mic, Axel, with help from Lilly, Gerv, Pascal) have been working on introductory documentation for localizers new to Mozilla (as well as for Localizers already working with Mozilla looking for more information). We'll be looking for general and specific feedback. General in terms of any comment on the content as a whole and/or specific areas that you may be intimately familiar with and wishing to provide input. New Localizer will be pointed to these pages as a starting point. Pascal asked if/how we should treat the content being written on http://developer.mozilla.org/en/docs/Firefox_3_for_developers We believe Sheppy (the author of much of that content) wants to update this too. ACTION: decisions should be coming out of Paris Developer Day this month pertaining to this documentation; following those discussions we'll create an action plan to integrate the content into the overall Process pages.

AMO/Language Packs

We are attempting to improve the way users find, download and update our language packs and localizers post, have reviewed and update their language packs. That's the objective for this discussion. The current process is a poor user experience on both fronts. (Traditionally we've not been good at detecting the language people are interested in, it's also hard to get Google to find the languages people are interested in).

Our approach is to start small and do things we know we can do, then get into more complex higher effort initiatives. So here are two good questions to start the discussion:

(1) what do we want the user experience to be for non-english speakers to find things

• look at this in more depth and create new plan that suits our target user
• geographic map of the world, might be an idea

(2) what do we want the user experience to be for localizers to build and update their language packs

In order to have this discussion we think we're missing UE people and JT or PKim from Marketing and Shaver would be great to have more thoughts (e.g., what's the upgrade experience). We're also missing some data e.g.,

• we'd like to know how many people hit the Mozilla website that are looking for a language that we don't offer (according to their computer); this should allow us to make more focused decision
• Geo-localization information apart from en-US use of Firefox; understanding what countries/languages use en-US
• any more detail on survey data that JT from Marketing team is working on

Axel also wondered if we should have a use case for those users/people that are really new vs those that have some experience with or building Firefox. And we wondered if the experience of getting to build should match quality of the build itself, unless it's a very simple process.

We decided a few more email exchanges with some internal experts about this could result in useful conclusions about what bilding blocks we can offer today/tmo and then where we want to invest/time effort to improve things. ACTION: Mic respond to email exchange started at Mozilla describing the context for this discussion and then WilC to articulate what users actually experience when they use a language pack, which websites they use and what kind of support options they get; then Axel could articulate the differences from "normal" experience. So WilC: how user's and localizers find it, updates, input