L10n:Planning/2016-10-18: Difference between revisions

Line 28: Line 28:
====PM Meeting Notes====
====PM Meeting Notes====


* Attendees:
* Attendees: Jeff, Flod, Pei, Delphine
* ''Put your talking points here.''
=====Project Roundtable:=====
;Firefox
*Focus on Search, a lot going on. Centralize json file
*Another tool in devtools moving to .properties file (100 strings). Get back to Dwayne because no PootleFS yet (was due for Nov)
**PootleFS is targeted for mozilla.org first. Pootle Tech Team needs to be aware of the risk with Firefox desktop in November so they can determine if they need to shift priorities.
;Fennec
*Android:
**Worked on patch to add ne-NP, bg, and kab. Dropped be
**Opened up related launch bugs for fm-tracker
**Gonna start sign-offs again tonight (saw Beta closes tomorrow)
**Discussion with BD about Indian localization
*iOS:
**Talked with St3fan about upcoming train schedule for iOS
**L10n taken into account of schedule
**Gonna work on opening up v6 l10n bugs
***Tentative schedule: https://docs.google.com/document/d/1FftFVrZ-fWjAQCeY7-YwxqnGQe65ofZoGlcCzORSH5A/edit#
***Also: https://docs.google.com/document/d/1a7GE-WcHXM-_iz3ox8QXLkvwZQF4b_EgG0z6x2iuZrg/edit#
;Web
*Internet Health Report (launch on Nov 21)
*MOSS launch on Oct 27 in English (3 sub-pages, ready for l10n)
*Fundraise campaign (Theo)
;Hackathons
*Paris
**Senegal guy visa/airbnb confirmation
***AirBNB’s confirmed with hosts, itineraries shared with all guests, AirBNB Captains identified in Registration, and those should be communicated to the people staying in AirBNBs.
**restaurant/cultural activity pending
**Wiki mostly done, still some info pending: https://wiki.mozilla.org/L10n:Meetings/2016_Paris_hackathon
*Middle East
**Heather agreed to help us to identify some locations with low visa requirements for those attending the hackathon this week.
=====Topics:=====
;Inclusian and Participation issues (today’s email thread)
* Social media team is running with the issue with a community facebook group.
* Meeting scheduled with Larissa for the rest.
;(reminder) Beta sign-offs close tomorrow
;Web parts as first l10n projects
*Pros
**Little to no dependencies for repo creation and other parts of the process.
***Do we have a hierarchy (dependency site map) for these sites?
**Quick pay-off for localizers to see their work publicly.
**Mozilla.org is the first point of interaction with users.
**Technical challenges for the localizer are minimal.
**Most text is prose-based.
**Second smallest project behind iOS.
*WE’RE DOING IT!!!
**Existing new communities will be grandfathered in. Starting with the next community to request to localize Firefox, we'll direct them to mozilla.org l10n first.
;Process for making technical requests from Tech group (Pontoon, etc.)
*Reach out to Axel first, so he can determine priority. He has overview of it all
*File bug (pontoon component bugzilla), ni Axel, CC mathjaz. Axel decides :)
;Communicating technical changes to l10n process in q4
*Outreach to the community to explain that all locales will be enabled in Pontoon before flipping the switch. *Also blocked by priorities to projects
**Targeted messages in Pontoon, depends on dashboard redesign and that has priority
*Their work is tracked with Github projects, we can link to those
;Communication piece about l10n for Mozilla Reps
*Proactively keeping the Mozilla Reps up-to-date on new developments to the l10n process.
*2 types of l10n events: hackathons and follow-up team meet-ups (not used for catching up l10n work!)
*Communicated tools vision for pontoon and l20n
*Next year’s hackathon update
**They want more proactive updates so they can train reps better to help with these events. Will help Reps being more effective on how they can support and create good localization events


==Tech Meeting Details==
==Tech Meeting Details==
Account confirmers, canmove, Confirmed users
2,357

edits