1433498 - [Engagement][email]: January: Mobile Apps Update

Status: RESOLVED FIXED

(Mozilla Localizations :: Other, enhancement)

Description

[Peiying Mo [:CocoMo]]

Starting this year, the email team will standardize the l10n process for all email projects by moving the activity to Pontoon, instead of spreadsheets. Jessica will communicate the change to all impacted communities.

*Source*:
- English: https://docs.google.com/document/d/1eHF9ga4sswpYftOdbWlQCaysC66xNHn_xf9SFw3XAqA/edit
- Target locales: in Pontoon

*Locales*: es, fr, id, pl, pt-BR, ru. 
(Note: for now, German follows a different process)

*Schedule*:
- Feb 6: translation complete
- Feb 7-12: linguistic review, functionality testing with a mobile device
- Feb 13: Launch

Comment 1

[Jessica Osorio [:josorio]]

Thanks for starting this thread Peiying! 

Some clarifications below:
- English: https://docs.google.com/document/d/1eHF9ga4sswpYftOdbWlQCaysC66xNHn_xf9SFw3XAqA/edit this copy can be used to PT-BR, RU, ES, PL

- For ID use this source: https://docs.google.com/document/d/1obOJO-ILreGsxJkVa7pUHTcYrgln4m0CWJMB-ifkjjk/edit

- For FR use this source: https://docs.google.com/document/d/1tjQ3ZTkdLSny-mv4OPJlPncv0uP-bM6VreaHHV0KGus/edit

Comment 2

[Peiying Mo [:CocoMo]]

Thanks Jessica. Let me update the strings in Pontoon per locale specific. I will send out an email about this project and about the change so the impacted communities don't touch it.

Comment 3

[Peiying Mo [:CocoMo]]

To check the completion status, there are two ways: 
1). Web project dashboard:
- 4 locales: https://l10n.mozilla-community.org/langchecker/?website=6&file=emails/2018/jan_mobile_app_updates.lang
- fr: https://l10n.mozilla-community.org/langchecker/?website=6&file=emails/2018/jan_mobile_app_updates_fr.lang
- id: https://l10n.mozilla-community.org/langchecker/?website=6&file=emails/2018/jan_mobile_app_updates_id.lang
2). Pontoon: (best for getting all the strings in the same language when you work on your template)
- 4 locales: https://pontoon.mozilla.org/xx/engagement/emails/2018/jan_mobile_app_updates.lang/ (change xx to es, pl, pt-BR, ru. They are case sensitive)
- fr: https://pontoon.mozilla.org/fr/engagement/emails/2018/jan_mobile_app_updates_fr.lang/
- id: https://pontoon.mozilla.org/id/engagement/emails/2018/jan_mobile_app_updates_id.lang/

Comment 4

[Peiying Mo [:CocoMo]]

@jessica, please proceed to the next step for verification testing.

To see who did helped with the localization request, go to the links in Pontoon, go through some strings and you will see the contributors' names on the bottom right corner. Click on the contributor's name, it will take you to the page where you can get the email address.

If there are corrections to be made, please have them file a bug per locale, and gather all the feedback there. Make that bug a dependent of this master bug.

Comment 5

[Jessica Osorio [:josorio]]

Hi Peiying,

We just sent the first ES Test Proof. I went through all the work done for this request in here:https://pontoon.mozilla.org/es/engagement/emails/2018/jan_mobile_app_updates.lang/?string=175240  and I found the following contributors helped with this request: 
[e-mail]
[e-mail]
[e-mail]

I added the above to the test list. All of them except [e-mail] should be able to see this in their inbox. My system is telling me that [e-mail] is not double opted in to this newsletter. Can you ask this person to complete this process by signing up here (https://www.mozilla.org/newsletter/firefox/) and confirming their email (in the confirmation email they will receive soon after signing up). *** of course, this is only if they want to take part in QAing the proof).

As this is the first time we do this QA review this way, lets just focus on ES for now before moving on to the next locale. 

What's the best way to keep track of ES only feedback/confirmation? Do we have unique bugs for each locale? A bug per locale would be useful for keeping feedback in one place, per locale (during the QA phase). 

Thank you!

Comment 6

[Peiying Mo [:CocoMo]]

@Jessica, 

Yes, let's try out the process in one locale before moving to other locales. [e-mail] is an "es" lead. I will send her an email to make sure she completes signup for the newsletters if she wants to be involved in QA. Do you have a list of contributors to the project who have not done so? We can send them an email regarding this now instead of later.

As for how to gather feedback, only if they have corrections to make, ask each community to file a bug for one language. It is easier for them to collaborate and you to have all the final input in one place. Of course, the source of truth is in Pontoon. Even if the comment is made in the bug, each community needs to make sure the corrections are updated in Pontoon. Same or similar content can be referenced for future requests

Comment 7

[Peiying Mo [:CocoMo]]

As communicated, avelper has signed up for the newsletters, thus ready to be part of the QA process.

Comment 8

[Jessica Osorio [:josorio]]

Hey Peiying,

I just resent the ES proof to the ES contributors who assisted with this request.

We do not have a set list of contributors, apart from the one I already provided a while back because this is a new process. As we discussed I will pick up the contributors' info from Pontoon, when it's 100% and I can see who contributed to each request.

Thank you!

Comment 9

[Jessica Osorio [:josorio]]

In and effort to move this along, I just sent the pt-BR test too. To our internal staff connected to this project and the two contributors that I saw contributed in pontoon: 
[e-mail]
[e-mail]

I also added Zilmar because I know he likes to be kept in the loop.


Peiying, I just sent you a meeting request. Lets try to sync up soon to get caught up on this new process.

Thank you,

Jess

Comment 10

[Peiying Mo [:CocoMo]]

@Ángela, @jlG, test email in "es" for QA was sent to you. Please confirm in this bug if it is ready to go. If there are chances to make, please file a separate bug and cc me on the bug on the changes you would like to make. Thank you!

Comment 11

[Peiying Mo [:CocoMo]]

@Maykon, pt-BR test email was sent to you for QA. Please let us know if it is good to go by commenting in this bug. If there are changes to be made, then file a separate bug and cc me on it. Thanks!

Comment 12

[Maykon Chagas [:mchagas]]

(In reply to Peiying Mo [:CocoMo] from comment #11)
> @Maykon, pt-BR test email was sent to you for QA. Please let us know if it
> is good to go by commenting in this bug. If there are changes to be made,
> then file a separate bug and cc me on it. Thanks!

Hi @Peiying,

The email was almost good, but I'm opening a new bug as you asked me for do it.

You've probably will be notified, but just to let all now this is the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1442585

Thank you!

--
On behalf of L10n pt-BR team

Comment 13

[avelper]

(In reply to Peiying Mo [:CocoMo] from comment #10)
> @Ángela, @jlG, test email in "es" for QA was sent to you. Please confirm in
> this bug if it is ready to go. If there are chances to make, please file a
> separate bug and cc me on the bug on the changes you would like to make.
> Thank you!

Hi! We checked and all good.

Thanks for the ping!

Cheers,
Ángela.

Comment 14

[Peiying Mo [:CocoMo]]

Hello All

Jessica O has sent you a test email for verification purpose. Could you please confirm if the email in your language is good to go. If so, please confirm in this bug. 

If not, please file a separate bug and list the strings you have changed (URL from Pontoon will do) to help with the update.

Emails in the following languages were sent: fr, id, pl, ru

Thanks!

Comment 15

[Piotr Drąg [:piotrdrag]]

I haven’t received any emails about this.

Comment 16

[Piotr Drąg [:piotrdrag]]

I got it a few minutes ago, and it looks good to go (pl).

Comment 17

[Victor Bychek]

RU is fine!

Comment 18

[rodin]

There is this strange "More 4 of 487" prefix in the subject line for ID test email: https://www.dropbox.com/s/744ron1f2jzaqp6/Tangkapan%20layar%202018-03-13%2000.46.41.png?dl=0
Otherwise everything else looks good to go.

Comment 19

[Peiying Mo [:CocoMo]]

Thanks for the quick replies. Jessica will fix the recommended changes.

Comment 20

[Peiying Mo [:CocoMo]]

Looks like all the reviews are done, and implementations of recommended changes were also reviewed and signed off. Mark the bug fixed.