Dave said: "our Page Editor is not compatible with the recently released Firefox 4."
Isn't the Page Editor an internal utility that no outside user will ever see?
If K1ZZ's message is only to those editing pages on the website, I don't see any problem with it.  Of course, in the long run it should be fixed, too, but it is likely not urgent in this circumstance.

--
73,
        Greg, KØGW
        Director, Dakota Division

----- Original Message -----
From: "JRS" <jrs@hamradio.us.com>
To: arrl-odv@reflector.arrl.org
Sent: Monday, March 28, 2011 10:36:48 AM
Subject: [arrl-odv:19811] Re: Website update

Ladies and Gentlemen:

    the solution for now is “Don’t upgrade to Firefox 4.” ?????????????????????!!!!!!!!!!!!!!!!!!!!!!!!

With all due respect - Surely, we jest.

Firefox 4 was released on 3/22/11 - over 7 MILLION copies were download in the first 24 hours. Compare that to IE9's download rate for the first 24 hours of only 2.35 million. As of this morning, over 38 million people have upgraded/downloaded Firefox 4 - and that number is steadily increasing. Go to: http://glow.mozilla.org/ to watch.

Internet Explorer's market share is declining and that of alternative browsers is increasing and Firefox holds the lion's share of the alternative browser market.

And the national association of Amateur Radio's response to its members is: Don't upgrade?

That "let them eat cake" response unfortunately exacerbates the ARRL's reputation amongst too many Hams as being out-of-touch and behind the times. Initial incompatibility is not a major embarrassment - it probably could have been caught before FF4 went live, but sometimes things are overlooked. I am certain the ARRL is not the only website with some issues, but no other major organization is relegating that incompatibility to the "whenever, whatever" bin.

Again, with all due respect, if the "Don't upgrade ... " comment was not intended to be humor, FF4 non-compatibility should not be a back burner issue; it should be moved up to a priority and the issue noted on the website as one of which the staff is aware, but is in the process of fixing. Acknowledging the incompatibility, but noting our esteemed staff has recognized it and is at work on a fix would be viewed favorably by the members. No one has a real problem with a "it is broke, but we are going to fix it" response.  "Don't upgrade" will not be viewed favorably.



On 3/25/11 3:25 PM, Sumner, Dave, K1ZZ wrote:

I have been asked to provide an update on the status of the website transition.

As I reported on February 14, the website is now running on its new hardware configuration at Rackspace. Proxy errors are no longer a significant issue, although one still might occur occasionally if a request involves a large amount of data and there is a timeout.

You may recall that late last year we contracted with Fathom for two enhancements, an audio RSS feed and a report generator. The audio RSS feed went live in early January, as previously reported, and yesterday the report generator did the same. So, those two projects are now completed.

The report generator resolves one of the major issues that SMs had, namely the downloading of their appointee data.

The only remaining work Fathom is doing for us is under the original agreement. Other than those related to forums, only four open tickets assigned to Fathom remain on the bugzilla list; everything else assigned to them has been cleared.

With regard to forums, I have not been pressing staff to complete this project because of what appeared to be a consensus that we should not launch any major new features as long as there was a perception that major problems were not yet resolved. We are now much closer to being past that. However, don’t expect dramatic or immediate progress on forums because of the time being devoted to the plan for electronic publishing of periodicals, as per Minute 41 of the January Board meeting.

Bugzilla is used to record desirable enhancements as they are identified as well as problems to be fixed. Other than enhancements, there are currently 20 open tickets assigned to ARRL staff. Most new tickets are resolved soon after being opened, although some will require more work. For example, today a new ticket was opened when we discovered that our Page Editor is not compatible with the recently released Firefox 4. This is not an immediate problem – the solution for now is “Don’t upgrade to Firefox 4.”

73,

Dave Sumner, K1ZZ

_______________________________________________
arrl-odv mailing list
arrl-odv@reflector.arrl.org
http://reflector.arrl.org/mailman/listinfo/arrl-odv

_______________________________________________
arrl-odv mailing list
arrl-odv@reflector.arrl.org
http://reflector.arrl.org/mailman/listinfo/arrl-odv