Maybe you should re-read the article yourself.. Even's google's own web page doesn't create events with no time-zone. Only Apple's IOS calendar does. Get your facts straight and stop being an apple fan boi!
Lol, ironic since there isn't any sort of issue as what you're describing. Something tells me you don't have a full grasp on the entire issue. It's written plain as day on Google's website. This is only evident on Calendar because of how Calendar handles time zones, but it's certainly not a bug. It's working exactly as Google and Apple intended for their respective services. If any change comes from this, it will be to revise the software to prevent confusion. That's all this is -- confusion. There is no bug, because it clearly states on Google's website this is expected. Quote from the Google link I posted, since it seems no one is actually reading it:
"Whenever you create an event, Calendar converts it from your time zone to UTC time, using currently known conversion rules. By using one universal time for all events, Calendar can keep all of your guests calendars consistent regardless of which time zones they're in. When we display the event on your calendar, it is converted from UTC to appear in your own time zone.
If you have a recurring meeting that spans across different time zones, then its time always remains constant for the organizer, and will shift for guests whenever their time difference with the organizer changes. Thats why if youre in London and attending a weekly meeting that was created by your New York colleagues at 10am NY time, it will always be at 10am for NY, almost always at 3pm for you, but at 2pm during that particular week in early November.
However, this process doesn't always work in cases where a country decides to change when they switch to DST or even their overall time zone. If you had created an event before we knew about the change, Calendar converted your time zone into UTC, using the information available at the time of creation. Once the time zone change is known, Calendar will use the new rule to display events in your time zone, and it might cause events to shift in your calendar.
Lets look once more into the Russian example. If you in March 2011 created an event for Nov 2011 at 17:00 MSK, then according to rules we knew in March, we would store it as 14:00 UTC. After the switch happened in Russia, Google Calendar takes the new rule and converts this event to 18:00 MSK. Luckily, all participants and rooms that you booked are still available for this meeting."
Edit for clarity, since I'm sure someone will reply with an angry counterpost calling me an ignorant fanboy; be sure to check out the screenshot. It shows the events in the appropriate time slot. The only part people are freaking out over is that it simply shows the GMT time zone. I'm not sure how this is confusing for people, but it's apparently SO confusing that people think it's a bug. If there is a bug that is REPLACING the time zone, then it's not the one described in this post by Macrumors. This post by Macrumors describes something that is expected behavior. When I reported this to Apple, the Apple engineers stated that it was expected. Google's own website states that it is expected. There is no counter-argument unless you're describing an unrelated issue than the one described in Macrumors' post. Simply because some folks in customer support said that it's an issue does not mean it actually is. I'm inclined to believe Apple's engineers and Google's webpage over a customer support employee. There is no issue here, at all.
