rich1.0npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7edhttps://nostr.ae/npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7ednjumphttps://nostr.ae📅 Original date posted:2015-09-18 📝 Original message:Google calendar is localised, so it doesn't matter. The problem with quoting UTC anyway it the meeting times are going to change for those that observe DST. It would be much better to quote an actual timezone of an actual area so it will remain constant, like 1700 CEST, or 0900AM PDT for example. Otherwise when the clocks change, what was a convenient meeting time will become inconvenient for some. On Fri, Sep 18, 2015 at 9:14 PM, Matt Corallo via bitcoin-dev < bitcoin-dev at lists.linuxfoundation.org> wrote: > Generally in favor, but for practical purposes can we select a timezone > that is available in Google Calendar? It appears it does not directly > support UTC... > > On 09/18/15 01:07, Wladimir J. van der Laan via bitcoin-dev wrote: > > Hello, > > > > At Monday's code sprint we had a good idea to schedule a regular > developer meeting in #bitcoin-dev. > > > > Attendance is of course voluntary, but it may be good to have a time > that many people are expected to be present and current issues can be > discussed. > > > > Any preference for days/times? > > > > What about e.g. every week 15:00-16:00 UTC on Thursday? > > > > Wladimir > > _______________________________________________ > > bitcoin-dev mailing list > > bitcoin-dev at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150918/c4455a41/attachment.html>