L10n:Meetings/Austin-All-Hands: Difference between revisions
Jump to navigation
Jump to search
(→Benny) |
(Goals added) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
=== Delphine === | === Delphine === | ||
* | * Define some priorities for Q1 in terms of improving l10n process for Focus iOS | ||
* Defining next steps in Firefox iOS right-to-left bug fixing | * Defining next steps in Firefox iOS right-to-left bug fixing | ||
* WoMoz: what next? | * WoMoz: what next? | ||
* Community Leadership Principles (Mission Driven Mozillians): how does l10n fit into that? Then, possibly start ideation process for implementation | * Community Leadership Principles (Mission Driven Mozillians): how does l10n fit into that? Then, possibly start ideation process for implementation | ||
* Documentation: update what's needed | * Documentation: update what's needed | ||
* Clean up old bugs | |||
* See if I have any comments on Peiying's survey | |||
=== Flod === | === Flod === | ||
| Line 67: | Line 69: | ||
=== Alizée === | === Alizée === | ||
*Talk to marketing teams about the issues around localizing content, including snippet and email teams | |||
*Discuss Pontoon features: what can be improved so that professional translators can use it more easily | |||
*Discuss Pontoon features: what can be improved so that translation agencies can use it more easily | |||
*Discuss translation project management processes | |||
=== Biraj === | === Biraj === | ||
| Line 74: | Line 79: | ||
=== Benny === | === Benny === | ||
* Discuss: how to define the path and manage l10n requests from other teams (Marketing, etc.) | * Discuss: how to define the path and manage l10n requests from other teams (Marketing, etc.) | ||
* Discuss: how to track the whole work of a localizer (Pontoon + Bugzilla + ?) | |||
* Discuss: how to increase the awareness of Firefox locale | * Discuss: how to increase the awareness of Firefox locale | ||
* Discuss: how to engage new and current localizers based on their motivation | * Discuss: how to engage new and current localizers based on their motivation | ||
* Encourage Firefox video promotion available in more languages | * Encourage Firefox video promotion available in more languages | ||
* Discuss: localizers community, translation agency and quality | * Discuss: localizers community, translation agency and quality | ||
* Discuss: relationship and leadership between localizers and local/region community | |||
* Discuss: local content for snippets | |||
* Discuss: Firefox social posts (Facebook & Twitter) and l10n | |||
=== Jotes === | === Jotes === | ||
Latest revision as of 23:02, 10 December 2017
Team Goals
- Showcase progress on Fluent-Preferences conversion
- Take initial proposals of Pontoon translate UI rewrite to localizers for in-person feedback
- Build out 2018 OKRs while in person
- Evangelize the current status of localization at Mozilla outside of our team
- Defining Terms of Service with Marketing at All Hands
- Create l10n-tamers cross-functional super group for l10n
Roundtable
Delphine
- Define some priorities for Q1 in terms of improving l10n process for Focus iOS
- Defining next steps in Firefox iOS right-to-left bug fixing
- WoMoz: what next?
- Community Leadership Principles (Mission Driven Mozillians): how does l10n fit into that? Then, possibly start ideation process for implementation
- Documentation: update what's needed
- Clean up old bugs
- See if I have any comments on Peiying's survey
Flod
Gandalf
- Build momentum and evangelize Fluent in Gecko
- Demo and get stakeholders buy-in for landing Preferences rewrite to Fluent
- Brainstorm the vision for Gecko Intl module in 2018
Ryan
Jeff
- Build out 2018 OKRs while in person
- Evangelize the current status of localization at Mozilla outside of our team
- Defining Terms of Service with Marketing at All Hands
- Scope for Pontoon as add-ons l10n platform
- Recruiting mozilla.org and mobile teams to reduce l10n PM overhead
- Discuss MT API licensing with Legal
- Create l10n-tamers cross-functional super group for l10n
- Scope for Common Voice localization
Matjaž
Pei
- Marketing:
- Post-mortem meetings with marketing teams.
- Scope and strategy on working with or without l10n communities when regional hires are involved.
- Terms and service agreement with Marketing team, including draft for budget proposal
- Product name l10n: Resume discussion with Branding and legal contacts.
- Legal: scope and budget in 2018
- Documentation overdue
- Flod: technical discussion on mozilla.org
Stas
Theo
Rhoslyn
Cynthia
- Get feedback about the Quality Assurance for Localization (QAL10n). :roar:
- Figure out how to create snippets to engage new contributors.
- L10n community gathering (how the Mission Driven Mozillians can help with that?)
- Brainstorm about recognition system to keep the contributors motivated.
Alizée
- Talk to marketing teams about the issues around localizing content, including snippet and email teams
- Discuss Pontoon features: what can be improved so that professional translators can use it more easily
- Discuss Pontoon features: what can be improved so that translation agencies can use it more easily
- Discuss translation project management processes
Biraj
Benny
- Discuss: how to define the path and manage l10n requests from other teams (Marketing, etc.)
- Discuss: how to track the whole work of a localizer (Pontoon + Bugzilla + ?)
- Discuss: how to increase the awareness of Firefox locale
- Discuss: how to engage new and current localizers based on their motivation
- Encourage Firefox video promotion available in more languages
- Discuss: localizers community, translation agency and quality
- Discuss: relationship and leadership between localizers and local/region community
- Discuss: local content for snippets
- Discuss: Firefox social posts (Facebook & Twitter) and l10n