Talk:Year 2007 problem

From Wikipedia, the free encyclopedia

 The neutrality of this article is disputed.
Please see the discussion on the talk page.(December 2007)
Please do not remove this message until the dispute is resolved.

This article sounds like it was written by some bitter person. Furthermore, it's not "an error caused by a US mandate," it's more of "a significant programming and coordination effort caused by an US energy saving policy."

Contents

[edit] Migrate talk page

So if someone is going to rename Y2K7 to Year 2007 Problem, why not migrate the talk page? And to do this without talking about it? Where was there any discussion?--Smkolins 14:54, 10 March 2007 (UTC)

Why is Western Australia in the countries affected list? Australia is in the southern hemisphere, our summer has just ended, WA began their daylight savings in December. How does this relate to the US changing the dates for the beginning and end of daylight saving? Kingturkey 14:10, 12 March 2007 (UTC)

[edit] {{current}} tag

I think that the tag should stay until the article has been updated with information about what has actually happened. (Is there a more appropriate tag for that?) Jobarts-Talk 18:45, 15 March 2007 (UTC)

I think the {{expand}} tag is what your looking for. To me it looks like it needs info that will take quite some time to get like how much money was spent on this. Jon 18:29, 2 April 2007 (UTC)

[edit] "Daylight Savings Time Puts Kid in Jail for 12 Days"

This might be worth mentioning. http://yro.slashdot.org/article.pl?sid=07/04/17/1240237&from=rss 165.196.201.162 22:12, 17 April 2007 (UTC)

See Cody Webb. DES (talk) 12:45, 25 April 2007 (UTC)

cody webb is deleted, but i cant seam to find the story other than slashdot

Slashdot is hardly a reliable source. —Preceding unsigned comment added by 63.230.177.22 (talk) 16:59, 24 October 2007 (UTC)

even if it is true I don't really think it is important enough to include on the page. - SimonLyall 19:45, 24 October 2007 (UTC)

[edit] My Alarm Clock

Gerrrr! My alarm clock changes itself for day-light savings time but I bought it before the recent changes. Now it changes on its own at the incorrect time. It did it just yesterday. Now I have to reset it early, then change it when the real date comes. Double the opportunity for confusion or worse. What if I had to be at a meeting and my clock changed itself on its own? Daylight savings time is a bad idea for all the confusion is causes, but keeping it and changing the implementation days makes it even worse. I wish congress didn't do this. --Jon in California, 29 October 2007 —Preceding unsigned comment added by 208.127.73.9 (talk) 12:21, 29 October 2007 (UTC)

I'd sugest taking that up with your Congresman and Senators. Jon 13:21, 29 October 2007 (UTC)
Actually, though, the thing that's not included in this article but maybe should be is that "Jon in California"'s alarm - and indeed, all clocks with this issue - are one hour late both in March and October, which is counterintuitive. Anybody object to me making the explanation (with the mathematical reasoning) in the article? -- JCaesar 00:32, 6 November 2007 (UTC)
I object. I don't think the article should have too much practical stuff or specific problems with particular devices - SimonLyall 10:57, 9 November 2007 (UTC)