L10n:Meetings/LATAM hackathon

Logistics

Av. La Paz 463, Miraflores, PE.

Phone: 51 (1) 213-4300

when: 11-12 July
arriving at hotel: We're working on arranging for a shuttle to take us between the hotel and airports.

Google map:

AirBNB 1
- Mónica Bonilla
- Delphine
AirBNB 2
- Marcus Saad
- Giovanny Gongora
- Odin Mojica
- Reuben Morais
- Jeff Beatty
AirBNB 3
- Richard von Moltke Necochea
- Fernando Joaquin Haeussler
- Alcides Torres
- Vedran Tomicic
AirBNB 4
- Julio Gomez
- Marcelo Poli
- Guillermo Movia
- Juna Becerra
AirBNB 5
- Roberto Alvarado
- Rodrigo Ramírez
- Eduardo Trapani
- Heber Meili
- Juan Sián
- Alex Mayorga
Casa Andina Select Miraflores
- Hugo Acosta
- Mauricio Navarro
- Martin Pacheco
- Gabriela Montagu

Saturday
- QA introduction and team overview
- Bug triage and verification (hands-on)
- Crash reports overview (hands-on)
- Test days

Mozilla mission and org updates applied to LATAM locales
- Introduction to Mozilla & the mission, for anyone unfamiliar with it.
- Organization changes introduced in Whistler.
- Virtuous participation cycle
- The role of LATAM language localization within Mozilla's mission.
Tools, resources, and translation workflows at Mozilla
- Dashboards overview
- Pootle, hg, & SVN tutorials
Review Prod roadmaps, schedules and priorities to better understand and plan upcoming localization work
- iOS in the LATAM
- Seasonal Firefox releases -- Firefox 42
- Communication of timelines -- what's working, what isn't, how do l10n-drivers support LATAM 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 LATAM languages & how they might be relevant to other localization teams.

L10n community stability in LATAM 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 LATAM.
- Brainstorm possible initiatives to increase locale usage and market share in LATAM.

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