Closed Bug 622621 Opened 15 years ago Closed 14 years ago

Retire hendrix.mozilla.org

Categories

(Websites :: website-archive.mozilla.org, defect)

Product:
Websites
Component:
website-archive.mozilla.org
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: ryansnyder, Assigned: cmore)

References

Details

Attachments

(1 file)

Hendrix.mozilla.org screenshot
200.13 KB, image/png
Details
Per https://wiki.mozilla.org/Websites/Taskforce/Proposals/Abandoned_Sites#Sites_Discussed_in_2010 we may retired hendrix.mozilla.org. Website visitors will be redirected to input.mozilla.org. Retirement blog post is available at: http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html Will need an additional blog post on website-archive.mozilla.org with the screenshot.
For the record, the blog post on website-archive is already drafted, just not published yet.
Blocks: 621711
Thanks Fred. We will also need to file a ticket to have the Hendrix component removed from the Webtools product in Bugzilla.
Isn't this bug 621711? (In reply to comment #2) > We will also need to file a ticket to have the Hendrix component removed from > the Webtools product in Bugzilla. Er, I don't think so. Hendrix-the-software continues even if hendrix.mozilla.org has been shut down. Gerv
Thanks Gerv. In that case we will not remove it from Bugzilla. I assumed the Bugzilla component was tied to the site, not the software.
Before redirecting hendrix.mozilla.org traffic to input.mozilla.com we should make sure people will be able to post feedback. I had replaced the link to Hendrix with a link to input.mozilla.com on the mozilla.org contact page and have received three emails from people since then saying our feedback system was broken. AFAICT, there's no way to leave feedback from the main input page -- just view feedback already left by others. So I guess the options would be to add a 'leave feedback' button there or redirect people instead to http://input.mozilla.com/feedback. Aakash, do you have a preference here?
Now that our feedback pages are not tightly tied to the UI buttons in our betas anymore, I'd suggest we add a link to leave feedback somewhere on the front page. Though I'll refer to Aakash, who might have a good reason[TM] why we don't do that.
Assignee: nobody → chrismore.bugzilla
Status: NEW → ASSIGNED
Just to mention this, but the feedback system is accepting feedback regardless of what build you're on now.
Note of self: 301 dedirect both http://feedback.mozilla.org/ and http://hendrix.mozilla.org/ to http://input.mozilla.org. Currently, feedback.mozilla.org is redirected to hendrix.mozilla.org and there is no sense of doing two redirects in the future when hendrix.mozilla.org is redirected to input.mozilla.org.
Here is a screenshot of the website for the blog post.
Do we need to save any of the data collected thus far? Who owns or has access to the database? Does any of the data contain PII?
It'd be good to archive that information for mining purposes, but you'd have to create a script to parse and save all the posts in each newsgroup (they're all sent to google groups listings). The data sometimes contain PII, but these are all publicly accessible groups.
aakash: Do you see an issue with leaving Google groups alone and redirecting the website? What is the URL of the associated Google Groups that items get dumped in to?
I don't see an issue with leaving the Google groups alone. The URLs of the groups used to be on the developer-forums page, but I don't see them anymore. So, Gerv may be the best person that can get you that information.
cmore: All the data collected by Hendrix has been placed in one of the dedicated Mozilla discussion forums (mozilla.feedback.*), which are newsgroups, mailing lists and Google Groups. You don't need to save any data, but don't take any steps to delete any of it either. So yes, just redirect the website URLs. Gerv
Gerv: Thanks and will do!
I made a few edits to the retire blog post and published it at: http://blog.mozilla.com/website-archive/2011/05/16/hendrix/
Depends on: 657373
Filed 301 redirect bug with IT: https://bugzilla.mozilla.org/show_bug.cgi?id=657373
Redirects complete and blogs posted!
done
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Guys, this isn't right. dboswell's comment 5 still stands - people are going to give feedback and being directed to a page with no obvious place to give feedback. We need to change the redirect to http://input.mozilla.com/en-US/feedback Gerv
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Why not redirect to the blog post, and link to the feedback page from there? At least then people know why hendrix.m.o takes them somewhere that's not hendrix.
It makes more sense to link to input.mozilla.com/feedback as said in Gerv's comment. From a user flow perspective, they've already decided to give feedback. If we show them a page that doesn't allow for them to give feedback, then there's a higher likelihood that scrumptious morsel of user-generated opinion will not happen.
What Aakash said. There are a number of sites which link to Hendrix, and the traffic before the redirect was hundreds of comments per day. Which means at least hundreds of people per day are now being stymied. Can we make changing this redirect a priority? Gerv
Severity: normal → critical
All: I've reopened bug 657373 will the adjustment to the redirect. I will update everyone once the change is made. Changing redirect from input.mozilla.com to input.mozilla.com/feedback. Thanks, Chris
All: The redirectors have been adjusted to point to ./feedback. Thanks, Chris
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/ verified across feedback.mozilla.org and hendrix.mozilla.org (They both go to input.mozilla.com/feedback)
Status: RESOLVED → VERIFIED
Some supported users can no longer give feedback, so I am not sure Verified Fixed is correct (but I have not modified bug). True Hendrix is retired, but the redirects used are not satisfactory. If someone uses a none current version but supported version ie Firefox 3.6 they try to use Hendrix, that redirects to feedback.mozilla.org that advises them they need to upgrade and can not give feedback. Some users are for instance having memory related problems with Firefox 4 and reverted to on Firefox 3.6. Such users feel rather frustrated they are unable to give feedback. Presumably this is an intended consequence, and feedback relating to earlier versions is of no use to developers, but I am not sure it is a good policy, if it results in disgruntled users downgrading to an older but supported version only to find they now can not provide feedback without upgrading to a version that caused problems for them. Presumably no point in making a new bug proposing Firefox 3.6 users be given a feedback facility, as I guess official support will be withdrawn shortly. (I imagine Firefox 3.6 still has a large number of users).
I agree with John's feedback in comment #29. I've seen some people posting to the mozilla.org webmaster address who are pretty upset that they're not allowed to provide feedback. For instance, one person was trying to use Firefox 4 but it wasn't working for her, but she wasn't allowed to submit feedback about this since since wasn't using Firefox 4.
Firstly thanks for the feedback, John. If you're having problems or issues related to a release build of Firefox, it's important that you go through SUMO (support.mozilla.com) and submit a new thread (or possibly find the article related to it). The Input application is intended to be a one-way form of communication that helps us conflate similar comments into large-scale insights. Users are able to give feedback in the form of Input, Bugzilla and Support. If that's not enough, please mention another channel that might better suit the type of feedback you can't send in through those 3 channels.
Thanks for the reply Aakash. I am not having problems. I am noticing others are and there is no facility to provide feedback in some cases. I would have hoped at the very least attempting to provide feedback would result in a sensible suggestion about how to do that other than an instruction to upgrade. I have mentioned this on SUMO, resulting in a comment from Michael Verdi SUMO content manager >Ah! I'm just emailed the input team to find out what the plans are for 3.6 >and the now "old" fx 4. > https://support.mozilla.com/en-US/forums/contributors/707021#post-40416
I think John has a great suggestion in comment #32 -- the page people see when they're not using the latest version should point people to the other feedback channels that Aakash mentions in comment #31 instead of just linking to the download page. Otherwise we're just frustrating people for no reason. For instance, see this comment about this issue I just received this morning on the mozilla.org webmaster address: "Your web site refuses to allow me to leave feedback about Firefox unless I upgrade to the latest version but this is the very issue about which I wish to comment. Please have the objectivity and courtesy to read my comments or to pass them to the appropriate department" I imagine the discussion should probably be moved at this point to a new input bug for this change on that page. John, feel free to file that?
I just filed bug 666673 to improve the message on the Input site people see to clarify the issue of where else to provide feedback.
David thanks for filing the new bug, but it has not resolved the matter. bug 6666673 comment 2 is closed as a duplicate of bug 629953 Bug 629953 "Make input download pages more informative" appears to have ceased to be active, with the intention of adding a link to the channels page: >(cmt #4) > Chris, can we add a hyperlink and some text, or even a graphical snippet, that > directs users to the firefox/channels page instead? > (cmt#9) > Doing a quick checkin. This was fixed shortly after comment #6, but I only landed the changes on GitHub: That does not resolve the issue of users of older versions, ie the still supported Fx3.6 being unable to use the input form.
(In reply to comment #35) > David thanks for filing the new bug, but it has not resolved the matter. > bug 6666673 comment 2 is closed as a duplicate of bug 629953 John, it may be best to move the discussion to bug 629953? Not sure how many people are tracking this fixed bug or the other bug that was marked as a dupe.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: