Webmaker/Localization

Links

Notes https://etherpad.mozilla.org/webmakerlocalization

Q3 Q4 Goal

/>Ship 600 new localization contributors by EOY. Grow the number of active MoFo localization contributors from current1,355 (Sep 15) to 2k by Dec 15 2014.

• Fun fact: l10n is our 2nd largest source of contributors right now. It's a powerhouse for 10K.
• BUT: we aren't really resourcing it right now. It needs focus and champions. 
• If we succeed: localization will account for 20% of our 2014 goal. Rawr! 
  
  

Strategy

• Growth. Push Webmaker to top of Transifex again. 90% of our localizers come from the Transifex community. 
• Re-activation. Re-engage dormant localizers. People who were active localizers, but aren't any longer. 
• Overlap. Focus on layering localization in as an explicit part of other campaigns and things we're already doing. 
  • (e.g., MozFest, Fall campaign, Lat Am train the trainer, etc.) 
    
    

Challenges

• Lack of a champion. Aali was rocking this file, but then needed to focus on other things. Need to distribute that knowledge. (e.g., Aali training others to step up) 
• The new /resources section is hard to localize. It links out to a bunch of third-party pages that we can't localize. So Transifex alone won't really work for it. 
• Not where we want to be on right-to-left. We made progress on RTL -- but more is needed.
  
  

Tactics

• Language completion. Need to engage with the community to push toward full language completion. 
• Comms. Spread the word about localization work
  • blog post. announcing our goal and plans. 
  • localization events
  • send Transifex announcements
  • Join IRC on Mozilla Network for locales we want to focus on
• Training. Share knowledge around Transifex / best practises. Spread what's in Aali's head.
• RTL. Finish Right-To-Left. Make sure they're implemented on all apps and pages.
• QA. Do QA on all pages. Ensure all strings are uploaded to Transifex
• User testing. Do more user-testing on localized pages to see our translation process.
  
  

Improve our localization process:

• Answer questions in Transifex from users related to strings
• Talk to people in Mozilla's irc channels to keep people active
• Change roles for translators (e.g., make reviewer)
• Manage languages (add new)
• Co-ordinate with devops for shipping new languages.
• Manage github repos and Transifex for automatic resource syncing
• Uploading new resource files
• Communicating with Transifex support (e.g., spam)
• Communicating with Transifex translators (e.g., "New resource added, please translate...")
  
  

Questions:

• Roles and resource allocation. Someone own the content localization experiment. Who?
• Community. How can community members help own this?
  • Will distributed ownership work? Should we have a working group (like the bug triage group)?
• Reactivation. 20-30% of 1000+ Transifex contributors are currently active. How do we reactivate the rest?
  
  
  
  

===================================================================
Localization Bootcamp: traning on Transifex and beyond
WHEN:
WHERE:
HOW: 
Hands-on training. Similar to GitClub. 
Training topics: 

• how to navigate Transifex
• what's needed to make a language live
• the process for adding new pages to the site. (and what that means for fully translated languages already on the site)
• localizing content, not just words
• open to all 
  
  

===================================================================
Roadmap 
===================================================================
to do: File these tickets:

[sep19]

• Ship blog post: "Localization for 10K"
• Research and demo Transifex Live for Webmaker
• Schedule Transifex Bootcamp training 
• Update our plan on the wiki: <a href="https://wiki.mozilla.org/Webmaker/Localization">https://wiki.mozilla.org/Webmaker/Localization</a>
  
  

[oct3]

• Document localization requirements for MozFest
  • 
    
• Document localization requirements for Fall Campaign (if any) 
  • needinfo: Geoff
• Document localization requirements for Lat Am "train the trainer" events (if any)
  • needinfo: Michelle
    
    

[oct17]

• Localization file is prepped and ready for MozFest 
  • (if we're doing anything special for MozFest -- maybe we aren't) 
    
    

[oct31]

[nov14]

[nov28]<br

Older Content

Q1 Goals

• Understand which new markets, languages, locales are our priority in the short and medium term. Gain wisdom from our Mozilla Japan colleagues.
• Plan and process for evaluating the quality of our localized sites. User testing with l10n focus.
• Plan, technical strategy and prototype for right-to-left (RTL) locales.

• Bugzilla component: Localization

• Owners: Humph, Ali
• Key Tasks
  • Right-to-Left Planning -- (Tues AM) https://bugzilla.mozilla.org/show_bug.cgi?id=965406
  • Prioritize Languages/Locales https://bugzilla.mozilla.org/show_bug.cgi?id=965412
  • Webmaker and Japan https://bugzilla.mozilla.org/show_bug.cgi?id=965416
  • Localization User Testing https://bugzilla.mozilla.org/show_bug.cgi?id=965417
  • Community Managment of our Transifex community. Do we need to do anything? How should we share the management of this beyond Ali?

• Post Work Week Priorities (individual tasks that could be done or put off):
  • Make language setting per-user vs. per-site (user setting, per session, ???)
  • UX for MakeAPI for localized searches
  • Localized Emails, especially auto-generated
  • Site banner/CTA to indicate lang/locale is not complete, and links to help translate, etc.
  • Automation to auto-upload translation files to Transifex when something changes in en-US
  • Can we co-ordinate with MDN for details we share with them (e.g., HTML and CSS info in Goggles/Thimble)?
  • Locale file info in healthcheck, to show how recently l10n translations where downloaded
  • Improve L10N Responsiveness of our Tools: we need to audit for things like widths/height. We've fixed in webmaker.org, but missed a lot in our tools.
  • Localization of Teaching Kits and other Makes. We don't have any automated/Transifex way of doing this now.
  • Need to educate people on using Tutorials vs. inline HTML comments in Thimble--this makes localization much easier.
  • Prompt users for locale on publish
  • Display appropriate locales on Webmaker.org locale (ie pt-br content on webmaker.org/pt-br/)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);