Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C51491B78 for ; Wed, 23 Sep 2015 14:06:21 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 21801159 for ; Wed, 23 Sep 2015 14:06:21 +0000 (UTC) Received: by ioiz6 with SMTP id z6so44536336ioi.2 for ; Wed, 23 Sep 2015 07:06:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=procabiak.com; s=procabiakindustries; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3vQ6TOXuD2Lg/5mZcdgKJPn7Njq3uP16oJQmkHtrGlA=; b=QWv66RpXvr6RbjxvWLHAWpqNSNOssyJi3nxzPj3RvG26VsibGOTZnU9lz9iHSSOn6R n75ydnnUX2fW5xzk22hqJESglQMAXfDQdelkGD9DFRbLbdtq9Y+EaIVrfMhct9VrUrq3 hEx924lE6DH6unesXnhRraBjGU3/l9DTx3ETw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3vQ6TOXuD2Lg/5mZcdgKJPn7Njq3uP16oJQmkHtrGlA=; b=C95aUsW4uOiZekvdjFL2HO4Vb7WOBnH5/9rTOHENA1N6ZaPLvMVN6sXcjvfvrKS13+ yaJNnA5TKY6WJtwGt5QqLW+j5bST3f445geH4jFLhLPsr3C2QyC/vm0y+djKW8vEQiyL Bw8qv1+Lz6IqmRTn2sI+YvW/Y8tItMe/AdUGuUzdwC7hbs624msIVHm4RENQwnUMgboU UlKA232suPSXcCD/VsaYJH0P+jq54KnwoRaSGt0oEXP/vcOk6TjVzGOYtVSHxUNitoaZ I8IwlJkOHsahshurfbWPE/NBE6KmyVcTPxv9mUZX5ZjM+6Pstc9wdpvVyMFeXlTfXBss xUnA== X-Gm-Message-State: ALoCoQlUG91V/39ljszG+uUdzaBZ5p7medlpxSJ1/FaH9dBX1RBu/oUgRAUq3NbBAmfA40v4k1tr MIME-Version: 1.0 X-Received: by 10.107.6.74 with SMTP id 71mr38586905iog.16.1443017180529; Wed, 23 Sep 2015 07:06:20 -0700 (PDT) Received: by 10.36.68.213 with HTTP; Wed, 23 Sep 2015 07:06:20 -0700 (PDT) X-Originating-IP: [14.202.127.219] Received: by 10.36.68.213 with HTTP; Wed, 23 Sep 2015 07:06:20 -0700 (PDT) In-Reply-To: References: <20150922143628.GB958@amethyst.visucore.com> Date: Thu, 24 Sep 2015 00:06:20 +1000 Message-ID: From: Vincent Truong To: jl2012@xbt.hk Content-Type: multipart/alternative; boundary=001a113deb3873611605206a9e6c X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Weekly development meetings on IRC: schedule 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: Wed, 23 Sep 2015 14:06:21 -0000 --001a113deb3873611605206a9e6c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable All, Current meeting time visualised globally. http://everytimezone.com/#2015-9-24,420,4ia jl, I think I found a good compromise: if the US want to accommodate Asia and willing to sacrifice preference, 23:00 to 00:00 UTC might work. http://everytimezone.com/#2015-9-24,660,4ia It isn't easy to grab everyone's preference and accommodate everyone, so this might work in theory but people may not be free to show up. US should be ok. UK can participate or catch some nice z. Asia will need a bit of early bird time but it's not as crazy as 3am. AU also fits in there nicely. A meeting like this once a month should be enough probably (say, do this on the first week of the month, and run every other week on the main schedule). But I don't know whether there are enough people in Asia/AU to make it worth it. Asia/AU people, thoughts? On Sep 23, 2015 9:01 PM, "jl2012 via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: > There could not be a worse timing than this for those in China (3-4am), > Japan/Korea (4-5am), and Australia (3-6am depends on which part of the > country). Maybe we have no dev in this part of the planet? Is there any > chance to review the timing in a weekly or monthly basis (also with a > doodle vote?) > > Will there be any agenda published before the meetings? If I'm really > interested in the topics, I'll have some reasons to get up in the middle = of > the night. > > Wladimir J. van der Laan via bitcoin-dev =E6=96=BC 2015-09-22 10:36 =E5= =AF=AB=E5=88=B0: > >> Hello, >> >> There was overwhelming response that weekly IRC meetings are a good thin= g. >> >> Thanks to the doodle site we were able to select a time slot that >> everyone (that voted) is available: >> >> Thursday 19:00-20:00 UTC, every week, starting September 24 (next >> Thursday) >> >> I created a shared Google Calendar here: >> >> https://www.google.com/calendar/embed?src=3DMTFwcXZkZ3BkOTlubGliZjliYTg2= MXZ1OHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ >> >> The timezone of this calendar is Reykyavik (Iceland) which is UTC+0. >> However, you can use the button on the lower right to add the calendar >> to your own calendar, which will then show the meeting in your own >> timezone. >> >> See you then, >> >> 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 > --001a113deb3873611605206a9e6c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

All,

Current meeting time visualised globally.

http= ://everytimezone.com/#2015-9-24,420,4ia

jl,

I think I found a good compromise: if the US want to accommo= date Asia and willing to sacrifice preference, 23:00 to 00:00 UTC might wor= k.

http= ://everytimezone.com/#2015-9-24,660,4ia

It isn't easy to grab everyone's preference and acco= mmodate everyone, so this might work in theory but people may not be free t= o show up. US should be ok. UK can participate or catch some nice z. Asia w= ill need a bit of early bird time but it's not as crazy as 3am. AU also= fits in there nicely.

A meeting like this once a month should be enough probably (= say, do this on the first week of the month, and run every other week on th= e main schedule). But I don't know whether there are enough people in A= sia/AU to make it worth it. Asia/AU people, thoughts?

On Sep 23, 2015 9:01 PM, "jl2012 via bitcoi= n-dev" <bi= tcoin-dev@lists.linuxfoundation.org> wrote:
=
There could not be a worse timing than this = for those in China (3-4am), Japan/Korea (4-5am), and Australia (3-6am depen= ds on which part of the country). Maybe we have no dev in this part of the = planet? Is there any chance to review the timing in a weekly or monthly bas= is (also with a doodle vote?)

Will there be any agenda published before the meetings? If I'm really i= nterested in the topics, I'll have some reasons to get up in the middle= of the night.

Wladimir J. van der Laan via bitcoin-dev =E6=96=BC 2015-09-22 10:36 =E5=AF= =AB=E5=88=B0:
Hello,

There was overwhelming response that weekly IRC meetings are a good thing.<= br>
Thanks to the doodle site we were able to select a time slot that
everyone (that voted) is available:

=C2=A0 =C2=A0 Thursday 19:00-20:00 UTC, every week, starting September 24 (= next Thursday)

I created a shared Google Calendar here:
https://www.google.com/calendar/embed?src=3DMTFwcXZkZ3BkOTlub= GliZjliYTg2MXZ1OHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

The timezone of this calendar is Reykyavik (Iceland) which is UTC+0.
However, you can use the button on the lower right to add the calendar
to your own calendar, which will then show the meeting in your own
timezone.

See you then,

Wladimir

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--001a113deb3873611605206a9e6c--