From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Weekly development meetings on IRC: schedule
Date: Tue, 22 Sep 2015 16:36:29 +0200 [thread overview]
Message-ID: <20150922143628.GB958@amethyst.visucore.com> (raw)
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=MTFwcXZkZ3BkOTlubGliZjliYTg2MXZ1OHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
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
next reply other threads:[~2015-09-22 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 14:36 Wladimir J. van der Laan [this message]
2015-09-23 11:01 ` [bitcoin-dev] Weekly development meetings on IRC: schedule jl2012
2015-09-23 13:02 ` Btc Drak
2015-09-23 14:06 ` Vincent Truong
2015-09-24 15:33 ` Micha Bailey
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=20150922143628.GB958@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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