From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TVoax-0006iR-33 for bitcoin-development@lists.sourceforge.net; Tue, 06 Nov 2012 19:13:55 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1TVoar-0003Uu-Dw for bitcoin-development@lists.sourceforge.net; Tue, 06 Nov 2012 19:13:55 +0000 Received: from ishibashi.localnet (unknown [173.170.188.216]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id C971627A296A; Tue, 6 Nov 2012 19:13:43 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 6 Nov 2012 19:13:33 +0000 User-Agent: KMail/1.13.7 (Linux/3.5.4-gentoo; KDE/4.8.5; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201211061913.35016.luke@dashjr.org> X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1TVoar-0003Uu-Dw Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2012 19:13:55 -0000 On Tuesday, November 06, 2012 6:47:34 PM Gavin Andresen wrote: > Thursdays at 18:00 UTC (6PM Europe/1PM east US/10AM west US) seem to > be a good time for the core dev team to meet on the #bitcoin-dev > freenode IRC channel to chat. > > I'd like to talk about: > > o Can we put together a TODO list to get to a 0.8 release candidate ? > > o Is it time to feature-freeze 0.8 and work on just testing the new > features and fixing existing bugs (the issues list keeps getting > longer and longer ... )? Not much has changed besides internal workings, right? Though perhaps that's still significant enough for 0.8. > o BIP process: are we happy with how it is working? What can we do to > improve it? Amir seems to be more and more absent these days, so it might be nice to setup a successor failsafe in the event that he cannot be reached. It would be a shame for the BIP process to fall apart merely because we can't get numbers assigned. But more important to the success of BIP today, I think, is encouraging wider community participation. The stratum mining mess seems to be a direct result of lack of participation in the GBT BIP process (resulting in it not being as ideal as some pools desire) and lack of any peer review/contribution toward the stratum protocol. What can we do to increase awareness of BIP and encourage more collaboration? Luke