Closed Bug 967046 Opened 10 years ago Closed 10 years ago

Document our localization plan for emails

Categories

(Webmaker Graveyard :: Engagement Ladder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: matt, Assigned: alicoding)

References

Details

(Whiteboard: infrastructurev1)

Attachments

(1 file)

* Now that we're scaling up our use of email on Webmaker.org, we need to flesh out our localization plan for outbound emails

* QUESTIONS:

* Jbuck: will Postal Service support localization? 

* Ali: where should we create a stub for this localization?
Flags: needinfo?(jon)
Flags: needinfo?(ali)
So, my quick thought on this one is that we should do it the same way with EOY campaign.

I believe doing it in Transifex is ideal and way to go for us, but we should maybe create a new project just for Webmaker-Email localization and maybe get some help from our current contribute or have a pay per translation service to do that since we need to have a profession translation for the email and get it done quickly as we want.
Flags: needinfo?(ali)
* @ Jbuck: will Transifex play well with Postal Service?
Yep, it'll work with localization
Flags: needinfo?(jon)
Depends on: 966336
Assignee: nobody → ali
Status: NEW → ASSIGNED
Component: General → Engagement Ladder
QA Contact: brett
Whiteboard: [workweek][workweek-engagement][engagement] → [workweek][workweek-engagement][engagement][infrastructure]
Ali work can continue with this as it will still use postal service.
Whiteboard: [workweek][workweek-engagement][engagement][infrastructure] → infrastructurev1
Depends on: 992982
Depends on: 995053
Depends on: 995054
Comment on attachment 8408333 [details] [review]
https://github.com/mozilla/node-webmaker-postalservice/pull/7

some things to fix up noted in github
Attachment #8408333 - Flags: review?(jon) → review-
Attachment #8408333 - Flags: review- → review?(jon)
Blocks: 995053, 995054
No longer depends on: 995053, 995054
Attachment #8408333 - Flags: review?(jon) → review+
Not sure what else we need in this one? Most of our tickets have been landed. Or do we need to write the process that we need somewhere?
I think we're good here because we localize it in the exact same way we localize everything else.
Closing this bug then \o/
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: