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.
>
>
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
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
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
On Mon, Sep 21, 2015 at 03:51:29PM +0200, gb wrote:
>
> Although the planning for this a bit far along now, one consideration I
> might add from experience on working with other transglobal IT projects
Nah, we can always change the scheduling later... But let's first try it out
with one time.
On Fri, Sep 18, 2015 at 03:07:10AM +0200, Wladimir J. van der Laan 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
Although the planning for this a bit far along now, one consideration I
might add from experience on working with other transglobal IT projects
is the effect of timezones on local mood/alertness/awareness etc. The
guys at 9am pinging on their first coffee in the antipodes will be in a
different
I am in a timezone that uses DST (currently PDT), but I would like us to
use a timezone that does NOT use DST. It will be nice to have something
that reflects the seasonal patterns like my own body does. I hate the time
change in both ways.
On Fri, Sep 18, 2015 at 2:50 PM, Luke Dashjr via
On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
wrote:
> 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
Yes, I'm aware, however they are closer to each other than UTC is to either :p.
On September 18, 2015 4:31:28 PM EDT, Gregory Maxwell
wrote:
>On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
> wrote:
>> Google Calendar is
I love the weekly meeting idea...but timezones might be an issue.
My general preference would be afternoons to late evenings pacific time, but
that translates to late night/early morning for those in europe.
On September 18, 2015 12:04:58 AM PDT, Jonas Schnelli via bitcoin-dev
Urgh... Can we hardfork time? It's clearly in need of an upgrade...
On Fri, Sep 18, 2015 at 9:31 PM, Gregory Maxwell wrote:
> On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
> wrote:
> > Google Calendar is localized, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17 September 2015 19:56:17 GMT-07:00, Alex Morcos via bitcoin-dev
wrote:
>+1
>sounds good to me!
+2
My schedule is chaotic, but I'll try to attend.
-BEGIN PGP SIGNATURE-
On Friday, September 18, 2015 1:07:10 AM Wladimir J. van der Laan via
bitcoin-dev wrote:
> 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
14 matches
Mail list logo