1498613 - [Legal]: Firefox Rocket brand change

Status: RESOLVED FIXED

(www.mozilla.org :: L10N, enhancement)

Description

[Peiying Mo [:CocoMo]]

@pmac, we need your help once the rebrand change is completed. Go-live is set on Nov 1.

Comment 1

[Paul [:pmac] McLanahan]

Sounds good. Thanks :CocoMo.

Comment 2

[Paul [:pmac] McLanahan]

Attachment: GitHub Pull Request

This PR updates to the latest legal-docs, adds the /privacy/firefox-lite/ URL and redirects /privacy/firefox-rocket/ to the new URL.

Comment 3

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

If we can do a time-based release, let's align the press event which will happen on (UTC -7)  21:00  Oct-31 == (UTC +7)  11:00  Nov-1st

Comment 4

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Two more items:
1. Would be great if we can redirect the old link "https://www.mozilla.org/en-US/privacy/firefox-rocket/" to the new one.
2. There is going to be a new logo. Let me forward that asset separately.

Comment 5

[Paul [:pmac] McLanahan]

(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #4)
> Two more items:
> 1. Would be great if we can redirect the old link
> "https://www.mozilla.org/en-US/privacy/firefox-rocket/" to the new one.

As I mentioned in my last comment this is already done as part of the existing pull-request.

> 2. There is going to be a new logo. Let me forward that asset separately.

Ah. I didn’t know that. We’ll add this to the current pull-request or as part of a followup. Thanks for the heads-up.

Comment 6

[Paul [:pmac] McLanahan]

Wesley, is that new logo you pointed me to in the google doc public? IOW can we add it to the pull-request now, or should we add that later after a certain date?

Comment 7

[Paul [:pmac] McLanahan]

(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #3)
> If we can do a time-based release, let's align the press event which will
> happen on (UTC -7)  21:00  Oct-31 == (UTC +7)  11:00  Nov-1st

Do we need the legal doc to go live at exactly this time? It's possible to do but will require more work and some coordination with the broader Websites team. I'll also have to redo the pull-request to put all of the changes behind a switch.

If we don't need it to go live at exactly 2100 Pacific then we can do it a bit earlier that day and we can just do it with a deployment rather than a switch.

Let me know what you think and I can get more people involved if need-be.

Comment 8

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

(In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #7)
> (In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #3)
> > If we can do a time-based release, let's align the press event which will
> > happen on (UTC -7)  21:00  Oct-31 == (UTC +7)  11:00  Nov-1st
> 
> Do we need the legal doc to go live at exactly this time? It's possible to
> do but will require more work and some coordination with the broader
> Websites team. I'll also have to redo the pull-request to put all of the
> changes behind a switch.

In such case I think it's ok to go live a few hours before 21:00 PDT.
Hope this make things easier :)
> 
> If we don't need it to go live at exactly 2100 Pacific then we can do it a
> bit earlier that day and we can just do it with a deployment rather than a
> switch.
> 
> Let me know what you think and I can get more people involved if need-be.

Comment 9

[Paul [:pmac] McLanahan]

(In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #6)
> Wesley, is that new logo you pointed me to in the google doc public? In other words, can
> we add it to the pull-request now, or should we add that later after a
> certain date?

Any info on this question I asked above? I can add the logo change to the PR, but that would mean attaching it to a public issue/pull-request on github.

Comment 10

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

(In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #9)
> (In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #6)
> > Wesley, is that new logo you pointed me to in the google doc public? In other words, can
> > we add it to the pull-request now, or should we add that later after a
> > certain date?
> 
> Any info on this question I asked above? I can add the logo change to the
> PR, but that would mean attaching it to a public issue/pull-request on
> github.

Yes. Github is fine.

Comment 11

[Paul [:pmac] McLanahan]

Great. I've updated the pull-request to include the logo change.

Comment 12

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

(In reply to Paul [:pmac] McLanahan ⏰ET needinfo? me from comment #7)
> (In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #3)
> > If we can do a time-based release, let's align the press event which will
> > happen on (UTC -7)  21:00  Oct-31 == (UTC +7)  11:00  Nov-1st

Actually we'll push apk to google play at 11am Nov-1st (UTC+8) == 8pm Oct-31 (UTC-7), which is a hour before the press event.
> 
> Do we need the legal doc to go live at exactly this time? It's possible to
> do but will require more work and some coordination with the broader
> Websites team. I'll also have to redo the pull-request to put all of the
> changes behind a switch.
> 
> If we don't need it to go live at exactly 2100 Pacific then we can do it a
> bit earlier that day and we can just do it with a deployment rather than a
> switch.
> 
> Let me know what you think and I can get more people involved if need-be.

As I commented earlier, please feel free to merge a few hours earlier than the timing mentioned above. 
I also replied on github.

Comment 13

[[github robot]]

Commit pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/232dd50df7eed25046ab117ef45fb2041a348033
Firefox Rocket -> Lite privacy document changes

Fix bug 1498613

Comment 14

[Paul [:pmac] McLanahan]

I've merged the changes and you can preview them on dev: https://www-dev.allizom.org/en-US/privacy/firefox-lite/

I'll be pushing them to production in the morning.

Comment 15

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Hi :pmac

Two links get 404 pages because we're not changing Rocket's github. (at least not at this moment)
Can you rollback below two URLs?

Read detailed documentation for Firefox Lite here => 
https://github.com/mozilla-tw/Rocket/wiki/Telemetry

Learn more about Referral and Campaign Data  => 
https://github.com/mozilla-tw/Rocket/wiki/Telemetry#install-campaign-tracking

Comment 16

[Paul [:pmac] McLanahan]

Ah yes. I called that out at some point but was told it was changing. This needs to be changed in the legal docs, so it will take a while. Here are the steps:

1. Make a PR against legal-docs
2. Get that PR reviewed and merged
3. Make a PR against bedrock to update legal-docs
4. Get that PR reviewed and merged
5. Deploy those changes to dev
6. Deploy those changes to production

That's all just FYI. I'll get started.

Comment 17

[Paul [:pmac] McLanahan]

Attachment: pr 1177: Fix bug 1498613: Revert Firefox Lite github link to Rocket repo

Comment 18

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/bedrock/pull/6388

Comment 19

[[github robot]]

Commit pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/1ed3a2793385016e8449f6aba117b4d0213af2d5
Fix bug 1498613: Update legal-docs to fix Fx Lite privacy policy

Links to github were changed but the Rocket repo's name was not.

Comment 20

[Paul [:pmac] McLanahan]

Steps 1-5 from comment #16 are now done. You can check the changes on dev now:

https://www-dev.allizom.org/en-US/privacy/firefox-lite/

The links are working for me. As soon as we have a fully successful test run of dev I'll start the production deployment.

Comment 21

[Paul [:pmac] McLanahan]

Prod deployment is done. All should now be finished with the privacy page.

Comment 22

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Yes. Saw it up and running. thank you :pmac