public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: gb <kiwigb@yahoo•com>
To: "Wladimir J. van der Laan" <laanwj@gmail•com>
Cc: Bitcoin development mailing list
	<bitcoin-dev@lists•linuxfoundation.org>,
	Pieter Wuille <pieter.wuille@gmail•com>,
	Cory Fields <cory@coryfields•com>
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
Date: Mon, 21 Sep 2015 15:51:29 +0200	[thread overview]
Message-ID: <1442843489.2507.10.camel@yahoo.com> (raw)
In-Reply-To: <20150921132914.GA2702@amethyst.visucore.com>


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 mindset than those at 21:00 in Europe, and this is
unavoidable. What is possible is to schedule the meeting every other
week at a time that is better for the "other" half, whoever that might
be. This comes at the cost of not having an exactly same time set every
week.

On Mon, 2015-09-21 at 15:29 +0200, Wladimir J. van der Laan via
bitcoin-dev wrote:
> 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 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?
> 
> From Jonasschnelli's doodle ( http://doodle.com/poll/cihug53sa8u4h2in#table ) it appears that Thursday 19:00 UTC - 20:00 UTC is the most popular time.
> 
> I think scheduling the meeting in UTC (=Iceland time) makes sense internationally because different locales have different DST or no DST at all, so all in all that makes it more complex. It's true that this can make a convenient time less convenient half of the year, for some people, but I don't think there's a time that works for everyone anyway...
> 
> Wladimir
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev




  reply	other threads:[~2015-09-21 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  1:07 Wladimir J. van der Laan
2015-09-18  2:56 ` Alex Morcos
2015-09-18  4:19   ` Peter Todd
2015-09-18  4:30 ` Mark Friedenbach
2015-09-18  4:57 ` Luke Dashjr
2015-09-18  7:04   ` Jonas Schnelli
2015-09-18  8:20     ` Eric Lombrozo
2015-09-18 20:14 ` Matt Corallo
2015-09-18 20:24   ` Btc Drak
2015-09-18 20:27     ` Matt Corallo
2015-09-18 20:30       ` Jeffrey Paul
2015-09-18 20:34         ` Matt Corallo
2015-09-18 20:31       ` Gregory Maxwell
2015-09-18 20:34         ` Btc Drak
2015-09-21 13:01           ` jl2012
2015-09-18 20:36         ` Matt Corallo
2015-09-18 21:50     ` Luke Dashjr
2015-09-18 23:29       ` Dave Scotese
2015-09-18 21:50     ` Luke Dashjr
2015-09-21 13:29 ` Wladimir J. van der Laan
2015-09-21 13:51   ` gb [this message]
2015-09-22 14:03     ` Wladimir J. van der Laan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1442843489.2507.10.camel@yahoo.com \
    --to=kiwigb@yahoo$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=cory@coryfields$(echo .)com \
    --cc=laanwj@gmail$(echo .)com \
    --cc=pieter.wuille@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox