Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 87D92FB8 for ; Fri, 18 Sep 2015 07:05:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from server3 (server3.include7.ch [144.76.194.38]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id B83DF1F2 for ; Fri, 18 Sep 2015 07:05:04 +0000 (UTC) Received: by server3 (Postfix, from userid 115) id 6503D2E604AC; Fri, 18 Sep 2015 09:05:03 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, FSL_HELO_NON_FQDN_1 autolearn=ham version=3.3.1 Received: from Jonass-MacBook-Pro.local (cable-static-140-182.teleport.ch [87.102.140.182]) by server3 (Postfix) with ESMTPSA id D53DA2E60319 for ; Fri, 18 Sep 2015 09:05:02 +0200 (CEST) Message-ID: <55FBB79A.1060504@jonasschnelli.ch> Date: Fri, 18 Sep 2015 09:04:58 +0200 From: Jonas Schnelli User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: bitcoin-dev@lists.linuxfoundation.org References: <20150918010709.GB5251@amethyst.visucore.com> <201509180457.15635.luke@dashjr.org> In-Reply-To: <201509180457.15635.luke@dashjr.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [bitcoin-dev] Weekly development meetings on IRC X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 07:05:05 -0000 -----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-----