Timezone / recurrence scheduling discussion for Kolab

Georg C. F. Greve greve at kolabsys.com
Wed Nov 3 10:12:05 CET 2010

Hi David, John, Sergio,

Tobias told me you're the people to contact about time zone issues.

Background is that several people identified a gap in Kolab's handling of 
recurring events when multiple time zones are involved, and we're wondering 
how to resolve this. An explanation of the issue can be found here:


For simplicity, I've come to refer to this as "the 'sticky' time zone issue" 
and here is a short summary of proposed solutions:


The people who work on native Kolab support for Evolution have proposed (and 
begun to implement) the following approach:


But naturally this forks the format, and will break compatibility with all 
other clients, which is not a satisfactory outcome.

So we should find a good way to approach this issue.

The question to you is: From your experience, which would be the most sensible 
approach, and would disrupt Kontact the least, with the least disruption of 
backward compatibility?

Your input would really be appreciated.

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20101103/9d05c434/attachment.sig>

More information about the format mailing list