L10n:Meetings/Paris hackathon: Difference between revisions

Revision as of 21:26, 4 September 2015

Phone:

Google maps:

Google map:

Mozilla mission and org updates applied to your locales
- Introduction to Mozilla & the mission, for anyone unfamiliar with it.
- Organization changes introduced in Whistler.
- Virtuous participation cycle
- The role of your language localization within Mozilla's mission.
Tools, resources, and translation workflows at Mozilla
- Dashboards overview
- Pootle, hg, & SVN tutorials
- Translation quality program
Review Prod roadmaps, schedules and priorities to better understand and plan upcoming localization work
- iOS launch
- Seasonal Firefox releases -- Firefox 42
- Communication of timelines -- what's working, what isn't, how do l10n-drivers support your locales more?
- Firefox OS

Dashboard review & translation catchup work where localization work has not been completed
- Discussion lead by l10n teams to share common practices between your languages & how they might be relevant to other localization teams.

L10n community stability in your locales
- Project priorities
  - How does each l10n team prioritize their active projects?
- Leadership & succession
  - How does each l10n team structure locale/project leadership?
  - Does the team have a plan of succession? If so, what is it, where is it strong and where is it weak?
- Recruitment
  - Does the l10n team need more localizers?
  - If so, what has the team done to recruit and mentor new localizers?
  - What can be improved?
  - What has been successful in other l10n teams?
- Sustainability
  - Does the l10n team have linguistic resources (e.g., Firefox glossary, style guide, etc.) to sustain the project?
  - If yes, how did they create them? Would they be willing to mentor other teams to create their own?
- Localizer recognition
  - Does the l10n team feel like they receive enough recognition from Mozilla for their efforts?
    - What form of recognition is most appreciated?
  - Does the l10n team provide recognition to outstanding members of the team?
Discuss localized product use in your regions.
- Brainstorm possible initiatives to increase locale usage and market share.

Dashboard review, and translation catchup work where localization work has not been completed
- Discussion lead by l10n teams to share common practices between your languages & how they might be relevant to other localization teams.
Update team wiki pages
Take l10n hackathon survey.
Group pictures

Community Introductions and brief overview of Mozilla
FxOS Development Cycle Current Status
- Understanding the current priorities and team structure
Deep dive into FxOS testing
- How and where to look for bugs in the various apps
- What ADB debugging is necessary for what apps?
  - Productivity Apps
  - Communication Apps
  - Media Apps
Examples of best practices for FxOS bugs

Hackathon Bug work - finding bugs on the Flame device and using knowledge gained in the morning.

FxOS Localization Testing Best Practices
- One session will cover how the community can help file localization bugs.
  - Examples include UI display issues, in which strings are improperly displayed (alignment, overlap, truncation, and so forth)
  - Clearly understand where these bugs get filed in Bugzilla

@@ Line 68: / Line 68: @@
 ==Draft QA Agenda==
-===Saturday 10 October===
+===Saturday 24 October===
 ;Morning - 930AM
 * Community Introductions and brief overview of Mozilla
@@ Line 85: / Line 85: @@
 ;Dinner -- TBD
-===Sunday 11 October===
+===Sunday 25 October===
 ;Morning -- 930AM
 * FxOS Localization Testing Best Practices