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 1TWOGb-0002v2-4f for bitcoin-development@lists.sourceforge.net; Thu, 08 Nov 2012 09:19:17 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TWOGV-0004xe-Jt for bitcoin-development@lists.sourceforge.net; Thu, 08 Nov 2012 09:19:17 +0000 Received: by mail-we0-f175.google.com with SMTP id t44so1221632wey.34 for ; Thu, 08 Nov 2012 01:19:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.84.102 with SMTP id x6mr12043693wiy.12.1352366345410; Thu, 08 Nov 2012 01:19:05 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.216.236.30 with HTTP; Thu, 8 Nov 2012 01:19:05 -0800 (PST) In-Reply-To: References: Date: Thu, 8 Nov 2012 10:19:05 +0100 X-Google-Sender-Auth: APM4gynQi79vy74OFQ1rZkrQMv0 Message-ID: From: Mike Hearn To: Pieter Wuille Content-Type: multipart/alternative; boundary=f46d043bdac49fd96104cdf85345 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1TWOGV-0004xe-Jt Cc: Bitcoin Dev 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: Thu, 08 Nov 2012 09:19:17 -0000 --f46d043bdac49fd96104cdf85345 Content-Type: text/plain; charset=UTF-8 I won't be able to make it this time. My feeling is IRC is a good place to bounce ideas around when time and people happen to be available, but having meetings there will inevitably lead to decision making that's better done in a slower manner via email. Comments: BIP process: are we happy with how it is working? What can we do to improve it? Needing some kind of process to allocate a number is over the top. I skipped this for the bloom filtering BIP. We should take off the part of the {{BIP}} template that says "don't just pick a number and add a bip" - that's exactly what people should do. I'm not sure there's any need for an editing role either. Is it time to feature-freeze 0.8 I'd like more time to get the bloom filtering work in. It'll be easier to promote the 0.8 release if we can sell it as "important scalability/performance improvement for the network, upgrade to help Bitcoin keep growing", as whilst there's no real auto update or organized people who religiously update promotion is very important. I think ultraprune + bloom filtering is the two major scalability improvements we have right now. --f46d043bdac49fd96104cdf85345 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I won't be able to make it this time. =C2=A0My feeling is IRC is a good= place to bounce ideas around when time and people happen to be available, = but having meetings there will inevitably lead to decision making that'= s better done in a slower manner via email.

Comments:

=C2=A0 =C2=A0BIP process: are we happy w= ith how it is working? What can we do to=C2=A0improve it?

=
Needing some kind of process to allocate a number is over the top. I ski= pped this for the bloom filtering BIP. We should take off the part of the {= {BIP}} template that says "don't just pick a number and add a bip&= quot; - that's exactly what people should do. I'm not sure there= 9;s any need for an editing role either.

=C2= =A0 =C2=A0=C2=A0= Is it time to feature-freeze 0.8

I&#= 39;d like more time to get the bloom filtering work in. It'll be easier= to promote the 0.8 release if we can sell it as "important scalabilit= y/performance improvement for the network, upgrade to help Bitcoin keep gro= wing", as whilst there's no real auto update or organized people w= ho religiously update promotion is very important. I think ultraprune + blo= om filtering is the two major scalability improvements we have right now.
--f46d043bdac49fd96104cdf85345--