Webmaker/Localization: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(33 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Localization ==
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/k5w0t_1w.png
[[Image:translation.gif|right]]
__NOTOC__
'''Goals'''
=Links=
* '''Understand which new markets, languages, locales are our priority in the short and medium term. Gain wisdom from our Mozilla Japan colleagues'''.
* '''Notes''' https://etherpad.mozilla.org/webmakerlocalization
* Plan and process for evaluating the quality of our localized sites. User testing with l10n focus.
* '''Sprinter''' [oct3] [localization] http://mzl.la/localization_oct3
* Plan, technical strategy and prototype for right-to-left (RTL) locales. 


* Bugzilla whiteboard: '''[workweek-l10n]'''
=Goal: 2K localizers=
<b>2,000 active localization contributors by Dec 31.</b> We will ship 600 new localization contributors in Q4. This means growing the number of active MoFo localization contributors from 1,355 (Sep 15) to 2,000 by end of Dec.<br
/><ul><li>'''Fun fact''': localization is our 2nd largest source of contributors right now. It's a quiet powerhouse for 10K!</li
><li>'''BUT''': we aren't really resourcing it right now. It needs focus and champions.&nbsp;</li
><li>'''If we succeed''': localization will account for 20% of our 2014 goal. Rawr!&nbsp;<br/><br
/></li></ul>


* '''Owners:''' Humph, Ali
=[oct3]=
* '''Scrum tasks'''
<bugzilla>
** 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
"product": "webmaker",
** Webmaker and Japan https://bugzilla.mozilla.org/show_bug.cgi?id=965416
"whiteboard": "[oct3] [localization]",
** Localization User Testing https://bugzilla.mozilla.org/show_bug.cgi?id=965417
"include_fields": "id, summary, whiteboard, assigned_to, status",
** '''Community Managment of our Transifex community.''' Do we need to do anything?  How should we share the management of this beyond Ali?
"maxrows":"50",
 
"order": "bug_id"
*  '''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, ???)
</bugzilla>
**  UX for MakeAPI for localized searches
=[oct17]=
**  Localized Emails, especially auto-generated
<bugzilla>
**  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
"product": "webmaker",
** Can we co-ordinate with MDN for details we share with them (e.g., HTML and CSS info in Goggles/Thimble)?
"whiteboard": "[oct17] [localization]",
**  Locale file info in healthcheck, to show how recently l10n translations where downloaded
"include_fields": "id, summary, whiteboard, assigned_to, status",
** 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.
"maxrows":"50",
** Localization of Teaching Kits and other Makes.  We don't have any automated/Transifex way of doing this now.
"order": "bug_id"
** Need to educate people on using Tutorials vs. inline HTML comments in Thimble--this makes localization much easier.
}
** Prompt users for locale on publish
</bugzilla>
**  Display appropriate locales on Webmaker.org locale (ie pt-br content on webmaker.org/pt-br/)
=[oct31]=
 
<bugzilla>
<onlyinclude>
{
"product": "webmaker",
"whiteboard": "[oct31] [localization]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
=[nov14]=
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[oct31] [localization]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
=[nov28]=
<bugzilla>
<bugzilla>
{
{
"product": "webmaker",
"product": "webmaker",
"component":"localization",
"whiteboard": "[oct31] [localization]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 40: Line 62:
}
}
</bugzilla>
</bugzilla>
</onlyinclude>
 
 
==Strategy==
<br
/><ul><li><b>Growth. </b>Push Webmaker to top of Transifex again. 90% of our localizers come from the Transifex community.&nbsp;</li
><li><b>Re-activation.</b> Re-engage dormant localizers. People who were active localizers, but aren't any longer.&nbsp;</li
><li><b>Overlap. </b>Focus on layering localization in as an explicit part of other campaigns and things we're already doing.&nbsp;<ul><li>(e.g., MozFest, Fall campaign, Lat Am train the trainer, etc.)&nbsp;<br/><br
/></li></ul
></li></ul>
==Localization Campaigns==
* '''Fall Campaign'''
** How localization fits: [please fill in here]
* '''Lat Am train the trainer events'''
** How localization fits: [please fill in here]
* '''/resources section'''
** Melissa and Aali have a strategy here: https://etherpad.mozilla.org/webmakerlocalization
* '''MozFest'''
** Localization focus:
* '''End of Year campaign'''
** Localization requirements:
 
==Tactics==
<ul><li><b>Language completion.</b> Need to engage with the community to push toward full language completion.&nbsp;</li
><li><b>Comms. </b>Spread the word about localization work<ul><li>blog post. announcing our goal and plans.&nbsp;</li
><li>localization events</li
><li>send Transifex announcements</li
><li>Join IRC on Mozilla Network for locales we want to focus on</li></ul
></li
><li><b>Training. </b>Share knowledge around Transifex / best practises. Spread what's in Aali's head.</li
><li><b>RTL. </b>Finish Right-To-Left. Make sure they're implemented on all apps and pages.</li
><li><b>QA. </b>Do QA on all pages. Ensure all strings are uploaded to Transifex</li
><li><b>User testing.</b> Do more user-testing on localized pages to see our translation process.<br/><br
/></li></ul
><b>Process improvements</b>:<br
/><ul><li>Answer questions in Transifex from users related to strings</li
><li>Talk to people in Mozilla's irc channels to keep people active</li
><li>Change roles for translators (e.g., make reviewer)</li
><li>Manage languages (add new)</li
><li>Co-ordinate with devops for shipping new languages.</li
><li>Manage github repos and Transifex for automatic resource syncing</li
><li>Uploading new resource files</li
><li>Communicating with Transifex support (e.g., spam)</li
><li>Communicating with Transifex translators (e.g., "New resource added, please translate...")<br/><br
/></li></ul>
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/vq78rkr5.png
 
=Older content=
* moved here https://wiki.mozilla.org/Webmaker/Localization/Archive

Latest revision as of 15:25, 29 September 2014

k5w0t_1w.png

Links

Goal: 2K localizers

2,000 active localization contributors by Dec 31. We will ship 600 new localization contributors in Q4. This means growing the number of active MoFo localization contributors from 1,355 (Sep 15) to 2,000 by end of Dec.

  • Fun fact: localization is our 2nd largest source of contributors right now. It's a quiet 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! 

[oct3]

No results.

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

[oct17]

No results.

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

[oct31]

No results.

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

[nov14]

No results.

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

[nov28]

No results.

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


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.) 

Localization Campaigns

  • Fall Campaign
    • How localization fits: [please fill in here]
  • Lat Am train the trainer events
    • How localization fits: [please fill in here]
  • /resources section
  • MozFest
    • Localization focus:
  • End of Year campaign
    • Localization requirements:

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.

Process improvements:

  • 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...")

vq78rkr5.png

Older content

Retrieved from "https://wiki.mozilla.org/index.php?title=Webmaker/Localization&oldid=1019180"