606278 - Tracking bug for implementing new domain name strategy

Status: NEW

(Websites :: Other, defect)

Description

[David Boswell]

The websites task force just approved a new domain name strategy for Mozilla sites.  I'm opening this bug to track progress on implementing changes coming from this new strategy.  Changes to specific sites will be addressed in separate bugs linked to this bug.

The short version of the strategy is that sites should follow this model for their URLs:

* service.mozilla.org/sub-category (with some exceptions such as for campaign or local sites)

The full strategy can be found at:

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

One example of a change from this is that Air Mozilla should live at air.mozilla.org instead of air.mozilla.com.

BTW, I wasn't sure where to file this bug -- these changes will be relevant for webdev, IT and security from a technical standpoint and a range of other groups as well.  Feel free to suggest better places for this.

Comment 1

[Axel Hecht [:Pike]]

FYI, input.mozilla.com has URLs to it coded into the fx4 products, both desktop and mobile.

Comment 2

[David Boswell]

Axel, thanks for pointing that out.  We definitely want to be careful with the sites that are linked from the product to make sure the switch goes smoothly.

Comment 3

[Les Orchard [:lorchard]]

(In reply to comment #1)
> FYI, input.mozilla.com has URLs to it coded into the fx4 products, both desktop
> and mobile.

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much that it's coded into Fx4, but that the domain name is part of the configuration distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are linked to by other sites and coded into products / configurations in the wild (ie. outside our control). Cleanly moving things may not be possible in all cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only with a 301 redirect at the legacy URL. However, some URLs may not be amenable to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where old/new URLs need to co-exist for an extended period of time. I can't think of any off the top of my head, though

Comment 4

[David Boswell]

Re comment #3, good point about the domain name strategy not being very clear on the issue of sites that are linked to from the product.  I copied that comment and added it to the wiki page.  Please feel free to add or edit anything there to provide further clarification.

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

I had expected that we'd learn a lot as we started going through this process, so we'll keep the wiki up to date with this sort of lessons learned information.

Comment 5

[mcbmoz]

reassigning to david, not sure how to help here.