Steps to reproduce:
- I made a meeting on a wiki in France (a-priori french times), starting at 9:30 AM
- I added some participants
- I sent an invitation mail to those participants, from the meeting application
- Some of those invitation mails ended up being read by the google mail client, which interprets the attached .ics invitation and displays it as a calendar event that the mail receiver can add to their google calendar
- the hour of the meeting in the display of google mail client was 11:30 AM
- I checked the .ics file attached and the date was sent as follows: DTSTART:20160715T093000Z
The ideal behaviour would be to send the proper timezone in the event, or the proper corresponding time in UTC time, so that whoever sees the event, from any timezone, they see the correct time of the meeting (as intepreted in the timezone of the wiki on which the meeting was created).
A less than ideal behaviour, but still an improvement to the current behaviour would be to send the hour of the meeting that is stored in the wiki but without any timezone indication (what they call a "local" time in the RFC), so that at least if the wiki and the receiver of the invitation are on the same timezone the time of the meeting displayed in the wiki and in the invitation mail are the same.
Steps to reproduce:
The ideal behaviour would be to send the proper timezone in the event, or the proper corresponding time in UTC time, so that whoever sees the event, from any timezone, they see the correct time of the meeting (as intepreted in the timezone of the wiki on which the meeting was created).
A less than ideal behaviour, but still an improvement to the current behaviour would be to send the hour of the meeting that is stored in the wiki but without any timezone indication (what they call a "local" time in the RFC), so that at least if the wiki and the receiver of the invitation are on the same timezone the time of the meeting displayed in the wiki and in the invitation mail are the same.