L10n:Meetings/SF-All-Hands: Difference between revisions

← Older edit

L10n:Meetings/SF-All-Hands (view source)

Revision as of 10:48, 19 June 2018

2,461 bytes added , 19 June 2018

→‎Michal: more links to tickets create for Pontoon Tools

Mstanke

291

edits

@@ Line 104: / Line 104: @@
 === Jakob ===
+* Design a better onboarding process for new contributors.
+* Get input on how to build a (non-compulsory) culture of accountability.
+* Figure out if/how a tighter integration between the three communities working with the closely related Scandinavian languages (Danish, Swedish and Norwegian) could lead to higher quality translations and help build better awareness of Mozilla's goals in Scandinavia.
+* Get Axel to tell me why my repeated attempts to upgrade compare-locales to 3.0 breaks everything a bit more for each try.
+DONE Define prerequisites for moving Firefox-da to Pontoon. SOLUTION: 1) We will keep using our current workflow, and 2) take on an active role in the upcoming design sprint to help with solutions for the review process in Pontoon.
 === Michal ===
 * Matjaž
-** What will Pontoon.Next & the expected localizers workflow mean for the Pontoon Tools future and how can Pontoon Tools support if (use cases to cover, sharing code/technologies with Pontoon.Next, APIs)?
+** Define the right positioning for Pontoon Tools.
+*** Do what's more appropriate to do in an add-on (decided per feature) and does not make sense or cannot be done in the app itself.
+** Promote Pontoon Tools to more users. ([https://github.com/MikkCZ/pontoon-tools/issues/79 #79])
+*** [AI] Port to Chrome and Chromium based browsers is a prerequisity. ([https://github.com/MikkCZ/pontoon-tools/issues/42 #42])
+*** [AI] Rename to Pontoon Add-on, so it's clear what it really is and does. ([https://github.com/MikkCZ/pontoon-tools/issues/72 #72])
+*** [AI] Review the code and define procedures for future updates and development (API changes, PR reviews etc.). (email sent to Adrian) ([https://github.com/MikkCZ/pontoon-tools/issues/80 #80])
+** APIs
+*** [AI] Document, what data from Pontoon are in use or are required for the planned features. ([https://github.com/MikkCZ/pontoon-tools/issues/56 #56])
+*** [AI-TODO] File bugs to provide them via Pontoon API. (see [[L10n:Pontoon-Tools]])
+** Share React components between Pontoon UI and Pontoon Tools.
+*** [AI] Talk to Adrian. (email sent to Adrian)
+** Get some insight of how Pontoon Tools are used. (TBD with Matjaž and probably Jeff)
+*** Internal metrics and analytics system?
+*** What metric would we want to track? Add #utm_source to Pontoon links, count number of interactions with the toolbar button per week etc. ([https://github.com/MikkCZ/pontoon-tools/pull/76 #76])
 ** How can we get involved in Pontoon.Next even with(out) coding?
+*** Bugs, patches, PRs, design sprints, early feedback will be gathered via Discourse.
 * Pei
 ** How to re-include Czech for localized snippets and/or how to prepare and deliver locally tailored snippets?
+** Can we help to speed up brand declensions?
 * ?
-** Can we help to speed up brand declensions?
 ** How to further improve l10n documentation (both language specific and general)?
 * Jeff:
 ** How to prepare l10n hackathon in autumn for multiple Czech communities? How to request some support and do the "paperwork"?
+*** Process documented on [https://blog.mozilla.org/l10n/2018/05/04/l10n-community-events-in-2018/ blog]/[[L10n:Meetings/2018 community requests|wiki]].
+*** Inviting localizers of other projects is perfectly OK.
+*** Good to invite l10n-drivers based on the chosen topics.
+*** Brno in November is OK (October may clash with Iceland), Matjaž can drive to Brno by car, others may fly to Vienna.
 ** How to implement roles in the Czech not-only-l10n community with(out) me in the lead?