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 6554A1439 for ; Thu, 24 Sep 2015 15:33:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8F0D4253 for ; Thu, 24 Sep 2015 15:33:07 +0000 (UTC) Received: by iofh134 with SMTP id h134so80533005iof.0 for ; Thu, 24 Sep 2015 08:33:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hWZtcYyvllla/Gx/XjFsKUOPaL7Lzl1kSlWID8+ADQU=; b=X5ehK3dXu+5z7jtMNEZahbHApd2tss7v1ogClzlDqkn8gx5VSbwqh1ca5WDp1EVhNR h2nKsEp+BXFZIZH+eTpJwhHGRS7XnO3qgjkHTsSL4FqA2B+pDvcqGhBtGGTfvhhhdLVE 0M2A/FbIeK1bWR3JyArzBB/JzMm5uMQoQKX13eirM5GrsP4Pvqnu1kCu0NSaTeNLwG35 DKm+S8hDwmrWbWqf0zkNN2ymU5NRiPZR+smZuLnpIqVBR52CLOJ3PUPWYOo9L0cMto1G iZRPKcXwvjpyzLBoYGLLOgfKLKD1zgNe86NoCrFyUpqNRqxzgV0B/0xYHF76i9nQRkLJ U7lA== MIME-Version: 1.0 X-Received: by 10.107.9.222 with SMTP id 91mr1294498ioj.107.1443108786915; Thu, 24 Sep 2015 08:33:06 -0700 (PDT) Received: by 10.79.37.196 with HTTP; Thu, 24 Sep 2015 08:33:06 -0700 (PDT) In-Reply-To: References: <20150922143628.GB958@amethyst.visucore.com> Date: Thu, 24 Sep 2015 18:33:06 +0300 Message-ID: From: Micha Bailey To: Vincent Truong Content-Type: multipart/alternative; boundary=001a113eba389de05405207ff26b X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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: Thu, 24 Sep 2015 15:33:08 -0000 --001a113eba389de05405207ff26b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That's suboptimal for Europe etc., starting at midnight in the UK, 1 AM in CET, 2 AM in EET (an hour earlier once DST ends). On Wednesday, September 23, 2015, Vincent Truong via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 shoul= d > 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 nicel= y. > > 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 >>> thing. >>> >>> 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=3DMTFwcXZkZ3BkOTlubGliZjliYTg= 2MXZ1OHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ >>> >>> 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 >> > --001a113eba389de05405207ff26b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That's suboptimal for Europe etc., starting at midnight in the UK, 1 AM= in CET,=C2=A02 AM in EET (an hour earlier once DST ends).
=
On Wednesday, September 23, 2015, Vincent Truong via bitcoin-dev <bitcoin-dev@lists.li= nuxfoundation.org> wrote:

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" <bitcoin-dev@lists.= linuxfoundation.org> wrote:
There could not be a worse timing than this for those in Chi= na (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 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
--001a113eba389de05405207ff26b--