Closed Bug 618157 Opened 15 years ago Closed 13 years ago

Domain Name Change - input.mozilla.com to input.mozilla.org

Categories

(Input Graveyard :: Backend, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lforrest, Unassigned)

References

(Blocks 2 open bugs, )

Details

(Whiteboard: [cname only, app fixes?][post fx4])

Please change the domain name of input.mozilla.com to input.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
Pretty sure you didn't want to assign this to Mozilla Messaging server ops.
Assignee: server-ops → server-ops
Stupid question: what happens when a user types in input.mozilla.com ?
(In reply to comment #2) > Stupid question: what happens when a user types in input.mozilla.com ? "Please have the .com redirect to the .org."
right..
Component: other.mozilla.org → Input
Product: Websites → Webtools
QA Contact: other-mozilla-org → input
Version: unspecified → Trunk
Assignee: server-ops → fwenzel
Assignee: fwenzel → server-ops
On the app's side, the Sites data (django admin site -> Sites) needs to be changed when this happens. We also need to ensure that our Zeus settings will be applied to the new domain.
Component: Input → Server Operations
Product: Webtools → mozilla.org
QA Contact: input → mrz
Version: Trunk → other
No redirect. CNAME only. input.mozilla.com is an in-product URL and I haven't seen any plans to backport this name change or replace it in future versions of Firefox.
Severity: normal → enhancement
Whiteboard: [cname only, app fixes?]
Blocks: 618189
Assignee: server-ops → nobody
Component: Server Operations → Server Operations: Projects
Whiteboard: [cname only, app fixes?] → [cname only, app fixes?][post fx4]
Now that Firefox 4 is out and we're starting to move public sites from mozilla.com to mozilla.org again (see bug 606326 for the air.mozilla.org change two weeks ago) can we talk about scheduling a switch from input.mozilla.com to input.mozilla.org?
This looks like it's not ready for IT to act on it yet. Over to Input for the product decision and triage. Assigning to Aakash. The Input devs can push this back to IT with concrete instructions later.
Assignee: nobody → mozaakash
Component: Server Operations: Projects → Backend
Product: mozilla.org → Input
QA Contact: mrz → backend
Version: other → unspecified
We'll need to file a bug to patch the in-product URLs as a long-term solution for that part of this bug. Once that bug is fixed and pushed onto into a release of Firefox (about 2 quarter time frame if we do it now). Otherwise, *thumbs up*
Aakash, should we start the IT process now then? They can set it up so everything redirects to .org. Then when the product changes everyone is spared a redirect, but effectively nothing changes on the UX end.
Fine with me as long as it won't take up more than 5-10 minutes of your time; otherwise, I'd prefer to wait for this after the 4.2 code freeze :).
Depends on: 664176
Target Milestone: --- → 4.x
Ok, we have the patch ready to go for Firefox in bug 618189. Gavin would like to have the necessary changes to be made soon after the change is put into nightlies, so we can make sure this is working. Fred, Dave or Chrie: can you follow up with IT?
Dave, can you take a look? Also keep in mind that the app uses the Django Sites framework to distinguish between the mobile and desktop site, so that'd need to change via the admin interface.
Yes, Aakashd, what's the ETA for this to land in release? I'll set a target date with IT for then. Also will look at the sites framework stuff as well.
Can we stagger it a bit and do it earlier like in the next few weeks, Dave? It'd be good to test this on Nightlies for Fx10 rather than later. If we find issues later in the aurora or beta process, the required changes on the Fx side will require updates to multiple channels. If it's Nightlies, we can set up a time in the next 2-3 weeks.
Sounds good; Gavin, davedash can work this in on Nov. 1st. The merge from Nightly to Aurora seems to be on 11/8, so we can land whenever.
It looks like the 3-4 bugs we have on file are ready to go here. Anyone want to mention any blockers still left?
Un-assigning myself. Waiting on bug 664176 at this point.
Assignee: mozaakash → nobody
This is now complete.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Not sure this caused bug 747316, but it's definitely fallout, likely from the app side?
Depends on: 747316
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.