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.
>
> ht
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
On Wed, Sep 23, 2015 at 12:01 PM, jl2012 via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> 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.
>
The #bitcoin-dev IRC chann
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 vot
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 Cale
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.
W
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 mi
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 t
It is possible to softfork. Just use Iceland time. Iceland time = UTC
without DST
Btc Drak via bitcoin-dev 於 2015-09-18 16:34 寫到:
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
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 bitcoi
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
> act
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
> act
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 localized, but has an option to change the
>timezone
>> of an
I believe that is out of date. I see neither UTC nor GMT on the website nor on
Android.
Matt
On September 18, 2015 4:30:23 PM EDT, Jeffrey Paul wrote:
>
>> On 18 Sep 2015, at 22:27, Matt Corallo via bitcoin-dev
> wrote:
>>
>> Google Calendar is localized, but has an option to change the
>timez
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 has an option to change the timezone
> > of an event, it jus
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 roughly the same way as everyone else
> - CES
> On 18 Sep 2015, at 22:27, 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 roughly the same way as everyone else
> - C
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 roughly the same way as everyone else
- CEST/PDT/EST/etc.
On 09/18/15 20:24, Btc Drak wrote:
> Google calendar is locali
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. O
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 reg
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
wrote:
>-BEG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> 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 ma
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 expected
I am unlikely to attend at that time, but there is no time that will fit
everybody's schedules. I approve of the idea and look forward to reading
the logs.
On Thu, Sep 17, 2015 at 9:07 PM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> At Mon
-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-
iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV+5
+1
sounds good to me!
On Thu, Sep 17, 2015 at 9:07 PM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> 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 voluntar
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
27 matches
Mail list logo
