From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 7FFCE123A for ; Fri, 18 Sep 2015 21:54:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1E8EF253 for ; Fri, 18 Sep 2015 21:54:17 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 3E3E31080196; Fri, 18 Sep 2015 21:50:07 +0000 (UTC) X-Hashcash: 1:25:150918:bitcoin-dev@lists.linuxfoundation.org::c90bW4NIsK1aTHld:Oem8 X-Hashcash: 1:25:150918:btcdrak@gmail.com::AXhb+albqVko7LAV:hEqA X-Hashcash: 1:25:150918:lf-lists@mattcorallo.com::uvQNgVUVb9rvPx03:R=pW X-Hashcash: 1:25:150918:pieter.wuille@gmail.com::GwH8RcRyCP7R48t3:gCo2Z X-Hashcash: 1:25:150918:cory@coryfields.com::zrJ4zXVDLl/1fj7T:bIIiG From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Btc Drak Date: Fri, 18 Sep 2015 21:50:04 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.6-gentoo; KDE/4.14.8; x86_64; ; ) References: <20150918010709.GB5251@amethyst.visucore.com> <55FC70A5.9080603@mattcorallo.com> In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201509182150.06275.luke@dashjr.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Cory Fields , Pieter Wuille 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 21:54:17 -0000 On Friday, September 18, 2015 8:24:50 PM Btc Drak via bitcoin-dev 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. Not everyone does crazy clock-changing. Using such a time system for scheduling seems to inconvenience the wrong position. (although perhaps arguably better since most people probably use DST) :p (Aside, if Google Calendar can't support standard UTC, that sounds like an argument against using Google Calendar...) > Urgh... Can we hardfork time? It's clearly in need of an upgrade... Tonal time works nice any consistently. :D Luke