Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5DE0D16D6 for ; Fri, 18 Sep 2015 20:27:07 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.bluematt.me (mail.bluematt.me [192.241.179.72]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D05E9150 for ; Fri, 18 Sep 2015 20:27:06 +0000 (UTC) Received: from [172.17.0.1] (gw.vpn.bluematt.me [162.243.132.6]) by mail.bluematt.me (Postfix) with ESMTPSA id 0BC55584E7; Fri, 18 Sep 2015 20:27:02 +0000 (UTC) To: Btc Drak References: <20150918010709.GB5251@amethyst.visucore.com> <55FC70A5.9080603@mattcorallo.com> From: Matt Corallo Message-ID: <55FC7394.4060901@mattcorallo.com> Date: Fri, 18 Sep 2015 20:27:00 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin development mailing list , Pieter Wuille , Cory Fields Subject: Re: [bitcoin-dev] Weekly development meetings on IRC X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 20:27:07 -0000 Google Calendar is localized, but has an option to change the timezone of an event, it just doesnt have UTC in its options. So, yes, we should use something that observes DST in roughly the same way as everyone else - CEST/PDT/EST/etc. On 09/18/15 20:24, Btc Drak wrote: > 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 > > 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@lists.linuxfoundation.org > > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > >