Closed Bug 580334 Opened 15 years ago Closed 15 years ago

Please re-direct the following URLs to input.mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: aakashd, Assigned: fox2mike)

Details

We're getting some requests for re-directs to input.mozilla.com. Can we get the following URLs to red-irect to http://input.mozilla.com/ ? - http://input.mozilla.org/ - http://feedback.mozilla.org/ - https://feedback.mozilla.org/ - http://feedback.mozilla.com/ - https://feedback.mozilla.com/ One caveat: Seamonkey is linking to feedback.mozilla.org instead of hendrix.mozilla.org. They need to change the "feedback form" link to hendrix.mozilla.org. (i.e. http://www.seamonkey-project.org/releases/seamonkey2.1a2/ ) Of the rest of the projects listed on Hendrix (Thunderbird, Camino and Sunbird) all seem to be linking elsewhere. Robert, can we get this fixed on the Seamonkey end?
input.firefox.com as well as feedback.firefox.com
Whoa, there. Lots of places use the feedback.mozilla.org alias for Hendrix - not just SeaMonkey. That's why, when Aakash asked me if he could use it a while back, I said no. And that is (I assume) why Input launched as input.mozilla.*, not feedback.mozilla.*. You can't pinch feedback.mozilla.*, I'm sorry. OTOH, having input.mozilla.org go there is entirely right and proper. Gerv
Using Hendrix anywhere is probably not the best idea nowadays anyhow, but is input up to serving non-Firefox products? In any case, where is SeaMonkey referencing feedback.m.o? On the relnote pages, I just might have copied those from some Firefox relnote and that's easy to change if I know what to change it to.
Decide on what the final call on this is? Looks like touching feedback* is bad idea, but input* is okay.
08:31:38 < fox2mike> aakashd: so If I leave out feedback*, you'd like input.mozilla.org and input.firefox.com to go to input.mozilla.com? 08:31:46 < fox2mike> and you'd be happy? 08:32:55 < aakashd> yes
Assignee: server-ops → shyam
I can see why we'd want input.mozilla.org, because we are trying to make mozilla.org and mozilla.com match, but why input.firefox.com? CCing david, who is masterminding our strategy in this area. Gerv
Because we think it's something people might type, and so we'd like to not leave those people at a 404. I don't think comment 6 should stop the excellent forward-motion of comment 5!
I don't want to be Mr Stop Energy, but there are at least two good reasons why input.firefox.com is a bad idea: - Input may one day support products other than Firefox, at which point it becomes confusing - choice paralysis (if users know about it) or irrelevance (if they don't) Ideally, every website has one, well-known domain. (Hendrix is not good in this respect.) Given what we are trying to do with One Mozilla, making *.mozilla.com do the same thing as *.mozilla.org in as many cases as possible is good (given where we are starting from). But why do we want to spread that unfortunateness to firefox.com? Gerv
input.mozilla.org and input.firefox.com redirect to input.mozilla.com for now. If you really have issues, reopen and I'll look at it when I wake up :)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #8) > I don't want to be Mr Stop Energy Great, thanks! (we can eventually redirect input.whateverthehellyouwant.com to the appropriate subsection of input; these problems are soluble, and should not stop us from supporting the people who are trying to give us feedback on our lead product.)
But input.whatever.whatever doesn't allow people to "give us feedback" - it only displays feedback given. (Unless I've missed a "Submit feedback" link somewhere.) And why would people go to "input.firefox.com" to give feedback (or read it) unless someone told them to? And no-one would tell them to if we didn't make it work. They would tell them to go to one of the other two working URLs instead. I can't imagine "input.firefox.com" as something people would just invent and speculatively type into their web browser. If we are going down that route, how about talktous.firefox.com? Or support.firefox.com (which doesn't currently work)? Or comments.firefox.com? <shrug> Gerv
Since this project is called Firefox Input, I naturally type in input.firefox.com... and then I get 404'd... and then I click on "feedback" and say "Firefox made me sad because I don't know where anything is."
To alleviate this, we could simply offer the input.mozilla.com/happy and input.mozilla.com/sad links as a way to offer feedback to us. We're currently UA sniffing and suggesting for people to download the latest beta if they're not on it. Obviously this is not the same as hendrix which allows people to offer feedback no matter what build of Firefox they're on. So, if it's possible to offer the happy/sad forms on places that are meant for firefox betas (for now) and incorporate Input when its on Fx Proper (the method is not finalized yet, so don't ask how it's going to work there), I'd go with that route. At least, that's the sanest way I can think of doing this. What do you think, Gerv?
Aakash: I'm not entirely following what you are proposing. But should we take this to the mozilla.tools group? Gerv
I'll re-send a more cohesive message to the tools group a little later in the day.
FWIW, since the site is called Firefox Input it sounds like input.firefox.com makes sense. Earlier comments in this bug though have pointed out that the way we use different domains often doesn't make much sense (one of my favorite examples is that we have two different sites at survey.mozilla.com and surveys.mozilla.org and survey.mozilla.org and surveys.mozilla.com both give 404 errors). If having a coherent domain name strategy is something you are interested in, consider taking part in the websites task force. More information about the task force in general and plans for the initial meeting on August 12 are at http://davidwboswell.wordpress.com/2010/07/14/a-mozilla-websites-taskforce/
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.