>>Project/Request Title: Last Firefox OS + YOU Newsletter >>Project Overview: The final Firefox OS + YOU Newsletter email send Email content here: https://docs.google.com/document/d/1I14lYqZ2qJnpSWmGi5mbCOR8zMI8fFk9D6Rz6xhRZkk/edit >> Creative Help Needed: Copy: Yes Design: No Video: No Other: No >>Creative Specs: Copy: Editing the content to ensure right tone of voice. >>CTA and Design: Link to the copy: https://docs.google.com/document/d/1I14lYqZ2qJnpSWmGi5mbCOR8zMI8fFk9D6Rz6xhRZkk/edit Some sensitivity/background should be given to our l10n teams when Brynne emails them to alert them about this being the last email, thanking them for all their time, etc.. >>Expected Launch Date: 2016-02-22 >>Mozilla Goal: Firefox OS >>Mozilla Creative Collective: No >>Points of Contact: email@example.com; firstname.lastname@example.org
I'm trying to include Porfirio in the bug but it didn't accept his email.
(In reply to Marcia from comment #1) > I'm trying to include Porfirio in the bug but it didn't accept his email. It looks like he doesn't have a Bugzilla account, at least not under either of the email addresses in the phonebook. I'll give this a read now and let you know when I'm done.
Assignee: jbalaco → matej
I made a few edits. Have a look and let me know what you think.
Hi Matej, The edits look good to me. Thanks, Marcia.
Hi Brianna, How are you? I would like to check about next steps on this Newsletter. Do you have dates in mind to send it? Thanks, Marcia.
Hi Marcia - Checking in to see if the copy is ready to send to l10n teams? Also, when can we expect design for coding? Firefox + You is scheduled to send March 17, so I recommend a send date of March 24 for this email. Does that sound okay? Thanks, Brynne
Hi Brynne, The copy is ready, please send to l10n. Yes, the dates sounds good. Thanks, Marcia.
Hi Team - It looks like we're missing a subject line and pre-header. Let me know once that's added to the copy doc, and I'll send to the l10n teams for localization. Thanks, Brynne
I added some options to the gdoc and flagged a few people for comments.
You need to log in before you can comment on or make changes to this bug.