Closed Bug 488497 Opened 15 years ago Closed 15 years ago

Geolocation informational page (for beta)

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: dougt, Assigned: wenzel)

References

(
URL
)

Details

(Keywords: fixed1.9.1, Whiteboard: [server-side][geo]) 

When 488218 lands, it will have a link to mozilla.com that allows the user to find out more about how geolocation works, read privacy policy, and discover how to use the feature.  Currently, the url I am using in bug 488218 is:

http://www.mozilla.com/geolocation
Flags: blocking-firefox3.5?
Should be mozilla.com/firefox/geolocation IMO
Flags: blocking-firefox3.5? → blocking-firefox3.5+
Priority: -- → P1
Whiteboard: [server-side]
Doug & I have touched base offline and will start figuring this page out soon.

Seeing that it just got bumped up to a 3.5 blocker raises another question...will this page be mandatory for l10n? If so, that changes everything (and makes things much more difficult), b/c the localizers already have their hands full with existing content (which I've promised to them by end-of-month).

To put it another way, if this page could be en-US only for launch (or at least not a mandatory l10n page) then I'd feel a lot better about it.
This page is tier-1 l10n required for launch. It's en-US-something required for beta 4 launch ... as in it can't be 404.

I'm happy to help review/work up interim content. We'll likely need to get final approval from Google on the wording. On the plus side, though, they're also likely to help us do the tier-1 l10n work for the page if we ask them nicely.
(In reply to comment #3)
> This page is tier-1 l10n required for launch. 
Ok, got it. Copying Seth & Pascal as a heads-up to them.

>It's en-US-something required for beta 4 launch ... as in it can't be 404.
Got it. Just exchanged emails with Morgamic and he's in.

> I'm happy to help review/work up interim content. We'll likely need to get
> final approval from Google on the wording. On the plus side, though, they're
> also likely to help us do the tier-1 l10n work for the page if we ask them
> nicely.
Duly noted. I'm happy to drive this in terms of getting the page up on the site by b4 (Tuesday?). I think the #1 condition to making that happen would be having the interim content really soon. Could you, or some other geolocation expert (Doug?), work up something basic by tomorrow? I can help wordsmith if needed.

Then we could be coding the page while you run it by Google for approval. Any further changes they have could be made pretty easily, I'd think.

So, if we can get the content by EOD tomorrow we should be in good shape. Sound doable?
Quick update:
- I wrote up a draft of the content based on info from Doug & Jay and have sent it to Jay for review
- after Jay approves, Morgamic & crew will get the page staged (final URL will be www.mozilla.com/en-US/firefox/geolocation)
- then it's onto QA and the beta...

Definitely an aggressive schedule, but right now we're on track for making it happen. We'll reconvene next week to work out more fully fleshed out content for the final 3.5 page.
Whiteboard: [server-side] → [server-side][geo]
Assignee: doug.turner → fwenzel
The styling for this page should be based on http://www.mozilla.com/firefox/phishing-protection

John: are we gonna get new art or re-use something from somewhere else?
I just committed a placeholder page (r24565). It's available here: https://www-trunk.stage.mozilla.com/en-US/firefox/geolocation/ .

It will obviously need actual text, and possibly additional graphics etc.
(In reply to comment #6)
> The styling for this page should be based on
> http://www.mozilla.com/firefox/phishing-protection 
> John: are we gonna get new art or re-use something from somewhere else?
There's no way to get new art like on Phishing Protection in time for the beta...but, if we think it's necessary for the final version of the page that's definitely something to discuss and plan out next week. I'm certainly up for it.
(In reply to comment #7)
> It will obviously need actual text, and possibly additional graphics etc.
Just emailed the correct text to Frédéric...no additional graphics needed at this time.

Thanks!
(In reply to comment #7)
> I just committed a placeholder page (r24565). It's available here:
> https://www-trunk.stage.mozilla.com/en-US/firefox/geolocation/ .
> 
> It will obviously need actual text, and possibly additional graphics etc.

This is certainly fine, design-wise, for b4.

(In reply to comment #8)
> beta...but, if we think it's necessary for the final version of the page that's
> definitely something to discuss and plan out next week. I'm certainly up for
> it.

Not a blocker, but definite nice to have. Again, could re-use one of the existing globe or signpost like pieces that we may have in hand already.
Thanks, John. The text contained three apparent links, the Mozilla privacy policy is obvious but I have questions about the Google ones.

- Google has a general privacy policy but also numerous specific ones. Which one do you want to link to here?
- where is the "Google Location Services" link supposed to point to?
I added the text (r24578). I also used the UFO background which I find deliciously ironic on the page about geolocation. If you want any other graphic or just the plain background again, let me know.

It's available on www-trunk for you to look at again.
I don't like hiding content like this by default -- I'd prefer to have the page expanded with a <ul> for the header links at the top.  Are you guys married to the expand/collapse action?  I don't think it's doing users a service there.
No strong opinions on comment #13...while we resolve that and any other minor issues, I've filed the QA bug so we can begin that process.
Depends on: 489278
Can I get the link targets, please? Once we get these in (pending QA) we are rrrrready to rrrrumble, so to say.
(In reply to comment #15)
> Can I get the link targets, please? Once we get these in (pending QA) we are
> rrrrready to rrrrumble, so to say.
I talked to Jay and Stuart and the latest word is that we won't likely have the Google links (both of them) in time for the beta release, so let's just leave those out altogether (for now).

So:
- don't make Google Location Services a link
- remove the link & text about the Google privacy policy

Thanks!
If we push the exiting version to live, IMO, this bug ceases to be a P1 blocker. Can we get that current version pushed?
Whiteboard: [server-side][geo] → [needs push to live][server-side][geo]
(In reply to comment #16)
> So:
> - don't make Google Location Services a link
> - remove the link & text about the Google privacy policy

r24678. This should be done, please push it live at will.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #18)
> (In reply to comment #16)
> > So:
> > - don't make Google Location Services a link
> > - remove the link & text about the Google privacy policy
> 
> r24678. This should be done, please push it live at will.

http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-US/firefox/geolocation/index.html?revision=24678&pathrev=24678
"... and is done in a way that totally respects your privacy."
"... and is done with the utmost respect for your privacy."
"Your privacy is extremely important to us ..."

Yeah, right... Introducing completely unnecesary, unique cookie-like identifier is definitely privacy-friendly...

"a temporary cookie-like identifier"

Define "temporary" here. It is 2 weeks period, if I read the source correctly. I'm pretty sure average user doesn't think about 2 weeks period as "temporary", so don't manipulate, please.

"Am I being tracked?
No. ..."

Yes.
re: comment 19 - please file a follow up bug. We'll be revising this text for final, anyway; this content is good enough for beta 4.
Summary: Geolocation informational page → Geolocation informational page (for beta)
Ugh, wrestling with Kubla, but I'll get it posted.
http://www.mozilla.com/en-US/firefox/geolocation/ is live; verified FIXED
Status: RESOLVED → VERIFIED
Whiteboard: [needs push to live][server-side][geo] → [server-side][geo]
One quick little thing and then it looks good. This:

And, like all elements of Firefox it’s being created using standards to ease
adoption by Web developers.

Should be:

And, like all elements of Firefox, it's being created using standards to ease
adoption by Web developers.

Why? Because the 'like all elements of Firefox' is a parenthetical element or
in simpler terms, a part of a sentence that can be removed without changing the
essential meaning of that sentence.
Do we also need a follow up bug for the artwork on the page - it looks rather sparse.
(In reply to comment #24)
> Do we also need a follow up bug for the artwork on the page - it looks rather
> sparse.
We're in the process of creating an improved version of this page for the final release...will have slightly revised copy, a demo and better artwork. When all that is ready I'll file a new QA bug to cover it.
(In reply to comment #24)
> Do we also need a follow up bug for the artwork on the page - it looks rather
> sparse.

The geolocation.css file is missing, otherwise it'd have space ships: Compare https://www-trunk.stage.mozilla.com/en-US/firefox/geolocation/ .

John or Mike, can you push that file live, too?
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(In reply to comment #26)
> John or Mike, can you push that file live, too?
No problem. Just to confirm, is the only file I need to push this one? 
/style/tignish/geolocation.css
Yes, it is!
(In reply to comment #25)
> We're in the process of creating an improved version of this page for the final
> release...will have slightly revised copy, a demo and better artwork. When all
> that is ready I'll file a new QA bug to cover it.

John, can you CC me on this bug when you file it?  Thanks.
Why is this REOPENED yet fixed1.9.1? Either the fixed1.9.1 needs to be removed or we need to resolve this one as FIXED and perhaps mark the follow-up as blocking?
I think this one is done.  We've had to change this 30 times already.  Whatever is left shouldn't be blocking imo.
Yea, as per comment #25 and comment #22 our work for the beta page is done and John will file another bug for any pre-final release polishing we'll need to do.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Most of the work for this page has actually been taking place over in https://bugzilla.mozilla.org/show_bug.cgi?id=489278. But, that bug is closed and localization is well underway.

So, as far as I'm concerned this page is finished and shouldn't be addressed again until after 3.5.
Sounds good -- thanks Jonn. :)
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.