618095 - Domain Name Change - blog.mozilla.com to blog.mozilla.org

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Laura Forrest]

Please change the domain name of blog.mozilla.com to blog.mozilla.org.

This is part of the overall domain name strategy project driven by the website taskforce. 

Please have the .com redirect to the .org. 

More details here: 
https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy

Here's a link to the overall tracking bug for this project: 
https://bugzilla.mozilla.org/show_bug.cgi?id=606278

Comment 1

[Justin Fitzhugh]

why? we specifically chose to make this mozilla.com with mitchell's guidance given the blog is just for mozilla employees.  did this change?

Comment 2

[David Boswell]

Yes, our approach to using the mozilla.com domain on public sites has changed recently.  For reference, you can see the new domain name strategy at

https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy

In short, we no longer want to use organizational domains for our sites -- every public Mozilla site should use mozilla.org instead of mozilla.com or mozillamessaging.com.

Comment 3

[matthew zeier [:mrz]]

This is lower priority in context of everything else going on.  

* There's some Apache rewrite rules that will need to be worked out so existing blog entires work.  

* Renaming a WP blog is no walk in the park.  We did this one for Labs and it was some effort.

Comment 4

[Michael Coates [:mcoates] (acct no longer active)]

Bumping this up to critical. This bug is a blocker to remediation of another security issue.

Since this bug is open please see bug 669570 comment 18 and bug 669570 comment 23 to understand the importance of us making this transition in the immediate future.

Comment 5

[David Boswell]

(In reply to comment #4)
> Since this bug is open please see bug 669570 comment 18 and bug 669570
> comment 23 to understand the importance of us making this transition in the
> immediate future.

I don't believe there's any reason why we can't go ahead and make this switch now as long as all of the current .com URLs redirect to .org after the change.

Comment 6

[Michael Coates [:mcoates] (acct no longer active)]

MRZ, Oremj,

Can we resolve this bug this week? I'd like to address this issue and continue working on bug 669570

Comment 7

[matthew zeier [:mrz]]

I'll move it out of projects so it'll get picked up.

Comment 8

[Jeremy Orem [:oremj]]

When do you want me to make this change?

Comment 9

[Jeremy Orem [:oremj]]

ping ^

Comment 10

[David Boswell]

As mentioned in comment #5, I think it's fine to go ahead and change it whenever as long as all of the current blog.mozilla.com URLs redirect to blog.mozilla.org after the switch.  If you're looking for the go ahead from someone else, please let us know who to ask.

Comment 11

[David Boswell]

Note to Laura: after the switch we should check to make sure the blog.mozilla.org switch doesn't break anything with the newly working blog stats in WebTrends.

Comment 12

[Corey Shields [:cshields]]

Let's make the name change when we move this site from generic.sjc1 to generic.phx1

Comment 13

[David Boswell]

Based on the downtime note just sent around it sounds like this move from .com to .org is happening later.

Comment 14

[Jason Crowe [:jd]]

David,

The move is happening tonight during the datacenter migration.

Regards

Comment 15

[Jason Crowe [:jd]]

This is complete.  Redirects and CNAMEs are in place and worked when I tested.

Comment 16

[David Boswell]

I got the following error when trying to load https://blog.mozilla.com/about_mozilla/

This Connection is Untrusted

You have asked Aurora to connect
securely to blog.mozilla.com, but we can't confirm that your connection is secure.

Comment 17

[David Boswell]

(In reply to David Boswell from comment #16)
> I got the following error when trying to load
> https://blog.mozilla.com/about_mozilla/

I moved this into it's own bug so it can be tracked separately.  Please see bug 745883 for that.

Reclosing this bug.