Closed Bug 1264864 Opened 8 years ago Closed 7 years ago

Sun setting MasterFirefoxOS.mozilla.org

Categories

(Websites Graveyard :: Master Firefox OS, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mkhoo, Unassigned)

References

()

Details

Suggest:
Monitor the ping and if the there is no more selling, we can determind to pull down. Target decommissioning @ Q3, 2016.
Marvin: this bug is in the wrong place; it's not a Governance bug. Please can you move it?

Thanks,

Gerv
Hi Gervase,
Sorry for putting on wrong component. Do you know which component I should place if I want to pull down this website?
Thanks, and sorry for the confusion here.
Perhaps the "Master Firefox OS" component in the "Websites" product? :-)

Gerv
Assignee: gerv → nobody
Component: Governance → Master Firefox OS
Product: mozilla.org → Websites
Version: other → unspecified
Wow, thanks for your prompt feedback!!! I didn't noticed it. Appreciated!!!
Marvin:

Hi I wanted to followup with you on this (my team maintains this website). We have in our notes (from when John Bernard) was here that the site needed to stay live until end of 2017.

Based on this bug it sounds like we could do this earlier. Are you the new owner and if so can you let me know when you think we could de-com.
Flags: needinfo?(mkhoo)
(In reply to Ben (:bensternthal) from comment #5)
> Marvin:
> 
> Hi I wanted to followup with you on this (my team maintains this website).
> We have in our notes (from when John Bernard) was here that the site needed
> to stay live until end of 2017.
> 
> Based on this bug it sounds like we could do this earlier. Are you the new
> owner and if so can you let me know when you think we could de-com.

KW: Based on the activation activity (we are still getting over 4-5k (~3+k phones, ~1k TV) activations a day) I don't think we should take down the site yet.  Can we do another checkpoint in mid December?  See https://metrics.services.mozilla.com/fxos-ftu-dashboard/#
Flags: needinfo?(bsternthal)
Yes will check in mid dec.
Flags: needinfo?(bsternthal)
clear my ni here.

The original discussion I had with David Palomino was de-com the website if we don't have any sales or any pings generated from this website.

I believe this website purpose is to create a quick peek and aim for training, for those (customers / partners) who like to understand more about the operating system's highlighted features, so to build consistent tone and languages while doing product marketing.
This website contents contain only for handheld devices.

we can re-check in mid dec.
Flags: needinfo?(mkhoo)
Looks like the activity report is no longer valid (the most recent data is August 2016).  I suggest we take down the MasterFirefoxOS.mozilla.org pages.  What will a user experience be once that happens?  Do we have a 'graceful' way to handle it?

Want to check with Michael Henretty to see if there is anything on those pages that should be made available to the community via another mechanism.
Flags: needinfo?(mhenretty)
Karen: I would suggest we use the same approach we used with mobilepartners. Redirect the URL to mozilla.org.
After a cursory glance, I don't think there is anything on there we need to save. Thanks for checking.
Flags: needinfo?(mhenretty)
(In reply to Ben (:bensternthal) from comment #10)
> Karen: I would suggest we use the same approach we used with mobilepartners.
> Redirect the URL to mozilla.org.

Hi Ben - Based on Michael's response please proceed with taking down MasterFirefoxOS.mozilla.org and redirect the URL to Mozilla.org at you / your team's convenience.
Understood, will get this on the backlog.

Thanks for the help.
Decommissioning of the website has begun. Two open questions:

 1. masterfirefoxos.com expires on 03-jun-2017. Do we let this expire or do we renew? In the later case for how long?
 
    Currently www.masterfirefoxos.com redirects to masterfirefoxos.mozilla.org

 2. SSL certificate of masterfirefoxos.mozilla.org expires on 27-feb-2017. Do we let this expire or do we renew? In the later case for how long?
(In reply to Giorgos Logiotatidis [:giorgos] from comment #14)
> Decommissioning of the website has begun. Two open questions:
> 
>  1. masterfirefoxos.com expires on 03-jun-2017. Do we let this expire or do
> we renew? In the later case for how long?

{KW} I assume this relates to Mozilla's ownership of the URL.  Is that correct? If so I will check with Marketing to see if they believe there is value in Moz renewing the registration of the URL.

>     Currently www.masterfirefoxos.com redirects to
> masterfirefoxos.mozilla.org
> 
>  2. SSL certificate of masterfirefoxos.mozilla.org expires on 27-feb-2017.
> Do we let this expire or do we renew? In the later case for how long?

{KW} If we redirect the masterfirefoxos.com URL to mozilla.org before Feb 27 2017 then I see no value in extending the SSL certificate.  Am I Missing something?
Flags: needinfo?(giorgos)
(In reply to Karen Ward [:kward] from comment #15)
> (In reply to Giorgos Logiotatidis [:giorgos] from comment #14)
> > Decommissioning of the website has begun. Two open questions:
> > 
> >  1. masterfirefoxos.com expires on 03-jun-2017. Do we let this expire or do
> > we renew? In the later case for how long?
> 
> {KW} I assume this relates to Mozilla's ownership of the URL.  Is that
> correct? If so I will check with Marketing to see if they believe there is
> value in Moz renewing the registration of the URL.

Yes, it's about owning the URL and also redirecting masterfirefoxos.com correctly to mozilla.org if Marketing sees value in that.


> 
> >     Currently www.masterfirefoxos.com redirects to
> > masterfirefoxos.mozilla.org
> > 
> >  2. SSL certificate of masterfirefoxos.mozilla.org expires on 27-feb-2017.
> > Do we let this expire or do we renew? In the later case for how long?
> 
> {KW} If we redirect the masterfirefoxos.com URL to mozilla.org before Feb 27
> 2017 then I see no value in extending the SSL certificate.  Am I Missing
> something?

This will be integrated in mozilla.org cert so we don't need to take any other action. For browsers that have visited masterfirefoxos.mozilla.org they have already cached the redirect to https://masterfirefoxos.mozilla.org and thus not renewing the cert will give them a cert error message. This would happen even now that we're decommissioning before Feb 27. WebOps managing mozilla.org cert offered to integrate this into this so problem solved.
Flags: needinfo?(giorgos)
Hi Porfirio.
  Our 'ownership' of the masterfirefoxOS.org URL expires in a few months.  Do you see any value in renewing it?  (We've retired the site and redirected it to mozilla.org.)
Flags: needinfo?(planderos)
Hi Porfirio.
  Our 'ownership' of the masterfirefoxOS.org URL expires in a few months.  Do you see any value in renewing it?  (We've retired the site and redirected it to mozilla.org.)
Hi Karen, any updates on this? I'd like to complete the decom this week.
Flags: needinfo?(kward)
(In reply to Karen Ward [:kward] from comment #17)
> Hi Porfirio.
>   Our 'ownership' of the masterfirefoxOS.org URL expires in a few months. 
> Do you see any value in renewing it?  (We've retired the site and redirected
> it to mozilla.org.)

Hi Porfirio please share your thoughts about whether Moz should retain the masterfirefoxOS.org URL.
Flags: needinfo?(kward)
(In reply to Karen Ward [:kward] from comment #20)
> (In reply to Karen Ward [:kward] from comment #17)
> > Hi Porfirio.
> >   Our 'ownership' of the masterfirefoxOS.org URL expires in a few months. 
> > Do you see any value in renewing it?  (We've retired the site and redirected
> > it to mozilla.org.)
> 
> Hi Porfirio please share your thoughts about whether Moz should retain the
> masterfirefoxOS.org URL.

Hi, I am updating this bug to say there is no need to renew the URL.  Ok to close this bug from my perspective.
ok! thanks for the update Karen.
Flags: needinfo?(planderos)
So long and thanks for all the fish mffos
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
See Also: → 1334055
See Also: → 1334398
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.