Re: [board-discuss] new BoD call time due to daylight saving time
Hi, Norbert Thiebaud wrote on 2013-03-30 18:09: www.google.com CET enter I have given up on that for certain things. ;-) Well, the issue here is that UTC, of course, does not have that funky 'daylight-saving' thing... so if you pick UTC then you will have to ask for a vote like this 2twice a year for the foreseable future... Note: you can announce the time in UTC but still have an agreement that the time is _based_ on a CET time... so that you won;t have to do a vote for a 'change' twice a year. As we need to have approved the formal voting for the new time until Wednesday's call, and given it's Easter holidays - how about I simply afterwards make another formal vote, that includes both times, like from Nov to Mar it's 1600 UTC and from Mar to Nov it's 1500 UTC? That way, we keep UTC, but avoid voting every 6 months. Florian
Re: [board-discuss] new BoD call time due to daylight saving time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Em 29-03-2013 14:09, Norbert Thiebaud escreveu: may I suggest, to avoid that twice-yearly dance, to set the time based on CET once and for all.. rather than UTC with 2 adjustment a yer when CET switch in and out of DST. Norbert IIRC, the planet has 2 hemispheres divided by the equator. I know when I have my DST settings, but I almost never know when are the European DST settings. So either I am -3 hours CET or -5 hours CET with some weeks at -4 hours CET twice a year. UTC is very handy, believe me. Happy Easter - -- Olivier Hallot Founder, Board of Directors Member - The Document Foundation The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany Fundação responsável civilmente, de acordo com o direito civil Detalhes Legais: http://www.documentfoundation.org/imprint LibreOffice translation leader for Brazilian Portuguese +55-21-8822-8812 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJRWDUIAAoJEJp3R7nH3vLxGhcH/iu+jj9YLI7Udi5cjGt/A7Dn bV6btFmWBhaySsc5LBvNKZIbtWo8wT1z8ThCQDr4ImQanN7EkFxV9QNFhvMI+tk7 f7IOlNm+pdNvd45cdHRjwWOkcQFfvhNA7oiOY6s5vj9XCHu14s5U+80kZJruK5mq ny3n/Qb/9MEsYWL+/WhL5HLuZqr8IZj2THQRbVSPV3XkFqIajdTcuHrQa/HnWx75 mkHhM3/YUwz0sIUFZ65Jk8e+ydF9iRJtkOhwrTs7X3b4yHmIdGGdQBYeCE1nZNFG 1WfcKWMQ+Ajn6jc2oqxV84oJjNcej5dAlj7724LmWOiXiIy12ihRIVp5t8YEGAE= =pjXg -END PGP SIGNATURE-
Re: [board-discuss] new BoD call time due to daylight saving time
On Sun, Mar 31, 2013 at 8:07 AM, Olivier Hallot olivier.hal...@documentfoundation.org wrote: UTC is very handy, believe me. Sure I find the whole DST mess stupid to start with... but... _practically_ the meeting time is adjusted so that it always occurs at the same CET time. so the announce could be made using UTC for convenience, but in fact that UTC time has changed and will change according to the DST setting of CET... so instead of figuring out how many hours behind 3,4,5 you are from CET, you have to pay attention to the specific UTC time of the meeting, which will vary up to 2 hours depending on the specific date of the meeting. Note: 1/ I re-iterate that the reference time can be a certain CET time, and yet the announce can contain UTC time for convenience 2/ And the end of the day that was just a suggestion... that I made because we were running into the same problem with ESC meeting... I have no strong feeling about it... especially for a meeting that I rarely attend to start with :-) Norbert
