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 529451584 for ; Fri, 18 Sep 2015 20:25:12 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 93763FB for ; Fri, 18 Sep 2015 20:25:11 +0000 (UTC) Received: by wiclk2 with SMTP id lk2so44521287wic.1 for ; Fri, 18 Sep 2015 13:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HDmwv1LXwb2mRj2RgvrFb/YhxWyvMB/dwTiolZxjzgE=; b=FGebDDn0/f4q0FYkEZvCqEFwChhZXCLOB8TOwPpYGMEowmorW1qmSTNKySy50gIV+O JZVlX0JIrLjPbwVlv4UAwTQ8DqmrCJeKkuOsGNWtfB7UeDWX1sLkbxZTzDEfk78PjWsA QxaJ1Mbapl7yzNcV+om6dvC5t40zU4+E2OSTMAcOrlcq/saDOLAS0gsJu+XsIAP8kabB Hm7XfGXctCJHOA9g+r0fjj/jjLjlgRpoeldcnNg5uR4E8iu9HBgvkY3ZshAxjFb6253z cX1DqeQtWwLkC8bRPDxnw4q3aIOdw1X8+Ou1c3KSRORMLdJecGTWbz6c/pjwwk85HNAc N3iw== X-Received: by 10.180.79.34 with SMTP id g2mr160185wix.28.1442607910334; Fri, 18 Sep 2015 13:25:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.21.200 with HTTP; Fri, 18 Sep 2015 13:24:50 -0700 (PDT) In-Reply-To: <55FC70A5.9080603@mattcorallo.com> References: <20150918010709.GB5251@amethyst.visucore.com> <55FC70A5.9080603@mattcorallo.com> From: Btc Drak Date: Fri, 18 Sep 2015 21:24:50 +0100 Message-ID: To: Matt Corallo Content-Type: multipart/alternative; boundary=f46d041825d80bb4d605200b547b X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM, HK_RANDOM_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no 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:25:12 -0000 --f46d041825d80bb4d605200b547b Content-Type: text/plain; charset=UTF-8 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@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@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 > --f46d041825d80bb4d605200b547b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Google calendar is localised, so it doesn't matter. Th= e 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 time= zone of an actual area so it will remain constant, like 1700 CEST, or 0900A= M 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 C= orallo via bitcoin-dev <bitcoin-dev@lists.linuxfoundat= ion.org> wrote:
Generally i= n 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 d= eveloper meeting in #bitcoin-dev.
>
> Attendance is of course voluntary, but it may be good to have a time t= hat many people are expected to be present and current issues can be discus= sed.
>
> 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@l= ists.linuxfoundation.org
> https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
>
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev

--f46d041825d80bb4d605200b547b--