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

→‎Michal: updates from the discussion with Matjaž
(→‎Michal: branding)
(→‎Michal: updates from the discussion with Matjaž)
Line 112: Line 112:
=== Michal ===
=== Michal ===
* Matjaž
* 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 more appropriate to do in an add-on (decided per feature).
** Promote Pontoon Tools to more users (we estimate 1 out of 10 active Pontoon users have PT installed).
*** [AI] Port to Chrome and Chromium based browsers is a pre-requisity.
*** [AI] Rename to Pontoon Add-on, so it's clear what it really is (and does?).
*** [AI] Review the code and define some procedure for future updates and development (API changes, PR reviews etc.).
** APIs
*** [AI] Document, what data from Pontoon are in use or are required for the planned feature.
*** [AI] File bugs to provide them via Pontoon API.
** Share React components between Pontoon UI and Pontoon Tools.
*** [AI] Talk to Adrian.
** Get some insight of how Pontoon Tools are used.
*** Internal metrics and analytics system?
** How can we get involved in Pontoon.Next even with(out) coding?
** How can we get involved in Pontoon.Next even with(out) coding?
* Pei
* Pei
291

edits