public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <lf-lists@mattcorallo.com>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>,
	Bitcoin development mailing list
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: Pieter Wuille <pieter.wuille@gmail.com>,
	Cory Fields <cory@coryfields.com>
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
Date: Fri, 18 Sep 2015 20:14:29 +0000	[thread overview]
Message-ID: <55FC70A5.9080603@mattcorallo.com> (raw)
In-Reply-To: <20150918010709.GB5251@amethyst.visucore.com>

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 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?
> 
> Wladimir
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


  parent reply	other threads:[~2015-09-18 20:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  1:07 [bitcoin-dev] Weekly development meetings on IRC 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 [this message]
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
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=55FC70A5.9080603@mattcorallo.com \
    --to=lf-lists@mattcorallo.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=cory@coryfields.com \
    --cc=laanwj@gmail.com \
    --cc=pieter.wuille@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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