Closed Bug 988989 Opened 11 years ago Closed 9 years ago

[Legal][Cloud Services]: FF Cloud Services Privacy Notice need to be localized

Categories

(Mozilla Localizations :: Other, defect)

Product:
Mozilla Localizations
Component:
Other
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: CocoMo, Assigned: jgruen)

References

Details

(Whiteboard: URL should direct to privacy hub)

Hi Răzvan, This is a new request. For now, it will be one bug. If there are language specific review comments, I will file individual bugs accordingly *Project*: Firefox Cloud Service Terms of Use *Locales (11)*: cs, de, el, es (Spain), hr, hu, it, pl, pt-BR, sr-Latn, zh-CN, *Deadline*: 2 weeks or sooner *File location*: https://github.com/mozilla/legal-docs/tree/privacy-website-update/firefox_cloud_services_PrivacyNotice Please Note: - sr-Latn is currently labeled as sr-SP, which is incorrect, but the folder explanation says what it is supposed to be - L10n communities will be given a chance to review this. Not all will participate, but it will be case by case. - Do leverage any existing legal documentations you have localized and apply the same style and terminology to this request. - For the time being, the branding guideline states that they remain in English. When in doubt, reference http://transvision.mozfr.org/. It doesn't cover all aspects, but this is the best resource we have now. I will send an email to Magdalena about this job request. Thank you, Peiying
Assignee: nobody → corneliu
Hi Wil, Could you please merge the change requests before the agency can download the files? Thank you, Peiying
There are no open pull requests: https://github.com/mozilla/legal-docs/pulls
oops, I guess I don't know how to read the color or fully understand the process. All I see is green color, but it is the "original" content. Thanks for confirming.
Hi, Wil, We are trying to work on "privacy-website-update" branch for this file (Privacy Notice), but there seems to be big differences between the content of the file in this branch compared to "master" branch. In addition, the content of the file in "privacy-website-update" branch seems to be incomplete or just a draft. For your convenience, here are the URLs for both branches: https://github.com/mozilla/legal-docs/blob/master/firefox_cloud_services_PrivacyNotice/en-US.md https://github.com/mozilla/legal-docs/blob/privacy-website-update/firefox_cloud_services_PrivacyNotice/en-US.md Please, advise which content should we use for localization. Thank you, Răzvan P.S.: Thank you, Peiying for spelling my name correctly.
Peiying will have to help with that. I can help solve technical questions and merge issues but regarding the actual process, flows, or how branches are being used, I don't know much. When in doubt I'd always go with master.
Flags: needinfo?(pmo)
Wil and Răzvan, I forwarded you the email from Mika on the instruction of the location of the "final" files. I have the same issue on the Terms of Service file as well. Wil, I am currently in Paris now so please work with Mika to get clarification on the file setup. Mika, can you comment again on how this is set up? Maybe it is best to have a quick call with Wil.
Flags: needinfo?(pmo)
Răzvan - the content of the file in "privacy-website-update" branch is correct and this is what you should translate. It is intended to be much shorter than the existing content on the "master" branch. Much of the existing content on the master branch was moved to another URL. Thank you for checking in on this. Let me know if you have any questions. Best, Mika
(In reply to Peiying Mo from comment #0) > Please Note: > - sr-Latn is currently labeled as sr-SP, which is incorrect, but the folder > explanation says what it is supposed to be > - L10n communities will be given a chance to review this. Not all will > participate, but it will be case by case. > - Do leverage any existing legal documentations you have localized and apply > the same style and terminology to this request. > - For the time being, the branding guideline states that they remain in > English. When in doubt, reference http://transvision.mozfr.org/. It doesn't > cover all aspects, but this is the best resource we have now. Just adding another instruction - the term "Firefox Cloud Services" should remain in English latin script.
Thank you for clarifying, Mika. Kind regards, Corneliu
Flod and Pascal will coordinate the community review once the translations are back on github. Communities can decide if they want to review the file before it goes to production.
Hi, Wil, Flod and Pascal, I committed the changes for all 11 languages and issued the following pull requests (one for each file): https://github.com/mozilla/legal-docs/pull/30 https://github.com/mozilla/legal-docs/pull/31 https://github.com/mozilla/legal-docs/pull/32 https://github.com/mozilla/legal-docs/pull/33 https://github.com/mozilla/legal-docs/pull/34 https://github.com/mozilla/legal-docs/pull/35 https://github.com/mozilla/legal-docs/pull/36 https://github.com/mozilla/legal-docs/pull/37 https://github.com/mozilla/legal-docs/pull/38 https://github.com/mozilla/legal-docs/pull/39 https://github.com/mozilla/legal-docs/pull/40 https://github.com/mozilla/legal-docs/pull/41 Wil, could you, please, merge the changes? I know I should have done it all in one commit, like I did before for other requests, but I had some trouble pushing my changes to "privacy-website-update" branch instead of "master". Thank you, Corneliu
all done
Thank you, Wil.
Hello localizers, Please review the content on github or production. If changes need to be made, please file a separate bug and make it blocking this one bug. In addition to making changes, make sure to document some key findings so we can communicate the agency who provided localization service. This will help improving quality moving forward. - Github file: https://github.com/mozilla/legal-docs/tree/master/firefox_cloud_services_PrivacyNotice (select your locale to view the source). - On Production: https://accounts.firefox.com/xx/legal/privacy (replace xx with your locale code). Thank you, Peiying
Assignee: corneliu → pmo
Hi, the SUMO link in the final section always leads to the en-US article, which should not happen. Also, I’m wondering about the phrase „Learn More.“ that appears twice. Does this refer to the respective sections below?
Hi Michael, Like the other bug, the links are pointing to the US site. Mozilla Privacy is yet to be localized, so for now, we have to live with it. I will get the SUMO site fixed. As for the "Learn More" phrase, can you be more specific? Thank you.
(In reply to Peiying Mo from comment #17) > SUMO links to be updated: That's not necessary, just remove en-US from the English link, SUMO will manage the redirect. Old link: https://support.mozilla.org/en-US/kb/cookies-information-websites-store-on-your-computer New link: https://support.mozilla.org/kb/cookies-information-websites-store-on-your-computer
Hi Peiying, (In reply to Peiying Mo from comment #16) > As for the "Learn More" phrase, can you be more specific? Thank you. On the page <https://accounts.firefox.com/en/legal/privacy> the phrase „Learn more.“ appears twice. Usually, when this phrase appears somewhere on a webpage, it is a link to some other page, which gives further information about whatever the referencing page was about. In this case, the phrase is no link, and it is followed by a full stop. If „Learn more“ was to refer to the respective lists below, I would expect a colon instead of a full stop. It is not quite clear to me, what purpose the phrase serves in this context. I hope I could convey what I’m talking about. ;-) (In reply to Peiying Mo from comment #17) > Mozilla Privacy Policy is yet to be localized. For now, pointing to en-US is > the correct behavior. Afaik, just like SUMO, mozilla.org should automatically pick the user’s language if none is provided in the URL. Just a suggestion, but maybe change it now to save a step later?
I have the feeling that this "Learn more" was used to show/hide the next paragraph at some point, like it happens on Firefox OS Privacy. Doesn't make much sense in the current document.
Depends on: 1012379
I have updated the SUMO links in github per comment #17. Flod, I still have to update one by one to remove en-US, so I change to those direct links. Thank you for the review comments provided this far, I have relayed them to the agency.
Hi guys, Nothing more to add on my side (Spanish), except the aforementioned issue related to SUMO link directing to the en-US article page. Thank you,
Hi Mika, Can you check the text on "Learn More" stated in comment #15? It seems redundant.
Assignee: pmo → udevi
(In reply to Peiying Mo [:CocoMo] from comment #23) > Hi Mika, > > Can you check the text on "Learn More" stated in comment #15? It seems > redundant. Do you mean the "Learn More" text that appears here: https://accounts.firefox.com/xx/legal/privacy I believe the correct link is here: http://www.mozilla.org/en-US/privacy/firefox-cloud/
Hi - I think i see what you're talking about for this link: https://www.mozilla.org/en-US/privacy/firefox-cloud/ The "Learn More" that is not an expander is duplicative. Please delete. Thanks!
Assignee: udevi → pmo
Mika, Please communicate with the cloud service team on this duplicates. It looks fine in the source but it shows up on the web. http://www.mozilla.org/en-US/privacy/firefox-cloud/ Assigning the bug back to you as I can't fix it on my end.
Assignee: pmo → udevi
Hey John, Similar issue to Bug 988986. Can you please update the Privacy Notice URL that appears on the Cloud Sign-up/Log-in screen so that it directs users to: http://www.mozilla.org/en-US/privacy/firefox-cloud/ Please let me know if you have any questions, or if someone else is the right person to help with this. Thanks! mika
Assignee: udevi → jgruen
Status: NEW → ASSIGNED
Flags: needinfo?(jgruen)
Whiteboard: URL should direct to privacy hub
hello, any update on this bug?
In some FxA contexts, navigating to a 3rd party site from inside the FxA flow is problematic. In the case of FxA + Marketplace on 1.3/4 devices, the user has no chrome-level ability to get back to the original flow. In iframed FxA oauth cases, opening a 3rd party site adds distraction to UI. The FxA team needs to continue hosting its own versions of the ToS and PN to accommodate these cases. I think the best move here is to have a discussion about whether, and in what contexts, it makes sense to link to the privacy & (forthcoming) terms hubs from FxA given the sensitivity of the account creation funnel.
Flags: needinfo?(jgruen)
Locale: cs / Czech, de / German, el / Greek, es-ES / Spanish (Spain), hr / Croatian, hu / Hungarian, it / Italian, pl / Polish, pt-BR / Portuguese (Brazilian), sr / Serbian, zh-CN / Chinese (Simplified)
Isn't this fixed already?
yes, we can close the bug!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.