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

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

145 bytes added , 13 June 2018

→‎Michal: turn some of the action items into tickets

291

edits

@@ Line 115: / Line 115: @@
 *** 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.
-*** [AI] Port to Chrome and Chromium based browsers is a pre-requisity (we estimate 1 out of 10 active Pontoon users have PT installed).
+*** [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?).
+*** [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.).
 ** APIs
-*** [AI] Document, what data from Pontoon are in use or are required for the planned features.
+*** [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] File bugs to provide them via Pontoon API.
 ** Share React components between Pontoon UI and Pontoon Tools.
@@ Line 125: / Line 125: @@
 ** Get some insight of how Pontoon Tools are used.
 *** Internal metrics and analytics system?
+*** What metric would we want to track?
 ** How can we get involved in Pontoon.Next even with(out) coding?
 * Pei