From: Eric Lombrozo <elombrozo@gmail.com>
To: Jonas Schnelli <dev@jonasschnelli.ch>,
Jonas Schnelli via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>,
bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
Date: Fri, 18 Sep 2015 01:20:54 -0700 [thread overview]
Message-ID: <0E200A95-ECF4-4588-B0CE-003269C7850C@gmail.com> (raw)
In-Reply-To: <55FBB79A.1060504@jonasschnelli.ch>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
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 <bitcoin-dev@lists.linuxfoundation.org> wrote:
>-----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 may be good to have a
>>> time that many people are expected to be present and current
>>> issues can be discussed.
>>
>> I think it's important to make a point that these meetings are for
>> discussions, and explicitly never decisions, to avoid a repeat of
>> the P2SH events when people have to miss it.
>>
>>> Any preference for days/times?
>>>
>>> What about e.g. every week 15:00-16:00 UTC on Thursday?
>
>+1 for the weekly IRC meetings.
>
>For time and date maybe a Doodle could help:
>http://doodle.com/poll/cihug53sa8u4h2in#table
>
>
>- ---
>jonas
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>
>iQIcBAEBCAAGBQJV+7eaAAoJECnUvLZBb1PsESgQAIQnHDe7owv3OzMvxwupzGaD
>IkTsRtCTSntIb75Wb/KYc0y1L3ilSENRTfZ4nNc4QquqTstkhjU5t+u9T3Mak4D3
>2/5AOiJhV6OLYav1SC7uSJh0B4halnZlTwclU7NOvmnkg40DUpNxmEbf+RvUZup3
>J0EQFxIuhtjIz0HfZTvw6wmstrP3+UJZTbM5fg0FO3TpgmGybAUoQ3eWgRa7v/gR
>OUxnAV//Mus2O80/Z+c5KycZ1Dqc/iN7cQsQFt7kEIK0epkJhkTjoRrW9MyQW04d
>1jv7d0mjEJt+2EiC8UuwpaW2eFmeFnGR0pL4UCY1QsDzGENyHKNbrVg26v1AzIbB
>SNEYN1+fmsXQYosY5t0Z887Ij+u4/GLHciimh5z7fbI5VB1Ng6Wl84maVmP5Zb3L
>MHtkIqQ00RX7GIXUp5+u7eKOO0pH9S08tqo5Ag6ceynJ2lh4Wr8BCNghHzH+ybNJ
>NG3BaSkQmjxnWjW3XplaYyxz6E4qJ8id7qH4s0iaNKchAfXiCaBtbcMfljlyBSn/
>UbzHJk5jlWZEVpxmiMRctFxusk6GI4P+0eRTJrkffskLEjImUN93A8hOLs5Dy+gI
>mm/PZKT2S2qKKa6dlI2kpyPZuRbN7+WSi/FwI0YsUDGl+IoDSqTX7WqRY8cY40ji
>rUgzYTw3Won3BcjHTe9y
>=JsXj
>-----END PGP SIGNATURE-----
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 3208 bytes --]
next prev parent reply other threads:[~2015-09-18 8:20 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 [this message]
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
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=0E200A95-ECF4-4588-B0CE-003269C7850C@gmail.com \
--to=elombrozo@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=dev@jonasschnelli.ch \
/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